1、 International Telecommunication Union ITU-T Q.3304.1TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (06/2012) SERIES Q: SWITCHING AND SIGNALLING Signalling requirements and protocols for the NGN Resource control protocols Resource control protocol No. 4 (rcp4) Protocols at the Rc interface between
2、a transport resource control physical entity and a transport physical entity: COPS alternative Recommendation ITU-T Q.3304.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 FUNCTI
3、ONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN Q.60Q.99 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
4、. 7 Q.700Q.799 Q3 INTERFACE Q.800Q.849 DIGITAL SUBSCRIBER 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
5、 OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (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
6、.3100Q.3129 Bearer control signalling Q.3130Q.3179 Signalling and control requirements and protocols to support attachment in NGN environments Q.3200Q.3249 Resource control protocols Q.3300Q.3369Service and session control protocols Q.3400Q.3499 Service and session control protocols supplementary se
7、rvices Q.3600Q.3649 NGN applications Q.3700Q.3849 Testing for next generation networks Q.3900Q.3999 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T Q.3304.1 (06/2012) i Recommendation ITU-T Q.3304.1 Resource control protocol No. 4 (rcp4) Protocols at the Rc interfa
8、ce between a transport resource control physical entity and a transport physical entity: COPS alternative Summary Recommendation ITU-T Q.3304.1v2 provides the Stage 3 technical specifications for a protocol variant which uses the common open policy service (COPS) (described in IETF RFC 2748) to sati
9、sfy the requirements for information transfer across the Rc reference point, as defined in clause 9.3 of Recommendation ITU-T Y.2111. This protocol allows a transport resource control physical entity (TRC-PE) to collect network topology and resource status information from elements of an access or a
10、 core network. History Edition Recommendation Approval Study Group 1.0 ITU-T Q.3304.1 2007-10-29 11 2.0 ITU-T Q.3304.1 v2 2012-06-15 11 ii Rec. ITU-T Q.3304.1 (06/2012) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunication
11、s, information and communication technologies (ICTs). The ITU Telecommunication 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
12、on a worldwide basis. The World Telecommunication Standardization Assembly (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
13、down in WTSA Resolution 1. In some areas of information technology which 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 telecommunicati
14、on administration and a recognized operating agency. Compliance with 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 mandat
15、ory provisions are met. The words “shall“ or some other obligatory language 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 at
16、tention to the possibility that the practice or implementation of this 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 oth
17、ers outside of the Recommendation development process. As of the date 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 represen
18、t the latest information and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2012 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T Q.3304.1 (06/201
19、2) iii Table of Contents Page 1 Scope 1 2 References. 1 3 Definitions 2 3.1 Terms defined elsewhere 2 3.2 Terms defined in this Recommendation . 2 4 Abbreviations and acronyms 2 5 Conventions 3 6 Resource Control Protocol No. 4 (rcp4) . 3 7 Procedures 3 7.1 Establishment of the COPS session 3 7.2 CO
20、PS session maintenance and termination 3 7.3 Provision of policy by the TRC-PE 3 7.4 Generation of reports by the T-PE 4 8 Application of the policy information base (PIB) 4 8.1 Role of the PIB . 4 8.2 Encoding of the PIB . 4 8.3 Definition of the PIB 4 9 Reference to functional architecture . 4 9.1
21、 Recommendation ITU-T Y.2111 4 10 Security considerations . 5 Annex A Policy information base . 6 A.1 Static description of the PIB . 6 A.2 Usage 6 A.3 Rc Policy Information Base 7 Annex B List of messages imported from IETF RFCs . 14 B.1 IETF RFC 2748 14 Appendix I High-level information flow at Rc
22、 Reference point 15 Bibliography. 16 Rec. ITU-T Q.3304.1 (06/2012) 1 Recommendation ITU-T Q.3304.1 Resource control protocol No. 4 (rcp4) Protocols at the Rc interface between a transport resource control physical entity and a transport physical entity: COPS alternative 1 Scope This Recommendation p
23、rovides the Stage 3 technical specifications for a protocol satisfying the requirements for information transfer across the Rc reference point, as defined in clause 9.3 of ITU-T Y.2111. This protocol allows a transport resource control physical entity (TRC-PE) to collect network topology and resourc
24、e status information from elements of an access or a core network. The normative part of this Recommendation uses or refers to messages which are defined and their behaviours are described in one or more IETF RFCs. To help the users of this Recommendation, a list of all these messages and their orig
25、ins is provided in Annex B. 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 editions indicated were valid. All Recommendations and other refer
26、ences 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 ITU-T Recommendations is regularly published. The reference
27、to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T Q.3300 v2 Recommendation ITU-T Q.3300 v2 (2010), Architectural framework for the Q.33xx series of Recommendations. ITU-T Y.2012 Recommendation ITU-T Y.2012 (2010), Functional r
28、equirements and architecture of next generation networks. ITU-T Y.2111 Recommendation ITU-T Y.2111 (2011), Resource and admission control functions in next generation networks. IETF RFC 2104 IETF RFC 2104 (1997), HMAC: Keyed-Hashing for Message Authentication. IETF RFC 2578 IETF RFC 2578 (1999), Str
29、ucture of Management Information Version 2 (SMIv2). IETF RFC 2748 IETF RFC 2748 (2000), The COPS (Common Open Policy Service) Protocol. IETF RFC 3084 IETF RFC 3084 (2001), COPS Usage for Policy Provisioning (COPS-PR). IETF RFC 3159 IETF RFC 3159 (2001), Structure of Policy Provisioning Information (
30、SPPI). IETF RFC 3318 IETF RFC 3318 (2003), Framework Policy Information Base. IETF RFC 4001 IETF RFC 4001 (2005), Textual Conventions for Internet Network Addresses. 2 Rec. ITU-T Q.3304.1 (06/2012) 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following terms defined elsewhe
31、re: 3.1.1 client handle IETF RFC 2748: A term used to identify a unique request state for a single PEP per client-type. 3.1.2 policy information base (PIB) IETF RFC 3084: A term used to identify the type and purpose of unsolicited policy information that is “pushed“ from the PDP to the PEP for provi
32、sioning policy or sent to the PDP from the PEP as a notification. 3.1.3 transport physical entity (T-PE) ITU-T Q.3300 v2: A term used to refer to any device implementing the transport functions in the limited sense provided in clause 7.2.4 of ITU-T Y.2111 (i.e., those with which the RACF interacts).
33、 3.1.4 transport resource control physical entity (TRC-PE) ITU-T Q.3300 v2: A device that implements the transport resource control functional entity (TRC-FE) as defined in clause 7.2.3.3 of ITU-T Y.2111. 3.2 Terms defined in this Recommendation This Recommendation defines the following term: 3.2.1
34、session: The term “session“ used in this Recommendation refers to a common open policy service (COPS) signalling relationship established between the TRC-PE acting in the role of a COPS policy decision point (PDP) and the T-PE of acting in the role of a COPS policy enforcement point (PEP). 4 Abbrevi
35、ations and acronyms This Recommendation uses the following abbreviations and acronyms: COPS Common Open Policy Service COPS-PR COPS usage for policy provisioning DEC COPS DECision message DEC Install COPS DECision Install message DEC Remove COPS DECision Remove message Diffserv Differentiated Servic
36、es model DRE Data Relay Entity HMAC keyed-Hashing for Message Authentication LSP Label Switched Path MPLS MultiProtocol Label Switching PDP Policy Decision Point PEP Policy Enforcement Point PIB Policy Information Base PRC Provisioning Class PRI Provisioning Instance PRID Provisioning Instance Ident
37、ifier Rec. ITU-T Q.3304.1 (06/2012) 3 QoS Quality of Service REQ COPS Request message RPT COPS Report state message TCP Transmission Control Protocol TLS Transport Layer Security T-PE Transport Physical Entity TRC-PE Transport Resource Control Physical Entity VSWITCH Virtual Switches 5 Conventions N
38、one. 6 Resource Control Protocol No. 4 (rcp4) This variant of the Rc Stage 3 definition uses the COPS protocol, and in particular the COPS-PR procedures and data models defined in IETF RFC 3084. The COPS protocol is a request/response protocol intended to operate in the Client/Server mode. The T-PE
39、serves as the policy enforcement point (PEP) and Client and the TRC-PE as the policy decision point (PDP) and Server. COPS implementations supporting this Recommendation shall support the COPS client type 0x800d (ITUT-RcPIB) and shall support the policy information base (PIB) defined in Annex A. 7 P
40、rocedures 7.1 Establishment of the COPS session The T-PE shall initiate a TCP connection and open a COPS session with the TRC-PE as described in IETF RFC 2748. To establish an Rc session, the T-PE shall send a Client-Open message with the client identifier 0x800d (ITUT-RcPIB). The TRC-PE shall respo
41、nd with a Client-Accept message for that client type. State synchronization may proceed as described in sections 2.5 of IETF RFC 2748 and 3.1 of IETF RFC 3084. The client handle within the REQ message is of local significance to the T-PE. This Recommendation does not specify use of a ClientSI object
42、 within the Client-Accept message. 7.2 COPS session maintenance and termination The T-PE and TRC-PE shall use the Keep-Alive procedures defined in IETF RFC 2748 to ensure the continued availability of the COPS session. The session shall be terminated only by the loss of availability of one of the pe
43、ers through failure or management action. 7.3 Provision of policy by the TRC-PE The TRC-PE shall provide policy to the T-PE to indicate what information the TRC-PE wishes to acquire, using the contents of Named Decision objects within COPS-PR DEC messages. A DEC message must be returned in response
44、to a REQ message from the T-PE. The TRC-PE may also send further DEC messages as required to modify previously set policy or collect additional information on a one-time basis. Details are provided in clause A.2. 4 Rec. ITU-T Q.3304.1 (06/2012) 7.4 Generation of reports by the T-PE The T-PE shall pr
45、ovide information to the TRC-PE as determined by the policy installed by the DEC messages it receives. This information is provided within instances of the Named ClientSI object within COPS Report-State (RPT) messages. Details are given in clause A.2. 8 Application of the policy information base (PI
46、B) 8.1 Role of the PIB The policy information base (PIB) provides a means to interwork between different product vendors. The PIB defines a collection of provisioning classes (PRC) which can be used by the COPS to request or pass data instances (i.e., PRIs) for any given data structure (i.e., PRC).
47、Instances of the policy classes (i.e., PRIs) are each identified by a provisioning instance identifier (PRID) in the PIB. (A PIB is just like a virtual database of the PRC.) This Recommendation defines a PIB and inherits part of the data definitions from other PIBs, including PIBs in IETF RFC 3159,
48、IETF RFC 3318 and IETF RFC 4001. 8.2 Encoding of the PIB ASN.1 BER shall be used to encode the provisioning instance identifier (PRID) and policy data as described in section 2.2.1 of IETF RFC 3084. 8.3 Definition of the PIB See clauses A.1 and A.3 for details. 9 Reference to functional architecture
49、 9.1 Recommendation ITU-T Y.2111 The protocol defined in this Recommendation (i.e., rcp4) operates across the Rc reference point as defined in ITU-T Y.2111. The realization presented in this Recommendation accepts the considerations of scalability and domain independence that motivated the development of the functional architecture as defined in ITU-T Y.2111. As a result, it maps each functional entity of the functional architecture to a separate type of physical entity. Fi
