System information for multicast and broadcast services

Abstract

To provide a processing method for a user equipment (UE) that receives multicast broadcast service (MBS) data from a base station (BS), and also provide the user equipment and the base station.SOLUTION: In a mobile communication system 100, a UE includes a step of receiving, via a first cell, a first system information block (SIB) associated with one or more MBS services. The first SIB includes information required for the UE to receive an MBS control channel, and is a SIB of a second cell different from the first cell. The UE also includes a step of receiving, via the second cell, the MBS control channel, and a step of receiving MBS data based on the MBS control channel.SELECTED DRAWING: Figure 22

Description

[Technical Field]

[0001] (CROSS-REFERENCE TO RELATED APPLICATIONS) This application claims priority under 35 U.S.C. §119(e) to U.S. Provisional Patent Application No. 63 / 216,097, filed June 29, 2021 (the "Provisional Application"), the contents of which are incorporated herein by reference. [Background technology]

[0002] This invention is directed to 5G, the fifth generation mobile network. It is the new global wireless standard following 1G, 2G, 3G, and 4G networks. 5G enables networks designed to connect machines, objects, and devices.

[0003] The present invention more specifically relates to Multicast Broadcast Service (MBS) system information and configuration signaling, in which a user equipment (UE) receives, via a first cell, a system information block (SIB) from a base station (BS) including scheduling information for receiving MBS control configuration parameters, an MBS control channel, and an MBS traffic channel. Summary of the Invention

[0004] In one embodiment, the present invention provides a method for Multicast Broadcast Service (MBS) system information and configuration signaling. The method includes the steps of: receiving, by a user equipment (UE), from a base station (BS), a plurality of system information blocks (SIBs), each including a first SIB associated with one or more MBS services, the first SIB including scheduling information for receiving MBS control configuration parameters; receiving, via a first cell, an MBS control channel including scheduling information for receiving an MBS traffic channel; and receiving MBS data based on the scheduling information for receiving the MBS traffic channel. The method may include receiving first system information associated with the first cell, the first system information block indicating that at least one SIB associated with one or more Multicast Broadcast Service (MBS) services is applicable to the first cell.

[0005] The first system information may be based on System Information Block 1 (SIB1) and / or Residual System Information (RMSI). The first system information may be received before the first system information block (SIB), via a physical downlink shared channel, and / or via a broadcast channel. Furthermore, the first system information block (SIB) may include one or more Multicast Broadcast Service (MBS) configuration parameters. Preferably, the Multicast Broadcast Service (MBS) control channel is associated with a Multicast Control Channel (MCCH) logical channel and / or a Multicast Traffic Channel (MTCH) logical channel. The Multicast Broadcast Service (MBS) data is preferably based on the Multicast Traffic Channel (MTCH) logical channel.

[0006] The method may also include receiving Multicast Broadcast Service (MBS) notification signaling indicating a change or update to a Multicast Broadcast Service (MBS) control configuration parameter. The step of receiving the Multicast Broadcast Service (MBS) notification signaling can be based on one or more of a paging channel, a broadcast channel, and a downlink shared channel. At least one of the first system information, the first system information block (SIB), and the Multicast Broadcast Service (MBS) control channel is preferably used for transmitting the first parameter, which is beam-specific or distributed unit (DU)-specific. The base station may include a centralized unit (CU) and one or more distributed units (DUs). Preferably, one or more parameters in at least one of the first system information, the first system information block (SIB), and the Multicast Broadcast Service (MBS) control channel indicate that the first parameter is beam-specific or distributed unit (DU)-specific.

[0007] In this method, the one or more parameters may indicate one or more beam or distributed unit (DU) identifiers. Similarly, the absence of the one or more parameters indicates that the first parameters are not beam- or distributed unit (DU)-specific. At least one of the first system information, the first system information block (SIB), and the Multicast Broadcast Service (MBS) control channel may be used to transmit the first parameters that are MBS service-specific. The Multicast Broadcast Service (MBS) service may be associated with one of a Vehicle-to-Everything (V2X) service type and an Internet of Things (IoT) service type. The one or more parameters in at least one of the first system information, the first system information block (SIB), and the Multicast Broadcast Service (MBS) control channel indicate that the first parameters are MBS service-specific. The one or more parameters may indicate one or more MBS service identifiers, and the absence of the one or more parameters indicates that the first parameters are not Multicast Broadcast Service (MBS) service-specific.

[0008] In this method, at least one of the first system information, the first system information block (SIB), and the multicast and broadcast service (MBS) control channel is preferably used for transmitting a first parameter that is bandwidth portion (BWP) specific. The first cell may be associated with multiple bandwidth portions (BWP). One or more parameters in at least one of the first system information, the first system information block (SIB), and the multicast and broadcast service (MBS) control channel may indicate that the first parameter is bandwidth portion (BWP) specific. The one or more parameters may also indicate one or more bandwidth portion (BWP) identifiers. The absence of the one or more parameters may indicate that the first parameter is not bandwidth portion (BWP) specific. The first system information block (SIB) includes information regarding the availability of the first MBS service in neighboring cells, and the first cell may be a primary cell in a cell group, which may be a master cell group (MCG) provided by a master base station or a secondary cell group (SCG) provided by a secondary base station.

[0009] In one embodiment, the present invention also provides a method for Multicast Broadcast Service (MBS) system information and configuration signaling. The method includes receiving, by a user equipment (UE), a System Information Scheduling Information (SI-SchedulingInfo) information element (IE) including first scheduling information for receiving a first System Information Block (SIB) associated with one or more MBS services; receiving the first SIB based on the first scheduling information; and receiving MBS data based on the first SIB. Receiving the system information may be via a System Block 1 (SIB1) message, and receiving the remaining MBS data based on the first SIB. This may be via system information (RMSI).

[0010] In one embodiment, the present invention also provides a method for multicast broadcast service (MBS) system information and configuration signaling. The method includes receiving, by a user equipment (UE), a first MBS system information block (SIB) from a base station (BS) via a first cell, determining based on receiving the first MBS SIB that a first MBS service group or a first MBS service type is provided by the first cell, and receiving MBS data associated with the first MBS service group or the first MBS service type based on the first MBS SIB. In the method, a plurality of system information blocks (SIBs) including the first MBS SIB are multicast broadcast service (MBS) SIBs, each MBS SIB of the plurality of MBS SIBs is associated with a corresponding MBS service group or MBS service type, and the first MBS SIB is associated with the first MBS service group or the first MBS service type. More particularly, the first MBS SIB is a bitmap including a plurality of bits, each bit of which is associated with a corresponding MBS service group or MBS service type, a first bit of which is associated with the first MBS service group or MBS service type, and the determining step is based on the first bit having a first value, which is preferably 1.

[0011] In one embodiment, the present invention provides a method for multicast broadcast service (MBS) system information and configuration signaling. The method includes receiving, by a user equipment (UE), a first MBS-related system information block (SIB) from a base station (BS) via a first cell; determining, based on receiving the first MBS-related SIB, that at least one MBS service is provided by a first beam associated with the first cell; and receiving MBS data via the first beam of the first cell based on the first MBS-related SIB. Thus, the MBS-related SIB includes a bitmap including a plurality of bits, each bit of the plurality of bits being associated with a corresponding beam, and a first bit of the plurality of bits being associated with the first beam, and the determining step is based on the first bit having a first value, which may be 1. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 illustrates an example of a mobile communication system in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 2A] FIG. 1 illustrates example radio protocol stacks for the user plane and control plane in accordance with certain aspects of various exemplary embodiments of the present disclosure. [Figure 2B] FIG. 1 illustrates example radio protocol stacks for the user plane and control plane in accordance with certain aspects of various exemplary embodiments of the present disclosure. [Figure 3A] FIG. 1 illustrates an example mapping between logical channels and transport channels in the downlink, uplink, and sidelink in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 3B] FIG. 1 illustrates an example mapping between logical channels and transport channels in the downlink, uplink, and sidelink in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 3C] FIG. 1 illustrates an example mapping between logical channels and transport channels in the downlink, uplink, and sidelink in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 4A] FIG. 1 illustrates example mappings between transport channels and physical channels in the downlink, uplink, and sidelink in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 4B] FIG. 1 illustrates example mappings between transport channels and physical channels in the downlink, uplink, and sidelink in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 4C] FIG. 1 illustrates example mappings between transport channels and physical channels in the downlink, uplink, and sidelink in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 5A] FIG. 1 illustrates an example radio protocol stack for NR sidelink communications in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 5B] FIG. 1 illustrates an example radio protocol stack for NR sidelink communications in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 5C] FIG. 1 illustrates an example radio protocol stack for NR sidelink communications in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 5D] FIG. 1 illustrates an example radio protocol stack for NR sidelink communications in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 6] FIG. 1 illustrates exemplary physical signals in the downlink, uplink, and sidelink in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 7] 1A-1C illustrate examples of radio resource control (RRC) states and transitions between different RRC states in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 8] FIG. 1 illustrates an example frame structure and physical resources in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 9] 1A-1C illustrate example component carrier configurations in different carrier aggregation scenarios in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 10] 1A-1C illustrate exemplary bandwidth portion configurations and switching in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 11] FIG. 1 illustrates an exemplary four-step contention-based and contention-free random access process, in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 12] FIG. 1 illustrates an exemplary two-step contention-based and contention-free random access process, in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 13] FIG. 1 illustrates an example time and frequency structure of synchronization signals and physical broadcast channel (PBCH) blocks (SSBs) in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 14] FIG. 1 illustrates an exemplary SSB burst transmission in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 15] FIG. 1 illustrates exemplary components of a user equipment and a base station for transmission and / or reception in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 16] 1 illustrates an example MBS interest indication signaling in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 17] FIG. 1 illustrates an example system information provisioning in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 18] FIG. 1 illustrates an example process according to some aspects of some of various exemplary embodiments of the present disclosure. [Figure 19] FIG. 1 illustrates an example process according to some aspects of some of various exemplary embodiments of the present disclosure. [Figure 20] FIG. 1 illustrates an example process according to some aspects of some of various exemplary embodiments of the present disclosure. [Figure 21] FIG. 1 illustrates an example process according to some aspects of some of various exemplary embodiments of the present disclosure. [Figure 22] FIG. 1 illustrates an example process according to some aspects of some of various exemplary embodiments of the present disclosure. [Figure 23] FIG. 1 illustrates an example process according to some aspects of some of various exemplary embodiments of the present disclosure. [Figure 24] FIG. 1 illustrates an example process according to some aspects of some of various exemplary embodiments of the present disclosure. [Figure 25] FIG. 1 illustrates an example process according to some aspects of some of various exemplary embodiments of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0013] 1 illustrates an example of a mobile communication system 100 according to some aspects of some of various exemplary embodiments of the present disclosure. The mobile communication system 100 may be operated by a wireless communication system operator, such as a mobile network operator (MNO), a private network operator, a multi-system operator (MSO), an Internet of Things (IoT) network operator, etc., and may provide services such as voice, data (e.g., wireless Internet access), messaging, vehicular communication services such as vehicle-to-thing (V2X) communication services, safety services, mission-critical services, and services in residential, commercial, or industrial environments, such as IoT and Industrial IoT (IIOT).

[0014] The mobile communication system 100 can enable various types of applications with different requirements regarding latency, reliability, throughput, etc. Examples of supported applications include enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC). eMBB can support stable connections with high peak data rates and moderate rates for cell-edge users. URLLC can support applications with stringent requirements regarding latency and reliability, as well as moderate requirements regarding data rates. An exemplary mMTC application includes a network of many IoT devices that are only sporadically active and transmit small data payloads.

[0015] The mobile communication system 100 may include a radio access network (RAN) portion and a core network portion. In the example shown in FIG. 1 , a Next Generation RAN (NG-RAN) 105 and a 5G Core Network (5GC) 110 are shown as examples of a RAN and a core network, respectively. Other examples of a RAN and a core network may be implemented without departing from the scope of this disclosure. Other examples of a RAN include an Evolved Universal Terrestrial Radio Access Network (EUTRAN), a Universal Terrestrial Radio Access Network (UTRAN), etc. Other examples of a core network include an Evolved Packet Core (EPC), a UMTS Core Network (UCN), etc. The RAN implements a radio access technology (RAT) and resides between a user equipment (UE) 125 and the core network. Examples of such RATs include New Radio (NR), Long Term Evolution (LTE), also known as Evolved Universal Terrestrial Radio Access (EUTRA), Universal Mobile Telecommunications System (UMTS), etc. The RAT of the example mobile communication system 100 may be NR. The core network exists between the RAN and one or more external networks (e.g., data networks) and is responsible for functions such as mobility management, authentication, session management, bearer setup, and application of different Quality of Service (QoS). The functional layer between the UE 125 and the RAN (e.g., the NG-RAN 105) may be referred to as the Access Stratum (AS), and the functional layer between the UE 125 and the core network (e.g., the 5GC 110) may be referred to as the Non-access Stratum (NAS).

