ITU-T Q 3305 1-2011 Resource control protocol No 5 (rcp5) C Protocol at the interface between transport resource control physical entity and policy decision physical entity (Rt int.pdf

1、 International Telecommunication Union ITU-T Q.3305.1TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (06/2011) SERIES Q: SWITCHING AND SIGNALLING Signalling requirements and protocols for the NGN Resource control protocols Resource control protocol No. 5 (rcp5) Protocol at the interface between tran

2、sport resource control physical entity and policy decision physical entity (Rt interface): Diameter-based Recommendation ITU-T Q.3305.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.4

3、Q.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 SPECIFICATIONS OF SIGNALLIN

4、G 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 IMT-2000 Q.1700Q.1799 SPE

5、CIFICATIONS 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 withi

6、n 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 session control protocols suppl

7、ementary services Q.3600Q.3649 NGN applications 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.3305.1 (06/2011) i Recommendation ITU-T Q.3305.1 Resource control protocol No. 5 (rcp5) Protocol at the interface be

8、tween transport resource control physical entity and policy decision physical entity (Rt interface): Diameter-based Summary Recommendation ITU-T Q.3305.1 specifies a protocol to be used between the physical implementation of the transport resource control functional entity (TRC-FE) and the policy de

9、cision physical entity (PD-PE) of a transport network, defined as the Rt reference point in Recommendation ITU-T Y.2111. It is used to control network transport resources required to convey the media flow in an access or a core network. History Edition Recommendation Approval Study Group 1.0 ITU-T Q

10、.3305.1 2008-05-22 11 2.0 ITU-T Q.3305.1 v2 2011-06-29 11 Keywords RACF, resource control, Rt interface. ii Rec. ITU-T Q.3305.1 (06/2011) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communicatio

11、n 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 on a worldwide basis. The World

12、 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 down in WTSA Resolution 1. In s

13、ome 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 telecommunication administration and a recogni

14、zed 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 mandatory provisions are met. The wor

15、ds “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 attention to the possibility that

16、 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 others outside of the Recommendati

17、on 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 represent the latest information and ar

18、e 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.3305.1 (06/2011) iii Table of Contents Page 1

19、 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 4 6 Rt interface 4 6.1 Overview 4 6.2 Functional elements and capabilities 5 6.3 Rt interface protocol . 5 7 Resource control procedures. 5

20、 8 Rt protocol 6 8.1 Protocol support 6 8.2 Use of the Diameter base protocol . 6 8.3 Rt messages 7 8.4 Experimental-Result-Code AVP values . 11 8.5 AVPs . 11 9 Security considerations . 20 Appendix I Resource reservation flow states maintained by RAC-PE . 21 Bibliography. 23 Rec. ITU-T Q.3305.1 (06

21、/2011) 1 Recommendation ITU-T Q.3305.1 Resource control protocol No. 5 (rcp5) Protocol at the interface between transport resource control physical entity and policy decision physical entity (Rt interface): Diameter-based 1 Scope This Recommendation provides the stage 3 specification of the Rt inter

22、face (rcp5). The Rt protocol is used between the policy decision physical entity (PD-PE) and the transport resource control physical entity (TRC-PE) in the resource and admission control functional block. The Rt interface provides the ability for the PD-PE to request the TRC-PE entities in the invol

23、ved networks to detect and determine the requested QoS resource for a given media flow. The PD-PE may also request the TRC-PE to provide the path selection information for a given flow in the core network. The functional requirements corresponding to this interface are contained in clause 8.5 of ITU

24、-T Y.2111 and in ITU-T Q-Sup.51. 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

25、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 Recommendations is regularly published. The refer

26、ence to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T Q.3320 Recommendation ITU-T Q.3320 (2010), Architectural framework for the Q.332x series of Recommendations. ITU-T Q.3321.1 Recommendation ITU-T Q.3321.1 (2010), Resource

27、control protocol No. 1, version 2 Protocol at the Rs interface between service control entities and the policy decision physical entity. ITU-T Q-Sup.51 ITU-T Q-series Recommendations Supplement 51 (2004), Signalling Requirements for IP-QoS. ITU-T Y.2111 Recommendation ITU-T Y.2111 (2008), Resource a

28、nd admission control functions in next generation networks. ETSI TS 129 209 ETSI TS 129 209 V6.7.0 (2007-06), Universal Mobile Telecommunications System (UMTS); Policy control over Gq interface (3GPP TS 29.209 version 6.7.0 Release 6). ETSI TS 183 017 ETSI TS 183 017 V2.3.1 (2008-09), Telecommunicat

29、ions and Internet converged Services 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. E

30、TSI ES 283 026 ETSI ES 283 026 V2.4.1 (2008-11), Telecommunications and Internet converged Services and Protocols for Advanced Networks (TISPAN); Resource and Admission Control; Protocol for QoS reservation information exchange between the Service Policy Decision Function (SPDF) and the Access-Resou

31、rce and Admission Control Function (A-RACF) in the Resource and Protocol specification. 2 Rec. ITU-T Q.3305.1 (06/2011) ETSI ES 283 034 ETSI ES 283 034 V2.2.0 (2008-07), Telecommunications and Internet converged Services and Protocols for Advanced Networks (TISPAN); Network Attachment Sub-System (NA

32、SS); e4 interface based on the DIAMETER protocol. IETF RFC 3588 IETF RFC 3588 (2003), Diameter Base Protocol. IETF RFC 4005 IETF RFC 4005 (2005), Diameter Network Access Server Application. IETF RFC 4301 IETF RFC 4301 (2005), Security Architecture for the Internet Protocol. 3 Definitions 3.1 Terms d

33、efined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 attribute-value pair (AVP) IETF RFC 3588: The Diameter protocol consists of a header followed by one or more Attribute-Value-Pairs (AVPs). An AVP includes a header and is used to encapsulate protocol-specific data

34、 (e.g., routing information) as well as authentication, authorization or accounting information. 3.1.2 flow identifier b-ETSI TS 129 207: Used for the identification of the IP flows, described within a media component associated with an AF session. NOTE A flow identifier consists of two parts: 1) th

