Candidate cell resource switching and timer operation

Abstract

A wireless device may initiate a random access procedure to a cell. The wireless device may not receive a random access response. If a random access procedure is initiated on a serving cell, the wireless device may stop the cell's bandwidth portion inactive timer and switch the cell's active bandwidth portion. However, if a random access procedure is initiated on a candidate cell, the wireless device may improve efficiency by not stopping the cell's bandwidth portion inactive timer and / or not switching the cell's active bandwidth portion.

Description

Summary of the Invention

[0001] Cross - reference to Related Applications This application claims the benefit of U.S. Provisional Patent Application No. 63 / 457,578, filed Apr. 6, 2023. The above - mentioned application is hereby incorporated by reference in its entirety.

Background Art

[0002] Wireless devices communicate with a base station. The wireless device receives configuration parameters for communicating via a cell.

[0003] The following summary shows a simplified overview of specific functions. The summary is not an extensive overview and is not intended to identify key or important elements.

[0004] A wireless device may initiate a random access procedure for a cell. The wireless device may, for example, not receive a random access response when the cell is a candidate cell for layer 1 / layer 2 trigger - type mobility procedures. In such examples, the wireless device may improve efficiency by not stopping the cell's bandwidth part inactive timer and not switching the cell's active bandwidth part. In multi - transmission - reception - point operation, the wireless device may, for example, monitor a control resource set associated with a first transmission - reception point when the cell's active bandwidth part is composed of a single reference signal resource set associated with the first transmission - reception point. By not monitoring control resource sets associated with other transmission - reception points, misalignment between the transmission pre - coder and the transmission beam can be avoided.

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

Brief Description of the Drawings

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

[0007] [Figure 1A] An example of a communication network is shown. [Figure 1B] An example of a communication network is shown. [Figure 2A] An exemplary user plane is shown. [Figure 2B] An exemplary control plane configuration is shown. [Figure 3] An example of a protocol layer is shown. [Figure 4A] This shows an exemplary downlink data flow for a user plane configuration. [Figure 4B] This shows an example format of a Media Access Control (MAC) subheader in a MAC Protocol Data Unit (PDU). [Figure 5A] An exemplary mapping of the downlink channel is shown. [Figure 5B] This shows an exemplary mapping of uplink channels. [Figure 6] Exemplary radio resource control (RRC) states and RRC state transitions are shown. [Figure 7] An example of a frame configuration is shown. [Figure 8] This shows an exemplary resource configuration for one or more carriers. [Figure 9] An exemplary configuration of the bandwidth portion (BWP) is shown. [Figure 10A] An exemplary carrier aggregation configuration based on component carriers is shown. [Figure 10B] A group of example cells is shown. [Figure 11A] This shows an exemplary mapping of one or more synchronous signal / physical broadcast channel (SS / PBCH) blocks. [Figure 11B] This shows an exemplary mapping of one or more channel status information reference signals (CSI-RS). [Figure 12A] An example of a downlink beam management procedure is shown. [Figure 12B] An example of an uplink beam management procedure is shown. [Figure 13A] An exemplary 4-step random access procedure is shown. [Figure 13B] An exemplary 2-step random access procedure is shown. [Figure 13C] An exemplary 2-step random access procedure is shown. [Figure 14A] An example of a control resource set (CORESET) configuration is shown. [Figure 14B] An example of the mapping of control channel elements to resource element groups (CCE-to-REG) is shown. [Figure 15A] An example of communication between a wireless device and a base station is shown. [Figure 15B] Exemplary elements of a computing device that can be used to implement any of the various devices described herein are shown. [Figure 16A] Examples of uplink and downlink signal transmissions are shown. [Figure 16B] Examples of uplink and downlink signal transmissions are shown. [Figure 16C] Examples of uplink and downlink signal transmissions are shown. [Figure 16D] Examples of uplink and downlink signal transmissions are shown. [Figure 17] An example of transmission configuration indicator (TCI) state activation is shown. [Figure 18] An example of TCI state activation is shown. [Figure 19] An example of beam misalignment in uplink scheduling is shown. [Figure 20A] An exemplary method of beam misalignment in uplink scheduling is shown. [Figure 20B] An exemplary method of beam misalignment in uplink scheduling is shown. [[ID=5〕] [Figure 21] An exemplary method of BWP management is shown. [Figure 22]An example method for managing BWP (Body Waste Management) is shown. [Modes for carrying out the invention]

[0008] The attached drawings and descriptions provide examples. The examples shown in the drawings and / or descriptions are non-exclusive, and it should be understood that the features illustrated and described may be practiced in other examples. Examples for the operation of wireless communication systems are provided.

[0009] Figure 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 communication network (PLMN) operated / managed / executed by a network operator. The communication network 100 may include one or more of the following: 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 one or more data networks (DNs) 108 (e.g., via CN 102). The wireless device 106 may communicate with one or more DNs 108, such as public DNs (e.g., the Internet), private DNs, and / or intra-operator DNs. The wireless device 106 may communicate with one or more DNs 108 via RAN 104 and / or CN 102. CN102 can provide / configure the wireless device 106 with one or more interfaces to one or more DN108s. As part of its interface functionality, CN102 can set up an end-to-end connection between the wireless device 106 and one or more DN108s, authenticate the wireless device 106, and provide / configure charging capabilities.

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

[0011] When used as a whole, the term “wireless device” may include one or more of the following: mobile devices, fixed (e.g., non-mobile) devices on which wireless communication is configured or enabled, computing devices, nodes, wirelessly radioactive devices, or any other devices capable of transmitting and / or receiving signals. In non-limiting examples, wireless devices may include, for example, telephones, mobile phones, Wi-Fi phones, smartphones, tablets, computers, laptops, sensors, meters, wearable devices, Internet of Things (IoT) devices, hotspots, cellular repeaters, vehicle roadside units (RSUs), relay nodes, automobiles, wireless user devices (e.g., user equipment (UE), user terminals (UT), etc.), access terminals (AT), mobile stations, handsets, wireless transmit and receive units (WTRUs), wireless communication devices, and / or any combination thereof.

[0012] RAN104 may include one or more base stations (not shown). As used throughout, the term “base station” may include one or more of the following: base station, node, node B (NB), evolutionary node B (eNB), gNB, ng-eNB, relay node (e.g., integrated access and backhaul (IAB) node), donor node (e.g., donor eNB, donor gNB), access point (e.g., Wi-Fi access point), transmit and receive point (TRP), computing device, wireless communication capable device, or other device capable of transmitting and / or receiving signals. A base station may include one or more of each of the elements listed above. For example, a base station may include one or more TRPs. Other non-limiting examples include, for example, a base station may include one or more of the following: Node B (e.g., associated with Universal Mobile Communications System (UMTS) and / or 3G standards), Evolutionary Node B (eNB) (e.g., associated with Evolutionary Universal Terrestrial Radio Access (E-UTRA) and / or 4G standards), Remote Radio Heads (RRHs), Baseband Processing Units coupled to one or more Remote Radio Heads (RRHs), Repeater or Transiting Nodes used to extend the coverage area of ​​a Donor Node, Next Generation Evolutionary Node B (ng-eNB), Generation Node B (gNB) (e.g., associated with NR and / or 5G standards), Access Points (APs) (e.g., associated with Wi-Fi or other suitable wireless communication standards), Base stations of other generations, 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)).

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

[0014] One or more base stations (e.g., in RAN104) may be implemented as sector sites having more or fewer than three sectors. One or more base stations in RAN104 may be implemented as access points, as baseband processing devices / units coupled to multiple RRHs, and / or as repeaters or relay nodes used to extend the coverage area of ​​a node (e.g., a donor node). Baseband processing devices / units coupled to RRHs may be part of a centralized or cloud RAN architecture, for example, the baseband processing devices / units may be centralized within a pool of baseband processing devices / units, or they may be virtualized. Repeater nodes may amplify and transmit (e.g., transmission, retransmission, rebroadcast, etc.) radio signals received from donor nodes. Relay nodes may perform substantially the same / similar functions as repeater nodes. Relay nodes may decode radio signals received from donor nodes to remove noise before amplifying and transmitting the radio signals.

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

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

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

[0018] CN152 (e.g., 5G-CN) may provide / configure a radio device 156 to one or more interfaces to one or more DNs 170, such as public DNs (e.g., the Internet), private DNs, and / or intra-operator DNs. As part of its interface functionality, CN152 (e.g., 5G-CN) may set up an end-to-end connection between the radio device 156 and one or more DNs, authenticate the radio device 156, and / or provide / configure charging functionality. CN152 (e.g., 5G-CN) may be a service-based architecture that differs from other CNs (e.g., 3GPP 4G CN). The node architecture of CN152 (e.g., 5G-CN) may be defined as a network function that provides services via interfaces to other network functions. The network functionality of CN152 (e.g., 5G CN) can 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).

[0019] CN152 (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 a single component AMF / UPF device 158. The UPF device 158B may function as a gateway between RAN154 (e.g., NG-RAN) and one or more DN170s. The UPF device 158B may perform functions such as packet routing and forwarding, packet inspection and enforcement of user plane policy rules, traffic usage reporting, uplink classification supporting routing of traffic flows to one or more DN170s, quality of service (QoS) processing for the user plane (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink traffic validation), downlink packet buffering, and / or downlink data notification triggers. UPF device 158B may support multi-homed PDU sessions by functioning as an anchor point for intra / inter-radio access technology (RAT) mobility, an external protocol (or packet) data unit (PDU) session point interconnected to one or more DNs, and / or a branch point. Radio device 156 may be configured to receive services via PDU sessions, which may be logical connections between the radio device and the DN.

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

[0021] CN152 (e.g., 5G-CN) may include one or more additional network functions not shown in Figure 1B. CN152 (e.g., 5G-CN) may include one or more devices implementing at least one of the following functions: Session Management Function (SMF), NR Repository Function (NRF), Policy Control Function (PCF), Network Exposure Function (NEF), Unified Data Management (UDM), Application Function (AF), Authentication Server Function (AUSF), and / or any other functions.

[0022] RAN154 (e.g., NG-RAN) may communicate with radio device 156 via radio communication (e.g., via an air interface). Radio device 156 may communicate with CN152 via RAN154. RAN154 (e.g., NG-RAN) may include one or more base stations of a first type (e.g., gNB160A and gNB160B (collectively gNB160)) and / or one or more base stations of a second type (e.g., ng-eNB162A and ng-eNB162B (collectively ng eNB162)). RAN154 may include one or more of any number of base station types. gNB160 and ng eNB162 may be called base stations. A base station (e.g., gNB160 and ng eNB162) may include one or more sets of antennas for radio communication (e.g., via an air interface) with radio device 156. One or more base stations (e.g., gNB160 and / or ng-eNB162) may include multiple antenna sets for controlling multiple cells (or sectors), each of which may include multiple antenna sets. The cells of the base stations (e.g., gNB160 and ng-eNB162) may provide radio coverage to radio devices 156 over a wide geographical area to support radio device mobility.

[0023] A base station (e.g., gNB160 and / or ng-eNB162) may be connected to CN152 (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 on an underlying transport network, such as an Internet Protocol (IP) transport network, using direct physical and / or indirect connections. A base station (e.g., gNB160 and / or ng-eNB162) may communicate with a radio device 156 via a third interface (e.g., Uu interface). A base station (e.g., gNB160A) may communicate with a radio device 156A via the Uu interface. The NG, Xn, and Uu interfaces may be associated with a protocol stack. The protocol stack associated with the interfaces may be used by the network elements shown in Figure 1B to exchange data and signaling messages. The protocol stack may include two planes, namely the user plane and the control plane. Any other amount of planes may be used (e.g., within the protocol stack). The user plane may process data of interest to the user. The control plane may process signaling messages of interest to network elements.

[0024] One or more base stations (e.g., gNB160 and / or ng-eNB162) may communicate with one or more AMF / UPF devices, such as AMF / UPF158, via one or more interfaces (e.g., NG interfaces). A base station (e.g., gNB160A) may communicate with and / or connect to the UPF158B of the AMF / UPF158 via the NG user plane (NG-U) interface. The NG-U interface may provide / implement the delivery (e.g., unguaranteed delivery) of user plane PDUs between the base station (e.g., gNB160A) and the UPF device (e.g., UPF158B). A base station (e.g., gNB160A) may communicate with and / or connect to an AMF device (e.g., AMF158A) via the NG control plane (NG-C) interface. The NG-C interface may provide / perform, for example, NG interface management, wireless device context management (e.g., UE context management), wireless device mobility management (e.g., UE mobility management), NAS message transport, paging, PDU session management, configuration transfer, and / or warning message sending.

[0025] A radio device may access a base station via an interface (e.g., a Uu interface) for user plane and control plane configurations. A base station (e.g., gNB160) may provide user plane and control plane protocol terminations to radio device 156 via a Uu interface. A base station (e.g., gNB160A) may provide user plane and control plane protocol terminations to radio device 156A on a Uu interface associated with a first protocol stack. A base station (e.g., ng-eNB162) may provide Evolutionary UMTS Terrestrial Radio Access (E UTRA) user plane and control plane protocol terminations to radio device 156 via a Uu interface (e.g., E UTRA may refer to 3GPP 4G radio access technology). A base station (e.g., ng-eNB162B) may provide E UTRA user plane and control plane protocol terminations to radio device 156B via a Uu interface associated with a second protocol stack. User plane and control plane protocol terminations may include, for example, NR user plane and control plane protocol terminations, 4G user plane and control plane protocol terminations, and so on.

[0026] A CN152 (e.g., 5G-CN) may be configured to handle one or more radio accesses (e.g., NR, 4G, and / or any other radio access). An NR network / device (or any first network / device) may also be able to connect to a 4G core network / device (or any second network / device) in non-standalone mode (e.g., non-standalone operation). In non-standalone mode / operation, the 4G core network may be used to provide (or at least support) control plane functions (e.g., initial access, mobility, and / or paging). Although only one AMF / UPF158 is shown in Figure 1B, one or more base stations (e.g., one or more gNBs and / or one or more ng-eNBs) may be connected to multiple AMF / UPF nodes, for example, to provide redundancy and / or load sharing across multiple AMF / UPF nodes.

[0027] Interfaces between network elements (e.g., network elements shown in Figure 1B) (e.g., Uu, Xn, and / or NG interfaces) may be associated with a protocol stack that 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 may be used (e.g., within the protocol stack). 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).

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

[0029] Figure 2A shows an exemplary user plane configuration. The user plane configuration may include, for example, an NR user plane protocol stack. Figure 2B shows 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 configurations and / or control plane configurations may use a possible Uu interface between the radio device 210 and the base station 220. The protocol stacks shown in Figures 2A and 2B may be substantially the same as or similar to those used for the Uu interface between the radio device 156A and the base station 160A shown in Figure 1B.

[0030] The user plane configuration (e.g., the NR user plane protocol stack) may include multiple layers (e.g., five layers or any other number of layers) implemented in the radio device 210 and base station 220 (e.g., as shown in Figure 2A). At the bottom of the protocol stack, the physical layers (PHYs) 211 and 221 may provide transport services to the upper layers of the protocol stack and may correspond to layer 1 of the Open Systems Interconnection (OSI) model. The protocol layers above PHY 211 may include the Medium Access Control Layer (MAC) 212, the Radio Link Control Layer (RLC) 213, the Packet Data Convergence Protocol Layer (PDCP) 214, and / or the Service Data Application Protocol Layer (SDAP) 215. The protocol layers above PHY 221 may include the Medium Access Control Layer (MAC) 222, the Radio Link Control Layer (RLC) 223, the Packet Data Convergence Protocol Layer (PDCP) 224, and / or the Service Data Application Protocol Layer (SDAP) 225. One or more of the four protocol layers on PHY211 may correspond to layer 2 or the data link layer of the OSI model. One or more of the four protocol layers on PHY221 may correspond to layer 2 or the data link layer of the OSI model.

[0031] Figure 3 shows an example of a protocol layer. The protocol layer may include, for example, the protocol layer of the NR user plane protocol stack. One or more services may be provided between the protocol layers. SDAP (e.g., SDAP215 and 225 shown in Figures 2A and 3) may perform quality of service (QoS) flow processing. Radio devices (e.g., radio devices 106, 156A, 156B, and 210) may receive services via / through a PDU session, which may be a logical connection between the radio device and the DN. A PDU session may have one or more QoS flows 310. The CN's UPF (e.g., UPF158B) may map IP packets to one or more QoS flows of the PDU session based on, for example, one or more QoS requirements (e.g., delay, data rate, error rate, and / or any other quality / service requirements). SDAP215 and 225 may perform mapping / unmapping 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 radio device 210 may be informed of the mapping between QoS flows 310 and radio bearers 320 via reflected mapping and / or control signaling received from the base station 220. For reflected mapping, the SDAP 225 of the base station 220 may determine the mapping / demapping between one or more QoS flows 310 and radio bearers 320 by marking downlink packets with QoS flow indicators (QFIs) that can be monitored / detected / identified / indicated / observed by the SDAP 215 of the radio device 210.

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

[0033] The PDCP layer (e.g., PDCP214 and 224) may perform mapping / demapping between segmented radio bearers and RLC channels (e.g., RLC channel 330) (e.g., in dual-connectivity scenarios / configurations). Dual-connectivity may refer to a technique that enables a radio device to communicate with multiple cells (e.g., two cells), or more broadly, multiple cell groups, including a master cell group (MCG) and secondary cell groups (SCG). Segmented bearers may be configured and / or used, for example, when a single radio bearer (e.g., one of the radio bearers provided / configured by PDCP214 and 224 as a service to SDAP215 and 225) is handled by a cell group in a dual-connectivity scenario. PDCP214 and 224 may map / demap segmented radio bearers to and from RLC channels 330 belonging to the cell group.

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

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

[0036] The PHY layer (e.g., PHY211 and 221) may perform mapping of transport channels to physical channels and / or digital and analog signal processing functions for transmitting and / or receiving information (e.g., via an air interface). Digital and / or analog signal processing functions may include, for example, coding / decoding and / or modulation / demodulation. The PHY layer (e.g., PHY211 and 221) may perform multi-antenna mapping. The PHY layer (e.g., PHY211 and 221) may provide / configure one or more transport channels (e.g., transport channel 350) as a service to the MAC layer (e.g., MAC212 and 222, respectively).

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

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

[0039] Each protocol layer (e.g., the protocol layer as shown in Figure 4A), or at least some protocol layers, may perform its own function (e.g., one or more functions of each protocol layer as described with respect to Figure 3), add the corresponding header, and / or forward its respective output to the next lower layer (e.g., the layer below it). PDCP224 may perform IP header compression and / or encryption. PDCP224 may forward its output (e.g., a PDCP PDU which is an RLC SDU) to RLC223. RLC223 may optionally perform segmentation (e.g., as shown for the IP packet in Figure 4A). RLC223 may forward its output (e.g., two RLC PDUs which are two MAC SDUs generated by adding their respective subheaders to two SDU segments (SDU Segs)) to MAC222. MAC222 can multiplex the quantity / number of RLC PDUs (MAC SDUs). MAC222 can form a TB by attaching a MAC subheader to the RLC PDU (MAC SDU). The MAC subheader can be distributed across the MAC PDU (e.g., in an NR configuration, as shown in Figure 4A). The MAC subheader can be located entirely at the beginning of the MAC PDU (e.g., in an LTE configuration). The NR MAC PDU structure can reduce processing time and / or associated delays, for example, if the MAC PDU subheader is computed before assembling the complete MAC PDU.

[0040] Figure 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 to indicate the length (e.g., bytes) of the MAC SDU to which the MAC subheader corresponds, a logical channel identifier (LCID) field to identify / indicate the logical channel initiated by the MAC SDU to assist in the multiplexing process, a flag (F) to indicate the size of the SDU length field, and a reserved bit (R) field for future use.

[0041] One or more MAC control elements (CEs) may be added to or inserted into a MAC PDU by a MAC layer such as MAC223 or MAC222. Two MAC CEs may be inserted / added before two MAC PDUs, as shown in Figure 4B. MAC CEs may be inserted / added at the beginning of a MAC PDU for downlink transmission (as shown in Figure 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. Examples of MAC CEs include scheduling-related MAC CEs such as buffer status reports and power headroom reports, activation / deactivation MAC CEs (e.g., activation / deactivation of PDCP duplicate detection, channel status information (CSI) reports, sounding reference signal (SRS) transmission, and MAC CEs for pre-configured components), discontinuous receive (DRX)-related MAC CEs, timing advance MAC CEs, and random access-related MAC CEs. A MAC CE may be preceded by a MAC subheader in a format similar to that described for MAC SDUs, and may be identified by a reserved value in the LCID field indicating the type of control information contained in the corresponding MAC CE.

[0042] Figure 5A shows an exemplary mapping of downlink channels. Uplink channel mapping may include mappings between downlink channels (e.g., logical channels, transport channels, and physical channels). Figure 5B shows an exemplary mapping of uplink channels. Uplink channel mapping 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 the protocol stack (e.g., the NR protocol stack). Logical channels may be used between the RLC layer and the MAC layer. Logical channels may be classified / represented as control channels that can carry control and / or configuration information (e.g., within the NR control plane) or as traffic channels that can carry data (e.g., within the NR user plane). Logical channels may be classified / represented as dedicated logical channels that may be exclusive to a particular radio device and / or as common logical channels that may be used by one or more radio devices (e.g., a group of radio devices).

[0043] A logical channel can be defined by the type of information it carries. A set of logical channels (for example, in an NR configuration) may include one or more channels as described below: A paging control channel (PCCH) may contain or carry one or more paging messages used for paging wireless devices whose location is unknown to the network at the cell level. A broadcast control channel (BCCH) may contain / carry system information messages in the form of master information blocks (MIBs) and several system information blocks (SIBs). System information messages may be used by wireless devices to obtain information about how a cell is configured and how it operates within the cell. A common control channel (CCCH) may contain / carry control messages along with random access. A dedicated control channel (DCCH) may contain / carry control messages to / from a specific wireless device and configure the wireless device with configuration information. A dedicated traffic channel (DTCH) may contain / carry user data to / from a specific wireless device.

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

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

[0046] The physical layer may generate physical signals to support the low-level operation of the physical layer, which may be analogous to a physical control channel. As shown in Figures 5A and 5B, physical layer signals (which may be defined, for example, by an NR configuration or other configuration) may include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a channel status 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 other arbitrary signals.

[0047] One or more 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). Figure 2B shows an example of a control plane configuration (e.g., an NR control plane protocol stack). In Figure 2B, the control plane configuration (e.g., an NR control plane protocol stack) may use one or more substantially identical / similar protocol layers (e.g., PHY211 and 221, MAC212 and 222, RLC213 and 223, and PDCP214 and 224) as an exemplary user plane configuration (e.g., an NR user plane protocol stack). Four similar protocol layers may include PHY211 and 221, MAC212 and 222, RLC213 and 223, and PDCP214 and 224. The control plane configuration (e.g., NR control plane stack) may have, for example, the Radio Resource Control (RRC) 216 and 226 and NAS protocols 217 and 237 at the top of the control plane configuration (e.g., NR control plane protocol stack), instead of having SDAP 215 and 225. The control plane configuration may also include the AMF 230, which includes the NAS protocol 237.

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

[0049] RRC layers 216 and 226 may provide / configure control plane functionality between the radio device 210 and the base station 220 and / or more generally between the radio device 210 and the RAN (e.g., base station 220). RRC layers 216 and 226 may provide / configure control plane functionality between the radio device 210 and the base station 220 via signaling messages, which may be called RRC messages. RRC messages may be transmitted between the radio device 210 and the RAN (e.g., base station 220) using a signaling radio bearer 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. RRC layers 216 and 226 may provide / configure control plane functions such as broadcasting system information related to the AS and NAS, paging initiated by the CN or RAN, establishing, maintaining, and releasing RRC connections between the radio device 210 and the RAN (e.g., base station 220), security functions including key management, establishing, configuring, maintaining, and releasing signaling radio bearers and data radio bearers, mobility functions, QoS management functions, radio device measurement reports (e.g., radio device measurement reports) and report control, detection and recovery from radio link failures (RLFs), and / or NAS message forwarding functions. As part of establishing an RRC connection, RRC layers 216 and 226 may establish an RRC context, which may involve configuring parameters for communication between the radio device 210 and the RAN (e.g., base station 220).

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

[0051] An RRC connection may be established for a radio device. For example, this may occur during an RRC connection state. During an RRC connection state (e.g., during RRC connection 602), the radio device may have an established RRC context and may have at least one RRC connection with a base station. The base station may be one of several base stations (e.g., one or more base stations of RAN104 shown in Figure 1A, one of gNB160 or ng-eNB162 shown in Figure 1B, base station 220 shown in Figures 2A and 2B, or any other base station). The base station to which the radio device is connected (e.g., which has established an RRC connection) may have an RRC context for the radio device. The RRC context, which may be called the radio device context (e.g., UE context), may contain parameters for communication between the radio 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 bearer, signaling radio bearer, logical channel, QoS flow, and / or PDU session), security information, and / or layer configuration information (e.g., PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information). During an RRC connection state (e.g., RRC connection 602), the mobility of the radio device may be managed / controlled by the RAN (e.g., RAN104 or NG RAN154). The radio device may measure received signal levels (e.g., reference signal level, reference signal received power, reference signal received quality, received signal strength indicator, etc.) based on one or more signals transmitted from the serving cell and adjacent cells. The radio device may report these measurements to the serving base station (e.g., the base station currently providing service to the radio device). The serving base station of the radio device may, for example, request a handover to one of the adjacent base stations' cells based on the reported measurements. 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 the connection release procedure 608.The RRC state can transition from an RRC connected state (e.g., RRC connected 602) to an RRC inactive state (e.g., RRC inactive 604) via the connection deactivation procedure 610.

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

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

