3G TS 22.115 3.2.

0 (1999-10)
Technical Specification

3rd Generation Partnership Project; Technical Specification Group Services and System Aspects Service aspects; Charging and Billing (3G TS 22.105 version 3.2.0)

The present document has been developed within the 3 Generation Partnership Project (3GPP ) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification. TM Specifications and reports for implementation of the 3GPP system should be obtained via the 3GPP Organisational Partners' Publications Offices.

rd

TM

3G TS 22.105 version 3.2.0

3G TS 22.115 3.2.0 (1999-10)

Reference
DTS/TSGS-0122115U

Keywords
<keyword[, keyword]> All rights reserved.

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.
1999, 3GPP Organizational Partners (ARIB, CWTS, ETSI, T1, TTA,TTC).

3GPP

3G TS 22.105 version 3.2.0

3G TS 22.115 3.2.0 (1999-10)

Contents
Foreword ................................................................................................................................................4 1 2 3
3.1 3.2

Scope ............................................................................................................................................5 Normative references.....................................................................................................................5 Definitions and abbreviations ...........................................................................................................5

Definitions............................................................................................................................................................................. 5 Abbreviations....................................................................................................................................................................... 6

4
4.1

Requirements.................................................................................................................................6
Cross Phase Compatibility for Release 99........................................................................................................................ 6

5
5.1 5.1.1 5.1.2 5.1.3 5.2 5.2.1 5.2.2 5.2.3 5.2.4

Generation of Call Detail Records ...................................................................................................6

Call Detail Record Requirements ....................................................................................................................................... 7 Information provided by the user............................................................................................................................... 7 Information provided by the serving network .......................................................................................................... 7 Charged Party................................................................................................................................................................. 8 Special Cases ........................................................................................................................................................................ 8 Long calls ........................................................................................................................................................................ 8 Multimedia calls ............................................................................................................................................................. 8 E-Commerce.................................................................................................................................................................... 8 Volume Based Charging ............................................................................................................................................... 8

6
6.1

Transfer of Charging Information ....................................................................................................8

Integrity, Secrecy and Validation of Content and Receipt of Charging Information................................................. 9

7
7.1 7.2 7.2.1 7.2.2 7.3 7.3.1 7.4

Accounting and Settlement..............................................................................................................9

Delegation of charging authority ...................................................................................................................................... 9 Fraud Control........................................................................................................................................................................ 9 Fraud Control by the Home Environment.................................................................................................................. 9 Fraud Control by the Serving Network .................................................................................................................... 10 Cost Control................................................................................................................................................................. 10 Cross Phase Compatibility................................................................................................................................... 10 Inter-network Settlement................................................................................................................................................... 10

8
8.1 8.2

Automatic Roaming Agreements...................................................................................................10

Routing the Registration Request................................................................................................................................... 11 Settlement of charges ........................................................................................................................................................ 11

Annex A (informative) : Change history ........................................................................................... 12 History..................................................................................................................................................13

3GPP

3G TS 22.105 version 3.2.0

3G TS 22.115 3.2.0 (1999-10)

Foreword
This Technical Specification has been produced by the 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 this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version 3.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 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 specification;

3GPP

3G TS 22.105 version 3.2.0

3G TS 22.115 3.2.0 (1999-10)

Scope

This Technical Specification describes the Service Aspects of charging and billing of the Universal Mobile Telecommunications System (UMTS). This standard is not intended to duplicate existing standards or standards being developed by other groups on these topics, and will reference these where appropriate. This standard will elaborate on the charging requirements described in the Charging Principles in UMTS 22.01 Service Principles. It will allow the generation of accurate charging information to be used in the commercial and contractual relationships between the parties concerned.

Normative references

The following documents contain provisions which, through reference in this text, constitute provisions of the present document. [1] [2] [3] [4] 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. A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. 3GTS 22.01 Service aspects; Service Principles; GSM 02.31: "Fraud Information Gathering System (FIGS); Service description - Stage 1". TS 22.078: Customised Applications for Mobile network Enhanced Logic (CAMEL); Service definition Stage 1 TS 22.086: "Advice of Charge (AoC) Supplementary Services; Stage 1

3
3.1

Definitions and abbreviations

Definitions

