User-equipment-initiated channel state information reporting and bandwidth part activation

Abstract

A wireless device receives one or more radio resource control (RRC) messages comprising one or more configuration parameters for user-equipment (UE)-initiated channel state information (CSI) reporting. Based on whether the one or more configuration parameters indicating, for an active uplink bandwidth part (BWP), a physical uplink control channel (PUCCH) resource used for the UE-initiated CSI reporting, determining to measure a reference signal for event instances of the UE-initiated CSI reporting. Based on a number of the event instances being equal to, or greater than, a value, transmitting, via the PUCCH resource, a PUCCH transmission for a UE-initiated CSI report.

Description

TITLEUser-Equipment-Initiated Channel State Information Reporting and Bandwidth Part Activation CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 645,129, filed May 9, 2024, which is hereby incorporated by reference in its entirety.BRIEF DESCRIPTION OF THE DRAWINGS

[0002] Examples of several of the various embodiments of the present disclosure are described herein with reference to the drawings.

[0003] FIG. 1A and FIG. 1B illustrate example mobile communication networks in which embodiments of the present disclosure may be implemented.

[0004] FIG. 2A and FIG. 2B respectively illustrate a New Radio (NR) user plane and control plane protocol stack.

[0005] FIG. 3 illustrates an example of services provided between protocol layers of the NR user plane protocol stack of FIG. 2A.

[0006] FIG. 4A illustrates an example downlink data flow through the NR user plane protocol stack of FIG. 2A.

[0007] FIG. 4B illustrates an example format of a MAC subheader in a MAC PDU.

[0008] FIG. 5A and FIG. 5B respectively illustrate a mapping between logical channels, transport channels, and physical channels for the downlink and uplink.

[0009] FIG. 6 is an example diagram showing RRC state transitions of a UE.

[0010] FIG. 7 illustrates an example configuration of an NR frame into which OFDM symbols are grouped.

[0011] FIG. 8 illustrates an example configuration of a slot in the time and frequency domain for an NR carrier.

[0012] FIG. 9 illustrates an example of bandwidth adaptation using three configured BWPs for an NR carrier.

[0013] FIG. 10A illustrates three carrier aggregation configurations with two component carriers.

[0014] FIG. 10B illustrates an example of how aggregated cells may be configured into one or more PUCCH groups.

[0015] FIG. 11A illustrates an example of an SS / PBCH block structure and location.

[0016] FIG. 11 B illustrates an example of CSI-RSs that are mapped in the time and frequency domains.

[0017] FIG. 12A and FIG. 12B respectively illustrate examples of three downlink and uplink beam management procedures.

[0018] FIG. 13A, FIG. 13B, and FIG. 13C respectively illustrate a four-step contention-based random-access procedure, a two-step contention-free random access procedure, and another two-step random access procedure.

[0019] FIG. 14A illustrates an example of CORESET configurations fora bandwidth part.

[0020] FIG. 14B illustrates an example of a CCE-to-REG mapping for DCI transmission on a CORESET and PDCCH processing.

[0021] FIG. 15 illustrates an example of a wireless device in communication with a base station.

[0022] FIG. 16A, FIG. 16B, FIG. 16C, and FIG. 16D illustrate example structures for uplink and downlink transmission.

[0023] FIGs. 17A and 17B are signal flow diagrams illustrating aspects of transmission configuration indicator (TCI) state indication according to the present disclosure.

[0024] FIGs. 18A, 18B, and 18C are signal flow diagrams illustrating aspects of channel state information (CSI) reporting, triggered by the network, according to the present disclosure.

[0025] FIGs. 19A, 19B, and 19C are signal flow diagrams illustrating aspects of CSI reporting, triggered by a wireless device, according to the present disclosure.

[0026] FIG. 20 is a signal flow diagram illustrating aspects according to the present disclosure.

[0027] FIGs. 21 A and 21 B are signal flow diagrams illustrating aspects according to the present disclosure.

[0028] FIG. 22 is a signal flow diagram, between layers of a wireless device, illustrating aspects according to the present disclosure.

[0029] FIGs. 23A and 23B are signal flow diagrams illustrating aspects according to the present disclosure.

[0030] FIG. 24 is a flowchart illustrating aspects of a process according to the present disclosure.

[0031] FIGs. 25A, 25B, and 25C are flowcharts illustrating aspects of a process according to the present disclosure.

[0032] FIG. 26 is a flowchart illustrating aspects of a process according to the present disclosure.

[0033] FIG. 27 is a flowchart illustrating aspects of a process according to the present disclosure.DETAILED DESCRIPTION

[0034] In the present disclosure, various embodiments are presented as examples of how the disclosed techniques may be implemented and / or how the disclosed techniques may be practiced in environments and scenarios. It will be apparent to persons skilled in the relevant art that various changes in form and detail can be made therein without departing from the scope. In fact, after reading the description, it will be apparent to one skilled in the relevant art how to implement alternative embodiments. The present embodiments should not be limited by any of the described exemplary embodiments. The embodiments of the present disclosure will be described with reference to the accompanying drawings. Limitations, features, and / or elements from the disclosed example embodiments may be combined to create further embodiments within the scope of the disclosure. Any figures which highlight the functionality and advantages, are presented for example purposes only. The disclosed architecture is sufficiently flexible and configurable, such that it may be utilized in ways other than that shown. For example, the actions listed in any flowchart may be re-ordered or only optionally used in some embodiments.

[0035] Embodiments may be configured to operate as needed. The disclosed mechanism may be performed when certain criteria are met, for example, in a wireless device, a base station, a radio environment, a network, a combination of the above, and / or the like. Example criteria may be based, at least in part, on for example, wireless device or network node configurations, traffic load, initial system set up, packet sizes, traffic characteristics, a combination of theabove, and / or the like. When the one or more criteria are met, various example embodiments may be applied. Therefore, it may be possible to implement example embodiments that selectively implement disclosed protocols.

[0036] A base station may communicate with a mix of wireless devices. Wireless devices and / or base stations may support multiple technologies, and / or multiple releases of the same technology. Wireless devices may have some specific capability(ies) depending on wireless device category and / or capabil ity(ies). When this disclosure refers to a base station communicating with a plurality of wireless devices, this disclosure may refer to a subset of the total wireless devices in a coverage area. This disclosure may refer to, for example, a plurality of wireless devices of a given LTE or 5G release with a given capability and in a given sector of the base station. The plurality of wireless devices in this disclosure may refer to a selected plurality of wireless devices, and / or a subset of total wireless devices in a coverage area which perform according to disclosed methods, and / or the like. There may be a plurality of base stations ora plurality of wireless devices in a coverage area that may not comply with the disclosed methods, for example, those wireless devices or base stations may perform based on older releases of LTE or 5G technology.

[0037] In this disclosure, “a” and “an” and similar phrases are to be interpreted as “at least one” and “one or more.” Similarly, any term that ends with the suffix “(s)” is to be interpreted as “at least one” and “one or more.” In this disclosure, the term “may” is to be interpreted as “may, for example." In other words, the term “may" is indicative that the phrase following the term “may” is an example of one of a multitude of suitable possibilities that may, or may not, be employed by one or more of the various embodiments. The terms “comprises” and “consists of”, as used herein, enumerate one or more components of the element being described. The term “comprises” is interchangeable with “includes” and does not exclude unenumerated components from being included in the element being described. By contrast, “consists of’ provides a complete enumeration of the one or more components of the element being described. The term “based on”, as used herein, should be interpreted as “based at least in part on” rather than, for example, “based solely on”. The term “and / or” as used herein represents any possible combination of enumerated elements. For example, “A, B, and / or C” may represent A; B; C; A and B; A and C; B and C; or A, B, and C.

[0038] If A and B are sets and every element of A is an element of B, A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B = {celH , cell2} are: {celH }, {cell2}, and {celH, cell2}. The phrase “based on” (or equally “based at least on”) is indicative that the phrase following the term “based on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “in response to” (or equally “in response at least to”) is indicative that the phrase following the phrase “in response to” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “depending on” (or equally “depending at least to”) is indicative that the phrase following the phrase “depending on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “employing / using” (or equally “employing / using at least’) is indicative that the phrase following the phrase“employing / usi ng” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments.

[0039] The term configured may relate to the capacity of a device whether the device is in an operational or non- operational state. Configured may refer to specific settings in a device that affect or implement the operational characteristics of the device whether the device is in an operational or non-operational state. In other words, the hardware, software, firmware, registers, memory values, and / or the like may be “configured” within a device, whether the device is in an operational or nonoperational state, to provide the device with specific characteristics. Terms such as “a control message to cause in a device” may mean that a control message has parameters that may be used to configure specific characteristics or may be used to implement certain actions in the device, whether the device is in an operational or non-operational state.

[0040] In this disclosure, parameters (or equally called, fields, or Information elements: lEs) may comprise one or more information objects, and an information object may comprise one or more other objects. For example, if parameter (IE) N comprises parameter (IE) M, and parameter (IE) M comprises parameter (IE) K, and parameter (IE) K comprises parameter (information element) J. Then, for example, N comprises K, and N comprises J. In an example embodiment, when one or more messages comprise a plurality of parameters, it implies that a parameter in the plurality of parameters is in at least one of the one or more messages, but does not have to be in each of the one or more messages.

[0041] Many features presented are described as being optional through the use of “may” or the use of parentheses. For the sake of brevity and legibility, the present disclosure does not explicitly recite each and every permutation that may be obtained by choosing from the set of optional features. The present disclosure is to be interpreted as explicitly disclosing all such permutations. For example, a system described as having three optional features may be embodied in seven ways, namely with just one of the three possible features, with any two of the three possible features or with three of the three possible features.

[0042] Many of the elements described in the disclosed embodiments may be implemented as modules. A module is defined here as an element that performs a defined function and has a defined interface to other elements. The modules described in this disclosure may be implemented in hardware, software in combination with hardware, firmware, wetware (e.g. hardware with a biological element) ora combination thereof, which may be behaviorally equivalent. For example, modules may be implemented as a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, MATLAB or the like) or a modeling / simulation program such as Simulink, Stateflow, GNU Octave, or LabVI E WMathScript. It may be possible to implement modules using physical hardware that incorporates discrete or programmable analog, digital and / or quantum hardware. Examples of programmable hardware comprise: computers, microcontrollers, microprocessors, applicationspecific integrated circuits (ASICs); field programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers and microprocessors are programmed using languages such as assembly, C,C++ or the like. FPGAs, ASICs and CPLDs are often programmed using hardware description languages (HDL) such as VHSIC hardware description language (VHDL) or Verilog that configure connections between internal hardware modules with lesser functionality on a programmable device. The mentioned technologies are often used in combination to achieve the result of a functional module.

[0043] FIG. 1A illustrates an example of a mobile communication network 100 in which embodiments of the present disclosure may be implemented. The mobile communication network 100 may be, for example, a public land mobile network (PLMN) run by a network operator. As illustrated in FIG. 1A, the mobile communication network 100 includes a core network (CN) 102, a radio access network (RAN) 104, and a wireless device 106.

[0044] The CN 102 may provide the wireless device 106 with an interface to one or more data networks (DNs), such as public DNs (e.g., the Internet), private DNs, and / or intra-operator DNs. As part of the interface functionality, the CN 102 may set up end-to-end connections between the wireless device 106 and the one or more DNs, authenticate the wireless device 106, and provide charging functionality.

[0045] The RAN 104 may connect the CN 102 to the wireless device 106 through radio communications over an air interface. As part of the radio communications, the RAN 104 may provide scheduling, radio resource management, and retransmission protocols. The communication direction from the RAN 104 to the wireless device 106 over the air interface is known as the downlink and the communication direction from the wireless device 106 to the RAN 104 over the air interface is known as the uplink. Downlink transmissions may be separated from uplink transmissions using frequency division duplexing (FDD), time-division duplexing (TDD), and / or some combination of the two duplexing techniques.

[0046] The term wireless device may be used throughout this disclosure to refer to and encompass any mobile device or fixed (non-mobile) device for which wireless communication is needed or usable. For example, a wireless device maybe a telephone, smartphone, tablet, computer, laptop, sensor, meter, wearable device, Internet of Things (loT) device, vehicle roadside unit (RSU), relay node, automobile, and / or any combination thereof. The term wireless device encompasses other terminology, including user equipment (UE), user terminal (UT), access terminal (AT), mobile station, handset, wireless transmit and receive unit (WTRU), and / or wireless communication device.

[0047] The RAN 104 may include one or more base stations (not shown). The term base station may be used throughout this disclosure to refer to and encompass a Node B (associated with UMTS and / or 3G standards), an Evolved Node B (eNB, associated with E-UTRA and / or 4G standards), a remote radio head (RRH), a baseband processing unit coupled to one or more RRHs, a repeater node or relay node used to extend the coverage area of a donor node, a Next Generation Evolved Node B (ng-eNB), a Generation Node B (g N B, associated with NR and / or 5G standards), an access point (AP, associated with, for example, Wi-Fi or any other suitable wireless communication standard), and / or any combination thereof. A base station may comprise at least one g N B Central Unit (gNB-CU) and at least one a g NB Distributed Unit (gNB-DU).

[0048] A base station included in the RAN 104 may include one or more sets of antennas for communicating with the wireless device 106 over the air interface. For example, one or more of the base stations may include three sets of antennas to respectively control three cells (or sectors). The size of a cell may be determined by a range at which a receiver (e.g., a base station receiver) can successfully receive the transmissions from a transmitter (e.g., a wireless device transmitter) operating in the cell. Together, the cells of the base stations may provide radio coverage to the wireless device 106 over a wide geographic area to support wireless device mobility.

[0049] In addition to three-sector sites, other implementations of base stations are possible. For example, one or more of the base stations in the RAN 104 may be implemented as a sectored site with more or less than three sectors. One or more of the base stations in the RAN 104 may be implemented as an access point, as a baseband processing unit coupled to several remote radio heads (RRHs), and / or as a repeater or relay node used to extend the coverage area of a donor node. A baseband processing unit coupled to RRHs may be part of a centralized or cloud RAN architecture, where the baseband processing unit may be either centralized in a pool of baseband processing units or virtualized. A repeater node may amplify and rebroadcast a radio signal received from a donor node. A relay node may perform the same / similar functions as a repeater node but may decode the radio signal received from the donor node to remove noise before amplifying and rebroadcasting the radio signal.

[0050] The RAN 104 may be deployed as a homogenous network of macrocell base stations that have similar antenna patterns and similar high-level transmit powers. The RAN 104 may be deployed as a heterogeneous network. In heterogeneous networks, small cell base stations may be used to provide small coverage areas, for example, coverage areas that overlap with the comparatively larger coverage areas provided by macrocell base stations. The small coverage areas may be provided in areas with high data traffic (or so-called “hotspots”) or in areas with weak macrocell coverage. Examples of small cell base stations include, in order of decreasing coverage area, microcell base stations, picocell base stations, and femtocell base stations or home base stations.

[0051] The Third-Generation Partnership Project (3GPP) was formed in 1998 to provide global standardization of specifications for mobile communication networks similar to the mobile communication network 100 in FIG. 1A. To date, 3GPP has produced specifications for three generations of mobile networks: a third generation (3G) network known as Universal Mobile Telecommunications System (UMTS), a fourth generation (4G) network known as Long-Term Evolution (LTE), and a fifth generation (5G) network known as 5G System (5GS). Embodiments of the present disclosure are described with reference to the RAN of a 3GPP 5G network, referred to as next-generation RAN (NG- RAN). Embodiments may be applicable to RANs of other mobile communication networks, such as the RAN 104 in FIG. 1 A, the RANs of earlier 3G and 4G networks, and those of future networks yet to be specified (e.g., a 3GPP 6G network). NG-RAN implements 5G radio access technology known as New Radio (NR) and may be provisioned to implement 4G radio access technology or other radio access technologies, including non-3GPP radio access technologies.

[0052] FIG. 1 B illustrates another example mobile communication network 150 in which embodiments of the present disclosure may be implemented. Mobile communication network 150 may be, for example, a PLMN run by a network operator. As illustrated in FIG. 1B, mobile communication network 150 includes a 5G core network (5G-CN) 152, an NG-RAN 154, and UEs 156A and 156B (collectively UEs 156). These components may be implemented and operate in the same or similar manner as corresponding components described with respect to FIG. 1A.

[0053] The 5G-CN 152 provides the UEs 156 with an interface to one or more DNs, such as public DNs (e.g., the Internet), private DNs, and / or intra-operator DNs. As part of the interface functionality, the 5G-CN 152 may set up end- to-end connections between the UEs 156 and the one or more DNs, authenticate the UEs 156, and provide charging functionality. Compared to the CN of a 3GPP 4G network, the basis of the 5G-CN 152 may be a service-based architecture. This means that the architecture of the nodes making up the 5G-CN 152 may be defined as network functions that offer services via interfaces to other network functions. The network functions of the 5G-CN 152 may be implemented in several ways, including as network elements on dedicated or shared hardware, as software instances running on dedicated or shared hardware, or as virtualized functions instantiated on a platform (e.g., a cloud-based platform).

[0054] As illustrated in FIG. 1B, the 5G-CN 152 includes an Access and Mobility Management Function (AMF) 158A and a User Plane Function (UPF) 158B, which are shown as one component AMF / UPF 158 in FIG. 1B for ease of illustration. The UPF 158B may serve as a gateway between the NG-RAN 154 and the one or more DNs. The UPF 158B may perform functions such as packet routing and forwarding, packet inspection and user plane policy rule enforcement, traffic usage reporting, uplink classification to support routing of traffic flows to the one or more DNs, quality of service (QoS) handling for the user plane (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink traffic verification), downlink packet buffering, and downlink data notification triggering. The UPF 158B may serve as an anchor point for intra- / i nter-Radio Access Technology (RAT) mobility, an external protocol (or packet) data unit (PDU) session point of interconnect to the one or more DNs, and / or a branching point to support a multi-homed PDU session. The UEs 156 may be configured to receive services through a PDU session, which is a logical connection between a UE and a DN.

[0055] The AMF 158A may perform functions such as Non-Access Stratum (NAS) signaling termination, NAS signaling security, Access Stratum (AS) security control, inter-CN node signaling for mobility between 3GPP access networks, idle mode UE reachability (e.g., control and execution of paging retransmission), registration area management, intra-system and inter-system mobility support, access authentication, access authorization including checking of roaming rights, mobility management control (subscription and policies), network slicing support, and / or session management function (SMF) selection. NAS may refer to the functionality operating between a CN and a UE, and AS may refer to the functionality operating between the UE and a RAN.

[0056] The 5G-CN 152 may include one or more additional network functions that are not shown in FIG. 1 B for the sake of clarity. For example, the 5G-CN 152 may include one or more of a Session Management Function (SMF), anNR Repository Function (NRF), a Policy Control Function (PCF), a Network Exposure Function (NEF), a Unified Data Management (UDM), an Application Function (AF), and / or an Authentication Server Function (AUSF).

[0057] The NG-RAN 154 may connect the 5G-CN 152 to the UEs 156 through radio communications over the air interface. The NG-RAN 154 may include one or more g NBs, illustrated as g NB 160A and g NB 160B (collectively gNBs 160) and / or one or more ng-eNBs, illustrated as ng-eNB 162A and ng-eNB 162B (collectively ng-eNBs 162). The gNBs 160 and ng-eNBs 162 may be more generically referred to as base stations. The gNBs 160 and ng-eNBs 162 may include one or more sets of antennas for communicating with the UEs 156 over an air interface. For example, one or more of the gNBs 160 and / or one or more of the ng-eNBs 162 may include three sets of antennas to respectively control three cells (or sectors). Together, the cells of the gNBs 160 and the ng-eNBs 162 may provide radio coverage to the UEs 156 over a wide geographic area to support UE mobility.

[0058] As shown in FIG. 1B, the gNBs 160 and / or the ng-eNBs 162 may be connected to the 5G-CN 152 by means of an NG interface and to other base stations by an Xn interface The NG and Xn interfaces may be established using direct physical connections and / or indirect connections over an underlying transport network, such as an internet protocol (IP) transport network. The gNBs 160 and / or the ng-eNBs 162 may be connected to the UEs 156 by means of a Uu interface. For example, as illustrated in FIG. 1B, gNB 160A maybe connected to the UE 156A by means of a Uu interface. The NG, Xn, and Uu interfaces are associated with a protocol stack. The protocol stacks associated with the interfaces may be used by the network elements in FIG. 1 B to exchange data and signaling messages and may include two planes: a user plane and a control plane. The user plane may handle data of interest to a user. The control plane may handle signaling messages of interest to the network elements.

[0059] The gNBs 160 and / or the ng-eNBs 162 may be connected to one or more AMF / UPF functions of the 5G-CN 152, such as the AMF / UPF 158, by means of one or more NG interfaces. For example, the gNB 160A maybe connected to the UPF 158B of the AMF / UPF 158 by means of an NG-User plane (NG-U) interface. The NG-U interface may provide delivery (e.g., non-guaranteed delivery) of user plane PDUs between the gNB 160A and the UPF 158B. The gNB 160A may be connected to the AMF 158A by means of an NG-Control plane (NG-C) interface. The NG-C interface may provide, for example, NG interface management, UE context management, UE mobility management, transport of NAS messages, paging, PDU session management, and configuration transfer and / or warning message transmission.

[0060] The gNBs 160 may provide NR user plane and control plane protocol terminations towards the UEs 156 over the Uu interface. For example, the gNB 160A may provide NR user plane and control plane protocol terminations toward the UE 156A over a Uu interface associated with a first protocol stack. The ng-eNBs 162 may provide Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminations towards the UEs 156 over a Uu interface, where E-UTRA refers to the 3GPP 4G radio-access technology. For example, the ng-eNB 162B may provide E-UTRA user plane and control plane protocol terminations towards the UE 156B over a Uu interface associated with a second protocol stack.

[0061] The 5G-CN 152 was described as being configured to handle NR and 4G radio accesses. It will be appreciated by one of ordinary skill in the art that it may be possible for NR to connect to a 4G core network in a mode known as “non-standalone operation.” In non-standalone operation, a 4G core network is used to provide (or at least support) control-plane functionality (e.g., initial access, mobility, and paging). Although only one AMF / UPF 158 is shown in FIG. 1 B, one g N B or ng-eNB may be connected to multiple AMF / UPF nodes to provide redundancy and / or to load share across the multiple AMF / UPF nodes.

[0062] As discussed, an interface (e.g., Uu, Xn, and NG interfaces) between the network elements in FIG. 1B may be associated with a protocol stack that the network elements use to exchange data and signaling messages. A protocol stack may include two planes: a user plane and a control plane. The user plane may handle data of interest to a user, and the control plane may handle signaling messages of interest to the network elements.

[0063] FIG. 2A and FIG. 2B respectively illustrate examples of NR user plane and NR control plane protocol stacks for the Uu interface that lies between a UE 210 and a gNB 220. The protocol stacks illustrated in FIG. 2A and FIG. 2B maybe the same or similar to those used for the Uu interface between, for example, the UE 156A and the gNB 160A shown in FIG. 1B.

[0064] FIG. 2A illustrates a NR user plane protocol stack comprising five layers implemented in the UE 210 and the gNB 220. At the bottom of the protocol stack, physical layers (PHYs) 211 and 221 may provide transport services to the higher layers of the protocol stack and may correspond to layer 1 of the Open Systems Interconnection (OSI) model. The next four protocols above PHYs 211 and 221 comprise medium access control layers (MACs) 212 and 222, radio link control layers (RLCs) 213 and 223, packet data convergence protocol layers (PDCPs) 214 and 224, and service data application protocol layers (SDAPs) 215 and 225. Together, these four protocols may make up layer 2, or the data link layer, of the OSI model.

[0065] FIG. 3 illustrates an example of services provided between protocol layers of the NR user plane protocol stack. Starting from the top of FIG. 2A and FIG. 3, the SDAPs 215 and 225 may perform QoS flow handling. The UE 210 may receive services through a PDU session, which may be a logical connection between the UE 210 and a DN. The PDU session may have one or more QoS flows. A UPF of a CN (e.g., the UPF 158B) may map IP packets to the one or more QoS flows of the PDU session based on QoS requirements (e.g., in terms of delay, data rate, and / or error rate). The SDAPs 215 and 225 may perform mapping / de-mapping between the one or more QoS flows and one or more data radio bearers. The mapping / de-mapping between the QoS flows and the data radio bearers may be determined by the SDAP 225 at the gNB 220. The SDAP 215 at the UE 210 may be informed of the mapping between the QoS flows and the data radio bearers through reflective mapping or control signaling received from the gNB 220. For reflective mapping, the SDAP 225 at the gNB 220 may mark the downlink packets with a QoS flow indicator (QFI), which may be observed by the SDAP 215 at the UE 210 to determine the mapping / de-mapping between the QoS flows and the data radio bearers.

