Configuring resources for multicast and / or broadcast services in distributed base station architecture

By coordinating the operation of CU and DU, the problem of unclear MBS resource configuration in the distributed base station architecture is solved, and effective MBS data transmission is achieved, ensuring that UE can receive data from multicast and broadcast services.

CN118901250APending Publication Date: 2024-11-05GOOGLE LLC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380023247.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-04-28
Filing Date
2023-01-06
Publication Date
2024-11-05

AI Technical Summary

Technical Problem

In a distributed base station architecture, it remains unclear how to effectively configure resources to enable the transmission of multicast and/or broadcast service (MBS) data.

Method used

Through coordinated operation of the central unit (CU) and the distributed unit (DU), the CU sends MBS session information and resource configuration requests to the DU. The DU generates or receives relevant configuration information and sends MBS broadcast configuration messages to the UE to ensure that the UE can receive the configuration parameters of the MBS session.

Benefits of technology

This enables efficient resource configuration in a distributed base station architecture, ensuring that the UE can receive data from multicast and/or broadcast services, thereby improving the efficiency and reliability of MBS data transmission.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118901250A_ABST
    Figure CN118901250A_ABST
Patent Text Reader

Abstract

Comprising a central unit (CU) and a distributed unit (DU) may implement a method for configuring a user equipment (UE) to receive a multicast and / or broadcast service (MBS). The method may comprise: receiving (1002), from the CU, a CU-to-DU message identifying an MBS session and requesting the DU to configure resources for the MBS session; and in response to receiving the CU-to-DU message, transmitting (1004) configuration parameters to the UE for receiving the MBS session.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to wireless communications, and more particularly to enabling broadcast communications for multicast and / or broadcast services (MBS) in a distributed or disaggregated base station architecture. Background Art

[0002] The background description provided herein is for the purpose of generally presenting the context of the present disclosure. The work of the presently named inventors, to the extent that it is described in this background section, and aspects of the description that may not otherwise be identified as prior art at the time of filing, are neither explicitly nor implicitly admitted as prior art to the present disclosure.

[0003] In telecommunication systems, the Packet Data Convergence Protocol (PDCP) sublayer of the radio protocol stack provides services such as user plane data transmission, encryption, integrity protection, etc. For example, the PDCP sublayer defined for the Evolved Universal Terrestrial Radio Access (EUTRA) radio interface (see the Third Generation Partnership Project (3GPP) specification TS 36.323) and the New Radio (NR) (see the 3GPP specification TS38.323) provides sequencing of protocol data units (PDUs) in the uplink direction from a user device (also referred to as user equipment or "UE") to a base station and in the downlink direction from a base station to a UE. The PDCP sublayer also provides services of signaling radio bearers (SRBs) to the radio resource control (RRC) sublayer. The PDCP sublayer further provides services of data radio bearers (DRBs) to the service data adaptation protocol (SDAP) sublayer or protocol layers such as the Internet Protocol (IIP) layer, the Ethernet protocol layer, and the Internet Control Message Protocol (II CMP) layer. In general, the UE and the 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, the UE may simultaneously utilize resources of multiple nodes (e.g., base stations or components of distributed base stations or decomposed base stations) of a radio access network (RAN) interconnected by backhaul, which is called dual connection (DC) operation. These network nodes may all be nodes using the same radio access technology (RAT), or may include nodes using different RATs. Example DC configurations include NR-only dual connection (NR-DC) and EUTRA and NR dual connection (EN-DC). When the UE operates in DC, the cell associated with the base station used as the master node (MN) defines a master cell group (MCG), while the cell associated with the base station used as the secondary node (SN) defines a secondary cell group (SCG). The MCG covers the primary cell (PCel l) and zero, one or more secondary cells (SCel l), and the SCG covers the primary and secondary cells (PSCel l) and zero, one or more SCel l. 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 in a single connection (SC). UEs in the SC communicate with the MN only via the MCG. The base station and / or the UE determine when the UE should establish a radio connection with another base station. For example, the base station may determine to hand over the UE to another base station and initiate a handover procedure. UEs in other scenarios may simultaneously utilize resources of another RAN node (e.g., a base station or a component of a distributed or decomposed base station) interconnected by a backhaul.

[0005] There are several types of SRBs and DRBs that a UE can use. So-called "SRB1" resources carry RRC messages including NAS messages on a dedicated control channel (DCCH) in some cases, while "SRB2" resources support RRC messages including logged measurement information or NAS messages also on the DCCH, but with lower priority than SRB1 resources. More generally, SRB1 and SRB2 resources allow the UE and MN to exchange RRC messages related to the MN and embed RRC messages related to the SN, and may also be referred to as MCG SRBs. "SRB3" resources allow the UE and SN to exchange RRC messages related to the SN, and may also be referred to as SCG SRBs. Split SRBs allow the UE to exchange RRC messages directly with the MN via the lower layer resources of the MN and the SN. In addition, a DRB that terminates at the MN and uses only the lower layer resources of the MN may be referred to as an MCG DRB, a DRB that terminates at the SN and uses only the lower layer resources of the SN may be referred to as an SCG DRB, and a DRB that terminates at the MN or SN but uses the lower layer resources of both the MN and the SN may be referred to as a split DRB. A DRB that is terminated at the MN but uses only the lower layer resources of the SN may be referred to as an MN-terminated SCG DRB. A DRB that is terminated at the SN but uses only the lower layer resources of the MN may be referred to as an SN-terminated MCG DRB.

[0006] Whether in SC or DC operation, the UE can perform a handover procedure from one cell to another. These procedures involve messaging (e.g., RRC signaling and preparation) between the RAN node and the UE. Depending on the scenario, the UE can switch from a cell of a serving base station to a target cell of a target base station, or from a cell of a first distributed unit (DU) of a serving base station to a target cell of a second DU of the same base station. In a DC scenario, the UE can perform a PSCell change procedure to change the PSCell. These procedures involve messaging (e.g., RRC signaling and preparation) between the RAN node and the UE. Depending on the scenario, the UE can perform a PSCell change from the PSCell of a serving SN to the target PSCell of a target SN, or from the PSCell of a source DU of a base station to the PSCell of a target DU of the same base station. In addition, the UE can perform a handover or PSCell change within a cell for synchronous reconfiguration.

[0007] Base stations operating according to the fifth generation (5G) New Radio (NR) requirements support much larger bandwidths than fourth generation (4G) base stations. Therefore, the Third Generation Partnership Project (3GPP) has proposed, for Release 15, that user equipment units (UEs) support 100 MHz bandwidth in frequency range 1 (FR1) and 400 MHz bandwidth in frequency range (FR2). Since the bandwidth of a typical carrier in 5G NR is relatively wide, 3GPP has proposed for Release 17 that 5G NR base stations be able to provide multicast and / or broadcast services (MBS) to UEs. MBS can be used for many content delivery applications, such as, for example, transparent IPv4 / IPv6 multicast delivery, IPTV, wireless software delivery, group communications, Internet of Things (IoT) applications, V2X applications, and emergency messages related to public safety.

[0008] 5G NR provides point-to-point (PTP) and point-to-multipoint (PTM) delivery methods for transmitting MBS packet streams over the radio interface. In PTP communication, the RAN node transmits different copies of each MBS data packet to different UEs over the radio interface, while in PTM communication, the RAN node transmits a single copy of each MBS data packet to multiple UEs over the radio interface. However, in some scenarios, it is not clear how the distributed base stations configure resources to transmit MBS data packets via broadcast. Summary of the invention

[0009] A network node operating as a central unit (CU) or a distributed unit (DU) of a distributed base station may implement the techniques of the present disclosure for configuring resources for a multicast and / or broadcast service (MBS). For example, the CU may receive a message from a core network (CN) requesting a distributed base station to establish resources for an MBS session. In response, the CU may send a CU-to-DU message (e.g., an MBS context establishment request message) to the DU that identifies the MBS session (e.g., using a session identifier (ID) corresponding to the session) and requests the DU to configure resources for the MBS session. The DU may then send an MBS broadcast configuration message to the UE (or more specifically, broadcast an MBS broadcast configuration message to one or more UEs), the MBS broadcast configuration message including a list of one or more MBS sessions and MBS session information for each corresponding MBS session. The MBS session information for the MBS session includes configuration parameters that enable the UE to receive MBS data for the MBS session, such as a Packet Data Convergence Protocol (PDCP) configuration, a Radio Link Control (RLC) configuration, a Discontinuous Reception (DRX) configuration, a Group Radio Network Temporary Identifier (G-RNTI) associated with the MBS session, and / or a session ID for the MBS session.

[0010] Depending on the implementation, the CU or DU may generate the MBS broadcast configuration message or the MBS session information. In some implementations, the DU generates the MBS session information and the MBS broadcast configuration message. The DU may receive configurations associated with the layers operated by the CU from the CU and include these configurations in the MBS session information. For example, the DU receives a PDCP configuration or a DRX configuration from the CU. The DU may then generate information such as a G-RNTI and RLC configuration at the layers operated by the DU and include such information in the MBS session information.

[0011] In other implementations, the CU generates the MBS session information and may or may not generate the MBS broadcast configuration message. In such implementations, the CU may receive the RLC configuration and G-RNTI for the MBS session from the DU and include the RLC configuration and G-RNTI in the MBS session information together with the configuration generated by the CU (such as the PDCP configuration and the DRX configuration). In some scenarios, the CU sends the MBS session information to the DU so that the DU can generate the MBS broadcast configuration message and send it to the UE. Alternatively, the CU may generate an MBS broadcast configuration message including the MBS session information and send the MBS broadcast configuration message to the DU for forwarding to the UE.

[0012] As described above, the MBS broadcast configuration message may include MBS session information for more than one MBS session. In order to request resources for the second MBS session, the CU may send a second CU-to-DU message identifying the second MBS session to the DU, or the CU may send a single CU-to-DU message identifying both the first MBS session and the second MBS session. The DU may then send MBS broadcast configuration information including both the first and second MBS session information for the first and second MBS sessions, respectively. In the event that the CU determines to suspend or release resources for the first MBS session (e.g., in response to a request from the CN), the CU sends a request to the DU. In response, the DU may stop transmitting the first MBS session information and instead transmit an MBS broadcast configuration message that does not include the first MBS session information but includes the second MBS session information. The CU may also request the DU to modify the resources used for the MBS session, in which case the DU may update the MBS session information of the MBS session accordingly and transmit an MBS broadcast configuration message including the updated MBS session information.

[0013] An example embodiment of these techniques is a method for configuring a UE to receive MBS implemented in a DU of a distributed base station including a CU and a DU. The method may be performed by processing hardware and includes: receiving a CU-to-DU message from the CU identifying an MBS session and requesting the DU to configure resources for the MBS session; and in response to receiving the CU-to-DU message, transmitting configuration parameters for receiving the MBS session to the UE.

[0014] Another example embodiment of these techniques is a method for configuring a UE to receive MBS implemented in a CU of a distributed base station including a CU and a DU. The method may be performed by processing hardware and includes: receiving a CN to BS message from a core network (CN) requesting the distributed base station to configure resources for an MBS session; and transmitting a CU to DU message identifying the MBS session to the DU so that the DU transmits configuration parameters for receiving the MBS session to the UE.

[0015] Yet another example embodiment of the techniques is a network node comprising processing hardware and configured to implement any of the methods described above. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1A is a block diagram of an example system in which techniques for managing resources for MBS of the present disclosure may be implemented;

[0017] Figure 1B The central unit (CU) and distributed unit (DU) can be Figure 1A A block diagram of an example base station operating in a system of FIG.

[0018] Figure 2Ayes Figure 1A The UE can Figure 1A A block diagram of an example protocol stack for base station communications;

[0019] Figure 2B yes Figure 1A A block diagram of an example protocol stack according to which a UE may communicate with a DU and a CU of a base station;

[0020] Figure 3 is a block diagram illustrating an example tunnel architecture for an MBS session and a PDU session;

[0021] Figure 4 is a block diagram illustrating example MRBs and DRBs that a distributed base station may configure for communicating multicast, broadcast, and / or unicast traffic with a UE;

[0022] Figure 5A is a message passing diagram for an example scenario in which a CN and a distributed base station configure resources for transmitting MBS data for an MBS session to multiple UEs via broadcast, wherein the DU generates MBS session information using a Packet Data Convergence Protocol (PDCP) configuration received from the CU in an MBS Context Setup Request message and broadcasts the MBS session information in an MBS Broadcast Configuration message;

[0023] Figure 5B is with Figure 5A Message passing diagram for an example scenario similar to the scenario of , but where the DU receives the PDCP configuration of the CU to DU message after receiving the MBS context setup request message;

[0024] Figure 5C is with Figure 5A Message passing diagram of an example scenario similar to the scenario of , but where the CU generates MBS session information using a radio link control (RLC) configuration received from the DU in an MBS context setup response message, and transmits the MBS session information to the DU.

[0025] Figure 5D is with Figure 5C Message passing diagram for an example scenario similar to the scenario of , but where the CU receives the RLC configuration in the DU to CU message after receiving the MBS Context Setup Response message;

[0026] Figure 5E is with Figure 5A Message passing diagram for an example scenario similar to the scenario of , but where the DU generates MBS session information without receiving PDCP configuration from the CU;

[0027] Fig. 5F It is possible to FIG. 5A to FIG. 5EA message passing diagram for an example scenario similar to any of the illustrated scenarios, wherein the distributed base station later releases resources for the MBS session;

[0028] Figure 5G It is possible to FIG. 5A to FIG. 5E A message passing diagram for an example scenario similar to any of the illustrated scenarios, where the distributed base station later suspends and resumes resources for the MBS session;

[0029] Figure 5H It is possible to FIG. 5A to FIG. 5E a message passing diagram for an example scenario similar to any of the illustrated scenarios, wherein the distributed base station also configures resources for transmitting MBS data for another MBS session via broadcast, and later releases the resources for the initial MBS session;

[0030] Fig.5I It is possible to FIG. 5A to FIG. 5E A message passing diagram for an example scenario similar to any of the scenarios shown, wherein the distributed base station later modifies the resources used for the MBS session;

[0031] Fig. 6A is a flow chart of an example method that may be implemented in a DU for configuring resources for one or more MBS sessions, wherein the DU receives a session identifier (ID) for the corresponding one or more MBS sessions in a corresponding CU-to-DU message;

[0032] Figure 6B is with Fig. 6A A flowchart of an example method similar to the method of , but wherein the DU receives a session ID for corresponding one or more MBS sessions in a single CU-to-DU message;

[0033] Fig. 7A is a flow chart of an example method that may be implemented in a CU for configuring resources for one or more MBS sessions, wherein the CU transmits a session ID for the corresponding one or more MBS sessions in a corresponding CU-to-DU message;

[0034] Figure 7B is with Fig. 7A A flowchart of an example method similar to the method of , but wherein the CU transmits a session ID for corresponding one or more MBS sessions in a single CU-to-DU message;

[0035] Fig. 8A is a flow chart of an example method that may be implemented in a DU for suspending or releasing resources for an MBS session;

[0036] Figure 8B is a flow chart of an example method that may be implemented in a DU for modifying resources for an MBS session;

[0037] Fig. 9A is a flow chart of an example method that may be implemented in a CU for suspending or releasing resources for an MBS session;

[0038] Fig. 9B is a flow chart of an example method that may be implemented in a CU for modifying resources for an MBS session;

[0039] Fig.10 is a flow chart of an example method that may be implemented in a DU for configuring resources for an MBS; and

[0040] Fig.11 is a flow chart of an example method that may be implemented in a CU for configuring resources for an MBS. DETAILED DESCRIPTION

[0041] In general, the RAN and / or CN implement the techniques of the present disclosure to manage the transmission of a multicast and / or broadcast service (MBS). The CN may request a base station to configure a common downlink (DL) tunnel for multiple UEs, and the CN may transmit MBS data for an MBS session to the base station via the common DL tunnel. In response to the request, the base station transmits the configuration of the common DL tunnel to the CN. The configuration may include transport layer information such as an Internet Protocol (IIP) address and a tunnel identifier (e.g., a tunnel endpoint identifier (TEID)).

[0042] The base station may also configure one or more logical channels toward the UE, and / or one or more MBS radio bearers (MRBs) associated with the MBS session, where there may be a one-to-one mapping between each logical channel and each MRB. After receiving MBS data for the MBS session via a common DL tunnel, the base station may transmit the MBS data to one or more UEs that have joined the MBS session via one or more logical channels. In some implementations, the base station transmits MBS data to multiple UEs via a single logical channel. In addition, if there are multiple quality of service (QoS) flows for the MBS session, a single logical channel may be associated with multiple QoS flows, or there may be a one-to-one mapping between each QoS flow and each logical channel.

[0043] The CN can enable the base station to configure a common DL tunnel before or after the UE joins the MBS session. If an additional UE joins the MBS session after the tunnel is configured, the CN can transmit the MBS data of multiple UEs to the base station using the same common DL tunnel.

