Managing transmission and reception of multicast and broadcast services

Abstract

A method in a base station for managing communications of a multicast and / or broadcast service (MBS) includes causing (1402) establishment of a session for communicating MBS data packets from a core network (CN) to a user equipment (UE). The method also includes communicating (1404) configuration parameters associated with the session to the UE. Further, the method includes communicating (1406) the MBS data packets to the UE in accordance with the configuration parameters.

Description

Technical Field

[0001] This disclosure relates to wireless communications, and more specifically, to the establishment and / or modification of radio resources that enable transmission and / or reception for one or more multicast and / or broadcast services (MBS). Background Technology

[0002] The background description provided herein is intended to provide a general overview of the context of this disclosure. To the extent described in this background section, the work of the inventors currently identified, and aspects of the description that may not conform to the prior art at the time of filing, are neither explicitly nor implicitly considered to be prior art of this disclosure.

[0003] In telecommunications systems, the Packet Data Convergence Protocol (PDCP) sublayer of the radio protocol stack provides services such as user plane data delivery, encryption, and integrity protection. For example, the PDCP layer, defined for the Evolved Universal Terrestrial Radio Access (EUTRA) radio interface (see 3GPP specification TS 36.323) and New Radio (NR) (see 3GPP specification TS 38.323), provides the ordering of Protocol Data Units (PDUs) in the uplink direction (from the User Equipment, also known as the UE, to the base station) and the downlink direction (from the base station to the UE). Furthermore, the PDCP sublayer provides services for Signaling Radio Bearers (SRBs) to the Radio Resource Control (RRC) sublayer. The PDCP sublayer also provides Data Radio Bearer (DRB) services to the Serving Data Adaptation Protocol (SDAP) sublayer or protocol layers such as the Internet Protocol (IP) layer, Ethernet layer, and Internet Control Message Protocol (ICMP) layer. Generally, the UE and base station can use SRBs to exchange RRC messages and Non-Access Stratum (NAS) messages, and can use DRBs to transmit data on the user plane.

[0004] In some scenarios, a UE can simultaneously utilize the resources of multiple nodes (e.g., components of a base station, distributed base station, or decentralized base station) in a radio access network (RAN) interconnected via backhaul. This type of connection is called Multiple Radio Dual Connectivity (MR-DC) when these network nodes support different Radio Access Technologies (RATs). When operating in an MR-DC, the cells associated with a base station operating as a primary node (MN) define a Primary Cell Group (MCG), and the cells associated with a base station operating as a secondary node (SN) define a Secondary Cell Group (SCG). The MCG covers the primary cell (PCell) and zero or more secondary cells (SCells), while the SCG covers the primary and secondary cells (PSCells) and zero or more SCells. The UE communicates with the MN (via the MCG) and the SN (via the SCG). In other scenarios, the UE utilizes the resources of one base station at a time, i.e., Single Connectivity (SC). In an SC, the UE only communicates with the MN (via the MCG). One base station and / or the UE determines that the UE should establish a radio connection with another base station. For example, a base station can determine to hand over the UE to a second base station and initiate a handover process. In other scenarios, the UE can simultaneously utilize the resources of RAN nodes interconnected via backhaul (e.g., components of a single base station, distributed base stations, or decentralized base stations).

[0005] UEs can use several types of SRBs and DRBs. The so-called SRB1 resource carries RRC messages, which in some cases include NAS messages on the Dedicated Control Channel (DCCH), and the SRB2 resource supports RRC messages including recorded measurement information or NAS messages, which also pass through the DCCH but have a lower priority than the SRB1 resource. More generally, SRB1 and SRB2 resources allow the UE and MN to exchange MN-related RRC messages as well as embedded SN-related RRC messages, and can also be referred to as MCG SRBs. SRB3 resources allow the UE and SN to exchange SN-related RRC messages, and can be referred to as SCG SRBs. Separate SRBs allow the UE to exchange RRC messages directly with the MN via lower-level resources of the MN and SN. Furthermore, a DRB that terminates at the MN and uses only the lower-level resources of the MN can be referred to as an MCG DRB, a DRB that terminates at the SN and uses only the lower-level resources of the SN can be referred to as an SCG DRB, and a DRB that terminates at either the MN or SN but uses the lower-level resources of both the MN and SN can be referred to as a separate DRB. A DRB that terminates at MN but only uses lower-level resources of SN can be called an MN-terminated SCG DRB. A DRB that terminates at SN but only uses lower-level resources of MN can be called an SN-terminated MCG DRB.

[0006] In both single-connectivity (SC) and DC operations, a UE can perform handover procedures to switch from one cell to another. These procedures involve messaging between the RAN node and the UE (e.g., RRC signaling and preparation). Depending on the scenario, the UE can handover from the serving base station's cell to the target cell of the target base station, or from the cell of the first distributed unit (DU) of the serving base station to the target cell of the second DU of the same base station. In DC scenarios, a UE can perform PSCell change procedures to change its PS cell. These procedures involve messaging between the RAN node and the UE (e.g., RRC signaling and preparation). Depending on the scenario, the UE can perform a PSCell change from the serving SN to the target SN, or from the source DU of the base station to the target DU of the same base station. Furthermore, the UE can perform handover or PSCell change within a cell for synchronous reconfiguration.

[0007] Base stations operating under the fifth-generation (5G) New Radio (NR) requirements support significantly larger bandwidths than fourth-generation (4G) base stations. Therefore, the 3rd Generation Partnership Project (3GPP) has proposed, for Release 15, that User Equipment Units (UEs) support 100MHz bandwidth in Frequency Range 1 (FR1) and 400MHz bandwidth in Frequency Range 2 (FR2). Due to the relatively wide bandwidth of typical carriers, 3GPP has also proposed, for Release 17, that 5G NR base stations can provide multicast and / or broadcast services (MBS) to UEs, which is useful in many content delivery applications such as transparent IPv4 / IPv6 multicast delivery, IPTV, wireless software delivery, group communications, IoT applications, V2X applications, and emergency messages related to public safety.

[0008] However, in some cases, it is unclear how the UE and the base station should configure and manage the flow of MBS packets. Summary of the Invention

[0009] The RAN and / or UE implement the techniques of this disclosure to manage the transmission and reception of MBS. The UE may perform a session establishment procedure (e.g., PDU session establishment procedure) with the core network (CN) via the RAN's base station. The base station may use a DRB associated with the session to transmit MBS data packets to the UE. The DRB may be a unicast DRB (i.e., a dedicated DRB assigned to the UE) or a multicast DRB (also referred to herein as "MRB").

[0010] During session establishment, the base station can send configuration parameters to the UE to configure a first DRB associated with the session. The UE can use this first DRB to transmit an MBS request for MBS service to the base station. Alternatively, the UE can transmit the MBS request via an SRB, or the base station can receive the request from the CN to transmit the MBS service to the UE. In response to the MBS request, the base station can transmit MBS data packets for MBS service via the first DRB, or the base station can configure a second DRB associated with the session and transmit MBS data packets to the UE via the second DRB.

[0011] In some implementations, the base station can use a first or second DRB associated with the session to transmit unicast data packets associated with the unicast service to the UE. Furthermore, in some implementations, the CN can establish multiple PDU sessions for multiple UEs via the base station. The base station can configure one or more DRBs for each PDU session. In some cases, the base station can transmit the same configuration parameters to a first subset of UEs and transmit MBS data packets to the UEs according to the configuration parameters (i.e., the configuration parameters can be used for a shared multicast DRB). For a second subset of UEs, the base station can transmit unicast configuration parameters to each corresponding UE (i.e., the configuration parameters can be used for the corresponding unicast DRB).

[0012] An example embodiment of these technologies is a method for managing MBS communications implemented in a base station. This method can be executed by processing hardware and includes prompting the establishment of a session for transmitting MBS data packets from the CN to the UE. The method also includes transmitting configuration parameters associated with the session to the UE. Furthermore, the method includes transmitting MBS data packets to the UE according to the configuration parameters.

[0013] Another example embodiment of these technologies is a base station that includes processing hardware and is configured to implement the methods described above.

[0014] Another example embodiment of these technologies is a method for managing MBS reception implemented in a UE. This method can be executed by processing hardware and includes establishing a session for receiving MBS data packets from a CN via a base station. The method also includes receiving configuration parameters associated with the session from the base station and receiving MBS data packets according to the configuration parameters.

[0015] Another example embodiment of these technologies is a UE that includes processing hardware and is configured to implement the methods described above. Attached Figure Description

[0016] Figure 1A This is a block diagram of an example system in which the RAN and / or UE implement the techniques of this disclosure to manage the transmission and reception of MBS.

[0017] Figure 1B This is a block diagram of an example base station, where the central unit (CU) and distributed units (DU) can be... Figure 1A Operating within the system;

[0018] Figure 2 This is a block diagram of an example protocol stack. Based on this protocol stack, Figure 1A The UE can be with Figure 1A Communicate with base stations;

[0019] Figure 3A This is a message passing diagram for an example scenario, in which the base station establishes a PDU session between the core network (CN) and the UE, and transmits MBS data packets to the UE via the data radio bearer (DRB) configured during the PDU session establishment process;

[0020] Figure 3B Is with Figure 3A The message passing diagram is similar to that of the scenario, but in this case, the base station transmits MBS data packets to the UE via the DRB associated with the PDU session and configured after the PDU establishment process;

[0021] Figure 3C Is with Figure 3B The message passing diagram is similar to that of the example scenario, but in this case, the PDU session is used for MBS transmission and unicast transmission to the UE.

[0022] Figure 4 This is a message passing diagram for an example scenario, in which the base station establishes PDU sessions with multiple UEs for MBS transmission to the UEs;

[0023] Figure 5 This is a message passing diagram for an example scenario, in which a distributed base station including DU and CU establishes a PDU session between CN and UE for MBS transmission to UE, wherein DU forwards multicast configuration parameters to CU;

[0024] Figure 6A It is possible Figure 1A A flowchart of an example method implemented in a UE, which includes receiving MBS packets from the RAN using configuration parameters associated with a PDU session;

[0025] Figure 6B Is with Figure 6A The flowchart is similar to that of the example method, but this method also includes receiving MBS packets using a second configuration parameter associated with the PDU session;

[0026] Figure 7A It is possible Figure 1AA flowchart of an example method implemented in a UE, the method comprising receiving MBS packets according to unicast configuration parameters associated with a PDU session, and subsequently receiving MBS packets according to multicast configuration parameters associated with a PDU session;

[0027] Figure 7B Is with Figure 7A The flowchart is similar to that of the example method, but in which the UE receives MBS packets according to multicast configuration parameters and then receives MBS packets according to unicast configuration parameters.

[0028] Figure 7C Is with Figure 7A The flowchart is similar to that of the example method, but in which the UE receives MBS packets for the first MBS service according to unicast configuration parameters and receives MBS packets for the second MBS service according to multicast configuration parameters.

[0029] Figure 8 It is possible Figure 1A A flowchart of an example method implemented in a UE, the method including transmitting a request for MBS service through a first DRB associated with a PDU session, and receiving MBS packets of MBS through a second DRB associated with a PDU session;

[0030] Figure 9A It is possible Figure 1A A flowchart of an example method implemented in a base station, the method including transmitting MBS packets to the UE according to configuration parameters associated with a PDU session;

[0031] Figure 9B Is with Figure 9A The flowchart is similar to that of the example method, but the method also includes transmitting MBS packets for the second MBS service to the UE according to the second configuration parameters associated with the PDU session;

[0032] Figure 10A It is possible Figure 1A A flowchart of an example method implemented in a base station, the method comprising transmitting MBS packets of MBS service to the UE according to unicast configuration parameters associated with a PDU session, and subsequently transmitting MBS packets of MBS to the UE according to multicast configuration parameters associated with a PDU session;

[0033] Figure 10B Is with Figure 10A The flowchart is similar to that of the example method, but in which the base station transmits MBS packets according to multicast configuration parameters and then transmits MBS packets to the UE according to unicast configuration parameters;

[0034] Figure 10C Is with Figure 10AThe flowchart is similar to that of the example method, but in which the base station transmits MBS packets for the first MBS service according to unicast configuration parameters and transmits MBS packets for the second MBS service according to multicast configuration parameters.

[0035] Figure 11 It is possible Figure 1A A flowchart of an example method implemented in a base station, the method including receiving a request for MBS service from a UE via a first DRB associated with a PDU session, and transmitting MBS packets of MBS via a second DRB associated with a PDU session;

[0036] Figure 12 It is possible Figure 1B The flowchart shows an example method implemented in the CU, which includes requesting multicast configuration parameters for the UE from the DU and receiving multicast configuration parameters from the DU.

[0037] Figure 13 It is possible Figure 1B A flowchart of an example method implemented in the DU, which includes receiving a request for multicast configuration parameters for the UE from the CU and transmitting the multicast configuration parameters to the CU;

[0038] Figure 14 It is possible Figure 1A A flowchart of an example method for managing MBS communications implemented in a base station; and

[0039] Figure 15 It is possible Figure 1A The flowchart shows an example method implemented in the UE for managing MBS reception. Detailed Implementation

[0040] Generally, the technology disclosed herein allows a UE to receive MBS information via radio resources allocated by a base station of the RAN. For this purpose, the base station can configure different radio resources in one or more overlapping cells to multicast or broadcast (“multicast” or “broadcast” is interchangeably referred to as “transmit”) MBS data (and associated control information) and / or unicast (“unicast” is interchangeably referred to as “transmit”) non-MBS data (and associated control information) to one or more UEs on the downlink (DL). The base station can also unicast MBS data (and associated control information) to the UE on the UE’s dedicated DRB. One or more UEs can transmit (i.e., unicast) non-MBS data to the base station on the uplink (UL).

