Charging for 5MBS multicast systems

Abstract

The embodiments herein disclose an apparatus for charging for multicast sessions 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, to a first charging function, information indicating that the MBS session is created, updated, or deleted.

Description

[0001] CHARGING FOR 5MBS MULTICAST SYSTEMS

[0002] Technical Field:

[0003] Various example embodiments of the present disclosure relate to the field of wireless communication, and more particularly relate to charging for 5MB S multicast systems.

[0004] Background:

[0005] Certain abbreviations that may be found in the description and / or in the figures are herewith defined as follows.

[0006] CTF Charging Trigger Function

[0007] CHF Charging Function

[0008] ABMF Account Balance Management Function

[0009] RF Rating Function

[0010] CGF Charging Gateway Function

[0011] BD Billing Domain

[0012] PDR Packet Detection Rule

[0013] FAR Forward Action Rules

[0014] It is currently not possible in current 5G MBS architecture to apply charging based on time or based on volume associated with a user of a multicast / broadcast service.

[0015] Existing LTE architecture cannot be used for charging for MBMS service or the 5G charging framework, since 5MB S has new Network functions (example - MB-SMF, MB-UPF) introduced in the 5G system architecture compared to LTE architecture. Furthermore, multicast transmissions and relevant mechanisms are completely different than broadcast case, whereas the broadcast was the only possibility in LTE.

[0016] Summary:

[0017] According to some aspects, there is provided the subject matter of independent claims. Some embodiments are defined in the dependent claims.

[0018] In a first aspect of the present disclosure, there is provided an apparatus comprising: at least one processor; and at least one memory storing instructions for a multicast and broadcast session management function (MB-SMF) that, when executed by the at least one processor, cause the apparatus at least to perform: receiving a request, originating 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 comprises at least one of: an indication of an event that triggered the reporting; 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 identifier of the Area Session; an indication whether the MBS session is a multicast session or a broadcast session; a description of Quality of Service(QoS) flows related to the MBS session; a data volume transmitted for the MBS session; a data volume transmitted for a QoS flow of the MBS session; a duration of the MBS session; a duration for which the MBS session was active; a duration for which the MBS session was deactivated; a time when the report of the reporting is created; or a charging identifier.

[0019] In a second aspect of the present disclosure, there is provided an apparatus comprising: at least one processor; at least one memory comprising instructions for a session management function (SMF) that, 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, to a charging function, information indicating that the UE joined the MBS session, wherein the information comprises at least one of: an indication of an event that triggered the report, wherein the event comprises that the UE joined the MBS session; an identifier of the MBS session; an identifier of the Area Session; an identifier of the UE; an identifier of a service area of the MBS session; an indication whether individual delivery is applied for the MBS session; a description of Quality of Service(QoS) flows related to the MBS session; an identifier of a multicast broadcast session management function (MB-SMF) handling the MBS session, a time when the report is created; or a charging identifier.

[0020] In a third aspect of the present disclosure, there is provided an apparatus comprising: 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 at least to perform: receive from a multicast broadcast session management function (MB-SMF) a report that an MBS session is created, updated or deleted, wherein the report comprises at least one of: an indication of the event that triggered 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 Area Session; an indication whether the MBS session is a multicast session or a broadcast session; a description of Quality of Service(QoS) flows related to the MBS session; a data volume transmitted for the MBS session; a data volume transmitted for a QoS flow of the MBS session; a duration of the MBS session; a duration for which the MBS session was active; a duration for which the MBS session was deactivated; a time when the report is created; or a charging identifier; and store the reported information.

[0021] In a fourth aspect of the present disclosure, there is provided an apparatus comprising: 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 at least to perform: receive a report from a session management function (SMF) indicating that the UE joined the MBS session, wherein the report comprises at least one of: an indication that the UE joined the MBS session as event that triggered the report; an Identifier of the MBS session; an Identifier of the Area Session an Identifier of the UE a service area of the MBS session; an identifier of a second charging function an indication whether individual delivery is applied for the MBS session; a description of Quality of Service(QoS) flows related to the MBS session; an identifier of the multicast broadcast session management function (MB-SMF) handling the MBS session, a time when the report is created; or a charging identifier; and store the reported information.

[0022] Brief Description of the Drawings

[0023] FIG. 1 is an illustration of a converged charging architecture in accordance with one or more embodiments;

[0024] FIG. 2 illustrates a system architecture for 5GMBS in accordance with one or more embodiments;

[0025] FIG. 3 illustrates a converged charging architecture in accordance with one or more embodiments;

[0026] FIG. 4A and 4B is a diagram showing operations performed by network entities of a communication network during MBS session creation without PCC;

[0027] FIG. 5 is a diagram showing operations performed by network entities of a communication network during MBS session update without PCC;

[0028] FIG. 6 is a diagram showing operations performed by network entities of a communication network during MBS session deletion without PCC; FIG. 7A is a diagram showing operations performed by network entities of a communication network during MBS session deletion without PCC;

[0029] FIG. 7B is part of a diagram showing operations performed by network entities of a communication network during PDU session modification for UE joining Multicast MBS session;

[0030] FIG. 8 is a diagram showing operations performed by network entities of a communication network during UE initiated multicast MBS session leave;

[0031] FIG. 9 is a diagram showing operations performed by network entities of a communication network during MBS session activation procedure;

[0032] FIG. 10 is a diagram showing operations performed by network entities of a communication network during MBS session activation procedure;

[0033] FIG. 11 is a diagram showing operations performed by network entities of a communication network during MBS session activation without PCC;

[0034] FIG. 12 is a diagram showing operations performed by network entities of a communication network during MBS session release or multicast session leave requested by the network;

[0035] FIG. 13 is a diagram showing operations performed by network entities of a communication network during Xn based handover with MBS session;

[0036] FIG. 14 is a diagram showing operations performed by network entities of a communication network during N2 based handover with MBS session;

[0037] FIG. 15A and 15B are illustrations of MBMS online charging architecture and MBMS offline charging architecture respectively;

[0038] FIG. 16A and 16B is a diagram showing enhancements to MBS session creation in accordance with one or more embodiments;

[0039] FIG. 17 is a diagram showing enhancements to MBS session update in accordance with one or more embodiments;

[0040] FIG. 18 is a diagram showing enhancements to MBS session deactivation / activation based on received multicast data in accordance with one or more embodiments;

[0041] FIG. 19 is a diagram showing enhancements to MBS session deactivation / activation based on received multicast data in accordance with one or more embodiments;

[0042] FIG. 20A and 20B is a diagram showing enhancements to UE joining Multicast MBS session, option 1;

[0043] FIG. 21 A and 21B is a diagram showing enhancements to UE joining Multicast MBS session, option 2; FIG. 22A and 22B is a diagram showing enhancements to UE joining Multicast MBS session, option 3;

[0044] FIG. 23 is a diagram showing enhancements to UE initiated Multicast MBS session leave;

