Mission Operations Reference Model. Draft ... - CCSDS

DRAFT RECOMMENDED PRACTICE FOR MISSION OPERATIONS REFERENCE MODEL2 MISSION OPERATIONS SERVICE CONCEPT2.1 OVERVIEWA service is an operation, or set of operations, that is well defined, self-contained, and doesnot depend on the state or context of another service.The services given in reference [B1] are based on a generic service pattern. This patterncovers not only the primary service interface but also includes the configuration data andhistory associated with the service. This is illustrated in figure 2-1.Service ConsumerServiceConfigurationConfiguration interrogationService invocationService responseHistory population History observationServiceHistoryService ProviderThe pattern comprises four main components:Figure 2-1: Generic Service Model– The service provider is responsible for supporting the service functions.– The service consumer is a user of the service functions, and is typically either aHuman-Computer Interface, or another software application.– The Service Configuration specifies the entities that exist for a specific instance ofthe service. This specification must be available to both service provider and serviceconsumer if they are to communicate effectively; however, for simple services it maybe implicit for one component if the configuration is hard-coded into it.– The Service History maintains persistent storage of service history, such that aservice consumer can retrieve historical information for the service.NOTE – The service specification does not define the actual implementation of any ofthese four collaborating components; it confines itself to definition of the highlevelservice layer that binds them together. This is represented in figure 2-1 bythe shaded area and the arrows within it.CCSDS 520.1-R-1 Page 2-1 October 2009