3GPP TS 23.125 V2.0.0 (2004-03)
`
`Technical Specification
`
`3rd Generation Partnership Project;
`Technical Specification Group Services and System Aspects;
`Overall High Level Functionality and Architecture Impacts of
`Flow Based Charging;
`Stage 2
`(Release 6)
`
`
`
`
`
`
`
`The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP.
`
`
`
`The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
`This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
`Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners' Publications Offices.
`
`
`
`T-MOBILE EXHIBIT 1103
`
`

`
`2
`
`

`
`
`
` Release 6
`
`3
`
`3GPP TS 23.125 V2.0.0 (2004-03)
`
`Keywords
`UMTS, <keyword[, keyword]>
`
`
`
`
`
`3GPP
`
`Postal address
`
`
`3GPP support office address
`650 Route des Lucioles - Sophia Antipolis
`Valbonne - FRANCE
`Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
`
`Internet
`http://www.3gpp.org
`
`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.
`
`© 2004, 3GPP Organizational Partners (ARIB, CCSA, ETSI, T1, TTA, TTC).
`All rights reserved.
`
`
`3GPP
`
`

`
`
`
` Release 6
`
`4
`
`3GPP TS 23.125 V2.0.0 (2004-03)
`
`Contents
`Foreword............................................................................................................................................................. 6
`1
`Scope ........................................................................................................................................................ 7
`2
`References ................................................................................................................................................ 7
`3
`Definitions, symbols and abbreviations ................................................................................................... 7
`3.1 Definitions ............................................................................................................................................................... 7
`3.2
`Symbols ................................................................................................................................................................... 8
`3.3 Abbreviations .......................................................................................................................................................... 8
`4
`General Requirements ............................................................................................................................ 10
`4.1 General .................................................................................................................................................................. 10
`4.2 Backwards compatibility ....................................................................................................................................... 10
`4.3 Charging models .................................................................................................................................................... 10
`4.3.1
`General ............................................................................................................................................................. 10
`4.3.2
`Examples of Service Data Flow Charging ....................................................................................................... 11
`5
`Flow Based Charging Concepts ............................................................................................................. 12
`5.1 Overview ............................................................................................................................................................... 12
`5.2 Charging rules ....................................................................................................................................................... 12
`5.3
`Service data flow filters and counting ................................................................................................................... 13
`5.4 Reporting ............................................................................................................................................................... 14
`5.5 Credit management ................................................................................................................................................ 14
`5.6
`Termination Action ............................................................................................................................................... 15
`6
`Architectural Concepts ........................................................................................................................... 15
`6.1 Architecture ........................................................................................................................................................... 15
`6.1.1
`Online service data flow based bearer charging architecture ........................................................................... 15
`6.1.2
`Offline service data flow based bearer charging architecture .......................................................................... 16
`6.2
`Functional Entities ................................................................................................................................................. 17
`6.2.1
`Service Data Flow Based Charging Rules Function ........................................................................................ 17
`6.2.2
`Service Data Flow Based Credit Control Function .......................................................................................... 17
`6.2.3
`Charging Collection Function .......................................................................................................................... 17
`6.2.4
`Traffic Plane Function ..................................................................................................................................... 17
`6.2.5
`Application Function ....................................................................................................................................... 18
`6.3 Reference points .................................................................................................................................................... 19
`6.3.1
`Gx reference point ........................................................................................................................................... 19
`6.3.1.1
`Initialisation and Maintenance of Connection ................................................................................................. 19
`6.3.1.2 Request for Charging Rules (from TPF to CRF) ............................................................................................. 20
`6.3.1.3
`Provision of Charging Rules (from CRF to TPF) ............................................................................................ 20
`6.3.1.4
`Indication of Bearer Termination (from TPF to CRF) ..................................................................................... 20
`6.3.2
`Gy reference point ........................................................................................................................................... 20
`6.3.3
`Gz reference point ............................................................................................................................................ 21
`6.3.4
`Rx reference point ............................................................................................................................................ 21
`6.3.4.1 General ............................................................................................................................................................. 21
`6.3.4.2
`Initialisation and Maintenance of Connection ................................................................................................. 21
`6.3.5
`Ry reference point ............................................................................................................................................ 21
`7
`Message Flows ....................................................................................................................................... 21
`7.1 AF input to provision of charging rules ................................................................................................................. 21
`7.2 Bearer events ......................................................................................................................................................... 22
`7.2.1
`Bearer Service Establishment .......................................................................................................................... 22
`7.2.2
`Bearer Service Modification ............................................................................................................................ 23
`7.2.3
`Bearer Service Termination ............................................................................................................................. 24
`7.3
`Provision of Charging Rules triggered by other event to the CRF ........................................................................ 25
`Overall architectural impacts of IP flow based charging ........................... 26
`Annex A (informative):
`A.1 GGSN in HPLMN ................................................................................................................................................. 26
`
`3GPP
`
`

