Uplink control channel configuration for channel state information reporting

Abstract

A wireless device transmits, via a physical uplink control channel (PUCCH) resource, a PUCCH transmission with a user equipment (UE) initiated report indicator (UEIRI) for UE-initiated channel state information (CSI) reporting. The UEIRI notifies that a PUSCH transmission of a Type 1 configured uplink grant is to be used to carry a CSI report. The UE transmits, in a first available transmission occasion of the Type 1 configured uplink grant, the CSI report. The first available transmission occasion occurs a number of symbols after an end of the PUCCH transmission, and the number of symbols is based on a subcarrier spacing of the PUCCH resource.

Description

Docket No.: 25-1025PCTTITLEUplink Control Channel Configuration for Channel State Information Reporting CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 747,513, filed January 21 , 2025, 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. 1 B 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. 11 A 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.Docket No.: 25-1025PCT

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

[0019] FIG. 14A illustrates an example of CORESET configurations for a 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 illustrates an example signal flow diagram illustrating aspects according to the present disclosure.

[0027] FIG. 21 illustrates an example signal flow diagram illustrating aspects according to the present disclosure.

[0028] FIG. 22 illustrates an example CSI report configuration illustrating aspects according to the present disclosure.DETAILED DESCRIPTION

[0029] 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 otherDocket No.: 25-1025PCTthan that shown. For example, the actions listed in any flowchart may be re-ordered or only optionally used in some embodiments.

[0030] 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 the above, 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.

[0031] 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 capability(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 or a 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.

[0032] 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.Docket No.: 25-1025PCT

[0033] 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 / using” 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.

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

[0035] In this disclosure, parameters (or equally called, fields, or Information elements: IBs) 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.

[0036] 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 justDocket No.: 25-1025PCTone of the three possible features, with any two of the three possible features or with three of the three possible features.

[0037] 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) or a 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 LabVIEWMathScript. 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, application-specific 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.

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

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

[0040] 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 asDocket No.: 25-1025PCTthe 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.

[0041] 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 may be a telephone, smart phone, 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.

[0042] 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 (gNB, 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 gNB Central Unit (gNB-CU) and at least one a gNB Distributed Unit (gNB-DU).

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

[0044] 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. ADocket No.: 25-1025PCTrelay 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.

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

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

[0047] FIG. 1B 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. 1 B, 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.

[0048] 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 offerDocket No.: 25-1025PCTservices 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).

[0049] As illustrated in FIG. 1 B, 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. 1 B 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- / inter-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.

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

[0051] The 5G-CN 152 may include one or more additional network functions that are not shown in FIG. 1B for the sake of clarity. For example, the 5G-CN 152 may include one or more of a Session Management Function (SMF), an NR 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).

[0052] 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 gNBs, illustrated as gNB 160A and gNB 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 forDocket No.: 25-1025PCTcommunicating 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.

[0053] 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. 1 B, gNB 160A may be 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. 1B 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.

[0054] 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 may be 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.

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

[0056] 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 coreDocket No.: 25-1025PCTnetwork 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 gNB 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.

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

[0058] 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 may be 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.

[0059] 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 (MAC) layers (MACs) 212 and 222 (also referred to as media access control layers), radio link control (RLC) layers (RLCs) 213 and 223, packet data convergence protocol (PDCP) layers (PDCPs) 214 and 224, and service data application protocol (SDAP) layers (SDAPs) 215 and 225. Together, these four protocols may make up layer 2, or the data link layer, of the OSI model.

[0060] 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.Docket No.: 25-1025PCT

[0061] 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-gNB 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.

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

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

[0064] 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 PHYs 211 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 gNB 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 MACs 212 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 numerologyDocket No.: 25-1025PCTand / 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.

[0065] 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 211 and 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.

[0066] 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 gNB 220. An uplink data flow through the NR user plane protocol stack may be similar to the downlink data flow depicted in FIG. 4A.

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

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

[0069] 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 logicalDocket No.: 25-1025PCTchannel 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.

[0070] 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 may be 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.

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

[0072] 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:

[0073] - 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;

[0074] - 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;Docket No.: 25-1025PCT

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

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

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

[0078] 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:

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

[0080] - a broadcast channel (BCH) for carrying the M IB from the BCCH;

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

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

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

[0084] 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 the control 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:

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

[0086] - 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;

[0087] - 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;

[0088] - 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;

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

[0090] -- a physical random access channel (PRACH) for random access.Docket No.: 25-1025PCT

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

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

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

[0094] 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 be transmitted 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 ofDocket No.: 25-1025PCTestablishing 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.

[0095] 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. 2A and 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., RRCJDONNECTED), RRC idle 604 (e.g., RRCJDLE), and RRC inactive 606 (e.g., RRCJNACTIVE).

[0096] 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. 1 B, the gNB 220 depicted in FIG. 2A and 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.

[0097] 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 may be managed by the UE through a procedure known as cell reselection. The RRC state may transition from RRC idle 604 to RRC connected 602 through a connection establishment procedure 612, which may involve a random access procedure as discussed in greater detail below.

[0098] 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, theDocket No.: 25-1025PCTUE 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.

[0099] 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).

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

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

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

[0103] A gNB, such as gNBs 160 in FIG. 1B, may be 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 anDocket No.: 25-1025PCTF1 interface. The gNB-CU may comprise the RRC, the PDCP, and the SDAP. A gNB-DU may comprise the RLC, the MAC, and the PHY.

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

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

[0106] 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 / 0.59 ps; and 240 kHz / 0.29 ps.Docket No.: 25-1025PCT

[0107] 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 subcarrier spacing of 240 kHz is not shown in FIG. 7 for ease of illustration). A subframe in NR may be used as a numerology-independent 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.

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

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

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

[0111] 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.Docket No.: 25-1025PCT

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

[0113] 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, a base 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.

[0114] 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).

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

[0116] A base station may semi-statically 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.

[0117] 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 theDocket No.: 25-1025PCTBWP inactivity timer expires, the UE may switch from the active downlink BWP to the default downlink BWP.

[0118] 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).

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

[0120] 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 MHz and 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.

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

[0122] 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 beDocket No.: 25-1025PCTreferred to as component carriers (CCs). When CA is used, there are a number of serving cells for the U E, one for a CC. The CCs may have three configurations in the frequency domain.

[0123] 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).

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

[0125] 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 RRC Connection 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).

[0126] 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 may be 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).

[0127] 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 selfscheduling. The DCI for the cell may be transmitted on another cell, which is known as cross-carrierDocket No.: 25-1025PCTscheduling. 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.

[0128] 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, UCI 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 UCI 1071, UCI 1072, and UC1 1073, may be 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.

[0129] 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, the disclosure 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.

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

[0131] 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 inDocket No.: 25-1025PCTFIG. 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) / 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.

[0132] FIG. 11 A 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.

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

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

[0135] 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 ofDocket No.: 25-1025PCTthe 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.

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

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

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

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

[0140] 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 measure the 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 moreDocket No.: 25-1025PCTdownlink 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.

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

[0142] 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 may be 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.

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

[0144] 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-MIMO, 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 aDocket No.: 25-1025PCTDMRS 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.

[0145] 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).

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

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

[0148] 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 may be 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.,Docket No.: 25-1025PCTmaximum 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.

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

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

[0151] 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 resourceDocket No.: 25-1025PCTsets. 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 RUSCH 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.

[0152] 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, mini-slot, 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.

[0153] 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 co-located (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.

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

[0155] FIG. 11 B 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-RSDocket No.: 25-1025PCTports, 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, qd-csi-rs-configNZPid), and / or other radio resource parameters.

[0156] The three beams illustrated in FIG. 11 B may be configured for a UE in a UE-specific configuration. Three beams are illustrated in FIG. 11B (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 (FDM), 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.

[0157] CSI-RSs such as those illustrated in FIG 11 B (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.Docket No.: 25-1025PCT

[0158] 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 (PM I), a channel quality indicator (CQI), and / or a rank indicator (Rl).

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

[0160] FIG. 12B illustrates examples of three uplink beam management procedures: U1, 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 of one or more UE Tx beams and / or base station Rx beams (shown as ovals in the top row and bottom row, respectively, of U 1 ). 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.

[0161] 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) basedDocket No.: 25-1025PCTon 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).

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

[0163] 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 RRCJDLE state and / or an RRCJNACTIVE 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.

[0164] 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 3 1313, 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).

[0165] 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:Docket No.: 25-1025PCTgeneral parameters for one or more random access procedures (e.g., RACH-configGeneral),’ cellspecific parameters (e.g., RACH-ConfigCommon); and / or dedicated parameters (e.g., RACH- configDedicated). The base station may broadcast or 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 RRCJNACTIVE 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 3 1313. Based on the one or more RACH parameters, the UE may determine a reception timing and a downlink channel for receiving the Msg 2 1312 and the Msg 4 1314.

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

[0167] 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).

[0168] 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 3 1313. The UE may measure an RSRP of one or more reference signals (e.g., SSBsDocket No.: 25-1025PCTand / 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.

[0169] 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-OccasionList) may indicate an association between the PRACH occasions and the one or more reference signals.

[0170] 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_TRANSMISSION_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).

[0171] 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 andDocket No.: 25-1025PCTindicated on a PDCCH using a random access 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 3 1313, and / or a 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:

[0172] RA-RNTI= 1 + sjd + 14 x tjd + 14 x 80 x fjd + 14 x 80 x 8 x ul_carrier_id, where sjd may be 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).

[0173] The UE may transmit the Msg 3 1313 in response to a successful reception of the Msg 2 1312 (e.g., using resources identified in the Msg 2 1312). 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 3 1313 and the Msg 4 1314) 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 3 1313 (e.g., a C-RNTI if assigned, a TC-RNTI included in the Msg 2 1312, and / or any other suitable identifier).

[0174] The Msg 4 1314 may be received after or in response to the transmitting of the Msg 3 1313. If a C-RNTI was included in the Msg 3 1313, 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 3 1313 (e.g., if the UE isDocket No.: 25-1025PCTin an RRCJDLE 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 otherwise corresponds 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.

[0175] 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).

[0176] FIG. 13B illustrates a two-step contention-free random access procedure. Similar to the four- step contention-based 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 con tent! on -free random access procedure may not include messages analogous to the Msg 3 1313 and / or the Msg 4 1314

[0177] 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).

[0178] 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 transmissionDocket No.: 25-1025PCTaddressed 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.

[0179] 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 may be 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.

[0180] 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 ACK / 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.

[0181] 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 UE’s RRC state; a type of spectrum (e.g., licensed vs. unlicensed); and / or any other suitable factors.

[0182] 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)Docket No.: 25-1025PCTmay 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.

[0183] 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).

[0184] 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 control signaling 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.

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

[0186] 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).

[0187] 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.Docket No.: 25-1025PCTThe 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.

[0188] 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_1 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_1 may be used for notifying a group of UEs of a physical 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.

[0189] 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).Docket No.: 25-1025PCT

[0190] 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 time-frequency 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 at a 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.

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

[0192] 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).

[0193] As shown in FIG. 14B, the UE may determine a time-frequency resource for a CORESET based on RRC messages. The UE may determine a CCE-to-REG mapping (e.g., interleaved or noninterleaved, 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 oneDocket No.: 25-1025PCTor 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).

[0194] 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 (RUSCH). The UE may transmit the uplink control signaling via a PUCCH using one of several PUCCH formats.

[0195] 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 two OFDM 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 isDocket No.: 25-1025PCTtwo 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.

[0196] 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”.

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

[0198] 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 illustratedDocket No.: 25-1025PCTin FIG. 15, but it will be understood that a mobile communication network may include more than one UE and / or more than one base station, with the same or similar configuration as those shown in FIG. 15.

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

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

[0201] 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 (MIMO) or multi-antenna processing, and / or the like.

[0202] 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.Docket No.: 25-1025PCT

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

[0204] The processing system 1508 and the processing system 1518 may be 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.

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

[0206] 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 powerDocket No.: 25-1025PCTsource 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.

[0207] 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 complexvalued symbols; mapping of the complex-valued modulation 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 complexvalued 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.

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

[0209] 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 comp lex- valued modulation symbols; mapping of the complex-valued modulation symbols onto one or several transmission layers; precoding of the complexvalued modulation symbols on a layer for transmission on the antenna ports; mapping of complexvalued modulation symbols for an antenna port to resource elements; generation of complex-valued time-domain 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.

[0210] 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.Docket No.: 25-1025PCT

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

[0212] 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 BWP switching). A timer may be used to measure 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.

[0213] 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, channelspecific 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 for downlink 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.

[0214] 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 oneDocket No.: 25-1025PCTor more CORESETs. For example, RRC messages 1702 may comprise a list of TCI states (e.g., a list of IDs of TCI states) for CORESETs of wireless device 1700.

[0215] 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).

[0216] 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).

[0217] 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 may determine (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.

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

[0219] 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 viaDocket No.: 25-1025PCTCORESETs. The TCI states indicated by MAC CE 1704 may be referred to as activated TCI states or MAC-CE activated TCI states.

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

[0221] 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. DC1 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 MAC CE that indicates a (e.g., one) TCI state may be referred to as an indicated TCI state.

[0222] Although DCI 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, DCI 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.

[0223] 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).

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

[0225] 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. 17A 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 DCI 1708 not comprising a field indicating a TCI state (any TCI state) for PDSCH reception 1710 (e.g., based on a DCI format of DCI 1708, such as DCI 1_0), wireless device 1700 may apply the TCI state of the CORESET for PDSCH reception 1710.Docket No.: 25-1025PCT

[0226] 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 TCI 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 jointdownlink 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.

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

[0228] 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 may be 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 for downlink 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).

[0229] 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 oneDocket No.: 25-1025PCTTCI state, wireless device 1740 may (e.g., start to) apply the TCI state without additional signaling via MAC CE and / or DCI.

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

[0231] 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 or a 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.

[0232] 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).

