Channel state information feedback for multicast broadcast services

Abstract

To provide a suitable CSI reporting method for MBS services.SOLUTION: A system, a method, and an apparatus for wireless communications are provided. User equipment (UE) receives one or more messages. The one or more messages include first configuration parameters for channel state information, reference signal (CSI-RS) measurement, and CSI report in a first radio resource control (RRC) state. The one or more messages also include second configuration parameters for the CSI-RS measurement and the CSI report in a second RRC state. The UE transmits a first CSI report, based on the first configuration parameters, when the UE is in the first RRC state. The UE transmits a second CSI report, based on the second configuration parameters, when the UE is in the second RRC state.SELECTED DRAWING: Figure 20

Description

[Technical field]

[0001] The present disclosure relates to a method for channel state information feedback. [Background technology]

[0002] Generally described, computing devices and communication networks can be used to exchange information. In a typical application, a computing device can request / transmit data to another computing device via a communication network. More specifically, computing devices can use a wireless communication network to exchange information or establish a communication channel.

[0003] A wireless communications network may include a wide variety of devices that include components for accessing the wireless communications network or that access the wireless communications network, and such devices may utilize the wireless communications network to facilitate interaction with other devices that can access the wireless communications network or to facilitate interaction over the wireless communications network with devices that utilize other communications networks. Summary of the Invention

[0004] In some embodiments of the present disclosure, a method for providing user equipment (UE) feedback is provided, the method including receiving, by a UE, one or more messages including one or more first configuration parameters for a first UE feedback in a radio resource control (RRC) connected state and one or more second configuration parameters for a second UE feedback in an RRC idle state or an RRC inactive state, transmitting, by the UE, the first UE feedback based on the one or more first configuration parameters when the UE is in the RRC connected state, and transmitting, by the UE, the second UE feedback based on the one or more second configuration parameters when the UE is in the RRC idle state or when the UE is in the RRC inactive state.

[0005] Some embodiments of the present disclosure provide a method for providing user equipment (UE) feedback associated with a multicast broadcast service (MBS), including receiving, by the UE, one or more configuration parameters for UE feedback associated with the MBS, determining, by the UE, a first timing for transmission of the UE feedback associated with the MBS based on the one or more configuration parameters, and dropping the UE feedback associated with the MBS from transmission at the first timing when the first timing for the UE feedback conflicts with a second timing for an uplink channel or an uplink signal.

[0006] In some embodiments of the present disclosure, a user equipment (UE) for a mobile communication network is provided, the UE including: a memory storing instructions; and a processor configured to execute the instructions, whereby the UE receives one or more messages, the one or more messages including one or more first configuration parameters for a first UE feedback in a Radio Resource Control (RRC) connected state, and one or more second configuration parameters for a second UE feedback in an RRC idle state or an RRC inactive state; and when the UE is in an RRC connected state: Transmitting first UE feedback based on the one or more first configuration parameters, and transmitting second UE feedback based on the one or more second configuration parameters when the UE is in an RRC idle state or when the UE is in an RRC inactive state.

[0007] In some embodiments of the present disclosure, a user equipment (UE) for a mobile communication network is provided, the UE including a memory storing instructions and a processor configured to execute the instructions to receive one or more configuration parameters for UE feedback associated with an MBS, determine a first timing for transmission of the UE feedback associated with the MBS based on the one or more configuration parameters, and drop the UE feedback associated with the MBS from transmission at the first timing when the first timing for the UE feedback conflicts with a second timing for an uplink channel or an uplink signal.

[0008] In some embodiments of the present disclosure, a base station for a mobile communication system is provided, the base station including a memory storing instructions and a processor configured to execute the instructions, to transmit one or more messages to a user equipment (UE), the one or more messages including one or more first configuration parameters for a first UE feedback in a radio resource control (RRC) connected state and one or more second configuration parameters for a second UE feedback in an RRC idle state or an RRC inactive state, receive the first UE feedback from the UE when the UE is in an RRC connected state, and receive the second UE feedback from the UE when the UE is in an RRC idle state or when the UE is in an RRC inactive state.

[0009] In some embodiments of the present disclosure, a base station for a mobile communication system is provided, the base station including a memory storing instructions and a processor configured to execute the instructions, whereby the base station is configured to transmit to a user equipment (UE) one or more configuration parameters for UE feedback associated with a multicast broadcast service (MBS), the UE being configured to determine a first timing for transmission of the UE feedback associated with the MBS based on the one or more configuration parameters, and to drop the UE feedback associated with the MBS from transmission at the first timing when the first timing for the UE feedback conflicts with a second timing for an uplink channel or an uplink signal.

[0010] In some embodiments of the present disclosure, a system for mobile communications is provided, including a base station configured to transmit one or more messages including one or more first configuration parameters for a first UE feedback in a radio resource control (RRC) connected state and one or more second configuration parameters for a second UE feedback in an RRC idle state or an RRC inactive state, and a user equipment (UE) configured to receive the one or more messages, transmit the first UE feedback based on the one or more first configuration parameters when the UE is in an RRC connected state, and transmit the second UE feedback based on the one or more second configuration parameters when the UE is in an RRC idle state or when the UE is in an RRC inactive state.

[0011] In some embodiments of the present disclosure, a system for mobile communications is provided, the system including: a base station configured to transmit one or more configuration parameters for UE feedback associated with a Multicast Broadcast Service (MBS); or a user equipment (UE) configured to receive a plurality of configuration parameters, determine a first timing for transmission of UE feedback associated with the MBS, and drop the UE feedback associated with the MBS from transmission at the first timing when the first timing of the UE feedback conflicts with a second timing of the uplink channel or uplink signal.

[0012] In some embodiments of the present disclosure, a non-transitory computer-readable medium is provided. The non-transitory computer-readable medium stores a set of instructions executable by at least one processor of a user equipment (UE) in a mobile communication system to perform a method. The method includes receiving one or more messages, the one or more messages including one or more first configuration parameters for a first UE feedback in a Radio Resource Control (RRC) connected state and one or more second configuration parameters for a second UE feedback in an RRC idle state or an RRC inactive state, transmitting the first UE feedback based on the one or more first configuration parameters when the UE is in the RRC connected state, and transmitting the second UE feedback based on the one or more second configuration parameters when the UE is in the RRC idle state or when the UE is in the RRC inactive state.

[0013] In some embodiments of the present disclosure, a non-transitory computer-readable medium is provided. The non-transitory computer-readable medium stores a set of instructions executable by at least one processor of a user equipment (UE) in a mobile communication system to perform a method. The method includes receiving, by the UE, one or more configuration parameters for UE feedback associated with a multicast broadcast service (MBS), determining, by the UE, a first timing for transmission of the UE feedback associated with the MBS based on the one or more configuration parameters, and dropping the UE feedback associated with the MBS from transmission at the first timing when the first timing for the UE feedback conflicts with a second timing for an uplink channel or an uplink signal.

[0014] In some embodiments of the present disclosure, a non-transitory computer-readable medium is provided. The non-transitory computer-readable medium stores a set of instructions executable by at least one processor of a base station in a mobile communication system to perform a method. The method includes transmitting one or more messages to a user equipment (UE), the one or more messages including one or more first configuration parameters for a first UE feedback in a radio resource control (RRC) connected state and one or more second configuration parameters for a second UE feedback in an RRC idle state or an RRC inactive state, receiving the first UE feedback from the UE when the UE is in an RRC connected state, and receiving the second UE feedback from the UE when the UE is in an RRC idle state or when the UE is in an RRC inactive state.

[0015] In some embodiments of the present disclosure, a non-transitory computer-readable medium is provided. The non-transitory computer-readable medium stores a set of instructions executable by at least one processor of a base station in a mobile communication system to perform a method. The method includes transmitting, to a user equipment (UE), one or more configuration parameters for UE feedback associated with a multicast broadcast service (MBS), the UE determining a first timing for transmission of the UE feedback associated with the MBS based on the one or more configuration parameters, and determining, when the first timing for the UE feedback conflicts with a second timing for an uplink channel or an uplink signal, whether the UE determines a first timing for transmission of the UE feedback associated with the MBS based on the one or more configuration parameters, and determining whether the UE determines a first timing for transmission of the UE feedback associated with the MBS based on the first timing. and dropping from transmission the received packet. [Brief description of the drawings]

[0016] [Figure 1] 1 illustrates an example of a system for mobile communications in accordance with some aspects of one or more exemplary embodiments of the present disclosure. [Diagram 2]2A and 2B are diagrams illustrating example radio protocol stacks for a user plane in accordance with some aspects of one or more exemplary embodiments of the present disclosure. [Diagram 3] 3A, 3B, and 3C are diagrams illustrating example mappings between logical channels and transport channels in the downlink in accordance with some aspects of one or more example embodiments of the present disclosure. [Figure 4] 4A, 4B, and 4C are diagrams illustrating example mappings between transport channels and physical channels in the downlink in accordance with some aspects of one or more example embodiments of the present disclosure. [Diagram 5] 5A, 5B, 5C, and 5D are diagrams illustrating example radio protocol stacks for NR sidelink communications in accordance with some aspects of one or more exemplary embodiments of the present disclosure. [Figure 6] 1 illustrates exemplary physical signals in the downlink, uplink, and sidelink in accordance with some aspects of one or more exemplary embodiments of the present disclosure. [Figure 7] 1 illustrates examples of Radio Resource Control (RRC) states and transitions between different RRC states, in accordance with some aspects of one or more example embodiments of the present disclosure. [Figure 8] 1 illustrates an example frame structure and physical resources in accordance with some aspects of one or more example embodiments of the present disclosure. [Figure 9] 1 illustrates example component carrier configurations in different carrier aggregation scenarios in accordance with some aspects of one or more example embodiments of the present disclosure. [Figure 10] 1 illustrates an exemplary bandwidth portion configuration and switching in accordance with some aspects of one or more exemplary embodiments of the present disclosure. [Figure 11] 1 illustrates an exemplary four-step contention-based and contention-free random access process in accordance with some aspects of one or more exemplary embodiments of the present disclosure. [Figure 12]1 illustrates an example two-step contention-based and contention-free random access process in accordance with some aspects of one or more example embodiments of the present disclosure. [Figure 13] 1 illustrates an example time and frequency structure of a synchronization signal and a Physical Broadcast Channel (PBCH) block (SSB), in accordance with some aspects of one or more example embodiments of the present disclosure. [Figure 14] 1 illustrates an example of an SSB burst transmission according to some aspects of one or more exemplary embodiments of the present disclosure. [Figure 15] 1 illustrates example components of a user terminal and a base station for transmission and / or reception in accordance with some aspects of one or more example embodiments of the present disclosure. [Figure 16] 1 illustrates an exemplary Multicast Broadcast Service (MBS) interest indication, in accordance with some aspects of one or more exemplary embodiments of the present disclosure. [Figure 17] 1 illustrates an exemplary selective multicast broadcast service (MBS) transmission involving multiple distributed units (DUs), remote units (RUs), transmission receiving points (TRPs), and / or beams in accordance with some aspects of one or more exemplary embodiments of the present disclosure. [Figure 18] 1 illustrates an example channel state information (CSI) and quasi-colocation (QCL) configuration, in accordance with some aspects of one or more example embodiments of the present disclosure. [Figure 19] 1 illustrates an example MBS CSI feedback from a user equipment (UE) in an RRC connected or idle / inactive state, in accordance with some aspects of one or more example embodiments of the present disclosure. [Figure 20] 1 illustrates an example process according to some aspects of one or more example embodiments of the present disclosure. [Figure 21] 1 illustrates an example process according to some aspects of one or more example embodiments of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0017] The following disclosure provides many different embodiments or examples for implementing different features of the provided subject matter. To simplify the disclosure, specific examples of configurations are described below. These are merely examples and are not intended to be limiting.

[0018] Terms such as "first", "second", etc. may be used herein to describe various elements, but these elements should not be limited by these terms. These terms are used to distinguish one element from another. For example, a first element can be referred to as a second element, and similarly, a second element can be referred to as a first element, without departing from the scope of the embodiment.

[0019] 1 illustrates an example of a mobile communication system 100 according to some aspects of one or more 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 Multiple 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-everything (V2X) communication services, safety services, mission-critical services, IoT, Industrial IoT (IIOT), and other services in residential, commercial, or industrial environments.

[0020] The mobile communication system 100 may enable various types of applications having different requirements in terms of 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, as well as moderate rates for cell-edge users. URLLC can support applications with stringent requirements in terms of latency and reliability, and moderate requirements in terms of data rates. An exemplary mMTC application includes a network of vast numbers of IoT devices that are only sporadically active and transmit small data payloads.

