1、 International Telecommunication Union ITU-T Q.3308.1TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (03/2012) SERIES Q: SWITCHING AND SIGNALLING Signalling requirements and protocols for the NGN Resource control protocols Resource control protocol No. 8 Protocol at the interface between a policy de
2、cision physical entity and a customer premises network gateway policy enforcement physical entity (Rh interface): COPS alternative Recommendation ITU-T Q.3308.1 ITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNALLING SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE Q.1Q.3 INTERNATIONAL AUTOMATIC AND S
3、EMI-AUTOMATIC WORKING Q.4Q.59 FUNCTIONS 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 SP
4、ECIFICATIONS OF SIGNALLING SYSTEM No. 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
5、IMT-2000 Q.1700Q.1799 SPECIFICATIONS 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 Networ
6、k data organization within the NGN Q.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 sessio
7、n control protocols supplementary services 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.3308.1 (03/2012) i Recommendation ITU-T Q.3308.1 Resource control protocol No.
8、8 Protocol at the interface between a policy decision physical entity and a customer premises network gateway policy enforcement physical entity (Rh interface): COPS alternative Summary Recommendation ITU-T Q.3308.1 specifies the rcp8 protocol used between a policy decision physical entity (PD-PE) a
9、nd a customer premises network gateway policy enforcement physical entity (CGPE-PE). This interface was defined in Recommendation ITU-T Y.2111. The interface can be supported in direct mode and the interaction for resource and admission control between PD-PE and CGPE-PE. History Edition Recommendati
10、on Approval Study Group 1.0 ITU-T Q.3308.1 2012-03-29 11 ii Rec. ITU-T Q.3308.1 (03/2012) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication
11、 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 Assembly (WTS
12、A), 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 which fall w
13、ithin 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 this Recom
14、mendation 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 language suc
15、h 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 Recommen
16、dation 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 of approv
17、al 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 the TSB pa
18、tent 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.3308.1 (03/2012) iii Table of Contents Page 1 Scope 1 2 References. 1 3 Definitions 1 3.1 Ter
19、ms defined elsewhere 1 3.2 Terms defined in this Recommendation . 2 4 Abbreviations and acronyms 2 5 Conventions 3 6 Rh interface . 3 6.1 Overview 3 6.2 Rh reference model . 3 6.3 Functional elements and capabilities 4 7 Resource control procedures. 4 7.1 Procedures at the PD-PE 4 8 Procedures at th
20、e CGPE-PE . 6 8.1 Session initiation 6 8.2 Session modification 6 8.3 Session termination 6 9 Protocol specifications 6 9.1 Protocol support 6 9.2 COPS basic message 7 9.3 Resource management information 7 10 Message specifications . 8 10.1 Request (CGPE-PE PD-PE) 8 10.2 Decision (PD-PE CGPE-PE) . 8
21、 10.3 Report (CGPE-PE PD-PE) 8 10.4 Delete request State (CGPE-PE PD-PE) . 8 11 Security considerations . 8 Annex A Rh policy information base . 9 Annex B List of messages imported from IETF RFCs . 41 B.1 IETF RFC 2748 41 B.2 IETF RFC 3084 41 Appendix I Examples of procedures of the Rh interface for
22、 resource reservation and modification 42 I.1 Use case for the Rh interface . 42 Appendix II Rh Stage 1 message to COPS message mapping . 45 Bibliography. 46 Rec. ITU-T Q.3308.1 (03/2012) 1 Recommendation ITU-T Q.3308.1 Resource control protocol No. 8 Protocol at the interface between a policy decis
23、ion physical entity and a customer premises network gateway policy enforcement physical entity (Rh interface): COPS alternative 1 Scope This Recommendation specifies the protocol used between a policy decision physical entity (PD-PE) and a customer premises network (CPN) gateway policy enforcement p
24、hysical entity (CGPE-PE). The functional requirements of the Rh interface are contained in ITU-T Y.2111. The Rh interface between a PD-PE in the access network and a CGPE-PE can be handled by quality of service (QoS) resource control modes, such as push mode and pull mode. That is, the Rh interface
25、allows the final admission decisions to be installed (either pushed or pulled) to the CGPE-PE from the PD-PE. The normative part of this Recommendation uses or refers to messages which are defined, and whose behaviours are described, in one or more IETF RFCs. To help the users of this Recommendation
26、, a list of all these messages and their origins are 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 w
27、ere 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 ITU-T Recommen
28、dations 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 Q.3300 v2 Recommendation ITU-T Q.3300 v2 (2010), Architectural framework for the Q.33xx series of Recommendations. ITU-T Y.2012 Re
29、commendation ITU-T Y.2012 (2010), Functional requirements 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 2748 IETF RFC 2748 (2000), The COPS (Common Open Policy Service) Pro
30、tocol. IETF RFC 3084 IETF RFC 3084 (2001), COPS Usage for Policy Provisioning (COPS-PR). 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 COPS connection b-ITU-T Q.3303.1: A COPS signalling relationship established between the PD-PE acti
31、ng in the role of a COPS Policy Decision Point (PDP) and the CGPE-PE acting in the role of a COPS Policy Enforcement Point (PEP). 3.1.2 policy decision physical entity (PD-PE) b-ITU-T Q.3303.1: The PD-PE is an implemented instance of the policy decision functional entity (PD-FE) as defined in ITU-T
32、Y.2111. 2 Rec. ITU-T Q.3308.1 (03/2012) 3.1.3 flow ID b-ITU-T Q.3303.1: It is an identifier for the individual media flow within a session. Usually the Flow ID is created by the PD-PE. 3.1.4 flow information b-ITU-T Q.3303.1: It describes the features of the media flow (e.g., filter and filter statu
33、s). 3.2 Terms defined in this Recommendation This Recommendation defines the following term: 3.2.1 CPN gateway policy enforcement physical entity (CGPE-PE): The CGPE-PE is an implemented instance of the customer premises network (CPN) gateway policy enforcement functional entity (CGPE-FE) as defined
34、 in ITU-T Y.2111. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: CAT Client Accept CC Client Close CGPE-PE CPN Gateway Policy Enforcement Physical Entity COPS Common Open Policy Service COPS-PR COPS Usage for Policy Provisioning CPE Customer Premises
35、Equipment CPN Customer Premises Network DEC Decision DiffServ Differentiated Services DRQ Delete Request state DSCP Differentiated Services Code Point IP Internet Protocol KA Keep Alive NACE Network Attachment Control Entity OPN client Open PD-PE Policy Decision Physical Entity PIB Policy Informatio
36、n Base PRC Provisioning Class PRI Provisioning Instance QinQ 802.1Q in 802.1Q QoS Quality of Service RACF Resource and Admission Control Functions REQ Request RIP Resource Initiation Response RIR Resource Initiation Request RMR Resource Modification Request Rec. ITU-T Q.3308.1 (03/2012) 3 RPT Report
37、 state SCE Service Control Entity SLA Service Level Agreement SSC Synchronize Complete SSQ Synchronize State Request TOS Type of Service T-PE Transport Physical Entity TRC-PE Transport Resource Control Physical Entity TRE-PE Transport Resource Enforcement Physical Entity VLAN Virtual Local Area Netw
38、ork 5 Conventions None. 6 Rh interface 6.1 Overview The Rh reference point is used for interaction between a policy decision physical entity (PD-PE) and a CPN gateway policy enforcement physical entity (CGPE-PE). The interface is defined in ITU-T Y.2111. The Rh reference point allows the final admis
39、sion decisions to be installed or uninstalled to the CGPE-PE from the PD-PE. 6.2 Rh reference model Figure 6-1 shows the Rh reference model. Figure 6-1 Overall architecture of the Rh interface 4 Rec. ITU-T Q.3308.1 (03/2012) 6.3 Functional elements and capabilities 6.3.1 Policy decision physical ent
40、ity (PD-PE) The PD-PE is a physical element that coordinates a resource reservation request received from the service control entity (SCE). The PD-PE makes policy decisions using network resource and admission control based on network policy rules and service level agreements (SLAs). 6.3.2 CPN gatew
41、ay policy enforcement physical entity (CGPE-PE) The CGPE-PE is a physical element that enforces the network policy rules instructed by the PD-PE in the access network via the Rh interface. The CGPE-PE should be able to support the opening and closing gate; rate limiting and bandwidth allocation; tra
42、ffic classification and marking; traffic policing and shaping; mapping of the Internet Protocol (IP) layer QoS information onto link layer QoS information based on pre-defined static policy rules; collecting and reporting resource usage information; etc. 7 Resource control procedures 7.1 Procedures
43、at the PD-PE 7.1.1 Resource initiation 7.1.1.1 Transport subscription profile verification The Rh interface allows the PD-PE to push policy decisions to the CGPE-PE. The PD-PE verifies the transport profile received from the network attachment control entity (NACE). Thus, the PD-PE acquires the QoS
44、class, priority of reservation, and maximum and/or minimum uplink and downlink bandwidth. 7.1.1.2 Transport resource detection and admission The PD-PE is required to confirm transport resources availability to the transport resource control (TRC)-PE. The PD-PE is required to make policy decisions ba
45、sed on the confirmation result from the TRC-PE. 7.1.1.3 Initial policy decisions The PD-PE makes initial policy decisions for IP flows by the resource initiation request from the SCE based on all information, including: Service information received from the SCE. Transport subscription information fr
46、om the PD-PE. Transport subscription profiles. Service based network policies. Transport resource availability and admission decision information received from the TRC-PE. In order to support the policy decision, the following information shall be contained in the policy decisions. IP media flow des
47、cription The uplink and downlink packet classifiers from the IP addresses and port numbers provided by the SCE shall be derived from the PD-PE. Rec. ITU-T Q.3308.1 (03/2012) 5 Transport subscription information The transport subscription information includes QoS parameter for L2 (layer 2) packet mar
48、king and handling in CGPE-PE (e.g., 802.1p). It can be derived from the network QoS parameters and transport subscription information by the PD-PE. QoS information The QoS information includes QoS class based on the requested service type and bandwidth requirements. The QoS information for IP media
49、flows is extracted from the media profile (e.g., type of service (TOS), traffic class, media priority and bandwidth) received from the SCE. Also, it can be derived from the network QoS parameters and transport subscription information by the PD-PE. A QoS parameter for L2 packet marking and handling can be used in CGPE-PE (e.g., 802.1p). The PD-PE may select the QoS class for the media, and the PD-PE shall use the same QoS class for both links (uplink and downlink) when both di
