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

More documents

Recommendations

Info

ARINC PROJECT PAPER 830 – Page 243.0 AGIE OVERVIEWoriginates. The delivery of data takes either of two forms depending on the messagetype, class and message service used.1. The server notifies the client of the data and the client subsequently requeststhe data to be “pulled” to the client.2. The server can also “push” the data directly to a client when a connection isestablished without prior explicit notification.AGIE defines the capability to send data to multiple destinations via direct naming orvia publish-subscribe methods. The exchange of data via AGIE is completelysymmetrical, i.e., the same services apply for aircraft to ground as wells as forground to aircraft messaging.3.6.6 PrioritizationAGIE provides for prioritization and preemption to facilitate needed performance,cost management, and manage link usage. Prioritization is an important construct insupporting cross-domain services. Prioritization includes messaging, datalink,queuing, and processing. The admin sets AGIE priorities.AGIE prioritizes messages based on message type, client attributes, and messageservice used. A sender requests the message’s priority. The admin pre-determinesprioritization policies. AGIE accepts the sender’s request and maps it to the adminset policies.Prioritization affects AGIE processing and underlying network IP services.Prioritization supports a range of options from background to immediate messaging.One aspect of prioritization is preemption, which is AGIE’s ability to re-orderprocessing based on a later arriving higher priority message or task.Within AGIE, two levels of fixed data priority are defined, “NORMAL” and“URGENT.” The vast majority of traffic is expected to be managed as NORMALtraffic. As a rule, all data are strictly queued and acted on a First-In First-Out (FIFO)basis irrespective of their origin and/or destinations. Priorities are applied to serverfunctions, processing queues and communication paths/ports. With respect tonormal vs. urgent messages, the following general rules apply: Urgent messages take precedence over normal messages Newly appearing urgent messages generally are placed ahead of the queue Urgent messages are queued in FIFO order with respect to each other Small urgent messages can suspend the processing of normal messages Some level of fair-weighted queuing also existsThe AGIE standard does not stipulate prioritization implementation details, such ashow many queues a particular server needs to maintain. It does provideprioritization expectations and guidance, explained in Section 4.4. Also, eachmessage service has a default priority associated with it. The default may beoverridden by message request and/or admin control. “NORMAL” is the defaultpriority attribute value for all transactions. A “user priority” is defined in the messagefield and allows the implementation to provide more fidelity in handling priorities insophisticated implementations. Also, AGIE provides a priority mapping interface tothe underlying IP network.3.6.7 Application Message ManagementAGIE applications use built-in services to manage messages that are in-transit to afinal destination. The AGIE data delivery framework includes methods of managing
ARINC PROJECT PAPER 830 – Page 253.0 AGIE OVERVIEWdata flow that includes status tracking and enquiry, automated reporting, logging,delivery time management, and message deletion.AGIE provides applications and administrators with the ability to determine whatlevel of message delivery status and reporting is required on a per message basis.This can be defined for each message instance, for each message type and/or foreach service invoked. Reporting may be automated or by a later request. AGIEensures the reports and status are delivered to the originating client, whether or notit has changed hosts or is off-line when report is generated.AGIE provides built-in automated and on-demand logging features. There areaviation requirements relative to the logging of data sent to the aircraft. Loggingfunctionality is defined to facilitate efficient logging and to allow tailoring tooperational needs. Log function is required as it supports highly important functions,such as capturing security events.AGIE tracks the status of a message from origination until successful delivery, nondelivery,or timeout. A sending client can enquire about the status of a message atany time while the message is in transit via the defined message service interface.AGIE ensures transaction history is maintained. The retention period is based onregulatory and/or operational considerations and is not defined by AGIE. It is a goalfor onboard transactions and event logging to be minimized, and where possible,handled on the ground. Also, when possible, aircraft logged events areautomatically transferred to ground for permanent logging.3.7 List of OperationsThe AGIE concept of operations defines users and operations for each user. Thissection lists user operations specific to the type of user.3.7.1 Application OperationsThe following operations are initiated by end user applications via the AGIE clientinterface.1. Send message using message service (considered to be a complexoperation)2. Pull messages from AGIE server3. Manage (control/status) in transit message4. Request AGIE node/network status (ping)5. Log event6. Manage publication subscription3.7.2 Client OperationsThe following operations are initiated by AGIE client on behalf of the applications orAGIE system via client-host interface.1. Associate with AGIE host server2. Un-associate with host server3. Log event3.7.3 AGIE Server OperationsThe following operations are initiated by AGIE server via server-host and serverserverinterfaces.
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 27: ARINC PROJECT PAPER 830 - Page 233.
Page 33 and 34: 4.0 AGIE FUNCTIONAL SPECIFICATIONAR
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?