[0066] The PDCPs 214 and 224 may perform header compression / decompression to reduce the amount of data that needs to be transmitted over the air interface, ciphering / deciphering to prevent unauthorized decoding of data transmitted over the air interface, and integrity protection (to ensure control messages originate from intended sources. The PDCPs 214 and 224 may perform retransmissions of undelivered packets, in-sequence delivery and reordering of packets, and removal of packets received in duplicate due to, for example, an intra-g NB handover. The PDCPs 214 and 224 may perform packet duplication to improve the likelihood of the packet being received and, at the receiver, remove any duplicate packets. Packet duplication may be useful for services that require high reliability.

[0067] Although not shown in FIG. 3, PDCPs 214 and 224 may perform mapping / de-mapping between a split radio bearer and RLC channels in a dual connectivity scenario. Dual connectivity is a technique that allows a UE to connect to two cells or, more generally, two cell groups: a master cell group (MCG) and a secondary cell group (SCG). A split bearer is when a single radio bearer, such as one of the radio bearers provided by the PDCPs 214 and 224 as a service to the SDAPs 215 and 225, is handled by cell groups in dual connectivity The PDCPs 214 and 224 may map / de-map the split radio bearer between RLC channels belonging to cell groups.

[0068] The RLCs 213 and 223 may perform segmentation, retransmission through Automatic Repeat Request (ARQ), and removal of duplicate data units received from MACs 212 and 222, respectively. The RLCs 213 and 223 may support three transmission modes: transparent mode (TM); unacknowledged mode (UM); and acknowledged mode (AM). Based on the transmission mode an RLC is operating, the RLC may perform one or more of the noted functions. The RLC configuration may be per logical channel with no dependency on numerologies and / or Transmission Time Interval (TTI) durations. As shown in FIG. 3, the RLCs 213 and 223 may provide RLC channels as a service to PDCPs 214 and 224, respectively.

[0069] The MACs 212 and 222 may perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. The multiplexing / demultiplexing may include multiplexing / demultiplexing of data units, belonging to the one or more logical channels, into / from Transport Blocks (TBs) delivered to / from the PHYs211 and 221. The MAC 222 may be configured to perform scheduling, scheduling information reporting, and priority handling between UEs by means of dynamic scheduling. Scheduling may be performed in the g N B 220 (at the MAC 222) for downlink and uplink. The MACs 212 and 222 may be configured to perform error correction through Hybrid Automatic Repeat Request (HARQ) (e.g. , one HARQ entity per carrier in case of Carrier Aggregation (CA)), priority handling between logical channels of the UE 210 by means of logical channel prioritization, and / or padding. The MACs212 and 222 may support one or more numerologies and / or transmission timings. In an example, mapping restrictions in a logical channel prioritization may control which numerology and / or transmission timing a logical channel may use. As shown in FIG. 3, the MACs 212 and 222 may provide logical channels as a service to the RLCs 213 and 223.

[0070] The PHYs 211 and 221 may perform mapping of transport channels to physical channels and digital and analog signal processing functions for sending and receiving information over the air interface. These digital and analog signal processing functions may include, for example, coding / decoding and modulation / demodulation. The PHYs 211and 221 may perform multi-antenna mapping. As shown in FIG. 3, the PHYs 211 and 221 may provide one or more transport channels as a service to the MACs 212 and 222.

[0071] FIG. 4A illustrates an example downlink data flow through the NR user plane protocol stack. FIG. 4A illustrates a downlink data flow of three IP packets (n, n+1, and m) through the NR user plane protocol stack to generate two TBs at the g N B 220. An uplink data flow through the NR user plane protocol stack may be similar to the downlink data flow depicted in FIG. 4A.

[0072] The downlink data flow of FIG. 4A begins when SDAP 225 receives the three IP packets from one or more QoS flows and maps the three packets to radio bearers. In FIG. 4A, the SDAP 225 maps IP packets n and n+1 to a first radio bearer 402 and maps IP packet m to a second radio bearer 404. An SDAP header (labeled with an “H” in FIG. 4A) is added to an IP packet. The data unit from / to a higher protocol layer is referred to as a service data unit (SDU) of the lower protocol layer and the data unit to / from a lower protocol layer is referred to as a protocol data unit (PDU) of the higher protocol layer. As shown in FIG. 4A, the data unit from the SDAP 225 is an SDU of lower protocol layer PDCP 224 and is a PDU of the SDAP 225.

[0073] The remaining protocol layers in FIG. 4A may perform their associated functionality (e.g. , with respect to FIG. 3), add corresponding headers, and forward their respective outputs to the next lower layer. For example, the PDCP 224 may perform IP-header compression and ciphering and forward its output to the RLC 223. The RLC 223 may optionally perform segmentation (e.g., as shown for IP packet m in FIG. 4A) and forward its output to the MAC 222. The MAC 222 may multiplex a number of RLC PDUs and may attach a MAC subheader to an RLC PDU to form a transport block. In NR, the MAC subheaders may be distributed across the MAC PDU, as illustrated in FIG. 4A. In LTE, the MAC subheaders may be entirely located at the beginning of the MAC PDU. The NR MAC PDU structure may reduce processing time and associated latency because the MAC PDU subheaders may be computed before the full MAC PDU is assembled.

[0074] FIG. 4B illustrates an example format of a MAC subheader in a MAC PDU. The MAC subheader includes: an SDU length field for indicating the length (e.g., in bytes) of the MAC SDU to which the MAC subheader corresponds; a logical channel identifier (LCID) field for identifying the logical channel from which the MAC SDU originated to aid in the demultiplexing process; a flag (F) for indicating the size of the SDU length field; and a reserved bit (R) field for future use.

[0075] FIG. 4B further illustrates MAC control elements (CEs) inserted into the MAC PDU by a MAC, such as MAC 223 or MAC 222. For example, FIG. 4B illustrates two MAC CEs inserted into the MAC PDU. MAC CEs may be inserted at the beginning of a MAC PDU for downlink transmissions (as shown in FIG. 4B) and at the end of a MAC PDU for uplink transmissions. MAC CEs maybe used for in-band control signaling. Example MAC CEs include: scheduling-related MAC CEs, such as buffer status reports and power headroom reports; activation / deactivation MAC CEs, such as those for activation / deactivation of PDCP duplication detection, channel state information (CSI) reporting, sounding reference signal (SRS) transmission, and prior configured components; discontinuous reception (DRX)related MAC CEs; timing advance MAC CEs; and random access related MAC CEs. A MAC CE may be preceded by a MAC subheader with a similar format as described for MAC SDUs and may be identified with a reserved value in the LCID field that indicates the type of control information included in the MAC CE.

[0076] Before describing the NR control plane protocol stack, logical channels, transport channels, and physical channels are first described as well as a mapping between the channel types. One or more of the channels may be used to carry out functions associated with the NR control plane protocol stack described later below.

[0077] FIG. 5A and FIG. 5B illustrate, for downlink and uplink respectively, a mapping between logical channels, transport channels, and physical channels. Information is passed through channels between the RLC, the MAC, and the PHY of the NR protocol stack. A logical channel may be used between the RLC and the MAC and may be classified as a control channel that carries control and configuration information in the NR control plane or as a traffic channel that carries data in the NR user plane. A logical channel may be classified as a dedicated logical channel that is dedicated to a specific UE or as a common logical channel that may be used by more than one UE. A logical channel may also be defined by the type of information it carries. The set of logical channels defined by NR include, for example:

[0078] - a paging control channel (PCCH) for carrying paging messages used to page a UE whose location is not known to the network on a cell level;

[0079] -- a broadcast control channel (BCCH) for carrying system information messages in the form of a master information block (MIB) and several system information blocks (SIBs), wherein the system information messages may be used by the UEs to obtain information about how a cell is configured and how to operate within the cell;

[0080] - a common control channel (CCCH) for carrying control messages together with random access;

[0081] -- a dedicated control channel (DCCH) for carrying control messages to / from a specific the UE to configure the UE; and

[0082] - a dedicated traffic channel (DTCH) for carrying user data to / from a specific the UE.

[0083] Transport channels are used between the MAC and PHY layers and may be defined by how the information they carry is transmitted over the air interface. The set of transport channels defined by NR include, for example:

[0084] -- a paging channel (PCH) for carrying paging messages that originated from the PCCH;

[0085] - a broadcast channel (BCH) for carrying the MIB from the BCCH;

[0086] - a downlink shared channel (DL-SCH) for carrying downlink data and signaling messages, including the SIBs from the BCCH;

[0087] -- an uplink shared channel (UL-SCH) for carrying uplink data and signaling messages; and

[0088] - a random access channel (RACH) for allowing a UE to contact the network without any prior scheduling.

[0089] The PHY may use physical channels to pass information between processing levels of the PHY. A physical channel may have an associated set of time-frequency resources for carrying the information of one or more transport channels. The PHY may generate control information to support the low-level operation of the PHY and provide thecontrol information to the lower levels of the PHY via physical control channels, known as L1 / L2 control channels. The set of physical channels and physical control channels defined by NR include, for example:

[0090] - a physical broadcast channel (PBCH) for carrying the MIB from the BCH;

[0091] - a physical downlink shared channel (PDSCH) for carrying downlink data and signaling messages from the DL-SCH, as well as paging messages from the PCH;

[0092] -- a physical downlink control channel (PDCCH) for carrying downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling grants, and uplink power control commands;

[0093] - a physical uplink shared channel (PUSCH) for carrying uplink data and signaling messages from the UL- SCH and in some instances uplink control information (UCI) as described below;

[0094] -- a physical uplink control channel (PUCCH) for carrying UCI, which may include HARQ acknowledgments, channel quality indicators (CQI), pre-coding matrix indicators (PMI), rank indicators (Rl), and scheduling requests (SR); and

[0095] - a physical random access channel (PRACH) for random access.

[0096] Similar to the physical control channels, the physical layer generates physical signals to support the low-level operation of the physical layer. As shown in FIG. 5A and FIG. 5B, the physical layer signals defined by NR include: primary synchronization signals (PSS), secondary synchronization signals (SSS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), sounding reference signals (SRS), and phase-tracking reference signals (PT-RS). These physical layer signals will be described in greater detail below.

[0097] FIG. 2B illustrates an example NR control plane protocol stack. As shown in FIG. 2B, the NR control plane protocol stack may use the same / similar first four protocol layers as the example NR user plane protocol stack. These four protocol layers include the PHYs 211 and 221, the MACs 212 and 222, the RLCs 213 and 223, and the PDCPs 214 and 224. Instead of having the SDAPs 215 and 225 at the top of the stack as in the NR user plane protocol stack, the NR control plane stack has radio resource controls (RRCs) 216 and 226 and NAS protocols 217 and 237 at the top of the NR control plane protocol stack.

[0098] The NAS protocols 217 and 237 may provide control plane functionality between the UE 210 and the AMF 230 (e.g., the AMF 158A) or, more generally, between the UE 210 and the CN. The NAS protocols 217 and 237 may provide control plane functionality between the UE 210 and the AMF 230 via signaling messages, referred to as NAS messages. There is no direct path between the UE 210 and the AMF 230 through which the NAS messages can be transported. The NAS messages may be transported using the AS of the Uu and NG interfaces. NAS protocols 217 and 237 may provide control plane functionality such as authentication, security, connection setup, mobility management, and session management.

[0099] The RRCs 216 and 226 may provide control plane functionality between the UE 210 and the gNB 220 or, more generally, between the UE 210 and the RAN. The RRCs 216 and 226 may provide control plane functionality between the UE 210 and the gNB 220 via signaling messages, referred to as RRC messages. RRC messages may betransmitted between the UE 210 and the RAN using signaling radio bearers and the same / similar PDCP, RLC, MAC, and PHY protocol layers. The MAC may multiplex control-plane and user-plane data into the same transport block (TB). The RRCs 216 and 226 may provide control plane functionality such as: broadcast of system information related to AS and NAS; paging initiated by the CN or the RAN; establishment, maintenance and release of an RRC connection between the UE 210 and the RAN; security functions including key management; establishment, configuration, maintenance and release of signaling radio bearers and data radio bearers; mobility functions; QoS management functions; the UE measurement reporting and control of the reporting; detection of and recovery from radio link failure (RLF); and / or NAS message transfer. As part of establishing an RRC connection, RRCs 216 and 226 may establish an RRC context, which may involve configuring parameters for communication between the UE 210 and the RAN.

[0100] FIG. 6 is an example diagram showing RRC state transitions of a UE. The UE may be the same or similar to the wireless device 106 depicted in FIG. 1A, the UE 210 depicted in FIG. 2Aand FIG. 2B, or any other wireless device described in the present disclosure. As illustrated in FIG. 6, a UE may be in at least one of three RRC states: RRC connected 602 (e.g., RRC_CONNECTED), RRC idle 604 (e.g., RRC_I DUE), and RRC inactive 606 (e.g., RRCJNACTIVE).

[0101] In RRC connected 602, the UE has an established RRC context and may have at least one RRC connection with a base station. The base station may be similar to one of the one or more base stations included in the RAN 104 depicted in FIG. 1A, one of the gNBs 160 or ng-eNBs 162 depicted in FIG. 1B, the gNB 220 depicted in FIG. 2Aand FIG. 2B, or any other base station described in the present disclosure. The base station with which the UE is connected may have the RRC context for the UE. The RRC context, referred to as the UE context, may comprise parameters for communication between the UE and the base station. These parameters may include, for example: one or more AS contexts; one or more radio link configuration parameters; bearer configuration information (e.g , relating to a data radio bearer, signaling radio bearer, logical channel, QoS flow, and / or PDU session); security information; and / or PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information. While in RRC connected 602, mobility of the UE may be managed by the RAN (e.g., the RAN 104 or the NG-RAN 154). The UE may measure the signal levels (e.g., reference signal levels) from a serving cell and neighboring cells and report these measurements to the base station currently serving the UE. The UE’s serving base station may request a handover to a cell of one of the neighboring base stations based on the reported measurements. The RRC state may transition from RRC connected 602 to RRC idle 604 through a connection release procedure 608 or to RRC inactive 606 through a connection inactivation procedure 610.

[0102] In RRC idle 604, an RRC context may not be established for the UE. In RRC idle 604, the UE may not have an RRC connection with the base station. While in RRC idle 604, the UE may be in a sleep state for the majority of the time (e.g., to conserve battery power). The UE may wake up periodically (e.g., once in every discontinuous reception cycle) to monitor for paging messages from the RAN. Mobility of the UE maybe managed by the UE through a procedure known as cell reselection. The RRC state may transition from RRC idle 604 to RRC connected 602 througha connection establishment procedure 612, which may involve a random access procedure as discussed in greater detail below.

[0103] In RRC inactive 606, the RRC context previously established is maintained in the UE and the base station. This allows for a fast transition to RRC connected 602 with reduced signaling overhead as compared to the transition from RRC idle 604 to RRC connected 602. While in RRC inactive 606, the UE may be in a sleep state and mobility of the UE may be managed by the UE through cell reselection. The RRC state may transition from RRC inactive 606 to RRC connected 602 through a connection resume procedure 614 or to RRC idle 604 though a connection release procedure 616 that may be the same as or similar to connection release procedure 608.

[0104] An RRC state may be associated with a mobility management mechanism. In RRC idle 604 and RRC inactive 606, mobility is managed by the UE through cell reselection. The purpose of mobility management in RRC idle 604 and RRC inactive 606 is to allow the network to be able to notify the UE of an event via a paging message without having to broadcast the paging message over the entire mobile communications network. The mobility management mechanism used in RRC idle 604 and RRC inactive 606 may allow the network to track the UE on a cell-group level so that the paging message may be broadcast over the cells of the cell group that the UE currently resides within instead of the entire mobile communication network. The mobility management mechanisms for RRC idle 604 and RRC inactive 606 track the UE on a cell-group level. They may do so using different granularities of grouping. For example, there may be three levels of cell-grouping granularity: individual cells; cells within a RAN area identified by a RAN area identifier (RAI); and cells within a group of RAN areas, referred to as a tracking area and identified by a tracking area identifier (TAI).

[0105] Tracking areas may be used to track the UE at the CN level. The CN (e.g., the CN 102 or the 5G-CN 152) may provide the UE with a list of TAIs associated with a UE registration area. If the UE moves, through cell reselection, to a cell associated with a TAI not included in the list of TAIs associated with the UE registration area, the UE may perform a registration update with the CN to allow the CN to update the UE’s location and provide the UE with a new the UE registration area.

[0106] RAN areas may be used to track the UE at the RAN level. For a UE in RRC inactive 606 state, the UE may be assigned a RAN notification area. A RAN notification area may comprise one or more cell identities, a list of RAIs, or a list of TAIs. In an example, a base station may belong to one or more RAN notification areas. In an example, a cell may belong to one or more RAN notification areas. If the UE moves, through cell reselection, to a cell not included in the RAN notification area assigned to the UE, the UE may perform a notification area update with the RAN to update the UE’s RAN notification area.

[0107] A base station storing an RRC context for a UE or a last serving base station of the UE may be referred to as an anchor base station. An anchor base station may maintain an RRC context for the UE at least during a period of time that the UE stays in a RAN notification area of the anchor base station and / or during a period of time that the UE stays in RRC inactive 606.

[0108] AgNB, such as gNBs 160 in FIG. 1B, maybe split into two parts: a central unit (gNB-CU), and one or more distributed units (gNB-DU). A gNB-CU may be coupled to one or more gNB-DUs using an F1 interface. The gNB-CU may comprise the RRC, the PDCP, and the SOAP. A gNB-DU may comprise the RLC, the MAC, and the PHY.

[0109] In NR, the physical signals and physical channels (discussed with respect to FIG. 5A and FIG. 5B) may be mapped onto orthogonal frequency divisional multiplexing (OFDM) symbols. OFDM is a multicarrier communication scheme that transmits data over F orthogonal subcarriers (or tones). Before transmission, the data may be mapped to a series of complex symbols (e.g., M-quadrature amplitude modulation (M-QAM) or M-phase shift keying (M-PSK) symbols), referred to as source symbols, and divided into F parallel symbol streams. The F parallel symbol streams may be treated as though they are in the frequency domain and used as inputs to an Inverse Fast Fourier Transform (IFFT) block that transforms them into the time domain. The IFFT block may take in F source symbols at a time, one from each of the F parallel symbol streams, and use each source symbol to modulate the amplitude and phase of one of F sinusoidal basis functions that correspond to the F orthogonal subcarriers. The output of the IFFT block may be F time-domain samples that represent the summation of the F orthogonal subcarriers. The F time-domain samples may form a single OFDM symbol. After some processing (e.g addition of a cyclic prefix) and up-conversion, an OFDM symbol provided by the IFFT block may be transmitted over the air interface on a carrier frequency. The F parallel symbol streams may be mixed using an FFT block before being processed by the IFFT block. This operation produces Discrete Fourier Transform (DFT)-precoded OFDM symbols and may be used by UEs in the uplink to reduce the peak to average power ratio (PARR). Inverse processing may be performed on the OFDM symbol at a receiver using an FFT block to recover the data mapped to the source symbols.

[0110] FIG. 7 illustrates an example configuration of an NR frame into which OFDM symbols are grouped. An NR frame may be identified by a system frame number (SFN). The SFN may repeat with a period of 1024 frames. As illustrated, one NR frame may be 10 milliseconds (ms) in duration and may include 10 subframes that are 1 ms in duration. A subframe may be divided into slots that include, for example, 14 OFDM symbols per slot.

[0111] The duration of a slot may depend on the numerology used for the OFDM symbols of the slot. In NR, a flexible numerology is supported to accommodate different cell deployments (e.g., cells with carrier frequencies below 1 GHz up to cells with carrier frequencies in the mm-wave range). A numerology may be defined in terms of subcarrier spacing and cyclic prefix duration. For a numerology in NR, subcarrier spacings may be scaled up by powers of two from a baseline subcarrier spacing of 15 kHz, and cyclic prefix durations may be scaled down by powers of two from a baseline cyclic prefix duration of 4.7 ps. For example, NR defines numerologies with the following subcarrier spacing / cyclic prefix duration combinations: 15 kHz / 4.7 ps; 30 kHz / 2.3 ps; 60 kHz / 1.2 ps; 120 kHz / 059 ps; and 240 kHz / 0.29 ps.

[0112] A slot may have a fixed number of OFDM symbols (e.g., 14 OFDM symbols). A numerology with a higher subcarrier spacing has a shorter slot duration and, correspondingly, more slots per subframe. FIG. 7 illustrates this numerology-dependent slot duration and slots-per-subframe transmission structure (the numerology with a subcarrierspacing of 240 kHz is not shown in FIG. 7 for ease of illustration). A subframe in NR may be used as a numerologyindependent time reference, while a slot may be used as the unit upon which uplink and downlink transmissions are scheduled. To support low latency, scheduling in NR may be decoupled from the slot duration and start at any OFDM symbol and last for as many symbols as needed for a transmission. These partial slot transmissions may be referred to as mini-slot or subslot transmissions.

[0113] FIG. 8 illustrates an example configuration of a slot in the time and frequency domain for an NR carrier. The slot includes resource elements (REs) and resource blocks (RBs). An RE is the smallest physical resource in NR. An RE spans one OFDM symbol in the time domain by one subcarrier in the frequency domain as shown in FIG. 8. An RB spans twelve consecutive REs in the frequency domain as shown in FIG. 8. An NR carrier may be limited to a width of 275 RBs or 275*12 = 3300 subcarriers. Such a limitation, if used, may limit the NR carrier to 50, 100, 200, and 400 MHz for subcarrier spacings of 15, 30, 60, and 120 kHz, respectively, where the 400 MHz bandwidth may be set based on a 400 MHz per carrier bandwidth limit.

[0114] FIG. 8 illustrates a single numerology being used across the entire bandwidth of the NR carrier. In other example configurations, multiple numerologies may be supported on the same carrier.

[0115] NR may support wide carrier bandwidths (e.g., up to 400 MHz for a subcarrier spacing of 120 kHz). Not all UEs may be able to receive the full carrier bandwidth (e.g., due to hardware limitations). Also, receiving the full carrier bandwidth may be prohibitive in terms of UE power consumption. In an example, to reduce power consumption and / or for other purposes, a UE may adapt the size of the UE’s receive bandwidth based on the amount of traffic the UE is scheduled to receive. This is referred to as bandwidth adaptation.

[0116] NR defines bandwidth parts (BWPs) to support UEs not capable of receiving the full carrier bandwidth and to support bandwidth adaptation. In an example, a BWP may be defined by a subset of contiguous RBs on a carrier. A UE may be configured (e.g., via RRC layer) with one or more downlink BWPs and one or more uplink BWPs per serving cell (e.g., up to four downlink BWPs and up to four uplink BWPs per serving cell). At a given time, one or more of the configured BWPs for a serving cell may be active. These one or more BWPs may be referred to as active BWPs of the serving cell. When a serving cell is configured with a secondary uplink carrier, the serving cell may have one or more first active BWPs in the uplink carrier and one or more second active BWPs in the secondary uplink carrier.

[0117] For unpaired spectra, a downlink BWP from a set of configured downlink BWPs may be linked with an uplink BWP from a set of configured uplink BWPs if a downlink BWP index of the downlink BWP and an uplink BWP index of the uplink BWP are the same. For unpaired spectra, a UE may expect that a center frequency for a downlink BWP is the same as a center frequency for an uplink BWP.

[0118] For a downlink BWP in a set of configured downlink BWPs on a primary cell (PCell), a base station may configure a UE with one or more control resource sets (CORESETs) for at least one search space. A search space is a set of locations in the time and frequency domains where the UE may find control information. The search space may be a UE-specific search space or a common search space (potentially usable by a plurality of UEs). For example, abase station may configure a UE with a common search space, on a PCell or on a primary secondary cell (PSCell), in an active downlink BWP.

[0119] For an uplink BWP in a set of configured uplink BWPs, a BS may configure a UE with one or more resource sets for one or more PUCCH transmissions. A UE may receive downlink receptions (e.g., PDCCH or PDSCH) in a downlink BWP according to a configured numerology (e.g., subcarrier spacing and cyclic prefix duration) for the downlink BWP. The UE may transmit uplink transmissions (e.g., PUCCH or PUSCH) in an uplink BWP according to a configured numerology (e.g., subcarrier spacing and cyclic prefix length for the uplink BWP).

[0120] One or more BWP indicator fields may be provided in Downlink Control Information (DCI). A value of a BWP indicator field may indicate which BWP in a set of configured BWPs is an active downlink BWP for one or more downlink receptions. The value of the one or more BWP indicator fields may indicate an active uplink BWP for one or more uplink transmissions.

[0121] A base station may semi-statical ly configure a UE with a default downlink BWP within a set of configured downlink BWPs associated with a PCell. If the base station does not provide the default downlink BWP to the UE, the default downlink BWP may be an initial active downlink BWP. The UE may determine which BWP is the initial active downlink BWP based on a CORESET configuration obtained using the PBCH.

[0122] A base station may configure a UE with a BWP inactivity timer value for a PCell. The UE may start or restart a BWP inactivity timer at any appropriate time. For example, the UE may start or restart the BWP inactivity timer (a) when the UE detects a DCI indicating an active downlink BWP other than a default downlink BWP for a paired spectra operation; or (b) when a UE detects a DCI indicating an active downlink BWP or active uplink BWP other than a default downlink BWP or uplink BWP for an unpaired spectra operation. If the UE does not detect DCI during an interval of time (e g., 1 ms or 0.5 ms), the UE may run the BWP inactivity timer toward expiration (for example, increment from zero to the BWP inactivity timer value, or decrement from the BWP inactivity timer value to zero). When the BWP inactivity timer expires, the UE may switch from the active downlink BWP to the default downlink BWP.

[0123] In an example, a base station may semi-statically configure a UE with one or more BWPs. A UE may switch an active BWP from a first BWP to a second BWP in response to receiving a DCI indicating the second BWP as an active BWP and / or in response to an expiry of the BWP inactivity timer (e.g., if the second BWP is the default BWP).

[0124] Downlink and uplink BWP switching (where BWP switching refers to switching from a currently active BWP to a not currently active BWP) may be performed independently in paired spectra. In unpaired spectra, downlink and uplink BWP switching may be performed simultaneously. Switching between configured BWPs may occur based on RRC signaling, DCI, expiration of a BWP inactivity timer, and / or an initiation of random access.

[0125] FIG. 9 illustrates an example of bandwidth adaptation using three configured BWPs for an NR carrier. A UE configured with the three BWPs may switch from one BWP to another BWP at a switching point. In the example illustrated in FIG. 9, the BWPs include: a BWP 902 with a bandwidth of 40 MHz and a subcarrier spacing of 15 kHz; a BWP 904 with a bandwidth of 10 MHz and a subcarrier spacing of 15 kHz; and a BWP 906 with a bandwidth of 20 MHzand a subcarrier spacing of 60 kHz. The BWP 902 may be an initial active BWP, and the BWP 904 may be a default BWP. The UE may switch between BWPs at switching points. In the example of FIG. 9, the UE may switch from the BWP 902 to the BWP 904 at a switching point 908. The switching at the switching point 908 may occur for any suitable reason, for example, in response to an expiry of a BWP inactivity timer (indicating switching to the default BWP) and / or in response to receiving a DCI indicating BWP 904 as the active BWP. The UE may switch at a switching point 910 from active BWP 904 to BWP 906 in response to receiving a DCI indicating BWP 906 as the active BWP. The UE may switch at a switching point 912 from active BWP 906 to BWP 904 in response to an expiry of a BWP inactivity timer and / or in response to receiving a DCI indicating BWP 904 as the active BWP. The UE may switch at a switching point 914 from active BWP 904 to BWP 902 in response to receiving a DCI indicating BWP 902 as the active BWP.

[0126] If a UE is configured for a secondary cell with a default downlink BWP in a set of configured downlink BWPs and a timer value, UE procedures for switching BWPs on a secondary cell may be the same / similar as those on a primary cell For example, the UE may use the timer value and the default downlink BWP for the secondary cell in the same / similar manner as the UE would use these values for a primary cell.

[0127] To provide for greater data rates, two or more carriers can be aggregated and simultaneously transmitted to / from the same UE using carrier aggregation (CA). The aggregated carriers in CA may be referred to as component carriers (CCs). When CA is used, there are a number of serving cells for the UE, one for a CC. The CCs may have three configurations in the frequency domain.

[0128] FIG. 10A illustrates the three CA configurations with two CCs. In the intraband, contiguous configuration 1002, the two CCs are aggregated in the same frequency band (frequency band A) and are located directly adjacent to each other within the frequency band. In the intraband, non-contiguous configuration 1004, the two CCs are aggregated in the same frequency band (frequency band A) and are separated in the frequency band by a gap. In the interband configuration 1006, the two CCs are located in frequency bands (frequency band A and frequency band B).

[0129] In an example, up to 32 CCs may be aggregated. The aggregated CCs may have the same or different bandwidths, subcarrier spacing, and / or duplexing schemes (TDD or FDD). A serving cell for a UE using CA may have a downlink CC. For FDD, one or more uplink CCs may be optionally configured for a serving cell. The ability to aggregate more downlink carriers than uplink carriers may be useful, for example, when the UE has more data traffic in the downlink than in the uplink.

[0130] When CA is used, one of the aggregated cells for a UE may be referred to as a primary cell (PCell). The PCell may be the serving cell that the UE initially connects to at RRC connection establishment, reestablishment, and / or handover. The PCell may provide the UE with NAS mobility information and the security input. UEs may have different PCells. In the downlink, the carrier corresponding to the PCell may be referred to as the downlink primary CC (DL PCC). In the uplink, the carrier corresponding to the PCell may be referred to as the uplink primary CC (UL PCC). The other aggregated cells for the UE may be referred to as secondary cells (SCells) . In an example, the SCells may be configured after the PCell is configured for the UE. For example, an SCell may be configured through an RRCConnection Reconfiguration procedure. In the downlink, the carrier corresponding to an SCell may be referred to as a downlink secondary CC (DL SCC). In the uplink, the carrier corresponding to the SCell may be referred to as the uplink secondary CC (UL SCC).

[0131] Configured SCells for a UE may be activated and deactivated based on, for example, traffic and channel conditions. Deactivation of an SCell may mean that PDCCH and PDSCH reception on the SCell is stopped and PUSCH, SRS, and CQI transmissions on the SCell are stopped. Configured SCells maybe activated and deactivated using a MAC CE with respect to FIG. 4B. For example, a MAC CE may use a bitmap (e.g., one bit per SCell) to indicate which SCells (e.g ., in a subset of configured SCells) for the UE are activated or deactivated. Configured SCells may be deactivated in response to an expiration of an SCell deactivation timer (e.g., one SCell deactivation timer per SCell).

[0132] Downlink control information, such as scheduling assignments and scheduling grants, for a cell may be transmitted on the cell corresponding to the assignments and grants, which is known as self-scheduling. The DCI for the cell may be transmitted on another cell, which is known as cross-carrier scheduling. Uplink control information (e.g., HARQ acknowledgments and channel state feedback, such as CQI, PMI, and / or Rl) for aggregated cells may be transmitted on the PUCCH of the PCell. For a larger number of aggregated downlink CCs, the PUCCH of the PCell may become overloaded. Cells may be divided into multiple PUCCH groups.

[0133] FIG. 10B illustrates an example of how aggregated cells may be configured into one or more PUCCH groups. A PUCCH group 1010 and a PUCCH group 1050 may include one or more downlink CCs, respectively. In the example of FIG. 10B, the PUCCH group 1010 includes three downlink CCs: a PCell 1011, an SCell 1012, and an SCell 1013. The PUCCH group 1050 includes three downlink CCs in the present example: a PCell 1051, an SCell 1052, and an SCell 1053. One or more uplink CCs may be configured as a PCell 1021, an SCell 1022, and an SCell 1023. One or more other uplink CCs may be configured as a primary SCell (PSCell) 1061, an SCell 1062, and an SCell 1063. Uplink control information (UCI) related to the downlink CCs of the PUCCH group 1010, shown as UC1 1031, UC1 1032, and UC1 1033, may be transmitted in the uplink of the PCell 1021. Uplink control information (UCI) related to the downlink CCs of the PUCCH group 1050, shown as UC1 1071, UC1 1072, and UC1 1073, maybe transmitted in the uplink of the PSCell 1061. In an example, if the aggregated cells depicted in FIG. 10B were not divided into the PUCCH group 1010 and the PUCCH group 1050, a single uplink PCell to transmit UCI relating to the downlink CCs, and the PCell may become overloaded. By dividing transmissions of UCI between the PCell 1021 and the PSCell 1061, overloading may be prevented.

[0134] A cell, comprising a downlink carrier and optionally an uplink carrier, may be assigned with a physical cell ID and a cell index. The physical cell ID or the cell index may identify a downlink carrier and / or an uplink carrier of the cell, for example, depending on the context in which the physical cell ID is used. A physical cell ID may be determined using a synchronization signal transmitted on a downlink component carrier. A cell index may be determined using RRC messages. In the disclosure, a physical cell ID may be referred to as a carrier ID, and a cell index may be referred to as a carrier index. For example, when the disclosure refers to a first physical cell ID for a first downlink carrier, thedisclosure may mean the first physical cell ID is for a cell comprising the first downlink carrier. The same / similar concept may apply to, for example, a carrier activation. When the disclosure indicates that a first carrier is activated, the specification may mean that a cell comprising the first carrier is activated.

[0135] In CA, a multi-carrier nature of a PHY may be exposed to a MAC. In an example, a HARQ entity may operate on a serving cell. A transport block may be generated per assignment / grant per serving cell. A transport block and potential HARQ retransmissions of the transport block may be mapped to a serving cell.

[0136] In the downlink, a base station may transmit (e.g., unicast, multicast, and / or broadcast) one or more Reference Signals (RSs) to a UE (e.g., PSS, SSS, CSI-RS, DMRS, and / or PT-RS, as shown in FIG. 5A). In the uplink, the UE may transmit one or more RSs to the base station (e.g., DMRS, PT-RS, and / or SRS, as shown in FIG. 5B). The PSS and the SSS may be transmitted by the base station and used by the UE to synchronize the UE to the base station. The PSS and the SSS may be provided in a synchronization signal (SS) I physical broadcast channel (PBCH) block that includes the PSS, the SSS, and the PBCH. The base station may periodically transmit a burst of SS / PBCH blocks.

[0137] FIG. 11A illustrates an example of an SS / PBCH block's structure and location. A burst of SS / PBCH blocks may include one or more SS / PBCH blocks (e.g., 4 SS / PBCH blocks, as shown in FIG. 11 A). Bursts may be transmitted periodically (e.g., every 2 frames or 20 ms). A burst may be restricted to a half-frame (e.g., a first half-frame having a duration of 5 ms). It will be understood that FIG. 11 A is an example, and that these parameters (number of SS / PBCH blocks per burst, periodicity of bursts, position of burst within the frame) may be configured based on, for example: a carrier frequency of a cell in which the SS / PBCH block is transmitted; a numerology or subcarrier spacing of the cell; a configuration by the network (e.g., using RRC signaling); or any other suitable factor. In an example, the UE may assume a subcarrier spacing for the SS / PBCH block based on the carrier frequency being monitored, unless the radio network configured the UE to assume a different subcarrier spacing.

[0138] The SS / PBCH block may span one or more OFDM symbols in the time domain (e.g., 4 OFDM symbols, as shown in the example of FIG. 11A) and may span one or more subcarriers in the frequency domain (e.g., 240 contiguous subcarriers). The PSS, the SSS, and the PBCH may have a common center frequency. The PSS may be transmitted first and may span, for example, 1 OFDM symbol and 127 subcarriers. The SSS may be transmitted after the PSS (e.g., two symbols later) and may span 1 OFDM symbol and 127 subcarriers. The PBCH may be transmitted after the PSS (e.g., across the next 3 OFDM symbols) and may span 240 subcarriers.

[0139] The location of the SS / PBCH block in the time and frequency domains may not be known to the UE (e.g., if the UE is searching for the cell). To find and select the cell, the UE may monitor a carrier for the PSS. For example, the UE may monitor a frequency location within the carrier. If the PSS is not found after a certain duration (e.g., 20 ms), the UE may search for the PSS at a different frequency location within the carrier, as indicated by a synchronization raster. If the PSS is found at a location in the time and frequency domains, the UE may determine, based on a known structure of the SS / PBCH block, the locations of the SSS and the PBCH, respectively. The SS / PBCH block may be a cell-defining SS block (CD-SSB). In an example, a primary cell may be associated with a CD-SSB. The CD-SSB may be located on a synchronization raster. In an example, a cell selection / search and / or reselection may be based on the CD- SSB.

[0140] The SS / PBCH block may be used by the UE to determine one or more parameters of the cell. For example, the UE may determine a physical cell identifier (PCI) of the cell based on the sequences of the PSS and the SSS, respectively. The UE may determine a location of a frame boundary of the cell based on the location of the SS / PBCH block. For example, the SS / PBCH block may indicate that it has been transmitted in accordance with a transmission pattern, wherein a SS / PBCH block in the transmission pattern is a known distance from the frame boundary.

[0141] The PBCH may use a QPSK modulation and may use forward error correction (FEC). The FEC may use polar coding. One or more symbols spanned by the PBCH may carry one or more DMRSs for demodulation of the PBCH. The PBCH may include an indication of a current system frame number (SFN) of the cell and / or a SS / PBCH block timing index. These parameters may facilitate time synchronization of the UE to the base station. The PBCH may include a master information block (MIB) used to provide the UE with one or more parameters. The MIB may be used by the UE to locate remaining minimum system information (RMSI) associated with the cell. The RMSI may include a System Information Block Type 1 (SIB1 ). The SIB1 may contain information needed by the UE to access the cell. The UE may use one or more parameters of the MIB to monitor PDCCH, which may be used to schedule PDSCH. The PDSCH may include the SIB1. The SIB1 may be decoded using parameters provided in the MIB. The PBCH may indicate an absence of SIB1. Based on the PBCH indicating the absence of SIB1, the UE may be pointed to a frequency. The UE may search for an SS / PBCH block at the frequency to which the UE is pointed.

[0142] The UE may assume that one or more SS / PBCH blocks transmitted with a same SS / PBCH block index are quasi co-located (QCLed) (e.g., having the same / similar Doppler spread, Doppler shift, average gain, average delay, and / or spatial Rx parameters). The UE may not assume QCL for SS / PBCH block transmissions having different SS / PBCH block indices.

[0143] SS / PBCH blocks (e.g., those within a half-frame) may be transmitted in spatial directions (e.g., using different beams that span a coverage area of the cell). In an example, a first SS / PBCH block may be transmitted in a first spatial direction using a first beam, and a second SS / PBCH block may be transmitted in a second spatial direction using a second beam.

[0144] In an example, within a frequency span of a carrier, a base station may transmit a plurality of SS / PBCH blocks. In an example, a first PCI of a first SS / PBCH block of the plurality of SS / PBCH blocks may be different from a second PCI of a second SS / PBCH block of the plurality of SS / PBCH blocks. The PCIs of SS / PBCH blocks transmitted in different frequency locations may be different or the same.

[0145] The CSI-RS may be transmitted by the base station and used by the UE to acquire channel state information (CSI). The base station may configure the UE with one or more CSI-RSs for channel estimation or any other suitable purpose. The base station may configure a UE with one or more of the same / similar CSI-RSs. The UE may measurethe one or more CSI-RSs. The UE may estimate a downlink channel state and / or generate a CSI report based on the measuring of the one or more downlink CSI-RSs. The UE may provide the CSI report to the base station. The base station may use feedback provided by the UE (e.g., the estimated downlink channel state) to perform link adaptation.

[0146] The base station may semi-statically configure the UE with one or more CSI-RS resource sets. A CSI-RS resource may be associated with a location in the time and frequency domains and a periodicity. The base station may selectively activate and / or deactivate a CSI-RS resource. The base station may indicate to the UE that a CSI-RS resource in the CSI-RS resource set is activated and / or deactivated.

[0147] The base station may configure the UE to report CSI measurements. The base station may configure the UE to provide CSI reports periodically, aperiodically, or semi-persistently. For periodic CSI reporting, the UE maybe configured with a timing and / or periodicity of a plurality of CSI reports. For aperiodic CSI reporting, the base station may request a CSI report. For example, the base station may command the UE to measure a configured CSI-RS resource and provide a CSI report relating to the measurements. For semi-persistent CSI reporting, the base station may configure the UE to transmit periodically, and selectively activate or deactivate the periodic reporting. The base station may configure the UE with a CSI-RS resource set and CSI reports using RRC signaling.

[0148] The CSI-RS configuration may comprise one or more parameters indicating, for example, up to 32 antenna ports. The UE may be configured to employ the same OFDM symbols for a downlink CSI-RS and a control resource set (CORESET) when the downlink CSI-RS and CORESET are spatially QCLed and resource elements associated with the downlink CSI-RS are outside of the physical resource blocks (PRBs) configured for the CORESET. The UE may be configured to employ the same OFDM symbols for downlink CSI-RS and SS / PBCH blocks when the downlink CSI-RS and SS / PBCH blocks are spatially QCLed and resource elements associated with the downlink CSI-RS are outside of PRBs configured for the SS / PBCH blocks.

[0149] Downlink DMRSs may be transmitted by a base station and used by a UE for channel estimation. For example, the downlink DMRS may be used for coherent demodulation of one or more downlink physical channels (e.g., PDSCH). An NR network may support one or more variable and / or configurable DMRS patterns for data demodulation. At least one downlink DMRS configuration may support a front-loaded DMRS pattern. A front-loaded DMRS may be mapped over one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). A base station may semi- statically configure the UE with a number (e.g. a maximum number) of front-loaded DMRS symbols for PDSCH. A DMRS configuration may support one or more DMRS ports. For example, for single user-MIMO, a DMRS configuration may support up to eight orthogonal downlink DMRS ports per UE. For multiuser-MI MO , a DMRS configuration may support up to 4 orthogonal downlink DMRS ports per UE. A radio network may support (e.g., at least for CP-OFDM) a common DMRS structure for downlink and uplink, wherein a DMRS location, a DMRS pattern, and / or a scrambling sequence may be the same or different. The base station may transmit a downlink DMRS and a corresponding PDSCH using the same precoding matrix. The UE may use the one or more downlink DMRSs for coherent demodulation / channel estimation of the PDSCH.

