ETSI TS 102 602-2009 Satellite Earth Stations and Systems (SES) Broadband Satellite Multimedia Connection Control Protocol (C2P) for DVB-RCS Specifications (V1 1 1 Includes Diskett.pdf

1、 ETSI TS 102 602 V1.1.1 (2009-01)Technical Specification Satellite Earth Stations and Systems (SES);Broadband Satellite Multimedia;Connection Control Protocol (C2P) for DVB-RCS;Specificationsfloppy3 ETSI ETSI TS 102 602 V1.1.1 (2009-01) 2 Reference DTS/SES-00275 Keywords broadband, control, DVB, mul

2、timedia, protocol, satellite 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 Individual copies

3、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 Format (PDF

4、). 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 current status o

5、f 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: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as

6、 authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2009. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered f

7、or 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. LTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TS 102 602 V1.1.1

8、(2009-01) 3 Contents Intellectual Property Rights7 Foreword.7 Introduction 7 1 Scope 8 2 References 9 2.1 Normative references .9 2.2 Informative references9 3 Definitions and abbreviations.10 3.1 Definitions10 3.2 Abbreviations .11 4 Connection Control Overview14 4.1 Protocol High Level Functionali

9、ty .14 4.2 DVB-RCS Network Reference Scenarios 15 4.3 Definition of C2P Elements17 4.3.1 Connection17 4.3.2 Stream.18 4.3.3 IP Flow .18 4.3.4 Channel and Channel_ID19 4.3.5 Route and Route_ID .19 4.4 Connection Types.20 4.4.1 Star and mesh connections20 4.4.2 Signalling and traffic connections 20 4.

10、4.2.1 Signalling connections 20 4.4.2.2 Traffic connections21 4.4.3 C2P connection profile .23 4.5 Overview of C2P messages23 4.6 Data structures and dynamic connectivity support.24 4.6.1 C2P logon information24 4.6.2 C2P functional flags29 4.6.3 RCST data structures 29 4.6.3.1 Packet Classification

11、 Table .30 4.6.3.2 Connection Profile Mapping Table.31 4.6.3.3 Active Connections Table.32 4.6.3.4 PHB/CoS Mapping Table .35 4.6.3.5 Request Class (RC) Table .36 5 State Machines, counters and timers 37 5.1 Introduction 37 5.2 Timers 39 5.2.1 RCST/RSGW timers.40 5.2.2 NCC timers .41 5.3 Counters .42

12、 5.3.1 RCST/RSGW counters .42 5.3.2 NCC counters43 5.4 PER-Connection State machines43 5.4.1 RCST state machine43 5.4.2 NCC state machine .48 5.4.2.1 RCST/RSGW initiated unicast connections49 5.4.2.2 NCC initiated unicast connections 58 6 Connection Control Procedures67 6.1 Point-to-point connection

13、 establishment procedures68 6.1.1 RCST/RSGW initiated connections68 6.1.1.1 Successful set up .68 ETSI ETSI TS 102 602 V1.1.1 (2009-01) 4 6.1.1.2 Successful set up - Resolved cross connection70 6.1.2 NCC initiated connections 73 6.2 Point-to-multipoint connection establishment procedures .74 6.2.1 R

14、CST/RSGW initiated connections74 6.2.2 NCC initiated connections 75 6.3 Point-to-point Connection release procedures76 6.3.1 RCST/RSGW initiated connections77 6.3.1.1 Successful release by the RCST/RSGW .77 6.3.1.2 Successful release by the NCC78 6.3.2 NCC initiated connections 79 6.4 Point-to-multi

15、point connection release procedures 80 6.4.1 RCST/RSGW initiated connections80 6.4.2 NCC initiated connections 81 6.5 Point-to-point connection modify procedures (rate change) 82 6.5.1 RCST/RSGW initiated connections83 6.5.2 NCC initiated connections 84 6.6 Point-to-multipoint connection modify proc

16、edures (rate change) 84 6.6.1 RCST/RSGW initiated connections85 6.6.2 NCC initiated connections 86 6.7 RC modify procedures86 6.7.1 RCST/RSGW initiated RC modify.87 6.7.2 NCC initiated RC modify .88 6.8 RCST Capability request/response procedures 88 6.8.1 RCST/RSGW initiated RCST Capability request.

17、89 6.8.2 NCC initiated RCST Capability request .89 7 Connection Control Messages Formatting.90 7.1 Overview 90 7.2 RCST to NCC messages (DULM) .90 7.2.1 DULM format.90 7.2.1.1 DULM with ATM formatting .90 7.2.1.2 DULM with MPEG formatting.92 7.2.2 Connection Control IE Types Description94 7.2.2.1 Me

18、ssage Header IE .96 7.2.2.2 Cause IE 98 7.2.2.3 Channel_ID IE 99 7.2.2.4 Source/Destination Address IE .99 7.2.2.5 Forward/Return Stream Identifier IE 100 7.2.2.5.1 Applicability100 7.2.2.5.2 MPEG2-TS stream 101 7.2.2.5.3 ATM stream 101 7.2.2.6 Connection Type IE 102 7.2.2.7 Forward/Return Profile I

19、E.102 7.2.2.8 Route_ID IE 104 7.2.2.9 RC_Capacity_Parameters IE.104 7.2.2.10 Other_Group_and_Logon_ID IE 104 7.2.2.11 Other_Channel_ID IE .105 7.2.2.12 Other_Route_ID IE .105 7.2.2.13 IPv6_Source_Address/IPv6_Destination_Address IE 105 7.2.2.14 Connection_Inactivity_Timeout IE.106 7.2.2.15 Maximum_P

20、acket_Size IE106 7.2.2.16 Traffic_Spec_and_Policy_Data IE106 7.2.2.17 RCST_Capability IE .106 7.2.2.18 MAC Destination Address IE .107 7.2.2.19 Connection_Status_Stats IE 107 7.3 NCC to RCST messages (TIMu)108 7.3.1 TIMu format .108 8 Connection Control Messages110 8.1 Point-to-point connection esta

21、blishment message113 8.1.1 Connection Establishment Request (CnxEstReq).113 8.1.1.1 RCST/RSGW initiated unicast connection .113 ETSI ETSI TS 102 602 V1.1.1 (2009-01) 5 8.1.1.1.1 From initiating RCST/RSGW to NCC (DULM).113 8.1.1.1.2 From NCC to peer RCST/RSGW (TIMu).114 8.1.1.2 NCC initiated unicast

22、connection (TIMu).115 8.1.2 Connection Establishment Response (CnxEstResp).116 8.1.2.1 RCST/RSGW initiated unicast connection .116 8.1.2.1.1 From peer RCST/RSGW to NCC (DULM) 117 8.1.2.1.2 From NCC to initiating RCST/RSGW (TIM) .118 8.1.2.2 NCC initiated unicast connection118 8.2 Point-to-multipoint

23、 connection establishment messages120 8.2.1 Connection Establishment Request (CnxEstReq).121 8.2.1.1 RSGW initiated regenerative multicast connection 121 8.2.1.2 RCST initiated multicast connection.121 8.2.1.3 NCC initiated multicast connection 122 8.2.2 Connection Establishment Response (CnxEstResp

24、).124 8.2.2.1 RSGW initiated regenerative multicast connection 124 8.2.2.2 RCST initiated multicast connection.125 8.2.2.3 NCC initiated multicast connection 126 8.3 Connection release messages .127 8.3.1 Connection Release Request (CnxRelReq).127 8.3.2 Connection Release Response (CnxRelResp).128 8

25、.4 Connection modify messages .128 8.4.1 Connection Modify Request (CnxModReq) .129 8.4.2 Connection Modify Response (CnxModResp) .130 8.5 RC Modify messages131 8.5.1 RC Modify Request (RCModReq) .131 8.5.2 RC Modify Response (RCModResp) .132 8.6 RCST Capability messages 132 8.6.1 RCST Capability Re

26、quest (RCSTCapReq).132 8.6.2 RCST Capability Response (RCSTCapResp).133 8.7 Connection Status Stats Messages135 8.7.1 Connection Status Stats Request (CnxStatusStatsReq).135 8.7.2 Connection Status Stats Response (CnxStatusStatsResp).136 Annex A (informative): C2P state machines 137 A.1 RCST PER-CON

27、NECTION state machine139 A.2 NCC PER-CONNECTION state machine .139 A.3 RCST PER-RC state machine 139 A.4 NCC PER-RC state machine139 A.5 Example of the mapping between C2P UML, PER-ST and PER-CONNECTION state machines.139 Annex B (informative): C2P scenarios .141 Annex C (informative): Examples of C

28、2P exception procedures.146 C.1 Point-to-point connection establishment procedures146 C.1.1 RCST/RSGW initiated connections .146 C.1.1.1 Successful set up - Initiating RCST/RSGW retry.146 C.1.1.2 Successful set up - NCC retry.147 C.1.1.3 Unsuccessful set up - Peer RCST/RSGW responses lost148 C.1.1.4

29、 Unsuccessful set up - Peer RCST/RSGW does not get any NCC set up message149 C.1.1.5 Unsuccessful set up - Initiating RCST/RSGW retry.150 C.1.1.6 Unsuccessful set up - NCC no answer151 C.1.1.7 Unsuccessful set up - NCC reject .152 C.1.1.8 Unsuccessful set up - Peer RCST/RSGW reject.153 C.1.1.9 Unsuc

30、cessful set up - Initiating RCST/RSGW release .154 C.1.1.10 Unsuccessful set up - NCC release .155 C.1.1.11 Unsuccessful set up - Peer RCST/RSGW release.156 C.1.2 NCC initiated connections157 C.1.2.1 Successful set up - NCC retry.157 ETSI ETSI TS 102 602 V1.1.1 (2009-01) 6 C.1.2.2 Unsuccessful set-u

31、p - One of the peer parties does not answer the NCCs setup requests158 C.1.2.3 Unsuccessful set-up - One of the peer parties does not answer the NCCs setup requests nor the NCCs release requests159 C.1.2.4 Unsuccessful set-up - One of the peer parties rejects the connection .160 C.1.2.5 Unsuccessful

32、 set-up - NCC release.161 C.2 Point-to-multipoint connection establishment procedures .162 C.2.1 RCST/RSGW initiated connections .162 C.2.1.1 Successful set-up: RCST/RSGW multicast source retry 162 C.2.1.2 Unsuccessful set-up: NCC reject 163 C.2.1.3 Unsuccessful set-up: RCST/RSGW multicast source re

33、lease.163 C.2.1.4 Unsuccessful set-up: NCC release 164 C.2.1.5 Unsuccessful set-up: Multicast source retry .165 C.2.2 NCC initiated connections166 C.2.2.1 Successful set-up: NCC retry166 C.2.2.2 Unsuccessful set-up: Multicast source reject167 C.2.2.3 Unsuccessful set-up: NCC release 167 C.2.2.4 Unsu

34、ccessful set-up: Multicast source no answer.168 C.2.2.5 Unsuccessful set-up: Logoff multicast source 169 C.3 Point-to-point Connection release procedures170 C.3.1 RCST/RSGW initiated connections .170 C.3.1.1 Successful release by the RCST/RSGW: RCST/RSGW retry or NCC no answer .170 C.3.1.2 Successfu

35、l release initiated by the RCST/RSGW: RCST/RSGW no answer .171 C.3.1.3 Successful release initiated by the NCC: NCC retry 172 C.3.1.4 Successful release by the NCC: Peer RCST/RSGW logoff173 C.3.1.5 Successful release by the RCST/RSGW: NCC busy 173 C.4 Point-to-multipoint connection release procedure

36、s175 C.4.1 RCST/RSGW initiated connections .175 C.4.1.1 Successful release by the multicast source: NCCs responses get lost175 C.4.1.2 Successful release by the multicast source: Multicast sources requests get lost 176 C.4.1.3 Successful release: NCC busy 177 C.4.1.4 Unsuccessful release by the NCC

37、(of an RCST/RSGW initiated connection): Multicast source no answer.179 C.5 Point-to-point connection modify procedures (rate change) 180 C.5.1 RCST/RSGW initiated connections .180 C.5.1.1 Unsuccessful connection modify profile - NCCs responses get lost180 C.5.2 NCC initiated connections182 C.5.2.1 U

38、nsuccessful connection modify: RCST As responses get lost .182 C.6 Point-to-multipoint connection modify procedures (rate change)184 C.6.1 RCST/RSGW initiated connections .184 C.6.1.1 Unsuccessful connection modify profile - NCCs responses lost184 C.6.2 NCC initiated connections186 C.6.2.1 Unsuccess

39、ful connection modify: RCST/RSGW connection modify responses lost186 C.7 RC modify procedures187 C.7.1 RCST/RSGW initiated RC modify 187 C.7.1.1 Unsuccessful RC modify - NCC no answer187 C.7.2 NCC initiated RC modify.189 C.7.2.1 Unsuccessful RC modify - RCST/RSGW no answer .189 C.8 RCST Capability p

40、rocedures192 C.8.1 RCST/RSGW initiated RCST Capability notify 192 C.8.1.1 Unsuccessful RCST/RSGW initiated RCST Capability notify.192 C.8.2 NCC initiated Capability Notify.193 C.8.2.1 Unsuccessful NCC initiated RCST Capability Notify193 History 194 ETSI ETSI TS 102 602 V1.1.1 (2009-01) 7 Intellectua

41、l 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 non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IP

42、Rs); 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/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR sear