`
`
`
` Release 6
`
`5
`
`3GPP TS 23.125 V2.0.0 (2004-03)
`
`A.2 Comparison of S-CDR and G-CDR fields ............................................................................................................. 26
`A.2.1
`S-CDR information missing from G-CDR ...................................................................................................... 26
`A.2.2
`Served IMEI..................................................................................................................................................... 26
`A.2.3 MS Network Capability ................................................................................................................................... 27
`A.2.4
`LAC/RAC/CI at “record opening” ................................................................................................................... 27
`A.2.5
`Access Point Name Operator Identifier ........................................................................................................... 27
`A.2.6
`System Type .................................................................................................................................................... 27
`A.2.7
`CAMEL information........................................................................................................................................ 28
`A.2.8
`RNC unsent data volume ................................................................................................................................. 28
`A.3 RADIUS attributes ................................................................................................................................................ 28
` IMS and Flow based Charging .................................................................... 29
`Annex B (informative):
`B.1
`IMS SIP signalling ................................................................................................................................................ 29
`B.2 Rx/Gx functions and SBLP usage ......................................................................................................................... 29
`Annex C (informative): WLAN and flow based charging .................................................................. 30
`C.1 TPF usage for WLAN ........................................................................................................................................... 30
`Change history ............................................................................................... 31
`Annex D (informative):
`
`
`3GPP
`
`