[0150] In an example, a transmitter (e.g., a base station) may use a precoder matrices for a part of a transmission bandwidth. For example, the transmitter may use a first precoder matrix for a first bandwidth and a second precoder matrix for a second bandwidth. The first precoder matrix and the second precoder matrix may be different based on the first bandwidth being different from the second bandwidth. The UE may assume that a same precoding matrix is used across a set of PRBs. The set of PRBs may be denoted as a precoding resource block group (PRG).

[0151] A PDSCH may comprise one or more layers. The UE may assume that at least one symbol with DMRS is present on a layer of the one or more layers of the PDSCH. A higher layer may configure up to 3 DMRSs for the PDSCH.

[0152] Downlink PT-RS may be transmitted by a base station and used by a UE for phase-noise compensation. Whether a downlink PT-RS is present or not may depend on an RRC configuration. The presence and / or pattern of the downlink PT-RS may be configured on a UE-specific basis using a combination of RRC signaling and / or an association with one or more parameters employed for other purposes (e.g., modulation and coding scheme (MCS)), which may be indicated by DCI. When configured, a dynamic presence of a downlink PT-RS may be associated with one or more DCI parameters comprising at least MCS. An NR network may support a plurality of PT-RS densities defined in the time and / or frequency domains. When present, a frequency domain density may be associated with at least one configuration of a scheduled bandwidth. The UE may assume a same precoding for a DMRS port and a PT-RS port. A number of PT-RS ports may be fewer than a number of DMRS ports in a scheduled resource. Downlink PT-RS may be confined in the scheduled time / frequency duration for the UE. Downlink PT-RS may be transmitted on symbols to facilitate phase tracking at the receiver.

[0153] The UE may transmit an uplink DMRS to a base station for channel estimation. For example, the base station may use the uplink DMRS for coherent demodulation of one or more uplink physical channels. For example, the UE may transmit an uplink DMRS with a PUSCH and / or a PUCCH. The uplink DM-RS may span a range of frequencies that is similar to a range of frequencies associated with the corresponding physical channel. The base station may configure the UE with one or more uplink DMRS configurations. At least one DMRS configuration may support a front- loaded DMRS pattern. The front-loaded DMRS maybe mapped over one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DMRSs may be configured to transmit at one or more symbols of a PUSCH and / or a PUCCH. The base station may semi-statically configure the UE with a number (e.g. maximum number) of front-loaded DMRS symbols for the PUSCH and / or the PUCCH, which the UE may use to schedule a single-symbol DMRS and / or a double-symbol DMRS. An NR network may support (e.g., for cyclic prefix orthogonal frequency division multiplexing (CP-OFDM)) a common DMRS structure for downlink and uplink, wherein a DMRS location, a DMRS pattern, and / or a scrambling sequence for the DMRS may be the same or different.

[0154] A PUSCH may comprise one or more layers, and the UE may transmit at least one symbol with DMRS present on a layer of the one or more layers of the PUSCH. In an example, a higher layer may configure up to three DMRSs for the PUSCH.

[0155] Uplink PT-RS (which may be used by a base station for phase tracking and / or phase-noise compensation) may or may not be present depending on an RRC configuration of the UE. The presence and / or pattern of uplink PT- RS may be configured on a UE-specific basis by a combination of RRC signaling and / or one or more parameters employed for other purposes (e.g., Modulation and Coding Scheme (MCS)), which may be indicated by DCI. When configured, a dynamic presence of uplink PT-RS may be associated with one or more DCI parameters comprising at least MCS. A radio network may support a plurality of uplink PT-RS densities defined in time / frequency domain. When present, a frequency domain density may be associated with at least one configuration of a scheduled bandwidth. The UE may assume a same precoding for a DMRS port and a PT-RS port. A number of PT-RS ports may be fewer than a number of DMRS ports in a scheduled resource. For example, uplink PT-RS may be confined in the scheduled time / frequency duration for the UE.

[0156] SRS may be transmitted by a UE to a base station for channel state estimation to support uplink channel dependent scheduling and / or link adaptation. SRS transmitted by the UE may allow a base station to estimate an uplink channel state at one or more frequencies. A scheduler at the base station may employ the estimated uplink channel state to assign one or more resource blocks for an uplink PUSCH transmission from the UE. The base station may semi-statically configure the UE with one or more SRS resource sets. For an SRS resource set, the base station may configure the UE with one or more SRS resources. An SRS resource set applicability may be configured by a higher layer (e.g., RRC) parameter. For example, when a higher layer parameter indicates beam management, an SRS resource in an SRS resource set of the one or more SRS resource sets (e.g., with the same / similar time domain behavior, periodic, aperiodic, and / or the like) may be transmitted at a time instant (e.g., simultaneously). The UE may transmit one or more SRS resources in SRS resource sets. An NR network may support aperiodic, periodic and / or semi-persistent SRS transmissions. The UE may transmit SRS resources based on one or more trigger types, wherein the one or more trigger types may comprise higher layer signaling (e.g., RRC) and / or one or more DCI formats. In an example, at least one DCI format may be employed for the UE to select at least one of one or more configured SRS resource sets. An SRS trigger type 0 may refer to an SRS triggered based on a higher layer signaling. An SRS trigger type 1 may refer to an SRS triggered based on one or more DCI formats. In an example, when PUSCH and SRS are transmitted in a same slot, the UE may be configured to transmit SRS after a transmission of a PUSCH and a corresponding uplink DMRS.

[0157] The base station may semi-statically configure the UE with one or more SRS configuration parameters indicating at least one of following: a SRS resource configuration identifier; a number of SRS ports; time domain behavior of an SRS resource configuration (e.g , an indication of periodic, semi-persistent, or aperiodic SRS); slot, minislot, and / or subframe level periodicity; offset for a periodic and / or an aperiodic SRS resource; a number of OFDM symbols in an SRS resource; a starting OFDM symbol of an SRS resource; an SRS bandwidth; a frequency hopping bandwidth; a cyclic shift; and / or an SRS sequence ID.

[0158] An antenna port is defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed. If a first symbol and a second symbol are transmitted on the same antenna port, the receiver may infer the channel (e.g., fading gain, multipath delay, and / or the like) for conveying the second symbol on the antenna port, from the channel for conveying the first symbol on the antenna port. A first antenna port and a second antenna port may be referred to as quasi colocated (QCLed) if one or more large-scale properties of the channel over which a first symbol on the first antenna port is conveyed may be inferred from the channel over which a second symbol on a second antenna port is conveyed. The one or more large-scale properties may comprise at least one of: a delay spread; a Doppler spread; a Doppler shift; an average gain; an average delay; and / or spatial Receiving (Rx) parameters.

[0159] Channels that use beamforming require beam management. Beam management may comprise beam measurement, beam selection, and beam indication. A beam may be associated with one or more reference signals. For example, a beam may be identified by one or more beamformed reference signals. The UE may perform downlink beam measurement based on downlink reference signals (e.g., a channel state information reference signal (CSI-RS)) and generate a beam measurement report. The UE may perform the downlink beam measurement procedure after an RRC connection is set up with a base station.

[0160] FIG. 11B illustrates an example of channel state information reference signals (CSI-RSs) that are mapped in the time and frequency domains. A square shown in FIG. 11 B may span a resource block (RB) within a bandwidth of a cell. A base station may transmit one or more RRC messages comprising CSI-RS resource configuration parameters indicating one or more CSI-RSs. One or more of the following parameters may be configured by higher layer signaling (e.g., RRC and / or MAC signaling) for a CSI-RS resource configuration: a CSI-RS resource configuration identity, a number of CSI-RS ports, a CSI-RS configuration (e.g., symbol and resource element (RE) locations in a subframe), a CSI-RS subframe configuration (e.g., subframe location, offset, and periodicity in a radio frame), a CSI-RS power parameter, a CSI-RS sequence parameter, a code division multiplexing (CDM) type parameter, a frequency density, a transmission comb, quasi co-location (QCL) parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn- subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and / or other radio resource parameters.

[0161] The three beams illustrated in FIG. 11 B may be configured fora UE in a UE-specific configuration. Three beams are illustrated in FIG. 11 B (beam #1 , beam #2, and beam #3), more or fewer beams may be configured. Beam #1 may be allocated with CSI-RS 1101 that may be transmitted in one or more subcarriers in an RB of a first symbol. Beam #2 may be allocated with CSI-RS 1102 that may be transmitted in one or more subcarriers in an RB of a second symbol. Beam #3 may be allocated with CSI-RS 1103 that may be transmitted in one or more subcarriers in an RB of a third symbol. By using frequency division multiplexing (EDM), a base station may use other subcarriers in a same RB (for example, those that are not used to transmit CSI-RS 1101) to transmit another CSI-RS associated with a beam for another UE. By using time domain multiplexing (TDM), beams used for the UE may be configured such that beams for the UE use symbols from beams of other UEs.

[0162] CSI-RSs such as those illustrated in FIG. 11B (e.g., CSI-RS 1101, 1102, 1103) may be transmitted by the base station and used by the UE for one or more measurements. For example, the UE may measure a reference signal received power (RSRP) of configured CSI-RS resources. The base station may configure the UE with a reporting configuration and the UE may report the RSRP measurements to a network (for example, via one or more base stations) based on the reporting configuration. In an example, the base station may determine, based on the reported measurement results, one or more transmission configuration indication (TCI) states comprising a number of reference signals. In an example, the base station may indicate one or more TCI states to the UE (e.g., via RRC signaling, a MAC CE, and / or a DCI). The UE may receive a downlink transmission with a receive (Rx) beam determined based on the one or more TCI states. In an example, the UE may or may not have a capability of beam correspondence. If the UE has the capability of beam correspondence, the UE may determine a spatial domain filter of a transmit (Tx) beam based on a spatial domain filter of the corresponding Rx beam. If the UE does not have the capability of beam correspondence, the UE may perform an uplink beam selection procedure to determine the spatial domain filter of the Tx beam. The UE may perform the uplink beam selection procedure based on one or more sounding reference signal (SRS) resources configured to the UE by the base station. The base station may select and indicate uplink beams for the UE based on measurements of the one or more SRS resources transmitted by the UE.

[0163] In a beam management procedure, a UE may assess (e.g., measure) a channel quality of one or more beam pair links, a beam pair link comprising a transmitting beam transmitted by a base station and a receiving beam received by the UE. Based on the assessment, the UE may transmit a beam measurement report indicating one or more beam pair quality parameters comprising, e.g., one or more beam identifications (e.g., a beam index, a reference signal index, or the like), RSRP, a precoding matrix indicator (PMI), a channel quality indicator (CQI), and / or a rank indicator (Rl).

[0164] FIG. 12A illustrates examples of three downlink beam management procedures: P1 , P2, and P3. Procedure P1 may enable a UE measurement on transmit (Tx) beams of a transmission reception point (TRP) (or multiple TRPs), e.g., to support a selection of one or more base station Tx beams and / or UE Rx beams (shown as ovals in the top row and bottom row, respectively, of P1 ). Beamforming at a TRP may comprise a Tx beam sweep for a set of beams (shown, in the top rows of P1 and P2, as ovals rotated in a counterclockwise direction indicated by the dashed arrow). Beamforming at a UE may comprise an Rx beam sweep for a set of beams (shown, in the bottom rows of P1 and P3, as ovals rotated in a clockwise direction indicated by the dashed arrow). Procedure P2 may be used to enable a UE measurement on Tx beams of a TRP (shown, in the top row of P2, as ovals rotated in a counterclockwise direction indicated by the dashed arrow). The UE and / or the base station may perform procedure P2 using a smaller set of beams than is used in procedure P1 , or using narrower beams than the beams used in procedure P1. This may be referred to as beam refinement. The UE may perform procedure P3 for Rx beam determination by using the same Tx beam at the base station and sweeping an Rx beam at the UE.

[0165] FIG. 12B illustrates examples of three uplink beam management procedures: U 1 , U2, and U3. Procedure U1 may be used to enable a base station to perform a measurement on Tx beams of a UE, e.g., to support a selection ofone or more UE Tx beams and / or base station Rx beams (shown as ovals in the top row and bottom row, respectively, of U1). Beamforming at the UE may include, e.g., a Tx beam sweep from a set of beams (shown in the bottom rows of U1 and U3 as ovals rotated in a clockwise direction indicated by the dashed arrow). Beamforming at the base station may include, e.g., an Rx beam sweep from a set of beams (shown, in the top rows of U1 and U2, as ovals rotated in a counterclockwise direction indicated by the dashed arrow). Procedure U2 may be used to enable the base station to adjust its Rx beam when the UE uses a fixed Tx beam. The UE and / or the base station may perform procedure U2 using a smaller set of beams than is used in procedure P1 , or using narrower beams than the beams used in procedure P1. This may be referred to as beam refinement The UE may perform procedure U3 to adjust its Tx beam when the base station uses a fixed Rx beam.

[0166] A UE may initiate a beam failure recovery (BFR) procedure based on detecting a beam failure. The UE may transmit a BFR request (e.g., a preamble, a UCI, an SR, a MAC CE, and / or the like) based on the initiating of the BFR procedure. The UE may detect the beam failure based on a determination that a quality of beam pair link(s) of an associated control channel is unsatisfactory (e.g., having an error rate higher than an error rate threshold, a received signal power lower than a received signal power threshold, an expiration of a timer, and / or the like).

[0167] The UE may measure a quality of a beam pair link using one or more reference signals (RSs) comprising one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more demodulation reference signals (DMRSs). A quality of the beam pair link may be based on one or more of a block error rate (BLER), an RSRP value, a signal to interference plus noise ratio (SINR) value, a reference signal received quality (RSRQ) value, and / or a CSI value measured on RS resources. The base station may indicate that an RS resource is quasi co-located (QCLed) with one or more DM-RSs of a channel (e.g., a control channel, a shared data channel, and / or the like). The RS resource and the one or more DMRSs of the channel may be QCLed when the channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameter, fading, and / or the like) from a transmission via the RS resource to the UE are similar or the same as the channel characteristics from a transmission via the channel to the UE.

[0168] A network (e.g., a gNB and / or an ng-eNB of a network) and / or the UE may initiate a random access procedure. A UE in an RRC_I DLE state and / or an RRC_INACTI\ / E state may initiate the random access procedure to request a connection setup to a network. The UE may initiate the random access procedure from an RRC_CONNECTED state. The UE may initiate the random access procedure to request uplink resources (e.g., for uplink transmission of an SR when there is no PUCCH resource available) and / or acquire uplink timing (e.g., when uplink synchronization status is non-synchronized). The UE may initiate the random access procedure to request one or more system information blocks (SIBs) (e.g., other system information such as SIB2, SIB3, and / or the like). The UE may initiate the random access procedure for a beam failure recovery request. A network may initiate a random access procedure for a handover and / or for establishing time alignment for an SCell addition.

[0169] FIG. 13A illustrates a four-step contention-based random access procedure. Prior to initiation of the procedure, a base station may transmit a configuration message 1310 to the UE. The procedure illustrated in FIG. 13A comprises transmission of four messages: a Msg 1 1311, a Msg 2 1312, a Msg 31313, and a Msg 4 1314. The Msg 1 1311 may include and / or be referred to as a preamble (or a random access preamble). The Msg 2 1312 may include and / or be referred to as a random access response (RAR).

[0170] The configuration message 1310 may be transmitted, for example, using one or more RRC messages. The one or more RRC messages may indicate one or more random access channel (RACH) parameters to the UE. The one or more RACH parameters may comprise at least one of following: general parameters for one or more random access procedures (e.g., RACH-configGeneral)', cell-specific parameters (e.g., RACH-ConfigCommon); and / or dedicated parameters (e.g., RACH-configDedicated). The base station may broadcastor multicast the one or more RRC messages to one or more UEs. The one or more RRC messages may be UE-specific (e.g., dedicated RRC messages transmitted to a UE in an RRC_CONNECTED state and / or in an RRC_I NACTIVE state) The UE may determine, based on the one or more RACH parameters, a time-frequency resource and / or an uplink transmit power for transmission of the Msg 1 1311 and / or the Msg 31313. Based on the one or more RACH parameters, the UE may determine a reception timing and a downlink channel for receiving the Msg 21312 and the Msg 4 1314.

[0171] The one or more RACH parameters provided in the configuration message 1310 may indicate one or more Physical RACH (PRACH) occasions available for transmission of the Msg 1 1311. The one or more PRACH occasions may be predefined. The one or more RACH parameters may indicate one or more available sets of one or more PRACH occasions (e.g., prach-Configlndex). The one or more RACH parameters may indicate an association between (a) one or more PRACH occasions and (b) one or more reference signals. The one or more RACH parameters may indicate an association between (a) one or more preambles and (b) one or more reference signals. The one or more reference signals may be SS / PBCH blocks and / or CSI-RSs. For example, the one or more RACH parameters may indicate a number of SS / PBCH blocks mapped to a PRACH occasion and / or a number of preambles mapped to a SS / PBCH blocks.

[0172] The one or more RACH parameters provided in the configuration message 1310 may be used to determine an uplink transmit power of Msg 1 1311 and / or Msg 3 1313. For example, the one or more RACH parameters may indicate a reference power for a preamble transmission (e.g., a received target power and / or an initial power of the preamble transmission). There may be one or more power offsets indicated by the one or more RACH parameters. For example, the one or more RACH parameters may indicate: a power ramping step; a power offset between SSB and CSI-RS; a power offset between transmissions of the Msg 1 1311 and the Msg 3 1313; and / or a power offset value between preamble groups. The one or more RACH parameters may indicate one or more thresholds based on which the UE may determine at least one reference signal (e.g., an SSB and / or CSI-RS) and / or an uplink carrier (e.g., a normal uplink (NUL) carrier and / or a supplemental uplink (SUL) carrier).

[0173] The Msg 1 1311 may include one or more preamble transmissions (e.g., a preamble transmission and one or more preamble retransmissions). An RRC message may be used to configure one or more preamble groups (e.g., group A and / or group B). A preamble group may comprise one or more preambles. The UE may determine the preamble group based on a pathloss measurement and / or a size of the Msg 31313. The UE may measure an RSRP of one or more reference signals (e.g., SSBs and / or CSI-RSs) and determine at least one reference signal having an RSRP above an RSRP threshold (e.g., rsrp-ThresholdSSB and / or rsrp-ThresholdCSI-RS). The UE may select at least one preamble associated with the one or more reference signals and / or a selected preamble group, for example, if the association between the one or more preambles and the at least one reference signal is configured by an RRC message.

[0174] The UE may determine the preamble based on the one or more RACH parameters provided in the configuration message 1310. For example, the UE may determine the preamble based on a pathloss measurement, an RSRP measurement, and / or a size of the Msg 3 1313. As another example, the one or more RACH parameters may indicate: a preamble format; a maximum number of preamble transmissions; and / or one or more thresholds for determining one or more preamble groups (e.g., group A and group B). A base station may use the one or more RACH parameters to configure the UE with an association between one or more preambles and one or more reference signals (e.g., SSBs and / or CSI-RSs). If the association is configured, the UE may determine the preamble to include in Msg 1 1311 based on the association. The Msg 1 1311 may be transmitted to the base station via one or more PRACH occasions. The UE may use one or more reference signals (e.g., SSBs and / or CSI-RSs) for selection of the preamble and for determining of the PRACH occasion. One or more RACH parameters (e.g., ra-ssb-OccasionMsklndex and / or ra-OccasionLisf) may indicate an association between the PRACH occasions and the one or more reference signals.

[0175] The UE may perform a preamble retransmission if no response is received following a preamble transmission. The UE may increase an uplink transmit power for the preamble retransmission. The UE may select an initial preamble transmit power based on a pathloss measurement and / or a target received preamble power configured by the network. The UE may determine to retransmit a preamble and may ramp up the uplink transmit power. The UE may receive one or more RACH parameters (e.g., PREAMBLE_POWER_RAMPING_STEP) indicating a ramping step for the preamble retransmission. The ramping step may be an amount of incremental increase in uplink transmit power for a retransmission. The UE may ramp up the uplink transmit power if the UE determines a reference signal (e.g., SSB and / or CSI-RS) that is the same as a previous preamble transmission. The UE may count a number of preamble transmissions and / or retransmissions (e.g., PREAMBLE 71ANSMISSION_COUNTER). The UE may determine that a random access procedure completed unsuccessfully, for example, if the number of preamble transmissions exceeds a threshold configured by the one or more RACH parameters (e.g., preambleTransMax .

[0176] The Msg 2 1312 received by the UE may include an RAR. In some scenarios, the Msg 2 1312 may include multiple RARs corresponding to multiple UEs. The Msg 2 1312 may be received after or in response to the transmitting of the Msg 1 1311. The Msg 2 1312 may be scheduled on the DL-SCH and indicated on a PDCCH using a randomaccess RNTI (RA-RNTI). The Msg 2 1312 may indicate that the Msg 1 1311 was received by the base station. The Msg 2 1312 may include a time-alignment command that may be used by the UE to adjust the UE’s transmission timing, a scheduling grant for transmission of the Msg 31313, and / ora Temporary Cell RNTI (TC-RNTI). After transmitting a preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor a PDCCH for the Msg 2 1312. The UE may determine when to start the time window based on a PRACH occasion that the UE uses to transmit the preamble. For example, the UE may start the time window one or more symbols after a last symbol of the preamble (e.g., at a first PDCCH occasion from an end of a preamble transmission). The one or more symbols may be determined based on a numerology. The PDCCH may be in a common search space (e.g., a Typel -PDCCH common search space) configured by an RRC message. The UE may identify the RAR based on a Radio Network Temporary Identifier (RNTI). RNTIs may be used depending on one or more events initiating the random access procedure. The UE may use random access RNTI (RA-RNTI). The RA-RNTI may be associated with PRACH occasions in which the UE transmits a preamble. For example, the UE may determine the RA-RNTI based on: an OFDM symbol index; a slot index; a frequency domain index; and / or a UL carrier indicator of the PRACH occasions. An example of RA-RNTI may be as follows:

[0177] RA-RNTI= 1 + sjd + 14 x tjd + 14 x 80 x fjd + 14 x 80 x 8 x ul_carrier_id, where sjd maybe an index of a first OFDM symbol of the PRACH occasion (e.g., 0 < sjd < 14), tjd may be an index of a first slot of the PRACH occasion in a system frame (e.g., 0 < tjd < 80), fjd may be an index of the PRACH occasion in the frequency domain (e.g., 0 < fjd < 8), and ul_carrierjd may be a UL carrier used for a preamble transmission (e.g., 0 for an NUL carrier, and 1 for an SUL carrier).

[0178] The UE may transmit the Msg 31313 in response to a successful reception of the Msg 2 1312 (e.g., using resources identified in the Msg 21312). The Msg 3 1313 may be used for contention resolution in, for example, the contention-based random access procedure illustrated in FIG. 13A. In some scenarios, a plurality of UEs may transmit a same preamble to a base station and the base station may provide an RAR that corresponds to a UE. Collisions may occur if the plurality of UEs interpret the RAR as corresponding to themselves. Contention resolution (e.g., using the Msg 31313 and the Msg 41314) may be used to increase the likelihood that the UE does not incorrectly use an identity of another the UE. To perform contention resolution, the UE may include a device identifier in the Msg 31313 (e.g., a C-RNTI if assigned, a TC-RNTI included in the Msg 2 1312, and / or any other suitable identifier).

[0179] The Msg 4 1314 may be received after or in response to the transmitting of the Msg 31313. If a C-RNTI was included in the Msg 31313, the base station will address the UE on the PDCCH using the C-RNTI. If the UE's unique C-RNTI is detected on the PDCCH, the random access procedure is determined to be successfully completed. If a TC-RNTI is included in the Msg 31313 (e.g., if the UE is in an RRC_I DLE state or not otherwise connected to the base station), Msg 4 1314 will be received using a DL-SCH associated with the TC-RNTI. If a MAC PDU is successfully decoded and a MAC PDU comprises the UE contention resolution identity MAC CE that matches or otherwisecorresponds with the CCCH SDU sent (e.g., transmitted) in Msg 3 1313, the UE may determine that the contention resolution is successful and / or the UE may determine that the random access procedure is successfully completed.

[0180] The UE may be configured with a supplementary uplink (SUL) carrier and a normal uplink (NUL) carrier. An initial access (e.g., random access procedure) may be supported in an uplink carrier. For example, a base station may configure the UE with two separate RACH configurations: one for an SUL carrier and the other for an NUL carrier. For random access in a cell configured with an SUL carrier, the network may indicate which carrier to use (NUL or SUL). The UE may determine the SUL carrier, for example, if a measured quality of one or more reference signals is lower than a broadcast threshold. Uplink transmissions of the random access procedure (e.g., the Msg 1 1311 and / or the Msg 3 1313) may remain on the selected carrier. The UE may switch an uplink carrier during the random access procedure (e.g., between the Msg 1 1311 and the Msg 3 1313) in one or more cases. For example, the UE may determine and / or switch an uplink carrier for the Msg 1 1311 and / or the Msg 3 1313 based on a channel clear assessment (e.g., a listen- before-talk)

[0181] FIG. 13B illustrates a two-step contention-free random access procedure. Similar to the four-step contentionbased random access procedure illustrated in FIG. 13A, a base station may, prior to initiation of the procedure, transmit a configuration message 1320 to the UE. The configuration message 1320 may be analogous in some respects to the configuration message 1310. The procedure illustrated in FIG. 13B comprises transmission of two messages: a Msg 1 1321 and a Msg 2 1322. The Msg 1 1321 and the Msg 2 1322 may be analogous in some respects to the Msg 1 1311 and a Msg 2 1312 illustrated in FIG. 13A, respectively. As will be understood from FIGS. 13A and 13B, the contention- free random access procedure may not include messages analogous to the Msg 3 1313 and / or the Msg 4 1314.

[0182] The contention-free random access procedure illustrated in FIG. 13B may be initiated for a beam failure recovery, other SI request, SCell addition, and / or handover. For example, a base station may indicate or assign to the UE the preamble to be used for the Msg 1 1321. The UE may receive, from the base station via PDCCH and / or RRC, an indication of a preamble (e.g., ra-Preamblelndex).

[0183] After transmitting a preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor a PDCCH for the RAR. In the event of a beam failure recovery request, the base station may configure the UE with a separate time window and / or a separate PDCCH in a search space indicated by an RRC message (e.g., recoverySearchSpaceld). The UE may monitor for a PDCCH transmission addressed to a Cell RNTI (C-RNTI) on the search space. In the contention-free random access procedure illustrated in FIG. 13B, the UE may determine that a random access procedure successfully completes after or in response to transmission of Msg 1 1321 and reception of a corresponding Msg 2 1322. The UE may determine that a random access procedure successfully completes, for example, if a PDCCH transmission is addressed to a C-RNTI. The UE may determine that a random access procedure successfully completes, for example, if the UE receives an RAR comprising a preamble identifier corresponding to a preamble transmitted by the UE and / or the RAR comprises a MAC sub-PDU with the preamble identifier. The UE may determine the response as an indication of an acknowledgement for an SI request.

[0184] FIG. 13C illustrates another two-step random access procedure. Similar to the random access procedures illustrated in FIGS. 13A and 13B, a base station may, prior to initiation of the procedure, transmit a configuration message 1330 to the UE. The configuration message 1330 maybe analogous in some respects to the configuration message 1310 and / or the configuration message 1320. The procedure illustrated in FIG. 13C comprises transmission of two messages: a Msg A 1331 and a Msg B 1332.

[0185] Msg A 1331 may be transmitted in an uplink transmission by the UE. Msg A 1331 may comprise one or more transmissions of a preamble 1341 and / or one or more transmissions of a transport block 1342. The transport block 1342 may comprise contents that are similar and / or equivalent to the contents of the Msg 3 1313 illustrated in FIG. 13A. The transport block 1342 may comprise UCI (e.g., an SR, a HARQ AC K / NACK, and / or the like). The UE may receive the Msg B 1332 after or in response to transmitting the Msg A 1331. The Msg B 1332 may comprise contents that are similar and / or equivalent to the contents of the Msg 2 1312 (e.g., an RAR) illustrated in FIGS. 13A and 13B and / or the Msg 4 1314 illustrated in FIG. 13A.

[0186] The UE may initiate the two-step random access procedure in FIG. 13C for licensed spectrum and / or unlicensed spectrum. The UE may determine, based on one or more factors, whether to initiate the two-step random access procedure. The one or more factors may be: a radio access technology in use (e.g., LTE, NR, and / or the like); whether the UE has valid TA or not; a cell size; the U E’s RRC state; a type of spectrum (e.g., licensed vs. unlicensed); and / or any other suitable factors.

[0187] The UE may determine, based on two-step RACH parameters included in the configuration message 1330, a radio resource and / or an uplink transmit power for the preamble 1341 and / or the transport block 1342 included in the Msg A 1331. The RACH parameters may indicate a modulation and coding schemes (MCS), a time-frequency resource, and / or a power control for the preamble 1341 and / or the transport block 1342. A time-frequency resource for transmission of the preamble 1341 (e.g., a PRACH) and a time-frequency resource for transmission of the transport block 1342 (e.g., a PUSCH) may be multiplexed using FDM, TDM, and / or CDM. The RACH parameters may enable the UE to determine a reception timing and a downlink channel for monitoring for and / or receiving Msg B 1332.

[0188] The transport block 1342 may comprise data (e.g., delay-sensitive data), an identifier of the UE, security information, and / or device information (e.g., an International Mobile Subscriber Identity (IMSI)). The base station may transmit the Msg B 1332 as a response to the Msg A 1331 . The Msg B 1332 may comprise at least one of following: a preamble identifier; a timing advance command; a power control command; an uplink grant (e.g., a radio resource assignment and / or an MCS); a UE identifier for contention resolution; and / or an RNTI (e.g., a C-RNTI or a TC-RNTI). The UE may determine that the two-step random access procedure is successfully completed if: a preamble identifier in the Msg B 1332 is matched to a preamble transmitted by the UE; and / or the identifier of the UE in Msg B 1332 is matched to the identifier of the UE in the Msg A 1331 (e.g., the transport block 1342).

[0189] A UE and a base station may exchange control signaling. The control signaling may be referred to as L1 / L2 control signaling and may originate from the PHY layer (e.g., layer 1) and / or the MAC layer (e.g., layer 2). The controlsignaling may comprise downlink control signaling transmitted from the base station to the UE and / or uplink control signaling transmitted from the UE to the base station.

[0190] The downlink control signaling may comprise: a downlink scheduling assignment; an uplink scheduling grant indicating uplink radio resources and / or a transport format; a slot format information; a preemption indication; a power control command; and / or any other suitable signaling. The UE may receive the downlink control signaling in a payload transmitted by the base station on a physical downlink control channel (PDCCH). The payload transmitted on the PDCCH may be referred to as downlink control information (DCI) . In some scenarios, the PDCCH may be a group common PDCCH (GC-PDCCH) that is common to a group of UEs.

[0191] A base station may attach one or more cyclic redundancy check (CRC) parity bits to a DCI in order to facilitate detection of transmission errors. When the DCI is intended for a UE (or a group of the UEs), the base station may scramble the CRC parity bits with an identifier of the UE (or an identifier of the group of the UEs). Scrambling the CRC parity bits with the identifier may comprise Modulo-2 addition (or an exclusive OR operation) of the identifier value and the CRC parity bits. The identifier may comprise a 16-bit value of a radio network temporary identifier (RNTI).

[0192] DCIs may be used for different purposes. A purpose may be indicated by the type of RNTI used to scramble the CRC parity bits. For example, a DCI having CRC parity bits scrambled with a paging RNTI (P-RNTI) may indicate paging information and / or a system information change notification. The P-RNTI may be predefined as “FFFE” in hexadecimal. A DCI having CRC parity bits scrambled with a system information RNTI (SI-RNTI) may indicate a broadcast transmission of the system information. The SI-RNTI may be predefined as “FFFF” in hexadecimal. A DCI having CRC parity bits scrambled with a random access RNTI (RA-RNTI) may indicate a random access response (RAR). A DCI having CRC parity bits scrambled with a cell RNTI (C-RNTI) may indicate a dynamically scheduled unicast transmission and / or a triggering of PDCCH-ordered random access. A DCI having CRC parity bits scrambled with a temporary cell RNTI (TC-RNTI) may indicate a contention resolution (e.g., a Msg 3 analogous to the Msg 3 1313 illustrated in FIG. 13A). Other RNTIs configured to the UE by a base station may comprise a Configured Scheduling RNTI (CS-RNTI), a Transmit Power Control-PUCCH RNTI (TPC-PUCCH-RNTI), a Transmit Power Control-PUSCH RNTI (TPC-PUSCH-RNTI), a Transmit Power Control-SRS RNTI (TPC-SRS-RNTI), an Interruption RNTI (INT-RNTI), a Slot Format Indication RNTI (SFI-RNTI), a Semi-Persistent CSI RNTI (SP-CSI-RNTI), a Modulation and Coding Scheme Cell RNTI (MCS-C-RNTI), and / or the like.

[0193] Depending on the purpose and / or content of a DCI, the base station may transmit the DCIs with one or more DCI formats. For example, DCI format 0_0 may be used for scheduling of PUSCH in a cell. DCI format 0_0 may be a fallback DCI format (e.g., with compact DCI payloads). DCI format 0 J may be used for scheduling of PUSCH in a cell (e.g., with more DCI payloads than DCI format 0_0). DCI format 1_0 may be used for scheduling of PDSCH in a cell. DCI format 1_0 may be a fallback DCI format (e.g., with compact DCI payloads). DCI format 1_1 may be used for scheduling of PDSCH in a cell (e.g., with more DCI payloads than DCI format 1_0). DCI format 2_0 may be used for providing a slot format indication to a group of UEs. DCI format 2 J may be used for notifying a group of UEs of aphysical resource block and / or OFDM symbol where the UE may assume no transmission is intended to the UE. DCI format 2_2 may be used for transmission of a transmit power control (TPC) command for PUCCH or PUSCH. DCI format 2_3 may be used for transmission of a group of TPC commands for SRS transmissions by one or more UEs. DCI format(s) for new functions may be defined in future releases. DCI formats may have different DCI sizes, or may share the same DCI size.

[0194] After scrambling a DCI with a RNTI, the base station may process the DCI with channel coding (e.g . , polar coding), rate matching, scrambling and / or QPSK modulation. A base station may map the coded and modulated DCI on resource elements used and / or configured for a PDCCH. Based on a payload size of the DCI and / or a coverage of the base station, the base station may transmit the DCI via a PDCCH occupying a number of contiguous control channel elements (CCEs). The number of the contiguous CCEs (referred to as aggregation level) may be 1, 2, 4, 8, 16, and / or any other suitable number. A CCE may comprise a number (e.g., 6) of resource-element groups (REGs). A REG may comprise a resource block in an OFDM symbol. The mapping of the coded and modulated DCI on the resource elements may be based on mapping of CCEs and REGs (e.g., CCE-to-REG mapping).

[0195] FIG. 14A illustrates an example of CORESET configurations for a bandwidth part. The base station may transmit a DCI via a PDCCH on one or more control resource sets (CORESETs). A CORESET may comprise a timefrequency resource in which the UE tries to decode a DCI using one or more search spaces. The base station may configure a CORESET in the time-frequency domain. In the example of FIG. 14A, a first CORESET 1401 and a second CORESET 1402 occur at the first symbol in a slot. The first CORESET 1401 overlaps with the second CORESET 1402 in the frequency domain. A third CORESET 1403 occurs ata third symbol in the slot. A fourth CORESET 1404 occurs at the seventh symbol in the slot. CORESETs may have a different number of resource blocks in frequency domain.

[0196] FIG. 14B illustrates an example of a CCE-to-REG mapping for DCI transmission on a CORESET and PDCCH processing. The CCE-to-REG mapping may be an interleaved mapping (e.g., for the purpose of providing frequency diversity) or a non-interleaved mapping (e.g., for the purposes of facilitating interference coordination and / or frequency- selective transmission of control channels). The base station may perform different or same CCE-to-REG mapping on different CORESETs. A CORESET may be associated with a CCE-to-REG mapping by RRC configuration. A CORESET may be configured with an antenna port quasi co-location (QCL) parameter. The antenna port QCL parameter may indicate QCL information of a demodulation reference signal (DMRS) for PDCCH reception in the CORESET.

[0197] The base station may transmit, to the UE, RRC messages comprising configuration parameters of one or more CORESETs and one or more search space sets. The configuration parameters may indicate an association between a search space set and a CORESET. A search space set may comprise a set of PDCCH candidates formed by CCEs at a given aggregation level. The configuration parameters may indicate: a number of PDCCH candidates to be monitored per aggregation level; a PDCCH monitoring periodicity and a PDCCH monitoring pattern; one or more DCI formats to be monitored by the UE; and / or whether a search space set is a common search space set or a UE-specific search space set. A set of CCEs in the common search space set may be predefined and known to the UE. A set of CCEs in the UE-specific search space set may be configured based on the UE’s identity (e.g., C-RNTI).

[0198] As shown in FIG 14B, the UE may determine a time-frequency resource fora CORESET based on RRC messages. The UE may determine a CCE-to-REG mapping (e.g., interleaved or non-interleaved, and / or mapping parameters) for the CORESET based on configuration parameters of the CORESET. The UE may determine a number (e.g., at most 10) of search space sets configured on the CORESET based on the RRC messages. The UE may monitor a set of PDCCH candidates according to configuration parameters of a search space set. The UE may monitor a set of PDCCH candidates in one or more CORESETs for detecting one or more DCIs. Monitoring may comprise decoding one or more PDCCH candidates of the set of the PDCCH candidates according to the monitored DCI formats. Monitoring may comprise decoding a DCI content of one or more PDCCH candidates with possible (or configured) PDCCH locations, possible (or configured) PDCCH formats (e.g., number of CCEs, number of PDCCH candidates in common search spaces, and / or number of PDCCH candidates in the UE-specific search spaces) and possible (or configured) DCI formats. The decoding may be referred to as blind decoding. The UE may determine a DCI as valid for the UE, in response to CRC checking (e.g., scrambled bits for CRC parity bits of the DCI matching a RNTI value). The UE may process information contained in the DCI (e.g., a scheduling assignment, an uplink grant, power control, a slot format indication, a downlink preemption, and / or the like).

[0199] The UE may transmit uplink control signaling (e.g., uplink control information (UCI)) to a base station. The uplink control signaling may comprise hybrid automatic repeat request (HARQ) acknowledgements for received DL- SCH transport blocks. The UE may transmit the HARQ acknowledgements after receiving a DL-SCH transport block. Uplink control signaling may comprise channel state information (CSI) indicating channel quality of a physical downlink channel. The UE may transmit the CSI to the base station. The base station, based on the received CSI, may determine transmission format parameters (e.g., comprising multi-antenna and beamforming schemes) for a downlink transmission. Uplink control signaling may comprise scheduling requests (SR). The UE may transmit an SR indicating that uplink data is available for transmission to the base station. The UE may transmit a UCI (e.g., HARQ acknowledgements (HARQ-ACK), CSI report, SR, and the like) via a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH). The UE may transmit the uplink control signaling via a PUCCH using one of several PUCCH formats.

