Configuring resources for duplicate submissions

Abstract

A wireless device may communicate with a base station by using overlapping transmissions. Transmissions such as a physical uplink control channel (PUCCH) transmission (e.g., including uplink control information (UCI)) may be multiplexed with repetitions of transmissions such as a physical uplink shared channel (PUSCH) transmission. Information such as channel state information (CSI) reports may be multiplexed with repetitions of transmissions such as a physical uplink shared channel (PUSCH) transmission. Rules may be applied to indicate / determine which repetitions among multiple repetitions include the multiplexed information (e.g., which PUSCH repetitions include UCI). The rules may include the multiplexed information within a transmission associated with at least one of a minimum (or maximum) frequency or range of frequencies, a minimum (or maximum) starting (or ending) resource block, a minimum (or maximum) transmission configuration indicator (TCI) state, a minimum (or maximum) TCI state index, a minimum (or maximum) panel or panel index, and / or any other parameter / indicator that may distinguish a transmission (including the multiplexed information) from other transmissions. Transmissions such as power headroom reports may be multiplexed with transmissions such as physical uplink shared channel (PUSCH) transmissions. Rules may be applied to indicate / determine values / parameters associated with the transmissions. For example, rules may be used to indicate / determine values ​​of the power headroom report that may be indicative of a path loss reference signal used to determine the power headroom report. The rules may include indicating / determining values / parameters associated with the transmissions using at least one of a minimum (or maximum) frequency or range of frequencies, a minimum (or maximum) starting (or ending) resource block, a minimum (or maximum) transmission configuration indicator (TCI) state, a minimum (or maximum) TCI state index, a minimum (or maximum) panel or panel index, and / or any other parameter / indicator that may distinguish the transmissions. Overlapping transmissions may include multiple transmissions of the same type / channel, such as physical uplink shared channel (PUSCH) transmissions, physical uplink control channel (PUCCH) transmissions, etc. Rules may be applied to indicate / determine power prioritization for overlapping transmissions. For example, rules may be used to indicate which of overlapping transmissions of the same type / channel (e.g., PUSCH, PUCCH, etc.) may be dropped or transmitted using reduced power if the overlapping transmissions would otherwise exceed a power threshold. The rules may include indicating / determining power prioritization for overlapping transmissions based on at least one of a lowest (or highest) frequency or range of frequencies, a lowest (or highest) starting (or ending) resource block, a lowest (or highest) transmission configuration indicator (TCI) state, a lowest (or highest) TCI state index, a lowest (or highest) panel or panel index, and / or any other parameter / indicator that may distinguish overlapping transmissions.

Description

[Technical Field]

[0001] (CROSS-REFERENCE TO RELATED APPLICATIONS) This application claims the benefit of U.S. Provisional Patent Application No. 63 / 307,299, filed February 7, 2022, U.S. Provisional Patent Application No. 63 / 307,301, filed February 7, 2022, U.S. Provisional Patent Application No. 63 / 308,699, filed February 10, 2022, and U.S. Provisional Patent Application No. 63 / 307,703, filed February 8, 2022. The above-referenced applications are incorporated herein by reference in their entireties. [Background technology]

[0002] Wireless communication involves repetition of transmissions to increase the likelihood of successful reception of a message. The repetitions are transmitted using time division multiplexing. 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 may communicate with a base station by using overlapping transmissions. For example, the overlapping transmissions may include using time division multiplexing (TDM), frequency division multiplexing (FDM), and / or spatial division multiplexing (SDM) for transmissions that overlap in time (e.g., using FDM and / or SDM), frequency (e.g., using TDM and / or SDM), and / or spatial domains (e.g., using TDM and / or FDM). The wireless device may use multiplexing to transmit repetitions of a message / transmission, which may increase the likelihood of successful reception. For at least some repetitions, the wireless device may multiplex information within the repeated message / transmission. The multiplexed information may include, for example, a channel state information (CSI) report multiplexed with the repetition of a physical uplink shared channel (PUSCH) transmission, a physical uplink control channel (PUCCH) transmission (e.g., including uplink control information (UCI)) multiplexed with the repetition of a PUSCH transmission, and / or any other information included in the transmission. The rules are applied by wireless devices and base stations to indicate / determine which of the multiple repetitions contain multiplexed information so that the multiplexed information can be successfully communicated. For example, the rules include a minimum (or maximum) frequency or range of frequencies, a minimum (or maximum) starting (or ending) resource block, a minimum (or maximum) transmission configuration indicator (TCI) state, a minimum (or maximum) TCI state index, a minimum (or maximum) panel or panel index, and / or any other parameters / indicators that may distinguish a transmission (containing multiplexed information) from other transmissions.Additionally or alternatively, the rules may be applied by the wireless device and base station to display / determine (e.g., using the lowest or highest frequency, lowest / starting or highest / ending resource block, lowest or highest TCI state or TCI state index, lowest or highest panel or panel index, etc.) values / parameters associated with the transmission, such as the value of the power headroom report, which may indicate the path loss reference signal used to determine the power headroom report (e.g., which may then indicate which of multiple transmission / reception points the power headroom report corresponds to). Additionally or alternatively, the rules may include power prioritization rules that may be applied by the wireless device and the base station to indicate / determine power prioritization for transmissions that overlap in time (e.g., using lowest or highest frequency, lowest / starting or highest / ending resource block, lowest or highest TCI state / TCI state index, lowest or highest panel / panel index, etc.), where the power prioritization rules may indicate which of multiple transmissions of the same type / channel (e.g., PUSCH, PUCCH, etc.) the multiple transmissions would otherwise be. The method of any one of claims 1-11, wherein establishing one or more rules for overlapping transmissions as described herein may result in benefits such as increased synchronization between the wireless device and the base station, reduced retransmissions, reduced latency, and / or reduced power consumption.

[0005] These and other features and advantages are described in more detail below.

[0006] Certain features are illustrated by way of example, and not by way of limitation, in the accompanying drawings in which like numerals refer to like elements and in which: [Brief explanation of the drawings]

[0007] [Figure 1A] FIG. 1A illustrates an embodiment of a communication network. [Figure 1B] FIG. 1B illustrates an embodiment 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 shows 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 illustrates an exemplary TCI state update. [Figure 18] FIG. 18 shows an example of an uplink repetition scheme. [Figure 19] FIG. 19 shows an example of report multiplexing. [Figure 20] FIG. 20 shows an example of report multiplexing. [Figure 21A] FIG. 21A shows an example of report multiplexing. [Figure 21B] FIG. 21B shows an example of report multiplexing. [Figure 22] FIG. 22 shows an example of uplink control information multiplexing. [Figure 23] FIG. 23 shows an example of uplink control information multiplexing. [Figure 24A] FIG. 24A shows an example of uplink control information multiplexing. [Figure 24B] FIG. 24B shows an example of uplink control information multiplexing. [Figure 25] FIG. 25 shows an example of a unified beam update. [Figure 26] FIG. 26 shows an example of a power headroom report (PHR). [Figure 27A] FIG. 27A shows an example of a PHR. [Figure 27B] FIG. 27B shows an example of a PHR. [Figure 28A] FIG. 28A shows an example of a PHR. [Figure 28B] FIG. 28B shows an example of a PHR. [Figure 29A] FIG. 29A shows an example of a PHR. [Figure 29B] FIG. 29B shows an example of a PHR. [Figure 30] FIG. 30 shows an example of power prioritization. [Figure 31] FIG. 31 shows an example of power prioritization. [Figure 32] FIG. 32 shows an example of power prioritization. [Figure 33] FIG. 33 shows an example of power prioritization. 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 description are non-exclusive, and that the features shown and described may be practiced in other examples. Examples are provided for the operation of wireless communication systems that may be used in the field of multi-carrier communication systems. More specifically, the techniques disclosed herein may relate to wireless communication exposure detection and / or reporting.

[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 wireless devices 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 devices 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 devices 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 the interface functionality, 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 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 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-portable) 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, a motor vehicle, 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 (RRH), a repeater 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., 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 number of sets) for respectively controlling multiple cells or sectors (e.g., three cells, three sectors, any other number of cells, or any other number 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 a transmission 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 number 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 embodiments 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 communications networks). Embodiments 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. The embodiments 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 illustrates an example of a 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 within 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 have 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 CN 152 (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 control and execution of 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., an NG-RAN) may communicate with 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., an 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-eNB 162A and ng-eNB 162B (collectively ng eNB 162)). The RAN 154 may include one or more of any quantity of base station types. The gNBs 160 and ng eNB 162 may be referred to as base stations. The base stations (e.g., the gNBs 160 and ng eNB 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., a 5G CN) via a first interface (e.g., an NG interface) and to other base stations via a second interface (e.g., an Xn interface). The NG and Xn interfaces may be established using direct physical connections and / or indirect connections over an underlying transport network, such as an Internet Protocol (IP) transport network. 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 number of planes may be used (e.g., in a protocol stack): A user plane may handle data of interest to users. A 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 / perform, 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, it may be possible for an NR network / device (or any first network / device) to connect 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 can 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). A user plane may process data associated with a user (e.g., data of interest to a user). A 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 of a user plane configuration. The user plane configuration may include, for example, an NR user plane protocol stack. FIG. 2B illustrates an example of a 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 that may be between wireless device 210 and 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 wireless device 156A and 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 or any other number 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 medium 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 medium 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 transmitted over the air interface, encryption / decryption to prevent unauthorized decoding of data 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, for 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 map / undap between split radio bearers and RLC channels (e.g., RLC channel 330) (e.g., in dual connectivity scenarios / configurations). 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. PDCP 214 and 224 may map / undap between split radio bearers and RLC channels 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 indicated 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 of 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. Commands and logical channel priority mapping restrictions 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 the 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 also 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 illustrates 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., 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 a radio bearer (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 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 also be referred to as a PDCP SDU. Data units transferred to and from higher protocol layers may also be referred to as service data units (SDUs) of the lower protocol layer, and data units transferred to and from lower protocol layers may also be referred to as protocol data units (PDUs) of the higher protocol layer. As shown in FIG. 4A, the data units from the SDAP 225 may be SDUs of the lower protocol layer PDCP 224 (eg, PDCP SDUs) or PDUs of the SDAP 225 (eg, SDAP PDUs).

[0039] Each protocol layer (e.g., a protocol layer as 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 several RLC PDUs (MAC SDUs). The MAC 222 may attach the 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. Examples of 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. A 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 channels between the RLC, MAC, and PHY layers of a protocol stack (e.g., the 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. A 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 / conveyed (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 embodiments, as described below. The Physical Uplink Control Channel (PUCCH) may include / carry UCI, which may include HARQ acknowledgements, 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 SDAP 215 and 225. The control plane configuration may include AMF 230, which includes NAS protocol 237.

[0048] The NAS protocols 217 and 237 may provide control plane functions between the wireless device 210 and the AMF 230 (e.g., the AMF 158A or any other AMF), and / or more broadly, between the wireless device 210 and the CN (e.g., the CN 152 or any other CN). The NAS protocols 217 and 237 may provide control plane functions between the wireless device 210 and the AMF 230 via signaling messages called NAS messages. There may not be a direct path between the wireless device 210 and the AMF 230 over which the NAS messages may be transmitted. The NAS messages may be transported using the ASs of the Uu and NG interfaces. The 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 broadly, 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 the wireless device). The wireless device may be substantially identical to or similar to the 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). The 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. A 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 another base station). The base station to which the wireless device is connected (e.g., has established an RRC connection) may have an 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: The RRC connection state may include 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 in a sleep state, 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, for example, 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. If the wireless device moves (e.g., via cell reselection) to a cell that is not included in the RAN notification area assigned / provisioned / configured to the wireless device, the notification area may be updated in the RAN to update the RAN notification area of ​​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 gNB DUs). 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 divided 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 / communicated 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 produce a Discrete Fourier Transform (DFT) pre-coded OFDM symbol, which may be used by one or more wireless devices in the uplink to reduce the peak-to-average power ratio (PAPR). Inverse processing may be performed on the OFDM symbols at the receiver using the FFT block to recover the data mapped to the source symbols.

[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 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 number of symbols, slots, or durations 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. Numerologies may be defined for 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 number / quantity 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-per-subframe transmission structure 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 can start with 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 minislots 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 width of a particular amount of RBs and / or subcarriers (e.g., 275 RBs or 275 × 12 = 3300 subcarriers). If used, such restrictions may restrict carrier (e.g., NR carrier) frequencies 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 can 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, for example, support 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 a downlink BWP to be the same as the center frequency of an 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). The search space may include a set of locations in the time and frequency domain where the wireless device may monitor / detect / 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 a group of multiple wireless devices or wireless user equipments). 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] A 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 / convey 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 BWP of a set of configured BWPs is an active downlink BWP for one or more downlink receptions. The value of one or more BWP indicator fields may indicate an active uplink BWP for one or more uplink transmissions.

[0070] A base station may semi-statically configure a wireless device with a default downlink BWP within a set of configured downlink BWPs associated with a PCell. The default downlink BWP may be an 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] A base station may configure a wireless device with a BWP inactivity timer value for a 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 within a time interval (e.g., 1 ms or 0.5 ms). A wireless device may switch from an active downlink BWP to a default downlink BWP, for example, when 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] Downlink BWP switching 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). Uplink BWP switching 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 switching may occur independently (e.g., in paired spectrum / spectrum). Downlink and uplink BWP switching may occur simultaneously (e.g., in 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 BWPs configured 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 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 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 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 / communicated 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 numbers / quantities 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 example of a 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 number of CCs that can be aggregated (e.g., up to 32 CCs may be aggregated in NR, or any other number may be aggregated in other systems). 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 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 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 cell CC (DL PCC). For the uplink, a carrier corresponding to a PCell may be referred to as an uplink primary cell 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 SCell configured 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 reference 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 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., an UL PCC), an SCell 1022 (e.g., an UL SCC), and an SCell 1023 (e.g., an UL SCC). One or more uplink CCs of the PUCCH group 1050 may be configured as a PUCCH SCell (or PSCell) 1061 (e.g., an UL SCC), an SCell 1062 (e.g., an UL SCC), and an SCell 1063 (e.g., an 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 / conveyed via the uplink of the PCell 1021 (e.g., via the PUCCH of the PCell 1021). UCI associated with downlink CCs of PUCCH group 1050, denoted as UCI 1071, UCI 1072, and UCI 1073, may be transmitted / conveyed via uplink on PUCCH SCell (or PSCell) 1061 (e.g., via the PUCCH of PUCCH SCell 1061).A single uplink PCell can be configured to transmit / convey UCI related to 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 be overloaded if, for example, UCI 1031, 1032, 1033, 1071, 1072, and 1073 are transmitted / conveyed 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 / conveyed 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 / communicate (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 / communicate one or more RSs to a base station (e.g., DM-RS, PT-RS, and / or SRS). The PSS and SSS may be transmitted / communicated by a base station and may be 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 / communicate 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 / conveyed 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., the number of SS / PBCH blocks per burst, the periodicity of the burst, the 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 / conveyed, 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 / communicated first and may span, for example, one OFDM symbol and 127 subcarriers. The SSS may be transmitted / communicated after the PSS (e.g., two symbols later) and may span one OFDM symbol and 127 subcarriers. The PBCH may be transmitted / conveyed 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 fewer 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 wireless device finds a PSS at a location in the time and frequency domains, it 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 frame boundary position of the cell, for example, based on the position of the SS / PBCH block. The SS / PBCH block may indicate that it was transmitted / communicated 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 include or carry one or more DM-RSs for demodulation of the PBCH. The PBCH may include an indication of the cell's current system frame 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 / convey one or more parameters to the wireless device. The MIB can be used by the wireless device to find the minimum remaining system information (RSSI) 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-collocated (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 a cell's coverage area). 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 / communicate 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 / communicated at different frequency locations may be different or substantially identical.

[0093] A CSI-RS may be transmitted / communicated 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 transmit / communicate 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-permanently. 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 related to the measurements. For semi-persistent CSI reporting, a base station may configure a wireless device to transmit / transmit periodically and selectively activate or deactivate periodic reports (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 / conveyed 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 number / quantity (e.g., maximum number / quantity) 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 the same 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 and second precoder matrices 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 / conveyed 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 a 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 a 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 quantity / number of PT-RS ports may be smaller than the quantity / number of DM-RS ports in the scheduled resources. The downlink PT-RS may be configured / assigned / restricted with a scheduled time / frequency duration for the wireless device. The downlink PT-RS may be transmitted / conveyed via symbols, for example, to facilitate phase tracking at the receiver.

[0100] A wireless device may transmit / communicate 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 / communicate 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 number / amount (e.g., maximum number / amount) 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 positions, 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 / convey 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 or may not be present, 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 / employed 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 the 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 quantity / number of PT-RS ports may be smaller than the quantity / number of DM-RS ports in the scheduled resources. The uplink PT-RS may be configured / assigned / restricted at a scheduled time / frequency duration for the wireless device.

[0102] One or more SRSs may be transmitted / communicated 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 / communicated 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 / transmitted 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 / convey 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 / convey SRS after the transmission of a PUSCH and a corresponding uplink DM-RS, for example, when the PUSCH and SRS are transmitted / conveyed 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 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 number of OFDM symbols in the SRS resource, a starting OFDM symbol of the SRS resource, 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 and second symbols are transmitted / conveyed on the same antenna port. A first antenna port and a second antenna port may be referred to as approximately co-located (QCL-ized) if, for example, 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 indication. 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 of mapping 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. The one or more parameters may be configured by higher layer signaling (e.g., RRC and / or MAC signaling) for CSI-RS resource configuration. The one or more parameters may include at least one of a CSI-RS resource configuration identity, a 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-colocation (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 / communicated 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 / communicated 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 / communicated on one or more subcarriers in the RB of the third symbol. A base station may transmit another CSI-RS associated with a beam for another wireless device using other subcarriers in the same RB (e.g., those not used to transmit / communicate CSI-RS 1101), for example, by using frequency division multiplexing (FDM). A beam used for a wireless device may be configured to use symbols that are different from the symbols used by beams of other wireless devices, for example, by using time domain multiplexing (TDM). A wireless device may be delivered with a beam 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 several 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-beam correspondence capability. The wireless device may determine a 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-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-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 / convey 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) can be implemented. 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 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 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 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 also 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) can be implemented. Procedure U1 can 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 Rx beams 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 can be used, for example, to allow a base station to adjust its Rx beam when a wireless device (e.g., a UE) uses a fixed Tx beam. The wireless device and / or 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 a narrower beam than the beam used in procedure P1. Procedure U2 may also be referred to as beam refinement. The wireless device can 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 transmit / convey a BFR request (e.g., a preamble, UCI, SR, MAC CE, and / or the like) based on, for example, 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 transmit / convey a configuration message 1310 to a wireless device, for example, before initiating the random access procedure. The four-step random access procedure may include transmitting four messages, including a first message (e.g., Msg 1 1311), a second message (e.g., Msg 2 1312), a third message (e.g., Msg 3 1313), and a fourth message (e.g., Msg 4 1314). The first message (e.g., Msg 1 1311) may include a preamble (or random access preamble). The first message (e.g., Msg 1 1311) may also be referred to as a preamble. The second message (e.g., Msg 2 1312) may be included as a random access response (RAR). The second message (eg, Msg 2 1312) may be called RAR.

[0115] The configuration message 1310 may be transmitted / communicated 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 / communicate (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 / communicated 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., Msg 1 1311) and / or the third message (e.g., Msg 3 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., Msg 2 1312) and the fourth message (e.g., Msg 4 1314).

[0116] The 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., Msg 1 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 quantity / number of SS / PBCH blocks mapped to the PRACH opportunities and / or the quantity / 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., Msg 1 1311) and / or the third message (e.g., Msg 3 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., Msg 1 1311) and the third message (e.g., Msg 3 1313), and / or a power offset value between preamble groups. The one or more RACH parameters may indicate one or more thresholds based on which the wireless device may determine at least one reference signal (e.g., SSB and / or CSI-RS) and / or uplink carrier (e.g., a normal uplink (NUL) carrier and / or a complementary uplink (SUL) carrier), for example.

