CCSDS MO Services

Last updated

The Spacecraft Monitoring & Control (SM&C) Working Group of the Consultative Committee for Space Data Systems (CCSDS), which sees the active participation of 10 space agencies and of the Space Domain Task Force of the Object Management Group (OMG), is defining a service oriented architecture consisting of a set of standard end-to-end services between functions resident on board a spacecraft or based on the ground, that are responsible for mission operations.

Contents

The CCSDS Mission Operations (MO) Services provides a set of standard operations services for the day-to-day operation of space assets and are outlined in the CCSDS Mission Operations Services Concept. [1]

Service Definition

Each service is defined in terms of an information model that defines a set of object types that are shared by providers and consumers of the service. Examples of such object types are status parameters, control actions and notification alerts, orbit vectors, schedules, planning requests and software images.

In addition to definition of the static information model, the service defines the interactions (through extension of the patterns defined in the Message Abstraction Layer) required between service provider and consumer to allow:

The specification of an MO service defines the structure of the objects, however, each deployment (or instantiation) of a service will also require service configuration data that defines the actual instances of those object types that exist for that service instance. For example, the M&C service may define what parameters, actions and alerts are, but it is the associated service configuration data that specifies the set of parameters, actions and alerts that exist for a particular spacecraft.

Identified Mission Operations Services

The following table lists the application-level Mission Operations services that have currently been identified by the working group. [1] It is to be stressed, however, that the service framework is designed to be extensible and additional services may be identified in the future to address additional requirements for end-to-end interaction in mission operations.

NameService Objects and Operations
Monitoring & ControlParameters: monitor status

Actions [Commands]: monitor status; precheck; invoke Alerts [Events]: raise; request state; monitor occurrence

TimeTime: report; set; correlate; notify
Software ManagementOn-board Software: load; dump
AutomationProcedure/Function: control; progress reporting
SchedulingSchedule: distribute; edit; control; progress reporting
Planning RequestPlanning Request/Goal: request; response
Data Product ManagementData Product [Payload Data File]: directory; transfer
NavigationPosition: tracking, ranging, onboard positioning

Orbit/Attitude/Predicted Events: determination, propagation, manoeuvre preparation

Remote Buffer ManagementBuffer: catalogue; retrieve; clear

NOTE – Services are listed together with a summary of the associated Service Objects and Operations.

See also

Related Research Articles

SOAP Messaging protocol for web services

SOAP is a messaging protocol specification for exchanging structured information in the implementation of web services in computer networks. Its purpose is to provide extensibility, neutrality, verbosity and independence. It uses XML Information Set for its message format, and relies on application layer protocols, most often Hypertext Transfer Protocol (HTTP), although some legacy systems communicate over Simple Mail Transfer Protocol (SMTP), for message negotiation and transmission.

In telecommunication, provisioning involves the process of preparing and equipping a network to allow it to provide new services to its users. In National Security/Emergency Preparedness telecommunications services, "provisioning" equates to "initiation" and includes altering the state of an existing priority service or capability.

Windows Management Instrumentation (WMI) consists of a set of extensions to the Windows Driver Model that provides an operating system interface through which instrumented components provide information and notification. WMI is Microsoft's implementation of the Web-Based Enterprise Management (WBEM) and Common Information Model (CIM) standards from the Distributed Management Task Force (DMTF).

The High Level Architecture (HLA) is a standard for distributed simulation, used when building a simulation for a larger purpose by combining (federating) several simulations. The standard was developed in the 90s under the leadership of the US Department of Defense and was later transitioned to become an open international IEEE standard. It is a recommended standard within NATO through STANAG 4603. Today the HLA is used in a number of domains including defense and security and civilian applications.

Interplanetary Internet model of Internet between planets

The interplanetary Internet is a conceived computer network in space, consisting of a set of network nodes that can communicate with each other. These nodes are the planet's orbiters (satellites) and landers, and the earth ground stations. For example, the orbiters collect the scientific data from the Curiosity rover on Mars through near-Mars communication links, transmit the data to Earth though direct links from the Mars orbiters to the Earth ground stations, and finally the data can be routed through Earth's internal internet.

Glossary of Unified Modeling Language (UML) terms provides a compilation of terminology used in all versions of UML, along with their definitions. Any notable distinctions that may exist between versions are noted with the individual entry it applies to.

CANopen is a communication protocol and device profile specification for embedded systems used in automation. In terms of the OSI model, CANopen implements the layers above and including the network layer. The CANopen standard consists of an addressing scheme, several small communication protocols and an application layer defined by a device profile. The communication protocols have support for network management, device monitoring and communication between nodes, including a simple transport layer for message segmentation/desegmentation. The lower level protocol implementing the data link and physical layers is usually Controller Area Network (CAN), although devices using some other means of communication can also implement the CANopen device profile.