[0045] FIG. 24 is a diagram showing enhancements to MBS session activation / deactivation / update procedure;

[0046] FIG. 25 is a diagram showing enhancements to MBS session release procedure;

[0047] FIG. 26 is a diagram showing enhancements to join procedures if NG RAN node does not support 5MB S and individual delivery; and

[0048] FIG. 27 is a diagram showing enhancements to handover related to start and stop of individual delivery;

[0049] Detailed Description

[0050] Example embodiments now will be described with reference to the accompanying drawings. The invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this invention will be thorough and complete, and will fully convey its scope to those skilled in the art. The terminology used in the detailed description of the example embodiments illustrated in the accompanying drawings is not intended to be limiting. In the drawings, like numbers refer to like elements.

[0051] The specification may refer to “an”, “one” or “some” embodiment s) in several locations. This does not necessarily imply that each such reference is to the same embodiment(s), or that the feature only applies to a single embodiment. Single features of different embodiments may also be combined to provide other embodiments. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless expressly stated otherwise. It will be further understood that the terms “includes”, “comprises”, “including” and / or “comprising” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. In other words, the terms “includes”, “comprises”, “including” and / or “comprising” is to be understood as being open-ended. As used herein, whenever the phrase “at least one of the following” precedes a list of elements, wherein the elements are joined by “and” or “or”, it means that at least any one of the elements or at least all the elements are present. As used herein, the term “and / or” includes any and all combinations and arrangements of one or more of the associated listed items.

[0052] Conditional language — such as “can” or “may” — among others, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments could include, while other embodiments may not include certain features, elements, and / or steps. Thus, such conditional language is not generally intended to imply that features, elements, and / or steps are in any way required for one or more embodiments. It will be understood that when an element is referred to as being “connected” or “coupled” to another element, it can be directly connected or coupled to the other element or intervening elements may be present. Furthermore, “connected” or “coupled” as used herein may include wirelessly connected or coupled.

[0053] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0054] The figures depict a simplified structure only showing some elements and functional entities, all being logical units whose implementation may differ from what is shown. The connections shown are logical connections; the actual physical connections may be different. In addition, all logical units described and depicted in the figures include the software and / or hardware components required for the unit to function. Further, each unit may comprise within itself one or more components, which are implicitly understood. These components may be operatively coupled to each other and be configured to communicate with each other to perform the function of the said unit.

[0055] As used herein, the term “circuitry” may refer to at least one of the following: a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry); b) combinations of hardware circuits and software, such as (as applicable): (i) a combination of analog and / or digital hardware circuit(s) with software / firmware and (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions); or c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.

[0056] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

[0057] For individual delivery of a multicast session via a RAN node that does not support MBS, the MBS data received by the MB-UPF is replicated towards the UPF(s) where individual delivery is performed in the following way:

[0058] The MB-SMF configures the MB-UPF to receive packets related to an MBS session, to replicate those packets and forward them towards multiple UPFs via GTP tunnels if unicast transport over N19mb is applied, or via a single GTP tunnel if multicast transport over N19mb is applied.

[0059] The SMF(s) instructs the UPF to receive packets related to a Multicast MBS session from an MB-UPF over N19mb, to replicate those packets and to forward them in multiple PDU sessions.

[0060] For the SMF and the UPF (for 5GC individual delivery), packet detection, replication and forwarding for an MBS session is realized by PDR and FAR of the PDU session in which the UE has joined the MBS session:

[0061] The SMF instructs the UPF to associate the PFCP session of the PDU session with an MBS session.

[0062] A new PDR with Source Interface "Core" is used to detect MBS data from N19mb.

[0063] NOTE: This PDR is also containing the MBS Session ID to enable a single detection of the incoming MBS data for multiple PDU sessions at the UPF. For unicast transport over N19mb, the SMF requests UPF to allocate N19mb Tunnel Info if not allocated.

[0064] For multicast transport over N19mb, the SMF includes the low layer source specific multicast address information and C-TEID to UPF.

[0065] If the SMF wants to maintain the MBS data reception over N19mb but suspends the delivery of the data to the UE's PDU session, the Action of FAR set to "drop" (e.g. when the UE is switching from 5GC Individual delivery to 5GC Shared delivery due to the UE moving from MBS non-supporting NG-RAN to MBS supporting NG-RAN). Otherwise the SMF remove the related PDR and FAR.

[0066] For 5GC Shared MBS traffic delivery of a multicast session via a RAN node that supports MBS (i.e. MB-UPF delivers user plane data to NG-RAN supporting MBS), if the transport network supports IP multicast, the NG-RAN node uses multicast transport via a common GTP-U tunnel per MBS session, otherwise unicast transport via separate GTP-U tunnel per MBS session per NG-RAN node is used.

[0067] For shared delivery, if unicast transport over N3mb applies, the MB-SMF instructs MB-UPF to replicate the received MBS packets and forward them towards multiple RAN nodes via separate GTP tunnel. For shared delivery, if multicast transport over N3mb applies, the MB- SMF instructs the MB-UPF to replicate the received MBS data and forwards the data via a single GTP tunnel.

[0068] For the MB-SMF and MB-UPF, packet detection, replication and forwarding for an MBS session is realized by using for each MBS session one PDR that detects the incoming MBS packets and points to one FAR that describes the forwarding of the data towards multiple destinations (UPFs or RAN nodes):

[0069] A PFCP session is created when the MBS Session is started, regardless of multicast or unicast transport over N3mb and N19mb.

[0070] For Multicast transport over N3mb and N19mb, the destination in the FAR contains the MB-UPF IP Multicast Distribution Info.

[0071] For unicast transport over N3mb and N19mb, the FAR in the PFCP session may contain multiple destinations represented by the NG-RAN N3mb Tunnel Info and UPF N19mb Tunnel Info (if applicable). Those procedures are are illustrated for informational purposes in FIGS. 4-14 (for textual description refer to TS 23.247):

[0072] TS 32.273 describesCharging management; Multimedia Broadcast and Multicast Service (MBMS) charging standards.

[0073] The TS 32.273 specification provides the details for 4G / LTE and GPRS Technologies but lacks details necessary for 5G.

[0074] The functional architectures illustrated in FIG. 15A and 15B cover the online and offline charging scenario for MBMS 4G.

[0075] The above architectures are missing the support of MBMS in 5G Technology (Converged Charging - Nchf service).

[0076] In addition, he collection and reporting of MBS specific charging information are not specified by TS 23.247.

[0077] Embodiments described and illustrated herein address charging for Multicast sessions.

[0078] Common to all options and cases:

[0079] • SMF is aware of the individual UE joining or leaving the multicast MBS Session (based on UE ID and the associated MBS Session ID) as well as the release of an MBS session that a UE has joined and reports those events to the CHF.

[0080] • SMF can also report the activation and deactivation of an MBS session that a UE joined, the service area of the MBS session, and / or QoS flows for the MBS session to the CHF.

[0081] • CHF may configure the SMF with rules what charging information to report for the UE and MBS session when the SMF reports that a UE joined an MBS session.

