(AGIE) Using Internet Protocols - Aviation Committees - AEEC - AMC

More documents

Recommendations

Info

ARINC PROJECT PAPER 830 – Page 223.0 AGIE OVERVIEW1. A client always initiates an association with a server (client-serverassociation).2. An onboard server always initiates an association with a ground-basedserver. A ground-based server cannot initiate an association with an aircraftbased server (server-server association).3. Ground server-server associations are static within AGIE (setting up,establishing, modifying ground connectivity is not within AGIE scope).4. Connection establishment between two onboard servers requires the non-Primary servers to initiate the association.5. A ground-based client only associates with a ground-based server (never anaircraft based server).Association indicates to each party that the ability to exchange information has beenestablished. The actual physical link exists outside the AGIE framework at a lowerlayer and is managed by the underlying components employed for actual transportof AGIE messages. This is described further in Section 4.3.The “association” process involves the exchange of specific coordination messagesbetween two AGIE nodes. Within AGIE association and the exchange of suchmessages is the only mechanism through which AGIE entities are allowed toconnect to the AGIE system. Association includes updating the ANS andpropagating the new client status and access information throughout the AGIEsystem.AGIE interfaces to network management functions that provide notification andstatus of connectivity changes and other connectivity information used by a specificimplementation.The creation of an AGIE connection, and subsequent association, is automatic anddoes not involve any human action. It is externally triggered by networkmanagement. However, in the event a connection is interrupted, the party whichnormally initiates the connection may re-initiate the connection. AGIE does notrequire explicit un-association, though this is provided to allow efficient resourcemanagement.3.6.3 Protocol BindingAlthough AGIE is a Layer 7 protocol, the standard stipulates the use the AdvancedMessage Queuing Protocol (AMQP) through which binding of the application’s XMLmessage documents to a data transport protocol is achieved for both client-serverand server-server communication. Details of protocol binding are found in Section6.0 for AGIE client-to-AMQP client and AGIE server-to-AMQP broker bindings andinterfaces. Functional mapping to AMQP is found in Section 4.6.3.6.4 AGIE AddressingOne of the main AGIE challenges is accommodating the need to dynamicallydetermine how AGIE clients can be reached at any given time. Aircraft with onboardAGIE servers move around the network and mobile devices come and go as well asmove around the network. Fixed aircraft equipment is regularly removed from oneaircraft and installed on a different aircraft. An example of this is an Electronic FlightBag (EFB) that is ported from aircraft to ground networks, e.g., hotels, and again toanother aircraft.The AGIE standard addresses this need by allowing applications to address otherapplications by client name and application ID without knowing the actual physical
ARINC PROJECT PAPER 830 – Page 233.0 AGIE OVERVIEWor IP address of the destination, see Section 4.5. AGIE centrally maintainsdatabases containing the following information for the entire AGIE system:1. List of all defined AGIE clients2. List of all defined AGIE servers3. List of current associations between clients and servers4. List of current connections (paths) between servers.To assure that all AGIE nodes have access to this data, AGIE uses a ground basedsystem to host Primary functions including AGIE name services and hosting allcoordination databases.Every client has a ground-based “Home” server. All air-ground and ground-groundexchanges are routed through the client’s home to the final destination. While thisindirection adds latency, it reduces complexity and overhead and there is still only asingle air-ground exchange.It is, however, not efficient for client-to-client data exchange within the same aircraftto require routing messages through the Home server. Therefore, an onboard AGIEserver acts as a “local Primary” server and supports direct onboard routing. It alsoacts as a local “Temporary Client Home” server when there is no access to theground-based client’s Home, providing store-and-forward capabilities todisconnected AGIE sub-networks. AGIE naming and addressing is further defined inSection 4.5.3.6.5 AGIE Data Delivery ManagementAGIE implements “store and forward” and “direct delivery” methods. All end-systemmessages are sent strictly from one client to another client with no exception.Internally, AGIE sends data to specific servers or functions, but clients are not setup or even allowed to do this. To initiate a transfer of data to a destination client, theoriginator client sends an XML document as a message to its host using a messageservice interface. The host processes the message and forwards it to the destination(or home). It may be necessary to locally store the information along the way until itreaches the destination, see Section 4.6.AGIE defines two end message servers. An “Origination server” receives themessage from its client. A “Destination server” delivers the message to thedestination client. While actual data paths may consist of multiple physical “hops,”only the origination and the destination servers are of relevance to the end clientsfor an AGIE data transfer. Both servers may be the same AGIE server.Data transfer between those two servers is managed via standard IP protocol usingAMQP in conjunction with any other aircraft/ground link IP routing service (e.g.,MAGIC).AGIE defines two principal classes of messages.User messages used to transfer end-system application related databetween AGIE clients.Coordination messages used to communicate any internal systemmanagement related information such as notifications, status enquires,connection coordination etc.Each message includes a unique identifier which is a combination of the senderidentifier plus an integer number, unique to the server, from which the message
Page 2 and 3: ARINC PROJECT PAPER 830TABLE OF CON
Page 5 and 6: ARINC PROJECT PAPER 830 - Page 11.0
Page 7 and 8: ARINC PROJECT PAPER 830 - Page 31.0
Page 9 and 10: 2.0 AGIE PURPOSE AND OBJECTIVESARIN
Page 17 and 18: 2.0 AGIE PURPOSE AND OBJECTIVESAGIE
Page 19 and 20: ARINC PROJECT PAPER 830 - Page 153.
Page 25: ARINC PROJECT PAPER 830 - Page 213.
Page 33 and 34: 4.0 AGIE FUNCTIONAL SPECIFICATIONAR
Page 77 and 78:
ARINC PROJECT PAPER 830 - Page 735.
Page 79 and 80:
ARINC PROJECT PAPER 830 - Page 755.
Page 81 and 82:
6.0 AGIE PROTOCOL INTERFACESARINC P
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
ARINC PROJECT PAPER 830 - Page 83AP
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
APPENDIX BAGIE OPERATIONAL THREADSA
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
APPENDIX CAPPENDIX CAMQP THREAD MAP
show all

(AGIE) Using Internet Protocols - Aviation Committees - AEEC - AMC

Create successful ePaper yourself

Delete template?

Save as template?