[0044] Figure 1AAn example wireless communication system 100 is depicted in which the disclosed techniques for managing transmission and reception of multicast and / or broadcast service (MBS) information may be implemented. The wireless communication system 100 includes user equipment (UE) 102A, 102B, 103, and base stations 104, 106 of a radio access network (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 noted. In other implementations or scenarios, the wireless communication system 100 may instead include more than one UE. Figure 1A More or fewer UEs and / or more or fewer base stations are shown. Base stations 104, 106 can be one or more base stations of any suitable type, 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 station 106 can be a gNB.

[0045] Base station 104 supports cell 124, while base station 106 supports cell 126. Cell 124 partially overlaps with cell 126, so that UE 102A can be within the range of communicating with base station 104 while being within the range of communicating with base station 106 (or within the range of detecting or measuring a signal from base station 106). For example, the overlap can enable UE 102A to switch between cells (e.g., from cell 124 to cell 126) or between base stations (e.g., from base station 104 to base station 106) before UE 102A experiences a radio link failure. In addition, the overlap allows various dual connectivity (DC) scenarios. For example, UE 102A can communicate with base station 104 (acting as a master node (MN)) and base station 106 (acting as a secondary node (SN)) in DC. When UE 102A is in DC with base station 104 and base station 106, base station 104 functions as a master eNB (MeNB), a master ng-eNB (Mng-eNB), or a master gNB (MgNB), and base station 106 functions as a secondary gNB (SgNB) or a secondary ng-eNB (Sng-eNB).

[0046] In non-MBS (unicast) operation, UE 102A may use radio bearers (e.g., DRBs or SRBs) that terminate at different times at a MN (e.g., base station 104) or a SN (e.g., base station 106). For example, after a handover or SN change to base station 106, UE 102A may use radio bearers (e.g., DRBs or SRBs) that terminate at base station 106. UE 102A may apply one or more security keys when communicating on the radio bearers in the uplink (from UE 102A to base station) and / or downlink (from base station to UE 102A) directions. In non-MBS operation, UE 102A transmits data to a base station via a radio bearer on an uplink (UL) bandwidth part (BWP) of a cell (i.e., within) and / or receives data from a base station via a radio bearer on a downlink (DL) BWP of a cell. 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. UE 102A may receive paging, system information, public warning messages, or random access responses on the DL BWP. In this non-MBS operation, UE 102A may be in a connected state. Alternatively, if UE 102A supports a small amount of data transmission in an idle or inactive state, UE 102A may be in an idle or inactive state.

[0047] In MBS operation, UE 102A may use MBS radio bearers (MRBs) that terminate at MN (e.g., base station 104) or SN (e.g., base station 106) at different times. For example, after handover or SN change, UE 102A may use an MRB that terminates at base station 106, which may be operating as a MN or SN. In some scenarios, the base station (e.g., MN or SN) may transmit MBS data to UE 102A via the MRB over unicast radio resources (i.e., radio resources dedicated to UE 102A). In other scenarios, the base station (e.g., MN or SN) may transmit MBS data from the base station to UE 102A via the MRB over multicast radio resources (i.e., radio resources shared by UE 102A and one or more other UEs) or a DL BWP of a cell. The DL BWP may be an initial DL BWP, a dedicated DL BWP, or an MBSDL BWP (i.e., a DL BWP specific to MBS or not used for unicast).

[0048] Base station 104 includes processing hardware 130, which may include one or more general purpose processors (e.g., central processing units (CPUs)), and computer readable memory storing machine readable instructions executable on the one or more general purpose processors and / or special purpose processing units. Figure 1AThe processing hardware 130 in an example implementation of includes an MBS controller 132 that is configured to manage or control the transmission of MBS information received from the CN 110 or an edge server. For example, the MBS controller 132 may be configured to support radio resource control (RRC) configurations, procedures, and messaging associated with MBS procedures, and / or other operations associated with those configurations and / or procedures, as discussed below. The processing hardware 130 may also include a non-MBS controller 134 that is configured to manage or control one or more RRC configurations and / or RRC procedures when the base station 104 operates as a MN or SN during non-MBS operation.

[0049] The base station 106 includes processing hardware 140, which may include one or more general purpose processors (e.g., CPUs) and computer readable memory storing machine readable instructions executable on the general purpose processors and / or special purpose processing units. Figure 1A In an example implementation, processing hardware 140 includes an MBS controller 142 and a non-MBS controller 144, which may be similar to controllers 132 and 134 of base station 130, respectively. Figure 1A Not shown, but RAN 105 may include additional base stations with processing hardware similar to processing hardware 130 of base station 104 and / or processing hardware 140 of base station 106.

[0050] UE 102A includes processing hardware 150, which may include one or more general-purpose processors (e.g., CPUs) and computer-readable memory storing machine-readable instructions executable on the general-purpose processors and / or special-purpose processing units. Figure 1A In an example implementation of , the processing hardware 150 includes an MBS controller 152 that is configured to manage or control the reception of MBS information. For example, the UE MBS controller 152 may be configured to support RRC configurations, procedures, and messaging associated with MBS procedures, and / or other operations associated with those configurations and / or procedures, as discussed below. The processing hardware 150 may also include a non-MBS controller 154 that is configured to manage or control one or more RRC configurations and / or RRC procedures when the UE 102A is communicating with the MN and / or SN during non-MBS operation, in accordance with any of the implementations discussed below. Although Figure 1A Not shown, but UE 102B and UE 103 may include processing hardware similar to processing hardware 150 of UE 102A.

[0051] CN 110 may be an evolved packet core (EPC) 111 or a fifth generation core (5GC) 160, both of which are Figure 1A . The base station 104 may be an eNB supporting an S1 interface for communicating with the EPC 111, an ng-eNB supporting an NG interface for communicating with the 5GC 160, or a gNB supporting an NR radio interface and an NG interface for communicating with the 5GC 160. The base station 106 may be an EUTRA-NR DC (EN-DC) gNB (en-gNB) with an S1 interface to the EPC 111, an en-gNB not connected to the EPC 111, a gNB supporting an NR radio interface and an NG interface to the 5GC 160, or an ng-eNB supporting an EUTRA radio interface and an NG interface to the 5GC 160. In order to exchange messages directly with each other in the scenarios discussed below, the base stations 104 and 106 may support an X2 or Xn interface.

[0052] 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 generally configured to pass user plane packets associated with 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 a UE (e.g., UE 102A or 102B) to one or more external packet data networks (e.g., an Internet network and / or an Internet Protocol (IP) Multimedia Subsystem (IMS network). 5GC 160 includes a user plane function (UPF) 162, an access and mobility management function (AMF) 164, and / or a session management function (SMF) 166. UPF 162 is generally configured to deliver user plane packets associated with audio calls, video calls, Internet traffic, etc., AMF 164 is generally configured to manage authentication, registration, paging, and other related functions, and SMF 166 is generally configured to manage PDU sessions.

[0053] UPF 162, AMF 164, and / or SMF 166 may be configured to support MBS. For example, SMF 166 may be configured to manage or control MBS transmissions, configure UPF 162 and / or RAN 105 for MBS flows, and / or manage or configure one or more MBS sessions or PDU sessions for MBS for a UE (e.g., UE 102A or 102B). UPF 162 is configured to deliver MBS data packets for audio, video, Internet traffic, etc. to RAN 105. UPF 162 and / or SMF 166 may be configured for both non-MBS unicast services and MBS, or only for MBS, such as Figure 1A The prefix "(MB-)" shown in FIG.

[0054] Typically, the wireless communication system 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 be connected to any suitable number of base stations supporting NR cells and / or EUTRA cells. Although the following examples specifically mention specific CN types (EPC, 5GC) and radio access technology (RAT) types (5G NR and EUTRA), in general, the technology of the present disclosure may 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 network or 5G NR-6G DC.

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

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

[0057] Figure 1B An example distributed implementation of any one or more of the base stations 104 and 106 is depicted. In this implementation, the base stations 104, 106 include a central unit (CU) 172 and one or more distributed units (DUs) 174. In implementations where the base stations 104, 106 include multiple DUs, the terms DU 174A and 174B may be used to refer to a first DU and a second DU of the multiple DUs, respectively. The 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 that can be executed on the general-purpose processors and / or special-purpose processing units. For example, the CU 172 may include Figure 1ASome or all of the processing hardware 130 or 140.

[0058] Each of the DUs 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 the one or more general-purpose processors, and / or a dedicated processing unit. For example, the processing hardware may include: a media access control (MAC) controller configured to manage or control one or more MAC operations or processes (e.g., random access processes); and a radio link control (RLC) controller configured to manage or control one or more RLC operations or processes when a base station (e.g., base station 104) operates as a MN or SN. The processing hardware may also include a physical (PHY) layer controller configured to manage or control one or more PHY layer operations or processes.

[0059] In some implementations, CU 172 may include one or more logical nodes (CU-CP 172A) that host a control plane portion of a packet data convergence protocol (PDCP protocol) of CU 172 and / or a radio resource control (RRC) protocol of CU 172. CU 172 may also include one or more logical nodes (CU-UP 172B) that host a user plane portion of a PDCP protocol and / or a service data adaptation protocol (SDAP) protocol of CU 172. CU-CP 172A may transmit non-MBS control information and MBS control information, while CU-UP 172B may transmit non-MBS data packets and MBS data packets, as described herein.

[0060] CU-CP 172A may be connected to multiple CU-UPs 172B via an E1 interface. CU-CP 172A selects an appropriate CU-UP 172B for the service requested by UE 102A. In some implementations, a single CU-UP 172B may be connected to multiple CU-CPs 172A via an E1 interface. CU-CP 172A may be connected to one or more DUs 174 via an F1-C interface. CU-UP 172B may be connected to one or more DUs 174 via an F1-U interface under the control of the same CU-CP 172A. In some implementations, one DU 174 may be connected to multiple CU-UPs 172B under the control of the same CU-CP 172A. In such implementations, the connection between CU-UP 172B and DU 174 is established by CU-CP 172A using a bearer context management function.

[0061] Figure 2AAn example protocol stack 200 is shown in a simplified manner, according to which a UE (e.g., UE 102A, 102B, or 103) can communicate with an eNB / ng-eNB or gNB (e.g., one or more of base stations 104, 106). In the example protocol stack 200, the EUTRA PHY sublayer 202A provides transport channels to the EUTRA MAC sublayer 204A, which in turn provides logical channels to the EUTRA RLC sublayer 206A. The EUTRA RLC sublayer 206A in turn provides RLC channels to the EUTRA PDCP sublayer 208 and, in some cases, to the NR PDCP sublayer 210. Similarly, the NR PHY 202B provides transport channels to the NR MAC sublayer 204B, which in turn provides logical channels to the NR RLC sublayer 206B. The NR RLC sublayer 206B in turn provides RLC channels to the NR PDCP sublayer 210. In some implementations, such as Figure 2A As shown, the UE supports both EUTRA and NR stacks to support handover between EUTRA and NR base stations and / or support DC implemented through EUTRA and NR interfaces. Figure 2A As shown, the UE may support NR PDCP 210 layered on EUTRA RLC 206A, and SDAP sublayer 212 layered on NR PDCP sublayer 210. Sublayers are also referred to herein as “layers” for short.

[0062] The EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 receive packets that may be referred to as service data units (SDUs) (e.g., from an IP layer layered directly or indirectly on the PDCP layer 208 or 210) and output packets that may be referred to as protocol data units (PDUs) (e.g., to the RLC layer 206A or 206B). In addition to the difference between SDUs and PDUs, for simplicity, the present disclosure refers to both SDUs and PDUs as "packets". The packets may be MBS packets or non-MBS packets. For example, the MBS packets may include application content for MBS services (e.g., IPv4 / IIPv6 multicast delivery, IPTV, wireless software delivery, group communication, IoT applications, V2X applications, and / or emergency messages related to public safety). As another example, the MBS packets may include application control information for the MBS services.

[0063] For example, on the control plane, the EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 may provide SRBs to exchange RRC messages or non-access stratum (NAS) messages. On the user plane, the EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 may provide DRBs to support data exchange. The data exchanged on the NR PDCP sublayer 210 may be, for example, SDAP PDUs, IP packets, or Ethernet packets.

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

[0065] In some implementations, a base station (e.g., base station 104, 106) broadcasts MBS data packets via one or more MBS radio bearers (MRBs), and then the UE receives the MBS data packets via the MRBs. The base station may include the configuration of the MRBs in the multicast configuration parameters (also referred to as MBS configuration parameters) described below. In some implementations, the base station broadcasts the MBS data packets via the RLC sublayer 206, the MAC sublayer 204, and the PHY sublayer 202, and accordingly, the UE receives the MBS data packets using the PHY sublayer 202, the MAC sublayer 204, and the RLC sublayer 206. In such implementations, the base station and the UE may or may not use the PDCP sublayer 208 and the SDAP sublayer 212 to transmit the MBS data packets. In other implementations, the base station transmits the MBS data packets via the PDCP sublayer 208, the RLC sublayer 206, the MAC sublayer 204, and the PHY sublayer 202, and accordingly, the UE receives the MBS data packets using the PHY sublayer 202, the MAC sublayer 204, the RLC sublayer 206, and the PDCP sublayer 208. In such implementations, the base station and the UE may or may not use the SDAP sublayer 212 to transmit the MBS data packets. In other implementations, the base station transmits the MBS data packets via the SDAP sublayer 212, the PDCP sublayer 208, the RLC sublayer 206, the MAC sublayer 204, and the PHY sublayer 202, and accordingly, the UE receives the MBS data packets using the PHY sublayer 202, the MAC sublayer 204, the RLC sublayer 206, the PDCP sublayer 208, and the SDAP sublayer 212.

[0066] Figure 2B An example protocol stack 250 is illustrated in a simplified manner, according to which UE 102 or UE 103 can communicate with a DU (e.g., DU 174) and a CU (e.g., CU 172). The radio protocol stack 200 is functionally divided, such as Figure 2B 206B, NR MAC204B, and NR PHY 202B) are delegated to the DU. To support the connection with the 5GC, the NR PDCP 210 provides SRBs to the RRC 214, and the NR PDCP 210 provides DRBs to the SDAP 212 and SRBs to the RRC 214.

[0067] refer to Figure 3, the MBS session 302A may include a tunnel 312A with endpoints at the CN 110 and the base station 104 / 106. The MBS session 302A may correspond to a session IID, such as, for example, a temporary mobile group identity (TMGI). For example, the MBS data may include IIP packets, TCP / IIP packets, UDP / IIP packets, real-time transport protocol (RTP) / UDP / IIP packets, or RTP / TCP / IIP packets.

[0068] In some cases, CN 110 and / or base station 104 / 106 configure tunnel 312A only for MBS traffic directed from CN 110 to base station 104 / 106, and tunnel 312A may be referred to as a downlink (DL) tunnel. However, in other cases, CN 110 and base station 104 / 106 use tunnel 312A for downlink as well as uplink (UL) MBS traffic to support, for example, commands or service requests from UEs. In addition, because base station 104 / 106 may direct MBS traffic arriving via tunnel 312A to multiple UEs, tunnel 312A may be referred to as a common tunnel or a common DL tunnel.

[0069] Tunnel 312A may operate at a transport layer or sublayer, such as a User Datagram Protocol (UDP) protocol layered on an Internet Protocol (IP). As a more specific example, tunnel 312A may be associated with a General Packet Radio System (GPRS) Tunnel Protocol (GTP). For example, tunnel 312A may correspond to a certain IP address (e.g., the IP address of base station 104 / 106) and a certain Tunnel Endpoint Identifier (TEID) (e.g., assigned by base station 104 / 106). More generally, tunnel 312A may have any suitable transport layer configuration. CN 110 may specify an IIP address and a TEID address in a header of a tunnel packet including an MBS data packet, and transmit the tunnel packet downstream to base station 104 / 106 via tunnel 312A. The header may include an IIP address and / or a TEID. For example, the header includes an IIP header and a GTP header including an IIP address and a TEID, respectively. Thus, base station 104 / 106 may use the IIP address and / or TEID to identify data packets traveling via tunnel 312A.

[0070] like Figure 3As shown, the base station 104 / 106 maps the traffic in the tunnel 312A to N radio bearers 314A-1, 314A-2...314A-N, which can be configured as MBS radio bearers or MRBs, where N≥1. Each MRB can correspond to a corresponding logical channel. As discussed above, the PDCP sublayer provides support for radio bearers such as SRBs, DRBs, and MRBs, and the EUTRA or NR MAC sublayer provides logical channels to the EUTRA or NR RLC sublayer. For example, each of the MRBs 314A can correspond to a corresponding MBS traffic channel (MTCH). The base station 104 / 106 and the CN 110 can also maintain another MBS session 302B, which can similarly include a tunnel 312B corresponding to MRBs 314B-1, 314B-2...314B-N, where N≥1. Each of the MRBs 314B can correspond to a corresponding logical channel.

[0071] For each of the tunnels 312A, 312B, etc., the MBS service may include one or more quality of service (QoS) flows. For example, the MBS service on the tunnel 312B may include a set of flows 316, which includes QoS flows 316A, 316B, ... 316L. In addition, the logical channels of the MRB may support a single QoS flow or multiple QoS flows. Figure 3 In the example configuration of , base station 104 / 106 maps QoS flows 316A and 316B to the MTCH of MRB 314B-1, and maps QoS flow 316L to the MTCH of MRB 314B-N.

[0072] In various scenarios, CN 110 may assign different types of MBS services to different QoS flows. For example, a flow with a relatively higher QoS value may correspond to an audio packet, while a flow with a relatively lower QoS value may correspond to a video packet. As another example, a flow with a relatively higher QoS value may correspond to an II frame or a complete image used in video compression, while a flow with a relatively lower QoS value may correspond to a P frame or a predicted picture including only a change to an II frame.

[0073] Continue to refer Figure 3, the base station 104 / 106 and the CN 110 may maintain one or more PDU sessions to support unicast services between the CN 110 and a specific UE. The PDU session 304A may include a UE-specific DL tunnel and / or a UE-specific UL tunnel 322A corresponding to one or more DRBs 324A (such as DRBs 324A-1, 324A-2, ..., 324-N). Each of the DRBs 324A may correspond to a corresponding logical channel such as a dedicated traffic channel (DTCH). The base station 104 / 106 and the CN 110 may also maintain one or more other PDU sessions to support unicast services between the CN 110 and a specific UE. For example, the PDU session 304B may include a UE-specific DL tunnel and / or a UE-specific UL tunnel 322B corresponding to one or more DRBs 324B (such as DRBs 324B-1, 324B-2 ... 324B-N). Each of the DRBs 324B may correspond to a corresponding logical channel, such as a DTCH.

[0074] Reference now Figure 4 , when the base station 104 / 106 is implemented in a distributed manner, one or more DUs 174A / 174B may be associated with the CU 172. The CU 172 and the DUs 174A / 174B may establish tunnels for downlink data and / or uplink data associated with an MRB or a DRB. For example, the MRB 314A-1 discussed above may be implemented as an MRB 402A that connects the CU 172 to multiple UEs, such as UEs 102A and 102B. The MRB 402A may include a DL tunnel 412A connecting the CU 172 and the DUs 174A / 174B, and a DL logical channel 422A corresponding to the DL tunnel 412A. Specifically, the DUs 174A / 174B may map downlink traffic received via the DL tunnel 412A to the DL logical channel 422A, which may be, for example, an MTCH or a DTCH. DL tunnel 412A may be a common DL tunnel via which CU 172 transmits MBS data packets to multiple UEs. Alternatively, DL tunnel 412A may be a UE-specific DL tunnel via which CU 172 transmits MBS data packets to a specific UE.

[0075] Optionally, the MRB 402A further includes a UL tunnel 413A connecting the CU 172 and the DU 174A / 174B, and a UL logical channel 423A corresponding to the UL tunnel 413A. For example, the UL logical channel 423A may be a PUCCH. The DU 174A / 174B may map uplink traffic received via the UL logical channel 423A to the UL tunnel 413A.

[0076] Tunnels 412A and 413A may operate at a transport layer or sublayer of the F1-U interface. As a more specific example, CU 172 and DU 174A / 174B may utilize F1-U for user plane traffic, and tunnels 412A and 413A may be associated with a GTP-U protocol layered above UDP / IIP, where IP is layered above appropriate data link and physical (PHY) layers. In addition, in at least some cases, MRB 402 and / or DRB 404 additionally support control plane traffic. More specifically, CU 172 and DU 174A / 174B may exchange F1-AP messages via an F1-C interface that relies on a stream control transmission protocol (SCTP) layered above IP, where IP is layered above appropriate data link and PHY layers, similar to F1-U.

[0077] Similarly, MRB 402B may include DL tunnel 412B and optionally UL tunnel 413B. DL tunnel 412B may correspond to DL logical channel 422B, while UL tunnel 413B may correspond to UL logical channel 423B.

[0078] In some cases, CU 172 transmits MBS data packets or unicast data packets associated with a PDU session to a specific UE (e.g., UE 102A or UE 102B) using DRB 404A. DRB 404A may include a UE-specific DL tunnel 432A connecting CU 172 and DU 174A / 174B, and a DL logical channel 442A corresponding to DL tunnel 432A. Specifically, DU174A / 174B may map downlink traffic received via DL tunnel 432A to DL logical channel 442A, which may be, for example, DTCH. DRB 404A further includes a UE-specific UL tunnel 433A connecting CU 172 and DU 174A / 174B, and a UL logical channel 443A corresponding to UL tunnel 433A. For example, UL logical channel 443A may be PUSCH. The DU 174A / 174B may map uplink traffic received via the UL logical channel 443A to the UL tunnel 433A.

[0079] Similarly, DRB 404B may include a UE-specific DL tunnel 432B corresponding to a DL logical channel 442B, and a UE-specific UL tunnel 433B corresponding to a UL logical channel 443B.

[0080] In some implementations, the DU (e.g., DU 174A / 174B) assigns a specific logical channel IID (value) to each of the logical channels associated with the MRB associated with the same MBS session or different MBS sessions. In other implementations, the DU assigns the same logical channel ID (value) to each of the logical channels associated with the MRB associated with different MBS sessions. In some implementations, the DU assigns a specific logical channel IID (value) to each of the logical channels associated with the DRB. In some implementations, the DU sets the logical channel IIDs associated with the MRB and the DRB, respectively, to different values. In other implementations, the DU sets the logical channel IIDs associated with the MRB and the DRB, respectively, to the same value.

[0081] Next, refer to FIG. 5A to FIG. 5I Several example scenarios are discussed in which base station 104 (including CU 172 and DU 174) configures resources for transmitting MBS data for an MBS session (ie, a broadcast MBS session). FIG. 5A to FIG. 5I Similar events in the are labeled with the same reference numerals, and the differences are discussed below where appropriate.

[0082] First reference Figure 5A , in scenario 500A, DU 174 generates MBS session information using the PDCP configuration received from CU 172. In scenario 500A, base station 104 broadcasts a certain MBS session (i.e., a first MBS session identified by a first MBS session |ID). Initially, CN 110 may send 502 an MBS session resource establishment request message including the first MBS session IID to CU 172 to request CU 172 to configure resources for the first MBS session. In some implementations, CN 110 excludes the PDU session IID from the MBS session resource establishment request message. In response, CU 172 may send 504 an MBS context establishment request message to DU 174 to request establishment of an MBS context and / or a common DL tunnel for the first MBS session. In the MBS context establishment request message, CU 172 includes the first session IID and the first PDCP configuration for the first MBS session. CU 172 generates the first PDCP configuration to transmit MBS data for the first MBS session. Later, CU 172 transmits MBS data for the first MBS session according to the first PDCP configuration, as described for event 522. In some implementations, each of the first PDCP configurations includes at least one of a PDCP sequence number size (e.g., 12 bits) and a header compression configuration. The header compression configuration may configure one or more header compression profiles, or may not configure header compression.

[0083] In some implementations, the CU 172 may include a first discontinuous reception (DRX) cycle configuration for the first MBS session in the MBS context setup request message. The first DRX cycle configuration includes or configures a first DRX cycle length. In some implementations, the CU 172 may determine the first DRX cycle length based on the QoS configuration. In other implementations, the CU 172 may receive 502 the first DRX cycle length in the MBS session resource setup request message. In some implementations, the CU 172 excludes the PDU session IID from the MBS context setup request message.

[0084] In some implementations, CU 172 may also include first MBS neighbor cell information in the MBS context establishment request message. The first MBS neighbor cell information indicates one or more neighbor cells providing the first MBS session. Alternatively, DU 174 may receive the first MBS neighbor cell information from an operation, administration, and maintenance (OAM) node.

[0085] In response to receiving 504 the MBS context setup request message, DU 174 may send 506 an MBS context setup response message to CU 172, the MBS context setup response message including a first DU DL transport layer configuration to configure a first common CU-to-DU DL tunnel for the first MBS session. CN 110 may also include a quality of service (QoS) configuration for the first MBS session in the MBS session resource setup request message. In such a case, CU 172 may include the QoS configuration in the MBS context setup request message. In some implementations, the MBS context setup request message and the MBS context setup response message may be non-UE specific messages.

[0086] In response to the message of event 504, CU 172 sends 508 an MBS session resource setup response message to CN 110. In some implementations, CU 172 may send 508 an MBS session resource setup response message after receiving 506 an MBS context setup response message. In other implementations, CU 172 may send 508 an MBS session resource setup response message before receiving 506 an MBS context setup response message. CU 172 may include the first MBS session ID in the MBS session resource setup response message. The MBS session resource setup response message may include a first CU DL transport layer configuration to configure a first public CN to BSDL tunnel for CN 110 to send MBS data of the first MBS session to CU 172. The first CU DL transport layer configuration includes transport layer information, such as a transport layer address (e.g., an IP address) and / or a TEID to identify the first public CN to BSDL tunnel.

[0087] In some implementations, the QoS configuration includes QoS parameters for the MBS session. In some implementations, the QoS configuration includes configuration parameters for configuring one or more QoS flows for the MBS session (see Figure 3 ). In some implementations, the configuration parameters include one or more QoS flow IDs that identify the QoS flows. Each QoS flow ID in the QoS flow IDs identifies a specific QoS flow in the QoS flows. In some implementations, the configuration parameters include QoS parameters for each QoS flow. The QoS parameters may include a 5G QoS identifier (5QI), a priority level, a packet delay budget, a packet error rate, an average window, and / or a maximum data burst. The CN 110 may specify different values ​​for the QoS parameters for the QoS flows.

[0088] In some implementations, DU 174 may include the first MBS session IID in the MBS context setup response message to indicate that resources for the first MBS session are successfully established. In some implementations, DU 174 may indicate the association between the first MBS session and the first common CU-to-DU DL tunnel in the MBS context setup response message.

[0089] In some implementations, CU 172 may configure one or more MRBs (MRBs) for the first MBS session and generate one or more MRBIIDs (MRBIIDs), each MRBIID being used for a specific MRB in the MRBs. In such cases, CU 172 may include the MRBIID in an MBS context setup request message to request DU 174 to configure resources for the MRBs. In some implementations, CU 172 may associate each of the first PDCP configurations with a specific MRB / MRBIID of the MRBs / MRBIIDs and indicate the association in the MBS context setup request message. In some implementations, DU 174 may include the MRBIID in an MBS context setup response message to indicate that resources for the MRBs are successfully established. In the event that DU 174 does not have sufficient resources for all MRBs, DU 174 may include a portion of the MRBIID in the MBS context setup response message to indicate that resources for the portion of the MRBs are successfully established. In the MBS context setup response message, DU 174 may, in some implementations, include an additional DU DL transport layer configuration that configures an additional common CU to DU DL tunnel for the first MBS session. DU 174 may associate each of the common CU to DU DL tunnels (including the first common CU to DU DL tunnel and the additional common CU to DU DL tunnel) with a specific MRB or portion of the MRB in the MRBs and indicate the association in the MBS context setup response message. The additional DU DL transport layer configuration includes transport layer information, such as a transport layer address (e.g., an IIP address) and / or a TEID to identify the additional common CU to DU DL tunnel.

[0090] In response to or after receiving 504 the MBS context setup request message, the DU 174 may generate 512 a first MBS broadcast configuration message (eg, MBSBroadcastConfiguration message) including the first session IID and the first PDCP configuration.

[0091] Events 502, 504, 506, 508, and 512 are Figure 5A are collectively referred to as MBS resource establishment process 586A.

[0092] Before, during, or after the MBS resource setup procedure 586A, the DU 174 transmits (e.g., broadcasts) 514 system information (e.g., one or more system information blocks (SI Bs)) including MBS control information about one or more cells (e.g., cell 124 and / or other cells operated by the DU 174). In some implementations, the DU 174 periodically transmits 514 system information about the one or more cells. The MBS control information includes configuration parameters for the UE 102 to receive the first MBS broadcast configuration message. In some implementations, the DU 174 may (start) transmitting 514 the system information in response to performing 586A the MBS resource setup procedure. In some implementations, the CU 172 generates the system information and transmits a CU-to-DU message including the system information to the DU 174. For example, the CU-to-DU message may be a non-UE associated message (e.g., an F1AP message), such as a gNB-CU configuration update message, a gNB-DU configuration update confirmation message, a system information delivery command message, or an F1 setup response message. In other implementations, the DU 174 generates the system information. In some implementations, the DU 174 may transmit a DU-to-CU message to the CU 172 including the system information.

[0093] After generating 512 the first MBS broadcast configuration message, the DU 174 transmits (eg, broadcasts) 516 the first MBS broadcast configuration message according to the MBS control information. In some implementations, the DU 174 may transmit 516 the first MBS broadcast configuration message according to the MBS control information via one or more cells.

[0094] In some implementations, the MBS control information includes an MBS control channel (MCCH) configuration, a common frequency resource (CFR) configuration (e.g., cfr-Config-MCCH-MTCH), a PDSCH configuration for MCCH (e.g., pdsch-Config-MCCH), a PDSCH configuration for MTCH (e.g., pdsch-Config-MTCH), a PDCCH configuration for MCCH (e.g., pdcch-Config-MCCH), and / or a PDCCH configuration for MTCH (e.g., pdcch-Config-MTCH). The CFR configuration configures the common frequency resources to enable the UE 102 to receive the MBS (e.g., the first MBS session). If the CFR configuration does not exist, the UE 102 may receive the MBS via the initial DL BWP. The UE 102 may obtain the configuration parameters of the initial DL BWP in the SI B1 received by the UE 102 from the DU 172. The PDSCH configuration for MCCH configures cell-specific configuration parameters to enable the UE 102 to receive a PDSCH transmission including MCCH data (e.g., an MBS broadcast configuration message including a first MBS broadcast configuration message). If the PDSCH configuration for MCCH does not exist, the UE 102 may use the PDSCH configuration in SI B1 to receive a PDSCH transmission including MCCH data (e.g., an MBS broadcast configuration message including a first MBS broadcast configuration message). The PDSCH configuration for MTCH configures cell-specific configuration parameters to enable the UE 102 to receive a PDSCH transmission. If the PDSCH configuration for MTCH does not exist, the UE 102 may use the PDSCH configuration in SI B1 to receive a PDSCH transmission. Each of the PDSCH transmissions includes MTCH data (e.g., MBS data for an MBS session, such as MBS data for a first MBS session). The PDCCH configuration for MCCH configures cell-specific configuration parameters to enable the UE 102 to receive a PDCCH transmission. If the PDCCH configuration for MCCH does not exist, the UE 102 may use the PDCCH configuration in SI B1 to receive a PDCCH transmission. Each of the PDCCH transmissions includes a DCI and a CRC (of the DCI) scrambled with the MCCH-RNTI or G-RNTI that schedules a PDSCH transmission including MCCH data (e.g., an MBS broadcast configuration message including the first MBS broadcast configuration message). The PDCCH configuration for the MTCH configures cell-specific configuration parameters to enable the UE 102 to receive the PDCCH transmission. If the PDCCH configuration for the MTCH does not exist, the UE 102 can use the PDCCH configuration in SI B1 to receive the PDCCH transmission.Each of the PDCCH transmissions includes a DCI and a CRC (of the DCI) scrambled with a G-RNTI scheduling a PDSCH transmission including MTCH data (eg, MBS data for an MBS session, such as the first MBS session).

[0095] In some implementations, the first MBS broadcast configuration message may include a PDSCH configuration for MTCH (eg, pdsch-Config-MTCH) and / or a PDCCH configuration for MTCH (eg, pdcch-Config-MTCH), instead of system information or MBS control information.

[0096] In some implementations, the MCCH configuration includes configuration parameters such as a window start slot, a window duration, a modification period and / or a repetition period and an offset. The window duration indicates a duration starting from the slot indicated by the window start slot (i.e., an MCCH transmission window in units of, for example, (continuous) slots), during which the transmission of MCCH information (i.e., the transmission of the MBS configuration via the MCCH) can be scheduled. The modification period defines boundaries that occur periodically, i.e., radio frames where the SFN modifies the modification period = 0. The content of different transmissions of the MCCH information differs only if there is at least one such boundary between them. The repetition period and offset parameters define the length and offset of the MCCH repetition period. The transmission of the MCCH information is scheduled in a radio frame for which the system frame number (SFN) modifies the repetition period length offset.

[0097] In some implementations, the DU 174 may generate 512 first MBS session information (e.g., MBS-SessionInfoIE) including a first MBS session ID, a first G-RNTI, a first RLC configuration, and / or a first PDCP configuration, and include the first MBS session information in an MBS broadcast configuration message. In some implementations, the DU 174 may generate 512 a first MRB configuration including a first PDCP configuration and / or a first RLC configuration. Each of the first MRB configurations may include a specific PDCP configuration of the first PDCP configuration. Each of the first MRB configurations may include a specific RLC configuration of the first RLC configuration. In some implementations, the DU 174 may establish and use one / multiple RLC entities to transmit 522 MBS data of the first MBS session to the UE 102 according to the first RLC configuration. In the case where the DU 174 receives the first DRX cycle configuration from the CU 172, the DU 174 may generate the first DRX configuration (e.g., DRX-Config MIIE) according to the first DRX cycle configuration (e.g., the first DRX cycle length). In such a case, the DU 174 may include the first DRX configuration in the first MBS session information.

[0098] DU 174 schedules the transmission of MBS data for the first MBS session using the first G-RNTI. Each of the first RLC configurations configures a logical channel IID, an RLC sequence number size (e.g., 6 bits or 12 bits), and / or a timer (value) for reorganizing a specific MRB in the MRBs. The first DRX configuration configures DRX parameters for transmitting MBS data for the first MBS session over the on-duration of the periodic DRX cycle to save power of the UE. According to the DRX parameters, the UE enables discontinuous reception of MBS data for the first MBS session. For example, the DRX parameters may include the following items:

[0099] • Inactivity timer parameters (e.g., drx-InactivityTimerPTM field): duration after a PDCCH opportunity where the PDCCH indicates a new DL multicast transmission for the MAC entity;

[0100] DRX cycle and start offset parameters (e.g., drx-(Long)CycleStartOffsetPTM field): define the length of the DRX cycle and define the subframe in which the DRX cycle starts;

[0101] • On-Duration parameter (eg, drx-onDurationTimerPTM): The duration at which the DRX cycle starts.

[0102] In some implementations, DU 174 may generate the first RLC configuration, for example, based on the QoS configuration and / or MRBIID. Alternatively, DU 174 may generate the first RLC configuration using pre-configured RLC parameters. In some implementations, DU 174 may include the first logical channel IID in the first RLC configuration. In the case where DU 174 receives the first DRX cycle configuration, DU 174 sets the length of the DRX cycle to the first DRX cycle length. In the case where DU 174 does not receive the DRX cycle configuration for the first MBS session, DU 174 may determine the length of the DRX cycle, for example, based on the QoS configuration received from CU 172. Alternatively, DU 174 may determine the length of the DRX cycle based on pre-configured DRX parameters. Alternatively, DU 174 does not include the DRX configuration for the first MBS session in the first MBS session information or MBS broadcast configuration message, excludes or avoids including the DRX configuration for the first MBS session therein. In some implementations, the DU 174 may allocate a first G-RNTI (value) and associate the first G-RNTI with the first MBS session ID.

[0103] In the case where DU 174 receives the first MBS neighbor cell information, DU 174 may include the first MBS neighbor cell information in the first MBS session information. In the case where CU 172 does not transmit the first MBS neighbor cell information to DU 174, DU 174 may generate the first MBS neighbor cell information and include the first MBS neighbor cell information in the first MBS session information. In some implementations, DU 174 may generate a first field / IE (e.g., mt ch-NeighborCell-r17) to indicate one or more cells included in the first MBS neighbor cell information, and include the field / IE in the first MBS session information.

[0104] After the MBS resource establishment process 586A, the CN 110 sends 518 MBS data of the first MBS session to the CU 172 via the first public CN to BSDL tunnel. Subsequently, the CU 172 transmits 520 the MBS data to the DU 174 via the first public CU to DU DL tunnel and / or the additional public CU to DU DL tunnel according to the first PDCP configuration. Then, the DU 174 transmits (i.e., broadcasts) 522 the MBS data according to the MBS broadcast configuration message (e.g., via the first logical channel identified by the first logical channel ID and using the first RLC configuration and / or the first G-RNTI). The UE 102 receives 522 the MBS data according to the first MBS broadcast configuration or the first MBS session information. For example, the CU 172 receives 518 the MBS data packet, generates a PDCP PDU including the MBS data packet according to the PDCP configuration, and transmits 520 the PDCP PDU to the DU 174 via the first public CU to DU DL tunnel. In some implementations, the CU 172 may use the PDCP state variable to generate a PDCP sequence number included in the PDCP PDU. In some implementations, the DU 174 generates a MAC PDU including the first logical channel ID and the PDCP PDU, and transmits 522 the MAC PDU to the UE 102 using the first G-RNTI. The UE 102 receives 522 the MAC PDU using the first G-RNTI, retrieves the PDCP PDU and the first logical channel ID from the MAC PDU, identifies the PDCP PDU associated with the MRB based on the first logical channel ID, and retrieves the MBS data packet from the PDCP PDU according to the first PDCP configuration. In other implementations, the DU 174 generates a plurality of RLC PDU segments including the PDCP PDU, wherein the plurality of RLC PDU segments include an RLC sequence number (i.e., the same RLC sequence number), and each of the plurality of RLC PDU segments includes a specific portion of the PDCP PDU. In some implementations, the DU 174 may use the RLC state variable to generate the RLC sequence number. For each of the plurality of RLC PDU segments, the DU 174 generates a MAC PDU including a first logical channel ID and the RLC PDU segment, and transmits 522 the MAC PDU using the first G-RNTI to the UE 102. The UE 102 receives 522 the MAC PDU using the first G-RNTI, retrieves the first logical channel ID and the RLC PDU segment from the MAC PDU, assembles the RLC PDU segments to obtain a PDCP PDU, identifies a PDCP PDU associated with the MRB based on the first logical channel ID, and retrieves the MBS data packet from the PDCP PDU according to the first PDCP configuration.

[0105] In some implementations, CU 172 includes CU-CP 172A and CU-UP 172B, such as for Figure 1B In such a case, the events of the MBS resource establishment process 586A occur between CU-CP 172A, CN 110, and DU 174. In such a case, events 518 and 520 occur between CN 110, CU-UP 172B, and DU 174. After receiving 506 the MBS context establishment response message, CU-CP 172A may send an MBS bearer context establishment request message (MBS bearer context establishment request message) including the first MBS session ID and / or MRB ID to CU-UP 172B. Figure 5A 172B may transmit 518 the MBS data of the first MBS session to CU-UP 172B via the first public CN to BSDL tunnel.

[0106] In some implementations, the CU-CP 172A may include the first PDCP configuration in the MBS bearer context setup request message, and the CU-UP 172B transmits 520 the MBS data of the first MBS session to the DU 174 according to the first PDCP configuration. In some implementations, the CU-UP 172B establishes one / multiple PDCP entities according to the first PDCP configuration, and transmits 520 the MBS data of the first MBS session to the DU 174 using the one / multiple PDCP entities. In some implementations, the CU-CP 172A includes the MRB|ID in the MBS bearer context setup request message, and the CU-CP 172A may associate each of the first PDCP configurations with a specific MRB / MRB|ID of the MRB / MRB IDs, and indicate the association in the MBS bearer context setup request message. In some implementations, CU-CP 172A includes the first DU DL transport layer configuration and / or the additional DU DL transport layer configuration in the MBS bearer context establishment request message, so that CU-UP 172B can transmit 520 MBS data of the first MBS session to DU 174 via the first common CU to DU DL tunnel and / or the additional common CU to DU DL tunnel.

[0107] In some implementations, the MBS bearer context may include a first PDCP configuration, a first DU DL transport layer configuration, an additional DU DL transport layer configuration, and / or a first CU DL transport layer configuration.

[0108] refer to FIG. 7A to FIG. 7B and FIG. 9A to FIG. 9B The actions that can be performed by CU-CP 172A and CU-UP 172B are further described. FIG. 5B to FIG. 5E Not shown, but the events of MBS resource processes 586B-586E (described below) may occur between CU-CP 172A, CN 110, and DU 174 in a similar manner as described for MBS resource process 586A.

[0109] Figure 5Bis a message passing diagram of example scenario 500B that is similar to scenario 500A, except that DU 174 receives the PDCP configuration in a CU-to-DU message from CU 172 after receiving the MBS context setup request message, as described below. More specifically, CU 172 transmits 503 an MBS context setup request message including a first MBS session ID to DU 174, wherein CU 172 excludes the first PDCP configuration and / or the first DRX cycle configuration from the MBS context setup request message. CU 172 transmits 510 a CU-to-DU message including the first MBS session ID, the first PDCP configuration, and / or the first DRX cycle configuration to DU 174, instead of including the first PDCP configuration and / or the first DRX cycle configuration in the MBS context setup request message at event 503. In some implementations, the CU-to-DU message may be an F1 Application Protocol (F1AP) message. Events 502, 503, 506, 508, 510, and 512 are described in detail below. Figure 5B are collectively referred to as the MBS resource establishment process 586B.

[0110] Figure 5C 5 is a message passing diagram for an example scenario 500C similar to scenarios 500A and 500B, but in which CU 172 generates MBS session information instead of DU 174. In scenario 500C, DU 174 transmits 505 an MBS context setup response message including a first RLC configuration and a first G-RNTI to CU 172. After receiving the first RLC configuration and the first G-RNTI, CU 172 generates 511 first MBS session information including a first MBS session ID, a first G-RNTI, and a first MRB configuration (i.e., including a first PDCP configuration and a first RLC configuration). CU 172 then transmits 513 a CU-to-DU message including the first MBS session information to DU 174. After receiving the first MBS session information, DU 174 may generate a first MBS broadcast configuration message including the first MBS session information and transmit 516 the first MBS broadcast configuration message, as described above. Alternatively, the CU 172 may generate a first MBS broadcast configuration message including the first MBS session information and include the first MBS broadcast configuration message in the CU-to-DU message of event 513. Accordingly, the DU 174 may transmit 516 the first MBS broadcast configuration message as described above.

[0111] In the case where DU 174 generates the first DRX configuration as described above, DU 174 may include the first DRX configuration in the CU-to-DU message of event 505 in some implementations. In such cases, CU 172 includes the first DRX configuration in the first MBS session information. In other implementations, CU 172 may generate the first DRX configuration and include the first DRX configuration in the first MBS session information. In other implementations, CU 172 excludes the DRX configuration from (or avoids including the DRX configuration in) the first MBS session information or the first MBS broadcast configuration message.

[0112] In some implementations, CU 172 may include the first MBS neighbor cell information in the first MBS session information. In some implementations, DU 174 may include the first MBS neighbor cell information in the MBS context setup response message. In other implementations, CU 172 generates the first MBS neighbor cell information. In some implementations, CU 172 may generate a first field / IE (e.g., mt ch-NeighborCell-r17) to indicate one or more cells included in the first MBS neighbor cell information, and include the field / IE in the first MBS session information.

[0113] Events 502, 503, 505, 508, 511, and 513 are Figure 5C It is collectively referred to as the MBS resource establishment process 586C.

[0114] Figure 5D 500D is a message passing diagram of an example scenario 500D similar to scenario 500C, but in which DU 174 transmits 509 a DU to CU message including a first RLC configuration and a first G-RNTI to CU 172, instead of including the first RLC configuration, the first G-RNTI and / or the first DRX cycle configuration in an MBS context setup response message at event 505. In some implementations, the CU to DU message may be an F1AP message. Events 502, 503, 506, 508, 509, 511, and 513 are described in detail in detail in detail. Figure 5D It is collectively referred to as MBS resource establishment process 586D.

[0115] Figure 5Eis a message passing diagram for example scenario 500E similar to scenarios 500A and 500B, except that DU 174 does not receive a PDCP configuration from CU 172. Since CU 172 does not provide a first PDCP configuration to DU 174, DU 174 may be pre-configured with a first PDCP configuration or receive the first PDCP configuration from an OAM node in some implementations. In other implementations, DU 174 may generate a first PDCP configuration based on a configuration in a CU-to-DU message received from CU 172. In one implementation, the CU-to-DU message may be an MBS context establishment request message. In some implementations, the configuration may be a QoS configuration. DU 174 may determine or generate a PDCP sequence number size and / or header compression configuration based on the QoS configuration. For example, if the QoS configuration requires or indicates a high data rate, DU 174 may determine or generate a PDCP sequence number size as a larger size (e.g., 18 bits). Otherwise, DU 174 may determine a PDCP sequence number size as a smaller size (e.g., 12 bits). In another example, if the QoS configuration requires or indicates QoS for a streaming service (e.g., voice or video service), DU 174 may determine or generate one or more header compression profiles configured for the MRB for the first MBS session. Otherwise, DU 174 may determine not to configure header compression for the MRB for the first MBS session.

[0116] In other implementations, the configuration may include a CU-to-DU header compression configuration, where each CU-to-DU header compression configuration is an IE (e.g., F1AP IE) of a CU-to-DU message for a specific MRB in the MRBs for the first MBS session. DU 174 may generate a header compression configuration in the first PDCP configuration based on the CU-to-DU header compression configuration. In the event that the CU-to-DU message does not include a CU-to-DU header compression configuration for a specific MRB in the MRBs, DU 174 may generate a header compression configuration that does not configure header compression and include the header compression configuration in the first PDCP configuration.

[0117] In other implementations, the configuration may include a CU-to-DU PDCP sequence number size configuration, where each CU-to-DU PDCP sequence number size configuration is an IE (e.g., F1APIE) of the CU-to-DU message for a specific one of the MRBs for the first MBS session. The DU 174 may generate the PDCP sequence number size in the first PDCP configuration based on the CU-to-DU PDCP sequence number size configuration. In the event that the CU-to-DU message does not include a PDCP sequence number size configuration for a specific one of the MRBs, the DU 174 may include a default PDCP sequence number size in the first PDCP configuration.

[0118] Then, DU 174 generates 515 a first MBS broadcast configuration message. Events 502, 503, 506, 508, and 515 are Figure 5E These are collectively referred to as the MBS resource establishment process 586E.

[0119] Fig. 5F 5 is a message passing diagram for example scenario 500F similar to scenarios 500A-E, except that base station 104 later releases resources for the first MBS session. Scenario 500F may start from any of the MBS resource establishment procedures 586A-E. After transmitting 518 the MBS data, CN 110 may determine to request RAN 105 to release resources for the first MBS session. In response to the determination, CN 110 transmits 524 an MBS session resource release request message including the first MBS session ID to CU 172. In response to or after receiving 524 the MBS session resource release request message, CU 172 transmits 526 an MBS context release command message to DU 174 to request DU 174 to release resources for the first MBS session. In some implementations, CU 172 may include the first MBS session ID in the MBS context release command message. CU 172 may or may not include the MRBIID in the MBS context release command message. In response, DU 174 releases resources (e.g., the first G-RNTI, the first RLC configuration, the first DRX configuration, and / or the first and / or additional DU DL transport layer configurations), and transmits 528 an MBS context release complete message to CU 172. In response to or after receiving 528 the MBS context release complete message, CU 172 may transmit 530 an MBS session resource release response message to CN 110 to confirm that the resources for the first MBS session have been released.

[0120] In some implementations, CU 172 may determine to request DU 174 to release resources for the first MBS session without receiving an MBS session resource release request message from CN 110. For example, CU 172 may make this determination after detecting that the MBS data of the first MBS session is inactive for a certain period of time. In response to this determination, CU 172 may transmit 526 an MBS context release command message to DU 174. In some implementations, CU 172 may receive a value of the time period in a CN to BS message from CN 110. For example, the CN to BS message may be an MBS session resource establishment request message or an NG Application Protocol (NGAP) message of event 502. In other implementations, CU 172 may receive a value of the time period from an OAM node. In other implementations, CU 172 may be pre-configured with a value of the time period.

[0121] DU 174 may stop 532 transmitting (e.g., broadcasting) the first MBS broadcast configuration message in response to or after receiving 526 the MBS context release command message. Alternatively, DU 174 may transmit (e.g., broadcast) a second MBS broadcast configuration message that does not include the first MBS session information according to the MBS control information in response to or after receiving 526 the MBS context release command message. In some implementations, DU 174 generates the second MBS broadcast configuration message as described for the first MBS broadcast configuration message. In other implementations, CU 172 generates the second MBS broadcast configuration message and transmits a CU-to-DU message including the second MBS broadcast configuration message to DU 174, as described for the first MBS broadcast configuration message in scenario 500C. The CU-to-DU message may be an MBS context release command message or an F1AP message.

[0122] In some implementations, DU 174 may release one / multiple RLC entities used by DU 174 to transmit MBS data for the first MBS session in response to or after receiving 526 the MBS Context Release Command message. In some implementations, DU 174 may stop transmitting system information of event 514 .

[0123] Events 524, 526, 528, and 530 are Fig. 5F It is collectively referred to as the MBS resource release process 588.

[0124] In some implementations, CU 172 includes CU-CP 172A and CU-UP 172B. In such cases, events 524, 526, 528, and 530 occur between CU-CP 172A, CN 110, and DU 174 of CU 172. After receiving the message of event 524, CU-CP 172A may send an MBS bearer context release command message (MBS BEARER CONTEXT RELEASE COMMAND) including the first MBS session ID and / or MRBID to CU-UP 172B. Fig. 5F 172B releases the MBS bearer context for the first MBS session. In some implementations, CU-CP 172A excludes the PDU session ID from the MBS bearer context release command message. In response to the MBS bearer context release command message, CU-UP 172B may release the MBS bearer context and send an MBS bearer context release command message to CU-CP 172A. In some implementations, CU-UP 172B may release one or more PDCP entities used by CU-UP 172B to transmit MBS data for the first MBS session in response to or after receiving the MBS bearer context release command message.

[0125] Figure 5G 5 is a message passing diagram of example scenario 500G similar to scenarios 500A-E, except that base station 104 later suspends and resumes resources for the first MBS session. Scenario 500G may start from any of the MBS resource establishment processes 586A-E. After transmitting 518 the MBS data, CN 110 may determine to suspend the first MBS session. In response to the determination, CN 110 transmits 525 an MBS session resource modification request message to CU 172, the MBS session resource modification request message including the first MBS session ID and an indication to suspend the first MBS session. The indication may be a suspension indication or an |IE that indicates or causes CU 172 to suspend resources and / or operations for the first MBS session. In response to or after receiving 525 the MBS session resource modification request message or indication, CU 172 transmits 527 an MBS context modification request message to DU 174, the MBS context modification request message including an indication requesting DU 174 to suspend resources for the first MBS session or MRB. The indication may be a suspension indication or an IE that indicates or causes CU 172 to suspend resources and / or operations for the first MBS session. In some implementations, CU 172 may include the first MBS session|ID and / or MRB|ID in the MBS context modification request message. In response, DU 174 suspends resources and / or operations for the first MBS session or MRB, and transmits 529 an MBS context modification response message to CU 172. In response to or after receiving the 529 MBS context modification response message, CU 172 may transmit 531 an MBS session resource modification response message to CN 110 to confirm that resources for the first MBS session have been suspended.

[0126] In some implementations, CU 172 may determine to request DU 174 to suspend the first MBS session without receiving an MBS session resource modification request message from CN 110. For example, CU 172 may make this determination after detecting that the MBS data of the first MBS session is inactive for a certain period of time. In response to this determination, CU 172 may transmit 527 an MBS context modification request message to DU 174. In some implementations, CU 172 may receive a value of a time period in a CN to BS message from CN 110. For example, the CN to BS message may be an MBS session resource establishment request message or an NG Application Protocol (NGAP) message of event 502. In other implementations, CU 172 may receive a value of a time period from an OAM node. In other implementations, CU 172 may be pre-configured with a value of a time period.

[0127] DU 174 may stop 532 transmitting (e.g., broadcasting) the first MBS broadcast configuration message in response to or after receiving 527 the MBS context modification request message. Alternatively, DU 174 may transmit (e.g., broadcast) a second MBS broadcast configuration message that does not include the first MBS session information according to the MBS control information in response to or after receiving 527 the MBS context modification request message. In some implementations, DU 174 generates a second MBS broadcast configuration message as described for the first MBS broadcast configuration message. In other implementations, CU 172 generates a second MBS broadcast configuration message and transmits a CU-to-DU message including the second MBS broadcast configuration message to DU 174. The CU-to-DU message may be an MBS context modification request message or an F1AP message.

[0128] In some implementations, DU 174 may, in response to or after receiving 527 the MBS context modification request message, reserve one / multiple RLC entities used by DU 174 to transmit MBS data for the first MBS session. In such a case, in one implementation, DU 174 may reserve the RLC state variables. In another implementation, DU 174 may, in response to or after receiving 527 the MBS context modification request message, reset the RLC state variables.

[0129] Events 525, 527, 529, and 531 are Figure 5G It is collectively referred to as the MBS resource suspension process 589.

[0130] In some implementations, CU 172 includes CU-CP 172A and CU-UP 172B. In such cases, events 525, 527, 529, and 531 occur between CU-CP 172A, CN 110, and DU 174 of CU 172. After receiving the message of event 525, CU-CP 172A may send an MBS bearer context modification request message (MBS bearer context modification request message) including the first MBS session ID and / or MRB ID to CU-UP 172B. Figure 5G) to request CU-UP 172B to suspend resources and / or operations for the first MBS session. In some implementations, CU-CP 172A excludes the PDU session ID from the MBS bearer context modification request message. In response to the MBS bearer context modification request message, CU-UP 172B may suspend resources (e.g., MBS bearer context) and / or operations for the first MBS session and send an MBS bearer context modification response message to CU-CP 172A. In some implementations, CU-UP may retain one / more PDCP entities used by CU-UP 172B to transmit MBS data for the first MBS session in response to or after receiving the MBS bearer context modification request message. In such a case, in one implementation, CU-UP 172B may retain the PDCP state variables. In another implementation, DU 174 may reset the PDCP state variables.

