Resource grouping for transmission repetition

By configuring multiple TRPs in a wireless communication system to prioritize the repeated sending of higher priority messages and repeating lower priority messages when allowed, the problem of resource waste in the prior art is solved, and communication efficiency and success are improved Receive rate.

CN118947075APending Publication Date: 2024-11-12COMCAST CABLE COMM LLC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380025080.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-01-03
Filing Date
2023-01-03
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

In existing wireless communication systems, higher priority messages and lower priority messages are wasted when resource configuration, resulting in uneffective utilization of resources, affecting communication efficiency and successful reception rate.

Method used

By configuring multiple TRPs in a wireless device to accommodate duplication of messages, priority processing of resource configuration, ensuring duplicate transmission of higher priority messages, and repeating lower priority messages when resources allow, improving resource utilization.

Benefits of technology

It improves the resource efficiency and successful reception rate of wireless communication, ensures reliable transmission of messages, and enhances the overall performance of the communication system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118947075A_ABST
    Figure CN118947075A_ABST
Patent Text Reader

Abstract

A wireless device may be configured with resources to communicate with a base station. At least two transmit and receive points may be used to transmit one or more repetitions using resources such as sounding reference signal (SRS) resources. Based on the availability of the resources, repetition may be prioritized over a single transmission. For example, transmission of information of a lower priority type configured with resources for repetition may be prioritized over transmission of information of a higher priority type configured with resources for only a single transmission, such that increased repetition utilization may be achieved.
Need to check novelty before this filing date? Find Prior Art

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 296,030, filed on January 3, 2022. The above-referenced application is hereby incorporated by reference in its entirety. Background Art

[0002] The wireless device uses a transmission and reception point (TRP) to communicate with the base station. The wireless device is configured with a sounding reference signal (SRS) resource to communicate using the TRP. Summary of the invention

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

[0004] The wireless device may be configured with resources to communicate with the base station. For example, the wireless device may use time / frequency resources such as SRS resources 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, the wireless device may include a certain number of components (e.g., TRPs) that may be configured with a corresponding amount of time / frequency resources (e.g., SRS resource sets), which may enable the wireless device to transmit repetitions of messages, which may increase the likelihood of successfully receiving the message. However, for example, if the second message has a higher priority than the first message and is configured so that there are not enough resources for repetition, repetition of the first message may not be possible. For example, at least some time / frequency resources may be grouped for a certain type of communication (e.g., one or more SRS resource sets may be grouped in an SRS resource set list), for example, 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 lower priority message has at least two SRS resource sets configured in an SRS resource set list associated with the communication type of the lower priority message, and if a higher priority message has only one SRS resource set configured in an SRS resource set list associated with the communication type of the higher priority message, then repetition may not be possible if the priority level determines which message is sent. Therefore, configured resources may be wasted / unused (e.g., a higher priority message may be sent via one TRP even though the lower priority message may have been sent in repetition via two TRPs). However, as described herein, communications configured with resources (e.g., an SRS resource set list) that can accommodate repetitions of a message via multiple components (e.g., multiple TRPs) can take precedence over the priority level of the message type, which can increase use of repetitions, and which in turn can provide advantages such as increased efficiency of the configured resources and / or an increased likelihood of successfully receiving 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 limitation in the accompanying drawings. Like reference numerals in the drawings refer to like elements.

[0007] 1A and 1B illustrate exemplary communication networks.

[0008] FIG. 2A illustrates an exemplary user plane.

[0009] FIG. 2B illustrates an exemplary control plane configuration.

[0010] FIG. 3 shows an example of protocol layers.

[0011] FIG. 4A illustrates an exemplary downlink data flow for user plane configuration.

[0012] 4B shows an exemplary format of a media access control (MAC) subheader in a MAC protocol data unit (PDU).

[0013] FIG. 5A shows an exemplary mapping of downlink channels.

[0014] FIG5B shows an exemplary mapping of uplink channels.

[0015] FIG6 illustrates exemplary radio resource control (RRC) states and RRC state transitions.

[0016] FIG. 7 shows an exemplary configuration of a frame.

[0017] FIG. 8 shows an exemplary resource configuration for one or more carriers.

[0018] FIG. 9 shows an exemplary configuration of a bandwidth part (BWP).

[0019] FIG. 10A shows an exemplary component carrier based carrier aggregation configuration.

[0020] FIG. 10B shows an exemplary cell group.

[0021] FIG. 11A illustrates an example mapping of one or more synchronization signal / physical broadcast channel (SS / PBCH) blocks.

[0022] FIG. 11B shows an example mapping of one or more channel state information reference signals (CSI-RS).

[0023] FIG. 12A shows an example of a downlink beam management procedure.

[0024] FIG12B shows an example of an uplink beam management procedure.

[0025] FIG. 13A illustrates an exemplary four-step random access procedure.

[0026] FIG. 13B illustrates an exemplary two-step random access procedure.

[0027] FIG. 13C illustrates an exemplary two-step random access procedure.

[0028] FIG. 14A shows an example of a control resource set (CORESET) configuration.

[0029] FIG. 14B shows an example of control channel element to resource element group (CCE to REG) mapping.

[0030] FIG. 15A shows an example of communication between a wireless device and a base station.

[0031] FIG. 15B illustrates exemplary elements of a computing device that may be used to implement any of the various devices described herein.

[0032] 16A , 16B, 16C, and 16D illustrate examples of uplink and downlink signal transmission.

[0033] FIG. 17 illustrates an exemplary TCI status update.

[0034] 18A and 18B illustrate an exemplary method of unified beam updating.

[0035] 19A and 19B show examples of uplink transmission / reception.

[0036] Fig. 20A and FIG. 20B illustrate an exemplary method of uplink transmission and reception.

[0037] FIG. 21 illustrates an exemplary method for uplink transmission. DETAILED DESCRIPTION

[0038] The drawings and description provide examples. It should be understood that the examples shown and / or described in the drawings are non-exclusive and that the features shown and described may be practiced in other examples. Examples of operations of wireless communication systems that may be used in the field of multi-carrier communication systems are provided. More specifically, the technology disclosed herein may relate to wireless communication exposure detection and / or reporting.

[0039] FIG. 1A shows an exemplary communication network 100. The communication network 100 may include a mobile communication network. The communication network 100 may include, for example, a public land mobile network (PLMN) operated / managed / 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 one or more data networks (DNs) 108, and / or devices within the communication network 100 may communicate with (e.g., via CN 102) the one or more data networks. The wireless device 106 may communicate with one or more DNs 108, such as a public DN (e.g., the Internet), a private DN, and / or an operator's internal DN. The wireless device 106 may communicate with one or more DNs 108 via RAN 104 and / or via CN 102. CN 102 may provide / configure one or more interfaces to the wireless device 106 that interface with the one or more DNs 108. As part of the interface functionality, the CN 102 may set up an end-to-end connection between the wireless device 106 and one or more DNs 108, authenticate the wireless device 106, provide / configure charging functionality, etc.

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

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

[0042] 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 the following: a base station, a node, a Node B (NB), an evolved Node B (eNB), a gNB, an ng-eNB, a relay node (e.g., an integrated access and backhaul (IAB) node), a donor node (e.g., a donor eNB, a donor gNB, etc.), an access point (e.g., a Wi-Fi access point), a transmit and receive point (TRP), a computing device, a device capable of wireless communication, or any other device capable of sending 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 a Universal Mobile Telecommunications System (UMTS) and / or a third generation (3G) standard), an evolved Node B (eNB) (e.g., associated with an Evolved Universal Terrestrial Radio Access (E-UTRA) and / or a fourth generation (4G) standard), a remote radio head (RRH), a baseband processing unit coupled to one or more remote radio heads (RRHs), a relay node or relay node for extending the coverage area of ​​a donor node, a next generation evolved Node B (ng-eNB), a second generation Node B (gNB) (e.g., associated with NR and / or a fifth generation (5G) standard), an access point (AP) (e.g., associated with, for example, Wi-Fi or any other suitable wireless communication standard), any other generation of base stations, and / or any combination thereof. A base station may include one or more devices, such as at least one base station central device (e.g., a gNB central unit (gNB-CU)) and at least one base station distributed device (e.g., a gNB distributed unit (gNB-DU)).

[0043] A base station (e.g., in RAN 104) may include one or more groups of antennas for communicating wirelessly with wireless devices 106 (e.g., via an air interface). One or more base stations may include multiple groups (e.g., three groups or any other number of groups) of antennas to respectively control 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) can successfully receive transmissions from a transmitter (e.g., a wireless device transmitter) operating in the cell. One or more cells of a base station (e.g., alone or in combination with other cells) may provide / configure radio coverage to wireless devices 106 over a wide geographic area to support wireless device mobility. A base station including three sectors (e.g., or n sectors, where n represents 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).

[0044] One or more base stations (e.g., in RAN 104) may be implemented as sectored sites with more or less than three sectors. One or more base stations of RAN 104 may be implemented as access points, baseband processing devices / units coupled to several RRHs, and / or repeaters or relay nodes for extending the coverage area of ​​a node (e.g., a donor node). The baseband processing devices / units coupled to the RRHs may be part of a centralized or cloud RAN architecture, for example, in which the baseband processing devices / units may be centralized in a pool of baseband processing devices / units or virtualized. The relay node may amplify and send (e.g., transmit, retransmit, rebroadcast, etc.) a radio signal received from a donor node. The relay node may perform substantially the same / similar functions as a relay node. The relay node may decode a radio signal received from a donor node, for example, to remove noise before amplifying and sending the radio signal.

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

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

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

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

[0049] 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 serve as a gateway between the RAN 154 (e.g., NG-RAN) and one or more DNs 170. The UPF device 158B may perform functions such as: packet routing and forwarding, packet inspection and user plane policy rule enforcement, traffic usage reporting, uplink classification to support routing of traffic flows to one or more DNs 170, quality of service (QoS) processing for the user plane (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink traffic verification), downlink packet buffering, and / or downlink data notification triggering. The UPF device 158B may serve as an anchor point for intra / inter-radio access technology (RAT) mobility, an external protocol (or packet) data unit (PDU) session point interconnecting one or more DNs, and / or a branch 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.

[0050] The AMF device 158A may perform functions such as: non-access stratum (NAS) signaling termination, NAS signaling security, access stratum (AS) security control, CN node inter-signaling for mobility between access networks (e.g., 3GPP access networks and / or non-3GPP networks), idle mode wireless device reachability (e.g., idle mode UE reachability for controlling and performing paging retransmissions), registration area management, intra-system and inter-system mobility support, access authentication, access authorization including roaming rights check, mobility management control (e.g., subscription and policy), network slicing support, and / or session management function (SMF) selection. NAS may refer to functions running between the CN and the wireless device, and AS may refer to functions running between the wireless device and the RAN.

[0051] The CN 152 (e.g., 5G-CN) may include one or more additional network functions that may not be shown in Figure 1B. The CN 152 (e.g., 5G-CN) may include one or more devices that implement at least one of the following: a session management function (SMF), a 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 functions.

[0052] The RAN 154 (e.g., NG-RAN) may communicate with the wireless device 156 via radio communication (e.g., over an air interface). The wireless device 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 gNB 160A and gNB 160B (collectively referred to as gNB 160)) and / or one or more second type base stations (e.g., ng eNBs including ng-eNB 162A and ng-eNB 162B (collectively referred to as ng eNB 162)). The RAN 154 may include one or more of any number of types of base stations. The gNB 160 and ng eNB 162 may be referred to as base stations. The base stations (e.g., gNB 160 and ng gNB 162) may include one or more antennas for communicating wirelessly with the wireless device 156 (e.g., over an air interface). One or more base stations (e.g., gNB 160 and / or ng-eNB 162) may include multiple groups of antennas to control multiple cells (or sectors) respectively. The cells of the base stations (e.g., gNB 160 and ng-eNB 162) may provide radio coverage to wireless devices 156 over a wide geographic area to support wireless device mobility.

[0053] A base station (e.g., gNB 160 and / or ng-eNB 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 a direct physical connection and / or an indirect connection through an underlying transport network (e.g., an Internet Protocol (IP) transport network). A base station (e.g., gNB 160 and / or ng-eNB 162) may communicate with a wireless device 156 via a third interface (e.g., Uu interface). A base station (e.g., gNB 160A) may communicate with a wireless device 156A via a Uu interface. The NG, Xn, and Uu interfaces may be associated with a protocol stack. The protocol stack associated with the interface may be used by the network elements shown in FIG. 1B to exchange data and signaling messages. The protocol stack may include two planes: a user plane and a control plane. Any other number of planes (e.g., in a protocol stack) may be used. The user plane may process data of interest to a user. The control plane may handle signaling messages of interest to network elements.

[0054] 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 and / or connect with UPF 158B of AMF / UPF 158 via an NG user plane (NG-U) interface. The NG-U interface may provide / perform delivery (e.g., non-guaranteed delivery) of user plane PDUs between the base station (e.g., gNB 160A) and the UPF device (e.g., UPF 158B). A base station (e.g., gNB 160A) may communicate and / or connect with an AMF device (e.g., AMF 158A) via an NG control plane (NG-C) interface. The NG-C interface may provide / perform, for example, NG interface management, wireless device context management (e.g., UE context management), wireless device mobility management (e.g., UE mobility management), transmission of NAS messages, paging, PDU session management, configuration transfer, and / or warning message transmission.

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

[0056] The CN 152 (e.g., 5G-CN) can be configured to handle one or more radio accesses (e.g., NR, 4G, and / or any other radio access). The NR network / device (or any first network / device) can also be connected to a 4G core network / device (or any second network / device) in a non-independent mode (e.g., non-independent operation). In non-independent mode / operation, the 4G core network can 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) can be connected to multiple AMF / UPF nodes, for example, to provide redundancy and / or load sharing across multiple AMF / UPF nodes.

[0057] The 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 a protocol stack that the network elements can use to exchange data and signaling messages. The protocol stack may include two planes: a user plane and a control plane. Any other number of planes (e.g., in a protocol stack) may be used. The user plane may process data associated with a user (e.g., data of interest to the user). The control plane may process data associated with one or more network elements (e.g., signaling messages of interest to the network elements).

[0058] The communication network 100 in FIG. 1A and / or the communication network 150 in FIG. 1B may include any quantity / number and / or type of devices, such as computing devices, wireless devices, mobile devices, handsets, tablet computers, laptop computers, Internet of Things (IoT) devices, hotspots, cellular repeaters, computing devices, and / or more generally user equipment (e.g., UE). Although one or more of the above types of devices (e.g., UE, wireless devices, computing devices, etc.) may be referred to herein, 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 mentioned 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). The apparatus, system, and / or method described herein may generally be described as being implemented on one or more devices (e.g., wireless devices, base stations, eNBs, gNBs, computing devices, etc.) in one or more networks, but it should be understood that one or more features and steps may be implemented in any device and / or any network.

[0059] FIG. 2A illustrates an exemplary user plane configuration. The user plane configuration may include, for example, an NR user plane protocol stack. FIG. 2B illustrates an exemplary 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 located between the wireless device 210 and the base station 220. The protocol stacks shown in FIG. 2A and FIG. 2B may be substantially the same or similar to the protocol stack for the Uu interface between the wireless device 156A and the base station 160A shown in, for example, FIG. 1B.

[0060] The user plane configuration (e.g., NR user plane protocol stack) may include multiple layers (e.g., five layers or any other number 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, the physical layers (PHY) 211 and 221 may provide transport services to the higher layers of the protocol stack and may correspond to layer 1 of the open system interconnection (OSI) model. The protocol layers above the PHY 211 may include a media access control layer (MAC) 212, a radio link control layer (RLC) 213, a packet data convergence protocol layer (PDCP) 214, and / or a service data application protocol layer (SDAP) 215. The protocol layers above the PHY 221 may include a media access control layer (MAC) 222, a radio link control layer (RLC) 223, a packet data convergence protocol layer (PDCP) 224, and / or a service data application protocol layer (SDAP) 225. One or more of the four protocol layers above the 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.

[0061] FIG. 3 shows an example of a protocol layer. The protocol layer may include, for example, a protocol layer of an NR user plane protocol stack. One or more services may be provided between the protocol layers. An SDAP (e.g., SDAPs 215 and 225 shown in FIG. 2A and FIG. 3 ) may perform quality of service (QoS) flow processing. A wireless device (e.g., wireless device 106, 156A, 156B, and 210) may receive a service through / via a PDU session, which may be a logical connection between the wireless device and a DN. The PDU session may have one or more QoS flows 310. The UPF (e.g., UPF 158B) of the CN may map IP packets to the one or more QoS flows of the PDU session, for example, based on one or more QoS requirements (e.g., based on delay, data rate, bit error rate, and / or any other quality / service requirements). SDAPs 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 the radio bearers 320 via the reflected mapping and / or control signaling received from the base station 220. For the reflected mapping, the SDAP 225 of the base station 220 may mark the downlink packet with a QoS flow indicator (QFI), which the SDAP 215 of the wireless device 210 may monitor / detect / identify / indicate / observe to determine the mapping / demapping between the one or more QoS flows 310 and the radio bearers 320.

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

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

[0064] The RLC layer (e.g., RLC 213 and 223) can 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) can support multiple transmission modes (e.g., three transmission modes: transparent mode (TM); unacknowledged mode (UM); and acknowledged mode (AM)). The RLC layer can perform one or more of the marked functions, for example, based on the transmission mode in which the RLC layer is operating. The RLC configuration can be for each logical channel. The RLC configuration may not depend on a parameter set and / or a transmission time interval (TTI) duration (or other duration). The RLC layer (e.g., RLC 213 and 223) can provide / configure an RLC channel as a service for the PDCP layer (e.g., PDCP 214 and 224, respectively), as shown in Figure 3.