[0041] Therefore, the base station of this disclosure can be configured with one or more radio bearers to transmit MBS information (i.e., MBS data packets and / or control information) to the UE. The radio bearer carrying the MBS information to the UE can be a unicast DRB (i.e., a dedicated DRB for the UE) or a multicast DRB (i.e., a DRB that can be shared by multiple UEs, also known as an MBS radio bearer or MRB). For example, the base station can transmit unicast configuration parameters or multicast configuration parameters to the UE to configure the UE to receive MBS information via a unicast DRB or a multicast DRB, respectively. As used in this disclosure, the term "DRB" can refer to either a unicast DRB or a multicast DRB, unless otherwise specifically indicated.

[0042] Figure 1A An example wireless communication system 100 is depicted that can implement the MBS operation technology of this disclosure. The wireless communication system 100 includes UE 102A and UE 102B, and base stations 104, 106A, and 106B connected to a radio access network (RAN) (e.g., RAN 105) connected to a core network (CN) 110. For ease of reading, UE 102 is used herein to refer to UE 102A, UE 102B, or both UE 102A and UE 102B, unless otherwise stated. Base stations 104, 106A, and 106B can be any suitable type of base station, such as an evolved Node B (eNB), a next-generation eNB (ng-eNB), or a 5G Node B (gNB). As a more specific example, base station 104 can be an eNB or a gNB, and base stations 106A and 106B can be gNBs.

[0043] Base station 104 supports cell 124, base station 106A supports cell 126A, and base station 106B supports cell 126B. Cell 124 partially overlaps with cells 126A and 126B, allowing UE 102 to communicate with base station 104 while simultaneously communicating with either base station 106A or 106B (or detecting or measuring signals from base stations 106A and 106B). For example, this overlap allows UE 102 to handover between cells (e.g., from cell 124 to cell 126A or 126B) or base stations (e.g., from base station 104 to base station 106A or 106B) before experiencing a radio link failure. Furthermore, this overlap enables various dual-connectivity (DC) scenarios discussed below. For example, UE 102 can communicate with base station 104 (operating as MN) and base station 106A (operating as SN) in the DC, and after completing the handover to base station 106B, it can communicate with base station 106B (operating as MN). As another example, UE 102 can communicate with base station 104 (operating as MN) and base station 106A (operating as SN) in the DC, and after completing the SN change, it can communicate with base station 104 (operating as MN) and base station 106B (operating as SN).

[0044] More specifically, when UE 102 is in the DC with base station 104 and base station 106A, base station 104 operates as a primary eNB (MeNB), primary ng-eNB (Mng-eNB), or primary gNB (MgNB), and base station 106A operates as a secondary gNB (SgNB) or secondary ng-eNB (Sng-eNB).

[0045] In non-MBS (i.e., unicast) operation, UE 102 may use radio bearers (e.g., DRB or SRB) that terminate at different times to MN (e.g., base station 104) or SN (e.g., base station 106A). For example, after a handover or SN change to base station 106B, UE 102 may use radio bearers (e.g., DRB or SRB) that terminate at different times to base station 106B. When communicating on radio bearers in the UL (from UE 102 to the base station) and / or DL ​​(from the base station to UE 102) directions, UE 102 may apply one or more security keys. In non-MBS operation, UE 102 transmits data to the base station via radio bearers on (i.e., within) the cell's uplink BWP, and / or receives data from the base station via radio bearers on the cell's DL BWP. The UL BWP may be an initial UL BWP or a dedicated UL BWP, and the DL BWP may be an initial DL BWP or a dedicated DL BWP. UE102 can receive paging, system information, multiple public warning messages, or random access responses on the DL BWP. In this non-MBS operation, UE102 can be in a connected state. Alternatively, if UE102 supports small packet transmission in an idle or inactive state, then UE102 can be in an idle or inactive state.

[0046] In MBS operation, UE 102 can use radio bearers (e.g., DRB or MRB) that terminate at different times to an MN (e.g., base station 104) or an SN (e.g., base station 106A). For example, after a handover or SN change to base station 106B, UE 102 can use radio bearers (e.g., DRB or MRB) that terminate at different times to base station 106B, which can be either an MN or an SN. The base station can use the radio bearers to transmit application-level messages, such as security keys, to UE 102. In some implementations, the base station (e.g., MN or SN) can transmit MBS data to UE 102 via dedicated radio resources (i.e., radio resources dedicated to UE 102) (e.g., via DRB or MRB). In such implementations, the base station can apply one or more security keys to protect the integrity of the MBS data and / or encrypt the MBS data, and transmit encrypted and / or integrity-protected MBS data to UE 102 via dedicated radio resources. Accordingly, when receiving MBS data on a radio bearer in the downlink direction (from the base station to UE 102), UE 102 can apply one or more security keys to decrypt the MBS data and / or check the integrity of the MBS data. In other implementations, the base station (e.g., MN or SN) can transmit MBS data to UE 102 via common radio resources (i.e., radio resources shared by UE 102 and (a plurality of) other UEs) or a cell DL BWP (e.g., via DRB or MRB). The DL BWP can be an initial DL BWP, a dedicated DL BWP, or an MBS DL BWP (i.e., a DL BWP dedicated to MBS or not used for unicast). In such an implementation, the base station can suppress the application of security keys to MBS data and transmit MBS data on the radio bearer. Accordingly, UE 102 can omit the application of security keys to MBS data received on the radio bearer. UE 102 can apply application-level security keys received from CN 110 or the MBS server to MBS data received on the radio bearer.

[0047] Base station 104 includes processing hardware 130, which may include one or more general-purpose processors (e.g., central processing unit (CPU)) and computer-readable memory storing machine-readable instructions that can be executed on one or more general-purpose processors and / or dedicated processing units. Figure 1AIn the example implementation, the processing hardware 130 includes a base station MBS controller 132 configured to manage or control the transmission of MBS information received from CN 110 or an edge server. For example, the base station MBS controller 132 may be configured to support Radio Resource Control (RRC) configuration, procedures, and messaging associated with MBS procedures, and / or support necessary operations as described below. The processing hardware 130 may include a base station non-MBS controller 134 configured to manage or control one or more RRC configurations and / or RRC procedures when the base station 104 operates as an MN or SN during non-MBS operation.

[0048] Base station 106A includes processing hardware 140, which may include one or more general-purpose processors (e.g., CPUs) and computer-readable memory storing machine-readable instructions that can be executed on the general-purpose processors and / or dedicated processing units. Figure 1A In the example implementation, the processing hardware 140 includes a base station MBS controller 142 configured to manage or control the transmission of MBS information received from CN 110 or an edge server. For example, the base station MBS controller 142 may be configured to support RRC configuration, procedures, and messages associated with MBS procedures, and / or support necessary operations, as described below. The processing hardware 140 may include a base station non-MBS controller 144 configured to manage or control one or more RRC configurations and / or RRC procedures when the base station 106A operates as an MN or SN during non-MBS operation. Although not explicitly stated in the text... Figure 1A As shown, however, base station 106B may include processing hardware similar to the processing hardware 130 of base station 104 or the processing hardware 140 of base station 106A.

[0049] UE 102 includes processing hardware 150, which may include one or more general-purpose processors (e.g., CPUs) and computer-readable memory storing machine-readable instructions that can be executed on the general-purpose processors and / or dedicated processing units. Figure 1AIn an example implementation, the processing hardware 150 includes a UE MBS controller 152 configured to manage or control the reception of MBS information. For example, the UE MBS controller 152 may be configured to support RRC configuration, procedures, and messaging associated with MBS procedures, and / or support necessary operations as described below. The processing hardware 150 may include a UE non-MBS controller 154 configured to manage or control one or more RRC configurations and / or RRC procedures, according to any implementation discussed below, when the UE 102 communicates with the MN and / or SN during non-MBS operation.

[0050] CN 110 can be either the Evolution Packet Core (EPC) 111 or the 5th Generation Core (5GC) 160, both of which are... Figure 1A As depicted in the diagram, base station 104 can be an eNB supporting an S1 interface for communication with EPC 111, an ng-eNB supporting an NG interface for communication with 5GC 160, or a gNB supporting an NR radio interface and an NG interface for communication with 5GC 160. Base station 106A can be an EUTRA-NR DC (EN-DC) gNB (en-gNB) with an S1 interface to EPC 111, an en-gNB not connected to EPC 111, a gNB supporting an NR radio interface and an NG interface to 5GC 160, or an ng-eNB supporting an EUTRA radio interface and an NG interface to 5GC 160. To directly exchange messages with each other during the scenarios discussed below, base stations 104, 106A, and 106B can support X2 or Xn interfaces.

[0051] Among other components, EPC 111 may include a Serving Gateway (SGW) 112, a Mobility Management Entity (MME) 114, and a Packet Data Network Gateway (PGW) 116. SGW 112 is typically configured to deliver user plane packets related to audio calls, video calls, internet traffic, etc., and MME 114 is configured to manage authentication, registration, paging, and other related functions. PGW 116 provides connectivity from the UE to one or more external packet data networks, such as the Internet and / or an Internet Protocol (IP) Multimedia Subsystem (IMS) network. 5GC 160 includes a User Plane Function (UPF) 162 and Access and Mobility Management (AMF) 164, and / or Session Management Function (SMF) 166. UPF 162 is typically configured to deliver user plane packets related to audio calls, video calls, internet traffic, etc., AMF 164 is configured to manage authentication, registration, paging, and other related functions, and SMF 166 is configured to manage PDU sessions. UPF 162, AMF 164, and / or SMF 166 can be configured to support MBS. For example, SMF 166 can be configured to manage or control MBS transmissions, configure UPF 162 and / or RAN 105 for MBS streams, and / or manage or configure (multiple) MBS sessions or (multiple) PDU sessions for UE 102's MBS. UPF 162 is configured to deliver MBS data packets related to audio, video, internet traffic, etc., to RAN 105. UPF 162 and / or SMF 166 can be configured for unicast services and MBS, or for MBS only.

[0052] Typically, the wireless communication network 100 may include any suitable number of base stations supporting NR cells and / or EUTRA cells. More specifically, the EPC 111 or 5GC 160 may connect to any suitable number of base stations supporting NR cells and / or EUTRA cells. Although the examples below specifically relate to particular CN types (EPC, 5GC) and RAT types (5G NR and EUTRA), in general, the techniques disclosed herein can also be applied to other suitable radio access and / or core network technologies, such as, for example, sixth-generation (6G) radio access and / or 6G core networks or 5G NR-6G DC.

[0053] In different configurations or scenarios of the wireless communication system 100, base station 104 can operate as a MeNB, Mng-eNB, or MgNB; base station 106B can operate as a MeNB, Mng-eNB, MgNB, SgNB, or Sng-eNB; and base station 106A can operate as an SgNB or Sng-eNB. UE 102 can communicate with base station 104 and base station 106A or 106B via the same radio access technology (RAT), such as EUTRA or NR, or via a different RAT.

[0054] When base station 104 is a MeNB and base station 106A is an SgNB, UE 102 can be in an EN-DC with MeNB 104 and SgNB 106A. When base station 104 is a Mng-eNB and base station 106A is an SgNB, UE 102 can be in a Next Generation (NG) EUTRA-NR DC (NGEN-DC) with Mng-eNB 104 and SgNB 106A. When base station 104 is a MgNB and base station 106A is an SgNB, UE 102 can be in an NR-NR DC (NR-DC) with MgNB 104 and SgNB 106A. When base station 104 is a MgNB and base station 106A is a Sng-eNB, UE 102 can be in an NR-EUTRADC (NE-DC) with MgNB 104 and Sng-eNB 106A.

[0055] Figure 1B Example distributed implementations of any one or more base stations 104, 106A, 106B are depicted. In this implementation, base station 104, 106A, or 106B includes a central unit (CU) 172 and one or more distributed units (DUs) 174. CU 172 includes processing hardware, such as one or more general-purpose processors (e.g., CPUs) and a computer-readable memory storing machine-readable instructions executable on the general-purpose processor(s) and / or dedicated processing units. For example, CU 172 may include... Figure 1A The processing hardware is 130 or 140.

[0056] Each DU 174 also includes processing hardware, which may include one or more general-purpose processors (e.g., CPUs) and computer-readable memory storing machine-readable instructions executable on one or more general-purpose processors and / or dedicated processing units. For example, the processing hardware may include a Media Access Control (MAC) controller configured to manage or control one or more MAC operations or procedures (e.g., random access procedures), and a Radio Link Control (RLC) controller configured to manage or control one or more RLC operations or procedures when the base station (e.g., base station 106A) operates as an MN or SN. The processing hardware may also include a physical layer controller configured to manage or control one or more physical layer operations or procedures.

[0057] In some implementations, CU 172 may include a logical node CU-CP 172A, which hosts the control plane portion of the Packet Data Convergence Protocol (PDCP) and / or the Radio Resource Control (RRC) protocol of CU 172. CU 172 may also include (multiple) logical nodes CU-UP 172B, which host the user plane portion of the PDCP and / or the Service Data Adaptation Protocol (SDAP) protocol of CU 172. As described herein, CU-CP 172A may transmit non-MBS control information and MBS control information, and CU-UP 172B may transmit non-MBS data packets and MBS data packets.

