Downlink reception for beam failure recovery

Abstract

A wireless device transmits a physical random-access channel (PRACH) transmission indicating a candidate reference signal (RS) for a beam failure recovery (BFR). The wireless device monitors a search space set, for the BFR, using quasi-collocation (QCL) parameters of the candidate RS until reception of downlink control information (DCI) indicating a transmission configuration indicator (TCI) state.

Description

Docket No.: 25-1039PCTTITLEDownlink Reception for Beam Failure RecoveryCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 753,629, filed February 4, 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. 1B illustrate example mobile communication networks in which embodiments of the present disclosure may be implemented.

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

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

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

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

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

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

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

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

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

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

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

[0015] FIG. 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-1039PCT

[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] FIG. 17 is a call flow diagram illustrating a procedure that may be used to enable uplink transmission using a TCI state.

[0024] FIG. 18 is a call flow diagram illustrating aspects of beam failure detection and recovery for a cell.

[0025] FIG. 19 is a call flow diagram illustrating aspects of beam failure recovery using a contention- free random-access procedure.

[0026] FIG. 20 is a call flow diagram illustrating aspects of beam failure recovery using a contentionbased random-access procedure.

[0027] FIG. 21 is a call flow diagram illustrating aspects of an embodiment according to the present disclosure.

[0028] FIG. 22 is a flowchart illustrating aspects of a process 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 other than that shown. For example, the actions listed in any flowchart may be re-ordered or only optionally used in some embodiments.Docket No.: 25-1039PCT

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