[0200] There may be five PUCCH formats and the UE may determine a PUCCH format based on a size of the UCI (e.g., a number of uplink symbols of UCI transmission and a number of UCI bits). PUCCH format 0 may have a length of one or two OFDM symbols and may include two or fewer bits. The UE may transmit UCI in a PUCCH resource using PUCCH format 0 if the transmission is over one or two symbols and the number of HARQ-ACK information bits with positive or negative SR (HARQ-ACK / SR bits) is one or two. PUCCH format 1 may occupy a number between four and fourteen OFDM symbols and may include two or fewer bits. The UE may use PUCCH format 1 if the transmission is four or more symbols and the number of HARQ-ACK / SR bits is one or two. PUCCH format 2 may occupy one or twoOFDM symbols and may include more than two bits. The UE may use PUCCH format 2 if the transmission is over one or two symbols and the number of UCI bits is two or more. PUCCH format 3 may occupy a number between four and fourteen OFDM symbols and may include more than two bits. The UE may use PUCCH format 3 if the transmission is four or more symbols, the number of UCI bits is two or more and PUCCH resource does not include an orthogonal cover code. PUCCH format 4 may occupy a number between four and fourteen OFDM symbols and may include more than two bits. The UE may use PUCCH format 4 if the transmission is four or more symbols, the number of UCI bits is two or more and the PUCCH resource includes an orthogonal cover code.

[0201] The base station may transmit configuration parameters to the UE for a plurality of PUCCH resource sets using, for example, an RRC message. The plurality of PUCCH resource sets (e.g., up to four sets) may be configured on an uplink BWP of a cell. A PUCCH resource set may be configured with a PUCCH resource set index, a plurality of PUCCH resources with a PUCCH resource being identified by a PUCCH resource identifier (e.g., pucch-Resourceid), and / or a number (e.g a maximum number) of UCI information bits the UE may transmit using one of the plurality of PUCCH resources in the PUCCH resource set. When configured with a plurality of PUCCH resource sets, the UE may select one of the plurality of PUCCH resource sets based on a total bit length of the UCI information bits (e.g., HARQ- ACK, SR, and / or CSI). If the total bit length of UCI information bits is two or fewer, the UE may select a first PUCCH resource set having a PUCCH resource set index equal to “0”. If the total bit length of UCI information bits is greater than two and less than or equal to a first configured value, the UE may select a second PUCCH resource set having a PUCCH resource set index equal to “1”. If the total bit length of UCI information bits is greater than the first configured value and less than or equal to a second configured value, the UE may select a third PUCCH resource set having a PUCCH resource set index equal to “2”. If the total bit length of UCI information bits is greater than the second configured value and less than or equal to a third value (e.g., 1406), the UE may select a fourth PUCCH resource set having a PUCCH resource set index equal to “3”.

[0202] After determining a PUCCH resource set from a plurality of PUCCH resource sets, the UE may determine a PUCCH resource from the PUCCH resource set for UCI (HARQ-ACK, CSI, and / or SR) transmission. The UE may determine the PUCCH resource based on a PUCCH resource indicator in a DCI (e.g., with a DCI format 1_0 or DCI for 1_1) received on a PDCCH. A three-bit PUCCH resource indicator in the DCI may indicate one of eight PUCCH resources in the PUCCH resource set. Based on the PUCCH resource indicator, the UE may transmit the UCI (HARQ- ACK, CSI and / or SR) using a PUCCH resource indicated by the PUCCH resource indicator in the DCI.

[0203] FIG. 15 illustrates an example of a wireless device 1502 in communication with a base station 1504 in accordance with embodiments of the present disclosure. The wireless device 1502 and base station 1504 may be part of a mobile communication network, such as the mobile communication network 100 illustrated in FIG. 1A, the mobile communication network 150 illustrated in FIG. 1B, or any other communication network. Only one wireless device 1502 and one base station 1504 are illustrated in FIG. 15, but it will be understood that a mobile communication network mayinclude more than one UE and / or more than one base station, with the same or similar configuration as those shown in FIG. 15.

[0204] The base station 1504 may connect the wireless device 1502 to a core network (not shown) through radio communications over the air interface (or radio interface) 1506. The communication direction from the base station 1504 to the wireless device 1502 over the air interface 1506 is known as the downlink, and the communication direction from the wireless device 1502 to the base station 1504 over the air interface is known as the uplink. Downlink transmissions may be separated from uplink transmissions using FDD, TDD, and / or some combination of the two duplexing techniques.

[0205] In the downlink, data to be sent to the wireless device 1502 from the base station 1504 may be provided to the processing system 1508 of the base station 1504. The data may be provided to the processing system 1508 by, for example, a core network. In the uplink, data to be sent to the base station 1504 from the wireless device 1502 may be provided to the processing system 1518 of the wireless device 1502. The processing system 1508 and the processing system 1518 may implement layer 3 and layer 2 OSI functionality to process the data for transmission. Layer 2 may include an SDAP layer, a PDCP layer, an RLC layer, and a MAC layer, for example, with respect to FIG. 2A, FIG. 2B, FIG. 3, and FIG. 4A. Layer 3 may include an RRC layer as with respect to FIG. 2B.

[0206] After being processed by processing system 1508, the data to be sent to the wireless device 1502 may be provided to a transmission processing system 1510 of base station 1504. Similarly, after being processed by the processing system 1518, the data to be sent to base station 1504 may be provided to a transmission processing system 1520 of the wireless device 1502. The transmission processing system 1510 and the transmission processing system 1520 may implement layer 1 OSI functionality. Layer 1 may include a PHY layer with respect to FIG. 2A, FIG. 2B, FIG. 3, and FIG. 4A. For transmit processing, the PHY layer may perform, for example, forward error correction coding of transport channels, interleaving, rate matching, mapping of transport channels to physical channels, modulation of physical channel, multiple-input multiple-output (Ml MO) or multi-antenna processing, and / or the like.

[0207] At the base station 1504, a reception processing system 1512 may receive the uplink transmission from the wireless device 1502. At the wireless device 1502, a reception processing system 1522 may receive the downlink transmission from base station 1504. The reception processing system 1512 and the reception processing system 1522 may implement layer 1 OSI functionality. Layer 1 may include a PHY layer with respect to FIG. 2A, FIG. 2B, FIG. 3, and FIG. 4A. For receive processing, the PHY layer may perform, for example, error detection, forward error correction decoding, deinterleaving, demapping of transport channels to physical channels, demodulation of physical channels, MIMO or multi-antenna processing, and / or the like.

[0208] As shown in FIG. 15, a wireless device 1502 and the base station 1504 may include multiple antennas. The multiple antennas may be used to perform one or more MIMO or multi-antenna techniques, such as spatial multiplexing (e.g., single-user MIMO or multi-user MIMO), transmit / receive diversity, and / or beamforming. In other examples, the wireless device 1502 and / or the base station 1504 may have a single antenna.

[0209] The processing system 1508 and the processing system 1518 maybe associated with a memory 1514 and a memory 1524, respectively. Memory 1514 and memory 1524 (e.g., one or more non-transitory computer readable mediums) may store computer program instructions or code that may be executed by the processing system 1508 and / or the processing system 1518 to carry out one or more of the functionalities discussed in the present application. Although not shown in FIG. 15, the transmission processing system 1510, the transmission processing system 1520, the reception processing system 1512, and / or the reception processing system 1522 may be coupled to a memory (e.g., one or more non-transitory computer readable mediums) storing computer program instructions or code that may be executed to carry out one or more of their respective functionalities.

[0210] The processing system 1508 and / or the processing system 1518 may comprise one or more controllers and / or one or more processors. The one or more controllers and / or one or more processors may comprise, for example, a general-purpose processor, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) and / or other programmable logic device, discrete gate and / or transistor logic, discrete hardware components, an on-board unit, or any combination thereof. The processing system 1508 and / or the processing system 1518 may perform at least one of signal coding / processing, data processing, power control, input / output processing, and / or any other functionality that may enable the wireless device 1502 and the base station 1504 to operate in a wireless environment.

[0211] The processing system 1508 and / or the processing system 1518 may be connected to one or more peripherals 1516 and one or more peripherals 1526, respectively. The one or more peripherals 1516 and the one or more peripherals 1526 may include software and / or hardware that provide features and / or functionalities, for example, a speaker, a microphone, a keypad, a display, a touchpad, a power source, a satellite transceiver, a universal serial bus (USB) port, a hands-free headset, a frequency modulated (FM) radio unit, a media player, an Internet browser, an electronic control unit (e.g., for a motor vehicle), and / or one or more sensors (e.g., an accelerometer, a gyroscope, a temperature sensor, a radar sensor, a lidar sensor, an ultrasonic sensor, a light sensor, a camera, and / or the like). The processing system 1508 and / or the processing system 1518 may receive user input data from and / or provide user output data to the one or more peripherals 1516 and / or the one or more peripherals 1526. The processing system 1518 in the wireless device 1502 may receive power from a power source and / or may be configured to distribute the power to the other components in the wireless device 1502. The power source may comprise one or more sources of power, for example, a battery, a solar cell, a fuel cell, or any combination thereof. The processing system 1508 and / or the processing system 1518 may be connected to a GPS chipset 1517 and a GPS chipset 1527, respectively. The GPS chipset 1517 and the GPS chipset 1527 may be configured to provide geographic location information of the wireless device 1502 and the base station 1504, respectively.

[0212] FIG. 16A illustrates an example structure for uplink transmission. A baseband signal representing a physical uplink shared channel may perform one or more functions. The one or more functions may comprise at least one of: scrambling; modulation of scrambled bits to generate complex-valued symbols; mapping of the complex-valuedmodulation symbols onto one or several transmission layers; transform precoding to generate complex-valued symbols; precoding of the complex-valued symbols; mapping of precoded complex-valued symbols to resource elements; generation of complex-valued time-domain Single Carrier-Frequency Division Multiple Access (SC-FDMA) or CP- OFDM signal for an antenna port; and / or the like. In an example, when transform precoding is enabled, a SC-FDMA signal for uplink transmission may be generated. In an example, when transform precoding is not enabled, a CP-OFDM signal for uplink transmission may be generated by FIG. 16A. These functions are illustrated as examples and it is anticipated that other mechanisms may be implemented in various embodiments.

[0213] FIG. 16B illustrates an example structure for modulation and up-conversion of a baseband signal to a carrier frequency. The baseband signal may be a complex-valued SC-FDMA or CP-OFDM baseband signal for an antenna port and / or a complex-valued Physical Random Access Channel (PRACH) baseband signal. Filtering may be employed prior to transmission.

[0214] FIG. 16C illustrates an example structure for downlink transmissions. A baseband signal representing a physical downlink channel may perform one or more functions. The one or more functions may comprise: scrambling of coded bits in a codeword to be transmitted on a physical channel; modulation of scrambled bits to generate complexvalued modulation symbols; mapping of the complex-valued modulation symbols onto one or several transmission layers; precoding of the complex-valued modulation symbols on a layer for transmission on the antenna ports; mapping of complex-valued modulation symbols for an antenna port to resource elements; generation of complex-valued timedomain OFDM signal for an antenna port; and / or the like. These functions are illustrated as examples and it is anticipated that other mechanisms may be implemented in various embodiments.

[0215] FIG. 16D illustrates another example structure for modulation and up-conversion of a baseband signal to a carrier frequency. The baseband signal may be a complex-valued OFDM baseband signal for an antenna port. Filtering may be employed prior to transmission.

[0216] A wireless device may receive from a base station one or more messages (e.g. RRC messages) comprising configuration parameters of a plurality of cells (e.g. primary cell, secondary cell). The wireless device may communicate with at least one base station (e.g. two or more base stations in dual connectivity) via the plurality of cells. The one or more messages (e.g. as a part of the configuration parameters) may comprise parameters of physical, MAC, RLC, PCDP, SDAP, RRC layers for configuring the wireless device. For example, the configuration parameters may comprise parameters for configuring physical and MAC layer channels, bearers, etc. For example, the configuration parameters may comprise parameters indicating values of timers for physical, MAC, RLC, PCDP, SDAP, RRC layers, and / or communication channels.

[0217] A timer may begin running once it is started and continue running until it is stopped or until it expires. A timer may be started if it is not running or restarted if it is running. A timer may be associated with a value (e.g. the timer may be started or restarted from a value or may be started from zero and expire once it reaches the value). The duration of a timer may not be updated until the timer is stopped or expires (e.g., due to B WP switching). A timer may be used tomeasure a time period / window for a process. When the specification refers to an implementation and procedure related to one or more timers, it will be understood that there are multiple ways to implement the one or more timers. For example, it will be understood that one or more of the multiple ways to implement a timer may be used to measure a time period / window for the procedure. For example, a random access response window timer may be used for measuring a window of time for receiving a random access response. In an example, instead of starting and expiry (or expiration) of a random access response window timer, the time difference between two time stamps may be used. When a timer is restarted, a process for measurement of time window may be restarted. Other example implementations may be provided to restart a measurement of a time window.

[0218] FIGs. 17A and 17B illustrate examples procedures for beam indication based on TCI states. FIG. 17A illustrates an example of a wireless device 1700 receiving, from a base station 1720, channel-specific beam indications for separate downlink physical channels, such as the PDCCH and the PDSCH. FIG. 17B illustrates an example of a wireless device 1740 receiving, from a base station 1760, beam indications applicable (jointly) to multiple physical channels (i.e., common among physical channels), such as TCI states fordownlink receptions and / or uplink transmissions. This approach of using a TCI state for multiple physical channels as illustrated in FIG. 17B may be referred to as a unified TCI framework.

[0219] As illustrated in FIG. 17A, wireless device 1700 receives one or more RRC messages 1702 from base station 1720. One or more RRC messages 1702 may indicate one or more TCI states for one or more CORESETs. For example, RRC messages 1702 may comprise a list of TCI states (e.g., a listof IDs of TCI states) for CORESETs of wireless device 1700.

[0220] Each TCI state may indicate one or more reference signals. For example, each TCI state may comprise one or more IDs of one or more reference signals. The one or more reference signals of a TCI state may be used for channel estimation (including beam determination) such that a signal that is quasi co-located (QCL’d) with the reference signal of a TCI state may experience the same channel conditions (e.g., distortions) and properties as the reference signal of the TCI state and therefore the effects of the channel on the signal may be inferred from the effects of the channel on the reference signal as the reference signal is a known sequence (e.g., a pilot signal).

[0221] A TCI state may indicate which, so-called, large-scale channel properties may be inferred from the QCL association between a signal and a reference signal of a TCI state. To do so, each of the one or more reference signals of a TCI state may be associated with a QCL type. In an example, there may be four QCL types, such as QCL-Type A, QCL-Type B, QCL-Type C, and QCL-Type D. QCL-Type A may be used to estimate Doppler shift, Doppler spread, average delay, and delay spread QCL-Type B may be used to estimate Doppler shift and Doppler spread. QCL-Type C may be used to estimate average delay and Doppler shift. QCL-Type D may be used for spatial domain parameters (e.g., one or more parameters for spatial domain reception filters used to receive downlink signals).

[0222] A reference signal of a TCI state with a QCL type of QCL-Type D may be used for beam determination. For example, when a signal is QCL’d with a reference signal of a TCI state with QCL-Type D, wireless device 1700 maydetermine (e.g., assume or infer) that base station 1720 applies the same spatial (domain) filter to both the signal and the reference signal of the TCI states. By being able to determine (e.g., assume or infer) the spatial domain (transmission) filter applied by base station 1720 to a signal (from the spatial domain filter applied to the QCL’d reference signal), wireless device 1700 may apply a spatial domain (reception) filter suitable to receive the signal.

[0223] Returning to FIG. 17A, wireless device 1700 receives one or more RRC messages 1702 that indicate TCI states. For example, one or more RRC messages 1702 may comprise a list of TCI states of a CORESET (e.g., a list of IDs of TCI states). Wireless device 1700 may use the TCI states in the list for receiving PDCCHs on the CORESETs. The TCI states indicated by one or more RRC messages 1702 may be referred to as configured TCI states or RRC- configured TCI states.

[0224] FIG. 17A illustrates that wireless device 1700 receives MAC CE 1704 from base station 1720. MAC CE 1704 may indicate, or activate, one or more TCI states configured by one or more RRC messages 1702. For example, MAC CE 1704 may indicate a (e.g., single) TCI state for one or more CORESETs (e.g., for PDCCH receptions via the one or more CORESETs). As another example, MAC CE 1704 may activate a plurality of TCI states that may be used (applied) for PDCCH receptions via CORESETs. The TCI states indicated by MAC CE 1704 may be referred to as activated TCI states or MAC-CE activated TCI states.

[0225] Wireless device 1700 may determine one or more spatial (domain) filter parameters based on a reference signal of the TCI state. For example, FIG. 17A illustrates that wireless device 1700 receives PDCCH 1706, of a CORESET, via a TCI state of the CORESET.

[0226] For PDSCH reception, a DCI may be used to indicate which TCI state, among the (MAC-CE) activated TCI states (e.g., for the CORESETs), wireless device 1700 is to use (apply) for receiving PDSCH receptions (e.g., data, transport blocks, code block groups of a transport block). As illustrated, wireless device 1700 receives DC1 1708. DCI 1708 schedules a PDSCH transmission and indicates which TCI state, among the activated TCI states, wireless device 1700 is to use (apply) for receiving the PDSCH transmission. A TCI state indicated by a DCI may be referred to as an indicated TCI state. Similarly, a TCI state indicated by a MAC CE that indicates a single TCI (e.g., one TCI state) state may be referred to as an indicated TCI state.

[0227] Although DC1 1708 indicates a TCI state to use for receiving the scheduled PDSCH reception, wireless device 1700 may apply a different TCI state depending on an offset (e.g., in scheduling) between receiving DC1 1708 and the PDSCH reception. For example, DC1 1708 may schedule PDSCH reception 1710 within an offset 1712. Offset 1712 may be referred to as a scheduling offset. Offset 1712 may be a duration or a number of symbols. Offset 1712 may be based on a UE-capability of wireless device 1700.

[0228] Based on base station 1720 scheduling, via DC1 1708, the PDSCH reception 1710 within offset 1712, wireless device 1700 applies the TCI state of the CORESET. That is, wireless device 1700 applies the TCI state used to receive PDCCH 1706 (e.g., and does not apply the TCI state indicated by DC1 1708 for receiving PDSCH reception 1710).

[0229] Within offset 1712, wireless device 1700 may be unable to (successfully) decode DC1 1708, update the spatial filtering, and / or retune RF chains in time for receiving PDSCH reception 1710. By using the TCI state of the CORESET used to receive PDCCH 1706 (instead of the TCI state indicated in DC1 1708 for receiving the PDSCH reception 1710), this allows wireless device 1700 to receive PDSCH reception 1710 within offset 1712.

[0230] On the other hand, when, e.g., PDSCH 1710 is scheduled after offset 1712, wireless device 1700 may apply the TCI state indicated by DC1 1708 for receiving PDSCH reception 1710. For example, FIG. 17 illustrates that wireless device 1700 receives, from base station 1720, PDSCH reception 1710 via the TCI state indicated by DC1 1708. As another example, in response to DC1 1708 not comprising a field indicating a TCI state (any TCI state) for PDSCH reception 1710 (e.g., based on a DCI format of DC1 1708, such as DC1 1_0), wireless device 1700 may apply the TCI state of the CORESET for PDSCH reception 1710.

[0231] In the example illustrated in FIG. 17A, base station 1720 may transmit separate beam indications for the PDCCH and the PDSCH, along with separate beam indications for each PDSCH transmission. FIG. 17B illustrates an example of a unified TCI state framework. Under the unified TCI state framework, a single TCI state (or a set of TCI states) may be indicated for each of the downlink physical channels, such as a single T Cl state for both PDCCH and PDSCH transmissions. A TCI state that is applied to both the PDCCH and PDSCH may be referred to as a downlink TCI state or a joint-downlink TCI state (joint may refer to a TCI state being jointly applied to different physical channels). For uplink beam indications under the unified TCI state framework, the network may indicate a TCI state (or a set of TCI states) for each of the uplink physical channels, such as a single TCI state for both PUCCH and PUSCH transmissions. A TCI state that is applied to both the PUCCH and PUSCH may be referred to as an uplink TCI state or a joint-uplink TCI state.

[0232] In addition to providing TCI states that are (jointly) applied to each of the physical channels in the downlink or uplink, the unified TCI state framework may also be used to indicate a single TCI state (or a set of TCI states) for both downlink and uplink. That is, the TCI state is used for each of the physical channels of the downlink and uplink, such as the PDCCH, PDSCH, PUCCH, and PUSCH. A TCI state applicable to both downlink and uplink, the TCI state may be referred to as a joint TCI state, a joint DL / UL TCI state, or a common TCI state. A TCI state applicable to the unified TCI state framework, the TCI state may be referred to as a unified TCI state.

[0233] Returning to FIG. 17B, wireless device 1740 receives, from base station 1760, one or more RRC messages 1714. One or more RRC messages 1714 indicates a plurality of TCI states. The plurality of TCI states maybe a plurality of unified TCI states. As an example, one or more RRC messages 1714 may comprise a list of the plurality of TCI states. The list of the plurality of TCI states may be a list of joint (downlink-and-uplink) TCI states, which may be applied to both the downlink and uplink (e.g., each of the downlink and uplink physical channels). The list of joint TCI states may be a list of downlink TCI states (or joint-downlink TCI states), and the absence of a (separate) list of uplink TCI states may imply that the list of downlink TCI states is applicable to both the downlink and uplink (physical channels). In another example, one or more RRC messages 1714 may comprise separate lists of TCI states fordownlink and uplink. For example, the list of the plurality of TCI states may comprise a list of downlink TCI states and a list of uplink TCI states. Additionally or alternatively, one or more RRC messages 1714 may comprise a parameter indicating that the TCI states are joint (e.g., TCI states are applicable for both downlink and uplink) or separate (e.g., TCI states are applicable to downlink or uplink).

[0234] As another example, one or more RRC messages 1714 may indicate one (e.g., a single) TCI state instead of a plurality of TCI states. In response to one or more RRC messages 1714 indicating one TCI state, wireless device 1740 may (e.g., start to) apply the TCI state without additional signaling via MAC CE and / or DCI.

[0235] Similar to the TCI states indicated by one or more RRC messages 1702 of FIG. 17A, the plurality of TCI states indicated by one or more RRC messages 1714 may be referred to as configured TCI states or RRC-configured TCI states.

[0236] There may be two mechanisms for indicating which TCI state, among the plurality of TCI states configured by one or more RRC messages 1714, to use (apply) to transmissions between wireless device 1740 and base station 1760. In a first mechanism, wireless device 1740 receives a MAC CE 1716. MAC CE 1716 indicates a (e.g., single) TCI state, or multiple TCI states, among the plurality of TCI states indicated by one or more RRC messages 1714 (i.e., among the (RRC-)configured TCI states). For example, a field of MAC CE 1716 may indicate a (e.g., single) value (e.g., a single value ora single codepoint) that is associated with one TCI state or more TCI states (e.g., one codepoint associated with two TCI states) among the plurality of TCI states indicated by one or more RRC messages 1714.

[0237] MAC CE 1716 may indicate a TCI state to be applied to downlink and uplink. For example, MAC CE 1716 may indicate, or comprise, an ID of a TCI state among TCI states in a list of downlink TCI states (joint-downlink TCI states). As another example, MAC CE 1716 may indicate separate TCI states for downlink and uplink. For example, MAC CE 1716 may indicate an ID of a TCI from the TCI states in a list of downlink TCI states (joint-downlink TCI states) and an ID of a TCI state from TCI states in a (separate) list of uplink TCI states. To indicate the one or more TCI states, MAC CE 1716 may comprise a field and a value of the field may correspond to an ID of the TCI state. In addition, MAC CE 1716 may have an indicator associated with the field (e.g., in the same octet) that indicates whether the indicated TCI state is an uplink TCI or a downlink TCI state (e.g., the ID of the TCI state is from the list of downlink TCI states or from the list of uplink TCI states configured by one or more RRC messages 1714).

[0238] In a second mechanism for indicating which TCI state to use (apply), both MAC CE and DCI signaling is involved. As illustrated in FIG. 17B, wireless device 1740 receives MAC CE 1716. MAC CE 1716 may indicate activation of a plurality of TCI states. For example, fields of MAC CE 1716 may indicate a plurality of values (e.g., codepoints) that are associated with the plurality of TCI states (e.g , each codepoint being associated one or more TCI states) among the plurality of TCI states indicated by one or more RRC messages 1714. The TCI states activated by MAC CE 1716 may be referred to as activated TCI states. Wireless device 1740 may receive DC1 1718. DC1 1718 may indicate a TCI state among the TCI states activated by MAC CE 1716. Based on DC1 1718 indicating the TCI stateamong the (MAC-CE) activated TCI states, wireless device 1740 applies the (DCI-)indicated TCI state for receiving transmissions on physical channels.

[0239] Similar to MAC CE 1716, DC1 1718 may indicate one or more TCI states. For example, DC1 1718 may indicate a TCI state for downlink receptions (e.g., from among the plurality of TCI states activated by MAC CE 1716). DC1 1718 may indicate a TCI state for uplink transmissions (e.g., from among the plurality of TCI states activated by MAC CE 1716). As example of indicating a TCI state, DC1 1718 may comprise a field to indicate the one or more TCI states. The field may be referred to as a TCI state field. A value (e.g., a codepoint) of the TCI state field of DC1 1718 may be associated with one or more TCI states. For example, a value of the TCI state field may indicate a TCI state to be applied to downlink transmission, a value of the TCI state field may indicate a TCI state to be applied to uplink transmissions, and / or a value of the TCI state field may indicate (both) a TCI to be applied to downlink transmissions and a TCI state to be applied to uplink transmissions. One or more RRC messages 1714 may indicate the association between the vales (e.g., codepoints) of the TCI state field of DC1 1718 and the IDs of the plurality of TCI states (configured by one or more RRC messages 1714 and activated by MAC CE 1716).

[0240] A TCI state indicated by MAC CE 1716 and / or DC1 1718 may be referred to as an updated TCI state, and the indicating by MAC CE 1716 and / or DC1 1718 may be referred to as updating the (current) TCI state. That is, by indicating a TCI state for downlink and / or uplink, MAC CE 1716 (in the first mechanism) may be said to update the (indicated) TCI state. Similarly, when MAC CE 1716 indicates activation of TCI states and DC1 1718 indicates a TCI state for downlink and / or uplink, DC1 1718 may be said to update the (indicated) TCI state.

