ETSI TS 122 115 V14.3.0 (2020-01)

Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Service aspects; Charging and billing (3GPP TS 22.115 version 14.3.0 Release 14)

RTS/TSGS-0122115ve30

General Information

• Status: Published
• Publication Date: 12-Jan-2020
• Technical Committee: 3GPP SA 1 - Services
• Current Stage: 12 - Completion
• Completion Date: 13-Jan-2020

Standards Content (Sample)

TECHNICAL SPECIFICATION
Digital cellular telecommunications system (Phase 2+) (GSM);
Universal Mobile Telecommunications System (UMTS);
LTE;
Service aspects;
Charging and billing
(3GPP TS 22.115 version 14.3.0 Release 14)

3GPP TS 22.115 version 14.3.0 Release 14 1 ETSI TS 122 115 V14.3.0 (2020-01)

Reference
RTS/TSGS-0122115ve30
Keywords
GSM,LTE,UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
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 other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2020.
All rights reserved.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.

3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners. ®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
3GPP TS 22.115 version 14.3.0 Release 14 2 ETSI TS 122 115 V14.3.0 (2020-01)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables 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); 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 (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Legal Notice
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 3GPP and ETSI identities can be found under http://webapp.etsi.org/key/queryform.asp.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
3GPP TS 22.115 version 14.3.0 Release 14 3 ETSI TS 122 115 V14.3.0 (2020-01)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 5
1 Scope . 6
2 References . 6
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 7
4 Main Requirements and High Level Principles . 7
4.1 Cross Phase Compatibility . 9
4.2 Charging Entity Relationships . 9
4.3 Charging guidelines for IP-Multimedia services . 11
4.3.1 User Charging Requirements . 11
4.3.1.1 Session End Point Configurations . 11
4.3.1.2 Charging Principles For User Session Components . 12
4.3.1.3 Other Charging Requirements . 14
4.3.2 Roaming Charging Requirements . 14
4.3.3 Interconnect Charging Requirements. 15
4.3.4 Conveyance & Usage charging requirements . 16
rd
4.3.5 Charging 3 parties . 16
4.3.6 Advice of Charge (AoC) . 16
4.3.7 Service Aware Charging Requirements . 17
4.4 Additional Charging requirements for prepay services . 17
4.5 QoS and gating based on spending limit . 18
4.6 ProSe Charging Requirements . 18
4.7 Void . 19
4.8 Void . 19
5 Collection of charging information . 19
5.1 Charging information Requirements . 19
5.1.1 Information provided by the user . 19
5.1.2 Information provided by the serving network . 19
5.1.3 Charged Party . 20
5.1.4 Information provided by the third party accessed by the user . 21
5.2 Special Cases . 22
5.2.1 Long calls and sessions . 22
5.2.2 Multimedia calls . 22
5.2.3 Service Change . 22
5.2.4 E-Commerce . 22
5.2.5 Volume Based Charging . 22
5.2.6 VAS . 22
5.2.7 Usage of IP Multimedia service . 22
5.2.8 I- WLAN . 23
5.2.9 Charging for two( and multi)-phases services for IMS networks . 23
5.2.10 CSG charging requirements for UTRAN and E-UTRAN . 23
5.2.11 Inter-UE Transfer charging . 23
5.2.12 Selected IP Traffic Offload charging . 23
5.2.12A Charging requirements for IoT small data . 23
5.2.13 TV Service Support Requirements . 24
5.2.14 Accounting for Flexible Mobile Service Steering . 24
6 Transfer of Charging Information . 24
6.1 Integrity, Secrecy and Validation of Content and Receipt of Charging Information . 24
ETSI
3GPP TS 22.115 version 14.3.0 Release 14 4 ETSI TS 122 115 V14.3.0 (2020-01)
7 Accounting and Settlement . 24
7.1 Delegation of charging authority . 24
7.2 Fraud Control . 25
7.2.1 Fraud Control by the Home Environment . 25
7.2.2 Fraud Control by the Serving Network . 25
7.3 Cost Control . 25
7.3.1 Cross Phase Compatibility . 25
7.4 Inter-network Settlement . 25
8 Automatic Roaming Agreements . 26
8.1 Routing the Registration Request . 26
8.2 Settlement of charges . 27
Annex A (informative) : Change history . 28
History . 32

ETSI
3GPP TS 22.115 version 14.3.0 Release 14 5 ETSI TS 122 115 V14.3.0 (2020-01)
Foreword
rd
This Technical Specification (TS) has been produced by the 3 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.
ETSI
3GPP TS 22.115 version 14.3.0 Release 14 6 ETSI TS 122 115 V14.3.0 (2020-01)
1 Scope
The present document describes the Service Aspects of charging and billing of the 3GPP System.
The present document is not intended to duplicate existing standards or standards being developed by other groups on
these topics, and will reference these where appropriate. The present document will elaborate on the charging
requirements described in the Charging Principles in 3GPP TS 22.101 Service Principles. It will allow the generation of
accurate charging information to be used in the commercial and contractual relationships between the parties concerned.
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, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1] 3GPP TS 22.101: "Service aspects; Service Principles".
[2] 3GPP TS 22.066: "Support of Mobile Number Portability (MNP)".
[3] 3GPP TS 22.234: "Requirements for 3GPP system to wireless local area network (WLAN)
interworking".
[4] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications"
[5] 3GPP TS 22.086: "Advice of Charge (AoC) supplementary services"
[6] ETS 300 178: "Integrated Services Digital Network (ISDN); Advice of Charge: charging
information at call set-up time (AOC-S) supplementary service; Service description"
[7] ETS 300 179: "Integrated Services Digital Network (ISDN); Advice of Charge: charging
information during the call (AOC-D) supplementary service; Service description"
[8] ETS 300 180: "Integrated Services Digital Network (ISDN); Advice of Charge: charging
information at the end of the call (AOC-E) supplementary service; Service description"
[9] TS 183 047: "Telecommunications and Internet converged Services and Protocols for Advanced
Networking (TISPAN); NGN IMS Supplementary Services; Advice Of Charge (AOC)"
[10] TS 183 058: "Telecommunications and Internet Converged Services and Protocols for Advanced
Networking (TISPAN); SIP Transfer of IP Multimedia Service Tariff Information;Protocol
specification"
[11] void
[12] 3GPP TS 22.220, "Service requirements for Home NodeBs and Home eNodeBs"
[13] 3GPP TS 22.278, "Service requirements for the Evolved Packet System (EPS)"
ETSI
3GPP TS 22.115 version 14.3.0 Release 14 7 ETSI TS 122 115 V14.3.0 (2020-01)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the definitions in [4] are supplemented by the following definitions:
Prepay service: A prepay service allows a subscriber to pay in advance for the use of specific services, the prepay account
may be updated each time the subscriber uses the services related to that account.
Real time: Time, typically in number of seconds, to perform the on-line mechanism used for fraud control and cost
control.
Session: logical connection between parties involved in a packet switched based communication This term is used for
IP connections rather than the term "call" that is normally used for a connection over conventional (circuit switched)
systems.
Note: Information about charging is typically collected in Charging Data Records (CDR).
Local Charging Zone (LCZ): A logical grouping of a number of cells, where a special tariff applies for a select group
of users. A network may have a number of LCZs. A LCZ does not necessarily need to be aligned with an LA or RA, i.e.
the border of LCZ may not be the border of an LA or RA.
3.2 Abbreviations
For the purposes of the present document the definition of abbreviations in [4] apply.
4 Main Requirements and High Level Principles
The main new requirements for 3GPP system charging and accounting are:
- to provide charging information 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;
- to enable the Home environment to provide a Prepay Service and to enable the serving network to support that
Prepay Service for the Home environment’s subscribers;
- to allow interconnect (inter-operator) charging including mobile/fixed operator to mobile/fixed operator (circuit
switched & IP), and mobile/fixed operator to IP network provider; and mobile/fixed operator to I-WLAN
operator;
rd
- to allow Network operator to 3 party supplier (e.g. Value Added Service Provider) charging;
- to provide details required for Customer Care purposes;
- to support the shared network architecture so that end users can be appropriately charged for their usage of the
shared network, and network sharing partners can be allocated their share of the costs of the shared network
resources.
The high level principles that will guide the charging requirements are summarised as follows:
ETSI
3GPP TS 22.115 version 14.3.0 Release 14 8 ETSI TS 122 115 V14.3.0 (2020-01)
- It shall be possible to charge separately for each type of medium used (e.g. voice, video, data) in a session and
for each service used (e.g. voice call, streaming video, file download);
- It shall be possible to charge for different levels of QoS applied for and/or allocated during a session for each
type of medium or service used;
- It shall be possible to charge each "leg" of a session separately. This includes the incoming and outgoing legs
and any forwarded/redirected legs. (Note: The legs mentioned here are logical legs, i.e. not necessarily identical
to actual signal and traffic flow. Even though tromboning may be avoided by optimal routing, the operator
should still be able to charge for the ‘virtual legs’ of the call);
- It shall be possible to charge unsuccessful calls and sessions (e.g. for billing purposes, to provide the user a full
documentation of his call attempts);
- The user can be charged according to the service used irrespective of the technology used to deliver it. (That is,
the charge is not derived from whether 2G or 3G is used);
- The user can be charged according to the technology used to deliver a service. (That is, different charges can be
applied on 2G and 3G);
- It shall be possible to charge a user according to the network resources used. For example, if a large bandwidth is
required to use high quality video, the user could be charged accordingly. This is related to charging by QoS;
- It shall be possible to charge users flexibly for the use of extra resources (in at least the same network) for all
legs of the call. For example, if a video component is added to a voice call the use of extra radio resource at both
ends of the call could be paid for by each user in the call or totally by the initiating user;
- It shall be possible to suppress charging for certain types of connection e.g. when a customer receives tones or
network announcements or during sessions such as automated pre-pay top-up;
rd
- It shall be possible to apply different charging based on tariff information provided by a 3 party. This tariff
information may change during the use of the service (e.g. based on menu selection in a voice response menu).
In this case the requirement applies both for customer-charging and interconnect-charging;
- It shall be possible for the home network to charge its customers while roaming in the same ways as when they
are at home. For example, if duration based charging is used for charging for streaming music in the home
network, then it shall be possible to apply the same principle when the user is roaming;
- It shall be possible for operators to have the option to apply charging mechanisms that are used in GSM/GPRS.
For example for duration of a voice call, for the amount of data transmitted (eg for streaming, file download,
browsing) and for an event (one-off charge);
- It shall be possible for a network operator to charge its users for activities while roaming so that the home
network will get the capability to raise service charges depending on the roamed to network, e.g. because of inter
operator charges for the use of service capabilities within the visited network which will in general depend on
the serving network. The ability to supply all the necessary information for all the charging options will depend
on the capability of the visited network. For service capabilities which are provided by the home network,
however, it is required that the charging information is collected to allow to identify the serving network of the
served subscriber;
- It shall be possible for charging to be applied based on location, presence, push services etc.;
- The network may provide information to the UE so that the UE is able to notify and indicate to the user the
LCZs it is in. This allows the user to decide whether to accept/originate the service depending on the LCZs they
are in;
rd
- It shall be possible to charge using pre-pay, post-pay, advice of charge, 3 party charging techniques;
- It shall be possible for the home network to apply different tariffs to national calls and short messages
established/sent by their subscribers while roaming in their Home PLMN depending on whether or not the called
subscriber’s Home PLMN equals the calling subscriber’s Home PLMN, rather than on the called subscriber’s
MSISDN;
Note: This distinction is necessary only in the case, where the called subscriber's MSISDN may have been
ported by Mobile Number Portability.
ETSI
3GPP TS 22.115 version 14.3.0 Release 14 9 ETSI TS 122 115 V14.3.0 (2020-01)
- For circuit switched interconnection only a capability is required to collect information regarding user rate and
user protocol at the interconnection point so that e.g. the identification of CS video telephony at the
interconnection point for inter-network accounting purposes becomes possible.
These new requirements and principles 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
Where possible (e.g. services already defined within earlier releases), the charging information collected shall be
consistent with the information already provided
It is envisaged that 3GPP system will evolve beyond this Release with the addition of a number of new requirements for
charging and billing, 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 each release 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 3GPP 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 implementation.
4.2 Charging Entity Relationships
In the process of introduction of the all-IP technology there will be a mixture of different types of entities using
different types of technology.
The diagram below shows the different entities involved in charging and their relationships.
ETSI
3GPP TS 22.115 version 14.3.0 Release 14 10 ETSI TS 122 115 V14.3.0 (2020-01)

