Search

CN-122003837-A - Charging for 5MBS multicast system

CN122003837ACN 122003837 ACN122003837 ACN 122003837ACN-122003837-A

Abstract

Embodiments herein disclose an apparatus for charging for a multicast session. The apparatus receives a request originating from an Application Function (AF) to create, update, activate, deactivate, or release a Multicast Broadcast Service (MBS) session, and reports information indicating that the MBS session is created, updated, or deleted to a first charging function.

Inventors

  • J. A. Pereira Rodriguez
  • R. B. Natarajan
  • H. T. belline
  • P. GODIN
  • U. B. Elmali
  • B. Landace
  • A. Cha Ou Bu

Assignees

  • 诺基亚技术有限公司

Dates

Publication Date
20260508
Application Date
20240809
Priority Date
20230811

Claims (20)

  1. 1. An apparatus, comprising: At least one processor, and At least one memory storing instructions of a multicast and broadcast session management function (MB-SMF), which when executed by the at least one processor, cause the apparatus at least to perform: Receiving a request for creating a Multicast Broadcast Service (MBS) session originating from an Application Function (AF), and Reporting information indicating that the MBS session is created to a first charging function, wherein the information comprises at least one of the following: triggering the indication of the reported event; An identifier of the MBS session; an identifier of the AF from which the request originated; An identifier of a service area of the MBS session; an indication of whether the MBS session is a multicast session or a broadcast session; A description of quality of service (QoS) flows associated with the MBS session; the amount of data sent for the MBS session; the duration of the MBS session; the MBS session is active duration, or A billing identifier.
  2. 2. The apparatus of claim 1, wherein the instructions, when executed by the at least one processor, further cause the apparatus to at least perform: Receiving configuration information associated with the reporting of the information from the first charging function, wherein the configuration information includes at least one of: the reporting includes an indication of a volume reporting; the reporting includes an indication of duration reporting; the frequency of the reporting of the information; the threshold amount of reporting is required; Information identifying the event, or The charging identifier, and Wherein the reporting is based on the configuration information.
  3. 3. The apparatus of claim 1 or 2, wherein the event comprises at least one of: Releasing the MBS session; Activating the MBS session; Deactivation of the MBS session; Updating the MBS session; updating the MBS session QoS information; Updating the QoS information of the MBS session; update of the MBS session service area, or Updating an identifier of a service area for the MBS session.
  4. 4. An apparatus according to any one of claims 1 to 3, wherein the instructions, when executed by the at least one processor, further cause the apparatus to at least perform: Providing information to a multicast broadcast user plane function (MB-UPF), the information to be used to configure the MB-UPF to provide usage reports related to the MBs session; receiving a usage report indicating a data amount of the MBS session from the multicast broadcast user plane function (MB-UPF), and And sending a report comprising the data amount to the first charging function.
  5. 5. The apparatus according to any of claims 1 to 4, wherein the instructions, when executed by the at least one processor, further cause the apparatus to at least perform: Providing information to a multicast broadcast user plane function (MB-UPF) to be used to configure the MB-UPF to provide usage reports related to QoS flows of the MBs session; receiving a usage report indicating a data amount of the QoS flow for the MBS session from the multicast broadcast user plane function (MB-UPF), and A report is sent to the first charging function including the amount of data for the QoS flow.
  6. 6. The apparatus according to any of claims 1 to 5, wherein the instructions, when executed by the at least one processor, further cause the apparatus to at least perform: Receiving a request from a Session Management Function (SMF) or a second charging function for the data amount indicating that the data amount was transmitted for the MBS session or for at least one QoS flow for the MBS session; Providing multicast broadcast user plane function (MB-UPF) with information to be used to configure the MB-UPF to provide usage reports related to the MBS session or to the at least one QoS flow of the MBS session, and Receiving at least one usage report from the multicast broadcast user plane function (MB-UPF), the at least one usage report indicating an amount of data for the MBS session or the at least one QoS flow for the MBS session, and At least one message is sent to the SMF or to the second charging function, the at least one message comprising the data amount for the MBS session or the at least one QoS flow for the MBS session.
  7. 7. The apparatus of claim 6, wherein the request for the indication of the amount of data is at least one of: Nmbsmf _ MBSSession _ ContextStatusSubscribe request, Nmbsmf _ MBSSession _ ContextUpdate request, For a one-time-to-report request, Requests for periodic reporting, or Including a request for the charging key, and Wherein the message to the SMF or to the second charging function is at least one of: in response to the request indicating the amount of data, The request is notified of the request, Nmbsmf _ MBSSession _ ContextStatusSubscribe in response, Nmbsmf-MBSSession-ContextUpdate response, or Nmbsmf _ MBSSession _ ContextStatusNotify request.
  8. 8. The apparatus according to any of claims 1 to 7, wherein the instructions, when executed by the at least one processor, further cause the apparatus to at least perform: Receiving Nmbsmf _ MBSSession _ ContextStatusSubscribe requests for said MBS session from a Session Management Function (SMF), and A Nmbsmf _ MBSSession _ ContextStatusSubscribe response is sent that includes at least one of an identifier of the charging function or the charging identifier.
  9. 9. An apparatus, comprising: at least one processor; At least one memory including instructions for a Session Management Function (SMF), which when executed by the at least one processor, cause the apparatus at least to perform: Receiving a request from a User Equipment (UE) to join a Multicast Broadcast Service (MBS) session, and Reporting information indicating the UE to join the MBS session to a charging function, wherein the information comprises at least one of the following: An indication of an event triggering a report, wherein the event includes the UE joining the MBS session; An identifier of the MBS session; An identifier of the regional session; an identifier of the UE; An identifier of a service area of the MBS session; An indication of whether individual delivery is applied to the MBS session; A description of quality of service (QoS) flows associated with the MBS session; An identifier of a multicast broadcast session management function (MB-SMF) handling the MBS session. The time at which the report was created, or A billing identifier.
  10. 10. The apparatus of claim 9, wherein the instructions, when executed by the at least one processor, further cause the apparatus to at least perform: Transmitting Nmbsmf _ MBSSession _ ContextStatusSubscribe request for said MBS session to multicast broadcast session management function (MB-SMF), and Receiving Nmbsmf _ MBSSession _ ContextStatusSubscribe response including an identifier of the second charging function, and Performing at least one of: Selecting the charging function to report the UE joining the MBS session based on the identifier of the second charging function, or In the information indicating that the UE joined the MBS session, the identifier of the second charging function is provided.
  11. 11. The apparatus according to claim 9 or 10, wherein the instructions, when executed by the at least one processor, further cause the apparatus to at least perform: Transmitting Nmbsmf _ MBSSession _ ContextStatusSubscribe request for said MBS session to multicast broadcast session management function (MB-SMF), and Receiving Nmbsmf _ MBSSession _ ContextStatusSubscribe response including a charging identifier, and The charging identifier is provided within the information indicating that the UE joined the MBS session.
  12. 12. The apparatus according to any of claims 9 to 11, wherein the instructions, when executed by the at least one processor, further cause the apparatus to at least perform: Receiving configuration information associated with the reporting of the information from the charging function, wherein the configuration information includes at least one of: the reporting includes an indication of a volume reporting; the reporting includes an indication of duration reporting; the frequency of the reporting of the information; the threshold amount of reporting is required; Quota for said MBS session requiring said reporting; Information identifying the event; Information indicating how to report the amount of data of the MBS session delivered via individual delivery; Information indicating how to report the time at which the MBS session was delivered via individual delivery, or A second charging identifier to be used in said reporting, and Wherein the reporting is based on the configuration information.
  13. 13. The apparatus of claim 12, wherein the event comprises at least one of: the UE leaves the MBS session; Releasing the MBS session; Removal of the UE from the MBS session; termination of PDU sessions associated with said MBS session; Activating the MBS session; Deactivation of the MBS session; Updating the MBS session; updating the MBS session QoS information; Updating the QoS information of the MBS session; Updating an identifier of a service area for the MBS session; updating the MBS session service area; updating an identifier of a service area of the MBS session; a start time of individual delivery of data of the MBS session towards the UE; a stop time of individual delivery of data of the MBS session towards the UE; the UE moves out of the service area of the MBS session; the UE enters the service area of the MBS session, or A change in a location-related sub-session of the MBS session delivered to the UE.
  14. 14. The apparatus of any of claims 9 to 13, wherein the information comprises at least one of: Triggering the reported indication of the event; An identifier of the MBS session; an identifier of the multicast broadcast session management function (MB-SMF) handling the MBS session; an identifier of the regional session; an identifier of the UE; The charging identifier; The second charging identifier; An identifier of a service area of the MBS session; An indication of whether individual delivery is applied to the MBS session; A description of quality of service (QoS) flows associated with the MBS session; the amount of data sent for the MBS session; an amount of data transmitted for a QoS flow of the MBS session; A data amount for data of the MBS session transmitted via individual delivery; A data amount of data for QoS flows of the MBS session transmitted via individual delivery; the duration of the MBS session; the MBS session is the duration of the activity; Duration of time that the MBS session is deactivated, or The time at which the report was created.
  15. 15. The apparatus according to any of claims 9 to 14, wherein the instructions, when executed by the at least one processor, further cause the apparatus to at least perform: determining that data volume reporting is applicable to the MBS session and the UE; Providing configuration information to the UPF to be used for configuring the UPF to receive data of the MBS session if the User Plane Function (UPF) processing the PDU session related to the MBS session of the UE is determined to have not received the data of the MBS session; Providing additional configuration information to the UPF, the additional configuration information to be used to configure the UPF to provide usage reports related to the MBS session or to at least one QoS flow of the MBS session, and Receiving a usage report indicating a data amount of the MBS session or the at least one QoS flow of the MBS session from the User Plane Function (UPF); and sending a report comprising the data amount to the charging function.
  16. 16. The apparatus according to any of claims 9 to 14, wherein the instructions, when executed by the at least one processor, further cause the apparatus to at least perform: determining that data volume reporting is applicable to the MBS session and the UE; If an appropriate amount of data indicates that it has not been requested for the MBS session, sending a request to a multicast broadcast session management function (MB-SMF) for the amount of data that indicates that it is sent for the MBS session or at least one QoS flow for the MBS session; Receiving at least one message from said MB-SMF, said at least one message comprising said data amount for said MBS session or said at least one QoS flow for said MBS session, and Sending a report to the charging function, the report comprising the data amount for the MBS session or the at least one QoS flow for the MBS session.
  17. 17. The apparatus of claim 16, wherein the request for the indication of the amount of data is at least one of: Nmbsmf _ MBSSession _ ContextStatusSubscribe request, Nmbsmf _ MBSSession _ ContextUpdate request, For a one-time-to-report request, Requests for periodic reporting, or Including a request for the charging key, and Wherein the message from the MB-SMF is at least one of: in response to the request indicating the amount of data, The request is notified of the request, Nmbsmf _ MBSSession _ ContextStatusSubscribe in response, Nmbsmf-MBSSession-ContextUpdate response, or Nmbsmf _ MBSSession _ ContextStatusNotify request.
  18. 18. The apparatus according to 16 or 17, wherein the instructions, when executed by the at least one processor, further cause the apparatus to at least perform: Detecting at least one of the following: The UE joins the MBS session; the UE leaves the MBS session, Removal of the UE from the MBS session; termination of PDU sessions associated with said MBS session; The initiation of individual delivery of data of the MBS session towards the UE, or Stopping individual delivery of data of said MBS session towards said UE, and A request is sent for a one-time indication of a current amount of data that is sent for the MBS session for at least one QoS flow of the MBS session.
  19. 19. The apparatus according to any of claims 9 to 18, wherein the instructions, when executed by the at least one processor, further cause the apparatus to at least perform: determining that data volume reporting is applicable to the MBS session and the UE; Determining that MBS data of the MBS session is delivered to the user equipment via individual delivery in at least one QoS flow of the PDU session related to the MBS session; configuring the User Plane Function (UPF) that processes the PDU session to forward MBS data received in the at least one QoS flow and provide a usage report associated with the at least one QoS flow, and Determining to terminate delivering MBS data of the MBS session to the user equipment via individual delivery in at least one QoS flow of the PDU session related to the MBS session; Configuring the user plane function to stop forwarding MBS data received in the at least one QoS flow and to provide a usage report associated with the at least one QoS flow, and Receiving a usage report from the User Plane Function (UPF) indicating an amount of data of the at least one QoS flow, and Sending a report to the charging function comprising at least one of: an amount of data transmitted for the MBS session, wherein the amount of data does not include the received amount of data for the at least one QoS flow; An amount of data transmitted for QoS flows of the MBS session, wherein the amount of data does not include the received amount of data for the at least one QoS flow; a data amount for data of said MBS session being transmitted via individual delivery, wherein said data amount comprises said received data amount of said at least one QoS flow, or A data amount of data for QoS flows of the MBS session transmitted via individual delivery, wherein the data amount comprises the received data amount of the at least one QoS flow.
  20. 20. An apparatus, comprising: at least one processor; At least one memory storing instructions for a billing function, which when executed by the at least one processor, cause the apparatus to at least perform: Receiving a report from a multicast broadcast session management function (MB-SMF) that an MBs session is created, updated or deleted, wherein the report includes at least one of: an indication of an event triggering the report; An identifier of the MBS session; An identifier of the AF requesting the creation of the MBS session; a service area of the MBS session; An identifier of the regional session; an indication of whether the MBS session is a multicast session or a broadcast session; A description of quality of service (QoS) flows associated with the MBS session; the amount of data sent for the MBS session; an amount of data transmitted for a QoS flow of the MBS session; the duration of the MBS session; the MBS session is the duration of the activity; the duration that the MBS session is deactivated; the time at which the report was created, or Charging identifier, and The reported information is stored.