[0131] Later, CN 110 may determine to resume the first MBS session. In response to the determination, CN 110 may transmit 534 another second MBS session resource modification request message to CN 110, the second MBS session resource modification request message including the first MBS session ID and an indication requesting CU 172 to resume the first MBS session. In some implementations, the indication may be a resume indication or an IE that indicates or causes CU 172 to resume the first MBS session. In response to or after receiving 534 the MBS session resource modification request message, CU 172 transmits 536 an MBS context modification request message to DU 174, the MBS context modification request message including an indication to resume the first MBS session. In some implementations, CU 172 may include the first MBS session ID in the MBS context modification request message. CU 172 may or may not include the MRBID in the MBS context modification request message. In response to the MBS context modification request message, DU 174 resumes the suspended resources and / or operations and transmits 538 an MBS context modification response message to CU 172. In response to or after receiving 538 the MBS context modification response message, CU 172 may transmit 540 an MBS session resource modification response message to CN 110 to confirm that the resources of the first MBS session have been resumed.

[0132] In some implementations, CU 172 may determine to request DU 174 to resume the first MBS session without receiving an MBS session resource modification request message from CN 110. For example, CU 172 detects MBS data activity in response to receiving 548 MBS data for the first MBS session, and makes the determination after detecting the MBS data activity. In response to the determination, CU 172 may transmit 536 an MBS context modification request message to DU 174. In response to the MBS context modification request message, DU 174 resumes the suspended resources and / or operations and transmits 538 an MBS context modification response message to CU 172.

