5.1.4 Service level CDR parameters

32.2983GPPCharging Data Record (CDR) parameter descriptionCharging managementRelease 18Telecommunication managementTS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

5.1.4.1 MMS CDR parameters

5.1.4.1.0 Introduction

This clause contains the description of each field of the MMS CDRs specified in TS 32.270 [30].

5.1.4.1.1 3GPP MMS Version

The MMS version of the originator MMS Relay/Server as defined in TS 23.140 [206].

5.1.4.1.2 Access Correlation

If the parameter is provided and is not an empty string, it is a unique identifier delivered by the used access network domain of the originator or recipient MMS User Agent. It may be used for correlation of the MMS CDRs with the corresponding MSC server CDRs in CS domain or GSN CDRs in PS domain. It is an empty string if the parameter is not delivered by the access network.

5.1.4.1.3 Acknowledgement Request

This Boolean value indicates whether (value TRUE) or not (value FALSE) a response has been requested in a request at the MM4 reference point.

5.1.4.1.4 Attributes List

This field contains a list of information element names that are used in the MM1_mmbox_view.REQ, which request corresponding information elements from the MMs to be conveyed in the MM1_mmbox_view.RES. The list of known information element names are those currently defined for the MM1_retrieve.RES and MM1_notification.REQ. In the absence of the Attributes list information element, the MMS Relay/Server shall, by default and if available, select these information elements from each viewed MM: Message ID, Date and time, Sender address, Subject, Message size, MM State, and MM Flags.

5.1.4.1.5 Billing Information

This field contains transparent charging information provided by the MSCF to the MMS R/S for use by the billing system to properly bill the user for the service being supplied as defined in TS 29.140 [218]. Only the format, but not the content of the "Billing information" field is defined.

5.1.4.1.6 Charge Information

This field consists of two parts, the charged party and the charge type.

The Charged Party is an indication on which party is expected to be charged for an MM e.g. the sending, receiving, both parties or neither. This indicator is only applicable to MM7 CDRs (for VASP-originated MMs). It may be provided by the VASP when submitting an MM.

The Charge Type indicates the type of subscription (i.e. postpaid or prepaid). This indicator is derived from the subscription parameters and only applicable to MM1 CDRs.

The Charged Parties are as follows:

– Sender: This indicates the sending party is expected to be charged (‘normal’ charging model);

– Recipient: This indicates the receiving party is expected to be charged (‘reverse’ charging model). This model implies there is a commercial agreement between the Recipient and the VASP;

– Both: This indicates both the sending and the receiving parties are expected to be charged (‘shared’ charging model);

– Neither: This indicates neither the sending nor the receiving parties are expected to be charged (‘free of charge’ charging model).

The Charge types are as follows:

– Postpaid;

– Prepaid.

5.1.4.1.7 Content Type

The Content Type of the MM as defined in TS 23.140 [206].

5.1.4.1.8 Delivery Report Requested

This is an indication of type Boolean whether (value TRUE) or not (value FALSE) the originator/forwarding MMS User Agent has requested a delivery report in the MM1_submit.REQ/MM1_forward.REQ.

5.1.4.1.9 Duration of Transmission

This field contains the relevant time in seconds. The Duration of Transmission is the time from the beginning to the end of the MM transfer between the MMS User Agent and the MMS Relay/Server; e.g. for streaming purposes.

Note that the CDRs purposely do not contain any information about the duration of storage on the MMS Relay/Server. If such information is required it can be calculated by post-processing systems from the CDR timestamps. For instance, the total duration of storage on the originator MMS Relay/Server could be calculated by taking the difference between the ‘Record Time Stamp’ of the O1S-CDR and the ‘Record Time Stamp’ of the OMD-CDR.

5.1.4.1.10 Earliest Time of Delivery

This field contains either the earliest time to deliver message or the number of seconds to wait before delivering the message.

5.1.4.1.11 Forward Counter

A Counter indicating the number of times the particular MM was forwarded as defined in TS 23.140 [206].

5.1.4.1.12 Forwarding Address

This field contains a forwarding MMS User Agent address. The MMS supports the use of E-Mail addresses (RFC 822 [400]), MSISDN (E.164[308]) or IP addresses.

5.1.4.1.13 Forwarding MMS Relay/Server Address

This field contains one or more addresses of the forwarding MMS Relay/Server. The address is either an IP address or a domain name.

5.1.4.1.14 Limit

This field contains a number that may be provided in the MM1_mmbox_view.REQ to specify a limit for the number of MMs the information elements to which shall be returned in the MM1_mmbox_view.RES.

5.1.4.1.15 Linked ID

This field identifies a correspondence to a previous valid message delivered to the VASP

5.1.4.1.16 Local Record Sequence Number

This field includes a unique record number created by this node. The number is allocated sequentially including all CDR types. The number is unique within one node, which is identified either by field Node ID or by record-dependent MMS Relay/Server.

The field can be used e.g. to identify missing records in post processing system.

5.1.4.1.17 Managing Address

This field contains the managing MMS User Agent address i.e. the MMS User Agent that sends and receives transactions related to the MMBox management . The MMS supports the use of E-Mail addresses (RFC 822) [400], MSISDN (E.164[308]) or IP address.

5.1.4.1.18 Message Class

A class of messages such as personal, advertisement, information service etc. For more information see TS 23.140 [206].

5.1.4.1.19 Message Distribution Indicator

This is an indication of type Boolean whether (value TRUE) or not (value FALSE) the VASP has indicated the content of the MM is intended for redistribution.

5.1.4.1.20 Message ID

This field specifies the MM Message ID of the MM as defined in TS 23.140 [206]. The concrete syntax of this MM Message ID is given by the body of the field introduced by the string "X-Mms-Message-ID:" in the concrete syntax of the message MM4_Forward.REQ. All CDRs pertaining to the same MM shall employ the same value of this parameter, i.e. the value initially assigned by the originator MMS Relay/Server upon submission of the MM by the Originator MMS User Agent.

5.1.4.1.21 Message Reference

A reference as specified in TS 23.140 [206], e.g. URI, for the MM that can be used for retrieving the MM from the recipient MMS Relay/Server.

5.1.4.1.22 Message selection

Messages which are to be viewed may be selected by a list of Message References or by a selection based on MM State and/or MM Flags keywords.

5.1.4.1.23 Message Size

This field contains the number of octets of the MM that is calculated as specified in TS 23.140 [206].

5.1.4.1.24 MMBox Storage Information

This field includes following storage information elements for the MMBox containing the MM State, MM Flags, Store Status, Store Status Text and Stored Message Reference.

– MM State;

This field contains the state of the MM.

– MM Flags:

