Mission Operations Reference Model. Draft ... - CCSDS

More documents

Recommendations

Info

DRAFT RECOMMENDED PRACTICE FOR MISSION OPERATIONS REFERENCE MODELThe layering of the message transport, MAL, MO Services and the service provider andconsumer is shown in figure 2-2 (each layer builds upon the layers below).Service ConsumerServiceConfigurationConfiguration interrogationService invocationService responseHistory populationHistory observationServiceHistoryService ProviderMission Operations Services LayerMessaging Abstraction LayerMessaging TechnologyFigure 2-2: Service Stack ViewNOTE – A benefit of implementing multiple services over a message abstraction layer isthat it is easier to bind them to different underlying technologies and protocolencodings. All that is required is an ‘adapter’ layer between the MAL and theunderlying protocol to enable all services over that technology. This can be eitheran implementation of the MAL that is bound to a specific technology or animplementation that supports multiple technologies. Hence the same service canbe implemented over ground-based network technologies and middleware, or itcould even be carried across the space link itself.The services, in the form of standard language-specific APIs, themselves providethe ‘plug-and-play’ interface for applications, allowing them to be integrated anddeployed wherever is appropriate for the mission.CCSDS 520.1-R-1 Page 2-4 October 2009
DRAFT RECOMMENDED PRACTICE FOR MISSION OPERATIONS REFERENCE MODEL2.5 MISSION OPERATIONS FRAMEWORKThe service specifications and the MAL are abstract in their definition; they do not containany specific information on how to represent them for a particular implementation languageor transport encoding.However, the service specifications are supplemented by a set of standard MO specificationsfor representing the MAL in specific implementation languages and also for mapping theMAL to a specific message encoding and transport:ApplicationLayerConsumer/ProviderMO ServicesLayerMission Operations Services LayerCOM, Common, Core, Automation, Scheduling, Time, …Mapping toimplementationlanguageAbstract servicespecificationdefined in termsof the MALMessageAbstractionLayerMessaging Abstraction Layer (MAL)Generic Interaction Patterns, Access Control, Quality of ServiceAbstractmessaginginfrastructureTransportLayerMessaging TechnologyMapping of theMAL to encodingand transportFigure 2-3: Service LayeringNOTE – Only the MAL specification needs to be mapped to a specific implementationlanguage. The service specifications are defined in terms of the MAL andtherefore the same language mapping applies to these services unmodified.Of the Recommended Standards produced for the MO framework specification, each bookfalls into one of the following four categories:a) Language MappingOne book exists for each mapping from the MAL to the specific implementationlanguage.b) MAL SpecificationOnly one book exists defining the MAL.CCSDS 520.1-R-1 Page 2-5 October 2009
Page 2: Institutional Commercial Real Estat
Page 6 and 7: DRAFT RECOMMENDED PRACTICE FOR MISS

Mission Operations Reference Model. Draft ... - CCSDS

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

Delete template?

Save as template?