[0016] The UE 125 may include wireless transmission and reception means for communicating with one or more nodes in a RAN, one or more relay nodes, one or more other UEs, etc. Examples of UEs include, but are not limited to, smartphones, tablets, laptops, computers, wireless transmitting and / or receiving units in vehicles, V2X or vehicle-to-vehicle (V2V) devices, wireless sensors, IoT devices, IIOT devices, etc. Other names may be used for the UE, such as mobile station (MS), terminal equipment, terminal node, client device, mobile device, etc.

[0017] The RAN may include nodes (e.g., base stations) for communicating with UEs. For example, the NG-RAN 105 of the mobile communication system 100 may include nodes for communicating with the UE 125. For example, different names may be used for the RAN nodes depending on the RAT used for the RAN. A RAN node may be referred to as a Node B (NB) in a RAN using the UMTS RAT. A RAN node may be referred to as an evolved Node B (eNB) in a RAN using the LTE / EUTRA RAT. In the exemplary example of the mobile communication system 100 of FIG. 1, the node of the NG-RAN 105 may be either a Next Generation Node B (gNB) 115 or a Next Generation Evolved Node B (ng-eNB) 120. In this specification, the terms base station, RAN node, gNB, and ng-eNB may be used interchangeably. The gNB 115 may provide NR user plane and control plane protocol terminations for the UE 125. The ng-eNB 120 may provide E-UTRA user plane and control plane protocol terminations for the UE 125. The interface between the gNB 115 and the UE 125 or between the ng-eNB 120 and the UE 125 may be referred to as a Uu interface. The Uu interface may be established using a user plane protocol stack and a control plane protocol stack. For the Uu interface, the direction from the base station (e.g., the gNB 115 or the ng-eNB 120) to the UE 125 may be referred to as the downlink, and the direction from the UE 125 to the base station (e.g., the gNB 115 or the ng-eNB 120) may be referred to as the uplink.

[0018] The gNB 115 and the ng-eNB 120 may be interconnected using an Xn interface. The Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The transport network layer of the Xn-U interface may be built on Internet Protocol (IP) transport, and GPRS Tunneling Protocol (GTP) may be used on User Datagram Protocol (UDP) / IP to carry user plane protocol data units (PDUs). Xn-U may provide non-guaranteed delivery of user plane PDUs and may support data forwarding and flow control. The transport network layer of the Xn-C interface may be built on Stream Control Transport Protocol (SCTP) over IP. The application layer signaling protocol may be referred to as Xn Application Protocol (XnAP). The SCTP layer may provide guaranteed delivery of application layer messages. At the transport IP layer, point-to-point transmission may be used to deliver signaling PDUs. The Xn-C interface handles Xn interface management, context transfer, and RAN page forwarding. It can support UE mobility management including routing and dual connectivity.

[0019] The gNB 115 and ng-eNB 120 may also be connected to the 5GC 110 via an NG interface, more specifically to the Access and Mobility Management Function (AMF) 130 of the 5GC 110 via an NG-C interface, and to the User Plane Function (UPF) 135 of the 5GC 110 via an NG-U interface. The transport network layer of the NG-U interface may be built on IP transport and may carry user plane PDUs between the NG-RAN node (e.g., the gNB 115 or ng-eNB 120) and the UPF 135 using the GTP protocol over UDP / IP. The NG-U may provide non-guaranteed delivery of user plane PDUs between the NG-RAN node and the UPF. The transport network layer of the NG-C interface may be built on IP transport. SCTP may be added on top of IP for reliable transmission of signaling messages. The application layer signaling protocol may be referred to as the NG Application Protocol (NGAP). The SCTP layer may provide guaranteed delivery of application layer messages. At the transport IP layer, point-to-point transmission may be used to deliver signaling PDUs. The NG-C interface can provide the following functions: NG interface management, UE context management, UE mobility management, forwarding of NAS messages, paging, PDU session management, configuration transfer, and alert message transmission.

[0020] The gNB 115 or ng-eNB 120 performs the following functions: radio bearer control, radio admission control, connection mobility control, radio resource management functions such as dynamic allocation of resources to UEs in both uplink and downlink (e.g., scheduling), IP and Ethernet header compression of data, encryption and integrity protection, selection of AMF at UE attachment when routing to AMF cannot be determined from information provided by the UE, routing of user plane data to UPF, routing of control plane information to AMF, connection setup and release, scheduling and transmission of paging messages, system broadcasting. The 5G LTE-R can host one or more of the following: scheduling and transmission of data information (e.g., derived from AMF), measurement and measurement reporting configuration for mobility and scheduling, transport level packet marking in the uplink, session management, support for network slicing, QoS flow management and mapping to data radio bearers, support for UEs in RRC inactive state, delivery functionality for NAS messages, radio access network sharing, dual connectivity, close interaction between NR and E-UTRA, and maintaining security and radio configuration for user plane 5G system (5GS) cellular IoT (CIoT) optimization.

[0021] The AMF 130 may host one or more of the following functions: NAS signaling termination, NAS signaling security, AS security control, CN inter-node signaling for mobility between 3GPP access networks, idle mode UE reachability (including control and execution of paging retransmissions), registration area management, support for intra-system and inter-system mobility, access authentication, access authorization including verification of roaming rights, mobility management control (subscription and policy), support for network slicing, Session Management Function (SMF) selection, 5GS CIoT optimization selection.

[0022] The UPF135 performs the following functions: anchor point for intra-RAT / inter-RAT mobility (where applicable), external PDU session point for interconnection to data networks, packet routing and forwarding, packet inspection and user interface for policy rule enforcement. It may host one or more of the following: user plane parts, traffic usage reporting, uplink classifier to support routing of traffic flows to the data network, branching point to support multi-homed PDU sessions, QoS processing for the user plane, e.g., packet filtering, gating, UL / DL rate enforcement, uplink traffic validation (Service Data Flow (SDF) to QoS flow mapping), and downlink packet buffering and downlink data notification triggering.

[0023] As shown in FIG. 1, the NG-RAN 105 can support a PC5 interface between two UEs 125 (e.g., UE 125A and UE 125B). In the PC5 interface, the direction of communication between the two UEs (e.g., from UE 125A to UE 125B or vice versa) may be referred to as a sidelink. Sidelink transmission and reception over the PC5 interface may be supported when the UE 125 is within NG-RAN 105 coverage and when the UE is out of NG-RAN 105 coverage, regardless of which RRC state the UE 125 is in. Support for V2X services over the PC5 interface may be provided by NR sidelink communication and / or V2X sidelink communication.

[0024] PC5-S signaling can be used for unicast link establishment with direct communication request / accept messages. A UE can self-assign a source Layer-2 ID for a PC5 unicast link, for example, based on the V2X service type. During the unicast link establishment procedure, a UE can send its source Layer-2 ID for the PC5 unicast link to a peer UE, e.g., the UE from which the destination ID was received from a higher layer. The pair of source Layer-2 ID and destination Layer-2 ID can uniquely identify the unicast link. The receiving UE can verify that the destination ID belongs to it and accept the unicast link establishment request from the source UE. During the PC5 unicast link establishment procedure, a PC5-RRC procedure on the access stratum can be invoked for UE sidelink context establishment purposes, as well as for AS layer configuration, capability exchange, etc. PC5-RRC signaling can enable the exchange of UE capabilities and AS layer configurations, such as sidelink radio bearer configuration, between a pair of UEs with established PC5 unicast links.

[0025] NR sidelink communication can support one of three types of transmission modes (e.g., unicast transmission, groupcast transmission, and broadcast transmission) for a pair of source Layer 2 ID and destination Layer 2 ID in an AS. The unicast transmission mode can be characterized by supporting one PC5-RRC connection between peer UEs for the pair, transmitting and receiving control information and user traffic between peer UEs on the sidelink, supporting sidelink HARQ feedback, supporting sidelink transmit power control, supporting RLC acknowledged mode (AM), and detecting radio link failures for the PC5-RRC connection. The groupcast transmission can be characterized by transmitting and receiving user traffic between UEs belonging to a group on the sidelink and supporting sidelink HARQ feedback. The broadcast transmission can be characterized by transmitting and receiving user traffic between UEs on the sidelink.

[0026] NR sidelink communications may use a source Layer-2 ID, a destination Layer-2 ID, and a PC5 link identifier. The source Layer-2 ID may be a link layer identity that identifies the device or group of devices that is the sender of the sidelink communication frame. The destination Layer-2 ID may be a link layer identity that identifies the device that receives the sidelink communication frame. In some examples, the source Layer-2 ID and destination Layer-2 ID may be assigned by a management function in the core network. The source Layer-2 ID may identify the source of data in NR sidelink communications. The source Layer-2 ID may be 24 bits long and may be split into two bit strings at the MAC layer. One bit string may be the least significant 8-bit portion of the source Layer-2 ID and may be forwarded to the sender's physical layer. This may identify the intended source of data in the sidelink control information and may be used for packet filtering at the receiver's physical layer. The second bit string may be the most significant 16-bit portion of the source Layer-2 ID and may be carried in the medium access control (MAC) header. This may be used for packet filtering at the receiver's MAC layer. The destination Layer-2 ID may identify the target of data in NR sidelink communications. For NR sidelink communications, the destination Layer-2 ID may be 24 bits long and may be split into two bit strings at the MAC layer. One bit string may be the least significant 16-bit portion of the destination Layer-2 ID and may be forwarded to the sender's physical layer. This can identify the intended target of the data in the sidelink control information and can be used for packet filtering at the receiver's physical layer. The second bit string can be the MSB part (8 bits) of the destination Layer 2 ID and can be carried in the MAC header. This can be used for packet filtering at the receiver's MAC layer. The PC5 link identifier can uniquely identify a PC5 unicast link within a UE for the lifetime of the PC5 unicast link. The PC5 link identifier can be used to indicate the PC5 unicast link for which a sidelink radio link failure (RLF) declaration has been made and the PC5-RRC connection has been released.

[0027] 2A and 2B illustrate example radio protocol stacks for the user plane and control plane, respectively, in accordance with some aspects of some of the various exemplary embodiments of the present disclosure. As shown in FIG. 2A, the protocol stack for the user plane of the Uu interface (between the UE 125 and the gNB 115) includes Service Data Adaptation Protocol (SDAP) 201 and SDAP 211, Packet Data Convergence Protocol (PDCP) 202 and PDCP 212, Radio Link Control (RLC) 203 and RLC 213, MAC 204 and MAC 214, and sublayers of Layer 2 and Physical (PHY) 205 and PHY 215 layers (Layer 1 is also referred to as L1).

[0028] The PHY 205 and PHY 215 provide transport channels 244 to the MAC 204 and MAC 214 sublayers. The MAC 204 and MAC 214 sublayers provide logical channels 243 to the RLC 203 and RLC 213 sublayers. The RLC 203 and RLC 213 sublayers provide RLC channels 242 to the PDCP 202 and PCP 212 sublayers. The PDCP 202 and PDCP 212 sublayers provide radio bearers 241 to the SDAP 201 and SDAP 211 sublayers. Radio bearers may be categorized into two groups: data radio bearers (DRBs) for user plane data and signaling radio bearers (SRBs) for control plane data. The SDAP 201 and SDAP 211 sublayers provide QoS flows 240 to the 5GC.

[0029] The main services and functions of the MAC204 or MAC214 sublayer are mapping between logical channels and transport channels, multiplexing / demultiplexing of MAC Service Data Units (SDUs) belonging to one or more different logical channels to / from Transport Blocks (TBs) passed to / from the physical layer on the transport channels, scheduling information reporting, error correction with Hybrid Automatic Repeat Request (HARQ) (one HARQ entity per cell in case of Carrier Aggregation (CA)), priority handling between UEs with dynamic scheduling, priority handling between logical channels of one UE with Logical Channel Prioritization (LCP), and priority handling between overlapping resources of one UE. This includes multiple processing, and padding. A single MAC entity can support multiple numerologies, transmission timings, and cells. Mapping restrictions in logical channel prioritization control which numerologies, cells, and transmission timings a logical channel can use.

[0030] The HARQ function can guarantee delivery between peer entities at Layer 1. If the physical layer is not configured for downlink / uplink spatial multiplexing, a single HARQ process can support one TB, and if the physical layer is configured for downlink / uplink spatial multiplexing, a single HARQ process can support one or more TBs.

[0031] The RLC203 or RLC213 sublayer can support three transmission modes: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). The RLC configuration may be per logical channel independent of the numerology and / or transmission time, and automatic repeat request (ARQ) may operate with any of the numerologies and / or transmission times for which the logical channel is configured.

[0032] The main services and functions of the RLC203 or RLC213 sublayer depend on the transmission mode (e.g., TM, UM, or AM) and may include transport of upper layer PDUs, sequence numbers independent of PDCP sequence numbers (UM and AM), error correction via ARQ (AM only), segmentation (AM and UM) and resegmentation (AM only) of RLC SDUs, reassembly of SDUs (AM and UM), duplicate detection (AM only), RLC SDU discard (AM and UM), RLC re-establishment, and protocol error detection (AM only).