[0133] DU 174 may resume 542 transmission of the first MBS broadcast configuration message in response to receiving 536 the MBS context modification request message or thereafter. Alternatively, DU 174 may determine to transmit (e.g., broadcast) 542 a third MBS broadcast configuration message in response to receiving 536 the MBS context modification request message or thereafter. The third MBS broadcast configuration message may include the first MBS session information or new MBS session information for the first MBS session. In some implementations, DU 174 generates the third MBS broadcast configuration message as described for the first MBS broadcast configuration message. In other implementations, CU 172 generates the third MBS broadcast configuration message and transmits a CU-to-DU message including the third MBS broadcast configuration message to DU 174 as described for the first MBS broadcast configuration message. The CU-to-DU message may be an MBS context modification request message or an F1AP message.

[0134] In some implementations, DU 174 may reset the RLC state variable in response to or after receiving 536 the MBS context modification request message. Alternatively, DU 174 avoids resetting the RLC state variable in response to or after receiving 536 the MBS context modification request message. In the case where DU 174 stops transmitting system information in response to or after receiving 527 the MBS context modification request message, DU 174 resumes transmitting system information in response to or after receiving 536 the MBS context modification request message. Alternatively, DU 174 determines to transmit new system information including new MBS control information in response to or after receiving 536 the MBS context modification request message. In response to the resumption or determination, DU 174 transmits 544 the (new) system information to UE 102 via broadcast. In response to the resumption or determination of event 542, DU 174 transmits (e.g., broadcasts) 546 the first or third MBS broadcast configuration message via the (new) MBS control information.