[0233] 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 state among the (MAC-CE) activated TCI states, wireless device 1740 applies the (DCI-)indicated TCI state for receiving transmissions on physical channels.Docket No.: 25-1025PCT

[0234] Similar to MAC CE 1716, DC1 1718 may indicate one or more TCI states. For example, DCI 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, DCI 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).

[0235] 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 DCI 1718 indicates a TCI state for downlink and / or uplink, DC1 1718 may be said to update the (indicated) TCI state.

[0236] 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).

[0237] Returning to FIG. 17B, wireless device 1740 receives a DC1 1722 from base station 1760. DCI 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 DC1 1718). In addition, wireless device 1740 transmits uplink transmission 1726 via the TCI state (indicated by MAC CE 1716 and / or DC1 1718).

[0238] 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 untilDocket No.: 25-1025PCTwireless 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 station 1850, 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).

[0239] 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).

[0240] 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).

[0241] 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).

[0242] 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 (non-zero 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).

[0243] 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 aDocket No.: 25-1025PCTreference signal with a periodicity that may be (e.g., dynamically) stopped or skipped based on signaling.

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

[0245] 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 may be 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.

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

[0247] 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.Docket No.: 25-1025PCT

[0248] 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 RUSCH). 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.

[0249] 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 may be 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 DCI 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,

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

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

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

[0253] 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).Docket No.: 25-1025PCT

[0254] 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 RUSCH). 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.

[0255] 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 request field 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

[0256] 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 CSI reports 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.

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

[0258] 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 may be 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.Docket No.: 25-1025PCT

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

[0260] FIG. 19A illustrates a first mode / scheme 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 / scheme 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.

[0261] As illustrated 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).

[0262] 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, of the 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).

[0263] 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.Docket No.: 25-1025PCT

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

[0265] 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).

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

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

[0268] 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 CSI resource 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.

[0269] 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.Docket No.: 25-1025PCT

[0270] 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, PUCCH 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).

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

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

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

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

[0275] 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 state by MAC CE and / or DCI fordownlink and / or uplink). As illustrated, wireless device 1900 receives a reference signal 1906. Reference signal 1906 is a candidate referenceDocket No.: 25-1025PCTsignal for CSI 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.

[0276] In an example, reference signal 1904 of the TCI state may be a reference signal (e.g., CSI-RS) indicated by the TCI state. A configuration of the TCI state may comprise a reference signal identifier / index indicating / identifying the reference signal 1904 of the TCI state.

[0277] In an example, reference signal 1904 of the TCI state may be a source reference signal (e.g., SSB) that is quasi co-located with a reference signal indicated by the TCI state. A configuration of the TCI state may comprise a reference signal identifier / index indicating / identifying the reference signal. The reference signal may be quasi co-located with the reference signal 1904.

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

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

[0280] 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 may be PUCCH format 0 or PUCCH format 1. In yet another example, PUCCH transmission 1912 may be a UCI

[0281] After transmitting PUCCH transmission 1912, wireless device 1900 receives DCI 1914 from base station 1910. DCI 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.

[0282] 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).Docket No.: 25-1025PCT

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

[0284] 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 RRC messages 1902 may comprise a parameter indicating the maximum number of radio link qualities for CSI reporting triggered by wireless device 1900).

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

[0286] 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 TCI 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 referenceDocket No.: 25-1025PCTsignal 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.

[0287] 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 is detected. 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.

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

[0289] 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 ofthe 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).

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

[0291] 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).Docket No.: 25-1025PCT

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

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

[0294] 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) indicating a mode that is being configured among the first mode and the second mode.

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

[0296] 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-SINR) 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.

[0297] 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 transmittingDocket No.: 25-1025PCTCSI 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.

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

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

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

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

[0302] 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).

[0303] 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.Docket No.: 25-1025PCT

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

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

[0306] After receiving PUCCH transmission 1952, base station 1950 transmits a DC1 1954. DCI 1954 may indicate (alternative) uplink resources in order to avoid inference. For example, as illustrated, DCI 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.

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

[0308] FIG. 20 illustrates an example of a first mode for UE-initiated CSI reporting as per an aspect of an embodiment of the present disclosure.

[0309] FIG. 21 illustrates an example of a second mode for UE-initiated CSI reporting as per an aspect of an embodiment of the present disclosure.

[0310] FIG. 22 illustrates an example of a CSI report configuration as per an aspect of an embodiment of the present disclosure.

[0311] In an example, a wireless device may receive one or more messages (e.g., RRC in FIG. 20 and FIG. 21). In an example, the wireless device may receive the one or more messages from a base station. In an example, the wireless device may receive the one or more messages from a relay node. In an example, the wireless device may receive the one or more messages from another wireless device (e.g., TRP, vehicle, remote radio head, and the like). The one or more messages may comprise one or more configuration parameters. In an example, the one or more configuration parameters may be RRC configuration parameter(s). In an example, the one or more configuration parameters may be RRC reconfiguration parameter(s).

[0312] In an example, the one or more configuration parameters may be for one or more cells.Docket No.: 25-1025PCT

[0313] The one or more cells may comprise a cell. The cell may be, for example, a serving cell. In an example, at least one configuration parameter of the one or more configuration parameters may be for the cell. In an example, the cell may be a primary cell (PCell). In an example, the cell may be a primary secondary cell (PSCell). In an example, the cell may be a secondary cell (SCell). The cell may be a secondary cell configured with PUCCH (e.g ., PUCCH SCell). In an example, the cell may be an unlicensed cell, e.g., operating in an unlicensed band. In an example, the cell may be a licensed cell, e.g., operating in a licensed band. In an example, the cell may operate in a first frequency range (FR1). The FR1 may, for example, comprise frequency bands below 6 GHz. In an example, the cell may operate in a second frequency range (FR2). The FR2 may, for example, comprise frequency bands from 24 GHz to 52.6 GHz. In an example, the cell may operate in a third frequency range (FR3). The FR3 may, for example, comprise frequency bands from 52.6 GHz to 71 GHz. The FR3 may, for example, comprise frequency bands starting from (or above) 52.6 GHz.

[0314] In an example, the wireless device may perform uplink transmissions (e.g., PUSCH, PUCCH, PUCCH) via / of the cell in a first time and in a first frequency. The wireless device may perform downlink receptions (e.g., PDCCH, PDSCH) via / of the cell in a second time and in a second frequency. In an example, the cell may operate in a time-division duplex (TDD) mode. In the TDD mode, the first frequency and the second frequency may be the same. In the TDD mode, the first time and the second time may be different. In an example, the cell may operate in a frequency-division duplex (FDD) mode. In the FDD mode, the first frequency and the second frequency may be different. In the FDD mode, the first time and the second time may be the same.

[0315] In an example, the wireless device may be in an RRC connected mode. In an example, the wireless device may be in an RRC idle mode. In an example, the wireless device may be in an RRC inactive mode.

[0316] In an example, the cell may comprise a plurality of BWPs. The plurality of BWPs may comprise one or more uplink BWPs comprising an uplink BWP of the cell. The plurality of BWPs may comprise one or more downlink BWPs comprising a downlink BWP of the cell.

[0317] In an example, a BWP of the plurality of BWPs may be in one of an active state and an inactive state. In an example, in the active state of a downlink BWP of the one or more downlink BWPs, the wireless device may monitor a downlink channel / signal (e.g., PDCCH, DCI, CSI-RS, PDSCH) on / for / via the downlink BWP. In an example, in the active state of a downlink BWP of the one or more downlink BWPs, the wireless device may receive a PDSCH on / via / for the downlink BWP. In an example, in the inactive state of a downlink BWP of the one or more downlink BWPs, the wireless device may not monitor a downlink channel / signal (e.g., PDCCH, DCI, CSI-RS, PDSCH) on / via / for the downlink BWP. In the inactive state of a downlink BWP of the one or more downlink BWPs, the wireless device mayDocket No.: 25-1025PCTstop monitoring (or receiving) a downlink channel / signal (e.g PDCCH, DCI, CSI-RS, PDSCH) on / via / for the downlink BWP. In an example, in the inactive state of a downlink BWP of the one or more downlink BWPs, the wireless device may not receive a PDSCH on / via / for the downlink BWP. In the inactive state of a downlink BWP of the one or more downlink BWPs, the wireless device may stop receiving a PDSCH on / via / for the downlink BWP.

[0318] In an example, in the active state of an uplink BWP of the one or more uplink BWPs, the wireless device may transmit an uplink signal / channel (e.g., PUCCH, preamble, PUSCH, PRACH, PUCCH, etc.) on / via the uplink BWP. In an example, in the inactive state of an uplink BWP of the one or more uplink BWPs, the wireless device may not transmit an uplink signal / channel (e.g., PUCCH, preamble, PUSCH, PRACH, PUCCH, etc.) on / via the uplink BWP.

[0319] In an example, the wireless device may activate the downlink BWP of the one or more downlink BWPs of the cell. In an example, the activating the downlink BWP may comprise setting (or switching to) the downlink BWP as an active downlink BWP of the cell. In an example, the activating the downlink BWP may comprise setting the downlink BWP in the active state. In an example, the activating the downlink BWP may comprise switching the downlink BWP from the inactive state to the active state.

[0320] In an example, the wireless device may activate the uplink BWP of the one or more uplink BWPs of the cell. In an example, the activating the uplink BWP may comprise that the wireless device sets (or switches to) the uplink BWP as an active uplink BWP of the cell. In an example, the activating the uplink BWP may comprise setting the uplink BWP in the active state. In an example, the activating the uplink BWP may comprise switching the uplink BWP from the inactive state to the active state.

[0321] In an example, the one or more configuration parameters may be for the (active) downlink BWP of the cell. In an example, at least one configuration parameter of the one or more configuration parameters may be for the downlink BWP of the cell.

[0322] In an example, the one or more configuration parameters may be for the (active) uplink BWP of the cell. In an example, at least one configuration parameter of the one or more configuration parameters may be for the uplink BWP of the cell.

[0323] The one or more configuration parameters may indicate a subcarrier spacing (or a numerology) for the downlink BWP.

[0324] The one or more configuration parameters may indicate a subcarrier spacing (or numerology) for the uplink BWP.

[0325] A value of the subcarrier spacing (of the downlink BWP and / or the uplink BWP) may be / indicate, for example, 15 kHz (mu = 0). A value of the subcarrier spacing may be / indicate, for example, 30 kHz (mu = 1). A value of the subcarrier spacing may be / indicate, for example, 60 kHz (mu = 2). A value of the subcarrier spacing may be / indicate, for example, 120 kHz (mu = 3). A value of theDocket No.: 25-1025PCTsubcarrier spacing may be / indicate, for example, 240 kHz (mu = 4). A value of the subcarrier spacing may be / indicate, for example, 480 kHz (mu = 5). A value of the subcarrier spacing may be / indicate, for example, 960 kHz (mu = 6). For example, 480 kHz may be valid / applicable in FR3. For example, 960 kHz may be valid / applicable in FR3. For example, 240 kHz may be valid / applicable in FR3. For example, 120 kHz may be valid / applicable in FR3.

[0326] The use of the term “UE-initiated CSI report (or UE-initiated CSI reporting)” is exemplary and is not intended to limit the scope of the invention. Alternative terms that may be substituted include “CSI report triggered by the wireless device”, “CSI report initiated by the wireless device”, “event-triggered CSI report”, “UE-initiated event-triggered CSI report”, “event-driven CSI report”, “event-based CSI report” and “UE-initiated beam report”, among others.

[0327] The one or more configuration parameters may comprise one or more CSI reporting configuration parameters (e.g., CSI-ReportConfig in FIG. 22) of a CSI report configuration.

[0328] The one or more CSI reporting configuration parameters may comprise a report configuration type parameter (e.g., reportConfigType in FIG. 22). A value (e.g., EventTriggered, UE-initiated, UEIBR, and the like) of the report configuration type parameter may indicate UE-initiated CSI reporting. The value of the report configuration type parameter may indicate CSI reporting triggered / initiated by the wireless device. The value is different from ‘periodic’, ‘semiPersistentOnPUCCH’, ‘semiPersistentOnPUSCH, and ‘aperiodic’.

[0329] The one or more CSI reporting configuration parameters may indicate a list / set of reference signals (e.g., CSI-RS, SS / PBCH blocks) for UE-initiated CSI reporting (e.g., RS set for UE-initiated CSI reporting in FIG. 20 and FIG. 21 or a candidate RS set). The list / set of reference signals (hereinafter “a list / set of candidate reference signals”) may be a list / set of candidate reference signals. The list / set of reference signals may be interchangeably used with the list / set of candidate reference signals.

[0330] The one or more CSI reporting configuration parameters may indicate the list / set of candidate reference signals (e.g., CSI-RS, SS / PBCH blocks) for UE-initiated CSI reporting (e.g., RS set for UE- initiated CSI reporting in FIG. 20 and FIG. 21 or a candidate RS set) In an example, the one or more CSI reporting configuration parameters may indicate the list / set of candidate reference signals for use by the wireless device to detect an event (or a trigger-event) that triggers UE-initiated CSI reporting. The one or more CSI reporting configuration parameters may comprise a resource parameter (e.g., resourcesForChannelMeasurement in FIG. 22) indicating the list / set of candidate reference signals. The list / set of candidate reference signals may comprise / indicate one or more candidate reference signals (e.g., Reference signal 1, 2, ..., N in FIG. 20 and FIG. 21).Docket No.: 25-1025PCT

[0331] In an example, the one or more CSI reporting configuration parameters may comprise a carrier parameter (e.g., carrier, ServCelllndex in FIG. 22) indicating / identifying the cell. The carrier parameter may indicate the cell that the list / set of candidate reference signals are configured / transmitted.

