WO2022034050A1

WO2022034050A1 - Mbs with individual qos option

Info

Publication number: WO2022034050A1
Application number: PCT/EP2021/072225
Authority: WO
Inventors: Joakim ÅKESSON; Jie LING; Hans Bertil RÖNNEKE; Paul Schliwa-Bertling; Alexander Vesely; Juying GAN; Maria Belen PANCORBO MARCOS; John Camilo SOLANO ARENAS
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2020-08-13
Filing date: 2021-08-10
Publication date: 2022-02-17

Abstract

Systems and methods are disclosed herein for configuring and applying User Equipment (UE) specific Quality of Service(s) (QoS(s)) for an individual UE(s) in a Multicast/Broadcast Service (MBS) session.

Description

MBS WITH INDIVIDUAL QoS OPTION

Technical Field

The present disclosure relates to Multicast/Broadcast Service (MBS) and Quality of Service (QoS).

Background

The Third Generation Partnership Project (3GPP) has earlier developed the Multicast/Broadcast Multimedia Subsystem (MBMS) (3GPP Technical Specification (TS) 23.246 v16.1.0) for third generation (3G) networks for video multicast/broadcasting and streaming services and later introduced the evolved MBMS (eMBMS) for the Evolved Packet System (EPS). In Rel-13 and Rel-14, the MBMS system has been updated to support new services such as Public Safety, Cellular Internet of Things (CloT), and Vehicle to Anything (V2X).

The scope of a new Release-17 study in 3GPP SA2 working group is to study both multicast requirements and use cases for CloT, Public Safety, V2X, etc., and dedicated broadcasting requirements and use cases. The study targets the Fifth Generation (5G) Release 17 and the New Radio (NR) radio access. The study results so far have been documented in the 3GPP Technical Report (TR) 23.757 V0.4.0.

Multicast / Broadcast services are so far not supported on 5G NR. With the enhanced characteristics of the 5G NR (e.g. short delays, bandwidth, etc.), it is believed Mission Critical Services (e.g., Mission Critical Push To Talk (MCPTT), Mission Critical Data (MCData), and Mission Critical Video (MCVideo), as well as VTX services, will show an enhanced and much better performance on 5G NR. Different types of MBS sessions require different Quality of Service (QoS) characteristics.

Summary

Certain challenges exist with existing MBMS solutions. In the EPS based Mission Critical Services, leveraging the Group Communication System Enablers (GCSE) architecture, there was a possibility for the application server to choose between unicast and multicast delivery of the service on a per user basis (e.g., on a per User Equipment (UE) basis). In 5G Multicast/Broadcast Service (5MBS), there is an ambition to do the 5MBS service so efficient and reliable that there is no need to choose unicast delivery. But there is a concern from e.g. the Public Safety community that, when using 5MBS, it is not possible to prioritize certain key users within a group with higher QoS requirements - they will all be treated equally. At very high concentration of users in bad radio conditions, this may result in a degraded service for all users including users with higher importance.

Solutions to the aforementioned and/or other challenges are disclosed herein. In some embodiments, on top of a default QoS applicable for a 5MBS session, individual QoS(s) can be applied to individual users (e.g., individual UEs) in the 5MBS session (e.g. raise priority for key users in the session). In one embodiment:

1 . An Application Function (AF) (e.g., an AF associated to the 5MBS session) sends a request for an individual QoS towards a Policy Control Function (PCF) of the 3GPP network. The requested individual QoS is a requested QoS towards an individual user, or UE, in the 5MBS session.

2. In this case, the requested individual QoS is coupled to the 5MBS session through a session identifier (e.g., a Temporary Mobile Group Identity (TMGI)) - e.g., a new Information Element (IE).

3. The Core network propagates this IE (e.g., IE containing the requested individual QoS) to the 5G Radio Access Network (which is referred to as a Next Generation Radio Access Network (NG- RAN)).

4. The NG-RAN uses the individual QoS with respect to the individual user in the 5MBS session. As an example, at high load, where the RAN for example must limit the uplink (UL) feedback from participating UEs (e.g. HARQ), the RAN prioritizes certain users primarily based on individual QoS (e.g., and secondly on other mechanisms available in NR such as beam forming, Point-to-Point delivery of 5MBS content, or other proprietary algorithms based on e.g. radio conditions).

Embodiments of the proposed solution enable individual treatment of certain UEs in the RAN even for a multicast session, based on instructions from the application layer. This allows increased (or decreased) priority for some UEs in the multicast session.

Embodiments of the proposed solution may allow the application server (with detailed intelligence on user based roles and priority, normally not known in the network at that detailed level) to control that certain users are given QoS treatment for their MBS bearer (PTM or PTP) on par with using a dedicated unicast flow for these users. This can be done with optimized/reduced impact on network capacity. If the same priority was instead applied using legacy unicast based procedures, it would not be possible to provide the same capacity e.g. at high concentration of UEs in poor radio conditions. Brief Description of the Drawings

The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

Figure 1 illustrates one example of a cellular communications system according to some embodiments of the present disclosure;

Figures 2 and 3 illustrate example embodiments in which the cellular communication system of Figure 1 is a Fifth Generation (5G) System (5GS);

Figure 4 illustrates an Application Function (AF) session with a Quality of Service (QoS) update procedure in accordance with one embodiment of the present disclosure

Figure 5 illustrates a User Equipment (UE) UE or network requested Protocol Data Unit (PDU) Session Modification (non-roaming and roaming with local breakout) procedure in accordance with one embodiment of the present disclosure;

Figure 6 illustrates the operation of the cellular communications system of Figure 1 in accordance with embodiments of the present disclosure;

Figure 7 is a schematic block diagram of a network node according to some embodiments of the present disclosure;

Figure 8 is a schematic block diagram that illustrates a virtualized embodiment of the network node of Figure 7 according to some embodiments of the present disclosure; and

Figure 9 is a schematic block diagram of the network node of Figure 7 according to some other embodiments of the present disclosure.

Detailed Description

The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.

Radio Node: As used herein, a “radio node” is either a radio access node or a wireless communication device.

Radio Access Node: As used herein, a “radio access node” or “radio network node” or “radio access network node” is any node in a Radio Access Network (RAN) of a cellular communications network that operates to wirelessly transmit and/or receive signals. Some examples of a radio access node include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a Third Generation Partnership Project (3GPP) Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP Long Term Evolution (LTE) network), a high-power or macro base station, a low-power base station (e.g., a micro base station, a pico base station, a home eNB, or the like), a relay node, a network node that implements part of the functionality of a base station or a network node that implements a gNB Distributed Unit (gNB-DU)) or a network node that implements part of the functionality of some other type of radio access node.

