Patent ID: 12231596

DESCRIPTION OF EMBODIMENTS

In order to address the aforementioned problems, the inventors propose the following solutions:Solution 1 Charging reporting for traffic over PC5Solution 2 Charging reporting for traffic over PC5 based on SBA-AF contributes to PC5 charging policySolution 3 Charging reporting for traffic over PC5 with pre-configured usage information collection and reportingSolution 4 UE reporting triggered by AFSolution 5 UE reporting triggered by UE's application layerSolution 6 UE reporting charging on PC5 via SMF
Modifications on PCC Rules

The following contents are proposed to add to the current PCC rules as specified in 3GPP TS 23.503 [3]:Charging for PC5: This attribute in PCC rules includes a charging key, a service identifier, an application service provider identifier, a charging method, a measurement method, application function record information, service identifier level reporting, a reference interface ID (i.e. PC5) and other kinds of relevant charging parameters.Usage Monitoring and Reporting for PC5: This attribute in PCC rules includes parameters having an application layer group ID, a Layer 2 group ID, a UE application ID, an Application ID, an Application server ID, usage report on PC5 or other kinds of relevant usage parameters. Usage report on PC5 includes a list of amount of data transmitted and received with timestamp, a source ID, a destination ID and the UE location. Trigger condition and threshold are also included.
Solution 1 Charging Reporting for Traffic Over PC5
Example Aspect 1-1: UE Reporting Usage Report to CHF Via PCF when the Criteria is Met

The main idea of this solution is that the PCF12defines rules and policies for the UE3to collect and report its usage information on both Uu and PC5. In this Example Aspect, the UE3reports usage information to the CHF13via the PCF12. For example, the criteria can be that the configured collection period for usage information has elapsed. As another example, when the UE3is out of RAN coverage, the UE3generates reports from the recorded usage information every collection period and stores the non-empty reports, and sends the reports once the UE3returns to coverage.

FIG.1illustrates schematically an exemplary procedure for charging reporting for traffic over PC5 via the PCF12.

Step1: When the UE3initiates a ProSe service, ProSe service authorization takes place. In this step, the ProSe service authorization has been successfully executed as per described in 3GPP TS 23.303 [4]. Although in the present example a ProSe Function is used, it will be appreciated that the functionalities of the ProSe Function may be provided by the PCF12(or another node responsible for proximity services).

Step2: The AF16invokes a PC5 charging enforcement procedure or any other procedure or sends, to the PCF12, a Npcf_PC5_charging message to inform the PCF12of a PC5 Charging policy. The PC5 charging policy includes a charging key, a service identifier, an application service provider identifier, a charging method, a measurement method, application function record information, service identifier level reporting, and a reference interface Indicator (i.e. PC5), usage reporting criteria and other kinds of relevant usage parameters.

Step3: The PCF12invokes a PC5 charging enforcement procedure or any other procedure or sends, to the AMF11, a Namf_PC5_charging message to inform the AMF11of the PC5 Charging policy. The PCF12may add a usage information collection and reporting in PCC rules. The usage information collection and reporting includes a usage information reporting criteria and usage information measurement, which has an Application Layer Group ID, a Layer 2 group ID, a UE application ID, an Application ID, an Application Server ID, a “Usage Report on PC5” Indicator, a “Usage Report on Uu” indicator, and other kinds of relevant usage parameters.

Step4: The AMF11delivers the PC5 Charging policy and PCC rules to the UE3using the UE Configuration Update procedure.

Step5: The AMF11sends the Namf_PC5_charging acknowledge message to the PCF12.

Step6: The PCF12sends the Npcf_PC5_charging acknowledge message to the AF16.

Step7: PC5 communication takes place. The UE3creates a usage information report when the reporting criteria is met. For example, the criteria can be that the configured collection period for usage information has elapsed. As another example, when the UE3is out of RAN coverage, the UE3generates reports from the recorded usage information every collection period and stores the non-empty reports, and sends the reports once the UE3returns to coverage.

Step8: The UE3invokes the usage reporting procedure or any other service procedure or sends an MM message with PC5 charging report Information to the AMF11. This report includes an Application Layer Group ID, an Application ID, a Layer 2 Group ID, a UE Application ID, an Application Server ID, Usage Report on PC5, Usage Report on Uu, and other kinds of relevant usage parameters. The usage report on PC5 includes a list of amount of data transmitted and received via PC5 with timestamp, a source ID, a destination ID and the UE location. The usage report on Uu includes a list of amount of data transmitted and received via Uu with timestamp, a source ID, a destination ID and the UE location.

Step9: The AMF11sends the Usage information reporting to the PCF12with the PC5 charging report Information.

Step10: The PCF12sends the Charging Data Request message to the CHF13with the PC5 charging report Information.

Step11: The CHF13generates a CDR based on the PC5 charging report Information received in step10.

Step12: The CHF13sends the Charging Data Response message to the PCF12.

