1、 International Telecommunication Union ITU-T Q.3303.0TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (11/2007) SERIES Q: SWITCHING AND SIGNALLING Signalling requirements and protocols for the NGN Resource control protocols Resource control protocol No. 3 Protocols at the Rw interface between a polic
2、y decision physical entity (PD-PE) and a policy enforcement physical entity (PE-PE): Overview ITU-T Recommendation Q.3303.0 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 FUNCTIO
3、NS 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.3369 Service 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 NGN networks Q.3900Q.3999 For further details, please refer to the list of ITU-T Recommendations. ITU-T Rec. Q.3303.0 (11/2007) i ITU-T Recommendation Q.3303.0 Resource control protocol No. 3 Protocols at the Rw interface between a policy
8、 decision physical entity (PD-PE) and a policy enforcement physical entity (PE-PE): Overview Summary Interface Rw defines an interface between a policy decision physical entity (PD-PE) and a policy enforcement physical entity (PE-PE). There are a number of signalling alternatives for Rw, each is def
9、ined in a protocol-specific Recommendation in the Q.3303.x-series of Recommendations. ITU-T Recommendation Q.3303.0 provides a protocol-independent introduction, describing the common material, which is relevant for all protocol specific signalling solutions. Source ITU-T Recommendation Q.3303.0 was
10、 approved on 6 November 2007 by ITU-T Study Group 11 (2005-2008) under the ITU-T Recommendation A.8 procedure. ii ITU-T Rec. Q.3303.0 (11/2007) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and commun
11、ication 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
12、 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 down in WTSA Resolution 1
13、. 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 telecommunication administration and a r
14、ecognized 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. Th
15、e 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 attention to the possibility
16、 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 others outside of the Recomme
17、ndation 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 a
18、nd are therefore strongly urged to consult the 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.3303.0 (11/2007) iii CONTENTS Page 1 Sco
19、pe 1 2 References. 1 3 Definitions 1 3.1 Terms defined elsewhere 1 3.2 Terms defined in this Recommendation. 2 4 Abbreviations and acronyms 2 5 Conventions 3 6 Rw interface 3 6.1 Overview 3 6.2 Rw reference model 4 6.3 Functional elements and capabilities 4 Bibliography. 9 ITU-T Rec. Q.3303.0 (11/20
20、07) 1 ITU-T Recommendation Q.3303.0 Resource control protocol No. 3 Protocols at the Rw interface between a policy decision physical entity (PD-PE) and a policy enforcement physical entity (PE-PE): Overview 1 Scope Interface Rw defines an interface between a policy decision physical entity (PD-PE) a
21、nd a policy enforcement physical entity (PE-PE). There are a number of signalling alternatives for Rw, defined in protocol-specific Recommendations in the Q.3303.x-series of Recommendations. This Recommendation provides a protocol-independent introduction, describing the common material, which is re
22、levant for all protocol specific signalling solutions. In particular, the scope of this Recommendation includes the following aspects: overview; Rw reference model; functional elements and capabilities. 2 References The following ITU-T Recommendations and other references contain provisions which, t
23、hrough reference in this text, constitute 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 applyi
24、ng 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 to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T Q
25、.3300 ITU-T Recommendation Q.3300 (2008), Architectural framework for the Q.33xx series of Recommendations. ITU-T Y.2012 ITU-T Recommendation Y.2012 (2006), Functional requirements and architecture of the NGN release 1. ITU-T Y.2111 ITU-T Recommendation Y.2111 (2006), Resource and admission control
26、functions in Next Generation Networks. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 policy decision physical entity (PD-PE) ITU-T Q.3300: The PD-PE is an implemented instance of the policy decision functional entity (PD-FE) identifie
27、d in ITU-T Y.2111. 3.1.2 policy enforcement physical entity (PE-PE) ITU-T Q.3300: The PE-PE is an implemented instance of the policy enforcement functional entity (PE-FE) identified in ITU-T Y.2111. 3.1.3 transport resource control physical entity (TRC-PE) ITU-T Q.3300: A device that implements the
28、transport resource control functional entity (TRC-FE) as defined in clause 7.2.3.3 of ITU-T Y.2111. 2 ITU-T Rec. Q.3303.0 (11/2007) 3.2 Terms defined in this Recommendation None. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: BGW Border Gateway BRAS B
29、roadband Remote Access Server CDMA Code Division Multiple Access CNPS Core Network Path Selection CMTS Cable Modem Termination System COPS Common Open Policy Service DSL Digital Subscriber Line DSLAM DSL Access Multiplexer FDP Final Decision Point FWMS Firewall Working Mode Selection GC Gate Control
30、 GGSN Gateway GPRS Support Node GPRS General Packet Radio Service IP Internet Protocol IPMC IP Packet Marking Control MG Media Gateway NAPT Network Address and Port Translation NAPTC NAPT Control NAT Network Address Translation NS Network Selection PDG Packet Data Gateway PDP Packet Data Protocol PD
31、SN Packet Data Serving Node QMTI QoS Mapping Technology Independent QoS Quality of Service RLC Rate Limiting Control SCE Service Control Entity SCF Service Control Function TCP Transmission Control Protocol UDP User Datagram Protocol UE User Equipment VLAN Virtual LAN ITU-T Rec. Q.3303.0 (11/2007) 3
32、 VPN Virtual Private Network WLAN Wireless Local Area Network 5 Conventions None. 6 Rw interface 6.1 Overview As defined in the stage 2 specifications ITU-T Y.2111 and b-ITU-T Q-Sup.51, the Rw interface is used for information exchange to apply policy decisions between the PD-PE and the PE-PE that m
33、ay reside in various transport devices, e.g., BGW, DSLAM/BRAS and GGSN/PDSN. The Rw interface shall be an intra-operator interface. One PD-PE instance may be able to serve more than one PE-PE instance, and one given PE-PE instance may interact with more than one PD-PE instance. For any individual se
34、ssion, one PD-PE instance shall make the final policy decisions in a single operator domain. The Rw interface shall be understood by the both sides of PD-PE and PE-PE which means PD-PE shall know which protocol is bound with the given PE-PE. The binding relationship can be static using dedicated wel
35、l-known transport ports. In the case when PE-PE resides in various transport devices, we can use other port value (outside the well-known port range), which is a subject of a mutual agreement (= provisioning) between PE-PE and PD-PE. Alternatively, we can establish a binding relationship between PE-
36、FE and PD-FE according to the terminal type. The Rw interface allows the PD-PE to push the admission decisions to the PE-PE. It also allows the PE-PE to request admission decisions when path-coupled resource reservation mechanisms are in use. The PD-PE may specify: resources to be reserved and/or co
37、mmitted for media flows; QoS handling such as packet marking and policing to use; gate control (opening/closing) for a media flow; insertion of a NAPT function, requesting the necessary address mapping information; resource usage information request and report for a media flow; dynamic firewall work
38、ing mode selection for a media flow; technology-independent core network ingress/egress path information for a media flow. The following provides a brief description of the information exchange requirements for the Rw interface. Request-response “transactions“: The interface must allow the PD-PE or
39、the PE-PE respectively to request an action to be performed by the PE-PE or the PD-PE respectively and get a response (that can be correlated with the request) in return. NOTE 1 Some terms like “transaction“, “message“, “action“, “command“ and others are used in a generic manner in this Recommendati
40、on. These terms may have a protocol-specific meaning, and if they do, they will be defined in the relevant Q.3303.x-specific protocol Recommendation. Notifications: The interface must allow for the notification of asynchronous events (from the PE-PE to the PD-PE). 4 ITU-T Rec. Q.3303.0 (11/2007) Rel
41、iable delivery: The interface should provide reliable delivery of messages. Capabilities: The PD-PE must be able to determine capabilities when requesting resources and other transport plane functions from the PE-PE. Security: All messages between the PD-PE and the PE-PE should be authenticated such
42、 that requests to the PE-PE from unauthenticated sources will not be performed and such that notifications sent from the PE-PE to the PD-PE came from an authenticated PE-PE source. One-to-many/many-to-one: Two modes shall be supported: 1) One-to-many mode, a PD-PE shall be able to communicate with m
43、ultiple PE-PEs. 2) Many-to-one mode, multiple PD-PEs shall be able to make requests to a given PE-PE. NOTE 2 This mode is not supported when using COPS (ITU-T Rec. Q.3303.1). NOTE 3 This mode requires the support of virtual MGs when using H.248 (ITU-T Rec. Q.3303.2). For either mode, only a single P
44、D-PE shall make a request to a given PE-PE for a particular session. 6.2 Rw reference model The Rw interface, as shown in Figure 1, is defined between the PD-PE and the PE-PE. Figure 1 Rw reference model 6.3 Functional elements and capabilities 6.3.1 Policy decision physical entity (PD-PE) 6.3.1.1 S
45、ummary The PD-PE coordinates the resource requests from the SCE and/or the PE-PE, and makes policy decisions using a collection of information as described below. The PD-PE requests the resource availability information and resource admission control from the TRC-PE. Finally, the PD-PE shall request
46、 the policy enforcement operations to the PE-PE via the Rw interface. The functionality of the PD-PE is further detailed in clause 7.2.3 of ITU-T Y.2111. ITU-T Rec. Q.3303.0 (11/2007) 5 The PD-PE should be able to support both push mode and pull mode according to the configuration of network operato
47、r and/or the access network type in the process of resource reservation, gate control and policy enforcement. In the push mode, the PD-PE takes the initiative in pushing down policy decisions to the PE-PE upon receipt of a request from the SCE; in the pull mode, the PD-PE should re-authorize and ret
48、rieve policy decisions upon receipt of a request from the PE-PE. The push mode is typically used in transport networks that do not support or require transport signalling for establishing network resources dynamically on behalf of, or directly by, an individual service session of the UE, e.g., DSL b
49、roadband access and Ethernet. The pull mode is typically used in transport networks that support or require the use of transport signalling to establish the network resource dynamically on behalf of or directly by an individual service session of the UE, e.g., GPRS. In addition, the PD-PE may provision the static policy configuration onto the PE-PE upon the triggers of network policies, conditions and resource status. The dynamic policy decisions are produced by the PD-PE according to th