[0058] The CU-CP 172A can connect to multiple CU-UP 172Bs via the E1 interface. The CU-CP 172A selects the appropriate CU-UP 172B for the service requested by UE 102. In some implementations, a single CU-UP 172B can connect to multiple CU-CP 172As via the E1 interface. The CU-CP 172A can connect to one or more DU 174s via the F1-C interface. A CU-UP 172B can connect to one or more DU 174s via the F1-U interface under the control of the same CU-CP 172A. In some implementations, a DU 174 can connect to multiple CU-UP 172Bs under the control of the same CU-CP 172A. In such implementations, the connection between the CU-UP 172B and DU 174 is established by the CU-CP 172A using bearer context management functions.

[0059] Figure 2An example protocol stack 200 is illustrated in a simplified manner, according to which UE 102 can communicate with an eNB / ng-eNB or gNB (e.g., one or more of base stations 104, 106A, 106B).

[0060] In example stack 200, the EUTRA physical layer (PHY) 202A provides a transport channel to the EUTRAMAC sublayer 204A, which in turn provides a logical channel to the EUTRARLC sublayer 206A. The EUTRA RLC sublayer 206A then provides an RLC channel to the EUTRA PDCP sublayer 208, and in some cases, to the NR PDCP sublayer 210. Similarly, the NR PHY 202B provides a transport channel to the NR MAC sublayer 204B, which in turn provides a logical channel to the NR RLC sublayer 206B. The NR RLC sublayer 206B then provides an RLC channel to the NRPDCP sublayer 210. In some implementations, UE 102 supports, for example... Figure 2 The EUTRA and NR stacks shown are designed to support handover between EUTRA and NR base stations and / or support DC on the EUTRA and NR interfaces. Additionally, as... Figure 2 As illustrated, UE 102 can support layering of NRPDCP 210 on EUTRA RLC 206A, and SDAP sublayer 212 on NR PDCP sublayer 210.

[0061] EUTRA PDCP sublayer 208 and NR PDCP sublayer 210 receive packets that can be referred to as Service Data Units (SDUs) (e.g., from the Internet Protocol (IP) layer, layered directly or indirectly on PDCP layers 208 or 210), and output packets that can be referred to as Protocol Data Units (PDUs) (e.g., to RLC layers 206A or 206B). Except where the difference between SDU and PDU is relevant, for simplicity, this disclosure refers to both SDU and PDU as "packets". The packet can be an MBS packet or a non-MBS packet. For example, an MBS packet includes MBS data packets that contain application content of the MBS service (e.g., IPv4 / IPv6 multicast delivery, IPTV, wireless software delivery, group communications, IoT applications, V2X applications, and / or emergency messages related to public safety). In another example, an MBS packet includes application control information for the MBS service.

[0062] For example, on the control plane, EUTRA PDCP sublayer 208 and NR PDCP sublayer 210 can provide SRBs to exchange RRC messages or Non-Access Stratum (NAS) messages. On the user plane, EUTRA PDCP sublayer 208 and NR PDCP sublayer 210 can provide DRBs to support data exchange. The data exchanged on NR PDCP sublayer 210 can be SDAP PDUs, Internet Protocol (IP) packets, or Ethernet packets.

[0063] In a scenario where UE 102 operates in EN-DC with base station 104 operating as a MeNB and base station 106A operating as an SgNB, wireless communication system 100 can provide UE 102 with an MN-terminated bearer using EUTRA PDCP sublayer 208, or an MN-terminated bearer using NR PDCP sublayer 210. In various scenarios, wireless communication system 100 can also provide UE 102 with an SN-terminated bearer, which uses only NR PDCP sublayer 210. The MN-terminated bearer can be an MCG bearer, a separate bearer, or an MN-terminated SCG bearer. The SN-terminated bearer can be an SCG bearer, a separate bearer, or an SN-terminated MCG bearer. The MN-terminated bearer can be an SRB (e.g., SRB1 or SRB2) or a DRB. The SN-terminated bearer can be an SRB or a DRB.

[0064] In some implementations, a base station (e.g., base station 104, 106A, or 106B) broadcasts MBS data packets via one or more MBS radio bearers (MRBs), and UE 102 subsequently receives MBS data packets via the MRBs. The base station may include multiple configurations of the MRBs in the multicast configuration parameters (also referred to as MBS configuration parameters) described below. In some implementations, the base station broadcasts MBS data packets via RLC sublayer 206, MAC sublayer 204, and PHY sublayer 202, and accordingly, UE 102 uses PHY sublayer 202, MAC sublayer 204, and RLC sublayer 206 to receive MBS data packets. In such an implementation, the base station and UE 102 may communicate MBS data packets without using PDCP sublayer 208 and SDAP sublayer 212. In other implementations, the base station transmits MBS data packets via PDCP sublayer 208, RLC sublayer 206, MAC sublayer 204, and PHY sublayer 202, and correspondingly, UE 102 uses PHY sublayer 202, MAC sublayer 204, RLC sublayer 206, and PDCP sublayer 208 to receive MBS data packets. In such an implementation, the base station and UE 102 may not use SDAP sublayer 212 to communicate MBS data packets. In other implementations, the base station transmits MBS data packets via SDAP sublayer 212, PDCP sublayer 208, RLC sublayer 206, MAC sublayer 204, and PHY sublayer 202, and correspondingly, UE 102 uses PHY sublayer 202, MAC sublayer 204, RLC sublayer 206, PDCP sublayer 208, and SDAP sublayer 212 to receive MBS data packets.

[0065] Figures 3A-5 This is a message passing diagram illustrating an example scenario of MBS information communication between the base station, CN, and UE. Generally speaking, Figures 3A-5 Similar events are labeled with similar reference numerals (e.g., event 350A is similar to events 350B, 350C, 450A, etc.), and the differences will be discussed in the appropriate places below. Apart from the differences shown in the figures and discussed below, any alternative implementations discussed regarding specific events (e.g., those used for message passing and processing) can be applied to events labeled with similar reference numerals in other figures.

[0066] Now for reference Figure 3AIn scenario 300A illustrated in the diagram, UE 102 initially transmits a First PDU Session Establishment Request message 302A to base station (BS) 104 to establish a first PDU session for MBS. To indicate that UE 102 is requesting a DRB for receiving MBS information, UE 102 may include a flag or other indication in the PDU session establishment request. For example, the flag may be set to "MBS" or a Data Network Name (DNN) field corresponding to the MBS service. In some implementations, UE 102 initially operates in an idle or inactive state (e.g., RRC_IDLE state, RRC_INACTIVE state), or more generally, in a state where there is no active radio connection between UE 102 and base station 104. Alternatively, UE 102 initially operates in a connected state (e.g., RRC_CONNECTED state), or more generally, in a state where there is an active radio connection between UE 102 and base station 104.

[0067] Base station 104 then sends a 304A first PDU session establishment request message to CN 110 (e.g., AMF 164 and / or SMF 166). In some implementations, base station 104 may send a 304A BS-CN interface message (e.g., NG interface message, initial UE message, or uplink NAS transmission message) including the first PDU session establishment request message to CN 110.

[0068] In response to the first PDU session establishment request message, CN 110 sends a 306A first PDU session establishment acceptance message to base station 104, and base station 104 then sends a 308A first PDU session establishment acceptance message to UE 102. In some implementations, CN 110 sends a 306A CN-BS interface message (e.g., an NG interface message or a PDU session resource setup request message) including the first PDU session establishment acceptance message. In response to the CN-BS interface message, base station 104 transmits a 310A RRC reconfiguration message configuring the first DRB to UE 102. In some implementations, base station 104 may include the first PDU session establishment acceptance message in the RRC reconfiguration message 310A transmitted by base station 104. In other implementations, base station 104 may transmit a 308A DL RRC message including the first PDU session establishment acceptance message to UE 102. The DL RRC message may be a DLInformationTransfer message, an RRC reconfiguration message, or any suitable RRC message that may include a NAS PDU.

[0069] In response to base station 104 transmitting the RRC reconfiguration message 310A, UE 102 may transmit the RRC reconfiguration complete message 312A to base station 104. In some implementations, after receiving the RRC reconfiguration complete message 312A, base station 104 sends a BS to CN interface message (e.g., a PDU session resource setup response message) to CN 110 to confirm that base station 104 has configured radio resources for the first PDU session for UE 102.

[0070] Events 302A, 304A, 306A, 308A, 310A, and 312A are collectively referred to as MBS PDU session establishment procedure 350A.

[0071] In some implementations, UE 102 may transmit an MBS request message to base station 104 to request, join, or register for a specific MBS service, and base station 104 may send a 316A MBS request message to CN 110. In one implementation, UE 102 may include the MBS request message in an IP packet and transmit the IP packet to base station 104 via a first DRB. In this implementation, base station 104 sends the 316A IP packet to CN 110 (e.g., UPF 162). In another implementation, UE 102 may transmit a 314A MBS request (e.g., as a NAS message or RRC message) via an SRB. For example, UE 102 may transmit a NAS message requesting MBS service to base station 104 via an SRB, and base station 104 then sends a 316A NAS message to CN 110 (e.g., AMF 164 and / or SMF 166). In other implementations, UE 102 may suppress the transmission of explicit MBS requests to base station 104. For example, a PDU session establishment request message (event 302A) may indicate the MBS service that UE 102 is interested in receiving. In other implementations, CN 110 may transmit a message to base station 104 requesting base station 104 to deliver MBS services (e.g., emergency broadcast) to UE 102.

[0072] After CN 110 determines that base station 104 has configured radio resources for UE 102 for the first PDU session, in some implementations, CN 110 may send 318A MBS control information to base station 104, which then transmits 320A MBS control information to UE 102, for example, via SRB or a first DRB. Specifically, in some implementations, a network node (e.g., CN 110 or an MBS server) generates the MBS control information. In one implementation, the network node may include the MBS control information in multiple IP packets and send 318A of those IP packets to base station 104, which then transmits 320A of those IP packets to UE 102 via the first DRB. In another implementation, CN 110 sends 318A NAS messages including the MBS control information to base station 104. Base station 104 then sends 320A NAS messages to UE 102 via SRB. In some implementations, CN 110 and / or base station 104 may transmit MBS control information about a first Quality of Service (QoS) flow to UE 102. That is, CN 110 associates the MBS control information with a first QoS profile of a first QoS flow including a first plurality of QoS parameters. CN 110 and base station 104 implement the first QoS profile for the transmission of MBS data packets.

[0073] Alternatively, in other implementations, base station 104 generates MBS control information instead of receiving it from CN 110 or an MBS server. Base station 104 transmits the 320A MBS control information to UE 102, for example, via an SRB or a first DRB.

[0074] MBS control information assists UE 102 in receiving 338A MBS data packets. In some implementations, in response to a PDU session resource setup response message or an MBS request message, CN 110 can determine that UE 102 has been configured with radio resources for the first PDU session. After CN 110 determines that UE 102 has been configured with radio resources for the first PDU session, in some implementations, CN 110 sends MBS data packets for a specific MBS service (338A) to base station 104, which then transmits the MBS data packets to UE 102 via the first DRB. In other implementations involving a group of UEs, CN 110 can send MBS data packets for a specific MBS service (338A) to base station 104 regardless of whether UE 102 has been configured with radio resources for the first PDU session.

[0075] In some implementations, CN 110 and / or base station 104 may transmit MBS data packets to UE 102 on a second Quality of Service (QoS) stream. Specifically, CN 110 associates the MBS data packets with a second QoS profile of a second QoS stream that includes a second plurality of QoS parameters. CN 110 and base station 104 implement the second QoS profile for the transmission of MBS data packets. In other implementations, CN 110 may transmit MBS data packets on a first QoS stream. CN 110 and base station 104 implement a first QoS profile for the transmission of MBS data packets.

[0076] In some implementations, the MBS control information includes security configuration parameters. In one implementation, the security configuration parameters include multiple security keys, and the UE 102 uses these security keys to decrypt MBS data packets and / or perform integrity checks on them. In another implementation, the UE 102 derives multiple security keys from the security configuration parameters and uses these security keys to decrypt MBS data packets and / or perform integrity checks on them.

[0077] In other implementations, MBS control information includes a group identifier (e.g., a Temporary Mobile Group Identifier (TMGI)) or an MBS session identifier. UE 102 uses the group identifier and / or the MBS session identifier to receive MBS data packets.

[0078] In some implementations, the RRC reconfiguration message transmitted by base station 104 for 310A includes a first DRB configuration configuring the first DRB, and includes physical layer configuration parameters, MAC configuration parameters, and / or RLC configuration parameters. Base station 104 may assign radio resources for transmitting MBS data packets to a specific UE (e.g., UE 102A) or a group of UEs (e.g., UE 102A and UE 102B, or UE 102A, UE 102B, and / or...). Figure 3A (Multiple other UEs not shown). In the case of a group of UEs, base station 104 transmits 338A MBS data packets on radio resources (i.e., radio resources shared by the group of UEs), wherein the group of UEs receives MBS data packets using configuration parameters. Therefore, each UE in the group receives 338A MBS data packets from base station 104 on the same radio resources. Therefore, the RRC reconfiguration message or first DRB configuration transmitted by base station 104 may include unicast configuration parameters for a specific UE or multicast configuration parameters for a group of UEs.