[0135] Events 534, 536, 538, and 540 are Figure 5G 542, 544, or 546, CN 110 may transmit 548 MBS data for the first MBS session to CU 172, similar to event 518. CU 172 may then transmit 550 MBS data for the first MBS session to DU 174, similar to event 520. DU 174 may then transmit 552 MBS data for the first MBS session to UE 102, similar to event 522. In some implementations, DU 174 may transmit 552 MBS data for the first MBS session using (resetting) RLC state variables.

[0136] In some implementations, CU 172 includes CU-CP 172A and CU-UP 172B. In such cases, events 534, 536, 538, and 540 occur between CU-CP 172A, CN 110, and DU 174 of CU 172. After receiving the message of event 534, CU-CP 172A may send an MBS bearer context modification request message ( 540 ) including the first MBS session ID and / or MRBIID to CU-UP 172B. Figure 5G 172B may transmit 550 MBS data for the first MBS session to DU 174 using the retained one / multiple PDCP entities in response to or after receiving the MBS bearer context modification request message. In some implementations, CU-CP 172A excludes the PDU session ID from the MBS bearer context modification request message. In response to the MBS bearer context modification request message, CU-UP 172B may resume the suspended resources (e.g., MBS bearer context) and / or operations for the first MBS session and send an MBS bearer context modification response message. After resuming the suspended resources and / or operations, CU-UP 172B may transmit (e.g., broadcast) 550 MBS data for the first MBS session to DU 174 using the retained one / multiple PDCP entities in response to or after receiving the MBS bearer context modification request message. In one implementation, CU-UP 172B may transmit 550 MBS data using the retained PDCP state variables. In another implementation, the CP-UP 172B may reset the PDCP state variables in response to the MBS bearer context modification request message and then transmit 552 the MBS data of the first MBS session to the UE 102 using the PDCP state variables.

[0137] Figure 5H is a messaging diagram for an example scenario 500H similar to the scenarios 500A-E, where the base station 104 also configures resources for transmitting MBS data for a second MBS session via broadcast.

[0138] Scenario 500H may start with any of the MBS resource establishment procedures 586A-E to establish resources for a first MBS session. After transmitting 518 MBS data for the first MBS session, CN 110 may determine to establish resources for a second MBS session. In response to the determination, CN 110, CU 172, and DU 174 may perform 587 an MBS resource establishment procedure for the second MBS session, similar to any of the procedures 586A-E. In the MBS resource establishment procedure 587, CU 172 or DU 174 generates second MBS session information for the second MBS session, including a second MBS session ID, a second G-RNTI, and a second MRB configuration. The second MBS session ID identifies the second MBS session, and the second MRB configuration configures one or more MRBs for the second MBS session. CU 172 or DU 174 may also include a second DRX configuration and / or second neighboring cell information in the second MBS session information. In response to or after performing the MBS resource establishment procedure 587, DU 174 may transmit 554 system information and 556 a second MBS broadcast configuration message via broadcast, similar to events 514 and 516, respectively. More specifically, CU 172 or DU 174 may include the first MBS session information and the second MBS session information in the second MBS broadcast configuration message. Thus, UE 102 (i.e., a UE interested in receiving the first MBS session) and UE 103 (a UE interested in receiving the second MBS session) may each receive a second MBS broadcast configuration message including the broadcast of the first MBS session information and the second MBS session information.

[0139] In some implementations, DU 174 sets the second G-RNTI and the first G-RNTI to different values. In other implementations, DU 174 sets the second G-RNTI and the first G-RNTI to the same value. In some implementations, CU 172 may indicate whether the second MBS session is multiplexed with the first MBS session in the MBS context establishment request or CU to DU message in process 587. For example, CU 172 may include a first indication indicating that the second MBS session is multiplexed with the first MBS session in the MBS context establishment request or CU to DU message in process 587. In response to the first indication, DU 174 may set the second G-RNTI and the first G-RNTI to the same value. In the event that DU 174 does not receive the first indication in process 587, DU 174 sets the second G-RNTI and the first G-RNTI to different values. In another example, CU 172 may include a second indication indicating that the second MBS session is not multiplexed with the first MBS session in the MBS context establishment request or CU to DU message in process 587. In response to the second indication, DU 174 may set the second G-RNTI and the first G-RNTI to different values. In the case that DU 174 does not receive the second indication in process 587, DU 174 sets the second G-RNTI and the first G-RNTI to the same value.

[0140] Similar to establishing the first public CN to BSDL tunnel, CU 172 may establish a second public CN to BSDL tunnel with CN 110 in the MBS resource establishment process 587. The MBS session resource establishment response message of process 587 may include a second CU DL transport layer configuration to configure the second public CN to BSDL tunnel for CN 110 to send MBS data of the second MBS session to CU 172. The second CU DL transport layer configuration includes transport layer information, such as a transport layer address (e.g., an IP address) and / or a TEID to identify the second public CN to BSDL tunnel. Similar to establishing the first public CU to DU DL tunnel, DU 174 may establish at least one second public CU to DU DL tunnel with CU 172 in the MBS resource establishment process 587. The MBS context establishment response message of process 587 may include at least one second DU DL transport layer configuration to configure at least one second public CU to DU DL tunnel for the second MBS session.

[0141] After the MBS resource establishment process 587, CN 110 sends 558 MBS data of the second MBS session to CU 172 via the second public CN to BSDL tunnel. Subsequently, CU 172 transmits 560 MBS data to DU 174 via the second public CU to DU DL tunnel and / or the additional public CU to DU DL tunnel according to the second PDCP configuration. Then, DU 174 transmits (i.e., broadcasts) 562 MBS data according to the MBS broadcast configuration message (e.g., via the second logical channel identified by the second logical channel ID, and using the second RLC configuration and / or the second G-RNTI). UE 103 receives 562 MBS data according to the second MBS broadcast configuration or the second MBS session information. For example, CU 172 receives 558 MBS data packets, generates PDCP PDUs including the MBS data packets according to the PDCP configuration, and transmits 560 PDCP PDUs to DU 174 via the second public CU to DU DL tunnel. In some implementations, the CU 172 may use the PDCP state variable to generate a PDCP sequence number included in the PDCP PDU. In some implementations, the DU 174 generates a MAC PDU including the second logical channel ID and the PDCP PDU, and transmits 562 the MAC PDU to the UE 103 using the second G-RNTI. In some implementations, the DU 174 may use the RLC state variable to generate an RLC sequence number. The UE 103 receives 562 the MAC PDU using the second G-RNTI, retrieves the second logical channel ID and the PDCP PDU from the MAC PDU, identifies the PDCP PDU associated with the MRB based on the second logical channel IID, and retrieves the MBS data packet from the PDCP PDU according to the first PDCP configuration. In other implementations, the DU 174 generates a plurality of RLC PDU segments including the PDCP PDU, wherein the plurality of RLC PDU segments include an RLC sequence number (i.e., the same RLC sequence number), and each of the plurality of RLC PDU segments includes a specific portion of the PDCP PDU. In some implementations, DU 174 may use the RLC state variable to generate an RLC sequence number. For each of the plurality of RLC PDU segments, DU 174 generates a MAC PDU including the first logical channel IID and the RLC PDU segment, and transmits 562 the MAC PDU to UE 102 using the second G-RNTI. UE 103 receives 562 the MAC PDU using the second G-RNTI, retrieves the second logical channel IID and the RLC PDU segment from the MAC PDU, assembles the RLC PDU segment to obtain a PDCP PDU, identifies the PDCP PDU associated with the MRB based on the second logical channel IID, and retrieves the MBS data packet from the PDCP PDU according to the second PDCP configuration.

[0142] After the MBS resource establishment process 587, CN 110 transmits 548 MBS data for the first MBS session to CU 172, similar to 518. CU 172 then transmits 550 MBS data to DU 174, similar to event 520. Subsequently, DU 174 transmits 552 MBS data to UE 102 via broadcast, similar to event 522.

[0143] Later, CN 110, CU 172, and DU 174 perform 588 an MBS resource release procedure to release resources for the first MBS session. In response to or after performing 588 the MBS resource release procedure, DU 174 stops broadcasting the first MBS session information. To stop broadcasting the first MBS session information, DU 174 may transmit 564 (e.g., broadcast) a second MBS broadcast configuration message that does not include the first MBS session information according to the MBS control information.

[0144] In some implementations, CU 172 includes CU-CP 172A and CU-UP 172B. In such a case, the events of process 587 occur between CU-CP 172A, CN 110, and DU 174 of CU 172. In such a case, events 518, 548, 558 and events 520, 550, 560 occur between CN 110 and CU-UP 172B and between CU-UP 172B and DU 174, respectively. After receiving the MBS context establishment response message of process 587, CU-CP 172A may send an MBS bearer context establishment request message including a second MBS session ID for a second MBS session and / or MRBIID of an MRB to CU-UP 172B to request CU-UP to establish an MBS bearer context for the second MBS session and / or MRB. In some implementations, CU-CP 172A excludes the PDU session IID from the MBS bearer context establishment request message. In response to the MBS bearer context setup request message, CU-UP 172B may generate an MBS bearer context and send an MBS bearer context setup response message to CU-CP 172A. In some implementations, CU-UP may include a second CU DL transport layer configuration in the MBS bearer context setup response message, so that CU-CP 172A may include at least one second CU DL transport layer configuration in the MBS session resource setup response message. Thus, CN 110 may transmit 558 MBS data for the second MBS session to CU-UP 172B via at least one second public CN to BSDL tunnel.

[0145] In some implementations, the CU-CP 172A may include the second PDCP configuration in the MBS bearer context setup request message, and the CU-UP 172B transmits 560 the MBS data for the second MBS session according to the second PDCP configuration. In some implementations, the CU-UP 172B establishes one or more PDCP entities according to the second PDCP configuration, and transmits 560 the MBS data for the second MBS session to the DU 174 using the one or more PDCP entities. In some implementations, the CU-CP 172A includes the MRBIID in the MBS bearer context setup request message, and the CU-CP 172A may associate each of the second PDCP configurations with a specific MRB / MRBIID of the MRB / MRBIIDs, and indicate the association in the MBS bearer context setup request message. In some implementations, CU-CP 172A includes at least one second DU DL transport layer configuration in the MBS bearer context setup request message so that CU-UP 172B can transmit 560 MBS data of the second MBS session to DU 174 via at least one second common CU-to-DU DL tunnel.

[0146] In some implementations, the MBS bearer context may include a second PDCP configuration, at least one second DU DL transport layer configuration, and / or a second CU DL transport layer configuration.

[0147] Fig.5I is a message passing diagram of an example scenario 500I that is similar to scenarios 500A-E, except that the base station 104 later modifies the resources used for the first MBS session. Scenario 500I may start with any of the MBS resource establishment procedures 586A-E.

[0148] After transmitting 518 the MBS data, CN 110 may determine to modify the resources for the first MBS session. In response to the determination, CN 110 transmits 535 an MBS session resource modification request message including the first MBS session IID to CU 172 to request CU 172 to modify the resources for the first MBS session. In response to or after receiving 535 the MBS session resource modification request message, CU 172 transmits 537 an MBS context modification request message to DU 174 to request DU 174 to modify the resources for the first MBS session or MRB. In some implementations, CU 172 may include the first MBS session IID and / or MRBIID in the MBS context modification request message. In response, DU 174 modifies the resources for the first MBS session or MRB and transmits 539 an MBS context modification response message to CU 172. In response to or after receiving 539 the MBS context modification response message, the CU 172 may transmit 541 an MBS session resource modification response message to the CN 110 to confirm that the resources for the first MBS session have been modified.

[0149] Events 535, 537, 539, and 541 are Figure 5H It is collectively referred to as MBS resource modification process 591.

[0150] In some implementations, CN 110 may include the new QoS configuration in an MBS session resource modification request message to request CU 174 to modify resources for the first MBS session. In such cases, CU 172 may include the new QoS configuration in an MBS context modification request message. Thus, DU 174 may enforce the new QoS configuration to transmit 552 MBS data for the first MBS session.

[0151] In some implementations, the DU 174 may transmit 517 a new MBS broadcast configuration message including new MBS session information for the first MBS session via one or more cells according to the MBS control information in response to or as a result of the MBS resource modification procedure 591. The new MBS session information may include a first MBS session ID, a first MRB configuration, a new MRB configuration (described below), and / or a DRX configuration (i.e., a first DRX configuration or a new DRX configuration described below). In some implementations, the DU 174 may generate the new MBS session information or the new MBS broadcast configuration message, such as for Figure 5A In other implementations, CU 172 may generate new MBS session information or new MBS broadcast configuration messages, such as for Figure 5C As described.

[0152] In some implementations, CU 172 may generate a new DRX cycle configuration that configures or includes a new DRX cycle length, and include the new DRX cycle configuration in an MBS context modification request message. In some implementations, CU 172 may determine the new DRX cycle length based on the new QoS configuration. In other implementations, CU 172 may receive the new DRX cycle length in an MBS session resource modification request message. After receiving the new DRX cycle length, DU 174 may generate a new DRX configuration (e.g., DRX-Config MII E) based on the new DRX cycle length. In some implementations, DU 174 generates new MBS session information including the new DRX configuration, and generates a new MBS broadcast configuration message including the new MBS session information. In other implementations, DU 174 includes the new DRX configuration in an MBS context modification response message. In such cases, CU 172 generates new MBS session information including the new DRX configuration, and transmits a CU-to-DU message (e.g., F1AP message) including the new MBS session information to DU 174. Then, DU 174 generates a new MBS broadcast configuration message including the new MBS session information. Alternatively, CU 172 generates a new MBS broadcast configuration message including the new MBS session information, and transmits a CU-to-DU message (eg, F1AP message) including the new MBS session information to DU 174.

