1、 ETSI TS 123 125 V7.0.0 (2007-06)Technical Specification Universal Mobile Telecommunications System (UMTS);Overall high level functionality andarchitecture impacts of flow based charging;Stage 2 (3GPP TS 23.125 version 7.0.0 Release 7)ETSI ETSI TS 123 125 V7.0.0 (2007-06) 1 3GPP TS 23.125 version 7.
2、0.0 Release 7 Reference RTS/TSGS-0223125v700 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 Impor
3、tant 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 such versions, the reference version is the
4、 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 subject to revision or change of status. Infor
5、mation 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/ETSI_support.asp Copyright Notification No pa
6、rt 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 2007. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benef
7、it 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 123 125 V7.0.0 (2007-06) 2 3GPP TS 23.125 v
8、ersion 7.0.0 Release 7 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-members, and can be found in ETSI SR 000 314:
9、 “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/home.asp). Pursuant to the ETSI IPR Policy, no
10、 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 present document. Foreword This Technical
11、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 being references to the corresponding ETSI deli
12、verables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TS 123 125 V7.0.0 (2007-06) 3 3GPP TS 23.125 version 7.0.0 Release 7 Contents Intellectual Property Rights2 Foreword.2 Foreword.5 1 Scope 6 2 References 6 3
13、 Definitions, symbols and abbreviations .7 3.1 Definitions7 3.2 Symbols7 3.3 Abbreviations .7 4 General Requirements 8 4.1 General .8 4.2 Backwards compatibility8 4.3 Charging models 9 4.3.1 General9 4.3.2 Examples of Service Data Flow Charging10 5 Flow Based Charging Concepts .10 5.1 Overview 10 5.
14、2 Charging rules 11 5.3 Service data flow detection and counting.13 5.4 Reporting14 5.5 Credit management.14 5.6 Termination Action 15 5.7 Re-authorisation and Event Triggers15 5.8 Policy functions provided by FBC architecture16 5.8.1 General16 5.8.2 Charging correlation .16 5.8.3 Gating .17 5.8.4 Q
15、oS control.17 5.8.5 Bearer events 17 5.8.6 Session events.17 5.9 Bearer Relation.18 6 Architectural concepts18 6.1 Architecture18 6.1.1 Online service data flow based bearer charging architecture18 6.1.2 Offline service data flow based bearer charging architecture .18 6.2 Functional Entities19 6.2.1
16、 Charging Rules Function 19 6.2.2 Service Data Flow Based Credit Control Function.19 6.2.3 Offline Charging System 20 6.2.4 Traffic Plane Function 20 6.2.5 Application Function 21 6.2.6 Relationship between functional entities 22 6.3 Reference points.22 6.3.1 Gx reference point 22 6.3.1.1 Initialisa
17、tion and Maintenance of Gx Connection.22 6.3.1.2 Request for Charging Rules (from TPF to CRF).23 6.3.1.3 Provision of Charging Rules (from CRF to TPF) .23 6.3.1.4 Indication of Bearer Termination (from TPF to CRF) 23 6.3.2 Gy reference point 23 6.3.3 Gz reference point.24 6.3.4 Rx reference point.24
18、 6.3.4.1 General24 ETSI ETSI TS 123 125 V7.0.0 (2007-06) 4 3GPP TS 23.125 version 7.0.0 Release 7 6.3.4.2 Initialisation and Maintenance of Rx Connection.24 6.3.5 Void 24 7 Message Flows .24 7.1 AF input to provision of charging rules24 7.2 Bearer events 25 7.2.1 Bearer Service Establishment .25 7.2
19、.2 Bearer Service Modification.27 7.2.2.1 General27 7.2.2.2 Bearer Service Modification in case of offline charging.27 7.2.2.3 Void.28 7.2.2.4 Bearer Service Modification in case of online charging .29 7.2.3 Bearer Service Termination 30 7.2.4 Notification of AF on bearer events31 7.3 Provision of C
20、harging Rules triggered by other event to the CRF.32 7.4 TPF initiated Bearer Service Termination33 Annex A (informative): Overall architectural impacts of IP flow based charging.35 A.1 GGSN in HPLMN35 A.2 Comparison of S-CDR and G-CDR fields .35 A.2.1 S-CDR information missing from G-CDR.35 A.2.2 S
21、erved IMEI .35 A.2.3 MS Network Capability36 A.2.4 LAC/RAC/CI at “record opening“ .36 A.2.5 Access Point Name Operator Identifier36 A.2.6 System Type.36 A.2.7 CAMEL information 37 A.2.8 RNC unsent data volume37 A.2.9 Time zone of the users location .37 A.3 RADIUS attributes .38 Annex B (informative)
22、: IMS and Flow based charging 39 B.1 IMS SIP signalling .39 B.2 IMS media39 B.3 FBC with IMS compared to release 5 IMS charging correlation.41 B.4 Rx/Gx functions and SBLP usage41 Annex C (informative): WLAN and flow based charging 42 C.1 TPF usage for WLAN 42 Annex D (informative): Policy functions
23、 provided by FBC architecture43 D.1 General .43 D.2 General architectural considerations 43 D.2.1 Charging correlation.43 D.2.2 Gating.44 D.2.3 QoS control 44 D.2.4 Bearer events 44 D.2.5 Session events 45 D.3 Summary and comparison46 Annex E (informative): Change history .47 History 49 ETSI ETSI TS
24、 123 125 V7.0.0 (2007-06) 5 3GPP TS 23.125 version 7.0.0 Release 7 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.
25、 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 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 gr
26、eater indicates TSG approved 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 123 12
27、5 V7.0.0 (2007-06) 6 3GPP TS 23.125 version 7.0.0 Release 7 1 Scope The present document specifies the overall high level functionality and architecture impacts of Flow Based Charging. 2 References The following documents contain provisions which, through reference in this text, constitute provision
28、s 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, subsequent revisions do not apply. For a non-specific reference, the latest version applies. In the case of a reference to a
29、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 Void. 2 3GPP TS 21.905: “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Vocabular
30、y for 3GPP Specifications“. 3 3GPP TS 32.240: “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Charging management; Charging architecture and principles“. 4 Void. 5 3GPP TS 23.002: “3rd Generation Partnership Project; Techn
31、ical Specification Group Services and Systems Aspects; Network architecture“. 6 3GPP TS 23.060: “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS); Service description; Stage 2“. 7 3GPP TS 32.251: “3rd Generation Partne
32、rship Project; Technical Specification Group Services and System Aspects; Telecommunication management; Charging management; Packet Switched (PS) domain charging“. 8 3GPP TS 23.078: “3rd Generation Partnership Project; Technical Specification Group Core Network; Customised Applications for Mobile ne
33、twork Enhanced Logic (CAMEL); Stage 2“. 9 IETF RFC 4006: “Diameter Credit-Control Application“. 10 3GPP TS 23.234: “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3GPP system to Wireless Local Area Network (WLAN) interworking; System description“. 11 3
34、GPP TR 33.919: “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Generic Authentication Architecture (GAA); System description“. 12 3GPP TS 23.207: 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects
35、; End-to-end Quality of Service (QoS) concept and architecture“. 13 3GPP TS 23.246: “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description“. ETSI ETSI TS 123 125 V7.0.0 (20
36、07-06) 7 3GPP TS 23.125 version 7.0.0 Release 7 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TS 21.905 2 and in TS 32.251 7 and the following apply: Charging key: information used by the online and offline charg
37、ing system for rating purposes. Charging rule: a set of information including the service data flow filters, and the charging key, for a single service data flow (further details can be found in 5.2). Dynamic charging rule: Charging rule where some of the data within the charging rule (e.g. service
38、data flow filter information) is assigned via real-time analysis, which may use dynamic application derived criteria. FBC Policy Functions: The charging rules may be configured in such a way to allow FBC for a certain usage that allows/disallows traffic to pass through the TPF (further details can b
39、e found in 5.8). IP network connection: The unique UE association with an IP network (for GPRS, APN) and the allocated IP address at the TPF. Packet flow: a specific user data flow carried through the TPF. A packet flow can be an IP flow. Predefined charging rule: A charging rule which is predefined
40、 in the TPF. A predefined charging rule is either applicable for all bearers of all users or dynamically activated for an individual bearer. Service identifier: An identifier for a service. The service identifier may designate an end user service, a part of an end user service or an arbitrarily form
41、ed group thereof. The service identifier provides the most detailed identification, specified for flow based charging, of a service data flow. A concrete instance of a service may be identified if additional AF information is available (further details to be found in clause 5.2). Service data flow:
42、aggregate set of packet flows. In the case of GPRS, it shall be possible that a service data flow is more granular than a PDP context. Service Data Flow Filter: a set of filter parameters used to identify one or more of the packet flows constituting a service data flow. At least the following means
43、for the packet flow identification shall be supported: source and destination IP address+port, transport protocol, or application protocol. 3.2 Symbols For the purposes of the present document, the following symbols apply: 3.3 Abbreviations For the purposes of the present document, the following abb
44、reviations apply: AF Application Function CDR Charging Data Records CGF Charging Gateway Function CRF Charging Rules Function CSCF Call Session Control Function FBC Flow Based Charging FTP File Transfer Protocol G-CDR GGSN generated CDR GGSN Gateway GPRS Support Node GPRS General Packet Radio Servic
45、e gsmSCF GSM Service Control Function HPLMN Home PLMN HTTP Hypertext Transfer Protocol I-CSCF Interrogating CSCF ETSI ETSI TS 123 125 V7.0.0 (2007-06) 8 3GPP TS 23.125 version 7.0.0 Release 7 IM IP Multimedia IMS IP Multimedia Core Network Subsystem IMSI International Mobile Subscriber Identity OFCS
46、 Offline Charging System OCS Online Charging System P-CSCF Proxy-CSCF PDG Packet Data Gateway PLMN Public Land Mobile Network QoS Quality of Service SAI Service Area Identity S-CDR SGSN generated CDR S-CSCF Serving-CSCF SBLP Service Based Local Policy SDF Service Data Flow SGSN Serving GPRS Support
47、Node SIP Session Initiation Protocol TPF Traffic Plane Function UE User Equipment WAP Wireless Application Protocol WLAN Wireless LAN 4 General Requirements 4.1 General The current level of traffic differentiation and traffic-type awareness of the GPRS architecture shall be extended beyond APN and P
48、DP Context level. It shall be possible to apply differentiated charging for the traffic flows belonging to different services (a.k.a. different service data flows) even if they use the same PDP Context. In addition, it shall be possible to apply differentiated charging for the traffic flows belongin
49、g to different services carried by other IP Connectivity Access Networks (IP-CANs). Charging and tariffing models described in this Technical Specification shall be possible to be applied to both prepaid and postpaid subscribers, i.e. to both online and offline charging. Online and offline are not the same as prepaid and postpaid (see TS 32.240 3). For example it is worth highlighting that the operator can have postpaid subscribers on credit control by using online charging mechanisms. The GPRS online charging solutions up to release 5 are
