Table of Contents
1.0INTRODUCTION
1.1PurposeofThisDocument
1.2SummaryDescriptionofGenericInterface
1.3DocumentOrganization
1.4RelationshiptoOtherDocuments
1.5ReferencedDocuments
2.0OVERVIEW
2.1Introduction
3.0PROTOCOLDESCRIPTIONS
3.1Overview
3.2PhysicalLayer
3.3DataLinkLayer
3.3.1DataLinkLayerProtocolsoverHighSpeedBus
3.3.1.1ARINC429Version3WilliamsburgProtocol
3.3.1.2ARINCSpecification646EthernetProtocol
3.3.2PrimitivesBetweenDataLinkLayerandIETFIP
3.3.2.1MA_DATA.request
(source_address,destinationaddress,data
service_class)
3.3.2.2MA_DATA.indication
(source_address,destination_address,data,
reception_status,service_class)
3.3.2.3MA_CONTROL.request
(Command_type,destination_address,PAUSEopcode,
Request_operand)
3.3.2.4MA_CONTROL.indication
(Command_type,destination_address,PAUSEopcode,
Request_operand)
3.4NetworkLayer
3.5TransportLayer
3.6NetworkManagementInterface
3.7PerformanceCriteria
3.7.1SystemIntegrity
3.7.2Timing/TransactionDelay
3.8SupportforMaintenanceFunctions
4.0SIMPLENETWORKMANAGEMENTPROTOCOL(SNMP)
4.1ProtocolOverview
4.2MIBDescription
4.3ASN.1Encoding
4.4ProtocolDefinition
4.5SNMPv1MessageFormatDefinitions
4.5.1SNMPMessage
4.5.2SNMPProtocolDataUnits
4.5.3CommonPart
4.5.4GetRequest-PDU
4.5.5GetNextRequest-PDU
4.5.6GetResponse-PDU
4.5.7SetRequest-PDU
4.5.8Trap-PDU
4.6MIBDefinitions
4.6.1ApplicationConfigurationMIB
4.6.1.1DefinitionoftheApplicationConfigurationTable
4.6.2SpecificTrapDefinition
4.7EnterpriseMIBNamingProcedures
5.0CMU/FMCINFORMATIONBROKER(CFIB)
5.1Overview
5.2CFIBServiceDefinition
5.2.1ImmediateOperations
5.2.2ContractOperations
5.2.2.1DefinitionoftheApplicationConfigurationTable
5.3FMC/CMUMIBDefinition
5.3.1ApplicationConfigurationTable
5.3.2FullFormatOperationTable
5.3.2.1EntryIndex
5.3.2.2ContractID
5.3.2.3SourceID
5.3.2.4Actions
5.3.2.5Triggers
5.3.2.5.1TimeRelatedEvents
5.3.2.5.2FMCRelatedEvents
5.3.2.5.3CMURelatedEvents
5.3.2.6CFIBTable
5.3.3PartialModeOperationTable
5.3.4FMGroupandCMUGroupCFIBVariablesTable
5.4CMU-FMSInformationBroker(CFIB)Procedures
5.4.1CFIBOverview
5.4.2Initialization
5.4.3InformationTransfer
5.4.3.1ContractRequestMessages
5.4.3.2DataRetrieval
5.4.3.3PeriodicDataTransmit
5.4.3.4EventRequests
5.4.3.5ValidateRequests
5.4.3.6LoadRequests
5.4.3.7CancelRequests
5.4.4ErrorProcedures
5.4.5Termination
6.0PROTOCOLCONFIGURATIONS
6.1Overview
6.2FMCasEndSystem
6.2.1Overview
6.2.2ACARSEnvironment
6.2.2.1PhysicalLayer
6.2.2.2DataLinkLayer
6.2.2.3NetworkLayer
6.2.2.4TransportLayer
6.2.2.5ApplicationLayer
6.2.3ATNEnvironment
6.2.3.1PhysicalLayer
6.2.3.2DataLinkLayer
6.2.3.3NetworkLayer
6.2.3.3.1Addressing
6.2.3.4TransportLayer
6.2.3.5SessionLayer
6.2.3.6PresentationLayer
6.2.3.7ApplicationLayer
6.3CMUasSingleEndSystem
6.3.1Overview
6.3.2ACARSorATNEnvironment
6.3.2.1PhysicalLayer
6.3.2.2DataLinkLayer
6.3.2.3NetworkLayer
6.3.2.4TransportLayer
6.3.2.5ApplicationLayer
6.4Remote-Stack
6.4.1Overview
6.4.2ACARSorATNEnvironment
6.4.2.1PhysicalLayer
6.4.2.2DataLinkLayer
6.4.2.3NetworkLayer
6.4.2.4TransportLayer
6.4.2.5ApplicationLayer
6.5IntegratedArchitecture
6.5.1Overview
6.5.2ACARSEnvironment
6.5.2.1NetworkLayer
6.5.2.2TransportLayer
6.5.2.3ApplicationLayer
6.5.3ATNEnvironment
6.5.3.1NetworkLayer
6.5.3.2TransportLayer
6.5.3.3SessionLayer
6.5.3.4PresentationLayer
6.5.3.5ApplicationLayer
6.6Conformance
7.0DUALEQUIPMENTCONFIGURATIONS
7.1Overview
7.2DualSystemConfigurations
7.2.1DualProceduresforCMUasSingleEndSystem
7.2.1.1DualFMCswithSingleCMU
7.2.1.2DualFMCswithDualCMU
7.2.2DualProceduresforRemote-Stack
7.2.2.1DualFMCswithSingleCMU
7.2.2.2DualFMCswithDualCMUs
7.2.3DualProceduresforFMCasEndSystem
7.2.3.1DualFMCswithSingleCMU
7.2.3.2DualFMCswithDualCMUs
ATTACHMENTS
1EXAMPLEINTERFACEDIAGRAMS
2PROTOCOLCONFIGURATIONDIAGRAMS
3CAPABILITYMATRIX
4CFIBPROTOCOLDIAGRAMSANDEXAMPLEMESSAGES
5EXAMPLESOFCMU/FMCINFORMATIONBROKERMESSAGES
6SIMPLENETWORKMANAGEMENTPROTOCOL(SNMP)
7FMC/CMUMIBDEFINITION
8ASN.1ENCODING
9CFIBVARIABLELISTDEFINITION
APPENDICES
AREFERENCEDOCUMENTS
BACRONYMSANDTERMS
CFMC/CMUUSERSGUIDE
DSYSTEMDESIGNER'SCHECKLIST
EATUTORIALONTHEAVIONICSINTERFACEDEFINITIONFORFLIGHT
MANAGEMENTANDCOMMUNICATIONSMANAGEMENTFUNCTIONS
FRECOMMENDEDMINIMUMCFIBCAPABILITIES Abstract
Defines the specification of generic interface used between avionics computing equipment that exchange binary message-oriented data. The interface could be used between a Communication Management Computer (CMU) Mark 2 and Flight Management Computer (FMC) or between any two avionics Line Replaceable Units (LRU). Within this standard, the term FMC may be applied to any type of navigational unit.