[0153] In some implementations, CU 172 may determine to configure additional MRBs for the first MBS session in response to the MBS session resource modification request message or based on the new QoS configuration. For example, the new QoS configuration includes a new QoS flow ID for the new QoS flow, and CU 172 determines to configure additional MRBs for the new QoS flow. In response to the determination, CU 172 may include additional PDCP configurations for the additional MRBs in the MBS context modification request message, similar to event 504. CU 172 may or may not include additional MRBs|IDs for the additional MRBs in the MBS context modification request message. After receiving the additional PDCP configuration, DU 174 may generate additional RLC configurations for the additional PDCP configuration or the additional MRBs. The additional RLC configuration includes an additional logical channel ID. DU 174 may generate an additional MRB configuration including an additional RLC configuration and an additional PDCP configuration, generate new MBS session information (e.g., MBS-SessionInfo|IE) including a first MBS session ID, a first G-RNTI, a first MRB configuration, and an additional MRB configuration, and generate a new MBS broadcast configuration message including the new MBS session information. Then, DU 174 transmits 517 the new MBS broadcast configuration message via one or more cells according to the MBS control information, similar to event 516. In some implementations, DU 174 may include a new G-RNTI (value) in the new MBS session information instead of the first G-RNTI (value).

[0154] In an alternative implementation, DU 174 includes the additional RLC configuration in the MBS context modification response message, similar to event 505. In such a case, CU 172 may generate new MBS session information, similar to event 511. In the case where DU 174 includes a new G-RNTI (value) for the first MBS session in the MBS context modification response message, CU 172 includes the new G-RNTI (value) instead of the first G-RNTI (value) in the new MBS session information. In some implementations, CU 172 may transmit a CU-to-DU message including the new MBS session information to DU 174. In such a case, DU 174 generates a new MBS broadcast configuration message including the new MBS session information, and transmits 517 the new MBS broadcast configuration message to UE 102. In other implementations, CU 172 generates a new MBS broadcast configuration message including the new MBS session information, and transmits 517 the new MBS broadcast configuration message to UE 102.

[0155] In some implementations, DU 174 may include an additional DU DL transport layer configuration to configure an additional common CU to DU DL tunnel for an additional MRB. The additional DU DL transport layer configuration includes transport layer information, such as a transport layer address (e.g., an IP address) and / or a TEID to identify the additional common CU to DU DL tunnel. DU 174 may receive 550 MBS data for a first MBS session via the additional common CU to DU DL tunnel and transmit 552 the MBS data using the additional logical channel ID, similar to event 522. DU 174 may receive 550 MBS data for a first MBS session via the first common CU to DU DL tunnel and transmit 552 the MBS data using the first logical channel ID, similar to event 522.

[0156] Next, refer to FIG. 6A to FIG. 11 discuss Figure 1A and Figure 1B Several example methods may be implemented by the apparatus shown in FIG. 1 , such as the CU 172 (which may include the CU-CP 172A and the CU-UP 172B) and the DU 174 of the base station 104. FIG. 6A to FIG. 11 The example methods described may be performed during the above-described scenarios 500A-500I. Each of these methods may be implemented as a set of instructions stored on a non-transitory computer-readable medium and executable by one or more processors.

[0157] First reference Fig. 6A , a DU (such as DU 174) may implement method 600A to transmit configuration parameters for transmitting MBS data for an MBS session.

[0158] Method 600A begins at block 602, where the DU receives at least one first CU-to-DU message including a first MBS session|ID for a first MBS session from a first RAN node (see, e.g., events 503, 504, 510, 513, 537, 586A-E, 591). At block 604, the DU generates a first MBS broadcast configuration message including first MBS session information for the first MBS session (see, e.g., events 512, 515, 586A-E, 591). Alternatively, the DU receives the first MBS broadcast configuration message in one of the at least one first CU-to-DU message from the first RAN node (see, e.g., event 513). At block 606, the DU transmits the first MBS broadcast configuration message via one or more cells (see, e.g., events 516, 517, 546). At block 608, the DU receives MBS data for the first MBS session from a second RAN node (see, e.g., events 520, 550). At block 610, the DU transmits MBS data for a first MBS session via one or more cells using the first MBS session information (eg, 522, 552).

[0159] At block 612, the DU receives at least one second CU-to-DU message including a second MBS session IID for a second MBS session from a third RAN node (see, e.g., event 587). At block 614, the DU generates a second MBS broadcast configuration message including the first MBS session information and the second MBS session information for the second MBS session (see, e.g., event 587). Alternatively, the DU receives the second MBS broadcast configuration message in one of the at least one second CU-to-DU message from the third RAN node (see, e.g., events 513, 587). Since the first MBS broadcast configuration message does not include the second MBS session information, the second MBS broadcast configuration message replaces the first MBS broadcast configuration message. At block 616, the DU transmits the second MBS broadcast configuration message via one or more cells (see, e.g., event 556), as described for scenario 500H. At block 618, the DU receives MBS data for the second MBS session from a fourth RAN node (see, e.g., event 560). At block 620, the DU transmits MBS data for the second MBS session via one or more cells using the second MBS session information (see, e.g., event 562). After transmitting the second MBS broadcast configuration message, the DU may receive subsequent MBS data for the first MBS session from the second RAN node and transmit the subsequent MBS data via one or more cells using the first MBS session information.

[0160] According to method 600A, the DU may transmit new MBS session information for a new MBS session.

[0161] In some implementations, at least one first CU-to-DU message may include an MBS session establishment list including a first MBS session ID. Similarly, at least one second CU-to-DU message may include an MBS session establishment list including a second MBS session ID. In some implementations, the DU may generate the first MBS session information and / or the second MBS session information. In other implementations, the DU may receive the first MBS session information and / or the second MBS session information from the first RAN node and / or the third RAN node, respectively. In such cases, the DU may include the first MBS session information and / or the second MBS session information in the first MBS broadcast configuration message and the second MBS broadcast configuration message, respectively.

[0162] In some implementations, the first MBS session information includes a first MBS session ID, a first G-RNTI, and / or at least one first MRB configuration. Each of the at least one first MRB configuration may include a first PDCP configuration and / or a first RLC configuration. The first MBS session information may also include a first DRX configuration. Similarly, the first MBS session information may include a second MBS session ID, a second G-RNTI, and / or at least one second MRB configuration. Each of the at least one second MRB configuration may include a second PDCP configuration and / or a second RLC configuration. The second MBS session information may also include a second DRX configuration.

[0163] In some implementations, at least one first CU to DU message includes a first PDCP configuration. In other implementations, at least one first CU to DU message does not include the first PDCP configuration. In such a case, in one implementation, the DU may receive the first PDCP configuration from a first operation, administration, and maintenance (OAM) node. In another implementation, the first PDCP configuration is pre-configured for the first MBS session ID. That is, the DU has stored the first PDCP configuration before receiving the at least one first CU to DU message.

[0164] In some implementations, at least one second CU to DU message includes a second PDCP configuration. In other implementations, at least one second CU to DU message does not include the second PDCP configuration. In such a case, in one implementation, the DU may receive the second PDCP configuration from the second OAM. In another implementation, the second PDCP configuration is pre-configured for the second MBS session ID. That is, the DU has stored the second PDCP configuration before receiving the at least one second CU to DU message. The first and second OAM nodes may be the same OAM node or different OAM nodes.

[0165] In some implementations, the first RAN node and the second RAN node are the same RAN node (e.g., CU). In other implementations, the first RAN node and the second RAN node are different RAN nodes. In such cases, the first RAN node may be a CU-CP and the second RAN node may be a CU-UP. In some implementations, the third RAN node and the fourth RAN node are the same RAN node (e.g., CU). In other implementations, the third RAN node and the fourth RAN node are different RAN nodes. In such cases, the third RAN node may be a CU-CP and the fourth RAN node may be a CU-UP. In some implementations, the first RAN node and the third RAN node may be the same CU or CU-CP. In other implementations, the first RAN node and the third RAN node are different CUs or CU-CPs. In some implementations, the second RAN node and the fourth RAN node are the same CU-UP. In other implementations, the second RAN node and the fourth RAN node are different CU-UPs.

[0166] In response to at least one first CU to DU message, the DU may generate a first DRX configuration for a first DRX cycle in some implementations. In the first DRX cycle configuration, the DU may include at least one first DRX parameter, such as a DRX on duration timer value, a DRX inactivity timer value, a DRX slot offset value, a DRX cycle start offset configuration, a DRX retransmission timer value, and / or a DRX HARQ round trip time timer value. The DRX cycle start offset configuration indicates or includes a DRX cycle length and a subframe number at which the first DRX cycle starts. In some implementations, at least one first CU to DU message may include a first DRX cycle configuration for a first MBS session. The first DRX cycle configuration includes a first DRX cycle length. In some implementations, the first DRX cycle configuration is a CU to DU interface protocol II E. In such a case, the DU configures the DRX cycle length in the DRX cycle start offset configuration as the first DRX cycle length. In the case where the at least one first CU to DU message does not include a DRX cycle configuration for the first MBS session, the DU configures the DRX cycle length in the DRX cycle start offset configuration as a pre-configured DRX cycle length.

[0167] In other implementations, the DU receives the first DRX configuration from the first RAN node in one of the at least one first CU-to-DU message, rather than autonomously generating the first DRX configuration.

[0168] Similarly, in response to at least one second CU to DU message, the DU may generate a second DRX configuration for a second DRX cycle in some implementations. In the second DRX cycle configuration, the DU may include at least one second DRX parameter, such as a DRX on duration timer value, a DRX inactivity timer value, a DRX slot offset value, a DRX cycle start offset configuration, a DRX retransmission timer value, and / or a DRX HARQ round trip time timer value. The DRX cycle start offset configuration indicates or includes a DRX cycle length and a subframe number at which the second DRX cycle starts. In some implementations, at least one first CU to DU message may include a second DRX cycle configuration for a first MBS session. The second DRX cycle configuration includes a second DRX cycle length. In some implementations, the second DRX cycle configuration is a CU to DU interface protocol II E. In such a case, the DU configures the DRX cycle length in the DRX cycle start offset configuration as the second DRX cycle length. In the case where at least one second CU to DU message does not include a DRX cycle configuration, the DU configures the DRX cycle length in the DRX cycle start offset configuration as a pre-configured DRX cycle length.

[0169] In other implementations, the DU receives the second DRX configuration from the third RAN node in one of the at least one second CU-to-DU message, instead of autonomously generating the first DRX configuration.

[0170] In some implementations, the first DRX cycle length and the second DRX cycle length may be the same or different. The RAN node (e.g., the first or third RAN node or DU) may determine the DRX cycle length (e.g., the first or second DRX cycle length) based on one or more QoS configurations required for the MBS session (e.g., the first or second MBS session).

[0171] In some implementations, at least one first DRX parameter and at least one second DRX parameter include the same or different parameters. For example, at least one first DRX parameter and at least one second DRX parameter include a first on-duration of a first DRX cycle and a second on-duration of a second DRX cycle, respectively. The DU transmits MBS data of a first MBS session and MBS data of a second MBS session in the first on-duration and the second on-duration, respectively. The DU may configure the first on-duration and the second on-duration to be non-overlapping so as to provide sufficient radio resources to transmit the MBS data of the first MBS session and the MBS data of the second MBS session. On the other hand, the DU may configure the first on-duration and the second on-duration to be partially or completely overlapping so as to simplify the DU implementation and save power for the UE to simultaneously receive the first MBS session and the second MBS session.

[0172] Figure 6B is a flow chart of an example method 600B, which is similar to method 600A, except that the DU receives a CU-to-DU message including session IIDs for two MBS sessions instead of a single MBS session.

[0173] Method 600B begins at block 603, where the DU receives a CU-to-DU message from a first RAN node including a first MBS session ID and a third MBS session ID for a first MBS session and a third MBS session, respectively (see, e.g., events 503, 504, 510, 513, 537, 586A-E, 591). In some implementations, the CU-to-DU message may be Fig. 6A At box 605, the DU generates a first MBS broadcast configuration message including first MBS session information and third MBS session information for the first MBS session and the third MBS session, respectively (see, e.g., events 512, 515, 586A-E, 591). Alternatively, the DU receives the first MBS broadcast configuration message in a CU-to-DU message from the first RAN node (see, e.g., event 513). After transmitting the first MBS broadcast configuration message, the DU may receive MBS data for the first MBS session and MBS data for the third MBS session at boxes 608 and 619, respectively. At box 610, the DU transmits the MBS data for the first MBS session via one or more cells using the first MBS session information. At box 621, the DU transmits the MBS data for the third MBS session via one or more cells using the third MBS session information.

[0174] In some implementations, the third MBS session information includes a third MBS session ID, a third G-RNTI and / or at least one third MRB configuration. Each of the at least one third MRB configuration may include a third PDCP configuration and / or a third RLC configuration. The third MBS session information may also include a third DRX configuration. In some implementations, the CU to DU message includes a first PDCP configuration and / or a third PDCP configuration. In other implementations, the CU to DU message does not include the first and / or third PDCP configuration. In such a case, in one implementation, the DU may receive the first and / or third PDCP configuration from the first OAM node. In another implementation, the first and / or third PDCP configurations are pre-configured for the first and / or third MBS session IDs, respectively. That is, the DU has stored the first and / or third PDCP configurations before receiving the CU to DU message.

[0175] In response to the CU to DU message, the DU may, in some implementations, generate a first DRX configuration for a first DRX cycle, such as for Fig. 6A As described. In response to the CU-to-DU message, the DU may generate a third DRX configuration for a third DRX cycle in some implementations. In the third DRX cycle configuration, the DU may include at least one third DRX parameter, such as a DRX on duration timer value, a DRX inactivity timer value, a DRX slot offset value, a DRX cycle start offset configuration, a DRX retransmission timer value, and / or a DRX HARQ round trip time timer value. The DRX cycle start offset configuration indicates or includes a DRX cycle length and a subframe number at which the third DRX cycle starts. In some implementations, the CU-to-DU message may include the first DRX cycle configuration for the first MBS session, such as for Fig. 6A Described. The CU-to-DU message may include a third DRX cycle configuration for a third MBS session. The third DRX cycle configuration includes a third DRX cycle length. In some implementations, the third DRX cycle configuration is a CU-to-DU interface protocol | IE. In such a case, the DU configures the DRX cycle length in the DRX cycle start offset configuration to the third DRX cycle length. In the case where the CU-to-DU message does not include a DRX cycle configuration for the third MBS session, the DU configures the DRX cycle length in the DRX cycle start offset configuration to the pre-configured DRX cycle length.

[0176] In other implementations, the DU receives the third DRX configuration from the first RAN node in one of the at least one first CU-to-DU message, rather than autonomously generating the third DRX configuration.

[0177] In some implementations, the first DRX cycle length and the third DRX cycle length may be the same or different. The RAN node (e.g., the first RAN node or the DU) may determine the DRX cycle length (e.g., the first or third DRX cycle length) based on one or more QoS configurations required for the MBS session (e.g., the first or third MBS session).

[0178] In some implementations, at least one first DRX parameter and at least one third DRX parameter include the same or different parameters. For example, at least one first DRX parameter and at least one third DRX parameter include a first on-duration of a first DRX cycle and a third on-duration of a third DRX cycle, respectively. The DU transmits MBS data of a first MBS session and MBS data of a third MBS session in the first on-duration and the third on-duration, respectively. The DU may configure the first on-duration and the third on-duration to be non-overlapping so as to provide sufficient radio resources to transmit the MBS data of the first MBS session and the MBS data of the third MBS session. On the other hand, the DU may configure the first on-duration and the third on-duration to be partially or completely overlapping so as to simplify the DU implementation and save power for the UE to simultaneously receive the first MBS session and the third MBS session.

[0179] Next reference Fig. 7A , a CU (such as CU 172) may implement method 700A to transmit configuration parameters for transmitting MBS data for an MBS session. In some implementations, a CU-CP and a CU-UP (such as CU-CP 172A and CU-UP 172B) of a CU implement method 700A, respectively. Control plane functions that may be performed by a CU-CP are shown in a box labeled "CP", and user plane functions that may be performed by a CU-UP are shown in a box labeled "UP". Figure 7B and FIG. 9A to FIG. 9B These “CP” and “UP” boxes are similarly used in to illustrate the control plane and user plane functions that can be performed by the CU-CP and CU-UP, respectively.

[0180] Method 700A starts at block 702, where a CU or CU-CP receives a first CN to BS message including a first MBS session ID from a first CN node to request resources for a first MBS session (see, e.g., events 502, 586A-E). At block 704, the CU or CU-CP transmits at least one first CU to DU message including the first MBS session ID to at least one first DU to broadcast a first MBS broadcast configuration message (see, e.g., events 503, 504, 510, 513, 537, 586A-E, 591). At block 706, the CU or CU-CP transmits at least one first CP to UP message to at least one first CU-UP to configure at least one first CU-UP to receive MBS data for the first MBS session from a second CN and to configure at least one first CU-UP to transmit MBS data to at least one first DU. At block 708, the CU or CU-UP receives MBS data for the first MBS session from the second CN node (see, e.g., events 518, 548). At block 710 , a CU or CU-UP transmits MBS data for a first MBS session to at least one first DU (see, eg, events 520 , 550 ).