[0065] 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 may include multiplexing data units / data portions belonging to the one or more logical channels into a transport block (TB) delivered to the PHY layer (e.g., PHY 211 and 221, respectively), and demultiplexing may include demultiplexing data units / data portions from TBs delivered from the PHY layer. The MAC layer (e.g., MAC 222) of the base station may be configured to perform scheduling, scheduling information reporting, and / or priority handling between wireless devices via dynamic scheduling. Scheduling may be performed by a base station (e.g., base station 220 at MAC 222) for 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 the case of carrier aggregation (CA)), and to perform priority handling between logical channels of the wireless device 210 via logical channel prioritization and / or padding. The MAC layer (e.g., MAC 212 and 222) may support one or more parameter sets and / or transmit timings. Mapping restrictions in logical channel prioritization may control the parameter sets and / or transmit timings that may be used by the logical channels. The MAC layer (e.g., MAC 212 and 222) may provide / configure the logical channel 340 as a service to the RLC layer (e.g., RLC 213 and 223).

[0066] The PHY layer (e.g., PHY 211 and 221) may perform mapping of transport channels to physical channels and / or digital and analog signal processing functions, for example, for sending and / or receiving information (e.g., via 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., PHY 211 and 221) may perform multi-antenna mapping. The PHY layer (e.g., PHY 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., MAC 212 and 222, respectively).

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

[0068] For example, if SDAP 225 receives three IP packets (or other number of IP packets) from one or more QoS flows and maps the three packets (or other number of packets) to radio bearers (e.g., radio bearers 402 and 404), the downlink data flow may begin. 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 (marked as "H" before each SDAP SDU shown in FIG. 4A) may be added to the IP packet to generate an SDAP PDU, which may be referred to as a PDCP SDU. A data unit transmitted from / to a higher protocol layer may be referred to as a service data unit (SDU) of a lower protocol layer, and a data unit transmitted to / from a lower protocol layer may be referred to as a protocol data unit (PDU) of a higher protocol layer. As shown in FIG. 4A, a data unit from SDAP 225 may be an SDU (e.g., a PDCP SDU) of a lower protocol layer PDCP 224, and may be a PDU (e.g., an SDAP PDU) of SDAP 225.

[0069] Each protocol layer (e.g., the protocol layers shown in FIG. 4A ) or at least some of the protocol layers may: perform its own functions (e.g., one or more functions of each protocol layer described with respect to FIG. 3 ), add a corresponding header, and / or forward the corresponding output to the next lower layer (e.g., its corresponding lower layer). PDCP 224 may perform IP header compression and / or encryption. PDCP 224 may forward its output (e.g., PDCP PDU, which is RLC SDU) to RLC 223. RLC 223 may optionally perform segmentation (e.g., as shown in IP packet m in FIG. 4A ). RLC 223 may forward its output (e.g., two RLC PDUs, which are two MAC SDUs, generated by adding corresponding subheaders to two SDU segments (SDU segments)) to MAC 222. MAC 222 may multiplex multiple RLC PDUs (MAC SDUs). MAC 222 may attach a MAC subheader to the RLC PDU (MAC SDU) to form a TB. The MAC subheader may be distributed over the MAC PDU (e.g., in a 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). For example, if the MAC PDU subheader is calculated before assembling the complete MAC PDU, the NR MAC PDU structure may reduce processing time and / or associated delays.

[0070] 4B shows an exemplary format of a MAC subheader in a MAC PDU. A MAC PDU may include a MAC subheader (H) and a MAC SDU. Each of the one or more MAC subheaders may include: an SDU length field for indicating the length (e.g., in bytes) of the MAC SDU to which the MAC subheader corresponds; a logical channel identifier (LCID) field for identifying / indicating the logical channel from which the MAC SDU originates to assist in demultiplexing processing; a flag (F) for indicating the size of the SDU length field; and a reserved bit (R) field for future use.

[0071] 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 / added before two MAC PDUs. A MAC CE may be inserted / added at the beginning of a MAC PDU for downlink transmission (as shown in FIG. 4B ). One or more MAC CEs may be inserted / added at the end of a MAC PDU for uplink transmission. MAC CEs may be used for in-band control signaling. Exemplary MAC CEs may include scheduling-related MAC CEs, such as buffer status reports and power headroom reports; activation / deactivation MAC CEs (e.g., activation / deactivation for PDCP duplication detection, channel state information (CSI) reporting, sounding reference signal (SRS) transmission, and MAC CEs of previously 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 having a format similar to that described for the MAC subheader of the MAC SDU, and may be identified with a reserved value in the LCID field indicating the type of control information included in the corresponding MAC CE.

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

[0073] 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 for paging a wireless device whose location is unknown 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). Wireless devices may use system information messages to obtain information about how a 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 to configure the wireless device with configuration information. A Dedicated Traffic Channel (DTCH) may include / carry user data to / from a specific wireless device.

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

[0075] The PHY layer may use physical channels to pass / transmit information between processing layers of the PHY layer. A physical channel may have an associated set of time-frequency resources for carrying information of one or more transport channels. The PHY layer may generate control information to support low-level operations of the PHY layer. The PHY layer may provide / transmit control information to lower layers of the PHY layer via a physical control channel (e.g., referred to as an L1 / L2 control channel). The set of physical channels and physical control channels (e.g., defined by an NR configuration or any other configuration) may include one or more of the following channels. The physical broadcast channel (PBCH) may include / carry 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, and in some cases include uplink control information (UCI) as described below. The physical uplink control channel (PUCCH) may include / carry UCI, which may include HARQ acknowledgment, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and scheduling request (SR). The physical random access channel (PRACH) may be used for random access.

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

[0077] One or more of these channels (e.g., logical channels, transport channels, physical channels, etc.) can be used to perform functions associated with a control plan protocol stack (e.g., an NR control plane protocol stack). FIG. 2B illustrates an exemplary control plane configuration (e.g., an NR control plane protocol stack). As shown in FIG. 2B , the control plane configuration (e.g., an NR control plane protocol stack) can use substantially the same / similar one or more protocol layers (e.g., PHY 211 and 221, MAC 212 and 222, RLC 213 and 223, and PDCP 214 and 224) as an exemplary user plane configuration (e.g., an NR user plane protocol stack). 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 at an upper layer of the control plane configuration (e.g., NR control plane protocol stack), for example, instead of having SDAP 215 and 225. The control plane configuration may include an AMF 230 including a NAS protocol 237.

[0078] The NAS protocols 217 and 237 may provide control plane functions between the wireless device 210 and the AMF 230 (e.g., AMF 158A or any other AMF) and / or more generally between the wireless device 210 and the CN (e.g., 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 referred to as NAS messages. There may be no direct path between the wireless device 210 and the AMF 230 via which NAS messages may be transmitted. NAS messages may be transmitted 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.

[0079] The RRC 216 and 226 may provide / configure control plane functions between the wireless device 210 and the base station 220 and / or more generally between the wireless device 210 and the RAN (e.g., the base station 220). The RRC layers 216 and 226 may provide / configure control plane functions 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 sent / transmitted between the wireless device 210 and the RAN (e.g., the base station 220) using signaling radio bearers and the same / similar PDCP, RLC, MAC, and PHY protocol layers. The MAC layer may multiplex control plane and user plane data into the same TB. The RRC layers 216 and 226 may provide / configure control plane functions, such as one or more of the following functions: broadcast of system information related to AS and NAS; paging initiated by CN or RAN; establishment, maintenance, and release of an RRC connection between the wireless device 210 and the RAN (e.g., base station 220); security functions including key management; establishment, configuration, maintenance, and release of signaling radio bearers and data radio bearers; mobility functions; QoS management functions; wireless device measurement reports (e.g., wireless device measurement reports) and control of reporting; detection of and recovery from radio link failure (RLF); and / or NAS message delivery. As part of establishing an RRC connection, the RRC layers 216 and 226 may establish an RRC context, which may involve configuring communication parameters between the wireless device 210 and the RAN (e.g., base station 220).

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

[0081] An RRC connection may be established for the wireless device. For example, this may occur during an RRC connected state. During the RRC connected state (e.g., during RRC connection 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 be similar to one of the one or more base stations (e.g., one or more base stations of the RAN 104 shown in FIG. 1A, one of the gNB 160 or ng eNB 162 shown in FIG. 1B, the base station 220 shown in FIGS. 2A and 2B, or any other base station). A base station connected to the wireless device (e.g., having established an RRC connection) may have an RRC context for the wireless device. The RRC context may be referred to as a wireless device context (e.g., a UE context) and may include parameters for communication between the wireless device and the base station. These parameters may include, for example, one or more of the following: AS context; radio link configuration parameters; bearer configuration information (e.g., 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 connection 602), the mobility of the wireless device may be managed / controlled by the RAN (e.g., RAN 104 or NG RAN 154). The wireless device may measure the received signal level (e.g., reference signal level, reference signal received power, reference signal quality, received signal strength indicator, etc.) based on one or more signals sent from the serving cell and the neighboring cell. The wireless device may report these measurement results to the serving base station (e.g., the base station currently serving the wireless device). The serving base station of the wireless device may, for example, request a handover to a cell of one of the neighboring base stations based on the reported measurement results. The RRC state may transition from an RRC connected state (e.g., RRC connected 602) to an RRC idle state (e.g., RRC idle 606) via a connection release procedure 608. The RRC state may transition from an RRC connected state (e.g., RRC connected 602) to an RRC inactive state (e.g., RRC inactive state 604) via a connection detachment procedure 610.

[0082] An RRC context may not be established for the wireless device. For example, this may occur during an RRC idle state. During an RRC idle state (e.g., RRC idle 606), an RRC context may not be established for the wireless device. During an RRC idle state (e.g., RRC idle 606), the wireless device may not have an RRC connection with a base station. During an RRC idle state (e.g., RRC idle 606), the wireless device may be in a sleep state most of the time (e.g., to save battery power). The wireless device may periodically wake up (e.g., once in each discontinuous reception (DRX) cycle) to monitor paging messages (e.g., paging messages set from the RAN). The 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.

[0083] A previously established RRC context may be maintained for the wireless device. For example, this may occur during an RRC inactive state. During an RRC inactive state (e.g., RRC inactive state 604), a previously established RRC context may be maintained in the wireless device and the base station. Compared to a transition from an RRC idle state (e.g., RRC idle 606) to an RRC connected state (e.g., RRC connected 602), the maintenance of the RRC context may enable / allow a fast transition to an RRC connected state (e.g., RRC connected 602) with reduced signaling overhead. During an RRC inactive state (e.g., RRC inactive state 604), the wireless device may be 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 state 604) to an RRC connected state (e.g., RRC connected 602) via a connection recovery procedure 614. The RRC state may transition from an RRC inactive state (eg, RRC inactive state 604 ) to an RRC idle state (eg, RRC idle 606 ) via a connection release procedure 616 , which may be the same as or similar to the connection release procedure 608 .

[0084] The RRC state may be associated with a mobility management mechanism. During an RRC idle state (e.g., RRC idle 606) and an RRC inactive state (e.g., RRC inactive state 604), mobility may be managed / controlled by the wireless device via cell reselection. The purpose of mobility management during an RRC idle state (e.g., RRC idle 606) or during an RRC inactive state (e.g., RRC inactive state 604) may be to enable / allow the network to notify the wireless device of an event via a paging message without broadcasting the paging message over the entire mobile communication network. The mobility management mechanism used during an RRC idle state (e.g., RRC idle 606) or during an RRC idle state (e.g., RRC inactive state 604) may enable / allow the network to track the wireless device, for example, at a cell group level, so that a paging message may be broadcast over a cell of a cell group in which the wireless device is currently residing (e.g., instead of sending a paging message over the entire mobile communication network). The mobility management mechanism for the RRC idle state (e.g., RRC idle 606) and the RRC inactive state (e.g., RRC inactive state 604) can track the wireless device at the cell group level. The mobility management mechanism can, for example, use different grouping granularities for tracking. There can be multiple levels of cell grouping granularity (e.g., three levels of cell grouping granularity: a single cell; cells within a RAN area identified by a RAN area identifier (RAI); and cells within a group of RAN areas referred to as a tracking area and identified by a tracking area identifier (TAI)).

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

[0086] The RAN area may be used to track the 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 state 604), a RAN notification area may be assigned / provisioned / configured to the wireless device. The RAN notification area may include one or more cell identities (e.g., RAI list and / or TAI list). A base station may belong to one or more RAN notification areas. A cell may belong to one or more RAN notification areas. The wireless device may perform a notification area update with the RAN to update the RAN notification area of ​​the wireless device, for example, 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.

[0087] A base station storing the RRC context of the wireless device or the last serving base station of the wireless device may be referred to as an anchor base station. The anchor base station may maintain the RRC context of the wireless device at least during a period when the wireless device stays in a RAN notification area of ​​the anchor base station and / or during a period when the wireless device stays in an RRC inactive state (e.g., RRC inactive state 604).

[0088] A base station (e.g., gNB 160 in FIG. 1B or any other base station) may be divided into two parts: a central unit (e.g., a base station central unit such as a gNB CU) and one or more distributed units (e.g., base station distributed units such as gNBDUs). 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 an NR configuration). The base station CU may include RRC, PDCP, and SDAP layers. The base station distributed unit (DU) may include RLC, MAC, and PHY layers.

[0089] Physical signals and physical channels (e.g., as described with respect to FIG. 5A and FIG. 5B ) can be mapped to one or more symbols (e.g., orthogonal frequency division multiplexing (OFDM) symbols in an NR configuration or any other symbol). OFDM is a multi-carrier communication scheme that sends / transmits data through F orthogonal subcarriers (or carriers). The data can be mapped to a series of complex symbols (e.g., M orthogonal amplitude modulation (M-QAM) symbols or M phase shift keying (M-PSK) symbols or any other modulated symbols) referred to as source symbols, and divided into F parallel symbol streams, for example, before data transmission. The F parallel symbol streams can be viewed as if they were in the frequency domain. The F parallel symbols can be used as input to an inverse fast Fourier transform (IFFT) block that transforms them into the time domain. The IFFT block can receive F source symbols at a time, receiving one source symbol from each of the F parallel symbol streams. The IFFT block can 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 the sum of 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 sent / transmitted over the air interface at a carrier frequency, for example, after one or more processes (e.g., adding a cyclic prefix) and up-conversion. For example, a Fast Fourier Transform (FFT) block may be used to mix the F parallel symbol streams before being processed by the IFFT block. This operation may produce a discrete Fourier transform (DFT) precoded OFDM symbol and may be used by one or more wireless devices in the uplink to reduce the peak-to-average power ratio (PAPR). The FFT block may be used at the receiver to perform inverse processing on the OFDM symbol to recover the data mapped to the source symbol.

[0090] FIG. 7 shows an exemplary configuration of a frame. The frame may include, for example, an NR radio frame into which OFDM symbols may be grouped. A frame (e.g., an NR radio frame) may be identified / indicated by a system frame number (SFN) or any other value. The SFN may be repeated in a period of 1024 frames. The duration of an NR frame may be 10 milliseconds (ms) and may include 10 subframes of duration 1 ms. The subframe may be divided into one or more time slots (e.g., depending on a parameter set and / or different subcarrier spacings). Each of the one or more time slots may include, for example, 14 OFDM symbols per time slot. Any number of symbols, time slots, or durations may be used for any time interval.

[0091] The duration of a slot may depend on a parameter set for the OFDM symbol used for the slot. For example, flexible parameter sets may be supported to accommodate different deployments (e.g., cells with carrier frequencies below 1 GHz to cells with carrier frequencies in the millimeter wave range). For example, in an NR configuration or any other radio configuration, flexible parameter sets may be supported. The parameter set may be defined based on subcarrier spacing and / or cyclic prefix duration. The subcarrier spacing may be increased in proportion to a power of two from a baseline subcarrier spacing of 15 kHz. For example, for a parameter set in an NR configuration or any other radio configuration, the cyclic prefix duration may be decreased in proportion to a power of two from a baseline cyclic prefix duration of 4.7 μs. The parameter set may be defined with the following subcarrier spacing / cyclic prefix duration combinations: 15 kHz / 4.7 μs; 30 kHz / 2.3 μs; 60 kHz / 1.2 μs; 120 kHz / 0.59 μs; 240 kHz / 0.29 μs, and / or any other subcarrier spacing / cyclic prefix duration combination.

[0092] A slot may have a fixed number / quantity of OFDM symbols (e.g., 14 OFDM symbols). Parameter sets with higher subcarrier spacing may have shorter slot durations and more slots per subframe. An example of a parameter set-dependent slot duration and a per-subframe slot transmission structure is shown in FIG7 (a parameter set with 240 kHz subcarrier spacing is not shown in FIG7). A subframe (e.g., in an NR configuration) may be used as a parameter set-independent time reference. A slot may be used as a unit for scheduling uplink and downlink transmissions. Scheduling (e.g., in an NR configuration) may be decoupled from the slot duration. Scheduling may start at any OFDM symbol. Scheduling may last as many symbols as required for the transmission, e.g., to support low latency. These partial slot transmissions may be referred to as microslots or subslot transmissions.

[0093] FIG8 shows an exemplary resource configuration for one or more carriers. The resource configuration may include a slot in the time domain and the frequency domain for an NR carrier or any other carrier. The slot may include a resource element (RE) and a resource block (RB). A resource element (RE) may be the smallest physical resource (e.g., in an NR configuration). An RE may span one OFDM symbol in the time domain through one subcarrier in the frequency domain, as shown in FIG8. An RB may span twelve consecutive REs in the frequency domain, as shown in FIG8. A carrier (e.g., an NR carrier) may be limited to a certain number of RBs and / or subcarrier widths (e.g., 275 RBs or 275×12=3300 subcarriers). If such a restriction is used, the carrier (e.g., NR carrier) frequency may be limited based on the subcarrier spacing (e.g., for subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, and 120 kHz, the carrier frequencies are 50 MHz, 100 MHz, 200 MHz, and 400 MHz, respectively). A 400 MHz bandwidth may be set based on a 400 MHz bandwidth restriction per carrier. Any additional bandwidth may be set based on the per-carrier bandwidth limit.