[0082] The MB-SMF can create a charging session with CHF when the MBS session is created in 5GC (note that such creation is known as shown in the figures above of the 3GPP standards) [See TS23.247 MBS Session Creation],

[0083] • MB-SMF can report to the CHF the creation, update, activation, deactivation and release of an MBS session, the service area of the MBS session, QoS flows for an MBS session, data volumes transmitted for the MBS session, type of MBS session (multicast or broadcast), and / or the entity (e.g. AF) that requested the creation of the session

[0084] • CHF may configure the MB-SMF with rules what charging information to report for the MBS session when the MB-SMF reports the creation of that MBS session.

[0085] • MB-SMF can configure MB-UPF to provide usage reports for the MBS session, for instance to obtain the data volume related to the MBS session

[0086] Case#l - Multicast MBS session with Individual traffic delivery

[0087] • SMF can also report when it starts and terminates individual delivery to the CHF.

[0088] • Alternatively, the individual delivery is not reported and the same charging as outlined for shared delivery is used.

[0089] • SMF via Nchf interface provides the charging information to CHF based on data report from UPF for the UE’s PDU session.

[0090] • In a variant, the SMF subtracts the data volume for individual delivery MBS QoS flow(s) from the data volume reported for the PDU session to the CHF.

[0091] • In a variant, the SMF reports the data volume for individual delivery MBS QoS flow(s) to the CHF.

[0092] • SMF may configure the UPF for individual delivery related QoS flow data usage reporting when it configures the UPF to forward data MBS data within the PDU session using those QoS flows

[0093] Case#2 - Multicast MBS session with Shared traffic delivery

[0094] Option 1: Correlation of data reports in SMF

[0095] • SMF subscribes at MB-SMF to periodic reporting of data volume transmitted for entire MBS session or QoS flows related to an MBS session, for instance if CHF requested volume reporting when some UE joined the MBS session.

[0096] • MB-SMF can configure MB-UPF to provide usage reports for the MBS session, for instance to obtain the data volume related to the MBS session.

[0097] • MB-SMF then forwards volume / data reports received from MB-UPF for the multicast session to the SMF.

[0098] • SMF provides volume reports of the Multicast Session (if received from MB-SMF) for each UE to the charging function (CHF). • When the UE leaves the Multicast Session, SMF signals the CHF accordingly (session termination, session release, UE leaving session) and a final volume report.

[0099] • SMF may also request a volume counter for the MBS session whenever a UE joins or leaves the MBS session and either report this information directly to the CHF or calculate and report the MBS-session related volume consumed by the UE. SMF or CHF can calculate the MBS-session related volume consumed by the UE by subtracting the volume counter at the time the UE leaves from the volume counter at the time the UE joins.

[0100] Option 2: correlation of data reports in CHF

[0101] • The CHF correlates the information about a UE joining or leaving an MBS session reported by the SMF with information about the MBS session reported by the MB-SMF (for instance related to data volumes) to derive the MBS session related charging information for that UE.

[0102] • In a variant, the MB-SMF provides a CHF ID of a CHF handling the MBS session towards the SMF in in the Context Status Subscribe response, and the SMF then either contacts that CHF when providing reports related to this MBS session, or the SMF interacts with another CHF but provides the CHF ID to that other CHF to enable that other CHF to obtain information related to the MBS session from the CHF handling the MBS session.

[0103] • In a variant, the CHF handling a UE that joined a multicast session discovers the MB- SMF that handles the multicast session (e.g. via a query to the NRF) and sends a request for charging information related to the multicast session to the MB-SMF.

[0104] • In an embodiment 1, both the SMF and MB-SMF provide the MBS session ID to the CHF and the CHF uses the MBS session ID to correlate the information. The MB-SMF provides information about QoS flows of the MBS session in the Context Status Subscribe response to the SMF. SMF and MB-SMF may also report information related to QoS flows within the MBS session and use the same identifier(s), as indicated by the MB-SMF in the Context Status Subscribe response, forthose QoS flow(s) together with the MBS session ID.

[0105] • In an embodiment 2, the MB-SMF or CHF assigns a Charging ID for the entire MBS session or for a QoS flow related to the MBS session; if the CHF assigns the ID it provides it to the MB-SMF when the MB-SMF reports the creation of the MBS session. The MB-SMF provides the Charging ID to SMFs in the Context Status Subscribe response. Both the MB-SMF and the SMF use this Charging ID in the Charging Data report message to the CHF related to the MBS session or the Qos Flow to update the CHF with the data reports.

[0106] • In summary, the Charging Data Request (update / termination) message contains a CDR correlation ID which equals either the MBS session id, or charging id depending on the above-described option.

[0107] • For online charging and converged charging with quota management, the CHF provides time-based quota to SMFs, but may adjust the quota based on the volume / bandwidth of the MBS session as reported by the MB-SMF.

[0108] Option 3: Configuring UPF to also receive MBS data during shared delivery and provide usage reports.

[0109] • If MBS volume charging applies for an MBS session, regardless of whether shared delivery or individual delivery is used towards UEs served by the SMF, the SMF requests the MB-SMF to deliver data for the MBS session to the UPF and configures the UPF to provide usage reports related to the incoming data of the MBS session. The SMF provides information about the data volume of the MBS session, as reported by the UPF, in charging records related to the MBS session and UE within the MBS session. o If no individual delivery is required, the SMF does not configure the UPF to forward the received MBS data in any PDU session and the UPF then discards the data.

[0110] FIGS. 16-27 illustrate enhancement to the various procedures of the 3 GPP standard.

[0111] Charging Data Request message contents

[0112] Charging Data Response message contents

[0113]

[0114] It’s required to introduce new triggers for Charging. This is accomplished in step 4 and the last step of the flow.

[0115] According to TS 32.255, when a PDU session starts, and the converged charging is activated, the SMF invokes a Charging Data Request [Initial] towards the CHF to get authorization to start based on the default triggers. The SMF is optionally provided in a Charging Data Response [Initial] to override the default triggers, with a set of chargeable event triggers to be enabled, and the associated category (on this case deferred report).

[0116] The triggers remain active until they are updated or disabled by subsequent Charging Data Response [Update] from the CHF or the PDU session is terminated. On this scenario, taking in account that this is a Multicast Session then it’s required to trigger charging for Time.

[0117] Table 1: Default Trigger Conditions in SMF

[0118]

[0119]

[0120] The PDU Session Charging information table (TS 32.255 - Table 6.2.1.2.1) shall be considered too (new attribut in green)

[0121] Structure of PDU Session Charging Information

[0122] The charging aspects of the 5G multicast-broadcast services defined in TS 23.247, include: o The charging scenarios for multicast and broadcast services; o The charging enhancement to NFs (i.e. SMF, MB-SMF) for multicast and broadcast services; o The charging information and relevant charging procedures for multicast and broadcast services; o The corresponding Open API and ASN.1 for multicast and broadcast services charging.

