Space Link Extension - Service Management - CCSDS

DRAFT RECOMMENDED STANDARD FOR SPACE LINK EXTENSION SERVICE MANAGEMENT
ANNEX B
INCREMENTAL ADOPTION
(NORMATIVE)
This Recommended Standard recognizes that an installed base of service management
information and interfaces for SLE-SM exists. Therefore, the Recommended Standard
allows for incremental adoption and deployment towards standardized SLE-SM.
Table B-1 identifies the minimum set of operations that need to be implemented to be SLE-
SM compliant.
If an implementation is not fully compliant with the Recommended Standard, it is said to be
bilateral, which means that a particular UM and CM have agreed to accommodate variations
from the Recommended Standard. An implementation may be bilateral in the definition of
the content of the management information, or in the mechanisms used to exchange (e.g.,
create, delete, query) the information. If the table indicates that bilaterally defined exchange
is allowed for a particular type of management information, an implementation is not
required to use the SLE-SM service defined for that information.
An implementation may be compliant in one aspect and bilateral in another. For example, for
Configuration Profile operations, the message contents may be compliant, but the procedure
for transferring the data between UM and CM may be outside the SLE-SM Recommended
Standard. This case is an example of ‘bilaterally defined exchange allowed’.
An example of ‘bilaterally defined content allowed’ is the case where a network provides
services that are not completely in conformance with all of the CCSDS standards upon which
the standard Carrier Profiles are based, e.g., because a non-CCSDS-standard modulation
scheme is used. In such a case, an appropriate (bilaterally defined) carrier profile format
might be developed and agreed to by UM and CM, but could be exchanged via the standard
ASLSP and QSLSP operations. Thus space link service providers that support both CCSDS
and non-CCSDS-conformant spacecraft can use the common SLE-SM service infrastructure
to support both sets of clients.
CCSDS 910.11-R-2 Page B-1 March 2008