METHODS PERFORMED BY A MULTI-BROADCAST SESSION MANAGEMENT FUNCTION, BY A POLICY CONTROL FUNCTION AND BY A NETWORK FUNCTION, MULTI-BROADCAST SESSION MANAGEMENT FUNCTION, POLICY CONTROL FUNCTION, NETWORK FUNCTION, COMPUTER-READABLE STORAGE MEDIUM, AND COMPUTER PROGRAM PRODUCT

Description

147 METHODS PERFORMED BY A MULTI-BROADCAST SESSION MANAGEMENT FUNCTION, BY A POLICY CONTROL FUNCTION AND BY A NETWORK FUNCTION, MULTI-BROADCAST SESSION MANAGEMENT FUNCTION, POLICY CONTROL FUNCTION, NETWORK FUNCTION, AND COMPUTER-READABLE STORAGE MEDIUM FIELD OF THE TECHNIQUE

[001] The non-limiting and illustrative applications of this description generally relate to the field of communications technology and, specifically, to a method and apparatus for a location-dependent multicast / broadcast (MBS) service. FUNDAMENTALS

[002] This section introduces aspects that may facilitate a better understanding of the description. Consequently, the statements in this section should be read in this light and should not be understood as admissions about what is in the prior art or what is not in the prior art.

[003] MBS is a point-to-multipoint service in which data is transmitted from a single source entity to multiple recipients, either to all users in a broadcast service area or to users in a multicast group. The corresponding MBS session types are broadcast session and multicast session.

[004] MBS may be one of the most promising fifth-generation (5G) applications / services, where the 5G network can be used to transmit content to multiple user devices (UEs). It may be a critical technology for public safety, the automotive industry, etc.

[005] Designing a meaningful and efficient system architecture to enable such a service is fundamental. Furthermore, the policy and billing control (PCC) procedure defines how to handle the 5G MBS (5MBS) session with appropriate policies and charges while the service is running. Petition 870250090277, dated 03 / 10 / 2025, page 201 / 362 / 147 MBS is in use. Therefore, a comprehensive PCC procedure is essential to cover different scenarios and use cases.

[006] The Third Generation Partnership Project (3GPP) Technical Specification (TS) 23.247 V18.1.0, the description of which is incorporated herein by reference in its entirety, describes architectural enhancements for 5G (fifth generation) multicast-cast services.

[007] Figure 1A shows an example of delivery methods, which is the same as Figure 4.1-1 of TS 23.247 V18.1.0 3GPP.

[008] The MBS architecture follows the architectural principles of the 5G (5GS) system, as defined in TS 23.501 V18.0.0 3GPP, the description of which is incorporated herein by reference in its entirety, allowing the distribution of MBS data from the 5GS input to the nodes of the next-generation radio access network (NG-RAN) and then to the UE. The MBS architecture provides efficient use of radio access network (RAN) and core network (CN) resources, with emphasis on radio interface efficiency and efficient transport for a variety of multicast and broadcast services.

[009] MBS also provides functionalities such as service of Local MBS, multicast MBS authorization, and Quality of Service Differentiation (QoS). MBS traffic can be delivered from a single data source (e.g., application service provider) to multiple UEs. Depending on many factors, there are several delivery methods that can be used to deliver MBS traffic in the 5GS.

[0010] Between the 5G core network (5GC) and the NG-RAN, there are two possible delivery methods for transmitting MBS data.

[0011] The first delivery method is the 5GC individual MBS traffic delivery method. This method is only applied to multicast MBS sessions. 5GC receives a single copy of the MBS data packets and delivers separate copies of these MBS data packets to individual UEs via Protocol Data Unit (PDU) session. Petition 870250090277, dated 03 / 10 / 2025, page 202 / 362 / 147 by the EU. Therefore, for each EU, it is necessary that a PDU session be associated with a multi-broadcast session.

[0012] The second delivery method is the 5GC shared MBS traffic delivery method. This method is applied to both broadcast and multicast MBS sessions. 5GC receives a single copy of the MBS data packets and delivers a single copy of these MBS packets to an NG-RAN node, which then delivers them to one or more UEs.

[0013] Between NG-RAN and UE, two delivery methods are available for transmitting MBS data packets via radio interface.

[0014] The first delivery method is the point-to-point (PTP) delivery method, in which the NG-RAN delivers separate copies of MBS data packets per radio interface to individual UE(s).

[0015] The second delivery method is the point-to-multipoint (PTM) delivery method, in which the NG-RAN delivers a single copy of MBS data packets via radio interface to multiple UEs. SUMMARY

[0016] This summary is provided to introduce a selection of concepts in a simplified form which are further described below in the detailed description. This summary is not intended to identify major features or essential characteristics of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

[0017] A location-dependent MBS service is an MBS service provided in multiple MBS service areas. An MBS service area may be identified by a list of cells or a list of tracking areas. The MBS service area may be geographic area information or civic address information, and the Network Exposure Function (NEF) / Multicast / Broadcast Service Function (MBSF) may translate the location information into a list of Identifiers. Petition 870250090277, dated 03 / 10 / 2025, page 203 / 362 / 147 Cell (ID) or a Tracking Area Identity (TAI) list as an MBS service area, see clause 7.1.1.2 of TS 23.247 V18.1.0 3GPP.

[0018] A location-dependent MBS can be identified by the MBS session ID and provided in multiple MBS service areas. The location-dependent MBS service allows the distribution of different content data to different MBS service areas. The same MBS session ID is used, but a different area session ID is used for each MBS service area.

[0019] Multiple application functions (AFs) can start the same multi-broadcast MBS session with different content in different MBS service areas.

[0020] Several problems have been identified in the MBS PCC procedures for location-dependent MBS service (note that “area session,” as used in this document, refers to a location-dependent MBS session within an MBS service area).

[0021] Problem #1. It is unclear how to handle the creation of MBS policy associations for the 2nd, 3rd... area sessions.

[0022] The policy control function (PCF) may handle policy association creation requests for the 2nd, 3rd... area sessions as an error situation because a policy association already exists for the same MBS session ID. Therefore, the PCF is expected to reject the MBS policy control creation request (e.g., Npcf_MBSPolicyControl_Create request) for the 2nd, 3rd... area sessions.

[0023] If the PCF, based on the implementation, proceeds with the creation of the policy association, there is no way to distinguish which policy association is being updated, etc.

[0024] Problem #2. It is unclear how to link the policy association created by the MBS policy control creation request. Petition 870250090277, dated 10 / 03 / 2025, page 204 / 362 / 147 (e.g., Npcf_MBSPolicyControl_Create request) with the authorized policies in the MBS policy authorization creation request (e.g., Npcf_MBSPolicyAuthorization_Create request) for the same area session when AF / NEF / MBSF decides to interact with PCF based on the local configuration.

[0025] Problem #3. May fail to create the application session context during MBS policy authorization creation (e.g., Npcf_MBSPolicyAuthorization_Create) for the same area session with the same MBS session ID from a location-dependent service.

[0026] Therefore, the MBS PCC procedures for location-dependent MBS services do not function as expected. To overcome or mitigate at least one of the problems mentioned above or other problems, the embodiments in this description propose an enhanced solution for location-dependent MBS service.

[0027] In one embodiment, to address Problem #1, for each area session, MB-SMF can provide an additional ID (e.g., Area Session Policy ID) along with the MBS session ID in the MBS policy control creation request (such as Npcf_MBSPolicyControl_Create request) to PCF by N7mb.

[0028] In one embodiment, to address Problem #2 and Problem #3, for each area session, an additional ID (e.g., Area Session Policy Binding ID) can be assigned when AF / NEF / MBSF interacts with PCF, and such ID can be sent by AF / NEF / MBSF to MB-SMF.

[0029] In one embodiment, regarding how MB-SMF determines the area session policy ID, the following is proposed. If AF / NEF / MBSF does not interact with PCF, MB-SMF may use the area session ID as the area session policy ID. If AF / NEF / MBSF interacts with PCF, MB-SMF may use the policy binding ID. Petition 870250090277, dated 10 / 03 / 2025, page 205 / 362 / 147, area session as area session policy ID.

[0030] In one embodiment, regarding how the Area Session Policy Binding ID is assigned when AF / NEF / MBSF decides to interact with PCF based on the local configuration, the following is proposed.

[0031] In one embodiment, the AF / NEF / MBSF can assign an additional ID (e.g., Area Session Policy Binding ID) and send it in the MBS policy authorization creation request (such as the Npcf_MBSPolicyAuthorization_Create request) to the PCF.

[0032] In one mode, AF / NEF / MBSF can include an area session policy binding ID in the MBS session creation request (such as the Nmbsmf_MBSSession_Create request).

[0033] In one embodiment, MB-SMF can use the area session policy binding ID as the area session policy ID in the MBS policy control creation request (such as the Npcf_MBSPolicyControl_Create request) to the PCF, so that the PCF can retrieve the previously authorized policy when AF / NEF / MBSF interacted with the PCF.

[0034] In one embodiment, MB-SMF can include the area session policy binding ID in the MBS session creation response (such as the Nmbsmf_MBSSession_Create response) so that AF / NEF / MBSF knows the relationship between the area session ID and the area session policy binding ID.

[0035] In one embodiment, in the PCC procedures for location-dependent MBS service, MB-SMF can include a new area session policy ID in the MBS policy control creation request (such as the Npcf_MBSPolicyControl_Create request).

[0036] In one mode, when AF / NEF / MBSF does not interact with PCF, MB-SMF can use the area session ID as the area session policy ID. Petition 870250090277, dated 03 / 10 / 2025, page 206 / 362 / 147

[0037] In one mode, when the AF / NEF / MBSF decides to interact with the PCF, for example, based on the local configuration, the AF / NEF / MBSF can assign a new area session policy binding ID and send it to the PCF.

[0038] In one embodiment, AF / NEF / MBSF may also include the area session policy binding ID in the MBS session creation request (such as the Nmbsmf_MBSSession_Create request) sent to MB-SMF.

[0039] In one embodiment, MB-SMF can use the area session policy binding ID as the area session policy ID and send it to PCF, so that PCF can retrieve the previously authorized policy when AF / NEF / MBSF interacted with PCF.

[0040] In one embodiment, MB-SMF can include the area session policy binding ID in the MBS session creation response (such as the Nmbsmf_MBSSession_Create response).

[0041] In a first aspect of the description, a method executed by a multicast / broadcast session management function (MB-SMF) is provided. The method may comprise sending a multicast / broadcast (MBS) service policy control creation request for a location-dependent MBS session to a policy control function (PCF). The method may further comprise receiving an MBS policy control creation response for the location-dependent MBS session from the PCF. The MBS policy control creation request may comprise an MBS session identifier (ID) and some first information. The first information and the MBS session ID may be used to uniquely identify an MBS session toward a specific MBS service area from a location-dependent MBS session and / or create a policy association for the MBS session. Petition 870250090277, dated 03 / 10 / 2025, page 207 / 362 / 147 location-dependent session corresponding to the MBS session ID and the first information and / or differentiate different services based on location provided through the location-dependent MBS session with the same MBS session ID and / or associate application function (AF) session information with the location-dependent MBS session in a specific MBS service area and / or uniquely identify policy information for the location-dependent MBS session corresponding to the MBS session ID and the first information.

[0042] In one embodiment, the first piece of information may comprise at least one MBS ID or service area.

[0043] In one mode, the ID may comprise at least one binding ID or one area session policy ID.

[0044] In one embodiment, the linking ID may be assigned by at least one AF, a network exposure function (NEF), or a multicast / broadcast service function (MBSF).

[0045] In one embodiment, the linking ID may be assigned by at least one AF, a network exposure function (NEF), or a multicast / broadcast service function (MBSF).

[0046] In one mode, the area session policy binding ID can be assigned by at least one AF, one NEF, one MBSF, or one PCF.

[0047] In one embodiment, if a request to create an MBS policy authorization for the location-dependent MBS session has not been sent to PCF, the area session ID may be used as the area session policy ID.

[0048] In one embodiment, if the request to create MBS policy authorization for the location-dependent MBS session has been sent to PCF, the area session policy binding ID may be used as the area session policy ID. Petition 870250090277, dated 03 / 10 / 2025, page 208 / 362 / 147

[0049] In one embodiment, the method may further comprise receiving an MBS session creation request for the location-dependent MBS session of a network function. The method may further comprise sending an MBS session creation response for the location-dependent MBS session to the network function.

[0050] In one embodiment, the MBS session creation request may comprise a second piece of information and the MBS session ID. The second piece of information and the MBS session ID may be used to uniquely identify an MBS session toward a specific MBS service area from a location-dependent MBS session and / or differentiate different location-based services provided through location-dependent MBS sessions with the same MBS session ID and / or associate application function (AF) session information with the location-dependent MBS session in a specific MBS service area.

[0051] In one embodiment, the second piece of information may comprise at least one binding ID, an area session policy binding ID, or an MBS service area.

[0052] In one mode, the binding ID can be assigned by at least one AF, a network exposure function (NEF), or a multicast / broadcast service function (MBSF). The area session policy binding ID can be assigned by at least one of the following: AF, NEF, MBSF, or PCF.

[0053] In one embodiment, the network function may comprise at least one AF, one NEF or one MBSF.

[0054] In one embodiment, the MBS session creation response may comprise an area session ID and second information.

[0055] In a second aspect of the description, a method is provided. Petition 870250090277, dated 10 / 03 / 2025, page 209 / 362 / 147, filed by a PCF. The method may comprise receiving a request to create an MBS policy control for a location-dependent MBS session from an MB-SMF. The method may further comprise sending an MBS policy control creation response for the location-dependent MBS session to the MB-SMF. The MBS policy control creation request may comprise an MBS session ID and first information. The first information and the MBS session ID may be used to uniquely identify an MBS session toward a specific MBS service area from a location-dependent MBS session and / or create a policy association for the location-dependent MBS session corresponding to the MBS session ID and first information and / or differentiate different location-based services provided through the location-dependent MBS session.location with the same MBS session ID and / or associate application function (AF) session information with the location-dependent MBS session in a specific MBS service area and / or uniquely identify policy information for the location-dependent MBS session corresponding to the MBS session ID and the first piece of information and / or link the policy association with the application session context for the location-dependent MBS session corresponding to the MBS session ID and the first piece of information.

[0056] In one embodiment, when the MBS policy control creation request does not include MBS service information, the method may additionally include location policy information for the location-dependent MBS session corresponding to the MBS session ID and the first piece of information.

[0057] In one embodiment, when the request to create an MBS policy control includes MBS service information and is authorized and at least one quality of service (QoS) parameter Petition 870250090277, dated 03 / 10 / 2025, page 210 / 362 / 147, necessary derivative based on MBS service information is permitted; the method may additionally comprise the generation of policy information for the location-dependent MBS session corresponding to the MBS session ID and the first information. The method may additionally comprise the storage of policy information for the location-dependent MBS session corresponding to the MBS session ID and the first information together with the MBS session ID and the first information.

[0058] In one embodiment, the first piece of information may comprise at least one MBS ID or service area.

[0059] In one mode, the ID may comprise at least one binding ID or one area session policy ID.

[0060] In one embodiment, the linking ID may be assigned by at least one AF, a network exposure function (NEF), or a multicast / broadcast service function (MBSF).

[0061] In one embodiment, the linking ID may be assigned by at least one AF, a network exposure function (NEF), or a multicast / broadcast service function (MBSF).

[0062] In one mode, the area session policy binding ID can be assigned by at least one AF, one NEF, one MBSF, or one PCF.

[0063] In one embodiment, if a request to create an MBS policy authorization for the location-dependent MBS session has not been sent to PCF, the area session ID may be used as the area session policy ID.

[0064] In one embodiment, if the request to create MBS policy authorization for the location-dependent MBS session has been sent to PCF, the area session policy binding ID may be used as the area session policy ID. Petition 870250090277, dated 03 / 10 / 2025, page 211 / 362 / 147

[0065] In one embodiment, the method may further comprise receiving a request to create an MBS policy authorization for the location-dependent MBS session of a network function. The MBS policy authorization creation request may include the second piece of information, the MBS session ID and MBS service information. The method may further comprise sending an MBS policy authorization creation response for the location-dependent MBS session to the network function.The second piece of information and the MBS session ID can be used to uniquely identify an MBS session toward a specific MBS service area from a location-dependent MBS session and / or differentiate different location-based services provided through location-dependent MBS sessions with the same MBS session ID and / or associate application function (AF) session information with the location-dependent MBS session in a specific MBS service area.

[0066] In one embodiment, the second piece of information may comprise at least one binding ID, an area session policy binding ID, or an MBS service area.

[0067] In one embodiment, the linking ID may be assigned by at least one AF, a network exposure function (NEF), or a multicast / broadcast service function (MBSF).

[0068] In a modality, the area session policy binding ID can be assigned by at least one of the following: AF, NEF, or MBSF.

[0069] In one embodiment, the method may additionally comprise receiving a request to create an MBS policy authorization for the location-dependent MBS session of a network function. The MBS policy authorization creation request may include an MBS service area for an MBS service. Petition 870250090277, dated 10 / 03 / 2025, page 212 / 362 / 147 location-dependent and the MBS session ID and MBS service information. The method may additionally comprise assigning a unique area session policy binding ID to the MBS service area. The unique area session policy binding ID may be used as the second piece of information. The method may additionally comprise sending an MBS policy authorization creation response for the location-dependent MBS session to the network function. The MBS policy authorization creation response may comprise the unique area session policy binding ID used as the second piece of information.

[0070] In one embodiment, when the MBS policy authorization creation request is authorized and at least one required QoS parameter derived from the MBS service information is allowed, the method may additionally comprise creating an application session context for the location-dependent MBS session corresponding to the MBS session ID and the second piece of information. The method may additionally comprise generating policy information for the location-dependent MBS session corresponding to the MBS session ID and the second piece of information. The method may additionally comprise storing the policy information for the location-dependent MBS session corresponding to the MBS session ID and the second piece of information, along with the MBS session ID and the second piece of information.

[0071] In one embodiment, the network function may comprise at least one AF, a network exposure function (NEF), or a multicast / broadcast service function (MBSF).

[0072] In a third aspect of the description, a method performed by a network function is provided. The method may comprise sending an MBS session creation request to an MBS session. Petition 870250090277, dated 10 / 03 / 2025, page 213 / 362 / 147, location-dependent for an MB-SMF. The method may additionally comprise receiving an MBS session creation response for the MB-SMF location-dependent MBS session. The MBS session creation request may include a second piece of information and an MBS session ID. The second piece of information and the MBS session ID may be used to uniquely identify an MBS session toward a specific MBS service area from a location-dependent MBS session and / or differentiate different location-based services provided through a location-dependent MBS session with the same MBS session ID and / or associate application function (AF) session information with the location-dependent MBS session in a specific MBS service area.

[0073] In one embodiment, the second piece of information may comprise at least one binding ID, an area session policy binding ID, or an MBS service area.

[0074] In one embodiment, the linking ID may be assigned by at least one AF, a network exposure function (NEF), or a multicast / broadcast service function (MBSF).

[0075] In a modality, the area session policy binding ID can be assigned by at least one of the following: AF, NEF, or MBSF.

[0076] In one embodiment, the MBS session creation response may comprise an area session ID and second information.

[0077] In one embodiment, the network function may comprise at least one AF, one NEF or one MBSF.

[0078] In one embodiment, when the network function is a NEF or an MBSF, the method may additionally comprise receiving the MBS session creation request for the location-dependent MBS session of an AF. The method may additionally comprise sending Petition 870250090277, dated 03 / 10 / 2025, page 214 / 362 / 147 of the response to the creation of an MBS session for the location-dependent MBS session for the AF.

[0079] In one embodiment, when the network function is an AF, sending an MBS session creation request to a location-dependent MBS session to an MB-SMF may comprise sending the MBS session creation request to the location-dependent MBS session to the MB-SMF directly or sending the MBS session creation request to the location-dependent MBS session to the MB-SMF via a NEF or an MBSF.

[0080] The method may additionally comprise sending a request to create an MBS policy authorization for the location-dependent MBS session to a PCF. The MBS policy authorization creation request may include the second piece of information, the MBS session ID, and the MBS service information. The method may additionally comprise receiving an MBS policy authorization creation response for the location-dependent MBS session from the PCF. The second piece of information and the MBS session ID may be used to create an application session context for the location-dependent MBS session corresponding to the MBS session ID and the second piece of information.

[0081] In one embodiment, the method may further comprise sending a request to create an MBS policy authorization for the location-dependent MBS session to a PCF. The MBS session creation request may include an MBS service area for a location-dependent MBS service and the MBS session ID and MBS service information. The method may further comprise receiving an MBS policy authorization creation response for the location-dependent MBS session from the PCF. The MBS policy authorization creation response may comprise a unique area session policy binding ID used as the Petition 870250090277, dated 03 / 10 / 2025, page 215 / 362 / 147 second piece of information. The second piece of information and the MBS session ID can be used to create an application session context for the location-dependent MBS session corresponding to the MBS session ID and the second piece of information.

[0082] In one embodiment, when the network function is a NEF or an MBSF, the method may additionally comprise receiving the MBS policy authorization creation request for the location-dependent MBS session from an AF. The method may additionally comprise sending the MBS policy authorization creation response for the location-dependent MBS session to the AF.

[0083] In one embodiment, when the network function is an AF, sending the MBS policy authorization creation request for the location-dependent MBS session to the PCF may comprise sending the MBS policy authorization creation request for the location-dependent MBS session to the PCF directly or sending the MBS policy authorization creation request for the location-dependent MBS session to the PCF via a NEF or an MBSF.

[0084] In a fourth aspect of the description, an MBSMF is provided. The MB-SMF may comprise a processor and processor-coupled memory. Said memory contains instructions executable by said processor. Said MB-SMF is operational for sending a multicast / broadcast (MBS) service policy control creation request for a location-dependent MBS session to a policy control function (PCF). Said MB-SMF is additionally operational for receiving an MBS policy control creation response for the location-dependent MBS session from the PCF. The MBS policy control creation request may comprise an MBS session identifier (ID) and a first piece of information. The first piece of information and the MBS session ID. Petition 870250090277, dated 10 / 03 / 2025, pp. 216 / 362 / 147, can be used to uniquely identify an MBS session toward a specific MBS service area from a location-dependent MBS session and / or create a policy association for the location-dependent MBS session corresponding to the MBS session ID and the first information and / or differentiate different location-based services provided through the location-dependent MBS session with the same MBS session ID and / or associate application function (AF) session information with the location-dependent MBS session in a specific MBS service area and / or uniquely identify policy information for the location-dependent MBS session corresponding to the MBS session ID and the first information.

[0085] In a fifth aspect of the description, a PCF is provided. The PCF may comprise a processor and memory coupled to the processor. Said memory contains instructions executable by said processor. The PCF is operational for receiving a request to create an MBS policy control for a location-dependent MBS session of an MB-SMF. Said PCF is additionally operational for sending an MBS policy control creation response to the location-dependent MBS session of the MB-SMF. The MBS policy control creation request may comprise an MBS session ID and the first information.The first MBS session ID and information can be used to uniquely identify an MBS session toward a specific MBS service area from a location-dependent MBS session and / or create a policy association for the location-dependent MBS session corresponding to the MBS session ID and the first MBS session ID and / or differentiate different location-based services provided through the location-dependent MBS session with the same MBS session ID and / or associate application function (AF) session information with the location-dependent MBS session. Petition 870250090277, dated 10 / 03 / 2025, p. 217 / 362 / 147 in a specific MBS service area and / or uniquely identify policy information for the location-dependent MBS session corresponding to the MBS session ID and the first piece of information and / or link the policy association with the application session context for the location-dependent MBS session corresponding to the MBS session ID and the first piece of information.

[0086] In a sixth aspect of the description, a network function is provided. The network function may comprise a processor and memory coupled to the processor. Said memory contains instructions executable by said processor. Said network function is operational for sending an MBS session creation request to a location-dependent MBS session for an MB-SMF. Said network function is also operational for receiving an MBS session creation response to the location-dependent MBS session of the MB-SMF. The MBS session creation request may include a second piece of information and an MBS session ID.The second piece of information and the MBS session ID can be used to uniquely identify an MBS session toward a specific MBS service area from a location-dependent MBS session and / or differentiate different location-based services provided through a location-dependent MBS session with the same MBS session ID and / or associate application function (AF) session information with the location-dependent MBS session in a specific MBS service area.

[0087] In a seventh aspect of the description, an MB-SMF is provided. The MB-SMF may comprise a first sending module configured to send a multicast / broadcast service (MBS) policy control creation request for a location-dependent MBS session to a policy control function (PCF). The MB-SMF may comprise a first receiving module configured to receive Petition 870250090277, dated 10 / 03 / 2025, page 218 / 362 / 147, a response to create an MBS policy control for the location-dependent MBS session from the PCF. The MBS policy control creation request may include an MBS session identifier (ID) and some initial information.The first piece of information and the MBS session ID can be used to uniquely identify an MBS session toward a specific MBS service area from a location-dependent MBS session and / or create a policy association for the location-dependent MBS session corresponding to the MBS session ID and the first piece of information and / or differentiate different location-based services provided through the location-dependent MBS session with the same MBS session ID and / or associate application function (AF) session information with the location-dependent MBS session in a specific MBS service area and / or uniquely identify policy information for the location-dependent MBS session corresponding to the MBS session ID and the first piece of information.

[0088] In one embodiment, MB-SMF may additionally comprise a second receiver module configured to receive an MBS session creation request for the location-dependent MBS session of a network function.

[0089] In one embodiment, MB-SMF may additionally comprise a second sending module configured to send an MBS session creation response to the location-dependent MBS session for the network function.

[0090] In an eighth aspect of the description, a PCF is provided. The PCF may comprise a first receiver module configured to receive a request to create an MBS policy control for a location-dependent MBS session from an MB-SMF. The PCF may further comprise a first send module configured to send an MBS policy control creation response to the session. Petition 870250090277, dated 10 / 03 / 2025, page 219 / 362 / 147, regarding location-dependent MBS for MB-SMF. The request to create an MBS policy control may include an MBS session ID and first information. The first information and the MBS session ID may be used to uniquely identify an MBS session toward a specific MBS service area from a location-dependent MBS session and / or create a policy association for the location-dependent MBS session corresponding to the MBS session ID and the first information and / or differentiate different location-based services provided through the location-dependent MBS session with the same MBS session ID and / or associate application function (AF) session information with the location-dependent MBS session in a specific MBS service area and / or uniquely identify policy information for the location-dependent MBS session.corresponding to the MBS session ID and the first piece of information and / or linking the policy association with the application session context for the location-dependent MBS session corresponding to the MBS session ID and the first piece of information.

