LINK 16: Difference between revisions

Jump to navigation Jump to search

LINK 16 (view source)

Revision as of 08:03, 9 July 2024

257 bytes removed ,  4 months ago
no edit summary
mNo edit summary
No edit summary
Line 1: Line 1:
[[File:Link 16 Systems tree.png|thumb|499x499px|Link 16 Systems tree]]
[[File:Link 16 Systems tree.png|thumb|499x499px|Link 16 Systems tree]]


==='''What is LINK 16?'''===
===What is LINK 16? ===
Link-16 is a high capacity, secure, jam-resistant, nodeless broadcast-type RF data link that uses a Time Division Multiple Access (TDMA) protocol. It provides information distribution, position location, and identification capabilities in an integrated form for tactical military operations. Link-16 utilises the Joint Tactical Information Distribution System (JTIDS) or the Multi-Functional Information Distribution System (MIDS) terminals, and the protocols, conventions, and fixed word message formats defined by STANAG 5516. JTIDS/MIDS operates in the upper ultra high frequency Lx band.
Link-16 is a high capacity, secure, jam-resistant, nodeless broadcast-type RF data link that uses a Time Division Multiple Access (TDMA) protocol. It provides information distribution, position location, and identification capabilities in an integrated form for tactical military operations. Link-16 utilises the Joint Tactical Information Distribution System (JTIDS) or the Multi-Functional Information Distribution System (MIDS) terminals, and the protocols, conventions, and fixed word message formats defined by STANAG 5516. JTIDS/MIDS operates in the upper ultra high frequency Lx band.


