Resource grouping for repeated sends

Abstract

A wireless device may be configured with resources for communicating with a base station. One or more repetitions may be transmitted using resources such as sounding reference signal (SRS) resources using at least two transmission and reception points. Repetitions may be prioritized over single transmissions based on resource availability. For example, transmissions of lower priority types of information configured with resources for repetitions may be prioritized over transmissions of higher priority types of information configured with resources for only single transmissions, such that increased utilization of repetitions may be achieved.

Description

[Background technology]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims the benefit of U.S. Provisional Patent Application No. 63 / 296,030, filed January 3, 2022. The above-mentioned applications are incorporated herein by reference in their entireties.

[0002] The wireless device communicates with the base station using a transmission and reception point (TRP). The wireless device is configured with a sounding reference signal (SRS) resource for communicating using the TRP. Summary of the Invention

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

[0004] A wireless device may be configured with resources for communicating with a base station. For example, time / frequency resources such as SRS resources may be used by the wireless device for transmission. At least some of these time / frequency resources (e.g., SRS resource sets) may be configured for components (e.g., TRPs, antennas, antenna panels, etc.) used for transmission. For example, a wireless device may include a quantity of components (e.g., TRPs) that may be configured with respective amounts of time / frequency resources (e.g., SRS resource sets), which may enable the wireless device to transmit repetitions of a message, which may increase the likelihood of successful reception of the message. However, repetition of a first message may not be possible, for example, if a second message has a higher priority than the first message and is configured without sufficient resources for repetition. For example, at least some time / frequency resources may be grouped for a type of communication (e.g., one or more SRS resource sets may be grouped within an SRS resource set list) such that one or more SRS resource sets are included in a first SRS resource set list for a first type of communication (e.g., ultra-reliable low latency communication (uRLLC) or any other type or communication) and one or more SRS resource sets are included in a second SRS resource set list for a second type of communication (e.g., enhanced mobile broadband (eMBB) or any other type of communication). If a low priority message has at least two SRS resource sets configured in the SRS resource set list associated with its communication type and a higher priority message has only one SRS resource set configured in the SRS resource set list associated with its communication type, repetition may not be possible when priority levels determine which messages are transmitted.As a result, configured resources may be wasted / unused (e.g., a high priority message may be transmitted over one TRP while a low priority message may be transmitted repeatedly over two TRPs). However, as described herein, communications configured with resources (e.g., SRS resource set lists) that can accommodate message repetition over multiple components (e.g., multiple TRPs) may be prioritized over the priority level of the message type, which may increase the use of repetition, which in turn may provide benefits such as increased efficiency of configured resources and / or increased likelihood of successful reception of wireless communications.

[0005] These and other features and advantages are described in greater detail below. [Brief description 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 like elements and in which: [Figure 1A] FIG. 1A illustrates an embodiment of a communication network. [Figure 1B] FIG. 1B illustrates an embodiment of a communication network. [Figure 2A] FIG. 2A illustrates an exemplary user plane. [Figure 2B] FIG. 2B illustrates an example of a control plane configuration. [Diagram 3] FIG. 3 shows an embodiment of the protocol layers. [Figure 4A] FIG. 4A illustrates an example of downlink data flow in a user plane configuration. [Figure 4B] FIG. 4B illustrates an example format of a Medium Access Control (MAC) subheader of a MAC Protocol Data Unit (PDU). [Figure 5A] FIG. 5A shows an example of downlink channel mapping. [Figure 5B] FIG. 5B shows an example of uplink channel mapping. [Figure 6]FIG. 6 illustrates an example of Radio Resource Control (RRC) states and RRC state transitions. [Figure 7] FIG. 7 shows an example of a frame structure. [Figure 8] FIG. 8 illustrates an example resource configuration for one or more carriers. [Figure 9] FIG. 9 shows an example of the configuration of the bandwidth portion (BWP). [Figure 10A] FIG. 10A illustrates an example carrier aggregation configuration based on component carriers. [Figure 10B] FIG. 10B shows an example group of cells. [Figure 11A] FIG. 11A shows an example mapping of one or more synchronization signal / physical broadcast channel (SS / PBCH) blocks. [Figure 11B] FIG. 11B illustrates an example mapping of one or more channel state information reference signals (CSI-RS). [Figure 12A] FIG. 12A shows an example of a downlink beam management procedure. [Figure 12B] FIG. 12B shows an example of an uplink beam management procedure. [Figure 13A] FIG. 13A shows an example of a four-step random access procedure. [Figure 13B] FIG. 13B shows an example of a two-step random access procedure. [Figure 13C] FIG. 13C shows an example of a two-step random access procedure. [Figure 14A] FIG. 14A shows an example of a control resource set (CORESET) configuration. [Figure 14B] FIG. 14B illustrates an example of mapping of control channel elements to resource element groups (CCE-to-REG). [Figure 15A] FIG. 15A illustrates an example of communication between a wireless device and a base station. [Figure 15B]FIG. 15B illustrates exemplary elements of a computing device that may be used to implement any of the various devices described herein. [Figure 16A] FIG. 16A illustrates an example of uplink and downlink signal transmission. [Figure 16B] FIG. 16B illustrates an example of uplink and downlink signal transmission. [Figure 16C] FIG. 16C illustrates an example of uplink and downlink signal transmission. [Figure 16D] FIG. 16D illustrates an example of uplink and downlink signal transmission. [Figure 17] FIG. 17 illustrates an example TCI status update. [Figure 18A] FIG. 18A illustrates an exemplary method for unified beam updating. [Figure 18B] FIG. 18B illustrates an exemplary method for unified beam updating. [Figure 19A] FIG. 19A shows an example of uplink transmission / reception. [Figure 19B] FIG. 19B shows an example of uplink transmission / reception. [Figure 20A] FIG. 20A illustrates an example of an uplink transmission and reception method. [Figure 20B] FIG. 20B illustrates an example of an uplink transmission and reception method. [Figure 21] FIG. 21 illustrates an exemplary method of uplink transmission. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0007] The accompanying drawings and description provide examples. It should be understood that the examples shown in the drawings and / or description are non-exclusive, and the features shown and described may be practiced in other examples. An example is provided for the operation of a wireless communication system that may be used in the technical field of multi-carrier communication systems. More specifically, the techniques disclosed herein may relate to wireless communication exposure detection and / or reporting.

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

[0009] The wireless device 106 may communicate with the RAN 104 via wireless communication over the air interface. The RAN 104 may communicate with the CN 102 via various communications (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 and / or downlink communication direction. The communication direction from the wireless device 106 to the RAN 104 over / through the air interface may be referred to as the uplink and / or uplink communication direction. The downlink transmission may be separated and / or differentiated 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-portable) device configured or enabled for wireless communication, a computing device, a node, a wireless communication-enabled device, or any other device capable of transmitting and / or receiving signals. As non-limiting examples, a wireless device may include, for example, a telephone, a cell phone, a Wi-Fi phone, a smartphone, a tablet, a computer, a laptop, a sensor, a meter, a wearable device, an Internet of Things (IoT) device, a hotspot, a cellular repeater, a vehicular roadside unit (RSU), a relay node, an automobile, a wireless user device (e.g., user equipment (UE), user terminal (UT), etc.), an access terminal (AT), a mobile station, a handset, a wireless transmit / receive unit (WTRU), a wireless communication device, and / or any combination thereof.

