5 Monitoring event charging principles and scenarios

32.2783GPPCharging managementMonitoring event chargingRelease 17Telecommunication managementTS

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

5.1 Monitoring event charging principles

Two types of activities associated with Monitoring Events as specified in TS 23.682 [243] are:

– Monitoring Event configuration request

– Monitoring Event report

The following are high level charging requirements for Monitoring Events, derived from requirements in TS 23.682 [243]:

– MECN shall be able, based on operator configuration, to collect charging information for Monitoring Event configuration requests from HSS or SCEF in the same PLMN using offline charging.

– MECN shall be able, based on operator configuration, to collect charging information for Monitoring Event configuration requests from HSS or SCEF in a different PLMN using offline charging.

– MECN shall be able, based on operator configuration, to collect charging information for Monitoring Event reports toward SCEF in the same PLMN using offline charging.

– MECN shall be able, based on operator configuration, to collect charging information for Monitoring Event reports towards SCEF in a different PLMN using offline charging.

For Monitoring Event configuration requests, the MECN shall collect the following information:

– time configuration request received;

– configuration activity: create, transfer, update, delete;

– identity of the SCEF originating request and the reference identifier used by the SCEF for the request;

– type of event to be monitored;

– maximum number of reports to be generated for the event type;

– time at which the request is considered to expire;

– identity of the chargeable party for the request, when provided to the MECN.

For Monitoring Event configuration requests, the MECN shall collect the following information, if applicable for the type of event:

– identity of the monitored user;

– maximum period of time without any communication with the UE;

– reachability type, e.g. SMS or data;

– maximum delay acceptable for downlink data transfers;

– time for which the UE stays reachable to allow the SCS/AS to reliable deliver the required downlink data;

– number of packets that the Serving Gateway shall buffer in case the UE is not reachable;

– whether the request is for current location or last known location;

– desired level of accuracy of the requested location information;

– list of cells, eNodeB’s and/or RAI(s)/TAI(s) for determination of the number of UEs in the area;

– whether the request was successful or not.

For Monitoring Event reports, the MECN shall collect the following information:

– identity of the SCEF originating request and the reference identifier used by the SCEF for the request;

– type of event reported;

– number of the event report for the specific configured request in the MECN;

– identity of the chargeable party for the request, when provided to the MECN.

For Monitoring Event reports, the MECN shall collect the following information, if applicable for the type of event:

– identity of the monitored user;

– reachability status of the user;

– reported location of the user;

– RAN or NAS cause code for communication failure with the UE;

– an indication whether an error occurred in the report.

5.2 Monitoring event offline charging scenarios

5.2.1 Basic principles

If charging is supported by an SGSN, MME, or IWK-SCEF, known as a MECN, it shall be able to report charging events for CDRs generated by the CDF.

The following chargeable events are defined for Monitoring Event configuration requests:

– Monitoring Event configuration request received from HSS or SCEF.

– Monitoring Event configuration request transferred from another MECN.

– Monitoring Event configuration request update received from HSS or SCEF.

– Monitoring Event configuration request deletion received from HSS or SCEF.

The following chargeable events are defined for Monitoring Event reports:

– Monitoring Event report sent, including standalone report request or immediate reporting in the configuration answer messages.

5.2.2 Rf message flows

When a charging event is reported to the CDF, it includes details about the configured Monitoring Event including the identity of the SCEF originating the request and the reference identifier used by the SCEF for the request; type of Monitoring Event; and identity of the chargeable party, if available. Additional information is included based on whether the charging event is for a configuration request or a report and on the specific type of Monitoring Event.

The trigger conditions described in Table 5.2.2.1 are applicable for charging information collection for Monitoring Event charging. Charging Data Request[Event] is sent upon occurrence of the specified event.

In order to save MECN processing effort, a burst of Monitoring Event reports in a short time interval may be treated as a single charging event for reporting to the CDF. The determination of whether to send Charging Data Request[Event] for a single Monitoring Event report sent or for a burst of Monitoring Event reports sent is implementation-specific.

Table 5.2.2.1: Charging Data Request messages triggered for Monitoring Event charging

message

Triggering conditions

Charging Data Request[Event]

Receipt of Monitoring Event configuration request (new request, update, delete).

Transfer of Monitoring Event configuration request.

Single Monitoring Event report sent.

Burst of Monitoring Event reports sent.

5.2.3 CDR generation

A Monitoring Event Configuration Request CDR (ME-CO-CDR) is meant to collect charging information related to an individual Monitoring Event configuration request in the MECN. A single CDR is generated for each event.

A Monitoring Event Report CDR (ME-RE-CDR) is meant to collect charging information related to a single Monitoring Event report or a burst of Monitoring Event reports in a short time interval. The CDF, may, based on operator implementation, generate a single ME-RE-CDR when a burst of Monitoring Event reports is reported by the CTF or may generate an individual ME-RE-CDR for each Monitoring Event report when a burst is reported by the CTF.

5.2.4 Ga record transfer flows

Details of the Ga protocol application are specified in TS 32.295 [54].

5.2.5 Bmn CDR file transfer

Details of the Bx protocol application are specified in TS 32.297 [52].

5.3 Monitoring event online charging scenarios

5.3.1 Basic principles

Not specified in the present document.

5.3.2 Ro message flows

Not specified in the present document.