[0332] A current reference signal of the wireless device may correspond to a current beam used by the wireless device. The current beam may be a beam corresponding to a TCI state indicated to the wireless device (the indicated TCI state). The wireless device may receive a control command (e.g., DCI, MAC-CE, DC1 1718, Control command in FIG. 20 and FIG. 21) indicating the TCI state for the cell. The TCI state may be a joint TCI state or a downlink TCI state. The joint TCI state may be for use by the wireless device for both downlink receptions (e.g., PDSCH, PDCCH) and uplink transmissions (e.g., PUSCH, PUCCH) via the cell. The downlink TCI state may be for use by the wireless device for downlink receptions (e.g., PDSCH, PDCCH) via the cell and not for uplink transmissions (e.g., PUSCH, PUCCH) via the cell.

[0333] In an example, the TCI state may indicate the current reference signal. The wireless device may determine the current beam (or a spatial domain filter), based on a reference signal (e.g., or the current reference signal) indicated by the TCI state, for receiving downlink transmissions and / or for transmitting uplink transmissions.

[0334] The reference signal indicated by the TCI state (hereinafter “ the current reference signal”) may be the current reference signal. The reference signal indicated by the TCI state may be interchangeably used with the current reference signals.

[0335] The indicated TCI state may be one of a list / set of TCI states configured / indicated by the one or more configuration parameters to the wireless device. The one or more configuration parameters may comprise one or more PDSCH configuration parameters for the cell. The one or more PDSCH configuration parameters may comprise a TCI state list parameter (e.g., dl-OrJointTCI-StateLisf) indicating the list / set of TCI states. In an implementation, where the control command is a MAC CE, the control command may indicate a TCI state of the list / set of configured TCI states. The MAC-CE may indicate mapping of the TCI state to a single TCI codepoint. The MAC-CE may both activate and indicate the TCI state for the cell. In another implementation, where the control command is a DCI, the control command may indicate an activated TCI state of the list / set of configured TCI states. The activated TCI state may be a TCI state of a set of activated TCI states, among the list / set of configured TCI states, activated by another command (e.g., MAC CE) that follows (or after) the reception of the one or more configuration parameters. The MAC-CE may indicate mapping of the activated TCI states to a plurality of TCI codepoints. The MAC-CE may activate (or indicate activation of) the activated TCI states for the cell and the DCI may indicate the TCI state among the activated TCI states.Docket No.: 25-1025PCT

[0336] The one or more configuration parameters may indicate, for the TCI state (or for configuration of the TCI state), a reference signal index / identifier indicating / identifying the current reference signal (e.g . , CSI-RS, TRS). In an example, the current reference signal may be implicitly derived from a quasi- co-location reference signal (QCL RS) of the indicated TCI state. The one or more configuration parameters may indicate, for the TCI state (or for configuration of the TCI state), a reference signal index / identifier indicating / identifying a reference signal (e.g., CSI-RS, TRS) that is quasi co-located with the current reference signal (e.g., SS / PBCH block).

[0337] For example, in a first event (e.g., Event 1), when a radio link quality of the current reference signal becomes worse / lower than a threshold (or a threshold value or a value of a threshold), the wireless device may trigger a UE-initiated CSI reporting.

[0338] For example, in a second event (e.g., Event 2), when a radio link quality of at least one candidate reference signal in / of the list / set of candidate reference signals becomes better than a radio link quality of the current reference signal by a threshold (or a threshold value or a value of a threshold), the wireless device may trigger a UE-initiated CSI reporting.

[0339] For example, in a third event (e.g., Event 7), when a radio link quality of at least one candidate reference signal in / of the list / set of candidate reference signals becomes better than a radio link quality of a reference signal (e g., CSI-RS, TRS, SS / PBCH block) of an activated (or active) TCI state associated with the Q-th best quality among activated TCI states by a threshold (or a threshold value or a value of a threshold), the wireless device may trigger a UE-initiated CSI reporting. The one or more CSI reporting configuration parameters may comprise / indicate a value of the Q (e.g., valueOfQ in FIG.22). Q-th best quality may refer to Q-th highest quality (e.g., Q-th highest RSRP, Q-th highest SINR, Q- th lowest BLER, and the like). For example, when the value of the Q is equal to two, when a radio link quality of at least one candidate reference signal in / of the list / set of candidate reference signals becomes better than a radio link quality of a reference signal of an activated TCI state, among activated TCI states, associated with the second best quality among the activated TCI states by a threshold (or a threshold value or a value of a threshold), the wireless device may trigger a UE-initiated CSI reporting. For example, when the value of the Q is equal to three, when a radio link quality of at least one candidate reference signal in / of the list / set of candidate reference signals becomes better than a radio link quality of a reference signal of an activated TCI state, among activated TCI states, associated with the third best quality among the activated TCI states by a threshold (or a threshold value or a value of a threshold), the wireless device may trigger a UE-initiated CSI reporting. The wireless device may receive a MAC-CE (e.g., MAC CE 1716) indicating the activated TCI states for the cell. The MAC-CE may indicate activation of the TCI states among the list / set of TCI states.Docket No.: 25-1025PCT

[0340] In an example, the activated TCI state may indicate the reference signal. The one or more configuration parameters may indicate, for the activated TCI state (or for configuration of the activated TCI state), a reference signal index / identifier indicating / identifying the reference signal (e.g., CSI-RS, TRS). In an example, the reference signal may be implicitly derived from a quasi-co-location reference signal (QCL RS) of the activated TCI state. The one or more configuration parameters may indicate, for the activated TCI state (or for configuration of the activated TCI state), a reference signal index / identifier indicating / identifying a reference signal (e.g., CSI-RS, TRS) that is quasi co-located with the reference signal (e.g., SS / PBCH block).

[0341] The one or more CSI reporting configuration parameters may comprise / indicate a value of the threshold (e.g., eventThreshold in FIG. 22, eventThresholdEvent2orEvent7, eventThresholdEventl , and the like). The one or more CSI reporting configuration parameters may comprise / indicate the threshold value (e.g., eventThreshold in FIG. 22). The one or more CSI reporting configuration parameters may comprise / indicate the value (or the threshold value) for UE-initiated CSI reporting. The one or more CSI reporting configuration parameters may comprise / indicate the threshold (e.g., the threshold value) for use by the wireless device to detect a trigger-event (an event that triggers a CSI report according to the UE-initiated CSI reporting).

[0342] The one or more CSI reporting configuration parameters may comprise an event type parameter (e.g., eventType in FIG. 22) indicating an event type. A value of the event type parameter may indicate the event type. For example, a first value of the event type parameter may indicate the first event. A second value of the event type parameter may indicate the second event. A third value of the event type parameter may indicate the third event.

[0343] The radio link quality of the current reference signal may be, for example, a layer 1 received signal received power (L1-RSRP). The radio link quality of the at least one candidate reference signal may be, for example, a L1-RSRP.

[0344] In the first event, the wireless device may trigger the UE-initiated CSI reporting, for example, when L1-RSRP of the current reference signal < the threshold. In the first event, the wireless device may trigger the UE-initiated CSI reporting, for example, when L1-RSRP of the current reference signal < the threshold.

[0345] In the second event, the wireless device may trigger the UE-initiated CSI reporting, for example, when L1-RSRP of the at least one candidate reference signal > (the threshold + L1-RSRP of the current reference signal). The wireless device may trigger the UE-initiated CSI reporting, for example, when L1-RSRP of the at least one candidate reference signal (the threshold + L1-RSRP of the current reference signal).Docket No.: 25-1025PCT

[0346] In the third event, the wireless device may trigger the UE-initiated CSI reporting, for example, when L1-RSRP of the at least one candidate reference signal > (the threshold + L1-RSRP of the reference signal of the activated TCI state associated with the Q-th best quality). The wireless device may trigger the UE-initiated CSI reporting, for example, when L1-RSRP of the at least one candidate reference signal (the threshold + L1-RSRP of the reference signal of the activated TCI state associated with the Q-th best quality).

[0347] The radio link quality of the current reference signal may be, for example, layer 1 sig nal-to- interference-plus-noise ratio (L1-SINR). The radio link quality of the at least one candidate reference signal may be, for example, L1-SINR.

[0348] In the first event, the wireless device may trigger the UE-initiated CSI reporting, for example, when L1-SINR of the current reference signal < the threshold. In the first event, the wireless device may trigger the UE-initiated CSI reporting, for example, when L1-SINR of the current reference signal < the threshold.

[0349] In the second event, the wireless device may trigger the UE-initiated CSI reporting, for example, when L1-SINR of the at least one candidate reference signal > (the threshold + L1-SINR of the current reference signal). The wireless device may trigger the UE-initiated CSI reporting, for example, when L1-SINR of the at least one candidate reference signal > (the threshold + L1-SINR of the current reference signal).

[0350] In the third event, the wireless device may trigger the UE-initiated CSI reporting, for example, when L1-SINR of the at least one candidate reference signal > (the threshold + L1-SINR of the reference signal of the activated TCI state associated with the Q-th best quality). The wireless device may trigger the UE-initiated CSI reporting, for example, when L1-SINR of the at least one candidate reference signal (the threshold + L1-SINR of the reference signal of the activated TCI state associated with the Q-th best quality).

[0351] The wireless device may implement a first mode / option / scheme of UE-initiated CSI reporting (as illustrated in FIG. 19A), a second mode / option of UE-initiated CSI reporting (as illustrated in FIG. 19B), or a combination of the first mode / option and the second mode / option for UE-initiated CSI reporting (as illustrated in FIG. 19C). The first mode / option / scheme, which may be referred to as mode A, may include the wireless device requesting an uplink resource to transmit a UE-initiated CSI report and transmitting the UE-initiated CSI report via a dynamically indicated uplink resource. The second mode / option / scheme, which may be referred to as mode B, may include the wireless device using a preconfigured uplink resource (e.g., configured / indicated by the one or more CSI reporting configuration parameters) to transmit a UE-initiated CSI report. As would be understood by a person of skill in the art, a UE-initiated CSI report may be referred, interchangeably, as a UE-initiated beam report, an event-Docket No.: 25-1025PCTdriven CSI / beam report, or a UE-triggered CSI / beam report, event-triggered CSI / beam report, a CSI report triggered by the UE, for example).

[0352] In an example, the one or more CSI reporting configuration parameters may comprise report mode parameter (e.g., reportTransmissionMode in FIG. 22). A first value (e.g. , Mode A) of the report mode parameter may indicate the first mode / option / scheme of U E-initiated CSI reporting. A second value (e.g., Mode B) of the report mode parameter may indicate the second mode / option / scheme of UE- initiated CSI reporting.

[0353] In an example, the one or more CSI reporting configuration parameters may comprise a configured resource configuration (e.g., ConfiguredGrant, RRC-ConfiguredGrant configuredResourceForSecondChannelOfModeB in FIG. 22, and the like) indicating a configured uplink grant on a second uplink BWP of a second cell. The configured resource configuration may comprise a configured grant configuration index / identifier (e.g., ConfiguredGrantConfiglndexm FIG 22) indicating / identifying the configured uplink grant. The configured resource configuration may comprise a BWP index / identifier (e.g., BWP-ld in FIG 22) indicating / identifying the second uplink BWP. The configured resource configuration may comprise a serving cell index / identifier (e.g., ServCelllndex in FIG 22) indicating / identifying the second cell.

[0354] In an example, the cell and the second cell may be the same. In an example, the cell and the second cell may be different.

[0355] The second mode / option / scheme of UE-initiated CSI reporting may be indicated based on the one or more CSI reporting configuration parameters comprising the configured resource configuration. The second mode / option / scheme of UE-initiated CSI reporting may be indicated based on the configured resource configuration being present / provided in the one or more CSI reporting configuration parameters. The one or more CSI reporting configuration parameters comprising the configured resource configuration may indicate the second mode / option / scheme of UE-initiated CSI reporting.

[0356] In an example, the one or more CSI reporting configuration parameters may not comprise the configured resource configuration (e.g., ConfiguredGrant, RRC-ConfiguredGrant configuredResourceForSecondChannelOfModeB in FIG. 22, and the like)

[0357] The first mode / option / scheme of UE-initiated CSI reporting may be indicated based on the one or more CSI reporting configuration parameters not comprising the configured resource configuration. The first mode / option / scheme of UE-initiated CSI reporting may be indicated based on the configured resource configuration being absent (or not being provided) in the one or more CSI reporting configuration parameters. The one or more CSI reporting configuration parameters not comprising the configured resource configuration may indicate the first mode / option / scheme of UE-initiated CSI reporting.Docket No.: 25-1025PCT

[0358] The wireless device may monitor / determine / assess / measure a radio link quality (e.g., L1- RSRP) of the current reference signal.

[0359] The wireless device may monitor / determine / assess / measure a radio link quality (e.g., L1- RSRP) of each candidate reference signal in / of the list / set of candidate reference signals. The wireless device may monitor a respective radio link quality (e.g., L1-RSRP) of each candidate reference signal in / of the list / set of candidate reference signals.

[0360] In the first event, the wireless device may monitor / determine / assess / measure the radio link quality (e g., L1-RSRP) of the current reference signal, for example, after receiving the control command indicating the TCI state.

[0361] In the second event, the wireless device may monitor / determine / assess / measure the radio link quality (e.g., L1-RSRP) of each candidate reference signal in / of the list / set of candidate reference signals, for example, after receiving the control command indicating the TCI state.

[0362] In the third event, the wireless device may monitor / determine / assess / measure the radio link quality (e.g., L1-RSRP) of each candidate reference signal in / of the list / set of candidate reference signals, for example, after receiving the MAC CE indicating activation of the activated TCI states.

[0363] In an example, the one or more CSI reporting configuration parameters may comprise a time window parameter (e.g., eventDetedionTimeWindowLength in FIG. 22) indicating (or set to) a time window (or a value of the time window).

[0364] In an example, the one or more CSI reporting configuration parameters may comprise a count parameter (e.g., eventlnstanceCount, eventlnstanceMaxCount) indicating an event instance count.