[0091] In one embodiment, when the MBS policy control creation request does not include MBS service information, the PCF may include a location module configured to locate policy information for the location-dependent MBS session corresponding to the MBS session ID and the first information.

[0092] In one embodiment, when the MBS policy control creation request comprises MBS service information and is authorized, and at least one required Quality of Service (QoS) parameter derived from the MBS service information is enabled, the PCF may additionally comprise a first generation module configured to generate policy information for the location-dependent MBS session corresponding to the MBS session ID and to Petition 870250090277, dated 03 / 10 / 2025, page 220 / 362 / 147 first information. The PCF may also comprise a first storage module configured to store policy information for the MBS session dependent on the location corresponding to the MBS session ID and the first information, along with the MBS session ID and the first information.

[0093] In one embodiment, the PCF may further comprise a second receiver module configured to receive a request to create an MBS policy authorization for the location-dependent MBS session of a network function. The MBS policy authorization request may include the second information, the MBS session ID and the MBS service information. The PCF may additionally comprise a second send module configured to send an MBS policy authorization creation response for the location-dependent MBS session to the network function.The second piece of information and the MBS session ID can be used to uniquely identify an MBS session toward a specific MBS service area from a location-dependent MBS session and / or differentiate different location-based services provided through location-dependent MBS sessions with the same MBS session ID and / or associate application function (AF) session information with the location-dependent MBS session in a specific MBS service area.

[0094] In one embodiment, the PCF may additionally comprise a third receiver module configured to receive a request to create an MBS policy authorization for the location-dependent MBS session of a network function. The MBS policy authorization creation request may include an MBS service area for a location-dependent MBS service and the MBS session ID and MBS service information.

[0095] In one embodiment, the PCF may additionally comprise Petition 870250090277, dated 10 / 03 / 2025, page 221 / 362 / 147, an assignment module configured to assign a unique area session policy binding ID to the MBS service area. The unique area session policy binding ID is used as the second piece of information.

[0096] In one embodiment, the PCF may additionally comprise a third sending module configured to send an MBS policy authorization creation response to the location-dependent MBS session for the network function. The MBS policy authorization creation response may comprise the exclusive area session policy binding ID used as the second piece of information.

[0097] In one embodiment, when the MBS policy authorization creation request is authorized and at least one required QoS parameter derived from the MBS service information is allowed, a PCF may comprise a creation module configured to create an application session context for the location-dependent MBS session corresponding to the MBS session ID and second information. The PCF may comprise a second generation module configured to generate policy information for the location-dependent MBS session corresponding to the MBS session ID and second information. The PCF may comprise a second storage module configured to store the policy information for the location-dependent MBS session corresponding to the MBS session ID and second information, along with the MBS session ID and second information.

[0098] In a ninth aspect of the description, a network function is provided. The network function may comprise a first sending module configured to send an MBS session creation request to a location-dependent MBS session for an MB-SMF. The network function may further comprise a first receiving module. Petition 870250090277, dated 10 / 03 / 2025, page 222 / 362 / 147, is configured to receive an MBS session creation response for the location-dependent MBS session from MB-SMF. The MBS session creation request may include a second piece of information and an MBS session ID. The second piece of information and the MBS session ID may be used to uniquely identify an MBS session toward a specific MBS service area from a location-dependent MBS session and / or differentiate different location-based services provided through a location-dependent MBS session with the same MBS session ID and / or associate application function (AF) session information with the location-dependent MBS session in a specific MBS service area.

[0099] In one embodiment, when the network function is a NEF or an MBSF, the network function may additionally comprise a second receiver module configured to receive the MBS session creation request for the location-dependent MBS session of an AF. The network function may additionally comprise a second send module configured to send the MBS session creation response for the location-dependent MBS session to the AF.

[00100] In one embodiment, the network function may additionally comprise a third sending module configured to send an MBS policy authorization creation request for the location-dependent MBS session to a PCF. The MBS policy authorization creation request may include the second piece of information, the MBS session ID, and the MBS service information. The network function may additionally comprise a third receiving module configured to receive an MBS policy authorization creation response for the location-dependent MBS session from the PCF. The second piece of information and the MBS session ID may be used to create an application session context for the location-dependent MBS session. Petition 870250090277, dated 10 / 03 / 2025, page 223 / 362 / 147 location corresponding to the MBS session ID and the second piece of information.

[00101] In one embodiment, the network function may additionally comprise a fourth sending module configured to send an MBS policy authorization creation request for the location-dependent MBS session to a PCF. The MBS session creation request may include an MBS service area for a location-dependent MBS service and the MBS session ID and MBS service information. The network function may additionally comprise a fourth receiving module configured to receive an MBS policy authorization creation response for the location-dependent MBS session from the PCF. The MBS policy authorization creation response may comprise a unique area session policy binding ID used as the second piece of information.The second piece of information and the MBS session ID can be used to create an application session context for the location-dependent MBS session corresponding to the MBS session ID and the second piece of information.

[00102] In one embodiment, when a network function is a NEF or an MBSF, the network function may additionally comprise a fifth receiving module configured to receive the MBS policy authorization creation request for the location-dependent MBS session from an AF. The network function may additionally comprise a fifth sending module configured to send the MBS policy authorization creation response for the location-dependent MBS session to the AF.

[00103] In a tenth aspect of the description, a computer-readable storage medium is provided that stores instructions which, when executed by at least one processor, cause that processor to perform any of the methods according to the first, second, or third aspect of the description. Petition 870250090277, dated 03 / 10 / 2025, pp. 224 / 362 / 147

[00104] In an eleventh aspect of the description, a computer program product is provided, comprising instructions that, when executed on at least one processor, cause that processor to perform any of the methods according to the first, second, or third aspect of the description.

[00105] Many advantages can be achieved by applying the proposed solution according to the modalities described herein. In some modalities described herein, failures in creating application session context and / or policy association can be avoided. In some modalities described herein, the policy association created by the MBS policy control creates request with the authorized policy in the MBS policy authorization creates request for the same area session of a location-dependent MBS service can be well linked. In some modalities described herein, there is no significant added complexity to the current procedure. Some of the available information, such as area session ID, can be reused in the framework. In some modalities described herein, it has good compatibility with previous versions.The features and advantages described in this document are not limited to those mentioned above. Those skilled in the art will recognize additional features and advantages by reading the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[00106] The aspects, characteristics and benefits described above, and others of various embodiments of the present description, will become more fully apparent, by way of example, from the following detailed description with reference to the accompanying drawings, in which similar reference numbers or letters are used to designate similar or equivalent elements. The drawings are illustrated to facilitate a better understanding of the embodiments of the description and are not necessarily drawn to scale. Petition 870250090277, dated 03 / 10 / 2025, pages 225 / 362 / 147, in which: Figure 1A shows an example of delivery methods; Figure 1B shows the 5G system architecture for multicast and broadcast services; Figure 1C shows the 5G system architecture for multicast and broadcast services in reference point representation; Figure 1D shows a flowchart for creating an MBS session with PCC; Figure 2A shows a flowchart of a method according to an embodiment of the present description; Figure 2B shows a flowchart of a method according to another embodiment of the present description; Figure 3A shows a flowchart of a method according to another embodiment of the present description; Figure 3B shows a flowchart of a method according to another embodiment of the present description; Figure 3C shows a flowchart of a method according to another embodiment of the present description; Figure 3D shows a flowchart of a method according to another embodiment of the present description; Figure 3E shows a flowchart of a method according to another embodiment of the present description; Figure 4A shows a flowchart of a method according to another embodiment of the present description; Figure 4B shows a flowchart of a method according to another embodiment of the present description; Figure 4C shows a flowchart of a method according to another embodiment of the present description; Figure 4D shows a flowchart of a conformity method. Petition 870250090277, dated 03 / 10 / 2025, page 226 / 362 / 147 with another modality of the present description; Figure 4E shows a flowchart of a method according to another embodiment of the present description; Figure 5 shows a flowchart for creating an MBS session with PCC according to another modality of the present description; Figure 6 shows a flowchart for creating an MBS session with PCC according to another modality of the present description; Figure 7A shows a flowchart for creating an MBS session with PCC according to another modality of the present description; Figure 7B shows a flowchart for creating an MBS session with PCC according to another modality of the present description; Figure 8A is a block diagram showing a device suitable for practicing some of the sports described; Figure 8B is a block diagram showing an MBSMF according to one embodiment of the description; Figure 8C is a block diagram showing a PCF according to an embodiment of the description; and Figure 8D is a block diagram that shows a network function according to one embodiment of the description. Figure 9 shows an example of a communication system according to one modality of the description; Figure 10 shows a UE according to some modalities; Figure 11 shows a network node according to some modalities; Figure 12 is a block diagram of a host according to one embodiment of the description; Figure 13 is a block diagram illustrating a virtualization environment in which functions implemented by some modalities Petition 870250090277, dated 03 / 10 / 2025, pages 227 / 362 / 147, can be virtualized; and Figure 14 shows a communication diagram of a host communicating via a network node with a UE through a partially wireless connection, according to one embodiment of the description. DETAILED DESCRIPTION

[00107] The embodiments of this description are described in detail with reference to the accompanying drawings. It should be understood that these embodiments are discussed only for the purpose of enabling those skilled in the art to better understand and thus implement the present description, rather than suggesting any limitations on the scope of the present description. Reference throughout this descriptive report to features, advantages, or similar language does not imply that all features and advantages that can be obtained from the present description must be or are in any single embodiment of the description. Preferably, language referring to features and advantages is understood to mean that a specific feature, advantage, or aspect described in conjunction with an embodiment is included in at least one embodiment of the present description.Additionally, the characteristics, advantages, and aspects described in the description may be combined in any suitable manner in one or more modalities. A person skilled in the relevant art will recognize that the description may be practiced without one or more of the specific characteristics or advantages of a particular modality. In other cases, additional characteristics and advantages may be recognized in certain modalities that may not be present in all modalities of the description.

[00108] As used in this document, the term “network” refers to a network that follows any suitable communication standards, such as new radio (NR), long-term evolution (LTE), LTE Advanced, access Petition 870250090277, dated 03 / 10 / 2025, page 228 / 362 / 147 Wideband Code Division Multiple (WCDMA), High-Speed ​​Packet Access (HSPA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SCFDMA), and other wireless networks. A CDMA network may implement a radio technology, such as Universal Terrestrial Radio Access (UTRA), etc. UTRA includes WCDMA and other CDMA variants. A TDMA network may implement a radio technology, such as Global System for Mobile Communications (GSM). An OFDMA network can implement a radio technology such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, OFDMA Flash, Ad-hoc network, wireless sensor network, etc.In the following description, the terms “network” and “system” may be used interchangeably. Furthermore, communications between two devices on the network may be carried out in accordance with any suitable communication protocols, including, but not limited to, communication protocols defined by a standard organization such as 3GPP. For example, communication protocols may include first-generation (1G), 2G, 3G, 4G, 4.5G, 5G, 6G communication protocols and / or any other protocols currently known or to be developed in the future.

[00109] The term “network device” or “network node” or “network function” refers to any suitable function that can be implemented on a network entity (physical or virtual) of a communication network. For example, the network function can be implemented as a network element on dedicated hardware, as a software instance running on dedicated hardware, or as a virtualized function instantiated on an appropriate platform, for example, in a cloud infrastructure. Petition 870250090277, dated 03 / 10 / 2025, page 229 / 362 / 147, for example, the 5G (5GS) system may comprise a plurality of NFs, such as AMF (Access and Mobility Function), SMF (Session Management Function), AUSF (Authentication Service Function), UDM (Unified Data Management), PCF (Policy Control Function), AF (Application Function), NEF (Network Exposure Function), UPF (User Plane Function) and NRF (Network Repository Function), RAN (Radio Access Network), SCP (Service Communication Proxy), NWDAF (Network Data Analysis Function), NSSF (Network Slice Selection Function), NSSAAF (Network Slice Specific Authorization and Authentication Function), etc.For example, the 4G system (such as LTE (Long Term Evolution)) may include MME (Mobile Management Entity), HSS (Home Subscriber Server), Policy and Billing Rules Function (PCRF), Packet Data Network Connection Port (PGW), PGW control plane (PGW-C), Service Connection Port (SGW), SGW control plane (SGW-C), EUTRAN B Node (eNB), etc. In other embodiments, the network function may comprise different types of NFs, for example, depending on a specific network.

[00110] The term “terminal device” refers to any endpoint device that can access a communication network and receive services from it. By way of example and without limitation, a terminal device refers to a mobile terminal, user equipment (UE), or other suitable devices. UE may be, for example, a Subscriber Station (SS), a Portable Subscriber Station, a Mobile Station (MS), or an Access Terminal (AT). A terminal device may include, but is not limited to, a laptop computer, an image capture terminal device such as a digital camera, a gaming terminal device, a music storage and playback application, a mobile phone, a cell phone, a smartphone, a voice over IP (VoIP) phone, a wireless local area link phone, a tablet, a wearable device, a Petition 870250090277, dated 03 / 10 / 2025, pp. 230 / 362 / 147 personal digital assistant (PDA), a laptop computer, a desktop computer, a wearable terminal device, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, a laptop embedded equipment (LEE), a laptop mounted equipment (LME), a USB dongle, a smart device, a customer premises wireless equipment (CPE), and the like. In the following description, the terms “terminal device,” “terminal,” “user equipment,” and “UE” may be used interchangeably. As an example, a terminal device may represent a UE configured for communication in accordance with one or more communication standards promulgated by 3GPP (3rd Generation Partnership Project), such as the 3GPP LTE standard or the NR standard.As used in this document, a “user device” or “UE” may not necessarily have a “user” in the sense of a human user who owns and / or operates the relevant device. In some embodiments, a terminal device may be configured to transmit and / or receive information without direct human interaction. For example, a terminal device may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the communication network. Alternatively, a UE may represent a device that is intended for sale or operation by a human user, but may not initially be associated with a specific human user.

[00111] As yet another example, in an Internet of Things (IoT) scenario, a terminal device can represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another terminal device and / or network equipment. The terminal device can, in this case, be a machine-to-machine (M2M) device, which can, in a Petition 870250090277, dated 03 / 10 / 2025, p. 231 / 362 / 147, in the context of 3GPP, can be referred to as a machine-type communication device (MTC). As a particular example, the terminal device could be a UE implementing the 3GPP narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, measuring devices such as power meters, industrial machinery, or household or personal appliances, for example, refrigerators, televisions, personal wearable devices such as watches, etc. In other scenarios, a terminal device could represent a vehicle or other equipment that has the capability to monitor and / or report on its operational position or other functions associated with its operation.

[00112] References in the descriptive report to “a (numeral) modality”, “a (indefinite article) modality”, “an (indefinite article) exemplary modality” and the like indicate that the modality described may include a particular feature, structure or aspect, but it is not necessary that every modality includes the particular feature, structure or aspect. Furthermore, such phrases do not necessarily refer to the same modality. In addition, when a particular feature, structure or characteristic is described in conjunction with a modality, it is shown that it is within the knowledge of the person skilled in the art because it affects that feature, structure or characteristic in conjunction with other modalities, whether or not it is explicitly described.

[00113] It should be understood that, although the terms “first” and “second,” etc., may be used in this document to describe various elements, these elements should not be limited by these terms. These terms are only to distinguish one element from another. For example, a first element could be called a second element, and similarly, a second element could be called a first element, without departing from the scope of illustrative modalities. As used in this document, the term “and / or” includes any of the following: Petition 870250090277, dated 03 / 10 / 2025, pages 232 / 362 / 147 and all combinations of one or more of the associated listed terms.

[00114] As used in this document, the expression “at least one of A and B” or “at least one of A or B” should be understood as meaning “only A, only B, or both A and B”. The expression “A and / or B” should be understood as meaning “only A, only B, or both A and B”.

[00115] The terminology used in this document is intended only to describe particular modalities and is not intended to be limiting of exemplary modalities. As used in this document, the singular forms “a”, “an” and “the” are intended to include the plural forms as well unless the context clearly indicates otherwise. It will be further understood that the terms “comprises”, “that comprises”, “has”, “that has”, “includes” and / or “that includes”, when used in this document, specify the presence of features, elements and / or components presented, etc., but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof.

[00116] Note that these terms as used in this document are used only for ease of description and differentiation between nodes, devices or networks, etc. With the development of technology, other terms with similar / identical meanings may also be used.

[00117] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meanings as commonly understood by a person skilled in the art to which this description pertains.

[00118] Although the subject described here can be implemented in any appropriate type of system using any suitable components, the modalities described here are described in relation to a communication system conforming to the exemplary architecture. Petition 870250090277, dated 03 / 10 / 2025, page 233 / 362 / 147 of the system illustrated in Figure 1B and Figure 1C. For simplicity, the system architecture in Figure 1B and Figure 1C describes only a few exemplary elements. In practice, a communication system may additionally include any suitable additional elements to support communication between terminal devices or between a wireless device and another communication device, such as a landline phone, a service provider, or any other network node or terminal device. The communication system may provide communication and various types of services to one or more terminal devices to facilitate access by the terminal devices and / or the use of services provided by or through the communication system.

[00119] Figure 1B shows the 5G system architecture for multicast and broadcast services, which is the same as Figure 5.1-1 of TS 23.247 V18.1.0 3GPP. Figure 1C shows the 5G system architecture for multicast and broadcast services in reference point representation, which is the same as Figure 5.1-2 of TS 23.247 V18.1.0 3GPP.The architecture of the 5G MBS system can comprise functional entities such as PCF (Policy Control Function), MB-SMF (Multicast / Broadcast Session Management Function), SMF (Session Management Function), MB-UPF (Multicast / Broadcast User Plane Function), UPF (User Plane Function), AMF (Access and Mobility Management Function), NG-RAN (Next Generation Radio Access Network), UE (User Equipment), AF / AS (Application / Application Server Function), NEF (Network Exposure Function), MBSF (Multicast / Broadcast Service Function), MBSTF (Multicast / Broadcast Service Transport Function), UDM (Unified Data Management), UDR (Unified Data Repository), NRF (Network Repository Function), etc. These functional entities were described in clause 5.3.2 of TS 23.247 V18.1.0 3GPP. Petition 870250090277, dated 03 / 10 / 2025, pp. 234 / 362 / 147

[00120] MBSF is optional and can be placed together with NEF or AF / AS, and MBSTF is an optional network function.

[00121] The existing service-based interfaces for Nnrf, Nudm, and Nsmf have been enhanced to support MBS. The existing service-based interfaces for Npcf and Nnef have been enhanced to support MBS.

[00122] An MBS-enabled AF uses Nmbsf or Nnef to interact with MBSF.

[00123] SMF and MB-SMF can be co-located or deployed separately.

[00124] The MBS System Architecture may contain the following reference points: N3mb: Reference point between (R)AN and MB-UPF.

[00125] N4mb: Reference point between MB-SMF and MB-UPF.

[00126] N6mb: Reference point between MB-UPF and AF / AS.

[00127] N7mb: Reference point between MB-SMF and PCF.

[00128] N11mb: Reference point between AMF and MB-SMF.

[00129] N16mb: Reference point between SMF and MB-SMF.

[00130] N19mb: Reference point between UPF and MB-UPF.

[00131] N29mb: Reference point between MB-SMF and NEF.

[00132] Nmb1: Reference point between MB-SMF and MBSF.

[00133] Nmb2: Reference point between MBSF and MBSTF.

[00134] Nmb5: Reference point between MBSF and NEF.

[00135] Nmb8: Reference point between MBSTF and AF.

[00136] Nmb9: Reference point between MB-UPF and MBSTF.

[00137] Nmb10: Reference point between MBSF and AF.

[00138] Nmb12: Reference point between MBSF and PCF.

[00139] Nmb13: Reference point between MB-SMF and AF.

[00140] The existing reference points of N1, N2, N4, N10, N11, Petition 870250090277, dated 03 / 10 / 2025, pp. 235 / 362 / 147 N30 and N33 have been enhanced to offer MBS support.

[00141] Regarding functionalities, Nmb13, N29mb and Nmb1 are identical, Nmb5 and Nmb10 are identical, Nmb9 and N6mb are identical.

[00142] Figure 1D shows a flowchart for creating an MBS session with PCC, which is the same as Figure 7.1.1.3-1 of TS 23.247 V18.1.0 3GPP.

[00143] The implementation of dynamic PCC is optional. Clause 7.3.1 of TS 23.247 V18.1.0 3GPP describes the procedure when dynamic PCC is implemented as follows.

[00144] Steps 1 through 7 are optional and only applicable if TMGI is used as the MBS session ID and needs to be pre-allocated.

[00145] 1 to 9: Same as Figure 7.1.1.2-1 of TS 23.247 V18.1.0 3GPP.

[00146] 10. The NEF / MBSF may optionally, based on the local configuration, decide to interact with the PCF.

[00147] NOTE 1: In deployments without NEF and MBSF, AF optionally interacts with PCF in steps 11 to 18.

[00148] If NEF / MBSF decides to interact with PCF, steps 11 to 19 are performed and, in step 20, MBS Service Information is not provided to MB-SMF.

[00149] If NEF / MBSF decides not to interact with PCF, steps 12 to 19 will be skipped and, in step 20, MBS service information will be provided to MB-SMF.

[00150] 11. [Conditional] If the NEF / MBSF did not receive an MBS session ID from the AF in step 8, the NEF / MBSF sends an NmbsmfTMGIAllocate (1) request message to the MB-SMF and the MB-SMF allocates a TMGI and returns the TMGI to the NEF / MBSF via the Nmbsmf TMGI Allocate response (TMGI, expiration time).

[00151] 12. [Conditional] If the NEF / MBSF receives the AF location-dependent session request and there is a need to select the Petition 870250090277, dated 10 / 03 / 2025, page 236 / 362 / 147 same PCF for location-dependent MBS sessions, the NEF / MBSF will first use the BSF Discovery service to check if there is a PCF serving the MBS session with the MBS session ID using the Nbsf_management_Discovery operation. If there is a PCF registered for the MBS session ID, the NEF / MBSF interacts with that PCF and skips the following step 13.

[00152] NOTE 2: This step is not required in a deployment with a single PCF.

[00153] 13. [Conditional] If step 12 was not executed or interaction with the BSF showed that no PCF is registered for the MBS session ID, the NEF / MBSF checks PCF candidates by interacting with the NRF and selects a PCF, possibly based on the MBS service area.

[00154] 14. NEF / MBSF sends a request Npcf_MBSPolicy_Authorization_Create (MBS session ID, MBS service information (as defined in clause 6.14 of TS 23.247 V18.1.0 3GPP)) for the PCF.

[00155] 15. [Optional] PCF may retrieve authorization information for the UDR MBS session (see clause 6.10.2 of TS 23.247 V18.1.0 3GPP) and take it into account for subsequent authorization and QoS permission verification.

[00156] NOTE 3: This step is not required in a deployment with a single PCF if the authorization data is stored in the PCF.

[00157] 16. The PCF determines whether the request is authorized and, if authorized, the PCF derives the necessary QoS parameters based on the received MBS service information and determines whether this QoS is permitted. If the required QoS is permitted, the PCF generates the policy information for the MBS session (as defined in clause 6.10 of the TS). Petition 870250090277, dated 03 / 10 / 2025, pp. 237 / 362 / 147 23.247 V18.1.0 3GPP) and stores them along with the MBS session ID.

[00158] 17. If the request is authorized and the necessary QoS is enabled, the PCF registers with the BSF that it handles the MBS session using the NbsfmanagementRegister request (MBS session ID, PCF ID). It provides an identifier indicating that the policy association is for MBS and the MBS session ID, its own PCF ID, and optionally its PCF pool ID.

[00159] NOTE 4: This step is not required in a deployment with a single PCF.

[00160] 18. PCF sends a reply Npcf_MBSPolicy_Authorization_Create (Result indication) for NEF / MBSF.

[00161] If the request is not authorized or the required QoS is not permitted, the PCF indicates this in the response to the NEF / MBSF, which in turn informs the AF about this (by sending the NnefMBSSessionCreate response) and terminates this procedure.

[00162] 19. Same as step 10 in Figure 7.1.1.2-1 of TS 23.247 V18.1.0 3GPP.

[00163] 20. Same as step 11 in Figure 7.1.1.2-1 of TS 23.247 V18.1.0 3GPP with the difference that MBS Service Information is not present if the optional interaction between AF / NEF / MBSF and PCF has been performed (as MBS Service Information was provided to PCF in step 14).

[00164] 21. The MB-SMF checks the PCF using NRF.

[00165] 22. MB-SMF sends a request Npcf_MBSPolicyControl_Create (MBS session ID, [MBS service information (as defined in clause 6.14 of TS 23.247 V18.1.0 3GPP)]) for the MBS session toward the PCF. The MB-SMF forwards the MBS service information to the PCF if received from the NEF / MBSF in Petition 870250090277, dated 03 / 10 / 2025, page 238 / 362 / 147 previous stage 20.

[00166] If the PCF receives MBS service information from MBSMF, the PCF performs the subsequent steps 23 to 26. If the PCF does not receive MBS service information from MB-SMF, but has previously determined policy information for the MBS session (see step 16) corresponding to the MBS session ID received from MB-SMF, the PCF continues with step 27.

[00167] 23. If the PCF is not handling the MBS session ID, the PCF uses the BSF Registration service to check if there is already a PCF serving the MBS session. In this case, the PCF skips steps 24 to 26 and indicates in step 27 that the PCF serving the MBS session should be put in contact.

[00168] NOTE 5: This step is not required in a deployment with a single PCF.

[00169] 24. [Optional] The PCF may retrieve authorization information for the UDR MBS session (see clause 6.10.2 of TS 23.247 V18.1.0 3GPP) and take it into account for subsequent authorization and QoS permission verification.

[00170] NOTE 6: This step is not necessary if the authorization data is stored in the PCF.

[00171] 25. The PCF determines whether the request is authorized and, if authorized, the PCF derives the necessary QoS parameters based on the received MBS service information and determines whether this QoS is permitted. If the required QoS is permitted, the PCF generates the policy information for the MBS session (as defined in clause 6.10 of TS 23.247 V18.1.0 3GPP) and stores it along with the MBS session ID.