[0123] The embodiments herein disclose a device comprising a processor which can control the device’s operations. The processor may also be referred to as a central processing unit (CPU). The memory, which may include both read-only memory (ROM) and random access memory (RAM), can provide instructions and data to the processor. The memory and the processor may be operatively coupled. The memory may store computer readable instructions / computer program code. The computer readable instructions / computer program code may be pre-stored to the memory or, alternatively or additionally, they may be received, by the device, via an electromagnetic carrier signal and / or may be copied from a physical entity such as a computer program product. Execution of the computer readable instructions by the processor, can cause the device to carry out the example embodiments described herein.

[0124] In the context of this document, a “memory” (also referred to as “computer-readable media” or “computer-readable medium”) may be any non-transitory media or medium or means that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer. The term “non-transitory,” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM). The device may have means implemented in any suitable form to perform the embodiments disclosed herein. For example, the means may be implemented in a circuitry (e.g., the memory and processor) or a software module.

[0125] As explained above and reiterated below, the present disclosure includes, without limitation, the following example implementations.

[0126] Clause 1. An apparatus comprising: at least one processor; and at least one memory storing instructions for a multicast and broadcast session management function (MB-SMF) that, when executed by the at least one processor, cause the apparatus at least to perform: receiving a request, originating 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 comprises at least one of: an indication of an event that triggered the reporting; 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 identifier of the Area Session; an indication whether the MBS session is a multicast session or a broadcast session; a description of Quality of Service(QoS) flows related to the MBS session; a data volume transmitted for the MBS session; a data volume transmitted for a QoS flow of the MBS session; a duration of the MBS session; a duration for which the MBS session was active; a duration for which the MBS session was deactivated; a time when the report of the reporting is created; or a charging identifier.

[0127] Clause 2. The apparatus of clause 1, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform: receiving, from the first charging function, configuration information associated with the reporting of the information, wherein the configuration information comprises at least one of the following: an indication that the reporting comprises volume reporting; an indication that the reporting comprising duration reporting; a frequency of the reporting of the information; a threshold volume requiring the reporting; information identifying the event; or the charging identifier; and wherein the reporting is based on the configuration information.

[0128] Clause 3. The apparatus of clauses 1 or 2, wherein the event comprises at least one of the following: release of the MBS session; activation of the MBS session; deactivation of the MBS session; update of the MBS session; update of the MBS session QoS information; update of the QoS information of the MBS session; update of the MBS session service area; update of an identifier of a service area for the MBS session.

[0129] Clause 4. The apparatus of any of clauses 1 to 3, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform: providing, to a multicast-broadcast user plane function (MB-UPF), information to be used to configure the MB-UPF to provide usage reports related to the MBS session; receiving, from the multicastbroadcast user plane function (MB-UPF), a usage report indicating a data volume of the MBS session; and sending, to the first charging function, a report comprising the data volume.

[0130] Clause 5. The apparatus of any of clauses 1 to 4, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform: providing, to a multicast-broadcast user plane function (MB-UPF), information to be used to configure the MB-UPF to provide usage reports related to a QoS flow of the MBS session; receiving, from the multicast-broadcast user plane function (MB-UPF), a usage report indicating a data volume for the QoS flow of the MBS session; and sending, to the first charging function, a report comprising the data volume for the QoS flow.

[0131] Clause 6. The apparatus of any of clauses 1 to 5, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform: receiving, from a session management function (SMF) or a second charging function, a request to indicate the data volume transmitted for the MBS session or for at least one QoS flow of the MBS session; providing, to a multicast-broadcast user plane function (MB-UPF), information to be used to configure the MB-UPF to provide usage reports related to the MBS session or related to the at least one QoS flow of the MBS session; and receive at least one usage report from the multicast-broadcast user plane function (MB-UPF) indicating a data volume for the MBS session or for the at least one QoS flow of the MBS session; and sending to the SMF or to the second charging function at least one message comprising the data volume for the MBS session or for the at least one QoS flow of the MBS session.

[0132] Clause 7. The apparatus of clause 6, wherein the request to indicate the data volume is at least one of the following: a Nmbsmf MBSSession ContextStatusSubscribe request, a

[0133] Nmbsmf MBSSession ContextUpdate request, a request for one-time reporting, a request for periodic reporting, or a request comprising the charging key; and wherein the message to the SMF or to the second charging function is at least one of the following: a response to the request to indicate the data volume, a notification request, a Nmbsmf_MBSSession_ContextStatusSubscribe response, a Nmbsmf_MBSSession_ContextUpdate response, or a Nmbsmf_MBSSession_ContextStatusNotify request.

[0134] Clause 8. The apparatus of any of clauses 1 to 7, wherein the instructions, when executed by the at least one processor, further cause the apparatus to at least perform: receiving from a session management function (SMF) an Nmbsmf MBSSession ContextStatusSubscribe request for the MBS session; and sending an Nmbsmf MBSSession ContextStatusSubscribe response comprising at least one of the following: an identifier of the charging function or the charging identifier.

[0135] Clause 9. An apparatus comprising: at least one processor; at least one memory comprising instructions for a session management function (SMF) that, 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, to a charging function, information indicating that the UE joined the MBS session, wherein the information comprises at least one of: an indication of an event that triggered the report, wherein the event comprises that the UE joined the MBS session; an identifier of the MBS session; an identifier of the Area Session; an identifier of the UE; an identifier of a service area of the MBS session; an indication whether individual delivery is applied for the MBS session; a description of Quality of Service(QoS) flows related to the MBS session; an identifier of a multicast broadcast session management function (MB-SMF) handling the MBS session; a time when the report is created; or a charging identifier.

[0136] Clause 10. The apparatus of clause 9, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform: sending to a multicast broadcast session management function (MB-SMF) an mbsmf MBSSession ContextStatusSubscribe request for the MBS session; and receiving an Nmbsmf MBSSession ContextStatusSubscribe response comprising an identifier of a second charging function; and performing at least one of the following: selecting the charging function to report that that the UE joined the MBS session based on the identifier of the second charging function; or provide the identifier of the second charging function in the information indicating that the UE joined the MBS session.

[0137] Clause 11. The apparatus of clauses 9 or 10, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform: sending to a multicast broadcast session management function (MB-SMF) an

[0138] Nmbsmf MBSSession ContextStatusSubscribe request for the MBS session; and receiving an Nmbsmf MBSSession ContextStatusSubscribe response comprising an charging identifier; and providing the charging identifier within the information indicating that that the UE joined the MBS session.

[0139] Clause 12. The apparatus of any of clauses 9 to 11, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform: receiving, from the charging function, configuration information associated with the reporting of the information, wherein the configuration information comprises at least one of the following: an indication that the reporting comprises volume reporting; an indication that the reporting comprises duration reporting; a frequency of the reporting of the information; a threshold volume that requires the reporting; a quota for the MBS session that requires the reporting; information identifying the event; information indicating how to report volume of data of the MBS session delivered via individual delivery; information indicating how to report time the MBS session was delivered via individual delivery; or a second charging identifier to be used in the reporting; and wherein the reporting is based on the configuration information.

