Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 28.201  Word version:  17.0.0

Top   Top   Up   Prev   Next
1…   4…   5…   6…

 

5  Network slice performance and analytics charging principles and scenariosp. 11

5.1  Network slice performance and analytics charging principlesp. 11

5.1.1  Generalp. 11

Performance and analytics based charging shall be achieved by subscription to the performance metrics or analytics information of a specific network slice and report them to CHF for charging purpose. The detail of performance and analytics information is specified in the clause 5.1.3.
Network slice performance and analytics charging shall support collection of network slice performance metrics related to network slice charging based on network slice performance and analytics charging requirements.
Up

5.1.2  Requirementsp. 11

The following are high-level charging requirements specific to the network slice performance and analytics charging:
  • The CEF shall support subscription to specific network slice performance and analytics information.
  • The CEF shall support reporting charging information based on network slice performance and analytics information.
  • The CEF shall support reporting performance and analytics charging information per network slice.
  • The CEF shall support PEC scenario to report performance and analytics charging information.
Up

5.1.3  Network slice performance and analytics charging informationp. 11

The following is a non-exhaustive list related to one or more of the performance and analytics inputs relevant to charging for network slice:
Up

5.1.4  NWDAF discoveryp. 11

The NWDAF service discovery by the CEF is specified in TS 29.510.

5.1.5  CHF selectionp. 12

The CHF selection, i.e. CHF address determination, by the CEF is done based on the following and with this priority order (highest to lowest):
  • NRF based discovery;
  • pre-configured CHF address in the CEF.

5.2  Network slice performance and analytics charging scenariosp. 12

5.2.1  Basic principlesp. 12

5.2.1.1  Generalp. 12

Network slice performance and analytics charging is performed by the CEF interacting with CHF using Nchf specified in TS 32.290 and TS 32.291.In order to provide the data required for the charging management activities outlined in TS 32.240, the CEF shall be able to perform converged charging for each of the following:
  • the performance and analytics information obtained from NWDAF.
  • the performance and analytics information obtained from MnS;
The CEF shall be able to obtain performance and analytics information from the NWDAF and/or MnS as follows:
  • The Subscribe/Notify are exchanged between the CEF and the NWDAF using the Nnwdaf service. The interactions are issued by the CEF towards the NWDAF when certain conditions are met.
  • The Subscribe/Notify are exchanged between the CEF and the MnS producer. The interactions are issued by the CEF when certain conditions are met.
The CEF shall be able to perform converged charging by interacting with CHF, for charging data related to network slice performance and analytics. The Charging Data Request and Charging Data Response are exchanged between the CEF and the CHF, based on PEC scenarios specified in TS 32.290. The Charging Data Request is issued by the CEF towards the CHF when certain conditions (chargeable events) are met.
The charging information is collected per Single Network Slice Selection Assistance Information (S-NSSAI).
The services provided by NWDAF are defined in the TS 23.288 and the services provided by MnS producer are defined in the TS 28.533. The charging functionalities for network slice performance and analytics, i.e. CEF functionality, charging events and charging procedures, are defined in the following clauses.
Whether performance and analytics charging for an S-NSSAI in the CEF is active or not is based on configuration. Which performance and analytics information is obtained from NWDAF or MnS by the CEF is based on configuration.
The configuration may be per S-NSSAI, detailed information about the configuration or provisioning of the configuration is outside the present document.
The contents and purpose of each charging event that triggers interaction with CHF, as well as the chargeable events that trigger them, are described in clauses 5.2.2.
A detailed formal description of the converged charging parameters to CHF defined in the present document can be found in TS 32.291.
A detailed formal description of the CDR parameters defined in the present document can be found in TS 32.298.
Up

5.2.1.2  Applicable triggers in network slice performance and analytics chargingp. 12

Triggers for CEF to invoke a Charging Data Request [Event] towards the CHF are defined as following trigger conditions.
When a charging event is issued towards the CHF, it includes details such as Single Network Slice Selection Assistance Information (S-NSSAI). Table 5.2.1.2-1 summarizes the set of default trigger conditions and their category which shall be supported by the CEF.
Trigger Conditions Trigger level Default category CHF allowed to change category CHF allowed to enable and disable Message when "immediate reporting" category
Notify event for a subscription-DeferredNot ApplicableNot ApplicableCharging Data Request [Event]
Expiry of time limit per S-NSSAI-ImmediateNot ApplicableNot ApplicableCharging Data Request [Event]
Threshold reached for a performance indicator (e.g. load level per S-NSSAI)-ImmediateNot ApplicableNot ApplicableCharging Data Request [Event]
Limit reached for number of notify events per subscription made by CEF-ImmediateNot ApplicableNot ApplicableCharging Data Request [Event]
Limit reached for number of notify events per S-NSSAI-ImmediateNot ApplicableNot ApplicableCharging Data Request [Event]
NOTE 1:
In addition, there may be operator specific triggers.
NOTE 2:
The threshold and limit is default configured and updated based on the configuration.
The CDR generation mechanism processed by the CHF upon receiving Charging Data Request [Event] issued by the CEF for these chargeable events, is specified in clause 5.2.3.
Up

5.2.2  Message flowsp. 13

5.2.2.1  Generalp. 13

