HKVFS Wiki

LINK 16: Difference between revisions

Page Discussion

LINK 16 (view source)

Revision as of 09:20, 7 July 2024

1,545 bytes added ,  4 months ago
m
no edit summary
(Created page with "==='''What is LINK 16?'''=== Link 16 is a secure, jam-resistant, digital data link used by military aircraft, including the F-16, for real-time exchange of tactical information. It enables seamless communication and coordination between friendly forces operating in the air, on land, and at sea, this system is by US and NATO. ==='''How does LINK 16 work?'''=== Link 16 operates in the UHF frequency band, providing line-of-sight and beyond-line-of-sight connectivity over c...")
 
mNo edit summary
Line 11: Line 11:


==='''Acronyms'''===
==='''Acronyms'''===
{| class="wikitable"
{| class="wikitable" style="font-weight:bold;"
|+
|- style="text-align:center; background-color:#EAECF0; color:#202122;"
!Short form
! Short form
!Full form
! Full form
!Implemented in BMS
! style="font-size:100%;" | Implemented in BMS
!Meaning
! Meaning
|- style="background-color:#F8F9FA; color:#202122;"
| N.A.
| Donor
| style="text-align:center; font-weight:normal;" | No
| style="font-weight:normal;" |
|- style="background-color:#F8F9FA; color:#202122;"
| FC
| Fighter Channel
| 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="background-color:#F8F9FA; color:#202122;"
| IDM
| Improved Data Modem
| 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="background-color:#F8F9FA; color:#202122;"
| JDN
| Joint Data Net
| 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="background-color:#F8F9FA; color:#202122;"
| JTIDS
| Joint Tactical Information Distribution System
| 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="background-color:#F8F9FA; color:#202122;"
| MC
| Mission Channel
| 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="background-color:#F8F9FA; color:#202122;"
| NDL
| Network Design Load
| style="text-align:center; font-weight:normal;" | Yes
| style="font-weight:normal;" | The system used to
|- style="background-color:#F8F9FA; color:#202122;"
| NPG
| Network Participation Groups
| 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="background-color:#F8F9FA; color:#202122;"
| PPLI
| Precise Participant Location and Identification
| style="text-align:center; font-weight:normal;" | Yes
| style="font-weight:normal;" |
|- style="background-color:#F8F9FA; color:#202122;"
| SC
| Special Channel
| 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.
|-
|-
|N.A.
| style="background-color:#F8F9FA; color:#202122;" | SURV
|'''Donor'''
| style="background-color:#F8F9FA; color:#202122;" | Surveillance
|
| style="text-align:center; background-color:#F8F9FA; color:#202122; font-weight:normal;" | Yes
|
| style="font-weight:normal;" | m
|-
|- style="font-weight:normal;"
|'''FC'''
|  
|'''Fighter Channel'''
|  
|
|  
|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'''
|'''Improved Data Modem'''
|
|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'''
|'''Joint Data Net'''
|
|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'''
|'''Joint Tactical Information Distribution System'''
|
|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'''
|'''Mission Channel'''
|
|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.
|-
|'''NDL'''
|'''Network Design Load'''
|
|The system used to
|-
|'''NPG'''
|'''Network Participation Groups'''
|
|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'''
|'''Precise Participant Location and Identification'''
|
|
|-
|'''SC'''
|'''Special Channel'''
|
|This Channel establishes for SEAD NPG and identification information.The numerical value can be set between 0 and 126.
|-
|'''SURV'''
|'''Surveillance'''
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|}
|}


Retrieved from "https://wiki.hkvfs.com/index.php/Special:MobileDiff/88"