Core Network Node: As used herein, a “core network node” is any type of node in a core network or any node that implements a core network function. Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Exposure Function (SCEF), a Home Subscriber Server (HSS), or the like. Some other examples of a core network node include a node implementing a Access and Mobility Function (AMF), a User Plane Function (UPF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Network Slice Selection Function (NSSF), a Network Exposure Function (NEF), a Network Function (NF) Repository Function (NRF), a Policy Control Function (PCF), a Unified Data Management (UDM), or the like.

Communication Device: As used herein, a “communication device” is any type of device that has access to an access network. Some examples of a communication device include, but are not limited to: mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or Personal Computer (PC). The communication device may be a portable, hand-held, computer-comprised, or vehicle-mounted mobile device, enabled to communicate voice and/or data via a wireless or wireline connection.

Wireless Communication Device: One type of communication device is a wireless communication device, which may be any type of wireless device that has access to (i.e., is served by) a wireless network (e.g., a cellular network). Some examples of a wireless communication device include, but are not limited to: a User Equipment device (UE) in a 3GPP network, a Machine Type Communication (MTC) device, and an Internet of Things (loT) device. Such wireless communication devices may be, or may be integrated into, a mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or PC. The wireless communication device may be a portable, hand-held, computer-comprised, or vehicle-mounted mobile device, enabled to communicate voice and/or data via a wireless connection. Network Node: As used herein, a “network node” is any node that is either part of the RAN or the core network of a cellular communications network/system.

Transmission/Reception Point (TRP): In some embodiments, a TRP may be either a network node, a radio head, a spatial relation, or a Transmission Configuration Indicator (TCI) state. A TRP may be represented by a spatial relation or a TCI state in some embodiments. In some embodiments, a TRP may be using multiple TCI states.

Note that the description given herein focuses on a 3GPP cellular communications system and, as such, 3GPP terminology or terminology similar to 3GPP terminology is oftentimes used. However, the concepts disclosed herein are not limited to a 3GPP system.

Note that, in the description herein, reference may be made to the term “cell”; however, particularly with respect to 5G NR concepts, beams may be used instead of cells and, as such, it is important to note that the concepts described herein are equally applicable to both cells and beams.

Figure 1

Figure 1 illustrates one example of a cellular communications system 100 in which embodiments of the present disclosure may be implemented. In the embodiments described herein, the cellular communications system 100 is a 5G system (5GS) including a Next Generation RAN (NG-RAN) and a 5G Core (5GC); however, embodiments of the solution disclosed herein are not limited thereto. In this example, the RAN includes base stations 102-1 and 102-2, which in the 5GS include NR base stations (gNBs) and optionally next generation eNBs (ng-eNBs) (e.g., LTE RAN nodes connected to the 5GC), controlling corresponding (macro) cells 104-1 and 104-2. The base stations 102-1 and 102-2 are generally referred to herein collectively as base stations 102 and individually as base station 102. Likewise, the (macro) cells 104-1 and 104-2 are generally referred to herein collectively as (macro) cells 104 and individually as (macro) cell 104. The RAN may also include a number of low power nodes 106-1 through 106-4 controlling corresponding small cells 108-1 through 108-4. The low power nodes 106-1 through 106- 4 can be small base stations (such as pico or femto base stations) or Remote Radio Heads (RRHs), or the like. Notably, while not illustrated, one or more of the small cells 108-1 through 108-4 may alternatively be provided by the base stations 102. The low power nodes 106-1 through 106-4 are generally referred to herein collectively as low power nodes 106 and individually as low power node 106. Likewise, the small cells 108-1 through 108-4 are generally referred to herein collectively as small cells 108 and individually as small cell 108. The cellular communications system 100 also includes a core network 110, which in the 5G System (5GS) is referred to as the 5GC. The base stations 102 (and optionally the low power nodes 106) are connected to the core network 110. The base stations 102 and the low power nodes 106 provide service to wireless communication devices 112-1 through 112-5 in the corresponding cells 104 and 108. The wireless communication devices 112-1 through 112-5 are generally referred to herein collectively as wireless communication devices 112 and individually as wireless communication device 112. In the following description, the wireless communication devices 112 are oftentimes UEs, but the present disclosure is not limited thereto.

Figure 2

Figure 2 illustrates a wireless communication system represented as a 5G network architecture composed of core Network Functions (NFs), where interaction between any two NFs is represented by a point-to-point reference point/interface. Figure 2 can be viewed as one particular implementation of the system 100 of Figure 1.

Seen from the access side the 5G network architecture shown in Figure 2 comprises a plurality of UEs 112 connected to either a RAN 102 or an Access Network (AN) as well as an AMF 200. Typically, the R(AN) 102 comprises base stations, e.g. such as eNBs or gNBs or similar. Seen from the core network side, the 5GC NFs shown in Figure 2 include a NSSF 202, an AUSF 204, a UDM 206, the AMF 200, a SMF 208, a PCF 210, and an Application Function (AF) 212.

Reference point representations of the 5G network architecture are used to develop detailed call flows in the normative standardization. The N1 reference point is defined to carry signaling between the UE 112 and AMF 200. The reference points for connecting between the AN 102 and AMF 200 and between the AN 102 and UPF 214 are defined as N2 and N3, respectively. There is a reference point, N11 , between the AMF 200 and SMF 208, which implies that the SMF 208 is at least partly controlled by the AMF 200. N4 is used by the SMF 208 and UPF 214 so that the UPF 214 can be set using the control signal generated by the SMF 208, and the UPF 214 can report its state to the SMF 208. N9 is the reference point for the connection between different UPFs 214, and N14 is the reference point connecting between different AMFs 200, respectively. N15 and N7 are defined since the PCF 210 applies policy to the AMF 200 and SMF 208, respectively. N12 is required for the AMF 200 to perform authentication of the UE 112. N8 and N10 are defined because the subscription data of the UE 112 is required for the AMF 200 and SMF 208.

The 5GC network aims at separating UP and CP. The UP carries user traffic while the CP carries signaling in the network. In Figure 2, the UPF 214 is in the UP and all other NFs, i.e., the AMF 200, SMF 208, PCF 210, AF 212, NSSF 202, AUSF 204, and UDM 206, are in the CP. Separating the UP and CP guarantees each plane resource to be scaled independently. It also allows UPFs to be deployed separately from CP functions in a distributed fashion. In this architecture, UPFs may be deployed very close to UEs to shorten the Round Trip Time (RTT) between UEs and data network for some applications requiring low latency. The core 5G network architecture is composed of modularized functions. For example, the AMF 200 and SMF 208 are independent functions in the CP. Separated AMF 200 and SMF 208 allow independent evolution and scaling. Other CP functions like the PCF 210 and AUSF 204 can be separated as shown in Figure 2. Modularized function design enables the 5GC network to support various services flexibly.

Each NF interacts with another NF directly. It is possible to use intermediate functions to route messages from one NF to another NF. In the CP, a set of interactions between two NFs is defined as service so that its reuse is possible. This service enables support for modularity. The UP supports interactions such as forwarding operations between different UPFs.

Figure 3

Figure 3 illustrates a 5G network architecture using service-based interfaces between the NFs in the CP, instead of the point-to-point reference points/interfaces used in the 5G network architecture of Figure 2. However, the NFs described above with reference to Figure 2 correspond to the NFs shown in Figure 3. The service(s) etc. that a NF provides to other authorized NFs can be exposed to the authorized NFs through the service-based interface. In Figure 3 the service based interfaces are indicated by the letter “N” followed by the name of the NF, e.g. Namf for the service based interface of the AMF 200 and Nsmf for the service based interface of the SMF 208, etc. The NEF 300 and the NRF 302 in Figure 3 are not shown in Figure 2 discussed above. However, it should be clarified that all NFs depicted in Figure 2 can interact with the NEF 300 and the NRF 302 of Figure 3 as necessary, though not explicitly indicated in Figure 2.

Some properties of the NFs shown in Figures 2 and 3 may be described in the following manner. The AMF 200 provides UE-based authentication, authorization, mobility management, etc. A UE 112 even using multiple access technologies is basically connected to a single AMF 200 because the AMF 200 is independent of the access technologies. The SMF 208 is responsible for session management and allocates Internet Protocol (IP) addresses to UEs. It also selects and controls the UPF 214 for data transfer. If a UE 112 has multiple sessions, different SMFs 208 may be allocated to each session to manage them individually and possibly provide different functionalities per session. The AF 212 provides information on the packet flow to the PCF 210 responsible for policy control in order to support QoS. Based on the information, the PCF 210 determines policies about mobility and session management to make the AMF 200 and SMF 208 operate properly. The AUSF 204 supports authentication function for UEs or similar and thus stores data for authentication of UEs or similar while the UDM 206 stores subscription data of the UE 112. The Data Network (DN), not part of the 5GC network, provides Internet access or operator services and similar. An NF may be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g., a cloud infrastructure.

[0047] In some embodiments of the solution described herein, on top of a default QoS applicable for a MBS session (e.g., a 5MBS session in the example embodiments described herein), individual QoS(s) can be applied to individual users (e.g., individual UEs) in the session (e.g. to raise priority for key users in the session). In one embodiment:

Embodiments of the proposed solution may allow the application server (with detailed intelligence on user based roles and priority, normally not known in the network at that detailed level) to control that certain users are given QoS treatment for their MBS bearer (PTM or PTP) on par with using a dedicated unicast flow for these users. This can be done with optimized/reduced impact on network capacity. If the same priority was instead applied using legacy unicast based procedures, it would not be possible to provide the same capacity e.g. at high concentration of UEs in poor radio conditions.

Now, some example embodiments related to the 5GS will be described.

Embodiments of the solution introduce support for a UE specific handling of the MBS Session to ensure the necessary QoS level required for the service and the role of the UE in the context of that MBS Session, e.g. introducing a QoS profile for the handling of the MBS Session in case the UE is used by e.g. the leader of a group of first responders or someone in immediate peril. Such QoS profile can be used by the RAN to enable specific Radio Resource Management (RRM) measures to maintain the quality of the MBS Session data delivery, as such handling may not be feasible to be applied to all potential members of the group in case of e.g. very high concentration of users at cell border.

Embodiments of the solution disclosed herein support Key Issue #4 in 3GPP TR 23.757, which aims at studying QoS requirements, the need for different QoS levels, how support it and which entity determines the QoS level, which entity enforces it and how. In some embodiments, the AF determines the need for the QoS levels and then RAN enforces it. As such, the enforcement is a shared responsibility between SA2 and RAN.

In one embodiment, the process is as follows:

- The UE participates in the MBS Session.

- The UE communicates with an Application Server using application layer signaling over a PDU Session. The IP address of the PDU Session, and by that the UE, is known in the AF.

- AF provides UE specific service requirements for the MBS Session of the user using the already existing PDU Session to the appropriate PCF. The information provided by the AF includes, besides the service requirement (QoS), a reference to the MBS Session, e.g. the TMGI.

In regard to QoS level support for Multicast and Broadcast communication services, different multicast and broadcast communication services have potentially different QoS requirements. For this, the QoS framework of TS 23.501 , clause 5.7 is taken as baseline. QoS requirements include, e.g., packet error rate, delay budget, MBR or GBR, and/or the like. In one embodiment, systems and methods are disclosed for configuring and using different QoS levels for a subset of members in in a group (e.g., individual QoS level for at least one of the individual users, or UEs, in the MBS group).

In one embodiment, the AF provides a specific priority for a MBS group member. This embodiment is based on the baseline architecture 2 in Annex A.2 of 3GPP TR 23.757 but might also be applied to architecture 1 in Annex A.1 of 3GPP TR 23.757. By addressing the aspects of Key Issue #4, it is complementary to other solutions to Key Issues #1 and #7 and possibly also to other solutions to Key Issue #4.

Any time during an ongoing MBS session or any time after TMGI allocation, the AF (e.g., AF 212) may provide QoS information to the PCF (e.g., PCF 210), including specific QoS requirements for the MBS service data flows of a specific UE (e.g., a specific UE 112). In RAN, this may result e.g. in applying HARQ for the PTM delivery to the UE even in a loaded resource situation where RAN cannot do this to all UEs, or other RAN NR specific handling. Note that the term “QoS” should in embodiments of the solution be interpreted more generally such as the term “reliability.” Based on the received information, the PCF provides PDU Session policy control information to the SMF (e.g., SMF 208) including the specific QoS requirements for the MBS service data flows of the UE, but that information may be transparently conveyed by the PCF and the 5GC to the RAN. The SMF provides the QoS requirements for the MBS service data flows i.e. MBS session ID and MBS session priority to the RAN. Note that the specific priority is set on bearer level and not on flow level.

Note that the PCF provisions PDU Session policy control information to the SMF of the PDU Session known by the AF (e.g. used for application level signaling) and the SMF conveys the QoS information to the NR RAN.

Figure 4

Figure 4 illustrates an AF session with a QoS update procedure in accordance with one embodiment of the present disclosure. The below description specifies updates to TS 23.502 clause 4.15.6.6a "AF session with required QoS update procedure". Proposed changes are shown below as italic bold text. Note that the procedure “Setting up an AF session with required QoS procedure” is also impacted with similar changes as defined below. The steps of the process of Figure 4 are as follows:

Step 1 : For an established AF session with required QoS, the AF (e.g., AF 212) may send a Nnef_AFsessionWithQoS_Update request message (Transaction Reference ID, [MBS Session Priority, MBS Session ID]) to NEF (e.g., 300) for requesting prioritization of the MBS Session of a particular UE (e.g., UE 112).

The MBS Session ID may be a list of MBS Session IDs with associated MBS Session Priority for each MBS Session ID. A UE may be a member of multiple groups, and the AF may want to set priorities for all the UE’s groups in a single message.

Steps 2-7: Steps unchanged compared to TS 23.502 clause 4.15.6.6a.

Subsequently, as a result of the above, a PDU Session modification is triggered by update of the policy by the PCF (e.g., PCF 210) using the PCF initiated SM policy association modification.

- PDU Modification procedure of the PDU Session associated with the MBS Session provides the MBS Session Priority and the MBS Session ID (e.g. the TMGI) to the RAN.

- By reception of the MBS Session ID/TMGI, the RAN identifies that the QoS profile is applied on the handling of the MBS Session for that UE.

Figure 5

Figure 5 illustrates a UE or network requested PDU Session Modification (non-roaming and roaming with local breakout) procedure in accordance with one embodiment of the present disclosure. The below description specifies updates to TS 23.502 clause 4.3.3.2 "UE or network requested PDU Session Modification (non-roaming and roaming with local breakout)". Proposed changes are shown below as italic bold text. The steps of the procedure of Figure 5 are as follows:

Step 1 : The procedure may be triggered by following events:

• Step 1 a: Step unchanged compared to TS 23.502 clause 4.3.3.2.

• Step 1 b: (SMF requested modification) The PCF (e.g., PCF 210) performs a PCF initiated SM Policy Association Modification procedure as defined in clause 4.16.5.2 to notify SMF (208) about the modification of policies.

If the UE specific QoS level for an MBS Session is requested, the PCF generates the QoS policy for the corresponding MBS Session, and provides the policy in the PDU session policy control information with the reference to the MBS Session to the SMF in this step.

• Steps 1c-1f: Steps unchanged compared to TS 23.502 clause 4.3.3.2.

Steps 2-3a: Steps unchanged compared to TS 23.502 clause 4.3.3.2.

Step 3b: For SMF requested modification, the SMF invokes Namf_Communication_N1 N2MessageTransfer ([N2 SM information] (PDU Session ID, QFI(s), QoS Profile(s), [Alternative QoS Profile(s)], Session-AMBR, [CN Tunnel lnfo(s)], QoS Monitoring indication, QoS Monitoring reporting frequency, [TSCAI(s)], MBS Session Priority, MBS Session ID), N1 SM container (PDU Session Modification Command (PDU Session ID, QoS rule(s), QoS Flow level QoS parameters if needed for the QoS Flow(s) associated with the QoS rule(s), QoS rule operation and QoS Flow level QoS parameters operation, Session-AMBR))).

If the PCF generates a QoS policy for the corresponding MBS Session, and provides the policy in the PDU session policy control information with the reference to the MBS Session to the SMF in step 1b, the SMF forwards the MBS Session Priority and the associated MBS Session ID to the RAN.

Steps 3c-4: Steps unchanged compared to TS 23.502 clause 4.3.3.2.

Step 5: The (R)AN may issue AN specific signaling exchange with the UE that is related with the information received from SMF. For example, in the case of a NG-RAN, an RRC Connection Reconfiguration may take place with the UE modifying the necessary (R)AN resources related to the PDU Session or if only N1 SM container is received in step 4 from AMF, RAN transports only the N1 SM container to the UE.

The (R)AN may consider the updated CN assisted RAN parameters tuning to reconfigure the AS parameters. As part of this, the N1 SM container is provided to the UE. If the N1 SM container includes a Port Management Information Container then the UE provides the container to DS-TT.

If RAN received MBS Session Priority associated with MBS Session ID, RAN uses this information for local RRM policies to ensure forthat UE the QoS level for the respective MBS Session(s) is provided.

Steps 6-13: Steps unchanged compared to TS 23.502 clause 4.3.3.2.

In summary, in some embodiments, the AF (e.g., AF 212) provides specific QoS to the PCF (e.g., PCF 210). A new IE is added to the existing procedure for PDU Session QoS update.

In some embodiments, the PCF provides PDU session policy control information including the MBS Session ID and MBS priority that is propagated to NG-RAN using existing procedure for PDU Session QoS update.

In some embodiments, the SMF (e.g., SMF 208) determines the new QoS profiles and provides to the NG-RAN. In one embodiment, the new QoS profile is also stored in the SMF to be conveyed at subsequent transitions to CM-CONNECTED mode.

In some embodiments, the NG-RAN links the new QoS profile to a specific MB Session based on a TMGI in the QoS profile. In some embodiments, the NG-RAN uses the new QoS profile to control QoS of a MB Session for a specific user or member of the MB Session.

Above, embodiments of the solution are described which are based on a PDU session coupled to the 5MBS session. In other embodiments this coupling is not needed, i.e. using a PDU Session of the UE that is known by the AF, to convey QoS to NG-RAN (NR) for an MB Session that this same UE has joined. An IE indicating the 5MBS session (using e.g. the TMGI) could also be used by RAN to apply the request to the correct 5MBS session.

Embodiments of how the RAN applies the individual QoS for a user, or UE, in a MBS session are as follows. Reliability of the 5MBS point to multipoint (PTM) delivery of the multicast service is increased by allowing UEs to send uplink (UL) feedback including measurement reports and HARQ feedback. With this feedback RAN can make intelligent decisions how to schedule the traffic including e.g. modulation and coding schemes, optional beam forming, retransmissions etc.

At very high concentration of UEs, especially if they are in poor radio conditions, uplink resources may be scarce. RAN then needs to make intelligent decisions to limit the feedback from the participating UEs of the 5MBS sessions. In a legacy solution this is likely to be based mainly on radio conditions. The solution described in this IvD provides information from the application layer to RAN about UEs that should not be discriminated (or be less discriminated) if RAN must limit the uplink feedback due to scarce resources. Or (if the QoS requirements are lower than default QoS of the 5MBS session) it could also provide information about UEs that may be more discriminated.

In another embodiment RAN is instead (of providing individual feedback treatment in a PTM session) serving the UE with an individual point-to-point (PTP) transmission.

Figure 6

Figure 6 illustrates the operation of the cellular communications system 100 in accordance with at least some aspects of the embodiments described above. Note that while not all aspects of the embodiments described above are repeated here in the description of Figure 6, it should be understood that they are all applicable. As illustrated, a core NF, which in this particular example is the PCF 210, receives, directly from AF 212 or indirectly from the AF 212 (e.g., via the NEF 300), information that indicates QoS requirements for a particular MBS session for a particular UE 112 (e.g., information that indicates QoS requirements for one or more MBS service data flows of the particular UE 112) (step 600). The PCF 210 then triggers application of the QoS requirements for the particular MBS for the particular UE 112 in the RAN (step 602). More specifically in this particular example, in step 602, the PCF 210 sends PDU session policy control information to the SMF 208 (step 602A). The session policy control information comprises information that indicates the QoS requirements for the particular MBS session for the particular UE 112 (e.g., indicates QoS requirements for one or more MBS service data flows of the particular UE 112).

The SMF 208 receives the PDU session policy control information from the PCF in step 602 and provides information that indicates the QoS requirements for the particular MBS session for the particular UE 112 to a RAN node (i.e., a base station 102 in this example) (step 604). In one embodiment, the information provided from the SMF 208 to the RAN node comprises a MBS session priority and an MBS Session ID of the particular MBS session. The RAN node then performs one or more actions based on the indicated QoS requirements for the particular MBS session for the particular UE (step 606). For example, the one or more actions may comprise using the indicated QoS requirements for the particular MBS session for the particular UE for local RRM policies to ensure that, for the particular UE 112, the QoS requirements are satisfied for the MBS session.

Figure 1

Figure 7 is a schematic block diagram of a network node 700 according to some embodiments of the present disclosure. Optional features are represented by dashed boxes. The network node 700 may be, for example, a network node that implements a core NF such as, e.g., the PCF 210 or the SMF 208 as described herein. As illustrated, the network node 700 includes one or more processors 704 (e.g., Central Processing Units (CPUs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), and/or the like), memory 706, and a network interface 708. The one or more processors 704 are also referred to herein as processing circuitry. The one or more processors 704 operate to provide one or more functions of the network node 700 as described herein (e.g., one or more functions of a core NF such as, e.g., the PCF 210 or the SMF 208 as described herein). In some embodiments, the function(s) are implemented in software that is stored, e.g., in the memory 706 and executed by the one or more processors 704.

Figure 8

Figure 8 is a schematic block diagram that illustrates a virtualized embodiment of the network node 700 according to some embodiments of the present disclosure. Again, optional features are represented by dashed boxes.

As used herein, a “virtualized” network node is an implementation of the network node 700 in which at least a portion of the functionality of the network node 700 is implemented as a virtual component(s) (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network(s)). As illustrated, in this example, the network node 700 includes one or more processing nodes 800 coupled to or included as part of a network(s) 802. Each processing node 800 includes one or more processors 804 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 806, and a network interface 808.

In this example, functions 810 of the network node 700 described herein (e.g., one or more functions of a core NF such as, e.g., the PCF 210 or the SMF 208 as described herein) are implemented at the one or more processing nodes 800 or distributed across the two or more of the processing nodes 800 in any desired manner. In some particular embodiments, some or all of the functions 810 of the network node 700 described herein (e.g., one or more functions of a core NF such as, e.g., the PCF 210 or the SMF 208 as described herein) are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment(s) hosted by the processing node(s) 800.

In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of the network node 700 or a node (e.g., a processing node 800) implementing one or more of the functions 810 of the network node 700 in a virtual environment according to any of the embodiments described herein is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory). Figure 9