Example Aspect 1-2: UE Reporting Usage Report to CHF Via AMF when the Criteria is Met

The main idea of this solution is that the PCF12defines rules and policies for the UE3to collect and report its usage information on both Uu and PC5. In this Example Aspect, UE reporting to the CHF13is performed via the AMF11when the criteria is met. For example, the criteria can be that the configured collection period for usage information has elapsed. As another example, when the UE3is out of RAN coverage, the UE3generates reports from the recorded usage information every collection period and stores the non-empty reports, and sends the reports once the UE3returns to coverage.

FIG.2illustrates schematically an exemplary procedure for charging reporting traffic over PC5 via the AMF11.

Step1: When the UE3initiates a ProSe service, ProSe service authorization takes place. In this step, the ProSe service authorization has been successfully executed as per described in 3GPP TS 23.303 [4]. Although in the present example a ProSe Function is used, it will be appreciated that the functionalities of the ProSe Function may be provided by the PCF12(or another node responsible for proximity services).

Step2: The AF16invokes a PC5 charging enforcement procedure or any other procedure or sends, to the PCF12, a Npcf_PC5_charging message to inform the PCF12of a PC5 Charging policy. The PC5 charging policy includes a charging key, a service identifier, an application service provider identifier, a charging method, a measurement method, application function record information, a service identifier level reporting, and a reference interface Indicator (i.e. PC5), a usage reporting criteria and other kinds of relevant usage parameters.

Step3: The PCF12invokes a PC5 charging enforcement procedure or any other procedure or sends, to the AMF11, a Namf_PC5_charging message to inform the AMF11of the PC5 Charging policy. The PCF12includes CHF related information, i.e., CHF address information, in this message so that the AMF11can report the usage information to the CHF13. The PCF12may add a usage information collection and reporting in PCC rules. The usage information collection and reporting includes usage information reporting criteria and usage information measurement, which has an Application Layer Group ID, a Layer 2 group ID, a UE application ID, an Application ID, an Application Server ID, a “Usage Report on PC5” Indicator, a “Usage Report on Uu” indicator, and other kinds of relevant usage parameters.

Step4: The AMF11delivers the PC5 Charging policy and PCC rules to the UE3using the UE Configuration Update procedure.

Step5: The AMF11sends the Namf_PC5_charging acknowledge message to the PCF12.

Step6: The PCF12sends the Npcf_PC5_charging acknowledge message to the AF16.

Step7: PC5 communication takes place. The UE3creates usage information report when the reporting criteria is met. For example, the criteria can be that the configured collection period for usage information has elapsed. As another example, when the UE3is out of RAN coverage, the UE3generates reports from the recorded usage information every collection period and stores the non-empty reports, and sends the reports once the UE3returns to coverage.

Step8: The UE3invokes the usage reporting procedure or any other service procedure or sends an MM message with PC5 charging report Information to the AMF11. This report includes an Application Layer Group ID, an Application ID, a Layer 2 Group ID, a UE Application ID, an Application Server ID, Usage Report on PC5, Usage Report on Uu, and other kinds of relevant usage parameters. The usage report on PC5 includes a list of amount of data transmitted and received via PC5 with timestamp, a source ID, a destination ID and the UE location. The usage report on Uu includes a list of amount of data transmitted and received via Uu with timestamp, a source ID, a destination ID and the UE location.

Step9: The AMF11sends the Charging Data Request message to the CHF13with the PC5 charging report Information.

Step10: The CHF13generates a CDR based on the PC5 charging report Information received in step9.

Step11: The CHF13sends the Charging Data Response message to the AMF11.

Solution 2 Charging Reporting for Traffic Over PC5 Based on SBA-AF Contributes to PC5 Charging Policy

Example Aspect 2-1: AF Contributes to PC5 Charging Policy

The main idea of this solution is that the AF16contributes to PC5 charging policy, and the PCF12delivers the charging policies to the UE via the AMF11/SMF15. the UE3reports the SMF15its usage when the report criteria is met, and the SMF15notifies the CHF13of the usage report.

FIG.3illustrates schematically an exemplary procedure for Charging over PC5 for traffic (such as Interactive Services) based on SBA, in which the AF16contributes to PC5 charging policy.

Step1: When the UE3initiates ProSe service, ProSe service authorization takes place. In this step, the ProSe service authorization has been successfully executed as per described in 3GPP TS 23.303 [4]. Although in the present example a ProSe Function is used, it will be appreciated that the functionalities of the ProSe Function may be provided by the PCF12(or another node responsible for proximity services).

Step2: The AF16invokes a PC5 charging enforcement procedure or any other procedure or sends, to the PCF12, a Npcf_PC5_charging message to inform the PCF12of a PC5 Charging policy. The PC5 charging policy includes a charging key, a service identifier, an application service provider identifier, a charging method, a measurement method, application function record information, service identifier level reporting, and a reference interface Indicator (i.e. PC5), usage reporting criteria and other kinds of relevant usage parameters.

