B.2 Charging Architecture for 5G VN group management charging
32.2543GPPCharging managementExposure function Northbound Application Program Interfaces (APIs) chargingRelease 17Telecommunication managementTS
B.2.1 General
The 5G VN group management converged charging architecture including CEF based charging specified in the following clause B.2.1.1.
B.2.1.1 Logical Charging architecture – CEF based charging
The logical ubiquitous charging architecture and the reference points for 5G VN group management with the CEF architecture is shown in figure B.2.1-1.
Figure B.2.1.1-1: Logical ubiquitous charging architecture for 5G VN group management with the CEF architecture
B.2.2 Void
B.2.3 Charging principles and scenarios
B.2.3.1 Basic principles
5G VN group management charging is performed by the NEF or CEF interacting with CHF using Nchf specified in TS 32.290 [57] and TS 32.291 [58]. In order to provide the data required for the charging management activities, the converged charging can be performed for each of the following:
– The CEF are able to get the 5G VN group information (e.g. GroupIdentifiers) from UDM via Nudm_SubscriberDataManagement service, specified in the TS 23.502 [214] and TS 29.503[236]. The Charging Data Request and Charging Data Response are exchanged between the CEF and the CHF, based on PEC scenarios as specified in TS 32.290 [57]. The Charging Data Request is issued by the CEF towards the CHF when certain conditions (chargeable events) are met.
The CEF only uses the GET operation of Nudm_SubscriberDataManagement service to obtain the 5G VN group information.
– The NEF are able to report the 5G VN group information (e.g. add/delete 5G VN Group members) to CHF based on the API invocation (i.e. 5GLANParameterProvision API) chargeable events.
In order to avoid the duplicate charging, the NEF based and CEF based 5G VN group management charging will not be invoked at the same time, which depend on the implementation based on the operator policy.
The 5G VN group management charging information is collected per VN group. The message contents and purpose of each charging event that triggers interaction with CHF, as well as the chargeable events that trigger them, are described in following clauses.
A detailed formal description of the converged charging parameters to CHF defined in the present document can be found in TS 32.291 [58].
A detailed formal description of the CDR parameters defined in the present document can be found in TS 32.298 [51].
B.2.3.2 Applicable triggers in 5G VN group management charging
B.2.3.2.1 5G VN group management charging via UDM
A set of trigger conditions are defined for the CEF to invoke a Charging Data Request [Event] towards the CHF.
Table B.2.3.2.1-1 summarizes the set of default trigger conditions and their category which shall be supported by the CEF.
Table B.2.3.2.1-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 |
|---|---|---|---|---|---|
|
Receive the 5G VN group information from UDM |
– |
Immediate |
Not Applicable |
Not Applicable |
Charging Data Request [Event] |
B.2.3.3 Message flows
B.2.3.3.1 5G VN group management charging via UDM
The following message flow specifies the interaction between the CEF and the CHF for 5G VN group management charging. This interaction is based on Charging Data Request /Response specified in TS 32.290 [57].
Figure B.2.3.3.1-1: Message flow for CEF interation for 5G VN group charging—PEC
1. The CEF decides to get the 5G VN group management information based on the charging requirement.
2. The CEF sends the 5G VN group management information Request to the UDM via Nudm_SubscriberDataManagement service.
3. The UDM sends the 5G VN group management information successful Response to the CEF, including current VN group information, e.g. the Internal Group ID, External Group ID, and UE Id List.
3ch-a. The CEF sends Charging Data Request [Event] to CHF for 5G VN group management information.
3ch-b. The CHF creates a CDR.
3ch-c. The CHF acknowledges by sending Charging Data Response [Event] to the CEF.
B.2.3.4 CDR generation
The CHF CDRs for 5G VN group management charging are generated by the CHF to collect charging information that they subsequently transfer to the Charging Gateway Function (CGF).
A 5G VN group management CHF CDR is used to capture charging information related to 5G VN group management chargeable events and is generated by the CHF for each received Charging Data Request [Event].
B.2.4 Charging Information
B.2.4.1 Data description for 5G VN group management charging
The Charging Data Request and Charging Data Response are specified in subclause 5.1.2.2.1 of TS 32.290 [57].
Table B.2.4.1-1 describes the use of these messages for 5G VN group management charging.
Table B.2.4.1-1: 5G LAN VN group management messages reference table
|
Message |
Source |
Destination |
|
Charging Data Request |
CEF/NEF |
CHF |
|
Charging Data Response |
CHF |
CEF/NEF |
Table B.2.4.1-2 illustrates the basic structure of a Charging Data Request message from the CEF as used for 5G VN group management charging.
Table B.2.4.1-2: 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. |
|
NF Consumer Identification |
OC |
Described in TS 32.290 [57] |
|
Charging Identifier |
– |
This field is not applicable. |
|
Invocation Timestamp |
M |
Described in TS 32.290 [57] |
|
Invocation Sequence Number |
M |
Described in TS 32.290 [57] |
|
One-time Event |
OC |
Described in TS 32.290 [57] |
|
One-time Event Type |
OC |
Described in TS 32.290 [57] |
|
Retransmission Indicator |
OC |
Described in TS 32.290 [57] |
|
Notify URI |
– |
This field is not applicable. |
|
Supported Features |
OC |
Described in TS 32.290 [57] |
|
Service Specification Information |
OC |
Described in TS 32.290 [57] |
|
Triggers |
OC |
This field holds the specific triggers described in clause B.2.3.2.1. |
|
Multiple Unit Usage |
– |
This field is not applicable. |
|
5G VNGM Charging Information |
OM |
This field is mapped to the NEF API Charging information defined in clause 6.3 for 5G VN group management charging |
Table B.2.4.1-3 illustrates the basic structure of a Charging Data Response message from the CHF to CEF as used for 5G VN group management charging.
Table B.2.4.1-3: 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 |
M |
Described in TS 32.290 [57] |
|
Session Failover |
– |
This field is not applicable. |
|
Supported Features |
OC |
Described in TS 32.290 [57] |
|
Triggers |
– |
This field is not applicable. |
|
Multiple Unit Information |
– |
This field is not applicable. |
Details of the Ga message contents are specified in TS 32.295 [54].
The following table B.2.4.1-4 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. Full definitions of the CDR parameters, sorted by the name in alphabetical order, are provided in TS 32.298 [51].
Table B.2.4.1-4 5G VN group management charging 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 CEF id. |
|
Subscriber Identifier |
– |
This field is not applicable. |
|
NF Consumer Information |
M |
This field holds the information of the entity that used the charging service (i.e. NF consumer (CTF), CEF). |
|
NF Functionality |
M |
This field contains the function of the entity: Service Producer (CTF) or CEF |
|
NF Name |
OC |
This field holds the name of the entity. |
|
NF Address |
OC |
This field holds the IP Address of the entity |
|
NF PLMN ID |
OC |
This field holds the PLMN identifier (MCC MNC) of the entity. |
|
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] |
|
Diagnostics |
OM |
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] |
|
5G VNGM Charging Information |
OM |
This field is mapped to the NEF API Charging information defined in clause 6.3 for 5G VN group management charging. |
B.2.4.2 Definition of 5G VN group management charging information
The 5G VN Group Management Charging information is mapped to in the "NEF API Charging Information" in the table B.2.4.2-1.
Table B.2.4.2-1: Structure of NEF API Charging Information for 5G VNGM Charging Information
|
5G VNGM Charging Information (Mapped to NEF API Charging Information) |
Category |
Description |
|---|---|---|
|
External Group Identifier |
OC |
This field contains the External Group ID associated to the provided Internal Group ID |
|
Internal Group Identifier |
OC |
This field contain the Internal Group ID associated to the provided External Group ID. |
|
External Individual Identifier |
OC |
The list of the UE identifiers in the 5G VN group. |
|
API Direction |
– |
This fiels is not applicable |
|
API Target Network Function |
– |
This fiels is not applicable |
|
API Result Code |
– |
This fiels is not applicable |
|
API Name |
– |
This fiels is not applicable |
|
API Reference |
– |
This fiels is not applicable |
|
API Content |
OC |
The API content includes the 5G VN group data, including the Single Nssai DNN and PDU Session Types. |
B.2.4.3 Detailed message format for converged charging
The following clause specifies per Operation Type the charging data that are sent by CEF for 5G VN group management 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 B.2.4.3-1 defines the basic structure of the supported fields in the Charging Data Request message for CEF converged charging.
Table B.2.4.3-1: Supported fields in Charging Data Request message
|
Information Element |
Analytics and Performance |
CEF |
|---|---|---|
|
Supported Operation Types |
E |
|
|
Session Identifier |
E |
|
|
Subscriber Identifier |
– |
|
|
NF Consumer Identification |
E |
|
|
Charging Identifier |
– |
|
|
Invocation Timestamp |
E |
|
|
Invocation Sequence Number |
E |
|
|
One-time Event |
E |
|
|
One-time Event Type |
E |
|
|
Retransmission Indicator |
E |
|
|
Notify URI |
– |
|
|
Supported Features |
E |
|
|
Service Specification Information |
E |
|
|
Triggers |
E |
|
|
Multiple Unit Usage |
– |
|
|
5G VNGM Charging Information |
E |
|
Table B.2.4.3-2 defines the basic structure of the supported fields in the Charging Data Response message for CEF converged charging.
Table B.2.4.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 |
E |
|
|
Session Failover |
– |
|
|
Supported Features |
E |
|
|
Triggers |
E |
|
|
Multiple Unit information |
– |
|
B.2.5 Bindings for 5G VN group management converged charging
This mapping between the Information Elements, resource attributes and CHF CDR parameters for 5G VN group management and communication converged charging is described in clause 7 of TS 32.291 [51].
Annex C (informative):
Change history
|
Change history |
|||||||
|
Date |
Meeting |
Tdoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2018-06 |
SA#80 |
Upgrade to change control version |
15.0.0 |
||||
|
2018-12 |
SA#82 |
SP-181041 |
0001 |
1 |
F |
Correction on the TTRL and TLTRL |
15.1.0 |
|
2019-03 |
SA#83 |
SP-190114 |
0002 |
1 |
B |
Add convergent charging architecture |
16.0.0 |
|
2019-03 |
SA#83 |
SP-190114 |
0003 |
1 |
B |
Add basic principles for convergent charging |
16.0.0 |
|
2019-03 |
SA#83 |
SP-190114 |
0004 |
1 |
B |
Add message flows for converged charging |
16.0.0 |
|
2019-03 |
SA#83 |
SP-190114 |
0005 |
1 |
B |
Adding CDR generation and handling for converged charging |
16.0.0 |
|
2019-06 |
SA#84 |
SP-190380 |
0006 |
1 |
B |
Addition of NEF charging data for Converged Charging |
16.1.0 |
|
2019-06 |
SA#84 |
SP-190380 |
0007 |
1 |
B |
Adding NEF API Information for charging |
16.1.0 |
|
2019-09 |
SA#85 |
SP-190756 |
0009 |
1 |
B |
Update of NEF API Charging Information |
16.2.0 |
|
2019-09 |
SA#85 |
SP-190756 |
0010 |
1 |
B |
Addition of detailed message format for converged charging |
16.2.0 |
|
2020-07 |
SA#88-E |
SP-200484 |
0011 |
1 |
F |
Add the Retransmission Indicator |
16.3.0 |
|
2020-07 |
SA#88-E |
SP-200484 |
0012 |
1 |
F |
Correct the message content for NEF charging |
16.3.0 |
|
2021-03 |
SA#91e |
SP-210159 |
0013 |
– |
F |
Correction on applicable scenarios and flows |
16.4.0 |
|
2021-03 |
SA#91e |
SP-210159 |
0014 |
1 |
F |
Correction on different identities |
16.4.0 |
|
2021-03 |
SA#91e |
SP-210159 |
0015 |
1 |
F |
Correction on Multiple Unit Usage |
16.4.0 |
|
2021-03 |
SA#91e |
SP-210159 |
0016 |
– |
F |
Correction on binding description |
16.4.0 |
|
2021-06 |
SA#92e |
SP-210407 |
0017 |
1 |
C |
Correction on Reference Points |
17.0.0 |
|
2022-06 |
SA#96 |
SP-220518 |
0018 |
1 |
B |
Addition of the 5G VN group management Charging Architecture |
17.1.0 |
|
2022-06 |
SA#96 |
SP-220518 |
0019 |
1 |
B |
Addition of the 5G VN group management Charging Principles |
17.1.0 |
|
2022-06 |
SA#96 |
SP-220518 |
0020 |
1 |
B |
Addition of the 5G VN group management Charging |
17.1.0 |
|
2022-06 |
SA#96 |
SP-220565 |
0022 |
1 |
A |
Correction on the NEF API Charging information |
17.1.0 |
|
2022-06 |
SA#97e |
SP-220867 |
0024 |
– |
F |
Correction on the 5G LAN VN management converged charging |
17.2.0 |
|
2022-06 |
SA#98e |
SP-221192 |
0026 |
1 |
A |
Correction on the Triggers for the NEF |
17.3.0 |
|
2022-06 |
SA#98e |
SP-221192 |
0028 |
1 |
A |
Correction on the notifyURI for NEF Charging |
17.3.0 |