The message flows in the present document specify the interaction for performance and analytics charging functionality, based on the performance and analytics information from NWDAF and MnS.
The charging interaction is based on Charging Data Request /Response messages specified in TS 32.290, exchanged between the CEF and the CHF.
One source of performance and analytics information is based on the messages specified in TS 23.288, exchanged between the CEF and NWDAF.
Another source of performance and analytics information is based on the messages specified in TS 28.532, exchanged between the CEF and MnS.
Up

5.2.2.2  Analytics and performance charging from CEFp. 13

5.2.2.2.1  Generalp. 13
The clause below describes analytics and performance charging from CEF scenarios.
5.2.2.2.2  General analytics and performance charging - PECp. 14
The following Figure 5.2.2.2.2-1 describes analytics and performance charging:
Reproduction of 3GPP TS 28.201, Fig. 5.2.2.2.2-1: Analytics and performance reporting
Up
Step 1.
Collection of analytics and performance information: Collection of information related to the network slice analytics and performance is done by the CEF.
Step 2.
Trigger condition met: the CEF determines based on the collected information and the trigger conditions that a report of charging information to the CHF is needed.
Step 3.
Charging Data Request [Event]: The CEF generates charging data related to the collected information and sends the charging data request for the CHF to process the related charging data for CDR generation purpose.
Step 4.
Create CDR: the CHF stores received information and creates a CDR related to the event.
Step 5.
Charging Data Response [Event]: The CHF informs the CEF on the result of the request.
Up

5.2.2.3  Network Slice data analytics subscription from NWDAFp. 14

5.2.2.3.1  Generalp. 14
The clause below describes network data analytics subscription scenarios. The CEF acts as a NWDAF Service Consumer and uses the Nnwdaf_AnalyticsSubscription service to subscribe to the applicable analytics information required for the chargeable events, based on clause 6.1.1 in TS 23.288.
5.2.2.3.2  Network slice performance and analytics information Subscribe/Notifyp. 14
The following Figure 5.2.2.3.2-1 procedure is used by CEF to subscribe/unsubscribe at NWDAF to be notified on performance and analytics information, using Nnwdaf_AnalyticsSubscription service for Network Slice defined in TS 23.288.
Reproduction of 3GPP TS 28.201, Fig. 5.2.2.3.2-1: Analytics and performance from NWDAF
Up
Step 1.
Subscribe Request: the CEF decides to start the collection of performance and analytics information and subscribes to performance and analytics information from NWDAF with the performance indicator, S-NSSAI and subscription condition (e.g. Start time, stop time).
Step 2.
Subscribe Respond: the NWDAF responses the subscription successful.
Step 3.
Notification: based on the subscription of performance and analytics information, the NWDAF notifies the CEF with the performance and analytics information.
Step 4.
Unsubscribe Request: the CEF cancels the subscription to performance and analytics information.
Step 5.
Unsubscribe Respond: the NWDAF responses the unsubscription successful.
The CEF could update the subscription during the duration of the subscription.
Up

5.2.2.4  Network slice performance and analytics subscription using MnSp. 15

5.2.2.4.1  Generalp. 15
CEF may support subscription to network slice performance information using MnS. The clauses below describes message flow of network slice performance and analytics charging using MnS defined in clause 11.3.1 in TS 28.532 (e.g. Subscribe operation, unsubscribe operation and notifyFileReady).
5.2.2.4.2  Network slice performance and analytics information Subscribe/Notifyp. 15
The following Figure 5.2.2.4.2-1 procedure is used by CEF to subscribe/unsubscribe the performance and analytics information using MnS.
Reproduction of 3GPP TS 28.201, Fig. 5.2.2.4.2-1: Performance and analytics information from MnS Producer
Up
Step 1.
Subscribe Request: The CEF decides to start the collection of performance and analytics information and subscribes to performance and analytics information using MnS with the performance indicator, S-NSSAI and subscription condition (e.g. Start time, stop time).
Step 2.
Subscribe Respond: the MnS producer responses the subscription successful.
Step 3.
Notification: Based on the subscription of performance and analytics information, the MnS producer notifies the CEF with the performance and analytics information.
Step 4.
Notification Acknowledge: the CEF sends the acknowledge notification.
Step 5.
Unsubscribe Request: the CEF cancels the subscription to performance and analytics information.
Step 6.
Unsubscribe Respond: the MnS producer responses the unsubscription successful.
The CEF could update the subscription during the duration of the subscription
Up

5.2.3  CDR generationp. 16

5.2.3.1  Introductionp. 16

The network slice performance and analytics CHF CDRs 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 network slice performance and analytics CHF CDR, which shall be supported by the CHF.

5.2.3.2  Triggers for CHF CDRp. 16

5.2.3.2.1  Generalp. 16
A network slice performance and analytics CHF CDR is used to capture charging information related to network slice performance and analytics chargeable events for PEC.
5.2.3.2.2  Triggers for CHF CDR generationp. 16
A network slice performance and analytics CHF CDR is generated by the CHF for each received Charging Data Request [Event].

5.2.4  Ga record transfer flowsp. 16

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

5.2.5  Bns CDR file transferp. 17

Details of the Bns protocol application are specified in TS 32.297.

Up   Top   ToC