Patent Description:
Examples of mobile or wireless telecommunication systems may include <NUM> RAT, the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), LTE Evolved UTRAN (E-UTRAN), LTE-Advanced (LTE-A), LTE-A Pro, NR access technology, and/or MulteFire Alliance. <NUM> wireless systems refer to the next generation (NG) of radio systems and network architecture. A <NUM> system is typically built on a <NUM> NR, but a <NUM> (or NG) network may also be built on E-UTRA radio. It is expected that NR can support service categories such as enhanced mobile broadband (eMBB), ultra-reliable low-latency-communication (URLLC), and massive machine-type communication (mMTC). NR is expected to deliver extreme broadband, ultra-robust, low-latency connectivity, and massive networking to support the Internet of Things (IoT). The next generation radio access network (NG-RAN) represents the RAN for <NUM>, which may provide radio access for NR, LTE, and LTE-A. It is noted that the nodes in <NUM> providing radio access functionality to a user equipment (e.g., similar to the Node B in UTRAN or the Evolved Node B (eNB) in LTE) may be referred to as next-generation Node B (gNB) when built on NR radio, and may be referred to as next-generation eNB (NG-eNB) when built on E-UTRA radio.

Document <CIT>discloses a multicast session establishment method. When the multicast session is established, policy control, for example, quality of service QoS control, of the multicast session may be completed via a policy control network element or a session management network element.

The <NPL>, discusses session establishment procedures for broadcast services.

Accordingly, methods, apparatuses and non-transitory computer readable medium according to the independent claims are provided.

It will be readily understood that the components of certain example embodiments, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of some example embodiments of systems, methods, apparatuses, and computer program products for policy controls for broadcast sessions is not intended to limit the scope of certain example embodiments, but is instead representative of selected example embodiments.

Policy updates may occur during certain procedures, and may trigger a potentially large amount of signalling to many access and mobility management function (AMF) and radio access network (RAN) nodes involved in the distribution of a broadcast session. However, a multicast/broadcast session management function (MB-SMF) may not know in advance whether a policy update will occur.

Certain example embodiments described herein may have various benefits and/or advantages to overcome the disadvantages described above. For example, certain example embodiments may enable an MB-SMF to know if a policy update will occur in advance. Certain embodiments may also avoid duplicated signalling for the establishment of broadcast resources towards RAN nodes due to possible policy updates within the initial configuration procedures. Thus, certain example embodiments discussed below are directed to improvements in computer-related technology.

In request to create a broadcast session, a network exposure function (NEF) or multicast/broadcast service function (MBSF) indicates to a MB-SMF whether it will also provide a policy authorization for the broadcast session with the policy control function (PCF). If the MB-SMF obtains this indication, it waits until after requesting and obtaining policies for the broadcast session from the PCF for an update of policies from the PCF before signaling to AMFs to request the allocation of resources to for the transmission of the broadcast session. When obtaining a request for the creation of a policy authorization for a broadcast session, for which it already performs policy control towards an MB-SMF, the PCF may provide a policy update message to the MB-SMF even if no policies need to be changed. In certain example embodiments, the PCF may repeat previous policies or send an empty update message.

In certain example embodiments, policies for broadcast sessions provided by the PCF to the MB-SMF may contain an indication whether resources to for the transmission of the broadcast session shall be allocated. When obtaining a request to establish policy control for a broadcast session from the MB-SMF, the PCF may decide to provide policies requesting no resource allocation in the reply and start a timer to wait for the establishment of a policy authorization. Upon expiry of that timer or upon receiving a request for a policy authorization for that broadcast session from the NEF or MBSF, the PCF provides policies requesting the resource allocation. Based on the indication about the resource allocation in the policies, the MB-SMF signals to AMFs to request the allocation of resources to for the transmission of the broadcast session.

In various example embodiments, after receiving a request to create a broadcast session, and requesting and obtaining policies for the broadcast session from the PCF, the MB-SMF may start a timer to wait for an update of those policies from the PCF. Upon expiry of that timer or upon receiving updated policies from the PCF, the MB-SMF may signal to AMFs to request the allocation of resources to for the transmission of the broadcast session.

<FIG> illustrates an example of a signaling diagram depicting how to perform initial multicast/broadcast service (MBS) session configuration with policy and charging control (PCC). AMF <NUM>, multicast/broadcast user plane function (MB-UPF) <NUM>, MB-SMF <NUM>, PCF <NUM>, binding support function (BSF) <NUM>, unified data repository (UDR) <NUM>, NRF <NUM>, NEF/MBSF <NUM>, multicast/broadcast service transport function (MBSTF) <NUM>, and application function (AF) <NUM> may be similar to NE <NUM>, as illustrated in <FIG>, according to certain example embodiments.