[00172] 26. If the request is authorized and the necessary QoS is enabled, the PCF registers with the BSF that it handles the MBS session using the Nbsf management register request (MBS session ID, PCF ID). Petition 870250090277, dated 03 / 10 / 2025, pp. 239 / 362 / 147 It provides an identifier indicating that the policy association is for MBS and the MBS session ID, its own PCF ID, and optionally, its PCF pool ID.

[00173] NOTE 7: This step is not required in a deployment with a single PCF.

[00174] 27. PCF responds with the answer Npcf_MBSPolicyControl_Create ([policy information for the MBS session (as defined in clause 6.10 of TS 23.247 V18.1.0 3GPP)], result indication).

[00175] If the request is not authorized or the required QoS is not permitted, the PCF indicates this in its response to MB-SMF, which in turn informs the AF about this (by sending the NmbsmfMBSSessionCreate response) and terminates this procedure.

[00176] If another PCF is handling the MBS session, the PCF indicates that another PCF handling the MBS session should be put in contact and provides an ID of that other PCF. The MB-SMF then repeats step 22 towards the other PCF.

[00177] 28-37: Same as steps 14-22 in Figure 7.1.1.2-1 of TS 23.247 V18.1.0 3GPP.

[00178] NOTE 8: Steps 33 to 36 can be performed in parallel with step 32.

[00179] Below is a brief summary of creating an MBS with a PCC procedure, which can cover two deployment scenarios.

[00180] Deployment-1: The AF / NEF / MBSF interacts with the PCF, for example, based on the local configuration, and then the MB-SMF interacts with the PCF.

[00181] Deployment-2: Only MB-SMF interacts with PCF (i.e., AF / NEF / MBSF does not interact with PCF).

[00182] When AF / NEF / MBSF decides to interact with PCF and if the Petition 870250090277, dated 03 / 10 / 2025, page 240 / 362 / 147 MBS session corresponds to a location-dependent service, AF / NEF / MBSF will check with the Binding Support Function (BSF) if there is a PCF that is already handling this MBS session ID.

[00183] If it exists, AF / NEF / MBSF will initiate the Npcf_MBSPolicyAuthorization_Create request with this PCF.

[00184] If it does not exist, the AF / NEF / MBSF will request the NRF to select a PCF instance. If the Npcf_MBSPolicyAuthorization_Create request, as described in TS 23.247 V18.1.0 3GPP from the AF / NEF / MBSF, is authorized and the necessary QoS is enabled, the PCF will be registered with the BSF using Nbsf_Management_Register_Request (MBS session ID, PCF ID), as described in TS 23.502 V18.0.0 3GPP.

[00185] When the MB-SMF needs to interact with the PCF, the MB-SMF can check the PCF using NRF and send the Npcf_MBSPolicyControl request, as described in TS 23.247 V18.1.0 3GPP, for that PCF ID. If this PCF is not handling the MBS session, then the PCF contacts the BSF (step 23) to register with the BSF. The PCF responds with the Npcf_MBSPolicyControl_Create response to continue the procedure with the PCF ID.

[00186] Several problems have been identified in the MBS PCC procedures for location-dependent MBS service.

[00187] As a first issue, there may be a failure in creating the MBS policy association by MB-SMF for location-dependent MBS services with the same MBS session ID. For example, this issue may apply to both Deployment-1 and Deployment-2.

[00188] If a PCF has created a policy association with an MBS session ID for a location-dependent session in the first MBS service area, when the MB-SMF invokes the Npcf_MBSPolicyControl_Create request with the PCF for the location-dependent MBS session with the same MBS session ID for the Petition 870250090277, dated 10 / 03 / 2025, pp. 241 / 362 / 147, second MBS service area, it is expected that PCF will reject the request due to the fact that the policy association for that MBS session ID already exists. If PCF, based on the implementation, accepts the second request, there will be no way to distinguish between both policy associations for future interactions.

[00189] As a second issue, there may be a failure in creating the application session context by AF / NEF / MBSF for the location-dependent MBS service with the same MBS session ID. For example, this issue may apply to Deployment-1.

[00190] If a PCF has created an application session context with an MBS session ID for the location-dependent session in the first MBS service area, when the AF / NEF / MBSF decides to interact with the PCF for the location-dependent MBS session with the same MBS session ID for the second MBS service area, the PCF will reject that request and indicate that the MBS application session context already exists for that MBS session ID. Alternatively, it could create another application session context, but then the PCF would have no way to link the policy context to the application session context.

[00191] As a third issue, there is no mechanism to link the policy association created by the Npcf_MBSPolicyControl_Create request with the authorized policy in the Npcf_MBSPolicyAuthorization_Create request for the same area session of a location-dependent MBS service when AF / NEF / MBSF decides to interact with PCF, for example, based on the local configuration. For example, this issue may apply to Deployment-1.

[00192] For example, when receiving Npcf_MBSPolicyAuthorization_Create requests from AF / NEF / MBSF for location-dependent MBS session in MBS Service Area 1 (abbreviated as “area session 1”) and location-dependent MBS session in area Petition 870250090277, dated 10 / 03 / 2025, pp. 242 / 362 / 147 of MBS 2 service (abbreviated as “area session 2”), if the PCF created two application session contexts and derived corresponding policies and when the MB-SMF creates the MBS policy associations for area session 1 and area session 2 above, currently, there is no mechanism for the PCF to retrieve the policy that the PCF previously derived for an area session.

[00193] To overcome or mitigate at least one of the problems mentioned above or other problems, the embodiments of the present description propose an improved solution for location-dependent MBS service.

[00194] In one embodiment, it can introduce the Area Session Policy Binding ID along with the Area Session Policy ID or MBS Service Area ID, or an identifier that uniquely identifies a session for a specific MBS Service Area with the same MBS Session ID to differentiate service areas of a location-dependent MBS service and ensure that Npcf_MBSPolicyAuthorization and Npcf_MBSPolicyControl requests for different location-based services with the same MBS Session ID terminate in the same PCF.

[00195] In one embodiment, it can introduce an additional attribute / information / identifier to the MBS creation procedure with PCC for a location-dependent MBS service to ensure a complete procedure and prevent failure cases.

[00196] Figure 2A shows a flowchart of a method according to an embodiment of the present description, which can be executed by an apparatus implemented in / as or communicatively coupled to a multicast / broadcast session management function (MB-SMF). As such, the apparatus can provide a means to perform various parts of method 200 as well as a means to perform other processes in conjunction with other components. Petition 870250090277, dated 03 / 10 / 2025, pp. 243 / 362 / 147

[00197] In block 202, MB-SMF can send a request to create a multicast / broadcast (MBS) service policy control for a location-dependent MBS session to a policy control function (PCF).

[00198] In one embodiment, the MBS policy control creation request may comprise an MBS session identifier (ID) and the first piece of information.

[00199] In one embodiment, the first MBS session ID and information can be used (e.g., by MB-SMF, etc.) to uniquely identify an MBS session toward a specific MBS service area from a location-dependent MBS session and / or create a policy association for the location-dependent MBS session corresponding to the MBS session ID and the first MBS session ID and / or differentiate different location-based services provided through the location-dependent MBS session with the same MBS session ID and / or associate application function (AF) session information with the location-dependent MBS session in a specific MBS service area and / or uniquely identify policy information for the location-dependent MBS session corresponding to the MBS session ID and the first MBS session ID.

[00200] MB-SMF can be any suitable node, entity, or function that can implement the Multicast / Broadcast (MB) session management function. In one embodiment, MB-SMF can be MBSMF or Multimedia Broadcast / Broadcast Service Gateway (MBMS GW) as described in TS 23.247 V18.1.0 3GPP.

[00201] A PCF can be any node, entity, or function suitable for implementing the policy control function. In one embodiment, the PCF can be a PCF as described in TS 23.247 V18.1.0 3GPP or a PCRF as described in TS 23.401 V18.0.0 3GPP. Petition 870250090277, dated 03 / 10 / 2025, pp. 244 / 362 / 147

[00202] The location-dependent MBS session may be the same as or similar to the location-dependent MBS session as described in TS 23.247 V18.1.0 3GPP.

[00203] The MBS policy control creation request can be an existing message or a new message. In one embodiment, the MBS policy control creation request can be an Npcf_MBSPolicyControl_Create request, for example, as described in TS 23.247 V18.1.0 3GPP.

[00204] The MBS session ID can be used to identify a Multicast / Broadcast MBS session by the communication system (such as 5GS) on the external interface towards the AF and between the AF and the UE, and towards the UE. The MBS session ID can have the following types: Temporary Mobile Group Identity (TMGI) (for broadcast and multicast MBS sessions) and / or source-specific Internet Protocol (IP) multicast address (for multicast MBS sessions). In one embodiment, the MBS session ID may be the same as or similar to the MBS session ID as described in TS 23.247 V18.1.0 3GPP.

[00205] The first piece of information may take any suitable form and the present description places no limit on this. For example, the first piece of information may be an identifier, an MBS service area, etc.

[00206] The first information can be obtained in various ways and the present description does not limit this. For example, the first information can be assigned / allocated by at least one of an AF, a network exposure function (NEF), a multicast / broadcast service function (MBSF), or a PCF or MB-SMF.

[00207] In one embodiment, the first piece of information may comprise at least one of an MBS service area or ID. The ID may be any suitable ID, and the present description does not impose any limits on this. For each service area of ​​a dependent MBS service Petition 870250090277, dated 03 / 10 / 2025, p. 245 / 362 / 147, location, AF / NEF / MBSF / PCF may mark it with a unique identifier, for example, an AF ID plus a unique character sequence or a timestamp plus a unique character sequence. The MBS service area may be the area within which data from a Multicast or Broadcast MBS session may be sent. For location-dependent MBS, for each MBS service area, an area session ID, which is unique per MBS session ID, is allocated and the same location-dependent content data for an MBS session is delivered to the UE(s) within an MBS service area.

[00208] In one embodiment, the ID may comprise at least one binding ID or one area session policy ID. The binding ID may be any suitable ID, and the present description does not impose limits on this. For each service area of ​​a location-dependent MBS service, the AF / NEF / MBSF may tag it with a unique identifier, for example, an AF ID plus a unique character string or a timestamp plus a unique character string.

[00209] In one embodiment, the linking ID may be assigned by at least one AF, a network exposure function (NEF), or a multicast / broadcast service function (MBSF).

[00210] The area session policy ID can be any suitable ID, and the present description does not impose any limits on it. In one embodiment, the area session policy ID can be assigned by MBSMF.

[00211] In one embodiment, the area session policy ID may comprise at least one area session ID or one area session policy binding ID. The area session policy ID may be a unique identifier within an MBS session used for an MBS session with location-dependent content. When present, the area session ID, along with the MBS session ID, as TMGI, is used. Petition 870250090277, dated 10 / 03 / 2025, pp. 246 / 362 / 147 to uniquely identify the data flow of an MBS session in a specific MBS service area. The area session policy binding ID can be any suitable ID, and the present description does not impose any limit on this.

[00212] In one mode, the area session policy binding ID can be assigned by at least one AF, one NEF, one MBSF, or one PCF.

[00213] In one embodiment, if a request to create an MBS policy authorization for the location-dependent MBS session has not been sent to the PCF (for example, if the AF / NEF / MBSF does not interact with the PCF), the area session ID may be used as the area session policy ID.

[00214] In one embodiment, if the request to create MBS policy authorization for the location-dependent MBS session has been sent to the PCF (for example, if AF / NEF / MBSF interacts with the PCF), the area session policy binding ID may be used as the area session policy ID.

[00215] In one embodiment, when MB-SMF receives the binding ID or the Area Session Policy binding ID from a network function, the binding ID or the Area Session Policy binding ID can be used as the Area Session Policy ID.

[00216] In one embodiment, when MB-SMF receives the MBS service area from a network function, MB-SMF can generate the area session policy ID based on the MBS service area. Alternatively, the MBS service area can be used as the area session policy ID.

[00217] In block 204, MB-SMF may receive a response to create an MBS policy control for the location-dependent MBS session of the PCF. Petition 870250090277, dated 03 / 10 / 2025, pp. 247 / 362 / 147

[00218] The MBS policy control creation response may include any appropriate information, such as policy information for the location-dependent MBS session and result indication, etc.

[00219] The MBS policy control creation response can be an existing message or a new message. In one embodiment, the MBS policy control creation response can be an Npcf_MBSPolicyControl_Create response, for example, as described in TS 23.247 V18.1.0 3GPP.

[00220] Figure 2B shows a flowchart of a method according to another embodiment of the present description, which can be performed by an apparatus implemented in / as or communicatively coupled to the MBSMF. As such, the apparatus can provide a means to perform various parts of method 210 as well as a means to perform other processes in conjunction with other components. For some parts that were described in the embodiments above, their description is omitted here for the sake of brevity.

[00221] In block 212, MB-SMF may receive a request to create an MBS session for the location-dependent MBS session of a network function.

[00222] In one embodiment, after MB-SMF receives the MBS session creation request for the location-dependent MBS session from a network function in block 212, it can send an MBS policy control creation request for a location-dependent MBS session to PCF in block 202 of Figure 2A.

[00223] A network function can be any suitable network function, for example, as described in various 3GPP specifications, such as TS 23.501 V18.0.0 3GPP, TS 23.682 V17.3.0 3GPP, TS 23.247 V18.1.0 3GPP.

[00224] In one embodiment, the network function may comprise Petition 870250090277, dated 03 / 10 / 2025, page 248 / 362 / 147 minus one AF, one NEF or one MBSF.

[00225] The AF can be any suitable node that can provide a function similar to or the same as that of the AF, as described in TS 23.501 V18.0.0 3GPP, or that of the Application Server (AS) or Service Capacity Server (SCS), as described in TS 23.682 V17.3.0 3GPP. For example, the application node can be a content provider or a multicast source or a broadcast source.

[00226] The NEF can be any suitable node that can provide similar or equal function to the NEF, as described in TS 23.501 V18.0.0 3GPP, or the Service Capacity Exposure Function (SCEF), as described in TS 23.682 V17.3.0 3GPP.

[00227] The MBSF may be any suitable node that can provide similar or equal function to the MBSF, as described in TS 23.501 V18.0.0 3GPP, or the Broadcast and Multicast Service Center (BM-SC), as described in TS 23.682 V17.3.0 3GPP.

[00228] The MBS session creation request can be an existing message or a new message. In one embodiment, the MBS session creation request can be an Nmbsmf_MBSSession_Create request, for example, as described in TS 23.247 V18.1.0 3GPP.

[00229] In one embodiment, the MBS session creation request may comprise a second piece of information and the MBS session ID.

[00230] In one embodiment, the second piece of information and the MBS session ID can be used to uniquely identify an MBS session toward a specific MBS service area from a location-dependent MBS session and / or differentiate different location-based services provided through location-dependent MBS sessions with the same MBS session ID and / or associate application function (AF) session information with the location-dependent MBS session. Petition 870250090277, dated 03 / 10 / 2025, page 249 / 362 / 147 location in a specific MBS service area.

[00231] The second piece of information may be any suitable information and the present description makes no limit to it. In one embodiment, the second piece of information may comprise at least a binding ID, an area session policy binding ID, or an MBS service area.

[00232] In a modality, the linking ID can be assigned by at least one of an AF, a NEF, or an MBSF.

[00233] In one modality, the area session policy binding ID can be assigned by at least one of the AF, NEF, MBSF, or PCF.

[00234] In block 214, MB-SMF can send an MBS session creation response for the location-dependent MBS session for a network function.

[00235] In one embodiment, after MB-SMF receives an MBS policy control creation response for the location-dependent MBS session from PCF in block 204, it can send an MBS session creation response for the location-dependent MBS session for the network function in block 214 of Figure 2A.

[00236] The MBS session creation response can be an existing message or a new message. In one embodiment, the MBS session creation response can be an Nmbsmf_MBSSession_Create response, for example, as described in TS 23.247 V18.1.0 3GPP.

[00237] The MBS session creation response may include any appropriate information, such as an incoming address (Internet Protocol (IP) address and port).

[00238] In one embodiment, the MBS session creation response may comprise an area session ID and second information. Petition 870250090277, dated 03 / 10 / 2025, pp. 250 / 362 / 147

[00239] In one embodiment, if the network function such as AF / NEF / MBSF has the mechanism to associate the area session ID and second information, such as the binding ID, when receiving the MBS session creation response, such as the Nmbsmf_MBSSession_Create response, there is no need to send back the second information, such as the binding ID, in the response to the location-dependent MBS service.

[00240] Figure 3A shows a flowchart of a method according to another embodiment of the present description, which can be performed by an apparatus implemented in / as or communicatively coupled to a PCF. As such, the apparatus can provide a means to perform various parts of method 300, as well as a means to perform other processes in conjunction with other components. For some parts that were described in the embodiments above, their description is omitted here for brevity.

[00241] In block 302, the PCF may receive a request to create an MBS policy control for a location-dependent MBS session of an MB-SMF.

[00242] In one embodiment, the MBS policy control creation request may comprise an MBS session ID and the first piece of information.

[00243] In one embodiment, the first piece of information may comprise at least one MBS ID or service area.

[00244] In one mode, the ID may comprise at least one binding ID or one area session policy ID.

[00245] In one embodiment, the linking ID may be assigned by at least one AF, a Network Exposure Function (NEF), or a Multicast / Broadcast Service (MBSF) function.

[00246] In one mode, the linking ID can be assigned by at least one AF, one network exposure function (NEF), or one Petition 870250090277, dated 03 / 10 / 2025, pp. 251 / 362 / 147 multicast / broadcast service function (MBSF).

[00247] In one mode, the area session policy binding ID can be assigned by at least one AF, one NEF, one MBSF, or one PCF.

[00248] In one embodiment, if a request to create an MBS policy authorization for the location-dependent MBS session has not been sent to PCF, the area session ID may be used as the area session policy ID.

[00249] In one embodiment, if the request to create MBS policy authorization for the location-dependent MBS session has been sent to PCF, the area session policy binding ID may be used as the area session policy ID.

[00250] In one embodiment, the first MBS session ID and information can be used to uniquely identify an MBS session toward a specific MBS service area from a location-dependent MBS session and / or create a policy association for the location-dependent MBS session corresponding to the MBS session ID and the first MBS session ID and / or differentiate different location-based services provided through the location-dependent MBS session with the same MBS session ID and / or associate application function (AF) session information with the location-dependent MBS session in a specific MBS service area and / or uniquely identify policy information for the location-dependent MBS session corresponding to the MBS session ID and the first MBS session ID and / or link the policy association with the application session context for the location-dependent MBS session corresponding to the MBS session ID and the first MBS session ID and / or link the policy association to the application session context for the location-dependent MBS session corresponding to the MBS session ID and the first MBS session ID and / or link the policy association to the application session context for the location-dependent MBS session corresponding to the MBS session ID and the first MBS session ID and / or link the policy association to the location-dependent MBS session context.MBS session ID and initial information.

[00251] For example, MB-SMF can send the MBS policy control creation request in block 202 of Figure 2A, and then PCF Petition 870250090277, dated 10 / 03 / 2025, pages 252 / 362 / 147, may receive the request to create MBSMF policy control.

[00252] In block 304, optionally, when the MBS policy control creation request does not include MBS service information, the PCF can find policy information for the location-dependent MBS session matching the MBS session ID and the first piece of information.

[00253] For example, if optional interaction between a network function such as AF / NEF / MBSF and the PCF has been performed (for example, MBS service information was provided to a PCF in the Npcf_MBSPolicy_Authorization_Create request), the MBS policy control creation request does not include MBS service information. In this case, the PCF may have generated and stored policy information for the location-dependent MBS session corresponding to the MBS session ID and the first piece of information. The PCF can find the policy information for the location-dependent MBS session corresponding to the MBS session ID and the first piece of information.

[00254] In block 306, PCF can send an MBS policy control creation response for the location-dependent MBS session to MB-SMF. For example, the MBS policy control creation response might include policy information for the location-dependent MBS session corresponding to the MBS session ID and the first piece of information.

[00255] Figure 3B shows a flowchart of a method according to another embodiment of the present description, which can be performed by an apparatus implemented in / as or communicatively coupled to a PCF. As such, the apparatus can provide a means to perform various parts of method 310 as well as a means to perform other processes in conjunction with other components. For some parts that were described in Petition 870250090277, dated 03 / 10 / 2025, pp. 253 / 362 / 147 modalities above, the description of which is omitted here for the sake of brevity.

[00256] In block 312, the PCF may receive a request to create an MBS policy control for a location-dependent MBS session from an MB-SMF. Block 312 is the same as block 302 in Figure 3A.

[00257] In one embodiment, when the MBS policy control creation request includes MBS service information and is authorized and at least one required quality of service (QoS) parameter derived from the MBS service information is allowed, blocks 314 and 316 may be performed.

[00258] MBS service information may be the same as or similar to MBS service information as defined in clause 6.14 of TS 23.247 V18.1.0 3GPP.

[00259] For example, if the optional interaction between a network function such as AF / NEF / MBSF and the PCF has not been performed (for example, MBS service information has not been provided to the PCF), the MBS policy control creation request may include the MBS service information. In this case, the PCF may generate and store policy information for the MBS session dependent on the location corresponding to the MBS session ID and the first piece of information.

[00260] In block 314, PCF can generate policy information for the MBS session dependent on the location corresponding to the MBS session ID and the first piece of information. For example, the policy information may be the same as or similar to the policy information as defined in clause 6.10 of TS 23.247 V18.1.0 3GPP.

[00261] In block 316, PCF can store the policy information for the location-dependent MBS session corresponding to the MBS session ID and the first information along with the MBS session ID and the first information. Petition 870250090277, dated 03 / 10 / 2025, pp. 254 / 362 / 147

[00262] In block 318, the PCF can send an MBS policy control creation response to the location-dependent MBS session for the MB-SMF. Block 318 is the same as block 306 in Figure 3A.

[00263] Figure 3C shows a flowchart of a method according to another embodiment of the present description, which can be performed by an apparatus implemented in / as or communicatively coupled to a PCF. As such, the apparatus can provide a means to perform various parts of method 320 as well as a means to perform other processes in conjunction with other components. For some parts that were described in the embodiments above, their description is omitted here for the sake of brevity.

[00264] In block 322, the PCF may receive a request to create MBS policy authorization for the location-dependent MBS session of a network function.

[00265] In one embodiment, the MBS policy authorization creation request may include the second information and the MBS session ID and MBS service information.

[00266] In one embodiment, the network function may comprise at least one AF, one NEF or one MBSF.

[00267] The MBS policy authorization creation request can be an existing message or a new message. In one embodiment, the MBS policy authorization creation request can be an Npcf_MBSPolicy_Authorization_Create request, for example, as described in TS 23.247 V18.1.0 3GPP.

[00268] The second piece of information may be in any suitable format and the present description does not impose any limits on this. For example, the second piece of information may be an identifier, an MBS service area, etc.

[00269] The second piece of information can be obtained in various ways, and the present description does not limit this. For example, the second Petition 870250090277, dated 03 / 10 / 2025, page 255 / 362 / 147 information can be assigned / allocated by at least one of an AF, a network exposure function (NEF) and a multicast / broadcast service function (MBSF).

[00270] In one embodiment, the second piece of information and the MBS session ID can be used to uniquely identify an MBS session toward a specific MBS service area from a location-dependent MBS session and / or differentiate different location-based services provided through location-dependent MBS sessions with the same MBS session ID and / or associate application function (AF) session information with the location-dependent MBS session in a specific MBS service area.

[00271] In one embodiment, the second piece of information may comprise at least one binding ID, an area session policy binding ID, or an MBS service area.

[00272] In a modality, the linking ID can be assigned by at least one of an AF, a NEF, or an MBSF.

[00273] In a modality, the area session policy binding ID can be assigned by at least one of the following: AF, NEF, or MBSF.

[00274] In block 324, PCF can send an MBS policy authorization creation response for the location-dependent MBS session for a network function.

[00275] The MBS policy authorization creation response can be an existing message or a new message. In one embodiment, the MBS policy authorization creation response can be an Npcf_MBSPolicy_Authorization_Create response, for example, as described in TS 23.247 V18.1.0 3GPP.

[00276] Figure 3D shows a flowchart of a method according to another embodiment of the present description, which can be performed by a Petition 870250090277, dated 03 / 10 / 2025, pp. 256 / 362 / 147 apparatus implemented in / as or communicatively coupled to a PCF. As such, the apparatus may provide a means to perform various parts of method 330 as well as a means to perform other processes in conjunction with other components. For some parts that have been described in the embodiments above, their description is omitted here for the sake of brevity.

[00277] In block 332, the PCF may receive a request to create an MBS policy authorization for the location-dependent MBS session of a network function. The MBS policy authorization creation request may include an MBS service area for a location-dependent MBS service and the MBS session ID and MBS service information.

[00278] In block 334, PCF can assign a unique area session policy binding ID to the MBS service area.

[00279] In one mode, the exclusive area session policy binding ID can be used as the second piece of information.

[00280] For example, PCF can assign a unique area session policy association ID to the MBS service area based on the MBS service area in the MBS policy authorization creation request.

[00281] In block 336, PCF can send an MBS policy authorization creation response for the location-dependent MBS session for a network function.

[00282] In one embodiment, the MBS policy authorization creation response may comprise the exclusive area session policy binding ID used as the second piece of information.

[00283] Figure 3E shows a flowchart of a method according to another embodiment of the present description, which can be performed by an apparatus implemented in / as or communicatively coupled to a Petition 870250090277, dated 03 / 10 / 2025, pages 257 / 362 / 147 PCF. As such, the apparatus can provide a means to perform various parts of method 340 as well as a means to perform other processes in conjunction with other components. For some parts that have been described in the embodiments above, their description is omitted here for the sake of brevity.

[00284] In one mode, when the MBS policy authorization creation request is authorized and at least one required QoS parameter derived from MBS service information is allowed, blocks 342, 344, and 346 can be performed.

[00285] In block 342, PCF can create an application session context for the MBS session dependent on the location corresponding to the MBS session ID and the second piece of information.

[00286] The application session context may be the same as or similar to the application session context as described in TS 23.247 V18.1.0 3GPP.

