ETSI TR 102 353-2015 Satellite Earth Stations and Systems (SES) Broadband Satellite Multimedia (BSM) Guidelines for the Satellite Independent Service Access Point (SI-SAP) (V1 2 1)_1.pdf

1、 ETSI TR 102 353 V1.2.1 (2015-12) Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM); Guidelines for the Satellite Independent Service Access Point (SI-SAP) TECHNICAL REPORT ETSI ETSI TR 102 353 V1.2.1 (2015-12) 2 Reference RTR/SES-00352 Keywords broadband, interface, s

2、atellite, service ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be d

3、ownloaded from: http:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any exi

4、sting or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be su

5、bject to revision or change of status. Information on the current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: https:/portal.etsi.org/People/Co

6、mmiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. The content of the PDF version shall not be modified without the writte

7、n authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2015. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM

8、and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TR 102 353 V1.2.1 (2015-12) 3 Contents Intellectual Property Rights 4g3Foreword . 4g3Modal ve

9、rbs terminology 4g31 Scope 5g32 References 5g32.1 Normative references . 5g32.2 Informative references 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 6g34 SI-SAP architecture 6g34.1 BSM functional architecture. 6g34.2 Client-Server model . 8g34.3 SI-SAP model . 8g34.4

10、 Protocols for the CSF-3 interface . 9g35 SI-SAP addresses and identifiers . 11g35.1 General . 11g35.2 SI-SAP addressing 11g35.2.0 Overview 11g35.2.1 BSM_IDentity (BSM_ID) 11g35.2.2 Unicast and group BSM_IDs 12g35.2.3 IP unicast addressing 12g35.2.4 IPv4 multicast addressing . 13g35.3 Queue IDentifi

11、ers (QIDs) . 14g36 SI-SAP functions 14g36.1 General . 14g36.1.0 Overview of functional planes and groups . 14g36.1.1 U-plane functions 15g36.1.2 C-plane functions 15g36.1.3 M-plane functions . 15g36.2 SI-SAP data transfer . 15g36.3 SI-SAP address resolution 16g36.3.1 General 16g36.3.2 Static vs. dyn

12、amic address resolution . 17g36.3.3 Unicast address resolution 17g36.3.4 Multicast address resolution . 17g36.4 Resource reservation 18g36.4.1 General 18g36.4.2 Resource reservation . 18g36.4.3 Quality of Service . 19g36.5 Group receive . 19g36.5.1 General 19g36.6 Group transmit 20g36.6.1 General 20

13、g37 IP interworking scenarios . 20g37.1 General . 20g37.2 Sending unicast data . 21g37.3 Receiving multicast data 22g3Annex A (informative): Bibliography . 23g3History 24g3ETSI ETSI TR 102 353 V1.2.1 (2015-12) 4 Intellectual Property Rights IPRs essential or potentially essential to the present docu

14、ment may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of

15、 ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/ipr.etsi.org). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IP

16、Rs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Report (TR) has been produced by ETSI Technical Committee Satellite Earth Stations and Systems (SES). Modal verbs terminology I

17、n the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI de

18、liverables except when used in direct citation. ETSI ETSI TR 102 353 V1.2.1 (2015-12) 5 1 Scope The present document provides a guide to the underlying models and assumptions that have been used to specify the BSM Satellite Independent Service Access Point (SI-SAP) interface. 2 References 2.1 Normat

19、ive references References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) app

20、lies. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following

21、referenced documents are necessary for the application of the present document. Not applicable. 2.2 Informative references References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version appli

22、es. For non-specific references, the latest version of the reference document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not neces

23、sary for the application of the present document but they assist the user with regard to a particular subject area. i.1 ETSI TR 101 984: “Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM); Services and architectures“. i.2 ETSI TS 102 292: “Satellite Earth Stations and

24、Systems (SES); Broadband Satellite Multimedia (BSM) services and architectures; Functional architecture for IP interworking with BSM networks“. i.3 ETSI TS 102 295: “Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM) services and architectures; BSM Traffic Classes“. i.4

25、 ETSI TR 102 375: “Satellite Independent Service Access Point (SI-SAP) interface: Services“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: BSM_IDentity (BSM_ID): SI-SAP address that defines the BSM Subnetwork Poin

