5.2.1 Basic principles

32.2773GPPCharging managementProximity-based Services (ProSe) chargingRelease 17Telecommunication managementTS

5.2.1.1 General

The ProSe Functions in HPLMN, VPLMN, and Local PLMNs shall be able to report charging events for CDRs generation by CDF.

In ProSe EPC-level Discovery scenario, the ProSe EPC-level Discovery CDRs (PF-ED-CDR) shall be opened, updated, and closed based on the following:

– Charging data related to ProSe EPC-level Discovery Proximity Request;

– Charging data related to ProSe EPC-level Discovery Proximity Alert;

– Charging data related to ProSe EPC-level Discovery Proximity Request Cancellation.

The contents and purpose of each charging event that triggers CDR creation, information addition, or closure are described in the following clauses.

When the CDF is implemented as a separate entity (than the ProSe Function), the Charging Events triggering and contents for CDRs handling by the CDF are described in clause 5.2.2.

NOTE: the notion of "Local PLMN" does not apply to WLAN-based ProSe Direct Discovery, so the collection of charging information by ProSe Functions in local PLMN does not apply to WLAN-based ProSe Direct Discovery.

5.2.1.2 ProSe Direct Discovery charging

The charging information on the use of ProSe Direct Discovery is collected by the ProSe Functions in HPLMN, VPLMN, and local PLMNs. Inter-operator charging is supported.

When a charging event is reported to the CDF, it includes relevant information as listed in clause 5.1.2.

The following chargeable events are defined for ProSe Direct Discovery charging:

– Monitor Request received by the ProSe Function in the HPLMN of the Monitoring UE. Upon this event, a PF-DD-CDR is generated.

– Monitor Request received by the ProSe Function of the PLMN providing the Discovery Filter. Upon this event, a PF-DD-CDR is generated.

– Announce Request received by the HPLMN ProSe Function of the Announcing UE. Upon this event, a PF-DD-CDR is generated.

– Announce Request received by the ProSe Function in the VPLMN of the Announcing UE when roaming. Upon this event, PF-DD-CDR is generated.

– Announce Request received by the ProSe Function in the other PLMN of the Announcing UE when inter-PLMN transmission. Upon this event, PF-DD-CDR is generated.

– Discovery query received by the ProSe Function in the HPLMN of the Discoverer UE. Upon this event, a PF-DD-CDR is generated.

– Discovery query received by the ProSe Function in the VPLMN of the Discoverer UE when roaming. Upon this event, PF-DD-CDR is generated.

– Discovery query received by the ProSe Function in the other PLMN of the Discoverer UE when inter-PLMN transmission. Upon this event, PF-DD-CDR is generated.

– Discovery response received by the ProSe Function in the HPLMN of the Discoveree UE. Upon this event, a PF-DD-CDR is generated.

– Discovery response received by the ProSe Function in the VPLMN of the Discoveree UE when roaming. Upon this event, a PF-DD-CDR is generated.

– Discovery response received by the ProSe Function in other PLMN of the Discoveree UE when inter-PLMN transmission. Upon this event, a PF-DD-CDR is generated.

– Match Report Request received by the ProSe Function in the HPLMN of the Monitoring UE. Upon this event, a PF-DD-CDR is generated.

– Match Report Request received by the ProSe Function in the HPLMN of the Discoverer UE. Upon this event, a PF-DD-CDR is generated.

– Match Report Request received by the ProSe Function in the HPLMN of the Announcing UE. Upon this event, a PF-DD-CDR is generated.

– Match Report Info received by the ProSe Function in the VPLMN of the Announcing UE when roaming. Upon this event, a PF-DD-CDR is generated.

5.2.1.3 ProSe EPC-level Discovery charging

When a charging event is reported to the CDF, it includes relevant information as listed in clause 5.1.2.

The following chargeable events are defined for ProSe EPC-level Discovery charging:

– Proximity Request. Upon this event, a new PF-ED-CDR is opened, and the corresponding EPUID, ALUIDs, Application ID, window, Range, and location of the UE are captured.

– Proximity Request Renewal. Upon this event, an already open PF-ED-CDR for corresponding initial request is updated with new location of the UE, time window and range class.

– Proximity Request Reject. Upon this event, the corresponding PF-ED-CDR is closed, and an indication of the cause for reject is captured.

– Proximity Request Cancellation. Upon this event, the corresponding PF-ED-CDR is closed, and an indication of whether Proximity Alert was sent is captured.

When the CDF is implemented as a separate entity, all these ProSe EPC-level Discovery related chargeable events triggers the CDRs to be constructed, enriched, or closed by CDF, according to description in clause 5.2.2.

5.2.1.4 ProSe Direct Communication charging

Based on the usage information reported by the UE, the ProSe Functions in HPLMN produces CDRs or reports charging events for CDRs generation by CDF. The CDRs or charging events are generated for the ProSe one-to-many Direct Communication for Public Safety use (PF-DC-CDR).

When the CDF is implemented as a separate entity (than the ProSe Function), the charging events triggering and handling are described in clause 5.2.2.3.

For ProSe one-to-many Direct Communication charging, ProSe one-to-one Direct Communication and Direct Communication via ProSe UE-to-Network Relay, either event based charging or session based charging can be used, depending on configuration of the ProSe Function and CDF.

NOTE: The charging session does not correspond to any ProSe one-to-many Direct Communication session, as there is no session concept defined for the group communication in TS 23.303 [238].

When a charging event is reported to the CDF, it includes relevant information as listed in clause 5.1.2.

The following chargeable events are defined for ProSe one-to-many Direct Communication charging:

– Received Direct Communication Usage Report (for a group).

If event based charging is used, upon this event, a Charging Data Request[Event] for a specific group is generated.

If session based charging is used, either a Charging Data Request[Start], Charging Data Request[Interim], or Charging Data Request[Stop] for a specific group is generated.

The following chargeable events are defined for ProSe one-to-one Direct Communication (none of the UEs is a relay) charging:

– Received Direct Communication Usage Report (for the both UEs in the one-to-one communication).

If event based charging is used, upon this event, a Charging Data Request[Event] for each UE in the one-to-one communication is generated.

If session based charging is used, either a Charging Data Request[Start], Charging Data Request[Interim], or Charging Data Request[Stop] for each UE in the one-to-one communication is generated.

The following chargeable events are defined for Direct Communication via ProSe UE-to-Network Relay charging:

– Received Direct Communication Usage Report (for the remote UE).

If event based charging is used, upon this event, a Charging Data Request[Event] for a remote UE is generated.

If session based charging is used, either a Charging Data Request[Start], Charging Data Request[Interim], or Charging Data Request[Stop] for a remote UE is generated.

The triggering conditions for the corresponding charging events are defined in clause 5.2.2.3.1.