[00287] In block 344, PCF can generate policy information for the MBS session dependent on the location corresponding to the MBS session ID and the second piece of information. For example, the policy information may be the same as or similar to the policy information as defined in clause 6.10 of TS 23.247 V18.1.0 3GPP.

[00288] In block 346, PCF can store the policy information for the location-dependent MBS session corresponding to the MBS session ID and the second piece of information along with the MBS session ID and the second piece of information.

[00289] Figure 4A shows a flowchart of a method according to another embodiment of the present description, which can be performed by an apparatus implemented in / as or communicatively coupled to a network function. As such, the apparatus can provide a means to perform various parts of method 400 as well as a means to perform other processes in Petition 870250090277, dated 03 / 10 / 2025, pp. 258 / 362 / 147 together with other components. For some parts that were described in the modalities above, their description is omitted here for the sake of brevity.

[00290] In block 402, a network function can send an MBS session creation request for a location-dependent MBS session for an MB-SMF.

[00291] In block 404, a network function may receive an MBS session creation response for the MBS session dependent on the MB-SMF location.

[00292] In one embodiment, when a network function is an AF, a network function can send the MBS session creation request for the location-dependent MBS session directly to the MBSMF. The network function can receive the MBS session creation response for the location-dependent MBS session directly from the MB-SMF.

[00293] In one embodiment, when a network function is an AF, a network function can send the MBS session creation request for the location-dependent MBS session to the MB-SMF via a NEF or MBSF. The network function can receive the MBS session creation response for the location-dependent MBS session from the MB-SMF via the NEF or MBSF.

[00294] In one embodiment, the MBS session creation request may include the second piece of information and an MBS session ID.

[00295] In one embodiment, the second piece of information and the MBS session ID can be used to uniquely identify an MBS session toward a specific MBS service area from a location-dependent MBS session and / or differentiate different location-based services provided through the location-dependent MBS session with the same MBS session ID and / or associate application function (AF) session information with the location-dependent MBS session. Petition 870250090277, dated 03 / 10 / 2025, page 259 / 362 / 147 location in a specific MBS service area.

[00296] In one embodiment, the second piece of information may comprise at least one binding ID, an area session policy binding ID, or an MBS service area.

[00297] In a modality, the linking ID can be assigned by at least one of an AF, a NEF, or an MBSF.

[00298] In a modality, the area session policy binding ID can be assigned by at least one of the following: AF, NEF, or MBSF.

[00299] In one embodiment, the MBS session creation response may comprise an area session ID and second information.

[00300] In one embodiment, the network function may comprise at least one AF, one NEF or one MBSF.

[00301] Figure 4B shows a flowchart of a method according to another embodiment of the present description, which can be performed by a device implemented in / as or communicatively coupled to a network function. As such, the device can provide a means to perform various parts of method 410 as well as a means to perform other processes in conjunction with other components. For some parts that were described in the embodiments above, their description is omitted here for brevity.

[00302] In one embodiment, the network function can be a NEF or an MBSF.

[00303] In block 412, the network function can receive the MBS session creation request for the location-dependent MBS session of an AF. For example, after receiving the MBS session creation request in block 412, the network function can send the MBS session creation request for the location-dependent MBS session to MB-SMF in block 402 of Figure 4A. Petition 870250090277, dated 03 / 10 / 2025, pp. 260 / 362 / 147

[00304] In block 414, the network function can send the MBS session creation response to the location-dependent MBS session to the AF. For example, the network function can receive the MBS session creation response from MB-SMF in block 404 of Figure 4A. Then, the network function can send the MBS session creation response to the AF in block 414 of Figure 4A.

[00305] Figure 4C shows a flowchart of a method according to another embodiment of the present description, which can be performed by an apparatus implemented in / as or communicatively coupled to a network function. As such, the apparatus can provide a means to perform various parts of method 420 as well as a means to perform other processes in conjunction with other components. For some parts that were described in the embodiments above, their description is omitted here for the sake of brevity.

[00306] In block 422, the network function can send a request to create an MBS policy authorization for the location-dependent MBS session to a PCF. In one embodiment, the MBS policy authorization creation request can comprise the second information and the MBS session ID and MBS service information.

[00307] In one embodiment, when the network function can optionally, for example, based on the local configuration, decide to interact with the PCF, the network function can send the MBS policy authorization creation request for the location-dependent MBS session to the PCF in block 422.

[00308] In block 424, the network function may receive an MBS policy authorization creation response for the location-dependent MBS session of a PCF.

[00309] In one mode, the network function can use the second piece of information and the MBS session ID can be used to create a context. Petition 870250090277, dated 03 / 10 / 2025, page 261 / 362 / 147 of application session for the MBS session dependent on location corresponding to the MBS session ID and the second piece of information.

[00310] Figure 4D shows a flowchart of a method according to another embodiment of the present description, which can be performed by an apparatus implemented in / as or communicatively coupled to a network function. As such, the apparatus can provide a means to perform various parts of method 430 as well as a means to perform other processes in conjunction with other components. For some parts that were described in the embodiments above, their description is omitted here for the sake of brevity.

[00311] In block 432, the network function can send a request to create an MBS policy authorization for the location-dependent MBS session to a PCF. In one embodiment, the MBS session creation request can comprise an MBS service area for a location-dependent MBS service and the MBS session ID and MBS service information.

[00312] In block 434, the network function may receive an MBS policy authorization creation response for the location-dependent MBS session of the PCF. In one embodiment, the MBS policy authorization creation response may comprise a unique area session policy binding ID used as the second piece of information.

[00313] In one embodiment, the second piece of information and the MBS session ID can be used to create an application session context for the location-dependent MBS session that matches the MBS session ID and the second piece of information.

[00314] In one embodiment, when the network function is an AF, the network function can send the MBS policy authorization creation request for the location-dependent MBS session directly to the PCF. The network function can receive an authorization creation response. Petition 870250090277, dated 10 / 03 / 2025, pp. 262 / 362 / 147 regarding MBS policy for location-dependent MBS session directly from PCF.

[00315] In one embodiment, when the network function is an AF, the network function can send the MBS policy authorization creation request for the location-dependent MBS session to the PCF via a NEF or an MBSF. The network function can receive an MBS policy authorization creation response for the location-dependent MBS session from the PCF via the NEF or MBSF.

[00316] Figure 4E shows a flowchart of a method according to another embodiment of the present description, which can be performed by an apparatus implemented in / as or communicatively coupled to a network function. As such, the apparatus can provide a means to perform various parts of method 440 as well as a means to perform other processes in conjunction with other components. For some parts that were described in the embodiments above, their description is omitted here for the sake of brevity.

[00317] In one embodiment, the network function can be a NEF or an MBSF.

[00318] In block 442, the network function can receive the MBS policy authorization creation request for the location-dependent MBS session of an AF. For example, after receiving the MBS policy authorization creation request, the network function can send the MBS policy authorization creation request to the PCF in block 432 of Figure 4D.

[00319] In block 444, the network function can send the MBS policy authorization creation response for the location-dependent MBS session to the AF. For example, the network function can receive the MBS policy authorization creation response from the PCF in block 434 of Figure 4D. Then, the network function can send the authorization creation response. Petition 870250090277, dated 03 / 10 / 2025, pp. 263 / 362 / 147 regarding MBS policy to AF.

[00320] In one embodiment, three alternatives can be proposed to address the problems. For example, it is possible to introduce the area session policy binding ID along with the area session policy ID. It is possible to introduce the MBS service area. It is possible to use an identifier that uniquely identifies a session for a specific MBS service area within the same MBS session ID. One may not care about the format or meaning of the identifier, since the identifier is used as a session binder. For example, one could use “binding ID.”

[00321] Alternative 1: Area session policy binding ID along with the area session policy ID.

[00322] In one embodiment, an area session policy binding ID can be assigned by AF / NEF / MBSF or by PCF, which can be used to uniquely identify an MBS session for a specific MBS service area within the same MBS session ID.

[00323] In one embodiment, the Area Session Policy ID can be a new attribute introduced in the MB-SMF policy control creation procedure for a location-dependent MBS service. MB-SMF can use either the Area Session ID or the Area Session Policy Binding ID as the Area Session Policy ID.

[00324] Option 1: Area session policy binding ID can be assigned by AF / NEF / MBSF.

[00325] In one mode, when AF / NEF / MBSF does not interact with PCF, MB-SMF can use the area session ID as the area session policy ID.

[00326] In one mode, when the AF / NEF / MBSF decides to interact with the PCF, for example, based on the local configuration, the AF / NEF / MBSF can assign a new session policy binding ID. Petition 870250090277, dated 03 / 10 / 2025, page 264 / 362 / 147 of area and send it to PCF.

[00327] In one mode, AF / NEF / MBSF can also include area session policy binding ID in the Nmbsmf_MBSSession_Create request sent to MB-SMF.

[00328] In one embodiment, MB-SMF can use the area session policy binding ID as the area session policy ID and send it to PCF, so that PCF can retrieve the previously authorized policy when AF / NEF / MBSF interacted with PCF.

[00329] In one mode, MB-SMF can include the area session policy binding ID in the Nmbsmf_MBSSession_Create response.

[00330] Figure 5 shows a flowchart for creating an MBS session with PCC according to another modality of the present description.

[00331] Steps 1 through 7 are optional and only applicable if TMGI is used as the MBS session ID and needs to be pre-allocated.

[00332] Steps 1 to 9: Same as Figure 7.1.1.2-1 of TS 23.247 V18.1.0 3GPP.

[00333] Clause 7.1.1.2 of TS 23.247 V18.1.0 3GPP describes steps 1 through 9 below.

[00334] 1. AF sends a request message NnefMBSTMGIAllocate (TMGI number, [MBS service area]) to NEF / MBSF to request the allocation of one or more TMGI(s) to identify new MBS sessions. The MBS service area indicates the possible service area for those TMGI(s) to be allocated, which may be required for local MBS.

[00335] NOTE 1: Depending on the network deployment and use case, MB-SMF may receive requests from AF directly or via NEF or via MBSF or via both NEF and MBSF.

[00336] 2. The NEF / MBSF verifies the AF authorization. If information Petition 870250090277, dated 03 / 10 / 2025, pp. 265 / 362 / 147, regarding geographic area or civic address provided by the AF as an MBS service area, NEF / MBSF performs the translation.

[00337] NOTE 2: NEF is not required if the AF is in a trusted domain.

[00338] 3. The NEF / MBSF verifies and selects an MB-SMF using NRF or based on local configuration, possibly based on the MBS service area.

[00339] 4. The NEF / MBSF sends a request message Nmbsmf_TMGI_Allocate (TMGI number) to MB-SMF.

[00340] 5. MB-SMF allocates TMGI(s) and returns the TMGI(s) to NEF / MBSF via the response NmbsmfTMGIAllocate (TMGI(s), expiration time).

[00341] 6. The NEF or MBSF responds to the AF by sending a reply. NnefMBSTMGIAllocate (TMGI(s), expiration time).

[00342] 7. The AF may issue a Service Announcement to UEs. The AF informs UEs about MBS session information with MBS session ID, for example, TMGI, SSM and possibly other information, for example, MBS service area, session description information, etc.

[00343] MBS service area information may be a cell ID list, TAI list, geographic area information, or civic address information. Among these, the cell ID list and the TAI list should only be used by AFs residing in a domain of trust and when the AFs are aware of this information.

[00344] The EU needs to be aware of whether the service is broadcast or multi-broadcast in order to decide whether UNIR should be implemented.

[00345] 8. The content provider's AF can provide a description for an MBS session (possibly providing information for a previously allocated TMGI for NEF via an Nnef_MBSSession_Create request ([MBS session ID], MBS service type, Petition 870250090277, dated 03 / 10 / 2025, pp. 266 / 362 / 147 MBS service information, [TMGI allocation request], [MBS service area], [any UE indication], [MBS session start and end time], [MBS session status], [inbound transport address request indication], [location-dependent session request], [FSA ID(s)]). If steps 1-6 have not been performed beforehand, the AF may provide an MBS session ID containing an SSM or may request that the network allocate an MBS session ID (i.e., TMGI). The AF provides the MBS service type (i.e., multicast service or broadcast service) and MBS service information (as defined in clause 6.14 of TS 23.247 V18.1.0 3GPP). AF can provide the indication of any UE (indicating whether a multicast MBS session is open to any UEs), MBS service area, MBS session start and end time, and MBS session status (active / inactive).Additionally, the AF request may also indicate that the allocation of an inbound transport address is requested and that the AF request is for a location-dependent MBS service.

[00346] If geographic area or civic address information was provided by the AF as the MBS service area, the NEF / MBSF translates the MBS service area to the cell ID list or TAI list.

[00347] For broadcast communication, AF may determine the MBS FSA ID(s) for the broadcast MBS session based on commercial agreements and include them in the MBS session description.

[00348] NOTE 3: The MBS session state applies to the multicast MBS session.

[00349] 9. NEF / MBSF verifies authorization from the content provider.

[00350] 10. The NEF / MBSF may optionally, based on the local configuration, decide to interact with a PCF.

[00351] NOTE 1: In deployment without NEF and MBSF, AF interacts Petition 870250090277, dated 03 / 10 / 2025, pages 267 / 362 / 147 optionally with the PCF in steps 11 to 18.

[00352] If the NEF / MBSF decides to interact with a PCF, steps 11 to 19 are performed and, in step 20, MBS Service Information is not provided to MB-SMF.

[00353] If the NEF / MBSF decides not to interact with a PCF, steps 12 to 19 will be skipped and, in step 20, MBS service information will be provided to MB-SMF.

[00354] 11. [Conditional] If the NEF / MBSF did not receive an MBS session ID from the AF in step 8, the NEF / MBSF sends an Nmbsmf_TMGI_Allocate request message to the MB-SMF and the MB-SMF allocates a TMGI and returns the TMGI to the NEF / MBSF via the Nmbsmf_TMGI_Allocate response (TMGI, expiration time).

[00355] 12. [Conditional] If the NEF / MBSF receives the location-dependent session request from the AF and there is a need to select the same PCF for location-dependent MBS sessions, the NEF / MBSF will first use the BSF Discovery service to check if there is a PCF serving the MBS session with the MBS session ID using the Nbsf_management_Discovery operation. If there is a registered PCF for the MBS session ID, the NEF / MBSF interacts with that PCF and skips the following step 13.

[00356] NOTE 2: This step is not required in a deployment with a single PCF.

[00357] 13. [Conditional] If step 12 was not executed or interaction with the BSF showed that no PCF is registered for the MBS session ID, the NEF / MBSF checks PCF candidates by interacting with the NRF and selects a PCF, possibly based on the MBS service area.

[00358] 14. NEF / MBSF sends a request Npcf_MBSPolicy_Authorization_Create (MBS session ID, [ID of Petition 870250090277, dated 10 / 03 / 2025, page 268 / 362 / 147 [linking of area session policy], MBS Service Information (as defined in clause 6.14 of TS 23.247 V18.1.0 3GPP)) to PCF.

[00359] The area session binding ID can be assigned by NEF / MBSF for location-dependent MBS service.

[00360] NOTE X: In deployments without NEF and MBSF, it is the AF that assigns the area session policy binding ID to the location-dependent MBS service.

[00361] 15. [Optional] The PCF may retrieve authorization information for the UDR MBS session (see clause 6.10.2 of TS 23.247 V18.1.0 3GPP) and take it into account for subsequent authorization and QoS permission verification.

[00362] NOTE 3: This step is not required in a deployment with a single PCF if the authorization data is stored in the PCF.

[00363] 16. The PCF determines whether the request is authorized and, if authorized, the PCF derives the necessary QoS parameters based on the received MBS service information and determines whether this QoS is permitted. If the required QoS is permitted, the PCF generates the policy information for the MBS session (as defined in clause 6.10 of TS 23.247 V18.1.0 3GPP) and stores it along with the MBS session ID and the area session policy binding ID.

[00364] 17. If the request is authorized and the necessary QoS is enabled, the PCF registers with the BSF that it handles the MBS session using the Nbsf_management_Register request (MBS session ID, PCF ID). It provides an identifier indicating that the policy association is for MBS and the MBS session ID, its own PCF ID, and optionally its PCF pool ID.

[00365] NOTE 4: This step is not required in a deployment with a single PCF. Petition 870250090277, dated 03 / 10 / 2025, pp. 269 / 362 / 147

[00366] 18. PCF sends a reply Npcf_MBSPolicy_Authorization_Create (Result indication) for NEF / MBSF.

[00367] If the request is not authorized or the required QoS is not permitted, the PCF indicates this in the response to the NEF / MBSF, which in turn informs the AF about this (by sending the Nnef_MBSSession_Create response) and terminates this procedure.

[00368] 19. Same as step 10 in Figure 7.1.1.2-1 of TS 23.247 V18.1.0 3GPP below.

[00369] The NEF / MBSF verifies MB-SMF candidates and selects the MB-SMF as the inbound control node, possibly based on the MBS service area. If a TMGI is included in step 8, the NEF / MBSF finds the MB-SMF based on that TMGI.

[00370] 20. Same as step 11 in Figure 7.1.1.2-1 of TS 23.247 V18.1.0 3GPP with the following differences: - MBS Service Information is not present if the optional interaction between AF / NEF / MBSF and PCF has been performed (as MBS Service Information was provided to PCF in step 14).

[00371] - For location-dependent MBS service, the area session policy binding ID is sent by AF / NEF / MBSF to MBSMF in the Nmbsmf_MBSSession_Create request.

[00372] Step 11 in Figure 7.1.1.2-1 of TS 23.247 V18.1.0 3GPP is as follows.

[00373] The NEF / MBSF sends the request Nmbsmf_MBSSession_Create ([MBS session ID], MBS service type, [TMGI allocation request], MBS service information (as defined in clause 6.14), [MBS service area], [indication of any UE], [MBS session start and end time], [MBS session status], [indication of transport address request Petition 870250090277, dated 10 / 03 / 2025, page 270 / 362 / 147 entry], [FSA ID(s), [multicast session security context]) to MB-SMF, to request that MB-SMF reserve ingress resources for an MBS distribution session. The NEF / MBSF forwards all parameters it received from AF in step 8. If MBSF decides to insert an MBSTF into the user plane for the MBS session, it also indicates that the allocation of an ingress transport address is requested, even if this was not requested in step 8. The request also includes the indication Any UE, if provided in step 8. If MBSF acts as the MBS security function for multicast, as defined in TS 33.501

[20] , it provides a multicast session security context for the MBS session.

[00374] If requested or if a source-specific multicast is provided as the MBS session ID in step 11, MB-SMF allocates a TMGI.

[00375] For broadcast communication, if no MBS FSA ID has been received, MB-SMF selects the MBS FSA ID(s) for the broadcast MBS session based on the local configuration.

[00376] 21. The MB-SMF checks the PCF using NRF.

[00377] 22. MB-SMF sends a request Npcf_MBSPolicyControl_Create (MBS session ID, [Area session policy ID], [MBS service information (as defined in clause 6.14)]) for the MBS session to the PCF. The MB-SMF forwards the MBS service information to the PCF if received from the NEF / MBSF in the previous step 20.

[00378] For location-dependent MBS service, MB-SMF also sends the area session policy ID to PCF as follows: -If the AF / NEF / MBSF has not interacted with the PCF, the MBSMF uses the area session ID as the area session policy ID.

[00379] -If the AF / NEF / MBSF has interacted with the PCF, the MB-SMF Petition 870250090277, dated 10 / 03 / 2025, page 271 / 362 / 147 uses the Area Session Policy Binding ID (received from AF / NEF / MBSF) as the Area Session Policy ID.

[00380] If the PCF receives MBS service information from MBSMF, the PCF performs subsequent steps 23 to 26. If the PCF does not receive MBS service information from MB-SMF, but has previously determined policy information for the MBS session (see step 16) corresponding to the MBS session ID (and location-dependent MBS area session policy ID) received from MB-SMF, the PCF continues with step 27.

[00381] 23. If the PCF is not handling the MBS session ID, the PCF uses the BSF Registration service to check if there is already a PCF serving the MBS session. In this case, the PCF skips steps 24 to 26 and indicates in step 27 that the PCF serving the MBS session should be put in contact.

[00382] NOTE 5: This step is not required in a deployment with a single PCF.

[00383] 24. [Optional] PCF may retrieve authorization information for the UDR MBS session (see clause 6.10.2 of TS 23.247 V18.1.0 3GPP) and take it into account for subsequent authorization and QoS permission verification.

[00384] NOTE 6: This step is not necessary if the authorization data is stored in the PCF.

[00385] 25. The PCF determines whether the request is authorized and, if authorized, the PCF derives the necessary QoS parameters based on the received MBS service information and determines whether this QoS is permitted. If the required QoS is permitted, the PCF generates the policy information for the MBS session (as defined in clause 6.10) and stores it along with the MBS session ID.

[00386] 26. If the request is authorized and the required QoS is Petition 870250090277, dated 10 / 03 / 2025, page 272 / 362 / 147, allowed, the PCF registers in the BSF that it handles the MBS session using the Nbsf_management_Register request (MBS session ID, PCF ID). It provides an identifier that the policy association is for MBS and the MBS session ID, its own PCF ID, and optionally its PCF pool ID.

[00387] NOTE 7: This step is not required in a deployment with a single PCF.

[00388] 27. PCF responds with the answer Npcf_MBSPolicyControl_Create ([policy information for the MBS session (as defined in clause 6.10 of TS 23.247 V18.1.0 3GPP)], result indication).

[00389] If the request is not authorized or the required QoS is not permitted, the PCF indicates this in its response to MB-SMF, which in turn informs the AF about this (by sending the Nmbsmf_MBSSession_Create response) and terminates this procedure.

[00390] If another PCF is handling the MBS session, the PCF indicates that another PCF handling the MBS session should be put in contact and provides an ID of that other PCF. The MB-SMF then repeats step 22 towards the other PCF.

[00391] 28-37: Same as steps 14-22 in Figure 7.1.1.2-1 of TS 23.247 V18.1.0 3GPP, with the following difference: In step 30, MB-SMF includes the Area Session Policy Binding ID in the Nmbsmf_MBSSession_Create response, if the Area Session Policy Binding ID was received in step 20.

[00392] NOTE 7a: If AF / NEF / MBSF has the mechanism to associate the Area Session ID and the Area Session Policy Binding ID when receiving the Nmbsmf_MBSSession_Create response, there is no need to send back the Area Session Policy Binding ID in the response, even if the Area Session Policy Binding ID has been Petition 870250090277, dated 03 / 10 / 2025, page 273 / 362 / 147 received in stage 20.

[00393] NOTE 8: Steps 33 to 36 can be performed in parallel with step 32.

[00394] Steps 14 to 22 in Figure 7.1.1.2-1 of TS 23.247 V18.1.0 3GPP are as follows.

[00395] 14. MB-SMF selects MB-UPF. If allocation of an inbound transport address was requested in step 11, MB-SMF requests MB-UPF to reserve user plane inbound resources. If multicast transport of MBS data towards RAN nodes is used, MB-SMF will also request MB-UPF to reserve a tunnel endpoint and related identifiers (source IP address, SSM, and GTP tunnel ID) for outbound data and forward the received data on the user plane inbound resource using that tunnel endpoint.

[00396] If the allocation of an inbound transport address was not requested in step 11, MB-SMF provides the received SSM as the MBS session ID to MB-UPF and requests that MB-UPF join the corresponding multicast tree of the content provider. MB-SMF may also postpone the configuration to join the corresponding multicast tree, for example, based on information that the session is inactive, service requirements, and MBS start / end time, until it receives the first query for the MBS session as part of the establishment procedure in clause 7.2.1.3 or until it receives a request to activate the MBS session through the MBS session update procedure in clause 7.1.1.6.

[00397] 15. If requested, MB-UPF selects an incoming address (IP address and port) and a tunnel endpoint for outgoing data and provides them to MB-SMF.

[00398] 16. MB-SMF indicates the possibly incoming address Petition 870250090277, dated 10 / 03 / 2025, page 274 / 362 / 147 allocated to NEF / MBSF. MB-SMF may include TMGI if allocated in step 11. For broadcast communication, MB-SMF includes any selected MBS FSA ID(s) in step 11. It also indicates the success or failure of the transmission resource reservation.

[00399] 16a. If a source-specific multicast address is provided as the MBS session ID in step 11, MB-SMF updates its NF profile in the NRF with the server MBS session ID. If an MBS service area was received in step 11, MB-SMF updates its NF profile in the NRF with that information.

[00400] NOTE 3: If the TMGI is used to represent an MBS session, the MB-SMF will not need to update the NRF if the TMGI interval(s) supported by an MB-SMF are already included in the MB-SMF profile when the MB-SMF registers with the NRF.

[00401] 17. For broadcast communication, MB-SMF continues the procedure towards AMF and NG-RAN as specified in clause 7.3.1 to request the allocation of resources for the transmission of the broadcast session.

[00402] 18. [Optional] If MBSF decides to use an MBSTF, the NEF / MBSF provides the ingress address received in step 16 to MBSTF as the DL destination. If allocation of an ingress transport address was requested in step 8, MBSF requests MBSTF to allocate the user plane ingress resources. If allocation of an ingress transport address was not requested in step 8, MBSF provides the received SSM as the multicast session ID in step 8 and requests MBSTF to join the corresponding multicast tree of the content provider.

[00403] 19. [Conditional in step 19] If requested, MBSTF selects an incoming address (IP address and port) and provides it to NEF / MBSF. Petition 870250090277, dated 03 / 10 / 2025, pp. 275 / 362 / 147

[00404] 20. The NEF / MBSF-C indicates the possibly allocated inbound address and other parameters (e.g., TMGI) to the AF via a response Nnef MBSSession Create ([TMGI], [Allocated Inbound Address])). If the MBS session ID is not provided in step 8 or if the MBS session ID is SSM, the NEF / MBSF will provide the allocated TMGI. If the AF requested the allocation of an inbound transport address, the message would also include the allocated inbound address. For broadcast communication, the message also includes any MBS FSA ID(s) received in step 17.

[00405] 21. Same as step 7. AF can also make a service announcement at this stage.

[00406] 22. For multicast communication, depending on the configuration, UEs can join the MBS session as specified in clause 7.2.1.

[00407] Option 2: The area session policy binding ID is assigned by the PCF.

[00408] When the AF / NEF / MBSF decides to interact with the PCF and the PCF receives the Npcf_MBSPolicyAuthorization_Create from the AF / NEF / MBSF: - PCF can assign a unique Area Session Policy Binding ID to this MBS service area based on the MBS service area in the request. - PCF can pass the Area Session Policy Binding ID via response to AF / NEF / MBSF.

[00409] AF / NEF / MBSF can invoke Nmbsmf_MBSSession_Create using the Area Session Policy Binding ID as the Area Session Policy ID.

[00410] MB-SMF can send the area session policy ID to PCF so that PCF can retrieve the previously authorized policy when AF / NEF / MBSF interacted with PCF. Petition 870250090277, dated 03 / 10 / 2025, pp. 276 / 362 / 147

[00411] MB-SMF can include the area session policy binding ID in the Nmbsmf_MBSSession_Create response.

[00412] Figure 6 shows a flowchart for creating an MBS session with PCC according to another modality of the present description.

[00413] Steps 1 through 7 are optional and only applicable if TMGI is used as the MBS session ID and needs to be pre-allocated.

[00414] 1 to 9: Same as Figure 7.1.1.2-1 of TS 23.247 V18.1.0 3GPP.

[00415] 10. The NEF / MBSF may optionally, based on the local configuration, decide to interact with the PCF.

[00416] NOTE 1: In deployments without NEF and MBSF, AF optionally interacts with PCF in steps 11 to 18.

[00417] If NEF / MBSF decides to interact with PCF, steps 11 to 19 are performed and, in step 20, MBS Service Information is not provided to MB-SMF.

[00418] If NEF / MBSF decides not to interact with PCF, steps 12 to 19 will be skipped and, in step 20, MBS service information will be provided to MB-SMF.

[00419] 11. [Conditional] If the NEF / MBSF did not receive an MBS session ID from the AF in step 8, the NEF / MBSF sends an Nmbsmf_TMGI_Allocate request message to the MB-SMF and the MB-SMF allocates a TMGI and returns the TMGI to the NEF / MBSF via the Nmbsmf_TMGI_Allocate response (TMGI, expiration time).

[00420] 12. [Conditional] If the NEF / MBSF receives the location-dependent session request from the AF and there is a need to select the same PCF for location-dependent MBS sessions, the NEF / MBSF will first use the BSF Discovery service to check if there is a PCF serving the MBS session with the MBS session ID using the Nbsf_management_Discovery operation. If there is a registered PCF for the MBS session ID, the NEF / MBSF interacts with that PCF and skips the step. Petition 870250090277, dated 03 / 10 / 2025, page 277 / 362 / 147 following.

[00421] NOTE 2: This step is not required in a deployment with a single PCF.

[00422] 13. [Conditional] If step 12 was not executed or interaction with the BSF showed that no PCF is registered for the MBS session ID, the NEF / MBSF checks PCF candidates by interacting with the NRF and selects a PCF, possibly based on the MBS service area.

[00423] 14. NEF / MBSF sends a request Npcf_MBSPolicy_Authorization_Create (MBS Session ID, MBS Service Information (as defined in clause 6.14 of TS 23.247 V18.1.0 3GPP), [MBS Service Area for a Location-Dependent MBS Service]) for the PCF.

[00424] 15. [Optional] PCF may retrieve authorization information for the UDR MBS session (see clause 6.10.2 of TS 23.247 V18.1.0 3GPP) and take it into account for subsequent authorization and QoS permission verification.

[00425] NOTE 3: This step is not required in a deployment with a single PCF if the authorization data is stored in the PCF.

[00426] 16. The PCF determines whether the request is authorized and, if authorized, the PCF derives the necessary QoS parameters based on the received MBS service information and determines whether this QoS is permitted. If the required QoS is permitted, the PCF generates the policy information for the MBS session (as defined in clause 6.10 of TS 23.247 V18.1.0 3GPP) and stores it along with the MBS session ID and the area session policy binding ID assigned by the PCF below.

[00427] 17. If the request is authorized and the necessary QoS is enabled, the PCF registers with the BSF that it handles the MBS session using the Petition 870250090277, dated 10 / 03 / 2025, page 278 / 362 / 147 requesting Nbsf_management_Register (MBS session ID, PCF ID). It provides an identifier indicating that the policy association is for MBS and the MBS session ID, its own PCF ID, and optionally its PCF pool ID.

[00428] NOTE 4: This step is not required in a deployment with a single PCF.

[00429] 18. The PCF may assign the Area Session Policy Binding ID based on the received MBS session area for the location-dependent MBS service and send an Npcf_MBSPolicy_Authorization_Create response (result indication, [Area Session Policy Binding ID]) to the NEF / MBSF.

[00430] The Area Session Policy Binding ID can be assigned by PCF for the location-dependent MBS service.

[00431] If the request is not authorized or the required QoS is not permitted, the PCF indicates this in the response to the NEF / MBSF, which in turn informs the AF about this (by sending the Nnef_MBSSession_Create response) and terminates this procedure.

[00432] 19. Same as step 10 in Figure 7.1.1.2-1 of TS 23.247 V18.1.0 3GPP.

[00433] 20. Same as step 11 in Figure 7.1.1.2-1 of TS 23.247 V18.1.0 3GPP with the following differences: - MBS Service Information is not present if the optional interaction between AF / NEF / MBSF and PCF has been performed (as MBS Service Information was provided to PCF in step 14).

[00434] - for location-dependent MBS service and AF / NEF / MBSF that interacted with PCF, the Area Session Policy Binding ID is sent by NEF / MBSF to MB-SMF. Otherwise, no Area Session Policy Binding ID is provided.

[00435] 21. The MB-SMF checks the PCF using NRF. Petition 870250090277, dated 03 / 10 / 2025, pp. 279 / 362 / 147

[00436] 22. MB-SMF sends a request Npcf_MBSPolicyControl_Create (MBS session ID, [Area session policy ID], [MBS service information (as defined in clause 6.14)]) for the MBS session to the PCF. The MB-SMF forwards the MBS service information to the PCF if received from the NEF / MBSF in the previous step 20.

[00437] For location-dependent MBS service, MB-SMF also sends the area session policy ID to PCF as follows: - If the AF / NEF / MBSF has not interacted with the PCF, the MBSMF uses the area session ID as the area session policy ID.

[00438] -If AF / NEF / MBSF has interacted with PCF, MB-SMF uses the area session policy binding ID (received from AF / NEF / MBSF) as the area session policy ID.

[00439] If the PCF receives MBS service information from MBSMF, the PCF performs subsequent steps 23 to 26. If the PCF does not receive MBS service information from MB-SMF, but has previously determined policy information for the MBS session (see step 16) corresponding to the MBS session ID (and location-dependent MBS area session policy ID) received from MB-SMF, the PCF continues with step 27.

[00440] 23. If the PCF is not handling the MBS session ID, the PCF uses the BSF Registration service to check if there is already a PCF serving the MBS session. In this case, the PCF skips steps 24 to 26 and indicates in step 27 that the PCF serving the MBS session should be put in contact.

[00441] NOTE 5: This step is not required in a deployment with a single PCF.

[00442] 24. [Optional] PCF may retrieve authorization information for the MBS session from the UDR (see clause 6.10.2 of the TS). Petition 870250090277, dated 03 / 10 / 2025, pp. 280 / 362 / 147 23.247 V18.1.0 3GPP) and take them into account for subsequent authorization and QoS permission verification.