[0118] The first message (e.g., Msg 1 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., Msg 3 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 at least one preamble associated with the one or more reference signals and / or the selected preamble group, for example, if an association between the one or more preambles and the at least one reference signal is configured by the 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., Msg 3 1313). The one or more RACH parameters may indicate one or more thresholds for determining a preamble format, a maximum quantity / number of preamble transmissions, and / or 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., Msg 1 1311), for example, based on the association if the association is configured. The first message (e.g., Msg 1 1311) may be transmitted / communicated 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 perform a preamble retransmission, for example, if no response is received based on (e.g., after or in response to) a preamble transmission (e.g., a monitoring window for monitoring an RAR). 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 quantity / 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 was not successful, for example, if the quantity / 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., Msg 2 1312) (e.g., received by the wireless device) may include an RAR. The second message (e.g., Msg 2 1312) may include multiple RARs corresponding to multiple wireless devices. The second message (e.g., Msg 2 1312) may be received, for example, based on (e.g., subsequently in response to) the transmission / transmission of the first message (e.g., Msg 1 1311). The second message (e.g., Msg 2 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., Msg 2 1312) may indicate that the first message (e.g., Msg 1 1311) has been received by the base station. The second message (e.g., Msg 2 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 the transmission of the third message (e.g., Msg 3 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., Msg 2 1312) after transmitting / transmitting the first message (e.g., Msg 1 1311) (e.g., a 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 / transmit the first message (e.g., Msg 1 1311) (e.g., a preamble). The wireless device may start the time window one or more symbols after the last symbol (e.g., Msg 1 1311) of the first message including the preamble (e.g., the symbol at which the first message including the preamble transmission (e.g., Msg 1 1311) is completed 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 / carries 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:

number

[0122] The wireless device may, for example, transmit / transmit a third message (e.g., Msg 3 1313) based on (e.g., subsequently to, or in response to) successful reception of the second message (e.g., Msg 2 1312) (e.g., using the resources identified in Msg 2 1312). The third message (e.g., Msg 3 1313) may be used, for example, for contention resolution in a contention-based random access procedure. Multiple wireless devices may transmit / convey the same preamble to a base station, and the base station may transmit / convey 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., Msg 3 1313) and the fourth message (e.g., Msg 4 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., Msg 3 1313) (e.g., the C-RNTI, if assigned, the TC RNTI included in the second message (e.g., Msg 2 1312), and / or any other suitable identifier), for example, to perform contention resolution.

[0123] The fourth message (e.g., Msg 4 1314) may be received, for example, based on (e.g., after or in response to) the transmission / transmission of the third message (e.g., Msg 3 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., Msg 3 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., Msg 4 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., Msg 3 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 a CCCH SDU transmitted / carried in the third message (e.g., Msg 3 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.

[0124] A wireless device may be configured with an SUL carrier and / or a NUL carrier. Initial access (e.g., random access) may be supported over an uplink carrier. A base station may configure a wireless device with multiple RACH configurations (e.g., two separate RACH configurations, 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., Msg 1 1311) and / or the third message (e.g., Msg 3 1313)) may remain on or be made via the selected carrier. A wireless device may switch uplink carriers during a random access procedure (e.g., between Msg 1 1311 and Msg 3 1313). A wireless device may determine and / or switch uplink carriers for the first message (e.g., Msg 1 1311) and / or the third message (e.g., Msg 3 1313) based on, for example, a channel clearance assessment (e.g., listen-before-talk).

[0125] 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 transmit / convey 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 transmitting two messages: a first message (e.g., Msg 1 1321) and a second message (e.g., Msg 2 1322). The first message (e.g., Msg 1 1321) and the second message (e.g., Msg 2 1322) may be similar in some respects to the first message (e.g., Msg 1 1311) and the second message (e.g., Msg 2 1312), respectively. A two-step contention-free random access procedure may not include messages similar to the third message (eg, Msg 3 1313) and / or the fourth message (eg, Msg 4 1314).

[0126] 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., Msg 1 1321). The wireless device may receive an indication of the preamble (e.g., ra-PreambleIndex) from the base station via PDCCH and / or RRC.

[0127] The wireless device may start a time window (e.g., ra-ResponseWindow) for monitoring the PDCCH for RAR, for example, based on (e.g., after or in response to) transmitting / transmitting 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 / transmitting the beam failure recovery request (e.g., the window may start any number of symbols and / or slots after transmitting / transmitting the beam failure recovery request). The wireless device may monitor for 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., after or in response to) transmitting / transmitting a first message (e.g., Msg 1 1321) and receiving a corresponding second message (e.g., Msg 2 1322). The wireless device may determine that the random access procedure has been 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 has been successfully completed, for example, if the wireless device receives an RAR including a preamble identifier corresponding to a preamble transmitted / communicated by the wireless device and / or the RAR includes a MAC sub-PDU having the preamble identifier. The wireless device may determine the response as an indication of an acknowledgment to the SI request.

[0128] 13C shows an example of a two-step random access procedure. Similar to the random access procedure shown in FIGS. 13A and 13B, a base station may transmit / communicate a configuration message 1330 to a 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 transmitting multiple messages (e.g., two messages including a first message (e.g., Msg A 1331) and a second message (e.g., Msg B 1332)).

[0129] Msg A 1320 may be sent / transmitted in an uplink transmission by the wireless device. Msg A 1320 may include one or more transmissions of preamble 1341 and / or one or more transmissions of transport block 1342. Transport block 1342 may include content similar and / or equivalent to the content of a third message (e.g., Msg 3 1313) (e.g., shown in FIG. 13A). 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., Msg B 1332), for example, based on (e.g., subsequently in response to) sending / transmitting a first message (e.g., Msg A 1331). The second message (e.g., Msg B 1332) may include content similar and / or equivalent to the content of the second message (e.g., Msg 2 1312) (e.g., the RAR shown in FIG. 13A), the content of the second message (e.g., Msg 2 1322) (e.g., the RAR shown in FIG. 13B), and / or the content of the fourth message (e.g., Msg 4 1314) (e.g., shown in FIG. 13A).

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

[0131] A wireless device may determine radio resources and / or uplink transmit power of the preamble 1341 and / or transport block 1342 (e.g., included in the first message (e.g., Msg A 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 of 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., Msg B 1332).

[0132] 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 transmit / convey a second message (e.g., Msg B 1332) in response to the first message (e.g., Msg A 1331). The second message (e.g., Msg B 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., Msg B 1332) corresponds to or matches the preamble transmitted / communicated by the wireless device, and / or if the identifier of the wireless device in the second message (e.g., Msg B 1332) corresponds to or matches the identifier of the wireless device in the first message (e.g., Msg A 1331) (e.g., transport block 1342).

[0133] A wireless device and a 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 a PHY layer (e.g., Layer 1) and / or a MAC layer (e.g., Layer 2) of a wireless device or a base station. The control signaling may include downlink control signaling transmitted / communicated from a base station to a wireless device and / or uplink control signaling transmitted / communicated from a wireless device to a base station.

[0134] The downlink control signaling may include at least one of a downlink scheduling assignment, an uplink scheduling grant indicating uplink radio resources and / or transport formats, 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 / conveyed via a PDCCH by a base station. The payload transmitted / conveyed 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.

[0135] 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 modulo-2 addition (or exclusive-OR) of the identifier value and the CRC parity bits. The identifier may include a 16-bit value of the RNTI.

[0136] 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., Msg 3 similar to Msg 3 1313 shown in FIG. 13A). Encodings of other RNTIs configured by the base station for the wireless device include a configured scheduling RNTI (CS RNTI), transmit power control PUCCH RNTI (TPC PUCCH-RNTI), transmit power control PUSCH RNTI (TPC-PUSCH-RNTI), transmit power control SRS RNTI (TPC-SRS-RNTI), Interruption RNTI (INT-RNTI), slot format indication RNTI (SFI-RNTI), semi-persistent CSI RNTI (SP-CSI-RNTI), modulation and coding scheme Cell RNTI (MCS-C RNTI), and / or the like.

[0137] 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 a 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 for transmitting transmit power control (TPC) commands for the PUCCH or PUSCH. DCI format 2_3 may be used for transmitting 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.

[0138] A base station may process the DCI using channel coding (e.g., polar 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 / convey the DCI via a PDCCH occupying several consecutive control channel elements (CCEs), for example, based on the payload size of the DCI and / or the coverage of the base station. The number of consecutive CCEs (referred to as an aggregation level) may be 1, 2, 4, 8, 16, and / or any other suitable 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 of CCEs and REGs (e.g., CCE to REG mapping).

[0139] 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 a 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 CORESETs 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 numbers of resource blocks in the frequency domain.

[0140] FIG. 14B shows an example of CCE-to-REG mapping. CCE-to-REG mapping may be performed 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 perform different or identical CCE-to-REG mappings for 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.

[0141] A base station may transmit / convey 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: several PDCCH candidates to be monitored per aggregation level; a PDCCH monitoring periodicity and a PDCCH monitoring pattern; one or more DCI formats to be monitored by the 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, for example, based on the identity of the wireless device (e.g., C-RNTI).

[0142] In FIG. 14B , the wireless device may determine time-frequency resources of the CORESET based on one or more RRC messages. The wireless device may determine the CCE-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 several (e.g., up to 10) 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 positions, possible (or configured) PDCCH formats (e.g., the number of CCEs, the number of PDCCH candidates in a common search space, and / or the 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).

[0143] Uplink control signaling (such as 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 beamforming schemes) for the downlink transmission based on the received CSI. The uplink control signaling may include a scheduling request (SR). The wireless device may send / transmit 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 / communicate uplink control signaling over the PUCCH using one of several PUCCH formats.

[0144] 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 quantity / number of uplink symbols for UCI transmission and the 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 / convey UCI over PUCCH resources, for example, if the transmission spans one or two symbols and the number / number of HARQ-ACK information bits with positive or negative SR (HARQ-ACK / SR bits) is one or two. PUCCH format 1 may occupy several OFDM symbols (e.g., between 4 and 14 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 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 number of UCI bits is two or more. PUCCH format 3 may occupy several 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 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 several 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 number of UCI bits is two or more, and the PUCCH resource includes an OCC.

[0145] A base station may transmit / convey configuration parameters of 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 number of sets in other systems) may be configured on the uplink BWP of a cell. A PUCCH resource set may consist of multiple PUCCH resources, with the PUCCH resource identified by a PUCCH resource set index, a PUCCH resource identifier (e.g., pucch-Resourceid), and / or a number (e.g., a maximum number) of UCI information bits that a wireless device can transmit using one of the multiple PUCCH resources in a PUCCH resource set. When configured with multiple PUCCH resource sets, a 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). A wireless device may select a first PUCCH resource set whose PUCCH resource set index is equal to "0," for example, if the total bit length of the UCI information bits is two or less. 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 the 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 the second configuration value and less than or equal to a third value (e.g., 1406, 1706, or any other number of bits).

[0146] 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 received on / via a PDCCH (e.g., in DCI format 1_0 or DCI format 1_1). An n-bit (e.g., 3-bit) PUCCH resource indicator in the DCI may indicate one of multiple (e.g., eight) PUCCH resources in the PUCCH resource set. The wireless device may transmit / convey UCI (HARQ-ACK, CSI, and / or SR) based on the PUCCH resource indicator, for example.

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

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

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

[0150] 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 transmit 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 transmit processing system 1520 of the wireless device 1502. The transmit processing system 1510 and the transmit 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 transmit processing, the PHY layer may perform, for example, forward error correction coding of transport channels, interleaving, rate matching, mapping of transport channels to physical channels, modulation of physical channels, multiple-input multiple-output (MIMO) or multi-antenna processing, and / or the like.

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

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

[0153] 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 functions (e.g., one or more functions described herein and other functions of computers, processors, memories, and / or other peripherals in general). 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.

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

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

[0156] 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. The 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 controllers 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 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.

[0157] While FIG. 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. Furthermore, 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 FIG. 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).

[0158] FIG. 16A shows an example structure for uplink transmission. Processing of a baseband signal representing a physical uplink shared channel may include / perform 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. An SC-FDMA signal for uplink transmission may be generated, for example, when transform precoding is enabled. A CP-OFDM signal for uplink transmission may be generated, for example, when transform precoding is not enabled (e.g., as shown in FIG. 16A). These functions are examples, and other mechanisms for uplink transmission may be implemented.

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

[0160] Figure 16C shows an example structure for downlink transmission. 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 layers for transmission on antenna ports, mapping the complex-valued modulation symbols of antenna ports to resource elements, generating a complex-valued time-domain OFDM signal per antenna port, and / or the like. These functions are examples for downlink transmission, and other mechanisms may be implemented.

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

[0162] A wireless device may receive one or more messages (e.g., RRC messages) from a base station including 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.

[0163] 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 until the timer is stopped or expires (e.g., due to BWP switching). A timer may be used to measure a time period / window of a process. With regard to implementations and / or procedures related to one or more timers or other parameters, it will be understood that 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 embodiment implementations may be configured / provided to restart the measurement of the time window.

[0164] FIG. 17 shows an example TCI state update. The TCI state update may include a unified beam update. A wireless device 1701 may receive one or more messages (e.g., at time T0). The wireless device 1701 may receive one or more messages from a computing device 1702, which may include any computing device described herein (e.g., a base station, a relay node, a wireless device, etc.). For example, the wireless device 1701 may receive one or more messages from a base station. The wireless device 1701 may receive one or more messages from a relay node. The wireless device 1701 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 (e.g., the configuration parameters at time T0 of FIG. 17). The one or more configuration parameters may include RRC configuration parameters. The one or more configuration parameters may include RRC reconfiguration parameters.

[0165] The one or more configuration parameters may be for one or more cells (e.g., multiple cells). The one or more (or multiple) cells may include a cell. The cell may be, for example, a serving cell. At least one configuration parameter of the one or more configuration parameters may be for a cell. The cell may be a primary cell (PCell). 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, for example, an unlicensed cell operating in an unlicensed band. The cell may be, for example, a licensed cell 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 (or any other frequency or frequency range). 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 (or any other frequency or frequency range). The cell may operate in a third frequency range (FR3). FR3 may include, for example, the frequency band from 52.6 GHz to 71 GHz (or any other frequency or frequency range). FR3 may include, for example, the frequency band beginning at (or exceeding) 52.6 GHz (or any other frequency).

[0166] The wireless device may perform uplink transmission (e.g., PUSCH, PUCCH, SRS) through / for the cell at a first time and a first frequency. The wireless device may perform downlink reception (e.g., PDCCH, PDSCH) through / for the cell at a second time and a second frequency. The cell may operate in a time division duplex (TDD) mode. For example, in the TDD mode, the first frequency and the second frequency may be the same. The first time and the second time may be different, for example, in the TDD mode. The cell may operate in a frequency division duplex (FDD) mode. For example, in the FDD mode, the first frequency and the second frequency may be different. For example, in the FDD mode, the first time and the second time may be the same. The cell may operate in a code division multiplexing (CDM) mode, for example, where the first frequency and the second frequency may be the same or different and / or the first time and the second time may be the same or different. The cell may operate in a spatial domain multiplexing (SDM) mode, for example, where the first frequency and the second frequency may be the same or different and / or the first time and the second time may be the same or different. The cell may operate in one or more of a TDD mode, an FDD mode, a CDM mode, and / or an SDM mode.

[0167] The wireless device may be in a plurality of RRC modes. For example, the wireless device may be in an RRC connected mode, an RRC idle mode, or an RRC inactive mode.

[0168] A cell may include multiple BWPs, including one or more uplink BWPs that include the cell's uplink BWP, and one or more downlink BWPs that include the cell's downlink BWP.

[0169] One BWP of the multiple BWPs is in one of an active state and an inactive state. When one downlink BWP of one or more downlink BWPs is in an active state, the wireless device may monitor a downlink channel / signal (e.g., PDCCH, DCI, CSI-RS, PDSCH) on / for / via the downlink BWP. When one downlink BWP of one or more downlink BWPs is in an active state, the wireless device may receive a PDSCH on / through / for the downlink BWP. When one downlink BWP of one or more downlink BWPs is in an inactive state, the wireless device may not monitor a downlink channel / signal (e.g., PDCCH, DCI, CSI-RS, PDSCH) on / through / for the downlink BWP. When one downlink BWP of one or more downlink BWPs is in an inactive state, the wireless device may stop monitoring (or receiving) a downlink channel / signal (e.g., PDCCH, DCI, CSI-RS, PDSCH) on / for / via the downlink BWP. When one or more downlink BWPs are in an inactive state, the wireless device cannot receive a PDSCH on / through / for the downlink BWP. When one of the one or more downlink BWPs is in an inactive state, the wireless device may stop receiving a PDSCH on / through / for the downlink BWP.

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

[0171] The wireless device may activate a downlink BWP of one or more downlink BWPs of a cell. Activating a downlink BWP may include setting (or switching) the downlink BWP as an 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.

[0172] The wireless device may activate an uplink BWP of one or more uplink BWPs of a cell. Activating the uplink BWP may include the wireless device setting (or switching to) 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.

[0173] The one or more configuration parameters may be for the (active) downlink BWP of the cell. At least one configuration parameter of the one or more configuration parameters may be for the downlink BWP of the cell.

[0174] The one or more configuration parameters may be for the (active) uplink BWP of the cell. 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 (or numerology) for the downlink BWP. The one or more configuration parameters may indicate subcarrier spacing (or numerology) for the uplink BWP.

[0175] The subcarrier spacing value (of the downlink BWP and / or uplink BWP) may be / may indicate, for example, 15 kHz (μ=0), or any other frequency or frequency range. The subcarrier spacing value may be / may indicate, for example, 30 kHz (μ=1). The subcarrier spacing value may be / may indicate, for example, 60 kHz (μ=2). The subcarrier spacing value may be / may indicate, for example, 120 kHz (μ=3). The subcarrier spacing value may be / may indicate, for example, 240 kHz (μ=4). The subcarrier spacing value may be / may indicate, for example, 480 kHz (μ=5). The subcarrier spacing value may be / may indicate, for example, 960 kHz (μ=6). For example, 480 kHz may be valid / applicable in FR3. For example, 960 kHz may be valid / applicable in FR3. For example, 240 kHz may be valid / applicable in FR3. For example, 120 kHz may be valid / applicable for FR3. Any frequency or range of frequencies may be valid / applicable for any FR(n) (e.g., μ may be equal to any value).

[0176] The one or more configuration parameters may indicate multiple control resource sets (CORESETS). The one or more configuration parameters may indicate multiple CORESETS for the (active) downlink BWP of the cell. The (active) downlink BWP may include multiple CORESETS.

[0177] One or more configuration parameters may indicate multiple CORESET indices / identifiers / indicators (e.g., provided by the upper layer parameter ControlResourceSetId) for multiple CORESETs. Each CORESET of the multiple CORESETs may be identified / indicated by a respective CORESET index of the multiple CORESET indexes. A first CORESET of the multiple CORESETs may be identified by a first CORESET index of the multiple CORESET indexes. A second CORESET of the multiple CORESETs may be identified by a second CORESET index of the multiple CORESET indexes.

[0178] The one or more configuration parameters may indicate multiple TCI states (e.g., provided by higher layer parameter tci-StatesToAddModList, such as PDSCH_Config, PUSCH_Config, PDCCH_Config, PUCCH_Config, etc.). The one or more configuration parameters may be transmitted / received in one or more messages 1710, as shown in FIG. 17 at time T0. The one or more configuration parameters may indicate multiple TCI states, for example, of a downlink BWP of a cell. In FIG. 17, the multiple TCI states may include TCI state 1, TCI state 2, ..., TCI state M.

[0179] The quantity / number of the plurality of TCI states may be equal to, for example, 128 (e.g., M=128) or any other value. The quantity / number of the plurality of TCI states may be equal to, for example, 64 (e.g., M=64). The quantity / number of the plurality of TCI states may be equal to, for example, 32 (e.g., M=32). The quantity / number of the plurality of TCI states may be based on the capabilities of the wireless device. The wireless device may send (e.g., transmit) a capability message (e.g., a UE capability message) indicating the maximum quantity / number of TCI states. The quantity / number of the plurality of TCI states indicated by one or more configuration parameters may be less than or equal to the maximum number of TCI states.

[0180] The one or more configuration parameters may indicate multiple TCI state indexes / identifiers / indicators (e.g., provided by the higher layer parameter TCI-StateId) for multiple TCI states. Each TCI state of the multiple TCI states may be identified / indicated by a respective TCI state index of the multiple TCI state indices. A first TCI state of the multiple TCI states may be identified by a first TCI state index of the multiple TCI state indices. A second TCI state of the multiple TCI states may be identified by a second TCI state index of the multiple TCI state indices.

[0181] The multiple TCI states (or at least one TCI state among the multiple TCI states) may be for (decoding) PDSCH transmission / reception of / for the cell. The one or more configuration parameters may indicate the multiple TCI states (or at least one TCI state among the multiple TCI states) for decoding PDSCH transmission / reception of / for the downlink BWP of the cell. The TCI state among the multiple TCI states may indicate a quasi-co-located reference signal (e.g., by SourceRs-Info) of / for the DM-RS (or DM-RS antenna port) of the PDSCH transmission / reception.

[0182] The multiple TCI states (or at least one TCI state among the multiple TCI states) may be for PDCCH transmission / reception of / for the cell. The one or more configuration parameters may indicate multiple TCI states (or at least one TCI state among the multiple TCI states) for PDCCH transmission / reception of / for the downlink BWP of the cell. A TCI state among the multiple TCI states may indicate a quasi-co-located reference signal of / for the DM-RS (or DM-RS antenna port) of the PDCCH transmission / reception.