==='''How does LINK 16 work?'''===
===How does LINK 16 work?===
Link 16 operates in the UHF frequency band, providing line-of-sight and beyond-line-of-sight connectivity over considerable distances. It employs a [https://wikipedia.org/wiki/Time-division%20multiple%20access TDMA] (Time Division Multiple Access) architecture, allowing multiple users to transmit and receive data on the same frequency without interference.
Link 16 operates in the UHF frequency band, providing line-of-sight and beyond-line-of-sight connectivity over considerable distances. It employs a [https://wikipedia.org/wiki/Time-division%20multiple%20access TDMA] (Time Division Multiple Access) architecture, allowing multiple users to transmit and receive data on the same frequency without interference.


===What are the 3 requirements to get into link 16?===
===What are the 3 requirements to get into link 16?===
* Correct crypto (Key)
*Correct crypto (Key)
* Network Design Load (NDL)
*Network Design Load (NDL)
* Time synchronization (NTR)
*Time synchronization (NTR)


===Which F-16 Variants have LINK 16 implemented?===
===Which F-16 Variants have LINK 16 implemented? ===
Check [[F-15/F-16 Variants|F-16 Variants]].
Check [[F-15/F-16 Variants|F-16 Variants]].


===What is a J-Series message?===
===What is a J-Series message?===
* It is a template for data exchange that is programmed into the link 16 structure
*It is a template for data exchange that is programmed into the link 16 structure
* Its data fields are populated by transmitting aircraft and interpreted by receiving aircraft
* Its data fields are populated by transmitting aircraft and interpreted by receiving aircraft


===LINK 16 Limitations in Falcon BMS ===
===LINK 16 Limitations in Falcon BMS===
* Only C2 can provide SURV air track information.
*Only C2 can provide SURV air track information.
* Secondary fighter air target tracks, Lock lines and AMRAAM shotlines are not currently implemented.
*Secondary fighter air target tracks, Lock lines and AMRAAM shotlines are not currently implemented.
* Ground LINK 16 is not currently implemented.
*Ground LINK 16 is not currently implemented.


==='''LINK 16 PPLI vs Surveillance'''===
===LINK 16 PPLI vs Surveillance ===
* Add later
*Add later


==='''Acronyms'''===
===Acronyms ===
{| class="wikitable sortable" style="font-weight:bold;"
{| class="wikitable sortable" style="font-weight:bold;"
|- style="text-align:center;"
|- style="text-align:center;"
! Short form
!Short form
! Full form
!Full form
! style="font-size:100%;" | Implemented in BMS
! style="font-size:100%;" |Implemented in BMS
! Meaning
!Meaning
|-
|-
| style="background-color:#fe0000;" |  
| style="background-color:#fe0000;" |
| Donor
|Donor
| style="text-align:center; font-weight:normal;" | Partially yes
| style="text-align:center; font-weight:normal;" |Partially yes
| style="font-weight:normal;" | For situational awareness during a mission, pilots may want to monitor aircraft or targets reported by aircraft that aren’t part of their flight or team. These aircraft, known as donors, can be designated during mission planning (via the Data Cartridge), or selection or deselection can be managed in the cockpit through the LINK 16 DNR page on the DED.'''<br />Note: Secondary fighter air target tracks, Lock lines and AMRAAM shotlines are not currently implemented.'''
| style="font-weight:normal;" |For situational awareness during a mission, pilots may want to monitor aircraft or targets reported by aircraft that aren’t part of their flight or team. These aircraft, known as donors, can be designated during mission planning (via the Data Cartridge), or selection or deselection can be managed in the cockpit through the LINK 16 DNR page on the DED.'''<br />Note: Secondary fighter air target tracks, Lock lines and AMRAAM shotlines are not currently implemented.'''
|-
|-
| FC
|FC
| Fighter Channel
|Fighter Channel
| style="text-align:center; font-weight:normal;" | Yes
| style="text-align:center; font-weight:normal;" |Yes
| style="font-weight:normal;" | This Channel establishes the subnet on intraflight communications. This subnet is used to share ownship targets within a flight. The pilot would change the Fighter Channel to receive target information from aircraft that are operating on a different fighter-to-fighter subnet (e.g. different donors) or to join another flight. All members of the flight must select the same Fighter Channel; otherwise, the Link 16 target sorting messages from the flight members will not be received. The numerical value can be set between 0 and 126.
| style="font-weight:normal;" |This Channel establishes the subnet on intraflight communications. This subnet is used to share ownship targets within a flight. The pilot would change the Fighter Channel to receive target information from aircraft that are operating on a different fighter-to-fighter subnet (e.g. different donors) or to join another flight. All members of the flight must select the same Fighter Channel; otherwise, the Link 16 target sorting messages from the flight members will not be received. The numerical value can be set between 0 and 126.
|-
|-
| IDM
| IDM
| Improved Data Modem
|Improved Data Modem
| style="text-align:center; font-weight:normal;" | Yes
| style="text-align:center; font-weight:normal;" |Yes
| style="font-weight:normal;" | The F-16's improved data modem is a crucial component of its avionics system, enhancing communication capabilities for both command and control purposes anddata transfer. The IDM facilitates seamless and secure transmission of various typesof data, including mission-critical information, sensor data, and tactical updates between aircrafts. IDM was designed in the late 70’s before LINK 16 was on the horizon of the aircraft manufactures. Even if limited in features compared to MIDS/JTIDS systems, it follows the same principle of exchanging data.
| style="font-weight:normal;" |The F-16's improved data modem is a crucial component of its avionics system, enhancing communication capabilities for both command and control purposes anddata transfer. The IDM facilitates seamless and secure transmission of various typesof data, including mission-critical information, sensor data, and tactical updates between aircrafts. IDM was designed in the late 70’s before LINK 16 was on the horizon of the aircraft manufactures. Even if limited in features compared to MIDS/JTIDS systems, it follows the same principle of exchanging data.
|-
|-
| JDN
|JDN
| Joint Data Net
|Joint Data Net
| style="text-align:center; font-weight:normal;" | Yes
| style="text-align:center; font-weight:normal;" |Yes
| style="font-weight:normal;" | An interconnected network of JTIDS/MIDS based systems which links air and missile defence Command and Control and weapons systems across L16 capable forces.
| style="font-weight:normal;" |An interconnected network of JTIDS/MIDS based systems which links air and missile defence Command and Control and weapons systems across L16 capable forces.
|-
|-
| JTIDS
|JTIDS
| Joint Tactical Information Distribution System
|Joint Tactical Information Distribution System
| style="text-align:center; font-weight:normal;" | Yes
| style="text-align:center; font-weight:normal;" |Yes
| style="font-weight:normal;" | Refers to the communications component of Link-16. It encompasses the Class 2 terminal software, hardware, RF equipments, and the high-capacity, secure, antijam waveform that they generate. Among NATO subscribers, the equivalent term for JTIDS is the Multifunctional Information Distribution System (MIDS).
| style="font-weight:normal;" |Refers to the communications component of Link-16. It encompasses the Class 2 terminal software, hardware, RF equipments, and the high-capacity, secure, antijam waveform that they generate. Among NATO subscribers, the equivalent term for JTIDS is the Multifunctional Information Distribution System (MIDS).
|-
|-
| MC
|MC
| Mission Channel
|Mission Channel
| style="text-align:center; font-weight:normal;" | Yes
| style="text-align:center; font-weight:normal;" |Yes
| style="font-weight:normal;" | This Channel establishes the subnet on the C2 (e.g. AWACS or ABCCC) aircraft is operating. The control NPG is used by C2 to transmit assignments to the flight lead and for the flight lead to transmit responses and report assignment status. As a flight progresses to the target area, the controlling aircraft could change. When a controller change is required, the current controlling aircraft transmits a request for handover message to the flight indicating the new controllers subnet (i.e., MC). After accepting the handover request, the flight members change the mission channel to communicate with the new controller. The numerical value can be set between 0 and 127.
| style="font-weight:normal;" |This Channel establishes the subnet on the C2 (e.g. AWACS or ABCCC) aircraft is operating. The control NPG is used by C2 to transmit assignments to the flight lead and for the flight lead to transmit responses and report assignment status. As a flight progresses to the target area, the controlling aircraft could change. When a controller change is required, the current controlling aircraft transmits a request for handover message to the flight indicating the new controllers subnet (i.e., MC). After accepting the handover request, the flight members change the mission channel to communicate with the new controller. The numerical value can be set between 0 and 127.
|-
|-
| MIDS
| MIDS
| Multifunctional Information Distribution System
|Multifunctional Information Distribution System
| style="text-align:center; font-weight:normal;" | Yes
| style="text-align:center; font-weight:normal;" |Yes
| style="font-weight:normal;" | See JTIDS
| style="font-weight:normal;" |See JTIDS
|-
|-
| NDL
|NDL
| Network Design Load
|Network Design Load
| style="text-align:center; font-weight:normal;" | Yes
| style="text-align:center; font-weight:normal;" |Yes
| style="font-weight:normal;" | This system used to initialize the JTIDS/MIDS terminal
| style="font-weight:normal;" |This system used to initialize the JTIDS/MIDS terminal
|-
|-
| NPG
|NPG
| Network Participation Groups
|Network Participation Groups
| style="text-align:center; font-weight:normal;" | Yes
| style="text-align:center; font-weight:normal;" |Yes
| style="font-weight:normal;" | FC and MC channels are part of dedicated NPG’s. Each channel and its number define what data can be exchanged on that channel. If you create a package for example, all LINK 16 capable aircraft of this package will have the same FC and MC (because one AWACS controller will be responsible for this package).
| style="font-weight:normal;" |FC and MC channels are part of dedicated NPG’s. Each channel and its number define what data can be exchanged on that channel. If you create a package for example, all LINK 16 capable aircraft of this package will have the same FC and MC (because one AWACS controller will be responsible for this package).
|-
|-
| PPLI
| PPLI
| Precise Participant Location and Identification
|Precise Participant Location and Identification
| style="text-align:center; font-weight:normal;" | Yes
| style="text-align:center; font-weight:normal;" |Yes
| style="font-weight:normal;" | PPLI air tracks are shared between aircraft sharing the same NPG. Each PPLI message contains an abundance ofinformation about a unit, including its detailed position andidentification information, its time quality, its IFF codes, and much more.
| style="font-weight:normal;" |PPLI air tracks are shared between aircraft sharing the same NPG. Each PPLI message contains an abundance ofinformation about a unit, including its detailed position andidentification information, its time quality, its IFF codes, and much more.
|-
|-
| SC
|SC
| Special Channel
|Special Channel
| style="text-align:center; font-weight:normal;" | Yes
| style="text-align:center; font-weight:normal;" |Yes
| style="font-weight:normal;" | This Channel establishes for SEAD NPG and identification information.The numerical value can be set between 0 and 126.
| style="font-weight:normal;" |This Channel establishes for SEAD NPG and identification information.The numerical value can be set between 0 and 126.
|-
|-
| SURV
| SURV
| Surveillance
|Surveillance
| style="text-align:center; font-weight:normal;" | Yes
| style="text-align:center; font-weight:normal;" |Yes
| style="font-weight:normal;" | This message is used to share air trajectory data and is primarily disseminated by command and control agencies.
| style="font-weight:normal;" |This message is used to share air trajectory data and is primarily disseminated by command and control agencies.
|}
|}


==='''LINK 16 Net Message Table (STANAG 5516)'''===
===LINK 16 Net Message Table (STANAG 5516) ===
{| class="wikitable" style="font-weight:bold; vertical-align:middle; background-color:#ffffff;"
{| class="wikitable" style="font-weight:bold; vertical-align:middle; background-color:#ffffff;"
|- style="text-align:center;"
|- style="text-align:center;"
! J
!J
! Series
!Series
! Message
!Message
! Note
!Note
|-
|-
| J0.0
|J0.0
| rowspan="15" style="text-align:center;" | Network Management
| rowspan="15" style="text-align:center;" |Network Management
| style="font-weight:normal;" | Initial Entry
| style="font-weight:normal;" | Initial Entry
| style="font-weight:normal;" |
| style="font-weight:normal;" |
|-
|-
| J0.1
|J0.1
| style="font-weight:normal;" | Test Message
| style="font-weight:normal;" | Test Message
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J0.2
|J0.2
| style="font-weight:normal;" | Net Time Update
| style="font-weight:normal;" | Net Time Update
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J0.3
|J0.3
| style="font-weight:normal;" | Time Slot Assignment
| style="font-weight:normal;" | Time Slot Assignment
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J0.4
|J0.4
| style="font-weight:normal;" | Radio Relay Control
| style="font-weight:normal;" | Radio Relay Control
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J0.5
|J0.5
| style="font-weight:normal;" | Repromulgation Relay
| style="font-weight:normal;" | Repromulgation Relay
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J0.6
|J0.6
| style="font-weight:normal;" | Comm Control
| style="font-weight:normal;" | Comm Control
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J0.7
|J0.7
| style="font-weight:normal;" | TSR Announcement
| style="font-weight:normal;" | TSR Announcement
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J1.0
|J1.0
| style="font-weight:normal;" | Connectivity Interrogation
| style="font-weight:normal;" | Connectivity Interrogation
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J1.1
|J1.1
| style="font-weight:normal;" | Connectivity Status
| style="font-weight:normal;" | Connectivity Status
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J1.2
|J1.2
| style="font-weight:normal;" | Route Establishment
| style="font-weight:normal;" | Route Establishment
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J1.3
|J1.3
| style="font-weight:normal;" | Acknowledgment
| style="font-weight:normal;" | Acknowledgment
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J1.4
|J1.4
| style="font-weight:normal;" | Communication Status
| style="font-weight:normal;" | Communication Status
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J1.5
|J1.5
| style="font-weight:normal;" | Net Control Initialization
| style="font-weight:normal;" | Net Control Initialization
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J1.6
|J1.6
| style="font-weight:normal;" | Needline PG Assignment
| style="font-weight:normal;" | Needline PG Assignment
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J2.0
|J2.0
| rowspan="6" style="text-align:center;" | Precise Participation Location & Identification (PPLI)
| rowspan="6" style="text-align:center;" |Precise Participation Location & Identification (PPLI)
| style="font-weight:normal;" | Indirect Interface Unit PPLI
| style="font-weight:normal;" | Indirect Interface Unit PPLI
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J2.2
|J2.2
| style="font-weight:normal;" | Air PPLI
| style="font-weight:normal;" | Air PPLI
| style="font-weight:normal;" | Transmitted by Link 16 air participants that provides network participation status, identification, positional information, and relative navigation information. This message can include the voice call sign, position (latitude/longitude), altitude, course, IFF codes, air platform type (generic - fighter, bomber, attack, etc.), air platform activity (engaging, investigating, etc.), etc.  
| style="font-weight:normal;" | Transmitted by Link 16 air participants that provides network participation status, identification, positional information, and relative navigation information. This message can include the voice call sign, position (latitude/longitude), altitude, course, IFF codes, air platform type (generic - fighter, bomber, attack, etc.), air platform activity (engaging, investigating, etc.), etc.
|-
|-
| J2.3
|J2.3
| style="font-weight:normal;" | Surface (Maritime) PPLI
| style="font-weight:normal;" | Surface (Maritime) PPLI
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J2.4
|J2.4
| style="font-weight:normal;" | Subsurface (Maritime) PPLI
| style="font-weight:normal;" | Subsurface (Maritime) PPLI
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J2.5
|J2.5
| style="font-weight:normal;" | Land (Ground) Point PPLI
| style="font-weight:normal;" | Land (Ground) Point PPLI
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J2.6
|J2.6
| style="font-weight:normal;" | Land (Ground) Track PPLI
| style="font-weight:normal;" | Land (Ground) Track PPLI
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J3.0
|J3.0
| rowspan="8" style="text-align:center;" | Surveillance
| rowspan="8" style="text-align:center;" |Surveillance
| style="font-weight:normal;" | Reference Point
| style="font-weight:normal;" | Reference Point
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J3.1
|J3.1
| style="font-weight:normal;" | Emergency Point
| style="font-weight:normal;" | Emergency Point
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J3.2
|J3.2
| style="font-weight:normal;" | Air Track
| style="font-weight:normal;" | Air Track
| style="font-weight:normal;" | This message is used to exchange information on air tracks. The message is primarily transmitted by a command and control agency. The message includes exercise (exercise messages are filtered out)/nonexercise tracks, track number, strength, position, speed, course, identity (pending, unknown, assumed friend, friend, neutral, suspect, hostile, or undefined), IFF codes, air platform type (generic - fighter, bomber, attack, etc.), air platform activity (engaging, investigating, etc.), air specific type (F-15, F-16, Mig-29, etc.), etc.  
| style="font-weight:normal;" | This message is used to exchange information on air tracks. The message is primarily transmitted by a command and control agency. The message includes exercise (exercise messages are filtered out)/nonexercise tracks, track number, strength, position, speed, course, identity (pending, unknown, assumed friend, friend, neutral, suspect, hostile, or undefined), IFF codes, air platform type (generic - fighter, bomber, attack, etc.), air platform activity (engaging, investigating, etc.), air specific type (F-15, F-16, Mig-29, etc.), etc.
|-
|-
| J3.3
|J3.3
| style="font-weight:normal;" | Surface (Maritime)
| style="font-weight:normal;" | Surface (Maritime)
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J3.4
|J3.4
| style="font-weight:normal;" | Subsurface (Maritime) Track
| style="font-weight:normal;" | Subsurface (Maritime) Track
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J3.5
|J3.5
| style="font-weight:normal;" | Land (Ground) Point/Track
| style="font-weight:normal;" | Land (Ground) Point/Track
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J3.6
|J3.6
| style="font-weight:normal;" | Space Track
| style="font-weight:normal;" | Space Track
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J3.7
|J3.7
| style="font-weight:normal;" | Electronic Warfare Product Information
| style="font-weight:normal;" | Electronic Warfare Product Information
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J5.4
|J5.4
| style="text-align:center;" | Anti Submarine Warfare
| style="text-align:center;" |Anti Submarine Warfare
| style="font-weight:normal;" | Acoustic Bearing/Range
| style="font-weight:normal;" | Acoustic Bearing/Range
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J6.0
|J6.0
| style="text-align:center;" | Intelligence
| style="text-align:center;" |Intelligence
| style="font-weight:normal;" | Intelligence Information
| style="font-weight:normal;" | Intelligence Information
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J7.0
|J7.0
| rowspan="10" style="text-align:center;" | Track Management
| rowspan="10" style="text-align:center;" |Track Management
| style="font-weight:normal;" | Track Management
| style="font-weight:normal;" | Track Management
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J7.1
|J7.1
| style="font-weight:normal;" | Data Update Request
| style="font-weight:normal;" | Data Update Request
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J7.2
|J7.2
| style="font-weight:normal;" | Correlation
| style="font-weight:normal;" | Correlation
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J7.3
|J7.3
| style="font-weight:normal;" | Pointer
| style="font-weight:normal;" | Pointer
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J7.4
|J7.4
| style="font-weight:normal;" | Track Identifier
| style="font-weight:normal;" | Track Identifier
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J7.5
|J7.5
| style="font-weight:normal;" | IFF/SIF Management
| style="font-weight:normal;" | IFF/SIF Management
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J7.6
|J7.6
| style="font-weight:normal;" | Filter Management
| style="font-weight:normal;" | Filter Management
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J7.7
|J7.7
| style="font-weight:normal;" | Association
| style="font-weight:normal;" | Association
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J8.0
|J8.0
| style="font-weight:normal;" | Unit Designator
| style="font-weight:normal;" | Unit Designator
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J8.1
|J8.1
| style="font-weight:normal;" | Mission Correlation Change
| style="font-weight:normal;" | Mission Correlation Change
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J9.0
|J9.0
| rowspan="6" style="text-align:center;" | Weapons Coordination &amp; Management
| rowspan="6" style="text-align:center;" |Weapons Coordination &amp; Management
| style="font-weight:normal;" | Command
| style="font-weight:normal;" | Command
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J9.1
|J9.1
| style="font-weight:normal;" | Engagement Coordination
| style="font-weight:normal;" | Engagement Coordination
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J10.2
|J10.2
| style="font-weight:normal;" | ECCM Coordination
| style="font-weight:normal;" | ECCM Coordination
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J10.3
|J10.3
| style="font-weight:normal;" | Handover
| style="font-weight:normal;" | Handover
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J10.5
|J10.5
| style="font-weight:normal;" | Controlling Unit Report
| style="font-weight:normal;" | Controlling Unit Report
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J10.6
|J10.6
| style="font-weight:normal;" | Pairing
| style="font-weight:normal;" | Pairing
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J12.0
|J12.0
| rowspan="8" style="text-align:center;" | Control
| rowspan="8" style="text-align:center;" |Control
| style="font-weight:normal;" | Mission Assignment
| style="font-weight:normal;" | Mission Assignment
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J12.1
|J12.1
| style="font-weight:normal;" | Vector
| style="font-weight:normal;" | Vector
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J12.2
|J12.2
| style="font-weight:normal;" | Precision AC Direction
| style="font-weight:normal;" | Precision AC Direction
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J12.3
|J12.3
| style="font-weight:normal;" | Flight Path
| style="font-weight:normal;" | Flight Path
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J12.4
|J12.4
| style="font-weight:normal;" | Controlling Unit Change
| style="font-weight:normal;" | Controlling Unit Change
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J12.5
|J12.5
| style="font-weight:normal;" | Target/Track Correlation
| style="font-weight:normal;" | Target/Track Correlation
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J12.6
|J12.6
| style="font-weight:normal;" | Target Sorting
| style="font-weight:normal;" | Target Sorting
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J12.7
|J12.7
| style="font-weight:normal;" | Target Bearing
| style="font-weight:normal;" | Target Bearing
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J13.0
|J13.0
| rowspan="5" style="text-align:center;" | Platform &amp; System Status
| rowspan="5" style="text-align:center;" |Platform &amp; System Status
| style="font-weight:normal;" | Airfield Status
| style="font-weight:normal;" | Airfield Status
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J13.2
|J13.2
| style="font-weight:normal;" | Air Platform Status
| style="font-weight:normal;" | Air Platform Status
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J13.3
|J13.3
| style="font-weight:normal;" | Surface Platform Status
| style="font-weight:normal;" | Surface Platform Status
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J13.4
|J13.4
| style="font-weight:normal;" | Subsurface Platform Status
| style="font-weight:normal;" | Subsurface Platform Status
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J13.5
|J13.5
| style="font-weight:normal;" | Land Platform Status
| style="font-weight:normal;" | Land Platform Status
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J14.0
|J14.0
| rowspan="2" style="text-align:center;" | Electronic Warfare
| rowspan="2" style="text-align:center;" |Electronic Warfare
| style="font-weight:normal;" | EW Parametric
| style="font-weight:normal;" | EW Parametric
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J14.2
|J14.2
| style="font-weight:normal;" | EW Coordination &amp;amp;amp;amp;amp;amp;amp; Control
| style="font-weight:normal;" | EW Coordination &amp;amp;amp;amp;amp;amp;amp; Control
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J15.0
|J15.0
| rowspan="3" style="text-align:center;" | Threat Warning
| rowspan="3" style="text-align:center;" |Threat Warning
| style="font-weight:normal;" | Threat Warning
| style="font-weight:normal;" | Threat Warning
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J16.0
|J16.0
| style="font-weight:normal;" | Imagery
| style="font-weight:normal;" | Imagery
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J17.0
|J17.0
| style="font-weight:normal;" | Weather over target
| style="font-weight:normal;" | Weather over target
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J28.0
|J28.0
| rowspan="8" style="text-align:center;" | National Use
| rowspan="8" style="text-align:center;" |National Use
| style="font-weight:normal;" | US National 1-Army
| style="font-weight:normal;" | US National 1-Army
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J28.1
|J28.1
| style="font-weight:normal;" | US National 2-Navy
| style="font-weight:normal;" | US National 2-Navy
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J28.2
|J28.2
| style="font-weight:normal;" | US National 3-USAF
| style="font-weight:normal;" | US National 3-USAF
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J28.3
|J28.3
| style="font-weight:normal;" | US National 4-USMC
| style="font-weight:normal;" | US National 4-USMC
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J28.4
|J28.4
| style="font-weight:normal;" | FR National 1
| style="font-weight:normal;" | FR National 1
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J28.5
|J28.5
| style="font-weight:normal;" | FR National 2
| style="font-weight:normal;" | FR National 2
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J28.6
|J28.6
| style="font-weight:normal;" | US National 5-NSA
| style="font-weight:normal;" | US National 5-NSA
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J28.7
|J28.7
| style="font-weight:normal;" | UK National 1
| style="font-weight:normal;" | UK National 1
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J31.0
|J31.0
| rowspan="3" style="text-align:center;" | Miscellaneous
| rowspan="3" style="text-align:center;" |Miscellaneous
| style="font-weight:normal;" | OTAR Management
| style="font-weight:normal;" | OTAR Management
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J31.1
|J31.1
| style="font-weight:normal;" | OTAR
| style="font-weight:normal;" | OTAR
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| J31.7
|J31.7
| style="font-weight:normal;" | No Statement
| style="font-weight:normal;" | No Statement
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| RTT-A
|RTT-A
| rowspan="3" style="text-align:center;" | Round Trip Timing
| rowspan="3" style="text-align:center;" |Round Trip Timing
| style="font-weight:normal;" | RTT Addressed
| style="font-weight:normal;" | RTT Addressed
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| RTT-B
|RTT-B
| style="font-weight:normal;" | RTT Broadcast
| style="font-weight:normal;" | RTT Broadcast
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|-
|-
| RTT-REP
|RTT-REP
| style="font-weight:normal;" | RTT Reply
| style="font-weight:normal;" | RTT Reply
| style="font-weight:normal;" |  
| style="font-weight:normal;" |
|}
|}


==Notes==
==Notes==
<references />
<references />
Retrieved from "https://wiki.hkvfs.com/index.php/Special:MobileDiff/128"

Navigation menu