Description

Charging for 5MBS multicast system Technical Field Various example embodiments of the present disclosure relate to the field of wireless communications, and more particularly to charging for 5MBS multicast systems. Background Certain abbreviations that may appear in the specification and/or drawings are defined below. CTF charging trigger function CHF billing function ABMF account balance management function RF rate function CGF charging gateway function BD (digital video) account recording domain PDR packet detection rules FAR forwarding action rules In current 5G MBS architectures, charging may not currently be based on time or based on an amount associated with users of the multicast/broadcast service. Existing LTE architecture cannot be used for charging of MBMS services or 5G charging framework because, in contrast to LTE architecture, 5MBS introduces new network functions (e.g., MB-SMF, MB-UPF) in the 5G system architecture. Furthermore, multicast transmission and related mechanisms are quite different from the broadcast case, which is the only possibility in LTE. Disclosure of Invention According to some aspects, the subject matter of the independent claims is provided. Some embodiments are defined in the dependent claims. In a first aspect of the present disclosure, an apparatus is provided that includes at least one processor, and at least one memory storing instructions for a multicast broadcast session management function (MB-SMF), which when executed by the at least one processor, cause the apparatus to at least perform receiving a request from an Application Function (AF) to create, update, activate, deactivate or release a Multicast Broadcast Service (MBS) session, and reporting to a first charging function information indicating that the MBS session is created, updated or deleted, wherein the information includes at least one of an indication of an event triggering the report, an identifier of the MBS session, an identifier of an AF from which the request originated, an identifier of a service area of the MBS session, an indication of whether the MBS session is a multicast session or a broadcast session, a description of a quality of service (QoS) flow associated with the MBS session, an amount of data sent for the QoS flow of the MBS session, a duration of the MBS session being active, a duration of the MBS session, a duration of the inactivity, a duration of the MBS, a duration of the charging report, or a duration of the MBS. In a second aspect of the disclosure, an apparatus is provided that includes at least one processor, at least one memory including instructions for a Session Management Function (SMF), which when executed by the at least one processor, cause the apparatus to at least perform receiving a request to join a Multicast Broadcast Service (MBS) session from a User Equipment (UE), and reporting information to a charging function indicating that the UE joined the MBS session, wherein the information includes at least one of an indication of an event triggering a report, wherein the event includes that the UE joined the MBS session, an identifier of a zone session, an identifier of the UE, an identifier of a service zone of the MBS session, an indication of whether individual delivery is applied to the MBS session, a description of a quality of service (QoS) flow associated with the MBS session, and an identifier of the multicast broadcast session management function (MB-SMF) handling the MBS session. The time at which the report was created, or a billing identifier. In a third aspect of the disclosure, an apparatus is provided that includes at least one processor, at least one memory storing instructions for a charging function that, when executed by the at least one processor, cause the apparatus to at least perform receiving a report from a multicast broadcast session management function (MB-SMF) that an MBS session is created, updated or deleted, wherein the report includes at least one of an indication of an event triggering the report, an identifier of the MBS session, an identifier of an AF requesting creation of the MBS session, a service area of the MBS session, an identifier of a zone session, an indication of whether the MBS session is a multicast session or a broadcast session, a description of a quality of service (QoS) flow associated with the MBS session, an amount of data sent for the QoS flow of the MBS session, a duration of the MBS session being active, a duration of a deactivation of the MBS session, a time the report being created, or a charging identifier, and storing the reported information. In a fourth aspect of the disclosure, an apparatus is provided that includes at least one processor, at least one memory storing instructions for a charging function that, when executed by the at least one processor, cause the apparatus to at least perform receiving a report from a Session Management Function (SMF) indicating that a UE joined an MBS session, wherein