[0094] A single parameter set may be used over the entire bandwidth of a carrier (e.g., such as NR shown in FIG8 ). In other exemplary configurations, multiple parameter sets may be supported on the same carrier. NR and / or other access technologies may support wide carrier bandwidths (e.g., up to 400 MHz for a subcarrier spacing of 120 kHz). Not all wireless devices may be able to receive the full carrier bandwidth (e.g., due to hardware limitations and / or different wireless device capabilities). For example, receiving and / or utilizing the full carrier bandwidth may be prohibited depending on wireless device power consumption. The wireless device may, for example, adjust the size of the wireless device's receive bandwidth based on the amount of traffic the wireless device is scheduled to receive (e.g., to reduce power consumption and / or other purposes). Such adaptation may be referred to as bandwidth adaptation.

[0095] Configuration of one or more bandwidth parts (BWPs) may support one or more wireless devices that are not capable of receiving the full carrier bandwidth. The BWP may support bandwidth adaptation, for example, for such wireless devices that are not capable of receiving 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 an 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 configured BWPs of 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. For example, if a serving cell is configured with a secondary uplink carrier, the serving cell may have one or more first active BWPs in the uplink carrier and one or more second active BWPs in the secondary uplink carrier.

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

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

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

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

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

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

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

[0103] Downlink BWP switching may refer to switching the active downlink BWP from a first downlink BWP to a second downlink BWP (e.g., activating the second downlink BWP, deactivating the first downlink BWP). Uplink BWP switching may refer to switching the active uplink BWP from a first uplink BWP to a second uplink BWP (e.g., activating the second uplink BWP, deactivating the first uplink BWP). Downlink and uplink BWP switching may be performed independently (e.g., in one or more paired spectrums). Downlink and uplink BWP switching may be performed simultaneously (e.g., in one or more unpaired spectrums). Switching between configured BWPs may occur, for example, based on RRC signaling, DCI signaling, expiration of a BWP inactivity timer, and / or the initiation of a random access.

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

[0105] The wireless device procedures for switching BWP on the secondary cell may be the same / similar to those on the primary cell, for example, if the wireless device is configured for a secondary cell with a default downlink BWP and timer value in a set of configured downlink BWPs. The wireless device can use the timer value and the default downlink BWP for the secondary cell in the same / similar manner as the wireless device uses the timer value and / or default BWP for the primary cell. The timer value (e.g., BWP inactivity timer) may be configured for each 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 the expiration of the BWP inactivity timer.

[0106] Two or more carriers may be aggregated, and carrier aggregation (CA) may be used to simultaneously send / transmit data to / from the same wireless device (e.g., to increase data rates). Aggregated carriers in CA may be referred to as component carriers (CCs). For example, if CA is configured / used, there may be a certain number / amount of serving cells for wireless devices (e.g., one serving cell for a CC). A CC may have multiple configurations in the frequency domain.

[0107] FIG10A shows an exemplary CC-based CA configuration. As shown in FIG10A , three types of CA configurations may include an intra-band (contiguous) configuration 1002, an intra-band (non-contiguous) configuration 1004, and / or an inter-band configuration 1006. In the intra-band (contiguous) configuration 1002, two CCs may be aggregated in the same frequency band (Band A) and may be 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 (Band A), but may be spaced apart from each other in the frequency band by a certain gap. In the inter-band configuration 1006, two CCs may be located in different frequency bands (e.g., Band A and Band B, respectively).

[0108] The network may set the maximum number of CCs that can be aggregated (e.g., up to 32 CCs may be aggregated in NR, or any other number may be aggregated in other systems). Aggregated CCs may have the same or different bandwidth, subcarrier spacing, and / or duplex scheme (TDD, FDD, or any other duplex 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, if the wireless device has more data traffic in the downlink than in the uplink.

[0109] One of the aggregated cells for a wireless device may be referred to as a primary cell (PCell), for example, if CA is configured. PCell may be a serving cell for wireless initial connection or access, for example, during or at the time of RRC connection establishment, RRC connection reestablishment, and / or handover. PCell may provide / configure NAS mobility information and security input to the wireless device. The wireless device may have different PCells. For the downlink, the carrier corresponding to PCell may be referred to as a downlink primary CC (DL PCC). For the uplink, the carrier corresponding to PCell may be referred to as an uplink primary CC (UL PCC). Other aggregated cells for wireless devices (e.g., associated with CCs other than DL PCC and UL PCC) may be referred to as secondary cells (SCells). For example, SCell may be configured after PCell is configured for the wireless device. SCell may be configured via an RRC connection reconfiguration procedure. For the downlink, the carrier corresponding to SCell may be referred to as a downlink secondary CC (DL SCC). For the uplink, the carrier corresponding to SCell may be referred to as an uplink secondary CC (UL SCC).

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

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

[0112] FIG. 10B shows an exemplary cell group. The aggregated cell 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 include one or more downlink CCs, respectively. PUCCH group 1010 may include one or more downlink CCs, for example, three downlink CCs: PCell 1011 (e.g., DL PCC), SCell 1012 (e.g., DL SCC), and SCell 1013 (e.g., DL SCC). PUCCH group 1050 may include one or more downlink CCs, for example, three downlink CCs: PUCCH SCell (or PSCell) 1051 (e.g., DL SCC), SCell 1052 (e.g., DL SCC), and SCell 1053 (e.g., DL SCC). One or more uplink CCs of the PUCCH group 1010 may be configured as PCell 1021 (e.g., UL PCC), SCell 1022 (e.g., UL SCC), and SCell 1023 (e.g., UL SCC). One or more uplink CCs of the PUCCH group 1050 may be configured as PUCCH SCell (or PSCell) 1061 (e.g., UL SCC), SCell 1062 (e.g., UL SCC), and SCell 1063 (e.g., UL SCC). UCI related to the downlink CCs of the PUCCH group 1010 may be sent / transmitted via the uplink of the PCell 1021 (e.g., via the PUCCH of the PCell 1021), shown as UCI 1031, UCI 1032, and UCI 1033. UCI associated with the downlink CCs of the PUCCH group 1050 may be sent / transmitted via the uplink of the PUCCH SCell (or PSCell) 1061 (e.g., via the PUCCH of the PUCCH SCell 1061), shown as UCI 1071, UCI 1072, and UCI 1073. For example, if the aggregated cell shown in FIG. 10B is not divided into the PUCCH group 1010 and the PUCCH group 1050, a single uplink PCell may be configured to send / transmit UCI associated with six downlink CCs. For example, if UCI 1031, 1032, 1033, 1071, 1072, and 1073 are sent / transmitted via the PCell 1021, the PCell 1021 may become overloaded. By dividing the transmission of UCI between the PCell 1021 and the PUCCH SCell (or PSCell) 1061, overload may be prevented and / or reduced.

[0113] A PCell may include a downlink carrier (e.g., PCell 1011) and an uplink carrier (e.g., PCell 1021). An SCell may include only a downlink carrier. A physical cell ID and a cell index may be assigned to a cell including a downlink carrier and optionally an uplink carrier. The physical cell ID or 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. For example, a synchronization signal (e.g., PSS and / or SSS) sent / transmitted via a downlink component carrier may be used to determine the physical cell ID. The cell index may be determined, for example, using one or more RRC messages. The physical cell ID may be referred to as a carrier ID, and the cell index may be referred to as a carrier index. A first physical cell ID for a first downlink carrier may refer to a first physical cell ID of a cell including the first downlink carrier. Substantially the same / similar concepts may be applied, for example, to carrier activation. Activation of a first carrier may refer to activation of a cell including the first carrier.

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

[0115] For the downlink, the base station may send / 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, the one or more wireless devices may send / transmit one or more RS (e.g., DM-RS, PT-RS, and / or SRS) to the base station. The PSS and SSS may be sent / transmitted by the base station and used by the one or more wireless devices to synchronize the one or more wireless devices with the base station. A synchronization signal (SS) / physical broadcast channel (PBCH) block may include the PSS, SSS, and PBCH. The base station may periodically send / transmit a burst of SS / PBCH blocks, which may be referred to as an SSB.

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

[0117] The SS / PBCH block may span one or more OFDM symbols in the time domain (e.g., 4 OFDM symbols, as shown in FIG. 11A or any other quantity / number of symbols), and may span one or more subcarriers in the frequency domain (e.g., 240 consecutive subcarriers or any other quantity / number of subcarriers). The PSS, SSS, and PBCH may have a common center frequency. The PSS may be sent / transmitted first and may span, for example, 1 OFDM symbol and 127 subcarriers. The SSS may be sent / transmitted after the PSS (e.g., two symbols later) and may span 1 OFDM symbol and 127 subcarriers. The PBCH may be sent / transmitted after the PSS (e.g., across the next 3 OFDM symbols) and may span 240 subcarriers (e.g., in the second OFDM symbol and the fourth OFDM symbol 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).

[0118] The wireless device may not know the location of the SS / PBCH block in the time domain and the frequency domain (e.g., if the wireless device is searching for a cell). For example, the wireless device may monitor the carrier of the PSS to find and select a cell. The wireless device may monitor the frequency location within the carrier. For example, if the PSS is not found after a certain duration (e.g., 20 ms), the wireless device may search for the PSS at different frequency locations within the carrier. The wireless device may search for the PSS at different frequency locations within the carrier, for example, as indicated by a synchronization raster. If the PSS is found at a location in the time domain and the frequency domain, the wireless device may determine the location of the SSS and the PBCH, respectively, for example based on the known structure of the SS / PBCH block. The SS / PBCH block may be a cell definition SS block (CD-SSB). The primary cell may be associated with the CD-SSB. The CD-SSB may be located on the synchronization raster. Cell selection / search and / or reselection may be based on the CD-SSB.

[0119] The wireless device may use the SS / PBCH block to determine one or more parameters of the cell. The wireless device may determine the physical cell identifier (PCI) of the cell, for example, based on the sequence of the PSS and SSS, respectively. The wireless device may determine the position of the frame boundary of the cell, for example, based on the position of the SS / PBCH block. The SS / PBCH block may indicate that it has been sent / transmitted according to the transmission mode. The SS / PBCH block in the transmission mode may be a known distance from the frame boundary (e.g., a predefined distance configured by the RAN between one or more networks, one or more base stations, and one or more wireless devices).

[0120] The PBCH may use QPSK modulation and / or forward error correction (FEC). The FEC may use polarity coding. One or more symbols spanned by the PBCH may include / carry one or more DM-RS for PBCH demodulation. The PBCH may include an indication of the current system frame number (SFN) of the cell and / or an SS / PBCH block timing index. These parameters may facilitate time synchronization of the wireless device with the base station. The PBCH may include a MIB for sending / transmitting one or more parameters to the wireless device. The wireless device may use the MIB to locate the remaining minimum system information (RMSI) associated with the cell. The RMSI may include a system information block type 1 (SIB1). SIB1 may include information for the wireless device to access the cell. The wireless device may use one or more parameters of the MIB to monitor the PDCCH, which may be used to schedule the PDSCH. The PDSCH may include SIB1. SIB1 may be decoded using parameters provided / included in the MIB. The PBCH may indicate that SIB1 is not present. The wireless device may be directed to a frequency, for example, based on a PBCH indicating that SIB1 is not present. The wireless device may search for SS / PBCH blocks at the frequency to which the wireless device is directed.

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

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

[0123] The CSI-RS may be sent / transmitted by a base station and used by a wireless device to collect / acquire / determine channel state information (CSI). The base station may configure one or more CSI-RS for the wireless device for channel estimation or any other suitable purpose. The base station may configure one or more of the same / similar CSI-RS for the wireless device. The wireless device may measure the one or more CSI-RS. The wireless device may estimate the downlink channel state and / or generate a CSI report based on the measurement results of the one or more downlink CSI-RS, for example. The wireless device may send / transmit a CSI report to the base station (e.g., based on a periodic CSI report, a semi-persistent CSI report, and / or an aperiodic CSI report). The base station may use feedback provided by the wireless device (e.g., an estimated downlink channel state) to perform link adaptation.

[0124] The base station may semi-statically configure one or more CSI-RS resource sets for the wireless device. The CSI-RS resources may be associated with positions and periodicities in the time domain and the frequency domain. The base station may selectively activate and / or deactivate CSI-RS resources. The base station may indicate to the wireless device that CSI-RS resources in the CSI-RS resource set are activated and / or deactivated.

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

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

[0127] The downlink DM-RS may be sent / 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). The network (e.g., 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 front-loaded DM-RS pattern. The front-loaded DM-RS may be mapped to one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). The base station may semi-statically configure a certain number / quantity (e.g., maximum number / quantity) of front-loaded DM-RS symbols for PDSCH for the wireless device. 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 4 orthogonal downlink DM-RS ports per wireless device (e.g., for multi-user MIMO). The radio network may support (e.g., at least for CP-OFDM) a common DM-RS structure for downlink and uplink. The DM-RS positions, DM-RS patterns, and / or scrambling sequences may be the same or different. The base station may, for example, send / transmit the downlink DM-RS and the corresponding PDSCH using the same precoding matrix. The wireless device may use the one or more downlink DM-RS for coherent demodulation / channel estimation of the PDSCH.

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

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

[0130] For example, the wireless device may send / transmit an uplink DM-RS to the base station for channel estimation. The base station may use the uplink DM-RS for coherent demodulation of one or more uplink physical channels. The wireless device may use PUSCH and / or PUCCH to send / transmit uplink DM-RS. The uplink DM-RS may span a frequency range similar to the frequency range associated with the corresponding physical channel. The base station may configure one or more uplink DM-RS configurations for the wireless device. At least one DM-RS configuration may support a front-loaded DM-RS mode. The front-loaded DM-RS may be mapped to one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DM-RS may be configured to send / transmit at one or more symbols of PUSCH and / or PUCCH. The base station may semi-statically configure a certain number / number (e.g., a maximum number / number) of front-loaded DM-RS symbols for PUSCH and / or PUCCH for the wireless device, and the wireless device may use these symbols to schedule single-symbol DM-RS and / or dual-symbol DM-RS. A network (e.g., an NR network) may support a common DM-RS structure for 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-RSs may be substantially the same or different.

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

[0132] One or more SRSs may be sent / transmitted by a wireless device to a base station, for example, for channel state estimation to support uplink channel-related scheduling and / or link adaptation. The SRS sent / transmitted by the wireless device may enable / allow the base station to estimate the uplink channel state at one or more frequencies. The scheduler at the base station may use / adopt the estimated uplink channel state to assign one or more resource blocks for uplink PUSCH transmission of the wireless device. The base station may semi-statically configure one or more SRS resource sets for the wireless device. For an SRS resource set, the base station may configure one or more SRS resources for the wireless device. The applicability of the SRS resource set may be configured, for example, by a high-level (e.g., RRC) parameter. The SRS resources in the SRS resource set in the one or more SRS resource sets (e.g., having the same / similar time domain behavior, periodicity, aperiodicity, etc.) may be sent / transmitted at a certain time (e.g., at the same time), for example, if the higher-level parameters indicate beam management. The wireless device may send / transmit one or more SRS resources in the SRS resource set. The network (e.g., NR network) may support aperiodic, periodic, and / or semi-persistent SRS transmission. The wireless device may, for example, send / transmit SRS resources based on one or more trigger types. The one or more trigger types may include high-layer signaling (e.g., RRC) and / or one or more DCI formats. The wireless device may use / adopt at least one DCI format to select at least one of one or more configured SRS resource sets. SRS trigger type 0 may refer to SRS triggered based on high-layer signaling. SRS trigger type 1 may refer to SRS triggered based on one or more DCI formats. If PUSCH and SRS are sent / transmitted in the same time slot, the wireless device may be configured to send / transmit SRS, for example, after the transmission of PUSCH and the corresponding uplink DM-RS. The base station can semi-statically configure one or more SRS configuration parameters for the wireless device, wherein the configuration parameters indicate at least one of the following: an SRS resource configuration identifier; the number of SRS ports; the time domain behavior of the SRS resource configuration (e.g., an indication of periodic semi-persistent or non-periodic SRS); slot, micro-slot and / or subframe level periodicity; offsets of periodic and / or non-periodic SRS resources; the number of OFDM symbols in the SRS resource; the starting OFDM symbol of the SRS resource; SRS bandwidth; frequency hopping bandwidth; cyclic shift; and / or SRS sequence ID.

[0133] Antenna ports may be determined / defined such that a channel for transmitting another symbol on the same antenna port may be inferred from a channel for transmitting a symbol on the antenna port. For example, if a first symbol and a second symbol are sent / transmitted on the same antenna port, a receiver may infer / determine a channel (e.g., attenuation gain, multipath delay, etc.) for transmitting the second symbol on the antenna interface from a channel for transmitting the first symbol on the antenna port. For example, if one or more large-scale properties of a channel for transmitting a first symbol on a first antenna port may be inferred from a channel for transmitting a second symbol on a second antenna port, the first antenna port and the second antenna port may be referred to as quasi-co-located (QCLed). The one or more large-scale properties may include at least one of: delay spread; Doppler spread; Doppler shift; average gain; average delay; and / or spatial receive (Rx) parameters.

[0134] Channels 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. The wireless device may, for example, perform downlink beam measurement based on one or more downlink reference signals (e.g., CSI-RS) and generate a beam measurement report. For example, after establishing an RRC connection with a base station, the wireless device may perform a downlink beam measurement procedure.

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

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