26、t of Attachment (SNPA) NOTE: The BSM_ID is divided into BSM Unicast ID (BSM_UID) and BSM Group ID (BSM_GID). BSM Subnetwork Point of Attachment (SNPA): SI-SAP endpoint of the BSM data transport services NOTE: The BSM_ID is used to address data sent to and received from the BSM Subnetwork Point of At

27、tachment. ETSI ETSI TR 102 353 V1.2.1 (2015-12) 6 Queue IDentifier (QID): SI-SAP parameter that identifies an abstract queue at the SI-SAP NOTE: The QID is used to identify a specific lower layer resource when sending (submitting) data via the SI-SAP. SI-SAP Instance (SAPI): specific independent ins

28、tance of the SI-SAP in one ST NOTE: A single unicast BSM_ID (UID) is associated with each instance of the SI-SAP (each SAPI). In addition one or more group BSM_IDs (GIDs) may be associated with each instance of the SI-SAP. 3.2 Abbreviations For the purposes of the present document, the following abb

29、reviations apply: ARP Address Resolution Protocol ASM Any Source Multicast BSM Broadband Satellite Multimedia BSM_GID BSM Group Identity BSM_ID BSM IDentity BSM_UID BSM Unicast IDentity CSF Client Server Function Flowspec flow specification GID Group ID ID IDentity IP Internet Protocol IPv4 Internet

30、 Protocol version 4 IPv6 Internet Protocol version 6 L2Add Layer 2 Address LL Lower Layer LN Local Network MAC Medium Access Control NAT Network Address Translation ND Neighbor Discovery PEP Performance Enhancing Proxy QID Queue IDentifier QoS Quality of Service RSVP Resource ReserVation Protocol SA

31、PI SI-SAP Instance SD Satellite Dependent SDAF Satellite Dependent Adaptation Functions SD-ARP Satellite Dependent Address Resolution Protocol SDU Service Data Unit SI Satellite Independent SIAF Satellite Independent Adaptation Functions SI-SAP Satellite Independent Service Access Point SN Satellite

32、 Network SNPA BSM SubNetwork Point of Attachment SSM Source Specific Multicast ST Satellite Terminal UID Unicast ID UL Upper Layer 4 SI-SAP architecture 4.1 BSM functional architecture The Satellite Independent Service Access Point (SI-SAP) is introduced in the BSM services and architectures report

33、(see ETSI TR 101 984 i.1) and a more detailed functional model of this interface is provided in the BSM functional architecture (see ETSI TS 102 292 i.2). ETSI ETSI TR 102 353 V1.2.1 (2015-12) 7 Figure 4.1.1, which is reproduced from the BSM functional architecture (see ETSI TS 102 292 i.2) presents

34、 the BSM protocol stack for unicast services and figure 4.1.2 presents the same stack showing the multicast functions. Both figures show the location of the Satellite Independent Service Access Point (SI-SAP) interface. This interface provides the BSM with a layer of abstraction for the lower layer

35、functions and makes use of a BSM specific identity, the BSM_ID, to address the BSM subnetwork point of attachment (SNPA). It allows the BSM protocols developed in the Satellite Independent layer to operate over any BSM family. Moreover, the SI-SAP also enables the use of standard Internet protocols

36、for example address resolution or multicast group management, directly over the BSM or with minimal adaptation to lower layer physical characteristics. Lastly the SI-SAP even makes it possible to envisage switching from one satellite system to another while preserving the BSM operators investment in

37、 layer 3 software development. NOTE: This figure is taken from ETSI TS 102 292 i.2. Figure 4.1.1: BSM protocol stack for unicast services SIAFAddressTableIP RoutingIP Route DeterminationBSMSecurityMgmtSatellite Link Control (SLC)Satellite Medium Access Control (SMAC)Satellite Physical (SPHY)SDAFSate

