1、 ETSI TS 102 189-3 V1.1.2 (2004-07)Technical Specification Satellite Earth Stations and Systems (SES);Regenerative Satellite Mesh - A (RSM-A);SMAC/SLC layer specification;Part 3: ST-SAM Interface specificationETSI ETSI TS 102 189-3 V1.1.2 (2004-07) 2 Reference RTS/SES BSM-212-3 Keywords air interfac
2、e, broadband, satellite, multimedia, IP 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 Individ
3、ual copies of the present document can be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document
4、Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the curre
5、nt 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, send your comment to: editoretsi.org Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the fo
6、regoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2004. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON logo are Trade Marks currently being registered
7、 by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TS 102 189-3 V1.1.2 (2004-07) 3 Contents Intellectual Property Rights5 Foreword.5 1 Scope 6 2 References 6 3 Definitions and abbreviati
8、ons.6 3.1 Definitions6 3.2 Abbreviations .7 4 General aspects.7 4.1 Security Access Module - functional description.7 5 ST-SAM physical interface9 6 Client - Function interface9 6.1 Procedures 9 6.1.1 Health check .9 6.1.2 Frame count maintenance .10 6.1.3 ACF procedure10 6.1.4 Bandwidth Request pro
9、cedure 11 6.1.5 Bandwidth Assignment procedure11 6.1.6 Bandwidth Request and Assignment timing requirements .12 6.1.7 Registration.14 6.1.8 De-registration 14 7 Management messages.14 7.1 General .14 7.2 Segmentation and reassembly 14 8 Message formats.15 8.1 Packet order of presentation .15 8.2 Ord
10、er of bits within a field .15 8.3 Message types 16 8.4 Error codes .17 8.5 Message header formats .18 8.5.1 SAM-ST header18 8.5.1.1 transID.18 8.5.1.2 msgLength.18 8.5.2 H2 header18 8.5.2.1 ST - SAM direction.18 8.5.2.2 SAM - ST direction.19 8.5.2.2.1 Function field 19 8.5.2.2.2 F/L field.19 8.5.2.2
11、.3 C bit .20 8.5.3 L1 header 20 8.5.3.1 TMF 20 8.5.3.2 Length .20 8.6 Message formats.20 8.6.1 ACF creation indication20 8.6.1.1 Sub-band designator21 8.6.1.2 HVUL bit 21 8.6.1.3 Carrier designator21 8.6.1.4 MAC header information 21 8.6.1.5 CGID index.21 8.6.1.6 Time slot number 21 8.6.2 ACF creati
12、on response21 8.6.3 ACF creation failure .22 ETSI ETSI TS 102 189-3 V1.1.2 (2004-07) 4 8.6.4 ACF creation frame count indication22 8.6.4.1 ST health check indication 22 8.6.5 ST health check response23 8.6.5.1 Return code .23 8.6.5.2 Boot SW version .23 8.6.5.3 Boot SW ICD version .23 8.6.5.4 Operat
13、ion SW version.23 8.6.5.5 Operation SW ICD version .23 8.6.5.6 RS bit 23 8.6.5.7 CK bit23 8.6.6 Bandwidth Assignment indication24 8.6.6.1 Uplink frame number 24 8.6.6.2 Number of assignments.24 8.6.6.3 IF version 24 8.6.6.4 Assignment field .24 8.6.6.5 TOD check 24 8.6.7 Bandwidth Assignment respons
14、e25 8.6.8 Bandwidth Assignment failure .25 8.6.8.1 Failure code.25 8.6.9 Bandwidth Request indication 26 8.6.9.1 Frame count.26 8.6.9.2 Bandwidth request header .26 8.6.9.3 Bandwidth request data .26 8.6.10 Bandwidth Request response 26 8.6.10.1 Integrity check.27 8.6.10.2 AB Key .27 8.6.11 Bandwidt
15、h Request Failure.27 8.6.12 ST registration indication27 8.6.12.1 challengeResponseTimeoutValue .27 8.6.12.2 registrationRequestTimeoutValue.27 8.6.13 ST registration complete.28 8.6.13.1 MC bit .28 8.6.14 ST registration failure backoff28 8.6.14.1 Error Code.28 8.6.14.2 backOffTime .28 8.6.15 SAM d
16、eregistration status.29 8.6.15.1 Error code29 Annex A (informative): SAM pin layout 30 A.1 SAM pin layout 30 Annex B (informative): Message flow diagrams31 B.1 Successful bandwidth request/assignment/data transfer 31 B.2 Successful registration31 B.3 Successful de-registration.32 Annex C (informativ
17、e): Bibliography.33 History 34 ETSI ETSI TS 102 189-3 V1.1.2 (2004-07) 5 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and
18、 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 ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/
19、IPR/home.asp). 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 IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential
20、 to the present document. Foreword This Technical Specification (TS) has been produced by ETSI Technical Committee Satellite Earth Stations and Systems (SES). The present document is part 3 of a multi-part deliverable covering Regenerative Satellite Mesh - A (RSM-A) air interface SMAC/SLC layer spec
21、ification, as identified below: Part 1: “General description“; Part 2: “Satellite Medium Access Control and Satellite Link Control detailed specification“; Part 3: “ST-SAM interface specification“. ETSI ETSI TS 102 189-3 V1.1.2 (2004-07) 6 1 Scope The present document defines the communication inter
22、face between a TC-SES BSM Regenerative Satellite Mesh-A (RSM-A) air interface compliant Satellite Terminal (ST) and the Security Access Module (SAM). It specifies the communication medium and the protocols for communication. The present document describes how packets, received at the ST from the Net
23、work Operations Control Centre (NOCC), are routed to the SAM, how messages created originally by the ST are routed to the SAM, how message from the SAM are routed via the ST to the NOCC and how messages from the SAM are consumption by the ST. 2 References The following documents contain provisions w
24、hich, through reference in this text, constitute provisions of the present document. References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference,
25、the latest version applies. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. 1 ETSI TS 102 188-5: “Satellite Earth Stations and Systems (SES); Regenerative Satellite Mesh - A (RSM-A) air interface; Physical
26、layer specification; Part 5: Radio transmission and reception“. 2 ETSI TS 102 188-7: “Satellite Earth Stations and Systems (SES); Regenerative Satellite Mesh - A (RSM-A) air interface; Physical layer specification; Part 7: Synchronization“. 3 ETSI TS 102 189-2: “Satellite Earth Stations and Systems
27、(SES); Regenerative Satellite Mesh - A (RSM-A); SMAC/SLC layer specification; Part 2: Satellite Medium Access Control and Satellite Link Control detailed specification“. 4 ETSI TS 102 189-1: “Satellite Earth Stations and Systems (SES); Regenerative Satellite Mesh - A (RSM-A); SMAC/SLC layer specific
28、ation; Part 1: General description“. 5 “Universal Serial Bus Specification“, revision 1.1, September 23, 1998. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: Network Operations Control Centre (NOCC): centre that co
29、ntrols the access of the satellite terminal to an IP network and also provides element management functions and control of the address resolution and resource management functionality satellite payload: part of the satellite that provides air interface functions NOTE: The satellite payload operates
30、as a packet switch that provides direct unicast and multicast communication between STs at the link layer. Satellite Terminal (ST): terminal that is installed in the user premises ETSI ETSI TS 102 189-3 V1.1.2 (2004-07) 7 terrestrial host: entity on which application level programs are running NOTE:
31、 It may be connected directly to the Satellite Terminal or through one or more networks. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: ACF Access Control Field BA Bandwidth Assignment BCSTID Bandwidth Control Satellite Terminal IDentity BR Bandwidth R
32、equest BRIC Bandwidth Request Integrity Check FIFO First In First Out HVUL High Volume UpLink IP Internet ProtocolLSB Least Significant Bit MAC Medium Access Control Mbps Mega-bits per second (millions of bits per second) MSB Most Significant Bit NOCC Network Operations Control Centre RSM Regenerati
33、ve Satellite Mesh SAM Security Access Module SAP Service Access Point SLC Satellite Link Control SOF Start Of Frame ST Satellite Terminal TOD Time Of Day UDP User Datagram Protocol USB Universal Serial Bus 4 General aspects 4.1 Security Access Module - functional description The SAM is the security
34、component of a satellite terminal. Physically it is a secure chip embedded in the terminal. The SAM contains secret key material and authenticates every RSM-A packet sent out by the terminal by generating an Access Control Field, which can be verified by other authorized components of the system. Th
35、e SAM will only sign requests that are valid within the policies set forth for that particular ST. On the receive side it verifies that management messages are authentic messages from the NOCC. The set of functionality, including the ACF generation, bandwidth assignment and bandwidth request integri
36、ty checks, is called capacity protection and is introduced in TR 102 287 (see bibliography). ETSI ETSI TS 102 189-3 V1.1.2 (2004-07) 8 Core Layers SD adaptationSI adaptation Ethernet or USB PHYSSMACSLC SD adaptationSI adaptationIP PHYSMEDIUM ACCESSCONTROLPHYS PHYSTo/fromHost To/from Host U interface
37、U interfaceSATELLITESATELLITE TERMINAL SI-SAP IP Transport Protocols IP IP Transport Protocols Application Protocols Application Protocols SATELLITE TERMINAL Ethernet or USB SLC SMACSI-SAP P interfaceT interfaceT interfaceRSM-A Air interface SI-SAP SAM SAM-ST interface SAM Figure 4.1: Protocol archi
38、tecture and SAM-ST interface The SAMs areas of responsibility to the RSM-A system are as follows: Authentication. Authorization protection. Registration. Usage audit. ACFOutputsfrom theSAMInputs tothe SAMSecurityAccessModuleAudit dataBandwidthrequestIntegrity CheckRequest forBandwidthRequest forACFs
39、 to SendTrafficManagementInformationfrom NOCCBandwidthAllocationfrom SatelliteManagementInformationfor NOCCFigure 4.2: Security function interactions between the SAM and the ST ETSI ETSI TS 102 189-3 V1.1.2 (2004-07) 9 5 ST-SAM physical interface The ST-SAM physical interface is divided into an elec
40、trical interface and a mechanical interface. The physical/electrical interface between the ST and the SAM shall be a Universal Serial Bus (USB) revision 1.1 5. The SAM shall be equivalent to a “USB device“ function and the ST shall be equivalent to a “USB host“. The ST implementation shall not requi
41、re the SAM to share this USB port with any other device or hub. The ST should suppress frame timing, i.e. should not send USB Start Of Frame (SOF) token timing packets on the USB interface. The physical/mechanical interface may use any suitable interface. An optional mechanical description is given
42、in annex A. Client USB System USB Bus Interface Function USB Device USB Bus Interface ST SAM Interconnect Actual communications flow Logical communications flow Phys/ mech interface Phys/ mech interface USB revision 1.1 ST-SAM interface Physical/mechanical interface between SAM and board Figure 5.1:
43、 Interlayer communications model 6 Client - Function interface 6.1 Procedures The ST and SAM shall use the messages described in the procedures below to communicate with each other. Whenever the ST sends the SAM an INDICATION message, the SAM shall always respond with either a RESPONSE message (for
44、a successful operation) or a FAILURE message (whenever the requested operation fails) with an error code. However, the SAM does not respond to the ACF FRAME COUNT INDICATION message. 6.1.1 Health check The ST sends the ST HEALTH CHECK INDICATION message to the SAM periodically. There is no strict re
45、quirement on the length of the period however it should be 1 second. The SAM shall respond with the ST HEALTH CHECK RESPONSE. ETSI ETSI TS 102 189-3 V1.1.2 (2004-07) 106.1.2 Frame count maintenance The ST shall send the Frame count at the start of each uplink frame using the ACF creation frame count
46、 message. The SAM shall use the latest Frame Count sent by the ST to process subsequent ACF Creation Indication Messages. The Frame count field is the current 35-bit uplink frame number in TOD 39, 5 format, as specified in TS 102 188-7 2. The ST shall send this message to the SAM within 100 s of the
47、 start of each uplink frame. 6.1.3 ACF procedure The ST shall send packet header information to the SAM, for both of the RSM-A packets contained in the uplink block that the ST is preparing to transmit, using the ACF CREATION INDICATION message. If the SAM approves the request, it shall respond with
48、 an ACF CREATION RESPONSE message containing the ACF field. The ST shall append this ACF to the MAC block before transmission to the satellite. The ST shall not transmit a MAC block to the satellite without an ACF field. The SAM responds to the ST with an ACF CREATION FAILURE message if the ACF cann
49、ot be computed. The following clause outlines the timing requirements for the ACF generation process. The timing diagram for the process is illustrated in figure 6.1. The diagram illustrates activity on the USB interface bus between the host and the SAM, as well as the processing that is performed by the SAM. The host initiates all activity on the USB bus, and the SAM behaves as a USB device. The process involves the following steps, and must be completed within one 16 Mbps code block period, which is 87,8 s. Figure 6.1 shows this code block per