[00443] NOTE 6: This step is not necessary if the authorization data is stored in the PCF.

[00444] 25. The PCF determines whether the request is authorized and, if authorized, the PCF derives the necessary QoS parameters based on the received MBS service information and determines whether this QoS is permitted. If the required QoS is permitted, the PCF generates the policy information for the MBS session (as defined in clause 6.10 of TS 23.247 V18.1.0 3GPP) and stores it along with the MBS session ID.

[00445] 26. If the request is authorized and the necessary QoS is allowed, the PCF registers with the BSF that it handles the MBS session using the Nbsf_management_Register request (MBS session ID, PCF ID). It provides an identifier indicating that the policy association is for MBS and the MBS session ID, its own PCF ID, and optionally its PCF pool ID.

[00446] NOTE 7: This step is not required in a deployment with a single PCF.

[00447] 27. PCF responds with the answer Npcf_MBSPolicyControl_Create ([policy information for the MBS session (as defined in clause 6.10 of TS 23.247 V18.1.0 3GPP)], result indication).

[00448] If the request is not authorized or the required QoS is not permitted, the PCF indicates this in its response to MB-SMF, which in turn informs the AF about this (by sending the Nmbsmf_MBSSession_Create response) and terminates this procedure.

[00449] If another PCF is handling the MBS session, the PCF indicates that another PCF handling the MBS session should be put in contact and provides an ID of that other PCF. The MB-SMF then repeats step 22. Petition 870250090277, dated 03 / 10 / 2025, pages 281 / 362 / 147 directed to another PCF.

[00450] 28-37: Same as steps 14-22 in Figure 7.1.1.2-1 of TS 23.247 V18.1.0 3GPP, with the following difference:

[00451] In step 30, MB-SMF includes the Area Session Policy Binding ID in the Nmbsmf_MBSSession_Create response, if the Area Session Policy Binding ID was received in step 20.

[00452] NOTE 7a: If AF / NEF / MBSF has the mechanism to associate the Area Session ID and the Area Session Policy Binding ID when receiving the Nmbsmf_MBSSession_Create response, there is no need to send back the Area Session Policy Binding ID in the response, even if the Area Session Policy Binding ID was received in step 20.

[00453] NOTE 8: Steps 33 to 36 can be performed in parallel with step 32.

[00454] Alternative 2: MBS Service Area

[00455] For a location-dependent service, the AF can send the MBS Service Area to the NEF / MBSF, along with the MBS session ID. This information is a unique identifier to differentiate location-based services with the same MBS session ID. This information can be used directly by the Npcf_MBSPolicyAuthrization_Create request and the Npcf_MBSPolicyControl_Create request to avoid the failure cases described above.

[00456] Figure 7A shows a flowchart for creating an MBS session with PCC according to another modality of the present description.

[00457] Steps 1 through 7 are optional and only applicable if TMGI is used as the MBS session ID and needs to be pre-allocated.

[00458] 1 to 9: Same as Figure 7.1.1.2-1 of TS 23.247 V18.1.0 3GPP.

[00459] 10. The NEF / MBSF may, optionally, based on Petition 870250090277, dated 03 / 10 / 2025, page 282 / 362 / 147 local configuration, decide to interact with the PCF.

[00460] NOTE 1: In deployments without NEF and MBSF, AF optionally interacts with PCF in steps 11 to 18.

[00461] If the NEF / MBSF decides to interact with the PCF, steps 11 to 19 are performed and, in step 20, MBS Service Information is not provided to MB-SMF.

[00462] If NEF / MBSF decides not to interact with PCF, steps 12 to 19 will be skipped and, in step 20, MBS service information will be provided to MB-SMF.

[00463] 11. [Conditional] If the NEF / MBSF did not receive an MBS session ID from the AF in step 8, the NEF / MBSF sends an Nmbsmf_TMGI_Allocate request message to the MB-SMF and the MB-SMF allocates a TMGI and returns the TMGI to the NEF / MBSF via the Nmbsmf_TMGI_Allocate response (TMGI, expiration time).

[00464] 12. [Conditional] If the NEF / MBSF receives the location-dependent session request from the AF and there is a need to select the same PCF for location-dependent MBS sessions, the NEF / MBSF will first use the BSF Discovery service to check if there is a PCF serving the MBS session with the MBS session ID using the Nbsf_management_Discovery operation. If there is a registered PCF for the MBS session ID, the NEF / MBSF interacts with that PCF and skips the following step 13.

[00465] NOTE 2: This step is not required in a deployment with a single PCF.

[00466] 13. [Conditional] If step 12 was not executed or interaction with the BSF showed that no PCF is registered for the MBS session ID, the NEF / MBSF checks PCF candidates by interacting with the NRF and selects a PCF, possibly based on the MBS service area. Petition 870250090277, dated 03 / 10 / 2025, pp. 283 / 362 / 147

[00467] 14. NEF / MBSF sends a request Npcf_MBSPolicy_Authorization_Create (MBS Session ID, MBS Service Information (as defined in clause 6.14 of TS 23.247 V18.1.0 3GPP), [MBS Service Area for a Location-Dependent MBS Service]) for the PCF.

[00468] 15. [Optional] The PCF may retrieve authorization information for the UDR MBS session (see clause 6.10.2 of TS 23.247 V18.1.0 3GPP) and take it into account for subsequent authorization and QoS permission verification.

[00469] NOTE 3: This step is not required in a deployment with a single PCF if the authorization data is stored in the PCF.

[00470] 16. The PCF determines whether the request is authorized and, if authorized, the PCF derives the necessary QoS parameters based on the received MBS service information and determines whether this QoS is permitted. If the required QoS is permitted, the PCF generates the policy information for the MBS session (as defined in clause 6.10) and stores it along with the MBS session ID and the MBS Service Area.

[00471] 17. If the request is authorized and the necessary QoS is enabled, the PCF registers with the BSF that it handles the MBS session using the Nbsf_management_Register request (MBS session ID, PCF ID). It provides an identifier indicating that the policy association is for MBS and the MBS session ID, its own PCF ID, and optionally its PCF pool ID.

[00472] NOTE 4: This step is not required in a deployment with a single PCF.

[00473] 18. PCF sends a reply Npcf_MBSPolicy_Authorization_Create (Result indication) for NEF / MBSF. Petition 870250090277, dated 03 / 10 / 2025, pp. 284 / 362 / 147

[00474] If the request is not authorized or the required QoS is not permitted, the PCF indicates this in the response to the NEF / MBSF, which in turn informs the AF about this (by sending the Nnef_MBSSession_Create response) and terminates this procedure.

[00475] 19. Same as step 10 in Figure 7.1.1.2-1 of TS 23.247 V18.1.0 3GPP.

[00476] 20. Same as step 11 in Figure 7.1.1.2-1 of TS 23.247 V18.1.0 3GPP with the following differences: - MBS Service Information is not present if the optional interaction between AF / NEF / MBSF and PCF has been performed (as MBS Service Information was provided to PCF in step 14).

[00477] - for location-dependent MBS service, the Area of The MBS service must be included in the Create request.

[00478] 21. The MB-SMF checks the PCF using NRF.

[00479] 22. MB-SMF sends a request Npcf_MBSPolicyControl_Create (MBS session ID, [MBS Service Information (as defined in clause 6.14 of TS 23.247 V18.1.0 3GPP)], [MBS Service Area]) for the MBS session to the PCF. The MB-SMF forwards the MBS service information to the PCF if received from the NEF / MBSF in the previous step 20.

[00480] For location-dependent MBS service, MB-SMF also sends the MBS Service Area to PCF.

[00481] If the PCF receives MBS service information from MBSMF, the PCF performs subsequent steps 23 to 26. If the PCF does not receive MBS service information from MB-SMF, but has previously determined policy information for the MBS session (see step 16) corresponding to the MBS session ID (and MBS service area for a location-dependent MBS) received from MB-SMF, the PCF continues with step 27. Petition 870250090277, dated 03 / 10 / 2025, pp. 285 / 362 / 147

[00482] 23. If the PCF is not handling the MBS session ID, the PCF uses the BSF Registration service to check if there is already a PCF serving the MBS session. In this case, the PCF skips steps 24 to 26 and indicates in step 27 that the PCF serving the MBS session should be put in contact.

[00483] NOTE 5: This step is not required in a deployment with a single PCF.

[00484] 24. [Optional] The PCF may retrieve authorization information for the UDR MBS session (see clause 6.10.2 of TS 23.247 V18.1.0 3GPP) and take it into account for subsequent authorization and QoS permission verification.

[00485] NOTE 6: This step is not necessary if the authorization data is stored in the PCF.

[00486] 25. The PCF determines whether the request is authorized and, if authorized, the PCF derives the necessary QoS parameters based on the received MBS service information and determines whether this QoS is permitted. If the required QoS is permitted, the PCF generates the policy information for the MBS session (as defined in clause 6.10 of TS 23.247 V18.1.0 3GPP) and stores it along with the MBS session ID.

[00487] 26. If the request is authorized and the necessary QoS is allowed, the PCF registers with the BSF that it handles the MBS session using the Nbsf_management_Register request (MBS session ID, PCF ID). It provides an identifier indicating that the policy association is for MBS and the MBS session ID, its own PCF ID, and optionally its PCF pool ID.

[00488] NOTE 7: This step is not required in a deployment with a single PCF.

[00489] 27. PCF responds with the answer Npcf_MBSPolicyControl_Create ([policy information for the session of Petition 870250090277, dated 03 / 10 / 2025, pp. 286 / 362 / 147 MBS (as defined in clause 6.10 of TS 23.247 V18.1.0 3GPP)], indication of result).

[00490] If the request is not authorized or the required QoS is not permitted, the PCF indicates this in its response to MB-SMF, which in turn informs the AF about this (by sending the Nmbsmf_MBSSession_Create response) and terminates this procedure.

[00491] If another PCF is handling the MBS session, the PCF indicates that another PCF handling the MBS session should be put in contact and provides an ID of that other PCF. The MB-SMF then repeats step 22 towards the other PCF.

[00492] 28-37: Same as steps 14 to 22 in Figure 7.1.1.2-1 of the TS 23.247 V18.1.0 3GPP.

[00493] NOTE 8: Steps 33 to 36 can be performed in parallel with step 32.

[00494] Alternative 3: Use a unique identifier, linking ID

[00495] For each service area of ​​a location-dependent MBS service, the AF / NEF / MBSF can tag it with a unique identifier, for example, an AF ID plus a unique character string or a timestamp plus a unique character string. The identifier can then be used later by Npcf_MBSPolicyAuthorization_Create requests and Npcf_MBSPolicyControl_Create to avoid the failure cases that were discussed. For simplicity, the term "binding ID" was used as a unique identifier in the following discussion.

[00496] Figure 7B shows a flowchart for creating an MBS session with PCC according to another modality of the present description.

[00497] Steps 1 through 7 are optional and only applicable if TMGI is used as the MBS session ID and needs to be pre-allocated. Petition 870250090277, dated 03 / 10 / 2025, pp. 287 / 362 / 147

[00498] 1 to 9: Same as Figure 7.1.1.2-1 of TS 23.247 V18.1.0 3GPP.

[00499] 9a. For a location-dependent MBS service, a NEF / MBSF assigns a binding ID based on the received MBS session ID and MBS Service Area to uniquely identify the session. The binding ID can be a unique sequence that begins with AF ID or Timestamp.

[00500] 10. The NEF / MBSF may optionally, based on the local configuration, decide to interact with the PCF.

[00501] NOTE 1: In deployments without NEF and MBSF, AF optionally interacts with PCF in steps 11 to 18.

[00502] If NEF / MBSF decides to interact with PCF, steps 11 to 19 are performed and, in step 20, MBS Service Information is not provided to MB-SMF.

[00503] If NEF / MBSF decides not to interact with PCF, steps 12 to 19 will be skipped and, in step 20, MBS service information will be provided to MB-SMF.

[00504] 11. [Conditional] If the NEF / MBSF did not receive an MBS session ID from the AF in step 8, the NEF / MBSF sends an Nmbsmf_TMGI_Allocate (1) request message to the MB-SMF and the MB-SMF allocates a TMGI and returns the TMGI to the NEF / MBSF via the Nmbsmf_TMGI_Allocate (TMGI, expiration time) response.

[00505] 12. [Conditional] If the NEF / MBSF receives the location-dependent session request from the AF and there is a need to select the same PCF for location-dependent MBS sessions, the NEF / MBSF will first use the BSF Discovery service to check if there is a PCF serving the MBS session with the MBS session ID using the Nbsf_management_Discovery operation. If there is a registered PCF for the MBS session ID, the NEF / MBSF interacts with that PCF and skips the following step 13. Petition 870250090277, dated 03 / 10 / 2025, pp. 288 / 362 / 147

[00506] NOTE 2: This step is not required in a deployment with a single PCF.

[00507] 13. [Conditional] If step 12 was not executed or interaction with the BSF showed that no PCF is registered for the MBS session ID, the NEF / MBSF checks PCF candidates by interacting with the NRF and selects a PCF, possibly based on the MBS service area.

[00508] 14. NEF / MBSF sends a request Npcf_MBSPolicy_Authorization_Create (MBS session ID, MBS Service Information (as defined in clause 6.14 of TS 23.247 V18.1.0 3GPP), [Binding ID for a location-dependent MBS service]) for the PCF.

[00509] 15. [Optional] PCF may retrieve authorization information for the UDR MBS session (see clause 6.10.2 of TS 23.247 V18.1.0 3GPP) and take it into account for subsequent authorization and QoS permission verification.

[00510] NOTE 3: This step is not required in a deployment with a single PCF if the authorization data is stored in the PCF.

[00511] 16. The PCF determines whether the request is authorized and, if authorized, the PCF derives the necessary QoS parameters based on the received MBS service information and determines whether this QoS is allowed. If the required QoS is allowed, the PCF generates the policy information for the MBS session (as defined in clause 6.10 of TS 23.247 V18.1.0 3GPP) and stores it along with the MBS session ID and the binding ID.

[00512] 17. If the request is authorized and the necessary QoS is allowed, the PCF registers with the BSF that it handles the MBS session using the Nbsf_management_Register request (MBS session ID, PCF ID). Petition 870250090277, dated 03 / 10 / 2025, pp. 289 / 362 / 147 It provides an identifier indicating that the policy association is for MBS and the MBS session ID, its own PCF ID, and optionally, its PCF pool ID.

[00513] NOTE 4: This step is not required in a deployment with a single PCF.

[00514] 18. PCF sends a reply Npcf_MBSPolicy_Authorization_Create (Result indication) for NEF / MBSF.

[00515] If the request is not authorized or the required QoS is not permitted, the PCF indicates this in the response to the NEF / MBSF, which in turn informs the AF about this (by sending the Nnef_MBSSession_Create response) and terminates this procedure.

[00516] 19. Same as step 10 in Figure 7.1.1.2-1 of TS 23.247 V18.1.0 3GPP.

[00517] 20. Same as step 11 in Figure 7.1.1.2-1 of TS 23.247 V18.1.0 3GPP with the following differences: - MBS Service Information is not present if the optional interaction between AF / NEF / MBSF and PCF has been performed (as MBS Service Information was provided to PCF in step 14).

[00518] - For location-dependent MBS service, the binding ID must be included in the Create request.

[00519] 21. The MB-SMF checks the PCF using NRF.

[00520] 22. MB-SMF sends a request Npcf_MBSPolicyControl_Create (MBS session ID, [MBS Service Information (as defined in clause 6.14 of TS 23.247 V18.1.0 3GPP)], [Binding ID]) for the MBS session to PCF. MB-SMF forwards MBS service information to PCF if received from NEF / MBSF in the previous step 20.

[00521] For location-dependent MBS service, MB-SMF Petition 870250090277, dated 10 / 03 / 2025, pages 290 / 362 / 147, also sends the linking ID to the PCF.

[00522] If the PCF receives MBS service information from MBSMF, the PCF performs subsequent steps 23 to 26. If the PCF does not receive MBS service information from MB-SMF, but has previously determined policy information for the MBS session (see step 16) corresponding to the MBS session ID (and location-dependent MBS service binding ID) received from MB-SMF, the PCF continues with step 27.

[00523] 23. If the PCF is not handling the MBS session ID, the PCF uses the BSF Registration service to check if there is already a PCF serving the MBS session. In this case, the PCF skips steps 24 to 26 and indicates in step 27 that the PCF serving the MBS session should be put in contact.

[00524] NOTE 5: This step is not required in a deployment with a single PCF.

[00525] 24. [Optional] PCF may retrieve authorization information for the UDR MBS session (see clause 6.10.2 of TS 23.247 V18.1.0 3GPP) and take it into account for subsequent authorization and QoS permission verification.

[00526] NOTE 6: This step is not necessary if the authorization data is stored in the PCF.

[00527] 25. The PCF determines whether the request is authorized and, if authorized, the PCF derives the necessary QoS parameters based on the received MBS service information and determines whether this QoS is permitted. If the required QoS is permitted, the PCF generates the policy information for the MBS session (as defined in clause 6.10) and stores it along with the MBS session ID.

[00528] 26. If the request is authorized and the necessary QoS is enabled, the PCF registers with the BSF that it handles the MBS session using the Petition 870250090277, dated 10 / 03 / 2025, page 291 / 362 / 147 request Nbsf_management_Register (MBS session ID, PCF ID). It provides an identifier indicating that the policy association is for MBS and the MBS session ID, its own PCF ID, and optionally its PCF pool ID.

[00529] NOTE 7: This step is not required in a deployment with a single PCF.

[00530] 27. PCF responds with the answer Npcf_MBSPolicyControl_Create ([policy information for the MBS session (as defined in clause 6.10 of TS 23.247 V18.1.0 3GPP)], result indication).

[00531] If the request is not authorized or the required QoS is not permitted, the PCF indicates this in its response to MB-SMF, which in turn informs the AF about this (by sending the Nmbsmf_MBSSession_Create response) and terminates this procedure.

[00532] If another PCF is handling the MBS session, the PCF indicates that another PCF handling the MBS session should be put in contact and provides an ID of that other PCF. The MB-SMF then repeats step 22 towards the other PCF.

[00533] 28-37: Same as steps 14 to 22 in Figure 7.1.1.2-1 of the TS 23.247 V18.1.0 3GPP.

[00534] In step 30, MB-SMF includes the binding ID in the Nmbsmf_MBSSession_Create response for the location-dependent MBS service.

[00535] NOTE 7a: If AF / NEF / MBSF has the mechanism to associate the area session ID and the binding ID when receiving the Nmbsmf_MBSSession_Create response, there is no need to send back the binding ID in the response for a location-dependent MBS service.

[00536] NOTE 8: Steps 33 to 36 can be performed in parallel with step 32. Petition 870250090277, dated 03 / 10 / 2025, pp. 292 / 362 / 147

[00537] Some messages in Figures 5 to 6, 7A and 7B may be the same as the corresponding messages described in TS 23.247 V18.1.0 3GPP. Some messages in Figures 5 to 6, 7A and 7B are altered according to some embodiments of the present description.

[00538] In one embodiment, clause 6.10 of TS 23.247 V18. 1.0 3GPP may be amended as follows.

[00539] 6.10 Policy control for multicast and broadcast services

[00540] 6.10.1 General