AF <NUM> may use the configuration steps for an MBS session to start an MBS session towards 5GC, which may consist of temporary mobile group identity (TMGI) allocation and MBS session start procedures that apply to both multicast and broadcast communications. MBS session establishment/activation procedures may follow MBS session configuration procedures per their service type (multicast or broadcast service) to reserve resources towards NG-RAN. For broadcast communication, MBS session establishment/start may include radio resource reservation towards a NG-RAN. For multicast communication, the radio resource reservation may be performed when a user equipment (UE) is available to join. For both broadcast and multicast communication, the TMGI allocation may be separated from the MBS session establishment/start procedure. For multicast communication, TMGI allocation procedures may be applicable if TMGI is used as MBS Session ID.

At <NUM>, AF <NUM> may transmit to NEF/MBSF <NUM> at least one Allocate TMGI Request () message configured to request allocation of a TMGI to identify a new MBS session. Depending on the configuration, MB-SMF <NUM> may receive requests from AF <NUM> directly, or via NEF/MBSF <NUM>. At <NUM>, NEF/MBSF <NUM> may check authorization of AF <NUM>. At <NUM>, NEF/MBSF <NUM> may discover and select MB-SMF <NUM> using NRF <NUM> and/or based on local configurations. At <NUM>, NEF/MBSF <NUM> may send an Allocate TMGI Request () message to MB-SMF <NUM>. At <NUM>, MB-SMF <NUM> may allocate TMGI(s) and return the TMGI(s) to NEF/MBSF <NUM> via Allocate TMGI Response (TMGI(s)). It is noted that steps <NUM>-<NUM> may be optional, and may only apply if TMGI is used as an MBS Session ID and required to be pre-allocated.

At <NUM>, NEF/MBSF <NUM> may respond to AF <NUM> by sending an Allocate TMGI Response (TMGI(s)) message. At <NUM>, AF <NUM> may perform a service announcement towards at least one UE, which may be similar to UE <NUM> shown in <FIG>. For example, AF <NUM> may inform UEs about MBS Session information with MBS Session ID, e.g., TMGI, source specific multicast address, and possibly other information e.g., MBS service area, session description information, etc. In some example embodiments, the MBS service area information may be a Cell ID list, TAI list, geographical area information, or civic address information. Amongst them, the Cell ID list and TAI list may be used by AFs that reside in trust domain, and when the AFs are aware of such information. In addition, the UEs may need to be aware if the service is broadcast or multicast to decide if to join.

At <NUM>, AF <NUM> of at least one content provider may provide at least one description for an MBS session (possibly providing information for a previously allocated TMGI; e.g., service type of either multicast service or broadcast service) to NEF/MBSF <NUM> by MBS Session Request ([MBS Session ID], service type, MBS information,) message. If steps <NUM>-<NUM> have not been executed before, AF <NUM> may provide a source specific multicast address and/or may request that the network allocate an identifier for the MBS session (i.e., TMGI) and its service type of either multicast service or broadcast service. MBS information may further include QoS requirements, MBS service area information (e.g., step <NUM>) identifying the service scope, start and end time of MBS. In addition, MBS information may also indicate whether the allocation of an ingress transport address is requested. If geographical area information or civic address information was provided by AF <NUM> as MBS service area, NEF/MBSF <NUM> may translate the MBS service area to Cell ID list or TAI list. Additionally or alternatively, NEF/MBSF <NUM> may check for authorizations of at least one content provider.

At <NUM>, NEF/MBSF <NUM> may discover MB-SMF <NUM> candidates and/or select MB-SMF <NUM> as an ingress control node, possibly based on location area. If TMGI is included at step <NUM>, NEF/MBSF <NUM> may find MB-SMF <NUM> based on TMGI.

At <NUM>, NEF/MBSF <NUM> may send an MBS Session Create Request (MBS Session ID, service type, TMGI allocation indication, MBS service area information, ingress transport address request indication) to MB-SMF <NUM> to request MB-SMF <NUM> to reserve ingress resources for an MBS distribution session, and may provide MBS Session ID or request allocation, and indicate its service type (either multicast service or broadcast service). In some example embodiments, NEF/MBSF <NUM> may decide based on local configuration or based on parameters received at <NUM> (e.g., whether the session comprises several data flows) whether it will invoke the Npcf_MBSPolicy Authorization service for the MBS session. In the request to create a broadcast session, NEF/MBSF <NUM> may indicate to MB-SMF <NUM> whether it will also provide a policy authorization session for the MBS session with PCF <NUM>. The MBS Session Create Request may also indicate if the allocation of an ingress transport address is requested. The MBS service area information may be provided by NEF/MBSF <NUM> to MB-SMF <NUM> if provided by AF <NUM> at step <NUM>.

At <NUM>, if MB-SMF <NUM> is selected by NEF/MBSF <NUM> at step <NUM>, and source specific multicast address is provided at step <NUM>, MB-SMF <NUM> may allocate TMGI, and MB-SMF <NUM> may update at least one NF profile to NRF <NUM> with the serving MBS Session ID.

In certain example embodiments, if TMGI is used to represent an MBS Session, MB-SMF <NUM> may not need to update NRF <NUM> if the TMGI range(s) supported by MB-SMF <NUM> are already included in the MB-SMF profile when MB-SMF <NUM> registers itself into NRF <NUM>.