This field contains the keyword flags of the MM.

– Store Status:

This field contains an appropriate status value of the stored MM, e.g. stored, error-transient-mailbox-full,…

– Store Status Text;

This field includes a more detailed technical description of the store status at the point in time when the CDR is generated.

– Stored Message Reference;

A reference of the newly stored MM.

5.1.4.1.25 MM component list

The MM component list is a set of subject and media components from type of media formats including the size of all elements in octets. For a complete description of media formats that may be supported by MMS, refer to IANA [xx].

5.1.4.1.26 MM Date and Time

The date and time field contains the time stamp relevant for the handling of the MM by the recipient MMS Relay/ Server (read, deleted without being read, etc.). The time-stamp includes at a minimum: date, hour, minute and second.

5.1.4.1.27 MM Listing

This field contains a list of information elements from the MMs returned within the MM1_mmbox_view.RES. The listing shall consist of the following information elements, separately grouped for each MM returned in the list:

– Message reference: a unique reference to an MM;

– Information elements corresponding to those requested in the Message Selection information element on the MM1_mmbox_view.REQ.

5.1.4.1.28 MM Status Code

This field contains an appropriate status value of the delivered MM (e.g. retrieved, rejected, etc.).

5.1.4.1.28A MS Time Zone

This field contains the ‘Time Zone’ IE provided for the MMS User Agent as specified in TS 29.060 [215].

5.1.4.1.29 MSCF Information

This is a grouped field comprising several the following sub-fields associated with the invocation of the MSCF for advanced addressing:

– Billing Information;

– Routeing address List.

These field elements are described in the appropriate subclause.

5.1.4.1.30 Originator Address

This field contains an originator MMS User Agent address. The MMS supports the use of E-Mail addresses (RFC 822 [400]) or MSISDN (E.164 [308]).

5.1.4.1.31 Originator MMS Relay/Server Address

This field contains an address of the originator MMS Relay/Server. This address is composed of a mandatory IP address and/or an optional domain name.

5.1.4.1.32 Priority

The priority (importance) of the message, see TS 23.140 [206].

5.1.4.1.33 Quotas

The quotas of the MMBox in messages and/or octets identified with Messages or Octets

5.1.4.1.34 Quotas requested

This is an indication that the Managing User Agent has requested the current message and/or size quotas.

5.1.4.1.35 Read Reply Requested

A Boolean value indicating whether the originator MMS User Agent has requested a read-reply report (value TRUE) or not (value FALSE).

5.1.4.1.36 Read Status

See TS 23.140 [206]: Status of the MM, e.g. Read, Deleted without being read.

5.1.4.1.37 Recipient Address

This field contains a recipient MMS User Agent address. The MMS supports the use of E-Mail addresses (RFC 822 [400]), MSISDN (E.164 [308]) or Service provider specific addresses (short code).

5.1.4.1.38 Recipient MMS Relay/Server Address

This field contains an address of the recipient MMS Relay/Server. This address is composed of a mandatory IP address and/or an optional domain name.

5.1.4.1.39 Recipients Address List

This field contains a list of recipient MMS User Agent addresses.

5.1.4.1.40 Record Extensions

The field enables network operators and/or manufacturers to add their own extensions to the standard record definitions.

5.1.4.1.41 Record Time Stamp

This field indicates the date and time when the CDR was produced.

5.1.4.1.42 Record Type

The field identifies the type of the record, see TS 32.250 [10].

5.1.4.1.43 Reply Charging

This field indicates whether the originator of the MM is willing to take over the charge for the sending of a reply-MM to their submitted MM from the recipient(s). In this case the originator MMS Relay/Server marks the MM as no charge (reply-charged).

In the Originator MM1 Submission CDR (O1S-CDR) this parameter indicates whether the originator MMS User Agent has requested reply-charging (value TRUE) or not (value FALSE).

In the Recipient MM1 Notification Request record (R1NRq -CDR) it indicates whether a reply to this particular original MM is free of charge (value TRUE) or not (value FALSE).

In the MM7 Submission CDR (7S-CDR) this parameter indicates whether the originator MMS VASP has requested reply-charging (value TRUE) or not (value FALSE).

5.1.4.1.44 Reply Charging ID

This field is present in the CDR only if the MM is a reply-MM to an original MM. The Reply Charging ID is the Message ID of the original MM.

5.1.4.1.45 Reply Charging Size

In the Originator MM1 Submission CDR (O1S-CDR), in case of reply-charging, this field indicates the maximum size for reply-MM(s) granted to the recipient(s) as specified by the originator MMS User Agent.

In the Recipient MM1 Notification Request CDR (R1NRq-CDR), in case of reply-charging, this field indicates the maximum size of a reply-MM granted to the recipient as specified in the MM1_notification.REQ.

In the MM7 Submission CDR (7S-CDR), in case of reply-charging, this field indicates the maximum size for reply-MM(s) granted to the recipient(s) as specified by the originator MMS VASP.

5.1.4.1.46 Reply Deadline

In the Originator MM1 Submission CDR (O1S-CDR), in case of reply-charging, this field indicates the latest time of submission of replies granted to the recipient(s) as specified by the originator MMS User Agent.

In the Recipient MM1 Notification Request CDR (R1NRq-CDR), in case of reply-charging, this field indicates the latest time of submission of a reply granted to the recipient as specified in the MM1_notification.REQ.

In the MM7 Submission CDR (7S-CDR), in case of reply-charging, this field indicates the latest time of submission of replies granted to the recipient(s) as specified by the originator MMS VASP.

5.1.4.1.47 Report allowed

A Boolean value indicating, if present whether sending of a delivery report is permitted (value TRUE) or not (value FALSE).

5.1.4.1.48 Request Status code

The status of the MM as reflected in the corresponding MM4 message (e.g. error service denied, error network problem, error unsupported message, etc.). For further details see TS 23.140 [206].

5.1.4.1.49 Routeing Address

The field contains a recipient address for routeing of a multimedia message. For a complete description of the routeing address, refer to TS 29.140 [218].

5.1.4.1.50 Routeing Address List

This field contains a list of routeing addresses.

5.1.4.1.51 Sender Address

The address of the MMS User Agent as used in the MM1_notification_REQ/MM1_retrieve.RES. This parameter is present in the CDR even if address hiding was requested, resulting in the sender address is not being included in the above messages.

5.1.4.1.52 Sender Visibility

This Boolean value indicates whether the originator MMS User Agent has requested her address to be hidden from the recipient (value TRUE) or not (value FALSE).

5.1.4.1.53 Service code