[0021] The mobile communication system 100 may include a radio access network (RAN) portion and a core network portion. The example shown in FIG. 1 illustrates a Next Generation RAN (NG-RAN) 105 and a 5G Core Network (5GC) 110 as examples of the RAN and the core network, respectively. Other examples of the RAN and the core network may be implemented without departing from the scope of the present disclosure. Other examples of the RAN include an Evolved Universal Terrestrial Radio Access Network (EUTRAN), a Universal Terrestrial Radio Access Network (UTRAN), and the like. Other examples of the core network include an Evolved Packet Core (EPC), a UMTS Core Network (UCN), and the like. The RAN implements a radio access technology (RAT) and resides between a user equipment (UE) 125 (e.g., UE 125A-UE 125E) 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 Telecommunication System (UMTS), and the like. The RAT of the exemplary system 100 for mobile communication may be NR. The core network may be a RAN and one or more external networks (e.g., data A functional layer between the UE 125 and the RAN (e.g., the NG-RAN 105) may be referred to as an access stratum (AS), and a functional layer between the UE 125 and the core network (e.g., the 5GC 110) may be referred to as a non-access stratum (NAS).

[0022] The UE 125 may include wireless transmitting and receiving components for communication with one or more nodes in the RAN, one or more relay nodes, or one or more other UEs, etc. Examples of the UE 125 include, but are not limited to, a smartphone, a tablet, a laptop, a computer, a wireless transmitting and / or receiving unit in a vehicle, a V2X or vehicle-to-vehicle (V2V) device, a wireless sensor, an IoT device, an IIOT device, etc. Other names may be used for the UE 125, such as a mobile station (MS), terminal equipment, terminal node, client device, mobile device, etc. Still further, the UE 125 may also include components or subcomponents integrated into other devices, such as a vehicle, to provide wireless communication capabilities with nodes in the RAN, other UEs, satellite communications, as described herein. Such other devices may have other functions or functions in addition to wireless communications. Thus, reference to a UE may include individual components that enable wireless communications as well as an entire device incorporating components for enabling wireless communications.

[0023] The RAN may include nodes (e.g., base stations) for communication with UEs. For example, the NG-RAN 105 of the mobile communication system 100 may include nodes for communication with the UEs 125. Different names may be used for the RAN nodes depending, for example, on the RAT used for the RAN. The RAN nodes may be referred to as Node Bs (NBs) in a RAN using a UMTS RAT. The RAN nodes may be referred to as Evolved Node Bs (eNBs) in a RAN using an LTE / EUTRA RAT. In the illustrative example of the mobile communication system 100 of FIG. 1, the nodes of the NG-RAN 105 may be either Next Generation Node Bs (gNBs) 115 (e.g., gNBs 115A, gNBs 115B) or Next Generation Evolved Node Bs (ng-eNBs) 120 (e.g., ng-eNBs 120A, ng-eNBs 120B). 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 towards the UE 125. The ng-eNB 120 may provide E-UTRA user plane and control plane protocol terminations towards 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 with a user plane protocol stack and a control plane protocol stack. For the Uu interface, the direction from the base station (e.g., gNB 115 or ng-eNB 120) to the UE 125 may be referred to as a downlink, and the direction from the UE 125 to the base station (e.g., gNB 115 or ng-eNB 120) may be referred to as an uplink.

[0024] The gNB 115 and the ng-eNB 120 may be interconnected with each other by 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 General Packet Radio Service (GPRS) Tunneling Protocol (GTP) may be used on top of 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) on top of IP. A The application layer signaling protocol is XnAP (Xn Application The SCTP layer can provide guaranteed delivery of application layer messages. At the transport IP layer, point-to-point transmission can be used to deliver signaling PDUs. The Xn-C interface can support Xn interface management, UE mobility management including context transfer and RAN paging, and dual connectivity.

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

[0026] 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 (e.g., scheduling) to UEs in both uplink and downlink, IP and Ethernet header compression, data encryption and integrity protection, selection of an AMF at UE attachment when routing to an AMF cannot be determined from information provided by the UE, routing of user plane data to UPF(s), routing of control plane information to AMF, connection setup and release, scheduling and transmission of paging messages (e.g., P2P messages originating from the AMF, etc.), and transmission of UE-originated AMF messages (e.g., P2P messages originating from the AMF). The 5G LTE-RPC can host one or more of the following: scheduling and transmission of system broadcast information (including LTE-RPC), 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 UE in RRC inactive state, delivery function for NAS messages, radio access network sharing, dual connectivity, tight interworking between NR and E-UTRA, and maintaining security and radio configuration for User Plane 5G System (5GS) Cellular IoT (CIoT) optimization.

[0027] The AMF 130 provides 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 checking roaming rights, mobility management control (subscription and policy), support for network slicing. It may host one or more of the following: a session management function (SMF) selection, and a 5GS CIoT optimization selection.

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

[0029] As shown in FIG. 1, the NG-RAN 105 may 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. Regardless of which RRC state the UE is in, sidelink transmission and reception over the PC5 interface may be supported when the UE 125 is within the coverage of the NG-RAN 105 and when the UE 125 is out of the coverage of the NG-RAN 105. Support for V2X services over the PC5 interface may be provided by NR sidelink communication and / or V2X sidelink communication.

[0030] PC5-S signaling may be used for unicast link establishment with direct communication request / accept messages. A UE may self-assign its 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 may send its source layer 2 ID for a PC5 unicast link to a peer UE, for example, a UE for which a destination ID was received from a higher layer. The source layer 2 ID and destination layer 2 ID pair may uniquely identify a unicast link. The receiving UE may verify that the destination ID belongs to it and may accept the unicast link establishment request from the source UE. During the PC5 unicast link establishment procedure, PC5-RRC procedures on the access stratum may be invoked for UE sidelink context establishment as well as for AS layer configuration, capability exchange, etc. PC5-RRC signaling may enable UE capabilities and AS layer configuration, such as sidelink radio bearer configuration, to be exchanged between a pair of UEs for which a PC5 unicast link is established.

[0031] 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 and destination layer 2 IDs in an AS. The unicast transmission mode may be characterized by the support of one PC5-RRC connection between peer UEs for the pair, the transmission and reception of control information and user traffic between peer UEs in the sidelink, the support of sidelink HARQ feedback, the support of sidelink transmit power control, the support of RLC acknowledged mode (AM), and the detection of radio link failure for the PC5-RRC connection. The groupcast transmission may be characterized by the transmission and reception of user traffic between UEs belonging to a group in the sidelink and the support of sidelink HARQ feedback. The broadcast transmission may be characterized by the transmission and reception of user traffic between UEs in the sidelink.

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

[0033] 2A and 2B illustrate example radio protocol stacks for the user plane and control plane, respectively, in accordance with some aspects of one or more example 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 sublayers of Layer 2, and Physical (PHY) 205 and PHY 215 layers (Layer 1 is also referred to as L1).

[0034] 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. The radio bearers can be classified 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.

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

[0036] The HARQ function may ensure delivery between peer entities at Layer 1. A single HARQ process may support one TB if the physical layer is not configured for downlink / uplink spatial multiplexing, and a single HARQ process may support one or multiple TBs if the physical layer is configured for downlink / uplink spatial multiplexing.

[0037] 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 numerology and / or transmission duration, and Automatic Repeat Request (ARQ) may operate for any numerology and / or transmission duration for which the logical channel is configured.

[0038] The main services and functions of the RLC203 or RLC213 sub-layer depend on the transmission mode (e.g., TM, UM, or AM) and may include transport of higher layer PDUs, sequence numbering independent of the sequence numbering in PDCP (UM and AM), error correction via ARQ (AM only), segmentation (AM and UM) and re-segmentation (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).

[0039] An automatic repeat request in the RLC 203 or RLC 213 sub-layer may have the following characteristics: ARQ retransmits RLC SDUs or RLC SDU segments based on an RLC status report. Polling of RLC status reports may be used when required by RLC. The RLC receiver may also trigger an RLC status report after detecting a missing RLC SDU or RLC SDU segment.

[0040] The main services and functions of the PDCP202 or PDCP212 sub-layer may include forwarding of data (user plane or control plane), maintenance of 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, routing for split bearers, duplication, reordering and in-order delivery, out-of-order delivery, and duplication discarding.

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

[0042] As shown in FIG. 2B, the control plane protocol stack of the Uu interface (between the UE 125 and the gNB 115) includes a PHY layer (Layer 1), the MAC, RLC, and PDCP sublayers of Layer 2 as described above, and further the RRC 206 and RRC 216 sublayers. The main services and functions of the RC216 sublayer include broadcasting of system information related to AS and NAS, paging initiated by 5GC or NG-RAN, establishment, maintenance, and release of RRC connection between UE and NG-RAN (including adding, modifying, and releasing carrier aggregation, and adding, modifying, and releasing dual connectivity within NR or between E-UTRA and NR), security functions including key management, establishment, configuration, maintenance, and release of SRB and DRB, mobility functions (including handover and context transfer, UE cell selection and reselection, and control of cell selection and reselection, and inter-RAT mobility), QoS management functions, UE measurement reporting and control of reporting, detection of radio link failure and recovery from radio link failure, and NAS message transfer from NAS to UE / UE to NAS. 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.

[0043] 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 pattern(s).

[0044] 3A, 3B, and 3C show example mappings between logical channels and transport channels in the downlink, uplink, and sidelink, respectively, according to some aspects of one or more example 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. The logical channels may be classified into two groups: control channels and traffic channels. The control channels may be used for transfer of control plane information only. 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 the UE and the 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 the UE and the network and may be used by UEs that have an RRC connection. The traffic channels may be used for transfer of user plane information only. A Dedicated Traffic Channel (DTCH) is a point-to-point channel dedicated to one UE for the transfer of user information. A DTCH can exist in both 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 UE(s). A Sidelink Traffic Channel (STCH) is a sidelink channel for transmitting user information from one UE to other UE(s). A Sidelink Broadcast Control Channel (SBCCH) is a sidelink channel for broadcasting sidelink system information from one UE to other UE(s).

[0045] Downlink transport channel types include the Broadcast Channel (BCH), the Downlink Shared Channel (DL-SCH), and the Paging Channel (PCH). The BCH may be characterized by a fixed predefined transport format and the requirement to be broadcast throughout the coverage area of ​​a cell, either as a single message or by beamforming different BCH instances. The DL-SCH is characterized by support for HARQ, support for dynamic link adaptation by varying modulation, coding, and transmit power, the possibility of being broadcast throughout the entire cell, the possibility of using beamforming, support for both dynamic and semi-static resource allocation, and UE discontinuous reception (DR) to enable UE power savings. The DL-SCH may be characterized by support for HARQ, support for dynamic link adaptation by varying modulation, coding, and transmission power, the possibility of being broadcast in the entire 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 may be characterized by support for UE discontinuous reception (DRX) to enable UE power saving (DRX cycles are indicated to the UE by the network), the requirement to be broadcast in the entire coverage area of ​​the cell, either as a single message or by beamforming different BCH instances, and being mapped to physical resources that may also be dynamically used for traffic / other control channels.

[0046] 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.

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

[0048] 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.

[0049] Sidelink transport channel types include a Sidelink Broadcast Channel (SL-BCH) and a 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 semi-static resource allocation when the UE is allocated resources by the NG-RAN, support for HARQ, and support for dynamic link adaptation by varying transmit power, modulation, and coding.

[0050] 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.

[0051] 4A, 4B, and 4C show example mappings between transport channels and physical channels in the downlink, uplink, and sidelink, respectively, in accordance with some aspects of one or more example embodiments of the present disclosure. The 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. The PDCCH does not include a transport channel. The port channel is not mapped and downlink control information (DCI) is carried.

[0052] The physical channels in the uplink include the Physical Uplink Shared Channel (PUSCH), the Physical Uplink Control Channel (PUCCH), and the Physical Random Access Channel (PRACH). The UL-SCH transport channel may be mapped to the PUSCH, and the RACH transport channel may be mapped to the PRACH. The PUCCH is not mapped to any transport channel, and carries uplink control information (UCI).

[0053] The physical channels in the sidelink 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) may indicate the resources and other transmission parameters used by the UE for the PSSCH. The physical sidelink shared channel (PSSCH) may transmit TBs of the data itself, as well as control information for the HARQ procedure and channel state information (CSI) feedback triggering, etc. At least six orthogonal frequency division multiplexing (OFDM) symbols in a slot may be used for the 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 that is repeated across two OFDM symbols near the end of the sidelink resources in the slot. The SL-SCH transport channel may be mapped to the PSSCH. The SL-BCH may be mapped to the PSBCH. No transport channel is mapped to the PSFCH, but sidelink feedback control information (SFCI) may be mapped to the PSFCH. No transport channel is mapped to the PSCCH, but sidelink control information (SCI) may be mapped to the PSCCH.