At <NUM>, if NEF/MBSF <NUM> indicated at <NUM> that it will also provide a policy authorization for the broadcast session to PCF <NUM>, MB-SMF <NUM> may select a PCF and send an Npcf_MBSPolicyControl_Create Request (MBS session ID) for the MBS session towards PCF <NUM> to create a policy control session for the MBS session, and may defer step <NUM> until MB-SMF <NUM> receives an Npcf_MBSPolicyControl_UpdateNotify for the MBS session. Otherwise, MB-SMF <NUM> may decide based on local configuration whether to invoke the Npcf_ MBSPolicyControl service.

At <NUM>, PCF <NUM> may register at BSF <NUM> that it handles the multicast session. For example, PCF <NUM> may provide an identifier that the policy authorization is for multicast and the MBS Session ID, its own PCF ID, and optionally its PCF set ID. At <NUM>, PCF <NUM> may retrieve preconfigured policy information for the MBS session from UDR <NUM>. At <NUM>, PCF <NUM> may respond in the policy control session with an SM MBS Policy authorization Response (MBS Policy) with policies for the MBS Session ID. Based on the indication in step <NUM>, MB-SMF <NUM> may not signal to AMFs to request the allocation of resources to for the transmission of the broadcast session after this step.

At <NUM>, if PCC is not used, MB-SMF <NUM> may derive the required QoS parameters locally. MB-SMF <NUM> may select MB-UPF <NUM> and/or request it to reserve user plane ingress resources. If multicast transport of the MBS data towards RAN nodes is to be used, MB-SMF <NUM> may also request MB-UPF <NUM> to reserve for the outgoing data a tunnel endpoint and the related identifiers (source IP address, source specific multicast address and GTP Tunnel ID) and to forward data received at the user plane ingress resource using that tunnel endpoint. If ingress address is not requested, MB-SMF <NUM> may configure MB-UPF <NUM> to handle the multicast data distribution, and request MB-UPF <NUM> to join the multicast tree towards the content provider. MB-UPF <NUM> may also join the distribution tree of the content provider in the subsequent session establishment procedure.

At <NUM>, if requested, MB-UPF <NUM> may select an ingress address (IP address and port) and a tunnel endpoint for the outgoing data, and provide it to MB-SMF <NUM>. For broadcast communication, MB-SMF <NUM> may continue the procedure towards AMF <NUM> (and/or an NG-RAN) before step <NUM> is executed.

At <NUM>, MB-SMF <NUM> may indicate the possibly allocated ingress address to NEF/MBSF <NUM>. MB-SMF <NUM> may include TMGI if it is allocated in step <NUM>. It also indicates the success or failure of reserving transmission resources.

At <NUM> and <NUM>, NEF/MBSF <NUM> may use the BSF discovery service, with a request and response, to discover PCF <NUM> serving the MBS session with the MBS session ID.

At <NUM>, NEF/MBSF may send SM MBS Policy authorization Request to PCF <NUM> with the MBS session ID and MBS information. PCF <NUM> may determine whether the request is authorized. If the request is authorized, PCF may derive the required QoS parameters based on the information provided by NEF <NUM>, and determine whether this QoS is allowed (according to the PCF configuration for this application). If the request is not authorized or the required QoS is not allowed, PCF <NUM> may indicate so in the response to NEF/MBSF <NUM>.

At <NUM>, when obtaining a request for the creation of a policy authorization session at <NUM>, for a broadcast session for which it already performs policy control towards MB-SMF <NUM>, PCF <NUM> may provide a policy update message to MB-SMF <NUM> even if no policies need to be changed.

At <NUM>, if required by the updated policies, MB-SMF <NUM> may update MB-UPF <NUM>, accordingly. At <NUM>, when obtaining an MBS policy control update from PCF <NUM> at <NUM>, MB-SMF <NUM> may signal to AMF <NUM> to request the allocation of resources for the transmission of the broadcast session.

At <NUM>, if NEF/MBSF <NUM> decides to use MBSTF <NUM>, NEF/MBSF <NUM> may provide the received ingress address in step <NUM> towards MBSTF <NUM> as DL destination, and may request MBSTF <NUM> to allocate the user plane ingress resources. At <NUM>, if requested, MBSTF <NUM> may select an ingress address (IP address and port), and provide it to NEF/MBSF <NUM>. At <NUM>, NEF/MBSF-C <NUM> may include the ingress address if allocated and other parameters (e.g., TMGI) to AF <NUM> by MBS Session Response ([TMGI], [Allocated ingress address]) message. If MBS Session ID is not provided in step <NUM>, or the MBS Session ID is source specific multicast address, NEF/MBSF <NUM> may provide the allocated TMGI. If AF <NUM> requests the allocation of an ingress transport address, the message may also include the allocated ingress address. <NUM> may be similar to <NUM>, where AF <NUM> may perform a service announcement. For multicast communication, depending on configuration, at least one UE join request may be accepted from this point onward.

