1、 ETSI TS 129 210 V6.7.0 (2006-12)Technical Specification Universal Mobile Telecommunications System (UMTS);Charging rule provisioning over Gx interface (3GPP TS 29.210 version 6.7.0 Release 6)ETSI ETSI TS 129 210 V6.7.0 (2006-12) 1 3GPP TS 29.210 version 6.7.0 Release 6 Reference RTS/TSGC-0329210v67
2、0 Keywords 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 Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the presen
3、t 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 such versions, the reference version is the Portable Document Format (PDF). In case of
4、 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 subject to revision or change of status. Information on the current status of this and ot
5、her 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/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized b
6、y written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2006. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON l
7、ogo 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 129 210 V6.7.0 (2006-12) 2 3GPP TS 29.210 version 6.7.0 Release 6 Intellectual Propert
8、y 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-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Esse
9、ntial, 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/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has
10、 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 present document. Foreword This Technical Specification (TS) has been produced by ETS
11、I 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 being references to the corresponding ETSI deliverables. The cross reference between GSM,
12、UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp . ETSI ETSI TS 129 210 V6.7.0 (2006-12) 3 3GPP TS 29.210 version 6.7.0 Release 6 Contents Intellectual Property Rights2 Foreword.2 Foreword.5 1 Scope 6 2 References 6 3 Definitions, symbols and abbreviations .7
13、 3.1 Definitions7 3.3 Abbreviations .7 4 Gx reference point8 4.1 Overview 8 4.2 Charging Rules.8 4.3 Functionality of the Gx reference point8 4.3.1 Initialization and maintenance of connection .8 4.3.2 Request for charging rules from the TPF9 4.3.3 Provision of charging rules from the CRF 9 4.3.4 Pr
14、ovision of event triggers from the CRF.9 4.3.5 Provision of charging addresses from the CRF.10 4.3.6 Indication of bearer termination (from TPF to CRF)10 5. Gx Protocol 10 5.1 Protocol support .10 5.2 Gx specific AVPs .10 5.2.1 Bearer-Usage AVP .11 5.2.2 Charging-Rule-Install AVP 11 5.2.3 Charging-R
15、ule-Remove AVP .11 5.2.4 Charging-Rule-Definition AVP12 5.2.5 Charging-Rule-Base-Name AVP12 5.2.6 Charging-Rule-Name AVP.12 5.2.7 Event-Trigger AVP.12 5.2.8 Metering-Method AVP .13 5.2.9 Offline AVP13 5.2.10 Online AVP 13 5.2.11 Precedence AVP .13 5.2.12 Void 14 5.2.13 Void 14 5.2.14 Void 14 5.2.15
16、Reporting-Level AVP .14 5.2.16 Void 14 5.2.17 Void 14 5.2.18 TFT-Filter AVP 14 5.2.19 TFT-Packet-Filter-Information AVP 14 5.2.20 ToS-Traffic-Class AVP 15 5.2.21 PDP-Session-Operation AVP .15 5.3 Gx re-used AVPs15 5.4 Gx specific Experimental-Result-Code AVP values17 5.4.1 Success17 5.4.2 Permanent
17、Failures .17 6 Gx Messages 17 6.1 Gx Application .18 6.1.1 CC-Request (CCR) Command18 6.1.2 CC-Answer (CCA) Command18 6.1.3 Re-Auth-Request (RAR) Command .19 6.1.4 Re-Auth-Answer (RAA) Command .19 ETSI ETSI TS 129 210 V6.7.0 (2006-12) 4 3GPP TS 29.210 version 6.7.0 Release 6 6.2 Gx over Gy Applicati
18、on .19 6.2.1 Simultaneous charging rule provision and credit authorization20 Annex A (informative): Change history .21 History 22 ETSI ETSI TS 129 210 V6.7.0 (2006-12) 5 3GPP TS 29.210 version 6.7.0 Release 6 Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Pr
19、oject (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 contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in v
20、ersion 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 document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corre
21、ctions, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 129 210 V6.7.0 (2006-12) 6 3GPP TS 29.210 version 6.7.0 Release 6 1 Scope The present document provides the stage 3 specification of the Gx reference point. The fun
22、ctional requirements and the stage 2 specifications of the Gx reference point are contained in 3GPP TS 23.125 3. The Gx reference point is for provisioning service data flow based charging rules between the Traffic Plane Function (TPF) and the Charging Rules Function (CRF), also known as Service Dat
23、a Flow Based Charging Rules Function. The present document defines: - the protocol to be used between TPF and CRF over the Gx reference point; - the information to be exchanged between TPF and CRF over the Gx reference point. Whenever it is possible the present document specifies the requirements fo
24、r this protocol by reference to specifications produced by the IETF within the scope of Diameter. Where this is not possible, extensions to Diameter are defined within the present document. 3GPP TS 29.211 15 provides callflows for Flow Based Charging, covering the signalling on the Gx reference poin
25、t. 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, edition number, version number, etc.) or non-specific. For a specific reference, subsequ
26、ent 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 3GPP TR 21.
27、905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 23.002: “Network architecture“. 3 3GPP TS 23.125: “Overall high level functionality and architecture impacts of flow based charging; Stage 2“. 4 IETF RFC 3588: “Diameter Base Protocol“. 5 IETF RFC 2234: “Augmented BNF for syntax specifications: AB
28、NF“. 6 3GPP TS 33.210: “3G security; Network Domain Security (NDS); IP network layer security“. 7 3GPP TS 29.207: “Policy control over Go interface“. 8 IETF RFC 4006: “Diameter Credit-Control Application“. 9 3GPP TS 32.299: “Telecommunication management; Charging management; Diameter charging applic
29、ations“. 10 3GPP TS 29.209: “Policy control over Gq interface“. 11 3GPP TS 29.061: “Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)“. 12 IETF RFC 4005: “Diameter Network Access Server Application“. 13 3GPP TS 32.251: “Packet
30、Switched (PS) domain charging“. ETSI ETSI TS 129 210 V6.7.0 (2006-12) 7 3GPP TS 29.210 version 6.7.0 Release 6 14 3GPP TS 24.008: “Mobile radio interface Layer 3 specification; Core network protocols; Stage 3“. 15 3GPP TS 29.211: “Rx Interface and Rx/Gx signalling flows“. 16 3GPP TS 29.229: “Cx and
31、Dx interfaces based on the Diameter protocol; Protocol details“. 17 IETF RFC 3162: “Radius and IPv6“. 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 1, in 3GPP TS 23.125 3 and the following apply: A
32、pplication Function (AF): element offering applications that use IP bearer resources The AF is capable of communicating with the CRF to transfer dynamic charging rules related service information. One example of an AF is the P-CSCF of the IM CN subsystem. Attribute-Value Pair: See IETF RFC 3588 4, c
33、orresponds to an Information Element in a Diameter message. PDP Session: unique association of a subscriber with a network access service given by the combination of MSISDN, APN and IP address. A PDP session can consist of one or more PDP contexts. 3.3 Abbreviations For the purposes of the present d
34、ocument, the abbreviations given in 3GPP TR 21.905 1 and the following apply: AF Application Function AVP Attribute-Value PairCCF Charging Collection Function CGF Charging Gateway Function CRF Charging Rules Function CSCF Call Session Control Function DCC Diameter Credit Control GCID GPRS Charging I
35、D ICID IMS Charging IDentifier IM IP Multimedia IMS IP Multimedia core network Subsystem IMSI International Mobile Subscriber Identity OCS Online Charging System P-CSCF Proxy-CSCF PDGw Packet Data Gateway PLMN Public Land Mobile Network QoS Quality of Service SBLP Service Based Local Policy S-CSCF S
36、erving-CSCF SDF Service Data Flow SGSN Serving GPRS Support Node SIP Session Initiation Protocol TPF Traffic Plane Function UE User Equipment WAP Wireless Application Protocol WLAN Wireless LAN ETSI ETSI TS 129 210 V6.7.0 (2006-12) 8 3GPP TS 29.210 version 6.7.0 Release 6 4 Gx reference point 4.1 Ov
37、erview The Gx reference point is used for provisioning service data flow based charging rules. The reference point is located between the Traffic Plane Function (TPF) and the Charging Rules Function (CRF), also known as Service Data Flow Based Charging Rules Function. The stage 2 level requirements
38、for the Gx reference point are defined in 3GPP TS 23.125 3. 4.2 Charging Rules Charging rules determine how service data flows are identified and charged. The TPF shall apply charging rules by evaluating received packets against service data flow filters. When a packet matches a service data flow fi
39、lter, the packet matching process for that packet is completed, and the charging rule for that filter shall be applied. Charging rules may be: - Pre-defined and active within the TPF, i.e. default rules that are configured within the TPF. - Pre-defined within the TPF but not active, i.e. charging ru
40、les that can be activated dynamically over the Gx reference point. - Pre-defined within the CRF and provided by the CRF, i.e. charging rules that can be installed dynamically over the Gx reference point. - Dynamically generated and provided by the CRF, i.e. charging rules that can be installed dynam
41、ically over the Gx reference point. (e.g. dynamic charging rules for example for IMS peer to peer service data flows, where both the service data flow filter and the charging rule are identified dynamically). NOTE: Whether the charging rule is pre-defined or dynamically generated by the CRF does not
42、 impact the procedures at the Gx reference point. - Pre-defined rules within the TPF may be grouped allowing CRF to dynamically activate a set of rules over the Gx reference point. A charging rule shall consist of a charging rule name, charging key (i.e. rating group), service identifier, service fl
43、ow filter and other charging parameters. The charging rule name shall be used to reference to a charging rule in the communication between the TPF and the CRF. The service identifier shall be used to identify the service or the service component the service data flow relates to. The service flow fil
44、ter shall be used to select the traffic for which the charging rule applies. The charging parameters define whether online and offline charging interfaces are used, what is to be metered in offline charging, what is the precedence of the charging rule, on what level the TPF shall report the usage re
45、lated to the charging rule, etc. For different charging rules with overlapping service data flow filter, the precedence of the charging rule determines which of these charging rules is applicable. Charging rule also includes Application Function record information for enabling charging correlation b
46、etween the application and bearer layer if the Application Function has provided this information via the Rx interface. For IMS this includes the IMS Charging Identifier (ICID) and flow identifiers. See the AVPs in clauses 5.2 and 5.3. 4.3 Functionality of the Gx reference point 4.3.1 Initialization
47、 and maintenance of connection The initialization and maintenance of the connection between each interworking CRF and TPF pair is defined by the underlying protocol. Establishment and maintenance of connections between Diameter nodes is described in IETF RFC 3588 4. ETSI ETSI TS 129 210 V6.7.0 (2006
48、-12) 9 3GPP TS 29.210 version 6.7.0 Release 6 4.3.2 Request for charging rules from the TPF The TPF shall indicate, via the Gx reference point, a request for charging rules in the following instances. 1) At bearer establishment: The TPF shall send a CC-Request with CC-Request-Type AVP set to the val
49、ue INITIAL_REQUEST. The TPF shall supply user identification and other attributes to allow the CRF to identify the charging rules to be applied. The other attributes shall include the type of the radio access technology (e.g UTRAN, GERAN, WLAN) and the UE IP address. For GPRS, information about the user equipment (e.g. IMEISV), QoS negotiated, SGSN Address, SGSN country and network codes, APN, TFT and indication if the bearer is used as IMS signalling PDP context shall be provided. 2) At bearer modification if an Event t
