Transmission Repetition for Wireless Communications

Abstract

A base station and / or wireless device may communicate using multiple transmission beams. Multiple transmission beams may be used for transmission so that a message may be transmitted via different transmission beams. Multiple transmission beams may be used to transmit multiple repetitions of a message or to transmit different portions of a message.

Description

[Technical Field]

[0001] (CROSS-REFERENCE TO RELATED APPLICATIONS) This application claims the benefit of U.S. Provisional Patent Application No. 63 / 056,129, filed July 24, 2020. The above-referenced applications are incorporated herein by reference in their entireties. [Background technology]

[0002] Multiple repetitions of the message are transmitted to one or more communication devices. The repetitions of the message may be transmitted over multiple radio resources. Summary of the Invention

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

[0004] Signal transmissions (e.g., uplink transmissions) may be sent via transmission beams. Multiple transmission beams may be used for uplink transmissions (e.g., repetitions of an uplink message or portions of an uplink message). A message (e.g., from a base station) may indicate multiple transmission beams to be used. For example, the message may include multiple fields, each indicating a corresponding transmission beam. Spatial diversity facilitated by the use of multiple transmission beams may provide advantages such as improved signal reliability.

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

[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 similar elements and in which: [Figure 1A] 1 illustrates an exemplary communication network. [Figure 1B] 1 illustrates an exemplary communication network. [Figure 2A] 1 illustrates an exemplary user plane. [Figure 2B] 1 illustrates an exemplary control plane configuration. [Figure 3] 1 shows an example of a protocol layer. [Figure 4A] 1 illustrates an exemplary downlink data flow for a user plane configuration. [Figure 4B] 1 illustrates an exemplary format of a Medium Access Control (MAC) subheader in a MAC Protocol Data Unit (PDU). [Figure 5A] 1 illustrates an exemplary mapping for a downlink channel. [Figure 5B] 10 illustrates an exemplary mapping for an uplink channel. [Figure 6] 1 illustrates exemplary radio resource control (RRC) states and RRC state transitions. [Figure 7] 1 shows an exemplary configuration of a frame. [Figure 8] 1 illustrates an example resource configuration for one or more carriers. [Figure 9] 1 shows an exemplary configuration of a bandwidth part (BWP). [Figure 10A] 1 shows an example of a carrier aggregation configuration based on component carriers. [Figure 10B] 1 illustrates an exemplary cell group. [Figure 11A] 1 illustrates an exemplary mapping of one or more synchronization signal / physical broadcast channel (SS / PBCH) blocks. [Figure 11B]1 illustrates an example mapping of one or more channel state information reference signals (CSI-RS). [Figure 12A] 1 shows an example of a downlink beam management procedure. [Figure 12B] An example of an uplink beam management procedure is shown. [Figure 13A] 1 illustrates an exemplary four-step random access procedure. [Figure 13B] 1 illustrates an exemplary two-step random access procedure. [Figure 13C] 1 illustrates an exemplary two-step random access procedure. [Figure 14A] 1 shows an example of a control resource set (CORESET) configuration. [Figure 14B] 1 illustrates an example of control channel element to resource element group (CCE-to-REG) mapping. [Figure 15A] 1 illustrates an example of communication between a wireless device and a base station. [Figure 15B] 1 illustrates exemplary elements of a computing device that may be used to implement any of the various devices described herein. [Figure 16A] 1 illustrates an example of uplink and downlink signal transmission. [Figure 16B] 1 illustrates an example of uplink and downlink signal transmission. [Figure 16C] 1 illustrates an example of uplink and downlink signal transmission. [Figure 16D] 1 illustrates an example of uplink and downlink signal transmission. [Figure 17] 1 illustrates exemplary beam management for transmit repetitions. [Figure 18] 1 illustrates exemplary beam management for transmission. [Figure 19] 10 illustrates an exemplary transmit power determination for a transmission iteration. [Figure 20]10 shows an example of determining transmission power. [Figure 21A] 1 illustrates an exemplary configuration of transmission configuration indication (TCI) codepoints and / or TCI states associated with a CORESET. [Figure 21B] 1 illustrates an exemplary configuration of transmission configuration indication (TCI) codepoints and / or TCI states associated with a CORESET. [Figure 21C] 1 illustrates an exemplary configuration of transmission configuration indication (TCI) codepoints and / or TCI states associated with a CORESET. [Figure 22] 1 illustrates an exemplary uplink repetition scheme for transmission of a transport block. [Figure 23] 1 illustrates an exemplary method for beam management. [Figure 24] 1 illustrates an exemplary method for beam management. [Figure 25] 1 illustrates an exemplary method for beam management. [Figure 26] 1 illustrates an exemplary method for transmission of a transport block. DETAILED DESCRIPTION OF THE INVENTION

[0007] The accompanying drawings and description provide examples. It should be understood that the examples shown and / or described in the drawings are non-exclusive, and that the features shown and described may be implemented in other examples. Examples are provided for the operation of a wireless communication system that may be used in the technical field of multi-carrier communication systems. More particularly, the technology disclosed herein may relate to transmission and / or reception configurations and signaling for wireless communication.

[0008] 1A illustrates an exemplary 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 / operated by a network operator. The communication network 100 may comprise 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 one or more data networks (DNs) 108, and / or devices within the communication network 100 may communicate with (e.g., the CN 102). 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 its interfacing function, 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, provide / configure charging functionality, etc.

[0009] The wireless device 106 may communicate with the RAN 104 via wireless communication over an 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 / through the air interface may be referred to as the 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 communication direction. The downlink transmission may be separated and / or distinguished from the uplink transmission 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.

[0010] As used throughout, the term "wireless device" may include one or more of a mobile device, a fixed (e.g., non-mobile) device configured or enabled for wireless communication, a computing device, a node, a wireless communication capable 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 road side unit (RSU), a relay node, an automobile, a wireless user device (e.g., user equipment (UE)), a user terminal (UT), an access terminal (AT), a mobile station, a handset, a wireless transmit and receive unit (WTRU), a wireless communication device, and / or any combination thereof.

[0011] The RAN 104 may comprise 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), donor node (e.g., donor eNB, donor gNB, etc.), access point (e.g., Wi-Fi access point), transmission and reception point (TRP), computing device, wireless communication enabled device, or any other device capable of transmitting and / or receiving signals. A base station may comprise 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 be, for example, 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 connected to one or more remote radio heads (RRHs), a repeater node or relay node used to extend the coverage area of ​​a donor node, a Next Generation Evolved Node B (ng-eNB), a Generation Node B (gNB) (e.g., associated with NR and / or fifth-generation (5G) standards), an access point (AP), or a wireless LAN (WAN). The base station may comprise one or more of a gNB Central Point (AP) (e.g., associated with, for example, Wi-Fi or any other suitable wireless communication standard), any other generation base station, and / or any combination thereof. The base station may include one or more devices such as at least one base station central equipment (e.g., a gNB Central Unit (gNB-CU)) and at least one base station distribution equipment (e.g., a gNB Distributed Unit (gNB-DU)).

[0012] A base station (e.g., in the RAN 104) may include one or more sets of antennas for communicating wirelessly (e.g., over an air interface) with wireless devices 106. One or more base stations may include a set (e.g., three sets or any other number of sets) of antennas 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 of the cells of a base station (e.g., alone or in combination with other cells) may provide / establish wireless coverage to wireless devices 106 over a wide geographic area to support wireless device mobility. A base station with 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).

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

[0014] 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 arranged 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 with high data traffic (or so-called "hot spots") or areas with 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.

[0015] The examples described herein may be used in various types of communications. For example, the communications may be communications by the Third-Generation Partnership Project (3GPP) (e.g., one or more network elements similar to those of communications network 100), communications by the Institute of Electrical and Electronics Engineers (IEEE), communications by the International Telecommunication Union (ITU), communications by the International Organization for Standardization (ISO), etc. 3GPP produces specifications for multiple generations of mobile networks, namely, 3G networks known as UMTS, 4G networks known as Long-Term Evolution (LTE) and LTE Advanced (LTE-A), and 5G networks known as 5G System (5GS) and NR System. 3GPP may produce specifications for further generations of communications networks (e.g., 6G and / or any other generation communications networks). Examples may be described in the context of one or more elements (e.g., RAN) of a 3GPP 5G network, referred to as next-generation RAN (NG-RAN), or any other communication network, such as a 3GPP network and / or a non-3GPP network. Examples described herein may be applicable to other communication networks, such as 3G and / or 4G networks, as well as communication networks not yet finalized / specified (e.g., a 3GPP 6G network), satellite communication networks, and / or any other communication network. NG-RAN may be provisioned to implement and upgrade 5G radio access technology, referred to as NR, and to implement other radio access technologies, such as 4G radio access technology and / or other 3GPP and / or non-3GPP radio access technologies.

[0016] FIG. 1B illustrates an exemplary communication network 150. The communication network may include a mobile communication network. The communication network 150 may comprise, for example, a PLMN operated / managed / executed by a network operator. The communication network 150 may comprise a CN 152 (e.g., a 5G core network (5G-CN)), a RAN 154 (e.g., an NG-RAN), and / or one or more wireless devices 156A and 156B (collectively, wireless devices 156). The communication network 150 may include one or more data networks (DNs) 170, and / or devices in the communication network 150 may communicate with one or more DNs 170 (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.

[0017] The CN 152 (e.g., 5G-CN) may provide / configure one or more interfaces to the wireless device 156 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 architecture of a node 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 function of the CN 152 (e.g., 5G CN) may be implemented in several ways, for example, as a network element on dedicated or shared hardware, as a software instance running on dedicated or shared hardware, and / or as a virtualized function instantiated on a platform (e.g., a cloud-based platform).

[0018] The CN 152 (e.g., 5G-CN) may comprise an Access and Mobility Management Function (AMF) device 158A and / or a User Plane Function (UPF) device 158B, which may be separate components or one 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 outer Protocol (or Packet) Data Unit (PDU) session point interconnecting 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.

[0019] The AMF device 158A may perform functions such as Non-Access Stratum (NAS) signaling termination, NAS signaling security, Access Stratum (AS) security control, inter-CN node signaling for mobility between access networks (e.g., 3GPP access networks and / or non-3GPP networks), idle mode wireless device reachability (e.g., idle mode UE reachability for controlling and performing paging retransmissions), registration area management, intra-system and inter-system mobility support, access authentication, access authorization including checking roaming rights, mobility management control (e.g., subscription and policy), 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.

[0020] CN 152 (e.g., 5G-CN) may comprise one or more additional network functions that may not be shown in Figure 1B. CN 152 (e.g., 5G-CN) may comprise one or more devices implementing 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.

[0021] The RAN 154 (e.g., NG-RAN) may communicate with the wireless device 156 over wireless communications (e.g., the air interface). The wireless device 156 may communicate with the CN 152 via the RAN 154. The RAN 154 (e.g., the NG-RAN) may comprise one or more base stations of a first type (e.g., gNBs including gNB 160A and gNB 160B (collectively gNB 160)) and / or one or more base stations of a second type (e.g., ng eNBs including ng-eNB 162A and ng-eNB 162B (collectively ng eNB 162)). The RAN 154 may comprise one or more base stations of any number of types. The gNBs 160 and ng eNB 162 may be referred to as base stations. The base stations (e.g., gNB 160 and ng eNB 162) may comprise one or more sets of antennas for communicating over wireless communications (e.g., the air interface) with the wireless device 156. One or more base stations (e.g., gNB 160 and / or ng eNB 162) may include multiple sets of antennas to respectively control multiple cells (or sectors). 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.

[0022] 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 a direct physical connection and / or an indirect connection via 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): The user plane may handle data of interest to users. The control plane may handle signaling messages of interest to network elements.

[0023] 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 be connected to UPF 158B of the AMF / UPF 158 via an NG-User plane (NG-U) interface. The NG-U interface may provide / perform 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 be connected 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), NAS message transfer, paging, PDU session management, configuration transfer, and / or alert message transmission.

[0024] 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 towards wireless device 156 via the Uu interface. A base station (e.g., gNB 160A) may provide user plane and control plane protocol terminations towards wireless device 156A via 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 towards wireless device 156 via the Uu interface (e.g., E UTRA may refer to a 3GPP 4G radio access technology). A base station (e.g., ng-eNB 162B) may provide UTRA user plane and control plane protocol terminations towards wireless device 156B via 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.

[0025] 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). It may also 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 balancing across multiple AMF / UPF nodes.

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

[0027] 1A and / or 150 of FIG. 1B may comprise any number / quantity 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., UEs). While reference may be made herein to one or more of the above types of devices (e.g., UEs, wireless devices, computing devices, 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 may be understood that one or more features and steps may be implemented in any device and / or any network.

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

[0029] A user plane configuration (e.g., an NR user plane protocol stack) may comprise multiple layers (e.g., five layers 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 higher 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 (PDCP) 214, and / or a service data application protocol (SDAP) 215. The 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 221 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.

[0030] 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. An SDAP (e.g., 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. A UPF (e.g., UPF 158B) of the CN 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 SDAPs 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 / demapping 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. In the case of reflected mapping, the SDAP 225 of the base station 220 may mark downlink packets with a QoS flow indicator (QFI) that can be monitored / detected / identified / indicated / observed by the SDAP 215 of the wireless device 210 to determine the mapping / demapping between one or more QoS flows 310 and radio bearers 320.

[0031] 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 packets that are not delivered, for example, due to handover (e.g., intra-gNB handover), in-order delivery and packet reordering, and / or removal of duplicately received packets. PDCPs 214 and 224 may perform packet duplication, for example, to improve the likelihood that a packet will be received. A receiver may receive packets duplicately and remove duplicate packets. Packet duplication may be useful for certain services, such as services that require high reliability.

[0032] The PDCP layer (e.g., PDCP 214 and 224) may perform mapping / demapping between a split radio bearer and an RLC channel (e.g., RLC channel 330) (e.g., in a dual connectivity scenario / configuration). Dual connectivity may refer to a technology that enables a wireless device to communicate with multiple cells (e.g., two cells) or, more generally, multiple cell groups including a master cell group (MCG) and a secondary cell group (SCG). 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, a split bearer may be configured and / or used. The PDCP 214 and 224 may map / demap between the split radio bearer belonging to the cell group and the RLC channel 330.

[0033] The RLC layer (e.g., RLC 213 and 223) may perform segmentation, retransmission, and / or removal of duplicate data units received from the MAC layer (e.g., MAC 212 and 222, respectively) via Automatic Repeat Request (ARQ). 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 described functions, for example, based on the transmission mode in which the RLC layer is operating. The RLC configuration may be per logical channel. The RLC configuration may be independent of numerology and / or Transmission Time Interval (TTI) duration (or other duration). The RLC layer (eg, RLC 213 and 223) may provide / configure RLC channels as services to the PDCP layer (eg, PDCP 214 and 224, respectively), as shown in FIG.

[0034] 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 / portions belonging to one or more logical channels to / from a transport block (TB) delivered to / from the PHY layer (e.g., PHY 211 and 221, respectively). The MAC layer of the base station (e.g., MAC 222) may be configured to perform scheduling, scheduling information reporting, and / or priority handling between wireless devices via dynamic scheduling. Scheduling may be performed by the base station (e.g., base station 220 at MAC 222) for the downlink and / or uplink. The MAC layer (e.g., MAC 212 and 222) may be configured to prioritize among the logical channels of the wireless device 210 via Hybrid Automatic Repeat Request (HARQ) (e.g., one HARQ entity per carrier in the case of Carrier Aggregation (CA)), logical channel prioritization, and / or padding. The MAC layer (e.g., MAC 212 and 222) may support one or more numerologies and / or transmission timings. Mapping restrictions in the logical channel prioritization may control which numerologies and / or transmission timings a logical channel may use. The MAC layer (e.g., MAC 212 and 222) may provide / configure the logical channels 340 as services to the RLC layer (e.g., RLC 213 and 223).

[0035] 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, coding / decoding and / or modulation / demodulation. The PHY layer (e.g., PHYs 211 and 221) may perform multi-antenna mapping. The PHY layer (e.g., PHYs 211 and 221) may provide / configure one or more transport channels (e.g., transport channel 350) as services to the MAC layer (e.g., MACs 212 and 222, respectively).

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

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

[0038] Each protocol layer (e.g., the protocol layers shown in FIG. 4A ), or at least some of the protocol layers, may perform its own function (e.g., one or more functions of each protocol layer described with respect to FIG. 3 ), add a corresponding header, and / or forward its 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 packet m 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 multiple RLC PDUs (MAC SDUs). The MAC 222 may attach a MAC subheader to the RLC PDU (MAC SDU) to form a TB. The MAC subheader may be distributed across the MAC PDU (e.g., in the NR configuration 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 latency, for example, if the MAC PDU subheader is calculated before assembling the complete MAC PDU.

[0039] 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 to indicate the length (e.g., in bytes) of the MAC SDU to which the MAC subheader corresponds; a logical channel identifier (LCID) field to identify / indicate the logical channel on which the MAC SDU originated to aid in the demultiplexing process; a flag (F) to indicate the size of the SDU length field; and a reserved bit (R) field for future use.

[0040] 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 to the beginning of a MAC PDU for downlink transmission (as shown in FIG. 4B). One or more MAC CEs may be inserted / appended to the end of a MAC PDU for uplink transmission. MAC CEs may be used for bandwidth control signaling. Exemplary MAC CEs may include scheduling-related MAC CEs such as buffer status reports and power headroom reports; activation / deactivation MAC CEs (e.g., MAC CEs for activating / deactivating PDCP duplicate detection, channel state information (CSI) reports, sounding reference signal (SRS) transmissions, and pre-configured components); discontinuous reception (DRX)-related MAC CEs; timing advance MAC CEs; and random access-related MAC CEs. A MAC CE may be preceded by a MAC subheader having a format similar to that described for the MAC subheader of a MAC SDU, and may be identified with a reserved value in the LCID field that indicates the type of control information contained in the corresponding MAC CE.

[0041] FIG. 5A shows an example mapping for downlink channels. Mapping of uplink channels may include mapping between channels (e.g., logical channels, transport channels, and physical channels) for the downlink. FIG. 5B shows an example mapping for uplink channels. Mapping of uplink channels may include mapping between channels (e.g., logical channels, transport channels, and physical channels) for the uplink. Information may be passed over / via channels between the RLC layer, MAC layer, and PHY layer of a protocol stack (e.g., an NR protocol stack). Logical channels may be used between the RLC layer and the MAC layer. Logical channels may be classified / designated as control channels (e.g., in an NR control plane) that may carry control and / or configuration information or as traffic channels (e.g., in an NR user plane) that may carry data. Logical channels may be classified / designated as dedicated logical channels that may be dedicated to a particular 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).

[0042] 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 comprise one or more channels described below. A paging control channel (PCCH) may include / transmit one or more paging messages used to page wireless devices whose locations are unknown to the network at the cell level. A broadcast control channel (BCCH) may include / transmit 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. A common control channel (CCCH) may include / transmit control messages along with random access. A dedicated control channel (DCCH) may include / transmit control messages to / from specific wireless devices to configure the wireless devices with configuration information. A dedicated traffic channel (DTCH) may include / transmit user data to / from specific wireless devices.

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

[0044] The PHY layer may use physical channels to pass / transfer information between processing levels of the PHY layer. 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 low-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 the NR configuration or any other configuration) may comprise one or more of the following channels: A physical broadcast channel (PBCH) may contain / carry the MIB from the BCH. A physical downlink shared channel (PDSCH) may contain / carry downlink data and signaling messages from the DL-SCH and paging messages from the PCH. The physical downlink control channel (PDCCH) may contain / 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 contain / carry uplink data and signaling messages from the UL-SCH, and possibly uplink control information (UCI), as described below.The physical uplink control channel (PUCCH) may comprise / transmit UCI, which may comprise a HARQ acknowledgement, a channel quality indicator (CQI), a pre-coding matrix indicator (PMI), a rank indicator (RI), and a scheduling request (SR). For random access, a physical random access channel (PRACH) may be used.

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

[0046] One or more of the channels (e.g., logical channels, transport channels, physical channels, etc.) may be used to perform functions associated with a control plan protocol stack (e.g., an NR control plane protocol stack). FIG. 2B illustrates an exemplary control plane configuration (e.g., an NR control plane protocol stack). As shown in FIG. 2B, the control plane configuration (e.g., an NR control plane protocol stack) may use one or more protocol layers (e.g., PHYs 211 and 221, MACs 212 and 222, RLCs 213 and 223, and PDCPs 214 and 224) that are substantially the same / similar to the exemplary user plane configuration (e.g., an NR user plane protocol stack). The four similar protocol layers may include PHYs 211 and 221, MACs 212 and 222, RLCs 213 and 223, and PDCPs 214 and 224. For example, instead of having SDAPs 215 and 225, 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). The control plane configuration may include an AMF 230 that includes the NAS protocol 237.

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

[0048] The RRC layers 216 and 226 may provide / configure control plane functionality between the wireless device 210 and the base station 220, and / or more generally, between the wireless device 210 and the RAN (e.g., the base station 220). The RRC layers 216 and 226 may provide / configure control plane functionality between the wireless device 210 and the base station 220 by signaling messages, which may be referred to as RRC messages. The RRC messages may be transmitted / transmitted 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 functions: broadcasting system information related to the AS and NAS; paging initiated by the CN or 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 reporting (e.g., wireless device measurement reporting) and reporting control; radio link failure (RLF) detection and recovery from radio link failure; and / or NAS message forwarding. As part of establishing an RRC connection, the RRC layers 216 and 226 may establish an RRC context, which may include setting parameters for communications between the wireless device 210 and the RAN (e.g., base station 220).

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

[0050] An RRC connection may be established for the wireless device. For example, this may be during an RRC connected state. During the RRC connected state (e.g., during RRC connected 602), the wireless device has an established RRC context and may have at least one RRC connection with a base station. The base station may be similar to one of one or more base stations (e.g., one or more base stations of the RAN 104 shown in FIG. 1A, one of the gNB 160 or ng-eNB 162 shown in FIG. 1B, the base station 220 shown in FIGS. 2A and 2B, or any other base station). The base station to which the wireless device is connected (e.g., has established an RRC connection) may have 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: AS context; radio link configuration parameters; bearer configuration information (e.g., for 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 its serving base station (e.g., the base station currently serving the wireless device). The serving base station of the wireless device may, for example, request a handover to a cell of one of the neighboring base stations 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.

[0051] 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 most of the time (e.g., to conserve battery power). The wireless device may wake up periodically (e.g., each 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 include a random access procedure.

[0052] 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. Maintaining the RRC context may enable / enable a fast transition to an RRC connected state (e.g., RRC connected 602) with reduced 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 may sleep, and the mobility of the wireless device may be managed / controlled by the wireless device via cell reselection. The RRC state may transition from the RRC inactive state (e.g., RRC inactive 604) to the 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, which may be the same as or similar to the connection release procedure 608.

[0053] The RRC states may be associated with mobility management mechanisms. 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 entire mobile communication network. The mobility management mechanism used during an RRC idle state (e.g., RRC idle 606) or an RRC inactive state (e.g., RRC inactive 604) may enable / allow the network to track the wireless device at a cell group level (e.g., instead of sending a paging message throughout the entire mobile communication network), for example, so that a paging message may be broadcast through cells of the cell group in which the wireless device currently resides. Mobility management mechanisms for 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, for example, perform tracking using 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)).

[0054] 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 a wireless device registration area (e.g., UE registration area) 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 and provide the wireless device with a new UE registration area, for example, when the wireless device moves (e.g., via cell reselection) to a cell associated with a TAI that may not be included in the list of TAIs associated with the UE registration area.

[0055] 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 / provided / configured with 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. For example, if the wireless device moves (e.g., via cell reselection) to a cell that is not included in the RAN notification area assigned / provided / configured to the wireless device, the wireless device may perform a notification area update with the RAN to update the RAN notification area of ​​the wireless device.

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

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

[0058] Physical signals and physical channels (e.g., those described with reference to FIGS. 5A and 5B ) may be mapped to 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 / transmits data over F orthogonal subcarriers (or tones). For example, before transmitting the data, the data may be mapped to a series of complex symbols called source symbols (e.g., M-quadrature amplitude modulation (M-QAM) symbols or M-phase shift keying (M-PSK) symbols or any other modulation symbols) and split into F parallel symbol streams. 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 the F source symbols at a time, one 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 F sinusoidal basis functions corresponding to the F orthogonal subcarriers. The output of the IFFT block may be F time-domain samples representing the 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 / transmitted over an 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 be used by one or more wireless devices in the uplink to generate Discrete Fourier Transform (DFT) precoded OFDM symbols to reduce the peak to average power ratio (PAPR). Inverse processing may be performed on the OFDM symbols at the receiver using an FFT block to recover the data mapped to the source symbols.

[0059] FIG. 7 illustrates an exemplary configuration of a frame. A frame may comprise, 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 at 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 over any time interval.

[0060] 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 various deployments (e.g., from cells with carrier frequencies below 1 GHz to cells with carrier frequencies in the mmWave range). Flexible numerology may be supported, for example, 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 μs, for example, for numerology in an NR configuration or any other radio configuration. The numerology may be defined for the following subcarrier spacing / cyclic prefix duration combinations: 15 kHz / 4.7 μs; 30 kHz / 2.3 μs; 60 kHz / 1.2 μs; 120 kHz / 0.59 μs; 240 kHz / 0.29 μs, and / or any other subcarrier spacing / cyclic prefix duration combination.

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

[0062] FIG. 8 shows an example resource configuration of one or more carriers. This resource configuration may include slots in the time and frequency domains for an NR carrier or any other carrier. A slot may comprise a resource element (RE) and a resource block (RB). A resource element (RE) may be the smallest physical resource (e.g., in an NR configuration). An RE may span one OFDM symbol in the time domain by one subcarrier in the frequency domain, as illustrated in FIG. 8, for example. An RB may span 12 consecutive REs in the frequency domain, as illustrated in FIG. 8, for example. A carrier (e.g., an NR carrier) may be limited in width to a certain number of RBs and / or subcarriers (e.g., 275 RBs or 275 × 12 = 3300 subcarriers). If such limitations are used, carrier (e.g., NR carrier) frequencies may be limited 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 per carrier bandwidth limit. Any other bandwidth may be set based on a per-carrier bandwidth limit.

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

[0064] The configuration of one or more bandwidth portions (BWPs) may support one or more wireless devices that cannot receive the entire carrier bandwidth. The BWPs may support, for example, bandwidth adaptation for such wireless devices that cannot receive the entire carrier bandwidth. A BWP (e.g., a BWP in 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 at a given time, for example. 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.

[0065] 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., in the case of unpaired spectrum). A downlink BWP and an uplink BWP may be linked, for example, if the downlink BWP index of the downlink BWP and the uplink BWP index of the uplink BWP are the same. A wireless device may expect the center frequency of the downlink BWP to be the same as the center frequency of the uplink BWP (e.g., in the case of unpaired spectrum).

[0066] 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 within a set of configured downlink BWPs on a primary cell (PCell) or a secondary cell (SCell), for example. A search space may comprise a set of locations in the time and frequency domains where the wireless device may monitor / discover / detect / identify control information. The search space may be a wireless device-specific search space (e.g., a UE-specific search space) or a common search space (e.g., potentially usable by multiple wireless devices or a group of wireless user devices). The base station may configure a group of wireless devices with a common search space on a PCell or a primary secondary cell (PSCell) in an active downlink BWP.

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

[0068] 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 in the set of configured BWPs is the active downlink BWP for one or more downlink receptions. The value of the one or more BWP indicator fields may indicate the active uplink BWP for one or more uplink transmissions.

[0069] The base station may semi-statically configure the wireless device with a default downlink BWP within a set of configured downlink BWPs associated with the PCell. The default downlink BWP may be the initial active downlink BWP, for example, if the base station does not provide / configure a default downlink BWP for 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.

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

[0071] 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, after receiving (e.g., based on or in response to receiving) a DCI indicating the second BWP as the active BWP. The wireless device may switch the active BWP from a first BWP to a second BWP, for example, after (e.g., based on or in response to) expiration of a BWP inactivity timer (e.g., if the second BWP is a default BWP).

[0072] Switching a downlink BWP 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). Switching an uplink BWP 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). Switching between downlink BWPs and uplink BWPs may be performed independently (e.g., in paired spectrum / spectrum). Switching between downlink BWPs and uplink BWPs may be performed simultaneously (e.g., in unpaired spectrum / spectrum). Switching between configured BWPs may be based on, for example, RRC signaling, DCI signaling, BWP inactivity timer expiration, and / or random access initiation.