[0241] After the TCI state is indicated by MAC CE 1716 and / or DC1 1718, wireless device 1740 applies the TCI state to receive downlink receptions and / or transmit uplink transmissions. That is, the (indicated) TCI state may remain as the TCI state that wireless device 1740 applies to (subsequent) downlink receptions and uplink receptions (e.g., until the TCI state is indicated, or updated, by a subsequent MAC CE and / or DCI).

[0242] Returning to FIG. 17B, wireless device 1740 receives a DC1 1722 from base station 1760. DC1 1722 schedules one or more downlink transmissions and / or schedules (or triggers) one or more uplink transmissions. Wireless device 1740 receives downlink transmission 1724 via the TCI state (indicated by MAC CE 1716 and / or DCI 1718). In addition, wireless device 1740 transmits uplink transmission 1726 via the TCI state (indicated by MAC CE 1716 and / or DC1 1718).

[0243] FIGs. 18A, 18B, and 18C illustrate example procedures for CSI reporting triggered by the network (e.g., a base station). FIG. 18A illustrates an example of periodic CSI reporting in which a wireless device 1800 periodically transmits CSI reports to a base station 1810. FIG. 18B illustrates an example of semi-persistent CSI reporting in which a wireless device 1820, after receiving an activation command from a base station 1830, periodically transmits CSI reports to base station 1830 until wireless device 1820 receives a deactivation command from base station 1830. FIG. 18C illustrates an example of aperiodic CSI reporting in which a wireless device 1840 receives, from a base station1850, a request to transmit one or more aperiodic CSI reports to base station 1850 (e.g. , a plurality of aperiodic CSI reports may be requested, which are not periodically transmitted).

[0244] FIG. 18A illustrates wireless device 1800 receives, from base station 1810, one or more RRC messages 1802. One or more RRC messages 1802 may indicate, or comprise, parameters for periodic CSI reporting. The parameters for periodic CSI reporting may comprise, for example, one or more CSI reporting configuration parameters, such as a CSI report configuration and / or a resource configuration of reference signals (e.g., resources of reference signals).

[0245] One or more RRC messages 1802 may indicate a periodicity for CSI reporting. This may be referred to as a report periodicity type. The periodicity may indicate that report periodicity type is periodic or semi-persistent. In FIG. 18A, the one or more parameters for periodic CSI reporting, in one or more RRC messages 1802, indicate that the periodicity for CSI reporting is periodic (e.g., the periodicity is set to periodic).

[0246] The one or more parameters for periodic CSI reporting (e.g., in the CSI report configuration), of one or more RRC messages 1802, may indicate one or more quantities to measure and report. A quantity to measure and report may be referred to as a report quantity, a quantity, or a radio link quality. The report quantity of the one or more configuration parameters for periodic CSI reporting may indicate to report one or a combination of any one of the following report quantities: channel quality indicator (CQI), a rank indicator (Rl), a precoder-matrix indicator (PMI), a (e.g., strongest) layer indicator (LI or SLI), and / or a layer-1 RSRP (L1-RSRP).

[0247] The one or more parameters for periodic CSI reporting, of one or more RRC messages 1802, may indicate the (downlink) reference signals that wireless device 1800 measures to report the report quantity. For example, one or more parameters may indicate a reference signal from reference signals in a reference signal configuration. The reference signals and configurations of reference signals may be referred to as resource sets (e.g., of reference signals) and configuration of resource sets (e.g., for reference signals). The types of reference signals indicated by the one or more parameters may be CSI-RSs and / or SSBs. For example, the reference signal configuration may be a (nonzero power) CSI-RS resource set, which configures a set of CSI-RSs or a set of SSBs for CSI. The set of CSI-RSs may be one or more CSI-RSs (e.g., one CSI-RS may be configured in the set) and the set of SSBs may be one or more SSBs (e.g., one SSB may be configured in the set).

[0248] As with CSI reports, there may be three types of periodicities of (downlink) reference signals that may be measured and reported. A reference signal may be a periodic reference signal, a semi-persistent reference signal, or an aperiodic reference signal. A semi-persistent reference signal is a reference signal with a periodicity that may be (e.g., dynamically) stopped or skipped based on signaling.

[0249] The CSI reporting periodicity and the periodicity of the reference signal may be different from each other. For example, periodic CSI reporting may be reported for periodic reference signals. Semi-persistent CSI reporting may be reported for periodic reference signals and / or semi-persistent reference signals. Aperiodic CSI reporting may be reported for periodic reference signals, semi-persistent reference signals, and / or aperiodic reference signals.

[0250] In periodic CSI reporting, wireless device 1800 may not receive any signaling to begin reporting CSI (other than one or more RRC messages 1802) from base station 1810. That is, there is no (trigger) condition for periodic CSI reporting. For example, FIG. 18A illustrates that, after wireless device 1800 receives one or more RRC messages 1802, wireless device 1800 receives (e.g., starts receiving) a reference signal 1804 from base station 1810. Reference signal 1804 maybe a periodic reference signal (e.g., periodic CSI-RS or SSB), as explained above. One or more RRC messages 1808 may indicate reference signal 1804 to be used for the periodic CSI reporting (e.g., from a reference signal configuration). Wireless device the transmits a CSI report 1806 based on reference signal 1804 to base station 1810. CSI report 1806 may comprise the report quantity indicated by the one or more parameters for periodic CSI reporting in one or more RRC messages 1802. Wireless device 1800 may measure (e.g., a radio link quality) of reference signal 1804 based on the report quantity indicated by one or more RRC messages 1802.

[0251] As illustrated in FIG. 18A, wireless device 1800 periodically transmits CSI report 1806 to base station 1810. While the same CSI report 1806 is illustrated (with the same type of report quantity), a value of the report quantity may change with each transmission of CSI report 1806 based on reference signal 1804.

[0252] FIG. 18B illustrates an example of semi-persistent CSI reporting. As illustrated, wireless device 1820 receives one or more RRC messages 1808 from base station 1830. One or more RRC messages 1808 comprise parameters for semi-persistent CSI reporting. One or more RRC messages 1808 may indicate, or comprise, the same parameters discussed above one or more RRC messages 1802 in FIG. 18A. For example, one or more RRC messages 1808 may indicate a periodicity for CSI reporting. The report periodicity type in one or more RRC messages 1808 is semi- persistent (instead of periodic as in one or more RRC messages 1802). In addition, the report periodicity type may indicate one of two types of semi-persistent CSI reporting. For example, the report periodicity type may indicate semi- persistent CSI reporting on PUCCH or semi-persistent CSI reporting on RUSCH. In FIG. 18B, the report periodicity type is semi-persistent on PUSCH.

[0253] Like one or more RRC messages 1802, one or more RRC messages 1808 may indicate a report quantity and (downlink) reference signals for the semi-persistent CSI reporting (on PUCCH or PUSCH). The parameters for semi- persistent CSI reporting may indicate a periodic reference signal or a semi-persistent reference signal for wireless device 1820 to measure and report to base station 1830.

[0254] Semi-persistent CSI reporting is similar to periodic CSI reporting except that signaling is involved to activate and deactivate the CSI reporting. As illustrated, wireless device 1820 receives a command 1812 indicating activation of the (semi-persistent) CSI reporting. Command 1812 maybe an activation command. For example, command 1812 may be a MAC CE indicating activation of the semi-persistent CSI reporting (e.g., on PUCCH) or a DO indicating activation of semi-persistent CSI reporting (e.g., on PUSCH). After receiving command 1812, wireless device 1820 may (start) receiving a reference signal 1814 for CSI reporting (e.g., CSI-RS or SSB). As illustrated, wireless device 1820 does not receive (e.g., measure) reference signal 1814 until (after) wireless device 1820 receives command 1812 from base station 1830,

[0255] After base station 1830 indicates activation of semi-persistent CSI reporting via command 1812, wireless device 1820 (periodically) transmits a CSI report 1816 for reference signal 1814. CSI report 1816 indicates the reporting quantity of reference signal 1814 Similar to (periodic) CSI report 1806 of FIG. 18A, the reporting quantity in CSI report 1816 may change over time based on measurements on reference signal 1814.

[0256] Wireless device 1820 (continues) periodically transmitting CSI report 1816 until a deactivation command is received in semi-persistent CSI reporting. As illustrated, wireless device 1820 receives a command 1818 from base station 1830. Command 1818 indicates deactivation of the (semi-persistent) CSI reporting. Command 1818 may be a deactivation command. For example, command 1818 may be a MAC CE indicating deactivation of the semi-persistent CSI reporting (e.g. , on PUCCH) or a DCI indicating deactivation of semi-persistent CSI reporting (e.g . , on PUSCH). After receiving command 1818 indicating to deactivate (semi-persistent) CSI reporting, wireless device 1820 may stop transmitting (and measuring) CSI report 1816 of reference signal 1814.

[0257] FIG. 18C illustrates an example of aperiodic CSI reporting. As illustrated, wireless device 1840 receives one or more RRC messages 1822 from base station 1850. One or more RRC messages 1822 comprises parameters for aperiodic CSI reporting.

[0258] One or more RRC messages 1822 may indicate, or comprise, the same parameters discussed above one or more RRC messages 1802 in FIG. 18A for periodic CSI reporting and / or one or more RRC messages 1808 for semi- persistent CSI reporting. For example, one or more RRC messages 1822 may indicate a periodicity for CSI reporting. The report periodicity type in one or more RRC messages 1822 is aperiodic (instead of periodic or semi-persistent).

[0259] Like one or more RRC messages 1802 for periodic CSI reporting and one or more RRC messages 1808 for semi-persistent CSI reporting, one or more RRC messages 1822 may indicate a report quantity and (downlink) reference signals for the aperiodic CSI reporting (e.g., on PUSCH) The parameters for aperiodic CSI reporting may indicate one or more reference signals for aperiodic CSI reporting. The types of reference signals for aperiodic CSI reporting may be periodic reference signals, semi-persistent reference signals, and / or aperiodic reference signals. The reference signals used for aperiodic CSI reports may be CSI-RSs and / or SSBs.

[0260] For aperiodic CSI reporting, a base station 1850 may transmit a DCI indicating a request for one or more aperiodic CSI reports. The request may be a CSI request field of the DCI. One or more RRC messages 1822 may indicate an association between reference signals or reference signal resource sets) and one or more bits of a CSI requestfield of a DCI. This allows base station 1850 to (dynamically) request (or trigger) wireless device 1840 to transmit a CSI report for one or more of the reference signals (or reference signal resource sets). In addition, one or more RRC messages 1822 may indicate a size of the CSI request field of the DCI for requesting aperiodic CSI reports (e.g., a trigger size). The size of CSI request field may be 0, 1 , 2, 3, 4, 5 or 6 bits depending on the size indicated by a parameter in (the parameters for aperiodic CSI reporting of) one or more RRC messages 1822.

[0261] After receiving one or more RRC messages 1822 in FIG. 18C, wireless device 1840 receives a command 1824 from base station 1850. Command 1824 requests wireless device 1840 to transmit one or more aperiodic CSIreports 1826 of one or more reference signals 1828. Command 1824 may be a DCI. One or more aperiodic CSI reports 1826 may be a plurality of aperiodic CSI reports.

[0262] The parameters for aperiodic CSI reporting in one or more RRC messages 1822 do not comprise uplink resources for transmitting aperiodic CSI reports 1826. Instead, command 1824 indicates uplink resources (e.g., comprises an uplink grant) for one or more CSI reports 1826. As illustrated, wireless device 1840 transmits one or more CSI reports 1826 for one or more reference signals 1828. Wireless device 1840 transmits the one or more CSI reports 1826 on the PUSCH.

[0263] FIGs. 19A, 19B, and 19C illustrate example procedures for CSI reporting triggered (initiated) by the wireless device independently of the network. In periodic CSI reporting, semi-persistent CSI reporting, and aperiodic CSI reporting as illustrated in FIGs. 18A, 18B, and 18C, respectively, the network acts as a scheduler of CSI reporting and triggers the wireless device to transmit CSI reports. In the CSI reporting illustrated in FIGs. 19A, 19B, and 19C, the wireless device initiates (and triggers) CSI reporting. The example procedures in FIGs. 19A, 19B, and 19C maybe used to provide the network with CSI for use in updating a (current) TCI state, such as a TCI state used in the unified TCI framework (e.g., for downlink, uplink, and / or both downlink and uplink) as illustrated in FIG. 17B.

[0264] In the present disclosure, CSI reporting triggered by a wireless device may be referred to event-driven CSI reporting, event-based CSI reporting, UE-initiated CSI reporting, UE-initiated beam reporting, or UE-initiated beam management. Similarly, a procedure for CSI reporting triggered by the wireless device may be referred to as an event- driven CSI reporting procedure, an event-based CSI reporting procedure, a UE-initiated CSI reporting procedure, a UE- initiated beam reporting procedure, or a UE-initiated beam management procedure. A CSI report, based on CSI reporting triggered by the wireless device, may be referred to as an event-driven CSI report, an event-based CSI report, a UE-initiated CSI report, a UE-initiated beam report, or a UE-initiated beam management report. Furthermore, the terms “event-driven,” “event-based,” “event-triggered,” “UE-initiated,” “UE-triggered,” “terminal-initiated,” and “terminal- triggered” may be used to refer to CSI reporting triggered by a wireless device and CSI reports based on the same.

[0265] FIG. 19A illustrates a first mode of UE-initiated CSI reporting in which a wireless device 1900 uses (dynamic) uplink grants to transmit UE-initiated CSI reporting to a base station 1910. FIG. 19B illustrates a second mode of UE- initiated CSI reporting in which a wireless device 1920 uses preconfigured uplink resources for reporting UE-initiated CSI reports to a base station 1930. FIG. 19C illustrates a scenario in which a wireless device 1940 and a base station 1950 use a combination of the first mode of FIG. 19A (using dynamic uplink grants) and the second mode of FIG. 19B (using preconfigured uplink resources) for transmitting UE-initiated CSI reporting.

[0266] As illustrate in FIG. 19A, wireless device 1900 receives one or more RRC messages 1902 from base station 1910. One or more RRC messages 1902 may indicate, or comprise, one or more CSI reporting configuration parameters for CSI reporting (e.g., UE-initiated CSI reporting).

[0267] The one or more CSI reporting configuration parameters, in one or more RRC messages 1902, may comprise a report configuration type parameter. The report configuration type parameter may indicate that the CSI reporting, ofthe one or more CSI reporting configuration parameters, is based on wireless device 1900 detecting an event. For example, the report configuration type parameter may be set to event-triggered (or UE-initiated).

[0268] The event may be a result from a comparison of a radio link quality of a reference signal to a reference signal of a TCI state. The reference signal of the TCI state may be referred to as a current reference signal or a reference signal of a current TCI state (e.g., a TCI state that has been indicated by a MAC CE for downlink and / or uplink or a TCI state that has been activated by a MAC CE and indicated by a DCI, as discussed in connection with FIG. 17B). A QCL type of the reference signal of the TCI, used for the comparison, may be QCL-Type D. The reference signal that wireless device 1900 compares to the current reference signal of the TCI state, for detecting the event, may be referred to a candidate reference signal.

[0269] In an example, the event may be that the radio link quality of the candidate reference signal is a threshold value better than a radio link quality of a reference signal of a TCI state. For example, the event may be that the radio link quality of the candidate reference signal is better (e.g., higher) than a radio link quality of a current reference signal of a TCI state by a threshold value. That is, the amount that the radio link quality of the candidate reference signal is better (e.g., higher or greater than) the radio link quality of the current reference signal of the TCI state may be greater than, or equal to, a threshold value.

[0270] One or more RRC messages 1902 may indicate the threshold value for detecting the event. In another example, the threshold value may be preconfigured (e.g., predetermined without being signaled). The threshold value may be an RSRP value, an RSRP offset, an SINR value, or an SINR offset. Similarly, the radio link quality may be a RSRP, a layer-1 RSRP, or a signal to interference-and-noise ratio (SINR). The radio link quality may be referred to as a report quantity. One or more RRC messages 1902 may indicate in the radio link quality to report (e.g., a report quantity).

[0271] The one or more CSI reporting configuration parameters may comprise a CSI resource parameter indicating a list of candidate reference signals. The list of candidate reference signals may be for CSI reporting triggered by the wireless device based on detecting the event. The list of candidate reference signals may be referred to as a list of candidate reference signals for UE-initiated CSI reporting or a reference signal resource set for UE-initiated CSI reporting.

[0272] In an example, the list of candidate reference signals may be a (e.g., UE-specific or dedicated) list of reference signals for CSI reporting triggered by wireless device 1900. In another example, the list of candidate reference signals may be for a cell (e.g., common among wireless devices in the cell). In another example, the list of reference signals for CSI reporting may be reference signals of TCI states indicated (e.g., configured) by one or more RRC messages 1902. In another example, the list of reference signals for CSI reporting may be reference signals of TCI states activated by a MAC CE.

[0273] The one or more CSI reporting configuration parameters, indicated by one or more RRC messages 1902, may comprise an ID of a reference signal (resource) configuration. The reference signal configuration may be a CSIresource configuration ID. The reference signal configuration may indicate a list of one or more CSI-RS resource sets. The reference signals of the one or more CSI-RS resource sets may be CSI-RSs or SSBs.

[0274] The one or more CSI reporting configuration parameters may indicate PUCCH resources. The one or more CSI reporting configuration parameters may indicate a PUCCH resource among PUCCH resources of an uplink BWP. For example, the one or more CSI reporting configuration parameters, of one or more RRC messages 1902, may comprise an ID of a PUCCH resource among (IDs of) PUCCH resources of an uplink BWP.

[0275] In the first mode, the one or more CSI reporting configuration parameters may not indicate uplink resources for (transmitting) the CSI reporting. That is, the one or more CSI reporting configuration parameters may not indicate the uplink resources (e.g., PUSCH resources) for transmitting CSI reports triggered by wireless device 1900 based on detecting an event. The absence of an indication of the uplink resources to be used for transmitting CSI reports triggered by wireless device 1900 may (implicitly) indicate that the CSI reporting configuration parameters are for a first mode of CSI reporting in which the uplink resources must be requested from base station 1910 (e.g., a request for a dynamic grant).

[0276] The one or more CSI reporting configuration parameters may comprise a parameter indicating that CSI reporting, triggered by wireless device 1900 based on detecting the event (e.g., UE-initiated or event-driven CSI reporting), is enabled or activated. In an embodiment, the parameter may indicate that CSI reporting is enabled, or activated, for a cell. In another embodiment, the parameter may indicate that CSI reporting is enabled, or activated, for an uplink BWP. Additionally or alternatively to the implicit indication, the parameter (or another parameter) may (explicitly) indicate a mode that is being configured among the first mode and the second mode.

[0277] The one or more CSI reporting configuration parameters may comprise one or more timer values of one or more timers for detecting the event. Each of the one or more timers may be associated with at least one candidate reference signal among the one or more candidate reference signals.

[0278] The one or more CSI reporting configuration parameters may comprise one or more maximum count values of one or more counters of a number of times the event is detected, for one or more candidate reference signals. Each of the one or more counters may be incremented (e.g., up to an associated maximum count value among the one or more maximum count values) in response to receiving an indication (e.g., from a PHY layer of wireless device 1900) that the one or more candidate reference signals satisfy the event. Each of the one or more counters may be associated with a (respective) candidate reference signal.

[0279] The one or more CSI reporting configuration parameters may comprise, or indicate, one or more configuration parameters of an SR (e g., an SR configuration for the SR). The one or more configuration parameters of the SR may indicate a PUCCH resource, from among PUCCH resources in an uplink BWP, configured for the SR. The one or more configuration parameters of the SR indicate a periodicity and offset of the SR.

[0280] After receiving one or more RRC messages 1902, wireless device 1900 receives a reference signal 1904, of a TCI state, from base station 1910. Reference signal 1904 is a current reference signal of a TCI (an indicated TCI stateby MAC CE and / or DCI for downlink and / or uplink). As illustrated, wireless device 1900 receives a reference signal 1906. Reference signal 1906 is a candidate reference signal forCSI reporting triggered by wireless device 1900. Reference signal 1906 may be from a list of candidate reference signals in one or more RRC messages 1902. As another example, reference signal 1906 may be a reference signal of a TCI state among the (e.g., MAC CE) activated TCI states (other than reference signal 1904). In yet another example, reference signal 1906 may be a reference signal of a TCI state among the (e.g., RRC) configured TCI states.

[0281] FIG. 19A illustrates that wireless device 1900 detects an event 1908 for CSI reporting (e.g., that triggers CSI reporting). For example, as an example of event 1908, wireless device 1900 may detect that a radio link quality (e.g., L1-RSRP, L1-SINR) of reference signal 1906 is a threshold value better than (e.g., greater than by at least a threshold value) than a radio link quality of reference signal 1904 of the TCI state.

[0282] Based on detecting event 1908 for CSI reporting, wireless device 1900 transmits PUCCH transmission 1912. Wireless device 1900 may transmit PUCCH transmission 1912 via one or more PUCCH resources indicated by one or more RRC messages 1902. For example, PUCCH transmission 1912 may be transmitted via the PUCCH resource indicated by one or more RRC messages 1902.

[0283] PUCCH transmission 1912 requests uplink resources for transmitting a CSI report. The uplink resources may be PUSCH resources. As one example, PUCCH transmission 1912 may be SR. In another example, PUCCH transmission 1912 may comprise a SR. A PUCCH format of PUCCH transmission 1912 maybe PUCCH format 0 or PUCCH format 1. In yet another example, PUCCH transmission 1912 may be a UCI.

[0284] After transmitting PUCCH transmission 1912, wireless device 1900 receives DC1 1914 from base station 1910. DC1 1914 indicates uplink resources 1916 for transmitting CSI reporting based on wireless device 1900 detecting event 1908. For example, DC1 1914 may comprise an uplink grant indicating uplink resources 1916. Uplink resources 1916 may be PUSCH resources.

[0285] After receiving DC1 1914, wireless device 1900 transmits a CSI report 1918 via uplink resources 1916. For example, CSI report 1918 may be a UCI (e.g., CSI report 1918 may be a type of UCI). Wireless device 1900 may transmit the UCI on uplink resources 1916. The UCI (e.g., CSI report 1918) may be multiplexed on uplink resources 1916 (indicated by DC1 1914).

[0286] CSI report 1918 may comprise one or more radio link qualities and / or IDs of reference signals. For example, CSI report 1918 may comprise a radio link quality of (candidate) reference signal 1906. In another example, CSI report 1918 may comprise an ID of reference signal 1906. In another example, CSI report 1918 may comprise a radio link quality of (current) reference signal 1904 of the (indicated or current) TCI state In yet another example, CSI report 1918 may comprise a plurality of radio link qualities of a plurality of candidate reference signals.

[0287] The number of radio link qualities and / or reference signals indicated in CSI report 1918 may be one, greater than one, or less than or equal to a maximum number of radio link qualities for CSI reporting (e.g., one or more RRCmessages 1902 may comprise a parameter indicating the maximum number of radio link qualities for CSI reporting triggered by wireless device 1900).

[0288] The one or more radio link qualities indicated by CSI report 1918 may be absolute values, or differential values, of one or more radio link qualities of reference signals. The radio link qualities may be RSRP values, L1-RSRP values, and / or SINR values.

[0289] In an example, wireless device 1900 may monitor, detect, and / or report one or more events among a plurality of events for reporting CSI. A first event may be that a radio link quality of a candidate reference signal is a threshold value better than a radio link quality of a current reference signal of a TCI state. A second event may be that a radio link quality of a candidate reference signal is worse than a threshold. A third event may be that a radio link quality of a candidate reference signal is better than a threshold. A fourth event may be that a radio link quality of a reference signal, of a TCI state indicated by a control command, is worse than a first threshold and a radio link quality of at least one candidate reference signal is better than a second threshold. A fifth event may be that a difference between a radio link quality of a reference signal, of a TCI state indicated by a control command (e.g., DCI or MAC CE), and a radio link quality of at least one candidate reference signal is lower than a threshold. A sixth event may be that a radio link quality of the reference signal, of the T Cl state indicated by the control command, is not among a number of candidate reference signals with a highest radio link qualities. A seventh event may be that a radio link quality of at least one candidate reference signal is a threshold value better than a reference signal of a TCI state, indicated by a control command, with a worst radio link quality among reference signals of TCI states indicated by the control command. An eighth event may be that a radio link quality of at least one candidate reference signal is a threshold value better than a reference signal of a TCI state, indicated by a control command, with a highest radio link quality among reference signals of TCI states indicated by the control command. A ninth event may be that a radio link quality of a number of candidate reference signals become a threshold value better than the reference signal of the TCI state indicated by the control command. A tenth event may be that a radio link quality of at least one candidate reference signal becomes a threshold value better than a reference signal configured by one or more RRC messages. The one or more events may comprise any one or any combination of the first, second, third, fourth, fifth, sixth, seventh, eighth, ninth, and tenth events. Furthermore, wireless device 1900 may monitor, detect, and / or report events other than those listed above.

[0290] CSI report 1918 may comprise an ID of the event. The ID of the event may be referred to as an event ID. Each of the events among a plurality of events may be associated with an event ID. For example, a first value of the event ID may indicate that the first event is detected (or satisfied). A second value of the event ID may indicate that the second event is detected. A third value of the event ID may indicate that the third event is detected. A fourth value of the event ID may indicate that the fourth event is detected. A fifth value of the event ID may indicate that the fifth event is detected. A sixth value of the event ID may indicate that the sixth event is detected. A seventh value of the event ID may indicate that the seventh event is detected. An eighth value of the event ID may indicate that the eighth event isdetected. A ninth value of the event ID may indicate that the ninth event is detected. A tenth value of the event ID may indicate that the tenth event is detected.

[0291] Additionally or alternatively, PUCCH transmission 1912 may comprise, or indicate, an event ID. As an example of (implicitly) indicating an event ID, a set of PUCCH resources for PUCCH transmission 1912 may be associated with an event ID among the plurality of event IDs. Based on receiving PUCCH transmission 1912 via the set of PUCCH resources, base station 1910 may determine (e.g., infer) that the PUCCH transmission 1912 is for the associated event ID.

[0292] One or more RRC messages 1902 may comprise a list of the plurality of events and / or event IDs of the plurality of events. Each of the event IDs in CSI report 1918 (and / or PUCCH transmission 1912) may be associated with a respective reference signal (e.g., of a candidate reference signal or a reference signal of a TCI state) in CSI report 1918 (and / or PUCCH transmission 1912).

[0293] FIG. 19B illustrates a second mode of CSI reporting in which wireless device 1920 uses preconfigured uplink resources for reporting CSI, to base station 1930, based on wireless device 1920 detecting an event based on a radio link quality of a reference signal. The procedure, messages, and parameters in second mode illustrated in FIG. 19B may be the same as those discussed above in the first mode illustrated in FIG. 19A and the specific differences between the procedure, messages, and parameters in the second mode for CSI reporting based on preconfigured uplink resources will be discussed below.

[0294] As illustrated, wireless device 1920 receives one or more RRC messages 1922. One or more RRC messages 1922 may comprise, or indicate, the one or more CSI reporting configuration parameters (and other parameters) of one or more RRC messages 1902 (from FIG. 19A).

[0295] In contrast to the one or more CSI reporting configuration parameters of one or more RRC messages 1902, the one or more CSI reporting configuration parameters of one or more RRC messages 1922 indicate uplink resources 1924 for (transmitting) CSI reporting triggered by wireless device 1920. Uplink resources 1924 may be PUSCH resources or PUCCH resources for transmitting CSI reporting triggered by the wireless device 1920.

[0296] Base station 1930 may transmit the one or more CSI reporting configuration parameters of one or more RRC messages 1922 to wireless device 1920 based on receiving a UE-capability message from wireless device 1920 indicating that wireless device 1920 supports the second mode.

[0297] The presence of an indication of uplink resources 1924 may indicate to wireless device 1920 that the one or more CSI reporting configuration parameters, of one or more RRC messages 1922, are for the second mode of CSI reporting. In another example, the one or more CSI reporting configuration parameters of one or more RRC messages 1922 may comprise a parameter indicating that one or more CSI reporting configuration parameters are for reporting (e.g., UE-initiated) CSI on preconfigured uplink resources (e.g., the second mode). The parameter may indicate that the (e.g., UE-initiated) CSI reporting on preconfigured uplink resources is enabled or activated. Additionally or alternatively,the parameter (or another parameter) may (explicitly) indicate a mode that is being configured among the first mode and the second mode.

[0298] One or more RRC messages 1922 may indicate a periodicity of uplink resources 1924 (e.g., a configured (uplink) grant). The periodicity of uplink resources 1924 is illustrated in FIG. 19B. Before transmitting CSI reporting, wireless device 1920 transmits a notification to base station 1930. For example, FIG. 19B illustrates that wireless device 1920 receives a reference signal 1926. Similar to reference signal 1904 of FIG. 19A, reference signal 1926 is a (current) reference signal of a TCI state. Wireless device 1920 receives a reference signal 1928. Similar to reference signal 1906 of FIG. 19A, reference signal 1928 is a candidate reference signal.

[0299] After receiving reference signal 1926 and reference signal 1928, wireless device 1920 detects an event 1932 for CSI reporting (e.g., that triggers CSI reporting). Event 1932 may be the same as event 1908 of FIG. 19A. For example, for event 1932, wireless device 1920 may detect that a radio link quality (e.g., L1-RSRP, L1 -SI NR) of reference signal 1928 is a threshold value better than (e.g., greater than by at least a threshold value) than a radio link quality (e.g., L1-RSRP) of reference signal 1926 of the TCI state.

[0300] Based on detecting event 1932 for (UE-initiated) CSI reporting, wireless device 1920 transmits PUCCH transmission 1934 to base station 1930. Wireless device 1900 may transmit PUCCH transmission 1912 via one or more PUCCH resources indicated by one or more RRC messages 1922. As discussed above, one or more RRC messages 1922 indicate uplink resources 1924 for transmitting CSI reporting triggered by wireless device 1920. In the second mode, PUCCH transmission 1934 notifies that CSI reporting is to be transmitted on uplink resources 1924.

[0301] Similar to PUCCH transmission 1912, PUCCH transmission 1934 may be SR. In another example, PUCCH transmission 1934 may comprise a SR. A PUCCH format of PUCCH transmission 1934 may be PUCCH format 0 or PUCCH format 1. In yet another example, PUCCH transmission 1934 may be a UCI.

[0302] After transmitting PUCCH transmission 1934, wireless device 1920 transmits a CSI report 1936 via uplink resources 1924. CSI report 1936 may be a UCI. For example, wireless device 1920 may transmit the UCI on the uplink resources 1924. The UCI (e.g., CSI report 1936) may be multiplexed on uplink resources 1924 (on PUSCH). CSI report 1936 may indicate, or comprise, the same information as CSI report 1918 of FIG. 19A.

[0303] The (advance) notification, provided by PUCCH transmission 1934, may enable the network (e.g., base station 1930) to indicate (e.g., allocate) uplink resources 1924 to multiple wireless devices and reassign uplink resources 1924 prior to the (notified) CSI reporting is transmitted. In order to reassign uplink resources 1924 or otherwise prevent a collision (interference) from occurring on uplink resources 1924 when uplink resources 1924 are configured to multiple wireless devices, base station 1930 may transmit a reconfiguration (e.g., via RRC message with modified values for the parameters of one or more RRC messages 1922). In another example, the network uses a combination of the first mode and the second mode as discussed below in FIG. 19C.

[0304] FIG. 19C illustrates a scenario in which wireless device 1940 and base station 1950 use a combination of the first mode of FIG. 19A (using dynamic uplink grants) and the second mode of FIG. 19B (using preconfigured uplink resources) for reporting CSI triggered by wireless device 1940.

[0305] As illustrated, wireless device 1940 receives one or more RRC messages 1938. One or more RRC messages 1938 indicate uplink resources 1942 for transmitting CSI reporting triggered by wireless device 1940 (similar to one or more RRC messages 1922 and uplink resources 1924). After receiving one or more RRC messages 1938, wireless device 1940 receives a reference signal 1944, which may be a (current) reference signal of an (indicated) TCI state (similar to reference signal 1904 and reference signal 1926). Wireless device 1940 receives a reference signal 1946, which may be a candidate reference signal (similar to reference signal 1906 and reference signal 1928).

[0306] Based on (measurements of radio link qualities of) reference signal 1944 and reference signal 1946, wireless device 1940 detects an event 1948 for CSI reporting (e.g., that triggers UE-initiated CSI reporting). Event 1948 may be the same as event 1908 and / or event 1932 of FIGs. 19A and 19B, respectively.

[0307] Based on detecting event 1948, wireless device 1940 transmits a PUCCH transmission 1952 to base station 1950. Like PUCCH transmission 1934, PUCCH transmission notifies base station 1950 that CSI reporting is to be transmitted on uplink resources 1942.

[0308] In the example in FIG. 19C, base station 1950 may determine, after receiving PUCCH transmission 1952, that another wireless device is to transmit on uplink resources 1942. Additionally or alternatively, base station 1950 may determine that another wireless device is to perform a transmission on other radio resources (uplink or downlink) that may interfere (or collide) with the CSI reporting that wireless device 1940 intends to transmit using uplink resources 1942.