The types of entities and the relevant type of charging as shown on the diagram are as follows:
rd
- Users: retail charged by Mobile Network Operator or 3 Party Service Provider.
rd
- 3 Party Service Providers: wholesale charged by Mobile Network Operator.
- Other telecommunications operators: interconnect charging between Mobile Network Operator and non-IP
"circuit-switched" Network Operators for call traffic carried; usage charging between Mobile Network Operator
and IP-based Network Operators for session traffic carried.
- Other mobile operators: roaming charging between these entities, this may require different mechanisms for IP-
based types from the traditional "circuit-switched" types. Also, where mobile operators need to pass traffic to one
another, there will be interconnect charging for non-IP "circuit switched" types; usage charging for IP-based types.
- I-WLAN operators: where I-WLAN operators need to pass traffic to mobile operators or mobile operators to I-
WLAN operators, there may be roaming and usage charging.
- IP backbone carriers: conveyance charging Mobile Network Operators for traffic carried.
rd
- 3 Party content & application suppliers: supplier charging between Mobile Network Operators and Value
Added Service Providers for information exchanged.
rd
- 3 Party Portals: access charging between Mobile Network Operators and this entity.
- Internet: charge for capacity of connection between Mobile Network Operator and Internet. An Operator pays a
provider for a connection based on capacity, e.g. annual charge for a 2Mbit/s "pipe".
ETSI
3GPP TS 22.115 version 14.3.0 Release 14 11 ETSI TS 122 115 V14.3.0 (2020-01)
4.3 Charging guidelines for IP-Multimedia services
4.3.1 User Charging Requirements
This section describes the options required for the charging of end users. The network operator could charge users
rd
directly (retail charging) or charge a 3 party service provider (wholesale charging). These requirements can therefore
apply to retail and wholesale charging. Note that the word "session" is used to describe the connection between a user
and either another user or a service. This term is used for IP connections rather than the term "call" that is normally used
for a connection over conventional (circuit switched) systems.
The various ways that users can establish sessions and the main components are described. Also, the required charging
options are specified.
4.3.1.1 Session End Point Configurations
A variety of different connection configurations are possible for IP multi-media independently of the components of the
session being used. It should be possible to charge for the following types of sessions with the options identified. These
charging options should be applicable to each medium separately. Note that not all the charging options need to be used
and that some of the options can be used only if the particular party is using the resources of IMS:
The table below lists some example session scenarios and describes some of the possible charging options for each
scenario. The table does not list all possible session scenarios nor does it list all possible charging options for the scenarios.
Rather, the intent of the table is to emphasize the numerous charging options that shall be supported by an IP Multimedia
System due to the complexity of sessions possible. The charging options shall adequately account for all session resources
used in order to enable the operators to apply flexible billing policies and to satisfy regional and/or national regulatory
policies.
In general, any session shall allow for the following charging options:
• To apply the "Calling Party Pays" charging principle;
rd
• A 3 party to be charged for all or part of the session;
rd
• Split charging between any of the parties, including 3 parties;
• Session setup and session resources to have different charging rules. Different rules would be applied for example,
in a scenario where A calls an advertising number, say B. B could be a web-based toy advertisement number, for
example. In this scenario, A could pay for the initiation fee (session setup), and B could pay for the session
resource.
• Any party can add another media to the current session in progress and any of the parties (not necessarily the one(s)
being charged for the current session) can be charged for the additional media. For example, A calls B and A is
paying for the audio; B adds a wireless video image to the call and pays for that portion. The individual resource
set-up and usage should be separately identified. This supports the "Calling Party Pays" model;
• During an active session, media types can change (e.g. audio changed to data) and shall be charged for
appropriately. It is thus necessary to be able to detect a change of media during a session so that different rating
may be applied.
It should also be noted that during a multi-party session, normally if the charged party drops off the session, all
components being charged to that party should drop. But it is foreseeable to support a service option that allows the
charged party to continue to be charged even if they drop off the session. The charging rules should support this option.
ETSI
3GPP TS 22.115 version 14.3.0 Release 14 12 ETSI TS 122 115 V14.3.0 (2020-01)