[0054] RRC states can be associated with mobility management mechanisms. During RRC idle states (e.g., RRC idle 606) and RRC inactive states (e.g., RRC inactive 604), mobility can be managed / controlled by radio devices via cell reselection. The purpose of mobility management during RRC idle states (e.g., RRC idle 606) or RRC inactive states (e.g., RRC inactive 604) may be to enable / enable the network to notify radio devices of events via paging messages without having to broadcast paging messages across the entire mobile communications network. Mobility management mechanisms used during RRC idle states (e.g., RRC idle 606) or RRC inactive states (e.g., RRC inactive 604) may enable / enable the network to track radio devices at the cell group level so that paging messages can be broadcast across cells in the cell group in which the radio device is currently located (e.g., rather than sending paging messages across the entire mobile communications network). The mobility management mechanism in the RRC idle state (e.g., RRC idle 606) and the RRC inactive state (e.g., RRC inactive 604) may track wireless devices at the cell group level. The mobility management mechanism may perform tracking using, for example, different levels of grouping. There may be multiple levels of cell grouping granularity (e.g., three levels of cell grouping granularity: individual cells, cells within a RAN area identified by a RAN area identifier (RAI), and cells within a group of RAN areas identified by a tracking area identifier (TAI), called a tracking area).

[0055] A tracking area can be used to track a radio device (e.g., to track the location of a radio device at the CN level). A CN (e.g., CN102, 5G CN152, or any other CN) may transmit a list of TAIs associated with radio device registration areas (e.g., UE registration areas) to a radio device. The radio device may perform a registration update with the CN to allow the CN to update the radio device's location, for example, if the radio device moves to a cell associated with a TAI that is not included in the list of TAIs associated with UE registration areas (e.g., via cell reselection), providing the radio device with a new UE registration area.

[0056] RAN areas may be used to track radio devices (e.g., the location of a radio device at the RAN level). For radio devices in an RRC inactive state (e.g., RRC inactive 604), the radio device may be assigned / provided / configured in a RAN notification area. A RAN notification area may contain one or more cell identification information (e.g., a list of RAIs and / or a list of TAIs). A base station may belong to one or more RAN notification areas. A cell may belong to one or more RAN notification areas. A radio device may perform a notification area update in the RAN to update its RAN notification area, for example, if the radio device moves to a cell that is not included in the RAN notification area to which it is assigned / provided / configured (e.g., via cell reselection).

[0057] A base station that stores the RRC context for a radio device, or the final serving base station of a radio device, may be called an anchor base station. The anchor base station may maintain the RRC context for the radio device for at least the duration that the radio device remains in the anchor base station's RAN notification area and / or the duration that the radio device remains in an RRC inactive state (e.g., RRC inactive 604).

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

[0059] Physical signals and physical channels (e.g., Figures 5A and 5B) can be mapped onto one or more symbols (e.g., orthogonal frequency division multiplexing (OFDM) symbols in an NR configuration, or any other symbols). OFDM is a multicarrier communication scheme that transmits / transmits data via F orthogonal subcarriers (or tones). The data, called source symbols, can be mapped to a set of complex symbols (e.g., M orthogonal amplitude modulation (M-QAM) symbols or M phase shift key (M PSK) symbols or any other modulation symbols) which are divided into F parallel symbol streams before the data is transmitted. The F parallel symbol streams can be treated 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 converts them to the time domain. The IFFT block can take F source symbols at a time, one 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 an F-time-domain sample representing the sum of F-orthogonal subcarriers. An F-time-domain sample can form a single OFDM symbol. The OFDM symbol provided / output by the IFFT block can be transmitted / transmitted over the air interface at the carrier frequency after, for example, one or more processes (e.g., the addition of a cyclic prefix) and upconversion. The F-parallel symbol streams may be mixed using a Fast Fourier Transform (FFT) block before being processed by the IFFT block. This operation can generate an OFDM symbol precoded with a Discrete Fourier Transform (DFT), which may be used by one or more radio devices on the uplink to reduce the peak-to-average power ratio (PAPR). Inverse processing may be performed on the OFDM symbol at the receiver using an FFT block to reconstruct the data mapped to the source symbol.

[0060] Figure 7 shows an exemplary frame configuration. A frame may include, for example, an NR radio frame in which OFDM symbols may be grouped. A frame (e.g., an NR radio frame) may be identified / indicated by a System Frame Quantity / Number (SFN) or any other value. The SFN may repeat over a period of 1024 frames. A single NR frame may have a duration of 10 milliseconds (ms) and may contain 10 subframes, each with a duration of 1 millisecond. A subframe may be divided into one or more slots (e.g., depending on the numerology and / or different subcarrier intervals). Each of the one or more slots may contain, for example, 14 OFDM symbols per slot. Any amount of symbols, slots, or durations may be used for any time interval.

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

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

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

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

[0065] The configuration of one or more Bandwidth Parts (BWPs) may support one or more radio devices that cannot receive the full carrier bandwidth. BWPs may, for example, support bandwidth adaptation for such radio devices that cannot receive the full carrier bandwidth. A BWP (e.g., a BWP in an NR configuration) may be defined by a subset of consecutive RBs on the carrier. A radio device may consist of one or more downlink BWPs and one or more uplink BWPs per serving cell (e.g., up to four downlink BWPs and up to four uplink BWPs per serving cell) (e.g., via the RRC layer). One or more of the BWPs configured for a serving cell may be active, for example, at a given time. One or more BWPs may be called the active BWPs of a serving cell. A serving cell may have one or more first active BWPs on the uplink carrier and, for example, one or more second active BWPs on the secondary uplink carrier if the serving cell consists of a secondary uplink carrier.

[0066] A downlink BWP from a set of configured downlink BWPs can be linked with an uplink BWP from a set of configured uplink BWPs (for example, for unpaired spectra). Downlink BWPs and uplink BWPs can be linked, for example, if the downlink BWP index of one downlink BWP and the uplink BWP index of the other uplink BWP are the same. A wireless device can expect that the center frequency of a downlink BWP is the same as the center frequency of an uplink BWP (for example, for unpaired spectra).

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

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

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

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

[0071] A base station may configure a radio device with a BWP inactivity timer value for PCell. The radio device may start or restart the BWP inactivity timer at any appropriate time. The radio device may start or restart the BWP inactivity timer if, for example, one or more conditions are met. One or more conditions may include at least one of the following: the radio device detects a DCI indicating an active downlink BWP other than the default downlink BWP for paired spectral operations; the radio device detects a DCI indicating an active downlink BWP other than the default downlink BWP for unpaired spectral operations; and / or the radio device detects a DCI indicating an active uplink BWP other than the default uplink BWP for unpaired spectral operations. The radio device may start / run the BWP inactivity timer toward expiration (e.g., increment from zero to the BWP inactivity timer value or decrement from the BWP inactivity timer value to zero) if the radio device does not detect a DCI during a time interval (e.g., 1 millisecond or 0.5 milliseconds). A wireless device may switch from an active downlink BWP to a default downlink BWP, for example, when the BWP non-activity timer expires.

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

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

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

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

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

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

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

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

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

[0081] DCI may include control information such as scheduling assignments and scheduling grants for cells. DCI may be transmitted / transmitted through the cell corresponding to the scheduling assignment and / or scheduling grant, which may be called self-scheduling. DCI containing cell control information may be transmitted / transmitted through another cell, which may be called cross-carrier scheduling. Uplink control information (UCI) may include control information such as HARQ acknowledgments and channel state feedback (e.g., CQI, PMI, and / or RI) for aggregation cells. UCI may be transmitted / transmitted through the uplink control channel (e.g., PUCCH) of a PCell or a specific SCell (e.g., a SCell composed of PUCCHs). If the amount / number of aggregated downlink CCs is large, the PUCCH of the PCell may become overloaded. A cell may be divided into multiple PUCCH groups.

[0082] Figure 10B shows an exemplary group of cells. An aggregation cell may consist of one or more PUCCH groups (for example, as shown in Figure 10B). One or more cell groups or one or more uplink control channel groups (e.g., PUCCH group 1010 and PUCCH group 1050) may each contain one or more downlink CCs. PUCCH group 1010 may contain one or more downlink CCs, for example, three downlink CCs, i.e., PCell 1011 (e.g., DL PCC), SCell 1012 (e.g., DL SCC), and SCell 1013 (e.g., DL SCC). PUCCH group 1050 may contain one or more downlink CCs, for example, three downlink CCs, i.e., PUCCH SCell (or PSCell) 1051 (e.g., DL SCC), SCell 1052 (e.g., DL SCC), and SCell 1053 (e.g., DL SCC). One or more uplink CCs of PUCCH group 1010 may be configured as PCell1021 (e.g., UL PCC), SCell1022 (e.g., UL SCC), and SCell1023 (e.g., UL SCC). One or more uplink CCs of PUCCH group 1050 may be configured as PUCCH SCell (or PSCell)1061 (e.g., UL SCC), SCell1062 (e.g., UL SCC), and SCell1063 (e.g., UL SCC). UCIs associated with downlink CCs of PUCCH group 1010, indicated as UCI1031, UCI1032, and UCI1033, may be transmitted / transmitted via the uplink of PCell1021 (e.g., via the PUCCH of PCell1021). The UCIs associated with the downlink CC of PUCCH group 1050, indicated as UCI1071, UCI1072, and UCI1073, may be transmitted / transmitted via the uplink of PUCCH SCell (or PSCell) 1061 (for example, via the PUCCH of PUCCH SCell 1061).A single uplink PCell may be configured to transmit / transmit UCIs associated with six downlink CCs, for example, when the aggregation cell shown in Figure 10B is not divided into PUCCH group 1010 and PUCCH group 1050. PCell 1021 may become overloaded if, for example, UCIs 1031, 1032, 1033, 1071, 1072, and 1073 are transmitted / transmitted through PCell 1021. Overload can be prevented and / or reduced by separating the transmission of UCIs between PCell 1021 and PUCCH SCell (or PSCell) 1061.

[0083] A PCell may include a downlink carrier (e.g., PCell1011) and an uplink carrier (e.g., PCell1021). An SCell may include only a downlink carrier. A cell containing a downlink carrier and optionally an uplink carrier may be assigned a physical cell ID and a cell index. The physical cell ID or cell index may, for example, display / identify the cell's downlink carrier and / or uplink carrier, depending on the context in which the physical cell ID is used. The physical cell ID may be determined, for example, using synchronization signals (e.g., PSS and / or SSS) transmitted over the downlink component carrier. The cell index may be determined, for example, using one or more RRC messages. The physical cell ID may be called a carrier ID, and the cell index may be called a carrier index. A first physical cell ID for a first downlink carrier may refer to a first physical cell ID for a cell containing the first downlink carrier. Substantially the same / similar concepts may apply, for example, to carrier activation. Activation of the first carrier may refer to the activation of the cell containing the first carrier.

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

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