[0033] An automatic repeat request in the RLC203 or RLC213 sublayer may have the following characteristics: ARQ retransmits an RLC SDU or an RLC SDU segment based on an RLC status report, polling for RLC status notification may be used if required by RLC, and the RLC receiver may also trigger an RLC status notification after detecting a missing RLC SDU or an RLC SDU segment.

[0034] The main services and functions of the PDCP202 or PDCP212 sublayer may include forwarding of data (user plane or control plane), maintaining the PDCP sequence number (SN), header compression and decompression using the Robust Header Compression (ROHC) protocol, header compression and decompression using the EHC protocol, encryption and decryption, integrity protection and integrity verification, timer-based SDU discard, split bearer routing, duplication, reordering and in-order delivery, out-of-order delivery, and duplicate discarding.

[0035] The main services and functions of the SDAP 201 or SDAP 211 include mapping between QoS flows and data radio bearers, and marking QoS Flow IDs (QFIs) in both downlink and uplink packets. A single protocol entity of the SDAP may be configured for each individual PDU session.

[0036] As shown in Figure 2B, the protocol stack of the control plane of the Uu interface (between the UE 125 and the gNB 115) includes the PHY layer (Layer 1), the MAC, RLC and PDCP sublayers of Layer 2, and the RRC206 and RRC216 sublayers, as described above. The main services and functions of the RRC206 and RRC216 sublayers on the Uu interface are the broadcasting of system information related to ASs and NASs, and the transmission of system information initiated by 5GC or NG-RAN. The NAS207 and NAS227 layers are control protocols (terminated in the AMF on the network side) that perform functions such as authentication, mobility management, and security control.

[0037] Sidelink specific services and functions of the RRC sublayer over the Uu interface include configuration of sidelink resource allocation via system information or dedicated signaling, reporting of UE sidelink information, sidelink related measurement configuration and reporting, and reporting of UE assistance information for SL traffic patterns.

[0038] 3A, 3B, and 3C illustrate example mappings between logical channels and transport channels in the downlink, uplink, and sidelink, respectively, according to some aspects of some of various exemplary embodiments of the present disclosure. Different types of data transfer services may be provided by the MAC. Each logical channel type may be defined by what type of information is transferred. Logical channels may be classified into two groups: control channels and traffic channels. Control channels may be used only for the transfer of control plane information. The Broadcast Control Channel (BCCH) is a downlink channel for broadcasting system control information. The Paging Control Channel (PCCH) is a downlink channel that carries paging messages. The Common Control Channel (CCCH) is a channel for transmitting control information between a UE and a network. This channel may be used for UEs that do not have an RRC connection with the network. The Dedicated Control Channel (DCCH) is a point-to-point bidirectional channel that transmits dedicated control information between a UE and a network and may be used by UEs that have an RRC connection. The Traffic Channel may be used only for the transfer of user plane information. A dedicated traffic channel (DTCH) is a point-to-point channel dedicated to one UE for transferring user information. A DTCH can exist in both the uplink and downlink. A sidelink control channel (SCCH) is a sidelink channel for transmitting control information (e.g., PC5-RRC and PC5-S messages) from one UE to other UEs. A sidelink traffic channel (STCH) is a sidelink channel for transmitting user information from one UE to other UEs. A sidelink broadcast control channel (SBCCH) is a sidelink channel for broadcasting sidelink system information from one UE to other UEs.

[0039] Downlink transport channel types include the Broadcast Channel (BCH), the Downlink Shared Channel (DL-SCH), and the Paging Channel (PCH). The BCH can be characterized by a fixed, predefined transport format and must be broadcast throughout the coverage area of ​​a cell either as a single message or by beamforming different BCH instances. The DL-SCH can be characterized by support for HARQ, support for dynamic link adaptation by varying modulation, coding, and transmit power, the possibility of being broadcast throughout the cell, the possibility of using beamforming, support for both dynamic and semi-static resource allocation, and support for UE discontinuous reception (DRX) to enable UE power saving. The PCH can be characterized by support for HARQ, support for dynamic link adaptation by varying modulation, coding, and transmit power, the possibility of being broadcast throughout the cell, the possibility of using beamforming, support for both dynamic and semi-static resource allocation, and support for UE discontinuous reception (DRX) to enable UE power saving. It may be characterized by support for UE discontinuous reception (DRX) for UE (DRX cycle indicated by the network to the UE), a requirement for it to be broadcast throughout the coverage area of ​​the cell, either as a single message or by beamforming different BCH instances, as well as being mapped to physical resources that can also be dynamically used for traffic / other control channels.

[0040] In the downlink, the following connections may exist between logical channels and transport channels: BCCH may be mapped to BCH, BCCH may be mapped to DL-SCH, PCCH may be mapped to PCH, CCCH may be mapped to DL-SCH, DCCH may be mapped to DL-SCH, and DTCH may be mapped to DL-SCH.

[0041] Uplink transport channel types include the Uplink Shared Channel (UL-SCH) and the Random Access Channel (RACH). The UL-SCH may be characterized by the possibility of using beamforming, support for dynamic link adaptation by varying transmit power and potentially modulation and coding, support for HARQ, and support for both dynamic and quasi-static resource allocation. The RACH may be characterized by limited control information and collision risk.

[0042] In the uplink, the following connections may exist between logical channels and transport channels: CCCH may be mapped to UL-SCH, DCCH may be mapped to UL-SCH, and DTCH may be mapped to UL-SCH.

[0043] Sidelink transport channel types include the Sidelink Broadcast Channel (SL-BCH) and the Sidelink Shared Channel (SL-SCH). The SL-BCH may be characterized by a predefined transport format. The SL-SCH may be characterized by support for unicast, groupcast, and broadcast transmissions; support for both UE autonomous resource selection and scheduled resource allocation by the NG-RAN; support for both dynamic and quasi-static resource allocation when the UE is assigned resources by the NG-RAN; support for HARQ; and support for dynamic link adaptation by varying transmit power, modulation, and coding.

[0044] In the sidelink, the following connections may exist between logical channels and transport channels: SCCH may be mapped to SL-SCH, STCH may be mapped to SL-SCH, and SBCCH may be mapped to SL-BCH.

[0045] 4A, 4B, and 4C illustrate example mappings between transport channels and physical channels in the downlink, uplink, and sidelink, respectively, in accordance with some aspects of some of various exemplary embodiments of the present disclosure. Physical channels in the downlink include a physical downlink shared channel (PDSCH), a physical downlink control channel (PDCCH), and a physical broadcast channel (PBCH). The PCH and DL-SCH transport channels are mapped to the PDSCH. The BCH transport channel is mapped to the PBCH. No transport channels are mapped to the PDCCH, and downlink control information (DCI) is transmitted via the PDCCH.

[0046] The physical channel in the uplink is the Physical Uplink Shared Channel (PUSCH). The UL-SCH transport channel may be mapped to the PUSCH, and the RACH transport channel may be mapped to the PRACH. No transport channel is mapped to the PUCCH, and uplink control information (UCI) is transmitted via the PUCCH.

[0047] The sidelink physical channels include the Physical Sidelink Shared Channel (PSSCH), the Physical Sidelink Control Channel (PSCCH), the Physical Sidelink Feedback Channel (PSFCH), and the Physical Sidelink Broadcast Channel (PSBCH). The Physical Sidelink Control Channel (PSCCH) indicates the resources and other transmission parameters used by the UE for the PSSCH. The Physical Sidelink Shared Channel (PSSCH) transmits the TBs of the data itself as well as control information such as HARQ procedures and CSI feedback triggers. At least six OFDM symbols within a slot may be used for PSSCH transmission. The Physical Sidelink Feedback Channel (PSFCH) may carry HARQ feedback over the sidelink from the UE that is the intended recipient of the PSSCH transmission to the UE that performed the transmission. The PSFCH sequence may be transmitted in one PRB repeated across two OFDM symbols near the end of the sidelink resources within the slot. The SL-SCH transport channel may be mapped to the PSSCH. The SL-BCH may be mapped to the PSBCH. Transport channels are not mapped to the PSFCH, but sidelink feedback control information (SFCI) may be mapped to the PSFCH. Transport channels are not mapped to the PSCCH, but sidelink control information (SCI) may be mapped to the PSCCH.

[0048] Figures 5A, 5B, 5C, and 5D illustrate example radio protocol stacks for NR sidelink communications, respectively, in accordance with some aspects of various exemplary embodiments of the present disclosure. The AS protocol stack for the user plane at the PC5 interface (i.e., for STCH) may consist of the SDAP, PDCP, RLC, and MAC sublayers, and a physical layer. The user plane protocol stack is shown in Figure 5A. The AS protocol stack for the SBCCH at the PC5 interface may consist of the RRC, RLC, MAC sublayers, and a physical layer, as shown below in Figure 5B. To support the PC5-S protocol, PC5-S is placed above the PDCP, RLC, and MAC sublayers, and a physical layer in the control plane protocol stack for SCCH for PC5-S, as shown in Figure 5C. The AS protocol stack for the control plane for SCCH for RRC at the PC5 interface consists of the RRC, PDCP, RLC, and MAC sublayers, and a physical layer. The control plane protocol stack for SCCH for RRC is shown in Figure 5D.

[0049] Sidelink Radio Bearers (SLRBs) can be categorized into two groups: Sidelink Data Radio Bearers (SL DRBs) for user plane data and Sidelink Signaling Radio Bearers (SL SRBs) for control plane data. Separate SL SRBs using different SCCHs can be configured for PC5-RRC and PC5-S signaling, respectively.

[0050] The MAC sublayer can provide the following services and functions over the PC5 interface: radio resource selection, packet filtering, priority handling between uplink and sidelink transmissions for a given UE, and sidelink CSI reporting. Due to the restriction of logical channel prioritization in MAC, only sidelink logical channels belonging to the same destination can be associated with a destination (unicast, groupcast, etc.). For packet filtering, a SL-SCH MAC header containing both the source Layer 2 ID and the destination Layer 2 ID can be added to the MAC PDU. The logical channel identifier (LCID) contained within the MAC subheader can uniquely identify a logical channel within the combination of the source Layer 2 ID and the destination Layer 2 ID.

[0051] The services and functions of the RLC sublayer may be supported for the sidelink. Both RLC unacknowledged mode (UM) and acknowledged mode (AM) may be used for unicast transmission, while only UM may be used for groupcast or broadcast transmission. In the case of UM, only one-way transmission may be supported for groupcast and broadcast.

[0052] The services and functions of the PDCP sublayer for the Uu interface may be supported for the sidelink with some restrictions: out-of-order delivery may only be supported for unicast transmission and may not support duplication over the PC5 interface.

[0053] The SDAP sublayer can provide the following services and functions over the PC5 interface: mapping between QoS flows and sidelink data radio bearers: There can be one SDAP entity per destination for one of unicast, groupcast, and broadcast associated with the destination.

[0054] The RRC sublayer can provide the following services and functions over the PC5 interface: transfer of PC5-RRC messages between peer UEs, maintenance and release of PC5-RRC connections between two UEs, and detection of sidelink radio link failures for PC5-RRC connections based on instructions from MAC or RLC. A PC5-RRC connection may be a logical connection between two UEs for a pair of source and destination Layer-2 IDs that can be considered established after a corresponding PC5 unicast link is established. There may be a one-to-one correspondence between PC5-RRC connections and PC5 unicast links. A UE may have multiple PC5-RRC connections with one or more UEs for different pairs of source and destination Layer-2 IDs. Separate PC5-RRC procedures and messages may be used by the UE to transfer UE capabilities and sidelink configurations, including SL-DRB configurations, to the peer UE. Both peer UEs can exchange their UE capabilities and sidelink configurations using separate bidirectional procedures in both sidelink directions.

[0055] FIG. 6 illustrates exemplary physical signals in the downlink, uplink, and sidelink in accordance with some aspects of various exemplary embodiments of the present disclosure. Demodulation reference signals (DM-RSs) may be used in the downlink, uplink, and sidelink and may be used for channel estimation. DM-RSs are UE-specific reference signals that may be transmitted along with downlink, uplink, or sidelink physical channels and may be used for channel estimation and coherent detection of the physical channels. Phase tracking reference signals (PT-RSs) may be used in the downlink, uplink, and sidelink and may be used to track phase and mitigate performance loss due to phase noise. PT-RSs may be primarily used to estimate and minimize the impact of common phase error (CPE) on system performance. Due to phase noise characteristics, PT-RS signals may have low density in the frequency domain and high density in the time domain. PT-RSs may occur when configured with DM-RSs in a network configuration. Positioning reference signals (PRSs) may be used in the downlink for positioning using different positioning techniques. The PRS transmits the received signal from the base station to the local area within the receiver. The CSI-RS may be used to measure downlink transmission delays by correlating with the channel replica. The channel state information reference signal (CSI-RS) may be used in the downlink and sidelink. CSI-RS may be used for, among other things, channel state estimation, reference signal received power (RSRP) measurement for mobility and beam management, and time / frequency tracking for demodulation. While CSI-RS may be configured UE-specific, multiple users may share the same CSI-RS resource. The UE can determine CSI reports and transmit them to the base station in the uplink using the PUCCH or PUSCH. CSI reports may be carried in the sidelink MAC CE. The primary synchronization signal (PSS) and secondary synchronization signal (SSS) may be used for radio frame synchronization. The PSS and SSS may be used for cell search procedures during initial attach or for mobility purposes. The sounding reference signal (SRS) may be used in the uplink for uplink channel estimation. Similar to the CSI-RS, the SRS can serve as a QCL reference for other physical channels, such that they may be configured to be transmitted quasi-colocated with the SRS. Sidelink PSS (S-PSS) and Sidelink SSS (S-SSS) may be used in the sidelink for sidelink synchronization.