This field contains charging information provided by the VASP to the MMS R/S for use by the billing system to properly bill the user for the service being supplied. The usage of the "service code" is, in the release, open to any usage envisioned by the operators, service providers or MMS Relay/Server vendors. In this release only the format, but not the content of the "service code" field is defined.

5.1.4.1.54 Start

This field contains a number that may be used in the MM1_mmbox_view.REQ to index the first MM to be viewed, relative to the selected set of MMs, allowing partial views to be requested

5.1.4.1.55 Status Text

This field includes a more detailed technical status of the message at the point in time when the CDR is generated..

5.1.4.1.56 Submission Time

The submission time field contains the time stamps relevant for the submission of the MM. The time-stamp includes a minimum of date, hour, minute and second.

5.1.4.1.57 Time of Expiry

This field contains the desired date or the number of seconds to expiry of the MM, if specified by the originator MMS User Agent.

5.1.4.1.58 Totals

The total number of messages and/or octets for the MMBox, identified with Messages or Octets.

5.1.4.1.59 Totals requested

This is an indication that the Managing User Agent has requested the current total number of messages and/or size contained by the MMBox.

5.1.4.1.60 Upload Time

The upload time field contains the time stamps relevant for the upload of the MM. The time-stamp includes a minimum of date, hour, minute and second.

5.1.4.1.61 VAS ID

This field specifies the identification of the VASP as defined in TS 23.140 [206].

5.1.4.1.62 VASP ID

This field specifies the identification of the originating application as defined in TS 23.140 [206].

5.1.4.2 LCS CDR parameters

5.1.4.2.0 Introduction

This clause contains the description of each field of the LCS CDRs specified in TS 32.271 [31].

5.1.4.2.1 Home GMLC Identity

This field contains the IP address of the Home GMLC (H-GMLC) involved in the location request.

5.1.4.2.2 LCS Client Identity

This field contains further information on the LCS Client identity as defined in TS 29.002 [214].

5.1.4.2.3 LCS Client Type

This field contains the type of the LCS Client as defined in TS 29.002 [214].

5.1.4.2.4 LCS Priority

This parameter gives the priority of the location request as defined in TS 49.031 [227].

5.1.4.2.5 Location Estimate

The Location Estimate field is providing an estimate of a geographic location of a target MS according to TS 29.002 [214].

5.1.4.2.6 Location Type

This field contains the type of the location as defined in TS 29.002 [214].

5.1.4.2.7 Positioning Data

This information element is providing positioning data associated with a successful or unsuccessful location attempt for a target MS according TS 49.031 [227].

5.1.4.2.8 Provider Error

This parameter is used to indicate a protocol related type of error as defined in TS 29.002 [214].

5.1.4.2.9 Requesting GMLC Identity

This field contains the IP address of the Requesting GMLC (R-GMLC) involved in the location request.

5.1.4.2.10 Result code

This field indicates the result of the request or individual positioning as defined in OMA Mobile Location Protocol [311].

5.1.4.2.11 Target IMSI

This field contains the International Mobile Subscriber Identity (IMSI) of the targeted party. The term "targeted" party is used to describe the mobile subscriber involved in the transaction recorded e.g. the subscriber whose location is requested in case of mobile terminated location request.

The structure of the IMSI is defined in TS 23.003 [200].

5.1.4.2.12 Target MSISDN

This field contains the Mobile Station ISDN Number (MSISDN) of the targeted party. The term "targeted" party is used to describe the mobile subscriber involved in the transaction recorded e.g. the subscriber whose location is requested in case of mobile terminated location request.

In case of multi-numbering the MSISDN stored in a LCS CDR will be the primary MSISDN of the requesting party.

The structure of the MSISDN is defined in TS 23.003 [200].

5.1.4.2.13 User Error

This parameter is sent by the responder when the location request has failed or cannot proceed and if present, takes one of the following values defined in TS 29.002 [214]:

– System Failure;

– Data Missing;

– Unexpected Data Value;

– Facility Not Supported;

– Unidentified Subscriber;

– Illegal Subscriber;

– Illegal Equipment;

– Absent Subscriber (diagnostic information may also be provided);

– Unauthorised requesting network;

– Unauthorised LCS Client with detailed reason;

– Position method failure with detailed reason.

5.1.4.2.14 Visited GMLC Identity

This field contains the IP address of the Visited GMLC (V-GMLC) involved in the location request.

5.1.4.3 PoC CDR parameters

5.1.4.3.0 Introduction

This clause contains the description of each field of the PoC CDRs specified in TS 32.272 [32].

5.1.4.3.1 Called Party Address

Called Party Address is of type UTF8String. It indicates address (Public User ID, SIP URL, E.164, etc.) of the participants involved in the PoC session.

5.1.4.3.2 Charged Party

This field indicates the party accepting the charge for the session, whether participating in the session or not. The contents are obtained from the Charged-Party AVP in offline charging.

5.1.4.3.3 List of Talk Burst Exchange

This list contains a number of containers consisting of the following fields:

Change Condition

Change Time

Number of participants

Number of received talk bursts

Number of talk bursts

Received talk burst volume

Received talk bursts time

Talk burst volume

Talk bursts time

Number of talk bursts and Number of received talk bursts indicate the number of talk bursts sent and received respectively by the charged party (for the participating PoC functions) or for the whole session (for the controlling PoC function).

Talk burst volume and Received talk burst volume indicate the total data volume for talk bursts sent and received respectively by the charged party (for the participating PoC functions) or for the whole session (for the controlling PoC function).

Talk burst Time and Received talk burst time indicate the total duration of talk bursts sent and received respectively by the charged party (for the participating PoC functions) or for the whole session (for the controlling PoC function).

Change Time is a time stamp, which defines the moment when the container is closed or the CDR is closed.

Change Condition indicates the reason for closing the container and the addition of a new container.

Number of participants indicates the number of attached participants involved in the talk burst exchange within a container.

5.1.4.3.4 Number of participants

For PoC, this field indicates the number of active participants within the PoC session. For MMtel Charging, this field indicates the number of active participants attached in the MMTel conference.

5.1.4.3.5 Participant Access Priority

This field indicates the access priority for each participant involved in the PoC session.

5.1.4.3.6 Participants involved

This field indicates the participants involved in the PoC session.

The field is of type grouped. It contains the participant address (Called party address), the participant access priority and User Participating Type.

5.1.4.3.7 PoC controlling address

This field contains the address of the server performing the controlling PoC function.

5.1.4.3.8 PoC Event Type

This field contains the PoC session unrelated charging event type.

5.1.4.3.9 PoC group name

This field indicates the name of a group used for the PoC session.

5.1.4.3.10 PoC session id

This field uniquely identifies the overall PoC session.

5.1.4.3.11 PoC session initiation type