[0140] Clause 13. The apparatus of clause 12, wherein the event comprises at least one of: the UE leaving the MBS session; release of the MBS session; removal of the UE from the MBS session; termination of a PDU session related to the MBS session; activation of the MBS session; deactivation of the MBS session; update of the MBS session; update of the MBS session QoS information; update of the QoS information of the MBS session; update of an identifier of a service area for the MBS session; update of the MBS session service area; update of an identifier of a service area of the MBS session; start time of individual delivery of data of the MBS session towards the UE; stop time of individual delivery of data of the MBS session towards the UE; the UE moving out of the service area of the MBS session; the UE entering the service area of the MBS session; or change of location dependent sub session of the MBS session delivered to the UE. Clause 14. The apparatus of any of clauses 9 to 13, wherein the information comprises at least one of: an indication of the event that triggered the reporting; 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 Area 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 whether individual delivery is applied for the MBS session; a description of Quality of Service(QoS) flows related to the MBS session; a data volume transmitted for the MBS session; a data volume transmitted for a QoS flow of the MBS session; a data volume for data of the MBS session transmitted via individual delivery; a data volume for data for a QoS flow of the MBS session transmitted via individual delivery; a duration of the MBS session; a duration for which the MBS session was active; a duration for which the MBS session was deactivated; or a time when the report is created.

[0141] Clause 15. The apparatus of any of clauses 9 to 14, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform: determining data volume reporting applies for the MBS session and the UE; if the user plane function (UPF) handling the PDU session related to the MBS session of the UE is determined to not yet receive data of the MBS session, providing the UPF with configuration information to be used to configure the UPF to receive data of the MBS session; providing the UPF with additional configuration information to be used configure the UPF to provide a usage report related to the MBS session or at least one QoS flow of the MBS session; and receiving from the user plane function (UPF) a usage report indicating a data volume of the MBS session or the at least one QoS flow of the MBS session; sending the charging function a report comprising the data volume.

[0142] Clause 16. The apparatus of any of clauses 9 to 14, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform: determining data volume reporting applies for the MBS session and the UE; if suitable data volume indications have not yet been requested for the MBS session, sending, to a multicast broadcast session management function (MB-SMF), a request to indicate the data volume transmitted for the MBS session or at least one QoS flow of the MBS session; receiving from the MB-SMF at least one message comprising the data volume for the MBS session or the at least one QoS flow of the MBS session; and sending to the charging function a report comprising the data volume for the MBS session or the at least one QoS flow of the MBS session.

[0143] Clause 17. The apparatus of clause 16, wherein the request to indicate the data volume is at least one of the following: a Nmbsmf MBSSession ContextStatusSubscribe request, a Nmbsmf MBSSession ContextUpdate request, a request for one-time reporting, a request for periodic reporting, or a request comprising the charging key; and wherein the message from the MB-SMF is at least one of the following: a response to the request to indicate the data volume, a notification request, a Nmbsmf MBSSession ContextStatusSubscribe response, a Nmbsmf_MBSSession_ContextUpdate response, or a Nmbsmf_MBSSession_ContextStatusNotify request.

[0144] Clause 18. The apparatus of 16 or 17, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform: detecting at least one of the following: the UE joining the MBS session; the UE leaving the MBS session, removal of the UE from the MBS session; termination of a PDU session related to the MBS session; start of individual delivery of data of the MBS session towards the UE, or nstop of individual delivery of data of the MBS session towards the UE; and sending a request for a one-time indication of the current data volume transmitted for the MBS session for at least one QoS flow of the MBS session.

[0145] Clause 19. The apparatus of any of clauses 9 to 18, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform: determining data volume reporting applies for the MBS session and the UE; determining to deliver MBS data of the MBS session via individual delivery in at least one QoS flow of the PDU session related to the MBS session to the user equipment; configure the user plane function (UPF) handling the PDU session to forward received MBS data in the in at least one QoS flow and to provide a usage report related to the at least one QoS flow; and determine to terminate delivery of MBS data of the MBS sessions via individual delivery in at least one QoS flow of the PDU session related to the MBS session to the user equipment; configure the user plane function to stop forwarding received MBS data in the in at least one QoS flow and to provide a usage report related to the at least one QoS flow; and receiving from the user plane function (UPF) a usage report indicating a data volume of the at least one QoS flow; and sending a report to the charging function that comprises at least one of: a data volume transmitted for the MBS session, wherein the data volume excludes the received data volume of the at least one QoS flow; a data volume transmitted for a QoS flow of the MBS session, wherein the data volume excludes the received data volume of the at least one QoS flow; a data volume for data of the MBS session transmitted via individual delivery, wherein the data volume includes the received data volume of the at least one QoS flow; or a data volume for data for a QoS flow of the MBS session transmitted via individual delivery, wherein the data volume includes the received data volume of the at least one QoS flow.

[0146] Clause 20. An apparatus comprising: 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 at least to perform: receive from a multicast broadcast session management function (MB-SMF) a report that an MBS session is created, updated or deleted, wherein the report comprises at least one of: an indication of the event that triggered 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 Area Session; an indication whether the MBS session is a multicast session or a broadcast session; a description of Quality of Service(QoS) flows related to the MBS session; a data volume transmitted for the MBS session; a data volume transmitted for a QoS flow of the MBS session; a duration of the MBS session; a duration for which the MBS session was active; a duration for which the MBS session was deactivated; a time when the report is created; or a charging identifier; and store the reported information.

[0147] Clause 21. The apparatus of clause 20, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform: send to the MB-SMF instructions about the information related to the MBS session to be reported subsequently, wherein the instructions comprise at least one of a: a request for volume reporting, a request for duration reporting, a frequency of reporting, a threshold volume requiring reporting, events to be reported, or a charging identifier to be used in the reporting.

[0148] Clause 22. The apparatus of clauses 20 or 21, wherein the events to be reported comprise at least one of: release of the MBS session; activation of the MBS session; deactivation of the MBS session; update of the MBS session; update of the MBS session QoS information; or update of the MBS session service area. Clause 23. The apparatus of any of clauses 20 to 22, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform: receive a report from a session management function (SMF) indicating that the UE joined the MBS session, wherein the report comprises at least one of: an indication that the UE joined the MBS session as event that triggered the report; an Identifier of the MBS session; an Identifier of the Area Session; an Identifier of the UE; a service area of the MBS session; an indication whether individual delivery is applied for the MBS session; a description of Quality of Service (QoS) flows related to the MBS session; an identifier of the multicast broadcast session management function (MB-SMF) handling the MBS session, a time when the report is created; or the charging identifier; and store the reported information.