[0054] 5A, 5B, 5C, and 5D illustrate examples of radio protocol stacks for NR sidelink communication according to some aspects of one or more exemplary embodiments of the present disclosure. The AS protocol stack for the user plane (i.e., for STCH) in the PC5 interface may consist of SDAP, PDCP, RLC, and MAC sublayers, and a physical layer. The user plane protocol stack is shown in FIG. 5A. The AS protocol stack for SBCCH in the PC5 interface may consist of RRC, RLC, MAC sublayers, and a physical layer, as shown in FIG. 5B below. For support of the PC5-S protocol, PC5-S sits on top of the PDCP, RLC, and MAC sublayers, and the physical layer in the control plane protocol stack for SCCH for PC5-S, as shown in FIG. 5C. The AS protocol stack for the control plane for SCCH for RRC in the PC5 interface consists of RRC, PDCP, RLC, and MAC sublayers, and a physical layer. The control plane protocol stack for SCCH for RRC is shown in FIG. 5D.

[0055] Sidelink Radio Bearers (SLRBs) may be classified 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 may be configured for PC5-RRC and PC5-S signaling, respectively.

[0056] The MAC sublayer may 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 the AC, only sidelink logical channels belonging to the same destination can be multiplexed into the MAC PDU for all unicast, groupcast, and broadcast transmissions that may be associated with the destination. For packet filtering, the SL-SCH contains both the source Layer 2 ID and the destination Layer 2 ID part. A MAC header may be added to the MAC PDU. A Logical Channel Identifier (LCID) contained within the MAC sub-header may uniquely identify a logical channel within the combination of a source Layer 2 ID and a destination Layer 2 ID.

[0057] 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.

[0058] The PDCP sub-layer services and functions for the Uu interface may be supported for the sidelink with some restrictions, namely, out-of-order delivery may only be supported for unicast transmission and duplication may not be supported over the PC5 interface.

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

[0060] The RRC sublayer may 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, detection of sidelink radio link failure of PC5-RRC connections based on indications from MAC or RLC. A PC5-RRC connection may be a logical connection between two UEs for a pair of source layer 2 ID and destination layer 2 ID that may be considered to be 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 multiple UEs for different pairs of source layer 2 ID and destination layer 2 ID. Separate PC5-RRC procedures and messages may be used for the UE to transfer UE capabilities and sidelink configurations, including SL-DRB configurations, to a peer UE. Both peer UEs may exchange their own UE capabilities and sidelink configurations using separate bidirectional procedures in both sidelink directions.

[0061] FIG. 6 illustrates example physical signals in the downlink, uplink, and sidelink according to some aspects of one or more example embodiments of the present disclosure. Demodulation reference signals (DM-RS) may be used in the downlink, uplink, and sidelink and may be used for channel estimation. DM-RS is a UE-specific reference signal that may be transmitted along with a physical channel in the downlink, uplink, or sidelink and may be used for channel estimation and coherent detection of the physical channel. Phase tracking reference signals (PT-RS) 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-RS 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-RS may occur when the network configures PT-RS to exist in combination with DM-RS. Positioning Reference Signals (PRS) are used in the downlink for positioning using different positioning technologies. The PRS may be used in the downlink. The PRS may be used to measure the delay of the downlink transmission by correlating the received signal from the base station with a local replica in the receiver. The Channel State Information Reference Signal (CSI-RS) may be used in the downlink and sidelink. The CSI-RS may be used for channel state estimation, Reference Signal Received Power (RSRP) measurement for mobility and beam management, time / frequency tracking for demodulation, among others. The CSI-RS may be configured UE specific, but multiple users may share the same CSI-RS resource. The UE may determine the CSI reports and transfer them to the base station in the uplink using PUCCH or PUSCH. The CSI reports may be carried in the sidelink MAC control element (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 procedure 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 may serve as a QCL reference for other physical channels such that they may be configured and transmitted quasi-collocated with the SRS. Sidelink PSS (S-PSS) and Sidelink SSS (S-SSS) may be used in the sidelink for sidelink synchronization.

[0062] 7 illustrates an example of radio resource control (RRC) states and transitions between different RRC states according to some aspects of one or more example 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 powering 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, perform data transfer, and / or make / receive voice calls. Once an RRC connection is established, the UE may be in the RRC connected state 710. The UE may 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.

[0063] The RRC inactive state 730 may be used to reduce 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.

[0064] FIG. 8 illustrates an example frame structure and physical resources according to some aspects of one or more example embodiments of the present disclosure. Downlink or uplink or sidelink transmissions may be organized into frames of 10 ms duration consisting of 10 (0-9) 1 ms subframes. Each subframe may consist of k slots (k=1, 2, 4, ...), where the number of slots per subframe k may depend on the subcarrier spacing of the carrier on which the transmission takes place. The slot duration may be 14 (0-13) symbols with normal cyclic prefix (CP) and 12 symbols with extended CP, and may scale in time as a function of the subcarrier spacing used such that there is an integer number of slots in a subframe. FIG. 8 illustrates a resource grid in the time and frequency domain. Each element of the resource grid, which includes one symbol in time and one subcarrier in frequency, is referred to as a resource element (RE). A resource block (RB) is defined as 12 consecutive subcarriers in the frequency domain. obtain.

[0065] 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 application examples 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 over eMBB).

[0066] FIG. 9 illustrates example component carrier configurations in different carrier aggregation scenarios according to some aspects of one or more example embodiments of the present disclosure. In carrier aggregation (CA), two or more component carriers (CCs) may be aggregated. A UE may receive or transmit simultaneously 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 on different bands, as shown in FIG. 9. The gNB and the UE may communicate using a serving cell. The serving cell may be associated with at least one downlink CC (e.g., may be associated with only one downlink CC or may be associated with a downlink CC and an uplink CC). The serving cell may be a primary cell (PCell) or a secondary cCell (SCell).

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

[0068] In the RRC connected state, the gNB may be responsible for maintaining the Timing Advance (TA) to keep L1 synchronized. Serving cells with uplinks to which the same TA applies and using 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 in some cases the SCell may also be used as the timing reference cell. For a secondary TAG, the UE may use any of the activated SCells of this TAG as the timing reference cell and may not change it unless necessary.

[0069] A timing advance update may be signaled by the gNB to the UE via a MAC CE command, which may restart a TAG-specific timer that may indicate whether L1 may be synchronized or not; when the timer is running, L1 may be considered synchronized, otherwise L1 may be considered unsynchronized (uplink transmissions may only be made on the PRACH).

[0070] A UE with single-TA capability for CA can simultaneously receive and / or transmit on multiple CCs corresponding to multiple serving cells (multiple serving cells grouped into one TAG) sharing the same TA. A UE with multiple-TA capability for CA can simultaneously receive and / or transmit on multiple CCs corresponding to multiple serving cells (multiple serving cells grouped into multiple TAGs) with different TAs. The NG-RAN ensures that each TAG contains at least one serving cell. A non-CA capable 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).

[0071] The multi-carrier nature 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. If CA is configured, the UE may have one RRC connection with the network. Upon 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 configured set of serving cells for a UE may consist of one PCell and one or more SCells. Reconfiguration, addition, and removal of SCells may be done by RRC.

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

[0073] FIG. 10 illustrates an example bandwidth portion configuration and switching according to some aspects of one or more example embodiments of the present disclosure. A UE may be configured with one or more bandwidth portions (BWPs) 1010 (e.g., 1010A, 1010B) on 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 operating bandwidth of the cell. For initial access and until the UE's configuration in the cell is received, an initial bandwidth portion 1020 determined from system information may be used. With bandwidth adaptation (BA), for example, through BWP switching 1040, the UE's reception and transmission bandwidth may not be as large as the cell's bandwidth and may be adjusted. For example, the width may be commanded to vary (e.g., to shrink during periods of low activity to save power), the location may move in the frequency domain (e.g., to increase scheduling flexibility), and the subcarrier spacing may be commanded to vary (e.g., to enable different services). The first active BWP 1030 may be the active BWP upon RRC (re)configuration for the PCell or activation of the SCell.

[0074] For a downlink BWP or an uplink BWP in a set of downlink BWP or uplink BWP, respectively, the UE may be provided with the following configuration parameters: subcarrier spacing (SCS), cyclic prefix, common RB and adjacent RBs, index in the set of downlink BWP or uplink BWP by each BWP-Id, a set of BWP common parameters and a set of BWP-specific parameters. The BWP may be associated with an OFDM numerology according to the configured subcarrier spacing and cyclic prefix 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.

[0075] A downlink BWP may be associated with a BWP inactivity timer. If a 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 a 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 not, the UE may perform a BWP switch to the initial downlink BWP.

[0076] FIG. 11 illustrates an example 4-step contention-based random access (CBRA) process and contention-free random access (CFRA) process according to some aspects of one or more example embodiments of the present disclosure. FIG. 12 illustrates an example 2-step contention-based random access (CBRA) process and contention-free random access (CFRA) process according to some aspects of one or more example embodiments of the present disclosure. The random access procedure can be triggered by multiple 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 status is "unsynchronized", uplink data arrival during an RRC connected state when there are no PUCCH resources for a Scheduling Request (SR) available, an SR failure, a request by RRC upon synchronization reconfiguration (e.g., handover), a transition from an RRC inactive state to establish time alignment for a secondary TAG, a request for other system information (SI), beam failure recovery (BFR), and consistent uplink listen-before-talk (LBT) failure on the PCell.

[0077] Two types of random access (RA) procedures can be supported: a four-step RA type using MSG1 and a two-step RA type using 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.

[0078] The UE may 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 may 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 may perform random access with the 4-step RA type. If CFRA resources for the 2-step RA type are configured, the UE may perform random access with the 2-step RA type.

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

[0080] The two-step RA type MSGA may include a preamble on PRACH and a payload on PUSCH (e.g., step A of CBRA in FIG. 12). After MSGA transmission, the UE may 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 (steps 0 and A of CFRA in FIG. 12), and upon receiving a network response (step B of CFRA in FIG. 12), the UE may monitor for a response from the network within a configured window as shown in FIG. 12. In the case of CBRA, if the contention resolution is successful when receiving a network response (step B of CBRA in FIG. 12), the UE may terminate the random access procedure as shown in FIG. 12, whereas if a fallback indication is received in MSGB, the UE may perform MSG3 transmission using the uplink grant scheduled in the fallback indication and monitor contention resolution. If contention resolution is not successful after MSG3 (re)transmission(s), the UE may return to MSGA transmission.

[0081] FIG. 13 illustrates an exemplary time and frequency structure of a synchronization signal and a physical broadcast channel (PBCH) block (SSB) according to some aspects of one or more exemplary embodiments of the present disclosure. The SS / PBCH block (SSB) may consist of a primary synchronization signal and a secondary synchronization signal (PSS, SSS), each occupying one symbol and 127 subcarriers (e.g., subcarrier numbers 56-182 in FIG. 13), and a PBCH on one symbol that spans three OFDM symbols and 240 subcarriers but leaves an unused portion in the middle for the SSS as shown in FIG. 13. The possible time positions of the SSBs within a half-frame may be determined by the subcarrier spacing, and the periodicity of the half-frames during 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 that span the coverage area of ​​the cell).

[0082] The PBCH may be used to carry a Master Information Block (MIB) 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 required to acquire System Information Block 1 (SIB1), more specifically, the information required to monitor the PDCCH for scheduling the PDSCH carrying SIB1. The MIB may also 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 SIs. Other SI 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 state), or sent in a dedicated manner to UEs in RRC connected state on the DL-SCH (e.g., if configured by the network, upon request from a UE in RRC connected state, or when the UE has an active BWP that does not have a configured common search space).

[0083] FIG. 14 illustrates an example SSB burst transmission according to some aspects of one or more example embodiments of the present disclosure. The SSB burst may include N SSBs (e.g., SSB_1, SSB_2, ..., SSB_N), where each SSB of the N SSBs may correspond to a beam (e.g., beam_1, beam_2, ..., beam_N). The SSB burst may be transmitted according to a periodicity (e.g., SSB burst period). During a contention-based random access process, the UE may perform a random access resource selection process, where 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 an SSB with an RSRP above a configured threshold is not available. A set of random access preambles may be associated with the SSB. After selecting the SSB, the UE may select a random access preamble from the set of random access preambles associated with the SSB, and may transmit the selected random access preamble to initiate the random access process.