No CONNECTION DESCRIPTION CHARGING OPTIONS REQUIRED
1 A sets up a session to B A simple connection between 2 A pays for the session set-up to B
subscribers or a subscriber and a A pays for the session resource to B
B pays for the session resource to A
service (eg voicemail)
2 A sets up a session to B A simple connection where B is a "toll B pays for the session set-up
free" (800) type service B pays for the session resource
A pays for part of the session resource
(i.e. allowing split charging between A &
B)
A requests session with B, B A pays for the session set-up to B
3 This is redirection. The connection
redirects to C path is not set up to B from A, instead A pays for the session resource to C
A is told to set up a connection direct C pays for the session resource to A
to C A pays for the session resource as
though it were to B and B pays for the
session resource to C as though it came
from B
A requests session with B, B A pays for the session set-up to B
4 This is normal forwarding as in GSM.
forwards to C The connection path is A to B’s home A pays for the session resource as
network and B’s home network to C though it were to B and B pays for the
session resource to C.
5 A sets up sessions with Connections to multiple parties are A pays for the set-up of each session
multiple parties (Multi-party) initiated by A A pays for each of the sessions resource
to each of the called parties
Each of the called parties pays for the
session resource to A
6 A has a multi-party session The multiple parties in the session Each party pays for the session set-up to
where the individual parties initiate the session to A A
set up the session to A A pays for the session resource to the
multiple parties
The individual parties in the session each
pay for the session resource to A
7 A is in a session with B, then A still has a connection to B while A pays for each of session set-ups to B
puts B on hold to set up a also in a session with C. The session and C
session with C, then returns with B continues after the session A pays for the session resource to B & C
to B after dropping C with C is terminated B & C pay for the session resource to A
8 A is in a session with B then A still has a connection to B while A pays for the session set-up to B
also in a session with C. The session C pays for the session set-up to A
answers a session request
from C while keeping B on with B continues after the session A pays for the session resource to B and
hold with C is terminated C
B & C pay for the session resource to A
A sets up a session with B The connection is made from A to B’s A pays for the session set-up to B
who is roaming in another home network and then forwarded to A pays for the session resource as
network B in the visited network. (Normal though it were to B in his home network
GSM mechanism) and B pays for the session resource from
Alternatively, A is redirected directly his home network to the visited network
to B in the visited network A pays for the session resource to B in
the visited network
B pays for the session resource to A

