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

More documents

Recommendations

Info

ARINC PROJECT PAPER 830 – Page 102.0 AGIE PURPOSE AND OBJECTIVESAGIE users initiate and/or terminate operations. From a systems perspective the setof AGIE users is small and each user specific sets of operations are defined: The primary AGIE user is an end system application AGIE automated client and server functions initiate operations Network Management Function (NMF) initiates operations externally to AGIE AGIE Administration or “admin” is an important external user and is a superuserapplicationEach operation is invoked as a processing “thread” by an AGIE user. These threads(described further in Section 3.7.6 and are not to be confused with executingthreads within a computer’s operating system) describe process flow and provideinsight into required functionality and component interfaces. Threads are intended todescribe general information about and control flow between components and majorfunctions and are not intended to provide rigorous data flows or sequence diagrams.Moreover, only major success paths and occasionally common failures aredepicted. In summary, they provide a bridge between functionality, described inSection 4.0, and operations, described in Section 5.0.The list of operations provides a summary of operations each AGIE user/componentcan initiate. Each operation in this list is captured in the detailed operational threadslist. The threads are organized by user (without repeats) and provide a mapping todetailed functional flows. The list of AGIE operations is found in Section 3.7 withdetailed operational threads being provided in APPENDIX B “AGIE OperationalThreads” APPENDIX C “AMQP Thread Mapping and diagrams”.A key element of validating specification requirements and ensuring definedcapabilities meet user needs are use cases. Use cases define proper end-to-endfunctionality, performance expectations, and allow modeling of data flows. Theyprovide concrete examples of anticipated AGIE usage in the real-world. Primary usecases involve user applications, such as electronic software delivery, IFE contentdelivery, and FOQA data download. These are supplemented by infrastructure usecases that facilitate AGIE system operation and management.A list of use cases has been selected to provide an overview of the operationalintent and capabilities of AGIE in use. The detailed use cases provide a mapping ofuse cases with objectives to threads for functional completeness and accuracy.2.3.3 AGIE Development and TestingAGIE is intended to permit implementation via independently developedcomponents and integrated into working implementations by adapting them to thespecific operator implementation. A related prime AGIE goal is to minimize rework ofre-integration of components while maximizing re-use and interoperability. Thisrequires the use of integration, testing, and demonstration environments.Two problem categories result from the complex aviation development andoperational environments.1. Validating end-to-end functionality and performance of message deliveryover realistic onboard and ground architectures.2. Validating interoperability between independently developed messaginginfrastructure components (server end) and independently developedapplications (client end).
2.0 AGIE PURPOSE AND OBJECTIVESARINC PROJECT PAPER 830 – Page 11To facilitate common demonstration and testing respective scenarios and topologiesare found in AGIE Demonstration and Testing paper, see Section 1.4 for reference.2.3.4 InteroperabilityInteroperability is one of AGIE’s primary goals. In order to realize this goal, an AGIEobjective is to allow elements of AGIE implementations developed by independentdevelopers to operate seamlessly in a single AGIE system. Another objective is tofacilitate seamless adaptation and re-use across system implementations.AGIE defines four primary areas of interoperability:1. Interoperability between independently developed AGIE Clients and AGIEServers2. Interoperability between independently developed AGIE Servers and AGIEServers3. Interoperable configuration and management from an administrative point ofview4. Re-usability of components, functions, and subsystems across independentimplementations2.4 Policy and Quality of Service Considerations2.4.1 Priority, Cost and PerformanceAGIE provides features that support operationally defined policies regardingprioritization and QoS management. Further, AGIE provides policy based pathselection using profiles of air-to-ground connections. AGIE allows the operator to setpolicies to manage cost, performance, and datalink usage.2.4.2 Certification and ApprovalOperators need to work with regulators to obtain certification and/or operationalapproval. There are built-in features, many of which offer a range of options,designed to allow tailoring AGIE to meet certification and approval needs. Thesefeatures are controlled by operator policies and include: prioritization, partitioning,visibility limits, network topologies, security features, association mechanisms, andmessage type definitions. The Considerations for AGIE Certification and Approvalpaper (See Section 1.4 for reference) provides more detailed discussion.AGIE is defined to allow operators to modify elements of AGIE without affectingcertification or approval basis for minor changes and updates to configuration andsecurity parameters. For example, the operators may add new clients-applicationassociations without affecting system’s operational approval. AGIE specifies thatserver associations are always initiated by the onboard equipment, never by theground. Moreover, Operators are strongly encouraged to utilize AGIE security andpartitioning features.2.5 Security AspectsSome of the key policies managed by the operator with regard to AGIE are itsinformation security policies. This section addresses the approach taken for thesecurity related aspects of AGIE.2.5.1 Security GoalsAGIE’s goal is to perform secure and reliable communications for applications inmultiple aviation domains communicating over shared data links and networks.
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 11 and 12: 2.0 AGIE PURPOSE AND OBJECTIVESARIN
Page 13: 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 65 and 66:
4.0 AGIE FUNCTIONAL SPECIFICATIONAR
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
ARINC PROJECT PAPER 830 - Page 675.
Page 73 and 74:
Page 75 and 76:
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?