6 Definition of charging information
32.2713GPPCharging managementLocation Services (LCS) chargingRelease 17Telecommunication managementTS
6.0 General
This clause provides Stage 3 specifications of the CDR type and content in line with the CDR type definitions provided in clause 5.2.3 and Diameter Credit-Control messages for LCS
6.1 Data description for LCS offline charging
6.1.0 Introduction
Dedicated types of CDRs can be generated for LCS by the GMLC. The content of each CDR type is defined in one of the tables that are part of this clause. For each CDR type the parameter definition includes the parameter name, description and category.
The GMLC’s CGF shall be able to provide the CDRs at the Billing System interface in the format and encoding described in the present document. In LCS, both fully qualified partial CDRs (FQPC) and reduced partial CDRs (RPC), as specified in TS 32.240 [1] may be supported on the Bl interface. In line with TS 32.240 [1], the support of FQPCs is mandatory, the support of RPCs is optional.
6.1.1 Rf message contents
Not applicable. Refer to clause 5.2.2 for further information.
6.1.2 Ga message contents
Not applicable. Refer to clause 5.2.3 for further information.
6.1.3 CDR description on the BL interface
6.1.3.0 Introduction
This clause provides stage 3 specifications of the CDR type and content for the 3GPP LCS domain. For each of the CDR types, a parameter table, which gives a short description of the parameters, is provided. 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 specification of the CDR parameters and their encoding is contained in TS 32.298 [51], while TS 32.297 [52] specify the details of the CDR file transfer to the BD.
6.1.3.1 LCS records for Mobile Originated Location Request (LCS‑GMO‑CDR)
If enabled, a LCS GMLC Mobile Originated Charging Data Record (LCS-GMO-CDR) shall be produced for each MO-LR performed via the GMLC.
The fields in the record are specified in table 6.1.3.1.1, which provides a brief description of each field.
Table 6.1.3.1.1: LCS GMLC Mobile Originated CDR (LCS-GMO-CDR)
|
Field |
Category |
Description |
|
Record Type |
M |
LCS GMLC Mobile Originated Record |
|
Recording Entity |
M |
The E.164 address of this GMLC |
|
LCS Client Type |
C |
The type of the LCS client that invoked the LR, if available. |
|
LCS Client Identity |
C |
Further identification of the LCS client, if available. |
|
Served IMSI |
M |
The IMSI of the subscriber that requests the location. |
|
Served MSISDN |
Om |
The primary MSISDN of the subscriber that requests the location. |
|
Serving Entity |
C |
The E.164 address of the serving MSC (in case of CS-MO-LR) or SGSN (in case of PS-MO-LR) |
|
Location Estimate |
Oc |
The location estimate for the subscriber if contained in geographic position and the LR was successful. |
|
Positioning Data |
C |
The positioning method used or attempted, if available. |
|
User Error |
C |
The Location Service type of error if any failure happened |
|
Provider Error |
Oc |
The protocol related type of error if any failure happened |
|
Record Time Stamp |
Om |
Time of generation of the CDR |
|
Local Record Sequence Number |
Om |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types. |
|
Record extensions |
Oc |
A set of network/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. |
6.1.3.2 LCS records for Mobile Terminated Location Request (MT-LR)
6.1.3.2.1 LCS records for Requesting GMLC (LCS-RGMT-CDR)
If enabled, a LCS Requesting GMLC Mobile Terminated Charging Data Record (LCS-RGMT-CDR) shall be produced for each MT-LR is performed via the R-GMLC.
The fields in the record are specified in table 6.1.3.2.1.1, which provides a brief description of each field.
Table 6.1.3.2.1.1: LCS Requesting GMLC Mobile Terminated CDR (LCS-RGMT-CDR)
|
Field |
Category |
Description |
|
Record Type |
M |
LCS Requesting GMLC Mobile Terminated Record |
|
Recording Entity |
M |
The E.164 address of this GMLC |
|
Home GMLC Identity |
C |
If available, the IP address of the HGMLC involved in the location request |
|
LCS Client Type |
C |
The type of the LCS client that invoked the LR, if available. |
|
LCS Client Identity |
C |
Further identification of the LCS client, if available. |
|
Target IMSI |
M |
The IMSI of the targeted LCS subscriber |
|
Target MSISDN |
Om |
The primary MSISDN of the targeted subscriber. |
|
Location Type |
M |
The type of location information being requested. |
|
LCS Priority |
C |
Priority of the LR, if available |
|
Result Code |
Om |
The result code that indicate the result of the request or individual positioning |
|
Record Time Stamp |
Om |
Time of generation of the CDR |
|
Local Record Sequence Number |
Om |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types. |
|
Record extensions |
Oc |
A set of network/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. |
6.1.3.2.2 LCS records for Home GMLC (LCS-HGMT-CDR)
If enabled, a LCS Home GMLC Mobile Terminated Charging Data Record (LCS-HGMT-CDR) shall be produced for each MT-LR is performed via the H-GMLC.
The fields in the record are specified in table 6.1.3.2.2.1, which provides a brief description of each field.
Table 6.1.3.2.2.1: LCS Home GMLC Mobile Terminated CDR (LCS-HGMT-CDR)
|
Field |
Category |
Description |
|
Record Type |
M |
LCS Home GMLC Mobile Terminated Record |
|
Recording Entity |
M |
The E.164 address of this GMLC |
|
Requesting GMLC Identity |
C |
If available, the IP address of the RGMLC involved in the location request |
|
Visited GMLC Identity |
C |
If available, the IP address of the VGMLC involved in the location request |
|
Serving Network Identity |
Oc |
MCC and MNC of the serving network used during this record, if available. |
|
LCS Client Type |
C |
The type of the LCS client that invoked the LR, if available. |
|
LCS Client Identity |
C |
Further identification of the LCS client, if available. |
|
Target IMSI |
M |
The IMSI of the targeted LCS subscriber |
|
Target MSISDN |
Om |
The primary MSISDN of the targeted subscriber. |
|
Location Type |
M |
The type of location information being requested. |
|
LCS Priority |
C |
Priority of the LR, if available |
|
Result Code |
Om |
The result code that indicate the result of the request or individual positioning |
|
Record Time Stamp |
Om |
Time of generation of the CDR |
|
Local Record Sequence Number |
Om |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types. |
|
Record extensions |
Oc |
A set of network/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. |
6.1.3.2.3 LCS records for Visited GMLC (LCS-VGMT-CDR)
If enabled, a LCS Visited GMLC Mobile Terminated Charging Data Record (LCS-VGMT-CDR) shall be produced for each MT-LR is performed via the V-GMLC.
The fields in the record are specified in table 6.1.3.2.3.1, which provides a brief description of each field.
Table 6.1.3.2.3.1: LCS Visited GMLC Mobile Terminated CDR (LCS-VGMT-CDR)
|
Field |
Category |
Description |
|
Record Type |
M |
LCS Visited GMLC Mobile Terminated Record |
|
Recording Entity |
M |
The E.164 address of this GMLC |
|
Home GMLC Identity |
C |
If available, the IP address of the HGMLC involved in the location request |
|
LCS Client Type |
C |
The type of the LCS client that invoked the LR, if available. |
|
LCS Client Identity |
C |
Further identification of the LCS client, if available. |
|
Target IMSI |
M |
The IMSI of the targeted LCS subscriber |
|
Target MSISDN |
Om |
The primary MSISDN of the targeted subscriber. |
|
Location Type |
M |
The type of location information being requested. |
|
LCS Priority |
C |
Priority of the LR, if available |
|
Result Code |
Om |
The result code that indicate the result of the request or individual positioning |
|
Record Time Stamp |
Om |
Time of generation of the CDR |
|
Local Record Sequence Number |
Om |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types. |
|
Record extensions |
Oc |
A set of network/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. |
6.1.3.3 LCS Records for Network Initiated Location Request (LCS‑GNI‑CDR)
If enabled, a LCS GMLC Network Induced Charging Data Record (LCS-GNI-CDR) shall be produced for each NI-LR performed via the GMLC.
The fields in the record are specified in table 6.1.3.3.1, which provides a brief description of each field.
Table 6.1.3.3.1: LCS GMLC Network Induced CDR (LCS-GNI-CDR)
|
Field |
Category |
Description |
|
Record Type |
M |
LCS GMLC Network Induced Record |
|
Recording Entity |
M |
The E.164 address of this GMLC |
|
LCS Client Type |
C |
The type of the LCS client that invoked the LR, if available. |
|
LCS Client Identity |
C |
Further identification of the LCS client, if available. |
|
Served IMSI |
M |
The IMSI of the subscriber that requests the location. |
|
Served MSISDN |
Om |
The primary MSISDN of the subscriber that requests the location. |
|
Serving Entity |
C |
The E.164 address of the serving MSC (in case of CS-NI-LR) or SGSN (in case of PS-NI-LR) |
|
Result Code |
Om |
The result code that indicate the result of the request or individual positioning |
|
Record Time Stamp |
Om |
Time of generation of the CDR |
|
Local Record Sequence Number |
Om |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types. |
|
Record extensions |
Oc |
A set of network/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. |
6.2 Data description for LCS online charging
6.2.1 Ro message contents
6.2.1.0 General
The Debit Units / Reserve Units operation for the "interim interrogation" and "final interrogation" reports the actual number of "units" that were used, from what was previously reserved. This determines the actual amount debited from the subscriber’s account.
Table 6.2.1.0.1 describes the use of these messages for online charging.
Table 6.2.1.0.1: Online charging messages reference table
|
Message |
Source |
Destination |
|
Debit / Reserve Units Request |
GMLC |
OCS |
|
Debit / Reserve Units Response |
OCS |
GMLC |
This clause describes the different Information Elements (IE) used in the Debit / Reserve Units messages and the charging data configuration defined in clause 5.4 of TS 32.240 [1].
6.2.1.1 Debit / Reserve Units Request message
Table 6.2.1.1.1 illustrates the basic structure of a Debit / Reserve Units Request message from GMLC as used for LCS online charging.
Table 6.2.1.1.1: Debit / Reserve Units Request message contents for LCS
|
Information Element |
Category |
Description |
|---|---|---|
|
Session Identifier |
M |
Described in TS 32.299 [50] |
|
Originator Host |
M |
Described in TS 32.299 [50] |
|
Originator Domain |
M |
Described in TS 32.299 [50] |
|
Destination Domain |
M |
Described in TS 32.299 [50] |
|
Operation Identifier |
M |
Described in TS 32.299 [50] |
|
Operation Token |
M |
Described in TS 32.299 [50] |
|
Operation Type |
M |
Described in TS 32.299 [50] |
|
Operation Number |
M |
Described in TS 32.299 [50] |
|
Destination Host |
Oc |
Described in TS 32.299 [50] |
|
User Name |
Oc |
Described in TS 32.299 [50] |
|
Origination State |
Oc |
Described in TS 32.299 [50] |
|
Origination Timestamp |
Oc |
Described in TS 32.299 [50] |
|
Subscriber Identifier |
OM |
Described in TS 32.299 [50] |
|
Termination Cause |
Oc |
Described in TS 32.299 [50] |
|
Requested Action |
Oc |
Described in TS 32.299 [50] |
|
Multiple Operation |
OM |
Described in TS 32.299 [50] |
|
Multiple Unit Operation |
OC |
Described in TS 32.299 [50] |
|
Subscriber Equipment Number |
Oc |
Described in TS 32.299 [50] |
|
Service Information |
Oc |
Holds the LCS service specific parameters. It is further described in the table below |
NOTE: A full description and the detailed use of the Information Elements for GMLC and for each CCR request type (initial/update/termination/event) is specified in TS 32.299 [50].
6.2.1.2 Debit / Reserve Units Response message
Table 6.2.1.2.1 illustrates the basic structure of a Debit / Reserve Units Response message as used for LCS charging. This message is always used by the OCS as specified below, independent of the receiving GMLC and the Debit / Reserve Units Request type that is being replied to.
Table 6.2.1.2.1: Debit / Reserve Units Response message contents for LCS
|
AVP |
Category |
Description |
|---|---|---|
|
Session Identifier |
M |
Described in TS 32.299 [50] |
|
Operation Result |
M |
Described in TS 32.299 [50] |
|
Originator Host |
M |
Described in TS 32.299 [50] |
|
Originator Domain |
M |
Described in TS 32.299 [50] |
|
Operation Identifier |
M |
Described in TS 32.299 [50] |
|
Operation Type |
M |
Described in TS 32.299 [50] |
|
Operation Number |
M |
Described in TS 32.299 [50] |
|
User-Name |
Oc |
Described in TS 32.299 [50] |
|
Origin-State-Id |
Oc |
Described in TS 32.299 [50] |
|
Event-Timestamp |
Oc |
Described in TS 32.299 [50] |
|
Operation Failover |
Oc |
Described in TS 32.299 [50] |
|
Multiple Unit Operation |
Oc |
Described in TS 32.299 [50] |
|
Operation Failure Action |
Oc |
Described in TS 32.299 [50] |
|
Operation Event Failure Action |
Oc |
Described in TS 32.299 [50] |
|
Redirection Host |
Oc |
Described in TS 32.299 [50] |
|
Redirection Host Usage |
Oc |
Described in TS 32.299 [50] |
|
Redirection Cache Time |
Oc |
Described in TS 32.299 [50] |
|
Service Information |
OC |
This field holds additional 3GPP service specific parameter. It is further described in the table below |
6.3 LCS charging specific parameters
6.3.1 Definition of LCS charging information
6.3.1.0 General
The LCS Information parameter used for LCS charging is provided in the Service Information parameter.
6.3.1.1 LCS charging information assignment for Service Information
The components in the Service Information that are use for LCS charging can be found in Table 6.3.1.1.
Table 6.3.1.1.1: Service Information used for LCS Charging
|
Information Element |
Category |
Description |
|
Service Information |
OM |
A set of fields hold the 3GPP specific parameter |
|
Subscriber Identifier |
OM |
Used as defined in TS 32.260 [20]. |
|
LCS Information |
OM |
This field holds a set of MMTel services with theirs specific parameters. |
6.3.1.2 Definition of the LCS Information
LCS specific charging information is provided within the LCS Information, and the detailed structure of the LCS Information can be found in table 6.3.1.2.1.
Table 6.3.1.2.1: Structure of the LCS Information
|
Information Element |
Category |
Description |
|
LCS Client ID |
OC |
This field holds the ID of the LCS client that invoked the LR, if available. |
|
Location Type |
OC |
This field holds the type of location information being requested in case of MT-LR. |
|
Location Estimate |
OC |
This field denotes the location of an MS in universal coordinates and |
|
Positioning Data |
Oc |
This field indicates the positioning method that was attempted |
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 2003 |
SA_21 |
SP-030411 |
— |
— |
Submitted to TSG SA#21 for Information |
— |
1.0.0 |
1.1.0 |
|
Dec 2004 |
SA_26 |
SP-040781 |
— |
— |
Submitted to TSG SA#26 for Approval |
— |
2.0.0 |
6.0.0 |
|
Jun 2005 |
SA_28 |
SP-050278 |
0001 |
— |
Add peer GMLC Identification and network ID to LCS CDRs |
C |
6.0.0 |
6.1.0 |
|
Jun 2005 |
SA_28 |
SP-050278 |
0002 |
— |
Correction to scope |
F |
6.0.0 |
6.1.0 |
|
Jun 2005 |
SA_28 |
SP-050278 |
0003 |
— |
Correction to references |
F |
6.0.0 |
6.1.0 |
|
Sep 2005 |
SA_29 |
SP-050622 |
0004 |
— |
Correct GMLC address used in LCS CDRs |
F |
6.1.0 |
6.2.0 |
|
Jun 2007 |
SA_36 |
— |
— |
— |
Automatic upgrade to Rel-7 (no CR) at freeze of Rel-7. |
— |
6.2.0 |
7.0.0 |
|
Dec 2008 |
SA_42 |
SP-080841 |
0005 |
— |
Correction on Multiple Service indication and parameter |
F |
7.0.0 |
7.1.0 |
|
Dec 2008 |
SA_42 |
— |
— |
— |
Upgrade to Release 8 |
— |
7.1.0 |
8.0.0 |
|
Dec 2009 |
– |
– |
– |
– |
Update to Rel-9 version (MCC) |
8.0.0 |
9.0.0 |
|
|
Dec 2010 |
SA_50 |
SP-100759 |
0006 |
2 |
Change the Title of Clause 6.1.1 to "Rf message contents" |
F |
9.0.0 |
10.0.0 |
|
Jun 2012 |
SA_56 |
SP-120361 |
0012 |
3 |
Correction of Location Information field in LCS Charging |
F |
10.0.0 |
10.1.0 |
|
2012-09 |
– |
– |
– |
– |
Update to Rel-11 version (MCC) |
– |
10.1.0 |
11.0.0 |
|
2013-03 |
SA_59 |
SP-130054 |
0013 |
1 |
Correction of invalid reference to LCS offline charging architecture |
F |
11.0.0 |
11.1.0 |
|
2013-03 |
Editorial changes on CDR tables (MCC) |
11.1.0 |
11.1.1 |
|||||
|
2014-07 |
– |
– |
– |
– |
Rapporteur/MCC: General editorial changes and clean-up. |
11.1.1 |
11.1.2 |
|
|
2014-09 |
SA_65 |
SP-140564 |
0014 |
1 |
Corrections for alignment between charging specifications |
F |
11.1.2 |
12.0.0 |
|
2014-12 |
SA_66 |
SP-140804 |
0015 |
– |
Additional corrections for removal of I-WLAN solution |
F |
12.0.0 |
12.1.0 |
|
SP-140805 |
0016 |
– |
Corrections on definition for parameter category |
F |
||||
|
2016-01 |
Upgrade to Rel-13 (MCC) |
12.1.0 |
13.0.0 |
|||||
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2017-03 |
SA#75 |
SP-170138 |
0018 |
1 |
C |
Remove reference to RFC 3588 |
14.0.0 |
|
2018-06 |
– |
– |
– |
– |
– |
Update to Rel-15 version (MCC) |
15.0.0 |
|
2020-07 |
– |
– |
– |
– |
– |
Update to Rel-16 version (MCC) |
16.0.0 |
|
2022-03 |
– |
– |
– |
– |
– |
Update to Rel-17 version (MCC) |
17.0.0 |