[0149] Clause 24. The apparatus of clauses 23, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform send to the SMF instructions about the information related to the MBS session and user equipment to be reported subsequently, wherein the instructions comprise at least one of: a request for volume reporting, a request for duration reporting, a frequency of reporting, a threshold volume requiring reporting, a quota for the MBS session, events to be reported, instructions how to report volume of data of the MBS session delivered via individual delivery; instructions how to report the time while the MBS session was delivered via individual delivery; or a second charging identifier to be used in the reporting.

[0150] Clause 25. The apparatus of 24, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform: determine a time-based quota for the MBS session and user equipment taking into consideration at least one of the following reported by the MB-SMF: a data volume transmitted for the MBS session; a data volume transmitted for a QoS flow of the MBS session; a duration of the MBS session; or a duration for which the MBS session was active;

[0151] Clause 26. The apparatus of any of clauses 20 to 22, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform: receive, from a second charging function, a request to indicate information related to the MBS session; send at least one message to the second charging function that comprises information related to the MBS session, wherein the information comprises at least one of. an indication of at least one event; the Identifier of the MBS session; a service area of the MBS session; an Identifier of the Area Session; a description of Quality of Service(QoS) flows related to the MBS session; a data volume transmitted for the MBS session; a data volume transmitted for a QoS flow of the MBS session; a duration of the MBS session; a duration for which the MBS session was active; a duration for which the MBS session was deactivated; a time when the report is created; or the charging identifier.

[0152] Clause 27. The apparatus of any of clause 26, wherein the request from the second charging function, comprises at least one of the following: the Identifier of the MBS session; the Identifier of the Area Session; or the charging identifier.

[0153] Clause 28. An apparatus comprising: 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 at least to perform: receive a report from a session management function (SMF) indicating that the UE joined the MBS session, wherein the report comprises at least one of: an indication that the UE joined the MBS session as event that triggered the report; an Identifier of the MBS session; an Identifier of the Area Session; an Identifier of the UE; a service area of the MBS session; an identifier of a second charging function; an indication whether individual delivery is applied for the MBS session; a description of Quality of Service (QoS) flows related to the MBS session; an identifier of the multicast broadcast session management function (MB-SMF) handling the MBS session; a time when the report is created; or a charging identifier; and store the reported information.

[0154] Clause 29. The apparatus of clauses 28, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform: send to the SMF instructions about the information related to the MBS session and user equipment to be reported subsequently, wherein the instructions comprise at least one of: a request for volume reporting, a request for duration reporting, a frequency of reporting, a threshold volume requiring reporting, a quota for the MBS session, events to be reported, instructions how to report volume of data of the MBS session delivered via individual delivery; instructions how to report the time while the MBS session was delivered via individual delivery; or a second charging identifier to be used in the reporting.

[0155] Clause 30. The apparatus of clause 29, wherein the events to be reported comprise at least one of the following: the UE leaving the MBS session; release of the MBS session; removal of the UE from the MBS session; termination of a PDU session related to the MBS session; activation of the MBS session; deactivation of the MBS session; update of the MBS session; update of the MBS session Qos information; update of the MBS session service area; start of individual delivery of data of the MBS session towards the UE; stop of individual delivery of data of the MBS session towards the UE; the UE moving out of the service area of the MBS session; the UE entering the service area of the MBS session; or change of location dependent sub session of the MBS session delivered to the UE.

[0156] Clause 31. The apparatus of any of clauses 28 to 30, wherein the subsequent received reports comprise at least one of: an indication of the event that triggered the report; 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 Area Session; an Identifier of the UE; the charging identifier; the second charging identifier; a service area of the MBS session; an indication whether individual delivery is applied for the MBS session; a description of Quality of Service(QoS) flows related to the MBS session; a data volume transmitted for the MBS session; a data volume transmitted for a QoS flow of the MBS session; a data volume for data of the MBS session transmitted via individual delivery; a data volume for data for a QoS flow of the MBS session transmitted via individual delivery; a duration of the MBS session; a duration for which the MBS session was active; a duration for which the MBS session was deactivated; or a time when the report is created.

[0157] Clause 32. The apparatus of any of clauses 28 to 31, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform: determine that data volume reporting applies for the MBS session and the UE; determine the multicast broadcast session management function (MB-SMF) handling the MBS session based on at least one of: the received Identifier of the MBS session; the received identifier of MB-SMF; or the Identifier of the Area Session; if suitable data volume indications have not yet been requested for the MBS session, send, to the MB-SMF a request to indicate the data volume transmitted for the MBS session of for at least one QoS flow of the MBS session; receive at least one message from the MB-SMF that comprises the data volume for the MBS session of for the at least one QoS flow of the MBS session; and store the received information.

[0158] Clause 33. The apparatus of clause 32, wherein: The request to indicate the data volume is at least one of an Nmbsmf MBSSession ContextStatusSubscribe request, a Nmbsmf MBSSession ContextUpdate request, a request for one-time reporting, a request for periodic reporting, or a request comprising the charging key; and the message from the MB- SMF is at least one of a response to the request to indicate the data volume, a notification request, an Nmbsmf MBSSession ContextStatusSubscribe response, a Nmbsmf_MBSSession_ContextUpdate response, or a Nmbsmf_MBSSession_ContextStatusNotify request.

[0159] Clause 34. The apparatus of 32 or 33, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform: obtain a report of at least one of the following events:the UE joining the MBS session; the UE leaving the MBS session, removal of the UE from the MBS session; termination of a PDU session related to the MBS session; start of individual delivery of data of the MBS session towards the UE, or stop of individual delivery of data of the MBS session towards the UE; and when obtaining a report of at least one of the events, send a request for a one-time indication of the current data volume transmitted for the MBS session of for at least one QoS flow of the MBS session.

[0160] Clause 35. The apparatus of any of clauses 28 to 34, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform: determine a second charging function based on at least one of: the received identifier of the second charging function; the Identifier of the MBS session; the Identifier of the Area Session; orthe charging identifier; send, to the second charging function, a request to indicate information related to the MBS session; receive from the second charging function at least one message that comprises information related to the MBS session, wherein the information comprises at least one of. an indication of at least one event; the Identifier of the MBS session; a service area of the MBS session; an Identifier of the Area Session; a description of Quality of Service(QoS) flows related to the MBS session; a data volume transmitted for the MBS session; a data volume transmitted for a QoS flow of the MBS session; a duration of the MBS session; a duration for which the MBS session was active; a duration for which the MBS session was deactivated; a time when the report is created; or the charging identifier.

[0161] Clause 36. The apparatus of clause 35, wherein the request to the second charging function, comprises at least one of: the Identifier of the MBS session; the Identifier of the Area Session; the charging identifier. Clause 37. The apparatus of any of clauses 32 to 36, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform: determine a time-based quota for the MBS session and user equipment taking into consideration at least one of the following reported by the MB-SMF or by the second charging function: a data volume transmitted for the MBS session; a data volume transmitted for a QoS flow of the

[0162] MBS session; a duration of the MBS session; or a duration for which the MBS session was active.