Step3: The PCF12invokes a PC5 charging enforcement procedure or any other procedure or sends, to the SMF15, a Nsmf_PC5_charging message to inform the SMF15of the PC5 Charging policy. The PCF12includes CHF related information, i.e. CHF address information in this message so that the AMF11can report the usage information to the CHF13. The PCF12may add a usage information collection and reporting in PCC rules. The usage information collection and reporting includes a usage information reporting criteria and usage information measurement, which has an Application Layer Group ID, a Layer 2 group ID, a UE application ID, an Application ID, an Application Server ID, a “Usage Report on PC5” Indicator, a “Usage Report on Uu” indicator, and other kinds of relevant usage parameters.

Step4: The SMF15invokes a PC5 charging enforcement procedure or any other procedure or sends, to the AMF11, a Namf_PC5_charging message to inform the AMF11of the PC5 Charging policy and PCC rules.

Step5: The AMF11delivers the PC5 Charging policy and PCC rules to the UE3using the UE Configuration Update procedure.

Step6: The AMF11sends the Namf_PC5_charging acknowledge message to the SMF15.

Step7: The SMF15sends the Nsmf_PC5_charging acknowledge message to the PCF12.

Step8: The PCF12sends the Npcf_PC5_charging acknowledge message to the AF16.

Step9: PC5 communication takes place. The UE3creates usage information report when the reporting criteria is met. For example, the criteria can be that the configured collection period for usage information has elapsed. As another example, when the UE3is out of RAN coverage, the UE3generates reports from the recorded usage information every collection period and stores the non-empty reports, and sends the reports once the UE3returns to coverage.

Step10: The UE3invokes the usage reporting procedure or any other service procedure or sends an SM message with PC5 charging report Information to the SMF15via the AMF11. This report includes an Application Layer Group ID, an Application ID, a Layer 2 Group ID, a UE Application ID, an Application Server ID, Usage Report on PC5, Usage Report on Uu, and other kinds of relevant usage parameters. The usage report on PC5 includes a list of amount of data transmitted and received via PC5 with timestamp, a source ID, a destination ID and the UE location. The usage report on Uu includes a list of amount of data transmitted and received via Uu with timestamp, a source ID, a destination ID and the UE location.

Step11: The SMF15sends the Nchf_Notify message to the CHF13with PC5 charging report Information. The SMF15then generates a CDR based on the PC5 charging report Information received in this step.

Solution 3 Charging Reporting for Traffic Over PC5 with Pre-Configured Usage Information Collection and Reporting

Example Aspect 3-1: UE Reporting Via PCF to CHF when the Criteria is Met

The main idea of this solution is that the UE3is pre-configured to collect and report its usage information on both Uu and PC5. In this Example Aspect, the UE reporting to the CHF13is via the PCF12when the criteria is met. For example, the criteria can be that the configured collection period for usage information has elapsed. As another example, when the UE3is out of RAN coverage, the UE3generates reports from the recorded usage information every collection period and stores the non-empty reports, and sends the reports once the UE3returns to coverage.

FIG.4illustrates schematically an exemplary procedure for Charging reporting for traffic over PC5 via the PCF12(with pre-configured rules on usage information collection and reporting).

Step1: The UE3uses pre-configured usage information collection and reporting policies.

Step2: The UE3creates a usage information report when the reporting criteria is met. For example, the criteria can be that the configured collection period for usage information has elapsed. As another example, when the UE3is out of RAN coverage, the UE3generates reports from the recorded usage information every collection period and stores the non-empty reports, and sends the reports once the UE3returns to coverage.

Step3-4: The UE3invokes the usage reporting procedure or any other service procedure or sends, to the PCF12, a Usage Information Reporting Message via the AMF11to report, to the network, a UE's usage information report. The usage information report has an Application Layer Group ID, an Application ID, a Layer 2 Group ID, a UE Application ID, an Application Server ID, a Usage Report on PC5, a Usage Report on Uu, and other kinds of relevant usage parameters. The usage report on PC5 includes a list of amount of data transmitted and received via PC5 with a timestamp, a source ID, a destination ID and the UE location. The usage report on Uu includes a list of amount of data transmitted and received via Uu with timestamp, a source ID, a destination ID and the UE location.

Step5-7: The PCF12contacts the CHF13to create a CDR. The CHF13can cross-check the usage information report from different UEs.

Example Aspect 3-2: UE Reporting Via AMF to CHF when the Criteria is Met

The main idea of this solution is that the UE3is pre-configured to collect and report its usage information on both Uu and PC5. In this Example Aspect, the UE reporting to the CHF13is via the AMF11when the criteria is met. For example, the criteria can be that the configured collection period for usage information has elapsed. As another example, when the UE3is out of RAN coverage, the UE3generates reports from the recorded usage information every collection period and stores the non-empty reports, and sends the reports once the UE3returns to coverage.