[0079] In cases involving a group of UEs, in some implementations, base station 104 may transmit the first DRB configuration and configuration parameters to the group of UEs in a separate RRC reconfiguration message. In other implementations, base station 104 may broadcast the first DRB configuration and / or configuration parameters to the group of UEs (e.g., base station 104 may broadcast the first DRB configuration and / or configuration parameters in System Information Blocks (SIBs) to cell 124). Configuration parameters for UE 102 to receive MBS data packets on public radio resources may include a Radio Network Temporary Identifier (RNTI). The group of UEs or UE 102 uses the RNTI to receive a DCI with a CRC scrambled with the RNTI on the PDCCH and receives the PDSCH according to the DCI. The PDSCH may include some MBS data packets and / or at least one MBS data packet. In some implementations, the RNTI may be an RNTI group (G-RNTI) or an MBS-RNTI. In some implementations, for example, the configuration parameters for UE 102 to receive MBS data packets on public radio resources may include DL BWP configuration for configuring MBS DL BWP.

[0080] In cases involving a specific UE, base station 104 transmits 338A MBS data packets on dedicated radio resources (i.e., dedicated only to the specific UE), where the specific UE receives MBS packets using configuration parameters. Thus, the specific UE receives 338A MBS data packets from base station 104 on the dedicated radio resources.

[0081] In some implementations, the RRC reconfiguration message transmitted by base station 104 for 310A may include a CellGroupConfig information element (IE) configuring configuration parameters. In other implementations, the RRC reconfiguration message transmitted by base station 104 for 310A may include an MBS-specific IE configuring configuration parameters. Base station 104 may indicate in the RRC reconfiguration message transmitted by base station 104 for 310A that the first DRB is associated with the first PDU session. For example, the first DRB configuration may include a PDU session identifier for the first PDU session. In some implementations, the base station configures UE 102 to use RLC acknowledged mode (AM) for the first DRB in the RLC configuration parameters. In other implementations, the base station configures UE 102 to use RLC unacknowledged mode (UM) for the first DRB in the RLC configuration parameters.

[0082] Before, during, or after the MBS PDU session establishment procedure 350A, in some implementations, UE 102 may perform a unicast PDU session establishment procedure 360A with base station 104 and CN 110 (e.g., AMF 164 and / or SMF 166 or another AMF and / or SMF). UE 102 transmits a second PDU session establishment request message 362A to base station 104 for establishing a second PDU session for one or more unicast services. For example, one or more unicast services may be voice calls, video calls, or internet services (e.g., services for email, navigation, social media, streaming, gaming, web browsing, etc.).

[0083] Base station 104 then sends a 364A second PDU session establishment request message to CN 110 (e.g., AMF 164 and / or SMF 166). In some implementations, base station 104 may send a 364A BS-CN interface message (e.g., NG interface message, initial UE message, or uplink NAS transmission message) including the second PDU session establishment request message to CN 110.

[0084] In response to the second PDU session establishment request message, CN 110 sends a 366A second PDU session establishment acceptance message to base station 104, and base station 104 then sends a 368A second PDU session establishment acceptance message to UE 102. In some implementations, CN 110 sends a 366A CN-BS interface message (e.g., an NG interface message or a PDU session resource setup request message) that includes the second PDU session establishment acceptance message. In response to the CN-BS interface message, base station 104 transmits a 370A RRC reconfiguration message that configures the second DRB to UE 102. In some implementations, base station 104 may include the second PDU session establishment acceptance message in the RRC reconfiguration message that base station 104 transmits. In other implementations, base station 104 may transmit a 368A DL RRC message that includes the second PDU session establishment acceptance message to UE 102. The DL RRC message may be a DLInformationTransfer message, an RRC reconfiguration message, or any suitable RRC message that may include a NAS PDU.

[0085] In response to UE 102 receiving the 370A RRC reconfiguration message, UE 102 may transmit a 372ARRC reconfiguration complete message to base station 104. In some implementations, after receiving the 372ARRC reconfiguration complete message, base station 104 sends a BS-CN interface message (e.g., a PDU session resource setup response message) to CN 110 to confirm that base station 104 has configured radio resources for the second PDU session for UE 102.

[0086] In some implementations, the RRC reconfiguration message transmitted by base station 104 for 370A includes a second DRB configuration for configuring the second DRB, and includes physical layer configuration parameters, MAC configuration parameters, and / or RLC configuration parameters for configuring radio resources. Base station 104 can assign radio resources for unicast packets to a specific UE (e.g., UE 102A), meaning the radio resources can be dedicated solely to that specific UE. Base station 104 transmits unicast packets to the specific UE on the dedicated resources, and the specific UE transmits unicast packets to base station 104 on the dedicated resources.

[0087] In some implementations, the RRC reconfiguration message 370A transmitted by base station 104 may include a CellGroupConfig information element (IE) configuring configuration parameters. Base station 104 may indicate in the RRC reconfiguration message 370A transmitted by base station 104 that the second DRB is associated with the second PDU session. For example, the second DRB configuration may include the PDU session identifier of the second PDU session. In some implementations, base station 104 configures UE 102 to use RLC AM for the second DRB in the RLC configuration parameters. In some implementations, the RLC configuration parameters in the RRC reconfiguration message 370A transmitted by base station 104 may be the same as or different from the RLC configuration parameters in the RRC reconfiguration message 310A transmitted by base station 104.

[0088] After configuring the second DRB, UE 102 communicates 374A unicast packets with CN 110 (e.g., UPF 162 or another UPF) and base station 104 via the second DRB. In some implementations, the unicast services are multiple IMS services (e.g., voice service, supplemental service, and / or short message service), and UE 102 establishes a second PDU session for the multiple IMS services. In such an implementation, UE 102 may transmit a Session Initiation Protocol (SIP) message to base station 104 via the second DRB, and base station 104 then sends a SIP message to CN 110. CN 110 can then send the SIP message to the IMS network, which includes, for example, a Proxy Call Session Control Function (P-CSCF), appropriate network nodes processing SIP messages, and / or specific network nodes processing voice packets. In this implementation, CN 110 can receive SIP messages from the IMS network and transmit the SIP messages to base station 104, which then transmits the SIP messages to UE 102 via the second DRB.

[0089] In some implementations, UE 102 sends a SIP message (e.g., SIP INVITE) to BS via a second DRB for a mobile-initiated voice call, and BS then sends a SIP message to CN 110. CN 110 then sends a SIP message to the IMS network. In other implementations, the IMS network sends a SIP message (e.g., SIPINVITE) for a mobile-terminated voice call by UE 102. The IMS network may send an IMS-CN interface message (e.g., an Npcf_PolicyAuthorization_Update message or a suitable Npcf message) to CN 110 for a mobile-initiated or terminated voice call (e.g., in response to a SIP message received from UE 102 or transmitted by the IMS network). In response to the IMS-CN interface message, CN 110 sends a CN-BS interface message (e.g., a PDU session resource modification request message) to base station 104, prompting base station 104 to configure UE 102's DRB for communication (e.g., transmitting and / or receiving) voice packets. In response to the CN-BS interface message, base station 104 transmits a third RRC reconfiguration message to UE 102, which includes a third DRB configuration. In response to the third RRC reconfiguration message, UE 102 can transmit an RRC reconfiguration complete message to base station 104. Thus, UE 102 communicates voice packets with CN 110 via base station 104 (through the third DRB). CN 110 can communicate voice packets with the IMS network.

[0090] In some implementations, CN 110 may include a PDU session modification command message in the CN-BS interface message to configure a third Quality of Service (QoS) flow for transmitting voice packets to and / or from UE 102. CN 110 associates voice packets with a third QoS profile that includes a third QoS flow containing a third set of QoS parameters. CN 110 and base station 104 implement the third QoS profile for the transmission of voice packets to and / or from UE 102. Then, base station 104 transmits the PDU session modification command message to UE 102. In some implementations, base station 104 may include the PDU session modification command message in a DL RRC message and transmit the DL RRC message to UE 102. For example, the DL RRC message may be a third RRC reconfiguration message, an additional RRC reconfiguration message, or a DLInformationTransfer message. UE 102 may transmit an RRC reconfiguration complete message in response to the additional RRC reconfiguration message. Therefore, UE 102 can communicate voice packets with CN 110 on the QoS stream via base station 104 (through the third DRB).

[0091] In some implementations, the third RRC reconfiguration message includes physical layer configuration parameters, MAC configuration parameters, and / or RLC configuration parameters. Base station 104 can assign radio resources for voice packets to a specific UE (e.g., UE 102A), meaning the radio resources are dedicated solely to that specific UE. Base station 104 transmits voice packets to the specific UE on the dedicated resources, and the specific UE transmits voice packets to base station 104 on the dedicated resources.

[0092] In some implementations, the third RRC reconfiguration message may include a CellGroupConfig information element (IE) that configures the configuration parameters. In some implementations, the RLC configuration parameters in the third RRC reconfiguration message may be the same as or different from the RLC configuration parameters in the RRC reconfiguration message transmitted by base station 104 for 370A. In some implementations, base station 104 configures UE 102 to use RLC UM for the third DRB in the RLC configuration parameters.

[0093] Base station 104 may indicate in the third RRC reconfiguration message that the third DRB is associated with the second PDU session and / or QoS flow. For example, the third DRB configuration may include the PDU session identifier of the second PDU session and / or the QoS flow identifier of the third QoS flow.

[0094] In response to a PDU session modification command message, UE 102 can send a PDU session modification complete message to CN 110 via base station 104. In some implementations, UE 102 can include the PDU session modification complete message in a UL RRC message and transmit the UL RRC message to base station 104. Base station 104 then extracts the PDU session modification complete message from the UL RRC message and sends the PDU session modification complete message to CN 110. In some implementations, base station 104 can send a BS-CN interface message (e.g., a PDU session resource modification response message or an uplink NAS transmission message) to CN 110 that includes the PDU session modification complete message. Base station 104 sends a PDU session resource modification response message in response to a PDU session resource modification request message. In some implementations, the UL RRC message can be an RRC reconfiguration complete message in response to a third RRC reconfiguration message or an additional RRC reconfiguration message. In other implementations, the UL RRC message can be a ULInformationTransfer message.

[0095] In some implementations, the unicast services are multiple Internet services, and UE 102 establishes a second PDU session for the multiple Internet services. The UE communicates Internet Protocol (IP) packets with CN 110 via base station 104 (through the second DRB).

[0096] In some implementations, UE 102 may include a first data network name (DNN) in the first PDU session establishment request message to indicate the specific data network that UE 102 wishes to access via the first PDU session. In some implementations, UE 102 may include a second DNN in the second PDU session establishment request message to indicate the specific data network that UE 102 wishes to access via the first PDU session. In other implementations, UE 102 may exclude a DNN in the second PDU session establishment request message. In this case, the second PDU session may be associated with a default DNN.

[0097] In some implementations, as previously described, UE 102 performs a first unicast PDU session establishment procedure 360A for multiple IMS services. In such an implementation, UE 102 may perform a second unicast PDU session establishment procedure with base station 104 and CN 110 to establish a third PDU session for multiple Internet services, similar to the first unicast PDU session establishment procedure 360A. During the second unicast PDU session establishment procedure, similar to event 370A, base station 104 transmits a fourth RRC reconfiguration message to UE 102, including a fourth DRB configuration that configures the fourth DRB. UE 102 and base station 104 establish a fourth DRB with the fourth DRB configuration. In response to the fourth RRC reconfiguration message, UE 102 may transmit a fourth RRC reconfiguration complete message to base station 104. Similar to event 374A, UE 102 communicates IP packets for multiple Internet services with base station 104 (via the fourth DRB) and CN 110.

[0098] In some implementations, the fourth RRC reconfiguration message includes physical layer configuration parameters, MAC configuration parameters, and / or RLC configuration parameters. Base station 104 can send the message to a specific UE (e.g., UE 102A) or a group of UEs (e.g., UE 102A and UE 102B, or UE 102A, UE 102B, and / or...). Figure 1A and Figure 3BConfiguration parameters or radio resources are assigned to (multiple) other UEs (not shown). In the case of this group of UEs, base station 104 transmits MBS data packets on radio resources (i.e., radio resources shared by the group of UEs), where the group of UEs receives MBS data packets using configuration parameters. Therefore, the group of UEs receives MBS data packets from base station 104 on the same radio resources. In the case of this group of UEs, base station 104 may transmit a fourth DRB configuration and configuration parameters to each UE in the group in a separate RRC reconfiguration message or in a broadcast (e.g., a broadcast to (multiple) SIBs of cell 124). The configuration parameters for UE 102 to receive MBS data packets on shared radio resources may include a Radio Network Temporary Identifier (RNTI). The group of UEs or UE 102 uses the RNTI to receive a DCI with a CRC scrambled with the RNTI on the PDCCH and receives the PDSCH according to the DCI. The PDSCH may include some MBS data packets and / or at least one MBS data packet. In some implementations, the RNTI can be an RNTI group (G-RNTI) or an MBS-RNTI.

[0099] In cases involving a specific UE, base station 104 transmits MBS data packets on dedicated radio resources (i.e., dedicated only to the specific UE), where the specific UE receives them using configuration parameters. Therefore, the specific UE receives MBS data packets from base station 104 on the dedicated radio resources.

[0100] In some implementations, the fourth RRC reconfiguration message may include a CellGroupConfig information element (IE) configuring configuration parameters. Base station 104 may indicate in the fourth RRC reconfiguration message that the fourth DRB is associated with the third PDU session. For example, the fourth DRB configuration may include the PDU session identifier of the second PDU session. In some implementations, base station 104 configures UE 102 to use RLC AM for the fourth DRB in the RLC configuration parameters. In some implementations, the RLC configuration parameters in the fourth RRC reconfiguration message may be the same as or different from the RLC configuration parameters in the RRC reconfiguration message transmitted by base station 104 in the 370A.