[00541] The policy and control structure for charges as defined in TS 23.503 [7] applies to multicast and broadcast services in the following respects: - MBS Session Binding: MBS session binding is the association of AF Session information to one and only one MBS session. The PCF must perform session binding based on the MBS session ID, i.e., the TMGI or source-specific IP multicast address. For location-dependent MBS sessions, the area session policy ID is used along with the MBS session ID to associate AF Session information with the location-dependent MBS session in a specific MBS service area.

[00542] - QoS Flow Binding: For an MBS session, QoS flow binding is the association of a PCC rule with a QoS flow within an MBS session. MB-SMF performs QoS flow binding for an MBS session in the same way that SMF does for a PDU session.

[00543] - Information regarding MBS policy consists of: - The PCC rules for the MBS session are used to provide policies for QoS flows: The following PCC rule parameters defined in Table 6.3.1 of TS 23.503 [7] are applicable to MBS: Petition 870250090277, dated 03 / 10 / 2025, pp. 293 / 362 / 147 Rule identifier.

[00544] - Service data flow detection: Precedence, service data flow model (for IP PDU traffic only).

[00545] - Policy control: 5G QoS identifier (5QI), DL maximum bit rate, DL guaranteed bit rate, ARP, priority level, averaging window, maximum data burst volume.

[00546] - Policy information may also apply to an entire MBS session. The following parameters defined for a PDU Session in Table 6.4.1 of TS 23.503 [7] apply to an entire MBS session:

[00547] - Session Authorized-AMBR.

[00548] - QoS characteristics explicitly signaled.

[00549] - Policy control request triggers for MBS sessions are used to define the conditions under which MB-SMF should interact again with PCF to request an update of policy information for the MBS session, providing information on the conditions that have been met. The following policy control request triggers are defined for MBS: MBS session update.

[00550] In one embodiment, clause 9.1.3.6 of TS 23.247 V18.1.0 3GPP may be amended as follows.

[00551] 9.1.3.6 Nmbsmf_MBSSession_Create service operation

[00552] Service operation name: Nmbsmf_MBSSession_Create

[00553] Description: Create a new multicast session or broadcast session or for a location-dependent MBS session, the part of the MBS session within a service area. Optionally, subscribe to notifications for this MBS session.

[00554] Input, Required: MBS session ID (SSM or TMGI) or TMGI allocation request, MBS service type (multicast) Petition 870250090277, dated 03 / 10 / 2025, pp. 294 / 362 / 147 or dissemination).

[00555] Entry, Optional: DNN, S-NSSAI, MBS service area, Area session policy binding ID, MBS service information (as defined in clause 6.14), Inbound transport address request, MBS start time, MBS end time. For a multicast session, indication that any UE can participate, multicast session security context. For a broadcast session, MBS FSA ID(s). For notification event ID(s) subscription, Notification destination address, Location-dependent MBS session request, Associated session ID for resource sharing between broadcast MBS sessions during network sharing.

[00556] Exit, Mandatory: Result indication.

[00557] Output, Optional: TMGI, NID, TMGI expiration time, cause, MB-UPF tunnel information, MBS FSA ID(s), area session ID, area session policy binding ID.

[00558] The Area Session Policy Binding ID is provided to the location-dependent MBS service by AF / NEF / MBSF when interacting with the PCF, see Figure 5 description.

[00559] In one embodiment, clause 9.2.2.2 of TS 23.247 V18.1.0 3GPP may be amended as follows.

[00560] 9.2.2.2 Npcf_MBSPolicyControl_Create service operation

[00561] Service operation name: Npcf_MBSPolicyControl_Create

[00562] Description: The NF service consumer can request the creation of an MBS Policy Association and provide relevant parameters about the MBS session to the PCF.

[00563] Required entries: MBS session ID.

[00564] Entries, Optional: MBS service information (as defined in clause 6.14), Area session policy ID, DNN, Petition 870250090277, dated 03 / 10 / 2025, pp. 295 / 362 / 147 S-NSSAI.

[00565] Outputs, Mandatory: Success or Failure. In case of success, the MBS policy association ID and policy information for the MBS session (as defined in clause 6.10).

[00566] Outputs, Optional: In case of failure, the Service Information may be accepted by the PCF. In case of failure, an indication that another PCF should be put in contact and an ID of that other PCF.

[00567] The area session policy ID is provided for the location-dependent MBS service. The area session policy ID is set to the area session ID if the AF / NEF / MBSF does not interact with the PCF, or set to the area session policy binding ID if the AF / NEF / MBSF interacts with the PCF; see Figure 5 for description.

[00568] In one embodiment, clause 9.2.3.2 of TS 23.247 V18.1.0 3GPP may be amended as follows.

[00569] 9.2.3.2 Service operation Npcf_MBSPolicyAuthorization_Create

[00570] Service operation name: Npcf_MBSPolicyAuthorization_Create

[00571] Description: Authorize the request and, optionally, determine and install the MBS Policy Control Data according to the information provided by the NF Consumer.

[00572] Required Entries: MBS session ID.

[00573] Entries, Optional: DNN if available, S-NSSAI if available, MBS service information (as defined in clause 6.14), Area session binding ID.

[00574] Outputs, Required: Success (application session context) or Failure (reason for failure).

[00575] Outputs, Optional: In case of failure, MBS service information can be accepted by PCF. Petition 870250090277, dated 03 / 10 / 2025, pp. 296 / 362 / 147

[00576] The Area Session Policy Binding ID is provided to the location-dependent MBS service by AF / NEF / MBSF when interacting with the PCF, see Figure 5 description.

[00577] Many advantages can be achieved by applying the proposed solution according to the modalities described herein. In some modalities described herein, failures in creating application session context and / or policy association can be avoided. In some modalities described herein, the policy association created by the MBS policy control creates request with the authorized policy in the MBS policy authorization creates request for the same area session of a location-dependent MBS service can be well linked. In some modalities described herein, there is no significant added complexity to the current procedure. Some of the available information, such as area session ID, can be reused in the framework. In some modalities described herein, it has good compatibility with previous versions.The features and advantages described in this document are not limited to those mentioned above. Those skilled in the art will recognize additional features and advantages by reading the following detailed description.

[00578] In some embodiments in this document, it introduces the Area Session Policy Binding ID along with the Area Session Policy ID to resolve at least one of the problems identified above. It can avoid cases of failure in creating the application session context and / or policy binding. The policy binding created by the MBS policy control creation request with the authorized policy in the MBS policy authorization creation request for the same area session of a location-dependent MBS service can be well bound. There is no significant added complexity to the current procedure. Part of the information Petition 870250090277, dated 03 / 10 / 2025, pages 297 / 362 / 147 available, such as area session ID, can be reused in the framework. It has good compatibility with previous versions.

[00579] In some embodiments in this document, it uses the MBS Service Area as a unique identifier to address at least one of the problems identified above. It can avoid cases of failure in creating application session context and / or policy association. The policy association created by the MBS policy control creation request with the authorized policy in the MBS policy authorization creation request for the same area session of a location-dependent MBS service can be well linked. It may have fewer effects on the procedure. It can use the data currently available within the framework. It is a backward compatible solution.

[00580] In some embodiments in this document, it introduces a generic identifier that uniquely identifies a session for a specific MBS service area with the same MBS session ID to resolve at least one of the problems identified above. It can avoid cases of failure in application session context creation and / or policy association. The policy association created by the MBS policy control creates request with the authorized policy in the MBS policy authorization creates request for the same area session of a location-dependent MBS service can be well linked. There is no significant complexity added to the current procedure. A completely new identifier can be defined with the simplest format. It has good backward compatibility.

[00581] Figure 8A is a block diagram showing an apparatus suitable for practicing some of the described modes. For example, MB-SMF, PCF, or a network function described above can be implemented as or through the 800 apparatus.

[00582] The 800 device may comprise at least one processor Petition 870250090277, dated 03 / 10 / 2025, pp. 298 / 362 / 147 821, as a digital processor (DP), and at least one memory (MEM) 822 coupled to the processor 821. The apparatus 800 may further comprise a TX transmitter and an RX receiver 823 coupled to the processor 821. The MEM 822 stores a program (PROG) 824. The PROG 824 may include instructions that, when executed in the associated processor 821, enable the apparatus 800 to operate according to the embodiments of the present description. A combination of at least one processor 821 and at least one MEM 822 may form a processing medium 825 adapted to implement various embodiments of the present description.

[00583] Various embodiments of the present description may be implemented by a computer program executable by one or more of the 821 processor, software, firmware, hardware, or a combination thereof.

[00584] MEM 822 can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memories and removable memories as non-limiting examples.

[00585] The 821 processor may be of any type suitable for the local technical environment, and may include one or more of the following, including general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), and multi-core processor architecture-based processors, as non-limiting examples.

[00586] In an embodiment where the device is implemented as or in MB-SMF, memory 822 contains instructions executable by processor 821, by means of which MB-SMF operates according to any of the methods executed by MB-SMF as described above. Petition 870250090277, dated 03 / 10 / 2025, pp. 299 / 362 100 / 147

[00587] In an embodiment in which the device is implemented as or in the PCF, memory 822 contains instructions executable by processor 821, by means of which the PCF operates according to any of the methods performed by the PCF as described above.

[00588] In an embodiment where the device is implemented as or in a network function, memory 822 contains instructions executable by processor 821, wherein a network function operates according to any of the methods performed by a network function as described above.

[00589] Figure 8B is a block diagram showing an MBSMF according to one embodiment of the description. As shown, the MBSMF 850 ​​may comprise a first sending module 851 configured to send a multicast / broadcast (MBS) service policy control creation request to a policy control function (PCF). The MB-SMF 850 ​​may comprise a first receiving module 852 configured to receive an MBS policy control creation response for the location-dependent MBS session of the PCF. The MBS policy control creation request may comprise an MBS session identifier (ID) and some first information.The initial MBS session ID and information can be used to uniquely identify an MBS session toward a specific MBS service area from a location-dependent MBS session and / or create a policy association for the location-dependent MBS session corresponding to the MBS session ID and the initial information and / or differentiate different location-based services provided through the location-dependent MBS session with the same MBS session ID and / or associate application function (AF) session information with the location-dependent MBS session in a specific MBS service area and / or uniquely identify policy information for the location-dependent MBS session corresponding to the MBS session ID and the initial information. Petition 870250090277, dated 03 / 10 / 2025, pages 300 / 362 101 / 147 first piece of information.

[00590] In one embodiment, the MB-SMF 850 ​​may additionally comprise a second receiving module 853 configured to receive an MBS session creation request for the location-dependent MBS session of a network function.

[00591] In one embodiment, the MB-SMF 850 ​​may additionally comprise a second 854 sending module configured to send an MBS session creation response to the location-dependent MBS session for a network function.

[00592] Figure 8C is a block diagram showing a PCF according to one embodiment of the description. As shown, PCF 860 may comprise a first receiving module 861 configured to receive a request to create an MBS policy control for a location-dependent MBS session from an MB-SMF. PCF 860 may additionally comprise a first sending module 862 configured to send an MBS policy control creation response for the location-dependent MBS session to the MB-SMF. The MBS policy control creation request may comprise an MBS session ID and the first information.The first MBS session ID and information can be used to uniquely identify an MBS session toward a specific MBS service area from a location-dependent MBS session and / or create a policy association for the location-dependent MBS session corresponding to the MBS session ID and the first MBS session ID and / or differentiate different location-based services provided through the location-dependent MBS session with the same MBS session ID and / or associate application function (AF) session information with the location-dependent MBS session in a specific MBS service area and / or uniquely identify policy information for the location-dependent MBS session. Petition 870250090277, dated 03 / 10 / 2025, pages 301 / 362 102 / 147 corresponding to the MBS session ID and the first information and / or link the policy association with the application session context for the location-dependent MBS session corresponding to the MBS session ID and the first information.

[00593] In one embodiment, when the MBS policy control creation request does not include MBS service information, PCF 860 may include a location module 863 configured to locate policy information for the location-dependent MBS session corresponding to the MBS session ID and the first information.

[00594] In one embodiment, when the MBS policy control creation request comprises MBS service information and is authorized, and at least one required Quality of Service (QoS) parameter derived from the MBS service information is permitted, PCF 860 may additionally comprise a first generation module 864 configured to generate policy information for the location-dependent MBS session corresponding to the MBS session ID and the first information. PCF 860 may further comprise a first storage module 865 configured to store the policy information for the location-dependent MBS session corresponding to the MBS session ID and the first information, along with the MBS session ID and the first information.

[00595] In one embodiment, PCF 860 may further comprise a second receiving module 866 configured to receive a request to create an MBS policy authorization for the location-dependent MBS session of a network function. The MBS policy authorization creation request may include the second information, the MBS session ID and MBS service information. PCF 860 may additionally comprise a second sending module 867 Petition 870250090277, dated 03 / 10 / 2025, pages 302 / 362 103 / 147 is configured to send an MBS policy authorization creation response for the location-dependent MBS session for the network function. The second piece of information and the MBS session ID can be used to uniquely identify an MBS session toward a specific MBS service area from a location-dependent MBS session and / or differentiate different location-based services provided through location-dependent MBS sessions with the same MBS session ID and / or associate application function (AF) session information with the location-dependent MBS session in a specific MBS service area.

[00596] In one embodiment, PCF 860 may additionally comprise a third receiving module 868 configured to receive a request to create an MBS policy authorization for the location-dependent MBS session of a network function. The MBS policy authorization creation request may include an MBS service area for a location-dependent MBS service and the MBS session ID and MBS service information.

[00597] In one embodiment, PCF 860 may additionally comprise an assignment module 869 configured to assign a unique area session policy binding ID to the MBS service area. The unique area session policy binding ID may be used as the second piece of information.

[00598] In one embodiment, PCF 860 may additionally comprise a third 870 sending module configured to send an MBS policy authorization creation response for the location-dependent MBS session for the network function. The MBS policy authorization creation response may comprise the exclusive area session policy binding ID used as the second piece of information.

[00599] In one mode, when the request to create Petition 870250090277, dated 03 / 10 / 2025, pages 303 / 362 104 / 147 MBS policy request is authorized and at least one required QoS parameter derived based on MBS service information is allowed, PCF 860 may comprise a creation module 871 configured to create an application session context for the location-dependent MBS session corresponding to the MBS session ID and second information. PCF 860 may comprise a second generation module 872 configured to generate policy information for the location-dependent MBS session corresponding to the MBS session ID and second information. PCF 860 may comprise a second storage module 873 configured to store the policy information for the location-dependent MBS session corresponding to the MBS session ID and second information, along with the MBS session ID and second information.

[00600] Figure 8D is a block diagram showing a network function according to one embodiment of the description. As shown, network function 880 may comprise a first sending module 881 configured to send an MBS session creation request for a location-dependent MBS session to an MB-SMF. Network function 880 may additionally comprise a first receiving module 882 configured to receive an MBS session creation response for the location-dependent MBS session from the MB-SMF. The MBS session creation request may include second information and an MBS session ID.The second piece of information and the MBS session ID can be used to uniquely identify an MBS session toward a specific MBS service area from a location-dependent MBS session and / or differentiate different location-based services provided through a location-dependent MBS session with the same MBS session ID and / or associate application function (AF) session information with the location-dependent MBS session. Petition 870250090277, dated 03 / 10 / 2025, pages 304 / 362 105 / 147 location in a specific MBS service area.

[00601] In one embodiment, when the network function is a NEF or an MBSF, network function 880 may additionally comprise a second receiver module 883 configured to receive the MBS session creation request for the location-dependent MBS session of an AF. Network function 880 may additionally comprise a second send module 884 configured to send the MBS session creation response for the location-dependent MBS session to the AF.

[00602] In one embodiment, network function 880 may additionally comprise a third sending module 885 configured to send an MBS policy authorization creation request for the location-dependent MBS session to a PCF. The MBS policy authorization creation request may include the second piece of information, the MBS session ID, and the MBS service information. Network function 880 may additionally comprise a third receiving module 886 configured to receive an MBS policy authorization creation response for the location-dependent MBS session from the PCF. The second piece of information and the MBS session ID may be used to create an application session context for the location-dependent MBS session corresponding to the MBS session ID and the second piece of information.

[00603] In one embodiment, network function 880 may additionally comprise a fourth sending module 887 configured to send an MBS policy authorization creation request for the location-dependent MBS session to a PCF. The MBS session creation request may include an MBS service area for a location-dependent MBS service and the MBS session ID and MBS service information. Network function 880 may additionally comprise a fourth receiving module 888 configured to receive a creation response. Petition 870250090277, dated 03 / 10 / 2025, pages 305 / 362 106 / 147 MBS policy authorization for the location-dependent MBS session from the PCF. The MBS policy authorization creation response may include a unique area session policy binding ID used as the second piece of information. The second piece of information and the MBS session ID can be used to create an application session context for the location-dependent MBS session corresponding to the MBS session ID and the second piece of information.

[00604] In one embodiment, when a network function is a NEF or an MBSF, network function 880 may additionally comprise a fifth receiving module 889 configured to receive the MBS policy authorization creation request for the location-dependent MBS session from an AF. Network function 880 may additionally comprise a fifth sending module 890 configured to send the MBS policy authorization creation response for the location-dependent MBS session to the AF.

[00605] The term unit or module may have conventional meaning in the field of electronics, electrical devices and / or electronic devices and may include, for example, a set of electrical and / or electronic circuits, devices, modules, processors, memories, solid-state and / or distinct logic devices, computer programs or instructions to perform the respective tasks, procedures, computations, outputs and / or display functions and others, such as those described in this document.

[00606] With function units, MB-SMF, PCF or a network function may not need a fixed processor or memory; any computing and storage resource can be organized from the MB-SMF, PCF or network function in the communication system. The introduction of virtualization technology and network computing technology can improve the efficiency of network resource utilization and network flexibility.

[00607] In addition, the exemplary general switching system, Petition 870250090277, dated 03 / 10 / 2025, pages 306 / 362 107 / 147 including the terminal device (such as UE) and the network node (such as MB-SMF, PCF or network function), will be presented below.

[00608] Figure 9 shows an example of a QQ100 communication system according to some modalities.

[00609] In the example, the QQ100 communication system includes a QQ102 telecommunications network which includes a QQ104 access network, such as a radio access network (RAN), and a QQ106 core network, which includes one or more QQ108 core network nodes. The QQ104 access network includes one or more access network nodes, such as QQ110a and QQ110b network nodes (one or more of which may generally be referred to as QQ110 network nodes) or any other similar access nodes from the 3GPP (3GPP) or non-3GPP access points. Furthermore, as will be understood by those knowledgeable in the field, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are provided and integrated by a single vendor. Thus, it should be understood that network nodes include disaggregated implementations or parts thereof.For example, in some embodiments, the QQ102 telecommunications network includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the QQ102 telecommunications network that supports an ORAN specification (for example, a specification published by the O-RAN Alliance or any similar organization) and may operate alone or in conjunction with other nodes to implement one or more functionalities of any node in the QQ102 telecommunications network, including one or more QQ110 network nodes and / or QQ108 core network nodes.

[00610] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), an intelligent RAN controller. Petition 870250090277, dated 03 / 10 / 2025, pp. 307 / 362 108 / 147 (near real-time or non-real-time) that hosts software or software plugins, such as a near real-time control application (e.g., xApp) or a non-real-time control application (e.g., rApp) or any combination thereof (the adjective “open” designates support for an ORAN specification). The network node may support a specification, for example, by supporting an interface defined by the ORAN specification, such as an A1, F1, W1, E1, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Additionally, an ORAN access node may be a logical node within a physical node. Furthermore, an ORAN network node may be deployed in a virtualization environment (described later) in which one or more network functions are virtualized.For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies. QQ110 network nodes facilitate the direct or indirect connection of user equipment (UE), such as connecting QQ112a, QQ112b, QQ112c, and QQ112d UEs (one or more of which may generally be referred to as QQ112 UEs) to the QQ106 core network via one or more wireless connections.

[00611] Exemplary wireless communications via a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for carrying information without the use of wires, cables, or other material conductors. Furthermore, in different embodiments, the QQ100 communication system may include any number of wired or wireless networks, network nodes, UEs, and / or any other component or system that may facilitate or participate in the communication of data and / or signals via wired or wireless connections. The QQ100 communication system may Petition 870250090277, dated 03 / 10 / 2025, pages 308 / 362 109 / 147 include and / or interface with any type of communication, telecommunication, data, cellular, radio network and / or other similar type of system.

[00612] QQ112 UEs can be any type of a wide variety of communication devices, including wireless devices arranged, configured and / or operational to communicate wirelessly with QQ110 network nodes and other communication devices. Similarly, QQ110 network nodes are arranged, capable, configured and / or operational to communicate directly or indirectly with QQ112 UEs and / or with other network nodes or equipment on the QQ102 telecommunications network to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration on the QQ102 telecommunications network.

[00613] In the example shown, the QQ106 core network connects the QQ110 network nodes to one or more hosts, such as the QQ116 host. These connections can be direct or indirect through one or more intermediate networks or devices. In other examples, network nodes may be directly coupled to hosts. The QQ106 core network includes one or more core network nodes (e.g., QQ108 core network node) that are structured with hardware and software components. The characteristics of these components may be substantially similar to those described in relation to UEs, network nodes, and / or hosts, so the descriptions thereof are generally applicable to the corresponding components of the QQ108 core network node.Exemplary core network nodes include functions from one or more of the following: Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Service (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Signature Identifier Unmasking Function (SIDF), Unified Data Management (UDM), Protection Proxy. Petition 870250090277, dated 03 / 10 / 2025, pp. 309 / 362 110 / 147 Security Edge Protection (SEPP), Network Exposure Function (NEF) and / or a User Plane Function (UPF).

[00614] The QQ116 host may be owned or controlled by a service provider other than an operator or provider of the QQ104 access network and / or the QQ102 telecommunications network and may be operated by the service provider or on behalf of the service provider. The QQ116 host may host a variety of applications to provide one or more services. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieval and compilation of data under various environmental conditions detected by a plurality of UEs, analytics functionality, social networking, functions to control or otherwise interact with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[00615] As a whole, the QQ100 communication system in Figure 9 enables connectivity between UEs, network nodes, and hosts. In this sense, the communication system can be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE) and / or other 2G, 3G, 4G, 5G standards or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the 802.11 (WiFi) standards of the Institute of Electrical and Electronics Engineers (IEEE); and / or any other suitable wireless communication standard, such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, ZigBee Near Field Communication (NFC), LiFi and / or any low-power wide area network (LPWAN) standard, such as LoRa and Sigfox.

[00616] In some examples, the QQ102 telecommunications network is a Petition 870250090277, dated 03 / 10 / 2025, pages 310 / 362 111 / 147 cellular network that implements standardized 3GPP features. Consequently, the QQ102 telecommunications network can support network slicing to provide different logical networks for different devices that are connected to the QQ102 telecommunications network. For example, the QQ102 telecommunications network can provide Ultra-Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Wideband (eMBB) services to other UEs and / or Massive Machine Type Communication (mMTC) / Massive IoT services to still other UEs.

[00617] In some examples, QQ112 UEs are configured to transmit and / or receive information without direct human interaction. For example, a UE may be designed to transmit information to the QQ104 access network on a predetermined schedule, when triggered by an internal or external event or in response to requests from the QQ104 access network. Additionally, a UE may be configured to operate in single or multiple RAT mode or multiple patterns. For example, a UE may operate with any one or a combination of Wi-Fi, NR (New Radio) and LTE, i.e., it is configured for dual multi-radio connectivity (MR-DC), such as E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[00618] In the example, the QQ114 concentrator communicates with the QQ104 access network to facilitate indirect communication between one or more UEs (e.g., UE QQ112c and / or QQ112d) and network nodes (e.g., network node QQ110b). In some examples, the QQ114 concentrator may be a controller, router, content and analytics source, or any of the other communication devices described in this document in relation to UEs. For example, the QQ114 concentrator may be a wideband router that allows access to the QQ106 core network for the UEs. As another example, the QQ114 concentrator may be a controller that sends Petition 870250090277, dated 03 / 10 / 2025, pp. 311 / 362 112 / 147 commands or instructions for one or more actuators in the UEs. The commands or instructions can be received from the UEs, QQ110 network nodes, or through executable code, script, process, or other instructions in the QQ114 concentrator. As another example, the QQ114 concentrator can be a data collector that acts as temporary storage for UE data and, in some embodiments, can perform analysis or other processing of the data. As another example, the QQ114 concentrator can be a content source. For example, for a UE that is a VR headset, display, speaker, or other media delivery device, the QQ114 concentrator can retrieve VR resources, video, audio, or other media or data related to sensory information through a network node, which the QQ114 concentrator then provides to the UE directly after performing local processing and / or after adding additional local content.In yet another example, the QQ114 concentrator acts as a proxy server or orchestrator for the UEs, particularly if one or more of the UEs are low-energy IoT devices.

[00619] The QQ114 concentrator can have a constant / persistent or intermittent connection with the QQ110b network node. The QQ114 hub can also allow a different communication scheme and / or schedule between the QQ114 hub and the UEs (e.g., QQ112c and / or QQ112d UEs) and between the QQ114 hub and the QQ106 core network. In other examples, the QQ114 concentrator is connected to the QQ106 core network and / or one or more UEs via a wired connection. Additionally, the QQ114 concentrator can be configured to connect to an M2M service provider via the QQ104 access network and / or to another UE via a direct connection. In some scenarios, UEs can establish a wireless connection with the QQ110 network nodes while still connected through the QQ114 concentrator via a wired or wireless connection. In some configurations, the QQ114 concentrator may be a concentrator. Petition 870250090277, dated 03 / 10 / 2025, pp. 312 / 362 113 / 147 dedicated - that is, a concentrator whose primary function is to route communications to / from UEs to / from the QQ110b network node. In other embodiments, the QQ114 concentrator may be a non-dedicated concentrator - that is, a device that is capable of operating to route communications between UEs and the QQ110b network node, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[00620] Figure 10 shows a QQ200 UE according to some embodiments. As used in this document, a UE refers to a device capable, configured, disposed and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smartphone, mobile phone, cellular phone, voice over IP (VoIP) phone, wireless local link phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, portable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop embedded equipment (LEE), laptop mounted equipment (LME), smart device, wireless client premise equipment (CPE), vehicle, vehicle mounted or vehicle embedded / integrated wireless device, etc.Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a Narrowband Internet of Things (NB-IoT) UE, a Machine-Type Communication (MTC) UE, and / or an Enhanced MTC (eMTC) UE.