[0073] FIG. 9 shows an example of configured BWPs. Bandwidth adaptation using multiple BWPs (e.g., three configured BWPs for an NR carrier) may be available. A wireless device configured with multiple BWPs (e.g., three BWPs) may switch from one BWP to another at a switching 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 BWPs at a switching point. The wireless device may switch from BWP 902 to BWP 904 at switching point 908. The switching at switching point 908 may be performed for any suitable reason. The switch at switch point 908 may occur, for example, after expiration (e.g., based on or in response to) of a BWP inactivity timer indicating a switch to a default BWP. The switch at switch point 908 may occur, for example, after receiving a DCI indicating BWP 904 as the active BWP. The wireless device may switch from the active BWP 904 to BWP 906 at switch point 910, for example, after receiving or in response to receiving a DCI indicating BWP 906 as the new active BWP. The wireless device may switch from the active BWP 906 to BWP 904 at switch point 912, for example, after expiration (e.g., based on or in response to) of a BWP inactivity timer. The wireless device may switch from the active BWP 906 to BWP 904 at switch point 912, for example, after receiving or in response to receiving a DCI indicating BWP 904 as the new active BWP. The wireless device may switch from the active BWP 902 to BWP 902 at switching point 914, for example, after or in response to receiving a DCI indicating BWP 904 as the new active BWP.

[0074] A wireless device procedure for switching BWPs on a secondary cell may be the same / similar to the procedure on a primary cell, for example, if the wireless device is configured for a secondary cell with default downlink BWPs and timer values ​​in the set of configured downlink BWPs. The wireless device may use timer values ​​and default downlink BWPs for the secondary cell in the same / similar manner as the wireless device uses timer values ​​and / or default BWPs for the primary cell. Timer values ​​(e.g., BWP inactivity timers) 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, for example, based on the expiration of a BWP inactivity timer.

[0075] Two or more carriers may be aggregated to simultaneously transmit / transmit data to / from the same wireless device using carrier aggregation (CA) (e.g., to increase the data rate). The aggregated carriers in CA may be referred to as component carriers (CCs). For example, when CA is configured / used, there may be a number / quantity 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.

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

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

[0078] One of the aggregated cells of a wireless device may be referred to as a primary cell (PCell), for example, if CA is configured. The PCell may be a serving cell that the radio initially connects to or accesses during, for example, RRC connection establishment, RRC connection re-establishment, and / or handover. The PCell may provide / configure NAS mobility information and security inputs to the wireless device. A wireless device may have different PCells. For the downlink, a carrier corresponding to the PCell may be referred to as a downlink primary CC (DL PCC). For the uplink, a carrier corresponding to the PCell may be referred to as an uplink primary CC (UL PCC). Other aggregated cells for the 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 the PCell is configured for the wireless device. SCells may be configured via an RRC connection reconfiguration procedure. For the downlink, a carrier corresponding to an SCell may be referred to as a downlink secondary CC (DL SCC). For the downlink, a carrier corresponding to an SCell may be referred to as an uplink secondary CC (UL SCC).

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

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

[0081] 10B shows an example cell group. Aggregated 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: 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: PUCCH SCell (or PSCell) 1051 (e.g., DL SCC), SCell 1052 (e.g., DL SCC), and SCell 1053 (e.g., DL SCC). One or more uplink CCs of the PUCCH group 1010 may be configured as a PCell 1021 (e.g., a UL PCC), an SCell 1022 (e.g., a UL SCC), and an SCell 1023 (e.g., a UL SCC). One or more uplink CCs of the PUCCH group 1050 may be configured as a PUCCH SCell (or PSCell) 1061 (e.g., a UL SCC), an SCell 1062 (e.g., a UL SCC), and an SCell 1063 (e.g., a UL SCC). UCIs associated with the downlink CCs of the PUCCH group 1010, denoted as UCI 1031, UCI 1032, and UCI 1033, may be transmitted / transmitted via the uplink of the PCell 1021 (e.g., via the PUCCH of the PCell 1021). The UCIs associated with the downlink CCs of the PUCCH group 1050, denoted as UCI 1071, UCI 1072, and UCI 1073, may be transmitted / transmitted over the uplink of the PUCCH SCell (or PSCell) 1061 (eg, via the PUCCH of the PUCCH SCell 1061).A single uplink PCell may be configured to transmit / carry UCI related to six downlink CCs, for example, if the aggregated cell shown in Figure 10B is not divided into PUCCH group 1010 and PUCCH group 1050. PCell 1021 may be overloaded if, for example, UCIs 1031, 1032, 1033, 1071, 1072, and 1073 are transmitted / carried via PCell 1021. By splitting the transmission of UCI between PCell 1021 and PUCCH SCell (or PSCell) 1061, overloading may be prevented and / or reduced.

[0082] A PCell may comprise 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 / carried by 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 of a first downlink carrier may refer to the first physical cell ID of 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 comprising the first carrier.

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

[0084] For the downlink, a base station may transmit / transmit (e.g., unicast, multicast, and / or broadcast) one or more reference signals (RS) (e.g., PSS, SSS, CSI-RS, DM-RS, and / or PT-RS) to one or more wireless devices. For the uplink, one or more wireless devices may transmit / transmit one or more RSs to a base station (e.g., DM-RS, PT-RS, and / or SRS). The PSS and SSS are transmitted / transmitted 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 comprise a PSS, SSS, and PBCH. A base station may periodically transmit / transmit bursts of SS / PBCH blocks, which may be referred to as SSBs.

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

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

[0087] 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 a carrier for a PSS to find and select a cell, for example. The wireless device may monitor a frequency location within the carrier. If the wireless device does not find a PSS after a specific time duration (e.g., 20 ms), for example, the wireless device may search for a PSS at a different frequency location within the carrier. The wireless device may search for a PSS at a different frequency location within the carrier, for example, as indicated by a synchronization raster. If the PSS is found at a location in the time and frequency domains, the wireless device may determine the location of the SSS and PBCH, respectively, based on the known structure of the SS / PBCH block. The SS / PBCH block may be a cell-defining SS block (CD-SSB). The 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.

[0088] 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 position of a frame boundary of the cell, for example, based on the position of the SS / PBCH block. The SS / PBCH block may indicate that it was sent / transmitted 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).

[0089] 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 comprise / carry one or more DM-RS 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 comprise an MIB used to transmit / carry one or more parameters to the wireless device. The MIB may be used by the wireless device to find remaining minimum system information (RMSI) associated with the cell. The RMSI may include System Information Block Type 1 (SIB1). SIB1 may comprise 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 / contained in the MIB. The PBCH may indicate the absence of SIB1. The wireless device may be pointed to a frequency, for example, based on the PBCH indication of the absence of SIB1. The wireless device may search for SS / PBCH blocks on the frequency to which the wireless device is pointed.

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

[0091] For example, a base station may transmit multiple SS / PBCH blocks 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 at different frequency locations may be different or substantially the same.

[0092] The CSI-RS may be transmitted by a base station and used by a wireless device to acquire / obtain / determine channel state information (CSI). The base station may configure a wireless device with one or more CSI-RS for channel estimation or any other suitable purpose. The base station may configure a wireless device with one or more of the same / similar CSI-RS. The wireless device may measure one or more CSI-RS. The 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. The wireless device may transmit / transmit a CSI report to the base station (e.g., based on periodic CSI reporting, semi-persistent CSI reporting, and / or aperiodic CSI reporting). The base station may use feedback provided by the wireless device (e.g., estimated downlink channel conditions) to perform link adaptation.

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

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

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

[0096] A downlink DM-RS may be transmitted / transmitted by a base station and received / used by a wireless device for channel estimation. The downlink DM-RS may be used for coherent demodulation of one or more downlink physical channels (e.g., PDSCH). A network (e.g., an NR network) may support one or more variable and / or configurable DM-RS patterns for data demodulation. At least one downlink DM-RS configuration may support a frontloaded DM-RS pattern. The frontloaded DM-RS may be mapped to 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 / amount (e.g., maximum number / amount) 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. The base station may, for example, transmit / transmit the downlink DM-RS and corresponding PDSCH using the same precoding matrix. The wireless device may use one or more downlink DM-RSs for coherent demodulation / channel estimation of the PDSCH.

[0097] A transmitter (e.g., a base station transmitter) may use a precoder matrix for a portion of a transmission bandwidth. The transmitter may use a first precoder matrix for a first bandwidth and a second precoder matrix for a second bandwidth. The first precoder matrix and the second precoder matrix may differ based on, for example, 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 / instantiated / identified / denoted as a precoding resource block group (PRG).

[0098] The PDSCH may include one or more layers. The 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 DMRSs for the PDSCH). The downlink PT-RS is transmitted / transmitted by the base station and may be used by the wireless device, for example, for phase noise compensation. Whether a downlink PT-RS is present may depend on the RRC configuration. The presence and / or pattern of the downlink PT-RS may be configured on a wireless device-specific basis, 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)) that may be indicated by DCI. The dynamic presence of the downlink PT-RS may be associated with one or more DCI parameters, including at least the MCS, if configured. A network (e.g., an NR network) may support multiple PT-RS densities defined in the time domain and / or the 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 DM-RS ports and PT-RS ports. The number / quantity of PT-RS ports may be less than the number / quantity of DM-RS ports in the scheduled resources. The downlink PT-RS may be configured / allocated / restricted in the scheduled time / frequency duration for the wireless device. The downlink PT-RS may be transmitted / transmitted via symbols, for example, to facilitate phase tracking at the receiver.

[0099] A wireless device may transmit / transmit an uplink DM-RS to a base station, for example, for channel estimation. The base station may use the uplink DM-RS for coherent demodulation of one or more uplink physical channels. The wireless device may transmit / transmit an uplink DM-RS on a PUSCH and / or a PUCCH. The uplink DM-RS may span a frequency range similar to the frequency range associated with the corresponding physical channel. The base station may configure the 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 across 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, which the wireless device may use to schedule single-symbol DM-RS and / or dual-symbol DM-RS. A network (e.g., an NR network) may support a common DM-RS structure for the downlink and uplink (e.g., in the case of cyclic prefix orthogonal frequency division multiplexing (CP-OFDM)). The DM-RS positions, DM-RS patterns, and / or DM-RS scrambling sequences may be substantially the same or different.

[0100] The PUSCH may include one or more layers. A wireless device may transmit / transmit at least one symbol with a DM-RS present in one or more layers of the PUSCH. Higher layers may configure one or more DM-RSs (e.g., up to three DMRSs) for the PUSCH. An uplink PT-RS (which may be used by a base station for phase tracking and / or phase noise compensation) may be present or absent, for example, depending on the RRC configuration of the wireless device. The presence and / or pattern of the uplink PT-RS may be configured on a wireless device-specific basis (e.g., a UE-specific basis) by a combination of one or more parameters configured / adopted for other purposes (e.g., MCS) that may be indicated by RRC signaling and / or DCI. The dynamic presence of the uplink PT-RS may be associated with one or more DCI parameters, including at least MCS, if configured. 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 number / quantity of PT-RS ports may be less than the number / quantity of DM-RS ports within the scheduled resources. The uplink PT-RS may be configured / allocated / restricted within the scheduled time / frequency duration of the wireless device.

[0101] One or more SRSs may be sent / transmitted by a wireless device to a base station, for example, for channel condition estimation to support uplink channel-dependent scheduling and / or link adaptation. The SRS sent / transmitted by the wireless device may enable the base station to estimate uplink channel conditions in one or more frequencies. A scheduler in the base station may use the estimated uplink channel conditions to allocate one or more resource blocks for uplink PUSCH transmission for the wireless device. The base station may semi-statically configure the 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 one or more SRS resource sets (e.g., with the same / similar time-domain behavior, periodic, aperiodic, etc.) may be sent / transmitted at a certain point in time (e.g., simultaneously), for example, if higher layer parameters indicate beam management. A wireless device may transmit / transmit one or more SRS resources in an SRS resource set. A network (e.g., an NR network) may support aperiodic, periodic, and / or semi-persistent SRS transmission. A wireless device may transmit / transmit an SRS resource, 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 / employed by a wireless device to select at least one of one or more configured SRS resource sets. SRS trigger type 0 may refer to an SRS triggered based on higher layer signaling. SRS trigger type 1 may refer to an SRS triggered based on one or more DCI formats. A wireless device may be configured to transmit / transmit an SRS after transmission of a PUSCH and a corresponding uplink DM-RS, for example, when the PUSCH and SRS are transmitted / transmitted in the same slot.The base station may semi-statically configure the wireless device with one or more SRS configuration parameters indicating at least one of the following: an SRS resource configuration identifier; the number of SRS ports; the 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; the offset of the periodic and / or aperiodic SRS resources; the number of OFDM symbols in the SRS resource; the starting OFDM symbol of the SRS resource; the SRS bandwidth; the frequency hopping bandwidth; the cyclic shift; and / or the SRS sequence ID.

[0102] Antenna ports may be determined / defined such that a channel on which a symbol on an antenna port is carried can be inferred from a channel on which another symbol on the same antenna port is carried. For example, when a first symbol and a second symbol are transmitted / transmitted on the same antenna port, a receiver may infer / determine a channel (e.g., fading gain, multipath delay, etc.) on which a second symbol on an antenna port is carried from a channel on which a first symbol on the antenna port is carried. For example, a first antenna port and a second antenna port may be referred to as quasi-colocated (QCLed) if one or more large-scale characteristics of a channel on which a first symbol on the first antenna port is carried can be inferred from a channel on which a second symbol on the second antenna port is carried. The one or more large-scale characteristics may include at least one of the following: delay spread; Doppler spread; Doppler shift; average gain; average delay; and / or spatial receive (Rx) parameters.

[0103] 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 beamformed reference signals. A wireless device may, for example, perform downlink beam measurements based on one or more downlink reference signals (e.g., CSI-RS) and generate a beam measurement report. A wireless device may perform a downlink beam measurement procedure, for example, after an RRC connection with a base station is set up.

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

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