[0084] In some embodiments, one beam of the N beams may be associated with a CSI-RS resource (e.g., CSI-RS_1, CSI-RS_2, ..., CSI-RS_N). The UE may measure the CSI-RS resources and may select a CSI-RS having an RSRP above a configured threshold. The UE may select a random access preamble corresponding to the selected CSI-RS and may 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 may select a random access preamble corresponding to an SSB quasi-co-located with the selected CSI-RS.

[0085] In some embodiments, based on the UE measurements of CSI-RS resources and the UE CSI report, the base station may determine a transmission configuration indication (TCI) state and may indicate the TCI state to the UE, and the UE may use the indicated TCI state for reception of downlink control information (e.g., via PDCCH) or data (e.g., via PDSCH). The UE may use the indicated TCI state to use an appropriate beam for reception of data or control information. The indication of the TCI state may use 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 a value of a field in the downlink control information that schedules the downlink transmission). The TCI state may 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., PDCCH or PDSCH, respectively).

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

[0087] FIG. 15 illustrates example components of a user terminal and a base station for transmission and / or reception in accordance with some aspects of one or more example embodiments of the present disclosure. In one embodiment, the example components of FIG. 15 may be considered to be illustrative of functional blocks of an example base station 1505. In another embodiment, the example components of FIG. 15 may be considered to be illustrative of functional blocks of an example user equipment (UE) 1500. Thus, the components illustrated in FIG. 15 are not necessarily limited to either a UE or a base station.

[0088] The antenna 1510 may be used for transmission or reception of electromagnetic signals. The antenna 1510 may include one or more antenna elements and may be configured with different input / output antennas including multiple-input multiple-output (MIMO) configurations, multiple-input single-output (MISO) configurations, and single-input multiple-output (SIMO) configurations. 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 only support a single antenna.

[0089] The transceiver 1520 can communicate wireless links described herein bidirectionally 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 may include a modem for modulating packets, providing the modulated packets to the antenna 1510 for transmission, and demodulating packets received from the antenna 1510.

[0090] 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.

[0091] The processor 1540 may include a hardware device having processing capabilities (e.g., a general purpose processor, a digital signal processor (DSP), a central processing unit (CPU), a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some examples, the processor 1540 may be configured to operate a memory using a memory controller. In other examples, a 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., memory 1530) to cause the UE 1500 or the base station 1505 to perform various functions.

[0092] The CPU 1550 may perform basic arithmetic, logical, control, and input / output (I / O) operations specified by computer instructions in the memory 1530. The UE 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 processing performance of the UE 1500 and / or base station 1505. The GPS 1570 may be used, for example, to enable location-based services or other services based on the geographic location of the UE 1500.

[0093] In some examples, the UE 1500 may be configured or programmed to provide UE feedback. The UE 1500 may include a memory (e.g., memory 1530 of FIG. 15) that stores instructions (e.g., code 1535 of FIG. 15) and a processor (e.g., processor 1540 of FIG. 15) configured or programmed to execute instructions to perform a method. The method includes receiving, by the UE, one or more messages, the one or more messages including one or more first configuration parameters for a first UE feedback in a radio resource control (RRC) connected state and one or more second configuration parameters for a second UE feedback in an RRC idle state or an RRC inactive state; transmitting, by the UE, the first UE feedback based on the one or more first configuration parameters when the UE is in the RRC connected state; and transmitting, by the UE, the first UE feedback based on the one or more first configuration parameters when the UE is in the RRC idle state or when the UE is in the RRC inactive state. and transmitting, by the UE, second UE feedback based on the second configuration parameter. The UE 1500 can receive one or more messages from a base station (e.g., base station 1505) and provide the first UE feedback and the second UE feedback to the base station.

[0094] In some examples, the UE 1500 may be configured or programmed to provide UE feedback. The UE 1500 may include a memory (e.g., memory 1530 of FIG. 15) storing instructions (e.g., code 1535 of FIG. 15) and a processor (e.g., processor 1540 of FIG. 15) configured or programmed to execute instructions to perform a method. The method includes receiving, by the UE, one or more configuration parameters for UE feedback associated with the MBS, determining, by the UE, a first timing for transmission of the UE feedback associated with the MBS based on the one or more configuration parameters, and dropping the UE feedback associated with the MBS from transmission at the first timing when the first timing for the UE feedback conflicts with a second timing for an uplink channel or an uplink signal. The UE 1500 may receive the one or more configuration parameters from a base station (e.g., base station 1505) and provide the UE feedback to the base station.

[0095] In some examples, the UE 1500 and the base station 1505 are included in a system for mobile communication. The base station may be configured or programmed to transmit one or more messages including one or more first configuration parameters for a first UE feedback in a Radio Resource Control (RRC) connected state and one or more second configuration parameters for a second UE feedback in an RRC idle state or an RRC inactive state. The UE may be configured or programmed to receive the one or more messages, transmit the first UE feedback based on the one or more first configuration parameters when the UE is in an RRC connected state, and transmit the second UE feedback based on the second configuration parameters when the UE is in an RRC idle state or when the UE is in an RRC inactive state.

[0096] In some examples, the UE 1500 and the base station 1505 are included in a system for mobile communication. The base station may be configured or programmed to transmit one or more configuration parameters for UE feedback associated with a Multicast Broadcast Service (MBS). The UE may be configured or programmed to receive the one or more configuration parameters, determine a first timing for transmission of UE feedback associated with the MBS, and drop the UE feedback associated with the MBS from transmission at the first timing when the first timing of the UE feedback conflicts with a second timing of an uplink channel or an uplink signal.

[0097] In some examples, MBS services may be enabled via single-cell transmission. MBS may be transmitted within the coverage of a single cell. One or more multicast / broadcast control channels (e.g., MCCH) and one or more multicast / broadcast data channels (e.g., MTCH) may be mapped onto the DL-SCH. Scheduling may be performed by the gNB. Multicast / broadcast control channel and multicast / broadcast data channel transmissions may be indicated by logical channel specific RNTIs 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, the multicast / broadcast control channel and / or the multicast / broadcast data channel may be mapped onto the DL-SCH. A single transmission may be used for the DL-SCH associated with the multicast data channel transmission, 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 transmissions over the multicast / broadcast control channel and / or the multicast / broadcast data channel.

[0098] 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 scheduling cycle; multicast / broadcast data channel on duration (e.g., the duration the UE waits to receive a PDCCH after waking up from DRX); multicast / broadcast data channel inactivity timer (e.g., the duration the UE waits to successfully decode a PDCCH, failing which it re-enters DRX, since the last successful decoding of a PDCCH indicating the DL-SCH to which this multicast / broadcast data channel is mapped).

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

[0100] In some examples, one or more logical channels may be related to 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 more 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.

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

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