FIG.5illustrates schematically an exemplary procedure for charging reporting for traffic over PC5 via the AMF11(with pre-configured rules on usage information collection and reporting).

Step1: The UE3uses pre-configured usage information collection and reporting policies.

Step2: The UE3creates a usage information report when the reporting criteria is met. For example, the criteria can be that the configured collection period for usage information has elapsed. As another example, when the UE3is out of RAN coverage, the UE3generates reports from the recorded usage information every collection period and stores the non-empty reports, and sends the reports once the UE3returns to coverage.

Step3: The UE3invokes the usage reporting procedure or any other service procedure or sends, to the AMF11, a Usage Information Reporting Message to report, to the network, a UE's usage information report. The usage information report has an Application Layer Group ID, an Application ID, a Layer 2 Group ID, a UE Application ID, an Application Server ID, a Usage Report on PC5, a Usage Report on Uu, and other kinds of relevant usage parameters. The usage report on PC5 includes a list of amount of data transmitted and received via PC5 with timestamp, a source ID, a destination ID and the UE location. The usage report on Uu includes a list of amount of data transmitted and received via Uu with timestamp, a source ID, a destination ID and the UE location.

Step4-6: The AMF11contacts the CHF13to create a CDR. The CHF13can cross-check the usage information report from different UEs.

In this solution, the UE3uses pre-configured charging policies. As its result, it allows the network to charge UE's usage accurately and flexibly.

Solution 4 UE Reporting Triggered by AF

Example Aspect 4-1: UE Reporting Triggered by AF's Charging Request Message

The main idea of this Example Aspect is that the AF16requests the network to provide charging report, and the network triggers the UE3to report its usage.

FIG.6illustrates schematically an exemplary procedure for UE reporting triggered by an AF's charging request message.

Step1: When the NCIS session finishes, the AF16invokes the charging reporting procedure or any other service procedure or sends, to the PCF12, a charging reporting request message to inform the PCF12that the NCIS session is over and request the network to provide the charging information.

Step2-3: The PCF12sends the UE Usage Information reporting request. This message may include a UE ID, a Group ID, an Application ID, a usage information report indication and other kinds of relevant usage parameters.

Step4-5: The UE3invokes the usage reporting procedure or any other service procedure or sends, to the PCF12, a Usage Information Reporting Message via the AMF11to report, to the network, a UE's usage information report. The usage information report has an Application Layer Group ID, an Application ID, a Layer 2 Group ID, a UE Application ID, an Application Server ID, a Usage Report on PC5, a Usage Report on Uu, and other kinds of relevant usage parameters. The usage report on PC5 includes a list of amount of data transmitted and received via PC5 with timestamp, a source ID, a destination ID and the UE location. The usage report on Uu includes a list of amount of data transmitted and received via Uu with timestamp, a source ID, a destination ID and the UE location.

Step6-8: The PCF12contacts the CHF13to create a CDR

In this example aspect, the AF16requests the network to provide charging report. As its result, it allows the network to charge UE's usage accurately and flexibly.

Example Aspect 4-2: Enforce CDR Generation after UE has been Authorized for ProSe Service

The main idea of this solution is that the ProSe application Server16issues a Subscribe message to the SMF15/PCF12when UE3has been authorized by the server. The SMF15behaves as a Producer Proxy. Once the Subscribe message is received by the SMF15/PCF12, the SMF15/PCF12performs the UE configuration Update procedure so that UE3can get the Charging policy.

FIG.7is a high level illustration of charging over PC5 based on SBA.

FIG.8illustrates schematically an exemplary procedure for UE reporting triggered by AF's Subscription message.

Step1: The ProSe service authorization has been successfully executed as per described in 3GPP TS 23.303. Although in the present example a ProSe Function is used, it will be appreciated that the functionalities of the ProSe Function may be provided by the PCF12(or another node responsible for proximity services).

Step2: The AF16invokes a PC5 charging services procedure or any other procedure or sends, to the PCF12, a Npcf_PC5_0message to subscribe the network's PC5 Charging service.

Step3-5: The PCF12delivers its policies, which includes the PC5 charging policy, and CHF related information to UE3. The CHF related information is the CHF ID that needs to receive the usage information report. If the UE3is in CM-CONNECTED, UE policy delivery with new PCC rules with usage information collection and reporting is in the UE Policy container. The AMF11transfers transparently the UE Policy container received from the PCF12to the UE3. The usage information collection and reporting includes usage information reporting criteria and usage information measurement, which has an Application Layer Group ID, a Layer 2 group ID, a UE application ID, an Application ID, an Application Server ID, a Usage Report on PC5 Indicator, a Usage Report on Uu indicator, and other kinds of relevant usage parameters.

Step6-8: The AMF11acknowledges the UE policies by sending the message Namf_PC5_charging acknowledgement to the network, which is transferred to the AF16via the SMF15/PCF12.

