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

4.0 AGIE FUNCTIONAL SPECIFICATIONARINC PROJECT PAPER 830 – Page 294.2 ArchitectureThe AGIE based communication system is composed of a network of AGIE Clientinstantiations through which end-system (software) applications interface with thesystem and a network of AGIE server instantiations that manage the actualinformation exchange across the system. The functions of an AGIE client aredescribed below. The functions of AGIE servers are considerably more complex andare described in Section 4.6. Architecture describes AGIE nodes, both clients andservers, and their relationships defined by node definitions and end-to-end topologyconsiderations.COMMENTARYMessage implies “message push” or “message notifications.”COMMENTARYThe terms AGIE protocols and AGIE interfaces are used throughout thisdocument. AGIE protocols refer functional interfaces between AGIEcomponents. These are primarily related to AMQP. AGIE interfaces are peerlevel inter-function communications using AGIE messages which areconsumed by AGIE functions. AGIE interface semantics are defined inSection 6. AGIE interface syntax is defined in Appendix D.4.2.1 AGIE ClientsThe AGIE client is an AGIE node that interacts between an end user application andan AGIE host server. The client provides AGIE services to the applications. Itinterfaces between applications and its host.COMMENTARYThe term “application” as used throughout the document usually means anexternal software based AGIE user. However, most often is can also be readas “AGIE function” or “function”, as AGIE infrastructure functions behave likeuser applications in regards to AGIE messaging. They however, oftenprovide their inputs directly in well formed and compressed formats and havespecial security handling provisionsThe client-application interfaces are defined as XML documents over an undefinedphysical interface via AMQP client layer. Physically, clients and applications maycommunicate via any method, such as inter-process communication (i.e., sockets),by function calls within software programs, or over LAN or IP networks. This is left toimplementation.AGIE defines a service layer application-client interface. This interface operates viaservice request on message originator side and via message notification/push onthe receiver side and may use application-to-application addressing via applicationIDs.Clients perform fragmentation and re-assembly of large data. A size limit for datatransfer is defined within a particular AGIE system implementation. Should a datafile be larger than this size, then the client fragments the file into smaller messages.This ensures the AMQP data transfers and internal memory constraints are notoverloaded. The destination client re-assembles the message fragments into a finalmessage for delivery. This requires care in implementation to minimize data lossand efficiency, where either the client has persistent storage or is highly available.