[0011] The RAN 104 may include one or more base stations (not shown). As used throughout, the term "base station" may include one or more of a base station, node, Node B (NB), Evolved Node B (eNB), gNB, ng-eNB, relay node (e.g., integrated access and backhaul (IAB) node, etc.), donor node (e.g., donor eNB, donor gNB, etc.), access point (e.g., Wi-Fi access point, etc.), transmit / receive point (TRP), computing device, device capable of wireless communication, or other device capable of transmitting and / or receiving signals. A base station may include one or more of each of the elements listed above. For example, a base station may include one or more TRPs. As other non-limiting examples, a base station may include, for example, one or more of a Node B (e.g., associated with Universal Mobile Telecommunications System (UMTS) and / or third generation (3G) standards), an Evolved Node B (eNB) (e.g., associated with Evolved Universal Terrestrial Radio Access (E-UTRA) and / or fourth generation (4G) standards), a remote radio head (RRH), a baseband processing unit coupled to one or more remote radio heads (RRH), a repeater or relay node used to extend the coverage area of ​​a donor node, a next generation evolved Node B (ng-eNB), a generation Node B (gNB) (e.g., associated with NR and / or fifth generation (5G) standards), an access point (AP) (e.g., associated with Wi-Fi or other suitable wireless communication standards), other generation base stations, and / or any combination thereof. A base station may include one or more devices, such as at least one base station central device (e.g., gNB central unit (gNB-CU)) and at least one base station distribution device (e.g., gNB distribution 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 the wireless devices 106. One or more base stations may include a set of antennas (e.g., a set of three or any other number of sets) for respectively controlling multiple cells or sectors (e.g., three cells, three sectors, any other number of cells, or any other number of sectors). The size of a cell may be determined by the range at which a receiver (e.g., a base station receiver) may successfully receive a transmission from a transmitter (e.g., a wireless device transmitter) operating within the cell. One or more cells of a base station (e.g., alone or in combination with other cells) may provide / configure wireless coverage to the wireless devices 106 over a wide geographic area to support wireless device mobility. A base station including three sectors (e.g., or n sectors, where n refers to any number n) may be referred to as a three-sector site (e.g., or n-sector site) or a three-sector base station (e.g., an n-sector base station).

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

[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 deployed as a heterogeneous network of base stations (e.g., different base stations having different antenna patterns). In a heterogeneous network, small cell base stations may be used to provide / configure small coverage areas, e.g., coverage areas that overlap with relatively larger coverage areas provided / configured by other base stations (e.g., macrocell base stations). Small coverage areas may be provided / configured in areas of high data traffic (or so-called "hot spots") or areas of weak macrocell coverage. Examples of small cell base stations may include, in order of decreasing coverage area, microcell base stations, picocell base stations, and femtocell or home base stations.

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

[0016] FIG. 1B illustrates an example of a communication network 150. The communication network may include a mobile communication network. The communication network 150 may include, for example, a PLMN operated / managed / run by a network operator. The communication network 150 may include a CN 152 (e.g., a 5G Core Network (5G-CN)), a RAN 154 (e.g., an NG-RAN), and / or one or more of wireless devices 156A and 156B (collectively wireless devices 156). The communication network 150 may include one or more data networks (DNs) 170, and / or devices in the communication network 150 may communicate with it (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 the wireless device 156 with one or more interfaces to one or more DNs 170, such as a public DN (e.g., the Internet), a private DN, and / or an intra-operator DN. As part of the interface function, the CN 152 (e.g., 5G-CN) may set up an end-to-end connection between the wireless device 156 and one or more DNs, authenticate the wireless device 156, and / or provide / configure charging functions. The CN 152 (e.g., 5G-CN) may be a service-based architecture that may differ from other CNs (e.g., 3GPP 4G CN, etc.). The architecture of the nodes of the CN 152 (e.g., 5G-CN) may be defined as a network function that provides services via interfaces to other network functions. The network functions of the CN 152 (e.g., 5G CN) may be implemented in several ways, for example, as network elements on dedicated or shared hardware, as software instances running on dedicated or shared hardware, and / or as virtualized functions instantiated on a platform (e.g., a cloud-based platform).

[0018] The CN 152 (e.g., 5G-CN) may include an Access and Mobility Management Function (AMF) device 158A and / or a User Plane Function (UPF) device 158B, which 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 enforcement of user plane policy rules, traffic utilization 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 triggers. The UPF device 158B may function as an anchor point for intra / inter radio access technology (RAT) mobility, an external protocol (or packet) data unit (PDU) session point interconnected to one or more DNs, and / or a branching point to support multi-homed PDU sessions. The wireless device 156 may be configured to receive services via a PDU session, which may be a logical connection between the wireless device and the DN.

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

[0020] CN 152 (e.g., 5G-CN) may include one or more additional network functions that may not be shown in Figure 1B. CN 152 (e.g., 5G-CN) may include one or more devices 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 devices 156 via wireless communication (e.g., over an air interface). The wireless devices 156 may communicate with the CN 152 via the RAN 154. The RAN 154 (e.g., NG-RAN) may include one or more first type base stations (e.g., gNBs including gNBs 160A and gNBs 160B (collectively gNBs 160)) and / or one or more second type base stations (e.g., ng-eNBs 162A and ng-eBs 162B (collectively ng eNBs 162)). The RAN 154 may include one or more of any quantity of types of base stations. The gNBs 160 and ngeNBs 162 may be referred to as base stations. The base stations (e.g., gNBs 160 and ng eNBs 162) may include one or more sets of antennas for wirelessly communicating (e.g., over an air interface) with the wireless devices 156. One or more base stations (e.g., gNB 160 and / or ng eNB 162) may include multiple antenna sets for controlling multiple cells (or sectors) respectively. The cells of the base stations (e.g., gNB 160 and ng-eNB 162) may provide wireless coverage to wireless devices 156 over a wide geographic area to support wireless device mobility.

[0022] A base station (e.g., gNB 160 and / or ng-eNBs 162) may be connected to CN 152 (e.g., 5G CN) via a first interface (e.g., NG interface) and to other base stations via a second interface (e.g., Xn interface). The NG and Xn interfaces may be established using direct physical connections and / or indirect connections over an underlying transport network, such as an Internet Protocol (IP) transport network. A base station (e.g., gNB 160 and / or ng-eNBs 162) may communicate with wireless device 156 via a third interface (e.g., Uu interface). A base station (e.g., gNB 160A) may communicate with wireless device 156A via a 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, namely, a user plane and a control plane. Any other number of planes may be used (eg, 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 connect to UPF 158B of AMF / UPF 158 via an NG user plane (NG-U) interface. The NG-U interface may provide / enforce delivery (e.g., non-guaranteed delivery) of user plane PDUs between a base station (e.g., gNB 160A) and a UPF device (e.g., UPF 158B). A base station (e.g., gNB 160A) may communicate with and / or connect to AMF devices (e.g., AMF 158A) via an NG control plane (NG-C) interface. The NG-C interface may provide / perform, for example, NG interface management, wireless device context management (e.g., UE context management), wireless device mobility management (e.g., UE mobility management), transport of NAS messages, paging, PDU session management, configuration transfer, and / or alert message transmission.

[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 on a Uu interface associated with a first protocol stack. A base station (e.g., ng-eNB 162) may provide Evolved UMTS Terrestrial Radio Access (E UTRA) user plane and control plane protocol terminations to wireless device 156 via the Uu interface (e.g., E UTRA may refer to 3GPP 4G radio access technology). A base station (e.g., ng-eNB 162B) may provide E UTRA user plane and control plane protocol terminations towards wireless device 156B via a 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). Also, it may be possible for an NR network / device (or any first network / device) to connect to a 4G core network / device (or any second network / device) in a non-standalone mode (e.g., non-standalone operation). In a non-standalone mode / operation, the 4G core network may be used to provide (or at least support) control plane functions (e.g., initial access, mobility, and / or paging). Although only one AMF / UPF 158 is shown in FIG. 1B, one or more base stations (e.g., one or more gNBs and / or one or more ng-eNBs) may be connected to multiple AMF / UPF nodes, e.g., to provide redundancy and / or load sharing across multiple AMF / UPF nodes.

[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 can use 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., within a protocol stack). The user plane may process data associated with a user (e.g., data of interest to a user). The control plane may process data associated with one or more network elements (e.g., signaling messages of interest to a network element).

[0027] The communication network 100 of FIG. 1A and / or the communication network 150 of FIG. 1BA may include any quantity / number and / or type 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). Although one or more of the above types of devices may be referenced herein (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 network, and any other network referenced herein, may include an LTE network, a 5G network, a satellite network, and / or any other network for wireless communication (e.g., any 3GPP network and / or any non-3GPP network). Although the apparatus, systems, and / or methods described herein may generally be described as being implemented in one or more devices (e.g., wireless devices, base stations, eNBs, gNBs, computing devices, etc.) in one or more networks, it will be understood that one or more features and steps may be implemented in any device and / or any network.

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

[0029] A user plane configuration (e.g., an NR user plane protocol stack) may include multiple layers (e.g., five layers or any other amount of layers) implemented in the wireless device 210 and the 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 layer (PDCP) 214, and / or a service data application protocol layer (SDAP) 215. Protocol layers above PHY 221 may include a medium access control layer (MAC) 222, a radio link control layer (RLC) 223, a packet data convergence protocol layer (PDCP) 224, and / or a service data application protocol layer (SDAP) 225. One or more of the four protocol layers above PHY 211 may correspond to Layer 2 or the Data Link layer of the OSI model. One or more of the four protocol layers above PHY 221 may correspond to Layer 2 or the Data Link layer of the OSI model.

[0030] FIG. 3 illustrates an example of protocol layers. The protocol layers may include, for example, protocol layers of a NR user plane protocol stack. One or more services may be provided between the protocol layers. The SDAP (e.g., SDAPS 215 and 225 shown in FIG. 2A and FIG. 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 / through a PDU session, which may be a logical connection between a wireless device and a 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, for example, based on one or more QoS requirements (e.g., with respect to delay, data rate, error rate, and / or any other quality / service requirement). The SDAP 215 and 225 may perform mapping / de-mapping 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. For reflected mapping, the SDAP 225 of the base station 220 may mark downlink packets with a QoS flow indicator (QFI) that may be monitored / detected / identified / indicated / observed by the SDAP 215 of the wireless device 210 to determine the mapping / demapping between one or more QoS flows 310 and radio bearers 320.

[0031] PDCPs (e.g., PDCPs 214 and 224 shown in FIG. 2A and FIG. 3) may perform, for example, header compression / decompression to reduce the amount of data that may need to be transmitted over the air interface, encryption / decryption to prevent unauthorized decoding of data transmitted over the air interface, and / or integrity protection (e.g., to ensure that control messages originate from the intended source). PDCPs 214 and 224 may perform retransmission of undelivered packets, sequential delivery and reordering of packets, and / or removal of duplicately received packets, for example, for handover (e.g., intra-gNB handover). PDCPs 214 and 224 may perform packet duplication, for example, to improve the likelihood of a packet being received. A receiver may receive packets duplicately and may remove any 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 map / undemap between split radio bearers and RLC channels (e.g., RLC channel 330) (e.g., in a dual connectivity scenario / configuration). Dual connectivity may refer to a technology that allows a wireless device to communicate with multiple cells (e.g., two cells), or more broadly, multiple cell groups including a master cell group (MCG) and a secondary cell group (SCG). A split bearer may be configured and / or used, for example, when a single radio bearer (e.g., one of the radio bearers provided / configured by PDCP 214 and 224 as a service to SDAP 215 and 225) is handled by a cell group in dual connectivity. The PDCP 214 and 224 may map / undemap between the split radio bearer and the RLC channel 330 belonging to the cell group.

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

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

[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 an air interface). The digital and / or analog signal processing functions may include, for example, encoding / decoding and / or modulation / demodulation. The PHY layer (e.g., PHYs 211 and 221) may perform multi-antenna mapping. The PHY layer (e.g., PHYs 211 and 221) may provide / configure one or more transport channels (e.g., transport channel 350) as a service to the MAC layer (e.g., MACs 212 and 222, respectively).

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

[0037] A downlink data flow may be initiated, for example, when the SDAP 225 receives three IP packets (or other quantity of IP packets) from one or more QoS flows and maps the three packets (or other quantity of packets) to a radio bearer (e.g., radio bearers 402 and 404). The SDAP 225 may map IP packets n and n+1 to the first radio bearer 402 and map IP packet m to the second radio bearer 404. An SDAP header (labeled with an "H" before each SDAP SDU shown in FIG. 4A) may be added to the IP packets to generate an SDAP PDU, which may be referred to as a PDCPSDU. Data units transferred to and from a higher protocol layer may be referred to as service data units (SDUs) of the lower protocol layer, and data units transferred to and from a lower protocol layer 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., a protocol layer as shown in FIG. 4A), or at least some of the protocol layers, may perform its own function (e.g., one or more functions of each protocol layer described with respect to FIG. 3), add a corresponding header, and / or forward its respective output to the next lower layer (e.g., its respective lower layer). PDCP 224 may perform IP header compression and / or encryption. PDCP 224 may forward its output (e.g., a PDCP PDU, which is an RLC SDU) to RLC 223. RLC 223 may optionally perform segmentation (e.g., as shown for an IP packet in FIG. 4A). RLC 223 may forward its output (e.g., two RLC PDUs, which are two MAC SDUs, generated by adding respective subheaders to two SDU Segments (SDU Segs)) to MAC 222. MAC 222 may multiplex several RLC PDUs (MAC SDUs). MAC 222 may attach MAC subheaders to the RLC PDUs (MAC SDUs) and form a TB. The MAC subheader may be distributed across the MAC PDU (e.g., in an NR configuration, as shown in FIG. 4A). The MAC subheader may be located entirely at the beginning of the MAC PDU (e.g., in an LTE configuration). The NR MAC PDU structure may reduce processing time and / or associated delays, for example, if the MAC PDU subheaders are calculated before assembling the complete MAC PDU.

[0039] 4B illustrates 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., bytes) of the MAC SDU to which the MAC subheader corresponds, a logical channel identifier (LCD) field to identify / indicate the logical channel on which the MAC SDU is initiated to assist in the demultiplexing process, a flag (F) to indicate the size of the SDU length field, and a reserved bit for future use (R) field.

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

[0041] FIG. 5A illustrates an example mapping of downlink channels. The mapping of uplink channels may include mapping between downlink channels (e.g., logical channels, transport channels, and physical channels). FIG. 5B illustrates an example mapping of uplink channels. The mapping of uplink channels may include mapping between uplink channels (e.g., logical channels, transport channels, and physical channels). Information may be passed through channels between the RLC, MAC, and PHY layers of a protocol stack (e.g., the NR protocol stack). Logical channels may be used between the RLC and MAC layers. Logical channels may be classified / denoted as control channels that can carry control and / or configuration information (e.g., in the NR control plane) or as traffic channels that can carry data (e.g., in the NR user plane). Logical channels may be classified / denoted as dedicated logical channels that may be dedicated to a 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. The set of logical channels (e.g., in an NR configuration) may include one or more channels described below: A paging control channel (PCCH) may include / carry one or more paging messages used for paging wireless devices whose locations are not known to the network at the cell level. A broadcast control channel (BCCH) may include / carry system information messages in the form of a master information block (MIB) and several system information blocks (SIBs). System information messages may be used by wireless devices to obtain information about how the cell is configured and how to operate within the cell. A common control channel (CCCH) may include / carry control messages along with random access. A dedicated control channel (DCCH) may include / carry control messages to / from a specific wireless device and may configure the wireless device with configuration information. A dedicated traffic channel (DTCH) may include / carry user data to / from a specific wireless device.

[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, e.g., by the NR configuration or any other configuration) may include one or more of the following channels: Paging Channel (PCH) may include / carry paging messages originated from PCCH; Broadcast Channel (BCH) may include / carry MIBs from BCCH; Downlink Shared Channel (DL-SCH) may include / carry downlink data and signaling messages, including SIBs from BCCH; Uplink Shared Channel (UL-SCH) may include / carry uplink data and signaling messages; Random Access Channel (RACH) may provide wireless devices with access to the network without prior scheduling.

[0044] The PHY layer may pass / transfer information between processing levels of the PHY layer using physical channels. A physical channel may have an associated set of time-frequency resources for carrying information of one or more transport channels. The PHY layer may generate control information to support 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, e.g., by the NR configuration or any other configuration) may include one or more of the following channels: The physical broadcast channel (PBCH) may include / carry the MIB from the BCH. The physical downlink shared channel (PDSCH) may include / carry downlink data and signaling messages from the DL-SCH and paging messages from the PCH. The physical downlink control channel (PDCCH) may include / carry downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling grants, and uplink power control commands. The Physical Uplink Shared Channel (PUSCH) may include / carry uplink data and signaling messages from the UL-SCH, as well as uplink control information (UCI) in some embodiments, as described below. The Physical Uplink Control Channel (PUCCH) may include / carry UCI, which may include HARQ acknowledgements, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and scheduling requests (SR). The Physical Random Access Channel (PRACH) may be used for random access.

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

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

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

[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 broadly, between the wireless device 210 and the RAN (e.g., the base station 220). The RRC layers 216 and 226 may provide / configure control plane functionality between the wireless device 210 and the base station 220 via signaling messages, which may be referred to as RRC messages. The RRC messages may be transmitted / 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 the control plane and user plane data into the same TB. The RRC layers 216 and 226 may provide / configure control plane functions such as one or more of the following: broadcast of system information related to the AS and the NAS, paging initiated by the CN or the RAN, establishment, maintenance, and release of an RRC connection between the wireless device 210 and the RAN (e.g., base station 220), security functions including key management, establishment, configuration, maintenance, and release of signaling and data radio bearers, mobility functions, QoS management functions, wireless device measurement reports (e.g., wireless device measurement reports) and control of reports, detection and recovery from radio link failure (RLF), and / or NAS message forwarding functions. As part of establishing an RRC connection, the RRC layers 216 and 226 may establish an RRC context, which may involve configuration of parameters for communications between the wireless device 210 and the RAN (e.g., base station 220).

[0049] FIG. 6 illustrates an example of 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 identical to or similar to the wireless device 106, 210, or any other wireless device. The wireless device may be in at least one of a number of states, such as three RRC states including RRC connected 602 (e.g., RRC_CONNECTED), RRC idle 606 (e.g., RRC_IDLE), and RRC inactive 604 (e.g., RRC_INACTIVE). The RRC inactive 604 may be RRC connected but inactive.

[0050] An RRC connection may be established for the wireless device. For example, this may be during an RRC connected state. During an RRC connected state (e.g., during RRC connected 602), the wireless device may have an established RRC context and may have at least one RRC connection with a base station. The base station may resemble one of one or more base stations (e.g., one or more base stations of the RAN 104 shown in FIG. 1A, one of the gNB 160 or ng-eNB 162 shown in FIG. 1B, the base station 220 shown in FIGS. 2A and 2B, or 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 the following: The RRC connected state (e.g., RRC connected 602) may include the following information: AS context, radio link configuration parameters, bearer configuration information (e.g., related to 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 NGRAN 154). The wireless device may measure received signal levels (e.g., reference signal level, reference signal received power, reference signal received quality, received signal strength indicator, etc.) based on one or more signals transmitted from the serving cell and neighboring cells. The wireless device may report these measurements to a serving base station (e.g., a base station currently serving the wireless device). The serving base station of the wireless device may request a handover to a cell of one of the neighboring base stations, for example, based on the reported measurements. The RRC state may transition from an RRC connected state (eg, RRC connected 602) to an RRC idle state (eg, RRC idle 606) via a connection release procedure 608.The RRC state may transition from an RRC connected state (eg, RRC connected 602) to an RRC inactive state (eg, RRC inactive 604) via a connection deactivation procedure 610.

[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 (e.g., to save battery power) most of the time. The wireless device may wake up periodically (e.g., every discontinuous reception (DRX) cycle) to monitor for paging messages (e.g., paging messages configured from the RAN). Mobility of the wireless device may be managed by the wireless device via a cell reselection procedure. The RRC state may transition from an RRC idle state (e.g., RRC idle 606) to an RRC connected state (e.g., RRC connected 602) via a connection establishment procedure 612, which may involve a random access procedure.

[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. The maintenance of the RRC context may enable / allow a fast transition to an RRC connected state (e.g., RRC connected 602) with less signaling overhead compared to a transition from an RRC idle state (e.g., RRC idle 606) to an RRC connected state (e.g., RRC connected 602). During an RRC inactive state (e.g., RRC inactive 604), the wireless device is in a sleep state and the mobility of the wireless device may be managed / controlled by the wireless device via cell reselection. The RRC state may transition from an RRC inactive state (e.g., RRC inactive 604) to an RRC connected state (e.g., RRC connected 602) via a connection resumption procedure 614. The RRC state may transition from an RRC inactive state (eg, RRC inactive 604) to an RRC idle state (eg, RRC idle 606) via a connection release procedure 616 that is the same as or similar to the connection release procedure 608.

[0053] The RRC states may be associated with mobility management mechanisms. During the RRC idle state (e.g., RRC idle 606) and the 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 the RRC idle state (e.g., RRC idle 606) or the 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 the need to broadcast the paging message throughout the entire mobile communication network. The mobility management mechanism used during the RRC idle state (e.g., RRC idle 606) or the RRC idle state (e.g., RRC inactive 604) may enable / allow the network to track the wireless device at a cell group level, for example, so that a paging message may be broadcast over the cells of the cell group in which the wireless device is currently in (e.g., instead of transmitting the paging message throughout the entire mobile communication network). The mobility management mechanism in the RRC idle state (e.g., RRC idle 606) and the RRC inactive state (e.g., RRC inactive 604) may track wireless devices at a cell group level. The mobility management mechanism may perform tracking using, for example, different granularity of grouping. There may be multiple levels of cell grouping granularity (e.g., three levels of cell grouping granularity: individual cells, cells in a RAN area identified by a RAN Area Identifier (RAI), and cells in a group of RAN areas called 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 the 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, e.g., provide the wireless device with a new UE registration area if the wireless device moves (e.g., via cell reselection) to a cell associated with a TAI that is not included in the list of TAIs associated with the UE registration area.

[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 / provisioned / configured in a RAN notification area. The RAN notification area may include one or more cell identities (e.g., a list of RAIs and / or a list of TAIs). A base station may belong to one or more RAN notification areas. A cell may belong to one or more RAN notification areas. If the wireless device moves (e.g., via cell reselection) to a cell that is not included in the RAN notification area assigned / provisioned / configured to the wireless device, the notification area may be updated in the RAN to update the RAN notification area of ​​the wireless device.

[0056] A base station that stores an RRC context for a wireless device or a final serving base station for a wireless device may be referred to as an anchor base station. The anchor base station may maintain the RRC context for the wireless device 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., a base station distributed unit 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] The physical signals and physical channels (e.g., FIG. 5A and FIG. 5B) may be mapped onto one or more symbols (e.g., orthogonal frequency division multiplexing (OFDM) symbols in a NR configuration, or any other symbols). OFDM is a multicarrier communication scheme that transmits / transmits data over F orthogonal subcarriers (or tones). The data may be mapped onto a series of complex symbols (e.g., M-quadrature amplitude modulation (M-QAM) symbols or M-phase shift keying (M PSK) symbols or any other modulation symbols), which are called source symbols and are, for example, divided into F parallel symbol streams before the transmission of the data. 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 transforms them into 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 the F sinusoidal basis functions corresponding to the F orthogonal subcarriers. The output of the IFFT block may be F time domain samples representing a sum of the F orthogonal subcarriers. The F time domain samples may form a single OFDM symbol. The OFDM symbol provided / output by the IFFT block may be transmitted / transmitted over the air interface at a carrier frequency, for example, after one or more processes (e.g., adding a cyclic prefix) and upconversion. The F parallel symbol streams may be mixed, for example, using a Fast Fourier Transform (FFT) block before being processed by the IFFT block. This operation may generate a Discrete Fourier Transform (DFT) pre-coded OFDM symbol, which may be used by one or more wireless devices in the uplink to reduce the peak-to-average power ratio (PAPR). Inverse processing may be performed on the OFDM symbol at the receiver using the FFT block to recover the data mapped to the source symbol.

[0059] FIG. 7 illustrates an example configuration of a frame. The frame may include, for example, an NR radio frame in which OFDM symbols may be grouped. The frame (e.g., NR radio frame) may be identified / indicated by a system frame number (SFN) or any other value. The SFN may repeat for a period of 1024 frames. One NR frame may be 10 milliseconds (ms) in duration and may include 10 subframes that are 1 ms in duration. The 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 quantity of symbols, slots, or duration may be used for 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 different deployments (e.g., from cells with carrier frequencies below 1 GHz to cells with carrier frequencies in the mm-wave range). For example, flexible numerology may be supported in an NR configuration or any other radio configuration. The numerology may be defined in terms of subcarrier spacing and / or cyclic prefix duration. The subcarrier spacing may be scaled up by a power of 2 from a baseline subcarrier spacing of 15 kHz. The cyclic prefix duration may be scaled down by a power of 2 from a baseline cyclic prefix duration of 4.7 microseconds, for example, for numerology in an NR configuration or any other radio configuration. Numerologies may be defined for the following subcarrier spacing / cyclic prefix duration combinations: 15 kHz / 4.7 microseconds, 30 kHz / 2.3 microseconds, 60 kHz / 1.2 microseconds, 120 kHz / 0.59 microseconds, 240 kHz / 0.29 microseconds, and / or any other subcarrier spacing / cyclic prefix duration combination.

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

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

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

[0064] The configuration of one or more bandwidth portions (BWPs) may support one or more wireless devices that cannot receive the full carrier bandwidth. The BWPs may support, for example, bandwidth adaptation for such wireless devices that cannot receive the full carrier bandwidth. A BWP (e.g., a BWP for an NR configuration) may be defined by a subset of contiguous RBs on a carrier. A wireless device may be configured (e.g., via the RRC layer) with one or more downlink BWPs per serving cell and one or more uplink BWPs per serving cell (e.g., up to four downlink BWPs per serving cell and up to four uplink BWPs per serving cell). One or more of the BWPs configured for a serving cell may be active, for example, at a given time. The one or more BWPs may be referred to as 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., for an 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 a downlink BWP to be the same as the center frequency of an uplink BWP (e.g., for an 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. A base station may configure a wireless device with one or more CORESETs for a downlink BWP, for example, for a set of downlink BWPs configured on a primary cell (PCell) or a secondary cell (SCell). A search space may include a set of locations in the time and frequency domain where a wireless device may monitor / detect / detect / identify control information. A search space may be a wireless device-specific search space (e.g., a UE-specific search space) or a common search space (e.g., potentially usable by a group of multiple wireless devices or wireless user equipments). A base station may configure a group of wireless devices with a common search space on a PCell or a primary secondary cell (PSCell) for an active downlink BWP.

[0067] A base station may configure a wireless device with one or more resource sets for one or more PUCCH transmissions, for an uplink BWP within a set of configured uplink BWPs. The wireless device may receive a downlink reception (e.g., a PDCCH or PDSCH) in a downlink BWP, for example, according to a configured numerology (e.g., a configured subcarrier spacing and / or a configured cyclic prefix duration) for the downlink BWP. The wireless device may transmit / transmit an uplink transmission (e.g., a PUCCH or PUSCH) in an uplink BWP, for example, according to a configured numerology (e.g., a configured subcarrier spacing and / or a 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 of a set of configured BWPs is an active downlink BWP for one or more downlink receptions. The value of the one or more BWP indicator field may indicate an active uplink BWP for one or more uplink transmissions.

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

[0070] A base station may configure a wireless device with a BWP inactivity timer value for a PCell. A wireless device may start or restart a BWP inactivity timer at any appropriate time. A wireless device may start or restart a BWP inactivity timer, for example, if one or more conditions are met. The one or more conditions may include at least one of: a wireless device detects a DCI indicating an active downlink BWP other than a default downlink BWP for paired spectrum operation, a wireless device detects a DCI indicating an active downlink BWP other than a default downlink BWP for unpaired spectrum operation, and / or a wireless device detects a DCI indicating an active uplink BWP other than a default uplink BWP for unpaired spectrum operation. A wireless device may start / run a BWP inactivity timer towards expiration (e.g., incrementing from zero to the BWP inactivity timer value or decrementing from the BWP inactivity timer value to zero), for example, if the wireless device does not detect a DCI during a time interval (e.g., 1 ms or 0.5 ms). A 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, based on (e.g., thereafter or in response to) receiving a DCI indicating the second BWP as the active BWP. The wireless device can switch the active BWP from a first BWP to a second BWP, for example, based on (e.g., thereafter or in response to) expiration of a BWP inactivity timer (e.g., if the second BWP is a default BWP).

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

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

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

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

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

[0077] The network may set a maximum number of CCs that can be aggregated (e.g., up to 32 CCs may be aggregated in NR, or any other number may be aggregated in other systems). 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., for FDD). The ability to aggregate more downlink carriers than uplink carriers may be useful, for example, when a wireless device has more data traffic in the downlink than the uplink.

[0078] One of the aggregation cells for the wireless device may be referred to as a primary cell (PCell), for example, when CA is configured. The PCell may be a serving cell to which the radio initially connects or accesses, for example, during or to 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. The wireless device may have different PCells. For the downlink, the carrier corresponding to the PCell may be referred to as a downlink primary cell CC (DL PCC). For the uplink, the carrier corresponding to the PCell may be referred to as an uplink primary cell CC (UL PCC). Other aggregation cells for the wireless device (e.g., associated with CCs other than DL PCC and UL PCC) may be referred to as secondary cells (SCells). The SCells may be configured, for example, after the PCell is configured for the wireless device. The SCells may be configured via an RRC connection reconfiguration procedure. For the downlink, the carrier corresponding to the SCell may be referred to as a downlink secondary CC (DL SCC). For the uplink, the carrier corresponding to the SCell may be referred to as an Uplink Secondary CC (UL SCC).

[0079] A SCell configured for a wireless device may be activated or deactivated, for example, based on 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 to the wireless device which SCells (e.g., within a subset of configured SCells) are activated or deactivated using a bitmap (e.g., one bit per SCell). A configured SCell may be deactivated, for example, based on (e.g., after or in response to) expiration of a SCell deactivation timer (e.g., one SCell deactivation timer per SCell may be configured).

[0080] The 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. The uplink control information (UCI) may include control information such as HARQ acknowledgement and channel state feedback (e.g., CQI, PMI, and / or RI) for the aggregation cell. The UCI may be transmitted / transmitted via an uplink control channel (e.g., PUCCH) of the PCell or a particular SCell (e.g., a SCell that is composed of PUCCH). A large number of aggregated downlink CCs may overload the PUCCH of the PCell. A cell may be divided into multiple PUCCH groups.

[0081] FIG. 10B illustrates an example group of cells. The aggregation cells may be configured into one or more PUCCH groups (e.g., as shown in FIG. 10B). One or more cell groups or one or more uplink control channel groups (e.g., PUCCH group 1010 and PUCCH group 1050) may each include one or more downlink CCs. The PUCCH group 1010 may include one or more downlink CCs, e.g., three downlink CCs, i.e., PCell 1011 (e.g., DL PCC), SCell 1012 (e.g., DL SCC), and SCell 1013 (e.g., DL SCC). The PUCCH group 1050 may include one or more downlink CCs, e.g., three downlink CCs, i.e., PUCCH SCell (or PSCell) 1051 (e.g., DL SCC), SCell 1052 (e.g., DL SCC), and SCell 1053 (e.g., DL SCC). One or more uplink CCs of the PUCCH group 1010 may be configured as a PCell 1021 (e.g., a UL PCC), a SCell 1022 (e.g., a UL SCC), and a 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), a SCell 1062 (e.g., a UL SCC), and a 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 downlink CCs of the PUCCH group 1050, denoted as UCI 1071, UCI 1072, and UCI 1073, may be transmitted / transmitted via the uplink of a 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 associated with six downlink CCs, for example, if the aggregation cells shown in FIG. 10B are not divided into PUCCH group 1010 and PUCCH group 1050. PCell 1021 may be overloaded, for example, if 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 include a downlink carrier (e.g., PCell 1011) and an uplink carrier (e.g., PCell 1021). A 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. A physical cell ID or a cell index may indicate / identify a downlink carrier and / or an uplink carrier of a cell, for example, depending on the context in which the physical cell ID is used. A physical cell ID may be determined, for example, using a synchronization signal (e.g., PSS and / or SSS) transmitted / transmitted via a downlink component carrier. A cell index may be determined, for example, using one or more RRC messages. A physical cell ID may be referred to as a carrier ID, and a cell index may be referred to as a carrier index. A first physical cell ID for a first downlink carrier may refer to a first physical cell ID for a cell including the first downlink carrier. Substantially the same / similar concept may be applied, for example, to carrier activation. Activation of a first carrier may refer to activation of a cell including the first carrier.

[0083] The multi-carrier nature of the PHY layer may be exposed / indicated to the MAC layer (e.g., in a CA configuration). A HARQ entity may operate on the serving cell. Transport blocks may be generated per assignment / grant per serving cell. Transport blocks and potential HARQ retransmissions of transport blocks 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 RS to a base station (e.g., DM-RS, PT-RS, and / or SRS). The PSS and SSS may be transmitted / transmitted by a base station and may be used by one or more wireless devices to synchronize one or more wireless devices with a base station. A synchronization signal (SS) / physical broadcast channel (PBCH) block may include a PSS, SSS, and PBCH. A base station may periodically transmit / transmit a burst of SS / PBCH blocks, which may be referred to as an SSB.

[0085] FIG. 11A illustrates an example mapping of one or more SS / PBCH blocks. A burst of SS / PBCH blocks may include one or more SS / PBCH blocks (e.g., four SS / PBCH blocks as shown in FIG. 11A). A burst may be transmitted / transmitted periodically (e.g., every two frames, every 20 ms, or any other duration). A burst may be limited to a half frame (e.g., the first half frame having a duration of 5 ms). 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, for example, based on at least one of the carrier frequency of the cell in which the SS / PBCH block is transmitted / transmitted, the numerology or subcarrier spacing of the cell, configuration by the network (e.g., using RRC signaling), and / or any other suitable factor. The wireless device may assume a subcarrier spacing for the SS / PBCH block based on the monitored carrier frequency, unless, for example, the wireless network configures the wireless device to assume a different subcarrier spacing.

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

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

[0088] The SS / PBCH block may be used by the 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 transmitted / transmitted according to a transmission pattern. The SS / PBCH block in the transmission pattern may be a known distance from a 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 include or 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 include a MIB used to transmit / transmit one or more parameters to the wireless device. The MIB may be used by the wireless device to find the remaining minimum system information (RSSI) associated with the cell. The RMSI may include a system information block type 1 (SIB1). The SIB1 may include information for the wireless device to access the cell. The wireless device may use one or more parameters of the MIB to monitor the PDCCH, which may be used to schedule the PDSCH. The PDSCH may include SIB1. The SIB1 may be decoded using parameters provided / included in the MIB. The PBCH may indicate that SIB1 is not present. For example, the wireless device may point to a frequency based on the PBCH indicating that SIB1 is not present. The wireless device may search for an SS / PBCH block at the frequency to which the wireless device is pointed.

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

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

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

[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 domain. A base station may selectively activate and / or deactivate CSI-RS resources. A base station may indicate to a 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. A base station may configure a wireless device to provide CSI reports periodically, aperiodically, or semi-permanently. For periodic CSI reporting, a wireless device may be configured with the timing and / or periodicity of CSI reports. For aperiodic CSI reporting, a base station may request a CSI report. A base station may instruct a wireless device to measure configured CSI-RS resources and provide a CSI report related to the measurements. For semi-persistent CSI reporting, a base station may configure a wireless device to transmit / transmit periodically and selectively activate or deactivate periodic reporting (e.g., via one or more activate / deactivate MAC CEs and / or one or more DCIs). A base station may configure a wireless device with a CSI-RS resource set and a CSI report, e.g., using RRC signaling.

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

[0096] The downlink DM-RS may be transmitted / transmitted by a base station and received / used by a wireless device for channel estimation. The downlink DM-RS may be used for coherent demodulation of one or more downlink physical channels (e.g., PDSCH). A network (e.g., an NR network) may support one or more variable and / or configurable DM-RS patterns for data demodulation. At least one downlink DM-RS configuration may support a frontloaded DM-RS pattern. The frontloaded DM-RS may be mapped onto one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). A base station may semi-statically configure a wireless device with the number / quantity (e.g., maximum number / quantity) of frontloaded DM-RS symbols of the PDSCH. The DM-RS configuration may support one or more DM-RS ports. The DM-RS configuration may support up to eight orthogonal downlink DM-RS ports per wireless device (e.g., for single user MIMO). The DM-RS configuration may support up to four orthogonal downlink DM-RS ports per wireless device (e.g., for multi-user-MIMO). The wireless network may support a common DM-RS structure for the downlink and uplink (e.g., at least for CP-OFDM). The DM-RS position, DM-RS pattern, and / or scrambling sequence may be identical or different. A base station may transmit / transmit a downlink DM-RS and a corresponding PDSCH, for example, using the same precoding matrix. A wireless device may use one or more downlink DM-RS 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 and second precoder matrices may be different based, for example, on the first bandwidth being different from the second bandwidth. A wireless device may assume that the same precoding matrix is ​​used across a set of PRBs. The set of PRBs may be determined / indicated / identified / indicated as a precoding resource block group (PRG).

[0098] The PDSCH may include one or more layers. A wireless device may assume that at least one symbol with a DM-RS is present on one or more layers of the PDSCH. Higher layers may configure one or more DM-RSs for the PDSCH (e.g., up to three DMRSs for the PDSCH). A downlink PT-RS may be transmitted / transmitted by a base station and may be used by a wireless device, for example, for phase noise compensation. Whether a downlink PT-RS is present may depend on an RRC configuration. The presence and / or pattern of the downlink PT-RS is configured based on wireless device specific criteria, for example, using a combination of RRC signaling and / or association with one or more parameters used / employed for other purposes (e.g., modulation and coding scheme (MCS)), which may be indicated by a DCI. The dynamic presence of the downlink PT-RS, if configured, may be associated with one or more DCI parameters including at least the MCS. A network (e.g., an NR network) may support multiple PT-RS densities defined in the time and / or frequency domain. The frequency domain density (configuration / if present) may be associated with at least one configuration of the scheduled bandwidth. The wireless device may assume the same precoding for the DM-RS and PT-RS ports. The quantity / number of PT-RS ports may be less than the quantity / number of DM-RS ports in the scheduled resources. The downlink PT-RS may be configured / assigned / restricted with a scheduled time / frequency duration for the wireless device. The downlink PT-RS may be transmitted / transmitted over 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, e.g., for channel estimation. A base station may use the uplink DM-RS for coherent demodulation of one or more uplink physical channels. A wireless device may transmit / transmit an uplink DM-RS on a PUSCH and / or a PUCCH. An uplink DM-RS may span a range of frequencies similar to the range of frequencies associated with a corresponding physical channel. A base station may configure a wireless device with one or more uplink DM-RS configurations. At least one DM-RS configuration may support a frontloaded DM-RS pattern. The frontloaded DM-RS may be mapped onto one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DM-RS may be configured to transmit / transmit on one or more symbols of a PUSCH and / or a PUCCH. A base station may semi-statically configure a wireless device with the number / amount (e.g., maximum number / amount) of frontloaded DM-RS symbols for PUSCH and / or PUCCH that the wireless device may use to schedule single symbol DM-RS and / or double symbol DM-RS. A network (e.g., an NR network) may support a common DM-RS structure for the downlink and uplink (e.g., for cyclic prefix orthogonal frequency division multiplexing (CP-OFDM)). The DM-RS positions, DM-RS patterns, and / or scrambling sequences of the DM-RS may be substantially identical or different.

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

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

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

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

[0104] FIG. 11B illustrates an example of mapping one or more CSI-RS. The CSI-RS may be mapped in the time domain and the frequency domain. Each rectangular block illustrated in FIG. 11B may correspond to a resource block (RB) in the bandwidth of a cell. A base station may transmit one or more RRC messages including CSI-RS resource configuration parameters indicating one or more CSI-RS. The one or more parameters may be configured by higher layer signaling (e.g., RRC and / or MAC signaling) for CSI-RS resource configuration. The one or more 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., symbols and resource element (RE) locations within a subframe), a CSI-RS subframe configuration (e.g., subframe location, offset, and radio frame periodicity), a CSI-RS power parameter, a CSI-RS sequence parameter, a code division multiplexing (CDM) type parameter, frequency density, transmit comb, quasi-collocation (QCL) parameters (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. Three beams are shown in FIG. 11B (Beam #1, Beam #2, and Beam #3), but more or less beams may be configured. Beam #1 may be assigned with CSI-RS 1101, which may be transmitted / transmitted in one or more subcarriers of the RB of the first symbol. Beam #2 may be assigned with CSI-RS 1102, which may be transmitted / transmitted in one or more subcarriers of the RB of the second symbol. Beam #3 may be assigned with CSI-RS 1103, which may be transmitted / transmitted in one or more subcarriers in the RB of the third symbol. A base station may use other subcarriers in the same RB (e.g., not used to transmit / transmit CSI-RS 1101) to transmit another CSI-RS associated with a beam for another wireless device, e.g., by using Frequency Division Multiplexing (FDM). A beam used for a wireless device may be configured such that the beam for the wireless device uses different symbols than the symbols used by the beams of the other wireless devices, e.g., by using Time Domain Multiplexing (TDM). A wireless device may be transmitted with beams of orthogonal symbols (eg, no overlapping symbols) by using, for example, TDM.

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

[0107] A wireless device may determine / assess (e.g., measure) channel quality of one or more beam pair links, for example, in a beam management procedure. The beam pair link may include a Tx beam of the base station and an Rx beam of the wireless device. The Tx beam of the base station may transmit / transmit downlink signals, and the Rx beam of the wireless device may receive downlink signals. The wireless device may transmit / 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 identities (e.g., beam index, reference signal index, or similar), RSRP, precoding matrix indicator (PMI), channel quality indicator (CQI), and / or rank indicator (RI).

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

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

[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 transmit / transmit a BFR request (e.g., a preamble, UCI, SR, MAC CE, and / or the like), for example, based on initiating a BFR procedure. A wireless device may detect a beam failure, for example, based on determining that the quality of a beam pair link of an associated control channel is insufficient (e.g., having an error rate higher than an error rate threshold, a received signal power lower than a received signal power threshold, a timer expiring, and / or the like).

[0111] A wireless device may measure the quality of a beam pair link using one or more reference signals (RSs) including, for example, one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more DM-RSs. The quality of the beam pair link may be based on one or more of a block error rate (BLER), an RSRP value, a signal-to-interference plus noise ratio (SINR) value, an RSRQ value, and / or a CSI value measured on the RS resource. A base station may indicate that an RS resource is QCLed with one or more DM-RSs of a channel (e.g., a control channel, a shared data channel, and / or the like). An RS resource and one or more DM-RSs of a channel may be QCLed, for example, if the channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameters, fade, and / or the like) transmitted to the wireless device via the RS resource are similar or identical to the channel characteristics transmitted to the wireless device via the channel.

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

[0113] FIG. 13A illustrates an example of a four-step random access procedure. The four-step random access procedure may include a four-step contention-based random access procedure. A base station may transmit / transmit a configuration message 1310 to a wireless device, for example, before initiating a random access procedure. The four-step random access procedure may include transmitting four messages, including a first message (e.g., Msg 1 1311), a second message (e.g., Msg 2 1312), a third message (e.g., Msg 3 1313), and a fourth message (e.g., Msg 4 1314). The first message (e.g., Msg 1 1311) may include a preamble (or random access preamble). The first message (e.g., Msg 1 1311) may be referred to as a preamble. The second message (e.g., Msg 2 1312) may be included as a random access response (RAR). The second message (eg, Msg 2 1312) may be called a RAR.

[0114] The configuration message 1310 may be transmitted / 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 include at least one of general parameters (e.g., RACH-configGeneral), cell-specific parameters (e.g., RACH-ConfigCommon), and / or dedicated parameters (e.g., RACH-configDedicated) of one or more random access procedures. A base station may transmit / transmit (e.g., broadcast or multicast) one or more RRC messages to one or more wireless devices. The one or more RRC messages may be wireless device specific. The wireless device specific one or more RRC messages may be, for example, dedicated RRC messages transmitted / transmitted to wireless devices in an RRC connected (e.g., RRC_CONNECTED) state and / or an RRC inactive (e.g., RRC_INACTIVE) state. The wireless device may determine time frequency resources and / or uplink transmit power for transmitting the first message (e.g., Msg 1 1311) and / or the third message (e.g., Msg 3 1313) 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, the 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 a quantity / number of SS / PBCH blocks mapped to the PRACH opportunities and / or a quantity / number 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 of the preamble transmission). There may be one or more power offsets indicated by the one or more RACH parameters. The one or more RACH parameters may indicate a power ramping step, a power offset between SSB and CSI-RS, a power offset between the transmission of the first message (e.g., Msg 1 1311) and the third message (e.g., Msg 3 1313), and / or a power offset value between the preamble groups. The one or more RACH parameters may indicate one or more thresholds based on which the wireless device may determine at least one reference signal (e.g., SSB and / or CSI-RS) and / or uplink carrier (e.g., a normal uplink (NUL) carrier and / or a complementary uplink (SUL) carrier), for example.

[0117] The first message (e.g., Msg 1 1311) may include one or more preamble transmissions (e.g., a preamble transmission and one or more preamble retransmissions). The RRC message may be used to configure one or more preamble groups (e.g., Group A and / or Group B). The 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 the one or more reference signals and / or at least one preamble associated with 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 quantity / number of preamble transmissions, and / or one or more thresholds for determining one or more preamble groups (e.g., Group A and Group B). The base station may configure the wireless device with an association between one or more preambles and one or more reference signals (e.g., SSB and / or CSI-RS) using the one or more RACH parameters. The wireless device may determine the preamble to be included in the first message (e.g., 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-OccasionList) 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., after or in response to) a preamble transmission (e.g., a monitoring window for monitoring the RAR). The wireless device may increase an uplink transmit power for the preamble retransmission. The wireless device may select an initial preamble transmit power, for example, based on a path loss measurement and / or a target received preamble power configured by the network. The wireless device may decide to retransmit / retransmit the preamble and may ramp up the uplink transmit power. The wireless device may receive one or more RACH parameters (e.g., PREAMBLE_POWER_RAMPING_STEP) indicating a ramping step for the preamble retransmission. The ramping step may be the amount of incremental increase in the uplink transmit power for the retransmission. The wireless device may increase the uplink transmit power, for example, if the wireless device determines the same reference signal (e.g., SSB and / or CSI-RS) as the previous preamble transmission. The wireless device may, for example, count the quantity / number 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 was not successful if, for example, the quantity / number of preamble transmissions exceeds a threshold configured by one or more RACH parameters (e.g., preambleTransMax) without receiving a successful response (e.g., RAR).

[0120] The second message (e.g., Msg 2 1312) (e.g., received by a wireless device) may include an RAR. The second message (e.g., Msg 2 1312) may include multiple RARs corresponding to multiple wireless devices. The second message (e.g., Msg 2 1312) may be received, for example, based on (e.g., subsequently in response to) the transmission / transmission of the first message (e.g., Msg 1 1311). The second message (e.g., Msg 2 1312) may be scheduled on the DL-SCH and may be indicated by the PDCCH, for example, using a random access radio network temporary identifier (RA RNTI). The second message (e.g., Msg 2 1312) may indicate that the first message (e.g., Msg 1 1311) has been received by the base station. The second message (e.g., Msg 2 1312) may include a time alignment command that may be used by the wireless device to adjust the transmission timing of the wireless device, a scheduling grant for the transmission of the third message (e.g., Msg 3 1313), and / or a temporary cell RNTI (TC-RNTI). The wireless device may, for example, determine / start a time window (e.g., ra-Response window) during which it monitors the PDCCH for the second message (e.g., Msg 2 1312) after transmitting / transmitting the first message (e.g., Msg 1 1311) (e.g., preamble). The wireless device may determine the start time of the time window based on, for example, the PRACH opportunity that the wireless device uses to transmit / transmit the first message (e.g., Msg 1 1311) (e.g., preamble). The wireless device may begin the time window one or more symbols after the last symbol (e.g., Msg 1 1311) of a first message including a preamble (e.g., a symbol at which a first message including a preamble transmission (e.g., Msg 1 1311) is completed or is in the first PDCCH opportunity from the end of the preamble transmission). The one or more symbols may be determined based on a numerology.The PDCCH may be mapped to a common search space (e.g., Type1-PDCCH common search space) configured by an RRC message. The wireless device may identify / determine the RAR, for example, based on the RNTI. The radio network temporary identifier (RNTI) may be used in response to one or more events that initiate / start a random access procedure. The wireless device may use the RA-RNTI, for example, for one or more communications related to random access or any other purpose. The RA-RNTI may be associated with a PRACH opportunity in which the wireless device transmits / transmits a preamble. The wireless device may determine the RA-RNTI, for example, based on at least one of an OFDM symbol index, a slot index, a frequency domain index, and / or a UL carrier indicator of the PRACH opportunity. An example of the RA-RNTI may be determined as follows: RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_idd Here, 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] The wireless device may, for example, transmit / transmit a third message (e.g., Msg 3 1313) based on (e.g., subsequently or in response to) successful reception of the second message (e.g., Msg 2 1312) (e.g., using resources identified in Msg 2 1312). The third message (e.g., Msg 3 1313) may, for example, be used for contention resolution in a contention-based random access procedure. Multiple wireless devices may transmit / transmit the same preamble to a base station, and the base station may transmit / transmit an RAR corresponding to the wireless device. Collisions may occur, for example, when multiple wireless devices interpret the RAR as corresponding to itself. Contention resolution (e.g., using the third message (e.g., Msg 3 1313) and the fourth message (e.g., Msg 4 1314)) may be used to increase the likelihood that a wireless device does not mistakenly use the identity of another wireless device. The wireless device may include an equipment identifier in a third message (e.g., Msg 3 1313) (e.g., the C-RNTI, if assigned, the TC RNTI included in the second message (e.g., Msg 2 1312), and / or any other suitable identifier), for example, to perform contention resolution.

[0122] A fourth message (e.g., Msg 4 1314) may be received, for example, based on (e.g., after or in response to) the transmission / transmission of the third message (e.g., Msg 3 1313). The base station may address the radio on 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 be successful, for example, if the wireless device's unique C-RNTI is detected on the PDCCH (e.g., the PDCCH is scrambled by the C-RNTI). A fourth message (e.g., Msg 4 1314) may be received using a DL-SCH associated with the TC RNTI, e.g., if the TC RNTI is included in the third message (e.g., Msg 3 1313) (e.g., if the wireless device is in an RRC idle (e.g., RRC_IDLE) state or is otherwise connected to a base station). For example, if the MAC PDU is successfully decoded and the MAC PDU includes a wireless device contention resolution identity MAC CE that matches or otherwise corresponds to the CCCH SDU 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] A wireless device may be configured with a SUL carrier and / or a NUL carrier. Initial access (e.g., random access) may be supported over an uplink carrier. A base station may configure a wireless device with multiple RACH configurations (e.g., two separate RACH configurations, one for the SUL carrier and the other for the NUL carrier). For random access in a cell configured with a SUL carrier, the network may indicate which carrier (NUL or SUL) to use. The wireless device may decide to use the SUL carrier, for example, if the measured quality of one or more reference signals (e.g., one or more reference signals associated with the NUL carrier) is lower than a broadcast threshold. Uplink transmission of the random access procedure (e.g., the first message (e.g., Msg 1 1311) and / or the third message (e.g., Msg 3 1313)) may remain on or be made over the selected carrier. The wireless device may switch uplink carriers during a 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 transmit / 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. A two-step contention-free random access procedure may not include messages similar to the third message (eg, Msg 3 1313) and / or the fourth message (eg, Msg 4 1314).

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

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

[0127] 13C shows an example of a two-step random access procedure. Similar to the random access procedure shown in FIGS. 13A and 13B, a base station may send / transmit a configuration message 1330 to a wireless device prior to initiation of the procedure. The configuration message 1330 may be similar in some respects to the configuration message 1310 and / or the configuration message 1320. The procedure shown in FIG. 13C may include 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 transmitted / 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, and / or the like). The wireless device may receive a second message (e.g., Msg B 1332), for example, based on (e.g., subsequently in response to) transmitting / transmitting a first message (e.g., Msg A 1331). The second message (e.g., Msg B 1332) may include content that is 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 start / initiate a two-step random access procedure (e.g., the two-step random access procedure shown in FIG. 13C) for licensed and / or unlicensed spectrum. The wireless device may determine whether to start / initiate a two-step random access procedure based on one or more factors. The one or more factors may include at least one of the radio access technology in use (e.g., LTE, NR, and / or the like), whether the wireless device has a valid TA, the cell size, the RRC state of the wireless device, the type of spectrum (e.g., licensed vs. unlicensed), and / or any other suitable factor.

[0130] The wireless device may determine radio resources and / or uplink transmit power of the preamble 1341 and / or transport block 1342 (e.g., included in the first message (e.g., Msg A 1331)) based on the two-step RACH parameters included in the configuration message 1330. The RACH parameters may indicate the MCS, time-frequency resources, and / or power control of the preamble 1341 and / or transport block 1342. The time-frequency resources for the transmission of the preamble 1341 (e.g., PRACH) and the time-frequency resources for the transmission of the transport block 1342 (e.g., PUSCH) may be multiplexed using FDM, TDM, and / or CDM. The RACH parameters may enable the wireless device to determine the receive timing and downlink channel 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, for example, if a preamble identifier of the second message (e.g., Msg B 1332) corresponds to or matches the preamble sent / transmitted by the wireless device and / or if an identifier of the wireless device of the second message (e.g., Msg B 1332) corresponds to or matches an identifier of the wireless device of the first message (e.g., Msg A 1331) (e.g., transport block 1342).

[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 / carried over a PDCCH by a base station. The payload transmitted / carried over a 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] A base station may, for example, attach one or more cyclic redundancy check (CRC) parity bits to the DCI to facilitate detection of transmission errors. A 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 a 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 unicast transmission of a dynamic schedule and / or a random access of a PDCCH order trigger. A DCI with CRC parity bits scrambled with the Temporary Cell RNTI (TC-RNTI) may indicate contention resolution (e.g., Msg 3 similar to Msg 3 1313 shown in FIG. 13A). Encodings of other RNTIs configured by the base station for the wireless device may include a configured Scheduling RNTI (CS RNTI), transmit power control PUCCH RNTI (TPC PUCCH-RNTI), transmit power control PUSCH RNTI (TPC-PUSCH-RNTI), transmit power control SRS RNTI (TPC-SRS-RNTI), Interruption RNTI (INT-RNTI), Slot Format Indication RNTI (SFI-RNTI), Semi-Persistent CSI RNTI (SP-CSI-RNTI), Modulation and Coding Scheme Cell RNTI (MCS-C RNTI), and / or the like.

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

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

[0138] FIG. 14A illustrates 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 include time-frequency resources on 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 CORESET in the time-frequency domain. The first CORESET 1401 and the second CORESET 1402 may occur or be configured / configured at a first symbol in a slot. The first CORESET 1401 may overlap with the second CORESET 1402 in the frequency domain. The third CORESET 1403 may occur or be configured / configured at a third symbol in a slot. The fourth CORESET 1404 may occur or be configured / configured at a seventh symbol in a slot. The CORESETs may have different numbers of resource blocks in the frequency domain.

[0139] FIG. 14B illustrates an example of CCE-REG mapping. CCE-REG mapping may be implemented for DCI transmission via CORESET and PDCCH processing. CCE-REG mapping may be interleaved (e.g., for providing frequency diversity) or non-interleaved (e.g., for facilitating interference coordination and / or frequency selective transmission of control channels). A base station may perform different or identical CCE-REG mappings on 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 QCL parameter of an antenna port may indicate QCL information of a DM-RS for PDCCH reception via a CORESET.

[0140] A base station may send / transmit one or more RRC messages including configuration parameters of one or more CORESETs and one or more search space sets to a wireless device. The configuration parameters may indicate an association between a search space set and a CORESET. The search space set may include a set of PDCCH candidates formed by CCEs (e.g., at a given aggregation level). The configuration parameters may indicate at least one of a 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, for example, based on the identity of the wireless device (e.g., a C-RNTI).

[0141] In FIG. 14B, the wireless device may determine time-frequency resources of the CORESET based on one or more RRC messages. The wireless device may determine the CCE-REG mapping (e.g., interleaved or non-interleaved, and / or mapping parameters) of the CORESET based on, for example, configuration parameters of the CORESET. The wireless device may determine a number (e.g., up to 10) of search space sets configured on / for the CORESET based on, for example, one or more RRC messages. The wireless device may monitor a set of PDCCH candidates according to 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 a monitored DCI format. The monitoring may include decoding DCI content of one or more PDCCH candidates in possible (or configured) PDCCH positions, possible (or configured) PDCCH formats (e.g., number of CCEs, number of PDCCH candidates in a common search space, and / or number of PDCCH candidates in a wireless device specific search space), and possible (or configured) DCI formats. The decoding may be referred to as blind decoding. The wireless device may determine the DCI to be valid for the wireless device, for example, based on (e.g., in response to) a CRC check (e.g., scrambling bits of the CRC parity bits of the DCI matching the RNTI value). The wireless device may process information included in the DCI (e.g., scheduling assignments, uplink grants, power control, slot format indication, downlink preemption, and / or the like).

[0142] Uplink control signaling (such as UCI) may be sent / transmitted to the base station. The uplink control signaling may include a HARQ acknowledgement for a received DL-SCH transport block. The wireless device may send / transmit the HARQ acknowledgement, for example, based on (e.g., subsequently in response to) receiving the DL-SCH transport block. The uplink control signaling may include CSI indicating a 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 multiple antennas and beamforming schemes) for the downlink transmission based on the received CSI. The uplink control signaling may include a scheduling request (SR). The wireless device may send / transmit an SR indicating that uplink data is available to be transmitted to the base station. The wireless device may send / transmit UCI (e.g., HARQ acknowledgement (HARQ-ACK), CSI report, SR, etc.) via the PUCCH or PUSCH. A wireless device may transmit / carry uplink control signaling over the PUCCH using one of several PUCCH formats.

[0143] There may be multiple PUCCH formats (e.g., five PUCCH formats). A wireless device may determine a PUCCH format based on, for example, the size of the UCI (e.g., the quantity / number of uplink symbols of the UCI transmission and the number of UCI bits). PUCCH format 0 may have a length of one or two OFDM symbols and may include two or less bits. A wireless device may use PUCCH format 0 to transmit / transmit UCI over PUCCH resources, for example, when the transmission spans one or two symbols and the quantity / number of HARQ-ACK information bits with positive or negative SR (HARQ-ACK / SR bits) is one or two. PUCCH format 1 may occupy several OFDM symbols (e.g., between 4-14 OFDM symbols) and may include two or less bits. A wireless device may use PUCCH format 1, for example, when the transmission spans four or more symbols and the number of HARQ-ACK / SR bits is one or two. PUCCH format 2 may occupy one or two OFDM symbols and may include more than two bits. A wireless device may use PUCCH format 2, for example, when the transmission is over one or two symbols and the quantity / number of UCI bits is two or more. PUCCH format 3 may occupy several OFDM symbols (e.g., between 4 and 14 OFDM symbols) and may include more than two bits. A wireless device may use PUCCH format 3, for example, when the transmission is four or more symbols, the quantity / number of UCI bits is two or more, and the PUCCH resource does not include an orthogonal cover code (OCC). PUCCH format 4 may occupy several OFDM symbols (e.g., between 4 and 14 OFDM symbols) and may include more than two bits. A wireless device may use PUCCH format 4, for example, when the transmission is four or more symbols, the quantity / number of UCI bits is two or more, and the PUCCH resource includes an OCC.

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

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

[0146] FIG 15A illustrates an example of communication between a wireless device and a base station. The wireless device 1502 and the base station 1504 may be part of a communication network, such as the communication network 100 shown in FIG 1A, the communication network 150 shown in FIG 1B, or 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 configuration as that 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 communication direction from the base station 1504 to the wireless device 1502 over the air interface 1506 may be referred to as the downlink. The communication direction 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 transmitted from the base station 1504 to the wireless device 1502 may be provided / forwarded / transmitted to the processing system 1508 of the base station 1504. The data may be provided / forwarded / transmitted to the processing system 1508 by, for example, a core network. For the uplink, data transmitted from the wireless device 1502 to the base station 1504 may be provided / forwarded / transmitted to the processing system 1518 of the wireless device 1502. The processing system 1508 and the processing system 1518 may implement Layer 3 and Layer 2 OSI functions to process the data for transmission. Layer 2 may include, for example, the SDAP layer, the PDCP layer, the RLC layer, and the MAC layer described with respect to Figures 2A, 2B, 3, and 4A. Layer 3 may include, for example, the RRC layer described with respect to Figure 2B.

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

[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 include one or more TRPs. The receive processing system 1522 of the wireless device 1502 may receive downlink transmissions from the base station 1504. The receive processing system 1522 of the wireless device 1502 may include one or more antenna panels. The receive processing system 1512 and the receive processing system 1522 may implement Layer 1 OSI functions. Layer 1 may include, for example, the PHY layer described with respect to Figures 2A, 2B, 3, and 4A. For receive processing, the PHY layer may perform, for example, error detection, forward error correction decoding, deinterleaving, demapping of transport channels to physical channels, demodulation of physical channels, MIMO or multi-antenna processing, and / or the like.

[0151] The base station 1504 may include multiple antennas (e.g., multiple antenna panels, multiple TRPs, etc.). The wireless device 1502 may include multiple antennas (e.g., multiple antenna panels, etc.). The multiple antennas may be used to implement one or more MIMO or multi-antenna techniques, such as spatial multiplexing (e.g., single-user MIMO or multi-user MIMO), transmit / receive diversity, and / or beamforming. The wireless device 1502 and / or the base station 1504 may have a single antenna.

[0152] The processing system 1508 and the processing system 1518 may be associated with a memory 1514 and a memory 1524, respectively. The memory 1514 and the memory 1524 (e.g., one or more non-transitory computer-readable media) may store computer program instructions or code that may be executed by the processing system 1508 and / or the processing system 1518, respectively, to perform one or more functions (e.g., one or more functions described herein and other functions of a general computer, processor, memory, and / or other peripheral device). The transmit processing system 1510 and / or the receive processing system 1512 may be coupled to the memory 1514 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. The transmit processing system 1520 and / or the receive processing system 1522 may be coupled to a 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] The processing system 1508 and / or the processing system 1518 may include one or more controllers and / or one or more processors. The one or more controllers and / or the one or more processors may include, for example, a general purpose processor, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) and / or other programmable logic devices, discrete gate and / or transistor logic, discrete hardware components, on-board units, or any combination thereof. The processing system 1508 and / or the processing system 1518 may perform at least one of signal coding / processing, data processing, power control, input / output processing, and / or any other functionality that may enable the wireless device 1502 and / or the base station 1504 to operate in a wireless environment.

[0154] The processing system 1508 may be connected to one or more peripheral devices 1516. The processing system 1518 may be connected to one or more peripheral devices 1526. The one or more peripheral devices 1516 and the one or more peripheral devices 1526 may include software and / or hardware that provide features and / or functionality, such as a speaker, a microphone, a keypad, a display, a touchpad, a power source, a satellite transceiver, a universal serial bus (USB) port, a hands-free headset, a frequency modulation (FM) radio unit, a media player, an Internet browser, an electronic control unit (e.g., for a vehicle), and / or one or more sensors (e.g., an accelerometer, a gyroscope, a temperature sensor, a radar sensor, a lidar sensor, an ultrasonic sensor, a light sensor, a camera, and / or the like). The processing system 1508 and / or the processing system 1518 may receive input data (e.g., user input data) from and / or provide output data (e.g., user output data) to the one or more peripheral devices 1516 and / or the one or more peripheral devices 1526. The processing system 1518 of the wireless device 1502 may receive power from a power source and / or may be configured to distribute power to other components of the wireless device 1502. The power source may include one or more power sources, such as a battery, a solar cell, a fuel cell, or any combination thereof. The processing system 1508 may be connected to a global positioning system (GPS) chipset 1517. The processing system 1518 may be connected to a global positioning system (GPS) chipset 1527. The GPS chipset 1517 and the GPS chipset 1527 may be configured to determine and provide geographic location information of the wireless device 1502 and the 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 in random access memory (RAM) 1533, removable media 1534 (such as a universal serial bus (USB) drive, a compact disc (CD) or digital versatile disc (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) that may execute instructions of one or more computer programs to monitor processes running on the processor 1531 and any processes requesting access to any hardware and / or software components of the computing device 1530 (e.g., ROM 1532, RAM 1533, removable media 1534, hard drive 1535, device controller 1537, network interface 1539, GPS 1541, Bluetooth interface 1542, WiFi interface 1543, etc.). The computing device 1530 may include one or more output devices such as a display 1536 (e.g., a screen, display device, monitor, television, etc.) and may include one or more output device controllers 1537, such as a video processor. There may also be one or more user input devices 1538, such as a remote control, keyboard, mouse, touch screen, microphone, etc.The computing device 1530 may also include one or more network interfaces, such as a network interface 1539, which may be a wired interface, a wireless interface, or a combination of the two. The network interface 1539 may provide an interface for the computing device 1530 to communicate with a network 1540 (e.g., a RAN, or any other network). The network interface 1539 may include a modem (e.g., a cable modem), and the external network 1540 may include a communications link, an external network, a home network, a provider's wireless, coaxial, fiber, or hybrid fiber / coaxial distribution system (e.g., a DOCSIS network), or any other desired network. Additionally, the computing device 1530 may include a location device, such as a global positioning system (GPS) microprocessor 1541, which may be configured to receive and process global positioning signals and determine the geographic location of the computing device 1530, with possible assistance from external servers and antennas.

[0156] FIG. 15B may be a hardware configuration, but the components shown may be implemented as software as well. If desired, modifications may be made to add, remove, combine, divide, etc. components of the computing device 1530. Furthermore, the 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 may coexist on a common physical platform (e.g., a requesting entity may be a separate software process and program from a dependent entity, both of which may be executed as software on a common computing device).

[0157] FIG. 16A illustrates an example structure for uplink transmission. The processing of the baseband signal representing the physical uplink shared channel may include / perform one or more functions. The one or more functions may include at least one of: scrambling, modulation of scramble bits to generate complex-valued symbols, mapping of complex-valued modulation symbols onto one or several transmission layers, transform precoding to generate complex-valued symbols, precoding of the complex-valued symbols, mapping of the precoded complex-valued symbols onto resource elements, complex-valued time domain single carrier frequency division multiple access (SC-FDMA), generation of CP-OFDM signals for antenna ports, or any other signals, and / or the like. The SC-FDMA signals for uplink transmission may be generated, for example, when transform precoding is enabled. The CP-OFDM signals 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 example structure for modulation and up-conversion of a baseband signal to a carrier frequency. The baseband signal may be a complex-valued SC-FDMA, CP-OFDM baseband signal (or any other baseband signal) for an antenna port and / or a complex-valued Physical Random Access Channel (PRACH) baseband signal. Filtering may be performed / employed, for example, before transmission.

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

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

[0161] A wireless device may receive one or more messages (e.g., RRC messages) from a base station including configuration parameters for multiple cells (e.g., a primary cell, one or more secondary cells). A wireless device may communicate with at least one base station (e.g., two or more base stations for dual connectivity) via the multiple cells. The one or more messages (e.g., as part of the configuration parameters) may include PHY, MAC, RLC, PCDP, SDAP, 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 continue to run until it is stopped or expires. A timer may be started if it is not running or restarted if it is running. A timer may be associated with a value (e.g., a timer may be started or restarted from a value, or may be started from zero and expire when the value is reached). A timer's duration may not be updated until the timer is stopped or expires (e.g., due to BWP switching). A timer may be used to measure a time period / window of a process. With respect to implementations and / or procedures related to one or more timers or other parameters, it will be understood that there may be multiple ways to implement one or more timers or other parameters. One or more of multiple ways of implementing a timer may be used to measure a time period / window of a procedure. A random access response window timer may be used to measure a window of time for receiving a random access response. The time difference between two timestamps may be used, for example, instead of starting a random access response window timer and determining the expiration of the timer. The process for measuring the time window may be restarted, for example, if the timer is restarted. Other embodiment implementations may be configured / provided to restart the measurement of the time window.

[0163] The wireless device may receive configuration parameters, for example, from a base station. The configuration parameters may indicate values ​​for fields (e.g., unified TCI state index, TRP index, core set pool index, etc.) for uplink resources (and / or uplink resource sets / groups). The uplink resources may be PUCCH resources. The uplink resources may be SRS resources. The uplink resource set / group may be a PUCCH resource group. The uplink resource set / group may be an SRS resource set.

[0164] The wireless device may receive a first downlink message (e.g., DCI, MAC-CE) indicating activation of two TCI states (e.g., two unified TCI states) including at least a first TCI state and a second TCI state. The first TCI state may be associated with a first TRP. The second TCI state may be associated with a second TRP. The wireless device may apply / use the first TCI state and / or the second TCI state for transmission of an uplink signal via an uplink resource, for example, based on the value of the field. The wireless device may use the first TCI state, for example, if the value is equal to 0 (e.g., 0, 00). The wireless device may use the second TCI state, for example, if the value is equal to 1 (e.g., 1, 01). The wireless device may use the first TCI state and the second TCI state, for example, if the value is equal to 2 (e.g., 10, 11).

[0165] The wireless device may receive a second downlink message (e.g., DCI, MAC-CE) indicating activation of a third TCI state (e.g., single / one TCI state). In at least some systems, the value of the field may be used to determine a TCI state to apply / use for transmission of an uplink signal over the uplink resource. This operation may not be efficient, for example, if a single TCI state is activated. The wireless device may apply / use the third TCI state for transmission of an uplink signal over the uplink resource regardless of the value of the field. The wireless device may ignore the value of the field, for example, if the second downlink message indicates activation of the single / one TCI state. The wireless device may apply / use the single / one TCI state for transmission of an uplink signal over the uplink resource, for example, if the second downlink message indicates activation of the single / one TCI state. The wireless device may suspend transmission of an uplink signal over the uplink resource. The wireless device may suspend transmission of an uplink signal over the uplink resource based, for example, on the third TCI state being associated with the first TRP and the value of the field being associated with the second TRP (or vice versa). The wireless device may, for example, apply / use a third TCI state for transmission of an uplink signal via the second uplink resource based on the third TCI state being associated with the first TRP and the second value of the field for the second uplink resource being associated with the first TRP. The configuration parameter may indicate a second value for the field for the second uplink resource.

[0166] The wireless device may receive configuration parameters, for example from a base station, that may indicate a first SRS resource set list and a second SRS resource set list, and the one or more configuration parameters may indicate two SRI fields for a configured uplink grant (e.g., a type 1 configured uplink grant).

[0167] The first SRS resource set list may include two SRS resource sets. The second SRS resource set list may include two SRS resource sets. In at least some systems, the wireless device may transmit (e.g., transmit) at least one transport block based on the two SRS resource sets in the first SRS resource set list for a configured uplink grant. The wireless device may transmit (e.g., transmit) at least one transport block based on the two SRS resource sets in the first SRS resource set list for a configured uplink grant, e.g., based on (e.g., in response to) one or more configuration parameters indicating two SRI fields for the configured uplink grant. The SRI field in the configured uplink grant may, for example, indicate (e.g., always indicate) an SRS resource in an SRS resource set in one SRS resource set list (e.g., srs-ResourceSetToAddModList) of two SRS resource set lists (e.g., srs-ResourceSetToAddModList and srs-ResourceSetToAddModListDCI-0-2) if the wireless device is configured with two SRS resource set lists. The quantity / number of SRS resource sets in the SRS resource set list may be one, two, or any other quantity / number (e.g., srs-ResourceSetToAddModList and srs-ResourceSetToAddModList may each include one or two SRS resource sets). The SRI field in the configured uplink grant may, for example, indicate (e.g., always indicate) an SRS resource in an SRS resource set in a first SRS resource set list (e.g., srs-ResourceSetToAddModList) if one or two SRI fields are configured for the configured uplink grant.For example, in at least some systems, the SRI field of a configured uplink grant may always indicate an SRS resource in the SRS resource set of srs-ResourceSetToAddModList. A first SRS resource list (e.g., srs-ResourceSetToAddModList) may have a higher priority than a second SRS resource list (e.g., srs-ResourceSetToAddModListDCI-0-2), which may result in the first SRS resource list being indicated by the SRI field of the configured grant.

[0168] In at least some systems, the first SRS resource set list may include a single SRS resource set and the second SRS resource set list may include two (or more) SRS resource sets. At least some wireless communications may not be efficient, for example, if one or more configuration parameters indicate that for a configured uplink grant, two SRI fields and the first SRS resource set list include a single SRS resource set. At least some wireless devices may not transmit (e.g., transmit) a transport block based on two SRS resource sets for a configured uplink grant. For example, a base station may configure a single SRS resource set in the first SRS resource set list (e.g., srs-ResourceSetToAddModList) and two SRS resource sets in the second SRS resource set list (e.g., srs-ResourceSetToAddModListDCI-0-2). In at least some wireless communications, a first SRS resource set list may be configured (or associated) for a first type of information for a transmission (e.g., eMBB transmission), which may be prioritized over a second type of information for the transmission (e.g., uRLLC transmission). A second SRS resource set list may be configured (or associated) for a second (or other) type of information for a transmission, such that resources of the first SRS resource set list may be used instead of resources of the second SRS resource set list, for example, when only one of the SRS resource set lists may be used (e.g., in a single TRP mode, where a TRP is associated with a single SRS resource set list). However, when two SRI fields are configured for an uplink grant, prioritizing the first SRS resource set list (e.g., srs-ResourceSetToAddModList) may not be efficient.For example, such prioritization of a first SRS resource set list may require the wireless device to either ignore one of the two SRI fields of the configured uplink grant or not support multiple TRP repetition (e.g., multiple TRP PUSCH repetition) by using a single SRS resource set in the first SRS resource set list (e.g., srs-ResourceSetToAddModList). Prioritizing a particular SRS resource set list without considering the amount of SRS resources configured in the list may reduce the reliability and / or robustness of transmissions.

[0169] As described herein, prioritization may be applied to the use of SRS resource set lists configured with a larger number of SRS resource sets to improve wireless communication. For example, if two SRS resource sets are configured in a first SRS resource set list (e.g., srs-ResourceSetToAddModList), the two SRI fields of the configured uplink grant may indicate the two SRS resource sets in the first SRS resource set list (e.g., srs-ResourceSetToAddModList). However, if only one SRS resource set is configured in the first SRS resource set list (e.g., srs-ResourceSetToAddModList) and a second SRS resource set list (e.g., srs-ResourceSetToAddModListDCI-0-2) is configured with two SRS resource sets, the two SRI fields of the configured uplink grant may indicate the two SRS resource sets in the second SRS resource set list (e.g., srs-ResourceSetToAddModListDCI-0-2). As described herein (e.g., in FIG. 20A and FIG. 20B), for example, when a first SRS resource set list includes a single SRS resource set and a second SRS resource set list includes two (or more) SRS resource sets, a wireless device may be configured to transmit (e.g., transmit) a message (e.g., at least one transport block) based on two (or more) SRS resource sets in the second SRS resource set list for a configured uplink grant. The wireless device may transmit a message based on the second SRS resource list (e.g., using repetitions) even if, for example, the wireless device may have a second, higher priority message configured for transmission based on the first resource list (e.g., a single transmission). This use of two (or more) SRS resource sets may enable the use of repetitions over a single transmission, which may provide advantages such as, for example, increased reliability and / or robustness of the transmission.

[0170] In another embodiment, at least some wireless devices may receive configuration parameters (e.g., from a base station). The configuration parameters may indicate a first SRS resource set list and a second SRS resource set list. The first SRS resource set list may include an SRS resource set. The second SRS resource set list may include an SRS resource set. In at least some systems, if such wireless devices may receive an indication (e.g., a MAC-CE indicates the activation (or update)) to activate or update a path loss reference signal for an SRS resource set in the first SRS resource set, the wireless device may apply / use a path loss reference signal for an SRS resource set in the first SRS resource set list and an SRS resource set in the second SRS resource set list. The first SRS resource set list may include two SRS resource sets. The second SRS resource set list may include two SRS resource sets. Such a wireless device may not know, for example, whether to use the path loss reference signal for the first SRS resource set or the second SRS resource set in the second SRS resource set list when the wireless device receives an indication (e.g., the MAC-CE indicates the activation (or update)) of a path loss reference signal for a first SRS resource set of two SRS resource sets in the first SRS resource set. For example, if two SRS resource sets in a first SRS resource set list (e.g., srs-ResourceSetToAddModList) and two SRS resource sets in a second SRS resource set list (e.g., srs-ResourceSetToAddModListDCI-0-2) are configured and the path loss reference signal of the first SRS resource set in the first SRS resource set list (e.g., srs-ResourceSetToAddModList) is updated, such a wireless device may not be able to determine which SRS resource set in the second SRS resource set list (e.g., srs-ResourceSetToAddModListDCI-0-2) should be updated.This uncertainty may result in misalignment between such wireless devices and base stations (e.g., power control misalignment, transmit power misalignment, path loss reference signal misalignment, etc.) For example, such wireless devices may apply / use a path loss reference signal to a second SRS resource set of a second SRS resource set list, and the base station may assume that the wireless device applies the path loss reference signal to a first SRS resource set of the second SRS resource set list, resulting in misalignment between the wireless devices and the base station.

[0171] As described herein, the extended path loss reference signal update operation may be performed, for example, when a first SRS resource set list includes two SRS resource sets and a second SRS resource set list includes two SRS resource sets. For example, if the wireless device receives an indication (e.g., the MAC-CE indicates its activation (or its update)) to activate or update a path loss reference signal for a first SRS resource set of the two SRS resource sets in the first SRS resource set, the wireless device may apply / use a path loss reference signal to / for the first SRS resource set in the second SRS resource set list. The wireless device may use a path loss reference signal for a second SRS resource set in the second SRS resource set list, for example, when the wireless device receives an indication (e.g., the MAC-CE indicates its activation (or its update)) to activate or update a path loss reference signal for a second SRS resource set of the two SRS resource sets in the first SRS resource set. As described herein (e.g., with respect to FIG. 21), when the path loss reference signal of the first / second SRS resource set in the first SRS resource set list (e.g., srs-ResourceSetToAddModList) is updated, the wireless device may also update the path loss reference signal of the first / second SRS resource set in the second SRS resource set list (e.g., srs-ResourceSetToAddModListDCI-0-2). The first SRS resource set (in the first SRS resource set list and / or the second SRS resource set list) may be identified / indicated with / using the lowest SRS resource set index or the first SRS resource set index that is lower than the second SRS resource set index of the second SRS resource set (in the first SRS resource set list and / or the second SRS resource set list).The second SRS resource set (in the first SRS resource set list and / or the second SRS resource set list) may be identified / indicated with / using the highest SRS resource set index or the second SRS resource set index that is higher than the first SRS resource set index of the second SRS resource set (in the first SRS resource set list and / or the second SRS resource set list). The described path loss criteria update / activation may also be applied when the first SRS resource set list includes two SRS resource sets and the second SRS resource set list includes a single SRS resource set, and / or when the first SRS resource set list includes a single SRS resource set and the second SRS resource set list includes two SRS resource sets. The path loss criteria update / activation operations described herein may provide advantages such as reduced beam misalignment, which may result in reduced retransmissions, reduced delays / latencies, and / or reduced power consumption.

[0172] FIG. 17 illustrates an example TCI state update. The TCI state update may include a unified beam update. The wireless device 1701 may receive one or more messages (e.g., at time T0). The wireless device 1701 may receive one or more messages from a computing device 1702, which may include any computing device described herein (e.g., a base station, a relay node, a wireless device, etc.). For example, the wireless device 1701 may receive one or more messages from a base station. The wireless device 1701 may receive one or more messages from a relay node. The wireless device 1701 may receive one or more messages from another wireless device (e.g., a TRP, a vehicle, a remote radio head, etc.). The one or more messages may include one or more configuration parameters (e.g., the configuration parameters at time T0 of FIG. 17). The one or more configuration parameters may include RRC configuration parameters. The one or more configuration parameters may include RRC reconfiguration parameters.

[0173] The one or more configuration parameters may be for the multiple cells. The multiple cells may include a cell. The cell may be, for example, a serving cell. At least one configuration parameter of the one or more configuration parameters may be for a cell. The cell may be a primary cell (PCell). The cell may be a secondary cell (SCell). The cell may be a secondary cell configured for / with a PUCCH (e.g., a PUCCH SCell). The cell may be, for example, an unlicensed cell operating in an unlicensed band. The cell may be, for example, a licensed cell operating in a licensed band. The cell may operate in a first frequency range (e.g., FR1). FR1 may include, for example, a frequency band below 6 GHz (or any other frequency or frequency range). The cell may operate in a second frequency range (e.g., FR2). FR2 may include, for example, a frequency band from 24 GHz to 52.6 GHz (or any other frequency or frequency range). The cell may operate in a third frequency range (FR3). FR3 may include, for example, the frequency band from 52.6 GHz to 71 GHz (or any other frequency or range of frequencies). FR3 may include, for example, the frequency band beginning at (or exceeding) 52.6 GHz (or any other frequency).

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

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

[0176] A cell may include multiple BWPs. The multiple BWPs may include one or more uplink BWPs including an uplink BWP of the cell. The multiple BWPs may include one or more downlink BWPs including a downlink BWP of the cell.

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

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

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

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

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

[0182] The one or more configuration parameters may be for an (active) uplink BWP of the cell. At least one of the one or more configuration parameters may be for an uplink BWP of the cell. The one or more configuration parameters may indicate a subcarrier spacing (or numerology) for a downlink BWP. The one or more configuration parameters may indicate a subcarrier spacing (or numerology) for an uplink BWP.

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

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

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

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

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

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

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

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

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

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

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

[0194] A (single) TCI state pool / group may include multiple TCI states. The multiple TCI states may / can include multiple downlink TCI states. The multiple TCI states may / can include multiple uplink TCI states.

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

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

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

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

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

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

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

[0202] The activation command may include one or more fields indicating / including at least one TCI state index identifying / indicating / a subset of the plurality of TCI states. The plurality of TCI state indexes may include at least one TCI state index. Each TCI state of the subset of the plurality of TCI states may be identified / indicated by a respective TCI state index of the at least one TCI state index. The one or more fields may be set to a value (e.g., 1) indicating activation of the subset of the plurality of TCI states. Based on the one or more fields indicating the subset of the plurality of TCI states being set to a value, the wireless device may activate the subset of the plurality of TCI states. The wireless device may activate the subset of the plurality of TCI states based on, for example, receiving an activation command to activate / select / indicate / update the subset of the plurality of TCI states.

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

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

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

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

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

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

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

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

[0211] Receiving a downlink signal based on the TCI state may include at least one DMRS antenna port of the downlink signal (e.g., PDSCH / PDCCH transmission, transport block) being quasi-collocated with a reference signal (e.g., CSI-RS, SS / PBCH block, SRS, PUCCH, etc.) indicated by the TCI state. At least one DMRS antenna port of the downlink signal may be quasi-collocated with a reference signal with respect to a quasi-collocation type (e.g., QCL TypeA, QCL TypeB, QCL TypeC, QCL TypeD, etc.). The TCI state may indicate / include / have a quasi-collocation type. The TCI state may include / have a reference signal index that indicates / identifies a reference signal. One or more configuration parameters may indicate a reference signal index for the TCI state.

[0212] Receiving a downlink signal based on the TCI state may include the downlink signal (e.g., CSI-RS, DM-RS) being quasi-collocated with a reference signal (e.g., CSI-RS, SS / PBCH block, SRS, PUCCH, etc.) indicated by the TCI state. The downlink signal may be quasi-collocated with the reference signal with respect to a quasi-collocation type (e.g., QCL TypeA, QCL TypeB, QCL TypeC, QCL TypeD, etc.). The TCI state may indicate / include / have the quasi-collocation type. The TCI state may include / have a reference signal index that indicates / identifies the reference signal. One or more configuration parameters may indicate a reference signal index for the TCI state.

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

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

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

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

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

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

[0219] The DCI may include a TCI field. The TCI field may indicate one TCI code point among one or more TCI code points. The value of the TCI field (e.g., 110 in step 1730 of FIG. 17 or 111 in step 1740 of FIG. 17) may be equal to a TCI code point, for example. The value of the TCI field may indicate a TCI code point, for example. The TCI code point (e.g., 110) may indicate / include at least two TCI states. The at least two TCI states may include a first TCI state and a second TCI state. For example, in FIG. 17, the first TCI state is TCI state 26. The second TCI state is TCI state 61. Any TCI code point may indicate / include any one or more TCI states (e.g., one TCI state, two TCI states, or any quantity of TCI states). The DCI indicates the activation of one TCI state (e.g., TCI state 42 at time T3 in FIG. 17). A DCI may indicate the activation of at least two TCI states (or any other quantity of TCI states).

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

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

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

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

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

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

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

number

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0241] In at least some wireless communications, a unified / joint transmission configuration indicator (TCI) state may be used. A wireless device may apply the unified / joint TCI state for transmission of all uplink signals (e.g., PUSCH / PUCCH / SRS) and reception of all downlink signals (e.g., PDSCH / PDCCH / CSI-RS) when, for example, the wireless device is indicated / activated in the unified / joint TCI state. Using the unified / joint TCI state may reduce the quantity / number of TCI state (or beam) activations for each channel separately, which may reduce beam activation signaling. By using the unified / joint TCI state with a single beam activation signaling, the wireless device may use the same beam for all uplink transmissions and / or downlink receptions. In at least some wireless communications, two unified / joint TCI states may be used. For example, a first unified / joint TCI state may be associated with a first TRP, and a second unified / joint TCI state may be associated with a second TRP. Fields (e.g., unified TCI state field, TRP field, etc.) may be configured for uplink and downlink channels. The values ​​of the fields may indicate to apply a first unified / joint TCI and / or a second unified / joint TCI state. In at least some instances, the base station may decide to switch to a single TRP mode and thus activate the single unified / joint TCI state. However, the wireless device may not be able to determine (e.g., in sufficient time) that the base station has activated the single unified / joint TCI state, e.g., depending on the location and / or velocity of the wireless device relative to the base station. The wireless device may not be able to interpret / process the base station switch from two unified / joint TCI states (e.g., two TRP or multi-TRP mode) to a single unified / joint TCI state (e.g., single TRP mode). Additionally or alternatively, the wireless device may not be able to determine the TCI state to use for one or more channels if the wireless device is switched to the single unified TCI state.For example, a first channel (e.g., PDSCH) may be configured with a first value (e.g., 0) of the unified TCI state field, and a second channel (e.g., PDCCH) may be configured with a second value (e.g., 1) of the unified TCI state field. When two unified TCI states are activated (e.g., multi-TRP mode is turned on), the wireless device may apply a first unified TCI state to the first channel using the first value of the unified TCI state field, and the wireless device may apply a second unified TCI state to the second channel using the second value of the unified TCI state field. However, when a single unified TCI state is switched (e.g., single TRP mode is turned on), the first value and the second value may not refer to any related TCI state because only a single unified TCI state may be activated. Thus, such a wireless device may experience difficulty in determining / selecting a TCI state to use for one or more channels, for example, when a single unified TCI state is activated.

[0242] As described herein, wireless communication may be enhanced to switch between two unified / joint TCI states and a single unified / joint TCI state. A wireless device may be configured such that if the uplink / downlink channels of the wireless device are configured with a field (e.g., unified TCI state field, TRP field, etc.) and if the wireless device is indicated / configured in a single unified / joint TCI state, the wireless device may perform one or more default actions (e.g., known by the base station according to a default rule). For example, the wireless device may ignore the field and apply a single unified / joint TCI state to the uplink / downlink channels, and / or the wireless device may pause / stop / clear / release transmission / reception of the uplink / downlink channels. The wireless device may pause / stop / clear / release transmission / reception based on, for example, a relationship / mapping / association between the single unified / joint TCI state TCI state and the TRP. By configuring a wireless device to operate in a predictable / default manner as described herein (e.g., FIGS. 18A and 18B), the wireless device and base station may improve alignment in wireless communications, for example, when switching between two unified / joint TCI states and a single unified / joint TCI state.

[0243] 18A and 18B illustrate an example method of unified beam updating. In step 1810, the wireless device may receive (e.g., from a base station) one or more messages including one or more configuration parameters of the cell. In step 1805, the base station may send (e.g., transmit) one or more messages including the one or more configuration parameters to the wireless device. The one or more configuration parameters may indicate multiple TCI states. For example, the one or more configuration parameters may indicate multiple TCI states for an uplink BWP of the cell. For example, the one or more configuration parameters may indicate multiple TCI states for a downlink BWP of the cell.

[0244] The wireless device may activate (and / or set) an uplink BWP as the active uplink BWP for the cell. The wireless device may activate (and / or set) a downlink BWP as the active downlink BWP for the cell. For example, the base station may send (e.g., transmit) a downlink message (e.g., DCI, MAC-CE, RRC message) indicating activation of the uplink BWP. For example, the base station may send (e.g., transmit) a downlink message (e.g., DCI, MAC-CE, RRC message) indicating activation of the downlink BWP.

[0245] The multiple TCI states may include multiple joint / downlink TCI states (or joint uplink / downlink TCI states). The multiple TCI states may include multiple uplink TCI states. The multiple TCI states may include multiple downlink TCI states.

[0246] The one or more configuration parameters may indicate a field (e.g., a unified / common / joint TCI state index field, a TRP index field, a core set pool index field, etc.) having a value indicating at least one TCI state of at least two TCI states for an uplink resource group / set (or an uplink resource within an uplink resource group / set).

[0247] The uplink resource group / set may / can include a PUCCH resource group. The uplink resources may be PUCCH resources. The uplink resource group / set may / can include an SRS resource set. The uplink resources may be SRS resources. The uplink BWP may include uplink resources. One or more configuration parameters may indicate the uplink resources (or uplink resource group / set) for the uplink BWP.

[0248] The one or more configuration parameters may include / indicate a parameter indicating to apply / use a common / unified TCI state for an uplink resource group / set (or uplink resource) (e.g., ApplyTCI-State-UL-List, ApplyTCI-State-DL-List, ApplyTCI-State-List, Use-Indicated-TCI-State, Use-Indicated-UL-TCI-State, Use-Indicated-DL-TCI-State, Follow-Unified-TCI-State, Follow-Unified-UL-TCI-State, Follow-Unified-DL-TCI-State, etc.). The parameter may be set to "enabled".

[0249] In step 1820, the wireless device may receive a wake-up command (e.g., MAC-CE, DCI) indicating activation of a subset of the plurality of TCI states. In step 1815, the base station may send (e.g., transmit) a wake-up command indicating activation of the subset of the plurality of TCI states.

[0250] The wireless device may map a subset of the multiple TCI states to one or more TCI code points, each TCI code point of the one or more TCI code points may indicate a respective TCI state of the subset of the multiple TCI states, and the base station may map the subset of the multiple TCI states to one or more TCI code points.

[0251] The wireless device may receive (e.g., at step 1820) a control message / command (e.g., DCI, MAC-CE). The base station may send (e.g., transmit) the control message / command (e.g., at step 1815). The control message may indicate activation of at least two transmission configuration indicator (TCI) states. The subset of the multiple TCI states may include at least two TCI states. The control message (e.g., DCI) may include a TCI field indicating at least two TCI states. A TCI codepoint of the one or more TCI codepoints may indicate / include at least two TCI states. The TCI field may indicate a TCI codepoint. The control message may be, for example, an activation command. The at least two TCI states may be a subset of the multiple TCI states. The one or more TCI codepoints may be (or may include) a single TCI codepoint.

[0252] The at least two TCI states may / may include at least two joint / common / unified TCI states. The at least two TCI states may / may include at least two joint / common / unified uplink and downlink TCI states. The at least two TCI states may / may include at least two joint / common / unified uplink TCI states. The at least two TCI states may / may include at least two uplink TCI states. The at least two TCI states may / may include at least two joint / common / unified downlink TCI states. The at least two TCI states may / may include at least two downlink TCI states.

[0253] In step 1830, the wireless device may transmit (e.g., transmit) an uplink signal (e.g., HARQ-ACK, SR, CSI report, UCI, SRS, etc.) via the uplink resource based on the at least one TCI state indicated by the value of the field (e.g., based on at least two TCI states). In step 1835, the base station may receive an uplink signal via the uplink resource based on the at least one TCI state indicated by the value of the field (e.g., based on at least two TCI states). The wireless device may transmit (e.g., transmit) an uplink signal via the uplink resource based on the at least one TCI state indicated by the value of the field, e.g., based on (e.g., in response to) a control message / command indicating activation of at least two TCI states. The wireless device may transmit (e.g., transmit) an uplink signal via the uplink resource based on (e.g., in response to) a control message / command indicating activation of two or more TCI states. The wireless device may transmit (e.g., transmit) an uplink signal via the uplink resources based on at least one TCI state indicated by the value of the field, e.g., based on (e.g., in response to) a control message / command indicating activation of the two TCI states, and the base station may receive an uplink signal via the uplink resources based on at least one TCI state indicated by the value of the field, e.g., based on (e.g., in response to) a control message / command indicating activation of the two TCI states.

[0254] The wireless device may apply / use at least one TCI state for transmission of an uplink signal via the uplink resource. Applying / using the at least one TCI state for transmission of an uplink signal via the uplink resource may include transmitting (e.g., transmitting) the uplink signal via the uplink resource with (or based on) at least one spatial domain transmit filter determined based on the at least one TCI state. The wireless device may, for example, determine a respective spatial domain transmit filter of the at least one spatial domain transmit filter based on a respective TCI state of the at least one TCI state. The wireless device may, for example, determine a respective spatial domain transmit filter of the at least one spatial domain transmit filter based on a reference signal indicated by the respective TCI state of the at least one TCI state. Applying / using the at least one TCI state for transmission of an uplink signal via the uplink resource may include transmitting (e.g., transmitting) the uplink signal via the uplink resource at (or based on) at least one transmit power determined based on the at least one TCI state. The wireless device may, for example, determine a respective transmit power of the at least one transmit power based on the respective TCI state of the at least one TCI state. The wireless device may determine each of the at least one transmit powers based on, for example, one or more power control parameters indicated by (or associated with, mapped to, or included in) a respective TCI state of the at least one TCI state. The one or more configuration parameters may indicate, for each TCI state of the at least one TCI state, a respective power control parameter set including one or more power control parameters.

[0255] The base station may apply / use at least one TCI state for reception of an uplink signal via the uplink resources. Applying / using at least one TCI state for reception of an uplink signal via the uplink resources may include receiving the uplink signal via the uplink resources using (or based on) at least one spatial-domain receive / receive filter determined based on the at least one TCI state. The base station may, for example, determine each spatial-domain receive filter of the at least one spatial-domain receive filter based on the respective TCI state of the at least one TCI state. The base station may, for example, determine each spatial-domain receive filter of the at least one spatial-domain receive filter based on a reference signal indicated by the respective TCI state of the at least one TCI state.

[0256] The at least one TCI state may be a first TCI state of the at least two TCI states, for example, based on the value of the field being equal to a first value (e.g., 00, or 0). The at least one TCI state may be a second TCI state of the at least two TCI states, for example, based on the value of the field being equal to a second value (e.g., 01 or 1). The at least one TCI state may be the first TCI state and the second TCI state, for example, based on the value being equal to a third value (e.g., 10). The at least one TCI state may be the first TCI state and the second TCI state, for example, based on the value being equal to a fourth value (e.g., 11).

[0257] The wireless device may transmit (e.g., transmit) an uplink signal via the uplink resources in the uplink resource group / set, e.g., based on (e.g., in response to) one or more configuration parameters including / indicating the parameters for the uplink resource group (or uplink resources), and based on at least one TCI state. The base station may receive an uplink signal via the uplink resources, e.g., based on (e.g., in response to) one or more configuration parameters including / indicating the parameters for the uplink resource group (or uplink resources), and based on at least one TCI state.

[0258] The control message may indicate activation of a TCI state. A subset of the multiple TCI states may include the TCI state. The number of TCI states activated / indicated by the control message may be equal to 1. The control message may indicate activation of a single / one TCI state.

[0259] A control message (e.g., DCI) may include a TCI field indicating a TCI state. One or more TCI codepoints may indicate / include the TCI state. The TCI field may indicate the TCI codepoint.

[0260] The control message may be, for example, an activation command. The at least two TCI states may be a subset of the plurality of TCI states. The one or more TCI codepoints may be (or may include) a single TCI codepoint.

[0261] The TCI state may be / include a joint / common / unified TCI state. The TCI state may be / include a joint / common / unified uplink and downlink TCI state. The TCI state may be / include a joint / common / unified uplink TCI state. The TCI state may be / include an uplink TCI state. The TCI state may be / include a joint / common / unified downlink TCI state. The TCI state may be / include a downlink TCI state.

[0262] In step 1840, the wireless device may transmit (e.g., transmit) an uplink signal (e.g., HARQ-ACK, SR, CSI report, UCI, SRS, etc.) via the uplink resource based on the TCI state indicated by the control message. The wireless device may transmit (e.g., transmit) an uplink signal via the uplink resource based on the TCI state, e.g., regardless of the value of the field. The wireless device may transmit (e.g., transmit) an uplink signal via the uplink resource based on the TCI state, e.g., based on (e.g., in response to) ignoring the value of the field. The wireless device may transmit (e.g., transmit) an uplink signal via the uplink resource based on the TCI state, e.g., based on (e.g., in response to) the control message / command indicating activation of a TCI state. The wireless device may transmit (e.g., transmit) an uplink signal via the uplink resource based on the TCI state, e.g., based on (e.g., in response to) the control message / command indicating activation of a single / one TCI state (and / or based on determining that at least the TCI state is not activated). The wireless device may ignore the value of the field, for example, based on the control message / command indicating activation of a single / one TCI state.

[0263] In step 1845, the base station may receive, via the uplink resources, an uplink signal based on the TCI state indicated by the control message. The base station may receive, via the uplink resources, an uplink signal based on the TCI state, e.g., regardless of the value of the field. The base station may receive, via the uplink resources, an uplink signal based on the TCI state, e.g., based on (e.g., in response to) ignoring the value of the field. The base station may receive, via the uplink resources, an uplink signal based on the TCI state, e.g., based on (e.g., in response to) a control message / command indicating activation of a TCI state. The base station may receive, via the uplink resources, an uplink signal based on the TCI state, e.g., based on (e.g., in response to) a control message / command indicating activation of a single / one TCI state (and / or based on determining that at least the TCI state is not activated). The base station may ignore the value of the field, e.g., based on a control message / command indicating activation of a single / one TCI state.

[0264] The wireless device may apply / use a TCI state for transmission of an uplink signal via an uplink resource. Applying / using at least one TCI state for transmission of an uplink signal via an uplink resource may include transmitting (e.g., transmitting) the uplink signal via the uplink resource using (or based on) a spatial domain transmit filter determined based on a reference signal indicated by the TCI state. Applying / using at least one TCI state for transmission of an uplink signal via the uplink resource may include transmitting (e.g., transmitting) the uplink signal via the uplink resource using (or based on) a transmit power determined based on one or more power control parameters indicated by (or associated with, mapped to, or included in) the TCI state.

[0265] The base station may apply / use the TCI state for reception of the uplink signal via the uplink resource. Applying / using at least one TCI state for reception of the uplink signal via the uplink resource may include receiving the uplink signal via the uplink resource with (or based on) a spatial-domain receive filter determined based on a reference signal indicated by the TCI state.

[0266] The wireless device may transmit (e.g., transmit) an uplink signal via uplink resources in an uplink resource group / set based on (e.g., in response to) one or more configuration parameters including / indicating a parameter for an uplink resource group (or uplink resource) and based on the TCI status. The base station may receive an uplink signal via uplink resources based on (e.g., in response to) one or more configuration parameters including / indicating a parameter for an uplink resource group (or uplink resource).

[0267] The TCI state may be associated with a second value of the field (e.g., a unified / common / joint TCI state index field, a TRP index field, a core set pool index field, a PCI index, etc.). One or more configuration parameters may indicate the second value of the field for the TCI state. An activation command indicating activation of a subset of the TCI states may indicate the second value of the field for the TCI state. A control message / command may indicate the second value of the field for the TCI state.

[0268] The wireless device may pause / stop / abort transmission of an uplink signal (e.g., HARQ-ACK, SR, CSI report, UCI, SRS, etc.) over the uplink resource. The wireless device may pause / stop / abort transmission of an uplink signal over the uplink resource based, for example, on a second value of a field of (or associated with) the TCI status being different (or not equal) to a value of a field of the uplink resource (or uplink resource set / group).

[0269] The wireless device may transmit (e.g., transmit) an uplink signal over the uplink resource based on the TCI status, e.g., based on (e.g., in response to) a second value of a field of (or associated with) the TCI status being the same as (or equal to) a value of a field of the uplink resource (or uplink resource set / group).

[0270] Figures 19A and 19B show examples of uplink transmission / reception. Figures 20A and 20B show examples of methods of uplink transmission and reception, respectively. Figure 21 shows an exemplary method of uplink transmission.

[0271] The one or more configuration parameters may include a parameter (e.g., ConfiguredGrantConfig) indicating a configured uplink grant. The configured uplink grant may be, for example, a type 1 configured uplink grant. The configured uplink grant may be, for example, a type 2 configured uplink grant.

[0272] The one or more configuration parameters may indicate at least two power control fields / parameters / values ​​(e.g., p0-PUSCH-Alpha) for the configured uplink grant. The at least two power control fields / parameters / values ​​may / can include at least two target received power fields / parameters / values. The at least two power control fields / parameters / values ​​may / can include at least two path loss compensation factor fields / parameters / values ​​(e.g., p0-PUSCH-Alpha). The at least two power control fields / parameters / values ​​may / can include at least two path loss reference signals (e.g., pathlossReferenceIndex). The at least two power control fields / parameters / values ​​may / can include at least two closed loop index / values / fields (e.g., powerControlLoopToUse).

[0273] In FIG. 20, in step 2010, the wireless device may receive one or more configuration parameters. In step 2005, the base station may transmit (e.g., transmit) one or more configuration parameters. The one or more configuration parameters may indicate at least two SRS resource indicator (SRI) fields for the configured uplink grant. The one or more configuration parameters may indicate at least two precodingAndNumberOfLayers fields for the configured uplink grant. The one or more configuration parameters (e.g., as discussed in FIG. 17) may indicate at least two SRS resource set lists. The at least two SRS resource set lists may include a first SRS resource set list (e.g., the first SRS resource set list of FIG. 19A and FIG. 19B) and a second SRS resource set list (e.g., the second SRS resource set list of FIG. 19A and FIG. 19B).

[0274] The one or more configuration parameters may include a first SRS parameter indicating a first SRS resource set list (e.g., srs-ResourceSetToAddModList) and a second SRS parameter indicating a second SRS resource set list (e.g., srs-ResourceSetToAddModListDCI-0-2).

[0275] In FIG. 19A, the first SRS resource set list may include an SRS resource set. The first SRS resource set list may include a single / one SRS resource set. The number of SRS resource sets in the first SRS resource set list may be equal to one. In FIG. 19A, the second SRS resource set list may include at least two SRS resource sets. The quantity / number of SRS resource sets in the second SRS resource set list may be two or more. The quantity / number of SRS resource sets in the second SRS resource set list may be equal to two, for example. The at least two SRS resource sets may include a first SRS resource set and a second SRS resource set. In FIG. 20A, in step 2015, the base station may determine a "NO" path. In step 2020, the wireless device may select / determine a "NO" path. The wireless device may select / determine a "NO" path, for example, based on the first SRS resource set list including a single / one SRS resource set. The wireless device may select / determine the "NO" path based on, for example, the first SRS resource set list not including two SRS resource sets (or more than two SRS resource sets).

[0276] The one or more configuration parameters may indicate a use for an SRS resource set in the first SRS resource set list. The one or more configuration parameters may include a use parameter (e.g., use) that indicates a use for the SRS resource set. The use may be set to "codebook", for example. The use may be set to "non-codebook", for example.

[0277] The one or more configuration parameters may indicate a usage state for the first SRS resource set in the second SRS resource set list. The one or more configuration parameters may include a usage parameter (e.g., usage) indicating a usage for the first SRS resource set. The usage may be set to "codebook", for example. The usage may be set to "non-codebook", for example.

[0278] The one or more configuration parameters may indicate a use for the second SRS resource set in the second SRS resource set list. The one or more configuration parameters may include a use parameter (e.g., use) indicating a use for the second SRS resource set. The use may be set to "codebook", for example. The use may be set to "non-codebook", for example.

[0279] The one or more configuration parameters may indicate a first SRS resource set index / indicator / identifier (e.g., srs-ResourceSetId) for a first SRS resource set. The one or more configuration parameters may indicate a second SRS resource set index / indicator / identifier for a second SRS resource set. The first SRS resource set index / indicator / identifier may be lower than the second SRS resource set index / indicator / identifier.

[0280] The SRS resource set in the first SRS resource set list may include one or more SRS resources. The first SRS resource set in the second SRS resource set list may include a first number of SRS resources among the one or more SRS resources in the SRS resource set. The one or more configuration parameters may indicate the number of SRS resources (e.g., N_SRS,0_2). For example, the one or more SRS resources in the SRS resource set may include / be {SRS resource 1, SRS resource 2, SRS resource 3, SRS resource 4}. The first SRS resource set in the second SRS resource set list may include {SRS resource 1, SRS resource 2}, for example, if the number of SRS resources is equal to 2. The first SRS resource set in the second SRS resource set list may include {SRS resource 1, SRS resource 2, SRS resource 3}, for example, if the number of SRS resources is equal to 3. The first SRS resource set in the second SRS resource set list may include, for example, {SRS resource 1, SRS resource 2, SRS resource 3, SRS resource 4} when the number of SRS resources is equal to 4. The first SRS resource set in the second SRS resource set list may be, for example, a subset of the SRS resource set in the first SRS resource set list. The SRS resource set in the first SRS resource set list and the first SRS resource set in the second SRS resource set list may be associated. The SRS resource set in the first SRS resource set list and the first SRS resource set in the second SRS resource set list may be associated, for example, based on the first SRS resource set in the second SRS resource set list being a subset of the SRS resource set in the first SRS resource set list.

[0281] The second SRS resource set in the second SRS resource set list may not be a subset of the SRS resource set in the first SRS resource set list, for example. The SRS resource set in the first SRS resource set list and the second SRS resource set in the second SRS resource set list may not be related. The SRS resource set in the first SRS resource set list and the second SRS resource set in the second SRS resource set list may not be related, for example, based on the second SRS resource set in the second SRS resource set list not being a subset of the SRS resource set in the first SRS resource set list.

[0282] In FIG. 20, in step 2010, the wireless device may receive from the base station, which may transmit (e.g., in step 2005), configuration parameters indicating, for example, a first SRS resource set list, a second SRS resource set list, and two SRI fields for the configured uplink grant. In step 2040, the wireless device may transmit (e.g., transmit) at least one transport block (or PUSCH transmission) based on the at least two SRS resource sets of the second SRS resource set list for the configured uplink grant. In step 2045, the base station may receive at least one transport block based on the at least two SRS resource sets of the second SRS resource set list for the configured uplink grant. The wireless device may transmit (e.g., transmit) at least one transport block based on the first SRS resource set in / from the second SRS resource set list and the second SRS resource set in / from the second SRS resource set list for the configured uplink grant.

[0283] The wireless device may transmit (e.g., transmit) at least one transport block based on at least two SRS resource sets of the second SRS resource set list for the configured uplink grant, e.g., based on (e.g., in response to) one or more configuration parameters indicating at least two power control fields / parameters / values ​​(e.g., p0-PUSCH-Alpha, pathlossReferenceIndex, powerControlLoopToUse) for the configured uplink grant. The wireless device may transmit (e.g., transmit) at least one transport block based on at least two SRS resource sets of the second SRS resource set list for the configured uplink grant, e.g., based on (e.g., in response to) one or more configuration parameters indicating at least two SRI fields for the configured uplink grant. The wireless device may transmit (e.g., transmit) at least one transport block based on at least two SRS resource sets of the second SRS resource set list for the configured uplink grant, e.g., based on (e.g., in response to) one or more configuration parameters indicating at least two precodingAndNumberOfLayers fields for the configured uplink grant.

[0284] The wireless device may transmit (e.g., transmit) at least one transport block based on at least two SRS resource sets of a second SRS resource set list for a configured uplink grant, e.g., based on (e.g., in response to) the first SRS resource set list including a single / one SRS resource set. The wireless device may transmit (e.g., transmit) at least one transport block based on at least two SRS resource sets of a second SRS resource set list for a configured uplink grant, e.g., based on (e.g., in response to) one or more configuration parameters indicating a single / one SRS resource set for the first SRS resource set list.

[0285] The wireless device may transmit (e.g., transmit) at least one transport block based on at least two SRS resource sets of the second SRS resource set list, for a configured uplink grant, e.g., based on (e.g., in response to) the second SRS resource set list including two or more SRS resource sets (or including two SRS resource sets). The wireless device may transmit (e.g., transmit) at least one transport block based on at least two SRS resource sets of the second SRS resource set list, for a configured uplink grant, e.g., based on (e.g., in response to) one or more configuration parameters indicating two or more SRS resource sets (or including two SRS resource sets) for the second SRS resource set list. The wireless device may transmit (e.g., transmit) at least one transport block based on at least two SRS resource sets of the second SRS resource set list, for a configured uplink grant, e.g., based on (e.g., in response to) one or more configuration parameters indicating at least two SRS resource sets for the second SRS resource set list.

[0286] The wireless device may transmit (e.g., transmit) one or more first repetitions of at least one transport block based on a first SRS resource set of the second SRS resource set list. The wireless device may transmit (e.g., transmit) one or more first repetitions of the transport block using a first spatial domain transmit / transmit filter / beam. The wireless device may determine a first spatial domain transmit / transmit filter / beam based on a first SRS resource in the first SRS resource set. A first SRI field of the at least two SRI fields may indicate a first SRS resource. The quantity / number of SRS resources in the first SRS resource set may be greater than one. The quantity / number of SRS resources in the first SRS resource set may be equal to one. The first SRS resource set may not include a second SRS resource that is different from the first SRS resource.

[0287] The wireless device may transmit (e.g., transmit) one or more second repetitions of the at least one transport block based on a second SRS resource set in the second SRS resource set list. The wireless device may transmit (e.g., transmit) one or more second repetitions of the transport block using a second spatial domain transmit / transmit filter / beam. The wireless device may determine a second spatial domain transmit / transmit filter / beam based on a second SRS resource in the second SRS resource set. A second SRI field of the at least two SRI fields may indicate a second SRS resource. The number of SRS resources in the second SRS resource set may be greater than one. The number of SRS resources in the second SRS resource set may be equal to one. The second SRS resource set may not include SRS resources that are different from the second SRS resource.

[0288] In FIG. 21, in step 2110, the wireless device may receive, for example, from a base station, configuration parameters indicating a first SRS resource set list, a second SRS resource set list. The second SRS resource set list may include two SRS resource sets. In step 2120, the wireless device may receive an activation command (e.g., MAC-CE, DCI, SRS Path Loss Reference RS Update MAC CE) indicating activation / update of a path loss reference signal for an SRS resource set in the first SRS resource set list. The one or more configuration parameters may indicate a plurality of path loss reference signals (e.g., indicated by higher layer / RRC parameter pathlossReferenceRSList) including the path loss reference signal for the SRS resource set. The activation command may include a first field including an SRS resource set index for the SRS resource set. The one or more configuration parameters may indicate an SRS resource set index for the SRS resource set. The activation command may include a second field indicating a path loss reference signal. The second field may include a path loss reference RS index indicating / including / identifying the path loss reference signal.

[0289] In step 2130, the wireless device may apply / use a path loss reference signal to / for the SRS resource set. The wireless device may apply / use a path loss reference signal to / for each SRS resource of the SRS resource set. Applying the path loss reference signal to the SRS resource set may include transmitting (e.g., transmitting) the SRS via the SRS resources in the SRS resource set at a transmit power determined based on the path loss reference signal. The wireless device may transmit (e.g., transmit) the SRS via the SRS resources in the SRS resource set at a transmit power determined based on the path loss reference signal. The wireless device may transmit (e.g., transmit) the SRS via each SRS resource of the SRS resource set at a respective transmit power determined based on the path loss reference signal. For example, the wireless device may transmit (e.g., transmit) a first SRS via a first SRS resource in the SRS resource set at a first transmit power determined based on the path loss reference signal. The wireless device may transmit (e.g., transmit) a second SRS via a second SRS resource in the SRS resource set at a second transmit power determined based on the path loss reference signal.

[0290] The wireless device may apply / use a path loss reference signal to / for a first SRS resource set of the second SRS resource set list. The wireless device may apply / use a path loss reference signal for each SRS resource of the first SRS resource set. Applying the path loss reference signal to the first SRS resource set may include transmitting (e.g., transmitting) the SRS via the SRS resources in the first SRS resource set at a transmit power determined based on the path loss reference signal. The wireless device may transmit (e.g., transmit) the SRS via the SRS resources in the first SRS resource set at a transmit power determined based on the path loss reference signal. The wireless device may transmit (e.g., transmit) the SRS via each SRS resource of the first SRS resource set at a respective transmit power determined based on the path loss reference signal. For example, the wireless device may transmit (e.g., transmit) the first SRS via the first SRS resource in the first SRS resource set at a first transmit power determined based on the path loss reference signal. The wireless device may transmit (e.g., transmit) the second SRS via a second SRS resource in the first SRS resource set at a second transmit power determined based on the path loss reference signal. The wireless device may use the path loss reference signal for the first SRS resource set in the second SRS resource set list based, for example, on the SRS resource set in the first SRS resource set list and the first SRS resource set in the second SRS resource set list being associated.

[0291] The wireless device may not apply / use a path loss reference signal to / for the second SRS resource set in the second SRS resource set list. The wireless device may transmit (e.g., transmit) an SRS over SRS resources in the second SRS resource set at a transmit power determined based on the configured / activated path loss reference signal. The one or more configuration parameters may indicate, for example, a configured / activated path loss reference signal for the second SRS resource set. The wireless device may receive, for example, a MAC-CE indicating a configured / activated path loss reference signal for the second SRS resource set. The wireless device may not apply / use a path loss reference signal to / for the second SRS resource set in the second SRS resource set list based, for example, on the SRS resource set in the first SRS resource set list and the second SRS resource set in the second SRS resource set list being unassociated.

[0292] The base station may not transmit (e.g., may not transmit) an activation command (e.g., MAC-CE, DCI, SRS Pathloss Reference RS Update MAC CE) indicating activation / update of a path loss reference signal for a first SRS resource set in a second SRS resource set list. The base station may not transmit (e.g., may not transmit) an activation command (e.g., MAC-CE, DCI, SRS Pathloss Reference RS Update MAC CE) indicating activation / update of a path loss reference signal for a first SRS resource set in a second SRS resource set list, for example, based on one or more configuration parameters indicating a first SRS resource set in / for the first SRS resource set list. The wireless device may / do not expect to receive an activation command (e.g., MAC-CE, DCI, SRS Pathloss Reference RS Update MAC CE) indicating activation / update of a path loss reference signal for a first SRS resource set in a second SRS resource set list. The base station may not send (e.g., may not transmit) an activation command (e.g., MAC-CE, DCI, SRS path loss reference RS update MAC CE) indicating activation / update of the path loss reference signal and including the first SRS resource set index of the first SRS resource set in the second SRS resource set list. The wireless device may not expect / receive an activation command (e.g., MAC-CE, DCI, SRS path loss reference RS update MAC CE) indicating activation / update of the path loss reference signal and including the first SRS resource set index of the first SRS resource set in the second SRS resource set list.

[0293] The wireless device may receive an activation command (e.g., MAC-CE, DCI, SRS Path Loss Reference RS Update MAC CE) indicating activation / update of a path loss reference signal for a second SRS resource set in a second SRS resource set list. The one or more configuration parameters may indicate a plurality of path loss reference signals (e.g., indicated by a higher layer / RRC parameter pathlossReferenceRSList) including the path loss reference signal for the second SRS resource set. The activation command may include a first field including a second SRS resource set index for the second SRS resource set. The one or more configuration parameters may indicate the second SRS resource set index for the second SRS resource set. The activation command may include a second field indicating a path loss reference signal. The second field may include a path loss reference RS index indicating / including / identifying the path loss reference signal. The wireless device may receive an activation command indicating activation / update of a path loss reference signal for a second SRS resource set in a second SRS resource set list, for example, based on one or more configuration parameters not indicating the second SRS resource set in / for the first SRS resource set list. The wireless device may receive an activation command indicating activation / update of a path loss reference signal for a second SRS resource set in a second SRS resource set list, for example, based on one or more configuration parameters indicating a single / single SRS resource set in / for the first SRS resource set list. The base station may send (e.g., transmit) an activation command indicating activation / update of a path loss reference signal for a second SRS resource set in a second SRS resource set list, for example, based on one or more configuration parameters not indicating the second SRS resource set in / for the first SRS resource set list.The base station may, for example, send (e.g., transmit) an activation command indicating activation / update of a path loss reference signal for a second SRS resource set in a second SRS resource set list based on one or more configuration parameters indicating a single / one SRS resource set in / for a first SRS resource set list, and the wireless device may apply / use a path loss reference signal to / for the second SRS resource set.

[0294] In FIG. 19B, the first SRS resource set list may include at least two SRS resource sets. The quantity / number of SRS resource sets in the first SRS resource set list may be equal to or greater than two. The quantity / number of SRS resource sets in the first SRS resource set list may be equal to, for example, two. The at least two SRS resource sets may include a first SRS resource set and a second SRS resource set. In FIG. 19B, the second SRS resource set list may include at least two SRS resource sets. The number of SRS resource sets in the second SRS resource set list may be equal to or greater than two. The number of SRS resource sets in the second SRS resource set list may be equal to, for example, two. The at least two SRS resource sets may include a first SRS resource set and a second SRS resource set. In FIG. 20, in step 2015, the base station may select / determine a "YES" path. In step 2020, the wireless device may select / determine a "YES" path. The wireless device may select / determine the “YES” path based on, for example, a first SRS resource set list that includes two or more SRS resource sets. The wireless device may select / determine the “YES” path based on, for example, a first SRS resource set list that includes at least two SRS resource sets.

[0295] The one or more configuration parameters may indicate a use for the first SRS resource set in the first SRS resource set list. The one or more configuration parameters may include a use parameter (e.g., use) indicating a use for the first SRS resource set. The use may be set to "codebook", for example. The use may be set to "non-codebook", for example.

[0296] The one or more configuration parameters may indicate a use for the second SRS resource set in the first SRS resource set list. The one or more configuration parameters may include a use parameter (e.g., use) indicating a use for the second SRS resource set. The use may be set to "codebook", for example. The use may be set to "non-codebook", for example.

[0297] The one or more configuration parameters may indicate a usage state for the first SRS resource set in the second SRS resource set list. The one or more configuration parameters may include a usage parameter (e.g., usage) indicating a usage for the first SRS resource set. The usage may be set to "codebook", for example. The usage may be set to "non-codebook", for example.

[0298] The one or more configuration parameters may indicate a use for the second SRS resource set in the second SRS resource set list. The one or more configuration parameters may include a use parameter (e.g., use) indicating a use for the second SRS resource set. The use may be set to "codebook", for example. The use may be set to "non-codebook", for example.

[0299] The one or more configuration parameters may indicate a first SRS resource set index / indicator / identifier (e.g., srs-ResourceSetId) for a first SRS resource set in the first SRS resource set list. The one or more configuration parameters may indicate a second SRS resource set index / indicator / identifier for a second SRS resource set in the first SRS resource set list. The first SRS resource set index / indicator / identifier may be lower than the second SRS resource set index / indicator / identifier.

[0300] The one or more configuration parameters may indicate a first SRS resource set index / indicator / identifier (e.g., srs-ResourceSetId) for a first SRS resource set in the second SRS resource set list. The one or more configuration parameters may indicate a second SRS resource set index / indicator / identifier for a second SRS resource set in the second SRS resource set list. The first SRS resource set index / indicator / identifier may be lower than the second SRS resource set index / indicator / identifier.

[0301] The first SRS resource set in the first SRS resource set list may include one or more SRS resources. The first SRS resource set in the second SRS resource set list may include a first number of SRS resources among the one or more SRS resources in the first SRS resource set of / in the first SRS resource set of the first SRS resource set list. The one or more configuration parameters may indicate the number of SRS resources (e.g., N_SRS,0_2). For example, the one or more SRS resources in the first SRS resource set of the first SRS resource set list may / can include {SRS resource 1, SRS resource 2, SRS resource 3, SRS resource 4}. The first SRS resource set in the second SRS resource set list may include {SRS resource 1, SRS resource 2}, for example, if the number of SRS resources is equal to 2. The first SRS resource set in the second SRS resource set list may include {SRS resource 1, SRS resource 2, SRS resource 3}, for example, if the number of SRS resources is equal to 3. The first SRS resource set in the second SRS resource set list may include, for example, {SRS resource 1, SRS resource 2, SRS resource 3, SRS resource 4} when the number of SRS resources is equal to 4. The first SRS resource set in the second SRS resource set list may be, for example, a subset of the first SRS resource set in the first SRS resource set list. The first SRS resource set in the first SRS resource set list and the first SRS resource set in the second SRS resource set list may be associated. The first SRS resource set in the first SRS resource set list and the first SRS resource set in the second SRS resource set list may be associated, for example, based on the first SRS resource set in the second SRS resource set list being a subset of the first SRS resource set in the first SRS resource set list.

[0302] The second SRS resource set in the first SRS resource set list may include one or more SRS resources. The second SRS resource set in the second SRS resource set list may include a first number of SRS resources among the one or more SRS resources in the second SRS resource set of the first SRS resource set list. The one or more configuration parameters may indicate the number of SRS resources (e.g., N_SRS,0_2). For example, the one or more SRS resources in the second SRS resource set of the first SRS resource set list may / can include {SRS resource 1, SRS resource 2, SRS resource 3, SRS resource 4}. The second SRS resource set in the second SRS resource set list may include {SRS resource 1, SRS resource 2}, for example, if the number of SRS resources is equal to 2. The second SRS resource set in the second SRS resource set list may include {SRS resource 1, SRS resource 2, SRS resource 3}, for example, if the number of SRS resources is equal to 3. The second SRS resource set in the second SRS resource set list may include, for example, {SRS resource 1, SRS resource 2, SRS resource 3, SRS resource 4} when the number of SRS resources is equal to 4. The second SRS resource set in the second SRS resource set list may be, for example, a subset of the second SRS resource set in the first SRS resource set list. The second SRS resource set in the first SRS resource set list and the second SRS resource set in the second SRS resource set list may be associated. The second SRS resource set in the first SRS resource set list and the second SRS resource set in the second SRS resource set list may be associated, for example, based on the second SRS resource set in the second SRS resource set list being a subset of the second SRS resource set in the first SRS resource set list.

[0303] In FIG. 20, in step 2030, the wireless device may transmit (e.g., transmit) at least one transport block (or PUSCH transmission) based on at least two SRS resource sets of the first SRS resource set list for the configured uplink grant. In step 2035, the base station may receive at least one transport block based on at least two SRS resource sets of the first SRS resource set list for the configured grant. The wireless device may transmit (e.g., transmit) at least one transport block based on / its first SRS resource set in the first SRS resource set list and / its second SRS resource set in the first SRS resource set list for the configured uplink grant.

[0304] The wireless device may transmit (e.g., transmit) at least one transport block based on at least two SRS resource sets of the first SRS resource set list for a configured uplink grant, e.g., based on (e.g., in response to) one or more configuration parameters indicating at least two power control fields / parameters / values ​​(e.g., p0-PUSCH-Alpha, pathlossReferenceIndex, powerControlLoopToUse) for the configured uplink grant. The wireless device may transmit (e.g., transmit) at least one transport block based on at least two SRS resource sets of the first SRS resource set list for a configured uplink grant, e.g., based on (e.g., in response to) one or more configuration parameters indicating at least two SRI fields for the configured uplink grant. The wireless device may transmit (e.g., transmit) at least one transport block based on at least two SRS resource sets of the first SRS resource set list for a configured uplink grant, e.g., based on (e.g., in response to) one or more configuration parameters indicating at least two precodingAndNumberOfLayers fields for the configured uplink grant.

[0305] The wireless device may transmit (e.g., transmit) at least one transport block based on at least two SRS resource sets of the first SRS resource set list for a configured uplink grant, e.g., based on (e.g., in response to) the first SRS resource set list including more than one SRS resource set (or including two SRS resource sets). The wireless device may transmit (e.g., transmit) at least one transport block based on at least two SRS resource sets of the first SRS resource set list for a configured uplink grant, e.g., based on (e.g., in response to) one or more configuration parameters indicating more than one SRS resource set (or including two SRS resource sets) for the first SRS resource set list. The wireless device may transmit (e.g., transmit) at least one transport block based on at least two SRS resource sets of the first SRS resource set list for a configured uplink grant, e.g., based on (e.g., in response to) one or more configuration parameters indicating at least two SRS resource sets for the first SRS resource set list.

[0306] The wireless device may transmit (e.g., transmit) one or more first repetitions of at least one transport block based on a first SRS resource set in a first SRS resource set list. The wireless device may transmit (e.g., transmit) one or more first repetitions of at least one transport block using a first spatial domain transmit / transmit filter / beam. The wireless device may determine a first spatial domain transmit / transmit filter / beam based on a first SRS resource in the first SRS resource set. A first SRI field of the at least two SRI fields may indicate a first SRS resource. The quantity / number of SRS resources in the first SRS resource set may be greater than one. The quantity / number of SRS resources in the first SRS resource set may be equal to one. The first SRS resource set may not include a second SRS resource that is different from the first SRS resource.

[0307] The wireless device may transmit (e.g., transmit) one or more second repetitions of the at least one transport block based on a second SRS resource set in the first SRS resource set list. The wireless device may transmit (e.g., transmit) one or more second repetitions of the at least one transport block using a second spatial domain transmit / transmit filter / beam. The wireless device may determine a second spatial domain transmit / transmit filter / beam based on a second SRS resource in the second SRS resource set. A se...

Claims

1. 1. A method comprising: By wireless devices, a first sounding reference signal (SRS) resource set list consisting of a single SRS resource set; A second SRS resource set list associated with downlink control information (DCI) format 2_0; and receiving one or more configuration parameters indicating at least two SRS resource indicator (SRI) fields for a configured uplink grant; and transmitting a physical uplink shared channel (PUSCH) transmission for the configured uplink grant using the at least two SRS resource sets of the second SRS resource set list, based on the first SRS resource set list being configured with a single SRS resource set and based on the second SRS resource set list being configured with at least two SRS resource sets.

2. transmitting the PUSCH transmission using the at least two SRS resource sets of the second SRS resource set list. transmitting at least one transport block in a first transmission using at least one of a first spatial filter or a first precoder indicated by a first SRS resource in a first SRS resource set of the at least two SRS resource sets of the second SRS resource set list; and transmitting the at least one transport block in a second transmission using at least one of a second spatial filter or a second precoder indicated by a second SRS resource in a second SRS resource set of the at least two SRS resource sets of the second SRS resource set list.

3. determining that enhanced mobile broadband (eMBB) data is available for uplink transmission via one or more resources indicated by the single SRS resource set of the first SRS resource set list; determining that Ultra Reliable Low Latency Communication (URLLC) data is repeatedly available for uplink transmission via one or more resources indicated by the at least two SRS resource sets of the second SRS resource set list; The method of any one of claims 1 to 2, wherein the transmitting the PUSCH transmission comprises transmitting the URLLC data in at least one repetition of at least one transport block.

4. The one or more configuration parameters are: a first SRS resource set index for a first SRS resource set of the at least two SRS resource sets; and 4. The method of claim 1, further comprising: indicating a second SRS resource set index for a second SRS resource set of the at least two SRS resource sets; and wherein the first SRS resource set index is smaller than the second SRS resource set index.

5. receiving one or more second configuration parameters indicating that the first SRS resource set list is to be modified to include the at least two SRS resource sets after the transmitting of the PUSCH transmission; 5. The method of claim 1, further comprising: transmitting a second PUSCH transmission for the configured uplink grant based on the first SRS resource set list including the at least two SRS resource sets via one or more resources indicated by the at least two SRS resource sets of the first SRS resource set list.

6. a first SRI field of the at least two SRS resource sets indicating a first SRS resource in a first SRS resource set of the at least two SRS resource sets; The method according to any one of claims 1 to 5, wherein a second SRI field of the at least two SRI fields indicates a second SRS resource in a second SRS resource set of the at least two SRS resource sets.

7. 1. A method comprising: By base station, a first sounding reference signal (SRS) resource set list consisting of a single SRS resource set; A second SRS resource set list associated with downlink control information (DCI) format 2_0; and transmitting one or more configuration parameters indicating at least two SRS resource indicator (SRI) fields for the configured uplink grant; receiving a physical uplink shared channel (PUSCH) transmission for the configured uplink grant using the at least two SRS resource sets of the second SRS resource set list, based on the first SRS resource set list being configured with a single SRS resource set and based on the second SRS resource set list being configured with at least two SRS resource sets.

8. receiving the PUSCH transmission using the at least two SRS resource sets of the second SRS resource set list; receiving at least one transport block in a first reception using a first space indicated by a first SRS resource in a first SRS resource set of the at least two SRS resource sets of the second SRS resource set list; and receiving the at least one transport block in a second reception using a second spatial filter indicated by a second SRS resource in a second SRS resource set of the at least two SRS resource sets of the second SRS resource set list.

9. The one or more configuration parameters are: a first SRS resource set index for a first SRS resource set of the at least two SRS resource sets; and 9. The method according to claim 7, further comprising: indicating a second SRS resource set index for a second SRS resource set of the at least two SRS resource sets; and wherein the first SRS resource set index is smaller than the second SRS resource set index.

10. transmitting one or more second configuration parameters indicating that, after the receiving the PUSCH transmission, the first SRS resource set list is modified to include the at least two SRS resource sets; 10. The method according to claim 7, further comprising: receiving a second PUSH via one or more resources indicated by the at least two SRS resource sets of the first SRS resource set list for the configured grant based on the first SRS resource set list including the at least two SRS resource sets.

11. a first SRI field of the at least two SRS resource sets indicating a first SRS resource in a first SRS resource set of the at least two SRS resource sets; The method according to any one of claims 7 to 10, wherein a second SRI field of the at least two SRI fields indicates a second SRS resource in a second SRS resource set of the at least two SRS resource sets.

12. The first SRS resource set list is indicated by an SRI field of a downlink control information (DCI) using DCI format 0_1; and The method according to any one of claims 7 to 11, wherein the second SRS resource set list is indicated by an SRI field of a DCI using DCI format 0_2.

13. 1. A computing device, comprising: one or more processors; and, when executed by the one or more processors, the computing device: A method according to any one of claims 1 to 6, or A memory storing instructions for carrying out the method of any one of claims 7 to 12.

14. 1. A system comprising: A wireless device configured to perform the method according to any one of claims 1 to 6; A base station configured to perform the method according to any one of claims 7 to 12.

15. At run time, A method according to any one of claims 1 to 6, or A computer readable medium having stored thereon instructions causing the execution of a method according to any one of claims 7 to 12.

Images