35、e ordinal number of the position of the media component description in the session description information and 2) the ordinal number of the IP flow(s) within the media component description assigned in the order of increasing port numbers. 3.2 Terms defined in this Recommendation This Recommendation

36、 defines the following terms: 3.2.1 hard-state reservation: A type of reservation whereby the requested resources are reserved without time limit. Hard-state reservations are terminated when the DIAMETER session is terminated. 3.2.2 SCE session: A session established by a service or session control

37、signalling protocol offered by the service control entity (SCE) that requires a session set-up with explicit session description before the use of the service. NOTE One example of a service control entity (SCE) session is an IP multimedia subsystem (IMS) session. 3.2.3 SCE session signalling protoco

38、l: The signalling protocol used to control the service control entity (SCE) session. NOTE One example of an SCE session signalling protocol is session initiation protocol (SIP) with session description protocol (SDP). 3.2.4 soft-state reservation: A type of reservation whereby the requested resource

39、s are reserved for a finite amount of time. Soft-state reservations are terminated when the DIAMETER session is terminated. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: AAA AA-Answer AAR AA-Request AF Application Function Rec. ITU-T Q.3305.1 (06/201

40、1) 3 A-RACF Access Resource and Admission Control Function ASA Abort-Session-Answer ASR Abort-Session-Request ATM Asynchronous Transfer Mode AVP Attribute-Value Pair CEA Capabilities-Exchange-Answer CER Capabilities-Exchange-Request CGPE-FE CPN Gateway Policy Enforcement Functional Entity CGPE-PE CP

41、N Gateway Policy Enforcement Physical Entity CPN Customer Premises Network IANA Internet Assigned Numbers Authority IMS IP Multimedia Subsystem IP-CAN IP-Connectivity Access Network IPSec Internet Protocol Security NAS Network Access Server NGN Next Generation Networks PD-FE Policy Decision Function

42、al Entity PD-PE Policy Decision Physical Entity PE-FE Policy Enforcement Functional Entity PE-PE Policy Enforcement Physical Entity QoS Quality of Service RAA Re-Auth-Answer RACF Resource and Admission Control Function RAC-PE Resource and Admission Control Physical Entity RAR Re-Auth-Request RTCP Re

43、al-time Transport Control Protocol RTP Real-time Transport Protocol SCE Service Control Entity SCTP Stream Control Transport Protocol SDI Session Description Information SDP Session Description Protocol SIP Session Initiation Protocol SPDF Service-based Policy Decision Function STA Session-Terminati

44、on-Answer STR Session-Termination-Request TRC-FE Transport Resource Control Functional Entity TRC-PE Transport Resource Control Physical Entity 4 Rec. ITU-T Q.3305.1 (06/2011) TRE-FE Transport Resource Enforcement Functional Entity TRE-PE Transport Resource Enforcement Physical Entity UE User Equipm

45、ent VC Virtual Channel 5 Conventions None. 6 Rt interface 6.1 Overview The Rt interface is used between the policy decision functional entity (PD-PE) and the transport resource control functional entity (TRC-PE) in the resource and admission control physical entity (RAC-PE) to control network transp

46、ort resources required to convey the media flow. It is utilized by the PD-PE to request the TRC-PE entities in the involved networks to detect and determine the requested QoS resource for a given media flow and to provide the path selection information for a given flow in the core network. The Rt in

47、terface and functional requirements corresponding to this interface are defined in clause 8.5 of ITU-T Y.2111 and in ITU-T Q-Sup.51. The Rt interface localization is shown on Figure 6-1, which provides generic resource and admission control functional architecture in NGN. It is based on Figure 5 of

48、ITU-T Y.2111 with the following modifications: “Service control 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 i

49、s replaced by TRE-PE PE-FE is replaced by PE-PE RACF is replaced by RAC-PE Q.3305.1(11)_F6-1Scope of thisRecommendationService controlentityService stratumTransport stratumNetworkattachementcontrolentityCGPE-PECPNOtherNGNsRAC-PERsRdRiPD-PETRC-PERuRhRn Rc RwTRE-PE PE-PETransport physical entityRtRpFigure 6-1 Localization of the Rt reference point in the generic resource and admission control functional architecture in NGN Rec. ITU-T Q.3305.1 (06/2011) 5 6.2 Functional elements an