[0365] In / for the first event, the wireless device may compare the radio link quality of the current reference signal and / against the threshold. The current reference signal may correspond to the current beam used by the wireless device. The current reference signal may correspond to the indicated TCI state by the control command.

[0366] In / for the first event, the wireless device may be configured to detect a trigger-event (an event that triggers a CSI report according to the UE-initiated CSI reporting) when the radio link quality of the current reference signal becomes worse / lower the threshold value (e.g., L1-RSRP of the current reference signal < threshold). In example, the wireless device may detect a trigger-event based on the radio link quality of the current reference signal being worse / lower the threshold value. Based on detecting the trigger-event, the wireless device may trigger a UE-initiated CSI reporting, for example, to indicate (or trigger a UE-initiated CSI report that indicates) the first event.

[0367] The wireless device may trigger the UE-initiated CSI reporting, for example, for the cell.

[0368] In an example, the wireless device may detect / determine a trigger-event instance based on the radio link quality of the current reference signal becoming worse / lower the threshold value.Docket No.: 25-1025PCT

[0369] In an example, the wireless device may detect the trigger-event based on the radio link quality of the current reference signal becoming worse / lower the threshold value. The wireless device may detect the trigger-event based on detecting / determining the trigger-event instance. The wireless device may detect the trigger-event based on detecting / determining one trigger-event instance. The wireless device may transmit a UE capability information message. The UE capability information message may not comprise a parameter indicating capability / support of detecting the trigger-event based on a total number of trigger-event instances determined / generated with the time window being equal to or greater than the event instance count.

[0370] In an example, the wireless device may detect the trigger-event based on a total number of trigger-event instances determined / generated with the time window being equal to or greater than the event instance count. The wireless device may transmit a UE capability information message. The UE capability information message may comprise a parameter indicating capability / support of detecting the trigger-event based on a total number of trigger-event instances determined / generated with the time window being equal to or greater than the event instance count.

[0371] In / for the second event, the wireless device may compare the monitored radio link quality of each candidate reference signal to a radio link quality of the current reference signal. The current reference signal may correspond to the current beam used by the wireless device. The current reference signal may correspond to the indicated TCI state by the control command.

[0372] In / for the second event, the wireless device may be configured to detect a trigger-event (an event that triggers a CSI report according to the UE-initiated CSI reporting) when the radio link quality of at least one candidate reference signal in / of the list / set of candidate reference signals becomes / is better than the radio link quality of the current reference signal by the threshold value (e.g., L1-RSRP of at least one candidate reference signal > threshold + L1-RSRP of the current reference signal). In example, the wireless device may detect a trigger-event based on the radio link quality of a first candidate reference signal (e.g., Reference signal 1 in FIG. 20 and FIG. 21) in / of the list / set of candidate reference signals becoming better than the radio link quality of the current reference signal by the threshold value. Based on detecting the trigger-event, the wireless device may trigger a UE-initiated CSI reporting to indicate (or a UE-initiated CSI report that indicates) the first candidate reference signal.

[0373] In an example, the wireless device may detect / determine a trigger-event instance based on the radio link quality of at least one candidate reference signal in / of the list / set of candidate reference signals becoming / being better than the radio link quality of the current reference signal by the threshold value.

[0374] In an example, the wireless device may detect the trigger-event based on the radio link quality of at least one candidate reference signal in / of the list / set of candidate reference signalsDocket No.: 25-1025PCTbecomi ng / being better than the radio link quality of the current reference signal by the threshold value. The wireless device may detect the trigger-event based on detecting / determining the trigger-event instance. The wireless device may detect the trigger-event based on detecting / determining one triggerevent instance. The wireless device may transmit a UE capability information message. The UE capability information message may not comprise a parameter indicating capability / support of detecting the trigger-event based on a total number of trigger-event instances determined / generated with the time window being equal to or greater than the event instance count.

[0375] In an example, the wireless device may detect the trigger-event based on a total number of trigger-event instances determined / generated with the time window being equal to or greater than the event instance count. The wireless device may transmit a UE capability information message. The UE capability information message may comprise a parameter indicating capability / support of detecting the trigger-event based on a total number of trigger-event instances determined / generated with the time window being equal to or greater than the event instance count.

[0376] The wireless device may trigger the UE-initiated CSI reporting, for example, for the cell. The wireless device may trigger the UE-initiated CSI reporting, for example, for the first candidate reference signal of the cell.

[0377] In / for the third event, the wireless device may compare the monitored radio link quality of each candidate reference signal to a radio link quality of the reference signal of the activated TCI state associated with the Q-th best quality.

[0378] In / for the third event, the wireless device may be configured to detect a trigger-event (an event that triggers a CSI report according to the UE-initiated CSI reporting) when the radio link quality of at least one candidate reference signal in / of the list / set of candidate reference signals becomes / is better than the radio link quality of the reference signal of the activated TCI state associated with the Q-th best quality by the threshold value (e.g., L1-RSRP of at least one candidate reference signal > threshold + L1-RSRP of the reference signal of the activated TCI state associated with the Q-th best quality). In example, the wireless device may detect a trigger-event based on the radio link quality of a first candidate reference signal (e.g., Reference signal 1 in FIG. 20 and FIG. 21) in / of the list / set of candidate reference signals becoming better than the radio link quality of the reference signal of the activated TCI state associated with the Q-th best quality by the threshold value. Based on detecting the trigger-event, the wireless device may trigger a UE-initiated CSI reporting to indicate (or a UE-initiated CSI report that indicates) the first candidate reference signal.

[0379] The wireless device may trigger the UE-initiated CSI reporting, for example, for the cell. The wireless device may trigger the UE-initiated CSI reporting, for example, for the first candidate reference signal of the cell.Docket No.: 25-1025PCT

[0380] In an example, the wireless device may detect / determine a trigger-event instance based on the radio link quality of at least one candidate reference signal in / of the list / set of candidate reference signals becoming / being better than the radio link quality of the reference signal of the activated TCI state associated with the Q-th best quality by the threshold value.

[0381] In an example, the wireless device may detect the trigger-event based on the radio link quality of at least one candidate reference signal in / of the list / set of candidate reference signals becoming / being better than the radio link quality of the reference signal of the activated TCI state associated with the Q-th best quality by the threshold value. The wireless device may detect the triggerevent based on detecting / determining the trigger-event instance. The wireless device may detect the trigger-event based on detecting / determining one trigger-event instance. The wireless device may transmit a UE capability information message. The UE capability information message may not comprise a parameter indicating capability / support of detecting the trigger-event based on a total number of trigger-event instances determined / generated with the time window being equal to or greater than the event instance count.

[0382] In an example, the wireless device may detect the trigger-event based on a total number of trigger-event instances determined / generated with the time window being equal to or greater than the event instance count. The wireless device may transmit a UE capability information message. The UE capability information message may comprise a parameter indicating capability / support of detecting the trigger-event based on a total number of trigger-event instances determined / generated with the time window being equal to or greater than the event instance count.

[0383] For the first event and / or the second event and / or the third event, based on detecting / determining the trigger-event instance, the wireless device may detect the trigger-event, for example, in response to the one or more CSI reporting configuration parameters not indicating the time window. Based on detecting / determining the trigger-event instance, the wireless device may detect the trigger-event, for example, in response to the one or more CSI reporting configuration parameters not comprising the time window parameter (e.g., eventDetedionTimeWindowLength in FIG. 22). Based on detecting / determining the trigger-event instance, the wireless device may detect the trigger-event, for example, in response to the time window parameter being absent in the one or more CSI reporting configuration parameters.

[0384] For the first event and / or the second event and / or the third event, based on detecting / determining the trigger-event instance, the wireless device may detect the trigger-event, for example, in response to the one or more CSI reporting configuration parameters not indicating the event instance count. Based on detecting / determining the trigger-event instance, the wireless device may detect the trigger-event, for example, in response to the one or more CSI reporting configurationDocket No.: 25-1025PCTparameters not comprising the count parameter (e.g., eventlnstanceCount, eventlnstanceMaxCounf) . Based on detecting / determining the trigger-event instance, the wireless device may detect the triggerevent, for example, in response to the count parameter being absent in the one or more CSI reporting configuration parameters.

[0385] A value of the count parameter (e.g., eventlnstanceCount) may be equal to one. The event instance count may be equal to one. The event instance count may be equal to the value of the count parameter. The value of the count parameter may be equal to one, for example, based on the wireless device not being capable of (or not supporting) detecting the trigger-event based on a total number of trigger-event instances determined / generated with the time window being equal to or greater than the event instance count. The base station may set the value of the count parameter to one, for example, based on the wireless device not being capable of (or not supporting) detecting the trigger-event based on a total number of trigger-event instances determined / generated with the time window being equal to or greater than the event instance count

[0386] The value of the count parameter may not be different from one, for example, based on the wireless device not being capable of (or not supporting) detecting the trigger-event based on a total number of trigger-event instances determined / generated with the time window being equal to or greater than the event instance count. The base station may not set the value of the count parameter different from one, for example, based on the wireless device not being capable of (or not supporting) detecting the trigger-event based on a total number of trigger-event instances determined / generated with the time window being equal to or greater than the event instance count.

[0387] A value of the time window parameter (e.g., eventDetedionTimeWindowLength in FIG. 22) may be equal to zero. The time window may be equal to zero. The time window may be equal to the value of the time window parameter. The value of the time window parameter may be equal to zero, for example, based on the wireless device not being capable of (or not supporting) detecting the triggerevent based on a total number of trigger-event instances determined / generated with the time window being equal to or greater than the event instance count. The base station may set the value of the time window parameter to zero, for example, based on the wireless device not being capable of (or not supporting) detecting the trigger-event based on a total number of trigger-event instances determined / generated with the time window being equal to or greater than the event instance count

[0388] The value of the time window parameter may not be different from zero, for example, based on the wireless device not being capable of (or not supporting) detecting the trigger-event based on a total number of trigger-event instances determined / generated with the time window being equal to or greater than the event instance count. The base station may not set the value of the time window parameter different from zero, for example, based on the wireless device not being capable of (or not supporting)Docket No.: 25-1025PCTdetecting the trigger-event based on a total number of trigger-event instances determined / generated with the time window being equal to or greater than the event instance count.

[0389] A respective periodicity of each candidate reference signal in / of the I ist / set of candidate reference signals may be the same. The one or more configuration parameters may indicate, for each candidate reference signal in / of the I ist / set of candidate reference signals, a respective periodicity. Each candidate reference signal in / of the I ist / set of candidate reference signals may have a first periodicity.

[0390] The one or more configuration parameters may indicate, for the current reference signal, a second periodicity. The current reference signal may have a second periodicity.

[0391] In an example, the first periodicity and the second periodicity may be the same (or equal). In an example, the first periodicity and the second periodicity may be different.

[0392] An evaluation periodicity for the trigger-event instance may be, for example, based on the second periodicity of the current reference signal. The evaluation periodicity for the trigger-event instance may be, for example, same as (or equal to) the second periodicity of the current reference signal.

[0393] An evaluation periodicity for the trigger-event instance may be, for example, based on the first periodicity of a candidate reference signal in / of the I ist / set of candidate reference signals. An evaluation periodicity for the trigger-event instance may be, for example, based on the first periodicity of any candidate reference signal in / of the list / set of candidate reference signals. The evaluation periodicity for the trigger-event instance may be, for example, same as (or equal to) the first periodicity.