[0137] A CSI-RS (e.g., CSI-RS 1101, 1102, 1103) may be sent / transmitted by a base station and used by a wireless device for one or more measurements. The wireless device may measure the RSRP of a configured CSI-RS resource. The base station may configure a reporting configuration for the wireless device, and the wireless device may report the RSRP measurement result 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 multiple 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 a downlink transmission with an Rx beam determined based on the one or more TCI states. The wireless device may or may not have a beam-corresponding capability. If the wireless device has a beam-corresponding capability, the wireless device may, for example, determine a spatial domain filter for a transmit (Tx) beam based on a spatial domain filter for a corresponding Rx beam. For example, if the wireless device does not have beam-corresponding capability, the wireless device may perform an uplink beam selection procedure to determine a spatial domain filter for a Tx beam. The wireless device may perform an uplink beam selection procedure, for example, based on one or more sounding reference signal (SRS) resources configured by the base station for the wireless device. The base station may select and indicate an uplink beam for the wireless device, for example, based on a measurement result of the one or more SRS resources sent / transmitted by the wireless device.

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

[0139] 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) may be executed. Procedure P1 may enable measurements (e.g., wireless device measurements) of Tx beams of a TRP (or multiple TRPs) (e.g., to support selection of one or more base station Tx beams and / or wireless device Rx beams). The Tx beams of the base station and the Rx beams of the wireless device are shown as ovals in the top row of P1 and the bottom row of P1, respectively. Beamforming (e.g., at the TRP) may include Tx beam scanning for a set of beams (e.g., shown as an elliptical beam scanning rotating counterclockwise as indicated by a dashed arrow in the top row of P1 and P2). Beamforming (e.g., at the wireless device) may include Rx beam scanning for a set of beams (e.g., shown as an elliptical beam scanning rotating clockwise as indicated by a dashed arrow in the bottom row of P1 and P3). Procedure P2 may be used to enable measurements (e.g., wireless device measurements) of the Tx beams of the TRP (shown in the top row of P2 as an ellipse rotating counterclockwise indicated by a dashed arrow). The wireless device and / or the base station may perform procedure P2, for example, using a smaller set of beams than the set of beams used in procedure P1, or using narrower beams than the beams used in procedure P1. Procedure P2 may be referred to as beam refinement. The wireless device may perform procedure P3 for Rx beam determination, for example, by using the same Tx beam of the base station and scanning the Rx beam of the wireless device.

[0140] 12B shows an example of an uplink beam management procedure. One or more uplink beam management procedures (e.g., uplink beam management procedures U1, U2, and U3) may be executed. Procedure U1 may be used to enable a base station to perform measurements on a Tx beam of a wireless device (e.g., to support selection of one or more Tx beams of a wireless device and / or an Rx beam of a base station). The Tx beam of a wireless device and the Rx beam of a base station are shown as ovals in the top row of U1 and the bottom row of U1, respectively. Beamforming (e.g., at a wireless device) may include one or more beam scans, such as Tx beam scans from a set of beams (shown as ovals rotating clockwise as indicated by dashed arrows in the bottom rows of U1 and U3). Beamforming (e.g., at a base station) may include one or more beam scans, such as Rx beam scans from a set of beams (shown as ovals rotating counterclockwise as indicated by dashed arrows in the top rows of U1 and U2). For example, if a wireless device (e.g., UE) uses a fixed Tx beam, procedure U2 may be used to enable the base station to adjust its Rx beam. The wireless device and / or the base station may perform procedure U2, for example, to use a smaller set of beams than the set of beams used in procedure P1, or to use a narrower beam than the beam used in procedure P1. Procedure U2 may be referred to as beam refinement. For example, if a base station uses a fixed Rx beam, the wireless device may perform procedure U3 to adjust its Tx beam.

[0141] The wireless device may initiate / start / perform a beam failure recovery (BFR) procedure, for example, based on detecting a beam failure. The wireless device may send / transmit a BFR request (e.g., preamble, UCI, SR, MACCE, etc.), for example, based on initiating the BFR procedure. The wireless device may detect a beam failure, for example, based on determining that the quality of the beam-pair link of the associated control channel is unsatisfactory (e.g., having a bit error rate above a bit error rate threshold, a received signal power below a received signal power threshold, expiration of a timer, etc.).

[0142] The wireless device may measure the quality of the beam-to-link using, for example, one or more reference signals (RS) including one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more DM-RS. The quality of the beam-to-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 for the RS resource. The base station may indicate the QCL of one or more DM-RS of the RS resource and a channel (e.g., a control channel, a shared data channel, etc.). For example, if the channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameters, fading, etc.) from the transmission to the wireless device via the RS resource are similar or identical to the channel characteristics from the transmission to the wireless device via the channel, the RS resource and the one or more DM-RS of the channel may be QCL.

[0143] The network (e.g., an NR network including gNB and / or ng-eNB) and / or the 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 / start / perform a random access procedure to request a connection setup to the network. The wireless device may initiate / start / perform a random access procedure from an RRC connected (e.g., RRC_CONNECTED) state. The wireless device may initiate / start / perform a random access procedure to request uplink resources (e.g., uplink transmission for SR if there are no PUCCH resources) and / or acquire / acquire / determine uplink timing (e.g., if the uplink synchronization state is asynchronous). The 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, etc.). The wireless device may initiate / start / perform a random access procedure for a beam failure recovery request. The network may initiate / start / perform a random access procedure, for example, for handover and / or for adding establishment of time alignment for SCells.

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

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

[0146] The one or more RACH parameters provided / configured / included in the configuration message 1310 may indicate one or more physical RACH (PRACH) opportunities that may be used to transmit the first message (e.g., Msg 1 1311). The one or more PRACH opportunities may be predefined (e.g., by a network including one or more base stations). The one or more RACH parameters may indicate one or more available sets of one or more PRACH opportunities (e.g., prach-ConfigIndex). The one or more RACH parameters may indicate an association between (a) one or more PRACH opportunities and (b) one or more reference signals. The one or more RACH parameters may indicate an association between (a) one or more preambles and (b) one or more reference signals. The one or more reference signals may be SS / PBCH blocks and / or CSI-RS. The one or more RACH parameters may indicate the number / number of SS / PBCH blocks mapped to the PRACH opportunities and / or the number / number of preambles mapped to the SS / PBCH blocks.

[0147] The one or more RACH parameters provided / configured / included in the configuration message 1310 may be used to determine the uplink transmit power of the first message (e.g., Msg 1 1311) and / or the third message (e.g., Msg 3 1313). The one or more RACH parameters may indicate a reference power for preamble transmission (e.g., a received target power and / or an initial power for preamble transmission). There may be one or more power offsets indicated by the one or more RACH parameters. The one or more RACH parameters may indicate: a power ramp-up step; a power offset between SSB and CSI-RS; a power offset between the transmission of the first message (e.g., Msg 1 1311) and the third message (e.g., Msg 3 1313); and / or a power offset value between preamble groups. The one or more RACH parameters may indicate one or more thresholds, for example, 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 supplemental uplink (SUL) carrier).

[0148] The first message (e.g., Msg 1 1311) may include one or more preamble transmissions (e.g., 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, for example, based on the path loss measurement result and / or the size of the third message (e.g., Msg 3 1313). The wireless device may measure the RSRP of one or more reference signals (e.g., SSB and / or CSI-RS) and determine at least one reference signal having an RSRP higher than an RSRP threshold (e.g., rsrp-ThresholdSSB and / or rsrp-ThresholdCSI-RS). For example, if the association between the one or more preambles and the at least one reference signal is configured by the RRC message, the wireless device may select at least one preamble associated with the one or more reference signals and / or the selected preamble group.

[0149] For example, the wireless device may determine the preamble based on the 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 result, an RSRP measurement result, and / or a size of a third message (e.g., Msg 3 1313). The one or more RACH parameters may indicate: a preamble format; a maximum number / 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 use the one or more RACH parameters to configure an association between one or more preambles and one or more reference signals (e.g., SSB and / or CSI-RS) for the wireless device. For example, if the association is configured, the wireless device may determine the preamble to be included in the first message (e.g., Msg 1 1311) based on the association. The first message (e.g., Msg 1 1311) may be sent / transmitted to the base station via one or more PRACH opportunities. The wireless device may use one or more reference signals (e.g., SSB and / or CSI-RS) to select a preamble and determine a PRACH opportunity. One or more RACH parameters (e.g., ra-ssb-OccasionMskIndex and / or ra-OccasionList) may indicate an association between a PRACH opportunity and the one or more reference signals.

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

[0151] The second message (e.g., Msg 2 1312) (e.g., received by the wireless device) may include the 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 the transmission / transmission of the first message (e.g., Msg 1 1311) (e.g., after or in response to it). 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 base station received the first message (e.g., Msg 1 1311). The second message (e.g., Msg 2 1312) may include a time alignment command (which may be used by the wireless device to adjust the transmit timing of the wireless device), a scheduling grant and / or a temporary cell RNTI (TC-RNTI) for transmitting a third message (e.g., Msg 3 1313). For example, after sending / transmitting the first message (e.g., Msg 1 1311) (e.g., a preamble), the wireless device may determine / start a time window (e.g., a RA-ResponseWindow) to monitor the PDCCH for the second message (e.g., Msg 2 1312). The wireless device may determine the start time of the time window, for example, based on a PRACH opportunity used by the wireless device to send / transmit the first message (e.g., Msg 1 1311) (e.g., a preamble). The wireless device may start the time window at one or more symbols after the last symbol of the first message (e.g., Msg 1 1311) including the preamble (e.g., the symbol in which the first message (Msg 1 1311) including the preamble transmission is completed or at the first PDCCH opportunity from which the preamble transmission ends). The one or more symbols may be determined based on a parameter set. The PDCCH may be mapped in a common search space (e.g., Type1-PDCCH common search space) configured by an RRC message. The wireless device may identify / determine the RAR based on, for example, the RNTI. The radio network temporary identifier (RNTI) may be used according to one or more events of initiating / starting a random access procedure. The wireless device may use the RA-RNTI, for example, for one or more communications associated with random access or any other purpose. The RA-RNTI may be associated with a PRACH opportunity in which the wireless device sends / transmits a preamble. The wireless device may determine the RA-RNTI, for example, based on at least one of the following: an OFDM symbol index; a time slot index; a frequency domain index; and / or a UL carrier indicator of a PRACH opportunity. An exemplary RA-RNTI may be determined as follows:

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

[0153] Where s_id may be the index of the first OFDM symbol of the PRACH opportunity (e.g., 0≤s_id<14), t_id may be the index of the first time 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).

[0154] The wireless device may send / transmit a third message (e.g., Msg 3 1313), for example, based on (e.g., after or in response to) successful reception of the second message (e.g., Msg 2 1312) (e.g., using the resources identified in Msg 2 1312). The third message (e.g., Msg 3 1313) may be used, for example, for contention resolution in a contention-based random access procedure. Multiple wireless devices may send / transmit the same preamble to a base station, and the base station may send / transmit a RAR corresponding to the wireless device. For example, if the multiple wireless devices interpret the RAR as corresponding to themselves, a collision may occur. Contention resolution (e.g., using the third message (e.g., Msg 3 1313) and the fourth message (e.g., Msg 4 1314)) may be used to increase the likelihood that a wireless device will not mistakenly use the identity of another wireless device. For example, the wireless device may include a device identification (e.g., the TC RNTI included in the second message (e.g., Msg2 1312) if a C-RNTI is assigned, and / or any other suitable identifier) ​​in a third message (e.g., Msg 3 1313), for example, to perform contention resolution.

[0155] The fourth message (e.g., Msg 4 1314) may be received, for example, based on (e.g., after or in response to) the sending / transmission of the third message (e.g., Msg 3 1313). For example, if the C-RNTI is included in the third message (e.g., Msg 3 1313), the base station may address the wireless device on the PDCCH using the C-RNTI (e.g., the base station may send the PDCCH to the wireless device). For example, if a unique C RNTI of the wireless device is detected on the PDCCH (e.g., the PDCCH is scrambled by the C-RNTI), the random access procedure may be determined to be successfully completed. For example, 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 not otherwise connected to the base station), the fourth message (e.g., Msg 4 1314) may be received using a DL-SCH associated with the TC RNTI. 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 can determine that the contention resolution is successful and / or the wireless device can determine that the random access procedure is successfully completed.

[0156] The wireless device may be configured with a SUL carrier and / or a NUL carrier. Initial access (e.g., random access) may be supported via an uplink carrier. The base station may configure multiple RACH configurations for the wireless device (e.g., two separate RACH configurations, including: one for the SUL carrier and the other for the NUL carrier). For random access in a cell configured with a SUL carrier, the network may indicate which carrier (NUL or SUL) to use. 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, the wireless device may determine to use the SUL carrier. The 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 be maintained on the selected carrier or may be performed via the selected carrier. The wireless device may switch the uplink carrier during the random access procedure (e.g., between Msg 1 1311 and Msg 3 1313). The wireless device may determine and / or switch uplink carriers for the first message (eg, Msg1 1311) and / or the third message (eg, Msg 3 1313), for example, based on channel idle assessment (eg, listen before talk).

[0157] FIG. 13B illustrates a two-step random access procedure. The two-step random access procedure may include a two-step contention-free random access procedure. Similar to the four-step contention-based random access procedure, the base station may send / transmit a configuration message 1320 to the wireless device before initiating the procedure. The configuration message 1320 may be similar to the configuration message 1310 in some aspects. The procedure shown 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 to the first message (e.g., Msg 1 1311) and the second message (e.g., Msg 2 1312), respectively. The two-step contention-free random access procedure may not include messages similar to the third message (e.g., Msg 3 1313) and / or the fourth message (e.g., Msg 4 1314).

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

[0159] The wireless device may, for example, start a time window (e.g., ra-ResponseWindow) based on (e.g., after or in response to) sending / transmitting a preamble to monitor the PDCCH for the RAR. The base station may configure one or more beam failure recovery parameters for the wireless device, 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 the 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 sending / transmitting the beam failure recovery request (e.g., the window may start any number of symbols and / or time slots after sending / transmitting the beam failure recovery request). The wireless device may monitor PDCCH transmissions addressed to a cell RNTI (C-RNTI) on the search space. During a two-step (e.g., contention-free) random access procedure, for example, based on sending / transmitting a first message (e.g., Msg 1 1321) and receiving a corresponding second message (e.g., Msg 2 1322) (e.g., thereafter or in response thereto), the wireless device may determine that the random access procedure is successful. For example, if the PDCCH transmission is addressed to the corresponding C-RNTI, the wireless device may determine that the random access procedure has been successfully completed. For example, if the wireless device receives a RAR including a preamble identifier corresponding to a preamble sub-PDU sent / transmitted by the wireless device and / or the RAR includes a MAC sub-PDU with a preamble identifier, the wireless device may determine that the random access procedure has been successfully completed. The wireless device may determine the response as an indication of an acknowledgement of the SI request.

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

[0161] Msg A 1320 may be sent / transmitted by the wireless device in an uplink transmission. 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 the third message (e.g., Msg 3 1313) (e.g., as shown in FIG. 13A). The transport block 1342 may include UCI (e.g., SR, HARQ ACK / NACK, etc.). The wireless device may receive the second message (e.g., Msg B 1332), for example, based on (e.g., after or in response to) sending / transmitting the first message (e.g., Msg A 1331). The second message (e.g., Msg B 1332) may include content similar to and / or equivalent to the content of the second message (e.g., Msg 2 1312) (e.g., the RAR shown in FIG. 13A), the second message (e.g., Msg 2 1322) (e.g., the RAR shown in FIG. 13B), and / or the fourth message (e.g., Msg 4 1314) (e.g., shown in FIG. 13A).

[0162] The wireless device may start / initiate a two-step random access procedure for a licensed spectrum and / or an unlicensed spectrum (e.g., the two-step random access procedure shown in FIG. 13C ). 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 being used (e.g., LTE, NR, etc.); whether the wireless device has a valid TA; the cell size; the RRC state of the wireless device; the spectrum type (e.g., licensed vs. unlicensed); and / or any other suitable factor.

[0163] The wireless device may determine radio resources and / or uplink transmit power for the preamble 1341 and / or the 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 for the preamble 1341 and / or the transport block 1342. The time-frequency resources for transmitting the preamble 1341 (e.g., PRACH) and the time-frequency resources for transmitting 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 reception timing and downlink channel for monitoring and / or receiving the second message (e.g., Msg B 1332).

[0164] The transmission block 1342 may include data (e.g., delay-sensitive data), an identification of the wireless device, security information, and / or device information (e.g., an International Mobile Subscriber Identity (IMSI)). The base station may send / transmit a second message (e.g., Msg B 1332) as a response to the first message (e.g., Msg A 1331). The second message (e.g., Msg B 1332) may include at least one of the following: a preamble identifier; a timing advance command; a power control command; an uplink grant (e.g., a radio resource assignment and / or an MCS); a wireless device identification (e.g., a UE identifier for contention resolution); and / or an RNTI (e.g., a C-RNTI or a TC-RNTI). For example, if the preamble identifier in the second message (e.g., Msg B 1332) corresponds to or matches the preamble sent / transmitted by the wireless device and / or the identifier of the wireless device in the second message (e.g., Msg B 1332) corresponds to or matches the identifier of the wireless device in the first message (e.g., Msg A 1331) (e.g., transport block 1342), the wireless device can determine that the two-step random access procedure is successfully completed.

[0165] The wireless device and the base station may exchange control signaling (e.g., control information). The control signaling may be referred to as L1 / L2 control signaling and may originate from the PHY layer (e.g., layer 1) and / or the MAC layer (e.g., layer 2) of the wireless device or the base station. The control signaling may include downlink control signaling sent / transmitted from the base station to the wireless device and / or uplink control signals sent / transmitted from the wireless device to the base station.