<FIG> illustrates an example of a signaling diagram depicting how to perform initial MBS session configuration with PCC, according to certain example embodiments. AMF <NUM>, MB-UPF <NUM>, MB-SMF <NUM>, PCF <NUM>, BSF <NUM>, UDR <NUM>, NRF <NUM>, NEF/MBSF <NUM>, MBSTF <NUM>, and AF <NUM> may be similar to NE <NUM>, as illustrated in <FIG>, according to certain example embodiments.

AF <NUM> may use the configuration steps for an MBS session to start an MBS session towards 5GC, which may consist of TMGI allocation and MBS session start procedures that apply to both multicast and broadcast communications. MBS session establishment/activation procedures may follow MBS session configuration procedures per their service type (multicast or broadcast service) to reserve resources towards NG-RAN. For broadcast communication, MBS session establishment/start may include radio resource reservation towards a NG-RAN. For multicast communication, the radio resource reservation may be performed when a UE is available to join. For both broadcast and multicast communication, the TMGI allocation may be separated from the MBS session establishment/start procedure. For multicast communication, TMGI allocation procedures may be applicable if TMGI is used as MBS Session ID.

Steps <NUM>-<NUM> in <FIG> may be similar to steps <NUM>-<NUM> described above with respect to <FIG>. At <NUM>, NEF/MBSF <NUM> may send an MBS Session Create Request (MBS Session ID, service type, TMGI allocation indication, MBS service area information, ingress transport address request indication) to MB-SMF <NUM> to request MB-SMF <NUM> to reserve ingress resources for an MBS distribution session, and may provide MBS Session ID or request allocation, and indicate its service type (either multicast service or broadcast service). The MBS Session Create Request may also indicate if the allocation of an ingress transport address is requested. The MBS service area information may be provided by NEF/MBSF <NUM> to MB-SMF <NUM> if provided by AF <NUM> at step <NUM>.

Steps <NUM>-<NUM> may also be similar to steps <NUM>-<NUM> described in <FIG>. At <NUM>, when receiving a request for the establishment of policy control session for a broadcast session at <NUM>, PCF <NUM> may provide policies with an indication requesting no resource allocation in the reply, and/or may start a timer for the broadcast session to wait for the establishment of a policy authorization. Based on the indication about no resource allocation in the policies, MB-SMF <NUM> may not signal to AMF <NUM> to request the allocation of resources to for the transmission of the broadcast session.

Steps <NUM>-<NUM> may also be similar to steps <NUM>-<NUM> as described above with respect to <FIG>. At <NUM>, upon expiration of the timer and/or upon receiving a request for a policy authorization for that broadcast session from NEF/MBSF <NUM> at <NUM>, PCF <NUM> may provide policies within the policy control session with an indication requesting the resource allocation. At 22a, upon receiving a request for a policy authorization for that broadcast session from NEF/MBSF <NUM>, PCF <NUM> may stop the timer. At <NUM>, if required by the updated policies, MB-SMF <NUM> may update MB-UPF <NUM>, accordingly. At <NUM>, based on the indication about the resource allocation in the policies, MB-SMF <NUM> may signal AMF <NUM> to request the allocation of resources to for the transmission of the broadcast session. Steps <NUM>-<NUM> may then be similar to steps <NUM>-<NUM> discussed in <FIG>.

Steps <NUM>-<NUM> in <FIG> may be similar to steps <NUM>-<NUM> described above with respect to <FIG>. At <NUM>, PCF <NUM> may respond with an SM MBS Policy control Response (MBS Policy) with policies for the MBS Session ID. At 15a, after receiving a request to create a broadcast session at <NUM>, and requesting (at <NUM>) and obtaining (at <NUM>) policies for the broadcast session from PCF <NUM>, MB-SMF <NUM> may start a timer for the broadcast session to wait for an update of those policies from PCF <NUM> (at <NUM>, below).

Steps <NUM>-<NUM> in <FIG> may be similar to steps <NUM>-<NUM> described above with respect to <FIG>. At <NUM>, if PCF <NUM> determines updated policies for the MBS session in step <NUM>, PCF <NUM> may update the policy information at MB-SMF <NUM>. At <NUM>, if required by the updated policies, MB-SMF <NUM> may update MB-UPF <NUM>, accordingly. At <NUM>, upon expiration of the timer and/or upon receiving a policy update for that broadcast session from PCF <NUM>, MB-SMF <NUM> may signal to AMF <NUM> to request the allocation of resources for the transmission of the broadcast session. At 24a, upon receiving a policy update for that broadcast session from NEF/MBSF <NUM>, PCF <NUM> may also stop the timer. Steps <NUM>-<NUM> in <FIG> may also be similar to steps <NUM>-<NUM> described above with respect to <FIG>.

<FIG> illustrates an example of a flow diagram of a method that may be performed by a MB-SMF, such as NE <NUM> illustrated in <FIG>, according to various example embodiments.

At <NUM>, the MB-SMF may receive an Allocate TMGI Request () message from a NEF/MBSF, which may be similar to NE <NUM> illustrated in <FIG>, according to various example embodiments. At <NUM>, the MB-SMF may allocate TMGI(s) and return the TMGI(s) to the NEF/MBSF via Allocate TMGI Response (TMGI(s)).

