ETSI - TS 102 357
Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM); Common Air interface specification; Satellite Independent Service Access Point (SI-SAP) interface: Primitives
|Publication Date:||1 May 2015|
The present document specifies the Satellite Independent Service Access Point (SI-SAP) for the provision of standard Broadband Satellite Multimedia (BSM) services. The SI-SAP defines the Satellite Independent to Satellite Dependent (SI-SD) interface as described in the BSM Services and Architectures report ETSI TR 101 984 [i.1].
The SI-SAP services are accessed via the SI-SAP interface and they can be used to transport standard IP-based network services. These SI-SAP services are applicable to any IP-based satellite network, including both transparent and regenerative satellites, and including both star and mesh topologies. For example, in the case of a star network topology, one SI-SAP would be located in the remote Satellite Terminal (ST) and the other in the hub ST; whereas in the case of a mesh network topology, the SI-SAPs would be located in the source and destination STs.
The present document divides the services into user plane (U-plane), control plane (C-plane), and management plane (M-plane) services. This is a logical (functional) division but these different planes may also be physically separated. For example, in the case of a star topology being used to provide mesh connectivity using bridging at the hub, the SI-SAP will be located in the remote STs for the U-plane but will be located in the remote STs plus the hub ST for the C-plane and M-plane. Similar separations may be required for fully meshed network topologies.
The SI-SAP is a logical interface and the service primitives are defined in abstract functional terms. The present document is only intended to define the functionality of this interface and is not intended to constrain the implementation of the interface. The SI-SAP may be implemented as a physical external interface (e.g. using message based exchanges, as reported in annex B of ETSI TS 103 275 ); as a logical interface (e.g. using API function calls); as an internal interface (e.g. using embedded procedure calls) or in any other format that provides the specified functionality.
More details of the models and concepts used in the present document can be found in the associated SI-SAP guidelines ETSI TR 102 353 [i.2].