[0086] Figure 11A shows an exemplary mapping of one or more SS / PBCH blocks. A burst of SS / PBCH blocks may consist of one or more SS / PBCH blocks (e.g., four SS / PBCH blocks as shown in Figure 11A). Bursts may be transmitted / transmitted periodically (e.g., every two frames, every 20 milliseconds, or at any other duration). Bursts may be limited to half frames (e.g., a first half frame with a duration of 5 milliseconds). These parameters (e.g., the amount / number of SS / PBCH blocks per burst, the periodicity of the burst, the location of the burst within a frame) may be configured based on at least one of the following: for example, the carrier frequency of the cell to which the SS / PBCH blocks are transmitted / transmitted, the cell numerology or subcarrier spacing, the network configuration (e.g., using RRC signaling), and / or any other preferred factors. A wireless device may assume subcarrier spacing for SS / PBCH blocks based on the monitored carrier frequency, for example, unless the wireless network configures a wireless device that assumes different subcarrier spacings.

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

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

[0089] SS / PBCH blocks can be used by a radio device to determine one or more parameters of a cell. For example, a radio device may determine the physical cell identifier (PCI) of a cell based on the PSS and SSS arrays, respectively. A radio device may determine the location of a cell's frame boundary based on the location of an SS / PBCH block. An SS / PBCH block may indicate that it was transmitted / transmitted according to a transmission pattern. An SS / PBCH block in a transmission pattern may be a known distance from the frame boundary (e.g., a predefined distance for a RAN configuration between one or more networks, one or more base stations, and one or more radio devices).

[0090] The PBCH may use QPSK modulation and / or forward error correction (FEC). FEC may use polarity coding. One or more symbols straddled by the PBCH may include / carry one or more DM-RS for demodulation of the PBCH. The PBCH may include indications of the cell's current system frame quantity / number (SFN) and / or SS / PBCH block timing index. These parameters may facilitate time synchronization of radio devices to base stations. The PBCH may include an MIB used to transmit one or more parameters to radio devices. The MIB can be used by radio devices to find the remaining minimum system information (RMSI) associated with the cell. The RMSI may include a System Information Block Type 1 (SIB1). The SIB1 may contain information for radio devices to access the cell. Radio devices 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 the SIB1. The SIB1 can be decoded using parameters provided / included in the MIB. A PBCH can indicate the absence of SIB1. For example, based on the PBCH indicating the absence of SIB1, a wireless device may point to a frequency. The wireless device may then search the SS / PBCH block at the frequency to which it is directed.

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

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

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

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

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

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

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

[0098] A transmitter (e.g., a base station transmitter) may use a precoder matrix for a portion of the transmission bandwidth. The transmitter may use a first precoder matrix for a first bandwidth and a second precoder matrix for a second bandwidth. The first and second precoder matrices may differ, for example, on the basis that the first bandwidth is different from the second bandwidth. A wireless device may assume that the same precoder matrix is ​​used across a set of PRBs. A set of PRBs can be determined / suggested / identified / represented as a precoder resource block group (PRG).

[0099] A PDSCH may contain one or more layers. A radio device may assume that at least one symbol with DM-RS exists on one or more layers of the PDSCH. The upper layers may constitute one or more DM-RS for the PDSCH (e.g., up to three DM-RS for the PDSCH). Downlink PT-RS may be transmitted / transmitted by a base station and may be used by a radio device for, for example, phase noise compensation. Whether downlink PT-RS exists may depend on the RRC configuration. The presence and / or pattern of downlink PT-RS may be configured on radio device-specific criteria using association with one or more parameters used / adopted for other purposes (e.g., modulation and coding scheme (MCS)) that may be indicated by, for example, a combination of RRC signaling and / or DCI. The dynamic presence of downlink PT-RS may be associated with one or more DCI parameters, including at least MCS, if configured. A network (e.g., an NR network) may support multiple PT-RS densities defined in the time and / or frequency domain. The frequency domain density (configuration / if any) may be associated with at least one configuration of the planned bandwidth. A wireless device may assume the same precoding for DM-RS and PT-RS ports. The quantity / number of PT-RS ports may be less than the quantity / number of DM-RS ports in the planned resources. Downlink PT-RS may be configured / allocated / limited for the planned interval / frequency duration for the wireless device. Downlink PT-RS may be transmitted / transmitted via symbols, for example, to facilitate phase tracking in the receiver.

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

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

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

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

[0104] Channels that use beamforming may require beam management. Beam management may include beam measurement, beam selection, and / or beam display. A beam may be associated with one or more reference signals. A beam may be identified by one or more beamforming reference signals. A wireless device may perform downlink beam measurement and generate a beam measurement report based on, for example, one or more downlink reference signals (e.g., CSI-RS). A wireless device may perform downlink beam measurement procedures after, for example, an RRC connection has been set up with a base station.

[0105] Figure 11B shows an exemplary mapping of one or more CSI-RS. CSI-RS can be mapped in the time domain and the frequency domain. Each rectangular block shown in Figure 11B may correspond to a resource block (RB) within the cell bandwidth. A base station may send / transmit one or more RRC messages containing CSI-RS resource configuration parameters that represent one or more CSI-RS. One or more of the parameters may be configured by higher-layer signaling for CSI-RS resource configuration (e.g., RRC and / or MAC signaling). One or more parameters may include at least one of the following: CSI-RS resource configuration identity, CSI-RS port quantity / number, CSI-RS configuration (e.g., position of symbols and resource elements (REs) in subframes), CSI-RS subframe configuration (e.g., subframe position, offset, and periodicity of radio frames), CSI-RS power parameters, CSI-RS sequence parameters, code division multiplexing (CDM) type parameters, frequency density, transmit comb, quasi-coposition (QCL) parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and / or other radio resource parameters.