For the purposes of this TS, the definitions in [1] are supplemented by the following definitions: Accounting: The process of apportioning charges between the Home Environment, Serving Network and User. Billing: A function whereby CDRs generated by the charging function are transformed into bills requiring payment. Call Detail Record (CDR): A formatted collection of information about a chargeable event (e.g. time of call set-up, duration of the call, amount of data transferred, etc) for use in billing and accounting. For each party to be charged for parts of or all charges of a chargeable event a separate CDR shall be generated, i.e more than one CDR may be generated for a single chargeable event, e.g. because of its long duration, or because more than one charged party is to be charged. Chargeable Event: An activity utilising telecommunications network infrastructure and related services for user to user communication (e.g. a single call, a data communication session or a short message), or for user to network communication (e.g. service profile administration), or for inter-network communication (e.g. transferring calls, signalling, or short messages), or for mobility (e.g. roaming or inter-system handover), which the network operator wants to charge for. The cost of a chargeable event may cover the cost of sending, transporting, delivery and storage. The cost of call related signalling may also be included.

3GPP

3G TS 22.105 version 3.2.0

3G TS 22.115 3.2.0 (1999-10)

Charged Party: A user involved in a chargeable event who has to pay parts or the whole charges of the chargeable event, or a third party paying the charges caused by one or all users involved in the chargeable event, or a network operator. Charging: A function whereby information related to a chargeable event is formatted and transferred in order to make it possible to determine usage for which the charged party may be billed. Real time: Time, typically in number of seconds, to perform the on-line mechanism used for fraud control and cost control. Settlement: Payment of amounts resulting from the accounting process. Short time: Time, typically in number of minutes, to perform the off-line mechanism used for accounting.

3.2
CDR

Abbreviations
Call Detail Record

For the purposes of the present document, the following abbreviations apply:

4
-

Requirements
to provide a call detail record for all charges incurred and requiring settlement between the different commercial roles; to allow fraud control by the Home Environment and the Serving network; to allow cost control by the charged party; to provide at the beginning of a chargeable event an indication to the charged party (if involved in the chargeable event) of the charges to be levied for this event; to allow itemised billing for all services charged to each subscription, including voice and data calls, and services offered by home environments.

The main new requirements for UMTS charging and accounting are:

These new requirements will allow users more freedom to obtain service when roaming, whilst providing effective cost and credit control for the Home Environment and User.

4.1

Cross Phase Compatibility for Release 99

There are no earlier releases of the UMTS standards for which backward compatibility of equipment implementing these standards is required. It is envisaged that UMTS will evolve beyond Release 99, for example with the addition of a number of new requirements for charging and billing; these are noted in the appropriate sections below. The technical standards for Release 99 should be developed in such a way that it is possible and practical to introduce these requirements, ideally in a backward compatible manner.

Note:

When a change is introduced which affects the UMTS technical standards, it is said to be 'backward compatible' if existing equipment can continue to operate and perform correctly with equipment that conforms to the new implemenation.

Generation of Call Detail Records

The standard shall support the creation and transfer of charging records in order to facilitate:

3GPP

3G TS 22.105 version 3.2.0

3G TS 22.115 3.2.0 (1999-10)

interworking with pre-UMTS systems (e.g. GSM); fraud management procedures; detailed itemised billing.

5.1

Call Detail Record Requirements

Call Detail Records shall be generated in the Serving Network to record chargeable User or Mobile Station activity and inter-carrier connections. Some of the information is provided by the user, other information is only available in the network element of the serving network. Depending on the type of chargeable event some of the information may not be available or might not be required.

5.1.1
-

Information provided by the user

User identity used for authentication; Home environment identity; Terminal Identity and Terminal Class; Destination endpoint identifier for service requested (e.g. B number); Resource requested (e.g. bandwidth, connectionless); QoS parameters (e.g. maximum delay).

The users user equipment that is incurring the charge shall provide the following information to the serving network:

5.1.2
-

Information provided by the serving network

