Military Communications and Information Technology: A Trusted ...
Military Communications and Information Technology: A Trusted ... Military Communications and Information Technology: A Trusted ...
324 Military Communications and Information Technology... Server should support existing data exchange standards, therefore NFFI and Link 16 shall be supported. Following protocols have been identified as applicable for CID Server: • Link 16, • NFFI IP1, IP2, • NFFI SIP3, • VMF, • Cooperative sensors, • National standards for exchanging PLI (Position Location Information) from SA systems. A. CID server NATO standardization The lack of a system of this type has been identified in NATO, and work on the standardization has been started. Draft version of STANAG was created: “NATO STANDARD FOR SERVICES TO FORWARD FRIENDLY FORCE INFORMA- TION TO WEAPON DELIVERY ASSETS” [3][4]. This STANAG provides guidance for implementation of existing interoperability and data exchange standards, interface profiles, and both business rules and forwarding rules for collecting PLI and forwarding it to users in the appropriate systems. Currently there are no fielded CID systems capable of providing friendly PLI to the service for forwarding to weapon delivery platforms. For the foreseeable future, only FFT and SA systems are capable of providing the necessary information. The service is primarily based on conveying friendly PLI to weapon delivery platforms through Link 16, the only NATO-wide, standardized tactical data link (STANAG 5516). The service is planned to be based on an open architecture to provide connectivity of all FFT, CID, and SA technologies and as much as possible: • use existing ground and air systems and infrastructure, • require no modification of existing systems, • be expandable/adaptable to emerging PLI Sources (e.g. MMW, RBCI), • be NATO and Coalition interoperable. The work on STANAG for CID Server will last at least until the end of 2012. B. CID server usage scenarios Below some of the usage scenarios for CID Server are listed: • Air-to-surface – in this scenario CID data from ground actors is pushed into CID Server and exposed to fighter aircrafts. Aircrafts use CID information to identify targets and to support engagement decision. • Ground-to-ground – in this scenario CID data from CID Server is consumed by Weapon Delivery Assets on battlefield. CID information supports decision about weapon usage.
Chapter 3: Information Technology for Interoperability and Decision... 325 • Multinational – in this scenario CID Servers from different countries and systems can exchange information with each other and enable CID when forces from various countries cooperate on battlefield. The use cases described above are presented on the next picture. Figure 3. CID Server use cases C. CID server application in NATO operations Since the idea of CID Server has grown during Afghanistan mission, its usability in NATO operations is the main motivation for its development. Different nations have various CID capabilities, both cooperative and non-cooperative, that are specific and not based on NATO standards. This capabilities cannot be used in multinational environment. It would be very non-efficient to replace this national solutions and create new ones dedicated for NATO missions. Therefore creation of one solution – CID Server – that will mediate between different solutions from different vendors and countries, will simplify the goal of unification and cooperation of NATO forces. Such an application of CID Server might be a goal in a long term. In a short term CID Server will use already proven solutions like NFFI and Link 16. This will be still very valuable for improving CID capabilities of joint forces NATO operations. Another important capability is an ability to exchange information between different CID Servers. This can be made using already existing NATO standards and protocols (like NFFI) however STANAG document can simplify this task.
- Page 273 and 274: Chapter 3: Information Technology f
- Page 275 and 276: Chapter 3: Information Technology f
- Page 277 and 278: Chapter 3: Information Technology f
- Page 279 and 280: Chapter 3: Information Technology f
- Page 281 and 282: Information Fusion Under Network Co
- Page 283 and 284: Chapter 3: Information Technology f
- Page 285 and 286: Chapter 3: Information Technology f
- Page 287 and 288: Chapter 3: Information Technology f
- Page 289 and 290: Chapter 3: Information Technology f
- Page 291 and 292: Chapter 3: Information Technology f
- Page 293: Chapter 3: Information Technology f
- Page 296 and 297: 296 Military Communications and Inf
- Page 298 and 299: 298 Military Communications and Inf
- Page 300 and 301: 300 Military Communications and Inf
- Page 302 and 303: 302 Military Communications and Inf
- Page 305 and 306: Commanding Multi-Robot Systems with
- Page 307 and 308: Chapter 3: Information Technology f
- Page 309 and 310: Chapter 3: Information Technology f
- Page 311 and 312: Chapter 3: Information Technology f
- Page 313 and 314: Chapter 3: Information Technology f
- Page 315 and 316: Chapter 3: Information Technology f
- Page 317 and 318: Application of CID Server in Decisi
- Page 319 and 320: Chapter 3: Information Technology f
- Page 321 and 322: Chapter 3: Information Technology f
- Page 323: Chapter 3: Information Technology f
- Page 327 and 328: Chapter 3: Information Technology f
- Page 329 and 330: Chapter 3: Information Technology f
- Page 331 and 332: Managing Lessons Learnt from Daily
- Page 333 and 334: Chapter 3: Information Technology f
- Page 335 and 336: Chapter 3: Information Technology f
- Page 337 and 338: Chapter 3: Information Technology f
- Page 339 and 340: Chapter 3: Information Technology f
- Page 341 and 342: Chapter 3: Information Technology f
- Page 343: Chapter 3: Information Technology f
- Page 347 and 348: Federated Cyber Defence System - Ap
- Page 349 and 350: Chapter 4: Information Assurance &
- Page 351 and 352: Chapter 4: Information Assurance &
- Page 353 and 354: Chapter 4: Information Assurance &
- Page 355 and 356: Chapter 4: Information Assurance &
- Page 357: Chapter 4: Information Assurance &
- Page 360 and 361: 360 Military Communications and Inf
- Page 362 and 363: 362 Military Communications and Inf
- Page 364 and 365: 364 Military Communications and Inf
- Page 366 and 367: 366 Military Communications and Inf
- Page 368 and 369: 368 Military Communications and Inf
- Page 370 and 371: 370 Military Communications and Inf
- Page 372 and 373: 372 Military Communications and Inf
324 <strong>Military</strong> <strong>Communications</strong> <strong>and</strong> <strong>Information</strong> <strong>Technology</strong>...<br />
Server should support existing data exchange st<strong>and</strong>ards, therefore NFFI <strong>and</strong><br />
Link 16 shall be supported. Following protocols have been identified as applicable<br />
for CID Server:<br />
• Link 16,<br />
• NFFI IP1, IP2,<br />
• NFFI SIP3,<br />
• VMF,<br />
• Cooperative sensors,<br />
• National st<strong>and</strong>ards for exchanging PLI (Position Location <strong>Information</strong>)<br />
from SA systems.<br />
A. CID server NATO st<strong>and</strong>ardization<br />
The lack of a system of this type has been identified in NATO, <strong>and</strong> work on<br />
the st<strong>and</strong>ardization has been started. Draft version of STANAG was created: “NATO<br />
STANDARD FOR SERVICES TO FORWARD FRIENDLY FORCE INFORMA-<br />
TION TO WEAPON DELIVERY ASSETS” [3][4].<br />
This STANAG provides guidance for implementation of existing interoperability<br />
<strong>and</strong> data exchange st<strong>and</strong>ards, interface profiles, <strong>and</strong> both business rules <strong>and</strong> forwarding<br />
rules for collecting PLI <strong>and</strong> forwarding it to users in the appropriate systems.<br />
Currently there are no fielded CID systems capable of providing friendly PLI to<br />
the service for forwarding to weapon delivery platforms. For the foreseeable future, only<br />
FFT <strong>and</strong> SA systems are capable of providing the necessary information. The service<br />
is primarily based on conveying friendly PLI to weapon delivery platforms through<br />
Link 16, the only NATO-wide, st<strong>and</strong>ardized tactical data link (STANAG 5516).<br />
The service is planned to be based on an open architecture to provide connectivity<br />
of all FFT, CID, <strong>and</strong> SA technologies <strong>and</strong> as much as possible:<br />
• use existing ground <strong>and</strong> air systems <strong>and</strong> infrastructure,<br />
• require no modification of existing systems,<br />
• be exp<strong>and</strong>able/adaptable to emerging PLI Sources (e.g. MMW, RBCI),<br />
• be NATO <strong>and</strong> Coalition interoperable.<br />
The work on STANAG for CID Server will last at least until the end of 2012.<br />
B. CID server usage scenarios<br />
Below some of the usage scenarios for CID Server are listed:<br />
• Air-to-surface – in this scenario CID data from ground actors is pushed into<br />
CID Server <strong>and</strong> exposed to fighter aircrafts. Aircrafts use CID information<br />
to identify targets <strong>and</strong> to support engagement decision.<br />
• Ground-to-ground – in this scenario CID data from CID Server is consumed<br />
by Weapon Delivery Assets on battlefield. CID information supports<br />
decision about weapon usage.