4.3.1.2 Charging Principles For User Session Components
A number of different components can comprise a session. These components may be added or dropped from an ongoing
session by any participating party. These components should be individually identifiable for charging purposes.
Generally, the party that adds a component should be responsible for the payment for the use of the component. However,
it should also be possible to charge all users that need an increase in resource to handle the component. An example is 2
users in an audio session where one of the users upgrades the session to videophone session. Both users could be charged
extra for the use of the video component as this requires extra resource at both ends.
Possible components are:
- Voice
ETSI
3GPP TS 22.115 version 14.3.0 Release 14 13 ETSI TS 122 115 V14.3.0 (2020-01)
- Audio (real time)
- Audio (streaming)
- Video (real-time)
- Video (streaming)
- Data (download/upload)
- Data interactive eg web browsing
- Messaging (SMS text type)
- E-mail
- Data stream (unspecified content) This is where the network operator acts as a "bit-pipe"
It shall be possible to charge for each of these components separately in a session with the options shown in the table
below.
It shall be possible for operators to be able to charge for individual components of sessions even if there is no identificable
service. For example a proprietary codec may be used to set up an "end-to-end" speech session where the network operator
acts as a "bit-pipe". In this case, it should be possible for the operator to charge for this differentially. This type of
component is called "datastream" in the table below.
It might not be possible to apply some of the charging mechanism and type options described below depending on the
capability of the networks used.