[0166] Downlink control signaling may include at least one of the following: downlink scheduling assignment; uplink scheduling grant indicating uplink radio resources and / or transmission format; time slot format information; preemption indication; power control command; and / or any other suitable signaling. The wireless device may receive downlink control signaling in a payload sent / transmitted by the base station via the PDCCH. The payload sent / transmitted via the PDCCH may be referred to as downlink control information (DCI). The PDCCH may be a group common PDCCH (GC-PDCCH) shared by a group of wireless devices. The GC-PDCCH may be scrambled by a group common RNTI.

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

[0168] DCI can be used for different purposes. The purpose can be indicated by the type of RNTI used to scramble the CRC parity bits. DCI with CRC parity bits scrambled with a paging RNTI (P-RNTI) can indicate paging information and / or system information change notification. P-RNTI can be predefined as hexadecimal "FFFE". DCI with CRC parity bits scrambled with a system information RNTI (SI-RNTI) can indicate a broadcast transmission of system information. SI-RNTI can be predefined as hexadecimal "FFFF". DCI with CRC parity bits scrambled with a random access RNTI (RA-RNTI) can indicate a random access response (RAR). DCI with CRC parity bits scrambled with a cell RNTI (C-RNTI) can indicate a triggering of a dynamically scheduled unicast transmission and / or an ordered random access of a PDCCH. A DCI with CRC parity bits scrambled with a temporary cell RNTI (TC-RNTI) may indicate contention resolution (e.g., Msg3 similar to Msg 3 1313 shown in FIG. 13A ). Other RNTIs configured by the base station for the wireless device may include a configured scheduling RNTI (CS RNTI), a transmit power control PUCCH RNTI (TPC PUCCH-RNTI), a transmit power control PUSCH RNTI (TPC-PUSCH-RNTI), a transmit power control SRS RNTI (TPC-SRS-RNTI), an interruption RNTI (INT-RNTI), a slot format indication RNTI (SFI-RNTI), a semi-persistent CSI RNTI (SP-CSI-RNTI), a modulation and coding scheme cell RNTI (MCS-C RNTI), and the like.

[0169] The base station may send / transmit DCI in one or more DCI formats, for example, depending on the purpose and / or content of the DCI. DCI format 0_0 may be used to schedule PUSCH in a cell. DCI format 0_0 may be a fallback DCI format (e.g., with a compact DCI payload). DCI format 0_1 ​​may be used to schedule PUSCH in a cell (e.g., with more DCI payload than DCI format 0_0). DCI format 1_0 may be used to schedule PDSCH in a cell. DCI format 1_0 may be a fallback DCI format (e.g., with a compact DCI payload). DCI format 1_1 may be used to schedule PDSCH in a cell (e.g., with more 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 notify / inform a group of wireless devices of physical resource blocks and / or OFDM symbols, where the group of wireless devices may assume that no transmission is intended for the group of wireless devices. DCI format 2_2 can be used to transmit transmit power control (TPC) commands for PUCCH or PUSCH. DCI format 2_3 can be used to transmit a set of TPC commands for SRS transmission of one or more wireless devices. DCI formats for new functions may be defined in future releases. DCI formats can have different DCI sizes, or can share the same DCI size.

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

[0171] FIG. 14A shows an example of a CORESET configuration. The CORESET configuration may be used for a bandwidth portion or any other frequency band. The base station may send / transmit DCI via the PDCCH on one or more control resource sets (CORESETs). The CORESET may include time-frequency resources that the wireless device attempts / tries to use one or more search spaces to decode the DCI. The 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 appear at the first symbol in the time slot, or may be set / configured at the first symbol of the time slot. The first CORESET 1401 may overlap with the second CORESET 1402 in the frequency domain. The third CORESET 1403 may appear at the third symbol in the time slot, or may be set / configured at the third symbol of the time slot. The fourth CORESET 1404 may appear at the seventh symbol in the time slot, or may be set / configured at the seventh symbol of the time slot. The CORESET may have different numbers of resource blocks in the frequency domain.

[0172] 14B shows an example of CCE to REG mapping. CCE to REG mapping for DCI transmission may be performed via CORESET and PDCCH processing. CCE to REG mapping may be an interleaved mapping (e.g., for the purpose of providing frequency diversity) or a non-interleaved mapping (e.g., for the purpose of facilitating interference coordination and / or frequency selective transmission of control channels). A base station may perform different or the same CCE to REG mapping on different CORESETs. A CORESET may be associated with a CCE to REG mapping (e.g., configured by RRC). A CORESET may be configured with an antenna port QCL parameter. The antenna port QCL parameter may indicate QCL information for a DM-RS received via the PDCCH of the CORESET.

[0173] The 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 the wireless device. These configuration parameters may indicate the association between the search space set and the CORESET. The search space set may include a set of PDCCH candidates formed by CCEs (e.g., at a given aggregation level). These configuration parameters may indicate at least one of the following: the number of PDCCH candidates to be monitored per aggregation level; PDCCH monitoring periodicity and PDCCH monitoring mode; 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). A set of CCEs in the common search space set may be predefined and known to the wireless device. A set of CCEs in a wireless device-specific search space set (e.g., a UE-specific search space set) may be configured, for example, based on the identity of the wireless device (e.g., C-RNTI).

[0174] As shown in FIG. 14B , the wireless device may determine the time-frequency resources for the CORESET based on one or more RRC messages. For example, the wireless device may determine the CCE to REG mapping for the CORESET based on the configuration parameters of the CORESET (e.g., interleaved or non-interleaved and / or mapping parameters). For example, the wireless device may determine the number of search space sets configured on / for the CORESET based on the one or more RRC messages (e.g., up to 10). The wireless device may monitor a set of PDCCH candidates based on the configuration parameters of the search space set. The wireless device may monitor the PDCCH candidate sets in one or more CORESETs to detect one or more DCIs. Monitoring may include decoding one or more PDCCH candidates of the PDCCH candidate set based on the monitored DCI format. Monitoring may include decoding the DCI content of one or more PDCCH candidates using possible (or configured) PDCCH positions, possible (or configured) PDCCH formats (e.g., the number of CCEs, the number of PDCCH candidates in a common search space, and / or the number of PDCCH candidates in a wireless device-specific search space), and possible (or configured) DCI formats. Decoding may be referred to as blind decoding. The wireless device may determine that the DCI is valid for the wireless device, for example, based on a CRC check (e.g., a scrambled bit of a CRC parity bit of the DCI matches the RNTI value) (e.g., thereafter or in response thereto). The wireless device may process information included in the DCI (e.g., scheduling assignments, uplink grants, power control, slot format indications, downlink preemption, etc.).

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

[0176] There may be multiple PUCCH formats (e.g., five PUCCH formats). The wireless device may determine the PUCCH format, for example, based on the size of the UCI (e.g., the number / number of uplink symbols transmitted by the UCI and the number of UCI bits). PUCCH format 0 may have a length of one or two OFDM symbols and may include two bits or less. If the transmission is performed by / via one or two symbols and the number / number of HARQ-ACK information bits (HARQ-ACK / SR bits) with positive or negative SR is one or two bits, the wireless device may send / transmit UCI via PUCCH resources, for example, using PUCCH format 0. PUCCH format 1 may occupy multiple OFDM symbols (e.g., between four and fourteen OFDM symbols) and may include two bits or less. For example, if the transmission is performed by / via four or more symbols and the number of HARQ-ACK / SR bits is one or two bits, the wireless device may use PUCCH format 1. PUCCH format 2 may occupy one or two OFDM symbols and may include more than two bits. For example, if the transmission is by / via one or two symbols, and the number / number of UCI bits is two or more bits, the wireless device may use PUCCH format 2. PUCCH format 3 may occupy multiple OFDM symbols (e.g., between four and fourteen OFDM symbols) and may include more than two bits. For example, if the transmission is four or more symbols, the number / number of UCI bits is two or more bits, and the PUCCH resource does not include an orthogonal cover code (OCC), the wireless device may use PUCCH format 3. PUCCH format 4 may occupy multiple OFDM symbols (e.g., between four and fourteen OFDM symbols) and may include more than two bits. For example, if the transmission is four or more symbols, the number / number of UCI bits is two or more bits, and the PUCCH resource includes an OCC, the wireless device may use PUCCH format 4.

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

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

[0179] FIG15A illustrates exemplary communications between a wireless device and a base station. Wireless device 1502 and base station 1504 may be part of a communication network, such as communication network 100 illustrated in FIG1A , communication network 150 illustrated in FIG1B , or any other communication network. A communication network may include more than one wireless device and / or more than one base station having substantially the same or similar configuration as those shown in FIG15A .

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

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

[0182] Data to be transmitted to the wireless device 1502 may be provided / transmitted / sent to the transmit processing system 1510 of the base station 1504, for example, after being processed by the processing system 1508. Data to be transmitted to the base station 1504 may be provided / transmitted / sent to the transmit processing system 1520 of the wireless device 1502, for example, after being processed by the processing system 1518. 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 FIG. 2A, FIG. 2B, FIG. 3, and FIG. 4A. For transmit processing, the PHY layer may perform, for example, forward error correction coding of a transport channel, interleaving, rate matching, mapping of a transport channel to a physical channel, modulation of a physical channel, multiple-input multiple-output (MIMO) or multi-antenna processing, etc.

[0183] 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, etc.

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

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

[0186] 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 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 device, 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 encoding / processing, data processing, power control, input / output processing, and / or any other functions that may enable the wireless device 1502 and / or the base station 1504 to operate in a wireless environment.

[0187] 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 provides features and / or functionality, such as a speaker, a microphone, a keypad, a display, a touch pad, 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 motor vehicle), and / or one or more sensors (e.g., an accelerometer, a gyroscope, a temperature sensor, a radar sensor, a laser sensor, an ultrasonic sensor, a light sensor, a camera, etc.). The processing system 1508 and / or the processing system 1518 may receive input data (e.g., user output data) / provide output data (e.g., user output data) from and / or to the one or more peripheral devices 1516 and / or the one or more peripheral devices 1526. The processing system 1518 in the wireless device 1502 can receive power from a power source and / or can be configured to distribute power to other components in the wireless device 1502. The power source can include one or more power sources, such as a battery, a solar cell, a fuel cell, or any combination thereof. The processing system 1508 can be connected to a global positioning system (GPS) chipset 1517. The processing system 1518 can be connected to a global positioning system (GPS) chipset 1527. The GPS chipset 1517 and the GPS chipset 1527 can be configured to determine and provide geographic location information of the wireless device 1502 and the base station 1504, respectively.

[0188] 15B illustrates exemplary elements of a computing device that can 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. Computing device 1530 may include one or more processors 1531 that can execute instructions stored in random access memory (RAM) 1533, removable media 1534 (such as, a universal serial bus (USB) drive, a compact disk (CD) or a digital versatile disk (DVD), or a floppy disk drive), or any other desired storage medium. Instructions may also be stored in 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 executed on the processor 1531 and any process requesting access to any hardware and / or software component 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, a display device, a monitor, a 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, a keyboard, a mouse, a touch screen, a 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 both. The network interface 1539 may provide an interface for the computing device 1530 to communicate with the network 1540 (e.g., 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 communication link, an external network, a home network, a provider's wireless, coaxial cable, fiber optic or hybrid fiber optic / coaxial cable distribution system (e.g., a DOCSIS network), or any other desired network. In addition, the computing device 1530 may include a location detection device, such as a global positioning system (GPS) microprocessor 1541, which may be configured to receive and process global positioning signals and determine the geographic location of the computing device 1530 with possible help from an external server and antenna.

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

[0190] FIG. 16A shows an exemplary 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 the following: scrambling; modulating the scrambled bits to generate complex-valued symbols; mapping the complex-valued modulation symbols to one or several transmission layers; transforming precoding to generate complex-valued symbols; precoding the complex-valued symbols; mapping the precoded complex-valued symbols to resource elements; generating a complex-valued time-domain single carrier frequency division multiple access (SC-FDMA), a CP-OFDM signal for an antenna port, or any other signal; and the like. For example, if transform precoding is enabled, an SC-FDMA signal for uplink transmission may be generated. For example, if transform precoding is not enabled (e.g., as shown in FIG. 16A ), a CP-OFDM signal for uplink transmission may be generated. These functions are examples, and other mechanisms for uplink transmission may be implemented.

[0191] FIG16B shows an exemplary structure for modulating and up-converting 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) and / or a complex-valued physical random access channel (PRACH) baseband signal for an antenna port. For example, filtering may be performed / adopted prior to transmission.

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

[0193] FIG16D shows an exemplary structure for modulating and up-converting 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. For example, filtering may be performed / adopted before transmission.

[0194] The wireless device may receive one or more messages (e.g., RRC messages) including configuration parameters of multiple cells (e.g., a primary cell, one or more secondary cells) from a base station. The wireless device may communicate with at least one base station (e.g., two or more base stations in a dual connection) via the multiple cells. The one or more messages (e.g., as part of the configuration parameters) may include parameters for configuring the PHY, MAC, RLC, PCDP, SDAP, and RRC layers of 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.

[0195] The timer may, for example, start running once started and continue running until it stops or until it expires. For example, if the timer is not running, the timer may be started, or if the timer is running, the timer may be restarted. The timer may be associated with a value (e.g., the timer may be started or restarted from a certain value, or may be started from zero and expire once the value is reached). For example, the duration of the timer may not be updated before the timer stops or expires (e.g., due to BWP switching). The timer may be used to measure the period / window used for the process. As for the embodiments and / or procedures related to one or more timers or other parameters, it should be understood that there may be multiple ways to implement the one or more timers or other parameters. One or more of the multiple ways of implementing the timer may be used to measure the period / window used for the procedure. The random access response window timer may be used to measure the time window for receiving a random access response. For example, the time difference between two timestamps may be used instead of starting the random access response window timer and determining the expiration of the timer. For example, if the timer is restarted, the process for measuring the time window may be restarted. Other exemplary embodiments may be configured / provided to restart the measurement of the time window.

[0196] The wireless device may receive configuration parameters, for example, from a base station. The configuration parameters may indicate the value of a field (e.g., a unified TCI state index, a TRP index, a control resource set pool index, etc.) for an uplink resource (and / or an uplink resource set / group). The uplink resource may be a PUCCH resource. The uplink resource may be an SRS resource. The uplink resource set / group may be a PUCCH resource group. The uplink resource set / group may be an SRS resource set.

[0197] 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 to transmit an uplink signal via an uplink resource, for example, based on the value of the field. For example, if the value is equal to 0 (e.g., 0, 00), the wireless device may use the first TCI state. For example, if the value is equal to 1 (e.g., 1, 01), the wireless device may use the second TCI state. For example, if the value is equal to 2 (e.g., 10, 11), the wireless device may use the first TCI state and the second TCI state.

[0198] The wireless device may receive a second downlink message (e.g., DCI, MAC-CE) indicating activation of a third TCI state (e.g., a single / one TCI state). In at least some systems, the value of the field may be used to determine the TCI state to be applied / used to transmit an uplink signal via an uplink resource. For example, if a single TCI state is activated, this operation may not be effective. The wireless device may apply / use the third TCI state to transmit an uplink signal via an uplink resource regardless of the value of the field. For example, if the second downlink message indicates activation of a single / one TCI state, the wireless device may ignore the value of the field. For example, if the second downlink message indicates activation of a single / one TCI state, the wireless device may apply / use a single / one TCI state to transmit an uplink signal via an uplink resource. The wireless device may suspend transmitting an uplink signal via an uplink resource. The wireless device may, for example, suspend transmitting an uplink signal via an uplink resource based 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 apply / use the third TCI state to transmit an uplink signal via the second uplink resource, for example, based on the third TCI state being associated with the first TRP and the second value of the field of the second uplink resource being associated with the first TRP. The configuration parameter may be for the second uplink resource indication field.

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

[0200] 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 send (e.g., transmit) at least one transport block for a configured uplink grant based on the two SRS resource sets in the first SRS resource set list. The wireless device may send (e.g., transmit) the at least one transport block for a configured uplink grant based on the two SRS resource sets in the first SRS resource set list, for example, based on (e.g., in response to) the one or more configuration parameters indicating two SRI fields for the configured uplink grant. For example, if the wireless device is configured with two SRS resource set lists, the SRI field in the configured uplink grant may (e.g., always) indicate an SRS resource in an SRS resource set in one SRS resource set list (e.g., srs-ResourceSetToAddModList and srs-ResourceSetToAddModListDCI-0-2) of the 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). For example, if one or two SRI fields are configured for a configured uplink grant, the SRI field of the configured uplink grant may (e.g., may always) indicate the SRS resources in the SRS resource set in the first SRS resource set list (e.g., srs-ResourceSetToAddModList). For example, in at least some systems, the SRI field of the configured uplink grant may always indicate the SRS resources in the SRS resource set in the srs-ResourceSetToAddModList. The first SRS resource list (e.g., srs-ResourceSetToAddModList) may have a higher priority than the 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.

[0201] 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. For example, if one or more configuration parameters indicate two SRI fields for a configured uplink grant and the first SRS resource set list includes a single SRS resource set, at least some wireless communications may not be efficient. At least some wireless devices may not send (e.g., may not 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 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). In at least some wireless communications, the first SRS resource set list may be configured as a first type of information (or associated with the first type of information) for transmission (e.g., eMBB transmission), and the first type of information may be prioritized over a second type of information for transmission (e.g., uRLLC transmission). The second SRS resource set list may be configured for (or associated with) a second (or other) type of information for transmission, such that if, for example, 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), resources of the first SRS resource set list may be used instead of resources of the second SRS resource set list. However, if two SRI fields are configured for a configured uplink grant, prioritizing the first SRS resource set list (e.g., srs-ResourceSetToAddModList) may not be effective. For example, by prioritizing the first SRS resource set list in this manner, the wireless device may need to ignore one of the two SRI fields of the configured uplink grant by using a single SRS resource set in the first SRS resource set list (e.g., srs-ResourceSetToAddModList), or may not support multiple TRP repetitions (e.g., multiple TRP PUSCH repetitions). By prioritizing a particular SRS resource set list without regard to the number of SRS resources configured in the list, the reliability and / or robustness of the transmission may be reduced.