[0183] The multiple TCI states (or at least one TCI state among the multiple TCI states) may be for CSI-RS transmission / reception of / for the cell. The one or more configuration parameters may indicate multiple TCI states (or at least one TCI state among the multiple TCI states) for CSI-RS transmission / reception of / for the downlink BWP of the cell. A TCI state among the multiple TCI states may indicate a quasi-colocated reference signal of / for CSI-RS transmission / reception.

[0184] The multiple TCI states (or at least one TCI state among the multiple TCI states) may be for transmission of an uplink signal (e.g., UCI, dynamic grant PUSCH, configured uplink grant-based PUSCH, SRS, PUCCH, transport block, SR, CSI, HARQ-ACK) of / for / on / via uplink resources (e.g., PUSCH resources, PUCCH resources, SRS resources) of the cell. One or more configuration parameters may indicate the multiple TCI states (or at least one TCI state among the multiple TCI states) for transmission of an uplink signal of / for / on / via uplink resources of the uplink BWP of the cell. The wireless device may determine a spatial domain transmit filter / beam for transmission of the uplink signal based on a reference signal indicated by (or in) a TCI state among the multiple TCI states.

[0185] The multiple TCI state pools / groups may include multiple TCI states. For example, two TCI state pools / groups may include multiple TCI states. A first TCI state pool of the two TCI state pools may include multiple downlink TCI states of the multiple TCI states. A second TCI state pool of the two TCI state pools may include multiple uplink TCI states of the multiple TCI states.

[0186] A (single) TCI state pool / group may include multiple TCI states, the multiple TCI states may / can include multiple downlink TCI states, and the multiple TCI states may / can include multiple uplink TCI states.

[0187] A wireless device may apply / use multiple downlink TCI states for reception / decoding of a transport block (or PDSCH transmission / reception). A wireless device may use multiple downlink TCI states, for example, for reception / decoding of a transport block (or PDSCH transmission / reception) scheduled for a cell's downlink BWP. A wireless device may use multiple downlink TCI states, for example, for reception of a downlink signal (e.g., PDSCH transmission / reception, PDCCH transmission / reception, DCI, transport block, CSI-RS, etc.) via a cell's downlink BWP. For example, a wireless device may not use multiple downlink TCI states (or each TCI state of multiple downlink TCI states) for transmission of an uplink signal (e.g., PUSCH transmission, PUCCH transmission, UCI, transport block, SRS, etc.). A TCI state among the multiple downlink TCI states may indicate / have / include a quasi-co-located reference signal of a DM-RS of a downlink signal (e.g., PDSCH / PDCCH transmission / reception). The reference signal may be quasi-colocated with the DM-RS of the downlink signal. The reference signal may be quasi-colocated with the DM-RS of the downlink signal with respect to the quasi-colocation type (e.g., QCL Type A, QCL Type B, QCL Type C, QCL Type D, QCL Type E, etc.). The TCI state may indicate / include / have the quasi-colocation type for the reference signal. A TCI state among the multiple downlink TCI states may indicate a quasi-colocated reference signal with / for reception of the downlink signal (e.g., CSI-RS). Each TCI state of the multiple downlink TCI states may indicate a respective reference signal for quasi-colocation with / for DM-RS (e.g., PDSCH / PDCCH transmission / reception) of the downlink signal. Each TCI state of the multiple downlink TCI states may indicate a respective reference signal for quasi-colocation with / for reception of the downlink signal (e.g., CSI-RS).

[0188] A wireless device may apply / use multiple uplink TCI states for a transport block transmission (or a PUSCH transmission). A wireless device may use multiple uplink TCI states, for example, for a transport block transmission (or a PUSCH transmission) scheduled / configured for a cell's uplink BWP. A wireless device may use multiple uplink TCI states, for example, for an uplink signal transmission (e.g., a PUSCH transmission, a PUCCH transmission, a UCI, a transport block, an SRS, etc.) via a cell's uplink BWP. A wireless device may not use multiple uplink TCI states (or each TCI state of multiple uplink TCI states) for downlink signal reception (e.g., a PDSCH transmission / reception, a PDCCH transmission / reception, a DCI, a transport block, a CSI-RS, etc.). A wireless device may determine a spatial domain transmit filter / beam based on a reference signal indicated by (or in) a TCI state among the multiple uplink TCI states for an uplink signal transmission. The wireless device may determine a respective spatial domain transmit filter / beam based on a reference signal indicated by (or present in) each TCI state of the multiple uplink TCI states for transmission of the uplink signal. The wireless device may determine a transmit power based on one or more power control parameters (e.g., a target received power, a closed-loop index, a path loss compensation factor, an alpha, a path loss reference signal, etc.) indicated by (or included in, associated with, or mapped to) each TCI state of the multiple uplink TCI states for transmission of the uplink signal. The wireless device may determine a respective transmit power based on one or more power control parameters indicated by (or included in, associated with, or mapped to) each TCI state of the multiple uplink TCI states for transmission of the uplink signal.

[0189] A (single) TCI state pool / group may include multiple TCI states. One or more configuration parameters may indicate a joint / common UL / DL TCI state mode and a separate UL / DL TCI state mode, for example, based on the number of TCI state pools. One or more configuration parameters may indicate a joint / common UL / DL TCI state mode, for example, based on one or more configuration parameters indicating a (single) TCI state pool / group. One or more configuration parameters may indicate a separate UL / DL TCI state mode, for example, based on one or more configuration parameters indicating two TCI state pools / groups.

[0190] The one or more configuration parameters may include, for example, a TCI type parameter indicating a joint / common UL / DL TCI state mode or a separate UL / DL TCI state mode. The TCI type parameter may be set to "joint" or "joint UL / DL TCI state," indicating a joint / common UL / DL TCI state mode. The TCI type parameter may be set to "separate" or "separate UL / DL TCI state," indicating a separate UL / DL TCI state mode.

[0191] The multiple TCI states may be / include multiple common / joint TCI states (or multiple common / joint uplink and downlink TCI states). A wireless device may use multiple common / joint TCI states, for example, for reception of downlink signals (e.g., PDSCH, PDCCH, CSI-RS, DCI, transport blocks, etc.) via a cell's downlink BWP. A wireless device may use multiple common / joint TCI states, for example, for transmission of uplink signals (e.g., PUSCH, PUCCH, UCI, transport blocks, SRS, etc.) via a cell's uplink BWP. A wireless device may use each TCI state of the multiple common / joint TCI states, for example, for reception of downlink signals and transmission of uplink signals. A TCI state of the multiple TCI states (or multiple common / joint TCI states) may indicate a quasi-colocated reference signal for / for DM-RS of downlink signals (e.g., PDSCH / PDCCH transmission / reception). A TCI state of the multiple TCI states (or multiple common / joint TCI states) may indicate a quasi-collocated reference signal for / for reception of a downlink signal (e.g., CSI-RS). Each TCI state of the multiple TCI states (or multiple common / joint TCI states) may indicate a respective reference signal for quasi-collocated for / for DM-RS of a downlink signal (e.g., PDSCH / PDCCH transmission / reception). Each TCI state of the multiple TCI states (or multiple common / joint TCI states) may indicate a respective reference signal for quasi-collocated for / for reception of a downlink signal (e.g., CSI-RS). The wireless device may determine a spatial-domain transmit filter / beam based on the reference signal indicated by (or in) a TCI state of the multiple TCI states (or multiple common / joint TCI states) for transmission of an uplink signal. The wireless device may determine a respective spatial domain transmit filter / beam for transmitting an uplink signal based on a reference signal indicated by (or in) each TCI state of multiple TCI states (or multiple common / joint TCI states).

[0192] One or more configuration parameters may not indicate one or more TCI states of the downlink BWP of the cell. One or more TCI state parameters / configurations may not be present in one or more configuration parameters. One or more configuration parameters may not include one or more TCI state parameters / configurations in / for the downlink BWP of the cell. One or more configuration parameters may indicate, for example, multiple TCI states for a reference BWP (e.g., a reference downlink BWP) of a reference cell. The multiple cells may include a reference cell. The wireless device may apply / use (or be associated with) multiple TCI states of the reference BWP of the reference cell for the downlink BWP of the cell. One or more configuration parameters may indicate the reference BWP of the reference cell to apply / use, for the cell (or the downlink BWP of the cell), multiple TCI states of (or that may be associated with) the reference BWP of the reference cell.

[0193] The wireless device may receive a wake-up command 1720 as shown in FIG. 17. The wake-up command may be sent / received in one or more messages (e.g., activate / deactivate DCI, MAC-CE, UE-specific MAC CE TCI state at time T1 in FIG. 17, wake-up command) indicating activation of a subset of the plurality of TCI states. The wake-up command may activate / select / display / update the subset of the plurality of TCI states. The subset of the plurality of TCI states may / can include, for example, one or more TCI states of the plurality of TCI states. The subset of the plurality of TCI states may / can include, for example, a first plurality of TCI states of the plurality of TCI states. For example, in FIG. 17, the subset of the plurality of TCI states is TCI state 4, TCI state 5, TCI state 8, TCI state 26, TCI state 61, and TCI state 42.

[0194] The activation command may include one or more fields indicating / including at least one TCI state index that identifies / indicates / identifies a subset of the plurality of TCI states. The plurality of TCI state indexes may include at least one TCI state index. Each TCI state of the subset of the plurality of TCI states may be identified / indicated by a respective TCI state index of the at least one TCI state index. The one or more fields may be set to a value (e.g., 1) that indicates activation of the subset of the plurality of TCI states. Based on the one or more fields indicating that the subset of the plurality of TCI states is set to a value, the wireless device may activate the subset of the plurality of TCI states. The wireless device may activate the subset of the plurality of TCI states, for example, based on receiving an activation command that activates / selects / indicates / updates the subset of the plurality of TCI states.

[0195] The wireless device may map a subset of the multiple TCI states to one or more TCI code points (e.g., in FIG. 17, in TCI code points 000, 001, ..., 110, and 011). Mapping a subset of the multiple TCI states to one or more TCI code points may include grouping the subset of the multiple TCI states to / in one or more TCI code points. Each TCI code point of the one or more TCI code points may include / indicate a respective TCI state of the subset of the multiple TCI states. For example, in FIG. 17, TCI state 4 may be mapped to TCI code point 000, TCI state 5 and TCI state 8 may be mapped to TCI code point 001, TCI state 26 and TCI state 61 may be mapped to TCI code point 110, and TCI state 42 may be mapped to TCI code point 111. Each TCI code point of the one or more TCI code points may be equal to the value of the TCI field in the DCI. The DCI may or may not schedule a transport block (e.g., PDSCH, PUSCH). The TCI field in the DCI may indicate (or be equal to) a TCI codepoint among one or more TCI codepoints. The TCI codepoint may include / indicate at least one TCI state among a subset of multiple TCI states.

[0196] A TCI state of a subset of the multiple TCI states may indicate a reference signal having / for a quasi-co-location type (e.g., QCL Type A, QCL Type D). The TCI state may not include / indicate a BWP index / ID and / or a cell index / ID for the reference signal. The wireless device may assume that the reference signal consists of a downlink BWP of the cell to which the TCI state applies.

[0197] The subset of the multiple TCI states may be for (decoding) PDSCH transmission / reception of / for the cell. The activation command may indicate activation of the subset of the multiple TCI states for decoding PDSCH transmission / reception of / for the downlink BWP of the cell.

[0198] The multiple TCI states may be for transmission of uplink signals (e.g., UCI, PUSCH transmission, SRS, PUCCH, transport block, SR, CSI, CSI report, HARQ-ACK) of / for / at / via uplink resources (e.g., PUSCH resource, PUCCH resource, SRS resource) of the cell. The activation command may indicate activation of a subset of the multiple TCI states for transmission of uplink signals of / for / on / via uplink resources of the uplink BWP of the cell.

[0199] The subset of the multiple TCI states may be / include one or more downlink TCI states. A wireless device may use one or more downlink TCI states for reception / decoding of transport blocks (or PDSCH transmission / reception). A wireless device may use one or more downlink TCI states for reception / decoding of transport blocks (or PDSCH transmission / reception) scheduled / configured for a cell's downlink BWP, for example. A wireless device may use one or more downlink TCI states for reception of downlink signals (e.g., PDSCH, PDCCH, DCI, CSI-RS, transport blocks, etc.) via a cell's downlink BWP, for example.

[0200] The subset of the multiple TCI states may be / include one or more uplink TCI states. A wireless device may use one or more uplink TCI states for transmission of a transport block (or PUSCH transmission). A wireless device may use one or more uplink TCI states for transmission of a transport block (or PUSCH transmission) scheduled / configured for a cell's uplink BWP. A wireless device may use one or more uplink TCI states for transmission of an uplink signal (e.g., PUSCH, PUCCH, UCI, transport block, SRS, etc.) via a cell's uplink BWP.

[0201] The subset of the plurality of TCI states may be / include one or more common / joint TCI states. A wireless device may use one or more common / joint TCI states, for example, for reception of downlink signals (e.g., PDSCH, PDCCH, DCI, CSI-RS, transport blocks, etc.) via a cell's downlink BWP. A wireless device may use one or more common / joint TCI states, for example, for transmission of uplink signals (e.g., PUSCH, PUCCH, UCI, transport blocks, SRS, etc.) via a cell's uplink BWP. For example, a wireless device may use one or more common / joint TCI states for reception of downlink signals via a cell's downlink BWP and for transmission of uplink signals via the cell's uplink BWP.

[0202] A wireless device may receive downlink signals 1730 as shown in FIG. 17. The downlink signals may be transmitted / received in one or more messages. The downlink signals may include date and / or control information (e.g., transport block, PDCCH / PDSCH transmission, CSI-RS, aperiodic CSI-RS, DCI, etc.). The wireless device may receive the downlink signals based on, for example, a TCI state of a subset of multiple TCI states. The wireless device may receive, for example, a DCI that schedules / triggers reception / transmission of the downlink signals. The DCI may indicate, for example, a dynamic uplink / downlink grant. The DCI may indicate, for example, activation of an SPS PDSCH transmission. The wireless device may receive a downlink signal (e.g., transport block) for / that SPS PDSCH transmission. The DCI may include a TCI field (or a TCI codepoint that includes / indicates the TCI state) that indicates the TCI state. The one or more configuration parameters may indicate / configure / schedule / trigger transmission / reception of downlink signals (e.g., periodic CSI-RS, PDCCH / PDSCH transmission, etc.) The one or more configuration parameters may include / indicate a TCI field (or a TCI codepoint that includes / indicates a TCI state) that indicates a TCI state for transmission / reception of downlink signals.

[0203] Receiving a downlink signal based on the TCI state may include at least one DMRS antenna port of the downlink signal (e.g., PDSCH / PDCCH transmission, transport block) being quasi-co-located with a reference signal (e.g., CSI-RS, SS / PBCH block, SRS, PUCCH, etc.) indicated by the TCI state. The at least one DMRS antenna port of the downlink signal may be quasi-co-located with a reference signal with respect to a quasi-co-location type (e.g., QCL Type A, QCL Type B, QCL Type C, QCL Type D, etc.). The TCI state may indicate / include / have a quasi-co-location type. The TCI state may include / have a reference signal index that indicates / identifies a reference signal. One or more configuration parameters may indicate the reference signal index for the TCI state.

[0204] Receiving a downlink signal based on the TCI state may include the downlink signal (e.g., CSI-RS, DM-RS) being quasi-co-located with a reference signal (e.g., CSI-RS, SS / PBCH block, SRS, PUCCH, etc.) indicated by the TCI state. The downlink signal may be quasi-co-located with the reference signal with respect to a quasi-co-location type (e.g., QCL Type A, QCL Type B, QCL Type C, QCL Type D, etc.). The TCI state may indicate / include / have the quasi-co-location type. The TCI state may include / have a reference signal index that indicates / identifies the reference signal. One or more configuration parameters may indicate the reference signal index for the TCI state.

[0205] Receiving the downlink signal based on the TCI state may include receiving the downlink signal using a spatial-domain receive / receive filter / beam used to receive a reference signal indicated by the TCI state. The spatial-domain receive / receive filter / beam used to receive the downlink signal may be the same (or substantially the same, x degree intervals, x=0, 1, 5, 10, etc.) as the spatial-domain receive / receive filter / beam used to receive the reference signal.

[0206] The wireless device may transmit (e.g., transmit) an uplink signal (e.g., a transport block, a PUCCH / PUSCH transmission, an SRS, an aperiodic SRS, a PUCCH, an aperiodic PUCCH, a UCI, etc.) based on a TCI state of a subset of the plurality of TCI states. The wireless device may receive, for example, a DCI that schedules / triggers the transmission of an uplink signal. The DCI may, for example, indicate a dynamic uplink / downlink grant. The DCI may, for example, indicate the activation of a configured uplink grant (e.g., a type 2 configured uplink grant). The wireless device may transmit (e.g., transmit) an uplink signal (e.g., a transport block, etc.) for / of the configured uplink grant. The DCI may include a TCI field (or a TCI codepoint that includes / indicates the TCI state) that indicates the TCI state. One or more configuration parameters may indicate / configure / schedule / trigger the transmission of an uplink signal (e.g., a periodic SRS, a PUCCH / PUSCH transmission, a periodic PUCCH, a configured uplink grant, etc.). The one or more configuration parameters may include / indicate a TCI field (or a TCI codepoint that includes / indicates a TCI state) that indicates a TCI state for transmission of an uplink signal. The one or more configuration parameters indicate a TCI state of a configured uplink grant (e.g., a type 1 configured uplink grant). The wireless device may transmit (e.g., transmit) an uplink signal (e.g., a transport block) for / of the configured uplink grant (e.g., a type 1 configured uplink grant).

[0207] Transmitting (e.g., transmitting) the uplink signal based on the TCI state may include transmitting the uplink signal using a space-domain transmit / transmit filter / beam determined based on a reference signal (e.g., CSI-RS, SS / PBCH block, SRS, PUCCH) indicated by the TCI state. The space-domain transmit / transmit filter / beam used to transmit the uplink signal may be the same (or substantially the same, x-degree intervals, x=0, 1, 5, 10, etc.) as the space-domain transmit / transmit filter / beam used to transmit the reference signal (e.g., SRS, PUCCH). The space-domain transmit / transmit filter / beam used to transmit the uplink signal may be the same (or substantially the same, x-degree intervals, x=0, 1, 5, 10, etc.) as the space-domain receive / receive filter / beam used to receive the reference signal (e.g., CSI-RS, SS / PBCH block).

[0208] The wireless device may monitor PDCCH transmissions in / via a CORESET for DCI based on the TCI state. The multiple CORESETs may include the CORESET. The downlink BWP of the cell (or one or more CORESETs within the downlink BWP) may include the CORESET. A subset of the multiple TCI states may include the TCI state. The subset of the TCI states may or may not include the TCI state. The wireless device may receive a second wake-up command indicating activation of the TCI state for the CORESET. The second wake-up command may or may not be the same as the wake-up command (time T1 in FIG. 17). Monitoring PDCCH transmissions in the CORESET based on the TCI state may include at least one DMRS antenna port of the PDCCH transmissions in the CORESET being quasi-co-located with a reference signal (e.g., CSI-RS, SS / PBCH block, SRS, etc.) indicated by the TCI state. At least one DMRS antenna port may be quasi-co-located with the reference signal for a quasi-co-location type (e.g., QCL Type A, QCL Type B, QCL Type C, QCL Type D, etc.) The TCI state may indicate / include / have the quasi-co-location type.

[0209] The quantity / number of the one or more TCI code points may be equal to 1. The one or more TCI code points may be a (single) TCI code point. The (single) TCI code point may indicate at least two TCI states of the multiple TCI states. The subset of the multiple TCI states may be at least two TCI states. The wireless device may not receive a DCI indicating activation of one or more TCI states of the at least two TCI states, for example, based on the number of the one or more TCI code points being equal to 1. The wireless device may not receive a DCI indicating activation of one or more TCI states of the at least two TCI states, for example, based on an activation command indicating activation of the at least two TCI states.

[0210] The quantity / number of one or more TCI code points may be greater than 1. The wireless device may receive a DCI (e.g., DCI 1 at time T2 in FIG. 17). The DCI may be, for example, DCI format 1_1. The DCI may be, for example, DCI format 1_2. The DCI may be, for example, DCI format 1_x, where x = 0, 1, 2, .... The DCI may be, for example, DCI format 0_x, where x = 0, 1, 2, ....

[0211] The DCI may include a TCI field. The TCI field may indicate one TCI codepoint among one or more TCI codepoints. The value of the TCI field (e.g., 110 in step 1730 of FIG. 17) may be equal to the TCI codepoint, for example. The value of the TCI field may indicate, for example, a TCI codepoint. The TCI codepoint (e.g., 110) may indicate / include at least two TCI states. The DCI may indicate (or activate) the activation of at least two TCI states. The at least two TCI states may include a first TCI state and a second TCI state. For example, in FIG. 17, the first TCI state is TCI state 26. The second TCI state is TCI state 61. Any TCI codepoint may indicate / include any one or more TCI states (e.g., one TCI state, two TCI states, or any number of TCI states). The DCI may indicate the activation of one TCI state (e.g., TCI state 42). A DCI may indicate the activation of at least two TCI states (or any other quantity of TCI states).