[0394] An evaluation periodicity for the trigger-event instance may be, for example, based on both the first periodicity of a candidate reference signal in / of the list / set of candidate reference signals and the second periodicity of the current reference signal. The evaluation periodicity for the trigger-event instance may be, for example, same as (or equal to) a shortest / minimum periodicity among the first periodicity and the second periodicity (e.g., minimum{the first periodicity, the second periodicity}. The evaluation periodicity for the trigger-event instance may be, for example, same as (or equal to) a largest / maximum periodicity among the first periodicity and the second periodicity (e g., maximum{the first periodicity, the second periodicity}. The evaluation periodicity for the trigger-event instance may be, for example, same as (or equal to) a maximum of a time duration and a shortest / minimum periodicity among the first periodicity and the second periodicity (e.g., maximum{the time duration, minimum{the first periodicity, the second periodicity}}. The time duration may be, for example, fixed / predefined / preset / preconfigured (e.g., 2 ms, 4 ms, 6 ms, and the like). The time duration may be, for example, in milliseconds. In an example, the one or more configuration parameters may indicate the time duration.

[0395] The evaluation periodicity may be interchangeably used with an evaluation period.Docket No.: 25-1025PCT

[0396] The wireless device may be configured, after detecting the trigger-event, to trigger a UE- initiated CSI reporting.

[0397] The one or more CSI reporting configuration parameters may comprise a PUCCH resource configuration parameter (e.g., firstPUCCH-ResourceConfig-UEIBR'm FIG. 22, PUCCHResourceConfig- UEIBR, PUCCHResourceConfig, PUCCHResource, FirstPUCCH-ID-UEIBR, FirstPUCCH-UEIBR eventlndicatorChannel, eventlndicatorPUCCH, eventlndicatorUEIBR) for UE-initiated CSI reporting. The PUCCH resource configuration parameter may indicate a PUCCH resource configuration.

[0398] The PUCCH resource configuration may comprise / indicate a PUCCH resource identifier (e.g., resource PUCCH-Resourceld in FIG. 22) indicating / identifying a PUCCH resource (e.g., PUCCH resource in FIG. 20 and FIG. 21).

[0399] The PUCCH resource may be, for example, a periodic PUCCH resource.

[0400] The PUCCH resource configuration may comprise a periodicity-and-offset parameter (e.g., periodicityAndOffset in FIG. 22). The periodicity-and-offset parameter may indicate, for PUCCH transmissions via the PUCCH resource, a periodicity in number of symbols or slots and an offset in slots. The PUCCH transmissions via the PUCCH resource may use, for example, PUCCH format 0. The PUCCH transmissions via the PUCCH resource may use, for example, PUCCH format 1. The PUCCH transmissions via the PUCCH resource may not use, for example, a PUCCH format different from PUCCH format 0 and PUCCH format 1.

[0401] The one or more configuration parameters may comprise one or more PUCCH configuration parameters (e.g., PUCCH-Config). The one or more PUCCH configuration parameters may comprise one or more PUCCH format configuration parameters (e.g., PUCCH-formatO or in PUCCH-formatl).

[0402] The one or more PUCCH format configuration parameters may comprise a starting symbol index parameter (e.g., startingSymbollndex) indicating a starting symbol index (e.g., Zo).

[0403] The one or more PUCCH format configuration parameters may comprise a symbol number parameter (e.g., nrofSymbols) indicating a number of symbols.

[0404] The PUCCH resource may be, for example, on a second cell (or on a second uplink BWP of a second cell). In an example, the cell may be different from the second cell. In an example, the cell may be the same as the second cell.

[0405] Based on (or after) triggering the UE-initiated CSI reporting, the wireless device may transmit, via the PUCCH resource, a PUCCH transmission (e.g., PUCCH resource in FIG. 20 and FIG. 21). The wireless device may transmit, via the PUCCH resource of the second cell, the PUCCH transmission

[0406] The PUCCH transmission via the PUCCH resource may carry (or may be with or may be multiplexed with) an uplink control information (UCI) for / of UE-initiated CSI reporting.Docket No.: 25-1025PCT

[0407] The PUCCH resource configuration parameter in the one or more CSI reporting configuration parameters may comprise a timer parameter (e.g., prohibitTimer'm FIG. 22, UElBR-prohibitTimer, EventlndicatorProhibitTimer, and the like) indicating a timer for PUCCH transmissions with UCI for / of UE-initiated CSI reporting. A value of the timer may be, for example, in milliseconds. The wireless device may not transmit PUCCH transmissions with UCI for / of UE-initiated CSI reporting while the timer is running. The wireless device may be prohibited to transmit PUCCH transmissions with UCI for / of UE- initiated CSI reporting while the timer is running. The wireless device may not be allowed to transmit PUCCH transmissions with UCI for / of UE-initiated CSI reporting while the timer is running.

[0408] In an example, the PUCCH resource configuration parameter in the one or more CSI reporting configuration parameters may not comprise the timer parameter (e.g., prohibitTimer 'm FIG. 22). The timer parameter may be absent in the PUCCH resource configuration parameter. The wireless device may apply / determine / assume zero for the value of the timer. The wireless device may apply / determine / assume zero for the value of the timer, for example, based on the timer parameter being absent in the PUCCH resource configuration parameter.

[0409] The wireless device may transmit, via the PUCCH resource, the PUCCH transmission with the UCI for UE-initiated CSI reporting, for example, based on the timer is not running.

[0410] In an example, the wireless device may start (or restart) the timer from / at a first / starting / initi al / earl iest symbol after the end of the PUCCH transmission with the UCI for UE-initiated CSI reporting.

[0411] The PUCCH transmissions via the PUCCH resource may use, for example, PUCCH format 0. The PUCCH transmissions via the PUCCH resource may use, for example, PUCCH format 1.

[0412] The wireless device may determine / obtain / compute, for the PUCCH transmission with the UCI for UE-initiated CSI reporting, a cyclic shift (e.g., a, or a value of a cyclic shift). The wireless device may determine / obtain / compute the cyclic shift based on an initial cycle shift (e.g., m0) and a second cycle shift (e.g., mcs) set to zero. The wireless device may determine / obtain, for the PUCCH transmission with the UCI for UE-initiated CSI reporting, the initial cycle shift. In an example, the one or more configuration parameters may comprise an initial cycle shift parameter (e.g., initialCyclicShiff) with a value indicating the initial cycle shift. The second cycle shift (e.g., mcs) may be set to (or assumed) as zero.

[0413] The wireless device may transmit, via the PUCCH resource and using the cyclic shift, the PUCCH transmission with the UCI for UE-initiated CSI reporting. The wireless device may determine a low peak-to-average power ratio (PAPR) sequence associated with the cyclic shift. The wireless device may transmit, via the PUCCH resource and using the low PAPR sequence, the PUCCH transmission with the UCI for UE-initiated CSI reporting.Docket No.: 25-1025PCT

[0414] The base station may receive, from the wireless device and via the PUCCH resource, the PUCCH transmission with the UCI for UE-initiated CSI reporting.

[0415] may denote a number of slots in a frame.

[0416] The periodicity indicated by the periodicity-and-offset parameter may be, for example, larger than one slot. The wireless device may determine a transmission occasion in a PUCCH. Based on the periodicity being larger than one slot, the wireless device may determine the transmission occasion in the PUCCH. The transmission occasion may be in a slot with a slot number (e.g.,and in a frame with a frame number (e.g., nf) that satisfies the following:

[0417] (rtf— offset) mod periodicity = 0.

[0418] Based on the periodicity being larger than one slot, the wireless device may determine the transmission occasion in the slot with the slot number in the frame with the frame number that satisfies the equation above.

[0419] The wireless device may transmit, via the PUCCH resource and in the transmission occasion of / in the slot, the PUCCH transmission with the UCI for / of UE-initiated CSI reporting.

[0420] The periodicity indicated by the periodicity-and-offset parameter may be, for example, one slot. Based on the periodicity being one slot, the offset may be equal to zero. Based on the periodicity being one slot, the wireless device may expect the offset to be equal to zero. Based on the periodicity being one slot, the offset may not be different from zero. The base station may set, for the periodicity-and- offset parameter, a value indicating an offset equal to zero, for example, based on the periodicity being one slot. The base station may not set, for the periodicity-and-offset parameter, a value indicating an offset different from zero, for example, based on the periodicity being one slot.

[0421] Based on the periodicity being one slot, the wireless device may determine a transmission occasion in a PUCCH in every / each slot. Based on the periodicity being one slot, the wireless device may determine, in a PUCCH, a respective transmission occasion in each slot. The wireless device may transmit, via the PUCCH resource and in a transmission occasion in / of a slot, the PUCCH transmission with the UCI for / of UE-initiated CSI reporting.

[0422] The periodicity indicated by the periodicity-and-offset parameter may be, for example, smaller than one slot. The wireless device may determine a transmission occasion, in a PUCCH, to start in a symbol with an index (e.g., I). Based on the periodicity being smaller than one slot, the wireless device may determine the transmission occasion, in the PUCCH, to start in the symbol with the index. The index (e.g., I) may satisfy the following equation:

[0423] ( / — Z0mod periodicity) mod periodicity = 0Docket No.: 25-1025PCT

[0424] Based on the periodicity being smaller than one slot, the wireless device may determine the transmission occasion to start in the symbol with the index that satisfies the equation above. (The index of the symbol minus (the starting symbol index mod periodicity)) mod periodicity is equal to zero.

[0425] A mod B returns the remainder of A divided by B (e.g., A / B).

[0426] The wireless device may transmit, via the PUCCH resource and in the transmission occasion of / in a slot, the PUCCH transmission with the UCI for / of UE-initiated CSI reporting.

[0427] The wireless device may determine, for / in the transmission occasion in the PUCCH, a number of symbols available for the PUCCH transmission in the slot is smaller than the number of symbols (e g., nrof Symbols) . The wireless device may not transmit, via the PUCCH resource, the PUCCH transmission based on the number of symbols available for the PUCCH transmission in the slot being smaller than the number of symbols.

[0428] The use of the term "UCI for / of UE-initiated CSI reporting” is exemplary and is not intended to limit the scope of the invention. Alternative terms that may be substituted include "UE-initiated beam report (UEIBR)”, "Event indicator”, “Event Indicator for UEIBR”, “Event indicator channel”, and “UEIBR indicator” among others.

[0429] The use of the term “transmission occasion” is exemplary and is not intended to limit the scope of the invention. Alternative terms that may be substituted include “UEIBR transmission occasion”, “Event indicator transmission occasion”, “UEIBR indicator transmission occasion”, and “Event indicator channel transmission occasion” among others.

[0430] The UCI for / of UE-initiated CSI reporting may be different from scheduling request (SR). The UCI for / of UE-initiated CSI reporting may be different from HARQ-ACK. The UCI for / of UE-initiated CSI reporting may be different from CSI report. The UCI for / of UE-initiated CSI reporting may be different from link recovery request (LRR).

[0431] UCI types reported in a PUCCH transmission may comprise UCI for / of UE-initiated CSI reporting, HARQ-ACK information, SR, LRR, and CSI.

[0432] UCI bits may comprise, for example, UCI for / of UE-initiated CSI reporting bits, if any, HARQ- ACK information bits, if any, SR information bits, if any, LRR information bits, if any, and CSI bits, if any.

[0433] UCI bits may comprise, for example, UCI bits for / of UE-initiated CSI reporting, if any, HARQ- ACK information bits, if any, SR information bits, if any, LRR information bits, if any, and CSI bits, if any.

[0434] In accordance with the first mode / option / scheme of UE-initiated CSI reporting in FIG. 20, the PUCCH transmission via the PUCCH resource may request an uplink resource (or an uplink grant) for a PUSCH transmission (e.g., PUSCH in FIG. 20) to carry / multiplex the UE-initiated CSI report. The PUCCH transmission with the UCI for / of UE-initiated CSI reporting may indicate the request of the uplink resource (or the uplink grant) for the PUSCH transmissionDocket No.: 25-1025PCT

[0435] After transmitting the PUCCH transmission via the PUCCH resource, the wireless device may receive / detect a DCI (e.g., DCI in FIG. 20) indicating an uplink resource (or an uplink grant) for the PUSCH transmission (e.g., PUSCH in FIG. 20). After receiving the DCI, the wireless device may transmit the PUSCH transmission via the uplink resource indicated by the uplink grant.

[0436] The PUSCH transmission may carry (or may be with or may be multiplexed with) the UE- initiated CSI report.

[0437] The PUSCH transmission may be, for example, on a second cell (or on a second uplink BWP of a second cell). In an example, the cell may be different from the second cell. In an example, the cell may be the same as the second cell.

[0438] In an example, the second cell that the wireless device transmits the PUCCH transmission may be different from the second cell that the wireless device transmits the PUSCH transmission. In an example, the second cell that the wireless device transmits the PUCCH transmission may be the same as the second cell that the wireless device transmits the PUSCH transmission.

[0439] For example, the PUSCH transmission may comprise the UE-initiated CSI report indicating the first candidate reference signal. The PUSCH transmission may comprise the UE-initiated CSI report indicating the first candidate reference signal, for example, for the second event and / or the third event. The UE-initiated CSI report may comprise a reference signal resource index / identifier / indicator indicating / identifying the first candidate reference signal. The UE-initiated CSI report may indicate / comprise the radio link quality of the first candidate reference signal.

[0440] The DCI may comprise a CSI request field with a value. The value may indicate (or may be mapped to) a CSI trigger state (or an aperiodic CSI trigger state) associated with the CSI report configuration. The wireless device may transmit the PUSCH transmission with the UE-initiated CSI report, for example, based on the value of the CSI request field in the DCI indicating the CSI trigger state associated with the CSI report configuration that is associated with the UE-initiated CSI reporting.

[0441] For example, the PUSCH transmission may comprise the UE-initiated CSI report indicating the first event. The UE-initiated CSI report may comprise a reference signal resource index / identifier / indicator indicating / identifying a first candidate reference signal from / among the list / set of candidate reference signals. The UE-initiated CSI report may indicate / comprise a radio link quality of the first candidate reference signal.

[0442] The one or more CSI reporting configuration parameters may comprise a reference signal report parameter (e.g., nrof Reported RS in FIG. 22). The reference signal report parameter (or a value of the reference signal report parameter) may indicate a number of reference signals to report in a report format for UE-initiated / event-driven beam reporting. The reference signal report parameter (or a value ofDocket No.: 25-1025PCTthe reference signal report parameter) may indicate a number of reference signals to report in a UE- initiated CSI report.

[0443] The UE-initiated CSI report may indicate one or more candidate reference signals in / from / among the list / set of candidate reference signals. The one or more candidate reference signals may comprise the first candidate reference signal. A number of the one or more candidate reference signals may be equal to the value of the reference signal report parameter. The UE-initiated CSI report may indicate / comprise one or more radio link qualities of the one or more candidate reference signals. Each radio link quality of the one or more radio link qualities may be for (or associated with) a respective candidate reference signal of the one or more candidate reference signals. The one or more radio link qualities may comprise the radio link quality of the first candidate reference signal.

[0444] The one or more CSI reporting configuration parameters may comprise a current beam parameter (e.g., enabledCurrentBeamReport in FIG. 22, enabledCurrentRS-Report, and the like). The current beam parameter may indicate (or enable or disable) whether the current reference signal (or the current beam) is reported in the UE-initiated CSI report, or not.

[0445] In an example, when the current beam parameter is enabled (or present in the one or more CSI reporting configuration parameters), the UE-initiated CSI report may indicate the one or more candidate reference signals and the current reference signal. The UE-initiated CSI report may comprise the one or more radio link qualities of the one or more candidate reference signals and the radio link quality of the current reference signal. A number of reference signals indicated by the UE-initiated CSI report may be equal to the value of the reference signal report parameter plus one. A number of radio link qualities indicated by the UE-initiated CSI report may be equal to the value of the reference signal report parameter plus one.

[0446] In an example, when the current beam parameter is not enabled (or is disabled or is absent in the one or more CSI reporting configuration parameters), the UE-initiated CSI report may indicate the one or more candidate reference signals and may not indicate the current reference signal. The UE- initiated CSI report may comprise the one or more radio link qualities of the one or more candidate reference signals and may not comprise the radio link quality of the current reference signal. A number of reference signals indicated by the UE-initiated CSI report may be equal to the value of the reference signal report parameter. A number of radio link qualities indicated by the UE-initiated CSI report may be equal to the value of the reference signal report parameter.

[0447] FIG. 21 shows an example that illustrates a procedure according to a second mode / option / scheme for UE-initiated CSI reporting. Further, in accordance with the second mode / option / scheme for UE-initiated CSI reporting, the configured resource configuration (e.g., ConfiguredGrant, RRC-ConfiguredGrantconfiguredResourceForSecondChannelOfModeBm ' FIG. 22,Docket No.: 25-1025PCTand the like) may indicate one or more PUSCH transmission occasions of the configured uplink grant for use by the wireless device to transmit UE-initiated CSI reports to the base station (e.g., PUSCH 1, 2, 3, 4 in FIG. 21 ). The one or more PUSCH transmission occasions of the configured uplink grant may be, for example, periodic.

[0448] In accordance with the second mode / option / scheme of UE-initiated CSI reporting in FIG. 21 , the PUCCH transmission via the PUCCH resource may notify of a PUSCH transmission that will carry (be multiplexed with) the UE-initiated CSI report via a PUSCH transmission occasion (e.g., PUSCH 4 in FIG. 21 ) of the configured uplink grant. The one or more PUSCH transmission occasions of the configured uplink grant may comprise the PUSCH transmission occasion of the configured uplink grant. The PUCCH transmission via the PUCCH resource may notify the base station that the PUSCH transmission with the UE-initiated CSI report is to be transmitted via the PUSCH transmission occasion of the one or more PUSCH transmission occasions. The PUCCH transmission may notify the base station that the UE-initiated CSI reporting has been triggered. The PUCCH transmission may comprise a notification that indicates the PUSCH transmission occasion, of the one or more PUSCH transmission occasions, that will be used by the wireless device for the PUSCH transmission. In example, the notification may indicate the PUSCH transmission occasion (e.g., PUSCH 4 in FIG. 21), of the one or more PUSCH transmission occasions, for the PUSCH transmission.

[0449] The PUSCH transmission occasion may be, for example, an earliest / first / starting PUSCH transmission occasion, among the one or more PUSCH transmission occasions of the configured uplink grant, that occurs after the PUCCH transmission.

[0450] The PUSCH transmission occasion may be, for example, an earliest / first / starting PUSCH transmission occasion, among the one or more PUSCH transmission occasions, that occurs a time duration / gap / delay / offset (e.g., time duration in FIG. 21) after the PUCCH transmission. The PUSCH transmission occasion may be an earliest / first / starting available PUSCH transmission occasion, among the one or more PUSCH transmission occasions, that occurs a time duration / gap / delay / offset after the PUCCH transmission. The PUSCH transmission occasion may be an earliest / first / starting available PUSCH transmission occasion, among the one or more PUSCH transmission occasions, that occurs a time duration / gap / delay / offset after a last / final repetition of the PUCCH transmission. The wireless device may not drop PUSCH transmission(s) in an available PUSCH transmission occasion. The PUSCH transmission occasion may be an earliest / first / starting available PUSCH transmission occasion, among the one or more PUSCH transmission occasions, that is at least the time duration / gap / delay / offset after a last / final / ending symbol of the PUCCH transmission.Docket No.: 25-1025PCT

[0451] In an example, the one or more CSI reporting configuration parameters may indicate the time duration / gap / delay / offset. In an example, the one or more configuration parameters may indicate the time duration / gap / delay / offset.

[0452] The wireless device may transmit a UE capability message. In an example, the UE capability message may comprise a parameter indicating a minimum time duration / gap / delay / offset. The minimum time duration / gap / delay may be, for example, in terms of symbols. The time duration / gap / delay may be equal to or greater / larger than the minimum time duration / gap / delay / offset. In an example, the UE capability message may comprise a parameter indicating a second time duration / gap / delay / offset. The second time duration / gap / delay may be, for example, in terms of symbols. The time duration / gap / delay may be equal to or greater / larger than the second time duration / gap / delay / offset.

[0453] After transmitting the PUCCH transmission, the wireless device may transmit the PUSCH transmission via the PUSCH transmission occasion. After notifying the PUSCH transmission, the wireless device may transmit the PUSCH transmission via the PUSCH transmission occasion.

[0454] The PUSCH transmission may carry (or may be with or may be multiplexed with) the UE- initiated CSI report.

[0455] The PUSCH transmission may be, for example, on a second cell (or on a second uplink BWP of a second cell). In an example, the cell may be different from the second cell. In an example, the cell may be the same as the second cell.

[0456] In an example, the second cell that the wireless device transmits the PUCCH transmission may be different from the second cell that the wireless device transmits the PUSCH transmission. In an example, the second cell that the wireless device transmits the PUCCH transmission may be the same as the second cell that the wireless device transmits the PUSCH transmission.

[0457] When a first numerology (or a subcarrier spacing) of the second cell that the wireless device transmits the PUCCH transmission is different from a second numerology (or a subcarrier spacing) of the second cell that the wireless device transmits the PUSCH transmission, the wireless device may not know whether to determine a symbol duration of the time duration / gap / delay based on the first numerology and / or the second numerology. If the base station and the wireless device are not aligned on the numerology used to determine the symbol duration, the wireless device may transmit the PUSCH transmission in a first PUSCH transmission occasion of the configured uplink grant and the base station may monitor the PUSCH transmission in a second PUSCH transmission occasion of the configured uplink grant. When the first and the second PUSCH transmission occasions are not the same, the base station may not receive the PUSCH transmission. The base station may not receive the UE-initiated CSI report timely that may lead to beam failure and / or radio link failure. The wireless device may retransmit the PUSCH transmission leading to increased latency and power consumption. Example embodimentsDocket No.: 25-1025PCTbelow enhance symbol duration determination of the time duration / gap / delay which may result in timely UE-initiated CSI reports, reduced latency and / or reduced power consumption.

[0458] A symbol duration of the time d uration / g ap / delay / offset may be determined, for example, based on a smallest numerology (or a smallest subcarrier spacing) between the PUCCH transmission via the PUCCH resource and the PUSCH transmission via the PUSCH transmission occasion.

[0459] A symbol duration of the time duration / gap / delay / offset may be determined, for example, based on a largest / highest numerology (or a largest / highest subcarrier spacing) between the PUCCH transmission via the PUCCH resource and the PUSCH transmission via the PUSCH transmission occasion.

[0460] A symbol duration of the time duration / gap / delay / offset may be determined, for example, based on a numerology (or a subcarrier spacing or a subcarrier spacing configuration) of the PUCCH transmission via the PUCCH resource.

[0461] A symbol duration of the time duration / gap / delay / offset may be determined, for example, based on a numerology (or a subcarrier spacing or a subcarrier spacing configuration) of the PUSCH transmission via the PUSCH transmission occasion.

[0462] A symbol duration of the time duration / gap / delay / offset may be determined, for example, based on an active BWP with the smallest subcarrier spacing among BWP(s), of / from cell(s) with the trigger-event detected, that are active at the end of the PUCCH transmission. Each BWP of the BWP(s) may be for a respective cell of the cell(s). The cell(s) may comprise the cell. The active BWP may be, for example, an active uplink BWP.

[0463] A symbol duration of the time duration / gap / delay / offset may be determined, for example, based on an active BWP with the smallest subcarrier spacing among BWPs, of / from the second cell with the PUCCH transmission and the second cell with the PUSCH transmission, that are active at the end of the PUCCH transmission.

[0464] For example, the PUSCH transmission may comprise the UE-initiated CSI report indicating the first candidate reference signal. The PUSCH transmission may comprise the UE-initiated CSI report indicating the first candidate reference signal, for example, for the second event and / or the third event. The UE-initiated CSI report may comprise a reference signal resource index / identifier / indicator indicating / identifying the first candidate reference signal. The UE-initiated CSI report may indicate / comprise the radio link quality of the first candidate reference signal.

[0465] For example, the PUSCH transmission may comprise the UE-initiated CSI report indicating the first event. The UE-initiated CSI report may comprise a reference signal resource index / identifier / indicator indicating / identifying a first candidate reference signal from / among the list / set ofDocket No.: 25-1025PCTcandidate reference signals. The UE-initiated CSI report may indicate / comprise a radio link quality of the first candidate reference signal.

[0466] The UE-initiated CSI report may indicate one or more candidate reference signals in / from / among the list / set of candidate reference signals. The one or more candidate reference signals may comprise the first candidate reference signal. A number of the one or more candidate reference signals may be equal to the value of the reference signal report parameter. The UE-initiated CSI report may indicate / comprise one or more radio link qualities of the one or more candidate reference signals. Each radio link quality of the one or more radio link qualities may be for (or associated with) a respective candidate reference signal of the one or more candidate reference signals. The one or more radio link qualities may comprise the radio link quality of the first candidate reference signal.

[0467] In an example, when the current beam parameter is enabled (or present in the one or more CSI reporting configuration parameters), the UE-initiated CSI report may indicate the one or more candidate reference signals and the current reference signal. The UE-initiated CSI report may comprise the one or more radio link qualities of the one or more candidate reference signals and the radio link quality of the current reference signal. A number of reference signals indicated by the UE-initiated CSI report may be equal to the value of the reference signal report parameter plus one. A number of radio link qualities indicated by the UE-initiated CSI report may be equal to the value of the reference signal report parameter plus one.

[0468] In an example, when the current beam parameter is not enabled (or is disabled or is absent in the one or more CSI reporting configuration parameters), the UE-initiated CSI report may indicate the one or more candidate reference signals and may not indicate the current reference signal. The UE- initiated CSI report may comprise the one or more radio link qualities of the one or more candidate reference signals and may not comprise the radio link quality of the current reference signal. A number of reference signals indicated by the UE-initiated CSI report may be equal to the value of the reference signal report parameter. A number of radio link qualities indicated by the UE-initiated CSI report may be equal to the value of the reference signal report parameter

[0469] In an example, the wireless device may start (or restart) the timer (e.g., prohibitTimer'm FIG.22) from / at a first / starting / initial / earliest symbol after the end of the PUSCH transmission with the UE- initiated CSI report.

[0470] The base station may receive, from the wireless device and in / via the PUSCH transmission occasion, the PUSCH transmission with the UE-initiated CSI report.

[0471] In an example, the PUCCH transmission via the PUCCH resource may fail. The PUCCH transmission via the PUCCH resource may fail, for example, based on a number of the PUCCH transmission via the PUCCH resource being equal to or greater than a maximum transmission countDocket No.: 25-1025PCT(e.g. , UElBR-TransMax, Eventlndicator-TransMax, and the like). The one or more configuration parameters may indicate the maximum transmission count. The PUCCH transmission via the PUCCH resource may fail, for example, based on the number of the PUCCH transmission via the PUCCH resource reaching the maximum transmission count.

[0472] The wireless device may initiate a random-access procedure, for example, based on the PUCCH transmission via the PUCCH resource failing.

[0473] The wireless device may complete the random-access procedure, for example, successfully.

[0474] The wireless device may trigger a random-access report (or a random-access report entry). The wireless device may trigger the random-access report, for example, for the random-access procedure initiated based on the PUCCH transmission via the PUCCH resource failing.

[0475] The random-access report may comprise a field (e.g., raPurpose) to include the purpose of triggering the random-access procedure. The wireless device may set the field to a value / indicator (e.g., UEIBR-Failure, Eventindicator-Failure, and the like) that indicates the failure of the PUCCH transmission via the PUCCH resource. The value / indicator may indicate the failure of the PUCCH transmission with the UCI for / of UE-initiated CSI reporting. The value / indicator may be different from an value / indicator of a scheduling request failure that is used in case of SR failures.

[0476] The wireless device may transmit, to the base station, a UE information response message (e.g., UElnformationResponse) based on a request from the base station. The UE information response message may comprise the random-access report. The base station may receive the UE information response.

[0477] In an example, the wireless device may perform / execute a MAC reset.

[0478] In an example, an upper layer (e.g., RRC) of the wireless device may request a reset of a MAC entity of the wireless device. The wireless device may perform / execute the MAC reset, for example, based on the upper layer requesting the reset of the MAC entity. The upper layer may request the reset of the MAC entity, for example, based on receiving an RRC message (e.g., RRCResume or RRCSetup).

[0479] The wireless device may perform / execute the MAC reset, for example, based on a deactivation of secondary cell group (SCG).

[0480] The wireless device may perform / execute the MAC reset, for example, based on performing an RRC reconfiguration with synchronization (e.g., RRCReconflguration with reconfiguratlonWithSync).

[0481] The wireless device may release, for the MAC reset, the PUCCH resource configuration parameter for UE-initiated CSI reporting. The wireless device may release, during the MAC reset, the PUCCH resource configuration parameter for UE-initiated CSI reporting. The wireless device may release, based on performing / executing the MAC reset, the PUCCH resource configuration parameter for UE-initiated CSI reporting.Docket No.: 25-1025PCT

[0482] The wireless device may release, for the MAC reset, a PUCCH configuration for CSI different from the UE-initiated CSI reporting. The wireless device may release, for the MAC reset, a PUCCH configuration for periodic CSI and / or semi-persistent CSI. The wireless device may release, for the MAC reset, a PUCCH configuration for scheduling request (SR). The wireless device may release, for the MAC reset, an SRS configuration.

[0483] The wireless device may trigger / initiate / perform, on / to / via a target SpCell, a random-access procedure for the RRC reconfiguration with synchronization (e.g., RRCReconfiguration with reconfigurationWithSync). The wireless device may complete the random-access procedure successfully. One or more SpCell configuration parameters (e.g., spCellConfig) may comprise a reconfiguration with synch parameter (e.g., reconfigurationWithSync). Based on completing the randomaccess procedure successfully, the wireless device may apply parts of the PUCCH resource configuration parameter for UE-initiated CSI reporting that do not require the wireless device to know a system frame number (SFN) of the target SpCell. Based on completing the random-access procedure successfully, the wireless device may apply parts of the SR configuration that do not require the wireless device to know the SFN of the target SpCell. Based on completing the random-access procedure successfully, the wireless device may apply parts of the CSI reporting configuration that do not require the wireless device to know the SFN of the target SpCell.

[0484] After / upon acquiring the SFN of the target SpCell, the wireless device may apply parts of a measurement configuration and a radio resource configuration that requires the wireless device to know the SFN of the target SpCell. The measurement configuration and the radio resource configuration that requires the wireless device to know the SFN of the target SpCell may comprise PUCCH resource configuration parameter for UE-initiated CSI reporting, measurement gaps, periodic CQI reporting, scheduling request configuration, and sounding RS configuration

[0485] The wireless device may receive, from the base station, a UE capability enquiry message (e.g., UECapabilityEnquiry). The wireless device may transmit, to the base station, a capability information message (e.g., U ECapability Information, UE capability information message), for example, based on receiving the UE capability enquiry message. The base station may receive the capability information message. In an example, the wireless device may transmit the capability information message before receiving the one or more messages comprising the one or more configuration parameters.

[0486] The capability information message may comprise a first multiplexing parameter (e.g., mux- UEIBR-HARQ-ACK, mux-Eventlndicator-HARQ-ACK, and the like).

[0487] The wireless device may transmit / signal the first multiplexing parameter per feature set per component carrier (per CC per band per band combination). The wireless device may transmit / signal the first multiplexing parameter, for example, per feature set per component carrier (CC) per band perDocket No.: 25-1025PCTband combination. The wireless device may transmit / signal the first multiplexing parameter, for example, for each CC in each band in each band combination.

[0488] The first multiplexing parameter may indicate whether the wireless device supports an U Cl for UE-initiated CSI reporting and a HARQ-ACK multiplexing once per subslot using a PUCCH (or HARQ- ACK piggybacked on a PUSCH) when the UCI for UE-initiated CSI reporting and the HARQ-ACK are supposed / configured to be sent / transmitted with different starting symbols in a subslot.

[0489] The first multiplexing parameter may indicate whether the wireless device supports multiplexing of an UCI for UE-initiated CSI reporting and a HARQ-ACK once per subslot, for example, using a PUCCH (or HARQ-ACK piggybacked on a PUSCH) when the UCI for UE-initiated CSI reporting and the HARQ-ACK are supposed / configured to be sent / transmitted with different starting symbols in a subslot.

[0490] The first multiplexing parameter may indicate whether the wireless device supports multiplexing of an UCI for UE-initiated CSI reporting and a HARQ-ACK in / on a PUCCH or piggybacking on a PUSCH once per subslot, for example, when the UCI for UE-initiated CSI reporting and the HARQ- ACK are supposed / configured to be sent / transmitted with different starting symbols in a subslot.

[0491] A starting symbol of an UCI for UE-initiated CSI reporting may be a first symbol in a subslot. A starting symbol of a HARQ-ACK may be a second symbol in the subslot. The first symbol and the second symbol may be different. The one or more configuration parameters may indicate, for transmission of the UCI for UE-initiated CSI reporting, the first symbol in the subslot as the starting symbol. The one or more configuration parameters may indicate, for transmission of the HARQ-ACK, the second symbol in the subslot as the starting symbol.

[0492] The wireless device may multiplex (or piggyback) the UCI for UE-initiated CSI reporting and the HARQ-ACK in / using / on an uplink transmission (e.g., PUCCH transmission or a PUSCH transmission if piggybacked), for example, based on the capability information message comprising the first multiplexing parameter. The wireless device may multiplex (or piggyback) the UCI for UE-initiated CSI reporting and the HARQ-ACK in / using / on the uplink transmission (e.g., PUCCH transmission or a PUSCH transmission if piggybacked), for example, based on the wireless device supporting (or being capable of) multiplexing of an UCI for UE-initiated CSI reporting and a HARQ-ACK once per subslot when the UCI for UE-initiated CSI reporting and the HARQ-ACK are supposed / configured to be sent / transmitted with different starting symbols in a subslot.

[0493] The wireless device may multiplex (or piggyback) the UCI for UE-initiated CSI reporting and the HARQ-ACK, for example, based on a scheduled / configured transmission of the UCI for UE-initiated CSI reporting overlapping in time with a scheduled / configured transmission of the HARQ-ACK. The wireless device may multiplex (or piggyback) the UCI for UE-initiated CSI reporting and the HARQ-ACK,Docket No.: 25-1025PCTfor example, based on a transmission occasion of the UCI for UE-initiated CSI reporting overlapping in time with a transmission occasion of the HARQ-ACK. The wireless device may multiplex (or piggyback) the UCI for UE-initiated CSI reporting and the HARQ-ACK, for example, based on an uplink resource (e.g., PUCCH resource) of the UCI for UE-initiated CSI reporting overlapping in time with an uplink resource (e.g., PUCCH resource) of the HARQ-ACK.

[0494] The wireless device may transmit the uplink transmission with / carrying the UCI for UE-initiated CSI reporting and the HARQ-ACK. The wireless device may transmit the uplink transmission, for example, after multiplexing (or piggybacking) the UCI for UE-initiated CSI reporting and the HARQ-ACK in the uplink transmission.

[0495] The first multiplexing parameter may be different from a multiplexing parameter (e.g., mux-SR- HARQ-ACK) that indicates whether the wireless device supports an SR and a HARQ-ACK multiplexing once per subslot using a PUCCH (or HARQ-ACK piggybacked on a PUSCH) when the SR and the HARQ-ACK are supposed / configured to be sent / transmitted with different starting symbols in a subslot. The capability information message may, for example, comprise the multiplexing parameter. The capability information message may not, for example, comprise the multiplexing parameter.

[0496] The capability information message may comprise a second multiplexing parameter (e.g., mux- UEIBR-HARQ-ACK-PUCCH, mux-Eventlndicator-HARQ-ACK-PUCCH, and the like). The second multiplexing parameter may be, for example, applicable to non-shared spectrum channel access. The second multiplexing parameter may not be, for example, applicable to shared spectrum channel access.

[0497] The wireless device may transmit / signal the second multiplexing parameter per UE.

[0498] The second multiplexing parameter may indicate whether the wireless device supports multiplexing of an UCI for UE-initiated CSI reporting and a HARQ-ACK in / on a PUCCH or piggybacking on a PUSCH once per slot, for example, when the UCI for UE-initiated CSI reporting and the HARQ- ACK are supposed / configured to be sent / transmitted with different starting symbols in a slot.

[0499] A starting symbol of an UCI for UE-initiated CSI reporting may be a first symbol in a slot. A starting symbol of a HARQ-ACK may be a second symbol in the slot. The first symbol and the second symbol may be different. The one or more configuration parameters may indicate, for transmission of the UCI for UE-initiated CSI reporting, the first symbol in the slot as the starting symbol. The one or more configuration parameters may indicate, for transmission of the HARQ-ACK, the second symbol in the slot as the starting symbol.

[0500] The wireless device may multiplex (or piggyback) the UCI for UE-initiated CSI reporting and the HARQ-ACK in / using / on an uplink transmission (e.g., PUCCH transmission or a PUSCH transmission if piggybacked), for example, based on the capability information message comprising the second multiplexing parameter. The wireless device may multiplex (or piggyback) the UCI for UE-Docket No.: 25-1025PCTinitiated CSI reporting and the HARQ-ACK in / using / on the uplink transmission (e.g., PUCCH transmission or a RUSCH transmission if piggybacked), for example, based on the wireless device supporting (or being capable of) multiplexing of an UCI for UE-initiated CSI reporting and a HARQ-ACK once per slot when the UCI for UE-initiated CSI reporting and the HARQ-ACK are supposed / configured to be sent / transmitted with different starting symbols in a slot.

[0501] The wireless device may multiplex (or piggyback) the UCI for UE-initiated CSI reporting and the HARQ-ACK, for example, based on a scheduled / configured transmission of the UCI for UE-initiated CSI reporting overlapping in time with a scheduled / configured transmission of the HARQ-ACK. The wireless device may multiplex (or piggyback) the UCI for UE-initiated CSI reporting and the HARQ-ACK, for example, based on a transmission occasion of the UCI for UE-initiated CSI reporting overlapping in time with a transmission occasion of the HARQ-ACK. The wireless device may multiplex (or piggyback) the UCI for UE-initiated CSI reporting and the HARQ-ACK, for example, based on an uplink resource (e.g., PUCCH resource) of the UCI for UE-initiated CSI reporting overlapping in time with an uplink resource (e.g., PUCCH resource) of the HARQ-ACK.

[0502] The wireless device may transmit the uplink transmission with / carrying the UCI for UE-initiated CSI reporting and the HARQ-ACK. The wireless device may transmit the uplink transmission, for example, after multiplexing (or piggybacking) the UCI for UE-initiated CSI reporting and the HARQ-ACK in the uplink transmission.

[0503] The second multiplexing parameter may be different from a multiplexing parameter (e.g., mux- SR-HARQ-ACK-PUCCH) that indicates whether the wireless device supports an multiplexing of an SR and a HARQ-ACK in / on a PUCCH or piggybacking on a PUSCH once per slot when the SR and the HARQ-ACK are supposed / configured to be sent / transmitted with different starting symbols in a slot. The capability information message may, for example, comprise the multiplexing parameter. The capability information message may not, for example, comprise the multiplexing parameter. The multiplexing parameter may be, for example, applicable to non-shared spectrum channel access. The multiplexing parameter may not be, for example, applicable to shared spectrum channel access.

[0504] The capability information message may comprise a third multiplexing parameter (e.g., mux- UEIBR-HARQ-ACK-PUCCH, mux-Eventlndicator-HARQ-ACK-PUCCH, and the like). The third multiplexing parameter may not be, for example, applicable to non-shared spectrum channel access. The third multiplexing parameter may be, for example, applicable to shared spectrum channel access.

[0505] The wireless device may transmit / signal the third multiplexing parameter per UE.

[0506] The third multiplexing parameter may indicate whether the wireless device supports multiplexing of an UCI for UE-initiated CSI reporting and a HARQ-ACK in / on a PUCCH or piggybacking on a PUSCH once per slot, for example, when the UCI for UE-initiated CSI reporting and the HARQ-Docket No.: 25-1025PCTACK are supposed / configured to be sent / transmitted with different starting symbols in a slot in a shared spectrum channel access.

[0507] A starting symbol of an UCI for UE-initiated CSI reporting may be a first symbol in a slot. A starting symbol of a HARQ-ACK may be a second symbol in the slot. The first symbol and the second symbol may be different. The one or more configuration parameters may indicate, for transmission of the UCI for UE-initiated CSI reporting, the first symbol in the slot as the starting symbol. The one or more configuration parameters may indicate, for transmission of the HARQ-ACK, the second symbol in the slot as the starting symbol.

[0508] The wireless device may multiplex (or piggyback) the UCI for UE-initiated CSI reporting and the HARQ-ACK in / using / on an uplink transmission (e.g., PUCCH transmission or a PUSCH transmission if piggybacked), for example, based on the capability information message comprising the third multiplexing parameter. The wireless device may multiplex (or piggyback) the UCI for UE-initiated CSI reporting and the HARQ-ACK in / using / on the uplink transmission (e.g., PUCCH transmission or a PUSCH transmission if piggybacked), for example, based on the wireless device supporting (or being capable of) multiplexing of an UCI for UE-initiated CSI reporting and a HARQ-ACK once per slot when the UCI for UE-initiated CSI reporting and the HARQ-ACK are supposed / configured to be sent / transmitted with different starting symbols in a slot in a shared spectrum channel access.

[0509] The wireless device may multiplex (or piggyback) the UCI for UE-initiated CSI reporting and the HARQ-ACK, for example, based on a scheduled / configured transmission of the UCI for UE-initiated CSI reporting overlapping in time with a scheduled / configured transmission of the HARQ-ACK. The wireless device may multiplex (or piggyback) the UCI for UE-initiated CSI reporting and the HARQ-ACK, for example, based on a transmission occasion of the UCI for UE-initiated CSI reporting overlapping in time with a transmission occasion of the HARQ-ACK. The wireless device may multiplex (or piggyback) the UCI for UE-initiated CSI reporting and the HARQ-ACK, for example, based on an uplink resource (e.g., PUCCH resource) of the UCI for UE-initiated CSI reporting overlapping in time with an uplink resource (e g., PUCCH resource) of the HARQ-ACK.

[0510] The wireless device may transmit the uplink transmission with / carrying the UCI for UE-initiated CSI reporting and the HARQ-ACK. The wireless device may transmit the uplink transmission, for example, after multiplexing (or piggybacking) the UCI for UE-initiated CSI reporting and the HARQ-ACK in the uplink transmission.

[0511] The third multiplexing parameter may be different from a multiplexing parameter (e.g., mux- SR-HARQ-ACK-PUCCH that indicates whether the wireless device supports an multiplexing of an SR and a HARQ-ACK in / on a PUCCH or piggybacking on a PUSCH once per slot when the SR and the HARQ-ACK are supposed / configured to be sent / transmitted with different starting symbols in a slot in aDocket No.: 25-1025PCTshared spectrum channel access. The capability information message may, for example, comprise the multiplexing parameter. The capability information message may not, for example, comprise the multiplexing parameter. The multiplexing parameter may not be, for example, applicable to non-shared spectrum channel access. The multiplexing parameter may be, for example, applicable to shared spectrum channel access.

[0512] If the wireless device does not indicate whether the wireless device is capable of multiplexing / piggybacking the UCI for UE-initiated CSI reporting and the HARQ-ACK in an uplink transmission, the base station may not receive the uplink transmission leading to increased error rates. If the wireless device does not indicate whether the wireless device is capable of multiplexing / piggybacking the UCI for UE-initiated CSI reporting and the HARQ-ACK in an uplink transmission, the base station may apply two hypotheses to receive the uplink transmission (e.g., one with multiplexed / piggybacked and one without multiplexed / piggybacked) leading to increased power consumption at the base station.

[0513] Indication of at least one of the first multiplexing parameter, the second multiplexing parameter, or and the third multiplexing parameter may reduce error rates and / or reduce power consumption.

[0514] An aperiodic CSI report is different from a UE-initiated CSI report (e.g., event-triggered CSI report, UE-initiated beam report). The aperiodic CSI report may be triggered / requested based on receiving, from a base station, a DCI. The DCI may comprise a CSI request field with a non-zero value. The base station may request / trigger the aperiodic CSI report by sending / transmitting the DCI. The UE- initiated CSI report is triggered, by a wireless device, based on detecting an event (or satisfying / fulfilling a condition). The base station may not request / trigger the UE-initiated CSI report.

[0515] A semi-persistent CSI report is different from a UE-initiated CSI report (e.g., event-triggered CSI report, UE-initiated beam report). The semi-persistent CSI report may be activated / deactivated based on receiving, from a base station, a control command (e.g., DCI, MAC-CE). For example, when the control command is a DCI, the DCI may comprise a CSI request field with a non-zero value. The base station may activate / deactivate the semi-persistent CSI report by sending / transmitting the control command. The UE-initiated CSI report is triggered, by a wireless device, based on detecting an event (or satisfying / fulfilling a condition). The base station may not activate / deactivate the UE-initiated CSI report.

Claims

1. Docket No.: 25-1025PCTCLAIMSWhat 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 of an uplink bandwidth part (BWP) of a cell, wherein the one or more configuration parameters indicate a subcarrier spacing of an uplink BWP; and one or more channel state information (CSI) report configuration parameters for userequipment (UE) initiated CSI reporting, wherein the one or more CSI report configuration parameters comprise:a report transmission mode parameter indicating a transmission mode for the UE- initiated CSI reporting is a second mode in which a CSI report of the UE-initiated CSI reporting is transmitted in a physical uplink shared channel (PUSCH) transmission of a Type 1 configured uplink grant; anda physical uplink control channel (PUCCH) resource configuration indicating a PUCCH resource on the uplink BWP for UE-initiated report indicator (UEIRI), wherein the UEIRI notifies that a PUSCH transmission of the Type 1 configured uplink grant is to be used to carry the CSI report;transmitting, via the PUCCH resource of the uplink BWP, a PUCCH transmission with the UEIRI; andtransmitting, in a first available transmission occasion of the Type 1 configured uplink grant, the PUSCH transmission comprising the CSI report, wherein:the first available transmission occasion occurs a number of symbols after an end of the PUCCH transmission; andthe number of symbols is based on the subcarrier spacing of the PUCCH resource with the UEIRI.

2. A method comprising:transmitting, by a wireless device via a physical uplink control channel (PUCCH) resource, a PUCCH transmission with a user equipment (UE) initiated report indicator (UEIRI) for UE-initiated channel state information (CSI) reporting, wherein the UEIRI notifies that a PUSCH transmission of a Type 1 configured uplink grant is to be used to carry a CSI report; andtransmitting, in a first available transmission occasion of the Type 1 configured uplink grant, the CSI report, wherein:Docket No.: 25-1025PCTthe first available transmission occasion occurs a number of symbols after an end of the PUCCH transmission; andthe number of symbols is based on a subcarrier spacing of the PUCCH resource.

3. The method of claim 2, further comprising receiving one or more radio resource control (RRC) messages comprising one or more CSI report configuration parameters for UE-initiated CSI reporting.

4. The method of claim 3, wherein the one or more CSI report configuration parameters comprise a report transmission mode parameter indicating a transmission mode for the UE-initiated CSI reporting is a second mode in which the CSI report of the UE-initiated CSI reporting is transmitted in PUSCH transmissions of the Type 1 configured uplink grant.

5. The method of claim 4, wherein:a first value of the report transmission mode parameter indicates a first mode for the UE- initiated CSI reporting; anda second value of the report transmission mode parameter indicates a second mode for the UE-initiated CSI reporting.

6. The method of claim 5, wherein the report transmission mode parameter is set to the second value.

7. The method of any one of claims 3 to 6, wherein the one or more CSI report configuration parameters comprise a PUCCH resource configuration indicating the PUCCH resource for PUCCH transmissions, of the UE-initiated CSI reporting, with UEIRI.

8. The method of any one of claims 3 to 7, wherein:the one or more RRC messages comprise one or more configuration parameters of an uplink BWP of a cell; andthe one or more configuration parameters indicate a subcarrier spacing of the uplink BWP.

9. The method of claim 8, wherein the PUCCH resource is on the uplink BWP.

10. The method of any one of claims 8 to 9, wherein the PUCCH resource configuration indicates the PUCCH resource on the uplink BWP for UEIRI.

11. The method of any one of claims 8 to 10, wherein the subcarrier spacing of the PUCCH resource is a subcarrier spacing of the uplink BWP.

12. The method of any one of claims 8 to 11, wherein:the PUSCH transmission is transmitted via a second uplink BWP of a second cell; and a subcarrier spacing of the second uplink BWP, of the second cell, is different from the subcarrier spacing of the PUCCH resource.

13. The method of any one of claims 2 to 12, wherein the CSI report is a UE-initiated CSI report.

14. The method of any one of claims 2 to 13, wherein a PUCCH format of the PUCCH transmission is:PUCCH format 0; orDocket No.: 25-1025PCTPUCCH format 1.

15. The method of any one of claims 2 to 14, further comprising transmitting a capability information message, wherein the capability information message comprises a parameter indicating a minimum number of symbols between the PUCCH transmission and the PUSCH transmission of the Type 1 configured uplink grant.

16. The method of claim 15, wherein the number of symbols is based on the minimum number of symbols indicated by the capability information message.

17. The method of any one of claims 15 to 16, wherein the number of symbols is no less than the minimum number of symbols indicated by the capability information message.

18. The method of any one of claims 15 to 17, wherein the capability information message further comprises at least one of:a first multiplexing parameter indicating whether the wireless device supports multiplexing of a UEIRI and a HARQ-ACK once per subslot when a UE-initiated CSI report and the HARQ-ACK are configured to be sent with different starting symbols in a subslot; ora second multiplexing parameter indicating whether the wireless device supports multiplexing of a UEIRI and a HARQ-ACK once per slot when the UE-initiated CSI report and the HARQ-ACK are configured to be sent with different starting symbols in a slot.

19. The method of any one of claims 2 to 18, further comprising determining, for the PUCCH transmission, a cyclic shift based on:an initial cyclic shift; anda second cyclic shift set to zero.

20. The method of claim 19, wherein one or more RRC messages comprise an initial cyclic shift parameter with a value indicating the initial cyclic shift.

21. The method of any one of claims 19 to 20, wherein the PUCCH transmission is transmitted using a low peak-to-average power ratio (PAPR) sequence associated with the cyclic shift.

22. The method of any one of claims 7 to 21 , wherein the one or more RRC messages indicate indicating a first number of symbols in a PUCCH format of the PUCCH resource.

23. The method of claim 22, further comprising not transmitting a second PUCCH transmission with a second UEIRI in a slot based on a second number of symbols, available for the PUCCH transmission in the slot, being smaller than the first number of symbols.

24. The method of claim 23, wherein:the one or more PUCCH configuration parameters comprise one or more PUCCH format configuration parameters of the PUCCH format; andthe one or more PUCCH format configuration parameter indicate:Docket No.: 25-1025PCTa starting symbol index; andthe first number of symbols.

25. The method of claim 24, wherein the one or more PUCCH format configuration parameters comprise:a starting symbol index parameter indicating the starting symbol index; anda number of symbols parameter indicating the first number of symbols.

26. The method of claim 25 wherein the PUCCH resource configuration indicates a periodicity for the PUCCH transmissions.

27. The method of claim 26, wherein the periodicity is in symbols or slots.

28. The method of any one of claims 26 to 27, further comprising determining, for the PUCCH transmission, a transmission occasion based on:the periodicity; andthe starting symbol index.

29. The method of any one of claims 26 to 28, wherein the PUCCH resource configuration further indicates an offset for the PUCCH transmissions.

30. The method of claim 29, wherein the offset is in slots.

31. The method of any one of claims 29 to 30, wherein:the periodicity is one slot; andthe offset is equal to zero based on the periodicity being one slot.

32. The method of any one of claims 2 to 31 , further comprising:initiating a random-access procedure based on a failure of PUCCH transmissions via a PUCCH resource, wherein the failure is based on a number of PUCCH transmissions via the PUCCH resource being equal to or greater than a maximum transmission count; and transmitting a random-access report, in a UE information response message, for the randomaccess procedure, wherein the random-access report comprises a field, indicating a purpose of triggering the random-access procedure, with a value indicating the failure.

33. The method of claim 32, wherein the value indicates the failure of the PUCCH transmissions with UEIRI.

34. The method of any one of claims 7 to 33, further comprising releasing the PUCCH resource configuration based on performing a medium-access control (MAC) reset.

35. The method of claim 34, further comprising performing the MAC reset based on:an RRC layer of the wireless device requesting a reset of a MAC entity of the wireless device; a deactivation of a secondary cell group (SCG); orperforming RRC reconfiguration with synchronization.

36. The method of any one of claims 2 to 35, wherein UEIRI is different from a scheduling request (SR).Docket No.: 25-1025PCT37. A method comprising:receiving, by a wireless device, one or more radio resource control (RRC) messages comprising:one or more channel state information (CSI) report configuration parameters for userequipment (UE) initiated CSI reporting, wherein the one or more CSI report configuration parameters comprise a physical uplink control channel (PUCCH) resource configuration indicating:a PUCCH resource for PUCCH transmissions, of the UE-initiated CSI reporting, with UE-initiated report indicator (UEIRI); anda periodicity for the PUCCH transmissions; andone or more PUCCH configuration parameters that comprise one or more PUCCH format configuration parameters, wherein the one or more PUCCH format configuration parameters comprise:a starting symbol index parameter indicating a starting symbol index; and a number of symbols parameter indicating a first number of symbols; determining, for a PUCCH transmission with UEIRI, a transmission occasion based on:the periodicity; andthe starting symbol index; andbased on a second number of symbols available for the PUCCH transmission in a slot being smaller than the first number of symbols, not transmitting the PUCCH transmission in the slot.

38. A method comprising:receiving, by a wireless device, one or more radio resource control (RRC) messages comprising:a physical uplink control channel (PUCCH) resource configuration of a PUCCH resource for user equipment (UE) initiated report indicators (UElRIs) in UE-initiated channel state information (CSI) reporting; andone or more PUCCH configuration parameters indicating a first number of symbols in a PUCCH format of the PUCCH resource; andnot transmitting a PUCCH transmission with a UEIRI in a slot based on a second number of symbols, available for the PUCCH transmission in the slot, being smaller than the first number of symbols.

39. The method of claim 38, wherein the one or more RRC messages further comprise one or more CSI report configuration parameters for UE-initiated CSI reporting.

40. The method of claim 39, wherein the one or more CSI report configuration parameters comprise the PUCCH resource configuration.Docket No.: 25-1025PCT41. The method of any one of claims 38 to 40, wherein the one or more CSI report configuration parameters comprise a report transmission mode parameter indicating a transmission mode for the UE-initiated CSI reporting.

42. The method of claim 41, wherein:a first value of the report transmission mode parameter indicates a first mode for the UE- initiated CSI reporting; anda second value of the report transmission mode parameter indicates a second mode for the UE-initiated CSI reporting.

43. The method of claim 42, wherein a CSI report of the UE-initiated CSI reporting is transmitted in:a dynamically scheduled physical uplink shared channel (PUSCH) transmission in the first mode; anda PUSCH transmission of a Type 1 configured uplink grant in the second mode.

44. The method of any one of claims 42 to 43, wherein the PUCCH transmissions of the UE-initiated CSI reporting:requests a dynamically scheduled PUSCH transmission to carry the CSI report for the first mode; andnotifies a PUSCH transmission of a Type 1 configured uplink grant to carry the CSI report for the second mode.

45. The method of any one of claims 43 to 44, wherein the CSI report is a UE-initiated CSI report.

46. The method of any one of claims 38 to 45, wherein a PUCCH format of the PUCCH transmission is:PUCCH format 0; orPUCCH format 1.

47. The method of any one of claims 38 to 46, wherein:the one or more PUCCH configuration parameters comprise one or more PUCCH format configuration parameters of the PUCCH format; andthe one or more PUCCH format configuration parameter indicate:a starting symbol index; andthe first number of symbols.

48. The method of claim 47, wherein the one or more PUCCH format configuration parameters comprise:a starting symbol index parameter indicating the starting symbol index; anda number of symbols parameter indicating the first number of symbols.

49. The method of any one of claims 47 to 48, wherein the one or more PUCCH format configuration parameters are for:PUCCH format 0; orDocket No.: 25-1025PCTPUCCH format 1.

50. The method of any one of claims 38 to 49, wherein:the PUCCH resource configuration indicates a periodicity for the PUCCH transmissions; and the one or more PUCCH configuration parameters indicate a starting symbol index.

51. The method of claim 50, wherein the periodicity is in symbols or slots.

52. The method of any one of claims 50 to 51 , further comprising determining, for the PUCCH transmission, a transmission occasion based on:the periodicity; andthe starting symbol index.

53. The method of any one of claims 50 to 52, wherein the PUCCH resource configuration further indicates an offset for the PUCCH transmissions.

54. The method of claim 53, wherein the offset is in slots.

55. The method of any one of claims 53 to 54, further comprising determining, based on the periodicity being larger than one slot and for a second PUCCH transmission with UEIRI, a second transmission occasion in a second slot in a frame.

56. The method of claim 55, wherein the second slot is based on:a number of the frame;a number of slots in the frame;the offset; andthe periodicity.

57. The method of any one of claims 53 to 56, wherein:the periodicity is one slot; andthe offset is equal to zero based on the periodicity being one slot.

58. 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 57.

59. 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

Images