[00621] A UE can support device-to-device (D2D) communication, for example, through the implementation of a 3GPP standard for side-link communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who possesses Petition 870250090277, dated 03 / 10 / 2025, pages 313 / 362 114 / 147 and / or operates the relevant device. Alternatively, a UE may represent a device that is intended for sale to, or operation by, a human user, but which cannot, or cannot initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user, but which may be associated with or operated for the benefit of a user (e.g., a smart energy meter).

[00622] The QQ200 UE includes a set of QQ202 processing circuits that are operatively coupled via a 2504 bus to an input / output interface QQ206, a power supply QQ208, a memory QQ210, a communication interface QQ212 and / or any other component or any combination thereof. Certain UEs may use all or a subset of the components shown in Figure 10. The level of integration between the components may vary from one UE to another. Additionally, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[00623] The QQ202 processing circuitry is configured to process instructions and data and can be configured to implement any operational sequential state machine to execute stored instructions as machine-readable computer programs in QQ210 memory. The QQ202 processing circuitry can be implemented as one or more hardware-implemented state machines (e.g., in field-programmable distinct logic arrays (FPGAs), application-specific integrated circuits (ASICs), etc.); programmable logic in conjunction with suitable firmware; one or more stored computer programs; general-purpose processors such as a microprocessor or digital signal processor. Petition 870250090277, dated 03 / 10 / 2025, pp. 314 / 362 115 / 147 (DSP), in conjunction with appropriate software; or any combination of the above. For example, the QQ202 processing circuitry may include multiple central processing units (CPUs).

[00624] In the example, the QQ206 input / output interface can be configured to provide an interface to, or interface with, an input device, an output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, a transmitter, a smart card, another output device, or any combination thereof. An input device can allow a user to capture information on the UE QQ200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a webcam, etc.), a microphone, a sensor, a mouse, a moving sphere, a directional panel, a touch panel, a scroll wheel, a smart card, and the like.The presence-sensitive display may include a capacitive or resistive touch sensor to detect user input. A sensor may be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide both an input and an output device.

[00625] In some embodiments, the QQ208 power supply is structured as a battery or battery pack. Other types of power supplies, such as an external power source (e.g., an electricity outlet), photovoltaic device, or energy cell, may be used. The QQ208 power supply may additionally include a Petition 870250090277, dated 03 / 10 / 2025, pp. 315 / 362 116 / 147 power circuitry for delivering power from the QQ208 power supply itself and / or from an external power supply to various parts of the QQ200 UE via the input circuitry or an interface such as a power cable. Power delivery may be, for example, to charge the QQ208 power supply. The power circuitry may perform any shaping, conversion or other modification to the power from the QQ208 power supply to make the power suitable for the respective QQ200 UE components to which the power is supplied.

[00626] The QQ210 memory may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and others. In one example, the QQ210 memory includes one or more QQ214 application programs, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding QQ216 data. The QQ210 memory may store, for use by the UE QQ200, any one of a variety of different operating systems or combinations of operating systems.

[00627] The QQ210 memory can be configured to include numerous physical drive units, such as a redundant array of independent disks (RAID), flash memory, USB flash drive, external hard drive, mini-USB drive, pen drive, key drive, high-density digital versatile disc (HD-DVD), optical disc drive, internal hard drive, Blu-ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external dual mini-in-line memory module (DIMM), random access memory. Petition 870250090277, dated 03 / 10 / 2025, pp. 316 / 362 117 / 147 Synchronous dynamic memory (SDRAM), external micro-DIMM SDRAM, smart card memory, as a tamper-resistant module in the form of a Universal Integrated Circuit Card (UICC) including one or more Subscriber Identity Modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may, for example, be an embedded UICC (eUICC), integrated UICC (iUICC), or a removable UICC commonly known as a “SIM card.” The QQ210 memory may allow the UE QQ200 to access instructions, application programs, and the like, stored in transient or non-transient memory media to download data or to load data. A manufacturing article, such as one that utilizes a communication system, may be tangibly incorporated as or in the QQ210 memory, which may be or comprise a device-readable storage medium.

[00628] The QQ202 processing circuitry can be configured to communicate with an access network or another network using the QQ212 communication interface. The QQ212 communication interface may comprise one or more communication subsystems and may include, or be communicatively coupled to, a QQ222 antenna. The QQ212 communication interface may include one or more transceivers used to communicate, such as through communication with one or more remote transceivers from another wirelessly communicative device (e.g., another UE or a network node in an access network). Each transceiver may include an appropriate QQ218 transmitter and / or QQ220 receiver to provide network communications (e.g., frequency allocations, optical, electrical, and others).Furthermore, the QQ218 transmitter and the QQ220 receiver can be coupled to one or more antennas (e.g., QQ222 antenna) and can share circuit components, software, or firmware, or alternatively, be implemented separately.

[00629] In the illustrated version, the communication functions of Petition 870250090277, dated 03 / 10 / 2025, pp. 317 / 362 The QQ212 communication interface (118 / 147) may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as using the Global Positioning System (GPS) to determine a location, other similar communication functions, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Optical Network Linking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and others.

[00630] Regardless of the sensor type, a UE can provide an output of data captured by its sensors, through its QQ212 communication interface, via a wireless connection to a network node. The data captured by the sensors of a UE can be communicated via a wireless connection to a network node through another UE. The output can be periodic (e.g., once every 15 minutes if it reports the captured temperature), random (e.g., to regulate the reporting load of multiple sensors), in response to a trigger event (e.g., when humidity is detected, an alert is sent), in response to a request (e.g., a user-initiated request), or a continuous stream (e.g., a live video feed of a patient).

[00631] As another example, a UE comprises an actuator, a motor or a switch, related to a communication interface configured to receive wireless input from a network node through a Petition 870250090277, dated 03 / 10 / 2025, pp. 318 / 362 119 / 147 wireless connection. In response to received wireless input, the states of the actuator, motor, or switch can change. For example, the UE can understand a motor that adjusts the control surfaces or rotors of a drone in flight according to received input, or a robotic arm that performs a medical procedure according to received input.

[00632] A UE, when in the form of an Internet of Things (IoT) device, may be a device for use in one or more application domains, wherein these domains comprise, but are not limited to, city wearable technology, extended industrial application, and healthcare. Non-limiting examples of such an IoT device are a device that is, or is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice-controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / humidity sensor, an electric door lock, a connected doorbell, an air conditioning system such as a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device,An electric vehicle charging station, a smartwatch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable item for tactile augmentation or sensory enhancement, a water sprayer, an animal or item tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any type of medical device, such as a heart rate monitor or a remotely controlled surgical robot. A UE in the form of an IoT device comprises a set of circuits and / or software depending on the intended application of the IoT device in addition to others, Petition 870250090277, dated 03 / 10 / 2025, pp. 319 / 362 120 / 147 components, as described in relation to the UE QQ200 shown in Figure 10.

[00633] As yet another specific example, in an IoT scenario, a UE can represent a machine or other device that performs monitoring and / or measurements and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE can, in this case, be an M2M device, which, in a 3GPP context, can be referred to as an MTC device. As a particular example, the UE can implement the 3GPP NB-IoT standard. In other scenarios, a UE can represent a vehicle, such as a car, bus, truck, vessel, or aircraft, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[00634] In practice, any number of UEs can be used together in relation to a single use case. For example, a first UE might be integrated into a drone and provide the drone's speed information (obtained through a speed sensor) to a second UE which is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE can adjust the drone's acceleration (e.g., by controlling an actuator) to increase or decrease the drone's speed. The first and / or second UE can also include more than one of the functionalities described above. For example, a UE might understand both the sensor and the actuator and handle data communication for both the speed sensor and the actuators.

[00635] Figure 11 shows a QQ300 network node according to some embodiments. As used in this document, a network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment in a telecommunications network. Examples of nodes of Petition 870250090277, dated 03 / 10 / 2025, pp. 320 / 362 121 / 147 network includes, but is not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, B nodes, evolved B nodes (eNBs), and NR NodeBs (gNBs)), ORAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[00636] Base stations can be categorized based on the amount of coverage they provide (or otherwise their transmitted power level) and others, depending on the amount of coverage provided, can be provided as femto-base stations, pico-base stations, micro-base stations, or macro-base stations. A base station can be a relay node or a relay donor node that controls a relay.A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an ORAN access node), and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna-integrated radio. The parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[00637] Other examples of network nodes include 5G multi-point transmission point (multi-TRP) access nodes, multi-standard radio equipment (MSR) such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multi-cast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Service Mobile Location Centres (E-SMLCs)) and / or Drive Test Minimization (MDTs).

[00638] The QQ300 network node includes a set of circuits of Petition 870250090277, dated 03 / 10 / 2025, pages 321 / 362 The QQ300 network node consists of 122 / 147 QQ302 processing, QQ304 memory, a QQ306 communication interface, and a QQ308 power supply. The QQ300 network node can be composed of multiple physically separate components (e.g., a NodeB component and an RNC component, or a BTS component and a BSC component, etc.), each of which may have its own respective components. In certain scenarios where the QQ300 network node comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each single NodeB and pair of RNCs may, in some cases, be considered a single separate network node. In some embodiments, the QQ300 network node can be configured to support multiple radio access technologies (RATs).In such configurations, some components may be duplicated (e.g., separate QQ304 memory for different RATs) and some components may be reused (e.g., the same QQ310 antenna may be shared by different RATs). The QQ300 network node may also include multiple sets of the various components illustrated for different wireless technologies integrated into the QQ300 network node, for example, GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID), or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or a different chip or set of chips and other components within the QQ300 network node.

[00639] The QQ302 processing circuitry may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field-programmable gate array, or any other suitable computing device, feature, or combination of hardware, software, and / or logic. Petition 870250090277, dated 03 / 10 / 2025, pages 322 / 362 123 / 147 encoded operable to provide, individually or in conjunction with other QQ300 network node components, such as QQ304 memory, QQ300 network node functionality.

[00640] In some embodiments, the QQ302 processing circuitry includes a system-on-a-chip (SOC). In some embodiments, the QQ302 processing circuitry includes one or more of the QQ312 radio frequency (RF) transceiver circuitry and the QQ314 baseband processing circuitry. In some embodiments, the QQ312 radio frequency (RF) transceiver circuitry and the QQ314 baseband processing circuitry may be on separate chips (or chip assemblies), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of the QQ312 RF transceiver circuitry and the QQ314 baseband processing circuitry may be on the same chip or chip assemblies, boards, or units.

[00641] QQ304 memory may comprise any form of computer-readable volatile or non-volatile memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., a hard disk), removable storage media (e.g., a flash drive, a Compact Disc (CD) or a Digital Video Disc (DVD)) and / or any other volatile or non-volatile, device-readable, non-transient and / or computer-executable memory device that stores information, data and / or instructions that can be used by the QQ302 processing circuitry. QQ304 memory may store any suitable instruction, data or information that includes a computer program, software, an application that includes one or more of the following logic. Petition 870250090277, dated 03 / 10 / 2025, pp. 323 / 362 124 / 147 rules, codes, tables and / or other instructions capable of being executed by the QQ302 processing circuitry and used by the QQ300 network node. The QQ304 memory can be used to store any calculations performed by the QQ302 processing circuitry and / or any data received through the QQ306 communication interface. In some embodiments, the QQ302 processing circuitry and the QQ304 memory are integrated.

[00642] The QQ306 communication interface is used in wired or wireless signaling and / or data communication between a network node, access network, and / or UE. As illustrated, the QQ306 communication interface comprises one or more QQ316 ports / terminals for sending and receiving data, for example, to and from a network via a wired connection. The QQ306 communication interface also includes a set of QQ318 radio front-end circuits that can be coupled to, or in certain embodiments, a part of, the QQ310 antenna. The QQ318 radio front-end circuit set comprises QQ320 filters and QQ322 amplifiers. The QQ318 radio front-end circuit set can be connected to a QQ310 antenna and the QQ302 processing circuit set. The radio front-end circuitry can be configured to condition signals communicated between the QQ310 antenna and the QQ302 processing circuitry.The QQ318 radio front-end circuitry can receive digital data that must be sent to other network nodes or UEs via a wireless connection. The QQ318 radio front-end circuitry can convert the digital data into a radio signal with the appropriate channel and bandwidth parameters using a combination of QQ320 filters and / or QQ322 amplifiers. The radio signal can then be transmitted through the QQ310 antenna. Similarly, when receiving data, the QQ310 antenna can collect radio signals that are then converted into digital data by the front-end circuitry. Petition 870250090277, dated 03 / 10 / 2025, pp. 324 / 362 125 / 147 radio QQ318. Digital data can be passed to the QQ302 processing circuitry. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[00643] In certain alternative embodiments, the QQ300 network node does not include a separate QQ318 radio front-end circuit set; instead, the QQ302 processing circuit set includes a radio front-end circuit set and is connected to the QQ310 antenna. Similarly, in some embodiments, all or part of the QQ312 RF transceiver circuit set is part of the QQ306 communication interface. In still other embodiments, the QQ306 communication interface includes one or more QQ316 ports or terminals, the QQ318 radio front-end circuit set, and the QQ312 RF transceiver circuit set as part of a radio unit (not shown), and the QQ306 communication interface communicates with the QQ314 baseband processing circuit set, which is part of a digital unit (not shown).

[00644] The QQ310 antenna may include one or more antennas or antenna arrays, configured to send and / or receive wireless signals. The QQ310 antenna may be coupled to the QQ318 radio front-end circuitry and may be any type of antenna capable of transmitting and receiving wireless data and / or signals. In certain embodiments, the QQ310 antenna is separate from the QQ300 network node and is connectable to the QQ300 network node via an interface or port.

[00645] The QQ310 antenna, the QQ306 communication interface and / or the QQ302 processing circuitry can be configured to perform any reception operations and / or certain acquisition operations described in this document as being performed by the network node. Any information, data and / or signals can be received from a UE. Petition 870250090277, dated 03 / 10 / 2025, pp. 325 / 362 126 / 147 another network node and / or any other network equipment. Similarly, the QQ310 antenna, the QQ306 communication interface and / or the QQ302 processing circuitry can be configured to perform any transmission operations described herein as being performed by the network node. Any information, data and / or signals can be transmitted to another network node and / or any other network equipment.

[00646] The QQ308 power supply provides power to the various components of the QQ300 network node in a form suitable for the respective components (e.g., at a voltage and current level required for each respective component). The QQ308 power supply may additionally comprise or be coupled to a power management circuitry to provide the QQ300 network node components with power to perform the functionality described in this document. For example, the QQ300 network node may be connectable to an external power source (e.g., a power grid, an electricity outlet) via an input circuitry or interface such as a power cable, where the external power supply provides power to the power circuitry of the QQ308 power supply.As a further example, the QQ308 power supply may comprise a power supply in the form of a battery or battery pack that is connected to or integrated into the power circuitry. The battery may provide backup power should the external power supply fail.

[00647] QQ300 network node configurations may include additional components beyond those shown in Figure 11 to provide certain aspects of network node functionality, including any of the functionalities described herein and / or any functionality necessary to support the subject matter described herein. For example, the QQ300 network node may include equipment such as Petition 870250090277, dated 03 / 10 / 2025, pp. 326 / 362 The 127 / 147 user interface allows for inputting information into and outputting information from the QQ300 network node. This enables a user to perform diagnostics, maintenance, repair, and other administrative functions on the QQ300 network node.

[00648] Figure 12 is a block diagram of a QQ400 host, which may be an embodiment of the QQ116 host of Figure 9, according to various aspects described in this document. As used in this document, the QQ400 host may be or comprise various combinations of hardware and / or software, including a single server, a blade server, a cloud-deployed server, a distributed server, a virtual machine, a container, or processing resources in a server farm. The QQ400 host may provide one or more services to one or more UEs.

[00649] The QQ400 host includes a set of QQ402 processing circuits that are operatively coupled via a QQ404 bus to a QQ406 input / output interface, a QQ408 network interface, a QQ410 power supply, and a QQ412 memory. Other components may be included in other embodiments. The characteristics of these components may be substantially similar to those described in relation to the terminal devices, so the descriptions thereof are generally applicable to the corresponding QQ400 host components.

[00650] QQ412 memory may include one or more computer programs that include one or more QQ414 host application programs and QQ416 data, which may include user data, for example, data generated by a UE for the QQ400 host or data generated by the QQ400 host for a UE. QQ400 host embodiments may use only a subset or all of the components shown. QQ414 host application programs may be implemented in Petition 870250090277, dated 03 / 10 / 2025, pages 327 / 362 128 / 147 a container-based architecture and can provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, head-mounted display systems). The QQ414 host application programs can also provide for user authentication and license checks and can periodically report health, routes, and content availability to a central node, such as a device at or over the edge of a core network. Consequently, the QQ400 host can select and / or indicate a different host for over-the-top services for a UE.QQ414 host application programs can support various protocols, such as HTTP Live Streaming Protocol (HLS), Real-Time Messaging Protocol (RTMP), Real-Time Broadcast Protocol (RTSP), Dynamic Adaptive Broadcast over HTTP (MPEG-DASH), etc.

[00651] Figure 13 is a block diagram illustrating a QQ500 virtualization environment in which functions implemented by some modalities can be virtualized. In this context, virtualization means creating virtual versions of appliances or devices, which may include the virtualization of hardware platforms, storage devices, and network linking resources. As used in this document, virtualization can be applied to any device described herein or components thereof, and refers to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components. Petition 870250090277, dated 03 / 10 / 2025, pages 328 / 362 129 / 147 executed by one or more virtual machines (VMs) deployed in one or more QQ500 virtual environments hosted by one or more hardware nodes, such as a hardware computing device operating as a network node, UE, core network node, or host. Additionally, in modes where the virtual node does not require radio connectivity (e.g., a core network node or host), then the node can be fully virtualized. In some modes, the QQ500 virtualization environment includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Orchestration and Management Framework via an O-2 interface.

[00652] QQ502 applications (which may alternatively be referred to as software cases, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) run in the Q400 virtualization environment to implement some features, functions and / or benefits of some of the modalities described in this document.

[00653] The QQ504 hardware includes the processing circuitry, memory that stores software and / or instructions executable by the hardware processing circuitry, and / or other hardware devices, as described herein, such as a network interface, input / output interface, and others. The software may be executed by the processing circuitry to instantiate one or more QQ506 virtualization layers (also referred to as hypervisors or virtual machine monitors (VMMs)), provide QQ508A and QQ508B VMs (one or more of which may be generally referred to as QQ508 VMs), and / or perform any of the functions, features, and / or benefits described in relation to some embodiments described herein. The QQ506 virtualization layer may present a virtual operating platform that appears as network binding hardware to the QQ508 VMs. Petition 870250090277, dated 03 / 10 / 2025, pp. 329 / 362 130 / 147

[00654] QQ508 VMs comprise virtual processing, virtual memory, virtual network linking or interface, and virtual storage, and can be run by a corresponding QQ506 virtualization layer. Different modalities of a QQ502 virtual appliance case can be implemented in one or more of the QQ508 VMs, and the implementations can be done in different ways. Hardware virtualization is, in some contexts, referred to as network function virtualization (NFV). NFV can be used to consolidate many types of network equipment into high-volume, industry-standard server hardware, physical switches, and physical storage, which may be located in data centers and customer premises equipment.

[00655] In the context of NFV, a QQ508 VM can be a software implementation of a physical machine that executes programs as if they were running on a non-virtualized physical machine. Each of the QQ508 VMs and the QQ504 hardware component that runs that VM, being dedicated by hardware to that VM and / or shared by hardware by that VM with other VMs, form separate virtual network elements. Also in the context of NFV, a virtual network function is responsible for handling specific network functions that are executed by one or more QQ508 VMs on top of the QQ504 hardware and correspond to the QQ502 application.

[00656] The QQ504 hardware can be implemented in an individual network node with generic or specific components. The QQ504 hardware can implement some functions through virtualization. Alternatively, the QQ504 hardware can be part of a larger hardware cluster (e.g., as in a data center or CPE) where many hardware nodes work together and are managed through QQ510 management and orchestration, which, among other things, oversees the application lifecycle management of QQ502 applications. In some Petition 870250090277, dated 03 / 10 / 2025, pages 330 / 362 In 131 / 147 embodiments, the QQ504 hardware is coupled to one or more radio units, each of which includes one or more transmitters and one or more receivers that may be coupled to one or more antennas. The radio units may communicate directly with other hardware nodes via one or more suitable network interfaces and may be used in combination with virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling may be provided using a QQ512 control system which may alternatively be used for communication between hardware nodes and radio units.

[00657] Figure 14 shows a communication diagram of a QQ602 host communicating through a QQ604 network node with a QQ606 UE via a partially wireless connection according to several modalities. Exemplary implementations, according to various modalities, of the UE (such as a QQ112a UE of Figure 9), network node (such as a QQ110a network node of Figure 9) and host (such as a QQ116 host of Figure 9 and / or a QQ400 host of Figure 12) discussed in the preceding paragraphs will now be described with reference to Figure 14.

[00658] Like the QQ400 host, the QQ602 host modalities include hardware, such as a communication interface, processing circuitry, and memory. The QQ602 host also includes software, which is stored or accessible by the QQ602 host and executable by the processing circuitry. The software includes a host application that can be operational to provide a service to a remote user, such as the UE QQ606 connecting via an over-the-top (OTT) QQ650 connection extending between the UE QQ606 and the QQ602 host. When providing the service to the remote user, a host application can provide user data that is transmitted using the QQ650 OTT connection. Petition 870250090277, dated 03 / 10 / 2025, pages 331 / 362 132 / 147

[00659] The QQ604 network node includes hardware that allows it to communicate with the QQ602 host and the QQ606 UE. The QQ660 connection can be direct or pass through a core network (such as the QQ106 core network in Figure 9) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network could be a main chain network or the Internet.

[00660] The UE QQ606 includes hardware and software, which is stored on or accessible by the UE QQ606 and executable through the UE's processing circuitry. The software includes a client application, such as a web browser or operator-specific "app," that can be operated to provide a service to a human or non-human user through the UE QQ606 with support from the QQ602 host. On the QQ602 host, a running host application can communicate with the running client application via the QQ650 OTT connection that terminates on the UE QQ606 and the QQ602 host. When providing the service to the user, the UE client application can receive request data from the host application and provide user data in response to the request data. The QQ650 OTT connection can transfer both request data and user data.The UE client application can interact with the user to generate the user data provided to the host application via the QQ650 OTT connection.

[00661] The QQ650 OTT connection can be extended via the QQ660 connection between host QQ602 and network node QQ604 and via a wireless QQ670 connection between network node QQ604 and UE QQ606 to provide the connection between host QQ602 and UE QQ606. The QQ660 connection and the wireless QQ670 connection, through which the QQ650 OTT connection can be provided, were abstractly drawn to illustrate communication between host QQ602 and UE QQ606 via network node QQ604, without Petition 870250090277, dated 03 / 10 / 2025, pages 332 / 362 133 / 147 explicit reference to any intermediate device and the precise routing of messages through those devices.

[00662] As an example of data transmission via the QQ650 OTT connection, in step QQ608, the QQ602 host provides user data, which can be carried out through the execution of a host application. In some embodiments, the user data is associated with a particular human user interacting with the QQ606 UE. In other embodiments, the user data is associated with a QQ606 UE that shares data with the QQ602 host without explicit human interaction. In step QQ610, the QQ602 host initiates a transmission that carries the user data towards the QQ606 UE. The QQ602 host can initiate the transmission in response to a request transmitted by the QQ606 UE. The request can be caused by human interaction with the QQ606 UE or through the operation of the client application running on the QQ606 UE. The transmission can pass through the QQ604 network node according to the teachings of the embodiments described throughout this description.Consequently, in step QQ612, network node QQ604 transmits to UE QQ606 the user data that was executed in the transmission initiated by host QQ602, according to the principles of the modalities described throughout this description. In step QQ614, UE QQ606 receives the user data transported in the transmission, which can be performed through the client application running on UE QQ606 associated with the host application running on host QQ602.

[00663] In some examples, UE QQ606 runs a client application that provides user data to the host QQ602. User data may be provided in reaction to or response to data received from the host QQ602. Consequently, in step QQ616, UE QQ606 may provide user data, which can be accomplished by running the client application. By providing user data, the client application Petition 870250090277, dated 03 / 10 / 2025, pages 333 / 362 134 / 147 may additionally consider user input received from the user through an input / output interface of UE QQ606. Regardless of the specific way in which the user data was provided, UE QQ606 initiates, in step QQ618, the transmission of user data towards host QQ602 through network node QQ604. In step QQ620, according to the teachings of the embodiments described throughout this description, network node QQ604 receives user data from UE QQ606 and initiates the transmission of the received user data towards host QQ602. In step QQ622, host QQ602 receives the user data carried in the transmission initiated by UE QQ606.

[00664] One or more of the various embodiments enhance the performance of OTT services provided to UE QQ606 using the QQ650 OTT connection, in which the QQ670 wireless connection forms the last segment. More precisely, in some embodiments in this document, instances of failure in creating application session context and / or policy association can be avoided. In some embodiments in this document, the policy association created by the MBS policy control creates request with the authorized policy in the MBS policy authorization creates request for the same area session of a location-dependent MBS service can be well linked. In some embodiments in this document, there is no significant added complexity to the current procedure. Some of the available information, such as area session ID, can be reused in the framework. In some embodiments in this document, it has good backward compatibility.

[00665] In an illustrative scenario, factory state information can be collected and analyzed by the QQ602 host. As another example, the QQ602 host can process audio and video data that can be retrieved from a UE for use in map creation. As yet another example, the QQ602 host can collect and analyze real-time data. Petition 870250090277, dated 03 / 10 / 2025, pp. 334 / 362 135 / 147 to assist in vehicle congestion control (e.g., traffic light control). As another example, the QQ602 host can store surveillance video uploaded by a UE. As another example, the QQ602 host can store or control access to media content such as video, audio, VR, or AR, which can be broadcast, multi-broadcast, or uni-broadcast to UEs. As other examples, the QQ602 host can be used for energy pricing determination, remote control of critical electrical load without time to balance energy generation needs, location services, presentation services (such as compiling diagrams, etc., from data collected from remote devices), or any other data collection, retrieval, storage, analysis, and / or transmission function.