[0056] 7 illustrates example radio resource control (RRC) states and transitions between different RRC states in accordance with some aspects of various exemplary embodiments of the present disclosure. A UE may be in one of three RRC states: an RRC connected state 710, an RRC idle state 720, and an RRC inactive state 730. After power-on, the UE may be in the RRC idle state 720, and the UE may use initial access to establish a connection with the network via an RRC connection establishment procedure to perform data transfer and / or conduct a voice call. Once the RRC connection is established, the UE may be in the RRC connected state 710. The UE can transition from the RRC idle state 720 to the RRC connected state 710 or from the RRC connected state 710 to the RRC idle state 720 using an RRC connection establishment / release procedure 740.

[0057] The RRC inactive state 730 may be used to reduce the signaling load and latency resulting from frequent transitions from the RRC connected state 710 to the RRC idle state 720 when the UE transmits frequent small data. In the RRC inactive state 730, the AS context may be stored by both the UE and the gNB. This may result in a faster state transition from the RRC inactive state 730 to the RRC connected state 710. The UE may transition from the RRC inactive state 730 to the RRC connected state 710 or from the RRC connected state 710 to the RRC inactive state 730 using an RRC connection resume / deactivation procedure 760. The UE may transition from the RRC inactive state 730 to the RRC idle state 720 using an RRC connection release procedure 750.

[0058] FIG. 8 illustrates an example frame structure and physical resources according to some aspects of various exemplary embodiments of the present disclosure. Downlink, uplink, or sidelink transmissions may be organized into frames with a 10 ms duration consisting of ten 1 ms subframes. Each subframe may consist of 1, 2, 4, ... slots, and the number of slots per subframe may depend on the subcarrier spacing of the carrier on which the transmission occurs. The slot duration may be 14 symbols with a normal cyclic prefix (CP) or 12 symbols with an extended CP, and may be scaled in time depending on the subcarrier spacing used so that there are an integer number of slots in a subframe. FIG. 8 illustrates a resource grid in the time and frequency domains. Each element of the resource grid, containing one symbol in time and one subcarrier in frequency, is called a resource element (RE). A resource block (RB) may be defined as 12 consecutive subcarriers in the frequency domain.

[0059] In some examples, with non-slot-based scheduling, transmission of a packet may occur over a portion of a slot, e.g., 2, 4, or 7 OFDM symbols, which may be referred to as a minislot. Minislots may be used for low-latency applications such as URLLC and operation in unlicensed bands. In some embodiments, minislots may also be used for fast flexible scheduling of services (e.g., preemption of URLLC for eMBB).

[0060] FIG. 9 illustrates example component carrier configurations in different carrier aggregation scenarios according to some aspects of various exemplary embodiments of the present disclosure. In carrier aggregation (CA), two or more component carriers (CCs) may be aggregated. A UE can simultaneously receive or transmit on one or more CCs depending on its capabilities. CA may be supported for both contiguous and non-contiguous CCs in the same band or different bands, as illustrated in FIG. 9. The gNB and UE can communicate using a serving cell. The serving cell may be associated with at least one downlink CC (e.g., associated with only one downlink CC or associated with a downlink CC and an uplink CC). The serving cell may be a primary cell (PCell) or a secondary cell (SCell).

[0061] The UE can adjust the timing of its uplink transmission using an uplink timing control procedure. It can use a timing advance (TA) to adjust the uplink frame timing relative to the downlink frame timing. The gNB can determine the desired timing advance setting and provide it to the UE. The UE can use the provided TA to determine its uplink transmit timing relative to the UE's observed downlink receive timing.

[0062] In the RRC connected state, the gNB may be responsible for maintaining the timing advance to keep L1 synchronized. Serving cells with uplinks to which the same timing advance applies and that use the same timing reference cell are grouped into a timing advance group (TAG). A TAG may contain at least one serving cell with a configured uplink. The mapping of serving cells to TAGs may be configured by RRC. For a primary TAG, the UE may use the PCell as the timing reference cell, except for shared spectrum channel access, where an SCell may also be used as the timing reference cell in some cases. For a secondary TAG, the UE may use any of the activated SCells of this TAG as the timing reference cell and may not need to change it unless necessary.

[0063] The timing advance update may be signaled by the gNB to the UE via a MAC CE command. Such a command may restart a TAG-specific timer that may indicate whether L1 can be synchronized; when the timer is running, L1 may be considered synchronized; otherwise, L1 may be considered unsynchronized (in which case uplink transmissions may only occur on the PRACH).

[0064] A UE with single timing advance capability for CA can simultaneously receive and / or transmit multiple CCs corresponding to multiple serving cells (multiple serving cells grouped into one TAG) that share the same timing advance. A UE with multiple timing advance capability for CA can simultaneously receive and / or transmit multiple CCs corresponding to multiple serving cells (multiple serving cells grouped into multiple TAGs) with different timing advances. The NG-RAN: It may be ensured that each TAG contains at least one serving cell. A non-CA-enabled UE may receive on a single CC and transmit on a single CC corresponding to only one serving cell (one serving cell in one TAG).

[0065] The multi-carrier characteristics of the physical layer in case of CA may be exposed to the MAC layer, and one HARQ entity may be required per serving cell. When CA is configured, the UE may have one RRC connection with the network. In RRC connection establishment / re-establishment / handover, one serving cell (e.g., PCell) may provide NAS mobility information. Depending on the UE capabilities, the SCell may be configured to form a set of serving cells together with the PCell. The set of serving cells configured for the UE may consist of one PCell and one or more SCells. Reconfiguration, addition, and deletion of SCells may be performed by RRC.

[0066] In a dual connectivity scenario, a UE may be configured with multiple cells including a Master Cell Group (MCG) for communicating with a master base station, a Secondary Cell Group (SCG) for communicating with a secondary base station, and two MAC entities, one for the MCG for communicating with the master base station and one for the SCG for communicating with the secondary base station.

[0067] FIG. 10 illustrates exemplary bandwidth portion configuration and switching in accordance with some aspects of some of various exemplary embodiments of the present disclosure. A UE may be configured with one or more bandwidth portions (BWPs) 1010 in a given component carrier. In some examples, one of the one or more bandwidth portions may be active at a time. The active bandwidth portion may define the UE's operating bandwidth within the cell's operating bandwidth. For initial access, an initial bandwidth portion 1020 determined from system information may be used until the UE's configuration within the cell is received. For example, in bandwidth adaptation (BA) via BWP switching 1040, the UE's reception and transmission bandwidths may not be as large as the cell's bandwidth and may be adjusted. For example, the widths may be sequenced to change (e.g., shrink during periods of low activity to save power), the positions may move in the frequency domain (e.g., to increase scheduling flexibility), and the subcarrier spacing may be sequenced to change (e.g., to enable different services). The first active BWP 1020 may be the active BWP upon RRC (re)configuration of the PCell or activation of the SCell.

[0068] For a downlink BWP or an uplink BWP in a set of downlink or uplink BWPs, respectively, the UE may be provided with the following configuration parameters: subcarrier spacing (SCS), cyclic prefix, common RBs and a number of consecutive RBs, an index within the set of downlink or uplink BWPs by the respective BWP-Id, a set of BWP common parameters, and a set of BWP-specific parameters. A BWP may be associated with an OFDM numerology according to the subcarrier spacing and cyclic prefix configured for the BWP. For the serving cell, the UE may be provided with a default downlink BWP among the configured downlink BWPs. If the UE is not provided with a default downlink BWP, the default downlink BWP may be the initial downlink BWP.

[0069] A downlink BWP may be associated with a BWP inactivity timer. If the BWP inactivity timer associated with an active downlink BWP expires and a default downlink BWP is configured, the UE may perform a BWP switch to the default BWP. If the BWP inactivity timer associated with an active downlink BWP expires and a default downlink BWP is not configured, , the UE can perform a BWP switch to the initial downlink BWP.

[0070] 11 illustrates an exemplary four-step contention-based and contention-free random access process according to some aspects of various exemplary embodiments of the present disclosure. FIG. 12 illustrates an exemplary two-step contention-based and contention-free random access process according to some aspects of various exemplary embodiments of the present disclosure. The random access procedure can be triggered by several events, such as initial access from an RRC idle state, an RRC connection re-establishment procedure, downlink or uplink data arrival during an RRC connected state when the uplink synchronization state is "unsynchronized," uplink data arrival during an RRC connected state when no PUCCH resources are available for a scheduling request (SR), an SR failure, a request by RRC upon synchronization reconfiguration (e.g., handover), a transition from an RRC inactive state, establishing time alignment of a secondary TAG, a request for other system information (SI), beam failure recovery (BFR), and a consistent uplink listen-before-talk (LBT) failure on the PCell.

[0071] Two types of random access (RA) procedures can be supported: a four-step RA type with MSG1 and a two-step RA type with MSGA. Both types of RA procedures can support contention-based random access (CBRA) and contention-free random access (CFRA), as shown in Figures 11 and 12.

[0072] The UE can select the type of random access at the start of the random access procedure based on the network configuration. If CFRA resources are not configured, the RSRP threshold can be used by the UE to select between the 2-step RA type and the 4-step RA type. If CFRA resources for the 4-step RA type are configured, the UE can perform random access using the 4-step RA type. If CFRA resources for the 2-step RA type are configured, the UE can perform random access using the 2-step RA type.

[0073] MSG1 for the 4-step RA type may consist of a preamble on the PRACH. After MSG1 transmission, the UE may monitor for a response from the network within a configured window. For CFRA, a dedicated preamble for MSG1 transmission is allocated by the network, and upon receiving a random access response (RAR) from the network, the UE may terminate the random access procedure as shown in FIG. 11. For CBRA, upon receiving the random access response, the UE may transmit MSG3 using the uplink grant scheduled in the random access response and monitor contention resolution as shown in FIG. 11. If contention resolution is not successful after MSG3 (re)transmission, the UE may return to MSG1 transmission.

[0074] The MSGA for the two-step RA type may include a preamble in the PRACH and a payload in the PUSCH. After the MSGA transmission, the UE can monitor for a response from the network within a configured window. For CFRA, a dedicated preamble and PUSCH resources may be configured for MSGA transmission, and upon receiving a network response, the UE can terminate the random access procedure as shown in FIG. 12. For CBRA, if contention resolution is successful upon receiving a network response, the UE can terminate the random access procedure as shown in FIG. 12. On the other hand, if a fallback indication is received in MSGB, the UE can perform MSG3 transmission using the uplink grant scheduled with the fallback indication and monitor contention resolution. If contention resolution is not successful after MSG3 (re)transmission, the UE can return to MSGA transmission.