[0212] A first TCI state of the at least two TCI states may be identified / indicated by a first TCI state index. A second TCI state of the at least two TCI states may be identified / indicated by a second TCI state index. The plurality of TCI state indices may include the first TCI state. The plurality of TCI state indices may include the second TCI state index. At least one TCI state indicator / index of the plurality of TCI states may include the first TCI state indicator / index. At least one TCI state indicator / index of the plurality of TCI states may include the second TCI state indicator / index.

[0213] The at least two TCI states may be / include at least two unified TCI states, the first TCI state may be / include a first unified TCI state, and the second TCI state may be / include a second unified TCI state.

[0214] The first TCI state (e.g., TCI state 26) may be the first / starting / earliest / initial TCI state in a vector / set / list of at least two TCI states. The first TCI state may be the first / starting / earliest element in a vector / set / list of at least two TCI states. The first TCI state may be the first / starting / earliest TCI state of at least two TCI states in (or indicated by) a TCI code point. The location / position of the first TCI state may be the earliest / highest / lowest in a vector of at least two TCI states. The location / position of the first TCI state may be earlier (or before) than the location / position of the second TCI state in a vector of at least two TCI states. The first TCI state may occur first in a vector / set / list of at least two TCI states. The first / starting / earliest TCI state (or first TCI state) is, for example, TCI state 26 if a vector of at least two TCI states is equal to [TCI state 26, TCI state 61]. The first / starting / earliest TCI state (or first TCI state) is, for example, TCI state 2 if a vector of at least two TCI states is equal to [TCI state 2, TCI state 1].

[0215] The second TCI state (e.g., TCI state 61) may be the second / second starting / second earliest TCI state in a vector / set / list of at least two TCI states. The second TCI state may be the second / second starting / second earliest element in a vector / set / list of at least two TCI states. The second TCI state may be the second / second starting / second earliest TCI state of at least two TCI states in (or indicated by) a TCI code point. The location / position of the second TCI state may be the second earliest / second highest / second lowest in a vector of at least two TCI states. The location / position of the first TCI state may be earlier (or earlier) than the location / position of the second TCI state in a vector of at least two TCI states. The location / position of the second TCI state may be later (e.g., later) than the location / position of the first TCI state in a vector of at least two TCI states. The second TCI state may occur second in a vector / set / list of at least two TCI states. The second / second starting / second earliest TCI state (or second TCI state) is, for example, TCI state 61 if the vector of at least two TCI states is equal to [TCI state 26, TCI state 61]. The second / second starting / second earliest TCI state (or second TCI state) is, for example, TCI state 1 if the vector of at least two TCI states is equal to [TCI state 2, TCI state 1].

[0216] The DCI may schedule the transmission of a transport block (e.g., PDSCH, PUSCH). The DCI may include, for example, a downlink assignment indicating resources for the transport block. The DCI may include, for example, an uplink grant / assignment indicating resources for the transport block. The wireless device may transmit (e.g., transmit) the transport block via the resources.

[0217] The DCI may not schedule a transport block transmission (e.g., a PDSCH / PUSCH transmission). The DCI may not, for example, include a downlink allocation. The DCI may not, for example, include an uplink grant / allocation. The CRC for / its DCI may be scrambled with the RNTI (e.g., CS-RNTI). The RV field of the DCI may be set to (or may indicate or may be equal to) 1 (e.g., all "1s") by, for example, a base station. The MCS field of the DCI may be set to (or may indicate or may be equal to) one (e.g., all "1s") by, for example, a base station. The New Data Indicator (NDI) field of the DCI may be set to (or may indicate or may be equal to) zero by, for example, a base station. The FDRA field of the DCI may be set to (or may indicate or may be equal to) zero (e.g., all "0s"), for example, for FDRA type 0. The FDRA field of the DCI may be set to (or indicate or may be equal to) 1 (e.g., all "1's"), for example, for FDRA Type 1. The FDRA field of the DCI may be set to (or indicate or may be equal to) zero (e.g., all "0's"), for example, for a dynamic switch.

[0218] The wireless device may transmit (e.g., transmit) an uplink signal (e.g., a HARQ-ACK or a PUCCH with HARQ-ACK information) via a PUCCH resource. The wireless device may transmit (e.g., transmit) an uplink signal, for example, for a transport block scheduled by a DCI. The wireless device may transmit (e.g., transmit) an uplink signal, for example, in response to a DCI (e.g., when the DCI does not schedule transmission of a transport block).

[0219] The wireless device may, for example, determine the number of symbols (e.g., beam application time, MAC-CE activation time,

number

[0220] The wireless device may apply (or begin using) at least two TCI states (e.g., DCI1 at time T1 in FIG. 17) indicated / activated by an activation command starting from the starting / initial / earliest / first slot, for example, based on the number of one or more TCI code points being equal to 1.

[0221] The wireless device may apply (or begin using) at least two TCI states indicated / activated by a DCI starting from the starting / initial / earliest / first slot (e.g., at time T2 in FIG. 17) based, for example, on the number of one or more TCI code points being greater than one.

[0222] The at least two TCI states may be / include at least two uplink TCI states. The multiple uplink TCI states may include at least two uplink TCI states. The first TCI state may be / include a first uplink TCI state of the at least two uplink TCI states. The second TCI state may be / include a second uplink TCI state of the at least two uplink TCI states. The wireless device may apply / use at least two uplink TCI states, for example, for transmission of uplink signals (e.g., PUSCH transmission, PUCCH transmission, UCI, transport block, SRS, etc.) via the uplink BWP of the cell.

[0223] Using / applying at least two uplink TCI states for transmission of uplink signals may include transmitting (e.g., transmitting) one or more first uplink signals (e.g., PUSCH transmission, PUCCH transmission, UCI, transport block, SRS, etc.) using a first spatial-domain transmit filter / beam determined based on a first reference signal indicated by the first uplink TCI state. The first spatial-domain transmit / transmit filter / beam may be, for example, the same as (or substantially the same as, x-degree intervals, x=0, 1, 5, 10, etc.) the spatial-domain receive / receive filter / beam used to receive the first reference signal. The first spatial-domain transmit / transmit filter / beam may be, for example, the same as (or substantially the same as, x-degree intervals, x=0, 1, 5, 10, etc.) the spatial-domain transmit / transmit filter / beam used to transmit (e.g., transmit) the first reference signal. Using / adapting at least two uplink TCI states for transmission of uplink signals may include transmitting (e.g., transmitting) one or more first uplink signals at a first transmit power determined based on one or more first power control parameters (e.g., target received power, closed-loop index, path loss compensation factor, alpha, path loss reference signal, etc.) indicated by (or included in, associated with, or mapped to) a first uplink TCI state. The uplink signals may include one or more first uplink signals. Using / adapting at least two uplink TCI states for transmission of uplink signals may include transmitting (e.g., transmitting) one or more second uplink signals (e.g., PUSCH transmission, PUCCH transmission, UCI, transport block, SRS, etc.) using a second spatial-domain transmit filter / beam determined based on a second reference signal indicated by a second uplink TCI state. The second spatial domain transmit / transmit filter / beam may be, for example, the same as (or substantially the same as, x degree intervals, x=0, 1, 5, 10, etc.) the spatial domain receive / receive filter / beam used to receive the second reference signal.The second spatial-domain transmit / transmit filter / beam may be, for example, the same (or substantially the same, x degree intervals, x=0, 1, 5, 10, etc.) as the spatial-domain transmit / transmit filter / beam used to transmit (e.g., transmit) the second reference signal. Using / applying at least two uplink TCI states for transmission of uplink signals may include transmitting (e.g., transmitting) one or more second uplink signals at a second transmit power determined based on one or more second power control parameters (e.g., target received power, closed-loop index, path loss compensation factor, alpha, path loss reference signal, etc.) indicated by (or included in, associated with, or mapped to) the second uplink TCI state. The uplink signals may include one or more second uplink signals.

[0224] The at least two TCI states may be / include at least two downlink TCI states. The multiple downlink TCI states may include at least two downlink TCI states. The first TCI state may be / include a first downlink TCI state of the at least two downlink TCI states. The second TCI state may be / include a second downlink TCI state of the at least two downlink TCI states. The wireless device may apply / use at least two downlink TCI states, for example, for reception of downlink signals (e.g., PDSCH transmission / reception, PDCCH transmission / reception, CSI-RS, DMRS, etc.) via the cell's downlink BWP.

[0225] Using / applying at least two downlink TCI states for reception of downlink signals may include receiving one or more first downlink signals (e.g., PDSCH, PDCCH, CSI-RS, DMRS, etc.) using a first spatial-domain receive / receive filter / beam determined based on a first reference signal indicated by the first downlink TCI state. The first spatial-domain receive / receive filter / beam may be, for example, the same (or substantially the same, x-degree intervals, x=0, 1, 5, 10, etc.) as the spatial-domain receive / receive filter / beam used to receive the first reference signal. The first spatial-domain receive / receive filter / beam may be, for example, the same (or substantially the same, x-degree intervals, x=0, 1, 5, 10, etc.) as the spatial-domain transmit / transmit filter / beam used to transmit (e.g., transmit) the first reference signal. The downlink signals may include one or more first downlink signals. Using / applying at least two downlink TCI states for reception of downlink signals may include receiving one or more second downlink signals (e.g., PDSCH, PDCCH, CSI-RS, DMRS, etc.) using a second spatial-domain receive / receive filter / beam determined based on a second reference signal indicated by the second downlink TCI state. The second spatial-domain receive / receive filter / beam may be, for example, the same as (or substantially the same as, x-degree intervals, x=0, 1, 5, 10, etc.) the spatial-domain receive / receive filter / beam used to receive the second reference signal. The second spatial-domain receive / receive filter / beam may be, for example, the same as (or substantially the same as, x-degree intervals, x=0, 1, 5, 10, etc.) the spatial-domain transmit / transmit filter / beam used to transmit (e.g., transmit) the second reference signal. The downlink signals may include one or more second downlink signals.

[0226] Using / applying at least two downlink TCI states for reception of downlink signals may include a DM-RS (or DM-RS antenna port) of one or more first downlink signals (e.g., PDSCH, PDCCH, CSI-RS, DMRS, etc.) being quasi-co-located with a first reference signal indicated by the first downlink TCI state. The DM-RS (or DM-RS antenna port) of the one or more first downlink signals may be quasi-co-located with the first reference signal for a first quasi-co-location type (e.g., QCL Type A, QCL Type B, QCL Type C, QCL Type D, QCL Type E, etc.) indicated by the first downlink TCI state. Using / applying at least two downlink TCI states for reception of downlink signals may include a DM-RS (or DM-RS antenna port) of one or more second downlink signals (e.g., PDSCH, PDCCH, CSI-RS, DMRS, etc.) being quasi-co-located with a second reference signal indicated by a second downlink TCI state. The DM-RS (or DM-RS antenna ports) of one or more second downlink signals may be quasi-colocated with a second reference signal with respect to a second quasi-colocation type (e.g., QCL Type A, QCL Type B, QCL Type C, QCL Type D, QCL Type E, etc.) indicated by the second downlink TCI state.

[0227] Using / applying at least two downlink TCI states for reception of downlink signals may include one or more first downlink signals (e.g., CSI-RS, DMRS, etc.) being quasi-collocated with a first reference signal indicated by the first downlink TCI state. The one or more first downlink signals may be quasi-collocated with the first reference signal for a first quasi-collocation type indicated by the first downlink TCI state. Using / applying at least two downlink TCI states for reception of downlink signals may include one or more second downlink signals (e.g., CSI-RS, DMRS, etc.) being quasi-collocated with a second reference signal indicated by a second downlink TCI state. The one or more second downlink signals may be quasi-collocated with the second reference signal for a second quasi-collocation type indicated by the second downlink TCI state.

[0228] The at least two TCI states may be / include at least two common / joint TCI states (or at least two common / joint uplink and downlink TCI states). The multiple common / joint TCI states may include at least two common / joint TCI states. The first TCI state may be / include a first common / joint TCI state of the at least two common / joint TCI states. The second TCI state may be / include a second common / joint TCI state of the at least two common / joint TCI states. The wireless device may apply / use at least two common / joint TCI states, for example, for reception of downlink signals (e.g., PDSCH, PDCCH, CSI-RS, DMRS, etc.) via the downlink BWP of the cell. The wireless device may apply / use at least two common / joint TCI states, for example, for transmission of uplink signals (e.g., PUSCH, PUCCH, UCI, transport block, SRS, etc.) via the uplink BWP of the cell. A wireless device may apply / use at least two common / joint TCI states for receiving downlink signals and transmitting uplink signals.

[0229] Using / applying at least two common / joint TCI states for reception of downlink signals may include receiving one or more first downlink signals (e.g., PDSCH, PDCCH, CSI-RS, DMRS, etc.) using a first spatial-domain receive / receive filter / beam determined based on a first reference signal indicated by a first common / joint TCI state. The first spatial-domain receive / receive filter / beam may be, for example, the same (or substantially the same, x-degree intervals, x=0, 1, 5, 10, etc.) as the spatial-domain receive / receive filter / beam used to receive the first reference signal. The first spatial-domain receive / receive filter / beam may be, for example, the same (or substantially the same, x-degree intervals, x=0, 1, 5, 10, etc.) as the spatial-domain transmit / transmit filter / beam used to transmit (e.g., transmit) the first reference signal. The downlink signals may include one or more first downlink signals. Using / applying at least two common / joint TCI states for reception of downlink signals may include receiving one or more second downlink signals (e.g., PDSCH, PDCCH, CSI-RS, DMRS, etc.) using a second spatial-domain receive / receive filter / beam determined based on a second reference signal indicated by a second common / joint TCI state. The second spatial-domain receive / receive filter / beam may be, for example, the same as (or substantially the same as, x-degree intervals, x=0, 1, 5, 10, etc.) the spatial-domain receive / receive filter / beam used to receive the second reference signal. The second spatial-domain receive / receive filter / beam may be, for example, the same as (or substantially the same as, x-degree intervals, x=0, 1, 5, 10, etc.) the spatial-domain transmit / transmit filter / beam used to transmit (e.g., transmit) the second reference signal. The downlink signals may include one or more second downlink signals.

[0230] Using / applying at least two common / joint TCI states for reception of downlink signals may include a DMRS (or DM-RS antenna port) of one or more first downlink signals (e.g., PDSCH, PDCCH, CSI-RS, DMRS, etc.) being quasi-collocated with a first reference signal indicated by the first common / joint TCI state. A DM-RS (or DM-RS antenna port) of one or more first downlink signals may be quasi-collocated with the first reference signal for a first quasi-collocation type (e.g., QCL Type A, QCL Type B, QCL Type C, QCL Type D, QCL Type E, etc.) indicated by the first common / joint TCI state. Using / applying at least two common / joint TCI states for reception of downlink signals may include a DMRS (or DM-RS antenna port) of one or more second downlink signals (e.g., PDSCH, PDCCH, CSI-RS, DMRS, etc.) being quasi-collocated with a second reference signal indicated by a second common / joint TCI state. The DM-RS (or DM-RS antenna ports) of one or more second downlink signals may be quasi-colocated with a second reference signal with respect to a second quasi-colocation type (e.g., QCL Type A, QCL Type B, QCL Type C, QCL Type D, QCL Type E, etc.) indicated by a second common / joint TCI state.

[0231] Using / applying at least two common / joint TCI states for reception of downlink signals may include one or more first downlink signals (e.g., CSI-RS, DMRS, etc.) being quasi-collocated with a first reference signal indicated by the first common / joint TCI state. The one or more first downlink signals may be quasi-collocated with the first reference signal with respect to a first quasi-collocation type indicated by the first common / joint TCI state. Using / applying at least two common / joint TCI states for reception of downlink signals may include one or more second downlink signals (e.g., CSI-RS, DMRS, etc.) being quasi-collocated with a second reference signal indicated by a second common / joint TCI state. The one or more second downlink signals may be quasi-collocated with the second reference signal with respect to a second quasi-collocation type indicated by the second common / joint TCI state.

[0232] Using / applying at least two common / joint TCI states for transmission of uplink signals may include transmitting (e.g., transmitting) one or more first uplink signals (e.g., PUSCH transmission, PUCCH transmission, UCI, transport block, SRS, etc.) using a first spatial-domain transmit filter / beam determined based on a first reference signal indicated by a first common / joint TCI state. The first spatial-domain transmit / transmit filter / beam may be, for example, the same as (or substantially the same as, x-degree intervals, x=0, 1, 5, 10, etc.) the spatial-domain receive / receive filter / beam used to receive the first reference signal. The first spatial-domain transmit / transmit filter / beam may be, for example, the same as (or substantially the same as, x-degree intervals, x=0, 1, 5, 10, etc.) the spatial-domain transmit / transmit filter / beam used to transmit (e.g., transmit) the first reference signal. Using / applying at least two common / joint TCI states for transmission of uplink signals may include transmitting (e.g., transmitting) one or more first uplink signals at a first transmit power determined based on one or more first power control parameters (e.g., target received power, closed-loop index, path loss compensation factor, alpha, path loss reference signal, and the like) indicated by (or included in, associated with, or mapped to) a first common / joint TCI state. The uplink signals may include the one or more first uplink signals.

[0233] Using / applying at least two common / joint TCI states for transmission of uplink signals may include transmitting (e.g., transmitting) one or more second uplink signals (e.g., PUSCH transmission, PUCCH transmission, UCI, transport block, SRS, etc.) using a second spatial-domain transmit filter / beam determined based on a second reference signal indicated by a second common / joint TCI state. The second spatial-domain transmit / transmit filter / beam may be, for example, the same as (or substantially the same as, x-degree intervals, x=0, 1, 5, 10, etc.) the spatial-domain receive / receive filter / beam used to receive the second reference signal. The second spatial-domain transmit / transmit filter / beam may be, for example, the same as (or substantially the same as, x-degree intervals, x=0, 1, 5, 10, etc.) the spatial-domain transmit / transmit filter / beam used to transmit (e.g., transmit) the second reference signal. Using / applying at least two common / joint TCI states for transmission of uplink signals may include transmitting (e.g., transmitting) one or more second uplink signals at a second transmit power determined based on one or more second power control parameters (e.g., target received power, closed-loop index, path loss compensation factor, alpha, path loss reference signal, and the like) indicated by (or included in, associated with, or mapped to) a second common / joint TCI state. The uplink signals may include one or more second uplink signals.

[0234] 18 illustrates an example of an uplink repetition scheme. One or more wireless devices may repeat (transmit) an uplink signal (e.g., a PUSCH transmission, a transport block, a PUCCH transmission, uplink control information, HARQ-ACK, SR, CSI report, SRS) across / across / in multiple transmission / repetition opportunities. One or more wireless devices may transmit (e.g., transmit) repetitions of the uplink signal across / within / across / in multiple transmission opportunities.

[0235] One or more configuration parameters may indicate a repetition scheme (e.g., an FDM scheme, a TDM scheme, an SDM scheme, a CDM scheme). One or more wireless devices may, for example, repeat (transmit of) an uplink signal over / across / at multiple transmission / repetition opportunities based on the one or more configuration parameters indicating the repetition scheme. The wireless devices may, for example, transmit / transmit a transport block over (e.g., over, through, at) multiple uplink signal / channel transmission opportunities and with / using multiple transmit powers based on the one or more configuration parameters indicating the repetition scheme.

[0236] One or more wireless devices may receive a DCI scheduling / triggering transmission of an uplink signal. The DCI may indicate a repetition scheme (e.g., an FDM scheme, a TDM scheme, an SFN scheme, an SDM scheme, a CDM scheme). The DCI may include one or more fields indicating the repetition scheme (e.g., an SRI field, a TCI field, an antenna port field, a PUCCH resource indicator field, an SRS resource set indicator field, etc.). The one or more fields may be set / equal to one or more values ​​indicating the repetition scheme. Each field of the one or more fields may be set to a respective value of the one or more values. The one or more wireless devices may, for example, repeat (transmit) an uplink signal over / over / across multiple transmission / repetition opportunities based on the DCI indicating the repetition scheme. The wireless devices may, for example, transmit (e.g., transmit) repetitions of an uplink signal over / over / across multiple transmission opportunities based on the DCI indicating the repetition scheme.

[0237] The amount of repetition may be for repetition of the uplink signal over uplink resources (e.g., PUCCH resources, SRS resources, PUSCH resources). The repetition scheme may, for example, be (or may not be) a time domain repetition (e.g., TDM in FIG. 18). The repetition scheme may, for example, be (or may not be) a frequency domain repetition (e.g., FDM in FIG. 18). The repetition scheme may, for example, be (or may not be) a code / spatial domain repetition (e.g., SDM / SFN in FIG. 18).

[0238] The repetition of the uplink signal may be, for example, time-domain repetition (e.g., TDM, TDMSchemeA, and TDMSchemeB in FIG. 18). In time-domain repetition, the multiple transmission opportunities may not overlap in time. Each transmission opportunity among the multiple transmission opportunities may have a non-overlapping time-domain resource allocation with respect to other transmission opportunities among the multiple transmission opportunities. A first uplink signal / channel transmission opportunity among the multiple uplink signal / channel transmission opportunities may not overlap in time with a second signal / channel transmission opportunity among the multiple uplink signal / channel transmission opportunities. The first uplink signal / channel transmission opportunity and the second uplink signal / channel transmission opportunity may be different. In the time domain, the multiple transmission opportunities may or may not overlap in frequency. The multiple transmission opportunities may include a first TX opportunity, a second TX opportunity, a third TX opportunity, and a fourth TX opportunity in time-domain repetition (e.g., FIG. 18). In time-domain repetition, the repetition of the uplink signal may be / occur, for example, in time units (e.g., TDM-ed). A wireless device may repeat transmission of an uplink signal, for example, over / throughout / within a time unit. One or more wireless devices may transmit (e.g., transmit) repetitions of an uplink signal, for example, over / across / across time units. The time units may, for example, be contiguous. The time units may, for example, not be contiguous (e.g., may have a time / symbol / slot gap). The number / quantity of time units may be equal to the number / quantity of repetitions of the uplink signal. The time unit may, for example, be a time slot. The time unit may, for example, be a minislot. The time unit may, for example, be a time symbol (e.g., an OFDM symbol). The time unit may, for example, be a subframe. The time unit may, for example, be an actual / nominal repetition. Multiple transmission opportunities may / may occur in a time unit. For example, a first transmission opportunity of a multiple transmission opportunities may / may occur in a first time unit of a time unit. A second transmission opportunity of a multiple transmission opportunities may / may occur in a second time unit of a time unit, and / or the like.The first time unit may be different from the second time unit. The first time unit may not overlap in time with the second time unit.

[0239] The uplink signal repetition may be, for example, frequency domain repetition (e.g., FDM, FDMSchemeA, FDMSchemeB, etc., of FIG. 18). In frequency domain repetition, the multiple transmission opportunities may or may not overlap in time. In frequency domain repetition, the multiple transmission opportunities may not overlap in frequency. Each transmission opportunity among the multiple transmission opportunities may have a non-overlapping frequency domain resource allocation with respect to other transmission opportunities among the multiple transmission opportunities. A first uplink signal / channel transmission opportunity among the multiple uplink signal / channel transmission opportunities may not overlap in frequency with a second signal / channel transmission opportunity among the multiple uplink signal / channel transmission opportunities. The first transmission opportunity and the second transmission opportunity may overlap in time. The first uplink signal / channel transmission opportunity and the second uplink signal / channel transmission opportunity may be different. The multiple transmission opportunities may include a first TX opportunity and a second TX opportunity in frequency domain repetition (e.g., FIG. 18). In frequency domain repetition, the repetition of the uplink signal may be / occur, for example, in frequency units (e.g., frequencies, resource blocks (RBs), physical resource blocks (PRBs), frequency bands, subbands, bandwidth portions, cells). One or more wireless devices may, for example, repeat transmission of the uplink signal across / across / in the frequency units. One or more wireless devices may, for example, transmit (e.g., transmit) repetitions of the uplink signal across / across / in the frequency units. The frequency units may, for example, be contiguous. The frequency units may, for example, not be contiguous (e.g., may have frequency / PRB / RB gaps). The number / amount of frequency units may be equal to the number / amount of repetitions of the uplink signal. The frequency unit may, for example, be a frequency band. The frequency unit may, for example, be a PRB (or RB). The frequency unit may, for example, be a BWP. The frequency unit may, for example, be a cell. Multiple transmission opportunities may be / occur in frequency units. For example, a first transmission opportunity of the multiple transmission opportunities may be / occur in a first frequency unit of the frequency units.A second transmission opportunity of the plurality of transmission opportunities may be / occur in a second frequency unit of a frequency unit, etc. The first frequency unit and the second frequency unit may be different. The first frequency unit and the second frequency unit may not overlap in frequency.

[0240] The uplink signal repetition may be, for example, code / spatial domain repetition (e.g., SDM / SFN of FIG. 18, an SDM scheme, a CDM scheme, an SDM scheme, a CDMS scheme, etc.). In code / spatial domain repetition, the multiple transmission opportunities may not overlap in time. In code / spatial domain repetition, the multiple transmission opportunities may not overlap in frequency. In code / spatial domain repetition, the multiple transmission opportunities may be transmission opportunities (e.g., or single transmission opportunities). Each transmission opportunity of the multiple transmission opportunities may be the same (or the same as the transmission opportunity or single transmission opportunity). Each transmission opportunity of the multiple transmission opportunities may have a frequency-domain resource allocation that overlaps with respect to other transmission opportunities of the multiple transmission opportunities. Each transmission opportunity of the multiple transmission opportunities may have a time-domain resource allocation that overlaps with respect to other transmission opportunities of the multiple transmission opportunities. A first uplink signal / channel transmission opportunity of the multiple uplink signal / channel transmission opportunities may overlap in time / frequency with a second signal / channel transmission opportunity of the multiple uplink signal / channel transmission opportunities. The first transmission opportunity (e.g., first TX opportunity) and the second transmission opportunity (e.g., second TX opportunity) may be the same. The multiple transmission opportunities are first TX opportunities and second TX opportunities in a code / space domain repetition (e.g., FIG. 18). The first TX opportunity and second TX opportunity may be the same in a code / space domain repetition (e.g., overlap in time and frequency). In a code / space domain repetition, the multiple transmission opportunities may occur in the same frequency unit (e.g., frequency, RB, PRB, frequency band, bandwidth portion, cell). The first frequency unit of the first signal / channel transmission opportunity and the second frequency unit of the second signal / channel transmission opportunity may overlap in frequency. The first frequency unit of the first transmission opportunity and the second frequency unit of the second transmission opportunity may be the same. The multiple transmission opportunities may occur in the same time unit (e.g., symbol, actual / nominal repetition, minislot, slot, subframe, etc.). The first time unit of the first signal / channel transmission opportunity and the second time unit of the second signal / channel transmission opportunity may overlap in time.The first time unit of the first transmit opportunity and the second time unit of the second transmit opportunity may be the same.

[0241] A wireless device may receive a DCI, for example, from a base station. The DCI may trigger / indicate / activate / schedule transmission of information such as a CSI report (e.g., an aperiodic CSI report, a semi-persistent CSI report) and / or any other information. The DCI may schedule repetitions of a PUSCH transmission. The wireless device may transmit (e.g., transmit) repetitions of a PUSCH transmission to at least one TRP. For example, the wireless device may transmit (e.g., transmit) a first repetition of a PUSCH transmission to a first TRP or a first computing device. The wireless device may transmit (e.g., transmit) a second repetition of a PUSCH transmission to a second TRP or a second computing device. Repetitions of uplink transmissions (e.g., PUSCH transmissions) may be, for example, in the time domain. Repetitions of PUSCH transmissions may be time-domain repetitions.

[0242] The wireless device may receive one or more messages including one or more configuration parameters, which may include a CSI multiplexing mode parameter, which may be enabled (configured).

[0243] In at least some wireless communications, a wireless device may transmit (e.g., the CSI report (or other information)) for the PUSCH transmission (e.g., a first repetition (or first transmit opportunity) of the PUSCH transmission and a second repetition (or second transmit opportunity) of the PUSCH transmission. The method includes receiving the CSI multiplexing mode parameter based on the CSI multiplexing mode parameter set based on the one or more configuration parameters, e.g., where the CSI multiplexing mode parameter set is enabled. The wireless device may transmit (e.g., transmit) the first repetition of the PUSCH transmission at the first transmit opportunity. The wireless device may transmit (e.g., transmit) the second repetition of the PUSCH transmission at the second transmit opportunity. The first repetition may include the first repetition. The first repetition may be the earliest / starting / first / initial repetition of the first repetition. The second repetition may include the second repetition. The second repetition may be the earliest / starting / first / initial repetition of the second repetition.

[0244] The one or more configuration parameters may not include a CSI multiplexing mode parameter (or may not include an enabled CSI multiplexing mode parameter). The one or more configuration parameters may include a disabled (or not enabled) CSI multiplexing mode parameter set. In at least some wireless communications, a wireless device may transmit (e.g., transmit) a CSI report (or other information) in a first repetition of a PUSCH transmission (or a first transmit opportunity) based on, for example, one or more configuration parameters that do not include an enabled CSI multiplexing mode parameter set. The wireless device may transmit (e.g., transmit) the first repetition of a PUSCH transmission in the first transmit opportunity. The wireless device may not transmit (e.g., transmit) / multiplex a CSI report in a second repetition of a PUSCH transmission (or a second transmit opportunity) based on, for example, one or more configuration parameters that do not include an enabled CSI multiplexing mode parameter set. The wireless device may not transmit (e.g., transmit) the second repetition of a PUSCH transmission in the second transmit opportunity. The repetition of a PUSCH transmission may include the first repetition. The first repetition may be the earliest / starting / first / initial repetition of the PUSCH transmission repetitions.

[0245] The repetition of the uplink transmission (e.g., PUSCH transmission) may be, for example, the frequency domain. The repetition of the PUSCH transmission may be a frequency domain repetition. The repetition of the uplink transmission (e.g., PUSCH transmission) may start at the same time / symbol (or at the same time), for example, based on the repetition being in the frequency domain. The first repetition of the PUSCH transmission may start at a first symbol. The second repetition of the PUSCH transmission may start at a second symbol. The first symbol and the second symbol may be the same (or substantially similar), for example, based on the repetition being in the frequency domain. In at least some wireless communications, transmitting (e.g., transmitting) a CSI report (or other information) at the earliest / starting / first / initial / first repetition of the PUSCH transmission repetition may not be efficient for the frequency domain repetition, for example, based on the PUSCH transmission repetition starting at the same time / symbol in the frequency domain repetition. Each repetition of the PUSCH transmission repetition may be the earliest / starting / first / first repetition of the PUSCH transmission repetition. A base station may not receive / decode a repetition of a PUSCH transmission if, for example, the base station and the wireless device are not aligned with the PUSCH transmission repetition on which the CSI report (or other information) is transmitted / multiplexed. For example, a wireless device may transmit (e.g., transmit) / multiplex a CSI report (or other information) in the first repetition of a PUSCH transmission. The wireless device may not transmit (e.g., transmit) / multiplex a CSI report (or other information) in the second repetition of a PUSCH transmission. The base station may not have information regarding the repetition on which the wireless device transmits (e.g., transmits) / multiplexes a CSI report (or other information). The base station may decode one / each of the PUSCH transmission repetitions under two different assumptions (e.g., 1) the repetition is multiplexed with a CSI report (or other information), and 2) the CSI report is not multiplexed in the repetition). This behavior of the base station may increase power consumption at the base station.