The field is of type Enumerated. It identifies the type of the PoC session initiation.

The identifier can be one of the following:

Pre-established
On-demand

5.1.4.3.12 PoC session type

The field identifies the type of the PoC session.

5.1.4.3.13 User location info

This field contains any available location information for the charged party. The field is coded as per the 3GPP-User-Location-Info RADIUS VSA defined in TS 29.061 [216].

5.1.4.3.14 User Participating Type

Indicates the User Participating Type participating in the PoC session i.e. Normal, NW PoC Box, UE PoC Box.

5.1.4.4 MBMS CDR parameters

5.1.4.4.0 Introduction

This clause contains the description of each field of the MBMS CDRs specified in TS 32.273 [33].

5.1.4.4.1 CN IP Multicast Distribution

This field is used to indicate if IP multicast distribution to UTRAN is used for the MBMS user plane data.

5.1.4.4.2 MBMS 2G 3G Indicator

The MBMS 2G 3G Indicator is used to indicate the radio access type that can receive the MBMS bearer service.

5.1.4.4.2A MBMS Data Transfer Start

The field contains the absolute time stamp of the data delivery start. The value indicates the time in seconds for the radio resources set up relative to 00:00:00 on 1 January 1900 (calculated as continuous time without leap seconds and traceable to a common time reference) where binary encoding of the integer part is in the first 32 bits and binary encoding of the fraction part in the last 32 bits. The fraction part is expressed with a granularity of 1/2**32 second.

This field is only valid for E-UTRAN access type.

5.1.4.4.2B MBMS Data Transfer Stop

The field contains the absolute time stamp of the data delivery stop. The value indicates the time in seconds for the release of radio resources relative to 00:00:00 on 1 January 1900 (calculated as continuous time without leap seconds and traceable to a common time reference) where binary encoding of the integer part is in the first 32 bits and binary encoding of the fraction part in the last 32 bits. The fraction part is expressed with a granularity of 1/2**32 second.

This field is only valid for E-UTRAN access type.

5.1.4.4.3 MBMS GW Address

This parameter holds the IP-address of the MBMS GW that generated the Charging Id when MBMS GW is stand-alone.

5.1.4.4.4 MBMS Service Area

The field indicates the area over which the MBMS bearer service has to be distributed.

5.1.4.4.5 MBMS Service Type

The field is used to indicate the type of MBMS bearer service: multicast or broadcast.

5.1.4.4.6 MBMS Session Identity

This field together with TMGI identifies a transmission of a specific MBMS session.

5.1.4.4.7 Required MBMS Bearer Capabilities

The field contains the minimum bearer capabilities the UE needs to support.

5.1.4.4.8 TMGI

The field contains the Temporary Mobile Group Identity allocated to a particular MBMS bearer service. TMGI use and structure is specified in TS 23.003 [200].

5.1.4.5 MMTel CDR parameters

5.1.4.5.0 Introduction

This subclause contains the description of each of the CDR fields needed to support the charging of MMTel services as specified in TS 32.275 [35].

5.1.4.5.1 Associated Party Address

This field holds the address (SIP URI or Tel URI) of the user, for MMTel supplementary service this field is used for : the "forwarding party" for CDIV, the "transferor" for ECT, the "Pilot Identity" for FA and the "Initiator party" for 3PTY, as specified in TS 32.275 [35]. The content is obtained from the Associated-Party-Address AVP.

5.1.4.5.2 List of Supplementary services

This list includes several MMTel Supplementary services. Each Supplementary Service may contain the following fields as specified in TS 32.275 [35] :

– Service Type;

– Service Mode;

– Number Of Diversions;

– Associated Party Address;

– Service ID;

– Change Time;

– Number Of Participants;

– Participant Action Type;

– AoC information.

Service Type is defined in clause 5.1.4.5.6

Service Mode is defined in clause 5.1.4.5.5

Number Of Diversions is defined in clause 5.1.4.5.3

Associated Party Address is defined in clause 5.1.4.5.1

Service ID is an identifier of the conference.

Change Time is a time stamp, which defines the moment when the conference participant has an action (e.g. creating the conference, joining in the conference, being invited into the conference or quitting the conference) triggering the Accounting Request message to CDF in MMTel Charging.

Number Of Participants indicates the number of attached participants involved in the conference.

Participant Action Type indicates the participant’s action type during the conference. It is just for Billing Domain’s information in each CDR, e.g. creating the conference, joining in the conference, being invited into the conference and quitting the conference. CUG Information indicates the "CUG interlock code" used during the "Closed User Group" communication.

AoC information is defined in clause 5.1.3.1.3A.

5.1.4.5.3 Number Of Diversions

This field identifies the number of diversions related to a CDIV service as defined in TS 32.275 [35] and TS 24.604 [211]. When counting the number of diversions, all types of diversion are included.

5.1.4.5.4 Participant Action Type

This field indicates the participant’s action type during the conference. The content is obtained from the Participants-Action-Type AVP in TS 32.299 [50].

5.1.4.5.5 Service Mode

This field of Supplementary service indicates the mode for MMTel supplementary services (e.g. CDIV, CB and ECT). The content is obtained from the Service-Mode AVP and described in TS 32.299 [50].

Service Mode values  1024 are reserved for specific Network/Manufacturer variants.

5.1.4.5.6 Service Type

This field identifies the MMTel supplementary service type as defined in TS 32.275 [35]. . The content is obtained from the MMTel-SService-Type AVP and described in TS 32.299 [50].

Service Type values  1024 are reserved for specific Network/Manufacturer variants

5.1.4.5.7 Void

5.1.4.6 SMS CDR parameters

5.1.4.6.0 Introduction

This clause contains the description of each field of the SMS CDRs specified in TS 32.274 [34].

5.1.4.6.1 Event Timestamp

This field contains the timestamp of the event that triggered the generation of charging information for the SMS transaction.

5.1.4.6.0A Carrier Select Routing

This field contains information on carrier select routing, received by S-CSCF during ENUM/DNS processes.

5.1.4.6.1A External Identifier

This field contains the External Identifier of the UE, which identifies a subscription associated to an IMSI, as specified in TS 23.003 [200].

5.1.4.6.2 Local Record Sequence Number

This field includes a unique record number created by this node. The number is allocated sequentially The number is allocated sequentially including all CDR types. The number is unique within the CDF.

The field can be used e.g. to identify missing records in post processing system.

5.1.4.6.3 Message Class

This field contains a class of messages such as personal, advertisement, information service. For more information see TS 23.140 [206].

5.1.4.6.4 Message Reference

This field contains the identity used to identify a Short Message in the SMS node associated with entity that submitted it, and corresponds to the TP-Message-Reference (TP-MR) as defined in TS 23.040 [201].