Figure 9 is a schematic block diagram of the network node 700 according to some other embodiments of the present disclosure. The network node 700 includes one or more modules 900, each of which is implemented in software. The module(s) 900 provide the functionality of the network node 700 described herein (e.g., one or more functions of a core NF such as, e.g., the PCF 210 or the SMF 208 as described herein). This discussion is equally applicable to the processing node 800 of Figure 8 where the modules 900 may be implemented at one of the processing nodes 800 or distributed across multiple processing nodes 800.

Some Embodiments

Some of the embodiments described above may be summarized in the following enumerated manner:

1 . A method performed by core network function, NF, for User Equipment, UE, specific Quality of Service, QoS, level configuration and application for a User Equipment, UE, in a Multicast/Broadcast System, MBS, session, the method comprising: receiving (Fig. 4, step 1; 600), directly or indirectly from an Application Function, AF, (212), information that indicates QoS requirements for a particular MBS session for a particular UE (e.g., indicates QoS requirements for one or more MBS service data flows of the particular UE); triggering (Fig. 5, step 1 b; 602) application of the QoS requirements for the particular MBS for the particular UE in a radio access network, RAN.

2. The method of embodiment 1 wherein the core NF is a Policy and Control Function, PCF, (210) in a core network of the cellular communications system (100).