[0246] As described herein, transmission / multiplexing of CSI reports (or other information) for / in frequency domain repetitions may be enhanced, for example, by aligning the operations of a base station and a wireless device. A wireless device may repeatedly transmit (e.g., transmit) / multiplex a CSI report (or other information) in a PUSCH transmission repetition based on rules such as transmitting / transmitting at the lowest / highest starting / ending frequency / resource block (RB). A wireless device may repeatedly transmit (e.g., transmit) / multiplex a CSI report (or other information) in a PUSCH transmission repetition transmitted (e.g., transmitted) at the antenna panel with the lowest / highest antenna panel index / identifier. A wireless device may repeatedly transmit (e.g., transmit) / multiplex a CSI report (or other information) in a PUSCH transmission repetition transmitted (e.g., transmitted) based on the TCI state (e.g., transmit beam) with the lowest TCI state index. The wireless device may repeatedly transmit (e.g., transmit) / multiplex a CSI report (or other information) among the repetitions of the PUSCH transmissions that are transmitted (e.g., transmitted) based on the first TCI state (or first SRS resource set).

[0247] A wireless device may transmit (e.g., transmit) / multiplex a CSI report (or other information) in multiple repetitions of a PUSCH transmission in the frequency domain. The wireless device may transmit (e.g., transmit) / multiplex a CSI report (or other information) in each repetition of a PUSCH transmission in the frequency domain. Transmitting (e.g., transmit) / multiplexing a CSI report (or other information) in each repetition of a PUSCH transmission may increase robustness and diversity. In the frequency domain repetition, the wireless device may not determine / check whether one or more configuration parameters include a CSI multiplex mode parameter (or other parameter) that is set to enabled or not. In the frequency domain repetition, the wireless device may transmit (e.g., transmit) / multiplex a CSI report (or other information) in each repetition of a PUSCH transmission, regardless of whether the CSI multiplex mode parameter (or other parameter) is enabled or not. In the time domain repetition, the wireless device may determine / check whether one or more configuration parameters include a CSI multiplex mode parameter (or other parameter) that is enabled or not. In time domain repetition, the wireless device may transmit (e.g., transmit) / multiplex a CSI report (or other information) in each repetition of the PUSCH transmission repetition based on whether one or more configuration parameters, including a CSI multiplex mode parameter (or other parameters), are enabled.

[0248] The embodiments described herein may provide advantages, such as by helping to align a base station and a wireless device over one or more iterations in which the wireless device transmits (e.g., transmits) / multiplexes a CSI report (or other information). This alignment may achieve advantages, such as reduced power consumption at the base station, increased probability of successful decoding of a PUSCH transmission, and / or other advantages apparent from the description herein.

[0249] FIG. 19 shows an example of report multiplexing. The one or more configuration parameters may indicate at least two SRS resource sets. The at least two SRS resource sets may include a first SRS resource set and a second SRS resource set. The one or more configuration parameters may include an enabled parameter. The one or more configuration parameters may include, for example, respective usage parameters for the SRS resource set (e.g., each SRS resource set of the at least two SRS resource sets). The usage parameters may be configured in a codebook. The usage parameters for the SRS resource set (e.g., each SRS resource set of the at least two SRS resource sets) may be configured in a codebook. The one or more configuration parameters may indicate, for example, a codebook for the SRS resource set (e.g., each SRS resource set of the at least two SRS resource sets). The one or more configuration parameters may indicate a codebook (or usage parameters configured in the codebook) for the first SRS resource set. The one or more configuration parameters may indicate a codebook (or usage parameters configured in the codebook) for the second SRS resource set.

[0250] The usage parameters may be set to a non-codebook. The usage parameters of an SRS resource set (e.g., each SRS resource set of at least two SRS resource sets) may be set to a non-codebook. One or more configuration parameters may, for example, indicate a non-codebook for an SRS resource set (e.g., each SRS resource set of at least two SRS resource sets). One or more configuration parameters may indicate a non-codebook (or usage parameters set to a non-codebook) for a first SRS resource set. One or more configuration parameters may indicate a non-codebook (or usage parameters set to a non-codebook) for a second SRS resource set.

[0251] The one or more configuration parameters may indicate at least two SRS resource set indexes for the at least two SRS resource sets. The one or more configuration parameters may indicate a respective SRS resource set index (e.g., at least two SRS resource set indexes) for the SRS resource set (e.g., each SRS resource set of the at least two SRS resource sets). The SRS resource set (e.g., each SRS resource set of the at least two SRS resource sets) may be identified / indicated by a respective SRS resource set index (e.g., at least two SRS resource set indexes). A first SRS resource set of the one or more SRS resource sets may be indicated / identified by a first SRS resource set indicator / index among the SRS resource set indicators / indexes. A second SRS resource set of the one or more SRS resource sets may be indicated / identified by a second SRS resource set indicator / index among the SRS resource set indicators / indexes. The first SRS resource set index of the first SRS resource set may be lower than the second SRS resource set index of the second SRS resource set.

[0252] One or more wireless devices may receive a DCI (e.g., at T0 in FIG. 19). The DCI may be, for example, DCI format 0_1. The DCI may be, for example, DCI format 0_2. The DCI may be, for example, DCI format 0_x, where x = 0, 1, 2, 3, .... The DCI (e.g., at time T0 in FIG. 19) may be, for example, the same as the DCI indicating the activation of at least two TCI states (e.g., at time T2 in FIG. 17). The DCI (e.g., at time T0 in FIG. 19) may be different from the DCI indicating the activation of at least two TCI states (e.g., at time T2 in FIG. 17).

[0253] The DCI may schedule / trigger / activate transmission of a CSI report. The CSI report may be, for example, an aperiodic CSI report. The DCI may include a CSI request field scheduling / triggering transmission of the aperiodic CSI report. The CSI report may be, for example, a semi-persistent CSI report. The DCI may include a CSI request field that activates transmission of the semi-persistent CSI report. The CSI report may be, for example, a single CSI report. The CSI report may be, for example, multiple CSI reports. The CSI report may be, for example, one or more CSI reports.

[0254] The DCI may include at least one field (e.g., an SRS resource set indicator, a TCI field, a unified TCI status field, a TRP indicator field, and / or the like). The field may indicate, for example, multiple TRP uplink repetition (e.g., multiple TRP PUSCH repetition, multiple TRP PUCCH repetition). The value of the field may indicate multiple TRP uplink repetition. The value of the field may indicate multiple TRP PUSCH repetition. The value of the field may indicate multiple TRP PUCCH repetition. The size / length of the field may be, for example, 2 bits (or any other bit amount). For example, the value of the field (e.g., SRS resource set indicator) may be equal to '10' or any other value. For example, the value of the field (e.g., SRS resource set indicator) may be equal to '11'. The size / length of the field may be, for example, 1 bit. For example, the value of the field (e.g., SRS resource set indicator) may be equal to '1'.

[0255] The DCI may schedule repetitions of an uplink transmission. For example, the DCI may schedule repetitions of a PUSCH transmission. The wireless device may transmit (e.g., transmit) repetitions of an uplink transmission (e.g., a PUSCH transmission) at multiple transmit opportunities. The wireless device may transmit (e.g., transmit) at least one repetition of the uplink transmission (e.g., each repetition of a PUSCH transmission) at each transmit opportunity of the multiple transmit opportunities. The wireless device may transmit (e.g., transmit) a first repetition of the repetition of the PUSCH transmission at a first transmit opportunity of the multiple transmit opportunities. The wireless device may transmit (e.g., transmit) a second repetition of the repetition of the PUSCH transmission at a second transmit opportunity of the multiple transmit opportunities.

[0256] A repetition of a PUSCH transmission may be associated with at least two SRS resource sets. One or more first repetitions of a PUSCH transmission may be associated with a first SRS resource set of the at least two SRS resource sets. One or more second repetitions of a PUSCH transmission may be associated with a second SRS resource set of the at least two SRS resource sets. A repetition of a PUSCH transmission may be associated with at least two SRS resource sets, for example, based on a value of a field (e.g., an SRS resource set indicator) being equal to '10' (or any other value). A repetition of a PUSCH transmission may be associated with at least two SRS resource sets, for example, based on a value of a field (e.g., an SRS resource set indicator) being equal to '11' (or any other value). A repetition of a PUSCH transmission may be associated with at least two SRS resource sets, for example, based on a value of a field (e.g., an SRS resource set indicator) indicating multiple TRP uplink repetitions.

[0257] The PUSCH transmission may, for example, include / carry (or may have) a transport block. The PUSCH transmission may, for example, not include / carry (or have) a transport block. The wireless device may determine / assume the number of repetitions of the PUSCH transmission as (or equal to) 2, for example, based on the PUSCH transmission not including / carrying a transport block. The wireless device may determine / assume the number of repetitions of the PUSCH transmission as (or equal to) 2, for example, based on the PUSCH transmission not having a transport block. The wireless device may determine / assume the number of repetitions of the PUSCH transmission as (or equal to) 2, for example, based on the PUSCH transmission not having a transport block. The wireless device may determine / assume the number of repetitions of the PUSCH transmission as 2, regardless of the value of the higher layer (e.g., RRC) parameter numberOfRepetitions or the value of the higher layer parameter pusch-AggregationFactor. The one or more configuration parameters may, for example, include the higher layer parameter numberOfRepetitions. The one or more configuration parameters may, for example, include the higher layer parameter pusch-AggregationFactor.

[0258] The one or more configuration parameters may include a CSI multiplexing mode parameter. The CSI multiplexing mode parameter may be enabled (configured). The CSI multiplexing mode parameter may indicate whether transmission (e.g., transmission) of a CSI report for at least two repetitions of PUSCH transmission is enabled. The at least two repetitions of PUSCH transmission may be in the time domain (e.g., TDM in FIG. 18), for example. The CSI multiplexing mode parameter may be used / applied to the time domain repetition (e.g., TDM in FIG. 18). The at least two repetitions of PUSCH transmission may be in the frequency domain (e.g., FDM in FIG. 18), for example. The CSI multiplexing mode parameter may be used / applied to the frequency domain repetition (e.g., FDM in FIG. 18). The at least two repetitions of PUSCH transmission may not be in the frequency domain (e.g., FDM in FIG. 18), for example. The CSI multiplexing mode parameter may not be used / applied to the frequency domain repetition (e.g., FDM in FIG. 18). The at least two repetitions of the PUSCH transmission may be associated with at least two SRS resource sets. A first repetition of the at least two repetitions of the PUSCH transmission may be associated with a first SRS resource set of the at least two SRS resource sets. A second repetition of the at least two repetitions of the PUSCH transmission may be associated with a second SRS resource set of the at least two SRS resource sets.

