Reference signal reception using a reference cell

Abstract

A wireless device may communicate with a base station over a channel of a cell. Characteristics of the channel may be evaluated based on a reference signal. The reference signal may be indicated by a transmission configuration indication state, which may be determined based on a list of transmission configuration indication states configured for the cell and / or a reference cell.

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims the benefit of U.S. Provisional Patent Application No. 63 / 432,632, filed December 14, 2022. The above-referenced application is incorporated herein by reference in its entirety. [Background technology]

[0002] A wireless device communicates with a base station, and the wireless device measures and reports channel state information of the communication channel. Summary of the Invention

[0003] The following summary provides a simplified overview of certain features. It is not an extensive overview and is not intended to identify key or critical elements.

[0004] A wireless device can communicate with a base station. The wireless device may be configured to communicate over a channel of a cell. Characteristics of the channel (e.g., channel state information) may be determined by measuring a reference signal. The reference signal may be measured based on a transmission configuration indication state. The transmission configuration indication state may be determined based on a list of transmission configuration indication states configured for the cell. The transmission configuration indication state may also, or alternatively, be determined based on a list of transmission configuration indication states configured for a reference cell (e.g., downlink or joint transmission configuration indication state parameters, and / or unified transmission configuration indication state reference parameters). Measuring the reference signal based on a transmission configuration indication state determined using configuration information of the reference cell may enable accurate channel assessment, for example, even if a transmission configuration indication state list is not configured for the cell.

[0005] These and other features and advantages are described in more detail below. [Brief explanation of the drawings]

[0006] Some examples of various embodiments of the present disclosure are described herein with reference to the drawings.

[0007] [Figure 1A] FIG. 1A shows an example of a communication network. [Figure 1B] FIG. 1B shows an example of a communication network. [Figure 2A] FIG. 2A illustrates an exemplary user plane. [Figure 2B] FIG. 2B shows an example of a control plane configuration. [Figure 3] FIG. 3 shows an example of the protocol layers. [Figure 4A] FIG. 4A illustrates an example of a downlink data flow in a user plane configuration. [Figure 4B] FIG. 4B illustrates an example format of a Medium Access Control (MAC) subheader of a MAC Protocol Data Unit (PDU). [Figure 5A] FIG. 5A shows an example of downlink channel mapping. [Figure 5B] FIG. 5B shows an example of uplink channel mapping. [Figure 6] FIG. 6 illustrates an example of Radio Resource Control (RRC) states and RRC state transitions. [Figure 7] FIG. 7 shows an example of a frame configuration. [Figure 8] FIG. 8 illustrates an exemplary resource configuration for one or more carriers. [Figure 9] FIG. 9 shows an example of the configuration of the bandwidth portion (BWP). [Figure 10A] FIG. 10A illustrates an exemplary carrier aggregation configuration based on component carriers. [Figure 10B] FIG. 10B shows an example group of cells. [Figure 11A] FIG. 11A illustrates an example mapping of one or more synchronization signal / physical broadcast channel (SS / PBCH) blocks. [Figure 11B]FIG. 11B illustrates an example mapping of one or more channel state information reference signals (CSI-RS). [Figure 12A] FIG. 12A shows an example of a downlink beam management procedure. [Figure 12B] FIG. 12B shows an example of an uplink beam management procedure. [Figure 13A] FIG. 13A shows an example of a four-step random access procedure. [Figure 13B] FIG. 13B shows an example of a two-step random access procedure. [Figure 13C] FIG. 13C shows an example of a two-step random access procedure. [Figure 14A] FIG. 14A shows an example of a control resource set (CORESET) configuration. [Figure 14B] FIG. 14B illustrates an example of mapping of control channel elements to resource element groups (CCE-to-REG). [Figure 15A] FIG. 15A illustrates an example of communication between a wireless device and a base station. [Figure 15B] FIG. 15B illustrates exemplary elements of a computing device that may be used to implement any of the various devices described herein. [Figure 16A] FIG. 16A shows an example of uplink and downlink signal transmission. [Figure 16B] FIG. 16B shows an example of uplink and downlink signal transmission. [Figure 16C] FIG. 16C shows an example of uplink and downlink signal transmission. [Figure 16D] FIG. 16D shows an example of uplink and downlink signal transmission. [Figure 17] FIG. 17 shows an example of TCI state activation. [Figure 18] FIG. 18 shows an example of TCI state activation. [Figure 19] FIG. 19 shows an example of CSI measurement. [Figure 20A]FIG. 20A illustrates an example of radio resource control (RRC) configuration parameters for channel state information reference signal (CSI-RS) resources. [Figure 20B] FIG. 20B illustrates example radio resource control (RRC) configuration parameters for aperiodic channel state information (CSI) reporting. [Figure 20C] FIG. 20C illustrates example radio resource control (RRC) configuration parameters for the physical downlink shared channel (PDSCH). [Figure 21A] FIG. 21A shows an example of a CSI measurement. [Figure 21B] FIG. 21B shows an example of a CSI measurement. DETAILED DESCRIPTION OF THE INVENTION

[0008] The accompanying drawings and description provide examples. It should be understood that the examples shown in the drawings and / or described are non-exclusive, and that the features shown and described may be practiced in other examples. The examples are provided for the operation of a wireless communication system that may be used in the technical field of multi-carrier communication systems.

[0009] FIG. 1A illustrates an example of a communication network 100. The communication network 100 may include a mobile communication network. The communication network 100 may include, for example, a public land mobile network (PLMN) operated / managed / run by a network operator. The communication network 100 may include one or more of a core network (CN) 102, a radio access network (RAN) 104, and / or a wireless device 106. The communication network 100 may include, and / or devices within the communication network 100 may communicate with (e.g., via the CN 102), one or more data networks (DNs) 108. The wireless device 106 may communicate with one or more DNs 108, such as public DNs (e.g., the Internet), private DNs, and / or intra-operator DNs. The wireless device 106 may communicate with one or more DNs 108 via the RAN 104 and / or the CN 102. The CN 102 may provide / configure the wireless device 106 with one or more interfaces to one or more DNs 108. As part of its interface functions, the CN 102 may set up an end-to-end connection between the wireless device 106 and one or more DNs 108, authenticate the wireless device 106, and provide / configure charging functionality.

[0010] The wireless device 106 may communicate with the RAN 104 via wireless communication over the air interface. The RAN 104 may communicate with the CN 102 via various communication methods (e.g., wired and / or wireless). The wireless device 106 may establish a connection with the CN 102 via the RAN 104. The RAN 104 may provide / configure, for example, scheduling, radio resource management, and / or retransmission protocols as part of the wireless communication. The communication direction from the RAN 104 to the wireless device 106 over / over the air interface may be referred to as the downlink and / or downlink communication direction. The communication direction from the wireless device 106 to the RAN 104 over / over the air interface may be referred to as the uplink and / or uplink communication direction. Downlink transmissions may be separated and / or distinguished from uplink transmissions based on, for example, at least one of frequency division duplexing (FDD), time division duplexing (TDD), any other duplexing scheme, and / or one or more combinations thereof.

[0011] As used throughout, the term "wireless device" may include one or more of a mobile device, a fixed (e.g., non-mobile) device configured or enabled for wireless communication, a computing device, a node, a wireless communication-enabled device, or any other device capable of transmitting and / or receiving signals. As non-limiting examples, a wireless device may include, for example, a telephone, a cell phone, a Wi-Fi phone, a smartphone, a tablet, a computer, a laptop, a sensor, a meter, a wearable device, an Internet of Things (IoT) device, a hotspot, a cellular repeater, a vehicular roadside unit (RSU), a relay node, an automobile, a wireless user device (e.g., user equipment (UE), user terminal (UT), etc.), an access terminal (AT), a mobile station, a handset, a wireless transmit / receive unit (WTRU), a wireless communication device, and / or any combination thereof.

[0012] The RAN 104 may include one or more base stations (not shown). As used throughout, the term “base station” may include one or more of a base station, node, Node B (NB), Evolved Node B (eNB), gNB, ng-eNB, relay node (e.g., integrated access and backhaul (IAB) node, etc.), donor node (e.g., donor eNB, donor gNB, etc.), access point (e.g., Wi-Fi access point, etc.), transmit / receive point (TRP), computing device, wireless communication enabled device, or other device capable of transmitting and / or receiving signals. A base station may include one or more of each of the elements listed above. For example, a base station may include one or more TRPs. As other non-limiting examples, a base station may include, for example, one or more of a Node B (e.g., associated with Universal Mobile Telecommunications System (UMTS) and / or third-generation (3G) standards), an Evolved Node B (eNB) (e.g., associated with Evolved Universal Terrestrial Radio Access (E-UTRA) and / or fourth-generation (4G) standards), a Remote Radio Head (RRH), a baseband processing unit coupled to one or more Remote Radio Heads (RRHs), a repeater node or relay node used to extend the coverage area of ​​a donor node, a Next Generation Evolved Node B (ng-eNB), a Generation Node B (gNB) (e.g., associated with NR and / or fifth-generation (5G) standards), an Access Point (AP) (e.g., associated with Wi-Fi or other suitable wireless communication standards), other generation base stations, and / or any combination thereof. A base station may include one or more devices, such as at least one base station central device (e.g., a gNB central unit (gNB-CU)) and at least one base station distribution device (e.g., a gNB distribution unit (gNB-DU)).

[0013] A base station (e.g., in the RAN 104) may include one or more sets of antennas for communicating wirelessly (e.g., via an over-the-air interface) with wireless devices 106. One or more base stations may include a set of antennas (e.g., a set of three or any other quantity of sets) for respectively controlling multiple cells or sectors (e.g., three cells, three sectors, any other quantity of cells, or any other quantity of sectors). The size of a cell may be determined by the range over which a receiver (e.g., a base station receiver) can successfully receive transmissions from a transmitter (e.g., a wireless device transmitter) operating within the cell. One or more cells of a base station (e.g., alone or in combination with other cells) may provide / configure wireless coverage to wireless devices 106 over a wide geographic area to support wireless device mobility. A base station including three sectors (e.g., or n sectors, where n refers to any quantity n) may be referred to as a three-sector site (e.g., or n-sector site) or a three-sector base station (e.g., n-sector base station).

[0014] One or more base stations (e.g., in the RAN 104) may be implemented as sector sites having more or less than three sectors. One or more base stations in the RAN 104 may be implemented as an access point, as a baseband processing unit / unit coupled to multiple remote radio heads (RRHs), and / or as a repeater or relay node used to extend the coverage area of ​​a node (e.g., a donor node). The baseband processing unit / unit coupled to the RRHs may be part of a centralized or cloud RAN architecture, for example, where the baseband processing unit / unit may be centralized or virtualized within a pool of baseband processing units / units. The repeater node may amplify and transmit (e.g., transmit, retransmit, rebroadcast, etc.) radio signals received from the donor node. The relay node may perform substantially the same / similar functions as the repeater node. The relay node may decode the radio signals received from the donor node, for example, to remove noise before amplifying and transmitting the radio signals.

[0015] The RAN 104 may be deployed as a homogeneous network of base stations (e.g., macrocell base stations) having similar antenna patterns and / or similar high-level transmit power. The RAN 104 may be deployed as a heterogeneous network of base stations (e.g., different base stations having different antenna patterns). In a heterogeneous network, small cell base stations may be used to provide / configure small coverage areas, for example, coverage areas that overlap with relatively larger coverage areas provided / configured by other base stations (e.g., macrocell base stations). Small coverage areas may be provided / configured in areas of high data traffic (or so-called "hot spots") or areas of weak macrocell coverage. Examples of small cell base stations may include, in order of decreasing coverage area, microcell base stations, picocell base stations, and femtocell or home base stations.

[0016] The examples described herein may be used in various types of communications. For example, the communications may be through the Third Generation Partnership Project (3GPP®) (e.g., one or more network elements similar to those of communications network 100), the communications may be through the Institute of Electrical and Electronics Engineers (IEEE), the communications may be through the International Telecommunications Union (ITU), or the communications may be through the International Organization for Standardization (ISO). 3GPP® has produced specifications for multiple generations of mobile networks: 3G networks known as UMTS, 4G networks known as Long Term Evolution (LTE) and LTE Advanced (LTE-A), and 5G networks known as 5G systems (5GS) and NR systems. 3GPP® may produce specifications for additional generations of communications networks (e.g., 6G, and / or any other generation of communications networks). Examples may be described with reference to one or more elements (e.g., RAN) of a 3GPP® 5G network, referred to as Next Generation RAN (NG-RAN), or any other communication network, such as a 3GPP® network and / or a non-3GPP® network. Examples described herein may apply to other communication networks, such as 3G and / or 4G networks, as well as communication networks that are not yet finalized / specified (e.g., a 3GPP® 6G network), satellite communication networks, and / or any other communication network. NG-RAN may be provided to implement and upgrade 5G radio access technologies, referred to as NR, and to implement other radio access technologies, such as 4G radio access technologies and / or other 3GPP® and / or non-3GPP® radio access technologies.

[0017] FIG. 1B shows an exemplary communication network 150. The communication network may include a mobile communication network. The communication network 150 may include, for example, a PLMN operated / managed / executed by a network operator. The communication network 150 may include a CN 152 (e.g., a 5G Core Network (5G-CN)), a RAN 154 (e.g., an NG-RAN), and / or one or more of wireless devices 156A and 156B (collectively, wireless devices 156). The communication network 150 may include one or more data networks (DNs) 170, and / or devices in the communication network 150 may communicate with them (e.g., via the CN 152). These components may be implemented and operate in substantially the same or similar manner as the corresponding components described with respect to FIG. 1A.

[0018] The CN 152 (e.g., 5G-CN) may provide / configure the wireless device 156 with one or more interfaces to one or more DNs 170, such as a public DN (e.g., the Internet), a private DN, and / or an intra-operator DN. As part of the interface function, the CN 152 (e.g., 5G-CN) may set up an end-to-end connection between the wireless device 156 and one or more DNs, authenticate the wireless device 156, and / or provide / configure charging functionality. The CN 152 (e.g., 5G-CN) may be a service-based architecture that may differ from other CNs (e.g., 3GPP 4G CNs, etc.). The node architecture of the CN 152 (e.g., 5G-CN) may be defined as a network function that provides services via interfaces to other network functions. The network functions of CN152 (e.g., 5G CN) may be implemented in several ways, for example, as network elements on dedicated or shared hardware, as software instances running on dedicated or shared hardware, and / or as virtualized functions instantiated on a platform (e.g., a cloud-based platform).

[0019] The CN 152 (e.g., 5G-CN) may include an access and mobility management function (AMF) device 158A and / or a user plane function (UPF) device 158B, which can be separate components or a single component AMF / UPF device 158. The UPF device 158B may act as a gateway between the RAN 154 (e.g., NG-RAN) and one or more DNs 170. The UPF device 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 one or more DNs 170, quality of service (QoS) processing for the user plane (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink traffic validation), downlink packet buffering, and / or downlink data notification triggering. The UPF device 158B may function as an anchor point for intra / inter radio access technology (RAT) mobility, an external protocol (or packet) data unit (PDU) session point interconnected to one or more DNs, and / or a branching point to support multi-homed PDU sessions. The wireless device 156 may be configured to receive services via PDU sessions, which may be logical connections between the wireless device and the DNs.

[0020] The AMF device 158A may perform functions such as termination of non-access stratum (NAS) signaling, NAS signaling security, access stratum (AS) security management, inter-CN node signaling for mobility between access networks (such as 3GPP access networks and / or non-3GPP networks), idle mode wireless device reachability (e.g., idle mode UE reachability for controlling and executing paging retransmissions), registration area management, intra-system and inter-system mobility support, access authentication, roaming right validation, access permissions including mobility management control (e.g., subscriptions and policies), network slicing support, and / or session management function (SMF) selection. NAS may refer to functions operating between the CN and the wireless device, and AS may refer to functions operating between the wireless device and the RAN.

[0021] CN 152 (e.g., 5G-CN) may include one or more additional network functions that may not be shown in Figure 1B. CN 152 (e.g., 5G-CN) may include one or more devices that implement at least one 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), an Authentication Server Function (AUSF), and / or any other function.

[0022] The RAN 154 (e.g., the NG-RAN) may communicate with the wireless devices 156 via wireless communications (e.g., over an air interface). The wireless devices 156 may communicate with the CN 152 via the RAN 154. The RAN 154 (e.g., the NG-RAN) may include one or more base stations of a first type (e.g., gNBs including gNB 160A and gNB 160B (collectively gNB 160)) and / or one or more base stations of a second type (e.g., ng eNBs including ng-eNB 162A and ng-eNB 162B) (collectively ng eNBs 162). The RAN 154 may include one or more of any quantity of types of base stations. The gNBs 160 and ng eNBs 162 may be referred to as base stations. The base stations (e.g., the gNBs 160 and ng eNBs 162) may include one or more sets of antennas for communicating wirelessly (e.g., over an air interface) with the wireless devices 156. One or more base stations (e.g., gNB 160 and / or ng eNB 162) may include multiple antenna sets for controlling multiple cells (or sectors), respectively. The cells of the base stations (e.g., gNB 160 and ng-eNB 162) may provide wireless coverage to wireless devices 156 over a wide geographic area to support wireless device mobility.

[0023] A base station (e.g., gNB 160 and / or ng-eNB 162) may be connected to the CN 152 (e.g., 5G CN) via a first interface (e.g., an NG interface) and may be connected to other base stations via a second interface (e.g., an Xn interface). The NG and Xn interfaces may be established using a direct physical connection and / or an indirect connection over an underlying transport network, such as an Internet Protocol (IP) transport network. A base station (e.g., gNB 160 and / or ng-eNB 162) may communicate with a wireless device 156 via a third interface (e.g., a Uu interface). A base station (e.g., gNB 160A) may communicate with a wireless device 156A via the Uu interface. The NG, Xn, and Uu interfaces may be associated with protocol stacks. The protocol stacks associated with the interfaces may be used by the network elements shown in FIG. 1B to exchange data and signaling messages. The protocol stacks may include two planes: a user plane and a control plane. Any other quantity of planes may be used (e.g., in a protocol stack): The user plane may handle data of interest to users. The control plane may handle signaling messages of interest to network elements.

[0024] One or more base stations (e.g., gNB 160 and / or ng-eNB 162) may communicate with one or more AMF / UPF devices, such as AMF / UPF 158, via one or more interfaces (e.g., NG interfaces). A base station (e.g., gNB 160A) may communicate with and / or connect to UPF 158B of AMF / UPF 158 via an NG user plane (NG-U) interface. The NG-U interface may provide / enforce delivery (e.g., non-guaranteed delivery) of user plane PDUs between a base station (e.g., gNB 160A) and a UPF device (e.g., UPF 158B). A base station (e.g., gNB 160A) may communicate with and / or connect to an AMF device (e.g., AMF 158A) via an NG control plane (NG-C) interface. The NG-C interface may provide / implement, for example, NG interface management, wireless device context management (e.g., UE context management), wireless device mobility management (e.g., UE mobility management), transport of NAS messages, paging, PDU session management, configuration transfer, and / or alert message transmission.

[0025] A wireless device may access a base station via an interface (e.g., a Uu interface) for user plane and control plane configuration. A base station (e.g., gNB 160) may provide user plane and control plane protocol terminations toward wireless device 156 via the Uu interface. A base station (e.g., gNB 160A) may provide user plane and control plane protocol terminations toward wireless device 156A over the Uu interface associated with a first protocol stack. A base station (e.g., ng-eNB 162) may provide Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminations to wireless device 156 via the Uu interface (e.g., E-UTRA may refer to 3GPP 4G radio access technology). A base station (e.g., ng-eNB 162B) may provide E-UTRA user plane and control plane protocol terminations toward wireless device 156B over the Uu interface associated with a second protocol stack. The user plane and control plane protocol terminations may include, for example, NR user plane and control plane protocol terminations, 4G user plane and control plane protocol terminations, etc.

[0026] The CN 152 (e.g., 5G-CN) may be configured to handle one or more radio accesses (e.g., NR, 4G, and / or any other radio access). Also, an NR network / device (or any first network / device) may be capable of connecting to a 4G core network / device (or any second network / device) in a non-standalone mode (e.g., non-standalone operation). In non-standalone mode / operation, the 4G core network may be used to provide (or at least support) control plane functions (e.g., initial access, mobility, and / or paging). Although only one AMF / UPF 158 is shown in FIG. 1B, one or more base stations (e.g., one or more gNBs and / or one or more ng-eNBs) may be connected to multiple AMF / UPF nodes, e.g., to provide redundancy and / or load sharing across multiple AMF / UPF nodes.

[0027] Interfaces (e.g., Uu, Xn, and / or NG interfaces) between network elements (e.g., the network elements shown in FIG. 1B) may be associated with protocol stacks that the network elements may use to exchange data and signaling messages. A protocol stack may include two planes: a user plane and a control plane. Any other number of planes may be used (e.g., within a protocol stack). The user plane may process data associated with a user (e.g., data of interest to a user). The control plane may process data associated with one or more network elements (e.g., signaling messages of interest to a network element).

[0028] 1A and / or 150 of FIG. 1B may include any quantity / number and / or types of devices, such as, for example, computing devices, wireless devices, mobile devices, handsets, tablets, laptops, Internet of Things (IoT) devices, hotspots, cellular repeaters, computing devices, and / or more generally, user equipment (e.g., UE). While one or more of the above types of devices may be referenced herein (e.g., UE, wireless device, computing device, etc.), it should be understood that any device herein may include any one or more of the above types of devices or similar devices. The communication networks, and any other networks referenced herein, may include LTE networks, 5G networks, satellite networks, and / or any other networks for wireless communication (e.g., any 3GPP network and / or any non-3GPP network). Although the apparatus, systems, and / or methods described herein may generally be described as being implemented in one or more devices (e.g., wireless devices, base stations, eNBs, gNBs, computing devices, etc.) in one or more networks, it will be understood that one or more features and steps may be implemented in any device and / or any network.

[0029] FIG. 2A illustrates an example user plane configuration. The user plane configuration may include, for example, an NR user plane protocol stack. FIG. 2B illustrates an example control plane configuration. The control plane configuration may include, for example, an NR control plane protocol stack. One or more of the user plane configuration and / or control plane configuration may use a Uu interface, which may be between the wireless device 210 and the base station 220. The protocol stacks illustrated in FIG. 2A and FIG. 2B may be substantially the same as or similar to those used for the Uu interface between the wireless device 156A and the base station 160A shown in FIG. 1B, for example.

[0030] A user plane configuration (e.g., an NR user plane protocol stack) may include multiple layers (e.g., five layers or any other amount of layers) implemented in wireless device 210 and base station 220 (e.g., as shown in FIG. 2A). At the bottom of the protocol stack, physical layers (PHYs) 211 and 221 may provide transport services to the upper layers of the protocol stack and may correspond to Layer 1 of the Open Systems Interconnection (OSI) model. Protocol layers above PHY 211 may include a media access control layer (MAC) 212, a radio link control layer (RLC) 213, a packet data convergence protocol layer (PDCP) 214, and / or a service data application protocol layer (SDAP) 215. Protocol layers above PHY 221 may include a media access control layer (MAC) 222, a radio link control layer (RLC) 223, a packet data convergence protocol layer (PDCP) 224, and / or a service data application protocol layer (SDAP) 225. One or more of the four protocol layers above PHY 211 may correspond to Layer 2 or the Data Link layer of the OSI model. One or more of the four protocol layers above PHY 221 may correspond to Layer 2 or the Data Link layer of the OSI model.

[0031] FIG. 3 illustrates an example of protocol layers. The protocol layers may include, for example, protocol layers of an NR user plane protocol stack. One or more services may be provided between the protocol layers. The SDAP (e.g., the SDAPS 215 and 225 shown in FIGS. 2A and 3) may perform quality of service (QoS) flow processing. A wireless device (e.g., wireless devices 106, 156A, 156B, and 210) may receive a service via a PDU session, which may be a logical connection between the wireless device and the DN. A PDU session may have one or more QoS flows 310. The CN's UPF (e.g., the UPF 158B) may map IP packets to one or more QoS flows of the PDU session based on, for example, one or more QoS requirements (e.g., with respect to delay, data rate, error rate, and / or any other quality / service requirement). The SDAP 215 and 225 may perform mapping / demapping between one or more QoS flows 310 and one or more radio bearers 320 (e.g., data radio bearers). The mapping / undemoping between one or more QoS flows 310 and radio bearers 320 may be determined by the SDAP 225 of the base station 220. The SDAP 215 of the wireless device 210 may be informed of the mapping between the QoS flows 310 and radio bearers 320 via reflected mapping and / or control signaling received from the base station 220. For reflected mapping, the SDAP 225 of the base station 220 may mark downlink packets with a QoS flow indicator (QFI) that may be monitored / detected / identified / indicated / observed by the SDAP 215 of the wireless device 210 to determine the mapping / undemoping between one or more QoS flows 310 and radio bearers 320.

[0032] PDCPs (e.g., PDCPs 214 and 224 shown in FIGS. 2A and 3) may perform, for example, header compression / decompression to reduce the amount of data that may need to be sent (e.g., transmitted) over the air interface, encryption / decryption to prevent unauthorized decoding of data sent (e.g., transmitted) over the air interface, and / or integrity protection (e.g., to ensure that control messages originate from the intended source). PDCPs 214 and 224 may perform retransmission of undelivered packets, sequential delivery and reordering of packets, and / or removal of duplicately received packets, for example, due to handover (e.g., intra-gNB handover). PDCPs 214 and 224 may perform packet duplication, for example, to improve the likelihood of a packet being received. A receiver may receive packets duplicately and remove any duplicate packets. Packet duplication may be useful for certain services, such as services requiring high reliability.

[0033] The PDCP layer (e.g., PDCP 214 and 224) may perform mapping / undapping between split radio bearers and RLC channels (e.g., RLC channel 330) (e.g., in a dual connectivity scenario / configuration). Dual connectivity may refer to a technology that enables a wireless device to communicate with multiple cells (e.g., two cells), or more broadly, multiple cell groups, including a master cell group (MCG) and a secondary cell group (SCG). A split bearer may be configured and / or used, for example, when a single radio bearer (e.g., one of the radio bearers provided / configured by PDCP 214 and 224 as a service to SDAP 215 and 225) is handled by a cell group in dual connectivity. The PDCP 214 and 224 may map / undap the split radio bearer between the RLC channel 330 belonging to the cell group.

[0034] The RLC layer (e.g., RLC 213 and 223) may perform segmentation, retransmission via automatic repeat request (ARQ), and / or removal of duplicate data units received from the MAC layer (e.g., MAC 212 and 222, respectively). The RLC layer (e.g., RLC 213 and 223) may support multiple transmission modes (e.g., three transmission modes: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM)). The RLC layer may perform one or more of the above functions, for example, based on the transmission mode in which the RLC layer is operating. RLC configuration may be per logical channel. RLC configuration may be independent of numerology and / or transmission time interval (TTI) duration (or other period). The RLC layer (e.g., RLC 213 and 223) may provide / configure RLC channels as a service to the PDCP layer (e.g., PDCP 214 and 224, respectively) as shown in FIG. 3.

[0035] The MAC layer (e.g., MAC 212 and 222) may perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. Multiplexing / demultiplexing may include multiplexing / demultiplexing data units / data portions belonging to one or more logical channels into / from transport blocks (TBs) delivered to / from the PHY layer (e.g., PHY 211 and 221, respectively). The MAC layer of the base station (e.g., MAC 222) may be configured to perform scheduling, scheduling information reporting, and / or priority handling between wireless devices via dynamic scheduling. Scheduling may be performed by the base station (e.g., base station 220 at MAC 222) for the downlink and / or uplink. The MAC layer (e.g., MAC 212 and 222) may be configured to perform error correction via hybrid automatic repeat request (HARQ) (e.g., one HARQ entity per carrier in the case of carrier aggregation (CA)), priority handling between logical channels of the wireless device 210 via logical channel prioritization, and / or padding. The MAC layer (e.g., MAC 212 and MAC 222) may support one or more numerologies and / or transmission timings. Mapping restrictions in logical channel prioritization may control which numerologies and / or transmission timings a logical channel may use. The MAC layer (e.g., MAC 212 and 222) may provide / configure logical channels 340 as services to the RLC layer (e.g., RLC 213 and 223).

[0036] The PHY layer (e.g., PHYs 211 and 221) may perform, for example, mapping of transport channels to physical channels and / or digital and analog signal processing functions to transmit and / or receive information (e.g., over an air interface). The digital and / or analog signal processing functions may include, for example, encoding / decoding and / or modulation / demodulation. The PHY layer (e.g., PHYs 211 and 221) may perform multi-antenna mapping. The PHY layer (e.g., PHYs 211 and 221) may provide / configure one or more transport channels (e.g., transport channel 350) as services to the MAC layer (e.g., MACs 212 and 222, respectively).

[0037] FIG. 4A shows an example of a downlink data flow in a user plane configuration. The user plane configuration may include, for example, the NR user plane protocol stack shown in FIG. 2A. One or more TBs may be generated, for example, based on the data flow through the user plane protocol stack. As shown in FIG. 4A, a downlink data flow of three IP packets (n, n+1, and m) through the NR user plane protocol stack may generate two TBs (e.g., at base station 220). An uplink data flow through the NR user plane protocol stack may be similar to the downlink data flow shown in FIG. 4A. The three IP packets (n, n+1, and m) may be determined from the two TBs, for example, based on the uplink data flow through the NR user plane protocol stack. A first quantity of packets (e.g., three or any other quantity) may be determined from a second quantity of TBs (e.g., two or another quantity).

[0038] A downlink data flow may be initiated, for example, when the SDAP 225 receives three IP packets (or other quantity of IP packets) from one or more QoS flows and maps the three packets (or other quantity of packets) to radio bearers (e.g., radio bearers 402 and 404). The SDAP 225 may map IP packets n and n+1 to the first radio bearer 402 and map IP packet m to the second radio bearer 404. An SDAP header (labeled with an “H” before each SDAP SDU shown in FIG. 4A ) may be added to the IP packets to generate an SDAP PDU, which may be referred to as a PDCP SDU. Data units transferred to and from higher protocol layers may be referred to as service data units (SDUs) of the lower protocol layer, and data units transferred to and from lower protocol layers may be referred to as protocol data units (PDUs) of the higher protocol layer. As shown in FIG. 4A, the data unit from the SDAP 225 may be an SDU of the lower protocol layer PDCP 224 (eg, a PDCP SDU) or a PDU of the SDAP 225 (eg, an SDAP PDU).