All of the information listed in section above (Information provided by the user); Serving network identity; Recording network element identity; Universal Time (UT) at which the service request was initiated; Universal Time (UT) at which resources were provided for the service; Resource allocated to the user; Quantity of data transferred both to and from the user; QoS provided to the user; Location of the user in the standard format used for UMTS location based services (e.g. geographical coordinates, Cell ID); whether GSM Optimal Routing was applied; If IN or CAMEL services were applied, the service parameters and the actually used destination number and calling party number identification; Time duration covered by this call record to an accuracy of at least 1 second; Unique identity of the chargeable event which allows the billing system to correlate all records belonging to the same chargeable event;

The serving network serving the user shall provide the following information to the home environment:

3GPP

3G TS 22.105 version 3.2.0

3G TS 22.115 3.2.0 (1999-10)

Unique CDR identity (unique per network element in a period of about 100 days).

5.1.3

Charged Party

For subscription related chargeable events the CDR shall indicate the charged party, i.e. normally the calling party. As alternative it should be possible to apply reverse charging or to charge the event to a party not involved in the event itself (e.g. a company as VPN subscriber). It should be possible for multiple leg calls (e.g. forwarded, conference or roamed) to be charged to each party as if each leg was separately initiated. However, in certain types of call, the originating party may wish/be obliged to pay for other legs (e.g. SMS MO may also pay for the MT leg.). It shall be possible to change the chargeable party at the call set-up. In case of inter-network chargeable events, the CDR usually does not contain the charged party, but it can be derived from network configuration information contained in the CDR. For each party to be charged for a chargeable event or parts of it a separate CDR shall be generated.

5.2
5.2.1

Special Cases
Long calls

The advent of packet data services, which can extend for very long periods of time (days, weeks etc), although at low cost because charges are based on data throughput, may mean that billing records are only output at the end of very long periods. For this reason the serving network shall support the generation of call records also during the life of the packet data session, either when some charge value is reached or some duration or both, to allow for both charging settlement and cost control.

5.2.2

Multimedia calls

During one call the user may invoke different services like speech, data transmission, video and audio, which may lead to a separate CDR for each service. If several CDRs will be the result of each multimedia call, the billing system shall be able to correlate these records and to indicate to the user on the bill that they belonged to one call.

5.2.3

E-Commerce

The UMTS system may be used to trade soft goods (e.g. information, video, audio), or hard goods (e.g. books) of high or low value per item between the user and a merchant. It shall be possible for such merchants to charge users directly for services they provide. Electronic payment mechanisms are or shall be made available through other standards (micropayment, credit card payment, etc), and therefore are outside the scope of this specification UMTS shall not prohibit the use of these mechanisms, and, where possible, shall provide the basic communications transport to allow them to be used effectively. However, if the serving network acts as merchant of soft goods, it may charge the user directly, creating a CDR as described above or using micropayment mechanisms.

5.2.4 Volume Based Charging

It shall be possible to charge for the total volume of data/packets sent and received by the user.

Transfer of Charging Information

The efficient transfer of charging information between serving networks and from serving networks to home environments requires a standardised interface between these entities. It shall be possible to define different time intervals for the transfer of charging information between serving network and home environment (e.g. when a chargeable event occurs, when a chargeable event is initiated by the user, when a chargeable event terminates, at regular

3GPP

3G TS 22.105 version 3.2.0

3G TS 22.115 3.2.0 (1999-10)

intervals during a chargeable event). The format of the charging information exchanged (see 5.1) shall be standardised. It shall be possible for the relevant parties to agree minimum and maximum age of call information tranfered between themselves.

6.1

Integrity, Secrecy and Validation of Content and Receipt of Charging Information

The transmission mechanism for charging information collected in 5.1 above shall ensure its integrity and secrecy. A mechanism to validate the source and integrity of the information shall be provided so that: The home environment shall be able to validate the source and integrity of the charging information supplied by the serving network; The serving network shall be able to validate the source and integrity of the charging information supplied by the user; The serving network shall have proof that services were provided to a specified user.

Accounting and Settlement

The serving network shall collect and process the charging data generated in its network elements. The record of each individual transaction shall be reported to the home environment at short time intervals in order to provide itemised bills, and to deal with any disputes regarding charges both for users and for other UMTS networks and home environment. The standard shall support the transfer of charging data at different intervals as required by the Home Environment (e.g. short time intervals, real time, other regular intervals).

7.1

Delegation of charging authority