Step9: Direct communication takes place over PC5, and the UE3creates a usage information report when the reporting criteria is met. For example, the criteria can be that the configured collection period for usage information has elapsed. As another example, when the UE3is out of RAN coverage, the UE3generates reports from the recorded usage information every collection period and stores the non-empty reports, and sends the reports once the UE3returns to coverage.

Step10: The UE3invokes the usage reporting procedure or any other service procedure or sends, to the SMF15, a SM message with PC5 charging report Information to report, to the network, a UE's usage information report. The usage information report has an Application Layer Group ID, an Application ID, a Layer 2 Group ID, a UE Application ID, an Application Server ID, a Usage Report on PC5, a Usage Report on Uu, and other kinds of relevant usage parameters. The usage report on PC5 includes a list of amount of data transmitted and received via PC5 with timestamp, a source ID, a destination ID and the UE location. The usage report on Uu includes a list of amount of data transmitted and received via Uu with timestamp, a source ID, a destination ID and the UE location.

Step11: The SMF15notifies the CHF13to create a CDR. The CHF13can cross-check the usage information report from different UEs.

In this example aspect, the AF16subscribe the PCF's service on charging report, and the PCF12provides the CHF13the reports. As its result, it allows the network to charge UE's usage accurately and flexibly.

Solution 5 UE Reporting Triggered by UE's Application Layer

Example Aspect 5-1: UE Reporting Via PCF to CHF when the Criteria is Met

The main idea of this solution is that the UE application layer triggers the UE3to collect and report its usage information on both Uu and PC5. In this Example Aspect, the UE reporting to the CHF13is via the PCF12when the criteria is met. For example, the criteria can be that the configured collection period for usage information has elapsed. As another example, when the UE3is out of RAN coverage, the UE3generates reports from the recorded usage information every collection period and stores the non-empty reports, and sends the reports once the UE3returns to coverage.

FIG.9illustrates schematically an exemplary procedure in which the UE's application layer triggers the UE3to collect and report its usage information on both Uu and PC5 via the PCF12.

Step1: UE's Application Layer informs its Layer 2 when the NCIS session is over.

Step2: The UE3creates a usage information report when the reporting criteria is met. For example, the criteria can be that the configured collection period for usage information has elapsed. As another example, when the UE3is out of RAN coverage, the UE3generates reports from the recorded usage information every collection period and stores the non-empty reports, and sends the reports once the UE3returns to coverage.

Step3-4: The UE3invokes the usage reporting procedure or any other service procedure or sends, to the PCF12, a Usage Information Reporting Message via the AMF11to report the network UE's usage information report. The usage information report has an Application Layer Group ID, an Application ID, a Layer 2 Group ID, a UE Application ID, an Application Server ID, a Usage Report on PC5, a Usage Report on Uu, and other kinds of relevant usage parameters. The usage report on PC5 includes a list of amount of data transmitted and received via PC5 with timestamp, a source ID, a destination ID and the UE location. The usage report on Uu includes a list of amount of data transmitted and received via Uu with timestamp, a source ID, a destination ID and the UE location.

Step5-7: The PCF12contacts the CHF13to create a CDR. The CHF13can cross-check the usage information report from different UEs.

Example Aspect 5-2: UE Reporting Via AMF to CHF when the Criteria is Met

The main idea of this solution is that the UE application layer triggers the UE3to collect and report its usage information on both Uu and PC5. In this Example Aspect, the UE reporting to the CHF13is via the AMF11when the criteria is met. For example, the criteria can be that the configured collection period for usage information has elapsed. As another example, when the UE3is out of RAN coverage, the UE3generates reports from the recorded usage information every collection period and stores the non-empty reports, and sends the reports once the UE3returns to coverage.

FIG.10illustrates schematically an exemplary procedure in which the UE application layer triggers the UE3to collect and report its usage information on both Uu and PC5 via the AMF11.

Step1: UE's Application Layer informs its Layer 2 when the NCIS session is over.

Step2: The UE3creates a usage information report when the reporting criteria is met. For example, the criteria can be that the configured collection period for usage information has elapsed. As another example, when the UE3is out of RAN coverage, the UE3generates reports from the recorded usage information every collection period and stores the non-empty reports, and sends the reports once the UE3returns to coverage.

Step3: The UE3invokes the usage reporting procedure or any other service procedure or sends, to the AMF11, a Usage Information Reporting Message to report, to the network, a UE's usage information report. The usage information report has an Application Layer Group ID, an Application ID, a Layer 2 Group ID, a UE Application ID, an Application Server ID, a Usage Report on PC5, a Usage Report on Uu, and other kinds of relevant usage parameters. The usage report on PC5 includes a list of amount of data transmitted and received via PC5 with timestamp, a source ID, a destination ID and the UE location. The usage report on Uu includes a list of amount of data transmitted and received via Uu with timestamp, a source ID, a destination ID and the UE location.

