1、 International Telecommunication Union ITU-T Q.3302.1TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (03/2007) SERIES Q: SWITCHING AND SIGNALLING Signalling requirements and protocols for the NGN Resource control protocols Resource control protocol No. 2 Protocol at the Rp interface between transpor
2、t resource control physical entities ITU-T Recommendation Q.3302.1 ITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNALLING SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE Q.1Q.3 INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING Q.4Q.59 FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN Q.60Q.9
3、9 CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS Q.100Q.119 SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 Q.120Q.499 DIGITAL EXCHANGES Q.500Q.599 INTERWORKING OF SIGNALLING SYSTEMS Q.600Q.699 SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 Q.700Q.799 Q3 INTERFACE Q.800Q.849 DIGITAL SUBSCRIBER
4、SIGNALLING SYSTEM No. 1 Q.850Q.999 PUBLIC LAND MOBILE NETWORK Q.1000Q.1099 INTERWORKING WITH SATELLITE MOBILE SYSTEMS Q.1100Q.1199 INTELLIGENT NETWORK Q.1200Q.1699 SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 Q.1700Q.1799 SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL
5、(BICC) Q.1900Q.1999 BROADBAND ISDN Q.2000Q.2999 SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN Q.3000Q.3999 General Q.3000Q.3029 Network signalling and control functional architecture Q.3030Q.3099 Network data organization within the NGN Q.3100Q.3129 Bearer control signalling Q.3130Q.3179 Signall
6、ing and control requirements and protocols to support attachment in NGN environments Q.3200Q.3249 Resource control protocols Q.3300Q.3369 Service and session control protocols Q.3400Q.3499 Service and session control protocols supplementary services Q.3600Q.3649 NGN applications Q.3700Q.3849 Testing
7、 for NGN networks Q.3900Q.3999 For further details, please refer to the list of ITU-T Recommendations. ITU-T Rec. Q.3302.1 (03/2007) i ITU-T Recommendation Q.3302.1 Resource control protocol No. 2 Protocol at the Rp interface between transport resource control physical entities Summary ITU-T Recomme
8、ndation Q.3302.1 specifies the resource connection initiation protocol for use in carrying resource control requests and responses between transport resource control physical entities within the same domain. This protocol is designed to support signalling along a chain of control elements in an oper
9、ators network for a collection of most commonly used QoS models and requirements, including (but not limited to) traffic specification, priority, MPLS labels and Virtual Switching connection information. A multimedia service call traversing the network, which comprises one or more sessions (each hav
10、ing application/user-specific QoS specification), will get desired QoS treatment in the data plane (i.e., the chain of Transport physical entities), through appropriate configuration of the transport physical entities by the transport resource control physical entities. Source ITU-T Recommendation Q
11、.3302.1 was approved on 9 March 2007 by ITU-T Study Group 11 (2005-2008) under the ITU-T Recommendation A.8 procedure. ii ITU-T Rec. Q.3302.1 (03/2007) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Teleco
12、mmunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization As
13、sembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology w
14、hich fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance with
15、 this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory lan
16、guage such as “must“ and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this
17、 Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date
18、of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult t
19、he TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2008 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. ITU-T Rec. Q.3302.1 (03/2007) iii CONTENTS Page 1 Scope 1 2 References. 1 3 Definitions 1 3.1 Ter
20、ms defined elsewhere 1 3.2 Terms defined in this Recommendation. 1 4 Abbreviations and acronyms 2 5 Protocol design principles. 3 5.1 Introduction 3 5.2 Protocol overview. 4 6 Basic protocol operation. 6 6.1 Roles of TRC-PE 6 6.2 REQUEST 7 6.3 MODIFY 8 6.4 AUDIT 8 6.5 NOTIFY . 9 6.6 RELEASE. 9 6.7 T
21、RC-PE source seeking 9 7 Basic procedure 9 7.1 Resource connection establishment 9 7.2 Tear down a resource connection. 10 7.3 Overload control. 10 8 Protocol format . 11 8.1 Common HEADER 11 8.2 RCIP message format. 13 8.3 RCIP object formats . 15 9 Performance considerations 29 9.1 Performance req
22、uirements 29 10 Other issues. 29 10.1 Integrity 29 10.2 Security. 29 10.3 Protocol transport and maintenance . 30 10.4 Connection ID 30 Annex A A cross-reference matrix for objects and messages in Q.3302.1 31 iv ITU-T Rec. Q.3302.1 (03/2007) Page Appendix I An example message flow . 32 I.1 TRC-PE so
23、urce addressing information flows . 32 I.2 Unidirectional QoS path establishment information flows 33 I.3 Bidirectional QoS path establishment information flows 35 Appendix II Element components not supported in RCIP v1. 40 ITU-T Rec. Q.3302.1 (03/2007) 1 ITU-T Recommendation Q.3302.1 Resource contr
24、ol protocol No. 2 Protocol at the Rp interface between transport resource control physical entities 1 Scope This Recommendation defines the resource connection initiation protocol (RCIP) for signalling control information between peer TRC-PEs (Rp interface) in a single operators network. The require
25、ments for the Rp interface are defined in clause 8.6 of ITU-T Y.2111 and in ITU-T Q.Sup51. The possible methods of configuration and notification between the transport physical entities (T-PE) and the transport resource control are out of scope of RCIP. RCIP only specifies the control plane signalli
26、ng among transport resource control physical entities (TRC-PEs) in an operators network. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editi
27、ons indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid
28、 ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T G.805 ITU-T Recommendation G.805 (2000), Generic functional architecture of transport networks. ITU-T Q.2981 ITU-T
29、Recommendation Q.2981 (1999), Broadband integrated services digital network (B-ISDN) and broadband private integrated services network (B-PISN) Call control protocol. ITU-T Q.Sup51 ITU-T Q-series Supplement 51 (2004), Signalling requirements for IP-QoS. ITU-T Y.1291 ITU-T Recommendation Y.1291 (2004
30、), An architectural framework for support of Quality of Service in packet networks. ITU-T Y.2111 ITU-T Recommendation Y.2111 (2006), Resource and admission control functions in Next Generation Networks. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following term defined els
31、ewhere: 3.1.1 connection ITU-T G.805: A “transport entity“ which consists of an associated pair of “unidirectional connections“ capable of simultaneously transferring information in opposite directions between their respective inputs and outputs. 3.2 Terms defined in this Recommendation This Recomme
32、ndation defines the following terms: 3.2.1 bearer: Bearer is a connection for the transport of user plane information between users involved in a communication. (Derived from ITU-T Q.2981) 2 ITU-T Rec. Q.3302.1 (03/2007) 3.2.2 bearer control function (BCF): The BCF is a functional entity that perfor
33、ms the resource and admission control functions. (Derived from ITU-T Q.2981) NOTE BCF is identical to RACF, can be PD-FE, TRC-FE, or both. 3.2.3 upstream TRC-PE: The entity which sends the resource request to a downstream TRC-PE. 3.2.4 destination TRC-PE NOTE The destination TRC-PE receives a resour
34、ce request based on service, sent by the previous hop TRC-PE. When it finds out that the destination IP of the media flow belongs to the TRC-PE domain that is under its administration, if the request is a bidirectional one, the destination TRC-PE will deliver the routing result of the resource path
35、from the destination to the source directly to the edge router, and return the response message of the resource path from the source to the destination to the previous hop TRC-PE. 3.2.5 downstream TRC-PE: The entity which receives the resource request from an upstream TRC-PE. 3.2.6 flow information:
36、 The flow information is the information necessary to identify an IP data flow, as defined in clause 8.3.3. 3.2.7 IP data stream: A sequence of packets sent to convey communication between the two endpoints identified by the flow information. It is an instance of bearer. 3.2.8 RCIP resource connecti
37、on: An RCIP resource connection is a control signalling relationship maintained in all TRC-PEs between (and including) the source TRC-PE and the destination TRC-PE in support of a specific IP data stream. NOTE The messages sent along the RCIP resource connection can carry one or more pieces of resou
38、rce reservation information for that IP data stream. 3.2.9 RCIP transport channel: An RCIP transport channel is a signalling transport connection maintained between two TRC-PE peers, within which multiple RCIP resource connections can be multiplexed. 3.2.10 service control function: The SvCF (servic
39、e control function) is a functional entity that provides value-added service functionality. (Derived from ITU-T Q.Sup51) 3.2.11 session control function: The SeCF (session control function) is a functional entity that provides the call/session control functionality. (Derived from ITU-T Q.Sup51) 3.2.
40、12 source TRC-PE: The source TRC-PE receives a resource request based on service, sent by the PD-PE or the source-seeking TRC-PE from the previous hop. NOTE The source address of the media flow belongs to the TRC-PE domain that is under its administration. 3.2.13 transport physical entity: The T-PE
41、(transport physical entity) is an entity that performs stream classification, switching and forwarding and is capable of enforcing a QoS guarantee. (Derived from ITU-T Q.Sup51) 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: ACCT Accept AUP RCIP AUdit
42、resPonse AUR RCIP AUdit Request BCF Bearer Control Function KA Keep-Alive ITU-T Rec. Q.3302.1 (03/2007) 3 MPLS MultiProtocol Label Switching OVE OVErload indication PD-PE Policy Decision Physical Entity RA Resource Acceptance message RACF Resource Admission Control Functions RCIP Resource Connection
43、 Initiation Protocol REJ resource REJection message RLP Resource reLease resPonse message RLR Resource reLease Request message RR Resource Request message SCE Session/Service Control Entity SF Switching Function T-PE Transport Physical Entity TRC-PE Transport Resource Control Physical Entity 5 Proto
44、col design principles 5.1 Introduction ITU-T Q.Sup51 describes the control information flows between BCFs as shown in Figure 5-1, and ITU-T Y.2111 defines the Rp interface between TRC-FE instances within a domain as shown in Figures 5-1 and 5-2. Separation between data plane (transport functions) an
45、d control plane (bearer control functions, or BCFs) is an important feature in the NGN and RCIP architectures. BCF interacts with border SCEs and interior T-PEs in order to apply resource reservation made in the control plane to achieve the service in the data plane, and to get feedback from T-PEs o
46、r SCEs for (re-)negotiating reservations. The basic protocol architecture for RCIP is shown in Figure 5-1. Q.3302.1(07)_F5-1Service controlSCERsBCFRdPD-PEBCFPD-PE PD-PE PD-PESCEService controlRw RtRpRw RtTRC-PETRC-PE TRC-PE TRC-PERp RpRw Rt RtRwTRC-PE TRC-PERc RnAccesstransportCoretransportCoretrans
47、portSession signallingRi RiAccesstransportRequestingendsystemAddressedend systemRsBCF BCF BCF BCFRc Rn Rc Rn Rc Rn Rc Rn Rc RnFigure 5-1 Basic protocol architecture 4 ITU-T Rec. Q.3302.1 (03/2007) Q.3302.1(07)_F5-2RACFService control functionsNetworkattachmentcontrolfunctionsTRC-FERnService stratumT
48、ransport stratumPE-FEPD-FETRE-FETransport functionsRuRc RwRtRsRiRdRpOtherNGNsFigure 5-2 (Derived from Figure 5/Y.2111) Generic resource and admission control functional architecture in NGN In the IP network, TRC-PE(s) are used to manage all logical bearer networks in all managed areas. In each TRC-P
49、E, the topology and resources in each logical bearer network are recorded and managed respectively. Internally, RCIP maintains a resource connection for the resource reservation from a source T-PE to a destination T-PE. For example, a RCIP resource connection can reserve resource for a multimedia call which has an audio session and a video session. Each RCIP resource connection message contains reservation information or control information related to a RCIP resource connection. It is transported reliab