[0106] CSI-RS (e.g., CSI-RS 1101, 1102, 1103) may be transmitted / transmitted by a base station and used by a wireless device for one or more measurements. The wireless device may measure 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 using an Rx beam determined based on the one or more TCI states. The wireless device may or may not have beam-capable capability. If the wireless device has beam-capable capability, the wireless device may determine a spatial domain filter of a transmit (Tx) beam, for example, based on the spatial domain filter of a corresponding Rx beam. The wireless device may perform an uplink beam selection procedure to determine a spatial domain filter for a Tx beam, for example, if the wireless device does not have beam-enabled capability. The wireless device may perform the uplink beam selection procedure based on, for example, one or more sounding reference signal (SRS) resources configured to the wireless device by a base station. The base station may select and instruct an uplink beam for the wireless device based on, for example, measurements of one or more SRS resources transmitted / transmitted by the wireless device.

[0107] 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 links may include a Tx beam of the base station and an Rx beam of the wireless device. The Tx beam of the base station may transmit / transmit downlink signals, and the Rx beam of the wireless device may receive downlink signals. The wireless device may transmit / transmit 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 identification information (e.g., beam index, reference signal index, etc.), RSRP, precoding matrix indicator (PMI), channel quality indicator (CQI), and / or rank indicator (RI).

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

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

[0110] A wireless device may initiate / start / perform a beam failure recovery (BFR) procedure, for example, based on detecting a beam failure. A wireless device may send / transmit a BFR request (e.g., a preamble, UCI, SR, MAC CE, etc.) based on initiating a BFR procedure. A wireless device may detect beam failure, for example, based on determining that the beam-to-link quality 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 timeout, etc.).

[0111] A wireless device may measure the quality of a beam-pair link using one or more reference signals (RSs) comprising, 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 QCL'd with one or more DM-RSs of a channel (e.g., a control channel, a shared data channel, etc.). An RS resource and one or more DM-RSs of a channel may be QCL'd, for example, if channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameters, fading, etc.) from a transmission to the wireless device over the RS resource are similar or the same as channel characteristics from a transmission to the wireless device over the channel.

[0112] A network (e.g., an NR network including a gNB and / or an ng-eNB) and / or a wireless device may initiate / initiate / 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 a connection setup to the network. A wireless device may initiate / initiate / perform a random access procedure from an RRC connected (e.g., RRC_CONNECTED) state. A wireless device may initiate / initiate / 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 to acquire / obtain / determine uplink timing (e.g., when the uplink synchronization state is asynchronous). A wireless device may initiate / initiate / perform a random access procedure to request one or more system information blocks (SIBs) (e.g., other system information blocks such as SIB2, SIB3, etc.). A wireless device may initiate / initiate / perform a random access procedure for a beam failure recovery request. The network may initiate / start / perform a random access procedure, for example, for handover and / or to establish time alignment for SCell addition.

[0113] 13A shows an exemplary four-step random access procedure. The four-step random access procedure may include a four-step contention-based random access procedure. A base station may, for example, send / transmit a configuration message 1310 to a wireless device before initiating the random access procedure. The four-step random access procedure may include transmission of 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 comprise a preamble (or a random access preamble). The first message (e.g., Msg 1 1311) may be referred to as a preamble. The second message (e.g., Msg 2 1312) may comprise a random access response (RAR). The second message (e.g., Msg 2 1312) may be referred to as a RAR.

[0114] The configuration message 1310 may be sent / transmitted, for example, using one or more RRC messages. The one or more RRC messages may indicate one or more random access channel (RACH) parameters to the wireless device. The one or more RACH parameters may comprise at least one of: general parameters for one or more random access procedures (e.g., RACH-configGeneral); cell-specific parameters (e.g., RACH-ConfigCommon); and / or dedicated parameters (e.g., RACH-configDedicated). The base station may send / transmit (e.g., broadcast or multicast) one or more RRC messages to one or more wireless devices. The one or more RRC messages may be wireless device-specific. The wireless device-specific one or more RRC messages may be, for example, dedicated RRC messages sent / transmitted to the wireless device in an RRC connected (e.g., RRC_CONNECTED) state and / or an RRC inactive (e.g., RRC_INACTIVE) state. The wireless device may determine time-frequency resources and / or uplink transmit power for transmission of the first message (e.g., Msg 1 1311) and / or the third message (e.g., Msg 3 1313) based on one or more RACH parameters. The wireless device may determine receive timing and downlink channels for receiving the second message (e.g., Msg 2 1312) and the fourth message (e.g., Msg 4 1314) based on, for example, one or more RACH parameters.

[0115] 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 transmission of 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 number / quantity of SS / PBCH blocks mapped to the PRACH opportunities and / or the number / quantity of preambles mapped to the SS / PBCH blocks.

[0116] One or more RACH parameters provided / configured / included in the configuration message 1310 may be used to determine the uplink transmission 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 for 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 ramp 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, for example, one or more thresholds based on which the wireless device may determine at least one reference signal (e.g., SSB and / or CSI-RS) and / or uplink carrier (e.g., normal uplink (NUL) carrier and / or supplemental uplink (SUL) carrier).

[0117] The first message (e.g., Msg 1 1311) may comprise 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., A group and / or B group). 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 a 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.

[0118] 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 a size of the third message (e.g., Msg 3 1313). The one or more RACH parameters may indicate a preamble format; a maximum number of preamble transmissions; and / or one or more thresholds for determining one or more preamble groups (e.g., A group and B group). The base station may use the one or more RACH parameters to 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). The wireless device may determine the preamble to be included in the first message (e.g., Msg 1 1311) based on, for example, the association, if configured. The first message (e.g., Msg 1 1311) may be transmitted / transmitted to the base station via one or more PRACH opportunities. A wireless device may use one or more reference signals (e.g., SSB and / or CSI-RS) for preamble selection and PRACH opportunity determination. One or more RACH parameters (e.g., ra-ssb-OccasionMskIndex and / or ra-Occasion list) may indicate an association between a PRACH opportunity and one or more reference signals.

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

[0120] The second message (e.g., Msg 2 1312) (e.g., received by the wireless device) may comprise an RAR. The second message (e.g., Msg 2 1312) may comprise multiple RARs corresponding to multiple wireless devices. The second message (e.g., Msg 2 1312) may be received, for example, after (e.g., based on or 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 using, for example, 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 comprise a time alignment command, a scheduling grant for transmission of the third message (e.g., Msg 3 1313), and / or a Temporary Cell RNTI (TC-RNTI), which may be used by the wireless device to adjust its transmission timing. The wireless device may, for example, determine / start a time window (e.g., ra-ResponseWindow) for monitoring 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 on, for example, the PRACH opportunity the wireless device uses to transmit / transmit the first message (e.g., Msg 1 1311) (e.g., a preamble). The wireless device may start in the time window one or more symbols after the last symbol of the first message (e.g., Msg 1 1311) comprising the preamble (e.g., the symbol in which the first message (e.g., Msg 1 1311) including the preamble transmission is completed or in the first PDCCH opportunity from the end of the preamble transmission).The one or more symbols may be determined based on numerology. The PDCCH may be mapped to a common search space (e.g., Type 1-PDCCH common search space) configured by an RRC message. The wireless device may identify / determine the 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 / initiate a random access procedure. The wireless device may use the RA-RNTI, for example, for one or more communications associated with 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. The 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 exemplary RA-RNTI may be determined as follows: RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id where s_id may be the index of the first OFDM symbol of the PRACH opportunity (e.g., 0≦s_id<14), t_id may be the index of the first slot of the PRACH opportunity in the system frame (e.g., 0≦t_id<80), f_id may be the index of the PRACH opportunity in the frequency domain (e.g., 0≦f_id<8), and ul_carrier_id may be the UL carrier used for preamble transmission (e.g., 0 for NUL carrier and 1 for SUL carrier).

[0121] For example, after (e.g., based on or in response to) successful reception of the second message (e.g., Msg 2 1312), the wireless device may send / transmit a third message (e.g., Msg 3 1313) (e.g., using 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 send / transmit the same preamble to a base station, and the base station may send / transmit an RAR corresponding to the wireless device. For example, if multiple wireless devices interpret the RAR as corresponding to themselves, a collision may occur. 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 identification information of another wireless device. The wireless device may include a device identifier (e.g., a C-RNTI if assigned, a TC-RNTI included in the second message (e.g., Msg 2 1312), and / or any other suitable identifier) ​​in the third message (e.g., Msg 3 1313), for example, to perform contention resolution.

[0122] The fourth message (e.g., Msg 4 1314) may be received, for example, after (e.g., based on or in response to) the transmission / transmission of the third message (e.g., Msg 3 1313). The base station may address the radio on a 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 have completed successfully, 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). 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 not connected to a base station), a fourth message (e.g., Msg 4 1314) may be received using the DL-SCH associated with the TC RNTI. For example, if the MAC PDU is successfully decoded and includes a wireless device contention resolution identity MAC CE that matches or otherwise corresponds to the CCCH SDU sent / transmitted 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.

[0123] The wireless device may be configured with an SUL carrier and / or a NUL carrier. Initial access (e.g., random access) may be supported over the uplink carrier. The base station may configure the 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 to use (NUL or SUL). 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 performed over the selected carrier. The wireless device may switch uplink carriers during the random access procedure (e.g., between Msg 1 1311 and Msg 3 1313). The 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).

[0124] 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, the base station may send / transmit a configuration message 1320 to the wireless device before the procedure begins. The configuration message 1320 may be similar in some respects to the configuration message 1310. The procedure illustrated in FIG. 13B may include the transmission of two messages: a first message (e.g., 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. The 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).

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

[0126] The wireless device may start a time window (e.g., ra-ResponseWindow) to monitor the PDCCH for RAR, for example, after transmitting / transmitting a preamble (e.g., based on or in response to the transmission / transmission). 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 within 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 a beam failure recovery request (e.g., the window may start any number of symbols and / or slots after transmitting the beam failure recovery request). The wireless device may monitor PDCCH transmissions addressed to a cell RNTI (C-RNTI) over 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, after transmitting a first message (e.g., Msg 1 1321) and receiving a corresponding second message (e.g., Msg 2 1322) (e.g., based on or in response thereto). The wireless device may determine that the random access procedure is successfully completed, for example, if a PDCCH transmission is addressed to the corresponding C-RNTI. The wireless device may determine that the random access procedure is successfully completed, for example, if the wireless device receives an RAR comprising a preamble identifier corresponding to a preamble sent / transmitted by the wireless device and / or if the RAR comprises a MAC sub-PDU comprising the preamble identifier. The wireless device may determine this response as an indication of an acknowledgement to the SI request.

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

[0128] 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 a preamble 1341 and / or one or more transmissions of a transport block 1342. The transport block 1342 may include content similar and / or equivalent to the content of a third message (e.g., Msg 3 1313) (e.g., shown in FIG. 13A). The transport block 1342 may include UCI (e.g., SR, HARQ ACK / NACK, etc.). The wireless device may receive a second message (e.g., Msg B 1332) after (e.g., based on or 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).

[0129] A wireless device may initiate / initiate a two-step random access procedure for licensed and / or unlicensed spectrum (e.g., the two-step random access procedure shown in FIG. 13C). The wireless device may determine whether to initiate / 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, etc.); 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 or unlicensed); and / or any other suitable factor.

[0130] The wireless device may determine radio resources and / or uplink transmit power for the preamble 1341 and / or transport block 1342 based on two-stage RACH parameters included in the configuration message 1330 (e.g., included in the first message (e.g., Msg A 1331)). The RACH parameters may indicate MCS, time-frequency resources, and / or power control for the preamble 1341 and / or transport block 1342. The time-frequency resources (e.g., PRACH) for transmission of the preamble 1341 and the time-frequency resources (e.g., PUSCH) for transmission of the transport block 1342 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).

[0131] The transport block 1342 may include data (e.g., delay-sensitive data), a wireless device identifier, security information, and / or device information (e.g., International Mobile Subscriber Identity (IMSI)). The base station may send / transmit a second message (e.g., 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 (e.g., transport block 1342), for example, if the preamble identifier in the second message (e.g., Msg B 1332) corresponds to or matches the preamble sent / transmitted by the wireless device and / or the identifier of the wireless device in the second message (e.g., Msg B 1332), or corresponds to or matches the identifier of the wireless device in the first message (e.g., Msg A 1331).

[0132] 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 / transmitted from a base station to a wireless device and / or uplink control signaling transmitted / transmitted from a wireless device to a base station.

[0133] The downlink control signaling may include at least one of: a downlink scheduling assignment; an uplink scheduling grant indicating uplink radio resources and / or a transport format; slot format information; a preemption indication; a power control command; and / or any other suitable signaling. A wireless device may receive the downlink control signaling in a payload transmitted / transmitted by a base station via a PDCCH. The payload transmitted and received 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.

[0134] The base station may, for example, append one or more cyclic redundancy check (CRC) parity bits to the DCI to facilitate detection of transmission errors. The base station may, for example, scramble the CRC parity bits with an identifier of the wireless device (or an identifier of a group of wireless devices) 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.

[0135] 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 dynamically scheduled unicast transmission and / or a triggering of a PDCCH ordered random access. A DCI with CRC parity bits scrambled with the temporary cell RNTI (TC-RNTI) may indicate contention resolution (eg, Msg 3 similar to Msg 3 1313 shown in FIG. 13A).Other RNTIs configured for a wireless device by a base station may include a Configured Scheduling RNTI (CS RNTI), a Transmit Power Control PUCCH RNTI (TPC PUCCH-RNTI), a Transmit Power Control PUSCH RNTI (TPC-PUSCH-RNTI), a Transmit Power Control SRS RNTI (TPC-SRS-RNTI), an Interruption RNTI (INT-RNTI), a Slot Format Indication RNTI (SFI-RNTI), a Semi-Persistent CSI RNTI (SP-CSI-RNTI), a Modulation and Coding Scheme Cell RNTI (MCS-C RNTI), etc.

[0136] A base station may transmit / transmit DCI in one or more DCI formats, for example, depending on 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., with a compact DCI payload). DCI format 0_1 ​​may be used for scheduling a PUSCH in a cell (e.g., with 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., with a compact DCI payload). DCI format 1_1 may be used for scheduling a PDSCH in a cell (e.g., with a larger DCI payload than DCI format 1_0). DCI format 2_0 may be used to provide slot format indication to a group of wireless devices. DCI format 2_1 may be used to signal / indicate physical resource blocks and / or OFDM symbols to a group of wireless devices, which may assume that no transmission to the group of wireless devices is intended. DCI format 2_2 may be used for transmission of transmit power control (TPC) commands for PUCCH or PUSCH. DCI format 2_3 may be used for transmission of 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 may share the same DCI size.

[0137] The base station may process the DCI with 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 to resource elements used and / or configured for the PDCCH. The base station may transmit / transmit the DCI via the PDCCH occupying several consecutive control channel elements (CCEs), for example, based on the payload size of the DCI and / or the base station's coverage. 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 several (e.g., 6) resource-element groups (REGs). A REG may comprise a resource block within an OFDM symbol. The mapping of the coded and modulated DCI to resource elements may be based on a mapping of CCEs and REGs (e.g., a mapping from CCEs to REGs).

[0138] 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 / transmit DCI via a PDCCH on one or more control resource sets (CORESETs). A CORESET may comprise time-frequency resources in which a wireless device attempts / 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. A first CORESET 1401 and a second CORESET 1402 may occur or be configured / configured at the first symbol in a slot. The first CORESET 1401 may overlap with the second CORESET 1402 in the frequency domain. A third CORESET 1403 may occur or be configured / configured at the third symbol in a slot. A fourth CORESET 1404 may occur or be configured / configured at the seventh symbol in a slot. The CORESETs may have different numbers of resource blocks in the frequency domain.

[0139] FIG. 14B shows an example of CCE-to-REG mapping. CCE-to-REG mapping may be performed for DCI transmission with 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 the same CCE-to-REG mapping for different CORESETs. A CORESET may be associated with a CCE-REG mapping (e.g., by RRC configuration). A CORESET may be configured with an antenna port QCL parameter. The antenna port QCL parameter may indicate QCL information of a DM-RS for PDCCH reception via a CORESET.

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

[0141] As shown in FIG. 14B , the wireless device may determine time-frequency resources for the CORESET based on one or more RRC messages. The wireless device may determine a CCE-to-REG mapping (e.g., interleaved or non-interleaved, and / or mapping parameters) for the CORESET based on, for example, configuration parameters of the CORESET. The wireless device may determine the number of search space sets (e.g., up to 10) configured for the CORESET based on, for example, 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 having 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 that the DCI is valid for the wireless device, for example, after (e.g., based on or in response to) a CRC check (e.g., scrambling bits for 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, etc.).

[0142] The wireless device may send / transmit uplink control signaling (e.g., UCI) to the base station. The uplink control signaling may comprise a HARQ acknowledgment for a received DL-SCH transport block. The wireless device may send / transmit the HARQ acknowledgment, for example, after receiving (e.g., based on or in response to) the DL-SCH transport block. The uplink control signaling may comprise CSI indicating channel quality of a 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 multi-antenna and beamforming schemes) for 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 the PUSCH. A wireless device may transmit / carry uplink control signaling over the PUCCH using one of several PUCCH formats.

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

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

[0145] For example, the wireless device may determine a PUCCH resource set from multiple PUCCH resource sets and then 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 based on, for example, a PUCCH resource indicator in DCI received on / via a PDCCH (e.g., with DCI of DCI format 1_0 or 1_1). An n-bit (e.g., 3-bit) PUCCH resource indicator in the DCI may indicate one of multiple (e.g., 8) PUCCH resources in the PUCCH resource set. Based on, for example, the PUCCH resource indicator, the wireless device may transmit / transmit UCI (HARQ-ACK, CSI, and / or SR) using the PUCCH resource indicated by the PUCCH resource indicator in the DCI.

[0146] 15A shows exemplary 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 any other 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.

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

[0148] For the downlink, data to be 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 to be 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 FIGS. 2A, 2B, 3, and 4A. Layer 3 may include, for example, the RRC layer described with respect to FIG. 2B.

[0149] Data to be transmitted to wireless device 1502 may be processed by, for example, processing system 1508 and then provided / forwarded / transmitted to transmission processing system 1510 of base station 1504. Data to be transmitted to base station 1504 may be processed by, for example, processing system 1518 and then provided / forwarded / transmitted to transmission processing system 1520 of wireless device 1502. Transmission processing system 1510 and transmission processing system 1520 may implement Layer 1 OSI functions. Layer 1 may comprise, for example, the PHY layer described in connection with FIGS. 2A, 2B, 3, and 4A. For transmission / transmission processing, the PHY layer may perform, for example, forward error correction coding of transport channels, interleaving, rate matching, mapping of transport channels to physical channels, modulation of physical channels, multiple-input multiple-output (MIMO) or multi-antenna processing, etc.

[0150] 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 comprise 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 comprise 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 in connection with 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, etc.

[0151] The base station 1504 may be equipped with multiple antennas (e.g., multiple antenna panels, multiple TRPs, etc.). The wireless device 1502 may be equipped with 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.

[0152] Processing system 1508 and processing system 1518 may be associated with memory 1514 and memory 1524, respectively. Memory 1514 and memory 1524 (e.g., one or more non-transitory computer-readable media) may store computer program instructions or code that may be executed by processing system 1508 and / or processing system 1518, respectively, to perform one or more of the functions (e.g., one or more functions described herein, as well as 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.

[0153] Processing system 1508 and / or processing system 1518 may comprise one or more controllers and / or one or more processors. The one or more controllers and / or one or more processors may 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. Processing system 1508 and / or 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 wireless device 1502 and / or base station 1504 to operate in a wireless environment.

[0154] The processing system 1508 may be connected to one or more peripherals 1516. The processing system 1518 may be connected to one or more peripherals 1526. The one or more peripherals 1516 and the one or more peripherals 1526 may comprise software and / or hardware that provides functionality and / or capabilities such as, for example, 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 modulated (FM) radio unit, a media player, an internet browser, an electronic control unit (e.g., for an automobile), 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, etc.). Processing system 1508 and / or processing system 1518 may receive input data (e.g., user input data) from one or more peripherals 1516 and / or one or more peripherals and / or provide output data (e.g., user output data) to one or more peripherals 1526. Processing system 1518 in wireless device 1502 may be configured to receive power from a power source and / or distribute this power to other components in wireless device 1502. The power source may include one or more power sources, such as batteries, solar cells, fuel cells, or any combination thereof. Processing system 1508 may be connected to a Global Positioning System (GPS) chipset 1517. Processing system 1518 may be connected to a Global Positioning System (GPS) chipset 1527. GPS chipset 1517 and GPS chipset 1527 may be configured to determine and provide geographic location information for wireless device 1502 and base station 1504, respectively.

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

[0156] While the example of FIG. 15B may be a hardware configuration, the components shown may be implemented as software. Changes may be made to add, remove, combine, divide, etc., components of computing device 1530 as desired. 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 subordinate entities, both of which may run as software on a common computing device).

[0157] FIG. 16A shows an example structure for uplink transmission. Processing of a baseband signal representing a physical uplink shared channel may comprise / perform one or more functions. The one or more functions may include at least one of the following: scrambling; modulation of scrambled bits to generate complex-valued symbols; mapping of complex-valued modulation symbols to one or several transmission layers; transform precoding to generate complex-valued symbols; precoding of complex-valued symbols; mapping of precoded complex-valued symbols to resource elements; generation of a complex-valued time-domain Single Carrier-Frequency Division Multiple Access (SC-FDMA), CP-OFDM signal for an antenna port, or any other signal. 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.

[0158] 16B shows an exemplary structure for modulating and upconverting 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 / used, for example, before transmission.

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

[0160] 16D shows an exemplary structure for modulating and upconverting 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 / used, for example, before transmission.