3. The method of embodiment 2 wherein triggering (Fig. 5, step 1 b; 602) application of the QoS requirements for the particular MBS for the particular UE in the RAN comprises providing (Fig. 5, step 1 b; 602A) Protocol Data Unit, PDU, session policy control information to a Session Management Function, SMF, (208) in the core network, the session policy control information comprising information that indicates the QoS requirements for the particular MBS session for the particular UE (e.g., indicates QoS requirements for one or more MBS service data flows of the particular UE).

4. The method of any one of embodiment 1 to 3 wherein the information received from the AF comprises an identifier associated to the particular MBS session. 5. The method of embodiment 4 wherein the identifier associated to the particular MBS session is a Temporary Mobile Group Identity, TMGI, associated to the particular MBS session.

6. The method of any one of embodiment 1 to 5 wherein the MBS session is a Fifth Generation, 5G, MBS session.

7. The method of any one of embodiment 1 to 6 wherein the RAN is a Next Generation RAN, NG- RAN, and the core network is a Fifth Generation Core, 5GC.

8. A core network function, NF, for User Equipment, UE, specific Quality of Service, QoS, level configuration and application for a User Equipment, UE, in a Multicast/Broadcast System, MBS, session, the core NF adapted to: receive (Fig. 4, step 1; 600), directly or indirectly from an Application Function (212), information that indicates QoS requirements for a particular MBS session for a particular UE (e.g., indicates QoS requirements for one or more MBS service data flows of the particular UE); trigger (Fig. 5, step 1 b; 602) application of the QoS requirements for the particular MBS for the particular UE in a radio access network, RAN.