5.1.4.6.5 Message Size

This field contains the length of the user data part of the Short Message, corresponding to the TP-User-Data-Length (TP-UDL) as defined in TS 23.040 [201].

5.1.4.6.6 MTC IWF Address

This field contains the MTC IWF address.

5.1.4.6.6A Number Portability Routing

This field contains information on number portability routing, received by S-CSCF during ENUM/DNS processes.

5.1.4.6.7 Originator IMSI

This field contains IMSI of the originator of the Short Message. The structure of the IMSI is defined in TS 23.003 [200].

5.1.4.6.8 Originator Info

This field contains a set of information on the originator of the Short Message, and includes following elements:

– Originator IMSI

– Originator MSISDN

– Originator Other Address

– Originator SCCP Address

– Originator Received Address

– SM Originator Interface

– SM Originator Protocol Id

These fields are described in the appropriate subclause.

5.1.4.6.9 Originator MSISDN

This field contains MSISDN (E.164 number [308]) of the originator of the Short Message.

5.1.4.6.10 Originator Other Address

This field contains the addressee of an originator of the Short Message other than IMSI and MSISDN: e.g. short code, email.

5.1.4.6.11 Originator Received Address

This field contains the original address of the originator of the Short Message, as received by the SMS node.

5.1.4.6.12 Originator SCCP Address

This field contains the SCCP calling address used to receive the Short Message at the SMS node.

5.1.4.6.12A PDP Address

This field contains the UE IP address used by the subscriber for the SMS transaction.

5.1.4.6.13 RAT Type

This field contains the Radio Access Technology (RAT) type used for the SMS transaction, as provided to the SMS Node, and specified in TS 29.061 [216] 3GPP RAT Type.

5.1.4.6.14 Recipient IMSI

This field contains IMSI of a Recipient of the Short Message. The structure of the IMSI is defined in TS 23.003 [200].

5.1.4.6.15 Recipient Info

This field contains a set of information on a Recipient of the Short Message, and includes following elements:

– Recipient IMSI

– Recipient MSISDN

– Recipient Other Address

– Recipient Received Address

– Recipient SCCP Address

– SM Destination Interface

– SM Recipient Protocol Id

These fields are described in the appropriate subclause.

5.1.4.6.16 Recipient MSISDN

This field contains MSISDN (E.164 number [308]) of a Recipient of the Short Message.

5.1.4.6.17 Recipient Other Address

This field contains the addressee of a Recipient of the Short Message other than IMSI and MSISDN: e.g. short code, email….

5.1.4.6.18 Recipient Received Address

This field contains the original address of the originator of the Short Message, as received by the SMS node.

5.1.4.6.19 Recipient SCCP Address

This field contains the SCCP called address used by the SMS node to onward deliver the Short Message.

5.1.4.6.20 Record Type

The field identifies the type of the record, see TS 32.250 [10].

5.1.4.6.21 Record Extensions

The field enables network operators and/or manufacturers to add their own extensions to the standard record definitions.

5.1.4.6.22 Served IMEI

This fields contains the international mobile equipment identity (IMEI) or IMEISV of the equipment served. The term "served" equipment is used to describe the UE involved in the SMS transaction recorded.

The structure of the IMEI, IMEISV is specified in TS 23.003 [200].

5.1.4.6.22A Session ID

This fields contains the SIP CALL ID of the SIP session, as defined in the Session Initiation Protocol RFC 3261 [401].

5.1.4.6.23 SM Data Coding Scheme

This field contains the data coding scheme used within the Short Message and corresponds to TP-DCS header.

5.1.4.6.24 SM Delivery Report Requested

This field contains an indication whether a delivery report is requested by the Short Message originator.

5.1.4.6.25 SM Destination Interface

This field contains the information describing the interface on which the Short Message is to be delivered by the SMS node.

5.1.4.6.26 SM Device Trigger Indicator

This field contains indication whether the Short Message submission/delivery to/from SMS-SC is related to Device Trigger, and which Device trigger action is requested: request, replace or recall.

5.1.4.6.27 SM Device Trigger information

This field contains the set of information related to SMS submission to SMS-SC for Device Trigger, and includes following elements:

– MTC IWF Address

– SM DT Reference Number

– SM Serving Node

– SM DT Validity Period

– SM DT Priority Indication

– SMS Application Port ID

These fields are described in the appropriate subclause.

5.1.4.6.28 SM Discharge Time

This field contains the time associated with the event being reported in the Short Message Status field as defined in TS 23.040 [201]. This information is only applicable to delivery report charging procedures

5.1.4.6.29 SM DT Priority Indication

This field holds the priority of the device trigger request received via T4 reference point, as specified in TS 29.337 [231].

5.1.4.6.30 SM DT Reference Number

This field contains the Reference Number related to the device trigger request received via T4 reference point, as specified in TS 29.337 [231].

5.1.4.6.31 SM DT Validity Period

This field contains the validity period of the device trigger request received via T4 reference point, as specified in TS 29.337 [231].

5.1.4.6.32 SM Message Type

This field contains the message type that triggered the generation of charging information: submission, delivery report, SM Service Request, T4 Device Trigger, or SM Device Trigger, or MO-SMS T4 submission.

5.1.4.6.33 SM Originator Interface

This field contains the information describing the interface on which the Short Message was received by the SMS node

5.1.4.6.34 SM Originator Protocol Id

This field contains the TP-PROTOCOL-ID (TP-PID) as defined in TS 23.040 [201] describing the protocol used for the Short Message by originator.

5.1.4.6.35 SM Priority

This field contains any priority information associated with a Short Message, as defined in TS 23.040 [201].

5.1.4.6.36 SM Recipient Protocol Id

This field contains the TP-PROTOCOL-ID (TP-PID) as defined in TS 23.040 [201], describing the protocol used for the Short Message to the recipient.

5.1.4.6.37 SM Reply Path Requested

This field contains an indication of whether a reply Short Message to an original Short Message shall follow the same path and corresponds to the TP-Reply-Path (TP-RP) flag.

5.1.4.6.38 SMS Application Port ID

This field holds the Application Port ID of triggering application for the device trigger request received via T4 reference point, as specified in TS 29.337 [231] , or the Application port ID associated with the UE on MO delivery to the SCS.

5.1.4.6.39 SM Sequence Number

This field contains the sequence number of the SMS within the concatenated short message when part of concatenated short message.

5.1.4.6.40 SM Serving Node

This field contains the serving node identity, i.e. SGSN/MME/MSC identity serving the UE, received from MTC-IWF via T4 reference point for device trigger, as specified in TS 29.337 [231].