[0161] A wireless device may receive one or more messages (e.g., RRC messages) comprising configuration parameters for multiple cells (e.g., a primary cell, one or more secondary cells) from a base station. The wireless device may communicate with at least one base station (e.g., two or more base stations in 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.

[0162] A timer may, for example, begin running when started and may continue running until stopped or terminated. A timer may, for example, be started if not running and restarted if running. A timer may be associated with a value (e.g., a timer may start or restart from a value, or may start from 0 and terminate when the value is reached). The duration of a timer may not be updated, for example, until the timer is stopped or terminated (e.g., due to a BWP switch). A timer may be used to measure a period / window of a process. With regard to implementations and / or procedures related to one or more timers or other parameters, it may be understood that there may be multiple ways to implement one or more timers or other parameters. One or more of multiple ways to implement a timer may be used to measure the period / window of a procedure. A random access response window timer may be used to measure a time window for receiving a random access response. The time difference between two timestamps may, for example, be used instead of starting a random access response window timer and determining the timer timeout. The process for measuring the time window may be restarted, for example, if the timer is restarted. Other example implementations may be configured / provided to restart the measurement of the time window.

[0163] A wireless device may communicate via multiple TRPs. A wireless device may communicate via multiple TRPs using transmission repetition. For example, a wireless device may transmit repetitions of a transport block via a PUSCH using PUSCH repetition. A wireless device may use multiple different spatial domain transmit filters / beams for spatial diversity in transmission repetition. A wireless device may transmit a transport block and / or a first repetition of a transport block to a first TRP using a first spatial domain transmit filter / beam and a second repetition of the transport block to a second TRP using a second spatial domain transmit filter / beam. Using multiple different spatial domain transmit filters may increase the reliability and robustness of uplink transmissions.

[0164] The wireless device may determine a spatial domain transmit filter based on a base station configuration. The base station may configure a single SRI field (e.g., for a configured uplink grant). The SRI field may indicate an SRS resource within an SRS resource set. The wireless device may determine a single spatial domain transmit filter / beam based on a spatial relationship activated for the SRS resource. The wireless device may transmit a transport block (e.g., a repetition of a transport block) using the single spatial domain transmit filter / beam. If only a single spatial domain transmit filter can be configured by the base station, transmission repetition for communicating over multiple TRPs (e.g., using spatial diversity) cannot be supported.

[0165] Various examples herein may facilitate the configuration and use of multiple beams for communicating over multiple TRPs. A wireless device may transmit a transport block (e.g., repetitions of a transport block) over multiple different beams (e.g., spatial domain transmit filters). A base station may indicate multiple SRS resources for a wireless device. The wireless device may determine multiple spatial domain transmit filters based on the multiple SRS resources.

[0166] The base station may transmit a message (e.g., in a message associated with a configured uplink grant or a DCI) including multiple SRI fields (e.g., a first SRI field and a second SRI field). The multiple SRI fields may indicate multiple SRS resources. Each field of the multiple SRI fields may indicate a corresponding SRS resource. For example, the first SRI field may indicate a first SRS resource, and the second SRI field may indicate a second SRS resource. The first SRS resource and the second SRS resource may be in different SRS resource sets or in the same resource set. The base station may transmit a message (e.g., in a message associated with a configured uplink grant or a DCI) including a single SRI field. The single SRI field may indicate multiple SRS resources. For example, the SRI field may indicate a first SRS resource and a second SRS resource. The wireless device may determine multiple spatial domain transmit filters / beams based on the multiple SRS resources. A wireless device may transmit a transport block (e.g., repetitions of the transport block) through multiple spatial domain transmit filters.

[0167] Using multiple SRI fields may provide flexibility with respect to transmit power control for repeat transmissions. For example, each SRI field of the multiple SRI fields may indicate a corresponding SRS resource within a corresponding SRS resource set. Each of the SRS resource sets may be associated with a corresponding power control parameter set. The wireless device may determine the transmit power for the transmission repetition based on the power control parameter set. Using multiple power control parameter sets (e.g., as facilitated by providing multiple SRI fields) may allow the base station to more flexibly control the transmit power for the repetition of an uplink transmission. For example, different repetitions may be configured with different transmit powers.

[0168] The wireless device may receive one or more messages (e.g., from a base station) that include one or more configuration parameters, which may indicate multiple uplink resources (e.g., SRS resources) for an active uplink BWP of a cell.

[0169] A wireless device may receive a DCI. The DCI may schedule a message (e.g., a transport block). The DCI may indicate an uplink resource among a plurality of uplink resources. One or more configuration parameters may or may not indicate a spatial relationship (e.g., a transmission beam) for the uplink resource. The wireless device may determine a default TCI state for transmission of the transport block based on, for example, that the one or more configuration parameters do not indicate a spatial relationship for the uplink resource.

[0170] The wireless device may determine a spatial domain transmit filter (e.g., a transmission beam) based on a default TCI state. The wireless device may transmit (e.g., transmit) a transport block with / using the spatial domain transmit filter. The wireless device may repeat transmission of the transport block. The wireless device may use the (same) spatial domain transmit filter for transmission repetitions of the transport block over (e.g., across or through) multiple transmission opportunities. The wireless device may repeat transmission of the transport block if indicated in the DCI and / or one or more configuration parameters.

[0171] The wireless device may determine a transmit power (or a downlink path loss estimate of the transmit power) based on a default TCI state. The wireless device may transmit a transport block with / using the transmit power. The wireless device may repeat transmission of the transport block with / using the transmit power over multiple transmission opportunities (e.g., time slots, symbols) (e.g., if indicated by the DCI or one or more configuration parameters).

[0172] A wireless device may be served by (e.g., transmit to and / or receive from) multiple TRPs. The multiple TRPs may include a first TRP and a second TRP. The wireless device may receive a DCI scheduling a transport block. The wireless device may repeat transmission of the transport block if, for example, indicated by the DCI or one or more configuration parameters. The wireless device may transmit (e.g., transmit) a transport block via a first transmission opportunity to the first TRP. The wireless device may transmit a transport block via a second transmission opportunity to the second TRP. Transmission of a transport block via multiple transmission opportunities and to multiple TRPs may increase the reliability of the transport block and the probability of successful reception / decoding of the transport block (e.g., at a base station).

[0173] A base station may schedule uplink transmissions via multiple TRPs. For example, a DCI from the base station may indicate at least two uplink resources of the multiple uplink resources. Each uplink resource of the at least two uplink resources may be associated with a respective TRP of the multiple TRPs. One or more configuration parameters may or may not indicate a spatial relationship for the at least two uplink resources. A wireless device may select / determine a single default TCI state for transmission of a transport block based on, for example, one or more configuration parameters not indicating a spatial relationship for the at least two uplink resources. Selecting a single default TCI state for repetition of a transport block may be inefficient, for example, when a wireless device is served by multiple TRPs. A wireless device may not utilize spatial diversity if it selects a single default TCI state. A base station may not successfully receive / decode a transport block if, for example, a spatial domain transmit filter determined based on a single default TCI state fails and / or results in degraded reception quality (e.g., due to obstructions, movement, rotation, speed, etc. of the wireless device). Failure to receive / decode a transport block can increase error rates, reduce data rates, result in coverage loss, and increase retransmissions (which can lead to increased power consumption in wireless devices and base stations).

[0174] Using multiple beams (e.g., corresponding to different directions, different widths, etc.) for transmission to multiple TRPs may improve performance. Various examples herein improve / enhance default TCI state selection (e.g., beam selection), for example, when a wireless device is served by multiple TRPs. A wireless device may conditionally select multiple default TCI states. A wireless device may determine whether to select a single default TCI state or at least two default TCI states. One or more configuration parameters (e.g., transmitted by a base station) may include an enablement parameter indicating whether to select a single default TCI state or at least two default TCI states. A wireless device may determine to select at least two default TCI states, for example, based on at least one TCI codepoint indicating two activated TCI states. A wireless device may determine to select a single default TCI state, for example, based on the absence of a TCI codepoint indicating two activated TCI states. The one or more configuration parameters may indicate a repetition scheme (e.g., based on TDM, FDM, spatial division multiplexing (SDM), CDM, etc.). The wireless device may determine to select at least two default TCI states based on the one or more configuration parameters indicating a repetition scheme. The wireless device may determine to select at least two default TCI states based on the DCI (e.g., a TCI field of the DCI) indicating at least two uplink resources.

[0175] The wireless device may determine at least two default TCI states. The wireless device may determine the at least two default TCI states based on a rule. The wireless device may determine the at least two default TCI states based on the lowest TCI codepoints indicating two activated TCI states. The wireless device may determine the at least two default TCI states based on two activated TCI states of two CORESETs with the lowest two CORESET indicators / indices in the active downlink BWP. The wireless device may determine a first default TCI state of the at least two default TCI states based on the TCI state of the CORESET with the lowest CORESET indicator / indices in the active downlink BWP. The wireless device may determine a second default TCI state of the at least two default TCI states based on the second TCI state of the lowest TCI codepoint indicating two activated TCI states.

[0176] The wireless device may determine at least two default spatial domain transmit filters. The wireless device may determine the at least two default spatial domain transmit filters, for example, based on at least two default TCI states. The wireless device may transmit / transmit a transport block using / with the two default spatial domain transmit filters. The wireless device may repeat transmission of a message (e.g., a transport block) across / via multiple resources (e.g., time slots, minislots, symbols, etc.) using / with the two default spatial domain transmit filters. Repeated transmission of a transport block across / via multiple resources using / with the at least two default spatial domain transmit filters may increase robustness. For example, a first default spatial domain transmit filter of the at least two default spatial domain transmit filters may operate even if a second default spatial domain transmit filter of the at least two default spatial domain transmit filters operates, and vice versa. The redundancy enabled by the use of at least two default spatial domain transmit filters may reduce error rates, increase data rates, and / or reduce coverage loss. Reduced error rates and / or coverage loss may reduce retransmissions, thereby enabling reduced power consumption.

[0177] In at least some wireless communications (e.g., using 3GPP Release 16, earlier / later 3GPP releases or generations, LTE access technology, and / or other access technologies), a wireless device may apply / use a default TCI state based on one or more conditions. The wireless device may apply the default TCI state, for example, if the wireless device receives a DCI indicating an SRS resource and if the SRS resource is not configured (e.g., not provisioned or activated) with a spatial relationship. The default TCI state may correspond to a CORESET with the lowest CORESET indicator / index. The wireless device may use the default TCI state to determine a default transmission beam and / or a default path loss reference signal for transmission of a message (e.g., a transport block) scheduled by the DCI.

[0178] In at least some wireless communications (e.g., using 3GPP Release 17, earlier / later 3GPP releases or generations, LTE access technology, and / or other access technologies), a wireless device may support transmission repetitions (e.g., PUSCH transmission repetitions) for multiple TRPs. The wireless device may repeat transmission of a transport block using multiple different transmission beams and transmission powers. For example, if the SRS resources indicated by the DCI are not configured with a spatial relationship, selection of a single default TCI state (e.g., the TCI state of the CORESET with the lowest CORESET indicator / index) may not support multiple TRP transmission repetitions because multiple different transmission beams / transmission powers would be required. The wireless device may not be able to advantageously utilize spatial diversity.

[0179] The wireless device may determine multiple default TCI states based on one or more considerations. The wireless device may determine multiple default TCI states for a transmission repetition (e.g., of a transport block) scheduled by the DCI, for example, if the DCI indicates an SRS resource that is not configured with a spatial relationship and if at least one condition is met. The at least one condition may include at least one of: reception of an enabling parameter that indicates the use of at least two default beams for a transmission (e.g., a PUSCH transmission); at least one TCI codepoint that indicates at least two TCI states; parameters associated with an uplink resource (e.g., a PUSCH resource) are configured; and / or at least one of a multiple TRP repetition scheme (e.g., intra-slot repetition, TDMA scheme A, inter-slot repetition, etc.) is enabled.

[0180] The wireless device may determine multiple (e.g., at least two) default TCI states. The at least two default TCI states may be determined, for example, as at least two TCI states of a CORESET having at least two lowest CORESET indicators / indices when there are at least two CORESETs in the active downlink BWP. The at least two default TCI states may be determined as at least two TCI states indicated by lowest TCI codepoints among the TCI codepoints indicating the at least two TCI states. The at least two default TCI states may include a first default TCI state and a second default TCI state. The first default TCI state may be the TCI state of the CORESET having the lowest CORESET indicator / indices, and the second default TCI state may be the TCI state of the lowest TCI codepoint among the TCI codepoints indicating the at least two TCI states. The wireless device may determine at least two default TCI states for configured uplink grants (e.g., Type 1 and Type 2 configured uplink grants) activated by a DCI.

[0181] 17 illustrates exemplary beam management for transmission repetition. The exemplary beam management may be used for transmission repetition via multiple transmission beams. The transmission repetition may correspond to repeated transmissions via multiple time domain resources (e.g., TDM). The wireless device 1708 may transmit the repeated transmissions (e.g., of a transport block via a PUSCH resource) to the base station 1704.

[0182] 18 illustrates exemplary beam management for transmission. The exemplary beam management may be used for transmission via multiple transmission beams. The transmission may correspond to transmission of portions of a message via multiple frequency domain resources (e.g., FDM). The wireless device 1808 may transmit portions of the transmission (e.g., of a transport block via PUSCH resources) to the base station 1804 via corresponding transmission opportunities.

[0183] 19 illustrates an exemplary transmit power determination for transmission repetition. The exemplary transmit power determination may be used for transmission repetition via multiple transmission beams. The transmission repetition may correspond to repeated transmission via multiple time domain resources (e.g., TDM). The wireless device 1908 may transmit the repeated transmission (e.g., of a transport block via a PUSCH resource) to the base station 1904.

[0184] 20 illustrates an exemplary transmit power determination. The exemplary transmit power determination may be used for transmission via multiple transmission beams. The transmission may correspond to transmission of portions of a message via multiple frequency domain resources (e.g., FDM). The wireless device 2008 may transmit portions of the transmission (e.g., of a transport block via PUSCH resources) to the base station 2004 via corresponding transmission opportunities.

[0185] A wireless device (e.g., wireless device 1708, wireless device 1808, wireless device 1908, or wireless device 2008) may receive one or more messages (e.g., at or after time T0 shown in FIGS. 17-20). The wireless device may receive one or more messages from a base station (e.g., base station 1704, base station 1804, base station 1904, or base station 2004). The one or more messages may include one or more configuration parameters (e.g., configuration parameters 1712, configuration parameters 1812, configuration parameters 1912, or configuration parameters 2012). The one or more configuration parameters may include RRC configuration parameters. The one or more configuration parameters may include RRC reconfiguration parameters.

[0186] The one or more configuration parameters may be for a 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 (e.g., a PCell), a secondary cell (e.g., an SCell), or a secondary cell configured with a PUCCH (e.g., a PUCCH SCell). The cell may be an unlicensed cell (e.g., operating in an unlicensed band). The cell may be a licensed cell (e.g., operating in a licensed band). The cell may operate in a first frequency range (e.g., FR1). FR1 may include a frequency band below 6 GHz (or any other frequency band). The cell may operate in a second frequency range (e.g., FR2). FR2 may include a frequency band in the range of 24 GHz to 52.6 GHz (or any other frequency band).

[0187] The wireless device may perform uplink transmission (e.g., PUSCH transmission, PUCCH transmission, SRS transmission) through the cell at a first time and via a first frequency / frequency range. The wireless device may perform downlink reception (e.g., PDCCH reception, PDSCH reception) through the cell at a second time and via a second frequency. The cell may operate in a time division duplex (TDD) mode. The first frequency and the second frequency may be the same or different in the TDD mode. The cell may operate in a frequency division duplex (FDD) mode. The first frequency and the second frequency may be different in the FDD mode. The first time and the second time may be the same in the FDD mode.

[0188] The wireless device may be in an RRC connected mode, an RRC idle mode, or an RRC inactive mode.

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

[0190] A BWP of the multiple BWPs may be in an active state or an inactive state. The wireless device may monitor a downlink channel / signal (e.g., PDCCH, DCI, CSI-RS, PDSCH) on / for / via a downlink BWP of one or more downlink BWPs, for example, when the downlink BWP is in an active state. The wireless device may receive a PDSCH transmission via a downlink BWP of one or more downlink BWPs, for example, when the downlink BWP is in an active state. The wireless device may not monitor a downlink channel / signal (e.g., PDCCH, DCI, CSI-RS, PDSCH) on / via a downlink BWP of one or more downlink BWPs, for example, when the downlink BWP 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 / via a downlink BWP of one or more downlink BWPs, for example, when the downlink BWP is in an inactive state. A wireless device may not receive a PDSCH transmission on / through / for a downlink BWP of one or more downlink BWPs, for example, when the downlink BWP is in an inactive state. A wireless device may stop receiving a PDSCH transmission on / through / for a downlink BWP of one or more downlink BWPs, for example, when the downlink BWP is in an inactive state.

[0191] A wireless device may transmit / transmit uplink signals (e.g., PUCCH transmission, preamble, PUSCH transmission, PRACH transmission, SRS, etc.) on / via an uplink BWP of one or more uplink BWPs, for example, when the uplink BWP is in an active state. A wireless device may not transmit / transmit uplink signals (e.g., PUCCH transmission, preamble, PUSCH transmission, PRACH transmission, SRS, etc.) on / via an uplink BWP of one or more uplink BWPs, for example, when the uplink BWP is in an inactive state.

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

[0193] The wireless device may activate an uplink BWP of one or more uplink BWPs of a cell. Activating an uplink BWP may include the wireless device setting (or switching to) the uplink BWP as the active uplink BWP of the cell. Activating an uplink BWP may include the wireless device setting the uplink BWP to an active state. Activating an uplink BWP may include switching the uplink BWP from an inactive state to an active state.

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

[0195] A wireless device may send / transmit (e.g., to a base station) a wireless device capability message. The wireless device capability message may include wireless device capability information. The wireless device capability information may indicate (e.g., include an indication of) support for beam correspondence without uplink beam sweeping (e.g., an upper layer parameter beamCorrespondenceWithoutUL-BeamSweeping). The wireless device may set the value of the parameter in the wireless device capability message to a first value (e.g., 1, or any other value) to indicate support for beam correspondence without uplink sweeping.

[0196] The wireless device may select a (preferred) beam (or spatial-domain transmit filter) for uplink transmission. The wireless device may select a (preferred) beam (or spatial-domain transmit filter) for uplink transmission based on downlink measurements without relying on uplink beam sweeping, for example, based on wireless device capability information indicating support for beam support without uplink beam sweeping. The wireless device may not select a (preferred) beam (or spatial-domain transmit filter) for uplink transmission based on uplink beam sweeping.

[0197] The wireless device capability information may indicate support for repetition of uplink signal transmissions (e.g., PUCCH transmissions, PUSCH transmissions, transport blocks, SRS, etc.). The repetition may be based on TDM, FDM, SDM, and / or CDM.

[0198] One or more configuration parameters may indicate multiple uplink resources. The multiple uplink resources may correspond to (or be indicated for) a cell. A cell may include multiple uplink resources. The multiple uplink resources may be on (or may be indicated for) an (active) uplink BWP of a cell. The (active) uplink BWP of a cell may include multiple uplink resources.

[0199] The multiple uplink resources may include / may include multiple PUCCH resources. The multiple uplink resources may include / may include multiple SRS resources. The multiple uplink resources may include / may include multiple PUSCH resources. The wireless device may receive a DCI (e.g., corresponding to DCI format 0_0, DCI format 0_1, DCI format 0_2, etc.). The DCI may schedule transmission of one or more transport blocks over the multiple PUSCH resources. One or more configuration parameters may indicate multiple PUSCH resources for a configured uplink grant (e.g., a type 1 configured uplink grant, a type 2 configured uplink grant). The wireless device may transmit / transmit one or more transport blocks for a configured uplink grant over the multiple PUSCH resources.

[0200] The one or more configuration parameters may include / indicate multiple uplink resource indexes (e.g., identifiers, indicators, SRS resource indicators / IDs, PUCCH-ResourceIds, etc.). The multiple uplink resource indexes may identify / indicate multiple uplink resources. Each uplink resource of the multiple uplink resources may be identified / indicated by a respective uplink resource index / identifier of the multiple uplink resource indexes / identifiers. A first uplink resource of the multiple uplink resources may be identified / indicated by a first uplink resource index / identifier of the multiple uplink resource indexes / identifiers. A second uplink resource of the multiple uplink resources may be identified / indicated by a second uplink resource index / identifier of the multiple uplink resource indexes / identifiers. The one or more configuration parameters may indicate multiple uplink resources based on the one or more configuration parameters including / indicating multiple uplink resource indexes / identifiers that identify / indicate the multiple uplink resources.

[0201] The one or more configuration parameters may include an enabling parameter (e.g., enableDefaultBeamPlForPUSCH0_0, enableDefaultBeamPlForPUSCH0_1, enableDefaultBeamPlForPUCCH, enableDefaultBeamPlForSRS). The enabling parameter may indicate a value (e.g., enable, disable). The value may indicate whether the enabling parameter is enabled or disabled. The enabling parameter may be enabled. The one or more configuration parameters may indicate that the enabling parameter is enabled. The value of the enabling parameter may indicate that the enabling parameter is enabled. The enabling parameter may be for a cell. The enabling parameter may enable determination / selection of a default spatial relationship for transmission of uplink signals (e.g., SR, CSI, HARQ-ACK, UCI, PUCCH transmission, PUSCH transmission, SRS, transport block) over uplink resources (e.g., PUCCH resource, SRS resource, PUSCH resource). The enablement parameter may enable the determination / selection of a default path loss reference signal for transmission of uplink signals over this uplink resource. The plurality of uplink resources may include this uplink resource.

[0202] The wireless device may determine / select a default spatial relationship and / or a default path loss reference signal for transmission of an uplink signal over the uplink resource based on, for example, one or more configuration parameters including an enabled parameter being enabled.

[0203] The wireless device may determine / select a default spatial relationship and / or a default path loss reference signal based on, for example, the uplink resource not being provided with a spatial relationship (e.g., PUCCH-SpatialRelationInfo, spatialRelationInfo). The uplink resource not being provided with a spatial relationship may include one or more configuration parameters not indicating a spatial relationship. The uplink resource not being provided with a spatial relationship may include one or more configuration parameters not indicating a spatial relationship for the uplink resource. The uplink resource not being provided with a spatial relationship may include the wireless device not receiving an activation command (e.g., MAC CE) that indicates a spatial relationship for the uplink resource. The uplink resource not being provided with a spatial relationship may include the wireless device receiving a DCI (e.g., corresponding to DCI format 0_0, DCI format 0_1, DCI format 0_2) that schedules transmission of an uplink signal (e.g., a PUSCH transmission, a transport block) over the uplink resource, where the DCI does not include a field indicating a spatial relationship. The field may be an SRS resource indicator (SRI) field.

[0204] The wireless device may determine / select a default spatial relationship and / or a default path loss reference signal, for example, based on (e.g., in response to) the uplink resource not being provided with at least one path loss reference signal (e.g., provided by the upper layer parameter pathlossReferenceRSs, the upper layer parameter PUSCH-PathlossReferenceRS, or the upper layer parameter SRS-PathlossReferenceRS). The uplink resource not being provided with at least one path loss reference signal may include one or more configuration parameters not indicating at least one path loss reference signal for an SRS resource set that includes the uplink resource. The uplink resource not being provided with at least one path loss reference signal may include the wireless device not receiving an activation command (e.g., MAC CE) that indicates at least one path loss reference signal for an SRS resource set that includes the uplink resource. The uplink resource not being provided with at least one path loss reference signal may include one or more configuration parameters not indicating at least one path loss reference signal for an uplink BWP that includes the uplink resource. Not being provided with at least one path loss reference signal for an uplink resource may include the wireless device not receiving an activation command (e.g., MAC CE) indicating at least one path loss reference signal for an uplink BWP that includes the uplink resource. Not being provided with at least one path loss reference signal for an uplink resource may include one or more configuration parameters not indicating at least one path loss reference signal for the uplink resource. Not being provided with at least one path loss reference signal for an uplink resource may include the wireless device not receiving an activation command (e.g., MAC CE) indicating at least one path loss reference signal for the uplink resource.The wireless device may determine / select a default spatial relationship and / or a default path loss reference signal, for example, based on (e.g., in response to) one or more configuration parameters not indicating at least one path loss reference signal (e.g., for an uplink BWP, an SRS resource set, a PUCCH configuration parameter for the uplink BWP, or a PUSCH configuration parameter for the uplink BWP).

[0205] The one or more configuration parameters may include a second enabling parameter (e.g., enableTwoDefaultBeamsPlForPUSCH0_0, enableTwoDefaultBeamsPlForPUSCH0_1, enableTwoDefaultBeamsPlForPUCCH, enableTwoDefaultBeamsPlForSRS). The second enabling parameter may indicate a value (e.g., enabled, disabled). The value may indicate whether the second enabling parameter is enabled or disabled. The second enabling parameter may be enabled. The one or more configuration parameters may indicate that the second enabling parameter is enabled. The value of the second enabling parameter may indicate that the second enabling parameter is enabled. The second enabling parameter may be for a cell. The second enabling parameter may enable determination / selection of at least two default spatial relationships for transmission of uplink signals (e.g., SR, CSI, HARQ-ACK, UCI, PUCCH transmission, PUSCH transmission, transport block, SRS) over uplink resources (e.g., PUCCH resource, SRS resource, PUSCH resource). The second enabling parameter may enable determination / selection of at least two default path loss reference signals for transmission of uplink signals over the uplink resources. The multiple uplink resources of the cell may include uplink resources.

[0206] The wireless device may determine / select at least two default spatial relationships and at least two default path loss reference signals for transmission of uplink signals over the uplink resources. The wireless device may determine / select at least two default spatial relationships and / or at least two default path loss reference signals for transmission of uplink signals over the uplink resources based, for example, on the one or more configuration parameters including a second enabled parameter that is enabled.

[0207] The second enabling parameter may be for an uplink resource among the plurality of uplink resources. The one or more configuration parameters may indicate a respective second enabling parameter for each uplink resource among the plurality of uplink resources. The second enabling parameter may enable determining / selecting at least two default spatial relationships for transmission of an uplink signal (e.g., SR, CSI, HARQ-ACK, UCI, PUCCH transmission, PUSCH transmission, transport block, SRS) over the uplink resource (e.g., PUCCH resource, SRS resource, PUSCH resource). The second enabling parameter may enable determining / selecting at least two default path loss reference signals for transmission of an uplink signal over the uplink resource. The wireless device may determine / select at least two default spatial relationships and / or at least two default path loss reference signals for transmission of an uplink signal over the uplink resource based, for example, on the one or more configuration parameters including the second enabling parameter for the enabled uplink resource.

[0208] The one or more configuration parameters may not include a second enabling parameter (e.g., enableTwoDefaultBeamsPlForPUSCH0_0, enableTwoDefaultBeamsPlForPUSCH0_1, enableTwoDefaultBeamsPlForPUCCH, enableTwoDefaultBeamsPlForSRS). The one or more configuration parameters may include an enabling parameter (e.g., enableDefaultBeamPlForPUSCH0_0, enableDefaultBeamPlForPUSCH0_1, enableDefaultBeamPlForPUCCH, enableDefaultBeamPlForSRS). The enabling parameter may be enabled. The wireless device may determine / select a default spatial relationship and / or a default path loss reference signal for transmission of an uplink signal (e.g., SR, CSI, HARQ-ACK, UCI, PUCCH, PUSCH, transport block, SRS) over uplink resources based, for example, on the one or more configuration parameters not including the second enabling parameter. The wireless device may determine / select a default spatial relationship and / or a default path loss reference signal for transmission of an uplink signal over an uplink resource based, for example, on one or more configuration parameters including an enabled parameter that is enabled.

[0209] The one or more configuration parameters may include a second enabling parameter (e.g., enableTwoDefaultBeamsPlForPUSCH0_0, enableTwoDefaultBeamsPlForPUSCH0_1, enableTwoDefaultBeamsPlForPUCCH, enableTwoDefaultBeamsPlForSRS). The second enabling parameter may not be enabled. The one or more configuration parameters may indicate that the second enabling parameter is not enabled. A value of the second enabling parameter may not indicate that the second enabling parameter is enabled. The one or more configuration parameters may include an enabling parameter (e.g., enableDefaultBeamPlForPUSCH0_0, enableDefaultBeamPlForPUSCH0_1, enableDefaultBeamPlForPUCCH, enableDefaultBeamPlForSRS). The enabling parameter may be enabled. The wireless device may determine / select a default spatial relationship and / or a default path loss reference signal for transmission of an uplink signal (e.g., SR, CSI, HARQ-ACK, UCI, PUCCH transmission, PUSCH transmission, transport block, SRS) over the uplink resource, for example, based on one or more configuration parameters indicating that the second enabled parameter is not enabled. The wireless device may determine / select a default spatial relationship and / or a default path loss reference signal for transmission of an uplink signal over the uplink resource, for example, based on one or more configuration parameters including an enabled parameter that is enabled.

[0210] The one or more configuration parameters may include a second enabling parameter (e.g., enableTwoDefaultBeamsPlForPUSCH0_0, enableTwoDefaultBeamsPlForPUSCH0_1, enableTwoDefaultBeamsPlForPUCCH, enableTwoDefaultBeamsPlForSRS). The one or more configuration parameters may not include an enabling parameter (e.g., enableDefaultBeamPlForPUSCH0_0, enableDefaultBeamPlForPUSCH0_1, enableDefaultBeamPlForPUCCH, enableDefaultBeamPlForSRS) based on the one or more configuration parameters including the second enabling parameter. The one or more configuration parameters may include an enabling parameter (e.g., enableDefaultBeamPlForPUSCH0_0, enableDefaultBeamPlForPUCCH, enableDefaultBeamPlForSRS). One or more configuration parameters may not include a second enabling parameter (e.g., enableTwoDefaultBeamsPlForPUSCH0_0, enableTwoDefaultBeamsPlForPUCCH, enableTwoDefaultBeamsPlForSRS) based on the one or more configuration parameters including the enabling parameter.

[0211] The one or more configuration parameters may include a second enabling parameter (e.g., enableTwoDefaultBeamsPlForPUSCH0_0, enableTwoDefaultBeamsPlForPUCCH, enableTwoDefaultBeamsPlForSRS). The second enabling parameter may be enabled. The one or more configuration parameters may indicate that the second enabling parameter is enabled. A value of the second enabling parameter may indicate that the second enabling parameter is enabled. The one or more configuration parameters may not include an enabling parameter (e.g., enableDefaultBeamPlForPUSCH0_0, enableDefaultBeamPlForPUCCH, enableDefaultBeamPlForSRS) based on the one or more configuration parameters including the second enabling parameter being enabled. The one or more configuration parameters may include an enabling parameter (e.g., enableDefaultBeamPlForPUSCH0_0, enableDefaultBeamPlForPUCCH, enableDefaultBeamPlForSRS). The enabling parameter may not be enabled. One or more configuration parameters may not indicate that an enablement parameter is enabled. A value of an enablement parameter may not indicate that an enablement parameter is enabled. An enablement parameter may not be enabled based on a second enablement parameter being enabled.

[0212] The one or more configuration parameters may include an enabling parameter (e.g., enableDefaultBeamPlForPUSCH0_0, enableDefaultBeamPlForPUCCH, enableDefaultBeamPlForSRS). The enabling parameter may be enabled. The one or more configuration parameters may indicate that the enabling parameter is enabled. A value of the enabling parameter may indicate that the enabling parameter is enabled. The one or more configuration parameters may not include a second enabling parameter (e.g., enableTwoDefaultBeamsPlForPUSCH0_0, enableTwoDefaultBeamsPlForPUSCH0_1, enableTwoDefaultBeamsPlForPUCCH, enableTwoDefaultBeamsPlForSRS) based on the one or more configuration parameters including the enabling parameter. The one or more configuration parameters may include a second enabling parameter (e.g., enableTwoDefaultBeamsPlForPUSCH0_0, enableTwoDefaultBeamsPlForPUCCH, enableTwoDefaultBeamsPlForSRS). The second enabling parameter may not be enabled. The one or more configuration parameters may not indicate that the second enabling parameter is enabled. The value of the second enabling parameter may not indicate that the second enabling parameter is enabled. The second enabling parameter may not be enabled based on the enabling parameter being enabled.

[0213] The enabling parameter and the second enabling parameter may not be enabled at the same time. The one or more configuration parameters may not include an enabling parameter that is enabled and a second enabling parameter that is enabled (e.g., at the same time or simultaneously). The one or more configuration parameters may not include an enabling parameter that is enabled and a second enabling parameter that is disabled (e.g., at the same time or simultaneously). The one or more configuration parameters may include an enabling parameter that is disabled and a second enabling parameter that is enabled (e.g., at the same time or simultaneously).

[0214] The one or more configuration parameters may include an enabling parameter that is enabled. The one or more configuration parameters may include a second enabling parameter that is enabled. The wireless device may ignore the enabling parameter, for example, based on the enabling parameter being enabled and the second enabling parameter being enabled. Ignoring the enabling parameter may include setting the enabling parameter to indicate that the enabling parameter is disabled. Ignoring the enabling parameter may include not applying the enabling parameter (e.g., not performing an action required for and / or based on the enabling parameter). The wireless device may ignore the second enabling parameter, for example, based on the enabling parameter being enabled and the second enabling parameter being enabled. Ignoring the second enabling parameter may include setting the second enabling parameter to indicate that the second enabling parameter is disabled. Ignoring the second enabling parameter may include not applying the second enabling parameter (e.g., not performing an action required for and / or based on the second enabling parameter).

[0215] The one or more configuration parameters may not indicate at least one path loss reference signal (RS) (e.g., pathlossReferenceRSs, PUCCH-PathlossReferenceRS, PathlossReferenceRS-Config, pathlossReferenceRS-List-r16, pathlossReferenceRS-List, SRS-PathlossReferenceRS). The one or more configuration parameters may not indicate at least one path loss reference RS for the cell. The one or more configuration parameters may not indicate at least one path loss reference RS for the (active) uplink BWP of the cell. The one or more configuration parameters may not indicate at least one path loss reference signal for an SRS resource set of the (active) uplink BWP of the cell. The SRS resource set may include uplink resources. The one or more configuration parameters may include one or more SRS configuration parameters, PUCCH configuration parameters, and / or PUSCH configuration parameters of the (active) uplink BWP. The one or more SRS configuration parameters, PUCCH configuration parameters, and / or PUSCH configuration parameters may not indicate at least one path loss reference signal. A wireless device may not be provided with at least one path loss reference RS, for example, based on one or more configuration parameters not indicating at least one path loss reference RS.

[0216] The wireless device may not receive an activation command indicating at least one path loss reference RS (e.g., an SRS path loss reference RS activation / deactivation MAC CE, a PUCCH spatial relationship activation / deactivation MAC CE, an extended PUCCH spatial relationship activation / deactivation MAC CE, etc.). The wireless device may not receive an activation command indicating at least one path loss reference RS for an (active) uplink BWP. The wireless device may not receive an activation command indicating at least one path loss reference RS for a cell. The wireless device may not receive an activation command indicating at least one path loss reference signal for an SRS resource set including the uplink resource. The wireless device may not be provided with at least one path loss reference RS, for example, based on not receiving an activation command indicating at least one path loss reference RS. The wireless device may not receive an activation command indicating at least one path loss reference RS for an uplink resource of the plurality of uplink resources. The wireless device may not be provided with at least one path loss reference RS for the uplink resource, for example, based on not receiving an activation command indicating at least one path loss reference RS for the uplink resource.

[0217] One or more configuration parameters may not indicate a spatial relation (e.g., PUCCH-SpatialRelationInfo, spatialRelationInfo). One or more configuration parameters may not indicate a spatial relation for a cell. One or more configuration parameters may not indicate a spatial relation for an (active) uplink BWP of a cell. A wireless device may not be provided with a spatial relation, for example, based on one or more configuration parameters not indicating a spatial relation. One or more configuration parameters may not indicate a spatial relation for an uplink resource of a plurality of uplink resources. A wireless device may not be provided with a spatial relation for an uplink resource, for example, based on one or more configuration parameters not indicating a spatial relation for the uplink resource.

[0218] The one or more configuration parameters may indicate multiple spatial relationships (e.g., PUCCH-SpatialRelationInfo, spatialRelationInfo). The wireless device may not receive an activation command (e.g., AP / SP SRS activation / deactivation MAC CE, PUCCH spatial relationship activation / deactivation MAC CE, etc.) that indicates a spatial relationship among multiple spatial relationships for an uplink resource among multiple uplink resources. The wireless device may not be provided with a spatial relationship for an uplink resource, for example, based on not receiving an activation command that indicates a spatial relationship for the uplink resource. The wireless device may not be provided with a spatial relationship, for example, based on not receiving an activation command that indicates a spatial relationship.

[0219] A wireless device may receive a DCI (e.g., corresponding to DCI format 0_0) that schedules transmission of an uplink signal (e.g., a transport block, a PUSCH transmission). The DCI may schedule transmission of an uplink signal via an uplink resource (e.g., a PUSCH resource) among a plurality of uplink resources. The DCI may schedule transmission of an uplink signal via an (active) uplink BWP. The DCI may not indicate a spatial relationship for transmission of the uplink signal. The DCI may not include a field (e.g., an SRI field) that indicates a spatial relationship. The wireless device may not be provided with a spatial relationship for uplink resources, for example, based on receiving a DCI that does not indicate a spatial relationship for transmission of an uplink signal via the uplink resource.

[0220] A wireless device may receive a DCI (e.g., corresponding to DCI format 0_1 ​​or DCI format 0_2) that schedules transmission of an uplink signal (e.g., a transport block, a PUSCH transmission). The DCI may schedule transmission of the uplink signal via an uplink resource (e.g., a PUSCH resource) among a plurality of uplink resources. The DCI may schedule transmission of the uplink signal via an (active) uplink BWP. The DCI may include a field (e.g., an SRI field) that indicates the uplink resource. The uplink resource may not be provided with a spatial relationship. The wireless device may not be provided with a spatial relationship for transmission of the uplink signal, for example, based on the uplink resource indicated by the DCI not being provided with a spatial relationship.

[0221] 21A-21C show example configurations of TCI states associated with TCI codepoints and / or CORESETs. One or more configuration parameters may indicate one or more CORESETs (e.g., the first CORESET in FIG. 21B, the first CORESET and the second CORESET in FIG. 21C). One or more configuration parameters may indicate one or more CORESETs for the (active) downlink BWP of a cell. The (active) downlink BWP of a cell may include one or more CORESETs.

[0222] The one or more configuration parameters may indicate one or more CORESET indicators / indexes (e.g., provided by the upper layer parameter ControlResourceSetId) for one or more CORESETs. Each CORESET of the one or more CORESETs may be identified / indicated by a respective CORESET indicator / index of the one or more CORESET indicators / indexes. A first CORESET of the one or more CORESETs may be identified by a first CORESET index of the one or more CORESET indexes. A second CORESET of the one or more CORESETs may be identified by a second CORESET index of the one or more CORESET indexes. The CORESET index may be a CORESET identifier.

[0223] A first CORESET of the one or more CORESETs may be identified / indicated by a CORESET index of one or more CORESET indices. This CORESET index may be the lowest (or highest) of the one or more CORESET indices. The first CORESET (e.g., the first CORESET in FIG. 21B and the first CORESET in FIG. 21C) may be identified / indicated by a CORESET index that is the lowest among the one or more CORESET indices of the one or more CORESETs. One or more configuration parameters may indicate a first TCI state for the first CORESET (e.g., TCI state 8 in FIG. 21B and FIG. 21C, provided by the upper layer parameter tci-StatesPDCCH-ToAddList).

[0224] The one or more configuration parameters may indicate multiple TCI states for the first CORESET (e.g., provided by the higher layer parameter tci-StatesPDCCH-ToAddList). The wireless device may receive an activation command (e.g., a TCI state indication for a wireless device-specific PDCCH MAC CE) (e.g., at or after time T1 in FIGS. 17-20). The activation command may activate (e.g., select, indicate, or update) a first TCI state (e.g., TCI state 8 in FIGS. 21B and 21C) for the first CORESET. The activation command may correspond to activation command 1716, activation command 1816, activation command 1916, or activation command 2016. The multiple TCI states may include the first TCI state. The activation command may include one or more fields. A first field of the one or more fields may indicate / include a CORESET indicator / index of the first CORESET. A second field of the one or more fields may indicate / include a first TCI state indicator / index for the first TCI state. A third field of the one or more fields may indicate / include a serving cell indicator / index for the cell (e.g., provided by a higher layer parameter ServCellIndex). The one or more configuration parameters may indicate a serving cell index for the cell. A fourth field of the one or more fields may indicate / include a downlink BWP indicator / index for the downlink BWP. The one or more configuration parameters may indicate a downlink BWP index for the downlink BWP.

[0225] The one or more configuration parameters may indicate TCI state indicators / indexes (e.g., provided by the upper layer parameter TCI-StateId) for the multiple TCI states. Each TCI state of the multiple TCI states may be identified / indicated by a respective TCI state indicator / index of the TCI state indicators / indexes. A first TCI state of the multiple TCI states may be indicated / identified by a first TCI state indicator / index of the TCI state indicators / indexes. A second TCI state of the multiple TCI states may be indicated / identified by a second TCI state indicator / index of the TCI state indicators / indexes. The TCI state indicators / indexes may include a first TCI state indicator / index that identifies / indicates a first TCI state of the first CORESET. The TCI state indicator / index may be a TCI state identifier.

[0226] The first TCI state may indicate a first reference signal (e.g., CSI-RS, SSB / PBCH block, SRS, DM-RS). The first TCI state may include a first reference signal indicator / index (e.g., provided by higher layer parameters referenceSignal, ssb-index, csi-RS-Index, NZP-CSI-RS-ResourceId). The first reference signal indicator / index may identify (or indicate) the first reference signal. One or more configuration parameters may indicate the first reference signal indicator / index for the first TCI state. The first TCI state may indicate a first quasi-co-location type for the first reference signal. The first quasi-co-location (QCL) type may be QCL type D (or any other QCL type).

[0227] The first TCI state may correspond to a first QCL assumption (or characteristic or structure) of the first CORESET. The first QCL assumption of the first CORESET may indicate at least one of a channel characteristic, a Doppler shift, a Doppler spread, a mean delay, a delay spread, and / or a spatial receive filter for the first CORESET.

[0228] The wireless device may monitor a downlink control channel for the DCI. The wireless device may monitor a downlink control channel for the DCI via a first CORESET based on a first TCI state. The wireless device may monitor a downlink control channel for the DCI via a first CORESET based on the first TCI state, e.g., based on (e.g., in response to) receiving an activation command activating the first TCI state for the first CORESET. The wireless device may monitor a downlink control channel for the DCI via the first CORESET based on the first TCI state, e.g., based on (e.g., in response to) one or more configuration parameters indicating the first TCI state for the first CORESET. Monitoring the downlink control channel in the first CORESET based on the first TCI state may include one or more DM-RS antenna ports of a downlink control channel (e.g., a PDCCH) in the first CORESET being quasi-colocated with a first reference signal indicated by the first TCI state. One or more DM-RS antenna ports may be quasi-collocated with a first reference signal for a first quasi-collocation type indicated by a first TCI state. The wireless device may receive DCI via a first CORESET. The wireless device may receive DCI via the first CORESET, for example, based on monitoring a downlink control channel in the first CORESET. The wireless device may receive DCI via the first CORESET based on the first TCI state. Receiving DCI via the first CORESET based on the first TCI state may include one or more DM-RS antenna ports of a downlink control channel (e.g., a PDCCH) in the first CORESET, where the DCI is quasi-collocated with the first reference signal indicated by the first TCI state.

[0229] The one or more configuration parameters may indicate one or more configured uplink grants (e.g., by the higher layer parameter ConfiguredGrantConfig). The one or more configured uplink grants may include a configured uplink grant.

[0230] The configured uplink grant may be a configured uplink grant of type 1 (or a configured grant type 1 provided by the higher layer parameter rrc-ConfiguredUplinkGrant in the higher layer parameter ConfiguredGrantConfig). One or more configuration parameters (e.g., RRC configuration parameters) may indicate (e.g., provide, activate) the uplink grant. The wireless device may activate the configured uplink grant of type 1 based on receiving the one or more configuration parameters. The wireless device may store the uplink grant as a configured uplink grant. The wireless device may send / transmit a transport block (TB) based on / for the configured uplink grant. The wireless device may transmit a transport block (e.g., the TB shown in FIGS. 17-20) via one or more periodic uplink resources of the configured uplink grant.

[0231] The configured uplink grant may indicate at least two uplink resources (e.g., SRS resources). One or more configuration parameters may indicate an SRI field for the configured uplink grant (e.g., by srs-ResourceIndicator in rrc-ConfiguredUplinkGrant). The SRI field may indicate at least two uplink resources. The one or more configuration parameters may indicate a mapping between the SRI field and the at least two uplink resources. The mapping between the SRI field and the at least two uplink resources may be pre-configured (e.g., pre-defined, pre-set, fixed). The value of the SRI field may be mapped to at least two uplink resource indicators / indices of the at least two uplink resources. The multiple uplink resource indicators / indices may include at least two uplink resource indicators / indices.

[0232] The one or more configuration parameters may indicate at least two SRI fields for the configured uplink grant (e.g., by srs-ResourceIndicator in rrc-ConfiguredUplinkGrant). The at least two SRI fields may indicate at least two uplink resources. Each SRI field of the at least two SRI fields may indicate a respective uplink resource of the at least two uplink resources. The one or more configuration parameters may indicate a mapping between the at least two SRI fields and the at least two uplink resources. The mapping between the at least two SRI fields and the at least two uplink resources may be pre-configured (e.g., pre-defined, pre-set, or fixed). Values ​​of the at least two SRI fields may be mapped to at least two uplink resource indicators / indices of the at least two uplink resources. The multiple uplink resource indicators / indices may include at least two uplink resource indicators / indices.

[0233] The one or more configuration parameters may indicate a TCI field for a configured uplink grant. The TCI field may indicate (or may be equal to) a TCI codepoint (e.g., an uplink TCI codepoint, a downlink TCI codepoint). The TCI codepoint may indicate at least two uplink resources. The activation command may activate / indicate at least two uplink resources for the TCI codepoint. The TCI codepoint may indicate / include at least two activated TCI states. Each TCI state of the at least two activated TCI states may indicate (or may correspond to or include) a respective uplink resource of the at least two uplink resources. A first TCI state of the at least two activated TCI states may indicate (or may correspond to or include) a first uplink resource of the at least two uplink resources. The first TCI state may include a first uplink resource indicator / index of the first uplink resource (e.g., identifying or indicating the first uplink resource). The multiple uplink resource indexes / identifiers may include the first uplink resource index. A second TCI state of the at least two activated TCI states may indicate (or correspond to or include) a second uplink resource of the at least two uplink resources. The second TCI state may include a second uplink resource indicator / index of the second uplink resource (e.g., identifying or indicating the second uplink resource). The multiple uplink resource indexes / identifiers may include the second uplink resource index.

[0234] A wireless device may receive a DCI. The DCI may correspond to DCI format 0_1, DCI format 0_2, or DCI format 0_0. The DCI may schedule an uplink message (e.g., a transport block). The DCI may include a dynamic uplink grant for transmission of the transport block. The wireless device may, for example, transmit / transmit a transport block (e.g., a TB shown in FIGS. 17 to 20) via uplink resources indicated by the DCI (or the dynamic uplink grant).

[0235] The configured uplink grant may be a configured uplink grant of type 2 (or a configured grant type 2). A PDCCH transmission may, for example, indicate / provide an uplink grant in a configured uplink grant of type 2. The wireless device may store the uplink grant as a configured uplink grant based on receiving a DCI (or layer 1 signaling) indicating configured uplink grant activation. The DCI may activate the configured uplink grant. The wireless device may transmit / transmit a transport block (e.g., TB in Figures 17-20) for the configured uplink grant. The wireless device may transmit a transport block (e.g., PUSCH transmission) via one or more periodic uplink resources.

[0236] The DCI may indicate at least two uplink resources (e.g., SRS resources). The DCI may indicate / include an SRI field indicating the at least two uplink resources. One or more configuration parameters may indicate a mapping between the SRI field and the at least two uplink resources. The mapping between the SRI field and the at least two uplink resources may be pre-configured (e.g., pre-defined, pre-set, or fixed). The value of the SRI field may be mapped to at least two uplink resource indicators / indices of the at least two uplink resources. The multiple uplink resource indicators / indices may include at least two uplink resource indicators / indices.

[0237] The DCI may indicate / include at least two SRI fields indicating at least two uplink resources. Each SRI field of the at least two SRI fields may indicate a respective uplink resource of the at least two uplink resources. One or more configuration parameters may indicate a mapping between the at least two SRI fields and the at least two uplink resources. The mapping between the at least two SRI fields and the at least two uplink resources may be pre-configured (e.g., pre-defined, pre-set, or fixed). Values ​​of the at least two SRI fields may be mapped to at least two uplink resource indicators / indices of the at least two uplink resources. The multiple uplink resource indicators / indices may include at least two uplink resource indicators / indices.

[0238] The DCI may include a TCI field. The TCI field may indicate (or may include) a TCI codepoint (e.g., an uplink TCI codepoint, a downlink TCI codepoint). The TCI codepoint may indicate at least two uplink resources. The activation command may activate / indicate at least two uplink resources for the TCI codepoint. The TCI codepoint may indicate at least two activated TCI states. Each TCI state of the at least two activated TCI states may indicate (or correspond to or include) a respective uplink resource of the at least two uplink resources. For example, a first TCI state of the at least two activated TCI states may indicate (or correspond to) a first uplink resource of the at least two uplink resources. The first TCI state may include a first uplink resource indicator / index of the first uplink resource (e.g., indicating / identifying the first uplink resource). The multiple uplink resource indexes / identifiers may include a first uplink resource index. A second TCI state of the at least two activated TCI states may indicate (or correspond to or include) a second uplink resource of the at least two uplink resources. The second TCI state may include a second uplink resource indicator / index of the second uplink resource (e.g., indicating / identifying the second uplink resource). The multiple uplink resource indexes / identifiers may include the second uplink resource index.

[0239] The wireless device may determine / select at least two TCI states. The wireless device may determine / select at least two TCI states, for example, based on one or more configuration parameters or DCI. The wireless device may determine / select at least two TCI states for transmission of a transport block. For example, as shown in Figures 17 to 20, the wireless device may determine / select TCI state 8 and TCI state 23 as the at least two TCI states (e.g., at or before time T2).

[0240] A wireless device may be served by (e.g., transmit to and / or receive from) multiple TRPs, and the wireless device may determine / select at least two TCI states based on being served by multiple TRPs.

[0241] The wireless device may determine / select at least two TCI states based on at least one TCI codepoint (e.g., TCI codepoint 001 and TCI codepoint 010 in FIGS. 21A and 21B) of the one or more TCI codepoints including / indicating at least two activated TCI states. The wireless device may determine / select at least two TCI states based on the TCI codepoint (e.g., indicated by a TCI field of a DCI or a configured uplink grant) indicating at least two activated TCI states. The wireless device may determine / select at least two TCI states based on the DCI indicating at least two uplink resources. The wireless device may determine / select at least two TCI states based on the configured uplink grant indicating at least two uplink resources.

[0242] The wireless device may determine / select at least two TCI states based on one or more configuration parameters indicating at least two CORESET pool indicators / indices for one or more CORESETs. A first TRP of the multiple TRPs may transmit / transmit a DCI via one or more first CORESETs having a first CORESET pool indicator / indices (e.g., 0 or any other first value). The first TRP may not transmit / transmit a DCI via one or more second CORESETs having a second CORESET pool indicator / indices (e.g., 1 or any other second value). A second TRP of the multiple TRPs may not transmit / transmit a DCI via one or more first CORESETs having the first CORESET pool indicator / indices. The second TRP may transmit / transmit a DCI via one or more second CORESETs having the second CORESET pool indicator / indices. The at least two CORESET pool indicators / indexes may include a first CORESET pool indicator / index and a second CORESET pool indicator / index. The one or more CORESETs may include one or more first CORESETs and one or more second CORESETs. The first CORESET pool indicator / index may be different from the second CORESET pool indicator / index.

[0243] The wireless device may determine / select at least two TCI states based on, for example, that the one or more configuration parameters include an enablement parameter. The enablement parameter may be enabled. The one or more configuration parameters may indicate that the enablement parameter is enabled.

[0244] The wireless device may determine / select at least two TCI states based on, for example, that the one or more configuration parameters include a second enabling parameter. The second enabling parameter may be enabled. The one or more configuration parameters may indicate that the second enabling parameter is enabled.

[0245] The wireless device may determine / select at least two TCI states based on, for example, one or more configuration parameters indicating a repetition scheme (e.g., an FDM scheme, a TDM scheme, an SDM scheme, a CDM scheme). The repetition scheme may be for repetition of transmission of a transport block (e.g., PUSCH repetition).

[0246] The wireless device may determine / select at least two TCI states based on, for example, the wireless device capability information indicating / including support for beam capability without uplink beam sweeping. The wireless device may determine / select at least two TCI states based on, for example, the wireless device capability information indicating support for transmission repetition (e.g., for transmission of a transport block).

[0247] The wireless device may determine / select at least two TCI states based on, for example, at least one path loss reference RS not being provided. The wireless device may determine / select at least two TCI states based on, for example, one or more configuration parameters not indicating at least one path loss reference RS. The wireless device may determine / select at least two TCI states based on, for example, not receiving an activation command indicating at least one path loss reference RS.

[0248] The wireless device may determine / select the at least two TCI states, for example, based on the fact that a spatial relationship (e.g., PUCCH-SpatialRelationInfo, spatialRelationInfo) is not provided (e.g., for at least two uplink resources). The wireless device not being provided with a spatial relationship for the at least two uplink resources may include each uplink resource of the at least two uplink resources being provided with a spatial relationship. The wireless device may determine / select the at least two TCI states, for example, based on the fact that one or more configuration parameters do not indicate a spatial relationship (e.g., for the at least two uplink resources). The fact that one or more configuration parameters do not indicate a spatial relationship for the at least two uplink resources may include the fact that one or more configuration parameters do not indicate a spatial relationship for each uplink resource of the at least two uplink resources.

[0249] The wireless device may determine / select the at least two TCI states based on, for example, not receiving one or more activation commands that indicate a spatial relationship (e.g., for at least two uplink resources). The wireless device's not receiving one or more activation commands that indicate a spatial relationship for the at least two uplink resources may include the wireless device not receiving one or more activation commands that indicate a respective spatial relationship for each uplink resource of the at least two uplink resources.

[0250] The DCI may include a time domain resource alignment (TDRA) field. One or more configuration parameters may indicate the TDRA field for a configured uplink grant (e.g., a type 1 configured uplink grant). The TDRA field may indicate a resource allocation table. The resource allocation table may be indicated / configured by one or more configuration parameters. The resource allocation table may be pre-configured (e.g., fixed). The TDRA field may indicate an amount of repetitions (e.g., number of repetitions) for a transport block. The resource allocation table may include / indicate the amount of repetitions (e.g., number of repetitions). The amount of repetitions (e.g., number of repetitions) may be indicated / indicated by the resource allocation table. The wireless device may determine / select at least two TCI states, for example, based on the TDRA field indicating the amount of repetitions. For example, as shown in Figures 17 and 19, the number of repetitions may be equal to four (e.g., number of repetitions = 4). In other examples, the amount of repeats may be equal to any other value.

[0251] A higher layer parameter indicating the amount of repetitions (e.g., number of repetitions) may or may not be present in the resource allocation table indicated by the TDRA field of the DCI. A higher layer parameter indicating the amount of repetitions (e.g., number of repetitions) may or may not be present in the resource allocation table indicated by the TDRA field of a configured uplink grant (e.g., a Type 1 configured uplink grant). One or more configuration parameters may indicate the amount of repetitions (e.g., via the higher layer parameter pusch-AggregationFactor). The wireless device may, for example, determine / select at least two TCI states based on one or more configuration parameters indicating the amount of repetitions. For example, as shown in Figures 17 and 19, the number of repetitions may be equal to 4 (e.g., pusch-AggregationFactor=4). In other examples, the amount of repetitions may be equal to any other value.

[0252] The DCI may include an antenna port field. One or more configuration parameters may indicate the antenna port field for a configured uplink grant. The antenna port field may indicate a DM-RS port in at least two code division multiplexing (CDM) groups. The wireless device may determine / select at least two TCI states based on, for example, the antenna port field indicating a DM-RS port in at least two CDM groups.

[0253] At least two uplink resources may be dedicated uplink resources. The dedicated uplink resources may not be shared with a second wireless device different from the wireless device. One or more configuration parameters may indicate the dedicated uplink resources. The at least two uplink resources may or may not be indicated / configured using a SIB message.

[0254] The (determined / selected) at least two TCI states may indicate at least two reference signals (e.g., CSI-RS, SSB / PBCH block, SRS, DM-RS). Each TCI state of the at least two TCI states may indicate a respective reference signal of the at least two reference signals. Each TCI state of the at least two TCI states may include a reference signal indicator / index (e.g., provided by higher layer parameters referenceSignal, ssb-index, csi-RS-index, NZP-CSI-RS-ResourceId) that identifies (e.g., indicates) the respective reference signal. A first TCI state of the at least two TCI states (e.g., TCI state 8) may indicate a first reference signal of the at least two reference signals. A second TCI state of the at least two TCI states (e.g., TCI state 23) may indicate a second reference signal of the at least two reference signals. The first TCI state may include a first reference signal indicator / index (e.g., provided by higher layer parameters referenceSignal, ssb-index, csi-RS-Index, NZP-CSI-RS-ResourceId) that identifies (e.g., indicates) a first reference signal. One or more configuration parameters may indicate the first reference signal indicator / index for the first TCI state. The second TCI state may include a second reference signal indicator / index (e.g., provided by higher layer parameters referenceSignal, ssb-index, csi-RS-Index, NZP-CSI-RS-ResourceId) that identifies (e.g., indicates) a second reference signal. One or more configuration parameters may indicate the second reference signal indicator / index for the second TCI state.

[0255] The (determined / selected) at least two TCI states may indicate one or more pseudo collocation types. Each TCI state of the at least two TCI states may indicate a respective pseudo collocation type of the one or more pseudo collocation types. For example, the first TCI state may indicate a first pseudo collocation type for the first reference signal. The second TCI state may indicate a second pseudo collocation type for the second reference signal. The first pseudo collocation type and the second pseudo collocation type may be the same. For example, the first pseudo collocation type may be QCL Type D and the second pseudo collocation type may be QCL Type D. The first pseudo collocation type may be QCL Type A and the second pseudo collocation type may be QCL Type A. The first pseudo collocation type and the second pseudo collocation type may be different. For example, the first quasi-colocation type may be QCL Type A and the second quasi-colocation type may be QCL Type D. The first quasi-colocation type may be QCL Type C and the second quasi-colocation type may be QCL Type B. The one or more quasi-colocation types may include the first quasi-colocation type and the second quasi-colocation type.

[0256] The wireless device may determine multiple spatial domain transmit filters based on at least two TCI states. The wireless device may determine multiple spatial domain transmit filters for transmission of the transport block. The wireless device may perform transmission of the transport block with / using the multiple spatial domain transmit filters. The wireless device may transmit the transport block based on (e.g., with / using) the multiple spatial domain transmit filters (e.g., at time T2 in FIGS. 17 to 20 and / or thereafter).

[0257] The wireless device may determine a spatial domain transmission filter of the plurality of spatial domain transmission filters based on a TCI state of the at least two TCI states. The wireless device may determine each spatial domain transmission filter of the plurality of spatial domain transmission filters based on a respective TCI state of the at least two TCI states. Determining the plurality of spatial domain transmission filters based on the at least two TCI states may include, for example, determining the plurality of spatial domain transmission filters based on at least two reference signals indicated by the at least two TCI states. The wireless device may determine each spatial domain transmission filter of the plurality of spatial domain transmission filters based on a reference signal indicated by the respective TCI state of the at least two TCI states.

[0258] The wireless device may determine a first spatial-domain transmission filter of the plurality of spatial-domain transmission filters, for example, based on a first TCI state (e.g., TCI state 8) of the at least two TCI states. The wireless device may determine the first spatial-domain transmission filter, for example, based on a first reference signal indicated by the first TCI state. The wireless device may transmit / transmit a transport block (or a first portion of the transport block, or one or more first data layers / streams of the transport block) using / with the first spatial-domain transmission filter. The wireless device may determine a second spatial-domain transmission filter of the plurality of spatial-domain transmission filters, for example, based on a second TCI state (e.g., TCI state 23) of the at least two TCI states. The wireless device may determine a second spatial-domain transmission filter, for example, based on a second reference signal indicated by the second TCI state. The wireless device may transmit / transmit a transport block (or a second portion of the transport block, or one or more second data layers / streams of the transport block) using / with the second spatial-domain transmission filter.

[0259] The wireless device may determine a spatial domain transmit filter based on the TCI state for transmission of the transport block. The at least two TCI states may include a TCI state. The multiple spatial domain transmit filters may include a spatial domain transmit filter. The TCI state may indicate a reference signal (e.g., CSI-RS, SSB / PBCH block, SRS, DM-RS) of the at least two reference signals. The TCI state may include a reference signal index / identifier / indicator (e.g., provided by higher layer parameters referenceSignal, ssb-index, csi-RS-Index, NZP-CSI-RS-ResourceId) that identifies (e.g., indicates) the reference signal. One or more configuration parameters may indicate the reference signal index / identifier / indicator for the reference signal. The wireless device may determine the spatial domain transmit filter based on the reference signal indicated by the TCI state.

[0260] The reference signal may be a downlink reference signal. The downlink reference signal may include an SS / PBCH block. The downlink reference signal may include a CSI-RS (e.g., periodic CSI-RS, semi-persistent CSI-RS, aperiodic CSI-RS). The downlink reference signal may include a DM-RS (e.g., PDCCH, PDSCH, etc.). The wireless device may receive the downlink reference signal using a spatial domain receive filter. The wireless device may receive the downlink reference signal based on (e.g., using, with) the spatial domain receive filter. The wireless device may determine, for example, based on the reference signal being a downlink reference signal, that the spatial domain transmit filter used for transmission of the transport block is the same as the spatial domain receive filter used to receive the reference signal indicated by the TCI state. The wireless device may transmit / transmit the transport block based on (e.g., using, with) the spatial domain transmit filter that is the same as the spatial domain receive filter, for example, based on the reference signal being a downlink reference signal. The wireless device may transmit / transmit a transport block based on (e.g., using) the spatial domain receive filter, e.g., based on the reference signal being a downlink reference signal. The wireless device may transmit a transport block based on (e.g., in response to) the spatial domain receive filter, e.g., based on the reference signal being a downlink reference signal. Determining the spatial domain transmit filter based on the TCI state may include determining as the spatial domain transmit filter a spatial domain receive filter used to receive the reference signal indicated by the TCI state. Determining the spatial domain transmit filter based on the TCI state may include determining that the spatial domain transmit filter is the same as the spatial domain receive filter used to receive the reference signal indicated by the TCI state.

[0261] The reference signal may be an uplink reference signal (e.g., periodic SRS, semi-persistent SRS, aperiodic SRS, DM-RS). The wireless device may transmit / transmit the uplink reference signal using a second spatial domain transmit filter. The wireless device may transmit / transmit the uplink reference signal based on (e.g., using, with) the second spatial domain transmit filter. The wireless device may determine that the spatial domain transmit filter used for transmission of the transport block is the same as the second spatial domain receive filter used to transmit the reference signal indicated by the TCI status, for example, based on the reference signal being an uplink reference signal. The wireless device may transmit / transmit the transport block based on (e.g., using, with) the spatial domain transmit filter that is the same as the second spatial domain transmit filter used to transmit / transmit the uplink reference signal, for example, based on the reference signal being an uplink reference signal. The wireless device may transmit / transmit the transport block based on (e.g., using, with) the second spatial domain transmit filter used to transmit / transmit the uplink reference signal, for example, based on the reference signal being an uplink reference signal. Determining the spatial domain transmit filter based on the TCI state may include determining a second spatial domain transmit filter used to transmit / transmit a reference signal indicated by the TCI state as the spatial domain transmit filter. Determining the spatial domain transmit filter based on the TCI state may include determining that the spatial domain transmit filter is the same as the second spatial domain receive filter used to transmit / transmit a reference signal indicated by the TCI state.

[0262] Determining the spatial domain transmit filter based on the TCI state may include determining a spatial domain filter used to transmit and / or receive a reference signal indicated by the TCI state as the spatial domain transmit filter. Determining the spatial domain transmit filter based on the TCI state may include determining a spatial domain transmit filter that is the same as the spatial domain filter used to transmit and / or receive a reference signal indicated by the TCI state.

[0263] Determining the spatial domain transmit filter based on the reference signal indicated by the TCI state may include determining a spatial domain filter used to transmit and / or receive the reference signal as the spatial domain transmit filter. Determining the spatial domain transmit filter based on the reference signal indicated by the TCI state may include determining a spatial domain transmit filter that is the same as the spatial domain filter used to transmit and / or receive the reference signal.

[0264] Determining a spatial domain transmit filter based on a reference signal indicated by the TCI state may include at least one DM-RS port of the transport block (or a portion of the transport block, or at least one data layer / stream of the transport block) being quasi-co-located (QCL) with the reference signal indicated by the TCI state. Determining a spatial domain transmit filter based on a reference signal indicated by the TCI state may include determining at least one DM-RS port of the transport block (or a portion of the transport block, or at least one data layer / stream of the transport block) to be QCLed with the reference signal indicated by the TCI state. At least one DM-RS port of the transport block may be QCLed with the reference signal for a quasi-co-location type (e.g., QCL Type D) indicated by the TCI state.

[0265] The wireless device may determine (e.g., calculate, compute) multiple transmit powers based on at least two TCI states. The wireless device may determine multiple transmit powers for transmission of a transport block. The wireless device may perform transmission of the transport block with / using multiple transmit powers. The wireless device may transmit / transmit the transport block with / using multiple transmit powers (e.g., at or after time T2 in Figures 19 and 20).

[0266] The wireless device may determine (e.g., calculate, compute) a transmit power among the plurality of transmit powers based on a TCI state among the at least two TCI states. The wireless device may determine each transmit power among the plurality of transmit powers based on a respective TCI state among the at least two TCI states. Determining the plurality of transmit powers based on the at least two TCI states may include, for example, determining the plurality of transmit powers based on at least two reference signals indicated by the at least two TCI states. The wireless device may determine each transmit power among the plurality of transmit powers based on, for example, a reference signal indicated by the respective TCI state among the at least two TCI states.

[0267] The wireless device may determine a first transmission power among the plurality of transmission powers based on, for example, a first TCI state (e.g., TCI state 8) among the at least two TCI states. The wireless device may determine the first transmission power based on, for example, a first reference signal indicated by the first TCI state. The wireless device may transmit / transmit a transport block (or a first portion of the transport block, or one or more first data layers / streams of the transport block) using / using the first transmission power. The wireless device may determine a second transmission power among the plurality of transmission powers based on, for example, a second TCI state (e.g., TCI state 23) among the at least two TCI states. The wireless device may determine the second transmission power based on, for example, a second reference signal indicated by the second TCI state. The wireless device may transmit / transmit a transport block (or a second portion of the transport block, or one or more second data layers / streams of the transport block) using / using the second transmission power. The at least two reference signals may include a first reference signal and a second reference signal.

[0268] Determining (e.g., calculating) multiple transmit powers based on at least two reference signals may include determining (e.g., calculating) multiple downlink path loss estimates (or multiple path loss measurements) for the multiple transmit powers. Determining (e.g., calculating) the multiple downlink path loss estimates (or multiple path loss measurements) may be based on measurements (e.g., L1-RSRP, L3-RSRP, or higher filtered RSRP measurements) associated with the at least two reference signals. The wireless device may determine each downlink path loss estimate of the multiple downlink path loss estimates based on measurements (e.g., L1-RSRP, L3-RSRP, or higher filtered RSRP measurements) associated with a respective reference signal of the at least two reference signals. The wireless device may use the multiple downlink path loss estimates to determine multiple transmit powers for transmission of the transport block. The multiple transmit powers may include multiple downlink path loss estimates. The wireless device may determine (e.g., calculate, compute, measure) at least two filtered RSRP values ​​(e.g., L1-RSRP, L3-RSRP) of at least two reference signals for a plurality of downlink path loss estimates. The wireless device may determine at least two filtered RSRP values ​​for transmission of a transport block.

[0269] Determining (e.g., calculating) the first transmit power based on the first reference signal may include determining (e.g., calculating) a first downlink path loss estimate (or a first path loss measurement) for the first transmit power. The first downlink path loss estimate for the first transmit power may be based on a measurement (e.g., an L1-RSRP, an L3-RSRP, or a higher filtered RSRP measurement) associated with the first reference signal. The wireless device may use the first downlink path loss estimate to determine a first transmit power for transmission of a transport block (or a first portion of a transport block, or one or more first data layers / streams of a transport block). The first transmit power may include (e.g., based on) the first downlink path loss estimate. The wireless device may determine (e.g., calculate, measure) a first filtered RSRP (e.g., L1-RSRP, L3-RSRP) of the first reference signal for the first downlink path loss estimate. The wireless device may determine a first filtered RSRP for transmission of the transport block. The plurality of downlink path loss estimates may include the first downlink path loss estimate.

[0270] Determining (e.g., calculating, compute) the second transmit power based on the second reference signal may include determining (e.g., calculating, compute) a second downlink path loss estimate (or second path loss measurement) for the second transmit power. The second downlink path loss estimate (or second path loss measurement) for the second transmit power may be based on a measurement (e.g., an L1-RSRP, L3-RSRP, or higher filtered RSRP measurement) associated with the second reference signal. The wireless device may use the second downlink path loss estimate to determine a second transmit power for transmission of the transport block (or a second portion of the transport block, or one or more second data layers / streams of the transport block). The second transmit power may include (e.g., be based on) the second downlink path loss estimate. The wireless device may determine (e.g., calculate, compute, measure) a second filtered RSRP (e.g., L1-RSRP, L3-RSRP) of a second reference signal for a second downlink path loss estimate. The wireless device may determine a second filtered RSRP for transmission of the transport block. The multiple downlink path loss estimates may include the second downlink path loss estimate.

[0271] The wireless device may determine (e.g., calculate, compute) a transmit power based on the TCI state for transmission of the transport block. The at least two TCI states may include a TCI state. The multiple transmit powers may include transmit powers. The TCI state may indicate a reference signal (e.g., CSI-RS, SSB / PBCH block, SRS, DM-RS). The TCI state may include a reference signal indicator / index / identifier (e.g., provided by higher layer parameters referenceSignal, ssb-index, csi-RS-Index, NZP-CSI-RS-ResourceId) that identifies (e.g., indicates) the reference signal. One or more configuration parameters may indicate the reference signal indicator / index / identifier for the reference signal. The wireless device may determine the transmit power based on the reference signal indicated by the TCI state. The at least two reference signals may include a reference signal.

[0272] At least two reference signals indicated by the at least two TCI states may be periodic. Each reference signal of the at least two reference signals may be periodic. Each reference signal of the at least two reference signals may be periodic with a respective periodicity (e.g., 2 slots, 5 slots, 10 slots, 2 symbols, 5 symbols, etc.). The wireless device may periodically perform measurements of the at least two reference signals (e.g., L1-RSRP measurements, L3-RSRP measurements) based on the periodicity of the at least two reference signals. A first reference signal of the at least two reference signals may be periodic with a first periodicity. One or more configuration parameters may indicate the first periodicity. A second reference signal of the at least two reference signals may be periodic with a second periodicity. The one or more configuration parameters may indicate the second periodicity. The wireless device may periodically perform measurements of the first reference signal (e.g., L1-RSRP measurements, L3-RSRP measurements) based on the periodicity of the first reference signal. The wireless device may periodically perform measurements (e.g., L1-RSRP measurements, L3-RSRP measurements) of the second reference signal based on the second reference signal being periodic.

[0273] The (determined / selected) at least two TCI states may indicate one or more QCL types. Each TCI state of the at least two TCI states may indicate a respective QCL type of the one or more QCL types. A first TCI state of the at least two TCI states may indicate a first QCL type for a first reference signal. A second TCI state of the at least two TCI states may indicate a second QCL type for a second reference signal. The first QCL type may be QCL type D (or any other QCL type). The second QCL type may be QCL type D (or any other QCL type). The one or more QCL types may include the first QCL type and a second QCL type.

[0274] 22 shows an example uplink repetition scheme for transmission (e.g., of a transport block). The repetition scheme may be based on TDM 2204, FDM 2208, or SDM 2212. For example, a transport block may be repeated over multiple transmission opportunities in the time domain based on TDM 2204. A transport block may be repeated over multiple transmission opportunities in the frequency domain based on FDM 2208. A transport block may be repeated over multiple transmission opportunities in the spatial domain based on SDM 2212. Each repetition of a transport block may be transmitted using a corresponding spatial-domain transmit filter (e.g., based on TCI state 1, TCI state 2, etc.).

[0275] A wireless device may transmit / transmit a transport block via (e.g., over, through, with) multiple uplink signal / channel transmission opportunities. A wireless device may repeat (e.g., over, through, with) multiple uplink signal / channel transmission opportunities (e.g., as shown in Figures 17 and 19). Repetition of the transport block may be in the time domain (e.g., TDM 2204). Repetition of the transport block may be in the frequency domain (e.g., FDM 2208). Repetition of the transport block may be in the code / spatial domain (e.g., SDM 2212). The antenna port field may indicate a DM-RS port within a CDM group for the transport block. A wireless device may transmit / transmit a transport block via (e.g., over, through, with) one or more first uplink signal / channel transmission opportunities of multiple uplink signal / channel transmission opportunities with / using a first spatial domain transmit filter. The wireless device may transmit / transmit a transport block via (e.g., over, via, with) one or more second uplink signal / channel transmission opportunities of the plurality of uplink signal / channel transmission opportunities using / using a second spatial domain transmission filter. The plurality of spatial domain transmission filters may include a first spatial domain transmission filter and a second spatial domain transmission filter. The first spatial domain transmission filter may be based on a first TCI state (e.g., TCI state 1). The second spatial domain transmission may be based on a second TCI state (e.g., TCI state 2). The DM-RS port may QCL with a first reference signal indicated by the first TCI state in one or more first uplink signal / channel transmission opportunities. The DM-RS port may QCL with a second reference signal indicated by the second TCI state in one or more second uplink signal / channel transmission opportunities. The at least two TCI states may include a first TCI state and a second TCI state.The wireless device may transmit / transmit a transport block via (e.g., over, through, with) one or more first uplink signal / channel transmission opportunities using / using a first transmit power. The wireless device may transmit / transmit a transport block via (e.g., over, through, with) one or more second uplink signal / channel transmission opportunities using / using a second transmit power. The multiple transmit powers may include a first transmit power and a second transmit power.

[0276] For example, with reference to FIG. 17, a wireless device may transmit a first iteration of a transport block (via first transmission opportunity 1720-1) using a first spatial domain transmit filter based on a first TCI state (TCI state 8), transmit a second iteration of the transport block (via second transmission opportunity 1720-2) using a second spatial domain transmit filter based on a second TCI state (TCI state 23), transmit a third iteration of the transport block (via third transmission opportunity 1720-3) using a first spatial domain transmit filter based on the first TCI state (TCI state 8), and transmit a fourth iteration of the transport block (via fourth transmission opportunity 1720-4) using a second spatial domain transmit filter based on the second TCI state (TCI state 23). Similarly, with respect to FIG. 19, the wireless device may transmit a first iteration of a transport block (via first transmission opportunity 1920-1) using a first spatial domain transmit filter based on a first TCI state (TCI state 8), transmit a second iteration of the transport block (via second transmission opportunity 1920-2) using a second spatial domain transmit filter based on a second TCI state (TCI state 23), transmit a third iteration of the transport block (via third transmission opportunity 1920-3) using the first spatial domain transmit filter based on the first TCI state (TCI state 8), and transmit a fourth iteration of the transport block (via fourth transmission opportunity 1920-4) using a second spatial domain transmit filter based on the second TCI state (TCI state 23).

[0277] A wireless device may transmit / transmit a transport block via an uplink signal / channel transmission opportunity (e.g., as shown in Figures 18 and 20). The antenna port field may indicate DM-RS ports in at least two CDM groups. The wireless device may transmit / transmit a first portion of the transport block (or one or more first data layers / streams, or one or more first DM-RS ports) via an uplink signal / channel transmission opportunity using a first spatial domain transmit filter. The wireless device may transmit / transmit a second portion of the transport block (or one or more second data layers / streams, or one or more second DM-RS ports) via an uplink signal / channel transmission opportunity using a second spatial domain transmit filter. The transport block may include a first portion and a second portion. The transport block may include one or more first data layers / streams and one or more second data layers / streams. The multiple spatial domain transmit filters may include a first spatial domain transmit filter and a second spatial domain transmit filter. One or more first DM-RS ports of the transport block may be QCL'd with a first reference signal indicated by a first TCI state in an uplink signal / channel transmission opportunity. One or more second DM-RS ports of the transport block may be QCL'd with a second reference signal indicated by a second TCI state in an uplink signal / channel transmission opportunity. The at least two TCI states may include a first TCI state and a second TCI state. The wireless device may transmit / transmit a first portion of the transport block via an uplink signal / channel transmission opportunity using a first transmit power. The wireless device may transmit / transmit a second portion of the transport block via an uplink signal / channel transmission opportunity using a second transmit power. The multiple transmit powers may include a first transmit power and a second transmit power.

[0278] The one or more configuration parameters may indicate multiple TCI states (e.g., TCI state 1, TCI state 2, ..., TCI state 128 provided by the higher layer parameter tci-StatesToAddModList in PDSCH_Config, PUSCH_Config, or PUCCH_Config, etc.). The multiple TCI states may be for receiving (and / or decoding) downlink transmissions (e.g., PDSCH transmissions) of / for the cell. The one or more configuration parameters may indicate multiple TCI states for decoding PDSCH transmissions of / for the downlink BWP of the cell. The multiple TCI states may be for transmission of uplink signals (e.g., UCI, PUSCH transmission, transport block, SR, CSI, HARQ-ACK) of / for / at / over uplink resources (e.g., PUSCH resources, PUCCH resources, SRS resources) of the cell. The one or more configuration parameters may indicate multiple TCI states for transmission of uplink signals of / for / at / over uplink resources of the uplink BWP of the cell. The plurality of uplink resources may include this uplink resource.

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

[0280] A wireless device may receive (e.g., at or after time T1 in FIGS. 17-20 ) an activation command (e.g., a TCI describing activation / deactivation for a wireless device-specific PDSCH MAC CE, a TCI describing activation / deactivation for a wireless device-specific PUSCH MAC CE, etc.). The activation command may activate (e.g., select, indicate, or update) at least one TCI state of a plurality of TCI states (e.g., TCI state 5, TCI state 8, TCI state 23, TCI state 4, TCI state 11, and TCI state 1 in FIGS. 21A and 21B ). The activation command may include one or more fields. The one or more fields may indicate at least one TCI state indicator / index of the at least one TCI state. The TCI state index may include at least one TCI state index. The one or more fields may be set to a value (e.g., 1) indicating activation of the at least one TCI state. The wireless device may activate the at least one TCI state based on, for example, one or more fields indicating the at least one TCI state being set to this value.

[0281] The wireless device may map at least one TCI state to one or more TCI code points (e.g., 000, 001, 010, and 011 shown in FIGS. 21A and 21B). Mapping at least one TCI state to one or more TCI code points may include grouping at least one TCI state into one or more TCI code points. Each TCI code point of the one or more TCI code points may include / indicate one or more TCI states of the at least one TCI state. For example, as shown in FIGS. 21A and 21B, the at least one TCI state may include TCI state 5, TCI state 8, TCI state 23, TCI state 4, TCI state 11, and TCI state 1. The one or more TCI code points may include TCI code point 000, TCI code point 001, TCI code point 010, and TCI code point 011. TCI state 5 may be mapped to TCI codepoint 000, TCI state 8 and TCI state 23 may be mapped to TCI codepoint 001, TCI state 4 and TCI state 11 may be mapped to TCI codepoint 010, and TCI state 1 may be mapped to TCI codepoint 011. Each TCI codepoint of the one or more TCI codepoints may be indicated by a value of a TCI field within the DCI. For example, the TCI field may not be equal to 000 to indicate TCI codepoint 000, the TCI field may not be equal to 001 to indicate TCI codepoint 001, etc. The DCI may schedule a transport block (e.g., corresponding to a PDSCH transmission or a PUSCH transmission). The TCI field within the DCI may indicate (or may be equal to) a TCI codepoint of the one or more TCI codepoints. The TCI codepoint may include / indicate a TCI state of at least one TCI state.

[0282] A TCI codepoint among one or more TCI codepoints may indicate one or more (e.g., one or two) TCI states. For example, as shown in Figures 21A and 21B, TCI codepoint 000 may indicate one TCI state (e.g., TCI state 5). TCI codepoint 011 may indicate one TCI state (e.g., TCI state 1). TCI codepoint 001 may indicate two TCI states (e.g., TCI state 8 and TCI state 23). TCI codepoint 010 may indicate two TCI states (e.g., TCI state 4 and TCI state 11).

[0283] A TCI codepoint of one or more TCI codepoints (e.g., TCI codepoint 000 or TCI codepoint 011 in FIGS. 21A and 21B) may include / indicate a single TCI state (e.g., TCI state 5 or TCI state 1). At least one TCI state may include a single TCI state. The wireless device may map a single TCI state to a TCI codepoint.

[0284] A TCI codepoint (e.g., TCI codepoint 001 or TCI codepoint 010 in FIGS. 21A and 21B) among one or more TCI codepoints may include / indicate at least two activated TCI states (e.g., TCI state 8 and TCI state 23 in TCI codepoint 001, or TCI state 4 and TCI state 11 in TCI codepoint 010). At least one TCI state may include at least two activated TCI states. The wireless device may map the at least two activated TCI states to a TCI codepoint.

[0285] The at least one TCI state may include a first TCI state and a second TCI state. The wireless device may map the first TCI state (e.g., TCI state 8) and the second TCI state (e.g., TCI state 23) to one TCI code point (e.g., 001) of the one or more TCI code points. The TCI code point (e.g., TCI code point 001) may include / indicate at least two activated TCI states. The at least two activated TCI states may include the first TCI state and the second TCI state.

[0286] A TCI codepoint (e.g., TCI codepoint 001 and TCI codepoint 010) among the one or more TCI codepoints may include / indicate at least two activated TCI states. At least one TCI codepoint (e.g., TCI codepoint 001 and TCI codepoint 010) among the one or more TCI codepoints may include / indicate at least two activated TCI states. At least one TCI state indicated (e.g., activated, updated, selected) by an activation command may include at least two activated TCI states.

[0287] At least one TCI state may be applicable / used for transmission via the cell (e.g., PDSCH transmission). At least one TCI state may be applicable / used for PDSCH transmission via the cell's active downlink BWP. The wireless device may receive a DCI scheduling a PDSCH transmission for the cell's active downlink BWP. The DCI may indicate a TCI state of the at least one TCI state for reception / decoding of the PDSCH transmission. A TCI codepoint of the one or more TCI codepoints may include the TCI state. A TCI field within the DCI may indicate the TCI codepoint. The wireless device may not receive a DCI indicating a TCI state (e.g., scheduling a PDSCH transmission for the cell's active downlink BWP) that is not among the at least one TCI state. The wireless device may receive / decode a PDSCH transmission based on a TCI state of at least one TCI state, for example, if a DCI scheduling a PDSCH transmission for an active downlink BWP of the cell indicates the TCI state for reception / decoding of the PDSCH transmission. Receiving / decoding the PDSCH transmission based on the TCI state may include determining, for a QCL type (e.g., QCL type D) indicated by the TCI state, at least one DM-RS port of the PDSCH to be QCLed with a reference signal indicated by the TCI state. Receiving / decoding the PDSCH transmission based on the TCI state may include QCLed with a reference signal indicated by the TCI state for a QCL type (e.g., QCL type D) indicated by the TCI state.

[0288] A wireless device may receive a DCI scheduling a PDSCH transmission (or TB). The wireless device may receive the DCI via a scheduling cell. The DCI may schedule a PDSCH transmission for an active downlink BWP of the cell. The DCI may indicate a TCI state among at least one TCI state. The DCI may include a TCI field indicating the TCI state. The wireless device may receive / decode a PDSCH transmission for an active downlink BWP of the cell based on the TCI state, e.g., based on the TCI field indicating the TCI state. The one or more TCI codepoints may include a TCI codepoint. The TCI codepoint may include a TCI state. A value of the TCI field in the DCI may be equal to a value associated with the TCI codepoint.

[0289] At least one TCI state may be applicable / used for uplink transmission (e.g., PUSCH transmission, PUCCH transmission) via the cell. At least one TCI state may be applicable / used for uplink transmission in an active uplink BWP of the cell. The wireless device may receive a DCI scheduling uplink transmission for the active uplink BWP of the cell. The DCI may indicate a TCI state of the at least one TCI state for the uplink transmission. A TCI codepoint of the one or more TCI codepoints may include the TCI state. A TCI field in the DCI may indicate the TCI codepoint. The wireless device may not receive a DCI scheduling uplink transmission for the active uplink BWP of the cell that indicates a TCI state that is not among the at least one TCI state for the uplink transmission. The wireless device may perform uplink transmission based on a TCI state of the at least one TCI state, for example, if the DCI scheduling uplink transmission for the active uplink BWP of the cell indicates a TCI state for the uplink transmission. Performing uplink transmission based on the TCI state may include determining at least one DM-RS port of the uplink transmission to be QCLed with a reference signal indicated by the TCI state for a QCL type indicated by the TCI state (e.g., QCL Type D). Performing uplink transmission based on the TCI state may include determining at least one DM-RS port of the uplink transmission to be QCLed with a reference signal indicated by the TCI state for a QCL type indicated by the TCI state (e.g., QCL Type D).

[0290] The wireless device may receive a DCI scheduling an uplink transmission (e.g., a PUSCH transmission, a PUCCH transmission, a TB). The wireless device may receive the DCI via a scheduling cell. The DCI may schedule an uplink transmission for an active uplink BWP of the cell. The DCI may indicate a TCI state of at least one TCI state. The DCI may include a TCI field indicating the TCI state. The wireless device may perform an uplink transmission for the active uplink BWP of the cell based on the TCI state, e.g., based on the TCI field indicating the TCI state. The one or more TCI codepoints may include a TCI codepoint. The TCI codepoint may include a TCI state. The value of the TCI field in the DCI may be equal to the value of the TCI codepoint.

[0291] The wireless device may determine that at least one TCI codepoint (e.g., TCI codepoint 001 and TCI codepoint 010) of the one or more TCI codepoints indicates (e.g., includes, encompasses) at least two activated TCI states (e.g., TCI state 8 and TCI state 23 for TCI codepoint 001, TCI state 4 and TCI state 11 for TCI codepoint 010). The at least one TCI state indicated (e.g., activated, updated, or selected) by the activation command may include the at least two activated TCI states.

[0292] At least two activated TCI states indicated by a TCI codepoint of the at least one TCI codepoint may be different. For example, a TCI codepoint of the at least one TCI codepoint may indicate (e.g., include, encompass) at least two activated TCI states. A first TCI state of the at least two activated TCI states may be different from a second TCI state of the at least two activated TCI states.

[0293] The wireless device may determine / select the selected TCI codepoint from among the at least one TCI codepoint. The wireless device may determine / select the selected TCI codepoint from among the at least one TCI codepoint based on determining that the at least one TCI codepoint indicates (e.g., includes, encompasses) at least two activated TCI states.

[0294] The wireless device may determine / select a selected TCI codepoint from the at least one TCI codepoint, for example, based on whether the selected TCI codepoint has / is the lowest (or highest) TCI codepoint from the at least one TCI codepoint. The wireless device may determine / select a selected TCI codepoint from the at least one TCI codepoint based on whether the selected TCI codepoint is the lowest (or highest) from the at least one TCI codepoint. For example, with reference to FIGS. 21A and 21B, the at least one TCI codepoint may include a first TCI codepoint (TCI codepoint 001) and a second TCI codepoint (TCI codepoint 010). The wireless device may select the first TCI codepoint (TCI codepoint 001) as the selected TCI codepoint, for example, based on whether the first TCI codepoint (TCI codepoint 001) has / is a lower (or higher) TCI codepoint than the second TCI codepoint (TCI codepoint 010). The wireless device may, for example, select the first TCI codepoint (TCI codepoint 001) as the selected TCI codepoint based on the first TCI codepoint (TCI codepoint 001) being lower (or higher) than the second TCI codepoint (TCI codepoint 010).

[0295] At least one TCI codepoint may indicate / include a second plurality of TCI states (e.g., TCI state 8, TCI state 23, TCI state 4, TCI state 11). The wireless device may determine / select a selected TCI codepoint from the at least one TCI codepoint, for example, based on the selected TCI codepoint including / indicating a TCI state having the lowest (or highest) TCI state indicator / index among the second plurality of TCI state indicators / indexes of the second plurality of TCI states. The at least one TCI state indicated (e.g., selected, activated, or updated) by the activation command may include the second plurality of TCI states. The at least one TCI state indicator / index of the at least one TCI state may include the second plurality of TCI state indicators / indexes. For example, with reference to FIGS. 21A and 21B, the at least one TCI codepoint may include a first TCI codepoint (TCI codepoint 001) and a second TCI codepoint (TCI codepoint 010). The second plurality of TCI states may include TCI state 8, TCI state 23, TCI state 4, and TCI state 11. The wireless device may select the first TCI codepoint (TCI codepoint 010) as the selected TCI codepoint, for example, based on the first TCI state indicator / index of TCI state 8 at the first TCI codepoint (TCI codepoint 001) being lower (or higher) than the second TCI state indicator / index of TCI state 4 at the second TCI codepoint (TCI codepoint 001) and the third TCI state indicator / index of TCI state 11.The wireless device may select the second TCI codepoint (TCI codepoint 010) as the selected TCI codepoint, for example, based on the fact that the third TCI state indicator / index of TCI state 11 at the second TCI codepoint (TCI codepoint 010) is lower (or higher) than the first TCI state indicator / index of TCI state 8 at the first TCI codepoint (TCI codepoint 001) and the second TCI state indicator / index of TCI state 23.

[0296] The selected TCI codepoint may indicate at least two activated TCI states. With reference to Figures 21A and 21B, the at least two activated TCI states may be, for example, TCI state 8 and TCI state 23 when the selected TCI codepoint is TCI codepoint 001. The at least two activated TCI states may be, for example, TCI state 4 and TCI state 11 when the selected TCI codepoint is TCI codepoint 010.

[0297] The at least two activated TCI states indicated by the selected TCI code point may include a first TCI state and a second TCI state. The first TCI state of the at least two activated TCI states may be a first element / member in a set / vector including the at least two activated TCI states. The second TCI state of the at least two activated TCI states may be a second element / member in a set / vector including the at least two activated TCI states. For example, if the at least two activated TCI states include TCI state 8 and TCI state 23, the first TCI state may be TCI state 8 and the second TCI state may be TCI state 23. For example, if the at least two activated TCI states include TCI state 4 and TCI state 11, the first TCI state may be TCI state 4 and the second TCI state may be TCI state 11.

[0298] The wireless device may determine / select at least two TCI states for transmission of the transport block based on the selected TCI codepoint. The (determined / selected) at least two TCI states may be at least two activated TCI states indicated by the selected TCI codepoint. With reference to FIG. 21A , the (determined / selected) at least two TCI states may be, for example, TCI state 8 and TCI state 23 if the selected TCI codepoint is TCI codepoint 001. The (determined / selected) at least two TCI states may be, for example, TCI state 4 and TCI state 11 if the selected TCI codepoint is TCI codepoint 010.

[0299] The spatial configuration for transport block transmission may be the same as the spatial configuration for PDSCH reception in at least two activated TCI states. The at least two activated TCI states may correspond to (or be indicated by) the lowest TCI codepoint (or may correspond to a selected TCI codepoint) among one or more TCI codepoints that encompass / include two different TCI states (e.g., at least two activated TCI states) on the active downlink BWP of the cell. The spatial configuration for transport block transmission may be the same as the spatial configuration for PUSCH transmission in at least two activated TCI states. The at least two activated TCI states may correspond to (or be indicated by) the lowest TCI codepoint (or may correspond to a selected TCI codepoint) among one or more TCI codepoints that encompass / include two different TCI states (e.g., at least two activated TCI states) on the active uplink BWP of the cell.

[0300] The wireless device may determine / calculate multiple transmission powers. To determine / calculate multiple transmission powers, the wireless device may determine at least two RS resource indicators / indexes that provide at least two RS resources (e.g., having QCL type D) in at least two activated TCI states. The at least two activated TCI states may correspond to (or be indicated by) a lowest TCI code point (or may correspond to a selected TCI code point) among one or more TCI code points that encompass two different TCI states (e.g., at least two activated TCI states) on an active downlink BWP of the cell.

[0301] The wireless device may determine / select at least two TCI states for transmission of the transport block. The wireless device may determine / select at least two TCI states based on the selected TCI code point and the first CORESET. The wireless device may determine / select a first TCI state of the at least two TCI states based on a first TCI state of the first CORESET (e.g., TCI state 8 of the first CORESET in FIG. 21B). The first CORESET may be identified / indicated by a CORESET indicator / index that is the lowest among one or more CORESET indicators / indexes of the one or more CORESETs. The first TCI state of the at least two TCI states may be the first TCI state of the first CORESET identified / indicated by a CORESET indicator / index that is the lowest among one or more CORESET indicators / indexes of the one or more CORESETs. The wireless device may determine / select a second TCI state of the at least two TCI states based on a second TCI state of the at least two activated TCI states indicated by the selected TCI code point. The second TCI state of the at least two TCI states may be the second TCI state of the at least two activated TCI states indicated by the selected TCI code point (e.g., TCI state 23 in TCI code point 001 in FIG. 21B). The second TCI state of the at least two activated TCI states indicated by the selected TCI code point may be, for example, a second element / member in a set / vector including the at least two activated TCI states indicated by the selected TCI code point.

[0302] A first spatial configuration for transmission (e.g., of a transport block) may be the same as a spatial configuration for reception (e.g., PDCCH reception) via a first CORESET with the lowest CORESET indicator / index. A second spatial configuration for transmission (e.g., of a transport block) may be the same as a spatial configuration for reception (e.g., PDSCH reception) based on a second TCI state corresponding to the lowest TCI codepoint (or corresponding to a selected TCI codepoint) of the one or more TCI codepoints. The one or more TCI codepoints may include / cover two different TCI states (e.g., at least two activated TCI states) on the active downlink BWP of the cell.

[0303] A first spatial configuration for a transmission (e.g., of a transport block) may be the same as a spatial configuration for a transmission (e.g., PDCCH transmission) via a first CORESET with the lowest CORESET indicator / index. A second spatial configuration for a transmission (e.g., of a transport block) may be the same as a spatial configuration for reception (e.g., PUSCH reception) based on a second TCI state corresponding to the lowest TCI codepoint (or corresponding to a selected TCI codepoint) of the one or more TCI codepoints. The one or more TCI codepoints may include / cover two different TCI states (e.g., at least two activated TCI states) on the active uplink BWP of the cell.

[0304] The wireless device may determine a plurality of transmission powers. To determine the plurality of transmission powers, the wireless device may determine a first RS resource indicator / index that provides a first RS resource (e.g., having QCL type D) in a first TCI state (or QCL hypothesis) of a first CORESET (e.g., having a lowest CORESET index / indicator). To determine the plurality of transmission powers, the wireless device may determine a second RS resource indicator / index that provides a second RS resource (e.g., having QCL type D) in a second TCI state corresponding to the lowest TCI codepoint (or corresponding to a selected TCI codepoint) among the one or more TCI codepoints. The one or more TCI codepoints may include / encompass two different TCI states (e.g., at least two activated TCI states) on the active downlink BWP of the cell.

[0305] The quantity of one or more CORESETs may be two or more. The wireless device may select / determine at least two CORESETs from the one or more CORESETs. The at least two CORESETs (e.g., the first CORESET and the second CORESET in FIG. 21C ) may be identified / indicated by at least two CORESET indicators / indices from the one or more CORESET indicators / indices. Each CORESET from the at least two CORESETs may be identified / indicated by a respective CORESET indicator / index from the at least two CORESET indicators / indices. The at least two CORESET indexes may be the lowest (or highest) two CORESET indexes from the one or more CORESET indexes. The at least two CORESETs may be identified / indicated by at least two CORESET indexes that are the lowest (or highest) among one or more CORESET indexes of the one or more CORESETs. The at least two CORESETs may be identified / indicated by at least two lowest (or highest) CORESET indexes among one or more CORESET indexes of the one or more CORESETs. Selecting / determining the at least two CORESETs may include selecting / determining at least two CORESETs identified / indicated using at least two CORESET indexes that are lowest among one or more CORESET indexes of the one or more CORESETs. Selecting / determining the at least two CORESETs may include selecting / determining at least two CORESETs identified / indicated using at least two lowest CORESET indexes among one or more CORESET indexes of the one or more CORESETs. The wireless device may select / determine at least two CORESETs of the one or more CORESETs based on, for example, at least two CORESET indexes of the at least two CORESETs being lowest (or highest) among one or more CORESET indexes of the one or more CORESETs.The amount of at least two CORESETs may be 2 (or any other amount greater than 2). The one or more CORESETs may include a first CORESET, a second CORESET, a third CORESET, and a fourth CORESET. The one or more CORESET indexes may include a first CORESET index of the first CORESET, a second CORESET index of the second CORESET, a third CORESET index of the third CORESET, and a fourth CORESET index of the fourth CORESET. The first CORESET index may be the lowest (or highest) among the first CORESET index, the second CORESET index, the third CORESET index, and the fourth CORESET index. The second CORESET index may be lower (or higher) than the third CORESET index and the fourth CORESET index. The wireless device may select / determine the first CORESET and the second CORESET as at least two CORESETs, for example, based on the first CORESET index and the second CORESET index being the lowest (or highest) two CORESET indexes among the first CORESET index, the second CORESET index, the third CORESET index, and the fourth CORESET index.

[0306] The wireless device may monitor the downlink control channel for DCI in the at least two CORESETs based on at least two activated TCI states (e.g., TCI state 8 of the first CORESET and TCI state 23 of the second CORESET shown in FIG. 21C ). The wireless device may, for example, monitor the downlink control channel for DCI in each CORESET of the at least two CORESETs based on the respective TCI states of the at least two activated TCI states. Monitoring the downlink control channel for DCI in the at least two CORESETs based on the at least two activated TCI states may include quasi-co-locating DM-RS antenna ports of the downlink control channel (e.g., PDCCH) in the at least two CORESETs with at least two reference signals indicated by the at least two activated TCI states. Each DM-RS antenna port among the DM-RS antenna ports in (or associated with) each CORESET of the at least two CORESETs may be quasi-colocated with a reference signal among the at least two reference signals indicated by a respective TCI state among the at least two activated TCI states. The wireless device may monitor a downlink control channel for DCI in a first CORESET of the at least two CORESETs (e.g., the first CORESET of FIG. 21C ) based on a first TCI state among the at least two activated TCI states (e.g., TCI State 8 of FIG. 21C ). Monitoring the downlink control channel in the first CORESET based on the first TCI state may include one or more DM-RS antenna ports of a downlink control channel (e.g., PDCCH) in the first CORESET being quasi-colocated with a first reference signal indicated by the first TCI state. One or more DM-RS antenna ports may be quasi-collocated with a first reference signal for a first quasi-collocation type indicated by the first TCI state.The wireless device may monitor a downlink control channel for DCI in a second CORESET of the at least two CORESETs (e.g., the second CORESET of FIG. 21C ) based on a second TCI state of the at least two activated TCI states (e.g., TCI state 23 of FIG. 21C ). Monitoring the downlink control channel in the second CORESET based on the second TCI state may include one or more DM-RS antenna ports of a downlink control channel (e.g., a PDCCH) in the second CORESET being quasi-colocated with a second reference signal indicated by the second TCI state. The one or more DM-RS antenna ports may be quasi-colocated with the second reference signal for a second quasi-colocation type indicated by the second TCI state. The at least two reference signals may include a first reference signal and a second reference signal.

[0307] The one or more configuration parameters may indicate at least two activated TCI states (e.g., provided by the higher layer parameter tci-StatesPDCCH-ToAddList) for the at least two CORESETs. The one or more configuration parameters may indicate each TCI state of the at least two activated TCI states for each CORESET of the at least two CORESETs. The one or more configuration parameters may indicate a first TCI state for a first CORESET. The one or more configuration parameters may indicate a second TCI state for a second CORESET.

[0308] The wireless device may receive (e.g., at or after time T1 in FIGS. 17-20 ) one or more activation commands (e.g., TCI state indications for wireless device-specific PDCCH MAC CEs) that activate (e.g., select, indicate, or update) at least two activated TCI states for at least two CORESETs. Each activation command of the one or more activation commands may activate (e.g., select, indicate, update) a respective TCI state of the at least two activated TCI states for a CORESET of the at least two CORESETs. A first activation command of the one or more activation commands may activate a first TCI state for the first CORESET. One or more configuration parameters may indicate multiple TCI states (e.g., provided by higher layer parameter tci-StatesPDCCH-ToAddList) for the first CORESET. The first activation command may activate a first TCI state of the multiple TCI states for the first CORESET. A second activation command of the one or more activation commands may activate a second TCI state for the second CORESET. The one or more configuration parameters may indicate multiple TCI states for the second CORESET (e.g., provided by higher layer parameter tci-StatesPDCCH-ToAddList). The second activation command may activate a second TCI state of the multiple TCI states for the second CORESET. The first activation command and the second activation command may or may not be the same. The wireless device may receive the first activation command and the second activation command at the same time (e.g., simultaneously) or at different times.

[0309] For example, the wireless device may determine / select at least two TCI states for transmission of a transport block based on at least two CORESETs. The (determined / selected) at least two TCI states may be at least two activated TCI states indicat...

Claims

1. 1. A method comprising: receiving, by the wireless device, a radio resource control (RRC) message associated with a configured uplink grant, where the RRC message comprises: a first sounding reference signal (SRS) resource indicator (SRI) field indicating a first SRS resource in a first SRS resource set; a second SRI field indicating a second SRS resource in a second SRS resource set different from the first SRS resource set; transmitting at least one first repetition of a transport block associated with the configured uplink grant based on the first SRI field; and transmitting at least a second repetition of the transport block based on the second SRI field.

2. 2. The method of claim 1 , wherein transmitting the at least one first repetition of the transport block comprises transmitting the at least one first repetition of the transport block using a first spatial domain transmit filter associated with a first spatial relationship of the first SRS resource, and transmitting the at least one second repetition of the transport block comprises transmitting the at least one second repetition of the transport block using a second spatial domain transmit filter associated with a second spatial relationship of the second SRS resource.

3. and receiving at least one configuration parameter for the cell, the at least one configuration parameter comprising: the first SRS resource set; The method according to claim 1 or 2, further comprising: indicating the second SRS resource set.

4. determining the first spatial domain transmit filter for the transmission of the at least one first iteration of the transport block based on the first SRS resource; and determining the second spatial domain transmit filter for the transmission of the at least one second iteration of the transport block based on the second SRS resource.

5. determining the first spatial domain transmit filter includes determining the first spatial domain transmit filter based on a first reference signal indicated by the first spatial relationship of the first SRS resource; 5. The method of claim 4, wherein the determining the second spatial domain transmit filter comprises determining the second spatial domain transmit filter based on a second reference signal indicated by the second spatial relationship of the second SRS resource.

6. 6. The method of claim 1, wherein transmitting the at least one first repetition of the transport block comprises transmitting the at least one first repetition of the transport block using a first transmission power based on the first SRS resource, and transmitting the at least one second repetition of the transport block comprises transmitting the at least one second repetition of the transport block using a second transmission power based on the second SRS resource.

7. 7. The method of claim 2, further comprising receiving an activation command indicating, for the first SRS resource, the first spatial relationship associated with the first spatial domain transmit filter and, for the second SRS resource, the second spatial relationship associated with the second spatial domain transmit filter.

8. 2. The method of claim 1 , wherein transmitting the at least one first repetition of the transport block comprises transmitting the at least one first repetition of the transport block using a first spatial domain transmit filter associated with a first default Transmission Configuration Indication (TCI) state, and transmitting the at least one second repetition of the transport block comprises transmitting the at least one second repetition of the transport block using a second spatial domain transmit filter associated with a second default TCI state.

9. 9. The method of claim 8, wherein the transmitting the at least one first repetition of the transport block comprises transmitting the at least one first repetition of the transport block using a first transmit power based on the first default TCI state, and the transmitting the at least one second repetition of the transport block comprises transmitting the at least one second repetition of the transport block using a second transmit power based on the second default TCI state.

10. 10. The method of claim 8, wherein the transmitting of the at least one first iteration of the transport block using the first spatial domain transmit filter associated to the first default TCI state and the transmitting of the at least one second iteration of the transport block using the second spatial domain transmit filter associated to the second default TCI state are based on the first SRS resource being not associated with a spatial relationship and the second SRS resource being not associated with a spatial relationship.

11. transmitting the at least one first repetition of the transport block includes transmitting at least one first Physical Uplink Shared Channel (PUSCH) transmission during at least one first transmission opportunity; 11. The method of claim 1, wherein transmitting the at least one second repetition of the transport block comprises transmitting at least one second PUSCH transmission during at least one second transmission opportunity that is different from the at least one first transmission opportunity.

12. The method according to any one of claims 1 to 11, wherein the configured uplink grant is a configured uplink grant of type 1.

13. 1. A wireless device, comprising: one or more processors; A wireless device comprising: a memory storing instructions which, when executed by the one or more processors, cause the wireless 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 12; a base station configured to transmit the RRC message associated with the configured uplink grant.

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

Images