[0259] The CSI multiplexing mode parameter may be, for example, an aperiodic CSI multiplexing mode (or AP-CSI multiplexing mode) parameter. The CSI-AperiodicTriggerStateList parameter / IE may include an aperiodic-CSI-MultiplexingMode parameter. One or more configuration parameters may include / indicate the CSI-AperiodicTriggerStateList parameter / IE.

[0260] The CSI multiplexing mode parameter may be, for example, a semi-persistent CSI multiplexing mode (or SP-CSI multiplexing mode) parameter. The CSI-SemiPersistentOnPUSCH-TriggerStateList parameter / IE may include a semi-persistent-CSI-MultiplexingMode parameter. One or more configuration parameters may include / indicate a CSI-SemiPersistentOnPUSCH-TriggerStateList parameter / IE.

[0261] One or more wireless devices may send (e.g., transmit) a message such as a capability message (e.g., a UE capability message). The message (e.g., a UE capability message) may indicate, for example, support for transmitting (e.g., transmitting) a CSI report (or other information) in / on at least two repetitions of an uplink transmission (e.g., a PUSCH transmission). The capability message may indicate, for example, support for transmitting (e.g., transmitting) a CSI report (or other information) in / on at least two transmit opportunities of at least two repetitions of a PUSCH transmission. The capability message may indicate, for example, support for multiplexing a CSI report in / on at least two repetitions of a PUSCH transmission. The one or more configuration parameters may include, for example, a CSI multiplex mode parameter (or a CSI multiplex mode parameter set to valid) based on the capability message indicating support for transmitting (e.g., transmitting) / multiplexing a CSI report in / on at least two repetitions (or at least two transmit opportunities) of a PUSCH transmission.

[0262] The one or more configuration parameters may include a CSI multiplexing FDM mode parameter (or a CSI-FDM multiplexing mode parameter or a CSI-frequency multiplexing mode parameter, etc.). The CSI multiplexing FDM mode parameter may be enabled (configured). The CSI multiplexing FDM mode parameter may be different from, for example, the CSI multiplexing mode parameter.

[0263] The CSI multiplexing FDM mode parameter may indicate whether transmitting (e.g., transmitting) a CSI report (or other information) for at least two repetitions of the PUSCH transmission is enabled. The at least two repetitions of the PUSCH transmission are in the frequency domain (e.g., FIG. 18). The CSI multiplexing FDM mode parameter is in the frequency domain (e.g., FIG. 18). The at least two repetitions of the PUSCH transmission may be associated with at least two SRS resource sets. A first repetition of the at least two repetitions of the PUSCH transmission may be associated with a first SRS resource set of the at least two SRS resource sets. A second repetition of the at least two repetitions of the PUSCH transmission may be associated with a second SRS resource set of the at least two SRS resource sets.

[0264] The CSI multiplexing-FDM mode parameter may be, for example, an aperiodic-CSI multiplexing-FDM mode (or AP-CSI-multiplexing-FDM mode) parameter. The CSI-AperiodicTriggerStateList parameter / IE may include an aperiodic-CSI-Multiplexing-FDM-Mode parameter. One or more configuration parameters may include / indicate the CSI-AperiodicTriggerStateList parameter / IE.

[0265] The CSI multiplexing FDM mode parameter may be, for example, a semi-persistent CSI multiplexing FDM mode (or SP-CSI multiplexing FDM mode) parameter. The CSI-SemiPersistentOnPUSCH-TriggerStateList parameter / IE may include a semi-persistent CSI-Multiplexing-FDM-Mode parameter. One or more configuration parameters may include / indicate a CSI-SemiPersistentOnPUSCH-TriggerStateList parameter / IE.

[0266] One or more wireless devices may transmit (e.g., transmit) a message such as, for example, a UE capability message. The message (e.g., UE capability message) may indicate, for example, support for transmitting (e.g., transmitting) a CSI report in / on at least two repetitions of an uplink transmission (e.g., a PUSCH transmission). The at least two repetitions of a PUSCH transmission are in the frequency domain (e.g., FIG. 18). The capability message may indicate, for example, support for transmitting (e.g., transmitting) a CSI report in / on at least two transmission opportunities of the at least two repetitions of a PUSCH transmission. The capability message may indicate, for example, support for multiplexing a CSI report in / on at least two repetitions of a PUSCH transmission. The one or more configuration parameters may include, for example, a CSI multiplexing-FDM mode parameter (or the CSI multiplexing-FDM mode parameter set to be enabled) based on the capability message indicating support for transmitting (e.g., transmitting) / multiplexing a CSI report in / on at least two repetitions (or at least two transmission opportunities) of a PUSCH transmission.

[0267] One or more of the configuration parameters may not include a CSI multiplexing mode parameter (e.g., AP-CSI multiplexing mode, SP-CSI multiplexing mode). One or more of the configuration parameters may not include an enabled CSI multiplexing mode parameter set.

[0268] One or more wireless devices may send (e.g., transmit) a message such as, for example, a UE capability message. The message (e.g., UE capability message) may not indicate support for transmitting (e.g., transmitting) a CSI report in / on at least two repetitions of an uplink transmission (e.g., a PUSCH transmission). The capability message may not indicate support for transmitting (e.g., transmitting) a CSI report in / on at least two transmit opportunities of at least two repetitions of a PUSCH transmission. The capability message may not indicate support for multiplexing a CSI report in / on at least two repetitions of a PUSCH transmission. The one or more configuration parameters may not include a CSI multiplex mode parameter (or a CSI multiplex mode parameter set to valid), for example, based on a capability message that does not indicate support for transmitting (e.g., transmitting) / multiplexing a CSI report in / on at least two repetitions (or at least two transmit opportunities) of a PUSCH transmission.

[0269] One or more configuration parameters may not include a CSI multiplexing-FDM mode (e.g., AP-CSI-multiplexing-FDM mode, SP-CSI-multiplexing-FDM mode). One or more configuration parameters may not include an enabled CSI multiplexing-FDM mode parameter set.

[0270] One or more wireless devices may transmit (e.g., transmit) a message, such as, for example, a UE capability message. The message (e.g., UE capability message) may not indicate support for transmitting (e.g., transmitting) a CSI report in / on at least two repetitions of an uplink transmission (e.g., a PUSCH transmission). The at least two repetitions of a PUSCH transmission are in the frequency domain (e.g., FIG. 18). The UE capability message may not indicate support for transmitting (e.g., transmitting) a CSI report in / on at least two transmit opportunities of the at least two repetitions of a PUSCH transmission. The capability message may not indicate support for multiplexing a CSI report in / on at least two repetitions of a PUSCH transmission. The one or more configuration parameters may not include, for example, a CSI multiplex FDM mode parameter (or an enabled CSI multiplex FDM mode parameter set) based on a capability message that does not indicate support for transmitting (e.g., transmitting) / multiplexing a CSI report in / on at least two repetitions (or at least two transmit opportunities) of a PUSCH transmission.

[0271] One or more configuration parameters may indicate the amount of repetitions. The repetition scheme may be (or may be set to) frequency domain repetition (e.g., frequency domain multiplexing (FDM) repetition). The repetition of uplink transmissions (e.g., PUSCH transmissions) may be in the frequency domain. The repetition of uplink transmissions (e.g., PUSCH transmissions) may be in the frequency domain, for example, based on one or more configuration parameters indicating a repetition scheme that is (or is set to be) frequency domain repetition. The repetition of PUSCH transmissions may include a first repetition (e.g., repetition 1 in FIG. 19) and a second repetition (repetition 2 in FIG. 19). The first repetition and the second repetition may overlap in time (e.g., completely in time, partially in time, by at least one symbol). The start symbol of the first repetition and the start symbol of the second repetition may be the same, for example. The end symbol of the first repetition and the end symbol of the second repetition may be the same, for example. The first repetition and the second repetition may not overlap in frequency. The first repetition and the second repetition may be different frequencies (or different RBs or different PRBs). The first repetition and the second repetition may not overlap in at least one RB (or PRB).

[0272] The one or more first repetitions of the PUSCH transmission may include the first repetition (e.g., repetition 1 in FIG. 19 ). The first repetition may be associated with a first SRS resource set of the at least two SRS resource sets. The wireless device may transmit (e.g., transmit) the first repetition of the PUSCH transmission based on, for example, the first SRS resource set. The wireless device may transmit (e.g., transmit) the first repetition of the PUSCH transmission based on, for example, a first SRS resource in the first SRS resource set. The one or more configuration parameters may indicate a first number of SRS ports (e.g., nrofSRS-PORTs) for the first SRS resource. The wireless device may transmit (e.g., transmit) the first repetition of the PUSCH transmission based on, for example, the first number of SRS ports of the first SRS resource in the first SRS resource set. For example, the wireless device may transmit (e.g., transmit) the first repetition using a first transmit precoder determined based on the first number of SRS ports.

[0273] The one or more second repetitions of the PUSCH transmission may include a second repetition (e.g., repetition 2 in FIG. 19 ). The second repetition may be associated with a second SRS resource set of the at least two SRS resource sets. The wireless device may transmit (e.g., transmit) the second repetition of the PUSCH transmission based on, for example, the second SRS resource set. The wireless device may transmit (e.g., transmit) the second repetition of the PUSCH transmission based on, for example, a second SRS resource in the second SRS resource set. The one or more configuration parameters may indicate a second number of SRS ports (e.g., nrofSRS-PORTs) for the second SRS resource. The wireless device may transmit (e.g., transmit) the second repetition of the PUSCH transmission based on, for example, the second number of SRS ports of the second SRS resource in the second SRS resource set. For example, the wireless device may transmit (e.g., transmit) the second repetition using a second transmit precoder determined based on the second number of SRS ports.

[0274] One or more wireless devices may transmit (e.g., transmit) a first iteration of a repetition of a PUSCH transmission (e.g., repetition 1 of FIG. 19) at a first transmit opportunity (e.g., first TX opportunity of FIG. 19) of the multiple transmit opportunities (e.g., at time T1 of FIG. 19). The wireless device may transmit (e.g., transmit) a second iteration of a repetition of a PUSCH transmission (e.g., repetition 2 of FIG. 19) at a second transmit opportunity (e.g., second TX opportunity of FIG. 19) of the multiple transmit opportunities (e.g., at time T1 of FIG. 19).

[0275] One or more wireless devices may transmit (e.g., transmit) a first repetition of a PUSCH transmission based on a first TCI state (e.g., TCI state 26 in FIG. 17 ) of the at least two TCI states. The one or more wireless devices may transmit (e.g., transmit) the first repetition of a PUSCH transmission using a first spatial-domain transmit filter / beam determined based on a first reference signal indicated by the first TCI state. The first spatial-domain transmit / transmit filter / beam may be, for example, the same as (or substantially the same as, x-degree intervals, x=0, 1, 5, 10, etc.) the spatial-domain receive / receive filter / beam used to receive the first reference signal. The first spatial-domain transmit / transmit filter / beam may be, for example, the same as (or substantially the same as, x-degree intervals, x=0, 1, 5, 10, etc.) the spatial-domain transmit / transmit filter / beam used to transmit (e.g., transmit) the first reference signal.

[0276] The one or more wireless devices may transmit (e.g., transmit) a first repetition of a PUSCH transmission at a first transmit power determined based on one or more first power control parameters (e.g., target received power, closed-loop index, path loss compensation factor, alpha, path loss reference signal, and / or the like) indicated by (or included in, associated with, or mapped to) the first TCI state. The one or more configuration parameters may indicate the one or more first power control parameters for the first TCI state.

[0277] The one or more wireless devices may transmit (e.g., transmit) a second repetition of the PUSCH transmission based on a second TCI state (e.g., TCI state 61 in FIG. 17) of the at least two TCI states. The one or more wireless devices may transmit (e.g., transmit) the second repetition of the PUSCH transmission with a second spatial-domain transmit filter / beam determined based on a second reference signal indicated by the second TCI state. The second spatial-domain transmit / transmit filter / beam may be, for example, the same as (or substantially the same as, x-degree intervals, x=0, 1, 5, 10, etc.) the spatial-domain receive / receive filter / beam used to receive the second reference signal. The second spatial-domain transmit / transmit filter / beam may be, for example, the same as (or substantially the same as, x-degree intervals, x=0, 1, 5, 10, etc.) the spatial-domain transmit / transmit filter / beam used to transmit (e.g., transmit) the second reference signal.

[0278] The one or more wireless devices may transmit (e.g., transmit) a second repetition of the PUSCH transmission at a second transmit power determined based on one or more second power control parameters (e.g., target received power, closed-loop index, path loss compensation factor, alpha, path loss reference signal, and / or the like) indicated by (or included in, associated with, or mapped to) the second TCI state. The one or more configuration parameters may indicate the second TCI state for the second core set.

[0279] One or more wireless devices may be equipped with multiple antenna panels. The multiple antenna panels may include a first antenna panel and a second antenna panel. The first antenna panel may be identified / indicated by a first antenna panel index / identifier. One or more configuration parameters may indicate the first antenna panel indicator / index for the first antenna panel. For example, one or more wireless devices may transmit (e.g., transmit) an uplink signal (e.g., beam report, CSI report, UE capability message, PUCCH transmission) indicating the first antenna panel index for the first antenna panel. The second antenna panel may be identified / indicated by a second antenna panel index / identifier. One or more configuration parameters may indicate the second antenna panel indicator / index for the second antenna panel. For example, one or more wireless devices may transmit (e.g., transmit) an uplink signal (e.g., beam report, CSI report, UE capability message, PUCCH transmission) indicating the second antenna panel index of the second antenna panel.

[0280] One or more wireless devices may transmit (e.g., transmit) a first repetition of a PUSCH transmission on a first antenna panel. The first repetition of the PUSCH transmission may be associated with a first antenna panel, for example, based on transmitting (e.g., transmitting) the first repetition of the PUSCH transmission using the first antenna panel. One or more wireless devices may transmit (e.g., transmit) a second repetition of the PUSCH transmission on a second antenna panel. The second repetition of the PUSCH transmission may be associated with a second antenna panel, for example, based on transmitting (e.g., transmitting) the second repetition of the PUSCH transmission using the second antenna panel.

[0281] A message (e.g., a UE capability message) sent (e.g., transmitted) by one or more wireless devices may include / indicate a list of capability sets (e.g., a list of UE capability sets, a list of wireless device capability sets, etc.). A capability set (e.g., each capability set in the list of capability sets) may include / indicate a respective maximum number of SRS ports. For example, a first capability set in the list of capability sets may include / indicate a first maximum number of SRS ports. A second capability set in the list of capability sets may include / indicate a second maximum number of SRS ports.

[0282] A capability set (e.g., each capability set in a list of capability sets) may be identified / indicated by a respective capability set index. For example, a first capability set may be identified / indicated by a first capability set index. A second capability set may be identified / indicated by a second capability set index.

[0283] One or more wireless devices may send (e.g., transmit) at least one report (e.g., a beam report, a CSI report, an L1-RSRP report, an SINR report, and / or any other report). The one or more wireless devices may send (e.g., transmit) the report via the PUCCH. The report may indicate an association / mapping / correspondence between a first reference signal indicated by a first TCI state and a first capability value set. The report may include a first reference signal index (e.g., a CSI-RS and / or SSB resource index) of the first reference signal and a first capability value set index of the first capability value set. The one or more wireless devices may determine the association / mapping / correspondence between the first reference signal and the first capability value set. One or more configuration parameters may indicate a reference signal indicator / index / identifier for the reference signal. The first TCI state may be associated with the first capability value set, for example, based on the association / mapping / correspondence between the first reference signal indicated by the first TCI state and the first capability value set. The first repetition of the PUSCH transmission may be associated with a first capability value set, for example, based on (e.g., in response to) transmitting (e.g., transmitting) the first repetition based on a first TCI state associated with the first capability value set.

[0284] The report may indicate an association / mapping / correspondence between a second reference signal indicated by the second TCI state and a second capability value set. The report may include a second reference signal index (e.g., a CSI-RS and / or SSB resource index) of the second reference signal and a second capability value set index of the second capability value set. One or more wireless devices may determine the association / mapping / correspondence between the second reference signal and the second capability value set. One or more configuration parameters may indicate a reference signal indicator / index / identifier for the reference signal. The second TCI state may be associated with the second capability value set, for example, based on the association / mapping / correspondence between the second reference signal indicated by the second TCI state and the second capability value set. The second repetition of the PUSCH transmission may be associated with the second capability value set, for example, based on (e.g., in response to) transmitting (e.g., transmitting) the second repetition based on a second TCI state associated with the second capability value set.

[0285] The one or more wireless devices may receive an acknowledgement to the report, for example, from a base station. The acknowledgement may be, for example, a DCI.

[0286] One or more wireless devices may transmit (e.g., transmit) a CSI report at a first repetition of a PUSCH transmission (e.g., repetition 1 in FIG. 19) and a second repetition of a PUSCH transmission (e.g., repetition 2 in FIG. 19). The wireless devices may transmit (e.g., transmit) a CSI report at a first transmit opportunity (e.g., first TX opportunity in FIG. 19) and a second transmit opportunity (e.g., second TX opportunity in FIG. 19).

[0287] One or more wireless devices may multiplex a CSI report (or other information) in / on / with the first repetition of the PUSCH transmission and the second repetition of the PUSCH transmission. The one or more wireless devices may transmit (e.g., transmit) a CSI report in the first repetition of the PUSCH transmission and the second repetition of the PUSCH transmission, for example, based on multiplexing the CSI report in the first repetition of the PUSCH transmission and the second repetition of the PUSCH transmission. The one or more wireless devices may transmit (e.g., transmit) a CSI report in the first transmit opportunity (where the first repetition of the PUSCH transmission is transmitted (e.g., transmitted)) and the second transmit opportunity (where the second repetition of the PUSCH transmission is transmitted (e.g., transmitted)), for example, based on multiplexing the CSI report in the first repetition of the PUSCH transmission and the second repetition of the PUSCH transmission.

[0288] The one or more wireless devices may transmit (e.g., transmit) a CSI report in a first transmit opportunity (or a first repetition of a PUSCH transmission) and a second transmit opportunity (or a second repetition of a PUSCH transmission) based on, for example, one or more configuration parameters indicating at least two SRS resource sets. The one or more wireless devices may multiplex the CSI report in the first repetition of a PUSCH transmission and the second repetition of a PUSCH transmission based on, for example, the one or more configuration parameters indicating at least two SRS resource sets.

[0289] The one or more wireless devices may transmit (e.g., transmit) a CSI report at the first transmission opportunity (or the first repetition of PUSCH transmission) and the second transmission opportunity (or the second repetition of PUSCH transmission), for example, based on a field (or a value of the field) indicating a multi-TRP uplink repetition. The one or more wireless devices may transmit (e.g., transmit) a CSI report at the first transmission opportunity (or the first repetition of PUSCH transmission) and the second transmission opportunity (or the second repetition of PUSCH transmission), for example, based on the value of the field being equal to '10', '11', or '1' (or any other value). The one or more wireless devices may transmit (e.g., transmit) a CSI report at the first transmission opportunity (or the first repetition of PUSCH transmission) and the second transmission opportunity (or the second repetition of PUSCH transmission), for example, based on the repetition of PUSCH transmission being associated with at least two SRS resource sets.

[0290] The one or more wireless devices may multiplex a CSI report (or other information) in a first repetition of a PUSCH transmission and a second repetition of a PUSCH transmission based on, for example, a field (or a value of the field) indicating a multi-TRP uplink repetition. The one or more wireless devices may multiplex a CSI report in a first repetition of a PUSCH transmission and a second repetition of a PUSCH transmission based on, for example, the value of the field being equal to '10', '11', or '1' (or any other value). The one or more wireless devices may multiplex a CSI report in a first repetition of a PUSCH transmission and a second repetition of a PUSCH transmission based on, for example, the repetition of a PUSCH transmission being associated with at least two SRS resource sets.

[0291] The one or more wireless devices may transmit (e.g., transmit) a CSI report (or other information) at the first transmission opportunity (or first repetition of PUSCH transmission) and the second transmission opportunity (or second repetition of PUSCH transmission) based on one or more configuration parameters including, for example, a CSI multiplex mode parameter. The one or more wireless devices may transmit (e.g., transmit) a CSI report at the first transmission opportunity (or first repetition of PUSCH transmission) and the second transmission opportunity (or second repetition of PUSCH transmission) based on, for example, one or more configuration parameters including, for example, an enabled CSI multiplex mode parameter set.