5.1.4.6.41 Void

5.1.4.6.42 Void

5.1.4.6.43 SM Status

This field contains the information from the TP-Status field in a Status-Report TPDU as defined in TS 23.040 [201]. This information is only applicable to delivery report charging procedures.

5.1.4.6.44 SM Total Number

This field contains the total number of short messages when the SMS is part of concatenated short message.

5.1.4.6.45 SM User Data Header

This field contains the user data header extracted from the user data of the SM, corresponding to the user data header (TP-UDH) is specified in TS 23.040 [201].

5.1.4.6.45A SMS Node Address

This field contains the Address of the SMS Node that produced the record: assigned E.164 number.

5.1.4.6.45B SMS Result

The field contains the result of an attempt for a Short Message transaction (submission or delivery) at SMS Service Center, when unsuccessful.

5.1.4.6.46 Submission Time

This field contains the timestamp of when the submitted Short Message arrived at the originating SMS Node, obtained from the TP-Service-Center-Time-Stamp (TP-SCTS) as defined in TS 23.040 [201].

5.1.4.6.47 UE Time Zone

This field contains the “Time zone” as specified in TS 29.060 [215], provided for the Mobile User during the SMS transaction.

5.1.4.6.48 User Location Info

This field contains the information about the location of the subscriber during the SMS transaction , as provided to the SMS Node, and specified in TS 29.061 [216] 3GPP user location.

5.1.4.7 ProSe CDR parameters

5.1.4.7.0 Introduction

This clause contains the description of each field of the ProSe CDRs specified in TS 32.277 [37].

5.1.4.7.0A Announcing PLMN ID

This field contains PLMN identity of the serving PLMN which signalled the carrier frequency, when this serving PLMN is not the HPLMN or VPLMN, if available.

5.1.4.7.1 Announcing UE HPLMN Identifier

This field contains identifier of Announcing UE HPLMN (MCC and MNC).

5.1.4.7.2 Announcing UE VPLMN Identifier

This field contains PLMN identity (MCC and MNC) of VPLMN for announcing UE. This field corresponds to Monitored PLMN ID in match report request, as defined in TS 23.303[235] clause 5.3.4. In this case it’s the same with Announcing UE HPLMN Identifier when non-roaming.

5.1.4.7.3 Application ID

This field carries a globally unique identifier identifying a specific 3rd party application, as upper layer of ProSe.

5.1.4.7.4 Cause for Record Closing

This field contains a reason for the release of the CDR. In case of Rf interface is used, it is derived from Change-Condition AVP at ProSe-information AVP level defined in TS 32.299 [50], when received. The following is included:- proximity alerted: It corresponds to "Proximity Alerted" in Change-Condition AVP.

– time expired with no renewal: It corresponds to "Time Expired With No Renewal" in Change-Condition AVP.

– requestor cancellation: It corresponds to "Requestor Cancellation" in Change-Condition AVP.

– time limited: It corresponds to "Time Limit" in Change-Condition AVP.

– maximum number of reports: It corresponds to "Max Number of reports" in Change-Condition AVP.

– abnormal release: It corresponds to "Abnormal Release" in Change-Condition AVP.

5.1.4.7.5 Direct Discovery Model

This field indicates model of the Direct Discovery used by the UE, i.e. Model A, Model B.

5.1.4.7.5A Discoveree UE HPLMN Identifier

This field contains identifier Discoveree of Discoveree UE HPLMN.

5.1.4.7.5B Discoveree UE VPLMN Identifier

This field contains identifier of Discoveree UE VPLMN.

5.1.4.7.5C Discoverer UE HPLMN Identifier

This field contains identifier of Discoverer UE HPLMN.

5.1.4.7.5D Discoverer UE VPLMN Identifier

This field contains identifier of Discoverer UE VPLMN.

5.1.4.7.6 Layer two Group ID

This field contains the identifier of a ProSe communication group, uniquely represents a specific one to-many ProSe Direct Communication and is included in CDRs for each participants in the specific group.

5.1.4.7.6A List of Application Specific Data

This field contains a list of data blocks provided by the application in the UE. The content of each block is application-specific.

5.1.4.7.6B List of Coverage Info

This field contains a list of coverage status changes with time stamps. When in coverage, additionally includes list of location changes (i.e., ECGI change) and time stamps.

5.1.4.7.6C List of Radio Parameter Sets

This field contains a list of radio parameter sets configured in the UE for direct communication use. Each set has an associated time stamp of when it became active.

5.1.4.7.7 List of Reception Data Containers and List of Transmission Data Containers

The same structure is used to convey both the List of Reception Data Containers and the List of Transmission Data Containers. Each list includes a list of changes in trigger conditions (e.g. change of PLMN, go out of coverage, come back to coverage, etc.) for a specific Communication. Each change is time stamped. Trigger condition is used to categorize received or transmitted data volumes, respectively, such as per coverage status duration. Each Direct Communication data containers may include the following fields:

– Local Sequence Number

– Change Time.

– Coverage status.

– UE Location.

– Data Volume (transmitted or received).

– Change Condition.

– VPLMN Identifier.

– Usage Information Report Sequence Number.

– Radio Resources Indicator.

– Radio Frequency.

Local Sequence Number is a service data container sequence number. It starts from 1 and is increased by 1 for each service date container generated within the lifetime of this direct communication.

Change Time includes the time when the container is closed and reported due to ProSe charging condition change..

Coverage status indicates whether UE is served by E-UTRAN or not, i.e. enter coverage, leave coverage.

UE Location contains the location information of the UE, i.e. ECGI

Data Volume is the amount of data received or transmitted by UE.

Change Condition contains the reason for closing the container, e.g. change of PLMN, go out of coverage, come back to coverage.

VPLMN Identifier contains the identifier of PLMN (MCC and MNC) that the UE visits.

Usage Information Report Sequence Number contains the sequence number of usage information report, which is used to generate the container.

Radio Resource Indicator identifies whether the operator-provided radio resources or the configured radio resources were used for ProSe direction communication.

Radio Frequency identifies the radio frequency used for ProSe direct communication.

5.1.4.7.7A List of Transmitters

This field contains a list of transmitters detected for the group. The information stored consists of the source IP address and the ProSe UE ID for each transmitter.

5.1.4.7.8 Monitored PLMN Identifier

This field carries Monitored PLMN ID (MCC and MNC) in Match Report request, as defined in TS 23.303[235] clause 5.3.4. It corresponds to the Announcing UE VPLMN Identifier when roaming and Announcing UE HPLMN Identifier when non-roaming.

5.1.4.7.9 Monitoring UE PLMN Identifier

This field contains identifier of monitoring UE PLMN (MCC and MNC).