At <NUM>, the MB-SMF may receive, from the NEF/MBSF, at least one multicast/broadcast session creation request comprising at least one indication of policy authorization for the multicast/broadcast session. In some example embodiments, an MBS Session Create Request (MBS Session ID, service type, TMGI allocation indication, MBS service area information, ingress transport address request indication) requesting the MB-SMF to reserve ingress resources for an MBS distribution session, and may provide MBS Session ID or request allocation, and indicate its service type (either multicast service or broadcast service). In the request to create a broadcast session, the request may indicate whether it will also provide a policy authorization for the broadcast session with a PCF, which may also be similar to NE <NUM> illustrated in <FIG>. The MBS Session Create Request may also indicate if the allocation of an ingress transport address is requested.

At <NUM>, if the MB-SMF is selected by the NEF/MBSF, and source specific multicast address is received, the MB-SMF may allocate TMGI, and the MB-SMF may update at least one NF profile to a NRF (such as NE <NUM> illustrated in <FIG>) with the serving MBS Session ID. In certain example embodiments, if TMGI is used to represent an MBS Session, the MB-SMF may not need to update the NRF if the TMGI range(s) supported by the MB-SMF are already included in the MB-SMF profile when the MB-SMF registers itself into the NRF. In response to the at least one indication of policy authorization for the broadcast session, at <NUM>, the MB-SMF may request, from a PCF (such as NE <NUM> in <FIG>), the creation of a policy control session for the multicast/broadcast session from at least one policy control function.

At <NUM>, the PCF may respond with an SM MBS Policy control Response (MBS Policy) with policies for the MBS Session ID.

At <NUM>, in response to the at least one indication of policy authorization for the multicast/broadcast session and the determination that the multicast/broadcast session is a broadcast session, the MB-SMF may defer at least one resource allocation request associated with the at least one broadcast session to at least one access and mobility management function until the reception of an update request in the policy control session.

At <NUM>, if PCC is not used, the MB-SMF may derive the required QoS parameters locally. The MB-SMF may select a MB-UPF and/or request it to reserve user plane ingress resources. If multicast transport of the MBS data towards RAN nodes is to be used, the MB-SMF may also request an MB-UPF to reserve for the outgoing data a tunnel endpoint and the related identifiers (source IP address, source specific multicast address and GTP Tunnel ID) and to forward data received at the user plane ingress resource using that tunnel endpoint. If ingress address is not requested, the MB-SMF may configure the MB-UPF to handle the multicast data distribution, and request the MB-UPF to join the multicast tree towards the content provider. The MB-UPF may also join the distribution tree of the content provider in the subsequent session establishment procedure.

At <NUM>, if requested, the MB-UPF may select an ingress address (IP address and port) and a tunnel endpoint for the outgoing data, and the MB-SMF may receive the ingress address. For broadcast communication, the MB-SMF may continue the procedure towards the AMF <NUM> (and/or an NG-RAN).

At <NUM>, the MB-SMF may indicate the possibly allocated ingress address to the NEF/MBSF. The MB-SMF may include TMGI if it is allocated. It also indicates the success or failure of reserving transmission resources.

At <NUM>, the MB-SMF may receive at least one policy update request in the policy control session from the at least one policy control function.

At <NUM>, if required by the updated policies, the MB-SMF may update the MB-UPF, accordingly. At <NUM>, when obtaining an MBS policy control update from the PCF at <NUM>, the MB-SMF may signal to the AMF to request the allocation of resources for the transmission of the broadcast session.

At <NUM>, the MB-SMF may receive, from the NEF/MBSF, at least one broadcast session creation request, such as an MBS Session Create Request (MBS Session ID, service type, TMGI allocation indication, MBS service area information, ingress transport address request indication) requesting the MB-SMF to reserve ingress resources for an MBS distribution session, and may provide MBS Session ID or request allocation, and indicate its service type (either multicast service or broadcast service). The MBS Session Create Request may also indicate if the allocation of an ingress transport address is requested.

At <NUM>, if the MB-SMF is selected by the NEF/MBSF, and source specific multicast address is received, the MB-SMF may allocate TMGI, and the MB-SMF may update at least one NF profile to a NRF (such as NE <NUM> illustrated in <FIG>) with the serving MBS Session ID. In certain example embodiments, if TMGI is used to represent an MBS Session, the MB-SMF may not need to update the NRF if the TMGI range(s) supported by the MB-SMF are already included in the MB-SMF profile when the MB-SMF registers itself into the NRF. At <NUM>, the MB-SMF may request the creation of a policy control session for the broadcast session from, such as by sending a MBS Policy control Create Request (MBS Session ID) to a PCF (such as NE <NUM> in <FIG>) with the MBS Session ID.

At <NUM>, from the at least one policy control function, the MB-SMF receives from the at least one policy control function, in response to the at least one request for creation of a policy control session, policy information comprising at least one indication requesting no resource allocation, for instance within an MBS Policy control Create reply message.

