Managing multicast and unicast data transmission for MBS
By establishing common tunnels and using tunnel-based multicast/unicast methods, the management of MBS data transmission in 5G NR networks is optimized, addressing the unclear communication methods in multi-radio dual connectivity scenarios and improving network efficiency.
Patent Information
- Application Number
- JP2024523738
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2021-10-20
- Filing Date
- 2022-10-18
- Publication Date
- 2024-11-06
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
The challenge in 5G NR networks is the unclear method for base stations to receive and transmit multicast and broadcast services (MBS) data packets to multiple UEs, particularly in scenarios involving multi-radio dual connectivity and handover procedures, where the communication of MBS data packets between the core network and base stations is not well-defined.
The implementation of common tunnels between the core network and base stations for MBS traffic, along with the use of multicast or unicast transmission methods based on tunnel configurations, quality of service (QoS) flow IDs, and logical channel mappings to efficiently manage MBS data packet distribution to UEs.
This approach enables effective and efficient management of MBS data transmission, ensuring that UEs receive MBS data packets via optimal multicast or unicast methods, enhancing network performance and resource utilization in 5G NR networks.
Smart Images

Figure 2024540957000001 
Figure 2024540957000002 
Figure 2024540957000003
Abstract
Description
[Technical field]
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to and the benefit of the filing date of U.S. Provisional Patent Application No. 63 / 257,794, entitled "Managing Multicast and Unicast Data Transmission for MBS," filed October 20, 2021, the disclosure of which is expressly incorporated herein by reference in its entirety.
[0002] The present disclosure relates to wireless communications, and more particularly, to enabling setup and / or modification of radio resources for multicast and / or broadcast communications. [Background technology]
[0003] The background description provided herein is intended to provide an overall context for the present disclosure. To the extent described in this Background section, the work of the inventors named herein, as well as aspects of the description that may not in some cases qualify as prior art at the time of filing, are not expressly or implicitly admitted as prior art to the present disclosure.
[0004] In a telecommunication system, the Packet Data Convergence Protocol (PDCP) sublayer of the radio protocol stack provides services such as the transfer, encryption, and integrity protection of user plane data. For example, the PDCP sublayer defined for the Evolved Universal Terrestrial Radio Access (EUTRA) air interface (see 3rd Generation Partnership Project (3GPP) specification TS 36.323) and New Radio (NR) (see 3GPP specification TS 38.323) provides ordering of protocol data units (PDUs) in the uplink direction from a user device (also known 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 for signaling radio bearers (SRBs) to the Radio Resource Control (RRC) sublayer. The PDCP sublayer further provides services for data radio bearers (DRBs) to the Service Data Adaptation Protocol (SDAP) sublayer or protocol layers such as the Internet Protocol (IP) layer, the Ethernet protocol layer, and the Internet Control Message Protocol (ICMP) layer. In general, a UE and a base station may exchange RRC messages as well as non-access stratum (NAS) messages using SRBs, and may transport data in the user plane using DRBs.
[0005] In some scenarios, a UE can simultaneously utilize resources of multiple nodes (e.g., base stations or components of distributed or separated base stations) of a Radio Access Network (RAN) that are interconnected by a backhaul. When these network nodes support different Radio Access Technologies (RATs), this type of connection is called Multi-Radio Dual Connectivity (MR-DC). When operating in MR-DC, cells associated with a base station operating as a Master Node (MN) define a Master Cell Group (MCG) and cells associated with a base station operating as a Secondary Node (SN) define a Secondary Cell Group (SCG). The MCG covers a Primary Cell (PCell) and zero, one, or more Secondary Cells (SCells), and the SCG covers a Primary Secondary Cell (PSCell) and zero, one, or more SCells. The UE communicates with the MN (through the MCG) and with the SN (through the SCG). In other scenarios, the UE utilizes resources of one base station at a time in Single Connectivity (SC). A UE in an SC only communicates with the MN via the MCG. The base station and / or the UE decide when the UE should establish a radio connection with another base station. For example, the base station may decide to handover the UE to another base station and initiate a handover procedure. In other scenarios, the UE may simultaneously utilize resources of another RAN node (e.g., a base station or a component of a distributed or separated base station) interconnected by a backhaul.
[0006] The UE can use several types of SRBs and DRBs. The so-called "SRB1" resources carry RRC messages, which in some cases include NAS messages on a dedicated control channel (DCCH), and "SRB2" resources support RRC messages including recorded 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 regarding the MN to embed RRC messages regarding the SN, and may be referred to as MCG SRBs. "SRB3" resources allow the UE and SN to exchange RRC messages regarding the SN, and may be referred to as SCG SRBs. Split SRBs allow the UE to exchange RRC messages directly with the MN via the MN and SN lower layer resources. Furthermore, a DRB that terminates in an MN and uses lower layer resources of only the MN can be referred to as an MCG DRB, a DRB that terminates in an SN and uses lower layer resources of only the SN can be referred to as an SCG DRB, and a DRB that terminates in an MN or an SN but uses lower layer resources of both the MN and the SN can be referred to as a split DRB. A DRB that terminates in an MN but uses lower layer resources of only the SN can be referred to as an MN-terminated SCG DRB. A DRB that terminates in an SN but uses lower layer resources of only the MN can be referred to as an SN-terminated MCG DRB.
[0007] The UE may perform handover procedures to switch from one cell to another cell, whether in SC or DC operation. These procedures involve messaging (e.g., RRC signaling and preparation) between the RAN node and the UE. Depending on the scenario, the UE may handover 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 the serving base station to a target cell of a second DU of the same base station. In a DC scenario, the UE may perform a PSCell exchange procedure to exchange a PSCell. These procedures involve messaging (e.g., RRC signaling and preparation) between the RAN node and the UE. Depending on the scenario, the UE may perform a PSCell change from a PSCell of a serving SN to a target PSCell of a target SN, or from a PSCell of a source DU of a base station to a PSCell of a target DU of the same base station. Additionally, the UE may perform a handover or a PSCell change within a cell for synchronous reconfiguration.
[0008] Base stations operating according to the requirements of the fifth generation (5G) New Radio (NR) support much wider bandwidths than fourth generation (4G) base stations. Thus, the Third Generation Partnership Project (3GPP) proposed in Release 15 that a user equipment unit (UE) should support a bandwidth of 100 MHz in Frequency Range 1 (FR1) and a bandwidth of 400 MHz in Frequency Range 2 (FR2). Since the bandwidth of a typical carrier in 5G NR is relatively wide, 3GPP proposed in Release 17 that a 5G NR base station should be able to provide multicast and / or broadcast services (MBS) to the UE. MBS can be useful in many content distribution applications, such as, for example, transparent IPv4 / IPv6 multicast distribution, IPTV, wireless software distribution, group communication, Internet of Things (IoT) applications, V2X applications, and emergency messages for public safety. Summary of the Invention [Problem to be solved by the invention]
[0009] 5G NR provides both point-to-point (PTP) and point-to-multipoint (PTM) delivery methods for the transmission of MBS packet flows over the air interface. In PTP communication, the RAN node transmits different copies of each MBS data packet to different UEs over the air interface. Meanwhile, in PTM communication, the RAN node transmits a single copy of each MBS data packet to multiple UEs over the air interface. However, in some scenarios, it is unclear how the base station receives the MBS data packets from the core network and how the base station transmits each MBS data packet to one or multiple UEs. [Means for solving the problem]
[0010] Using the techniques of this disclosure, a core network (CN) and a base station communicate MBS traffic for multiple UEs via a shared (or "common") tunnel between the CN and the base station. The base station may generate and provide a configuration for the common tunnel, such as an Internet Protocol (IP) address and / or a tunnel endpoint identifier (TEID), to the CN in response to a request for the configuration from the CN. More generally, the configuration may include transport layer information.
[0011] The CN and base station may also communicate MBS traffic from multiple MBS sessions via multiple common tunnels between the CN and base station. For example, the CN and base station may establish one CN-to-BS tunnel for multiple MBS sessions or may establish a separate CN-to-BS tunnel for each MBS session.
[0012] The base station may also establish a BS-to-UE transport with the UE. The base station may communicate MBS traffic from multiple MBS sessions to the same UE using the same MBS radio bearer (MRB) associated with the MBS session. Alternatively, the base station may communicate MBS traffic from each MBS session to the UE using a different MRB. More specifically, the base station maps the traffic in the tunnel to a radio bearer that may be configured as an MRB. Each of the MRBs may correspond to a respective MBS traffic channel (MTCH). In some scenarios, the base station communicates MBS traffic for the MBS session via a single MRB and corresponding MTCH to all of the UEs that have joined the MBS session. In other scenarios, the base station communicates MBS traffic for the MBS session via a DRB that corresponds to a dedicated traffic channel (DTCH), with each DTCH being used to communicate MBS traffic with a particular one of the UEs that have joined the MBS session.
[0013] The base station may determine whether to transmit the MBS data packet to the UE via unicast or via multicast. For example, the base station may transmit the MBS data packet to a first set of UEs via multicast and to a second set of UEs via unicast. In some implementations, the base station may determine whether to transmit the MBS data packet to the UE via unicast or via multicast based on the tunnel from which the MBS data packet was received. The base station may store a mapping of each tunnel to a set of UEs to receive the MBS data packet via multicast (e.g., as indicated by a G-RNTI), a set of UEs to receive the MBS data packet via unicast (e.g., as indicated by a C-RNTI), individual legacy UEs to receive the MBS data packet via unicast (e.g., as indicated by a C-RNTI), a logical channel ID corresponding to the tunnel, an MRB for the tunnel, a DRB for the tunnel, etc.
[0014] An exemplary embodiment of these techniques is a method in a base station for managing multicast and unicast data transmission. The method includes receiving, by processing hardware, a multicast and / or broadcast service (MBS) downlink data packet from a core network (CN) via a downlink tunnel, and determining, by the processing hardware, whether to transmit the MBS downlink data packet to a plurality of UEs via unicast or via multicast. The method further includes at least one of transmitting, by the processing hardware, the MBS downlink data packet to a plurality of first UEs via a multicast data transmission, or transmitting, by the processing hardware, the MBS downlink data packet to a plurality of second UEs via a plurality of unicast data transmissions.
[0015] Another exemplary embodiment of these techniques is a method in a base station for managing transmission of MBS. The method includes receiving, by the processing hardware, from a UE a first request to join a first MBS session identified by a first MBS session identifier, and receiving, by the processing hardware, from the UE a second request to join a second MBS session identified by a second MBS session identifier. In addition, the method includes transmitting, by the processing hardware to the UE, first MBS data for the first MBS session, and transmitting, by the processing hardware to the UE, second MBS data for the second MBS session during the first MBS session.
[0016] Yet another exemplary embodiment of these techniques is a base station including processing hardware and configured to implement one of the above methods.
[0017] Another example embodiment of these techniques is a method in a UE for obtaining multicast and / or broadcast service (MBS) data from multiple MBS sessions. The method includes transmitting, by processing hardware to a base station, a first request to join a first MBS session identified by a first MBS session identifier, and transmitting, by processing hardware to the base station, a second request to join a second MBS session identified by a second MBS session identifier. In addition, the method includes receiving, by the processing hardware from the base station, first MBS data for the first MBS session, and receiving, by the processing hardware from the base station, second MBS data for the second MBS session during the first MBS session.
[0018] Yet another example embodiment of these techniques is a UE that includes processing hardware and is configured to perform the above methods. [Brief description of the drawings]
[0019] [Figure 1A] 1 is a block diagram of an example system in which the techniques of the present disclosure for managing multicast and unicast data transmission for MBS are disclosed. [Figure 1B] FIG. 1B is a block diagram of an exemplary base station in which the centralized unit (CU) and distributed unit (DU) can operate in the system of FIG. 1A. [Diagram 2] 1B is a block diagram of an example protocol stack according to which the UE of FIG. 1A can communicate with the base station of FIG. 1A. [Diagram 3] FIG. 1 is a block diagram illustrating an example tunnel architecture for MBS and PDU sessions. [Figure 4] FIG. 2 is a block diagram illustrating an example tunnel architecture for an MRB and a DRB. [Figure 5A] FIG. 1 is a messaging diagram of an example scenario in which a CN and a base station establish a first common downlink (DL) tunnel for a first UE to a base station through which the CN can transmit MBS data of a first MBS session, and establish a second common DL tunnel for a second UE to a base station through which the CN can transmit MBS data of a second MBS session. [Figure 5B] FIG. 11 is a messaging diagram of an example scenario in which a UE participates in first and second MBS sessions, and the CN and base station establish, for the UE, separate first and second common DL tunnels to the base station through which the CN can transmit MBS data for the first and second MBS sessions. [Figure 6] 1A is a flow diagram of an example method for identifying a UE for transmitting an MBS data packet via multicast and / or identifying a UE for transmitting an MBS data packet via unicast based on a tunnel through which the data packet was received, which may be implemented in the base station of FIG. 1A and / or the DU of FIG. 1B. [Figure 7]1B is a flow diagram of an example method for determining which logical channel to use to transmit an MBS data packet to a UE based on the tunnel through which the data packet was received, which may be implemented in the base station of FIG. 1A and / or the DU of FIG. 1B. [Figure 8] 1B is a flow diagram of an example method for determining which logical channel to use to transmit an MBS data packet to each UE based on the tunnel through which the data packet was received, which may be implemented in the base station of FIG. 1A and / or the DU of FIG. 1B. [Figure 9] 1A and / or DU of FIG. 1B, for determining which logical channel to use and which G-RNTI to use when scrambling a cyclic redundancy check (CRC) of a downlink control information element (DCI) for transmitting an MBS data packet to a UE based on the tunnel through which the data packet was received. [Figure 10A] 1B is a flow chart of an example method for determining which logical channel to use and whether to use N C-RNTIs to scramble N CRCs of N DCIs for transmitting a protocol data unit (PDU) including an MBS data packet to a UE based on a tunnel through which the data packet was received, which may be implemented in the base station of FIG. 1A and / or the DU of FIG. 1B. [Figure 10B] 1B is a flow chart of an example method for determining which logical channel to use and whether to use N C-RNTIs to scramble N CRCs of N DCIs for transmitting N PDUs including an MBS data packet to a UE based on a tunnel through which the data packet was received, which may be implemented in the base station of FIG. 1A and / or the DU of FIG. 1B. [Figure 10C]1B is a flow chart of an example method for determining which logical channel to use and whether to use N C-RNTIs to scramble the same CRC of the same DCI for transmitting a PDU including an MBS data packet to a UE based on the tunnel through which the data packet was received, which may be implemented in the base station of FIG. 1A and / or the DU of FIG. 1B. [Figure 11A] 10A is a flow diagram of another example method similar to the example method shown in FIG. 10A that may be implemented in the base station of FIG. 1A and / or the DU of FIG. 1B. [Figure 11B] 1B is a flow diagram of another example method similar to the example method shown in FIG. 10B that may be implemented in the base station of FIG. 1A and / or the DU of FIG. 1B. [Figure 11C] 10C is a flow diagram of another example method similar to the example method shown in FIG. 10C that may be implemented in the base station of FIG. 1A and / or the DU of FIG. 1B. [Figure 12] 1B is a flow chart of an example method for determining which logical channel to use and whether to use a C-RNTI to scramble the CRC of a DCI for transmitting an MBS data packet to a particular UE based on the tunnel through which the data packet was received, which may be implemented in the base station of FIG. 1A and / or the DU of FIG. 1B. [Figure 13A] 1A is a flow diagram of an example method for determining which logical channel to use and whether to transmit an MBS data packet via unicast or multicast based on an MBS Quality of Service (QoS) flow ID associated with the MBS data packet, which may be implemented in the base station of FIG. 1A and / or the DU of FIG. 1B. [Figure 13B] 1A and / or 1B, a flow diagram of an example method for determining which logical channel to use to transmit an MBS data packet to a UE via unicast based on an MBS Quality of Service (QoS) flow ID associated with the MBS data packet. [Figure 14A]1A and / or the DU of FIG. 1B, similar to the method shown in FIG. 13A, is a flowchart of another exemplary method for determining which logical channel to use and whether to transmit an MBS data packet via unicast or multicast based on an MBS Quality of Service (QoS) flow ID associated with the MBS data packet. [Figure 14B] 1A and / or the DU of FIG. 1B, similar to the method shown in FIG. 13B, is a flow diagram of another exemplary method for determining which logical channel to use to transmit an MBS data packet to a UE via unicast based on an MBS Quality of Service (QoS) flow ID associated with the MBS data packet. [Figure 15] 1A and / or 1B, based on specific transport layer information related to an MBS data packet, configure a DL transport layer configuration, identify UEs for receiving the MBS data packet via multicast, and / or identify UEs for receiving the MBS data packet via unicast. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0020] In general, the RAN and / or CN implement the techniques of this disclosure to manage multicast and unicast data transmission. The base station can determine whether to transmit MBS data packets to UEs via unicast or multicast. For example, the base station can transmit MBS data packets to a first set of UEs via multicast and to a second set of UEs via unicast.
[0021] In some implementations, the base station may determine whether to transmit the MBS data packet to the UE via unicast or via multicast according to an MBS quality of service (QoS) flow associated with the MBS data packet. For example, if the QoS flow ID associated with the MBS data packet is a first QoS flow ID, the base station may transmit the MBS data packet to the UE via multicast. Otherwise, if the QoS flow ID associated with the MBS data packet is a second QoS flow ID, the base station may transmit the MBS data packet to the UE via unicast. In other implementations, the base station may determine a logical channel ID for the MBS data packet based on the QoS flow. For example, the base station may identify or select a first logical channel ID if the QoS flow ID associated with the MBS data packet is a first QoS flow ID, or a second logical channel ID if the QoS flow ID associated with the MBS data packet is a second QoS flow ID.
[0022] Also, in some embodiments, the base station may configure a DL transport layer configuration corresponding to a common DL tunnel for receiving MBS data packets from the CN. When the MBS data packets are received at the base station, for example, from the CN, the base station may identify transport layer information included in the DL tunnel packet that includes the MBS data packets. The base station may then identify the tunnel from which the MBS data packets were received based on the transport layer information. For example, the transport layer information may include a transport layer address, such as an IP address or a TEID.
[0023] FIG. 1A illustrates an example wireless communication system 100 in which techniques of the present disclosure 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-103C of a radio access network (RAN) 105 connected to a core network (CN) 110, as well as base stations 104, 106. In other implementations or scenarios, the wireless communication system 100 may instead include more or fewer UEs and / or more or fewer base stations than shown in FIG. 1A. The base stations 104, 106 may be any suitable type or types of base stations, such as, for example, an evolved node B (eNB), a next generation eNB (ng-eNB), or a 5G Node B (gNB). As a more specific example, the base station 104 may be an eNB or a gNB, and the base station 106 may be a gNB.
[0024] The base station 104 supports a cell 124, and the base station 106 supports a cell 126. Because the cell 124 overlaps with the cell 126, the UE 102A can be in communication range with the base station 104 while simultaneously being in communication range with the base station 106 (or in range to detect or measure a signal from the base station 106). This overlap can enable the UE 102A to handover between cells (e.g., from the cell 124 to the cell 126) or between base stations (e.g., from the base station 104 to the base station 106) before the UE 102A experiences a radio link failure, for example. Moreover, this overlap enables various dual connectivity (DC) scenarios. For example, the UE 102A can communicate in DC with the base station 104 (acting as a master node (MN)) and the base station 106 (acting as a secondary node (SN)). When the UE 102A is in a DC state with the base station 104 and the base station 106, the base station 104 operates as a master eNB (MeNB), a master ng-eNB (Mng-eNB), or a master gNB (MgNB), and the base station 106 operates as a secondary gNB (SgNB) or a secondary ng-eNB (Sng-eNB).
[0025] In non-MBS (unicast) operation, the UE 102A may use a radio bearer (e.g., DRB or SRB) that terminates at a MN (e.g., base station 104) or a SN (e.g., base station 106) at different times. For example, after a handover or SN change to the base station 106, the UE 102A may use a radio bearer (e.g., DRB or SRB) that terminates at the base station 106. The UE 102A may apply one or more security keys in the uplink (UE 102A to base station) and / or downlink (base station to UE 102A) directions when communicating on a radio bearer. In non-MBS operation, the UE 102A transmits data to a base station via a radio bearer of (i.e., in) the uplink (UL) bandwidth portion (BWP) of the cell and / or receives data from the base station via a radio bearer on the downlink (DL) BWP of the 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. The UE 102A may receive paging, system information, public alert messages, or random access responses on the DL BWP. In this non-MBS operation, the UE 102A may be in a connected state. Alternatively, the UE 102A may be in an idle or inactive state if the UE 102A supports small amounts of data transmission in the idle or inactive state.
[0026] In MBS operation, the UE 102A may use an MBS radio bearer (e.g., MRB) that terminates at a MN (e.g., base station 104) or an SN (e.g., base station 106) at different times. For example, after a handover or SN change, the UE 102A may use an MRB that terminates at the base station 106, which may be operating as an MN or an SN. In some scenarios, the base station (e.g., MN or SN) may transmit MBS data to the UE 102A via the MRB on unicast radio resources (i.e., radio resources dedicated to the UE 102A). In other scenarios, the base station (e.g., MN or SN) may transmit MBS data from the base station to the UE 102A via the MRB on multicast radio resources (i.e., radio resources common to the UE 102A and one or more other UEs) or on the DL BWP of the cell. The DL BWP may be an initial DL BWP, a dedicated DL BWP, or an MBS DL BWP (i.e., a DL BWP specific to the MBS or not for unicast).
[0027] The 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 that stores machine-readable instructions executable on the one or more general-purpose processors, and / or special-purpose processing units. The processing hardware 130 in the example implementation of FIG. 1A includes an MBS controller 132 configured to manage or control transmission of MBS information received from the CN 110 or edge server. For example, as discussed below, the MBS controller 132 may be configured to support radio resource control (RRC) configurations, procedures and messaging related to MBS procedures, and / or other operations related to those configurations and / or procedures. The processing hardware 130 may also include a non-MBS controller 134 configured to manage or control one or more RRC configurations and / or RRC procedures when the base station 104 operates as a MN or SN during non-MBS operation.
[0028] The base station 106 includes processing hardware 140, which may include one or more general-purpose processors (e.g., CPUs) and computer-readable memory that stores machine-readable instructions executable on the general-purpose processors, and / or special-purpose processing units. The processing hardware 140 in the example implementation of FIG. 1A includes an MBS controller 142 and a non-MBS controller 144, which may be similar to the controllers 132 and 134, respectively, of the base station 130. Although not shown in FIG. 1A, the RAN 105 may include additional base stations with processing hardware similar to the processing hardware 130 of the base station 104 and / or the processing hardware 140 of the base station 106.
[0029] The UE 102A includes processing hardware 150, which may include one or more general-purpose processors (e.g., CPUs) and computer-readable memory that stores machine-readable instructions executable on the general-purpose processors, and / or dedicated processing devices. The processing hardware 150 in the example implementation of FIG. 1A includes an MBS controller 152 configured to manage or control reception of MBS information. For example, as discussed below, the UE MBS controller 152 may be configured to support RRC configurations, procedures and messaging related to MBS procedures, and / or other operations related to those configurations and / or procedures. The processing hardware 150 may also include a non-MBS controller 154 configured to manage or control one or more RRC configurations and / or RRC procedures according to any of the implementations discussed below when the UE 102A communicates with the MN and / or SN during non-MBS operation. Although not shown in FIG. 1A, the UEs 102B-103C may include processing hardware similar to the processing hardware 150 of the UE 102A.
[0030] The CN 110 may be an evolved packet core (EPC) 111 or a fifth generation core (5GC) 160, both of which are shown in FIG. 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 that does not connect 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. The base stations 104 and 106 may support an X2 interface or an Xn interface to directly exchange messages with each other during the scenarios discussed below.
[0031] Among other components, the EPC 111 may include a Serving Gateway (SGW) 112, a Mobility Management Entity (MME) 114, and a Packet Data Network Gateway (PGW) 116. The SGW 112 is generally configured to forward user plane packets related to voice calls, video calls, Internet traffic, etc., and the MME 114 is configured to manage authentication, registration, paging, and other related functions. The PGW 116 provides connectivity from the 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. The 5GC 160 includes a User Plane Function (UPF) 162 and an Access Mobility Management (AMF) 164, and / or a Session Management Function (SMF) 166. The UPF 162 is generally configured to forward user plane packets related to voice calls, video calls, Internet traffic, etc., the AMF 164 is generally configured to manage authentication, registration, paging, and other related functions, and the SMF 166 is generally configured to manage PDU sessions.
[0032] The UPF 162, the AMF 164, and / or the SMF 166 may be configured to support MBS. For example, the SMF 166 may be configured to manage or control MBS transport, configure the UPF 162 and / or the RAN 105 for MBS flows, and / or manage or configure one or more MBS or PDU sessions for MBS for a UE (e.g., UE 102A or 102B). The UPF 162 is configured to forward MBS data packets to the RAN 105 for audio, video, Internet traffic, etc. The UPF 162 and / or the SMF 166 may be configured for both non-MBS unicast services and MBS, or for MBS only.
[0033] In general, the wireless communication system 100 may include any suitable number of base stations supporting NR and / or EUTRA cells. More specifically, the EPC 111 or 5GC 160 may be connected to any suitable number of base stations supporting NR and / or EUTRA cells. Although the following examples refer specifically to particular CN types (EPC, 5GC) and RAT types (5G NR and EUTRA), in general, the techniques of this disclosure may also apply 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.
[0034] In different configurations or scenarios of the wireless communication system 100, the base station 104 may operate as an MeNB, an Mng-eNB, or an MgNB, and the base station 106 may operate as an SgNB or an Sng-eNB. The UE 102A may communicate with the base stations 104 and 106 via the same radio access technology (RAT), such as EUTRA or NR, or via a different RAT.
[0035] When the base station 104 is an MeNB and the base station 106 is an SgNB, the UE 102A may be in an EN-DC state with the MeNB 104 and the SgNB 106. When the base station 104 is an Mng-eNB and the base station 106 is an SgNB, the UE 102A may be in a Next Generation (NG) EUTRA-NR DC (NGEN-DC) state with the Mng-eNB 104 and the SgNB 106. When the base station 104 is an MgNB and the base station 106 is an SgNB, the UE 102A may be in an NR-NR DC (NR-DC) state with the MgNB 104 and the SgNB 106. When the base station 104 is an MgNB and the base station 106 is an SgNB, the UE 102A may be in an NR-EUTRA DC (NE-DC) state with the MgNB 104 and the Sng-eNB 106.
[0036] 1B illustrates any one or more exemplary distributed implementations of the base stations 104 and 106. In this implementation, the base stations 104, 106 include a central unit (CU) 172 and one or more distributed units (DUs) 174. The CU 172 includes processing hardware, such as one or more general-purpose processors (e.g., CPUs) and computer-readable memory that stores machine-readable instructions executable on the general-purpose processors, and / or dedicated processing units. For example, the CU 172 may include some or all of the processing hardware 130 or 140 of FIG. 1A.
[0037] 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 that stores 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 Medium Access Control (MAC) controller configured to manage or control one or more MAC operations or procedures (e.g., random access procedures) and a Radio Link Control (RLC) controller configured to manage or control one or more RLC operations or procedures when the base station (e.g., base station 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 procedures.
[0038] In some implementations, the CU 172 may include one or more logical nodes (CU-CP 172A) that host a control plane portion of the Packet Data Convergence Protocol (PDCP) protocol of the CU 172 and / or a Radio Resource Control (RRC) protocol of the CU 172. The CU 172 may also include one or more logical nodes (CU-UP 172B) that host a user plane portion of the PDCP protocol and / or a Service Data Adaptation Protocol (SDAP) protocol of the CU 172. As described herein, the CU-CP 172A may transmit non-MBS control information and MBS control information, and the CU-UP 172B may transmit non-MBS data packets and MBS data packets.
[0039] The CU-CP 172A may be connected to multiple CU-UPs 172B through an E1 interface. The CU-CP 172A selects an appropriate CU-UP 172B for a requested service for the UE 102A. In some implementations, a single CU-UP 172B may be connected to multiple CU-CPs 172A through an E1 interface. The CU-CP 172A may be connected to one or more DUs 174 through an F1-C interface. The CU-UP 172B may be connected to one or more DUs 174 through an F1-U interface under the control of the same CU-CP 172A. In some embodiments, 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 the CU-UP 172B and the DU 174 is established by the CU-CP 172A using a bearer context management function.
[0040] 2 illustrates, in a simplified manner, an exemplary protocol stack 200 according to which a UE (e.g., UE 102A or 102B) may communicate with an eNB / ng-eNB or gNB (e.g., one or more of base stations 104, 106). In the exemplary 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 then 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 then provides RLC channels to the NR PDCP sublayer 210. In some implementations, the UE 102A supports both EUTRA and NR stacks as shown in Figure 2 to support handover between EUTRA and NR base stations and / or to support DC on EUTRA and NR interfaces. Additionally, as shown in Figure 2, the UE 102A can support layering of NR PDCP 210 over EUTRA RLC 206A and SDAP sublayer 212 over the NR PDCP sublayer 210. In this specification, the sublayers are also referred to simply as "layers."
[0041] 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). Except where the distinction between SDUs and PDUs is important, this disclosure refers to both SDUs and PDUs as "packets" for brevity. Packets may be MBS packets or non-MBS packets. MBS packets may include, for example, application content for MBS services (e.g., IPv4 / IPv6 multicast distribution, IPTV, wireless software distribution, group communication, IoT applications, V2X applications, and / or public safety emergency messages). As another example, MBS packets may include application control information for MBS services.
[0042] On the control plane, the EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 can provide SRBs, for example, 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 can provide DRBs to support data exchange. The data exchanged on the NR PDCP sublayer 210 can be, for example, SDAP PDUs, IP packets, or Ethernet packets.
[0043] In a scenario where the UE 102A or 102B operates in an EN-DC with the base station 104 acting as an MeNB and the base station 106 acting as an SgNB, the wireless communication system 100 may provide the UE 102A or 102B with an MN terminated bearer using the EUTRA PDCP sublayer 208 or an MN terminated bearer using the NR PDCP sublayer 210. In various scenarios, the wireless communication system 100 may also provide the UE 102A or 102B with an SN terminated bearer using only the NR PDCP sublayer 210. The MN terminated bearer may be an MCG bearer, a split bearer, or an MN terminated SCG bearer. The SN terminated bearer may be an SCG bearer, a split bearer, or an SN terminated MCG bearer. The MN terminated bearer may be an SRB (e.g., SRB1 or SRB2) or a DRB. The SN terminated bearer may be an SRB or a DRB.
[0044] In some implementations, a base station (e.g., base station 104, 106) broadcasts MRB data packets via one or more MBS radio bearers (MRBs), and the UE 102A receives the MBS data packets via the MRBs. The base station may include a configuration of the MRB in a multicast configuration parameter (which may also be referred to as an MBS configuration parameter) 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 correspondingly, the UE 102A uses the PHY sublayer 202, the MAC sublayer 204, and the RLC sublayer 206 to receive the MBS data packets. In such implementations, the base station and the UE 102A may not use the PDCP sublayer 208 and the SDAP sublayer 212 to communicate 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 correspondingly, the UE 102A uses the PHY sublayer 202, the MAC sublayer 204, the RLC sublayer 206, and the PDCP sublayer 208 to receive the MBS data packets. In such implementations, the base station and the UE 102A may not use the SDAP sublayer 212 to communicate the MBS data packets. In yet another implementation, the base station transmits 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 correspondingly, the UE 102A uses the PHY sublayer 202, the MAC sublayer 204, the RLC sublayer 206, the PDCO sublayer 208, and the SDAP sublayer 212 to receive the MBS data packets.
[0045] 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 ID, such as, for example, a Temporary Mobile Group Identity (TMGI). The MBS data may include, for example, IP packets, TCP / IP packets, UDP / IP packets, Real-time Transport Protocol (RTP) / UDP / IP packets, or RTP / TCP / IP packets.
[0046] In some cases, the CN 110 and / or the base station 104 / 106 configure the tunnel 312A for only MBS traffic directed from the CN 110 to the base station 104 / 106, and the tunnel 312A may be referred to as a downlink (DL) tunnel. However, in other cases, the CN 110 and the base station 104 / 106 use the tunnel 312A for downlink as well as uplink (UL) MBS traffic, for example, to support a command or service request from a UE. Furthermore, the tunnel 312A may be referred to as a common tunnel or a common DL tunnel, because the base station 104 / 106 can direct MBS traffic arriving via the tunnel 312A to multiple UEs.
[0047] The tunnel 312A may operate at a transport layer or sublayer, for example, in a User Datagram Protocol (UDP) protocol layered over the Internet Protocol (IP). As a more specific example, the tunnel 312A may be associated with a General Packet Radio Service (GPRS) Tunneling Protocol (GTP). The tunnel 312A may correspond, for example, to an IP address (e.g., an IP address of the base station 104 / 106) and a Tunnel Endpoint Identifier (TEID) (e.g., assigned by the base station 104 / 106). More generally, the tunnel 312A may have any suitable transport layer configuration. The CN 110 may specify the IP address and the TEID address in a header of a tunnel packet including the MBS data packet and transmit the tunnel packet downstream to the base station 104 / 106 through the tunnel 312A. The header may include the IP address and / or the TEID. For example, the header includes an IP header and a GTP header including the IP address and the TEID, respectively. Thus, the base stations 104 / 106 can use the IP address and / or the TEID to identify data packets traveling through the tunnel 312A.
[0048] As shown in FIG. 3, the base station 104 / 106 maps the traffic in the tunnel 312A to N radio bearers 314A-1, 314A-2, ..., 314A-N, which may be configured as MBS radio bearers or MRBs, where N >= 1. Each MRB may correspond to a respective logical channel. As discussed above, the PDCP sublayer supports 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 may correspond to a respective MBS traffic channel (MTCH). The base station 104 / 106 and the CN 110 may also maintain another MBS session 302B, which may similarly include a tunnel 312B corresponding to MRBs 314B-1, 314B-2, ..., 314B-N, where N >= 1. Each of the MRBs 314B may correspond to a respective logical channel.
[0049] The MBS traffic may include one or more quality of service (QoS) flows for each of the tunnels 312A, 312B, etc. For example, the MBS traffic on the tunnel 312B may include a set of flows 316 including QoS flows 316A, 316B, ... 316L. Furthermore, the logical channel of an MRB may support a single QoS flow or multiple QoS flows. In the example configuration of FIG. 3, the base station 104 / 106 maps the QoS flows 316A and 316B to the MTCH of the MRB 314B-1 and the QoS flow 316L to the MTCH of the MRB 314B-N.
[0050] In various scenarios, the CN 110 can assign different types of MBS traffic to different QoS flows. For example, a flow with a relatively high QoS value may correspond to audio packets, and a flow with a relatively low QoS value may correspond to video packets. As another example, a flow with a relatively high QoS value may correspond to an I-frame or a complete image used in video compression, and a flow with a relatively low QoS value may correspond to a P-frame or a predicted picture that contains only changes to the I-frame.
[0051] Continuing with reference to Figure 3, the base stations 104 / 106 and the CN 110 may maintain one or more PDU sessions to support unicast traffic between the CN 110 and a particular 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 respective logical channel, such as a dedicated traffic channel (DTCH).
[0052] Now referring to FIG. 4, when the base stations 104 / 106 are implemented in a distributed manner, the CU 172 and the DU 174A / 174B can establish tunnels for downlink and / or uplink data related to the MRB or DRB. The MRB 314A-1 discussed above can be implemented as the MRB 402A connecting the CU 172 to multiple UEs, such as the UE 102A and the UE 102B. The MRB 402A can include a DL tunnel 412A connecting the CU 172 and the DU 174A / 174B, and a DL logical channel 422A corresponding to the DL tunnel 412A. In particular, the DU 174A / 174B can map downlink traffic received via the DL tunnel 412A to the DL logical channel 422A, which can be, for example, an MTCH or a DTCH. The DL tunnel 412A can be a common DL tunnel through which the CU 172 transmits MBS data packets to multiple UEs. Alternatively, the DL tunnel 412A may be a UE-specific DL tunnel through which the CU 172 transmits MBS data packets to a particular UE.
[0053] Optionally, the MRB 402A 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 DTCH. The DU 174A / 174B can map uplink traffic received via the UL logical channel 423A to the UL tunnel 413A.
[0054] The tunnels 412A and 413A may operate at the transport layer or sublayer of the F1-U interface. As a more specific example, the CU 172 and DU 174A / 174B may utilize the F1-U for user plane traffic, and the tunnels 412A and 413A may be associated with a GTP-U protocol layered over UDP / IP, with IP layered over the appropriate data link and physical (PHY) layer. Furthermore, the MRB 402 and / or DRB 404 additionally support control plane traffic, at least in some cases. More specifically, the CU 172 and DU 174A / 174B may exchange F1-AP messages over the F1-C interface that relies on the Stream Control Transmission Protocol (SCTP) layered over IP, with IP layered over the appropriate data link and PHY layer, similar to the F1-U.
[0055] Similarly, the MRB 402B may include a DL tunnel 412B and, optionally, a UL tunnel 413B. The DL tunnel 412B may correspond to a DL logical channel 422B, and the UL tunnel 413B may correspond to a UL logical channel 423B.
[0056] In some cases, the CU 172 uses the DRB 404A to transmit MBS data packets or unicast data packets related to a PDU session to a specific UE (e.g., UE 102A or UE 102B). The DRB 404A may include a UE-specific DL tunnel 432A connecting the CU 172 and the DU 174A / 174B, and a DL logical channel 442A corresponding to the DL tunnel 432A. In particular, the DU 174A / 174B may map downlink traffic received via the DL tunnel 432A to the DL logical channel 442A, which may be, for example, a DTCH. The DRB 404A further includes a UE-specific UL tunnel 433A connecting the CU 172 and the DU 174A / 174B, and a UL logical channel 443A corresponding to the UL tunnel 433A. For example, the UL logical channel 443A may be a PUSCH. The DU 174A / 174B can map uplink traffic received via the UL logical channel 443A to the UL tunnel 433A.
[0057] Similarly, the DRB 404B may include a UE-specific DL tunnel 432B corresponding to the DL logical channel 442B and a UE-specific UL tunnel 433B corresponding to the UL logical channel 443B.
[0058] Next, FIG. 5A illustrates an example scenario 500A in which the base station 104 configures a first common tunnel for MBS data in response to the CN requesting resources for a first MBS session and configures a second common tunnel for MBS data in response to the CN requesting resources for a second MBS session.
[0059] The UE 102 first performs an MBS session join procedure with the CN 110 via the base station 104 to join the first MBS session (502). In some scenarios, the UE 102 subsequently performs one or more additional MBS join procedures, such that event 502 is the first of multiple MBS join procedures. Because the base station 104 configures a common DL tunnel for MBS traffic rather than a UE-specific tunnel, as discussed below, procedures 502 and 590 can occur in either order. In other words, the base station 104 can configure a common DL tunnel even if there are no UEs yet to join the first MBS session.
[0060] To perform the MBS session join procedure, in some implementations, the UE 102 sends an MBS session join request message to the CN 110 via the base station 104. In response, the CN 110 can send an MBS session join response message to the UE 102 via the base station 104 to grant the UE 102 access to the first MBS session. In some implementations, the UE 102 can include a first MBS session ID for the first MBS session in the MBS session join request message. In some cases, the CN 110 includes the first MBS session ID in the MBS session join response message. In some implementations, the UE 102 can send an MBS session join complete message to the CN 110 via the base station 104 in response to the MBS session join response message.
[0061] In some cases, the UE 102 performs an additional MBS session join procedure with the CN 110 via the RAN 105 (e.g., the base station 104 or the base station 106) to join the additional MBS session. For example, the UE 102 can perform a second MBS session join procedure with the CN 110 via the RAN 105 to join the second MBS session. Similar to event 502, in some implementations, the UE 102 can send a second MBS session join request message to the CN 110 via the base station 104, and the CN 110 can respond with a second MBS session join response message to grant the UE 102 access to the second MBS session. In some implementations, the UE 102 can send a second MBS session join completion message to the CN 110 via the base station 104 in response to the second MBS session join response message. In some implementations, the UE 102 can include a second MBS session ID of the second MBS session in the second MBS session join request message. Optionally, the CN 110 includes the second MBS session ID in the second MBS session join response message. In some implementations, the UE 102 can include the first MBS session ID and the second MBS session ID in an MBS session join request message (e.g., the first MBS session join request message) to join the first MBS session and the second MBS session simultaneously. In such a case, the CN 110 can send an MBS session response message to admit either the first MBS session or the second MBS session, or both the first MBS session and the second MBS session.
[0062] In some implementations, the MBS session join request message, the MBS session join response message, and the MBS session join complete message may be a Session Initiation Protocol (SIP) message. In other implementations, the MBS session join request message, the MBS session join response message, and the MBS session join complete message may be a NAS message, such as a 5G Mobility Management (5GMM) message or a 5G Session Management message (5GSM). For a 5GSM message, the UE 102 may send a (first) UL container message including the MBS session join request message to the CN 110 via the base station 104, the CN 110 may send a DL container message including the MBS session join response message to the UE 102 via the base station 104, and the UE 102 may send a (second) UL container message including the MBS session join complete message to the CN 110 via the base station 104. These container messages may be 5GMM messages. In some implementations, the MBS session join request message, the MBS session join response message, and the MBS session join complete message may be a PDU Session Modification Request message, a PDU Session Modification Command message, and a PDU Session Modification Complete message, respectively. For simplicity of the following description, the MBS session join request message, the MBS session join response message, and / or the MBS session join complete message may represent container messages.
[0063] In some implementations, the UE 102 may perform a PDU session establishment procedure with the CN 110 via the base station 104 to perform a (first) MBS session join procedure and establish a PDU session. During the PDU session establishment procedure, the UE 102 may communicate a PDU session ID of the PDU session with the CN 110 via the base station 104.
[0064] Before, during, or after the first MBS session join procedure (event 502), the CN 110 may send a (first) CN-to-BS message including the first MBS session ID and / or PDU session ID to the CU 172 to request the CU 172 to configure resources for the first MBS session (504). The CN 110 may additionally include a quality of service (QoS) configuration for the first MBS session in the first CN-to-BS message. In response to receiving the first CN-to-BS message (504), the CU 172 sends a CU-to-DU message (e.g., an MBS context setup request message) to the DU 174 to request setup for an MBS context and / or a common DL tunnel for the first MBS session (506). The MBS context setup request message may include the first MBS session ID, the MRB ID, and the QoS configuration for the first MBS session.
[0065] In response to receiving the CU-to-DU message (506), the DU 174 sends a DU-to-CU message (e.g., an MBS context setup response message) including a first DL transport layer configuration to the CU to configure a common CU-to-DU DL tunnel (e.g., for an MRB identified by one of the MRB IDs) for the first MBS session (508). The DU 174 can include additional DL transport layer configurations in the DU-to-CU message to configure additional common CU-to-DU DL tunnels for additional MRBs identified by additional MRB IDs of the MRB IDs. In some implementations, the DU 174 can include MRB IDs associated with the first DL transport layer configuration and / or the additional DL transport layer configuration in the DU-to-CU message. In some implementations, the CU-to-DU message is a generic F1AP message or a dedicated F1AP message (e.g., an MBS context setup request message) specifically defined to carry this type of request. In some implementations, the DU-to-CU message of event 508 is a generic F1AP message or a dedicated F1AP message specifically defined for this purpose (e.g., an MBS context setup response message). The CN 110 may additionally include a quality of service (QoS) configuration for the first MBS session. In such a case, the CU 172 may include the QoS configuration in the CU-to-DU message (event 506).
[0066] The CU 172 may then send a first BS-to-CN message (e.g., an MBS Session Resource Setup Response message) including a DL transport layer configuration to configure the common DL tunnel (510). The CU 172 may include a first MBS Session ID and / or a PDU Session ID in the first BS-to-CN message. The first BS-to-CN message may include a DL transport layer configuration to configure a common DL tunnel for the CN 110 to transmit MBS data to the CU 172. The DL transport layer configuration includes a transport layer address (e.g., an IP address and / or a TEID) to identify the common DL tunnel.
[0067] In some implementations, the CN-to-BS message of event 504 may be a generic NGAP message or a dedicated NGAP message specifically defined to request resources for an MBS session (e.g., an MBS session resource setup request message). In some implementations, the BS-to-CN message of event 510 may be a generic NGAP message or a dedicated NGAP message specifically defined to carry resources for an MBS session (e.g., an MBS session resource setup response message). In such a case, the CN-to-BS message of event 504 and the BS-to-CN message of event 510 may be a non-UE specific message.
[0068] In some implementations, the QoS configuration includes QoS parameters for the first MBS session. In some implementations, the QoS configuration includes configuration parameters for configuring one or more QoS flows for the MBS session (see FIG. 3). In some implementations, the configuration parameters include one or more QoS flow IDs that identify the QoS flows. Each of the QoS flow IDs identifies a particular QoS flow of 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 duration, and / or a maximum data burst amount. The CN 110 can specify different values of the QoS parameters for the QoS flows.
[0069] Events 504, 506, 508, and 510 are collectively referred to as an MBS session resource setup procedure 586 in FIGS. 5A and 5B.
[0070] If the CN 110 admits an additional MBS session for the UE 102 in the additional MBS session join procedure, the CN 110 may include the additional MBS session ID and / or the QoS configuration for the additional MBS session ID in the first CN-to-BS message, the second CN-to-BS message, or the additional CN-to-BS message similar to the first or second CN-to-BS message. In such a case, the CU 172 includes the additional transport layer configuration for the additional MBS session to configure the additional common DL tunnel in the first BS-to-CN message, the second BS-to-CN message, or the additional BS-to-CN message similar to the first or second BS-to-CN message. Each of the transport layer configurations may configure a specific DL tunnel of the common DL tunnel and be associated with a specific MBS session of the additional MBS session. Alternatively, the CN 110 may perform an additional MBS session resource setup procedure with the CU 172 to obtain the additional transport layer configuration from the CU 172, similar to the single-session MBS session resource setup procedure 586. To distinguish different common DL tunnels, the transport layer configurations may be different. In particular, any pair of transport layer configurations may have different IP addresses, different DL TEIDs, or different IP addresses as well as different DL TEIDs.
[0071] In some implementations, the CN 110 may indicate in the CN-to-BS message of event 504 a list of UEs participating in the first MBS session. In other implementations, the CN 110 may send another second CN-to-BS message to the CU 172 indicating a list of UEs participating in the first MBS session (512). The CN 110 may include the first MBS session ID and / or PDU session ID in the second CN-to-BS message. The CU 172 may send a second BS-to-CN message to the CN 110 in response to the second CN-to-BS message 512 (519). In such a case, the second CN-to-BS message may be a non-UE specific message, i.e., a message that is not specific to the UE 102A or the UE 102B. The CU 172 may include the first MBS session ID and / or PDU session ID in the second BS-to-CN message. For example, the list of UEs includes the UE 102. To indicate the list of UEs, the CN 110 may include a list of (CN UE interface ID, RAN UE interface ID) pairs, each of which identifies a particular UE of the UE. The CN 110 assigns the CN UE interface ID, and the CU 172 assigns the RAN UE interface ID. Before the CN 110 sends the list of (CN UE interface ID, RAN UE interface ID) pairs, the CU 172 sends a BS-to-CN message (e.g., an NGAP message, an INITIAL UE message, or a PATH SWITCH REQUEST message) containing the RAN UE interface ID to the CN 110 for each of the UEs, and the CN 110 sends a CN-to-BS message (e.g., an NGAP message, an INITIAL CONTEXT SETUP REQUEST message, or a PATH SWITCH REQUEST ACKNOWLEDGE message) containing the CN UE interface ID to the CU 172 for each of the UEs. In one example, the list of pairs includes a first pair (first CN UE interface ID and first RAN UE interface ID) that identifies the UE 102.In some implementations, the "CN UE Interface ID" may be an "AMF UE NGAP ID" and the "RAN UE Interface ID" may be a "RAN UE NGAP ID". In other implementations, the CN 110 may include a list of UE IDs, each identifying a particular UE in the set of UEs. In some implementations, the CN 110 may assign the UE IDs and transmit each of the UE IDs to a particular UE of the UEs in a NAS procedure (e.g., a registration procedure) that the CN 110 performs with the particular UE. For example, the list of UE IDs may include a first UE ID of the UE 102A and a second UE ID of the UE 102B. In some implementations, the UE IDs are S-Temporary Mobile Subscriber Identities (S-TMSIs) (e.g., 5G-S-TMSI). Before the CN 110 transmits the list of UE IDs, the CU 172 may receive the UE IDs from the UE 102 or the CN 110 for each of the UEs. For example, the CU 172 may receive an RRC message (e.g., an RRC Setup Complete message) including the UE ID from the UE 102 during an RRC connection establishment procedure. In another example, the CU 172 may receive a CN-to-BS message (e.g., an NGAP message, an INITIAL CONTEXT SETUP REQUEST message, or a UE INFORMATION TRANSFER message) including the UE ID from the CN 110.
[0072] In other implementations, the CN 110 may send a second CN-to-BS message to the CU 172 indicating that the UE 102 (only) participates in the first MBS session (512). The second CN-to-BS message may be a UE-related message for the UE 102. That is, the second CN-to-BS message is specific to the UE 102. In response to receiving the second CN-to-BS message, the CU 172 may send a UE context request message for the UE 102 to the DU 174 (514). In some implementations, the CU 172 may include in the UE context request message the first MBS session ID and / or the MRB ID of the MRB associated with the first MBS session (ID). In response to the UE context request message, the DU 174 sends a UE context response message to the CU 172 including configuration parameters for the UE 102A to receive MBS data of the first MBS session (516). In some implementations, the CU 172 may include QoS configuration in the UE context request message. In such a case, the CU 172 may or may not include the QoS configuration in the CU-to-DU message. (Part of) the configuration parameters may be associated with the MRB / MRB ID. In some implementations, the DU 174 generates a DU configuration to include the configuration parameters and includes the DU configuration in the UE context response message. In some implementations, the DU configuration may be a CellGroupConfig IE. In other implementations, the DU configuration may be an MBS-specific IE. In some implementations, the configuration parameters configure one or more logical channels (LCs). For example, the configuration parameters include one or more logical channel IDs (LCIDs) for configuring one or more logical channels. Each of the LCIDs identifies a particular logical channel of the one or more logical channels.
[0073] In some implementations, the second CN-to-BS message and the second BS-to-CN message may be a PDU session resource modification request message and a PDU session resource modification response message, respectively. In some implementations, the second CN-to-BS message and the second BS-to-CN message may be UE-related messages, i.e., the messages are associated with a particular UE (e.g., UE 102A, 102B, or 102C).
[0074] Instead of the CN 110 sending a first CN-to-BS message to request the CU 172 to configure a common CN-to-BS DL tunnel (504), in some implementations the CU 172 may send a first BS-to-CN message (510) in response to receiving the second CN-to-BS message (512). The CN 110 may then send a CN-to-BS response message to the CU 172 in response to the first BS-to-CN message. In such a case, the CU 172 may send a CU-to-DU message to the DU 174 in response to receiving the second CN-to-BS message (506). In such a case, the first BS-to-CN message and the CN-to-BS response message may be non-UE-associated messages, i.e., the messages are associated with a particular UE.
[0075] Instead of the CU 172 sending a CU-to-DU message to request that a common CU-to-DU DL tunnel be configured (506), in some implementations, the DU 174 may send a DU-to-CU message in response to receiving the UE context request message (514) in addition to sending a UE context response message (516) (508). The CU 172 may then send a CU-to-DU response message to the DU 174 in response to the DU-to-CU message. In such a case, the DU-to-CU message and the CU-to-DU response message may be non-UE-associated messages, i.e., the messages are associated with a particular UE.
[0076] If the CN 110 admits an additional MBS session for the UE 102 in the additional MBS session join procedure, the CN 110 may include an additional MBS session ID and / or QoS configuration for the additional MBS session ID in the first CN-to-BS message or the second CN-to-BS message. In such a case, the CU 172 may include an additional MBS session ID and an additional MRB ID in the CU-to-DU message, and the DU 174 includes an additional DU transport layer configuration for configuring an additional CU-to-DU DL tunnel for the additional MBS session in the DU-to-CU message. Alternatively, the CU 172 may perform an additional MBS context setup procedure with the DU 174 to obtain the additional DU DL transport layer configuration, similar to events 506 and 508. In some implementations, the CU 172 includes an additional CU DL transport layer configuration for the additional MBS session in the first BS-to-CN message for configuring an additional CN-to-BS common DL tunnel. Each of the transport layer configurations may configure a specific DL tunnel of the common CN-to-BS DL tunnel and be associated with a specific MBS session of the additional MBS session. Alternatively, the CN 110 may perform additional MBS session resource setup procedures with the CU 172, similar to the MBS session resource setup procedure 586, to obtain additional CU DL transport layer configurations from the CU 172. The transport layer configurations may be different to distinguish between different common DL tunnels. In particular, any pair of transport layer configurations may have different IP addresses, different DL TEIDs, or different IP addresses as well as different DL TEIDs.
[0077] In some implementations, the CN 110 includes the QoS configuration in the second CN-to-BS message. In such a case, the CN 110 may include the QoS configuration in the first CN-to-BS message or may omit the QoS configuration. In some implementations, the DU 174 generates configuration parameters for the UE 102 to receive MBS data of the first MBS session in response to receiving the CU-to-DU message or the UE context request message. In some implementations, the CU 172 includes the QoS configuration in the UE context request message and / or the CU-to-DU message. The DU 174 can determine the content of the configuration parameters according to the QoS configuration. When the CU 172 does not include the QoS configuration in the CU-to-DU message or the UE context request message, the DU 174 can determine the value of the configuration parameter according to the predetermined QoS configuration.
[0078] In some implementations, the UE context request message and the UE context response message are UE Context Setup Request message and UE Context Setup Response message, respectively. In other implementations, the UE context request message and the UE context response message are UE Context Modification Request message and UE Context Modification Response message, respectively.
[0079] After receiving the UE context response message (516), the CU 172 generates an RRC reconfiguration message including the configuration parameters and one or more MRB configurations and sends the RRC reconfiguration message to the DU 174 (518). The DU 174 then sends an RRC reconfiguration message to the UE 102 (520). The UE 102 then sends an RRC reconfiguration complete message to the DU 174 (522), and the DU 174 sends an RRC reconfiguration complete message to the CU 172 (523). Events 512, 514, 516, 518, 519, 520, 522, and 523 are collectively referred to as a UE-specific MBS session configuration procedure 590 in Figures 5A and 5B.
[0080] In some implementations, the CU 172 generates a PDCP PDU including the RRC reconfiguration message and transmits a CU-to-DU message including the PDCP PDU to the DU 174 (518), and the DU 174 extracts the PDCP PDU from the CU-to-DU message and transmits the PDCP PDU to the UE 102 via the RLC layer 206B, the MAC layer 204B, and the PHY layer 202B (520). The UE 102 receives the PDCP PDU from the DU 174 via the PHY layer 202B, the MAC layer 204B, and the RLC layer 206B (520). In some implementations, the UE 102 generates a PDCP PDU including the RRC reconfiguration complete message and transmits the PDCP PDU to the DU 174 via the RLC layer 206B, the MAC layer 204B, and the PHY layer 202B (522). The DU 174 receives PDCP PDUs from the UE 102 via the PHY layer 202B, the MAC layer 204B, and the RLC layer 206B (522) and transmits a DU-to-CU message including the PDCP PDU to the CU 172 (523). The CU 172 extracts the PDCP PDUs from the DU-to-CU message and extracts the RRC reconfiguration complete message from the PDCP PDU.
[0081] Before or after receiving the UE context response message (516), the CU 172 may send the second BS to CN message to the CN 110 in response to the second CN to BS message 512 (519). In some implementations, the CU 172 sends the second BS to CN message to the CN 110 (519) before receiving the RRC reconfiguration complete message (523). In other implementations, the CN 110 sends the second BS to CN message to the CN 110 (519) after receiving the RRC reconfiguration complete message (523). The CU 172 may include the first CN UE interface ID and the first RAN UE interface ID in the second BS to CN message. Alternatively, the CU 172 may include the first UE ID in the second BS to CN message.
[0082] In some implementations, the CU 172 includes the CU DL transport layer configuration in the second BS-to-CN message and / or the additional BS-to-CN message. In other words, the CU 172 can send the same CU DL transport layer configuration in the BS-to-CN message in response to the CN-to-BS message indicating that the UE will participate in the same MBS session. In such implementations, the CN 110 can blend the MBS resource setup procedure 586 and the second CN-to-BS message and the BS-to-CN message into a single procedure.
[0083] If the CU 172 performs an MBS resource setup procedure 586 (e.g., events 504, 510) with the CN 110 to establish a common CN-to-BS DL tunnel for the first MBS session, the CU 172 may refrain from including a DL transport layer configuration for the first MBS session in the second BS-to-CN message. In such a case, the CN 110 may refrain from including a UL transport layer configuration for the first MBS session in the second CN-to-BS message. If the DU 174 performs an MBS resource setup procedure (e.g., events 506, 508) with the CU 172 to establish a common CU-to-DU DL tunnel for the first MBS session, the DU 174 may refrain from including a DL transport layer configuration for the first MBS session in the UE context response message. In such a case, the CU 172 may refrain from including a UL transport layer configuration for the first MBS session in the UE context request message.
[0084] After receiving the first BS-to-CN message (510) or after receiving the second BS-to-CN message (519), the CN 110 can transmit MBS data (e.g., one or more MBS data packets) for the first MBS session to the CU 172 via the common CN-to-BS DL tunnel (524), and the CU 172 transmits the MBS data to the DU 174 via the common CU-to-DU tunnel (526). The DU 174 transmits (e.g., multicast or unicast) the MBS data to the UE 102 via one or more logical channels (528). The UE 102 receives the MBS data via one or more logical channels (528). For example, the CU 172 receives the MBS data packet (524), generates a PDCP PDU including the MBS data packet, and transmits the PDCP PDU to the DU 174 (528). The DU 174 then generates a MAC PDU including the logical channel ID and the PDCP PDU, and transmits the MAC PDU to the UE 102 via multicast or unicast (528). The UE 102 receives the MAC PDU via multicast or unicast (528), extracts the PDCP PDU and the logical channel ID from the MAC PDU, identifies the PDCP PDU associated with the MRB according to the logical channel ID, and extracts the MBS data packets from the PDCP PDU according to the PDCP configuration in the MRB configuration.
[0085] In some implementations, the configuration parameters may include one or more MRB configurations that configure one or more MRBs associated with the first MBS session. The configuration parameters may also include one or more RLC bearer configurations, each associated with a particular MRB. Each of the MRB configurations may include an MRB ID, a PDCP configuration, a first MBS session ID, a PDCP re-establishment indication (e.g., reestablishPDCP), and / or a PDCP recovery indication (e.g., recoveryPDCP). In some implementations, the PDCP configuration may be a PDCP-Config IE for the DRB. In other implementations, the RLC bearer configuration may be an RLC-BearerConfig IE. In some implementations, the RLC bearer configuration may include a logical channel (LC) ID that configures a logical channel. In some implementations, the logical channel may be a multicast traffic channel (MTCH). In other implementations, the logical channel may be a dedicated traffic channel (DTCH). In some implementations, the configuration parameters may include a logical channel configuration (e.g., a LogicaChannelConfig IE) that configures a logical channel. In some implementations, the RLC bearer configuration may include an MRB ID.
[0086] In some implementations, the CU 172 can configure the MRB as a DL-only RB in the MRB configuration. For example, the CU 172 can refrain from including UL configuration parameters in the PDCP configuration in the MRB configuration to configure the MRB as a DL-only RB. The CU 172 can include only DL configuration parameters in the MRB configuration, for example, as described above. In such a case, the CU 172 configures the UE 102 not to transmit UL PDCP data PDUs to the DU 174 and / or the CU 172 via the MRB by not including UL configuration parameters for the MRB in the PDCP configuration in the MRB configuration. In another example, the DU 174 refrains from including UL configuration parameters in the RLC bearer configuration. In such a case, the DU 174 configures the UE 102 not to transmit control PDUs to the base station 104 via logical channels by not including UL configuration parameters in the RLC bearer configuration.
[0087] If the DU 174 includes the UL configuration parameters in the RLC bearer configuration, the UE 102 may use the UL configuration parameters to transmit a control PDU (e.g., a PDCP control PDU and / or an RLC control PDU) to the DU 174 via a logical channel. If the control PDU is a PDCP control PDU, the DU 174 may transmit the PDCP control PDU to the CU 172. For example, the CU 172 may configure the UE to receive MBS data using a compression (decompression) protocol (e.g., a Robust Header Compression (ROHC) protocol). In this case, when the CU 172 receives an MBS data packet from the CN 110 (524), the CU 172 compresses the MBS data packet using the compression protocol to obtain a compressed MBS data packet, and transmits a PDCP PDU including the compressed MBS data packet to the DU 174 via a common CU-to-DU DL tunnel (526). The DU 174 then transmits (e.g., multicast or unicast) the PDCP PDU to the UE 102 via a logical channel (528). When the UE 102 receives the PDCP PDU via the logical channel, the UE 102 extracts the compressed MBS data packet from the PDCP PDU. The UE 102 decompresses the compressed MBS data packet using a compression (decompression) protocol to obtain the original MBS data packet. In such a case, the UE 102 may transmit a PDCP control PDU including a header compression protocol feedback (e.g., interspersed ROHC feedback) for the operation of the header compression (decompression) protocol to the DU 174 via the logical channel. Then, the DU 174 transmits the PDCP control PDU to the CU 172 via a UE-specific UL tunnel, i.e., the UL tunnel is specific to the UE 102 (e.g., UE 102A). In some implementations, the CU 172 may include in the UE context request message a CU UL transport layer configuration for configuring the UE-specific UL tunnel. The CU UL transport layer configuration includes a CU transport layer address (e.g., an Internet Protocol (IP) address) and a CU UL TEID for identifying the UE-specific UL tunnel.
[0088] In some implementations, the MRB configuration may be an MRB-ToAddMod IE (e.g., mrb-Identity or MRB-Identity) that includes an MRB ID. The MRB ID identifies a particular MRB of the MRB. The base station 104 sets the MRB ID to a different value. When the CU 172 configures a DRB for the UE 102 for unicast data communication, in some implementations, the CU 172 may set one or more of the MRB IDs to a value different from the DRB ID of the DRB. In such a case, the UE 102 and the CU 172 may distinguish whether the RB is an MRB or a DRB according to the RB ID of the RB. In other implementations, the CU 172 may set one or more of the MRB IDs to a value that may be the same as the DRB ID. In such a case, the UE 102 and the CU 172 may distinguish whether the RB is an MRB or a DRB according to the RB ID of the RB and the RRC IE that configures the RB. For example, a DRB configuration that configures a DRB is a DRB-ToAddMod IE that includes a DRB identity (e.g., drb-Identity or DRB-Identity) and a PDCP configuration. Thus, the UE 102 can determine that an RB is a DRB if it receives a DRB-ToAddMod IE that configures an RB, and can determine that an RB is an MRB if it receives an MRB-ToAddMod IE that configures an RB. Similarly, the CU 172 can determine that an RB is a DRB if it sends a DRB-ToAddMod IE that configures an RB to the UE 102, and can determine that an RB is an MRB if it sends an MRB-ToAddMod IE that configures an RB to the UE 102.
[0089] In some implementations, the configuration parameters for receiving MBS data of the first MBS session include one or more logical channel (LC) IDs for configuring one or more logical channels. In some implementations, the logical channel may be a dedicated traffic channel (DTCH). In other implementations, the logical channel may be a multicast traffic channel (MTCH). In some implementations, the configuration parameters may or may not include a group radio network temporary identifier (G-RNTI). An RRC reconfiguration message for a UE joining the first MBS session includes the same configuration parameters as for receiving MBS data of the first MBS session. In some implementations, an RRC reconfiguration message for a UE may include the same or different configuration parameters as for receiving non-MBS data.
[0090] In some implementations, the CU 172 may include an MBS session join response message in an RRC reconfiguration message. The UE 102 may include an MBS session join complete message in an RRC reconfiguration complete message. Alternatively, the UE 102 may send a UL RRC message including the MBS session join complete message to the CU 172 via the DU 174. The UL RRC message may be any suitable RRC message that may include a UL Information Transfer message or a UL NAS PDU. The CU 172 may include the MBS session join complete message in a second BS-to-CN message. Alternatively, the CU 172 may send a BS-to-CN message (e.g., an UPLINK NAS TRANSPORT message) including the MBS session join complete message to the CN 110.
[0091] In other implementations, the CU 172 sends a DL RRC message including an MBS Session Join Response message to the UE 102. The DL RRC message may be a DL Information Transfer message, another RRC Reconfiguration message, or any suitable RRC message that may include a DL NAS PDU. The UE 102 may send a UL RRC message including an MBS Session Join Complete message to the CU 172 via the DU 174. The UL RRC message may be a UL Information Transfer message, another RRC Reconfiguration Complete message, or any suitable RRC message that may include a UL NAS PDU.
[0092] 5A, the UE 103 may perform an MBS session join procedure (530) similar to procedure 502 discussed above. The UE 103 may perform a PDU session establishment procedure with the CN 110 via the base station 104 as described above. The UE 103 may communicate a PDU session ID with the CN 110 in the PDU session establishment procedure. The UE 103 may join a different MBS session from the UE 102 by sending an MBS session join request and specifying a different MBS session ID (e.g., a second MBS session ID).
[0093] The CU172 includes additional transport layer configurations of the additional MBS sessions for configuring additional common DL tunnels in the BS-to-CN message in the MBS resource setup and UE-specific MBS session configuration procedure, similar to the first BS-to-CN message or the second BS-to-CN message. Each of the transport layer configurations may configure a specific common DL tunnel of the common DL tunnels and be associated with a specific MBS session of the additional MBS session. The transport layer configurations may be different to distinguish different common DL tunnels. In particular, any pair of transport layer configurations may have different IP addresses, different DL TEIDs, or different IP addresses as well as different DL TEIDs.
[0094] The CU 172 and the CN 110 then perform an MBS session resource setup procedure for the second MBS session (587) to establish a second common CN-to-BS DL tunnel and a second common CU-to-DU DL tunnel, similar to the MBS session resource setup procedure for the first MBS session 586 discussed above. The UE 103, the CU 172, and the CN 110 perform a UE-specific MBS session configuration procedure for the second MBS session (589), similar to the UE-specific MBS session configuration procedure for the first MBS session 590 discussed above.
[0095] In a UE-specific MBS session configuration procedure 590 for the second MBS session, the RRC reconfiguration message may include a different LCID (value), MRB configuration, and RLC bearer configuration as event 520. The RRC reconfiguration message may have, for example, a different G-RNTI, LCID, and / or RLC bearer configuration.
[0096] The CN 110 can then transmit (532) the MBS data for the first MBS session to the CU 172 and (538) the MBS data for the second MBS session to the CU 172 via their respective common CN-to-BS DL tunnels. The CU 172 then transmits (534) the MBS data for the first MBS session to the DU 174 and (540) the MBS data for the second MBS session to the DU 174 via their respective common CU-to-DU DL tunnels. The DU 174 transmits (536) the MBS data for the second MBS session to the UE 103 via one or more logical channels and / or MRBs and transmits (542) the MBS data for the first MBS session to the UE 102 via one or more logical channels and / or MRBs. UE 102 receives MBS data for the first MBS session via one or more logical channels (542), and UE 103 receives MBS data for the second MBS session via one or more logical channels that may be different from the logical channel for the first MBS session (536).
[0097] FIG. 5B illustrates an example scenario 500B similar to the scenario illustrated in FIG. 5A. In the example scenario 500B, the UE 103 participates in both the second MBS session (as in the example scenario 500A) and the first MBS session during the same period. More specifically, the UE 103 may perform an MBS session join procedure for the second MBS session (530) and may perform an MBS session join procedure for the first MBS session (531). The base station 104 and the CN 110 then perform an MBS session resource setup procedure for the second MBS session (587). The UE 103, the base station 104, and the CN 110 perform a UE-specific MBS session configuration procedure for the second MBS session (589). Additionally, the UE 103, the base station 104, and the CN perform a UE-specific MBS session configuration procedure for the first MBS session.
[0098] The UE 103 can join the same MBS session as the UE 102 by specifying the same MBS session ID (e.g., the first MBS session ID) in the MBS session join request. In this example scenario, the UE 103 joins the first MBS session after the base station 104 starts transmitting (528) MBS data packets for the first MBS session to the UE 102. The CN 110 sends a CN-to-BS message including the MBS session ID and / or the PDU session ID to the CU 172 to indicate that the UE 103 should start receiving MBS data for the first MBS session corresponding to the first MBS session ID.
[0099] The CU 172 or the CN 110 determines that a DL tunnel for the first MBS session already exists and that there is no need to perform procedure 586. However, optionally, the CU 172 sends a CU-to-DU message to the DU 174 to request a setup for the MBS context and / or a common DL tunnel for the first MBS session, and the DU 174 responds with a DU configuration. The CU 172 sends an RRC reconfiguration message to the UE 103 to configure the UE 103 to receive MBS traffic for the first MBS session. The RRC reconfiguration message may include the same LCID (value), MRB configuration, and RLC bearer configuration as for the UE 102 when the UEs 102 and 103 operate in the same cell. When the UEs 102A and 102B operate in different cells, the RRC reconfiguration message may have, for example, different G-RNTI, LCID, and / or RLC bearer configuration. The RRC reconfiguration message may include the same MRB configuration for UE 102 when UE 102 and 103 operate in different cells. As shown in FIG. 3, CU 172 may map data packets arriving over a common CN-to-BS DL tunnel to one or more MRBs, each corresponding to a common CU-to-DU DL tunnel and / or a respective logical channel. Furthermore, the RRC reconfiguration message may include the same LCID (value), MRB configuration, and RLC bearer configuration for the first MBS session for UE 103 as the LCID (value), MRB configuration, and RLC bearer configuration for the second MBS session for UE 103. Thus, UE 103 may receive MBS data for the first MBS session and the second MBS session over the same logical channel and / or MRB.
[0100] In any case, the CN 110 can then transmit (532) the MBS data for the first MBS session to the CU 172 and transmit (538) the MBS data for the second MBS session to the CU 172. The CU 172 then transmits (534) the MBS data for the first MBS session to the DU 174 and transmits (540) the MBS data for the second MBS session to the DU 174. The DU 174 transmits (536) the MBS data for the second MBS session to the UE 103 via one or more logical channels and / or MRBs and transmits (546) the MBS data for the first MBS session to the UE 103 via one or more logical channels and / or MRBs. The UE 103 receives (536) the MBS data for the first MBS session and (546) the MBS data for the second MBS session during the same period so that the UE 103 can receive two sets of MBS data for different MBS sessions at one time. In addition, the DU 174 transmits (542) the MBS data for the first MBS session to the UE 102 via one or more logical channels and / or MRBs. In some implementations, the DU 174 transmits (542) the MBS data for the first MBS session to the UE 102 and (546) the UE 103 via multicast. In other implementations, the DU 174 transmits (542) the MBS data for the first MBS session to the UE 102 and (546) the UE 103 separately via unicast.
[0101] In some implementations, the CU 172 transmits two entities of MBS data for the first MBS session to the DU 174 (544). The DU then transmits the first entity of MBS data for the first MBS session to the UE 102 (542) and the second entity of MBS data for the first MBS session to the UE 103 (546). In other implementations, the DU 174 receives the single entity of MBS data for the first MBS session from the CU 172 and transmits the MBS data for the first MBS session to each of the UEs that have joined the first MBS session.
[0102] Some example scenarios in which the devices shown in Figures 1A and 1B can be implemented are now discussed with reference to Figures 6 to 15. 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, and / or may be implemented by processing hardware.
[0103] 6, a base station, such as the base station 104 or a DU in the base station 104, can perform a method 600 to identify UEs for transmitting MBS data packets via multicast and / or identify UEs for transmitting MBS data packets via unicast. The method 600 begins at block 602, where the base station or DU receives a data packet from an upstream network node (e.g., CU, CU-UP, (MB-)UPF, etc.) via a DL tunnel (see, e.g., events 524, 526, 532, 534, 538, 540, 544). The base station or DU can determine which tunnel the data packet corresponds to based on the IP address and TEID or other suitable transport layer information included in the packet's header. The data packet can be an IP packet, an Ethernet packet, or a UP packet. In such a case, the base station or DU receives the data packet from a UPF (e.g., UPF 162 or MB-UPF 162). In some implementations, the data packet is associated with an MBS session. In some implementations, the packet may be a PDCP PDU, and the DU may receive the PDCP PDU from the CU. If the PDCP PDU includes an IP packet, an Ethernet packet, an MBS data packet, or a UP packet, the DU may receive the PDCP PDU from a CU-UP (e.g., CU-UP172B).
[0104] In block 604, the base station or DU identifies the DL tunnel from which the data packet was received. For example, the base station or DU identifies the DL tunnel as the first DL tunnel, the second DL tunnel, or the third DL tunnel. The base station or DU then identifies the UEs for transmitting the data packet via multicast and / or the UEs for transmitting the data packet via unicast based on the DL tunnel through which the data packet was received. For example, the base station or DU can maintain a table or mapping indicating each active DL tunnel, a set of UEs for receiving MBS data packets via multicast (e.g., as indicated by a G-RNTI), a set of UEs for receiving MBS data packets via unicast (e.g., as indicated by a C-RNTI), individual legacy UEs for receiving MBS data packets via unicast (e.g., as indicated by a C-RNTI), a logical channel ID corresponding to the DL tunnel, an MRB for the DL tunnel, a DRB for the DL tunnel, etc.
[0105] In response to determining that the DL tunnel is the first DL tunnel, the base station or DU transmits the data packet to the first set of UEs via an MBS multicast data transmission (block 606) (e.g., see events 528, 536, 542, 546) and transmits the data packet to the second set of UEs via an MBS unicast data transmission (block 608) (e.g., see events 528, 536, 542, 546).
[0106] In response to determining that the DL tunnel is the second DL tunnel, the base station or DU transmits the data packet to the third set of UEs (block 610) (see, e.g., events 528, 536, 542, 546) via MBS multicast data transmission and transmits the data packet to the fourth set of UEs (block 612) (see, e.g., events 528, 536, 542, 546) via MBS unicast data transmission. In some implementations, the first set of UEs and the third set of UEs may include the same UEs and / or different UEs. Also, in some implementations, the second set of UEs and the fourth set of UEs may include the same UEs and / or different UEs.
[0107] In response to determining that the DL tunnel is the third DL tunnel, the base station or DU transmits the data packet to the particular legacy UE via a non-MBS unicast data transmission (block 614).
[0108] FIG. 7 shows an example method 700 similar to method 600, except that the base station or DU identifies a logical channel to use to transmit an MPS data packet to the UE based on the tunnel through which the data packet was received.
[0109] In response to determining that the DL tunnel is the first DL tunnel, the base station or DU determines (e.g., identifies or selects) a first logical channel ID (block 706). The base station or DU then generates a PDU (e.g., a MAC PDU) including the first logical channel ID and the data packet (block 708). The base station or DU then transmits the PDU to the first set of UEs via MBS multicast data transmission (block 710) (see, e.g., events 528, 536, 542, 546) and transmits the PDU to the second set of UEs via MBS unicast data transmission (block 712) (see, e.g., events 528, 536, 542, 546).
[0110] In response to determining that the DL tunnel is the second DL tunnel, the base station or DU determines (e.g., identifies or selects) a second logical channel ID (block 714). The base station or DU then generates a PDU (e.g., a MAC PDU) including the second logical channel ID and the data packet (block 716). The base station or DU then transmits the PDU via MBS multicast data transmission to a third set of UEs (block 718) (see, e.g., events 528, 536, 542, 546) and transmits the PDU via MBS unicast data transmission to a fourth set of UEs (block 720) (see, e.g., events 528, 536, 542, 546). Blocks 714, 716, 718, and 720 are collectively referred to in FIG. 7 as block 760.
[0111] In response to determining that the DL tunnel is a third DL tunnel, the base station or DU determines (e.g., identifies or selects) a third logical channel ID (block 722). The base station or DU then generates a PDU (e.g., a MAC PDU) including the third logical channel ID and the data packet (block 724). The base station or DU then transmits the data packet to the particular legacy UE via a non-MBS unicast data transmission (block 726). Blocks 722, 724, and 726 are collectively referred to in FIG. 7 as block 770.
[0112] FIG. 8 illustrates an example method 800 similar to method 700, except that the base station or DU identifies a set of logical channels to be used to transmit MBS data packets to respective UEs via unicast.
[0113] In response to determining that the DL tunnel is the first DL tunnel, the base station or DU performs some of the same steps as method 700 (blocks 706, 708, 710) to transmit the MBS data packets to the first set of UEs via multicast. To transmit the MBS data packets to the second set of UEs via unicast, the base station or DU determines (e.g., identifies or selects) a set of M logical channel IDs corresponding to the second set of M UEs (block 808). The base station or DU then generates M PDUs each including one of the M logical channel IDs and a data packet for each of the second set of M UEs (block 810) (see, e.g., events 528, 536, 542, 546). The base station or DU then transmits the M PDUs to each of the second set of M UEs via M MBS unicast data transmissions (block 812) (see, e.g., events 528, 536, 542, 546).
[0114] In response to determining that the DL tunnel is the second DL tunnel, the base station or DU performs some of the same steps as method 700 (blocks 714, 716, 718) to transmit the MBS data packets to the third set of UEs via multicast. To transmit the MBS data packets to the fourth set of UEs via unicast, the base station or DU determines (e.g., identifies or selects) a set of N logical channel IDs corresponding to the fourth set of N UEs (block 816). The base station or DU then generates N PDUs each including one of the N logical channel IDs and a data packet for each of the fourth set of N UEs (block 818) (see, e.g., events 528, 536, 542, 546). The base station or DU then transmits the N PDUs to each of the fourth set of N UEs via N MBS unicast data transmissions (block 820) (see, e.g., events 528, 536, 542, 546). Blocks 814, 816, 818, and 820 are collectively referred to in FIG.
[0115] FIG. 9 illustrates an example method 900 similar to method 700, except that a base station or DU identifies a G-RNTI for transmitting an MBS data packet to a UE corresponding to the G-RNTI via multicast, and the G-RNTI and corresponding UE are identified based on the tunnel through which the data packet is received.
[0116] In response to determining that the DL tunnel is the first DL tunnel, the base station or DU determines (e.g., identifies or selects) a first logical channel ID and a first G-RNTI corresponding to the first set of UEs from method 700 (block 906). The base station or DU then generates a PDU (e.g., a MAC PDU) including the first logical channel ID and the data packet (block 908) (see, e.g., events 528, 536, 542, 546). The base station or DU also generates a DCI and a CRC of the DCI to schedule a physical downlink shared channel (PDSCH) transmission of the PDU (block 910) (see, e.g., events 528, 536, 542, 546). The base station or DU then scrambles the CRC with the first G-RNTI to obtain a scrambled CRC (block 912). The base station or DU transmits the DCI and scrambled CRC on a physical downlink control channel (PDCCH) (block 922) (see, e.g., events 528, 536, 542, 546) and transmits a PDSCH transmission of the PDU via multicast in accordance with the DCI (block 924) (see, e.g., events 528, 536, 542, 546). In this manner, a first set of UEs corresponding to the first G-RNTI receive the MBS data packet.
[0117] In response to determining that the DL tunnel is the second DL tunnel, the base station or DU determines (e.g., identifies or selects) a second logical channel ID and a second G-RNTI corresponding to the third set of UEs from method 700 (block 914). The base station or DU then generates a PDU (e.g., a MAC PDU) including the second logical channel ID and the data packet (block 916) (see, e.g., events 528, 536, 542, 546). The base station or DU also generates a DCI and a CRC of the DCI to schedule a PDSCH transmission of the PDU (block 917) (see, e.g., events 528, 536, 542, 546). The base station or DU then scrambles the CRC with the second G-RNTI to obtain a scrambled CRC (block 920) (see, e.g., events 528, 536, 542, 546). The base station or DU transmits the DCI and scrambled CRC on the PDCCH (block 922) and transmits a PDSCH transmission of the PDU via multicast in accordance with the DCI (block 924) (see, e.g., events 528, 536, 542, 546). In this manner, a third set of UEs corresponding to the second G-RNTI receive the MBS data packet. Blocks 914, 916, 916, 917, 920, 922, and 924 are collectively referred to in FIG. 9 as block 960.
[0118] 10A-10C show example methods 1000A, 1000B, 1000C that are similar to method 900, except that the base station or DU transmits the MBS data packet via unicast when the tunnel through which the data packet is received is the second DL tunnel.
[0119] In method 1000A, in response to determining that the DL tunnel is the first DL tunnel, the base station or DU performs some of the same steps as method 900 (blocks 906, 908, 910, 912, 922, and 924) to transmit MBS data packets via multicast to the first set of UEs.
[0120] In response to determining that the DL tunnel is the second DL tunnel, the base station or DU determines (e.g., identifies or selects) a second logical channel ID (block 1008). The base station or DU then generates a PDU (e.g., a MAC PDU) including the second logical channel ID and a data packet (block 1010). The base station or DU also determines (e.g., identifies or selects) N C-RNTIs for identifying a second set of N UEs (e.g., a fourth set of UEs in the method 700 for receiving a PDU from the second DL tunnel via unicast), respectively (block 1012). The base station or DU then generates N DCIs and N CRCs of the N DCIs to schedule N PDSCH transmissions of the PDU (block 1014) (see, e.g., events 528, 536, 542, 546). The base station or DU then scrambles each of the N CRCs with the respective C-RNTI to obtain N scrambled CRCs (block 1016) (see, e.g., events 528, 536, 542, 546). The base station or DU then transmits the N DCIs and the N scrambled CRCs on the N PDCCHs (block 1018) (see, e.g., events 528, 536, 542, 546). The base station or DU then transmits N PDSCH transmissions of the PDUs via unicast according to the N DCIs (block 1020) (see, e.g., events 528, 536, 542, 546). In this manner, a second set of N UEs corresponding to the N C-RNTIs receive the MBS data packet. Blocks 1012, 1014, 1016, 1018, and 1020 are collectively referred to in FIG. 10A as block 1080. Blocks 1008, 1010, and 1080 are collectively referred to as block 1090 in FIG. 10A.
[0121] FIG. 10B shows an example method 1000B similar to method 1000A in which a base station or DU identifies a set of N logical channels and generates a set of N PDUs to be used to transmit MBS data packets via unicast to a second set of N respective UEs.
[0122] In response to determining that the DL tunnel is a second DL tunnel, the base station or DU determines (e.g., identifies or selects) a set of N logical channel IDs corresponding to a second set of N UEs (e.g., a fourth set of UEs in the method 700 for receiving PDUs from a second DL tunnel via unicast) (block 1009). The base station or DU then generates (block 1011) N PDUs each including one of the N logical channel IDs and a data packet for each of the second set of N UEs (see, e.g., events 528, 536, 542, 546). The base station or DU also determines (e.g., identifies or selects) N C-RNTIs for identifying the second set of N UEs, respectively (block 1012). The base station or DU then generates N DCIs and N CRCs for the N DCIs (block 1015) to schedule N PDSCH transmissions for the N PDUs, respectively (see, e.g., events 528, 536, 542, 546). The base station or DU then scrambles each of the N CRCs with the respective C-RNTI (block 1016) to obtain N scrambled CRCs (see, e.g., events 528, 536, 542, 546). The base station or DU transmits the N DCIs and the N scrambled CRCs on the N PDCCHs, respectively (block 1018) (see, e.g., events 528, 536, 542, 546). The base station or DU then transmits N PDSCH transmissions of the N PDUs via unicast according to the N DCIs, respectively (block 1021) (see, e.g., events 528, 536, 542, 546). In this manner, a second set of N UEs corresponding to the N C-RNTIs receive the MBS data packet. Blocks 1009, 1011, 1012, 1015, 1016, 1018, and 1021 are collectively referred to in FIG. 10B as block 1091.
[0123] FIG. 10C shows an example method 1000C that is similar to method 1000A, except that the base station or DU generates the same DCI and scrambles the same CRC with N C-RNTIs to identify a second set of N UEs for each of the N PDCCH transmissions.
[0124] In response to determining that the DL tunnel is the second DL tunnel, the base station or DU determines (e.g., identifies or selects) a second logical channel ID (block 1008). The base station or DU then generates (block 1010) (e.g., see events 528, 536, 542, 546) a PDU (e.g., MAC PDU) including the second logical channel ID and a data packet. The base station or DU also determines (e.g., identifies or selects) N C-RNTIs for identifying a second set of N UEs (e.g., a fourth set of UEs in the method 700 for receiving a PDU from the second DL tunnel via unicast), respectively (block 1012). The base station or DU then generates (block 1013) (e.g., see events 528, 536, 542, 546) a single DCI and a single CRC of the DCI to schedule a PDSCH transmission of the PDU. The base station or DU then scrambles the CRC with each of the N C-RNTIs to obtain N scrambled CRCs (block 1017) (see, e.g., events 528, 536, 542, 546). The base station or DU transmits the DCI and the N scrambled CRCs on the N PDCCHs, respectively (block 1019) (see, e.g., events 528, 536, 542, 546). The base station or DU then transmits a PDSCH transmission of the PDU via unicast according to the DCI (block 1022) (see, e.g., events 528, 536, 542, 546). In this manner, a second set of N UEs corresponding to the N C-RNTIs receive the MBS data packet. Blocks 1012, 1013, 1017, 1019, and 1022 are collectively referred to in FIG. 10C as block 1081. Blocks 1008, 1010, and 1081 are collectively referred to in FIG. 10C as block 1092.
[0125] 11A-11C show example methods 1100A, 1100B, and 1100C that are similar to methods 1000A, 1000B, and 1000C, respectively, except that the base station or DU also transmits the MBS data packet via unicast when the tunnel through which the data packet was received is the first DL tunnel. In example methods 1100A, 1100B, and 1100C, the MBS data packet is transmitted via unicast for both the first DL tunnel and the second DL tunnel.
[0126] 11A illustrates an exemplary method 1100A including similar steps for transmitting a data packet received via a first DL tunnel as in method 1000A when the data packet is received via a second DL tunnel. More specifically, in response to determining that the DL tunnel is the first DL tunnel, the base station or DU determines (e.g., identifies or selects) a first logical channel ID (block 1106). The base station or DU then generates (block 1108) (e.g., see events 528, 536, 542, 546) a PDU (e.g., a MAC PDU) including the first logical channel ID and the data packet. The base station or DU also determines (e.g., identifies or selects) M C-RNTIs (block 1110) (e.g., see events 528, 536, 542, 546) for identifying a first set of M UEs (e.g., a second set of UEs in method 700 for receiving a PDU from a first DL tunnel via unicast), respectively. The base station or DU then generates M DCIs and M CRCs for the M DCIs to schedule M PDSCH transmissions of the PDU, respectively (block 1112) (see, e.g., events 528, 536, 542, 546). The base station or DU then scrambles each of the M CRCs with the respective C-RNTI to obtain M scrambled CRCs (block 1114) (see, e.g., events 528, 536, 542, 546). The base station or DU then transmits the M DCIs and the M scrambled CRCs on the M PDCCHs, respectively (block 1116). The base station or DU then transmits the M PDSCH transmissions of the PDU via unicast according to the M DCIs, respectively (block 1118) (see, e.g., events 528, 536, 542, 546). In this manner, the first set of M UEs corresponding to the M C-RNTIs receive the MBS data packet. Blocks 1110, 1112, 1114, 1116, and 1118 are collectively referred to in FIG. 11A as block 1180. Blocks 1106, 1108, and 1180 are collectively referred to in FIG. 11A as block 1190.
[0127] 11B illustrates an exemplary method 1100B including similar steps for transmitting a data packet received via a first DL tunnel as in method 1000B when the data packet is received via a second DL tunnel. More specifically, in response to determining that the DL tunnel is a first DL tunnel, the base station or DU determines (e.g., identifies or selects) a set of M logical channel IDs corresponding to a first set of M UEs (e.g., a second set of UEs in method 700 for receiving PDUs from a first DL tunnel via unicast) (block 1107). The base station or DU then generates M PDUs each including one of the M logical channel IDs and the data packet for each of the first set of M UEs (block 1109) (see, e.g., events 528, 536, 542, 546). The base station or DU also determines (e.g., identifies or selects) M C-RNTIs for identifying the first set of M UEs, respectively (block 1110). The base station or DU then generates M DCIs and M CRCs for the M DCIs (block 1113) to schedule M PDSCH transmissions for the M PDUs, respectively (see, e.g., events 528, 536, 542, 546). The base station or DU then scrambles each of the M CRCs with a respective C-RNTI (block 1114) to obtain M scrambled CRCs (see, e.g., events 528, 536, 542, 546). The base station or DU transmits the M DCIs and the M scrambled CRCs on the M PDCCHs, respectively (block 1116) (see, e.g., events 528, 536, 542, 546). The base station or DU then transmits M PDSCH transmissions of the M PDUs via unicast according to the M DCIs, respectively (block 1119) (see, e.g., events 528, 536, 542, 546). In this manner, the first set of M UEs corresponding to the M C-RNTIs receive the MBS data packet. Blocks 1107, 1109, 1110, 1113, 1114, 1116, and 1119 are collectively referred to in FIG. 11B as block 1191.
[0128] 11C illustrates an exemplary method 1100C including similar steps for transmitting a data packet received via a first DL tunnel as in method 1000C when the data packet is received via a second DL tunnel. More specifically, in response to determining that the DL tunnel is the first DL tunnel, the base station or DU determines (e.g., identifies or selects) a first logical channel ID (block 1106). The base station or DU then generates (block 1108) a PDU (e.g., a MAC PDU) including the first logical channel ID and the data packet (see, e.g., events 528, 536, 542, 546). The base station or DU also determines (e.g., identifies or selects) M C-RNTIs for identifying a first set of M UEs (e.g., a second set of UEs in method 700 for receiving a PDU from a first DL tunnel via unicast), respectively (block 1110). The base station or DU then generates a single DCI and a single CRC of the DCI to schedule a PDSCH transmission of the PDU (block 1111) (see, e.g., events 528, 536, 542, 546). The base station or DU then scrambles the CRC with each of the M C-RNTIs to obtain M scrambled CRCs (block 1115) (see, e.g., events 528, 536, 542, 546). The base station or DU transmits the DCI and the M scrambled CRCs on M PDCCHs, respectively (block 1117) (see, e.g., events 528, 536, 542, 546). The base station or DU then transmits a PDSCH transmission of the PDU via unicast according to the DCI (block 1122) (see, e.g., events 528, 536, 542, 546). In this manner, the first set of M UEs corresponding to the M C-RNTIs receive the MBS data packet. Blocks 1106, 1108, 1110, 1111, 1115, 1117, and 1122 are collectively referred to as block 1192 in FIG.
[0129] FIG. 12 shows an example method 1200 similar to method 700, except that when the tunnel through which the data packet is received is a third DL tunnel, the base station or DU identifies a C-RNTI for transmitting a data packet to a particular legacy UE corresponding to the C-RNTI via non-MBS unicast.
[0130] In response to determining that the DL tunnel is the third DL tunnel, the base station or DU determines (e.g., identifies or selects) a third logical channel ID and a C-RNTI corresponding to the particular UE from method 700 (block 1214). The base station or DU then generates a PDU (e.g., a MAC PDU) including the third logical channel ID and the data packet (block 1216) (see, e.g., events 528, 536, 542, 546). The base station or DU also generates a DCI and a CRC of the DCI to schedule a PDSCH transmission of the PDU (block 1210) (see, e.g., events 528, 536, 542, 546). The base station or DU then scrambles the CRC with the C-RNTI to obtain a scrambled CRC (block 1212) (see, e.g., events 528, 536, 542, 546). The base station or DU transmits the DCI and scrambled CRC on the PDCCH (block 1214) and transmits a PDSCH transmission of the PDU via unicast in accordance with the DCI (block 1216) (see, e.g., events 528, 536, 542, 546). In this manner, a particular legacy UE corresponding to the C-RNTI receives the data packet. Blocks 1214, 1216, 1218, 1220, 1222, and 1224 are collectively referred to in FIG. 12 as block 1270.
[0131] In some implementations, in addition to or instead of determining the tunnel from which the data packet was received, the base station 104 or DU 174 determines a QoS flow associated with the data packet. Figure 13A illustrates an example method 1300A for determining which logical channel to use and whether to transmit the MBS data packet via unicast or multicast based on an MBS QoS flow ID associated with the MBS data packet.
[0132] In block 1302, the base station or DU receives a data packet from an upstream network node (e.g., CU, CU-UP, (MB-)UPF, etc.) associated with the QoS flow (e.g., see events 524, 526, 532, 534, 538, 540, 544). In some implementations, the base station or DU may receive a first QoS information (e.g., a first QoS flow ID) associated with the first QoS flow and a second QoS information (e.g., a second QoS flow ID) associated with the second QoS flow from an upstream network node, an AMF, or a CU-CP prior to block 1302 (e.g., see events 504, 506, 512, 514, 586, 587, 589). In some implementations, the base station or CU receives the first QoS information and / or the second QoS information from the AMF in at least one CN-to-BS message. For example, the at least one CN-to-BS message includes an MBS session resource setup request message (e.g., event 504), a UE-associated CN-to-BS message (e.g., events 512, 532), and / or a non-UE-associated CN-to-BS message (e.g., event 512).
[0133] Also, in some implementations, the DU receives the first QoS information and / or the second QoS information from the CU in at least one CU-to-DU message, for example, the at least one CU-to-DU message including an MBS context request message (e.g., event 506) and / or a UE-associated CU-to-DU message (e.g., events 514, 534).
[0134] The base station or DU then receives a container packet (e.g., a tunnel packet or a GTP-U packet) including QoS information (e.g., a QoS flow ID) and a data packet from the CN. If the QoS information is a first QoS information having a first QoS flow ID, the base station or DU determines that the data packet is associated with the first QoS flow (block 1304). If the QoS information is a second QoS information having a second QoS flow ID, the base station or DU determines that the data packet is associated with the second QoS flow (block 1304).
[0135] The base station or DU then identifies UEs for transmitting the data packet via multicast and / or UEs for transmitting the data packet via unicast based on the QoS flow associated with the data packet. For example, the base station or DU may maintain a table or mapping from the QoS information received from the CU indicating each QoS flow, whether to transmit the data packet to the UE via multicast or unicast, a logical channel ID corresponding to the QoS flow, a set of UEs for receiving the MBS data packet via multicast (e.g., as indicated by the G-RNTI), a set of UEs for receiving the MBS data packet via unicast (e.g., as indicated by the C-RNTI), etc.
[0136] In response to determining that the QoS information has a first QoS flow ID for the first QoS flow, the base station or DU determines (e.g., identifies or selects) a first logical channel ID (block 1306). The base station or DU then generates a PDU (e.g., a MAC PDU) including the first logical channel ID and the data packet (block 1308) (see, e.g., events 528, 536, 542, 546). The base station or DU then transmits the PDU to the set of UEs via an MBS multicast data transmission (block 1310) (see, e.g., events 528, 536, 542, 546). If the packet is too large to be included in the payload of the PDU, the base station or DU can include a portion of the packet in the PDU. The base station or DU may then generate another PDU (i.e., a second PDU, e.g., a MAC PDU) including the first logical channel ID and another portion of the packet and transmit the other PDU to the set of UEs (e.g., see events 528, 536, 542, 546).
[0137] In response to determining that the QoS information has a second QoS flow ID for the second QoS flow, the base station or DU determines (e.g., identifies or selects) a second logical channel ID (block 1312). The base station or DU then generates a PDU (e.g., a MAC PDU) including the second logical channel ID and the data packet (block 1314) (see, e.g., events 528, 536, 542, 546). The base station or DU then transmits the PDU via an MBS unicast data transmission to the same set of UEs (block 1316) (see, e.g., events 528, 536, 542, 546). If the packet is too large to be included in the payload of the PDU, the base station or DU can include a portion of the packet in the PDU (see, e.g., events 528, 536, 542, 546). The base station or DU may then generate another PDU (i.e., a second PDU, e.g., a MAC PDU) including the second logical channel ID and another portion of the packet and transmit the other PDU to the set of UEs (see, e.g., events 528, 536, 542, 546). In this manner, the QoS flow ID may indicate to the base station or DU whether to transmit the data packet to the UE via multicast or unicast. Blocks 1304, 1306, 1308, 1310, 1312, 1314, and 1316 are collectively referred to in FIG. 13A as block 1350.
[0138] The exemplary method 1300A may be applied to a first set of UEs in the exemplary method 600. For example, in a first case, the QoS flow ID may be a first QoS flow ID. In response to determining that the QoS information includes the first QoS ID, the base station or DU transmits the data packet to the first set of UEs via a multicast data transmission. In a second case, the QoS flow ID may be a second QoS flow ID. In response to determining that the QoS information includes the second QoS ID, the base station or DU transmits the data packet to the first set of UEs via a unicast data transmission. The exemplary method 1300A may also be applied to a second set of UEs in the exemplary method 600. For example, in a third case, the QoS flow ID may be a first QoS flow ID. In response to determining that the QoS information includes the first QoS ID, the base station or DU transmits the data packet to the second set of UEs via a multicast data transmission. In a fourth case, the QoS flow ID may be a second QoS flow ID. In response to determining that the QoS information includes the second QoS ID, the base station or DU transmits the data packet to the second set of UEs via unicast data transmission. More generally, the exemplary method 1300A may be applied to any suitable set of UEs, including the third and / or fourth sets of UEs in the exemplary method 600.
[0139] FIG. 13B shows an example method 1300B that is similar to method 1300B, except that the base station or DU transmits the MBS data packet via unicast when the data packet is associated with either the first QoS flow or the second QoS flow.
[0140] In response to determining that the QoS information has a first QoS flow ID for the first QoS flow, the base station or DU determines (e.g., identifies or selects) a first logical channel ID (block 1306). The base station or DU then generates a PDU (e.g., a MAC PDU) that includes the first logical channel ID and the data packet (block 1308). The base station or DU then transmits the PDU to the set of UEs via an MBS unicast data transmission (block 1316).
[0141] In response to determining that the QoS information has a second QoS flow ID for the second QoS flow, the base station or DU determines (e.g., identifies or selects) a second logical channel ID (block 1312). The base station or DU then generates a PDU (e.g., a MAC PDU) including the second logical channel ID and the data packet (block 1314). The base station or DU then transmits the PDU to the same set of UEs via an MBS unicast data transmission (block 1316). Blocks 1304, 1306, 1308, 1312, 1314, and 1316 are collectively referred to in FIG. 13B as block 1351.
[0142] The example method 1300B may be applied, for example, to the second set or the fourth set of UEs in the example method 600.
[0143] FIG. 14A shows an example method 1400A that is similar to method 1300A, except that the base station or DU identifies a G-RNTI for transmitting MBS data packets to a UE corresponding to the G-RNTI via multicast and identifies a C-RNTI for transmitting MBS data packets to a UE corresponding to the C-RNTI via unicast.
[0144] In response to determining that the DL tunnel is the first DL tunnel, the base station or DU performs some of the same steps as method 900 (blocks 906, 908, 910, 912, 922, and 924) to transmit the MBS data packets to the set of UEs via multicast. In response to determining that the DL tunnel is the second DL tunnel, the base station or DU performs some of the same steps as one of methods 1000A, 1000B, 1000C (blocks 1090, 1091, or 1092) to transmit the MBS data packets to the set of UEs via unicast.
[0145] The example method 1400A may be applied to the first set of UEs in the example method 600. More generally, the example method 1400A may be applied to any appropriate set of UEs, including the second, third, and / or fourth set of UEs in the example method 600.
[0146] FIG. 14B illustrates an example method 1400B that is similar to method 1300B, except that the base station or DU identifies a C-RNTI for transmitting MBS data packets to a UE corresponding to the C-RNTI via unicast.
[0147] In response to determining that the DL tunnel is the first DL tunnel, the base station or DU performs some of the same steps as one of methods 1100A, 1100B, 1100C (blocks 1190, 1191, or 1192) to transmit MBS data packets to the set of UEs via unicast. In response to determining that the DL tunnel is the second DL tunnel, the base station or DU performs some of the same steps as one of methods 1000A, 1000B, 1000C (blocks 1090, 1091, or 1092) to transmit MBS data packets to the set of UEs via unicast.
[0148] The example method 1400B may be applied, for example, to the second set or the fourth set of UEs in the example method 600.
[0149] In some implementations, as mentioned above, the base station may configure a DL transport layer configuration corresponding to a common DL tunnel for receiving MBS data packets from the CN. Figure 15 illustrates an example method 1500 for configuring a DL transport layer configuration and identifying UEs for transmitting MBS data packets via multicast and / or identifying UEs for transmitting MBS data packets via unicast based on specific transport layer information associated with the MBS data packets.
[0150] In block 1502, the base station or DU configures a first DL transport layer configuration including first transport layer information for receiving packets from an upstream network node such as a CU, CU-UP, CU-CP, MB-UPF, or AMF (see, for example, events 502, 518, 524, 526, 530, 531, 532, 534, 538, 540, 544, 590). For example, in response to receiving a CU-to-DU message including an MBS context setup request, the DU sends a DU-to-CU message (e.g., an MBS context setup response message) including the first DL transport layer configuration to the CU to configure a common CU-to-DU DL tunnel for the first MBS session (e.g., event 508). In some implementations, the DU-to-CU message is a generic F1AP message or a dedicated F1AP message (e.g., an MBS context setup response message) specifically defined for this purpose.
[0151] The CU 172 may then send a first BS-to-CN message (e.g., an MBS Session Resource Setup Response message) including the first DL transport layer configuration to configure the first common DL tunnel (e.g., event 510). The CU 172 may include the first MBS Session ID and / or the first PDU Session ID in the first BS-to-CN message. The first BS-to-CN message may include the first DL transport layer configuration to configure the first common DL tunnel for the CN 110 to transmit the MBS data to the CU 172. The first DL transport layer configuration includes a first transport layer address (e.g., an IP address and / or a TEID) to identify the first common DL tunnel.
[0152] In block 1504, the base station or DU configures a second DL transport layer configuration including second transport layer information for receiving packets from an upstream network node such as a CU, CU-UP, CU-CP, MB-UPF, or AMF. For example, in response to receiving a CU-to-DU message including an MBS context setup request, the DU sends a DU-to-CU message (e.g., an MBS context setup response message) including the second DL transport layer configuration to the CU to configure a common CU-to-DU DL tunnel for the second MBS session (e.g., event 508). Each of the DL transport layer configurations may be associated with a different MBS session. In some implementations, the DU-to-CU message is a generic F1AP message or a dedicated F1AP message (e.g., an MBS context setup response message) specifically defined for this purpose.
[0153] The CU 172 may then send a first BS-to-CN message (e.g., an MBS Session Resource Setup Response message) including a second DL transport layer configuration to configure a second common DL tunnel (e.g., event 510). The CU 172 may include a second MBS Session ID and / or a second PDU Session ID in the first BS-to-CN message. The first BS-to-CN message may include a second DL transport layer configuration to configure a second common DL tunnel for the CN 110 to transmit MBS data to the CU 172. The second DL transport layer configuration includes a second transport layer address (e.g., an IP address and / or a TEID) to identify the second common DL tunnel. The first transport layer configuration and the second transport layer configuration may be different to distinguish between the first common DL tunnel and the second common DL tunnel. In particular, any pair of a first transport layer configuration and a second transport layer configuration may have different IP addresses, different DL TEIDs, or different IP addresses as well as different DL TEIDs.
[0154] In block 1506, the base station or DU configures a third DL transport layer configuration including third transport layer information for receiving packets from an upstream network node such as a CU, CU-UP, CU-CP, MB-UPF, or AMF. For example, in response to receiving a CU-to-DU message including an MBS context setup request, the DU sends a DU-to-CU message (e.g., an MBS context setup response message) including the third DL transport layer configuration to the CU to configure a common CU-to-DU DL tunnel for the third MBS session (e.g., event 508). Each of the DL transport layer configurations may be associated with a different MBS session. In some implementations, the DU-to-CU message is a generic F1AP message or a dedicated F1AP message (e.g., an MBS context setup response message) specifically defined for this purpose.
[0155] The CU 172 may then send a first BS-to-CN message (e.g., an MBS Session Resource Setup Response message) including a third DL transport layer configuration to configure a third common DL tunnel (e.g., event 510). The CU 172 may include a third MBS Session ID and / or a third PDU Session ID in the first BS-to-CN message. The first BS-to-CN message may include a third DL transport layer configuration to configure a third common DL tunnel for the CN 110 to transmit MBS data to the CU 172. The third DL transport layer configuration includes a third transport layer address (e.g., an IP address and / or a TEID) to identify the third common DL tunnel. The first transport layer configuration, the second transport layer configuration, and the third transport layer configuration may be different to distinguish the first common DL tunnel, the second common DL tunnel, and the third common DL tunnel. In particular, any pair of the first transport layer configuration, the second transport layer configuration, and the third transport layer configuration may have different IP addresses, different DL TEIDs, or different IP addresses and different DL TEIDs.
[0156] In block 1508, the base station or DU receives a DL tunnel packet from an upstream network node (e.g., CU, CU-UP, (MB-)UPF, etc.) via a DL tunnel. The DL tunnel packet includes transport layer information for a particular transport layer configuration and an MBS data packet. The base station or DU can determine which transport layer configuration and DL tunnel the data packet corresponds to based on the IP address and TEID or other suitable transport layer information included in the header of the DL tunnel packet. In some implementations, the first transport layer information includes a first transport layer address (e.g., IP address) and / or a first DL tunnel ID (e.g., GTP-U tunnel ID). In some implementations, the second transport layer information includes a second transport layer address (e.g., IP address) and / or a second DL tunnel ID (e.g., GTP-U tunnel ID). In some implementations, the third transport layer information includes a third transport layer address (e.g., IP address) and / or a third DL tunnel ID (e.g., GTP-U tunnel ID).
[0157] In some implementations, the first transport layer information, the second transport layer information, and the third transport layer information are different. For example, the first transport layer address and / or the first tunnel ID may be different from the second transport layer address and / or the second tunnel ID. If the first transport layer address and the second transport layer address are the same, the first tunnel ID and the second tunnel ID are different. If the first tunnel ID and the second tunnel ID are the same, the first transport layer address and the second transport layer address are different.
[0158] In block 1510, the base station or DU identifies the transport layer information included in the header of the DL tunnel packet and determines the DL tunnel from which the data packet was received based on the transport layer information. For example, the base station or DU identifies the transport layer information as first transport layer information, second transport layer information, or third transport layer information. If the transport layer information is the first transport layer information, the base station or DU determines that the data packet was received via the first DL tunnel. If the transport layer information is the second transport layer information, the base station or DU determines that the data packet was received via the second DL tunnel. If the transport layer information is the third transport layer information, the base station or DU determines that the data packet was received via the third DL tunnel, and so on.
[0159] The base station or DU then identifies UEs for transmitting data packets via multicast and / or UEs for transmitting data packets via unicast based on the DL tunnel through which the data packet was received. For example, the base station or DU may maintain a table or mapping indicating each active DL tunnel, a set of UEs for receiving MBS data packets via multicast (e.g., as indicated by a G-RNTI), a set of UEs for receiving MBS data packets via unicast (e.g., as indicated by a C-RNTI), individual legacy UEs for receiving MBS data packets via unicast (e.g., as indicated by a C-RNTI), a logical channel ID corresponding to the DL tunnel, an MRB for the DL tunnel, a DRB for the DL tunnel, etc.
[0160] In response to determining that the transport layer information is the first transport layer information, the base station or DU performs some of the same steps (blocks 1350, 1351, 1450, or 1451) as in one of methods 1300A, 1300B, 1400A, 1400B to transmit the MBS data packet to the set of UEs. As in methods 1300A, 1300B, 1400A, 1400B, the base station or DU may transmit the MBS data packet to the first set of UEs and / or the second set of UEs via multicast or unicast depending on the QoS flow associated with the MBS data packet, or may transmit the MBS data packet to the first set of UEs and / or the second set of UEs via unicast regardless of the QoS flow associated with the MBS data packet.
[0161] In response to determining that the transport layer information is the second transport layer information, the base station or DU performs some of the same steps (blocks 860, 960, 1090, 1091, or 1092) as in one of methods 800, 900, 1000A, 1000B, 1000C to transmit the MBS data packet to a third set of UEs via multicast and / or to a fourth set of UEs via unicast.
[0162] In response to determining that the transport layer information is third transport layer information, the base station or DU performs some of the same steps (blocks 770 or 1270) as in one of methods 700, 1200 to transmit the data packet via unicast to the particular legacy UE.
[0163] The following list of examples reflects additional embodiments specifically contemplated by this disclosure.
[0164] Example 1. A method in a base station for managing multicast and unicast data transmission, comprising: receiving, by processing hardware, multicast and / or broadcast service (MBS) downlink data packets from a core network (CN) via a downlink tunnel; determining, by the processing hardware, whether to transmit the MBS downlink data packets to a plurality of UEs via unicast or multicast; and at least one of transmitting, by the processing hardware, the MBS downlink data packets to a plurality of first UEs via multicast data transmission or transmitting, by the processing hardware, the MBS downlink data packets to a plurality of second UEs via multiple unicast data transmission.
[0165] Example 2. The method according to Example 1, wherein the step of determining whether to transmit the MBS downlink data packet via unicast or via multicast includes a step of determining, by processing hardware, whether to transmit the MBS downlink data packet to multiple UEs via unicast or via multicast based on identification information of the downlink tunnel.
[0166] Example 3. A method according to any of the preceding examples, wherein the downlink tunnel is a first downlink tunnel, and the step of transmitting the MBS downlink data packets to the plurality of first UEs or the step of transmitting the MBS downlink data packets to the plurality of second UEs includes, in response to determining that the downlink tunnel is the first downlink tunnel, transmitting, by the processing hardware, the MBS downlink data packets to the plurality of first UEs via a multicast data transmission based on an identification information of the first downlink tunnel, and transmitting, by the processing hardware, the MBS downlink data packets to the plurality of second UEs via a plurality of unicast data transmissions based on an identification information of the first downlink tunnel.
[0167] Example 4. The method according to any of the preceding examples, further comprising, in response to determining that the downlink tunnel is a first downlink tunnel in a first case, that the downlink tunnel is a second downlink tunnel in a second case, that the multicast data transmission is a first multicast data transmission, that the plurality of unicast data transmissions is a first plurality of unicast data transmissions, and that the downlink tunnel is a second downlink tunnel in the second case, transmitting, by the processing hardware, the MBS downlink data packets to a plurality of third UEs via a second multicast data transmission based on an identification information of the second downlink tunnel, and transmitting, by the processing hardware, the MBS downlink data packets to a plurality of fourth UEs via a second plurality of unicast data transmissions based on an identification information of the second downlink tunnel.
[0168] Example 5. A method according to any of the preceding examples, further comprising the steps of receiving, by the processing hardware, a downlink data packet from the CN via a third downlink tunnel, determining, by the processing hardware, to transmit the downlink data packet to a specific UE, and transmitting, by the processing hardware, the downlink data packet to the specific UE via a third unicast data transmission.
[0169] Example 6. A method according to any of the preceding examples, further comprising the steps of determining, by the processing hardware, a logical channel ID and a Cell Radio Network Temporary Identifier (C-RNTI) corresponding to the particular UE; generating, by the processing hardware, a protocol data unit (PDU) including the logical channel ID and the downlink data packet; generating, by the processing hardware, a DCI and a CRC of the DCI to schedule a PDSCH transmission of the PDU; and scrambling, by the processing hardware, the CRC with the C-RNTI to obtain a scrambled CRC, wherein the step of transmitting the downlink data packet via a third unicast data transmission to the particular UE includes the steps of transmitting, by the processing hardware, the DCI and the scrambled CRC on a PDCCH to the particular UE; and transmitting, by the processing hardware, a PDSCH transmission of the PDU in accordance with the DCI.
[0170] Example 7. A method according to any of the preceding examples, further comprising storing, by the processing hardware, a mapping of the tunnel identification information to one or more of a logical channel ID, a multicast radio bearer (MRB), a data radio bearer (DRB), a C-RNTI, or a group RNTI (G-RNTI).
[0171] Example 8. The method according to any of the preceding examples, further comprising: determining, by the processing hardware, a logical channel ID based on an identification information of the downlink tunnel; and generating, by the processing hardware, a protocol data unit (PDU) including the logical channel ID and the MBS downlink data packet, wherein the step of transmitting the MBS downlink data packet to the plurality of first UEs or the step of transmitting the MBS downlink data packet to the plurality of second UEs includes a step of transmitting, by the processing hardware, the PDU to the plurality of first UEs via a multicast data transmission or a step of transmitting, by the processing hardware, the PDU to the plurality of second UEs via a plurality of unicast data transmissions.
[0172] Example 9. A method according to any of the preceding examples, wherein the step of transmitting the PDU to the multiple second UEs via multiple unicast data transmissions includes the steps of: determining, by the processing hardware, multiple logical channel IDs for the multiple second UEs, respectively; generating, by the processing hardware, multiple PDUs each including one of the multiple logical channel IDs and an MBS downlink data packet; and transmitting, by the processing hardware, the multiple PDUs to the multiple second UEs via multiple unicast data transmissions.
[0173] Example 10. A method according to any of the preceding examples, further comprising: determining, by the processing hardware, a G-RNTI; generating, by the processing hardware, a downlink control information element (DCI) and a cyclic redundancy check (CRC) of the DCI to schedule a physical downlink shared channel (PDSCH) transmission of the PDU; and scrambling, by the processing hardware, the CRC with the G-RNTI to obtain a scrambled CRC, wherein transmitting the PDU to the plurality of first UEs includes transmitting, by the processing hardware, the DCI and the scrambled CRC on a physical downlink control channel (PDCCH) to the plurality of first UEs; and transmitting, by the processing hardware, a PDSCH transmission of the PDU to the plurality of first UEs in accordance with the DCI.
[0174] Example 11. A method according to any of the preceding examples, further comprising: determining, by the processing hardware, a plurality of C-RNTIs for a plurality of second UEs, respectively; generating, by the processing hardware, a plurality of DCIs and a plurality of CRCs of the DCIs to schedule a plurality of PDSCH transmissions of the PDU corresponding to each of the plurality of second UEs; and scrambling, by the processing hardware, the plurality of C-RNTIs with the respective plurality of C-RNTIs to obtain a plurality of scrambled CRCs, wherein the step of transmitting the PDUs to the plurality of second UEs via a plurality of unicast data transmissions includes transmitting, by the processing hardware, the plurality of DCIs and the plurality of scrambled CRCs on the respective plurality of PDCCHs to the plurality of second UEs; and transmitting, by the processing hardware, the plurality of PDSCH transmissions of the PDUs to the plurality of second UEs in accordance with the respective plurality of DCIs.
[0175] Example 12. A method according to any of the preceding examples, wherein the step of determining a logical channel ID includes determining, by the processing hardware, a plurality of logical channel IDs for a plurality of second UEs, respectively, the step of generating a PDU includes generating, by the processing hardware, a plurality of PDUs each including one of the plurality of logical channel IDs and an MBS downlink data packet, and the step of transmitting, by the processing hardware, a plurality of PDSCH transmissions of the plurality of PDUs to the plurality of second UEs in accordance with a respective plurality of DCIs.
[0176] Example 13. A method according to any of the preceding examples, further comprising: determining, by the processing hardware, a plurality of C-RNTIs for a plurality of second UEs, respectively; generating, by the processing hardware, a DCI and a CRC of the DCI to schedule a PDSCH transmission of the PDU; and scrambling, by the processing hardware, the CRC with the respective plurality of C-RNTIs to obtain a plurality of scrambled CRCs, wherein the step of transmitting the PDU to the plurality of second UEs via a plurality of unicast data transmissions includes transmitting, by the processing hardware, the DCI and the plurality of scrambled CRCs on a plurality of PDCCHs, respectively, to the plurality of second UEs; and transmitting, by the processing hardware, a PDSCH transmission of the PDU to the plurality of second UEs in accordance with the DCI.
[0177] Example 14. The method according to any of the preceding examples, further comprising determining, by the processing hardware, a quality of service (QoS) flow ID associated with the MBS downlink data packet, wherein determining whether to transmit the MBS downlink data packet to the plurality of UEs via unicast or multicast includes determining, by the processing hardware, based on the QoS flow ID, whether to transmit the MBS downlink data packet to the plurality of first UEs via a multicast data transmission or via a plurality of unicast data transmissions, and / or determining, by the processing hardware, based on the QoS flow ID, whether to transmit the MBS downlink data packet to the plurality of second UEs via a multicast data transmission or via a plurality of unicast data transmissions.
[0178] Example 15. The step of determining whether to transmit the MBS downlink data packet to the plurality of first UEs via a multicast data transmission or via a plurality of unicast data transmissions includes, in a first case, determining by the processing hardware to transmit the MBS downlink data packet to the plurality of first UEs via a multicast data transmission based on the QoS flow ID being a first QoS flow ID, and in a second case, determining by the processing hardware to transmit the MBS downlink data packet to the plurality of first UEs via a plurality of unicast data transmissions based on the QoS flow ID being a second QoS flow ID, and / or A method according to any of the preceding examples, wherein the step of determining whether to transmit the MBS downlink data packet to the multiple second UEs via a multicast data transmission or via multiple unicast data transmissions includes, in a third case, a step of determining, by the processing hardware, to transmit the MBS downlink data packet to the multiple second UEs via a multicast data transmission based on the QoS flow ID being a first QoS flow ID, and in a fourth case, a step of determining, by the processing hardware, to transmit the MBS downlink data packet to the multiple second UEs via one or more unicast data transmissions based on the QoS flow ID being a second QoS flow ID.
[0179] Example 16. A method according to any of the preceding examples, further comprising: determining, by the processing hardware, a quality of service (QoS) flow ID associated with the MBS downlink data packet; determining, by the one or more processors, a logical channel ID based on the QoS flow ID; and generating, by the one or more processors, a PDU including the determined logical channel ID and the MBS downlink data packet, wherein transmitting, by the processing hardware, the PDU to the multiple second UEs via multiple unicast data transmissions.
[0180] Example 17. A method according to any of the preceding examples, further comprising: configuring, by the processing hardware, one or more downlink transport layer configurations each including transport layer information for receiving MBS downlink data packets corresponding to a particular downlink tunnel, wherein the step of receiving the MBS downlink data packets from the CN includes receiving, by the processing hardware, from the CN, a downlink tunnel packet including the MBS downlink data packet and the particular transport layer information; and, in response to receiving the MBS downlink data packet via the downlink tunnel, identifying, by the processing hardware, the downlink tunnel based on the particular transport layer information and the one or more downlink transport layer configurations.
[0181] Example 18. A method in a base station for managing transmission of multicast and / or broadcast services (MBS), comprising: receiving, by processing hardware from a UE, a first request to join a first MBS session identified by a first MBS session identifier; receiving, by processing hardware from the UE, a second request to join a second MBS session identified by a second MBS session identifier; transmitting, by the processing hardware, first MBS data for the first MBS session to the UE; and transmitting, by the processing hardware, second MBS data for the second MBS session during the first MBS session to the UE.
[0182] Example 19. The method according to Example 18, further comprising: configuring, by the processing hardware, a first MBS session for transmitting the first MBS data via the first tunnel; and configuring, by the processing hardware, a second MBS session for transmitting the second MBS data via the second tunnel.
[0183] Example 20. The method according to any one of Examples 18 or 19, wherein the configuration of the first MBS session or the second MBS session includes at least one of a quality of service configuration for the first MBS session or the second MBS session, or a quality of service flow for the first MBS session or the second MBS session.
[0184] Example 21. The method according to any one of Examples 18 to 20, wherein the first tunnel configuration or the second tunnel configuration includes at least one of a transport layer address or a tunnel identifier.
[0185] Example 22. The method according to any one of Examples 18 to 21, wherein the step of configuring the first MBS session includes the step of performing, by the processing hardware, a first MBS session resource setup procedure with the CN.
[0186] Example 23. The method according to any one of Examples 18 to 22, further comprising the step of performing, by the processing hardware, a UE-specific MBS session configuration procedure with the UE.
[0187] Example 24. The method according to any one of Examples 18 to 23, wherein the step of performing a first MBS session resource setup procedure includes the steps of receiving, by the processing hardware, an MBS session resource setup request message from a core network (CN) including the first MBS session identifier, and transmitting, by the processing hardware, an MBS session resource setup response message including a transport layer configuration for the first MBS session.
[0188] Example 25. The method according to any one of Examples 18 to 24, wherein the step of performing a UE-specific MBS session configuration procedure includes the steps of: sending, by the processing hardware, to the UE, a radio resource control (RRC) reconfiguration message including a multicast radio bearer (MRB) configuration; and receiving, by the processing hardware, an RRC reconfiguration complete message from the UE.
[0189] Example 26. The method according to any one of Examples 18 to 25, wherein the UE is a first UE, and further comprising: receiving, by the processing hardware, from a second UE, a third request to join the first MBS session identified by the first MBS session identifier; and transmitting, by the processing hardware, to the second UE, first MBS data for the first MBS session.
[0190] Example 27. A base station comprising processing hardware and configured to perform a method according to any of the preceding examples.
[0191] Example 28. A method in a UE for obtaining multicast and / or broadcast service (MBS) data from multiple MBS sessions, the method comprising: sending, by processing hardware to a base station, a first request to join a first MBS session identified by a first MBS session identifier; sending, by the processing hardware to the base station, a second request to join a second MBS session identified by a second MBS session identifier; receiving, by the processing hardware from the base station, the first MBS data for the first MBS session; and receiving, by the processing hardware, from the base station, the second MBS data for the second MBS session during the first MBS session.
[0192] Example 29. The method according to Example 28, further comprising: performing, by the processing hardware, a first MBS session join procedure for a first MBS session for receiving the first MBS data via the first tunnel; and performing, by the processing hardware, a second MBS session join procedure for a second MBS session for receiving the second MBS data via the second tunnel.
[0193] Example 30. The method according to example 28 or example 29, wherein the first tunnel configuration or the second tunnel configuration includes at least one of a transport layer address or a tunnel identifier.
[0194] Example 31. The method according to any of Examples 28 to 30, further comprising: performing, by processing hardware, a UE-specific MBS session configuration procedure with the base station for each of the first MBS session and the second MBS session.
[0195] Example 32. The method according to any of Examples 28 to 31, wherein the step of performing a UE-specific MBS session configuration procedure includes the steps of receiving, by the processing hardware, from the base station, a radio resource control (RRC) reconfiguration message including a multicast radio bearer (MRB) configuration, and sending, by the processing hardware, an RRC reconfiguration complete message to the base station.
[0196] Example 33. A UE comprising processing hardware and configured to perform a method according to any of Examples 28 to 32.
[0197] The following additional considerations apply to the above discussion:
[0198] In some implementations, "message" may be used and replaced by "information element (IE)". In some implementations, "IE" may be used and replaced by "field". In some implementations, "configuration" may be replaced by "configurations" or configuration parameters. In some implementations, "MBS" may be replaced by "multicast" or "broadcast".
[0199] A user device (e.g., UE 102A or 102B) on which the techniques of this disclosure may be implemented may be any suitable device capable of wireless communication, such as a smartphone, a tablet computer, a laptop computer, a mobile game console, a point-of-sale (POS) terminal, a health management 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, or a broadband router. Furthermore, a user device may in some cases be incorporated into an electronic system such as a vehicle head unit or an advanced driver assistance system (ADAS). Still further, a user device may operate as an internet-of-things (IoT) device or a mobile internet device (MID). Depending on the type, a user device may include one or more general-purpose processors, computer-readable memory, a user interface, one or more network interfaces, one or more sensors, etc.
[0200] Some embodiments are described in this disclosure as including logic or some components or modules. The modules may be software modules (e.g., code stored on a non-transitory machine-readable medium) or hardware modules. A hardware module is a tangible unit capable of performing some operations and may be configured or arranged in a certain manner. A hardware module may comprise dedicated circuitry or logic that is 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 some operations. A hardware module may also comprise programmable logic or circuitry (e.g., as contained in a general-purpose processor or other programmable processor) that is temporarily configured by software to perform some operations. The decision to implement a hardware module in a dedicated permanently configured circuitry or in a temporarily configured circuitry (e.g., configured by software) may depend on cost and time considerations.
[0201] When implemented in software, the techniques may be provided as part of an operating system, a library used by multiple applications, a specific software application, etc. The software may be executed by one or more general-purpose processors or one or more special-purpose processors.
[0202] After reading this disclosure, those skilled in the art will appreciate still further alternative structural and functional designs for communicating MBS information through the principles disclosed herein. Thus, while specific embodiments and applications have been shown and described, it should be understood that the disclosed embodiments are not limited to the precise structures and components disclosed herein. Various modifications, changes and variations, which will be apparent to those skilled in the art, may be made in the arrangement, operation and details of the methods and apparatus disclosed herein without departing from the spirit and scope as defined in the appended claims. [Explanation of symbols]
[0203] 102UE 103UE 104 Base station 105 RAN 110 Core Network 111 EPC 112 SGW 114 MME 116 PGW 124 cells 126 cells 130 Processing Hardware 132 MBS Controller 134 Non-MBS Controller 140 Processing Hardware 142 MBS Controller 144 Non-MBS Controller 150 Processing Hardware 152 MBS Controller 154 Non-MBS Controller 160 5GC 162 (MB-)UPF 164 AMF 166 (MB-)SMF 172 CU 174 DU 202 PHY 204 MAC 206 RLC 208 EUTRA PDCP 210NR PDCP 212 SDAP 302 MBS Session 304 PDU sessions 312 DL Tunnel 314 MRB 316 QoS Flows 322 UE-specific DL and / or UL tunnels 324 DRB 402 MRB 404 DRB 412 DL Tunnel 413 UL Tunnel 422 DL logical channel 423 UL logical channel 432 UE-specific DL tunnel 433 UE-specific UL tunnel 442 DRB / DL logical channels 443 DRB / UL logical channels
Claims
1. A method in a central unit (CU) of a base station for managing multicast and unicast data transmission, comprising: receiving, by the CU, a multicast and / or broadcast service (MBS) downlink data packet from a core network (CN) via a first downlink tunnel; and transmitting, by the CU, the MBS downlink data packet to a distributed unit (DU) of the base station via a second downlink tunnel for multicasting the MBS downlink data packet to a plurality of first UEs via multicast data transmission.
2. sending, by the CU to the CN, a first transport layer configuration for the first downlink tunnel; and receiving, by the CU from the DU, a first transport layer configuration for the second downlink tunnel.
3. A method in a distributed unit (DU) of a base station for managing transmission of a multicast and / or broadcast service (MBS), comprising: receiving, by the DU, first MBS data for a first MBS session via a first downlink tunnel from a central unit (CU) of a base station; transmitting, by the DU, first MBS data for the first MBS session to a first plurality of UEs.
4. transmitting, by the DU to the CU, a first transport layer configuration for the first downlink tunnel; and optionally, receiving, by the DU, second MBS data for a second MBS session from the CU via a second downlink tunnel; transmitting the second MBS data for the second MBS session by the DU to a second plurality of UEs; and / or 4. The method of claim 3, further comprising: transmitting, by the DU to the CU, a second transport layer configuration for the second downlink tunnel.
5. configuring, by the DU, the first transport layer for transmitting the first MBS data through the first downlink tunnel; and configuring, by the DU, the second transport layer for transmitting the second MBS data through the second downlink tunnel; and optionally, The configuration of the first transport layer or the second transport layer is a quality of service configuration for the first MBS session or the second MBS session; a quality of service flow for the first MBS session or the second MBS session; A transport layer address, or Tunnel Identifier The method of claim 4, comprising at least one of the following:
6. receiving, by the DU, from a second UE, a request to join the first MBS session identified by the first MBS session identifier; and transmitting, by the DU to the second UE, first MBS data for the first MBS session.
7. The method further comprises: determining, by the DU, whether to transmit the first MBS data to the first plurality of UEs via unicast or multicast based on the identification information of the first downlink tunnel; and optionally further comprising: in response to determining that the first downlink tunnel is identified by a first identifier, transmitting, by the DU, the first MBS data to the first plurality of UEs via a multicast data transmission based on the identification information of the first downlink tunnel; and / or transmitting, by the DU, the first MBS data to a second plurality of UEs via multiple unicast data transmissions based on the identification of the first downlink tunnel. the first downlink tunnel is identified by the first identifier in a first case, the first downlink tunnel is identified by a second identifier in a second case, the multicast data transmission is a first multicast data transmission, the plurality of unicast data transmissions are a first plurality of unicast data transmissions, and in the second case, in response to determining that the first downlink tunnel is identified by the second identifier, transmitting, by the DU, the first MBS data to a third plurality of UEs via a second multicast data transmission based on the second identifier of the first downlink tunnel; and transmitting, by the DU, the first MBS data packet to a fourth plurality of UEs via a second plurality of unicast data transmissions based on the second identifier of the first downlink tunnel.
8. receiving a downlink data packet by the DU from the CU via a downlink tunnel identified by a third identifier; and transmitting, by the DU, the downlink data packet to a specific UE via a third unicast data transmission; and optionally, determining, by the DU, a logical channel ID and a Cell Radio Network Temporary Identifier (C-RNTI) corresponding to the particular UE; generating, by the DU, a protocol data unit (PDU) including the logical channel ID and the downlink data packet; generating, by the DU, a DCI and a CRC of the DCI for scheduling a PDSCH transmission of the PDU; and scrambling, by the DU, the CRC using the C-RNTI to obtain a scrambled CRC; transmitting the downlink data packet to the specific UE via the third unicast data transmission; transmitting, by the DU, the DCI and the scrambled CRC to the particular UE on a physical downlink control channel (PDCCH); and transmitting, by the DU, the PDSCH transmission of the PDU to the particular UE in accordance with the DCI.
9. By the DU, Logical channel ID, Multicast Radio Bearer (MRB), Data Radio Bearer (DRB), C-RNTI, or Group RNTI (G-RNTI) 9. The method of claim 7 or 8, further comprising the step of storing a mapping of the tunnel identification information to one or more of:
10. determining, by the DU, a logical channel ID based on the identification information of the first downlink tunnel; and generating, by the DU, a protocol data unit (PDU) including the logical channel ID and the first MBS data; and transmitting, by the DU, the PDU to the first plurality of UEs via the multicast data transmission; and / or The method further comprises: transmitting, by the DU, the PDU to the second plurality of UEs via the plurality of unicast data transmissions; and optionally, transmitting the PDU to the second plurality of UEs via the plurality of unicast data transmissions comprises: determining, by the DU, a plurality of logical channel IDs for the second plurality of UEs, respectively; generating, by the DU, a plurality of PDUs, each PDU including one of the plurality of logical channel IDs and the first MBS data; and transmitting, by the DU, the plurality of PDUs to the second plurality of UEs via the plurality of unicast data transmissions.
11. determining a G-RNTI by the DU; generating, by the DU, a DCI and a CRC of the DCI for scheduling a PDSCH transmission of the PDU; and scrambling, by the DU, the CRC using the G-RNTI to obtain a scrambled CRC; transmitting the PDU to the first plurality of UEs, transmitting, by the DU, the DCI and the scrambled CRC on a PDCCH to the first plurality of UEs; and transmitting, by the DU, the PDSCH transmission of the PDU to the first plurality of UEs according to the DCI, optionally further comprising: determining, by the DU, a plurality of C-RNTIs for the second plurality of UEs, respectively; (1) generating, by the DU, a plurality of DCIs and a plurality of CRCs of the DCIs to schedule a plurality of PDSCH transmissions of the PDU corresponding to each of the second plurality of UEs, and scrambling, by the DU, the plurality of C-RNTIs to obtain a plurality of scrambled CRCs, wherein transmitting the PDU via a plurality of unicast data transmissions to the second plurality of UEs includes transmitting, by the DU, the plurality of DCIs and the plurality of scrambled CRCs on a plurality of PDCCHs, respectively, to the second plurality of UEs, and transmitting, by the DU, the plurality of PDSCH transmissions of the PDU according to the respective plurality of DCIs to the second plurality of UEs; or (2) generating, by the DU, a DCI and a CRC of the DCI to schedule a PDSCH transmission of the PDU, and scrambling, by the DU, the CRC with the respective C-RNTIs to obtain a plurality of scrambled CRCs, wherein transmitting the PDU via the plurality of unicast data transmissions to the second plurality of UEs includes transmitting, by the DU, the DCI and the plurality of scrambled CRCs on a plurality of PDCCHs, respectively, to the second plurality of UEs, and transmitting, by the DU, the PDSCH transmission of the PDU to the second plurality of UEs in accordance with the DCI. and at least one of:
12. The step of determining the logical channel ID includes determining, by the DU, a plurality of logical channel IDs of the second plurality of UEs, respectively; The step of generating the PDU includes the step of generating, by the DU, a plurality of PDUs, each of which includes one of the plurality of logical channel IDs and the first MBS data; 12. The method of claim 11, wherein transmitting the PDSCH transmissions of the PDU comprises transmitting, by the DU, PDSCH transmissions of the PDUs to the second plurality of UEs in accordance with the DCIs, respectively.
13. determining, by the DU, a Quality of Service (QoS) flow ID associated with the first MBS data; determining whether to transmit the first MBS data to the first plurality of UEs via unicast or multicast, determining, by the DU, whether to transmit the first MBS data to the first plurality of UEs via the multicast data transmission or via the plurality of unicast data transmissions based on the QoS Flow ID; and / or determining, by the DU, whether to transmit the first MBS data to the second plurality of UEs via the multicast data transmission or via the plurality of unicast data transmissions based on the QoS flow ID; and optionally, determining whether to transmit the first MBS data to the first plurality of UEs via the multicast data transmission or via the plurality of unicast data transmissions includes: In a first case, determining, by the DU, to transmit the first MBS data to the first plurality of UEs via the multicast data transmission based on the QoS flow ID being a first QoS flow ID; In a second case, determining, by the DU, to transmit the first MBS data to the first plurality of UEs via multiple unicast data transmissions based on the QoS flow ID being a second QoS flow ID; and / or determining whether to transmit the first MBS downlink data to the second plurality of UEs via the multicast data transmission or via the plurality of unicast data transmissions, In a third case, determining, by the DU, to transmit the first MBS data to the second plurality of UEs via the multicast data transmission based on the QoS flow ID being the first QoS flow ID; and in a fourth case, determining, by the DU, to transmit the first MBS data to the second plurality of UEs via the one or more unicast data transmissions based on the QoS flow ID being the second QoS flow ID.
14. determining, by the DU, a Quality of Service (QoS) flow ID associated with the first MBS data; determining, by the DU, a logical channel ID based on the QoS flow ID; and generating, by the DU, a PDU including the determined logical channel ID and the first MBS data; transmitting the first MBS data to the second plurality of UEs; The method of claim 7, comprising transmitting, by the DU, the PDU to the second plurality of UEs via the plurality of unicast data transmissions.
15. A base station comprising processing hardware and configured to perform the method according to any one of claims 1 to 14.
Citation Information
Cited By
Method and apparatus for multicast and broadcast services
US12627950B2
Method and apparatus for multicast and broadcast services
US20240236619A1