[0163] In the drawings and specification, there have been disclosed exemplary embodiments of the invention. Although specific terms are employed, they are used in a generic and descriptive sense only and not for purposes of limitation. It will be apparent to those having ordinary skill in this art that various modifications and variations may be made to the embodiments disclosed herein, consistent with the present invention, without departing from the spirit and scope of the present invention. Other embodiments consistent with the present invention will become apparent from consideration of the specification and the practice of the description disclosed herein.

Claims

We Claim:

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) that, when executed by the at least one processor, cause the apparatus at least to perform: receiving a request, originating from an application function (AF), to create a multicast broadcast service (MBS) session; and reporting, to a first charging function, information indicating that the MBS session is created, wherein the information comprises at least one of: an indication of an event that triggered the reporting; 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 whether the MBS session is a multicast session or a broadcast session; a description of Quality of Service(QoS) flows related to the MBS session; a data volume transmitted for the MBS session; a duration of the MBS session; a duration for which the MBS session was active; or a charging identifier.

2. The apparatus of claim 1, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform: receiving, from the first charging function, configuration information associated with the reporting of the information, wherein the configuration information comprises at least one of the following: an indication that the reporting comprises volume reporting; an indication that the reporting comprising duration reporting; a frequency of the reporting of the information; a threshold volume requiring the reporting; information identifying the event; or the charging identifier; and wherein the reporting is based on the configuration information.

3. The apparatus of claims 1 or 2, wherein the event comprises at least one of the following: release of the MBS session; activation of the MBS session; deactivation of the MBS session; update of the MBS session; update of the MBS session QoS information; update of the QoS information of the MBS session; update of the MBS session service area; or update of an identifier of a service area for the MBS session.

4. The apparatus of any of claims 1 to 3, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform: providing, to a multicast-broadcast user plane function (MB-UPF), information to be used to configure the MB-UPF to provide usage reports related to the MBS session; receiving, from the multicast-broadcast user plane function (MB-UPF), a usage report indicating a data volume of the MBS session; and sending, to the first charging function, a report comprising the data volume.

5. The apparatus of any of claims 1 to 4, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform: providing, to a multicast-broadcast user plane function (MB-UPF), information to be used to configure the MB-UPF to provide usage reports related to a QoS flow of the MBS session; receiving, from the multicast-broadcast user plane function (MB-UPF), a usage report indicating a data volume for the QoS flow of the MBS session; and sending, to the first charging function, a report comprising the data volume for the QoS flow.

6. The apparatus of any of claims 1 to 5, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform:receiving, from a session management function (SMF) or a second charging function, a request to indicate the data volume transmitted for the MBS session or for at least one QoS flow of the MBS session; providing, to a multicast-broadcast user plane function (MB-UPF), information to be used to configure the MB-UPF to provide usage reports related to the MBS session or related to the at least one QoS flow of the MBS session; and receive at least one usage report from the multicast-broadcast user plane function (MB-UPF) indicating a data volume for the MBS session or for the at least one QoS flow of the MBS session; and sending to the SMF or to the second charging function at least one message comprising the data volume for the MBS session or for the at least one QoS flow of the MBS session.

7. The apparatus of claim 6, wherein the request to indicate the data volume is at least one of the following: a Nmbsmf_MBSSession_ContextStatusSubscribe request, a Nmbsmf_MBSSession_ContextUpdate request, a request for one-time reporting, a request for periodic reporting, or a request comprising the charging key; and wherein the message to the SMF or to the second charging function is at least one of the following: a response to the request to indicate the data volume, a notification request, a Nmbsmf_MBSSession_ContextStatusSubscribe response, a Nmbsmf_MBSSession_ContextUpdate response, or a Nmbsmf_MBSSession_ContextStatusNotify request.

8. The apparatus of 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 from a session management function (SMF) anNmbsmf MBSSession ContextStatusSubscribe request for the MBS session; and sending an Nmbsmf MBSSession ContextStatusSubscribe response comprising at least one of the following: an identifier of the charging function or the charging identifier.

9. An apparatus comprising: at least one processor; at least one memory comprising instructions for a session management function (SMF) that, 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, to a charging function, information indicating that the UE joined the MBS session, wherein the information comprises at least one of: an indication of an event that triggered the report, wherein the event comprises that the UE joined the MBS session; an identifier of the MBS session; an identifier of the Area Session; an identifier of the UE; an identifier of a service area of the MBS session; an indication whether individual delivery is applied for the MBS session; a description of Quality of Service(QoS) flows related to the MBS session; an identifier of a multicast broadcast session management function (MB-SMF) handling the MBS session. a time when the report is created; or a charging identifier.

10. The apparatus of claim 9, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform: sending to a multicast broadcast session management function (MB-SMF) an Nmbsmf MBSSession ContextStatusSubscribe request for the MBS session; and receiving an Nmbsmf MBSSession ContextStatusSubscribe response comprising an identifier of a second charging function; and performing at least one of the following: selecting the charging function to report that that the UE joined the MBS session based on the identifier of the second charging function; or provide the identifier of the second charging function in the information indicating that the UE joined the MBS session.

11. The apparatus of claims 9 or 10, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform: sending to a multicast broadcast session management function (MB-SMF) an Nmbsmf MBSSession ContextStatusSubscribe request for the MBS session; and receiving an Nmbsmf MBSSession ContextStatusSubscribe response comprising an charging identifier; and providing the charging identifier within the information indicating that that the UE joined the MBS session.

12. The apparatus of any of claims 9 to 11, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform: receiving, from the charging function, configuration information associated with the reporting of the information, wherein the configuration information comprises at least one of the following: an indication that the reporting comprises volume reporting; an indication that the reporting comprises duration reporting; a frequency of the reporting of the information; a threshold volume that requires the reporting; a quota for the MBS session that requires the reporting; information identifying the event; information indicating how to report volume of data of the MBS session delivered via individual delivery; information indicating how to report time the MBS session was delivered via individual delivery; or a second charging identifier to be used in the reporting; and wherein the reporting is based on the configuration information.

13. The apparatus of claim 12, wherein the event comprises at least one of: the UE leaving the MBS session; release of the MBS session; removal of the UE from the MBS session; termination of a PDU session related to the MBS session; activation of the MBS session; deactivation of the MBS session;update of the MBS session; update of the MBS session QoS information; update of the QoS information of the MBS session; update of an identifier of a service area for the MBS session. update of the MBS session service area; update of an identifier of a service area of the MBS session; start time of individual delivery of data of the MBS session towards the UE; stop time of individual delivery of data of the MBS session towards the UE; the UE moving out of the service area of the MBS session; the UE entering the service area of the MBS session; or change of location dependent sub session of the MBS session delivered to the UE.

14. The apparatus of any of claims 9 to 13, wherein the information comprises at least one of: an indication of the event that triggered the reporting; 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 Area 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 whether individual delivery is applied for the MBS session; a description of Quality of Service(QoS) flows related to the MBS session; a data volume transmitted for the MBS session; a data volume transmitted for a QoS flow of the MBS session; a data volume for data of the MBS session transmitted via individual delivery; a data volume for data for a QoS flow of the MBS session transmitted via individual delivery; a duration of the MBS session; a duration for which the MBS session was active; a duration for which the MBS session was deactivated; or a time when the report is created.