[0106] One or more beams may be configured for radio devices with configurations specific to the radio device. Three beams are shown in Figure 11B (beam #1, beam #2, and beam #3), but more or fewer beams may be configured. Beam #1 may be assigned to CSI-RS1101 which can be transmitted on one or more subcarriers of the RB of a first symbol. Beam #2 may be assigned to CSI-RS1102 which can be transmitted on one or more subcarriers of the RB of a second symbol. Beam #3 may be assigned to CSI-RS1103 which can be transmitted on one or more subcarriers in the RB of a third symbol. The base station may transmit another CSI-RS associated with a beam for another radio device using other subcarriers in the same RB (e.g., those not used to transmit CSI-RS1101), for example by using frequency division multiplexing (FDM). The beam used for a wireless device may be configured, for example, by using time-domain multiplexing (TDM), so that the beam for the wireless device uses different symbols than those used by the beams of other wireless devices. The wireless device may be delivered with a beam of orthogonal symbols (e.g., no overlapping symbols) by using TDM, for example.

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

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

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

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

[0111] A wireless device may initiate / start / execute a beam fault recovery (BFR) procedure, for example, based on the detection of a beam fault. A wireless device may transmit / transmit a BFR request (e.g., a preamble, UCI, SR, MAC CE, and / or similar) based on the initiation of a BFR procedure. A wireless device may detect a beam fault, for example, based on the determination that the quality of the beam pair link of the relevant control channel is insufficient (e.g., having an error rate higher than the error rate threshold, a received signal power lower than the received signal power threshold, a timer expiring, and / or similar).

[0112] A wireless device may measure the quality of a beampair 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 a beampair link may be based on one or more of the following: block error rate (BLER), RSRP value, signal-to-interference-plus-noise ratio (SINR) value, RSRQ value, and / or CSI values ​​measured on the RS resources. A base station may indicate that an RS resource has been QCL'd by one or more DM-RS of a channel (e.g., a control channel, a shared data channel, and / or similar). An RS resource and one or more DM-RS of a channel may be QCL'd if, for example, the channel characteristics transmitted to the wireless device via the RS resource (e.g., Doppler shift, Doppler spread, mean delay, delay spread, spatial Rx parameter, fade, and / or similar) are similar to or identical to the channel characteristics transmitted to the wireless device via the channel.

[0113] A network (e.g., an NR network including gNB and / or ng-eNB) and / or a radio device may initiate / start / execute a random access procedure. A radio device in an RRC idle (e.g., RRC_IDLE) state and / or RRC inactive (e.g., RRC_INACTIVE) state may initiate / execute a random access procedure to request network connection setup. A radio device may initiate / start / execute a random access procedure from an RRC connected (e.g., RRC_CONNECTED) state. A radio device may initiate / start / execute a random access procedure to request uplink resources (e.g., for uplink transmission of SRs when no PUCCH resources are available) and / or obtain / determine uplink timing (e.g., if the uplink synchronization state is asynchronous). A radio device may initiate / start / execute a random access procedure to request one or more System Information Blocks (SIBs) (e.g., other System Information Blocks such as SIB2, SIB3, etc., and / or similar). A wireless device may initiate / start / execute a random access procedure for beam fault recovery requests. A network may initiate / start / execute a random access procedure, for example, to establish time alignment for handover and / or SCell addition.

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

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

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

[0117] One or more RACH parameters provided / configured / included in configuration message 1310 may be used to determine the uplink transmit power for the first message (e.g., Msg1 1311) and / or the third message (e.g., Msg3 1313). One or more RACH parameters may indicate the reference power for preamble transmission (e.g., the received target power and / or the initial power for preamble transmission). There may be one or more power offsets indicated by one or more RACH parameters. One or more RACH parameters may indicate the power ramping step, the power offset between the SSB and CSI-RS, the power offset between the transmission of the first message (e.g., Msg1 1311) and the third message (e.g., Msg3 1313), and / or the power offset values ​​between preamble groups. One or more RACH parameters may indicate one or more thresholds, for example, based on the fact that the wireless device can determine at least one reference signal (e.g., SSB and / or CSI-RS) and / or uplink carriers (e.g., a normal uplink (NUL) carrier and / or a complementary uplink (SUL) carrier).

[0118] A first message (e.g., Msg1 1311) may include one or more preamble transmissions (e.g., a preamble transmission and one or more preamble retransmissions). An RRC message may be used to constitute one or more preamble groups (e.g., group A and / or group B). A preamble group may include one or more preambles. A wireless device may determine a preamble group based, for example, on the size of a path loss measurement and / or a third message (e.g., Msg3 1313). A 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 that has an RSRP exceeding an RSRP threshold (e.g., rsrp-ThresholdSSB and / or rsrp-ThresholdCSI-RS). A wireless device may select at least one preamble to be associated with one or more reference signals and / or a selected preamble group, for example, when an association between one or more preambles and at least one reference signal is constituted by an RRC message.

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

[0120] A wireless device may perform a preamble retransmission, for example, based on (e.g., subsequently or in response to) a preamble transmission, if no response is received (e.g., for a period of time, such as a monitoring window for monitoring RAR). The wireless device may increase the uplink transmission power for the preamble retransmission. The wireless device may select an initial preamble transmit power based, for example, on a target received preamble power configured by path loss measurement and / or the network. The wireless device may decide to retransmit / re-transmit the preamble and ramp up the uplink transmit power. The wireless device may receive one or more RACH parameters (e.g., PREAMBLE_POWER_RAMPING_STEP) indicating a ramping step for the preamble retransmission. The ramping step may be the amount of incremental increase in uplink transmit power for the retransmission. The wireless device may increase the uplink transmit power, for example, if the wireless device determines the same reference signal (e.g., SSB and / or CSI-RS) as the previous preamble transmission. A wireless device may, for example, use a counter parameter (e.g., PREAMBLE_TRANSMISSION_COUNTER) to count the amount / number of preamble transmissions and / or retransmissions. A wireless device may determine that a random access procedure has failed, for example, if the amount / number of preamble transmissions exceeds a threshold configured by one or more RACH parameters (e.g., preambleTransMax) without receiving a success response (e.g., RAR).

[0121] The second message (e.g., Msg2 1312) (e.g., received by a radio device) may contain a RAR. The second message (e.g., Msg2 1312) may contain multiple RARs corresponding to multiple radio devices. The second message (e.g., Msg2 1312) may be received based on (e.g., subsequently in response to) the transmission of the first message (e.g., Msg1 1311). The second message (e.g., Msg2 1312) may be scheduled on the DL-SCH and indicated by the PDCCH using, for example, a Random Access Radio Network Temporary Identifier (RA RNTI). The second message (e.g., Msg2 1312) may indicate that the first message (e.g., Msg1 1311) was received by a base station. A second message (e.g., Msg2 1312) may include a time alignment command that can be used by the wireless device to adjust the transmission timing of the wireless device, a scheduling grant for the transmission of a third message (e.g., Msg3 1313), and / or a temporary cell RNTI (TC-RNTI). The wireless device may determine / start a time window (e.g., ra-ResponseWindow) for monitoring PDCCH for the second message (e.g., Msg2 1312) after sending / transmitting the first message (e.g., Msg1 1311) (e.g., preamble). The wireless device may determine the start time of the time window based on the PRACH opportunity that the wireless device uses to send / transmit the first message (e.g., Msg1 1311) (e.g., preamble). A wireless device may begin a time window after one or more symbols of the last symbol of a first message (e.g., Msg1 1311) that includes a preamble (e.g., symbols that indicate the completion of the first message (e.g., Msg1 1311) including the transmission of the preamble, or symbols that are in the first PDCCH opportunity from the end of the transmission of the preamble). One or more symbols may be determined based on numerology. PDCCH may be mapped to a common lookup space (e.g., Type1-PDCCH common lookup space) composed of RRC messages.A wireless device may identify / determine a RAR, for example, based on an RNTI. A wireless network temporary identifier (RNTI) may be used in response to one or more events that initiate / start a random access procedure. A wireless device may use an RA-RNTI for one or more communications related to random access or any other purpose. An RA-RNTI may be associated with a PRACH opportunity in which the wireless device transmits / transmits a preamble. A wireless device may determine an RA-RNTI based, for example, on at least one of the OFDM symbol index, slot index, frequency domain index, and / or UL carrier indicators of a PRACH opportunity. An example of how an RA-RNTI may be determined is as follows: RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id Here, s_id may be the index of the first OFDM symbol of the PRACH opportunity (e.g., 0 ≤ s_id < 14), t_id may be the index of the first slot of the PRACH opportunity in the system frame (e.g., 0 ≤ t_id < 80), f_id may be the index of the PRACH opportunity in the frequency domain (e.g., 0 ≤ f_id < 8), and ul_carrier_id may be the UL carrier used for preamble transmission (e.g., 0 for a NUL carrier, 1 for a SUL carrier).

[0122] A wireless device may, for example, send / transmit a third message (e.g., Msg3 1313) based on (e.g., subsequently or in response to) the successful reception of a second message (e.g., Msg2 1312) (e.g., using the resource identified in Msg2 1312). The third message (e.g., Msg3 1313) may be used, for example, for conflict resolution in a conflict-based random access procedure. Multiple wireless devices may send / transmit the same preamble to a base station, and the base station may send / transmit RARs corresponding to the wireless devices. Conflicts can occur, for example, if multiple wireless devices interpret the RAR as corresponding to themselves. Conflict resolution (e.g., using a third message (e.g., Msg3 1313) and a fourth message (e.g., Msg4 1314)) can be used to increase the likelihood that a wireless device will not mistakenly use the identity of another wireless device. A wireless device may include a device identifier in a third message (e.g., Msg3 1313) (e.g., C-RNTI, if assigned, TC RNTI included in the second message (e.g., Msg2 1312), and / or any other appropriate identifier) ​​to perform conflict resolution, for example.

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

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

[0125] Figure 13B illustrates a two-step random access procedure. A two-step random access procedure may include a two-step non-conflict random access procedure. Similar to a four-step conflict-based random access procedure, the base station may send / transmit a configuration message 1320 to the radio device before the procedure begins. The configuration message 1320 may be similar in some respects to the configuration message 1310. The procedure shown in Figure 13B may include the transmission of two messages, a first message (e.g., Msg1 1321) and a second message (e.g., Msg2 1322). The first message (e.g., Msg1 1321) and the second message (e.g., Msg2 1322) may be similar in some respects to the first message (e.g., Msg1 1311) and the second message (e.g., Msg2 1312), respectively. A two-step, non-conflicting random access procedure cannot contain messages similar to a third message (e.g., Msg3 1313) and / or a fourth message (e.g., Msg4 1314).

[0126] A two-step (e.g., no-conflict) random access procedure may be configured / initiated for beam fault recovery, other SI requests, SCell addition, and / or handover. The base station may display or assign to the radio device the preamble used for the first message (e.g., Msg1 1321). The radio device may receive a display of the preamble (e.g., ra-PreambleIndex) from the base station via PDCCH and / or RRC.

[0127] A radio device may initiate a time window (e.g., ra-ResponseWindow) for monitoring the PDCCH for the RAR based on (e.g., after or in response to) the transmission of a preamble. A base station may configure a radio device with one or more beam fault recovery parameters, such as a separate time window and / or a separate PDCCH, in the search space indicated by an RRC message (e.g., recoverySearchSpaceId). A base station may configure one or more beam fault recovery parameters in association with a beam fault recovery request. A separate time window for monitoring the PDCCH and / or RAR may be configured to begin after the transmission of a beam fault recovery request (e.g., the window may begin with any number of symbols and / or slots after the transmission of the beam fault recovery request). A radio device may monitor a PDCCH transmission addressed to a cell RNTI (C-RNTI) in the search space. During a two-step (e.g., no-conflict) random access procedure, the radio device may determine that the random access procedure was successful, for example, based on having transmitted a first message (e.g., Msg1 1321) and received a corresponding second message (e.g., Msg2 1322) (e.g., subsequently or in response to it). The radio device may determine that the random access procedure was successfully completed, for example, if the PDCCH transmission is addressed to the corresponding C-RNTI. The radio device may determine that the random access procedure was successfully completed, for example, if the radio device receives a RAR containing a preamble identifier corresponding to the preamble transmitted by the radio device, and / or if the RAR contains a MAC sub-PDU having the preamble identifier. The radio device may determine a response as an acknowledgment of an SI request.

[0128] Figure 13C shows an exemplary two-step random access procedure. Similar to the random access procedures shown in Figures 13A and 13B, the base station may send / transmit a configuration message 1330 to the radio device before the procedure begins. The configuration message 1330 may be similar in some respects to the configuration messages 1310 and / or 1320. The procedure shown in Figure 13C may involve sending multiple messages (e.g., two messages, including a first message (e.g., MsgA 1331) and a second message (e.g., MsgB 1332)).

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

[0130] A wireless device may initiate a two-step random access procedure (e.g., the two-step random access procedure shown in Figure 13C) for licensed and / or unlicensed spectra. The wireless device may decide whether to initiate a two-step random access procedure based on one or more factors. One or more factors may include at least one of the following: the wireless access technology in use (e.g., LTE, NR, and / or similar), whether the wireless device has a valid TA, cell size, the RRC status of the wireless device, the type of spectrum (e.g., licensed versus unlicensed), and / or any other suitable factors.

[0131] A wireless device may determine the wireless resources and / or uplink transmit power of the preamble 1341 and / or transport block 1342 (e.g., included in the first message (e.g., Msg A1331)) based on a two-step RACH parameter contained in configuration message 1330. The RACH parameter may indicate the MCS, time-frequency resources, and / or power control of the preamble 1341 and / or transport block 1342. The time-frequency resources for 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 parameter may enable the wireless device to determine the receive timing and downlink channel for monitoring and / or receiving the second message (e.g., Msg B1332).

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

[0133] Wireless devices and base stations may exchange control signaling (e.g., control information). Control signaling may be called L1 / L2 control signaling and may originate from the PHY layer (e.g., layer 1) and / or MAC layer (e.g., layer 2) of the wireless device or base station. Control signaling may include downlink control signaling transmitted from the base station to the wireless device and / or uplink control signaling transmitted from the wireless device to the base station.

[0134] Downlink control signaling may include at least one of the following: downlink scheduling assignments, uplink scheduling grants indicating uplink radio resources and / or transport format, slot format information, preemption indications, power control commands, and / or any other suitable signaling. A radio device may receive downlink control signaling in a payload transmitted / transmitted by a base station via a PDCCH. The payload transmitted / transmitted via a PDCCH may be called downlink control information (DCI). The PDCCH may be a group-common PDCCH (GC-PDCCH) common to a group of radio devices. The GC-PDCCH may be scrambled by a group-common RNTI.

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

[0136] DCIs can be used for different purposes. The purpose may be indicated by the type of RNTI used to scramble the CRC parity bits. A DCI with scrambled CRC parity bits using a paging RNTI (P-RNTI) may indicate paging information and / or system information change notifications. P-RNTI can be predefined as "FFFE" in hexadecimal. A DCI with scrambled CRC parity bits using a system information RNTI (SI-RNTI) may indicate broadcast transmissions of system information. SI-RNTI can be predefined as "FFFF" in hexadecimal. A DCI with scrambled CRC parity bits using a random access RNTI (RA-RNTI) may indicate random access responses (RARs). A DCI with scrambled CRC parity bits using a cell RNTI (C-RNTI) may indicate unicast transmissions of dynamic schedules and / or triggers for random access in PDCCH sequences. A DCI with scrambled CRC parity bits in a temporary cell RNTI (TC-RNTI) may indicate conflict resolution (e.g., Msg3 similar to Msg3 1313 shown in Figure 13A). Other RNTIs configured by the base station for radio devices may include configured scheduling RNTIs (CS RNTIs), transmission power control PUCCH RNTIs (TPC PUCCH-RNTIs), transmission power control PUSCH RNTIs (TPC-PUSCH-RNTIs), transmission power control SRS RNTIs (TPC-SRS-RNTIs), interruption RNTIs (INT-RNTIs), slot format display RNTIs (SFI-RNTIs), semi-persistent CSI RNTIs (SP-CSI-RNTIs), modulation and coding scheme cell RNTIs (MCS-C RNTIs), and / or similar.

[0137] A base station may transmit / transmit DCI in one or more DCI formats, depending on the purpose and / or content of the DCI. DCI format 0_0 may be used for scheduling PUSCH in a cell. DCI format 0_0 may be a fallback DCI format (e.g., with a compact DCI payload). DCI format 0_1 ​​may be used for scheduling PUSCH in a cell (e.g., with a larger DCI payload than DCI format 0_0). DCI format 1_0 may be used for scheduling PDSCH in a cell. DCI format 1_0 may be a fallback DCI format (e.g., with a compact DCI payload). DCI format 1_1 may be used for scheduling PDSCH in a cell (e.g., with a larger DCI payload than DCI format 1_0). DCI format 2_0 may be used to provide a slot format representation to a group of radio devices. DCI format 2_1 may be used to inform / notify a group of radio devices of a physical resource block and / or OFDM symbol that a group of radio devices may not intend to use for that group of radio devices. DCI format 2_2 may be used to send Transmit Power Control (TPC) commands to PUCCH or PUSCH. DCI format 2_3 may be used to send a group of TPC commands for SRS transmission by one or more radio devices. DCI formats for new features may be defined in future releases. DCI formats may have different DCI sizes or may share the same DCI size.

[0138] A base station may process DCI using channel coding (e.g., polarity coding), rate matching, scrambling, and / or QPSK modulation after scrambling DCI with RNTI. A base station may map coded and modulated DCI onto resource elements used and / or configured for a PDCCH. A base station may transmit / transmit DCI over a PDCCH occupying a certain amount / number of consecutive control channel elements (CCEs), based on the DCI payload size and / or base station coverage. The amount / number of consecutive CCEs (called the aggregation level) may be 1, 2, 4, 8, 16, and / or other appropriate amount / number. A CCE may contain a number of resource element groups (REGs) (e.g., 6). A REG may contain resource blocks in OFDM symbols. Mapping coded and modulated DCI onto resource elements may be based on mapping CCEs to REGs (e.g., CCE-to-REG mapping).

[0139] Figure 14A shows an example of a CORESET configuration. A CORESET configuration may be for a bandwidth portion or any other frequency band. A base station may transmit / transmit DCIs via PDCCHs on one or more control resource sets (CORESETs). A CORESET may contain time-frequency resources that radio devices attempt to decode / try using one or more lookup spaces. A base station may configure the size and location of a CORESET in the time-frequency domain. A first CORESET 1401 and a second CORESET 1402 may occur or be set / configured at a first symbol in a slot. The first CORESET 1401 may overlap with the second CORESET 1402 in the frequency domain. A third CORESET 1403 may occur or be set / configured at a third symbol in a slot. A fourth CORESET 1404 may occur or be set / configured at a seventh symbol in a slot. A CORESET may have different amounts / numbers of resource blocks in the frequency domain.

[0140] Figure 14B shows an example of CCE-to-REG mapping. CCE-to-REG mapping can be performed for DCI transmissions via CORESET and PDCCH processing. CCE-to-REG mapping can be interleaved mapping (e.g., for the purpose of providing frequency diversity) or non-interleaved mapping (e.g., for the purpose of facilitating interference adjustment and / or frequency-selective transmission of control channels). A base station may perform different or identical CCE-to-REG mappings with different CORESETs. A CORESET can be associated with a CCE-to-REG mapping (e.g., by an RRC configuration). A CORESET can consist of antenna port QCL parameters. The antenna port QCL parameters may indicate DM-RS QCL information for PDCCH reception via the CORESET.

[0141] A base station may transmit one or more RRC messages to a radio device, each containing one or more CORESET and one or more locator space set configuration parameters. The configuration parameters may indicate the relationship between the locator space set and the CORESET. The locator space set may include a set of PDCCH candidates formed by the CCE (e.g., at a given aggregation level). The configuration parameters may indicate at least one of the following: several quantities / numbers of PDCCH candidates monitored at each aggregation level, PDCCH monitoring periodicity and PDCCH monitoring patterns, one or more DCI formats monitored by the radio device, and / or whether the locator space set is a common locator space set or a locator space set specific to a radio device (e.g., a UE-specific locator space set). The set of CCEs in a common locator space set may be predefined and known to the radio device. The set of CCEs in a locator space set specific to a radio device (e.g., a UE-specific locator space set) may be configured, for example, based on the identity of the radio device (e.g., C-RNTI).

[0142] As shown in Figure 14B, a wireless device may determine the time-frequency resources of a CORESET based on one or more RRC messages. A wireless device may determine the CCE-to-REG mapping of a CORESET (e.g., interleaved or non-interleaved, and / or mapping parameters) based, for example, the configuration parameters of a CORESET. A wireless device may determine a certain amount / number (e.g., up to 10) of search space sets configured on / for a CORESET based, for example, one or more RRC messages. A wireless device may monitor a set of PDCCH candidates according to the configuration parameters of a certain search space set. A wireless device may monitor a set of PDCCH candidates in one or more CORESETs to detect one or more DCIs. Monitoring may include decoding one or more PDCCH candidates from the set of PDCCH candidates according to the monitored DCI format. Monitoring may include decoding the DCI contents of one or more PDCCH candidates in a possible (or configured) DCI format, the possible (or configured) PDCCH format (e.g., the amount / number of CCEs, the amount / number of PDCCH candidates in a common search space, and / or the amount / number of PDCCH candidates in a radio device-specific search space), and the possible (or configured) DCI format. Decoding may be called blind decoding. The radio device may determine that the DCI is valid for the radio device based on (e.g., subsequently and in response to) a CRC check (e.g., a scrambled bit of the CRC parity bit of the DCI that matches the RNTI value). The radio device may process the information contained in the DCI (e.g., scheduling assignments, uplink grants, power control, slot format indications, downlink preemption, and / or similar).

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

[0144] There may be multiple PUCCH formats (e.g., five PUCCH formats). A wireless device may determine the PUCCH format based, for example, on the size of the UCI (e.g., the amount / number of uplink symbols and the amount / number of UCI bits in the UCI transmission). PUCCH format 0 may have the length of one or two OFDM symbols and may contain two or fewer bits. A wireless device may use PUCCH format 0 to transmit / transmit a UCI via a PUCCH resource, for example, when the transmission is via one or two symbols and the amount / number of HARQ-ACK information bits (HARQ-ACK / SR bits) with positive or negative SR is one or two. PUCCH format 1 may occupy a certain amount / number of OFDM symbols (e.g., four to fourteen OFDM symbols) and may contain two or fewer bits. A wireless device may use PUCCH format 1, for example, when the transmission is via four or more symbols and the amount / number of HARQ-ACK / SR bits is one or two. PUCCH format 2 may occupy one or two OFDM symbols and may contain more than two bits. A wireless device may use PUCCH format 2 if, for example, transmission is via one or two symbols and the amount / number of UCI bits is 2 or more. PUCCH format 3 may occupy a certain amount / number of OFDM symbols (e.g., 4 to 14 OFDM symbols) and may contain more than two bits. A wireless device may use PUCCH format 3 if, for example, transmission is four or more symbols, the amount / number of UCI bits is 2 or more, and the PUCCH resource does not contain orthogonal cover codes (OCCs). PUCCH format 4 may occupy a certain amount / number of OFDM symbols (e.g., 4 to 14 OFDM symbols) and may contain more than two bits. A wireless device may use PUCCH format 4 if, for example, transmission is four or more symbols, the amount / number of UCI bits is 2 or more, and the PUCCH resource contains OCCs.

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

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

[0147] Figure 15A shows an example of communication between a wireless device and a base station. The wireless device 1502 and base station 1504 may be part of a communication network, such as the communication network 100 shown in Figure 1A, the communication network 150 shown in Figure 1B, or other communication networks. The communication network may include one or more wireless devices and / or one or more base stations having substantially the same or similar configuration as shown in Figure 15A.

[0148] Base station 1504 may connect radio device 1502 to a core network (not shown) via radio communication over an air interface (or radio interface) 1506. The communication direction from base station 1504 to radio device 1502 over air interface 1506 may be called downlink. The communication direction from radio device 1502 to base station 1504 over air interface may be called uplink. Downlink transmissions may be separated from uplink transmissions, for example, using various redundancy schemes (e.g., FDD, TDD, and / or some combination of redundancy techniques).

[0149] For downlink, data transmitted from base station 1504 to radio device 1502 may be provided / transmitted / reported to processing system 1508 of base station 1504. The data may be provided / transmitted / reported to processing system 1508 by, for example, the core network. For uplink, data transmitted from radio device 1502 to base station 1504 may be provided / transmitted / reported to processing system 1518 of radio device 1502. Processing systems 1508 and 1518 may process the data for transmission by implementing OSI functions of layers 3 and 2. Layer 2 may include, for example, the SDAP layer, PDCP layer, RLC layer, and MAC layer as described with respect to Figures 2A, 2B, 3, and 4A. Layer 3 may include, for example, the RRC layer as described with respect to Figure 2B.

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

[0151] The receiving processing system 1512 of base station 1504 may receive uplink transmissions from radio device 1502. The receiving processing system 1512 of base station 1504 may include one or more TRPs. The receiving processing system 1522 of radio device 1502 may receive downlink transmissions from base station 1504. The receiving processing system 1522 of radio device 1502 may include one or more antenna panels. Receiving processing systems 1512 and 1522 may implement OSI functions of layer 1. Layer 1 may include, for example, the PHY layer described with respect to Figures 2A, 2B, 3, and 4A. For receiving processing, the PHY layer may perform, for example, error detection, forward error correction decoding, deinterleaving, demapping of transport channels to physical channels, demodulation of physical channels, MIMO or multi-antenna processing, and / or similar.

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

[0153] Processing systems 1508 and 1518 may be associated with memories 1514 and 1524, respectively. Memories 1514 and 1524 (e.g., one or more non-temporary computer-readable media) may store computer program instructions or code that can be executed by processing systems 1508 and / or 1518, respectively, to perform one or more functions (e.g., one or more functions described herein, and other functions of a general computer, processor, memory, and / or other peripheral device). Transmitting processing system 1510 and / or receiving processing system 1512 may be coupled to memory 1514 and / or another memory (e.g., one or more non-temporary computer-readable media) that stores computer program instructions or code that can be executed to perform one or more of their respective functions. The transmission processing system 1520 and / or the reception processing system 1522 may be coupled to memory 1524 and / or another memory (e.g., one or more non-temporary computer-readable media) that stores computer program instructions or code that can be executed to perform one or more of their respective functions.

[0154] Processing system 1508 and / or processing system 1518 may include one or more controllers and / or one or more processors. One or more controllers and / or one or more processors may include, for example, general-purpose processors, digital signal processors (DSPs), microcontrollers, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) and / or other programmable logic devices, discrete gates and / or transistor logic, discrete hardware components, onboard units, or any combination thereof. Processing system 1508 and / or processing system 1518 may perform at least one of signal coding / processing, data processing, power control, input / output processing and / or any other functions that may enable wireless devices 1502 and / or base stations 1504 to operate in a wireless environment.

[0155] The processing system 1508 may be connected to one or more peripheral devices 1516. The processing system 1518 may be connected to one or more peripheral devices 1526. One or more peripheral devices 1516 and one or more peripheral devices 1526 may include software and / or hardware that provides features and / or functions, such as a speaker, microphone, keypad, display, touchpad, power supply, satellite transceiver, Universal Serial Bus (USB) port, hands-free headset, frequency modulation (FM) radio unit, media player, internet browser, electronic control unit (e.g., for a vehicle), and / or one or more sensors (e.g., accelerometer, gyroscope, temperature sensor, radar sensor, lidar sensor, ultrasonic sensor, light sensor, camera, and / or similar). The processing system 1508 and / or the processing system 1518 may receive input data (e.g., user input data) from one or more peripheral devices 1516 and / or one or more peripheral devices 1526 and / or provide output data (e.g., user output data) to them. The processing system 1518 of the wireless device 1502 may be configured to receive power from a power source and / or distribute power to other components of the wireless device 1502. The power source may include one or more power sources, such as a battery, a solar cell, a fuel cell, or any combination thereof. The processing system 1508 may be connected to a global positioning system (GPS) chipset 1517. The processing system 1518 may be connected to a global positioning system (GPS) chipset 1527. The GPS chipset 1517 and the GPS chipset 1527 may be configured to determine and provide geographic location information for the wireless device 1502 and the base station 1504, respectively.

[0156] Figure 15B shows exemplary elements of a computing device that may be used to implement any of the various devices described herein, including, for example, base stations 160A, 160B, 162A, 162B, 220, 1710, 1810 and / or 1910, radio devices 106, 156A, 156B, 210, 1705, 1805 and / or 1905, or any other base stations, radio devices, AMFs, UPFs, network devices, or computing devices described herein. The computing device 1530 may include one or more processors 1531 capable of executing instructions stored in random access memory (RAM) 1533, removable media 1534 (such as a Universal Serial Bus (USB) drive, a compact disk (CD) or digital multipurpose 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) capable of executing instructions for one or more computer programs to monitor processes running on the processor 1531 and any processes requesting access to any hardware and / or software components of the computing device 1530 (e.g., ROM 1532, RAM 1533, removable media 1534, hard drive 1535, device controller 1537, network interface 1539, GPS 1541, Bluetooth interface 1542, WiFi interface 1543, etc.). The computing device 1530 may also include one or more output devices such as a display 1536 (e.g., a screen, display device, monitor, television, etc.) and one or more output device controllers 1537 such as a video processor. There may also be one or more user input devices 1538 such as a remote control, keyboard, mouse, touchscreen, microphone, etc.The computing device 1530 may also include one or more network interfaces, such as a network interface 1539, which may be a wired interface, a wireless interface, or a combination of the two. The network interface 1539 may provide an interface for the computing device 1530 to communicate with a network 1540 (e.g., a RAN, or any other network). The network interface 1539 may include a modem (e.g., a cable modem), and the external network 1540 may include a communication link, an external network, a home network, a provider's wireless, coaxial, fiber, or hybrid fiber / coaxial distribution system (e.g., a DOCSIS network), or any other desired network. Additionally, the computing device 1530 may include a location detection device, such as a global positioning system (GPS) microprocessor 1541, which may be configured to receive and process global positioning signals and determine the geographical location of the computing device 1530 with possible assistance from external servers and antennas.

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

[0158] Figure 16A shows an exemplary structure for uplink transmission. Processing of the baseband signal representing the physical uplink shared channel may include / implement one or more functions. These one or more functions may include at least one of the following: scrambling, modulation of scrambled bits to generate complex-valued symbols, mapping of complex-valued modulated symbols onto one or more transmit layers, conversion precoding to generate complex-valued symbols, precoding of complex-valued symbols, mapping of precoded complex-valued symbols to resource elements, complex-valued time-domain single-carrier frequency division multiplexing access (SC-FDMA), generation of a CP-OFDM signal to an antenna port, or any other signal, and / or similar. An SC-FDMA signal for uplink transmission may be generated, for example, when conversion precoding is enabled. A CP-OFDM signal for uplink transmission may be generated, for example, when conversion precoding is not enabled (for example, as shown in Figure 16A). These functions are examples, and other mechanisms for uplink transmission may be implemented.

