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

More documents

Recommendations

Info

ARINC PROJECT PAPER 830 – Page 444.0 AGIE FUNCTIONAL SPECIFICATION“hard requirements” but as goals with “nominal flow control behavior.” Nominal flowcontrol behavior means that AGIE compliant implementations are expected tofunction in the manner defined. This allows the specification to remain simple whilemeeting user expectations and adaptable to various implementation environments.It is an implementation issue to ensure the end-to-end prioritization meets userneeds of the in service applications and their intended functions.AGIE priorities are requested by the message originator, and are set and managedby the admin with defaults and ranges. Each message requests a priority for thatmessage. The AGIE server ensures the message request is within the range set forthat message type, that client, and for that service. AGIE sets the message priorityin the header which is used to communicate to AGIE computing functions themessage priority (AGIE service layer and AMQP layer). It is also communicated tothe underlying IP network by AMQP so it can do its best to implement AGIE’sdesired prioritization.4.4.4.1 Prioritization MechanismsAGIE includes two prioritization mechanisms. The first is a basic and mandatorycapability that all AGIE compliant implantations need to incorporate. This basicAGIE priority mechanism shall provide two priority levels that are NORMAL andURGENT message priorities. The second mechanism is the USER PRIORITYmechanism, and is optional but recommended. User priority refines the normalAGIE priority range to allow broader range in flow control options. User priorities aredefined as: very high, high, medium, low, and background and is captured in anoptional field in the AGIE message header. AGIE prioritization affects theAGIE/AMQP function processing, queuing as well as IP network processing (via IPTOS/Diffserv).4.4.4.2 AGIE Priority ExpectationsAGIE defines the following general behavior as the basis for specificationdevelopment and functional definition. An AGIE compliant implementation shallexhibit the following:1. Functions execute as if they are multi-threaded non-blocking (client andserver functions) manner2. Functions execute as if they are multi-threaded non-blocking manner at theclient interface to the application3. Queuing executes as if there are separate queues for each IO client/session4. Queuing executes as if there are separate queues for each connection/port5. Prevents queue starving for client IO from large files6. Prevents queue starving on connections from large files7. High priority coordination tasks are handled before payload and not waitingin back of queue8. no (major) priority inversions occur from priority stack (below)9. Large urgent messages are used sparingly, if at all10. Priorities are used with a fair weighted scheduling function that does notstarve other functions/queues if/when mishandledAGIE priority nominal behavior shall be implemented with some form of fairweighted queuing for basic AGIE priorities is defined below with highest priority firstand lowest priority last.1. Urgent coordination have highest system priority
4.0 AGIE FUNCTIONAL SPECIFICATIONARINC PROJECT PAPER 830 – Page 452. Urgent user small messages3. Urgent user large messages4. Normal coordination or user small messages5. Normal coordination or user large messagesAGIE priority nominal behavior for AGIE user priorities, when used with basic AGIEpriorities, shall be as defined below with highest priority first and lowest priority last.1. Urgent coordination have highest system priority2. Urgent user small messages3. Urgent user large messages4. Normal – Very high5. Normal – High6. Normal – Medium7. Normal – Low8. Normal - Background4.4.4.3 Priorities in FunctionsAGIE computing functions affect prioritization at the AGIE service and AMQP layers.AGIE server computing processing affects and manages prioritization in three ways.1. Best path selection considers priority setting and influences QoS2. AGIE and AMQP orders queues based on priority settings3. AGIE and AMQP feeds/meters data from queues to network based onpriority settingBest path selection is determined by priority setting and mapping table managed byoperator admin. Path selection is a key element of prioritization. Path selectiondetermines the datalink and type of service. Path selection is implemented byAMQP mapping to default or source-destination routing on the IP network betweenAGIE servers/AMQP brokers. Paths are defined by their connection profile name.AGIE sets the priority for messages, which may be treated anywhere from near realtimeto background message priorities. The priority settings determine how AMQPqueues and transmits the messages relative to other messages. Segmentedmessages are queued multiple times for each individual segment.4.4.4.4 Background PriorityAGIE supports the concept of background messaging using a “background priority”.Background priority allows the operator to minimize cost and QoS impacts ofsending less important (time criticality) messages, especially large ones, by longtermscheduling. The actual mapping of background priority features is left tooperator admin, but it includes the ability to hold a message until specified time orcondition exists. Examples would be only allowing transmission over grounddatalinks, metering traffic during phase of flight, or sending over a lower class ofservice. Again, the special feature of background priority is the ability to hold offinitial message sending from the origination host or home server.4.4.4.5 Priorities with NetworkThis standard is developed to support priority managed networks and datalinks.However, AGIE does not require them for operation. AGIE does not have control
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 33 and 34: 4.0 AGIE FUNCTIONAL SPECIFICATIONAR
Page 47: 4.0 AGIE FUNCTIONAL SPECIFICATIONAR
Page 81 and 82: 6.0 AGIE PROTOCOL INTERFACESARINC P
Page 87 and 88: ARINC PROJECT PAPER 830 - Page 83AP
Page 99 and 100:
ARINC PROJECT PAPER 830 - Page 95AP
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?