The registration process allows the home environment to authenticate users before they incur any charges. Once authenticated, the home environment then delegates authority to the serving network operator with which he has a direct commercial relationship to incur charges for services supplied to that user. The direct commercial relationship may be with either the serving network operator if known directly by the home environment or a network operator known to the home environment. This procedure uses each network as trusted third parties in a chain of delegation between entities, thus allowing commercial transactions between entities who have no direct commercial dealings. There shall be an authentication procedure between all entities in the UMTS system which have a commercial relationship.

7.2

Fraud Control

A mechanism to control fraud shall be provided by the serving networks and the home environment.

7.2.1

Fraud Control by the Home Environment

Charging information shall be collected by the home environment in real time from all serving networks which its users are allowed to use. The billing system in the home environment shall process the information in real time and provide the means to set charge thresholds per time interval upon which some actions may be started, such as informing the customer care centre or even barring the user in the HLR. It shall be possible for the Home Environment to define different time intervals for the collection and the processing of charging information (e.g. real time, short time, other regular intervals)

3GPP

3G TS 22.105 version 3.2.0

10

3G TS 22.115 3.2.0 (1999-10)

7.2.2

Fraud Control by the Serving Network

Charging information shall be collected from the network elements and processed in real time. This will allow the serving network to always be aware of the exposure to visitors. A limit for the accumulated charges for all visitors from one home environment or a limit per visitor may be agreed between the home environment and the serving network. It shall be possible for the Serving Network to define different time intervals for the collection and the processing of charging information (e.g. real time, short time, other regular intervals)

7.3 Cost Control

A mechanism shall be standardised providing an indication to the user (if involved in the chargeable event) of the charges to be levied for a chargeable event. This mechanism shall be able to handle all possible charging scenarios, and all service and tariff variants that the home environment and the serving network may offer to the user. The user shall be able to set in his home environment a limit for the accumulated charges per time interval. Upon exceeding this limit or prior to incurring a charge which would exceed the limit, certain actions may be desired by the user: notification to the user, requesting to extend the limit, or Home Environment barring allowing no further originating calls, or Home Environment barring cancelling the roaming permission.

7.3.1

Cross Phase Compatibility

For Release 99 the cost control mechanism may be based on Advice of Charge. However the Release 99 standards should not prevent the future implementation of the full Cost Control requirements. The Release 99 standards should allow these new features to be introduced in a backward compatible manner; specifically terminals conforming to Release 99 standards should continue to support the Release 99 service requirements when operating with future implementations of Advice of Charge in the Home Environment.

7.4

Inter-network Settlement

Mechanisms shall also be provided to allow inter-network settlement of charges on a bulk basis. The same mechanisms shall be used between home environments and serving networks. This will allow each of these parties to meter the total input and output of charges and thus determine the payments required on a periodic basis between each of the parties with which they directly interact. The mechanisms used shall allow each of the parties to meter charge flows independently, with the aim of matching the values recorded at both sides of the same interface. The imbalance in charge flow shall be accumulated in short time, such that each entity can be informed when a threshold has been exceeded and determine whether to continue.

Automatic Roaming Agreements

Support for the requirements in this section is not required in Relase 99. However the Release 99 standards should not prevent the future implemenation of this requirement in a backward compatible manner (eg a roaming broker enabled Home Environment should inter-operate with a R99 Serving Network). It is a requirement that UMTS users shall be able to obtain service and use chargeable services with networks with whom neither they nor their home environment have any direct commercial agreement. This shall be enabled by interworking via trusted third parties. Each Home Environment shall interwork with one or more serving network operators, with whom they would negotiate a commercial roaming agreement and test the interworking. Any user wishing to use the services of a particular serving network would register with that serving network, who would either directly or indirectly interwork with the home environment. Fraud and cost control mechanisms shall be used to ensure that charges incurred for UMTS services do not exceed the credit limits set. This can be applied for the user and the other roles involved in commercial dealings. In practice, any serving network shall be capable of operating as a roaming broker.

3GPP

3G TS 22.105 version 3.2.0

11

3G TS 22.115 3.2.0 (1999-10)

User

Serving Network Operator

Roaming Broker

Home Environment

Registration Request Authorisation Online Signalling Information

Call Detail Records

Figure 1: Registration and Roaming Process