[0039] Each protocol layer (e.g., the protocol layers shown in FIG. 4A), or at least some of the protocol layers, may perform its own function (e.g., one or more functions of each protocol layer described with reference to FIG. 3), add a corresponding header, and / or forward its respective output to the next lower layer (e.g., its respective lower layer). PDCP 224 may perform IP header compression and / or encryption. PDCP 224 may forward its output (e.g., PDCP PDUs, which are RLC SDUs) to RLC 223. RLC 223 may optionally perform segmentation (e.g., as shown for IP packets in FIG. 4A). RLC 223 may forward its output (e.g., two RLC PDUs, which are two MAC SDUs, generated by adding respective subheaders to two SDU segments (SDU Segs)) to MAC 222. MAC 222 may multiplex the amount / number of RLC PDUs (MAC SDUs). The MAC 222 may attach a MAC subheader to the RLC PDU (MAC SDU) to form a TB. The MAC subheader may be distributed throughout the MAC PDU (e.g., in an NR configuration, as shown in FIG. 4A). The MAC subheader may be located entirely at the beginning of the MAC PDU (e.g., in an LTE configuration). The NR MAC PDU structure may reduce processing time and / or associated delay, for example, if the MAC PDU subheader is calculated before assembling the complete MAC PDU.

[0040] 4B shows an example format of a MAC subheader in a MAC PDU. The MAC PDU may include a MAC subheader (H) and a MAC SDU. Each of the one or more MAC subheaders may include an SDU length field for indicating the length (e.g., bytes) of the MAC SDU to which the MAC subheader corresponds, a logical channel identifier (LCID) field for identifying / indicating the logical channel on which the MAC SDU originated to assist 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.

[0041] One or more MAC Control Elements (CEs) may be added or inserted into a MAC PDU by a MAC layer, such as MAC 223 or MAC 222. As shown in FIG. 4B, two MAC CEs may be inserted / appended before two MAC PDUs. A MAC CE may be inserted / appended at the beginning of a MAC PDU for downlink transmission (as shown in FIG. 4B). One or more MAC CEs may be inserted / appended at the end of a MAC PDU for uplink transmission. MAC CEs may be used for in-band control signaling. Exemplary MAC CEs may include scheduling-related MAC CEs such as buffer status reports and power headroom reports, activation / deactivation MAC CEs (e.g., MAC CEs for activating / deactivating PDCP duplicate detection, channel state information (CSI) reports, sounding reference signal (SRS) transmissions, and pre-configured components), discontinuous reception (DRX)-related MAC CEs, timing advance MAC CEs, and random access-related MAC CEs. The MAC CE may be preceded by a MAC subheader of a format similar to that described in MAC subheader for MAC SDUs and may be identified with a reserved value in the LCID field indicating the type of control information contained in the corresponding MAC CE.

[0042] FIG. 5A shows an example of downlink channel mapping. Uplink channel mapping may include downlink channel-to-channel mapping (e.g., logical channels, transport channels, and physical channels). FIG. 5B shows an example of uplink channel mapping. Uplink channel mapping may include uplink channel-to-channel mapping (e.g., logical channels, transport channels, and physical channels). Information may be passed through / via channels between the RLC, MAC, and PHY layers of a protocol stack (e.g., an NR protocol stack). Logical channels may be used between the RLC and MAC layers. Logical channels may be classified / denoted as control channels that can carry control and / or configuration information (e.g., in the NR control plane) or as traffic channels that can carry data (e.g., in the NR user plane). Logical channels may be classified / denoted as dedicated logical channels that may be dedicated to a specific wireless device and / or as common logical channels that may be used by two or more wireless devices (e.g., a group of wireless devices).

[0043] A logical channel may be defined by the type of information it carries. The set of logical channels (e.g., in an NR configuration) may include one or more channels described below. The Paging Control Channel (PCCH) may include or carry one or more paging messages used to page wireless devices whose locations are not known to the network at the cell level. The Broadcast Control Channel (BCCH) may include / carry system information messages in the form of a Master Information Block (MIB) and several System Information Blocks (SIBs). System information messages may be used by wireless devices to obtain information about how the cell is configured and how to operate within the cell. The Common Control Channel (CCCH) may include / carry control messages along with random access. The Dedicated Control Channel (DCCH) may include / carry control messages to / from specific wireless devices and configure wireless devices with configuration information. The Dedicated Traffic Channel (DTCH) may include / carry user data to / from specific wireless devices.

[0044] Transport channels may be used between the MAC layer and the PHY layer. Transport channels may be defined by how the information they carry is transmitted / transmitted (e.g., over the air interface). The set of transport channels (which may be defined, for example, by an NR configuration or any other configuration) may include one or more of the following channels: Paging Channel (PCH) may include / carry paging messages originated from PCCH; Broadcast Channel (BCH) may include / carry MIBs from BCCH; Downlink Shared Channel (DL-SCH) may include / carry downlink data and signaling messages, including SIBs from BCCH; Uplink Shared Channel (UL-SCH) may include / carry uplink data and signaling messages; Random Access Channel (RACH) may provide wireless devices with access to the network without prior scheduling.

[0045] The PHY layer may pass / transfer information between processing levels of the PHY layer using physical channels. A physical channel may have an associated set of time-frequency resources for carrying information of one or more transport channels. The PHY layer may generate control information to support lower-level operations of the PHY layer. The PHY layer may provide / transfer control information to lower levels of the PHY layer via physical control channels (e.g., referred to as L1 / L2 control channels). The set of physical channels and physical control channels (which may be defined, for example, by an NR configuration or any other configuration) may include one or more of the following channels: The Physical Broadcast Channel (PBCH) may include / carry MIBs from the BCH. The Physical Downlink Shared Channel (PDSCH) may include / carry downlink data and signaling messages from the DL-SCH and paging messages from the PCH. The Physical Downlink Control Channel (PDCCH) may include / carry downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling grants, and uplink power control commands. The Physical Uplink Shared Channel (PUSCH) may include / carry uplink data and signaling messages from the UL-SCH, as well as uplink control information (UCI) in some cases, as described below. The Physical Uplink Control Channel (PUCCH) may include / carry UCI, which may include HARQ acknowledgments, channel quality indicators (CQIs), precoding matrix indicators (PMIs), rank indicators (RIs), and scheduling requests (SRs). The Physical Random Access Channel (PRACH) may be used for random access.

[0046] The physical layer may generate physical signals to support low-level operations of the physical layer, which may be similar to physical control channels. As shown in Figures 5A and 5B, the physical layer signals (which may be defined, for example, by an NR configuration or other configuration) may include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DM-RS), a sounding reference signal (SRS), a phase tracking reference signal (PT RS), and / or any other signals.

[0047] One or more channels (e.g., logical channels, transport channels, physical channels, etc.) may be used to perform functions associated with a control plane protocol stack (e.g., an NR control plane protocol stack). FIG. 2B shows an example of a control plane configuration (e.g., an NR control plane protocol stack). In FIG. 2B, the control plane configuration (e.g., an NR control plane protocol stack) may use one or more substantially identical / similar protocol layers (e.g., PHYs 211 and 221, MACs 212 and 222, RLCs 213 and 223, and PDCPs 214 and 224) as an exemplary user plane configuration (e.g., an NR user plane protocol stack). The similar four protocol layers may include PHYs 211 and 221, MACs 212 and 222, RLCs 213 and 223, and PDCPs 214 and 224. The control plane configuration (e.g., NR control plane stack) may have radio resource control (RRC) 216 and 226 and NAS protocols 217 and 237 on top of the control plane configuration (e.g., NR control plane protocol stack), for example, instead of having SDAPs 215 and 225. The control plane configuration may include an AMF 230 that includes the NAS protocol 237.

[0048] NAS protocols 217 and 237 may provide control plane functions between wireless device 210 and AMF 230 (e.g., AMF 158A or any other AMF), and / or more generally, between wireless device 210 and a CN (e.g., CN 152 or any other CN). NAS protocols 217 and 237 may provide control plane functions between wireless device 210 and AMF 230 via signaling messages referred to as NAS messages. There may not be a direct path between wireless device 210 and AMF 230 over which NAS messages may be transmitted. NAS messages may be transported using ASs of the Uu and NG interfaces. NAS protocols 217 and 237 may provide control plane functions such as authentication, security, connection setup, mobility management, session management, and / or any other functions.

[0049] The RRC layers 216 and 226 may provide / configure control plane functionality between the wireless device 210 and the base station 220, and / or more generally, between the wireless device 210 and the RAN (e.g., the base station 220). The RRC layers 216 and 226 may provide / configure control plane functionality between the wireless device 210 and the base station 220 via signaling messages, which may be referred to as RRC messages. The RRC messages may be transmitted / conveyed between the wireless device 210 and the RAN (e.g., the base station 220) using signaling radio bearers and the same / similar PDCP, RLC, MAC, and PHY protocol layers. The MAC layer may multiplex control plane and user plane data onto the same TB. The RRC layers 216 and 226 may provide / configure control plane functions such as one or more of the following: broadcasting system information related to the AS and the NAS; paging initiated by the CN or the RAN; establishment, maintenance, and release of an RRC connection between the wireless device 210 and the RAN (e.g., base station 220); security functions including key management; establishment, configuration, maintenance, and release of signaling and data radio bearers; mobility functions; QoS management functions; wireless device measurement reports (e.g., wireless device measurement reports) and control of reports; detection and recovery from radio link failure (RLF); and / or NAS message transfer functions. As part of establishing an RRC connection, the RRC layers 216 and 226 may establish an RRC context, which may involve configuring parameters for communications between the wireless device 210 and the RAN (e.g., base station 220).

[0050] 6 illustrates examples of RRC states and RRC state transitions. The RRC state of a wireless device may be changed to another RRC state (e.g., an RRC state transition of a wireless device). The wireless device may be substantially identical to or similar to wireless device 106, 210, or any other wireless device. The wireless device may be in at least one of a plurality of states, such as three RRC states including RRC connected 602 (e.g., RRC_CONNECTED), RRC idle 606 (e.g., RRC_IDLE), and RRC inactive 604 (e.g., RRC_INACTIVE). RRC inactive 604 may be RRC connected but inactive.

[0051] An RRC connection may be established for a wireless device. For example, this may be during an RRC connected state. During an RRC connected state (e.g., during RRC connected 602), the wireless device may have an established RRC context and may have at least one RRC connection with a base station. The base station may resemble one of one or more base stations (e.g., one or more base stations of the RAN 104 shown in FIG. 1A, one of the gNB 160 or ng-eNB 162 shown in FIG. 1B, the base station 220 shown in FIGS. 2A and 2B, or any other base station). The base station to which the wireless device is connected (e.g., has established an RRC connection) may have the RRC context for the wireless device. The RRC context, which may be referred to as a wireless device context (e.g., a UE context), may include parameters for communication between the wireless device and the base station. These parameters may include, for example, one or more of the following: AS context, radio link configuration parameters, bearer configuration information (e.g., associated with data radio bearers, signaling radio bearers, logical channels, QoS flows, and / or PDU sessions), security information, and / or layer configuration information (e.g., PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information). During the RRC connected state (e.g., RRC connected 602), the mobility of the wireless device may be managed / controlled by the RAN (e.g., RAN 104 or NG RAN 154). The wireless device may measure received signal levels (e.g., reference signal level, reference signal received power, reference signal received quality, received signal strength indicator, etc.) based on one or more signals transmitted from the serving cell and neighboring cells. The wireless device may report these measurements to a serving base station (e.g., a base station currently serving the wireless device). The serving base station of the wireless device may request a handover to a cell of one of the neighboring base stations, for example, based on the reported measurements. The RRC state may transition from an RRC connected state (eg, RRC connected 602) to an RRC idle state (eg, RRC idle 606) via a connection release procedure 608.The RRC state may transition from an RRC connected state (eg, RRC connected 602) to an RRC inactive state (eg, RRC inactive 604) via a connection deactivation procedure 610.

[0052] An RRC context may not be established for the wireless device. For example, this may be during an RRC idle state. During an RRC idle state (e.g., RRC idle 606), an RRC context may not be established for the wireless device. During an RRC idle state (e.g., RRC idle 606), the wireless device may not have an RRC connection with a base station. During an RRC idle state (e.g., RRC idle 606), the wireless device may be in a sleep state (e.g., to conserve battery power) most of the time. The wireless device may wake up periodically (e.g., every discontinuous reception (DRX) cycle) to monitor for paging messages (e.g., paging messages configured from the RAN). Mobility of the wireless device may be managed by the wireless device via a cell reselection procedure. The RRC state may transition from an RRC idle state (e.g., RRC idle 606) to an RRC connected state (e.g., RRC connected 602) via a connection establishment procedure 612, which may involve a random access procedure.

[0053] A previously established RRC context may be maintained for the wireless device. For example, this may be during an RRC inactive state. During an RRC inactive state (e.g., RRC inactive 604), a previously established RRC context may be maintained in the wireless device and the base station. RRC context maintenance may enable / allow a fast transition to an RRC connected state (e.g., RRC connected 602) with less signaling overhead compared to a transition from an RRC idle state (e.g., RRC idle 606) to an RRC connected state (e.g., RRC connected 602). During the RRC inactive state (e.g., RRC inactive 604), the wireless device is asleep, and the mobility of the wireless device may be managed / controlled by the wireless device via cell reselection. The RRC state may transition from an RRC inactive state (e.g., RRC inactive 604) to an RRC connected state (e.g., RRC connected 602) via a connection resumption procedure 614. The RRC state may transition from an RRC inactive state (e.g., RRC inactive 604) to an RRC idle state (e.g., RRC idle 606) via a connection release procedure 616 that is the same as or similar to the connection release procedure 608.

[0054] The RRC state may be associated with a mobility management mechanism. During an RRC idle state (e.g., RRC idle 606) and an RRC inactive state (e.g., RRC inactive 604), mobility may be managed / controlled by the wireless device via cell reselection. The purpose of mobility management during an RRC idle state (e.g., RRC idle 606) or an RRC inactive state (e.g., RRC inactive 604) may be to enable / allow the network to notify the wireless device of an event via a paging message without having to broadcast the paging message throughout the mobile communication network. A mobility management mechanism used during an RRC idle state (e.g., RRC idle 606) or an RRC idle state (e.g., RRC inactive 604) may enable / allow the network to track the wireless device at a cell group level, for example, so that a paging message may be broadcast over the cells of the cell group in which the wireless device is currently located (e.g., rather than transmitting the paging message throughout the mobile communication network). The mobility management mechanism in the RRC idle state (e.g., RRC idle 606) and the RRC inactive state (e.g., RRC inactive 604) may track wireless devices at a cell group level. The mobility management mechanism may perform tracking using, for example, different levels of grouping granularity. There may be multiple levels of cell grouping granularity (e.g., 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)).

[0055] The tracking area may be used to track a wireless device (e.g., track the location of a wireless device at the CN level). A CN (e.g., CN 102, 5G CN 152, or any other CN) may send a list of TAIs associated with wireless device registration areas (e.g., UE registration areas) to the wireless device. The wireless device may perform a registration update with the CN to enable the CN to update the location of the wireless device, e.g., to provide the wireless device with a new UE registration area if the wireless device moves (e.g., via cell reselection) to a cell associated with a TAI that is not included in the list of TAIs associated with the UE registration area.

[0056] The RAN area may be used to track a wireless device (e.g., the location of the wireless device at the RAN level). For a wireless device in an RRC inactive state (e.g., RRC inactive 604), the wireless device may be assigned / provisioned / configured in a RAN notification area. The RAN notification area may include one or more cell identities (e.g., a list of RAIs and / or a list of TAIs). A base station may belong to one or more RAN notification areas. A cell may belong to one or more RAN notification areas. The wireless device may perform a notification area update with the RAN to update the RAN notification area of ​​the wireless device, for example, when the wireless device moves (e.g., via cell reselection) to a cell not included in the RAN notification area assigned / provisioned / configured to the wireless device.

[0057] A base station that stores the RRC context for a wireless device or a last serving base station for a wireless device may be referred to as an anchor base station. The anchor base station may maintain the RRC context for the wireless device for at least as long as the wireless device remains in the RAN notification area of ​​the anchor base station and / or for as long as the wireless device remains in an RRC inactive state (e.g., RRC inactive 604).

[0058] A base station (e.g., gNB 160 of FIG. 1B or any other base station) may be divided into two parts: a central unit (e.g., a base station central unit such as a gNB CU) and one or more distributed units (e.g., base station distributed units such as a gNB DU). The base station central unit (CU) may be coupled to one or more base station distributed units (DUs) using an F1 interface (e.g., an F1 interface defined in the NR configuration). The base station CU may include an RRC layer, a PDCP layer, and an SDAP layer. The base station distributed unit (DU) may include an RLC layer, a MAC layer, and a PHY layer.

[0059] Physical signals and physical channels (e.g., FIGS. 5A and 5B) may be mapped onto one or more symbols (e.g., orthogonal frequency division multiplexing (OFDM) symbols in an NR configuration, or any other symbols). OFDM is a multicarrier communication scheme that transmits / conveys data over F orthogonal subcarriers (or tones). The data may be mapped to a series of complex symbols (e.g., M-quadrature amplitude modulation (M-QAM) symbols, M-phase shift keying (M-PSK) symbols, or any other modulation symbols), called source symbols, which are split into F parallel symbol streams before transmission. The F parallel symbol streams may be treated as if they were in the frequency domain. The F parallel symbols may be used as input to an inverse fast Fourier transform (IFFT) block, which converts them to the time domain. The IFFT block may take F source symbols, one at a time, from each of the F parallel symbol streams. The IFFT block may use each source symbol to modulate the amplitude and phase of one of the F sinusoidal basis functions corresponding to the F orthogonal subcarriers. The output of the IFFT block may be F time-domain samples representing a sum of the F orthogonal subcarriers. The F time-domain samples may form a single OFDM symbol. The OFDM symbol provided / output by the IFFT block may be transmitted / sent over the air interface at a carrier frequency, for example, after one or more processes (e.g., adding a cyclic prefix) and upconversion. The F parallel symbol streams may be mixed, for example, using a Fast Fourier Transform (FFT) block before being processed by the IFFT block. This operation may generate a Discrete Fourier Transform (DFT) precoded OFDM symbol, which may be used by one or more wireless devices in the uplink to reduce the peak-to-average power ratio (PAPR). To recover the data mapped to the source symbols, inverse processing may be performed on the OFDM symbols at the receiver using the FFT block.

[0060] FIG. 7 shows an example of a frame configuration. A frame may include, for example, an NR radio frame in which OFDM symbols may be grouped. A frame (e.g., an NR radio frame) may be identified / indicated by a system frame quantity / number (SFN) or any other value. The SFN may repeat for a period of 1024 frames. One NR frame may be 10 milliseconds (ms) in duration and may include 10 subframes, each of which is 1 ms in duration. A subframe may be divided into one or more slots (e.g., according to numerology and / or different subcarrier spacing). Each of the one or more slots may include, for example, 14 OFDM symbols per slot. Any amount of symbols, slots, or duration may be used for any time interval.

[0061] The duration of a slot may depend on the numerology used for the OFDM symbols of the slot. For example, flexible numerology may be supported to accommodate different deployments (e.g., from cells with carrier frequencies below 1 GHz to cells with carrier frequencies in the mm-wave range). For example, flexible numerology may be supported in an NR configuration or any other radio configuration. The numerology may be defined in terms of subcarrier spacing and / or cyclic prefix duration. The subcarrier spacing may be scaled up by a power of two from the baseline subcarrier spacing of 15 kHz. The cyclic prefix duration may be scaled down by a power of two from the baseline cyclic prefix duration of 4.7 microseconds, for example, for numerology in an NR configuration or any other radio configuration. The numerology may be defined at the following subcarrier spacing / cyclic prefix duration combinations: 15 kHz / 4.7 microseconds, 30 kHz / 2.3 microseconds, 60 kHz / 1.2 microseconds, 120 kHz / 0.59 microseconds, 240 kHz / 0.29 microseconds, and / or any other subcarrier spacing / cyclic prefix duration combination.

[0062] A slot may have a fixed amount / number of OFDM symbols (e.g., 14 OFDM symbols). Numerologies with higher subcarrier spacing may have shorter slot durations and more slots per subframe. An example of a numerology-dependent slot duration and slot transmission structure per subframe is shown in Figure 7 (a numerology with 240 kHz subcarrier spacing is not shown in Figure 7). A subframe (e.g., in an NR configuration) may be used as a numerology-independent time reference. A slot may be used as the unit by which uplink and downlink transmissions are scheduled. Scheduling (e.g., in an NR configuration) may be decoupled from the slot duration. Scheduling may start at any OFDM symbol. Scheduling may continue for as many symbols as necessary for transmission, e.g., to support low latency. These partial slot transmissions may be referred to as minislot or subslot transmissions.

[0063] FIG. 8 shows an example resource configuration of one or more carriers. The resource configuration may include slots in the time and frequency domains for an NR carrier or any other carrier. A slot may include resource elements (REs) and resource blocks (RBs). A resource element (RE) may be the smallest physical resource (e.g., an NR configuration). An RE may span one OFDM symbol in the time domain by one subcarrier in the frequency domain, as shown in FIG. 8. An RB may span 12 consecutive REs in the frequency domain, as shown in FIG. 8. A carrier (e.g., an NR carrier) may be limited to a particular amount of RBs and / or subcarriers (e.g., 275 RBs or 275 × 12 = 3300 subcarriers) in width. If used, such restrictions may limit the carrier (e.g., an NR carrier) frequency based on subcarrier spacing (e.g., carrier frequencies of 50, 100, 200, and 400 MHz for subcarrier spacings of 15, 30, 60, and 120 kHz, respectively). The 400 MHz bandwidth may be set based on the 400 MHz bandwidth limit per carrier. Any other bandwidth may be set based on the bandwidth limit per carrier.

[0064] A single numerology may be used across the entire bandwidth of a carrier (e.g., NR as shown in FIG. 8). In other exemplary configurations, multiple numerologies may be supported on the same carrier. NR and / or other access technologies may support wide carrier bandwidths (e.g., up to 400 MHz with 120 kHz subcarrier spacing). Not all wireless devices may be able to receive the entire carrier bandwidth (e.g., due to hardware limitations and / or different wireless device capabilities). Reception and / or utilization of the entire carrier bandwidth may be prohibited, for example, with respect to wireless device power consumption. A wireless device may adapt the size of its reception bandwidth, for example, based on the amount of traffic the wireless device is scheduled to receive (e.g., to reduce power consumption and / or for other purposes). Such adaptation may be referred to as bandwidth adaptation.

[0065] The configuration of one or more bandwidth portions (BWPs) may support one or more wireless devices that cannot receive the entire carrier bandwidth. The BWP may support, for example, bandwidth adaptation for such wireless devices that cannot receive the entire carrier bandwidth. A BWP (e.g., a BWP for an NR configuration) may be defined by a subset of contiguous RBs on a carrier. A wireless device may be configured (e.g., via the RRC layer) with one or more downlink BWPs per serving cell and one or more uplink BWPs per serving cell (e.g., up to four downlink BWPs per serving cell and up to four uplink BWPs per serving cell). One or more of the BWPs configured for a serving cell may be active, for example, at a given time. One or more BWPs may be referred to as the active BWPs of the serving cell. A serving cell may have one or more first active BWPs on an uplink carrier and one or more second active BWPs on a secondary uplink carrier, for example, if the serving cell is configured with a secondary uplink carrier.

[0066] A downlink BWP from a set of configured downlink BWPs may be linked with an uplink BWP from a set of configured uplink BWPs (e.g., for unpaired spectrum). A downlink BWP and an uplink BWP may be linked if, for example, the downlink BWP index of the downlink BWP and the uplink BWP index of the uplink BWP are the same. A wireless device may expect the center frequency of the downlink BWP to be the same as the center frequency of the uplink BWP (e.g., for unpaired spectrum).

[0067] A base station may configure a wireless device with one or more control resource sets (CORESETs) for at least one search space. The base station may configure a wireless device with one or more CORESETs for downlink BWPs, for example, for a set of downlink BWPs configured on a primary cell (PCell) or a secondary cell (SCell). A search space may include a set of locations in the time and frequency domain where the wireless device may monitor / discover / detect / identify control information. The search space may be a wireless device-specific search space (e.g., a UE-specific search space) or a common search space (e.g., potentially usable by multiple wireless devices or a group of wireless user devices). The base station may configure a group of wireless devices with a common search space on a PCell or a primary secondary cell (PSCell) for active downlink BWPs.

[0068] The base station may configure a wireless device with one or more resource sets for one or more PUCCH transmissions, for example, for uplink BWPs within a set of configured uplink BWPs. The wireless device may receive downlink receptions (e.g., PDCCH or PDSCH) in the downlink BWPs, for example, according to a configured numerology (e.g., a configured subcarrier spacing and / or a configured cyclic prefix duration) for the downlink BWPs. The wireless device may transmit / transmit uplink transmissions (e.g., PUCCH or PUSCH) in the uplink BWPs, for example, according to a configured numerology (e.g., a configured subcarrier spacing and / or a configured cyclic prefix length for the uplink BWPs).

[0069] One or more BWP indicator fields may be provided / included in the downlink control information (DCI). The value of the BWP indicator field may indicate which BWPs of a set of configured BWPs are active downlink BWPs for one or more downlink receptions. The value of one or more BWP indicator fields may indicate active uplink BWPs for one or more uplink transmissions.

[0070] The base station may semi-statically configure the wireless device with a default downlink BWP within a set of configured downlink BWPs associated with the PCell. The default downlink BWP may be the initial active downlink BWP, for example, if the base station does not provide / configure a default downlink BWP for / to the wireless device. The wireless device may determine which BWP is the initial active downlink BWP based on, for example, a CORESET configuration obtained using the PBCH.

[0071] The base station may configure the wireless device with a BWP inactivity timer value for the PCell. The wireless device may start or restart the BWP inactivity timer at any appropriate time. The wireless device may start or restart the BWP inactivity timer, for example, if one or more conditions are met. The one or more conditions may include at least one of: the wireless device detecting a DCI indicating an active downlink BWP other than a default downlink BWP for paired spectrum operation; the wireless device detecting a DCI indicating an active downlink BWP other than a default downlink BWP for unpaired spectrum operation; and / or the wireless device detecting a DCI indicating an active uplink BWP other than a default uplink BWP for unpaired spectrum operation. The wireless device may start / run the BWP inactivity timer towards expiration (e.g., incrementing from zero to the BWP inactivity timer value or decrementing from the BWP inactivity timer value to zero), for example, if the wireless device does not detect a DCI during a time interval (e.g., 1 ms or 0.5 ms). The wireless device may switch from the active downlink BWP to the default downlink BWP, for example, if a BWP inactivity timer expires.

[0072] A base station may semi-statically configure a wireless device with one or more BWPs. The wireless device may switch the active BWP from a first BWP to a second BWP, for example, based on (e.g., after or in response to) receiving a DCI indicating the second BWP as the active BWP. The wireless device can switch the active BWP from a first BWP to a second BWP, for example, based on (e.g., after or in response to) expiration of a BWP inactivity timer (e.g., if the second BWP is the default BWP).

[0073] A downlink BWP switch may refer to switching an active downlink BWP from a first downlink BWP to a second downlink BWP (e.g., the second downlink BWP is activated and the first downlink BWP is deactivated). An uplink BWP switch may refer to switching an active uplink BWP from a first uplink BWP to a second uplink BWP (e.g., the second uplink BWP is activated and the first uplink BWP is deactivated). Downlink and uplink BWP switches may be performed independently (e.g., on paired spectrum / spectrum). Downlink and uplink BWP switches may be performed simultaneously (e.g., on unpaired spectrum / spectrum). Switching between configured BWPs may occur based on, for example, RRC signaling, DCI signaling, expiration of a BWP inactivity timer, and / or initiation of random access.

[0074] FIG. 9 shows an example of a configured BWP. Bandwidth adaptation using multiple BWPs (e.g., three configured BWPs for an NR carrier) may be available. A wireless device configured with multiple BWPs (e.g., three BWPs) may switch from one BWP to another at a switch point. The BWPs may include BWP 902 having a 40 MHz bandwidth and 15 kHz subcarrier spacing, BWP 904 having a 10 MHz bandwidth and 15 kHz subcarrier spacing, and BWP 906 having a 20 MHz bandwidth and 60 kHz subcarrier spacing. BWP 902 may be the initial active BWP, and BWP 904 may be the default BWP. A wireless device may switch between BWPs at a switch point. A wireless device may switch from BWP 902 to BWP 904 at switch point 908. Switching at switch point 908 may be performed for any suitable reason. The switch at switch point 908 may occur, for example, based on (e.g., after or in response to) expiration of a BWP inactivity timer (e.g., indicating a switch to a default BWP). The switch at switch point 908 may occur, for example, based on (e.g., after or in response to) receiving a DCI indicating BWP 904 as the active BWP. The wireless device may switch from the active BWP 904 to BWP 906 at switch point 910, for example, after or in response to receiving a DCI indicating BWP 906 as the new active BWP. The wireless device may switch from the active BWP 906 to BWP 904 at switch point 912, for example, based on (e.g., after or in response to) expiration of a BWP inactivity timer. The wireless device may switch from the active BWP 906 to BWP 904 at switch point 912, for example, after or in response to receiving a DCI indicating BWP 904 as the new active BWP. The wireless device may switch from active BWP 904 to BWP 902 at switch point 914, for example, after or in response to receiving a DCI indicating BWP 902 as the new active BWP.

[0075] A wireless device procedure for switching BWPs on a secondary cell may be the same / similar to that on a primary cell, for example, if the wireless device is configured for the secondary cell with a default downlink BWP in the set of configured downlink BWPs and timer values. The wireless device may use timer values ​​and a default downlink BWP for the secondary cell in the same / similar manner that the wireless device uses timer values ​​and / or a default BWP for the primary cell. The timer values ​​(e.g., BWP inactivity timer) may be configured per cell (e.g., for one or more BWPs), for example, via RRC signaling or any other signaling. One or more active BWPs may switch to another BWP based on, for example, expiration of a BWP inactivity timer.

[0076] Two or more carriers may be aggregated, and data may be transmitted / sent simultaneously to / from the same wireless device using carrier aggregation (CA) (e.g., to increase the data rate). The aggregated carriers of CA may be referred to as component carriers (CCs). For example, when CA is configured / used, there may be multiple quantities / numbers of serving cells for a wireless device (e.g., one serving cell for a CC). A CC may have multiple configurations in the frequency domain.

[0077] 10A shows an exemplary CA configuration based on CC. As shown in FIG. 10A, three types of CA configurations may include an intra-band (contiguous) configuration 1002, an intra-band (non-contiguous) configuration 1004, and / or an intra-band configuration 1006. In the intra-band (contiguous) configuration 1002, two CCs may be aggregated in the same frequency band (frequency band A) and may be located immediately adjacent to each other within the frequency band. In the intra-band (non-contiguous) configuration 1004, two CCs may be aggregated in the same frequency band (frequency band A) but may be separated from each other within the frequency band by a gap. In the intra-band configuration 1006, two CCs may be located in different frequency bands (e.g., frequency band A and frequency band B, respectively).