[0159] Figure 16B shows an exemplary structure for modulation and upconversion of a baseband signal to a carrier frequency. The baseband signal may be a complex-valued SC-FDMA, CP-OFDM baseband signal (or any other baseband signal) relative to an antenna port and / or complex-valued physical random access channel (PRACH) baseband signal. Filtering may be performed / applied, for example, before transmission.

[0160] Figure 16C shows an exemplary structure for downlink transmission. Processing of the baseband signal representing the physical downlink channel may include / implement one or more functions. These one or more functions may include scrambling of coded bits in a codeword to be transmitted / transmitted on / through the physical channel, modulating the scrambled bits to generate a complex-valued modulation symbol, mapping the complex-valued modulation symbol to one or more transmit layers, precoding of the complex-valued modulation symbol on layers for transmission over antenna ports, mapping of the complex-valued modulation symbol to resource elements at antenna ports, generation of a complex-valued time-domain OFDM signal per antenna port, and / or similar. These functions are examples, and other mechanisms for downlink transmission may be implemented.

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

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

[0163] A timer, for example, can start running once initiated and continue running until it is stopped or expires. A timer can be started when it is not running, or restarted when it is running. A timer can be associated with a value (for example, a timer can start from or restart from a certain value, or start from zero and expire when a value is reached). The duration of a timer does not have to be updated until the timer stops or expires (for example, due to a BWP switch). A timer can be used to measure the time duration / window of a process. With respect to implementations and / or procedures relating to one or more timers or other parameters, it will be understood that there can be multiple ways to implement one or more timers or other parameters. One or more of the multiple ways of implementing a timer can be used to measure the time duration / window of a procedure. A random access response window timer can be used to measure the time window for receiving a random access response. The time difference between two timestamps can be used, for example, instead of starting a random access response window timer and determining the timer's expiration. A process for measuring a time window can be restarted, for example, when the timer is restarted. Other implementations may be configured / provided to resume measuring the time window.

[0164] A wireless device may receive, for example, a downlink message (e.g., RRC message, DCI, etc.) from a base station indicating an SRS resource for uplink transmission (e.g., PUSCH transmission). Based on the SRS resource, the wireless device may determine the transmit precoder (e.g., PUSCH precoder) for uplink transmission. The wireless device may determine the transmit beam (e.g., spatial domain transmit filter or PUSCH spatial relation) for uplink transmission. The wireless device may use the same antenna port for uplink transmission as it does for the SRS resource. Using the same antenna port for both uplink transmission and SRS resource may indicate that uplink transmission and SRS resource experience similar small channel characteristics and that the transmit beam used for PUSCH transmission and SRS resource is the same (or substantially the same). In at least some wireless communications, the transmit beam for SRS resource and the transmit beam for uplink transmission may be aligned (or identical, or substantially identical). The base station may ensure that the transmit beam for SRS resource and uplink transmission are aligned. Otherwise, there may be a mismatch (or misalignment) between the analog beamforming used / applied to uplink transmission and the digital precoding matrix shown for uplink transmission.

[0165] For example, for a cell's uplink BWP, if the RRC configuration parameters configure at least two SRS resource sets, both having a "codebook" or both having a "non-codebook," and the cell is represented by at least two unified TCI states, then the first SRS resource set of the at least two SRS resource sets (e.g., associated with TRP1) may be associated with the first TCI state 1931 of the at least two unified TCI states (e.g., associated with TRP1), and the second SRS resource set of the at least two SRS resource sets (e.g., associated with TRP2) may be associated with the second TCI state 1932 of the at least two unified TCI states (e.g., associated with TRP2). A downlink message may, for example, if an uplink transmission is associated with the first TCI state 1931, indicate an SRS resource from the first SRS resource set associated with the first TCI state 1931. A downlink message may, for example, indicate an SRS resource from a second set of SRS resources associated with a second TCI state 1932, if the uplink transmission is associated with a second TCI state 1932. This may allow for alignment of the transmit beam of the SRS resource and the transmit beam of the uplink transmission.

[0166] A single SRS resource set can be associated with a first TCI state 1931 (e.g., TRP1) of at least two unified TCI states, for example, for a cell's uplink BWP, if the RRC configuration parameter configures a single SRS resource set having “codebook” and / or “non-codebook” states, and the cell can be represented by at least two unified TCI states. A downlink message can indicate an SRS resource from the SRS resource set associated with the first TCI state 1931, for example, if an uplink transmit is associated with the first TCI state 1931. The transmit beam of the SRS resource and the transmit beam of the uplink transmit can be aligned. In at least some radio communications, a message (e.g., a downlink message) can indicate an SRS resource from the SRS resource set associated with the first TCI state (e.g., associated with TRP1), for example, if a transmit (e.g., an uplink transmit) is associated with a second TCI state (e.g., associated with TRP2). The transmit beam of an SRS resource and the transmit beam of an uplink transmit do not need to be aligned. For example, if a single set of SRS resources is configured, and the (single) SRS resource set is associated with a first TCI state and the uplink transmit is associated with a second TCI state, the base station does not need to ensure that the transmit beam of the SRS resource and the transmit beam of the uplink transmit are aligned. The CSI information obtained by SRS measurements may not be suitable for uplink transmissions if, for example, the transmit beam of the SRS resource and the uplink transmit are different (e.g., misaligned). With misaligned beams, the base station may not know which beam is being used by the radio device for uplink transmissions, and the base station may not be able to demodulate the uplink transmit, which may lead to an increased error rate and a reduced data rate.

[0167] In at least some wireless communications, a wireless device may, for example, stop the cell's BWP inactive timer and / or switch the cell's active downlink BWP to a downlink BWP having the same BWP index as the cell's active uplink BWP, if the wireless device may initiate a random access procedure for the cell. In at least some procedures, such as Layer 1 and / or Layer 2 triggered mobility (LTM) procedures, a wireless device may initiate a random access procedure for a candidate cell, for example, to obtain a timing advance value for the candidate cell in advance. The wireless device may not need to receive a random access response after transmitting (e.g., sending) a random access preamble through / over the candidate cell. Stopping the BWP inactive timer and switching the active downlink BWP may be inefficient because it may cause a delay in the completion of the random access procedure.

[0168] Examples described herein may enhance uplink scheduling when, for example, a single SRS resource set having “codebooks” and / or “non-codebooks” is configured for a cell’s uplink BWP and the cell is indicated by at least two unified TCI states. For example, a wireless device may only expect single-layer uplink transmissions scheduled by TRP2 (e.g., scheduled by a second CORESET pool index) when, for example, a single SRS resource set having “codebooks” and / or “non-codebooks” is associated with TRP1 (or a first CORESET pool index). A wireless device may not expect multi-layer uplink transmissions scheduled by TRP2 (e.g., scheduled by a second CORESET pool index) when, for example, a single SRS resource set having “codebooks” and / or “non-codebooks” is associated with TRP1 (or a first CORESET pool index). A wireless device may anticipate multi-layer uplink transmissions scheduled by TRP1 (or a first CORESET pool index) when a single SRS resource set having “codebooks” and / or “non-codebooks” is associated with TRP1 (or a first CORESET pool index). For example, a base station (or TRP2) may not transmit or send DCIs that schedule / trigger uplink transmissions (e.g., PUSCH transmissions, PUCCH transmissions) via a CORESET having a second CORESET pool index. A base station (or TRP1) may transmit (e.g., send) DCIs that schedule / trigger uplink transmissions (e.g., PUSCH transmissions, PUCCH transmissions) via a CORESET having a first CORESET pool index.For example, a wireless device may not expect a single set of SRS resources having the parameter usage set to “codebook” or “non-codebook” for the cell’s active uplink BWP, for instance, when the wireless device is configured by a higher-layer parameter PDCCH-Config which includes two different values ​​for coresetPoolIndex in the ControlResourceSet of the cell’s active downlink BWP. The examples described herein can reduce beam misalignment between uplink transmits and SRS resources. This reduction in beam misalignment can result in accurate CSI measurements, reduced error rates, and increased data rates.

[0169] The examples described herein may provide a solution in which a wireless device does not stop the BWP inactive timer or switch an active downlink BWP to another downlink BWP when, for example, the wireless device can initiate / can initiate a random access procedure for a candidate cell for an LTM procedure. Stopping the BWP inactive timer and BWP switching may be determined, for example, based on whether a random access procedure is initiated for a serving cell or a candidate / target cell. Communication efficiency may be improved.

[0170] Figures 17 and 18 show examples of TCI state activation. A radio device may receive one or more messages. Figure 17 shows an example of TCI state activation. Radio device 1705 may receive one or more messages from base station 1710. Radio device 1705 may receive one or more messages from relay nodes. Radio device 1705 may receive one or more messages from other radio devices (e.g., TRP, vehicle, remote radio head, etc.). One or more messages may include one or more configuration parameters 1720 (e.g., configuration parameters at time T0, as shown in Figure 17).

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

[0172] One or more configuration parameters 1720 may be RRC reconfiguration parameters. One or more configuration parameters 1720 may be for a set of cells. A set of cells may include cells. A cell may be, for example, a serving cell. At least one of the one or more configuration parameters 1720 may be for a cell. A cell may be a primary cell (PCell). A cell may be a primary secondary cell (PSCell). A cell may be a secondary cell (SCell). A cell may be a secondary cell for / composed of a PUCCH (e.g., a PUCCH SCell). A set of cells may be multiple cells (and / or may be used interchangeably with them). A cell may be a special cell (SpCell). For dual-connection (DC) operation, SpCell may refer to (or indicate) a PCell of an MCG or a PSCell of an SCG. SpCell may refer to (or indicate) a PCell. A cell may be a primary SCG cell (PSCell). Regarding dual connection operation, a wireless device may, for example, perform a random access procedure via PSCell when performing a reconfiguration in a Sync procedure.

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

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

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

[0176] When one or more uplink BWPs are active, the wireless device 1705 may transmit (e.g., transmit) uplink channels and / or signals (e.g., PUCCH, preamble, PUSCH, PRACH, PUCCH, etc.) over and / or through the uplink BWPs when one or more uplink BWPs are inactive. The wireless device may not transmit (e.g., transmit) uplink channels and / or signals (e.g., PUCCH, preamble, PUSCH, PRACH, PUCCH, etc.) over and / or through the uplink BWPs.

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

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

[0179] One or more configuration parameters may be for the cell's downlink BWP (e.g., active downlink BWP). At least one of the one or more configuration parameters may be for the cell's downlink BWP. One or more configuration parameters may indicate the subcarrier spacing and / or numerology for the downlink BWP.

[0180] One or more configuration parameters may be for the cell's uplink BWP (e.g., active uplink BWP). At least one of the one or more configuration parameters may be for the cell's uplink BWP. One or more configuration parameters may indicate the subcarrier spacing and / or numerology for the uplink BWP.

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

[0182] One or more configuration parameters may indicate multiple control resource sets (CORESETs). One or more configuration parameters may indicate multiple CORESETs of a cell's downlink BWP (e.g., an active downlink BWP). A downlink BWP (e.g., an active downlink BWP) may contain multiple CORESETs. One or more configuration parameters may indicate multiple CORESET indices, identifiers, and / or indicators (e.g., provided by the higher-level parameter ControlResourceSetId) for multiple CORESETs. Each CORESET of multiple CORESETs may be identified and / or indicated by its respective CORESET index in a group of CORESET indices. The first CORESET of multiple CORESETs may be identified by the first CORESET index in a group of CORESET indices. The second CORESET of multiple CORESETs may be identified by the second CORESET index in a group of CORESET indices.

[0183] One or more configuration parameters 1720 may indicate one or more CORESET pool indices for multiple CORESETs (e.g., provided by the higher-level parameter CoresetPoolIndex). Each CORESET in multiple CORESETs may be configured, indicated, and / or include one or more configuration parameters, each with its own CORESET pool index (e.g., 0, 1, etc.). One or more configuration parameters 1720 indicate, for each CORESET in multiple CORESETs, the CORESET pool index corresponding to each of the one or more CORESET pool indices. One or more configuration parameters 1720 may indicate, for example, a first CORESET pool index 1825 (CoresetPoolIndex=0) for a first CORESET in multiple CORESETs. One or more configuration parameters may indicate a second CORESET pool index 1845 (CoresetPoolIndex=1) for a second CORESET in multiple CORESETs. One or more CORESET pool indexes may include a first CORESET pool index 1825 and a second CORESET pool index 1845.

[0184] Alternatively, one or more configuration parameters 1720 may not indicate a CORESET pool index for any of the multiple CORESETs. The higher-level parameter CoresetPoolIndex may be absent from the configuration parameters of a CORESET. The 1805 wireless device may determine the value of the CORESET pool index of a CORESET (e.g., a default value) as a first CORESET pool index 1825 (CoresetPoolIndex=0). The first CORESET pool index 1825 (CoresetPoolIndex=0) may be the CORESET pool index of a CORESET, for example, based on the fact that one or more configuration parameters do not indicate a CORESET pool index for the CORESET. The wireless device 1805 may determine the value of the CORESET pool index of a CORESET (e.g., a default value) as the first CORESET pool index 1825, for example, based on the fact that one or more configuration parameters do not indicate a CORESET pool index for the CORESET.

[0185] A first CORESET pool (e.g., CORESET pool 0) may contain one or more first CORESETs, each having a CORESET pool index that may be equal to the first CORESET pool index 1825 (e.g., CoresetPoolIndex=0). One or more configuration parameters 1720 may indicate the first CORESET pool index 1825 for each of the one or more first CORESETs in the first CORESET pool. Multiple CORESETs may contain one or more first CORESETs.

[0186] A second CORESET pool (e.g., CORESET pool 1) may contain one or more second CORESETs having a CORESET pool index equal to the second CORESET pool index 1845 (e.g., CoresetPoolIndex=1). One or more configuration parameters 1720 may indicate the second CORESET pool index 1845 for each of the one or more second CORESETs in the second CORESET pool. Multiple CORESETs may contain one or more second CORESETs.

[0187] One or more configuration parameters 1820 may not indicate the CORESET pool index of one of several CORESETs. The wireless device 1805 may determine a default value for the CORESET pool index of a CORESET, for example, based on the fact that one or more configuration parameters 1820 do not indicate the CORESET pool index of the CORESET. The default value may be equal to zero (e.g., CoresetPoolIndex=0). The default value may be equal to the first CORESET pool index 1825 (e.g., zero). The first CORESET pool may contain a CORESET, for example, based on the fact that one or more configuration parameters do not indicate the CORESET pool index for the CORESET. The first CORESET pool may contain a CORESET, based on the fact that the default value for the CORESET pool index of a CORESET is equal to the first CORESET pool index 1825.

[0188] The first CORESET pool index 1825 of the first CORESET and the second CORESET pool index 1845 of the second CORESET 1858 may be the same. Another configuration parameter may indicate the same CORESET pool index for the first CORESET and the second CORESET 1858. Multiple CORESETs may include the first CORESET and the second CORESET 1858. One or more CORESET pool indices may include the first CORESET pool index 1825 and the second CORESET pool index 1845. The wireless device 1805 may group the first CORESET and the second CORESET 1858 in the same CORESET pool (e.g., CoresetPoolIndex=0 or CoresetPoolIndex=1) based, for example, on the fact that the first CORESET pool index 1825 of the first CORESET and the second CORESET pool index 1840 of the second CORESET 1858 are the same. The first CORESET pool containing the first CORESET and the second CORESET pool containing the second CORESET 1858 may be the same, for example, on the basis that the first CORESET pool index 1825 of the first CORESET and the second CORESET pool index 1840 of the second CORESET 1858 are the same.

[0189] The first CORESET pool index 1825 of the first CORESET and the second CORESET pool index 1840 of the second CORESET 1858 may be different. Multiple CORESETs may include the first CORESET and the second CORESET 1858. One or more CORESET pool indices may include the first CORESET pool index 1825 and the second CORESET pool index 1840. The wireless device 1805 may group the first CORESET and the second CORESET 1858 into different CORESET pools, for example, based on the fact that the first CORESET pool index 1825 of the first CORESET and the second CORESET pool index 1840 of the second CORESET 1858 are different. The wireless device 1805 may group the first CORESET into the first CORESET pool (for example, CoresetPoolIndex=0). The wireless device 1805 may group the second CORESET 1858 into a second CORESET pool (e.g., CoresetPoolIndex=1) that is different from the first CORESET pool, for example, based on the fact that the first CORESET pool index 1825 and the second CORESET pool index 1840 are different. The first CORESET pool and the second CORESET pool may be different, for example, based on the fact that the first CORESET pool index 1825 of the first CORESET and the second CORESET pool index 1840 of the second CORESET 1858 are different.

[0190] One or more configuration parameters 1820 may indicate at least two CORESET pool indices (e.g., 0 and 1) with respect to the higher-level parameter CORESETPoolIndex. One or more configuration parameters 1820 may include the higher-level parameter CORESETPoolIndex which has and / or is set to at least two CORESET pool indices. At least two CORESET pool indices may include a first CORESET pool index 1825 (e.g., 0) with respect to one or more first CORESETs among a plurality of CORESETs. At least two CORESET pool indices may include a second CORESET pool index 1840 (e.g., 1) which is different from the first CORESET pool index 1825 with respect to one or more second CORESETs among a plurality of CORESETs. One or more first CORESETs may include one or more third CORESETs among a plurality of CORESETs without a value for the higher-level parameter CORESETPoolIndex. One or more configuration parameters 1820 cannot include one or more higher-level parameters CORESETPoolIndex for third CORESETs.