[0101] Figure 3B It shows the relationship with Figure 3A Scenario 300B is similar to Scenario 300A. Scenario 300B is largely similar to Scenario 300A, except that base station 104 is configured with an additional radio bearer (i.e., the fifth DRB) for transmitting MBS data packets to UE 102.

[0102] Initially, UE 102 performs a 350B MBS PDU session establishment procedure with CN 110 via base station 104. In some implementations, UE 102 may transmit a 314B MBS request message to base station 104 via the first DRB to request, join, or register for a specific MBS service. Base station 104 sends a 316B MBS request message to CN 110, and CN 110 can then request MBS services from the MBS network ( Figure 1A and Figure 3B (Not shown) The UE 102 sends an MBS request message. The MBS network may include an Application Function (AF), an MBS Function (MBSF), a Multicast Session Function (MSF), and / or one or more network nodes suitable for MBS. As described in conjunction with event 314A, UE 102 may transmit the 314B MBS request via the SRB or the first DRB, or may suppress the transmission of the 314B explicit request for MBS service. For example, a PDU session establishment request message (during process 350B) may indicate the MBS service that UE 102 is interested in receiving. In other implementations, CN 110 may transmit a message to base station 104 requesting base station 104 to deliver MBS service (e.g., emergency broadcast) to UE 102.

[0103] After establishing a first PDU session for MBS with UE 102 at event 350B or receiving an MBS request message at event 316B, CN 110 may send a 322B CN-BS interface message (e.g., a PDU session resource modification request message) to base station 104, which prompts base station 104 to configure the DRB for received MBS data packets for UE 102. In response to the CN-BS interface message, base station 104 transmits a 324B RRC reconfiguration message to UE 102, including the DRB configuration (e.g., the fifth DRB) and the configured DRB (e.g., the fifth DRB configuration). In response to the RRC reconfiguration message, UE 102 may transmit a 326BRRC reconfiguration complete message to base station 104. In response to base station 104 receiving CN to BS interface message 322B, base station 104 may send BS to CN interface message 328B (e.g., PDU session resource modification response message) to CN 110 before or after transmitting RRC reconfiguration message 324B or receiving RRC reconfiguration complete message 326B.

[0104] After CN 110 determines that base station 104 has configured radio resources that UE 102 can use to receive MBS data packets (i.e., UE 102 establishes a fifth DRB), CN 110 sends 338B MBS data packets to base station 104, which then transmits the 338B MBS data packets to UE 102 via the fifth DRB. Therefore, UE 102 receives 338B MBS data packets from base station 104 on the fifth DRB. CN 110 can receive MBS data packets from the MBS network.

[0105] In addition, before, during or after the MBS PDU session establishment process 350B, UE 102 can perform the first unicast PDU session establishment process 360B with CN 110 via base station 104, and communicate 374B unicast packets with CN 110 via base station 104.

[0106] In some implementations, the RRC reconfiguration message 324B transmitted by base station 104 includes physical layer configuration parameters, MAC configuration parameters, and / or RLC configuration parameters configuring radio resources dedicated to UE 102. For example, the RRC reconfiguration message 324B transmitted by base station 104 may include a CellGroupConfig information element (IE) configuring the configuration parameters. In some implementations, the RLC configuration parameters in the RRC reconfiguration message 324B transmitted by base station 104 may be the same as or different from the RLC configuration parameters in the RRC reconfiguration message for configuring the first DRB transmitted by base station 104 during the MBS PDU session establishment procedure 350B. In some implementations, base station 104 configures UE 102 to use RLC UM for the fifth DRB in the RLC configuration parameters.

[0107] In some implementations, and for Figure 3A The second QoS flow is similarly described. CN 110 can include a PDU session modification command message in the CN-BS interface message (322B) transmitted by CN 110 to configure the Quality of Service (QoS) flow of UE 102. Base station 104 can include the PDU session modification command message in a DL RRC message and transmit the DL RRC message to UE 102. For example, the DL RRC message can be an RRC reconfiguration message (324B), an additional RRC reconfiguration message, or a DLInformationTransfer message transmitted by base station 104. UE 102 can respond to the additional RRC reconfiguration message by transmitting an RRC reconfiguration complete message.

[0108] Base station 104 may indicate in a 324B RRC reconfiguration message transmitted by base station 104 that the fifth DRB is associated with the first PDU session and / or QoS flow. For example, the fifth DRB configuration may include the PDU session identifier of the first PDU session and / or the QoS flow identifier of the QoS flow.

[0109] In response to a PDU session modification command message, UE 102 can send a PDU session modification complete message to CN 110 via base station 104. In some implementations, UE 102 can include the PDU session modification complete message in a UL RRC message and transmit the UL RRC message to base station 104. Base station 104 then extracts the PDU session modification complete message from the UL RRC message and sends the PDU session modification complete message to CN 110. In some implementations, base station 104 can include the PDU session modification complete message in a BS-CN interface message (e.g., an uplink NAS transmission message) transmitted by base station 104 (e.g., 328B). In other implementations, base station 104 can send an additional BS-CN interface message (e.g., an uplink NAS transmission message) including the PDU session modification complete message to CN 110. In some implementations, the UL RRC message can be an RRC reconfiguration complete message in response to UE 102 receiving a 324B RRC reconfiguration message or an RRC reconfiguration message with an additional RRC reconfiguration message. In other implementations, the UL RRC message can be a ULInformationTransfer message.

[0110] After CN 110 determines that base station 104 has configured radio resources for receiving MBS data packets for the first PDU session or UE 102, in some implementations, CN 110 may send 318B MBS control information to base station 104, which then transmits 320B MBS control information to UE 102, for example, via SRB, first DRB, or fifth DRB. Alternatively, instead of receiving MBS control information from CN 110, base station 104 generates MBS control information and transmits 320B MBS control information to UE 102, for example, via SRB, first DRB, or fifth DRB. The MBS control information helps UE 102 receive 338B MBS data packets. Event 318B may occur before or after events 328B, 322B, or 316B. Event 320B may occur before or after events 326B, 324B, or 314B.

[0111] In some implementations, in response to a PDU session resource setup response message or an MBS request message, CN 110 can determine that base station 104 has configured radio resources for the first PDU session. In some implementations, in response to CN 110 receiving a 328B BS-CN interface message or an additional BS-CN interface message, CN 110 can determine that UE 102 has been configured with radio resources for receiving MBS data packets. After CN 110 determines that UE 102 has been configured with radio resources for receiving MBS data packets, in some implementations, CN 110 can send 338B MBS data packets to base station 104, which then transmits the MBS data packets to UE 102 via the fifth DRB. In cases involving a group of UEs, in other implementations, CN 110 can send 338B MBS data packets for a specific MBS service to base station 104, regardless of whether UE 102 has been configured with radio resources for the first PDU session.

[0112] Go to Figure 3C Scenario 300C is largely similar to Scenario 300B. However, for MBS and (multiple) unicast services (e.g., (multiple) IMS services and / or Internet services), UE 102 performs the PDU session establishment procedure with CN 110 via base station 104 in Scenario 350C. Therefore, unlike Scenarios 300A and 300B, UE 102 can receive MBS and (multiple) unicast services through the same PDU session. The message passing during PDU session establishment procedure 350C is largely similar to the message passing during MBS PDU session establishment procedure 350A, except that UE 102 initially transmits a PDU session establishment request message to base station 104 to establish a PDU session for MBS and unicast services, similar to event 302A.

[0113] Events 314C, 316C, 322C, 324C, 326C, 328C, 318C, 336C, and 338C used to configure MBS transmission to UE 102 can be similar to events 314B, 316B, 322B, 324B, 326B, 328B, 318B, 336B, and 338B, respectively. Before, after, or during these events used to configure MBS transmission, UE 102 can transmit a 363C unicast request message to base station 104 to request a specific unicast service, and base station 104 can transmit a 365C unicast request message to CN 110. In some implementations, UE 102 transmits the 363C unicast request message on the first DRB configured during PDU session establishment procedure 350C. Furthermore, in some implementations, the unicast request message can be a SIP message, as discussed above with reference to event 374A.

[0114] In response to receiving a 365C unicast request message, CN 110 may transmit a 382C CN-BS interface message (e.g., a PDU session resource modification request message), which prompts base station 104 to configure a DRB for UE 102 to receive unicast data packets. In response to receiving the 382C CN-BS interface message, base station 104 transmits a 384C RRC reconfiguration message to UE 102, including a DRB configuration (e.g., a sixth DRB) and a DRB configuration (e.g., a sixth DRB configuration). In response to the RRC reconfiguration message, UE 102 may transmit a 386C RRC reconfiguration complete message to base station 104. In response to the base station receiving the 382C CN-BS interface message, base station 104 may send a 388C BS-CN interface message (e.g., a PDU session resource modification response message) to CN 110 before or after transmitting the 384C RRC reconfiguration message or receiving the 386C RRC reconfiguration complete message. UE 102 can then communicate with CN via base station 104 through the sixth DRB using unicast packets 374C. Messages 382C, 384C, 386C, and 388C used to configure the sixth DRB are similar to events 322C, 324C, 326C, and 328C used to configure the fifth DRB, except that the sixth DRB is used for unicast service instead of MBS service.

[0115] In some implementations, CN 110 may include a PDU session modification command message in the CN-BS interface message to configure a Quality of Service (QoS) flow for transmitting unicast data packets to and / or from UE 102. CN 110 associates the unicast data packets with a QoS profile of the QoS flow, which includes multiple QoS parameters. CN 110 and base station 104 implement the QoS profile for the transmission of unicast data packets to and / or from UE 102. Base station 104 then transmits the PDU session modification command message to UE 102. In some implementations, base station 104 may include the PDU session modification command message in a DL RRC message and transmit the DL RRC message to UE 102. For example, the DL RRC message may be an RRC reconfiguration message (384C) transmitted by base station 104, an additional RRC reconfiguration message, or a DLInformationTransfer message. UE 102 may transmit an RRC reconfiguration complete message in response to the additional RRC reconfiguration message. Therefore, UE 102 can communicate unicast data packets with CN 110 on the QoS stream via base station 104 (e.g., via the fifth DRB).

[0116] In some implementations, base station 104 can transmit MBS data packets and unicast data packets over the same radio bearer associated with the PDU session (e.g., the fifth DRB or the sixth DRB) (e.g., if similar or identical QoS profiles apply to MBS data packets and unicast data packets). For example, in response to a user request for web browsing service from UE 102, UE 102 can establish a PDU session. During browsing, the user may choose to watch MBS services, such as live sports events. The DRB associated with the PDU session can be configured to transmit unicast data packets related to web browsing services and MBS data packets related to sports events. In other implementations, for example, if different QoS profiles apply to MBS data packets and unicast data packets, the base station transmits MBS data packets and unicast data packets over the fifth DRB and the sixth DRB, respectively.

[0117] Next reference Figure 4 During scenario 400, base station 104 establishes PDU sessions with multiple UEs. Base station 104 can utilize... Figure 4 The illustrated technique transmits MBS data packets to a first subset of UEs via multicast DRB (i.e., using multicast configuration parameters) and transmits MBS packets to each UE in a second subset of UEs via unicast DRB.

[0118] To establish a PDU session, base station 104 can utilize the above reference. Figures 3A-3C The techniques discussed are for establishing PDU sessions. Specifically, similar to MBS PDU session establishment procedures 350A or 350B, UE 102A can perform MBS PDU session establishment procedures 450A and CN (e.g., CN 110) via base station 104. In some implementations, UE 102A can perform PDU session establishment procedures for both MBS and unicast services, similar to PDU session establishment procedure 350C. Similarly, UE 102B and UE 102C perform MBS PDU session establishment procedures 450B and 450C with CN 110 respectively via base station 104, which can be similar to procedures 350A-C. Base station 104 can perform PDU session establishment procedures 450A-C in any order. Although not detailed in the provided text to avoid confusion... Figure 4 The scene is depicted in the text, but scene 400 may include... Figures 3A-3C Additional messages shown include MBS request messages and messages that include MBS control information (e.g., events 314A-C, 320A-C).

[0119] Base station 104 can use multicast or unicast configuration parameters to configure UE 102A-C to receive MBS data packets. For example, for UE 102C, base station 104 transmits a 452C RRC reconfiguration message to UE 102C, which includes the unicast configuration parameters that UE 102C will use to receive MBS services. The unicast configuration parameters can configure a unicast DRB. In response, UE 102C transmits a 454C RRC reconfiguration complete message. Base station 104 can then transmit a 438MBS data packet to UE 102C according to the unicast configuration parameters. In scenario 400, base station 104 transmits the 452C unicast configuration parameters in a dedicated RRC message.

[0120] Before or after transmitting unicast configuration parameters 452C to UE 102C, base station 104 may transmit an RRC reconfiguration message 442A to UE 102A, including multicast configuration parameters that UE 102A will use to receive MBS services, which may be the same MBS services received by UE 102C. In response, UE 102A transmits an RRC reconfiguration complete message 444A to base station 104. The multicast configuration parameters may be common multicast configuration parameters that base station 104 may transmit to other UEs. For example, base station 104 may transmit an RRC reconfiguration message 442B, including common multicast configuration parameters, to UE 102B. In response, UE 102B transmits an RRC reconfiguration complete message 444B to base station 104. Base station 104 may transmit MBS data packets for the 428 MBS service to UEs 102A and 102B according to the common multicast configuration parameters. In some implementations, multicast configuration parameters may include DL BWP configuration for configuring MBS DL BWP.

[0121] In scenario 400, base station 104 uses dedicated RRC messaging to transmit 442A and 442B multicast configuration parameters to individual UEs 102A and 102B. In other scenarios, base station 104 can broadcast multicast configuration parameters to UEs in cell 124, including UEs 102A and UE 102B, in multiple SIBs. UEs in idle, inactive, or connected states can receive the broadcast parameters, and UEs in connected states can receive dedicated RRC messages.

[0122] In some implementations, before, during, or after the MBS PDU session establishment procedures 450A and 450B, UE102A and UE102B can respectively perform unicast PDU session establishment procedures 460A and 460B with CN 110 via base station 104. UE102A and UE102B can then communicate unicast packets 474A and 474B with CN 110 via base station 110.

[0123] Turning Figure 5 Scenario 500 illustrates message passing that may occur between nodes in a distributed base station system. Base station 104 includes DU 174 and CU 172. The messages exchanged between DU 174 and CU 172 in Scenario 500 could also occur... Figure 3A -Figure C and Figure 4 In the scene illustrated. Furthermore, although not included in the illustration to avoid confusion. Figure 5 As depicted, but scene 500 may include Figures 3A-3C Additional messaging is shown, such as MBS request messages and messages that include MBS control information (e.g., events 314A-C, 320A-C).

[0124] Initially, UE 102 performs an MBS PDU session establishment procedure with CN (e.g., CN 110) via base station 104, similar to MBS PDU session establishment procedures 350A and 350B. In some implementations, UE 102 performs a PDU session establishment procedure for both MBS and unicast services, similar to PDU session establishment procedure 350C. During the MBS PDU session establishment procedure, UE 102 and CU 172 exchange messages with each other via DU 174. For example, UE 102 transmits messages (e.g., PDU session establishment request, RRC reconfiguration complete, MBS request, etc.) to DU 174, and DU 174 then sends a CU-DU message (e.g., UL RRC message delivery message) containing that message to CU 172. Similarly, CU 172 transmits a CU-DU message (e.g., DL RRC message passing message) containing messages (e.g., PDU session establishment acceptance, RRC reconfiguration, MBS control information, etc.) to DU 174, which then sends the message to UE 102.

[0125] CU 172 sends a first CU-to-DU message (502) to DU 174 to request DU to generate multicast configuration parameters for UE 102. The first CU-to-DU message can be, for example, a UE context setup request message or a UE context modification request message. DU 174 can generate the multicast configuration parameters and transmit them to CU 172 (504) in the first DU-to-CU message. The first DU-to-CU message can be, for example, a UE context setup response message or a UE context modification response message. In scenario 502, DU generates multicast configuration parameters (e.g., configuration parameters for configuring MRB). In other scenarios, DU can generate unicast configuration parameters for receiving MBS transmissions, similar to the unicast configuration parameters transmitted by base station 104 in event 452C.

[0126] CU 172 transmits a second CU-DU message 506, including an RRC reconfiguration message containing multicast configuration parameters, to DU 174, and DU 174 forwards a 542 RRC reconfiguration message to UE 102. In response, UE 102 transmits a 544 RRC reconfiguration complete message to DU 174, and DU 174 then transmits a 508 RRC reconfiguration complete message to CU 172 in the second DU-CU message. UE 102 communicates 528 MBS data packets with CN 110 via base station 104, wherein CU 172 transmits MBS data packets to UE 102 via DU 174.

[0127] Figures 6A-15 This is a flowchart illustrating an example method by which a base station and / or UE can manage the exchange of control information and data related to the MBS.

[0128] First turn Figure 6A Example method 600A can be implemented in a UE (e.g., UE 102, 102A, 102B, or 102C). In block 602A, the UE performs a PDU session establishment procedure with a CN (e.g., CN 110) via a RAN (e.g., RAN 105) to establish a PDU session for MBS transmission (e.g., procedures 350A-C, 450A-C, 550). In block 604A, the UE receives an RRC reconfiguration message from the RAN that includes configuration parameters (e.g., events 310A, 324B, 324C, 452C, 442A, 442B, or 542, or similar events in procedures 350B, 350C, 450A-C, or 550). The configuration parameters are associated with the PDU session established in block 602A. For example, the configuration parameters can configure the radio bearers associated with the PDU session (e.g., the configuration parameters can be unicast configuration parameters for DRB or multicast configuration parameters for MRB).

[0129] Next, in box 606A, the UE uses configuration parameters to receive MBS packets for the first MBS service (e.g., events 338A-C, 438, 428, 528). In some implementations, the UE also uses configuration parameters in box 608A to receive MBS packets for the second MBS service.

[0130] Next reference Figure 6BExample method 600B can be implemented in a UE (e.g., UE 102, 102A, 102B, or 102C). Method 600B is similar to method 600A, except that the UE can receive different configuration parameters for receiving the first and second MBS services, respectively. In block 602B, the UE performs a PDU session establishment procedure with a CN (e.g., CN 110) via a RAN (e.g., RAN 105) to establish a PDU session for MBS delivery (e.g., procedures 350A-C, 450A-C, 550). In block 604B, the UE receives a first RRC reconfiguration message from the RAN, which includes first configuration parameters for receiving the first MBS service (e.g., events 310A, 324B, 324C, 452C, 442A, 442B, or 542, or similar events in procedures 350B, 350C, 450A-C, or 550). The first configuration parameter is associated with the PDU session established in box 602B. For example, the first configuration parameter may configure the radio bearer associated with the PDU session (e.g., the first configuration parameter may be a unicast configuration parameter for DRB or a multicast configuration parameter for MRB). Then, in box 606B, the UE uses the first configuration parameter to receive MBS packets (e.g., events 338A-C, 438, 428, 528) from the RAN for the first MBS service.

[0131] In box 608B, the UE also receives a second RRC reconfiguration message from the RAN, which includes second configuration parameters for receiving the second MBS service. Similar to the first configuration parameters, the second configuration parameters can configure the radio bearer (e.g., DRB or MRB) associated with the PDU session. In box 610B, the UE uses the second configuration parameters to receive MBS packets for the second MBS service from the RAN.

[0132] Turning Figure 7AExample method 700A can be implemented in a UE (e.g., UE 102, 102A, 102B, or 102C). In block 702A, the UE performs a PDU session establishment procedure with a CN (e.g., CN 110) via a RAN (e.g., RAN 105) to establish a PDU session for MBS delivery (e.g., procedures 350A-C, 450A-C, 550). In block 704A, the UE receives a first RRC reconfiguration message from the RAN, which includes unicast configuration parameters associated with the PDU session (e.g., events 310A, 324B, 324C, 452C, or 542, or similar events in procedures 350B, 350C, 450A-C, or 550). The unicast configuration parameters can configure the unicast DRB. Then, in box 706A, the UE can receive MBS packets for MBS services from the RAN using unicast configuration parameters (e.g., events 338A-C, 438, 528). Following box 706A, in box 708A, the UE receives a second RRC reconfiguration message from the RAN including multicast configuration parameters (e.g., events 310A, 324B, 324C, 442A, 442B, or 542, or similar events in procedures 350B, 350C, 450A-C, or 550). The multicast configuration parameters can be associated with a PDU session and can be configured for the MRB used to receive MBS services. In box 710A, the UE can switch to receiving MBS packets for MBS services from the RAN using the multicast configuration parameters (e.g., events 338A-C, 428, 528).

[0133] Figure 7B The figure illustrates an example method 700B that can be implemented in a UE (e.g., UE 102, 102A, 102B, or 102C). Method 700B is similar to method 700A, except that the UE initially receives MBS packets according to multicast configuration parameters and subsequently receives MBS packets according to unicast configuration parameters.

[0134] In box 702B, the UE performs a PDU session establishment procedure with the CN (e.g., CN 110) via the RAN (e.g., RAN 105) to establish a PDU session for MBS delivery (e.g., procedures 350A-C, 450A-C, 550). In box 704B, the UE receives from the RAN a first RRC reconfiguration message including multicast configuration parameters associated with the PDU session (e.g., events 310A, 324B, 324C, 442A, 442B, or 542, or similar events in procedures 350B, 350C, 450A-C, or 550). Then, in box 706B, the UE can use the multicast configuration parameters to receive MBS packets for MBS service from the RAN (e.g., events 338A-C, 428, 528). Following box 706B, in box 708B, the UE receives a second RRC reconfiguration message from the RAN, including unicast configuration parameters (e.g., events 310A, 324B, 324C, 452C, or 542, or similar events within procedures 350B, 350C, 450A-C, or 550). The unicast configuration parameters can be associated with a PDU session and can be configured for receiving unicast DRBs for MBS services. In box 710B, the UE can switch to receiving MBS packets for MBS services from the RAN using the unicast configuration parameters (e.g., events 338A-C, 438, 528).

[0135] Figure 7C The figure illustrates an example method 700C that can be implemented in a UE (e.g., UE 102, 102A, 102B, or 102C). Method 700C is similar to methods 700A and 700B, except that the UE can use the configuration parameters in the first RRC reconfiguration message to receive the first MBS service, and use the configuration parameters in the second RRC reconfiguration message to receive the second MBS service.

[0136] In block 702C, the UE performs a PDU session establishment procedure with the CN (e.g., CN 110) via the RAN (e.g., RAN 105) to establish a PDU session for MBS delivery (e.g., procedures 350A-C, 450A-C, 550). In block 704C, the UE receives from the RAN a first RRC reconfiguration message including unicast configuration parameters associated with the PDU session (e.g., events 310A, 324B, 324C, 452C, or 542, or similar events in procedures 350B, 350C, 450A-C, or 550). Then, in block 706C, the UE can use the unicast configuration parameters to receive MBS packets for the first MBS service from the RAN (e.g., events 338A-C, 438, 528). In box 708C, the UE receives a second RRC reconfiguration message from the RAN, including multicast configuration parameters (e.g., events 310A, 324B, 324C, 442A, 442B, or 542, or similar events in procedures 350B, 350C, 450A-C, or 550). The multicast configuration parameters can be associated with a PDU session and can be configured for the MRB used to receive MBS services. In box 710C, the UE can switch to receiving MBS packets for the second MBS service from the RAN using the multicast configuration parameters (e.g., events 338A-C, 428, 528). Although... Figure 7C The diagram illustrates receiving the first MBS service using unicast configuration parameters and receiving the second MBS service using multicast configuration parameters. However, the UE can implement a similar approach, first receiving the first MBS service using multicast configuration parameters and then receiving the second MBS service using unicast configuration parameters. In some implementations, the UE can receive MBS packets for the first MBS service from the RAN using unicast configuration parameters and simultaneously receive MBS packets for the second MBS service from the RAN using multicast configuration parameters.

[0137] Turning Figure 8 Example method 800 can be implemented in a UE (e.g., UE 102, 102A, 102B, or 102C). In method 800, the UE transmits an MBS request via a first DRB associated with the PDU session and receives MBS packets for MBS service via a second DRB associated with the PDU session.

[0138] In block 802, the UE performs a PDU session establishment procedure with a CN (e.g., CN 110) via the RAN (e.g., RAN 105) to establish a PDU session for MBS transmission (e.g., procedures 350A-C, 450A-C, 550). In block 804, the UE receives from the RAN a first RRC reconfiguration message for configuring a first DRB (e.g., a unicast DRB or MRB) associated with the PDU session (e.g., event 310 or a similar event during procedures 350B, 350C, 450A-C, or 550). In block 806, the UE transmits an MBS request for MBS service via the first DRB (e.g., event 314A-C). In response to the MBS request, in block 808, the UE receives from the RAN a second RRC reconfiguration message for configuring a second DRB (e.g., a unicast DRB or MRB) associated with the PDU session (e.g., events 342B, 342C). In box 810, the UE receives MBS packets for MBS service from the RAN via the second DRB (e.g., events 338B, 338C).

[0139] Next reference Figure 9A The base station (e.g., base station 104, 106A, or 106B) can implement example method 900A. Method 900A is similar to method 600A, but method 900A includes steps implemented by the base station instead of the UE.

[0140] In block 902A, the base station receives a CN-BS interface message from the CN (e.g., CN 110) requesting the configuration of radio resources for a PDU session of the UE (e.g., UE 102, 102A, 102B, or 102C) (e.g., events 306A, 322B, 322C, or similar events within procedures 350B, 350C, 450A-C, or 550). In block 904A, in response to the CN-BS interface message, the base station transmits an RRC reconfiguration message to the UE including configuration parameters (e.g., events 310A, 324B, 324C, 452C, 442A, 442B, or 542, or similar events within procedures 350B, 350C, 450A-C, or 550). For example, the configuration parameters may configure the radio bearers associated with the PDU session (e.g., the configuration parameters may be unicast configuration parameters for DRB or multicast configuration parameters for MRB). In box 906A, the base station sends a BS-CN interface message to the CN to indicate that radio resource configuration for the UE has been successful (e.g., events 328B, 328C).

[0141] In block 908A, the base station transmits MBS packets for the first MBS service to the UE using configuration parameters associated with the PDU session (e.g., events 338A-C, 438, 428, 528). In some implementations, the base station also transmits MBS packets for the second MBS service using configuration parameters in block 910A.

[0142] Figure 9B The figure illustrates an example method 900B that can be implemented in a base station (e.g., base station 104, 106A, or 106B). Method 900B is similar to method 900A, except that the base station can use different configuration parameters to transmit the first and second MBS services. Similarly, method 900B is similar to method 600B, but method 900B includes steps implemented by the base station instead of the UE.

[0143] In block 902B, the base station receives a first CN-BS interface message from a CN (e.g., CN 110) requesting the configuration of radio resources for a PDU session of a UE (e.g., UE 102, 102A, 102B, or 102C) (e.g., events 306A, 322B, 322C, or similar events within processes 350B, 350C, 450A-C, or 550). In block 904B, in response to the first CN-BS interface message, the base station transmits a first RRC reconfiguration message to the UE including a first configuration parameter (e.g., events 310A, 324B, 324C, 452C, 442A, 442B, or 542, or similar events within processes 350B, 350C, 450A-C, or 550). For example, the first configuration parameter may configure the radio bearer associated with the PDU session (e.g., the first configuration parameter may be a unicast configuration parameter for DRB or a multicast configuration parameter for MRB). In block 906B, the base station sends a first BS-CN interface message to the CN to indicate that radio resource configuration for the UE is successful (e.g., events 328B, 328C). In block 908B, the base station transmits MBS packets for the first MBS service to the UE using first configuration parameters (e.g., events 338A-C, 438, 428, 528).

[0144] In block 909B, the base station receives a second CN-BS interface message from the CN requesting the configuration of radio resources for a PDU session of the UE (e.g., events 306A, 322B, 322C, or similar events within processes 350B, 350C, 450A-C, or 550). In block 910B, in response to the second CN-BS interface message, the base station transmits a second RRC reconfiguration message to the UE, including second configuration parameters. Similar to the first configuration parameters, the second configuration parameters can configure the radio bearers (e.g., DRB or MRB) associated with the PDU session. In block 912B, the base station sends a second BS-CN interface message to the CN to indicate that the radio resource configuration for the UE has been successful. In block 914B, the base station uses the second configuration parameters to transmit MBS packets for the second MBS service to the UE.

[0145] In one implementation, the CN can request radio resource configuration for a first QoS flow and a second QoS flow in a first CN-BS interface message and a second CN-BS interface message, respectively. Therefore, the base station configures the configuration parameters for the first QoS flow and the second QoS flow in the first RRC reconfiguration message and the second RRC reconfiguration message, respectively. In another implementation, the CN can request radio resource configuration for the first QoS flow and the second QoS flow in a single CN-BS interface message (i.e., the first CN-BS interface message). In this case, event 909B can be skipped. The base station configures the configuration parameters for the first QoS flow and the second QoS flow in the first RRC reconfiguration message and the second RRC reconfiguration message, respectively. Alternatively, the base station configures the configuration parameters for the first QoS flow and the second QoS flow in a single RRC reconfiguration message (i.e., the first RRC reconfiguration message). The base station indicates at event 906B or 912B that the radio resource configuration for the first and second QoS flows is successful, i.e., one of events 906B or 912B can be skipped.

[0146] In any of the above implementations, the CN sends the MBS packet of the first MBS on the first QoS stream and sends the MBS packet of the second MBS to the base station on the second QoS stream. The base station then uses the first configuration parameter and the second configuration parameter to transmit the MBS packet of the first MBS and the MBS packet of the second MBS to the UE respectively.

[0147] Turning Figure 10AThe base station (e.g., base station 104, 106A, or 106B) can implement example method 1000A. Method 1000A is similar to method 700A, but method 1000A includes steps implemented by the base station instead of the UE. In block 1002A, the base station receives from the CN (e.g., CN 110) a first CN-BS interface message (e.g., an event 306A, 322B, 322C, or a similar event within procedures 350B, 350C, 450A-C, or 550) requesting the configuration of radio resources for a PDU session of the UE (e.g., UE 102, 102A, 102B, or 102C). In box 1004A, in response to a CN-BS interface message, the base station transmits a first RRC reconfiguration message to the UE, including unicast configuration parameters (e.g., events 310A, 324B, 324C, 452C, or 542, or similar events in procedures 350B, 350C, 450A-C, or 550). The unicast configuration parameters can configure a unicast DRB. Then, in box 1006A, the base station uses the unicast configuration parameters to transmit MBS packets for MBS service to the UE (e.g., events 338A-C, 438, 528). Following box 1006A, in box 1008A, the base station transmits a second RRC reconfiguration message to the UE, including multicast configuration parameters (e.g., events 310A, 324B, 324C, 442A, 442B, or 542, or similar events in procedures 350B, 350C, 450A-C, or 550). In box 1010A, the base station uses multicast configuration parameters to transmit MBS packets for MBS service to the UE (e.g., events 338A-C, 428, 528).

[0148] Figure 10B The figure illustrates an example method 1000B that can be implemented in a base station (e.g., base station 104, 106A, or 106B). Method 1000B is similar to method 1000A, except that the base station initially transmits MBS packets according to multicast configuration parameters and subsequently transmits MBS packets according to unicast configuration parameters. Similarly, method 1000B is similar to method 700B, but method 1000B includes steps implemented by the base station instead of the UE.

[0149] In block 1002B, the base station receives a first CN-BS interface message from the CN (e.g., CN 110) requesting the configuration of radio resources for a PDU session of a UE (e.g., UE 102, 102A, 102B, or 102C) (e.g., events 306A, 322B, 322C, or similar events within procedures 350B, 350C, 450A-C, or 550). In block 1004B, in response to the CN-BS interface message, the base station transmits a first RRC reconfiguration message to the UE including multicast configuration parameters (e.g., events 310A, 324B, 324C, 442A, 442B, or 542, or similar events within procedures 350B, 350C, 450A-C, or 550). Then, in block 1006B, the base station transmits MBS packets for MBS service to the UE using the multicast configuration parameters (e.g., events 338A-C, 428, 528). Following box 1006B, in box 1008B, the base station transmits a second RRC reconfiguration message to the UE, including unicast configuration parameters (e.g., events 310A, 324B, 324C, 452C, or 542, or similar events in procedures 350B, 350C, 450A-C, or 550). In box 1010B, the base station uses the unicast configuration parameters to transmit MBS packets for MBS service to the UE (e.g., events 338A-C, 438, 528).

[0150] Figure 10C The figure illustrates an example method 1000C that can be implemented in a base station (e.g., base station 104, 106A, or 106B). Method 1000C is similar to methods 1000A and 1000B, except that the base station initially transmits MBS packets for the first MBS service according to unicast configuration parameters, and subsequently transmits MBS packets for the second MBS service according to multicast configuration parameters. Similarly, method 1000C is similar to method 700C, but method 1000C includes steps implemented by the base station instead of the UE.

[0151] In block 1002C, the base station receives a first CN-BS interface message from the CN (e.g., CN 110) requesting the configuration of radio resources for a PDU session of a UE (e.g., UE 102, 102A, 102B, or 102C) (e.g., events 306A, 322B, 322C, or similar events within procedures 350B, 350C, 450A-C, or 550). In block 1004C, in response to the CN-BS interface message, the base station transmits a first RRC reconfiguration message to the UE, including unicast configuration parameters (e.g., events 310A, 324B, 324C, 452C, or 542, or similar events within procedures 350B, 350C, 450A-C, or 550). Then, in block 1006C, the base station transmits an MBS packet for the first MBS service to the UE using the unicast configuration parameters (e.g., events 338A-C, 438, 528). In block 1008C, the base station transmits a second RRC reconfiguration message to the UE, including multicast configuration parameters (e.g., events 310A, 324B, 324C, 442A, 442B, or 542, or similar events in procedures 350B, 350C, 450A-C, or 550). At block 1010C, the base station uses the multicast configuration parameters to transmit MBS packets for the second MBS service to the UE (e.g., events 338A-C, 428, 528). Although... Figure 10C The diagram illustrates transmitting the first MBS service using unicast configuration parameters and the second MBS service using multicast configuration parameters. However, the base station could implement a similar approach, first transmitting the first MBS service using multicast configuration parameters and then transmitting the second MBS service using unicast configuration parameters. In some implementations, for example, if the UE switches to receiving the second MBS MBS packets from the BS, the base station stops transmitting the first MBS MBS packets to the UE after transmitting the second MBS MBS packets. In other implementations, if the UE is able to receive both the first and second MBS simultaneously, or if the UE does not indicate that it is no longer interested in receiving the first MBS or does not indicate that it wishes to stop receiving the first MBS, the base station continues to transmit the first MBS MBS packets to the UE.

[0152] Turning Figure 11Example method 1100 can be implemented in a base station (e.g., base station 104, 106A, or 106B). Method 1100 is similar to method 800, but method 1100 includes steps implemented by the base station instead of the UE. In block 1102, the base station receives a first CN-BS interface message requesting PDU session resources from a CN (e.g., CN 110) (e.g., an event like event 306A or a similar event during processes 350B, 350C, 450A-C, or 550). In block 1104, the base station transmits a first RRC reconfiguration message to the UE (e.g., UE 102, 102A, 102B, or 102C) for configuring a first DRB (e.g., a unicast DRB or MRB) associated with the PDU session (e.g., an event like event 310 or a similar event during processes 350B, 350C, 450A-C, or 550). In block 1106, the base station receives an MBS request from the UE via a first DRB for requesting MBS services (e.g., events 314A-C). The base station may forward the MBS request to the CN (e.g., events 316A-C). In block 1108, the base station receives a second CN-BS interface message from the CN for requesting resources for a PDU session (e.g., events 322B, 322C). In response, in block 1110, the base station transmits a second RRC reconfiguration message to the UE for configuring a second DRB (e.g., a unicast DRB or MRB) associated with the PDU session (e.g., events 342B, 342C). In block 1112, the base station transmits MBS packets for MBS services to the UE via the second DRB (e.g., events 338B, 338C).

[0153] In some implementations, the CN can request radio resource configuration for the first QoS flow and the second QoS flow in the first CN-BS interface message and the second CN-BS interface message, respectively. Therefore, the base station configures the first DRB for the first QoS flow and the second DRB for the second QoS flow in the first RRC reconfiguration message and the second RRC reconfiguration message, respectively. The CN sends MBS data packets of MBS to the base station on the second QoS flow, and the base station then transmits MBS data packets of MBS to the UE via the second DRB. The CN can also transmit MBS control information of MBS to the base station on the first QoS flow, and the base station then transmits the MBS control information via the first DRB.

[0154] Next reference Figure 12Example method 1200 can be implemented in a CU (e.g., CU 172). In block 1202, the CU sends a CU-DU message to a DU (e.g., DU 174) to request MBS service (e.g., event 502). In block 1204, the CU receives a DU-CU message from the DU including multicast configuration parameters (e.g., event 504). Next, in block 1206, the CU transmits an RRC reconfiguration message including multicast configuration parameters to a UE (e.g., UE 102, 102A, 102B, or 102C) via the DU (e.g., events 506, 542). In block 1208, the CU transmits an MBS packet for MBS service to the UE via the DU (e.g., event 528).

[0155] Next reference Figure 13 Example method 1300 can be implemented in a DU (e.g., DU 174). In block 1302, the DU receives a CU-DU message from a CU requesting MBS service (e.g., CU 172) (e.g., event 502). In block 1304, in response to the CU-DU message, the DU sends a DU-CU message to the CU including multicast configuration parameters (e.g., event 504). Then, in block 1306, the DU can use the multicast configuration parameters to transmit MBS packets for MBS service to a UE (e.g., UE 102, 102A, 102B, or 102C) (e.g., event 528).

[0156] Go to Figure 14 Example method 1400 can be implemented in a base station (e.g., base station 104, 106A, or 106B) for managing MBS communications. The base station can use processing hardware (e.g., processing hardware 130 or 140) to perform method 1400. In block 1402, the base station prompts the establishment of a session (e.g., PDU session) (e.g., procedures 350B, 350C, 450A-C, or 550) for transmitting MBS data packets from a CN (e.g., CN 110) to a UE (e.g., UE 102, 102A, 102B, or 102C). Prompting the establishment of the session may include configuring radio resources (e.g., DRB) for the session. In block 1404, the base station transmits session-related configuration parameters to the UE (e.g., events 310A, 324B, 324C, 452C, 442A, 442B, or 542, or similar events in procedures 350B, 350C, 450A-C, or 550). The configuration parameters can be unicast configuration parameters (e.g., parameters configuring a unicast DRB) or multicast configuration parameters (e.g., parameters configuring a multicast DRB such as an MRB). In block 1406, the base station transmits MBS data packets to the UE according to the configuration parameters (e.g., events 338A-C, 438, 428, 528).

[0157] Next reference Figure 15 Example method 1500 can be implemented in a UE (e.g., UE 102, 102A, 102B, or 102C) for managing MBS reception. The UE can use processing hardware (e.g., processing hardware 150) to perform method 1500. In block 1502, the UE establishes a session (e.g., PDU session) (e.g., procedures 350B, 350C, 450A-C, or 550) for receiving MBS data packets from a CN (e.g., CN 110) via a base station (e.g., base station 104, 106A, or 106B). In block 1504, the UE receives configuration parameters associated with the session from the base station (e.g., events 310A, 324B, 324C, 452C, 442A, 442B, or 542, or similar events in procedures 350B, 350C, 450A-C, or 550). Configuration parameters can be unicast configuration parameters (e.g., parameters for configuring a unicast DRB) or multicast configuration parameters (e.g., parameters for configuring a multicast DRB such as an MRB). In box 1506, the UE receives MBS data packets (e.g., events 338A-C, 438, 428, 528) from the base station according to the configuration parameters.

[0158] The following list of examples reflects various embodiments explicitly contemplated by this disclosure:

[0159] Example 1. A method for managing multicast and / or broadcast service (MBS) communications in a base station, the method comprising: having processing hardware of the base station prompt the establishment of a session for transmitting MBS data packets from a core network (CN) to a user equipment (UE); having the processing hardware transmit configuration parameters associated with the session to the UE; and having the processing hardware transmit the MBS data packets to the UE according to the configuration parameters.

[0160] Example 2. According to the method of Example 1, wherein prompting the establishment of a session includes: configuring a unicast data radio bearer (DRB).

[0161] Example 3. According to the method described in Example 1, wherein prompting the establishment of a session includes: configuring a multicast DRB.

[0162] Example 4. According to the method of Example 1, wherein prompting the establishment of a session includes: configuring a DRB for transmitting MBS data packets and unicast data packets.

[0163] Example 5. The method according to any of Examples 1-4, wherein, in response to receiving a request for MBS service from the UE, the transmission of MBS data packets occurs.

[0164] Example 6. The method according to Example 5, wherein: initiating the establishment of a session includes configuring a data radio bearer (DRB) associated with the session; and receiving a request includes receiving the request via the DRB.

[0165] Example 7. The method according to either Example 5 or 6, wherein: transmitting configuration parameters includes transmitting configuration parameters for configuring a new DRB associated with the session after the session is established; and transmitting MBS data packets includes transmitting MBS data packets through the new DRB.

[0166] Example 8. The method according to Example 5, wherein receiving the request includes receiving the request in a message associated with a protocol for controlling radio resources.

[0167] Example 9. The method according to any of Examples 1-4, wherein the base station transmits MBS data packets in response to receiving a message from the CN.

[0168] Example 10. The method according to any of the preceding examples, wherein: the session is associated with a first DRB; the method further includes: receiving a request for a unicast service from the UE by processing hardware; and transmitting unicast configuration parameters of a second DRB for receiving the unicast service through the UE by the processing hardware.

[0169] Example 11. The method according to any of the preceding examples, wherein the UE is a first UE and the session is a first session, the method further comprising: having processing hardware prompt the establishment of a second session for transmitting MBS data packets from the CN to the second UE; and having processing hardware transmit unicast configuration parameters to the second UE to configure a second unicast DRB for transmitting MBS data packets to the second UE.

[0170] Example 12. The method according to any of Examples 1-10, wherein the UE is a first UE and the session is a first session, the method further comprising: activating a second session by processing hardware for transmitting MBS data packets from the CN to the second UE; and transmitting configuration parameters to the second UE by processing hardware.

[0171] Example 13. The method according to Example 1 or any of Examples 3-12, wherein transmitting MBS data packets includes: (i) transmitting MBS data packets to a first subset of UEs including the UE via a multicast DRB, and (ii) transmitting MBS data packets to each UE of a second subset of UEs via a unicast DRB.

[0172] Example 14. The method according to any of the preceding examples, wherein the MBS packet is a first MBS packet of a first MBS service and the configuration parameter is a first configuration parameter, the method further comprising: transmitting a second configuration parameter associated with a session to the UE by processing hardware; and transmitting a second MBS packet of a second MBS service to the UE by processing hardware according to the second configuration parameter.

[0173] Example 15. The method according to any of the examples 1-13, wherein transmitting MBS packets includes a first MBS packet transmitting a first MBS and a second MBS packet transmitting a second MBS.

[0174] Example 16. The method according to any one of Examples 1-15 includes: transmitting a CU-DU message from a central unit (CU) of a base station to a distributed unit (DU) of a base station by processing hardware for requesting configuration parameters for a UE to receive MBS data packets; receiving the configuration parameters from the DU at the CU by processing hardware; transmitting the configuration parameters from the CU to the UE via the DU; and transmitting MBS data packets from the CU to the UE via the DU.

[0175] Example 17. The method according to any of the preceding examples further includes: transmitting application-level messages related to MBS packets to the UE by the processing hardware using a session.

[0176] Example 18. The method according to Example 17, wherein transmitting the application-level message includes transmitting a security key associated with the MBS packet.

[0177] Example 19. The method according to any of the preceding examples, wherein prompting the establishment of a session includes prompting the establishment of a Protocol Data Unit (PDU) session.

[0178] Example 20. The method according to any of the preceding examples, wherein transmitting the configuration parameters includes transmitting the configuration parameters in a message associated with a protocol for controlling radio resources.

[0179] Example 21. A base station including processing hardware and configured to implement a method according to any of the preceding examples.

[0180] Example 22. A method for managing the reception of multicast and / or broadcast services (MBS) in a user equipment (UE), the method comprising: establishing a session by processing hardware of the UE for receiving MBS data packets from a core network (CN) via a base station; receiving configuration parameters associated with the session by the processing hardware from the base station; and receiving MBS data packets from the base station by the processing hardware according to the configuration parameters.

[0181] Example 23. The method according to Example 22, wherein establishing a session includes: configuring a unicast data radio bearer (DRB).

[0182] Example 24. The method described in Example 22, wherein establishing a session includes: configuring a multicast DRB.

[0183] Example 25. The method according to Example 22, wherein establishing a session includes: configuring a DRB for receiving MBS data packets and unicast data packets.

[0184] Example 26. The method according to any of Examples 22-25 further includes: transmitting a request for MBS service to the base station by processing hardware before receiving the MBS packet.

[0185] Example 27. The method according to Example 26, wherein: establishing a session includes configuring a data radio bearer (DRB) associated with the session; and transmitting the request includes transmitting the request via the DRB.

[0186] Example 28. The method according to any of Examples 26 or 27, wherein: receiving configuration parameters includes receiving configuration parameters for configuring a new DRB associated with the session after the session is established; and receiving MBS data packets includes receiving MBS data packets through the new DRB.

[0187] Example 29. The method according to Example 26, wherein transmitting the request includes transmitting the request in a message associated with a protocol for controlling radio resources.

[0188] Example 30. The method according to any of Examples 22-29, wherein: the session is associated with a first DRB; the method further includes: transmitting a request for unicast service to a base station by processing hardware; and receiving unicast configuration parameters of a second DRB through which the processing hardware receives unicast service from the base station.

[0189] Example 31. The method according to any of Examples 22-30, wherein the MBS packet is a first MBS packet of a first MBS service and the configuration parameter is a first configuration parameter, the method further comprising: receiving a second configuration parameter associated with a session from a base station by processing hardware; and receiving a second MBS packet of a second MBS from a base station by processing hardware according to the second configuration parameter.

[0190] Example 32. The method according to any of the examples 22-31, wherein receiving MBS packets includes receiving a first MBS packet of a first MBS and a second MBS packet of a second MBS.

[0191] Example 33. The method according to any of Examples 22-32 further includes: receiving application-level messages related to MBS packets from the base station using a session by processing hardware.

[0192] Example 34. The method according to Example 33, wherein receiving application-level messages includes receiving a security key associated with an MBS packet.

[0193] Example 35. The method described in any of Examples 22-34, wherein establishing a session includes establishing a Protocol Data Unit (PDU) session.

[0194] Example 36. The method according to any of Examples 22-35, wherein receiving configuration parameters includes receiving configuration parameters in a message associated with a protocol for controlling radio resources.

[0195] Example 37. A user equipment (UE) includes processing hardware and is configured to implement the method according to any one of Examples 22-36.

[0196] The following additional considerations apply to the foregoing discussion.

[0197] User equipment (e.g., UE 102) that can implement the technologies of this disclosure can be any suitable device capable of wireless communication, such as a smartphone, tablet computer, laptop computer, mobile game console, point-of-sale (POS) terminal, health monitoring device, drone, camera, media streaming dongle or other personal media device, wearable device such as a smartwatch, wireless hotspot, femtocellular base station, or broadband router. Furthermore, in some cases, the user equipment can be embedded in electronic systems, such as the head unit of a vehicle or an advanced driver assistance system (ADAS). Additionally, the user equipment can operate as an Internet of Things (IoT) device or a mobile internet device (MID). Depending on the type, the user equipment may include one or more general-purpose processors, computer-readable storage, a user interface, one or more network interfaces, one or more sensors, etc.

[0198] Some embodiments described in this disclosure include logic or multiple components or modules. A module can be a software module (e.g., code stored on a non-transitory machine-readable medium) or a hardware module. A hardware module is a tangible unit capable of performing certain operations and can be configured or arranged in some manner. A hardware module may include dedicated circuitry or logic that is permanently configured (e.g., as a dedicated processor, such as a field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC)) to perform certain operations. A hardware module may also include programmable logic or circuitry (e.g., encompassed within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. The decision to implement a hardware module in dedicated and permanently configured circuitry or in temporarily configured circuitry (e.g., software-configured) may be driven by cost and time considerations.

[0199] When implemented in software, these technologies can be provided as part of an operating system, a library used by multiple applications, or a specific software application. This software can be executed by one or more general-purpose processors or one or more dedicated processors.

[0200] By reading this disclosure, those skilled in the art will understand alternative structural and functional designs for communicating MBS information based on the principles disclosed herein. Therefore, although specific embodiments and applications have been illustrated and described, it should be understood that the disclosed embodiments are not limited to the precise constructions and components disclosed herein. Various modifications, alterations, and variations that will be apparent to those skilled in the art may be made to the arrangement, operation, and details of the methods and apparatus disclosed herein without departing from the spirit and scope defined in the appended claims.

Claims

1. A method for managing communications of multicast and / or broadcast services (MBS) in a base station, the method comprising: The base station triggers the establishment of a first session for transmitting MBS data packets from the core network CN to the first user equipment UE, the triggering including receiving a first request from the first UE to establish a first PDU session, the first request indicating MBS service; Send the first request to CN; The base station transmits configuration parameters associated with the first session to the first UE; The base station prompts the establishment of a second session for transmitting MBS data packets from the CN to the second UE, the prompting including receiving a second request from the second UE to establish a second PDU session, the second request indicating the MBS service; Send the second request to CN; The base station transmits the configuration parameters to the second UE; and The base station transmits the MBS data packets to the first UE and the second UE according to the configuration parameters.

2. The method according to claim 1, wherein, The establishment of the first session includes: Configure the DRB for transmitting the MBS data packets and unicast data packets.

3. The method according to any one of the preceding claims, wherein: The first session is associated with the first DRB; The method also includes: The base station receives a request for unicast service from the first UE; and The base station transmits unicast configuration parameters for the second DRB to the first UE, and the first UE receives the unicast service through the second DRB.

4. The method according to any one of the preceding claims, wherein, Transmitting the MBS data packets includes: (i) transmitting the MBS data packets to a first subset of UEs including the first UE and the second UE via a multicast DRB, and (ii) transmitting the MBS data packets to each UE of a second subset of UEs via a unicast DRB.

5. The method according to any one of the preceding claims, wherein, The MBS data packet is the first MBS data packet of the first MBS service, and the configuration parameter is the first configuration parameter. The method further includes: The base station transmits second configuration parameters associated with the first session to the first UE; and The base station transmits the second MBS data packet of the second MBS service to the first UE according to the second configuration parameters.

6. The method according to any one of the preceding claims, comprising: The base station transmits a CU-DU message from its central unit (CU) to its distributed unit (DU) to request the first UE to use the configuration parameters for receiving the MBS data packets. The base station receives the configuration parameters from the DU at the CU. The configuration parameters are transmitted from the CU to the first UE via the DU; and The MBS data packet is transmitted from the CU to the first UE via the DU.

7. The method according to any one of the preceding claims further comprises: The base station uses the first session to transmit application-level messages related to the MBS data packets to the first UE.

8. The method according to claim 7, wherein, Transmitting the application-level message includes transmitting a security key associated with the MBS data packet.

9. The method according to any one of the preceding claims, wherein, Transmitting the configuration parameters to the first UE includes transmitting the configuration parameters in a message associated with a protocol for controlling radio resources.

10. A base station including processing hardware and configured to implement the method according to any one of the preceding claims.

11. A method for managing the reception of multicast and / or broadcast services (MBS) in a user equipment (UE), the method comprising: The UE establishes a Protocol Data Unit (PDU) for receiving MBS data packets from the core network (CN) via a base station, the establishment of which includes: A request is sent to the base station to establish a PDU session, the request instructing the MBS service. as well as Receive multicast configuration parameters associated with the PDU session from the base station; The UE receives multicast configuration parameters associated with the session from the base station; The UE receives the MBS data packets from the base station according to the multicast configuration parameters; The UE receives unicast configuration parameters associated with the session from the base station; and The UE receives the MBS data packets from the base station according to the unicast configuration parameters.

12. The method according to claim 11, wherein, Receiving the unicast configuration parameters includes: Receive the unicast configuration parameters used to configure the unicast data radio bearer (DRB).

13. The method according to claim 11, wherein, Receiving the multicast configuration parameters includes: Receive the multicast configuration parameters used to configure the multicast DRB.

14. The method according to any one of claims 11-13, wherein, Receiving the multicast configuration parameters includes receiving the multicast configuration parameters in a message associated with a protocol for controlling radio resources.

15. A user equipment (UE) including processing hardware and configured to implement the method according to any one of claims 11-14.

Images