[0078] The network may set the maximum amount of CCs that can be aggregated (e.g., up to 32 CCs can be aggregated in NR, or any other amount can be aggregated in other systems). The aggregated CCs may have the same or different bandwidths, subcarrier spacing, and / or duplexing schemes (TDD, FDD, or any other duplexing scheme). A serving cell for a wireless device using CA may have a downlink CC. One or more uplink CCs may optionally be configured for the serving cell (e.g., for FDD). The ability to aggregate more downlink carriers than uplink carriers may be useful, for example, when a wireless device has more data traffic on the downlink than on the uplink.

[0079] One of the aggregation cells for a wireless device may be referred to as a primary cell (PCell), for example, when CA is configured. The PCell may be a serving cell to which the radio initially connects or accesses, for example, during or at RRC connection establishment, RRC connection re-establishment, and / or handover. The PCell may provide / configure NAS mobility information and security inputs for the wireless device. A wireless device may have different PCells. For the downlink, a carrier corresponding to a PCell may be referred to as a downlink primary CC (DL PCC). For the uplink, a carrier corresponding to a PCell may be referred to as an uplink primary CC (UL PCC). Other aggregation cells for a wireless device (e.g., associated with CCs other than the DL PCC and UL PCC) may be referred to as secondary cells (SCells). SCells may be configured, for example, after a PCell is configured for the wireless device. SCells may be configured via an RRC connection reconfiguration procedure. For the downlink, a carrier corresponding to a SCell may be referred to as a downlink secondary CC (DL SCC). For the uplink, the carrier corresponding to the SCell may be referred to as an uplink secondary CC (UL SCC).

[0080] A configured SCell for a wireless device may be activated or deactivated, for example, based on traffic and channel conditions. Deactivating an SCell may cause the wireless device to stop PDCCH and PDSCH reception on the SCell, and PUSCH, SRS, and CQI transmission on the SCell. A configured SCell may be activated or deactivated, for example, using a MAC CE (e.g., the MAC CE described with respect to FIG. 4B). The MAC CE may indicate to the wireless device which SCells (e.g., within a subset of configured SCells) are activated or deactivated using a bitmap (e.g., one bit per SCell). A configured SCell may be deactivated, for example, based on (e.g., after or in response to) expiration of an SCell deactivation timer (e.g., one SCell deactivation timer may be configured per SCell).

[0081] DCI may include control information such as a scheduling assignment and a scheduling grant for a cell. DCI may be transmitted / conveyed via a cell corresponding to the scheduling assignment and / or scheduling grant, which may be referred to as self-scheduling. DCI including control information for a cell may be transmitted / conveyed via another cell, which may be referred to as cross-carrier scheduling. Uplink control information (UCI) may include control information such as a HARQ acknowledgement and channel state feedback (e.g., CQI, PMI, and / or RI) for an aggregation cell. UCI may be transmitted / conveyed via an uplink control channel (e.g., PUCCH) of a PCell or a specific SCell (e.g., an SCell configured with a PUCCH). A large amount / number of aggregated downlink CCs may overload the PUCCH of the PCell. A cell may be divided into multiple PUCCH groups.

[0082] 10B shows an example group of cells. Aggregation cells may be configured into one or more PUCCH groups (e.g., as shown in FIG. 10B). One or more cell groups or one or more uplink control channel groups (e.g., PUCCH group 1010 and PUCCH group 1050) may each include one or more downlink CCs. PUCCH group 1010 may include one or more downlink CCs, for example, three downlink CCs, i.e., PCell 1011 (e.g., DL PCC), SCell 1012 (e.g., DL SCC), and SCell 1013 (e.g., DL SCC). PUCCH group 1050 may include one or more downlink CCs, for example, three downlink CCs, i.e., PUCCH SCell (or PSCell) 1051 (e.g., DL SCC), SCell 1052 (e.g., DL SCC), and SCell 1053 (e.g., DL SCC). One or more uplink CCs of the PUCCH group 1010 may be configured as a PCell 1021 (e.g., a UL PCC), an SCell 1022 (e.g., a UL SCC), and an SCell 1023 (e.g., a UL SCC). One or more uplink CCs of the PUCCH group 1050 may be configured as a PUCCH SCell (or PSCell) 1061 (e.g., a UL SCC), an SCell 1062 (e.g., a UL SCC), and an SCell 1063 (e.g., a UL SCC). UCIs associated with the downlink CCs of the PUCCH group 1010, denoted as UCI 1031, UCI 1032, and UCI 1033, may be transmitted / transmitted via the uplink of the PCell 1021 (e.g., via the PUCCH of the PCell 1021). The UCIs associated with the downlink CCs of the PUCCH group 1050, denoted as UCI 1071, UCI 1072, and UCI 1073, may be transmitted / transmitted via the uplink of the PUCCH SCell (or PSCell) 1061 (e.g., via the PUCCH of the PUCCH SCell 1061).A single uplink PCell may be configured to transmit / carry UCI associated with six downlink CCs, for example, if the aggregation cell shown in FIG. 10B is not divided into PUCCH group 1010 and PUCCH group 1050. PCell 1021 may become overloaded, for example, if UCIs 1031, 1032, 1033, 1071, 1072, and 1073 are transmitted / transmitted via PCell 1021. By separating the transmission of UCI between PCell 1021 and PUCCH SCell (or PSCell) 1061, overloading can be prevented and / or reduced.

[0083] A PCell may include a downlink carrier (e.g., PCell 1011) and an uplink carrier (e.g., PCell 1021). An SCell may include only a downlink carrier. A cell including a downlink carrier and, optionally, an uplink carrier may be assigned a physical cell ID and a cell index. The physical cell ID or cell index may indicate / identify the downlink carrier and / or the uplink carrier of a cell, for example, depending on the context in which the physical cell ID is used. The physical cell ID may be determined, for example, using synchronization signals (e.g., PSS and / or SSS) transmitted / transmitted via the downlink component carrier. The cell index may be determined, for example, using one or more RRC messages. The physical cell ID may be referred to as a carrier ID, and the cell index may be referred to as a carrier index. A first physical cell ID for a first downlink carrier may refer to the first physical cell ID for a cell including the first downlink carrier. Substantially the same / similar concept may be applied, for example, to carrier activation. Activation of a first carrier may refer to activation of a cell that includes the first carrier.

[0084] The multi-carrier nature of the PHY layer may be exposed / indicated to the MAC layer (e.g., in a CA configuration). A HARQ entity may operate on the serving cell. Transport blocks may be generated per allocation / grant per serving cell. Transport blocks and potential HARQ retransmissions of transport blocks may be mapped to the serving cell.

[0085] For the downlink, a base station may transmit / transmit (e.g., unicast, multicast, and / or broadcast) one or more reference signals (RS) (e.g., PSS, SSS, CSI-RS, DM-RS, and / or PT-RS) to one or more wireless devices. For the uplink, one or more wireless devices may transmit / transmit one or more RSs to a base station (e.g., DM-RS, PT-RS, and / or SRS). The PSS and SSS may be transmitted / transmitted by a base station and used by one or more wireless devices to synchronize the one or more wireless devices with the base station. A synchronization signal (SS) / physical broadcast channel (PBCH) block may include a PSS, SSS, and PBCH. A base station may periodically transmit / transmit bursts of SS / PBCH blocks, which may be referred to as SSBs.

[0086] FIG. 11A shows an example mapping of one or more SS / PBCH blocks. A burst of SS / PBCH blocks may include one or more SS / PBCH blocks (e.g., four SS / PBCH blocks as shown in FIG. 11A). Bursts may be transmitted / sent periodically (e.g., every two frames, every 20 milliseconds, or any other duration). Bursts may be limited to half frames (e.g., the first half frame having a 5 millisecond duration). Such parameters (e.g., amount / number of SS / PBCH blocks per burst, burst periodicity, position of the burst within a frame) may be configured based on, for example, at least one of the carrier frequency of the cell in which the SS / PBCH block is transmitted / transmitted, the numerology or subcarrier spacing of the cell, configuration by the network (e.g., using RRC signaling), and / or any other suitable factor. The wireless device may assume subcarrier spacing for the SS / PBCH block based on the monitored carrier frequency, unless, for example, the wireless network configures the wireless device to assume a different subcarrier spacing.

[0087] An SS / PBCH block may span one or more OFDM symbols in the time domain (e.g., four OFDM symbols shown in FIG. 11A , or any other quantity / number of symbols) and one or more subcarriers in the frequency domain (e.g., 240 contiguous subcarriers or any other quantity / number of subcarriers). The PSS, SSS, and PBCH may have a common center frequency. The PSS may be transmitted / transmitted first and may span, for example, one OFDM symbol and 127 subcarriers. The SSS may be transmitted / transmitted after the PSS (e.g., two symbols later) and may span one OFDM symbol and 127 subcarriers. The PBCH may be transmitted / sent after the PSS (e.g., over the next three OFDM symbols), may span 240 subcarriers (e.g., in the second and fourth OFDM symbols as shown in FIG. 11A), and / or may span less than 240 subcarriers (e.g., in the third OFDM symbol as shown in FIG. 11A).

[0088] The location of the SS / PBCH block in the time and frequency domains may not be known to the wireless device (e.g., when the wireless device is searching for a cell). The wireless device may monitor the carrier for a PSS, for example, to find and select a cell. The wireless device may monitor a frequency location within the carrier. If the wireless device does not find a PSS, for example, after a period of time (e.g., 20 milliseconds), it may search for a PSS at a different frequency location within the carrier. The wireless device may search for a PSS at a different frequency location within the carrier, for example, as indicated by a synchronization raster. If the PSS is found at a location in the time and frequency domains, the wireless device may determine the location of the SSS and PBCH, respectively, for example, based on the known structure of the SS / PBCH block. The SS / PBCH block may be a cell-defined SS block (CD-SSB). A primary cell may be associated with the CD-SSB. The CD-SSB may be located on the synchronization raster. Cell selection / search and / or reselection may be based on the CD-SSB.

[0089] The SS / PBCH block may be used by a wireless device to determine one or more parameters of the cell. The wireless device may determine a physical cell identifier (PCI) of the cell, for example, based on the PSS and SSS sequences, respectively. The wireless device may determine a location of a frame boundary of the cell, for example, based on the location of the SS / PBCH block. The SS / PBCH block may indicate that it is to be transmitted / sent according to a transmission pattern. The SS / PBCH block in the transmission pattern may be a known distance from the frame boundary (e.g., a predefined distance for a RAN configuration between one or more networks, one or more base stations, and one or more wireless devices).

[0090] The PBCH may use QPSK modulation and / or forward error correction (FEC). The FEC may use polar coding. One or more symbols spanned by the PBCH may contain / carry one or more DM-RSs for demodulation of the PBCH. The PBCH may include an indication of the cell's current system frame volume / number (SFN) and / or SS / PBCH block timing index. These parameters may facilitate time synchronization of the wireless device to the base station. The PBCH may include a Management Information Block (MIB) used to transmit / transmit one or more parameters to the wireless device. The MIB can be used by the wireless device to find the Minimum Remaining System Information (RMSI) associated with the cell. The RMSI may include System Information Block Type 1 (SIB1). SIB1 may include information for the wireless device to access the cell. The wireless device may use one or more parameters of the MIB to monitor the PDCCH, which may be used to schedule the PDSCH. The PDSCH may include SIB1. SIB1 may be decoded using parameters provided / included in the MIB. The PBCH may indicate that SIB1 is not present. For example, the wireless device may point to a frequency based on the PBCH indicating that SIB1 is not present. The wireless device may search for an SS / PBCH block on the frequency to which the wireless device is pointed.

[0091] A wireless device may assume that one or more SS / PBCH blocks transmitted with the same SS / PBCH block index are quasi-co-located (QCLed) (e.g., have substantially the same / similar Doppler spread, Doppler shift, average gain, average delay, and / or spatial Rx parameters). The wireless device may not assume QCL for SS / PBCH block transmissions with different SS / PBCH block indices. SS / PBCH blocks (e.g., blocks within a half frame) may be transmitted in spatial directions (e.g., using different beams across the coverage area of ​​a cell). A first SS / PBCH block may be transmitted in a first spatial direction using a first beam, a second SS / PBCH block may be transmitted in a second spatial direction using a second beam, a third SS / PBCH block may be transmitted in a third spatial direction using a third beam, and a fourth SS / PBCH block may be transmitted in a fourth spatial direction using a fourth beam.

[0092] A base station may transmit / transmit multiple SS / PBCH blocks, for example, within the frequency span of a carrier. A first PCI of a first SS / PBCH block of the multiple SS / PBCH blocks may be different from a second PCI of a second SS / PBCH block of the multiple SS / PBCH blocks. The PCIs of SS / PBCH blocks transmitted / transmitted at different frequency locations may be different or substantially identical.

[0093] A CSI-RS may be transmitted / conveyed by a base station and used by a wireless device to acquire / obtain / determine channel state information (CSI). A base station may configure a wireless device with one or more CSI-RS for channel estimation or any other suitable purpose. A base station may configure a wireless device with one or more of the same / similar CSI-RS. A wireless device may measure one or more CSI-RS. A wireless device may estimate downlink channel conditions and / or generate a CSI report, for example, based on measurements of one or more downlink CSI-RS. A wireless device may send / transmit a CSI report to a base station (e.g., based on periodic CSI reports, semi-persistent CSI reports, and / or aperiodic CSI reports). A base station may perform link adaptation using feedback (e.g., estimated downlink channel conditions) provided by the wireless device.

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

[0095] A base station may configure a wireless device to report CSI measurements. A base station may configure a wireless device to provide CSI reports periodically, aperiodically, or semi-persistently. For periodic CSI reporting, a wireless device may be configured with the timing and / or periodicity of CSI reports. For aperiodic CSI reporting, a base station may request a CSI report. A base station may instruct a wireless device to measure configured CSI-RS resources and provide a CSI report associated with the measurements. For semi-persistent CSI reporting, a base station may configure a wireless device to transmit / transmit periodically and to selectively activate or deactivate periodic reporting (e.g., via one or more activate / deactivate MAC CEs and / or one or more DCIs). A base station may configure a wireless device with a CSI-RS resource set and a CSI report, for example, using RRC signaling.

[0096] The CSI-RS configuration may include, for example, one or more parameters indicating up to 32 antenna ports (or any other quantity of antenna ports). A wireless device may be configured to use / employ the same OFDM symbol for downlink CSI-RS and CORESET, such as when the downlink CSI-RS and CORESET are spatially QCL'd and resource elements associated with the downlink CSI-RS are outside of a physical resource block (PRB) configured for CORESET. A wireless device may be configured to use / employ the same OFDM symbol for downlink CSI-RS and SS / PBCH blocks, such as when the downlink CSI-RS and SS / PBCH blocks are spatially QCL'd and resource elements associated with the downlink CSI-RS are outside of a PRB configured for the SS / PBCH block.

[0097] A downlink DM-RS may be transmitted / transmitted by a base station and received / used by a wireless device for channel estimation. The downlink DM-RS may be used for coherent demodulation of one or more downlink physical channels (e.g., PDSCH). A network (e.g., an NR network) may support one or more variable and / or configurable DM-RS patterns for data demodulation. At least one downlink DM-RS configuration may support a frontloaded DM-RS pattern. The frontloaded DM-RS may be mapped onto one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). A base station may semi-statically configure a wireless device with the amount / number (e.g., maximum amount / number) of frontloaded DM-RS symbols for the PDSCH. A DM-RS configuration may support one or more DM-RS ports. A DM-RS configuration may support up to eight orthogonal downlink DM-RS ports per wireless device (e.g., for single-user MIMO). The DM-RS configuration may support up to four orthogonal downlink DM-RS ports per wireless device (e.g., for multi-user MIMO). The wireless network may support a common DM-RS structure for the downlink and uplink (e.g., at least for CP-OFDM). The DM-RS position, DM-RS pattern, and / or scrambling sequence may be identical or different. A base station may transmit / convey a downlink DM-RS and a corresponding PDSCH, for example, using the same precoding matrix. A wireless device may use one or more downlink DM-RSs for coherent demodulation / channel estimation of the PDSCH.

[0098] A transmitter (e.g., a base station transmitter) may use a precoder matrix for a portion of a transmission bandwidth. 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, for example, based on the first bandwidth being different from the second bandwidth. A wireless device may assume that the same precoding matrix is ​​used across a set of PRBs. The set of PRBs may be determined / indicated / identified / denoted as a precoding resource block group (PRG).

[0099] The PDSCH may include one or more layers. A wireless device may assume that at least one symbol with a DM-RS is present on one or more layers of the PDSCH. Higher layers may configure one or more DM-RSs for the PDSCH (e.g., up to three DM-RSs for the PDSCH). A downlink PT-RS may be transmitted / transmitted by a base station and may be used by a wireless device, for example, for phase noise compensation. Whether a downlink PT-RS is present may depend on an RRC configuration. The presence and / or pattern of the downlink PT-RS is configured based on wireless device-specific criteria, for example, using a combination of RRC signaling and / or an association with one or more parameters used / employed for other purposes (e.g., modulation and coding scheme (MCS)), which may be indicated by DCI. The dynamic presence of the downlink PT-RS, if configured, may be associated with one or more DCI parameters, including at least the MCS. A network (e.g., an NR network) may support multiple PT-RS densities defined in the time and / or frequency domains. The frequency domain density (configuration / if present) may be associated with at least one configuration of the scheduled bandwidth. The wireless device may assume the same precoding for DM-RS ports and PT-RS ports. The amount / number of PT-RS ports may be less than the amount / number of DM-RS ports in the scheduled resources. The downlink PT-RS may be configured / assigned / restricted at a time / frequency duration scheduled for the wireless device. The downlink PT-RS may be transmitted / transmitted via symbols, for example, to facilitate phase tracking at the receiver.

[0100] A wireless device may transmit / transmit an uplink DM-RS to a base station, for example, for channel estimation. A base station may use the uplink DM-RS for coherent demodulation of one or more uplink physical channels. A wireless device may transmit / transmit an uplink DM-RS on a PUSCH and / or a PUCCH. The uplink DM-RS may span a frequency range similar to the frequency range associated with the corresponding physical channel. A base station may configure a wireless device with one or more uplink DM-RS configurations. At least one DM-RS configuration may support a frontloaded DM-RS pattern. The frontloaded DM-RS may be mapped onto one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DM-RS may be configured to transmit / transmit on one or more symbols of a PUSCH and / or a PUCCH. A base station may semi-statically configure a wireless device with the amount / number (e.g., maximum amount / number) of frontloaded DM-RS symbols for the PUSCH and / or PUCCH that the wireless device may use to schedule single-symbol DM-RS and / or double-symbol DM-RS. A network (e.g., an NR network) may support a common DM-RS structure for the downlink and uplink (e.g., for cyclic prefix orthogonal frequency division multiplexing (CP-OFDM)). The DM-RS locations, DM-RS patterns, and / or DM-RS scrambling sequences may be substantially identical or different.

[0101] The PUSCH may include one or more layers. A wireless device may transmit at least one symbol using a DM-RS present on one or more layers of the PUSCH. Higher layers may configure one or more DM-RSs (e.g., up to three DMRSs) for the PUSCH. An uplink PT-RS (which may be used by a base station for phase tracking and / or phase noise compensation) may be present or absent, for example, depending on the RRC configuration of the wireless device. The presence and / or pattern of the uplink PT-RS may be configured on a wireless device-specific basis (e.g., a UE-specific basis), for example, by a combination of one or more parameters configured / adopted for RRC signaling and / or other purposes (e.g., MCS), which may be indicated by DCI. The dynamic presence of the uplink PT-RS, if configured, may be associated with one or more DCI parameters, including at least MCS. A wireless network may support multiple uplink PT-RS densities defined in the time / frequency domain. The frequency-domain density (if configured / present) may be associated with at least one configuration of the scheduled bandwidth. The wireless device may assume the same precoding for the DM-RS and PT-RS ports. The amount / number of PT-RS ports may be less than the amount / number of DM-RS ports in the scheduled resources. The uplink PT-RS may be configured / assigned / restricted at the time / frequency duration scheduled for the wireless device.

[0102] One or more SRSs may be transmitted / sent by a wireless device to a base station for channel condition estimation, e.g., to support uplink channel-dependent scheduling and / or link adaptation. The SRS transmitted / sent by the wireless device may enable / enable the base station to estimate uplink channel conditions at one or more frequencies. A scheduler at the base station may use / employ the estimated uplink channel conditions to allocate one or more resource blocks for uplink PUSCH transmission for the wireless device. A base station may semi-statically configure a wireless device with one or more SRS resource sets. For an SRS resource set, the base station may configure the wireless device with one or more SRS resources. SRS resource set applicability may be configured, for example, by higher layer (e.g., RRC) parameters. SRS resources within an SRS resource set of one or more SRS resource sets (e.g., having the same / similar time-domain behavior, periodic, aperiodic, and / or the like) may be transmitted / sent instantaneously (e.g., simultaneously), for example, when higher layer parameters indicate beam management. A wireless device may transmit / transmit one or more SRS resources in an SRS resource set. A network (e.g., an NR network) may support aperiodic, periodic, and / or semi-persistent SRS transmission. A wireless device may transmit / transmit SRS resources, for example, based on one or more trigger types. The one or more trigger types may include higher layer signaling (e.g., RRC) and / or one or more DCI formats. At least one DCI format may be used / adopted by the wireless device to select at least one of the one or more configured SRS resource sets. SRS trigger type 0 may refer to an SRS triggered based on higher layer signaling. SRS trigger type 1 may refer to an SRS triggered based on one or more DCI formats. A wireless device may be configured to transmit / transmit an SRS after the transmission of a PUSCH and a corresponding uplink DM-RS, for example, when the PUSCH and SRS are transmitted / transmitted in the same slot.The base station may quasi-statistically configure the wireless device with one or more SRS configuration parameters indicating at least one of an SRS resource configuration identifier, a quantity / number of SRS ports, a time domain behavior of the SRS resource configuration (e.g., an indication of periodic, semi-persistent, or aperiodic SRS), slot, minislot, and / or subframe level periodicity, an offset for periodic and / or aperiodic SRS resources, a quantity / number of OFDM symbols in the SRS resources, a starting OFDM symbol for the SRS resources, an SRS bandwidth, a frequency hopping bandwidth, a cyclic shift, and / or an SRS sequence ID.

[0103] Antenna ports may be determined / defined such that a channel through which a symbol on an antenna port is conveyed can be inferred from a channel through which another symbol on the same antenna port is conveyed. A receiver may infer / determine a channel (e.g., fade gain, multipath delay, and / or the like) for conveying a second symbol on an antenna port from a channel for conveying a first symbol on the antenna port, such as when the first symbol and the second symbol are transmitted / conveyed on the same antenna port. A first antenna port and a second antenna port may be referred to as quasi-co-located (QCL-ized), for example, if one or more large-scale characteristics of the channel through which the first symbol on the first antenna port is conveyed can be inferred from the channel through which the second symbol on the second antenna port is conveyed. The one or more large-scale characteristics may include at least one of delay spread, Doppler spread, Doppler shift, average gain, average delay, and / or spatial receive (Rx) parameters.

[0104] A channel using beamforming may require beam management. Beam management may include beam measurement, beam selection, and / or beam direction. A beam may be associated with one or more reference signals. A beam may be identified by one or more beamforming reference signals. A wireless device may perform downlink beam measurements and generate beam measurement reports, for example, based on one or more downlink reference signals (e.g., CSI-RS). A wireless device may perform a downlink beam measurement procedure, for example, after an RRC connection is set up with a base station.

