6 Definition of charging information
32.2513GPPCharging managementPacket Switched (PS) domain chargingRelease 17Telecommunication managementTS
6.1A Rf message content
6.1A.0 General
This clause is applicable to the ePDG, TWAG, MME, S-GW, P-GW and TDF, when the CDF is provided as an external entity.
6.1A.1 Summary of offline charging message formats
The PS Offline Charging and ""SMS over MME Charging" utilises the Charging Data Transfer that is specified in the 3GPP accounting application described in TS 32.299 [50].
The Charging Data Transfer operation employs the Charging Data Request and Charging Data Response messages.
The Charging Data Request can be of type [Start, Interim, Stop and Event] and includes all charging information. The Charging Data Response is an acknowledgement of the Charging Data Request.
Table 6.1A.1.1 describes the use of these messages for offline charging.
Table 6.1A.1.1: Offline charging messages reference table
Message |
Source |
Destination |
Charging Data Request |
ePDG, TWAG, MME, S-GW,P-GW,TDF |
CDF |
Charging Data Response |
CDF |
ePDG, TWAG, MME, S-GW, P-GW, TDF |
6.1A.2 Structure for the charging data message formats
6.1A.2.0 General
This clause describes the Information Elements (IE) used in the charging data messages.
Category in table 6.1A.2.1.1 and table 6.1A.2.2.1 shall use the categories according to the charging data configuration defined in clause 5.4 of TS 32.240 [1].
6.1A.2.1 Charging Data Request message
Table 6.1A.2.1.1 illustrates the basic structure of a Charging Data Request message from the MME, S-GW, ePDG, TWAG, P-GW and TDF as used for PS offline charging and ""SMS over MME Charging".
Table 6.1A.2.1.1: Charging Data Request message contents
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 Type |
M |
Described in TS 32.299 [50] |
Operation Number |
M |
Described in TS 32.299 [50] |
Operation Identifier |
OC |
Described in TS 32.299 [50] |
User Name |
OC |
The content of the field corresponds to the Protocol Configuration Options (PCO) field of the Create IP-CAN bearer Request message. (ffs) |
Destination Host |
OC |
Described in TS 32.299 [50] |
Operation Interval |
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] |
Proxy Information |
OC |
Described in TS 32.299 [50] |
Route Information |
OC |
Described in TS 32.299 [50] |
Operation Token |
OM |
This field identifies the PS domain. |
Service Information |
OM |
This field holds the PS charging specific parameters described in clause 6.3. |
NOTE: Detailed descriptions of the fields are provided in TS 32.299 [50].
6.1A.2.2 Charging Data Response message
Table 6.1A.2.2.1 illustrates the basic structure of a Charging Data Response message as used for the ePDG, TWAG, MME, S-GW, P-GW and TDF.
Table 6.1A.2.2.1 : Charging Data Response message contents
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 Type |
M |
Described in TS 32.299 [50] |
Operation Number |
OC |
Described in TS 32.299 [50] |
Operation Identifier |
OC |
Described in TS 32.299 [50] |
Operation Interval |
OC |
Described in TS 32.299 [50] |
Error Reporting Host |
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] |
Proxy Information |
OC |
Described in TS 32.299 [50] |
NOTE: Detailed descriptions of the fields are provided in TS 32.299 [50].
6.1B CDR content description on Bp interface
6.1B.0 General
This clause describes the CDR parameters used in the CDRs.
The tables in the subsequent parts of this clause specify the designations for the category of a CDR parameter ("field categories") according to the charging data configuration defined in clause 5.4 of TS 32.240 [1].
The following tables 6.1.1.1 – 6.1.14.1 provide a brief description of each CDR parameter. Full definitions of the CDR parameters, sorted by the name in alphabetical order, are provided in TS 32.298 [51].
6.1.1 IP-CAN bearer charging data in SGSN (S-CDR)
If the collection of CDR data is enabled then the SGSN data specified in table 6.1.1.1 shall be available for each IP-CAN bearer.
Table 6.1.1.1: SGSN IP-CAN bearer data (S-CDR)
Field |
Category |
Description |
---|---|---|
Record Type |
M |
SGSN IP-CAN bearer record. |
Network Initiated PDP Context |
OC |
A flag that is present if this is a network initiated IP-CAN bearer. |
Served IMSI |
C |
IMSI of the served party, if available. |
IMSI Unauthenticated Flag |
OC |
This field indicates the provided served IMSI is not authenticated (emergency bearer service situation). |
Served IMEI |
OC |
The IMEI or IMEISV of the ME, if available. It is used for identifying the user in case Served IMSI is not present during emergency bearer service. |
SGSN Address |
OM |
The IP address of the current SGSN. |
MS Network Capability |
OM |
The mobile station Network Capability. |
Routing Area Code (RAC) |
OM |
RAC at the time of "Record Opening Time". |
Location Area Code (LAC) |
OM |
LAC at the time of "Record Opening Time". |
User CSG information |
OC |
This field contains the User CSG information of the UE, if available, including CSG ID, access mode and CSG membership indication. |
Cell Identifier |
OM |
Cell identity for GSM or Service Area Code (SAC) for UMTS at the time of "Record Opening Time". |
Charging ID |
M |
IP-CAN bearer identifier used to identify this IP-CAN bearer in different records created by PCNs. |
GGSN Address Used |
M |
The control plane IP address of the P-GW currently used. The P-GW address is always the same for an activated IP-CAN bearer. |
Access Point Name Network Identifier |
OM |
The logical name of the connected access point to the external packet data network (network identifier part of APN). |
PDP Type |
OM |
PDP type, i.e. IPv4, IPv6, IPv4v6, PPP. |
Served PDP Address |
OC |
PDP address of the served IMSI, i.e. IPv4 address when PDP Type is IPv4 or IPv6 prefix when PDP Type is IPv6 or IPv4v6. This parameter shall be present except when both the PDP type is PPP and dynamic PDP address assignment is used. |
Served PDP Address prefix length |
OC |
PDP/PDN Address prefix length of an IPv6 typed Served PDP Address. The field needs not available for prefix length of 64 bits. |
Served PDP/PDN Address extension |
OC |
This field holds IPv4 address of the served IMSI, if available, when PDP type is IPv4v6. |
List of Traffic Data Volumes |
OM |
A list of changes in charging conditions for this IP-CAN bearer, each change is time stamped. Charging conditions are used to categorize traffic volumes, such as per tariff period. Initial and subsequently changed QoS and corresponding data volumes are also listed. |
Record Opening Time |
M |
Time stamp when IP-CAN bearer is activated in this SGSN or record opening time on subsequent partial records. |
Duration |
M |
Duration of this record in the SGSN. |
SGSN Change |
C |
Present if this is first record after SGSN change. |
Cause for Record Closing |
M |
The reason for closure of the record from this SGSN. |
Diagnostics |
OM |
A more detailed reason for the release of the connection. |
Record Sequence Number |
C |
Partial record sequence number in this SGSN. Only present in case of partial records. |
Node ID |
OM |
Name of the recording entity. |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types. |
APN Selection Mode |
OM |
An index indicating how the APN was selected. |
Access Point Name Operator Identifier |
OM |
The Operator Identifier part of the APN. |
Served MSISDN |
OC |
The primary MSISDN of the subscriber, if available. |
Charging Characteristics |
M |
The Charging Characteristics applied to the IP-CAN bearer. |
Serving Node PLMN Identifier |
Oc |
This field holds the PLMN Identifier (MCC and MNC) serving the UE during this record. Only one value is included in case multiple PLMN Ids are supported by the SGSN. |
CN Operator Selection Entity |
OC |
This field indicates whether the Serving Network identified by the "Serving Node PLMN Identifier” has been selected by the UE or by the network, as defined in TS 29.060 [203] for GPRS, and in TS 29.274 [210] for EPC, if available. |
RAT Type |
OC |
This field indicates the Radio Access Technology (RAT) type currently used by the Mobile Station as defined in TS 29.061 [205], when available. |
CAMEL Information |
OC |
Set of CAMEL information related to IP-CAN bearer. For more information see Description of Record Fields. This field is present if CAMEL service is activated. |
RNC Unsent Downlink Volume |
OC |
The downlink data volume, which the RNC has not sent to MS. This field is present when the RNC has provided unsent downlink volume count at RAB release. |
Charging Characteristics Selection Mode |
OM |
Holds information about how Charging Characteristics were selected. |
Dynamic Address Flag |
OC |
Indicates whether served PDP address is dynamic, which is allocated during IP-CAN bearer activation. This field is missing if address is static. |
Low Priority Indicator |
OC |
This field indicates if this IP-CAN bearer has a low priority, i.e. for Machine Type Communication. |
Record Extensions |
OC |
A set of network operator/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. |
6.1.2 IP-CAN bearer charging data in S-GW (SGW-CDR)
If the collection of CDR data is enabled then the S-GW data specified in table 6.1.2.1 shall be available for each IP-CAN bearer.
Table 6.1.2.1: S-GW IP-CAN bearer data (SGW-CDR)
Field |
Category |
Description |
---|---|---|
Record Type |
M |
S-GW IP-CAN bearer record. |
Retransmission |
OC |
This parameter, when present, indicates that information from retransmitted Charging Data Request has been used in this CDR. |
Served IMSI |
C |
IMSI of the served party, if available. |
IMSI Unauthenticated Flag |
OC |
This field indicates the provided served IMSI is not authenticated (emergency bearer service situation). |
Served IMEI |
OC |
The IMEI or IMEISV of the ME, if available. It is used for identifying the user in case Served IMSI is not present during emergency bearer service. |
S-GW Address used |
M |
The control plane IP address of the S-GW used. |
S-GW Address IPv6 |
OC |
The control plane IPv6 address, in case of IPv4v6 dual stack, of the S-GW. |
Charging ID |
M |
IP-CAN bearer Charging identifier used to identify this IP-CAN bearer in different records created by PCNs |
PDN Connection Charging Id |
OM |
This field holds the explicit Charging Id for the PDN connection if received from the P-GW. Otherwise, the field holds the Charging Id of the EPS default bearer in GTP case, or the unique Charging Id of the IP-CAN session in PMIP case. This field is used to identify different records belonging to same PDN connection. |
Serving Node Address |
M |
List of serving node control plane IP addresses (e.g. S4-SGSN, MME, …) used during this record. |
Serving Node IPv6 Address |
OC |
List of serving node control plane IPv6 addresses, in case of IPv4v6 dual stack, (e.g. S4-SGSN, MME, …) used during this record. |
Serving node Type |
M |
List of serving node types in control plane. The serving node types listed here map to the serving node addresses listed in the field "Serving node Address" in sequence. |
S-GW Change |
OC |
Present if this is first record after a change from another serving node (i.e. SGW, ePDG, HSGW). |
PGW PLMN Identifier |
Oc |
PLMN identifier (MCC MNC) of the P-GW used. |
Access Point Name Network Identifier |
OM |
The logical name of the connected access point to the external packet data network (network identifier part of APN). |
PDP/PDN Type |
OM |
This field indicates PDN type (i.e. IPv4, IPv6 or IPv4v6). |
PDP/PDN Type extension |
OM |
This field indicates Non-IP PDN type. |
Served PDP/PDN Address |
OC |
IP address allocated for the PDP context / PDN connection, if available, i.e. IPv4 address when PDN Type is IPv4 or IPv6 prefix when PDN Type is IPv6 or IPv4v6. For non-IP PDN connection, this field is not present |
Served PDP/PDN Address prefix length |
OC |
PDP/PDN Address prefix length of an IPv6 typed Served PDP Address. The field needs not available for prefix length of 64 bits. For non-IP PDN connection, this field is not present. |
Served PDP/PDN Address extension |
OC |
This field holds IPv4 address of the served IMSI, if available, when PDN type is IPv4v6. For non-IP PDN connection, this field is not present. |
Dynamic Address Flag |
OC |
Indicates whether served PDP/PDN address is dynamic, which is allocated during IP-CAN bearer activation, initial attach (E-UTRAN or over S2x) and UE requested PDN connectivity. This field is missing if IPv4 address is static when PDN Type is IPv4, or if IPv6 address is static when PDN Type is IPv6 or IPv4v6. |
Dynamic Address Flag extension |
OC |
Indicates whether served IPv4 PDP/PDN address is dynamic, which is allocated during IP-CAN bearer activation, initial attach (E-UTRAN or over S2x) and UE requested PDN connectivity with PDP/PDN type IPv4v6. This field is missing if IPv4 address is static. |
List of Traffic Data Volumes |
OM |
A list of changes in charging conditions for this QCI/ARP pair, each change is time stamped. Charging conditions are used to categorize traffic volumes, such as per tariff period. Initial and subsequently changed QoS and corresponding data values are also listed. |
Record Opening Time |
M |
Time stamp when IP-CAN bearer is activated in this S-GW or record opening time on subsequent partial records. |
MS Time Zone |
OC |
This field contains the MS Time Zone the MS is currently located as defined in TS 29.060 [203], if available. |
Last MS Time Zone |
OC |
This field contains the UE Time Zone the UE is located at IP-CAN bearer deactivation, or at default bearer deactivation when IP-CAN session charging is active, when available. |
Duration |
M |
Duration of this record in the S-GW. |
Cause for Record Closing |
M |
The reason for the release of record from this S-GW. |
Diagnostics |
OM |
A more detailed reason for the release of the IP-CAN bearer, when a single cause is applicable. |
Enhanced Diagnostics |
OC |
This field holds a more detailed reason for the release of the IP-CAN bearer, when a set of causes is applicable. |
Record Sequence Number |
C |
Partial record sequence number, only present in case of partial records. |
Node ID |
OM |
Name of the recording entity. |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types. |
APN Selection Mode |
OM |
An index indicating how the APN was selected. |
Served MSISDN |
OC |
The primary MSISDN of the subscriber, if available. |
User Location Information |
OC |
This field contains the User Location Information of the MS as defined in TS 29.060 [203] for GPRS case, and in TS 29.274 [210] for EPC case, if available. |
User Location Information Time |
OC |
This field contains the time at which the user location information was acquired. |
PSCell Information |
OC |
This field holds the PSCell information: Primary SCG (Secondary Cell Group) Cell information |
Last User Location Information |
OC |
This field contains the User Location Information of the UE at IP-CAN bearer deactivation, or at default bearer deactivation when IP-CAN session charging is active, when available. |
User CSG information |
OC |
This field contains the User CSG information of the UE, if available, including CSG ID, access mode and CSG membership indication. |
Presence Reporting Area Information |
OC |
This grouped field contains the Presence Reporting Area Identifierfor the UE PDN connection and the initial status of the UE presence in the Presence Reporting Area, if available. This field is not applicable to multiple PRA(s) |
Charging Characteristics |
M |
The Charging Characteristics applied to the IP-CAN bearer. |
Charging Characteristics Selection Mode |
OM |
Holds information about how Charging Characteristics were selected. |
IMS Signalling Context |
OC |
Included if the IM-CN Subsystem Signalling Flag is set, see TS 23.060 [201] IP-CAN bearer is used for IMS signalling. |
P-GW Address used. |
OC |
This field is the P-GW IP Address for the Control Plane |
P-GW Address IPv6 |
OC |
This field is the P-GW IPv6 Address, in case of IPv4v6 dual stack, for the Control Plane |
Serving Node PLMN Identifier |
OC |
This field holds the PLMN Identifier (MCC and MNC) serving the UE during this record, as received in the "Serving Network” IE over S4/S11, if available. |
CN Operator Selection Entity |
OC |
This field indicates whether the Serving Network identified by the "Serving Node PLMN Identifier” has been selected by the UE or by the network, as defined in TS 29.060 [203] for GPRS, and in TS 29.274 [210] for EPC, if available. |
RAT Type |
OC |
This field indicates the Radio Access Technology (RAT) type currently used by the Mobile Station as defined in TS 29.061 [205], when available. |
Start Time |
OC |
This field holds the time when User IP-CAN session starts, available in the CDR for the first bearer in an IP-CAN session. |
Stop Time |
OC |
This field holds the time when User IP-CAN session is terminated, available in the CDR for the last bearer in an IP-CAN session. |
Low Priority Indicator |
OC |
This field indicates if this IP-CAN session has a low priority, i.e. for Machine Type Communication. |
CP CIoT EPS Optimisation indicator |
OC |
This field indicates whether CP CIoT EPS Optimisation is used during data transfer with the UE (i.e. Control Plane NAS PDU via S11-U between SGW and MME) or not (i.e.User Plane via S1-U between SGW and eNB), if enabled. |
UNI PDU CP Only Flag |
OC |
This field indicates whether this PDN connection is applied with "Control Plane Only Flag" for UNI PDU transfer, i.e. transfer only using Control Plane NAS PDU (Control Plane CIoT EPS optimisation). |
Serving PLMN Rate Control |
Oc |
This field holds the Serving PLMN Rate Control used by the MME during this record. |
MO exception data counter |
Oc |
This field holds the MO exception data counter value with the timestamp indicating the time at which the counter value increased from 0 to 1, as defined in TS 29.274 [210]. |
Record Extensions |
OC |
A set of network operator/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. |
List of RAN Secondary RAT Usage Reports |
OC |
A list of containers with volumes reported from RAN for secondary RAT usage, each container is time stamped. |
6.1.3 FBC IP-CAN bearer charging data in P-GW (PGW-CDR)
If FBC is enabled and the collection of CDR data is enabled then the P-GW data specified in table 6.1.3.1 shall be available for each IP-CAN bearer when charging per IP-CAN session is not active, or for each IP-CAN session when charging per IP-CAN session is active.
Table 6.1.3.1: P-GW IP-CAN bearer data (PGW-CDR)
Field |
Category |
Description |
---|---|---|
Record Type |
M |
P-GW IP-CAN bearer record. |
Retransmission |
OC |
This parameter, when present, indicates that information from retransmitted Charging Data Request has been used in this CDR. |
Served IMSI |
C |
IMSI of the served party, if available. |
IMSI Unauthenticated Flag |
OC |
This field indicates the provided served IMSI is not authenticated (emergency bearer service situation). |
Served IMEI |
OC |
The IMEI or IMEISV of the ME, if available. It is used for identifying the user in case Served IMSI is not present during emergency bearer service. |
Served 3GPP2 MEID |
OC |
MEID of the served party’s terminal equipment for 3GPP2 access. |
Served MN NAI |
OC |
Mobile Node Identifier in NAI format (based on IMSI), if available. |
P-GW Address used |
M |
The control plane IP address of the P-GW used. |
P-GW Address IPv6 |
OC |
The control plane IPv6 address, in case of IPv4v6 dual stack, of the P-GW used. |
Charging ID |
M |
IP-CAN bearer Charging identifier used to identify this IP-CAN bearer in different records created by PCNs. This field holds the unique Charging Id in the PMIP case. When charging per IP-CAN session is active, this field holds the Charging Id of the EPS default bearer. It is the same as the PDN Connection Charging Id. |
Charging per IP-CAN Session Indicator |
Oc |
This field indicates whether charging per IP-CAN session is active. If this field is not present, charging per IP-CAN session is not active. |
PDN Connection Charging Id |
OM |
This field holds the explicit Charging Id for the PDN connection. When NBIFOM is supported, the PGW will assign an explicit PDN Connection Charging ID for the PDN connection. Otherwise the field holds the Charging Id of the EPS default bearer. This field is used to identify different records belonging to same PDN connection. |
Serving node Address |
M |
List of SGSN/S-GW/TWAG control plane IP addresses, or the ePDG address used during this record. |
Serving node IPv6 Address |
OC |
List of SGSN/S-GW/TWAG control plane IPv6 addresses, in case of IPv4v6 dual stack, used during this record. |
Serving node Type |
M |
List of serving node types in control plane (SGSN, SGW, ePDG, AGW, TWAG). The serving node types listed here map to the serving node addresses listed in the field "Serving node Address" in sequence. |
PGW PLMN Identifier |
Oc |
PLMN identifier (MCC MNC) of the P-GW. |
Access Point Name Network Identifier |
OM |
The logical name of the connected access point to the external packet data network (network identifier part of APN). |
PDP/PDN Type |
OM |
PDP/PDN type, i.e. IPv4, IPv6, IPv4v6 , or PDP type PPP. |
PDP/PDN Type extension |
OM |
This field indicates Non-IP PDN type. |
SGi PtP Tunnelling Method |
OC |
This field indicates whether SGi PtP tunnelling method based on UDP/IP or other methods are used for this PDN connection when non-IP PDN connection. |
SCS/AS Address |
OC |
This field holds the Address of SCS/AS for SGi PtP tunnelling. |
Served PDP/PDN Address |
OC |
IP address allocated for the PDP context / PDN connection, i.e. IPv4 address when PDP/PDN Type is IPv4 or IPv6 prefix when PDP/PDN Type is IPv6 or IPv4v6, or assigned IP address if any when PDP/PDN Type extension is Non-IP. This parameter shall be present except: – when both the PDP type is PPP and dynamic IP-CAN bearer address assignment is used or – when PDP/PDN Type extension is Non-IP, and no IP address has been assigned by the PGW for the PDN connection. |
Served PDP/PDN Address prefix length |
OC |
PDP/PDN Address prefix length of an IPv6 typed Served PDP Address. The field needs not available for prefix length of 64 bits. |
Served PDP/PDN Address extension |
OC |
This field holds IPv4 address of the served IMSI, if available, when PDP/PDN type is IPv4v6. |
Dynamic Address Flag |
OC |
Indicates whether served PDP/PDN address is dynamic, which is allocated during IP-CAN bearer activation, initial attach (E-UTRAN or over S2x) and UE requested PDN connectivity. This field is missing if IPv4 address is static when PDN Type is IPv4, or if IPv6 address is static when PDN Type is IPv6 or IPv4v6. |
Dynamic Address Flag extension |
OC |
Indicates whether served IPv4 PDP/PDN address is dynamic, which is allocated during IP-CAN bearer activation, initial attach (E-UTRAN or over S2x) and UE requested PDN connectivity with PDP/PDN type IPv4v6. This field is missing if IPv4 address is static. |
List of Traffic Data Volumes |
OC |
A list of changes in charging conditions for all bearers within the IP-CAN session. Each change is time stamped. Charging conditions are used to categorize traffic volumes, such as per tariff period. Initial and subsequently changed QoS and corresponding data values are also listed. Applicable only for IP-CAN bearer charging when IP-CAN session charging is active. See table 6.1.3.1 for a description of List of Traffic Data Volumes handling. |
List of Service Data |
OM |
A list of changes in charging conditions for all service data flows within this IP-CAN bearer categorized per rating group or per combination of the rating group and service id or per combination of rating group, sponsor identity and application service provider identity. Each change is time stamped. Charging conditions are used to categorize traffic volumes, elapsed time and number of events, such as per tariff period. Initial and subsequently changed QoS and corresponding data values are also listed. Online charging information (PS Furnish Charging Information) may be added per each service data flow container in case it is sent by the OCS. External charging identifiers may be added per each service data flow container in case sent by the PCRF. Failure-Handling: This field shall be present in case P-GW triggers the Failure-Handling procedure. It shall indicate the Failure Handling scenario and the instant the Failure Action is triggered (see annex B). Scenarios: Continue/New Session; Continue/Ongoing Session; Retry&Terminate/Ongoing Session; Terminate/Ongoing Session. When charging per IP-CAN session is active, see table 6.1.3.2 for a description of List of Service Data handling. |
Record Opening Time |
M |
Time stamp when IP-CAN bearer is activated in this P-GW or record opening time on subsequent partial records. |
MS Time Zone |
OC |
This field contains the MS Time Zone the MS is currently located as defined in TS 29.060 [203], if available. |
Last MS Time Zone |
OC |
This field contains the UE Time Zone the UE is located at IP-CAN bearer deactivation, or at default bearer deactivation when IP-CAN session charging is active, when available. |
Duration |
M |
Duration of this record in the P-GW. |
Cause for Record Closing |
M |
The reason for the release of record from this P-GW. |
Diagnostics |
OM |
A more detailed reason for the release of the IP-CAN bearer, when a single cause is applicable |
Enhanced Diagnostics |
OC |
This field holds a more detailed reason for the release of the IP-CAN bearer, when a set of causes is applicable. |
Record Sequence Number |
C |
Partial record sequence number, only present in case of partial records. |
Node ID |
OM |
Name of the recording entity. |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types. |
APN Selection Mode |
OM |
An index indicating how the APN was selected. |
Served MSISDN |
OC |
The primary MSISDN of the subscriber, if available. |
User Location Information |
OC |
This field contains the User Location Information of the MS when the CDR is opened as defined in TS 29.060 [203] for GPRS case, and in TS 29.274 [210] for EPC case, if available. |
Last User Location Information |
OC |
This field contains the User Location Information of the UE at IP-CAN bearer deactivation, or at default bearer deactivation when IP-CAN session charging is active, when available. |
User Location Information Time |
OC |
This field contains the time at which the user location information was acquired, if available. |
User CSG information |
OC |
This field contains the User CSG Information of the UE, if available, including CSG ID, access mode and CSG membership indication. |
3GPP2 User Location information |
OC |
This field contains the User Location Information of the MS when the CDR is opened as defined in TS 29.212 [71] for 3GPP2 access, if available. |
TWAN User Location Information |
OC |
This field contains the UE location in a Trusted WLAN Access Network (TWAN) , if available: – "TWAN identifier" as defined in TS 29.274 [210] for S2a GTP-based case, or, -"Access Network Identifier Option IE" as defined in 29.275 [211] for S2a PMIP-based case. |
UWAN User Location Information |
OC |
This field contains the UE location in an Untrusted Wireless Access Network (UWAN) which includes the UE local IP address and optionally UDP source port number (if NAT is detected) as defined in TS 29.274 [210]. It may also include WLAN location information (SSID and, when available, BSSID of the access point) the ePDG may have received from the 3GPP AAA server about the UE as defined in TS 29.274 [210]. |
Presence Reporting Area Information |
OC |
This grouped field contains the Presence Reporting Area Identifier for the UE PDN connection, additional the list(s) of elements comprising the Presence Reporting Area for a UE-dedicated Presence Reporting Area, and the initial status of the UE presence in the Presence Reporting Area, if available. This field is not applicable to multiple PRA(s). |
Charging Characteristics |
M |
The Charging Characteristics applied to the IP-CAN bearer. |
Charging Characteristics Selection Mode |
OM |
Holds information about how Charging Characteristics were selected. |
IMS Signalling Context |
OC |
Included if the IP-CAN default bearer IM-CN Subsystem Signalling Flag is set, see TS 23.060 [201] is used for IMS signalling. |
Serving node PLMN Identifier |
OM |
This fields holds the PLMN Identifier (MCC and MNC) serving the UE during this record, as received in the "Serving Network” IE over S5/S8 or retrieved from the RAI received over Gn/Gp. When the Serving node is TWAG, this field includes the PLMN identifier used for UE authentication, i.e. the VPLMN in roaming case, and the HPLMN in non-roaming case. |
CN Operator Selection Entity |
OC |
This field indicates whether the Serving Network identified by the "Serving Node PLMN Identifier” has been selected by the UE or by the network, as defined in TS 29.060 [203] for GPRS, and in TS 29.274 [210] for EPC, if available. |
PS Furnish Charging Information |
OC |
Online charging session specific information |
CAMEL Information |
OC |
Set of CAMEL information related to IP-CAN bearer, if available. This field applies only for GPRS. When charging per IP-CAN session is active, this field is not applicable. |
RAT Type |
OC |
This field indicates the Radio Access Technology (RAT) type currently used by the Mobile Station as defined in TS 29.061 [205], when available. When NBIFOM is accepted by PCRF, this field holds the first default bearer’s RAT type when charging per IP-CAN session is active. |
Start Time |
OC |
This field holds the time when User IP-CAN session starts, available in the CDR for the first bearer in an IP-CAN session. When charging per IP-CAN session is active, this field holds the time when User IP-CAN session starts. |
Stop Time |
OC |
This field holds the time when User IP-CAN session is terminated, available in the CDR for the last bearer in an IP-CAN session. When charging per IP-CAN session is active, this field holds the time when User IP-CAN session is terminated. |
Low Priority Indicator |
OC |
This field indicates if this IP-CAN session has a low priority, i.e. for Machine Type Communication. |
QoS Information |
OC |
This field indicates the APN-AMBR uplink and downlink information for the IP-CAN session. Applicable only when charging per IP-CAN session is active. |
NBIFOM Support |
OC |
This field indicates that NBIFOM was requested by the UE, supported and accepted by the network for the IP-CAN session or if NBIFOM is not supported for the IP-CAN session. |
NBIFOM Mode |
OC |
This field indicates the NBIFOM mode selected for the PDN connection, when NBIFOM is supported for the IP-CAN session. This field is only present when NBIFOM is accepted. |
UNI PDU CP Only Flag |
OC |
This field indicates whether this PDN connection is applied with "Control Plane Only Flag" for UNI PDU transfer, i.e. transfer only using Control Plane NAS PDU (Control Plane CIoT EPS optimisation). |
Serving PLMN Rate Control |
Oc |
This field holds the Serving PLMN Rate Control used by the MME during this record |
APN Rate Control |
Oc |
This field holds the APN Rate Controls enforced in the PGW during this record. |
MO exception data counter |
Oc |
This field holds the MO exception data counter value with the timestamp indicating the time at which the counter value increased from 0 to 1, as defined in TS 29.274 [210]. |
Record Extensions |
OC |
A set of network operator/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. |
3GPP PS Data Off Status |
Oc |
This field holds the 3GPP PS Data Off Status. |
List of RAN Secondary RAT Usage Reports |
OC |
A list of containers with volumes reported from RAN for secondary RAT usage, each container is time stamped. |
VoLTE Information |
OC |
This field holds the caller and callee Information of VoLTE. |
Table 6.1.3.2 contains special handling for the fields in the List of Traffic Data Volumes in PGW-CDR when charging per IP-CAN session is active and IP-CAN bearer charging is performed.
Table 6.1.3.2: List of Traffic Data Volumes in PGW-CDR when charging per IP-CAN session is active
Field |
Category |
Description |
---|---|---|
Data Volume Uplink |
OC |
This field includes the number of octets transmitted during the use of the packet data services in the uplink direction. |
Data Volume Downlink |
OC |
This field includes the number of octets transmitted during the use of the packet data services in the downlink direction. |
Change Condition |
M |
This field defines the reason for closing the container as specified in clause 5.2.1.10.1. |
Change Time |
M |
This field is a time stamp, which defines the moment when the volume container is closed. |
User Location Information |
OC |
This field contains the location (e.g. CGI/SAI, ECGI/TAI or RAI) where the UE is located and used during the transfer of the data volume captured by the container. This is included in the Traffic data container only if previous container’s change condition is "user location change". |
UWAN User Location Information |
OC |
This field contains the UE location in an Untrusted Wireless Access Network (UWAN) which includes the UE local IP address and optionally UDP or TCP source port number (if NAT is detected) as defined in TS 29.274 [210]. It may also include WLAN location information the ePDG may have received from the 3GPP AAA server about the UE as "WLAN location information" defined in TS 29.274 [210]. |
TWAN User Location Information |
OC |
This field contains the UE location in a Trusted WLAN Access Network (TWAN), if available: – as "TWAN identifier" defined in TS 29.274 [210] for S2a GTP-based case, or, – as "Access Network Identifier Option IE" defined in 29.275 [211] for S2a PMIP-based case. |
Presence Reporting Area Status |
OC |
This field contains the status of the UE presence in Presence Reporting Area. This field is not applicable to multiple PRA(s). |
List of Presence Reporting Area Information |
OC |
This field contains a list of Presence Reporting Area Identifier(s) for the UE PDN connection, and the Presence Reporting Area(s) status (UE presence or not, inactive), differentiated between PCRF and OCS subscription. |
EPC QoS Information |
OC |
This field contains the authorized QoS for the IP-CAN bearer. First container for each QCI/ARP pair includes this field. In following containers this field is present if previous change condition is "QoS change". This field includes: QCI and ARP. For GBR QCI values, this field also includes GBR for the downlink and uplink direction. If the MBR is different than the GBR, then this field also includes the MBR for the downlink and uplink direction. This field does not include the APN-AMBR, which is contained in a separate field in the CDR for the IP-CAN session. |
Charging Id |
OC |
IP-CAN bearer Charging identifier used to identify this IP-CAN bearer in different records created by PCNs. Charging Id is generated by P-GW at IP-CAN bearer activation and is included in all containers in order to identify the containers which pertain to the IP-CAN bearer. |
RAT Type |
OC |
This field contains the RAT type for the current IP-CAN bearer. |
Access Availability Change Reason |
OC |
This field indicates the reason why the availability of an access is changed by the PCEF, i.e. RAN rule indication or Access usable/unusable. This field is only present when one access of a multi-access PDN connection becomes unusable. |
Related Change Condition Information |
OC |
This field indicates the change condition associated with an alternate access of a multi-access PDN connection that indirectly caused closure of the container. This field includes optional supplemental information associated with the change event (e.g., user location information). |
Diagnostics |
OM |
A more detailed reason for the release of the IP-CAN bearer, when a single cause is applicable. |
Enhanced Diagnostics |
OC |
This field holds a more detailed reason for the release of the IP-CAN bearer, when a set of causes is applicable. |
3GPP PS Data Off Status |
OC |
This field contains the status of the UE’s 3GPP PS Data off Status. |
Serving PLMN Rate Control |
OC |
This field holds the Serving PLMN Rate Control used by the MME |
APN Rate Control |
OC |
This field holds the APN Rate Controls enforced in the PGW |
Table 6.1.3.3 contains special handling for fields in the List of Service Data when charging per IP-CAN session is active. The complete set of fields in the List of Service Data is defined in TS 32.298 [51].
Table 6.1.3.3: List of Service Data in PGW-CDR when charging per IP-CAN session is active
Field |
Category |
Description |
---|---|---|
AF Record Information |
OC |
As specified in TS 32.298 [51]. |
Charging Rule Base Name |
OC |
As specified in TS 32.298 [51]. |
ADC Rule Base Name |
OC |
Not applicable to PGW-CDR. |
Data Volume Downlink |
OC |
As specified in TS 32.298 [51]. |
Data Volume Uplink |
OC |
As specified in TS 32.298 [51]. |
Event Based Charging Information |
OC |
As specified in TS 32.298 [51]. |
Local Sequence Number |
OC |
As specified in TS 32.298 [51]. |
PS Furnish Charging Information |
OC |
As specified in TS 32.298 [51]. |
EPC QoS Information |
OC |
This field contains the authorized QoS for the IP-CAN bearer that is first reported for the Rating Group or Rating Group / Service Identifier in the container. If traffic from multiple bearers is included in the report for the container, only one field is included. This field includes: QCI and ARP. For non-GBR QCI values, this field also includes the MBR for the downlink and uplink direction. For GBR QCI values, this field also includes GBR for the downlink and uplink direction. If the MBR is different than the GBR, then this field also includes the MBR for the downlink and uplink direction. This field does not include the APN-AMBR, which is contained in a separate field in the CDR for the IP-CAN session. |
Rating Group |
M |
As specified in TS 32.298 [51]. |
Report Time |
M |
As specified in TS 32.298 [51]. |
Result Code |
OC |
As specified in TS 32.298 [51]. |
Service Condition Change |
M |
As specified in TS 32.298 [51]. Only those values specified for the events in clause 5.3.2.X apply. |
Service Identifier |
OC |
As specified in TS 32.298 [51]. |
Service Specific Info |
OC |
As specified in TS 32.298 [51]. |
Serving Node Address |
OC |
As specified in TS 32.298 [51]. |
Time of First Usage |
OC |
As specified in TS 32.298 [51]. |
Time of Last Usage |
OC |
As specified in TS 32.298 [51]. |
Tme Usage |
OC |
As specified in TS 32.298 [51]. |
User Location Information |
OC |
As specified in TS 32.298 [51]. |
3GPP2 User Location Information |
OC |
As specified in TS 32.298 [51]. |
UWAN User Location Information |
OC |
This field contains the UE location in an Untrusted Wireless Access Network (UWAN) which includes the UE local IP address and optionally UDP or TCP source port number (if NAT is detected) as defined in TS 29.274 [210]. It may also include WLAN location information the ePDG may have received from the 3GPP AAA server about the UE as "WLAN location information" defined in TS 29.274 [210]. |
Presence Reporting Area Status |
OC |
This field contains the status of the UE presence in Presence Reporting Area as defined in TS 29.274[210]. This field is not applicable to multiple PRA(s). |
List of Presence Reporting Area Information |
OC |
This field contains a list of Presence Reporting Area Identifier(s) for the UE PDN connection, and the Presence Reporting Area(s) status (UE presence or not, inactive), differentiated between PCRF and OCS subscription. |
RAT Type |
OC |
This field contains the RAT type for the IP-CAN bearer that is first reported for the Rating Group or Rating Group / Service Identifier in the container. If traffic from multiple bearers is included in the report for the container, only one field is included. |
Sponsor Identity |
OC |
As specified in TS 32.298 [51]. |
Application Service Provider Identity |
OC |
As specified in TS 32.298 [51]. |
Time Quota Mechanism |
OC |
As specified in TS 32.298 [51]. |
Related Change Condition Information |
OC |
This field indicates the change condition associated with an alternate access of a multi-access PDN connection that indirectly caused closure of the container. This field includes optional supplemental information associated with the change event (e.g., user location information). |
3GPP PS Data Off Status |
OC |
This field contains the status of the UE’s 3GPP PS Data Off Status. |
Traffic Steering Policy Identifier Uplink |
OC |
This field contains the traffic steering policy identifier in the uplink direction. |
Traffic Steering Policy Identifier Downlink |
OC |
This field contains the traffic steering policy identifier in the downlink direction. |
Serving PLMN Rate Control |
OC |
This field holds the Serving PLMN Rate Control used by the MME |
APN Rate Control |
OC |
This field holds the APN Rate Controls enforced in the PGW |
6.1.4 Mobile Station mobility management data in SGSN (M-CDR)
If the collection of MS mobility management data is enabled then the SGSN shall start collecting the information specified in the following table 6.1.4.1 each time the mobile is attached to the SGSN.
Table 6.1.4.1: SGSN Mobile Station mobility management data (M-CDR)
Field |
Category |
Description |
---|---|---|
Record Type |
M |
SGSN mobility management record. |
Served IMSI |
M |
IMSI of the MS. |
Served IMEI |
OC |
The IMEI or IMEISV of the ME, if available. |
SGSN Address |
OM |
The IP address of the current SGSN. |
MS Network Capability |
OM |
The mobile station network capability. |
Routing Area Code |
OM |
Routing Area at the time of the Record Opening Time. |
Local Area Code |
OM |
Location Area Code at the time of Record Opening Time. |
Cell Identifier |
OM |
The Cell Identity for GSM or Service Area Code (SAC) for UMTS at the time of the Record Opening Time. |
Cell PLMN Id |
OM |
The MCC and MNC of the Cell at the time of Record Opening Time. |
Change of Location |
OC |
A list of changes in Routing Area Code including MCC and MNC, each with a time stamp. This field is not required if partial records are generated when the location changes. |
Record Opening Time |
M |
Timestamp when MS is attached to this SGSN or record opening time on following partial record. |
Duration |
OM |
Duration of this record. |
SGSN Change |
C |
Present if this is first record after SGSN change. |
Cause for Record Closing |
M |
The reason for the closure of the record in this SGSN. |
Diagnostics |
OM |
A more detailed reason for the release of the connection. |
Record Sequence Number |
C |
Partial record sequence number in this SGSN; only present in case of partial records. |
Node ID |
OM |
Name of the recording entity. |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types. |
Served MSISDN |
Oc |
The primary MSISDN of the subscriber, if available. |
Charging Characteristics |
M |
The Charging Characteristics used by the SGSN. |
Serving Node PLMN Identifier |
Oc |
This field holds the PLMN Identifier (MCC and MNC) serving the UE during this record. Only one value is included in case multiple PLMN Ids are supported by the SGSN. |
CN Operator Selection Entity |
OC |
This field indicates whether the Serving Network identified by the "Serving Node PLMN Identifier” has been selected by the UE or by the network, as defined in TS 29.060 [203] for GPRS, and in TS 29.274 [210] for EPC, if available. |
CAMEL Information |
OC |
Set of CAMEL information related to Attach/Detach session. For more information see Description of Record Fields. This field is present if CAMEL service is activated. |
RAT Type |
OC |
This field indicates the Radio Access Technology (RAT) type currently used by the Mobile Station as defined in TS 29.061 [205], when available. |
Charging Characteristics Selection Mode |
OM |
Holds information about how Charging Characteristics were selected. |
Record Extensions |
OC |
A set of network operator/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. |
6.1.5 SMS-MO data in SGSN/MME (S-SMO-CDR)
If enabled, an S-SMO-CDR SGSN/MME Mobile originated SMS record shall be produced for each short message sent by a mobile subscriber via the SGSN/via the MME to the SMSC.
The fields in the record are specified in table 6.1.5.1.
Table 6.1.5.1: SGSN/MME Mobile originated SMS record (S-SMO-CDR)
Field |
Category |
Description |
|
---|---|---|---|
SGSN |
MME |
||
Record Type |
M |
M |
SGSN/MME Mobile Originated SMS. |
Retransmission |
– |
OC |
This parameter, when present, indicates that information from retransmitted Charging Data Requesthas been used in this CDR. |
Served IMSI |
M |
M |
The IMSI of the subscriber. |
Served IMEI |
OC |
OC |
The IMEI or IMEISV of the ME, if available. |
Served MSISDN |
OC |
OC |
The primary MSISDN of the subscriber, if available. For MSISDN-less subscription, this field holds the Dummy MSISDN as defined in TS 23.003 [103]. |
MS Network Capability |
OM |
– |
The mobile station network capability. |
Service Centre |
OM |
OM |
The address (E.164) of the SMS-service centre. |
Serving Node Type |
M |
M |
Type of node handling the SMS (SGSN or MME). |
Recording Entity |
OM |
OM |
The E.164 number of the SGSN/MME. |
Serving Node Address |
– |
OM |
The address of the MME used. |
Serving Node IPv6 Address Address |
– |
OC |
The IPv6 address, in case of IPv4v6 dual stack, of the MME. |
MME Name |
– |
OM |
The operation Identity of the MME. |
MME Realm |
– |
OM |
The operation Realm Identity of the MME. |
Location Area Code |
OM |
– |
The Location Area Code from which the message originated. |
Routing Area Code |
OM |
– |
The Routing Area Code from which the message originated. |
Cell Identifier |
OM |
– |
The Cell Identity for GSM or Service Area Code (SAC) for UMTS from which the message originated. |
User Location Information |
– |
OC |
This field contains the User Location (User location Information as defined in TS 29.274 [210]) from which the message originated. |
User Location Information Time |
– |
OC |
This field contains the time at which the user location information was acquired. |
Message Reference |
M |
M |
A reference provided by the MS uniquely identifying this message. |
Event Time Stamp |
M |
M |
The time at which the message was received by the SGSN/MME from the subscriber. |
SMS Result |
C |
C |
The result of the attempted delivery if unsuccessful. |
Node ID |
OM |
OM |
Name of the recording entity. |
Local Record Sequence Number |
OM |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types. |
Charging Characteristics |
M |
M |
The Charging Characteristics flag set used by the SGSN/MME. |
Serving Node PLMN Identifier |
Oc |
Oc |
This field holds the PLMN Identifier (MCC and MNC) serving the UE during this record. Only one value is included in case multiple PLMN Ids are supported by the SGSN/MME. |
CN Operator Selection Entity |
OC |
OC |
This field indicates whether the Serving Network identified by the "Serving Node PLMN Identifier” has been selected by the UE or by the network, as defined in TS 29.060 [203] for GPRS, and in TS 29.274 [210] for EPC, if available. |
RAT Type |
OC |
OC |
This field indicates the Radio Access Technology (RAT) type currently used by the Mobile Station as defined in TS 29.061 [205], when available. |
Destination Number |
OM |
OM |
The destination short message subscriber number. |
CAMEL Information |
OC |
– |
Set of CAMEL information related to SMS session. For more information see Description of Record Fields. This field is present if CAMEL service is activated. |
Charging Characteristics Selection Mode |
OM |
OM |
Holds information about how Charging Characteristics were selected. |
Record Extensions |
OC |
OC |
A set of network operator/ manufacturer specific extensions to the record. Conditioned upon the existence of an extension. |
6.1.6 SMS-MT data in SGSN/MME (S-SMT-CDR)
If enabled, an SGSN/MME Mobile terminated SMS record shall be produced for each short message received by a mobile subscriber via the SGSN/ from the SMSC via the MME. The fields in the record are specified in table 6.1.6.1.
Table 6.1.6.1: SGSN/MME Mobile terminated SMS record (S-SMT-CDR)
Field |
Category |
Description |
|
---|---|---|---|
SGSN |
MME |
||
Record Type |
M |
M |
SGSN/MME Mobile Terminated SMS. |
Retransmission |
– |
OC |
This parameter, when present, indicates that information from retransmitted Charging Data Request has been used in this CDR. |
Served IMSI |
M |
M |
The IMSI of the subscriber. |
Served IMEI |
OC |
OC |
The IMEI or IMEISV of the ME, if available. |
Served MSISDN |
OC |
OC |
The primary MSISDN of the subscriber. |
MS Network Capability |
OM |
– |
The mobile station network capability. |
Service Centre |
OM |
OM |
The address (E.164) of the SMS-service centre. |
Serving Node Type |
M |
M |
Type of node handling the SMS (SGSN or MME) |
Recording Entity |
OM |
OM |
The E.164 number of the SGSN/MME. |
Serving Node Address |
– |
OM |
The address of the MME used |
Serving Node IPv6 Address Address |
– |
OC |
The IPv6 address, in case of IPv4v6 dual stack, of the MME. |
MME Name |
– |
OM |
The Diameter Identity of the MME |
MME Realm |
– |
OM |
The Diameter Realm Identity of the MME |
Location Area Code |
OM |
– |
The Location Area Code to which the message was delivered. |
Routing Area Code |
OM |
– |
The Routing Area Code to which the message was delivered. |
Cell Identifier |
OM |
– |
The Cell Identity for GSM or Service Area Code (SAC) for UMTS to which the message was delivered. |
User Location Information |
– |
OC |
This field contains the User Location (User location Information as defined in TS 29.274 [210]) to which the message was delivered, if available. |
User Location Information Time |
– |
OC |
This field contains the time at which the user location information was acquired. |
Event Time Stamp |
M |
M |
Delivery time stamp, time at which message was sent to the MS by the SGSN/MME. |
SMS Result |
C |
C |
The result of the attempted delivery if unsuccessful. |
Node ID |
OM |
OM |
Name of the recording entity. |
Local Record Sequence Number |
OM |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types. |
Charging Characteristics |
M |
M |
The Charging Characteristics flag set used by the SGSN/MME. |
Serving Node PLMN Identifier |
Oc |
Oc |
This field holds the PLMN Identifier (MCC and MNC) serving the UE during this record. Only one value is included in case multiple PLMN Ids are supported by the SGSN/MME |
CN Operator Selection Entity |
OC |
OC |
This field indicates whether the Serving Network identified by the "Serving Node PLMN Identifier” has been selected by the UE or by the network, as defined in TS 29.060 [203] for GPRS, and in TS 29.274 [210] for EPC, if available. |
RAT Type |
OC |
OC |
This field indicates the Radio Access Technology (RAT) type currently used by the Mobile Station as defined in TS 29.061 [205], when available. |
Charging Characteristics Selection Mode |
OM |
OM |
Holds information about how Charging Characteristics were selected. |
CAMEL Information |
OC |
– |
Set of CAMEL information related to SMS session. For more information see Description of Record Fields. This field is present if CAMEL service is activated. |
Originating Address |
OC |
OC |
The address of the originating SME. |
Record Extensions |
OC |
OC |
A set of network operator/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. |
6.1.7 Mobile Terminated location request (LCS-MT-CDR)
If enabled, an SGSN Mobile terminated LCS record shall be produced for each mobile terminated location request that is performed via the SGSN. The fields in the record are specified in table 6.1.7.1.
Table 6.1.7.1: SGSN Mobile terminated LCS record (SGSN-LCS-MT)
Field |
Category |
Description |
---|---|---|
Record Type |
M |
SGSN Mobile Terminated LCS. |
Recording Entity |
M |
The E.164 number of the SGSN. |
LCS Client Type |
M |
The type of the LCS client that invoked the LR. |
LCS Client Identity |
M |
Further identification of the LCS client. |
Served IMSI |
M |
The IMSI of the subscriber. |
Served MSISDN |
OC |
The primary MSISDN of the subscriber, if available. |
SGSN Address |
OM |
The IP address of the current SGSN. |
Location Type |
M |
The type of the estimated location. |
LCS QoS |
C |
QoS of the LR, if available. |
LCS Priority |
C |
Priority of the LR, if available. |
MLC Number |
M |
The E.164 address of the requesting GMLC. |
Event Time stamp |
M |
The time at which the Perform_Location_Request is sent by the SGSN. |
Measurement Duration |
OM |
The duration of proceeding the location request. |
Notification To MS User |
C |
The privacy notification to MS user that was applicable when the LR was invoked, if available. |
Privacy Override |
C |
This parameter indicates the override MS privacy by the LCS client, if available. |
Location |
OM |
The LAC and CI when the LR is received. |
Routing Area Code |
OM |
The Routing Area Code to which the LCS terminated. |
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. |
LCS Cause |
OC |
The result of the LR if any failure or partial success happened as known at radio interface. |
Cause for Record Closing |
M |
The reason for closure of the record from this SGSN. |
Diagnostics |
C |
A more detailed information about the Cause for Record Closing if any failure or partial success happened. |
Node ID |
OM |
Name of the recording entity. |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types. |
Charging Characteristics |
M |
The Charging Characteristics used by the SGSN. (always use the subscribed CC). |
Charging Characteristics Selection Mode |
OM |
Holds information about how Charging Characteristics were selected. (only subscribed/home default/visited default). |
Serving Node PLMN Identifier |
Oc |
This field holds the PLMN Identifier (MCC and MNC) serving the UE during this record. Only one value is included in case multiple PLMN Ids are supported by the SGSN. |
CN Operator Selection Entity |
OC |
This field indicates whether the Serving Network identified by the "Serving Node PLMN Identifier” has been selected by the UE or by the network, as defined in TS 29.060 [203] for GPRS, and in TS 29.274 [210] for EPC, if available. |
RAT Type |
OC |
This field indicates the Radio Access Technology (RAT) type currently used by the Mobile Station as defined in TS 29.061 [205], when available. |
Record Extensions |
OC |
A set of network operator/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. |
6.1.8 Mobile originated Location request (LCS-MO-CDR)
If enabled, an SGSN Mobile originated LCS record shall be produced for each mobile originated location request that is performed via the SGSN. The fields in the record are specified in table 6.1.8.1.
Table 6.1.8.1: SGSN Mobile originated LCS record (SGSN-LCS-MO)
Field |
Category |
Description |
---|---|---|
Record Type |
M |
SGSN Mobile Originated LCS. |
Recording Entity |
M |
The E.164 number of the SGSN. |
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. |
Served MSISDN |
OC |
The primary MSISDN of the subscriber, if available. |
SGSN Address |
OM |
The IP address of the current SGSN. |
Location Method |
M |
The type of the location request. |
LCS QoS |
C |
QoS of the LR, if available. |
LCS Priority |
Oc |
Priority of the LR, if available. |
MLC Number |
C |
The E.164 address of the involved GMLC, if applicable. |
Event Time stamp |
M |
The time at which the Perform_Location_Request is sent by the SGSN. |
Measurement Duration |
OM |
The duration of proceeding the location request. |
Location |
OM |
The LAC and CI when the LR is received. |
Routing Area Code |
OM |
The Routing Area Code from which the LCS originated. |
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. |
LCS Cause |
OC |
The result of the LR if any failure or partial success happened as known at radio interface. |
Cause for Record Closing |
M |
The reason for closure of the record from this SGSN. |
Diagnostics |
C |
A more detailed information about the Cause for Record Closing if any failure or partial success happened. |
Node ID |
OM |
Name of the recording entity. |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types. |
Charging Characteristics |
M |
The Charging Characteristics flag set used by the SGSN. |
Charging Characteristics Selection Mode |
OM |
Holds information about how Charging Characteristics were selected. |
Serving Node PLMN Identifier |
Oc |
This field holds the PLMN Identifier (MCC and MNC) serving the UE during this record. Only one value is included in case multiple PLMN Ids are supported by the SGSN. |
CN Operator Selection Entity |
OC |
This field indicates whether the Serving Network identified by the "Serving Node PLMN Identifier” has been selected by the UE or by the network, as defined in TS 29.060 [203] for GPRS, and in TS 29.274 [210] for EPC, if available. |
RAT Type |
OC |
This field indicates the Radio Access Technology (RAT) type currently used by the Mobile Station as defined in TS 29.061 [205], when available. |
Record Extensions |
OC |
A set of network operator/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. |
6.1.9 Network induced Location request (LCS-NI-CDR)
If enabled, an SGSN Network induced LCS record shall be produced for each network induced location request that is performed via the SGSN. The fields in the record are specified in table 6.1.9.1.
Table 6.1.9.1: SGSN Network induced LCS record (SGSN-LCS-NI)
Field |
Category |
Description |
---|---|---|
Record Type |
M |
SGSN Network Induced LCS. |
Recording Entity |
M |
The E.164 number of the SGSN. |
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 |
C |
The IMSI of the subscriber if supplied. |
Served MSISDN |
C |
The primary MSISDN of the subscriber if supplied. |
SGSN Address |
OM |
The IP address of the current SGSN. |
Served IMEI |
OC |
The IMEI or IMEISV of the ME, if available. |
LCS QoS |
C |
QoS of the LR, if available. |
LCS Priority |
C |
Priority of the LR, if available. |
MLC Number |
C |
The E.164 address of the involved GMLC, if applicable. |
Event Time stamp |
M |
The time at which the Perform_Location_Request is sent by the SGSN. |
Measurement Duration |
OM |
The duration of proceeding the location request. |
Location |
OM |
The LAC and CI when the LR is received. |
Routing Area Code |
OM |
The Routing Area Code from which the LCS originated. |
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. |
LCS Cause |
OC |
The result of the LR if any failure or partial success happened as known at radio interface. |
Cause for Record Closing |
M |
The reason for closure of the record from this SGSN. |
Diagnostics |
C |
A more detailed information about the Cause for Record Closing if any failure or partial success happened. |
Node ID |
OM |
Name of the recording entity. |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types. |
Charging Characteristics |
M |
The Charging Characteristics flag set used by the SGSN. |
Charging Characteristics Selection Mode |
OM |
Holds information about how Charging Characteristics were selected. |
Serving Node PLMN Identifier |
Oc |
This field holds the PLMN Identifier (MCC and MNC) serving the UE during this record. Only one value is included in case multiple PLMN Ids are supported by the SGSN. |
CN Operator Selection Entity |
OC |
This field indicates whether the Serving Network identified by the "Serving Node PLMN Identifier” has been selected by the UE or by the network, as defined in TS 29.060 [203] for GPRS, and in TS 29.274 [210] for EPC, if available. |
RAT Type |
OC |
This field indicates the Radio Access Technology (RAT) type currently used by the Mobile Station as defined in TS 29.061 [205], when available. |
Record Extensions |
OC |
A set of network operator/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. |
6.1.10 MBMS bearer context charging data in SGSN (S-MB-CDR)
If the collection of CDR data is enabled then the SGSN data specified in table 6.1.10.1 shall be available for each MBMS bearer context.
Table 6.1.10.1: SGSN MBMS bearer context data (S-MB-CDR)
Field |
Category |
Description |
---|---|---|
Record Type |
M |
SGSN MBMS bearer context record. |
SGSN Address used |
M |
The control plane IP address of the SGSN used. |
Charging ID |
M |
Bearer context identifier used to identify this MBMS bearer context in different records created by GSNs |
List of RAs |
OC |
List of routeing areas receiving data used during this record. equivalent to the list of RAs defined in TS 23.246 [207]. |
Access Point Name Network Identifier |
OM |
The logical name of the connected access point to the BM-SC (network identifier part of APN). |
PDP Type |
OM |
This field indicates PDP type (i.e. IPv4 or IPv6). |
Served PDP Address |
OC |
Indicates the IP Multicast address used for the MBMS bearer context, i.e. IPv4 or IPv6, if available. |
List of Traffic Data Volumes |
OM |
A list of changes in charging conditions for this MBMS bearer context, each change is time stamped. Charging conditions are used to categorize traffic volumes, such as per tariff period. It shall include the required bearer capabilities (QoS Negotiated) |
Record Opening Time |
M |
Time stamp when MBMS bearer context is activated in this SGSN or record opening time on subsequent partial records. |
Duration |
M |
Duration of this record in the SGSN. |
Cause for Record Closing |
M |
The reason for the release of record from this SGSN. |
Diagnostics |
OM |
A more detailed reason for the release of the connection. |
Record Sequence Number |
C |
Partial record sequence number, only present in case of partial records. |
Node ID |
OM |
Name of the recording entity. |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types. |
Number of receiving UEs |
OC |
Indicates the number of UEs receiving the MBMS bearer service |
MBMS Information |
OM |
MBMS related information related to MBMS bearer context being charged, defined in TS 32.273 [33]. |
Record Extensions |
OC |
A set of network operator/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. |
6.1.11 MBMS bearer context charging data in GGSN (G-MB-CDR)
If the collection of CDR data is enabled then the GGSN data specified in table 6.1.11.1 shall be available for each MBMS bearer context.
Table 6.1.11.1: GGSN MBMS bearer context data (G-MB-CDR)
Field |
Category |
Description |
---|---|---|
Record Type |
M |
GGSN MBMS bearer context record. |
GGSN Address used |
M |
The control plane IP address of the GGSN used. |
Charging ID |
M |
Bearer context identifier used to identify this MBMS bearer context in different records created by GSNs |
List of Downstream Nodes |
M |
List of SGSN addresses used during this record. equivalent to the list of downstream nodes defined in TS 23.246 [207]. |
Access Point Name Network Identifier |
OM |
The logical name of the connected access point to the BM-SC (network identifier part of APN). |
PDP Type |
OM |
This field indicates PDP type (i.e. IPv4 or IPv6). |
Served PDP Address |
OC |
Indicates the IP Multicast address used for the MBMS bearer context, i.e. IPv4 or IPv6, if available. |
List of Traffic Data Volumes |
OM |
A list of changes in charging conditions for this MBMS bearer context, each change is time stamped. Charging conditions are used to categorize traffic volumes, such as per tariff period. It shall include the required bearer capabilities (QoS Negotiated). |
Record Opening Time |
M |
Time stamp when MBMS bearer context is activated in this GGSN or record opening time on subsequent partial records. |
Duration |
M |
Duration of this record in the GGSN. |
Cause for Record Closing |
M |
The reason for the release of record from this GGSN. |
Diagnostics |
OM |
A more detailed reason for the release of the connection. |
Record Sequence Number |
C |
Partial record sequence number, only present in case of partial records. |
Node ID |
OM |
Name of the recording entity. |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types. |
MBMS Information |
OM |
MBMS related information related to MBMS bearer context being charged, defined in TS 32.273 [33]. |
Record Extensions |
OC |
A set of network operator/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. |
6.1.12 MBMS bearer context charging data in MBMS GW (MBMS-GW-CDR)
If the collection of CDR data is enabled then the MBMS GW data specified in table 6.1.12.1 shall be available for each MBMS bearer context when MBMS GW doesn’t locate in MB-SC.
Table 6.1.12.1: MBMS GW MBMS bearer context data (MBMS-GW-CDR)
Field |
Category |
Description |
---|---|---|
Record Type |
M |
MBMS GW MBMS bearer context record. |
MBMS GW Address used |
M |
The control plane IP address of the MBMS GW used. |
Charging ID |
M |
Bearer context identifier used to identify this MBMS bearer context in different records created by Evolved Packet System core network elements |
List of Downstream Nodes |
M |
List of SGSN/MME addresses used during this record. equivalent to the list of downstream nodes defined in TS 23.246 [207]. |
Access Point Name Network Identifier |
OM |
The logical name of the connected access point to the BM-SC (network identifier part of APN). |
PDP/PDN Type |
OM |
This field indicates PDN type (i.e. IPv4 or IPv6). |
Served PDP/PDN Address |
OC |
Indicates the IP Multicast address used for the MBMS bearer context. (i.e. IPv4 or IPv6). |
List of Traffic Data Volumes |
OM |
A list of changes in charging conditions for this MBMS bearer context, each change is time stamped. Charging conditions are used to categorize traffic volumes, such as per tariff period. It shall include the required bearer capabilities (QoS Negotiated). |
Record Opening Time |
M |
Time stamp when MBMS bearer context is activated in this MBMS GW or record opening time on subsequent partial records. |
Duration |
M |
Duration of this record in the MBMS GW. |
Cause for Record Closing |
M |
The reason for the release of record from this MBMS GW. |
Diagnostics |
OM |
A more detailed reason for the release of the connection. |
Record Sequence Number |
C |
Partial record sequence number, only present in case of partial records. |
Node ID |
OM |
Name of the recording entity. |
Record Extensions |
OC |
A set of network operator/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types. |
MBMS Information |
OM |
MBMS related information related to MBMS bearer context being charged, defined in TS 32.273 [33]. |
C-TEID |
OC |
Common Tunnel Endpoint Identifier of MBMS GW for user plane, defined in TS 23.246 [207]. |
IP multicast and Source address for distribution |
OC |
IP addresses identifying the SSM channel used for user plane distribution on the backbone network defined in TS 23.246 [207]. |
6.1.13 IP-CAN bearer charging data in ePDG (ePDG-CDR)
If the collection of CDR data is enabled then the ePDG data specified in table 6.1.13.1 shall be available for each IP-CAN bearer.
Table 6.1.13.1: ePDG IP-CAN bearer data (ePDG-CDR)
Field |
Category |
Description |
---|---|---|
Record Type |
M |
ePDG IP-CAN bearer record. |
Retransmission |
OC |
This parameter, when present, indicates that information from retransmitted Charging Data Request has been used in this CDR. |
Served IMSI |
C |
IMSI of the served party, if available. |
IMSI Unauthenticated Flag |
OC |
This field indicates the provided served IMSI is not authenticated (emergency bearer service situation). |
Served IMEI |
OC |
The IMEI or IMEISV of the ME, if available. |
ePDG Address Used |
M |
The control plane IP address of the ePDG used. |
ePDG IPv6 Address |
OC |
The control plane IPv6 address, in case of IPv4v6 dual stack, of the ePDG. |
Charging ID |
M |
IP-CAN bearer Charging identifier used to identify this IP-CAN bearer in different records created by PCNs |
PDN Connection Charging Id |
OM |
This field holds the explicit Charging Id for the PDN connection. When NBIFOM is supported, the PGW will provide a unique PDN Connection Charging ID for the PDN connection. Otherwise the field holds the Charging Id of the EPS default bearer in GTP case, or the unique Charging Id of the IP-CAN session in PMIP case. This field is used to identify different records belonging to same PDN connection. |
SGW Change |
OC |
Present if this is first record after a change from another serving node (i.e. SGW, ePDG). |
PGW PLMN Identifier |
Oc |
PLMN identifier (MCC MNC) of the P-GW used. |
Access Point Name Network Identifier |
OM |
The logical name of the connected access point to the external packet data network (network identifier part of APN). |
PDP/PDN Type |
OM |
This field indicates PDN type (i.e. IPv4, IPv6 or IPv4v6). |
Served PDP/PDN Address |
OC |
IP address allocated for the PDP context / PDN connection, if available, i.e. IPv4 address when PDN Type is IPv4 or IPv6 prefix when PDN Type is IPv6 or IPv4v6. |
Served PDP/PDN Address prefix length |
OC |
PDP/PDN Address prefix length of an IPv6 typed Served PDP Address. The field needs not available for prefix length of 64 bits. |
Served PDP/PDN Address extension |
OC |
This field holds IPv4 address of the served IMSI, if available, when PDN type is IPv4v6. |
Dynamic Address Flag |
OC |
Indicates whether served PDP/PDN address is dynamic, which is allocated during IP-CAN bearer activation, initial attach and UE requested PDN connectivity. This field is missing if IPv4 address is static when PDN Type is IPv4, or if IPv6 address is static when PDN Type is IPv6 or IPv4v6. |
Dynamic Address Flag extension |
OC |
Indicates whether served IPv4 PDP/PDN address is dynamic, which is allocated during IP-CAN bearer activation, initial attach and UE requested PDN connectivity with PDP/PDN type IPv4v6. This field is missing if IPv4 address is static. |
List of Traffic Data Volumes |
OM |
A list of changes in charging conditions for this QCI/ARP pair, each change is time stamped. Charging conditions are used to categorize traffic volumes, such as per tariff period. Initial and subsequently changed QoS and corresponding data values are also listed. |
Record Opening Time |
M |
Time stamp when IP-CAN bearer is activated in this ePDG or record opening time on subsequent partial records. |
Duration |
M |
Duration of this record in the ePDG. |
Cause for Record Closing |
M |
The reason for the release of record from this ePDG. |
Diagnostics |
OM |
A more detailed reason for the release of the IP-CAN bearer, when a single cause is applicable. |
Enhanced Diagnostics |
OC |
This field holds a more detailed reason for the release of the IP-CAN bearer, when a set of causes is applicable. |
Record Sequence Number |
C |
Partial record sequence number, only present in case of partial records. |
Node ID |
OM |
Name of the recording entity. |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types. |
APN Selection Mode |
OM |
An index indicating how the APN was selected. |
Served MSISDN |
OC |
The primary MSISDN of the subscriber, if available. |
Charging Characteristics |
M |
The Charging Characteristics applied to the IP-CAN bearer. |
Charging Characteristics Selection Mode |
OM |
Holds information about how Charging Characteristics were selected. |
IMS Signalling Context |
OC |
Included if the IM-CN Subsystem Signalling Flag is set, see TS 23.060 [201] IP-CAN bearer is used for IMS signalling. |
P-GW Address used. |
OC |
This field is the P-GW IP Address for the Control Plane |
P-GW IPv6 Address |
OC |
This field is the P-GW IPv6 Address, in case of IPv4v6 dual stack, for the Control Plane. |
RAT Type |
OC |
This field indicates the Radio Access Technology (RAT) type currently used by the Mobile Station as defined in TS 29.061 [205], when available. |
Start Time |
OC |
This field holds the time when User IP-CAN session starts, available in the CDR for the first bearer in an IP-CAN session. |
Stop Time |
OC |
This field holds the time when User IP-CAN session is terminated, available in the CDR for the last bearer in an IP-CAN session. |
UWAN User Location Information |
OC |
This field contains the UE location in an Untrusted Wireless Access Network (UWAN) which includes the UE local IP address and optionally UDP or TCP source port number (if NAT is detected) as defined in TS 29.274 [210]. It may also include WLAN location information the ePDG may have received from the 3GPP AAA server about the UE as WLAN location information" defined in TS 29.274[210]. |
User Location Info Time |
OC |
This field contains the time at which the user location information was acquired, if available. |
Record Extensions |
OC |
A set of network operator/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. |
6.1.14 ABC data in TDF (TDF-CDR)
If ABC is enabled and the collection of CDR data is enabled, then the TDF data specified in table 6.1.14.1 shall be available for each TDF session.
NOTE: An indication that online charging is also active for the session may be provided by using PS Furnish Charging Information.
Table 6.1.14.1: TDF session data (TDF-CDR)
Field |
Category |
Description |
---|---|---|
Record Type |
M |
TDF session record. |
Retransmission |
OC |
This parameter, when present, indicates that information from retransmitted Charging Data Request has been used in this CDR. |
Served IMSI |
C |
IMSI of the served party, if available. |
Served IMEI |
OC |
The IMEI or IMEISV of the ME, if available. It is used for identifying the user in case Served IMSI is not present during emergency bearer service. |
Served 3GPP2 MEID |
OC |
MEID of the served party’s terminal equipment for 3GPP2 access. |
Served MN NAI |
OC |
Mobile Node Identifier in NAI format (based on IMSI), if available. |
P-GW Address used |
M |
The control plane IP address of the P-GW used. |
P-GW Address IPv6 |
OC |
The control plane IPv6 address, in case of IPv4v6 dual stack, of the P-GW used. |
TDF Address used |
M |
The control plane IP address of the TDF used. |
TDF Address IPv6 |
OC |
The control plane IPv6 address, in case of IPv4v6 dual stack, of the TDF used. |
PDN Connection Charging ID |
M |
This field is received from PCRF and holds explicit Charging Id for the PDN connection assigned by P-GW to identify different records belonging to same PDN connection. |
Serving node Address |
M |
List of SGSN/S-GW/TWAG control plane IP addresses, or the ePDG address used during this record. |
Serving node IPv6 Address |
OC |
List of SGSN/S-GW/TWAG control plane IPv6 addresses, in case of IPv4v6 dual stack, used during this record. |
Serving node Type |
M |
List of serving node types in control plane (SGSN, SGW, ePDG, AGW, TWAG). The serving node types listed here map to the serving node addresses listed in the field "Serving node Address" in sequence. |
PGW PLMN Identifier |
Oc |
PLMN identifier (MCC MNC) of the P-GW. |
TDF PLMN Identifier |
Oc |
PLMN identifier (MCC MNC) of the TDF. |
Access Point Name Network Identifier |
OM |
The logical name of the connected access point to the external packet data network (network identifier part of APN). |
PDP/PDN Type |
OM |
PDP/PDN type, i.e. IPv4, IPv6, IPv4v6 , or PDP type PPP. |
Served PDP/PDN Address |
OC |
IP address allocated for the PDP context / PDN connection, i.e. IPv4 address when PDP/PDN Type is IPv4 or IPv6 prefix when PDP/PDN Type is IPv6 or IPv4v6. This parameter shall be present except when both the PDP type is PPP and dynamic IP-CAN bearer address assignment is used. |
Served PDP/PDN Address prefix length |
OC |
PDP/PDN Address prefix length of an IPv6 typed Served PDP Address. The field needs not available for prefix length of 64 bits. |
Served PDP/PDN Address extension |
OC |
This field holds IPv4 address of the served IMSI, if available, when PDP/PDN type is IPv4v6. |
Dynamic Address Flag |
OC |
Indicates whether served PDP/PDN address is dynamic, which is allocated during IP-CAN bearer activation, initial attach (E-UTRAN or over S2x) and UE requested PDN connectivity. This field is missing if IPv4 address is static when PDN Type is IPv4, or if IPv6 address is static when PDN Type is IPv6 or IPv4v6. |
Dynamic Address Flag extension |
OC |
Indicates whether served IPv4 PDP/PDN address is dynamic, which is allocated during IP-CAN bearer activation, initial attach (E-UTRAN or over S2x) and UE requested PDN connectivity with PDP/PDN type IPv4v6. This field is missing if IPv4 address is static. |
List of Service Data |
OM |
A list of changes in charging conditions for application traffic within this TDF session categorized per rating group or per combination of the rating group and service id. Each change is time stamped. Charging conditions are used to categorize traffic volumes, elapsed time and number of events, such as per tariff period and subsequently changed maximal bandwidth limitation and corresponding data values are also listed. Online charging information (PS Furnish Charging Information) may be added per each service data container in case it is sent by the OCS. Failure-Handling: This field shall be present in case TDF initiates an interaction with the PCRF in relation to the OCS’s guidance for Failure Handling. It shall indicate the Failure Handling scenario and the instant the Failure Action is triggered (see annex B). Scenarios: Continue/New Session; Continue/Ongoing Session; Retry&Terminate/Ongoing Session; Terminate/Ongoing Session. |
Record Opening Time |
M |
Time stamp when TDF session is established or record opening time on subsequent partial records. |
MS Time Zone |
OC |
This field contains the MS Time Zone the MS is currently located as defined in TS 29.060 [203], if available. |
Duration |
M |
Duration of this record in the TDF. |
Cause for Record Closing |
M |
The reason for closing the record from this TDF. |
Diagnostics |
OM |
A more detailed reason forclosing the record. |
Record Sequence Number |
C |
Partial record sequence number, only present in case of partial records. |
Node ID |
OM |
Name of the recording entity. |
Record Extensions |
OC |
A set of network operator/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types. |
APN Selection Mode |
OM |
An index indicating how the APN was selected. |
Served MSISDN |
OC |
The primary MSISDN of the subscriber, if available. |
User Location Information |
OC |
This field contains the User Location Information of the MS as defined in TS 29.060 [203] for GPRS case, and in TS 29.274 [210] for EPC case, if available. |
User CSG information |
OC |
This field contains the User CSG Information of the UE, if available, including CSG ID, access mode and CSG membership indication. |
3GPP2 User Location information |
OC |
This field contains the User Location Information of the MS as defined in TS 29.212 [216] for 3GPP2 access, if available. |
TWAN User Location Information |
OC |
This field contains the UE location in a Trusted WLAN Access Network (TWAN) , if available: – as "TWAN identifier" defined in TS 29.274 [210] for S2a GTP-based case, or, – as "Access Network Identifier Option IE" defined in 29.275 [211] for S2a PMIP-based case. |
Charging Characteristics |
M |
The Charging Characteristics applied to the TDF session. |
Charging Characteristics Selection Mode |
OM |
Holds information about how Charging Characteristics were selected. |
Serving node PLMN Identifier |
OM |
This fields holds the PLMN Identifier (MCC and MNC) serving the UE during this record. When the Serving node is TWAG, this field includes the PLMN identifier used for UE authentication, i.e. the VPLMN in roaming case, and the HPLMN in non-roaming case. |
PS Furnish Charging Information |
OC |
Online charging session specific information |
RAT Type |
OC |
This field indicates the Radio Access Technology (RAT) type currently used by the Mobile Station as defined in TS 29.061 [205], when available. |
Start Time |
OC |
This field holds the time when TDF session starts. |
Stop Time |
OC |
This field holds the time when TDF session is terminated. |
6.1.15 IP-CAN bearer charging data in TWAG (TWAG-CDR)
If the collection of CDR data is enabled then theTWAG data specified in table 6.1.15.1 shall be available for each IP-CAN bearer.
Table 6.1.15.1: TWAG IP-CAN bearer data (TWAG-CDR)
Field |
Category |
Description |
---|---|---|
Record Type |
M |
TWAG IP-CAN bearer record. |
Retransmission |
OC |
This parameter, when present, indicates that information from retransmitted Charging Data Request has been used in this CDR. |
Served IMSI |
C |
IMSI of the served party, if available. |
IMSI Unauthenticated Flag |
OC |
This field indicates the provided served IMSI is not authenticated (emergency bearer service situation). |
Served IMEI |
OC |
The IMEI or IMEISV of the ME, if available. |
TWAG Address Used |
M |
The control plane IP address of the TWAG used. |
TWAG IPv6 Address |
OC |
The control plane IPv6 address, in case of IPv4v6 dual stack, of the TWAG. |
Charging ID |
M |
IP-CAN bearer Charging identifier used to identify this IP-CAN bearer in different records created by PCNs |
PDN Connection Charging Id |
OM |
This field holds the explicit Charging Id for the PDN connection. When NBIFOM is supported, the PGW will provide a unique PDN Connection Charging ID for the PDN connection. Otherwise the field holds the Charging Id of the EPS default bearer in GTP case, or the unique Charging Id of the IP-CAN session in PMIP case. This field is used to identify different records belonging to same PDN connection. |
SGW Change |
OC |
Present if this is first record after a change from another serving node (i.e. SGW, ePDG, TWAG). |
PGW PLMN Identifier |
Oc |
PLMN identifier (MCC MNC) of the P-GW used. |
Access Point Name Network Identifier |
OM |
The logical name of the connected access point to the external packet data network (network identifier part of APN). |
PDP/PDN Type |
OM |
This field indicates PDN type (i.e. IPv4, IPv6 or IPv4v6). |
Served PDP/PDN Address |
OC |
IP address allocated for the PDP context / PDN connection, if available, i.e. IPv4 address when PDN Type is IPv4 or IPv6 prefix when PDN Type is IPv6 or IPv4v6. |
Served PDP/PDN Address prefix length |
OC |
PDP/PDN Address prefix length of an IPv6 typed Served PDP Address. The field needs not available for prefix length of 64 bits. |
Served PDP/PDN Address extension |
OC |
This field holds IPv4 address of the served IMSI, if available, when PDN type is IPv4v6. |
Dynamic Address Flag |
OC |
Indicates whether served PDP/PDN address is dynamic, which is allocated during IP-CAN bearer activation, initial attach and UE requested PDN connectivity. This field is missing if IPv4 address is static when PDN Type is IPv4, or if IPv6 address is static when PDN Type is IPv6 or IPv4v6. |
Dynamic Address Flag extension |
OC |
Indicates whether served IPv4 PDP/PDN address is dynamic, which is allocated during IP-CAN bearer activation, initial attach and UE requested PDN connectivity with PDP/PDN type IPv4v6. This field is missing if IPv4 address is static. |
List of Traffic Data Volumes |
OM |
A list of changes in charging conditions for this QCI/ARP pair, each change is time stamped. Charging conditions are used to categorize traffic volumes, such as per tariff period. Initial and subsequently changed QoS and corresponding data values are also listed. |
Record Opening Time |
M |
Time stamp when IP-CAN bearer is activated in this TWAG or record opening time on subsequent partial records. |
Duration |
M |
Duration of this record in the TWAG. |
Cause for Record Closing |
M |
The reason for the release of record from this TWAG. |
Diagnostics |
OM |
A more detailed reason for the release of the IP-CAN bearer, when a single cause is applicable. |
Enhanced Diagnostics |
OC |
This field holds a more detailed reason for the release of the IP-CAN bearer, when a set of causes is applicable. |
Record Sequence Number |
C |
Partial record sequence number, only present in case of partial records. |
Node ID |
OM |
Name of the recording entity. |
Local Record Sequence Number |
OM |
Consecutive record number created by this node. The number is allocated sequentially including all CDR types. |
APN Selection Mode |
OM |
An index indicating how the APN was selected. |
Served MSISDN |
OC |
The primary MSISDN of the subscriber, if available. |
TWAN User Location Information |
OC |
This field contains the UE location in a Trusted WLAN Access Network (TWAN) , if available: – as "TWAN identifier" defined in TS 29.274 [210] for S2a GTP-based case, or, – as "Access Network Identifier Option IE" defined in 29.275 [211] for S2a PMIP-based case. |
Charging Characteristics |
M |
The Charging Characteristics applied to the IP-CAN bearer. |
Charging Characteristics Selection Mode |
OM |
Holds information about how Charging Characteristics were selected. |
P-GW Address used. |
OC |
This field is the P-GW IP Address for the Control Plane |
P-GW IPv6 Address |
OC |
This field is the P-GW IPv6 Address, in case of IPv4v6 dual stack, for the Control Plane. |
RAT Type |
OC |
This field indicates the Radio Access Technology (RAT) type currently used by the Mobile Station as defined in TS 29.061 [205], when available. |
Start Time |
OC |
This field holds the time when User IP-CAN session starts, available in the CDR for the first bearer in an IP-CAN session. |
Stop Time |
OC |
This field holds the time when User IP-CAN session is terminated, available in the CDR for the last bearer in an IP-CAN session. |
Record Extensions |
OC |
A set of network operator/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. |
6.2 Data description for PS online charging
6.2.1 Message contents
6.2.1.1 Summary of online charging message formats
The PS Online Charging uses the Debit / Reserve Units Request and Debit / Reserve Units Response messages defined in TS 32.299 [50].
Table 6.2.1.1.1 describes the use of these messages for online charging.
Table 6.2.1.1.1: Online charging messages reference table
Messages |
Source |
Destination |
Debit / Reserve Units Request |
PCEF, TDF |
OCS |
Debit / Reserve Units Response |
OCS |
PCEF, TDF |
6.2.1.2 Structure for the Debit / Reserve Units operation message formats
6.2.1.2.0 General
This clause describes the AVPs used in the Debit / Reserve Units operation messages.
6.2.1.2.1 Debit / Reserve Units Request message
Table 6.2.1.2.1.1 illustrates the basic structure of a Debit / Reserve Units Request message from the PCEF and TDF as used for PS online charging.
Table 6.2.1.2.1.1: Debit / Reserve Units Request message contents
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 |
OM |
Described in TS 32.299 [50] |
User Name |
OM |
The content of the field corresponds to the Protocol Configuration Options (PCO) field of the Create IP-CAN bearer Request message. |
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]. As a minimum the IMSI and the MSISDN have to be included. |
Termination Cause |
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] |
User-Equipment-Info |
OC |
Described in TS 32.299 [50]. Contains the identification of the terminal (IMEI or IMEISV etc.) |
Route Information |
OC |
Described in TS 32.299 [50] |
Service Information |
OM |
Described in clause 6.3.1.1 |
Editor’s Note: Terminal capabilities should be taken into account
The full description of the AVPs is specified in TS 32.299 [50].
6.2.1.2.2 Debit / Reserve Units Response message
The following table 6.2.1.2.2.1 llustrates the basic structure of a Debit / Reserve Units operation message as used for the PCEF and TDF. This message is always used by the OCS as specified below, independent of the receiving PCEF/TDF and the C redit-Control type that is being replied to.
Table 6.2.1.2.2.1: Debit / Reserve Units Response message contents
Information Element |
Category |
Description |
---|---|---|
Session Identifier |
M |
Described in 32.299 [50] |
Operation Result |
M |
Described in 32.299 [50] |
Originator Host |
M |
Described in 32.299 [50] |
Originator Domain |
M |
Described in 32.299 [50] |
Operation Identifier |
M |
Described in 32.299 [50] |
Operation Type |
M |
Described in 32.299 [50] |
Operation Number |
M |
Described in 32.299 [50] |
Operation Failover |
OC |
Described in 32.299 [50] |
Multiple Unit Operation |
OC |
Described in 32.299 [50] |
Operation Failure Action |
OC |
Described in 32.299 [50] |
Operation Event Failure Action |
OC |
Described in 32.299 [50] |
Redirection Host |
OC |
Described in 32.299 [50] |
Redirection Host Usage |
OC |
Described in 32.299 [50] |
Route Information |
OC |
Described in 32.299 [50] |
Failed parameter |
OC |
Described in 32.299 [50] |
Service Information |
OM |
Described in 32.299 [50] |
6.2.2 Void
6.3 PS charging specific parameters
6.3.1 Definition of PS charging information
6.3.1.0 General
The PS Information parameter used for PS charging is provided in the Service Information parameter, as defined in clause 6.3.1.1.
The PS Information parameter used for "SMS over MME Charging" is provided in the Service Information parameter as defined in 6.3.1.1a
6.3.1.1 PS charging information assignment for Service Information
The components in the Service Information that are use for PS charging can be found in table 6.3.1.1.1.
Table 6.3.1.1.1: Service Information used for PS Charging
Information Element |
Category |
Description |
Service Information |
OM |
This is a structured field and holds the 3GPP specific parameter as defined in TS 32.299 [50]. |
Subscriber Identifier |
OC |
This field contains the identification of the user (e.g. IMSI, MSISDN, NAI) if offline charging applies. |
PS Information |
OM |
This is a structured field and holds the PS specific parameters. |
IMS Information |
OM |
This is a structured field and holds IMS specific parameters. |
Node Functionality |
OM |
This field contains the function of the EPC node (SGW, ePDG, TWAG, PGW, TDF) |
NOTE: When Node Functionality is set to "HSGW" the HSGW Access specific charging information are provided as part of the PS Information |
6.3.1.1a "SMS over MME Charging" information assignment for Service Information
The components in the Service Information that are used for "SMS over MME Charging"can be found in table 6.3.1.1a.1.
Table 6.3.1.1a.1: Service Information used for "SMS over MME Charging"
Information Element |
Category |
Description |
Service Information |
OM |
This is a structured field and holds the 3GPP specific parameter as defined in TS 32.299 [50]. |
Subscriber Identifier |
OC |
This field contains the identification of the user (e.g. IMSI, MSISDN). |
IMS Information |
OM |
This is a structured field and holds IMS specific parameters. |
Node Functionality |
OM |
This field contains the function of the EPC node (i.e. MME) |
PS Information |
OM |
This is a structured field and holds the PS specific parameters. |
Node Id |
OC |
This fields holds the name of the Node |
Serving Node Type |
OC |
This field holds the type of the node handling the SMS with the UE (i.e. MME) |
Serving Node Adddress |
OC |
This field holds the IP-address of the MME used. It may occur twice in the case when the MME has IPv4v6 dual stack control plane. |
MME Number for MT SMS |
OC |
This field holds the MME international PSTN/ISDN number |
MME Name |
OC |
This field holds the operation Identity of the MME used. |
MME Realm |
OC |
This field holds the operation Realm Identity of the MME used. |
Charging Characteristics |
OM |
This field contains the Charging Characteristics applicable to the MME |
Charging Characteristics Selection Mode |
OM |
This field holds information about how the Charging Characteristics were selected. |
3GPP User Location Info |
OC |
This field holds the information about the location of the subscriber during the SMS transaction. |
User Location Info Time |
OC |
This field contains the time at which the user location information was acquired. |
RAT Type |
OC |
This field indicates which Radio Access Technology (RAT) is currently serving the UE as defined in TS 29.061 [205]. |
Terminal Information |
OC |
This field holds the identification of the terminal (IMEI or IMEISV). |
SMS Information |
OM |
This is a structured field and holds SMS specific parameters. |
Recipient Info |
OM |
This field a structured field and holds recipient information for the SM. The complete structure is defined in TS 32.274 [34]. |
Recipient Address |
OM |
This field holds the address of the recipient of the SM. |
SMSC Address |
OM |
This field holds the address of the SMSC to which the originating or terminating SM is directed to. |
MMS Information |
OM |
This is a structure field and the following parameters are specific to SMS. The complete structure is defined in TS 32.270 [30] |
Originator Address |
OC |
This field holds the address of the originator of the SM. |
Submission Time |
OC |
This field holds the time the Short Message is received by the MME from UE or sent by the MME to UE. |
Message Id |
OM |
This field holds a reference provided by the UE uniquely identifying this message. It contains the TP-Message-Reference (TP-MR) as defined in TS 23.040 [7]. |
6.3.1.2 Definition of the PS information
PS specific charging information is provided within the PS Information. The fields of the PS Information are indicated with the node (MME, S-GW, ePDG, TWAG, P-GW, TDF) from which the information is sent.
The detailed structure of the PS Information can be found in table 6.3.1.2.1.
Table 6.3.1.2.1: Structure of the PS Information
Information Element |
Category |
Description |
Supported Features |
OC |
This field holds the list of features supported by the PCN, CDF or OCF as defined in clause 6.3.1.x. |
Charging Id |
OC |
This field holds the Charging Id for this IP-CAN bearer (this together with the P-GW Address constitutes a unique identifier for the IP-CAN bearer). This field holds the unique Charging Id in the PMIP case. When charging per IP-CAN session is active, PGW use this field to hold the Charging Id of the EPS default bearer. It is the same as the PDN Connection Charging Id. |
Charging per IP-CAN Session Indicator |
Oc |
This field indicates whether charging per IP-CAN session is active. If this field is not present, charging per IP-CAN session is not active. |
Node Id |
OC |
This fields holds the name of the Node |
PDN Connection Charging Id |
OC |
This field holds the explicit Charging Id for the PDN connection. When NBIFOM is supported, the PGW will assign an explicit PDN Connection Charging ID for the PDN connection. Otherwise the field holds the Charging Id of the EPS default bearer. This field is used to identify different records belonging to same PDN connection. |
PDP/PDN Type |
OC |
This field holds the type of IP-CAN bearer, e.g. IP or PPP, or PDN type (i.e. IPv4, IPv6 or IPv4v6, or Non-IP). |
SGi PtP Tunnelling Method |
OC |
This field indicates whether SGi PtP tunnelling method based on UDP/IP or other methods are used for this PDN connection when a non-IP PDN type. |
SCS/AS Address |
OC |
This field holds the Address of SCS/AS for SGi PtP tunnelling. |
PDP/PDN Address |
OC |
This field holds the IP address of the served IMSI allocated for the PDP context / PDN connection, i.e. IPv4 address or IPv6 prefix, or assigned IP address if any when PDP/PDN Type is Non-IP. This parameter shall be present except: – when both the PDP type is PPP and dynamic PDP address assignment is used or, – when PDP/PDN Type is Non-IP, and no IP address has been assigned by the PGW for the PDN connection. It may occur twice within the PS Information field when PDN type is IPv4v6: first occurrence with IPv6 prefix, second occurrence with IPv4 address. |
PDP/PDN Address prefix length |
OC |
PDP/PDN Address prefix length of an IPv6 typed Served PDP Address. The field needs not available for prefix length of 64 bits. |
Dynamic Address Flag |
OC |
This field indicates whether served PDP/PDN address is dynamically allocated. This field is missing if address is static. |
Dynamic Address Flag Extension |
OC |
Indicates whether served IPv4 PDP/PDN address is dynamic, which is allocated during IP-CAN bearer activation, initial attach (E-UTRAN or over S2x) and UE requested PDN connectivity with PDP/PDN type IPv4v6. This field is missing if IPv4 address is static. |
Negotiated QoS Profile |
OC |
This field holds the authorized QoS applied to IP-CAN bearer. See NOTE. This field indicates the bandwith limitation, applied to TDF session in TDF case. When charging per IP-CAN session is active in P-GW, this field indicates the APN-AMBR applied to the IP-CAN session. |
Serving Node Address |
OC |
This field holds the SGSN/S-GW/TWAG IP address that is used by the control plane for the handling of control messages, or the AGW IP address, or the ePDG address, or the MME address. It may be used to identify the PLMN to which the user is attached. It may occur twice in the case when the serving node has IPv4v6 dual stack control plane. |
Serving Node Type |
OC |
This field holds the type of the serving node (SGSN/S-GW/ePDG/AGW/TWAG from PGW/TDF, or SGSN/MME from SGW). |
SGW Change |
OC |
This field is present if this is first Charging Data Request after a change from another serving node (from SGW/ePDG/ TWAG/HSGW). |
PGW Address |
OC |
This field holds the IP-address of the P-GW that generated the Charging Id. It may occur twice in the case when the P-GW has IPv4v6 dual stack control plane. |
TDF Address |
OC |
The control plane IP address of the TDF used. It may occur twice in the case when the TDF has IPv4v6 dual stack control plane. |
SGW Address |
OC |
This field holds the IP-address of the S-GW used. It may occur twice in the case when the P-GW has IPv4v6 dual stack control plane. |
ePDG Address |
OC |
This field holds the IP-address of the ePDG used. It may occur twice in the case when the ePDG has IPv4v6 dual stack control plane. |
TWAG Address |
OC |
This field holds the IP-address of the TWAG used. It may occur twice in the case when the TWAG has IPv4v6 dual stack control plane. |
MME Number for MT SMS |
OC |
This field holds the MME international PSTN/ISDN E.164 number used for "SMS over MME Charging". |
MME Name |
OC |
This field holds the operation Identity of the MME used for "SMS over MME Charging". |
MME Realm |
OC |
This field holds the operation Realm Identity of the MME used for "SMS over MME Charging". |
CG Address |
OC |
This field holds the Charging Gateway IP address if available. Only used in EPC Online Charging. |
IMSI MCC MNC |
OC |
This field holds the MCC and MNC extracted from the user’s IMSI (first 5 or 6 digits, as applicable from the presented IMSI). |
IMSI Unauthenticated Flag |
OC |
This field is present when IMSI is provided in Subscription Id and this IMSI is unauthenticated (due to emergency bearer service situations). |
PGW MCC MNC |
OC |
This field holds the MCC-MNC of the network the P-GW belongs to. |
TDF MCC MNC |
OC |
PLMN identifier (MCC MNC) of the TDF. |
NSAPI |
OC |
This field Identifies a particular IP-CAN bearer for the associated PDN and MSISDN/IMSI from creation to deletion. See NOTE. |
Called Station Id |
OC |
This field contains the identifier of the access point (APN) the user is connected to. |
Session Stop Indicator |
OC |
This field indicates to the OCS that the last IP-CAN bearer of a session is released and that the IP-CAN session has been terminated. This field only indicates to the OCS that the TDF session is terminated in TDF case. |
Selection Mode |
OC |
This field contains the Selection mode for this APN received in the Create PDP context request, on E-UTRAN initial attach and UE requested PDN connectivity, or Attach in WLAN on GTP S2a. |
Charging Characteristics |
OC |
This field contains the Charging Characteristics for this IP-CAN bearer received in the Create IP-CAN bearer Request Message (only available in R99 and later releases). |
Charging Characteristics Selection Mode |
OC |
This field holds information about how the "Charging Characteristics" was selected. |
Serving Node MCC MNC |
OC |
This field holds the MCC and MNC serving the UE: extracted from the RAI within the IP-CAN bearer activation or Update messages received over Gn/Gp, or provided by the SGW in the "Serving Network" IE over S5/S8 or by AGW/TWAG (For TWAN, PLMN identifier used for UE authentication, i.e. the VPLMN in roaming case, and the HPLMN in non-roaming case). |
CN Operator Selection Entity |
OC |
This field indicates whether the Serving Network identified by the "Serving Node MCC MNC" has been selected by the UE or by the network, as defined in TS 29.060 [203] for GPRS, and in TS 29.274 [210] for EPC, if available. |
MS Time Zone |
OC |
This field indicates the offset between universal time and local time in steps of 15 minutes of where the MS currently resides. |
Charging Rule Base Name |
OC |
This field indicates the name of a pre‑defined group of PCC rules residing at the PCEF. It may occur several times within the PS Information field. |
ADC Rule Base Name |
OC |
This field indicates the name of a pre-defined group of ADC rules in TDF case. |
User Location Info |
OC |
This field indicates details of where the UE is currently located (e.g. SAI, TAI, RAI, CGI, ECGI or access-specific user location information). |
User Location Info Time |
OC |
This field contains the time at which the user location information was acquired, if available. |
PSCell Information |
OC |
This field holds the PSCell information: Primary SCG (Secondary Cell Group) Cell information |
User CSG Information |
OC |
This field indicates details of the User CSG Information of the UE, if available, including CSG ID, access mode and CSG membership indication. |
3GPP2 User Location Info |
OC |
This field holds the 3GPP2 User Location Info of where the UE is currently located (i.e. 3GPP2 BSID: Cell-Id, SID, NID), as defined in TS 29.212 [216] |
TWAN User Location Information |
OC |
This field contains the UE location in a Trusted WLAN Access Network (TWAN) , if available: – as "TWAN identifier" defined in TS 29.274 [210] for S2a GTP-based case, or, – as "Access Network Identifier Option IE" defined in 29.275 [211] for S2a PMIP-based case. |
UWAN User Location Information |
OC |
This field contains the UE location in an Untrusted Wireless Access Network (UWAN) which includes the UE local IP address and optionally UDP or TCP source port number (if NAT is detected) as defined in TS 29.274 [210]. It may also include WLAN location information the ePDG may have received from the 3GPP AAA server about the UE as "WLAN location information" defined in TS 29.274 [210]. |
Presence Reporting Area Information |
OC |
This field contains part of the Presence Reporting Area Information of UE as defined in TS 29.212 [216], comprising the Presence Reporting Area identifier(s) the Presence Reporting Area(s) status (UE presence or not, inactive), and which Node subscribed-to, or the Presence Reporting Area is set to inactive, if available. It may occur several times within the PS Information field. |
RAT Type |
OC |
This field indicates which Radio Access Technology (RAT) is currently serving the UE as defined in TS 29.061 [205]. When NBIFOM is accepted by PCRF, this field holds the first default bearer’s RAT type when charging per IP-CAN session is active. |
Furnish Charging Information |
OC |
This field contains the PS Furnish Information Elements. |
Offline Charging |
OC |
This field contains the Offline Charging parameters to control offline charging. |
PDP Context Type |
OC |
This field indicates the type of a PDP context (i.e. Primary or Secondary). This field is present when using the Gn/Gp reference point only. |
Traffic data volumes |
OC |
This field holds the containers associated to a charging condition change on an IP-CAN bearer. This is included when triggers conditions are met (Qos change, tariff time change …). It may occur several times within the PS Information field. |
Service data container |
OC |
This field holds the container associated to a service condition change on a service data flow (categorized per rating group or per combination of the rating group and service id) within this IP-CAN bearer. For TDF case, this field holds the container associated to a charging condition change on an application traffic (categorized per rating group or per combination of the rating group and service id) within this TDF session. It may occur several times within the PS Information field. |
User Equipment Info |
OC |
This field holds the identification of the terminal (IMEI or IMEISV…) It is used for identifying the user in case IMSI is not present during emergency bearer service. Editor’s Note: Alignement with online charging is needed. |
Terminal Information |
OC |
This field holds the identification of the terminal (IMEI or IMEISV, 3GPP2-MEID..).It is used for identifying the user in case IMSI is not present during emergency bearer service. Editor’s Note : this parameter is only for offline charging and usage for online charging instead of User-Equipment-info is ffs |
Start Time |
OC |
Timestamp when User IP-CAN/TDF session starts. |
Stop Time |
OC |
Timestamp when User IP-CAN/TDF session terminates. |
Change Condition |
OC |
This field holds the reason for sending Charging Data Request from the PCN Nodes. |
Diagnostics |
OC |
This field holds a more detailed reason for the release of theIP-CAN bearer, when a single cause is applicable, and complements the "Change Condition" information. When charging per IP-CAN session is active, PGW uses this field to hold a more detailed reason for the release of the IP-CAN session, when a single cause is applicable. |
Enhanced Diagnostics |
OC |
This field holds a more detailed reason for the release of the connection, when a set of causes is applicable. |
Low Priority Indicator |
OC |
This field indicates if this IP-CAN session has a low priority, i.e. for Machine Type Communication. |
NBIFOM Support |
OC |
This field indicates that NBIFOM was requested by the UE, supported and accepted by the network for the IP-CAN session or if NBIFOM is not supported for the IP-CAN session. |
NBIFOM Mode |
OC |
This field indicates the NBIFOM mode selected for the PDN connection, when NBIFOM is supported for the IP-CAN session. This field is only present when NBIFOM is accepted. |
CP CIoT EPS Optimisation indicator |
OC |
This field indicates whether CP CIoT EPS Optimisation is used during data transfer with the UE (i.e. Control Plane NAS PDU via S11-U between SGW and MME) or not (i.e. User Plane via S1-U between SGW and eNB), if enabled. |
UNI PDU CP Only Flag |
OC |
This field indicates whether this PDN connection is applied with "Control Plane Only Flag" for UNI PDU transfer, i.e. transfer only using Control Plane NAS PDU (Control Plane CIoT EPS optimisation). |
Serving PLMN Rate Control |
Oc |
This field holds the Serving PLMN Rate Control used by the MME. |
MO exception data counter |
Oc |
This field holds the MO exception data counter value with the timestamp indicating the time at which the counter value increased from 0 to 1, as defined in TS 29.274 [210]. |
APN Rate Control |
Oc |
This field holds the list of APN Rate Controls enforced in the PGW. |
3GPP PS Data Off Status |
Oc |
This field holds the 3GPP Data off Status when UE’s 3GPP Data Off status is Activated or Deactivated. |
Unused Quota Timer |
Oc |
This field holds the threshold for the time period without any quota granted or any quota being consumed for any rating group belonging to the Gy session. It holds either the value configured in PCEF, if it is supported, or the value to be used as received from the OCS. A value of zero indicates that this mechanism shall not be used. |
RAN Secondary RAT Usage Report |
Oc |
This field holds a volumes container timestamped, reported from RAN for secondary RAT usage. It may occur several times within the PS Information field. |
NOTE: For network requested secondary IP-CAN bearer activation, the CCR[Initial] does not contain a value of NSAPI, whilst the Negotiated QoS profile reflects the requested QoS profile used in the activation request.
Editor’s Note: The handling of "CP CIoT EPS Optimisation" when charging per IP-CAN session applies is FFS.
6.3.1.3 Multiple Unit Operation information when charging per IP-CAN session is active
The components in the Multiple Unit Operation that are used when charging per IP-CAN session is active can be found in table 6.3.1.3.1.
Table 6.3.1.3.1: Structure of the Multiple Unit Operation when charging per IP-CAN session is active
Information Element |
Category |
Description |
---|---|---|
Granted Service Unit |
OC |
As specified in TS 32.299 [50]. |
Tariff Time Change |
OC |
As specified in TS 32.299 [50]. |
CC Time |
OC |
As specified in TS 32.299 [50]. |
CC Total Octets |
OC |
As specified in TS 32.299 [50]. |
CC Input Octets |
OC |
As specified in TS 32.299 [50]. |
CC Output Octets |
OC |
As specified in TS 32.299 [50]. |
CC Service Specific Units |
OC |
As specified in TS 32.299 [50]. |
Requested Service Unit |
OC |
As specified in TS 32.299 [50]. |
CC Time |
OC |
As specified in TS 32.299 [50]. |
CC Total Octets |
OC |
As specified in TS 32.299 [50]. |
CC Input Octets |
OC |
As specified in TS 32.299 [50]. |
CC Output Octets |
OC |
As specified in TS 32.299 [50]. |
CC Service Specific Units |
OC |
As specified in TS 32.299 [50]. |
Used Service Unit |
OC |
As specified in TS 32.299 [50]. |
Reporting Reason |
OM |
As specified in TS 32.299 [50]. |
Tariff Change Usage |
OM |
As specified in TS 32.299 [50]. |
CC Time |
OC |
As specified in TS 32.299 [50]. |
CC Total Octets |
OC |
As specified in TS 32.299 [50]. |
CC Input Octets |
OC |
As specified in TS 32.299 [50]. |
CC Output Octets |
OC |
As specified in TS 32.299 [50]. |
CC Service Specific Units |
OC |
As specified in TS 32.299 [50]. |
Event Charging Time Stamp |
OC |
As specified in TS 32.299 [50]. |
Service Identifier |
OC |
As specified in TS 32.299 [50]. |
Rating Group |
OC |
As specified in TS 32.299 [50]. |
Reporting Reason |
OC |
As specified in TS 32.299 [50]. |
Trigger |
OC |
As specified in TS 32.299 [50]. |
Related Trigger |
OC |
This field indicates the trigger condition associated with an alternate access of a multi-access PDN connection that indirectly triggered this multiple unit operation. |
Refund Information |
OC |
As specified in TS 32.299 [50]. |
Envelope |
OC |
As specified in TS 32.299 [50]. |
AF Correlation Information |
OC |
Supported for PS domain charging, as specified in TS 32.299 [50]. |
Service Specific Info |
OC |
Supported for PS domain charging, as specified in TS 32.299 [50]. |
QoS Information |
OC |
This field contains the authorized QoS for the first IP-CAN bearer for which traffic is reported for the Rating Group or Rating Group / Service Identifier. If traffic from multiple bearers is included in the report, only one field is included. This field includes: QCI and ARP. For non-GBR QCI values, this field also includes the MBR for the downlink and uplink direction. For GBR QCI values, this field also includes GBR for the downlink and uplink direction. If the MBR is different than the GBR, then this field also includes the MBR for the downlink and uplink direction. This field also includes the authorized APN-AMBR for the IP-CAN session. |
RAT Type |
OC |
This field contains the RAT Type of the IP-CAN bearer that is first reported for the Rating Group or Rating Group / Service Identifier. If traffic from multiple access types is included in this report, only one field is included. This field is only applicable when NBIFOM is accepted for the IP-CAN session. |
Editor’s Note: The handling of "Control Plane CIoT EPS Optimisation" when charging per IP-CAN session applies is FFS.
6.3.1.4 Supported features
The Supported features information that is used for PS domain charging is based on the information defined for the supported features mechanism specified in clause 6.5.10 TS 32.299 [50].
The following table defines the features applicable for the feature lists with a Feature-List-ID of 1.
Table 6.3.1.4: Features of Feature-List-ID 1 used in PS charging
Feature bit |
Feature |
Description |
Online/Offline |
0 |
EDCE5-CH |
This feature indicates the support of 5G New Radio via Dual Connectivity based on clause 5.2.1.11 Data Volume Reporting for Secondary RAT usage. |
Offline |
1 |
eFMSS_CH |
This feature indicates the support of Flexible Mobile Service Steering based on clause 5.1.6. |
Both |
2 |
WAEPC_CH_Untrusted |
This feature indicates the support of extensions of UWAN location information |
Both |
3 |
WAEPC_CH_trusted |
This feature indicates the support of extensions of TWAN location information |
Both |
4 |
EDCE5-CH_Extended-BW-NR |
This feature indicates the support of 5G New Radio extended QoS. |
Both |
5 |
EDCE5-CH_PSCELL_ID |
This feature indicates the support of PSCELL ID when Dual Connectivity is supported |
Offline |
Feature bit: The order number of the bit within the Feature-List AVP where the least significant bit is assigned number "0". Feature: A short name that can be used to refer to the bit and to the feature, e.g. "EPS". Feature in this table is always mandatory since it relates to the charging functionality of a network feature. Description: A clear textual description of the feature. |
6.3.2 Detailed message format for offline charging
The following clause specifies per Operation Type the charging data that are sent by MME, S-GW, ePDG, TWAG, P-GW and TDF.
The Operation Types are listed in the following order: S (Start)/I (Interim)/S (Stop)/E (Event). Therefore, when all Operation Types are possible it is marked as SISE. If only some Operation Types are allowed for a node, only the appropriate letters are used (i.e. SIS or E) as indicated in the table heading. The omission of an Operation Type for a particular field is marked with "-" (i.e. SI-E). Also, when an entire field is not allowed in a node the entire cell is marked as "-".
Table 6.3.2.1 illustrates the basic structure of the supported fields in the Charging Data Request message for PS offline charging.
Table 6.3.2.1: Supported fields in Charging Data Request message
Information Element |
Node Type |
S-GW |
ePDG |
P-GW |
TWAG |
TDF |
---|---|---|---|---|---|---|
Supported Operation Types |
S/I/S/E |
S/I/S/E |
S/I/S/E |
S/I/S/E |
S/I/S/E |
|
Session Identifier |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
Originator Host |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
Originator Realm |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
Destination Domain |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
Operation Type |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
Operation Number |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
Operation Identifier |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
User Name |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
Destination Host |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
Operation Interval |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
Origination State |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
Origination Timestamp |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
Proxy Information |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
Route Information |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
Operation Token |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
Service Information with PS and IMS Information |
||||||
Supported Features |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
Subscription Id |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
IMSI Unauthenticated Flag |
SIS- |
SIS- |
SIS- |
SIS- |
– |
|
Node Functionality |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
Charging Id |
SIS- |
SIS- |
SIS- |
SIS- |
– |
|
Charging per IP-CAN Session Indicator |
– |
– |
S— |
– |
– |
|
Node Id |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
PDN Connection Charging Id |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
PDP/PDN Type |
SIS- |
SIS- |
SIS- |
SIS- |
– |
|
SGi PtP Tunnelling Method |
– |
– |
SIS- |
– |
– |
|
SCS/AS Address |
– |
– |
SIS- |
– |
– |
|
PDP/PDN Address |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
PDP/PDN Address prefix length |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
Dynamic Address Flag |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
Dynamic Address Flag Extension |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
Serving Node Address |
SIS- |
– |
SIS- |
– |
SIS- |
|
Serving Node Type |
SIS- |
– |
SIS- |
– |
SIS- |
|
SGW Change |
S— |
S— |
– |
S— |
– |
|
P-GW Address |
SIS- |
– |
SIS- |
SIS- |
SIS- |
|
TDF Address |
– |
– |
– |
– |
SIS- |
|
SGW Address |
SIS- |
– |
– |
– |
– |
|
ePDG Address |
– |
SIS- |
– |
– |
– |
|
TWAG Address |
– |
– |
SIS- |
– |
– |
|
CG Address |
– |
– |
– |
– |
– |
|
IMSI MCC MNC |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
PGW MCC MNC |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
TDF MCC MNC |
– |
– |
– |
– |
SIS- |
|
NSAPI |
– |
– |
SIS- |
– |
– |
|
Called Station Id |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
Session Stop Indicator |
– |
– |
–S- |
– |
–S- |
|
Selection Mode |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
Charging Characteristics |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
Charging Characteristics Selection Mode |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
Serving Node MCC MNC |
SIS- |
– |
SIS- |
– |
SIS- |
|
MS Time Zone |
SIS- |
– |
SIS- |
– |
SIS- |
|
Charging Rule Base Name |
– |
– |
SIS- |
– |
– |
|
ADC Rule Base Name |
– |
– |
– |
– |
SIS- |
|
User Location Info |
SIS- |
– |
SIS- |
– |
SIS |
|
User Location Info Time |
SIS- |
– |
SIS- |
– |
– |
|
PSCell Information |
SIS- |
– |
– |
– |
– |
|
User CSG Information |
SIS- |
– |
SIS- |
– |
SIS- |
|
3GPP2 User Location Info |
SIS- |
– |
SIS- |
– |
SIS- |
|
TWAN User Location Information |
– |
– |
SIS- |
SIS- |
– |
|
UWAN User Location Information |
– |
SIS- |
SIS- |
– |
– |
|
Presence Reporting Area Information |
SIS- |
– |
SIS- |
– |
– |
|
RAT Type |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
Furnish Charging Information |
– |
– |
SIS- |
– |
– |
|
Offline Charging |
– |
– |
– |
– |
– |
|
QoS Information |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
Traffic data volumes |
-IS- |
-IS- |
– |
-IS- |
– |
|
Service data container |
– |
– |
-IS- |
– |
-IS- |
|
User Equipment Info |
– |
– |
– |
– |
S— |
|
Terminal-Information |
S— |
S— |
S— |
S— |
S— |
|
Start time |
S— |
S— |
S— |
S— |
S— |
|
Stop time |
–S- |
–S- |
–S- |
–S- |
–S- |
|
Change Condition |
-IS- |
-IS- |
-IS- |
-IS- |
-IS- |
|
Diagnostics |
–S- |
–S- |
–S- |
–S- |
–S- |
|
Enhanced Diagnostics |
–S- |
–S- |
–S- |
–S- |
– |
|
Low Priority Indicator |
S— |
– |
S— |
– |
– |
|
CN Operator Selection Entity |
SIS- |
– |
SIS- |
– |
– |
|
NBIFOM Support |
– |
– |
S— |
– |
– |
|
NBIFOM Mode |
– |
– |
S— |
– |
– |
|
CP CIoT EPS Optimisation Indicator |
SIS- |
– |
– |
– |
– |
|
UNI PDU CP Only Flag |
SIS- |
– |
SIS- |
– |
– |
|
Serving PLMN Rate Control |
SI– |
– |
SI– |
– |
– |
|
APN Rate Control |
– |
– |
SI– |
– |
– |
|
MO exception data counter |
SIS- |
– |
SIS- |
– |
– |
|
3GPP PS Data Off Status |
– |
– |
SIS- |
– |
– |
|
RAN Secondary RAT Usage Reports |
-IS- |
– |
-IS- |
– |
– |
Table 6.3.2.1a illustrates the basic structure of the supported fields in the Charging Data Request message for "SMS over MME Charging".
Table 6.3.2.1a: Supported fields in Charging Data Request message for "SMS over MME Charging"
Information Element |
Node Type |
MME |
---|---|---|
Supported Operation Types |
S/I/S/E |
|
Session Identifier |
—E |
|
Originator Host |
—E |
|
Originator Realm |
—E |
|
Destination Domain |
—E |
|
Operation Type |
—E |
|
Operation Number |
—E |
|
Operation Identifier |
—E |
|
User Name |
—E |
|
Destination Host |
—E |
|
Operation Interval |
—E |
|
Origination State |
—E |
|
Origination Timestamp |
—E |
|
Proxy Information |
—E |
|
Route Information |
—E |
|
Operation Token |
—E |
|
Service Information with PS, IMS, MMS and SMS Information |
||
Subscription Id |
—E |
|
Node Functionality |
—E |
|
Node Id |
—E |
|
MME Number for MT SMS |
—E |
|
MME Name |
—E |
|
MME Realm |
—E |
|
Serving Node Type |
—E |
|
SGSN Address |
—E |
|
Charging Characteristics |
—E |
|
Charging Characteristics Selection Mode |
—E |
|
3GPP User Location Info |
—E |
|
User Location Info Time |
—E |
|
RAT Type |
—E |
|
Terminal Information |
—E |
|
Recipient Address |
—E |
|
SMSC Address |
—E |
|
Originator Address |
—E |
|
Submission Time |
—E |
|
Message Id |
—E |
|
CN Operator Selection Entity |
—E |
Table 6.3.2.2 illustrates the basic structure of the supported fields in the Charging Data Response message for PS offline charging, and "SMS over MME Charging".
Table 6.3.2.2: Supported fields in Charging Data Response message
Information Element |
Node Type |
S-GW |
ePDG |
TWAG |
P-GW |
TDF |
---|---|---|---|---|---|---|
Supported Operation Types |
S/I/S/E |
S/I/S/E |
S/I/S/E |
S/I/S/E |
S/I/S/E |
|
Session Identifier |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
Operation Result |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
Originator Host |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
Originator Domain |
||||||
Operation Type |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
Operation Number |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
Operation Identifier |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
Operation Interval |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
Error Reporting Host |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
Origination State |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
Origination Timestamp |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
Proxy Information |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
Route Information |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
Service Information with PS Information |
||||||
Supported Features |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
6.3.3 Detailed message format for online charging
The following table specifies per Operation type the charging data that are sent P-GW and TDF network element for:
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 "-".
Note that not for all structured fields the individual field members are listed in the table. Detailed descriptions of the fields are provided in TS 32.299 [50].
Table 6.3.3.1 illustrates the basic structure of the supported fields in the Debit / Reserve Units Request for PS online charging.
Table 6.3.3.1: Supported fields in Debit / Reserve Units Request message
Information Element |
Node Type |
P-GW |
TDF |
---|---|---|---|
Supported Operation Types |
I/U/T/E |
I/U/T/E |
|
Session Identifier |
IUT- |
IUT- |
|
Originator Host |
IUT- |
IUT- |
|
Originator Domain |
IUT- |
IUT- |
|
Destination Domain |
IUT- |
IUT- |
|
Operation Identifier |
IUT- |
IUT- |
|
Operation Token |
IUT- |
IUT- |
|
Operation Type |
IUT- |
IUT- |
|
Operation Number |
IUT- |
IUT- |
|
Destination Host |
IUT- |
IUT- |
|
User Name |
IUT- |
IUT- |
|
Origination State |
IUT- |
IUT- |
|
Origination Timestamp |
IUT- |
IUT- |
|
Subscriber Identifier |
IUT- |
IUT- |
|
Termination Cause |
–T- |
–T- |
|
Requested Action |
IUT- |
IUT- |
|
Multiple Operation |
IU– |
IU– |
|
Multiple Unit Operation |
IUT- |
IUT- |
|
Subscriber Equipment Number |
IUT- |
IUT- |
|
Route Information |
IUT- |
IUT- |
|
Service Information |
IUT- |
IUT- |
|
Service Information with IMS and PS Information |
|||
Supported Features |
IUT- |
IUT- |
|
Node Functionality |
IUT- |
IUT- |
|
Charging Id |
IUT- |
– |
|
Node Id |
IUT- |
IUT- |
|
PDN Connection Charging Id |
IUT- |
IUT- |
|
PDP/PDN Type |
IUT- |
– |
|
SGi PtP Tunnelling Method |
IUT- |
– |
|
SCS/AS Address |
IUT- |
– |
|
PDP/PDN Address |
IUT- |
IUT- |
|
PDP/PDN Address prefix length |
IUT- |
IUT- |
|
Dynamic Address Flag |
IUT- |
IUT- |
|
Dynamic Address Flag Extension |
IUT- |
IUT- |
|
QoS Information |
IUT- |
IUT- |
|
Serving Node Address |
IUT- |
IUT- |
|
Serving Node Type |
IUT- |
IUT- |
|
SGW Change |
– |
– |
|
P-GW Address |
IUT- |
IUT- |
|
TDF Address |
– |
IUT- |
|
CG Address |
IUT- |
IUT- |
|
IMSI MCC MNC |
IUT- |
IUT- |
|
IMSI Unauthenticated Flag |
IUT- |
– |
|
PGW MCC MNC |
IUT- |
IUT- |
|
TDF MCC MNC |
– |
IUT- |
|
NSAPI |
IUT- |
– |
|
Called Station Id |
IUT- |
IUT- |
|
Session Stop Indicator |
–T- |
–T- |
|
Selection Mode |
IUT- |
IUT- |
|
Charging Characteristics |
IUT- |
IUT- |
|
Charging Characteristics Selection Mode |
IUT- |
IUT- |
|
Serving Node MCC MNC |
IUT- |
IUT- |
|
MS Time Zone |
IUT- |
IUT- |
|
Charging Rule Base Name |
IUT- |
– |
|
ADC Rule Base Name |
– |
IUT- |
|
User Location Info |
IUT- |
IUT- |
|
User Location Info Time |
IUT- |
– |
|
PSCell Information |
– |
– |
|
User CSG Information |
IUT- |
IUT- |
|
3GPP2 User Location Info |
IUT- |
IUT- |
|
TWAN User Location Information |
IUT- |
IUT- |
|
UWAN User Location Information |
IUT- |
– |
|
Presence Reporting Area Information |
UT- |
– |
|
RAT Type |
IUT- |
IUT- |
|
Furnish Charging Information |
– |
– |
|
Offline Charging |
IUT- |
IUT- |
|
PDP Context Type |
IUT- |
– |
|
Traffic data volumes |
– |
– |
|
Service data container |
– |
– |
|
User Equipment Info |
– |
– |
|
Terminal-Information |
– |
– |
|
Start time |
– |
– |
|
Stop time |
– |
– |
|
Change Condition |
– |
– |
|
Diagnostics |
–T- |
–T- |
|
Enhanced Diagnostics |
–T- |
– |
|
CN Operator Selection Entity |
– |
– |
|
NBIFOM Support |
I— |
– |
|
NBIFOM Mode |
I— |
– |
|
CP CIoT EPS Optimisation Indicator |
— |
– |
|
UNI PDU CP Only Flag |
IUT- |
– |
|
Serving PLMN Rate Control |
IU– |
– |
|
APN Rate Control |
IU– |
– |
|
MO exception data counter |
– |
– |
|
3GPP PS Data Off Status |
IUT- |
– |
|
Unused Quota Timer |
IU– |
– |
|
RAN Secondary RAT Usage Reports |
– |
– |
Table 6.3.3.2 illustrates the basic structure of the supported fields in the Debit / Reserve Units Response for PS online charging.
Table 6.3.3.2: Supported fields in Debit / Reserve Units Response Message
Information Element |
Node Type |
P-GW |
TDF |
---|---|---|---|
Supported Operation Types |
I/U/T/E |
I/U/T/E |
|
Session Identifier |
IUT- |
IUT- |
|
Operation Result |
IUT- |
IUT- |
|
Originator Host |
IUT- |
IUT- |
|
Originator Domain |
IUT- |
IUT- |
|
Operation Identifier |
IUT- |
IUT- |
|
Operation Type |
IUT- |
IUT- |
|
Operation Number |
IUT- |
IUT- |
|
Operation Failover |
IUT- |
IUT- |
|
Multiple Unit Operation |
IUT- |
IUT- |
|
Operation Failure Action |
IUT- |
IUT- |
|
Redirection Host |
IUT- |
IUT- |
|
Redirection Host Usage |
IUT- |
IUT- |
|
Redirection Cache Time |
IUT- |
IUT- |
|
Route Information |
IUT- |
IUT- |
|
Failed parameter |
IUT- |
IUT- |
|
Service Information |
IUT- |
IUT- |
|
Service Information with PS Information |
|||
Supported Features |
I— |
I— |
|
Furnish Charging Information |
IUT- |
IUT- |
|
Offline Charging |
I—- |
I—- |
|
Presence Reporting Area Information |
IU– |
– |
|
Unused Quota Timer |
IU– |
– |
6.4 Void
6.5 Bindings for EPC offline charging
This clause aims to describe the mapping between the Service Information fields, AVPs and CDR parameter for EPC offline charging.
Table 6.5.1 describes the mapping of the Information Element, AVP and CDR parameter of ePDG-CDR, TWAG-CDR, SGW-CDR, PGW-CDR and TDF-CDR in EPC offline charging.
Table 6.5.1: Bindings of CDR parameter, Information Element and AVP
CDR Parameter |
Information Element |
AVP |
---|---|---|
Retransmission |
– |
– |
Record Opening Time |
– |
– |
Duration |
– |
– |
Cause for Record Closing |
– |
– |
Record Sequence Number |
– |
– |
Local Record Sequence Number |
– |
– |
IMS Signalling Context |
– |
– |
CAMEL Information |
– |
– |
Record Extensions |
– |
– |
Service Information |
Service-Information |
|
Served IMSI |
Subscriber Identifier |
Subscription-Id |
Served MN NAI |
Subscriber Identifier |
Subscription-Id |
Served MSISDN |
Subscriber Identifier |
Subscription-Id |
IMS Information |
IMS-Information |
|
Record Type |
Node Functionality |
Node-Functionality |
PS Information |
PS-Information |
|
– |
Supported Features |
Supported-Features |
Charging Id |
Charging Id |
3GPP-Charging-Id |
Charging per IP-CAN Session Indicator |
Charging per IP-CAN Session Indicator |
Charging-Per-IP-CAN-Session-Indicator |
Node ID |
Node Id |
Node-ID |
PDN Connection Charging Id |
PDN Connection Charging Id |
PDN-Connection-Charging-ID |
PDP/PDN Type |
PDP/PDN Type |
3GPP-PDP-Type |
PDP/PDN Type extension |
PDP/PDN Type |
3GPP-PDP-Type |
SGi PtP Tunnelling Method |
SGi PtP Tunnelling Method |
SGi-PtP-Tunnelling-Method |
SCS/AS Address |
SCS/AS Address |
SCS-AS-Address |
Served PDP/PDN Address |
PDP/PDN Address |
PDP-Address |
Served PDP/PDN Address prefix length |
PDP/PDN Address prefix length |
PDP-Address-Prefix-Length |
Served PDP/PDN Address extension |
PDP/PDN Address |
PDP-Address |
Dynamic Address Flag |
Dynamic Address Flag |
Dynamic-Address-Flag |
Dynamic Address Flag extension |
Dynamic Address Flag Extension |
Dynamic-Address-Flag-Extension |
EPC QoS Information/Qos Information |
Negotiated QoS Profile |
Qos-Information |
Serving Node Address |
Serving Node Address |
SGSN-Address |
Serving node IPv6 Address |
Serving Node Address |
SGSN-Address |
Serving Node Type |
Serving Node Type |
Serving-Node-Type |
S-GW Change |
SGW Change |
SGW-Change |
PGW Address Used |
PGW Address |
GGSN-Address |
PGW IPv6 Address |
PGW Address |
GGSN-Address |
TDF Address Used |
TDF Address |
TDF-IP-Address |
TDF IPv6 Address |
TDF Address |
TDF-IP-Address |
S-GW Address used |
SGW Address |
SGW-Address |
S-GW Address IPv6 |
SGW Address |
SGW-Address |
ePDG Address Used |
ePDG Address |
ePDG-Address |
ePDG IPv6 Address |
ePDG Address |
ePDG-Address |
TWAG Address Used |
TWAG Address |
TWAG-Address |
TWAG IPv6 Address |
TWAG Address |
TWAG-Address |
– |
CG Address |
CG-Address |
– |
IMSI MCC MNC |
3GPP-IMSI-MCC-MNC |
IMSI Unauthenticated Flag |
IMSI Unauthenticated Flag |
IMSI-Unauthenticated-Flag |
PGW PLMN Identifier |
PGW MCC MNC |
3GPP-GGSN-MCC-MNC |
TDF PLMN Identifier |
TDF MCC MNC |
3GPP-GGSN-MCC-MNC |
– |
NSAPI |
3GPP-NSAPI |
Access Point Name Network Identifier |
Called Station Id |
Called-Station-Id |
– |
Session Stop Indicator |
3GPP-Session-Stop-Indicator |
APN Selection Mode |
Selection Mode |
3GPP-Selection-Mode |
Charging Characteristics |
Charging Characteristics |
3GPP-Charging-Characteristics |
Charging Characteristics Selection Mode |
Charging Characteristics Selection Mode |
Charging-Characteristics-Selection-Mode |
Serving node PLMN Identifier |
Serving Node MCC MNC |
3GPP-SGSN-MCC-MNC |
CN Operator Selection Entity |
CN Operator Selection Entity |
CN-Operator-Selection-Entity |
MS Time Zone |
MS Time Zone |
3GPP-MS-Time-Zone |
Last MS Time Zone |
MS Time Zone |
3GPP-MS-Time-Zone |
User Location Information |
User Location Info |
3GPP-User-Location-Info |
User Location Information Time |
User Location Info Time |
User-Location-Info-Time |
Last User Location Information |
User Location Info |
3GPP-User-Location-Info |
User CSG Information |
User CSG Information |
User-CSG-Information |
3GPP2 User Location information |
3GPP2 User Location Info |
3GPP2-BSID |
TWAN User Location Information |
TWAN User Location Information |
TWAN-User-Location-Info |
UWAN User Location Information |
UWAN User Location Information |
UWAN-User-Location-Info |
Presence Reporting Area Information |
Presence Reporting Area Information |
Presence-Reporting-Area-Information |
RAT Type |
RAT Type |
3GPP-RAT-Type |
PS Furnish Charging Information |
Furnish Charging Information |
PS-Furnish-Charging-Information |
– |
Offline Charging |
Offline-Charging |
– |
PDP Context Type |
PDP-Context-Type |
List of Traffic Data Volumes |
Traffic data volumes |
Traffic-Data-Volumes |
Data Volume Uplink |
– |
Accounting-Input-Octets |
Data Volume Downlink |
– |
Accounting-Output-Octets |
Change Condition |
Change Condition |
Change-Condition |
Change Time |
– |
Change-Time |
Access Availability Change Reason |
– |
Access-Availability-Change-Reason |
List of Service Data |
Service data container |
Service-Data-Container |
AF record information |
AF Correlation Information |
AF-Correlation-Information |
Charging Rule Base Name |
Charging Rule Base Name |
Charging-Rule-Base-Name |
ADC Rule Base Name |
ADC Rule Base Name |
ADC-Rule-Base-Name |
Rating Group |
Rating Group |
Rating-Group |
Service Identifier |
Service Identifier |
Service-Identifier |
Service Specific Info |
Service Specific Info |
Service-Specific-Info |
Report Time |
– |
Change-Time |
Service Condition Change |
– |
Change-Condition |
Result Code |
– |
Result-Code |
Time of First Usage |
– |
Time-First-Usage |
Time of Last Usage |
– |
Time–Last-Usage |
Time Usage |
– |
Time-Usage |
Traffic Steering Policy Identifier DL |
Traffic Steering Policy Identifier DL |
Traffic-Steering-Policy-Identifier-DL |
Traffic Steering Policy Identifier UL |
Traffic Steering Policy Identifier UL |
Traffic-Steering-Policy-Identifier-UL |
– |
User Equipment Info |
User-Equipment-Info |
Served IMEI |
Terminal Information |
Terminal-Information |
Served 3GPP2 MEID |
Terminal Information |
Terminal-Information |
Start Time |
Start Time |
Start-time |
Stop Time |
Stop Time |
Stop-time |
Cause for Record Closing |
Change Condition |
Change-Condition |
Diagnostics |
Diagnostics |
Diagnostics |
Enhanced Diagnostics |
Enhanced Diagnostics |
Enhanced-Diagnostics |
Low Priority Indicator |
Low Priority Indicator |
Low-Priority-Indicator |
NBIFOM Support |
NBIFOM Support |
NBIFOM-Support |
NBIFOM Mode |
NBIFOM Mode |
NBIFOM-Mode |
CP CIoT EPS Optimisation Indicator |
CP CIoT EPS Optimisation indicator |
CP-CIoT-EPS-Optimisation-Indicator |
UNI PDU CP Only Flag |
UNI PDU CP Only Flag |
UNI-PDU-CP-Only-Flag |
Serving PLMN Rate Control |
Serving PLMN Rate Control |
Serving-PLMN-Rate-Control |
MO exception data counter |
MO exception data counter |
RRC-Cause-Counter |
APN Rate Control |
APN Rate Control |
APN-Rate-Control |
VoLTE Information |
VoLTE Information |
VoLTE-Information |
3GPP PS Data Off Status |
3GPP PS Data Off Status |
3GPP-PS-Data-Off-Status |
List of RAN Secondary RAT Usage Reports |
RAN Secondary RAT Usage Reports |
RAN-Secondary-RAT-Usage Report |
Table 6.5.2 describes the mapping of the Information Element, AVP and the CDR parameter of S-SMO/S-SMT-CDR in EPC offline charging for SMS.
Table 6.5.2: Bindings of S-SMO/S-SMT-CDR parameter, Information Element and AVP
CDR Parameter |
Information Element |
AVP |
Retransmission |
– |
– |
Local Record Sequence Number |
– |
– |
CAMEL Information |
– |
– |
Record Extensions |
– |
– |
Service Information |
Service-Information |
|
Served IMSI |
Subscriber Identifier |
Subscription-Id |
Served MSISDN |
Subscriber Identifier |
Subscription-Id |
IMS Information |
IMS-Information |
|
Record Type |
Node Functionality |
Node-Functionality |
PS Information |
PS-Information |
|
Recording Entity |
MME Number for MT SMS |
MME-Number-for-MT-SMS |
MME Name |
MME Name |
MME-Name |
MME Realm |
MME Realm |
MME-Realm |
SMS Information |
SMS-Information |
|
Destination Number |
Recipient-Address |
Recipient-Address |
Service Centre |
SMSC-Address |
SMSC-Address |
MMS Information |
MMS-Information |
|
Originating Address |
Originator Address |
Originator-Address |
Event Time Stamp |
Submission-Time |
Submission-Time |
Message Reference |
Message Id |
MessageId |
NOTE: The whole set of ePDG-/TWAG-/MME-/SGW-/PGW-/TDF-CDR parameters is described in the TS 32.298 [51].
Annex A (normative):
Charging characteristics