[0191] A cell may include a plurality of transmit and receive points (TRPs). The plurality of TRPs may correspond to the cell and / or to the cell's radio device 1805 via, in, and / or in the cell. At least one of the plurality of TRPs may correspond to the cell's radio device via, and / or in the cell. The plurality of TRPs may include a first TRP and a second TRP. The first TRP may transmit (e.g., transmit) downlink transmits and / or signals (e.g., PDSCH, PDCCH, DCI) via a first CORESET pool. Transmitting downlink transmits and / or signals (e.g., PDCCH, DCI) via a first CORESET pool may include a first TRP that transmits downlink transmits and / or signals via a first CORESET having a first CORESET pool index and / or associated with the first CORESET pool index. The first TRP may not transmit (e.g., send) downlink transmits and / or signals (e.g., PDSCH, PDCCH, DCI) through the second CORESET pool. Not transmitting downlink transmits and / or signals (e.g., PDSCH, PDCCH, DCI) through the second CORESET pool may include the first TRP not transmitting (e.g., sending) downlink transmits and / or signals through the second CORESET 1858 having and / or associated with the second CORESET pool index.

[0192] A second TRP may transmit (e.g., send) downlink transmits and / or signals (e.g., PDSCH, PDCCH, DCI) via a second CORESET pool. Transmitting downlink transmits and / or signals (e.g., PDCCH, DCI) via a second CORESET pool may include the second TRP transmitting (e.g., sending) downlink transmits and / or signals via a second CORESET 1858 having and / or associated with the second CORESET pool index. A second TRP may not transmit (e.g., send) downlink transmits and / or signals (e.g., PDCCH, DCI) via the first CORESET pool. Not transmitting downlink transmits and / or signals (e.g., PDCCH, DCI) via the first CORESET pool may include the second TRP not transmitting (e.g., sending) downlink transmits and / or signals via a first CORESET having and / or associated with the first CORESET pool index.

[0193] One or more configuration parameters may indicate multiple uplink resources (e.g., PUCCH-resource, SRS-resource, etc.). One or more configuration parameters may indicate multiple uplink resources for a cell's uplink BWP (e.g., active uplink BWP). An uplink BWP (e.g., active uplink BWP) may contain multiple uplink resources. An uplink BWP (e.g., active uplink BWP) for a cell's uplink carrier (e.g., NUL, SUL) may contain multiple uplink resources. Multiple uplink resources may include, for example, multiple PUCCH resources. Multiple uplink resources may include, for example, multiple SRS resources. Multiple uplink resources may include, for example, multiple PUSCH resources.

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

[0195] One or more configuration parameters may indicate multiple uplink resource indices, identifiers, and / or indicators (e.g., provided by higher-level parameters PUCCH-ResourceId, SRS-ResourceId) for multiple uplink resources. Each uplink resource among the multiple uplink resources is identified and / or indicated by each uplink resource index among the multiple uplink resource indices. The first uplink resource among the multiple uplink resources is identified by the first uplink resource index among the multiple uplink resource indices. The second uplink resource among the multiple uplink resources is identified by the second uplink resource index among the multiple uplink resource indices.

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

[0197] One or more configuration parameters may indicate one or more CORESET pool indices for multiple uplink resources (e.g., provided by the higher-level parameter CoresetPoolIndex). Each uplink resource of multiple uplink resources may include, be configured by, and / or be indicated by one or more configuration parameters, each of which is a CORESET pool index of one or more CORESET pool indices (e.g., 0, 1). One or more configuration parameters may indicate each of which is a CORESET pool index of one or more CORESET pool indices for each uplink resource of multiple uplink resources. One or more configuration parameters may indicate, for example, a first CORESET pool index (CoresetPoolIndex=0) for a first uplink resource among multiple uplink resources. One or more configuration parameters may indicate, for example, a second CORESET pool index (CoresetPoolIndex=1) for a second uplink resource among multiple uplink resources. One or more CORESET pool indices may include the first CORESET pool index and the second CORESET pool index.

[0198] One or more configuration parameters may not indicate a CORESET pool index for one of several uplink resources. The higher-level parameter CoresetPoolIndex may be absent from the configuration parameters of the uplink resource. The wireless device 1805 may determine the value of the uplink resource's CORESET pool index (e.g., a default value) as the first CORESET pool index (CoresetPoolIndex=0). The wireless device may determine the value of the uplink resource's CORESET pool index (e.g., a default value) as the first CORESET pool index, for example, based on the fact that one or more configuration parameters do not indicate a CORESET pool index for the uplink resource. The first CORESET pool index (CoresetPoolIndex=0) may be the CORESET pool index of the uplink resource, for example, based on the fact that one or more configuration parameters do not indicate a CORESET pool index for the uplink resource.

[0199] One or more configuration parameters may indicate at least two CORESET pool indices (e.g., 0 and 1) with respect to the higher-level parameter CORESETPoolIndex. One or more configuration parameters may include the higher-level parameter CORESETPoolIndex which has and / or is set to at least two CORESET pool indices. At least two CORESET pool indices may include a first CORESET pool index (e.g., 0) for one or more first uplink resources among a plurality of uplink resources. At least two CORESET pool indices may include a second CORESET pool index (e.g., 1) different from the first CORESET pool index for one or more second uplink resources among a plurality of uplink resources. One or more first uplink resources may include one or more third uplink resources among a plurality of uplink resources without a value for the higher-level parameter CORESETPoolIndex. One or more configuration parameters may not include the higher-level parameter CORESETPoolIndex for one or more third uplink resources.

[0200] A cell may include multiple transmit and receive points (TRPs). Multiple TRPs may correspond to the cell, and / or to wireless devices in, through, and / or within the cell. At least one of the multiple TRPs may correspond to wireless devices in, through, and / or within the cell. Multiple TRPs may include a first TRP and a second TRP.

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

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

[0203] One or more configuration parameters may indicate one or more CORESET pool indices (e.g., provided by the higher-level parameter CoresetPoolIndex) for one or more uplink resource sets and / or groups. Each uplink resource set and / or group of one or more uplink resource sets and / or groups may include, be configured by, and / or be indicated by one or more configuration parameters, each of which is a CORESET pool index (e.g., 0, 1). One or more configuration parameters may indicate each of which is a CORESET pool index (e.g., 0, 1) for each uplink resource set and / or group of one or more uplink resource sets and / or groups. One or more configuration parameters may indicate a first uplink resource set and / or a group of one or more uplink resource sets and / or groups, e.g., a first CORESET pool index 1825 (CoresetPoolIndex=0). One or more configuration parameters may indicate, for example, a second CORESET pool index 1845 (CoresetPoolIndex=1) for a second uplink resource set and / or group among one or more uplink resource sets and / or groups thereof. One or more CORESET pool indexes may include a first CORESET pool index and a second CORESET pool index.

[0204] One or more configuration parameters may not indicate a CORESET pool index for one or more uplink resource sets and / or groups of uplink resource sets and / or groups. The higher-level parameter CoresetPoolIndex may be absent from the configuration parameters of uplink resource sets and / or groups. The wireless device 1805 may determine the value of the CORESET pool index for an uplink resource set and / or group (e.g., a default value) as the first CORESET pool index 1825 (CoresetPoolIndex=0). The wireless device may determine the value of the CORESET pool index for an uplink resource set and / or group (e.g., a default value) as the first CORESET pool index, for example, based on the fact that one or more configuration parameters do not indicate a CORESET pool index for an uplink resource set and / or group. The first CORESET pool index 1825 (CoresetPoolIndex=0) may be the CORESET pool index for an uplink resource set and / or group, for example, based on the fact that one or more configuration parameters do not indicate a CORESET pool index for the uplink resource set and / or group.

[0205] One or more configuration parameters may indicate at least two CORESET pool indices (e.g., 0 and 1) with respect to the higher-level parameter CORESETPoolIndex. One or more configuration parameters may include the higher-level parameter CORESETPoolIndex which has and / or is set to at least two CORESET pool indices. At least two CORESET pool indices may include a first CORESET pool index (e.g., 0) for a group of one or more first uplink resource sets and / or one or more uplink resource sets and / or groups. At least two CORESET pool indices may include a second CORESET pool index (e.g., 1) different from the first CORESET pool index for a group of one or more second uplink resource sets and / or groups. One or more first uplink resource sets and / or groups may include one or more third uplink resource sets and / or groups without a value for the higher-level parameter CORESETPoolIndex. One or more configuration parameters may not include a higher-level parameter CORESETPoolIndex for one or more third uplink resource sets and / or groups.

[0206] A cell may include multiple transmit and receive points (TRPs). Multiple TRPs may correspond to wireless devices in and / or in / through the cell. At least one of the multiple TRPs may correspond to wireless devices in, through, and / or in the cell. Multiple TRPs may include a first TRP and a second TRP.

[0207] The first TRP may receive uplink transmissions and / or signals (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) through the uplink resources in one or more uplink resource sets and / or groups having and / or associated with the first CORESET pool index. The first TRP may not receive uplink transmissions and / or signals (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) through the uplink resources in one or more uplink resource sets and / or groups having and / or associated with the second CORESET pool index.

[0208] A second TRP may receive uplink transmissions and / or signals (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) via uplink resources in one or more uplink resource sets and / or groups having and / or associated with a second CORESET pool index. A second TRP may not receive uplink transmissions and / or signals (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) via uplink resources in one or more uplink resource sets and / or groups having and / or associated with a first CORESET pool index.

[0209] A wireless device may transmit (e.g., transmit) uplink transmissions and / or signals (e.g., push / pucch / srs transmissions) via uplink resources. Multiple uplink resources may include uplink resources. One or more uplink resource sets and / or groups may include uplink resources.

[0210] The wireless device 1805 may receive downlink control information (DCI) 1830 via one of several CORESETs to schedule, trigger, and / or indicate uplink transmissions and / or signal transmissions. The DCI 1830 may schedule, trigger, and / or indicate uplink transmissions and / or signal transmissions via uplink resources. The DCI may indicate uplink resources. The DCI may include fields that indicate uplink resources.

[0211] Uplink transmissions and / or signals may be PUSCH transmissions (e.g., transport blocks). Uplink resources may be PUSCH resources. DCI1830 may schedule the transmission of PUSCH transmissions. Uplink transmissions and / or signals may be PUCCH transmissions (e.g., HARQ-ACK information feedback). Uplink resources may be PUCCH resources. DCI1830 may schedule the reception of transport blocks (e.g., PDSCH reception). Uplink transmissions and / or signals may be HARQ-ACK information feedback of transport blocks. Uplink transmissions and / or signals may be SRS. Uplink resources may be SRS resources. DCI1830 may schedule the transmission of SRS. SRS may be, for example, aperiodic SRS.

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

[0213] Uplink resources can be associated with CORESET pool indexes. Uplink resources can be associated with CORESET pool indexes, for example, by receiving DCIs that schedule, trigger, and / or indicate uplink transmissions and / or signal transmissions via the uplink resource through a CORESET associated with the CORESET pool index.

[0214] Uplink resource sets and / or groups containing uplink resources may be associated with a CORESET pool index. Uplink resource sets and / or groups may be associated with a CORESET pool index based on receiving DCIs that schedule, trigger, and / or indicate uplink transmissions and / or signal transmissions via uplink resources in (belonging to) the uplink resource set and / or group, for example, via a CORESET associated with the CORESET pool index. Uplink resource sets and / or groups may contain one or more uplink resources that contain uplink resources. One or more uplink resources may be associated with a CORESET pool index based on, for example, an uplink resource set and / or group containing one or more uplink resources being associated with a CORESET pool index. Each of the one or more uplink resources may be associated with a CORESET pool index based on, for example, an uplink resource set and / or group being associated with a CORESET pool index.

[0215] Uplink transmissions and / or signals may be associated with a CORESET pool index. Uplink transmissions and / or signals may be associated with a CORESET pool index, for example, based on receiving a DCI1830 that schedules, triggers, and / or indicates the transmission of uplink transmissions and / or signals via a CORESET associated with the CORESET pool index.

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

[0217] One or more configuration parameters 1720 may indicate multiple TCI states 1770 that represent a unified TCI state for a cell. One or more configuration parameters 1720 may include, for example, one or more PDSCH configuration parameters for the cell's downlink BWP. One or more configuration parameters 1720 may indicate multiple TCI states 1770 in the cell's downlink BWP.

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

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

[0220] The unified-TCI-state-type parameter may be set to "Joint". The wireless device 1805 may use (e.g., apply) multiple TCI states 1770 (e.g., provided and / or indicated by dl-orJoint-TCIStateList) for both cell uplink transmissions (e.g., PUSCH / PUCCH / SRS transmissions) and cell downlink receptions (e.g., PDCCH / PDSCH / CSI-RS receptions), based on, for example, that one or more configuration parameters include a unified-TCI-state-type parameter set to "Joint".

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

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

[0223] One or more configuration parameters 1720 may include, for example, one or more uplink BWP configuration parameters for the cell's uplink BWP. One or more configuration parameters 1720 may indicate a second set of TCI states 1770 for the cell's uplink BWP (broadcast workload pattern).

[0224] One or more configuration parameters 1720 may include, for example, one or more uplink BWP configuration parameters for the second uplink BWP of the second cell. One or more configuration parameters 1720 may indicate a second set of TCI states 1770 in the second uplink BWP of the second cell. The set of cells may include the second cell. One or more configuration parameters 1720 may include a standard unified TCI state list parameter (e.g., unifiedtci-StateType) for the uplink BWP of the cell that indicates the second uplink BWP of the second cell. The standard unified TCI state list parameter may include a BWP index (e.g., BWP-Id) that identifies (e.g., indicates) the second uplink BWP. The standard unified TCI state list parameter may include a cell index (e.g., ServCellIndex) that identifies (e.g., indicates) the second cell. The second uplink BWP of the second cell may be the standard BWP of the standard cell for the uplink BWP of the cell. A cell's uplink BWP can be the target BWP of a target cell. One or more uplink BWP configuration parameters for a cell's uplink BWP may not include higher-level (e.g., RRC) parameters such as ul-TCI-StateList, based on one or more configuration parameters for the cell's uplink BWP, including the standard unified TCI state list parameter.

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

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

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

[0228] For downlink reception via the cell's downlink BWP, the wireless device 1705 may use multiple TCI states 1770 of the second downlink BWP of a second cell, for example, based on a standard unified TCI state list parameter indicating the second downlink BWP of a second cell. For uplink transmission and reception via the cell's uplink BWP, the wireless device 1705 may use multiple TCI states 1770 of the second downlink BWP of a second cell, for example, based on a standard unified TCI state list parameter indicating the second downlink BWP of a second cell.

[0229] The wireless device 1705 may use a second set of TCI states 1770 for uplink transmission and reception via the cell's uplink BWP, for example, based on one or more configuration parameters 1720 indicating a second set of TCI states 1770 for the cell's uplink BWP. The wireless device 1705 may use a second set of TCI states 1770 for the second uplink BWP of a second cell, for example, based on a standard unified TCI state list parameter indicating the second uplink BWP of a second cell.

[0230] One or more configuration parameters 1720 may indicate a physical cell identifier (PCI) for a cell. One or more configuration parameters 1720 may indicate one or more PCIs for a set of cells. One or more PCIs may include the PCI of a cell. One or more configuration parameters 1720 may include a higher-level (e.g., RRC) parameter physCellId indicating one or more PCIs for a set of cells. One or more configuration parameters may indicate each of one or more PCIs for each cell in a set of cells. One or more configuration parameters may include a higher-level (e.g., RRC) parameter physCellId indicating each of one or more PCIs for each cell in a set of cells. One or more configuration parameters may indicate a first PCI of one or more PCIs for a first cell in a set of cells. The first PCI may identify the physical cell identity of the first cell. One or more configuration parameters may indicate a second PCI of one or more PCIs for a second cell in a set of cells. The second PCI can identify the physical cell identity of the second cell.

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

[0232] A list of PCI sets may include and / or indicate at least one PCI (e.g., additionalPCI or PhysCellId as described herein in Figure 17) of one or more PCIs. Each PCI set in the list of PCI sets (e.g., SSB-MTC-AdditionalPCI) may include and / or indicate each PCI of at least one PCI. One or more configuration parameters may indicate each PCI of at least one PCI for each PCI set in the list of PCI sets. At least one PCI may not include a PCI of a cell. Each PCI of at least one PCI may be different from a PCI of a cell. One or more PCIs may include at least one PCI and PCI of a cell. At least one PCI may indicate at least one cell of a set of cells (e.g., identify). Each PCI of at least one PCI may indicate each cell of at least one cell (e.g., identify). A first PCI set in a list of PCI sets may include a first PCI with at least one PCI. The first PCI may represent a first cell of at least one cell (e.g., identify one). A second PCI set in a list of PCI sets may include a second PCI with at least one PCI. The second PCI may represent a second cell of at least one cell (e.g., identify one). At least one cell may not contain any other cells. Each cell in at least one cell may be different from any other cell. A set of cells may include at least one cell and a other cell.

[0233] At least one cell may contain, for example, at least one non-serving cell. At least one cell may contain, for example, at least one adjacent cell. At least one cell may contain, for example, at least one candidate and / or support cell.

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

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

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

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

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

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

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

[0241] One or more configuration parameters 1720 cannot indicate at least one additional PCI index for one or more TCI states of a plurality of TCI states 1770. Additional PCI indexes may be absent (e.g., not exist) in the configuration parameters of one or more TCI states. One or more configuration parameters 1720 can include configuration parameters for one or more TCI states. One or more TCI states of a plurality of TCI states cannot be associated with an additional PCI index. One or more TCI states cannot contain an additional PCI index. Each TCI state of one or more TCI states cannot contain an additional PCI index. One or more TCI states can be associated with the PCI of a cell and / or a cell, for example, based on the fact that one or more configuration parameters do not indicate an additional PCI index for one or more TCI states of a plurality of TCI states. One or more TCI states can be associated with the PCI of a cell and / or a cell, for example, based on the fact that one or more configuration parameters do not indicate an additional PCI index for each TCI state of one or more TCI states. One or more TCI states may be associated with the PCI of a cell and / or cell, for example, on the basis that one or more configuration parameters do not indicate at least one additional PCI index for each of the one or more TCI states.

[0242] The wireless device 1705 may receive activation commands 1730 (e.g., MAC-CE, DCI, RRC, downlink control command / message, control command / message, unified TCI state activation / deactivation MAC CE, activation command 1730, etc., at time T1 as described herein in Figure 17). Activation command 1730 may indicate the activation of a subset 1780a of TCI states from a group of TCI states (e.g., DLorJoint-TCIStateList). Activation command may indicate the activation of a subset 1780 of a second group of TCI states (e.g., ul-TCI-StateList).