[0292] The one or more wireless devices may multiplex the CSI report (or other information) in the first repetition of the PUSCH transmission and the second repetition of the PUSCH transmission based on one or more configuration parameters including, for example, a CSI multiplex mode parameter. The one or more wireless devices may multiplex the CSI report in the first repetition of the PUSCH transmission and the second repetition of the PUSCH transmission based on, for example, one or more configuration parameters including, for example, a validly set CSI multiplex mode parameter.

[0293] The one or more wireless devices may transmit (e.g., transmit) a CSI report (or other information) at the first transmission opportunity (or first repetition of PUSCH transmission) and the second transmission opportunity (or second repetition of PUSCH transmission) based on one or more configuration parameters including, for example, a CSI-multiplexing-FDM mode parameter. The one or more wireless devices may transmit (e.g., transmit) a CSI report at the first transmission opportunity (or first repetition of PUSCH transmission) and the second transmission opportunity (or second repetition of PUSCH transmission) based on, for example, one or more configuration parameters including, for example, an enabled CSI multiplexing-FDM mode parameter set.

[0294] The one or more wireless devices may multiplex the CSI report (or other information) in the first repetition of the PUSCH transmission and the second repetition of the PUSCH transmission based on one or more configuration parameters including, for example, a CSI multiplex FDM mode parameter. The one or more wireless devices may multiplex the CSI report in the first repetition of the PUSCH transmission and the second repetition of the PUSCH transmission based on, for example, one or more configuration parameters including, for example, a validly set CSI multiplex FDM mode parameter.

[0295] One or more wireless devices may transmit (e.g., transmit) a CSI report (or other information) at a first transmission opportunity (or a first repetition of a PUSCH transmission) and a second transmission opportunity (or a second repetition of a PUSCH transmission), for example, based on the PUSCH transmission not including / carrying uplink control information (UCI) different from the CSI report. One or more wireless devices may transmit (e.g., transmit) a CSI report at a first transmission opportunity (or a first repetition of a PUSCH transmission) and a second transmission opportunity (or a second repetition of a PUSCH transmission), for example, based on not multiplexing UCI different from the CSI report in the PUSCH transmission. The UCI may include, for example, a HARQ-ACK. The UCI may include, for example, an SR.

[0296] One or more wireless devices may multiplex a CSI report (or other information) in a first repetition of a PUSCH transmission and a second repetition of a PUSCH transmission, for example, based on the PUSCH transmission not including / carrying uplink control information (UCI) different from the CSI report. One or more wireless devices may multiplex a CSI report in a first repetition of a PUSCH transmission and a second repetition of a PUSCH transmission, for example, based on not multiplexing UCI different from the CSI report in the PUSCH transmission. The UCI may include, for example, a HARQ-ACK. The UCI may include, for example, an SR.

[0297] The one or more wireless devices may include transmitting (e.g., transmitting), based on other information in the CSI report (or the first transmission opportunity (or the first repetition of the PUSCH transmission) and the second transmission opportunity (or the second repetition of the PUSCH transmission), e.g., a UE capability message indicating support for transmission (e.g., transmitting / multiplexing a CSI report in / over at least two repetitions of a PUSCH transmission (or at least two transmission opportunities)).

[0298] One or more wireless devices may, for example, transmit (e.g., transmit) a CSI report / multiplex a CSI report (or other information) in a first repetition of a PUSCH transmission and a second repetition of a PUSCH transmission based on a capability message (e.g., a UE capability message) indicating support for multiplexing in / on at least two repetitions of a PUSCH transmission (or at least two transmission opportunities).

[0299] The one or more wireless devices may transmit (e.g., transmit) a CSI report (or other information) in a first transmit opportunity (or a first repetition of a PUSCH transmission) and a second transmit opportunity (or a second repetition of a PUSCH transmission) based on one or more configuration parameters indicating a repetition scheme, e.g., frequency domain repetition. The one or more wireless devices may multiplex the CSI report (or other information) in a first repetition of a PUSCH transmission and a second repetition of a PUSCH transmission based on one or more configuration parameters indicating a repetition scheme, e.g., frequency domain repetition.

[0300] One or more wireless devices may transmit (e.g., transmit) a CSI report (or other information) in a repetition of PUSCH transmission between the first repetition of PUSCH transmission (e.g., repetition 1 in FIG. 19 ) and the second repetition of PUSCH transmission (e.g., repetition 2 in FIG. 19 ). One or more wireless devices may transmit (e.g., transmit) a CSI report in a transmission opportunity between the first transmit opportunity (e.g., the first TX opportunity in FIG. 19 ) and the second transmit opportunity (e.g., the second TX opportunity in FIG. 19 ). The wireless devices may transmit (e.g., transmit) a repetition of PUSCH transmission in a transmission opportunity. One or more wireless devices may not transmit (e.g., transmit) a CSI report in any repetition of PUSCH transmission that is different from the repetition of PUSCH transmission among the first repetition of PUSCH transmission and the second repetition of PUSCH transmission. One or more wireless devices may not transmit (e.g., transmit) a CSI report in any transmission opportunity among the first transmit opportunity and the second transmit opportunity that is different from the transmission opportunity.

[0301] The one or more wireless devices may determine / select a repetition of the PUSCH transmission between the first repetition of the PUSCH transmission and the second repetition of the PUSCH transmission for transmission of the CSI report (or other information). The one or more wireless devices may determine / select a transmission opportunity between the first transmission opportunity and the second transmission opportunity for transmission of the CSI report.

[0302] The repetition of the PUSCH transmission may be, for example, a default repetition of the PUSCH transmission. The repetition of the PUSCH transmission may be, for example, a reference repetition of the PUSCH transmission.

[0303] For example, in FIG. 19 , the repetition of the PUSCH transmission may be the first repetition of the PUSCH transmission (e.g., repetition 1 in FIG. 19 ). One or more wireless devices may transmit (e.g., transmit) a CSI report in the first repetition of the PUSCH transmission. One or more wireless devices may transmit (e.g., transmit) a CSI report in the first transmit opportunity (e.g., the first TX opportunity in FIG. 19 ). One or more wireless devices may not transmit (e.g., transmit) a CSI report in the second repetition of the PUSCH transmission (e.g., repetition 2 in FIG. 19 ). One or more wireless devices may not transmit (e.g., transmit) a CSI report in the second transmit opportunity (e.g., the second TX opportunity in FIG. 19 ).

[0304] For example, in FIG. 19 , the repetition of the PUSCH transmission may be the second repetition of the PUSCH transmission (e.g., repetition 2 in FIG. 19 ). One or more wireless devices may transmit (e.g., transmit) a CSI report in the second repetition of the PUSCH transmission. One or more wireless devices may transmit (e.g., transmit) a CSI report in the second transmit opportunity (e.g., the second TX opportunity in FIG. 19 ). One or more wireless devices may not transmit (e.g., transmit) a CSI report in the first repetition of the PUSCH transmission (e.g., repetition 1 in FIG. 19 ). One or more wireless devices may not transmit (e.g., transmit) a CSI report in the first transmit opportunity (e.g., the first TX opportunity in FIG. 19 ).

[0305] One or more wireless devices may multiplex a CSI report (or other information) in / on / with a repetition of a PUSCH transmission. One or more wireless devices may transmit (e.g., transmit) a CSI report in a repetition of a PUSCH transmission, e.g., based on the multiplexing of the CSI report in the repetition of a PUSCH transmission. One or more wireless devices may transmit (e.g., transmit) a CSI report in a transmission opportunity (at which a repetition of a PUSCH transmission is transmitted (e.g., transmitted)), e.g., based on the multiplexing of the CSI report in the repetition of a PUSCH transmission.

[0306] The one or more wireless devices may transmit (e.g., transmit) a CSI report (or other information) in a transmission opportunity (or repetition of a PUSCH transmission) based on, for example, one or more configuration parameters indicating at least two SRS resource sets. The one or more wireless devices may multiplex the CSI report (or other information) in a repetition of a PUSCH transmission based on, for example, one or more configuration parameters indicating at least two SRS resource sets.

[0307] One or more wireless devices may transmit (e.g., transmit) a CSI report (or other information) at a transmission opportunity (or a repetition of a PUSCH transmission) based on, for example, one or more configuration parameters not indicating at least two SRS resource sets in a codebook (or usage parameters set for the codebook). One or more wireless devices may transmit (e.g., transmit) a CSI report at a transmission opportunity (or a repetition of a PUSCH transmission) based on, for example, one or more configuration parameters not indicating at least two SRS resource sets in a non-codebook (or usage parameters set for the non-codebook). One or more wireless devices may transmit (e.g., transmit) a CSI report at a transmission opportunity (or a repetition of a PUSCH transmission) based on, for example, one or more configuration parameters indicating an SRS resource set (or a single SRS resource set) with a codebook (or usage parameters set for the codebook). One or more wireless devices may transmit (e.g., transmit) a CSI report at a transmission opportunity (or repetition of a PUSCH transmission) based on, for example, one or more configuration parameters indicating an SRS resource set (or a single SRS resource set) with a non-codebook (or usage parameters set for the non-codebook).

[0308] One or more wireless devices may multiplex CSI reports (or other information) in a repetition of a PUSCH transmission based on, for example, one or more configuration parameters not indicating at least two SRS resource sets with a codebook (or with usage parameters set in a codebook). One or more wireless devices may multiplex CSI reports in a repetition of a PUSCH transmission based on, for example, one or more configuration parameters not indicating at least two SRS resource sets with a non-codebook (or with usage parameters set in a non-codebook). One or more wireless devices may multiplex CSI reports in a repetition of a PUSCH transmission based on, for example, one or more configuration parameters indicating an SRS resource set (or a single SRS resource set) with a codebook (or with usage parameters set in a codebook). One or more wireless devices may multiplex CSI reports in a repetition of a PUSCH transmission based on, for example, one or more configuration parameters indicating an SRS resource set (or a single SRS resource set) with a non-codebook (or with usage parameters set in a non-codebook).

[0309] One or more wireless devices may transmit (e.g., transmit) a CSI report at a transmission opportunity (or a repetition of a PUSCH transmission) based on, for example, a field (or a value of the field) indicating a multi-TRP uplink repetition. One or more wireless devices may transmit (e.g., transmit) a CSI report at a transmission opportunity (or a repetition of a PUSCH transmission) based on, for example, the value of the field being equal to '10' or '11' or '1' (or ...

Claims

1. 1. A method comprising: By wireless devices, a physical uplink control channel (PUCCH) transmission of uplink control information (UCI); a frequency domain repetition scheme for a physical uplink shared channel (PUSCH) transmission; receiving downlink control information (DCI) scheduling frequency domain repetitions of a PUSCH transmission, the frequency domain repetitions including a first repetition and a second repetition; transmitting the UCI in a first repetition based on a frequency domain repetition of the PUSCH transmission that overlaps in time with the PUCCH transmission of the UCI and based on the first repetition being associated with a value that satisfies a criterion.

2. transmitting UCI in the first iteration, the one or more configuration parameters indicate a UCI multiplexing mode parameter that is not enabled; or The method of claim 1 , further based on at least one of: the one or more configuration parameters not including a UCI multiplexing mode parameter.

3. 3. The method according to claim 1, further comprising transmitting the second repetition in the same time period as the first repetition, wherein the UCI is multiplexed in the first repetition and the UCI is not multiplexed in the second repetition.

4. 4. The method of claim 1, further comprising transmitting each of the frequency domain repetitions of the PUSCH transmission in a plurality of transmission opportunities in different frequency ranges, each repetition of the frequency domain repetition of the PUSCH transmission being transmitted by the wireless device in a respective one of the plurality of transmission opportunities.

5. receiving a second DCI, transmitting a second UCI; and receiving a second DCI scheduling a frequency domain repetition of a second PUSCH transmission; 5. The method of claim 1, further comprising: transmitting the second UCI in each of the frequency domain repetitions of the second PUSCH transmission based on a UCI multiplexing mode parameter being valid.

6. 1. A method comprising: By base station, Physical Uplink Control Channel (PUCCH) transmission of uplink control information (UCI); and a frequency domain repetition scheme for a physical uplink shared channel (PUSCH) transmission; transmitting downlink control information (DCI) scheduling a frequency domain repetition of a PUSCH transmission, the frequency domain repetition including a first repetition and a second repetition; receiving the UCI in a first repetition based on a frequency domain repetition of the PUSCH transmission that overlaps in time with the PUCCH transmission of the UCI and based on the first repetition being associated with a value that satisfies a criterion.

7. transmitting UCI in the first iteration, the one or more configuration parameters indicate a UCI multiplexing mode parameter that is not enabled; or The method of claim 6 , further based on at least one of: the one or more configuration parameters not including a UCI multiplexing mode parameter.

8. 8. The method according to claim 6, further comprising receiving the second repetition in the same time period as the first repetition, wherein the UCI is multiplexed in the first repetition and the UCI is not multiplexed in the second repetition.

9. 9. The method of claim 6, further comprising receiving each of the frequency domain repetitions of the PUSCH transmission at a plurality of transmission opportunities in different frequency ranges, each repetition of the frequency domain repetition of the PUSCH transmission being received by the base station at a respective transmission opportunity of the plurality of transmission opportunities.

10. transmitting a second DCI, transmitting a second UCI; and transmitting a second DCI that schedules a frequency domain repetition of the second PUSCH transmission; 10. The method of claim 6, further comprising: receiving the second UCI in each of the frequency domain repetitions of the second PUSCH transmission based on a UCI multiplexing mode parameter being valid.

11. each iteration of the frequency domain iterations is associated with a respective value of a plurality of values; the criteria includes determining a minimum or maximum value among the plurality of values, the plurality of values ​​including the value that satisfies the criteria; The value associated with the first iteration is: frequency, Resource block value, Transmission Configuration Indicator (TCI) state, TCI Status Index, A sounding reference signal (SRS) resource set; Control Resource Set (CORESET) Pool Index, Transmit and receive point (TRP) index, Antenna panel, or The method according to any one of claims 1 to 10, further comprising indicating at least one of:

12. The UCI is Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK); Channel State Information (CSI) reports, and The method according to any one of claims 1 to 11, further comprising at least one of: a scheduling request (SR).

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

14. 1. A system comprising: A wireless device configured to carry out the method according to any one of claims 1 to 5 or, when dependent on the method according to claim 1, the method according to any one of claims 11 to 12; A base station arranged to carry out the method according to any one of claims 6 to 10 or, when dependent on claim 6, any one of claims 11 to 12.

15. A computer readable medium storing instructions that, when executed, cause the performance of the method of any one of claims 1 to 12.

16. 1. A method comprising: receiving, by the wireless device, one or more configuration parameters including an uplink control information (UCI) multiplexing mode parameter; and a frequency domain repetition scheme for Physical Uplink Shared Channel (PUSCH) transmissions; receiving downlink control information (DCI) scheduling frequency domain repetitions of a PUSCH transmission, the frequency domain repetitions including a first repetition and a second repetition; transmitting the UCI in one of the first repetition or the second repetition based on the one or more configuration parameters indicating that UCI multiplexing is not enabled, wherein selection of the first repetition or the second repetition for transmitting the UCI is based on an index associated with one of the first repetition or the second repetition, and transmitting the UCI satisfies a criterion.

17. 17. The method of claim 16, wherein the transmitting the UCI includes transmitting the UCI in the first repetition based on the first repetition including a lowest index of a plurality of indexes including a first index associated with the first repetition and a second index associated with the second repetition.

18. each iteration of the frequency domain iteration is associated with a respective index of a plurality of indexes, the plurality of indexes including the indexes that satisfy the criterion; the transmitting of the UCI is within the first repetition based on an index associated with the first repetition being a lowest index or a highest index of the plurality of indexes; the criteria including determining the lowest index or the highest index of the plurality of indexes; The index that satisfies the criteria is TCI status index, or 18. The method of claim 17, further comprising indicating at least one of: an antenna panel index;

19. 19. The method of claim 17, further comprising transmitting the second repetition in the same time period as the first repetition, wherein the UCI is multiplexed in the first repetition and the UCI is not multiplexed in the second repetition.

20. The UCI is Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK); Channel State Information (CSI) reports, and The method according to any one of claims 17 to 19, further comprising at least one of: a scheduling request (SR).

21. 21. The method of claim 17, further comprising transmitting each of the frequency domain repetitions of the PUSCH transmission in a plurality of transmission opportunities in different frequency ranges and overlapping in time, each repetition of the frequency domain repetition of the PUSCH transmission being transmitted by the wireless device in a respective one of the plurality of transmission opportunities.

22. receiving an indication of a change of the UCI multiplexing mode parameter from a not enabled state to an enabled state; receiving a second DCI after receiving the indication of the change of the UCI multiplexing mode parameter, transmitting a second UCI; and receiving a second DCI scheduling a frequency domain repetition of a second PUSCH transmission; and transmitting the second UCI in each of the frequency domain repetitions of the second PUSCH transmission based on the UCI multiplexing mode parameter being valid.

23. 1. A computing device comprising: one or more processors; and a memory storing instructions which, when executed by said one or more processors, cause said computing device to perform a method according to any one of claims 17 to 22.

24. 1. A system comprising: A wireless device configured to perform the method according to any one of claims 17 to 22; a base station configured to transmit the one or more configuration parameters.

25. A computer readable medium storing instructions that, when executed, cause the performance of the method of any one of claims 17 to 22.

26. 1. A method comprising: By base station, An uplink control information (UCI) multiplexing mode parameter; a physical uplink control channel (PUCCH) transmission of uplink control information (UCI); a frequency domain repetition scheme for a physical uplink shared channel (PUSCH) transmission; transmitting downlink control information (DCI) scheduling a frequency domain repetition of a PUSCH transmission, the frequency domain repetition including a first repetition and a second repetition; receiving the UCI in one of the first repetition or the second repetition based on the one or more configuration parameters indicating that UCI multiplexing is not enabled, wherein receiving the UCI in the first repetition or the second repetition is based on an index associated with one of the first repetition or the second repetition and satisfies a criterion.

27. each iteration of the frequency domain iteration is associated with a respective index of a plurality of indexes, the plurality of indexes including the indexes that satisfy the criterion; the receiving of the UCI is within the first repetition based on an index associated with the first repetition being a lowest index or a highest index of the plurality of indexes; the criteria including determining the lowest index or the highest index of the plurality of indexes; The index that satisfies the criteria is TCI status index, or and an antenna panel index.

28. 28. The method of claim 26, further comprising transmitting the second repetition in the same time period as the first repetition, wherein the UCI is multiplexed in the first repetition and the UCI is not multiplexed in the second repetition.

29. The UCI is Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK); Channel State Information (CSI) reports, and A method according to any one of claims 26 to 28, further comprising at least one of: a scheduling request (SR).

30. 30. The method of claim 26, further comprising receiving each of the frequency domain repetitions of the PUSCH transmission at a plurality of reception opportunities in different frequency ranges and overlapping in time, each repetition of the frequency domain repetition of the PUSCH transmission being received by the base station at a respective reception opportunity of the plurality of reception opportunities.

31. sending an indication of a change of the UCI multiplexing mode parameter from a not enabled state to an enabled state; transmitting a second DCI after transmitting the indication of the change of the UCI multiplexing mode parameter, transmitting a second UCI; and transmitting a second DCI that schedules a frequency domain repetition of the second PUSCH transmission; and receiving the second UCI within each of the frequency domain repetitions of the second PUSCH transmission based on the UCI multiplexing mode parameter being enabled.

32. 1. A computing device comprising: one or more processors; and a memory storing instructions which, when executed by said one or more processors, cause said computing device to perform a method according to any one of claims 26 to 31.

33. 1. A system comprising: A wireless device configured to perform the method according to any one of claims 26 to 31; a base station configured to transmit the one or more configuration parameters.

34. A computer readable medium storing instructions that, when executed, cause the performance of the method of any one of claims 26-31.

35. 1. A method comprising: receiving, by the wireless device, one or more configuration parameters associated with a frequency domain repetition of a physical uplink shared channel (PUSCH) transmission; receiving downlink control information (DCI), the DCI comprising: a channel state information (CSI) request field indicating transmission of a CSI report; scheduling a frequency domain repetition of a PUSCH transmission, the frequency domain repetition including a first repetition of a first frequency range that overlaps in time with a second repetition of a second frequency range; and forwarding the CSI report in the first iteration based on the first iteration being associated with a value that meets a criterion.

36. transmitting the CSI report in the first iteration, the one or more configuration parameters include a CSI multiplexing mode parameter that is not enabled; or 36. The method of claim 35, further based on at least one of: the one or more configuration parameters not including a CSI multiplexing mode parameter.

37. each iteration of the frequency domain iteration is associated with a respective value of a plurality of values, the plurality of values ​​including the value that satisfies the criterion; the criteria includes determining a minimum or maximum value among the plurality of values; The value associated with the first iteration is: frequency, Resource block value, Transmission Configuration Indicator (TCI) state, TCI Status Index, A sounding reference signal (SRS) resource set; Control Resource Set (CORESET) Pool Index, Transmit and receive point (TRP) index, Antenna panel, or and an antenna panel index.