5.1.4.7.10 Monitoring UE Identifier

This field carries identifier of the party who initiate Monitor/Match report, i.e. IMSI, which corresponds to UE Identifier parameter in Monitor/Match report request, as defined in TS 23.303[235].

5.1.4.7.11 Monitoring UE VPLMN Identifier

This field contains identifier of Monitoring UE VPLMN (MCC and MNC).

5.1.2.7.12 Node ID

This field contains an optional, operator configurable, identifier string for the node that had generated the CDR.
The Node ID may or may not be the DNS host name of the node.

5.1.4.7.13 PC Three Control Protocol Cause

This field holds the particular reason why a DISCOVERY_REQUEST or Match_Report messages from the UE have been rejected by the ProSe Function.

5.1.4.7.14 PC Three EPC Control Protocol Cause

This field holds the particular reason why a proximity request messages from the UE have been rejected by the ProSe Function.

5.1.4.7.14A PC5 Radio Technology

This field indicates the PC5 radio technology that the UE used for ProSe Direct Discovery.

5.1.4.7.15 ProSe Application ID

This field carries an identity used for ProSe direct discovery, identifying application related information for the ProSe-enabled UE.

5.1.4.7.16 ProSe Event Type

This field indicates ProSe charging event, i.e. open Announcing, open Monitoring, open Match Report, restricted Announcing, restricted Monitoring, restricted Match Report, restricted Discovery Request and restricted Discovery Reporting.

5.1.4.7.17 ProSe Function ID

This field holds the FQDN that identifies a ProSe Function.

5.1.4.7.18 ProSe Function IP Address

This field holds the IP-address of the ProSe Function.

5.1.4.7.19 ProSe Function PLMN Identifier

This field holds the PLMN Identifier (MCC and MNC) of the ProSe Function.

5.1.4.7.20 ProSe Group IP multicast address

This field holds The IP multicast address to be used for performing ProSe Direct Communication.

5.1.4.7.21 ProSe Reason for Cancellation

This field contains a reason for proximity request session is cancelled. In case of Rf interface is used, it is derived from ProSe-Reason-For-Cancellation AVP at ProSe-Information AVP level defined in TS 32.299 [50], when received. The following is included:

– Proximity alerted: When ProSe Function determines that two UEs are in proximity, a PROXIMITY_ALERT message is sent to UE. It corresponds to "Proximity alerted" in ProSe-Reason-For-Cancellation AVP.

– Time expired with no renewal: Allowed time windows is expired and no renewal request is received from UE. It corresponds to "Time expired with no renewal" in ProSe-Reason-For-Cancellation AVP.

– Requestor cancellation: a CANCEL_PROXIMITY_REQUEST message is received from UE. It corresponds to "Requestor cancellation" in ProSe-Reason-For-Cancellation AVP.

5.1.4.7.22 ProSe Request Timestamp

This field holds the timestamp when ProSe Request is received from UE.

5.1.4.7.22A ProSe Target Layer-2 ID

This field carries the identifier of UE, uniquely represents a specific one-to-one ProSe Direct Communication.

5.1.4.7.23 ProSe UE ID

This field carries a link layer identifier assigned by the EPS that uniquely represents the UE in the context of ProSe Direct Communication.

5.1.4.7.23A ProSe UE-to-Network Relay UE ID

The fields holds a link layer identifier that uniquely represents the ProSe UE-to-Network relay UE in the context of ProSe Direct Communication via UE-to-Network.

5.1.4.7.24 Proximity Alert Indication

This field indicates whether proximity alert has been sent before proximity request cancellation.

5.1.4.7.25 Proximity Alert Timestamp

This field holds the timestamp when proximity alert is sent, to indicate two UEs are in proximity.

5.1.4.7.26 Proximity Cancellation Timestamp

This field holds the timestamp when proximity request cancellation is requested.

5.1.4.7.27 Proximity Request Renewal Info Block List

This field holds a list of information blocks that are added by each of the Proximity Request renewal messages captured in the CDR. The information block contains information of the renewal request, e.g. timestamp, time window, range class, and UE location. Each Proximity Request Renewal Info Block may include the following fields:

– ProSe Request Timestamp

– Time Window

– Range Class

– UE Location

ProSe Request Timestamp is the time when ProSe Renewal Request is received from UE.

Time Window is the time interval in minutes during which a proximity renewal request is valid.

Range Class is the range class for a specific proximity renewal request.

UE Location the UE location with the best known accuracy (e.g. Cell ID or geo-location coordinates) at the time for the renewal request.

5.1.4.7.28 Range Class

This field carries a range class for a specific proximity request, e.g. 50 m, 100 m, 200 m, 500 m, 1000 m, which as "Range Class" defined in TS 24.334 [236].

5.1.4.7.29 Reason for Cancellation

This field indicates the reason for cancellation of an EPC-level Discovery request, i.e. Proximity alerted, Time expired with no renewal, Requestor cancellation.

5.1.4.7.30 Record Type

The field identifies the type of the record i.e. PF-DD-CDR, PF-ED-CDR and PF-DC-CDR.

5.1.4.7.30A Relay IP address

The field carries the IP address used as ProSe UE-to-Network Relay UE address for performing ProSe Direct Communication via UE-to-Network.

5.1.4.7.31 Requested Application Layer User ID

This field carries the user identifier designated in 3rd party application for the user who is targeted in proximity request.

5.1.4.7.32 Requested PLMN Identifier

This field contains PLMN identifier (MCC and MNC) of the user who is targeted in proximity request.

5.1.4.7.33 Requestor Application Layer User ID

This field carries the user identifier designated in 3rd party application for the user who initiate EPC-level ProSe discovery request.

5.1.4.7.34 Requestor EPC ProSe User ID

This field carries the identifier generated in ProSe Function for UE who initiate EPC-level ProSe Discovery request.

5.1.4.7.35 Requestor PLMN Identifier

This field contains PLMN identifier (MCC and MNC) of the user who initiate proximity request.

5.1.4.7.36 Role Of ProSe Function

This field indicates ProSe Function resides in which PLMN, i.e. HPLMN, VPLMN, Local PLMN.

5.1.4.7.37 Role Of UE

This field indicates role of the UE using ProSe served by the ProSe Function who generates the CDR, e.g. Announcing UE, Monitoring UE.

5.1.4.7.38 Source IP address

This field holds the IP address UE used as source address for performing ProSe Direct Communication.

5.1.4.7.38a Target IP address

The field holds the IP address used as target address for performing ProSe Direct one-to-one Communication.

5.1.4.7.38A Time of First Reception

This field contains the time when collection of reception data is started for the group in this CDR, i.e., the first one-to-many direct communication reception started.

