1、 TIA STANDARD SMCP: Satellite Network Modem System (SNMS) Mesh Control Protocol TIA-1088 May 2006 TELECOMMUNICATIONS INDUSTRY ASSOCIATION Representing the telecommunications industry in association with the Electronic Industries Alliance NOTICE OF COPYRIGHT This document is copyrighted by the TIA. R
2、eproduction of these documents either in hard copy or soft copy (including posting on the web) is prohibited without copyright permission. For copyright permission to reproduce portions of this document, please contact TIA Standards Department or go to the TIA website (www.tiaonline.org) for details
3、 on how to request permission. Details are located at: http:/www.tiaonline.org/standards/catalog/info.cfm#copyright OR Telecommunications Industry Association Standards (b) there is no assurance that the Document will be approved by any Committee of TIA or any other body in its present or any other
4、form; (c) the Document may be amended, modified or changed in the standards development or any editing process. The use or practice of contents of this Document may involve the use of intellectual property rights (“IPR”), including pending or issued patents, or copyrights, owned by one or more parti
5、es. TIA makes no search or investigation for IPR. When IPR consisting of patents and published pending patent applications are claimed and called to TIAs attention, a statement from the holder thereof is requested, all in accordance with the Manual. TIA takes no position with reference to, and discl
6、aims any obligation to investigate or inquire into, the scope or validity of any claims of IPR. TIA will neither be a party to discussions of any licensing terms or conditions, which are instead left to the parties involved, nor will TIA opine or judge whether proposed licensing terms or conditions
7、are reasonable or non-discriminatory. TIA does not warrant or represent that procedures or practices suggested or provided in the Manual have been complied with as respects the Document or its contents. If the Document contains one or more Normative References to a document published by another orga
8、nization (“other SSO”) engaged in the formulation, development or publication of standards (whether designated as a standard, specification, recommendation or otherwise), whether such reference consists of mandatory, alternate or optional elements (as defined in the TIA Engineering Manual, 4theditio
9、n) then (i) TIA disclaims any duty or obligation to search or investigate the records of any other SSO for IPR or letters of assurance relating to any such Normative Reference; (ii) TIAs policy of encouragement of voluntary disclosure (see Engineering Manual Section 6.5.1) of Essential Patent(s) and
10、 published pending patent applications shall apply; and (iii) Information as to claims of IPR in the records or publications of the other SSO shall not constitute identification to TIA of a claim of Essential Patent(s) or published pending patent applications. TIA does not enforce or monitor complia
11、nce with the contents of the Document. TIA does not certify, inspect, test or otherwise investigate products, designs or services or any claims of compliance with the contents of the Document. ALL WARRANTIES, EXPRESS OR IMPLIED, ARE DISCLAIMED, INCLUDING WITHOUT LIMITATION, ANY AND ALL WARRANTIES CO
12、NCERNING THE ACCURACY OF THE CONTENTS, ITS FITNESS OR APPROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, ITS MERCHANTABILITY AND ITS NONINFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL PROPERTY RIGHTS. TIA EXPRESSLY DISCLAIMS ANY AND ALL RESPONSIBILITIES FOR THE ACCURACY OF THE CONTENTS AND MAKES NO REPR
13、ESENTATIONS OR WARRANTIES REGARDING THE CONTENTS COMPLIANCE WITH ANY APPLICABLE STATUTE, RULE OR REGULATION, OR THE SAFETY OR HEALTH EFFECTS OF THE CONTENTS OR ANY PRODUCT OR SERVICE REFERRED TO IN THE DOCUMENT OR PRODUCED OR RENDERED TO COMPLY WITH THE CONTENTS. TIA SHALL NOT BE LIABLE FOR ANY AND
14、ALL DAMAGES, DIRECT OR INDIRECT, ARISING FROM OR RELATING TO ANY USE OF THE CONTENTS CONTAINED HEREIN, INCLUDING WITHOUT LIMITATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING DAMAGES FOR LOSS OF BUSINESS, LOSS OF PROFITS, LITIGATION, OR THE LIKE), WHETHER BASED UPO
15、N BREACH OF CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGATION OF DAMAGES IS A FUNDAMENTAL ELEMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WI
16、THOUT SUCH LIMITATIONS. iiiTable of Contents Table of Figures v References. vi Acronyms. vii 1 Background and Scope. 1 Mesh transparent network. 1 1.1 Organization of this Document and Relation of its Elements. 2 2 Overview 3 3 State Diagrams, Timers and Counters 5 3.1 Introduction. 5 3.1.1 Timers .
17、 6 RCST Timers 6 NCC Timers 6 3.1.2 Message Retransmission Counters . 7 RCST Message Retransmission Counters 7 NCC Message Retransmission Counters 7 3.2 Calling RCST State Diagram 8 3.3 NCC State Diagram 11 3.4 Called RCST State Diagram . 14 4 Protocol Procedures 17 4.1 Connection Setup Signaling 17
18、 4.1.1 Successful Setup . 17 4.1.2 Successful Setup Calling RCST Retry. 18 4.1.3 Successful Setup NCC Retry . 19 4.1.4 Successful Setup Called RCST Retry 20 4.1.5 Unsuccessful Setup Called RCST Not Responding. 20 4.1.6 Unsuccessful Setup Rejected by NCC. 21 4.1.7 Unsuccessful Setup Rejected by Calle
19、d RCST 22 4.1.8 Unsuccessful Setup Release from Calling RCST 22 4.1.9 Unsuccessful Setup Release from Called RCST . 23 4.1.10 Unsuccessful Setup NCC Reject after RCST Accept 23 4.2 Connection Rate (or other Profile) Change Signaling 24 4.2.1 Successful Rate Change 24 4.2.2 Successful Rate Change NCC
20、 Retry 25 4.2.3 Successful Rate Change Calling RCST Retry . 25 4.2.4 Successful Rate Change Called RCST Retry. 26 4.2.5 Unsuccessful Rate Change Rejection Scenarios 27 4.2.6 Successful Multiple Outstanding Rate Change Requests . 28 4.2.7 RCST Initiated Connection Release . 28 4.2.8 RCST Initiated Co
21、nnection Release Timeout at NCC. 29 4.2.9 RCST Initiated Connection Release Timeout at RCST. 29 4.2.10 NCC Initiated Connection Release . 30 4.2.11 NCC Initiated Connection Release Timeout at NCC 31 4.2.12 Unexpected Release Requests. 31 iv4.3 Status Inquiry Signaling 31 5 Connection Control message
22、s formatting. 32 5.1 RCST to NCC messages . 32 5.1.1 DULM format . 32 5.1.1.1 Message Header IE . 35 5.1.1.2 Cause IE 36 5.1.1.3 Channel_ID IE 37 5.1.1.4 Route_ID IE 37 5.1.1.5 Source/Destination address IEs. 37 5.1.1.6 Forward/Return stream Identifier IEs . 38 5.1.1.7 Connection Type IE 38 5.1.1.8
23、Forward/Return profiles IEs . 39 5.2 NCC to RCST messages . 40 5.2.1 TIMu format 40 6 Messages 42 6.1 Point-to-point connection establishment messages 42 6.1.1 CnxEstReq (Connection Establishment Request). 42 6.1.2 CnxEstResp (Connection Establishment Response). 43 6.2 Connection release messages 45
24、 6.2.1 CnxRelReq (Connection Release Request) 45 6.2.2 CnxRelResp (Connection Release Response) 45 6.3 Connection modify messages . 45 6.3.1 CnxModifyReq / Profile (Connection Modify Request) 46 6.3.2 CnxModifyResp / Profile (Connection Modify Response) 46 6.4 Channel modify messages. 47 6.4.1 ChnMo
25、difyReq (Channel modify request) . 47 6.4.2 ChnModifyResp (Channel modify response) . 48 6.5 Status Enquiry Message (NCC to RCST). 49 Appendix A Message Equivalencies between RSM-A and RSM-B Messages and Protocols 1 vTable of Figures Figure 1 Mesh Transparent Network . 2 Figure 2 Calling RCST State
26、Diagram 8 Figure 3 NCC State Diagram . 11 Figure 4 Called RCST State Diagram . 14 Figure 5 Successful Setup . 17 Figure 6 Successful Setup (with Origin Retry) . 18 Figure 7 Successful Setup (with NCC Retry) 19 Figure 8 Successful Setup (with Called RCST Retry . 20 Figure 9 Unsuccessful Setup (Called
27、 ST Not Responding) 21 Figure 10 Unsuccessful Setup Connection Rejected by NCC. 21 Figure 11 Unsuccessful Setup Connection Rejected by Called RCST. 22 Figure 12 Unsuccessful Setup Release from Calling RCST 22 Figure 13 Unsuccessful Setup Release from Called RCST . 23 Figure 14 Unsuccessful Setup NCC
28、 Reject after RCST Accept. 23 Figure 15 Successful Rate Change . 24 Figure 16 Successful Rate Change (NCC Retry) 25 Figure 17 Successful Rate Change (Calling RCST Retry). 26 Figure 18 Successful Rate Change (called RCST retry) 26 Figure 19 Unsuccessful RateChange Rejected by NCC 27 Figure 20 Unsucce
29、ssful Rate Change Rejected by Called RCST. 27 Figure 21 RCST Initiated Release 28 Figure 22 RCST Initiated Release Timeout at NCC . 29 Figure 23 RCST Initiated Release Timeout at RCST . 29 Figure 24 NCC Initiated Release 30 Figure 25 NCC Initiated Release Timeout at NCC . 31 Figure 26 DULM message w
30、ith ATM TRF bursts . 34 viReferences 1. IP Modem Functional Capabilities Description (FCD), TIA/EIA-157, Version 2.6, 13 Jan 2005. 2. SNMS General Requirements, TIA-1073-000, 6/20/2005. 3. Final Draft Digital Video Broadcasting (DVB); Interaction Channel for Satellite Distribution Systems, ETSI EN 3
31、01 790 v1.4.1 (2005-04). 4. Digital Video Broadcasting (DVB); Second generation framing structure, channel coding and modulation systems for Broadcasting, Interactive Services, News Gathering and other broadband satellite applications, ETSI EN 302 307 v1.1.1 (2004-06). 5. Digital Video Broadcasting
32、(DVB); Framing structure, channel coding and modulation for 11/12 GHz satellite services, ETSI EN 300 421. 6. “An IP-based satellite communication system architecture for interactive multimedia services,” N. Iuoras, T. Le-Ngoc, M. Ashour and T. Elshabrawy, International Journal of Satellite Communic
33、ations and Networking, 2003; 21:401-426. 7. Digital Video Broadcasting (DVB); Interaction Channel for Satellite Distribution Systems, Guidelines for use of EN 301 790, ETSI TR 101 790. 8. ITU-T Recommendation Z.100 (08/2002), Specification and Description Language (SDL). 9. ITU-T Recommendation Z.12
34、0 (04/2004), Message Sequence Chart (MSC). 10. Annex J: Example Connection Control Protocol, DVB-RCS TM-RCS0586. 11. Connection Control Protocol (C2P), DVB-RCS TM-RCS0550, Alcatel, 4/2/2005. So called RSM-B protocol. 12. RSM-A Connection Control Protocol, Hughes Network Systems (HNS). viiAcronyms Ta
35、ble i Table of Acronyms and Abreviations Acronym Description AAL ATM Adaptation Layer ACM Adaptive Coding and Modulation ARP Address Resolution Protocol ATM Asynchronous Transfer Mode AVBDC Absolute Volume Based Dynamic Capacity BER Bit Error Rate BUC Block Up-Converter CCM Constant Coding and Modul
36、ation CCP (or C2P) Connection Control Protocol CMT Correction Message Table COS Class of Service CRA Continuous Rate Assignment CRSC Circular Recursive Systematic Convolutional CSC Common Signaling Channel (Burst) DAMA Demand Assignment Multiple Access DHCP Dynamic Host Configuration Protocol DiffSe
37、rv Differentiated Services for IP QoS DULM Data Unit Labeling Method DVB Digital Video Broadcast DVB-S Digital Video Broadcast via Satellite DVB-ASI Digital Video Broadcast-Asynchronous Serial Interface DVB-MPE DVB Multi-Protocol Encapsulation DVB-RCS DVB-Return Channel via Satellite FCA Free Capaci
38、ty Assignment FCT Frame Composition Table FEC Forward Error Correction FLS Forward Link Signaling viiiFTP File Transfer Protocol ICMP Internet Control Message Protocol IGMP Internet Group Management Protocol IP Internet Protocol LSB Least Significant Bit MAC Address Media Access Control Address MF-T
39、DMA Multi-Frequency Time Division Multiple Access MPE Multi-Protocol Encapsulation MPEG Moving Picture Experts Group MPEG-2 Standard for compression and framing, from the MPEG MPEG2-TS MPEG-2 Transport Stream Data Unit MSB Most Significant Bit NAT Network Address Translation NCC Network Control Cent
40、er NCR Network Clock Reference NIT Network Information Table PCR Program Clock Reference PDU Protocol Data Unit PEP Protocol Enhancement Proxy PID Program Identifier or Packet Identifier PSI Program Specific Information RS Reed-Solomon Forward Error Correction mechanism QPSK Quaternary Phase Shift K
41、eying Modulation Technique QoS Quality of Service RBDC Rate-Based Dynamic Capacity RCS Return Channel via Satellite RCST Return Channel Satellite Terminal REF Reference Burst RIP Routing Information Protocol SAC Satellite Access Control SI Service Information SMCP SNMS Mesh Control Protocol ixSNMP S
42、imple Network Management Protocol SNMS Satellite Network Modem System SPT Super-frame Composition Table SYNC Synchronization Burst TBD To Be Determined TBR To Be Reviewed TBS To Be Specified TBTP Terminal Burst Time Plan TCP/IP Transmission Control Protocol for Internet Protocol TCT Timeslot Composi
43、tion Table TDMA Time Division Multiple Access TDM Time Division Multiplexing TIM Terminal Information Message (Table) TIMu TIM unicast TRF Traffic Burst (MPEG2-TS or ATM format) TS Transport Stream UDP/IP User Datagram Protocol/Internet Protocol uimsbf Unsigned integer most significant bit first VBD
44、C Volume-Based Dynamic Capacity VCI Virtual Circuit Identifier VCM Variable Coding and Modulation VPI Virtual Path Identifier 11 Background and Scope When a network employing SNMS modems is configured solely in a hub-spoke configuration, the management and control of network connectivity is centrali
45、zed at the hub, the link layer connections are structurally well-defined, and routing for the network layer is also well-defined. Extension of the SNMS requirements standard to mesh overlay configurations requires development and definition of a broader set of procedures and protocols for connection
46、 control. The need for a connection protocol framework specific to DVB-RCS was identified some time ago in ETSI and DVB groups, and is in the process of being prototyped in the IBIS/AmerHis network. Another similar connection protocol also was developed by a TIA member company for a processed satell
47、ite system. The ETSI/DVB C2P Ref. 10 addresses both regenerative and transponded (transparent) networks, and allows for multipoint/multicast connections. The SNMS is intended only for transponded use. In this document, only unicast (point-to-point) connections will be considered. This document has b
48、een developed using inputs from both ETSI/DVB and TIA member companies . The following terminology equivalencies should be noted: NOCC = NCC (usually located at the hub or Gateway/GW) ST = RCST C2P = CCP = SMCP Mesh transparent network This network is based on an architecture that supports Hub-spoke
49、 and Peer-to-Peer communications using a transparent/transponded satellite. The Hub shall have the capability to transmit DVB/S2 and receive the return channel of DVB-RCS. Similarly, the RCSTs shall have the capability to receive the DVB/S2 signal transmitted by the Hub. In addition, some or all of the RCSTs will have an optional capability to receive DVB-RCS, thus obtaining mesh connectivity. The mesh network is therefore an overlay to the star (or hub-spoke) DVB-RCS ne