[0243] A wireless device may map a subset of TCI states 1780a to one or more TCI code points 1780b. An activation command may indicate a mapping of a subset of TCI states to one or more TCI code points. A wireless device may map each TCI state of the subset of TCI states 1780a to each TCI code point of one or more TCI code points 1780b. One or more TCI code points 1780b may represent and / or contain a subset of TCI states 1780a. Each TCI code point of one or more TCI code points 1780b may represent and / or map each TCI state of the subset of TCI states 1780a. Each TCI code point of one or more TCI code points 1780b may represent, contain, and / or map one or more TCI states.

[0244] In Figure 17, for example, a subset 1780a of TCI states could be TCI state 4, TCI state 5, TCI state 8, TCI state 26, and TCI state 61. One or more TCI code points 1780b may include a first TCI code point (e.g., TCI code point 000), a second TCI code point (e.g., TCI code point 001), a third TCI code point (e.g., TCI code point 110), and a fourth TCI code point (e.g., TCI code point 111). The first TCI code point (e.g., TCI code point 000) may include and / or represent TCI state 4. The second TCI code point (e.g., TCI code point 001) may include and / or represent TCI state 5 and TCI state 8. A third TCI code point (e.g., TCI code point 110) may include and / or represent TCI states 26 and 61. A fourth TCI code point (e.g., TCI code point 111) may include and / or represent TCI state 26. The first TCI code point (e.g., TCI code point 000) and the fourth TCI code point (e.g., TCI code point 111) represent a single TCI state. The second TCI code point (e.g., TCI code point 001) and the third TCI code point (e.g., TCI code point 110) represent two TCI states (e.g., two joint TCI states, two uplink TCI states, two downlink TCI states, etc.).

[0245] The number of one or more TCI code points 1780b may be equal to 1. One or more TCI code points 1780b may be a single TCI code point. A radio device cannot receive a DCI indicating the activation of one or more TCI states from a subset of TCI states, for example, based on the number of one or more TCI code points being equal to 1. A single TCI code point may indicate, include, and / or map to at least two TCI states from a plurality of TCI states 1770. A subset of TCI states 1780a may be at least two TCI states. A radio device 1705 cannot receive a DCI 1740 indicating the activation of one or more TCI states from a subset of TCI states 1780a, for example, based on the activation command indicating activation of at least two TCI states. At least two TCI states may include a first TCI state and a second TCI state.

[0246] A single TCI code point indicates / contains (and / or can be mapped to) a first TCI state among multiple TCI states. The first TCI state may be a single TCI state. A subset of TCI states may be the first TCI state. A radio device may not receive a DCI indicating the activation of one or more TCI states from a subset of TCI states, for example, based on the activation command indicating the activation of the first TCI state.

[0247] The number of one or more TCI code points 1780b may be greater than 1. The wireless device 1705 may receive DCI 1740 (for example, DCI 1740 at time T2, as described herein in Figure 17). DCI 1740 may include a TCI field 1745. The TCI field 1745 may indicate one of the one or more TCI code points 1780b. The value of the TCI field 1745 (for example, TCI field = 110 as described herein in Figure 17) may indicate a TCI code point and / or be equal to a TCI code point.

[0248] A TCI code point (e.g., TCI code point 110 in Figure 17) may include, represent, and / or map to at least two TCI states (e.g., TCI states 26 and 61 in Figure 17). A subset of TCI states 1780a may include at least two TCI states of a TCI code point. DCI 1740 may represent the activation of at least two TCI states. The at least two TCI states may include a first TCI state (e.g., TCI state 26 in Figure 17) and a second TCI state (e.g., TCI state 61 in Figure 17).

[0249] A TCI code point (e.g., TCI code point 111 in Figure 17) may include / indicate and / or map to a first TCI state (e.g., TCI state 26 in Figure 17). A subset of TCI states may include the first TCI state of a TCI code point and / or the first TCI state in a TCI code point. A DCI may indicate the activation of the first TCI state.

[0250] The first TCI state may be (and / or be used interchangeably with) the first unified TCI state. The first TCI state may be (and / or be used interchangeably with) the first joint TCI state. The first TCI state may be (and / or be used interchangeably with) the first downlink TCI state. The first TCI state may be (and / or be used interchangeably with) the first joint / downlink TCI state. The first TCI state may be (and / or be used interchangeably with) the first uplink TCI state.

[0251] The second TCI state may be (and / or be used interchangeably with) the second unified TCI state. The second TCI state may be (and / or be used interchangeably with) the second joint TCI state. The second TCI state may be (and / or be used interchangeably with) the second downlink TCI state. The second TCI state may be (and / or be used interchangeably with) the second joint / downlink TCI state. The second TCI state may be (and / or be used interchangeably with) the second uplink TCI state.

[0252] Figure 18 shows an example of TCI state activation. The wireless device 1805 may receive a first activation command 1820 (e.g., MAC-CE, DCI, downlink control command / message, RRC, control command / message, unified TCI state activation / deactivation MAC CE, activation command 1820, etc., at time T1 as described herein in Figure 18). The first activation command 1820 may activate, select, display, update and / or indicate the activation of a first subset 1870a of TCI states from a plurality of TCI states 1770 (e.g., DLorJoint-TCIStateList). The first activation command 1820 may activate, select, display, update and / or indicate the activation of a first subset 1870a of TCI states from a second plurality of TCI states 1770 (e.g., UL-TCIStateList).

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

[0254] The wireless device 1805 may map a first subset 1870a of TCI states to one or more first TCI code points 1870b. A first activation command may indicate a mapping of a first subset of TCI states to one or more first TCI code points. The wireless device 1805 may map each TCI state of the first subset 1870a of TCI states to each TCI code point of one or more first TCI code points 1870b. One or more first TCI code points 1870b may indicate and / or include the first subset 1870a of TCI states. Each TCI code point of one or more first TCI code points 1870b may include, indicate, and / or map to each TCI state of the first subset 1870a of TCI states. Each of the one or more first TCI code points 1870b may contain, represent, and / or map to one or more TCI states. The one or more first TCI code points 1870b may be associated with a first CORESET pool index 1825.

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

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

[0257] The number of one or more first TCI code points 1870b may be greater than one. A radio device 1805 may receive a first DCI (e.g., DCI 1 1830 at time T2 in Figure 18). A radio device may receive the first DCI 1830 via a first CORESET 1838 (e.g., CORESET 1 in Figure 18) having a first CORESET pool index 1825 (e.g., CORESET pool index 0). Multiple CORESETs may include a first CORESET 1838. One or more configuration parameters may indicate a first CORESET pool index 1825 for a first CORESET 1838. One or more configuration parameters may not indicate a CORESET pool index for a first CORESET 1838. 838 may be associated with the first CORESET pool index 1825 (e.g., CORESET pool index 0) for the first CORESET 1838, for example, based on the fact that one or more configuration parameters do not indicate a CORESET pool index. The default value for the CORESET pool index of the first CORESET 1838 may be equal to the first CORESET pool index 1825 (e.g., CORESET pool index 0) for the first CORESET 1838, for example, based on the fact that one or more configuration parameters do not indicate a CORESET pool index for the first CORESET 1838.

[0258] The first DCI 1830 (for example, DCI 1 as described herein in Figure 18) may be, for example, DCI format 1_1. The first DCI 1830 may be, for example, DCI format 1_2. The first DCI 1830 may be, for example, DCI format 1_x (x=0, 1, 2, ...). The first DCI 1830 may be, for example, DCI format 0_x (x=0, 1, 2, ...).

[0259] The first DCI 1830 may include a first TCI field 1835. The first TCI field 1835 may indicate a first TCI code point in one or more first TCI code points 1870b. The first TCI field 1835 may indicate a first TCI code point in one or more first TCI code points 1870b associated with the first CORESET pool index 1825, based on receiving the first DCI 1830 via a first CORESET 1838 having a first CORESET pool index 1825. The value of the first TCI field 1835 (e.g., 110 in Figure 18) may be equal to, for example, the first TCI code point. The value of the first TCI field 1835 may indicate, for example, the first TCI code point. A first TCI code point (e.g., 110) may indicate, include, and / or map to a first TCI state (e.g., TCI state 26 in Figure 18). A first subset 1870a of TCI states may include the first TCI state. A first DCI 1830 may activate and / or indicate the activation of the first TCI state. A first DCI 1830 may indicate the activation of the first TCI state. A first TCI field 1835 in the first DCI 1830 may indicate the first TCI state in a first subset 1870a of TCI states, for example, based on the reception of the first DCI 1830 at the first CORESET pool index 1825 via the first CORESET 1838. The first TCI field 1835 in the first DCI 1830 may indicate a first TCI state in the first subset 1870a of the TCI state, based on a first activation command 1820 that indicates the activation of the first subset 1870a of the TCI state, which includes a field having a first CORESET pool index 1825, which may be identical to the index of the first CORESET 1838.

[0260] The first TCI state may be (or be used interchangeably with) the first unified TCI state. The first TCI state may be (or be used interchangeably with) the first joint TCI state. The first TCI state may be (or be used interchangeably with) the first downlink TCI state. The first TCI state may be (or be used interchangeably with) the first joint / downlink TCI state. The first TCI state may be (or be used interchangeably with) the first uplink TCI state.

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

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

[0263] A wireless device may apply a first TCI state to uplink transmissions associated with a first CORESET pool index 1825 (e.g., PUSCH transmission, transport block, PUCCH transmission, SRS, etc.).

[0264] One or more configuration parameters may indicate a first CORESET pool index 1825 for an uplink resource and / or an uplink resource set and / or a group containing an uplink resource. The wireless device 1805 may transmit (e.g., send) an uplink signal (e.g., UCI, HARQ-ACK, SR, CSI report, SRS) via the uplink resource, for example, based on (e.g., in response to) one or more configuration parameters indicating a first CORESET pool index 1825 for an uplink resource and / or an uplink resource set and / or a group containing an uplink resource, and based on a first TCI state. The cell's uplink BWP (e.g., active uplink BWP) may contain an uplink resource. The uplink resource may be, for example, a PUCCH resource. The uplink signal may be a UCI (e.g., UCI, HARQ-ACK, SR, CSI report). The uplink resource may be, for example, an SRS resource. The uplink signal may be an SRS. The uplink resource may be, for example, a PUSCH resource. An uplink signal may be a push transmission (e.g., a transport block) of a configured uplink grant (e.g., a configured uplink grant of type 1). Transmission of an uplink signal over an uplink resource may be associated with a first CORESET pool index 1825, for example, with respect to an uplink resource and / or uplink resource set and / or group containing an uplink resource, based on one or more configuration parameters indicating a first CORESET pool index 1825.

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

[0266] The wireless device 1805 may receive a second activation command 1840 (e.g., MAC-CE, DCI, downlink control command / message, RRC, control command / message, unified TCI state activation / deactivation MAC CE, activation command 2, at time T3 as described herein in Figure 18). The second activation command 1840 may activate, select, display, update and / or indicate the activation of a second subset 1880a of TCI states from among multiple TCI states (e.g., DLorJoint-TCIStateList). The second activation command 1840 may activate, select, display, update and / or indicate the activation of a second subset 1880a of TCI states from a second set of multiple TCI states (e.g., UL-TCIStateList).

[0267] The second activation command 1840 may include a field (e.g., CoresetPoolID) having a second CORESET pool index 1845 (e.g., CORESET pool index 1 in Figure 18). The value in the field may be equal to the second CORESET pool index 1845, which may be equal to, for example, 1. A second subset of the TCI state subset 1880a may be associated with the second CORESET pool index 1845. The second subset of the TCI state 1880a may be associated with the second CORESET pool index 1845 based on the second activation command 1840, which indicates the activation of the second subset of the TCI state 1880a, for example, including a field having the second CORESET pool index 1845. A wireless device may activate the second subset 1880a of the TCI state with respect to the second CORESET pool index 1845.

[0268] Wireless device 1805 maps a second subset 1880a of TCI states to one or more second TCI code points 1880b. The second activation command may indicate the mapping of a second subset of TCI states to one or more second TCI code points. Wireless device 1805 may map each TCI state of the second subset of TCI states 1880a to each TCI code point of one or more second TCI code points 1880b. One or more second TCI code points 1880b may indicate, include, and / or be mapped to a second subset of TCI states 1880a. Each TCI code point of one or more second TCI code points 1880b may include, indicate, and / or be mapped to each TCI state of the second subset of TCI states 1880a. Each TCI code point of one or more second TCI code points 1880b may include, indicate, and / or be mapped to one or more TCI states. One or more second TCI code points 1880b may be associated with a second CORESET pool index 1845.

[0269] In Figure 18, for example, a second subset 1880a of TCI states may be TCI state 8, TCI state 61, and TCI state 21. One or more second TCI code points 1880b may include a first TCI code point (e.g., TCI code point 000), a second TCI code point (e.g., TCI code point 001), and a third TCI code point (e.g., TCI code point 110). The first TCI code point (e.g., TCI code point 000) may include and / or represent TCI state 8. The second TCI code point (e.g., TCI code point 001) may include and / or represent TCI state 61. The third TCI code point (e.g., TCI code point 110) may include and / or represent TCI state 21. A first TCI code point (e.g., TCI code point 000), a second TCI code point (e.g., TCI code point 001), and a third TCI code point (e.g., TCI code point 110) may include and / or represent a single TCI state (e.g., a single joint TCI state, a single uplink TCI state, a single downlink TCI state, etc.).

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

[0271] The quantity of one or more second TCI code points 1880b may be greater than one. The wireless device 1805 may receive a second DCI 1850 (e.g., DCI2 at time T4 in FIG. 18) via a second CORESET 1858 (e.g., CORESET2 in FIG. 18) having a second CORESET pool index 1845 (e.g., CORESET pool index 1). One or more configuration parameters may indicate the second CORESET pool index 1845 for the second CORESET 1858. The plurality of CORESETs may include the second CORESET 1858.

[0272] The second DCI 1850 may be, for example, DCI format 1_1. The second DCI 1850 may be, for example, DCI format 1_2. The second DCI 1850 may be, for example, DCI format 1_x (x = 0, 1, 2,...). The second DCI 1850 may be, for example, DCI format 0_x (x = 0, 1, 2,...).

[0273] The second DCI 1850 may include a second TCI field 1855. The second TCI field 1855 may indicate a second TCI code point in one or more second TCI code points 1880b. The second TCI field 1855 may indicate a second TCI code point in one or more second TCI code points 1880b associated with a second CORESET pool index 1845, based on receiving the second DCI 1850 via a second CORESET 1858 having a second CORESET pool index 1845. The value of the second TCI field 1855 (e.g., 001 in Figure 18) may be equal to, for example, a second TCI code point. The value of the second TCI field 1855 may indicate, for example, a second TCI code point. A second TCI code point (e.g., 001) may indicate, include, and / or map to a second TCI state (e.g., TCI state 61 in Figure 18). A second subset 1880a of TCI states may include a second TCI state. A second DCI 1850 may activate and / or indicate the activation of a second TCI state. A second DCI 1850 may indicate the activation of a second TCI state. A second TCI field 1855 in the second DCI 1850 may indicate a second TCI state in a second subset 1880a of TCI states, based on the fact that the second DCI 1850 was received via a second CORESET 1858 having a second CORESET pool index 1845. The second TCI field 1855 in the second DCI 1850 may indicate a second TCI state in the second subset 1880a of the TCI state, based on a second activation command 1840 that indicates the activation of the second subset 1880a of the TCI state, which includes a field having a second CORESET pool index 1845 that may be identical to the index of the second CORESET 1858.

[0274] The second TCI state may be (and / or be used interchangeably with) the second unified TCI state. The second TCI state may be (and / or be used interchangeably with) the second joint TCI state. The second TCI state may be (and / or be used interchangeably with) the second downlink TCI state. The second TCI state may be (and / or be used interchangeably with) the second joint / downlink TCI state. The second TCI state may be (and / or be used interchangeably with) the second uplink TCI state.

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

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

[0277] The wireless device 1805 can apply a second TCI state to uplink transmissions (e.g., PUSCH transmissions, transport blocks, PUCCH transmissions, SRS, etc.) associated with a second CORESET pool index 1845. One or more configuration parameters may indicate a second CORESET pool index 1845 for uplink resources and / or uplink resource sets and / or groups containing uplink resources.

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

[0279] The wireless device 1805 may receive a DCI via a CORESET having a second CORESET pool index 1845 that triggers and / or schedules the transmission of an uplink signal (e.g., PUSCH transmit, transport block, SRS, HARQ-ACK). Multiple CORESETs may include CORESETs. The uplink signal may be associated with the second CORESET pool index 1845, for example, based on receiving a DCI via a CORESET having the second CORESET pool index 1845. The wireless device may transmit (e.g., transmit) the uplink signal based on a second TCI state, for example, based on (e.g., in response to) the uplink signal being associated with the second CORESET pool index 1845.

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

[0281] A first TCI state may be associated with the PCI of a cell. A first TCI state may not include at least one additional PCI index. Additional PCI indexes may be absent from the configuration parameters of the first TCI state. One or more configuration parameters may be included from the configuration parameters of the first TCI state. A first TCI state may be associated with the PCI of a cell, for example, based on the fact that the first TCI state does not include at least one additional PCI index. A first reference signal may be quasi-co-configured with a first SS / PBCH block. A first reference signal may be a first SS / PBCH block. A first reference signal may be quasi-co-configured with a first CSI-RS which may be quasi-co-configured with a first SS / PBCH block. A first SS / PBCH block may be associated with a cell. A first SS / PBCH block may be associated with the PCI of a cell. One or more configuration parameters may indicate a first SS / PBCH block for a cell.

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

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

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

[0285] The second cell identified and / or indicated by the second PCI may be a non-serving cell. The second cell identified and / or indicated by the second PCI may be an adjacent cell. The second cell identified and / or indicated by the second PCI may be a candidate and / or support cell.

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

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

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

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

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

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

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

[0293] The wireless device 1805 may receive a first DCI 1830 via a first CORESET 1838 that schedules a first PUSCH transmission. Multiple CORESETs may include the first CORESET 1838. The first DCI 1830 may include fields having first values ​​(e.g., 0, 00, 10, 11) that indicate a first TCI state (e.g., an SRS resource set indicator field, a TRP field, a CORESET pool index field, an additional PCI index, a BFD set index, a unified TCI state indicator field, a joint TCI state indicator field, an uplink TCI state indicator field, a panel index, a capability set index, etc.). Based on the first TCI state, the wireless device may transmit (e.g., send) a first PUSCH transmission based on (e.g., in response to) the first DCI 1830 which includes fields having first values ​​that indicate the first TCI state. One or more first uplink channels and / or resources may include push transmissions scheduled by DCIs that include a field having a first value. Each DCI may schedule one or more push transmissions of push transmissions.

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

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

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

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

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

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