[0309] After receiving PUCCH transmission 1952, base station 1950 transmits a DC1 1954. DC1 1954 may indicate (alternative) uplink resources in order to avoid inference. For example, as illustrated, DC1 1954 indicates uplink resources 1956. Uplink resources 1956 may be the same as uplink resources 1916. For example, DC1 1954 may comprise an uplink grant indicating uplink resources 1956. Uplink resources 1956 may be PUSCH resources.

[0310] Based on receiving DC1 1954, wireless device 1940 transmits a CSI report 1958 via uplink resource 1956. Wireless device 1940 may transmit CSI report 1958 on uplink resources 1956 instead of transmitting CSI report 1958 on the preconfigured uplink resources (i.e., uplink resources 1942). For example, based on receiving DC1 1954, wireless device 1940 may cancel (or skip) transmitting CSI report 1958 on the preconfigured resources.

[0311] In existing technologies, when a wireless device transmits a CSI report to the network, the network acts as the scheduler of the CSI reporting. In doing so, the network requests that the wireless device report CSI and provides uplink resources for the wireless device to use for transmitting the CSI report. Since the network acts as a scheduler of CSI reporting, the network may appropriately allocate uplink resources between wireless devices in the network and orchestrate the CSI reporting between multiple devices.

[0312] One of the shortcomings of existing CSI reporting mechanisms is that the wireless device is in the best position to determine when to schedule CSI reporting and not the network. This is at least because the network is not aware of the radio link quality at the wireless device until the network receives reporting from the wireless device. While the introduction of UE-initiated beam reporting, or event-driven beam reporting, (as illustrated in FIGs. 19A, 19B, and 19C), may improve CSI reporting, this procedure introduces additional problems into the existing technology framework for CSI reporting.

[0313] For example, in existing technologies, when a wireless device has data to transmit on the uplink, the wireless device initially determines whether there are uplink resources (e.g. , PUSCH resources) for the data. If uplink resources are not available for the data (e.g., no PUSCH resources at all or an insufficient amount of uplink resources to accommodate the data), the wireless device may (e.g., ultimately) initiate a random-access procedure for uplink resources (PUSCH). Although this may accommodate many types of uplink transmissions, this is problematic in CSI reporting.

[0314] As an example of this problem, the wireless device may transmit the CSI report using the PUSCH resources from a random-access procedure. In addition to problems associated with the delay of using random access for uplink resources (such that the CSI report may no longer be valid), the network may not be able to (successfully) receive the CSI report even if the wireless device uses the network-scheduled uplink resources. For example, the CSI report in UE- initiated CSI reporting may be a UCI. When a UCI is transmitted on PUSCH resources, a wireless device multiplexes the UCI on the PUSCH resources. Without knowledge that the UCI will be transmitted (e.g., multiplexed) on the PUSCH resources, the network (base station) maybe unable to (successfully) receive (e.g., decode, detect) the UCI carrying the CSI report.

[0315] FIG. 20 illustrates an example scenario of a problem that may occur in wireless device communication between a wireless device 2000 and a base station 2020 based on implementing existing technologies in CSI reporting triggered by a wireless device.

[0316] As illustrated at to in FIG. 20, wireless device 2000 receives, from base station 2020, one or more RRC messages 2002. One or more RRC messages 2002 indicates one or more TCI states and one or more reference signals. The one or more reference signals may be candidate reference signals to be used in UE-initiated CSI reporting.

[0317] At t1 in FIG. 20, wireless device 2000 receives a control command 2004 from base station 2020. Control command may be a MAC CE that indicates a TCI state 2006 to be used by wireless device 2000. For example, the TCI state 2006 may be indicated to be used for downlink transmissions, uplink transmissions, or (jointly) uplink and downlink transmissions under the unified TCI state framework (as discussed above in connection with FIG. 17B). On the other hand, control command 2004 may be a DCI that indicates TCI state 2006. For example, the DCI may indicate TCI state 2006 among one or more TCI states that are activated by a MAC CE among the TCI states 2002 configured by one or more RRC messages 2002.

[0318] At t2 in FIG. 20, wireless device 2000 may detect an event 2010 that triggers wireless device 2000 to report CSI of a candidate reference signal among one or more reference signals configured by one or more RRC messages 2002. For example, wireless device 2000 may determine that a layer-1 RSRP of the candidate reference signal is better (e.g., higher) than a layer-1 RSRP of a reference signal of TCI state 2006 (e.g., by a threshold value).

[0319] At t3 in FIG. 20, wireless device 2000 triggers a PUCCH transmission 2012 for the CSI reporting based on detecting the event. PUCCH transmission 2012 be triggered for requesting uplink resources from base station 2020 (e.g., a dynamic uplink grant), such as in the first mode illustrated in FIG. 19A. PUCCH transmission 2012 may triggered for notifying base station 2020 that CSI reporting triggered by wireless device 2000 is to be transmitted on preconfigured PUSCH resources. However, wireless device 2000 is ultimately not be able to transmit PUCCH 2012.

[0320] At t4 in FIG. 20, wireless device 2000 initiates a random-access procedure 2016 for CSI report 2014. As illustrated at t5, wireless device 2000 may transmit a preamble 2018 during random-access procedure 2016. In response to receiving preamble 2018 from wireless device 2000, base station 2020, at t6, transmits an uplink grant 2018 (PUSCH resources) to wireless device 2000.

[0321] At t7, wireless device 2000 has available uplink resources based on uplink grant 2018 from base station 2020. Based on the uplink resources being available, wireless device 2000 transmits CSI report 2014 on a PUSCH transmission via the uplink resources of uplink grant 2018. However, even though the base station 2020 assigned the uplink resources to wireless device 2000, base station 2020 may be unable to (successfully) receive CSI report 2012 at t7. This is because base station 2020 is unaware of the contents of the uplink transmission from wireless device 2000.

[0322] For example, when PUCCH transmission 2012 is (successfully) transmitted, base station 2020 may monitor for CSI report 2014. On the other hand, when wireless device 2000 uses random-access procedure 2016 to request uplink resources, base station 2020 may not monitor for CSI report 2014. Although existing technologies may use a random-access procedure for transmissions (e.g., beam failure), CSI report 2014 in FIG. 20 may be a UCI that is multiplexed on the PUSCH resources provided by uplink grant 2018. Unlike other process that may utilize randomaccess procedures (such as transmitted MAC CEs on PUSCH), base station 2020 is unable to decode (e.g., demultiplex) UCI on PUSCH unless base station 2020 is aware and decodes for such UC I -multiplexed transmissions.

[0323] This may cause decrease, or eliminate, some of the benefits provided by UE-initiated CSI reporting since the base station may not be able to (successfully) receive the CSI reporting triggered by the wireless device. Furthermore, this may decrease the reliability of the network since, without the CSI reporting, radio link quality may worsen to an extent that beam failure occurs. In addition, signaling overhead may occur due to repeated signaling attempts made by the wireless device. As another example, this misalignment between the understanding of the wireless device and the network may cause wasted internal resources (e.g., power and computational) at the wireless device since the CSI reporting is not being properly received by the network (unbeknown to the wireless device). Therefore, there is a need to improve existing procedures for uplink transmissions when UE-initiated, event-driven, CSI reporting is introduced.

[0324] According to embodiments of the present disclosure, a wireless device performs detection of an event, which triggers CSI reporting by the wireless device, based on a radio link quality of a candidate reference signal in response to activating an uplink BWP configured with PUCCH resources for the CSI reporting. In an embodiment, the wireless device according to embodiments of the present disclosure, may monitor for indications that the event is satisfied, based on activating an uplink BWP configured PUCCH resources for the CSI reporting.

[0325] By performing the detection of the event for the candidate reference signals based on the active uplink BWP being configured with the PUCCH resources, the embodiments of the present disclosure may increase network reliability since the network (base station) may be able to successfully receive the CSI reporting triggered by the wireless device. Furthermore, power consumption (and internal resource utilization) may be improved at the wireless device since CSI reporting may not be performed when the network (ultimately) cannot successfully receive the CSI reporting. In addition, signaling overhead may be reduced since procedures, such as random-access, may no longer be performed that involve numerous messages being transmitted and received between the wireless device and the base station. These and other additional effects may be provided by aspects of embodiments of the present disclosure.

[0326] FIGs. 21 A and 21 B illustrate aspects of one or more embodiments of the present disclosure. FIG. 21A illustrates aspects of an embodiment in which (UE-initiated) CSI reporting is triggered by a wireless device 2100 and is reported to a base station 2120 using a dynamic grant (such as the first mode as illustrated in FIGs. 19A and 19C). FIG. 21 B illustrates aspects of an embodiment in which (UE-initiated) CSI reporting is triggered by a wireless device 2140 and is reported to a base station 1960 using preconfigured uplink resources (such as the second mode illustrated in FIGs. 19B and 19C).

[0327] The procedure, messages, and parameters illustrated in FIG. 21A and 21 B may be the same as those discussed above in the first mode illustrated in FIG. 19A and in the second mode illustrated in FIG. 19B. The specific differences between the procedure, messages, and parameters for CSI reporting according to embodiments of the present disclosure will be discussed below. It should be understood that these features may be combined, substituted, or modified with any of the features discussed above or below.

[0328] As illustrated in FIG. 21A, wireless device 2100 receives, from base station 2120, one or more RRC messages 2102. One or more RRC messages 2102 may comprise, or indicate, any of the parameters for (UE-initiated) CSI reporting discussed above in connection with one or more RRC messages 1902 of FIG. 19A, one or more RRC messages 1922 of FIG. 19B, and / or one or more RRC messages 1938 of FIG. 19C.

[0329] One or more RRC messages 2102 may indicate (e.g. , identify) PUCCH resources for transmitting a PUCCH transmission to request uplink resources for CSI reporting triggered by wireless device 2100. For example, FIG. 21A illustrates that one or more RRC messages 2102 indicate PUCCH resources 2104. One or more RRC messages 2102 may indicate a PUCCH resource among PUCCH resources 2104. One or more RRC messages 2102 may indicate PUCCH resources 2104 of a BWP of a cell. The BWP may be an uplink BWP of the cell. Additionally or alternatively, one or more RRC messages 2102 may indicate, for the PUCCH transmission to request uplink resources for CSIreporting triggered by wireless device 2100, PUCCH resources of BWPs of a cell and / or a PUCCH resources, among PUCCH resources 2104, of a BWP among the BWPs of the cell.

[0330] FIG. 21A illustrates that wireless device 2100 determines whether PUCCH resources 2104 are configured in an active uplink BWP. For example, wireless device 2100 may determine whether the active uplink BWP is a BWP configured with PUCCH resources 2104. Wireless device 2100 may determine the active uplink BWP is a BWP configured with PUCCH resources 2104 for transmitting a PUCCH transmission to request uplink resources for CSI reporting triggered by wireless device 2100. This determination may be made before (prior to) triggering CSI reports detected by wireless device 2100. In another example, this determination may be made after triggering CSI reports by wireless device 2100.

[0331] In response to PUCCH resources 2104 not being configured in the active uplink BWP, wireless device 2100 may not perform (or trigger) CSI reporting (e.g., or a procedure for CSI reporting) detected by wireless device 2100. For example, in response to PUCCH resources 2104 not being configured in the active uplink BWP, wireless device 2100 may not perform (e.g., end, stop, skip, start, initiate) a (UE-initiated) CSI reporting procedure of a (candidate) reference signal.

[0332] As one example of PUCCH resources 2104 not being configured in the active uplink BWP, PUCCH resources 2104 may be configured on another uplink BWP other than the active uplink BWP (on the same cell or a different cell). For example, PUCCH resources 2104 may be configured on an initial uplink BWP and the initial uplink BWP may not be the active uplink BWP (e.g., may no longer be the active uplink BWP). Based on PUCCH resources 2104 not being configured in the active uplink BWP, wireless device 2100 does not perform (UE-initiated) CSI reporting triggered by wireless device 2100.

[0333] As another example, PUCCH resources 2104 may be configured on an uplink BWP (other than the initial uplink BWP) and not on an initial uplink BWP. When the active uplink BWP of wireless device 2100 is the initial uplink BWP, wireless device 2100 may determine that PUCCH resources 2104 are not configured on the active uplink BWP. Based on PUCCH resources 2104 not being configured in the active uplink BWP, wireless device 2100 does not perform (UE-initiated) CSI reporting triggered by wireless device 2100. Another example of an uplink BWP may be a first active uplink BWP.

[0334] As another example, wireless device 2100 may determine that the active uplink BWP is configured with PUCCH resources (e.g., for other purposes) that are not for transmitting a PUCCH transmission to request uplink resources for CSI reporting triggered by wireless device 2100. For example, wireless device 2100 may determine that PUCCH resources of the active uplink BWP do not comprise a PUCCH resource, indicated by one or more RRC messages 2102, for the PUCCH transmission to request uplink resources for CSI reporting triggered by wireless device 2100.

[0335] Returning to FIG. 21 A, wireless device 2100 may determine that PUCCH resources 2104 are configured on the active uplink BWP.

[0336] As an example, wireless device 2100 may determine that the active uplink BWP is configured with PUCCH resources 2104 that are for transmitting a PUCCH transmission to request uplink resources for CSI reporting triggered by wireless device 2100. For example, wireless device 2100 may determine that PUCCH resources 2104 of the active uplink BWP comprise a PUCCH resource, indicated by one or more RRC messages 2102, for the PUCCH transmission to request uplink resources for CSI reporting triggered by wireless device 2100.

[0337] Based on determining that PUCCH resources 2104 are configured on the active uplink BWP, wireless device 2100 may perform a procedure for CSI reporting triggered by wireless device 2100. As illustrated, wireless device 2100 in FIG. 21 performs a procedure 2106 for CSI reporting triggered by wireless device 2100. Procedure 2106 may be implemented based on the first and / or second modes of (UE-initiated) CSI reporting discussed above with reference to FIGs. 19A and 19C. Procedure 2106 is triggered by wireless device 2100 (e.g., as opposed to CSI reporting triggered by the network or a base station, such as periodic CSI reporting in FIG. 18A, the semi-persistent CSI reporting in FIG. 18B, and the aperiodic CSI reporting in FIG. 18B).

[0338] Wireless device 2100 may (e.g., start to) monitor one or more (candidate) reference signals for CSI reporting triggered by wireless device 2100. For example, wireless device 2100 may (e.g., start to) monitor one or more (candidate) reference signals for CSI reporting triggered by wireless device 2100. Wireless device 2100 may (e.g., start to) detect whether one or more candidate reference signals satisfies an event for responding CSI triggered by wireless device 2100. Wireless device 2100 may (e.g., start to) measure one or more (candidate) reference signals to detect an event for CSI reporting triggered by wireless device 2100. Wireless device 2100 may (e.g., start to) assess radio link qualities of one or more (candidate) reference signals to detect an event for CSI reporting triggered by wireless device 2100. Wireless device 2100 may (e.g., start to) compare radio link qualities of one or more (candidate) reference signals with a radio link quality of a reference signal of an (indicated) TCI state to detect an event for CSI reporting triggered by wireless device 2100.

[0339] As an example of monitoring, the PHY layer of wireless device 2100 may measure a radio link quality of one or more candidate reference signals (e.g., configured by one or more RRC messages 2102). The PHY layer of wireless device 2100 may send (report) indications of the radio link quality of a candidate reference signal to a MAC layer of wireless device 2100. The indications may be referred to as, e.g., triggering event instance indications or eventdetection instance indications. The PHY layer of wireless device 2100 may send an indication to the MAC layer of wireless device 2100 in response to the radio link quality of a candidate reference signal, among the one or more candidate reference signals, satisfying an event.

[0340] The event in procedure 2106 may be, for example, any of the events described above in connection with FIGs. 19A, 19B and 19C. For example, the event may be that a radio link quality of a candidate reference signal satisfies an event (e.g., the event is detected). The event may be a comparison of radio link quality of reference signals. For example, the comparison may be a comparison of a radio link quality of a (candidate) reference signal to a radiolink quality of a (current) reference signal of a TCI state. The event may be that a radio link quality of a candidate reference signal is a threshold better than a radio link quality of the current reference signal of the TCI state.

[0341] The TCI state of the current reference signal may be the TCI state that has been indicated by a MAC CE and / or activated by a MAC CE and indicated by a DCI, as described above in FIG. 17B as well as FIGs. 19A, 19B and 19C. The TCI state may be referred to as an activated TCI state or an indicated TCI state.

[0342] As additional examples of performing procedure 2106, wireless device 2100 may control one or more timers for detecting the event and / or one or more counters for detecting the event. For example, in response to activating the uplink BWP configured with the PUCCH resources 2104, wireless device 2100 may stop one or more timers for detecting the event in response to the one or more timers being running.

[0343] Additionally or alternatively, wireless device 2100 may start one or more timers for detecting the event in response to receiving an indication that one or more candidate reference signals satisfies the event. In response to activating the uplink BWP configured with the PUCCH resource, wireless device 2100 may set a value of one or more counters of a number of times the event is detected to zero. Wireless device 2100 may increment a counter of a number of times the event is detected in response to receiving an indication that a candidate reference signal satisfies the event.

[0344] In another example, one indication (e.g ., a single indication or instance) may be used for (UE-initiated) CSI reporting detected by wireless device 2100. For example, (e.g., the MAC layer of) wireless device 2100 may not use (or be configured with by one or more RRC messages 2102) the one or more counters and / or one or more timers for detecting the event. Wireless device 2100 may perform (UE-initiated) CSI reporting based on detecting (e.g., by the PHY layer of wireless device 2100) the one indication that one or more candidate reference signals satisfies the event.

[0345] Returning to FIG. 21A, wireless device 2100 detects that a candidate reference signal satisfies an event 2108 for (UE-initiated) CSI reporting. In response to detecting that a candidate reference signal satisfies event 2108, wireless device 2100 may (ultimately) transmit CSI reporting to base station 2120 (e.g., the network).

[0346] As explained above with reference to FIGs. 19A, 19B, and 19C, there may be multiple modes for transmitting CSI reports triggered by wireless device 2100. FIG. 21A illustrates aspects of an embodiment based, at least in part, on the first mode illustrated in FIG. 19A and 19C in which dynamic uplink grants are used for transmission of (UE-initiated) CSI reporting.

[0347] After detecting event 2108, wireless device 2100 transmits a PUCCH transmission 2110 for uplink resources. PUCCH transmission 2110 may be the same as PUCCH transmission 1908 of FIG. 19A, PUCCH transmission 1934 of FIG. 19B, and / or PUCCH transmission 1952 of FIG. 19C For example, PUCCH transmission 2110 may request uplink resources for (UE-initiated) CSI reporting. PUCCH transmission 2110 may be referred to as a request. As an example, PUCCH transmission 2110 may be a SR. As another example, PUCCH transmission 2110 may comprise an SR (e.g., a PUCCH format of PUCCH transmission 2110 may comprise at least one bit that correspond to an SR). As yet another example, PUCCH transmission 2110 may be, or comprise, UCI.

[0348] Wireless device 2100 transmits PUCCH transmission 2110 via PUCCH resources 2104. For example, wireless device 2100 transmits PUCCH transmission 2110 on the active uplink BWP, and the active uplink BWP comprises (e.g . , is configured with) PUCCH resources 2104. By performing the determination of whether PUCCH resources 2104 are configured in the active uplink BWP, PUCCH resources 2104 are (determined to be) available (e.g., in advance) to wireless device 2100.

[0349] Based on wireless device 2100 using PUCCH resources 2104, base station 2120 may determine that PUCCH transmission 2110 are for CSI reporting triggered by wireless device 2100. For example, base station 2120 may configure wireless device 2100 with multiple sets of PUCCH resources (e.g., by one or more RRC messages 2102). Instead of (or in addition to) explicitly indicating a purpose of a transmission using the PUCCH resources in the transmission itself (e.g., by a field), an implicit indication of the purpose of the transmission may be used based on which set of PUCCH resources are used for a transmission. For example, base station 2120 may determine (e.g., infer) the purpose of transmission of an SR based on which PUCCH resources wireless device 2100 uses to transmit the SR

[0350] Based on receiving PUCCH transmission 2110, base station 2120 transmits DCI 2112 to wireless device 2100. DCI 2112 indicates uplink resources 2114. For example, DCI 2112 may comprise one or more fields that indicate one or more parameters for transmitting on uplink resources 2114. DCI 2112 may be referred to as indicating, or comprising, a dynamic grant. The dynamic grant may indicate uplink resources 2114, which wireless device 2100 may use to transmit (UE-initiated) CSI reporting.

[0351] Based on receiving DCI 2112, wireless device 2100 transmits a CSI report 2116 via uplink resources 2114. CSI report 2116 may be the same as CSI report 1918 of FIG. 19A, CSI report 1936 of FIG. 19B, or CSI report 1958 of FIG. 19C. As an example, CSI report 2116 may be a UCI, and uplink resources 2114 may be PUSCH resources. Wireless device 2100 may transmit a UCI (e.g., CSI report 2116) on the PUSCH resources indicated by DCI 2112. For example, the UCI may be multiplexed on the PUSCH resources indicated by DCI 2112.

[0352] As discussed above, base station 2120 may determine (e.g., infer) the purpose of PUCCH transmission 2110 from wireless device 2100 from PUCCH resources 2104. That is, base station 2120 may determine that wireless device 2100 is to transmit (UE-initiated) CSI reporting triggered by wireless device 2100 using (requested) uplink resources 2114. This may enable base station 2120 to receive CSI report 2116 from wireless device 2100. For example, base station 2120 may (successfully) receive CSI report 2116 from wireless device 2100 by demultiplexing (and / or decoding) a UCI (e.g., CSI report 2116) on uplink resources 21114 (e.g., PUSCH resources or UCI on PUSCH).

[0353] By determining whether PUCCH resources 2104 are configured on an active uplink BWP, wireless device 2100 is able to transmit PUCCH transmission 2110 in response to determining event 2108 for CSI report 2116. On the other hand, if PUCCH resources 2104 were not configured on the active uplink BWP (e.g., another uplink BWP is the active uplink BWP), wireless device 2100 may not be able to transmit PUCCH transmission 2110 in response to detect event 2108 and, for example, waste internal resources.

[0354] As another example, wireless device 2100 may, based on not PUCCH resources 2104 not being configured on the active uplink BWP, wireless device 2100 may initiate a random access procedure for uplink resources of CSI report 2116 However, as described above in connection with FIG. 20, this may result in base station 2120 (the network) being unable to (successfully) receive (decode or demultiplex) CSI report 2116, such as a UCI on PUSCH.

[0355] For example, base station 2120 may, based on a random access procedure, grant wireless device 2100 uplink resources (e.g., PUSCH resources) and base station 2120 may be unaware that wireless device 2100 is to transmit (intends to transmit) CSI report 2116 on uplink resources from a random access procedure.

[0356] By performing procedure 2106 based on (e.g., determining that) PUCCH resources 2104 are configured on an active uplink BWP, embodiments of the present disclosure may avoid these types of problems that may occur. This may increase reliability of the network (e.g., as base station 2120 may successfully receive CSI report 2116) as well as decrease signaling overhead (e.g., by avoiding repeated transmissions) and improve power consumption (e.g., by wireless device 2100 not (re)performing procedure 2106 when base station 2120 may not be able to successfully receive CSI report 2116).

[0357] As described above, FIG. 21 A illustrates aspects of an embodiment of the present disclosure in which dynamic uplink grants are used for transmitting (UE-initiated) CSI reporting. As another example, FIG. 21 B illustrates aspects of an embodiment in which (UE-initiated) CSI reporting is triggered by wireless device 2140 and is reported to base station 2160 using preconfigured uplink resources (such as the second mode illustrated in FIGs. 19B and 19C).

[0358] The procedure, messages, and parameters illustrated in FIG. 21 B may be the same as those discussed above with and FIG. 21A as well as in the second mode illustrated in FIG. 19B. The specific differences between the procedure, messages, and parameters for CSI reporting according to embodiments of the present disclosure will be discussed below. It should be understood that these features may be combined, substituted, or modified with any of the features discussed above or below.

[0359] As illustrated in FIG. 21 B, wireless device 2140 receives, from base station 2160, one or more RRC messages 2118. One or more RRC messages 2118 may comprise, or indicate, any of the parameters for (UE-initiated) CSI reporting discussed above in connection with one or more RRC messages 1902 of FIG. 19A, one or more RRC messages 1922 of FIG. 19B, one or more RRC messages 1938 of FIG. 19C, and / or one or more RRC messages 2102 of FIG. 21A.

[0360] One or more RRC messages 2118 indicate PUCCH resources 2122. One or more RRC messages 2118 may indicate a PUCCH resources among PUCCH resources 2122 (similar to one or more RRC messages 2102 and PUCCH resources 2104).

[0361] For (transmitting) CSI reporting triggered by wireless device 2140, one or more RRC messages 2118 indicate uplink resources 2124. Uplink resources 2124 may be the same as the (preconfigured) uplink resources 1924 and uplink resources 1942 of FIGs. 19B and 19C, respectively.

[0362] As described in greater detail above in FIG. 21A, wireless device 2140 determines whether PUCCH resources 2122 are configured in an active uplink BWP. In response to PUCCH resources 2122 not being configured in the active uplink BWP, wireless device 2140 may not perform (or trigger) CSI reporting (e.g. , or a procedure for CSI reporting) detected by wireless device 2140.

[0363] Based on determining that PUCCH resources 2122 are configured on the active uplink BWP, wireless device 2140 performs a procedure 2126 for CSI reporting triggered by wireless device 2140. Procedure 2126 maybe the same as procedure 2106 and may be implemented based on the first and / or second modes of (UE-initiated) CSI reporting discussed above with reference to FIGs. 19B and 19C. Procedure 2126 is triggered by wireless device 2140 (e.g., as opposed to CSI reporting triggered by the network ora base station, such as periodic CSI reporting in FIG. 18A, the semi-persistent CSI reporting in FIG. 18B, and the aperiodic CSI reporting in FIG. 18B).

[0364] Returning to FIG. 21 B, wireless device 2140 detects that a (candidate) reference signal satisfies an event 2128. Event 2128 may be the same as event 2108 for (UE-initiated) CSI reporting. In response to detecting that a candidate reference signal satisfies event 2128, wireless device 2140 may (ultimately) transmit CSI reporting to base station 2160 (e.g., the network). FIG. 21 B illustrates aspects of an embodiment based, at least in part, on the second mode illustrated in FIG. 19B and 19C in which preconfigured uplink resources are used for transmission of (UE- initiated) CSI reporting. The preconfigured uplink resources maybe referred to as a preconfigured uplink grant.

[0365] After detecting event 2128, wireless device 2140 transmits a PUCCH transmission 2132 for uplink resources 2124. PUCCH transmission 2132 may be the same as PUCCH transmission 1908 of FIG. 19A, PUCCH transmission 1934 of FIG. 19B, PUCCH transmission 1952 of FIG. 19C, and PUCCH transmission 2110 of FIG. 21 A. For example, PUCCH transmission 2132 may notify (base station 2160) that (UE-initiated) CSI reporting is to be transmitted on uplink resources 2124. PUCCH transmission 2132 may be referred to as a notification. As an example, PUCCH transmission 2132 may be a SR. As another example, PUCCH transmission 2132 may comprise an SR (e.g., a PUCCH format of PUCCH transmission 2132 may comprise at least one bit that correspond to an SR). As yet another example, PUCCH transmission 2132 maybe, or comprise, UCI.

[0366] Wireless device 2140 transmits PUCCH transmission 2132 via PUCCH resources 2122. For example, wireless device 2140 transmits PUCCH transmission 2132 on the active uplink BWP, and the active uplink BWP comprises (e.g., is configured with) PUCCH resources 2122. By performing the determination of whether PUCCH resources 2122 are configured in the active uplink BWP, PUCCH resources 2122 are (determined to be) available (e.g., in advance) to wireless device 2140.

[0367] After transmitting PUCCH transmission 2132, wireless device 2140 transmits a CSI report 2134 via uplink resources 2124. CSI report 2134 maybe the same as CSI report 1918 of FIG. 19A, CSI report 1936 of FIG. 19B, CSI report 1958 of FIG. 19C, or CSI report 2116 of FIG. 21A. As an example, CSI report 2134 may be a UCI (e.g., CSI report 2134 may be a type of UCI), and uplink resources 2124 may be PUSCH resources. Wireless device 2140 maytransmit a UCI (e.g., CSI report 2134) on the PUSCH resources indicated by one or more RRC messages 2118. For example, the UCI may be multiplexed on the PUSCH resources indicated by one or more RRC messages 2118.

[0368] As discussed above with reference to FIG. 21A, base station 2160 may determine (e.g., infer) the purpose of PUCCH transmission 2132 from wireless device 2140 from PUCCH resources 2122. That is, base station 2160 may determine that wireless device 2140 is to transmit (UE-initiated) CSI reporting triggered by wireless device 2140 using (preconfigured) uplink resources 2124. This may enable base station 2160 to (successfully) receive (e.g., decode, demultiplex) CSI report 2134 from wireless device 2140.

[0369] It should be understood that FIGs. 21 A and 21 B are provided as examples and that embodiments of the present disclosure may be applied to UE-initiated CSI reporting regardless of whether dynamic or preconfigured uplink resources are used to transmit the UE-initiated CSI reporting.

[0370] The features discussed above in connection with UE-initiated CSI reporting may be combined with CSI reporting triggered by the network as illustrated in FIGs. 18A, 18B, and 18C. As an example based on FIGs. 18A, wireless device 2100 (or wireless device 2140) may receive one or more RRC messages 1802 comprising configuration parameters for periodic CSI reporting. Wireless device 2100 (or wireless device 2140) may transmit one or more periodic CSI reports 1806 in response to receiving the one or more RRC messages 1802 comprising configuration parameters for periodic CSI reporting.

[0371] As an example based on FIGs. 18B, wireless device 2100 (or wireless device 2140) may receive one or more RRC messages 1808 comprising configuration parameters for semi-persistent CSI reporting. Wireless device 2100 (or wireless device 2140) may receive command 1812 indicating activation of the semi-persistent CSI reporting and may transmit one or more semipersistent periodic CSI reports 1816 in response to command 1812. Additionally or alternatively, wireless device 2100 (or wireless device 2140) may receive command 1818 indicating deactivation of the semi-persistent CSI reporting and may stop transmit one or more semipersistent periodic CSI reports 1816 in response to command 1818.

[0372] As an example based on FIGs. 18C, wireless device 2100 (or wireless device 2140) may receive one or more RRC messages 1822 comprising configuration parameters for aperiodic CSI reporting. Wireless device 2100 (or wireless device 2140) may receive command 1824 (e.g., a DCI) indicating a request for one or more aperiodic CSI reports 1826. Wireless device 2100 (or wireless device 2140) may transmit one or more aperiodic CSI reports 1826 in response to receiving command 1824.

[0373] FIG. 22 illustrates additional aspects of the embodiments of FIGs. 21A and 21 B according to the present disclosure. The aspects illustrated in FIG. 22 may be combined, or substituted for, the aspects illustrated in FIGs. 21 A and 21 B. FIG. 22 illustrates an example of the interactions between a MAC layer 2200 of a wireless device and a PHY layer 2220 of the wireless device in monitoring a radio link quality of one or more candidate reference signals for an event that may trigger CSI reporting as illustrated in FIGs. 19A, 19B, 19C, 21 A, and 21 B. MAC layer 2200 and PHYlayer 2220 maybe implemented in wireless device 1900, wireless device 1920, wireless device 1940, wireless device 2100, or wireless device 2140.

[0374] As illustrated at tO in FIG. 22, MAC layer 2200 monitors (e.g. , starts monitoring) for indications, from PHY layer 2220, that a reference signal satisfies an event for (UE-initiated) CSI reporting. MAC layer 2200 monitors (e.g., starts monitoring) for the indications based on PUCCH resources 2202 are configured in an active uplink BWP. This determination for monitoring is discussed above in connection with FIGs. 21A and 21 B.

[0375] MAC layer 2200 may monitor for indications of one or more reference signals from a list of reference signals. The list of reference signals may be configured by the one or more CSI reporting configuration parameters of one or more RRC messages 1902. The list of reference signals is illustrated as a reference signal resource set 2204 for UE- initiated CSI reporting in FIG. 22. Reference signal resource set 2204 comprises n reference signals (RS-1, RS-2, RS- 3, . . . , RS-N).

[0376] MAC layer 2200 may control (e.g., start, stop, and / or reset) one or more timers for detecting an event. Additionally or alternatively, MAC layer 2200 may control (e.g., initialize, start, stop, increment, and / or reset) one or more counters of a number of times the event is detected. The one or more timers and / or one or more counters may be configured by the one or more CSI reporting configuration parameters of one or more RRC messages 1902.

[0377] Each of the one or more timers and / or one or more counters may be associated with a (respective) reference signal among the n reference signals in reference signal resource set 2204. For example, the one or more counters may be referred to as trigger event indication (TEI) counters. FIG. 22 illustrates that MAC layer 2200 is configured with a TEI counter 2206 for RS-2, a TEI counter 2208 for RS-N, and a TEI counter 2210 for RS-1.

[0378] In response to activating the uplink BWP configured with the PUCCH resources, MAC layer 2200 may stop one or more timers for detecting the event in response to the one or more timers being running. MAC layer 2200 may reset the one or more timers in response to activating the uplink BWP configured with the PUCCH resources.

