6 Definition of charging information
28.2013GPPCharging managementNetwork slice performance and analytics charging in the 5G System (5GS)Release 17Stage 2TS
6.1 Data description for network slice performance and analytics charging
6.1.1 Message contents
6.1.1.1 General
The Charging Data Request and Charging Data Response are specified in clause 5.1.2.2.1 of TSĀ 32.290 [50].
Table 6.1.1.1-1 describes the use of these messages for network slice performance and analytics charging.
Table 6.1.1.1-1: network slice performance and analytics charging messages reference table
|
Message |
Source |
Destination |
|
Charging Data Request |
CEF |
CHF |
|
Charging Data Response |
CHF |
CEF |
The following clauses describe the different fields used in the Charging Data messages and the category in the tables is used according to the charging data configuration defined in clause 5.4 of TS 32.240 [1].
6.1.1.2 Charging Data Request message
Table 6.1.1.2-1 illustrates the basic structure of a Charging Data Request message from the CEF as used for performance and analytics based charging.
Table 6.1.1.2-1: Charging Data Request message contents
|
Information Element |
Category for converged charging |
Description |
|---|---|---|
|
Session Identifier |
OC |
Described in TS 32.290 [57]. |
|
Subscriber Identifier |
– |
This field is not applicable. |
|
Tenant Identifier |
OM |
This field if present is the identifier of subscriber of network slice. |
|
NF Consumer Identification |
M |
Described in TS 32.290 [57]. |
|
NF Functionality |
M |
Described in TS 32.290 [57]. |
|
NF Name |
OC |
Described in TS 32.290 [57]. |
|
NF Address |
OC |
Described in TS 32.290 [57]. |
|
NF PLMN ID |
OC |
Described in TS 32.290 [57]. |
|
Invocation Timestamp |
M |
Described in TS 32.290 [57]. |
|
Invocation Sequence Number |
– |
This field is not applicable. |
|
Retransmission Indicator |
– |
This field is not applicable. |
|
One-time Event |
OC |
Described in TS 32.290 [57]. |
|
One-time Event Type |
OC |
Described in TS 32.290 [57]. |
|
Notify URI |
– |
This field is not applicable. |
|
Service Specification Information |
OC |
Described in TS 32.290 [57]. |
|
Triggers |
OC |
Described in TS 32.290 [57]. |
|
Multiple Unit Usage |
OM |
Described in TS 32.290 [57], with the exception that quota management is not applicable. |
|
Rating Group |
M |
Described in TS 32.290 [57] |
|
Requested Unit |
– |
This field is not applicable. |
|
Used Unit Container |
OC |
Described in TS 32.290 [57] |
|
Service Identifier |
– |
This field is not applicable. |
|
Quota management Indicator |
– |
This field is not applicable. |
|
Triggers |
OC |
This field is described in TS 32.290 [57] and holds the network slice performance and analytics specific triggers described in clause 5.2.1. |
|
Trigger Timestamp |
OC |
Described in TS 32.290 [57] |
|
Time |
– |
This field is not applicable. |
|
Total Volume |
– |
This field is not applicable. |
|
Uplink Volume |
– |
This field is not applicable. |
|
Downlink Volume |
– |
This field is not applicable. |
|
Service Specific Unit |
– |
This field is not applicable. |
|
Event Time Stamps |
– |
This field is not applicable. |
|
Local Sequence Number |
OM |
Described in TS 32.290 [57] |
|
NSPA Container Information |
OC |
This field holds the network slice performance and analytics container specific information described in clause 6.2.1.3. |
|
NSPA Charging Information |
OC |
This field holds the network slice information, which is reported to the CHF described in clause 6.2.1.2. |
6.1.1.3 Charging data response message
Table 6.1.1.3-1 illustrates the basic structure of a Charging Data Response message from the CHF as used for performance and analytics based charging.
Table 6.1.1.3-1: Charging Data Response message contents
|
Information Element |
Category for converged charging |
Description |
|---|---|---|
|
Session Identifier |
OC |
Described in TS 32.290 [57]. |
|
Invocation Timestamp |
M |
Described in TS 32.290 [57]. |
|
Invocation Result |
OC |
Described in TS 32.290 [57]. |
|
Invocation Sequence Number |
– |
This field is not applicable. |
|
Session Failover |
OC |
Described in TS 32.290 [57]. |
|
Triggers |
– |
This field is not applicable. |
|
Multiple Unit Information |
– |
This field is not applicable. |
6.1.2 Ga message contents
Details of the Ga message contents are specified in TS 32.295 [55].
6.1.3 CDR description on the Bns interface
6.1.3.1 General
This clause describes the CDR content and format generated for performance and analytics based charging.
The following table provide a brief description of each CDR parameter. The category in the tables is used according to the charging data configuration defined in clause 5.4 of TS 32.240 [1]. Full definitions of the CDR parameters, sorted by the name in alphabetical order, are provided in TS 32.298 [57].
6.1.3.2 Network slice performance and analytics CHF CDR data
If enabled, network slice performance and analytics CDRs shall be produced for each network slice (i.e. S-NSSAI).
The fields of network slice performance and analytics CHF CDR are specified in tableĀ 6.1.3.2-1.
Table 6.1.3.2-1: Network slice performance and analytics CHF record data
|
Field |
Category |
Description |
|---|---|---|
|
Record Type |
M |
CHF record. |
|
Recording Network Function ID |
OM |
This field holds the name of the recording entity, i.e. the CHF id. |
|
Tenant Identifier |
OM |
This field if present is the identifier of subscriber of network slice.. |
|
NF Consumer Information |
M |
This field holds the information of the CEF that used the charging service. |
|
NF Functionality |
M |
This field contains the function of the node (i.e. CEF) |
|
NF Name |
OC |
This field holds the name of the CEF used. |
|
NF Address |
OC |
This field holds the IP Address of the CEF used. |
|
NF PLMN ID |
OC |
This field holds the PLMN identifier (MCC MNC) of the CEF. |
|
List of Multiple Unit Usage |
OM |
This field holds a list of changes in charging conditions for one single Network Slice Selection Assistance. The list is categorized per rating group. Each change is time stamped. |
|
Rating Group |
OM |
This filed holds the rating group. |
|
Used Unit Container |
OC |
This field holds the information connected to the reported network slice. |
|
Triggers |
OC |
This field holds the reason for closing the used unit container. |
|
Trigger Timestamp |
OC |
This field holds the timestamp of the trigger. |
|
Local Sequence Number |
M |
This field holds the container sequence number. |
|
NSPA Container Information |
OC |
This field holds the network slice performance and analytics container specific information described in clause 6.2.1.3. |
|
NSPA Charging Information |
OM |
This field holds the network slice performance and analytics charging information defined in clause 6.2.1.2. |
|
Record Opening Time |
M |
Described in TS 32.298 [57]. |
|
Duration |
M |
Described in TS 32.298 [57]. |
|
Record Sequence Number |
C |
Described in TS 32.298 [57]. |
|
Cause for Record Closing |
M |
Described in TS 32.298 [57]. |
|
Local Record Sequence Number |
OM |
Described in TS 32.298 [57]. |
|
Record Extensions |
OC |
Described in TS 32.298 [57]. |
6.2 Network slice performance and analytics charging specific parameters
6.2.1 Definition of network slice performance and analytics charging information
6.2.1.1 General
The Charging Information parameter used for network slice performance and analytics charging is provided in the following clauses.
6.2.1.2 Definition of Performance and Analytics Charging Information
Specific charging information used for network slice performance and analytics charging is provided within the Performance and Analytics Charging Information.
The detailed structure of the Performance and Analytics Charging Information can be found in table 6.2.1.2.1.
Table 6.2.1.2-1: Structure of NSPA Charging Information
|
Information Element |
Category |
Description |
|
Single NSSAI |
M |
This field holds network slice information the performance and analytics information belongs to. |
6.2.1.3 Definition of NSPA Container Information
Specific charging information used for network slice performance and analytics charging is provided within the NSPA Container Information.
The detailed structure of the NSPA Charging Information can be found in table 6.2.1.3.1.
Table 6.2.1.3-1: Structure of NSPA Container Information
|
Information Element |
Category |
Description |
|
Latency |
OC |
This field holds latency as described in 28.554 [271]. |
|
Throughput |
OC |
This field holds throughput as described in TS 28.554 [271] |
|
Maximum packet loss rate |
OC |
This field holds maximum packet loss rate as described in TS GSMA NG.116 [500] |
|
Service Experience statistics data |
OC |
This field holds service experience statistics data as described in TS 23.288 [150] |
|
Number of PDU sessions |
OC |
This field holds the number of PDU sessions as described in TS 28.554 [271]. |
|
Number of registered Subscribers |
OC |
This field holds the number of registered subscribers as described in TS 28.554 [271]. |
|
Load level |
OC |
This field holds the load level as described in TS 23.288 [150]. |
6.2.2 Formal network slice performance and analytics charging parameter description
6.2.2.1 Network slice performance and analytics CHF CDR parameters
The detailed definitions, abstract syntax and encoding of network slice performance and analytics CHF CDRs parameters are specified in TS 32.298 [57].
6.2.2.2 Network slice performance and analytics resources attributes
The detailed definitions of resources attributes used for network slice performance and analytics charging are specified in TS 32.291 [51].
6.2.3 Detailed message format for converged charging
The following clause specifies per Operation Type the charging data that are sent by CEF for network slice performance and analytics converged charging.
The Operation Types are listed in the following order: I (Initial)/T (Termination)/E (Event). Therefore, when all Operation Types are possible it is marked as ITE. If only some Operation Types are allowed for a node, only the appropriate letters are used (i.e. IT or E) as indicated in the table heading. The omission of an Operation Type for a particular field is marked with "-" (i.e. I-E). Also, when an entire field is not allowed in a node the entire cell is marked as "-".
Table 6.2.3-1 defines the basic structure of the supported fields in the Charging Data Request message for CEF converged charging.
Table 6.2.3-1: Supported fields in Charging Data Request message
|
Information Element |
Analytics and Performance |
CEF |
|---|---|---|
|
Supported Operation Types |
E |
|
|
Session Identifier |
– |
|
|
Subscriber Identifier |
– |
|
|
Tenant Identifier |
E |
|
|
NF Consumer Identification |
E |
|
|
Invocation Timestamp |
E |
|
|
Invocation Sequence Number |
– |
|
|
Retransmission Indicator |
– |
|
|
One-time Event |
E |
|
|
One-time Event Type |
E |
|
|
Notify URI |
– |
|
|
Triggers |
E |
|
|
Multiple Unit Usage |
E |
|
|
Rating Group |
E |
|
|
Used Unit Container |
E |
|
|
Triggers |
E |
|
|
NSPA Container Information |
E |
|
|
NSPA Charging Information |
||
|
Single NSSAI |
E |
|
Table 6.2.3-2 defines the basic structure of the supported fields in the Charging Data Response message for CEF converged charging.
Table 6.2.3-2: Supported fields in Charging Data Response message
|
Information Element |
Analytics and Performance |
CEF |
|---|---|---|
|
Supported Operation Types |
E |
|
|
Session Identifier |
E |
|
|
Invocation Timestamp |
E |
|
|
Invocation Result |
E |
|
|
Invocation Sequence Number |
– |
|
|
Session Failover |
E |
|
|
Triggers |
– |
|
|
Multiple Unit information |
– |
|
6.3 Bindings for network slice performance and analytics converged charging
This mapping between the Information Elements, resource attributes and CHF CDR parameters for network slice performance and analytics converged charging is described in clause 7 of TS 32.291 [51].
Annex A (informative):
Change history
|
Change history |
|||||||
|
Date |
Meeting |
Tdoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2020-09 |
SA#89e |
Upgrade to change control version including EditHelp review |
16.0.0 |
||||
|
2020-12 |
SA#90e |
SP-201043 |
0002 |
1 |
F |
Correction of the Category and Operation Types |
16.1.0 |
|
2020-12 |
SA#90e |
SP-201043 |
0004 |
– |
F |
Update description of Charging Enablement Function |
16.1.0 |
|
2020-12 |
SA#90e |
SP-201043 |
0006 |
– |
F |
Correction on sender of Charging Data Response message |
16.1.0 |
|
2020-12 |
SA#90e |
SP-201043 |
0007 |
– |
F |
Correction on NSPA Container Information in Charging Data Request message |
16.1.0 |
|
2022-03 |
– |
– |
– |
– |
– |
Update to Rel-17 version (MCC) |
17.0.0 |