[0075] FIG. 13 illustrates an exemplary time and frequency structure of a synchronization signal and physical broadcast channel (PBCH) block (SSB) according to some aspects of various exemplary embodiments of the present disclosure. An SS / PBCH block (SSB) may consist of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS), each occupying one symbol and 127 subcarriers (e.g., subcarrier numbers 56 through 182 in FIG. 13), and a PBCH spanning three OFDM symbols and 240 subcarriers, but leaving an unused portion in the center of one symbol for the SSS, as shown in FIG. 13. The possible time locations of the SSBs within a half-frame may be determined by the subcarrier spacing, and the periodicity of the half-frames in which the SSBs are transmitted may be configured by the network. During a half-frame, different SSBs may be transmitted in different spatial directions (i.e., using different beams spanning the cell's coverage area).

[0076] The PBCH may be used to carry the Master Information Block (MIB), which is used by the UE during cell search and initial access procedures. The UE may first decode the PBCH / MIB to receive other system information. The MIB may provide the UE with the parameters necessary to acquire System Information Block 1 (SIB1), more specifically, the information necessary to monitor the PDCCH for scheduling the PDSCH carrying SIB1. Additionally, the MIB may indicate cell barring status information. The MIB and SIB1 may be collectively referred to as Minimum System Information (SI), and SIB1 may be referred to as Remaining Minimum System Information (RMSI). The other System Information Blocks (SIBs) (e.g., SIB2, SIB3, ..., SIB10, and SIBpos) may be referred to as Other SI. Other SI may be broadcast periodically on the DL-SCH, may be broadcast on demand on the DL-SCH (e.g., upon request from a UE in RRC idle, RRC inactive, or RRC connected state), or may be sent in a dedicated manner to UEs in RRC connected state on the DL-SCH (e.g., upon request, if configured by the network, from a UE in RRC connected state, or if the UE has an active BWP for which a common search space is not configured).

[0077] FIG. 14 illustrates an exemplary SSB burst transmission according to some aspects of various exemplary embodiments of the present disclosure. An SSB burst may include N SSBs, where each SSB of the N SSBs may correspond to a beam. The SSB burst may be transmitted according to a periodicity (e.g., an SSB burst duration). During a contention-based random access process, a UE may perform a random access resource selection process, in which the UE first selects an SSB before selecting an RA preamble. The UE may select an SSB with an RSRP above a configured threshold. In some embodiments, the UE may select any SSB if no SSB with an RSRP above a configured threshold is available. A set of random access preambles may be associated with the SSB. After selecting an SSB, the UE may select a random access preamble from the set of random access preambles associated with the SSB and transmit the selected random access preamble to initiate the random access process.

[0078] In some embodiments, a beam among the N beams may be associated with a CSI-RS resource. The UE may measure the CSI-RS resource and select a CSI-RS with an RSRP above a configured threshold. The UE may select a random access preamble corresponding to the selected CSI-RS and transmit the selected random access process to initiate the random access process. If there is no random access preamble associated with the selected CSI-RS, the UE The selector 100 may select a random access preamble corresponding to the quasi-co-located SSB with the selected CSI-RS.

[0079] In some embodiments, based on UE measurements of CSI-RS resources and UE CSI reports, the base station can determine a transmission configuration indication (TCI) state and indicate the TCI state to the UE, which can use the indicated TCI state for reception of downlink control information (e.g., via a PDCCH) or data (e.g., via a PDSCH). The UE can use the indicated TCI state to use an appropriate beam for reception of data or control information. The indication of the TCI state may be using an RRC configuration or a combination of RRC signaling and dynamic signaling (e.g., via a MAC Control Element (MAC CE) and / or based on the value of a field in the downlink control information that schedules downlink transmissions). The TCI state can indicate a quasi-co-location (QCL) relationship between a downlink reference signal, such as a CSI-RS, and a DM-RS associated with a downlink control or data channel (e.g., a PDCCH or PDSCH, respectively).

[0080] In some embodiments, a UE may be configured with a list of up to M TCI-state configurations using physical downlink shared channel (PDSCH) configuration parameters to decode a PDSCH according to a detected PDCCH with DCI for the UE and a given serving cell, where M may depend on the UE capabilities. Each TCI-State may include parameters for configuring a QCL relationship between one or two downlink reference signals and a DM-RS port of a PDSCH, a DM-RS port of a PDCCH, or a CSI-RS port of a CSI-RS resource. The quasi-co-location relationship may be configured by one or more RRC parameters. The quasi-co-location type corresponding to each DL RS can take one of the following values: "QCL-TypeA": {Doppler shift, Doppler spread, mean delay, delay spread}, "QCL-TypeB": {Doppler shift, Doppler spread}, "QCL-TypeC": {Doppler shift, mean delay}, and "QCL-TypeD": {Spatial Rx parameters}. The UE may receive an activation command (eg, MAC CE) used to map the TCI state to a codepoint in the DCI field.

[0081] FIG. 15 illustrates exemplary components of a user equipment and a base station for transmission and / or reception in accordance with some aspects of various exemplary embodiments of the present disclosure. All or a subset of the blocks and functions in FIG. 15 may reside in or be performed by the base station 1505 and the user equipment 1500. The antenna 1510 may be used to transmit or receive electromagnetic signals. The antenna 1510 may include one or more antenna elements and may enable different input / output antenna configurations, including a multiple-input multiple-output (MIMO) configuration, a multiple-input single-output (MISO) configuration, and a single-input multiple-output (SIMO) configuration. In some embodiments, the antenna 1510 may enable a massive MIMO configuration with tens or hundreds of antenna elements. The antenna 1510 may enable other multi-antenna techniques, such as beamforming. In some examples, depending on the capabilities of the UE 1500 or the type of the UE 1500 (e.g., a low-complexity UE), the UE 1500 may support only a single antenna.

[0082] The transceiver 1520 can communicate bidirectionally over the wireless links described herein via the antenna 1510. For example, the transceiver 1520 may represent a wireless transceiver in a UE and may communicate bidirectionally with a wireless transceiver in a base station, or vice versa. The transceiver 1520 modulates packets and provides the modulated packets to the antenna 1510 for transmission, and receives packets from the antenna 1510. The signal may include a modem for demodulating the received packets.

[0083] The memory 1530 may include RAM and ROM. The memory 1530 may store computer-readable computer-executable code 1535 including instructions that, when executed, cause the processor to perform various functions described herein. In some examples, the memory 1530 may include a basic input / output system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices, among other things.

[0084] The processor 1540 may include a hardware device having processing capabilities (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some examples, the processor 1540 may be configured to operate a memory using a memory controller. In other examples, the memory controller may be integrated into the processor 1540. The processor 1540 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1530) to cause the UE 1500 or the base station 1505 to perform various functions.

[0085] The central processing unit (CPU) 1550 may perform basic arithmetic, logic, control, and input / output (I / O) operations specified by computer instructions in the memory 1530. The user equipment 1500 and / or base station 1505 may include additional peripheral components such as a graphics processing unit (GPU) 1560 and a global positioning system (GPS) 1570. The GPU 1560 is dedicated circuitry for rapid manipulation and modification of the memory 1530 to accelerate the processing performance of the user equipment 1500 and / or base station 1505. The GPS 1570 may be used to enable location-based services or other services, for example, based on the geographic location of the user equipment 1500.

[0086] In some examples, MBS services may be enabled via single-cell transmission. MBS may be transmitted with single-cell coverage. One or more multicast / broadcast control channels (e.g., MCCH) and one or more multicast / broadcast data channels (e.g., MTCH) may be mapped to the DL-SCH. Scheduling may be performed by the gNB. Multicast / broadcast control channel and multicast / broadcast data channel transmissions may be indicated by a logical channel-specific RNTI on the PDCCH. In some examples, a one-to-one mapping between a service identifier, such as a temporary mobile group identifier (TMGI), and a RAN-level identifier, such as a group identifier (G-RNTI), may be used for reception of the DL-SCH to which the multicast / broadcast data channel may be mapped. In some examples, a single transmission may be used for the DL-SCH associated with the multicast / broadcast control channel and / or multicast / broadcast data channel transmissions, and HARQ or RLC retransmissions may not be used, and / or RLC unacknowledged mode (RLC UM) may be used. In other examples, some feedback (e.g., HARQ feedback or RLC feedback) may be used for transmission over a multicast / broadcast control channel and / or a multicast / broadcast data channel.

[0087] In some examples, for a multicast / broadcast data channel, the following scheduling information may be provided on the multicast / broadcast control channel: Multicast / broadcast data channel schedule These are the ring cycle, the multicast / broadcast data channel on duration (e.g., the period the UE waits to receive the PDCCH after waking up from DRX), and the multicast / broadcast data channel inactivity timer (e.g., the period the UE waits for a successful decoding of the PDCCH indicating the DL-SCH to which this multicast / broadcast data channel is mapped until a failure to re-enter DRX).

[0088] In some examples, one or more UE identities may be associated with the MBS transmission. The one or more identities may include at least one of one or more first RNTIs identifying a multicast / broadcast control channel transmission and one or more second RNTIs identifying a multicast / broadcast data channel transmission. The one or more first RNTIs identifying a multicast / broadcast control channel transmission may include a single-cell RNTI (SC-RNTI, although other names may be used). The one or more second RNTIs identifying a multicast / broadcast data channel transmission may include a G-RNTI (nG-RNTI or other names may be used).

[0089] In some examples, one or more logical channels may be associated with the MBS transmission. The one or more logical channels may include a multicast / broadcast control channel. The multicast / broadcast control channel may be a point-to-multipoint downlink channel used to transmit MBS control information from the network to the UE for one or several multicast / broadcast data channels. This channel may be used by UEs that receive or are interested in receiving the MBS. The one or more logical channels may include a multicast / broadcast data channel. This channel may be a point-to-multipoint downlink channel for transmitting MBS traffic data from the network.

[0090] In some examples, procedures may be used by a UE to notify the RAN that the UE is receiving or is interested in receiving MBS service(s) via an MBS radio bearer, and if so, to notify the 5G RAN about the priority of MBS over unicast reception or MBS service(s) reception in receive-only mode. An example is shown in FIG. 16. The UE may transmit a message (e.g., an MBS Interest Indication message) informing the RAN that the UE is receiving / interested in receiving, or no longer receiving / not interested in receiving, an MBS service. The UE may transmit the message, for example, based on receiving one or more messages (e.g., SIB messages or unicast RRC messages) from the network indicating one or more MBS service area identifiers for the current and / or neighboring carrier frequencies.

[0091] In some examples, a UE may consider an MBS service to be part of an MBS service of interest if the UE is able to receive the MBS service (e.g., via a single-cell point-to-multipoint mechanism), and / or the UE is receiving or is interested in receiving this service via a bearer associated with the MBS service, and / or one session of this service is in progress or about to start, and / or at least one of one or more MBS service identifiers indicated by the network is of interest to the UE.

[0092] In some examples, the control information for receiving the MBS service is transmitted to a specific logical channel. The MBS service information may be provided on the MCCH (e.g., the MCCH). The MCCH may carry one or more configuration messages indicating ongoing MBS sessions as well as (corresponding) information regarding when each session may be scheduled, e.g., scheduling period, scheduling window, and starting offset. The one or more configuration messages may provide information regarding neighboring cells transmitting MBS sessions that may be ongoing in the current cell. In some examples, a UE may receive a single MBS service at a time or multiple MBS services in parallel.

[0093] In some examples, MCCH information (e.g., information transmitted in a message transmitted over the MCCH) may be transmitted periodically using a configurable repetition period. The MCCH transmission (and associated radio resources and MCS) may be indicated on the PDCCH.

[0094] In some examples, changes to the MCCH information may occur in a specific radio frame / subframe / slot and / or a modification period may be used. For example, within a modification period, the same MCCH information may be transmitted multiple times as defined by its scheduling (based on the repetition period). The modification period boundary may be defined by an SFN value, where SFN mod m=0, where m is the number of radio frames that include the modification period. The modification period may be configured by SIB or RRC signaling.

[0095] In some examples, when the network changes (part of) the MCCH information, it may notify the UE of the change in the first subframe / slot that can be used for MCCH transmission in the repetition period. Upon receiving the change notification, the UE interested in receiving the MBS service can acquire the new MCCH information starting from the same subframe / slot. The UE may apply the previously acquired MCCH information until it acquires the new MCCH information.

[0096] In one example, the system information block (SIB) may include information necessary to obtain control information related to the transmission of the MBS. The information may include at least one of one or more discontinuous reception (DRX) parameters for monitoring scheduling information of the control information-related transmission of the MBS, a scheduling period and an offset of the scheduling information of the control information-related transmission of the MBS, a modification period for modifying the content of the control information-related transmission of the MBS, repetition information for repetition of the control information-related transmission of the MBS, etc.

[0097] In one example, the information element (IE) may provide configuration parameters indicating, for example, a list of ongoing MBS sessions transmitted over one or more bearers for each MBS session, one or more associated RNTIs (e.g., G-RNTI, other names may be used), and scheduling information. The configuration parameters may include at least one of one or more timer values ​​(e.g., inactivity timer or on-duration timer) for discontinuous reception (DRX), an RNTI for scheduling and scrambling transmission of a multicast / broadcast traffic channel (e.g., MTCH, other names may be used), information regarding the ongoing MBS sessions, one or more power control parameters, one or more scheduling periodicity and / or offset values ​​for one or more MBS traffic channels, information regarding a list of neighboring cells, etc.

[0098] In some examples, a gNB or ng-eNB may include logical nodes that host some, all, or a portion of user plane and / or control plane functions. For example, a gNB Central Unit (gNB-CU) may be a logical node that hosts the RRC, SDAP, and PDCP protocols of a gNB, or the RRC and PDCP protocols of an en-gNB, which controls the operation of one or more gNB-DUs. The gNB-DU may terminate the F1 interface connected to the gNB-CU. The gNB distributed unit (gNB-DU) may be a logical node that hosts the RLC, MAC, and PHY layers of a gNB or en-gNB, and its operation may be partially controlled by the gNB-CU. One gNB-DU can support one or multiple cells. One cell may be supported by only one gNB-DU. The gNB-DU may terminate the F1 interface connected to the gNB-CU. The gNB-CU-Control Plane (gNB-CU-CP) may be a logical node that hosts the control plane portion of the RRC and PDCP protocols of the gNB-CU for an en-gNB or gNB. The gNB-CU-CP may terminate the E1 interface connected to the gNB-CU-UP and the F1-C interface connected to the gNB-DU. The gNB-CU-User Plane (gNB-CU-UP) may be a logical node that hosts the user plane portion of the PDCP protocol of the gNB-CU for the en-gNB and the user plane portion of the PDCP and SDAP protocols of the gNB-CU for the gNB. The gNB-CU-UP may terminate the E1 interface connected to the gNB-CU-CP and the F1-U interface connected to the gNB-DU.

[0099] In some examples, the system information (SI) may include a MIB and several SIBs, which may be divided into a minimum SI and other SIs. An example of system information provisioning is shown in FIG.

[0100] In some examples, the minimum SI may include basic information required for initial access and information for obtaining any other SI. In some examples, the minimum SI may include an MIB and SIB1. The MIB may include additional system information, such as cell barring status information and required physical layer information for cells required to receive the CORESET#0 configuration. The MIB may be broadcast periodically on the BCH. SIB1 may define the scheduling of other system information blocks and may include information required for initial access. SIB1, also referred to as the remaining minimum SI (RMSI), may be broadcast periodically on the DL-SCH or may be transmitted exclusively to RRC_CONNECTED UEs on the DL-SCH.

[0101] In some examples, the Other SI may encompass all SIBs not broadcast with the minimum SI. These SIBs may be broadcast periodically on the DL-SCH, broadcast on demand on the DL-SCH (e.g., upon request from a UE in RRC_IDLE, RRC_INACTIVE, or RRC_CONNECTED), or transmitted in a dedicated manner to an RRC_CONNECTED UE on the DL-SCH (e.g., upon request, if configured by the network, from a UE in RRC_CONNECTED, or if the UE has an active BWP with no common search space configured). In some examples, the Other SI may include SIB2-SIB14 and SIBpos. One or more additional SIBs, including SIBs related to one or more MBS services, may be defined / used depending on the exemplary embodiment. In some examples, SIB2 may include cell reselection information primarily related to the serving cell, SIB3 may include information about the serving frequency and intra-frequency neighboring cells related to cell reselection (including frequency-common cell reselection parameters and cell-specific reselection parameters), SIB4 may include information about other NR frequencies and inter-frequency neighboring cells related to cell reselection (including frequency-common cell reselection parameters and cell-specific reselection parameters) that may also be used for NR idle / inactive measurements, SIB5 may include information about E-UTRA frequencies and E-UTRA neighboring cells related to cell reselection (including frequency-common cell reselection parameters and cell-specific reselection parameters), and SIB6 may include the ETWS primary notification. For example, SIB7 may contain ETWS secondary notifications, SIB8 may contain CMAS warning notifications, SIB9 may contain information about GPS time and Coordinated Universal Time (UTC), SIB10 may contain the Human Readable Network Name (HRNN) of the NPN listed in SIB1, SIB11 may contain information about idle / inactive measurements, and SIBpo may contain positioning assistance data. For sidelink, other SIs may include SIB12, which may contain information related to NR sidelink communications, SIB13, which may contain information related to SystemInformationBlockType21 for V2X sidelink communications, and SIB14, which may contain information related to SystemInformationBlockType26 for V2X sidelink communications.

[0102] In some instances, for a cell / frequency considered for camping by the UE, the UE may not need to obtain the minimum SI content of that cell / frequency from another cell / frequency layer, although this does not preclude the UE from applying a stored SI from a previously visited cell.

[0103] In some examples, if the UE cannot determine the full contents of a cell's minimum SI by receiving from that cell, the UE may consider the cell to be barred.

[0104] In some instances in the case of bandwidth adaptation (BA), the UE may acquire SI on an active BWP.

[0105] In some examples, the MIB may be mapped onto the BCCH and carried on the BCH, and other SI messages may be mapped onto the BCCH and then dynamically carried on the DL-SCH. The scheduling of the SI message portion of the other SI may be indicated by SIB1.

[0106] In some examples, for UEs in RRC_IDLE and RRC_INACTIVE, a request for Other SI can trigger a random access procedure, and MSG3 can contain an SI request message unless the requested SI is associated with a subset of PRACH resources, in which case MSG1 is used to indicate the requested Other SI. If MSG1 is used, the minimum granularity of the request can be one SI message (i.e., a set of SIBs), and one RACH preamble and / or PRACH resource can be used to request multiple SI messages, and the gNB acknowledges the request in MSG2. If MSG3 is used, the gNB can acknowledge the request in MSG4.

[0107] In some examples, for an RRC_CONNECTED UE, a request for Other SI may be sent to the network in a dedicated manner (i.e., via UL-DCCH) if configured by the network, and the granularity of the request may be one SIB. The gNB may respond with an RRCReconfiguration containing the requested SIB(s). It may be the network's choice to decide which requested SIBs may be delivered in a dedicated or broadcast manner.

[0108] In some examples, Other SI may be broadcast for a specific period with a configurable periodicity, or may be broadcast when requested by the UE in RRC_IDLE / RRC_INACTIVE / RRC_CONNECTED.

[0109] In some instances, in order for a UE to be allowed to camp on a cell, the UE must In some cases, the UE may obtain the minimum SI content from other cells. There may be cells in the system that do not broadcast the minimum SI, and therefore the UE cannot camp on them.

[0110] In some examples, the modification of the system information may occur in a specific radio frame, i.e., the concept of a modification period is used. The system information may be transmitted multiple times with the same content within a modification period, as defined by its scheduling. The modification period may be configured by the system information.

[0111] In some examples, when the network changes (part of) the system information, it may first notify the UE about this change, i.e., this may occur throughout a modification period. In the next modification period, the network may send updated system information. Upon receiving the change notification, the UE may acquire new system information from the start of the next modification period. The UE may apply the previously acquired system information until the UE acquires the new system information.

[0112] In some examples, the system information (SI) can be divided into an MIB and several SIBs and posSIBs. The MIB can be transmitted on the BCH with a periodicity (e.g., 80 ms) and repetition within 80 ms, and can contain parameters necessary to acquire SIB1 from the cell. SIB1 can be transmitted on the DL-SCH. SIBs other than SIB1 and posSIB can be carried in a System Information (SI) message, which can be transmitted on the DL-SCH. The SIBs and posSIBs can be mapped to different SI messages. Each SI message can be transmitted within a regularly occurring time-domain window (called an SI-window, which has the same length for all SI messages). Each SI message can be associated with an SI-window, and the SI-windows of different SI messages may not overlap. That is, within one SI-window, corresponding SI messages are transmitted. An SI message can be transmitted multiple times within an SI-window. Any SIB or posSIB, except for SIB1, can be configured to be cell-specific or area-specific using the SIB1 indication. While a cell-specific SIB may be applicable within a cell that can provide the SIB, an area-specific SIB is applicable within an area called an SI area, which may consist of one or more cells and may be identified by a systemInformationAreaID.

[0113] In some examples, the mapping of SIBs to SI messages may be configured in a schedulingInfoList, while the mapping of posSIBs to SI messages may be configured in a posSchedulingInfoList. Each SIB may be included in a single SI message, and each SIB and posSIB may be included at most once in that SI message.

[0114] In some examples, for a UE in RRC_CONNECTED, the network may provide system information via dedicated signaling using an RRCReconfiguration message, for example, if the UE has an active BWP without a common search space configured to monitor system information, paging, or upon request from the UE.

[0115] In some examples, for PSCell and SCell, the network may provide the required SI by dedicated signaling, i.e., in the RRCReconfiguration message. The UE may obtain the MIB of the PSCell to obtain the SFN timing of the SCG (which may be different from the MCG). When the associated SI is changed, the network can release and add the associated SCell. For a PSCell, the required SI can be changed by Reconfiguration using Sync.

[0116] In some examples, SIB1 may contain information relevant when evaluating whether a UE is allowed to access a cell and may define scheduling of other system information, which may exclude radio resource configuration information common to all UEs and information applicable to unified access control.

[0117] In some examples, the systemInformationAreaID IE, if present, may indicate the system information area to which the cell belongs. Any SIB with areaScope within the SI is considered to belong to this systemInformationAreaID. The systemInformationAreaID may be unique within a PLMN.

[0118] In some examples, the IE SI-SchedulingInfo may be included in SIB1. The IE SI-SchedulingInfo may contain information necessary for obtaining SI messages. The field areaScope may indicate that the SIB is area-specific. If the field is not present, the SIB may be cell-specific. The field si-BroadcastStatus may indicate whether the SI message is broadcast or not. A change in si-BroadcastStatus may not result in a system information change notification in a short message sent in P-RNTI over DCI. If the value of this indication is set to broadcast, it may be valid until the end of the BCCH modification period. The field si-Periodicity may indicate the periodicity of the SI message in radio frames. The field ra-AssociationPeriodIndex may indicate the index of an association period in si-RequestPeriod during which the UE can send an SI request for SI message(s) corresponding to this SI-RequestResources using the preamble indicated by ra-PreambleStartIndex and each opportunity indicated by ra-ssb-OccasionMaskIndex. The field ra-PreambleStartIndex is N>=1 if N SSBs are associated with the RACH opportunity, and for the i-th SSB (i=0,...,N-1), the preamble with preamble index = ra-PreambleStartIndex+i is used for the SI request. If N<1, the preamble with preamble index = ra-PreambleStartIndex is used for the SI request. The si-RequestConfig field may indicate the configuration of Msg1 resources that the UE uses to request SI messages with si-BroadcastStatus set to notBroadcasting. The field systemInformationAreaID, if present, may indicate the system information area to which the cell belongs.Any SIB with an areaScope within the SI is considered to belong to this systemInformationAreaID. The systemInformationAreaID may be unique within a PLMN.

[0119] The exemplary embodiments enhance MBS system and configuration signaling to support selective MBS transmission across cells and / or beams and / or bandwidth portions (BWPs) for multiple MBS services.

[0120] In some examples, depending on the type of MBS data and its QoS and traffic characteristics and available spectrum, multicast or broadcast transmission may be It may consist of different bands, different carriers or bandwidth portions.

[0121] In some examples, the transmission of MBS data may take into account the presence and / or number of interested users (e.g., users interested in the MBS service or one or more particular MBS services) within the coverage area.

[0122] In some examples, based on the distribution and presence of users' demand / interest and / or other considerations, MBS data may be selectively transmitted in some base stations, cells, or selective distribution units (DUs), or beams within a cell.

[0123] In some examples, different MBS data types may be configured for transmission on different spectrums, carriers, or BWPs based on characteristics of the MBS data, mixing capabilities of the target device, and / or other considerations.

[0124] In some examples, the MBS signaling design may support the configuration of MBS transmissions on a select set of beams and / or DUs and / or cells of a gNB.

[0125] In some examples, the MBS signaling design may support the configuration of MBS transmissions on one or more carriers or bandwidth portions.

[0126] In some examples, 5G networks may offer a variety of broadcast and multicast services and use cases, sometimes targeting different groups of users and devices. In some examples, a service-type or group-targeted MBS control signaling design may be such that unnecessary processing by UEs that are not interested in or affected by such signaling can be avoided. In some examples, an MBS signaling design may support service-type or group-targeted signaling such that unnecessary processing by unaffected UEs can be avoided. An example is shown in FIG. 18.

[0127] In this disclosure, MBS configuration may be used to refer to MBS radio bearer and control configurations, e.g., MBS QoS, MCCH / MTCH configuration, SPS configuration, etc. MBS notification may be an initial signaling to inform the UE about upcoming detailed MBS session / configuration changes or updates.

[0128] In some examples, MBS signaling configuration information may be grouped into multiple parts and provided to the UE at different stages. An example is shown in FIG. 19. For example, System Information Block 1 (SIB1) and / or the Remaining Minimum System Information (RMSI) may indicate whether MBS-related system information (SIB) is applicable to the cell. The MBS SIB may provide configuration and scheduling information for MBS control signaling, for example, carrying the MCCH logical channel. The MBS notification signaling may be used to indicate changes to the MBS configuration. The MBS control signaling may provide configuration and scheduling information for the MBS traffic channel, for example, carrying the MTCH logical channel. The MBS data / traffic transmission may carry the MTCH logical channel.

[0129] In some examples, at least for broadcast, Service System Information (SIB) messaging may be used to provide MBS control configuration and MCCH type messaging to provide MBS scheduling information.

[0130] In some instances, at least for broadcast services, the system information frame The MBS control signaling transmission, e.g., MCCH configuration, can be provided to the UE using the framework. The MBS SIB may be treated as Other System Information (OSI), and thus its transmission schedule and on-demand request information may be provided as part of SIB1 or RMSI.

[0131] In some examples, the presence of such information in the RMSI may be an implicit indication that the node supports some MBS services. In some examples, a base station may be associated with multiple carriers and / or beamforming. In some examples, MBS may be provided on some carriers or bandwidth portions (BWPs) of carriers, and transmission may also be selective on some distributed units of beams within the gNB. In some examples, to support MBS, SIB1 / RMSI may be extended to include information regarding scheduling and request information for the MBS SIB. For example, sibType n may be added to SI-SchedulingInfo along with its scheduling and request information.

[0132] In some examples, a variety of different MBS services for different use cases targeting different users may be provided. For example, one type of MBS service may target IoT and V2X devices, while another type may be video broadcasting. In one example, to enable SI optimization for MBS UEs, the network may be notified in advance about which MBS service types are supported, and the types may be pre-configured or indicated by higher layer service announcements.

[0133] In some examples, the RMSI may include information about MBS service groups / types configured and supported by the RAN, and the MBS service type indexes, e.g., A, B, and C, may be defined by higher layer signaling or may be pre-configured. In some examples, different reservation sib types may be used for different MBS service groups / types configured in a cell. In some examples, a bitmap code may be included in the sibType specific portion of the RMSI of the MBS-SIB, and each bit set to 1 may indicate that the corresponding MBS Service type is configured in the cell.

[0134] In some examples, different MBS services may be expected to be provided in a multi-beam base station. In some cases, MBS may be provided in several beams or sectors / DUs of a gNB selectively based on the presence of interested users. In such cases, UEs interested in MBS may need to be informed in advance about such subset of beams / DUs so that they can take it into account when performing any cell reselection as needed to continue receiving MBS data.

[0135] In some examples, in a multi-sector or multi-beam base station, the MBS-SIB scheduling information in the RMSI can include information about the set of sectors and beams over which the MBS is transmitted. In the absence of this information, the UE can assume that the MBS is provided in all beams within the sector, not necessarily across different sectors of the gNB. In some examples, the systemInformationAreaID in the RMSI can be used and extended, which can define the multi-cell area over which the sibType applies, to encode a subcell-level area, e.g., a subset of sectors / beams within a base station. In some examples, a separate bitmap can be defined and can include the MBS SIB scheduling information to encode the area over which the MBS SIB applies.

[0136] In some examples, for broadcast services, the UE can perform DU / beam selection based on the UE's interest. For multicast services, the UE can select a beam and DU based on the UE's interest and can indicate to the gNB whether to move to a DU / beam to which the target multicast data is not currently transmitted. In some examples, the RMSI can include information about the carrier / BWP and beam on which the MBS SIB is transmitted. In the absence of such information, the UE can assume that the MBS SIB is transmitted on the same BWP and that the RMSI is received across all SSB beams.

[0137] In some examples, the RMSI information for the MBS SIB may be simplified, and the distinction between different MBS services may be postponed to be included only in the MBS SIB. An example is shown in Figure 20. In this case, an MBS user, regardless of which MBS service group it is interested in or is receiving, obtains and processes the comprehensive MBS SIB before checking whether the target service is included.

[0138] In some examples, the RMSI may be simple and general without referring to a specific service type or beam, and may defer such information to the MBS SIB itself. The MBS SIB may be transmitted on the carrier on which the RMSI is transmitted. While such an approach offers greater flexibility than the RMSI approach, it may require all UEs interested in any MBS service to locate and process the MBS SIB transmitted on one or more beams to discover whether it contains information about the availability of their target MBS service. The RMSI approach is less flexible but simpler and may be used when all MBS services are provided similarly across all DUs and beams of the gNB.

[0139] In some examples, using parameters in the MBS SIB, the gNB can list MBS transmission configurations for one or more MBS service groups, e.g., provide scheduling information for multiple MCCHs.

[0140] In some examples, information regarding spatial transmission patterns across sectors, DUs, or beams of a gNB may be included in the MBS SIB for each MBS service group.

[0141] In some examples, to assist UEs in cell selection and reselection while maintaining MBS service continuity, the network may provide information about the availability of MBS services in neighboring cells with the same or different configurations. The nodes broadcasting such MBS configurations may not be directly involved in MBS scheduling and transmission.

[0142] In some examples, the MBS-SIB may include information regarding the availability of each MBS service group in neighboring cells and if the same configuration applies to such neighboring cells.

[0143] In some examples, in dual connectivity and carrier aggregation, the MBS SIB may be transmitted by a master PCell that provides MBS configuration to all MBS-supporting cells in the master cell group and / or secondary cell group.

[0144] In some examples, 5G MBS services may be provided on multiple carriers and different BWPs. MBS data transmissions may be on the same BWP as the MCCH. Therefore, the MCCH may include a BWP for the MTCH if it is different from the one on which the MCCH is transmitted.

[0145] In some examples, the MBS SIB may include MBS control information, such as information about the carrier and BWP on which the MCCH is transmitted. If such information does not exist for an MBS type / group, the UE may assume that the MCCH and MCCH change notification for that MBS type / group are transmitted on the same BWP on which the MBS SIB was received.

[0146] In some examples, different UEs may be configured with different bandwidth portions (BWPs) based on their capabilities, power saving optimization, and the mix of services each uses at a given time. A UE may be expected to operate on one of its configured BWPs, called the active BWP. The network may transmit MBS control information, such as the MCCH, on multiple BWPs or carriers to ensure that all target UEs receive the MBS control scheduling information.

[0147] In some examples, MBS data for different service groups may be transmitted over different BWPs, while the corresponding MBS control signaling may be transmitted over a common BWP, e.g., on the MCCH. An example is shown in FIG.

[0148] In some examples, MBS configuration updates, e.g., MCCH change notifications, may be transmitted across multiple cells, beams, and across multiple paging occasions and bandwidth portions as necessary to ensure that all target UEs receive such notifications.

[0149] In some examples, MBS scheduling information, eg, the MCCH, may include a pointer to the BWP in which the MTCH is transmitted and may be transmitted across multiple BWPs or carriers.

[0150] System information may be required to schedule control information and data for multicast and broadcast services. Existing system information, including system information blocks (SIBs), may not be sufficient for flexible scheduling of MBS data. To enable more flexible scheduling of MBS data, existing system information and corresponding procedures need to be enhanced. Exemplary embodiments may enhance existing system information and corresponding procedures to enable more flexible scheduling of MBS data.

[0151] In the exemplary embodiment shown in FIG. 22, the UE may receive system information while in an RRC state. In some examples, the RRC state may be an RRC_CONNECTED state. In some examples, the RRC state may be an RRC_IDLE state or an RRC_INACTIVE state. The system information received by the UE may include multiple SIBs, including a first SIB. The first SIB may be associated with one or more MBS services and / or may be used to schedule data associated with the one or more MBS services. The first SIB may include and / or indicate scheduling information (e.g., indicating used radio resources) for receiving MBS control / MBS control configuration parameters.

[0152] In some examples, the UE may receive first system information (e.g., via MIB / BCH, or via SIB1, or via RMSI (remaining system information)) indicating that at least one SIB associated with one or more MBS services is applicable and / or is received via the first cell (e.g., before receiving the first SIB). The UE may receive the system information via a broadcast channel (e.g., in the case of an MIB) or via a physical downlink shared channel (e.g., in the case of SIB1 or RMSI). In some examples, the first cell may be a primary cell. In some examples, the first cell may be a primary cell or a secondary cell. In some examples, the first cell may be a primary cell, and the information in the first SIB may be applicable to other cells (e.g., secondary cells in the same cell group, e.g., an MCG or SCG). The UE may receive the system information via a broadcast channel (e.g., in the case of an MIB) or via a physical downlink shared channel (e.g., in the case of SIB1 or RMSI). In some examples, the first system information may include scheduling information and / or indicate radio resources for receiving the first SIB.

[0153] The UE can receive the MBS control channel based on the scheduling information included in and / or indicated by the first SIB. In some examples, the MBS control channel may be a multicast control channel (MCCH). The MBS control channel may be used to transmit scheduling information (e.g., indicating radio resources) for receiving MBS data, e.g., a transport block including one or more logical channels associated with one or more MBS services. The MBS control channel may include and / or indicate scheduling information for receiving a multicast traffic channel (MTCH). In some examples, the MBS control channel may further include and / or indicate one or more MBS configuration parameters. The UE can receive the MBS data based on the scheduling information indicated by the MBS control channel.

[0154] In some examples, the base station may include a centralized unit (CU) and one or more distributed units (DUs). In some examples, the first cell may be associated with multiple beams. In some examples, first system information (e.g., received via MIB, SIB1, or RMSI) associated with one or more MBS services and / or the first SIB, and / or information indicated by the MBS control channel may be used to transmit a first parameter that is beam-specific or distributed unit (DU)-specific. For example, the first system information (e.g., received via MIB, SIB1, or RMSI) associated with one or more MBS services and / or one or more parameters in the first SIB, and / or information indicated by the MBS control channel may indicate that the first parameter is beam-specific or distributed unit (DU)-specific. For example, the one or more parameters may indicate one or more DU identifiers and / or one or more beam identifiers. In some examples, the first system information (e.g., received via a MIB or SIB1 or RMSI) associated with one or more MBS services and / or the absence of one or more parameters in the first SIB, and / or the information indicated by the MBS control channel may indicate that the first parameter is not beam-specific or DU-specific and / or that the first parameter is applicable to all beams and / or all DUs of the base station of the first cell.

[0155] In some examples, first system information (e.g., received via MIB, SIB1, or RMSI) and / or the first SIB, and / or information indicated by an MBS control channel associated with one or more MBS services may be used to transmit MBS service-specific first parameters. The MBS services may be associated with V2X or IoT. For example, the first system information (e.g., received via MIB, SIB1, or RMSI) and / or the one or more parameters in the first SIB, and / or information indicated by an MBS control channel associated with one or more MBS services may indicate that the first parameters are MBS service-specific. For example, the one or more parameters may be used to transmit MBS service-specific first parameters for one or more MBS services. In some examples, the first system information (e.g., received via a MIB or SIB1 or RMSI) related to one or more MBS services and / or the absence of one or more parameters in the first SIB and / or the information indicated by the MBS control channel may indicate that the first parameter is not MBS service specific and / or that the first parameter is applicable to all MBS services (e.g., in one or more MBS services associated with the first SIB).

[0156] In some examples, the first cell may include and / or be associated with multiple bandwidth portions (BWPs). In some examples, first system information (e.g., received via a MIB, SIB1, or RMSI) associated with one or more MBS services and / or the first SIB, and / or information indicated by an MBS control channel may be used to transmit a first parameter that is bandwidth portion (BWP) specific. For example, the first system information (e.g., received via a MIB, SIB1, or RMSI) associated with one or more MBS services and / or one or more parameters in the first SIB, and / or information indicated by an MBS control channel may indicate that the first parameter is BWP-specific. For example, the one or more parameters may indicate one or more BWP identifiers. In some examples, the first system information (e.g., received via a MIB or SIB1 or RMSI) associated with one or more MBS services and / or the absence of one or more parameters in the first SIB and / or information indicated by the MBS control channel may indicate that the first parameter is not BWP-specific and / or that the first parameter is applicable to all BWPs of the first cell.

[0157] In some examples, the first SIB may indicate information about the availability of the first MBS service in a neighboring cell, and the UE may utilize this information in a handover and / or cell reselection procedure.

[0158] In some examples, the UE may further receive MBS notification signaling indicating changes and / or updates to one or more MBS configuration parameters associated with one or more MBS services. The reception of MBS data may be further based on the changed and / or updated MBS configuration parameters indicated by the MBS notification signaling. The MBS notification signaling may be received via system information (e.g., via a broadcast channel) or may be paged via a downlink shared channel.

[0159] In the exemplary embodiment shown in FIG. 23, the UE may receive system information (e.g., via SIB1 or RMSI) while in an RRC state. In some examples, the RRC state may be an RRC_CONNECTED state. In some examples, the RRC state may be an RRC_IDLE state or an RRC_INACTIVE state. The system information received by the UE may include an SI-SchedulingInfo information element (IE). The SI-SchedulingInfo IE may include scheduling information for one or more SIBs, including the first SIB. The first SIB may be associated with and / or include information associated with one or more MBS services. The UE may receive the first SIB based on the scheduling information included in the SI-SchedulingInfo IE. The UE may utilize the information included in the first SIB and, based on the first SIB, receive MBS data associated with an MBS service of the one or more MBS services.

[0160] In the exemplary embodiment shown in FIG. 24, the UE may receive one or more SIBs including a first MBS SIB via the first cell while in an RRC state. In some examples, the RRC state may be an RRC_CONNECTED state. In some examples, the RRC state may be an RRC_IDLE state or an RRC_INACTIVE state. In response to receiving the first MBS SIB and based thereon, the UE may determine that a first MBS service group or an MBS service type is provided by the first cell. In some examples, the first SIB may include parameters for receiving MBS data associated with the first MBS service group or the first MBS service type. The UE may receive MBS data associated with the first MBS service group or the first MBS service type based on the first MBS SIB.

[0161] In some examples, the plurality of SIBs including the first MBS SIB may be associated with an MBS service and / or may be referred to as MBS SIBs. Each MBS SIB in the plurality of MBS SIBs may be associated with a corresponding MBS service group or MBS service. The first MBS SIB may be associated with the first MBS service group or the first MBS service type, and the UE may determine, based on receiving the first MBS SIB, that the first MBS service group or the first MBS service type is provided by the first cell.

[0162] In some examples, the first MBS SIB may include a bitmap including a plurality of bits. Each bit of the plurality of bits may be associated with a corresponding MBS service type or MBS service group. A first bit of the plurality of bits may be associated with the first MBS service type or the first MBS service group, and the UE may determine that the first MBS service type or the first MBS service group is provided by the first cell based on the first bit having a first value (e.g., 1).

[0163] In the exemplary embodiment shown in FIG. 25, the UE may receive one or more SIBs including a first MBS-related SIB via the first cell while in an RRC state. In some examples, the RRC state may be an RRC_CONNECTED state. In some examples, the RRC state may be an RRC_IDLE state or an RRC_INACTIVE state. In response to receiving the first MBS-related SIB, and based thereon, the UE may determine that an MBS service is provided by the first cell. In some examples, the first SIB may include parameters for receiving MBS data associated with the first beam. The UE may receive the MBS data associated with the first beam based on the first MBS SIB.

[0164] In some examples, the first MBS SIB may include a bitmap including a plurality of bits. Each bit in the plurality of bits may be associated with a corresponding beam. A first bit of the plurality of bits may be associated with the first beam, and the UE may determine that the MBS service is provided by the first beam based on the first bit having a first value (e.g., 1).

[0165] In an exemplary embodiment, a user equipment (UE) can receive from a base station (BS) a plurality of system information blocks (SIBs) including a first SIB associated with one or more MBS services, the first SIB including scheduling information for receiving MBS control configuration parameters. The UE can receive an MBS control channel including scheduling information for receiving an MBS traffic channel via the first cell. The UE may receive the MBS data based on the scheduling information.

[0166] In some examples, the UE may receive first system information associated with the first cell, where the first system information may indicate that at least one system information block (SIB) associated with one or more multicast broadcast service (MBS) services is applicable to the first cell. In some examples, the first system information may be based on system information block 1 (SIB1). In some examples, the first system information may be based on remaining system information (RMSI). In some examples, the first system information may be received before the first system information block (SIB). In some examples, receiving the first system information may be via a physical downlink shared channel. In some examples, receiving the first system information may be via a broadcast channel.

[0167] In some examples, the first system information block (SIB) further includes one or more multicast broadcast service (MBS) configuration parameters.

[0168] In some examples, a Multicast Broadcast Service (MBS) control channel may be associated with a Multicast Control Channel (MCCH) logical channel.

[0169] In some examples, the Multicast Broadcast Service (MBS) traffic channel may be associated with a Multicast Traffic Channel (MTCH) logical channel. In some examples, receiving the Multicast Broadcast Service (MBS) data may be based on the Multicast Traffic Channel (MTCH) logical channel.

[0170] In some examples, the UE may receive Multicast Broadcast Service (MBS) notification signaling indicating a change or update to a Multicast Broadcast Service (MBS) control configuration parameter. In some examples, receiving the Multicast Broadcast Service (MBS) notification signaling may be based on one or more of a paging channel, a broadcast channel, and a downlink shared channel.

[0171] In some examples, at least one of the first system information, the first system information block (SIB), and the multicast broadcast service (MBS) control channel may be used for transmission of a first parameter that is beam-specific or distributed unit (DU)-specific. In some examples, the base station may include a centralized unit (CU) and one or more distributed units (DUs). In some examples, one or more parameters in at least one of the first system information, the first system information block (SIB), and the multicast broadcast service (MBS) control channel may indicate that the first parameter is beam-specific or distributed unit (DU)-specific. In some examples, the one or more parameters may indicate one or more beam or distributed unit (DU) identifiers. In some examples, the absence of the one or more parameters may indicate that the first parameter is not beam-specific or distributed unit (DU)-specific.

[0172] In some examples, at least one of the first system information, the first system information block (SIB), and the Multicast Broadcast Service (MBS) control channel may be used for transmission of the first parameter that is MBS service specific. The service may be associated with one of a vehicle-to-everything (V2X) service type and an Internet of Things (IoT) service type. In some examples, the one or more parameters in at least one of the first system information, the first system information block (SIB), and the Multicast Broadcast Service (MBS) control channel may indicate that the first parameter is MBS service-specific. In some examples, the one or more parameters may indicate one or more MBS service identifiers. In some examples, the absence of the one or more parameters may indicate that the first parameter is not Multicast Broadcast Service (MBS) service-specific.

[0173] In some examples, at least one of the first system information, the first system information block (SIB), and the multicast and broadcast service (MBS) control channel may be used for transmission of a first parameter that is bandwidth portion (BWP) specific. In some examples, the first cell may be associated with multiple bandwidth portions (BWPs). In some examples, one or more parameters in at least one of the first system information, the first system information block (SIB), and the multicast and broadcast service (MBS) control channel may indicate that the first parameter is bandwidth portion (BWP) specific. In some examples, the one or more parameters may indicate one or more bandwidth portion (BWP) identifiers. In some examples, the absence of the one or more parameters may indicate that the first parameter is not bandwidth portion (BWP) specific.

[0174] In some examples, the first system information block (SIB) may include information regarding availability of the first MBS service in a neighboring cell.

[0175] In some examples, the first cell may be a primary cell in a cell group. In some examples, the cell group may be a master cell group (MCG) provided by a master base station. In some examples, the cell group may be a secondary cell group (SCG) provided by a secondary base station.

[0176] In an example embodiment, a user equipment (UE) can receive system information including a system information scheduling information (SI-SchedulingInfo) information element (IE) including first scheduling information for receiving a first system information block (SIB) associated with one or more MBS services. The UE can receive the first SIB based on the first scheduling information. The UE can receive MBS data based on the first SIB.

[0177] In some examples, receiving the system information may be via a System Block 1 (SIB1) message.

[0178] In some examples, receiving the system information may be via residual system information (RMSI).

[0179] In an exemplary embodiment, a user equipment (UE) may receive a first MBS system information block (SIB) from a base station (BS) via a first cell. The UE may determine, based on receiving the first MBS SIB, that a first MBS service group or a first MBS service type is provided by the first cell. The UE may receive MBS data associated with the first MBS service group or the first MBS service type based on the first MBS SIB.

[0180] In some examples, the plurality of system information blocks (SIBs) including the first MBS SIB may be Multicast Broadcast Service (MBS) SIBs. Each MBS SIB among the plurality of MBS SIBs may be associated with a corresponding MBS service group or MBS service type. The first MBS SIB may be associated with the first MBS service group or the first MBS service type.

[0181] In some examples, the first MBS SIB may include a bitmap including a plurality of bits. Each bit of the plurality of bits may be associated with a corresponding MBS service group or MBS service type. A first bit of the plurality of bits may be associated with the first MBS service group or MBS service type. The determination may be based on the first bit having a first value. In some examples, the first value may be 1.

[0182] In an example embodiment, a user equipment (UE) may receive a first MBS-related system information block (SIB) from a base station (BS) via a first cell. The UE may determine, based on receiving the first MBS-related SIB, that MBS data is provided by a first beam associated with the first cell. The UE may receive the MBS data via the first beam of the first cell based on the first MBS-related SIB.

[0183] In some examples, the MBS-related SIB may include a bitmap including a plurality of bits. Each bit in the plurality of bits may be associated with a corresponding beam. A first bit of the plurality of bits may be associated with a first beam. The determination may be based on the first bit having a first value. In some examples, the first value may be 1.

[0184] The exemplary blocks and modules described in this disclosure with respect to various exemplary embodiments may be implemented or performed using a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. Examples of general-purpose processors include, but are not limited to, a microprocessor, any conventional processor, controller, microcontroller, or state machine. In some examples, a processor may be implemented using a combination of devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration).