9. The core NF of embodiment 8 wherein the core NF is a Policy and Control Function, PCF, (210) in a core network of the cellular communications system (100).

10. The core NF of embodiment 9 wherein, in order to trigger (Fig. 5, step 1 b; 602) application of the QoS requirements for the particular MBS for the particular UE in the RAN, the PCF is further adapted to provide (Fig. 5, step 1 b; 602) Protocol Data Unit, PDU, session policy control information to a Session Management Function, SMF, (208) in the core network, the session policy control information comprising information that indicates the QoS requirements for the particular MBS session for the particular UE (e.g., indicates QoS requirements for one or more MBS service data flows of the particular UE).

11. A network node (700) for implementing a core network function, NF, for User Equipment, UE, specific Quality of Service, QoS, level configuration and application for a User Equipment, UE, in a Multicast/Broadcast System, MBS, session, the network node (700) comprising processing circuitry (704; 804) configured to cause the network node (700) to: receive (Fig. 4, step 1; 600), directly or indirectly from an Application Function (212), information that indicates QoS requirements for a particular MBS session for a particular UE (e.g., indicates QoS requirements for one or more MBS service data flows of the particular UE); trigger (Fig. 5, step 1 b; 602) application of the QoS requirements for the particular MBS for the particular UE in a radio access network, RAN.

