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

More documents

Recommendations

Info

ARINC PROJECT PAPER 830 – Page 203.0 AGIE OVERVIEWok, and a very low priority and cost basis. This type of delivery does not supportautomated message acknowledgement, but allows the sender to obtain a list ofsuccessful deliveries upon request.3.5.5 Publish-Subscribe Message ServiceThis AGIE data exchange service addresses the capability for an application topublish data under a topic name that is intended to be delivered to applicationssubscribing to the topic. The originator sends the message to the Publish-Subscribeservice with the specified message topic. The server in turn notifies subscribingapplications that a new message has been “published” to that topic.The originators of messages being distributed on a Publish-Subscribe basis aretypically ground-based applications and the recipients may be any combination ofaircraft or ground based applications. Publish-Subscribe messages are addressedto the ground based (on logically a function on Primary) Publish-Subscribe function(client).Messages may be sent at any time and with near-real time message delivery notexpected. There is no specific acknowledgement of message delivery forpublish/subscribe type message distribution. The originator may obtain a list ofsuccessful deliveries upon request.3.6 AGIE Principles of OperationThis standard defines protocols and functionality for exchange of data between endsystems/applications. End system software applications implement AGIE clientinterfaces. Clients associate with AGIE servers or hosts. Typically, Aircraft based(onboard) clients associate themselves with an aircraft resident server while nonaircraftbased clients associate with ground-based. Onboard clients are notprecluded from associating with ground-based servers. However, ground-basedclients cannot associate with an onboard server at any time. Onboard serversassociate with ground servers by connecting over active communication links whichcome and go over time. Association is based on establishing a connection or newlyjoining client.COMMENTARYAssociation does not constitute network level authentication, only functionalconnection establishment.“Fixed” clients can only associate with a designated server and only associateoccasionally, e.g., in the event of an aircraft power up sequence. An example is anairborne data loader, which is permanently installed in the aircraft that also hosts anonboard AGIE server. “Mobile” clients on the other hand are not permanentlyassigned to the same server, e.g., an EFB which is removed from the cockpit afterflight and later re-associates on a different aircraft, on the ground from flightoperations, or a hotel room via a ground-based server.3.6.1 AGIE Organization OverviewAGIE defines a message brokering system where dedicated AGIE servers managethe data exchanges and end system applications associate, as AGIE clients, with anAGIE “host” server for the purpose of submitting and receiving data from other AGIEclients and end system applications.AGIE nodes communicate with each other via AGIE addressing mechanisms. Theseare defined in Section 4.5. To allow flexible addressing of AGIE nodes, especiallyAGIE clients, an AGIE system is a closed system, where “closed” is defined as:
ARINC PROJECT PAPER 830 – Page 213.0 AGIE OVERVIEW1. The set of all clients and servers is known at all times to the Primary Serverand admin.2. The network topology between all AGIE servers is static, i.e., all nodes arepre-defined, fixed connectivity is known, and the limits on dynamicassociations and connections are bounded.COMMENTARYThe term “Primary” or “Primary Server” is a logical definition which may beimplemented as a single physical server or multiple federated servers.In this closed system the relationship between all servers is static in the sense thatall servers are known, all fixed connections are known, and dynamic connectionsare bounded. Association of clients to hosts is dynamic, such that any client canassociate or un-associate with any server (as bounded by system administration) atany time. To assure full addressing capability is maintained, hosts make all newassociations visible to the AGIE Name Service (ANS) and thus to all other nodes inthe system as described in Section 4.5.All clients are uniquely identifiable within the system. In the event more than oneinstantiation of a Client ID attempts to associate with a server, they are providedwith unique identifications or denied association. Typical examples are EFBs orcredit card authorization devices. See Section 4.5.It is necessary to amend the static system configuration from time to time. Suchchanges require a managed effort controlled by authorized system administrators.They are globally visible across the system. AGIE defines configuration controlmethods and messages for this purpose in Section 6.0.Part of the AGIE definition includes limitations of which clients other clients areallowed to see. This is accomplished by administrators setting a “visible client list”for each client and setting client visibility policies.AGIE provides for managing global system configuration and distributing thisinformation to all system nodes. For simplicity, the AGIE standard assumes thisinformation is centrally managed on the ground-based Primary knowledge store(Primary), which also hosts the root level AGIE Name Server.AGIE nodes may inquire about the status of other nodes. AGIE servers may alsorequest the status of AGIE databases from Primary server at any time. Whereredundant, distributed ANS is used, they are kept synchronized. In the case wheremore than one server exists on an aircraft, one of these servers is defined as thelocal primary. All AGIE servers know how to reach an ANS and other Primaryfunctions. ANS provides the translation of AGIE node identifiers to addresses andprovides path quality information.3.6.2 Connection ManagementAGIE is an application level (Layer 7) service. All AGIE connections are logicalconnections and not physical communication links and for that reason one AGIEentity is said to be “associated” with another AGIE entity on an application level.Within AGIE two types of connections exist. First are connections between clientsand servers; second are connections between two AGIE servers. The initiation ofconnection establishment is subject to the following rules/conventions which arestrictly adhered to:
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 23: ARINC PROJECT PAPER 830 - Page 193.
Page 33 and 34: 4.0 AGIE FUNCTIONAL SPECIFICATIONAR
Page 75 and 76:
ARINC PROJECT PAPER 830 - Page 715.
Page 77 and 78:
Page 79 and 80:
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?