15. The apparatus of any of claims 9 to 14, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform: determining data volume reporting applies for the MBS session and the UE; if the user plane function (UPF) handling the PDU session related to the MBS session of the UE is determined to not yet receive data of the MBS session, providing the UPF with configuration information to be used to configure the UPF to receive data of the MBS session; providing the UPF with additional configuration information to be used configure the UPF to provide a usage report related to the MBS session or at least one QoS flow of the MBS session; and receiving from the user plane function (UPF) a usage report indicating a data volume of the MBS session or the at least one QoS flow of the MBS session; sending the charging function a report comprising the data volume.

16. The apparatus of any of claims 9 to 14, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform: determining data volume reporting applies for the MBS session and the UE; if suitable data volume indications have not yet been requested for the MBS session, sending, to a multicast broadcast session management function (MB-SMF), a request to indicate the data volume transmitted for the MBS session or at least one QoS flow of the MBS session; receiving from the MB-SMF at least one message comprising the data volume for the MBS session or the at least one QoS flow of the MBS session; and sending to the charging function a report comprising the data volume for the MBS session or the at least one QoS flow of the MBS session.

17. The apparatus of claim 16, wherein the request to indicate the data volume is at least one of the following: a Nmbsmf_MBSSession_ContextStatusSubscribe request, a Nmbsmf_MBSSession_ContextUpdate request, a request for one-time reporting, a request for periodic reporting, or a request comprising the charging key; andwherein the message from the MB-SMF is at least one of the following: a response to the request to indicate the data volume, a notification request, a Nmbsmf_MBSSession_ContextStatusSubscribe response, a Nmbsmf_MBSSession_ContextUpdate response, or a Nmbsmf_MBSSession_ContextStatusNotify request.

18. The apparatus of 16 or 17, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform: detecting at least one of the following: the UE joining the MBS session; the UE leaving the MBS session, removal of the UE from the MBS session; termination of a PDU session related to the MBS session; start of individual delivery of data of the MBS session towards the UE, or nstop of individual delivery of data of the MBS session towards the UE; and sending a request for a one-time indication of the current data volume transmitted for the MBS session for at least one QoS flow of the MBS session.

19. The apparatus of any of claims 9 to 18, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform: determining data volume reporting applies for the MBS session and the UE; determining to deliver MBS data of the MBS session via individual delivery in at least one QoS flow of the PDU session related to the MBS session to the user equipment; configure the user plane function (UPF) handling the PDU session to forward received MBS data in the in at least one QoS flow and to provide a usage report related to the at least one QoS flow; and determine to terminate delivery of MBS data of the MBS sessions via individual delivery in at least one QoS flow of the PDU session related to the MBS session to the user equipment; configure the user plane function to stop forwarding received MBS data in the in at least one QoS flow and to provide a usage report related to the at least one QoS flow; and receiving from the user plane function (UPF) a usage report indicating a data volume of the at least one QoS flow; andsending a report to the charging function that comprises at least one of: a data volume transmitted for the MBS session, wherein the data volume excludes the received data volume of the at least one QoS flow; a data volume transmitted for a QoS flow of the MBS session, wherein the data volume excludes the received data volume of the at least one QoS flow; a data volume for data of the MBS session transmitted via individual delivery, wherein the data volume includes the received data volume of the at least one QoS flow; or a data volume for data for a QoS flow of the MBS session transmitted via individual delivery, wherein the data volume includes the received data volume of the at least one QoS flow.

20. An apparatus comprising: 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 at least to perform: receive from a multicast broadcast session management function (MB-SMF) a report that an MBS session is created, updated or deleted, wherein the report comprises at least one of: an indication of the event that triggered 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 Area Session an indication whether the MBS session is a multicast session or a broadcast session; a description of Quality of Service(QoS) flows related to the MBS session; a data volume transmitted for the MBS session; a data volume transmitted for a QoS flow of the MBS session; a duration of the MBS session; a duration for which the MBS session was active; a duration for which the MBS session was deactivated; a time when the report is created; or a charging identifier; andstore the reported information.

21. The apparatus of claim 20, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform: send to the MB-SMF instructions about the information related to the MBS session to be reported subsequently, wherein the instructions comprise at least one of a: a request for volume reporting, a request for duration reporting, a frequency of reporting, a threshold volume requiring reporting, events to be reported, or a charging identifier to be used in the reporting.

22. The apparatus of claims 20 or 21, wherein the events to be reported comprise at least one of: release of the MBS session; activation of the MBS session; deactivation of the MBS session; update of the MBS session; update of the MBS session QoS information; or update of the MBS session service area;23. The apparatus of any of claims 20 to 22, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform: receive a report from a session management function (SMF) indicating that the UE joined the MBS session, wherein the report comprises at least one of: an indication that the UE joined the MBS session as event that triggered the report; an Identifier of the MBS session; an Identifier of the Area Session an Identifier of the UE a service area of the MBS session; an indication whether individual delivery is applied for the MBS session; a description of Quality of Service (QoS) flows related to the MBS session;an identifier of the multicast broadcast session management function (MB- SMF) handling the MBS session. a time when the report is created; or the charging identifier; and store the reported information.

24. The apparatus of claims 23, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform send to the SMF instructions about the information related to the MBS session and user equipment to be reported subsequently, wherein the instructions comprise at least one of a request for volume reporting, a request for duration reporting, a frequency of reporting, a threshold volume requiring reporting, a quota for the MBS session, events to be reported, instructions how to report volume of data of the MBS session delivered via individual delivery; instructions how to report the time while the MBS session was delivered via individual delivery; or a second charging identifier to be used in the reporting.

25. The apparatus of 24, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform: determine a time-based quota for the MBS session and user equipment taking into consideration at least one of the following reported by the MB-SMF : a data volume transmitted for the MBS session; a data volume transmitted for a QoS flow of the MBS session; a duration of the MBS session; or a duration for which the MBS session was active;26. The apparatus of any of claims 20 to 22, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to perform:receive, from a second charging function, a request to indicate information related to the MBS session; send at least one message to the second charging function that comprises information related to the MBS session, wherein the information comprises at least one of. an indication of at least one event; the Identifier of the MBS session; a service area of the MBS session; an Identifier of the Area Session a description of Quality of Service(QoS) flows related to the MBS session; a data volume transmitted for the MBS session; a data volume transmitted for a QoS flow of the MBS session; a duration of the MBS session; a duration for which the MBS session was active; a duration for which the MBS session was deactivated; a time when the report is created; or the charging identifier.

27. The apparatus of any of claim 26, wherein the request from the second charging function, comprises at least one of the following: the Identifier of the MBS session; the Identifier of the Area Session; or the charging identifier.

Images