Step4-6: The AMF11contacts the CHF13to create a CDR. The CHF13can cross-check the usage information report from different UEs.

In this solution, the UE application layer triggers the UE3to collect and report its usage information. As its result, it allows the network to charge UE's usage accurately and flexibly.

Solution 6 UE Reporting Charging on PC5 Via SMF

Example Aspect 6-1: UE Reporting Charging on PC5 Via SMF

The main idea of this solution is that the SMF15exchanges messages with the CHF13for usage information collection and reporting.

FIG.11illustrates schematically an exemplary procedure in which the SMF15exchanges messages with the CHF13for usage information collection and reporting.

Step1: ProSe service authorization has been successfully executed as per described in 3GPP TS 23.303. Although in the present example a ProSe Function is used, it will be appreciated that the functionalities of the ProSe Function may be provided by the PCF12(or another node responsible for proximity services).

Step2: If the UE3is in CM-CONNECTED, the UE policy delivery with new PCC rules with usage information collection and reporting is in the UE Policy container. The AMF11transfers transparently the UE Policy container received from the PCF12to the UE3. The usage information collection and reporting includes usage information reporting criteria and usage information measurement, which has an Application Layer Group ID, a Layer 2 group ID, a UE application ID, an Application ID, an Application Server ID, a Usage Report on PC5 Indicator, a Usage Report on Uu indicator, and other kinds of relevant usage parameters.

Step3: The UE3creates a usage information report when the reporting criteria is met. For example, the criteria can be that the configured collection period for usage information has elapsed. As another example, when the UE3is out of RAN coverage, the UE3generates reports from the recorded usage information every collection period and stores the non-empty reports, and sends the reports once the UE3returns to coverage.

Step4-5: The UE3invokes the usage reporting procedure or any other service procedure or sends, to the SMF15, a Usage Information Reporting Message via the AMF11to report the network UE's usage information report. The usage information report has an Application Layer Group ID, an Application ID, a Layer 2 Group ID, a UE Application ID, an Application Server ID, a Usage Report on PC5, a Usage Report on Uu, and other kinds of relevant usage parameters. The usage report on PC5 includes a list of amount of data transmitted and received via PC5 with timestamp, a source ID, a destination ID and the UE location. The usage report on Uu includes a list of amount of data transmitted and received via Uu with timestamp, a source ID, a destination ID and the UE location.

Step6-8: The SMF15contacts the CHF13to create a CDR. The CHF13can cross-check the usage information report from different UEs.

In this solution, the SMF15exchanges messages with the CHF13for usage information collection and reporting. As its result, it allows the network to charge UE's usage accurately and flexibly.

Summary

Beneficially, the above described example embodiments include, although they are not limited to, one or more of the following functionalities:1) The proposed 5GS-based new charging solution allows the UE to report its usages on both PC5 and Uu interfaces to the network, which currently relies on the SMF/UPF to provide usage information on Uu interface only. It fills the gap that there is no usage reporting on PC5 interface in 5GS.2) The LTE-based ProSe charge solution cannot be used in 5GS straight forward, and the proposed 5GS-based new charging solution is based on the service-based architecture in 5GS.3) The new usage information reporting message can be triggered by the AF/the network/the application layer, which allows the AF and the network to flexibly obtain real-time charging information on the D2D direct communication.4) New PCC rules, new triggers and new measurement for monitoring and reporting UE usage allow the network to charge UE's usage accurately and flexibly.5) The AF can subscribe the charging policy from the PCF, who performs the UE configuration update procedure to deliver the charging policy to the UE.6) The AF can enforce the charging policy to the PCF, who performs the UE configuration update procedure to deliver the charging policy to the UE.

The CHF can cross-check the usage information report from different UEs. It reduces the chance of “fraud” usage reporting.

In order to provide these functionalities, the above example aspects describe exemplary methods comprising (at least some of) the following steps:1) NAS messages “Usage information reporting request/response” is used for UE usage information reporting, which enable on-demand request from the AF/PCF.2) PCC rules for usage information collection and reporting includes charging rules for PC5 and Usage Monitoring and Reporting rules for PC5.3) Pre-configured usage information collection and reporting for PC5 is used for NCIS.4) Measurements monitoring UE usage, which classifies the data flow usage on PC5 and Uu, respectively, and adds NCIS related parameters, such as an application layer group ID, a Layer 2 group ID, a UE application ID, an Application ID, and an Application server ID, is used. Both usage reports on PC5 and Uu have lists of amount of data transmitted and received with timestamp, a source ID, a destination ID and the UE location.
UE usage information reporting triggers, which can be based on AF's request or AF's subscription or UE's application layer message, are used for charging and usage reporting for NCIS in the D2D direct communication.
Benefits

New charging solutions are proposed for D2D direct communication based on 5GS. By using these solutions, it allows the network to charge UE usage accurately and flexibly.

System Overview