43、ches, 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 to the present document. Foreword This Technical Specification (TS) has been produc

44、ed by ETSI Technical Committee Satellite Earth Stations and Systems (SES). Introduction The present document is the first published version of a converged C2P specification for DVB-RCS systems, bringing together requirements for a range of different system scenarios. The present document is based on

45、 existing C2P implementation but with several important extensions and changes. Readers of the present document are therefore advised that the present document may be subject to changes in order to incorporate any possible corrections that may result from the testing and verification of the first im

46、plementations of the present document. ETSI ETSI TS 102 602 V1.1.1 (2009-01) 8 1 Scope The present BSM document defines and specifies a Connection Control Protocol (C2P) for DVB-RCS satellite networks, relying on specific DVB-RCS layer 2 signalling (DULM on the return link, unicast TIM on the forwar

47、d link). C2P is part of the control plane layer 2 functionality and is generally used for the dynamic establishment and management of connections between the ground elements of DVB-RCS networks (RCSTs, Gateways, NCC), regardless of their architectures and topologies (single-beam/multiple-beam archit

48、ectures, transparent/regenerative satellite payloads, star/mesh topologies). In this context C2P can be seen as a complement to the functionality of the interfaces already defined in the DVB-RCS and DVB-S/S2 standards 1 and i.1. The present document is organized as follows: Clause 4 contains the des

49、cription of the network reference scenarios (clause 4.2), of the C2P core elements (clause 4.3), of the connection types (clause 4.4) and of various data structures for dynamic connectivity support (clause 4.6). Clause 5 describes the state machines, including the timer and counter definitions and examples of state machines diagrams. Clause 6 describes the normal procedures and a few examples of exception procedures. Clause 7 describes the C2P Information Elements (IEs). Clause 8 defines the C2P messages. Annex A includes the description of C2P State Mac