[0300] One or more configuration parameters may indicate a field (e.g., SRS resource set indicator field, TRP field, CORESET pool index field, additional PCI index, BFD set index, unified TCI state indicator field, joint TCI state indicator field, uplink TCI state indicator field, panel index, capability set index, etc.) for a first PUCCH resource set and / or group having a first value (e.g., 0, 00, 10, 11) indicating a first TCI state. A wireless device may transmit (e.g., send) uplink signals (e.g., SR, HARQ-ACK, CSI report, uplink control information) over the PUCCH resources in the first PUCCH resource set and / or group based on the first TCI state, for example, based on one or more configuration parameters indicating a field having a first value indicating a first TCI state for a first PUCCH resource set and / or group (e.g., in response to that). A wireless device may transmit (e.g., send) its respective uplink signals (e.g., SR, HARQ-ACK, CSI report, uplink control information) through each PUCCH resource in a first PUCCH resource set and / or group, based on a first TCI state, for example, based on one or more configuration parameters indicating a field having a first value indicating the first TCI state for a first PUCCH resource set and / or group (e.g., in response thereto). One or more first uplink channels and / or resources may include PUCCH transmissions through each PUCCH resource in the first PUCCH resource set and / or group.

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

[0302] A wireless device may receive a first DCI 1830 via a first CORESET 1838 that triggers and / or schedules the transmission of a first PUCCH transmission (e.g., a HARQ-ACK feedback transmission). The first DCI 1830 may, for example, schedule a PDSCH reception. The first DCI 1830 may, for example, indicate a SCell hibernation state. The first DCI 1830 may, for example, indicate an SPS PDSCH release. The first DCI 1830 may, for example, indicate the activation of a unified TCI state. Multiple CORESETs may include the first CORESET 1838. The first DCI 1830 may include fields having a first value (e.g., 0, 00, 10, 11) that indicates a first TCI state (e.g., an SRS resource set indicator field, a TRP field, a CORESET pool index field, an additional PCI index, a BFD set index, a unified TCI state indicator field, a joint TCI state indicator field, an uplink TCI state indicator field, a panel index, a capability set index, etc.). A wireless device may transmit (e.g., send) a first PUCCH transmission based on the first TCI state, for example, based on (e.g., in response to) the first DCI 1830 which includes fields having a first value that indicates the first TCI state. One or more first uplink channels and / or resources may include PUCCH transmissions that are triggered and / or scheduled by a DCI which includes fields having a first value.

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

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

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

[0306] One or more configuration parameters may indicate a field (e.g., SRS resource set indicator field, TRP field, CORESET pool index field, additional PCI index, BFD set index, unified TCI status indicator field, joint TCI status indicator field, uplink TCI status indicator field, panel index, capability set index, etc.) for a first SRS resource having a first value (e.g., 0) that indicates a first TCI status. A wireless device may transmit (e.g., transmit) an SRS resource over the first SRS resource based on the first TCI status, for example, based on the fact that one or more configuration parameters indicate a field with a first value that can indicate a first TCI status for the first SRS resource. One or more first uplink channels and / or resources may include SRS transmission over the first SRS resource.

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

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

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

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

[0311] A first CORESET 1838 may be associated with a first CORESET pool index 1825 (e.g., CoresetPoolIndex=0). One or more configuration parameters may indicate the first CORESET pool index 1825 for a first CORESET 1838. One or more configuration parameters may not indicate a CORESET pool index for a first CORESET 1838. A wireless device may transmit (e.g., transmit) an SRS based on (e.g., in response to) a first DCI 1830 that, based on a first TCI state, triggers and / or schedules the transmission of an SRS through a first CORESET 1838 having the first CORESET pool index 1825. One or more first uplink channels and / or resources may include SRS transmissions triggered and / or scheduled by DCIs received through one or more first CORESETs having the first CORESET pool index 1825. Multiple CORESETs can contain one or more first CORESETs.

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

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

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

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

[0316] A wireless device may receive a first DCI via a first CORESET that schedules a first PDSCH reception. Multiple CORESETs may include the first CORESET. The first DCI may include fields (e.g., SRS resource set indicator field, TRP field, CORESET pool index field, additional PCI index, BFD set index, unified TCI state indicator field, joint TCI state indicator field, uplink TCI state indicator field, panel index, capability set index, etc.) that have a first value (e.g., 0, 00, 10, 11) indicating a first TCI state. Based on the first TCI state, the wireless device may receive / perform a first PDSCH reception based on a first DCI that includes fields having a first value indicating the first TCI state (e.g., in response to ). One or more first downlink channels / resources may be / include PDSCH receptions scheduled by a DCI message that includes fields having a first value. Each DCI message may schedule one or more PDSCH receptions.

[0317] A first CORESET may be associated with a first CORESET pool index (e.g., CoresetPoolIndex=0). One or more configuration parameters may indicate a first CORESET pool index for a first CORESET. For example, one or more configuration parameters may not indicate a CORESET pool index for a first CORESET. A wireless device may receive / perform a first PDSCH receive based on a first TCI state. A wireless device may receive / perform a first PDSCH receive based on (e.g., in response to) receiving a first DCI that schedules a first PDSCH receive via a first CORESET (e.g., having a first CORESET pool index). One or more first downlink channels / resources may be / include a first PDSCH receive. One or more first downlink channels / resources may be / include PDSCH receptions scheduled by DCI (e.g., DCI messages) received via one or more first CORESETs having a first CORESET pool index. Multiple CORESETs may include one or more first CORESETs.

[0318] A wireless device may receive a first PDSCH receiver with a first spatial domain receiver / receive filter / beam determined based on a first TCI state. At least one first DM-RS antenna port of the first PDSCH receiver may be (e.g., quasi)co-configured with a first reference signal indicated by the first TCI state.

[0319] One or more configuration parameters may indicate a field (e.g., SRS resource set indicator field, TRP field, CORESET pool index field, additional PCI index, BFD set index, unified TCI state indicator field, joint TCI state indicator field, uplink TCI state indicator field, panel index, capability set index, etc.) that has a first value (e.g., 0, 00, 10, 11) indicating a first TCI state for an SPS PDSCH configuration. A wireless device may receive / perform PDSCH reception for / to an SPS PDSCH configuration based on the first TCI state. A wireless device may receive / perform PDSCH reception for / to an SPS PDSCH configuration based on (e.g., in response to) one or more configuration parameters that indicate a field (e.g., 0, 00, 10, 11) indicating a first TCI state for an SPS PDSCH configuration. One or more first downlink channels / resources may be / include PDSCH transmissions for / to an SPS PDSCH configuration.

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

[0321] One or more first downlink channels / resources may be / contain PDCCHs. One or more first downlink channels / resources may be / contain one or more first PDCCH resources. One or more first downlink channels / resources may be / contain one or more first PDCCH resource sets / groups. One or more first downlink channels / resources may be / contain one or more first PDCCH receivers. One or more first downlink channels / resources may be / contain one or more first coresets. Multiple coresets may contain one or more first coresets.

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

[0323] One or more configuration parameters may indicate, for a first CORESET group, fields having a first value (e.g., 0, 00, 10, 11) that indicates a first TCI state (e.g., SRS resource set indicator field, TRP field, CORESET pool index field, additional PCI index, BFD set index, unified TCI state indicator field, joint TCI state indicator field, uplink TCI state indicator field, panel index, capability set index, etc.). The first CORESET group may include one or more first CORESETs of multiple CORESETs. A wireless device may receive / perform downlink signals (e.g., DCI, PDCCH reception) via the first CORESET in the first CORESET group based on the first TCI state. For example, a wireless device may receive / perform downlink signals via the first CORESET based on (e.g., in response to) one or more configuration parameters indicating fields having a first value that indicates a first TCI state for the first CORESET group. A wireless device may receive / perform its respective downlink signals (e.g., DCI, PDCCH reception) through each CORESET in a first CORESET group based on a first TCI state. A wireless device may receive / perform its respective downlink signals, for example, in response to a first CORESET group, based on one or more configuration parameters indicating a field having a first value indicating a first TCI state. One or more first downlink channels / resources may be / include PDCCH reception through each CORESET in the first CORESET group.

[0324] A wireless device may receive a downlink signal with a first spatial domain receiver / receive filter / beam determined based on a first TCI state. At least one first DM-RS antenna port of the downlink signal may be (e.g., quasi)co-located with a first reference signal indicated by the first TCI state.

[0325] A first CORESET may be associated with a first CORESET pool index (e.g., CoresetPoolIndex=0). One or more configuration parameters may indicate the first CORESET pool index for a first CORESET. For example, one or more configuration parameters may not indicate the CORESET pool index (e.g., the default CORESET pool index=0) for a first CORESET. A wireless device may receive / perform a first PDCCH reception (e.g., DCI, or containing / carrying / having DCI) via a first CORESET, for example, in response to the first CORESET being associated with a first CORESET pool index, based on a first TCI state. One or more first downlink channels / resources may be / contain PDCCH receptions via one or more first CORESETs having a first CORESET pool index. Multiple CORESETs may contain one or more first CORESETs. One or more first CORESETs may include a first CORESET.

[0326] A wireless device may receive a first PDCCH receiver with a first spatial domain receiver / receive filter / beam determined based on a first TCI state. At least one first DM-RS antenna port of the first PDCCH receiver may be quasi-co-configured with a first reference signal indicated by the first TCI state.

[0327] One or more first downlink channels / resources may be / include CSI-RS. One or more first downlink channels / resources may be / include one or more first CSI-RS resources. One or more first downlink channels / resources may be / include one or more first CSI-RS resource sets / groups. One or more first downlink channels / resources may be / include one or more first CSI-RS receivers.

[0328] One or more configuration parameters may indicate a field (e.g., SRS resource set indicator field, TRP field, CORESET pool index field, additional PCI index, BFD set index, unified TCI status indicator field, joint TCI status indicator field, uplink TCI status indicator field, panel index, capability set index, etc.) for a first CSI-RS resource having a first value (e.g., 0) indicating a first TCI status. A wireless device may receive CSI-RS via the first CSI-RS resource based on the first TCI status. A wireless device may receive CSI-RS via the first CSI-RS resource based on (e.g., in response to) one or more configuration parameters indicating a field (e.g., a field having a first value indicating a first TCI status) for a first CSI-RS resource. One or more first downlink channels / resources may be / include CSI-RS reception via the first CSI-RS resource.

[0329] One or more configuration parameters may indicate a field (e.g., SRS resource set indicator field, TRP field, CORESET pool index field, additional PCI index, BFD set index, unified TCI status indicator field, joint TCI status indicator field, uplink TCI status indicator field, panel index, capability set index, etc.) for a first CSI-RS resource set / group having a first value (e.g., 0, 00, 10, 11) indicating a first TCI status. A wireless device may receive CSI-RS via the CSI-RS resources in the first CSI-RS resource set / group based on the first TCI status. For example, a wireless device may receive CSI-RS via the CSI-RS resources in the first CSI-RS resource set / group based on one or more configuration parameters indicating a field (e.g., in response) for a first CSI-RS resource set / group having a first value indicating a first TCI status. A wireless device may receive its respective CSI-RS through each CSI-RS resource in a first CSI-RS resource set / group based on a first TCI state. For example, a wireless device may receive its respective CSI-RS through each CSI-RS resource in a first CSI-RS resource set / group based on (e.g., in response to) one or more configuration parameters indicating a field having a first value indicating a first TCI state for the first CSI-RS resource set / group. One or more first downlink channels / resources may / may include CSI-RS reception through each CSI-RS resource in the first CSI-RS resource set / group.

[0330] A wireless device may receive a first DCI via a first CORESET that triggers / schedules the reception of a CSI-RS. The CSI-RS may be, for example, aperiodic CSI-RS. The CSI-RS may be, for example, semi-persistent CSI-RS. Multiple CORESETs may include the first CORESET. The first DCI may include fields (e.g., SRS resource set indicator field, TRP field, CORESET pool index field, additional PCI index, BFD set index, unified TCI state indicator field, joint TCI state indicator field, uplink TCI state indicator field, panel index, capability set index, etc.) that have a first value (e.g., 0, 00, 10, 11) indicating a first TCI state. A wireless device may receive a CSI-RS based on a first TCI state. A wireless device may receive a CSI-RS based on (e.g., in response to) a first DCI that includes fields having a first value indicating a first TCI state. One or more first downlink channels / resources may be / include CSI-RS receptions triggered / scheduled by DCI, which include a field having a first value.

[0331] A first CORESET may be associated with a first CORESET pool index (e.g., CoresetPoolIndex=0). One or more configuration parameters may indicate the first CORESET pool index for a first CORESET. For example, one or more configuration parameters may not indicate the CORESET pool index for a first CORESET. A wireless device may receive CSI-RS based on a first TCI state. A wireless device may receive CSI-RS based on (e.g., in response to) receiving a first DCI that triggers / schedules the reception of CSI-RS via a first CORESET having the first CORESET pool index. One or more first downlink channels / resources may be / include CSI-RS receptions triggered / scheduled by DCIs received via one or more first CORESETs having the first CORESET pool index. Multiple CORESETs may include one or more first CORESETs.

[0332] A wireless device may receive and / or measure and / or evaluate CSI-RS using a first spatial domain receiver and / or receiver filter / beam determined based on a first TCI state. A wireless device may receive and / or measure and / or evaluate the wireless link quality (e.g., RSRP, BLER, SINR, SNR) of CSI-RS using a first spatial domain receiver and / or receiver filter and / or beam determined based on a first TCI state.

[0333] A wireless device may apply (e.g., use) a second TCI state to one or more second uplink channels / resources of a cell. Applying a first TCI state to one or more second uplink channels / resources may include transmitting (e.g., transmitting) an uplink signal over one or more second uplink channels / resources based on the second TCI state. A wireless device may transmit (e.g., transmit) an uplink signal over one or more second uplink channels and / or resources based on the second TCI state. A wireless device may transmit (e.g., transmit) each uplink signal over each of the one or more second uplink channels and / or resources based on the second TCI state.

[0334] A wireless device may transmit (e.g., transmit) an uplink signal having a transmit power determined based on a second TCI state over on...

Claims

1. It is a method, The wireless device initiates a random access procedure to the cell, Based on whether the cell is a serving cell or a candidate cell, Stopping the bandwidth partial inactive timer of the aforementioned cell, or Performing at least one of the following: switching the active bandwidth portion of the cell to the second bandwidth portion of the cell; A method comprising transmitting a random access preamble for the aforementioned random access procedure and through the aforementioned cell.

2. Receiving one or more messages containing one or more configuration parameters of the cell, wherein the one or more configuration parameters are A first control resource set pool index for one or more first control resource sets in the active bandwidth portion of the cell, A second control resource set pool index for one or more second control resource sets in the active bandwidth portion of the cell, A single reference signal resource set associated with the first control resource set pool index, and receiving, Receiving control information for scheduling uplink transmissions via a control resource set among the one or more first control resource sets associated with the first control resource set pool index, The method according to claim 1, further comprising determining not to monitor each of the one or more second control resource sets associated with the second control resource set pool index, based on one or more configuration parameters indicating the single reference signal resource set associated with the first control resource set pool index.

3. The method according to claim 1 or 2, wherein the cell is for a layer 1 / layer 2 triggered mobility procedure.

4. Based on the fact that the cell is the candidate cell, The bandwidth partial inactive timer of the aforementioned cell is not stopped, The method according to any one of claims 1 to 3, further comprising not switching the active bandwidth portion of the cell to the second bandwidth portion of the cell.

5. Based on the absence of a random access response configured for the aforementioned random access procedure, The bandwidth partial inactive timer of the aforementioned cell is not stopped, The method according to any one of claims 1 to 4, further comprising not switching the active bandwidth portion of the cell to the second bandwidth portion of the cell.

6. The method according to any one of claims 1 to 5, wherein initiating the random access procedure for a candidate cell is based on receiving a physical control channel sequence having a physical cell identifier field indicating the candidate cell.

7. The method according to any one of claims 1 to 6, wherein the wireless device comprises two reference signal resource sets, each reference signal resource set corresponding to a usage parameter set in a codebook or non-codebook, in which the wireless device comprises a higher-layer parameter including two different values ​​of a control resource set pool index in the control resource set for the active bandwidth portion of the serving cell.

8. Receiving one or more messages containing one or more configuration parameters, where the one or more configuration parameters are At least two control resource set pool indices for the bandwidth portion of the cell, A reference signal resource set for the uplink bandwidth portion of the cell, wherein the reference signal resource set is associated with a first control resource set pool index among the at least two control resource set pool indices, and to receive, The further includes receiving control information for scheduling uplink transmissions over the uplink bandwidth portion of the cell via a control resource set having one of the at least two control resource set pool indices, The method according to any one of claims 1 to 7, wherein the control information indicates a single layer for the uplink transmission based on the fact that the control resource set pool index of the control resource set is different from the first control resource set pool index.

9. Based on the fact that the cell is the serving cell, To stop the bandwidth partial inactive timer of the cell, The method according to any one of claims 1 to 8, further comprising switching the active bandwidth portion of the cell to the second bandwidth portion of the cell.

10. The aforementioned cell, Special cell (SpCell), Primary cell (PCell), or The method according to any one of claims 1 to 9, wherein at least one of the secondary cells (SCells).

11. The method according to any one of claims 1 to 10, further comprising receiving a random access response corresponding to the random access preamble via the second bandwidth portion.

12. The method according to any one of claims 1 to 11, further comprising starting the bandwidth partial inactive timer based on the completion of the random access procedure.

13. A wireless device, One or more processors, A wireless device comprising: a memory that stores instructions for causing the wireless device to perform the method according to any one of claims 1 to 12 when executed by the one or more processors.

14. It is a system, A wireless device configured to perform the method described in any one of claims 1 to 12, A system comprising a base station configured to receive the aforementioned random access preamble.

15. A computer-readable medium that stores, when executed, instructions that cause the execution of the method according to any one of claims 1 to 12.

Images