38、llite Data Unit SwitchingBSMAddress ResolutionBSMAddress ResolutionIP SecurityIPv4 and IPv6SI-U-SAPSI-C-SAPSI-M-SAPSegmentation/encapsulationBSM QoSAdaptationBSMRoutingAdaptationIP QoS ManagementIP Packet ForwardingBSM QoSMgmtBSMResourceMgmtBSMSecurityMgmtBSMTrafficManagerBSM SDQueueManagerETSI ETSI

39、 TR 102 353 V1.2.1 (2015-12) 8 NOTE: This figure is taken from ETSI TS 102 292 i.2. Figure 4.1.2: BSM protocol stack for multicast services 4.2 Client-Server model The BSM functional architecture (see ETSI TS 102 292 i.2) defines a Client-Server model that includes three logical interfaces called Cl

40、ient Server Function (CSF) interfaces. 4.3 SI-SAP model The SI-SAP model divides the protocol stack at an ST into two parts as illustrated in figure 4.3.1: 1) The Satellite Independent (SI) Upper Layers (UL). 2) The Satellite Dependent (SD) Lower Layers (LL). The SI-SAP model also defines two adapta

41、tion layers. These are also shown in figure 4.3.1: 1) The Satellite Independent Adaptation Functions (SIAF) to adapt between the upper layers and the SI-SAP services. 2) The Satellite Dependent Adaptation Functions (SDAF) to adapt between the lower layers and the SI-SAP services. SIAFAddressTableIP

42、Packet ForwardingSIMcastSecuritySatellite Link Control (SLC)Satellite Medium Access Control (SMAC)Satellite Physical (SPHY)SDAFSatellite Data Unit SwitchingBSM MulticastAddress ResolutionBSM MulticastAddress ResolutionIP McastSecurityIPv4 and IPv6SI-U-SAP SI-C-SAP SI-M-SAPBSMResourceMgmtIP Multicast

43、 RoutingSegmentation/encapsulationBSM Multicast GroupManagementBSM MulticastRoutingAdaptationSDSecurityMgmtSD MulticastFunctionsETSI ETSI TR 102 353 V1.2.1 (2015-12) 9 Figure 4.3.1: SI-SAP interface and the protocol stack 4.4 Protocols for the CSF-3 interface The protocols that are used for the CSF-

44、3 interface (see ETSI TS 102 292 i.2) can be divided into satellite independent upper layer protocols and satellite dependent lower layer protocols as illustrated in figure 4.4.1. NOTE: The adaptation functions (SIAF and SDAF) do not include any protocols. The protocols are assumed to be located in

45、either the IP layer (satellite independent case) or in the SLC/SMAC layer (satellite dependent case). Figure 4.4.1: Protocols for the CSF-3 interface Satellite Link Control (SLC)Satellite Physical (SPHY)SI-SAPIPV4 / IPV6Satellite Medium Access Control (SMAC)Satellite Independent Adaptation Functions

46、Satellite Dependent Adaptation FunctionsUpperLayers(satelliteindependent)LowerLayers(satellitedependent)Client ServerSatelliteSI-SAPIPfunctionsSI-SAPIPfunctionsLower layer protocolUpper layer protocolIP interworking IP interworkingIP functionAdaptation functionSD functionKEYSIAFfunctionsSLC/SMACfunc

47、tionsSDAFfunctionsSLC/SMACfunctionsSIAFfunctionsSDAFfunctionsETSI ETSI TR 102 353 V1.2.1 (2015-12) 10 A given IP interworking function can be realized using either the upper layer protocols or the lower layer protocols as follows: a) Upper Layer protocol (figure 4.4.2): In this case the IP interwork

48、ing functional exchanges between the Client and Server are carried using a satellite independent upper layer protocol(s). This upper layer protocol is then carried transparently by the SI-SAP U-plane data transport services. The upper layer protocols can be any suitable network layer protocol; for e

49、xample, standard IETF protocols; or adapted IETF protocols, or non-standard network layer protocols. b) Lower Layer protocol (figure 4.4.3): In this case, the IP interworking functional exchanges between the Client and Server are carried using a satellite dependent lower layer protocol(s). The network layer at the Client and the Server interwork these functions into an SI-SAP C-plane primitive. Below the SI-SAP these primitives activate the appropriate lower layer protocol(s). The available set of SI-SAP C-plane primitives (and the associated functions)