12. The core NF of embodiment 11 wherein the core NF is a Policy and Control Function, PCF, (210) in a core network of the cellular communications system (100).

13. The core NF of embodiment 12 wherein, in order to trigger (Fig. 5, step 1 b; 602) application of the QoS requirements for the particular MBS for the particular UE in the RAN, the processing circuitry (704; 804) is further configured to cause the network node (700) to provide (Fig. 5, step 1 b; 602) Protocol Data Unit, PDU, session policy control information to a Session Management Function, SMF, (208) in the core network, the session policy control information comprising information that indicates the QoS requirements for the particular MBS session for the particular UE (e.g., indicates QoS requirements for one or more MBS service data flows of the particular UE).

14. The core NF of any one of embodiment 11 to 13 wherein the core NF is further adapted to perform the method of any one of embodiment 4 to 7.

15. A method performed in a cellular communications system (100) for User Equipment, UE, specific Quality of Service, QoS, level configuration and application for a User Equipment, UE, in a Multicast/Broadcast System, MBS, session, the method comprising:

• at a Policy and Control Function, PCF, (210) in a core network of the cellular communications system (100): o receiving (Fig. 4, step 1 ; 600), directly or indirectly from an Application Function (212), information that indicates QoS requirements for a particular MBS session for a particular UE (e.g., indicates QoS requirements for one or more MBS service data flows of the particular UE); and o providing (Fig. 5, step 1 b; 602A) Protocol Data Unit, PDU, session policy control information to a Session Management Function, SMF, (208) in the core network, the session policy control information comprising information that indicates the QoS requirements for the particular MBS session for the particular UE (e.g., indicates QoS requirements for one or more MBS service data flows of the particular UE); and