[0185] The functions described in this disclosure may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. Instructions or code may be stored on or transmitted to a computer-readable medium to implement the functions. Other examples for implementing the functions disclosed herein are also within the scope of this disclosure. Implementation of the functions may be via physically co-located or distributed elements (e.g., in various locations), including being distributed such that some of the functions are implemented in different physical locations.

[0186] Computer-readable media include, but are not limited to, non-transitory computer storage media. Non-transitory storage media may be accessed by a general-purpose or special-purpose computer. Examples of non-transitory storage media include, but are not limited to, random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage, etc. Non-transitory media include, but are not limited to, It may be used to carry or store desired program code means (e.g., instructions and / or data structures) and may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. In some examples, the software / program code may be transmitted from a remote source (e.g., a website, a server, etc.) using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave. In such examples, coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are within the definition of medium. Combinations of the above examples are also within the scope of computer-readable media.

[0187] As used in this disclosure, the use of the term "or" in a list of items indicates an inclusive list. A list of items can begin with a phrase such as "at least one" or "one or more." For example, a list of at least one of A, B, or C includes A or B or C or AB (i.e., A and B) or AC or BC or ABC (i.e., A and B and C). Also, as used in this disclosure, the phrase "based on" preceding a list of conditions should not be interpreted as "based only on" the set of conditions, but rather as "based at least in part on" the set of conditions. For example, a result described as "based on condition A" can be based on both condition A and condition B without departing from the scope of this disclosure.