[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 =Docket No.: 25-1039PCT{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: lEs) may comprise one or more information objects, and an information object may comprise one or more other objects. For example, if parameter (IE) N comprises parameter (IE) M, and parameter (IE) M comprises parameter (IE) K, and parameter (IE) K comprises parameter (information element) J. Then, for example, N comprises K, and N comprises J. In an example embodiment, when one or more messages comprise a plurality of parameters, it implies that a parameter in the plurality of parameters is in at least one of the one or more messages, but does not have to be in each of the one or more messages.

[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 just one of the three possible features, with any two of the three possible features or with three of the three possible features.Docket No.: 25-1039PCT

[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 behavioral ly equivalent. For example, modules may be implemented as a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, MATLAB or the like) or a modeling / simulation program such as Simulink, Stateflow, GNU Octave, or LabVI EWMathScript. 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 as the uplink. Downlink transmissions may be separated from uplink transmissions using frequency divisionDocket No.: 25-1039PCTduplexing (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 (g NB, 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-1039PCTrelay 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. 1A, 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. 1B, mobile communication network 150 includes a 5G core network (5G-CN) 152, an NG-RAN 154, and UEs 156A and 156B (collectively UEs 156). These components may be implemented and operate in the same or similar manner as corresponding components described with respect to FIG. 1A.

[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-1039PCTservices 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. 1B for ease of illustration. The UPF 158B may serve as a gateway between the NG-RAN 154 and the one or more DNs. The UPF 158B may perform functions such as packet routing and forwarding, packet inspection and user plane policy rule enforcement, traffic usage reporting, uplink classification to support routing of traffic flows to the one or more DNs, quality of service (QoS) handling for the user plane (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink traffic verification), downlink packet buffering, and downlink data notification triggering. The UPF 158B may serve as an anchor point for intra- / 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. 1 B 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-1039PCTcommunicating 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-1039PCTnetwork 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. 1 B 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-1039PCT

[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-g NB handover. The PDCPs 214 and 224 may perform packet duplication to improve the likelihood of the packet being received and, at the receiver, remove any duplicate packets. Packet duplication may be useful for services that require high reliability.

[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-1039PCTand / 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-1039PCTchannel 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-1039PCT

[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 (P I), rank indicators (Rl), and scheduling requests (SR); and

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

[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 MAGs 212 and 222, the RLCs213 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-1039PCTestablishing 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-1039PCTUE 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-1039PCTF1 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 (PAPR). 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-1039PCT

[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-1039PCT

[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-1039PCTBWP 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-1039PCTreferred 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-1039PCTscheduling. 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 UCI 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-1039PCTFIG. 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 RSS and the SSS may be transmitted by the base station and used by the UE to synchronize the UE to the base station. The RSS 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.11A). 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 11 A) 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-1039PCTthe 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-1039PCTdownlink 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-1039PCTDMRS 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-1039PCTmaximum 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-1039PCTsets. 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-1039PCTports, a CSI-RS configuration (e.g., symbol and resource element (RE) locations in a subframe), a CSI- RS subframe configuration (e.g., subframe location, offset, and periodicity in a radio frame), a CSI-RS power parameter, a CSI-RS sequence parameter, a code division multiplexing (CDM) type parameter, a frequency density, a transmission comb, quasi co-location (QCL) parameters (e.g., QCL- scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and / or other radio resource parameters.

[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. 11 B (beam #1 , beam #2, and beam #3), more or fewer beams may be configured. Beam #1 may be allocated with CSI-RS 1101 that may be transmitted in one or more subcarriers in an RB of a first symbol. Beam #2 may be allocated with CSI-RS 1102 that may be transmitted in one or more subcarriers in an RB of a second symbol. Beam #3 may be allocated with CSI-RS 1103 that may be transmitted in one or more subcarriers in an RB of a third symbol. By using frequency division multiplexing (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. 11B (e.g., CSI-RS 1101, 1102, 1103) may be transmitted by the base station and used by the UE for one or more measurements. For example, the UE may measure a reference signal received power (RSRP) of configured CSI-RS resources. The base station may configure the UE with a reporting configuration and the UE may report the RSRP measurements to a network (for example, via one or more base stations) based on the reporting configuration. In an example, the base station may determine, based on the reported measurement results, one or more transmission configuration indication (TCI) states comprising a number of reference signals. In an example, the base station may indicate one or more TCI states to the UE (e.g., via RRC signaling, a MAC CE, and / or a DCI). The UE may receive a downlink transmission with a receive (Rx) beam determined based on the one or more TCI states. In an example, the UE may or may not have a capability of beam correspondence. If the UE has the capability of beam correspondence, the UE may determine a spatial domain filter of a transmit (Tx) beam based on a spatial domain filter of the corresponding Rx beam. If the UE does not have the capability of beam correspondence, the UE may perform an uplink beam selection procedure to determine the spatial domain filter of the Tx beam. The UE may perform the uplink beam selection procedure based on one or more sounding reference signal (SRS) resources configured to the UE by the base station. The base station may select and indicate uplink beams for the UE based on measurements of the one or more SRS resources transmitted by the UE.Docket No.: 25-1039PCT

[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 (PMI), 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 U1). Beamforming at the UE may include, e.g., a Tx beam sweep from a set of beams (shown in the bottom rows of U1 and U3 as ovals rotated in a clockwise direction indicated by the dashed arrow). Beamforming at the base station may include, e.g , an Rx beam sweep from a set of beams (shown, in the top rows of U1 and U2, as ovals rotated in a counterclockwise direction indicated by the dashed arrow). Procedure U2 may be used to enable the base station to adjust its Rx beam when the UE uses a fixed Tx beam. The UE and / or the base station may perform procedure U2 using a smaller set of beams than is used in procedure P1 , or using narrower beams than the beams used in procedure P1. This may be referred to as beam refinement The UE may perform procedure U3 to adjust its Tx beam when the base station uses a fixed Rx beam.

[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-1039PCTon 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 RRCJ ONNECTED 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-1039PCTgeneral 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- con fig Dedicated). 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-1039PCTand / 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-1039PCTindicated 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 +s_id + 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-1039PCTin 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 contention-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-1039PCTaddressed 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-1039PCTmay 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-1039PCTThe 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 (T C-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-1039PCT

[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-1039PCTor 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-1039PCTtwo 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-1039PCTin 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-1039PCT

[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-1039PCTsource 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 complex-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-1039PCT

[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] FIG. 17 illustrates a procedure 1700 that may be used to enable uplink transmission, using a TCI state, from a wireless device 1702 to a base station 1704. As shown in FIG. 17, procedure 1700 may include steps 1706, 1708, 1710, and 1712.

[0214] Step 1706 may include base station 1704 transmitting to wireless device 1702 one or more configuration parameters that comprise or indicate a list of TCI states. The one or more configuration parameters may configure wireless device 1702 with the list of TCI states.

[0215] In an implementation, the one or more configuration parameters comprise a higher layer parameter PDSCH-Config. Wireless device 1702 may use the TCI states configured within / by PDSCH- Config to decode a PDSCH according to a detected PDCCH with a DCI intended for wireless device 1702 and a given cell (e.g., a given serving cell, a given non-serving / candidate / target cell). A number of TCI states in the list may depend on a UE capability parameter maxNumberConfiguredTCIstatesPerCC.Docket No.: 25-1039PCTEach TCI state (e.g., TCI-State) may contain / comprise / include / indicate / have respective parameters for configuring a quasi co-location (QCL) relationship between one or more downlink reference signals and DM-RS port(s) of a PDSCH, a DM-RS port of a PDCCH, or CSI-RS port(s) of a CSI-RS resource. The QCL relationship may be configured by a higher layer parameter qcl-Type1 for a first downlink reference signal of the one or more downlink reference signals. The QCL relationship may be configured by a higher layer parameter qcl-Type2 for a second downlink reference signal of the one or more downlink reference signals. When two downlink reference signals comprising a first downlink reference signal and a second downlink reference signal are indicated by a TCI state, QCL types of the two downlink reference signals may not be the same, regardless of whether the first downlink reference signal and the second downlink reference signal are the same or different. A QCL type corresponding to a downlink reference signal of the one or more downlink reference signals may be given by a higher layer parameter qcl-Type in a higher layer parameter QCL-Info and may take one of the following values:

[0216] 'typeA': {Doppler shift, Doppler spread, average delay, delay spread}

[0217] 'typeB1: {Doppler shift, Doppler spread}

[0218] 'typeC: {Doppler shift, average delay}

[0219] 'typeD': {Spatial Rx parameter}

[0220] In an implementation, the one or more configuration parameters comprise a higher layer parameter dl-OrJointTCI-StateList, which may be comprised in PDSCH-Config. dl-OrJointTCI-StateList may comprise or indicate up to 128 TCI-State configurations, for example. A TCI state in the list of TCI states may provide / indicate a reference signal for a QCL for I) a DM-RS of a PDSCH, II) a DM-RS of a PDCCH in a BWP / cell, and / or iii) a CSI-RS. A TCI state in the list of TCI states may provide / indicate a reference signal for determining an uplink transmission spatial filter for I) a dynamic-grant PUSCH, ii) a configured-grant based PUSCH, iii) a PUCCH resource in a BWP / cell, and / or, iv) an SRS.

[0221] In an implementation, the one or more configuration parameters comprise a higher layer parameter ul-TCI-StateList, which may be comprised in the parameter BWP-UplinkDedicated. ul-TCI- StateList may comprise or indicate up to 64 TCI-UL State configurations. A TCI state (e.g., TCI-UL-State or a TCI state configuration) in the list of TCI states may contain / include / have / provide / comprise a parameter for configuring a reference signal, if applicable, for determining uplink transmission spatial filter for I) dynamic-grant PUSCH transmissions, II) configured-grant based PUSCH transmissions, iii) PUCCH transmissions via a PUCCH resource in a cell, and SRS transmissions.

[0222] The one or more configuration parameters transmitted, in step 1706, by base station 1704 may, additionally or alternatively, comprise configuration parameters for use by wireless device 1702 for one or more PUSCH transmission(s) to base station 1704. In an implementation, the configuration parameters may comprise a higher layer parameter applylndicatedTCIState. The parameterDocket No.: 25-1039PCTapplylndicatedTCIState may be set to the value ‘first’ or 'second'. Further details regarding the use of the configuration parameters by wireless device 1702 for a PUSCH transmission are provided below with reference to step 1712.

[0223] The one or more configuration parameters transmitted, in step 1706, by base station 1704 may, additionally or alternatively, comprise configuration parameters for use by wireless device 1702 for one or more configured uplink grants. In an implementation, the configuration parameters may comprise a higher layer parameter applylndicatedTCIState. The parameter applylndicatedTCIState may be set to the value ‘first’, 'second', or ‘both’. Further details regarding the use of the configuration parameters by wireless device 1702 for a configured uplink grant are provided below with reference to step 1712.

[0224] The one or more configuration parameters transmitted, in step 1706, by base station 1704 may, additionally or alternatively, comprise configuration parameters for application by wireless device 1702 to one or more SRS resource sets. In an implementation, the configuration parameters may comprise a higher layer parameter applylndicatedTCIState. The parameter applylndicatedTCIState may be set to the value ‘first’ or ‘second’. Further details regarding the use of the configuration parameters by wireless device 1702 for an SRS resource are provided below with reference to step 1712.

[0225] The one or more configuration parameters transmitted, in step 1706, by base station 1704 may, additionally or alternatively, comprise configuration parameters for use by wireless device 1702 for one or more PUCCH transmission(s) to base station 1704. In an implementation, the configuration parameters may comprise a higher layer parameter applylndicatedTCIState. The applylndicatedTCIState may be set to the value ‘first’ or ‘second’. Further details regarding the use of the configuration parameters by wireless device 1702 for a PUCCH transmission are provided below with reference to step 1712.

[0226] Returning to FIG. 17, step 1708 may include base station 1704 transmitting a control / activation command (e.g., DCI, MAC-CE) to wireless device 1702. The control / activation command may indicate a first TCI state and a second TCI state of the list of TCI states. The first / second TCI state may be a joint TCI state or an UL TCI state, depending on the list of TCI states Idl-GrJointTCI-StateList or ul-TCI- StateLisf) configured in step 1706. The control / activation command may comprise one or more parameter TCI-State(s) or TCI-UL-State(s) indicating the first TCI state and the second TCI state.

[0227] The control / activation command may be used to map up to a number of TCI states and / or pairs of TCI states (e.g., up to 8 TCI states and / or pairs of TCI states), with one TCI state fordownlink channels / signals and / or one TCI state for uplink channels / signals, to codepoint(s) of a DCI field 'Transmission Configuration Indication' for one cell or for a set of cells / downlink BWPs, and / or up to a number of sets of TCI states (e.g., up to 8 sets of TCI states). Each set of the number of sets may be comprised of up to a number of TCI state(s) for downlink and uplink signals / channels (e.g., up to twoDocket No.: 25-1039PCTTCI state(s)), or up to a number of TCI state(s) (e.g., up to two TCI state(s)) for downlink channels / signals and up to a number of TCI state(s) (e.g., up to two TCI state(s)) for uplink channels / signals to codepoint(s) of a DCI field 'Transmission Configuration Indication' for one cell or for a set of cel Is / down II nk BWPs, and if applicable, for one cell or for a set of cells / u plin k BWPs. When a set of TCI state IDs are activated, by the activation command, for a set of cells / downlink BWPs and if applicable, for a set of cells / uplink BWPs, where the applicable list of cells may be determined, by wireless device 1702, by an indicated cell in the activation command, the (same) set of TCI state IDs may be applied by wireless device 1702 to / for all downlink and / or uplink BWPs in the indicated cells (or the applicable list of cells). If the activation command maps TCI-State(s) and / or TCI-UL-State(s) to only one (or to a single) TCI codepoint, wireless device 1702 may apply the (indicated) TCI-State(s) and / or TCI-UL-State(s) to one cell or to a set of cells / downlink BWPs, and if applicable, to one cell or to a set of cells / uplink BWPs once the indicated mapping for the one single T Cl codepoint is applied by the wireless device.

[0228] When wireless device 1702 supports two TCI states in a codepoint of the DCI field 'Transmission Configuration Indication', wireless device 1702 may receive an activation command (e.g., MAC-CE, DCI) used to map up to 8 combinations of one or two TCI states to codepoint(s) of the DCI field 'Transmission Configuration Indication' Wireless device 1702 may not expect to receive more than 8 TCI states in the activation command.

[0229] In an example, when a parameter tci-PresentlnDCI (of the one or more configurations parameters) is set as ‘enabled’ or a parameter tci-PresentDCI-1-2 (of the one or more configuration parameters) is configured for a CORESET, the DCI transmitted in step 1708 (e.g., DCI format 1_1 / 1_2) may provide / indicate TCI state(s) (e.g., TCI-State(s) and / or TCI-UL-State(s)) for a cell or for all cells in a cell list configured by a simultaneous TCI update parameter (e.g., simultaneousU-TCI-UpdateList1 , simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3, simultaneousU-TCI-UpdateList4). The DCI format may be with or without a downlink assignment. The simultaneous TCI update parameter may be a higher layer parameter (e.g., RRC parameter).

[0230] When wireless device 1702 transmits an uplink transmission (e.g., a PUCCH transmission, a PUSCH transmission) with a positive HARQ-ACK corresponding to the DCI providing / indicating the indicated TCI state(s) (e.g., TCI-State(s) and / or TCI-UL-State(s)), and if the indicated TCI State(s) is / are different from previously indicated TCI state(s), the indicated TCI State(s) may be applied, by wireless device 1702, starting from a first / starting / earliest slot that is at least a number of symbols after the last symbol of the uplink transmission. The first / starting / earliest slot and the number of symbols may be both determined, by wireless device 1702, based on an active BWP with the smallest subcarrier spacing among BWP(s) of the cells applying the indicated TCI-State(s) that are active at the end of the uplinkDocket No.: 25-1039PCTtransmission carrying / with the positive HARQ-ACK. The number of symbols may be indicated / provided to wireless device 1702 by RRC messages (e.g one or more configuration parameters).

[0231] Returning to FIG. 17, step 1710 may include base station 1704 transmitting a DCI to wireless device 1702. The DCI may indicate one or more TCI states of the one or more TCI states indicated by the control command (e.g., the first TCI state and the second TCI state).

[0232] Step 1712 may include wireless device 1702 transmitting an uplink transmission to base station 1704. The uplink transmission may be in response to the DCI received in step 1710. In another operation, the uplink transmission may not be in response to the DCI. For example, procedure 1700 may not include step 1710.

[0233] In an example, the DCI transmitted in step 1710 may be a DCI format 0_0 that schedules or activates a PUSCH transmission for wireless device 1702. In response, wireless device 1702 may transmit the PUSCH transmission for the uplink transmission in step 1712. Wireless device 1702 may apply the first TCI state indicated by the control / activation command for the PUSCH transmission.

[0234] In an example, wireless device 1702 may be configured, by base station 1704, with a configured grant Type 1 for a PUSCH transmission. As mentioned above, wireless device 1702 may also be configured with a higher layer parameter applylndicatedTCIState for use for one or more configured uplink grants. Wireless device 1702 may transmit the PUSCH transmission for the uplink transmission in step 1712. Wireless device 1702 may use the parameter applylndicatedTCIState as follows for the PUSCH transmission:If the higher layer parameter applylndicatedTCIState is set to ‘first’, wireless device 1702 may apply the first TCI state to the PUSCH transmission. Wireless device 1702 may apply the first TCI state to each PUSCH transmission occasion of the PUSCH transmission.- If the higher layer parameter applylndicatedTCIState is set to 'second', wireless device 1702 may apply the second TCI state to the PUSCH transmission. Wireless device 1702 may apply the second TCI state to each PUSCH transmission occasion of the PUSCH transmission.- If the higher layer parameter applylndicatedTCIState is set to 'both', wireless device 1702 may apply both of the first and second TCI states to the PUSCH transmission. In an implementation, wireless device 1702 may apply:o the first TCI state to PUSCH transmission occasion(s) or PUSCH antenna port(s), of the PUSCH transmission, associated with a first SRS resource set for codebook / non-codebook transmission, and o the second TCI state to PUSCH transmission occasion(s) or PUSCH antenna port(s), of the PUSCH transmission, associated with a second SRS resource set for codebook / non-codebook transmission.Docket No.: 25-1039PCT- If wireless device 1702 is configured / indicated, by base station 1704, by a higher layer parameter PDCCH-Config that contains / comprises two different values of a higher layer parameter coresetPoollndex in different ControlResourceSets, the first TCI state and the second TCI state may be specific to a higher layer parameter coresetPoollndex with value 0 and a higher layer parameter coresetPoollndex with value 1, respectively. If wireless device 1702 is configured / indicated, by base station 1704, by a higher layer parameter PDCCH-Config that contains / comprises two different values of a higher layer parameter coresetPoollndex in different ControlResourceSets, the higher layer parameter applylndicatedTCIState may not be set to ‘both’ indicating both of the two indicated TCI states to be applied for the PUSCH transmission.

[0235] Wireless device 1702 may be configured with two SRS resource sets. When two SRS resource sets are configured in a higher layer parameter srs-ResourceSetToAddModLlst or a higher layer parameter srs-ResourceSetToAddModListDCI-0-2 with a higher layer parameter usage in SRS- ResourceSet set to 'codebook' or 'nonCodebook' and a higher layer parameter enableSTx2PofmDCI is configured and a higher layer parameter PDCCH-Config contains / comprises two different values of coresetPoollndex in a higher layer parameter ControlResourceSet for the active BWP of a serving cell, two PUSCH transmissions that are fully / partially overlapping in time domain and are fully / partially / non-overlapping in frequency domain may be dynamically scheduled by UL grant(s) in DCI(s) and / or scheduled by configured grant(s) Type 1 or Type 2,if dynamically scheduled by UL grant(s) in DCI(s) or activated by DCI(s) for configured grant Type 2, the DCI field SRS Resource Set Indicator may not be present in each PDCCH,two PUSCH transmissions may be associated to different values of coresetPoollndex where for configured grant Type 1 , the association may be based on a higher layer parameter srs-ResourceSetld in a higher layer parameter rrc-ConfiguredUplinkGrant that indicates either the first SRS resource set or the second SRS resource set of the two SRS resource sets with usage 'codebook' or 'nonCodeBook' in the higher layer parameter srs-ResourceSetToAddModList or the higher layer parameter srs-ResourceSetToAddModListDCI-0-2,wireless device 1702 may not be expected to be configured with different number of SRS resources in the two SRS resource sets,wireless device 1702 may expect a higher layer parameter maxNrofPorts in PTRS-UplinkConfig to be configured as one if UL PT-RS is configured.

[0236] In an example, the one or more configuration parameters transmitted in step 1706 by base station 1704 may comprise a higher layer parameter rrc-ConfiguredUplinkGrant that configures PUSCH transmission occasion(s) of a configured grant Type 1. When wireless device 1702 is configured with the higher layer parameter dl-OrJointTCI-StateList or TCI-UL-State, as described above, and two SRSDocket No.: 25-1039PCTresource sets are configured, e.g., in a higher layer parameter srs-ResourceSetToAddModList or a higher layer parameter srs-ResourceSetToAddModListDCI-0-2w'\Vn a higher layer parameter usage in SRS-ResourceSet set to 'codebook' or 'noncodebook', and a higher layer parameter multipanelScheme is set to ‘SDMscheme’ or 'SFNscheme', and the higher layer parameter rrc-ConfiguredUplinkGrant of the configured grant Type 1 does not contain srs-Resourcelndicator2 or precodingAndNumberOfLayers2, PUSCH transmission occasion(s) of the configured grant Type 1 may be associated with the first SRS resource set of the two SRS resource sets if the first TCI state (indicated in the control / activation command) applies to the configured grant Type 1 (e.g., when the higher layer parameter applylndicatedTCIState = ‘first") and may be associated with the second SRS resource set of the two SRS resource sets if the second TCI state (indicated in the control / activation command) applies to the configured grant Type 1 (e.g., when the higher layer parameter applylndicatedTCIState = ‘second).

[0237] In an example, the DCI transmitted in step 1710 by base station 1704 may be a DCI format 0_1 or 0_2 that schedules or activates PUSCH transmission occasion(s). When wireless device 1702 is configured with the higher layer parameter dl-OrJointTCI-StateList or TCI-UL-State and has the first and second TCI states indicated / activated as described above, and only one SRS resource set is configured in a higher layer parameter srs-ResourceSetToAddModList or a higher layer parameter srs- ResourceSetToAddModListDCI-0-2vj\Vn a higher layer parameter usage in SRS-ResourceSet set to 'codebook' or 'noncodebook', the PUSCH transmission occasion(s) scheduled or activated by the DCI in step 1710 may be associated with the first TCI state or may be associated with the second TCI state, as indicated by a higher layer parameter applylndicatedTCIState configured by a higher layer parameter PUSCH-Config. When the higher layer parameter applylndicatedTCIState is set to 'first', wireless device 1702 may transmit d, in / via the scheduled / activated PUSCH transmission occasion(s), a PUSCH transmission (or repetitions of a PUSCH transmission) using the first TCI state. When the higher layer parameter applylndicatedTCIState is set to ‘second’, wireless device 1702 may transmit in step 1712 for the uplink transmission, in / via the PUSCH transmission occasion(s), a PUSCH transmission (or repetitions of a PUSCH transmission) using the second TCI state. The higher layer parameter applylndicatedTCIState may indicate if wireless device 1702 applies the first or the second "indicated" UL TCI state or joint TCI state for a PUSCH transmission scheduled or activated by DCI format 0_1 / 0_2, for example, when an SRS resource set indicator field is not present (or is absent) in DCI format 0_1 / 0_2.

[0238] When wireless device 1702 is configured with a higher layer parameter enableSTx2PofmDCI and a higher later parameter PDCCH-Config contains two different values of coresetPoollndex in ControlResourceSet for the active BWP of a serving cell, wireless device 1702 may be expected to beDocket No.: 25-1039PCTconfigured with two SRS resource sets with a higher layer parameter usage set to ‘codebook’ or ‘nonCodeBook’ in a higher layer parameter srs-ResourceSetToAddModList. If wireless device 1702 is configured to monitor DCI format 0_2 and there is only one SRS resource set configured by a higher layer parameter srs-ResourceSetToAddModListDCI-0-2 and associated with a higher layer parameter usage set to 'codebook' or 'nonCodeBook', wireless device 1702 may monitor only coresetPoollndex configured with value 0 for detection of DCI format 0_2. The higher layer parameter enableSTx2PofmDCI may be (or may be interchangeably used with) a higher layer parameter stx2- Panel.

[0239] The higher layer parameter enableSTx2PofmDCI may enable PUSCH+PUSCH multiple panel simultaneous uplink transmission in multi-DCI based multi-transmission and reception point (mTRP) system (e.g., each TRP transmits a DCI scheduling a PDSCH / PUSCH / SRS transmission). When the higher layer parameter enableSTx2PofmDCI is configured, two coresetPoollndex values are configured and two SRS resource sets for codebook or non-codebook are configured, the multi-DCI based STxMP PUSCH+PUSCH may be configured.

[0240] The one or more configuration parameters in step 1706 may comprise a higher layer parameter multipanelScheme. When the higher layer parameter multipanelScheme is set to ‘SDMScheme’ and two SRS resource sets are configured / indicated, by base station 1704, e.g., in a higher layer parameter srs-ResourceSetToAddModList or a higher layer parameter srs- ResourceSetToAddModListDCI-0-2 with a higher layer parameter usage in a higher layer parameter SRS-ResourceSet set to 'codebook', two SRS resource indicators (SRIs) and two transmitted precoding matrix indicators (TPMIs) may be given / provided / indicated by two SRS resource indicator fields and two Precoding-information-and-number-of-layers fields for / in a DCI format 0_1 and a DCI format 0_2 (e.g., in the DCI transmitted in step 1710):- When codepoint “10” of SRS Resource Set indicator \s indicated in the DCI format 0_1 / 0_2: o a first TPMI of the two TPMIs may indicate a transmission precoder for the uplink transmission to be applied over layers {0...vi-1}, where Vi is a number of layers indicated by the first TPMI, that corresponds to an SRS resource selected by a first SRI of the two SRSs when multiple SRS resources are configured for a first SRS resource set or if single SRS resource is configured for the first SRS resource set, ando a second TPMI of the two TPMIs may indicate a transmission precoder for the uplink transmission to be applied over layers {vi.... V2+V1-I}, where V2 is a number of layers indicated by the second TPMI, that corresponds to an SRS resource selected by a second SRI of the two SRIs when multiple SRS resources are configured for a second SRS resource set or if single SRS resource is configured for the second SRS resource set, vi maxRankSdm and V2 s maxRankSdm or maxRankSdmDCI-0-2 and maxRankSdm orDocket No.: 25-1039PCTmaxRankSdmDCI-0-2 may define the maximum number of layers applied over the first SRS resource set and the second SRS resource sets, separately.- When codepoint “00” or “01” of SRS Resource Set indicator is indicated in the DCI format 0_1 / 0_2, the second SRI and second TPM I may be reserved, and the first TPM I may indicate a precoder to be applied over layers {0... v-1 }, where v maxRank, where maxRank may define the maximum number of layers.Codepoint “11” of SRS Resource Set indicator in the DCI format 0_1 / 0_2 may be reserved.- For one or two TPM Is, the transmission precoder may be selected from an uplink codebook that has a number of antenna ports equal to a higher layer parameter nrofSRS-Ports in a higher layer parameter SRS-Config for the indicated SRI(s). When two TPMIs are indicated, wireless device 1702 may expect that the precoder indicated by the first TPM I and the precoder indicated by the second TPM I are mapped to different PUSCH antenna ports.- When two SRIs are indicated, wireless device 1702 may expect that the number of SRS antenna ports associated with two indicated SRIs is the same. When wireless device 1702 is configured / indicated with a higher layer parameter txConfig set to 'codebook1, wireless device 1702 may be configured / indicated with at least one SRS resource. Each of the indicated one or two SRIs in slot n may be associated with the most recent transmission of an SRS resource, in associated SRS resource set, identified by an SRI of the two SRIs, where the SRS resource is prior to a PDCCH reception with the DCI format 0_1 / 0_2 carrying the SRI. When two SRS resource sets are configured / indicated in a higher layer parameter srs-ResourceSetToAddModList or a higher layer parameter srs-ResourceSetToAddModListDCI-0-2 with a higher layer parameter usage in a higher layer parameter SRS-ResourceSet set to 'codebook', wireless device 1702 may not be expected to be configured with a different number of SRS resources in the two SRS resource sets.

[0241] When the higher layer parameter multipanelScheme is set to ‘SFNScheme’ and two SRS resource sets are configured / indicated, by base station 1704, in a higher layer parameter srs- ResourceSetToAddModList or a higher layer parameter srs-ResourceSetToAddModListDCI-0-2 with a higher layer parameter usage in a higher layer parameter SRS-ResourceSet set to 'codebook', two SRIs and two TPMIs may be given / provided / indicated by two SRS resource indicator fields and two Precoding-information-and-number-of-layers fields for / in a DCI format 0_1 and a DCI format 0_2 (e.g., in the DCI transmitted in step 1710):- When codepoint “10” of SRS Resource Set indicator is indicated in the DCI format 0_1 / 0_2 (e.g., in the DCI transmitted in step 1710):Docket No.: 25-1039PCTo a first TPMI of the two TPMIs may indicate a transmission precoder to be applied over layers {0...V-1}, and a second TPMI of the two TPMIs may indicate a transmission precoder to be applied over layers {0... v-1 }, where v < maxRankSfn or maxRankSfnDCI-0-2 and maxRankSfn or maxRankSfnDCI-0-2 may define the maximum number of layers applied over the first SRS resource set and the second SRS resource sets, separately.When codepoint “00” or “01” of SRS Resource Set indicators indicated in the DCI format 0_1 / 0_2, the second SRI and second TPMI may be reserved, and the first TPMI may indicate a precoder to be applied over layers {0.. v-1}, where v < maxRank, where maxRank may define the maximum number of layers.- Codepoint “11” of SRS Resource Set indicator in the DCI format 0_1 / 0_2 may be reserved.For one or two TPMIs, the transmission precoder may be selected from an uplink codebook that has a number of antenna ports equal to a higher layer parameter nrofSRS-Ports in a higher layer parameter SRS-Config for the indicated SRI(s). When two TPMIs are indicated, the UE may expect that the precoder indicated by the first TPMI and the precoder indicated by the second TPMI are mapped to different PUSCH antenna ports.- When two SRIs are indicated, wireless device 1702 may expect that the number of SRS antenna ports associated with two indicated SRIs is the same. When wireless device 1702 is configured / indicated with a higher layer parameter txConfig set to 'codebook', wireless device 1702 may be configured / indicated with at least one SRS resource. Each of the indicated one or two SRIs in slot n may be associated with the most recent transmission of an SRS resource, in associated SRS resource set, identified by an SRI of the two SRIs, where the SRS resource is prior to a PDCCH reception with the DCI format 0_1 / 0_2 carrying the SRI. When two SRS resource sets are configured / indicated in a higher layer parameter srs-ResourceSetToAddModList or a higher layer parameter srs-ResourceSetToAddModListDCI-0-2 with a higher layer parameter usage in a higher layer parameter SRS-ResourceSet set to 'codebook', wireless device 1702 may not be expected to be configured with a different number of SRS resources in the two SRS resource sets.

[0242] When the higher layer parameter multipanelScheme is set to ‘SDMScheme’ and two SRS resource sets are configured / indicated, by base station 1704, in a higher layer parameter srs- ResourceSetToAddModList or a higher layer parameter srs-ResourceSetToAddModListDCI-0-2 with a higher layer parameter usage in a higher layer parameter SRS-ResourceSet set to 'nonCodebook', two SRIs may be given / provided / indicated by two SRS resource indicator fields for / in a DCI format 0_1 and a DCI format 0_2 (e.g., in the DCI transmitted in step 1710) :When codepoint “10” of SRS Resource Set indicators indicated in the DCI format 0_1 / 0_2:Docket No.: 25-1039PCTo a first SRI of the two SRIs may indicate resource(s) to be associated with layers {0... vi-1}, where Vi is a number of layers indicated by the first SRI and a second SRI of the two SRIs may indicate resource(s) to be associated with layers {vi .... V2+V1-I}, Vi < .max and V2 s Lmax. The UE may expect that SRS resource(s) indicated by the first SRI and SRS resource(s) indicated by the second SRI are corresponding to different PUSCH antenna ports.When codepoint “00” or “01” of SRS Resource Set indicators indicated in the DCI format 0_1 / 0_2, the second SRI may be reserved, and the first SRI may indicate resource(s) associated with layers {0...V-1}, where v < Lmax.

[0243] When the higher layer parameter multipanelScheme is set to ‘SFNScheme’ and two SRS resource sets are configured / indicated, by base station 1704, in a higher layer parameter srs-ResourceSetToAddModList or a higher layer parameter srs-ResourceSetToAddModListDCI-0-2 with a higher layer parameter usage in a higher layer parameter SRS-ResourceSet set to 'nonCodebook', two SRIs may be given / provided / indicated by two SRS resource indicator fields for / in a DCI format 0_1 and a DCI format 0_2 (e.g., in the DCI transmitted in step 1710):When codepoint “10” of SRS Resource Set indicators indicated in the DCI format 0_1 / 0_2: o a first SRI of the two SRIs may indicate resource(s) to be associated with layers {0... v-1 } and a second SRI of the two SRIs may indicate resource(s) to be associated with layers {0... v-1 }, v < Lmax. The UE may expect that SRS resource(s) indicated by the first SRI and SRS resource(s) indicated by the second SRI are corresponding to different PUSCH antenna ports.When codepoint “00” or “01” of SRS Resource Set indicators indicated in the DCI format 0_1 / 0_2, the second SRI may be reserved, and the first SRI may indicate resource(s) associated with layers {0...V-1}, where v Lmax. When two SRIs are indicated, wireless device 1702 may expect that the number of SRS antenna ports associated with two indicated SRIs to be the same.When wireless device 1702 is configured / indicated with a higher layer parameter txConfig set to 'nonCodebook', wireless device 1702 may be configured / indicated with at least one SRS resource. Each of the indicated one or two SRIs in slot n may be associated with the most recent transmission of an SRS resource, in associated SRS resource set, identified by an SRI of the two SRIs, where the SRS resource is prior to a PDCCH reception with the DCI format 0_1 / 0_2 carrying the SRI. When two SRS resource sets are configured / indicated in a higher layer parameter srs-ResourceSetToAddModList or a higher layer parameter srs-ResourceSetToAddModListDCI-0-2 with a higher layer parameter usage in a higher layer parameter SRS-ResourceSet set to 'nonCodebook', wireless device 1702 may not be expected to be configured with a different number of SRS resources in the two SRS resource sets.Docket No.: 25-1039PCT

[0244] In an example, the DCI transmitted in step 1710 by base station 1704 may be a DCI format 0_1 or 0_2 that schedules or activates PUSCH transmission occasion(s). When wireless device 1702 is configured / indicated, by base station 1704, with the higher layer parameter dl-OrJointTCI-StateList or the higher layer parameter TCI-UL-State and has the first and second TCI states indicated / activated as described above, and two SRS resource sets are configured / indicated, by base station 1704, in a higher layer parameter srs-ResourceSetToAddModList or a higher layer parameter srs- ResourceSetToAddModListDCI-0-2 with a higher layer parameter usage in a higher layer parameter SRS-ResourceSet set to 'codebook' or 'nonCodebook', for a PUSCH repetition Type A or Type B, or for a PUSCH transmission when the higher layer parameter multipanelScheme is set to 'SDMscheme' or 'SFNscheme', the association of the first TCI state and the second TCI state to PUSCH transmission occasions or to corresponding PUSCH antenna ports may be determined as follows:if the DCI format 0_1 or a DCI format 0_2 indicates codepoint “00” or “01” for an SRS resource set indicator, the first TCI state or the second TCI state may be applied, by wireless device 1702, to all PUSCH transmission occasions, respectively.if the DCI format 0_1 or a DCI format 0_2 indicates codepoint “10” or “11" for an SRS resource set indicator, and the higher layer parameter multipanelScheme is not configured,o the first TCI state may be applied, by wireless device 1702, to PUSCH transmission occasion(s) associated with a first SRS resource set of the two SRS resource sets and the second TCI state may be applied to PUSCH transmission occasion(s) associated with a second SRS resource set of the SRS resource sets, where the association of PUSCH transmission occasions to the two SRS resource sets may be determined based on whether a higher layer parameter cyclicMapping or a higher layer parameter sequentialMapping in a higher layer parameter PUSCH-Config is enabled.- if the DCI format 0_1 or a DCI format 0_2 indicates codepoint “10” for an SRS resource set indicator and the higher layer parameters multipanelScheme is configured and set to ‘SDMscheme’ or 'SFNscheme',o the first TCI state may be applied, by wireless device 1702, to first PUSCH antenna port(s), of a PUSCH transmission occasion, associated with the first SRS resource set, and the second TCI state may be applied, by wireless device 1702, to second PUSCH antenna port(s), of the PUSCH transmission occasion, associated with the second SRS resource set. The first PUSCH antenna port(s) and the second PUSCH antenna port(s) may be the same or different.

[0245] In an example, the DCI transmitted in step 1710 may schedule a PUSCH transmission and may comprise an SRS Resource Set Indicator field. In response, wireless device 1702 may transmit theDocket No.: 25-1039PCTPUSCH transmission for the uplink transmission in step 1712. Wireless device 1702 may apply a TCI state indicated by the SRS Resource Set Indicator field for the PUSCH transmission.

[0246] When wireless device 1702 transmits repetitions of a PUSCH transmission over / across K slots (e.g., K consecutive slots) and K = 2, the first and second SRS resource sets may be applied, by wireless device 1702 and / or base station 1704. to the first and second slot of 2 slots, respectively.

[0247] When wireless device 1702 transmits repetitions of a PUSCH transmission over / across K slots (e.g., K consecutive slots) > 2 slots, and when the higher layer parameter mappingPattern = 'cyclicMapping', the first and second SRS resource sets may be applied, by wireless device 1702 and / or base station 1704, to the first and second slot of K slots, respectively, and the same SRS resource set mapping pattern may continue to the remaining slots of K slots.

[0248] When wireless device 1702 transmits repetitions of a PUSCH transmission over / across K slots (e.g., K consecutive slots) > 2 slots, and when the higher layer parameter mappingPattern = ‘sequentialMapping’, the first SRS resource set may be applied, by wireless device 1702 and / or base station 1704, to the first and second slots of K slots, and the second SRS resource set may be applied, by wireless device 1702 and / or base station 1704, to the third and fourth slot of K slots, and the same SRS resource set mapping pattern may continue to the remaining slots of K slots.

[0249] As mentioned above, the one or more configuration parameters transmitted, in step 1706, by base station 1704 may comprise configuration parameters for application by wireless device 1702 to one or more SRS resource sets. The configuration parameters may comprise a higher layer parameter applylndicatedTCIState. In an example, when wireless device 1702 is configured / indicated / provided with the higher layer parameter di-OrJointTCI-StateList or the higher layer parameter TCI-UL-State and has the first and second TCI states indicated / activated as described above, the higher layer parameter applylndicatedTCIState may indicate whether wireless device 1702 applies the first TCI state or the second TCI state to the one or more SRS resource sets. The one or more SRS resource sets may comprise a periodic, semi-persistent or aperiodic SRS resource set with a higher layer parameter usage, in SRS-ResourceSet, set to ‘codebook', ‘nonCodebook or ‘antennaSwitching' or an aperiodic SRS resource set with a higher layer parameter usage, in SRS-ResourceSet, set to ‘beamManagemenf. In an implementation, when wireless device 1702 is configured / indicated / provided by a higher layer parameter PDCCH-Config that contains two different values of a higher layer parameter coresetPoollndex in a higher layer parameter ControlResourceSet, the first TCI state and second TCI state correspond to the indicated TCI states (or uplink TCI states) specific to a higher layer parameter coresetPoollndex with value 0 and a higher layer parameter coresetPoollndex with value 1 , respectively.

[0250] When two SRS resource sets comprising a first SRS resource set and a second SRS resource with a higher layer parameter usage in a higher layer parameter SRS-ResourceSet set to 'codebook' orDocket No.: 25-1039PCT‘nonCodebook' are configured / indicated / provided , wireless device 1702 may not expect that the first TCI state be applied to the second SRS resource set and that the second TCI state be applied to the first SRS resource set.

[0251] In another example, the configuration parameters may not comprise the higher layer parameter applylndicatedTCIState for the one or more SRS resource sets. When wireless device 1702 is configured / indicated / provided by / with a higher layer parameter PDCCH-Config that contains / comprises two different values of a higher layer parameter coresetPoollndex in a higher layer parameter ControlResourceSet, and is not configured / indicated / provided with the higher layer parameter applylndicatedTCIState for an aperiodic SRS resource set, if the aperiodic SRS resource set is triggered by PDCCH on a CORESET associated with a coresetPoollndex value, wireless device 1702 may apply, to the aperiodic SRS resource set, an indicated TCI state (or uplink TCI state) specific to the coresetPoollndex value.

[0252] As mentioned above, the one or more configuration parameters transmitted, in step 1706, by base station 1704 may comprise configuration parameters for use by wireless device 1702 for one or more PUCCH transmission(s) to base station 1704. The configuration parameters may comprise a higher layer parameter applylndicatedTCIState. The higher layer parameter applylndicatedTCIState may indicate whether wireless device 1702 applies the first TCI state, the second TCI state, or both to a PUCCH resource. In an implementation, if the higher layer parameter applylndicatedTCIState is set to 'first', wireless device 1702 may transmit for the uplink transmission in step 1712, via the PUCCH resource, a PUCCH transmission with / using a spatial domain filter corresponding to the first TCI state. If the higher layer parameter applylndicatedTCIState is set to ‘second’, wireless device 1702 may transmit for the uplink transmission in step 1712, via the PUCCH resource, a PUCCH transmission with / using a spatial domain filter corresponding to the second TCI state. If the higher layer parameter applylndicatedTCIState is set to ‘both’, wireless device 1702 may transmit for the uplink transmission in step 1712, via the PUCCH resource, a PUCCH transmission with / using a spatial domain filter corresponding to the first TCI state and a spatial domain filter corresponding to the second TCI state.

[0253] If wireless device 1702- is not provided with a higher layer parameter coresetPoollndex or is provided with a higher layer parameter coresetPoollndex with a value of 0 for first CORESETs on an active downlink BWP of a cell, and - is provided with a higher layer parameter coresetPoollndex with a value of 1 for second CORESETs on the active downlink BWP of the cello the first TCI state and the second TCI state may be specific to the first CORESETs (or to the higher layer parameter coresetPoollndex with a value of 0) and the second CORESETs (or to the higher layer parameter coresetPoollndex with a value of 1), respectively.Docket No.: 25-1039PCT

[0254] Wireless device 1702 may be indicated, by base station 1704, to transmit a PUCCH transmmission over a number of slots (e.g., Np^ccHslots) using / via a PUCCH resource. If the PUCCH resource is indicated by a DCI format (e.g., via the DCI transmitted by base station 1704 in step 1710) and the PUCCH resource includes (or is configured with) a higher layer parameter pucch- RepetitionNrof Slots, the number of slots may be indicated by the higher layer parameter pucch- RepetitionNrofSIots. If the PUCCH resource is not indicated by a DCI format or the PUCCH resource does not include (or is not configured with) a higher layer parameter pucch-RepetitionNrofSIots, the number of slots may be indicated by a higher layer parameter nrofSIots.

[0255] When a PUCCH resource used for repetitions of a PUCCH transmission by wireless device 1702 includes a first TCI state and a second TCI state (e.g., applylndicatedTCI State = 'both’) and wireless device 1702 is not provided a higher layer parameter multipanelSfnScheme, wireless device 1702uses the first TCI state and the second TCI state for first and second repetitions of the PUCCH transmission, respectively, when the number of slots (e.g., / Vp^QHslots) is equal to two,alternates between the first TCI state and the second TCI state per Wp*cChHrepetitions of the PUCCH transmission, where Wp*ccH= 1 if a higher layer parameter mappingPattern = 'cyclicMapping'; else (e.g., if a higher layer parameter mappingPattern = 'sequentialMapping ', Wp*cChH= 2.

[0256] FIG. 18 shows an example 1800 that illustrates beam failure detection and recovery for a cell. The cell may be a PCell, a PSCell, or an SCell, for example. As shown in FIG. 18, example 1800 includes a wireless device 1802 and a base station 1804. Example 1800 may include steps 1806, 1808, 1810, and 1812.

[0257] Step 1806 may include base station 1804 transmitting one or more configuration parameters to wireless device 1802. The one or more configuration parameters may be comprised in one or more messages (e.g., RRC message(s), RRC reconfigurations message(s)).

[0258] The one or more configuration parameters may comprise a radio link monitoring configuration (e.g., RadioLlnkMonitoringConfig). The radio link monitoring configuration may be used to configure radio link monitoring for detection of beam- and / or cell radio link failure by wireless device 1802.

[0259] The radio link monitoring configuration may comprise a beam failure detection parameter (e.g., failureDetectionResourcesToAddModList) indicating a list of reference signals (e.g., RadioLinkMonitoringRS) for detecting a beam failure. The list of reference signals may comprise, for example, CSI-RS(s) and / or SS / PBCH block(s). If no reference signals are provided / indicated for the purpose of beam failure detection of the cell, wireless device 1802 may perform beam monitoring (or beam failure detection) based on activated TCI state(s) for coreset(s) of PDCCH of the cell.Docket No.: 25-1039PCT

[0260] The radio link monitoring configuration (or the one or more configuration parameters of the beam failure detection parameter) may indicate, for the cell (or for beam failure detection of the cell), a beam failure instance maximum counter (e.g., beamFailurelnstanceMaxCount). The beam failure instance maximum counter may indicate / determine after how many beam failure instance indications (or events) wireless device 1802 triggers beam failure recovery for the cell.

[0261] The radio link monitoring configuration (or the one or more configuration parameters of the beam failure detection parameter) may indicate, for the cell (or for beam failure detection of the cell), a beam failure detection timer (e.g., beamFailureDetedionTimer).

[0262] For a BWP of a serving cell, the beam failure detection parameter (e.g., failureDetectionResourcesToAddModLisf) may indicate, for the cell, a beam failure detection (BFD) set (e.g., q0). The BFD set may indicate / comprise periodic CSI-RS resource configuration index(es) for radio link quality measurements on the BWP of the serving cell. A BFD set may be (or may be interchangeably used with) a BFD-RS set.

[0263] For a BWP of a serving cell, wireless device 1802 may be provided / configured with a candidate beam detection (CBD) set (e.g., q ) by a higher layer parameter candidateBeamRSList or candidateBeamRSListExt or candidateBeamRSSCellList. The CBD set may indicate / comprise respective periodic CSI-RS resource configuration index(es) and / or SS / PBCH block index(es) for radio link quality measurements on the BWP of the serving cell.

[0264] If wireless device 1802 is not provided / configured with a BFD set (e.g., q0), by a higher layer parameter failureDetectionResourcesToAddModList, for a BWP of the serving cell, wireless device 1802 may determine a BFD set (e.g., q0) to include periodic CSI-RS resource configuration index(es) with same values as RS indexes indicated by TCI states (e.g., TCI -State) for CORESET(s) that wireless device 1802 uses for monitoring PDCCH.

[0265] The radio link monitoring configuration may comprise a beam failure detection parameter (e.g., BeamFailureDetection). The beam failure detection parameter may comprise a higher layer parameter failureDetectionSetl indicating / configuring a first BFD set (e.g., q00) and a higher layer parameter failureDetectionSet2 indicating / configuring a second BFD set (e.g., qQ).

[0266] The radio link monitoring configuration (or the one or more configuration parameters of the beam failure detection parameter) may indicate, for the first BFD set, one or more first reference signals (e.g., BeamLinkMonitoringRS, bfdResourcesToAddModList') for beam failure detection of the first BFD set. The one or more first reference signals may comprise, for example, CSI-RS(s) and / or SS / PBCH block(s). The one or more first reference signals may be a first list of reference signals for detecting beam failure of the first BFD set.Docket No.: 25-1039PCT

[0267] The radio link monitoring configuration (or the one or more configuration parameters of the beam failure detection parameter) may indicate, for the first BFD set, one or more first beam failure detection resources (e.g. , bfdResourcesToAddModList) indicating / identifying the one or more first reference signals. Each beam failure detection resource of the one or more first beam failure detection resources may indicate / identify a respective reference signal of the one or more first reference signals.

[0268] The radio link monitoring configuration (or the one or more configuration parameters of the beam failure detection parameter) may indicate, for the second BFD set, one or more second reference signals (e.g., BeamLinkMonitoringRS, bfdResourcesToAddModList) for beam failure detection of the second BFD set. The one or more second reference signals may comprise, for example, CSI-RS(s). The one or more second reference signals may comprise, for example, SS / PBCH block(s). The one or more second reference signals may be a second list of reference signals for detecting beam failure of the second BFD set.

[0269] The radio link monitoring configuration (or the one or more configuration parameters of the beam failure detection parameter) may indicate, for the first BFD set, a first beam failure instance maximum counter (e.g., beamFailureinstanceMaxCounf). The first beam failure instance maximum counter may indicate / determine after how many beam failure instance indications (or events) wireless device 1802 triggers beam failure recovery for the first BFD set.

[0270] The radio link monitoring configuration (or the one or more configuration parameters of the beam failure detection parameter) may indicate, for the first BFD set, a first beam failure detection timer (e.g., beamFailureDetection Timer) .

[0271] The radio link monitoring configuration (or the one or more configuration parameters of the beam failure detection parameter) may indicate, for the second BFD set, one or more second beam failure detection resources (e.g., bfdResourcesToAddModList) indicating / identifying the one or more second reference signals. Each beam failure detection resource of the one or more second beam failure detection resources may indicate / identify a respective reference signal of the one or more second reference signals.

[0272] The radio link monitoring configuration (or the one or more configuration parameters of the beam failure detection parameter) may indicate, for the second BFD set, a second beam failure instance maximum counter (e.g., beamFailureinstanceMaxCount). The second beam failure instance maximum counter may indicate / determine after how many beam failure instance indications (or events) wireless device 1802 triggers beam failure recovery for the second BFD set.

[0273] The radio link monitoring configuration (or the one or more configuration parameters of the beam failure detection parameter) may indicate, for the second BFD set, a second beam failure detection timer (e.g., beamFailureDetectionTimer).Docket No.: 25-1039PCT

[0274] When a higher layer parameter failureDetectionSetl indicating / configuring the first BFD set (e.g., q00) is present in the one or more message(s), wireless device 1802 may consider all the reference signals for / in the first BFD set as activated if at most maxBFD-RS-resourcesPerSetPerBWP reference signals are configured for the first BFD set, otherwise wireless device 1802 may consider all the reference signals in the first BFD set as deactivated.

[0275] When a higher layer parameter failureDetectionSet2 indicating / configuring the second BFD set (e.g., q0,i) is present in the one or more message(s), wireless device 1802 may consider all the reference signals for / in the second BFD set as activated if at most maxBFD-RS- resourcesPerSetPerBWP reference signals are configured for the second BFD set, otherwise wireless device 1802 may consider all the reference signals in the second BFD set as deactivated.

[0276] Returning to example 1800, after receiving the configuration parameters in step 1806, wireless device 1802 may detect a beam failure for the cell at a time T1. Wireless device 1802 may declare / detect beam failure when a number of beam failure instance indications received by a higher layer (e.g., MAC layer, RRC layer) of wireless device 1802 from a lower layer (e.g., PHY layer) of wireless device 1802 reaches a configured threshold before a configured timer expires.

[0277] The lower layer of wireless device 1802 may assess a radio link quality according to the BFD set (e.g., q0), the first BFD set (e.g., q0 0), or the second BFD set (e.g., q01) of resource configurations against a first threshold (e.g., QOUI.LR). For the BFD set (g0), the first BFD set (e.g., q00), or the second BFD set (e.g., q01), wireless device 1802 may assess the radio link quality only according to SS / PBCH blocks on the PCell or the PSCell or periodic CSI-RS resource configurations that are quasi co-located with the DM-RS of PDCCH receptions by wireless device 1802. The wireless device may apply a second threshold (e.g., Qin.LR) to the L1-RSRP measurement obtained from a SS / PBCH block. The wireless device may apply the second threshold (e.g., Qin.LR) to the L1-RSRP measurement obtained for a CSI-RS resource after scaling a respective CSI-RS reception power with a value provided by powerControlOffsetSS . The first threshold (e.g., QOUI.LR) and the second threshold (e.g., Qin.LR) may correspond to a default value of a higher layer parameter rimlnSyncOutOfSyncThreshold for Qout and to a value provided by a higher layer parameter rsrp- ThresholdSSB or a higher layer parameter rsrp-ThresholdBFR, respectively.

[0278] The lower layer of wireless device 1802 may provide an indication to the higher layer (e.g., MAC layer, RRC layer) of wireless device 1802 when the radio link quality for all corresponding resource configurations in the BFD set (e.g., q0), the first BFD set (e.g., qo,o) or in the second BFD set (e.g., q01) that wireless device 1802 uses to assess the radio link quality is worse than the first thresholdDocket No.: 25-1039PCT(e.g., QOUILR). The lower layer of wireless device 1802 may inform the higher layer when the radio link quality is worse than the first threshold (e.g., QOUILR).

[0279] In a non-DRX mode operation, the lower layer of wireless device 1802 may inform the higher layer of wireless device 1802 when the radio link quality is worse than the first threshold with a periodicity determined by the maximum between the shortest periodicity among the SS / PBCH blocks on the PCell or the PSCell and / or the periodic CSI-RS configurations in the BPD set (e.g., q0), the first BPD set (e.g., q0>0), or the second BPD set (e.g., q0) that wireless device 1802 uses to assess the radio link quality and 2 milliseconds.

[0280] The higher layer (e.g., MAC layer) of wireless device 1802 may be configured, by RRC message(s), per cell (e.g., a serving cell) or per a BFD (or BFD-RS) set with a beam failure recovery procedure. The beam failure recovery procedure may be used, by wireless device 1802, to indicate to base station 1804 a new SSB or a new CSI-RS (or a candidate reference signal) when a beam failure is detected on the serving SSB(s) / CSI-RS(s). If a higher layer parameter beamFailureRecoveryConfig in the RRC message(s) is reconfigured by an upper layer (e.g., RRC layer) of wireless device 1802 during an ongoing random-access procedure for beam failure recovery for PCell / PSCell, the higher layer of wireless device 1802 may stop the ongoing random-access procedure and initiate a (second / new) random-access procedure using the new configuration (or using a new higher layer parameter beamFailureRecoveryConfig in an RRC reconfiguration message).

[0281] The RRC message(s) may configure / indicate the following parameters (or the parameters below) in the higher layer parameter beamFailureRecoveryConfig, a higher layer parameter beamFailureRecoverySpCellConfig, a higher layer parameter beamFailureRecoverySCellConfig, and / or a higher layer parameter radioLinkMonitoringConfig for a beam failure detection and recovery procedure:beamFailurelnstanceMaxCount for the beam failure detection (per cell or per BFD-RS set of a cell configured with two BFD-RS sets);- beamFailureDetectionTimer for the beam failure detection (per cell or per BFD-RS set of a cell configured with two BFD-RS sets);candidateBeamRSList a list of candidate beams for PCell / PSCell beam failure recovery;- candidateBeamRS-List. a list of candidate beams for SCell beam failure recovery or list of candidate beams for beam failure recovery of a cell for BFD-RS set one;candidateBeamRS-List2 a list of candidate beams for beam failure recovery of a cell for BFD-RS set two.Docket No.: 25-1039PCT

[0282] Wireless device 1802 may use a counter BFI_COUNTER (per cell or per BFD-RS set of a cell configured with two BFD-RS sets) for a beam failure detection procedure. BFI_COUNTER may be used to count beam failure instance indication(s) received from the lower layer of wireless device 1802. Wireless device 1802 may initially set BFI_COUNTER to 0.

[0283] For a cell not configured with two BFD-RS sets for beam failure detection (or for a cell configured with one / single BFD-RS set for beam failure detection), if the higher layer of wireless device 1802 receives a beam failure instance indication from the lower layer of wireless device 1802, wireless device 1802 may start or restart the beamFailureDetectionTimer and may increment BFI_COUNTER by 1. If BFI_COUNTER of the BFD-RS set is equal to or greater than beamFailurelnstanceMaxCount, wireless device 1802 may trigger a beam failure recovery (BFR) for the cell (e.g., SCell). If BFI_COUNTER of the BFD-RS set is equal to or greater than beamFailurelnstanceMaxCount, wireless device 1802 may initiate, for the beam failure recovery (BFR) of the cell, a random-access procedure on / for the cell (e.g., PCell / PSCell) . Wireless device 1802 may set BFI_COUNTER to 0 if the beamFailureDetectionTimer expires. Wireless device 1802 may set BFI_COUNTER to 0 if beamFailureDetectionTimer, beamFailurelnstanceMaxCount, or any of the reference signals used for beam failure detection is reconfigured by the upper layer (e.g., RRC layer) of wireless device 1802. Wireless device 1802 may set BFI_COUNTER to 0 if the reference signal(s) associated with the cell used for beam failure detection is changed. If the random-access procedure initiated on / for the cell (e.g., the PCell / PSCell) for the BFR of the cell is successfully completed, wireless device 1802 may set BFI_COUNTER to 0. If the random-access procedure initiated on / for the cell (e.g., the PCell / PSCell) for the BFR of the cell is successfully completed, the wireless device may stop the beamFailureRecoveryTimer. If the random-access procedure initiated on / for the cell (e g., the PCell / PSCell) for the BFR of the cell is successfully completed, wireless device 1802 may consider the beam failure recovery procedure successfully completed.

[0284] For a cell configured with two BFD-RS sets for beam failure detection, if the higher layer of wireless device 1802 receives, from the lower layer of wireless device 1802, a beam failure instance indication for a first BFD-RS set of the two BFD-RS sets, wireless device 1802 may start or restart the beamFailureDetectionTimer of the first BFD-RS set and may increment a BFI_COUNTER of the first BFD-RS set by 1. Wireless device 1802 may set BFI_COUNTER of the first BFD-RS set to zero if the beamFailureDetectionTimer of the first BFD-RS set expires. Wireless device 1802 may set BFI_COUNTER of the first BFD-RS set to zero if beamFailureDetectionTimer, beamFailurelnstanceMaxCount, or any of the reference signals used for beam failure detection of the first BFD-RS set is reconfigured by the upper layer (e.g., RRC layer) of wireless device 1802 or by a BFD-RS Indication MAC CE associated with the first BFD-RS set of the two BFD-RS sets of the cell.Docket No.: 25-1039PCTWireless device 1802 may set BFI_COUNTER of the first BFD-RS set to zero if the reference signal(s) associated with the first BFD-RS set of the two BFD-RS sets of the cell used for beam failure detection is changed. If the cell is an SCell and the SCell is deactivated, wireless device 1802 may set the BFI_COUNTER of each BFD-RS set of the two BFD-RS sets of the SCell to 0. If the cell is an SCell and the SCell is deactivated, wireless device 1802 may consider the beam failure recovery procedure successfully completed and cancel each triggered BFR of both of the two BFD-RS sets of the cell. If the BFI_COUNTER of the first BFD-RS set is equal to or greater than a beamFailurelnstanceMaxCount, wireless device 1802 may trigger a beam failure recovery (BFR) for the first BFD-RS set of the cell. If wireless device 1802 triggers BFR for both of the two BFD-RS sets of the cell (e.g ., PCell / PSCell) and a beam failure recovery procedure is not successfully completed for any of the two BFD-RS sets, wireless device 1802 may initiate a random-access procedure on the cell (e.g., the PCell / PSCell). Wireless device 1802 may initiate the random-access procedure for a beam failure recovery of the cell (or for a beam failure recovery for / of both of the two BFD-RS sets). If wireless device 1802 completes the random-access procedure initiated for the beam failure recovery of both of the two BFD-RS sets of an PCell / PSCell successfully, wireless device 1802 may set BFI_COUNTERof each BFD-RS set of the two BFD-RS sets of the cell (e.g., the PCell / PSCell) to 0. If wireless device 1802 completes the randomaccess procedure initiated for the beam failure recovery of both of the two BFD-RS sets of PCell / PSCell successfully, wireless device 1802 may consider the beam failure recovery procedure successfully completed.

[0285] For an PCell or an PSCell, upon request from the higher layer, wireless device 1802 may provide to the higher layer periodic CSI-RS configuration index(es) and / or SS / PBCH block index(es) from the CBD set (e.g., ^), or the first CBD set (e.g., q0) and the second CBD set (e.g., Q1 ;L) and the corresponding L1-RSRP measurements that are larger than or equal to the second threshold (e.g., Qin.LR).

[0286] For an SCell, upon request from the higher layer, wireless device 1802 may indicate to the higher layer whether there is at least one periodic CSI-RS configuration index or SS / PBCH block index from the CBD set (e.g., q ), the first CBD set (e.g., q10), or the second CBD set (e.g., q1) with corresponding L1-RSRP measurements that are larger than or equal to the second threshold (e.g., Qin LR) . Wireless device 1802 may provide / indicate to the higher layer periodic CSI-RS configuration index(es) and / or SS / PBCH block index(es) from the CBD set (e.g., q^), the first CBD set (e.g., g10), or the second CBD set (e.g., q1:1) having corresponding L1-RSRP measurements that are larger than or equal to the second threshold (e.g., Qin.LR), if any.Docket No.: 25-1039PCT

[0287] Returning to FIG. 18, after a beam failure is detected for the cell, in step 1808, wireless device 1802 may transmit, at a time T2, an uplink transmission for the beam failure recovery of the cell. The uplink transmission may indicate a suitable beam for the beam failure recovery. To transmit the uplink transmission, wireless device 1802 may use different procedures depending on whether the cell is a PCell or an SCell, for example. For a PCell, wireless device 1802 may use a contention-free randomaccess procedure or a contention-based random-access procedure, depending on whether dedicated random-access resources for the BFR procedure are configured. After transmitting the uplink transmission in step 1808, wireless device 1802 may monitor a PDCCH to detect a DCI that completes the beam failure recovery and may receive in step 1810, at a time T3, a DCI that completes the beam failure recovery. In the following, steps 1808 and 1810 are described respectively for a beam failure recovery for a PCell using the contention-free random-access procedure (FIG. 19), a beam failure recovery for a PCell using the contention-based random-access procedure (FIG. 20), and failure recovery for an SCell (FIG. 21).

[0288] FIG. 19 shows an example 1900 that illustrates beam failure recovery for a PCell (or PSCell) using the contention-free random-access procedure. As shown in FIG. 19, example 1900 includes wireless device 1802 and base station 1804 described above with reference to FIG. 18. Example 1900 may include step 1806 described above and steps 1902, 1904, and 1906. Step 1902 may be an embodiment of step 1808, step 1904 may be an embodiment of step 1810, and step 1906 may be an embodiment of step 1812 described further below.

[0289] In the case of a PCell or a PSCell, step 1806 may further include providing / configuring wireless device 1802, by a higher layer parameter PRACH-ResourceDedicatedBFR, a configuration for a PRACH transmission. Wireless device 1802 may use the configuration to perform the PRACH transmission in step 1902. The PRACH transmission in step 1902 may indicate a candidate reference signal. For example, a random-access preamble used for the PRACH transmission and / or a PRACH occasion (e.g ., time / frequency resource) used for the PRACH transmission may be associated with the candidate reference signal.

[0290] In the case of a PCell or a PSCell, step 1806 may further include providing / configuring wireless device 1802 with a CORESET through a link to a search space set provided by a higher layer parameter recoverySearchSpaceld for monitoring PDCCH in the CORESET. If wireless device 1802 is provided the higher layer parameter recoverySearchSpaceld, wireless device 1802 may not expect to be provided / configured another search space set for monitoring PDCCH in the CORESET associated with the search space set provided by the higher layer parameter recoverySearchSpaceld.

[0291] After the PRACH transmission, the higher layer (e.g., MAC) of wireless device 1802 may start a random-access response window (e.g., ra-ResponseWindow) configured inDocket No.: 25-1039PCTBeamFailureRecoveryConfig at the first / earliest PDCCH occasion as from the end of transmission of the random-access preamble of the PRACH transmission. Wireless device 1802 may monitor, while the random-access response window is running, for a PDCCH transmission / reception identified by the C- RNTI on the search space indicated by the higher layer parameter recoverySearchSpaceld. Specifically, wireless device 1802 may monitor, according to antenna port quasi co-location parameters associated with the candidate reference signal (e.g., periodic CSI-RS resource configuration or with SS / PBCH block associated with index qnewprovided by the higher layer), PDCCH in the search space set provided by the higher layer parameter recoverySearchSpaceld for detection of a DCI format with CRC scrambled by C-RNTI or MCS-C-RNTI. If wireless device 1802 receives, in step 1904, the PDCCH transmission / reception addressed to the C-RNTI, wireless device 1802 may consider / determine the random-access procedure successfully completed.

[0292] For PDCCH monitoring in a search space set provided by the higher layer parameter recoverySearchSpaceld and for corresponding PDSCH receptions, wireless device 1802 may assume the same antenna port quasi-collocation parameters as the ones associated with the candidate reference signal (e.g., with index qnew) until wireless device 1802 receives by higher layers an activation for a TCI state or any of the parameters tcl-StatesPDCCH-ToAddList and / or tci- StatesPDCCH-ToReleaseList. After wireless device 1802 detects a DCI format with CRC scrambled by C-RNTI or MCS-C-RNTI in the search space set provided by the higher layer parameter recoverySearchSpaceld, wireless device 1802 may continue to monitor PDCCH candidates in the search space set provided by the higher layer parameter recoverySearchSpaceld until wireless device 1802 receives a MAC CE activation command for a TCI state or tcl-StatesPDCCH-ToAddList and / or tci- StatesPDCCH-ToReleaseList.

[0293] FIG. 20 shows an example 2000 that illustrates beam failure recovery for a PCell (or PSCell) using the contention-based random-access procedure. As shown in FIG. 20, example 2000 includes wireless device 1802 and base station 1804 described above with reference to FIG. 18. Example 2000 may include step 1806 described above and steps 2002, 2004, and 2006. Step 2002 may be an embodiment of step 1808, step 2004 may be an embodiment of step 1810, and step 2006 may be an embodiment of step 1812 described further below.

[0294] Step 2002 may include wireless device 1802 transmitting, for the random-access procedure a Msg3 / MsgA transmission to base station 1804. The Msg3 / MsgA transmission may indicate a candidate reference signal. The Msg3 / MsgA transmission may comprise / include a C-RNTI MAC CE. The Msg3 / MsgA transmission may comprise a BFR MAC-CE. The BFR MAC-CE (e.g., BFR MAC CE, Truncated BFR MAC-CE) may comprise a field (e.g., SP field) that may indicate beam failure detection for the PCell / PSCell. The field may indicate presence of octet(s) containing a second field (e.g., a fieldDocket No.: 25-1039PCTindicating presence of candidate reference signal indexes) if the PCell / PSCell is configured with two BFD-RS sets. For an PCell / PSCell configured with two BFD-RS sets, the field set to 1 may indicate that a beam failure is detected for at least one BFD-RS set of the two BFD-RS sets of the PCell / PSCell and the octet(s) containing the second field is present for the PCell / PSCell. Wireless device 1802 may include / add / multiplex the BFR MAC CE into a MAC PDU as part of the random-access procedure.

[0295] After transmitting the Msg3 / MsgA in step 2002, the higher layer (e.g., MAC) of wireless device 1802 may start or restart a timer (e.g., ra-ContentionResolutionTimer or a msgB-ResponseWindow) in the first / earliest symbol after the end of the Msg3 / MsgA transmission. Wireless device 1802 may monitor for a PDCCH reception / transmission of / on the PCell / PSCell while the timer is running. Based on receiving, in step 2004, the PDCCH reception / transmission of / on the PCell / PSCell, wireless device may 1802 consider / determine the random-access procedure successfully completed.

[0296] In existing technologies, a wireless device completes a beam failure recovery of a primary cell (e.g., PCell or PSCell) after receiving a DCI in a recovery search space set (e.g., as illustrated at step 1904 in FIG. 19 above). After receiving the DCI in the recovery search space set, the wireless device continues to monitor the recovery search space set using (e.g., the QCL parameters of) the candidate reference signal indicated by the PRACH transmission (e.g., as illustrated at step 1902). In particular, the wireless device continue using the candidate reference signal to monitor the recovery search space until one of two conditions occurs: (i) until the wireless device receives an RRC message (e.g., RRC reconfiguration message) indicating TCI states for a coreset and a MAC CE indicating a TCI state among the (RRC-)configured coresets or (II) until the wireless device receives a MAC CE indicating a TCI state among the (RRC-)configured TCI states of the coreset.

[0297] In addition to monitoring the recovery search space set using (e.g., the QCL parameters of) the candidate reference signal, the wireless device receives PDSCH receptions using (e.g., the QCL parameters of) the candidate reference signal (I) until the wireless device receives an RRC message (e.g., RRC reconfiguration message) indicating TCI states for a coreset and a MAC CE indicating a TCI state among the (RRC-)configured coresets or (II) until the wireless device receives a MAC CE indicating a TCI state among the (RRC-)configured TCI states of the coreset.

[0298] However, under the unified TCI state framework (e.g., as illustrated in FIG. 17), the TCI state of the coreset may be updated by a control command, such as a MAC CE or a DCI (e.g., step 1708 in FIG. 17). Since the wireless device may not receive a MAC CE that updates an indicated TCI state (e.g., a DCI may be used as the control command), conditions (i) and (ii) may not occur. This may cause the wireless device to, e.g., continue monitoring the recovery search space set and / or receiving PDSCH receptions using the candidate search space set based on no MAC CE being received to update the indicated TCI state as specified under conditions (i) and (ii). This may increase power consumption atDocket No.: 25-1039PCTthe wireless device (e.g., due to the monitoring continuing and the MAC CE not being received), cause misalignment between the wireless device and the network (e.g., base station), and / or restrict the flexibility of the unified TCI state framework (e.g., by limiting the control command).

[0299] According to embodiments of the present disclosure, the wireless device monitors a search space set, for a BFR, using quasi co-location (QCL) parameters of a candidate reference signal, indicated for the BFR, until reception of a DCI indicating a TCI state.

[0300] By using the QCL parameters of the candidate reference signal until reception of the DCI indicating the TCI state, this may decrease power consumption at the wireless device (e.g., due to the monitoring being based on the DCI), increase reliability by aligning the operations between the wireless device and the network (e.g., base station), and / or enable flexibility for the network in using the unified TCI state framework (e.g., by not limiting the control command).

[0301] FIG. 21 illustrates an example of a wireless device 2100 that performs beam failure recovery (BFR) and communicates using the unified TCI state framework on a cell of a base station 2120.

[0302] As illustrated at tO, wireless device 2100 receives one or more RRC messages 2102. One or more RRC messages 2102 may be implemented based on FIGs. 17-20 (e.g., configuration parameters at step 1706 and / or configuration parameters at step 1806).

[0303] One or more RRC messages 2102 may comprise may comprise one or more beam failure recovery (BFR) configuration parameters (e.g., BeamFailureRecoveryConfig). The one or more BFR configuration parameters may indicate PRACH resources and / or candidate reference signals (e.g., candidate beams) for BFR. The candidate reference signals for BFR are used in case of a beam failure detection on the cell (e.g., of a base station 2120).

[0304] The cell may be a primary cell, such as a PCell or a PSCell . The candidate reference signals may be channel state information reference signals (CSI-RSs) and / or synchronization signal (SS) and physical broadcast channel (PBCH) blocks (SS / PBCH blocks). SS / PBCH blocks may be referred to as synchronization signals or synchronization signal blocks (SSBs).

[0305] The one or more BFR configuration parameters may comprise a PRACH resource parameter (e.g., PRACH-ResourceDedicatedBFR) comprising / indicating a configuration for PRACH transmission for BFR. The PRACH resource parameter indicates a candidate reference signal (e.g., among the candidate reference signals) and a preamble index (e.g., ra-Preamblelndex).

[0306] Additionally or alternatively, the one or more BFR configuration parameters may indicate a search space set for the BFR. As an example of indicating the search space set, the one or more BFR configuration parameters may comprise a recovery search space identifier (e.g., recoverySearchSpaceld) indicating / identifying a search space set for the BFR. That is, the search space set for the BFR is a search space set to use (e.g., or monitor) for a (BFR) random-access responseDocket No.: 25-1039PCT(RAR) (e.g., when a random access procedure, such as, e.g., illustrated in FIGs. 13A-13C, is performed due to a beam failure). The search space set may be referred to as a recovery search space or a beam failure recovery search space. The search space set for BFR may be associated with a coreset. The coreset, associated with the search space set for BFR, may be referred to as a BFR coreset. The BFR coreset may not be associated with any search space set other than the search space set for BFR.

[0307] As illustrated at t1 , wireless device 2100 detects a beam failure (e.g., on the cell of base station 2120). The detection of the beam failure may be implemented as illustrated in (e.g., at T1 in) FIGs. 18-20. To detect the beam failure, as described in greater detail above in connection with FIG. 18, wireless device 2100 may determine that the radio link quality of one or more reference signals in a beam failure detection set (e.g., indicated by one or more RRC messages 2102) is less (e.g., worse) than a threshold.

[0308] After detecting the beam failure (e.g., on the cell of base station 2120) at t1 , wireless device 2100 may trigger a beam failure recovery (BFR or BFR procedure). The BFR may be triggered by initiating a random-access procedure (e.g., on the cell). In the example illustrated in FIG. 21, the random-access procedure is a con tention -free random-access procedure (e.g., which may be implemented based on the contention-free random access procedure illustrated in, e.g. FIG. 19).

[0309] Wireless device 2100 may select, based on a radio link quality, a candidate reference signal among the candidate reference signals (e.g., indicated by one or more RRC messages 2102) and indicate (to base station 2120) that the candidate reference signal as a (e.g., new) reference signal to be used after beam failure. For example, wireless device 2100 may determine that a radio link quality (e.g., L1-RSRP) of a candidate reference signal is greater / larger than, or equal to, a threshold (e.g., Qin LR threshold indicated by rsrp-ThresholdSSB or rsrp-ThresholdBFR in one or more RRC messages 2102).

[0310] Although wireless device 2100 may indicate the candidate reference signal, it should be understood that base station 2120 may (e.g., determine) not to select the (same) candidate reference signal after the beam failure (e.g., is completed) for wireless device 2100.

[0311] As illustrated at t2, wireless device 2100 transmits a physical random-access channel (PRACH) transmission 2104 indicating the candidate reference signal. An implicit indication may be used to indicate the candidate reference signal for the BFR.

[0312] As an example of indicating the candidate reference signal, PRACH transmission 2104 comprises a random-access preamble. A preamble index of the random-access preamble and / or a random-access occasion used for the random-access preamble may be associated with (e g., mapped to) the candidate reference signal (e.g., by the PRACH resource parameter in the one or more BFR configuration parameters of one or more RRC messages 2102). Based on the which preamble index, and / or which random-access occasion, is used for (e.g., the random-access preamble of) PRACHDocket No.: 25-1039PCTtransmission 2104, the network (e.g., base station 2120) may identify the candidate reference signal. That is, the network (e.g., base station 2120) is able to determine which candidate reference signal that wireless device 2100 identified from among the one or more candidate reference signals (e.g., indicated by one or more RRC messages 2102) by the association of the candidate reference signal with the preamble index and / or the random-access occasion.

[0313] For example, different preamble indexes may be used for PRACH transmissions transmitted (e.g., by different wireless devices on the cell), and the network (e.g., base station 2120) may identify the candidate reference signal indicated by each of the PRACH transmissions based on which preamble index is used for each of the PRACH transmissions. As another example, the same preamble index may be used for (multiple) PRACH transmissions transmitted in different random-access occasions (e.g., by different wireless devices on the cell), and the network (e.g., base station 2120) may identify the candidate reference signal indicated by each of the PRACH transmissions based on which randomaccess occasion is used for each of the PRACH transmissions.

[0314] As illustrated at t3, wireless device 2100 monitors (e.g., starts monitoring) the search space set for the BFR (e.g., indicated by the one or more BFR configuration parameters of one or more RRC messages 2102). Wireless device 2100 monitors the search space set using the quasi co-location (QCL) parameters of the candidate reference signal. The QCL parameters may be referred to as antenna port QCL parameters of the candidate reference signal. The QCL parameters may be used (e.g., applied) to receive (e.g., detect, decode) downlink signals (e.g., PDCCH and / or PDSCH) via the search space set (e.g., DCIs received via the search space and / or PDSCHs scheduled by DCIs received via the search space set).

[0315] Wireless device 2100 may start monitoring the search space set for BFR after a time duration from PRACH transmission 2104. As an example, the time duration is illustrated in FIG. 21 as being between t2 and t3. To continue the example, wireless device 2100 may transmit PRACH transmission 2104 in a time slot (e.g., time slot n) after detecting the beam failure (e.g., at t1). Wireless device 2100 may start monitoring the search space set from the time slot (e.g., time slot n) plus the time duration (time slot n + time duration). The time duration may be equal to (e.g., in slots) a fixed number of slots, such as 4 slots (e.g., in which case t3 starts at time slot n + 4). As another example, the time duration may be equal to (e.g., in slots) 4 (slots) + (2iJ)kmac, where pi is the subcarrier spacing (SCS) configuration of PRACH transmission 2104 and kmac is a number of slots provided by a parameter (e.g., kmac) indicated by one or more RRC messages 2102. kmac is a scheduling offset, in number of slots, for the round trip time (RTT) between wireless device 2100 and base station 2120 in a non-terrestrial network (NTT). One or more RRC messages 2102 may comprise kmacbased on downlink and uplink frame timing are not being aligned at base station 2120 (e.g,. when implemented in an NTN). A value ofDocket No.: 25-1039PCTkmacis provided by the parameter (e.g., kmac) if the parameter is present (e.g., present in one or more RRC messages 2102). Alternatively, the value of kmac is zero if the parameter is absent (e.g., absent from one or more RRC messages 2102).

[0316] Wireless device 2100 may monitor the search space set within a (time) window (e.g., ra- ResponseWindow). For example, the window may be indicated by the one or more BFR configuration parameters (e.g., ra-ResponseWindow in BeamFailureRecoveryConfig) of one or more RRC messages 2102. The window may be referred to as an RAR window.

[0317] Wireless device 2100 monitors the search space set, using the QCL parameters of the candidate reference signal, until wireless device 2100 receives a DCI that indicates a TCI state. Before the DCI indicating the TCI state is received, wireless device 2100 may receive other downlink signals, such as DCIs, MAC CEs, and / or RRC messages. For example, wireless device 2100 may (e.g., initially) monitor (e.g., the PDCCH of) the search space set, using the QCL parameters of the candidate reference signal, until a DCI (e.g., with the C-RNTI of wireless device 2100) is received in the search space set. After wireless device 2100 receives the DCI in the search space set, the BFR may be completed.

[0318] As illustrated at t4, wireless device 2100 receives a DCI 2106 in the search space set. DCI 2106 is received (e.g., detected, decoded) in the search space set using the QCL parameters of the candidate reference signal. DCI 2106 indicates a C-RNTI of wireless device 2100. For example, a CRC of DCI 2106 may be scrambled by a C-RNTI, or an MCS-C-RNTI, of wireless device 2100. Based on receiving DCI 2106 in the search space set, the BFR is completed as illustrated in FIG. 21.

[0319] After, e.g., receiving DCI 2106 at t4, wireless device 2100 continues monitoring the search space set using the QCL parameters of the candidate reference signal until wireless device 2100 receives a DCI that indicates a TCI state. Until wireless device 2100 receives the DCI indicating the TCI state, wireless device 2100 uses the QCL parameters of the candidate reference to monitor (e.g., the PDCCH) of the search space set and / or receive PDSCH receptions via the search space set.

[0320] As an example of monitoring using the QCL parameters of the candidate reference signal, at least one demodulation RS (DM-RS) antenna port of / for PDCCH receptions in the coreset (e.g., the BFR coreset associated with the search space set for BFR) may be quasi co-located with the candidate reference signal. The at least one DM-RS antenna port of / for the PDCCH receptions in the coreset may be quasi co-located with the candidate RS with respect to spatial (domain) reception parameters, such as in QCL-TypeD. As another example, the PDCCH receptions may be received using the same spatial domain filter (e.g., a spatial domain reception filter) used to receive the candidate reference signal.

[0321] As an example of receiving the PDSCH receptions via the search space set, wireless device 2100 may receive a DCI in (e.g., the PDCCH of) the search space set and the DCI may schedule aDocket No.: 25-1039PCTPDSCH reception. Wireless device 2100 may use the QCL parameters of the candidate reference signal to receive the PDSCH reception (e.g., one or more TBs in the PDSCHs). For example, at least one DM- RS antenna port of / for the PDSCH receptions may be quasi co-located with the candidate reference signal. The at least one DM-RS antenna port of / for the PDSCH receptions may be quasi co-located with the candidate RS with respect to spatial (domain) reception parameters, such as in QCL-TypeD. As another example, the PDSCH receptions may be received using the same spatial domain filter (e.g., a spatial domain reception filter) used to receive the candidate reference signal.

[0322] As illustrated at t5, wireless device 2100 receives a DCI 2108 that indicates a TCI state. As an example of indicating the TCI state, DCI 2106 may comprise a field that indicates the TCI state. For example, a value of the field may correspond to the TCI state (e.g., the value in the field may correspond to a codepoint, such as a TCI codepoint, of the TCI state). The field may be referred to as a TCI field or a TCI state indicator field.

[0323] A DCI format of DCI 2108 may be, e g., DCI format 1_1 , DCI format 1 _2, or DCI format 1_3. In addition to indicating the TCI state, DCI 2108 may schedule a downlink transmission (e.g., PDSCH transmission). DCI 2106 may be implemented based on the DCI in step 1708 in FIG. 17.

[0324] The TCI state indicated by DCI 2108 may be from a list of TCI states (e.g., indicated by one or more RRC messages 2102). For example, one or more RRC messages 2102 may comprise one or more PDSCH configuration parameters (e.g., PDSCH-Config) that indicate a list of TCI states comprising the TCI state. To indicate the list of TCI states, the one or more PDSCH configuration parameters may comprise a downlink-or-joint TCI state list parameter (e.g., dl-OrJointTCI- StateToAddModList, dl-OrJointTCI-StateList) that indicates the list of TCI states.

[0325] The TCI state indicated by DCI 2108 is an active TCI state (e.g., an activated TCI state). The TCI state may be an active TCI state from among the list of TCI states (e.g., indicated by one or more RRC messages 2102). For example, wireless device 2100 may receive a MAC CE that indicates activation of at least two TCI states (e.g., from among the list of TCI states indicated by one or more RRC messages 2102). The MAC CE may be implemented based on step 1708 of FIG. 17 (e.g., the control command implemented as a MAC CE). The MAC CE is received before DCI 2108. For example, the MAC CE indicating activation of at least two TCI states may be received after t4 and before t5 in FIG. 21. As another example, the MAC CE indicating activation of the at least two TCI states may be received after tO and before t5 (e.g., after tO and before t1). As another example, the MAC CE indicating activation of the at least two TCI states may be received before one or more RRC messages 2102 in tO of FIG. 21.

[0326] The TCI state may be a TCI state of a coreset (e.g., of the cell of base station 2120). For example, one or more RRC messages 2102 may comprise one or more coreset configurationDocket No.: 25-1039PCTparameters (e.g., ControlResourceSef) of the coreset. The one or more coreset configuration parameters may comprise a parameter that indicates that the TCI states of the coreset are unified TCI states (and / or that the TCI state is a unified TCI state). For example, the parameter may be a follow- unified-TCI-state parameter (e.g., followUnifiedTCI-State) for the coreset. Based on (e.g., if, in response to, or when) the parameter is enabled / configured / present, wireless device 2100 applies an indicated downlink TCI state, or an indicated joint TCI state, to PDCCH receptions via the coreset.

[0327] The coreset may have a coreset index (e.g., indicated by one or more RRC messages 2102, such as the one or more coreset configuration parameters). In an example, the coreset index of the coreset may be zero. The coreset may be associated with at least one common search space set (CSS) (e.g., other than a Type3 PDCCH search space set). In another example, the coreset index of the coreset may be a value other than zero (e.g., a value that is different from zero, such as 1 , 2, 3, . . . . n). In this example, the coreset may be associated with one or more user-specific search space (USS) sets and / or one or more Type3 PDCCH search space sets. In addition, the coreset in this example with a CSS set (other than a Type3 PDCCH search space set).

[0328] The TCI state may be for a coreset of a downlink BWP of the cell. For example, the downlink BWP may comprise the coreset. The downlink BWP may be an active downlink BWP of the cell.

[0329] Based on the TCI state being a unified TCI state, the TCI state (indicated by DCI 2108) may be a downlink TCI state or a joint TCI state. A downlink TCI state applies to downlink receptions (e.g., PDCCH, PDSCH, CSI-RSs) via the cell. A joint TCI state applies to (both) downlink receptions (e.g., PDCCH, PDSCH, CSI-RS) via the cell and (as well as) to uplink transmissions (e.g., PUSCH, PUCCH, SRS) via the cell.

[0330] As an example for unified TCI states, one or more RRC messages 2102 may comprise one or more serving cell configuration parameters (e.g., ServingCellConfig) of the cell. The one or more serving cell configuration parameters may comprise a parameter indicating the type of unified TCI state. The parameter may be referred to as a unified TCI state type parameter (e.g., unifiedTCI-StateType). first value (e.g., separate) of the unified TCI state type parameter indicates that the cell is configured with (both) a TCI state list parameter (e.g., dl-OrJointTCI-StateLisf) for downlink TCI state and an uplink TCI state list parameter (e.g., ul-TCI-StateLisf) for uplink TCI states. A second value (e.g., joint) of the unified TCI state type parameter indicates that the cell is configured with a TCI state list parameter (e.g., dl-OrJointTCI-StateList) for joint TCI state for both uplink and downlink operations.

[0331] After receiving DCI 2108, wireless device 2100 may stop monitoring the search space set for BFR. For example, wireless device 2100 may stop monitoring (e.g., PDCCH candidates of) the search space set after receiving DCI 2108 indicating the TCI state or after applying the TCI state indicated byDocket No.: 25-1039PCTDCI 2108. Additionally or alternatively, wireless device 2100 may stop monitoring the coreset (e.g., BFR coreset) associated with the search space set.

[0332] As illustrated at t6, wireless device 2100 applies (e.g., starts applying) the TCI state indicated by DCI 2108. For example, after receiving DCI 2108 indicating the TCI state (or after applying the TCI state indicated by DCI 2108), wireless device 2100 may receive PDSCH receptions using QCL parameters of a reference signal indicated by the TCI state. Additionally or alternatively, after receiving DCI 2108 indicating the TCI state (or after applying the TCI state indicated by DCI 2108), wireless device 2100 may receive (or monitor for) PDCCH receptions using the QCL parameters of the TCI state. The PDCCH receptions may be received via a coreset other than BFR coreset (i.e., a coreset that is different than the coreset associated with the search space set for BFR). Additionally or alternatively, the QCL parameters, of the TCI state, used for receiving the PDCCH receptions may be for the coreset (i.e., a coreset other than the BFR coreset).

[0333] Wireless device 2100 may apply the TCI at t6 starting from a number of symbols (e.g., after t5). For example, wireless device 2100 may start applying the TCI state (e.g., no later than) a first / earliest / initial / starting slot that is at least a number of symbols (e.g., beamAppTime) after a last transmission of an uplink transmission (e.g., PUSCH or PUCCH transmission) with a positive HARQ- ACK corresponding to DCI 2108 (or corresponding to PDSCH(s) scheduled by DCI 2108). The number of symbols may be indicated by one or more RRC messages 2102. The number of symbols may be implemented based on the number of symbols illustrated in FIG. 18.

[0334] By using the QCL parameters of the candidate reference signal until reception of the DCI indicating the TCI state, this may decrease power consumption at the wireless device (e.g., due to the monitoring being based on the DCI), increase reliability by aligning the operations between the wireless device and the network (e.g., base station), and / or enable flexibility for the network in using the unified TCI state framework (e.g., by not limiting the control command).

[0335] As explained above, in existing technologies, a wireless device uses (e.g., the QCL parameters) of the candidate reference signal for monitoring the search space set (and / or corresponding PDSCH receptions) until (I) until the wireless device receives an RRC message (e.g., RRC reconfiguration message) indicating TCI states for a coreset and a MAC CE indicating a TCI state among the (RRC-)configured coresets or (II) until the wireless device receives a MAC CE indicating a TCI state among the (RRC-)configured TCI states of the coreset.

[0336] According to embodiments of the present disclosure, the wireless device monitors a search space set, for a BFR, using quasi co-location (QCL) parameters of a candidate reference signal, indicated for the BFR, until reception of a DCI indicating a TCI state. This feature may be combined with conditions (i) and (ii) above as well as other conditions. For example, the wireless device may monitorDocket No.: 25-1039PCTthe search space set, for the BFR, using the QCL parameters of the candidate reference signal, indicated for the BFR, until: reception of a DCI indicating a TCI state based on receiving a MAC CE indicating at least two TCI states are activated. As another example, the monitoring may be until: reception of a DCI indicating a TCI state based on receiving a MAC CE indicating at least two TCI states are activated; and / or reception of a MAC CE indicating (e.g., activation of) one TCI state (e.g., only one TCI state). This may decrease power consumption at the wireless device (e.g., due to the monitoring being based on the DCI or a MAC CE indicating ), increase reliability by aligning the operations between the wireless device and the network (e.g., base station), and / or enable flexibility for the network in using the unified TCI state framework (e.g., by not limiting the control command).

[0337] Although several aspects of the above example refer to (e.g., the QCL parameters of) the candidate reference signal being used (e.g., for monitoring and / or receiving) until reception of DCI 2108 indicating the TCI state, the reception of DCI 2108 may be replaced with application of the TCI state indicated by DCI 2108. For example, wireless device 2100 monitoring the search space set for BFR until reception of DCI 2108 may be replaced with wireless device 2100 monitoring the search space set for BFR until application of a TCI state indicated by DCI 2108. As another example, wireless device 2100 receiving PDSCHs using the QCL parameters of the candidate reference signal until reception of DCI 2108 may be replaced with wireless device 2100 receiving PDSCHs using the QCL parameters of the candidate reference signal until the TCI state indicated by DCI 2108 is applied. As yet another example, wireless device 2100 stopping monitoring the search space set for BFR until reception of DCI 2108 may be replaced with wireless device 2100 stopping monitoring the search space set after the TCI state indicated by DCI 2108 is applied.

[0338] In the present disclosure, the phrase "monitoring the PDCCH” may be replaced with "receiving one or more DCIs,” “detecting one or more DCIs” and / or “decoding one or more DCIs” as well as other similar phrases. The term “DCIs” may be replaced with “PDCCH" or “PDCCH transmissions” as well as other similar phrases. Similarly, “PDSCH receptions" may be replaced with “PDSCH" or “TBs” as well as other similar phrases. Furthermore, the phrase “receiving DCI 2108 indicating a TCI state” may be replaced with “applying a TCI state indicated by DCI 2106” as well as other similar phrases. The phrase “receiving a DCI” may be replaced with “reception of a DCI” or “wireless device 2100 receives a DCI” as well as other similar phrases. The phrase “until reception of DCI 2108 indicating a TCI state” may be replaced with “until application of a TCI state indicated by DCI 2108” or “until a TCI state, indicated by DCI 2108, is applied” as well as other similar phrases. In addition, “candidate reference signal” may be replaced with “reference signal for beam failure,” “reference signal for beam failure recovery,” “reference signal,” or a specific type of reference signal (e.g., CSI-RS or SS / PBCH block) as well as other similar phrases.Docket No.: 25-1039PCT

[0339] FIG. 22 illustrates a process 2200 according to an embodiment of the present disclosure. The aspects of the process 2200 in FIG. 22 may be implemented by the wireless device discussed above in connection with FIGs. 17-21. Reference numerals from FIG. 21 are included in the discussion below within parentheses for ease of understanding the examples. However, it should be understood that the reference numerals are not particularly limiting.

[0340] As illustrated in FIG. 22, process 2200 comprises a step 2202 of transmitting, by a wireless device (2100), a physical random-access channel (PRACH) transmission (2104) indicating a candidate reference signal (RS) for a beam failure recovery (BFR).

[0341] Process 2200 may further comprise a step 2204 of monitoring a search space set, for the BFR, using quasi-collocation (QCL) parameters of the candidate RS until reception of downlink control information (DCI) (2108) indicating a transmission configuration indicator (TCI) state.

[0342] Additional aspects, with examples, of step 2202, step 2204, and process 2200 are discussed below. Each of the additional aspects, and examples, below may be considered an embodiment. Each aspect of the embodiments may be combined with, or substituted for, the aspects of the embodiment of process 2200 illustrated in FIG. 22, such as step 2202 and / or step 2204. Furthermore, each of the additional aspects and examples below may be combined with each other.

[0343] In an example, the monitoring is until reception of: a DCI (2106) in the search space set and the DCI (2108) indicating the TCI state.

[0344] In an example, the monitoring occurs: after receiving a DCI (2106) in the search space set; and until receiving the DCI (2108) indicating the TCI state.

[0345] In an example, the monitoring comprises: monitoring the search space set for the BFR using the QCL parameters of the candidate RS until reception of a DCI (2106) in the search space set; and after receiving the DCI (2108) in the search space set, monitoring the search space set, using the QCL parameters of the candidate RS, until reception of the DCI indicating the TCI state.

[0346] In an example, the monitoring the search space set until the reception of the DCI (2108) indicating the TCI state is continuing monitoring the search space set until the reception of the DCI (2108) indicating the TCI state.

[0347] In an example, process 2200 further comprises a step of receiving one or more radio resource control (RRC) messages (2102).

[0348] In an example, the one or more RRC messages (2102) comprise one or more beam failure recovery (BFR) configuration parameters (e.g., BeamFailureRecoveryConfig) indicating / configuring: PRACH resources; and candidate beams for BFR of a cell in case of beam failure detection of the cell.

[0349] In an example, the cell is a primary cell.Docket No.: 25-1039PCT

[0350] In an example, the primary cell is: a primary master cell group cell (PCell); or a primary secondary cell group cell (PSCell).

[0351] In an example, the BFR configuration parameters comprise at least one of: a PRACH resource parameter (e.g., PRACH-ResourceDedicatedBFR) comprising / indicating a configuration for PRACH transmission for BFR; and / or a recovery search space identifier (e.g., recoverySearchSpaceld) indicating / identifying the search space set to use / monitor for BFR random-access response (RAR).

[0352] In an example, the PRACH resource parameter indicates: the candidate reference signal; and a preamble index (e g., ra-Preamblelndex).

[0353] In an example, the search space set for BFR is a recovery search space set.

[0354] In an example, the search space set is associated with a coreset.

[0355] In an example, the coreset is a BFR coreset.

[0356] In an example, the coreset is not associated with any search space set other than the search space set for BFR.

[0357] In an example, the transmitting the PRACH transmission (2104) is in a time slot after detecting a beam failure; and the monitoring starts from the time slot plus a time duration.

[0358] In an example, the time duration, in slots, is equal to 4 + 2 ■ kmac, where: p is the subcarrier spacing (SCS) configuration for the PRACH transmission; and / cmacis a number of slots provided by a parameter (e.g., kmac).

[0359] In an example, a value of kmacis: indicated by the parameter if present; and zero if absent (e.g., not present or not configured).

[0360] In an example, the monitoring is within a window (e.g., ra-ResponseWindow in BeamFailureRecoveryConfig) indicated / configured by the one or more BFR configuration parameters.

[0361] In an example, the monitoring is monitoring a physical downlink control channel (PDCCH) in the search space set for detection of a DCI format.

[0362] In an example, the DCI format has a cyclic redundancy check (CRC) scrambled by: a cell radio network temporary identifier (C-RNTI); or a modulation and coding scheme (MCS) C-RNTI (MCS-C- RNTI).

[0363] In an example, the candidate RS is: a channel state information (CSI) RS; or a synchronization signal (SS) and physical broadcast channel (PBCH) block (SS / PBCH block).

[0364] In an example, a radio link quality (e.g., L1-RSRP) of the candidate reference signal is greater / larger than, or equal to, a threshold (e.g., Qin.LR threshold indicated by rsrp-ThresholdSSB or rsrp-ThresholdBFR) .

[0365] In an example, the PRACH transmission (2104) comprises a random-access preamble.

[0366] In an example, the random-access preamble is indicated by the preamble index.Docket No.: 25-1039PCT

[0367] In an example, the transmitting the random-access preamble is in one or more random-access occasions.

[0368] In an example, the wireless device (2100) uses the one or more random-access occasions when performing the BFR after / upon selecting the candidate reference signal as a candidate beam.

[0369] In an example, the PRACH resource parameter indicates a list of random-access occasions (e.g., ra-OccasionLisf) comprising the one or more random-access occasions.

[0370] In an example, process 2200 further comprises a step of receiving physical downlink shared channel (PDSCH) receptions using the QCL parameters of the candidate RS until the reception of the DCI (2108) indicating the TCI state.

[0371] In an example, the receiving the PDSCH receptions is receiving the PDSCH receptions using the QCL parameters, of the candidate RS, after receiving the DCI (2106) in the search space set.

[0372] In an example, the PDSCH receptions are received, via the search space set, using the same spatial domain filter used to receive the candidate reference signal.

[0373] In an example, at least one demodulation RS (DM-RS) antenna port of / for PDCCH receptions in the coreset is quasi co-located with the candidate RS.

[0374] In an example, the at least one DM-RS antenna port of / for the PDCCH receptions in the coreset is quasi co-located with the candidate RS with respect to QCL-TypeD.

[0375] In an example, at least one DM-RS antenna port of / for the PDSCH receptions is quasi colocated with the candidate RS.

[0376] In an example, the at least one DM-RS antenna port of / for the PDSCH receptions is quasi colocated with the candidate RS with respect to QCL-TypeD.

[0377] In an example, process 2200 further comprises a step of receiving, via the search space set, PDCCH transmissions using the QCL parameters of the candidate reference signal.

[0378] In an example, PDCCH receptions are received, via the search space set, using the same spatial domain filter used to receive the candidate reference signal.

[0379] In an example, process 2200 further comprises a step of receiving the DCI (2106) in the search space set.

[0380] In an example, a cyclic redundance check (CRC) of DCI (2106) is scrambled by a C-RNTI, or an MCS-C-RNTI, of the wireless device (2100).

[0381] In an example, process 2200 further comprises a step of triggering, after detecting the beam failure, a BFR.

[0382] In an example, the BFR is triggered by initiating a random-access procedure on the cell.

[0383] In an example, the random-access procedure is a contention-free random-access procedure.Docket No.: 25-1039PCT

[0384] In an example, the transmitting the PRACH transmission (2104) is for the random-access procedure.

[0385] In an example, process 2200 further comprises a step of completing the BFR of the cell.

[0386] In an example, the BFR is completed successfully based on successfully completing the random-access procedure.

[0387] In an example, successfully completing the random-access procedure is based on receiving the DCI (2106) in the search space set.

[0388] In an example, the BFR is successfully completed based on receiving the DCI (2106) in the search space set.

[0389] In an example, process 2200 further comprises a step of receiving the DCI (2108) indicating the TCI state.

[0390] In an example, the DCI (2108) indicates the TCI state for a control resource set (coreset).

[0391] In an example, the DCI (2108) comprises a TCI state indicator filed that indicates the TCI state.

[0392] In an example, the TCI state indicator field indicates a codepoint of the TCI state.

[0393] In an example, a DCI format of the DCI (2108) is: DCI format 1_1 ; DCI format 1_2; or DCI format 1_3.

[0394] In an example, the one or more RRC messages (2102) indicate a list of TCI states comprising the TCI state.

[0395] In an example, the one or more RRC messages (2102) comprise one or more PDSCH configuration parameters (e.g., PDSCH-Config) that indicate the list of TCI states.

[0396] In an example, the one or more PDSCH configuration parameters comprise a downlink-or-joint TCI state list parameter (e.g., dl-OrJointTCI-StateToAddModList, dl-OrJointTCI-StateLisf) indicating the list of TCI states.

[0397] In an example, the one or more RRC messages (2102) comprise one or more coreset configuration parameters (e.g., ControlResourceSet), of a coreset, that comprise a follow-unified-TCI- state parameter (e.g., followUnifiedTCI-State) for the coreset

[0398] In an example, when the follow-unified-TCI-state parameter is enabled / configured / present, the wireless device applies an indicated downlink T Cl state or an indicated joint TCI state to PDCCH receptions via the coreset.

[0399] In an example, a coreset index of the coreset is zero.

[0400] In an example, the coreset is associated with at least one common search space (CSS) set other than a Type3 PDCCH search space set.Docket No.: 25-1039PCT

[0401] In an example, the coreset: is associated with at least one of user-specific search space (USS) sets or a Type3 PDCCH sets; and is not associated with a CSS set other than a Type 3 PDCCH search space set.

[0402] In an example, a coreset index of the coreset is not zero.

[0403] In an example, a downlink BWP of the cell comprises the coreset.

[0404] In an example, the downlink BWP is an active downlink BWP of the cell.

[0405] In an example, the TCI state is: a downlink TCI state applied to downlink receptions (e.g., PDCCH / PDSCH / CSI-RS) via the cell; or a joint TCI state applied to both downlink receptions (e.g., PDCCH / PDSCH / CSI-RS) via the cell and uplink transmissions (e.g., PUSCH / PUCCH / SRS) via the cell.

[0406] In an example, the one or more RRC messages (2102) comprise one or more serving cell configuration parameters (e.g., ServingCellConfig) of the cell; and the one or more serving cell configuration parameters comprise a unified TCI state type parameter (e.g., unifiedTCI-StateType) indicating the unified TCI state type for the cell.

[0407] In an example, a first value (e.g., separate) of the unified TCI state type parameter indicates that the cell is configured with: a TCI state list parameter (e.g., dl-OrJointTCI-StateList) for downlink TCI states; and an uplink TCI state list parameter (e.g., ul-TCI-StateLisf) for uplink TCI states.

[0408] In an example, a second value (e.g., joint) of the unified TCI state type parameter indicates that the cell is configured with a TCI state list parameter (e.g., dl-OrJointTCI-StateList) for joint TCI state for both uplink and downlink operations.

[0409] In an example, the TCI state is an active TCI state.

[0410] In an example, the TCI state, indicated by the DCI (2108), is an active TCI state.

[0411] In an example, process 2200 further comprises a step of receiving a MAC CE indicating activation of the TCI state.

[0412] In an example, the MAC CE indicates activation of at least two TCI states comprising the TCI state.

[0413] In an example, the at least two TCI states are from a list of TCI states indicated by the one or more RRC messages (2102).

[0414] In an example, the MAC CE is received after the DCI (2106) and before the DCI (2108).

[0415] In an example, the MAC CE is received after one or more RRC messages (2102) and before the DCI (2108).

[0416] In an example, process 2200 further comprises a step of stopping monitoring PDCCH candidates in the search space set after: receiving the DCI (2108) indicating the TCI state; or applying the TCI state indicated by the DCI (2108).Docket No.: 25-1039PCT

[0417] In an example, the stopping monitoring the PDCCH candidate in the search space set comprises stopping monitoring the coreset associated with the search space set for BFR.

[0418] In an example, process 2200 further comprises a step of, after receiving the DCI (2108) indicating the TCI state (or after applying the TCI state indicated by the DCI (2108)): receiving, via the cell, PDSCH receptions using QCL parameters of a reference signal indicated by the TCI state; receiving, via the coreset, PDCCH receptions using the QCL parameters of the reference signal indicated by the TCI state.

[0419] In an example, the PDCCH receptions are received via a coreset that is: not associated with the search space set for BFR; and / or other than the coreset for BFR.

[0420] In an example, process 2200 further comprises a step of applying the TCI state starting from a first / earliest / initial / starting slot that is at least a number of symbols (e.g., beamAppTime) after a last transmission of an uplink transmission (e.g., PUSCH or PUCCH transmission) with a positive HARQ- ACK corresponding to the DCI (or corresponding to PDSCH(s) scheduled by the DCI).

[0421] In an example, the one or more RRC messages (2102) indicate the number of symbols.

[0422] In an example, the monitoring until reception of the DCI (2108) is (or comprise) monitoring until application of TCI state indicated by the DCI (2108).

[0423] Any of the aspects, and / or examples, of process 2200 in FIG. 22 from the perspective of the wireless device (e.g., receiver perspective) may be implemented in process 2200 in FIG. 19 from the perspective of a base station (e.g., transmitter perspective). The relationship between the wireless device and the base station may be considered as transmitter-receiver reciprocal relationship.

[0424] An apparatus (e.g., a wireless device) comprising one or more processors and memory storing instructions that, when executed by the one or more processors, may cause the apparatus to perform process 2200 and / or any one or more of the above examples.

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

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

[0427] Additional working examples, and embodiments, are provided below. The working examples, and embodiments, may be combined with each other and FIGs. 17-22. Additionally or alternatively, the aspects of the working examples, and embodiments provided below may be substituted for any of the aspects of FIGs. 17-22.Docket No.: 25-1039PCT

[0428] For a cell (or PCell or PSCell), a wireless device may be provided / configu red / ind icated , by PRACH-ResourceDedicatedBFR in one or more RRC messages, a configuration for PRACH transmission. For a PRACH transmission in slot n and according to antenna port quasi co-location parameters associated with a periodic CSI-RS resource configuration or with an SS / PBCH block associated with index of a candidate reference signal (e.g., qnew), the wireless device may monitor, within a window configured by BeamFailureRecoveryConfig in the one or more RRC messages and starting from slot n + 4 + 2M■ kmac, PDCCH in a search space set provided by recoverySearchSpaceld for detection of a DCI format with CRC scrambled by C-RNTI or MCS-C-RNTI, where is the SCS configuration for the PRACH transmission and kmacis a number of slots provided by kmac in the one or more RRC messages, or kmac= 0 if kmac is not provided / indicated / configured in the one or more RRC messages.

[0429] For PDCCH monitoring in a search space set provided by recoverySearchSpaceld and for corresponding PDSCH receptions (e.g., PDSCHs scheduled by DCI(s) received in the search space set), the wireless device may assume / use / determine the same antenna port quasi-collocation parameters as the ones associated with the candidate reference signal (e.g., qnew) until the wireless device receives by higher layers (e.g., RRC, MAC) an activation for a TCI state or any of the parameters tci-StatesPDCCH-ToAddList and / or tci-StatesPDCCH-ToReleaseList, or receives an indication of a TCI state.

[0430] After the wireless device detects a DCI format with CRC scrambled by C-RNTI or MCS-C-RNTI in the search space set provided by recoverySearchSpaceld, the wireless device may continue to monitor PDCCH candidates in the search space set provided by recoverySearchSpaceld until the wireless device receives a MAC CE activation command or a DCI for a TCI state or tci-StatesPDCCH- ToAddList and / or tci-StatesPDCCH-ToReleaseList.

[0431] For PDCCH monitoring in a search space set provided by recoverySearchSpaceld and for corresponding PDSCH receptions (e.g., PDSCHs scheduled by DCI(s) received in the search space set), the wireless device may assume / use / determine the same antenna port quasi-collocation parameters as the ones associated with the candidate reference signal (e.g., qnew) until the wireless device receives by higher layers (e.g., RRC, MAC) an activation for a TCI state or any of the parameters tci-StatesPDCCH-ToAddList and / or tci-StatesPDCCH-ToReleaseList, or receives a DCI indicating a TCI state.

[0432] After the wireless device detects a DCI format with CRC scrambled by C-RNTI or MCS-C-RNTI in the search space set provided by recoverySearchSpaceld, the wireless device may continue to monitor PDCCH candidates in the search space set provided by recoverySearchSpaceld until theDocket No.: 25-1039PCTwireless device receives a MAC CE activation command for a TCI state, or a DCI indicating a TCI state, or tci-StatesPDCCH-ToAddList and / or tci-StatesPDCCH-ToReleasel st.

Claims

Docket No.: 25-1039PCTCLAIMSWhat is claimed is:

1. A method comprising:receiving, by a wireless device (2100), one or more radio resource control (RRC) messages (2102) comprising one or more beam failure recovery (BFR) configuration parameters for BFR of a cell, wherein the one or more BFR configuration parameters indicate:a recovery search space identifier identifying a search space set to monitor for randomaccess response (RAR) for the BFR; anda set of reference signals identifying candidate beams;transmitting, after detecting a beam failure on the cell, a physical random-access channel (PRACH) transmission (2104) associated with a reference signal among the set of reference signals;monitoring, after the PRACH transmission and using the reference signal, physical downlink control channel (PDCCH) in the search space set for detection of a first DCI (2106); andafter receiving the first DCI in the search space set and until receiving a second DCI (2108) indicating a TCI state for at least one control resource set (coreset) in the cell:continuing to monitor PDCCH in the search space set using the reference signal; and receiving PDSCH receptions scheduled by the search space set using the reference signal.

2. A method comprising:transmitting, by a wireless device (2100), a physical random-access channel (PRACH) transmission (2104) indicating a candidate reference signal (RS) for a beam failure recovery (BFR); andmonitoring a search space set, for the BFR, using quasi-collocation (QCL) parameters of the candidate RS until reception of downlink control information (DCI) (2108) indicating a transmission configuration indicator (TCI) state.

3. The method of claim 2, wherein the monitoring is until reception of:a DCI (2106) in the search space set; andthe DCI (2108) indicating the TCI state.

4. The method of any one of claims 2 to 3, wherein the monitoring occurs:after receiving a DCI (2106) in the search space set; anduntil receiving the DCI (2108) indicating the TCI state.

5. The method of any one of claims 2 to 3, wherein the monitoring comprises:Docket No.: 25-1039PCTmonitoring the search space set for the BFR using the QCL parameters of the candidate RS until reception of a DCI (2106) in the search space set; andafter receiving the DCI (2108) in the search space set, monitoring the search space set, using the QCL parameters of the candidate RS, until reception of the DCI indicating the TCI state.

6. The method of any one of claims 2 to 5, wherein the monitoring the search space set until the reception of the DCI (2108) indicating the TCI state is continuing monitoring the search space set until the reception of the DCI (2108) indicating the TCI state.

7. The method of any one of claims 2 to 6, receiving one or more radio resource control (RRC) messages (2102).

8. The method of claim 7, wherein the one or more RRC messages (2102) comprise one or more beam failure recovery (BFR) configuration parameters of a cell indicating:PRACH resources; andcandidate beams for BFR of the cell in case of beam failure detection of the cell.

9. The method of claim 8, wherein the cell is a primary cell.

10. The method of claim 9, wherein the primary cell is:a primary master cell group cell (PCell); ora primary secondary cell group cell (PSCell).

11. The method of any one of claims 8 to 10, wherein the BFR configuration parameters comprise at least one of:a PRACH resource parameter comprising a configuration for PRACH transmission for BFR; and / ora recovery search space identifier identifying the search space set to monitor for BFR randomaccess response (RAR).

12. The method of claim 11 , wherein the PRACH resource parameter indicates:the candidate reference signal; anda preamble index.

13. The method of any one of claims 2 to 12, wherein the search space set for BFR is a recovery search space set.

14. The method of any one of claims 2 to 13, wherein the search space set is associated with a coreset.

15. The method of claim 14, wherein the coreset is a BFR coreset.

16. The method of any one of claims 14 to 15, wherein the coreset is not associated with any search space set other than the search space set for BFR.

17. The method of any one of claims 2 to 16, wherein:Docket No.: 25-1039PCTthe transmitting the PRACH transmission (2104) is in a time slot after detecting a beam failure; andthe monitoring starts from the time slot plus a time duration.

18. The method of claim 17, wherein the time duration, in slots, is equal to 4 + 2^ ■ kmac, where: fi is a subcarrier spacing (SCS) configuration for the PRACH transmission; andAmacis a number of slots provided by a parameter.

19. The method of claim 18, wherein a value of fcmacis:indicated by the parameter if present; andzero if absent, not present, or not configured.

20. The method of any one of claims 8 to 19, wherein the monitoring is within a window indicated by the one or more BFR configuration parameters.

21. The method of any one of claims 2 to 20, wherein the monitoring is monitoring a physical downlink control channel (PDCCH) in the search space set for detection of a DCI format.

22. The method of claim 21 , wherein the DCI format has a cyclic redundancy check (CRC) scrambled by:a cell radio network temporary identifier (C-RNTI); ora modulation and coding scheme (MCS) C-RNTI (MCS-C-RNTI).

23. The method of any one of claims 2 to 22, wherein the candidate RS is:a channel state information (CSI) RS; ora synchronization signal (SS) and physical broadcast channel (PBCH) block (SS / PBCH block).

24. The method of any one of claims 2 to 23, wherein a radio link quality (e.g., L1-RSRP) of the candidate reference signal is greater than, or equal to, a threshold.

25. The method of any one of claims 2 to 24, wherein the PRACH transmission (2104) comprises a random-access preamble.

26. The method of claim 25, wherein the random-access preamble is indicated by the preamble index of the PRACH resource parameter.

27. The method of any one of claims 25 to 26, wherein the transmitting the random-access preamble is in one or more random-access occasions.

28. The method of claim 27, wherein the wireless device (2100) uses the one or more random-access occasions when performing the BFR after selecting the candidate reference signal as a candidate beam.

29. The method of any one of claims 27, wherein the PRACH resource parameter indicates a list of random-access occasions comprising the one or more random-access occasions.Docket No.: 25-1039PCT30. The method of any one of claims 2 to 29, further comprising receiving physical downlink shared channel (PDSCH) receptions using the QCL parameters of the candidate RS until the reception of the DCI (2108) indicating the TCI state.

31. The method of claim 30, wherein the receiving the PDSCH receptions is receiving the PDSCH receptions using the QCL parameters, of the candidate RS, after receiving the DCI (2106) in the search space set.

32. The method of any one of claims 30 to 31 , wherein the PDSCH receptions are received, via the search space set, using the same spatial domain filter used to receive the candidate reference signal.

33. The method of any one of claims 2 to 31 , wherein at least one demodulation RS (DM-RS) antenna port for PDCCH receptions in the coreset is quasi co-located with the candidate RS.

34. The method of claim 33, wherein the at least one DM-RS antenna port for the PDCCH receptions in the coreset is quasi co-located with the candidate RS with respect to QCL-TypeD.

35. The method of any one of claims 2 to 34, wherein at least one DM-RS antenna port for the PDSCH receptions is quasi co-located with the candidate RS.

36. The method of claim 35, wherein the at least one DM-RS antenna port for the PDSCH receptions is quasi co-located with the candidate RS with respect to QCL-TypeD.

37. The method of any one of claims 2 to 36, further comprising receiving, via the search space set, PDCCH transmissions using the QCL parameters of the candidate reference signal.

38. The method of any one of claims 2 to 37, wherein PDCCH receptions are received, via the search space set, using the same spatial domain filter used to receive the candidate reference signal.

39. The method of any one of claims 2 to 36, further comprising receiving the DCI (2106) in the search space set.

40. The method of claim 39, wherein a cyclic redundance check (CRC) of DCI (2106) is scrambled by a C- RNTI, or an MCS-C-RNTI, of the wireless device (2100).

41. The method of any one of claims 2 to 40, further comprising triggering, after detecting the beam failure, a BFR42. The method of claim 41 , wherein the BFR is triggered by initiating a random-access procedure on the cell.

43. The method of claim 42, wherein the random-access procedure is a contention-free random-access procedure.

44. The method of any one of claims 42 to 43, wherein the transmitting the PRACH transmission (2104) is for the random-access procedure.

45. The method of any one of claims 2 to 44, further comprising completing the BFR of the cell.Docket No.: 25-1039PCT46. The method of any one of claims 41 to 45, wherein the BFR is completed successfully based on successfully completing the random-access procedure.

47. The method of any one of claims 46, wherein successfully completing the random-access procedure is based on receiving the DCI (2106) in the search space set.

48. The method of any one of claims 2 to 47, wherein the BFR is successfully completed based on receiving the DCI (2106) in the search space set.

49. The method of any one of claims 2 to 29, further comprising receiving the DCI (2108) indicating the TCI state.

50. The method of any one of claims 2 to 49, wherein the DCI (2108) indicates the TCI state for a coreset.

51. The method of any one of claims 2 to 50, wherein the DCI (2108) comprises a TCI state indicator field that indicates the TCI state.

52. The method of claim 51, wherein the TCI state indicator field indicates a codepoint of the TCI state.

53. The method of any one of claims 2 to 52, wherein a DCI format of the DCI (2108) is:DCI format 1_1;DCI format 1_2; orDCI format 1_3.

54. The method of any one of claims 7 to 53, wherein the one or more RRC messages (2102) indicate a list of TCI states comprising the TCI state.

55. The method of claim 54, wherein the one or more RRC messages (2102) comprise one or more PDSCH configuration parameters that indicate the list of TCI states.

56. The method of claim 55, wherein the one or more PDSCH configuration parameters comprise a downlink-or-joint TCI state list parameter indicating the list of TCI states.

57. The method of any one of claims 7 to 56, wherein the one or more RRC messages (2102) comprise one or more coreset configuration parameters, of a coreset, that comprise a follow-unified-TCI-state parameter for the coreset.

58. The method of claim 57, wherein when the follow-unified-TCI-state parameter is present, the wireless device applies an indicated downlink TCI state or an indicated joint TCI state to PDCCH receptions via the coreset.

59. The method of any one of claims 57 to 58, wherein a coreset index of the coreset is zero.

60. The method of any one of claims 57 to 59, wherein the coreset is associated with at least one common search space (CSS) set other than a Type3 PDCCH search space set.

61. The method of any one of claims 57 to 58, wherein the coreset:is associated with at least one of user-specific search space (USS) sets or a Type3 PDCCH sets; andDocket No.: 25-1039PCTis not associated with a CSS set other than a Type 3 PDCCH search space set.

62. The method of claim 61 , wherein a coreset index of the coreset is not zero.

63. The method of any one of claims 57 to 62, wherein a downlink BWP of the cell comprises the coreset.

64. The method of claim 63, wherein the downlink BWP is an active downlink BWP of the cell.

65. The method of any one of claims 2 to 64, wherein the TCI state is:a downlink TCI state applied to downlink receptions via the cell; ora joint TCI state applied to both downlink receptions via the cell and uplink transmissions via the cell.

66. The method of any one of claims 7 to 65, wherein:the one or more RRC messages (2102) comprise one or more serving cell configuration parameters of the cell; andthe one or more serving cell configuration parameters comprise a unified TCI state type parameter indicating the unified TCI state type for the cell.

67. The method of claim 66, wherein a first value (e.g., separate) of the unified TCI state type parameter indicates that the cell is configured with:a TCI state list parameter for downlink TCI states; andan uplink TCI state list parameter for uplink TCI states.

68. The method of any one of claims 66 to 67, wherein a second value of the unified TCI state type parameter indicates that the cell is configured with a TCI state list parameter for joint TCI state for both uplink and downlink operations.

69. The method of any one of claims 2 to 68, wherein the TCI state, indicated by the DCI (2108), is an active TCI state.

70. The method of claim 69, further comprising receiving a MAC CE indicating activation of the TCI state.

71. The method of claim 70, wherein the MAC CE indicates activation of at least two TCI states comprising the TCI state.

72. The method of claim 71 , wherein the at least two TCI states are from a list of TCI states indicated by the one or more RRC messages (2102).

73. The method of any one of claims 70 to 72, wherein the MAC CE is received after the DCI (2106) and before the DCI (2108).

74. The method of any one of claims 70 to 73, wherein the MAC CE is received after one or more RRC messages (2102) and before the DCI (2108).

75. The method of any one of claims 2 to 74, further comprising stopping monitoring PDCCH candidates in the search space set after at least one of:receiving the DCI (2108) indicating the TCI state; orDocket No.: 25-1039PCTapplying the TCI state indicated by the DCI (2108).

76. The method of claim 75, wherein the stopping monitoring the PDCCH candidate in the search space set comprises stopping monitoring the coreset associated with the search space set for BFR.

77. The method of any one of claims 2 to 75, further comprising, after receiving the DCI (2108) indicating the TCI state or after applying the TCI state indicated by the DCI (2108):receiving, via the cell, PDSCH receptions using QCL parameters of a reference signal indicated by the TCI state; andreceiving PDCCH receptions using the QCL parameters of the reference signal indicated by the TCI state.

78. The method of claim 77, wherein the PDCCH receptions are received via a coreset that is:not associated with the search space set for BFR; and / orother than the coreset for BFR.

79. The method of any one of claims 2 to 76, further comprising applying the TCI state starting from an earliest slot that is at least a number of symbols after a last transmission of an uplink transmission (e.g., PUSCH or PUCCH transmission) with a positive HARQ-ACK corresponding to the DCI or corresponding to PDSCH(s) scheduled by the DCI.

80. The method of claim 79, wherein the one or more RRC messages (2102) indicate the number of symbols.

81. The method of any one of claims 2 to 80, wherein the monitoring until reception of the DCI (2108) is monitoring until application of TCI state indicated by the DCI (2108).

82. 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 81.

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

Images