• at the SMF (208): o receiving (Fig. 5, step 1 B; 602) the PDU session policy control information from the PCF (210); and o providing (Fig. 5, step 3b; 604) information that indicates the QoS requirements for the particular MBS session for the particular UE to a RAN node (102) in a RAN of the cellular communications system (100).

16. The method of embodiment 15 further comprising, at the RAN node (102), performing (606) one or more actions based on the indicated QoS requirements for the particular MBS session for the particular UE.

17. The method of embodiment 16 wherein the one or more actions comprise using the indicated QoS requirements for the particular MBS session for the particular UE for local RRM policies to ensure that, for the particular UE, the QoS requirements are satisfied for the MBS session.

18. The method of embodiment 16 or 17 wherein the one or more actions comprise allowing measurement reports and/or HARQ feedback from the particular UE even during uplink congestion when at least some other UEs in the MBS session are blocked from uplink feedback (e.g., measurement reports and/or HARQ feedback).

19. The method of any one of embodiment 16 to 18 wherein the one or more actions comprise switching to PTP delivery for the particular UE.

20. The method of any one of embodiment 15 to 19 wherein the information provided from the SMF (208) to the RAN node (102) comprises a MBS session priority and an MBS Session ID of the particular MBS session.

21 . The method of any one of embodiment 15 to 20 wherein the information provided from the SMF (208) to the RAN node (102) comprises an identifier associated to the particular MBS session.

22. The method of embodiment 21 wherein the identifier associated to the particular MBS session is a Temporary Mobile Group Identity, TMGI, associated to the particular MBS session. 23. The method of any one of embodiment 15 to 22 wherein the MBS session is a Fifth Generation, 5G, MBS session.

24. The method of any one of embodiment 15 to 23 wherein the RAN is a Next Generation RAN, NG- RAN, and the core network is a Fifth Generation Core, 5GC.

Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

While processes in the figures may show a particular order of operations performed by certain embodiments of the present disclosure, it should be understood that such order is exemplary (e.g., alternative embodiments may perform the operations in a different order, combine certain operations, overlap certain operations, etc.).

At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).

• 3GPP Third Generation Partnership Project

• 5G Fifth Generation

• 5GC Fifth Generation Core

• 5GS Fifth Generation System

• AF Application Function

• AMF Access and Mobility Function • AN Access Network

• AUSF Authentication Server Function

• CPU Central Processing Unit

• DN Data Network

• DSP Digital Signal Processor

• gNB New Radio Base Station

• LTE Long Term Evolution

• MB Multicast Broadcast

• MBS Multicast Broadcast Service

• NEF Network Exposure Function

• NF Network Function

• NR New Radio

• NRF Network Function Repository Function

• NSSF Network Slice Selection Function

• PCF Policy Control Function

• QoS Quality of Service

• RAN Radio Access Network

• SCEF Service Capability Exposure Function

• SMF Session Management Function

• TMGI Temporary Mobile Group Identity

• UDM Unified Data Management

• UE User Equipment

• UPF User Plane Function

Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.

Claims

Claims What is claimed is:

1 . A method performed by core network function, NF, for User Equipment, UE, specific Quality of Service, QoS, level configuration and application for a User Equipment, UE, in a Multicast/Broadcast System, MBS, session, the method comprising: receiving (Fig. 4, step 1 ; 600), directly or indirectly from an Application Function, AF, (212), information that indicates QoS requirements for a particular MBS session for a particular UE (e.g., indicates QoS requirements for one or more MBS service data flows of the particular UE); triggering (Fig. 5, step 1 b; 602) application of the QoS requirements for the particular MBS for the particular UE in a radio access network, RAN.

2. The method of claim 1 wherein the core NF is a Policy and Control Function, PCF, (210) in a core network of the cellular communications system (100).

3. The method of claim 2 wherein triggering (Fig. 5, step 1 b; 602) application of the QoS requirements for the particular MBS for the particular UE in the RAN comprises providing (Fig. 5, step 1 b; 602A) Protocol Data Unit, PDU, session policy control information to a Session Management Function, SMF, (208) in the core network, the session policy control information comprising information that indicates the QoS requirements for the particular MBS session for the particular UE (e.g., indicates QoS requirements for one or more MBS service data flows of the particular UE).

4. The method of any of claims 1 to 3 wherein the information received from the AF comprises an identifier associated to the particular MBS session.

5. The method of claim 4 wherein the identifier associated to the particular MBS session is a Temporary Mobile Group Identity, TMGI, associated to the particular MBS session.

6. The method of any of claims 1 to 5 wherein the MBS session is a Fifth Generation, 5G, MBS session.

7. The method of any of claims 1 to 6 wherein the RAN is a Next Generation RAN, NG-RAN, and the core network is a Fifth Generation Core, 5GC.

8. A core network function, NF, for User Equipment, UE, specific Quality of Service, QoS, level configuration and application for a User Equipment, UE, in a Multicast/Broadcast System, MBS, session, the core NF adapted to: receive (Fig. 4, step 1 ; 600), directly or indirectly from an Application Function (212), information that indicates QoS requirements for a particular MBS session for a particular UE (e.g., indicates QoS requirements for one or more MBS service data flows of the particular UE); trigger (Fig. 5, step 1 b; 602) application of the QoS requirements for the particular MBS for the particular UE in a radio access network, RAN.

9. The core NF of claim 8 wherein the core NF is a Policy and Control Function, PCF, (210) in a core network of the cellular communications system (100).

10. The core NF of claim 9 wherein, in order to trigger (Fig. 5, step 1 b; 602) application of the QoS requirements for the particular MBS for the particular UE in the RAN, the PCF is further adapted to provide (Fig. 5, step 1 b; 602) Protocol Data Unit, PDU, session policy control information to a Session Management Function, SMF, (208) in the core network, the session policy control information comprising information that indicates the QoS requirements for the particular MBS session for the particular UE (e.g., indicates QoS requirements for one or more MBS service data flows of the particular UE).

11. A network node (700) for implementing a core network function, NF, for User Equipment, UE, specific Quality of Service, QoS, level configuration and application for a User Equipment, UE, in a Multicast/Broadcast System, MBS, session, the network node (700) comprising processing circuitry (704; 804) configured to cause the network node (700) to: receive (Fig. 4, step 1 ; 600), directly or indirectly from an Application Function (212), information that indicates QoS requirements for a particular MBS session for a particular UE (e.g., indicates QoS requirements for one or more MBS service data flows of the particular UE); trigger (Fig. 5, step 1 b; 602) application of the QoS requirements for the particular MBS for the particular UE in a radio access network, RAN.

12. The core NF of claim 11 wherein the core NF is a Policy and Control Function, PCF, (210) in a core network of the cellular communications system (100).

13. The core NF of claim 12 wherein, in order to trigger (Fig. 5, step 1 b; 602) application of the QoS requirements for the particular MBS for the particular UE in the RAN, the processing circuitry (704; 804) is further configured to cause the network node (700) to provide (Fig. 5, step 1 b; 602) Protocol Data Unit, PDU, session policy control information to a Session Management Function, SMF, (208) in the core network, the session policy control information comprising information that indicates the QoS requirements for the particular MBS session for the particular UE (e.g., indicates QoS requirements for one or more MBS service data flows of the particular UE).

14. The core NF of any of claims 11 to 13 wherein the core NF is further adapted to perform the method of any of claims 4 to 7.

16. The method of claim 15 further comprising, at the RAN node (102), performing (606) one or more actions based on the indicated QoS requirements for the particular MBS session for the particular UE.

17. The method of claim 16 wherein the one or more actions comprise using the indicated QoS requirements for the particular MBS session for the particular UE for local RRM policies to ensure that, for the particular UE, the QoS requirements are satisfied for the MBS session.

18. The method of claim 16 or 17 wherein the one or more actions comprise allowing measurement reports and/or HARQ feedback from the particular UE even during uplink congestion when at least some other UEs in the MBS session are blocked from uplink feedback (e.g., measurement reports and/or HARQ feedback).

19. The method of any of claims 16 to 18 wherein the one or more actions comprise switching to PTP delivery for the particular UE.

20. The method of any of claims 15 to 19 wherein the information provided from the SMF (208) to the RAN node (102) comprises a MBS session priority and an MBS Session ID of the particular MBS session.

21 . The method of any of claims 15 to 20 wherein the information provided from the SMF (208) to the RAN node (102) comprises an identifier associated to the particular MBS session.

22. The method of claim 21 wherein the identifier associated to the particular MBS session is a Temporary Mobile Group Identity, TMGI, associated to the particular MBS session.

23. The method of any of claims 15 to 22 wherein the MBS session is a Fifth Generation, 5G, MBS session.

24. The method of any of claims 15 to 23 wherein the RAN is a Next Generation RAN, NG-RAN, and the core network is a Fifth Generation Core, 5GC.