[00666] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency, and other factors in which one or more modes are enhanced. There may additionally be optional network functionality to reconfigure the QQ650 OTT connection between the QQ602 host and the QQ606 UE in response to variations in measurement results. The measurement procedure and / or the network functionality to reconfigure the OTT connection may be implemented in software and hardware of the QQ602 host and / or QQ606 UE. In some embodiments, sensors (not shown) may be deployed in or in association with other communication devices through which the QQ650 OTT connection passes; the sensors may participate in the measurement procedure by providing values ​​of the monitored quantities exemplified above or by providing values ​​of other physical quantities from which the software can calculate or estimate the monitored quantities.Reconfiguring the QQ650 OTT connection can include message format, transmission settings, preferred routing, etc.; reconfiguration does not need to directly alter the operation of the network node. Petition 870250090277, dated 03 / 10 / 2025, pages 335 / 362 136 / 147 QQ604. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, the measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency, and the like by the QQ602 host. The measurements may be implemented by the fact that the software causes messages to be transmitted, in particular, empty or artificial messages, using the QQ650 OTT connection while monitoring propagation times, errors, etc.

[00667] Although the computing devices described in this document (e.g., UEs, network nodes, hosts) may include the combination of hardware components illustrated, other embodiments may comprise computing devices with different combinations of components. It should be understood that these computing devices may comprise any suitable combination of hardware and / or software necessary to perform the tasks, features, functions, and methods described in this document.Determination, calculation, acquisition, or similar operations described in this document can be performed through the set of processing circuits, which can process information by, for example, converting the obtained information into other information, comparing the information or converted information with information stored in the network node, and / or performing one or more operations based on the obtained or converted information and, as a result of said processing, making a determination. Furthermore, although the components are graphically represented as single boxes located within a larger box or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that constitute a single illustrated component, and functionality may be divided among separate components. For example, a communication interface might be... Petition 870250090277, dated 03 / 10 / 2025, pages 336 / 362 137 / 147 configured to include any of the components described in this document and / or the functionality of the components may be divided between the processing circuitry and the communication interface. In another example, the non-computationally intensive functions of any of these components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.

[00668] In certain embodiments, some or all of the functionality described herein may be provided by the processing circuitry executing instructions stored in memory, wherein certain embodiments may be a computer program product in the form of a non-transient computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored in a separate or distinct device-readable storage medium, such as in a non-adjustable manner. In either of these particular embodiments, whether executing instructions stored in a non-transient or non-transient computer-readable storage medium, the processing circuitry may be configured to perform the described functionality.The benefits provided by such functionality are not limited to the individual processing circuitry or other components of the computing device, but are leveraged by the computing device as a whole and / or by end users and typically a wireless network.

[00669] Modality 1. A host configured to operate on a communication system to provide an over-the-top (OTT) service, wherein the host comprises: a set of processing circuits configured to provide user data; and Petition 870250090277, dated 03 / 10 / 2025, pages 337 / 362 138 / 147 a network interface configured to initiate the transmission of user data to a network node in a cellular network for transmission to a user device (UE), wherein the network node has a communication interface and processing circuitry, wherein the processing circuitry of the network node is configured to perform any of the network node-related operations, as described above, to transmit user data from the host to the UE.

[00670] Mode 2. The host of the preceding mode, wherein: The host processing circuitry is configured to run a host application that provides user data; and the UE comprises a set of processing circuits configured to run a client application associated with the host application to receive user data transmission from the host.

[00671] Embodiment 3. A method implemented on a host configured to operate in a communication system that additionally includes a network node and a user equipment (UE), wherein the method comprises: provide user data to the UE; and initiate a transmission that carries the user data to the UE via a cellular network comprising the network node, wherein the network node performs the network node-related operations as described above to transmit the user data from the host to the UE.

[00672] Embodiment 4. The method of the preceding embodiment, which additionally comprises, at the network node, the transmission of the user data provided by the host to the UE.

[00673] Mode 5. The method of either of the 2 previous modes, in which user data is provided on the host by the execution of a host application that interacts with a host application. Petition 870250090277, dated 03 / 10 / 2025, pages 338 / 362 139 / 147 client running on the UE, where the client application is associated with the host application.

[00674] Modality 6. A communication system configured to provide an over-the-top (OTT) service, the communication system comprising: a host that includes: A set of processing circuits configured to provide user data to a user device (UE), wherein the user data is associated with the over-the-top service; and a network interface configured to initiate the transmission of user data towards a cellular network node for transmission to the UE, wherein the network node has a communication interface and a set of processing circuits, wherein the network node's processing circuits are configured to perform any of the network node-related operations, as described above, to transmit user data from the host to the UE.

[00675] Mode 7. The communication system of the previous mode, which additionally includes: the network node; and / or the user equipment.

[00676] Mode 8. The communication system of the 2 previous modes, in which: The host processing circuitry is configured to run a host application, thereby providing user data; and the host application is configured to interact with a client application running on the UE, where the client application is associated with the host application.

[00677] Mode 9. A host configured to operate in a Petition 870250090277, dated 03 / 10 / 2025, pp. 339 / 362 140 / 147 communication system to provide an over-the-top (OTT) service, in which the host comprises: a set of processing circuits configured to initiate the reception of user data; and a network interface configured to receive user data from a network node on a cellular network, wherein the network node has a communication interface and a set of processing circuits, wherein the network node's set of processing circuits is configured to perform any of the network node-related operations, as described above, to receive user data from the UE to the host.

[00678] Mode 10. The host of the 2 previous modes, wherein: The host processing circuitry is configured to run a host application, thereby providing user data; and the host application is configured to interact with a client application running on the UE, where the client application is associated with the host application.

[00679] Mode 11. The host of the 2 previous modes, in which the initial receipt of user data comprises the request for user data.

[00680] Mode 12. A method implemented by a host configured to operate in a communication system that additionally includes a network node and a user device (UE), wherein the method comprises: On the host, initiate the reception of user data from the UE, where the user data originates from a transmission that the network node received from the UE, where the network node performs the network node-related operations, as described above, to receive the user data from the UE to Petition 870250090277, dated 03 / 10 / 2025, pages 340 / 362 141 / 147 the host.

[00681] Mode 13. The method of the previous mode, which additionally includes, at the network node, the transmission of the received user data to the host.

[00682] Mode 14. A host configured to operate on a communication system to provide an over-the-top (OTT) service, wherein the host comprises: A set of processing circuits configured to provide user data; and a network interface configured to initiate the transmission of user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and a processing circuit, the communication interface and processing circuit of the UE being configured to perform any of the UE-related operations, as described above, to receive user data from the host.

[00683] Mode 15. The host of the previous mode, in which the cellular network additionally includes a network node configured to communicate with the UE to transmit user data to the UE from the host.

[00684] Mode 16. The host of the 2 previous modes, in which: The host processing circuitry is configured to run a host application, thereby providing user data; and the host application is configured to interact with a client application running on the UE, where the client application is associated with the host application.

[00685] Mode 17. A method implemented by a host Petition 870250090277, dated 03 / 10 / 2025, pages 341 / 362 142 / 147 operating in a communication system that additionally includes a network node and a user device (UE), wherein the method comprises: to provide user data to the UE; and to initiate a transmission that carries the user data to the UE via a cellular network comprising the network node, where the UE performs any of the UE-related operations, as described above, to receive the user data from the host.

[00686] Modality 18. The method of the previous modality, which additionally includes: On the host, run a host application associated with a client application running on the UE to retrieve user data from the UE.

[00687] Modality 19. The method of the previous modality, which additionally includes: On the host, transmit input data to the client application running on the UE, where the input data is provided by the host application running, and the user data is provided by the client application in response to the input data from the host application.

[00688] Modality 20. A host configured to operate on a communication system to provide an over-the-top (OTT) service, wherein the host comprises: A set of processing circuits configured to use user data; and a network interface configured to receive the transmission of user data to a cellular network for transmission to a user device (UD), wherein the UD comprises a communication interface and a set of processing circuits, wherein the communication interface and Petition 870250090277, dated 03 / 10 / 2025, pages 342 / 362 143 / 147 The UE processing circuitry is configured to perform any of the UE-related operations, as described above, to transmit user data to the host.

[00689] Mode 21. The host of the previous mode, in which the cellular network additionally includes a network node configured to communicate with the UE to transmit user data from the UE to the host.

[00690] Modality 22. The host of the 2 previous modalities, in which: The host processing circuitry is configured to run a host application, thereby providing user data; and the host application is configured to interact with a client application running on the UE, where the client application is associated with the host application.

[00691] Mode 23. A method implemented by a host configured to operate in a communication system that additionally includes a network node and a user device (UE), wherein the method comprises: On the host, receive user data transmitted to the host via the network node by the UE, where the UE performs any of the UE-related operations, as described above, to transmit the user data to the host.

[00692] Modality 24. The method of the previous modality, which additionally includes: On the host, run a host application associated with a client application running on the UE to retrieve user data from the UE.

[00693] Modality 25. The method of the previous modalities, which Petition 870250090277, dated 03 / 10 / 2025, pages 343 / 362 144 / 147 additionally includes: On the host, transmit input data to the client application running on the UE, where the input data is provided by the host application running, and the user data is provided by the client application in response to the input data from the host application.

[00694] The term unit or module may have conventional meaning in the field of electronics, electrical devices and / or electronic devices and may include, for example, a set of electrical and / or electronic circuits, devices, modules, processors, memories, solid-state and / or distinct logic devices, computer programs or instructions to perform the respective tasks, procedures, computations, outputs and / or display functions and others, such as those described in this document.

[00695] According to one aspect of the description, a computer program product is provided that is tangibly stored on a computer-readable storage medium and includes instructions that, when executed on at least one processor, cause that processor to execute any of the methods described above.

[00696] According to one aspect of the description, a computer-readable storage medium is provided that stores instructions which, when executed by at least one processor, causes that processor to execute any of the methods as described above.

[00697] In addition, the present description may also provide a carrier containing the computer program as mentioned above, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium. The computer-readable storage medium may be, for example, an optical compact disc or an electronic memory device such as RAM. Petition 870250090277, dated 03 / 10 / 2025, pages 344 / 362 145 / 147 (random access memory), ROM (read-only memory), Flash memory, magnetic tape, CD-ROM, DVD, Blu-ray disc and similar.

[00698] The techniques described in this document can be implemented by various means, such that an apparatus implementing one or more functions of a corresponding apparatus described with an embodiment comprises not only the means of the prior art, but also the means for implementing the one or more functions of the corresponding apparatus with the embodiment, and may comprise separate means for each separate function or means that can be configured to perform two or more functions. For example, these techniques can be implemented in hardware (one or more apparatuses), firmware (one or more apparatuses), software (one or more modules), or combinations thereof. For firmware or software, the implementation can be done through modules (e.g., procedures, functions, and others) that perform the functions described in this document.

[00699] The exemplary embodiments in this document have been described above with reference to block diagrams and flowchart illustrations of methods and apparatus. It will be understood that each block of the block diagrams and flowchart illustrations and combinations of blocks in the block diagrams and flowchart illustrations, respectively, can be implemented by various means including computer program instructions. These computer program instructions can be loaded into a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions executing on the computer or other programmable data processing apparatus create a means to implement the functions specified in the flowchart block or blocks. Petition 870250090277, dated 03 / 10 / 2025, pages 345 / 362 146 / 147

[00700] Additionally, although operations are represented in a specific order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be executed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are contained in the discussions above, these should not be interpreted as limitations on the scope of the subject matter described in this document, but rather as descriptions of features that may be specific to particular modalities. Certain features described in the context of separate modalities may also be implemented in combination in a single modality.Conversely, several features that are described in the context of a single modality can also be implemented separately in multiple modalities or in any suitable subcombination.

[00701] Although this descriptive report contains many specific implementation details, these should not be interpreted as limitations on the scope of any implementation or of what may be claimed, but rather as descriptions of features that may be specific to certain embodiments of specific implementations. Certain features that are described in this descriptive report in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, several features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable subcombination. Furthermore, although features may be described above as acting in certain combinations and yet initially claimed as such, one or more features of a Petition 870250090277, dated 03 / 10 / 2025, pages 346 / 362 147 / 147 The claimed combination may in some cases be removed from the combination, and the claimed combination may refer to a subcombination or variation of a subcombination.

[00702] It will be obvious to one skilled in the art that, as technology advances, the inventive concept can be implemented in various ways. The embodiments described above are provided for description rather than to limit the description, and it is understood that modifications and variations may be rearranged without departing from the spirit and scope of the description, as will be readily understood by those skilled in the art. Such modifications and variations are considered to be included within the scope of the description and the appended claims. The scope of protection of the description is defined by the appended claims. Petition 870250090277, dated 03 / 10 / 2025, pages 347 / 362

Claims

1 / 14 CLAIMS 1. Method (200) implemented by a multicast / broadcast session management function, MB-SMF, characterized in that it comprises: sending (202) a multicast / broadcast service policy control creation request, MBS, to a location-dependent MBS session to a policy control function, PCF; and receiving (204) an MBS policy control creation response to the location-dependent MBS session from the PCF, wherein the MBS policy control creation request comprises an MBS session identifier, ID, and first information,wherein the first piece of information and the MBS session ID are used to: uniquely identify an MBS session for a specific MBS service area; location-dependent MBS session and / or create a policy association for the location-dependent MBS session corresponding to the MBS session ID and the first piece of information; and / or differentiate different location-based services provided through the location-dependent MBS session with the same MBS session ID; and / or associate application function (AF) session information with the location-dependent MBS session in a specific MBS service area; and / or uniquely identify policy information for the location-dependent MBS session corresponding to the MBS session ID and the first piece of information.

2. Method according to claim 1, characterized by the fact that the first piece of information comprises at least one of: a binding ID or an area session policy ID.

3. Method according to claim 2, characterized in that the area session policy ID comprises an area session ID.

4. Method according to claim 2, characterized in that the binding ID is assigned by at least one of an AF, a network exposure function, NEF, or a multicast / broadcast service function, MBSF, wherein the area session policy ID is assigned by at least one of an AF, an NEF, an MBSF, or a PCF.

5. Method according to claim 3, characterized in that if a request to create an MBS policy authorization for the location-dependent MBS session has not been sent to the PCF, the area session ID is used as the area session policy ID.

6. Method according to any one of claims 1 to 5, characterized in that it further comprises: receiving (212) an MBS session creation request for the location-dependent MBS session of a network function; and sending (214) an MBS session creation response for the location-dependent MBS session to the network function.

7. Method according to claim 6, characterized in that the MBS session creation request comprises the second piece of information and the MBS session ID, wherein the second piece of information and the MBS session ID are used to: Petition 870250090277, dated 10 / 03 / 2025, p. 349 / 362 3 / 14 uniquely identify an MBS session for a specific MBS service area of ​​a location-dependent MBS session and / or differentiate different location-based services provided through location-dependent MBS sessions with the same MBS session ID and / or associate application function session information, AF, with the location-dependent MBS session in a specific MBS service area.

8. Method according to claim 7, characterized in that the second piece of information comprises at least one of: a binding ID, or an area session policy ID.

9. Method according to claim 8, characterized in that the binding ID is assigned by at least one of an AF, a network exposure function, NEF, or a multicast / broadcast service function, MBSF, wherein the area session policy ID is assigned by at least one of the AF, NEF, MBSF, or PCF.

10. Method according to claim 9, characterized in that if a request to create an MBS policy authorization for the location-dependent MBS session has been sent to the PCF, the second piece of information, received by the MB-SMF from the network function, will be used as the first piece of information sent by the MB-SMF to the PCF.

11. Method according to any one of claims 8 to 10, characterized in that the network function comprises at least one of: an AF, a NEF or a MBSF.

12. Method (300) performed by a policy control function, characterized in that it comprises: receiving (302) a request to create an MBS policy control for a location-dependent MBS session from an MB-SMF, sending (306) a response to create an MBS policy control for the location-dependent MBS session to the MB-SMF, wherein the request to create an MBS policy control comprises an MBS session ID and the first information,wherein the first piece of information and the MBS session ID are used to: uniquely identify an MBS session for a specific MBS service area of ​​a location-dependent MBS session and / or create a policy association for the location-dependent MBS session corresponding to the MBS session ID and the first piece of information and / or differentiate different location-based services provided through the location-dependent MBS session with the same MBS session ID and / or associate application function session information, AF, with the location-dependent MBS session in a specific MBS service area and / or uniquely identify policy information for the location-dependent MBS session corresponding to the MBS session ID and the first piece of information and / or link the policy association with the application session context for the location-dependent MBS session corresponding to Petition 870250090277,from 03 / 10 / 2025, page 351 / 362 5 / 14 MBS session ID and first information., 13. Method according to claim 12, wherein when the request to create MBS policy control does not comprise MBS service information, characterized in that the method additionally comprises: locating (304) exclusively policy information for the MBS session dependent location corresponding to the MBS session ID and the first information.

14. Method according to claim 12 or 13, wherein, when the request to create MBS policy control comprises MBS service information and is authorized and at least one required quality of service parameter, QoS, derived based on MBS service information is allowed, characterized in that the method further comprises: generating (314) policy information for the location-dependent MBS session corresponding to the MBS session ID and the first information, and storing (316) the policy information.

15. A method according to any one of claims 12 to 14, characterized in that the first piece of information comprises at least one of either a binding ID or an area session policy ID.

16. Method according to claim 15, characterized in that the binding ID is assigned by at least one of an AF, a network exposure function, NEF, or a multicast / broadcast service function, MBSF, wherein the area session policy ID is assigned by at least one of an AF, an NEF, an MBSF, or a PCF.

17. Method according to claim 15 or 16, Petition 870250090277, dated 10 / 03 / 2025, pp. 352 / 362 6 / 14 characterized in that if a request to create an MBS policy authorization for the location-dependent MBS session has not been received by the PCF, the area session policy ID will comprise an area session ID.

18. Method according to any one of claims 12 to 17, characterized in that it further comprises: receiving (332) a request to create MBS policy authorization for the location-dependent MBS session of a network function, wherein the MBS policy authorization creation request comprises an MBS service area for a location-dependent MBS service and the MBS session ID and MBS service information; assigning (334) a unique area session policy ID to the MBS service area, wherein the unique area session policy ID is used as the second piece of information; and sending (336) an MBS policy authorization creation response to the location-dependent MBS session for the network function, wherein the MBS policy authorization creation response comprises the unique area session policy binding ID used as the second piece of information.

19. Method according to claim 18, wherein, when the request to create MBS policy authorization is authorized and at least one required QoS parameter derived based on MBS service information is allowed, characterized in that the method further comprises: creating (342) an application session context for the location-dependent MBS session corresponding to the MBS session ID and the second piece of information; Petition 870250090277, 10 / 03 / 2025, p. 353 / 362 7 / 14 generating (344) policy information for the location-dependent MBS session corresponding to the MBS session ID and the second piece of information; and storing (346) the policy information.

20. Method according to claim 18 or 19, characterized in that the second piece of information comprises at least one of a binding ID or an area session policy ID.

21. Method according to claim 20, characterized in that the linking ID is assigned by at least one of an AF, a network exposure function, NEF, or a multicast / broadcast service function, MBSF.

22. A method according to any one of claims 18 to 21, characterized in that the second piece of information, comprised in the MBS policy authorization creation response, is additionally received by the MB-SMF PCF as the first piece of information comprised in the MBS policy control creation request.

23. Method according to any one of claims 18 to 22, characterized in that the network function comprises at least one of: an AF, a network exposure function, NEF, or a multicast / broadcast service function, MBSF.

24. Method (400) implemented by a network function, characterized in that it comprises: sending (402) a request to create an MBS session to a location-dependent MBS session for an MB-SMF; and receiving (404) a response to create an MBS session for the location-dependent MBS session of the MB-SMF, wherein the request to create an MBS session comprises Petition 870250090277, of 03 / 10 / 2025, page.354 / 362 8 / 14 the second piece of information and an MBS session ID, wherein the second piece of information and the MBS session ID are used to: uniquely identify an MBS session for a specific MBS service area of ​​a location-dependent MBS session and / or differentiate different location-based services provided through the location-dependent MBS session with the same MBS session ID and / or associate application function session information, AF, with the location-dependent MBS session in a specific MBS service area.

25. Method according to claim 24, characterized in that the second piece of information comprises at least one of: a binding ID, or an area session policy ID.

26. Method according to claim 25, characterized in that the binding ID is assigned by at least one of an AF, a network exposure function, NEF, or a multicast / broadcast service function, MBSF, wherein the area session policy binding ID is assigned by at least one of the AF, NEF, or MBSF.

27. Method according to any one of claims 24 to 26, characterized in that the network function comprises at least one of: an AF, a NEF or an MBSF.

28. Method according to any one of claims 24 to 27, wherein, when the network function is a NEF or an MBSF, Petition 870250090277, 10 / 03 / 2025, pp. 355 / 362 9 / 14 characterized in that the method further comprises: receiving (412) the MBS session creation request for the location-dependent MBS session of an AF; and sending (414) the MBS session creation response for the location-dependent MBS session to the AF.

29. A method according to any one of claims 24 to 28, characterized in that, when the network function is an AF, sending an MBS session creation request to a location-dependent MBS session to an MB-SMF comprises: sending the MBS session creation request to the location-dependent MBS session directly to the MB-SMF or sending the MBS session creation request to the location-dependent MBS session to the MB-SMF via a NEF or an MBSF.

30. A method according to any one of claims 24 to 29, characterized in that it further comprises: sending (432) a request to create MBS policy authorization for the location-dependent MBS session to a PCF, wherein the MBS session creation request comprises an MBS service area for a location-dependent MBS service and the MBS session ID and MBS service information; and receiving (434) a response to create MBS policy authorization for the location-dependent MBS session from the PCF, wherein the response to create MBS policy authorization comprises a unique area session policy ID used as the second piece of information, wherein the second piece of information and the MBS session ID are used to create an application session context for the location-dependent MBS session corresponding to the MBS session ID and the second piece of information. Petition 870250090277, October 3, 2025, p.356 / 362 10 / 14.

31. Method according to claim 30, wherein, when a network function is a NEF or an MBSF, characterized in that the method further comprises: receiving (442) the MBS policy authorization creation request for the location-dependent MBS session from an AF; and sending (444) the MBS policy authorization creation response for the location-dependent MBS session to the AF.

32. Method according to claim 30, characterized in that, when the network function is an AF, sending the MBS policy authorization creation request for the location-dependent MBS session to a PCF comprises: sending the MBS policy authorization creation request for the location-dependent MBS session to the PCF directly or sending the MBS policy authorization creation request for the location-dependent MBS session to the PCF through a NEF or an MBSF.

33. Multicast / Broadcast Session Management Function (900), characterized in that it comprises: a processor (921); and a memory (922) coupled to the processor (921), wherein said memory (922) comprises instructions executable by said processor (921), wherein said MB-SMF (900) is operational for: sending a request to create a Multicast / Broadcast Service Policy Control, MBS, for a location-dependent MBS session to a policy control function, PCF; and receiving a response to create an MBS policy control for the location-dependent MBS session from the PCF, wherein the request to create an MBS policy control Petition 870250090277, dated 03 / 10 / 2025, page.357 / 362 11 / 14 comprises an MBS session identifier, ID, and first information, wherein the first information and the MBS session ID are used to: uniquely identify an MBS session for a specific MBS service area of ​​a location-dependent MBS session and / or create a policy association for the location-dependent MBS session corresponding to the MBS session ID and the first information and / or differentiate different location-based services provided through the location-dependent MBS session with the same MBS session ID and / or associate application function session information, AF, with the location-dependent MBS session in a specific MBS service area and / or uniquely identify policy information for the location-dependent MBS session corresponding to the MBS session ID and the first information.

34. Multicast / broadcast session management function according to claim 33, characterized in that the MB-SMF is additionally operational to perform the method as defined in any one of claims 2 to 11.

35. Policy control function (900), characterized in that it comprises: a processor (921); and a memory (922) coupled to the processor (921), wherein said memory (922) contains instructions executable by said processor (921), by means of which said policy control function (900) is operational for: Petition 870250090277, dated 10 / 03 / 2025, pp. 358 / 362 12 / 14 receiving a request to create an MBS policy control for a location-dependent MBS session from an MB-SMF, sending an MBS policy control creation response to the location-dependent MBS session to the MB-SMF, wherein the MBS policy control creation request comprises an MBS session ID and the first information,where the initial information and the MBS session ID are used to: uniquely identify an MBS session for a specific MBS service area, a location-dependent MBS session, and / or create a policy association for the location-dependent MBS session corresponding to the MBS session ID and the initial information, and / or differentiate different location-based services provided through the location-dependent MBS session with the same MBS session ID, and / or associate application function session information, AF,with the location-dependent MBS session in a specific MBS service area and / or uniquely identify policy information for the location-dependent MBS session corresponding to the MBS session ID and the first piece of information and / or link the policy association with the application session context for the location-dependent MBS session corresponding to the MBS session ID and the first piece of information.

36. Policy control function according to claim 35, characterized in that the policy control function is additionally operational to perform the method as defined in any of claims 13 to 23.

37. Network function (900), characterized in that it comprises: a processor (921); and a memory (922) coupled to the processor (921), wherein said memory (922) comprises instructions executable by said processor (921), by means of which said network function (900) is operational for: sending a request to create an MBS session for a location-dependent MBS session to an MB-SMF;and receive an MBS session creation response for the MB-SMF location-dependent MBS session, wherein the MBS session creation request comprises the second piece of information and an MBS session ID, wherein the second piece of information and the MBS session ID are used to: uniquely identify an MBS session for a specific MBS service area of ​​the location-dependent MBS session and / or differentiate different location-based services provided through the location-dependent MBS session with the same MBS session ID and / or associate application function session information, AF, with the location-dependent MBS session in a specific MBS service area.

38. Network function according to claim 37, characterized in that the network function is additionally operational for performing the method as defined in any one of claims 25 to 32.

39. Computer-readable storage medium, Petition 870250090277, dated 10 / 03 / 2025, pp. 360 / 362 14 / 14 characterized in that it stores instructions which, when executed by at least one processor, cause that at least one processor to perform the method as defined in any of claims 1 to 32.

40. Product, process, system, method, kit or use, characterized by the fact that it comprises one or more elements as described in the report and / or illustrated in the figures. Petition 870250090277, dated 03 / 10 / 2025, pp. 361 / 362

Images