FIG.12schematically illustrates a mobile (cellular or wireless) telecommunication system1to which the above example embodiments are applicable.

In this network, users of mobile devices3(UEs) can communicate with each other and other users via respective base stations5and a core network7using an appropriate 3GPP radio access technology (RAT), for example, an E-UTRA and/or 5G RAT. It will be appreciated that a number of base stations5form a (radio) access network or (R)AN. As those skilled in the art will appreciate, whilst one mobile device3and one base station5are shown inFIG.12for illustration purposes, the system, when implemented, will typically include other base stations and mobile devices (UEs).

Each base station5controls one or more associated cells (either directly or via other nodes such as home base stations, relays, remote radio heads, distributed units, and/or the like). A base station5that supports E-UTRA/4G protocols may be referred to as an ‘eNB’ and a base station5that supports Next Generation/5G protocols may be referred to as a ‘gNBs’. It will be appreciated that some base stations5may be configured to support both 4G and 5G, and/or any other 3GPP or non-3GPP communication protocols.

The mobile device3and its serving base station5are connected via an appropriate air interface (for example the so-called ‘Uu’ interface and/or the like). Neighbouring base stations5are connected to each other via an appropriate base station to base station interface (such as the so-called ‘X2’ interface, ‘Xn’ interface and/or the like). The base station5is also connected to the core network nodes via an appropriate interface (such as the so-called ‘S1’, ‘N2’, ‘N3’ interface, and/or the like).

The core network7typically includes logical nodes (or ‘functions’) for supporting communication in the telecommunication system1. Typically, for example, the core network7of a ‘Next Generation’/5G system will include, amongst other functions, control plane functions (CPFs) and user plane functions (UPFs). It will be appreciated that the core network7may also include, amongst others: an Access and Mobility Management Function (AMF)11; a Policy Control Function (PCF)12, a Charging Function (CHF)13, a ProSe Function14; and a Session Management Function (SMF)15. It will be appreciated that in some systems (e.g. 3GPP Release 16 and onwards) the functionalities of the ProSe Function14may be provided by the PCF12(or another suitable node). Accordingly, whenever the present description refers to actions performed by the ProSe Function14, it is intended to cover the same actions being performed by the PCF12, when appropriate.

An Application Function (AF)16may also be provided within the core network7or coupled to the core network7. From the core network7, connection to an external IP network20(such as the Internet) is also provided.

The components of this system1are configured to perform one or more of the above described exemplary embodiments.

User Equipment (UE)

FIG.13is a block diagram illustrating the main components of the UE (mobile device3) shown inFIG.12. As shown, the UE includes a transceiver circuit31which is operable to transmit signals to and to receive signals from the connected node(s) via one or more antenna33. Although not necessarily shown inFIG.13, the UE will of course have all the usual functionality of a conventional mobile device (such as a user interface35) and this may be provided by any one or any combination of hardware, software and firmware, as appropriate. A controller37controls the operation of the UE in accordance with software stored in a memory39. The software may be pre-installed in the memory39and/or may be downloaded via the telecommunication network1or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system41and a communications control module43. The communications control module43is responsible for handling (generating/sending/receiving) signalling messages and uplink/downlink data packets between the UE3and other nodes, including (R)AN nodes5, core network nodes, and application functions. Such signaling includes appropriately formatted requests and responses relating to charging for device-to-device communications.

(R)AN Node

FIG.14is a block diagram illustrating the main components of an exemplary (R)AN node5(base station) shown inFIG.12. As shown, the (R)AN node5includes a transceiver circuit51which is operable to transmit signals to and to receive signals from connected UE(s)3via one or more antenna53and to transmit signals to and to receive signals from other network nodes (either directly or indirectly) via a network interface55. The network interface55typically includes an appropriate base station—base station interface (such as X2/Xn) and an appropriate base station—core network interface (such as S1/N2/N3). A controller57controls the operation of the (R)AN node5in accordance with software stored in a memory59. The software may be pre-installed in the memory59and/or may be downloaded via the telecommunication network1or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system61and a communications control module63. The communications control module63is responsible for handling (generating/sending/receiving) signalling between the (R)AN node5and other nodes, such as the UE3and the core network nodes/application functions. Such signaling includes appropriately formatted requests and responses relating to charging for device-to-device communications.

Core Network Node

FIG.15is a block diagram illustrating the main components of a generic core network node (or function) shown inFIGS.1to12, for example, the AMF11, the PCF12, the CHF13, the ProSe Function14, and the SMF15. It will be appreciated that the same block diagram may be applicable to the AF16as well. As shown, the core network node includes a transceiver circuit71which is operable to transmit signals to and to receive signals from other nodes (including the UE3and the (R)AN node5) via a network interface75. A controller77controls the operation of the core network node in accordance with software stored in a memory79. The software may be pre-installed in the memory79and/or may be downloaded via the telecommunication network1or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system81and at least a communications control module83. The communications control module83is responsible for handling (generating/sending/receiving) signaling between the core network node and other nodes, such as the UE3, (R)AN node5, the AFs16, and other core network nodes. Such signaling includes appropriately formatted requests and responses relating to charging for device-to-device communications.