38. 38. The method of claim 35, further comprising transmitting the second repetition in a same time period as the first repetition, wherein the CSI report is multiplexed in the first repetition and the CSI report is not multiplexed in the second repetition.

39. The CSI report, Aperiodic CSI reports, or A method according to any one of claims 35 to 38, comprising at least one of the following: semi-persistent CSI reporting.

40. The method according to any one of claims 35 to 39, wherein the CSI request field includes information for scheduling transmission of the CSI report.

41. 41. The method of claim 35, further comprising transmitting each of the frequency domain repetitions of the PUSCH transmission in a plurality of transmission opportunities in different frequency ranges and overlapping in time, each repetition of the frequency domain repetition of the PUSCH transmission being transmitted by the wireless device in a respective one of the plurality of transmission opportunities.

42. receiving a second DCI configured to schedule, transmitting a second CSI report; and receiving a second DCI scheduling a frequency domain repetition of a second PUSCH transmission; and transmitting the second CSI report within each of the frequency domain repetitions of the second PUSCH transmission based on a CSI multiplexing mode parameter being valid.

43. 1. A computing device comprising: one or more processors; and a memory storing instructions which, when executed by said one or more processors, cause said computing device to perform a method according to any one of claims 35 to 42.

44. 1. A system comprising: A wireless device configured to perform the method according to any one of claims 35 to 42; a base station configured to transmit the one or more configuration parameters.

45. A computer readable medium storing instructions that, when executed, cause the performance of the method of any one of claims 35 to 42.

46. 1. A method comprising: receiving, by the wireless device, one or more configuration parameters associated with a frequency domain repetition of a physical uplink shared channel (PUSCH) transmission, the one or more configuration parameters including a channel state information (CSI) multiplexing mode parameter; receiving downlink control information (DCI) scheduling a frequency domain repetition of a PUSCH transmission, the frequency domain repetition including a first repetition of a first frequency range overlapping in time with a second repetition of a second frequency range; transmitting a CSI report in one of the first iteration or the second iteration based on the one or more configuration parameters indicating that CSI multiplexing is not enabled, wherein selection of the first iteration or the second iteration for transmitting the CSI report is based on an index associated with one of the first iteration or the second iteration and satisfies a criterion.

47. 47. The method of claim 46, wherein the DCI further comprises a CSI request field for scheduling transmission of the CSI report.

48. each iteration of the frequency domain iteration is associated with a respective index of a plurality of indexes, the plurality of indexes including the indexes that satisfy the criterion; the transmission of the CSI report is within the first repetition based on an index associated with the first repetition being a lowest index or a highest index of the plurality of indexes; the criteria including determining the lowest index or the highest index of the plurality of indexes; The index that satisfies the criteria is TCI status index, or A method according to any one of claims 46 to 47, further comprising indicating at least one of:

49. 49. The method of claim 46, further comprising: transmitting the second repetition with a same time period as the first repetition, wherein the CSI report is multiplexed in the first repetition and the CSI report is not multiplexed in the second repetition.

50. The CSI report, Aperiodic CSI reports, or 50. The method of any one of claims 46 to 49, further comprising at least one of: semi-persistent CSI reporting.

51. 51. The method of claim 46, further comprising transmitting each of the frequency domain repetitions of the PUSCH transmission in a plurality of transmission opportunities in different frequency ranges and overlapping in time, each repetition of the frequency domain repetition of the PUSCH transmission being transmitted by the wireless device in a respective one of the plurality of transmission opportunities.

52. receiving an indication of a change of the CSI multiplexing mode parameter from a not enabled state to an enabled state; receiving a second DCI after receiving the indication of the change in the CSI multiplexing mode parameter, transmitting a second CSI report; and receiving a second DCI scheduling a frequency domain repetition of a second PUSCH transmission; and transmitting the second CSI report within each of the frequency domain repetitions of the second PUSCH transmission based on the CSI multiplexing mode parameter being valid.

53. 1. A computing device comprising: one or more processors; and a memory storing instructions which, when executed by said one or more processors, cause said computing device to perform a method according to any one of claims 46 to 52.

54. 1. A system comprising: A wireless device configured to perform the method according to any one of claims 46 to 52; a base station configured to transmit the one or more configuration parameters.

55. A computer readable medium storing instructions that, when executed, cause the performance of the method of any one of claims 46 to 52.

56. 1. A method comprising: transmitting, by the base station, one or more configuration parameters associated with a frequency domain repetition of a Physical Uplink Shared Channel (PUSCH) transmission, the one or more configuration parameters including a Channel State Information (CSI) multiplexing mode parameter; transmitting downlink control information (DCI) scheduling a frequency domain repetition of a PUSCH transmission, the frequency domain repetition including a first repetition of a first frequency range overlapping in time with a second repetition of a second frequency range; receiving a CSI report in one of the first iteration or the second iteration based on the one or more configuration parameters indicating that CSI multiplexing is not enabled, wherein receiving the CSI report in the first iteration or the second iteration is based on an index associated with one of the first iteration or the second iteration and satisfies a criterion.

57. each iteration of the frequency domain iterations is associated with a respective index of a plurality of indexes; determining that the reception of the CSI report is within the first repetition based on an index associated with the first repetition being a lowest index or a highest index of the plurality of indexes; the criteria including determining the lowest index or the highest index of the plurality of indexes; The index associated with the first iteration is TCI status index, or 57. The method of claim 56, further comprising indicating at least one of: an antenna panel index;

58. 58. The method of claim 56, further comprising receiving the second repetition in a same time period as the first repetition, wherein the CSI report is multiplexed in the first repetition and the CSI report is not multiplexed in the second repetition.

59. 59. The method of any one of claims 56 to 58, further comprising receiving each of the frequency domain repetitions of the PUSCH transmission at a plurality of reception opportunities in different frequency ranges and overlapping in time, each repetition of the frequency domain repetition of the PUSCH transmission being received by the base station at a respective reception opportunity of the plurality of reception opportunities.

60. transmitting an indication of a change of the CSI multiplexing mode parameter from a not enabled state to an enabled state; transmitting a second DCI after transmitting the indication of the change in the CSI multiplexing mode parameter, transmitting a second CSI report; and transmitting a second DCI configured to schedule a frequency domain repetition of a second PUSCH transmission; and receiving the second CSI report within each of the frequency domain repetitions of the second PUSCH transmission based on the CSI multiplexing mode parameter being valid.

61. 1. A computing device comprising: one or more processors; and a memory storing instructions which, when executed by said one or more processors, cause said computing device to perform a method according to any one of claims 56 to 60.

62. 1. A system comprising: A wireless device configured to perform the method according to any one of claims 56 to 60; a base station configured to transmit the one or more configuration parameters.

63. A computer readable medium storing instructions that, when executed, cause the performance of the method of any one of clauses 56-60.

64. 1. A method comprising: receiving, by a wireless device, downlink control information (DCI) scheduling a repetition of a first physical uplink shared channel (PUSCH) transmission; the repetition of the first PUSCH transmission is in the frequency domain; each iteration of the repetitions is associated with a respective transmission configuration indicator (TCI) state of a plurality of TCI states; receiving a power headroom report based on the repetition of the first PUSCH transmission overlapping in time with a second PUSCH transmission, the power headroom report determining the power headroom report using a path loss reference signal associated with a TCI state among the plurality of TCI states indicated by a lowest TCI state index among the TCI state indexes associated with the repetition of the first PUSCH transmission; transmitting the power headroom report.

65. 65. The method of claim 64, wherein each repetition of the repetition of the first PUSCH transmission is associated with a respective path loss reference signal of a plurality of path loss reference signals, each path loss reference signal of the plurality of path loss reference signals being associated with a respective TCI state of the plurality of TCI states.

66. transmitting a first repetition of the repetition of the first PUSCH transmission based on a first TCI state; The method of any one of claims 64 to 65, further comprising: transmitting a second repetition of the repetition of the first PUSCH transmission based on a second TCI state.

67. determining the power headroom report using the path loss reference signal; receiving a power headroom mode parameter indicating a single power headroom mode is in effect; A method according to any one of claims 64 to 66, based on at least one of: determining that two power headroom reporting mode parameters have not been received.

68. receiving an indication of initiating at least two TCI conditions including the TCI condition; transmitting a first repetition of the repetition of the first PUSCH transmission; using a spatial domain transmit filter determined based on a first TCI state of the at least two TCI states; A method according to any one of claims 64 to 67, further comprising: using a transmission power determined based on a path loss reference signal indicated by the first TCI state.

69. 69. The method of any one of claims 64 to 68, further comprising determining the path loss reference signal associated with a first repetition of the first PUSCH transmission, wherein the determining of the path loss reference signal is based on the power headroom report, and wherein the first repetition is associated with a same value of a TCI state index.

70. A method according to any one of claims 64 to 69, wherein the power headroom report comprises a power headroom value determined using the path loss reference signal associated with the TCI state indicated by the lowest TCI state index.

71. 1. A computing device comprising: one or more processors; and a memory storing instructions which, when executed by said one or more processors, cause said computing device to perform a method according to any one of claims 64 to 70.

72. 1. A system comprising: A wireless device configured to perform the method according to any one of claims 64 to 70; a base station configured to transmit the DCI.

73. A computer readable medium storing instructions that, when executed, cause the performance of the method of any one of claims 64 to 70.

74. 1. A method comprising: receiving, by the wireless device, downlink control information (DCI) scheduling frequency domain repetitions of a first physical uplink shared channel (PUSCH) that overlap in time with a second PUSCH transmission comprising a power headroom report, each repetition of the repetitions being associated with a respective path loss reference signal of a plurality of path loss reference signals and a respective index of a plurality of indexes; determining the power headroom report using a path loss reference signal corresponding to a repetition associated with a lowest index of the respective indexes of the repetition among the repetitions of the first PUSCH transmission; transmitting the power headroom report.

75. The lowest index is A transmit configuration indicator (TCI) index; Antenna Panel Index, or 75. The method of claim 74, further comprising at least one of: a. a resource block location;

76. 76. The method of claim 74, wherein each path loss reference signal of the plurality of path loss reference signals is associated with a respective transmission configuration indicator (TCI) state of a plurality of TCI states, and each TCI state of the plurality of TCI states is associated with a respective TCI state index of a plurality of TCI state indexes.

77. transmitting a first repetition of the repetition of the first PUSCH transmission based on a first transmission configuration indicator (TCI) state; 77. The method of any one of claims 74 to 76, further comprising: transmitting a second repetition of the repetition of the first PUSCH transmission based on a second TCI state.

78. A method according to any one of claims 74 to 77, wherein the transmitting of the power headroom report is based on receiving a power headroom mode parameter indicating that a single power headroom mode is in effect.

79. receiving an indication to activate at least two transmit configuration indicator (TCI) states; transmitting a first repetition of the repetition of the first PUSCH transmission; using a spatial domain transmit filter determined based on a first TCI state of the at least two TCI states; The method of any one of claims 74 to 78, further comprising: using a transmission power determined based on a path loss reference signal associated with the first TCI state.

80. 80. The method of any one of claims 74 to 79, further comprising determining the path loss reference signal corresponding to the iteration associated with the lowest index, wherein determining the path loss reference signal is based on the power headroom report and the iteration associated with the lowest index being associated with the same value of a transmission configuration indicator (TCI) state.

81. A method according to any one of claims 74 to 80, wherein the power headroom report comprises a power headroom value determined using the path loss reference signal associated with a transmission configuration indicator (TCI) state indicated by a lowest TCI state index.

82. 1. A computing device comprising: one or more processors; and a memory storing instructions which, when executed by said one or more processors, cause said computing device to perform a method according to any one of claims 74 to 81.

83. 1. A system comprising: A wireless device configured to perform a method according to any one of claims 74 to 81; a base station configured to transmit the DCI.

84. A computer readable medium storing instructions that, when executed, cause the performance of the method of any one of claims 74 to 81.

85. 1. A method comprising: receiving, by the wireless device, downlink control information (DCI) scheduling frequency domain repetitions of a first physical uplink shared channel (PUSCH) that overlap in time with a second PUSCH transmission comprising a power headroom report, each repetition of the repetitions being associated with a respective path loss reference signal of a plurality of path loss reference signals and a respective index of a plurality of indexes; and transmitting a power headroom value in the power headroom report, the power headroom value being determined using a path loss reference signal corresponding to a repetition of the first PUSCH transmission that is associated with a lowest index of the respective indexes of the repetition.

86. The lowest index is A minimum transmission configuration indicator (TCI) index; A minimum sounding reference signal (SRS) resource set; CORESET Pool Index, Minimum transmit and receive point (TRP) index, Minimum Antenna Panel Index, or 86. The method of claim 85, further comprising indicating at least one of: a. a lowest resource block position;

87. determining the power headroom report using the path loss reference signal; receiving a power headroom mode parameter indicating a single power headroom mode is in effect; A method according to any one of claims 85 to 86, based on at least one of: determining that two power headroom reporting mode parameters have not been received.

88. 88. The method of claim 85, further comprising determining the path loss reference signal corresponding to the iteration associated with the lowest index, wherein determining the path loss reference signal is based on the power headroom report and the iteration associated with the lowest index being associated to the same value of a transmission configuration indicator (TCI) state.

89. The method of any one of claims 85 to 88, wherein the transmitting of the power headroom report is based on receiving a power headroom mode parameter indicating that a single power headroom mode is in effect.

90. 1. A computing device comprising: one or more processors; and a memory storing instructions which, when executed by said one or more processors, cause said computing device to perform a method according to any one of claims 85 to 89.

91. 1. A system comprising: A wireless device configured to perform a method according to any one of claims 85 to 89; a base station configured to transmit the DCI.

92. A computer readable medium storing instructions that, when executed, cause the performance of the method of any one of claims 85 to 89.

93. 1. A method comprising: receiving, by the wireless device, first downlink control information (DCI) scheduling a first uplink transmission at a first transmit opportunity; receiving a second DCI scheduling a second uplink transmission in a second transmit opportunity that overlaps in time with the first transmit opportunity; determining that a total transmit power of transmissions by the wireless device, including the first uplink transmission and the second uplink transmission, exceeds a maximum transmit power; one of the first uplink transmission and the second uplink transmission, determining that the total transmit power of transmissions by the wireless device exceeds the maximum transmit power; and and prioritizing based on a comparison of a first value associated with the first uplink transmission and a second value associated with the second uplink transmission.

94. 94. The method of claim 93, wherein the receiving the first DCI includes receiving the first DCI via a first control resource set (CORESET) associated with a first CORESET pool index, and the receiving the second DCI includes receiving the second DCI via a second CORESET different from the first CORESET and associated with a second CORESET pool index different from the first CORESET pool index, wherein the first value is the first CORESET pool index and the second value is the second CORESET pool index.

95. the prioritizing the one of the first uplink transmission and the second uplink transmission; reducing a transmit power associated with at least one of the first uplink transmission or the second uplink transmission; or Dropping at least one of the first uplink transmission or the second uplink transmission.

96. the prioritizing the one of the first uplink transmission and the second uplink transmission; reducing a transmit power associated with at least one tier of the first uplink transmission; or Dropping at least one layer of transmission of the first uplink transmission.

97. The comparison of the first value associated with the first uplink transmission and the second value associated with the second uplink transmission comprises: frequency, Resource block value, Transmission Configuration Indicator (TCI) state, TCI Status Index, A sounding reference signal (SRS) resource set; Control Resource Set (CORESET) Pool Index, Transmit and receive point (TRP) index, Antenna panel, or 97. A method according to any one of claims 93 to 96, comprising determining a minimum or maximum of an antenna panel index.

98. 98. The method of any one of claims 93 to 97, further comprising transmitting the first uplink transmission based on the comparison indicating that the first value is less than the second value.

99. dropping the second uplink transmission based on the comparison indicating the first value is less than the second value; or transmitting the second uplink transmission using an adjusted transmit power based on the comparison indicating the first value is less than the second value.

100. 1. A computing device comprising: one or more processors; and a memory storing instructions which, when executed by said one or more processors, cause said computing device to perform a method according to any one of claims 93 to 99.

101. 1. A system comprising: A wireless device configured to perform a method according to any one of claims 93 to 99; a base station configured to transmit the first DCI.

102. A computer readable medium storing instructions that, when executed, cause the performance of the method of any one of claims 93 to 99.

103. 1. A method comprising: receiving, by the wireless device, first downlink control information (DCI) scheduling a first uplink transmission at a first transmit opportunity; receiving a second DCI scheduling a second uplink transmission in a second transmit opportunity that overlaps in time with the first transmit opportunity; determining that a total transmit power of transmissions by the wireless device, including the first uplink transmission and the second uplink transmission, exceeds a maximum transmit power; transmitting the first uplink transmission; and transmitting the second uplink transmission using an adjusted transmit power, the adjusted transmit power comprising: determining that the total transmit power of transmissions by the wireless device exceeds the maximum transmit power; and transmitting based on a determination that a first value associated with the first uplink transmission is less than a second value associated with the second uplink transmission.

104. 104. The method of claim 103, wherein the receiving the first DCI comprises receiving the first DCI via a first control resource set (CORESET) associated with a first CORESET pool index, and the receiving the second DCI comprises receiving the second DCI via a second CORESET different from the first CORESET and associated with a second CORESET pool index different from the first CORESET pool index, wherein the first value is the first CORESET pool index and the second value is the second CORESET pool index.

105. 105. The method of claim 103, wherein the first value comprises a first transmission configuration indicator (TCI) state index associated with the first uplink transmission, and the second value comprises a second TCI state index associated with the second uplink transmission.

106. transmitting the second uplink transmission using the adjusted transmit power. reducing a transmit power associated with at least one tier of the second uplink transmission; or Dropping at least one layer of transmission of the second uplink transmission.

107. the first value and the second value are different; frequency, Resource block value, Transmission Configuration Indicator (TCI) state, TCI Status Index, Antenna panel, or A method according to any one of claims 103 to 106, comprising: an antenna panel index.

108. 108. The method of any one of claims 103 to 107, further comprising transmitting the first uplink transmission using a first uplink transmit power that is greater than a second uplink transmit power used to transmit the second uplink transmission.

109. 1. A computing device comprising: one or more processors; and a memory storing instructions which, when executed by said one or more processors, cause said computing device to perform a method according to any one of claims 103 to 108.

110. 1. A system comprising: A wireless device configured to perform a method according to any one of claims 103 to 108; a base station configured to transmit the first DCI.

111. A computer readable medium storing instructions that, when executed, cause the performance of the method of any one of claims 103-108.

112. 1. A method comprising: receiving, by the wireless device, first downlink control information (DCI) scheduling a first uplink transmission at a first transmit opportunity; receiving a second DCI scheduling a second uplink transmission in a second transmit opportunity that overlaps in time with the first transmit opportunity; determining that a total transmit power of transmissions by the wireless device, including the first uplink transmission and the second uplink transmission, exceeds a maximum transmit power; based on a determination that a first value associated with the first uplink transmission is less than a second value associated with the second uplink transmission; transmitting the first uplink transmission; and transmitting the second uplink transmission using an adjusted transmit power or dropping the second uplink transmission.

113. 113. The method of claim 112, wherein the receiving the first DCI includes receiving the first DCI via a first control resource set (CORESET) associated with a first CORESET pool index, and the receiving the second DCI includes receiving the second DCI via a second CORESET different from the first CORESET and associated with a second CORESET pool index different from the first CORESET pool index, the first value being the first CORESET pool index and the second value being the second CORESET pool index.

114. A method according to any one of claims 112 to 113, wherein the first value comprises a first transmission configuration indicator (TCI) state index associated with the first uplink transmission, and the second value comprises a second TCI state index associated with the second uplink transmission.

115. transmitting the second uplink transmission using the adjusted transmit power. reducing a transmit power associated with at least one tier of the second uplink transmission; or Dropping at least one layer of transmission of the second uplink transmission.

116. the first value and the second value are different; frequency, Resource block value, Transmission Configuration Indicator (TCI) state, TCI Status Index, A sounding reference signal (SRS) resource set; Control Resource Set (CORESET) Pool Index, Transmit and receive point (TRP) index, Antenna panel, or The method of any one of claims 112 to 115, further comprising: an antenna panel index.

117. The method of any one of claims 112 to 116, further comprising transmitting the first uplink transmission using a first uplink transmit power that is greater than a second uplink transmit power used to transmit the second uplink transmission.

118. The method of any one of claims 112 to 117, further comprising: dropping the second uplink transmission based on the determination that the first value associated with the first uplink transmission is less than the second value associated with the second uplink transmission.

119. 1. A computing device comprising: one or more processors; and a memory storing instructions that, when executed by said one or more processors, cause said computing device to perform a method according to any one of claims 112 to 118.

120. 1. A system comprising: A wireless device configured to perform a method according to any one of claims 112 to 118; a base station configured to transmit the first DCI.

121. A computer readable medium storing instructions that, when executed, cause the performance of the method of any one of claims 112-118.

Images