B.1 General
32.2553GPP5G data connectivity domain chargingCharging managementRelease 17Stage 2Telecommunication managementTS
This clause specifies the EPS and 5GS interworking.
B.2 Definition of charging information for interworking
B.2.1 Data description for interworking with EPC
B.2.1.1 Message contents
The Charging message as described in clause 6.1.1 shall apply to the PGW-C+SMF for interworking with EPC scenario.
When UE is connected to PGW-C+SMF via EPC and interworking with 5GS is supported, the information and mechanism included in clause 6.1.1 and TS 32.290[57] is supported.
B.2.1.2 Ga message contents
B.2.1.3 CDR description on the Bd interface
The CDR description defined in clause 6.1.3.2 with Roaming QBC information per clause B.2.2.1.1 is used for interworking with EPC scenario.
B.2.2 Interworking charging specific parameters
B.2.2.1 Definition of Interworking charging information
B.2.2.1.1 Message content
The charging information defined in clause 6.2.1 is used for interworking with EPC scenario.
The specific information used for PS charging when UE is connected to P-GW+SMF via EPC is provided within the Charging Data Request message, as defined in clause 6.1.1.2, with the following difference:
Table B.2.2.1.1-1: Charging Data Request message contents
|
Information Element |
Category |
Description |
|
Roaming QBC information |
OC |
This field holds the QBC information specific to 5GC interworking with EPC as defined in clause B.2.2.1.2. This field is applicable in both non-roaming and roaming Home Routed scenario. |
B.2.2.1.2 Roaming QBC information
Roaming QBC information specific to 5GC interworking with EPC when UE is connected to P-GW+SMF via EPC is defined in table B.2.2.1.2-1:
Table B.2.2.1.2-1: Roaming QBC information
|
Information Element |
Category |
Description |
|
MultipleQFIcontainer |
OC |
This field holds the containers associated to a charging condition change on an IP-CAN bearer. This is included when triggers conditions are met (Qos change, tariff time change …). It may have multiple occurences. This field is applicable for both non-roaming and roaming Home Routed scenario |
|
Triggers |
OC |
Described in table 6.2.1.4.1 |
|
Trigger Timestamp |
OC |
Described in table 6.2.1.4.1 |
|
Uplink Volume |
OC |
Described in table 6.2.1.4.1 |
|
Downlink Volume |
OC |
Described in table 6.2.1.4.1 |
|
Local Sequence Number |
OC |
Described in table 6.2.1.4.1 |
|
QFI Container information |
OC |
This field holds the data container information defined in clause B.2.2.1.3 |
B.2.2.1.3 QFI Container Information
QFI Container Information specific to 5GC interworking with EPC when UE is connected to P-GW+SMF via EPC is defined in table B.2.2.1.3-1:
Table B.2.2.1.3-1: QFI Container Information
|
Information Element |
Category |
Description |
|---|---|---|
|
QoS Information |
OC |
Described in table 6.2.1.5.1 |
|
QoS Characteristics |
OC |
Described in table 6.2.1.5.1 |
|
User Location Information |
OC |
Described in table 6.2.1.5.1 |
|
Presence Reporting Area Information |
OC |
Described in table 6.2.1.5.1 |
|
RAT Type |
OC |
Described in table 6.2.1.5.1 |
|
Report Time |
M |
Described in table 6.2.1.5.1 |
|
3GPP PS Data Off Status |
OC |
Described in table 6.2.1.5.1 |
|
EPS bearer Charging Id |
OM |
This field holds the Charging Id associated to the bearer the QoS flow is mapped to. |
|
Diagnostics |
OM |
This field holds a more detailed reason for the release of the IP-CAN bearer, when a single cause is applicable. |
|
Enhanced Diagnostics |
OC |
This field holds a more detailed reason for the release of the IP-CAN bearer, when a set of causes is applicable. |
B.2.2.2 Detailed message format for Interworking charging
The message format defined in clause 6.2.2 is used for interworking with EPC scenario.
The supported fields in table 6.2.2.1 for the converged charging message shall apply to the P-GW+SMF for the applicable fields, with the difference that SMF is replaced by P-GW+SMF.
The table B.2.2.2-1 describes the mapping between the Multiple QFI Container Information Elements defined for interworking and Traffic data volumes CDR parameters defined in 32.298 [51] for EPC.
Table B.2.2.2-1: MultipleQFI Container for Interworking mapping to EPC Traffic data volumes
|
Information Element for 5G Data connectivity |
Information Element for Interworking |
Corresponding to 32.298 [51] |
|
Multiple QFI Container |
Yes |
Traffic data volumes |
|
Triggers |
Yes |
Change condition |
|
Trigger Timestamp |
Yes |
Change Time |
|
Time |
No |
– |
|
Total Volume |
No |
– |
|
Uplink Volume |
Yes |
Data Volume Uplink |
|
Downlink Volume |
Yes |
Data Volume Downlink |
|
Local Sequence Number |
yes |
– |
|
QFI Container Information |
Yes |
– |
|
QFI |
No |
– |
|
Time of First Usage |
No |
– |
|
Time of Last Usage |
No |
– |
|
QoS Information |
Yes |
EPC QoS Information |
|
User Location Information |
Yes |
User Location Information |
|
UE Time Zone |
No |
– |
|
Presence Reporting Area Information |
Yes |
Presence Reporting Area Status |
|
RAT Type |
Yes |
RAT Type |
|
Serving Network Function ID |
No |
– |
|
3GPP PS Data Off Status |
yes |
3GPP PS Data Off Status |
|
– |
3GPP Charging Id |
Charging Id |
|
– |
Enhanced Diagnostics |
Enhanced Diagnostics |
|
– |
Diagnostics |
Diagnostics |
|
– |
No |
UWAN User Location Information |
|
– |
No |
User CSG information |
|
– |
No |
Access Availability Change Reason |
|
– |
No |
Related Change of Charging Condition |
|
– |
No |
CP CIoT EPS optimisation indicator |
|
– |
No |
Serving PLMN Rate Control |
B.2.2.3 Formal Interworking charging parameter description
The CHF CDR parameters and resources attributes defined in clause 6.2.3 is used for interworking with EPC scenario.
Annex C (normative):
Support of GERAN/UTRAN access