6 Definition of charging information
32.2773GPPCharging managementProximity-based Services (ProSe) chargingRelease 17Telecommunication managementTS
6.1 Data description for ProSe offline charging
6.1.1 Rf message contents
6.1.1.1 General
The ProSe Offline Charging uses the Charging Data Transfer messages Charging Data Request and Charging Data Response defined in TS 32.299 [50].
The Charging Data Request can be of type event and includes all charging information. The Charging Data Response is an acknowledgement of the Charging Data Request.
Table 6.1.1.1.1 describes the use of these messages for offline charging.
Table 6.1.1.1.1: Offline charging messages reference table
Message |
Source |
Destination |
Charging Data Request |
ProSe Function |
CDF |
Charging Data Response |
CDF |
ProSe Function |
This clause describes the different fields used in the Charging Data messages and the category in the tables are 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 ProSe Function as used for ProSe offline charging.
Table 6.1.1.2.1: Charging Data Request message contents
Information Element |
Category |
Description |
---|---|---|
Session Identifier |
M |
Described in TS 32.299 [50] |
Originator Host |
M |
Described in TS 32.299 [50] |
Originator Domain |
M |
Described in TS 32.299 [50] |
Destination Domain |
M |
Described in TS 32.299 [50] |
Operation Type |
M |
Described in TS 32.299 [50] |
Operation Number |
M |
Described in TS 32.299 [50] |
Operation Identifier |
OC |
Described in TS 32.299 [50] |
User Name |
OC |
Described in TS 32.299 [50] |
Destination Host |
OC |
Described in TS 32.299 [50] |
Operation Interval |
OC |
Described in TS 32.299 [50] |
Origination State |
OC |
Described in TS 32.299 [50] |
Origination Timestamp |
OC |
Described in TS 32.299 [50] |
Proxy Information |
OC |
Described in TS 32.299 [50] |
Route Information |
OC |
Described in TS 32.299 [50] |
Operation Token |
OM |
This field identifies the Proximity-based Services. |
Service Information |
OM |
This field holds the ProSe specific information described in clause 6.3. |
NOTE: Detailed descriptions of the information elements are provided in TS 32.299 [50].
6.1.1.3 Charging Data Response message
Table 6.1.1.3.1 illustrates the basic structure of a Charging Data Response message as used for the ProSe function.
Table 6.1.1.3.1: Charging Data Response message contents
Information Element |
Category |
Description |
---|---|---|
Session Identifier |
M |
Described in TS 32.299 [50] |
Operation Result |
M |
Described in TS 32.299 [50] |
Originator Host |
M |
Described in TS 32.299 [50] |
Originator Domain |
M |
Described in TS 32.299 [50] |
Operation Type |
M |
Described in TS 32.299 [50] |
Operation Number |
OC |
Described in TS 32.299 [50] |
Operation Identifier |
OC |
Described in TS 32.299 [50] |
Operation Interval |
OC |
Described in TS 32.299 [50] |
Error Reporting Host |
OC |
Described in TS 32.299 [50] |
Origination State |
OC |
Described in TS 32.299 [50] |
Origination Timestamp |
OC |
Described in TS 32.299 [50] |
Proxy Information |
OC |
Described in TS 32.299 [50] |
NOTE: Detailed descriptions of the information elements are provided in TS 32.299 [50].
6.1.2 Ga message contents
Refer to clause 5.2.4 for further information.
6.1.3 CDR description on the Bx interface
6.1.3.1 General
The following standard CDR content and format are considered:
– PF-DD-CDR generated based on ProSe Direct Discovery information from the ProSe function;
– PF-ED-CDR generated based on ProSe EPC-level Discovery from the ProSe function.
– PF-DC-CDR generated based on ProSe Direct Communication from the ProSe function.
For each of the CDR types, a parameter table, which gives a short description of the parameters, is provided. The category in the tables are used according to the charging data configuration defined in clause 5.4 of TS 32.240 [1].
6.1.3.2 Direct Discovery charging data in ProSe Function (PF-DD-CDR)
If the collection of CDR data is enabled then the charging data specified in table 6.1.3.2.1 shall be available for direct discovery request.
Table 6.1.3.2.1: ProSe Function Direct Discovery data (PF-DD-CDR)
Field |
Category |
Description |
---|---|---|
Record Type |
M |
ProSe Direct Discovery record. |
Retransmission |
Oc |
This parameter, when present, indicates that information from retransmitted Accounting Requests has been used in this CDR. |
Served IMSI |
C |
IMSI of the served party. |
Announcing PLMN ID |
OC |
PLMN identity of the serving PLMN which signalled the carrier frequency, when this serving PLMN is not the HPLMN nor the VPLMN, if available. |
Announcing UE HPLMN Identifier |
OM |
PLMN identity of Announcing UE HPLMN. |
Announcing UE VPLMN Identifier |
OC |
PLMN identity of Announcing UE VPLMN. |
Monitoring UE HPLMN Identifier |
OC |
PLMN identity of monitoring UE HPLMN. |
Monitoring UE VPLMN Identifier |
OC |
PLMN identity of monitoring UE VPLMN. |
Discoverer UE HPLMN Identifier |
OM |
PLMN identity of Discoverer UE HPLMN. |
Discoverer UE VPLMN Identifier |
OC |
PLMN identity of Discoverer UE VPLMN. |
Discoveree UE HPLMN Identifier |
OC |
PLMN identity of Discoveree UE HPLMN. |
Discoveree UE VPLMN Identifier |
OC |
PLMN identity of Discoveree UE VPLMN. |
Monitored PLMN Identifier |
OC |
Monitored PLMN ID in Match_Report request, as defined in TS23.303 [238] clause 5.3.4. It corresponds to the Announcing UE VPLMN Identifier when roaming and Announcing UE HPLMN Identifier when non-roaming. |
Role of ProSe Function |
OM |
This field indicates the CDR resource ProSe Function resides in which PLMN, i.e. in HPLMN, VPLMN or local PLMN. |
ProSe Application ID |
Oc |
The identities used for ProSe Direct Discovery, identifying application related information for the ProSe-enabled UE. (see note) |
Application ID |
Oc |
A globally unique identifier identifying a specific 3rd party application. |
ProSe Event Type |
Oc |
This IE holds the event which triggers the charging message delivery, e.g. open Announcing, open Monitoringopen Match Report or, restricted Announcing. |
Direct Discovery Model |
Oc |
model of the Direct Discovery used by the UE, e.g. Model A, or Model B. |
Node ID |
Oc |
The identifier of the ProSe Function. |
ProSe Function IP Address |
Oc |
The IP address of the ProSe Function. |
ProSe Function ID |
Oc |
The FQDN that identifies the ProSe Function. |
Validity Period |
Oc |
Time interval during which user is authorized for using ProSe Direct Discovery functionality (e.g. announcing, monitoring, match reporting). |
Role of UE |
Oc |
Role of the UE using ProSe, e.g. Announcing UE, Monitoring UE, Discoveree UE, Discoverer UE. |
ProSe Request Timestamp |
Oc |
The time when ProSe Request is received from UE. |
PC3 Control Protocol Cause |
Oc |
This field holds the particular reason why a DISCOVERY_REQUEST or Match_Report messages from the UE have been rejected by the ProSe Function. |
Monitoring UE Identifier |
Oc |
Identifier of the party who initiate monitor/match report, i.e. IMSI, which corresponds to UE Identifier parameter in monitor/match report request, as defined in TS 23.303 [238]. |
Charging characteristics |
M |
The Charging Characteristics applied to the ProSe direct discovery. |
Charging Characteristics Selection Mode |
OM |
Holds information about how Charging Characteristics were selected. |
Record Extensions |
Oc |
A set of network operator/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. |
PC5 Radio Technology |
OM |
The PC5 radio technology used by UE for ProSe Direct Discovery. |
Note: For the CDR generated for announcing UE in match report event, it holds the ProSe application id name. |
6.1.3.3 ProSe EPC-level Discovery charging data in ProSe Function (PF-ED-CDR)
If enabled, a ProSe EPC-level Discovery record shall be produced for each EPC-level discovery request for a specific user received from a ProSe enabled UE. Renewal requests for a specific user are captured in the same CDR as the initial request. The fields in the record are specified in table 6.1.3.3.1.
Table 6.1.3.3.1: ProSe Function EPC-level Discovery data (PF-ED-CDR)
Field |
Category |
Description |
---|---|---|
Record Type |
M |
ProSe Function EPC-level Discovery record. |
Retransmission |
Oc |
This parameter, when present, indicates that information from retransmitted Accounting Requests has been used in this CDR. |
Served IMSI |
C |
IMSI of the served party. |
ProSe Function PLMN Identifier |
OC |
PLMN identity of ProSe function. |
Application ID |
Oc |
A globally unique identifier identifying a specific 3rd party application. |
ProSe Function ID |
Oc |
The FQDN that identifies a ProSe Function. |
ProSe Function IP Address |
Oc |
The IP address of the ProSe Function. |
Role of UE |
Oc |
role of the UE using ProSe, e.g. requestor UE, requested UE |
ProSe Request Timestamp |
Oc |
The time when ProSe Request is received from UE. |
PC3 EPC Control Protocol Cause |
Oc |
This field holds the particular reason why a Proximity request messages from the UE have been rejected by the ProSe Function. |
Requestor Application Layer User ID |
Oc |
The user identifier designated in 3rd party application for the user who initiate EPC-level ProSe discovery request. |
WLAN Link Layer ID |
Oc |
This field holds WLAN Link Layer ID. |
Requestor EPC ProSe User ID |
Oc |
The identifier generated in ProSe Function for UE who initiate EPC-level ProSe discovery request. |
Requested Application Layer User ID |
Oc |
The user identifier designated in 3rd party application for the user who is targeted in proximity request. |
Requested PLMN Identifier |
Oc |
The PLMN identifier of the user who is targeted in proximity request. |
Time Window |
Oc |
The time interval in minutes during which the first proximity request is valid. |
Range Class |
Oc |
A range class for the first proximity request. |
UE Location |
Oc |
The UE location with the best known accuracy (e.g. Cell ID or geo-location coordinates) at the time fo the first proximity request.. |
Proximity Request Renewal Info Block List |
Oc |
This is a list of information blocks that are added by each of the Proximity renewal Request messages captured in the CDR. The information block contains information of the renewal request, e.g. timestamp, time window, range class, and UE location. The definition of the information block is in table 6.1.3.3.2. |
Proximity Alert Indication |
Oc |
Indication of whether proximity alert has been sent before proximity request cancellation. |
Proximity Alert Timestamp |
Oc |
The time stamp when proximity alert is sent, to indicate two UEs are in proximity. |
Proximity Cancellation Timestamp |
Oc |
The time stamp when proximity request cancellation is requested. |
Reason for Cancellation |
Oc |
The reason for cancellation of an EPC-level discovery request i.e. proximity alerted, time expired with no renewal, requestor cancellation. |
Charging characteristics |
M |
The Charging Characteristics applied to the ProSe EPC-Level discovery. |
Charging Characteristics Selection Mode |
OM |
Holds information about how Charging Characteristics were selected. |
Cause for Record Closing |
M |
The reason for the release of record from this ProSe Function. |
Record Extensions |
Oc |
A set of network operator/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. |
Table 6.1.3.3.2: ProSe Function EPC-level Discovery Proximity Request Renewal Info Block
Field |
Category |
Description |
---|---|---|
ProSe Request Timestamp |
Oc |
The time when the proximity renewal request is received from UE. |
Time Window |
Oc |
The time interval in minutes during which the proximity renewal request is valid. |
Range Class |
Oc |
A range class for the proximity renewal request. |
UE Location |
Oc |
The UE location with the best known accuracy (e.g. Cell ID or geo-location coordinates) at the time fo the proximity renewal request. |
6.1.3.4 Direct communication charging data in ProSe Function (PF-DC-CDR)
If the collection of CDR data is enabled then the charging data specified in table 6.1.3.4.1 shall be available for Direct Communication request.
Table 6.1.3.4.1: ProSe Function Direct Communication data (PF-DC-CDR)
Field |
Category |
Description |
---|---|---|
Record Type |
M |
ProSe Direct Communication record. |
Retransmission |
Oc |
This parameter, when present, indicates that information from retransmitted Charging Data Request has been used in this CDR. |
Served IMSI |
C |
IMSI of the served party. |
ProSe Function PLMN Identifier |
OM |
PLMN identity of HPLMN ProSe function. |
Node ID |
Oc |
The identifier of the ProSe Function. |
ProSe Function IP Address |
Oc |
The IP address of the ProSe Function. |
ProSe Function ID |
Oc |
The FQDN that identifies the ProSe Function. |
Charging characteristics |
M |
The Charging Characteristics applied to the ProSe group communication. |
Charging Characteristics Selection Mode |
OM |
Holds information about how Charging Characteristics were selected. |
Record Opening Time |
M |
Time stamp when the CDR is open. |
Cause for Record Closing |
M |
The reason for the closing of record from this ProSe Function. |
List of Coverage Info |
Oc |
A list of coverage status changes with time stamps. When in coverage, additionally includes list of location changes (i.e., ECGI change) and time stamps. |
List of Radio Parameter Set Info |
Oc |
A list of radio parameter sets configured in the UE for direct communication use. Each set has an associated time stamp of when it became active. |
ProSe UE ID |
Oc |
A link layer identifier assigned by the EPS that uniquely represents the UE in the context of ProSe Direct Communication. |
Source IP address |
Oc |
The IP address UE used as source address for performing ProSe Direct Communication , including ProSe one-to-many, ProSe one-to-one Communication and via ProSe UE-to-Network Relay. |
Target IP address |
Oc |
The IP unicast address target UE used for non-relay ProSe Direct one-to-one Communication. |
Relay IP address |
Oc |
The IP address UE used as ProSe UE-to-Network Relay UE address for performing ProSe Direct Communication via UE-to-Network Relay. |
ProSe UE-to-Network Relay UE ID |
Oc |
A link layer identifier that uniquely represents the ProSe UE-to-Network Relay UE in the context of ProSe Direct Communication via UE-to-Network Relay. |
ProSe Layer-2 Group ID |
Oc |
The identifier of a ProSe communication group, uniquely represents a specific one-to-many ProSe Direct Communication and is included in CDRs for each participantes in the specific group. |
ProSe Target Layer-2 ID |
Oc |
The identifier of target UE, uniquely represents a specific one-to-one ProSe Direct Communication. |
ProSe Group IP multicast address |
Oc |
The IP multicast address to be used for performing ProSe Direct Communication. |
Time of First Transmission |
Oc |
Time when collection of transmission data is started for the group in this CDR, i.e., the first one-to-many direct communication transmission started. |
Time of First Reception |
Oc |
Time when collection of reception data is started for the group in this CDR, i.e., the first one-to-many direct communication reception started. |
List of Transmitters |
Oc |
A list of transmitters detected for the group. The information stored consists of the source IP address and the ProSe UE ID for each transmitter. |
List of Transmission Data |
OM |
A list of changes in trigger conditions (e.g. change of cell, go out of coverage, come back to coverage, etc.) for a specific ProSe group communication. Each change is time stamped. Trigger condition is used to categorize transmitted data volumes, such as per coverage status duration. |
List of Reception Data |
Oc |
A list of changes in trigger conditions (e.g. change of cell, go out of coverage, come back to coverage, etc.) for a specific ProSe group communication. Each change is time stamped. Trigger condition is used to categorize received data volumes, such as per coverage status duration. |
List of Application Specific Data |
Oc |
A list of data blocks provided by the application in the UE. The content of each block is application-specific. The Application Specific Data is not related to any specific group. When received from the UE, it shall be added to all open group CDRs. The content of the Application Specific Data for a particular application should clearly identify to which group(s) the information applies and uniquely identify chargeable events in order for the billing domain to properly charge this information and avoid duplicate charging. |
Record Extensions |
Oc |
A set of network operator/manufacturer specific extensions to the record. Conditioned upon the existence of an extension. |
The components of the Direct Communication Transmission and Reception Data Containers are defined in following table.
Table 6.1.3.4.2: Structure of the Direct Communication Transmission and Reception Data Containers
Field |
Category |
Description |
---|---|---|
Local Sequence Number |
Oc |
The sequence number of the Direct Communication data container, which is increased by 1 for each container closed |
Change Time |
Oc |
The time when the container is closed and reported due to ProSe charging condition change. |
Coverage status |
Oc |
Whether UE is served by E-UTRAN or not, i.e. in coverage, out of coverage. |
UE Location |
Oc |
The location of the UE, e.g. ECGI |
Data Volume Transmitted |
Oc |
Amount of data transmitted by UE, only applicable in the Transmission Data Container. |
Data Volume Received |
Oc |
Amount of data received by UE, only applicable in the Reception Data Container. |
Change Condition |
Oc |
ProSe specific reason for closing the container, e.g. change of Cell, go out of coverage, come back to coverage. |
VPLMN Identifier |
Oc |
Indentifier of PLMN which UE visits. |
Usage information report sequence number |
Oc |
The sequence number of usage information report, which is used to generate the container. |
Radio Resources Indicator |
Oc |
Identifies whether the operator-provided radio resources or the configured radio resources were used for ProSe direct communication. |
Radio Frequency |
Oc |
Identifies the radio frequency used for ProSe direct communication. |
6.2 Data description for ProSe online charging
6.2.1 Ro message contents
6.2.1.1 General
The ProSe Online Charging uses the Debit / Reserve Units Request and Debit / Reserve Units Response messages defined in TS 32.299 [50].
Table 6.2.1.1.1 describes the use of these messages for online charging.
Table 6.2.1.1.1: Online charging messages reference table
Message |
Source |
Destination |
Debit / Reserve Units Request |
ProSe Function |
OCS |
Debit / Reserve Units Response |
OCS |
ProSe Function |
The structure of the Debit / Reserve Units Request and Debit / Reserve Units Reponse messages defined in the following clauses. The category in the tables are used according to the charging data configuration defined in clause 5.4 of TS 32.240 [1].
6.2.1.2 Debit / Reserve Units Request message
Table 6.2.1.2.1 illustrates the basic structure of a Debit / Reserve Units Request message from the ProSe Function as used for ProSe online charging.
Table 6.2.1.2.1: Debit / Reserve Units Request message contents
Information Element |
Category |
Description |
---|---|---|
Session Identifier |
M |
Described in TS 32.299 [50] |
Originator Host |
M |
Described in TS 32.299 [50] |
Originator Domain |
M |
Described in TS 32.299 [50] |
Destination Domain |
M |
Described in TS 32.299 [50] |
Operation Identifier |
M |
Described in TS 32.299 [50] |
Operation Token |
M |
Described in TS 32.299 [50] |
Operation Type |
M |
Described in TS 32.299 [50] |
Operation Number |
M |
Described in TS 32.299 [50] |
Destination Host |
OC |
Described in TS 32.299 [50] |
User Name |
OC |
Described in TS 32.299 [50] |
Origination State |
OC |
Described in TS 32.299 [50] |
Origination Timestamp |
OC |
Described in TS 32.299 [50] |
Subscriber Identifier |
OM |
Described in TS 32.299 [50]. The IMSI and MSISDN shall be included, if available. |
Termination Cause |
OC |
Described in TS 32.299 [50] |
Requested Action |
OC |
Described in TS 32.299 [50] |
Multiple Operation |
OM |
Described in TS 32.299 [50] |
Multiple Unit Operation |
OC |
Described in TS 32.299 [50] |
Operation Correlation Identifier |
OC |
Described in TS 32.299 [50] |
Subscriber Equipment Number |
OC |
Described in TS 32.299 [50] |
Proxy Information |
OC |
Described in TS 32.299 [50] |
Route Information |
OC |
Described in TS 32.299 [50] |
Service Information |
OM |
This field holds the ProSe specific information described in clause 6.3 |
NOTE: Detailed descriptions of the information elements are provided in TS 32.299 [50].
6.2.1.3 Debit / Reserve Units Response message
Table 6.2.1.3.1 illustrates the basic structure of a Debit / Reserve Units Response message as used for the ProSe function.
Table 6.2.1.3.1: Debit / Reserve Units Response message contents
Information Element |
Category |
Description |
|
---|---|---|---|
Session Identifier |
M |
Described in TS 32.299 [50] |
|
Operation Result |
M |
Described in TS 32.299 [50] |
|
Originator Host |
M |
Described in TS 32.299 [50] |
|
Originator Domain |
M |
Described in TS 32.299 [50] |
|
Operation Identifier |
M |
Described in TS 32.299 [50] |
|
Operation Type |
M |
Described in TS 32.299 [50] |
|
Operation Number |
M |
Described in TS 32.299 [50] |
|
Operation Failover |
OC |
Described in TS 32.299 [50] |
|
Multiple Unit Operation |
OM |
Described in TS 32.299 [50] |
|
Cost Information |
OC |
Described in TS 32.299 [50] |
|
Low Balance Indication |
OC |
Described in TS 32.299 [50] |
|
Remaining Balance |
OC |
Described in TS 32.299 [50] |
|
Operation Failure Action |
OC |
Described in TS 32.299 [50] |
|
Operation Event Failure Action |
OC |
Described in TS 32.299 [50] |
|
Redirection Host |
OC |
Described in TS 32.299 [50] |
|
Redirection Host Usage |
OC |
Described in TS 32.299 [50] |
|
Redirection Cache Time |
OC |
Described in TS 32.299 [50] |
|
Proxy Information |
OC |
Described in TS 32.299 [50] |
|
Route Information |
OC |
Described in TS 32.299 [50] |
|
Failed Parameter |
OC |
Described in TS 32.299 [50] |
|
Service Information |
OC |
Described in TS 32.299 [50] |
NOTE: Detailed descriptions of the information elements are provided in TS 32.299 [50].
6.2a Data description for ProSe converged charging
6.2a.1 Message contents
6.2a.1.1 General
The Charging Data Request and Charging Data Response are specified in TS 32.290 [55] and include charging information. The Charging Data Request can be of type [Event, Initial, Update, Termination].
Table 6.2a.1.1.1 describes the use of these messages for converged charging.
Table 6.2a.1.1.1: Converged charging messages reference table
Message |
Source |
Destination |
Charging Data Request |
5G DDNMF |
CHF |
Charging Data Response |
CHF |
5G DDNMF |
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.2a.1.2 Structure for the converged charging message formats
6.2a.1.2.1 Charging Data Request message
Table 6.2a.1.2.1.1 illustrates the basic structure of a Charging Data Request message as used for 5G ProSe converged charging.
Table 6.2a.1.2.1.1: Charging Data Request message contents
Information Element |
Category |
Description |
Session Identifier |
OC |
Described in TS 32.290 [55] |
Subscriber Identifier |
OM |
Described in TS 32.290 [55], and holds the identifier of the AF |
NF Consumer Identification |
M |
Described in TS 32.290 [55] |
NF Functionality |
M |
Described in TS 32.290 [55]. |
NF Name |
OC |
Described in TS 32.290 [55]. |
NF Address |
OC |
Described in TS 32.290 [55]. |
NF PLMN ID |
OC |
Described in TS 32.290 [55]. |
Charging Identifier |
OM |
Described in TS 32.290 [55]. |
Invocation Timestamp |
M |
Described in TS 32.290 [55] |
Invocation Sequence Number |
M |
Described in TS 32.290 [55] |
Retransmission Indicator |
OC |
Described in TS 32.290 [55] |
One-time Event |
OC |
This field indicates, if included, that this is a one-time event and that there will be no update or termination. |
One-time Event Type |
OC |
Described in TS 32.290 [55]. |
Notify URI |
OC |
This field contains URI to which notifications are sent by the CHF. The latest received value shall always be used at notifications. |
Supported Features |
OC |
Described in TS 32.290 [55]. |
Service Specification information |
OC |
This field holds the ProSe specific information described in clause 6.x. |
Triggers |
OC |
This field is described in TS 32.290 [55] and holds the ProSe specific triggers described in clause 5.x |
Multiple Unit Usage |
OC |
This field contains the parameters for the quota management request and/or usage reporting. |
Rating Group |
M |
Described in TS 32.290 [55] |
Requested Unit |
OC |
Described in TS 32.290 [55] |
Time |
OC |
Described in TS 32.290 [55] |
Total Volume |
OC |
Described in TS 32.290 [55] |
Uplink Volume |
OC |
Described in TS 32.290 [55] |
Downlink Volume |
OC |
Described in TS 32.290 [55] |
Service Specific Units |
OC |
Described in TS 32.290 [55] |
Used Unit Container |
OC |
Described in TS 32.290 [55] |
Service Identifier |
OC |
Described in TS 32.290 [55] |
Quota management Indicator |
OC |
Described in TS 32.290 [55] |
Triggers |
OC |
Described in TS 32.290 [55] |
PC5 Container Information |
OC |
This field holds the 5G ProSe specific information described in clause 6.3. |
Trigger Timestamp |
OC |
Described in TS 32.290 [55] |
Time |
OC |
Described in TS 32.290 [55] |
Total Volume |
OC |
Described in TS 32.290 [55] |
Uplink Volume |
OC |
Described in TS 32.290 [55] |
Downlink Volume |
OC |
Described in TS 32.290 [55] |
Service Specific Unit |
OC |
Described in TS 32.290 [55] |
Event Time Stamps |
OC |
Described in TS 32.290 [55] |
Local Sequence Number |
OM |
Described in TS 32.290 [55] |
ProSe Information |
OM |
This field holds the 5G ProSe specific information described in clause 6.3. |
6.2a.1.2.2 Charging Data Response message
Table 6.2a.1.2.2.1 illustrates the basic structure of a Charging Data Response message as used for ProSe converged charging.
Table 6.2a.1.2.2.1: Charging Data Response message content
Information Element |
Category |
Description |
Session Identifier |
OC |
Described in TS 32.290 [55] |
Invocation Timestamp |
M |
Described in TS 32.290 [55] |
Invocation Result |
OC |
Described in TS 32.290 [55] |
Invocation Sequence Number |
M |
Described in TS 32.290 [55] |
Session Failover |
OC |
Described in TS 32.290 [55] |
Supported Features |
OC |
Described in TS 32.290 [55] |
Triggers |
OC |
Described in TS 32.290 [55] |
Multiple Unit Information |
OC |
Described in TS 32.290 [55] |
Result Code |
OC |
Described in TS 32.290 [55] |
Rating Group |
OM |
Described in TS 32.290 [55] |
Granted Unit |
OC |
Described in TS 32.290 [55] |
Tariff Time Change |
OC |
Described in TS 32.290 [55] |
Time |
OC |
Described in TS 32.290 [55] |
Total Volume |
OC |
Described in TS 32.290 [55] |
Uplink Volume |
OC |
Described in TS 32.290 [55] |
Downlink Volume |
OC |
Described in TS 32.290 [55] |
Service Specific Units |
OC |
Described in TS 32.290 [55] |
Validity Time |
OC |
Described in TS 32.290 [55] |
Final Unit Indication |
OC |
Described in TS 32.290 [55] |
Time Quota Threshold |
OC |
Described in TS 32.290 [55] |
Volume Quota Threshold |
OC |
Described in TS 32.290 [55] |
Unit Quota Threshold |
OC |
Described in TS 32.290 [55] |
Quota Holding Time |
OC |
Described in TS 32.290 [55] |
Triggers |
OC |
Described in TS 32.290 [55] |
6.3 ProSe charging specific parameters
6.3.1 Definition of ProSe charging information
6.3.1.1 ProSe charging information assignment for Service Information
The components in the Service Information that are used for ProSe charging can be found in table 6.3.1.1.1.
Table 6.3.1.1.1: Service Information used for ProSe charging
Information Element |
Category |
Description |
Service Information |
OM |
This is a structured IE and holds the 3GPP specific parameter as defined in TS 32.299 [50]. |
Subscriber Identifier |
OC |
This IE contains the identification of the user (e.g. IMSI), for offline charging only. |
PS Information |
Oc |
This is a structured IE and hold PS specification parameters. |
Node Id |
Oc |
This IE holds the name of the Node. |
User Location Info |
Oc |
This IE indicates details of where the UE is currently located (e.g. SAI, TAI, RAI, CGI, ECGI or access-specific user location information). |
Change Condition |
Oc |
This field holds the reason for sending Charging Data Request from the ProSe Function. |
Charging Characteristics |
Oc |
The Charging Characteristics applied to the ProSe service. |
Charging Characteristics Selection Mode |
Oc |
Holds information about how Charging Characteristics were selected. |
ProSe Information |
OM |
This is a structured IE and holds the ProSe specific parameters. |
6.3.1.2 Definition of the ProSe Information
ProSe specific charging information is provided within the ProSe Information. The fields of the ProSe Information are indicated with the node (ProSe Function) from which the information is sent.
The detailed structure of the ProSe Information can be found in table 6.3.1.2.1.
Table 6.3.1.2.1: Structure of the ProSe Information
Information Element |
Category |
Description |
---|---|---|
Supported Features |
OC |
This field holds the list of features supported by the ProSe Function, CDF or OCF as defined in clause 6.3.1.x. |
Announcing PLMN ID |
OC |
PLMN identity of the serving PLMN which signalled the carrier frequency, when this serving PLMN is not the HPLMN nor the VPLMN, if available |
Announcing UE HPLMN Identifier |
OM |
PLMN identity of HPLMN for announcing UE. This field holdes PLMN identity of HPLMN for UE requested to be monitored in monitor/match report procedure. |
Announcing UE VPLMN Identifier |
OC |
PLMN identity of VPLMN for announcing UE. This field correspondes to Monitored PLMN ID in match report request, as defined in TS23.303 [238] clause 5.3.4. In this case it’s the same with announcing UE HPLMN Identifier when non-roaming |
Monitoring UE HPLMN Identifier |
OC |
PLMN identity of HPLMN for monitoring UE. |
Monitoring UE VPLMN Identifier |
OC |
PLMN identity of VPLMN for monitoring UE. |
Discoverer UE HPLMN Identifier |
OM |
PLMN identity of Discoverer UE HPLMN. |
Discoverer UE VPLMN Identifier |
OC |
PLMN identity of Discoverer UE VPLMN. |
Discoveree UE HPLMN Identifier |
OC |
PLMN identity of Discoveree UE HPLMN. |
Discoveree UE VPLMN Identifier |
OC |
PLMN identity of Discoveree UE VPLMN. |
Monitored PLMN Identifier |
OC |
Monitored PLMN ID in Match_Report request, as defined in TS23.303 [238] clause 5.3.4. It corresponds to the Announcing UE VPLMN Identifier when roaming and Announcing UE HPLMN Identifier when non-roaming. |
Role of ProSe Function |
OM |
This IE indicates the CDR resource ProSe Function resides in which PLMN, i.e. in HPLMN, VPLMN or local PLMN. |
ProSe Application ID |
Oc |
The identities used for ProSe Direct Discovery, identifying application related information for the ProSe-enabled UE. Note: For the CDR generated for announcing UE in match report event, it holds the ProSe application id name. |
Application ID |
Oc |
A globally unique identifier identifying a specific 3rd party application. |
Application Specific Data |
Oc |
This IE contains a data block provided by the application in the UE. The content of each block is application-specific. |
ProSe functionality |
Oc |
This IE holds the ProSe functionality UE is requesting, e.g. direct discovery, EPC-level discovery, group communication. |
ProSe Event Type |
Oc |
This IE holds the event which triggers the charging message delivery, e.g. open Announcing, open Monitoring, open Match Report, or restricted Match Report. |
Direct Discovery Model |
Oc |
model of the Direct Discovery used by the UE, e.g. Model A, or Model B. |
ProSe Function IP Address |
Oc |
The IP address of the ProSe Function. |
ProSe Function ID |
Oc |
The FQDN that identifies a ProSe Function. |
Validity Period |
Oc |
Time interval during which user is authorized for using ProSe Direct Discovery functionality (e.g. announcing, monitoring, match reporting). |
Role of UE |
Oc |
Role of the UE using ProSe served by the ProSe Function, e.g. Announcing UE, Monitoring UE, requestor UE, requested UE, Disvoerer UE, Discoveree UE. |
ProSe Request Timestamp |
Oc |
The time when ProSe Request is received from UE. |
PC3 Protocol Cause |
Oc |
This IE holds the particular reason why a DISCOVERY_REQUEST or Match_Report messages from the UE have been rejected by the ProSe Function in PC3 interface. |
Monitoring UE Identifier |
Oc |
Identifier of the party who initiate monitor/match report, i.e. IMSI, which corresponds to UE Identifier parameter in monitor/match report request, as defined in TS 23.303 [238]. |
ProSe Function PLMN Identifier |
OC |
PLMN identity of ProSe function. |
Requestor PLMN Identifier |
OC |
The PLMN identifier of the user who initiate proximity request. |
Requestor Application Layer User ID |
Oc |
The user identifier designated in 3rd party application for the user who initiate EPC-level ProSe discovery request. |
WLAN Link Layer ID |
Oc |
This IE holds WLAN Link Layer ID. |
Requestor EPC ProSe User ID |
Oc |
The identifier generated in ProSe Function for UE who initiate EPC-level ProSe discovery request. |
Requested Application Layer User ID |
Oc |
The user identifier designated in 3rd party application for the user who is targeted in proximity request. |
Requested PLMN Identifier |
Oc |
The PLMN identifier of the user who is targeted in proximity request. |
Time Window |
Oc |
The time interval in minutes during which a proximity request is valid. |
Range Class |
Oc |
A range class for a specific proximity request. |
Proximity Alert Indication |
Oc |
Indication of whether proximity alert has been sent before proximity request cancellation. |
Proximity Alert Timestamp |
Oc |
The time stamp when proximity alert is sent, to indicate two UEs are in proximity. |
Proximity Cancellation Timestamp |
Oc |
The time stamp when proximity request cancellation is requested. |
Reason for Cancellation |
Oc |
The reason for cancellation of an EPC-level discovery request i.e. proximity alerted, time expired with no renewal, requestor cancellation. |
PC3 EPC Control Protocol Cause |
Oc |
This field holds the particular reason why a Proximity request messages from the UE have been rejected by the ProSe Function. |
ProSe UE ID |
Oc |
A link layer identifier assigned by the EPS that uniquely represents the UE in the context of ProSe Direct Communication. |
Source IP address |
Oc |
The IP address UE used as source address for performing ProSe direct communication. |
Target IP address |
Oc |
The IP unicast address target UE used for non-relay ProSe direct one-to-one communication. |
Relay IP address |
Oc |
The IP address UE used as ProSe UE-to-Network Relay UE address for performing ProSe direct communication via UE-to-Network Relay. |
ProSe UE-to-Network Relay UE ID |
Oc |
A link layer identifier that uniquely represents the ProSe UE-to-Network Relay UE in the context of ProSe Direct Communication. |
ProSe Layer-2 Group ID |
Oc |
The identifier of a ProSe communication group, uniquely represents a specific one-to-many ProSe Direct Communication and is included in CDRs for each participantes in the specific group. |
ProSe Target Layer-2 ID |
Oc |
The identifier of target UE, uniquely represents a specific one-to-one ProSe Direct Communication. |
ProSe Group IP multicast address |
Oc |
The IP multicast address to be used for performing ProSe direct communication. |
Coverage Info |
Oc |
This IE provides information on the coverage status (i.e., whether the UE is served by E-UTRAN or not) and the time when the coverage status changed to its current state. When in E-UTRAN coverage, additionally includes a list of location changes (i.e., ECGI change) and associated time for each change. |
Radio Parameter Set Info |
Oc |
This IE provides information on a radio parameter set configured in the UE for direct communication use. Each set has an associated time stamp of when it became active. |
Transmitter Info |
Oc |
This IE provides information on a transmitter detected for direct communication. Each transmitter is identified by a source IP address and ProSe UE ID. |
Time of First Transmission |
Oc |
This IE holds the time in UTC format for the first IP packet transmitted. |
Time of First Reception |
Oc |
This IE holds the time in UTC format for the first IP packet received. |
Transmission Data Container |
OC |
This field holds the container associated to a trigger conditions (e.g. change of Cell, go out of coverage, come back to coverage, etc.) on a specific ProSe transmission of group communication. |
Local Sequence Number |
Oc |
The sequence number of the Direct Communication data container, which is increased by 1 for each container closed |
Change Time |
Oc |
The time when the container is closed and reported due to ProSe charging condition change. |
Coverage status |
Oc |
Whether UE is served by E-UTRAN or not, i.e. in coverage, out of coverage. |
User Location Information |
Oc |
The location of the UE, e.g. ECGI |
Data Volume Transmitted |
Oc |
Amount of data transmitted by UE. |
Change Condition |
Oc |
ProSe specific reason for closing the container, e.g. change of Cell, go out of coverage, come back to coverage. |
VPLMN Identifier |
Oc |
Indentifier of PLMN which UE visits. |
Usage information report sequence number |
Oc |
The sequence number of usage information report, which is used to generate the container. |
Radio Resources indicator |
Oc |
This IE identifies whether the operator-provided radio resources or the configured radio resources were used for ProSe direct communication. |
Radio Frequency |
Oc |
This IE identifies the radio frequency used for ProSe direct communication. |
Reception Data Container |
Oc |
This field holds the container associated to a trigger conditions (e.g. change of Cell, go out of coverage, come back to coverage, etc.) on a specific ProSe reception of group communication. |
Local Sequence Number |
Oc |
The sequence number of the Direct Communication data container, which is increased by 1 for each container closed |
Change Time |
Oc |
The time when the container is closed and reported due to ProSe charging condition change. |
Coverage status |
Oc |
Whether UE is served by E-UTRAN or not, i.e. in coverage, out of coverage. |
User Location Information |
Oc |
The location of the UE, e.g. ECGI |
Data Volume Received |
Oc |
Amount of data received by UE. |
Change Condition |
Oc |
ProSe specific reason for closing the container, e.g. change of Cell, go out of coverage, come back to coverage. |
VPLMN Identifier |
Oc |
Indentifier of PLMN which UE visits. |
Usage information report sequence number |
Oc |
The sequence number of usage information report, which is used to generate the container. |
Radio Resources indicator |
Oc |
This IE identifies whether the operator-provided radio resources or the configured radio resources were used for ProSe direct communication. |
Radio Frequency |
Oc |
This IE identifies the radio frequency used for ProSe direct communication. |
PC5 Radio Technology |
OM |
The PC5 radio technology used by UE for ProSe Direct Discovery. |
6.3.1.3 Supported features
The Supported features information that is used for ProSe charging is based on the information defined for the supported features mechanism specified in clause 6.5.10 TS 32.299 [50].
The following table defines the features applicable for the feature lists with a Feature-List-ID of 1.
Table 6.3.1.3: Features of Feature-List-ID 1 used in ProSe charging
Feature bit |
Feature |
Description |
Online/Offline |
0 |
ProSe_WLAN_DD-CH |
This feature indicates the support of PC5 radio technology for WLAN-based Direct Discovery charging |
Both |
Feature bit: The order number of the bit within the Feature-List AVP where the least significant bit is assigned number "0". Feature: A short name that can be used to refer to the bit and to the feature, e.g. "EPS". Feature in this table is always mandatory since it relates to the charging functionality of a network feature. Description: A clear textual description of the feature. |
6.3.2 Formal ProSe charging parameter description
6.3.2.1 ProSe CDR parameters
The detailed definitions, abstract syntax and encoding of the ProSe CDR parameters are specified in TS 32.298 [51].
6.3.2.2 ProSe AVPs
The detailed definitions of ProSe AVPs are specified in TS 32.299 [50].
6.3.3 Detailed message format for offline charging
The following clause specifies per Operation Type the charging data that are sent by ProSe Function for different functionality, i.e. Direct Discovery, EPC_Level Discovery and Direct Communication.
The Operation Types are listed in the following order: S (Start)/I (Interim)/S (Stop)/E (Event). Therefore, when all Operation Types are possible it is marked as SISE. If only some Operation Types are allowed for a node, only the appropriate letters are used (i.e. SIS or E) as indicated in the table heading. The omission of an Operation Type for a particular field is marked with "-" (i.e. SI-E). Also, when an entire field is not allowed in a node the entire cell is marked as "-".
Table 6.3.3.1 illustrates the basic structure of the supported fields in the Charging Data Request message for ProSe offline charging.
Table 6.3.3.1: Supported fields in Charging Data Request message
Information Element |
Service Type |
Direct Discovery |
EPC_Level Discovery |
Direct Communication |
---|---|---|---|---|
Supported Operation Types |
S/I/S/E |
S/I/S/E |
S/I/S/E |
|
Session Identifier |
—E |
SIS- |
SISE |
|
Originator Host |
—E |
SIS- |
SISE |
|
Originator Domain |
—E |
SIS- |
SISE |
|
Destination Domain |
—E |
SIS- |
SISE |
|
Operation Type |
—E |
SIS- |
SISE |
|
Operation Number |
—E |
SIS- |
SISE |
|
Operation Identifier |
—E |
SIS- |
SISE |
|
User Name |
—E |
SIS- |
SISE |
|
Destination Host |
—E |
SIS- |
SISE |
|
Operation Interval |
—E |
SIS- |
SISE |
|
Origination State |
—E |
SIS- |
SISE |
|
Origination Timestamp |
—E |
SIS- |
SISE |
|
Proxy Information |
—E |
SIS- |
SISE |
|
Route Information |
—E |
SIS- |
SISE |
|
Operation Token |
—E |
SIS- |
SISE |
|
Service Information with PS and ProSe Information |
||||
Subscriber Identifier |
—E |
SIS- |
SISE |
|
Node Id |
—E |
SIS- |
SISE |
|
Announcing PLMN ID |
—E |
– |
– |
|
Announcing UE HPLMN Identifier |
—E |
– |
– |
|
Announcing UE VPLMN Identifier |
—E |
– |
– |
|
Monitoring UE HPLMN Identifier |
—E |
– |
– |
|
Monitoring UE VPLMN Identifier |
—E |
– |
– |
|
Discoverer UE HPLMN Identifier |
—E |
– |
– |
|
Discoverer UE VPLMN Identifier |
—E |
– |
– |
|
Discoveree UE HPLMN Identifier |
—E |
– |
– |
|
Discoveree UE VPLMN Identifier |
—E |
– |
– |
|
Role of ProSe Function |
—E |
– |
– |
|
ProSe Application ID |
—E |
– |
– |
|
Application ID |
—E |
SIS- |
– |
|
Application Specific Data |
– |
– |
SISE |
|
ProSe functionality |
—E |
SIS – |
SISE |
|
ProSe Event Type |
—E |
– |
– |
|
Direct Discovery Model |
—E |
– |
– |
|
ProSe Function IP Address |
—E |
SIS- |
SISE |
|
ProSe Function ID |
—E |
SIS- |
SISE |
|
ProSe Function PLMN Identifier |
—E |
SIS- |
SISE |
|
Validity Period |
—E |
– |
– |
|
Role of UE |
—E |
SIS- |
– |
|
ProSe Request Timestamp |
—E |
SIS- |
– |
|
PC3 Control Protocol Cause |
—E |
– |
– |
|
Monitoring UE Identifier |
—E |
– |
– |
|
Monitored PLMN Identifier |
—E |
– |
– |
|
Requestor PLMN Identifier |
– |
SIS- |
– |
|
Requestor Application Layer User ID |
—E |
SIS- |
– |
|
WLAN Link Layer ID |
—E |
SIS- |
– |
|
Requestor EPC ProSe User ID |
—E |
SIS- |
– |
|
Requested Application Layer User ID |
—E |
SIS- |
– |
|
Requested PLMN Identifier |
—E |
SIS- |
– |
|
Time Window |
—E |
SI– |
– |
|
Range Class |
—E |
SI– |
– |
|
User Location Info |
—E |
SI– |
– |
|
Proximity Alert Indication |
—E |
–S- |
– |
|
Proximity Alert Timestamp |
—E |
–S- |
– |
|
Proximity Cancellation Timestamp |
—E |
SIS- |
– |
|
Reason for Cancellation |
—E |
SIS- |
– |
|
PC3 EPC Control Protocol Cause |
– |
–S- |
– |
|
Charging Characteristics |
—E |
SIS- |
SISE |
|
Charging Characteristics Selection Mode |
—E |
SIS- |
SISE |
|
Change Condition |
– |
SIS- |
–SE |
|
ProSe UE ID |
– |
– |
SISE |
|
Source IP address |
– |
– |
SISE |
|
Target IP address |
– |
– |
SISE |
|
Relay IP address |
– |
– |
SISE |
|
ProSe UE-to-Network Relay UE ID |
– |
– |
SISE |
|
ProSe Layer-2 Group ID |
– |
– |
SISE |
|
ProSe Target Layer-2 ID |
– |
– |
SISE |
|
ProSe Group IP multicast address |
– |
– |
SISE |
|
Coverage Info |
– |
– |
SISE |
|
Radio Parameter Set Info |
– |
– |
SISE |
|
Reception Data Container |
– |
– |
SISE |
|
Time of First Reception |
– |
– |
SISE |
|
Time of First Transmission |
– |
– |
SISE |
|
Transmission Data Container |
– |
– |
SISE |
|
Transmitter Info |
– |
– |
SISE |
|
PC5 Radio Technology |
—E |
– |
– |
Table 6.3.3.2 illustrates the basic structure of the supported fields in the Charging Data Responsemessage for ProSe offline charging.
Table 6.3.3.2: Supported fields in Charging Data Response message
Information Element |
Service Type |
Direct Discovery |
EPC_Level Discovery |
Direct Communication |
---|---|---|---|---|
Supported Operation Types |
S/I/S/E |
S/I/S/E |
S/I/S/E |
|
Session Identifier |
—E |
SIS- |
SISE |
|
Operation Result |
—E |
SIS- |
SISE |
|
Originator Host |
—E |
SIS- |
SISE |
|
Originator Domain |
—E |
SIS- |
SISE |
|
Operation Type |
—E |
SIS- |
SISE |
|
Operation Number |
—E |
SIS- |
SISE |
|
Operation Identifier |
—E |
SIS- |
SISE |
|
Operation Interval |
—E |
SIS- |
SISE |
|
Error Reporting Host |
—E |
SIS- |
SISE |
|
Origination State |
—E |
SIS- |
SISE |
|
Origination Timestamp |
—E |
SIS- |
SISE |
|
Proxy Information |
—E |
SIS- |
SISE |
|
Route Information |
—E |
SIS- |
SISE |
6.3.4 Detailed Message Format for online charging
The following table specifies per Operation type the charging data that are sent ProSe Function network element for:
The Operation types are listed in the following order: I [initial]/U [update]/T [terminate]/E [event]. Therefore, when all Operation types are possible it is marked as IUTE. If only some Operation types are allowed for a node, only the appropriate letters are used (i.e. IUT or E) as indicated in the table heading. The omission of an Operation type for a particular field is marked with "-" (i.e. IU-E). Also, when an entire filed is not allowed in a node the entire cell is marked as "-".
Note that not for all structured fields the individual field members are listed in the table. Detailed descriptions of the fields are provided in TS 32.299 [50].
Table 6.3.4.1 illustrates the basic structure of the supported fields in the Debit / Reserve Units Request for ProSe online charging.
Table 6.3.4.1: Supported fields in Debit / Reserve Units Request message
Information Element |
Sevice Type |
Direct Discovery |
EPC_Level Discovery |
---|---|---|---|
Supported Operation Types |
I/U/T/E |
I/U/T/E |
|
Session Identifier |
IUTE |
IUT- |
|
Originator Host |
IUTE |
IUT- |
|
Originator Domain |
IUTE |
IUT- |
|
Destination Domain |
IUTE |
IUT- |
|
Operation Identifier |
IUTE |
IUT- |
|
Operation Token |
IUTE |
IUT- |
|
Operation Type |
IUTE |
IUT- |
|
Operation Number |
IUTE |
IUT- |
|
Destination Host |
IUTE |
IUT- |
|
User Name |
IUTE |
IUT- |
|
Origination State |
IUTE |
IUT- |
|
Origination Timestamp |
IUTE |
IUT- |
|
Subscriber Identifier |
IUTE |
IUT- |
|
Termination Cause |
–TE |
–T- |
|
Requested Action |
IUTE |
IUT- |
|
Multiple Operation |
IU-E |
IU– |
|
Multiple Unit Operation |
IUTE |
IUT- |
|
Operation Correlation Identifier |
IUTE |
IUT- |
|
Subscriber Equipment Number |
IUTE |
IUT- |
|
Proxy Information |
IUTE |
IUT- |
|
Route Information |
IUTE |
IUT- |
|
Service Information |
IUTE |
IUT- |
|
Service Information with PS and ProSe Information |
|||
Supported Features |
IUTE |
– |
|
Subscriber Identifier |
– |
– |
|
Node Id |
IUTE |
IUT- |
|
Announcing UE HPLMN Identifier |
IUTE |
– |
|
Announcing UE VPLMN Identifier |
IUTE |
– |
|
Monitoring UE HPLMN Identifier |
IUTE |
– |
|
Monitoring UE VPLMN Identifier |
IUTE |
– |
|
Discoverer UE HPLMN Identifier |
IUTE |
– |
|
Discoverer UE VPLMN Identifier |
IUTE |
– |
|
Discoveree UE HPLMN Identifier |
IUTE |
– |
|
Discoveree UE VPLMN Identifier |
IUTE |
– |
|
Role of ProSe Function |
IUTE |
– |
|
ProSe Application ID |
IUTE |
||
Application ID |
IUTE |
IUT- |
|
ProSe functionality |
IUTE |
– |
|
ProSe Event Type |
IUTE |
– |
|
Direct Discovery Model |
IUTE |
– |
|
ProSe Function IP Address |
IUTE |
IUT- |
|
ProSe Function ID |
IUTE |
IUT- |
|
Validity Period |
IUTE |
– |
|
Role of UE |
IUT- |
||
ProSe Request Timestamp |
IUTE |
IUT- |
|
PC3 Control Protocol Cause |
–TE |
– |
|
Monitoring UE Identifier |
IUTE |
IUT- |
|
Monitored PLMN Identifier |
IUTE |
– |
|
Requestor PLMN Identifier |
– |
IUT- |
|
Requestor Application Layer User ID |
– |
IUT- |
|
WLAN Link Layer ID |
– |
IUT- |
|
Requestor EPC ProSe User ID |
– |
IUT- |
|
Requested Application Layer User ID |
– |
IUT- |
|
Requested PLMN Identifier |
– |
IUT- |
|
Time Window |
– |
IU– |
|
Range Class |
– |
IU– |
|
User Location Info |
– |
IU– |
|
Proximity Alert Indication |
– |
–T- |
|
Proximity Alert Timestamp |
– |
–T- |
|
Proximity Cancellation Timestamp |
– |
–T- |
|
Reason for Cancellation |
– |
–T- |
|
PC3 EPC Control Protocol Cause |
– |
–T- |
|
Charging characteristics |
IUTE |
IUT- |
|
Charging Characteristics Selection Mode |
IUTE |
IUT- |
|
Change Condition |
– |
– |
|
ProSe UE ID |
– |
– |
|
Source IP address |
– |
– |
|
ProSe Layer-2 Group ID |
– |
– |
|
ProSe Group IP multicast address |
– |
– |
|
Application Specific Data |
– |
– |
|
Coverage Info |
– |
– |
|
ProSe Function PLMN Identifier |
– |
– |
|
Radio Parameter Set Info |
– |
– |
|
Reception Data Container |
– |
– |
|
Time of First Reception |
– |
– |
|
Time of First Transmission |
– |
– |
|
Transmission Data Container |
– |
– |
|
Transmitter Info |
– |
– |
|
PC5 Radio Technology |
IUTE |
– |
Table 6.3.4.2 illustrates the basic structure of the supported fields in the Debit / Reserve Units Response for ProSe online charging.
Table 6.3.4.2: Supported fields in Debit / Reserve Units Response Message
Information Element |
Sevice Type |
Direct Discovery |
EPC_Level Discovery |
---|---|---|---|
Supported Operation Types |
I/U/T/E |
I/U/T/E |
|
Session Identifier |
IUTE |
IUT- |
|
Operation Result |
IUTE |
IUT- |
|
Originator Host |
IUTE |
IUT- |
|
Originator Domain |
IUTE |
IUT- |
|
Operation Identifier |
IUTE |
IUT- |
|
Operation Type |
IUTE |
IUT- |
|
Operation Number |
IUTE |
IUT- |
|
Operation Failover |
IUTE |
IUT- |
|
Multiple Unit Operation |
IUTE |
IUT- |
|
Cost Information |
IUTE |
IUT- |
|
Low Balance Indication |
IUTE |
IUT- |
|
Remaining Balance |
IUTE |
IUT- |
|
Operation Failure Action |
IUTE |
IUT- |
|
Operation Event Failure Action |
IUTE |
IUT- |
|
Redirection Host |
IUTE |
IUT- |
|
Redirection Host Usage |
IUTE |
IUT- |
|
Redirection Cache Time |
IUTE |
IUT- |
|
Proxy Information |
IUTE |
IUT- |
|
Route Information |
IUTE |
IUT- |
|
Failed parameter |
IUTE |
IUT- |
|
Service Information |
IUTE |
IUT- |
|
Service Information with ProSe Information |
|||
Supported Features |
IUTE |
– |
6.4 Bindings for ProSe offline charging
This clause aims to describe the mapping between the Diameter Accounting AVPs, IEs and CDR parameters for ProSe offline charging.
Table 6.4.1 describes the mapping of the Diameter Accounting AVPs, IEs, and CDR parameters of PF-DD-CDR, PF-ED-CDR and PF-DC-CDR in ProSe offline charging.
Table 6.4.1: Bindings of CDR Parameters, Information Elements and AVPs
CDR Parameter |
Information Element |
AVP |
---|---|---|
Service Information |
Service-Information |
|
Served IMSI |
Subscriber Identifier |
Subscription-Id |
ProSe Information |
ProSe-Information |
|
– |
Supported Features |
Supported-Features |
Announcing PLMN ID |
Announcing PLMN ID |
Announcing-PLMN-ID |
Announcing UE HPLMN Identifier |
Announcing UE HPLMN Identifier |
Announcing-UE-HPLMN-Identifier |
Announcing UE VPLMN Identifier |
Announcing UE VPLMN Identifier |
Announcing-UE-VPLMN-Identifier |
Application ID |
Application ID |
ProSe-3rd-Party-Application-ID |
Application Specific Data |
Application Specific Data |
Application-Specific-Data |
Coverage Info |
Coverage Info |
Coverage-Info |
Direct Discovery Model |
Direct Discovery Model |
ProSe-Direct-Discovery-Model |
Discoveree UE HPLMN Identifier |
Discoveree UE HPLMN Identifier |
Discoveree-UE-HPLMN-Identifier |
Discoveree UE VPLMN Identifier |
Discoveree UE VPLMN Identifier |
Discoveree-UE-VPLMN-Identifier |
Discoverer UE HPLMN Identifier |
Discoverer UE HPLMN Identifier |
Discoverer-UE-HPLMN-Identifier |
Discoverer UE VPLMN Identifier |
Discoverer UE VPLMN Identifier |
Discoverer-UE-VPLMN-Identifier |
Monitoring UE Identifier |
Monitoring UE Identifier |
Monitoring-UE-Identifier |
Monitoring UE HPLMN Identifier |
Monitoring UE HPLMN Identifier |
Monitoring-UE-HPLMN-Identifier |
Monitoring UE VPLMN Identifier |
Monitoring UE VPLMN Identifier |
Monitoring-UE-VPLMN-Identifier |
Monitored PLMN Identifier |
Monitored PLMN Identifier |
Monitored-PLMN-Identifier |
PC3 Control Protocol Cause |
PC3 Control Protocol Cause |
PC3-Control-Protocol-Cause |
PC3 EPC Control Protocol Cause |
PC3 EPC Control Protocol Cause |
PC3-EPC-Control-Protocol-Cause |
ProSe Application ID |
ProSe Application ID |
ProSe-App-Id |
ProSe Event Type |
ProSe Event Type |
ProSe-Event-Type |
ProSe Function ID |
ProSe Function ID |
ProSe-Function-ID |
ProSe Function IP Address |
ProSe Function IP Address |
ProSe-Function-IP-Address |
ProSe Function PLMN Identifier |
ProSe Function PLMN Identifier |
ProSe-Function-PLMN-Identifier |
Record Type |
ProSe Functionality |
Prose-Functionality |
ProSe Group IP multicast address |
ProSe Group IP multicast address |
ProSe-Group-IP-multicast-address |
ProSe Layer-2 Group ID |
ProSe Layer-2 Group ID |
Layer-2-Group-ID |
ProSe Request Timestamp |
ProSe Request Timestamp |
ProSe-Request-Timestamp |
ProSe Target Layer-2 ID |
ProSe Target Layer-2 ID |
ProSe-Target-Layer-2-ID |
ProSe UE ID |
ProSe UE ID |
ProSe-UE-ID |
Proximity Alert Indication |
Proximity Alert Indication |
Proximity-Alert-Indication |
Proximity Alert Timestamp |
Proximity Alert Timestamp |
Proximity-Alert-Timestamp |
Proximity Cancellation Timestamp |
Proximity Cancellation Timestamp |
Proximity-Cancellation-Timestamp |
Proximity Request Renewal Info Block List |
Proximity Request Renewal Info Block List |
– |
ProSe Request Timestamp |
ProSe Request Timestamp |
ProSe-Request-Timestamp |
Range Class |
Range Class |
ProSe-Range-Class |
Time Window |
Time Window |
Time-Window |
UE Location |
User Location Info |
3GPP-User-Location-Info |
Radio Parameter Set Info |
Radio Parameter Set Info |
Radio-Parameter-Set-Info |
Range Class |
Range Class |
ProSe-Range-Class |
Reason for Cancellation |
Reason for Cancellation |
ProSe-Reason-for-Cancellation |
Reception Data Container |
Reception Data Container |
ProSe-Direct-Communication-Reception-Data-Container |
Change Time |
Change Time |
Change-Time |
Coverage status |
Coverage status |
Coverage-status |
Data Volume Received |
Data Volume Transmitted |
Accounting-Input-Octets |
Local Sequence Number |
Local Sequence Number |
Local-Sequence-Number |
Change Condition |
Change Condition |
Change-Condition |
Usage information report sequence number |
Usage information report sequence number |
Usage-information-report-sequence- number |
UE Location |
User Location Info |
3GPP-User-Location-Info |
VPLMN Identifier |
VPLMN Identifier |
Visited-PLMN-Id |
Radio Resources Indicator |
Radio Resources Indicator |
Radio-Resources-Indicator |
Radio Frequency |
Radio Frequency |
Radio-Frequency |
Relay IP address |
Relay IP address |
ProSe-Relay-IP-Address |
ProSe UE-to-Network Relay UE ID |
ProSe UE-to-Network Relay UE ID |
ProSe-UE-to-Network-Relay-UE-ID |
Requested Application Layer User ID |
Requested Application Layer User ID |
Target-App-Layer-User-Id |
Requested PLMN Identifier |
Requested PLMN Identifier |
Requested-PLMN-Identifier |
Requestor Application Layer User ID |
Requestor Application Layer User ID |
Origin-App-Layer-User-Id |
Requestor EPC ProSe User ID |
Requestor EPC ProSe User ID |
Requesting-EPUID |
Requestor PLMN Identifier |
Requestor PLMN Identifier |
Requestor-PLMN-Identifier |
Role of ProSe Function |
Role of ProSe Function |
Role-Of-ProSe-Function |
Role of UE |
Role of UE |
ProSe-Role-Of-UE |
Source IP address |
Source IP address |
ProSe-Source-IP-Address |
Target IP address |
Target IP address |
ProSe-Target -IP-Address |
Time of First Transmission |
Time of First Transmission |
Time-First-Transmission |
Time of First Reception |
Time of First Reception |
Time-First-Reception |
Time Window |
Time Window |
Time-Window |
Transmission Data Container |
Transmission Data Container |
ProSe-Direct-Communication-Transmission-Data-Container |
Change Time |
Change Time |
Change-Time |
Coverage status |
Coverage status |
Coverage-status |
Data Volume Transmitted |
Data Volume Transmitted |
Accounting-Output-Octets |
Local Sequence Number |
Local Sequence Number |
Local-Sequence-Number |
Change Condition |
Change Condition |
Change-Condition |
Usage information report sequence number |
Usage information report sequence number |
Usage-information-report-sequence- number |
UE Location |
User Location Info |
3GPP-User-Location-Info |
VPLMN Identifier |
VPLMN Identifier |
Visited-PLMN-Id |
Radio Resources Indicator |
Radio Resources Indicator |
Radio-Resources-Indicator |
Radio Frequency |
Radio Frequency |
Radio-Frequency |
Transmitter Info |
Transmitter Info |
ProSe-Direct-Communication-Transmitter-Info |
Validity Period |
Validity Period |
ProSe-Validity-Timer |
WLAN Link Layer ID |
WLAN Link Layer ID |
WLAN-Link-Layer-Id |
PC5 Radio Technology |
PC5 Radio Technology |
PC5-Radio-Technology |
PS Information |
PS-Information |
|
Cause for Record Closing |
Change Condition |
Change-Condition |
Charging characteristics |
Charging characteristics |
3GPP-Charging-Characteristics |
Charging Characteristics Selection Mode |
Charging Characteristics Selection Mode |
Charging-Characteristics-Selection-Mode |
Node Id |
Node Id |
Node-ID |
UE Location |
User Location Info |
3GPP-User-Location-Info |
6.5 Definition of the 5G ProSe converged charging information
6.5.1 General
The Charging Information parameter used for 5G ProSe converged charging is provided in the following clauses.
6.5.2 Definition of 5G ProSe charging information
6.5.2.1 Definition of ProSe Information
The fields of the ProSe specific charging information used for 5G ProSe is provided within the Service Specification Information.
The detailed structure of the ProSe Information can be found in table 6.5.2.1.1.
Table 6.5.2.1.1: Structure of ProSe information
Information Element |
Category |
Description |
Announcing PLMN ID |
OC |
Described in table 6.3.1.2.1. |
Announcing UE HPLMN Identifier |
OM |
Described in table 6.3.1.2.1. |
Announcing UE VPLMN Identifier |
OC |
Described in table 6.3.1.2.1. |
Monitoring UE HPLMN Identifier |
OC |
Described in table 6.3.1.2.1. |
Monitoring UE VPLMN Identifier |
OC |
Described in table 6.3.1.2.1. |
Discoverer UE HPLMN Identifier |
OM |
Described in table 6.3.1.2.1. |
Discoverer UE VPLMN Identifier |
OC |
Described in table 6.3.1.2.1. |
Discoveree UE HPLMN Identifier |
OC |
Described in table 6.3.1.2.1. |
Discoveree UE VPLMN Identifier |
OC |
Described in table 6.3.1.2.1. |
Monitored PLMN Identifier |
OC |
Described in table 6.3.1.2.1. |
ProSe Application ID |
Oc |
Described in table 6.3.1.2.1. |
Application ID |
Oc |
Described in table 6.3.1.2.1. |
Application Specific Data |
Oc |
Described in table 6.3.1.2.1. |
ProSe functionality |
Oc |
This IE holds the ProSe functionality UE is requesting, e.g. direct discovery (Announcing, Monitoring, or Match Report), direct communication. |
ProSe Event Type |
Oc |
Described in table 6.3.1.2.1. |
Direct Discovery Model |
Oc |
Described in table 6.3.1.2.1. |
Validity Period |
Oc |
Described in table 6.3.1.2.1. |
Role of UE |
Oc |
Described in table 6.3.1.2.1. |
ProSe Request Timestamp |
Oc |
Described in table 6.3.1.2.1. |
PC3 Protocol Cause |
Oc |
Described in table 6.3.1.2.1. |
Monitoring UE Identifier |
Oc |
Described in table 6.3.1.2.1. |
Requestor PLMN Identifier |
OC |
Described in table 6.3.1.2.1. |
Requested Application Layer User ID |
Oc |
Described in table 6.3.1.2.1. |
Requested PLMN Identifier |
Oc |
Described in table 6.3.1.2.1. |
Time Window |
Oc |
Described in table 6.3.1.2.1. |
Range Class |
Oc |
Described in table 6.3.1.2.1. |
Proximity Alert Indication |
Oc |
Described in table 6.3.1.2.1. |
Proximity Alert Timestamp |
Oc |
Described in table 6.3.1.2.1. |
Proximity Cancellation Timestamp |
Oc |
Described in table 6.3.1.2.1. |
Relay IP address |
Oc |
Described in table 6.3.1.2.1. |
ProSe UE-to-Network Relay UE ID |
Oc |
Described in table 6.3.1.2.1. |
ProSe Destination Layer-2 ID |
Oc |
The identifier of a link-layer that identifies a device or a group of devices that are recipients of ProSe communication frames. |
PFI Container information |
OC |
This field holds a list of PFI data container information defined in clause 6.5.2.3. |
Transmission Data Container |
OC |
Described in table 6.3.1.2.1. |
Local Sequence Number |
Oc |
Described in table 6.3.1.2.1. |
Change Time |
Oc |
Described in table 6.3.1.2.1. |
Coverage status |
Oc |
Whether UE is served by NG-RAN or not, i.e. in coverage, out of coverage. |
User Location Information |
Oc |
The location of the UE, e.g. NCGI. |
Data Volume Transmitted |
Oc |
Described in table 6.3.1.2.1. |
Change Condition |
Oc |
Described in table 6.3.1.2.1. |
VPLMN Identifier |
Oc |
Described in table 6.3.1.2.1. |
Usage information report sequence number |
Oc |
Described in table 6.3.1.2.1. |
Radio Resources indicator |
Oc |
Described in table 6.3.1.2.1. |
Radio Frequency |
Oc |
Described in table 6.3.1.2.1. |
PC5 Radio Technology |
OM |
Described in table 6.3.1.2.1. |
Reception Data Container |
Oc |
Described in table 6.3.1.2.1. |
Local Sequence Number |
Oc |
Described in table 6.3.1.2.1. |
Change Time |
Oc |
Described in table 6.3.1.2.1. |
Coverage status |
Oc |
Described in table 6.3.1.2.1. |
User Location Information |
Oc |
The location of the UE, e.g. NCGI. |
Data Volume Received |
Oc |
Described in table 6.3.1.2.1. |
Change Condition |
Oc |
Described in table 6.3.1.2.1. |
VPLMN Identifier |
Oc |
Described in table 6.3.1.2.1. |
Usage information report sequence number |
Oc |
Described in table 6.3.1.2.1. |
Radio Resources indicator |
Oc |
Described in table 6.3.1.2.1. |
Radio Frequency |
Oc |
Described in table 6.3.1.2.1. |
PC5 Radio Technology |
OM |
Described in table 6.3.1.2.1. |
Editor’s note: it is FFS for the structure of the ProSe Information and it is to be revisited.
6.5.2.2 Definition of PC5 Container Information
Used Unit Container, described in table 6.2a.1.2.1, specific charging information used for 5G ProSe charging is provided within the PC5 Container Information described in table 6.5.2.2.1.
Table 6.5.2.2.1: Structure of PC5 Container Information
Information Element |
Category |
Description |
---|---|---|
Coverage Info |
Oc |
This IE provides information on the coverage status (i.e., whether the UE is served by NG-RAN or not) and the time when the coverage status changed to its current state. When in NG-RAN coverage, additionally includes a list of location changes (i.e., NCGI change) and associated time for each change. |
Radio Parameter Set Info |
Oc |
Described in table 6.3.1.2.1.. |
Transmitter Info |
Oc |
Described in table 6.3.1.2.1. |
Time of First Transmission |
Oc |
Described in table 6.3.1.2.1. |
Time of First Reception |
Oc |
Described in table 6.3.1.2.1. |
6.5.2.3 Definition of PFI Container information
PFI Container information specific charging information used for 5G ProSe Direct Communication charging is provided within the PFI Container Information described in table 6.5.2.3.1.
Table 6.5.2.3.1: Structure of PFI Container Information
Information Element |
Category |
Description |
---|---|---|
PC5 QoS Flow Id |
M |
This field holds the PC5 QoS flow Identifier (PFI) |
Time of First Usage |
OC |
This field holds the Timestamp when the first transmitted IP packet of the service data flow matching the current PFI data container |
Time of Last Usage |
OC |
This field holds the Timestamp when the last transmitted IP packet of the service data flow matching the current PFI data container |
QoS Information |
OC |
This field holds the PC5 QoS applied during the PFI data container interval |
QoS Characteristics |
OC |
This field holds the PC5 QoS characteristics applied for PC5 QoS information. It is only be used when the non-standardized PQI is present in PC5 QoS information. |
User Location Information |
OC |
This field holds the user location during the PFI data container interval |
UE Time Zone |
OC |
This field holds the Time Zone of where the UE is located, during the PFI data container interval |
Presence Reporting Area Information |
OC |
This field holds the Presence Reporting Area Information of UE during the PFI data container interval. |
Report Time |
M |
This field holds the Timestamp when the PFI data container was closed |
6.5.3 Detailed message format for converged charging
The following clause specifies per Operation Type the charging data for 5G ProSe converged charging.
The Operation types are listed in the following order: I [Initial] / U (Update)/T [Termination]/E [event]. Therefore, when all Operation types are possible it is marked as IUTE. If only some Operation types are allowed for a node, only the appropriate letters are used (e.g. IUT or E) as indicated in the table heading. The omission of an Operation type for a particular field is marked with "-" (e.g. I-E). Also, when an entire field is not allowed in a node the entire cell is marked as "-".
Table 6.5.3.1 illustrates the basic structure of the supported fields in the Charging Data Request for 5G ProSe converged charging.
Table 6.5.3.1: Supported fields in Charging Data Request message
Information Element |
Node Type |
Direct Discovery |
Direct Communication |
---|---|---|---|
Supported Operation Types |
I/U/T/E |
I/U/T/E |
|
Session Identifier |
–E |
IUTE |
|
Subscriber Identifier |
–E |
IUTE |
|
NF Consumer Identification |
–E |
IUTE |
|
Invocation Timestamp |
–E |
IUTE |
|
Invocation Sequence Number |
–E |
IUTE |
|
Retransmission Indicator |
— |
— |
|
One-time Event |
–E |
–E |
|
One-time Event Type |
–E |
–E |
|
Notify URI |
I– |
I– |
|
Triggers |
–E |
IUTE |
|
Multiple Unit Usage |
–E |
IUTE |
|
Service Information with ProSe Information |
|||
Announcing PLMN ID |
—E |
– |
|
Announcing UE HPLMN Identifier |
—E |
– |
|
Announcing UE VPLMN Identifier |
—E |
– |
|
Monitoring UE HPLMN Identifier |
—E |
– |
|
Monitoring UE VPLMN Identifier |
—E |
– |
|
Discoverer UE HPLMN Identifier |
—E |
– |
|
Discoverer UE VPLMN Identifier |
—E |
– |
|
Discoveree UE HPLMN Identifier |
—E |
– |
|
Discoveree UE VPLMN Identifier |
—E |
– |
|
Monitored PLMN Identifier |
—E |
– |
|
ProSe Application ID |
—E |
– |
|
Application ID |
—E |
IUTE |
|
Application Specific Data |
– |
IUTE |
|
ProSe functionality |
—E |
IUTE |
|
ProSe Event Type |
—E |
– |
|
Direct Discovery Model |
—E |
||
Validity Period |
—E |
||
Role of UE |
—E |
||
ProSe Request Timestamp |
—E |
||
PC3 Protocol Cause |
—E |
||
Monitoring UE Identifier |
—E |
||
Requested Application Layer User ID |
—E |
||
Requested PLMN Identifier |
—E |
||
Time Window |
—E |
||
Range Class |
—E |
||
Proximity Alert Indication |
—E |
||
Proximity Alert Timestamp |
—E |
||
Proximity Cancellation Timestamp |
—E |
||
Relay IP address |
– |
IUTE |
|
ProSe UE-to-Network Relay UE ID |
– |
IUTE |
|
ProSe Destination Layer-2 ID |
– |
IUTE |
|
Coverage Info |
– |
IUTE |
|
Radio Parameter Set Info |
– |
IUTE |
|
Transmitter Info |
– |
IUTE |
|
Time of First Transmission |
– |
IUTE |
|
Time of First Reception |
– |
IUTE |
|
Transmission Data Container |
– |
IUTE |
|
Reception Data Container |
– |
IUTE |
|
PC5 Radio Technology |
—E |
– |
Table 6.5.3.2 illustrates the basic structure of the supported fields in the Charging Data Response for 5G ProSe converged charging.
Table 6.5.3.2: Supported fields in Charging Data Response Message
Information Element |
Node Type |
Direct Discovery |
Direct Communication |
---|---|---|---|
Supported Operation Types |
I/U/T/E |
I/U/T/E |
|
Session Identifier |
–E |
IUTE |
|
Invocation Timestamp |
–E |
IUTE |
|
Invocation Result |
–E |
IUTE |
|
Invocation Sequence Number |
–E |
IUTE |
|
Session Failover |
– |
IUTE |
|
Supported Features |
– |
IUTE |
|
Triggers |
I–E |
IUTE |
|
Multiple Unit Usage |
–E |
IUTE |
|
Result Code |
–E |
IUTE |
|
Rating Group |
–E |
IUTE |
|
Granted Unit |
–E |
IUTE |
|
Tariff Time Change |
–E |
IUTE |
|
Time |
–E |
IUTE |
|
Total Volume |
–E |
IUTE |
|
Uplink Volume |
–E |
IUTE |
|
Downlink Volume |
–E |
IUTE |
|
Service Specific Units |
–E |
IUTE |
|
Validity Time |
–E |
IUTE |
|
Final Unit Indication |
–E |
IUTE |
|
Time Quota Threshold |
–E |
IUTE |
|
Volume Quota Threshold |
–E |
IUTE |
|
Unit Quota Threshold |
–E |
IUTE |
|
Quota Holding Time |
–E |
IUTE |
|
Triggers |
–E |
IUTE |
6.5.4 Formal 5G ProSe converged charging parameter description
6.5.4.1 5G ProSe charging CHF CDR parameters
The detailed definitions, abstract syntax and encoding of the 5G ProSe charging CHF CDR parameters are specified in TS 32.298 [51].
6.5.4.2 5G ProSe charging resources attributes
The detailed definitions of resources attributes used for 5G ProSe charging are specified in TS 32.291 [56].
6.6 Bindings for 5G ProSe converged charging
This mapping between the Information Elements, resource attributes and CHF CDR parameters for 5G ProSe converged charging is described in clause 7 of TS 32.291 [56].
Annex A (normative):
Charging Characteristics