1、 International Telecommunication Union ITU-T Q.3306.1TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (10/2009) SERIES Q: SWITCHING AND SIGNALLING Signalling requirements and protocols for the NGN Resource control protocols Resource control protocol no. 6 (rcp6) Protocol at the interface between intr
2、a-domain policy decision physical entities (PD-PE) (Rd interface) Recommendation ITU-T Q.3306.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
3、 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. 7 Q.700Q.799 Q3 INTERFACE Q
4、.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 OF SIGNALLING RELATED TO BEA
5、RER 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.3100Q.3129 Bearer control si
6、gnalling 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 services Q.3600Q.3649 NGN appli
7、cations Q.3700Q.3849 Testing for NGN networks Q.3900Q.3999 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T Q.3306.1 (10/2009) i Recommendation ITU-T Q.3306.1 Resource control protocol no. 6 (rcp6) Protocol at the interface between intra-domain policy decision physi
8、cal entities (PD-PE) (Rd interface) Summary Recommendation ITU-T Q.3306.1 specifies the rcp6 protocol used between intra-domain policy decision physical entities (PD-PEs) in the resource and admission control functional block. This interface operates across the Rd reference point as defined in Recom
9、mendation ITU-T Y.2111. It is used for inter-communication between PD-PEs that can optionally be deployed in larger domains for scalability reasons. Source Recommendation ITU-T Q.3306.1 was approved on 29 October 2009 by ITU-T Study Group 11 (2009-2012) under Recommendation ITU-T A.8 procedures. Key
10、words Diameter, RACF, Rd interface, Resource control. ii Rec. ITU-T Q.3306.1 (10/2009) 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 St
11、andardization 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 (WTSA),
12、 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 with
13、in 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 Recommen
14、dation 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 such as
15、“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 Recommendatio
16、n 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 approval of
17、 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 patent
18、database at http:/www.itu.int/ITU-T/ipr/. ITU 2010 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.3306.1 (10/2009) iii CONTENTS Page 1 Scope 1 2 References. 1 3 Definitions 2 3.1 Terms defined els
19、ewhere 2 3.2 Terms defined in this Recommendation . 2 4 Abbreviations and acronyms 2 5 Conventions 2 6 Rd interface . 3 6.1 Overview 3 6.2 Functional elements and capabilities 3 6.3 Rd interface protocol 4 7 Procedures 4 7.1 Initial reservation for a session . 4 7.2 Session modification 7 7.3 Sessio
20、n termination 8 7.4 PD-PE notifications 8 8 Protocol specifications 9 9 Messages specifications 9 9.1 Commands 9 9.2 Experimental-Result-Code AVP values . 9 9.3 Attribute-Value Pairs (AVPs) . 10 10 Security considerations . 11 Rec. ITU-T Q.3306.1 (10/2009) 1 Recommendation ITU-T Q.3306.1 Resource co
21、ntrol protocol no. 6 (rcp6) Protocol at the interface between intra-domain policy decision physical entities (PD-PE) (Rd interface) 1 Scope This Recommendation specifies the protocol used between intra-domain policy decision physical entities (PD-PEs) in the resource and admission control functional
22、 block. The functional requirements of the Rd interface are contained in clause 8.8 of ITU-T Y.2111. The Rd interface is the interface between intra-domain PD-PEs. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitu
23、te provisions of this Recommendation. At the time of publication, the editions 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 Recom
24、mendations and other references listed below. A list of the currently valid 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 Q.3300 Recommendation ITU-T Q.3300 (2008
25、), Architectural framework for the Q.33xx series of Recommendations. ITU-T Q.3301.1 Recommendation ITU-T Q.3301.1 (2007), Resource control protocol No. 1 Protocol at the Rs interface between service control entities and the policy decision physical entity. ITU-T Y.2111 Recommendation ITU-T Y.2111 (2
26、008), Resource and admission control functions in next generation networks. ETSI TS 129 209 ETSI TS 129 209 V6.7.0 (2007), Universal Mobile Telecommunications System (UMTS); Policy control over Gq interface (3GPP TS 29.209 version 6.7.0 Release 6). ETSI TS 129 329 ETSI TS 129 329 V8.3.0 (2009), Digi
27、tal cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Sh interface based on the Diameter protocol; Protocol details (3GPP TS 29.329 version 8.3.0 Release 8). ETSI TS 183 017 ETSI TS 183 017 V2.3.1 (2008), Telecommunications and Internet converged Servi
28、ces and Protocols for Advanced Networking (TISPAN); Resource and Admission Control: DIAMETER protocol for session-based policy set-up information exchange between the Application Function (AF) and the Service Policy Decision Function (SPDF); Protocol specification. ETSI ES 283 026 ETSI ES 283 026 V2
29、.4.1 (2008), Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN);Resource and Admission Control; Protocol for QoS reservation information exchange between the Service Policy Decision Function (SPDF) and the Access-Resource and Admission Control Function
30、(A-RACF) in the Resource and Protocol specification. 2 Rec. ITU-T Q.3306.1 (10/2009) ETSI ES 283 034 ETSI ES 283 034 V2.2.0 (2008), Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Network Attachment Sub-System (NASS); e4 interface based on the DIAME
31、TER protocol. IETF RFC 3588 IETF RFC 3588 (2003), Diameter Base Protocol. IETF RFC 4005 IETF RFC 4005 (2005), Diameter Network Access Server Application. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following term defined elsewhere: 3.1.1 policy decision physical entity (PD
32、-PE) ITU-T Q.3300: A device that implements the policy decision functional entity (PD-FE) as defined in clause 7.2.3.2 of ITU-T Y.2111. 3.2 Terms defined in this Recommendation This Recommendation does not define any terms. 4 Abbreviations and acronyms This Recommendation uses the following abbrevia
33、tions and acronyms: AAA AA-Answer AAR AA-Request AVP Attribute-Value Pair CPN Customer Premises Network NAPT Network Address and Port Translation NAT Network Address Translation PD-PE Policy Decision Physical Entity PE-PE Policy Enforcement Physical Entity RAA Re-Auth-Answer RAC-PE Resource and Admi
34、ssion Control Physical Entity RAR Re-Auth-Request SCE Service Control Entity SDI Session Description Information STA Session Termination Answer STR Session Termination Request TRC-PE Transport Resource Control Physical Entity TRE-PE Transport Resource Enforcement Physical Entity 5 Conventions There
35、are no specific conventions in this Recommendation. Rec. ITU-T Q.3306.1 (10/2009) 3 6 Rd interface 6.1 Overview The Rd interface is defined in ITU-T Y.2111 and is used between intra-domain PD-PEs in the resource and admission control physical entity (RAC-PE). It is used for inter-communication betwe
36、en PD-PEs that can optionally be deployed in larger domains for scalability reasons. The Rd interface is shown in Figure 6-1, which depicts the generic resource and admission control functional architecture in NGN. It is based on Figure 5 of ITU-T Y.2111, with the following modifications: “Service c
37、ontrol functions“ is replaced by “Service control entity“, “Network attachment control functions“ is replaced by “Network attachment control entity“, CGPE-FE is replaced by CGPE-PE, PD-FE is replaced by PD-PE, TRC-FE is replaced by TRC-PE, TRE-FE is replaced by TRE-PE, PE-FE is replaced by PE-PE, RA
38、CF is replaced by RAC-PE. Q.3306.1(09)_F6.1RAC-PEService control entity (SCE)NetworkattachmentcontrolentityTRC-PERnService stratumTransport stratumPE-PEPD-PETRE-PETransport physical entityRuRc RwRtRsRiRdRpOtherNGNsCGPE-PECPNRhScope of this RecommendationFigure 6-1 Generic resource and admission cont
39、rol functional architecture in NGN 6.2 Functional elements and capabilities The PD-PE communicates with the service control entity (SCE) over the Rs interface and interacts across the Rd interface with other PD-PEs within the same network domain. In the case where multiple PD-PEs are deployed, each
40、one can handle a subset of the PE-PEs. If the PD-PE which receives a request over the Rs interface (i.e., the originating PD-PE) is not able to directly reach the targeted PE-PE, because of the network configuration, the originating PD-PE needs to communicate internally over Rd with an intra-domain
41、peer PD-PE to reach the requested PE-PE. Detailed information about the PD-PE implementation can be found in clause 6.3 of ITU-T Q.3300. An example configuration of multiple PD-PEs is shown in Figure 2 of ITU-T Q.3300. 4 Rec. ITU-T Q.3306.1 (10/2009) 6.3 Rd interface protocol Diameter IETF RFC 3588
42、is the base protocol used for the PD-PEs interconnection via the Rd interface. 7 Procedures 7.1 Initial reservation for a session 7.1.1 Procedures at the originating PD-PE The originating PD-PE performs the admission control based on requirements from the SCE. The originating PD-PE requests an autho
43、rization for the session from the intra-domain peer PD-PE by sending the AA-Request (AAR) message. It is required that this AAR message contain a new Session-Id. The AAR message can optionally contain an Authorization-Lifetime attribute-value pair (AVP) to indicate the maximum lifetime that it is re
44、questing. The AAR message can optionally include an Auth-Session-State AVP to indicate the originating PD-PEs preference for stateful or stateless operation. The originating PD-PE can optionally include the Operation-Indication AVP to indicate the following operations after receiving the AAR message
45、: the peer PD-PE must perform NAPT control and NAT traversal functions, or QoS resource reservation, or both. The originating PD-PE is required to include the corresponding Media-Component-Description AVP(s) into the AAR message, if the session description information (SDI) is already available. The
46、 originating PD-PE can optionally include the Flow-Grouping AVP(s) to request a particular grouping for the IP flows described within the SDI. When providing a given Media-Component-Description AVP in the initial AAR message, the originating PD-PE can optionally request the intra-domain peer PD-PE t
47、o commit the requested resources by setting the Flow-Status AVP to the value ENABLED, ENABLED-UPLINK or ENABLED-DOWNLINK. Alternatively, the originating PD-PE can optionally perform resource allocation in two phases using separate reserve and commit operations. If commitment is done in two phases, t
48、he Flow-Status AVP value of the initial AAR message is required to be set to DISABLED. If, based on local configuration data, the originating PD-PE determines that address translation needs to occur on the user plane (e.g., the PE-PE implements NAT, or NAPT, or the hosted NAPT procedure), the follow
49、ing action is performed: after the originating PD-PE receives an SDI that is associated with the end-point served by it, the originating PD-PE is required to include the Binding-Information AVP with the Input-List AVP. The originating PD-PE optionally includes the SDP-Direction AVP along with the Binding-Information AVP. These indicate whether the address set in the Output-list AVP is expected to be received in the AAA message in either of the following: th