[0103] In some examples, control information for reception of MBS services may be provided on a specific logical channel (e.g., 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 about neighboring cells that carry MBS sessions that may be ongoing on the current cell. In some examples, a UE may receive a single MBS service at a time or two or more MBS services in parallel.

[0104] 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.

[0105] In some examples, modification of MCCH information may occur in a particular 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 a SFN value, SFN mod m=0, where m is the number of radio frames that includes the modification period. The modification period may be configured by SIB or by RRC signaling.

[0106] In some examples, when the network changes (a part of) the MCCH information, it may notify the UE about the change in the first subframe / slot that may be used for MCCH transmission during the repetition period. Upon receiving the change notification, the UE that is interested in receiving the MBS service may 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.

[0107] In one example, the system information block (SIB) may include information required to obtain control information associated with the transmission of the MBS, which 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.

[0108] In one example, the information element (IE) may provide configuration parameters indicating, for example, a list of ongoing MBS sessions carried 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 about 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 about a list of neighbor cells, etc. It can be seen.

[0109] In some examples, a gNB or ng-eNB may include logical nodes hosting some, all, or part of user plane functions and / or control plane functions. For example, a gNB central unit (gNB-CU) may be a logical node hosting the RRC, SDAP, and PDCP protocols of a gNB, or the RRC and PDCP protocols of an en-gNB that controls the operation of one or more gNB-DUs. The gNB-CU may terminate an F1 interface connected with a gNB-DU. A gNB distributed unit (gNB-DU) may be a logical node hosting the RLC, MAC, and PHY layers of a gNB or an en-gNB, the operation of which may be partially controlled by the gNB-CU. One gNB-DU may support one or multiple cells. One cell may be supported by only one gNB-DU. The gNB-DU may terminate an F1 interface connected with a gNB-CU. The gNB-CU-Control Plane (gNB-CU-CP) may be a logical node hosting the RRC and control plane part of the PDCP protocol of the gNB-CU for the en-gNB or the 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 hosting the user plane part of the PDCP protocol of the gNB-CU for the en-gNB and the user plane part of the PDCP protocol and the SDAP protocol 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.

[0110] In some examples, the CSI-AperiodicTriggerStateList IE may be used to configure the UE with a list of aperiodic trigger states. Each codepoint of the DCI field "CSI Request" may be associated with one trigger state. Upon receiving a value associated with a trigger state, the UE may perform CSI-RS, CSI-IM and / or SSB (Reference Signal) measurements and aperiodic reporting over L1 according to all entries in the ReportConfigInfoList associated with that trigger state. The csi-IM-ResourcesForInterference field may indicate a CSI-IM-ResourceSet for interference measurements. The csi-SSB-ResourceSet field may indicate a CSI-SSB-ResourceSet for channel measurements. The nzp-CSI-RS-ResourcesForInterference field may indicate an NZP-CSI-RS-ResourceSet for interference measurements. The qcl-info field may indicate a list of references to TCI-States for providing a QCL source and a QCL type for each NZP-CSI-RS-Resource listed in nzp-CSI-RS-Resources of the NZP-CSI-RS-ResourceSet indicated by nzp-CSI-RS-ResourcesforChannel. Each TCI-StateId refers to a TCI-State that may have this value for tci-StateId, and may be defined in a tci-StatesToAddModList in a PDSCH-Config included in a BWP-Downlink corresponding to the serving cell and the DL BWP to which resourcesForChannelMeasurement (in the CSI-ReportConfig indicated by the above reportConfigId) belongs. The reportConfigId may indicate one reportConfigId of the CSI-ReportConfigToAddMod configured in the CSI-MeasConfig.The resourceSet field may indicate the NZP-CSI-RS-ResourceSet for channel measurements.

[0111] In some examples, the CSI-FrequencyOccupation IE may be used to configure the frequency domain occupancy of a channel state information measurement resource (e.g., NZP-CSI-RS-Resource, CSI-IM-Resource). The nrofRBs field may indicate the number of PRBs this CSI resource spans. The startingRB field may indicate the PRB where this CSI resource starts relative to common resource block #0 (CRB#0) on the common resource block grid.

[0112] In some examples, the CSI-IM-Resource IE may be used to configure one CSI interference management (IM) resource.

[0113] In some examples, the IE CSI-IM-ResourceId may be used to identify one CSI-IM-Resource.

[0114] In some examples, the IE CSI-IM-ResourceSet may be used to configure a set of one or more CSI interference management (IM) resources (their IDs) and set-specific parameters.

[0115] In some examples, the IE CSI-IM-ResourceSetId may be used to identify the CSI-IM-ResourceSets.

[0116] In some examples, the IE CSI-MeasConfig may be used to configure CSI-RS (Reference Signal) belonging to the serving cell in which the CSI-MeasConfig is included, channel state information reports to be transmitted on the PUCCH on the serving cell in which the CSI-MeasConfig is included, and channel state information reports on the PUSCH triggered by DCI received on the serving cell in which the CSI-MeasConfig is included.

[0117] In some examples, the IE CSI-ReportConfigId may be used to identify one CSI-ReportConfig.

[0118] In some examples, the IE CSI-ResourceConfig may define a group of one or more NZP-CSI-RS-ResourceSets, CSI-IM-ResourceSets, and / or CSI-SSB-ResourceSets.

[0119] In some examples, the IE CSI-ResourceConfigId may be used to identify the CSI-ResourceConfig.

[0120] In some examples, the IE CSI-ResourcePeriodicityAndOffset may be used to configure the periodicity and corresponding offset for periodic and semi-persistent CSI resources and for periodic and semi-persistent reporting on the PUCCH. Both the periodicity and offset may be provided in number of slots.

[0121] In some examples, the IE CSI-RS-ResourceConfigMobility may be used to configure CSI-RS based RRM measurements.

[0122] In some examples, the IE CSI-RS-ResourceMapping may be used to configure resource element mapping of CSI-RS resources in the time and frequency domains.

[0123] In some cases, CSI-SemiPersistentOnPUSCH-Trigger The rStateList IE may be used to configure the UE with a list of trigger states for semi-persistent reporting of channel state information on L1.

[0124] In some examples, the IE CSI-SSB-ResourceSet may be used to configure one SS / PBCH block resource set, which may point to the SS / PBCH as indicated in ServingCellConfigCommon.

[0125] In some examples, the IE CSI-SSB-ResourceSetId may be used to identify one SS / PBCH block resource set.

[0126] In some examples, the RRCRelease message may be used to command the release of the RRC connection or the suspension of the RRC connection. The cnType field may indicate that the UE is redirected to EPC or 5GC. The deprioritisationReq field may indicate whether the current frequency or RAT is deprioritized. The deprioritisationTimer field may indicate the period during which either the current carrier frequency or NR is deprioritized. The suspendConfig field may indicate the configuration for the RRC_INACTIVE state. The network may not configure suspendConfig when the network redirects the UE to an inter-RAT carrier frequency or if the UE is configured with DAPS bearers. The redirectedCarrierInfo field may indicate the carrier frequency (downlink for FDD) and may be used to redirect the UE to an NR or inter-RAT carrier frequency by cell selection upon transition to RRC_IDLE or RRC_INACTIVE. The carrierFreq field may indicate the redirected NR frequency. The ssbSubcarrierSpacing field may indicate the subcarrier spacing of the SSB frequency in the redirected SSB. The smtc field may indicate the SSB periodicity / offset / duration configuration for the redirected SSB frequency. This is based on the timing reference of the PCell. If this field is not present, the UE may use the SMTC configured in the measObjectNR with the same SSB frequency and subcarrier spacing. The cellList may indicate a list of cells configured as the RAN Area. The ran-AreaConfigList field may indicate a list of RAN Area Codes or RA Code(s) as the RAN Area. The plmn-Identity field may indicate the PLMN Identity to which the cells in the ran-Area belong. If the field is not present, the UE may use the ID of the registered PLMN. The ran-AreaCells field may indicate the total number of cells of all PLMNs.

[0127] In some examples, DCI format 1_1 may be used for scheduling of PDSCH in one cell. DCI format 1_1 with CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI may include a transmission configuration indication field that may have a bit width of 0 bits if the higher layer parameter tci-PresentInDCI is not enabled, otherwise the bit width of this field may be 3 bits. If the bandwidth portion indicator field indicates a bandwidth portion other than the active bandwidth portion, if the higher layer parameter tci-PresentInDCI is not enabled for a CORESET used for a PDCCH carrying DCI format 1_1, the UE may assume that tci-PresentInDCI is not enabled for all CORESETs in the indicated bandwidth portion, otherwise the UE may assume that tci-PresentInDCI is enabled for all CORESETs in the indicated bandwidth portion.

[0128] In some examples, DCI format 1_2 may be used for scheduling of PDSCH in one cell. DCI format 1_2 with CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI may include a transmission configuration indication field that may have a bit width of 0 bits if the higher layer parameter tci-PresentForDCI-Format1_2 is not enabled, otherwise the bit width may be 1 bit, 2 bits, or 3 bits determined by the higher layer parameter tci-PresentForDCI-Format1_2. If the bandwidth portion indicator field indicates a bandwidth portion other than the active bandwidth portion, if the higher layer parameter tci-PresentForDCI-Format1-2 is not enabled for a CORESET used for a PDCCH carrying DCI format 1_2, the UE may assume that tci-PresentForDCI-Format1-2 is not enabled for all CORESETs within the indicated bandwidth portion, otherwise the UE may assume that tci-PresentForDCI-Format1-2 is enabled for all CORESETs within the indicated bandwidth portion.

[0129] In some examples, in case of point-to-multipoint (PTM) delivery of MBS data to a group of UEs, it may be sufficient for the UE to report a wideband channel quality indicator (WB-CQI) (e.g., limited to the bandwidth portion (BWP) over which the PTM service is delivered) along with a rank indicator (RI) (e.g., if spatial multiplexing for PTM is supported by the system) for the gNB to perform the necessary link adaptation for PTM transmission.

[0130] In some examples, the CQI measurements may not be based on instantaneous CSI-RS measurements, but may be based on actual (e.g., time-averaged) BLER measurements at the UE. For example, the CSI-RS measurements may be subject to instantaneous interference fluctuations, based on which the gNB may not adapt its multicast transmissions (e.g., for MBS services). In some examples, the CSI-RS resource indicator (CRI) field of the CSI report may be preserved during the CSI report for PTM.

[0131] In some examples, the UE may report a wideband channel quality indicator together with a rank indicator (RI) (e.g., if spatial multiplexing for PTM is supported by the system) for the gNB to perform the link adaptation required for PTM transmission. In some examples, when using HARQ feedback based only on NACK with CSI reporting, CQI measurement may be based on actual (e.g., time-averaged) block error rate (BLER) measurement at the UE, rather than (instantaneous) CSI-RS measurement. In some examples, a compact CSI reporting format may be defined for multicast transmission. For example, CQI alone or CQI together with RI may be reported.

[0132] In some examples, the CSI-RS may be transmitted in an active BWP. The CSI-RS for multicast transmission may be restricted within a multicast (MC) BWP, which may be the only subband of the UE's active BWP.

[0133] In some examples, CSI-RS transmission and CSI reporting may be triggered for a group of multicast UEs. In some examples, a group common DL grant (GC-PDCCH for scheduling GC-PDSCH) may be used to trigger A-CSI-RS transmission. The A-CSI-RS transmitted by the gNB may be used for a group of multicast UEs. In some examples, based on the common A-CSI-RS, each UE may report CSI measurements on a per-UE PUSCH separately scheduled by the gNB. The GC-PDCCH may transmit the A-CSI-RS in a multicast BWP. The transmission can be triggered.

[0134] In some examples, for multicast communication, the beam for multicast transmission may be different from the beam for unicast communication to a particular UE. The multicast beam may be transmitted from multiple cells in an SFN area. The configuration of DL TRS / CSI-RS for TCI state for GC-PDCCH / PDSCH may be separate from that of unicast.

[0135] In some examples, beam failure detection for multicast may be associated with GC-PDCCH / GC-PDSCH during multicast BWP. When the UE fails to receive a unicast PDCCH, the UE may trigger beam failure and recovery on the PRACH or PUCCH. When the UE detects a multicast beam failure, beam recovery for multicast transmission may be assisted by using a unicast connection for multicast RRC_CONNECTED UEs, i.e., link radio recovery (LRR) and LRR response may be via a unicast link with the serving cell.

[0136] In some cases, in contrast to the PTP case with feedback from a single UE, the gNB may take into account feedback from multiple UEs involved in PTM transmission while selecting the beamforming or precoding vector and MCS index.

[0137] In some examples, by selecting an MCS based on the CQI corresponding to the worst case UE (e.g., the spectral efficiency corresponding to the minimum of the desired spectral efficiencies of all UEs), the gNB can ensure reliability even for UEs experiencing worst case channel quality.

[0138] In some examples, the MBS design may be based on a single-cell point-to-multipoint (PTM) architecture that does not use a single-frequency network (SFN) framework. Reliable and efficient delivery of MBS data to users in a multicast group, especially in Frequency Range 2 (FR2), may require transmission across multiple nodes, TRPs, and / or beams. In some examples, reliable delivery of MBS data with service continuity and mobility may require transmission of data from multiple transmission reception points (TRPs) and / or beams.

[0139] Exemplary embodiments may employ various multi-point transmission scenarios, such as multi-connectivity involving multiple gNBs or central units (CUs), multiple TRPs across a single CU, e.g., DUs with different MAC layers, multiple TRPs across multiple radio units (RUs) in a DU managed by the same MAC layer, use of multiple beams in the same DU / RU, etc. Examples of scenarios are shown in Figure 17. Efficient and reliable delivery of MBS transmissions in FR1 and / or FR2 may enable the use of multiple TRPs and beamforming to ensure coverage and reliability of MBS delivery.

[0140] In some examples, some or all members of a multicast group may be moving, for example in a V2X application. The physical layer and radio transmission configuration, e.g., the selection of involved TRP(s) and / or DU(s) and / or beam(s) may be updated. In some examples, the selection of TRP(s) / DU(s) / beam(s) and appropriate configured MBS PHY parameters may be a closed loop that requires some feedback from the UE. Based on the UE feedback / measurement information, the gNB can efficiently configure MBS transmission parameters and / or select TRP(s) / DU(s) / beam(s) for reliable and efficient MBS data, and all In some cases, the MBS group may be affected by the overall spectral efficiency. Maintaining efficient MBS distribution on one or more TRPs and / or beams may require some feedback from the UEs in the MBS group.

[0141] In some examples, the CSI feedback and QCL configuration for the MBS may be included in an MBS configuration that supports multiple TRP transmission. The framework may be based on multiple TRP operation with joint or selective cooperative transmission decision based on an aggregation of CSI feedback from UEs in an MBS group.

[0142] In some examples, to improve reliability and QoS support for multicast services for UEs in RRC idle / inactive states, and for broadcasting to all UEs in general, RRC idle / inactive UE feedback may be beneficial in addition to the RRC connected state. Maintaining efficient MBS delivery on one or more TRPs and beams may be based on some feedback from UEs in an MBS group.

[0143] In some examples, CSI feedback transmission from individual UEs for an MBS may not be time critical since the CSI feedback may be collectively considered by the gNB for any changes in MCS or MIMO / TRP / beam configuration. In some examples, resources may be configured for such CSI feedback, but the CSI feedback by individual UEs may be sporadic, random, and low frequency. In some examples, such CSI feedback may be triggered from a random subset of UEs since not all UEs receiving the MBS service may transmit CSI feedback at once. In some examples, CSI feedback for an MBS may not require periodic CSI feedback from the UEs and may be configured as aperiodic or semi-persistent CSI transmission. In some examples, common set resources may be configured to be shared and randomly used by UEs in an MBS group to transmit CSI feedback for that MBS bundle.

[0144] In some examples, the MBS RAN configuration for a given service bundle may include a set of TRPs used for transmission of associated multicast traffic channels (MTCHs) and may use quasi-co-location (QCL) with s sets of CSI-RSs or SSB reference signals. An exemplary CSI and QCL configuration as part of the MBS configuration in the RAN is shown in FIG. 18. The CSI feedback information required for MBS may be primarily CQI feedback and may be used to select the best set of antenna ports, e.g., CRI, SSB-RI. Such feedback may enable the gNB to identify the best set of TRPs / beams for delivering MBS data based on the near real-time distribution of member UEs. In some examples, the CSI feedback for MBS may be optimized to limit the information required by the RAN to adjust the MBS parameters. For example, wideband or sub-band CQI feedback and a bitmap indicating the QCL of the strongest selected RS with MBS may be included. In some examples, separate PRACH resources may be associated with different TRPs / beams and the UE may randomly transmit CQI feedback on the PRACH resources associated with the strongest received TRPs / beams. In some examples, multiple CSI processes, e.g., a combination of non-zero power and zero power CSI-RS / SSB-RS, may be RRC configured and the UE may transmit the CSI feedback CSI-RS process with the best channel quality. In some examples, MBS-specific CSI feedback information may be used for optimization of single-TRP MBS transmission and multi-TRP MBS transmission by the gNB.

[0145] In some examples, a given gNB may receive multiple CSI feedbacks and use them over time, and missing some of them may not significantly impact its MBS configuration. In some examples, such CSI feedback may be skipped by the UE if it conflicts with other uplink transmissions. CSI feedback for MBSs may have lower priority than other uplink transmissions from the UE and may be dropped if it causes conflicts with other data and control signaling transmissions. In some embodiments, CSI feedback for MBSs may have higher or equal priority than other uplink transmissions from the UE. In these embodiments, CSI feedback may be transmitted even if there is a conflict between the CSI feedback transmission and other data / control signaling transmissions. In some embodiments, as mentioned above, the CSI feedback may be any other type of UE feedback (e.g., HARQ feedback).

[0146] In some examples, for multicast services with long session durations, some with periodic traffic patterns, many UEs may be receiving MBS data mostly in idle / inactive state. In such cases, some form of CSI feedback from inactive / idle UEs is needed for the RAN to ensure proper use of radio and antenna resources for delivering MBS. Exemplary MBS CSI feedback from a random subset of connected, inactive, and idle UEs using PUCCH and / or PRACH resources is shown in FIG. 19. In some examples, for some MBS services, idle and inactive UEs may also be configured and enabled to transmit CSI feedback.

[0147] In some examples, the UE may be configured with some common PUCCH resources for idle / inactive UEs to be used randomly among the UEs in the group based on the UE ID or other identifier as a seed for transmitting CSI feedback for MBS. In some examples, the PUCCH for CSI feedback may be considered for inactive / idle UEs that maintain uplink synchronization, e.g., UEs in a small cell that are RRC connected or have recently been suspended become inactive / idle.

[0148] In some examples, some common PRACH resources for idle / inactive UEs may be configured with the same MBS transmitted as the CSI feedback / report. The timing of the transmission may be randomly selected by the UEs in the group based on the UE ID or other identifier as a seed for transmitting the CSI feedback for the MBS. The UE identifier may be used as a seed value for determining a probability value to be utilized in determining the timing information.

[0149] In some examples, UEs in certain RRC states, such as RRC inactive and idle, may transmit their CSI feedback using a shortened RACH procedure. The shortened RACH procedure may include transmitting CSI feedback in the PUSCH portion of message A in a two-step RACH without message B. The shortened RACH may alternatively include transmitting CSI feedback in the PUSCH portion of message 3 of a four-step RACH without message 4. The shortened RACH may illustratively utilize messages designated for transmission of CSI feedback as shown in the examples above.

[0150] In some examples, MBS data may be delivered to a UE in both an RRC connected state and an RRC idle or RRC inactive state. Existing CSI feedback mechanisms may not be sufficient to enable proper link adaptation or multi-TRP transmission of MBS data to a UE in an RRC idle or RRC inactive state. Extends CSI feedback to be used for link adaptation and / or multi-TRP operation for UEs in both connected or RRC idle / inactive states.

[0151] In an example embodiment as shown in FIG. 20, the UE may receive one or more messages (e.g., one or more RRC messages). The one or more messages may include a first configuration parameter and a second configuration parameter. The first configuration parameter and the second configuration parameter may be for CSI-RS configuration, CSI-RS measurements, and CSI-RS reporting. The first configuration parameter may be for CSI-RS configuration, CSI-RS measurements, and CSI-RS reporting while the UE is in a first RRC state. The second configuration parameter may be for CSI-RS configuration, CSI-RS measurements, and CSI-RS reporting while the UE is in a second RRC state. The first RRC state may illustratively include an RRC connected state. The second RRC state may illustratively include an RRC idle state or an RRC inactive state.

[0152] The first configuration parameter may indicate multiple parameters or information. The first configuration parameter may indicate a first radio resource for the first CSI-RS reference signal. The first configuration parameter may indicate a first trigger state list. The first configuration parameter may indicate a first frequency domain occupancy for the channel condition measurement. The first configuration parameter may indicate a first measurement configuration. Still further, the first configuration parameter may indicate a first reporting configuration. The first configuration parameter may indicate a first periodicity and offset (e.g., for periodic and semi-persistent reporting). The first configuration parameter may indicate a first CSI-RS based RRM measurement parameter to be used by the UE while the UE is in an RRC connected state.

[0153] The second configuration parameter may indicate multiple parameters or information. The second configuration parameter may indicate a second radio resource for a second CSI-RS reference signal. The second configuration parameter may indicate a second trigger state list. The second configuration parameter may indicate a second frequency domain occupancy for the channel condition measurement. The second configuration parameter may indicate a second measurement configuration. The second configuration parameter may indicate a second reporting configuration. The second configuration parameter may indicate a second periodicity and offset (e.g., for periodic and semi-persistent reporting). The second configuration parameter may indicate a second CSI-RS based RRM measurement parameter to be used by the UE while the UE is in an RRC connected state.

[0154] The UE may receive the first configuration parameter and the second configuration parameter while the UE is in an RRC connected state. In some examples, the first configuration parameter may be configured for delivering data associated with the MBS service. In some examples, the second configuration parameter may be configured for delivering data associated with the MBS service. In some examples, the UE may be configured with different CSI-RS related parameters (e.g., CSI-RS measurements and reporting) for the MBS and unicast services (e.g., different CSI-RS related parameters for the MBS and unicast services when the UE is in an RRC connected state). In some examples, the second configuration parameters for the UE in an RRC idle state or an RRC inactive state may be used by the UE only for the MBS service. In some examples, the UE may receive the first configuration parameter, the second configuration parameter, or a combination as part of the MBS configuration (e.g., included in a message received over a logical multicast control channel). In some examples, the logical multicast control channel may include the second configuration parameter and may further include scheduling information for receiving the MBS data. In some examples, the UE may transmit an MBS configuration request and / or an MBS interest indication message and may receive a first message including second configuration parameters for CSI measurement and reporting while in an RRC idle or RRC inactive state. In some examples, the UE may receive an RRC connected state indicating a command to transition from an RRC idle or RRC inactive state (e.g., from a first RRC state to a second RRC state). The UE may receive the second configuration parameter in a release message. In some examples, the UE may receive the second configuration parameter in an information element (e.g., a suspendconfig IE) of an RRC release message indicating a command to transition the UE to an RRC inactive state.

[0155] While in the RRC connected state, the UE may use a first configuration parameter and may transmit a first CSI report based on the first configuration parameter, and while in the RRC idle state or the RRC inactive state, the UE may use a second configuration parameter and may transmit a second CSI report based on the second configuration parameter.

[0156] In some examples, the UE may transmit both the first CSI report or the second CSI report based on a random trigger or possibly processing a probability value. The UE may determine the probability value based on an identifier of the UE (e.g., C-RNTI or other UE ID). The UE may use the identifier of the UE to determine a seed for calculating the probability value. In some examples, the UE may transmit both the first CSI report or the second CSI report based on a request / command from the base station (e.g., based on a CSI request field of the DCI). In some examples, the UE may transmit the first CSI report, the second CSI report, or both periodically or semi-persistently. In some examples, the UE may transmit the first CSI report using an uplink control channel (e.g., PUCCH).

[0157] In some examples, the UE may transmit the second CSI report (while in an RRC idle state or an RRC inactive state) using an uplink control channel (e.g., PUCCH), for example, when the UE is uplink synchronized (e.g., based on a determination that the UE is uplink synchronized, e.g., when the UE has a valid timing advance and / or is operating in a small cell). In some examples, the UE may transmit the second CSI report based on a random access process. For example, the UE may transmit the second CSI report based on an uplink shared channel (e.g., PUSCH) transmitted during the random access process (e.g., the PUSCH portion of Msg A or Msg 3). The random access process may be an abbreviated random access process (e.g., abbreviated 2-step random access process without Msg B, or abbreviated 4-step random access process without Msg 4). In these examples, the CSI report is associated with a designated message.

[0158] In some examples, in response to transmitting the first CSI report, in an RRC connected state, the UE may receive first scheduling information. The base station may transmit the first scheduling information to the UE based on one or more CSI reports from one or more UEs, including the first CSI report from the UE. The UE may receive the first scheduling information based on one or more first scheduling DCIs. The first scheduling information (e.g., received via one or more first DCIs) may include one or more fields indicating a first TCI state. In some examples, the first configuration parameter may include a first quasi-co-location configuration parameter indicating a first plurality of TCI states including the first TCI state. The first TCI state may indicate one or more first TRPs. In some examples, the one or more first TRPs may be associated with one or more first DUs of the base station. The UE may receive first data (e.g., MBS data) based on the one or more first TRPs. In some examples, in response to transmitting the second CSI report, the UE may receive the second scheduling information in an RRC idle state or an RRC inactive state. The UE may receive the second scheduling information based on the one or more second scheduling DCIs. The base station may transmit the second scheduling information to the UE based on one or more CSI reports from one or more UEs, including the second CSI report from the UE. The second scheduling information (e.g., received via one or more second DCIs) may be transmitted to the UE. The UE may receive second data (e.g., MBS data) based on the second TRP. In some examples, the second configuration parameter may include a second quasi-co-location configuration parameter indicating a second plurality of TCI states including the second TCI state. The second TCI state may indicate one or more second TRPs. In some examples, the one or more second TRPs may be associated with one or more second DUs of the base station. The UE may receive second data (e.g., MBS data) based on the one or more second TRPs.

[0159] In an example embodiment as shown in FIG. 21, the UE may receive one or more messages including configuration parameters. In one example, the one or more messages may include one or more RRC messages. The one or more messages may include CSI-RS measurement and reporting parameters. The one or more messages may include various types of information. The one or more messages may include radio resources for CSI-RS reference signals. The one or more messages may include a trigger state list. The one or more messages may include frequency domain occupancy for channel condition measurements. The one or more messages may include measurement configurations. The one or more messages may include reporting configurations. The one or more messages may include periodicity and offsets (e.g., for periodic and semi-persistent reporting). The one or more messages may include CSI-RS based RRM measurement parameters.

[0160] The configuration parameters may be for CSI-RS measurements and CSI reports associated with the MBS service. The UE may generate and / or determine to generate a CSI report associated with the MBS service based on the configuration parameters and may determine that a scheduled transmission of the CSI report is at a first timing. The UE may drop the CSI report based on a first timing of the scheduled CSI report to collide with a second timing of an uplink channel (e.g., PUSCH, PUCCH, PRACH) or an uplink signal (e.g., SRS). When one or more first symbols used for transmission of a first uplink channel used for transmission of the CSI report collide with one or more second symbols of the uplink channel or uplink signal. In some examples, the UE may drop the CSI report based on the CSI report being associated with the MBS service. In some examples, the uplink channel or uplink signal may be associated with a priority, and dropping the CSI report may be based on the priority of the uplink channel or uplink signal. The priority associated with the uplink signal may be lower than, higher than, or equal to the priority of the CSI report, which in some embodiments may include or be replaced by UE feedback (e.g., HARQ feedback), as described above.

[0161] In one embodiment, a user equipment (UE) may receive one or more messages including first configuration parameters for channel state information-reference signal (CSI-RS) measurements and CSI reporting in a radio resource control (RRC) connected state and second configuration parameters for CSI-RS measurements and CSI reporting in an RRC idle state or an RRC inactive state. The UE may transmit the first CSI report based on the first configuration parameters when the UE is in an RRC connected state. The UE may transmit the second CSI report based on the second configuration parameters when the UE is in an RRC idle state or when the UE is in an RRC inactive state.

[0162] In some embodiments, transmitting the first channel state information (CSI) report may be via an uplink control channel.

[0163] In some embodiments, transmitting the second channel state information (CSI) report comprises: In some embodiments, a UE may determine that a user equipment (UE) uplink is time synchronized when the UE is in a radio resource control (RRC) idle state or an RRC inactive state.

[0164] In some embodiments, transmitting the second channel state information (CSI) report may be based on a random access process. In some embodiments, the random access process may be a shortened 4-step random access process without Msg 4 and a shortened 4-step random access process without Msg 4. In some embodiments, transmitting the second channel state information (CSI) report may be via Msg 3 of the four-step random access process. In some embodiments, transmitting the second channel state information (CSI) report may be via Msg A of the two-step random access process.

[0165] In some embodiments, the second configuration parameter may be associated with delivery of Multicast Broadcast Service (MBS) data during a Radio Resource Control (RRC) idle state or an RRC inactive state.

[0166] In some embodiments, the one or more messages may include a first message received in response to a Multicast Broadcast Service (MBS) configuration request, and the first message may include the second configuration parameters.

[0167] In some embodiments, a user equipment (UE) may receive a logical multicast control channel carrying a configuration message including the second configuration parameter, In some embodiments, the logical multicast control channel may further carry scheduling information for receiving multicast broadcast service (MBS) data.

[0168] In some embodiments, the one or more messages may include a radio resource control (RRC) release message indicating a command to release the RRC connection, the RRC release message may include the second configuration parameters, hi some embodiments, the RRC release message may include a suspendconfig information element (IE) indicating the second configuration parameters.

[0169] In some embodiments, transmitting the second channel state information (CSI) report may be based on a random trigger. In some embodiments, the random trigger may be based on a user equipment (UE) identifier. In some embodiments, the user equipment (UE) identifier may be a Cell Random Network Temporary Identifier (C-RNTI). In some embodiments, the user equipment (UE) identifier may be used as a seed for determining a probability value indicating a random trigger.

[0170] In some embodiments, the second channel state information (CSI) report may be transmitted based on a request from a base station (BS).

[0171] In some embodiments, the second channel state information (CSI) report may be transmitted semi-persistently.

[0172] In some embodiments, the UE may receive first scheduling information in response to transmitting a first channel state information (CSI) report, the first scheduling information indicating a first transmission configuration indication (TCI) state associated with one or more first transmission reception points (TRPs). The UE may also receive a second scheduling information in response to transmitting a second channel state information (CSI) report, the first scheduling information indicating a second transmission configuration indication (TCI) state associated with one or more second transmission reception points (TRPs). The second scheduling information may be received.

[0173] In some embodiments, the UE may receive the first data via one or more first transmission reception points (TRPs) when in a radio resource control (RRC) connected state, and the UE may receive the second data via one or more second transmission reception points (TRPs) when in an RRC idle state or an RRC inactive state.

[0174] In some embodiments, one or more first transmission receiving points (TRPs) may be associated with one or more first distributed units (DUs) of the base station, and one or more second TRPs may be associated with one or more second DUs of the base station. In some embodiments, the first scheduling information may be received via at least one first downlink control information (DCI) including a first field indicating a first transmission configuration indication (TCI) state. Furthermore, the second scheduling information may be received via at least one second DCI including a second field indicating a second TCI state. In some embodiments, receiving the first scheduling information may be based on a first plurality of channel state information (CSI) reports from a first plurality of user equipments (UEs), including a first CSI report by the UE. Additionally, receiving the second scheduling information may be based on a second plurality of CSI reports from a second plurality of UEs, including a second CSI report by the UE.

[0175] In some embodiments, the first configuration parameter may include a first quasi-colocation configuration parameter and the second configuration parameter may include a second quasi-colocation configuration parameter. In some embodiments, the first quasi-colocation configuration parameter may indicate a first plurality of Transmission Configuration Indication (TCI) states and the second quasi-colocation configuration parameter may indicate a second plurality of TCI states.

[0176] In some embodiments, receiving the one or more messages may be while a user equipment (UE) is in a radio resource control (RRC) connected state.

[0177] In one embodiment, a user equipment (UE) may receive configuration parameters for channel state information-reference signal (CSI-RS) measurements and CSI reporting associated with a multicast broadcast service (MBS). The UE may determine a CSI report associated with the MBS service for transmission at a first timing based on the configuration parameters. The UE may drop the CSI report based on a first timing of the CSI report colliding with a second timing associated with at least one of an uplink channel or an uplink signal.

[0178] In some embodiments, dropping the channel state information (CSI) report may be further based on the CSI report being associated with a multicast and broadcast service (MBS) service.

[0179] In some embodiments, dropping a channel state information (CSI) report may be based on a priority associated with an uplink channel or signal.

[0180] In some embodiments, the first timing of the channel state information (CSI) report may collide with the second timing of the uplink channel when one or more first symbols of the first uplink channel used for transmitting the CSI report collide with one or more second symbols of the uplink channel. When one or more first symbols of the first uplink channel used for transmitting the CSI report collide with one or more second symbols of the uplink signal, the first timing of the CSI report may collide with the second timing of the uplink signal. 2. In some embodiments, the first uplink channel may be an uplink control channel. In some embodiments, the first uplink channel may be an uplink shared channel.

[0181] The example blocks and modules described in this disclosure with respect to various example 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 conjunction with a DSP core, or any other such configuration).