At <NUM>, when receiving a request for the establishment of policy control for a multicast session, the MB-SMF may receive from the PCF policies with an indication requesting no resource allocation in the reply. In response to the at least one indication requesting no resource allocation, the MB-SMF may defer at least one resource allocation request associated with the at least one broadcast session to at least one Access and Mobility Management Function until the reception of an update request in the a policy control session.

At <NUM>, if requested, the MB-UPF may select an ingress address (IP address and port) and a tunnel endpoint for the outgoing data, and the MB-SMF may receive the ingress address. For broadcast communication, the MB-SMF may continue the procedure towards the AMF (and/or an NG-RAN).

At <NUM>, the MB-SMF may receive at least one policy update request in the policy control session from the at least one policy control function comprising at least one indication requesting resource allocation. In certain embodiments, when obtaining a request for the creation of a policy authorization, for a broadcast session for which it already performs policy control towards the MB-SMF, the MB-SMF may receive from the PCF a policy update message even if no policies need to be changed.

At <NUM>, if required by the updated policies, the MB-SMF may update the MB-UPF, accordingly. At <NUM>, in response to the at least one indication requesting resource allocation, the MB-SMF may transmit at least one resource allocation request associated with at least one broadcast session to at least one Access and Mobility Management Function.

At <NUM>, the MB-SMF may receive, from the NEF/MBSF, at least one broadcast session creation request, for example, an MBS Session Create Request (MBS Session ID, service type, TMGI allocation indication, MBS service area information, ingress transport address request indication) requesting the MB-SMF to reserve ingress resources for an MBS distribution session, and may provide MBS Session ID or request allocation, and indicate its service type (either multicast service or broadcast service). The MBS Session Create Request may also indicate if the allocation of an ingress transport address is requested.

At <NUM>, if the MB-SMF is selected by the NEF/MBSF, and source specific multicast address is received, the MB-SMF may allocate TMGI, and the MB-SMF may update at least one NF profile to a NRF (such as NE <NUM> illustrated in <FIG>) with the serving MBS Session ID. In certain example embodiments, if TMGI is used to represent an MBS Session, the MB-SMF may not need to update the NRF if the TMGI range(s) supported by the MB-SMF are already included in the MB-SMF profile when the MB-SMF registers itself into the NRF. At <NUM>, the MB-SMF may request the creation of a policy control session for the broadcast session from at least one policy control function, for example, by sending a MBS Policy control create Request to a PCF (such as NE <NUM> in <FIG>) with the MBS Session ID to request the creation of a policy control session for the broadcast session. At <NUM>, the PCF may respond with an MBS Policy control create reply (MBS Policy) with policies for the MBS Session ID.

At <NUM>, in response to the broadcast session creation request, the MB-SMF may start at least one timer associated with at least one broadcast session.

At <NUM>, if PCC is not used, the MB-SMF may derive the required QoS parameters locally. The MB-SMF may select the MB-UPF and/or request it to reserve user plane ingress resources. If multicast transport of the MBS data towards RAN nodes is to be used, the MB-SMF may also request the MB-UPF to reserve for the outgoing data a tunnel endpoint and the related identifiers (source IP address, source specific multicast address and GTP Tunnel ID) and to forward data received at the user plane ingress resource using that tunnel endpoint. If ingress address is not requested, MB-SMF may configure the MB-UPF to handle the multicast data distribution, and request the MB-UPF to join the multicast tree towards the content provider. The MB-UPF may also join the distribution tree of the content provider in the subsequent session establishment procedure.

At <NUM>, if requested, the MB-UPF may select an ingress address (IP address and port) and a tunnel endpoint for the outgoing data, and the MB-SMF may receive the ingress address and tunnel endpoint. For broadcast communication, the MB-SMF may continue the procedure towards the AMF (and/or an NG-RAN).

At <NUM>, the MB-SMF may receive from the PCF a policy update message even if no policies need to be changed.

At <NUM>, if required by the updated policies, the MB-SMF may update the MB-UPF, accordingly. At <NUM>, upon one or more of the at least one timer expiring or receiving at least one policy update request in the policy control session from the at least one policy control function, the MB-SMF may transmit to at least one access and mobility management function, at least one resource allocation request associated with the at least one broadcast session. At <NUM>, the MB-SMF may stop the timer.

<FIG> illustrates an example of a flow diagram of a method that may be performed by a NEF-MBSF, such as NE <NUM> illustrated in <FIG>, according to various example embodiments.

At <NUM>, the NEF/MBSF may receive at least one request to create a multicast/broadcast session. At <NUM>, the NEF/MBSF may determine whether to create a policy authorization session for the multicast/broadcast session. In some embodiments, the determining whether to create a policy authorization session for the broadcast session is based on at least one of configured information indicating whether to create a policy authorization for all multicast/broadcast sessions and at least one description of the multicast/broadcast session in the received request to create the broadcast session. Additionally or alternatively, the determining determines to create a policy authorization session for the broadcast session in response to the description of the multicast/broadcast session in the received request to create the broadcast session comprising a plurality of data flows.