[0202] As described herein, prioritization may be applied to use an SRS resource set list configured with a larger number of SRS resource sets to improve wireless communications. 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 if the 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., regarding Fig. 20A 20B ), the wireless device may be configured to send (e.g., transmit) a message (e.g., at least one transport block) for a configured uplink grant based on the two (or more) SRS resource sets in the second SRS resource set, for example, if the first SRS resource set list includes a single SRS resource set and the second SRS resource set list includes two (or more) SRS resource sets. The wireless device may send the message based on the second SRS resource list (e.g., using repetitions), for example, even though the wireless device may have a second, higher priority message that is configured for transmission based on the first resource list (e.g., for a single transmission). Such use of two (or more) SRS resource sets may enable the use of repetitions on a single transmission, which may, for example, provide advantages such as increased transmission reliability and / or robustness.

[0203] In another example, 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 of a path loss reference signal for activating or updating an SRS resource set in a first SRS resource set (e.g., a MAC-CE indicating its activation (or update)), 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. For example, if a wireless device receives an indication of activating or updating a path loss reference signal of a first SRS resource set of two SRS resource sets in a first SRS resource set (e.g., a MAC-CE indicating its activation (or update)), such a wireless device may not know 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. 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 if 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. Such uncertainty may result in misalignment between such wireless device and the base station (e.g., misalignment in power control, misalignment in transmit power, misalignment in path loss reference signal, etc.) For example, such wireless device may apply / use a path loss reference signal for a second SRS resource set in the second SRS resource set list, and the base station may assume that the wireless device applies the path loss reference signal to the first SRS resource set in the second SRS resource set list, thereby resulting in misalignment between the wireless device and the base station.

[0204] As described herein, for example, if the first SRS resource set list includes two SRS resource sets and the second SRS resource set list includes two SRS resource sets, an enhanced path loss reference signal update operation may be performed. For example, if the wireless device receives an indication of activating or updating the path loss reference signal of the first SRS resource set of the two SRS resource sets in the first SRS resource set (e.g., a MAC-CE indicating its activation (or update)), the wireless device may apply / use the path loss reference signal for the first SRS resource set in the second SRS resource set list. For example, if the wireless device receives an indication of activating or updating the path loss reference signal of the second SRS resource set of the two SRS resource sets in the first SRS resource set (e.g., a MAC-CE indicating its activation (or update)), the wireless device may use the path loss reference signal for the second SRS resource set in the second SRS resource set list. As described herein (e.g., with respect to FIG. 21 ), if the path loss reference signal of the first SRS resource set / the 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 SRS resource set / the 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 in the second SRS resource set list) may be identified / indicated by / using a first SRS resource set index that is the lowest SRS resource set index or lower than a second SRS resource set index of the second SRS resource set (in the first SRS resource set list and / or in the second SRS resource set list). The second SRS resource set (in the first SRS resource set list and / or in the second SRS resource set list) may be identified / indicated by / using a second SRS resource set index that is the highest SRS resource set index or higher than a first SRS resource set index of the second SRS resource set (in the first SRS resource set list and / or in the second SRS resource set list). If 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 if 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 described path loss reference update / activation may also be applicable. The path loss reference update / activation operation described herein may provide advantages such as reduced beam misalignment, which may result in reduced retransmissions, reduced latency / delay, and / or reduced power consumption.

[0205] FIG. 17 illustrates an exemplary 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., configuration parameters at time T0 in FIG. 17). The one or more configuration parameters may include RRC configuration parameters. The one or more configuration parameters may include RRC reconfiguration parameters.

[0206] One or more configuration parameters may be used for multiple cells. The multiple cells may include a cell. The cell may be, for example, a serving cell. At least one of the one or more configuration parameters may be used 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 / having a PUCCH (e.g., a PUCCH SCell). The cell may be an unlicensed cell, for example, operating in an unlicensed band. The cell may be a licensed cell, for example, operating in a licensed band. The cell may operate in a first frequency range (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 (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, a frequency band from 52.6 GHz to 71 GHz (or any other frequency or frequency range). FR3 may include, for example, a frequency band starting at (or above) 52.6 GHz (or any other frequency).

[0207] The wireless device may perform / perform uplink transmission (e.g., PUSCH, PUCCH, SRS) of the cell via the cell in the first time and the first frequency. The wireless device may perform / perform downlink reception (e.g., PDCCH, PDSCH) of the cell via the cell in the second time and the 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. For example, in the TDD mode, the first time and the second time may be different. 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, wherein the first frequency and the second frequency may be the same or different, and or wherein 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, wherein the first frequency and the second frequency may be the same or different, and or wherein the first time and the second time may be the same or different. The cell may operate in one or more of TDD mode, FDD mode, CDM mode and / or SDM mode.

[0208] The wireless device may be in an RRC mode of 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.

[0209] The cell may include a plurality of BWPs. The plurality of BWPs may include one or more uplink BWPs, the one or more uplink BWPs including the uplink BWP of the cell. The plurality of BWPs may include one or more downlink BWPs, the one or more downlink BWPs including the downlink BWP of the cell.

[0210] A BWP in the plurality of BWPs may be in one of an active state and an inactive state. In the active state of a downlink BWP in the one or more downlink BWPs, the wireless device may monitor downlink channels / signals (e.g., PDCCH, DCI, CSI-RS, PDSCH) on / for / via the downlink BWP. In the active state of a downlink BWP in the one or more downlink BWPs, the wireless device may receive PDSCH on / for / via the downlink BWP. In the inactive state of a downlink BWP in the one or more downlink BWPs, the wireless device may not monitor downlink channels / signals (e.g., PDCCH, DCI, CSI-RS, PDSCH) on / for / via the downlink BWP. In the inactive state of a downlink BWP in the one or more downlink BWPs, the wireless device may stop monitoring (or receiving) downlink channels / signals (e.g., PDCCH, DCI, CSI-RS, PDSCH) on / for / via the downlink BWP. In an inactive state of a downlink BWP among the one or more downlink BWPs, the wireless device may not receive PDSCH on / via / for the downlink BWP. In an inactive state of a downlink BWP among the one or more downlink BWPs, the wireless device may stop receiving PDSCH on / via / for the downlink BWP.

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

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

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

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

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

[0216] The value of the subcarrier spacing (of the downlink BWP and / or uplink BWP) may be / indicate, for example, 15 kHz (µ = 0) or any other frequency or frequency range. The value of the subcarrier spacing may be / indicate, for example, 30 kHz (µ = 1). The value of the subcarrier spacing may be / indicate, for example, 60 kHz (µ = 2). The value of the subcarrier spacing may be / indicate, for example, 120 kHz (µ = 3). The value of the subcarrier spacing may be / indicate, for example, 240 kHz (µ = 4). The value of the subcarrier spacing may be / indicate, for example, 480 kHz (µ = 5). The value of the subcarrier spacing 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 in FR3. Any frequency or frequency range can be valid / applicable for any FR(n) (eg, µ can be equal to any value).

[0217] The one or more configuration parameters may indicate a plurality of control resource sets (CORESETs). The one or more configuration parameters may indicate the plurality of CORESETs for an (active) downlink BWP of a cell. The (active) downlink BWP may include the plurality of CORESETs.

[0218] One or more configuration parameters may indicate a plurality of CORESET indices / identifiers / indicators for the plurality of CORESETs (e.g., provided by a higher layer parameter ControlResourceSetId). Each CORESET in the plurality of CORESETs may be identified / indicated by a corresponding CORESET index in the plurality of CORESET indices. A first CORESET in the plurality of CORESETs may be identified by a first CORESET index in the plurality of CORESET indices. A second CORESET in the plurality of CORESETs may be identified by a second CORESET index in the plurality of CORESET indices.

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

[0220] The number / number of the plurality of TCI states may be equal to, for example, 128 (e.g., M=128) or any other value. The number / number of the plurality of TCI states may be equal to, for example, 64 (e.g., M=64). The number / number of the plurality of TCI states may be equal to, for example, 32 (e.g., M=32). The number / 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 number / number of TCI states. The number / number of the plurality of TCI states indicated by the one or more configuration parameters may be equal to or less than the maximum number of TCI states.

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

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

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

[0224] A plurality of TCI states (or at least one of the plurality of TCI states) may be used for CSI-RS transmission / reception of a cell. The one or more configuration parameters may indicate the plurality of TCI states (or at least one of the plurality of TCI states) for CSI-RS transmission / reception of a downlink BWP of a cell. A TCI state in the plurality of TCI states may indicate a quasi-co-located reference signal for CSI-RS transmission / reception.

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

[0226] 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 in the two TCI state pools may include multiple downlink TCI states in the multiple TCI states. A second TCI state pool in the two TCI state pools may include multiple uplink TCI states in the multiple TCI states.

[0227] The (single) TCI state pool / group may include the multiple TCI states. The multiple TCI states may include / may be multiple downlink TCI states. The multiple TCI states may include / may be multiple uplink TCI states.

[0228] The wireless device may apply / use the multiple downlink TCI states to receive / decode a transport block (or PDSCH transmission / reception). The wireless device may use the multiple downlink TCI states, for example, to receive / decode a transport block (or PDSCH transmission / reception) scheduled for a downlink BWP of a cell. The wireless device may use the multiple downlink TCI states, for example, to receive 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, the wireless device may not use the multiple downlink TCI states (or each TCI state in the multiple downlink TCI states) to transmit an uplink signal (e.g., PUSCH transmission, PUCCH transmission, UCI, transport block, SRS, etc.). The TCI states in the multiple downlink TCI states may indicate / have / include a quasi-co-located reference signal of a DM-RS for a downlink signal (e.g., PDSCH / PDCCH transmission / reception). The reference signal may be quasi-co-located with the DM-RS of the downlink signal. The reference signal may be quasi-co-located with the DM-RS of the downlink signal relative to the quasi-co-location 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-co-location type for the reference signal. The TCI state in the multiple downlink TCI states may indicate a quasi-co-located reference signal for reception of a downlink signal (e.g., CSI-RS). Each of the multiple downlink TCI states may indicate a corresponding reference signal for the quasi-co-location of the DM-RS for a downlink signal (e.g., PDSCH / PDCCH transmission / reception). Each of the multiple downlink TCI states may indicate a corresponding reference signal for the quasi-co-location of the downlink signal (e.g., CSI-RS).

[0229] The wireless device may apply / use the multiple uplink TCI states to transmit a transport block (or PUSCH transmission). The wireless device may use the multiple uplink TCI states, for example, to transmit a transport block (or PUSCH transmission) scheduled / configured for the uplink BWP of the cell. The wireless device may use the multiple uplink TCI states, for example, to transmit an uplink signal (e.g., PUSCH transmission, PUCCH transmission, UCI, transport block, SRS, etc.) via the uplink BWP of the cell. The wireless device may not use the multiple uplink TCI states (or each TCI state in the multiple uplink TCI states) to receive a downlink signal (e.g., PDSCH transmission / reception, PDCCH transmission / reception, DCI, transport block, CSI-RS, etc.). The wireless device may determine a spatial domain transmit filter / beam based on a reference signal indicated by (or in) a TCI state in the multiple uplink TCI states used for transmission of an uplink signal. The wireless device may determine a corresponding spatial domain transmit filter / beam for uplink signal transmission based on a reference signal indicated by (or in) each of the multiple uplink TCI states. 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, α, path loss reference signal, etc.) indicated by (or included in, associated with, or mapped to) a TCI state in the multiple uplink TCI states for uplink signal transmission. The wireless device may determine a corresponding transmit power for uplink signal transmission based on one or more power control parameters indicated by (or included in, associated with, or mapped to) each of the multiple uplink TCI states.

[0230] The (single) TCI state pool / group may include the plurality of TCI states. The 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. The 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 the (single) TCI state pool / group. The 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.

[0231] The one or more configuration parameters may, for example, include 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.

[0232] 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 receiving 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 transmitting 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 in the multiple common / joint TCI states, for example, for reception of downlink signals and transmission of uplink signals. The TCI states in the multiple TCI states (or the multiple common / joint TCI states) may indicate a quasi-co-located reference signal of a DM-RS for a downlink signal (e.g., PDSCH / PDCCH transmission / reception). The TCI state in the multiple TCI states (or the multiple common / joint TCI states) may indicate a quasi-co-located reference signal for reception of a downlink signal (e.g., CSI-RS). Each of the multiple TCI states (or the multiple common / joint TCI states) may indicate a corresponding reference signal for quasi-co-location of a DM-RS for a downlink signal (e.g., PDSCH / PDCCH transmission / reception). Each of the multiple TCI states (or the multiple common / joint TCI states) may indicate a corresponding reference signal for quasi-co-location 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 in the multiple TCI states (or the multiple common / joint TCI states) for uplink signal transmission. The wireless device may determine a corresponding spatial domain transmit filter / beam for uplink signal transmission based on a reference signal indicated by (or in) each TCI state of the plurality of TCI states (or the plurality of common / joint TCI states).

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

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

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

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

[0237] The TCI state of the subset of the plurality of TCI states may indicate a reference signal with / 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 of the reference signal. The wireless device may assume that the reference signal is configured in the downlink BWP of the cell to which the TCI state applies.

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

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

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

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

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

[0243] The wireless device may receive, for example, downlink signals 1730 and / or 1740 shown in FIG. 17. The downlink signal may be sent / received in one or more messages. The downlink signal 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 signal, for example, based on the TCI state of a subset of the multiple TCI states. The wireless device may, for example, receive a DCI that schedules / trigger reception / transmission of a downlink signal. For example, the DCI may indicate a dynamic uplink / downlink grant. The DCI may, for example, indicate activation of an SPS PDSCH transmission. The wireless device may receive a downlink signal (e.g., a transport block) transmitted by an SPS PDSCH. The DCI may include a TCI field indicating a TCI state (or a TCI code point including / indicating a TCI state). The one or more configuration parameters may indicate / configure / schedule / trigger transmission / reception of a downlink signal (e.g., periodic CSI-RS, PDCCH / PDSCH transmission, etc.). The one or more configuration parameters may include / indicate a TCI field indicating a TCI state (or a TCI code point including / indicating a TCI state) for transmission / reception of a downlink signal.

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

[0245] Receiving a downlink signal based on a TCI state may include quasi-co-location of a downlink signal (e.g., CSI-RS, DM-RS) with a reference signal (e.g., CSI-RS, SS / PBCH block, SRS, PUCCH, etc.) indicated by the TCI state. The downlink signal may be quasi-co-located with the reference signal relative to a quasi-co-location type (e.g., QCL type A, QCL type B, QCL type C, QCL type D, etc.). The TCI state may indicate / include / have a quasi-co-location type. The TCI state may include / have a reference signal index indicating / identifying a reference signal. The one or more configuration parameters may indicate a reference signal index for the TCI state.

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

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

[0248] Sending (e.g., transmitting) an uplink signal based on the TCI state may include transmitting the uplink signal using a spatial domain transmit / transmit filter / beam, wherein the spatial domain transmit / transmit filter / beam is determined based on a reference signal (e.g., CSI-RS, SS / PBCH block, SRS, PUCCH) indicated by the TCI state. The spatial domain transmit / transmit filter / beam used to transmit the uplink signal may be the same (or substantially the same, separated by x degrees, 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, separated by x degrees, 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).

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

[0250] The number / number of the one or more TCI code points may be equal to one. 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. A subset of the multiple TCI states may be the at least two TCI states. For example, based on the number of the one or more TCI code points being equal to one, the wireless device may not receive a DCI indicating activation of one or more TCI states of the at least two TCI states. The wireless device may not receive a DCI indicating activation of one or more TCI states among the at least two TCI states, for example, based on an activation command indicating activation of the at least two TCI states.

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

[0252] The DCI may include a TCI field. The TCI field may indicate a TCI code point in the one or more TCI code points. The value of the TCI field (e.g., 110 at step 1730 in FIG. 17 or 111 at step 1740 in FIG. 17) may be, for example, equal to the TCI code point. The value of the TCI field may be, for example, indicating a TCI code point. 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 number of TCI states). The DCI may indicate the activation of a TCI state (e.g., TCI state 42 at time T3 in FIG. 17). The DCI may indicate the activation of the at least two TCI states (or any other number of TCI states).

[0253] 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. The second TCI state may be / include a second unified TCI state.

[0254] The first TCI state (e.g., TCI state 26) may be the first / starting / earliest / initial TCI state in the vector / set / list of the at least two TCI states. The first TCI state may be the first / starting / earliest element in the vector / set / list of the at least two TCI states. The first TCI state may be the first / starting / earliest TCI state among the at least two TCI states in (or indicated by) a TCI code point. The position / location of the first TCI state may be the earliest / highest / lowest in the vector of the at least two TCI states. The position / location of the first TCI state in the vector of the at least two TCI states may be earlier than (or before) the position / location of the second TCI state. The first TCI state may occur first in the vector / set / list of the at least two TCI states. For example, if the vector of the 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 TCI state 26. For example, if the vector of the at least two TCI states is equal to [TCI state 2, TCI state 1], the first / starting / earliest TCI state (or first TCI state) is TCI state 2.

[0255] The second TCI state (e.g., TCI state 61) may be the second / second starting / second earliest TCI state in the vector / set / list of the at least two TCI states. The second TCI state may be the second / second starting / second earliest element in the vector / set / list of the at least two TCI states. The second TCI state may be the second / second starting / second earliest TCI state among the at least two TCI states in (or indicated by) a TCI code point. The position / location of the second TCI state may be the second earliest / second highest / second lowest in the vector of the at least two TCI states. The position / location of the first TCI state in the vector of the at least two TCI states may be earlier than (or before) the position / location of the second TCI state. The position / location of the second TCI state in the vector of the at least two TCI states may be later than (e.g., after) the position / location of the first TCI state. The second TCI state may occur second in the vector / set / list of the at least two TCI states. For example, if the vector of the 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 TCI state 61. For example, if the vector of the at least two TCI states is equal to [TCI state 2, TCI state 1], the second / second starting / second earliest TCI state (or second TCI state) is TCI state 1.