5.1.4.7.38B Time of First Transmission

This field contains the time when collection of transmitted data is started for the group in this CDR, i.e., the first one-to-many direct communication transmission started.

5.1.4.7.39 Time Window

This field specify a time interval in minutes during which a proximity request is valid. The Time Window is in the range of 1 – 1440 minutes.

5.1.4.7.40 UE Location

This field carries the UE location with the best known accuracy (e.g. Cell ID or geo-location coordinates). The UE Location is set to the cell identity part of the Evolved Cell Global Identifier and obtained from the lower layers of the UE. The value of UE Location is with fixed length of 28 bits.

5.1.4.7.41 Validity Period

This field holds the time interval duration in minutes during which user is authorized for using ProSe Direct Discovery functionality (e.g. Announcing, Monitoring, Match reporting).

5.1.4.7.42 WLAN Link Layer ID

This field carrys WLAN link layer identifier.

5.1.4.8 Monitoring Event CDR parameters

5.1.4.8.0 Introduction

This clause contains the description of each field of the Monitoring Event CDRs specified in TS 32.278 [38].

5.1.4.8.1 Accuracy

This field contains desired level of accuracy of the requested location information and is applicable to the "Location Reporting" Monitoring Event type. Accuracy could be at cell level (CGI/ECGI), eNB, TA/RA level.

5.1.4.8.2 Chargeable Party Identifier

This field identifies the entity towards which accounting/charging functionality is performed by the involved 3GPP network elements.

5.1.4.8.3 Event Timestamp

This field contains the timestamp of the event that triggered the generation of charging information for the Monitoring Event action.

5.1.4.8.4 List of Locations

This field identifies the list of cells, eNBs and/or RAI(s)/TAI(s) for determination of the number of UEs in the area and is applicable to the "Number of UEs present in a geographic area" Monitoring Event type.

5.1.4.8.5 List of Monitoring Event Report Data

This list includes charging information for one or more Monitoring Event reports. Each Monitoring Event Report Data container may include the following fields:

– Event Timestamp

– SCEF Reference ID

– SCEF Id

– Monitoring Event Report Number

– Chargeable Party Identifier

– Monitored User

– Monitoring Type

– Reachability Information

– Reported Location

– Communication Failure Information

– List of Number Of UE Per Location Reports

Event Timestamp is a time stamp, which defines the moment when the event triggered the generation of charging information for the Monitoring Event report.

SCEF Reference ID is the identifier created by the SCEF, to identify a Monitoring Request. When combined with the SCEF Id, serves as a globally unique identifier for the Monitoring Request.

SCEF Id is the identifier of the SCEF to which the Monitoring Event Report message was sent.

Monitoring Event Report Number contains the number of the report being sent for the specific request from this node. The number is monotonically increasing for each report starting at 1 for each unique request.

Chargeable Party Identifier identifies the entity towards which accounting/charging functionality is performed by the involved 3GPP network elements.

Monitored User identifies the user that is monitored and is applicable to the "Loss of connectivity", "UE reachability", "Location Reporting", "Communication Failure" and "Availability after DDN Failure" monitoring event types.

Monitoring Type identifies the specific Monitoring Event being reporting.

Reachability Information identifies the reachability status of the UE and is applicable to the "UE reachability" Monitoring Event type.

Reported Location indicates the reported 3GPP system specific location information and is applicable to the "Location Reporting" Monitoring Event type.

Communication Failure Information indicates the reported the reason for communication failure and is applicable to the "Communication Failure" Monitoring Event type.

List of Number of UE per Location Reports contains a list of the location information along with the number of UEs found at that location by the MME/SGSN. It is applicable to the "the number of UEs at a given geographic location" Monitoring Event type.

5.1.4.8.6 Local Record Sequence Number

This field includes a unique record number created by this node. The number is allocated sequentially for each CDR including all CDR types. The number is unique within one node, which is identified either by field Node ID or by record-dependent node address.

The field can be used e.g. to identify missing records in post processing system.

5.1.4.8.7 Location Type

This field identifies whether the request is for Current Location or Last Known Location and is applicable to the "Location Reporting" and "Number of UEs present in a geographic area" Monitoring Event type.

5.1.4.8.8 Maximum Detection Time

This field identifies the maximum period of time without any communication with the UE after which the SCEF is to be informed that the UE is considered to be unreachable and is applicable to the "Loss of connectivity" Monitoring Event type. The value is on the order of 1 minute to multiple hours.

5.1.4.8.9 Maximum Number of Reports

This field identifies the maximum number of event reports to be generated until the associated Monitoring Event is considered to expire. A value of one implies a single event report is to be generated which makes it equivalent to a One-time Monitoring Request. This parameter is not applicable to the "Availability after DDN Failure" Monitoring Event type.

5.1.4.8.10 Monitored User

This field identifies the user that is monitored and is applicable to the "Loss of connectivity", "UE reachability", "Location Reporting", "Communication Failure" and "Availability after DDN Failure" Monitoring Event types.

5.1.4.8.11 Monitoring Duration

This field identifies the absolute time at which the related Monitoring Event request is considered to expire.

5.1.4.8.12 Monitoring Event Config Status

This field identifies whether the request was successful or not. When the request is not successful, a specific value is chosen to indicate the error occurred during handling of the Requested action for the Monitoring event.

5.1.4.8.13 Monitoring Event Configuration Activity

This field indicates Monitoring Event Configuration Activity, i.e. create, transfer, update, and delete.

5.1.4.8.14 Monitoring Type

This field identifies the specific Monitoring Event being requested, which can have the following values:

– Loss of connectivity.

– UE reachability.

– Location Reporting.

– Communication Failure.

– Availability after DDN Failure

– Number of UEs present in a geographic area.

5.1.4.8.15 Node ID

This field contains an optional, operator configurable, identifier string for the node that had generated the CDR.
The Node ID may or may not be the DNS host name of the node.

5.1.4.8.16 Reachability Configuration

This field contains the details for configuration for UE reachability, including reachability type, maximum latency and maximum response time.

5.1.2.8.17 Record Opening Time

A time stamp reflecting the time the CDF opened this record.

5.1.2.8.18 Record Type

The field identifies the type of the record i.e. ME-CO-CDR and ME-RE-CDR.

5.1.2.8.19 Retransmission

This parameter, when present, indicates that information from retransmitted Accounting Requests have been used in this CDR.

5.1.4.8.20 SCEF ID

This field contains identifier of the SCEF to which the Monitoring Event Report message was sent.

5.1.4.8.21 SCEF Reference ID

When combined with the SCEF ID, this field serves as a globally unique identifier for the Monitoring Event Request.