[0181] At block 712, the CU or CU-CP receives a second first CN to BS message including a second MBS session ID from a third CN node to request resources for a second MBS session (see, e.g., event 587). At block 714, the CU or CU-CP transmits at least one second CU to DU message including a second MBS session ID to at least one second DU to cause the at least one second DU to broadcast a second MBS broadcast configuration message (see, e.g., event 587), as described for scenario 500H. At block 716, the CU or CU-CP transmits at least one second CP to UP message to at least one second CU-UP to configure the at least one second CU-UP to receive MBS data for the second MBS session from the fourth CN and to configure the at least one second CU-UP to transmit the MBS data to at least one second DU. At block 718, the CU or CU-UP receives MBS data for the second MBS session from the fourth CN node (see, e.g., event 560). At block 720, the CU or CU-UP transmits MBS data for the second MBS session to at least one second DU (see, e.g., event 562).

[0182] The first MBS session|ID and the second MBS session|ID identify the first MBS session and the second MBS session, respectively. In some implementations, the first CN node and the third CN node are the same CN node (e.g., AMF). In other implementations, the first CN node and the third CN node are different CN nodes (e.g., AMF). In some implementations, the second CN node and the fourth CN node are the same CN node (e.g., UPF). In other implementations, the second CN node and the fourth CN node are different CN nodes (e.g., (MB-)UPF). In some implementations, at least one first DU and at least one second DU may include the same DU and / or different DUs.

[0183] In some implementations, at least one first CU-to-DU message and at least one second CU-to-DU message are as described for Fig. 6A In some implementations, the first and second MBS broadcast configuration messages are as follows: Fig. 6A In some implementations, at least one first CU-to-DU message and at least one second CU-to-DU message may include a first PDCP configuration and a second PDCP configuration, respectively, such as for Fig. 6A In other implementations, at least one first CU-to-DU message and at least one second CU-to-DU message may include a first MRB configuration and a second MRB configuration, respectively, such as for Fig. 6A In other implementations, at least one first CU-to-DU message and at least one second CU-to-DU message may include first MBS session information and second MBS session information, respectively, such as for Fig. 6A As described.

[0184] Figure 7B is with Fig. 7A 700A, except for blocks 703, 705, 707, 719, and 721. Similar to method 700A, in some implementations, the CU-CP and CU-UP of the CU implement method 700B, where the example corresponding functions of the CU-CP and CU-UP are described in Figure 7B In the method 600B, the CU transmits a CU-to-DU message including session IDs for two MBS sessions.

[0185] The method 700B starts at block 703, where the CU or CU-CP receives a CN to BS message including a first MBS session IID and a third MBS session IID from a first CN node to request resources for the first MBS session and the third MBS session, respectively (see, e.g., events 502, 586A-E, 587). At block 705, the CU or CU-CP transmits a CU to DU message including the first MBS session IID and the third MBS session IID to at least one first DU to cause the at least one first DU to broadcast a first MBS broadcast configuration message (see, e.g., events 503, 504, 510, 513, 537, 586A-E, 587, 591). In some implementations, the CU to DU message may be Fig. 7A At box 707, the CU or CU-CP transmits at least one first CP to UP message to at least one first CU-UP to configure the at least one first CU-UP to receive MBS data for the first MBS session and the third MBS session from the second CN, and to configure the at least one first CU-UP to transmit the MBS data to at least one first DU. At box 719, the CU or CU-UP receives the MBS data for the third MBS session from the second CN node (see, e.g., events 518, 548). At box 721, the CU or CU-UP transmits the MBS data for the third MBS session to at least one first DU (see, e.g., events 520, 550).

[0186] The first MBS session ID and the third MBS session IID identify the first MBS session and the third MBS session, respectively. In some implementations, the CU-to-DU message is such as for Figure 6B In some implementations, the first MBS broadcast configuration message is such as for Figure 6B In some implementations, the CU-to-DU message may include a first PDCP configuration and a third PDCP configuration, such as for Figure 6B In other implementations, the CU-to-DU message may include the first MRB configuration and the third MRB configuration, respectively, such as for Figure 6B In other implementations, the CU-to-DU message may include the first MBS session information and the third MBS session information, respectively, such as for Figure 6B As described.

[0187] Now, refer to Fig. 8A, a DU (such as DU 174) may implement method 800A to establish and later suspend or release resources for an MBS session. Method 800A begins at block 802, where the DU performs a first CU-DU procedure with a first RAN node to configure resources for an MBS session (see, e.g., events 503, 504, 510, 513, 537, 586A-E, 587, 591). At block 804, the DU transmits an MBS control message including MBS session information for the MBS session via one or more cells in response to the first CU-DU procedure (see, e.g., events 516, 517, 546, 556). For example, the MBS control message may be an MBS broadcast configuration message. At block 806, the DU receives MBS data for the MBS session from a second RAN node (see, e.g., events 520, 550, 560). At block 808, the DU transmits MBS data for the MBS session via one or more cells using the MBS session information (see, e.g., events 522, 552, 562). At block 810, the DU performs a second CU-DU procedure with the first RAN node to suspend or release resources for the MBS session (see, e.g., events 526, 528, 527, 529, 588, 589). The flow may then proceed to block 812 or block 814. At block 812, the DU stops transmitting MBS control messages in response to the second CU-DU procedure (see, e.g., event 532). At block 814, the DU updates the MBS control message in response to the second CU-DU procedure to exclude the MBS session information (see, e.g., event 533). At block 816, the DU transmits the updated MBS control message via one or more cells (see, e.g., event 564).

[0188] In some implementations, the DU may determine to stop transmitting the MBS control message (i.e., proceed to block 812) or to update the MBS control message to exclude the MBS session information (i.e., proceed to block 814) depending on whether the MBS session is the last (i.e., the only) MBS session for which the DU configures resources. In the case where the MBS session is the last MBS session, the DU may stop transmitting the MBS control message. In the case where the MBS session is not the last MBS session (i.e., there are other MBS sessions for which the DU configures resources), the DU may update the MBS control message to exclude the MBS session information of the MBS session and transmit the updated MBS control message.

[0189] In some implementations, the first RAN node and the second RAN node may be the same RAN node (eg, CU). In other implementations, the first RAN node and the second RAN node may be a CU-CP and a CU-UP, respectively.

[0190] Figure 8Bis a flow chart of an example method 800B similar to method 800A, except for blocks 811, 813, 818, and 820. Compared to method 800B, in method 800A, the DU modifies resources for the MBS session. Specifically, at block 811, the DU performs a second CU-DU procedure with the first RAN node to modify resources for the MBS session. At block 813, the DU updates the MBS control message in response to the second CU-DU procedure. At block 818, the DU receives MBS data for the MBS session from the second RAN node. At block 820, the DU transmits the MBS data for the MBS session via one or more cells using the (updated) MBS session information.

[0191] In some implementations, as a result of the second CU-DU process, the DU adds or modifies configuration parameters in the MBS session information. Therefore, the DU updates the MBS control message at block 813 to include the added or modified configuration parameters. In other implementations, the DU receives the new QoS configuration in the CU-to-DU message of the second CU-DU process. In such cases, the DU enforces the new QoS configuration at block 820 to use the (updated) MBS session to transmit MBS data for the MBS session.

[0192] Next reference Fig. 9A , a CU (such as CU 172) may implement method 900A to establish and later release or suspend resources for an MBS session. FIG. 7A to FIG. 7B As discussed, a CU-CP and a CU-UP of a CU (such as CU-CP 172A and CU-UP 172B, respectively) may implement method 900A, wherein example corresponding functions of the CU-CP and the CU-UP are described in Fig. 9A This is indicated by the boxes marked "CP" and "UP".

[0193] Method 900A begins at block 902, where a CU or CU-CP performs a first CN-BS procedure with a CN to configure resources to broadcast an MBS session (see, e.g., events 502, 508, 586A-E). At block 904, the CU or CU-CP performs at least one first CU-DU procedure with at least one DU in response to the first CN-BS procedure to configure resources for the MBS session (see, e.g., events 503, 504, 505, 506, 510, 513, 537, 539, 586A-E, 591). At block 906, the CU or CU-CP performs at least one first CP-UP procedure with at least one CU-UP in response to the first CN-BS procedure to configure resources for the MBS session. At block 908, the CU or CU-UP receives MBS data for the MBS session from the CN (see, e.g., events 518, 548). At block 910, the CU or CU-UP transmits MBS data for a broadcast MBS session via at least one DU (see, e.g., events 520, 550). At block 912, the CU or CU-CP performs a second CN-BS procedure with the CN to release or suspend resources for the MBS session (see, e.g., events 524, 530, 525, 531, 588, 589). At block 914, the CU or CU-CP performs a second CU-DU procedure with at least one DU in response to the second CN-BS procedure to release or suspend resources for the MBS session (see, e.g., events 526, 528, 527, 529, 588, 589). At block 916, the CU or CU-CP performs at least one second CP-UP procedure with at least one CU-UP in response to the second CN-BS procedure to release or suspend resources for the broadcast MBS session.

[0194] Fig. 9B is with Fig. 9A 900A, except for blocks 913, 915, 917, 918, and 920. In addition, similar to method 700A, in some implementations, the CU-CP and CU-UP of the CU implement method 900B, where the example corresponding functions of the CU-CP and CU-UP are in Fig. 9BIndicated by boxes labeled "CP" and "UP". Compared to method 900B, in method 900A, the CU modifies the resources used for the MBS session. At box 913, the CU or CU-CP performs a second CN-BS process with the CN to modify the resources used for the MBS session (see, e.g., events 535, 541, 591). At box 915, the CU or CU-CP performs a second CU-DU process with at least one DU in response to the second CNBS process to modify the resources used for the MBS session (see, e.g., events 537, 539, 591). At box 917, the CU or CU-CP performs at least one second CP-UP process with at least one CU-UP in response to the second CN-BS process to modify the resources used for the MBS session. At box 918, the CU or CU-UP receives MBS data for the broadcast MBS session from the CN (see, e.g., event 548). At block 920, the CU or CU-UP transmits MBS data for the MBS session via at least one DU according to the modified resources (see, eg, event 550).

[0195] refer to Fig.10 , a DU (e.g., DU 174) of a distributed base station (e.g., base station 104 or 106) including a CU (e.g., CU 172) and a DU may implement a method 1000 for configuring a UE (e.g., UE 102) to receive an MBS. The method may be implemented by processing hardware (e.g., processing hardware 130 or 140). At block 1002, the DU receives a CU-to-DU message (e.g., an MBS context setup request message) from the CU identifying an MBS session and requesting the DU to configure resources for the MBS session (e.g., events 504, 503). At block 1004, the DU transmits (e.g., broadcasts) configuration parameters for receiving the MBS session to the UE in response to receiving the CU-to-DU message (e.g., event 516). At a later time, the DU may receive MBS data for the MBS session from the CU and transmit the MBS data to the UE according to the configuration parameters (e.g., events 520, 522).

[0196] In some implementations, the DU generates an MBS session information element (e.g., MBS session information, such as MBS-SessionInfoIE), includes the configuration parameters in the MBS session information element, and transmits the configuration parameters to the UE by transmitting the MBS session information element to the UE (e.g., Figure 5A , Figure 5B and Figure 5E, event 512, 515, event 516 in ). In such an implementation, the DU may receive a PDCP configuration from the CU (e.g., in a CU-to-DU message received at box 1002 (e.g., event 504), or in a second CU-to-DU message after receiving the CU-to-DU message at box 1002 (e.g., event 510)), and include the PDCP configuration in the MBS session information element. Alternatively, the DU may retrieve a PDCP configuration pre-configured at the DU and include the PDCP configuration in the MBS session information element (e.g., event 515). In addition, the DU may receive a DRX configuration and / or MBS neighbor cell information from the CU, and include the DRX configuration and / or MBS neighbor cell information in the MBS session information element. Depending on the implementation, the DU may generate an RLC configuration and / or a group temporary identifier (e.g., G-RNTI), and include the RLC configuration and / or the group temporary identifier in the MBS session information element. The CU-to-DU message may include a session identifier (IID) identifying the MBS session, and the DU may include the session IID in the MBS session information element.

[0197] In other implementations, the DU receives an MBS session information element including the configuration parameters from the CU before transmitting the configuration parameters, and transmits the configuration parameters to the UE by transmitting the MBS session information element (eg, Figure 5C and Figure 5D 513, event 516 in ). In such an implementation, the DU may transmit to the CU information for inclusion in the MBS session information element, such as the RLC configuration and / or the group temporary identifier associated with the MBS session. The DU may transmit the information in a DU to CU message (e.g., event 505) or in a second DU to CU message (e.g., event 509) in response to the CU to DU message. In addition, in such an implementation, the DU may (i) receive an MBS broadcast configuration message (e.g., MBSBroadcast Configuration message) including the MBS session information element from the CU and transmit the MBS broadcast configuration message to the UE, or (ii) receive the MBS session information element from the CU, generate an MBS configuration broadcast message including the MBS session information element, and transmit the MBS broadcast configuration message to the UE.

[0198] Depending on the scenario, method 1000 may also include configuring resources for multiple MBS sessions. The CU-to-DU message received by the DU at block 1002 (i.e., a first CU-to-DU message identifying a first MBS session and requesting the DU to configure first resources for the first MBS session) may identify a second MBS session and request the DU to configure second resources for the second MBS session (e.g., by including a first session ID for the first MBS session and a second session ID for the second MBS session), or the DU may receive a second CU-to-DU message after receiving the CU-to-DU message at block 1002, wherein the second CU-to-DU message identifies the second MBS session and requests the DU to configure second resources for the second MBS session (e.g., by including a second session ID for the second MBS session) (e.g., event 587). To transmit the second configuration parameter, the DU may transmit the first configuration parameter with the second parameter (e.g., by transmitting a first MBS session information element and a second MBS session information element in an MBS broadcast configuration message) (e.g., event 556). If the DU later receives a CU-to-DU message instructing the DU to release or suspend the first resources for the first MBS session, the DU may transmit an MBS broadcast message including the second MBS session information element but not the first MBS session information element (eg, event 564).

[0199] The DU may receive a notification from the CU to release, suspend, or modify resources for the MBS session. For example, the DU may receive a request from the CU to release resources for the MBS session (e.g., event 526). In response, the DU may stop transmitting configuration parameters (e.g., event 532). As another example, the DU may receive a request from the CU to suspend resources for the MBS session (e.g., event 527), and in response, the DU may stop transmitting configuration parameters. The DU may retain the configuration parameters and resume transmitting the configuration parameters in response to receiving a request from the CU to resume resources for the MBS session (e.g., events 536, 542). In yet another example, the DU may receive a request from the CU to modify resources for the MBS session, modify the configuration parameters according to the request, and transmit the modified configuration parameters to the UE (e.g., events 537, 517).

[0200] Go to Fig.11, a CU (e.g., CU 172) of a distributed base station (e.g., base station 104 or 106) including a DU (e.g., DU 174) and a CU may implement a method 1100 for configuring a UE (e.g., UE 102) to receive MBS. The method may be implemented by processing hardware (e.g., processing hardware 130 or 140). At block 1102, the CU receives a CN-to-BS message from the CN requesting the distributed base station to configure resources for an MBS session (e.g., event 502). At block 1104, the CU transmits a CU-to-DU message identifying the MBS session to the DU so that the DU transmits configuration parameters for receiving the MBS session to the UE (e.g., events 504, 503, 510, 513).

[0201] The following list of examples reflects the various embodiments expressly contemplated by the present disclosure:

[0202] Example 1. A method for configuring a user equipment (UE) to receive a multicast and / or broadcast service (MBS) implemented in a distributed unit (DU) of a distributed base station including a central unit (CU) and a distributed unit (DU), the method comprising: receiving, by processing hardware of the DU, a CU-to-DU message from the CU identifying an MBS session and requesting the DU to configure resources for the MBS session; and in response to receiving the CU-to-DU message, transmitting, by the processing hardware, configuration parameters for receiving the MBS session to the UE.

[0203] Example 2. The method as described in Example 1 further includes: generating an MBS session information element; and including the configuration parameter in the MBS session information element, wherein transmitting the configuration parameter includes: transmitting the MBS session information element.

[0204] Example 3. The method of Example 2, further comprising: receiving, by the processing hardware, a Packet Data Convergence Protocol (PDCP) configuration from the CU; wherein generating the MBS session information element comprises including the PDCP configuration in the MBS session information element.

[0205] Example 4. The method of Example 3, wherein receiving the PDCP configuration comprises: receiving the PDCP configuration in the CU to DU message.

[0206] Example 5. A method as described in Example 3, wherein the CU-to-DU message is a first CU-to-DU message, and wherein receiving the PDCP configuration includes: receiving a second CU-to-DU message after receiving the first CU-to-DU message, the second CU-to-DU message including the PDCP configuration.

[0207] Example 6. The method of Example 2, further comprising: retrieving, by the processing hardware, a Packet Data Convergence Protocol (PDCP) configuration pre-configured at the DU; wherein generating the MBS session information element comprises including the PDCP configuration in the MBS session information element.

[0208] Example 7. The method as described in any one of Examples 2 to 6 further includes: receiving, by the processing hardware, a discontinuous reception (DRX) configuration having the PDCP configuration from the CU, wherein generating the MBS session information element includes including the DRX configuration in the MBS session information element.

[0209] Example 8. The method of any one of Examples 2 to 7, further comprising: generating a radio link control (RLC) configuration, wherein generating the MBS session information element comprises including the RLC configuration in the MBS session information element.

[0210] Example 9. The method of any one of Examples 2 to 8, further comprising: generating a group temporary identifier associated with the MBS session, wherein generating the MBS session information element comprises including the group temporary identifier in the MBS session information element.

[0211] Example 10. A method as described in any one of Examples 2 to 9, wherein: receiving the CU-to-DU message includes receiving the CU-to-DU message including a session identifier (ID) identifying the MBS session; and generating the MBS session information element includes including the session identifier in the MBS session information element.