[0182] 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 for implementation of the functions. Other examples for implementation of the functions disclosed herein are also within the scope of this disclosure. Implementation of the functions may be through physically co-located or distributed elements (e.g., in various locations), including being distributed such that portions of the functions are implemented in different physical locations.

[0183] Non-transitory computer readable media includes, but is not limited to, non-transitory computer storage media. Non-transitory storage media can be accessed by general purpose or special purpose computers. 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 disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, and the like. Non-transitory media can be used to carry or store desired program code means (e.g., instructions and / or data structures) and can be accessed by general purpose or special purpose computers or general purpose or special purpose processors. In some examples, the software / program code can 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 media. Combinations of the above examples are also included within the scope of computer-readable media.

[0184] As used in this disclosure, the use of the term "or" in a list of items indicates an inclusive list. A list of items may be preceded by a phrase such as "at least one of" or "one or more of." 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" may be based on both condition A and condition B without departing from the scope of this disclosure.

[0185] As used herein, the terms "comprise", "include" or "contain" may be used interchangeably and have the same meaning, It should be interpreted 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 recited elements in the list are present, but 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.

[0186] The present disclosure describes exemplary configurations in conjunction with the accompanying drawings, which do not represent all examples that may be implemented or all configurations 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 "example, instance, or example." By reading this disclosure, including the description of the embodiments and the drawings, it will be understood by those skilled in the art that the technology disclosed herein may be implemented using alternative embodiments. Those skilled in the art will understand that the embodiments described herein, or specific features of the embodiments, may be combined to arrive at yet other embodiments for implementing the technology described in the present 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.