At <NUM>, the NEF/MBSF may request, from at least one multicast/broadcast session management function, a creation of the multicast/broadcast session. In response to determining to create a policy authorization session, the request for creation of the multicast/broadcast session may include at least one indication of policy authorization.

At <NUM>, in response to the determining to create a policy authorization session, the NEF/MBSF may request the creation of a policy authorization session for the multicast/broadcast session from at least one policy control function.

<FIG> illustrates an example of a flow diagram of a method that may be performed by a PCF, such as NE <NUM> illustrated in <FIG>, according to various example embodiments. At <NUM>, the PCF may receive, from an MB-SMF (which may be similar to NE <NUM> illustrated in <FIG>), at least one request for creation of a policy control session for a broadcast session. At <NUM>, the PCF may provide, in response to the at least one request for creation of a policy control session, policy information comprising at least one indication requesting no resource allocation. At <NUM>, in response to the request for creation of a policy control session, the PCF may start at least one timer.

At <NUM>, the PCF may receive at least one request for policy authorization associated to the at least one broadcast session.

At <NUM>, upon one or more of the at least one timer expiring or receiving at least one request for policy authorization associated to the at least one broadcast session, the PCF may transmit towards the multicast/broadcast session management function at least one request to update the policies for the policy control session comprising at least one indication requesting resource allocation.

At <NUM>, the PCF may, upon receiving at least one request for policy authorization associated at least one broadcast session, stop the at least one timer.

<FIG> illustrates an example of a system according to certain example embodiments. In one example embodiment, a system may include multiple devices, such as, for example, NE <NUM> and/or UE <NUM>.

NE <NUM> may be one or more of a base station, such as an eNB or gNB, a serving gateway, a server, and/or any other access node or combination thereof. Furthermore, NE <NUM> and/or UE <NUM> may be one or more of a citizens broadband radio service device (CBSD).

NE <NUM> may further comprise at least one gNB-CU, which may be associated with at least one gNB-DU. The at least one gNB-CU and the at least one gNB-DU may be in communication via at least one F1 interface, at least one Xn-C interface, and/or at least one NG interface via a 5GC.

UE <NUM> may include one or more of a mobile device, such as a mobile phone, smart phone, personal digital assistant (PDA), tablet, or portable media player, digital camera, pocket video camera, video game console, navigation unit, such as a global positioning system (GPS) device, desktop or laptop computer, single-location device, such as a sensor or smart meter, or any combination thereof.

NE <NUM> and/or UE <NUM> may include at least one processor, respectively indicated as <NUM> and <NUM>. Processors <NUM> and <NUM> may be embodied by any computational or data processing device, such as a central processing unit (CPU), application specific integrated circuit (ASIC), or comparable device. The processors may be implemented as a single controller, or a plurality of controllers or processors.

At least one memory may be provided in one or more of the devices, as indicated at <NUM> and <NUM>. The memory may be fixed or removable. The memory may include computer program instructions or computer code contained therein. Memories <NUM> and <NUM> may independently be any suitable storage device, such as a non-transitory computer-readable medium. A hard disk drive (HDD), random access memory (RAM), flash memory, or other suitable memory may be used. The memories may be combined on a single integrated circuit as the processor, or may be separate from the one or more processors. Furthermore, the computer program instructions stored in the memory, and which may be processed by the processors, may be any suitable form of computer program code, for example, a compiled or interpreted computer program written in any suitable programming language.

Processors <NUM> and <NUM>, memories <NUM> and <NUM>, and any subset thereof, may be configured to provide means corresponding to the various blocks of <FIG>. Although not shown, the devices may also include positioning hardware, such as GPS or micro electrical mechanical system (MEMS) hardware, which may be used to determine a location of the device. Other sensors are also permitted, and may be configured to determine location, elevation, velocity, orientation, and so forth, such as barometers, compasses, and the like.

As shown in <FIG>, transceivers <NUM> and <NUM> may be provided, and one or more devices may also include at least one antenna, respectively illustrated as <NUM> and <NUM>. The device may have many antennas, such as an array of antennas configured for multiple input multiple output (MIMO) communications, or multiple antennas for multiple RATs. Other configurations of these devices, for example, may be provided. Transceivers <NUM> and <NUM> may be a transmitter, a receiver, both a transmitter and a receiver, or a unit or device that may be configured both for transmission and reception.

The memory and the computer program instructions may be configured, with the processor for the particular device, to cause a hardware apparatus, such as UE, to perform any of the processes described above (i.e., <FIG>). Therefore, in certain example embodiments, a non-transitory computer-readable medium may be encoded with computer instructions that, when executed in hardware, perform a process such as one of the processes described herein. Alternatively, certain example embodiments may be performed entirely in hardware.

In certain example embodiments, an apparatus may include circuitry configured to perform any of the processes or functions illustrated in <FIG>. For example, circuitry may be hardware-only circuit implementations, such as analog and/or digital circuitry. In another example, circuitry may be a combination of hardware circuits and software, such as a combination of analog and/or digital hardware circuitry with software or firmware, and/or any portions of hardware processors with software (including digital signal processors), software, and at least one memory that work together to cause an apparatus to perform various processes or functions. In yet another example, circuitry may be hardware circuitry and or processors, such as a microprocessor or a portion of a microprocessor, that includes software, such as firmware, for operation. Software in circuitry may not be present when it is not needed for the operation of the hardware.

