6 Definition of charging information
32.2753GPPCharging managementMultiMedia Telephony (MMTel) chargingRelease 17Telecommunication managementTS
6.1 Data description for MMTel offline charging
6.1.1 Rf message contents
6.1.1.0 Introduction
For offline charging, the different service CTFs supporting MMtel specific service charging generate accounting information transferred to the CDF using the Diameter accounting application, as described in TS 32.299 [50].
The Charging Data Request and Charging Data Response are used for this MMTel service offline charging, as described in TS 32.260 [20].
This clause describes the different fields used in the Charging Data messages and the category in the tables are used according to the charging data configuration defined in clause 5.4 of TS 32.240 [1].
6.1.1.1 Charging Data Request message description
The generic Charging Data Request message described in TS 32.260 [20] used for MMTel offline charging is enhanced with specific MMTel service information.
Table 6.1.1.1.1 illustrates the overall Charging Data Request message as used for MMTel offline charging.
Table 6.1.1.1.1: Charging Data Request message contents
|
Information Element |
Category |
Description |
|---|---|---|
|
See Charging Data-Request message fields described in TS 32.260 [20] |
||
|
Service Information |
OM |
This field holds the MMTel specific parameter and is described in clause 6.3. |
NOTE: Detailed descriptions of the fields are provided in TS 32.299 [50].
6.1.1.2 Charging Data Response message description
The generic Charging Data Response message described in TS 32.260 [20] is used for MMTel offline charging.
6.1.2 GTP’ message contents
Not applicable. Refer to sclause 5.2.3 for further information.
6.1.3 CDR description on the Bi interface
6.1.3.1 CDR field type
The MMTel CDR content and format description is based on TS 32.260 [20] AS-CDR description, enhanced with specific MMTel service information.
The content of MMTel CDR type is defined in the table in clause 6.1.3.3. The field definition includes the field name, category and description. The category in the tables are used according to the charging data configuration defined in clause 5.4 of TS 32.240 [1]. The detailed field descriptions are provided in TS 32.298 [51].
The CDF provides the CDRs at the Bi interface in the format and encoding described in TS 32.298 [51]. Additional CDR formats and contents may be available at the interface to the billing system to meet the requirements of the billing system, these are outside of the scope of standardization.
6.1.3.2 CDR triggers
Accounting information for MMTel services charging is transferred from the CTFs supporting MMtel service charging to the CDF, using Charging Data Request start, interim stop or Event messages, depending on MMTel service behaviour (detailed in clause 5.2.2). Within the CDF, the CDRs triggering follows the same principle as described for SIP sessions in TS 32.260 [20]: MMTel CDR is opened upon reception of a Charging Data Request [start] message, closed upon reception of a Charging Data Request [stop] message, updated upon reception of a Charging Data Request [Interim], and created upon reception of a Charging Data Request [event].
6.1.3.3 MMTel-AS CDR content
The MMTel CDR content and format description is based on TS 32.260 [20] AS-CDR description, enhanced with specific MMTel information.
The detailed description of the field is provided in TS 32.298 [51].
Table 6.1.3.3.1 : Charging data of MMTel CDR
|
Field |
Category |
Description |
|---|---|---|
|
See Charging Data of AS CDR described in TS 32.260 [20]. |
||
|
MMTel information |
OC |
This field includes a list of MMTel supplementary services which may occur within the same AS. The MMTel supplementary services related informations are described in clause 6.3.1.2. |
6.2 Data description for MMTel online charging
6.2.1 Ro message contents
6.2.1.0 Introduction
For online charging, the different service CTFs supporting MMTel specific service charging, generate debit and reserve units information transferred to the OCF. For this purpose, MMTel online charging utilises the Debit Units and Reserve Units procedure specified in the Debit / Reserve Units operation in TS 32.299 [50].
The Debit / Reserve Units Request and Debit / Reserve Units Response messages are used for this MMTel service online charging, as described in TS 32.260 [20] and the category in the tables are used according to the charging data configuration defined in clause 5.4 of TS 32.240 [1].
6.2.1.1 Debit / Reserve Units Request message
The generic Debit / Reserve Units Request message described in TS 32.260 [20], used for MMTel online charging is enhanced with specific MMTel service information.
Table 6.2.1.1.1 illustrates the overall Debit / Reserve Units Request message as used for MMTel online charging.
Table 6.2.1.1.1: Debit / Reserve Units Request message contents
|
Information Element |
Category |
Description |
|---|---|---|
|
See Debit / Reserve Units Request message fields described in TS 32.260 [20]. |
||
|
Service Information |
OM |
This field holds the MMTel specific parameter and is described in clause 6.3. |
NOTE: Detailed descriptions of the fields are provided in TS 32.299 [50].
6.2.1.2 Debit / Reserve Units Response message
The generic Debit / Reserve Units Response message described in TS 32.260 [20] is used for MMTel online charging.
6.3 MMTel charging specific parameters
6.3.1 Definition of MMTel charging information
6.3.1.0 Introduction
The MMTel Information parameter used for MMTel charging is provided in the Service Information parameter.
6.3.1.1 MMTel charging information assignment for Service Information
The components in the Service Information that are use for MMTel charging can be found in table 6.3.1.1.1.
Table 6.3.1.1.1: Service Information used for MMTel charging
|
Information Element |
Category |
Description |
|
Service Information |
OM |
A set of fields hold the 3GPP specific parameter |
|
Subscription Id |
OM |
Used as defined in TS 32.260 [20]. |
|
IMS Information |
OC |
The details are defined in TS 32.260 [20]. |
|
PS Information |
OC |
The details are defined in TS 32.260 [20]. |
|
MMTel Information |
OM |
This field holds a set of MMTel services with theirs specific parameters. |
6.3.1.2 Definition of the MMTel Information
MMTel specific charging information is provided within the MMTel Information, and the detailed structure of the MMTel Information can be found in table 6.3.1.2.1
Table 6.3.1.2.1 : Structure of the MMTel Information
|
Information Element |
Category |
Description |
||
|---|---|---|---|---|
|
Supplementary Service |
OM |
This is a grouped field comprising several sub-fields associated with one supplementary service. It can be present multiple times as necessary to present the parallel activity of the different supplementary services. |
||
|
Service Type |
OM |
This field holds the type of the Supplementary Service, i.e. OIP, OIR, TIP, TIR, CW, HOLD, CB, MWI, CONF, CDIV, ECT, FA, MCID, CAT, CUG, PNM, CRS, AoC. |
||
|
Service Mode |
OC |
This field holds the mode of specific Service Type, i.e. for CB: ACR, ICB, OC, Bfor CDIV: CFU, CFB, CFNR, CFNRc, CFNL, CFUDB and for CONF: 3PTY, AoC-S, AoC-D, AoC-E. |
||
|
Number of diversions |
OC |
This field holds the number of diversions for CDIV. |
||
|
Associated party address |
OC |
This field holds additional party identification needed for the service charging, i.e. for CDIV the "forwarding party", for ECT the "transferor", for FA the "Pilot Identity", for 3PTY the "Initiator party". |
||
|
Service id |
OC |
This field holds the conference ID for CONF supplementary service |
||
|
Change Time |
OC |
This field holds the time of the requested action indicated in the "Participant Action Type" during the CONF supplementary service. It provides the time stamps for the CONF supplementary service parameters reporting. When the action is set to "CREATE", this field indicates the start time of the CONF supplementary service. When the action is set to "QUIT" and Number Of Participants holds the value "0", this field indicates the end time of the CONF supplementary service. |
||
|
Number Of Participants |
OC |
This field holds the number of parties who are currently attached to the Conference at the time stamped indicated in the "Change Time", for the CONF supplementary service. |
||
|
Participant Action Type |
OC |
This field holds the participant action type for CONF supplementary service (CREATE_CONF, JOIN_CONF, INVITE_CONF, QUIT_CONF) at the time stamped indicated in the "Change Time". |
||
|
CUG Information |
OC |
This field holds the CUG information conveyed by the Network and identifies the CUG-communication : it is the "CUG Interlock Code" . |
||
|
AoC information |
OC |
This field holds the AoC related Charging information conveyed to CDF, as defined in TS 32.280 [69 Since AoC information may be sent more than once (e.g for AoC-S), this field may be multiple. |
||
6.3.1.3 Support of MMTel Information in MMTel offline charging
In table 6.3.1.3.1, the supported Operation Types for Service Type field within the MMTel Information on the Rf interface are presented. The other MMTel Information fields are not detailed.
The supported Operation Types for Service Information fields, used in the Charging Data Request and Charging Data Response messages for MMTel charging, other than MMTel Information fields, are described in TS 32.260 [20].
Operation Types for Service Type, encompasses the various situations, where the basic MMTel service Charging Data Request messages are sent from:
– a separate entity (another AS or S-CSCF), than the AS implementing the supplementary service;
– the same AS.
Each service may be reported through a dedicated Charging Data Request Message or combined Charging Data Request Messages (regrouped supplementary services or with basic MMTel service).
Table 6.3.1.3.1: Supported values for Service Type in MMTel Information
|
Information Element |
|
|---|---|
|
Node Type |
AS |
|
Supported Operation Types |
S/I/S/E |
|
Service Type |
|
|
OIP (see note 1) |
SISE |
|
OIR |
SISE |
|
TIP |
SISE |
|
TIR (see note 2) |
SISE |
|
CW |
SISE |
|
HOLD (see note 3) |
SISE |
|
CB (see note 2) |
—E |
|
MWI |
—E |
|
CAT |
SISE |
|
CCBS |
SISE |
|
CCNR |
SISE |
|
CONF |
SISE |
|
CDIV |
SISE |
|
ECT |
SISE |
|
FA |
SISE |
|
MCID |
SISE |
|
CUG |
SISE |
|
PNM |
SISE |
|
CRS |
SISE |
|
AoC |
SISE |
|
NOTE 1: Only present at terminating side. NOTE 2: Terminating side service. NOTE 3: AS may be involved for announcement purposes. |
|
6.3.1.4 Support of MMTel Information in MMTel online charging
In table 6.3.1.4.1 the basic structure of the supported fields within the MMTel Information in the Debit and Reserve Units Request for IMS online charging on the Ro interface are presented. The Operation types are listed in the following order: I (initial)/U (update)/T (terminate)/E (event). Therefore, when all Operation types are possible it is marked as IUTE. If only some Operation types are allowed for a node, only the appropriate letters are used (i.e. IUT or E) as indicated in the table heading. The omission of an Operation type for a particular field is marked with "-" (i.e. IU-E). Also, when an entire filed is not allowed in a node the entire cell is marked as "-".
Table 6.3.1.4.1: Supported values in Debit / Reserve Units Request message MMTel Information
|
Information Element |
|
|
Node Type |
AS |
|
Supported Operation Types |
I/U/T/E |
|
Service Type |
|
|
OIP (see note) |
– |
|
OIR (see note) |
– |
|
TIP (see note) |
– |
|
TIR (see note) |
– |
|
CW (see note) |
– |
|
HOLD (see note) |
– |
|
CB (see note) |
– |
|
MWI (see note) |
– |
|
CAT (see note) |
– |
|
CCBS (see note) |
– |
|
CCNR (see note) |
– |
|
CONF |
IUTE |
|
CDIV |
IUT- |
|
ECT |
IUT- |
|
MCID (see note) |
– |
|
PNM (see note) |
– |
|
FA |
IUT- |
|
CUG |
IUT- |
|
CRS (see note) |
– |
|
AoC (see note) |
– |
|
NOTE: Only reported in offline charging. |
|
6.4 Data description for MMTel converged charging
6.4.1 Message contents
6.4.1.1 General
The Charging Data Request and Charging Data Response are specified in TS 32.290 [57] and include charging information. The Charging Data Request can be of type [Event, Initial, Update, Termination].
Table 6.4.1.1.1 describes the use of these messages for converged charging.
Table 6.4.1.1.1: Converged charging messages reference table
|
Message |
Source |
Destination |
|
Charging Data Request |
AS |
CHF |
|
Charging Data Response |
CHF |
AS |
6.4.1.2 Structure for the converged charging message formats
6.4.1.2.1 Charging Data Request message
Table 6.4.1.2.1.1 illustrates the basic structure of a Charging Data Request message as used for MMTel converged charging.
Table 6.4.1.2.1.1: Charging Data Request message contents
|
Information Element |
Category |
Description |
|---|---|---|
|
See Charging Data-Request message fields described in TS 32.260 [20] with MMTel specific triggers described in clause 5.4.1.2. |
||
|
MMTel charging information |
OC |
This field includes a list of MMTel supplementary services specific information described in clause 6.4.2.2 |
6.4.1.2.2 Charging Data Response message
Table 6.4.1.2.2.1 illustrates the basic structure of a Charging Data Response message as used for MMTel converged charging.
Table 6.4.1.2.2.1: Charging Data Response Message Contents
|
Information Element |
Category |
Description |
|---|---|---|
|
See Charging Data-Response message fields described in TS 32.260 [20] with MMTel specific triggers described in clause 5.4.1.2. |
||
6.4.2 Definition of the MMTel converged charging information
6.4.2.1 General
The Charging Information parameter used for MMTel converged charging is provided in the following clauses.
6.4.2.2 Definition of MMTel charging information
MMTel specific charging information used for MMTel converged charging is provided within the MMTel charging Information.
Table 6.4.2.2.1: Structure of MMTel Charging Information
|
Information Element |
Category |
Description |
|
Supplementary Service |
OM |
This is a grouped field comprising several sub-fields associated with one supplementary service. It can be present multiple times as necessary to present the parallel activity of the different supplementary services. |
|
Service Type |
OM |
This field holds the type of the supplementary service: OIP, OIR, TIP, TIR, CW, HOLD, CB, MWI, CONF, CDIV, ECT, FA, MCID, CAT, CUG, PNM, or CRS. |
|
Service Mode |
OC |
This field holds the mode of specific service type for – CB: ACR, ICB, OC, or B, – CDIV: CFU, CFB, CFNR, CFNRc, CFNL, or CFUDB and – CONF: 3PTY |
|
Number of diversions |
OC |
This field holds the number of diversions for CDIV. |
|
Associated party address |
OC |
This field holds additional party identification needed for the service charging for – CDIV the "forwarding party" – ECT the "transferor" – FA the "Pilot Identity" – 3PTY the "Initiator party". |
|
Conference Id |
OC |
This field holds the conference ID specific for CONV |
|
Participant Action Type |
OC |
This field holds the participant action type for CONF: CREATE_CONF, JOIN_CONF, INVITE_CONF, QUIT_CONF at the time stamped indicated in the "Change Time". |
|
Change Time |
OC |
This field holds the time of the requested action indicated in the "Participant Action Type" during the supplementary service CONF. For "Participant Action Type": – CREATE this field indicates the start time of the CONF – QUIT and Number Of Participants is 0, this field indicates the end time of the CONF |
|
Number Of Participants |
OC |
This field holds the number of parties who are currently attached to the Conference at the time stamped indicated in the "Change Time", for the CONF supplementary service. |
|
CUG Information |
OC |
This field holds the CUG information conveyed by the Network and identifies the CUG-communication: it is the "CUG Interlock Code". |
6.4.2.3 Detailed message format for converged charging
The following clause specifies per Operation Type the charging data that are sent by IMS node for IMS converged charging.
The Operation Types are listed in the following order: I (Initial)/U (Update)/T (Termination)/E (Event). Therefore, when all Operation Types are possible it is marked as IUTE. If only some Operation Types are allowed for a node, only the appropriate letters are used (i.e. IUT or E) as indicated in the table heading. The omission of an Operation Type for a particular field is marked with "-" (i.e. I-TE). Also, when an entire field is not allowed in a node the entire cell is marked as "-".
Table 6.4.2.3.1 defines the basic structure of the supported fields in the Charging Data Request message for MMTel converged charging.
Table 6.4.2.3.1: Supported fields in Charging Data Request message
|
Information Element |
Node Type |
IMS Node |
|---|---|---|
|
Supported Operation Types |
IUTE |
|
|
Session Identifier |
-UTE |
|
|
Subscriber Identifier |
IUTE |
|
|
NF Consumer Identification |
IUTE |
|
|
Invocation Timestamp |
IUTE |
|
|
Invocation Sequence Number |
IUTE |
|
|
Retransmission Indicator |
IUT- |
|
|
Notify URI |
IU– |
|
|
Supported Features |
IU-E |
|
|
Service Specification Information |
IUTE |
|
|
Triggers |
-UT- |
|
|
Multiple Unit Usage |
IUT- |
|
|
Rating Group |
IUT- |
|
|
Requested Unit |
IU– |
|
|
Used Unit Container |
-UT- |
|
|
Triggers |
-UT- |
|
|
IMS Charging Information |
IUTE |
|
|
MMTel Charging Information |
IUTE |
|
|
Supplementary Service |
IUTE |
|
|
Service Type |
IUTE |
|
|
Service Mode |
IUTE |
|
|
Number of diversions |
IUTE |
|
|
Associated party address |
IU-E |
|
|
Conference Id |
I–E |
|
|
Participant Action Type |
IUTE |
|
|
Change Time |
-UTE |
|
|
Number Of Participants |
IUTE |
|
|
CUG Information |
I–E |
|
Table 6.4.2.3.2 defines the basic structure of the supported fields in the Charging Data Response message for MMTel converged charging.
Table 6.4.2.3.2: Supported fields in Charging Data Response message
|
Information Element |
Node Type |
IMS Node |
|---|---|---|
|
Supported Operation Types |
IUTE |
|
|
Session Identifier |
IUTE |
|
|
Invocation Timestamp |
IUTE |
|
|
Invocation Result |
IUTE |
|
|
Invocation Sequence Number |
IUTE |
|
|
Session Failover |
I— |
|
|
Triggers |
– |
|
|
Multiple Unit information |
I–E |
|
|
Result Code |
IU-E |
|
|
Rating Group |
IU– |
|
|
Granted Unit |
IU– |
|
|
Validity Time |
IU– |
|
6.4.2.4 Formal MMTel converged charging parameter description
6.4.2.4.1 MMTel charging CHF CDR parameters
The detailed definitions, abstract syntax and encoding of the MMTel charging CHF CDR parameters are specified in TS 32.298 [51].
6.4.2.4.2 MMTel charging resources attributes
The detailed definitions of resources attributes used for MMTel charging are specified in TS 32.291 [58].
Annex A (informative):
Bibliography
This Annex is a placeholder for documents which are not explicitly cited in this specification.
Annex B (informative):
Change history
|
Change history |
||||||||
|
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Subject/Comment |
Cat |
Old |
New |
|
Sep 2008 |
— |
— |
— |
— |
Presentation to SA Plenary |
0.2.0 |
1.0.0 |
|
|
Mar 2009 |
SA-43 |
SP-090058 |
— |
— |
Presentation to SA for approval |
2.0.0 |
8.0.0 |
|
|
Jun 2009 |
SA-44 |
SP-090432 |
005 |
— |
Correction of offline charging message flow of Communications Diversion (CDIV) service |
F |
8.0.0 |
8.1.0 |
|
Jun 2009 |
SA-44 |
SP-090432 |
007 |
— |
Correction of offline charging message flow of Explicit Communication Transfer (ECT) service |
F |
8.0.0 |
8.1.0 |
|
Jun 2009 |
SA-44 |
SP-090432 |
012 |
— |
Clarification on MMTel charging architecture |
F |
8.0.0 |
8.1.0 |
|
Jun 2009 |
SA-44 |
SP-090294 |
1 |
– |
Add "Flexible Alerting" MMTel supplementary service Charging description |
|||
|
Jun 2009 |
SA-44 |
SP-090294 |
2 |
– |
Basic principles description for MMTel online charging |
B |
8.1.0 |
9.0.0 |
|
Jun 2009 |
SA-44 |
SP-090294 |
3 |
– |
R9 CR Add CCNR in MMTel Charging |
B |
8.1.0 |
9.0.0 |
|
Jun 2009 |
SA-44 |
SP-090294 |
4 |
– |
R9 CR Add CCNR in MMTel Charging |
B |
8.1.0 |
9.0.0 |
|
Jun 2009 |
SA-44 |
SP-090294 |
6 |
– |
Add MMTel CDIV online charging scenario |
B |
8.1.0 |
9.0.0 |
|
Jun 2009 |
SA-44 |
SP-090294 |
8 |
– |
Add CCBS and CCNR MMTel supplementary services in Scope chapter. Small cleanups |
B |
8.1.0 |
9.0.0 |
|
Jun 2009 |
SA-44 |
SP-090294 |
9 |
– |
Add "Malicious Communication Identification (MCID)" MMTel supplementary service Charging description |
B |
8.1.0 |
9.0.0 |
|
Jun 2009 |
SA-44 |
SP-090294 |
10 |
– |
Add "Customized Alerting Tone (CAT)" MMTel supplementary service Charging description |
B |
8.1.0 |
9.0.0 |
|
Jun 2009 |
SA-44 |
SP-090294 |
11 |
– |
Add "Closed User Group (CUG)" MMTel supplementary service Charging description |
B |
8.1.0 |
9.0.0 |
|
Jun 2009 |
SA-44 |
SP-090294 |
13 |
– |
Add "Flexible Alerting" MMTel supplementary service Online Charging scenario |
B |
8.1.0 |
9.0.0 |
|
Jun 2009 |
SA-44 |
SP-090294 |
14 |
– |
Add "Closed User Group (CUG)" MMTel supplementary service Online Charging scenario |
B |
8.1.0 |
9.0.0 |
|
Sep-2009 |
SA-45 |
SP-090538 |
16 |
– |
Aligning MMTel Charging error cases with TS 32.260 IMS Charging |
A |
9.0.0 |
9.1.0 |
|
Sep-2009 |
SA-45 |
SP-090538 |
17 |
– |
Refinement on CUG information in MMTel information |
F |
9.0.0 |
9.1.0 |
|
Sep-2009 |
SA-45 |
SP-090538 |
19 |
– |
Setting for Operation Types related to "service type"values in ACR for MMTel charging |
A |
9.0.0 |
9.1.0 |
|
Sep-2009 |
SA-45 |
SP-090538 |
20 |
– |
Add 3PTY MMTel supplementary service charging |
B |
9.0.0 |
9.1.0 |
|
Sep-2009 |
SA-45 |
SP-090538 |
21 |
– |
Clarification on generic behaviour for Supplementary services Online Charging description |
C |
9.0.0 |
9.1.0 |
|
Dec 2009 |
SA-46 |
SP-090722 |
22 |
– |
Add "Conference (CONF)" MMTel supplementary service Online Charging scenario |
B |
9.1.0 |
9.2.0 |
|
Dec 2009 |
SA-46 |
SP-090722 |
23 |
– |
MMTel Online charging scenarios simplification – IMS-GWF interaction removal |
C |
9.1.0 |
9.2.0 |
|
Dec 2009 |
SA-46 |
SP-090722 |
24 |
– |
Add "CONF (3PTY)" MMTel supplementary service Online Charging scenario |
B |
9.1.0 |
9.2.0 |
|
Dec 2009 |
SA-46 |
SP-090722 |
25 |
– |
Add Messages description for MMTel Online Charging |
B |
9.1.0 |
9.2.0 |
|
Mar 2010 |
SA-47 |
SP-100044 |
26 |
– |
Add "Explicit Communication Transfer (ECT)" MMTel supplementary service Online Charging scenario |
B |
9.2.0 |
9.3.0 |
|
Mar 2010 |
SA-47 |
SP-100040 |
28 |
– |
Correction on MMTel CDR description for Ealy SDP – Alignment with TS 32.260 |
A |
9.2.0 |
9.3.0 |
|
Mar 2010 |
SA-47 |
SP-100040 |
30 |
– |
Correction in MMTel Charging for session priority – Alignment with TS 32.260 |
A |
9.2.0 |
9.3.0 |
|
Mar 2010 |
SA-47 |
SP-100044 |
31 |
– |
Add "Personal Network management" MMTel supplementary service charging description. |
B |
9.2.0 |
9.3.0 |
|
Mar 2010 |
SA-47 |
SP-100044 |
32 |
– |
Add "Customized Ringing Signal (CRS)" MMTel supplementary service charging description |
B |
9.2.0 |
9.3.0 |
|
Mar 2010 |
SA-47 |
SP-100044 |
33 |
– |
Add "Reverse Charging" MMTel supplementary service Charging not supported |
B |
9.2.0 |
9.3.0 |
|
Mar 2010 |
SA-47 |
SP-100044 |
34 |
– |
Completion for Supported values setting for MMTel Information – Online Charging |
B |
9.2.0 |
9.3.0 |
|
Sep 2010 |
SA-49 |
SP-100496 |
036 |
— |
Correction to Message Sequence Chart for Offline Charging of CW Service |
A |
9.3.0 |
9.4.0 |
|
Sep 2010 |
SA-49 |
SP-100497 |
037 |
— |
Correction to Support of MMTel Information in MMTel Online Charging |
F |
9.3.0 |
9.4.0 |
|
Dec 2010 |
SA-50 |
SP-100758 |
038 |
2 |
Correction of Communication session Barring (CB) to support MMTel Information in MMTel Offline Charging |
F |
9.4.0 |
9.5.0 |
|
Dec 2010 |
SA-50 |
SP-100758 |
039 |
2 |
Correction of Communication Waiting (CW) Charging Flow |
F |
9.4.0 |
9.5.0 |
|
Mar 2011 |
SA-51 |
SP-110109 |
42 |
1 |
MMTel Charging enhancement for alignment with generic AS Charging description in TS 32.260 |
C |
9.5.0 |
10.0.0 |
|
Mar 2011 |
SA-51 |
SP-110112 |
40 |
1 |
Add ‘Advice Of Charge (AoC)’ MMTel supplementary service Charging description – Align with 22.173 |
B |
9.5.0 |
10.0.0 |
|
Mar 2011 |
SA-51 |
SP-110109 |
41 |
1 |
Correction on Subscriber role |
F |
9.5.0 |
10.0.0 |
|
2012-09 |
– |
– |
– |
– |
Update to Rel-11 version (MCC) |
– |
10.0.0 |
11.0.0 |
|
2012-12 |
SA-58 |
SP-120793 |
42 |
1 |
Single charging session applicability to MMTel |
B |
11.0.0 |
11.1.0 |
|
2013-03 |
SA-59 |
Changes from SA-59 implemented |
11.1.0 |
11.2.0 |
||||
|
2013-04 |
History table correction by MCC |
11.2.0 |
11.2.1 |
|||||
|
2013-09 |
SA-61 |
SP-130464 |
44 |
1 |
Correct use of PS information elements |
F |
11.2.1 |
11.3.0 |
|
SP-130437 |
47 |
– |
Correction on MMTel Online Charging |
A |
11.2.1 |
11.3.0 |
||
|
2014-06 |
SA-64 |
SP-140336 |
52 |
1 |
assured transfer charging discription |
B |
11.3.0 |
12.0.0 |
|
2014-07 |
– |
– |
– |
– |
Rapporteur/MCC: General editorial changes and clean-up. |
– |
12.0.0 |
12.0.1 |
|
2014-09 |
SA-65 |
SP-140564 |
57 |
1 |
Corrections for alignment between charging specifications |
F |
12.0.1 |
12.1.0 |
|
SP-140561 |
58 |
1 |
Removal of CDIVN service |
A |
||||
|
2014-12 |
SA-66 |
SP-140804 |
59 |
– |
Additional corrections for removal of I-WLAN solution |
F |
12.1.0 |
12.2.0 |
|
SP-140805 |
60 |
– |
Corrections on definition for parameter category |
F |
||||
|
2015-03 |
SA-67 |
SP-150065 |
63 |
1 |
Inconsistency correction of subscriber role |
A |
12.2.0 |
12.3.0 |
|
2015-12 |
SA-70 |
SP-150816 |
65 |
2 |
Introduction of Announcement service for MMTel service |
B |
12.3.0 |
13.0.0 |
|
2016-03 |
SA-71 |
SP-160039 |
66 |
1 |
Correction of interactions of Announcement service and MMTel supplementary services |
F |
13.0.0 |
13.1.0 |
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2017-03 |
SA#75 |
SP-170138 |
0067 |
1 |
C |
Remove reference to RFC 3588 |
14.0.0 |
|
2018-06 |
– |
– |
– |
– |
– |
Update to Rel-15 version (MCC) |
15.0.0 |
|
2019-09 |
SA#85 |
SP-190760 |
0068 |
2 |
B |
Addition of converged charging architecture |
16.0.0 |
|
2019-09 |
SA#85 |
SP-190760 |
0069 |
2 |
B |
Addition of converged charging scenarios |
16.0.0 |
|
2019-09 |
SA#85 |
SP-190760 |
0070 |
2 |
B |
Addition of applicable Triggers for converged charging |
16.0.0 |
|
2019-09 |
SA#85 |
SP-190760 |
0072 |
2 |
B |
Addition of converged charging CDR handling |
16.0.0 |
|
2019-12 |
SA#86 |
SP-191164 |
0073 |
1 |
B |
Addition of converged flows |
16.1.0 |
|
2020-12 |
SA#90e |
SP-201068 |
0075 |
1 |
B |
Add service based architecture for offline charging |
17.0.0 |
|
2020-12 |
SA#90e |
SP-201068 |
0076 |
1 |
B |
Adding converged charging in relevance table |
17.0.0 |
|
2020-12 |
SA#90e |
SP-201068 |
0077 |
1 |
B |
Adding converged charging for supplementary service |
17.0.0 |
|
2021-03 |
SA#91e |
SP-210164 |
0078 |
– |
B |
Introduction of CHF framework in the scope |
17.1.0 |
|
2021-03 |
SA#91e |
SP-210164 |
0079 |
1 |
B |
Introduce Post Event Charging (PEC) |
17.1.0 |
|
2021-06 |
SA#92e |
SP-210399 |
0080 |
1 |
B |
Adding CHF announcement handling |
17.2.0 |
|
2021-06 |
SA#92e |
SP-210399 |
0081 |
1 |
B |
Adding converged charging flows |
17.2.0 |
|
2021-06 |
SA#92e |
SP-210399 |
0082 |
1 |
B |
Adding converged charging data description |
17.2.0 |
|
2021-12 |
SA#94e |
SP-211482 |
0083 |
1 |
F |
Correction of references for converged charging |
17.3.0 |