[0187] Supplementary Note 1. A method for channel state information (CSI) feedback, comprising: Receiving, by a user equipment (UE), one or more messages, the one or more messages comprising: first configuration parameters for channel state information - reference signal (CSI-RS) measurements and CSI reporting in a first radio resource control (RRC) state; and second configuration parameters for the CSI-RS measurements and the CSI reporting in a second RRC state. transmitting a first CSI report based on the first configuration parameter when the UE is in the first RRC state; and transmitting a second CSI report based on the second configuration parameters when the UE is in the second RRC state.

[0188] Supplementary Note 2. The method of Supplementary Note 1, wherein transmitting the first CSI report includes transmitting the first CSI report over an uplink control channel.

[0189] Supplementary Note 3. The method of Supplementary Note 1, wherein transmitting the second CSI report includes transmitting the second CSI report over an uplink control channel.

[0190] Supplementary Note 4. The method of Supplementary Note 3, further comprising determining that an uplink of the user equipment (UE) is time synchronized when the UE is in the second RRC state.

[0191] Supplementary Note 5. The method of claim 1, wherein transmitting the second CSI report includes transmitting the second CSI report based on a random access process.

[0192] Addendum 6. The method according to Addendum 5, wherein the random access process corresponds to a shortened 4-step random access process without message Msg 4.

[0193] Addendum 7. The method according to Addendum 5, wherein the random access process corresponds to a shortened two-step random access process without message Msg B.

[0194] Supplementary Note 8. The method of Supplementary Note 5, wherein transmitting the second CSI report includes transmitting the second CSI report via a designated message of a four-step random access process.

[0195] Supplementary Note 9. The method of Supplementary Note 5, wherein transmitting the second CSI report includes transmitting the second CSI report via a designated message of a two-step random access process.

[0196] Supplementary Note 10. The method of Supplementary Note 1, wherein the second configuration parameter is associated with delivery of Multicast Broadcast Service (MBS) data during the second RRC state.

[0197] Addendum 11. The method of Addendum 1, wherein receiving the one or more messages includes receiving the one or more messages in response to a Multicast Broadcast Service (MBS) configuration request, the received one or more messages including the second configuration parameters.

[0198] Supplementary Note 12. The method of Supplementary Note 1, wherein receiving the one or more messages includes receiving a logical multicast control channel carrying a configuration message including the second configuration parameter.

[0199] Supplementary Note 13. The method of Supplementary Note 12, wherein the logical multicast control channel further carries scheduling information for receiving Multicast Broadcast Service (MBS) data.

[0200] Supplementary Note 14. The method of Supplementary Note 1, wherein receiving the one or more messages includes receiving an RRC release message including a command to release an RRC connection, the RRC release message including the second configuration parameter.

[0201] Supplementary Note 15. The method of Supplementary Note 14, wherein the RRC release message includes an information element (IE) including the second configuration parameter.

[0202] Supplementary Note 16. The method of Supplementary Note 1, wherein transmitting the second CSI report is based on a random trigger.

[0203] Additive 17. The method of Additive 15, wherein the random trigger is based on an identifier of the UE.

[0204] Supplementary Note 18. The method of Supplementary Note 17, wherein the identifier of the UE is a Cell Random Network Temporary Identifier (C-RNTI).

[0205] Supplementary Note 19. The method of Supplementary Note 17, further comprising determining a probability value indicating the random trigger based on a seed value, the seed value corresponding to the identifier of the UE.

[0206] Supplementary Note 20. The method of Supplementary Note 1, wherein transmitting the second CSI report includes transmitting the second CSI report in response to a request from a base station (BS).

[0207] Addition 21. The method of addition 1, wherein the second CSI report is transmitted semi-persistently.

[0208] Supplementary Note 22. The method of Supplementary Note 1, further comprising receiving first scheduling information in response to transmitting the first CSI report, the first scheduling information indicating a first Transmission Configuration Indication (TCI) state associated with one or more first Transmission Reception Points (TRPs).

[0209] Supplementary Note 23. The method of Supplementary Note 22, further comprising receiving first data via the one or more TRPs when in the first RRC state.

[0210] Addendum 24. The method of Addendum 22, wherein the one or more first TRPs are associated with one or more first distributed units (DUs) of a base station.

[0211] Supplementary Note 25. The method of Supplementary Note 22, wherein receiving the first scheduling information includes receiving the first scheduling information via at least one first downlink control information (DCI) including a first field indicating the first transmission configuration indication (TCI) state.

[0212] Supplementary Note 26. The method of Supplementary Note 22, wherein receiving the first scheduling information includes receiving the first scheduling information based on a plurality of CSI reports.

[0213] Supplementary Note 27. The method of Supplementary Note 1, further comprising receiving second scheduling information in response to transmitting the second CSI report, the second scheduling information indicating a second TCI state associated with one or more second TRPs.

[0214] Supplementary Note 28. The method of Supplementary Note 27, further comprising receiving second data via the one or more second TRPs when in the RRC idle state or when in the RRC inactive state.

[0215] Addendum 29. The method of Addendum 27, wherein the one or more second TRPs are associated with one or more second DUs of the base station.

[0216] Supplementary Note 30. The method of claim 27, wherein the second scheduling information is received via at least one second DCI including a second field indicating the second TCI state.

[0217] Supplementary Note 31. The method of Supplementary Note 27, wherein receiving the second scheduling information is based on a second plurality of CSI reports from a second plurality of UEs, the second plurality of CSI reports including the second CSI report by the UE.

[0218] Addendum 32. The method of Addendum 1, wherein the first configuration parameter includes a first quasi-colocation configuration parameter.

[0219] Addendum 33. The method of Addendum 32, wherein the first quasi-co-location configuration parameter indicates a first plurality of TCI states.

[0220] Addendum 34. The method of Addendum 1, wherein the second configuration parameters include second quasi-collocation configuration parameters.

[0221] Addendum 35. The method of Addendum 34, wherein the second quasi-co-location configuration parameter indicates a second plurality of TCI states.

[0222] Supplementary Note 36. The method of Supplementary Note 1, wherein receiving the one or more messages occurs while the UE is in the first RRC state.

[0223] 37. The method of claim 1, wherein the first RRC state corresponds to an RRC connected state. .

[0224] Supplementary Note 38. The method of Supplementary Note 1, wherein the second RRC state corresponds to at least one of an RRC idle state or an RRC inactive state.

[0225] Addition 39. A method of channel state information (CSI) feedback for a multicast broadcast service (MBS), comprising: Receiving, by a user equipment (UE), configuration parameters for channel state information-reference signal (CSI-RS) measurements and CSI reports associated with a multicast broadcast service (MBS); determining a CSI report associated with the MBS for transmission at a first timing based on the received configuration parameters; dropping the CSI report if the first timing of the CSI report conflicts with a second timing associated with at least one of an uplink channel or an uplink signal.

[0226] Addition 40. The method of addition 39, wherein the dropping of the CSI report is further based on the CSI report being associated with the Multicast and Broadcast Service (MBS) service.

[0227] 41. The method of claim 39, wherein the dropping of the CSI report is further based on a priority associated with the uplink channel or signal.

[0228] Supplementary Note 42. The method of Supplementary Note 39, wherein the first timing of the CSI report collides with the second timing of the uplink channel if one or more first symbols of a first uplink channel used for transmission of the CSI report collide with one or more second symbols of the uplink channel.

[0229] Supplementary Note 43. The method of Supplementary Note 42, wherein the first timing of the CSI report collides with the second timing of the uplink signal if one or more first symbols of the first uplink channel used for transmission of the CSI report collides with one or more second symbols of the uplink signal.

[0230] Addition 44. The method of Addition 42, wherein the first uplink channel is an uplink control channel.

[0231] Addition 45. The method of Addition 42, wherein the first uplink channel is an uplink shared channel.