Modifications and Alternatives

Detailed example embodiments have been described above. As those skilled in the art will appreciate, a number of modifications and alternatives can be made to the above example embodiments whilst still benefiting from the inventions embodied therein. By way of illustration only a number of these alternatives and modifications will now be described.

In the above description, the UE, the (R)AN node, and the core network node are described for ease of understanding as having a number of discrete modules (such as the communication control modules). Whilst these modules may be provided in this way for certain applications, for example where an existing system has been modified to implement the invention, in other applications, for example in systems designed with the inventive features in mind from the outset, these modules may be built into the overall operating system or code and so these modules may not be discernible as discrete entities. These modules may also be implemented in software, hardware, firmware or a mix of these.

Each controller may comprise any suitable form of processing circuitry including (but not limited to), for example: one or more hardware implemented computer processors; microprocessors; central processing units (CPUs); arithmetic logic units (ALUs); input/output (IO) circuits; internal memories/caches (program and/or data); processing registers; communication buses (e.g. control, data and/or address buses); direct memory access (DMA) functions; hardware or software implemented counters, pointers and/or timers; and/or the like.

In the above example embodiments, a number of software modules were described. As those skilled in the art will appreciate, the software modules may be provided in compiled or un-compiled form and may be supplied to the UE, the (R)AN node, and the core network node as a signal over a computer network, or on a recording medium. Further, the functionality performed by part or all of this software may be performed using one or more dedicated hardware circuits. However, the use of software modules is preferred as it facilitates the updating of the UE, the (R)AN node, and the core network node in order to update their functionalities.

The above example embodiments are also applicable to ‘non-mobile’ or generally stationary user equipment.

Various other modifications will be apparent to those skilled in the art and will not be described in further detail here.

Abbreviations and Terminology

3GPP 3rd Generation Partnership Project5GC 5G Core Network5GS 5G System5G-AN5G Access NetworkAF Application FunctionAMF Access and Mobility Management FunctionAN Access NetworkCHF Charging FunctionCM-CONNECTED Connection Management—CONNECTED StateCM-IDLE Connection Management—IDLE StateD2D Device to deviceDNN Data Network NameGFBR Guaranteed Flow Bit RateMM Mobility ManagementN1 Reference point between the UE and the Access and Mobility Management functionN2 Reference point between the (R)AN and the Access and Mobility Management functionNAS Non-Access-StratumNCIS Network Controlled Interactive ServiceNF Network FunctionNG Next GenerationNG-RAN Next Generation-Radio Access NetworkOAM Operations, Administration and MaintenanceOTT Over the TopPC3 The reference point between the UE and the ProSe FunctionPC5 The reference point between ProSe-enabled UEs used for control and userplane for ProSe Direct Discovery, ProSe Direct Communication and ProSe UE-to-Network RelayPCC Policy and Charging ControlPCF Policy Control FunctionPDB Packet Delay BudgetPDU Protocol Data UnitPER Packet Error RateProSe Proximity-based ServiceQFI QoS Flow IdentifierRAN Radio Access NetworkRRC Radio Resource ControlSBA Service-based ArchitectureSM Session ManagementSMF Session Management FunctionUE User EquipmentUPF User Plane FunctionUu The reference point between the UE and the radio access network

V2X Vehicle-to-everything

List All References Stated in the Present Specification

[1] 3GPP TS 23.501 V16.1.0[2] 3GPP TS 23.502 V16.1.0[3] 3GPP TS 23.503 V16.1.0[4] 3GPP TS 23.303 V15.1.0[5] 3GPP TS 32.277 V15.1.0

This application is based upon and claims the benefit of priority from European Patent Application No. 19200645.0, filed on Sep. 30, 2019, the disclosure of which are incorporated herein in their entirety by reference.

REFERENCE SIGNS LIST

1TELECOMMUNICATION SYSTEM3MOBILE DEVICE (UE)31TRANSCEIVER CIRCUIT33ANTENNA35USER INTERFACE37CONTROLLER39MEMORY41OPERATING SYSTEM43COMMUNICATION CONTROL MODULE5(R)AN NODE (GNB/ENB)51TRANSCEIVER CIRCUIT53ANTENNA55NETWORK INTERFACE57CONTROLLER59MEMORY61OPERATING SYSTEM63COMMUNICATION CONTROL MODULE7CORE NETWORK11AMF12PCF13CHF14PROSE FUNCTION15SMF16AF (PROSE APPLICATION SERVER)71TRANSCEIVER CIRCUIT75NETWORK INTERFACE77CONTROLLER79MEMORY81OPERATING SYSTEM83COMMUNICATION CONTROL MODULE20EXTERNAL IP NETWORK