[0379] Additionally or alternatively, in response to activating the uplink BWP configured with the PUCCH resource, MAC layer 2200 may set a value of one or more counters of a number of times the event is detected to zero. For example, MAC layer 2200 may set a value of TEI counter 2206 for RS-2, TEI counter 2208 for RS-N, and TEI counter 2210 for RS-1 to zero in response to activating the uplink BWP.

[0380] In response to receiving an indication that one or more candidate reference signals satisfies the event, MAC layer 2200 may start one or more timer for detecting the event. In response to receiving an indication that one or more candidate reference signals satisfies the event, MAC layer 2200 may increment a counter of a number of times the event is detected in response to receiving an indication that a candidate reference signal satisfies the event.

[0381] At t1 in FIG. 22, for example, MAC layer 2200 receives an indication from PHY layer 2202. The indication is illustrated as an event instance for RS-2. The indication indicates that a radio link quality of RS-2 satisfies an event. Based on receiving the event instance for RS-2 from PHY layer 2202 (and the timer being running), MAC layer 2200 increments TEI counter 2206 for RS-2 to a value of 1 (i.e„ from 0 to 1).

[0382] MAC layer 2200 may continue to increment the one or more counters until one or more maximum count values. For example, at t2 in FIG. 22, MAC layer 2200 receives an event instance for RS-N from PHY layer 2202. Based on receiving the event instance for RS-N, MAC layer 2200 increments TEI counter 2208 for RS-N to a value of 1 (i.e., from O to 1). At t3 in FIG. 22, MAC layer 2200 receives an event instance for RS-1 from PHY layer 2202. Based on receiving the event instance for RS-1 , MAC layer 2200 increments TEI counter 2210 for RS-1 to a value of 1 (i.e., from 0 to 1). At t4 in FIG. 22, MAC layer 2200 receives an event instance for RS-N from PHY layer 2202. Based on receiving the event instance for RS-N, MAC layer 2200 increments TEI counter 2208 for RS-N to a value of that is equal to the maximum counter for TEI counter 2208.

[0383] In response to a counter reaching a maximum count value, MAC layer 2200 may detect that an event (triggerevent) has been detect. MAC layer 2202200 may transmit one or more indications to PHY layer 2220 indicating an ID of the reference signal (e.g., a candidate reference signal). For example, at t5 in FIG. 22, MAC layer 2200 detects (e.g., determines) an event based on TEI counter 2208 for RS-N reaching (being equal to) the maximum counter for TEI counter 2208. At t6, MAC layer 2200 sends an indication to PHY layer 2220. The indication indicates an ID of the reference signal (e.g., RS-N).

[0384] Based on receiving the indication form MAC layer 2200, PHY layer may transmit a PUCCH transmission for uplink resources (e.g., requesting or notifying) as described in connection with FIGs. 19A, 19B, 21A, and 21 B.

[0385] FIGs. 23A and 23B illustrate additional aspects of the embodiments of FIGs. 21 A, 21 B, 22 according to the present disclosure. The aspects illustrated in FIGs. 23A and 23B may be combined, or substituted for, the aspects illustrated in FIG. 21A, FIG. 21 B, and FIG. 22.

[0386] FIG. 23A illustrates an example of an embodiment in which CSI reporting is triggered by a wireless device 2300, and reported to a base station 2320, based on a parameter (e.g., a parameter that enables CSI reporting using preconfigured uplink resources). FIG. 23B illustrates an example of an embodiment in which CSI reporting is triggered by a wireless device 2340, and reported to a base station 2360, based on UE capability information.

[0387] The procedure, messages, and parameters illustrated in FIG. 23A and 23B may be the same as those discussed above in the first mode illustrated in FIGs. 19A and 21 A as well as the second mode illustrated in FIGs. 19B and 21B. The specific differences between the procedure, messages, and parameters for CSI reporting according to embodiments of the present disclosure will be discussed below. It should be understood that these features may be combined, substituted, or modified with any of the features discussed above or below.

[0388] As illustrated in FIG. 23A, wireless device 2300 may receive a parameter 2302 from base station 2320. The parameter 2302 may indicate whether (UE-initiated) CSI reporting based on wireless device 2300 detecting an event is enabled (e.g., activated or permitted). Parameter 2302 may be received via one or more RRC messages.

[0389] FIG. 23A illustrates that wireless device 2300 determines whether PUCCH resources 2304 are configured in an active uplink BWP and / or parameter 2302 indicates that (US-initiated) CSI reporting is enabled (e.g., activated or permitted) for wireless device 2300.

[0390] In response to PUCCH resources 2304 not being configured in the active uplink BWP and / or parameter 2302 indicating that (US-initiated) CSI reporting is disabled (e.g not enabled, not activated, or not permitted) for wireless device 2300, wireless device 2300 may not perform (or trigger) CSI reporting (e.g., ora procedure for CSI reporting) detected by wireless device 2300.

[0391] Based on determining that PUCCH resources 2304 are configured on the active uplink BWP and / or parameter 2302 indicates that (UE-initiated) CSI reporting is enabled (e.g., activated or permitted) for wireless device 2300, wireless device 2300 may perform a procedure 2306 for CSI reporting triggered by wireless device 2300.

[0392] As illustrated, wireless device 2300 detects that a candidate reference signal satisfies an event 2308 for (UE- initiated) CSI reporting. After detecting event 2308, wireless device 2300 transmits, via PUCCH resources 2304, a PUCCH transmission 2310 for uplink resources. PUCCH transmission 2310 may request uplink resources for transmitting (UE-initiated) CSI reporting based on detecting event 2308. Additionally or alternatively, PUCCH transmission 2310 may notify (base station 2320) that CSI reporting (based on detecting event 2308) is to be transmitted on (preconfigured) uplink resources. After transmitting PUCCH transmission 2310, wireless device 2300 transmits a CSI report 2312 to base station 2320.

[0393] By determining whether PUCCH resources 2304 are configured on an active uplink BWP and / or parameter 2302 indicates that (UE-initiated) CSI reporting is enabled (e.g., activated or permitted), wireless device 2300 may avoid wasting internal resources in performing (UE-initiated) CSI reporting. Furthermore, the additional or alternative use of parameter 2302 (compared to checking PUCCH resources 2304 alone), may provide additional benefits. For example, this aligns operations between wireless device 2300 and base station 2320 (in case the active uplink BWP is not commonly understood). In addition, this allows base station 2320 (the network) to control when wireless device 2300 performs UE-initiated CSI reporting. This may improve resource allocations within the network. In addition, this may improve network reliability with reduced signaling overhead and congestion (e.g., the network may already be aware that channel conditions are poor and / or the indicated TCI state should be updated).

[0394] FIG. 23B illustrates an example of an embodiment in which CSI reporting is triggered by wireless device 2340, and reported to base station 2360, based on UE capability information.

[0395] As illustrated, wireless device 2340 receives a UE capability inquiry 2314 from base station 2360. Wireless device 2340 may receive UE capability inquiry 23 in one or more RRC messages from base station 2314. UE capability inquiry 2313 may request UE capability information from wireless device 2340.

[0396] In response to receiving UE capability inquiry 2314, wireless device 2340 transmits UE capability information 2316 to base station 2360. UE capability information 2316 indicates that wireless device 2340 supports (UE-initiated) CSI reporting triggered by wireless device 2340 (e.g., as illustrated in FIGs. 19A, 19B, 19C, 21A, 21 B, and 22).

[0397] Additionally or alternatively, UE capability information 2316 indicates that wireless device 2340 supports (UE- initiated) CSI reporting triggered by wireless device 2340 based on preconfigured uplink resources. That is, UE capability information 2316 indicates that wireless device 2340 supports UE-initiated CSI reporting based on detectingan event and transmission of CSI reporting using preconfigured uplink resources (e.g., PUSCH resources configurable by one or more RRC messages) (e.g., the second mode as illustrated in FIGs. 19B, 19C, and 21 B).

[0398] In response to PUCCH resources 2318 not being configured in the active uplink BWP and / or UE capability information 2316 not being transmitted (to base station 2360), wireless device 2340 may not perform (or trigger) CSI reporting (e.g., or a procedure for CSI reporting) detected by wireless device 2340. Additionally or alternatively, wireless device 2340 may not perform (UE-initiated) CSI reporting (e.g., or a procedure for CSI reporting) based on UE capability information 2316 indicating that wireless device 2340 does not support UE-initiated CSI reporting. To indicate that wireless device 2340 does not support UE-initiated CSI reporting, a parameter indicating that wireless device 2340 supports UE-initiated CSI reporting may be absent in UE capability information 2316.

[0399] Based on determining that PUCCH resources 2318 are configured on the active uplink BWP and / or UE capability information 2316 indicates that (UE-initiated) CSI reporting is supported (e.g., and / or activated) for wireless device 2340, wireless device 2340 may perform a procedure 2322 for CSI reporting triggered by wireless device 2340.

[0400] As illustrated, wireless device 2340 detects that a candidate reference signal satisfies an event 2324 for (UE- initiated) CSI reporting. After detecting event 2324, wireless device 2340 transmits, via PUCCH resources 2318, a PUCCH transmission 2326 for uplink resources. PUCCH transmission 2326 may request uplink resources for transmitting (UE-initiated) CSI reporting based on detecting event 2324. Additionally or alternatively, PUCCH transmission 2326 may notify (base station 2340) that CSI reporting (based on detecting event 2324) is to be transmitted on (preconfigured) uplink resources. After transmitting PUCCH transmission 2326, wireless device 2340 transmits a CSI report 2328 to base station 2340.

[0401] By determining whether PUCCH resources 2318 are configured on an active uplink BWP and / or UE capability information 2316 (is sent to base station 2360 and / or indicates that wireless device 2340 supports UE-initiated CSI reporting), wireless device 2340 may avoid wasting internal resources in performing (UE-initiated) CSI reporting. Furthermore, network reliability may be increased as, e.g., base station 2360 may be able to (e.g., more closely) monitor and update (unified) TCI states of wireless device 2340 (and other wireless devices) based on the UE capability information.

[0402] In one or more embodiments of the present disclosure, the PUCCH transmission for the uplink resources (e.g., used to request the uplink resources for the UE-initiated CSI reporting and / or notify that the uplink resources are to be used for the UE-initiated CSI reporting) may be (embodied as) an SR (or a message that is SR-like, such as a bit indicating that uplink resources are requested and / or notifying preconfigured uplink resources are to be used for transmission). However, when SR transmissions for CSI reporting triggered by the wireless device are implemented using the existing technologies, this may result in the CSI reception problems at the network (e.g., as described above with respect to FIG. 20).

[0403] There is a need to enhance the SR procedure based on existing technologies when the SR procedure is used for the PUCCH transmission in (UE-initiated) CSI reporting triggered by the wireless device.

[0404] FIG. 24 illustrates a procedure 2400 for SRs triggered for CSI reporting initiated (or triggered) by the wireless device. The aspects of FIG. 24 may be combined with the embodiments described above in connection with the PUCCH transmissions for uplink resources (requesting or notifying) in FIGs. 19A, 19B, 19C, 21A, 21B, 22, 23A, 23B. Procedure 2400 may be implemented by wireless device 1900, wireless device 1920, wireless device 1940, wireless device 2100, wireless device 2140, wireless device 2300, or wireless device 2340 (as well as the MAC layer of any of these wireless devices or MAC layer 2200 of FIG. 22).

[0405] FIGs. 25A, 25B, 25C, and 26 illustrate additional aspects of procedure 2400 of FIG. 24. As illustrated in FIG. 24, procedure 2400 comprises a section 2410, a section 2420, a section 2430, and a section 2440. Section 2410, section 2420, section 2430, section 2440 comprise additional aspects of procedure 2400 that may not be (fully) illustrated in FIG. 24. FIG. 25A illustrates the aspects of section 2410, FIG. 25B illustrates the aspects of section 2420, and FIG. 25C illustrates the aspects of section 2430. FIG. 26 illustrates aspects of section 2440. Although FIG. 24 illustrates a combination comprising section 2410, section 2420, section 2430, section 2440, these sections may be performed individually or in combination with other procedures for the PUCCH transmissions for uplink resources.

[0406] A wireless device may use an SR for requesting uplink resources (e.g ., UL-SCH resources or PUSCH resources) for a new transmission. A MAC layer (e.g., a MAC entity) of the wireless device may be configured with zero, one, or more SR configurations. An SR configuration may comprise a set of PUCCH resources for SRs across different BWPs and cells. In some SR configurations, there may be (e.g., only) one PUCCH resource for SR configured per BWP. In other SR configurations, there may be, e.g., two PUCCH resources for SR configured per BWP. In addition, a dedicated SR configuration may be configured.

[0407] For an SR configuration for UE-initiated CSI reporting, the wireless device may receive one or more RRC messages. The one or more RRC messages may comprise one or more configuration parameters of the SR. The one or more configuration parameters of the SR may comprise an SR configuration. The one or more configuration parameters of the SR may indicate a PUCCH resource, from among PUCCH resources in an uplink BWP, is configured for the SR. The one or more configuration parameters of the SR may indicate a periodicity and offset of the SR.

[0408] The one or more configuration parameters of the SR may indicate a maximum count of a counter of a number of transmissions of the SR. The maximum count of the counter may be referred to as sr-TransMax. The counter of a number of transmissions of the SR may be referred to as an SR counter (e.g., SR_Counter). The maximum count may be configured per SR configuration (e.g., a (respective) maximum count for each SR configuration in one or more RRC messages).

[0409] Additionally or alternatively, the one or more configuration parameters may indicate a time duration of a timer for prohibiting transmissions of the SR after a transmission of the SR. The timer may be referred to as an SR prohibit timer. The SR prohibit timer may be configured per SR configuration (e.g., a (respective) timer for each SR configuration in one or more RRC messages).

[0410] When an SR is triggered, the wireless device determines (e.g., considers) the SR to be pending until the wireless device cancels the SR. Procedure 2400 illustrates an example of triggering SRs, managing SRs, and canceling SRs.

[0411] As illustrated in FIG. 24, procedure 2400 comprises a step 2402 of determining that uplink data is available and whether there are (any) available uplink resources for the uplink transmission. In response to uplink resources being available (yes for step 2402), procedure 2400 proceeds to a step 2404 of not triggering an SR for the available uplink resources. In response to uplink resources not being available (no for step 2402), procedure 2400 proceeds to a step 2406 of triggering an SR for the uplink resources.

[0412] Based on the procedure 2400 being triggered for an SR for UE-initiated CSI reporting, step 2402 of determining whether there are available uplink resources for the uplink transmission may proceed to triggering the SR in step 2406 (in the first mode and / or the second mode of CSI reporting as discussed above).

[0413] After triggering the SR in step 2406, procedure 2400 proceeds to a step 2408 of determining whether the (triggered) SR is canceled. As explained above, when an SR is triggered, the wireless device determines (e.g., considers) the SR to be pending until the wireless device cancels the SR. In response to the SR being canceled (yes for step 2408), procedure 2400 proceeds to a step 2412 of stopping the SR prohibit timer.

[0414] In response to the SR being not being canceled (e.g., being pending or remaining pending) (no for step 2408), procedure 2400 proceeds to a step 2414 of determining whether PUCCH resources are configured for the SR.

[0415] In response to determining that no PUCCH resources are configured for the SR (no in step 2414) (e.g., no PUCCH resources are valid and / or configured in the active uplink BWP), procedure 2400 proceeds to section 2410. Section 2410 comprises a step 2416 of initiating a RACH process (a random-access procedure) and a step 2418 of canceling the SR. FIG. 25A illustrates additional aspects of section 2410 for UE-initiated CSI reporting

[0416] As illustrated in FIG. 25A, in response to determining that no PUCCH resources are configured for the SR (e.g., on an active uplink BWP), procedure 2400 proceeds to a step 2500 of determining whether the SR is triggered for UE-initiated CSI reporting.