`
`
`
` Release 6
`
`6
`
`3GPP TS 23.125 V2.0.0 (2004-03)
`
`Foreword
`This Technical Specification has been produced by the 3rd Generation 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 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 greater 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.
`
`3GPP
`
`

`
`
`
` Release 6
`
`7
`
`3GPP TS 23.125 V2.0.0 (2004-03)
`
`Scope
`1
`The present document specifies the overall high level functionality and architecture impacts of Flow Based Charging.
`
`References
`2
`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, 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.
`
`[<seq>]
`
`<doctype> <#>[ ([up to and including]{yyyy[-mm]|V<a[.b[.c]]>}[onwards])]: "<Title>".
`
`
`
`[1]
`
`[2]
`
`[3]
`
`[4]
`
`[5]
`
`[6]
`
`[7]
`
`[8]
`
`3GPP TR 41.001: "GSM Release specifications".
`
`3GPP TS 21.905: "Vocabulary for 3GPP Specifications".
`
`3GPP TS 32.200: "Charging Principles".
`
`3GPP TS 23.228: "IP Multimedia (IM) Subsystem - Stage 2".
`
`3GPP TS 23.002: "Network architecture".
`
`3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
`
`3GPP TS 32.225: “Telecommunication management; Charging management; Charging data
`description for the IP Multimedia Subsystem (IMS)”.
`
`3GPP TS 23.078: “Customised Applications for Mobile network Enhanced Logic (CAMEL);
`Stage 2”.
`
`3
`
`Definitions, symbols and abbreviations
`
`Definitions
`3.1
`For the purposes of the present document, the terms and definitions given in TS 21.905 [2] and in TS 32.225 [7] and the
`following apply:
`
`Editor’s note: terms shown in <angle brackets> are provisional.
`
`Packet flow: a specific user data flow carried through the Traffic Plane Function. A packet flow can be an IP flow.
`Service data flow: 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.
`
`3GPP
`
`

`
`
`
` Release 6
`
`8
`
`3GPP TS 23.125 V2.0.0 (2004-03)
`
`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 for the packet flow identification shall be supported: source and
`destination IP address+port, transport protocol, or application protocol.
`Charging rule: a set of information comprising the service data flow filters, charging key, and the associated charging
`actions, for a single service data flow (further details can be found in 4.3).
`Charging key: information used by the online and offline charging system for rating purposes.
`Dynamic charging rules: Charging rules where some of the data within the charging rule (e.g. service data flow filter
`information) is assigned via real-time analysis which may use dynamic application derived criteria.
`
`Static charging rules: Charging rules where all of the data within the charging rule describing the service data flow is
`permanently configured throughout the duration of a user’s data session. Static charging rules may be activated
`dynamically.
`
`Predefined charging rules: Static charging rules which are defined in the Traffic Plane Function.
`
`
`
`Symbols
`3.2
`For the purposes of the present document, the following symbols apply:
`
`Abbreviations
`3.3
`For the purposes of the present document, the following abbreviations apply:
`
`AF
`CCF
`CDR
`CGF
`CRF
`CSCF
`GCID
`GGSN
`GPRS
`HPLMN
`HTTP
`ICID
`IM
`IMS
`IMSI
`OCS
`P-CSCF
`PDGw
`PLMN
`QoS
`S-CSCF
`SBLP
`SDF
`SGSN
`SIP
`TPF
`UE
`WAP
`WLAN
`
`Application Function
`Charging Collection Function
`Charging Data Records
`Charging Gateway Function
`Charging Rules Function
`Call Session Control Function
`GPRS Charging ID
`Gateway GPRS Support Node
`General Packet Radio Service
`Home PLMN
`Hypertext Transfer Protocol
`IMS Charging Identifier
`IP Multimedia
`IP Multimedia Core Network Subsystem
`International Mobile Subscriber Identity
`Online Charging System
`Proxy-CSCF
`Packet Data Gateway
`Public Land Mobile Network
`Quality of Service
`Serving-CSCF
`Service Based Local Policy
`Service Data Flow
`Serving GPRS Support Node
`Session Initiation Protocol
`Traffic Plane Function
`User Equipment
`Wireless Application Protocol
`Wireless LAN
`
`3GPP
`
`

`
`
`
` Release 6
`
`9
`
`3GPP TS 23.125 V2.0.0 (2004-03)
`
`4
`
`General Requirements
`
`General
`4.1
`The current level of traffic differentiation and traffic-type awareness of the GPRS architecture shall be extended beyond
`APN and PDP 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 belonging 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.225 [7]). For example it is worth highlighting
`that the operator can have postpaid subscribers on credit control by using on-line charging mechanisms.
`
`The GPRS online charging solutions up to release 5 are built around CAMEL mechanisms that provide online access-
`and charging-control for GPRS - pertaining to PDP Contexts of an APN.
`
`The flow based charging architecture developed in this Technical Specification shall use generic native IP charging
`mechanisms to the extent possible in order to enable the reuse of the same charging solution and infrastructure for
`different type of IP-Connectivity Networks.
`
`Note:
`
`Providing differentiated service data flow based charging is a different function from providing
`differentiated traffic treatment on the IP-flow level. The operation of service data flow based charging
`shall not mandate the operation of service based local policy.
`
`In addition charging based on specific application services or protocols shall be supported.
`
`Backwards compatibility
`4.2
`The enhanced architecture shall be backwards compatible with release 5 charging capabilities. These new functions
`shall be compatible and coherent with the authentication, authorization, PDP context management, roaming and other
`functions provided by the release 5 architecture.
`
`It shall be possible to collect data volumes per PDP context for use in billing and operational management systems.
`
`It shall be possible to derive data volumes which are not subject to service data flow based charging. The data volumes
`may be charged according to the GPRS mechanisms.
`
`4.3
`
`Charging models
`
`4.3.1 General
`When developing the charging solutions, the following charging models should be considered, even though the full
`solution to support the models may not be within the scope of this TS.
`
`Shared revenue services shall be supported. In this case settlement for all parties shall be supported, including the third
`parties that may have been involved providing the services.
`
`The charging solution shall allow various charging models such as:
`
`- Volume based charging;
`
`- Time based charging.
`
`Editors note: Additional charging models that are event and service based require further investigation.
`
`3GPP
`
`