[0256] 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 send (e.g., transmit) the transport block via the resources.

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

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

[0259] The wireless device may apply (or start using) the at least two TCI states from a start / initial / earliest / first time slot, for example, a certain number of symbols (e.g., beam application time, MAC-CE activation time) from the last / end / latest symbol of the uplink signal (or PUCCH with HARQ-ACK information) or after. ). The wireless device may apply (or start using) the at least two TCI states from a starting / initial / earliest / first time slot, the starting / initial / earliest / first time slot being at least the number / number of symbols (e.g., beam application time, MAC-CE activation time) from / after the last / end / latest symbol of the uplink signal. The starting / initial / earliest / first time slot may occur at least the number / number of symbols from / after the last / end / latest symbol of the uplink signal. The number / number of symbols (e.g., beam application time) may be based on the capabilities of the wireless device. For example, the wireless device may send (e.g., transmit) a capability message (e.g., UE capability message) indicating the number / number of symbols. For example, the wireless device may send (e.g., transmit) a capability message (e.g., UE capability message) indicating the minimum and / or maximum number / number of symbols. The one or more configuration parameters (e.g., by RRC parameter beamAppTime) may indicate the number / number of symbols. The one or more configuration parameters (e.g., by RRC parameter beamAppTime) may indicate the number / number of symbols, for example, based on the minimum / maximum number of symbols. The number / number of symbols may, for example, be equal to or greater than the minimum and / or maximum number / number of symbols. The number / number of symbols may, for example, be equal to or less than the minimum and / or maximum number / number of symbols. The number / number of symbols may, for example, be based on the subcarrier spacing (e.g., µ) of the downlink BWP. The number / number of symbols may, for example, be based on the subcarrier spacing (e.g., µ) of the uplink BWP.

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

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

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

[0263] Transmitting an uplink signal using / applying the at least two uplink TCI states 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 uplink TCI state. The first spatial domain transmit / transmit filter / beam may, for example, be the same as (or substantially the same, separated by x degrees, x = 0, 1, 5, 10, etc.) a spatial domain receive / receive filter / beam used to receive the first reference signal. The first spatial domain transmit / transmit filter / beam may, for example, be the same as (or substantially the same, separated by x degrees, x = 0, 1, 5, 10, etc.) a spatial domain transmit / transmit filter / beam used to send (e.g., transmit) the first reference signal. Transmitting an uplink signal using / applying the at least two uplink TCI states may include sending (e.g., transmitting) the one or more first uplink signals at a first transmit power, the first transmit power being determined based on one or more first power control parameters (e.g., target received power, closed loop index, path loss compensation factor, α, path loss reference signal, etc.) indicated by the first uplink TCI state (or included in the first uplink TCI state or associated with the first uplink TCI state or mapped to the first uplink TCI state). The uplink signal may include the one or more first uplink signals. Transmitting an uplink signal using / applying the at least two uplink TCI states may include sending (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 as (or substantially the same as, separated by x degrees, x = 0, 1, 5, 10, etc.) the spatial domain receive / receive filter / beam used to receive the second reference signal. The second spatial domain transmit / transmit filter / beam may, for example, be the same as (or substantially the same as, separated by x degrees, x = 0, 1, 5, 10, etc.) the spatial domain transmit / transmit filter / beam used to send (e.g., transmit) the second reference signal.Transmitting an uplink signal using / applying the at least two uplink TCI states may include sending (e.g., transmitting) the one or more second uplink signals at a second transmit power, the second transmit power being determined based on one or more second power control parameters (e.g., target received power, closed loop index, path loss compensation factor, α, path loss reference signal, etc.) indicated by the second uplink TCI state (or included in the second uplink TCI state or associated with the second uplink TCI state or mapped to the second uplink TCI state). The uplink signal may include the one or more second uplink signals.

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

[0265] Using / applying the at least two downlink TCI states to receive 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 downlink TCI state. The first spatial domain receive / receive filter / beam may, for example, be the same as (or substantially the same, x degrees apart, x = 0, 1, 5, 10, etc.) as the spatial domain receive / receive filter / beam used to receive the first reference signal. The first spatial domain receive / receive filter / beam may, for example, be the same as (or substantially the same, x degrees apart, x = 0, 1, 5, 10, etc.) as the spatial domain transmit / transmit filter / beam used to send (e.g., transmit) the first reference signal. The downlink signal may include the one or more first downlink signals. Using / applying the at least two downlink TCI states to receive 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 downlink TCI state. The second spatial domain receive / receive filter / beam may, for example, be the same as (or substantially the same, x degrees apart, 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, for example, be the same as (or substantially the same, x degrees apart, x = 0, 1, 5, 10, etc.) as the spatial domain transmit / transmit filter / beam used to send (e.g., transmit) the second reference signal. The downlink signal may include the one or more second downlink signals.

[0266] Using / applying the at least two downlink TCI states to receive a downlink signal may include quasi-co-location of the DM-RS (or DM-RS antenna port) of one or more first downlink signals (e.g., PDSCH, PDCCH, CSI-RS, DMRS, etc.) with a first reference signal indicated by the first downlink TCI state. The DM-RS (or DM-RS antenna port) of the one or more first downlink signals may be quasi-co-located with the first reference signal relative to a first quasi-co-location type (e.g., QCL type A, QCL type B, QCL type C, QCL type D, QCL type E, etc.) indicated by the first downlink TCI state. Using / applying the at least two downlink TCI states to receive a downlink signal may include quasi-co-location of the DM-RS (or DM-RS antenna port) of one or more second downlink signals (e.g., PDSCH, PDCCH, CSI-RS, DMRS, etc.) 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 can be quasi-co-located with the second reference signal relative to a second quasi-co-site type (e.g., QCL Type A, QCL Type B, QCL Type C, QCL Type D, QCL Type E, etc.) indicated by a second downlink TCI state.

[0267] Using / applying the at least two downlink TCI states to receive a downlink signal may include one or more first downlink signals (e.g., CSI-RS, DMRS, etc.) quasi-co-located with a first reference signal indicated by the first downlink TCI state. The one or more first downlink signals may be quasi-co-located with the first reference signal relative to the first quasi-co-location type indicated by the first downlink TCI state. Using / applying the at least two downlink TCI states to receive a downlink signal may include one or more second downlink signals (e.g., CSI-RS, DMRS, etc.) quasi-co-located with a second reference signal indicated by the second downlink TCI state. The one or more second downlink signals may be quasi-co-located with the second reference signal relative to the second quasi-co-location type indicated by the second downlink TCI state.

[0268] 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 the first common / joint TCI state of the at least two common / joint TCI states. The second TCI state may be / include the second common / joint TCI state of the at least two common / joint TCI states. The wireless device may apply / use the at least two common / joint TCI states, for example, for receiving downlink signals (e.g., PDSCH, PDCCH, CSI-RS, DMRS, etc.) via the downlink BWP of the cell. The wireless device may apply / use the at least two common / joint TCI states, for example, for transmitting uplink signals (e.g., PUSCH, PUCCH, UCI, transport blocks, SRS, etc.) via the uplink BWP of the cell. The wireless device may apply / use the at least two common / joint TCI states to receive downlink signals and transmit uplink signals.

[0269] Using / applying the at least two common / joint TCI states to receive 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, for example, be the same as (or substantially the same, x degrees apart, x = 0, 1, 5, 10, etc.) as the spatial domain receive / receive filter / beam used to receive the first reference signal. The first spatial domain receive / receive filter / beam may, for example, be the same as (or substantially the same, x degrees apart, x = 0, 1, 5, 10, etc.) as the spatial domain transmit / transmit filter / beam used to send (e.g., transmit) the first reference signal. The downlink signal may include the one or more first downlink signals. Using / applying the at least two common / joint TCI states to receive 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, for example, be the same as (or substantially the same, x degrees apart, 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, for example, be the same as (or substantially the same, x degrees apart, x = 0, 1, 5, 10, etc.) as the spatial domain transmit / transmit filter / beam used to send (e.g., transmit) the second reference signal. The downlink signal may include the one or more second downlink signals.

[0270] Receiving a downlink signal using / applying the at least two common / joint TCI states may include quasi-co-location of the DMRS (or DM-RS antenna ports) of one or more first downlink signals (e.g., PDSCH, PDCCH, CSI-RS, DMRS, etc.) with a first reference signal indicated by the first common / joint TCI state. The DM-RS (or DM-RS antenna ports) of the one or more first downlink signals may be quasi-co-located with the first reference signal relative to a first quasi-co-location type (e.g., QCL type A, QCL type B, QCL type C, QCL type D, QCL type E, etc.) indicated by the first common / joint TCI state. Receiving a downlink signal using / applying the at least two common / joint TCI states may include quasi-co-location of the DMRS (or DM-RS antenna ports) of one or more second downlink signals (e.g., PDSCH, PDCCH, CSI-RS, DMRS, etc.) 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 can be quasi-co-located with the second reference signal relative to a second quasi-co-site 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.

[0271] Using / applying the at least two common / joint TCI states to receive downlink signals may include one or more first downlink signals (e.g., CSI-RS, DMRS, etc.) quasi-co-located with a first reference signal indicated by a first common / joint TCI state. The one or more first downlink signals may be quasi-co-located with the first reference signal relative to a first quasi-co-location type indicated by the first common / joint TCI state. Using / applying the at least two common / joint TCI states to receive downlink signals may include one or more second downlink signals (e.g., CSI-RS, DMRS, etc.) quasi-co-located with a second reference signal indicated by a second common / joint TCI state. The one or more second downlink signals may be quasi-co-located with the second reference signal relative to a second quasi-co-location type indicated by the second common / joint TCI state.

[0272] Transmitting uplink signals using / applying the at least two common / joint TCI states 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, for example, be the same as (or substantially the same, separated by x degrees, x = 0, 1, 5, 10, etc.) a spatial domain receive / receive filter / beam used to receive the first reference signal. The first spatial domain transmit / transmit filter / beam may, for example, be the same as (or substantially the same, separated by x degrees, x = 0, 1, 5, 10, etc.) a spatial domain transmit / transmit filter / beam used to send (e.g., transmit) the first reference signal. Transmitting uplink signals using / applying the at least two common / joint TCI states may include sending (e.g., transmitting) the one or more first uplink signals at a first transmit power, the first transmit power being determined based on one or more first power control parameters (e.g., target received power, closed loop index, path loss compensation factor, α, path loss reference signal, etc.) indicated by (or included in or associated with or mapped to) the first common / joint TCI state. The uplink signal may include the one or more first uplink signals.

[0273] Transmitting an uplink signal using / applying the at least two common / joint TCI states 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, for example, be the same as (or substantially the same, separated by x degrees, x = 0, 1, 5, 10, etc.) a spatial domain receive / receive filter / beam used to receive the second reference signal. The second spatial domain transmit / transmit filter / beam may, for example, be the same as (or substantially the same, separated by x degrees, x = 0, 1, 5, 10, etc.) a spatial domain transmit / transmit filter / beam used to send (e.g., transmit) the second reference signal. Transmitting an uplink signal using / applying the at least two common / joint TCI states may include sending (e.g., transmitting) the one or more second uplink signals at a second transmit power, the second transmit power being determined based on one or more second power control parameters (e.g., target received power, closed loop index, path loss compensation factor, α, path loss reference signal, etc.) indicated by (or included in or associated with or mapped to) the second common / joint TCI state. The uplink signal may include the one or more second uplink signals.

[0274] In at least some wireless communications, a unified / joint transmission configuration indicator (TCI) state may be used. For example, if a wireless device is indicated / activated with a unified / joint TCI state, the wireless device may apply the unified / joint TCI state to transmit all uplink signals (e.g., PUSCH / PUCCH / SRS) and receive all downlink signals (e.g., PDSCH / PDCCH / CSI-RS). Using a unified / joint TCI state may reduce the number / number of TCI state (or beam) activations for each channel individually, which may reduce beam activation signaling. By using a unified / joint TCI state with 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, wherein 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 fields, TRP fields, etc.) may be configured for uplink channels and downlink channels. The value of the field may indicate that a first unified / joint TCI and / or a second unified / joint TCI state is applied. In at least some instances, the base station may determine to switch to a single TRP mode and may therefore activate a single unified / joint TCI state. However, for example, depending on the position and / or speed of the wireless device relative to the base station, the wireless device may not be able to determine (e.g., within a sufficient time) that the base station has activated a single unified / joint TCI state. The wireless device may not be able to interpret / process that the base station switches from two unified / joint TCI states (e.g., dual TRP or multi-TRP mode) to a single unified / joint TCI state (e.g., single TRP mode). Additionally or alternatively, if the wireless device switches to a single unified TCI state, the wireless device may not be able to determine the TCI state for one or more channels. 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. If 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 a first channel having / using a first value of the unified TCI state field, and the wireless device may apply a second unified TCI state to a second channel having / using a second value of the unified TCI state field. However, if a single unified TCI state is switched (e.g., single TRP mode is turned on), the first value and the second value may not point to any relevant TCI state because there may be only a single unified TCI state that is activated. Therefore, for example, if a single unified TCI state is activated, such a wireless device may encounter difficulties in determining / selecting a TCI state for one or more channels.

[0275] As described herein, wireless communications for switching between two unified / joint TCI states and a single unified / joint TCI state may be enhanced. A wireless device may be configured such that if an uplink / downlink channel of the wireless device is configured with a field (e.g., a unified TCI state field, a TRP field, etc.), and if the wireless device is indicated / configured with a single unified / joint TCI state, the wireless device may perform one or more default operations (e.g., known to 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 channel, and / or the wireless device may pause / stop / clear / release transmission / reception of the uplink / downlink channel. The wireless device may pause / stop / clear / release transmission / reception, for example, based on a relationship / mapping / association between a single unified / joint TCI state TCI state and a TRP. As described herein (e.g., with respect to Figures 18A and 18B), by configuring the wireless device to operate in a predictable / default manner as described herein, the wireless device and base station can improve alignment in wireless communications, for example, if switching between two unified / joint TCI states versus a single unified / joint TCI state.

[0276] 18A and 18B illustrate an exemplary method for 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 for a cell. In step 1805, the base station may send (e.g., transmit) the one or more messages including the one or more configuration parameters to the wireless device. The one or more configuration parameters may indicate a plurality of TCI states. For example, the one or more configuration parameters may indicate the plurality of TCI states for an uplink BWP of a cell. For example, the one or more configuration parameters may indicate the plurality of TCI states for a downlink BWP of a cell.

[0277] The wireless device may activate (and / or set) an uplink BWP as an active uplink BWP for the cell. The wireless device may activate (and / or set) a downlink BWP as an 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.

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

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

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

[0281] The one or more configuration parameters may include / indicate a parameter indicating application / use of 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'.

[0282] At step 1820, the wireless device may receive an activation command (eg, MAC-CE, DCI) indicating activation of the subset of the plurality of TCI states. At step 1815, the base station may send (eg, transmit) an activation command indicating activation of the subset of the plurality of TCI states.

[0283] The wireless device may map a subset of the multiple TCI states to one or more TCI code points. Each of the one or more TCI code points may indicate a corresponding TCI state of the subset of the multiple TCI states. The base station may map the subset of the multiple TCI states to the one or more TCI code points.

[0284] The wireless device may receive a control message / command (e.g., DCI, MAC-CE) (e.g., at step 1820). The base station may send (e.g., transmit) a control message / command (e.g., at step 1815). The control message may indicate activation of at least two transmit configuration indicator (TCI) states. A subset of the multiple TCI states may include the at least two TCI states. The control message (e.g., DCI) may include a TCI field indicating the at least two TCI states. A TCI code point in the one or more TCI code points may indicate / include the at least two TCI states. The TCI field may indicate a TCI code point. 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 code points may be / include a single TCI code point.

[0285] The at least two TCI states may be / include at least two joint / common / unified TCI states. The at least two TCI states may be / include at least two joint / common / unified uplink states and a downlink TCI state. The at least two TCI states may be / include at least two joint / common / unified uplink TCI states. The at least two TCI states may be / include at least two uplink TCI states. The at least two TCI states may be / include at least two joint / common / unified downlink TCI states. The at least two TCI states may be / include at least two downlink TCI states.

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

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

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

[0289] 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 the first 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 second TCI state of the at least two TCI states. 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), the at least one TCI state may be the first TCI state and the second TCI state.

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

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

[0292] A control message (eg, DCI) may include a TCI field indicating a TCI state. A TCI code point in the one or more TCI code points may indicate / include a TCI state. A TCI field may indicate a TCI code point.

[0293] 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 code points may be / comprise a single TCI code point.

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

[0295] At step 1840, the wireless device may send (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. For example, regardless of the value of the field, the wireless device may send (e.g., transmit) an uplink signal via the uplink resource based on the TCI state. The wireless device may send (e.g., transmit) an uplink signal via the uplink resource based on the TCI state, for example, based on (e.g., in response to) the value of the ignore field. The wireless device may send (e.g., transmit) an uplink signal via the uplink resource based on the TCI state, for example, based on (e.g., in response to) a control message / command indicating activation of the TCI state. The wireless device may send (e.g., transmit) an uplink signal via the uplink resource based on the TCI state, for example, 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 wireless device may ignore the value of the field, for example, based on a control message / command indicating activation of a single / one TCI state.

[0296] In step 1845, the base station may receive an uplink signal via an uplink resource based on the TCI state indicated by the control message. For example, regardless of the value of the field, the base station may receive an uplink signal via an uplink resource based on the TCI state. The base station may receive an uplink signal via an uplink resource based on the TCI state, for example, based on (e.g., in response to) ignoring the value of the field. The base station may receive an uplink signal via an uplink resource based on the TCI state, for example, based on (e.g., in response to) a control message / command indicating activation of the TCI state. The base station may receive an uplink signal via an uplink resource based on the TCI state, for example, 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, for example, based on a control message / command indicating activation of a single / one TCI state.

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

[0298] The base station may apply / use the TCI state to receive an uplink signal via an uplink resource. Applying / using the at least one TCI state to receive an uplink signal via an uplink resource may include receiving an uplink signal via an uplink resource, the uplink signal having (or based on) a spatial domain receive filter determined based on a reference signal indicated by the TCI state.

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

[0300] The TCI state may be associated with a second value of a field (e.g., a unified / common / joint TCI state index field, a TRP index field, a control resource set pool index field, a PCI index, etc.). The one or more configuration parameters may be specific to the second value of the TCI state indication field. An activation command indicating activation of a subset of the plurality of TCI states may be specific to the second value of the TCI state indication field. A control message / command may be specific to the second value of the TCI state indication field.

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

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

[0303] 19A and 19B show examples of uplink transmission / reception. Fig. 20A 20A and 20B illustrate example methods for uplink transmission and reception, respectively. FIG21 illustrates an example method for uplink transmission.

[0304] The one or more configuration parameters may include a parameter indicating a configured uplink grant (eg, ConfiguredGrantConfig). 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.

[0305] For a configured uplink grant, the one or more configuration parameters may indicate at least two power control fields / parameters / values ​​(e.g., p0-PUSCH-Alpha). The at least two power control fields / parameters / values ​​may include / be at least two target receive power fields / parameters / values. The at least two power control fields / parameters / values ​​may include / be 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 include / be at least two path loss reference signals (e.g., pathlossReferenceIndex). The at least two power control fields / parameters / values ​​may include / be at least two closed loop indexes / values / fields (e.g., powerControlLoopToUse).

[0306] In FIG. 20 , at step 2010 , the wireless device may receive one or more configuration parameters. At step 2005 , the base station may send (e.g. , transmit) the one or more configuration parameters. The one or more configuration parameters may indicate at least two SRS resource indicator (SRI) fields for a configured uplink grant. The one or more configuration parameters may indicate at least two precodingAndNumberOfLayers fields for a configured uplink grant. The one or more configuration parameters (e.g. , 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 1st SRS resource set list in FIG. 19A and FIG. 19B ) and a second SRS resource set list (e.g. , the 2nd SRS resource set list in FIG. 19A and FIG. 19B ).

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

[0308] In FIG. 19A , a 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 , a second SRS resource set list may include at least two SRS resource sets. The number / number of SRS resource sets in the second SRS resource set list may be more than one. The number / number of SRS resource sets in the second SRS resource set list may be, for example, equal to two. The at least two SRS resource sets may include a first SRS resource set and a second SRS resource set. Fig. 20A In step 2015, the base station may determine a "no" path. In step 2020, the wireless device may select / determine the "no" path. The wireless device may select / determine the "no" path, for example, based on a first SRS resource set list that includes a single / one SRS resource set. The wireless device may select / determine the "no" path, for example, based on a first SRS resource set list that does not include two SRS resource sets (or more than one SRS resource set).

[0309] The one or more configuration parameters may indicate a purpose for an SRS resource set in the first SRS resource set list. For an SRS resource set, the one or more configuration parameters may include a purpose parameter (eg, purpose) indicating a purpose. The purpose may be, for example, set to 'codebook'. The purpose may be, for example, set to 'non-codebook'.

[0310] The one or more configuration parameters may indicate a purpose for the first SRS resource set in the second SRS resource set list. For the first SRS resource set, the one or more configuration parameters may include a purpose parameter (eg, purpose) indicating a purpose. The purpose may be, for example, set to 'codebook'. The purpose may be, for example, set to 'non-codebook'.

[0311] The one or more configuration parameters may indicate a purpose for the second SRS resource set in the second SRS resource set list. For the second SRS resource set, the one or more configuration parameters may include a purpose parameter (eg, purpose) indicating a purpose. The purpose may be, for example, set to 'codebook'. The purpose may be, for example, set to 'non-codebook'.

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

[0313] 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 / are {SRS resource 1, SRS resource 2, SRS resource 3, SRS resource 4}. 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}. 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 {SRS resource 1, SRS resource 2, SRS resource 3}. For example, if the number of SRS resources is equal to 4, the first SRS resource set in the second SRS resource set list may 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 be, for example, a subset of the SRS resource sets 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.

[0314] The second SRS resource set in the second SRS resource set list may not 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 second SRS resource set in the second SRS resource set list may not be associated. 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 associated, for example, based on the fact that the second SRS resource set in the second SRS resource set list is not a subset of the SRS resource set in the first SRS resource set list.

[0315] In FIG. 20 , at step 2010, 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, and two SRI fields for a configured uplink grant, and the base station may transmit (e.g., at step 2005) the configuration parameters. At step 2040, the wireless device may send (e.g., transmit) at least one transport block (or PUSCH transmission) for the configured uplink grant based on the at least two SRS resource sets in the second SRS resource set list. At step 2045, the base station may receive the at least one transport block for the configured uplink grant based on the at least two SRS resource sets in the second SRS resource set list. The wireless device may send (e.g., transmit) the at least one transport block for the configured uplink grant based on the first SRS resource set in the second SRS resource set list / the second SRS resource set list and the second SRS resource set in the second SRS resource set list / the second SRS resource set list.

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

[0317] The wireless device may send (e.g., transmit) the at least one transport block for a configured uplink grant based on the at least two SRS resource sets in the second SRS resource set list, 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 send (e.g., transmit) the at least one transport block for a configured uplink grant based on the at least two SRS resource sets in the second SRS resource set list, e.g., based on (e.g., in response to) the one or more configuration parameters indicating a single / one SRS resource set for the first SRS resource set list.

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

[0319] The wireless device may send (e.g., transmit) one or more first repetitions of the at least one transport block based on the first SRS resource set in the second SRS resource set list. The wireless device may send (e.g., transmit) the one or more first repetitions of the transport block with a first spatial domain transmit / transmit filter / beam. The wireless device may determine the first spatial domain transmit / transmit filter / beam based on the first SRS resource in the first SRS resource set. The first SRI field of the at least two SRI fields may indicate the first SRS resource. The number / number of SRS resources in the first SRS resource set may be greater than one. The number / 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 different from the first SRS resource.

[0320] The wireless device may send (e.g., transmit) one or more second repetitions of the at least one transport block based on a second SRS resource set in a second SRS resource set list. The wireless device may send (e.g., transmit) the 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 a second SRS resource set. The 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 an SRS resource different from the second SRS resource.

[0321] In FIG. 21 , at step 2110, the wireless device may receive, for example, from a base station, configuration parameters indicating a first SRS resource set list and a second SRS resource set list. The second SRS resource set list may include two SRS resource sets. At step 2120, the wireless device may receive an activation command (e.g., MAC-CE, DCI, SRS path loss reference RS update MAC CE), the activation command indicating activation / update of a path loss reference signal of 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 including the path loss reference signal for an SRS resource set (e.g., indicated by a higher layer / RRC parameter pathlossReferenceRSList). The activation command may include a first field including an SRS resource set index of an SRS resource set. The one or more configuration parameters may indicate an SRS resource set index for an 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 a path loss reference signal.

[0322] At step 2130, the wireless device may apply / use a path loss reference signal to an SRS resource set. The wireless device may apply / use a path loss reference signal to each SRS resource in the SRS resource set. Applying the path loss reference signal to the SRS resource set may include sending (e.g., transmitting) an SRS having a transmit power determined based on the path loss reference signal via an SRS resource in the SRS resource set. The wireless device may send (e.g., transmit) an SRS having a transmit power determined based on the path loss reference signal via an SRS resource in the SRS resource set. The wireless device may send (e.g., transmit) an SRS having a corresponding transmit power determined based on the path loss reference signal via each SRS resource in the SRS resource set. For example, the wireless device may send (e.g., transmit) a first SRS having a first transmit power determined based on the path loss reference signal via a first SRS resource in the SRS resource set. The wireless device may send (e.g., transmit) a second SRS having a second transmit power determined based on the path loss reference signal via a second SRS resource in the SRS resource set.

[0323] The wireless device may apply / use a path loss reference signal to a first SRS resource set in a second SRS resource set list. The wireless device may apply / use a path loss reference signal to each SRS resource in the first SRS resource set. Applying the path loss reference signal to the first SRS resource set may include sending (e.g., transmitting) an SRS with a transmit power determined based on the path loss reference signal via an SRS resource in the first SRS resource set. The wireless device may send (e.g., transmit) an SRS with a transmit power determined based on the path loss reference signal via an SRS resource in the first SRS resource set. The wireless device may send (e.g., transmit) an SRS with a corresponding transmit power determined based on the path loss reference signal via each SRS resource in the first SRS resource set. For example, the wireless device may send (e.g., transmit) a first SRS with a first transmit power determined based on the path loss reference signal via a first SRS resource in the first SRS resource set. The wireless device may send (e.g., transmit) a second SRS with a second transmit power determined based on the path loss reference signal via a second SRS resource in the first SRS resource set. For example, based on the SRS resource set in the first SRS resource set list being associated with the first SRS resource set in the second SRS resource set list, the wireless device may use the path loss reference signal for the first SRS resource set in the second SRS resource set list.

[0324] The wireless device may not apply / may not use the path loss reference signal for the second SRS resource set in the second SRS resource set list. The wireless device may send (e.g., transmit) an SRS with a transmit power determined based on the configured / activated path loss reference signal via the SRS resources in the second SRS resource set. The one or more configuration parameters may, for example, indicate the configured / activated path loss reference signal for the second SRS resource set. The wireless device may, for example, receive a MAC-CE indicating the configured / activated path loss reference signal for the second SRS resource set. For example, based on the fact that the SRS resource set in the first SRS resource set list and the second SRS resource set in the second SRS resource set list are not associated, the wireless device may not apply / use the path loss reference signal for the second SRS resource set in the second SRS resource set list.

[0325] 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 a path loss reference signal for a first SRS resource set in the 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 a path loss reference signal for a first SRS resource set in the second SRS resource set list, for example, based on the one or more configuration parameters indicating the first SRS resource set in / for the first SRS resource set list. The wireless device may / may not expect to 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 first SRS resource set in the 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 does / may not expect to 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.

[0326] The wireless device may receive an activation command (e.g., MAC-CE, DCI, SRS Path Loss Reference RS Update MACCE), the activation command 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 multiple path loss reference signals including the path loss reference signal for the second SRS resource set (e.g., indicated by a higher layer / RRC parameter pathlossReferenceRSList). The activation command may include a first field, the first field including a second SRS resource set index for the second SRS resource set. The one or more configuration parameters may indicate a 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 a 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 the one or more configuration parameters not indicating a second SRS resource set in a first SRS resource set list / for a first SRS resource set list. The wireless device may, for example, 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 based on the one or more configuration parameters indicating a single / one 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 the one or more configuration parameters not indicating a 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 the one or more configuration parameters indicating a single / one SRS resource set in / for the first SRS resource set list. The wireless device may apply / use the path loss reference signal for the second SRS resource set.

[0327] In FIG. 19B , the first SRS resource set list may include at least two SRS resource sets. The number / number of SRS resource sets in the first SRS resource set list may be more than one. The number / number of SRS resource sets in the first SRS resource set list may be, for example, equal to 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 more than one. The number of SRS resource sets in the second SRS resource set list may be, for example, equal to 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 a "yes" path, for example, based on a first SRS resource set list including more than one SRS resource set. The wireless device may select / determine the “yes” path, for example, based on the first SRS resource set list including the at least two SRS resource sets.

[0328] The one or more configuration parameters may indicate a usage for the first SRS resource set in the first SRS resource set list. For the first SRS resource set, the one or more configuration parameters may include a usage parameter (eg, usage) indicating a usage. The usage may be, for example, set to 'codebook'. The usage may be, for example, set to 'non-codebook'.

[0329] The one or more configuration parameters may indicate a purpose for the second SRS resource set in the first SRS resource set list. For the second SRS resource set, the one or more configuration parameters may include a purpose parameter (eg, purpose) indicating a purpose. The purpose may be, for example, set to 'codebook'. The purpose may be, for example, set to 'non-codebook'.

[0330] The one or more configuration parameters may indicate a purpose for the first SRS resource set in the second SRS resource set list. For the first SRS resource set, the one or more configuration parameters may include a purpose parameter (eg, purpose) indicating a purpose. The purpose may be, for example, set to 'codebook'. The purpose may be, for example, set to 'non-codebook'.

[0331] The one or more configuration parameters may indicate a purpose for the second SRS resource set in the second SRS resource set list. For the second SRS resource set, the one or more configuration parameters may include a purpose parameter (eg, purpose) indicating a purpose. The purpose may be, for example, set to 'codebook'. The purpose may be, for example, set to 'non-codebook'.

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

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

[0334] 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 in the first SRS resource set list / 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 in the first SRS resource set list may include / are {SRS resource 1, SRS resource 2, SRS resource 3, SRS resource 4}. 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}. 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 {SRS resource 1, SRS resource 2, SRS resource 3}. For example, if the number of SRS resources is equal to 4, the first SRS resource set in the second SRS resource set list may 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 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.

[0335] 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 in the first SRS resource set list / 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 in the first SRS resource set list may include / are {SRS resource 1, SRS resource 2, SRS resource 3, SRS resource 4}. 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}. 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 {SRS resource 1, SRS resource 2, SRS resource 3}. For example, if the number of SRS resources is equal to 4, the second SRS resource set in the second SRS resource set list may 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 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.

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

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

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