[0417] In response to the SR not being triggered for UE-initiated CSI reporting (no for step 2500), procedure 2400 proceeds to step 2416 of initiating a RACH process (a random-access procedure) and step 2418 of canceling the pending SR. In response to the SR being triggered for UE-initiated CSI reporting (yes for step 2500), procedure 2400 proceeds to a step 2502 of not initiating a RACH process (a random-access procedure). By making these determinations, the problems associated with performing a random-access procedure and (ultimately) transmitting UE- initiated CSI reporting via uplink resources from the random-access procedure may be avoided (as illustrated above (e.g., in FIG. 20).

[0418] Returning to FIG. 24, in response to determining that PUCCH resources are configured for the SR (yes in step 2414) (e.g., PUCCH resources are valid and / or configured in the active uplink BWP), procedure 2400 proceeds to a step 2416 of determining whether the PUCCH resources are in a measurement gap. The measurement gap may be a(time) duration in which the wireless device is (e.g. , RRC-configured to) to perform measurements (e.g., intrafrequency, inter-frequency, or inter-RAT measurements inside or outside of the active BWP and / or the current operating frequency). A wireless device may be configured with multiple measurement gaps and the measurement gap may include time for the wireless device to (re)tune RF components.

[0419] In response to determining that the PUCCH resources for the SR (or a PUCCH resource or an SR (transmission) opportunity) is in the measurement gap (yes in step 2422), procedure 2400 returns to step 2402 and does not transmit the SR in the measurement gap.

[0420] In response to determining that the PUCCH resources for the SR (or a PUCCH resource or an SR (transmission) opportunity) is not in the measurement gap (no in step 2422), procedure 2400 proceeds to a step 2424 of determining whether the SR prohibit timer, for the SR, is running.

[0421] In response to determining that the SR prohibit timer is running (yes in step 2424), procedure 2400 returns to step 2400 and does not transmit the SR (e g., does not retransmit the SR as an SR may have already been transmitted since the SR prohibit timer is running). In response to determining that the SR prohibit timer is not running (no in step 2424) (e.g., the SR prohibit timer for the SR has expired, has not been started, has been stopped, is set to zero, is set to infinity), procedure 2400 proceeds to a step 2426 of determining whether the SR prohibit timer is less than the maximum number of SR transmissions (e.g., sr-TransMax).

[0422] In response to determining that the SR prohibit timer is less than the maximum number of SR transmissions (e.g., sr-TransMax) (yes at step 2426), procedure 2400 proceeds to section 2420. Section 2420 comprises a step 2428 of incrementing an SR counter (e.g., increasing by the count by a value, such as one). FIG. 25B illustrates additional aspects of section 2420 for UE-initiated CSI reporting.

[0423] As illustrated in FIG. 25B, section 2420 comprises a step 2504 of determining whether the SR is triggered for UE-initiated CSI reporting. In response to determining that the SR is not triggered for UE-initiated CSI reporting (no in step 2504), procedure 2400 proceeds to step 2428 of incrementing the SR counter (e.g., incremented before the SR is transmitted). In response to determining that the SR is triggered for UE-initiated CSI reporting (yes in step 2504), procedure 2400 proceeds to a step 2506 of not incrementing the SR counter.

[0424] By not incrementing the SR counter, the wireless device may for example (simply) not increase a value of the SR counter (e.g., for transmission of the SR for UE-initiated CSI reporting). In another example, the wireless device may set the value of the SR counter to a value (e.g., another value such as zero, infinity, or the maximum value for the SR counter). This may enable the wireless device to prevent performing retransmissions of the SR (which may be one- shot for UE-initiated CSI reporting) and / or a random-access procedure for the SR (as discussed above).

[0425] Returning to FIG. 24, procedure 2400 proceeds from section 2420 to a step 2432 of sending the SR (e.g., instructing the PHY layer of the wireless device to transmit the SR). After sending the SR in step 24, procedure 2400 proceeds to section 2430. Section 2430 comprises a step 2434 of starting the SR prohibit timer. FIG. 25C illustrates additional aspects of section 2430 for UE-initiated CSI reporting.

[0426] As illustrated in FIG. 25C, section 2430 comprises a step 2508 of determining whether the SR is triggered for UE-initiated CSI reporting. In response to determining that the SR is not triggered for UE-initiated CSI reporting (no in step 2508), procedure 2400 proceeds to step 2434 of starting the SR prohibit timer. In response to determining that the SR is triggered for UE-initiated CSI reporting (yes in step 2508), procedure 2400 proceeds to a step 2510 of not starting the SR prohibit timer.

[0427] By not starting the SR prohibit timer, the wireless device may, for example, never start the SR prohibit timer, stop the SR prohibit timer if running, set the SR prohibit timer to a value (e.g., a value of zero, infinity, or any other value causing the SR prohibit timer to not run). This may enable the wireless device to prevent performing retransmissions of the SR (which may be one-shot for UE-initiated CSI reporting) and / or a random-access procedure for the SR (as discussed above).

[0428] Returning to FIG. 24, procedure 2400 returns to step 2402 and procedure 2400 may be run again (or be ended). Furthermore, returning to step 2426 of determining whether the SR counter is less than a maximum value for the SR count (sr-TransMax), the procedure 2400 may proceed to section 2440 in response to determining that the SR counter is not less than the maximum value (e.g ., the SR counter is equal to, is greater than, or has reached the maximum value of the SR counter).

[0429] Section 2440 comprises a step 2436 of releasing PUCCH resources of the wireless device (e.g., the MAC layer or MAC entity of the wireless device) (or notifying an RRC layer to release the PUCCH resources), a step 2438 of releasing SRS resources of the wireless device (e.g., the MAC layer or MAC entity of the wireless device) (or notifying an RRC layer to release the SRS resources), a step 2442 of clearing downlink assignments and / or uplink grants, and a step 2444 of initiating a RACH process (a random-access procedure). FIG. 26 illustrates additional aspects of section 2440 for UE-initiated CSI reporting.

[0430] As illustrated in FIG. 26, section 2440 comprises a step 2600 of determining whether the SR is triggered for UE-initiated CSI reporting. In response to determining that the SR is not triggered for UE-initiated CSI reporting (no in step 2600), procedure 2400 proceeds to step 2436 of releasing the PUCCH resources of the wireless device, step 2438 of releasing the SRS resources of the wireless device, step 2442 of clearing the downlink assignments and / or the uplink grants of the wireless device, and step 2444 of initiating a RACH process (a random-access procedure).

[0431] In response to determining that the SR is triggered for UE-initiated CSI reporting (yes in step 2600), procedure 2400 proceeds to at least one of the following: a step 2602 of not releasing PUCCH resources of the wireless device (e.g., the MAC layer or MAC entity of the wireless device) (or not notifying an RRC layer to release the PUCCH resources), a step 2604 of not releasing SRS resources of the wireless device (e g., the MAC layer or MAC entity of the wireless device) (or not notifying an RRC layer to release the SRS resources), a step 2606 of not clearing downlink assignments and / or uplink grants, and a step 2608 of not initiating a RACH process (a random-access procedure).

[0432] By not releasing (maintaining) PUCCH and / or SRS resources of the wireless device as well as not clearing downlink assignments and / or uplink grants, the UE-initiated CSI procedure may be able to continue when it wouldotherwise be ended. Additionally or alternatively, this may avoid releasing the PUCCH and / or SRS resources as well as clearing the downlink assignments and / or uplink grants when they are (or at least should be) valid and maintained. Furthermore, by not initiating a RACH process (a random-access procedure), this may enable the wireless device to prevent the wireless device from experiencing the random-access procedure for the SR (as discussed above).

[0433] Returning to FIG. 24, the procedure 2400 proceeds to a step 2446 of canceling the SR. As explained above, a wireless device may determine (e.g., consider) an SR to be pending until the wireless device cancels the SR. In UE- initiated CSI reporting, the SR for the PUCCH transmission may be transmitted as a one-shot transmission (e.g., one time).

[0434] FIG. 27 illustrates a process 2700 according to an embodiment of the present disclosure. The aspects of the process 2700 in FIG. 27 may be implemented by the wireless device discussed above in connection with FIGs. 17A, 17B, 18A, 18B, 18C, 19A, 19B, 19C, 21A, 21B, 22, 23A, 23B, 24, 25A, 25B, 25C, and 26.

[0435] As illustrated, process 2700 comprises a step 2702 of activating an uplink bandwidth part (BWP) configured with a physical uplink control channel (PUCCH) resource for channel state information (CSI) reporting triggered by the wireless device based on detecting an event.

[0436] Process 2700 further comprises a step 2704 of, in response to activating the uplink BWP configured with the PUCCH resource, performing detection of the event based on a radio link quality of a candidate reference signal.

[0437] Additional aspects of step 2702, step 2704, and process 2700 are discussed below.

[0438] In step 2702 or step 2704, the CSI reporting triggered by the wireless device may be a CSI reporting procedure; event-driven CSI reporting; an event-driven CSI reporting procedure; event-based CSI reporting; an eventbased CSI reporting procedure; user-equipment (UE) initiated CSI reporting; a UE-initiated CSI reporting procedure; UE-initiated beam reporting; ora UE-initiated beam reporting procedure.

[0439] Process 2700 may comprise an aspect of triggering a CSI report based on the wireless device detecting the event.

[0440] In step 2704 and / or any of the aspects discussed above, the performing detection of the event comprises monitoring for indications that the radio link quality of the candidate reference signal satisfies the event.

[0441] The monitoring for the indications may be monitoring, by a medium access control (MAC) layer of the wireless device, for indications from a physical (PHY) layer of the wireless device.

[0442] In step 2702, step 2704, and / or any of the aspects discussed above, triggering a CSI report may be based on detecting the indications.

[0443] In step 2702, step 2704, and / or any of the aspects discussed above, the event may be a comparison of the radio link quality of the candidate reference signal to a current reference signal of a transmission configuration indicator (TCI) state.

[0444] In step 2702, step 2704, and / or any of the aspects discussed above, the event may be that the radio link quality of the candidate reference signal is a threshold value better than a radio link quality of a reference signal of a TCI state

[0445] In step 2702, step 2704, and / or any of the aspects discussed above, process 2700 may further comprise receiving one or more radio resource control (RRC) messages comprising one or more configuration parameters of a plurality of TCI states, wherein the plurality of TCI states comprise the TCI state.

[0446] In step 2702, step 2704, and / or any of the aspects discussed above, process 2700 may further comprise receiving a control command indicating the TCI state.

[0447] In step 2702, step 2704, and / or any of the aspects discussed above, the radio link quality may be layer-1 reference signal received power (RSRP).

[0448] In step 2702, step 2704, and / or any of the aspects discussed above, the radio link quality may be signal to interference-and-noise (SINR).

[0449] In step 2702, step 2704, and / or any of the aspects discussed above, process 2700 may further comprise receiving one or more RRC messages indicating: physical uplink control channel (PUCCH) resources of bandwidth part (BWP) of a cell; the PUCCH resource, among the PUCCH resources, for CSI reporting triggered by the wireless device; and / or a list of candidate reference signals for CSI reporting triggered by the wireless device based on detecting the event.

[0450] In step 2702, step 2704, and / or any of the aspects discussed above, process 2700 may further comprise transmitting, via the PUCCH resource, a PUCCH transmission for uplink resources of a CSI report triggered by the wireless device; and / or transmitting, via the uplink resources, the CSI report indicating the candidate reference signal.

[0451] The PUCCH transmission may request the uplink resources for transmitting the CSI report.

[0452] In step 2702, step 2704, and / or any of the aspects discussed above, process 2700 may further comprise receiving downlink control information (DCI) indicating the uplink resources for transmitting the CSI report.

[0453] In any of the aspects discussed above, the PUCCH transmission may notify that the CSI report is to be transmitted via (or on) the uplink resources.

[0454] In any of the aspects discussed above, the PUCCH transmission may comprise a scheduling request (SR).

[0455] In any of the aspects discussed above, based on the SR being triggered for the CSI report triggered by the wireless device based on detecting the event, process 2700 may further comprise not incrementing a counter of a number of transmissions of the SR.

[0456] In any of the aspects discussed above, based on the SR being triggered for the CSI report triggered by the wireless device based on detecting the event, process 2700 may further comprise not starting a timer for prohibiting transmissions of the SR after a transmission of the SR.

[0457] In any of the aspects discussed above, based on the SR being triggered for the CSI report triggered by the wireless device based on detecting the event, process 2700 may further comprise not performing at least one of:releasing PUCCH or sounding reference signal (S RS) configuration; clearing configured downlink assignments; clearing configured uplink assignments; and / or initiating a random access process.

[0458] In step 2702, step 2704, and / or any of the aspects discussed above, the performing the detection of the event, in process 2700, may be based on a parameter indicating that CSI reporting, triggered by the wireless, is enabled or activated.

[0459] In step 2702, step 2704, and / or any of the aspects discussed above, process 2700 may further comprise transmitting one or more RRC messages indicating UE capability information of the wireless device.

[0460] In any of the aspects discussed above, the UE capability information indicates that the wireless device supports channel state information (CSI) reporting triggered by the wireless device based on detecting the event.

[0461] In any of the aspects discussed above, process 2700 may further comprise receiving one or more RRC messages comprising configuration parameters for aperiodic CSI reporting.

[0462] In any of the aspects discussed above, process 2700 may further comprise further comprising: receiving a downlink control information (DCI) indicating a request to transmit an aperiodic CSI report; and transmitting the aperiodic CSI report.

[0463] In any of the aspects discussed above, the transmitting the aperiodic CSI report is in response to receiving the DCI.

[0464] In any of the aspects discussed above, process 2700 may further comprise receiving one or more RRC messages comprising configuration parameters for semi-persistent CSI reporting.

[0465] In any of the aspects discussed above, process 2700 may further comprise receiving a medium access control (MAC) control element (CE) indicating activation of semi-persistent CSI reporting; and transmitting one or more semi- persistent CSI reports.

[0466] In any of the aspects discussed above, the transmitting the one or more semi-persistent CSI reports is in response to receiving the MAC CE indicating activation of the semi-persistent CSI reporting.

[0467] In any of the aspects discussed above, process 2700 may further comprise receiving MAC control element CE indicating deactivation of semi-persistent CSI reporting; and stopping transmission of one or more semi-persistent CSI reports.

[0468] In any of the aspects discussed above, the stopping transmitting the one or more semi-persistent CSI reports is in response to receiving the MAC CE indicating deactivation of the semi-persistent CSI reporting.

[0469] In any of the aspects discussed above, process 2700 may further comprise receiving one or more RRC messages comprising configuration parameters for periodic CSI reporting.

[0470] In any of the aspects discussed above, process 2700 may further comprise transmitting one or more periodic CSI reports.

[0471] In any of the aspects discussed above, transmitting the one or more periodic CSI reports is in response to receiving the one or more RRC messages.

[0472] An apparatus (e.g. , wireless device) may comprising one or more processors and memory storing instructions that, when executed by the one or more processors, may cause the apparatus to perform process 2700.

[0473] A (non-transitory) computer-readable medium may comprise instructions that, when executed by one or more processors of an apparatus (e.g., a wireless device), may cause the apparatus to perform process 2700.

[0474] A system may comprise a base station and an apparatus (e.g., wireless device) that may comprise one or more processors and memory storing instructions that, when executed by the one or more processors, may cause the apparatus to perform process 2700.

[0475] Additional aspects according to aspects of the present disclosure are provided below. The aspects of the example methods below may be combined, substituted, or otherwise added to any of the features discussed above.

[0476] Aspect 1. An example method comprising: receiving, by a wireless device, one or more radio resource control (RRC) messages indicating: physical uplink control channel (PUCCH) resources of bandwidth part (BWPs) of a cell; and a PUCCH resource, among the PUCCH resources, for channel state information (CSI) reports triggered by the wireless device based on an event being satisfied; activating a BWP, among the BWPs, as an active uplink BWP; based on activating the BWP configured with the PUCCH resource, monitoring for indications that a radio link quality of a candidate reference signal satisfies the event; and triggering a CSI report based on detecting the indications.

[0477] Aspect 2. An example method comprising: activating, by a wireless device, an uplink bandwidth part (BWP) configured with a physical uplink control channel (PUCCH) resource for channel state information (CSI) reporting triggered by the wireless device based on detecting an event; and in response to activating the uplink BWP configured with the PUCCH resource, performing detection of the event based on a radio link quality of a candidate reference signal.

[0478] Aspect 3. The example method of aspect 2, further comprising triggering a CSI report based on the wireless device detecting the event.

[0479] Aspect 4. The example method of any one of aspects 2 to 3, wherein the performing detection of the event comprises monitoring for indications that the radio link quality of the reference signal satisfies the event.

[0480] Aspect 5. The example method of aspect 4, further comprising triggering a CSI report based on detecting the indications.

[0481] Aspect 6. The example method of any one of aspects 2 to 5, further comprising triggering a CSI report based on detecting the event.

[0482] Aspect 7. The example method of any one of aspects 2 to 6, wherein the CSI reporting is: a CSI reporting procedure; event-driven CSI reporting; an event-driven CSI reporting procedure; event-based CSI reporting; an eventbased CSI reporting procedure; user-equipment (UE) initiated CSI reporting; a UE-initiated CSI reporting procedure; UE-initiated beam reporting; ora UE-initiated beam reporting procedure.

[0483] Aspect 8. The example method of any one of aspects 2 to 5, further comprising receiving one or more radio resource control (RRC) messages indicating the PUCCH resource for CSI reporting triggered by the wireless device based on the event.

[0484] Aspect 9. The example method of aspect 8, wherein the one or more RRC messages indicate: PUCCH resources of a plurality of uplink bandwidth part (BWPs); and the PUCCH resource, in the PUCCH resources, configured for CSI reports triggered by the wireless device.

[0485] Aspect 10. The example method of any one of aspects 2 to 9, further comprising transmitting, via the PUCCH resource, a PUCCH transmission for uplink resources of a CSI report triggered by the wireless device.

[0486] Aspect 11. The example method of aspect 10, wherein the PUCCH transmission requests the uplink resources for transmitting the CSI report.

[0487] Aspect 12. The example method of aspect 11 , further comprising receiving downlink control information (DCI) indicating the uplink resources for transmitting the CSI report.

[0488] Aspect 13. The example method of any one of aspects 10 to 11 , wherein the PUCCH transmission notifies that the CSI report is to be transmitted via the uplink resources.

[0489] Aspect 14. The example method of any one of aspects 10 to 13, wherein the PUCCH transmission comprises a scheduling request (SR).

[0490] Aspect 15. The example method of any one of aspects 10 to 14, wherein a PUCCH format of the PUCCH transmission is PUCCH format 0 or PUCCH format 1.

[0491] Aspect 16. The example method of any one of aspects 10 to 14, wherein the PUCCH transmission comprises uplink control information (UCI).

[0492] Aspect 17. The example method of any one of aspects 2 to 16, further comprising transmitting, via the uplink resources, a CSI report, of the candidate reference signal, triggered by the wireless device.

[0493] Aspect 18. The example method of aspect 17, wherein the CSI report indicates the candidate reference signal.

[0494] Aspect 19. The example method of any one of aspects 10 to 18, wherein the uplink resources are physical uplink shared channel (PUSCH) resources.

[0495] Aspect 20. The example method of any one of aspects 10 to 19, wherein the uplink resources are PUCCH resources.

[0496] Aspect 21. The example method of any one of aspects 10 to 20, wherein: the PUCCH transmission is a first PUCCH transmission; and the CSI report is transmitted in a second PUCCH transmission.

[0497] Aspect 22. The example method of any one of aspects 10 to 20, wherein: the PUCCH transmission is a first PUCCH transmission; and the CSI report is transmitted in a first PUSCH transmission.

[0498] Aspect 23. The example method of any one of aspects 2 to 22, wherein the event is a comparison of the radio link quality of the candidate reference signal to a reference signal of a transmission configuration indicator (TCI) state.

[0499] Aspect 24. The example method of any one of aspects 2 to 23, wherein the event is that the radio link quality of the candidate reference signal is a threshold value better than a radio link quality of a reference signal of a TCI state.

[0500] Aspect 25. The example method of any one of aspects 2 to 24, wherein the event is that the radio link quality of the candidate reference signal is better than a radio link quality of a reference signal of a TCI state by a threshold value.

[0501] Aspect 26. The example method of any one of aspects 2 to 25, wherein the event is that the radio link quality of the candidate reference signal is higher than a radio link quality of a reference signal of a TCI state by a threshold value.

[0502] Aspect 27. The example method of any one of aspects 2 to 26, wherein the event is that a reference signal received power (RS RP) value of the candidate reference signal is greater than an RSRP value of a reference signal of a TCI state plus a threshold RSRP value.

[0503] Aspect 28. The example method of any one of aspects 4 to 27, wherein the monitoring for the indications is monitoring, by a medium access control (MAC) layer of the wireless device, for indications from a physical (PHY) layer of the wireless device.

[0504] Aspect 29. The example method of any one of aspects 4 to 28, further comprising sending an indication instructing a PHY layer to transmit a CSI report of the candidate reference signal.

[0505] Aspect 30. The example method of any one of aspects 4 to 28, further comprising sending an indication to a PHY layer that an uplink grant is available based on receiving indications from the PHY layer that the event is satisfied.

[0506] Aspect 31. The example method of aspect 30, wherein the uplink grant is associated with the PUCCH resource.

[0507] Aspect 32. The example method of any one of aspects 30 to 31 , wherein the uplink grant is associated with PUSCH resources for transmitting the CSI report.

[0508] Aspect 33. The example method of any one of aspects 23 to 32, further comprising receiving one or more RRC messages comprising one or more configuration parameters of a plurality of TCI states, wherein the plurality of TCI states comprise the TCI state.

[0509] Aspect 34. The example method of aspect 33, wherein the one or configuration parameters, of the plurality of TCI states, comprises a list of TCI states.

[0510] Aspect 35. The example method of any one of aspects 33 to 34, wherein the one or configuration parameters, of the plurality of TCI states, comprise a list of joint-downlink TCI states.

[0511] Aspect 36. The example method of aspect 35, wherein the joint-downlink TCI states are applicable to downlink or both uplink and downlink.

[0512] Aspect 37. The example method of any one of aspects 33 to 36, wherein the one or configuration parameters, of the plurality of TCI states, comprise a list of uplink TCI states.

[0513] Aspect 38. The example method of any one of aspects 33 to 37, wherein the TCI state is from a list of jointdownlink TCI states.

[0514] Aspect 39. The example method of aspect 37, wherein the TCI state is from the list of uplink TCI states.

[0515] Aspect 40. The example method of any one of aspects 33 to 39, wherein each of the TCI states indicates a respective reference signal.

[0516] Aspect 41. The example method of any one of aspects 33 to 40, wherein each of the TCI states indicate a quasi co-location (QCL) type of the respective reference signal is for spatial domain parameters.

[0517] Aspect 42. The example method of aspect 41 , wherein the QCL type of the respective reference signal is QCL Type-D.

[0518] Aspect 43. The example method of any one of aspects 23 to 42, wherein the TCI state indicates a QCL type of the reference signal is for spatial domain parameters.

[0519] Aspect 44. The example method of aspect 43, wherein the QCL type of the reference signal is QCL Type-D.

[0520] Aspect 45. The example method of any one of aspects 23 to 44, further comprising receiving a control command indicating the TCI state.

[0521] Aspect 46. The example method of aspect 45, wherein the control command indicates the TCI state from among a plurality of TCI states configured by one or more RRC messages.

[0522] Aspect 47. The example method of any one of aspects 45 to 46, wherein the control command is a medium access control (MAC) control element (CE) indicating activation of the TCI state.

[0523] Aspect 48. The example method of aspect 47, wherein: the MAC CE indicates activation of a plurality of TCI states; and the plurality of activated TCI states comprises the TCI state.

[0524] Aspect 49. The example method of any one of aspects 47 to 48, further comprising receiving downlink control information (DCI) indicating the TCI state.

[0525] Aspect 50. The example method of any one of aspects 45 to 48, wherein the control command is a DCI indicating the TCI state.

[0526] Aspect 51. The example method of any one of aspects 49 to 50, wherein: the DCI comprises a TCI field; and a codepoint of the TCI field indicates the TCI state.

[0527] Aspect 52. The example method of aspect 51, wherein the codepoint of the TCI field indicates both the TCI states and a second TCI state.

[0528] Aspect 53. The example method of any one of aspects 49 to 52, wherein a DCI format of the DCI is DCI format 1_1 or DCI format 1_2.

[0529] Aspect 54. The example method of any one of aspects 49 to 53, wherein the DCI does not schedule a PUSCH transmission.

[0530] Aspect 55. The example method of any one of aspects 49 to 96, wherein the DCI does not comprise a field indicating to report CSI ora field indicating a CSI request.

[0531] Aspect 56. The example method of any one of aspects 2 to 55, further comprising receiving one or more RRC messages comprising one or more CSI reporting configuration parameters for the CSI reporting.

[0532] Aspect 57. The example method of aspect 56, wherein the one or more CSI reporting configuration parameters comprise a CSI resource parameter indicating a list of candidate reference signals.

[0533] Aspect 58. The example method of any one of aspects 2 to 57, further comprising receiving one or more RRC messages indicating a list of candidate reference signals for CSI reporting triggered by the wireless device based on detecting the event.

[0534] Aspect 59. The example method of any one of aspects 57 to 58, wherein the list of candidate reference signals comprises the candidate reference signal.

[0535] Aspect 60. The example method of any one of aspects 56 to 59, wherein the one or more CSI reporting configuration parameters comprise a report configuration type parameter.

[0536] Aspect 61. The example method of aspect 60, wherein the report configuration type parameter indicates that the CSI reporting is based on the wireless device detecting the event.

[0537] Aspect 62. The example method of any one of aspects 60 to 61 , wherein the report configuration type parameter is set to: event-triggered; or UE-initiated.

[0538] Aspect 63. The example method of any one of aspects 56 to 62, wherein the one or more CSI reporting configuration parameters indicate uplink resources for the CSI reporting.

[0539] Aspect 64. The example method of any one of aspects 56 to 63, wherein the one or more CSI reporting configuration parameters comprise a CSI resource configuration ID.

[0540] Aspect 65. The example method of aspect 64, wherein: the CSI resource configuration ID indicates a CSI resource configuration; and the CSI resource configuration indicates a list of one or more channel state information reference signals (CSI-RS) resource sets.

[0541] Aspect 66. The example method of aspect 65, wherein the list of one or more CSI-RS resource sets comprises one CSI-RS resource set based on a report configuration type parameter indicating that the CSI reporting is based on the wireless device detecting the event.

[0542] Aspect 67. The example method of aspect 66, wherein the list of one or more CSI-RS resource sets indicates the list of reference signals.

[0543] Aspect 68. The example method of any one of aspects 56 to 67, wherein the one or more CSI reporting configuration parameters comprise a parameter indicating that CSI reporting, triggered by the wireless device based on detecting the event, is enabled or activated.

[0544] Aspect 69. The example method of any one of aspects 2 to 68, further comprising receiving one or more RRC messages comprising a parameter indicating that CSI reporting, triggered by the wireless device based on detecting the event, is enabled or activated.

[0545] Aspect 70. The example method of aspects 68 to 69, wherein the parameter indicates that CSI reporting is enabled, or activated, for a cell.

[0546] Aspect 71. The example method of aspects 68 to 69, wherein the parameter indicates that CSI reporting is enabled, or activated, for an uplink BWP.

[0547] Aspect 72. The example method of any one of aspects 2 to 71, wherein the performing the detection of the event is based on a parameter indicating that the CSI reporting, triggered by the wireless device, is enabled or activated.

[0548] Aspect 73. The example method of any one of aspects 2 to 72, wherein the performing the detection of the event is based on a parameter being present that indicates CSI reporting, triggered by the wireless, is enabled or activated.

[0549] Aspect 74. The example method of any one of aspects 4 to 73, wherein the monitoring for the indications is based on a parameter indicating that CSI reporting is enabled or activated.

[0550] Aspect 75. The example method of any one of aspects 4 to 74, wherein the monitoring for the indications is based on a parameter indicating that CSI reporting is present.

[0551] Aspect 76. The example method of any one of aspects 2 to 75, further comprising transmitting one or more RRC messages indicating UE capability information of the wireless device, wherein the UE capability information indicates that the wireless device supports channel state information (CSI) reporting triggered by the wireless device based on detecting the event.

[0552] Aspect 77. The example method of aspect 76, wherein the UE capability information indicates that the wireless device supports CSI reporting based on preconfigured uplink resources.

[0553] Aspect 78. The example method of any one of aspects 75 to 77, further comprising receiving one or more RRC messages comprising a UE capability inquiry requesting UE capability information of the wireless device.

[0554] Aspect 79. The example method of any one of aspects 2 to 75, further comprising receiving one or more RRC messages indicating one or more timer values of one or more timers for detecting the event.

[0555] Aspect 80. The example method of any one of aspects 2 to 79, further comprising, in response to activating the uplink BWP configured with the PUCCH resources, stopping one or more timers for detecting the event in response to the one or more timers being running.

[0556] Aspect 81. The example method of any one of aspects 2 to 79, further comprising starting one or more timer for detecting the event in response to receiving an indication that one or more candidate reference signals satisfies the event.

[0557] Aspect 82. The example method of aspect 81 , wherein each of the one or more timers is associated with at least one candidate reference signal among the one or more candidate reference signals.

[0558] Aspect 83. The example method of any one of aspects 2 to 81 , further comprising receiving one or more maximum count values of one or more counters of a number of times the event is detected, for one or more candidatereference signals, in response to receiving an indication that the one or more candidate reference signals satisfy the event.

[0559] Aspect 84. The example method of any one of aspects 2 to 83, further comprising, in response to activating the uplink BWP configured with the PUCCH resource, setting a value of one or more counters of a number of times the event is detected to zero.

[0560] Aspect 85. The example method of any one of aspects 2 to 84, further comprising incrementing a counter of a number of times the event is detected in response to receiving an indication that a candidate reference signal satisfies the event.

[0561] Aspect 86. The example method of any one of aspects 84 to 85, wherein the counter is associated with the candidate reference signal.

[0562] Aspect 87. The example method of any one of aspects 14 to 86, further comprising receiving one or more RRC messages comprising one or more configuration parameters of the SR.

[0563] Aspect 88. The example method of aspect 87, wherein the one or more configuration parameters comprise an SR configuration for the SR.

[0564] Aspect 89. The example method of any one of aspects 87 to 88, wherein the one or more configuration parameters of the SR indicate a PUCCH resource, from among PUCCH resources in an uplink BWP, is configured for the SR.

[0565] Aspect 90. The example method of aspect 89, wherein the uplink BWP is the active uplink BWP.

[0566] Aspect 91. The example method of any one of aspects 87 to 90, wherein the one or more configuration parameters of the SR indicate a periodicity and offset of the SR.

[0567] Aspect 92. The example method of any one of aspects 87 to 91 , wherein the one or more configuration parameters of the SR indicate a maximum count of a counter of a number of transmissions of the SR.

[0568] Aspect 93. The example method of any one of aspects 14 to 92, further comprising not incrementing a counter of a number of transmissions of the SR.

[0569] Aspect 94. The example method of aspect 93, wherein the counter is not incremented based on the SR being triggered for a CSI report triggered by the wireless device based on detecting the event.

[0570] Aspect 95. The example method of any one of aspects 93 to 94, wherein the counter is not incremented while the counter is less than a maximum count of the counter.

[0571] Aspect 96. The example method of any one of aspects 93 to 95, wherein the counter is not incremented based on activating the uplink BWP configured with the PUCCH resource for the CSI reporting.

[0572] Aspect 97. The example method of any one of aspects 92 to 96, wherein a maximum count of the counter is sr-TransMax.

[0573] Aspect 98. The example method of any one of aspects 87 to 97, wherein the one or more configuration parameters indicate a time duration of a timer for prohibiting transmissions of the SR after a transmission of the SR.

[0574] Aspect 99. The example method of any one of aspects 14 to 98, further comprising not starting a timer for prohibiting transmissions of the SR after a transmission of the SR.

[0575] Aspect 100. The example method of aspect 99, wherein the timer is not started in response to the SR being triggered for the CSI reporting based on the wireless device detecting the event.

[0576] Aspect 101. The example method of any one of aspects 99 to 100, wherein the timer is not started in response to the SR being triggered for the CSI reporting based on activating the uplink BWP configured with the PUCCH resource for the CSI reporting.

[0577] Aspect 102. The example method of anyone of aspects 98 to 101, wherein the timer is an SR prohibit timer.

[0578] Aspect 103. The example method of any one of aspects 14 to 97, further comprising, based on the SR being triggered a CSI report triggered by the wireless device based on detecting the event, not performing at least one of: releasing PUCCH or sounding reference signal (SRS) configuration; clearing configured downlink assignments; clearing configured uplink assignments; or initiating a random-access process.

[0579] Aspect 104. The example method of aspect 103, wherein the not performing is based on activating the uplink BWP configured with the PUCCH resource for the CSI reporting.

[0580] Aspect 105. The example method of any one of aspects 3 to 104, wherein the CSI report comprises a radio link quality of the candidate reference signal.

[0581] Aspect 106. The example method of aspect 105, wherein the CSI report further comprises an ID of the candidate reference signal.

[0582] Aspect 107. The example method of any one of aspects 105 to 106, wherein the CSI report further comprises a radio link quality of a current reference signal of a TCI state.

[0583] Aspect 108. The example method of any one of aspects 3 to 107, wherein the CSI report further comprises a plurality of radio link qualities of a plurality of candidate reference signals.

[0584] Aspect 109. The example method of any one of aspects 105 to 108, wherein one or more radio link qualities in the CSI report are absolute values or differential values of the one or more radio link qualities.

[0585] Aspect 110. The example method of any one of aspects 3 to 109, wherein the radio link quality is a reference signal received power (RSRP).

[0586] Aspect 111. The example method of aspect 110, wherein the RSRP is a layer-1 RSRP (L1-RSRP).

[0587] Aspect 112. The example method of any one of aspects 3 to 111, wherein the radio link quality is signal to interference-and-noise ratio (SINR).

[0588] Aspect 113. The example method of any one of aspects 3 to 112, wherein the CSI report comprises a number of radio link qualities of reference signals.

[0589] Aspect 114. The example method of aspect 113, wherein the number is: one; greater than one; or less than, or equal to, a maximum number of radio link qualities for the CSI reporting.

[0590] Aspect 115. The example method of any one of aspects 87 to 114, further comprising receiving one or more RRC messages comprising a value of a maximum number of radio link qualities for the CSI reporting in a CSI report format.

[0591] Aspect 116. The example method of any one of aspects 3 to 115, wherein the event is a first event among a plurality of events.

[0592] Aspect 117. The example method of aspect 116, wherein the plurality of events further comprise at least one of: a second event in which a radio link quality of a candidate reference signal is worse than a threshold; a third event in which a radio link quality of a candidate reference signal is better than a threshold; a fourth event in which a radio link quality of a reference signal, of a TCI state indicated by a control command, is worse than a first threshold and a radio link quality of at least one candidate reference signal is better than a second threshold; a fifth event in which a difference between a radio link quality of a reference signal, of a TCI state indicated by a control command, and a radio link quality of at least one candidate reference signal is lower than a threshold; a sixth event in which a radio link quality of the reference signal, of the T Cl state indicated by the control command, is not among a number of candidate reference signals with a highest radio link qualities; a seventh event in which a radio link quality of at least one candidate reference signal is a threshold value better than a reference signal of a TCI state, indicated by a control command, with a worst radio link quality among reference signals of TCI states indicated by the control command; an eighth event in which a radio link quality of at least one candidate reference signal is a threshold value better than a reference signal of a TCI state, indicated by a control command, with a highest radio link quality among reference signals of TCI states indicated by the control command; a ninth event in which a radio link quality of a number of candidate reference signals become a threshold value better than the reference signal of the TCI state indicated by the control command; or a tenth event in which a radio link quality of at least one candidate reference signal becomes a threshold value better than a reference signal configured by one or more RRC messages.

[0593] Aspect 118. The example method of aspect 117, wherein each of the plurality of events is associated with an event identifier (ID).

[0594] Aspect 119. The example method of aspect 118, wherein: a first value of the event ID indicates the first event is satisfied; a second value of the event ID indicates the second event is satisfied; a third value of the event ID indicates the third event is satisfied; a fourth value of the event ID indicates the fourth event is satisfied; a fifth value of the event ID indicates the fifth event is satisfied; a sixth value of the event ID indicates the sixth event is satisfied; a seventh value of the event ID indicates the seventh event is satisfied; a eighth value of the event ID indicates the eighth event is satisfied; a ninth value of the event ID indicates the ninth event is satisfied; and / or a tenth value of the event ID indicates the tenth event is satisfied.

[0595] Aspect 120. The example method of any one of aspects 116 to 119, further comprising receiving RRC messages comprising a list of at least one of: the plurality of events; or event IDs of the plurality of events.

[0596] Aspect 121. The example method of any one of aspects 10 to 120, wherein the PUCCH transmission comprises one or more event IDs among event IDs of a plurality of events.

[0597] Aspect 122. The example method of any one of aspects 10 to 120, wherein the CSI report comprises one or more event IDs among event IDs of a plurality of events.

[0598] Aspect 123. The example method of aspect 121, wherein the one or more event I Ds are each associated with a respective reference signal.

[0599] Aspect 124. The example method of any one of aspects 118 to 123, wherein the CS I report comprises one or more event IDs among event IDs of the plurality of events.

[0600] Aspect 125. The example method of aspect 124, wherein the one or more event I Ds are each associated with a respective reference signal.

[0601] Aspect 126. The example method of any one of aspects 3 to 125, further comprising receiving one or more RRC messages indicating a threshold value for detecting the event.

[0602] Aspect 127. The example method of any one of aspects 3 to 125, wherein a threshold value, for detecting the event, is a preconfigured value in the wireless device.

[0603] Aspect 128. The example method of any one of aspects 126 to 127, wherein the threshold value is an RSRP value or an RSRP offset.

[0604] Aspect 129. The example method of aspect 126 to 127, wherein the threshold value is an SNIR value or an SNIR offset.

[0605] Aspect 130. The example method of any one of aspects 2 to 129, further comprising receiving one or more RRC messages comprising configuration parameters for aperiodic CSI reporting.

[0606] Aspect 131. The example method of any one of aspects 2 to 130, further comprising: receiving a downlink control information (DCI) indicating a request to transmit an aperiodic CSI report; and transmitting the aperiodic CSI report.

[0607] Aspect 132. The example method of aspect 131, wherein the transmitting the aperiodic CSI report is in response to receiving the DCI.

[0608] Aspect 133. The example method of any one of aspects 2 to 132, further comprising receiving one or more RRC messages comprising configuration parameters for semi-persistent CSI reporting.

[0609] Aspect 134. The example method of any one of aspects 2 to 133, further comprising: receiving a medium access control (MAC) control element (CE) indicating activation of semi-persistent CSI reporting; and transmitting one or more semi-persistent CSI reports.

[0610] Aspect 135. The example method of aspect 134, wherein the transmitting the one or more semi-persistent CSI reports is in response to receiving the MAC CE indicating activation of the semi-persistent CSI reporting.

[0611] Aspect 136. The example method of any one of aspects 134 to 135, further comprising: receiving MAC control element CE indicating deactivation of semi-persistent CSI reporting; and stopping transmission of one or more semi- persistent CSI reports.

[0612] Aspect 137. The example method of aspect 136, wherein the stopping transmitting the one or more semi- persistent CSI reports is in response to receiving the MAC CE indicating deactivation of the semi-persistent CSI reporting.

[0613] Aspect 138. The example method of any one of aspects 2 to 136, further comprising receiving one or more RRC messages comprising configuration parameters for periodic CSI reporting.

[0614] Aspect 139. The example method of aspect 138, further comprising transmitting one or more periodic CSI reports.

[0615] Aspect 140. The example method of aspect 139, wherein the transmitting the one or more periodic CSI reports is in response to receiving the one or more RRC messages.

[0616] Aspect 141. A wireless device comprising: one or more processors; and memory storing instructions that, when execute...

Claims

CLAIMSWhat is claimed is:

1. A method comprising: receiving, by a wireless device, one or more radio resource control (RRC) messages comprising one or more configuration parameters for user-equipment (UE)-initiated channel state information (CSI) reporting, wherein the one or more configuration parameters indicate one or more physical uplink control channel (PUCCH) resources for the UE-initiated CSI reporting; activating an uplink bandwidth part (BWP) of a cell; based on whether the one or more configuration parameters indicate, for the active uplink BWP, a PUCCH resource for the UE-initiated CSI reporting, determining to measure a first reference signal forevent instances of the UE-initiated CSI reporting; and based on a number of the event instances being equal to, or greater than, a value, transmitting, via the PUCCH resource, a PUCCH transmission for the UE-initiated CSI reporting.

2. A method comprising: receiving, by a wireless device, one or more radio resource control (RRC) messages comprising one or more configuration parameters for user-equipment (UE)-initiated channel state information (CSI) reporting; based on whether the one or more configuration parameters indicate, for an active uplink bandwidth part (BWP), a physical uplink control channel (PUCCH) resource for the UE-initiated CSI reporting, determining to measure a reference signal for event instances of the UE-initiated CSI reporting; and based on a number of the event instances being equal to, or greater than, a value, transmitting, via the PUCCH resource, a PUCCH transmission fora UE-initiated CSI report.

3. The method of claim 2, further comprising: measuring the reference signal for the event instances based on determining that the one or more configuration parameters indicating the PUCCH resource for the active uplink BWP; and / or not measuring the reference signal for the event instances based on determining that the one or more configuration parameters do not indicate the PUCCH resource for the active uplink BWP.

4. The method of any one of claims 2 to 3, wherein the one or more configuration parameters indicate the PUCCH resources.

5. The method of any one of claims 2 to 4, further comprising activating an uplink BWP of a cell as the active uplink BWP.

6. The method of any one of claims 2 to 5, wherein: the one or more RRC messages indicate one or more PUCCH resources for the UE-initiated CSI reporting; and the one or more PUCCH resources comprise the PUCCH resource.

7. The method of any one of claims 2 to 6, wherein the one or more RRC messages indicate a list of reference signals for the UE-initiated CSI reporting.

8. The method of claim 7, wherein the list of reference signals comprise the reference signal9. The method of any one of claims 2 to 8, wherein the event instances are based on at least one of: a radio link quality of a reference signal among a list of reference signals for UE-initiated CSI reporting being a first threshold value greater than a radio link quality of a reference signal of a TCI state; the radio link quality of the reference signal is lower than a second threshold value; the radio link quality of the reference signal is a third threshold value greater than a reference signal of a TCI state, indicated by a control command, with a highest radio link quality among reference signals of TCI states indicated by the control command.

10. The method of any one of claims 2 to 9, wherein the PUCCH transmission: requests a dynamic grant for the UE-initiated CSI report; or notifies that the UE-initiated CSI report is to be transmitted on uplink resources of a configured uplink grant.

11. The method of any one of claims 2 to 10, wherein a PUCCH format of the PUCCH transmission is PUCCH format O or PUCCH format 1.

12. The method of any one of claims 2 to 11 , further comprising transmitting a physical uplink shared channel (PUSCH) transmission carrying the UE-initiated CSI report.

13. The method of any one of claims 2 to 12, wherein the one or more configuration parameters comprise a parameter indicating a mode for the UE-initiated CSI reporting.

14. The method of claim 13, wherein: a first value of the parameter indicates that the mode is a first mode in which UE-initiated CSI reports are transmitted via uplink resources indicated by dynamic uplink grants; and a second value of the parameter indicates that the mode is a second mode in which the UE-initiated CSI reports are transmitted via uplink resources indicated by a configured uplink grant.

15. The method of claim 14, wherein a value of the parameter is set to the first value or the second value.

16. The method of any one of claims 14 to 15, wherein: the first mode is Mode A; and the second mode is Mode B.

17. The method of any one of claims 2 to 16, further comprising receiving a control command indicating a TCI state, wherein the TCI state indicates a reference signal.

18. The method of claim 17, wherein one or more RRC messages comprises a list of TCI states, wherein the list of TCI states comprises the TCI.

19. The method of claim 18, wherein the list of TCI states is: a list of uplink TCI states; ora listof joint-downlink TCI states.

20. The method of any one of claims 2 to 19, wherein the one or more configuration parameters comprise a parameter indicating the value of an event counter.

21. The method of any one of claims 2 to 20, wherein the value is a maximum count value of the number of event instances.

22. The method of any one of claims 2 to 21 , further comprising setting a respective event counter, associated with each reference signal in a list of reference signals for UE-initiated CSI reporting, to zero based on the one or more configuration parameters indicating, for the active uplink BWP, the PUCCH resource used for the UE-initiated CSI reporting.

23. The method of any one of claims 2 to 22, wherein the one or more configuration parameters indicate an event detection timer for the UE-initiated CSI reporting.

24. The method of claim 23, further comprising stopping the event detection timer based on the one or more configuration parameters indicating, for the active uplink BWP, the PUCCH resource.

25. The method of any one of claims 2 to 24, further comprising: activating a second uplink BWP; and based on the one or more configuration parameters not indicating, for the second active uplink BWP, a PUCCH resource used for the CSI reporting triggered by the wireless device, determining not to measure the reference signal for the event instances.

26. The method of any one of claims 2 to 25, further comprising monitoring, by a medium access control (MAC) layer of the wireless device, for the event from a physical layer (PHY) layer of the wireless device.

27. A method comprising: receiving, by a wireless device, one or more radio resource control (RRC) messages comprising one or more configuration parameters for user-equipment (UE)-initiated channel state information (CSI) reporting, wherein the one or more configuration parameters indicate one or more physical uplink control channel (PUCCH) resources for the UE-initiated CSI reporting; activating an uplink bandwidth part (BWP) of a cell; based on whether an uplink bandwidth part (BWP) comprising a physical uplink control channel (PUCCH) resource for the UE-initiated CSI reporting is active, determining to measure a first reference signal for event instances of the UE-initiated CSI reporting; and based on a number of the event instances being equal to, or greater than, a value, transmitting, via the PUCCH resource, a PUCCH transmission for the UE-initiated CSI reporting.

28. A method comprising: receiving, by a wireless device, one or more radio resource control (RRC) messages comprising one or more configuration parameters for user-equipment (UE)-initiated channel state information (CSI) reporting;based on whether an uplink bandwidth part (BWP) comprising a physical uplink control channel (PUCCH) resource for the UE-initiated CSI reporting is active, determining to measure a reference signal for event instances of the UE-initiated CSI reporting; and based on a number of the event instances being equal to, or greater than, a value, transmitting, via the PUCCH resource, a PUCCH transmission fora UE-initiated CSI report.

29. The method of claim 28, further comprising: measuring the reference signal for the event instances based on determining that the uplink BWP comprising the PUCCH resource is active; and / or not measuring the reference signal for the event instances based on determining that the uplink BWP comprising the PUCCH resource is not active.

30. The method of any one of claims 28 to 29, wherein the one or more configuration parameters indicate the PUCCH resources.

31. The method of any one of claims 28 to 30, further comprising activating the uplink BWP of a cell as an active uplink BWP.

32. The method of any one of claims 28 to 31, wherein: the one or more RRC messages indicate one or more PUCCH resources for the UE-initiated CSI reporting; and the one or more PUCCH resources comprise the PUCCH resource.

33. The method of any one of claims 28 to 32, wherein the one or more RRC messages indicate a list of reference signals for the UE-initiated CSI reporting.

34. The method of claim 33, wherein the list of reference signals comprise the reference signal.

35. The method of any one of claims 28 to 34, wherein the event instances are based on at least one of: a radio link quality of a reference signal among a list of reference signals for UE-initiated CSI reporting being a first threshold value greater than a radio link quality of a reference signal of a TCI state; the radio link quality of the reference signal is lower than a second threshold value; the radio link quality of the reference signal is a third threshold value greater than a reference signal of a TCI state, indicated by a control command, with a highest radio link quality among reference signals of TCI states indicated by the control command.

36. The method of any one of claims 28 to 35, wherein the PUCCH transmission: requests a dynamic grant for the UE-initiated CSI report; or notifies that the UE-initiated CSI report is to be transmitted on uplink resources of a configured uplink grant.

37. The method of any one of claims 28 to 36, wherein a PUCCH format of the PUCCH transmission is PUCCH format 0 or PUCCH format 1.

38. The method of any one of claims 28 to 37, further comprising transmitting a physical uplink shared channel (PUSCH) transmission carrying the UE-initiated CSI report.

39. The method of any one of claims 28 to 38, wherein the one or more configuration parameters comprise a parameter indicating a mode for the UE-initiated CSI reporting.

40. The method of claim 39, wherein: a first value of the parameter indicates that the mode is a first mode in which UE-initiated CSI reports are transmitted via uplink resources indicated by dynamic uplink grants; and a second value of the parameter indicates that the mode is a second mode in which the UE-initiated CSI reports are transmitted via uplink resources indicated by a configured uplink grant.

41. The method of claim 40, wherein a value of the parameter is set to the first value or the second value.

42. The method of any one of claims 40 to 41, wherein: the first mode is Mode A; and the second mode is Mode B.

43. The method of any one of claims 28 to 42, further comprising receiving a control command indicating a TCI state, wherein the TCI state indicates a reference signal.

44. The method of claim 43, wherein one or more RRC messages comprises a list of TCI states, wherein the list of TCI states comprises the TCI.

45. The method of claim 44, wherein the list of TCI states is: a list of uplink TCI states; or a listof joint-downlink TCI states.

46. The method of any one of claims 28 to 45, wherein the one or more configuration parameters comprise a parameter indicating the value of an event counter.

47. The method of any one of claims 28 to 46, wherein the value is a maximum count value of the number of event instances.

48. The method of any one of claims 28 to 47, further comprising setting a respective event counter, associated with each reference signal in a list of reference signals for UE-initiated CSI reporting, to zero based on the one or more configuration parameters indicating, for the active uplink BWP, the PUCCH resource used for the UE- initiated CSI reporting.

49. The method of any one of claims 28 to 48, wherein the one or more configuration parameters indicate an event detection timer for the UE-initiated CSI reporting.

50. The method of claim 49, further comprising stopping the event detection timer based on the the uplink BWP not being active.

51. The method of any one of claims 28 to 50, further comprising monitoring, by a medium access control (MAC) layer of the wireless device, for the event instances from a physical layer (PHY) layer of the wireless device.

52. An apparatus comprising: one or more processors; andmemory storing instructions that, when executed by the one or more processors, cause the apparatus to perform the method of any one of claims 1 to 51.

53. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors of an apparatus, cause the apparatus to perform the method of any one of claims 1 to 51.

Images