1、 ETSI TS 129 207 V6.5.0 (2005-09)Technical Specification Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);Policy control over Go interface(3GPP TS 29.207 version 6.5.0 Release 6)GLOBAL SYSTEM FOR MOBILE COMMUNICATIONSRETSI ETSI TS 129 207 V6.5.0
2、 (2005-09) 1 3GPP TS 29.207 version 6.5.0 Release 6 Reference RTS/TSGC-0329207v650 Keywords GSM, UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la So
3、us-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between
4、such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be sub
5、ject to revision or change of status. Information on the current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ET
6、SI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2005. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are T
7、rade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TS
8、129 207 V6.5.0 (2005-09) 2 3GPP TS 29.207 version 6.5.0 Release 6 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-me
9、mbers, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/hom
10、e.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the
11、 present document. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as bein
12、g references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp . ETSI ETSI TS 129 207 V6.5.0 (2005-09) 3 3GPP TS 29.207 version 6.5.0 Release 6 Contents Intellectual Property Rights2 Fore
13、word.2 Foreword.5 1 Scope 6 2 References 6 3 Definitions and abbreviations.7 3.1 Definitions7 3.2 Abbreviations .8 4 Go interface9 4.1 Overview 9 4.2 Go reference model 11 4.3 Functional elements and capabilities12 4.3.1 GGSN .12 4.3.1.1 Service-based local policy enforcement point.12 4.3.1.1.1 QoS
14、Information processing12 4.3.1.2 Initialisation and maintenance.13 4.3.1.3 Gate function.13 4.3.1.4 Void.14 4.3.1.5 Binding mechanism handling14 4.3.2 PDF.15 4.3.2.1 Service-based local policy decision point .15 4.3.2.2 Initialisation and maintenance.16 4.3.2.3 Binding mechanism handling16 5 Policy
15、control procedures.17 5.1 GGSN.17 5.1.1 Initial authorization at PDP context activation .17 5.1.2 Modification of previously authorized PDP context.17 5.1.3 Session modification initiated decision.18 5.1.4 PDP context deactivation18 5.1.5 Gate control operation 18 5.1.6 User plane operation .18 5.2
16、PDF 19 5.2.1 SBLP decisions.19 5.2.1.1 SBLP authorisation decision .19 5.2.1.2 Session modification initiated decision.21 5.2.1.3 SBLP revoke decision.21 5.2.1.4 SBLP gate decision .21 5.2.2 Support for SIP forking.22 5.2.2.1 Authorization of resources for forked responses.22 5.2.2.2 Updating the au
17、thorization information at the final answer 22 6 Go protocol.22 6.1 Protocol support .22 6.1.1 TCP connection for COPS protocol22 6.1.2 COPS protocol23 6.2 Basic COPS events/messages.23 6.2.1 Type of messages23 6.3 Go events/messages23 6.3.1 Event descriptions.24 6.3.1.1 Common Header, Client Type 2
18、4 6.3.1.2 Context Object 24 6.3.1.3 Client Specific Information (ClientSI) for outsourcing Operation24 6.3.1.4 Conformance Section24 ETSI ETSI TS 129 207 V6.5.0 (2005-09) 4 3GPP TS 29.207 version 6.5.0 Release 6 6.3.1.5 Reporting of Device Capabilities and Device Limitations26 6.3.1.6 Initial Go Pol
19、icy Provisioning.26 6.3.2 Message description26 6.4 Go data .29 6.5 Security Considerations29 Annex A: (Void)30 Annex B (normative): 3GPP Go PIB31 Annex C (normative): Flow identifiers: Format definition and examples50 C.1 Format of a flow identifier .50 C.2 Example 1.51 C.3 Example 2.52 C.4 Example
20、 3 without media components.54 C.5 Example 4.54 Annex D (normative): Go interface related error code values for the PDP context handling 56 Annex E (informative): Overview of the 3GPP Go PIB working mode 57 Annex F (informative): Change history .59 History 60 ETSI ETSI TS 129 207 V6.5.0 (2005-09) 5
21、3GPP TS 29.207 version 6.5.0 Release 6 Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the c
22、ontents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved
23、 document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 129 207 V6.5.0 (2005-09) 6 3GPP TS
24、 29.207 version 6.5.0 Release 6 1 Scope The present document provides the stage 3 specification of the Go interface. The functional requirements and the stage 2 specifications of the Go interface are contained in 3GPP TS 23.002 2 and 3GPP TS 23.207 3. The Go interface is the interface between the GG
25、SN and the Policy Decision Function (PDF). The present document defines: - the protocol to be used between PDF and GGSN over the Go interface; - the signalling interactions to be performed between PDF and GGSN over the Go interface; - the information to be exchanged between PDF and GGSN over the Go
26、interface. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For a specific referenc
27、e, subsequent revisions do not apply. For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. 1 3
28、GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 23.002: “Network architecture“. 3 3GPP TS 23.207: “End-to-end Quality of Service (QoS) concept and architecture“. 4 3GPP TS 23.228: “IP Multimedia Subsystem (IMS); Stage 2“. 5 Void. 6 IETF RFC 2753: “A Framework for Policy-based Admissio
29、n Control“. 7 IETF RFC 2748: “The COPS (Common Open Policy Service) Protocol“. 8 IETF RFC 3084: “COPS Usage for Policy Provisioning (COPS-PR)“. 9 IETF RFC 3159: “Structure of Policy Provisioning Information (SPPI)“. 10 Void. 11 IETF RFC 3520: “Session Authorization Policy Element“. 12 3GPP TS 24.008
30、: “Mobile radio interface Layer 3 specification; Core network protocols; Stage 3“. 13 3GPP TS 27.060: “Packet domain; Mobile Station (MS) supporting Packet Switched services“. 14 3GPP TS 24.229: “IP Multimedia Call Control Protocol based on SIP and SDP; Stage 3“. 15 IETF RFC 3318: “Framework Policy
31、Information Base“. 16 IETF RFC 3289: “Management Information Base for the Differentiated Services Architecture“ 17 IETF RFC 2327: “SDP: Session Description Protocol“. 18 3GPP TS 29.208: “End-to-end Quality of Service (QoS) signalling flows“. ETSI ETSI TS 129 207 V6.5.0 (2005-09) 7 3GPP TS 29.207 ver
32、sion 6.5.0 Release 6 19 IETF RFC 3291: “Textual Conventions for Internet Network Addresses“. 20 3GPP TS 29.060: “General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface“. 21 3GPP TS 32.225: “Telecommunication management; Charging management; Charging data d
33、escription for the IP Multimedia Subsystem (IMS)“. 22 IETF RFC 3313: “Private Session Initiation Protocol (SIP) Extensions for Media Authorization“ 23 3GPP TS 29.209: “Policy control over Gq interface“. 24 IETF RFC 3605: “Real Time Control Protocol (RTCP) attribute in Session Description Protocol (S
34、DP)“ 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 1 and the following apply: Application Function: The Application Function (AF) is an element offering applications that require the control of IP bearer re
35、sources. The AF is capable of communicating with the PDF to transfer dynamic QoS-related application information. One example of an AF is the P-CSCF of the IM CN subsystem. AF session: An AF session is established by an application level signalling protocol offered by the AF that requires a session
36、set-up with explicit session description before the use of the service. One example of an application session is an IMS session. AF session signalling: AF session signalling is used to control the AF session. One example of AF session signalling is SIP/SDP. Authorization Token: consists of the AF se
37、ssion identifier and the PDF identifier in conformance with RFC 3520 11. It is used for authorizing the QoS for the IP flow (s). The UE includes an authorization token as part of the binding information in order to obtain QoS authorization for the AF session. The UE obtains this authorization token
38、via the AF session signalling from the AF, e.g. via SIP from the P-CSCF by means of an extension SIP header described in RFC 3313 22. The AF communicates with the PDF in order to obtain a suitable authorization token for the UE. Binding Information: consists of an authorization token and the flow id
39、entifier(s) of IP flow(s) carried by a PDP context. When receiving an authorization token, the UE includes binding information when activating or modifying a PDP context. It is used for authorizing the QoS of the IP flows carried within a PDP context and to verify that the grouping of the IP flows i
40、s correct. Client Handle: an object in the COPS messages used as a unique number to correlate all the COPS messages with the same dialogue. Over the Go interface the Client Handle is used to correlate COPS messages with respect to the same PDP Context. For the exact definition see RFC 2748 7 and RFC
41、 3084 8. Common Open Policy Service (COPS) protocol: is a simple query and response protocol that can be used to exchange policy information between a policy server (Policy Decision Point) and its clients (Policy Enforcement Points) Flow identifier: used for the identification of the IP flows, descr
42、ibed within a media component associated with an AF session. A Flow identifier consists of two parts: 1) the 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 ass
43、igned in the order of increasing port numbers. Examples are provided in Annex C. Go Interface: interface between PDF and GGSN (3GPP TS 23.002 2) Gq Interface: interface between PDF and the AF. It is specified in 3GPP TS 29.209 23 GPRS Charging ID (GCID): the Charging Id generated by the GGSN as defi
44、ned in 3GPP TS 29.060 20. ETSI ETSI TS 129 207 V6.5.0 (2005-09) 8 3GPP TS 29.207 version 6.5.0 Release 6 IP Bearer Service Manager: uses standard IP mechanisms to manage the IP Bearer Service. It resides in the GGSN and optionally in the UE. IP flow: a unidirectional flow of IP packets with the same
45、 source IP address and port number and the same destination IP address and port number and the same transport protocol. Port numbers are only applicable if used by the transport protocol. Media component: is a part of an AF session description (e.g. SDP) conveying information about media (e.g. media
46、 type, format, IP address, port(s), transport protocol, bandwidth, direction). The media described by a media component can be either bi- or unidirectional. Media using RTP for transport may also have associated RTCP If so, the media component also conveys information about the associated RTCP (port
47、 and possibly bandwidth). An AF session description can consist of more than one media component. For, SDP, a media component shall not be deleted nor its position changed within the SDP session description. An SDP media component line where the port number has previously been set to 0 may be reused
48、 for a new media component. Policy Decision Function (PDF): is a logical policy decision element that uses standard IP mechanisms to implement policy in the IP media layer The PDF makes decisions in regard to network based IP policy using policy rules, and communicates these decisions to the PEP in
49、the GGSN. Proxy Call Session Control Function (P-CSCF): is a network element providing session management services (e.g. telephony call control) Policy Enforcement Point (PEP): is a logical entity that enforces policy decisions made by the PDF. It resides in the IP BS Manager of the GGSN Policy Information Base (PIB): is a set of policy data carried by COPS-PR The protocol assumes a named data structure, known as a Policy Information Base (PIB), to identify the type and purpose of solicited and unsolicite
