5.2.3 Charging scenarios for EAS deployment

32.2573GPPCharging managementEdge computing domain chargingRelease 17Telecommunication managementTS

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

5.2.3.1 Basic principles

5.2.3.1.1 General

Converged charging for EAS deployment may be performed by the CEF interacting with CHF using Nchf specified in 3GPP TS 32.290 [6] and 3GPP TS 32.291 [7]. In order to provide the data required for the management activities outlined in 3GPP TS 32.240 [1] (Credit-Control, accounting, billing, statistics etc.), the CEF shall be able to perform converged charging for each of the following:

– EAS deployment (see clause 5.1.2 3GPP TS 28.538 [12]);

– EAS modification (see clause 5.1.5 3GPP TS 28.538 [12]);

– EAS termination (see clause 5.1.3 3GPP TS 28.538 [12]).

The CEF shall subscribe to the notifications from the provisioning MnS producer for EAS LCM.

Once the notification about EAS LCM is received, the CEF shall be able to report the corresponding charging events to CHF for CDR generation.

A detailed formal description of the converged charging parameters defined in the present document is to be found in 3GPP TS 32.291 [7].

A detailed formal description of the CDR parameters defined in the present document is to be found in 3GPP TS 32.298 [3].

5.2.3.1.2 Applicable Triggers in the CEF

When a charging event is issued towards the CHF by the CEF, it includes details of charging information, such as EAS identifier (e.g. EAS ID, see 3GPP TS 23.558 [9]).

Each trigger condition (i.e. chargeable event) defined for EAS deployment charging, is specified with the associated behaviour when they are met.

The immediate report is applied to the chargeable events for EAS deployment charging, i.e. the chargeable events for which, when occurring, the current counts are closed and sent together with the charging data generated by the CEF towards the CHF in a Charging Data Request. New counts are started by the CEF.

When the CEF subscribes to the notifications about EAS LCM from the MnS producer, the converged charging is activated. When the CEF receives notifications about EAS LCM , the CEF invokes a Charging Data Request the CHF to report the EAS LCM activity as PEC.

Table 5.2.3.1.2-1 summarizes the set of default trigger conditions and their category which shall be supported by the CEF when charging is active for the EAS deployment charging.

Table 5.2.3.1.2-1: Default Trigger conditions in CEF

Trigger Conditions	Trigger level	Default category	CHF allowed to change category	CHF allowed to enable and disable	Message when "immediate reporting" category
EAS deployment charging
CEF receives the notifyMOICreation notification for an MOI of EASFunction from MnS producer, see 3GPP TS 28.532 [15].	–	Immediate	Not Applicable	No	PEC: Charging Data Request [Event]
CEF receives the notifyMOIAttributeValueChanges notification for an MOI of EASFunction from MnS producer, see 3GPP TS 28.532 [15].	–	Immediate	Not Applicable	No	PEC: Charging Data Request [Event]
CEF receives the notifyMOIDeletion notification for an MOI of EASFunction from MnS producer, see 3GPP TS 28.532 [15].	–	Immediate	Not Applicable	No	PEC: Charging Data Request [Event]

5.2.3.2 Message flows

5.2.3.2.1 General

The flows in the present document specify the interactions between the MnS producer, CEF and CHF for EAS deployment converged charging.

The interaction between MnS producer and CEF is based on MnS for subscribing to and reporting notifications specified in 3GPP TS 28.532 [15] and 3GPP TS 28.538 [12].

This interaction between CEF and CHF is based on Charging Data Request /Response specified in 3GPP TS 32.290 [6].

5.2.3.2.2 EAS deployment charging enabled by CEF

Figure 5.2.3.2.2-1 describes an EAS deployment charging message flows in PEC, based on the converged charging architecture with MnS producer enabled by CEF (see clause 4.2.2).

Figure 5.2.3.2.2-1: EAS deployment charging – PEC

1) CEF subscribes to the notifications about EAS LCM from the MnS: The CEF consumes the provisioning MnS (see 3GPP TS 28.532 [15]) to subscribe to the notifications about EAS LCM, including notifyMOICreation, notifyMOIAttributeValueChanges, and notifyMOIDeletion.

2) EAS LCM request: The MnS consumer sends the EAS LCM request to the MnS producer, the EAS LCM request is done via createMOI, modifyMOIAttributes or deleteMOI operation (see 3GPP TS 28.532 [15]) for the EASFunction IOC (see 3GPP TS 28.538 [12]).

3) EAS LCM process: The MnS producer processes and executes the EAS LCM according to the request (e.g. instantiation, upgrade, deletion).

4) EAS LCM response: The MnS producer sends the EAS LCM result to the MnS consumer.

5) EAS LCM notification: The MnS producer sends the EAS LCM notification (i.e. notifyMOICreation, notifyMOIAttributeValueChanges, or notifyMOIDeletion) to the CEF:

5ch-a) Charging Data Request [Event]: The CEF generates charging data related to the EAS LCM notification and sends the charging data request.

5ch-b) Create CDR: The CHF stores received information and create a CDR related to the event.

5ch-c) Charging Data Response [Event]: The CHF informs the CEF on the result of the request.

5.2.3.3 CDR generation

5.2.3.3.1 Introduction

The CHF CDRs for EAS deployment charging are generated by the CHF to collect charging information that they subsequently transfer to the Charging Gateway Function (CGF).

The following clauses describe in detail the conditions for generating the CHF CDR.

5.2.3.3.2 Triggers for CHF CDR

5.2.3.3.2.1 General

An EAS deployment charging CHF CDR is used to collect charging information related to EAS deployment chargeable events.

5.2.3.3.2.2 Triggers for CHF CDR generation

A CHF CDR shall be generated by the CHF for each received Charging Data Request [Event].

5.2.3.4 Ga record transfer flows

For Ga protocol application refer to 3GPP TS 32.295 [5].

5.2.3.5 Bee CDR file transfer

For Bee protocol application refer to 3GPP TS 32.297 [4].