[0212] Example 11. The method of Example 1, further comprising: receiving, by the processing hardware, an MBS session information element including the configuration parameters from the CU before transmitting the configuration parameters, wherein transmitting the configuration parameters comprises transmitting the MBS session information element.

[0213] Example 12. The method of Example 11, further comprising: transmitting, by the processing hardware to the CU, information for inclusion in the MBS session information element.

[0214] Example 13. The method of Example 12, wherein transmitting the information comprises: transmitting a radio link control (RLC) configuration.

[0215] Example 14. The method of Example 12 or 13, wherein transmitting the information comprises transmitting a group temporary identifier associated with the MBS session.

[0216] Example 15. The method of any one of Examples 12 to 14, wherein transmitting the information comprises transmitting the information in a DU to CU message in response to the CU to DU message.

[0217] Example 16. The method as described in any one of Examples 12 to 14 further includes: in response to the CU to DU message, transmitting a first DU to CU message by the processing hardware to the CU, wherein transmitting the information includes transmitting the information in a second DU to CU message after transmitting the first DU to CU message.

[0218] Example 17. A method as described in any one of Examples 11 to 16, wherein: receiving the MBS session information element from the CU includes receiving an MBS broadcast configuration message including the MBS session information element; and transmitting the MBS session information element includes transmitting the MBS broadcast configuration message.

[0219] Example 18. A method as described in any one of Examples 2 to 16, wherein transmitting the MBS session information element includes: generating an MBS broadcast configuration message including the MBS session information element; and transmitting the MBS broadcast configuration message to the UE.

[0220] Example 19. The method of Example 17 or 18, wherein transmitting the MBS broadcast configuration message comprises transmitting an MBSBroadcast Configuration message.

[0221] Example 20. A method as described in any of the preceding examples, wherein: the CU-to-DU message is a first CU-to-DU message that identifies a first MBS session and requests the DU to configure first resources for the first MBS session; the configuration parameter is the first configuration parameter; and the method further includes: receiving, by the processing hardware, a second CU-to-DU message from the CU that identifies a second MBS session and requests the DU to configure second resources for the second MBS session; and in response to receiving the second CU-to-DU message, transmitting, by the processing hardware, to the UE a second configuration parameter for receiving the second MBS session.

[0222] Example 21. The method of Example 20, wherein transmitting the second configuration parameter comprises transmitting the first configuration parameter and the second configuration parameter.

[0223] Example 22. The method of Example 20 or 21, wherein receiving the second CU-to-DU message comprises receiving the second CU-to-DU message including a session identifier (IID) identifying the second MBS session.

[0224] Example 23. A method as described in any one of Examples 1 to 19, wherein: the MBS session is a first MBS session; the resource is a first resource; the configuration parameter is a first configuration parameter; receiving the CU-to-DU message includes: receiving the CU-to-DU message that further identifies a second MBS session and further requests the DU to configure a second resource for the second MBS session; and transmitting the configuration parameter includes: transmitting the first configuration parameter and a second configuration parameter for receiving the second MBS session.

[0225] Example 24. The method of Example 23, wherein receiving the CU-to-DU message comprises: receiving the CU-to-DU message including a first session identifier (IID) identifying the first MBS session and a second session IID identifying the second MBS session.

[0226] Example 25. A method as described in any of Examples 21, 23 or 24, wherein transmitting the first configuration parameter and the second configuration parameter includes: transmitting a first MBS session information element including the first configuration parameter and a second MBS session information element including the second configuration parameter.

[0227] Example 26. The method of Example 25, wherein transmitting the first MBS session information element and the second MBS session information element comprises: transmitting an MBS broadcast configuration message including the first MBS session information element and the second MBS session information element.

[0228] Example 27. The method as described in Example 26 further includes: receiving, by the processing hardware, a third CU-to-DU message from the CU requesting the DU to release or suspend the first resource used for the first MBS session; and modifying, by the processing hardware, the MBS broadcast configuration message to exclude the first MBS session information element; and transmitting, by the processing hardware, to the UE, the MBS broadcast configuration message including the second MBS session information element and excluding the first MBS session information element.

[0229] Example 28. The method of any one of Examples 1 to 26, further comprising: receiving, by the processing hardware, a request from the CU to release the resources used for the MBS session; and stopping, by the processing hardware, transmitting the configuration parameters.

[0230] Example 29. The method of Example 28, further comprising: releasing, by the processing hardware, the configuration parameters.

[0231] Example 30. The method of any one of Examples 1 to 26, further comprising: receiving, by the processing hardware, a request from the CU to suspend the resources used for the MBS session; and stopping, by the processing hardware, transmitting the configuration parameters.

[0232] Example 31. The method of Example 30, further comprising: maintaining the configuration parameters by the processing hardware.

[0233] Example 32. The method of Example 30 or 31, wherein the request is a first request, the method further comprising: receiving, by the processing hardware, a request from the CU to resume the resources for the MBS session; and resuming transmission of the configuration parameters by the processing hardware.

[0234] Example 33. The method as described in any one of Examples 1 to 26 further includes: receiving, by the processing hardware, a request to modify the resources used for the MBS session; modifying, by the processing hardware, the configuration parameters according to the request; and transmitting, by the processing hardware, the modified configuration parameters.

[0235] Example 34. A method as described in any of the preceding examples, wherein receiving the CU to DU message includes: receiving an MBS context establishment request message.

[0236] Example 35. A method as described in any of the preceding examples, wherein transmitting the configuration parameters includes: broadcasting the configuration parameters to multiple UEs, the multiple UEs including the UE.

[0237] Example 36. The method as described in any of the preceding examples further comprises: receiving, by the processing hardware, MBS data for the MBS session from the CU; and transmitting, by the processing hardware, the MBS data to the UE according to the configuration parameters.

[0238] Example 37. A method for configuring a user equipment (UE) to receive a multicast and / or broadcast service (MBS) implemented in a distributed base station including a distributed unit (DU) and a central unit (CU), the method comprising: receiving, by processing hardware of the CU, a CN to BS message from a core network (CN) requesting the distributed base station to configure resources for an MBS session; and transmitting, by the processing hardware, a CU to DU message identifying the MBS session to the DU, so that the DU transmits configuration parameters for receiving the MBS session to the UE.

[0239] Example 38. The method of Example 37, further comprising transmitting, by the processing hardware, a Packet Data Convergence Protocol (PDCP) configuration to the DU, so that the DU includes the PDCP configuration in the configuration parameters.

[0240] Example 39. The method of Example 38, wherein transmitting the PDCP configuration comprises transmitting the PDCP configuration in the CU to DU message.

[0241] Example 40. A method as described in Example 38, wherein: the CU-to-DU message is a first CU-to-DU message; transmitting the PDCP configuration includes: transmitting a second CU-to-DU message including the PDCP configuration to the DU after transmitting the first CU-to-DU message.

[0242] Example 41. A method as described in any of Examples 38 to 40, wherein transmitting the PDCP configuration includes: transmitting a discontinuous reception (DRX) configuration with the PDCP configuration so that the DU includes the DRX configuration in the configuration parameters.

[0243] Example 42. The method of Example 37, further comprising: generating, by the processing hardware, an MBS session information element; including, by the processing hardware, the configuration parameters in the MBS session information element; and transmitting, by the processing hardware, the MBS session information element to the DU.

[0244] Example 43. The method of Example 42, further comprising: generating, by the processing hardware, a Packet Data Convergence Protocol (PDCP) configuration; and including, by the processing hardware, the PDCP configuration in the configuration parameters.

[0245] Example 44. The method of Example 42 or 43, further comprising: generating, by the processing hardware, a discontinuous reception (DRX) configuration; and including, by the processing hardware, the DRX configuration in the configuration parameters.

[0246] Example 45. The method of any one of Examples 42 to 44, further comprising: generating, by the processing hardware, an MBS broadcast configuration message including the MBS session information element; and transmitting, by the processing hardware, the MBS broadcast configuration message to the DU.

[0247] Example 46. The method of any one of Examples 42 to 45, further comprising: receiving, by the processing hardware, information from the DU for inclusion in the MBS session information element, wherein generating the MBS session information element comprises including the information in the MBS session information element.

[0248] Example 47. The method of Example 46, wherein receiving the information comprises receiving a radio link control (RLC) configuration.

[0249] Example 48. The method of Example 46 or 47, wherein receiving the information comprises receiving a group temporary identifier associated with the MBS session.

[0250] Example 49. A method as described in any of Examples 46 to 48, wherein receiving the information includes: receiving the information in a DU to CU message in response to the CU to DU message.

[0251] Example 50. The method as described in any one of Examples 46 to 48 further includes: receiving a first DU to CU message by the processing hardware in response to the CU to DU message; and receiving a second DU to CU message including the information by the processing hardware after receiving the first DU to CU message.

[0252] Example 51. A method as described in any one of Examples 37 to 50, wherein: the CN to BS message is a first CN to BS message requesting the distributed base station to configure first resources for a first MBS session; the CU to DU message is a first CU to DU message; the configuration parameter is a first configuration parameter; and the method further includes: receiving, by the processing hardware, a second CN to BS message requesting the distributed base station to configure second resources for a second MBS session; and transmitting, by the processing hardware, a second CU to DU message to the UE, so that the DU transmits a second configuration parameter for receiving the second MBS session.

[0253] Example 52. A method as described in Example 51, wherein: receiving the second CN to BS message includes: receiving the second CN to BS message including a session identifier (ID) identifying the second MBS session; and transmitting the second CU to DU message includes: transmitting the second CU to DU message including the session ID identifying the second MBS session.

[0254] Example 53. A method as described in any one of Examples 37 to 50, wherein: the MBS session is a first MBS session; the CN to BS message is a first CN to BS message; the resource is a first resource; the configuration parameter is a first configuration parameter; receiving the CN to BS message includes: receiving the CN to BS message that further requests the distributed base station to configure a second resource for a second MBS session; and transmitting the CU to DU message includes: transmitting the CU to DU message that further identifies the second MBS session so that the DU transmits the first configuration parameter and the second configuration parameter for receiving the second MBS session.

[0255] Example 54. A method as described in Example 53, wherein receiving the CN to BS message includes: receiving the CN to BS message including a first session identifier (IID) identifying the first MBS session and a second session IID identifying the second MBS session; and transmitting the CU to DU message includes: transmitting the CU to DU message including the first session IID and the second session IID.

[0256] Example 55. The method of any one of Examples 37 to 54, further comprising: transmitting, by the processing hardware to the DU, a request to release or suspend the resources used for the MBS session.

[0257] Example 56. The method of any one of Examples 37 to 54, further comprising: transmitting, by the processing hardware to the DU, a request to modify the resources used for the MBS session.

[0258] Example 57. The method of Example 55 or 56, wherein transmitting the request comprises transmitting the request in response to receiving a message from the CN.

[0259] Example 58. The method of any one of Examples 37 to 57, further comprising: receiving, by the processing hardware, MBS data for the MBS session from the CN; and transmitting, by the processing hardware, the MBS data to the DU.

[0260] Example 59. The method of Example 58, further comprising: transmitting, by a control plane (CP) logical node of the central unit to a user plane (UP) logical node of the central unit, a CP to UP message to configure the UP logical node to receive the MBS data from the CN and transmit the MBS data to the DU.

[0261] Example 60. The method of any one of Examples 37 to 59, wherein transmitting the CU to DU message comprises transmitting an MBS context establishment request message.

[0262] Example 61. A method as described in any of Examples 37 to 60, wherein transmitting the CU-to-DU message includes: transmitting the CU-to-DU message including a session identifier (IID) identifying the MBS session.

[0263] Example 62. A network node comprising processing hardware and configured to implement a method according to any of the preceding examples.

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

[0265] In some implementations, "message" is used and it can be replaced by "information element (IE)", or vice versa. In some implementations, "IE" is used and it can be replaced by "field", or vice versa. In some implementations, "configuration" can be replaced by "configurations" or configuration parameters. In some implementations, "MBS" can be replaced by "multicast" or "broadcast". The messages described in the above events are only examples and should not limit the applicability of the present invention. In some implementations, messages sent from CU to DU can be summarized as CU to DU messages, and messages sent from DU to CU can be summarized as DU to CU messages. In some implementations, CU to DU messages and DU to CU messages can be F1AP messages. In some implementations, messages sent from CU-CP to CU-UP can be summarized as CP to UP messages, and messages sent from CU-UP to CU-CP can be summarized as UP to CP messages. In some implementations, CP to UP messages and UP to CP messages can be E1 application protocol (E1AP) messages.

[0266] The user device (e.g., UE 102 or 103) in which the technology of the present disclosure can be implemented can be any suitable device capable of wireless communication, such as a smart phone, a tablet computer, a laptop computer, a mobile game console, a point of sale (POS) terminal, a health monitoring device, a drone, a camera, a media streaming dongle or another personal media device, a wearable device (such as a smart watch), a wireless hotspot, a femtocell base station, or a broadband router. In addition, in some cases, the user device may be embedded in an electronic system, such as a head unit of a vehicle or an advanced driver assistance system (ADAS). In addition, the user device can be operated as an Internet of Things (IoT) device or a mobile Internet device (MID). Depending on the type, the user device may include one or more general-purpose processors, a computer-readable memory, a user interface, one or more network interfaces, one or more sensors, etc.

[0267] Certain embodiments of the present disclosure are described as including logic or multiple components or modules. A module may 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 that is capable of performing certain operations and may be configured or arranged in a particular manner. A hardware module may include dedicated circuits or logic that are permanently configured (e.g., as a dedicated processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC)) to perform certain operations. A hardware module may also include programmable logic or circuits (e.g., contained within a general-purpose processor or other programmable processor) that are temporarily configured by software to perform certain operations. The decision to implement a hardware module in a dedicated and permanently configured circuit or in a temporarily configured circuit (e.g., configured by software) may be driven by cost and time considerations.

[0268] When implemented in software, the techniques may be provided as part of an operating system, as a library used by multiple applications, as a specific software application, etc. The software may be executed by one or more general-purpose processors or by one or more special-purpose processors.

[0269] After reading this disclosure, those skilled in the art will understand additional alternative structures and functional designs for transmitting MBS information through 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, changes 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 of the present disclosure.

Claims

1. A method for configuring a user equipment (UE) to receive a multicast and / or broadcast service (MBS) implemented in a distributed base station including a central unit (CU) and a distributed unit (DU), the method comprising: receiving, by processing hardware of the DU from the CU, an MBS context establishment request for an MBS session to request the DU to configure resources for the MBS session, wherein the MBS context establishment request includes a packet data convergence protocol (PDCP) configuration; In response to receiving the MBS context establishment request, the processing hardware transmits, to the UE, configuration parameters for receiving the MBS session, including at least the PDCP configuration.

2. The method of claim 1, further comprising: Generate an MBS session information element; as well as including the configuration parameters in the MBS session information element, The transmission of the configuration parameters comprises: The MBS session information element is transmitted.

3. The method of claim 2, wherein: Receiving the MBS context establishment request includes receiving the MBS context establishment request including a session identifier (ID) identifying the MBS session; and Generating the MBS session information element includes including the session identifier in the MBS session information element.

4. The method of claim 1, further comprising: receiving, by the processing hardware, from the CU an MBS session information element including at least some of the configuration parameters prior to transmitting the configuration parameters, The transmitting of the configuration parameter includes transmitting the MBS session information element.

5. The method of claim 4, further comprising: Information for inclusion in the MBS session information element is transmitted by the processing hardware to the CU.

6. The method according to any one of claims 1 to 5, further comprising: receiving, by the processing hardware, from the CU a request to release the resources for the MBS session; as well as Transmission of the configuration parameters is stopped by the processing hardware.

7. The method of claim 6, further comprising: The configuration parameters are released by the processing hardware.

8. The method according to any one of claims 1 to 5, further comprising: receiving, by the processing hardware, a request to modify the resources for the MBS session; modifying, by the processing hardware, the configuration parameters according to the request; as well as The modified configuration parameters are transmitted by the processing hardware.

9. A method for configuring a user equipment (UE) to receive a multicast and / or broadcast service (MBS) implemented in a distributed base station comprising a distributed unit (DU) and a central unit (CU), the method comprising: receiving, by processing hardware of the CU, a CN to BS message from a core network (CN) requesting the distributed base station to configure resources for an MBS session; as well as An MBS context establishment request identifying the MBS session and including a Packet Data Convergence Protocol (PDCP) configuration is transmitted by the processing hardware to the DU, so that the DU transmits configuration parameters including the PDCP configuration to the UE for receiving the MBS session.

10. The method of claim 9, further comprising: generating, by the processing hardware, an MBS session information element; including, by the processing hardware, at least some of the configuration parameters in the MBS session information element; and The MBS session information element is transmitted by the processing hardware to the DU.

11. The method of claim 10, further comprising: generating, by the processing hardware, an MBS broadcast configuration message including the MBS session information element; as well as The MBS broadcast configuration message is transmitted to the DU by the processing hardware.

12. The method of claim 10 or 11, further comprising: receiving, by the processing hardware, information from the DU for inclusion in the MBS session information element, The generating the MBS session information element includes including the information in the MBS session information element.

13. The method of claim 12, wherein receiving the information comprises: The information is received in a DU to CU message after receiving the MBS context establishment request.

14. The method of any one of claims 9 to 13, further comprising: A request to release, modify or suspend the resources for the MBS session is transmitted by the processing hardware to the DU.

15. The method of any one of claims 9 to 14, further comprising: A CP to UP message is transmitted by a control plane (CP) logical node of the central unit to a user plane (UP) logical node of the central unit to configure the UP logical node to receive MBS data from the CN and transmit the MBS data to the DU.

16. A network node comprising processing hardware and configured to implement a method according to any preceding claim.