[0188] As used herein, the terms "comprise," "include," or "contain" may be used interchangeably, have the same meaning, and should be construed as inclusive and open-ended. The terms "comprise," "include," or "contain" may be used before a list of elements to indicate that at least all of the listed elements in the list are present, but that other elements not in the list may also be present. For example, if A contains B and C, then both {B, C} and {B, C, D} are within the scope of A.

[0189] The present disclosure, in connection with the accompanying drawings, describes exemplary configurations that do not represent every example that may be implemented or every configuration within the scope of the present disclosure. The term "exemplary" should not be interpreted as "preferred" or "advantageous compared to other examples," but rather as "an example, instance, or example." By reading this disclosure, including the description of the embodiments and drawings, those skilled in the art will understand that the technology disclosed herein may be implemented using alternative embodiments. Those skilled in the art will understand that embodiments, or specific features of the embodiments described herein, can be combined to arrive at yet other embodiments for implementing the technology described in this disclosure. Thus, the present disclosure is not limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. 1. A method for processing a user equipment (UE) for receiving multicast broadcast service (MBS) data from a base station (BS), comprising: receiving, via a first cell, a first system information block (SIB) associated with one or more MBS services, the first SIB being an SIB of a second cell different from the first cell, the first SIB including information necessary for the UE to receive an MBS control channel; receiving the MBS control channel via the second cell; receiving MBS data based on the MBS control channel; The first SIB indicates information regarding configuration information specific to a bandwidth portion (BWP); method.