`
`
`
` Release 6
`
`10
`
`3GPP TS 23.125 V2.0.0 (2004-03)
`
`It shall be possible to apply different rates when a user is identified to be roaming from when the user is in the home
`network.
`
`It shall be possible to restrict special rates to a specific service, e.g. allow the user to download a certain volume of data
`from one service for free, but this allowed volume is not transferable to other services. It shall be possible also to apply
`special rates based on the time of day.
`
`It shall be possible to enforce per-service usage limits for a service data flow using online charging on a per user basis
`(may apply to pre-paid and postpaid users).
`
`In the case of online charging, and where information is available to enable service data flow packets to be associated
`with a specific PDP context, it shall be possible to perform rating and allocate credit depending on the characteristics of
`the resources allocated initially (in the GPRS case, the QoS of the PDP context).
`
`The flow based bearer level charging can support dynamic selection of charging to apply. A number of different inputs
`can be used in the decision to identify the specific charging to apply. For example, a service data flow may be charged
`with different rates depending on what QoS is applicable. The charging rate may thus be modified when a bearer is
`created or removed, to change the QoS provided for a service data flow.
`
`The charging rate or charging model applicable to a service data flow may also be changed as a result of events in the
`service (e.g. insertion of a paid advertisement within a user requested media stream). The charging model applicable to
`a service data flow may also change as a result of events identified by the OCS (e.g. after having spent a certain amount,
`the user gets to use some services for free).
`
`In the case of online charging, it shall be possible to apply an online charging action upon TPF events (e.g. re-
`authorization upon QoS change).
`
`4.3.2 Examples of Service Data Flow Charging
`There are many different services that may be used within a network, including both user-user and user-network
`services. Service data flows from these services may be identified and charged in many different ways. A number of
`examples of configuring charging rules for different service data flows are described below.
`
`A network server provides an FTP service. The FTP server supports both the active (separate ports for control and data)
`and passive modes of operation. A charging rule is configured for the service data flows associated with the FTP server
`for the user. The charging rule uses a filter specification for the uplink that identifies packets sent to port 20 or 21 of the
`IP address of the server, and the origination information is wildcarded. In the downlink direction, the filter specification
`identifies packets sent from port 20 or 21 of the IP address of the server.
`
`A network server provides a “web” service. A charging rule is configured for the service data flows associated with the
`HTTP server for the user. The charging rule uses a filter specification for the uplink that identifies packets sent to port
`80 of the IP address of the server, and the origination information is wildcarded. In the downlink direction, the filter
`specification identifies packets sent from port 80 of the IP address of the server.
`
`The same server also provides a WAP service. The server has multiple IP addresses, and the IP address of the WAP
`server is different from the IP address of the web server. The charging rule uses the same filter specification as for the
`web server, except the IP address is different.
`
`An operator offers a zero rating for network provided DNS service. A charging rule is established setting all DNS
`traffic to/from the operators DNS servers as offline charged. The data flow filter identifies the DNS port number, and
`the source/destination address within the subnet range allocated to the operators network nodes.
`
`An operator has a specific charging rate for user-user VoIP traffic over the IMS. A charging rule is established for this
`service data flow. The filter information to identify the specific service data flow for the user-user traffic is provided by
`the P-CSCF.
`
`3GPP
`
`

`
`
`
` Release 6
`
`11
`
`3GPP TS 23.125 V2.0.0 (2004-03)
`
`5
`
`Flow Based Charging Concepts
`
`Overview
`5.1
`Editor's note: This clause is planned to contain the relevant descriptions of the overall function for the flow based
`charging.
`
`The following functions are provided by the network for service data flow based charging. This applies to both online
`and offline charging unless otherwise specified:
`
`-
`
`Identification of the service data flows that need to be charged individually (e.g. at different rates);
`
`- Provision and control of charging rules on service data flow level;
`
`- Reporting of service data flow level byte counts;
`
`- Event indication according to on-line charging procedures (e.g. sending AAA Accounting Stop) and, optionally,
`following this particular event, taking appropriate actions on service data flow(s) according to the termination
`action.
`
`- Event indication and event monitoring by the TPF and following this particular event, taking the appropriate on-
`line charging actions.
`
`Charging rules
`5.2
`Charging rules contain information that allow for filtering of traffic to identify the packets belonging to a particular
`service data flow, and allow for defining how the service data flow is to be charged. The following apply to charging
`rules:
`
`- The charging rules for bearer charging are defined by the operator.
`
`- These charging rules are made available to the Traffic Plane function for both offline and online charging.
`
`- Multiple charging rules are supported simultaneously per user.
`
`- Filtering information within a charging rule is applied through filtering functionality at the Traffic Plane
`Function to identify the packets belonging to a particular service data flow.
`
`- Charging rules with dynamically provisioned filtering information (i.e. made available to the Traffic Plane
`Function) are supported in order to cover IP service scenarios where the filtering information is dynamically
`negotiated (e.g. negotiated on the application level (e.g. IMS)).
`
`- Pre-defined charging rules are supported.
`
`- Elements of charging rules may be statically configured at the Traffic Plane Function, or dynamically
`provisioned.
`
`Note-i: The mechanism to support use of elements statically pre-defined in the TPF (e.g. filter information) is for
`stage 3 development.
`
`Note-ii: The stage 3 development may also evaluate providing an optimisation to support dynamic provisioning of
`an entire charging rule pre-defined in the TPF.
`
`- Pre-defined filters may support extended capabilities, including enhanced capabilities to identify packets
`associated with application protocols.
`
`- There may be overlap between the charging rules that are applicable. Overlap can occur between:
`
`- multiple pre-defined charging rules in the TPF;
`
`3GPP
`
`

`
`
`
` Release 6
`
`12
`
`3GPP TS 23.125 V2.0.0 (2004-03)
`
`- charging rules pre-defined in the TPF and rules from the Service Data Flow Based Charging Rules
`Function, which can overlay the pre-defined rules in the TPF.
`
`The precedence identified with each charging rule shall resolve all overlap between the charging rules. When
`overlap occurs between a dynamically allocated charging rule and a pre-defined charging rule at the TPF, and
`they both share the same precedence, then the dynamically allocated charging rule shall be used.
`
`- Charging rules contain information on:
`
`- How a particular service data flow is to be charged: online/offline;
`
`-
`
`In case of offline charging whether to record volume- or time-based charging information;
`
`- Charging key;
`
`- Service data flow filter(s);
`
`- Precedence.
`
`- Once the charging rule is determined it is applied to the service data flow at the Traffic Plane Function and
`packets are counted and categorised per the rule set in the charging rule.
`
`- Separate charging rules can be provided for downlink and uplink.
`
`- Charging rules can be configured for both user initiated and network initiated flows.
`
`- Charging rules can change and be overridden, e.g. for a previously established PDP context in the GPRS case,
`based on specific events (e.g. IM domain events or GPRS domain events, credit control events).
`
`- Different charging rules can be applied for different users or groups of users.
`
`- Different charging rules can be applied based on the location of the user (e.g. based on identity of the roamed to
`network).
`
`- For GPRS, charging rule assignment can occur at PDP context establishment and modification.
`
`- For GPRS, the charging rules can be dependent on the APN used.
`
`Service data flow filters and counting
`5.3
`This section refers to the filtering that identifies the service data flows that need to be charged individually (e.g. at
`different rates). Basic example: look for packets of one service, e.g. to and from a server A.
`
`- Separate filtering and counting can be applied for downlink and uplink.
`
`- Different granularity for service data flow filters identifying the service data flow is possible e.g.
`
`- Filters based on the IP 5 tuple (source IP address, destination IP address, source port number, destination
`port number, protocol ID of the protocol above IP). Port numbers and protocol ID may be wildcarded. IP
`addresses may be wildcarded or masked by a prefix mask.
`
`- Special filters which look further into the packet, or require other complex operation (e.g. maintaining
`state) may be pre-defined in the TPF and invoked by the CRF using standardised means. Such filters may
`be used to support filtering with respect to a service data flow based on the transport and application
`protocols used above IP. This shall be possible for HTTP and WAP. This includes the ability to
`differentiate between TCP, Wireless-TCP according to WAP 2.0, WDP, etc, in addition to differentiation
`at the application level. Filtering for further application protocols and services may also be supported.
`
`-
`
`-
`
`In the case of GPRS, the traffic plane function supports simultaneous independent filtering on service data flows
`associated with all, and each individual active PDP contexts; that is, primary and secondary PDP contexts, of one
`APN.
`
`In case of no applicable filters for a service data flow, an operator configurable default charging should be
`applied. The default charging may use accounting information provided by FBC, or may use accounting
`
`3GPP
`
`

`
`
`
` Release 6
`
`13
`
`3GPP TS 23.125 V2.0.0 (2004-03)
`
`information provided by other charging mechanisms available for the IP-Connectivity Access Network (e.g.
`existing GPRS charging mechanisms).
`
`- The service data flow filters and counting are applied by the TPF (the GGSN in the case of GPRS).
`
`
`
`packet flow A
`
`packet flow B
`
`
`
`uplink
`counter
`
`service
`data
`flow
`filter
`1
`
`service
`data
`flow
`filter
`2
`
`service
`data
`flow
`filter
`3
`
`
`
`
`
`
`down-
`link
`counter
`
`service data flow
`
`packet flow C
`
`packet flow D
`
`Figure 5.1 – Relationship of service data flow, packet flow and service data flow filter
`
`Reporting
`5.4
`This refers to the differentiated charging information being reported to the charging functions. Basic example: those 20
`packets were in rating category A, include this in your global charging information.
`
`- The Traffic Plane function shall report bearer charging information for online charging;
`
`- The Traffic Plane function shall report bearer charging information for offline charging;
`
`- Charging information is reported based on the application of the bearer charging rules in the TPF (service data
`flow related charging information), and in the case of GPRS, a