[0232] Addendum 46. An apparatus for use in wireless communications, comprising: an antenna for use in transmitting electromagnetic signals; a memory for maintaining computer readable code; a processor for executing the computer readable code, the computer readable code configuring the device to: receiving one or more messages, the one or more messages comprising: first configuration parameters for channel state information - reference signal (CSI-RS) measurements and CSI reporting in a first radio resource control (RRC) state; and second configuration parameters for the CSI-RS measurements and the CSI reporting in a second RRC state. When the UE is in the first RRC state, a second RRC state is established based on the first configuration parameter. transmitting a CSI report of one; and transmitting a second CSI report based on the second configuration parameter when the UE is in the second RRC state.

[0233] Supplementary Note 47. The apparatus of Supplementary Note 46, wherein the apparatus transmits the first CSI report over an uplink control channel.

[0234] Supplementary Note 48. The apparatus of Supplementary Note 46, wherein the apparatus transmits the second CSI report over an uplink control channel.

[0235] Clause 49. The apparatus of clause 46, wherein the apparatus determines that an uplink of a user equipment (UE) is time synchronized when the UE is in the second RRC state.

[0236] Supplementary Note 50. The apparatus of Supplementary Note 46, wherein the apparatus transmits the second CSI report based on a random access process.

[0237] Clause 51. The apparatus of clause 50, wherein the random access process corresponds to a shortened four-step random access process without message Msg 4.

[0238] Clause 52. The apparatus of clause 50, wherein the random access process corresponds to a shortened two-step random access process without message Msg B.

[0239] Supplementary Note 53. The apparatus of Supplementary Note 50, wherein the apparatus transmits the second CSI report via a designated message of a four-step random access process.

[0240] 54. The apparatus of claim 50, wherein the apparatus transmits the second CSI report via a designated message of a two-step random access process.

[0241] Addition 55. The apparatus of Addition 46, wherein the second configuration parameter is associated with delivery of Multicast Broadcast Service (MBS) data during the second RRC state.

[0242] Addendum 56. The apparatus of Addendum 46, wherein receiving the one or more messages includes receiving the one or more messages in response to a Multicast Broadcast Service (MBS) configuration request, the received one or more messages including the second configuration parameters.

[0243] Addition 57. The apparatus of Addition 46, wherein the apparatus receives a logical multicast control channel carrying a configuration message including the second configuration parameter.

[0244] Addition 58. The apparatus of Addition 57, wherein the logical multicast control channel further carries scheduling information for receiving Multicast Broadcast Service (MBS) data.

[0245] Supplementary Note 59. The apparatus of Supplementary Note 46, wherein receiving the one or more messages includes receiving an RRC release message including a command to release an RRC connection, the RRC release message including the second configuration parameter.

[0246] Supplementary Note 60. The apparatus of Supplementary Note 59, wherein the RRC release message includes an information element (IE) including the second configuration parameter.

[0247] Appendix 61. The apparatus of Appendix 46, wherein transmitting the second CSI report is based on a random trigger.

[0248] Additive 62. The apparatus of Additive 61, wherein the random trigger is based on an identifier of the UE.

[0249] Addition 63. The apparatus of Addition 62, wherein the identifier of the UE is a Cell Random Network Temporary Identifier (C-RNTI).

[0250] Addition 64. The apparatus of Addition 62, wherein the apparatus determines a probability value indicating the random trigger based on a seed value, the seed value corresponding to the identifier of the UE.

[0251] Appendix 65. The apparatus of Appendix 46, wherein transmitting the second CSI report includes transmitting the second CSI report in response to a request from a base station (BS).

[0252] Additive 66. The apparatus of Additive 46, wherein the second CSI report is transmitted semi-persistently.

[0253] Supplementary Note 67. The apparatus of Supplementary Note 46, wherein the apparatus receives first scheduling information in response to transmitting the first CSI report, the first scheduling information indicating a first transmission configuration indication (TCI) state associated with one or more first transmission reception points (TRPs).

[0254] Addition 68. The apparatus of Addition 67, wherein the apparatus receives first data via the one or more TRPs when in the first RRC state.

[0255] Addendum 69. The apparatus of Addendum 67, wherein the one or more first TRPs are associated with one or more first distributed units (DUs) of a base station.

[0256] Supplementary Note 70. The apparatus of Supplementary Note 67, further comprising receiving first scheduling information via at least one first downlink control information (DCI) including a first field indicating the first transmission configuration indication (TCI) state.

[0257] Supplementary Note 71. The apparatus of Supplementary Note 67, wherein the apparatus receives first scheduling information based on a plurality of CSI reports.

[0258] Supplementary Note 72. The apparatus of Supplementary Note 46, wherein the apparatus receives second scheduling information in response to transmitting the second CSI report, the second scheduling information indicating a second TCI state associated with one or more second TRPs.

[0259] Supplementary Note 73. The apparatus of Supplementary Note 72, wherein the apparatus receives second data via the one or more second TRPs when in the RRC idle state or when in the RRC inactive state.

[0260] Addition 74. The apparatus of Addition 72, wherein the one or more second TRPs are associated with one or more second DUs of the base station.

[0261] 75. The apparatus of claim 72, wherein the second scheduling information is received via at least one second DCI including a second field indicating the second TCI status. Place.

[0262] 76. The apparatus of claim 72, wherein the apparatus receives the second scheduling information based on a second plurality of CSI reports from a second plurality of UEs, the second plurality of CSI reports including the second CSI reports by the UEs.

[0263] Addendum 77. The apparatus of Addendum 46, wherein the first configuration parameter includes a first quasi-colocation configuration parameter.

[0264] Clause 78. The apparatus of clause 77, wherein the first quasi-co-location configuration parameter indicates a first plurality of TCI states.

[0265] Clause 79. The apparatus of clause 46, wherein the second configuration parameters include second quasi-colocation configuration parameters.

[0266] Addendum 80. The apparatus of Addendum 79, wherein the second quasi-co-location configuration parameter indicates a second plurality of TCI states.

[0267] Addition 81. The apparatus of Addition 46, wherein the apparatus receives the one or more messages in the first RRC state.

[0268] Addition 82. The apparatus of Addition 46, wherein the first RRC state corresponds to an RRC connected state.

[0269] Addition 83. The apparatus of Addition 46, wherein the second RRC state corresponds to at least one of an RRC idle state or an RRC inactive state.

[0270] Addendum 84. An apparatus for use in wireless communications, comprising: an antenna for use in transmitting electromagnetic signals; a memory for maintaining computer readable code; a processor for executing the computer readable code, the computer readable code configuring the device to: receiving configuration parameters for channel state information-reference signal (CSI-RS) measurements and CSI reports associated with a multicast broadcast service (MBS); determining a CSI report associated with the MBS for transmission at a first timing based on the received configuration parameters; dropping the CSI report if the first timing of the CSI report conflicts with a second timing associated with at least one of an uplink channel or an uplink signal.

[0271] 85. The apparatus of claim 84, wherein the apparatus drops the CSI report based on the CSI report being associated with the Multicast and Broadcast Service (MBS) service.

[0272] 86. The apparatus of claim 84, wherein the apparatus drops the CSI report based on a priority associated with the uplink channel or signal.

[0273] Addition 87. One or more first symbols of a first uplink channel used for transmitting the CSI report are 85. The apparatus of claim 84, wherein the first timing of the CSI report collides with the second timing of the uplink channel if the first timing of the CSI report collides with the second timing of the uplink channel.

[0274] 88. The apparatus of claim 84, wherein the first timing of the CSI report collides with the second timing of the uplink signal if one or more first symbols of the first uplink channel used for transmission of the CSI report collides with one or more second symbols of the uplink signal.

[0275] Additive 89. The apparatus of Additive 87, wherein the first uplink channel is an uplink control channel.

[0276] Additive 90. The apparatus of Additive 87, wherein the first uplink channel is an uplink shared channel.

[0277] Addition 91. A method of channel state information (CSI) feedback, comprising: transmitting, by a base station, one or more messages, the one or more messages comprising: first configuration parameters for channel state information - reference signal (CSI-RS) measurements and CSI reporting in a first radio resource control (RRC) state; and second configuration parameters for the CSI-RS measurements and the CSI reporting in a second RRC state. receiving a first CSI report based on the first configuration parameter when the UE is in the first RRC state; and receiving a second CSI report based on the second configuration parameter when the UE is in the second RRC state.

[0278] Addition 92. A method of channel state information (CSI) feedback for a multicast broadcast service (MBS), comprising: 1. A method comprising: transmitting, by a base station, configuration parameters for channel state information - reference signal (CSI-RS) measurements and a CSI report associated with a Multicast Broadcast Service (MBS), wherein a CSI report associated with the MBS for transmission at a first timing is determined based on the configuration parameters, and the CSI report, in which the first timing of the CSI report conflicts with a second timing associated with at least one of an uplink channel or an uplink signal, is dropped.

[0279] Addition 93. A method for providing user equipment (UE) feedback, comprising: receiving, by the UE, one or more messages, the one or more messages comprising: one or more first configuration parameters for a first UE feedback in a Radio Resource Control (RRC) Connected state; and one or more second configuration parameters for second UE feedback in an RRC idle state or an RRC inactive state. transmitting, by the UE when the UE is in an RRC connected state, the first UE feedback based on the one or more first configuration parameters; transmitting, by the UE, the second UE feedback based on the one or more second configuration parameters when the UE is in the RRC idle state or when the UE is in the RRC inactive state.

[0280] Addition 94. The first UE feedback comprises a first channel state information (CSI) report. and wherein the second UE feedback is a second CSI report and the one or more first and second configuration parameters include parameters for channel state information - reference signal (CSI-RS) measurements.

[0281] 95. The method of claim 93, wherein the first UE feedback is a first Hybrid Automatic Repeat Request (HARQ) feedback and the second UE feedback is a second HARQ feedback.

[0282] Addition 96. A method for providing user equipment (UE) feedback associated with a multicast broadcast service (MBS), the method comprising: receiving, by a UE, one or more configuration parameters for the UE feedback associated with the MBS; determining, by the UE, a first timing for transmission of the UE feedback associated with the MBS based on the one or more configuration parameters; and dropping the UE feedback associated with the MBS from transmission at the first timing when the first timing for the UE feedback collides with a second timing for an uplink channel or an uplink signal.

[0283] Addition 97. The method of Addition 96, wherein the UE feedback includes a channel state information (CSI) report and the one or more configuration parameters include parameters for channel state information-reference signal (CSI-RS) measurements.

[0284] Addition 98. The method of Addition 96, wherein the UE feedback includes Hybrid Automatic Repeat Request (HARQ) feedback.

[0285] Clause 99. The method of clause 96, wherein a priority associated with the uplink channel or signal is equal to, higher than, or lower than a priority associated with the MBS.

[0286] This application claims the benefit of U.S. Provisional Application No. 63 / 115,490, entitled “CHANNEL SATTE INFORMATION (CSI) FEEDBACK FOR MULTICAST,” filed November 18, 2020, which is incorporated by reference in its entirety.

Claims

1. A method for user equipment (UE) feedback associated with a multicast broadcast service (MBS), comprising: receiving, by the UE, first configuration parameters for the MBS, the first configuration parameters for CSI-RS measurement and CSI reporting in an RRC connected state, and second parameters for the MBS, the second configuration parameters for CSI-RS measurement and CSI reporting in an RRC inactive state or an idle state; When the UE is in an RRC connected state, sending a CSI measurement report for the MBS to a base station based on the first configuration parameter by the UE, and when the UE is in an RRC inactive state or an idle state, sending a CSI measurement report for the MBS to a base station based on the second configuration parameter by the UE; and transmitting the measurement report to the base station includes dropping the measurement report based on a priority. method.

2. 1. An apparatus for use in wireless communications, comprising: an antenna for use in transmitting electromagnetic signals; a memory for maintaining computer readable code; a processor for executing the computer readable code; The computer readable code causes the device to: receiving first configuration parameters for a Multicast Broadcast Service (MBS), the first configuration parameters being for CSI-RS measurement and CSI reporting when the UE is in an RRC connected state, and second parameters for the MBS, the second configuration parameters being for CSI-RS measurement and CSI reporting when the UE is in an RRC inactive state or an idle state; sending a CSI measurement report for the MBS to a base station based on the first configuration parameter when the UE is in the RRC connected state, and sending a CSI measurement report for the MBS to a base station based on the second configuration parameter when the UE is in the RRC inactive state or in an idle state; The transmitting of the measurement report to the base station includes dropping the measurement report based on a priority. including, Device.

Images