<FIG> illustrates an example of a <NUM> network and system architecture according to certain example embodiments. Shown are multiple network functions that may be implemented as software operating as part of a network device or dedicated hardware, as a network device itself or dedicated hardware, or as a virtual function operating as a network device or dedicated hardware. The NE and UE illustrated in <FIG> may be similar to NE <NUM> and UE <NUM>, respectively. The user plane function (UPF) may provide services such as intra-RAT and inter-RAT mobility, routing and forwarding of data packets, inspection of packets, user plane quality of service (QoS) processing, buffering of downlink packets, and/or triggering of downlink data notifications. The application function (AF) may primarily interface with the core network to facilitate application usage of traffic routing and interact with the policy framework.

Some example embodiments described herein may be described as follows:.

The configuration steps for MBS Session are used by the AF to start the MBS Session towards 5GC and consist of TMGI allocation and MBS session start procedures, and they apply to both multicast and broadcast communications unless otherwise stated. MBS session establishment/activation procedure may follow the MBS session configuration procedure per its service type (multicast or broadcast service) to reserve resources towards NG-RAN.

For broadcast communication, MBS Session establishment/start consists of radio resource reservation towards the NG-RAN. For multicast communication, the radio resource reservation is performed when there is UE join.

For both broadcast and multicast communication, the TMGI allocation may be separated from the MBS Session Establishment/Start procedure.

For multicast communication, TMGI allocation procedure may be applicable if TMGI is used as MBS Session ID.

Steps <NUM> to <NUM> may be optional and applicable if TMGI is used as MBS Session ID and required to be pre-allocated.

The PCF may determine whether the request is authorized.

If the request is authorized, the PCF derives the required QoS parameters based on the information provided by the NEF and determines whether this QoS is allowed (according to the PCF configuration for this Application).

If the request is not authorized or the required QoS is not allowed, the PCF may indicate so in the response to the NEF.

[Conditional] When obtaining a request for the creation of a policy authorization (signal <NUM>) for a broadcast session, for which it already performs policy control towards an MB-SMF, the PCF may provide a policy update to the MB-SMF; if no real policy update is required, the PCF may repeat previous policies or sends an empty update message.

[Conditional] If required by the updated policies, the MB-SMF may update the MB-UPF accordingly.

When obtaining an MBS policy control update from the PCF (signal <NUM>) for a broadcast session, the MB-SMF may continue the procedure towards the AMF and NG-RAN as specified in clause <NUM>. <NUM> to request the allocation of resources to for the transmission of the broadcast session.

[Optional] If the MBSF decides to use an MBSTF, the MBSF may provide the received ingress address in step <NUM> towards the MBSTF as DL destination, and requests the MBSTF to allocate the user plane ingress resources.

[Conditional on step <NUM>] If requested, MBSTF may select an ingress address (IP address and port) and provides it to NEF/MBSF.

The NEF/MBSF-C may include the ingress address if allocated and other parameters (e.g. TMGI) to the AF by MBS Session Response ([TMGI], [Allocated ingress address]) message. If MBS Session ID is not provided in step <NUM>, or the MBS Session ID is source specific multicast address, the NEF/MBSF may provide the allocated TMGI. If AF requests the allocation of an ingress transport address, the message may also includes the allocated ingress address.

Same as step <NUM>. The AF may also perform a service announcement at this stage.

For multicast communication, depending on configuration, UE join request can be accepted from this point onward.

For example, the usage of the phrases "various embodiments," "certain embodiments," "some embodiments," or other similar language throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with an example embodiment may be included in at least one example embodiment. Thus, appearances of the phrases "in various embodiments," "in certain embodiments," "in some embodiments," or other similar language throughout this specification does not necessarily all refer to the same group of example embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more example embodiments.

Additionally, if desired, the different functions or procedures discussed above may be performed in a different order and/or concurrently with each other. Furthermore, if desired, one or more of the described functions or procedures may be optional or may be combined. As such, the description above should be considered as illustrative of the principles and teachings of certain example embodiments, and not in limitation thereof.

Claim 1:
A method, comprising:
receiving (<NUM>, <NUM>), by a multicast/broadcast session management function (<NUM>, <NUM>, <NUM>), at least one multicast/broadcast session creation request comprising at least one indication of policy authorization for a broadcast session, wherein the at least one indication of policy authorization comprises at least one indication that indicates whether a network exposure function or a multicast/broadcast service function will provide a policy authorization for the broadcast session;
requesting (<NUM>, <NUM>), by the multicast/broadcast session management function (<NUM>, <NUM>, <NUM>), in response to the at least one indication of policy authorization for the broadcast session, the creation of a policy control session for the multicast/broadcast session from at least one policy control function (<NUM>, <NUM>, <NUM>).