8.1

Routing the Registration Request

The same mechanisms used for routing calls and resolving addresses shall be used to route the subscription identity back to its Home Environment . of the standard shall support a routing identification mechanism to allow a serving network, which does not maintain its own list of all known HE, to determine the appropriate route to reach a given HE. A number of alternative routes may be possible, and ideally the system should be capable of determining the lowest cost to the end user. Typically, smaller networks will only have a limited number of external connections to other networks or clearing houses, but may not know which one to use for an unknown (new) HE. In this case, the serving network may make a number of inquiries for each route to determine the lowest cost route to handle the call.

8.2

Settlement of charges

Settlement of charges incurred by a user shall be on a wholesale basis between the different parties involved in the registration link. By authorising a user to register, or a roaming broker to pass that on, each party is in turn authorising charges up to a maximum credit limit with the adjacent party. Any charges levied can then be paid to the adjacent party on a wholesale basis at the end of a mutually agreed accounting period. Funds are thus passed between each party for the services supplied by the network operator in a serial fashion.

3GPP

3G TS 22.105 version 3.2.0

12

3G TS 22.115 3.2.0 (1999-10)

Annex A (informative) : Change history

Change history SMG No.
SMG#28
SA#3, Yokohama, Japan SP-99106 001r1

TDoc. No.

CR. No.

Section affected

New version
Version 3.0.0
Version 3.1.0

Subject/Comments
Approved
1. 2. Short time and real time defined. For multimedia calls (eg H324M) it is not always possible to identify the different media streams and not possible to define separate CDRs for the different media streams. 7.2.3 is restructured and the section is renamed The charging mechanism is also a function of the service and tariff variants in the serving network. The serving network should also be able to do fraud control. GSM 02.31 FIGS may be considered. A mobility event can also be an example of a chargeable event. It is here interpreted that the chargeable party can be changed at the call set-up.

3.

4.

5.

6.

7.

8.

9. Accumulated charges in the currency of the serving network should not be a CDR requirement.

SA#5, Kyongju, Korea

SP-99454

002 003

3.2.0

Charging Addition of Charging for Volume of Data and some edits

3GPP

3G TS 22.105 version 3.2.0

13

3G TS 22.115 3.2.0 (1999-10)

History
Document history
Date Status Comment

27 August 1996 3 February 1997

Version 0.0.1 Version 0.0.3

SMG 1 WPC output draft for editing purposes only Presented to SMG1 WPC meeting, London Incorporated changes agreed at Dec 96 Meeting including charging model and charge enquiry

20 April 1997

Version 0.0.4

Presented to SMG1 WPC meeting in Sophia Antipolis Incorporated text submitted at Feb 97 meeting

4 June 1997

Version 1.0.0

Proposed Version 1 incorporating changes discussed at SMG1 WPC meeting in Antwerps, June 97

23 June 1997

Version 1.0.2

Incorporated remaining changes discussed at SMG1 WPC meeting in Antwerps, June 97 Preparation for SMG1 UMTS Helsinki meeting, incorporating text from reports 22.24 and 22.71 Incorporated comments from 22.24, 22.71 developed at SMG1 UMTS Meeting in Helsinki

27 Nov 1997

Version 1.1.0

4 Dec 1997

Version 1.2.0

26 April 1999

Version 3.1.0

(continued)

3GPP

3G TS 22.105 version 3.2.0

14

3G TS 22.115 3.2.0 (1999-10)

(concluded) Document history 8 Dec 1997 5 November 1998 Version 1.2.2 Version 1.3.0 Format and editorial changes by ETSI Sec for SMG#24 Incorporate changes discussed at SMG1 Rome, including reflecting changes to 22.01 role model. Accept Changes and send to editing SMG1 Rome Tdoc 98-0859 Agreed by correspondence. Reviewed by Rapporteur Jan 13, 1999 To be presented at SMG#28 for Approval Approved at SMG#28 Reformatted for TSG SA SA#3, Yokohama, Japan SA#5, Kyongju, Korea

12 January 1999

Version 1.3.1

27 January 1999 February 1999 March 1999 May 1999 October 1999

Version 2.0.0 Version 3.0.0 Version 3.0.1 Version 3.1.0 Version 3.2.0

3GPP