Claims

1. A method wherein include: One or more configuration parameters are received by a wireless device, the one or more configuration parameters indicating: a first sounding reference signal (SRS) resource set list, wherein the first sounding reference signal resource set list is configured with a single SRS resource set; a second SRS resource set list, the second SRS resource set list being associated with downlink control information (DCI) format 2_0; as well as at least two SRS Resource Indicator (SRI) fields for a configured uplink grant; as well as 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, a physical uplink shared channel (PUSCH) transmission is transmitted for the configured uplink grant using the at least two SRS resource sets of the second SRS resource set list.

2. The method according to claim 1, wherein the PUSCH transmission is transmitted using the at least two SRS resource sets of the second SRS resource set list. include: 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 The at least one transport block is transmitted 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. The method according to any one of claims 1 to 2, further comprising: include: 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; as well as determining that Ultra Reliable Low Latency Communication (URLLC) data is available for repetition in uplink transmission via one or more resources indicated by the at least two SRS resource sets of the second SRS resource set list, Wherein said transmitting said PUSCH transmission comprises transmitting said URLLC data in at least one repetition of at least one transport block.

4. The method according to any one of claims 1 to 3, wherein the one or more configuration parameters indicate: A first SRS resource set index of a first SRS resource set in the at least two SRS resource sets; and A second SRS resource set index of a second SRS resource set among the at least two SRS resource sets, wherein the first SRS resource set index is smaller than the second SRS resource set index.

5. The method according to any one of claims 1 to 4, further comprising: include: receiving, after said transmitting said PUSCH transmission, one or more second configuration parameters indicating that said first SRS resource set list is changed to include said at least two SRS resource sets; as well as Based on the first SRS resource set list including the at least two SRS resource sets, a second PUSCH transmission is transmitted for the configured uplink grant via one or more resources indicated by the at least two SRS resource sets of the first SRS resource set list.

6. The method according to any one of claims 1 to 5, in: A first SRI field of the at least two SRI fields indicates a first SRS resource in a first SRS resource set of the at least two SRS resource sets; and 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. A method wherein include: One or more configuration parameters are transmitted by a base station, the one or more configuration parameters indicating: a first sounding reference signal (SRS) resource set list, wherein the first sounding reference signal resource set list is configured with a single SRS resource set; a second SRS resource set list, the second SRS resource set list being associated with downlink control information (DCI) format 2_0; as well as at least two SRS Resource Indicator (SRI) fields for a configured uplink grant; as well as 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, a physical uplink shared channel (PUSCH) transmission is received for the configured uplink grant using the at least two SRS resource sets of the second SRS resource set list.

8. The method according to claim 7, wherein the PUSCH transmission is received using the at least two SRS resource sets of the second SRS resource set list. include: 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 The at least one transport block is received 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 method according to any one of claims 7 to 8, wherein the one or more configuration parameters indicate: A first SRS resource set index of a first SRS resource set in the at least two SRS resource sets; and A second SRS resource set index of a second SRS resource set among the at least two SRS resource sets, wherein the first SRS resource set index is smaller than the second SRS resource set index.

10. The method according to any one of claims 7 to 9, further comprising: include: after said receiving said PUSCH transmission, transmitting one or more second configuration parameters indicating that said first SRS resource set list is changed to include said at least two SRS resource sets; as well as Based on the first SRS resource set list including the at least two SRS resource sets, a second PUSCH is received for the configured grant via one or more resources indicated by the at least two SRS resource sets of the first SRS resource set list.

11. The method according to any one of claims 7 to 10, in: A first SRI field of the at least two SRI fields indicates a first SRS resource in a first SRS resource set of the at least two SRS resource sets; and 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 method according to any one of claims 7 to 11, in: The first SRS resource set list is indicated by an SRI field of a downlink control information (DCI) using a DCI format 0_1; and The second SRS resource set list is indicated by the SRI field of the DCI using DCI format 0_2.

13. A computing device, include: one or more processors; and a memory storing instructions that, when executed by the one or more processors, cause the computing device to perform: A method according to any one of claims 1 to 6; or A method according to any one of claims 7 to 12.

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

15. A computer readable medium storing instructions which, when executed, cause execution of: A method according to any one of claims 1 to 6; or A method according to any one of claims 7 to 12.