[0105] Figure 11B shows an example mapping of one or more CSI-RSs. The CSI-RSs may be mapped in the time domain and the frequency domain. Each rectangular block shown in Figure 11B may correspond to a resource block (RB) in the bandwidth of a cell. A base station may transmit / convey one or more RRC messages including CSI-RS resource configuration parameters indicating one or more CSI-RSs. One or more of the parameters may be configured by higher layer signaling (e.g., RRC and / or MAC signaling) for CSI-RS resource configuration. One or more of the parameters may include at least one of a CSI-RS resource configuration identity, a quantity / number of CSI-RS ports, a CSI-RS configuration (e.g., symbol and resource element (RE) location within a subframe), a CSI-RS subframe configuration (e.g., subframe location, offset, and radio frame periodicity), a CSI-RS power parameter, a CSI-RS sequence parameter, a code division multiplexing (CDM) type parameter, a frequency density, a transmit comb, a quasi-co-located (QCL) parameter (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and / or other radio resource parameters.

[0106] One or more beams may be configured for a wireless device in a wireless device-specific configuration. Three beams are shown in FIG. 11B (Beam #1, Beam #2, and Beam #3), but more or fewer beams may be configured. Beam #1 may be assigned with CSI-RS 1101, which may be transmitted / carried on one or more subcarriers of the RB of the first symbol. Beam #2 may be assigned with CSI-RS 1102, which may be transmitted / carried on one or more subcarriers of the RB of the second symbol. Beam #3 may be assigned with CSI-RS 1103, which may be transmitted / carried on one or more subcarriers in the RB of the third symbol. A base station may use other subcarriers in the same RB (e.g., those not used to transmit / carry CSI-RS 1101) to transmit another CSI-RS associated with a beam for another wireless device, for example, by using frequency division multiplexing (FDM). A beam used for a wireless device may be configured to use symbols different from those used by beams of other wireless devices, for example, by using time domain multiplexing (TDM). Wireless devices may be delivered with beams of orthogonal symbols (e.g., no overlapping symbols), for example, by using TDM.

[0107] CSI-RS (e.g., CSI-RS 1101, 1102, 1103) may be transmitted / conveyed by a base station and may be used by a wireless device for one or more measurements. The wireless device may measure the RSRP of configured CSI-RS resources. The base station may configure the wireless device with a reporting configuration, and the wireless device may report RSRP measurements to the network (e.g., via one or more base stations) based on the reporting configuration. The base station may determine one or more transmission configuration indication (TCI) states, including some quantity / number of reference signals, based on the reported measurement results. The base station may indicate one or more TCI states to the wireless device (e.g., via RRC signaling, MAC CE, and / or DCI). The wireless device may receive downlink transmissions on an Rx beam determined based on the one or more TCI states. The wireless device may or may not have beam correspondence capability. The wireless device may determine the spatial domain filter of a transmit (Tx) beam based on the spatial domain filter of a corresponding Rx beam, for example, if the wireless device has beam correspondence capability. The wireless device may perform an uplink beam selection procedure to determine the spatial domain filter of a Tx beam, for example, if the wireless device does not have beam correspondence capability. The wireless device may perform the uplink beam selection procedure based on one or more sounding reference signal (SRS) resources configured in the wireless device by a base station, for example. The base station may select and display an uplink beam for the wireless device based on measurements of one or more SRS resources transmitted / communicated by the wireless device, for example.

[0108] A wireless device may determine / evaluate (e.g., measure) the channel quality of one or more beam pair links, for example, in a beam management procedure. The beam pair link may include a Tx beam of the base station and an Rx beam of the wireless device. The Tx beam of the base station may transmit / transmit downlink signals, and the Rx beam of the wireless device may receive downlink signals. The wireless device may transmit / convey a beam measurement report, for example, based on the evaluation / determination. The beam measurement report may indicate one or more beam pair quality parameters, including at least one of one or more beam identifications (e.g., beam index, reference signal index, or the like), RSRP, precoding matrix indicator (PMI), channel quality indicator (CQI), and / or rank indicator (RI).

[0109] FIG. 12A shows an example of a downlink beam management procedure. One or more downlink beam management procedures (e.g., downlink beam management procedures P1, P2, and P3) may be performed. Procedure P1 may enable measurements (e.g., wireless device measurements) on the Tx beam of a TRP (or multiple TRPs) (e.g., to support selection of one or more base station Tx beams and / or wireless device Rx beams). The base station Tx beams and wireless device Rx beams are shown as ellipses in the top and bottom rows of P1, respectively. Beamforming (e.g., at a TRP) may include a Tx beam sweep for a set of beams (e.g., a beam sweep shown in the top rows of P1 and P2 as an ellipse rotated in a counterclockwise direction as indicated by the dashed arrow). Beamforming (e.g., at a wireless device) may include an Rx beam sweep for a set of beams (e.g., a beam sweep shown in the bottom rows of P1 and P3 as an ellipse rotated in a clockwise direction as indicated by the dashed arrow). Procedure P2 may be used to enable measurements (e.g., wireless device measurements) on the Tx beam of the TRP (shown in the top row of P2 as an ellipse rotated in a counterclockwise direction indicated by a dashed arrow). The wireless device and / or the base station may perform procedure P1, for example, using a smaller set of beams than the set of beams used in procedure P2 or using narrower beams than the beams used in procedure P1. Procedure P2 may be referred to as beam refinement. The wireless device may perform procedure P3 for Rx beam determination, for example, by using the same Tx beam of the base station and sweeping the Rx beam of the wireless device.

[0110] FIG. 12B shows an example of an uplink beam management procedure. One or more uplink beam management procedures (e.g., uplink beam management procedures U1, U2, and U3) may be implemented. Procedure U1 may be used to enable a base station to perform measurements on a wireless device's Tx beam (e.g., to support selection of one or more Tx beams of the wireless device and / or an Rx beam of the base station). The wireless device's Tx beam and the base station's Rx beam are shown as ellipses in the top row of U1 and the bottom row of U1, respectively. Beamforming (e.g., at the wireless device) may include one or more beam sweeps, e.g., a Tx beam sweep from a set of beams (shown as ellipses rotated in a clockwise direction indicated by dashed arrows in the bottom row of U1 and U3). Beamforming (e.g., at the base station) may include one or more beam sweeps, e.g., an Rx beam sweep from a set of beams (shown as ellipses rotated in a counterclockwise direction indicated by dashed arrows in the top row of U1 and U2). Procedure U2 may be used, for example, to allow a base station to adjust its Rx beam when a wireless device (e.g., UE, etc.) uses a fixed Tx beam. The wireless device and / or the base station may perform procedure U2, for example, using a smaller set of beams than the set of beams used in procedure P1 or using narrower beams than the beams used in procedure P1. Procedure U2 may be referred to as beam refinement. The wireless device may perform procedure U3 to adjust its Tx beam, for example, when the base station uses a fixed Rx beam.

[0111] A wireless device may initiate / start / perform a beam failure recovery (BFR) procedure, for example, based on detecting a beam failure. A wireless device may send / transmit a BFR request (e.g., a preamble, UCI, SR, MAC CE, and / or the like) based on initiating a BFR procedure. A wireless device may detect a beam failure, for example, based on determining that the quality of a beam pair link of an associated control channel is insufficient (e.g., having an error rate higher than an error rate threshold, a received signal power lower than a received signal power threshold, a timer expiring, and / or the like).

[0112] A wireless device may measure the quality of a beam pair link using one or more reference signals (RSs) including, for example, one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more DM-RSs. The 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, an RSRQ value, and / or a CSI value measured on the RS resources. A base station may indicate that an RS resource is QCLed with one or more DM-RSs of a channel (e.g., a control channel, a shared data channel, and / or the like). An RS resource and one or more DM-RSs of a channel may be QCLed, for example, if the channel characteristics (e.g., Doppler shift, Doppler spread, mean delay, delay spread, spatial Rx parameters, fading, and / or the like) transmitted to the wireless device via the RS resource are similar or identical to the channel characteristics transmitted to the wireless device via the channel.

[0113] A network (e.g., an NR network including a gNB and / or an ng-eNB) and / or a wireless device may initiate / start / perform a random access procedure. A wireless device in an RRC idle (e.g., RRC_IDLE) state and / or an RRC inactive (e.g., RRC_INACTIVE) state may initiate / perform a random access procedure to request connection setup to the network. A wireless device may initiate / start / perform a random access procedure from an RRC connected (e.g., RRC_CONNECTED) state. A wireless device may initiate / start / perform a random access procedure to request uplink resources (e.g., for uplink transmission of SR when there are no available PUCCH resources) and / or acquire / obtain / determine uplink timing (e.g., when the uplink synchronization state is asynchronous). A wireless device may initiate / start / perform a random access procedure to request one or more system information blocks (SIBs) (e.g., other system information blocks such as SIB2, SIB3, and / or the like). The wireless device may initiate / start / perform a random access procedure for a beam failure recovery request. The network may initiate / start / perform a random access procedure, for example, to establish time alignment for handover and / or SCell addition.

[0114] FIG. 13A shows an example of a four-step random access procedure. The four-step random access procedure may include a four-step contention-based random access procedure. A base station may, for example, send / transmit a configuration message 1310 to a wireless device before initiating the random access procedure. The four-step random access procedure may include the transmission of four messages, including a first message (e.g., Msg1 1311), a second message (e.g., Msg2 1312), a third message (e.g., Msg3 1313), and a fourth message (e.g., Msg4 1314). The first message (e.g., Msg1 1311) may include a preamble (or random access preamble). The first message (e.g., Msg1 1311) may be referred to as a preamble. The second message (e.g., Msg2 1312) may be included as a random access response (RAR). The second message (eg, Msg2 1312) may be referred to as a RAR.

[0115] The configuration message 1310 may be transmitted / conveyed using, for example, one or more RRC messages. The one or more RRC messages may indicate one or more random access channel (RACH) parameters to the wireless device. The one or more RACH parameters may include at least one of general parameters (e.g., RACH-configGeneral), cell-specific parameters (e.g., RACH-ConfigCommon), and / or dedicated parameters (e.g., RACH-configDedicated) of one or more random access procedures. A base station may transmit / transmit (e.g., broadcast or multicast) one or more RRC messages to one or more wireless devices. The one or more RRC messages may be wireless device-specific. The wireless device-specific one or more RRC messages may be, for example, dedicated RRC messages transmitted / transmitted to wireless devices in an RRC connected (e.g., RRC_CONNECTED) state and / or an RRC inactive (e.g., RRC_INACTIVE) state. The wireless device may determine, based on one or more RACH parameters, time-frequency resources and / or uplink transmit power for transmitting the first message (e.g., Msg1 1311) and / or the third message (e.g., Msg3 1313). The wireless device may determine, based on one or more RACH parameters, receive timing and downlink channels for receiving the second message (e.g., Msg2 1312) and the fourth message (e.g., Msg4 1314).

[0116] One or more RACH parameters provided / configured / included in the configuration message 1310 may indicate one or more physical RACH (PRACH) opportunities available for transmitting the first message (e.g., Msg1 1311). The one or more PRACH opportunities may be predefined (e.g., by a network including one or more base stations). The one or more RACH parameters may indicate one or more available sets of one or more PRACH opportunities (e.g., prach-ConfigIndex). The one or more RACH parameters may indicate an association between (a) one or more PRACH opportunities 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-RS. The one or more RACH parameters may indicate the amount / number of SS / PBCH blocks mapped to the PRACH opportunities and / or the amount / number of preambles mapped to the SS / PBCH blocks.

[0117] One or more RACH parameters provided / configured / included in the configuration message 1310 may be used to determine the uplink transmit power of the first message (e.g., Msg1 1311) and / or the third message (e.g., Msg3 1313). The one or more RACH parameters may indicate a reference power for the 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. The one or more RACH parameters may indicate a power ramping step, a power offset between SSB and CSI-RS, a power offset between the transmission of the first message (e.g., Msg1 1311) and the third message (e.g., Msg3 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 wireless device may determine at least one reference signal (e.g., SSB and / or CSI-RS) and / or uplink carrier (e.g., normal uplink (NUL) carrier and / or complementary uplink (SUL) carrier), for example.

[0118] The first message (e.g., Msg1 1311) may include one or more preamble transmissions (e.g., a preamble transmission and one or more preamble retransmissions). The RRC message may be used to configure one or more preamble groups (e.g., Group A and / or Group B). A preamble group may include one or more preambles. The wireless device may determine the preamble group based on, for example, a path loss measurement and / or the size of the third message (e.g., Msg3 1313). The wireless device may measure the RSRP of one or more reference signals (e.g., SSB and / or CSI-RS) and determine at least one reference signal having an RSRP above an RSRP threshold (e.g., rsrp-ThresholdSSB and / or rsrp-ThresholdCSI-RS). The wireless device may select one or more reference signals and / or at least one preamble associated with a selected preamble group, for example, if an association between one or more preambles and at least one reference signal is configured by an RRC message.

[0119] The wireless device may determine the preamble based on, for example, one or more RACH parameters provided / configured / included in the configuration message 1310. The wireless device may determine the preamble based on, for example, a path loss measurement, an RSRP measurement, and / or the size of the third message (e.g., Msg3 1313). The one or more RACH parameters may indicate a preamble format, a maximum amount / number of preamble transmissions, and / or one or more thresholds for determining one or more preamble groups (e.g., Group A and Group B). The base station may configure the wireless device with an association between one or more preambles and one or more reference signals (e.g., SSB and / or CSI-RS) using the one or more RACH parameters. The wireless device may determine the preamble to be included in the first message (e.g., Msg1 1311) based on, for example, the association, if configured. The first message (e.g., Msg1 1311) may be transmitted / transmitted to the base station via one or more PRACH opportunities. A wireless device may use one or more reference signals (e.g., SSB and / or CSI-RS) for preamble selection and PRACH opportunity determination. One or more RACH parameters (e.g., ra-ssb-OccasionMskIndex and / or ra-OccasionList) may indicate an association between a PRACH opportunity and one or more reference signals.

[0120] The wireless device may, for example, perform a preamble retransmission if no response is received (e.g., for a period of time, such as a monitoring window for monitoring an RAR) based on (e.g., after or in response to) the preamble transmission. The wireless device may increase uplink transmit power for the preamble retransmission. The wireless device may select an initial preamble transmit power based on, for example, a path loss measurement and / or a target received preamble power configured by the network. The wireless device may decide to retransmit / retransmit the preamble and may ramp up the uplink transmit power. The wireless device 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 the amount of incremental increase in uplink transmit power for the retransmission. The wireless device may increase the uplink transmit power, for example, if the wireless device determines the same reference signal (e.g., SSB and / or CSI-RS) as the previous preamble transmission. The wireless device may count the amount / number of preamble transmissions and / or retransmissions, for example, using a counter parameter (e.g., PREAMBLE_TRANSMISSION_COUNTER). The wireless device may determine that the random access procedure has not completed successfully, for example, if the amount / number of preamble transmissions exceeds a threshold configured by one or more RACH parameters (e.g., preambleTransMax) without receiving a successful response (e.g., RAR).

[0121] The second message (e.g., Msg2 1312) (e.g., received by the wireless device) may include an RAR. The second message (e.g., Msg2 1312) may include multiple RARs corresponding to multiple wireless devices. The second message (e.g., Msg2 1312) may be received, for example, based on (e.g., subsequently in response to) the transmission / transmission of the first message (e.g., Msg1 1311). The second message (e.g., Msg2 1312) may be scheduled on the DL-SCH and may be indicated by the PDCCH, for example, using a random access radio network temporary identifier (RA RNTI). The second message (e.g., Msg2 1312) may indicate that the first message (e.g., Msg1 1311) has been received by the base station. The second message (e.g., Msg2 1312) may include a time alignment command that may be used by the wireless device to adjust the transmission timing of the wireless device, a scheduling grant for transmission of the third message (e.g., Msg3 1313), and / or a temporary cell RNTI (TC-RNTI). The wireless device may, for example, determine / start a time window (e.g., ra-ResponseWindow) in which to monitor the PDCCH for the second message (e.g., Msg2 1312) after transmitting / sending the first message (e.g., Msg1 1311) (e.g., preamble). The wireless device may determine the start time of the time window based, for example, on the PRACH opportunity that the wireless device uses to transmit / send the first message (e.g., Msg1 1311) (e.g., preamble). The wireless device may begin a time window one or more symbols after the last symbol of a first message (e.g., Msg1 1311) including a preamble (e.g., a symbol at which the first message (e.g., Msg1 1311) including a preamble transmission is complete or is in the first PDCCH opportunity from the end of the preamble transmission). The one or more symbols may be determined based on a numerology.The PDCCH may be mapped to a common search space (e.g., Type1-PDCCH common search space) configured by an RRC message. A wireless device may identify / determine an RAR, for example, based on the RNTI. A radio network temporary identifier (RNTI) may be used in response to one or more events that initiate / start a random access procedure. A wireless device may use the RA-RNTI, for example, for one or more communications related to random access or any other purpose. The RA-RNTI may be associated with a PRACH opportunity on which the wireless device transmits / transmits a preamble. A wireless device may determine the RA-RNTI based on, for example, at least one of an OFDM symbol index, a slot index, a frequency domain index, and / or a UL carrier indicator of the PRACH opportunity. An example of the RA-RNTI may be determined as follows:

[0122] RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id

[0123] where s_id may be the index of the first OFDM symbol of the PRACH opportunity (e.g., 0≦s_id<14), t_id may be the index of the first slot of the PRACH opportunity in the system frame (e.g., 0≦t_id<80), f_id may be the index of the PRACH opportunity in the frequency domain (e.g., 0≦f_id<8), and ul_carrier_id may be the UL carrier used for preamble transmission (e.g., 0 for NUL carrier and 1 for SUL carrier).

[0124] The wireless device may send / transmit a third message (e.g., Msg3 1313), for example, based on (e.g., subsequently or in response to) successful reception of the second message (e.g., Msg2 1312) (e.g., using resources identified in Msg2 1312). The third message (e.g., Msg3 1313) may be used, for example, for contention resolution in a contention-based random access procedure. Multiple wireless devices may send / transmit the same preamble to a base station, and the base station may send / transmit an RAR corresponding to the wireless device. Collisions may occur, for example, when multiple wireless devices interpret the RAR as corresponding to itself. Contention resolution (e.g., using the third message (e.g., Msg3 1313) and the fourth message (e.g., Msg4 1314)) may be used to increase the likelihood that a wireless device does not mistakenly use the identity of another wireless device. The wireless device may include a device identifier in the third message (e.g., Msg3 1313) (e.g., the C-RNTI, if assigned, the TC RNTI included in the second message (e.g., Msg2 1312), and / or any other suitable identifier), for example, to perform contention resolution.

[0125] A fourth message (e.g., Msg4 1314) may be received, for example, based on (e.g., after or in response to) the transmission / transmission of the third message (e.g., Msg3 1313). The base station may address the radio on the PDCCH (e.g., the base station may transmit a PDCCH to the wireless device) using the C-RNTI, for example, if the C-RNTI was included in the third message (e.g., Msg3 1313). The random access procedure may be determined to be successful, for example, if the wireless device's unique C-RNTI is detected on the PDCCH (e.g., the PDCCH is scrambled by the C-RNTI). The fourth message (e.g., Msg4 1314) may be received using the DL-SCH associated with the TC RNTI, for example, if the TC RNTI is included in the third message (e.g., Msg3 1313) (e.g., when the wireless device is in an RRC idle (e.g., RRC_IDLE) state or is otherwise connected to a base station). For example, if the MAC PDU is successfully decoded and the MAC PDU includes a wireless device contention resolution identity MAC CE that matches or otherwise corresponds to the CCCH SDU carried / transmitted in the third message (e.g., Msg3 1313), the wireless device may determine that contention resolution was successful and / or the wireless device may determine that the random access procedure was successfully completed.

[0126] The wireless device may be configured with an SUL carrier and / or a NUL carrier. Initial access (e.g., random access) may be supported via an uplink carrier. A base station may configure a wireless device with multiple RACH configurations (e.g., two separate RACH configurations, including one for the SUL carrier and the other for the NUL carrier). For random access in a cell configured with an SUL carrier, the network may indicate which carrier (NUL or SUL) to use. The wireless device may decide to use the SUL carrier, for example, if the measured quality of one or more reference signals (e.g., one or more reference signals associated with the NUL carrier) is lower than a broadcast threshold. Uplink transmission of the random access procedure (e.g., the first message (e.g., Msg1 1311) and / or the third message (e.g., Msg3 1313)) may remain on or occur via the selected carrier. The wireless device may switch uplink carriers during the random access procedure (e.g., between Msg1 1311 and Msg3 1313). The wireless device may determine and / or switch uplink carriers for the first message (e.g., Msg1 1311) and / or the third message (e.g., Msg3 1313) based on, for example, a channel clearance assessment (e.g., listen-before-talk).

[0127] FIG. 13B illustrates a two-step random access procedure. The two-step random access procedure may include a two-step contention-free random access procedure. Similar to the four-step contention-based random access procedure, a base station may send / transmit a configuration message 1320 to a wireless device before the procedure begins. The configuration message 1320 may be similar in some respects to the configuration message 1310. The procedure illustrated in FIG. 13B may include the transmission of two messages: a first message (e.g., Msg1 1321) and a second message (e.g., Msg2 1322). The first message (e.g., Msg1 1321) and the second message (e.g., Msg2 1322) may be similar in some respects to the first message (e.g., Msg1 1311) and the second message (e.g., Msg2 1312), respectively. A two-step contention-free random access procedure may not include a message similar to the third message (eg, Msg3 1313) and / or the fourth message (eg, Msg4 1314).

[0128] A two-step (e.g., contention-free) random access procedure may be configured / initiated for beam failure recovery, other SI request, SCell addition, and / or handover. The base station may indicate or assign to the wireless device a preamble to be used in the first message (e.g., Msg1 1321). The wireless device may receive an indication of the preamble (e.g., ra-PreambleIndex) from the base station via the PDCCH and / or RRC.

[0129] The wireless device may start a time window (e.g., ra-ResponseWindow) for monitoring the PDCCH for the RAR, for example, based on (e.g., after or in response to) transmitting / sending a preamble. The base station may configure the wireless device with one or more beam failure recovery parameters, such as a separate time window and / or a separate PDCCH, in a search space indicated by an RRC message (e.g., recoverySearchSpaceId). The base station may configure one or more beam failure recovery parameters, for example, in association with a beam failure recovery request. The separate time window for monitoring the PDCCH and / or RAR may be configured to start after transmitting / sending the beam failure recovery request (e.g., the window may start any amount of symbols and / or slots after transmitting / sending the beam failure recovery request). The wireless device may monitor PDCCH transmissions addressed to a Cell RNTI (C-RNTI) on the search space. During a two-step (e.g., contention-free) random access procedure, the wireless device may determine that the random access procedure is successful, for example, based on (e.g., subsequently to or in response to) transmitting / sending a first message (e.g., Msg1 1321) and receiving a corresponding second message (e.g., Msg2 1322). The wireless device may determine that the random access procedure is successfully completed, for example, if a PDCCH transmission is addressed to the corresponding C-RNTI. The wireless device may determine that the random access procedure is successfully completed, for example, if the wireless device receives an RAR including a preamble identifier corresponding to a preamble transmitted / sent by the wireless device and / or the RAR includes a MAC sub-PDU with the preamble identifier. The wireless device may determine the response as an indication of an acknowledgement to the SI request.

[0130] 13C shows an example of a two-step random access procedure. Similar to the random access procedures shown in FIGS. 13A and 13B, the base station may send / transmit a configuration message 1330 to the wireless device prior to initiating the procedure. The configuration message 1330 may be similar in some respects to the configuration message 1310 and / or the configuration message 1320. The procedure shown in FIG. 13C may include the transmission of multiple messages (e.g., two messages including a first message (e.g., MsgA 1331) and a second message (e.g., MsgB 1332)).

[0131] MsgA 1320 may be transmitted / sent by the wireless device in an uplink transmission. MsgA 1320 may include one or more transmissions of a preamble 1341 and / or one or more transmissions of a transport block 1342. The transport block 1342 may include content similar and / or equivalent to the content of a third message (e.g., Msg3 1313) (e.g., shown in FIG. 13A). The transport block 1342 may include UCI (e.g., SR, HARQ ACK / NACK, and / or the like). The wireless device may receive a second message (e.g., MsgB 1332), for example, based on (e.g., subsequently in response to) transmitting / sending a first message (e.g., MsgA 1331). The second message (e.g., MsgB 1332) may include content similar and / or equivalent to the content of the second message (e.g., Msg2 1312) (e.g., the RAR shown in FIG. 13A), the content of the second message (e.g., Msg2 1322) (e.g., the RAR shown in FIG. 13B), and / or the content of the fourth message (e.g., Msg4 1314) (e.g., shown in FIG. 13A).

[0132] A wireless device may start / initiate a two-step random access procedure (e.g., the two-step random access procedure shown in FIG. 13C) for licensed spectrum and / or unlicensed spectrum. The wireless device may determine whether to start / initiate the two-step random access procedure based on one or more factors. The one or more factors may include at least one of the radio access technology in use (e.g., LTE, NR, and / or the like), whether the wireless device has a valid TA, the cell size, the RRC state of the wireless device, the type of spectrum (e.g., licensed vs. unlicensed), and / or any other suitable factor.

[0133] A wireless device may determine radio resources and / or uplink transmit power for the preamble 1341 and / or transport block 1342 (e.g., included in the first message (e.g., MsgA 1331)) based on two-step RACH parameters included in the configuration message 1330. The RACH parameters may indicate MCS, time-frequency resources, and / or power control for the preamble 1341 and / or transport block 1342. The time-frequency resources for transmission of the preamble 1341 (e.g., PRACH) and the time-frequency resources for transmission of the transport block 1342 (e.g., PUSCH) may be multiplexed using FDM, TDM, and / or CDM. The RACH parameters may enable the wireless device to determine receive timing and downlink channels for monitoring and / or receiving the second message (e.g., MsgB 1332).

[0134] The transport block 1342 may include data (e.g., delay-sensitive data), a wireless device identifier, security information, and / or device information (e.g., International Mobile Subscriber Identity (IMSI)). The base station may send / transmit a second message (e.g., MsgB 1332) in response to the first message (e.g., MsgA 1331). The second message (e.g., MsgB 1332) may include at least one of a preamble identifier, a timing advance command, a power control command, an uplink grant (e.g., radio resource allocation and / or MCS), a wireless device identifier (e.g., a UE identifier for contention resolution), and / or an RNTI (e.g., C-RNTI or TC-RNTI). The wireless device may determine that the two-step random access procedure has been successfully completed, for example, if the preamble identifier of the second message (e.g., MsgB 1332) corresponds to or matches the preamble transmitted / transmitted by the wireless device and / or if the identifier of the wireless device of the second message (e.g., MsgB 1332) corresponds to or matches the identifier of the wireless device (e.g., transport block 1342) of the first message (e.g., MsgA 1331).

[0135] The wireless device and the base station may exchange control signaling (e.g., control information). 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) of the wireless device or the base station. The control signaling may include downlink control signaling transmitted / transmitted from the base station to the wireless device and / or uplink control signaling transmitted / transmitted from the wireless device to the base station.

[0136] The downlink control signaling may include at least one of an uplink scheduling grant indicating a downlink scheduling assignment, an uplink radio resource, and / or a transport format, slot format information, a preemption indication, a power control command, and / or any other suitable signaling. A wireless device may receive the downlink control signaling in a payload transmitted / sent by a base station via a PDCCH. The payload transmitted / sent via the PDCCH may be referred to as downlink control information (DCI). The PDCCH may be a group-common PDCCH (GC-PDCCH) that is common to a group of wireless devices. The GC-PDCCH may be scrambled by a group-common RNTI.

[0137] A base station may attach one or more cyclic redundancy check (CRC) parity bits to the DCI, for example, to facilitate detection of transmission errors. The base station may scramble the CRC parity bits with an identifier of the wireless device (or an identifier of a group of wireless devices), for example, if the DCI is intended for the wireless device (or a group of wireless devices). Scrambling the CRC parity bits with the identifier may include a modulo-2 addition (or exclusive-OR operation) of the identifier value and the CRC parity bits. The identifier may include a 16-bit value of the RNTI.

[0138] DCIs may be used for different purposes. The purpose may be indicated by the type of RNTI used to scramble the CRC parity bits. A DCI with CRC parity bits scrambled with a paging RNTI (P-RNTI) may indicate paging information and / or system information change notification. The P-RNTI may be predefined as "FFFE" in hexadecimal. A DCI with CRC parity bits scrambled with a system information RNTI (SI-RNTI) may indicate a broadcast transmission of system information. The SI-RNTI may be predefined as "FFFF" in hexadecimal. A DCI with CRC parity bits scrambled with a random access RNTI (RA-RNTI) may indicate a random access response (RAR). A DCI with CRC parity bits scrambled with a cell RNTI (C-RNTI) may indicate a unicast transmission of dynamic scheduling and / or a random access of PDCCH order trigger. A DCI with CRC parity bits scrambled with the Temporary Cell RNTI (TC-RNTI) may indicate contention resolution (e.g., Msg3 similar to Msg3 1313 shown in FIG. 13A). Other RNTIs configured for the wireless device by the base station include 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.

[0139] A base station may transmit / transmit DCI in one or more DCI formats depending on, for example, the purpose and / or content of the DCI. DCI format 0_0 may be used for scheduling a PUSCH in a cell. DCI format 0_0 may be a fallback DCI format (e.g., having a compact DCI payload). DCI format 0_1 ​​may be used for scheduling a PUSCH in a cell (e.g., having a larger DCI payload than DCI format 0_0). DCI format 1_0 may be used for scheduling a PDSCH in a cell. DCI format 1_0 may be a fallback DCI format (e.g., having a compact DCI payload). DCI format 1_1 may be used for scheduling a PDSCH in a cell (e.g., having a larger DCI payload than DCI format 1_0). DCI format 2_0 may be used to provide slot format indication to a group of wireless devices. DCI format 2_1 may be used to inform / inform a group of wireless devices of physical resource blocks and / or OFDM symbols that the group of wireless devices may assume are not intended for the group of wireless devices. DCI format 2_2 may be used to transmit transmit power control (TPC) commands for the PUCCH or PUSCH. DCI format 2_3 may be used to transmit a group of TPC commands for SRS transmission by one or more wireless devices. DCI formats for new features may be defined in future releases. DCI formats may have different DCI sizes or share the same DCI size.

[0140] A base station may process the DCI using channel coding (e.g., polarity coding), rate matching, scrambling, and / or QPSK modulation, for example, after scrambling the DCI with the RNTI. The base station may map the coded and modulated DCI onto resource elements used and / or configured for the PDCCH. The base station may transmit / transmit the DCI via a PDCCH occupying some amount / number of consecutive control channel elements (CCEs), for example, based on the payload size of the DCI and / or the coverage of the base station. The amount / number of consecutive CCEs (called aggregation levels) may be 1, 2, 4, 8, 16, and / or any other suitable amount / number. A CCE may include a number of resource element groups (REGs) (e.g., 6). A REG may include a resource block in an OFDM symbol. The mapping of the coded and modulated DCI onto resource elements may be based on a mapping between CCEs and REGs (e.g., CCE-to-REG mapping).

[0141] FIG. 14A shows an example of a CORESET configuration. The CORESET configuration may be for a bandwidth portion or any other frequency band. A base station may transmit / convey DCI via the PDCCH on one or more control resource sets (CORESETs). A CORESET may include time-frequency resources on which a wireless device attempts to decode the DCI using one or more search spaces. A base station may configure the size and location of the CORESET in the time-frequency domain. The first CORESET 1401 and the second CORESET 1402 may occur or be configured / set at the first symbol in a slot. The first CORESET 1401 may overlap with the second CORESET 1402 in the frequency domain. The third CORESET 1403 may occur or be configured / set at the third symbol in a slot. The fourth CORESET 1404 may occur or be configured / set at the seventh symbol in a slot. The CORESETs may have different amounts / numbers of resource blocks in the frequency domain.

[0142] FIG. 14B shows an example of CCE-to-REG mapping. CCE-to-REG mapping may be implemented for DCI transmission via CORESET and PDCCH processing. CCE-to-REG mapping may be interleaved (e.g., to provide frequency diversity) or non-interleaved (e.g., to facilitate interference coordination and / or frequency-selective transmission of control channels). A base station may implement different or identical CCE-to-REG mappings in different CORESETs. A CORESET may be associated with a CCE-to-REG mapping (e.g., by RRC configuration). A CORESET may be configured with an antenna port QCL parameter. The QCL parameter of an antenna port may indicate QCL information of a DM-RS for PDCCH reception via a CORESET.

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

[0144] As shown in FIG. 14B , the wireless device may determine the time-frequency resources of the CORESET based on one or more RRC messages. The wireless device may determine the CCE-to-REG mapping (e.g., interleaved or non-interleaved, and / or mapping parameters) of the CORESET, for example, based on configuration parameters of the CORESET. The wireless device may determine the amount / number (e.g., up to 10) of search space sets configured on / for the CORESET, for example, based on one or more RRC messages. The wireless device may monitor a set of PDCCH candidates according to the configuration parameters of the search space sets. The wireless device may monitor a set of PDCCH candidates in one or more CORESETs to detect one or more DCIs. The monitoring may include decoding one or more PDCCH candidates of the set of PDCCH candidates according to the monitored DCI format. The monitoring may include decoding DCI content of one or more PDCCH candidates in possible (or configured) PDCCH locations, possible (or configured) PDCCH formats (e.g., amount / number of CCEs, amount / number of PDCCH candidates in a common search space, and / or amount / number of PDCCH candidates in a wireless device-specific search space), and possible (or configured) DCI formats. The decoding may be referred to as blind decoding. The wireless device may determine the DCI to be valid for the wireless device, for example, based on (e.g., subsequently in response to) a CRC check (e.g., scrambling bits of the CRC parity bits of the DCI that match the RNTI value). The wireless device may process information included in the DCI (e.g., scheduling assignment, uplink grant, power control, slot format indication, downlink preemption, and / or the like).

[0145] Uplink control signaling (e.g., UCI) may be sent / transmitted to the base station. The uplink control signaling may include a HARQ acknowledgment for a received DL-SCH transport block. The wireless device may send / transmit the HARQ acknowledgment, for example, based on (e.g., subsequently in response to) receiving the DL-SCH transport block. The uplink control signaling may include CSI indicating the channel quality of the physical downlink channel. The wireless device may send / transmit the CSI to the base station. The base station may determine transmission format parameters (e.g., including multiple antennas and a beamforming scheme) for the downlink transmission based on the received CSI. The uplink control signaling may include a scheduling request (SR). The wireless device may send / convey an SR indicating that uplink data is available for transmission to the base station. The wireless device may send / transmit UCI (e.g., a HARQ acknowledgment (HARQ-ACK), a CSI report, an SR, etc.) via the PUCCH or PUSCH. A wireless device may transmit / carry uplink control signaling over the PUCCH using one of several PUCCH formats.

[0146] There may be multiple PUCCH formats (e.g., five PUCCH formats). A wireless device may determine the PUCCH format based on, for example, the size of the UCI (e.g., the amount / number of uplink symbols for UCI transmission and the amount / number of UCI bits). PUCCH format 0 may have a length of one or two OFDM symbols and may include two or fewer bits. A wireless device may use PUCCH format 0 to transmit UCI over PUCCH resources, for example, if the transmission spans one or two symbols and the amount / 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 certain amount / number of OFDM symbols (e.g., between four and fourteen OFDM symbols) and may include two or fewer bits. A wireless device may use PUCCH format 1, for example, if the transmission spans four or more symbols and the amount / 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. A wireless device may use PUCCH format 2, for example, when a transmission spans one or two symbols and the amount / number of UCI bits is two or more. PUCCH format 3 may occupy a certain amount / number of OFDM symbols (e.g., between 4 and 14 OFDM symbols) and may include more than two bits. A wireless device may use PUCCH format 3, for example, when a transmission is four or more symbols, the amount / number of UCI bits is two or more, and the PUCCH resource does not include an orthogonal cover code (OCC). PUCCH format 4 may occupy a certain amount / number of OFDM symbols (e.g., between 4 and 14 OFDM symbols) and may include more than two bits. A wireless device may use PUCCH format 4, for example, when a transmission is four or more symbols, the amount / number of UCI bits is two or more, and the PUCCH resource includes an OCC.

[0147] A base station may transmit / convey configuration parameters for multiple PUCCH resource sets to a wireless device, for example, using an RRC message. Multiple PUCCH resource sets (e.g., up to four sets in NR or up to any other amount of sets in other systems) may be configured on the uplink BWP of a cell. A PUCCH resource set may be configured with a PUCCH resource set index, multiple PUCCH resources with the PUCCH resource identified by a PUCCH resource identifier (e.g., pucch-Resourceid), and / or some amount / number (e.g., a maximum amount / number) of UCI information bits that the wireless device can transmit / transmit using one of the multiple PUCCH resources in the PUCCH resource set. When configured with multiple PUCCH resource sets, the wireless device may select one of the multiple PUCCH resource sets based, for example, on the total bit length of the UCI information bits (e.g., HARQ-ACK, SR, and / or CSI). The wireless device may, for example, select a first PUCCH resource set with a PUCCH resource set index equal to "0" if the total bit length of the UCI information bits is less than or equal to 2. The wireless device may, for example, select a second PUCCH resource set with a PUCCH resource set index equal to "1" if the total bit length of the UCI information bits is greater than 2 and less than or equal to a first configuration value. The wireless device may, for example, select a third PUCCH resource set with a PUCCH resource set index equal to "2" if the total bit length of the UCI information bits is greater than a first configuration value and less than or equal to a second configuration value. The wireless device may, for example, select a fourth PUCCH resource set with a PUCCH resource set index equal to "3" if the total bit length of the UCI information bits is greater than a second configuration value and less than or equal to a third value (e.g., 1406, 1706, or any other number of bits).

[0148] After determining a PUCCH resource set from multiple PUCCH resource sets, the wireless device may determine a PUCCH resource from the PUCCH resource set for UCI (HARQ-ACK, CSI, and / or SR) transmission. The wireless device may determine the PUCCH resource, for example, based on a PUCCH resource indicator in DCI (e.g., in DCI format 1_0 or DCI format 1_1) received on / via the PDCCH. An n-bit (e.g., 3-bit) PUCCH resource indicator in the DCI may indicate one of multiple (e.g., 8) PUCCH resources in the PUCCH resource set. The wireless device may transmit / transmit UCI (HARQ-ACK, CSI, and / or SR) based on the PUCCH resource indicator, for example, using the PUCCH resource indicated by the PUCCH resource indicator of the DCI.

[0149] 15A shows an example of communication between a wireless device and a base station. The wireless device 1502 and the base station 1504 may be part of a communication network, such as the communication network 100 shown in FIG. 1A, the communication network 150 shown in FIG. 1B, or another communication network. The communication network may include two or more wireless devices and / or two or more base stations having substantially the same or similar configurations as those shown in FIG. 15A.

[0150] The base station 1504 may connect the wireless device 1502 to a core network (not shown) via wireless communication over an air interface (or radio interface) 1506. The direction of communication from the base station 1504 to the wireless device 1502 over the air interface 1506 may be referred to as the downlink. The direction of communication from the wireless device 1502 to the base station 1504 over the air interface may be referred to as the uplink. The downlink transmission may be separated from the uplink transmission using, for example, various duplexing schemes (e.g., FDD, TDD, and / or some combination of duplexing techniques).

[0151] For the downlink, data transmitted from the base station 1504 to the wireless device 1502 may be provided / forwarded / transmitted to the processing system 1508 of the base station 1504. The data may be provided / forwarded / transmitted to the processing system 1508 by, for example, a core network. For the uplink, data transmitted from the wireless device 1502 to the base station 1504 may be provided / forwarded / transmitted 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 functions to process the data for transmission. Layer 2 may include, for example, the SDAP layer, PDCP layer, RLC layer, and MAC layer described with respect to Figures 2A, 2B, 3, and 4A. Layer 3 may include, for example, the RRC layer described with respect to Figure 2B.

[0152] Data to be transmitted to the wireless device 1502 may be processed by, for example, processing system 1508 before being provided / forwarded / transmitted to a transmission processing system 1510 of the base station 1504. Data to be transmitted to the base station 1504 may be processed by, for example, processing system 1518 before being provided / forwarded / transmitted to a transmission processing system 1520 of the wireless device 1502. The transmission processing system 1510 and the transmission processing system 1520 may implement the OSI functions of Layer 1. Layer 1 may include, for example, the PHY layer described with respect to FIGS. 2A, 2B, 3, and 4A. For transmission 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 channels, multiple-input multiple-output (MIMO) or multi-antenna processing, and / or the like.

[0153] The receive processing system 1512 of the base station 1504 may receive uplink transmissions from the wireless device 1502. The receive processing system 1512 of the base station 1504 may include one or more TRPs. The receive processing system 1522 of the wireless device 1502 may receive downlink transmissions from the base station 1504. The receive processing system 1522 of the wireless device 1502 may include one or more antenna panels. The receive processing system 1512 and the receive processing system 1522 may implement Layer 1 OSI functions. Layer 1 may include, for example, the PHY layer described with respect to FIGS. 2A, 2B, 3, and 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.

[0154] The base station 1504 may include multiple antennas (e.g., multiple antenna panels, multiple TRPs, etc.). The wireless device 1502 may include multiple antennas (e.g., multiple antenna panels, etc.). The multiple antennas may be used to implement 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. The wireless device 1502 and / or the base station 1504 may have a single antenna.

[0155] Processing system 1508 and processing system 1518 may be associated with memory 1514 and memory 1524, respectively. Memory 1514 and memory 1524 (e.g., one or more non-transitory computer-readable media) may store computer program instructions or code that may be executed by processing system 1508 and / or processing system 1518, respectively, to perform one or more of the functions (e.g., one or more functions described herein and other functions of a general computer, processor, memory, and / or other peripheral device). Transmit processing system 1510 and / or receive processing system 1512 may be coupled to memory 1514 and / or another memory (e.g., one or more non-transitory computer-readable media) that store computer program instructions or code that may be executed to perform one or more of their respective functions. The transmit processing system 1520 and / or the receive processing system 1522 may be coupled to memory 1524 and / or another memory (e.g., one or more non-transitory computer-readable media) that stores computer program instructions or code that may be executed to perform one or more of their respective functions.

[0156] The processing system 1508 and / or the processing system 1518 may include one or more controllers and / or one or more processors. The one or more controllers and / or the one or more processors may include, 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 devices, discrete gate and / or transistor logic, discrete hardware components, on-board units, 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 / or the base station 1504 to operate in a wireless environment.

[0157] The processing system 1508 may be connected to one or more peripheral devices 1516. The processing system 1518 may be connected to one or more peripheral devices 1526. The one or more peripheral devices 1516 and the one or more peripheral devices 1526 may include software and / or hardware that provide features and / or functionality, such as a speaker, a microphone, a keypad, a display, a touchpad, a power supply, a satellite transceiver, a universal serial bus (USB) port, a hands-free headset, a frequency modulation (FM) radio unit, a media player, an internet browser, an electronic control unit (e.g., for a 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 input data (e.g., user input data) from and / or provide output data (e.g., user output data) to the one or more peripheral devices 1516 and / or the one or more peripheral devices 1526. The processing system 1518 of the wireless device 1502 may receive power from a power source and / or may be configured to distribute power to other components of the wireless device 1502. The power source may include one or more power sources, such as a battery, a solar cell, a fuel cell, or any combination thereof. The processing system 1508 may be connected to a global positioning system (GPS) chipset 1517. The processing system 1518 may be connected to a global positioning system (GPS) chipset 1527. The GPS chipset 1517 and the GPS chipset 1527 may be configured to determine and provide geographic location information for the wireless device 1502 and the base station 1504, respectively.

[0158] 15B shows exemplary elements of a computing device that may be used to implement any of the various apparatuses described herein, including, for example, base station 160A, 160B, 162A, 162B, 220, and / or 1504, wireless device 106, 156A, 156B, 210, and / or 1502, or any other base station, wireless device, AMF, UPF, network apparatus, or computing device described herein. Computing device 1530 may include one or more processors 1531 that may execute instructions stored in random access memory (RAM) 1533, removable media 1534 (such as a universal serial bus (USB) drive, compact disc (CD) or digital versatile disc (DVD), or floppy disk drive), or any other desired storage medium. Instructions may also be stored on an attached (or internal) hard drive 1535. The computing device 1530 may also include a security processor (not shown) that may execute instructions of one or more computer programs to monitor processes running on the processor 1531 and any processes requesting access to any hardware and / or software components of the computing device 1530 (e.g., ROM 1532, RAM 1533, removable media 1534, hard drive 1535, device controller 1537, network interface 1539, GPS 1541, Bluetooth interface 1542, WiFi interface 1543, etc.). The computing device 1530 may include one or more output devices such as a display 1536 (e.g., a screen, display device, monitor, television, etc.) and may include one or more output device controllers 1537, such as a video processor. There may also be one or more user input devices 1538, such as a remote control, keyboard, mouse, touchscreen, microphone, etc.The computing device 1530 may also include one or more network interfaces, such as a network interface 1539, which may be a wired interface, a wireless interface, or a combination of the two. The network interface 1539 may provide an interface for the computing device 1530 to communicate with a network 1540 (e.g., a RAN, or any other network). The network interface 1539 may include a modem (e.g., a cable modem), and the external network 1540 may include a communications link, an external network, a home network, a provider's wireless, coaxial, fiber, or hybrid fiber / coaxial distribution system (e.g., a DOCSIS network), or any other desired network. Additionally, the computing device 1530 may include a location detection device, such as a global positioning system (GPS) microprocessor 1541, which may be configured to receive and process global positioning signals and, with possible assistance from external servers and antennas, determine the geographic location of the computing device 1530.

[0159] While Figure 15B may be a hardware configuration, the components shown may also be implemented as software. Changes may be made, as desired, to add, remove, combine, divide, etc., components of computing device 1530. Additionally, components may be implemented using basic computing devices and components, and the same components (e.g., processor 1531, ROM storage 1532, display 1536, etc.) may be used to implement any of the other computing devices and components described herein. For example, the various components described herein may be implemented using a computing device having components such as a processor that executes computer-executable instructions stored on a computer-readable medium, as shown in Figure 15B. Some or all of the entities described herein may be software-based and coexist on a common physical platform (e.g., a requesting entity may be a separate software process and program from a dependent entity, both of which may run as software on a common computing device).

[0160] Figure 16A shows an example structure for uplink transmission. The processing of the baseband signal representing the physical uplink shared channel may include / implement one or more functions. The one or more functions may include at least one of scrambling, modulation of scrambled bits to generate complex-valued symbols, mapping of 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 the precoded complex-valued symbols to resource elements, complex-valued time-domain single-carrier frequency-division multiple access (SC-FDMA), generation of a CP-OFDM signal for an antenna port, or any other signal, and / or the like. The SC-FDMA signal for uplink transmission may be generated, for example, when transform precoding is enabled. The CP-OFDM signal for uplink transmission may be generated, for example, when transform precoding is not enabled (e.g., as shown in Figure 16A). These functions are examples, and other mechanisms for uplink transmission may be implemented.

[0161] 16B shows an exemplary structure for modulation and upconversion of a baseband signal to a carrier frequency. The baseband signal may be a complex-valued SC-FDMA, CP-OFDM baseband signal (or any other baseband signal) for an antenna port, and / or a complex-valued Physical Random Access Channel (PRACH) baseband signal. Filtering may be performed / employed, for example, before transmission.

[0162] Figure 16C shows an example structure of a downlink transmission. The processing of a baseband signal representing a physical downlink channel may include / perform one or more functions. The one or more functions may include scrambling coded bits within a codeword to be transmitted / transmitted on / via the physical channel, modulating the scrambled bits to generate complex-valued modulation symbols, mapping the complex-valued modulation symbols onto one or more transmission layers, precoding the complex-valued modulation symbols on the layers for transmission on the antenna ports, mapping the complex-valued modulation symbols of the antenna ports to resource elements, generating a complex-valued time-domain OFDM signal per antenna port, and / or the like. These functions are examples, and other mechanisms for downlink transmission may be implemented.

[0163] 16D shows an exemplary structure for modulation and upconversion of a baseband signal to a carrier frequency. The baseband signal may be a complex-valued OFDM baseband signal for an antenna port or any other signal. Filtering may be performed / employed, for example, before transmission.

[0164] A wireless device may receive one or more messages (e.g., RRC messages) from a base station that include configuration parameters for multiple cells (e.g., a primary cell, one or more secondary cells). The wireless device may communicate with at least one base station (e.g., two or more base stations for dual connectivity) via the multiple cells. The one or more messages (e.g., as part of the configuration parameters) may include PHY, MAC, RLC, PCDP, SDAP, and RRC layer parameters for configuring the wireless device. The configuration parameters may include parameters for configuring PHY and MAC layer channels, bearers, etc. The configuration parameters may include parameters indicating timer values ​​for the PHY, MAC, RLC, PCDP, SDAP, RRC layers, and / or communication channels.

[0165] A timer may, for example, begin running when started and continue running until it is stopped or 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., a timer may be started or restarted from a value, or may start from zero and expire when the value is reached). A timer's duration may not be updated, for example, until the timer is stopped or expires (e.g., due to a BWP switch). A timer may be used to measure a time period / window of a process. It will be understood that with respect to implementations and / or procedures related to one or more timers or other parameters, there may be multiple ways to implement the one or more timers or other parameters. One or more of multiple ways of implementing a timer may be used to measure the time period / window of a procedure. A random access response window timer may be used to measure a window of time for receiving a random access response. The time difference between two timestamps may be used, for example, instead of starting a random access response window timer and determining timer expiration. The process for measuring the time window may be restarted, for example, if the timer is restarted. Other exemplary implementations may be configured / provided to restart the measurement of the time window.

[0166] The wireless device may receive one or more messages (e.g., an RRC message or an RRC reconfiguration message) from the base station. The one or more messages may include one or more configuration parameters. The one or more configuration parameters may be for one or more cells (e.g., a cell). The one or more configuration parameters may include one or more PDSCH configuration parameters for the cell (e.g., as in a PDSCH-Config information element, as shown in FIG. 20C).

[0167] The one or more configuration parameters may indicate a list of aperiodic trigger states for an aperiodic CSI report (e.g., based on the higher layer parameter CSI-AperiodicTriggerStateList information element as shown in FIG. 20B). The wireless device may receive a DCI that triggers transmission of an aperiodic CSI report. The DCI may indicate, for example, an aperiodic trigger state from a list of aperiodic trigger states. The aperiodic trigger state may include and / or indicate a list of CSI report configuration information (e.g., associatedReportConfigInfoList as shown in FIG. 20B). The list of CSI report configuration information may include CSI report configuration information. The CSI report configuration information (e.g., CSI-AssociatedReportConfigInfo as shown in FIG. 20B) may include and / or indicate a reference signal resource set (e.g., NZP-CSI-RS-ResourceSet, resourceSet, resourceSet2 in FIG. 20B) for channel measurements. The reference signal resource set may include one or more reference signal resources. The one or more reference signal resources may indicate / configure (or may be associated with) one or more reference signals (e.g., CSI-RS, TRS, aperiodic CSI-RS, etc.). The CSI report configuration information may include at least one TCI state index / identifier (e.g., TCI-StateId in FIG. 20B).

[0168] In at least some wireless communications, the wireless device receives and / or measures and / or evaluates one or more reference signals based on at least one of one or more TCI states indicated by and / or configured based on a TCI state list parameter (e.g., an add or modify TCI state parameter such as tci-StatesToAddModList, as shown in FIG. 20C). The TCI state list parameter may be identified and / or indicated by at least one TCI state index and / or identifier. One or more PDSCH configuration parameters may include the TCI state list parameter. Each TCI state index and / or identifier of the at least one TCI state index and / or identifier may indicate and / or identify a respective TCI state of the at least one TCI state.

[0169] One or more PDSCH configuration parameters may not include a TCI state list parameter (e.g., tci-StatesToAddModList). The wireless device may not receive, measure, and / or evaluate one or more reference signals based on the TCI state. For example, one or more reference signals may not be received, measured, and / or evaluated based on (e.g., due to) one or more PDSCH configuration parameters that do not include a TCI state list parameter. Not receiving, measuring, and / or evaluating one or more reference signals may result in inaccurate channel estimation. The wireless device may not measure the radio link quality of one or more reference signals, for example, based on not receiving and / or measuring one or more reference signals based on the TCI state. The wireless device may inaccurately measure the radio link quality of one or more reference signals, for example, based on not receiving and / or measuring one or more reference signals based on the TCI state.

[0170] As disclosed herein, CSI reporting (e.g., aperiodic CSI reporting) may be enhanced, for example, when one or more PDSCH configuration parameters do not include a TCI state list parameter (e.g., tci-StatesToAddModList). Although an example of aperiodic CSI reporting is discussed herein, the concepts herein may also or alternatively apply to periodic CSI reporting. One or more PDSCH configuration parameters may include a downlink or joint TCI state list parameter (e.g., dl-OrJoint-TCI-StateList in FIG. 20C).

[0171] The downlink or joint TCI state list parameter may include a downlink or joint TCI state parameter (e.g., a downlink or joint TCI state add or modify parameter such as dl-OrJointTCI-StateToAddModList in FIG. 20C ) indicating one or more TCI states. The wireless device may receive, measure, and / or evaluate one or more reference signals based on at least one TCI state from among the one or more TCI states indicated and / or configured by the downlink joint TCI state parameter, identified and / or indicated by the at least one TCI state index and / or identifier. Each TCI state index of the at least one TCI state index and / or identifier may indicate and / or identify a respective TCI state of the at least one TCI state.

[0172] The downlink or joint TCI state list parameter may include a unified TCI state reference parameter (e.g., unifiedTCI-StateRef in FIG. 20C). The downlink or joint TCI state list parameter may not include a downlink or joint TCI state parameter (e.g., dl-OrJointTCI-StateToAddModList in FIG. 20C). The unified TCI state reference parameter may indicate to a reference cell and a reference BWP whether a downlink or joint TCI state parameter (e.g., dl-OrJointTCI-StateToAddModList in FIG. 20C) is configured / defined for a cell (or a BWP of a cell). One or more cells may include the reference cell. The one or more configuration parameters may include one or more second PDSCH configuration parameters of the reference cell (e.g., PDSCH-Config in FIG. 20 and FIG. 20C and FIG. 21). The one or more second PDSCH configuration parameters may include a downlink or joint TCI state parameter (e.g., dl-OrJointTCI-StateToAddModList in FIG. 20C ) indicating one or more TCI states. The wireless device may receive, measure, and / or evaluate one or more reference signals based on at least one TCI state among the one or more TCI states indicated and / or configured by the downlink or joint TCI state parameter of the reference BWP of the reference cell, identified and / or indicated by the at least one TCI state index and / or identifier. Each TCI state index of the at least one TCI state index and / or identifier may indicate and / or identify a respective TCI state of the at least one TCI state. CSI reporting (e.g., aperiodic CSI reporting and / or periodic CSI reporting) may be enhanced as disclosed herein. The wireless device may accurately measure the radio link quality of one or more reference signals (e.g., when a TCI state is not configured for the cell). This may lead to better channel estimation and / or scheduling decisions by the base station.

[0173] A wireless device may receive (e.g., from a base station) one or more messages (e.g., an RRC message, an RRC reconfiguration message, etc.) including one or more configuration parameters. The one or more configuration parameters may be for a cell consisting of one or more cells. The one or more configuration parameters may include one or more PDSCH configuration parameters of the cell (e.g., PDSCH-Config1935, e.g., in Figures 19, 20C, and 21). The one or more configuration parameters may indicate a reference signal resource for periodic CSI reporting (e.g., provided by the higher layer parameter NZP-CSI-RS-Resource in Figure 20A). The reference signal resource may indicate, configure, and / or be associated with a reference signal (e.g., CSI-RS, TRS, aperiodic CSI-RS). The one or more configuration parameters may indicate a TCI state index and / or identifier (e.g., tci-StateId, as shown in Figure 20A) for the reference signal resource.

[0174] In at least some wireless communications, a wireless device may receive, measure, and / or evaluate a reference signal based on one or more TCI states indicated and / or configured by a TCI state list parameter (e.g., tci-StatesToAddModList in FIG. 20C ), which are identified and / or indicated by a TCI state index / identifier. One or more PDSCH configuration parameters may include the TCI state list parameter. One or more PDSCH configuration parameters may not include a TCI state list parameter (e.g., tci-StatesToAddModList). For example, the wireless device may not receive, measure, and / or evaluate a reference signal based on a TCI state in response to one or more PDSCH configuration parameters that do not include a TCI state list parameter. This may lead to inaccurate channel estimation. For example, the wireless device may not measure the radio link quality of the reference signal in response to not receiving and / or measuring a reference signal based on a TCI state. The wireless device may measure the radio link quality of an inaccurate reference signal, for example, in response to not receiving and / or measuring the reference signal based on the TCI condition.

[0175] As disclosed herein, periodic CSI reporting may be enhanced for cases where one or more PDSCH configuration parameters do not include a TCI state list parameter (e.g., tci-StatesToAddModList). One or more PDSCH configuration parameters may include a downlink or joint TCI state list parameter (e.g., dl-OrJoint-TCI-StateList, shown in FIG. 20C).

[0176] The downlink or joint TCI state list parameter may include a downlink or joint TCI state parameter (e.g., dl-OrJointTCI-StateToAddModList, as shown in FIG. 20C ) indicating one or more TCI states. The wireless device may receive, measure, and / or evaluate the reference signal based on the TCI state indicated and / or configured by the downlink or joint TCI state parameter, identified and / or indicated by the TCI state index and / or identifier.

[0177] The downlink or joint TCI state list parameter may include a unified TCI state reference parameter (unifiedTCI-StateRef, shown in FIG. 20C). The downlink or joint TCI state list parameter may not include a downlink or joint TCI state parameter (e.g., dl-OrJointTCI-StateToAddModList, shown in FIG. 20C). The unified TCI state reference parameter may indicate a reference cell and / or a reference BWP for which the downlink or joint TCI state parameter (e.g., dl-OrJointTCI-StateToAddModList in FIG. 20C) is configured and / or defined. One or more cells may include the reference cell. The one or more configuration parameters may include one or more second PDSCH configuration parameters of the reference cell (e.g., PDSCH-Config1935, such as in FIGs. 19, 20C, and 21). The one or more second PDSCH configuration parameters may include a downlink or joint TCI state parameter (e.g., dl-OrJointTCI-StateToAddModList, such as in FIG. 20C ) indicating one or more TCI states. The wireless device may receive, measure, and / or evaluate the reference signal based on the TCI state among one or more TCI states indicated and / or configured based on the downlink or joint TCI state parameter of the reference BWP of the reference cell, identified and / or indicated by the TCI state index and / or identifier. Using the unified TCI state reference parameter (e.g., based on not receiving and / or configuring the downlink or joint TCI state parameter) may enhance periodic and / or aperiodic CSI reporting. The wireless device may accurately measure the radio link quality of the reference signal (e.g., based on the unified TCI state reference parameter). This may lead to / enable better channel estimation and / or scheduling decisions by the base station.

[0178] 17 and 18 illustrate examples of TCI state activation. A wireless device may receive one or more messages. FIG. 17 illustrates an example of TCI state activation. A wireless device 1705 may receive one or more messages from a base station 1710. A wireless device 1705 may receive one or more messages from a relay node. A wireless device 1705 may receive one or more messages from another wireless device (e.g., a TRP, a vehicle, a remote radio head, etc.). The one or more messages may include one or more configuration parameters 1720 (e.g., configuration parameters at time T0 as shown in FIG. 17).

[0179] The one or more configuration parameters 1720 may be RRC configuration parameters. The one or more configuration parameters may be one or more RRC reconfiguration parameters (e.g., RRCReconfiguration, reconfigurationWithSync). The one or more messages may be one or more RRC messages. The one or more messages may be one or more RRC reconfiguration messages (e.g., RRCReconfiguration, reconfigurationWithSync).

[0180] The one or more configuration parameters 1720 may be RRC reconfiguration parameters. The one or more configuration parameters 1720 may be for one or more cells. The one or more cells may include one cell. The cell may be, for example, a serving cell. At least one configuration parameter of the one or more configuration parameters 1720 may be for a cell. The cell may be a primary cell (PCell). The cell may be a primary secondary cell (PSCell). The cell may be a secondary cell (SCell). The cell may be a secondary cell configured for / with a PUCCH (e.g., a PUCCH SCell). The cell may be a special cell (SpCell). For dual connectivity (DC) operation, the SpCell may point to (or indicate) a PCell of an MCG or a PSCell of an SCG. The SpCell may point to (or indicate) a PCell. The cell may be a primary SCG cell (PSCell). For dual connectivity operation, the wireless device may perform a random access procedure via the PSCell, for example, when performing reconfiguration in a Sync procedure.

[0181] The cell may be an unlicensed cell (e.g., operating in an unlicensed band). The cell may be a licensed cell (e.g., operating in a licensed band). The cell may operate in a first frequency range (e.g., FR1). FR1 may include, for example, a frequency band below 6 GHz. The cell may operate in a second frequency range (e.g., FR2). FR2 may include, for example, a frequency band from 24 GHz to 52.6 GHz. The cell may operate in a third frequency range (FR3). FR3 may include, for example, a frequency band from 52.6 GHz to 71 GHz. FR3 may include, for example, a frequency band starting at 52.6 GHz.

[0182] The wireless device 1705 may perform uplink transmission (e.g., PUSCH, PUCCH, PUCCH) via and / or using the cell at a first time and / or first frequency. The wireless device 1705 may perform downlink reception (e.g., PDCCH, PDSCH) via and / or using the cell at a second time and / or second frequency. The cell may operate in time division duplex (TDD) mode. In TDD mode, the first frequency and the second frequency may be the same. In TDD mode, the first time and the second time may be different. The cell may operate in frequency division duplex (FDD) mode. The first frequency and the second frequency may be different in FDD mode. In FDD mode, the first time and the second time may be the same. The wireless device 1705 may be in an RRC connected mode. The wireless device 1705 may be in an RRC idle mode. The wireless device 1705 may be in an RRC inactive mode.

[0183] A cell may include multiple BWPs. The multiple BWPs may include one or more uplink BWPs, including an uplink BWP (UL BWP) of the cell. The multiple BWPs may include one or more downlink BWPs, including a downlink BWP of the cell. The BWPs of the multiple BWPs may be in either an active state or an inactive state (or stopped state). In a downlink BWP active state of one or more downlink BWPs, for example, the wireless device 1705 may monitor downlink channels and / or signals (e.g., PDCCH, DCI, CSI-RS, PDSCH) on, for, and / or via the downlink BWPs. In a downlink BWP active state of one or more downlink BWPs, the wireless device 1705 may receive a PDSCH on, for, and / or via the downlink BWPs. When one of the one or more downlink BWPs is in an inactive state, the wireless device 1705 may not monitor downlink channels and / or signals (e.g., PDCCH, DCI, CSI-RS, PDSCH) on, to, and / or via the downlink BWP. When one of the one or more downlink BWPs is in an inactive state, the wireless device may stop monitoring and / or receiving downlink channels and / or signals (e.g., PDCCH, DCI, CSI-RS, PDSCH) on, to, and / or via the downlink BWP. When one of the one or more downlink BWPs is in an inactive state, the wireless device 1705 may not receive PDSCH on, to, and / or via the downlink BWP. When one of the one or more downlink BWPs is in an inactive state, the wireless device 1705 may stop receiving PDSCH on, to, and / or via the downlink BWP.

[0184] In an uplink BWP active state of one or more uplink BWPs, the wireless device 1705 may transmit (e.g., send) uplink channels and / or signals (e.g., PUCCH, preamble, PUSCH, PRACH, PUCCH, etc.) on and / or via the uplink BWPs in an uplink BWP inactive state of one or more uplink BWPs. The wireless device may not transmit (e.g., send) uplink channels and / or signals (e.g., PUCCH, preamble, PUSCH, PRACH, PUCCH, etc.) on and / or via the uplink BWPs.

[0185] The wireless device 1705 may activate a downlink BWP of one or more downlink BWPs of the cell. Activating a downlink BWP may include setting and / or switching the downlink BWP as the active downlink BWP of the cell. Activating a downlink BWP may include setting the downlink BWP to an active state. Activating a downlink BWP may include switching the downlink BWP from an inactive state to an active state.

[0186] The wireless device 1705 may activate one uplink BWP of one or more uplink BWPs of the cell. Activating the uplink BWP may include the wireless device 1705 setting and / or switching the uplink BWP as an active uplink BWP for the cell. Activating the uplink BWP may include setting the uplink BWP to an active state. Activating the uplink BWP may include switching the uplink BWP from an inactive state to an active state.

[0187] The one or more configuration parameters may be for a downlink BWP of the cell (e.g., an active downlink BWP). At least one configuration parameter of the one or more configuration parameters may be for a downlink BWP of the cell. The one or more configuration parameters may indicate subcarrier spacing and / or numerology for the downlink BWP.

[0188] The one or more configuration parameters may be for an uplink BWP of the cell (e.g., an active uplink BWP). At least one configuration parameter of the one or more configuration parameters may be for the uplink BWP of the cell. The one or more configuration parameters may indicate subcarrier spacing and / or numerology for the uplink BWP.

[0189] The subcarrier spacing value of the downlink BWP and / or uplink BWP may be and / or may indicate, for example, 15 kHz (μ=0). The subcarrier spacing value may be and / or may indicate, for example, 30 kHz (μ=1). The subcarrier spacing value may be and / or may indicate, for example, 60 kHz (μ=2). The subcarrier spacing value may be and / or may indicate, for example, 120 kHz (μ=3). The subcarrier spacing value may be and / or may indicate, for example, 240 kHz (μ=4). The subcarrier spacing value may be and / or may indicate, for example, 480 kHz (μ=5). The subcarrier spacing value may be and / or may indicate, for example, 960 kHz (μ=6). 480 kHz may be valid and / or applicable in FR3. 960 kHz may be valid and / or applicable in FR3. 240 kHz may be valid and / or applicable in FR3. 120 kHz may be valid and / or applicable in FR3.

[0190] The one or more configuration parameters may indicate multiple control resource sets (core sets). The one or more configuration parameters may indicate multiple core sets of a cell's downlink BWP (e.g., active downlink BWP). A downlink BWP (e.g., active downlink BWP) may include multiple core sets. The one or more configuration parameters may indicate multiple core set indices, identifiers, and / or indicators (e.g., provided by the higher layer parameter ControlResourceSetId) for the multiple core sets. Each core set of the multiple core sets may be identified and / or indicated by a respective core set index of the multiple core set indexes. A first core set of the multiple core sets may be identified by a first core set index of the multiple core set indexes. A second core set 1858 of the multiple core sets may be identified by a second core set index of the multiple core set indexes.

[0191] The one or more configuration parameters 1720 may indicate one or more core set pool indices (e.g., provided by the upper layer parameter CoresetPoolIndex) for the multiple core sets. Each core set of the multiple core sets may be configured, indicated by, and / or included by one or more configuration parameters with a respective core set pool index of one or more core set pool indices (e.g., 0, 1, etc.). The one or more configuration parameters 1720 indicate a core set pool index corresponding to each of the one or more core set pool indices for each core set of the multiple core sets. The one or more configuration parameters 1720 may indicate, for example, a first core set pool index 1825 (CoresetPoolIndex=0) for a first core set of the multiple core sets. The one or more configuration parameters may indicate a second core set pool index 1845 (CoresetPoolIndex=1) for a second core set of the multiple core sets. The one or more core set pool indices may include a first core set pool index 1825 and a second core set pool index 1845.

[0192] Also, or alternatively, the one or more configuration parameters 1720 may not indicate a core set pool index for a core set of the plurality of core sets. The higher layer parameter CoresetPoolIndex may not be present in the configuration parameters for the core set. The 1805 wireless device may determine a value (e.g., a default value) of the core set pool index for the core set as the first core set pool index 1825 (CoresetPoolIndex=0). The first core set pool index 1825 (CoresetPoolIndex=0) may be the core set pool index for the core set, for example, based on one or more configuration parameters not indicating a core set pool index for the core set. The wireless device 1805 may determine a value (e.g., a default value) of the core set pool index for the core set as the first core set pool index 1825, for example, based on one or more configuration parameters not indicating a core set pool index for the core set.

[0193] A first core set pool (e.g., core set pool 0) may include one or more first core sets having a core set pool index that may be equal to the first core set pool index 1825 (e.g., CoresetPoolIndex=0). The one or more configuration parameters 1720 may indicate the first core set pool index 1825 of each core set of the one or more first core sets in the first core set pool. Multiple core sets may include one or more first core sets.

[0194] The second core set pool (e.g., core set pool 1) may include one or more second core sets having a core set pool index equal to the second core set pool index 1845 (e.g., CoresetPoolIndex=1). The one or more configuration parameters 1720 may indicate the second core set pool index 1845 for each core set of the one or more second core sets in the second core set pool. The multiple core sets may include one or more second core sets.

[0195] The one or more configuration parameters 1820 may not indicate a core set pool index for one of the multiple core sets. The wireless device 1805 may determine a default value for the core set pool index for the core set, for example, based on the one or more configuration 1820 parameters not indicating a core set pool index for the core set. The default value may be equal to zero (e.g., CoresetPoolIndex=0). The default value may be equal to the first core set pool index 1825 (e.g., zero). The first core set pool may include the core set, for example, based on the one or more configuration parameters not indicating a core set pool index for the core set. The first core set pool may include the core set, for example, based on the default value for the core set pool index for the core set being equal to the first core set pool index 1825.

[0196] The first core set pool index 1825 of the first core set and the second core set pool index 1845 of the second core set 1858 may be the same. Another configuration parameter may indicate the same core set pool index for the first core set and the second core set 1858. The multiple core sets may include the first core set and the second core set 1858. The one or more core set pool indexes may include the first core set pool index 1825 and the second core set pool index 1845. The wireless device 1805 may group the first core set and the second core set 1858 in the same core set pool (e.g., CoresetPoolIndex=0 or CoresetPoolIndex=1), for example, based on the first core set pool index 1825 of the first core set and the second core set pool index 1840 of the second core set 1858 being the same. The first core set pool containing the first core set and the second core set pool containing the second core set 1858 may be the same, for example, based on the first core set pool index 1825 of the first core set and the second core set pool index 1840 of the second core set 1858 being the same.

[0197] The first core set pool index 1825 of the first core set and the second core set pool index 1840 of the second core set 1858 may be different. The multiple core sets may include the first core set and the second core set 1858. The one or more core set pool indexes may include the first core set pool index 1825 and the second core set pool index 1840. The wireless device 1805 may group the first core set and the second core set 1858 into different core set pools, for example, based on the first core set pool index 1825 of the first core set and the second core set pool index 1840 of the second core set 1858 being different. The wireless device 1805 may group the first core set into the first core set pool (e.g., CoresetPoolIndex=0). The wireless device 1805 may group the second core set 1858 into a second core set pool (e.g., CoresetPoolIndex=1) that is different from the first core set pool, for example, based on the first core set pool index 1825 and the second core set pool index 1840 being different. The first core set pool and the second core set pool may be different, for example, based on the first core set pool index 1825 of the first core set and the second core set pool index 1840 of the second core set 1858 being different.

[0198] The one or more configuration parameters 1820 may indicate at least two core set pool indices (e.g., 0 and 1) for the upper layer parameter CORESETPoolIndex. The one or more configuration parameters 1820 may include an upper layer parameter CORESETPoolIndex having and / or configured with at least two core set pool indices. The at least two core set pool indices may include a first core set pool index 1825 (e.g., 0) for one or more first core sets of the plurality of core sets. The at least two core set pool indices may include a second core set pool index 1840 (e.g., 1) that is different from the first core set pool index 1825 for one or more second core sets of the plurality of core sets. The one or more first core sets may include one or more third core sets of the plurality of core sets without a value for the upper layer parameter CORESETPoolIndex. The one or more configuration parameters 1820 may not include the upper layer parameter CORESETPoolIndex for one or more third core sets.

[0199] A cell may include multiple transmit and receive points (TRPs). The multiple TRPs may correspond to the cell and / or wireless devices 1805 within, through, and / or of the cell. At least one TRP of the multiple TRPs may correspond to wireless devices within, through, and / or of the cell. The multiple TRPs may include a first TRP and a second TRP. The first TRP may transmit (e.g., transmit) downlink transmissions and / or signals (e.g., PDSCH, PDCCH, DCI) via a first core set pool. Transmitting downlink transmissions and / or signals (e.g., PDCCH, DCI) via the first core set pool may include the first TRP transmitting downlink transmissions and / or signals via a first core set having and / or associated with a first core set pool index. The first TRP may not transmit (e.g., transmit) downlink transmissions and / or signals (e.g., PDSCH, PDCCH, DCI) over the second core set pool. Not transmitting downlink transmissions and / or signals (e.g., PDSCH, PDCCH, DCI) over the second core set pool may include the first TRP not transmitting (e.g., transmit) downlink transmissions and / or signals over the second core set 1858 that has and / or is associated with the second core set pool index.

[0200] The second TRP may transmit (e.g., transmit) downlink transmissions and / or signals (e.g., PDSCH, PDCCH, DCI) via the second core set pool. Transmitting downlink transmissions and / or signals (e.g., PDCCH, DCI) via the second core set pool may include the second TRP transmitting (e.g., transmit) downlink transmissions and / or signals via a second core set 1858 having and / or being associated with the second core set pool index. The second TRP may not transmit (e.g., transmit) downlink transmissions and / or signals (e.g., PDCCH, DCI) via the first core set pool. Not transmitting downlink transmissions and / or signals (e.g., PDCCH, DCI) via the first core set pool may include the second TRP not transmitting (e.g., transmit) downlink transmissions and / or signals via a first core set having and / or being associated with the first core set pool index.

[0201] The one or more configuration parameters may indicate multiple uplink resources (e.g., PUCCH-resources, SRS-resources, etc.). The one or more configuration parameters may indicate multiple uplink resources of an uplink BWP of a cell (e.g., an active uplink BWP). An uplink BWP (e.g., an active uplink BWP) may include multiple uplink resources. An uplink BWP (e.g., an active uplink BWP) of an uplink carrier of a cell (e.g., NUL, SUL) may include multiple uplink resources. The multiple uplink resources may include, for example, multiple PUCCH resources. The multiple uplink resources may include, for example, multiple SRS resources. The multiple uplink resources may include, for example, multiple PUSCH resources.

[0202] The one or more configuration parameters may indicate one or more uplink resource sets and / or groups (e.g., PUCCH-ResourceGroup, SRS-ResourceSet). The one or more uplink resource sets and / or groups may include multiple uplink resources. Each uplink resource set and / or group of the one or more uplink resource sets and / or groups may include a respective uplink resource of the multiple uplink resources. A first uplink resource set and / or group of one or more uplink resource sets and / or groups may include one or more first uplink resources of the multiple uplink resources. A second uplink resource set and / or group of one or more uplink resource sets and / or groups may include one or more second uplink resources of the multiple uplink resources. The first uplink resource set and / or group and the second uplink resource set and / or group may not include (e.g., may not share) common (e.g., shared, identical, etc.) uplink resources of the multiple uplink resources. A first uplink resource that may be in a first uplink resource set and / or group may not be in a second uplink resource set and / or group.

[0203] The one or more configuration parameters may indicate multiple uplink resource indices, identifiers, and / or indicators for the multiple uplink resources (e.g., provided by higher layer parameters PUCCH-ResourceId, SRS-ResourceId). Each uplink resource of the multiple uplink resources is identified and / or indicated by a respective uplink resource index of the multiple uplink resource indexes. A first uplink resource of the multiple uplink resources is identified by a first uplink resource index of the multiple uplink resource indexes. A second uplink resource of the multiple uplink resources is identified by a second uplink resource index of the multiple uplink resource indexes.

[0204] The one or more configuration parameters may indicate one or more uplink resource set and / or group indices, identifiers, and / or indicators for one or more uplink resource sets and / or groups (e.g., provided by higher layer parameters PUCCH-ResourceGroupId, SRS-ResourceSetId). Each uplink resource set and / or group of one or more uplink resource sets and / or groups may be identified and / or indicated by a respective uplink resource set and / or group index of one or more uplink resource set and / or group indexes. A first uplink resource set and / or group of one or more uplink resource sets and / or groups may be identified by a first uplink resource set and / or group index of one or more uplink resource set and / or group indexes. A second uplink resource set and / or group of one or more uplink resource sets and / or groups may be identified by a second uplink resource set and / or group index of one or more uplink resource set and / or group indexes.

[0205] The one or more configuration parameters may indicate one or more core set pool indexes (e.g., provided by the higher layer parameter CoresetPoolIndex) for the plurality of uplink resources. Each uplink resource of the plurality of uplink resources may include, be configured by, and / or be indicated by a respective core set pool index of one or more core set pool indexes (e.g., 0, 1). The one or more configuration parameters may indicate a respective core set pool index of one or more core set pool indexes for each uplink resource of the plurality of uplink resources. The one or more configuration parameters may indicate, for example, a first core set pool index (CoresetPoolIndex=0) for a first uplink resource of the plurality of uplink resources. The one or more configuration parameters may indicate, for example, a second core set pool index (CoresetPoolIndex=1) for a second uplink resource of the plurality of uplink resources. The one or more core set pool indexes may include a first core set pool index and a second core set pool index.

[0206] One or more configuration parameters may not indicate a core set pool index for one uplink resource of the plurality of uplink resources. The higher layer parameter CoresetPoolIndex may not be present in the configuration parameters for the uplink resources. The wireless device 1805 may determine a value (e.g., a default value) of the core set pool index for the uplink resource as the first core set pool index (CoresetPoolIndex=0). The wireless device may determine a value (e.g., a default value) of the core set pool index for the uplink resource as the first core set pool index, for example, based on one or more configuration parameters not indicating a core set pool index for the uplink resource. The first core set pool index (CoresetPoolIndex=0) may be the core set pool index for the uplink resource, for example, based on one or more configuration parameters not indicating a core set pool index for the uplink resource.

[0207] The one or more configuration parameters may indicate at least two core set pool indices (e.g., 0 and 1) for the higher layer parameter CORESETPoolIndex. The one or more configuration parameters may include an upper layer parameter CORESETPoolIndex having and / or configured with at least two core set pool indices. The at least two core set pool indices may include a first core set pool index (e.g., 0) for one or more first uplink resources of the plurality of uplink resources. The at least two core set pool indices may include a second core set pool index (e.g., 1) different from the first core set pool index for one or more second uplink resources of the plurality of uplink resources. The one or more first uplink resources may include one or more third uplink resources of the plurality of uplink resources without a value for the higher layer parameter CORESETPoolIndex. The one or more configuration parameters may not include the higher layer parameter CORESETPoolIndex for the one or more third uplink resources.

[0208] A cell may include multiple transmission and reception points (TRPs). The multiple TRPs may correspond to the cell and / or wireless devices within, through, and / or of the cell. At least one TRP of the multiple TRPs may correspond to the cell, through, and / or wireless devices of the cell. The multiple TRPs may include a first TRP and a second TRP.

[0209] The first TRP may receive uplink transmissions and / or signals (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) via a first uplink resource of the plurality of uplink resources having and / or associated with a first core set pool index. The first TRP may not receive uplink transmissions and / or signals (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) via a second uplink resource of the plurality of uplink resources having and / or associated with a second core set pool index.

[0210] The second TRP may receive uplink transmissions and / or signals (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) via a second uplink resource of the plurality of uplink resources having and / or being associated with the second core set pool index. The second TRP may not receive uplink transmissions and / or signals (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) via a first uplink resource of the plurality of uplink resources having and / or being associated with the first core set pool index.

[0211] The one or more configuration parameters may indicate one or more core set pool indices (e.g., provided by the higher layer parameter CoresetPoolIndex) for one or more uplink resource sets and / or groups. Each uplink resource set and / or group of one or more uplink resource sets and / or groups may include, be configured by, and / or be indicated by a respective core set pool index of one or more core set pool indices (e.g., 0, 1). The one or more configuration parameters may indicate a respective core set pool index of one or more core set pool indices for each uplink resource set and / or group of one or more uplink resource sets and / or groups. The one or more configuration parameters may indicate a first uplink resource set and / or group of one or more uplink resource sets and / or groups, e.g., a first core set pool index 1825 (CoresetPoolIndex=0). The one or more configuration parameters may indicate, for example, a second core set pool index 1845 (CoresetPoolIndex=1) for a second uplink resource set and / or group of the one or more uplink resource sets and / or groups. The one or more core set pool indexes may include a first core set pool index and a second core set pool index.

[0212] One or more configuration parameters may not indicate a core set pool index for one or more uplink resource sets and / or groups of uplink resource sets. The higher layer parameter CoresetPoolIndex may not be present in the configuration parameters of the uplink resource sets and / or groups. The wireless device 1805 may determine a value (e.g., a default value) of the core set pool index of the uplink resource set and / or group as the first core set pool index 1825 (CoresetPoolIndex=0). The wireless device may determine a value (e.g., a default value) of the core set pool index of the uplink resource set and / or group as the first core set pool index, for example, based on one or more configuration parameters not indicating a core set pool index for the uplink resource set and / or group. The first core set pool index 1825 (CoresetPoolIndex=0) may be the core set pool index of the uplink resource set and / or group, for example, based on one or more configuration parameters not indicating a core set pool index for the uplink resource set and / or group.

[0213] The one or more configuration parameters may indicate at least two core set pool indices (e.g., 0 and 1) for the higher layer parameter CORESETPoolIndex. The one or more configuration parameters may include an upper layer parameter CORESETPoolIndex having and / or configured with at least two core set pool indices. The at least two core set pool indices may include a first core set pool index (e.g., 0) for one or more first uplink resource sets and / or groups of one or more uplink resource sets and / or groups. The at least two core set pool indices may include a second core set pool index (e.g., 1) different from the first core set pool index for one or more second uplink resource sets and / or groups of one or more uplink resource sets and / or groups. One or more first uplink resource sets and / or groups may include one or more third uplink resource sets and / or groups of one or more uplink resource sets and / or groups without a value for the higher layer parameter CORESETPoolIndex. The one or more configuration parameters may not include the higher layer parameter CORESETPoolIndex for one or more third uplink resource sets and / or groups.

[0214] A cell may include multiple transmission and reception points (TRPs). The multiple TRPs may correspond to the cell and / or wireless devices within / through / of the cell. At least one TRP of the multiple TRPs may correspond to wireless devices within, through, and / or of the cell. The multiple TRPs may include a first TRP and a second TRP.

[0215] The first TRP may receive uplink transmissions and / or signals (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) via uplink resources in one or more uplink resource sets and / or a first uplink resource set and / or a group having and / or being associated with the first core set pool index. The first TRP may not receive uplink transmissions and / or signals (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) via uplink resources in one or more uplink resource sets and / or a second uplink resource set and / or a group having and / or being associated with the second core set pool index.

[0216] The second TRP may receive uplink transmissions and / or signals (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) via uplink resources in one or more uplink resource sets and / or a second uplink resource set and / or a group having and / or being associated with the second core set pool index. The second TRP may not receive uplink transmissions and / or signals (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) via uplink resources in one or more uplink resource sets and / or a first uplink resource set and / or a group having and / or being associated with the first core set pool index.

[0217] A wireless device may transmit (e.g., transmit) uplink transmissions and / or signals (e.g., PUSCH / PUCCH / SRS transmissions) via uplink resources. Multiple uplink resources may comprise an uplink resource. One or more uplink resource sets and / or groups may comprise the uplink resources.

[0218] The wireless device 1805 may receive downlink control information (DCI) 1830 that schedules, triggers, and / or indicates transmission of uplink transmissions and / or signals over a core set of the plurality of core sets. The DCI 1830 may schedule, trigger, and / or indicate transmission of uplink transmissions and / or signals over uplink resources. The DCI may indicate the uplink resources. The DCI may include a field indicating the uplink resources.

[0219] The uplink transmission and / or signal may be a PUSCH transmission (e.g., a transport block). The uplink resource may be a PUSCH resource. The DCI 1830 may schedule transmission of the PUSCH transmission. The uplink transmission and / or signal may be a PUCCH transmission (e.g., HARQ-ACK information feedback). The uplink resource may be a PUCCH resource. The DCI 1830 may schedule reception of a transport block (e.g., a PDSCH reception). The uplink transmission and / or signal may be HARQ-ACK information feedback of the transport block. The uplink transmission and / or signal may be an SRS. The uplink resource may be an SRS resource. The DCI 1830 may schedule transmission of the SRS. The SRS may be, for example, an aperiodic SRS.

[0220] A core set from which the wireless device 1805 receives DCI may be associated with a core set pool index. The one or more core set pool indices may include a core set pool index. One or more configuration parameters may indicate a core set pool index for a core set. The one or more configuration parameters may not indicate a core set pool index (CoresetPoolIndex=0 or CoresetPoolIndex=1) for a core set. The value (e.g., default value) of the core set pool index for a core set may be equal to the first core set pool index (CoresetPoolIndex=0), for example, based on one or more configuration parameters that do not indicate a core set pool index for the core set.

[0221] The uplink resources may be associated with a core set pool index based on, for example, receiving DCI that schedules, triggers, and / or indicates uplink transmission and / or signaling over the uplink resources via a core set associated with the core set pool index.

[0222] An uplink resource set and / or a group including uplink resources may be associated with a core set pool index. The uplink resource set and / or group may be associated with a core set pool index, for example, based on receiving DCI that schedules, triggers, and / or indicates uplink transmission and / or signal transmission via uplink resources in (belonging to) the uplink resource set and / or group via a core set associated with the core set pool index. The uplink resource set and / or group may include one or more uplink resources including the uplink resource. One or more uplink resources may be associated with a core set pool index, for example, based on the uplink resource set and / or group including the one or more uplink resources being associated with the core set pool index. Each uplink resource of the one or more uplink resources may be associated with a core set pool index, for example, based on the uplink resource set and / or group being associated with the core set pool index.

[0223] An uplink transmission and / or signal may be associated with a core set pool index, for example, by receiving DCI 1830 scheduling, triggering, and / or information directing transmission of an uplink transmission and / or signal via a core set associated with the core set pool index.

[0224] The one or more configuration parameters may indicate multiple TCI states 1770. The one or more configuration parameters may indicate a TCI state list (e.g., provided by a higher layer (e.g., RRC) parameter dl-OrJoint-TCIStateList) including multiple TCI states. The one or more configuration parameters 1720 may include, for example, one or more PDSCH configuration parameters indicating multiple TCI states 1770 (e.g., multiple TCI states including TCI state 1, TCI state 2, ..., and TCI state M, as described herein in FIG. 17). The one or more configuration parameters may indicate multiple TCI state indices / identifiers / identities (e.g., TCI-StateId) for the multiple TCI states. The one or more configuration parameters may indicate, for each TCI state of the multiple TCI states, a respective TCI state index of the multiple TCI state indexes. Each TCI state of the multiple TCI states 1770 may be indicated / identified by a respective TCI state index of the multiple TCI state indexes. For example, the one or more configuration parameters may indicate a first TCI state index of the plurality of TCI state indices for a first TCI state of the plurality of TCI states, and the one or more configuration parameters may indicate a second TCI state index of the plurality of TCI state indices for a second TCI state of the plurality of TCI states.

[0225] The one or more configuration parameters 1720 may indicate multiple TCI states 1770 that indicate a unified TCI state for the cell. The one or more configuration parameters 1720 may include, for example, one or more PDSCH configuration parameters for the downlink BWP of the cell. The one or more configuration parameters 1720 may indicate multiple TCI states 1770 in the downlink BWP of the cell.

[0226] The one or more configuration parameters 1720 may include, for example, one or more PDSCH configuration parameters for a second downlink BWP of the second cell. The one or more configuration parameters 1720 may indicate multiple TCI states 1770 in the second downlink BWP of the second cell. The one or more cells may include the second cell. The one or more configuration parameters may include, for a downlink BWP of the cell, a reference unified TCI state list parameter (e.g., unifiedTCI-StateRef) indicating the second downlink BWP of the second cell. The reference unified TCI state list parameter may include a BWP index (e.g., BWP-Id) that identifies (e.g., indicates) the second downlink BWP. The reference unified TCI state list parameter may include a cell index (e.g., ServCellIndex) that identifies (e.g., indicates) the second cell. The second downlink BWP of the second cell may be a reference BWP of a reference cell for the downlink BWP of the cell. The downlink BWP of the cell may be a target BWP of the target cell. The one or more PDSCH configuration parameters of the downlink BWP of the cell may be based on one or more configuration parameters including, for example, a reference unified TCI state list parameter for the downlink BWP of the cell, and may not include the higher layer (e.g., RRC) parameter dl-OrJoint-TCIStateList.

[0227] The one or more configuration parameters 1720 may include a unified TCI state type parameter (e.g., unifiedTCI-StateType, shown in FIG. 17). The one or more configuration parameters may include one or more serving cell parameters (e.g., ServingCellConfig) that include the unified TCI state type parameter. The unified TCI state type parameter may indicate the unified TCI state type of the cell.

[0228] The unified TCI state type parameter may be set to “Joint.” The wireless device 1805 may use (e.g., apply) multiple TCI states 1770 (e.g., provided and / or indicated by dl-orJoint-TCIStateList) for both the cell's uplink transmission (e.g., PUSCH / PUCCH / SRS transmission) and the cell's downlink reception (e.g., PDCCH / PDSCH / CSI-RS reception) based on, for example, one or more configuration parameters including the unified TCI state type parameter set to “Joint.”

[0229] The unified TCI state type parameter may be set to "Separate." The wireless device 1805 may use (e.g., apply) multiple TCI states (e.g., provided and / or indicated by higher layer parameter dl-orJoint-TCIStateList) for downlink reception (e.g., PDCCH / PDSCH / CSI-RS reception) of the cell based on, for example, one or more configuration parameters including the unified TCI state type parameter set to "Separate." The wireless device may not use (e.g., apply) multiple TCI states for uplink transmission (e.g., PUSCH / PUCCH / SRS transmission) of the cell based on, for example, one or more configuration parameters including the unified TCI state type parameter set to "Separate."

[0230] The one or more configuration parameters 1720 may indicate the second plurality of TCI states 1770. The one or more configuration parameters may indicate an uplink TCI state list (e.g., provided and / or indicated by higher layer parameter ul-TCIStateList) that includes the second plurality of TCI states. The one or more configuration parameters 1720 may include, for example, one or more uplink BWP configuration parameters that indicate the second plurality of TCI states 1770 (e.g., the second plurality of TCI states may be TCI state 1, TCI state 2, ..., and TCI state M, as described in FIG. 17 and herein).

[0231] The one or more configuration parameters 1720 may include, for example, one or more uplink BWP configuration parameters for the uplink BWP of the cell. The one or more configuration parameters 1720 may indicate second plurality of TCI states 1770 of the uplink BWP (broadcast workload pattern) of the cell.

[0232] The one or more configuration parameters 1720 may include, for example, one or more uplink BWP configuration parameters for a second uplink BWP of the second cell. The one or more configuration parameters 1720 may indicate a second plurality of TCI states 1770 for the second uplink BWP of the second cell. The one or more cells may include the second cell. The one or more configuration parameters 1720 may include, for the uplink BWP of the cell, a reference unified TCI state list parameter (e.g., unifiedtci-StateType) indicating the second uplink BWP of the second cell. The reference unified TCI state list parameter may include a BWP index (e.g., BWP-Id) that identifies (e.g., indicates) the second uplink BWP. The reference unified TCI state list parameter may include a cell index (e.g., ServCellIndex) that identifies (e.g., indicates) the second cell. The second uplink BWP of the second cell may be a reference BWP of a reference cell for the uplink BWP of the cell. The uplink BWP of the cell may be a target BWP of the target cell. The one or more uplink BWP configuration parameters for the uplink BWP of the cell may be based on one or more configuration parameters including, for example, a reference unified TCI state list parameter for the uplink BWP of the cell, and may not include higher layer (e.g., RRC) parameters such as ul-TCI-StateList.

[0233] The wireless device 1705 may use (e.g., apply) the second plurality of TCI states 1770 for uplink transmission (e.g., PUSCH / PUCCH / SRS transmission) of the cell based on, for example, one or more configuration parameters including the unified TCI state type parameter set to “Separate.” The wireless device 1705 may not use (e.g., apply) the second plurality of TCI states 1770 for downlink reception (e.g., PDCCH / PDSCH / CSI-RS reception) of the cell based on, for example, one or more configuration parameters including the unified TCI state type parameter set to “Separate.”

[0234] The wireless device 1705 may use multiple TCI states 1770 for downlink reception via the cell's downlink BWP, for example, based on one or more configuration parameters 1720 indicating multiple TCI states 1770 for the cell's downlink BWP.

[0235] The wireless device 1705 may use multiple TCI states 1770 for uplink transmission and reception via the cell's uplink BWP, for example, based on one or more configuration parameters 1720 indicating multiple TCI states 1770 for the cell's downlink BWP.

[0236] The wireless device 1705 may use multiple TCI states 1770 of the second downlink BWP of the second cell for downlink reception via the cell's downlink BWP, e.g., based on a reference unified TCI state list parameter indicating the second downlink BWP of the second cell for the cell's downlink BWP. The wireless device 1705 may use multiple TCI states 1770 of the second downlink BWP of the second cell for uplink transmission reception via the cell's uplink BWP, e.g., based on a reference unified TCI state list parameter indicating the second downlink BWP of the second cell for the cell's downlink BWP.

[0237] The wireless device 1705 may use the second plurality of TCI states 1770 for uplink transmissions and receptions via the cell's uplink BWP, e.g., based on one or more configuration parameters 1720 indicating the second plurality of TCI states 1770 for the cell's uplink BWP. The wireless device 1705 may use the second plurality of TCI states 1770 of the second uplink BWP of the second cell for uplink transmissions and receptions via the cell's uplink BWP, e.g., based on a reference unified TCI state list parameter indicating the second uplink BWP of the second cell, for the cell's uplink BWP.

[0238] The one or more configuration parameters 1720 may indicate a physical cell identifier (PCI) for the cell. The one or more configuration parameters 1720 may indicate one or more PCIs for the one or more cells. The one or more PCIs may include the PCI of the cell. The one or more configuration parameters 1720 may include an upper layer (e.g., RRC) parameter physCellId indicating one or more PCIs for the one or more cells. The one or more configuration parameters may indicate a respective PCI of the one or more PCIs for each cell of the one or more cells. The one or more configuration parameters may include an upper layer (e.g., RRC) parameter physCellId indicating one PCI of the one or more PCIs corresponding to each of the one or more cells. The one or more configuration parameters may indicate a first PCI of the one or more PCIs for a first cell of the one or more cells. The first PCI may identify a physical cell identity of the first cell. The one or more configuration parameters may indicate a second PCI of the one or more PCIs for a second cell of the one or more cells. The second PCI may identify the physical cell identity of the second cell.

[0239] The one or more configuration parameters may indicate a list of PCI sets (e.g., as indicated by the RRC parameter additionalPCI-ToAddModList shown herein in FIG. 17). The one or more configuration parameters may include one or more serving cell parameters (e.g., ServingCellConfig as described herein in FIG. 17) that indicate a list of PCI sets. The one or more serving cell parameters may include MIMO parameters (e.g., MIMOParam as described herein in FIG. 17) that include and / or indicate a list of PCI sets. The list of PCI sets may include at least one PCI set (e.g., as indicated and / or provided by the higher layer parameter SSB-MTC-AdditionalPCI shown herein in FIG. 17). The list of PCI sets may be associated with an SSB that has a PCI different from the cell's PCI.

[0240] The list of PCI sets may include and / or indicate at least one PCI (e.g., additionalPCI or PhysCellId described herein in FIG. 17) of one or more PCIs. Each PCI set (e.g., SSB-MTC-AdditionalPCI) in the list of PCI sets may include and / or indicate a respective PCI of the at least one PCI. One or more configuration parameters may indicate a respective PCI of the at least one PCI for each PCI set in the list of PCI sets. The at least one PCI may not include the PCI of the cell. Each PCI of the at least one PCI may be different from the PCI of the cell. The one or more PCIs may include at least one PCI and a PCI of the cell. The at least one PCI may indicate (e.g., identify, etc.) at least one cell of the one or more cells. Each PCI of the at least one PCI may indicate (e.g., identify, etc.) a respective cell of the at least one cell. The first PCI set in the list of PCI sets may include the first PCI of the at least one PCI. The first PCI may indicate (e.g., identify, etc.) a first PCI of the at least one cell. The second PCI set of the list of PCI sets may include a second PCI of the at least one PCI. The second PCI may indicate (e.g., identify, etc.) a second PCI of the at least one cell. The at least one cell may not include a cell. Each cell of the at least one cell may be different from the cell. The one or more cells may include at least one cell and a cell.

[0241] The at least one cell may include, for example, at least one non-serving cell, the at least one cell may include, for example, at least one neighboring cell, and the at least one cell may include, for example, at least one candidate and / or supporting cell.

[0242] The maximum size and / or length of the list of PCI sets (e.g., maxNrof AdditionalPCI) may be equal to a value (e.g., 7). The maximum number of PCI sets in the list of PCI sets may be equal to a value (e.g., 7).

[0243] The list of at least one PCI set may include and / or indicate at least one additional PCI index (e.g., additionalPCIIndex in FIG. 17 ). Each PCI set in the list of PCI sets (e.g., SSB-MTC-AddPCI) may include and / or indicate a respective additional PCI index of the at least one additional PCI index. One or more configuration parameters may indicate at least one additional PCI index for the list of PCI sets. The one or more configuration parameters may indicate a respective additional PCI index of the at least one additional PCI index for each PCI set in the list of PCI sets. Each PCI set in the list of PCI sets may be identified and / or indicated by a respective additional PCI index of the at least one additional PCI index. A first PCI set in the list of PCI sets may be identified and / or indicated by a first additional PCI index of the at least one additional PCI index. A second PCI set in the list of PCI sets may be identified and / or indicated by a second additional PCI index of the at least one additional PCI index.

[0244] The one or more configuration parameters may indicate, for example, a list of PCI sets for inter-cell beam management. The one or more configuration parameters may indicate, for example, a list of PCI sets for inter-cell multi-TRP operation / mode.

[0245] The list of PCI sets may, for example, be equal to [{1, PCI5}, {2, PCI2}, {3, PCI4}, {4, PCI10}, {5, PCI21}]. The PCIs of a cell may be different from PCI5, PCI2, PCI4, PCI10, and PCI21. The following conditions may apply: {PCI1, PCI5) may be the first PCI set in the list of PCI sets. '1' may be the first additional PCI index of the first PCI set. PCI5 may indicate and identify a first cell and / or be the first PCI of the first cell. {2, PCI2) may be a second PCI set in the list of PCI sets. '2' may be a second additional PCI index in the second PCI set. Indicates, identifies, and / or indicates, identifies the second PCI of the second cell, and / or PCI2 of the second cell. {PCI3, PCI4) may be a third PCI set in the list of PCI sets. '3' may be a third additional PCI index in the third PCI set. PCI4 may indicate and identify a third cell and / or be the third PCI of the third cell. {4, PCI10) may be a fourth PCI set in a list of PCI sets. '4' may be a fourth additional PCI index in the fourth PCI set. PCI10 may indicate, identify, and / or be the fourth PCI. {5, PCI21) may be a fifth PCI set in a list of PCI sets. The '5' may be a fifth additional PCI index of the fifth PCI set. PCI21 may indicate and identify a fifth cell and / or may be the fifth PCI of the fifth cell. o The at least one additional PCI index may include a first additional PCI index (1), a second additional PCI index (2), a third additional PCI index (3), a fourth additional PCI index (4), and a fifth additional PCI index (5). o The at least one PCI may include PCI5, PCI2, PCI4, PCI10, and / or PCI21. The at least one cell may include a first cell, a second cell, a third cell, a fourth cell, and / or a fifth cell. o The one or more cells may include at least one cell and a cell.

[0246] The at least one additional PCI index may include a first additional PCI index (1), a second additional PCI index (2), a third additional PCI index (3), a fourth additional PCI index (4), and a fifth additional PCI index (5). The at least one PCI may include PCI5, PCI2, PCI4, PCI10, and / or PCI21. The at least one cell may include a first cell, a second cell, a third cell, a fourth cell, and / or a fifth cell. The one or more cells may include at least one of cell and cell.

[0247] The one or more configuration parameters may indicate at least one additional PCI index for one or more TCI states of the plurality of TCI states and / or the second plurality of TCI states. The one or more configuration parameters may indicate a respective additional PCI index (e.g., additionalPCI, AdditionalPCIIndex) of the at least one additional PCI index for each TCI state of the one or more TCI states. The one or more configuration parameters may indicate a first additional PCI index (e.g., 1) of the at least one additional PCI index for a first TCI state of the one or more TCI states. The first additional PCI index may indicate (e.g., identify) a first PCI set of the list of PCI sets. The one or more configuration parameters may indicate a second additional PCI index (e.g., 2) of the at least one additional PCI index for a second TCI state of the one or more TCI states. The second additional PCI index may indicate (e.g., identify) a second PCI set of the list of PCI sets. The one or more configuration parameters may indicate, for a third TCI state of the one or more TCI states, a third additional PCI index (e.g., 3) of the at least one additional PCI index. The third additional PCI index may indicate (e.g., identify) a third PCI set of the list of PCI sets.

[0248] The TCI states of one or more TCI states may be associated with an additional PCI index of at least one additional PCI index, e.g., based on one or more configuration parameters indicating the additional PCI index for the TCI state. The TCI state may include the additional PCI index. The additional PCI index may indicate (e.g., identify) a PCI set of the list of at least one PCI set. The PCI set may include and / or indicate a second PCI of the at least one PCI. The second PCI may indicate (e.g., identify) a second cell of the at least one cell. The TCI state may be associated with a second PCI and / or a second cell, e.g., based on one or more configuration parameters indicating the second PCI and / or the additional PCI index indicating the second cell for the TCI state. The second PCI of the second cell may be different from the PCI of the cell, for example.

[0249] The one or more configuration parameters 1720 may not indicate an additional PCI index of at least one additional PCI index for one or more TCI states of the plurality of TCI states 1770. The additional PCI index may be absent (e.g., not present) in the configuration parameters for the one or more TCI states. The one or more configuration parameters 1720 may include a configuration parameter for one or more TCI states. One or more TCI states of the plurality of TCI states may not be associated with an additional PCI index. One or more TCI states may not include an additional PCI index. Each TCI state of the one or more TCI states may not include an additional PCI index. One or more TCI states may be associated with a cell and / or a PCI of a cell based, for example, on the one or more configuration parameters not indicating an additional PCI index for one or more TCI states of the plurality of TCI states. One or more TCI states may be associated with a cell and / or a PCI of a cell based, for example, on the one or more configuration parameters not indicating an additional PCI index for each TCI state of the one or more TCI states. The one or more TCI states may be associated with a cell and / or a PCI of the cell based on, for example, one or more configuration parameters indicating, for each TCI state of the one or more TCI states, no additional PCI index of at least one additional PCI index.

[0250] The wireless device 1705 may receive a control command 1730 (e.g., MAC-CE, DCI, downlink control command / message, control command / message, unified TCI state activate / stop MAC CE, activate command, at time T1 as described herein in FIG. 17). The control command 1730 may indicate activation of a subset 1780a of the TCI states of a plurality of TCI states (e.g., DLorJoint-TCIStateList). The control command may indicate activation of a subset of the TCI states 1780 of a second plurality of TCI states (e.g., ul-TCI-StateList).

[0251] The wireless device may map the subset of TCI states 1780a to one or more TCI code points 1780b. The wireless device may map each TCI state of the subset of TCI states 1780a to a respective TCI code point of the one or more TCI code points 1780b. The one or more TCI code points 1780b may indicate and / or include a TCI state of the subset of TCI states 1780a. Each TCI code point of the one or more TCI code points 1780b may indicate and / or be mapped to a respective TCI state of the subset of TCI states 1780a. Each TCI code point of the one or more TCI code points 1780b may indicate, include, and / or be mapped to one or more TCI states.

[0252] 17, for example, the subset 1780a of TCI states may be TCI state 4, TCI state 5, TCI state 8, TCI state 26, TCI state 61, and TCI state 42. The one or more TCI codepoints 1780b may include a first TCI codepoint (e.g., TCI codepoint 000), a second TCI codepoint (e.g., TCI codepoint 001), a third TCI codepoint (e.g., TCI codepoint 110), and a fourth TCI codepoint (e.g., TCI codepoint 111). The first TCI codepoint (e.g., TCI codepoint 000) may include and / or indicate TCI state 4. The second TCI codepoint (e.g., TCI codepoint 001) may include and / or indicate TCI state 5 and TCI state 8. The third TCI codepoint (e.g., TCI codepoint 110) may include and / or indicate TCI state 26 and TCI state 61. The fourth TCI codepoint (e.g., TCI codepoint 111) may include and / or indicate TCI state 42. The first TCI codepoint (e.g., TCI codepoint 000) and the fourth TCI codepoint (e.g., TCI codepoint 111) indicate a single TCI state. The second TCI codepoint (e.g., TCI codepoint 001) and the third TCI codepoint (e.g., TCI codepoint 110) indicate two TCI states (e.g., two joint TCI states, two uplink TCI states, two downlink TCI states, etc.).

[0253] The number of one or more TCI code points 1780b may be equal to one. The one or more TCI code points 1780b may be a single TCI code point. The single TCI code point may indicate, include, and / or map to at least two TCI states among the plurality of TCI states 1770. The subset 1780a of TCI states may be at least two TCI states. The wireless device 1705 may not receive a DCI 1740 indicating activation of one or more TCI states among the subset 1780a of TCI states, for example, based on the number of one or more TCI code points 1780b being equal to one. The control command 1730 may indicate activation of at least two TCI states. The wireless device 1705 may not receive a DCI 1740 indicating activation of one or more TCI states among the subset 1780a of TCI states, for example, based on the control command 1730 indicating activation of at least two TCI states. The at least two TCI states may include a first TCI state (e.g., TCI state 26 described herein in FIG. 17) and a second TCI state (e.g., TCI state 61 shown herein in FIG. 17).

[0254] The number of the one or more TCI code points 1780b may exceed one. The wireless device 1705 may receive the DCI 1740 (e.g., a DCI at time T2 as shown in FIG. 17). The DCI 1740 may include a TCI field 1745. The TCI field 1745 may indicate one of the one or more TCI code points 1780b. The value of the TCI field 1745 (e.g., TCI field=110 as described herein in FIG. 17) may indicate and / or be equal to a TCI code point.

[0255] A TCI code point may include, indicate, and / or be mapped to at least two TCI states (e.g., TCI state 26 and TCI state 61 shown herein in FIG. 17). A subset 1780a of TCI states may include at least two TCI states of a TCI code point. A DCI 1740 may indicate activation of at least two TCI states. The at least two TCI states may include a first TCI state (e.g., TCI state 26 shown herein in FIG. 17) and a second TCI state (e.g., TCI state 61 shown herein in FIG. 17).

[0256] 18 shows an example of TCI state activation. The wireless device 1805 may receive a first control command 1820 (e.g., MAC-CE, DCI, Downlink Control Command / Message, Control Command / Message, Unified TCI State Activate / Deactivate MAC CE, Activation Command 1, at time T1 as described herein, such as in FIG. 18). The first control command 1820 may activate, select, display, update, and / or indicate activation of a first subset of TCI states 1870a of the plurality of TCI states 1770 (e.g., DLorJoint-TCIStateList). The first control command 1820 may activate, select, display, update, and / or indicate activation of a first subset of TCI states 1870a of the second plurality of TCI states 1770 (e.g., UL-TCIStateList).

[0257] The first control command 1820 may include a field (e.g., CoresetPoolID) having a first core set pool index 1825 (e.g., core set pool index 0). The value in the field may be equal to the first core set pool index 1825. The first core set pool index 1825 may be equal to zero, for example. A first subset of TCI states 1870a may be associated with the first core set pool index 1825. The first subset of TCI states 1870a may be associated with the first core set pool index 1825, for example, based on the first control command 1820 indicating activation of the first subset of TCI states 1870a, which includes a field having the first core set pool index 1825. The wireless device may activate the first subset of TCI states 1870a for the first core set pool index 1825.

[0258] The wireless device 1805 may map the first subset of TCI states 1870a to one or more first TCI code points 1870b. The wireless device 1805 may map each TCI state of the first subset of TCI states 1870a to a respective TCI code point of the one or more first TCI code points 1870b. The one or more first TCI code points 1870b may indicate and / or include a TCI state of the first subset of TCI states 1870a. Each TCI code point of the one or more first TCI code points 1870b may include, indicate, and / or be mapped to a respective TCI state of the first subset of TCI states 1870a. Each TCI code point of the one or more first TCI code points 1870b may include, indicate, and / or be mapped to one or more TCI states. The one or more first TCI code points 1870b may be associated with a first core set pool index 1825.

[0259] 18 , for example, the first subset of TCI states 1870a may include TCI state 4, TCI state 5, TCI state 26, and / or TCI state 42. One or more first TCI codepoints 1870b may include a first TCI codepoint (e.g., TCI codepoint 000), a second TCI codepoint (e.g., TCI codepoint 001), a third TCI codepoint (e.g., TCI codepoint 110), and a fourth TCI codepoint (e.g., TCI codepoint 111). The first TCI codepoint (e.g., TCI codepoint 000) may include and / or indicate TCI state 4. The second TCI codepoint (e.g., TCI codepoint 001) may include and / or indicate TCI state 5. The third TCI codepoint (e.g., TCI codepoint 110) may include and / or indicate TCI state 26. The fourth TCI codepoint (e.g., TCI codepoint 111) may include and / or indicate a TCI state 42. The first TCI codepoint (e.g., TCI codepoint 000), the second TCI codepoint (e.g., TCI codepoint 001), the third TCI codepoint (e.g., TCI codepoint 110), and the fourth TCI codepoint (e.g., TCI codepoint 111) indicate a single TCI state (e.g., a single joint TCI state, a single uplink TCI state, a single downlink TCI state, etc.).

[0260] The number of the one or more first TCI code points 1870b may be equal to 1. The one or more first TCI code points 1870b may include a single TCI code point. The single TCI code point may indicate a first TCI state of the multiple TCI states. The first subset of TCI states 1870a may be the first TCI state. The wireless device may not receive a DCI indicating activation of one or more TCI states of the first subset of TCI states 1870a, for example, based on the number of the one or more first TCI code points 1870b being equal to 1. The wireless device 1805 may not receive a DCI indicating activation of one or more TCI states of the first subset of TCI states 1870a, for example, based on the first control command 1820 indicating activation of the first TCI state.

[0261] The number of the one or more first TCI code points 1870b may be greater than 1. The wireless device 1805 may receive the first DCI 1830 (e.g., DCI1 at time T2 in FIG. 18 ) via a first core set 1838 (e.g., core set 1 in FIG. 18 ) having a first core set 1838 pool index 1825 (e.g., core set pool index 0). The multiple core sets may include the first core set 1838. The one or more configuration parameters may indicate the first core set pool index 1825 for the first core set 1838. The one or more configuration parameters may not indicate a core set pool index for the first core set 1838. The first core set 1838 may be associated with the first core set pool index 1825 (e.g., core set pool index 0) based on, for example, the one or more configuration parameters not indicating a core set pool index for the first core set 1838. The default value of the core set pool index for the first core set 1838 may be equal to the first core set pool index 1825 (e.g., core set pool index 0), for example, based on one or more configuration parameters not indicating a core set pool index for the first core set 1838.

[0262] The first DCI 1830 (e.g., DCI1 described herein in FIG. 18) may be, for example, DCI format 1_1. The first DCI 1830 may be, for example, DCI format 1_2. The first DCI 1830 may be, for example, DCI format 1_x (x=0, 1, 2, ...). The first DCI 1830 may be, for example, DCI format 0_x (x=0, 1, 2, ...).

[0263] The first DCI 1830 may include a first TCI field 1835. The first TCI field 1835 may indicate a first TCI codepoint within one or more first TCI codepoints 1870b. The first TCI field 1835 may indicate a first TCI codepoint of one or more first TCI codepoints 1870b associated with the first core set pool index 1825, for example, based on receiving the first DCI 1830 via a first core set 1838 having a first core set pool index 1825. The value of the first TCI field 1835 (e.g., 110 in FIG. 18 ) may be equal to the first TCI codepoint, for example. The value of the first TCI field 1835 may indicate the first TCI codepoint, for example. The first TCI codepoint (e.g., 110) may indicate, include, and / or be mapped to a first TCI state (e.g., TCI state 26 in FIG. 18 ). The first subset of TCI states 1870a may include a first TCI state. The first DCI 1830 may activate and / or indicate activation of the first TCI state. The first DCI 1830 may indicate activation of the first TCI state. The first TCI field 1835 in the first DCI 1830 may indicate the first TCI state in the first subset of TCI states 1870a, for example, based on receiving the first DCI 1830 with a first core set pool index 1825 via the first core set 1838. The first TCI field 1835 in the first DCI 1830 may indicate the first TCI state in the first subset of TCI states 1870a based on a first control command 1820 indicating activation of the first subset of TCI states 1870a, for example, including a field having a first core set pool index 1825, which may be identical to the index of the first core set 1838.

[0264] A first TCI state may be associated with and / or activated by a first core set pool index 1825. The first TCI state may be associated with downlink and / or uplink reception and / or transmission associated with the first core set pool index 1825. The first TCI state may be associated with downlink and / or uplink reception and / or transmission associated with the first core set pool index 1825, for example, based on receiving a first DCI 1830 indicating activation of the first TCI state via a first core set 1838 having the first core set pool index 1825.

[0265] The wireless device may apply a first TCI state to downlink reception (e.g., PDSCH reception, transport block, PDCCH reception, CSI-RS, DM-RS, etc.) associated with a first core set pool index 1825. For example, one or more configuration parameters may indicate the first core set pool index 1825 for a core set of the multiple core sets. The wireless device may monitor a downlink control channel in the core set based on the first TCI state, e.g., based on (e.g., in response to) the one or more configuration parameters indicating the first core set pool index 1825 for the core set. For example, the wireless device may receive DCI scheduling a downlink signal (e.g., PDSCH transmission, transport block, DM-RS, CSI-RS, aperiodic CSI-RS, etc.) via a core set having the first core set pool index 1825. The multiple core sets may include the core set. A downlink signal may be associated with the first core set pool index 1825, e.g., based on receiving DCI via the core set having the first core set pool index 1825. The wireless device may receive the downlink signal based on the first TCI state, e.g., based on (e.g., in response to) the downlink signal being associated with the first core set pool index 1825. The wireless device receives the downlink signal (e.g., PDSCH transmission, transport block, DM-RS, CSI-RS, aperiodic CSI-RS) based on (e.g., in response to) one or more configuration parameters indicating the first core set pool index 1825 for the downlink signal and / or a resource set that includes the downlink signal.

[0266] The wireless device may apply the first TCI state to an uplink transmission (eg, a PUSCH transmission, a transport block, a PUCCH transmission, an SRS, etc.) associated with the first core set pool index 1825.

[0267] The one or more configuration parameters may indicate a first core set pool index 1825 for the uplink resource and / or uplink resource set and / or group including the uplink resource. The wireless device 1805 may transmit (e.g., transmit) an uplink signal (e.g., UCI, HARQ-ACK, SR, CSI report, SRS) via the uplink resource, e.g., based on (e.g., in response to) the one or more configuration parameters indicating the first core set pool index 1825 for the uplink resource and / or uplink resource set and / or group including the uplink resource, based on the first TCI state. The uplink BWP (e.g., active uplink BWP) of the cell may include the uplink resource. The uplink resource may be, for example, a PUCCH resource. The uplink signal may be a UCI (e.g., a UCI, HARQ-ACK, SR, CSI report). The uplink resource may be, for example, an SRS resource. The uplink signal may be an SRS. The uplink resource may be, for example, a PUSCH resource. The uplink signal may be a PUSCH transmission (e.g., a transport block) of a configured uplink grant (e.g., a Type 1 configured uplink grant). The transmission of the uplink signal over the uplink resources may be associated with a first core set pool index 1825 based on, for example, one or more configuration parameters indicating the first core set pool index 1825 for the uplink resource and / or uplink resource set and / or group including the uplink resource.

[0268] The wireless device 1805 receives a DCI 1830 that triggers and / or schedules transmission of an uplink signal (e.g., a PUSCH transmission, a transport block, an SRS, an HARQ-ACK) via a core set 1838 having a first core set pool index 1825. The multiple core sets may include a core set. The uplink signal may be associated with the first core set pool index 1825, for example, based on receiving the DCI 1830 via the core set 1838 having the first core set pool index 1825. The wireless device may transmit (e.g., transmit) the uplink signal based on a first TCI state, for example, based on (e.g., in response to) the uplink signal being associated with the first core set pool index 1825.

[0269] The wireless device 1805 may receive a second control command 1840 (e.g., MAC-CE, DCI, Downlink Control Command / Message, Control Command / Message, Unified TCI State Activate / Deactivate MAC CE, Activation Command 2, at time T3 as described herein, such as in FIG. 18). The second control command 1840 may activate, select, display, update, and / or indicate activation of a second subset of TCI states 1880a of a plurality of TCI states (e.g., DLorJoint-TCIStateList). The second control command 1840 may activate, select, display, update, and / or indicate activation of a second subset of TCI states 1880a of a second plurality of TCI states (e.g., UL-TCIStateList).

[0270] The second control command 1840 may include a field (e.g., CoresetPoolID) having a second core set pool index 1845 (e.g., core set pool index 1 in FIG. 18 ). The value in the field may be equal to the second core set pool index 1845. The second core set pool index 1845 may be equal to 1, for example. A second subset of the subset 1880a of TCI states may be associated with the second core set pool index 1845. The second subset of the subset 1880a of TCI states may be associated with the second core set pool index 1845, for example, based on the second control command 1840 indicating activation of the second subset 1880a of TCI states, the second subset 1880a including a field having the second core set pool index 1845. The wireless device may activate the second subset of TCI states 1880a for the second core set pool index 1845.

[0271] The wireless device 1805 maps the second subset of TCI states 1880a to one or more second TCI code points 1880b. The wireless device 1805 may map each TCI state of the second subset of TCI states 1880a to a respective TCI code point of the one or more second TCI code points 1880b. The one or more second TCI code points 1880b may indicate, include, and / or be mapped to the second subset of TCI states 1880a. Each TCI code point of the one or more second TCI code points 1880b may include, indicate, and / or be mapped to a respective TCI state of the second subset of TCI states 1880a. Each TCI code point of the one or more second TCI code points 1880b may include, indicate, and / or be mapped to one or more TCI states. The one or more second TCI code points 1880b may be associated with a second core set pool index 1845.

[0272] 18 , for example, the second subset of TCI states 1880a may be TCI state 8, TCI state 61, and TCI state 21. The one or more second TCI codepoints 1880b may include a first TCI codepoint (e.g., TCI codepoint 000), a second TCI codepoint (e.g., TCI codepoint 001), and a third TCI codepoint (e.g., TCI codepoint 110). The first TCI codepoint (e.g., TCI codepoint 000) may include and / or indicate TCI state 8. The second TCI codepoint (e.g., TCI codepoint 001) may include and / or indicate TCI state 61. The third TCI codepoint (e.g., TCI codepoint 110) may include and / or indicate TCI state 21. The first TCI code point (e.g., TCI code point 000), the second TCI code point (e.g., TCI code point 001), and the third TCI code point (e.g., TCI code point 110) may include and / or indicate a single TCI state (e.g., a single joint TCI state, a single uplink TCI state, a single downlink TCI state, etc.).

[0273] The number of the one or more second TCI code points 1880b may be equal to 1. The one or more second TCI code points 1880b may include a single TCI code point. The single TCI code point may indicate a second TCI state of the multiple TCI states. The second subset of TCI states 1880a may be the second TCI state. The wireless device 1805 may not receive a DCI 1850 indicating activation of one or more TCI states of the second subset 1880a of TCI states, for example, based on the number of the one or more second TCI code points 1880b being equal to 1. The wireless device 1805 may not receive a DCI 1850 indicating activation of one or more TCI states of the second subset 1880a of TCI states, for example, based on the second control command 1840 indicating activation of the second TCI state.

[0274] The number of the one or more second TCI code points 1880b may be greater than 1. The wireless device 1805 may receive the second DCI 1850 (e.g., DCI2 at time T4 in FIG. 18) over a second core set 1858 (e.g., core set 2 in FIG. 18) having a second core set 1858 pool index 1845 (e.g., core set pool index 1). The one or more configuration parameters may indicate the second core set pool index 1845 for the second core set 1858. The multiple core sets may include the second core set 1858.

[0275] The second DCI 1850 may be, for example, DCI format 1_1. The second DCI 1850 may be, for example, DCI format 1_2. The second DCI 1850 may be, for example, DCI format 1_x (x = 0, 1, 2, ...). The second DCI 1850 may be, for example, DCI format 0_x (x = 0, 1, 2, ...). The second DCI 1850 may include a second TCI field 1855. The second TCI field 1855 may indicate a second TCI codepoint within one or more second TCI codepoints 1880b. The second TCI field 1855 may indicate a second TCI codepoint of one or more second TCI codepoints 1880b associated with the second core set pool index 1845, for example, based on receiving the second DCI 1850 via a second core set 1858 having a second core set pool index 1845. The value of the second TCI field 1855 (e.g., 001 in FIG. 18 ) may be equal to, for example, a second TCI codepoint. The value of the second TCI field 1855 may indicate, for example, a second TCI codepoint. The second TCI codepoint (e.g., 001) may indicate, include, and / or be mapped to a second TCI state (e.g., TCI state 61 in FIG. 18 ). The second subset of TCI states 1880 a may include the second TCI state. The second DCI 1850 may activate and / or indicate activation of the second TCI state. The second DCI 1850 may indicate activation of the second TCI state. The second TCI field 1855 in the second DCI 1850 may indicate a second TCI state in the second subset of TCI states 1880a, for example, based on receiving the second DCI 1850 via the second core set 1858, which has a second core set pool index 1845. The second TCI field 1855 in the second DCI 1850 may indicate a second TCI state in the second subset of TCI states 1880a, for example, based on a second control command 1840 indicating activation of the second subset of TCI states 1880a, which includes a field having the second core set pool index 1845, which may be identical to the index of the second core set 1858.

[0276] A second TCI state may be associated with and / or activated by a second core set pool index 1845. The second TCI state may be associated with downlink and / or uplink reception and / or transmission associated with the second core set pool index 1845. The second TCI state may be associated with downlink and / or uplink reception and / or transmission associated with the second core set pool index 1845, for example, based on receiving a second DCI 1850 via a second core set 1858 having the second core set pool index 1845 that indicates activation of the second TCI state.

[0277] The wireless device 1805 applies the second TCI state to downlink reception (e.g., PDSCH reception, transport block, PDCCH reception, CSI-RS, DM-RS, etc.) associated with the second core set pool index 1845. The one or more configuration parameters may indicate the second core set pool index 1845 for a group of core sets of the multiple core sets. The wireless device 1805 may monitor the downlink control channel in the core set based on the second TCI state, e.g., based on (e.g., in response to) the one or more configuration parameters indicating the second core set pool index 1845 for the core set. For example, the wireless device 1805 may receive DCI scheduling a downlink signal (e.g., PDSCH transmission, transport block, DM-RS, CSI-RS, aperiodic CSI-RS) via the core set having the second core set pool index 1845. The multiple core sets may include the core set. The downlink signal may be associated with the second core set pool index 1845, e.g., based on receiving DCI over a core set having the second core set pool index 1845. The wireless device 1805 may receive the downlink signal based on the second TCI state, e.g., based on (e.g., in response to) the downlink signal being associated with the second core set pool index 1845. The wireless device 1805 may receive the downlink signal (e.g., PDSCH transmission, transport block, DM-RS, CSI-RS, aperiodic CSI-RS) based on the second TCI state, e.g., based on (e.g., in response to) one or more configuration parameters indicating the second core set pool index 1845 for the downlink signal and / or resource set, including the downlink signal.

[0278] The wireless device 1805 may apply the second TCI state to an uplink transmission (e.g., a PUSCH transmission, a transport block, a PUCCH transmission, an SRS, etc.) associated with the second core set pool index 1845. The one or more configuration parameters may indicate the second core set pool index 1845 for an uplink resource and / or an uplink resource set and / or a group including uplink resources. The wireless device 1805 may transmit (e.g., transmit) an uplink signal (e.g., a UCI, a HARQ-ACK, an SR, a CSI report, an SRS) via the uplink resources based on (e.g., in response to) the one or more configuration parameters indicating the second core set pool index 1845 for the uplink resource and / or an uplink resource set and / or a group including uplink resources, based on the second TCI state. The uplink BWP (e.g., an active uplink BWP) of the cell may include the uplink resources. The uplink resources may be, for example, PUCCH resources. The uplink signal may be UCI (e.g., UCI, HARQ-ACK, SR, CSI report). The uplink resource may be, for example, an SRS resource. The uplink signal may be an SRS. The uplink resource may be, for example, a PUSCH resource. The uplink signal may be a PUSCH transmission (e.g., a transport block) of a configured uplink grant (e.g., a Type 1 configured uplink grant). Transmitting (e.g., sending) the uplink signal via the uplink resource may be associated with a second core set pool index 1845, for example, based on one or more configuration parameters indicating the second core set pool index 1845 for the uplink resource and / or uplink resource set and / or group including the uplink resource.

[0279] The wireless device 1805 may receive DCI triggering and / or scheduling transmission of an uplink signal (e.g., a PUSCH transmission, a transport block, an SRS, a HARQ-ACK) via a core set with a second core set pool index 1845. The multiple core sets may include a core set. The uplink signal may be associated with the second core set pool index 1845, e.g., based on receiving the DCI via the core set having the second core set pool index 1845. The wireless device may transmit (e.g., send) the uplink signal based on (e.g., in response to) the uplink signal being associated with the second core set pool index 1845 and based on a second TCI state, e.g., based on

[0280] The first TCI state may include and / or indicate a first reference signal (e.g., CSI-RS, SSB / PBCH block, DM-RS, SRS, etc.) The first TCI state may include and / or indicate a first quasi-co-location type (e.g., QCL Type A, QCL Type B, QCL Type C, QCL Type D).

[0281] The first TCI state may be associated with a PCI of the cell. The first TCI state may not include an additional PCI index of the at least one additional PCI index. The additional PCI index may not be present in the configuration parameters of the first TCI state. The one or more configuration parameters may include configuration parameters of the first TCI state. The first TCI state may be associated with a PCI of the cell based on, for example, the first TCI state not including an additional PCI index of the at least one additional PCI index. The first reference signal may be quasi-co-located with a first SS / PBCH block. The first reference signal may be the first SS / PBCH block. The first reference signal may be quasi-co-located with a first CSI-RS, which may be quasi-co-located with the first SS / PBCH block. The first SS / PBCH block may be associated with a cell. The first SS / PBCH block may be associated with a PCI of the cell. The one or more configuration parameters may indicate the first SS / PBCH block for the cell.

[0282] The first TCI state may be associated with a second PCI of the second cell. At least one cell of the one or more cells may include the second cell. At least one PCI in the list of PCI sets and / or indicated by the list of PCI sets may include the second PCI. The second PCI may indicate (e.g., identify) the second cell. The first TCI state may include an additional PCI index of at least one additional PCI index. One or more configuration parameters may indicate the additional PCI index in the first TCI state. The additional PCI index may indicate a PCI set in the list of PCI sets. The PCI set may include and / or indicate the second PCI of the second cell. The first TCI state may be associated with the second PCI of the second cell based on, for example, the first TCI state including an additional PCI index indicating the second PCI of the second cell. The first TCI state may be associated with a second PCI of the second cell based on, for example, one or more configuration parameters indicating an additional PCI index indicating the second PCI of the second cell for the first TCI state. The first reference signal may be quasi-co-located with the first SS / PBCH block. The first reference signal may be the first SS / PBCH block. The first reference signal may be quasi-co-located with a first CSI-RS that may be quasi-co-located with the first SS / PBCH block. The first SS / PBCH block may be associated with the second cell. The first SS / PBCH block may be associated with a second PCI of the second cell. The one or more configuration parameters may indicate the first SS / PBCH block for the second cell.

[0283] The second TCI state may include and / or indicate a second reference signal (e.g., CSI-RS, SSB / PBCH block, DM-RS, SRS, etc.). The second TCI state may include and / or indicate a second quasi-co-located type (e.g., QCL Type A, QCL Type B, QCL Type C, QCL Type D). The second TCI state may be associated with the PCI of the cell. The second TCI state may not include the additional PCI index of the at least one additional PCI index. The additional PCI index may not be present in the configuration parameters of the second TCI state. The one or more configuration parameters may include the configuration parameters of the second TCI state. The second TCI state may be associated with the PCI of the cell based, for example, on the fact that the second TCI state does not include the additional PCI index of the at least one additional PCI index. The second reference signal may be quasi-co-located with the second SS / PBCH block. The second reference signal may be the second SS / PBCH block. The second reference signal may be quasi-co-located with a second CSI-RS, which may be quasi-co-located with the second SS / PBCH block. The second SS / PBCH block may be associated with a cell. The second SS / PBCH block may be associated with a PCI of the cell. One or more configuration parameters may indicate the second SS / PBCH block for the cell.

[0284] The second TCI state may be associated with a second PCI of the second cell. At least one cell of the one or more cells may include the second cell. At least one PCI in the list of PCI sets and / or indicated by the list of PCI sets may include the second PCI. The second PCI may indicate (e.g., identify) the second cell. The second TCI state may include an additional PCI index of at least one additional PCI index. One or more configuration parameters may indicate the additional PCI index in the second TCI state. The additional PCI index may indicate a PCI set in the list of PCI sets. The PCI set may include and / or indicate the second PCI of the second cell. The second TCI state may be associated with the second PCI of the second cell based on, for example, the second TCI state including an additional PCI index indicating the second PCI of the second cell. The second TCI state may be associated with a second PCI of the second cell, for example, based on one or more configuration parameters indicating an additional PCI index, which may indicate the second PCI of the second cell, for the second TCI state. The second reference signal may be quasi-co-located with the second SS / PBCH block. The second reference signal may be the second SS / PBCH block. The second reference signal may be quasi-co-located with a second CSI-RS, which may be quasi-co-located with the second SS / PBCH block. The second SS / PBCH block may be associated with the second cell. The second SS / PBCH block may be associated with a second PCI of the second cell. The one or more configuration parameters may indicate the second SS / PBCH block for the second cell.

[0285] The second cell identified and / or indicated by the second PCI may be a non-serving cell, a neighboring cell, or a candidate and / or supporting cell.

[0286] One or more configuration parameters may indicate a first TCI state index (e.g., tci-StateId) for the first TCI state. One or more configuration parameters may indicate a second TCI state index for the second TCI state. The first TCI state index may be lower (e.g., smaller) than the second TCI state index. The plurality of TCI state indexes may include the first TCI state index and the second TCI state index.

[0287] A control command indicating activation of a subset of TCI states may include a plurality of fields. A first field of the plurality of fields may indicate a first TCI state. The first field may include a first TCI state index that identifies and / or indicates the first TCI state. The first field may be located in the first octet of the control command. A second field of the plurality of fields may indicate a second TCI state. The second field may include a second TCI state index that identifies and / or indicates the second TCI state. The second field may be located in the second octet of the control command. The first octet may be lower (e.g., smaller) than the second octet. The first octet may be octet 5, and the second octet may be octet 6. The first octet may be octet 1, and the second octet may be octet 2. The first octet may be octet 9, and the second octet may be octet 10. The base station may order the first TCI state index and the second TCI state index based on the order positions within the control command. Octet n of the control command may include a first TCI state index that identifies (e.g., indicates) the first TCI state, and octet m of the control command may include a second TCI state index that identifies (e.g., indicates) the second TCI state, for example, when n < m.

[0288] The control command may indicate, map, and / or activate at least two sets, lists, and / or vectors of TCI states to a TCI code point. The control command may indicate mapping, association, and / or activation of at least two sets, lists, and / or vectors of TCI states to a TCI code point. The at least two TCI states may include a first TCI state and a second TCI state. The first TCI state may be the first to occur in the set, list, and / or vector of at least two TCI states. The first TCI state may be the first (e.g., start, earliest, initial, etc.). The TCI state exists in the set, list, and / or vector containing at least two TCI states. The second TCI state may be the second to occur in the set, list, and / or vector of at least two TCI states. The second TCI state may be the last (e.g., latest, end, etc.). The TCI state exists in the set, list, and / or vector containing at least two TCI states. The first TCI state may be TCI state 5, and for example, if the set, list, and / or vector of at least two TCI states is [TCI state 5, TCI state 8], the second TCI state may be TCI state 8. For example, if the set, list, and / or vector of at least two TCI states is [TCI state 26, TCI state 61], the first TCI state may be TCI state 26 and the second TCI state may be TCI state 61.

[0289] The wireless device may apply a first TCI state to one or more first uplink channels and / or resources of the cell. Applying the first TCI state to the one or more first uplink channels / resources may include transmitting (e.g., sending) uplink signals based on the first TCI state via the one or more first uplink channels / resources. The wireless device may transmit (e.g., send) the uplink signals based on the first TCI state via the one or more first uplink channels and / or resources. The wireless device may transmit (e.g., send) each uplink signal based on the first TCI state via each uplink channel and / or resource of the one or more first uplink channels and / or resources.

[0290] The wireless device may transmit (e.g., transmit) an uplink signal having a transmit power determined based on the first TCI state via one or more first uplink channels and / or resources. The wireless device may transmit (e.g., transmit) an uplink signal having a respective transmit power determined based on the first TCI state via each uplink channel and / or resource of the one or more first uplink channels and / or resources. The wireless device may transmit (e.g., transmit) a first uplink signal having a first transmit power determined based on the first TCI state via a first uplink channel and / or resource of the one or more first uplink channels and / or resources. The wireless device may determine the first transmit power based on one or more first power control parameters (e.g., target received power, path loss compensation factor, closed-loop index, alpha, path loss reference signal, and / or the like) associated with, mapped to, indicated by, and / or included in the first TCI state. The wireless device may transmit (e.g., transmit) a second uplink signal over a second uplink channel and / or resource among the one or more first uplink channels and / or resources, the second uplink signal having a second transmit power determined based on the first TCI state. The wireless device may determine the second transmit power based on one or more first power control parameters (e.g., target received power, path loss compensation factor, closed-loop index, path loss reference signal) associated with, mapped to, indicated by, and / or included in the first TCI state.

[0291] The wireless device may transmit (e.g., transmit) an uplink signal over one or more first uplink channels and / or resources using a first spatial domain transmit filter and / or beam determined based on the first TCI state. The wireless device may transmit (e.g., transmit) a respective uplink signal over each uplink channel and / or resource of the one or more first uplink channels and / or resources using a first spatial domain transmit filter and / or beam determined based on the first TCI state. The wireless device may transmit (e.g., transmit) a first uplink signal over the first uplink channel and / or resource of the one or more first uplink channels and / or resources using a first spatial domain transmit filter and / or beam determined based on the first TCI state. At least one DMRS antenna port of the first uplink signal may be quasi-co-located with a first reference signal indicated by the first TCI state. The wireless device may transmit (e.g., transmit) a second uplink signal over one or more of the first uplink channels and / or resources using a first spatial-domain transmit filter and / or beam determined based on the first TCI state, and at least one DMRS antenna port of the second uplink signal may be quasi-co-located with a first reference signal indicated by the first TCI state.

[0292] The one or more first uplink channels and / or resources may include a PUSCH. The one or more first uplink channels and / or resources may include one or more first PUSCH resources. The one or more first uplink channels and / or resources may include one or more first PUSCH transmissions.

[0293] The wireless device 1805 may receive a first DCI 1830 scheduling a first PUSCH transmission via a first core set 1838. The multiple core sets may include the first core set 1838. The first DCI 1830 may include, for example, a field (e.g., an SRS resource set indicator field, a TRP field, a core set pool index field, an additional PCI index, a BFD set index, a unified TCI state indicator field, a joint TCI state indicator field, an uplink TCI state indicator field, a panel index, a capability set index, etc.) having a first value (e.g., 0, 00, 10, 11) indicating a first TCI state. The wireless device may transmit (e.g., transmit) a first PUSCH transmission based on the first TCI state and based on (e.g., in response to) the first DCI 1830 including a field having a first value indicating the first TCI state. One or more first uplink channels, and / or resources, may include the PUSCH transmission scheduled by the DCI including a field having the first value. Each DCI of the DCI may schedule one or more PUSCH transmissions.

[0294] The first core set 1838 may be associated with a first core set pool index 1825 (e.g., CoresetPoolIndex=0). One or more configuration parameters may indicate the first core set pool index 1825 for the first core set 1838. The one or more configuration parameters may not indicate a core set pool index for the first core set 1838. The wireless device may transmit (e.g., transmit) a first PUSCH transmission based on the first TCI state, e.g., based on (e.g., in response to) receiving a first DCI 1830 scheduling the first PUSCH transmission via the first core set 1838 having the first core set pool index 1825. One or more first uplink channels and / or resources may include the first PUSCH transmission. The one or more first uplink channels and / or resources may include a PUSCH transmission scheduled by a DCI received via one or more first core sets having the first core set pool index 1825. The multiple core sets may include one or more first core sets. The wireless device 1805 may transmit (e.g., transmit) a first PUSCH transmission at a first transmit power determined based on the first TCI state. The wireless device 1805 may transmit (e.g., transmit) the first PUSCH transmission using a first spatial-domain transmit filter / beam determined based on the first TCI state.

[0295] The one or more configuration parameters may indicate, for the configured uplink grant, a field (e.g., an SRS resource set indicator field, a TRP field, a core set pool index field, an additional PCI index, a BFD set index, a unified TCI state indicator field, a joint TCI state indicator field, an uplink TCI state indicator field, a panel index, a capability set index, etc.) where a first value (e.g., 0, 00, 10, 11) indicates a first TCI state. The wireless device may transmit (e.g., send) a PUSCH transmission of the configured uplink grant based on the first TCI state, e.g., based on (e.g., in response to) the one or more configuration parameters indicating, for the configured uplink grant, a field having a first value that indicates the first TCI state. The configured uplink grant is, for example, a Type 1 configured uplink grant. The one or more first uplink channels and / or resources may include the PUSCH transmission of the configured uplink grant.

[0296] The wireless device 1805 may transmit (e.g., transmit) a PUSCH transmission of the configured uplink grant using a first transmit power determined based on the first TCI state. The wireless device 1805 may transmit (e.g., transmit) a PUSCH transmission of the configured uplink grant using a first spatial-domain transmit filter / beam determined based on the first TCI state.

[0297] The one or more first uplink channels and / or resources may include a PUCCH. The one or more first uplink channels and / or resources may include one or more first PUCCH resources. The one or more first uplink channels and / or resources may include one or more first PUCCH resource sets and / or groups. The one or more first uplink channels and / or resources may include one or more first PUCCH transmissions.

[0298] The one or more configuration parameters may indicate, for the first PUCCH resource, a field (e.g., an SRS resource set indicator field, a TRP field, a core set pool index field, an additional PCI index, a BFD set index, a unified TCI state indicator field, a joint TCI state indicator field, an uplink TCI state indicator field, a panel index, a capability set index, etc.) having a first value indicating a first TCI state. The wireless device may transmit (e.g., transmit) an uplink signal (e.g., an SR, HARQ-ACK, a CSI report, uplink control information, a PUCCH transmission) over the first PUCCH resource based on the first TCI state, e.g., based on (e.g., in response to) the one or more configuration parameters indicating, for the first PUCCH resource, a field having a first value indicating the first TCI state. The one or more first uplink channels and / or resources may include a PUCCH transmission over the first PUCCH resource.

[0299] The wireless device may transmit (e.g., transmit) an uplink signal via a first PUCCH resource at a first transmit power determined based on the first TCI state. The wireless device may transmit (e.g., transmit) an uplink signal via the first PUCCH resource using a first spatial-domain transmit filter / beam determined based on the first TCI state.

[0300] The one or more configuration parameters may indicate, for the first PUCCH resource set and / or group, a field (e.g., an SRS resource set indicator field, a TRP field, a core set pool index field, an additional PCI index, a BFD set index, a unified TCI state indicator field, a joint TCI state indicator field, an uplink TCI state indicator field, a panel index, a capability set index, etc.) having a first value indicating a first TCI state. The wireless device may transmit (e.g., send) an uplink signal (e.g., an SR, a HARQ-ACK, a CSI report, uplink control information) over the PUCCH resources in the first PUCCH resource set and / or group based on the first TCI state, e.g., based on (e.g., in response to) the one or more configuration parameters indicating, for the first PUCCH resource set and / or group, a field having a first value indicating the first TCI state. The wireless device may transmit (e.g., send) a respective uplink signal (e.g., an SR, HARQ-ACK, CSI report, uplink control information) over each PUCCH resource in the first PUCCH resource set and / or group based on the first TCI state, e.g., based on (e.g., in response to) one or more configuration parameters indicating a field having a first value indicating the first TCI state for the first PUCCH resource set and / or group. The one or more first uplink channels and / or resources may include a PUCCH transmission over each PUCCH resource in the first PUCCH resource set and / or group.

[0301] The wireless device may transmit (e.g., transmit) an uplink signal via the PUCCH resource at a first transmit power determined based on the first TCI state. The wireless device may transmit (e.g., transmit) an uplink signal via the PUCCH resource using a first spatial-domain transmit filter / beam determined based on the first TCI state.

[0302] The wireless device may receive a first DCI 1830 triggering and / or scheduling transmission of a first PUCCH transmission (e.g., a HARQ-ACK feedback transmission) via a first core set 1838. The first DCI 1830 may schedule PDSCH reception, for example. The first DCI 1830 may indicate an SCell dormant state, for example. The first DCI 1830 may indicate an SPS PDSCH release, for example. The first DCI 1830 may indicate activation of a unified TCI state, for example. The multiple core sets may include the first core set 1838. The first DCI 1830 may include, for example, a field (e.g., an SRS resource set indicator field, a TRP field, a core set pool index field, an additional PCI index, a BFD set index, a unified TCI state indicator field, a joint TCI state indicator field, an uplink TCI state indicator field, a panel index, a capability set index, etc.) having a first value (e.g., 0, 00, 10, 11) indicating the first TCI state. The wireless device may transmit (e.g., transmit) a first PUCCH transmission based on the first TCI state, e.g., based on (e.g., in response to) the first DCI 1830 including a field having a first value indicating the first TCI state. One or more first uplink channels, and / or resources may include a PUCCH transmission triggered and / or scheduled by a DCI including a field having the first value.

[0303] The first core set 1838 may be associated with a first core set pool index 1825 (e.g., CoresetPoolIndex=0). One or more configuration parameters may indicate the first core set pool index 1825 for the first core set 1838. The one or more configuration parameters may not indicate a core set pool index for the first core set 1838. The wireless device may transmit (e.g., transmit) the first PUCCH transmission based on the first TCI state, e.g., based on (e.g., in response to) receiving a first DCI 1830 that triggers and / or schedules the first PUCCH transmission via the first core set 1838 having the first core set pool index 1825. The one or more first uplink channels and / or resources may include the PUCCH transmission triggered and / or scheduled by the DCI received via the one or more first core sets having the first core set pool index 1825. The multiple core sets may include one or more first core sets.

[0304] The wireless device 1805 may transmit (e.g., transmit) a first PUCCH transmission at a first transmit power determined based on the first TCI state. The wireless device 1805 may transmit (e.g., transmit) the first PUCCH transmission using a first spatial-domain transmit filter / beam determined based on the first TCI state.

[0305] One or more first uplink channels and / or resources may include SRS. One or more first uplink channels and / or resources may include one or more first SRS resources. One or more first uplink channels and / or resources may include one or more first SRS resource sets and / or groups. One or more first uplink channels and / or resources may include one or more first SRS transmissions.

[0306] The one or more configuration parameters may indicate, for the first SRS resource, a field (e.g., an SRS resource set indicator field, a TRP field, a core set pool index field, an additional PCI index, a BFD set index, a unified TCI state indicator field, a joint TCI state indicator field, an uplink TCI state indicator field, a panel index, a capability set index, etc.) having a first value indicating a first TCI state. The wireless device may transmit (e.g., transmit) an SRS via the first SRS resource based on the first TCI state, e.g., based on (e.g., in response to) the one or more configuration parameters indicating, for the first SRS resource, a field having a first value that may indicate the first TCI state. One or more first uplink channels and / or resources may include the SRS transmission via the first SRS resource.

[0307] The wireless device 1805 may transmit (e.g., transmit) the SRS over the first SRS resource at a first transmit power determined based on the first TCI state. The wireless device 1805 may transmit (e.g., transmit) the SRS over the first SRS resource using a first spatial domain transmit filter / beam determined based on the first TCI state.

[0308] The one or more configuration parameters may indicate, for the first SRS resource set and / or group, a field (e.g., SRS resource set indicator field, TRP field, core set pool index field, additional PCI index, BFD set index, unified TCI state indicator field, joint TCI state indicator field, uplink TCI state indicator field, panel index, capability set index, etc.) having a first value that indicates a first TCI state. The wireless device may transmit (e.g., transmit) SRS over SRS resources in the first SRS resource set and / or group based on the first TCI state, e.g., based on (e.g., in response to) the one or more configuration parameters that indicate the field having a first value that may indicate the first TCI state for the first SRS resource set and / or group. The wireless device may transmit (e.g., transmit) a respective SRS via each SRS resource in the first SRS resource set and / or group based on the first TCI state, e.g., based on (e.g., in response to) one or more configuration parameters indicating a field having a first value for the first SRS resource set and / or group that may indicate the first TCI state. The one or more first uplink channels and / or resources may include the SRS transmission via each SRS resource in the first SRS resource set and / or group.

[0309] The wireless device 1805 may transmit (e.g., transmit) the SRS over the SRS resource at a first transmit power determined based on the first TCI state. The wireless device 1805 may transmit (e.g., transmit) the SRS over the SRS resource using a first spatial domain transmit filter / beam determined based on the first TCI state.

[0310] The wireless device 1805 may receive a first DCI 1830 via a first core set 1838 that triggers and / or schedules transmission of an SRS. The SRS may be, for example, an aperiodic SRS. The SRS may be, for example, a semi-persistent SRS. The multiple core sets may include the first core set 1838. The first DCI 1830 may include, for example, a field (e.g., an SRS resource set indicator field, a TRP field, a core set pool index field, an additional PCI index, a BFD set index, a unified TCI state indicator field, a joint TCI state indicator field, an uplink TCI state indicator field, a panel index, a capability set index, etc.) having a first value (e.g., 0, 00, 10, 11) indicating a first TCI state. The wireless device 1805 may transmit (e.g., send) an SRS based on the first TCI state, e.g., based on (e.g., in response to) the first DCI 1830 that includes a field having a first value indicating the first TCI state. The one or more first uplink channels and / or resources may include an SRS transmission triggered and / or scheduled by a DCI that includes a field having a first value.

[0311] The first core set 1838 may be associated with a first core set pool index 1825 (e.g., CoresetPoolIndex=0). One or more configuration parameters may indicate the first core set pool index 1825 for the first core set 1838. The one or more configuration parameters may not indicate a core set pool index for the first core set 1838. The wireless device may transmit (e.g., transmit) the SRS based on the first TCI state, e.g., based on (e.g., in response to) receiving a first DCI 1830 that triggers and / or schedules transmission of the SRS via the first core set 1838 having the first core set pool index 1825. The one or more first uplink channels and / or resources may include the SRS transmission triggered and / or scheduled by the DCI received via the one or more first core sets having the first core set pool index 1825. The multiple core sets may include one or more first core sets.

[0312] The wireless device 1805 may transmit (e.g., transmit) the SRS at a first transmit power determined based on the first TCI state. The wireless device 1805 may transmit (e.g., transmit) the SRS using a first spatial domain transmit filter / beam determined based on the first TCI state.

[0313] The wireless device may apply (e.g., use) a first TCI state to one or more first downlink channels / resources of the cell. Applying the first TCI state to the one or more first downlink channels / resources may include receiving downlink signals based on the first TCI state via the one or more first downlink channels / resources. The wireless device may receive downlink signals based on the first TCI state via the one or more first downlink channels / resources. The wireless device may receive each downlink signal of the downlink signals based on the first TCI state via each downlink channel / resource of the one or more first downlink channels / resources.

[0314] The wireless device may receive downlink signals via one or more first downlink channels / resources using a first spatial-domain receive / receive filter / beam determined based on the first TCI state. The wireless device may receive a respective downlink signal via each downlink channel / resource of the one or more first downlink channels / resources using a first spatial-domain receive / receive filter / beam determined based on the first TCI state. For example, the wireless device may receive a first downlink signal via a first downlink channel / resource of the one or more first downlink channels / resources using a first spatial-domain receive / receive filter / beam determined based on the first TCI state. At least one DMRS antenna port of the first downlink signal may be (e.g., quasi-) co-located with a first reference signal indicated by the first TCI state. The wireless device may receive a second downlink signal via a second downlink channel / resource of the one or more first downlink channels / resources using a first spatial-domain receive / receive filter / beam determined based on the first TCI state. At least one DMRS antenna port of the second downlink signal may be (eg, quasi-) co-located with the first reference signal indicated by the first TCI state.

[0315] The one or more first downlink channels / resources may be / include PDSCH. The one or more first downlink channels / resources may be / include one or more first PDSCH resources. The one or more first downlink channels / resources may be / include one or more first PDSCH transmissions.

[0316] The wireless device may receive a first DCI scheduling a first PDSCH reception via a first core set. The multiple core sets may include the first core set. The first DCI may include, for example, a field (e.g., an SRS resource set indicator field, a TRP field, a core set pool index field, an additional PCI index, a BFD set index, a unified TCI state indicator field, a joint TCI state indicator field, an uplink TCI state indicator field, a panel index, a capability set index, etc.) having a first value (e.g., 0, 00, 10, 11) indicating a first TCI state. The wireless device may receive / perform a first PDSCH reception based on the first TCI state and based on (e.g., in response to) the first DCI including a field having a first value indicating the first TCI state. One or more first downlink channels / resources may be / include PDSCH receptions scheduled by a DCI message including a field having the first value. Each DCI message may schedule one or more PDSCH receptions of the PDSCH receptions.

[0317] The first core set may be associated with a first core set pool index (e.g., CoresetPoolIndex=0). One or more configuration parameters may indicate the first core set pool index for the first core set. For example, the one or more configuration parameters may not indicate a core set pool index for the first core set. The wireless device may receive / perform first PDSCH reception based on the first TCI state. The wireless device may receive / perform first PDSCH reception, for example, based on (e.g., in response to) receiving a first DCI scheduling the first PDSCH reception via the first core set (e.g., having a first core set pool index). The one or more first downlink channels / resources may be / include the first PDSCH reception. The one or more first downlink channels / resources may be / include PDSCH reception scheduled by DCI (e.g., a DCI message) received via one or more first core sets having the first core set pool index. The multiple core sets may include one or more first core sets.

[0318] The wireless device may receive a first PDSCH reception with a first spatial-domain receive / receive filter / beam determined based on the first TCI state, and at least one first DMRS antenna port of the first PDSCH reception may be (e.g., quasi-) co-located with a first reference signal indicated by the first TCI state.

[0319] The one or more configuration parameters may indicate a field (e.g., an SRS resource set indicator field, a TRP field, a core set pool index field, an additional PCI index, a BFD set index, a unified TCI state indicator field, a joint TCI state indicator field, an uplink TCI state indicator field, a panel index, a capability set index, etc.) having a first value indicating a first TCI state for an SPS PDSCH configuration. The wireless device may receive / perform PDSCH reception for / on an SPS PDSCH configuration based on (e.g., in response to) one or more configuration parameters indicating a field having a first value indicating a first TCI state for an SPS PDSCH configuration. The one or more first downlink channels / resources may be / include PDSCH transmission for / on an SPS PDSCH configuration.

[0320] The wireless device may receive a PDSCH reception with a first spatial-domain receive / receive filter / beam determined based on the first TCI state, and at least one first DMRS antenna port of the PDSCH reception (and / or each PDSCH reception of the PDSCH reception) may be (e.g., quasi-) co-located with a first reference signal indicated by the first TCI state.

[0321] The one or more first downlink channels / resources may be / include PDCCHs. The one or more first downlink channels / resources may be / include one or more first PDCCH resources. The one or more first downlink channels / resources may be / include one or more first PDCCH resource sets / groups. The one or more first downlink channels / resources may be / include one or more first PDCCH receptions. The one or more first downlink channels / resources may be / include one or more first core sets. The multiple core sets may include one or more first core sets.

[0322] The one or more configuration parameters may indicate, for the first core set, a field (e.g., an SRS resource set indicator field, a TRP field, a core set pool index field, an additional PCI index, a BFD set index, a unified TCI state indicator field, a joint TCI state indicator field, an uplink TCI state indicator field, a panel index, a capability set index, etc.) having a first value indicating a first TCI state. The wireless device may receive / perform downlink signals (e.g., DCI, PDCCH reception, PDCCH reception having / carrying DCI) via the first core set based on the first TCI state. The wireless device may receive / perform downlink signals via the first core set based on (e.g., in response to) the one or more configuration parameters indicating, for the first core set, a field having a first value indicating the first TCI state. The one or more first downlink channels / resources may be / include PDCCH reception via the first core set. The one or more first core sets may include the first core set.

[0323] The one or more configuration parameters may indicate, for the first core set group, a field (e.g., an SRS resource set indicator field, a TRP field, a core set pool index field, an additional PCI index, a BFD set index, a unified TCI state indicator field, a joint TCI state indicator field, an uplink TCI state indicator field, a panel index, a capability set index, etc.) having a first value indicating a first TCI state. The first core set group may include one or more first core sets of the multiple core sets. The wireless device may receive / perform downlink signals (e.g., DCI, PDCCH reception) via a first core set in the first core set group based on the first TCI state. The wireless device may receive / perform downlink signals via the first core set based on (e.g., in response to) one or more configuration parameters indicating a field having a first value indicating a first TCI state for the first core set group, for example. The wireless device may receive / perform respective downlink signals (e.g., DCI, PDCCH reception) via each core set in the first core set gro...

Claims

1. 1. A method comprising: receiving, by a wireless device, one or more configuration parameters of a cell, the one or more configuration parameters comprising: a list of aperiodic trigger state configurations for aperiodic channel state information (CSI) reporting; receiving physical downlink shared channel (PDSCH) configuration parameters including a unified transmission configuration indicator (TCI) state reference parameter indicating a reference bandwidth portion (BWP) of the reference cell; receiving downlink control information (DCI) including a CSI request field, the CSI request field indicating an aperiodic trigger state configuration in the list of aperiodic trigger state configurations, the aperiodic trigger state configuration comprising: at least one TCI state identifier indicating at least one TCI state indicated by a downlink or joint TCI state list parameter of the reference BWP of the reference cell; and a resource set parameter indicating one or more reference signals. receiving the one or more reference signals based on the at least one TCI state indicated by the at least one TCI state identifier; transmitting a CSI report indicative of one or more radio link qualities of the one or more reference signals.

2. each TCI state identifier of the at least one TCI state identifier indicates a respective TCI state of the at least one TCI state; The method of claim 1 , wherein the CSI report includes a respective radio link quality of the one or more radio link qualities for a respective reference signal of the one or more reference signals.

3. The method of claim 1 or 2, wherein said receiving said one or more reference signals comprises measuring said one or more radio link qualities of said one or more reference signals.

4. each reference signal of the one or more reference signals is received by a respective TCI state of the at least one TCI state indicated by the at least one TCI state identifier; 4. A method according to claim 1, wherein each reference signal of the one or more reference signals is quasi-co-located with a reference signal indicated by the respective TCI state of the at least one TCI state indicated by the at least one TCI state identifier.

5. the resource set parameter indicates a CSI reference signal (CSI-RS) resource set; The method according to any one of claims 1 to 4, wherein the one or more reference signals are one or more aperiodic CSI-RS.

6. the DCI is configured to trigger transmission of an aperiodic CSI report; The method of any one of claims 1 to 5, wherein the one or more reference signals are associated with the cell.

7. 7. The method of claim 1, wherein the PDSCH configuration parameters are based on the unified TCI state reference parameters being present in the PDSCH configuration parameters and do not include downlink or joint TCI state addition or modification parameters for the cell.

8. The PDSCH configuration parameters do not include a TCI status list parameter based on the PDSCH configuration parameters including a downlink or joint TCI status list parameter; The method according to any one of claims 1 to 7, wherein the downlink or joint TCI state list parameter includes the unified TCI state reference parameter.

9. The unified TCI state reference parameters are: a cell index identifying the reference cell; A BWP index that identifies the reference BWP.

10. receiving, by the wireless device, one or more second configuration parameters of the reference cell, the one or more second configuration parameters comprising: a second list of aperiodic trigger state configurations for aperiodic CSI reports associated with the reference cell; and receiving PDSCH configuration parameters of the reference cell, the PDSCH configuration parameters including the downlink or joint TCI status list parameters of the reference BWP of the reference cell; receiving a second DCI including a second CSI request field, the second CSI request field indicating a second aperiodic trigger state configuration in the second list of aperiodic trigger state configurations, the second aperiodic trigger state configuration comprising: at least one second TCI state identifier indicating at least one second TCI state indicated by the downlink or joint TCI state list parameter of the reference BWP of the reference cell; a second resource set parameter indicative of one or more second reference signals; receiving the one or more second reference signals based on the at least one second TCI state indicated by the at least one second TCI state identifier; 10. The method of claim 1, further comprising: transmitting a second CSI report indicative of one or more radio link qualities of the one or more second reference signals.

11. receiving, by the wireless device, one or more second configuration parameters of a second cell, the one or more second configuration parameters comprising: a second list of aperiodic trigger state configurations for aperiodic CSI reporting associated with the second cell; and receiving PDSCH configuration parameters for the second cell, the PDSCH configuration parameters including a TCI status list parameter for the second cell and not including a downlink or joint TCI status list parameter; receiving a second DCI including a second CSI request field, the second CSI request field indicating a second aperiodic trigger state configuration in the second list of aperiodic trigger state configurations, the second aperiodic trigger state configuration comprising: at least one second TCI state identifier indicating at least one second TCI state indicated by the TCI state list parameter of the second cell; a second resource set parameter indicative of one or more second reference signals; receiving the one or more second reference signals based on the at least one second TCI state indicated by the at least one second TCI state identifier; 10. The method of claim 1, further comprising: transmitting a second CSI report indicative of one or more radio link qualities of the one or more second reference signals.

12. the TCI state list parameter of the second cell includes a TCI state addition or modification parameter of the second cell; The method of claim 11 , wherein the downlink or joint TCI state list parameter of the reference BWP of the reference cell includes a downlink or joint TCI state addition or modification parameter of the reference BWP of the reference cell.

13. 1. A wireless device, comprising: one or more processors; a memory storing instructions that, when executed by said one or more processors, cause said wireless device to perform a method according to any one of claims 1 to 12.

14. A wireless device configured to perform the method of any one of claims 1 to 12; a base station configured to transmit the one or more configuration parameters.

15. A computer readable medium storing instructions that, when executed, cause a wireless device to perform the method of any one of claims 1-12.

Images