An Open Archival Information System is an archive, consisting of an organization of people and systems, that has accepted the responsibility to preserve information and make it available for a Designated Community. The OAIS model can be applied to various archives, e.g., “open access, closed, restricted, “dark,” or proprietary.

In computing, an attribute is a specification that defines a property of an object, element, or file. It may also refer to or set the specific value for a given instance of such. For clarity, attributes should more correctly be considered metadata. An attribute is frequently and generally a property of a property. However, in actual usage, the term attribute can and is often treated as equivalent to a property depending on the technology being discussed. An attribute of an object usually consists of a name and a value; of an element, a type or class name; of a file, a name and extension.

Entity Framework (EF) is an open source object-relational mapping (ORM) framework for ADO.NET. It was originally shipped as an integral part of .NET Framework. Starting with Entity Framework version 6, it has been delivered separately from the .NET Framework.

The Spacecraft Monitoring & Control (SM&C) Working Group of the Consultative Committee for Space Data Systems (CCSDS), which sees the active participation of the main space agencies, is defining a service-oriented architecture consisting of a set of standard end-to-end services between functions resident on board a spacecraft or based on the ground, that are responsible for mission operations.

The Spacecraft Monitoring & Control (SM&C) Working Group of the Consultative Committee for Space Data Systems, which sees the active participation of 10 space agencies and of the Space Domain Task Force of the Object Management Group, is defining a service-oriented architecture consisting of a set of standard end-to-end services between functions resident on board a spacecraft or based on the ground, that are responsible for mission operations.

Live distributed object

Live distributed object refers to a running instance of a distributed multi-party protocol, viewed from the object-oriented perspective, as an entity that has a distinct identity, may encapsulate internal state and threads of execution, and that exhibits a well-defined externally visible behavior.

Event-driven SOA is a form of service-oriented architecture (SOA), combining the intelligence and proactiveness of event-driven architecture with the organizational capabilities found in service offerings. Before event-driven SOA, the typical SOA platform orchestrated services centrally, through pre-defined business processes, assuming that what should have already been triggered is defined in a business process. This older approach does not account for events that occur across, or outside of, specific business processes. Thus complex events, in which a pattern of activities—both non-scheduled and scheduled—should trigger a set of services is not accounted for in traditional SOA 1.0 architecture.

The beacon mode service is a Consultative Committee for Space Data Systems (CCSDS) telecommunications service aimed at spacecraft which are not communicated with via the Deep Space Network. It is primarily designed to relay a spacecraft's "health" information, and secondarily its telecommunications status, using a simple signal that can be detected with a moderately-sized antenna. Beacon mode also enables spacecraft to communicate with one another on a daily basis, allowing for one spacecraft to act as a data proxy for another.

The Application Interface Specification (AIS) is a collection of open specifications that define the application programming interfaces (APIs) for high-availability application computer software. It is developed and published by the Service Availability Forum and made freely available. Besides reducing the complexity of high-availability applications and shortening development time, the specifications intended to ease the portability of applications between different middleware implementations and to admit third party developers to a field that was highly proprietary in the past.

The Consultative Committee for Space Data Systems (CCSDS) was founded in 1982 for governmental and quasi-governmental space agencies to discuss and develop standards for space data and information systems. Currently composed of "eleven member agencies, twenty-eight observer agencies, and over 140 industrial associates," the CCSDS works to support collaboration and interoperability between member agencies through the establishment of data and system standards. According to the organisation's website, more than 900 space missions have utilized data and systems standards created by CCSDS. The activities of the CCSDS are organized around six topic areas and composed of many working groups within the overall Collaborative Working Group Environment (CWE).

OPS-SAT

OPS-SAT is a CubeSat by the European Space Agency (ESA) and it is intended to demonstrate the improvements in mission control capabilities that will arise when satellites can fly more powerful on-board computers. The satellite features an experimental computer that is ten times more powerful than any current ESA spacecraft.

Ground segment ground-based elements of a spacecraft system

A ground segment consists of all the ground-based elements of a spacecraft system used by operators and support personnel, as opposed to the space segment and user segment. The ground segment enables management of a spacecraft, and distribution of payload data and telemetry among interested parties on the ground. The primary elements of a ground segment are:

The NanoSat MO Framework (NMF) is a software framework for nanosatellites based on CCSDS Mission Operations services. It facilitates not only the monitoring and control of the nanosatellite software applications, but also the interaction with the nanosatellite platform. This is achieved by using the latest CCSDS standards for monitoring and control, and by exposing services for common peripherals among nanosatellite platforms. Furthermore, it is capable of managing the software on-board by exposing a set of services for software management.

References

  1. 1 2 Mission Operations Services Concept, CCSDS 520.0-G-3. Green Book. Issue 3. December 2010

29335606771