Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
So in short, all PAF assets have full compatibility with eachother?
US, Chinese and others...?
Is it me or this sounds surprisingly similar to the protocols used for data exchange using ********
Where do you think the 'Joint Tactical Information Distribution System' came from?
But seriously, like I said earlier, the idea of having a group where individuals shares relevant data at the expense and exclusion of other data is not new. The problems have always been the determination of what is 'relevant' and how to make that relevancy have priority among the clutter of communication where everyone believe his sh!t is of the highest priority. Need and want have a push/pull relationship and technology finally made that possible.
The declassified Link 16 standards are really adaptations of the civilian aviation standards of (mostly) one-way data transmission.Exactly, So if the contributor in this case.. becomes the Pakistani AEW system.. and is using the declassified standard for Link-16 messages.(available). It can not only interact and pass on information to the MIDS on the F-16. but also to any other platform that has the ability to read link-16 format.
I am not referring to the cryptographic part.. since that you can implement on your own..or select.
I am referring to the passing of Link-16 messages.. basically the protocol.
The reason I am asking you for your opinion is because this was being done where I worked. Initially the idea was to let the Links between the swedes Awacs and the F-16s communicate to the ground stations(basically complete packages with no Pakistani knowledge of what went inside the end terminals till it got to the application layer... and from there repackaging that data into a local datalink and re-transmitting it out to other assets.
However, it was decided to give the swedish systems the ability to manage the Chinese systems as well, so a custom datalink was designed inhouse with assistance(of which I worked on secure voice) that allows the swedish system to play a similar role as the E-3 does for the Chinese systems along with the F-16's.
In other words, you may not be able to replicate the cryptography.. but everything below the presentation layer can be replicated.
http://www.idlsoc.com/Documents/Symposiums/IDLS2006/viasat_quistorf.pdf
Infact.. I think it was YOU who first led me to the standards and references for Link-16 through PMwhen the initial work on it began! about two years ago.
So, @gambit has been a contributor to the development of the Pakistan Air Force's Datalink
Back then, broadband was nowhere as broad as we take for granted today, as far as the word implies. Your iPhone is probably more capable than what Boeing started. Crytographic protocols were already explored to prevent portable electronic devices (PED) from 'jamming' the increasingly fly-by-wire avionics, especially two-way communication and entertainment, that we see today. For flight controls subordinate systems, shielding is the best option instead of decryption of cryptographic protocols. We do not want delays between pilot commands and aileron response.The Boeing Company began research into broadband communications in the 1980s as part of its work for the U.S. government. As the Cold War ended, the company entered discussions with commercial airlines, most notably American and Delta, about how to adapt the technology to civilian use. During the late 1990s, these initiatives became known as Aviation Information Services and then Global Mobile Services.
The motors in electric shavers emit too low of freqs and too weak in amplitude to have any effects. As for the rest, any spurious radiation that remotely may be in the realm of avionics is also too weak in amplitude. More like in the 'near field communication' (NFC) usage area.There are still unknowns about the radio signals that portable electronic devices (PEDs) and cell phones give off. These signals, especially in large quantities and emitted over a long time, may unintentionally affect aircraft communications, navigation, flight control and electronic equipment.
Federal Aviation Administration regulations prohibit use of most portable electronic devices aboard aircraft, but they specifically exempt portable voice recorders, hearing aids, heart pacemakers and electric shavers because they dont give off signals that might interfere with aircraft systems.
So in short, all PAF assets have full compatibility with eachother?
US, Chinese and others...?
Exactly, So if the contributor in this case.. becomes the Pakistani AEW system.. and is using the declassified standard for Link-16 messages.(available). It can not only interact and pass on information to the MIDS on the F-16. but also to any other platform that has the ability to read link-16 format.
I am not referring to the cryptographic part.. since that you can implement on your own..or select.
I am referring to the passing of Link-16 messages.. basically the protocol.
The reason I am asking you for your opinion is because this was being done where I worked. Initially the idea was to let the Links between the swedes Awacs and the F-16s communicate to the ground stations(basically complete packages with no Pakistani knowledge of what went inside the end terminals till it got to the application layer... and from there repackaging that data into a local datalink and re-transmitting it out to other assets.
However, it was decided to give the swedish systems the ability to manage the Chinese systems as well, so a custom datalink was designed inhouse with assistance(of which I worked on secure voice) that allows the swedish system to play a similar role as the E-3 does for the Chinese systems along with the F-16's.
In other words, you may not be able to replicate the cryptography.. but everything below the presentation layer can be replicated.
http://www.idlsoc.com/Documents/Symposiums/IDLS2006/viasat_quistorf.pdf
Infact.. I think it was YOU who first led me to the standards and references for Link-16 through PMwhen the initial work on it began! about two years ago.
So, @gambit has been a contributor to the development of the Pakistan Air Force's Datalink
Not all, but most of them. Put it this way, the most important assets are fully compatible with each other. PAF is a fully network centric warfare organization.
So in a nutshell, you are going to use the Link 16 protocols without the proprietary encryption and overlay that unencrypted feed with your own encryption headers? How would that work with an unmodified F 16 which is expecting a specific type of proprietary link 16 encryption..
Sorry if I am not putting the question right..
So as I understand, the Chinese/French jets and Pak jets are all compatible, while the F-16 is compatible with the ERIEYE, and the ERIEYE in turn acts as the branch for the F-16 for data forwarding to other assets?
No I get it.. and NO.
The idea was to basically let the proprietary system work on its own.. i.e
Erieye Link-16/ equipment- MID-LVT(F-16) as an independent link.
Erieye- other assets-GC locally developed link.
So currently... the F-16's cannot share information from the other PAF assets without an intermediary.. but the initial idea of keeping it confined to the ground stations has been changed to making all PAF AEW assets capable of linking with each other and every other asset.(Voice for some reason will be left out due to all PAF assets using a modified version of this set
R&S®M3AR Software Defined Radios (Rohde & Schwarz - Products - Secure Communications - Airborne Radiocommunications))
Before I left, the next phase was to get the local "link" to work with the F-16s..
I cannot comment on hows(my field is..or was.. secure voice.).. just that they were confident on it being done.. whether it was realistic or not is no longer mine to assess but promises have been made that cant be kept.,..on the other hand there have been semi-successful attempts to get into certain sections of US/European hardware and see what was running inside(not easy when you have machine instructions to read).
Exactly.
He would be clueless -- overall. In order for admission into a 'mission capability package' (MCP), he would have to present credible credentials, at least to read data, if not to contribute his own. The credentials are secured, as in electronic engineering with capacitors, resistors, ROM modules, and so on, and in firmware implanted, to resist access and tampering. We do not want even maintenance to see these credentials, as in plug in a tester laptop and see those ones and zeros. So even if he may be equipped with Link 16 appropriate hardware, if he does not present the appropriate credentials, he does not exist to any MCP.So in a nutshell, you are going to use the Link 16 protocols without the proprietary encryption and overlay that unencrypted feed with your own encryption headers? How would that work with an unmodified F 16 which is expecting a specific type of proprietary link 16 encryption..
Sorry if I am not putting the question right..
So kind of a hub and spoke model for having F16s talk to other assets with the AEW acting as the Hub
This is applicable to adapting foreign platforms that you own and want to incorporate into your own NCO.
So either you do the mod and live with the limited NCO and MCP capability of this old fighter, at least it is better than nothing. Or get a new -16 version.