COMPONENT CHARGING MECHANISM OPTIONS CHARGING TYPE OPTIONS
Voice Charging principles as described in Charging by duration of session
section 4.3.1.1 Charging by QoS requested and/or
delivered
One-off set-up charge
Real time Audio and Video Charging principles as described in Charging by duration of session
section 4.3.1.1 Charging by QoS requested and/or
delivered
One-off set-up charge
Streaming Audio and Video Charged to the initiator of the request Charging by duration of session
Charged to the sender of the audio or Charging by volume of data, optionally
video QoS-differentiated
One-off set-up charge
Data (upload or download) Charged to the initiator of the request Charging by duration of session
Charged to the sender of the data Charging by volume of data, optionally
QoS-differentiated
One-off set-up charge
Interactive Data Charged to the initiator of the session Charging by duration of session
Charging by volume of data, optionally
QoS-differentiated
One-off set-up charge
Messaging (SMS text type) Charged to the initiator of the Charging by event (eg like SMS)
message Charging by volume of data
Charged to the recipient of the
message
Unspecified content (data stream) Charged to the initiator of the session Charging by duration of session
Charged to all parties involved Charging by volume of data (sent &
received), optionally QoS-
differentiated
One-off set-up charge
ETSI
3GPP TS 22.115 version 14.3.0 Release 14 14 ETSI TS 122 115 V14.3.0 (2020-01)
4.3.1.3 Other Charging Requirements
The user will also be charged for additional activities while in a session, for example downloaded applications or
information. The table below shows some of these requirements and the priority. [This section will need to be further
developed.]
CHARGING REQUIREMENT DESCRIPTION
Downloaded items User is charged for a specific item downloaded eg a
music file, video clip, application
Location based services User is charged for receiving information on his location
(charging based on accuracy as an option). This could be
a stand-alone location query or linked to another service
Content accessed or downloaded User is charged according to the value of the information.
Eg weather information, share price or other financial
information
rd
M-Commerce Electronic transactions to 3 party suppliers of goods &
services
Use of portal or other site User is charged for any access to a portal or any other
site. This could be a one-off charge or based on duration
or data volume of the portal or site use
APN and associated content User is charged for access to a specific APN and for the
content associated. Requirements are for further study.
Actual duration of rendered service User is charged (e.g. for premium rate services or hotline)
based on the actual duration of the rendered service