2. receiving information indicating that the first SIB is a SIB of the second cell; The method of claim 1.

3. the MBS control channel is associated with a Multicast Control Channel (MCCH) logical channel; The method of claim 1.

4. receiving MBS notification signaling indicating a change or update to a configuration parameter of the MBS control channel; The method of claim 1.

5. receiving the MBS notification signaling is based on one or more of a paging channel, a broadcast channel, and a downlink shared channel; The method of claim 4.

6. the first cell is a cell in a master cell group (MCG) provided by a master base station; The method of claim 1.

7. The first cell is a cell in a second cell group (SCG) provided by a secondary base station; The method of claim 1.

8. A method for a base station (BS) transmitting multicast broadcast service (MBS) data to a user equipment (UE), comprising: transmitting, via a first cell, a first system information block (SIB) associated with one or more MBS services, the first SIB being an SIB of a second cell different from the first cell, the first SIB including information necessary for the UE to receive an MBS control channel; transmitting the MBS control channel via the second cell; transmitting MBS data based on the MBS control channel; The first SIB indicates information regarding configuration information specific to a bandwidth portion (BWP); method.

9. A user equipment (UE) for receiving multicast broadcast service (MBS) data from a base station (BS), comprising: means for receiving, via a first cell, a first system information block (SIB) associated with one or more MBS services, the first SIB being an SIB of a second cell different from the first cell, the first SIB including information necessary for the UE to receive an MBS control channel; means for receiving the MBS control channel via the second cell; means for receiving MBS data based on the MBS control channel; Including, The first SIB indicates information regarding configuration information specific to a bandwidth portion (BWP); User equipment.

10. A base station (BS) for transmitting Multicast Broadcast Service (MBS) data to a user equipment (UE), comprising: means for transmitting, via a first cell, a first system information block (SIB) associated with one or more MBS services, the first SIB being an SIB of a second cell different from the first cell, the first SIB including information necessary for the UE to receive an MBS control channel; means for transmitting the MBS control channel via the second cell; means for transmitting MBS data based on the MBS control channel; Including, The first SIB indicates information regarding configuration information specific to a bandwidth portion (BWP); Base station.

Images