4.3.2 Roaming Charging Requirements
It shall be possible for a network operator to charge its users for activities while roaming. It shall be possible for a network
operator to charge its users while roaming using the same principles used while on the home network. The ability to
supply all the necessary information for all the charging options will depend on the capability of the visited network.
In addition, the network operators have to charge each other for the use of their networks by roaming users. The
methods of charging between operators may be different from the methods used to charge the user. For example, a user
may be charged by duration for voice sessions made while roaming but the home network may pay the visited network
by volume of data used. Based on preconfiguration or indication from the home network, the serving network may be
aware that charging information per individual subscription is not needed. In that case the serving network may omit
detailed collection of chargeable events per individual subscription and instead base roaming charging of the home
network on optimised collection of chargeable events.
Mechanisms used in today’s networks may also be applied e.g. Inter-Operator Tariff (IOT).
The table below shows the types of charging principle that networks will require for roaming settlement and a priority
for its provision.
ETSI
3GPP TS 22.115 version 14.3.0 Release 14 15 ETSI TS 122 115 V14.3.0 (2020-01)

ITEM CHARGING METHOD DESCRIPTION
Charging for session use Sessions made by users while roaming charged
according to the principles described in section 4.3.1.1,
above. This includes duration and volume charging
Downloaded items Items downloaded by the user while roaming from
providers associated with the visited network are charged
back to the home network for onward charge to the user
Location based services Location information provided by the visited network is
charged back to the home network for possible onward
charge to the user.
Content accessed or downloaded Information that is accessed by the user while roaming
from providers associated with the visited network is
charged according to its value by the visited network back
to the home network for onward charge to the user.
M-Commerce Charging requirements between visited and home
networks for M-Commerce transactions made by a
roaming user are for further study.
Use of portal or other site The visited network may charge the home network for
any access by the roaming user to a local portal or any
other local site. This could be a one-off charge and/or
based on duration or data volume of the portal or site use
APN & associated content Charge by visited network to home network for access to
a specific APN and for the content associated.
Requirements are for further study.

4.3.3 Interconnect Charging Requirements
This clause appli
...