Reference signal reception using reference cells

Abstract

A wireless device may communicate with a base station via a channel of a cell. A property of the channel may be evaluated based on a reference signal. The reference signal may be indicated by a transmission configuration indication state, which may be determined based on a list of transmission configuration indication states configured for the cell and / or a reference cell.

Description

[0001] Cross-referencing related applications

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 432,632, filed December 14, 2022. The entire contents of the application cited above are incorporated herein by reference. Background Technology

[0003] The wireless device communicates with the base station. The wireless device measures and reports channel state information of the communication channel. Summary of the Invention

[0004] The following summary presents a simplified overview of certain features. This summary is not a comprehensive overview and is not intended to identify any important or key elements.

[0005] The wireless device can communicate with a base station. The wireless device can be configured to communicate via a channel of the cell. The nature of the channel (e.g., channel state information) can be determined by measuring a reference signal. The reference signal can be measured based on a transmission configuration indication state. The transmission configuration indication state can be determined based on a list of transmission configuration indication states configured for the cell. Alternatively, the transmission configuration indication state can be determined based on a list of transmission configuration indication states configured for a reference cell (e.g., downlink or joint transmission configuration indication state parameters and / or unified transmission configuration indication state reference parameters). For example, even without a list of transmission configuration indication states configured for the cell, accurate channel assessment can be achieved by measuring the reference signal based on the transmission configuration indication state determined using the configuration information of the reference cell.

[0006] These and other features and advantages are described in more detail below. Attached Figure Description

[0007] Examples of several embodiments of the various embodiments of this disclosure are described herein with reference to the accompanying drawings.

[0008] Figure 1A and Figure 1B An exemplary communication network is shown.

[0009] Figure 2A An exemplary user plane is shown.

[0010] Figure 2B An exemplary control plane configuration is shown.

[0011] Figure 3 An example of a protocol layer is shown.

[0012] Figure 4A An exemplary downlink data flow for user plane configuration is shown.

[0013] Figure 4BAn exemplary format of the MAC subheader in a Media Access Control (MAC) Protocol Data Unit (PDU) is shown.

[0014] Figure 5A An exemplary mapping of the downlink channel is shown.

[0015] Figure 5B An exemplary mapping of the uplink channel is shown.

[0016] Figure 6 An exemplary Radio Resource Control (RRC) state and RRC state transitions are shown.

[0017] Figure 7 An exemplary configuration of the frame is shown.

[0018] Figure 8 An exemplary resource configuration for one or more carriers is shown.

[0019] Figure 9 An exemplary configuration of the Bandwidth Component (BWP) is shown.

[0020] Figure 10A An exemplary carrier aggregation configuration based on component carriers is shown.

[0021] Figure 10B An example cell group is shown.

[0022] Figure 11A An exemplary mapping of one or more Synchronization Signal / Physical Broadcast Channel (SS / PBCH) blocks is shown.

[0023] Figure 11B An exemplary mapping of one or more Channel State Information Reference Signals (CSI-RS) is shown.

[0024] Figure 12A An example of a downlink beam management procedure is shown.

[0025] Figure 12B An example of an uplink beam management procedure is shown.

[0026] Figure 13A An exemplary four-step random access procedure is shown.

[0027] Figure 13B An exemplary two-step random access procedure is shown.

[0028] Figure 13C An exemplary two-step random access procedure is shown.

[0029] Figure 14A An example of the configuration of the Control Resource Set (CORESET) is shown.

[0030] Figure 14B An example of the mapping from control channel elements to resource element groups (CCE to REG) is shown.

[0031] Figure 15A An example of communication between a wireless device and a base station is shown.

[0032] Figure 15B Exemplary elements of a computing device that can be used to implement any of the various apparatuses described herein are shown.

[0033] Figure 16A , Figure 16B , Figure 16C and Figure 16D Examples of uplink and downlink signal transmission are shown.

[0034] Figure 17 An example of TCI state activation is shown.

[0035] Figure 18 An example of TCI state activation is shown.

[0036] Figure 19 An example of a CSI measurement is shown.

[0037] Figure 20A An example of Radio Resource Control (RRC) configuration parameters for Channel State Information Reference Signal (CSI-RS) resources is shown.

[0038] Figure 20B An example Radio Resource Control (RRC) configuration parameter for an aperiodic Channel State Information (CSI) report is shown.

[0039] Figure 20C An exemplary Radio Resource Control (RRC) configuration parameter for a Physical Downlink Shared Channel (PDSCH) is shown.

[0040] Figure 21A and 21B An example of a CSI measurement is shown. Detailed Implementation

[0041] The accompanying drawings and description provide examples. It should be understood that the examples shown and / or described in the drawings are non-exclusive, and the features shown and described can be practiced in other examples. Examples of operation of wireless communication systems that can be used in the field of multi-carrier communication systems are provided.

[0042] Figure 1AAn exemplary communication network 100 is illustrated. Communication network 100 may include a mobile communication network. Communication network 100 may include, for example, a Public Land Mobile Network (PLMN) operated / managed / run by a network operator. Communication network 100 may include one or more of a core network (CN) 102, a radio access network (RAN) 104, and / or a wireless device 106. Communication network 100 may include one or more data networks (DNs) 108, and / or devices within communication network 100 may communicate with (e.g., via CN 102) said one or more data networks. Wireless device 106 may communicate with one or more DNs 108, such as public DNs (e.g., the Internet), private DNs, and / or operator-internal DNs. Wireless device 106 may communicate with one or more DNs 108 via RAN 104 and / or via CN 102. CN 102 may provide / configure one or more interfaces to wireless device 106 that interface with one or more DNs 108. As part of the interface functionality, CN 102 can set up end-to-end connections between wireless device 106 and one or more DN 108, authenticate wireless device 106, provide / configure charging functionality, etc.

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

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

[0045] RAN 104 may include one or more base stations (not shown). As used throughout, the term "base station" may include one or more of the following: base station, node, Node B (NB), evolved Node B (eNB), gNB, ng-eNB, relay node (e.g., Integrated Access and Backhaul (IAB) node), donor node (e.g., donor eNB, donor gNB, etc.), access point (e.g., Wi-Fi access point), transmit and receive point (TRP), computing device, device capable of wireless communication, or any other device capable of transmitting and / or receiving signals. A base station may include one or more of each of the elements listed above. For example, a base station may include one or more TRPs. As other non-limiting examples, a base station may include one or more of the following: a Node B (e.g., associated with Universal Mobile Telecommunications System (UMTS) and / or third-generation (3G) standards), an evolved Node B (eNB) (e.g., associated with Evolved Universal Terrestrial Radio Access (E-UTRA) and / or fourth-generation (4G) standards), a Remote Radio Header (RRH), a baseband processing unit coupled to one or more RRHs, a repeater node or relay node for extending the coverage area of ​​a donor node, a Next Generation Evolved Node B (ng-eNB), a Second Generation Node B (gNB) (e.g., associated with NR and / or fifth-generation (5G) standards), an Access Point (AP) (e.g., associated with, for example, Wi-Fi or any other suitable wireless communication standard), any other generation of base stations, and / or any combination thereof. A base station may include one or more devices, such as at least one base station central device (e.g., a gNB central unit (gNB-CU)) and at least one base station distributed device (e.g., a gNB distributed unit (gNB-DU)).

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

[0047] One or more base stations (e.g., in RAN 104) can be implemented as sector sites with more or fewer than three sectors. One or more base stations in RAN 104 can be implemented as access points, baseband processing units / units coupled to several RRHs, and / or repeaters or relay nodes for extending the coverage area of ​​nodes (e.g., donor nodes). Baseband processing units / units coupled to RRHs can be part of a centralized or cloud RAN architecture, for example, where baseband processing units / units can be centralized in a pool of baseband processing units / units or virtualized. Repeater nodes can amplify and transmit (e.g., transmit, retransmit, rebroadcast, etc.) radio signals received from donor nodes. Relay nodes can perform substantially the same / similar functions as repeater nodes. Relay nodes can decode radio signals received from donor nodes, for example, to remove noise before amplifying and transmitting the radio signals.

[0048] RAN 104 can be deployed as a homogeneous network of base stations (e.g., macrocell base stations) with similar antenna patterns and / or similar high levels of transmission power. RAN 104 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, such as coverage areas overlapping 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 with high data traffic (or so-called "hot spots") or in areas with weak macrocell coverage. Examples of small cell base stations can include (in descending order of coverage area) microcell base stations, picocell base stations, femtocell base stations, or femtocell base stations.

[0049] The examples described herein can be used for various types of communications. For example, communications can be based on the 3rd Generation Partnership Project (3GPP) (e.g., one or more network elements similar to a network element in a communications network 100), communications based on the Institute of Electrical and Electronics Engineers (IEEE), communications based on the International Telecommunication Union (ITU), communications based on the International Organization for Standardization (ISO), and so on. 3GPP specifies multiple generations of mobile networks: 3G networks known as UMTS, 4G networks known as Long Term Evolution (LTE) and LTE-Advanced (LTE-A), and 5G networks known as 5G Systems (5GS) and NR Systems. 3GPP can also specify additional generations of communications networks (e.g., 6G and / or any other generation of communications networks). Examples can be described by referring to one or more elements (e.g., RAN) of a 3GPP 5G network (known as Next Generation RAN (NG-RAN)) or any other communications network (such as 3GPP networks and / or non-3GPP networks). The examples described herein can be applied to other communication networks, such as 3G and / or 4G networks, as well as communication networks that may not yet be finalized / designated (e.g., 3GPP 6G networks), satellite communication networks, and / or any other communication networks. NG-RAN implements and updates 5G radio access technology known as NR and can be configured to implement 4G radio access and / or other radio access technologies, such as other 3GPP and / or non-3GPP radio access technologies.

[0050] Figure 1B An exemplary communication network 150 is illustrated. This communication network may include a mobile communication network. Communication network 150 may include, for example, a PLMN operated / managed / run by a network operator. 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., NG-RAN), and / or radio devices 156A and 156B (collectively, radio devices 156). Communication network 150 may include one or more data networks (DN) 170, and / or devices within communication network 150 may communicate with (e.g., via CN 152) said one or more data networks. These components are capable of communicating with... Figure 1A The corresponding components are implemented and operated in essentially the same or similar manner.

[0051] A CN 152 (e.g., a 5G-CN) can provide / configure one or more interfaces to a radio device 156 that interface with one or more DNs 170 (such as public DNs (e.g., the Internet), private DNs, and / or carrier-internal DNs). As part of the interface functions, the CN 152 (e.g., a 5G-CN) can establish end-to-end connections between the radio device 156 and one or more DNs, authenticate the radio device 156, and / or provide / configure charging functions. The CN 152 (e.g., a 5G-CN) can be a service-based architecture, which may differ from other CNs (e.g., such as 3GPP 4G CNs). The architecture of a node of a CN 152 (e.g., a 5G-CN) can be defined as a network function that provides services to other network functions via interfaces. The network functions of a CN 152 (e.g., a 5G CN) can be implemented in several ways, such as 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).

[0052] CN 152 (e.g., 5G-CN) may include Access and Mobility Management Function (AMF) device 158A and / or User Plane Function (UPF) device 158B, which may be a separate component or a single AMF / UPF device 158. UPF device 158B may serve as a gateway between RAN 154 (e.g., NG-RAN) and one or more DNs 170. UPF device 158B may perform functions such as: packet routing and forwarding, packet inspection and user plane policy rule enforcement, traffic usage reporting, uplink classification supporting the routing of traffic flows to one or more DNs 170, user plane Quality of Service (QoS) processing (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink service authentication), downlink packet buffering, and / or downlink data notification triggering. UPF device 158B may serve as an anchor point for intra / inter-Radio Access Technology (RAT) mobility, an external Protocol (or Packet) Data Unit (PDU) session point interconnected with one or more DNs, and / or a branch point supporting multi-homed PDU sessions. The wireless device 156 can be configured to receive services via a PDU session, which can be a logical connection between the wireless device and the DN.

[0053] The AMF device 158A can perform functions such as: Non-Access Stratum (NAS) signaling termination, NAS signaling security, Access Stratum (AS) security control, inter-CN node signaling for mobility between access networks (e.g., 3GPP access networks and / or non-3GPP networks), idle-mode radio device reachability (e.g., idle-mode UE reachability for controlling and performing paging retransmissions), registration area management, intra-system and inter-system mobility support, access authentication, access authorization including roaming rights checks, mobility management control (e.g., subscriptions and policies), network slicing support, and / or Session Management Function (SMF) selection. NAS can refer to functions operating between the CN and the radio device, and AS can refer to functions operating between the radio device and the RAN.

[0054] CN 152 (e.g., 5G-CN) can be included in Figure 1B One or more additional network functions may not be shown. CN 152 (e.g., 5G-CN) may include one or more means of implementing at least one of the following: 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 function.

[0055] RAN 154 (e.g., NG-RAN) can communicate with radio device 156 via radio communication (e.g., through an air interface). Radio device 156 can communicate with CN 152 via RAN 154. RAN 154 (e.g., NG-RAN) may include one or more first-type base stations (e.g., gNBs including gNB 160A and gNB 160B (collectively referred to as gNB 160)) and / or one or more second-type base stations (e.g., ng eNBs including ng-eNB 162A and ng-eNB 162B (collectively referred to as ng eNB 162)). RAN 154 may include one or more of any number of types of base stations. gNB 160 and ng eNB 162 may be referred to as base stations. Base stations (e.g., gNB 160 and ng gNB 162) may include one or more sets of antennas for wireless communication with radio device 156 (e.g., through an air interface). One or more base stations (e.g., gNB 160 and / or ng eNB 162) may include multiple sets of antennas to control multiple cells (or sectors) separately. The cells of the base stations (e.g., gNB 160 and ng-eNB 162) can provide radio coverage to the wireless device 156 over a wide geographical area to support the mobility of the wireless device.

[0056] Base stations (e.g., gNB 160 and / or ng-eNB 162) can connect to CN 152 (e.g., 5G CN) via a first interface (e.g., NG interface) and to other base stations via a second interface (e.g., Xn interface). The NG and Xn interfaces can be established using direct physical connections and / or indirect connections via underlying transport networks (such as Internet Protocol (IP) transport networks). Base stations (e.g., gNB 160 and / or ng-eNB 162) can communicate with wireless device 156 via a third interface (e.g., Uu interface). Base station (e.g., gNB 160A) can communicate with wireless device 156A via the Uu interface. The NG, Xn, and Uu interfaces can be associated with a protocol stack. The protocol stack associated with the interface can be... Figure 1B The network elements shown are used to exchange data and signaling messages. The protocol stack can include two planes: a user plane and a control plane. Any other number of planes can be used (e.g., in the protocol stack). The user plane can handle data that is of interest to the user. The control plane can handle signaling messages that are of interest to the network elements.

[0057] One or more base stations (e.g., gNB 160 and / or ng-eNB 162) may communicate with one or more AMF / UPF devices (such as AMF / UPF 158) via one or more interfaces (e.g., NG interfaces). A base station (e.g., gNB 160A) may communicate and / or connect to UPF 158B of AMF / UPF 158 via an NG user plane (NG-U) interface. The NG-U interface may provide / perform the delivery (e.g., non-guaranteed delivery) of user plane PDUs between the base station (e.g., gNB 160A) and the UPF device (e.g., UPF 158B). A base station (e.g., gNB 160A) may communicate and / or connect to an AMF device (e.g., AMF 158A) via an NG control plane (NG-C) interface. The NG-C interface can provide / perform functions such as NG interface management, radio device context management (e.g., UE context management), radio device mobility management (e.g., UE mobility management), NAS message transmission, paging, PDU session management, configuration transfer, and / or warning message transmission.

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

[0059] CN 152 (e.g., 5G-CN) can be configured to handle one or more radio accesses (e.g., NR, 4G, and / or any other radio access). The NR network / device (or any first network / device) can also 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 can be used to provide (or at least support) control plane functions (e.g., initial access, mobility, and / or paging). Although... Figure 1B Only one AMF / UPF 158 is shown, but one or more base stations (e.g., one or more gNBs and / or one or more ng-eNBs) can connect to multiple AMF / UPF nodes, for example, to provide redundancy and / or load sharing across multiple AMF / UPF nodes.

[0060] Network elements (e.g., Figure 1B The interfaces between the network elements shown (e.g., Uu, Xn, and / or NG interfaces) can be associated with a protocol stack that the network elements can use to exchange data and signaling messages. The protocol stack can include two planes: a user plane and a control plane. Any other number of planes can be used (e.g., in the protocol stack). The user plane can handle data associated with the user (e.g., data of interest to the user). The control plane can handle data associated with one or more network elements (e.g., signaling messages of interest to the network elements).

[0061] Figure 1A The communication network 100 and / or Figure 1BThe communication network 150 may include any number and / or type of devices, such as computing devices, wireless devices, mobile devices, handheld devices, tablet computers, laptop computers, Internet of Things (IoT) devices, hotspots, cellular repeaters, and / or more generally user equipment (e.g., UE). Although reference may be made herein to one or more devices of the types described above (e.g., UE, wireless device, computing device, etc.), it should be understood that any device herein may include any one or more devices of the types described above or similar devices. The communication network and any other networks mentioned herein may include LTE networks, 5G networks, satellite networks, and / or any other networks used for wireless communication (e.g., any 3GPP network and / or any non-3GPP network). The devices, systems, and / or methods described herein may generally be described as being implemented on one or more devices (e.g., wireless devices, base stations, eNBs, gNBs, computing devices, etc.) in one or more networks; however, it should be understood that one or more features and steps may be implemented in any device and / or any network.

[0062] Figure 2A An exemplary user plane configuration is shown. This user plane configuration may include, for example, the NR user plane protocol stack. Figure 2B An exemplary control plane configuration is shown. This control plane configuration may include, for example, an NR control plane protocol stack. One or more of the user plane configuration and / or control plane configuration may use a Uu interface that may be located between the wireless device 210 and the base station 220. Figure 2A and Figure 2B The protocol stack shown can be used with, for example, Figure 1B The protocol stack of the Uu interface between the wireless device 156A and the base station 160A shown is basically the same or similar.

[0063] User plane configuration (e.g., NR user plane protocol stack) may be included in the wireless device 210 and base station 220 (e.g., ... Figure 2AThe protocol stack implements multiple layers (e.g., five layers or any other number of layers). At the bottom of the protocol stack, the physical layers (PHY) 211 and 221 can provide transport services to higher layers of the protocol stack and can correspond to Layer 1 of the Open Systems Interconnection (OSI) model. Protocol layers above PHY 211 may include Media Access Control (MAC) 212, Radio Link Control (RLC) 213, Packet Data Convergence Protocol (PDCP) 214, and / or Service Data Application Protocol (SDAP) 215. Protocol layers above PHY 221 may include Media Access Control (MAC) 222, Radio Link Control (RLC) 223, Packet Data Convergence Protocol (PDCP) 224, and / or Service Data Application Protocol (SDAP) 225. One or more of the four protocol layers above PHY 211 can correspond to Layer 2 or the data link layer of the OSI model. One or more of the four protocol layers above PHY 221 can correspond to Layer 2 or the data link layer of the OSI model.

[0064] Figure 3 An example of a protocol layer is shown. A protocol layer can include, for example, the NR user plane protocol stack. One or more services can be provided between protocol layers. SDAP (e.g., Figure 2A and Figure 3SDAPs 215 and 225 (shown) can perform Quality of Service (QoS) stream processing. Radio devices (e.g., radio devices 106, 156A, 156B, and 210) can receive services via / through a PDU session, which can be a logical connection between the radio device and the DN. This PDU session can have one or more QoS streams 310. The DN's UPF (e.g., UPF 158B) can map IP packets to these one or more QoS streams of the PDU session, for example, based on one or more QoS requirements (e.g., based on latency, data rate, bit error rate, and / or any other quality / service requirements). SDAPs 215 and 225 can perform mapping / demapping between one or more QoS streams 310 and one or more radio bearers 320 (e.g., data radio bearers). The mapping / demapping between one or more QoS streams 310 and radio bearers 320 can be determined by SDAP 225 of base station 220. The SDAP 215 of the wireless device 210 can be informed of the mapping between QoS flow 310 and radio bearer 320 via reflection mapping and / or control signaling received from base station 220. For reflection mapping, the SDAP 225 of base station 220 can mark downlink packets with QoS flow indicator (QFI), and the SDAP 215 of wireless device 210 can monitor / detect / identify / indicate / observe the QoS flow indicator to determine the mapping / demapping between one or more QoS flows 310 and radio bearer 320.

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

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

[0067] The RLC layer (e.g., RLC 213 and 223) can perform segmentation, retransmission via Automatic Repeat Request (ARQ), and / or removal of duplicate data units received from the MAC layer (e.g., MAC 212 and 222, respectively). The RLC layer (e.g., RLC 213 and 223) can support multiple transmission modes (e.g., three transmission modes: Transparent Mode (TM); Unacknowledged Mode (UM); and Acknowledged Mode (AM)). The RLC layer can perform one or more of the labeled functions, for example, based on the transmission mode in which the RLC layer is operating. RLC configuration can be per logical channel. RLC configuration may not depend on the parameter set and / or Transmission Time Interval (TTI) duration (or other durations). The RLC layer (e.g., RLC 213 and 223) can provide / configure RLC channels as services for the PDCP layer (e.g., PDCP 214 and 224, respectively), such as... Figure 3 As shown.

[0068] The MAC layer (e.g., MAC 212 and 222) can perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. Multiplexing may include multiplexing data units / data portions belonging to one or more logical channels into transport blocks (TBs) delivered to the PHY layer (e.g., PHY 211 and 221, respectively), and demultiplexing may include demultiplexing data units / data portions from the TB delivered from the PHY layer. The MAC layer of the base station (e.g., MAC 222) 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 at MAC 222) for downlink and / or uplink. The MAC layer (e.g., MAC 212 and 222) may be configured to perform error correction via Hybrid Automatic Repeat Request (HARQ) (e.g., one HARQ entity per carrier in the case of carrier aggregation (CA), and to perform priority handling between logical channels of radio device 210 via logical channel priority ordering and / or filling. The MAC layer (e.g., MAC 212 and 222) can support one or more parameter sets and / or transmission timings. Mapping constraints in logical channel prioritization can control the parameter sets and / or transmission timings that logical channels can use. The MAC layer (e.g., MAC 212 and 222) can provide / configure logical channel 340 as a service against the RLC layer (e.g., RLC 213 and 223).

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

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

[0071] For example, if SDAP 225 receives three IP packets (or another number of IP packets) from one or more QoS flows and maps those three packets (or other number of packets) to radio bearers (e.g., radio bearers 402 and 404), a downlink data flow can begin. SDAP 225 can map IP packets n and n+1 to the first radio bearer 402 and IP packet m to the second radio bearer 404. The SDAP header (in...) Figure 4A Each SDAP SDU shown (preceded by "H") can be added to an IP packet to generate an SDAP PDU, which can be called a PDCP SDU. Data units transmitted from / to higher protocol layers can be called lower protocol layer Service Data Units (SDUs), and data units transmitted to / from lower protocol layers can be called higher protocol layer Protocol Data Units (PDUs). For example... Figure 4A As shown, the data unit from SDAP 225 can be an SDU (e.g., PDCP SDU) of the lower protocol layer PDCP 224, and can also be a PDU (e.g., SDAP PDU) of SDAP 225.

[0072] Each protocol layer (e.g., Figure 4A The protocol layers shown) or at least some of the protocol layers can: perform their own functions (e.g., regarding...) Figure 3 Each protocol layer may include one or more functions, add corresponding headers, and / or forward the corresponding output to the next lower layer (e.g., its corresponding lower layer). PDCP 224 may perform IP header compression and / or encryption. PDCP 224 may forward its output (e.g., PDCP PDU, which is an RLC SDU) to RLC 223. RLC 223 may optionally perform fragmentation (e.g., as described above). Figure 4A (As shown in IP packet m). RLC 223 can forward its output (e.g., two RLCPDUs, which are two MAC SDUs generated by adding appropriate subheaders to two SDU segments) to MAC 222. MAC 222 can multiplex a certain number of RLC PDUs (MAC SDUs). MAC 222 can attach MAC subheaders to RLC PDUs (MAC SDUs) to form a TB. MAC subheaders can be distributed on MAC PDUs (e.g., in...). Figure 4A(As shown in the NR configuration). The MAC sub-header can be located entirely at the beginning of the MAC PDU (e.g., in the LTE configuration). For example, if the MAC PDU sub-header is calculated before assembling the complete MAC PDU, the NR MAC PDU structure can reduce processing time and / or associated latency.

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

[0074] One or more MAC control elements (CEs) can be added to or inserted into a MAC PDU through a MAC layer (such as MAC 223 or MAC 222). Figure 4B As shown, two MAC CEs can be inserted / added before two MAC PDUs. MAC CEs can also be inserted / added at the beginning of a MAC PDU for downlink transmission (e.g., ...). Figure 4B (As shown). One or more MAC CEs can be inserted / added to the end of the MAC PDU for uplink transmission. MAC CEs can be used for in-band control signaling. Exemplary MAC CEs may include scheduling-related MAC CEs, such as buffer status reports and power headroom reports; activation / deactivation MAC CEs (e.g., activation / deactivation for PDCP replication detection, channel state information (CSI) reports, sounding reference signal (SRS) transmissions, and MAC CEs for previously configured components); discontinuous reception (DRX)-related MAC CEs; timing advance MAC CEs; and random access-related MAC CEs. MAC CEs may be preceded by a MAC subheader with a format similar to that described for the MAC subheader of the MAC SDU, and may be identified by a reserved value in the LCID field indicating the type of control information contained in the corresponding MAC CE.

[0075] Figure 5A An exemplary mapping of downlink channels is shown. Uplink channel mapping may include mappings between downlink channels (e.g., logical channels, transport channels, and physical channels). Figure 5BAn exemplary mapping of uplink channels is shown. Uplink channel mapping can include mappings between uplink channels (e.g., logical channels, transport channels, and physical channels). Information can be transmitted via / through channels between the RLC, MAC, and PHY layers of a protocol stack (e.g., the NR protocol stack). Logical channels can be used between the RLC and MAC layers. Logical channels can be classified / indicated as control channels that can carry control and / or configuration information (e.g., in the NR control plane) or traffic channels that can carry data (e.g., in the NR user plane). Logical channels can be classified / indicated as dedicated logical channels that can be used exclusively by a particular wireless device, and / or shared logical channels that can be used by more than one wireless device (e.g., a group of wireless devices).

[0076] Logical channels can be defined by the type of information they carry. This group of logical channels (e.g., in an NR configuration) may include one or more channels as described below. The Paging Control Channel (PCCH) may include / carry one or more paging messages for paging a radio device whose location is unknown to the network at the cell level. The Broadcast Control Channel (BCCH) may include / carry system information messages in the form of a Master Information Block (MIB) and several System Information Blocks (SIBs). Radio devices can use system information messages to obtain information about how the cell is configured and how to operate within the cell. The Common Control Channel (CCCH) may include / carry control messages along with random access. The Dedicated Control Channel (DCCH) may include / carry control messages destined for / from a specific radio device to configure the radio device with configuration information. The Dedicated Traffic Channel (DTCH) may include / carry user data destined for / from a specific radio device.

[0077] Transport channels can be used between the MAC and PHY layers. Transport channels can be defined according to how the information they carry is sent / transmitted (e.g., via the air interface). This set of transport channels (e.g., defined by NR configuration or any other configuration) can include one or more of the following channels: Paging channel (PCH) can include / carry paging messages originating from the PCCH. Broadcast channel (BCH) can include / carry MIBs from the BCCH. Downlink shared channel (DL-SCH) can include / carry downlink data and signaling messages, including SIBs from the BCCH. Uplink shared channel (UL-SCH) can include / carry uplink data and signaling messages. Random access channel (RACH) can provide access to the network for radio devices without any prior scheduling.

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

[0079] The physical layer can generate physical signals to support lower-level physical layer operations, which can resemble physical control channels. For example... Figure 5A and Figure 5B As shown, physical layer signals (e.g., which may be defined by NR configuration or any other configuration) may include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DM-RS), a sounding reference signal (SRS), a phase tracking reference signal (PT RS), and / or any other signal.

[0080] One or more of these channels (e.g., logical channels, transport channels, physical channels, etc.) can be used to perform functions associated with the control plan protocol stack (e.g., the NR control plane protocol stack). Figure 2B An exemplary control plane configuration (e.g., the NR control plane protocol stack) is shown. Figure 2BAs shown, a control plane configuration (e.g., an NR control plane protocol stack) can use one or more substantially the same / similar protocol layers (e.g., PHY 211 and 221, MAC 212 and 222, RLC 213 and 223, and PDCP 214 and 224) as an example user plane configuration (e.g., an NR user plane protocol stack). The four similar protocol layers may include PHY 211 and 221, MAC 212 and 222, RLC 213 and 223, and PDCP 214 and 224. A control plane configuration (e.g., an NR control plane stack) may have Radio Resource Control (RRC) 216 and 226 and NAS protocols 217 and 237 on top of the control plane configuration (e.g., an NR control plane protocol stack), for example, instead of having SDAP 215 and 225. A control plane configuration may include an AMF 230, which includes NAS protocol 237.

[0081] NAS protocols 217 and 237 can provide control plane functionality between wireless device 210 and AMF 230 (e.g., AMF 158A or any other AMF) and / or more generally, between wireless device 210 and CN (e.g., CN 152 or any other CN). NAS protocols 217 and 237 can provide control plane functionality between wireless device 210 and AMF 230 via signaling messages referred to as NAS messages. There may not be a direct path for NAS messages to be transmitted between wireless device 210 and AMF 230. NAS messages can be transmitted using AS interfaces of Uu and NG. NAS protocols 217 and 237 can provide control plane functions such as authentication, security, connection settings, mobility management, session management, and / or any other functions.

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

[0083] Figure 6 Exemplary RRC states and RRC state transitions are illustrated. The RRC state of a wireless device can change to another RRC state (e.g., an RRC state transition of the wireless device). The wireless device can be substantially the same as or similar to wireless devices 106, 210, or any other wireless device. The wireless device can be in at least one of a plurality of states, such as three RRC states, including RRC connected 602 (e.g., RRC_CONNECTED), RRC idle 606 (e.g., RRC_IDLE), and RRC inactive state 604 (e.g., RRC_INACTIVE). RRC inactive state 604 can be an RRC that is connected but inactive.

[0084] An RRC connection can be established for a wireless device. For example, this might occur during an RRC connection state. During an RRC connection state (e.g., during RRC connection 602), the wireless device may have an established RRC context and may have at least one RRC connection with a base station. The base station may resemble one of these base stations (e.g., Figure 1A One or more base stations of RAN 104 shown Figure 1BOne of gNB 160 or ng eNB 162 shown. Figure 2A and Figure 2B (Base station 220 shown or any other base station). A base station connected to a radio device (e.g., with an established RRC connection) may have the radio device's RRC context. The RRC context may be referred to as the radio device context (e.g., UE context) and may include parameters for communication between the radio device and the base station. These parameters may include one or more of the following: AS context; radio link configuration parameters; bearer configuration information (e.g., related to data radio bearers, signaling radio bearers, logical channels, QoS flows, and / or PDU sessions); security information; and / or layer configuration information (e.g., PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information). During RRC connection states (e.g., RRC connection 602), the mobility of the radio device may be managed / controlled by the RAN (e.g., RAN 104 or NG RAN 154). The radio device may measure the received signal level (e.g., reference signal level, reference signal received power, reference signal received quality, received signal strength indicator, etc.) based on one or more signals transmitted from the serving cell and neighboring cells. The wireless device can report these measurements to the serving base station (e.g., the base station currently serving the wireless device). The serving base station of the wireless device can, for example, request a handover to a cell of a neighboring base station based on the reported measurements. The RRC state can be transitioned from an RRC connected state (e.g., RRC connected 602) to an RRC idle state (e.g., RRC idle 606) via a connection release procedure 608. The RRC state can be transitioned from an RRC connected state (e.g., RRC connected 602) to an RRC inactive state (e.g., RRC inactive state 604) via a connection deactivation procedure 610.

[0085] An RRC context may not be established for the radio device. For example, this could occur during an RRC idle state. During an RRC idle state (e.g., RRC Idle 606), an RRC context may not be established for the radio device. During an RRC idle state (e.g., RRC Idle 606), the radio device may not have an RRC connection with the base station. During an RRC idle state (e.g., RRC Idle 606), the radio device may be in a sleep state most of the time (e.g., to conserve battery power). The radio device may periodically wake up (e.g., once in each Discontinuous Receive (DRX) cycle) to monitor paging messages (e.g., paging messages set from the RAN). The mobility of the radio device can be managed by the radio device via a cell reselection procedure. The RRC state can 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.

[0086] Previously established RRC contexts can be maintained for radio devices. For example, this might occur during RRC inactivity. During RRC inactivity (e.g., RRC inactivity 604), previously established RRC contexts can be maintained in both the radio device and the base station. Compared to the transition from an RRC idle state (e.g., RRC idle 606) to an RRC connected state (e.g., RRC connected 602), maintaining the RRC context allows for / permits a rapid transition to the RRC connected state (e.g., RRC connected 602) with reduced signaling overhead. During RRC inactivity (e.g., RRC inactivity 604), the radio device can be in a sleep state, and its mobility can be managed / controlled by the radio device via cell reselection. The RRC state can transition from the RRC inactivity state (e.g., RRC inactivity 604) to the RRC connected state (e.g., RRC connected 602) via a connection recovery procedure 614. The RRC state can be transitioned from an RRC inactive state (e.g., RRC inactive state 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.

[0087] 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 State 604), mobility can be managed / controlled by the radio device 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 State 604) can be to enable / permit the network to notify the radio device of events via paging messages without broadcasting paging messages across the mobile network. Mobility management mechanisms used during RRC idle states (e.g., RRC Idle 606) or RRC idle states (e.g., RRC Inactive State 604) can enable / permit the network to track the radio device, for example, at the cell group level, such that paging messages can be broadcast on the cells of the cell group where the radio device currently resides (e.g., instead of sending paging messages across the mobile network). Mobility management mechanisms for RRC idle states (e.g., RRC idle 606) and RRC inactive states (e.g., RRC inactive state 604) can track radio devices at the cell group level. This mobility management mechanism can, for example, use different packet granularities for tracking. Multiple levels of cell packet granularity can exist (e.g., three levels of cell packet granularity: a single cell; cells within a RAN area identified by a RAN Area Identifier (RAI); and a group of cells within a RAN area referred to as the tracking area and identified by a Tracking Area Identifier (TAI)).

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

[0089] RAN areas can be used to track radio devices (e.g., the location of radio devices at the RAN level). For radio devices in an RRC inactive state (e.g., RRC inactive state 604), RAN notification areas can be assigned / provided / configured to the radio device. A RAN notification area can include one or more cell identities (e.g., a RAI list and / or a TAI list). A base station can belong to one or more RAN notification areas. A cell can belong to one or more RAN notification areas. A radio device can perform notification area updates with the RAN to update its RAN notification area, for example, if the radio device moves (e.g., via cell reselection) to a cell not included in the RAN notification area assigned / provided / configured to the radio device.

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

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

[0092] Physical signals and physical channels (e.g., regarding Figure 5A and Figure 5BThe data can be mapped onto one or more symbols (e.g., orthogonal frequency division multiplexing (OFDM) symbols in an NR configuration or any other symbol). OFDM is a multicarrier communication scheme that transmits / transmits data over F orthogonal subcarriers (or carriers). The data can be mapped onto a series of complex symbols called source symbols (e.g., M-QAM symbols, M-PSK symbols, or any other modulated symbols), and is divided into F parallel symbol streams, for example, before data transmission. 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 transforms them into the time domain. The IFFT block can receive F source symbols at a time, one source symbol from each of the F parallel symbol streams. The IFFT block can use each source symbol to modulate the amplitude and phase of one of the F sinusoidal basis functions corresponding to the F orthogonal subcarriers. The output of the IFFT block can be F time-domain samples representing the sum of the F orthogonal subcarriers. The F time-domain samples can form a single OFDM symbol. OFDM symbols provided / output by the IFFT block can be transmitted / transmitted over the air interface at the carrier frequency, for example, after one or more processes (e.g., adding a cyclic prefix) and upsampling. For example, before processing by the IFFT block, a Fast Fourier Transform (FFT) block can be used to mix F parallel symbol streams. This operation can produce Discrete Fourier Transform (DFT) precoded OFDM symbols, which can be used by one or more radio devices in the uplink to reduce the peak-to-average power ratio (PAPR). Inverse processing of the OFDM symbols can be performed at the receiver using the FFT block to recover the data mapped to the source symbols.

[0093] Figure 7 An exemplary configuration of a frame is shown. The frame may include, for example, an NR radio frame, into which OFDM symbols can be grouped. The frame (e.g., an NR radio frame) can be identified / indicated by the System Frame Number (SFN) or any other value. The SFN can repeat in a period of 1024 frames. The duration of an NR frame can be 10 milliseconds (ms) and can include 10 subframes with a duration of 1 ms. Subframes can be divided into one or more time slots (e.g., depending on the parameter set and / or different subcarrier spacing). Each of these one or more time slots can include, for example, 14 OFDM symbols per slot. Any number of symbols, time slots, or duration can be used for any time interval.

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

[0095] A time slot can have a fixed number of OFDM symbols (e.g., 14 OFDM symbols). A parameter set with a higher subcarrier spacing can have a shorter time slot duration and more time slots per subframe. Figure 7 The example shown is an example of the time slot duration and per-subframe time slot transmission structure associated with the parameter set. Figure 7 (A parameter set with a 240 kHz subcarrier spacing is not shown in the diagram). Subframes (e.g., in an NR configuration) can be used as parameter set-independent time references. Time slots can be used as units for scheduling uplink and downlink transmissions. Scheduling (e.g., in an NR configuration) can be decoupled from the time slot duration. Scheduling can begin at any OFDM symbol. Scheduling can last as many symbols as required for transmission, for example, to support low latency. These partial time slot transmissions can be referred to as micro-time slot or sub-time slot transmissions.

[0096] Figure 8 An exemplary resource configuration for one or more carriers is shown. The resource configuration may include time slots in the time and frequency domains for NR carriers or any other carriers. These time slots may include resource elements (REs) and resource blocks (RBs). A resource element (RE) may be a minimum physical resource (e.g., in an NR configuration). An RE may span an OFDM symbol in the time domain via a subcarrier in the frequency domain, such as... Figure 8 As shown. RB can span twelve consecutive REs in the frequency domain, such as... Figure 8As shown. A carrier (e.g., an NR carrier) can be limited to a certain number of RBs and / or the width of subcarriers (e.g., 275 RBs or 275 × 12 = 3300 subcarriers). If this limitation is used, the carrier (e.g., an NR carrier) frequency can be limited based on the subcarrier spacing (e.g., for subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, and 120 kHz, the carrier frequencies are 50 MHz, 100 MHz, 200 MHz, and 400 MHz, respectively). A 400 MHz bandwidth can be set based on a 400 MHz bandwidth limit per carrier. Any other bandwidth can be set based on a per-carrier bandwidth limit.

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

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

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

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

[0101] A base station can configure one or more resource sets for a radio device to transmit one or more PUCCHs, for example, for an uplink BWP in a set of configured uplink BWPs. The radio device can receive downlink receptions (e.g., PDCCH or PDSCH) in a downlink BWP, for example, based on a configured set of parameters for the downlink BWP (e.g., configured subcarrier spacing and / or configured cyclic prefix duration). The radio device can transmit uplink transmissions (e.g., PUCCH or PUSCH) in an uplink BWP, for example, based on a configured set of parameters (e.g., configured subcarrier spacing and / or configured cyclic prefix length for the uplink BWP).

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

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

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

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

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

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

[0108] The radio device procedure for switching BWPs on a secondary cell can be the same as / similar to that on the primary cell, for example, if the radio device is configured for a secondary cell with a default downlink BWP and timer values ​​from a set of configured downlink BWPs. The radio device can use the timer values ​​and default downlink BWP for the secondary cell in the same / similar manner as the radio device uses the timer values ​​and / or default BWP for the primary cell. Timer values ​​(e.g., BWP inactivity timers) can be configured, for example, via RRC signaling or any other signaling, for each cell (e.g., for one or more BWPs). One or more active BWPs can switch to another BWP, for example, based on the expiration of the BWP inactivity timer.

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

[0110] Figure 10A An exemplary CA configuration based on CC is shown. For example... Figure 10A As shown, the three types of CA configurations can include an in-band (contiguous) configuration 1002, an in-band (non-contiguous) configuration 1004, and / or an inter-band configuration 1006. In an in-band (contiguous) configuration 1002, two CCs can be aggregated in the same frequency band (band A) and can be directly adjacent to each other within the band. In an in-band (non-contiguous) configuration 1004, two CCs can be aggregated in the same frequency band (band A), but can be spaced apart from each other within the band. In an inter-band configuration 1006, two CCs can be located in different frequency bands (e.g., band A and band B, respectively).

[0111] The network can be configured to aggregate a maximum number of CCs (e.g., up to 32 CCs in NR, or any other number in other systems). Aggregated CCs can have the same or different bandwidths, subcarrier spacing, and / or duplex schemes (TDD, FDD, or any other duplex scheme). The serving cell for a radio device using CA can have downlink CCs. One or more uplink CCs can optionally be configured for the serving cell (e.g., for FDD). The ability to aggregate more downlink carriers than uplink carriers can be useful, for example, if the radio device has more data traffic in the downlink than in the uplink.

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

[0113] For example, SCells configured for wireless devices can be activated or deactivated based on service and channel conditions. Deactivation of a SCell can cause the wireless device to stop receiving PDCCH and PDSCH on the SCell, as well as transmitting PUSCH, SRS, and CQI on the SCell. For example, this can be achieved using MAC CE (e.g., regarding...). Figure 4B The MAC CE activates or deactivates configured SCells. The MAC CE can use a bitmap (e.g., one bit per SCell) to indicate which SCells (e.g., in a subset of configured SCells) are activated or deactivated for the wireless device. For example, a configured SCell can be deactivated based on the expiration (e.g., after or in response to) of a SCell deactivation timer (e.g., configurable one SCell deactivation timer per SCell).

[0114] DCI (Distributed Control Information) can include control information for the cell, such as scheduling assignment and scheduling grant. DCI can be transmitted / transmitted via the cell corresponding to the scheduling assignment and / or scheduling grant; this can be referred to as self-scheduling. DCI including control information for the cell can be transmitted / transmitted via another cell; this can be referred to as cross-carrier scheduling. Uplink Control Information (UCI) can include control information such as HARQ acknowledgments and channel state feedback (e.g., CQI, PMI, and / or RI) for the aggregated cell. UCI can be transmitted / transmitted via the uplink control channel (e.g., PUCCH) of the PCell or a SCell (e.g., a SCell configured with PUCCH). For a large number of aggregated downlink CCs, the PUCCH of the PCell may become overloaded. Cells can be divided into multiple PUCCH groups.

[0115] Figure 10B An exemplary cell group is shown. Aggregated cells can be configured into one or more PUCCH groups (e.g., such as...). Figure 10B(As shown). One or more cell groups or one or more uplink control channel groups (e.g., PUCCH group 1010 and PUCCH group 1050) may each include one or more downlink CCs. PUCCH group 1010 may include one or more downlink CCs, for example, three downlink CCs: PCell 1011 (e.g., DL PCC), SCell 1012 (e.g., DL SCC), and SCell 1013 (e.g., DL SCC). PUCCH group 1050 may include one or more downlink CCs, for example, three downlink CCs: PUCCH SCell (or PSCell) 1051 (e.g., DL SCC), SCell 1052 (e.g., DL SCC), and SCell 1053 (e.g., DL SCC). One or more uplink CCs of PUCCH group 1010 may be configured as PCell 1021 (e.g., UL PCC), SCell 1022 (e.g., UL SCC), and SCell 1023 (e.g., UL SCC). One or more uplink CCs of PUCCH group 1050 can be configured as PUCCH SCell (or PSCell) 1061 (e.g., UL SCC), SCell 1062 (e.g., UL SCC), and SCell 1063 (e.g., UL SCC). UCIs associated with the downlink CCs of PUCCH group 1010 can be transmitted / transmitted via the uplink of PCell 1021 (e.g., via the PUCCH of PCell 1021), shown as UCI 1031, UCI 1032, and UCI 1033. UCIs associated with the downlink CCs of PUCCH group 1050 can be transmitted / transmitted via the uplink of PUCCH SCell (or PSCell) 1061 (e.g., via the PUCCH of PUCCH SCell 1061), shown as UCI 1071, UCI 1072, and UCI 1073. For example, if Figure 10B If the aggregated cell shown is not divided into PUCCH group 1010 and PUCCH group 1050, a single uplink PCell can be configured to send / transmit UCIs associated with six downlink CCs. For example, if UCIs 1031, 1032, 1033, 1071, 1072, and 1073 are sent / transmitted via PCell 1021, PCell 1021 may become overloaded. By partitioning the transmission of UCIs between PCell 1021 and PUCCH SCell (or PSCell) 1061, overload can be prevented and / or reduced.

[0116] A PCell may include a downlink carrier (e.g., PCell 1011) and an uplink carrier (e.g., PCell 1021). An SCell may include only a downlink carrier. A physical cell ID and a cell index may be assigned to a cell that includes a downlink carrier and optionally an uplink carrier. The physical cell ID or cell index may indicate / identify the downlink carrier and / or uplink carrier of the cell, for example, depending on the context in which the physical cell ID is used. For example, the physical cell ID may be determined using synchronization signals (e.g., PSS and / or SSS) transmitted / transmitted via downlink component carriers. The cell index may be determined, for example, using one or more RRC messages. The physical cell ID may be referred to as a carrier ID, and the cell index may be referred to as a carrier index. The first physical cell ID for the first downlink carrier may refer to the first physical cell ID of the cell that includes the first downlink carrier. Essentially the same / similar concepts may be applied, for example, carrier activation. The activation of the first carrier may refer to the activation of the cell that includes the first carrier.

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

[0118] For the downlink, the base station may send / transmit (e.g., unicast, multicast, and / or broadcast) one or more reference signals (RS) (e.g., PSS, SSS, CSI-RS, DM-RS, and / or PT-RS) to one or more radio devices. For the uplink, the one or more radio devices may send / transmit one or more RS (e.g., DM-RS, PT-RS, and / or SRS) to the base station. PSS and SSS may be sent / transmitted by the base station and used by the one or more radio devices to synchronize the one or more radio devices with the base station. Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) blocks may include PSS, SSS, and PBCH. The base station may periodically send / transmit bursts of SS / PBCH blocks, which may be referred to as SSBs.

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

[0120] SS / PBCH blocks can span one or more OFDM symbols in the time domain (e.g., 4 OFDM symbols, such as...). Figure 11A The PSS, SSS, and PBCH can have a common center frequency. The PSS can be transmitted first and can span, for example, one OFDM symbol and 127 subcarriers. The SSS can be transmitted after the PSS (e.g., two symbols later) and can span one OFDM symbol and 127 subcarriers. The PBCH can be transmitted after the PSS (e.g., across the next three OFDM symbols) and can span 240 subcarriers (e.g., in the frequency domain). Figure 11A (as shown in the second and fourth OFDM symbols) and / or may span fewer than 240 subcarriers (e.g., in such cases) Figure 11A (In the third OFDM symbol shown).

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

[0122] A radio device can use SS / PBCH blocks to determine one or more parameters of a cell. The radio device can determine the cell's Physical Cell Identifier (PCI) based, for example, on the sequences of PSS and SSS. The radio device can determine the location of the cell's frame boundary based, for example, on the location of the SS / PBCH block. The SS / PBCH block can indicate that it has been transmitted / transmitted according to a transmission mode. The SS / PBCH block in the transmission mode can be at a known distance from the frame boundary (e.g., a predefined distance in the RAN configuration between one or more networks, one or more base stations, and one or more radio devices).

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

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

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

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

[0127] A base station can semi-statically configure one or more CSI-RS resource sets for a wireless device. CSI-RS resources can be associated with location and periodicity in the time and frequency domains. The base station can selectively activate and / or deactivate CSI-RS resources. The base station can instruct the wireless device that CSI-RS resources in the CSI-RS resource set be activated and / or deactivated.

[0128] The base station can configure the wireless device to report CSI measurement results. The base station can configure the wireless device to provide CSI reports periodically, non-periodically, or semi-persistently. For periodic CSI reporting, the wireless device can be configured with multiple CSI reports at specific times and / or periodically. For non-periodic CSI reporting, the base station can request CSI reports. The base station can command the wireless device to measure configured CSI-RS resources and provide CSI reports related to the measurement results. For semi-persistent CSI reporting, the base station can configure the wireless device to periodically send / transmit and selectively activate or deactivate periodic reports (e.g., via one or more activation / deactivation MAC CEs and / or one or more DCIs). The base station can, for example, use RRC signaling to configure the CSI-RS resource set and CSI reports for the wireless device.

[0129] CSI-RS configuration may include one or more parameters indicating, for example, up to 32 antenna ports (or any other number of antenna ports). For example, if the downlink CSI-RS and CORESET are in a spatially QCL and the resource element associated with the downlink CSI-RS is outside the Physical Resource Block (PRB) configured for the CORESET, the radio device can be configured to use / adopt the same OFDM symbols for both the downlink CSI-RS and CORESET. Similarly, if the downlink CSI-RS and SS / PBCH block are in a spatially QCL and the resource element associated with the downlink CSI-RS is outside the PRB configured for the SS / PBCH block, the radio device can be configured to use / adopt the same OFDM symbols for both the downlink CSI-RS and SS / PBCH block.

[0130] Downlink DM-RS can be transmitted / transmitted by the base station and received / used by the radio device for channel estimation. Downlink DM-RS can be used for coherent demodulation of one or more downlink physical channels (e.g., PDSCH). The network (e.g., NR network) can support one or more variable and / or configurable DM-RS modes for data demodulation. At least one downlink DM-RS configuration can support a preloaded DM-RS mode. Preloaded DM-RS can be mapped to one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). The base station can semi-statically configure a certain number (e.g., maximum number) of preloaded DM-RS symbols for the radio device to use for PDSCH. A DM-RS configuration can support one or more DM-RS ports. A DM-RS configuration can support up to eight orthogonal downlink DM-RS ports per radio device (e.g., for single-user MIMO). A DM-RS configuration can support up to four orthogonal downlink DM-RS ports per radio device (e.g., for multi-user MIMO). The radio network can support (e.g., at least for CP-OFDM) a common DM-RS structure for both downlink and uplink. The DM-RS location, DM-RS mode, and / or scrambling sequence can be the same or different. The base station can, for example, use the same precoding matrix to transmit / transmit the downlink DM-RS and the corresponding PDSCH. The radio device can use this one or more downlink DM-RS for coherent demodulation / channel estimation of the PDSCH.

[0131] A transmitter (e.g., a transmitter at a base station) 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. For example, the first and second precoder matrices may differ based on the difference between the first and second bandwidths. A wireless device may assume the same precoding matrix is ​​used across a set of PRBs. This set of PRBs can be identified / indicated / identified / represented as a Precoded Resource Block Group (PRG).

[0132] A PDSCH may include one or more layers. A radio device may assume that at least one symbol with a DM-RS exists on one of these layers of the PDSCH. Higher layers may configure one or more DM-RS for the PDSCH (e.g., up to three DMRSs for the PDSCH). Downlink PT-RS may be transmitted / transmitted by the base station and used by the radio device, for example, for phase noise compensation. The presence of downlink PT-RS may depend on the RRC configuration. The presence and / or mode of downlink PT-RS can be configured on a radio device-specific basis, for example, using a combination of RRC signaling and / or associating it with one or more parameters for other purposes (e.g., modulation and coding scheme (MCS)), which may be indicated by the DCI. The dynamic presence of downlink PT-RS (if configured) may be associated with one or more DCI parameters that include at least an MCS. The network (e.g., an NR network) may support multiple PT-RS densities defined in the time and / or frequency domains. Frequency domain density (if configured / existing) may be associated with at least one configuration of the scheduling bandwidth. The radio device may assume the same precoding for both DM-RS and PT-RS ports. The number of PT-RS ports can be less than the number of DM-RS ports in the scheduling resources. Downlink PT-RS can be configured / assigned / limited within the scheduling time / frequency duration of the wireless device. Downlink PT-RS can be transmitted via symbols, for example, to facilitate phase tracking at the receiver.

[0133] For example, a wireless device can send / transmit uplink DM-RS to a base station for channel estimation. The base station can use the uplink DM-RS for coherent demodulation of one or more uplink physical channels. The wireless device can utilize PUSCH and / or PUCCH to send / transmit uplink DM-RS. The uplink DM-RS can span a frequency range similar to the frequency range associated with the corresponding physical channel. The base station can configure one or more uplink DM-RS configurations for the wireless device. At least one DM-RS configuration can support preloaded DM-RS mode. Preloaded DM-RS can be mapped to one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DM-RS can be configured to be sent / transmitted at one or more symbols of PUSCH and / or PUCCH. The base station can semi-statically configure a certain number (e.g., a maximum number) of preloaded DM-RS symbols for PUSCH and / or PUCCH, which the wireless device can use to schedule single-symbol DM-RS and / or dual-symbol DM-RS. The network (e.g., an NR network) can support (e.g., for Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM)) a common DM-RS structure for both downlink and uplink. The DM-RS location, DM-RS mode, and / or scrambling sequence of the DM-RS can be substantially the same or different.

[0134] The PUSCH may include one or more layers. A radio device may transmit / transmit at least one symbol where a DM-RS exists on one of these layers of the PUSCH. Higher layers may configure one or more DM-RSs (e.g., up to three DMRSs) for the PUSCH. For example, depending on the radio device's RRC configuration, an uplink PT-RS (which may be used by the base station for phase tracking and / or phase noise compensation) may or may not exist. The presence and / or mode of the uplink PT-RS may be configured on a radio device-specific basis (e.g., a UE-specific basis), such as through RRC signaling and / or a combination of one or more parameters configured / used for other purposes (e.g., MCS), which may be indicated by the DCI. If configured, the dynamic presence of the uplink PT-RS may be associated with one or more DCI parameters including at least one MCS. The radio network may support multiple uplink PT-RS densities defined in the time / frequency domain. Frequency domain density (if configured / existing) may be associated with at least one configuration of the scheduling bandwidth. The radio device may assume the same precoding for both DM-RS ports and PT-RS ports. The number of PT-RS ports can be less than the number of DM-RS ports in the scheduling resources. Uplink PT-RS can be configured / assigned / limited to the scheduling time / frequency duration of the wireless device.

[0135] One or more SRSs can be transmitted / transmitted by a radio device to a base station, for example, for channel state estimation to support uplink channel-dependent scheduling and / or link adaptation. The SRS transmitted / transmitted by the radio device enables / allows the base station to estimate uplink channel states at one or more frequencies. The scheduler at the base station can use / adopt the estimated uplink channel states to assign one or more resource blocks for uplink PUSCH transmissions by the radio device. The base station can semi-statically configure one or more SRS resource sets for the radio device. For each SRS resource set, the base station can configure one or more SRS resources for the radio device. The suitability of the SRS resource set can be configured, for example, by higher-layer (e.g., RRC) parameters. SRS resources in the one or more SRS resource sets (e.g., having the same / similar time-domain behavior, periodicity, aperiodicity, etc.) can be transmitted / transmitted at some point (e.g., simultaneously), for example, if higher-layer parameters instruct beam management. The radio device can transmit / transmit one or more SRS resources in the SRS resource set. The network (e.g., an NR network) can support aperiodic, periodic, and / or semi-persistent SRS transmissions. A wireless device may transmit / transmit SRS resources, for example, based on one or more trigger types. These one or more trigger types may include higher-layer signaling (e.g., RRC) and / or one or more DCI formats. The wireless device may use / emulate at least one DCI format to select at least one of one or more configured SRS resource sets. SRS trigger type 0 may refer to SRS triggered based on higher-layer signaling. SRS trigger type 1 may refer to SRS triggered based on one or more DCI formats. If PUSCH and SRS are transmitted / transmitted in the same time slot, the wireless device may be configured to transmit / transmit SRS, for example, after the transmission of PUSCH and the corresponding uplink DM-RS. The base station can semi-statically configure one or more SRS configuration parameters for the wireless device, the configuration parameters indicating at least one of the following: SRS resource configuration identifier; number of SRS ports; temporal behavior of SRS resource configuration (e.g., indication of periodic semi-persistent or aperiodic SRS); time slot, micro-time slot and / or subframe level periodicity; offset of periodic and / or aperiodic SRS resources; number of OFDM symbols in SRS resources; starting OFDM symbol of SRS resources; SRS bandwidth; frequency hopping bandwidth; cyclic shift; and / or SRS sequence ID.

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

[0137] Channels using beamforming may require beam management. Beam management can include beam measurement, beam selection, and / or beam indication. A beam can be associated with one or more reference signals. A beam can be identified by one or more beamforming reference signals. A wireless device can perform downlink beam measurements, for example, based on one or more downlink reference signals (e.g., CSI-RS), and generate a beam measurement report. For example, after establishing an RRC connection with a base station, the wireless device can perform a downlink beam measurement procedure.

[0138] Figure 11B An exemplary mapping of one or more CSI-RSs is shown. CSI-RSs can be mapped in the time domain and frequency domain. Figure 11BEach rectangular block shown may correspond to a resource block (RB) within the cell's bandwidth. The base station may send / transmit one or more RRC messages including CSI-RS resource configuration parameters indicating one or more CSI-RS. One or more parameters in the parameters may be configured via higher-layer signaling (e.g., RRC and / or MAC signaling) used for CSI-RS resource configuration. One or more of these parameters may include at least one of the following: CSI-RS resource configuration identity, number of CSI-RS ports, CSI-LS configuration (e.g., symbol and resource element (RE) positions in subframes), CSI-RS subframe configuration (e.g., subframe positions, offsets, and periodicity in radio frames), CSI-RS power parameters, CSI-RS sequence parameters, code division multiplexing (CDM) type parameters, frequency density, transmission comb, quasi-co-address (QCL) parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and / or other radio resource parameters.

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

[0140] CSI-RS (e.g., CSI-RS 1101, 1102, 1103) can be sent / transmitted by a base station and used by a wireless device for one or more measurements. The wireless device can measure the RSRP of the configured CSI-RS resources. The base station can configure a reporting configuration for the wireless device, and the wireless device can report the RSRP measurement results to the network (e.g., via one or more base stations) based on this reporting configuration. The base station can determine one or more Transmission Configuration Indication (TCI) states, including a certain number of reference signals, based on the reported measurement results. The base station can indicate one or more TCI states to the wireless device (e.g., via RRC signaling, MAC CE, and / or DCI). The wireless device can receive downlink transmissions using the Rx beam determined based on the one or more TCI states. The wireless device may or may not have beam-matching capability. If the wireless device has beam-matching capability, it can determine the spatial domain filter of the transmission (Tx) beam, for example, based on the spatial domain filter corresponding to the Rx beam. For example, if the wireless device lacks beamforming capability, it can perform an uplink beam selection procedure to determine the spatial domain filter for the Tx beam. The wireless device can perform the uplink beam selection procedure, for example, based on one or more Sounding Reference Signal (SRS) resources configured for it by the base station. The base station can, for example, select and indicate the uplink beam for the wireless device based on measurements of these one or more SRS resources transmitted / transmitted by the wireless device.

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

[0142] Figure 12AAn example of a downlink beam management procedure is shown. One or more downlink beam management procedures (e.g., downlink beam management procedures P1, P2, and P3) can be executed. Procedure P1 can enable the measurement of the Tx beam of a TRP (or multiple TRPs) (e.g., wireless device measurement) (e.g., to support the selection of one or more base station Tx beams and / or wireless device Rx beams). The base station Tx beam and the wireless device Rx beam are shown as ellipses in the top and bottom rows of P1, respectively. Beamforming (e.g., at the TRP) can include a Tx beam scan for a set of beams (e.g., an elliptical beam scan rotated counterclockwise as indicated by dashed arrows in the top rows of P1 and P2). Beamforming (e.g., at the wireless device) can include an Rx beam scan for a set of beams (e.g., an elliptical beam scan rotated clockwise as indicated by dashed arrows in the bottom rows of P1 and P3). Procedure P2 can be used to enable the measurement of the Tx beam of the TRP (e.g., wireless device measurement) (shown in the top row of P2 as an ellipse rotating counterclockwise as indicated by the dashed arrow). The wireless device and / or base station can perform procedure P2, for example, by using a smaller set of beams than that used in procedure P1, or by using a narrower beam than that used in procedure P1. Procedure P2 can be referred to as beam refinement. The wireless device can perform procedure P3 for Rx beam determination, for example, by using the same Tx beam of the base station and scanning the Rx beam of the wireless device.

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

[0144] A wireless device can, for example, initiate / start / execute a beam fault recovery (BFR) procedure based on the detection of a beam fault. The wireless device can, for example, send / transmit a BFR request (e.g., preamble, UCI, SR, MACCE, etc.) based on initiating a BFR procedure. The wireless device can, for example, detect a beam fault based on determining that the quality of the beam pair link associated with the control channel is unsatisfactory (e.g., a bit error rate higher than a bit error rate threshold, received signal power lower than a received signal power threshold, timer expiration, etc.).

[0145] A wireless device may, for example, use one or more reference signals (RS) comprising one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more DM-RSs to measure the quality of a beamp-link. The quality of the beamp-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 value measured on the RS resources. A base station may indicate the QCL of the RS resources and one or more DM-RSs for a channel (e.g., a control channel, a shared data channel, etc.). For example, if the channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameter, fading, etc.) from transmission to the wireless device via the RS resources are similar to or the same as the channel characteristics from transmission to the wireless device via that channel, then the RS resources and one or more DM-RSs for that channel may be QCLs.

[0146] Networks (e.g., NR networks including gNBs and / or ng-eNBs) and / or radio devices can initiate / start / execute random access procedures. Radio devices in an RRC idle (e.g., RRC_IDLE) and / or RRC inactive (e.g., RRC_INACTIVE) state can initiate / execute random access procedures to request connection settings to the network. Radio devices can initiate / start / execute random access procedures from an RRC connected (e.g., RRC_CONNECTED) state. Radio devices can initiate / start / execute random access procedures to request uplink resources (e.g., for uplink transmission of SR if PUCCH resources are not available) and / or acquire / obtain / determine uplink timing (e.g., if the uplink synchronization state is asynchronous). Radio devices can initiate / start / execute random access procedures to request one or more System Information Blocks (SIBs) (e.g., other System Information Blocks such as SIB2, SIB3, etc.). Radio devices can initiate / start / execute random access procedures in response to beam fault recovery requests. The network can initiate / start / execute random access procedures, for example, for handover and / or for adding setup time alignment for SCells.

[0147] Figure 13AAn exemplary four-step random access procedure is illustrated. The four-step random access procedure may include a four-step contention-based random access procedure. The base station may, for example, send / transmit configuration message 1310 to the radio device before initiating the random access procedure. The four-step random access procedure may include the transmission of four messages, including: a first message (e.g., Msg 1 1311), a second message (e.g., Msg 2 1312), a third message (e.g., Msg 3 1313), and a fourth message (e.g., Msg 4 1314). The first message (e.g., Msg 1 1311) may include a preamble (or random access preamble). The first message (e.g., Msg 1 1311) may be referred to as a preamble. The second message (e.g., Msg 2 1312) may include a random access response (RAR). The second message (e.g., Msg 2 1312) may be referred to as a RAR.

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

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

[0150] The one or more RACH parameters provided / configured / included in configuration message 1310 can be used to determine the uplink transmission power of the first message (e.g., Msg 1 1311) and / or the third message (e.g., Msg 3 1313). The one or more RACH parameters can indicate a reference power (e.g., the receive target power and / or initial power for preamble transmission) for the preamble transmission. One or more power offsets indicated by the one or more RACH parameters may exist. The one or more RACH parameters can indicate: power ramp-up steps; power offset between SSB and CSI-RS; power offset between the transmissions of the first message (e.g., Msg 1 1311) and the third message (e.g., Msg 3 1313); and / or power offset values ​​between preamble groups. The one or more RACH parameters may indicate one or more thresholds, for example, the wireless device may determine at least one reference signal (e.g. SSB and / or CSI-RS) and / or uplink carrier (e.g. normal uplink (NUL) carrier and / or supplementary uplink (SUL) carrier) based on the one or more thresholds.

[0151] The first message (e.g., Msg 1 1311) may include one or more preamble transmissions (e.g., preamble transmission and one or more preamble retransmissions). RRC messages can be used to configure one or more preamble groups (e.g., group A and / or group B). A preamble group may include one or more preambles. The wireless device may determine the preamble group, for example, based on path loss measurements and / or the magnitude of a third message (e.g., Msg 3 1313). The wireless device may measure the RSRP of one or more reference signals (e.g., SSB and / or CSI-RS) and determine at least one reference signal with an RSRP higher than an RSRP threshold (e.g., rsrp-ThresholdSSB and / or rsrp-ThresholdCSI-RS). For example, if the association between the one or more preambles and the at least one reference signal is configured by an RRC message, the wireless device can select at least one preamble associated with the one or more reference signals and / or the selected preamble group.

[0152] For example, the wireless device can determine the preamble based on one or more RACH parameters provided / configured / included in configuration message 1310. The wireless device can determine the preamble, for example, based on path loss measurements, RSRP measurements, and / or the size of a third message (e.g., Msg 3 1313). The one or more RACH parameters can indicate: the preamble format; the maximum number of preamble transmissions; and / or one or more thresholds for determining one or more preamble groups (e.g., group A and group B). The base station can use the one or more RACH parameters to configure an association between one or more preambles and one or more reference signals (e.g., SSB and / or CSI-RS) for the wireless device. For example, if an association is configured, the wireless device can determine the preamble to be included in a first message (e.g., Msg 1 1311) based on the association. The first message (e.g., Msg 1 1311) can be sent / transmitted to the base station via one or more PRACH timings. The wireless device may use one or more reference signals (e.g., SSB and / or CSI-RS) to select the preamble and determine the PRACH timing. One or more RACH parameters (e.g., ra-ssb-OccasionMskIndex and / or ra-OccasionList) may indicate the association between the PRACH timing and the one or more reference signals.

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

[0154] The second message (e.g., Msg 2 1312) (e.g., received by a wireless device) may include a RAR. The second message (e.g., Msg 2 1312) may include multiple RARs corresponding to multiple wireless devices. The second message (e.g., Msg 2 1312) may be received, for example, based on the transmission / transmission of the first message (e.g., Msg 1 1311) (e.g., after or in response to it). The second message (e.g., Msg 2 1312) may be scheduled on the DL-SCH and may be indicated by the PDCCH, for example, using a Random Access Radio Network Temporary Identifier (RA RNTI). The second message (e.g., Msg 2 1312) may indicate that the base station has received the first message (e.g., Msg 1 1311). The second message (e.g., Msg 2 1312) may include a time alignment command (which may be used by the wireless device to adjust the transmission timing of the wireless device), scheduling permission for transmitting the third message (e.g., Msg 3 1313), and / or a temporary cell RNTI (TC-RNTI). For example, after sending / transmitting the first message (e.g., Msg 1 1311) (e.g., a preamble), the wireless device may determine / start a time window (e.g., a ra-ResponseWindow) to monitor the PDCCH for the second message (e.g., Msg 2 1312). The wireless device may determine the start time of the time window, for example, based on the PRACH timing used by the wireless device to send / transmit the first message (e.g., Msg 1 1311) (e.g., a preamble). The radio device may begin one or more symbol start time windows after the last symbol of the first message including the preamble (e.g., Msg 1 1311) (e.g., the symbol in which the first message including the preamble transmission (Msg 1 1311) is completed, or the first PDCCH timing after the end of the preamble transmission). These one or more symbols may be determined based on a set of parameters. The PDCCH may be mapped into a common search space configured by RRC messages (e.g., a Type 1-PDCCH common search space). The radio device may identify / determine the RAR, for example, based on the RNTI. The Radio Network Temporary Identifier (RNTI) may be used based on one or more events that initiate / start a random access procedure. The radio device may use the RA-RNTI, for example, for one or more communications associated with random access or any other purpose. The RA-RNTI may be associated with the PRACH timing in which the radio device transmits / transmits the preamble. The radio device may determine the RA-RNTI, for example, based on at least one of the following: OFDM symbol index; time slot index; frequency domain index; and / or the UL carrier indicator of the PRACH timing. An exemplary RA-RNTI can be determined as follows:

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

[0156] Where s_id can be the index of the first OFDM symbol of the PRACH timing (e.g., 0 ≤ s_id < 14), t_id can be the index of the first slot of the PRACH timing in the system frame (e.g., 0 ≤ t_id < 80), f_id can be the index of the PRACH timing in the frequency domain (e.g., 0 ≤ f_id < 8), and ul_carrier_id can be the UL carrier used for preamble transmission (e.g., 0 for NUL carrier and 1 for SUL carrier).

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

[0158] A fourth message (e.g., Msg 4 1314) can be received, for example, based on the transmission / transmission of a third message (e.g., Msg 3 1313) (e.g., after or in response to it). For example, if a C-RNTI is included in the third message (e.g., Msg 3 1313), the base station can use the C-RNTI to address the radio on the PDCCH (e.g., the base station can send the PDCCH to the radio device). For example, if a unique C RNTI of the radio device is detected on the PDCCH (e.g., the PDCCH is scrambled by the C-RNTI), the random access procedure can be determined to have been successfully completed. For example, if the third message (e.g., Msg 3 1313) includes a TC RNTI (e.g., if the radio device is in an RRC idle (e.g., RRC_IDLE) state or is not otherwise connected to the base station), the fourth message (e.g., Msg 4 1314) can be received using the DL-SCH associated with the TC RNTI. For example, if the MAC PDU is successfully decoded and the MAC PDU includes a radio device contention resolution identity MAC CE that matches or otherwise corresponds to the CCCH SDU sent / transmitted in a third message (e.g., Msg 3 1313), the radio device can determine that the contention resolution was successful and / or the radio device can determine that the random access procedure was successfully completed.

[0159] The radio device can be configured with SUL carriers and / or NUL carriers. Initial access (e.g., random access) can be supported via the uplink carrier. The base station can configure multiple RACH configurations for the radio device (e.g., two separate RACH configurations, including one for the SUL carrier and another for the NUL carrier). For random access in a cell configured with an SUL carrier, the network can indicate which carrier (NUL or SUL) to use. For example, if the measured quality of one or more reference signals (e.g., one or more reference signals associated with the NUL carrier) is below a broadcast threshold, the radio device can determine to use the SUL carrier. Uplink transmissions of random access procedures (e.g., the first message (e.g., Msg 1 1311) and / or the third message (e.g., Msg 3 1313)) can be maintained on or performed via the selected carrier. The radio device can switch the uplink carrier during the random access procedure (e.g., between Msg 1 1311 and Msg 3 1313). The wireless device may determine and / or switch uplink carriers for the first message (e.g., Msg1 1311) and / or the third message (e.g., Msg 3 1313) based, for example, on channel idle assessment (e.g., listen-before-speak).

[0160] Figure 13BA two-step random access procedure is illustrated. This two-step random access procedure may include a two-step contention-free random access procedure. Similar to a four-step contention-based random access procedure, the base station may send / transmit configuration message 1320 to the radio device before initiating the procedure. Configuration message 1320 may be similar to configuration message 1310 in some respects. Figure 13B The procedure shown may include the transmission of two messages: a first message (e.g., Msg 1 1321) and a second message (e.g., Msg 2 1322). The first message (e.g., Msg 1 1321) and the second message (e.g., Msg 2 1322) may be similar to the first message (e.g., Msg 1 1311) and the second message (e.g., Msg 2 1312), respectively. The two-step contention-free random access procedure may not include messages similar to a third message (e.g., Msg 3 1313) and / or a fourth message (e.g., Msg 4 1314).

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

[0162] A radio device can, for example, initiate a time window (e.g., ra-ResponseWindow) based on a transmitted / transmitted preamble (e.g., after or in response to it) to monitor the PDCCH for RAR. The base station can configure one or more beam fault recovery parameters for the radio device, such as separate time windows and / or separate PDCCHs in the search space indicated by an RRC message (e.g., recoverySearchSpaceId). The base station can configure one or more beam fault recovery parameters, for example, associated with a beam fault recovery request. A separate time window for monitoring the PDCCH and / or RAR can be configured to begin after the transmitted / transmitted beam fault recovery request (e.g., the window can begin after any number of symbols and / or time slots after the transmitted / transmitted beam fault recovery request). The radio device can monitor PDCCH transmissions addressed to the cell RNTI (C-RNTI) in the search space. During a two-step (e.g., contention-free) random access procedure, for example, based on sending / transmitting a first message (e.g., Msg 1 1321) and receiving a corresponding second message (e.g., Msg 2 1322) (e.g., after or in response to this), the wireless device can determine that the random access procedure was successful. For example, if a PDCCH transmission is addressed to the corresponding C-RNTI, the wireless device can determine that the random access procedure has been successfully completed. For example, if the wireless device receives a RAR including a preamble identifier corresponding to a preamble sub-preamble sent / transmitted by the wireless device and / or the RAR includes a MAC sub-PDU with the preamble identifier, the wireless device can determine that the random access procedure has been successfully completed. The wireless device can determine the response as an indication of acknowledgment of the SI request.

[0163] Figure 13C An exemplary two-step random access procedure is shown. Similar to... Figure 13A and 13B In the random access procedure shown, the base station may send / transmit configuration message 1330 to the wireless device before initiating the procedure. Configuration message 1330 may be similar in some respects to configuration message 1310 and / or configuration message 1320. Figure 13C The procedure shown may include the transmission of multiple messages (e.g., two messages, including: a first message (e.g., Msg A 1331) and a second message (e.g., Msg B 1332)).

[0164] Msg A 1320 can be sent / transmitted by a wireless device in an uplink transmission. Msg A 1320 may include one or more transmissions of preamble 1341 and / or one or more transmissions of transport block 1342. Transport block 1342 may include content similar to and / or equivalent to the content of a third message (e.g., Msg 3 1313). Figure 13A (As shown in the diagram). Transport block 1342 may include UCIs (e.g., SR, HARQ ACK / NACK, etc.). The wireless device may receive a second message (e.g., Msg B 1332) for example, based on sending / transmitting a first message (e.g., Msg A 1331) (e.g., after or in response to this). The second message (e.g., Msg B 1332) may include the content of the second message (e.g., Msg 2 1312) (e.g., ...). Figure 13A The contents of the second message (e.g., Msg 2 1322) shown in the RAR (e.g., the RAR), are also shown in the RAR. Figure 13B The RAR shown in the image) and / or the fourth message (e.g., Msg 4 1314) (e.g., Figure 13A (as shown in the image) Similar and / or equivalent content.

[0165] Wireless devices can initiate / propose a two-step random access procedure for licensed and / or unlicensed spectrum (e.g., Figure 13C The two-step random access procedure is illustrated in the diagram. A radio device may determine whether to initiate / initiate a two-step random access procedure based on one or more factors. These factors may include at least one of the following: the radio access technology being used (e.g., LTE, NR, etc.); whether the radio device has a valid TA; cell size; the radio device's RRC status; spectrum type (e.g., licensed vs. unlicensed); and / or any other suitable factors.

[0166] The wireless device can determine the radio resources and / or uplink transmission power for preamble 1341 and / or transport block 1342 (e.g., included in the first message (e.g., Msg A 1331)) based on two-step RACH parameters included in configuration message 1330. The RACH parameters can indicate the MCS, time-frequency resources, and / or power control for preamble 1341 and / or transport block 1342. The time-frequency resources for transmitting preamble 1341 (e.g., PRACH) and for transmitting transport block 1342 (e.g., PUSCH) can be multiplexed using FDM, TDM, and / or CDM. The RACH parameters enable the wireless device to determine the receive timing and downlink channel for monitoring and / or receiving the second message (e.g., Msg B 1332).

[0167] 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)). The base station may send / transmit a second message (e.g., MsgB 1332) as a response to the first message (e.g., Msg A 1331). The second message (e.g., Msg B 1332) may include at least one of the following: a preamble identifier; a timing advance command; a power control command; uplink granting (e.g., radio resource allocation and / or MCS); a radio device identifier (e.g., a UE identifier for contention resolution); and / or an RNTI (e.g., a C-RNTI or TC-RNTI). For example, if the preamble identifier in the second message (e.g., Msg B 1332) corresponds to or matches the preamble sent / transmitted by the wireless device and / or the identifier of the wireless device in the second message (e.g., Msg B 1332) corresponds to or matches the identifier of the wireless device in the first message (e.g., Msg A 1331) (e.g., transport block 1342), then the wireless device can determine that the two-step random access procedure was successfully completed.

[0168] The wireless device and the base station can exchange control signaling (e.g., control information). This control signaling may be referred to as 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 sent / transmitted from the base station to the wireless device and / or uplink control signals sent / transmitted from the wireless device to the base station.

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

[0170] For example, a base station can attach one or more Cyclic Redundancy Check (CRC) parity bits to the DCI to facilitate the detection of transmission errors. For instance, if the DCI is intended for use with a wireless device (or a group of wireless devices), the base station can scramble the CRC parity bits using the identifier of the wireless device (or a group of identifiers for wireless devices). Scrambling the CRC parity bits using the identifier can include a modulo-2 addition (or XOR operation) of the identifier value and the CRC parity bits. The identifier can include a 16-bit value of the RNTI.

[0171] DCIs can be used for various purposes. The purpose can be indicated by the type of RNTI used to scramble the CRC parity bits. A DCI with CRC parity bits scrambled with a paging RNTI (P-RNTI) can indicate paging information and / or system information change notifications. A P-RNTI can be predefined as "FFFE" in hexadecimal. A DCI with CRC parity bits scrambled with a system information RNTI (SI-RNTI) can indicate broadcast transmission of system information. A SI-RNTI can be predefined as "FFFF" in hexadecimal. A DCI with CRC parity bits scrambled with a random access RNTI (RA-RNTI) can indicate a random access response (RAR). A DCI with CRC parity bits scrambled with a cell RNTI (C-RNTI) can indicate dynamically scheduled unicast transmissions and / or triggering of PDCCH ordered random access. A DCI with CRC parity bits scrambled with a temporary cell RNTI (TC-RNTI) can indicate contention resolution (e.g., similar to...). Figure 13A The Msg3 in Msg3 1313 shown is an example. Other RNTIs configured by the base station for the radio device may include the Configurable Scheduling RNTI (CS RNTI), Transmission Power Control PUCCH RNTI (TPC PUCCH-RNTI), Transmission Power Control PUSCH RNTI (TPC-PUSCH-RNTI), Transmission Power Control SRS RNTI (TPC-SRS-RNTI), Interruption RNTI (INT-RNTI), Slot Format Indication RNTI (SFI-RNTI), Semi-Persistent CSI RNTI (SP-CSI-RNTI), Modulation and Coding Scheme Cell RNTI (MCS-C RNTI), etc.

[0172] A base station can, for example, transmit / transmit a DCI using one or more DCI formats depending on the purpose and / or content of the DCI. DCI format 0_0 can be used to schedule PUSCH within a cell. DCI format 0_0 can be a fallback DCI format (e.g., with a compact DCI payload). DCI format 0_1 ​​can be used to schedule PUSCH within a cell (e.g., with a larger DCI payload than DCI format 0_0). DCI format 1_0 can be used to schedule PDSCH within a cell. DCI format 1_0 can be a fallback DCI format (e.g., with a compact DCI payload). DCI format 1_1 can be used to schedule PDSCH within a cell (e.g., with a larger DCI payload than DCI format 1_0). DCI format 2_0 can be used to provide a slot format indication to a group of radio devices. DCI format 2_1 can be used to notify / inform a group of radio devices of physical resource blocks and / or OFDM symbols, where the group of radio devices can assume that no transmissions are intended for that group of radio devices. DCI format 2_2 can be used to transmit Transmit Power Control (TPC) commands for PUCCH or PUSCH. DCI format 2_3 can be used to transmit a set of TPC commands for SRS transmission of one or more wireless devices. New DCI formats with new features may be defined in future versions. DCI formats can have different DCI sizes, or they can share the same DCI size.

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

[0174] Figure 14AAn example of a CORESET configuration is shown. A CORESET configuration can be used for a bandwidth portion or any other frequency band. A base station can transmit / transmit DCI via PDCCH on one or more control resource sets (CORESETs). A CORESET can include time-frequency resources that a radio device attempts to decode the DCI using one or more search spaces. The base station can configure the size and location of the CORESET in the time-frequency domain. A first CORESET 1401 and a second CORESET 1402 can appear at the first symbol of a time slot, or can be set / configured at the first symbol of a time slot. A first CORESET 1401 can overlap with a second CORESET 1402 in the frequency domain. A third CORESET 1403 can appear at the third symbol of a time slot, or can be set / configured at the third symbol of a time slot. A fourth CORESET 1404 can appear at the seventh symbol of a time slot, or can be set / configured at the seventh symbol of a time slot. A CORESET can have a different number / quantity of resource blocks in the frequency domain.

[0175] Figure 14B An example of CCE-to-REG mapping is shown. CCE-to-REG mapping for DCI transmission can be performed 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 coordination and / or frequency-selective transmission of the control channel). The base station can perform different or the same CCE-to-REG mapping on different CORESETs. CORESETs can be associated with CCE-to-REG mapping (e.g., via RRC configuration). CORESETs can be configured with antenna port QCL parameters. Antenna port QCL parameters can indicate the QCL information for DM-RS received via the PDCCH of the CORESET.

[0176] The base station can send / transmit one or more RRC messages to the radio device, including configuration parameters for one or more CORESETs and one or more search space sets. These configuration parameters can indicate the association between the search space set and the CORESET. The search space set can include a set of PDCCH candidates formed by CCEs (e.g., at a given aggregation level). These configuration parameters can indicate at least one of the following: the number of PDCCH candidates to be monitored at each aggregation level; the PDCCH monitoring periodicity and PDCCH monitoring mode; one or more DCI formats to be monitored by the radio device; and / or whether the search space set is a common search space set or a radio device-specific search space set (e.g., a UE-specific search space set). A set of CCEs in the common search space set can be predefined and known to the radio device. A set of CCEs in the radio device-specific search space set (e.g., a UE-specific search space set) can be configured, for example, based on the radio device's identity (e.g., C-RNTI).

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

[0178] Uplink control signaling (e.g., UCI) can be sent / transmitted to the base station. This uplink control signaling may include HARQ acknowledgments for received DL-SCH transport blocks. The radio device may send / transmit HARQ acknowledgments, for example, based on the receipt of a DL-SCH transport block (e.g., after or in response to it). Uplink control signaling may include a Channel Quality Indicator (CSI) indicating the channel quality of the physical downlink channel. The radio device may send / transmit the CSI to the base station. Based on the received CSI, the base station may determine transport format parameters (e.g., including multiple antennas and beamforming schemes) for downlink transmission. Uplink control signaling may include a Schedule Request (SR). The radio device may send / transmit an SR indicating that uplink data is available for transmission to the base station. The radio device may send / transmit UCIs (e.g., HARQ acknowledgments, CSI reports, SRs, etc.) via PUCCH or PUSCH. The radio device may use one of several PUCCH formats to send / transmit uplink control signaling via PUCCH.

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

[0180] The base station can, for example, use RRC messages to send / transmit configuration parameters for multiple PUCCH resource sets to the radio device. Multiple PUCCH resource sets (e.g., up to four sets in the NR, or up to any other number of sets in other systems) can be configured on the cell's uplink BWP. A PUCCH resource set can be configured with a PUCCH resource set index, multiple PUCCH resources, and / or a number / quantity (e.g., maximum number / quantity) of UCI information bits, where the PUCCH resources are identified by a PUCCH resource identifier (e.g., pucch-Resourceid). The radio device can use one of the multiple PUCCH resources in the PUCCH resource set to send / transmit the UCI information bits. If multiple PUCCH resource sets are configured, the radio device can, for example, select one resource set from the multiple PUCCH resource sets based on the total bit length of the UCI information bits (e.g., HARQ-ACK, SR, and / or CSI). For example, if the total bit length of the UCI information bits is two bits or less, the radio device can select a first PUCCH resource set with a PUCCH resource set index equal to "0". For example, if the total bit length of the UCI information bits is greater than two bits and less than or equal to the first configuration value, the radio device can select a second PUCCH resource set with a PUCCH resource set index equal to "1". For example, if the total bit length of the UCI information bits is greater than the first configuration value and less than or equal to the second configuration value, the radio device can select a third PUCCH resource set with a PUCCH resource set index equal to "2". For example, if the total bit length of the UCI information bits is greater than the second configuration value and less than or equal to the third value (e.g., 1406, 1706, or any other number of bits), the radio device can select a fourth PUCCH resource set with a PUCCH resource set index equal to "3".

[0181] For example, after determining a PUCCH resource set from multiple PUCCH resource sets, the radio device can determine the PUCCH resources from the PUCCH resource set used for UCI (HARQ-ACK, CSI, and / or SR) transmissions. The radio device can determine the PUCCH resources, for example, based on the PUCCH resource indicator in the DCI (e.g., a DCI with DCI format 1_0 or for 1_1) received on / via the PDCCH. The n-bit (e.g., three-bit) PUCCH resource indicator in the DCI can indicate one of multiple (e.g., eight) PUCCH resources in the PUCCH resource set. The radio device can, for example, use the PUCCH resource indicated by the PUCCH resource indicator in the DCI to transmit / transmit UCI (HARQ-ACK, CSI, and / or SR).

[0182] Figure 15A An exemplary communication between a wireless device and a base station is illustrated. The wireless device 1502 and the base station 1504 may be part of a communication network, such as... Figure 1A The communication network 100 shown in the figure Figure 1B The communication network 150 shown may be any other communication network. The communication network may include more than one wireless device and / or more than one base station, having [equipment / features] with [other features]. Figure 15A The base stations shown are basically the same or similar in configuration.

[0183] Base station 1504 can connect wireless device 1502 to the core network (not shown) via radio communication through air interface (or radio interface) 1506. The communication direction from base station 1504 to wireless device 1502 via air interface 1506 can be referred to as the downlink. The communication direction from wireless device 1502 to base station 1504 via air interface 1506 can be referred to as the uplink. For example, various duplex schemes (e.g., a combination of FDD, TDD, and / or duplex technologies) can be used to separate downlink and uplink transmissions.

[0184] For the downlink, data to be sent from base station 1504 to wireless device 1502 can be provided / transmitted / sent to processing system 1508 of base station 1504. Data can be provided / transmitted / sent to processing system 1508 via, for example, a core network. For the uplink, data to be sent from wireless device 1502 to base station 1504 can be provided / transmitted / sent to processing system 1518 of wireless device 1502. Processing systems 1508 and 1518 can implement Layer 3 and Layer 2 OSI functions to process the data for transmission. Layer 2 may include, for example, regarding... Figure 2A , Figure 2B , Figure 3 and Figure 4A The description includes the SDAP layer, PDCP layer, RLC layer, and MAC layer. Layer 3 may include, for example, information regarding... Figure 2B The RRC layer is described.

[0185] Data to be sent to wireless device 1502 may be provided / transmitted / sent to transmission processing system 1510 of base station 1504, for example, after being processed by processing system 1508. Data to be sent to base station 1504 may be provided / transmitted / sent to transmission processing system 1520 of wireless device 1502, for example, after being processed by processing system 1518. Transmission processing systems 1510 and 1520 may implement Layer 1 OSI functions. Layer 1 may include, for example, regarding... Figure 2A , Figure 2B , Figure 3 and Figure 4AThe PHY layer is described. For transmission processing, the PHY layer can perform operations such as forward error correction coding of the transmission channel, interleaving, rate matching, mapping of the transmission channel to the physical channel, modulation of the physical channel, multiple-input multiple-output (MIMO) or multiple-antenna processing, etc.

[0186] The receiving and processing system 1512 of base station 1504 can receive uplink transmissions from wireless device 1502. The receiving and processing system 1512 of base station 1504 may include one or more TRPs. The receiving and processing system 1522 of wireless device 1502 can receive downlink transmissions from base station 1504. The receiving and processing system 1522 of wireless device 1502 may include one or more antenna panels. Receiving and processing systems 1512 and 1522 can implement Layer 1 OSI functions. Layer 1 may include, for example, information about... Figure 2A , Figure 2B , Figure 3 and Figure 4A The PHY layer is described. For receive processing, the PHY layer can perform tasks such as error detection, forward error correction decoding, deinterleaving, demapping from the transport channel to the physical channel, demodulation of the physical channel, MIMO or multi-antenna processing, etc.

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

[0188] Processing systems 1508 and 1518 may be associated with memories 1514 and 1524, respectively. Memories 1514 and 1524 (e.g., one or more non-transitory computer-readable media) may store computer program instructions or code executable by processing systems 1508 and / or 1518 to perform one or more functions (e.g., one or more functions described herein and other functions of a general-purpose computer, processor, memory, and / or other peripheral devices). Transmission processing system 1510 and / or reception processing system 1512 may be coupled to memory 1514 and / or another memory (e.g., one or more non-transitory computer-readable media) storing computer program instructions or code executable to perform one or more of their respective functions. Transmission processing system 1520 and / or reception processing system 1522 may be coupled to memory 1524 and / or another memory (e.g., one or more non-transitory computer-readable media) storing computer program instructions or code executable to perform one or more of their respective functions.

[0189] Processing system 1508 and / or processing system 1518 may include one or more controllers and / or one or more processors. The one or more controllers and / or one or more processors may include, for example, a general-purpose processor, a digital signal processor (DSP), a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) and / or other programmable logic devices, discrete gate 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 encoding / processing, data processing, power control, input / output processing, and / or any other function that enables wireless device 1502 and / or base station 1504 to operate in a wireless environment.

[0190] Processing system 1508 can be connected to one or more peripheral devices 1516. Processing system 1518 can be connected to one or more peripheral devices 1526. The one or more peripheral devices 1516 and one or more peripheral devices 1526 may include software and / or hardware providing features and / or functions, such as speakers, microphones, keypads, displays, touchpads, power sources, satellite transceivers, universal serial bus (USB) ports, hands-free headsets, FM radio units, media players, internet browsers, electronic control units (e.g., for motor vehicles), and / or one or more sensors (e.g., accelerometers, gyroscopes, temperature sensors, radar sensors, laser sensors, ultrasonic sensors, light sensors, cameras, etc.). Processing system 1508 and / or processing system 1518 can receive input data (e.g., user output data) / provide output data (e.g., user output data) from and / or to one or more peripheral devices 1516 and / or one or more peripheral devices 1526. The processing system 1518 in the wireless device 1502 can receive power from a power source and / or can be configured to distribute power to other components in the wireless device 1502. The power source may include one or more power sources, such as a battery, solar cell, 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 GPS chipset 1527 may be configured, respectively, to determine and provide geographic location information for the wireless device 1502 and the base station 1504.

[0191] Figure 15BExemplary elements of a computing device are shown that can be used to implement any of the various devices described herein, including, for example, base stations 160A, 160B, 162A, 162B, 220 and / or 1504, wireless devices 106, 156A, 156B, 210 and / or 1502, or any other base station, wireless device, AMF, UPF, network device, or computing device described herein. The computing device 1530 may include one or more processors 1531 that can execute instructions stored in random access memory (RAM) 1533, removable media 1534 (such as a Universal Serial Bus (USB) drive, compact disk (CD) or digital universal optical disc (DVD), or floppy disk drive), or any other desired storage medium. Instructions may also be stored in an attached (or internal) hard disk drive 1535. The computing device 1530 may also include a security processor (not shown) that can execute instructions of one or more computer programs to monitor processes executing 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 disk drive 1535, device controller 1537, network interface 1539, GPS 1541, Bluetooth interface 1542, WiFi interface 1543, etc.). The computing device 1530 may include one or more output devices, such as a display 1536 (e.g., screen, display device, monitor, television, etc.), and may include one or more output device controllers 1537, such as a video processor. One or more user input devices 1538 may also be present, such as a remote control, keyboard, mouse, touchscreen, microphone, etc. The computing device 1530 may also include one or more network interfaces (such as network interface 1539), which may be wired, wireless, or a combination of both. Network interface 1539 can provide the computing device 1530 with an interface to communicate with network 1540 (e.g., RAN or any other network). Network interface 1539 may include a modem (e.g., a cable modem), and external network 1540 may include a communication link, an external network, a home network, a provider's wireless, coaxial cable, fiber optic, or hybrid fiber / coaxial cable distribution system (e.g., a DOCSIS network), or any other desired network. Additionally, computing device 1530 may include a location detection device, such as a Global Positioning System (GPS) microprocessor 1541, which can be configured to receive and process GPS signals and determine the geographic location of computing device 1530 with possible assistance from external servers and antennas.

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

[0193] Figure 16A An exemplary structure for uplink transmission is shown. Processing of the baseband signal representing the physical uplink shared channel may include / perform one or more functions. These one or more functions may include at least one of the following: scrambling; modulating scrambling bits to generate complex-valued symbols; mapping complex-valued modulated symbols onto one or more transport layers; transform precoding to generate complex-valued symbols; precoding the complex-valued symbols; mapping the precoded complex-valued symbols to resource elements; generating complex-valued time-domain single-carrier frequency division multiple access (SC-FDMA), CP-OFDM signals for antenna ports, or any other signals; and so on. For example, if transform precoding is enabled, an SC-FDMA signal for uplink transmission can be generated. For example, if transform precoding is not enabled (e.g., as...), Figure 16A As shown, CP-OFDM signals for uplink transmission can be generated. These functions are examples, and other mechanisms for uplink transmission can be implemented.

[0194] Figure 16B An exemplary structure for modulating and up-converting a baseband signal to a carrier frequency is shown. The baseband signal can be a complex-valued SC-FDMA, CP-OFDM baseband signal (or any other baseband signal) and / or a complex-valued Physical Random Access Channel (PRACH) baseband signal for the antenna port. For example, filtering can be performed / applied before transmission.

[0195] Figure 16CAn exemplary structure for downlink transmission is shown. Processing of the baseband signal representing the physical downlink channel may include / perform one or more functions. These functions may include: scrambling coded bits in the codeword to be transmitted / transmitted on / via the physical channel; modulating the scrambled bits to generate complex-valued modulation symbols; mapping the complex-valued modulation symbols onto one or more transport layers; precoding the complex-valued modulation symbols on the layers for transmission at the antenna port; mapping the complex-valued modulation symbols at the antenna port to resource elements; generating a complex-valued time-domain OFDM signal for the antenna port; and so on. These functions are examples, and other mechanisms for downlink transmission can be implemented.

[0196] Figure 16D An exemplary structure for modulating and up-converting a baseband signal to a carrier frequency is shown. The baseband signal can be a complex-valued OFDM baseband signal for the antenna port or any other signal. For example, filtering can be performed / applied before transmission.

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

[0198] A timer can, for example, start running once started and continue running until it stops or until it expires. For example, a timer can be started if it is not running, or restarted if it is running. A timer can be associated with a value (e.g., a timer can be started or restarted from a certain value, or it can be started from zero and expire once said value is reached). For example, the duration of a timer may not be updated until it stops or expires (e.g., due to a BWP switch). A timer can be used to measure time periods / windows used for a process. Regarding implementations and / or procedures associated with one or more timers or other parameters, it should be understood that there can be multiple ways to implement such timers or other parameters. One or more of these multiple ways of implementing a timer can be used to measure time periods / windows used for a program. A random access response window timer can be used to measure a time window used to receive a random access response. For example, instead of starting the random access response window timer and determining its expiration, the time difference between two timestamps can be used. For example, if the timer is restarted, the process used to measure the time window can be restarted. Other exemplary implementations can be configured / provided to restart the measurement of the time window.

[0199] A wireless device can receive one or more messages (e.g., RRC messages or RRC reconfiguration messages) from a base station. These messages may include one or more configuration parameters. The configuration parameters may be specific to one or more cells (e.g., a single cell). These configuration parameters may include one or more PDSCH configuration parameters for the cell (e.g., as in the PDSCH-Config information element, such as...). Figure 20C (As shown).

[0200] One or more configuration parameters can indicate a list of non-periodic trigger states for non-periodic CSI reports (e.g., based on higher-level parameters such as CSI-AperiodicTriggerStateList information elements, such as...). Figure 20B (As shown). The wireless device can receive a DCI that triggers the transmission of aperiodic CSI reports. The DCI may indicate, for example, an aperiodic trigger state from a list of aperiodic trigger states. The aperiodic trigger states may include and / or indicate a list of CSI report configuration information (e.g., associatedReportConfigInfoList, such as...). Figure 20B (As shown). The list of CSI report configuration information may include CSI report configuration information. CSI report configuration information (e.g., CSI-AssociatedReportConfigInfo, such as...) Figure 20B(As shown) may include and / or indicate a reference signal resource set (e.g., NZP-CSI-RS-ResourceSet, resourceSet, in) used for channel measurements. Figure 20B In the middle, resourceSet2). The reference signal resource set may include one or more reference signal resources. One or more reference signal resources may indicate / configure (or may be associated with) one or more reference signals (e.g., CSI-RS, TRS, aperiodic CSI-RS, etc.). CSI report configuration information may include at least one TCI status index / identifier (e.g., Figure 20B (TCI-StateId in the text).

[0201] In at least some wireless communications, parameters are based on a list of TCI state parameters (e.g., TCI state additions or modifications, such as...). Figure 20C The TCI-StatesToAddModList (as shown) indicates and / or configures one or more TCI states based on the TCI state list parameters, at least one of which is a TCI state. The wireless device can receive and / or measure and / or evaluate one or more reference signals. The TCI state list parameters can be identified and / or indicated by at least one TCI state index and / or identifier. One or more PDSCH configuration parameters may include the TCI state list parameters. Each of the at least one TCI state index and / or identifier can indicate and / or identify the corresponding TCI state among at least one TCI state.

[0202] One or more PDSCH configuration parameters may exclude TCI state list parameters (e.g., tci-StatesToAddModList). Based on TCI states, the wireless device may not receive and / or measure and / or evaluate one or more reference signals. For example, based on (e.g., because) one or more PDSCH configuration parameters do not include TCI state list parameters, one or more reference signals may not be received and / or measured and / or evaluated. Not receiving and / or not measuring and / or not evaluating one or more reference signals may result in inaccurate channel estimation. For example, based on not receiving and / or not measuring one or more reference signals based on TCI states, the wireless device may not measure the radio link quality of one or more reference signals. For example, based on not receiving and / or not measuring one or more reference signals based on TCI states, the wireless device may inaccurately measure the radio link quality of one or more reference signals.

[0203] As disclosed herein, for example, if one or more PDSCH configuration parameters do not include a TCI state list parameter (e.g., tci-StatesToAddModList), then CSI reporting (e.g., aperiodic CSI reporting) can be enhanced. Examples of aperiodic CSI reporting are discussed herein, but the concepts herein can also, or alternatively, be applied to periodic CSI reporting. One or more PDSCH configuration parameters may include downlink or joint TCI state list parameters (e.g., Figure 20C (dl-OrJoint-TCI-StateList in the context of this).

[0204] Downlink or joint TCI state list parameters may include downlink or joint TCI state parameters indicating one or more TCI states (e.g., downlink or joint TCI state addition or modification parameters, such as...). Figure 20C The wireless device can receive and / or measure and / or evaluate one or more reference signals based on at least one of one or more TCI states indicated and / or configured by downlink or joint TCI state parameters, wherein the downlink or joint TCI state parameters are identified and / or indicated by at least one TCI state index and / or identifier. Each TCI state index in the at least one TCI state index and / or identifier can indicate and / or identify the corresponding TCI state in the at least one TCI state.

[0205] Downlink or joint TCI state list parameters may include unified TCI state reference parameters (e.g., Figure 20C The unifiedTCI-StateRef in the downlink or joint TCI state list parameter may not include the downlink or joint TCI state parameter (e.g., Figure 20C The unified TCI state reference parameter can indicate the reference cell and reference BWP, where downlink or joint TCI state parameters for the cell (or the cell's BWP) are configured / defined (e.g., dl-OrJointTCI-StateToAddModList). Figure 20C The dl-OrJointTCI-StateToAddModList in the table. One or more cells may include a reference cell. One or more configuration parameters may include one or more second PDSCH configuration parameters of the reference cell (e.g., PDSCH-Config in Figure 20, and such as...). Figure 20C (as shown in Figure 21). One or more second PDSCH configuration parameters may include downlink or joint TCI status parameters indicating one or more TCI states (e.g., Figure 20CThe text discusses the use of `dl-OrJointTCI-StateToAddModList` to represent a reference signal. It describes a radio device that can receive and / or measure and / or evaluate one or more reference signals based on at least one TCI state indicated and / or configured by downlink or joint TCI state parameters of a reference BWP for a reference cell. The text also mentions that each TCI state index can indicate and / or identify a corresponding TCI state among at least one TCI state. As disclosed herein, CSI reporting (e.g., aperiodic and / or periodic CSI reporting) can be enhanced. The radio device can accurately measure the radio link quality of one or more reference signals (e.g., if no TCI state is configured for the cell). This can lead to better channel estimation and / or scheduling decisions by the base station.

[0206] A wireless device can (e.g., from a base station) receive one or more messages (e.g., RRC messages, RRC reconfiguration messages, etc.) that include one or more configuration parameters. The one or more configuration parameters can be specific to one or more cells, including a single cell. The one or more configuration parameters can include one or more PDSCH configuration parameters for the cell (e.g., PDSCH-Config 1935, such as...). Figure 19 , 20C (as shown in Figure 21). One or more configuration parameters can indicate the reference signal resources used for periodic CSI reporting (e.g., by means of, such as...). Figure 20A The higher-level parameter NZP-CSI-RS-Resource is provided. Reference signal resources can indicate and / or configure and / or be associated with reference signals (e.g., CSI-RS, TRS, aperiodic CSI-RS). For reference signal resources, one or more configuration parameters can indicate the TCI state index and / or identifier (e.g., such as...). Figure 20A (TCI-StateId in the text).

[0207] In at least some wireless communications, based on parameters from the TCI state list (e.g., Figure 20CThe TCI state (tci-StatesToAddModList) parameter indicates and / or configures one or more TCI states, allowing the wireless device to receive and / or measure and / or evaluate a reference signal. The TCI state list parameter is identified and / or indicated by a TCI state index / identifier. One or more PDSCH configuration parameters may include the TCI state list parameter. One or more PDSCH configuration parameters may not include the TCI state list parameter (e.g., tci-StatesToAddModList). For example, in response to one or more PDSCH configuration parameters not including the TCI state list parameter, the wireless device may not receive and / or measure and / or evaluate the reference signal based on the TCI state. This may lead to inaccurate channel estimation. For example, in response to not receiving and / or not measuring the reference signal based on the TCI state, the wireless device may not measure the radio link quality of the reference signal. For example, in response to not receiving and / or not measuring the reference signal based on the TCI state, the wireless device may inaccurately measure the radio link quality of the reference signal.

[0208] As disclosed herein, periodic CSI reporting can be enhanced for cases where one or more PDSCH configuration parameters do not include TCI state list parameters (e.g., tci-StatesToAddModList). One or more PDSCH configuration parameters may include downlink or joint TCI state list parameters (e.g., such as...). Figure 20C (dl-OrJoint-TCI-StateList in the context of this).

[0209] Downlink or joint TCI state list parameters may include downlink or joint TCI state parameters indicating one or more TCI states (e.g., such as...). Figure 20C (dl-OrJointTCI-StateToAddModList). Based on the TCI state among one or more TCI states indicated and / or configured by downlink or joint TCI state parameters, the wireless device can receive and / or measure and / or evaluate reference signals, the downlink or joint TCI state parameters being identified and / or indicated by TCI state indexes and / or identifiers.

[0210] Downlink or joint TCI state list parameters may include unified TCI state reference parameters (e.g., such as...) Figure 20C The unifiedTCI-StateRef in the context of TCI. Downlink or joint TCI state list parameters may not include downlink or joint TCI state parameters (e.g., such as...). Figure 20CThe unified TCI state reference parameter can indicate for which downlink or joint TCI state parameters have been configured and / or defined (e.g., dl-OrJointTCI-StateToAddModList). Figure 20C The reference cell and / or reference BWP in (dl-OrJointTCI-StateToAddModList) can be one or more cells. One or more configuration parameters can include one or more second PDSCH configuration parameters of the reference cell (e.g., PDSCH-Config 1935, such as...). Figure 19 , 20C (as shown in Figure 21). One or more second PDSCH configuration parameters may include downlink or joint TCI status parameters indicating one or more TCI states (e.g., such as...). Figure 20C The reference is defined in the `dl-OrJointTCI-StateToAddModList`. Based on one or more TCI states indicated and / or configured according to the downlink or joint TCI state parameters of the reference BWP of the reference cell, the radio device can receive and / or measure and / or evaluate the reference signal, where the downlink or joint TCI state parameters are identified and / or indicated by TCI state indexes and / or identifiers. Using unified TCI state reference parameters (e.g., based on unreceived and / or unconfigured downlink or joint TCI state parameters) can enhance periodic and / or aperiodic CSI reporting. The radio device can (e.g., based on unified TCI state reference parameters) accurately measure the radio link quality of the reference signal. This can lead to / allow the base station to perform better channel estimation and / or decision scheduling.

[0211] Figure 17 and Figure 18 An example of TCI state activation is shown. The wireless device can receive one or more messages. Figure 17 An example of TCI state activation is shown. Wireless device 1705 can receive one or more messages from base station 1710. Wireless device 1705 can receive one or more messages from a relay node. Wireless device 1705 can receive one or more messages from another wireless device (e.g., TRP, vehicle, remote wireless head, etc.). The one or more messages may include one or more configuration parameters 1720 (e.g., such as...). Figure 17 (As described in the text, the configuration parameters at time T0).

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

[0213] One or more configuration parameters 1720 can be RRC reconfiguration parameters. One or more configuration parameters 1720 can be for one or more cells. One or more cells can include a single cell. A cell can be, for example, a serving cell. At least one of the one or more configuration parameters 1720 can be for a cell. A cell can be a primary cell (PCell). A cell can be a primary-secondary cell (PSCell). A cell can be a secondary cell (SCell). A cell can be a secondary cell configured with a PUCCH (e.g., a PUCCH SCell). A cell can be a special cell (SpCell). For dual connectivity (DC) operation, SpCell can refer to (or indicate) the PCell of the MCG or the PUCell of the SCG. SpCell can refer to (or indicate) the PCell. A cell can be the primary SCG cell (PSCell). For dual connectivity operation, if a synchronization reconfiguration procedure is performed, the radio device can perform a random access procedure, for example, via the PUCell.

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

[0215] Radio device 1705 can perform and / or perform uplink transmissions (e.g., PUSCH, PUCCH, PUCCH) of the cell via a first time and / or a first frequency. Radio device 1705 can perform and / or perform downlink receptions (e.g., PDCCH, PDSCH) of the cell via a second time and / or a second frequency. The cell can operate in Time Division Duplex (TDD) mode. In TDD mode, the first frequency and the second frequency can be the same. In TDD mode, the first time and the second time can be different. The cell can operate in Frequency Division Duplex (FDD) mode. In FDD mode, the first frequency and the second frequency can be different. In FDD mode, the first time and the second time can be the same. Radio device 1705 can be in RRC connected mode. Radio device 1705 can be in RRC idle mode. Radio device 1705 can be in RRC inactive mode.

[0216] A cell may include multiple Backplane Devices (BWPs). The multiple BWPs may include one or more uplink BWPs, which include the cell's uplink BWP (UL BWP). The multiple BWPs may include one or more downlink BWPs, which include the cell's downlink BWP. One of the multiple BWPs may be in an active state or an inactive state (or deactivated state). In the active state of one or more downlink BWPs, for example, the radio device 1705 may monitor downlink channels and / or signals (e.g., PDCCH, DCI, CSI-RS, PDSCH) on, for, and / or via the downlink BWP. In the active state of one or more downlink BWPs, the radio device 1705 may receive PDSCH on, for, and / or via the downlink BWP. In the inactive state of one or more downlink BWPs, the wireless device 1705 may not monitor downlink channels and / or signals (e.g., PDCCH, DCI, CSI-RS, PDSCH) on, for, or via the downlink BWP. In the inactive state of one or more downlink BWPs, the wireless device may stop monitoring and / or receiving downlink channels and / or signals (e.g., PDCCH, DCI, CSI-RS, PDSCH) on, for, and / or via the downlink BWP. In the inactive state of one or more downlink BWPs, the wireless device 1705 may not receive PDSCH on, for, or via the downlink BWP. In the inactive state of one or more downlink BWPs, the wireless device 1705 may stop receiving PDSCH on, for, and / or via the downlink BWP.

[0217] 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.) on and / or via 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.) on or via the uplink BWPs.

[0218] The wireless device 1705 can activate one or more downlink BWPs in a cell. Activating a downlink BWP may include setting the downlink BWP to and / or switching to the cell's active downlink BWP. 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.

[0219] The wireless device 1705 can activate one or more uplink BWPs in a cell. Activating an uplink BWP may include the wireless device 1705 setting and / or switching an uplink BWP to the cell's active uplink BWP. Activating an uplink BWP may include setting an uplink BWP to an active state. Activating an uplink BWP may include switching an uplink BWP from an inactive state to an active state.

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

[0221] One or more configuration parameters may be configured for the uplink BWP of a cell (e.g., the active uplink BWP). At least one of the one or more configuration parameters may be configured for the uplink BWP of a cell. One or more configuration parameters may indicate the subcarrier spacing and / or parameter set used for the uplink BWP.

[0222] The subcarrier spacing values ​​for the downlink BWP and / or uplink BWP can be and / or indicate, for example, 15 kHz (mu = 0). The subcarrier spacing values ​​can be and / or indicate, for example, 30 kHz (mu = 1). The subcarrier spacing values ​​can be and / or indicate, for example, 60 kHz (mu = 2). The subcarrier spacing values ​​can be and / or indicate, for example, 120 kHz (mu = 3). The subcarrier spacing values ​​can be and / or indicate, for example, 240 kHz (mu = 4). The subcarrier spacing values ​​can be and / or indicate, for example, 480 kHz (mu = 5). The subcarrier spacing values ​​can be and / or indicate, for example, 960 kHz (mu = 6). 480 kHz can be valid and / or applicable in FR3. 960 kHz can be valid and / or applicable in FR3. 240 kHz can be valid and / or applicable in FR3. 120 kHz can be valid and / or applicable in FR3.

[0223] One or more configuration parameters can indicate multiple control resource sets (coresets). These configuration parameters can indicate multiple coresets for a cell's downlink BWP (e.g., an active downlink BWP). A downlink BWP (e.g., an active downlink BWP) can include multiple coresets. The one or more configuration parameters can indicate multiple coreset indices, identifiers, and / or indicators (e.g., provided by the higher-layer parameter ControlResourceSetId) for the multiple coresets. Each coreset in the multiple coresets can be identified and / or indicated by a corresponding coreset index among the multiple coreset indices. A first coreset in the multiple coresets can be identified by a first coreset index among the multiple coreset indices. A second coreset in the multiple coresets can be identified by a second coreset index among the multiple coreset indices.

[0224] One or more configuration parameters 1720 can indicate one or more coreset pool indices (e.g., provided by the higher-level parameter CoresetPoolIndex) for multiple coresets. Each coreset in the multiple coresets can be configured, indicated, and / or included by one or more configuration parameters through a corresponding coreset pool index (e.g., 0, 1, etc.) in one or more coreset pool indices. One or more configuration parameters 1720 can indicate a corresponding coreset pool index in one or more coreset pool indices for each coreset in the multiple coresets. One or more configuration parameters 1720 can indicate, for example, a first coreset pool index 1825 (CoresetPoolIndex = 0) for a first coreset in the multiple coresets. One or more configuration parameters can indicate a second coreset pool index 1845 (CoresetPoolIndex = 1) for a second coreset in the multiple coresets. One or more coreset pool indices can include a first coreset pool index 1825 and a second coreset pool index 1845.

[0225] Alternatively, one or more configuration parameters 1720 may not indicate a coreset pool index for a coreset among multiple coresets. The higher-level parameter `CoresetPoolIndex` may not be included in the coreset's configuration parameters. The wireless device 1805 may determine the value of the coreset pool index of the coreset (e.g., a default value) as the first coreset pool index 1825 (`CoresetPoolIndex = 0`). For example, based on one or more configuration parameters not indicating a coreset pool index for the coreset, the first coreset pool index 1825 (`CoresetPoolIndex = 0`) may be the coreset pool index of the coreset. For example, based on one or more configuration parameters not indicating a coreset pool index for the coreset, the wireless device 1805 may determine the value of the coreset pool index of the coreset (e.g., a default value) as the first coreset pool index 1825.

[0226] A first coreset pool (e.g., coreset pool 0) may include one or more first coresets whose coreset pool index may be equal to first coreset pool index 1825 (e.g., CoresetPoolIndex = 0). One or more configuration parameters 1720 may indicate first coreset pool index 1825 for each of the one or more first coresets in the first coreset pool. Multiple coresets may include one or more first coresets.

[0227] A second coreset pool (e.g., coreset pool 1) may include one or more second coresets whose coreset pool index is equal to second coreset pool index 1845 (e.g., CoresetPoolIndex = 1). One or more configuration parameters 1720 may indicate second coreset pool index 1845 for each coreset in one or more second coresets within the second coreset pool. Multiple coresets may include one or more second coresets.

[0228] One or more configuration parameters 1820 may not indicate a coreset pool index for a coreset among multiple coresets. For example, based on one or more configuration parameters 1820 not indicating a coreset pool index for a coreset, the wireless device 1805 may determine a default value for the coreset pool index of a 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). For example, based on one or more configuration parameters not indicating a coreset pool index for a coreset, the first coreset pool may include the coreset. Based on the default value of the coreset pool index of a coreset being equal to the first coreset pool index 1825, the first coreset pool may include the coreset.

[0229] The first coreset pool index 1825 of the first coreset and the second coreset pool index 1845 of the second coreset 1858 can be the same. One or more configuration parameters can indicate the same coreset pool index for the first coreset and the second coreset 1858. Multiple coresets can include the first coreset and the second coreset 1858. One or more coreset pool indices can include the first coreset pool index 1825 and the second coreset pool index 1845. 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 the same, the wireless device 1805 can group the first coreset and the second coreset 1858 into the same coreset pool (e.g., CoresetPoolIndex = 0 or CoresetPoolIndex = 1). 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 the same, the first coreset pool including the first coreset and the second coreset pool including the second coreset 1858 can be the same.

[0230] The first coreset pool index 1825 of the first coreset and the second coreset pool index 1840 of the second coreset 1858 can be different. Multiple coresets can include the first coreset and the second coreset 1858. One or more coreset pool indices can include the first coreset pool index 1825 and the second coreset pool index 1840. For example, based on the difference between the first coreset pool index 1825 of the first coreset and the second coreset pool index 1840 of the second coreset 1858, the wireless device 1805 can group the first coreset and the second coreset 1858 into different coreset pools. The wireless device 1805 can group the first coreset into a first coreset pool (e.g., CoresetPoolIndex = 0). For example, based on the difference between the first coreset pool index 1825 and the second coreset pool index 1840, the wireless device 1805 can group the second coreset 1858 into a second coreset pool different from the first coreset pool (e.g., CoresetPoolIndex = 1). For example, the first coreset pool index 1825 and the second coreset pool index 1840 based on the first coreset pool index 1858 are different, and the first coreset pool and the second coreset pool can be different.

[0231] One or more configuration parameters 1820 may indicate at least two coreset pool indices (e.g., 0 and 1) of the higher-level parameter CORESETPoolIndex. One or more configuration parameters 1820 may include a higher-level parameter CORESETPoolIndex having and / or being 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) of 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) of one or more second coresets among a plurality of coresets that differs from the first coreset pool index 1825. One or more first coresets may include one or more third coresets among a plurality of coresets that do not have a value for the higher-level parameter CORESETPoolIndex. One or more configuration parameters 1820 may exclude the higher-level parameter CORESETPoolIndex of one or more third coresets.

[0232] A cell may include multiple Transmit and Receive Points (TRPs). Multiple TRPs may serve the cell and / or serve radio devices 1805 within and / or via the cell. At least one of the multiple TRPs may serve the cell and / or serve radio devices within and / or via the cell. The multiple TRPs may include a first TRP and a second TRP. The first TRP may transmit (e.g., transmit) downlink transmissions and / or signals (e.g., PDSCH, PDCCH, DCI) via a first coreset pool. Transmitting downlink transmissions and / or signals (e.g., PDCCH, DCI) via the first coreset pool may include the first TRP transmitting downlink transmissions and / or signals via a first coreset having and / or being associated with an index of the first coreset pool. The first TRP may transmit (e.g., transmit) downlink transmissions and / or signals (e.g., PDSCH, PDCCH, DCI) without via a second coreset pool. Downlink transmissions and / or signals (e.g., PDSCH, PDCCH, DCI) not transmitted via the second coreset pool may include the first TRP not transmitting (e.g., transmitting) downlink transmissions and / or signals via the second coreset1858 having and / or being associated with the second coreset pool index.

[0233] The second TRP may be sent (e.g., transmitted) via the second coreset pool. Transmitting downlink transmissions and / or signals (e.g., PDSCH, PDCCH, DCI) via the second coreset pool may include the second TRP being sent (e.g., transmitted) via the second coreset pool. The second TRP may not be sent (e.g., transmitted) via the first coreset pool. Transmitting downlink transmissions and / or signals (e.g., PDCCH, DCI) without passing through the first coreset pool may include the second TRP not being sent (e.g., transmitted) via the first coreset pool.

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

[0235] 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 include multiple uplink resources. Each of the one or more uplink resource sets and / or groups may include a corresponding uplink resource from the multiple uplink resources. A first uplink resource set and / or group in one or more uplink resource sets and / or groups may include one or more first uplink resources from the multiple uplink resources. A second uplink resource set and / or group in one or more uplink resource sets and / or groups may include one or more second uplink resources from the multiple uplink resources. The first and / or groups and the second uplink resource sets and / or groups may not include (e.g., share) common (e.g., shared, identical, etc.) uplink resources from the multiple uplink resources. A first uplink resource that may be in the first uplink resource set and / or group may not be in the second uplink resource set and / or group.

[0236] One or more configuration parameters can indicate multiple uplink resource indices, identifiers, and / or indicators (e.g., provided by higher-layer parameters PUCCH-ResourceId, SRS-ResourceId) for multiple uplink resources. Each of the multiple uplink resources can be identified and / or indicated by a corresponding uplink resource index among the multiple uplink resource indices. A first uplink resource among the multiple uplink resources can be identified by a first uplink resource index among the multiple uplink resource indices. A second uplink resource among the multiple uplink resources can be identified by a second uplink resource index among the multiple uplink resource indices.

[0237] 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-layer parameters PUCCH-ResourceGroupId, SRS-ResourceSetId). Each uplink resource set and / or group in one or more uplink resource sets and / or groups may be identified and / or indicated by a corresponding uplink resource set and / or group index in one or more uplink resource set and / or group indices. A first uplink resource set and / or group in one or more uplink resource sets and / or groups may be identified by a first uplink resource set and / or group index in one or more uplink resource set and / or group indices. A second uplink resource set and / or group in one or more uplink resource sets and / or groups may be identified by a second uplink resource set and / or group index in one or more uplink resource set and / or group indices.

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

[0239] One or more configuration parameters may not indicate a coreset pool index for an uplink resource among multiple uplink resources. The higher-level parameter `CoresetPoolIndex` may not be included in the configuration parameters for the uplink resource. The wireless device 1805 may determine the value of the coreset pool index for the uplink resource (e.g., a default value) as the first coreset pool index (`CoresetPoolIndex = 0`). For example, based on one or more configuration parameters not indicating a coreset pool index for the uplink resource, the wireless device may determine the value of the coreset pool index for the uplink resource (e.g., a default value) as the first coreset pool index. For example, based on one or more configuration parameters not indicating a coreset pool index for the uplink resource, the first coreset pool index (`CoresetPoolIndex = 0`) may be the coreset pool index for the uplink resource.

[0240] One or more configuration parameters may indicate at least two coreset pool indices (e.g., 0 and 1) of the higher-level parameter CORESETPoolIndex. One or more configuration parameters may include a higher-level parameter CORESETPoolIndex that 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) of one or more first uplink resources. At least two coreset pool indices may include a second coreset pool index (e.g., 1) of one or more second uplink resources that differs from the first coreset pool index. One or more first uplink resources may include one or more third uplink resources that do not have a value for the higher-level parameter CORESETPoolIndex. One or more configuration parameters may exclude the higher-level parameter CORESETPoolIndex of one or more third uplink resources.

[0241] A cell may include multiple Transmit and Receive Points (TRPs). Multiple TRPs may serve the cell, and / or serve radio devices within the cell, via the cell, and / or the cell. At least one of the multiple TRPs may serve the cell, and / or serve radio devices within the cell, via the cell, and / or the cell. The multiple TRPs may include a first TRP and a second TRP.

[0242] The first TRP may receive uplink transmissions and / or signals (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) via a first uplink resource that has and / or is associated with a first coreset pool index among multiple uplink resources. The first TRP may receive uplink transmissions and / or signals (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) without via a second uplink resource that has and / or is associated with a second coreset pool index among multiple uplink resources.

[0243] The second TRP may receive uplink transmissions and / or signals (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) via a second uplink resource that has and / or is associated with a second coreset pool index among multiple uplink resources. The second TRP may also receive uplink transmissions and / or signals (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) without via a first uplink resource that has and / or is associated with a first coreset pool index among multiple uplink resources.

[0244] One or more configuration parameters can 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 can be configured and / or indicated by one or more configuration parameters, including the corresponding coreset pool index in one or more coreset pool indices (e.g., 0, 1). One or more configuration parameters can indicate the corresponding coreset pool index in one or more coreset pool indices for each uplink resource set and / or group in one or more uplink resource sets and / or groups. One or more configuration parameters can indicate, for example, a first coreset pool index 1825 (CoresetPoolIndex = 0) for a first uplink resource set and / or group in one or more uplink resource sets and / or groups. One or more configuration parameters can indicate, for example, a second coreset pool index 1845 (CoresetPoolIndex = 1) for a second uplink resource set and / or group in one or more uplink resource sets and / or groups. One or more coreset pool indexes may include a first coreset pool index and a second coreset pool index.

[0245] One or more configuration parameters may not indicate a coreset pool index for one or more uplink resource sets and / or groups. The higher-level parameter `CoresetPoolIndex` may not be included in the configuration parameters for the uplink resource set and / or group. The radio device 1805 may determine the value (e.g., a default value) of the coreset pool index for the uplink resource set and / or group as the first coreset pool index 1825 (CoresetPoolIndex = 0). For example, based on one or more configuration parameters not indicating a coreset pool index for the uplink resource set and / or group, the radio device may determine the value (e.g., a default value) of the coreset pool index for the uplink resource set and / or group as the first coreset pool index. For example, based on one or more configuration parameters not indicating a coreset pool index for the uplink resource set and / or group, the first coreset pool index 1825 (CoresetPoolIndex = 0) may be the coreset pool index for the uplink resource set and / or group.

[0246] One or more configuration parameters may indicate at least two coreset pool indices (e.g., 0 and 1) of the higher-level parameter CORESETPoolIndex. One or more configuration parameters may include the higher-level parameter CORESETPoolIndex having and / or being set to at least two coreset pool indices. The at least two coreset pool indices may include a first coreset pool index (e.g., 0) of one or more first uplink resource sets and / or groups. The at least two coreset pool indices may include a second coreset pool index (e.g., 1) of one or more second uplink resource sets and / or groups that differs from the first coreset pool index. One or more first uplink resource sets and / or groups may include one or more third uplink resource sets and / or groups that do not have a value for the higher-level parameter CORESETPoolIndex. One or more configuration parameters may exclude the higher-level parameter CORESETPoolIndex of one or more third uplink resource sets and / or groups.

[0247] A cell may include multiple Transmit and Receive Points (TRPs). Multiple TRPs may serve the cell, and / or serve radio devices in / via the cell / the cell. At least one of the multiple TRPs may serve the cell, and / or serve radio devices in, via, and / or the cell. Multiple TRPs may include a first TRP and a second TRP.

[0248] The first 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 that have and / or are associated with a first coreset pool index. The first TRP may also receive uplink transmissions and / or signals (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) without via uplink resources in one or more uplink resource sets and / or groups that have and / or are associated with a second coreset pool index.

[0249] The 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 that have and / or are associated with a second coreset pool index. The second TRP may also receive uplink transmissions and / or signals (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) without via uplink resources in one or more uplink resource sets and / or groups that have and / or are associated with a first coreset pool index.

[0250] A wireless device may transmit (e.g., carry out) uplink transmissions and / or signals (e.g., PUSCH / PUCCH / SRS transmissions) via uplink resources. Multiple uplink resources may be included. One or more sets and / or groups of uplink resources may include uplink resources.

[0251] Wireless device 1805 can receive downlink control information (DCI) 1830 via a coreset from among a plurality of coresets, which schedules, triggers, and / or instructs the transmission of uplink transmissions and / or signals. DCI 1830 can schedule, trigger, and / or instruct the transmission of uplink transmissions and / or signals via uplink resources. DCI can indicate uplink resources. DCI may include fields indicating uplink resources.

[0252] Uplink transmissions and / or signaling can be PUSCH transmissions (e.g., transport blocks). Uplink resources can be PUSCH resources. The DCI 1830 can schedule the transmission of PUSCH transmissions. Uplink transmissions and / or signaling can be PUCCH transmissions (e.g., HARQ-ACK information feedback). Uplink resources can be PUCCH resources. The DCI 1830 can schedule the reception of transport blocks (e.g., PDSCH reception). Uplink transmissions and / or signaling can be HARQ-ACK information feedback for transport blocks. Uplink transmissions and / or signaling can be SRS. Uplink resources can be SRS resources. The DCI 1830 can schedule the transmission of SRS. SRS can be, for example, aperiodic SRS.

[0253] The coreset from which the wireless device 1805 receives DCI can be associated with a coreset pool index. One or more coreset pool indices can include coreset pool indices. One or more configuration parameters can indicate a coreset pool index for a coreset. One or more configuration parameters can not indicate a coreset pool index for a coreset (CoresetPoolIndex = 0 or CoresetPoolIndex = 1). For example, if one or more configuration parameters do not indicate a coreset pool index for a coreset, the value of the coreset pool index of the coreset (e.g., the default value) can be equal to the first coreset pool index (CoresetPoolIndex = 0).

[0254] Uplink resources can be associated with coreset pool indexes. For example, an uplink resource can be associated with a coreset pool index based on a DCI that receives, schedules, triggers, and / or indicates the transmission of uplink transmissions and / or signals via the uplink resource through a coreset associated with the coreset pool index.

[0255] An uplink resource set and / or group that includes uplink resources can be associated with a coreset pool index. For example, an uplink resource set and / or group can be associated with a coreset pool index based on a DCI that receives, schedules, triggers, and / or indicates the transmission of uplink transmissions and / or signals via uplink resources (belonging to the uplink resource set and / or group) received via a coreset associated with the coreset pool index. An uplink resource set and / or group can include one or more uplink resources. For example, based on an uplink resource set and / or group that includes one or more uplink resources being associated with a coreset pool index, one or more uplink resources can be associated with the coreset pool index. For example, based on an uplink resource set and / or group that includes one or more uplink resources being associated with a coreset pool index, each of the one or more uplink resources can be associated with the coreset pool index.

[0256] Uplink transmissions and / or signals can be associated with a coreset pool index. For example, an uplink transmission and / or signal can be associated with a coreset pool index based on a DCI1830 that receives, schedules, triggers, and / or indicates the transmission of uplink transmissions and / or signals via a coreset associated with the coreset pool index.

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

[0258] One or more configuration parameters 1720 can indicate multiple TCI states 1770, which indicate a unified TCI state of the 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 can indicate multiple TCI states 1770 of the cell's downlink BWP.

[0259] One or more configuration parameters 1720 may include one or more PDSCH configuration parameters for, for example, a second downlink BWP of a second cell. One or more configuration parameters 1720 may indicate multiple TCI states 1770 for the second downlink BWP of the second cell. One or more cells may include a second cell. One or more configuration parameters may include, for the downlink BWP of a cell, a reference unified TCI state list parameter (e.g., unifiedTCI-StateRef) indicating the second downlink BWP of the second cell. The reference unified TCI state list parameter may include a BWP index (e.g., BWP-Id) identifying (e.g., indicating) the second downlink BWP. The reference unified TCI state list parameter may include a cell index (e.g., ServCellIndex) identifying (e.g., indicating) the second cell. The second downlink BWP of the second cell may be a reference BWP of a reference cell for the downlink BWP of the cell. The downlink BWP of the cell may be a target BWP of the target cell. For example, the downlink BWP for a cell may include a reference to the unified TCI state list parameter based on one or more configuration parameters. One or more PDSCH configuration parameters of the cell's downlink BWP may not include the higher-layer (e.g., RRC) parameter dl-OrJoint-TCIStateList.

[0260] One or more configuration parameters 1720 may include a uniform TCI status type parameter (e.g., as described in this article). Figure 17 The unifiedTCI-StateType is described in [the document]. One or more configuration parameters may include one or more serving cell parameters (e.g., ServingCellConfig), which include the unified TCI state type parameter. The unified TCI state type parameter can indicate the unified TCI state type of the cell.

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

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

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

[0264] One or more configuration parameters 1720 may include, for example, one or more uplink BWP configuration parameters for a cell's uplink BWP. One or more configuration parameters 1720 may indicate a second or more TCI states 1770 for the cell's uplink BWP.

[0265] One or more configuration parameters 1720 may include one or more uplink BWP configuration parameters for, for example, a second uplink BWP of a second cell. One or more configuration parameters 1720 may indicate a second plurality of TCI states 1770 for the second uplink BWP of the second cell. One or more cells may include a second cell. One or more configuration parameters 1720 may include, for the uplink BWP of a cell, a reference unified TCI state list parameter (e.g., unifiedtci-StateType) indicating the second uplink BWP of the second cell. The reference unified TCI state list parameter may include an identifier (e.g., indicating) a BWP index (e.g., BWP-Id) of the second uplink BWP. The reference unified TCI state list parameter may include an identifier (e.g., indicating) a cell index (e.g., ServCellIndex) of the second cell. The second uplink BWP of the second cell may be a reference BWP of a reference cell for the uplink BWP of the cell. The uplink BWP of the cell may be a target BWP of the target cell. For example, the uplink BWP for a cell may include reference to the unified TCI state list parameter based on one or more configuration parameters. One or more uplink BWP configuration parameters for the cell's uplink BWP may not include higher-layer (e.g., RRC) parameters, such as ul-TCI-StateList.

[0266] For example, based on one or more configuration parameters including a unified TCI state type parameter set to "separate", the radio device 1705 can use (e.g., apply) a second plurality of TCI states 1770 for uplink transmissions of the cell (e.g., PUSCH / PUCCH / SRS transmissions). For example, based on one or more configuration parameters including a unified TCI state type parameter set to "separate", the radio device 1705 can use (e.g., apply) a second plurality of TCI states 1770 without using them for downlink receptions of the cell (e.g., PDCCH / PDSCH / CSI-RS receptions).

[0267] For example, based on one or more configuration parameters 1720 indicating multiple TCI states 1770 of the cell's downlink BWP, the radio device 1705 can use multiple TCI states 1770 for downlink reception via the cell's downlink BWP.

[0268] For example, based on one or more configuration parameters 1720 indicating multiple TCI states 1770 of the downlink BWP of the cell, the radio device 1705 can use multiple TCI states 1770 for uplink transmission and reception via the uplink BWP of the cell.

[0269] For example, based on the reference to the unified TCI state list parameters indicating the second downlink BWP of the second cell for the downlink BWP of the cell, the radio device 1705 can receive and use multiple TCI states 1770 of the second downlink BWP of the second cell for downlink transmission via the cell's downlink BWP. Similarly, based on the reference to the unified TCI state list parameters indicating the second downlink BWP of the second cell for the downlink BWP of the cell, the radio device 1705 can transmit and receive multiple TCI states 1770 of the second downlink BWP of the second cell for uplink transmission via the cell's uplink BWP.

[0270] For example, based on one or more configuration parameters 1720 indicating a second plurality of TCI states 1770 for the uplink BWP of a cell, the radio device 1705 can use the second plurality of TCI states 1770 for uplink transmission and reception via the uplink BWP of the cell. For example, based on reference to a unified TCI state list parameter indicating a second uplink BWP for a cell, the radio device 1705 can use the second plurality of TCI states 1770 for uplink transmission and reception via the uplink BWP of the cell.

[0271] 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 one or more cells. The one or more PCIs may include the PCI of the cell. One or more configuration parameters 1720 may include a higher-layer (e.g., RRC) parameter physCellId indicating one or more PCIs for one or more cells. The one or more configuration parameters may indicate a corresponding PCI among one or more PCIs for each of the one or more cells. One or more configuration parameters may include a higher-layer (e.g., RRC) parameter physCellId indicating a corresponding PCI among one or more PCIs for each of the one or more cells. One or more configuration parameters may indicate a first PCI among one or more PCIs for a first cell in one or more cells. The first PCI may identify the physical cell identity of the first cell. One or more configuration parameters may indicate a second PCI among one or more PCIs for a second cell in one or more cells. The second PCI may identify the physical cell identity of the second cell.

[0272] One or more configuration parameters can indicate a list of PCI sets (e.g., as described in this article). Figure 17The RRC parameter additionalPCI-ToAddModList is described in the document. One or more configuration parameters may include one or more serving cell parameters indicating a list of PCI sets (e.g., as described in this document). Figure 17 The ServingCellConfig described herein. One or more serving cell parameters may include MIMO parameters (e.g., as described in this document). Figure 17 The MIMO parameter (as described in the document) includes and / or indicates a list of PCI sets. The PCI set list may include at least one PCI set (e.g., by...). Figure 17 The higher-layer parameter SSB-MTC-AdditionalPCI provides and / or indicates this. The list of PCI sets can be associated with SSBs that have PCIs different from the cell's PCI.

[0273] The PCI set list may include and / or indicate at least one PCI from one or more PCIs (e.g., as stated in this document). Figure 17 The additional PCI or PhysCellId described in the PCI set list. Each PCI set in the PCI set list (e.g., SSB-MTC-AdditionalPCI) may include and / or indicate a corresponding PCI in at least one PCI. One or more configuration parameters may indicate a corresponding PCI in at least one PCI for each PCI set in the PCI set list. At least one PCI may not include the cell's PCI. Each PCI in at least one PCI may be different from the cell's PCI. One or more PCIs may include at least one PCI and the cell's PCI. At least one PCI may indicate (e.g., an identifier, etc.) at least one cell in one or more cells. Each PCI in at least one PCI may indicate (e.g., an identifier, etc.) a corresponding cell in at least one cell. The first PCI set in the PCI set list may include the first PCI in at least one PCI. The first PCI may indicate (e.g., an identifier, etc.) the first cell in at least one cell. The second PCI set in the PCI set list may include the second PCI in at least one PCI. The second PCI may indicate (e.g., an identifier, etc.) the second cell in at least one cell. At least one cell may not include the cell. Each cell in at least one cell may be different from the cell. One or more cells may include at least one cell and the cell.

[0274] At least one cell may include, for example, at least one non-serving cell. At least one cell may include, for example, at least one neighboring cell. At least one cell may include, for example, at least one candidate and / or secondary cell.

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

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

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

[0278] For example, a list of PCI sets can be equal to [{1, PCI 5}, {2, PCI 2}, {3, PCI 4}, {4, PCI10}, {5, PCI 21}]. The PCI of a cell can be different from PCI 5, PCI 2, PCI 4, PCI 10, and PCI 21. The following conditions apply:

[0279] ●{1, PCI 5) can be the first PCI set in the PCI set list. '1' can be the first additional PCI index of the first PCI set. PCI 5 can be the first PCI indicating or identifying the first cell and / or can be the first PCI of the first cell.

[0280] ●{2, PCI 2) can be the second PCI set in the PCI set list. '2' can be the second additional PCI index of the second PCI set. PCI 2 indicates, identifies, and / or indicates, identifies the second PCI of the second cell and / or can be the second PCI of the second cell.

[0281] ●{3, PCI 4) can be the third PCI set in the PCI set list. '3' can be the third additional PCI index of the third PCI set. PCI 4 can be the third PCI indicating or identifying the third cell and / or can be the third PCI of the third cell.

[0282] ●{4, PCI 10) can be the fourth PCI set in the PCI set list. '4' can be the fourth additional PCI index of the fourth PCI set. PCI 10 can be the fourth PCI indicating or identifying the fourth cell and / or can be the fourth PCI of the fourth cell.

[0283] ●{5, PCI 21) can be the fifth PCI set in the PCI set list. '5' can be the fifth additional PCI index of the fifth PCI set. PCI 21 can be the fifth PCI indicating or identifying the fifth cell and / or can be the fifth PCI of the fifth cell.

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

[0285] At least one PCI may include PCI 5, PCI 2, PCI 4, PCI 10 and / or PCI 21.

[0286] ○ At least one cell may include a first cell, a second cell, a third cell, a fourth cell, and / or a fifth cell.

[0287] One or more cells may include at least one cell and the cell mentioned above.

[0288] At least one supplementary PCI index may include a first supplementary PCI index (1), a second supplementary PCI index (2), a third supplementary PCI index (3), a fourth supplementary PCI index (4), and a fifth supplementary 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 the cell mentioned above.

[0289] One or more configuration parameters can indicate at least one additional PCI index for one or more TCI states and / or a second set of TCI states. One or more configuration parameters can indicate a corresponding additional PCI index (e.g., additionalPCI, AdditionalPCIIndex) in at least one additional PCI index for each of the one or more TCI states. One or more configuration parameters can indicate a first additional PCI index (e.g., 1) in at least one additional PCI index for a first TCI state in one or more TCI states. The first additional PCI index can indicate (e.g., identifier, etc.) a first PCI set in a PCI set list. One or more configuration parameters can indicate a second additional PCI index (e.g., 2) in at least one additional PCI index for a second TCI state in one or more TCI states. The second additional PCI index can indicate (e.g., identifier, etc.) a second PCI set in a PCI set list. One or more configuration parameters can indicate a third additional PCI index (e.g., 3) in at least one additional PCI index for a third TCI state in one or more TCI states, and so on. The third additional PCI index can indicate (e.g., identifier, etc.) a third PCI set in a PCI set list.

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

[0291] One or more configuration parameters 1720 may not indicate an additional PCI index in at least one additional PCI index for one or more TCI states among multiple TCI states 1770. The additional PCI index may not be included (e.g., not exist) in the configuration parameters of one or more TCI states. One or more configuration parameters 1720 may include configuration parameters for one or more TCI states. One or more TCI states among multiple TCI states may not be associated with an additional PCI index. One or more TCI states may not include an additional PCI index. Each of one or more TCI states may not include an additional PCI index. For example, based on one or more configuration parameters not indicating an additional PCI index for one or more TCI states among multiple TCI states, one or more TCI states may be associated with the cell and / or the cell's PCI. For example, based on one or more configuration parameters not indicating an additional PCI index for each of one or more TCI states, one or more TCI states may be associated with the cell and / or the cell's PCI. For example, based on one or more configuration parameters, at least one additional PCI index in an additional PCI index is not indicated for each of the one or more TCI states, and the one or more TCI states may be associated with the cell and / or the cell's PCI.

[0292] Wireless device 1705 can receive control commands 1730 (e.g., MAC-CE, DCI, downlink control commands / messages, control commands / messages, unified TCI state activation / deactivation of MAC CE, as described herein). Figure 17 (e.g., the activation command at time T1 described in the document). Control command 1730 can instruct the activation of a subset 1780a of multiple TCI states (e.g., DLorJoint-TCIStateList). Control command can instruct the activation of a second subset 1780 of a plurality of TCI states (e.g., ul-TCI-StateList).

[0293] The wireless device can map a subset of TCI states 1780a to one or more TCI code points 1780b. The wireless device can map a corresponding TCI state in the subset of TCI states 1780a to a corresponding TCI code point in one or more TCI code points 1780b. One or more TCI code points 1780b can indicate and / or include the subset of TCI states 1780a. Each TCI code point in one or more TCI code points 1780b can indicate and / or be mapped to a corresponding TCI state in the subset of TCI states 1780a. Each TCI code point in one or more TCI code points 1780b can indicate, include, and / or be mapped to one or more TCI states.

[0294] exist Figure 17 For example, TCI state subset 1780a may be TCI state 4, TCI state 5, TCI state 8, TCI state 26, TCI state 61, and TCI state 42. 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 indicate TCI state 4. The second TCI code point (e.g., TCI code point 001) may include and / or indicate TCI states 5 and 8. The third TCI code point (e.g., TCI code point 110) may include and / or indicate TCI states 26 and 61. The fourth TCI code point (e.g., TCI code point 111) may include and / or indicate TCI state 42. The first TCI code point (e.g., TCI code point 000) and the fourth TCI code point (e.g., TCI code point 111) indicate 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) indicate two TCI states (e.g., two joint TCI states, two uplink TCI states, two downlink TCI states, etc.).

[0295] The number of one or more TCI code points 1780b can be equal to one. One or more TCI code points 1780b can be a single TCI code point. A single TCI code point can indicate, include, and / or map to at least two TCI states among a plurality of TCI states 1770. A subset of TCI states 1780a can be at least two TCI states. For example, based on the fact that the number of one or more TCI code points 1780b is equal to one, the wireless device 1705 may not receive DCI 1740 indicating the activation of one or more TCI states in the subset of TCI states 1780a. Control command 1730 can indicate the activation of at least two TCI states. For example, based on control command 1730 indicating the activation of at least two TCI states, the wireless device 1705 may not receive DCI 1740 indicating the activation of one or more TCI states in the subset of TCI states 1780a. At least two TCI states may include a first TCI state (e.g., as described herein). Figure 17 The TCI state 26 described herein) and the second TCI state (e.g., as described herein) Figure 17 TCI state 61 as described in the document.

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

[0297] TCI code points can include, indicate, and / or map to at least two TCI states (e.g., as described in this article). Figure 17 The TCI states 26 and 61 described herein). TCI state subset 1780a may include at least two TCI states for the TCI code point. DCI 1740 may indicate the activation of at least two TCI states. The at least two TCI states may include a first TCI state (e.g., as described herein). Figure 17 The TCI state 26 described herein) and the second TCI state (e.g., as described herein) Figure 17 TCI state 61 as described in the document.

[0298] Figure 18 An example of TCI state activation is shown. Wireless device 1805 can receive first control commands 1820 (e.g., MAC-CE, DCI, downlink control commands / messages, control commands / messages, unified TCI state activation / deactivation MACCE, as described herein). Figure 18 The first control command 1820 can activate, select, indicate, update, and / or indicate the activation of a first subset 1870a of a plurality of TCI states 1770 (e.g., DLorJoint-TCIStateList). The first control command 1820 can also activate, select, indicate, update, and / or indicate the activation of a first subset 1870a of a second plurality of TCI states 1770 (e.g., UL-TCIStateList).

[0299] The first control 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. The first coreset pool index 1825 may, for example, be equal to zero. A first TCI state subset 1870a may be associated with the first coreset pool index 1825. For example, based on the first control command 1820 instructing the activation of the first TCI state subset 1870a, including the field having the first coreset pool index 1825, the first TCI state subset 1870a may be associated with the first coreset pool index 1825. The wireless device may activate the first TCI state subset 1870a for the first coreset pool index 1825.

[0300] Wireless device 1805 can map a first TCI state subset 1870a to one or more first TCI code points 1870b. Wireless device 1805 can map a corresponding TCI state in the first TCI state subset 1870a to a corresponding TCI code point in one or more first TCI code points 1870b. One or more first TCI code points 1870b can indicate and / or include the first TCI state subset 1870a. Each TCI code point in one or more first TCI code points 1870b can include, indicate, and / or be mapped to a corresponding TCI state in the first TCI state subset 1870a. Each TCI code point in one or more first TCI code points 1870b can include, indicate, and / or be mapped to one or more TCI states. One or more first TCI code points 1870b can be associated with a first coreset pool index 1825.

[0301] exist Figure 18For example, the first TCI state subset 1870a 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 indicate TCI state 4. The second TCI code point (e.g., TCI code point 001) may include and / or indicate TCI state 5. The third TCI code point (e.g., TCI code point 110) may include and / or indicate TCI state 26. The fourth TCI code point (e.g., TCI code point 111) may include and / or indicate 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.).

[0302] The number of one or more first TCI code points 1870b can be equal to one. One or more first TCI code points 1870b can be a single TCI code point. A single TCI code point can indicate a first TCI state among multiple TCI states. A subset of first TCI states 1870a can be a first TCI state. For example, based on the fact that the number of one or more first TCI code points 1870b is equal to one, the wireless device may not receive a DCI indicating the activation of one or more TCI states in the subset of first TCI states 1870a. For example, based on a first control command 1820 indicating the activation of a first TCI state, the wireless device 1805 may not receive a DCI indicating the activation of one or more TCI states in the subset of first TCI states 1870a.

[0303] The number of one or more first TCI code points 1870b can be greater than one. The wireless device 1805 can communicate via a first coreset 1838 (e.g., coreset pool index 0) having a first coreset 1838 pool index 1825 (e.g., coreset pool index 0). Figure 18 In coreset1) the first DCI 1830 (e.g., Figure 18The DCI at time T2 in the table is 1). Multiple coresets may include a first coreset 1838. One or more configuration parameters may indicate a first coreset pool index 1825 for the first coreset 1838. One or more configuration parameters may not indicate a coreset pool index for the first coreset 1838. For example, if one or more configuration parameters do not indicate a coreset pool index for the first coreset 1838, the first coreset 1838 may be associated with a first coreset pool index 1825 (e.g., coreset pool index 0). For example, if one or more configuration parameters do not indicate a coreset pool index for the first coreset 1838, the default value of the coreset pool index for the first coreset 1838 may be equal to the first coreset pool index 1825 (e.g., coreset pool index 0).

[0304] First DCI 1830 (e.g., as in this article) Figure 18 The DCI 1) mentioned above can be, for example, DCI format 1_1. The first DCI 1830 can be, for example, DCI format 1_2. The first DCI 1830 can be, for example, DCI format 1_x, with the condition x = 0, 1, 2 ... The first DCI 1830 can be, for example, DCI format 0_x, with the condition x = 0, 1, 2 ...

[0305] 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. For example, based on receiving the first DCI 1830 via a first coreset 1838 having a first coreset pool index 1825, 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. The value of the first TCI field 1835 (e.g., Figure 18 The value of the first TCI field 1835 (e.g., 110) can, for example, be equal to the first TCI code point. The value of the first TCI field 1835 can, for example, indicate the first TCI code point. The first TCI code point (e.g., 110) can indicate, include, and / or map to the first TCI state (e.g., Figure 18(TCI state 26 in the first coreset 1870a). The first TCI state subset 1870a may include the first TCI state. The first DCI 1830 may activate and / or indicate the activation of the first TCI state. The first DCI 1830 may indicate the activation of the first TCI state. For example, based on receiving the first DCI 1830 via a first coreset 1838 having a first coreset pool index 1825, the first TCI field 1835 in the first DCI 1830 may indicate the first TCI state in the first TCI state subset 1870a. For example, based on the first control command 1820 indicating the activation of the first TCI state subset 1870a, including a field having a first coreset pool index 1825 that may be the same as the first coreset pool index of the first coreset 1838, the first TCI field 1835 in the first DCI 1830 may indicate the first TCI state in the first TCI state subset 1870a.

[0306] The first TCI state can be associated with and / or activated for the first coreset pool index 1825. The first TCI state can be associated with downlink and / or uplink reception and / or transmission associated with the first coreset pool index 1825. For example, based on a first DCI 1830 activating the first TCI state via a first coreset 1838 having the first coreset pool index 1825, the first TCI state can be associated with downlink and / or uplink reception and / or transmission associated with the first coreset pool index 1825.

[0307] The wireless device can apply a first TCI state to downlink reception (e.g., PDSCH reception, transport block, PDCCH reception, CSI-RS, DM-RS, etc.) associated with a first coreset pool index 1825. One or more configuration parameters can indicate the first coreset pool index 1825 for a coreset among multiple coresets. For example, based on (e.g., in response to) one or more configuration parameters indicating the first coreset pool index 1825 for a coreset, the wireless device can monitor the downlink control channel in the coreset based on the first TCI state. The wireless device can receive DCI scheduling downlink signals (e.g., PDSCH transmission, transport block, DM-RS, CSI-RS, aperiodic CSI-RS) via a coreset having the first coreset pool index 1825. Multiple coresets can include coresets. For example, based on receiving DCI via a coreset having the first coreset pool index 1825, downlink signals can be associated with the first coreset pool index 1825. For example, based on (e.g., in response to) the association of a downlink signal with a first coreset pool index 1825, the wireless device can receive the downlink signal based on a first TCI state. For example, based on (e.g., in response to) one or more configuration parameters indicating the first coreset pool index 1825 for the downlink signal and / or a resource set including the downlink signal, the wireless device can receive the downlink signal (e.g., PDSCH transmission, transport block, DM-RS, CSI-RS, aperiodic CSI-RS) based on a first TCI state.

[0308] The wireless device may apply the first TCI state to uplink transmissions (e.g., PUSCH transmissions, transport blocks, PUCCH transmissions, SRS, etc.) associated with the first coreset pool index 1825.

[0309] One or more configuration parameters may indicate a first coreset pool index 1825 for uplink resources and / or a set and / or group of uplink resources including uplink resources. For example, based on (e.g., in response to) one or more configuration parameters indicating a first coreset pool index 1825 for uplink resources and / or a set and / or group of uplink resources including uplink resources, the radio device 1805 may transmit (e.g., transmit) uplink signals (e.g., UCI, HARQ-ACK, SR, CSI report, SRS) via uplink resources based on a first TCI state. The cell's uplink BWP (e.g., active uplink BWP) may include uplink resources. Uplink resources may be, for example, PUCCH resources. Uplink signals may be UCI (e.g., UCI, HARQ-ACK, SR, CSI report). Uplink resources may be, for example, SRS resources. Uplink signals may be SRS. Uplink resources may be, for example, PUSCH resources. Uplink signaling can be a PUSCH transport (e.g., a transport block) configured for uplink permission (e.g., type 1 configured uplink permission). For example, an uplink signaling transport via uplink resources can be associated with a first coreset pool index 1825, which is indicated for uplink resources and / or uplink resource sets and / or groups including uplink resources based on one or more configuration parameters.

[0310] Wireless device 1805 may receive DCI 1830, which triggers and / or schedules uplink signals (e.g., PUSCH transmission, transport block, SRS, HARQ-ACK), via coreset 1838 having a first coreset pool index 1825. Multiple coresets may be included. For example, based on receiving DCI 1830 via coreset 1838 having a first coreset pool index 1825, uplink signals may be associated with the first coreset pool index 1825. For example, based on (e.g., in response to) the association of uplink signals with the first coreset pool index 1825, wireless device may transmit (e.g., transmit) uplink signals based on a first TCI state.

[0311] Wireless device 1805 can receive second control commands 1840 (e.g., MAC-CE, DCI, downlink control commands / messages, control commands / messages, unified TCI state activation / deactivation of MAC CE, as described herein). Figure 18The second control command 1840 can activate, select, indicate, update, and / or indicate the activation of a second subset of TCI states 1880a in a plurality of TCI states (e.g., DLorJoint-TCIStateList). The second control command 1840 can also activate, select, indicate, update, and / or indicate the activation of a second subset of TCI states 1880a in a second plurality of TCI states (e.g., UL-TCIStateList).

[0312] The second control command 1840 may include having a second coreset pool index 1845 (e.g., ...). Figure 18 The field (e.g., CoresetPoolID) of the coreset pool index 1845. The value in the field can be equal to the second coreset pool index 1845. The second coreset pool index 1845 can, for example, be equal to one. The second TCI state subset 1880a can be associated with the second coreset pool index 1845. For example, based on the second control command 1840 instructing the activation of the second TCI state subset 1880a, including the field with the second coreset pool index 1845, the second TCI state subset 1880a can be associated with the second coreset pool index 1845. The wireless device can activate the second TCI state subset 1880a for the second coreset pool index 1845.

[0313] Wireless device 1805 can map a second TCI state subset 1880a to one or more second TCI code points 1880b. Wireless device 1805 can map a corresponding TCI state in the second TCI state subset 1880a to a corresponding TCI code point in one or more second TCI code points 1880b. One or more second TCI code points 1880b can indicate, include, and / or map to the second TCI state subset 1880a. Each TCI code point in one or more second TCI code points 1880b can include, indicate, and / or map to a corresponding TCI state in the second TCI state subset 1880a. Each TCI code point in one or more second TCI code points 1880b can include, indicate, and / or map to one or more TCI states. One or more second TCI code points 1880b can be associated with a second coreset pool index 1845.

[0314] exist Figure 18For example, the second TCI state subset 1880a 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 indicate TCI state 8. The second TCI code point (e.g., TCI code point 001) may include and / or indicate TCI state 61. The third TCI code point (e.g., TCI code point 110) may include and / or indicate TCI state 21. The first TCI code point (e.g., TCI code point 000), the second TCI code point (e.g., TCI code point 001), and the third TCI code point (e.g., TCI code point 110) may include and / or indicate a single TCI state (e.g., a single joint TCI state, a single uplink TCI state, a single downlink TCI state, etc.).

[0315] The number of one or more second TCI code points 1880b can be equal to one. One or more second TCI code points 1880b can be a single TCI code point. A single TCI code point can indicate a second TCI state among multiple TCI states. A subset of second TCI states 1880a can be a second TCI state. For example, based on the fact that the number of one or more second TCI code points 1880b is equal to one, the wireless device 1805 may not receive DCI 1850 indicating the activation of one or more TCI states in the subset of second TCI states 1880a. For example, based on the second control command 1840 indicating the activation of a second TCI state, the wireless device 1805 may not receive DCI 1850 indicating the activation of one or more TCI states in the subset of second TCI states 1880a.

[0316] The number of one or more second TCI code points 1880b can be greater than one. The wireless device 1805 can communicate via a second coreset 1858 (e.g., coreset pool index 1845) having a second coreset 1858 pool index 1845 (e.g., coreset pool index 1). Figure 18 Coreset2 in the middle) receives the second DCI 1850 (e.g., Figure 18 DCI 2 at time T4 in the middle. One or more configuration parameters can indicate the second coreset pool index 1845 for the second coreset 1858. Multiple coresets can include the second coreset 1858.

[0317] The second DCI 1850 can be, for example, DCI format 1_1. The second DCI 1850 can be, for example, DCI format 1_2. The second DCI 1850 can be, for example, DCI format 1_x, where x = 0, 1, 2... The second DCI 1850 can be, for example, DCI format 0_x, where x = 0, 1, 2... The second DCI 1850 can include a second TCI field 1855. The second TCI field 1855 can indicate a second TCI code point in one or more second TCI code points 1880b. For example, based on receiving the second DCI 1850 via a second coreset 1858 having a second coreset pool index 1845, the second TCI field 1855 can indicate a second TCI code point in one or more second TCI code points 1880b associated with the second coreset pool index 1845. The value of the second TCI field 1855 (e.g., Figure 18 The value of the second TCI field 1855 (e.g., 001) can, for example, be equal to the second TCI code point. The value of the second TCI field 1855 can, for example, indicate the second TCI code point. The second TCI code point (e.g., 001) can indicate, include, and / or map to the second TCI state (e.g., Figure 18 (TCI state 61 in the second coreset 1880a). The second TCI state subset 1880a may include the second TCI state. The second DCI 1850 may activate and / or indicate the activation of the second TCI state. The second DCI 1850 may indicate the activation of the second TCI state. For example, based on receiving the second DCI 1850 via the second coreset 1858 having the second coreset pool index 1845, the second TCI field 1855 in the second DCI 1850 may indicate the second TCI state in the second TCI state subset 1880a. For example, based on the second control command 1840 indicating the activation of the second TCI state subset 1880a, including a field of the second coreset pool index 1845 which may be the same as the second coreset pool index of the second coreset 1858, the second TCI field 1855 in the second DCI 1850 may indicate the second TCI state in the second TCI state subset 1880a.

[0318] The second TCI state can be associated with and / or activated for the second coreset pool index 1845. The second TCI state can be associated with downlink and / or uplink reception and / or transmission associated with the second coreset pool index 1845. For example, based on a second DCI 1850 that activates the second TCI state via a second coreset 1858 having the second coreset pool index 1845, the second TCI state can be associated with downlink and / or uplink reception and / or transmission associated with the second coreset pool index 1845.

[0319] Wireless device 1805 can apply a second TCI state to downlink reception (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 can indicate the second coreset pool index 1845 for a coreset among multiple coresets. For example, based on (e.g., in response to) one or more configuration parameters indicating the second coreset pool index 1845 for a coreset, wireless device 1805 can monitor the downlink control channel in the coreset based on the second TCI state. Wireless device 1805 can receive DCI scheduling downlink signals (e.g., PDSCH transmission, transport block, DM-RS, CSI-RS, aperiodic CSI-RS) via a coreset having the second coreset pool index 1845. Multiple coresets can include coresets. For example, based on receiving DCI via a coreset having the second coreset pool index 1845, downlink signals can be associated with the second coreset pool index 1845. For example, based on (e.g., in response to) the association of a downlink signal with a second coreset pool index 1845, the wireless device 1805 can receive the downlink signal based on a second TCI state. For example, based on (e.g., in response to) one or more configuration parameters indicating the second coreset pool index 1845 for the downlink signal and / or a resource set including the downlink signal, the wireless device 1805 can receive the downlink signal (e.g., PDSCH transmission, transport block, DM-RS, CSI-RS, aperiodic CSI-RS) based on a second TCI state.

[0320] The radio 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 can indicate the second coreset pool index 1845 for uplink resources and / or uplink resource sets and / or groups including uplink resources. For example, based on (e.g., in response to) one or more configuration parameters indicating the second coreset pool index 1845 for uplink resources and / or uplink resource sets and / or groups including uplink resources, the radio device 1805 can send (e.g., transmit) uplink signals (e.g., UCI, HARQ-ACK, SR, CSI report, SRS) via uplink resources based on the second TCI state. The cell's uplink BWP (e.g., active uplink BWP) can include uplink resources. Uplink resources can be, for example, PUCCH resources. Uplink signals can be UCIs (e.g., UCI, HARQ-ACK, SR, CSI report). Uplink resources can be, for example, SRS resources. Uplink semaphores can be SRS. Uplink resources can be, for example, PUSCH resources. Uplink semaphores can be PUSCH transports (e.g., transport blocks) configured for uplink permission (e.g., type 1 configured for uplink permission). For example, an uplink semaphore sent (e.g., transported) via an uplink resource can be associated with a second coreset pool index 1845, indicating an uplink resource and / or a set and / or group of uplink resources based on one or more configuration parameters for the uplink resource.

[0321] The wireless device 1805 can receive a DCI that triggers and / or schedules uplink signals (e.g., PUSCH transmission, transport block, SRS, HARQ-ACK) transmissions via a coreset having a second coreset pool index 1845. Multiple coresets can be included. For example, based on receiving a DCI via a coreset having a second coreset pool index 1845, the uplink signal can be associated with the second coreset pool index 1845. For example, based on (e.g., in response to) the uplink signal being associated with the second coreset pool index 1845, the wireless device can send (e.g., transmit) the uplink signal based on a second TCI state.

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

[0323] The first TCI state can be associated with the cell's PCI. The first TCI state may not include an additional PCI index from at least one additional PCI index. The additional PCI index may not be included in the configuration parameters of the first TCI state. One or more configuration parameters may include the configuration parameters of the first TCI state. For example, based on the fact that the first TCI state does not include an additional PCI index from at least one additional PCI index, the first TCI state can be associated with the cell's PCI. The first reference signal can be quasi-co-located with the first SS / PBCH block. The first reference signal can be the first SS / PBCH block. The first reference signal can be quasi-co-located with the first CSI-RS, and the first CSI-RS can be quasi-co-located with the first SS / PBCH block. The first SS / PBCH block can be associated with the cell. The first SS / PBCH block can be associated with the cell's PCI. One or more configuration parameters can indicate the first SS / PBCH block for the cell.

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

[0325] 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-co-address type (e.g., QCL Type A, QCL Type B, QCL Type C, QCL Type D). The second TCI state may be associated with the cell's PCI. The second TCI state may not include an additional PCI index from at least one additional PCI index. The additional PCI index may not be included in the configuration parameters of the second TCI state. One or more configuration parameters may include the configuration parameters of the second TCI state. For example, based on the fact that the second TCI state does not include an additional PCI index from at least one additional PCI index, the second TCI state may be associated with the cell's PCI. The second reference signal may be quasi-co-addressed 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-addressed with a second CSI-RS, and the second CSI-RS may be quasi-co-addressed with a second SS / PBCH block. The second SS / PBCH block may be associated with the cell. The second SS / PBCH block may be associated with the cell's PCI. One or more configuration parameters can indicate the second SS / PBCH block for a cell.

[0326] The second TCI state can be associated with the second PCI of the second cell. At least one of one or more cells can include the second cell. At least one PCI in and / or indicated by the PCI set list can include the second PCI. The second PCI can indicate (e.g., identify, etc.) the second cell. The second TCI state can include an additional PCI index in at least one additional PCI index. One or more configuration parameters can indicate an additional PCI index for the second TCI state. The additional PCI index can indicate a PCI set in the PCI set list. The PCI set can include and / or indicate the second PCI of the second cell. For example, based on the second TCI state including an additional PCI index indicating the second PCI of the second cell, the second TCI state can 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, the second TCI state can be associated with the second PCI of the second cell. The second reference signal can be quasi-co-located with the second SS / PBCH block. The second reference signal can be the second SS / PBCH block. The second reference signal can be quasi-co-located with the second CSI-RS, and the second CSI-RS can be quasi-co-located with the second SS / PBCH block. The second SS / PBCH block can be associated with the second cell. The second SS / PBCH block can be associated with the second PCI of the second cell. One or more configuration parameters can indicate the second SS / PBCH block for the second cell.

[0327] The second cell identified and / or indicated by the second PCI can be a non-serving cell. The second cell identified and / or indicated by the second PCI can be a neighboring cell. The second cell identified and / or indicated by the second PCI can be a candidate and / or secondary cell.

[0328] One or more configuration parameters can indicate a first TCI state index (e.g., tci-StateId) for a first TCI state. One or more configuration parameters can indicate a second TCI state index for a second TCI state. The first TCI state index can be lower than (e.g., less than) the second TCI state index. Multiple TCI state indices can include both the first and second TCI state indices.

[0329] A control command indicating the activation of a subset of TCI states may include multiple fields. A first field among these 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 control command. A second field among these 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 control command. The first octet may be lower than (e.g., less 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 sort the first and second TCI state indices based on their ordinal positions in the control command. The octet n of the control command may include a first TCI state index that identifies (e.g., indicates) a first TCI state, and the octet m of the control command may include a second TCI state index that identifies (e.g., indicates) a second TCI state, for example, if the condition is n < m.

[0330] Control commands can indicate, map, and / or activate sets, lists, and / or vectors of at least two TCI states to TCI code points. The control commands can indicate the mapping, association, and / or activation of sets, lists, and / or vectors of at least two TCI states to TCI code points. The at least two TCI states can include a first TCI state and a second TCI state. The first TCI state can occur first in the set, list, and / or vector of at least two TCI states. The first TCI state can be the first (e.g., start, earliest, initial, etc.) TCI state in the set, list, and / or vector of at least two TCI states. The second TCI state can occur second in the set, list, and / or vector of at least two TCI states. The second TCI state can be the last (e.g., latest, end, etc.) TCI state in the set, list, and / or vector of at least two TCI states. For example, if the set, list, and / or vector of at least two TCI states = [TCI state 5, TCI state 8], then the first TCI state can be TCI state 5, and the second TCI state can 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 can be TCI state 26, and the second TCI state can be TCI state 61.

[0331] A wireless device may apply a first TCI state to one or more first uplink channels and / or resources of a cell. Applying the first TCI state to one or more first uplink channels / resources may include transmitting (e.g., transmitting) uplink signals via one or more first uplink channels / resources based on the first TCI state. The wireless device may transmit (e.g., transmit) uplink signals via one or more first uplink channels and / or resources based on the first TCI state. The wireless device may transmit (e.g., transmit) a corresponding uplink signal in the uplink signals for each of the one or more first uplink channels and / or resources based on the first TCI state.

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

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

[0334] One or more first uplink channels and / or resources may include PUSCH. One or more first uplink channels and / or resources may include one or more first PUSCH resources. One or more first uplink channels and / or resources may include one or more first PUSCH transmissions.

[0335] Wireless device 1805 may receive a first DCI 1830, which schedules a first PUSCH transmission, via a first coreset 1838. Multiple coresets may include the first coreset 1838. The first DCI 1830 may include fields (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.) having a first value (e.g., 0, 00, 10, 11) indicating a first TCI state. Based on (e.g., in response to) the first DCI 1830 including the field with the first value indicating the first TCI state, the wireless device may send (e.g., transmit) a first PUSCH transmission based on the first TCI state. One or more first uplink channels and / or resources may include PUSCH transmissions scheduled by a DCI including the field with the first value. Each DCI may schedule one or more PUSCH transmissions in a PUSCH transmission.

[0336] The 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 the first coreset 1838. One or more configuration parameters may not indicate the coreset pool index for the first coreset 1838. For example, based on (e.g., in response to) receiving a first DCI 1830 that schedules a first PUSCH transmission via the first coreset 1838 having the first coreset pool index 1825, the wireless device may transmit (e.g., transmit) the first PUSCH transmission based on a first TCI state. One or more first uplink channels and / or resources may include the first PUSCH transmission. One or more first uplink channels and / or resources may include PUSCH transmissions scheduled by DCIs received via one or more first coresets having the 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 PUSCH transmission using a first transmission power determined based on the first TCI state. The wireless device 1805 can transmit (e.g., transmit) a first PUSCH transmission using a first spatial domain transmission filter / beam determined based on a first TCI state.

[0337] One or more configuration parameters may be configured to specify 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.) that has a first value (e.g., 0, 00, 10, 11) indicating a first TCI state for the configured uplink permission indication. For example, based on (e.g., in response to) one or more configuration parameters specifying a field that has a first value indicating a first TCI state for the configured uplink permission indication, the wireless device may transmit (e.g., transmit) a configured uplink-permitted PUSCH transmission based on the first TCI state. The configured uplink permission may be, for example, type 1 configured uplink permission. One or more first uplink channels and / or resources may include configured uplink-permitted PUSCH transmissions.

[0338] Wireless device 1805 may transmit (e.g., transmit) PUSCH transmissions configured for uplink permission using a first transmission power determined based on a first TCI state. Wireless device 1805 may also transmit (e.g., transmit) PUSCH transmissions configured for uplink permission using a first spatial domain transmission filter / beam determined based on the first TCI state.

[0339] 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 sets and / or groups of first PUCCH resources. One or more first uplink channels and / or resources may include one or more first PUCCH transmissions.

[0340] 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.) with a first value (e.g., 0, 00, 10, 11) indicating a first TCI status for the first PUCCH resource. 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 status for the first PUCCH resource, the wireless device may transmit (e.g., transmit) uplink signals (e.g., SR, HARQ-ACK, CSI report, uplink control information, PUCCH transmission) via the first PUCCH resource based on the first TCI status. One or more first uplink channels and / or resources may include PUCCH transmissions via the first PUCCH resource.

[0341] The wireless device may transmit (e.g., transmit) uplink signals via the first PUCCH resource using a first transmission power determined based on the first TCI state. The wireless device may also transmit (e.g., transmit) uplink signals via the first PUCCH resource using a first spatial domain transmission filter / beam determined based on the first TCI state.

[0342] One or more configuration parameters may indicate fields (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.) with a first value (e.g., 0, 00, 10, 11) indicating a first TCI status for the first PUCCH resource set and / or group. For example, based on (e.g., in response to) one or more configuration parameters indicating fields with a first value indicating a first TCI status for the first PUCCH resource set and / or group, the wireless device may transmit (e.g., transmit) uplink signals (e.g., SR, HARQ-ACK, CSI report, uplink control information) via PUCCH resources in the first PUCCH resource set and / or group based on the first TCI status. 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 first PUCCH resource set and / or group, the wireless device can transmit (e.g., transmit) corresponding uplink signals (e.g., SR, HARQ-ACK, CSI report, uplink control information) via each PUCCH resource in the first PUCCH resource set and / or group based on the first TCI state. One or more first uplink channels and / or resources may include PUCCH transmissions via each PUCCH resource in the first PUCCH resource set and / or group.

[0343] The wireless device may transmit (e.g., transmit) uplink signals via PUCCH resources using a first transmission power determined based on a first TCI state. The wireless device may also transmit (e.g., transmit) uplink signals via PUCCH resources using a first spatial domain transmission filter / beam determined based on the first TCI state.

[0344] The wireless device can receive a first DCI 1830 via a first coreset 1838 that triggers and / or schedules a first PUCCH transmission (e.g., a HARQ-ACK feedback transmission). The first DCI 1830 can, for example, schedule PDSCH reception. The first DCI 1830 can, for example, indicate Scell ​​pausing. The first DCI 1830 can, for example, indicate SPS PDSCH release. The first DCI 1830 can, for example, indicate activation of a unified TCI state. Multiple coresets may include the first coreset 1838. The first DCI 1830 may include, for example, 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.) having a first value (e.g., 0, 00, 10, 11) indicating the first TCI state. For example, based on (e.g., in response to) a first DCI 1830 including a field having a first value indicating a first TCI state, a wireless device may send (e.g., transmit) a first PUCCH transmission based on the first TCI state. One or more first uplink channels and / or resources may include PUCCH transmissions triggered and / or scheduled by a DCI including a field having a first value.

[0345] The 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 the first coreset 1838. One or more configuration parameters may not indicate a coreset pool index for the first coreset 1838. For example, based on (e.g., in response to) receiving 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, the wireless device may send (e.g., transmit) a first PUCCH transmission based on a first TCI state. One or more first uplink channels and / or resources may include PUCCH transmissions triggered and / or scheduled by DCIs received via one or more first coresets having the first coreset pool index 1825. Multiple coresets may include one or more first coresets.

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

[0347] One or more first uplink channels and / or resources may include 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 sets and / or groups of first SRS resources. One or more first uplink channels and / or resources may include one or more first SRS transmissions.

[0348] One or more configuration parameters may indicate a field for the first SRS resource having a first value (e.g., 0) indicating 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.). For example, based on (e.g., in response to) one or more configuration parameters indicating a field for the first SRS resource having a first value indicating a first TCI state, the wireless device may transmit (e.g., transmit) SRS via the first SRS resource based on the first TCI state. One or more first uplink channels and / or resources may include SRS transmissions via the first SRS resource.

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

[0350] One or more configuration parameters may indicate fields (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.) with a first value (e.g., 0, 00, 10, 11) indicating a first TCI status for the first SRS resource set and / or group. For example, based on (e.g., in response to) one or more configuration parameters indicating fields with a first value indicating a first TCI status for the first SRS resource set and / or group, the wireless device may transmit (e.g., transmit) an SRS via an SRS resource in the first SRS resource set and / or group based on the first TCI status. For example, based on (e.g., in response to) one or more configuration parameters indicating fields with a first value indicating a first TCI status for the first SRS resource set and / or group, the wireless device may transmit (e.g., transmit) a corresponding SRS via each SRS resource in the first SRS resource set and / or group based on the first TCI status. One or more first uplink channels and / or resources may include SRS transmissions via each SRS resource in a first SRS resource set and / or group.

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

[0352] 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, an aperiodic 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., SRS resource set indicator field, TRP field, coreset pool index field, additional PCI index, BFD set index, unified TCI status indicator field, federated TCI status indicator field, uplink TCI status indicator field, panel index, capability set index, etc.) having a first value (e.g., 0, 00, 10, 11) indicating a first TCI state. For example, based on (e.g., in response to) the first DCI 1830 including fields with a first value indicating a first TCI state, wireless device 1805 may send (e.g., transmit) an SRS based on the first TCI state. One or more first uplink channels and / or resources may include SRS transmissions triggered and / or scheduled by a DCI that includes a field having a first value.

[0353] The 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 the first coreset 1838. One or more configuration parameters may not indicate a coreset pool index for the first coreset 1838. For example, based on (e.g., in response to) receiving a first DCI 1830 that triggers and / or schedules an SRS transmission via the first coreset 1838 having the first coreset pool index 1825, the wireless device may transmit (e.g., transmit) an SRS based on a first TCI state. One or more first uplink channels and / or resources may include SRS transmissions triggered and / or scheduled by DCIs received via one or more first coresets having the first coreset pool index 1825. Multiple coresets may include one or more first coresets.

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

[0355] A wireless device may apply a first TCI state to one or more first downlink channels / resources of a cell (e.g., use the first TCI state thereon). 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. A wireless device may receive downlink signals via one or more first downlink channels / resources based on the first TCI state. A wireless device may receive a corresponding downlink signal in the downlink signals of each of the one or more first downlink channels / resources based on the first TCI state.

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

[0357] One or more first downlink channels / resources may be / include PDSCH. 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.

[0358] A wireless device can receive a first DCI that schedules a first PDSCH reception via a first coreset. Multiple coresets may include a 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 status indicator field, joint TCI status indicator field, uplink TCI status indicator field, panel index, capability set index, etc.) having a first value (e.g., 0, 00, 10, 11) indicating a first TCI state. Based on (e.g., in response to) the first DCI including fields with the first value indicating the first TCI state, the wireless device can receive / perform a first PDSCH reception based on the first TCI state. One or more first downlink channels / resources may be / include PDSCH receptions scheduled by DCI messages including fields with the first value. Each DCI message in the DCI messages may schedule one or more PDSCH receptions in the PDSCH receptions.

[0359] A first coreset may be associated with a first coreset pool index (e.g., CoresetPoolIndex = 0). For example, one or more configuration parameters may indicate the first coreset pool index for the first coreset. Alternatively, one or more configuration parameters may not indicate the coreset pool index for the first coreset. The radio device may receive / perform a first PDSCH reception based on a first TCI state. For example, the radio device may receive / perform a first PDSCH reception based on (e.g., in response to) a first DCI that schedules the first PDSCH reception via (e.g., with the first coreset pool index). One or more first downlink channels / resources may be / include the first PDSCH reception. One or more first downlink channels / resources may be / include PDSCH receptions scheduled by DCIs (e.g., DCI messages) received via one or more first coresets with the first coreset pool index. Multiple coresets may include one or more first coresets.

[0360] The wireless device can receive the first PDSCH reception using a first spatial domain receive / receive filter / beam determined based on the first TCI state. At least one first DMRS antenna port of the first PDSCH reception can be co-located with a first reference signal (e.g., quasi-reference) indicated by the first TCI state.

[0361] One or more configuration parameters may configure fields for the SPS PDSCH that have a first value (e.g., 0, 00, 10, 11) indicating 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 radio device may receive / perform PDSCH reception configured for the SPS PDSCH / configured for the SPS PDSCH based on the first TCI state. For example, based on (e.g., in response to) one or more configuration parameters configuring fields for the SPS PDSCH that have a first value indicating a first TCI state, the radio device may receive / perform PDSCH reception configured for the SPS PDSCH / configured for the SPS PDSCH. One or more first downlink channels / resources may be / include PDSCH transmissions configured for the SPS PDSCH / configured for the SPS PDSCH.

[0362] The wireless device can receive PDSCH reception using a first spatial domain receive / receive filter / beam determined based on a first TCI state. At least one first DMRS antenna port of the PDSCH reception (and / or each PDSCH reception in the PDSCH reception) can be co-located with a first reference signal (e.g., quasi-) indicated by the first TCI state.

[0363] One or more first downlink channels / resources may be / include PDCCH. One or more first downlink channels / resources may be / include one or more first PDCCH resources. One or more first downlink channels / resources may be / include one or more sets / groups of first PDCCH resources. One or more first downlink channels / resources may be / include one or more first PDCCH receptions. One or more first downlink channels / resources may be / include one or more first coresets. Multiple coresets may include one or more first coresets.

[0364] One or more configuration parameters may indicate fields (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 the first coreset having a first value (e.g., 0, 00, 10, 11) indicating the first TCI status. The radio device may receive / perform downlink signals (e.g., DCI, PDCCH reception, PDCCH reception with / carrying DCI) via the first coreset based on the first TCI status. For example, based on (e.g., in response to) one or more configuration parameters indicating fields with a first value indicating the first TCI status for the first coreset, the radio device may receive / perform downlink signals via the first coreset. One or more first downlink channels / resources may be / include PDCCH reception via the first coreset. One or more first coresets may include the first coreset.

[0365] One or more configuration parameters may indicate fields (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.) with a first value (e.g., 0, 00, 10, 11) indicating a first TCI state for the first coreset group. The first coreset group may include one or more first coresets from a plurality of coresets. The radio device may receive / execute downlink signals (e.g., DCI, PDCCH reception) via the first coreset in the first coreset group based on the first TCI state. For example, based on (e.g., in response to) one or more configuration parameters indicating fields with a first value indicating a first TCI state for the first coreset group, the radio device may receive / execute downlink signals via the first coreset. The radio device may receive / execute corresponding downlink signals (e.g., DCI, PDCCH reception) via each coreset in the first coreset group 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 first coreset group, the wireless device can receive / execute a corresponding downlink signal. One or more first downlink channels / resources may be / included PDCCH reception via each coreset in the first coreset group.

[0366] The wireless device can receive downlink signals using a first spatial domain receive / receive filter / beam determined based on a first TCI state. At least one first DMRS antenna port of the downlink signal can be co-located with a first reference signal (e.g., quasi-reference) indicated by the first TCI state.

[0367] A first coreset may be associated with a first coreset pool index (e.g., CoresetPoolIndex = 0). For example, one or more configuration parameters may indicate the first coreset pool index for the first coreset. For example, one or more configuration parameters may not indicate the coreset pool index for the first coreset (e.g., default coreset pool index = 0). For example, in response to the association of a first coreset with a first coreset pool index, a wireless device may receive / perform a first PDCCH reception (e.g., DCI, or include / carry / have DCI) via the first coreset based on a first TCI state. One or more first downlink channels / resources may be / include PDCCH reception via one or more first coresets having the first coreset pool index. Multiple coresets may include one or more first coresets. One or more first coresets may include a first coreset.

[0368] The wireless device can receive the first PDCCH reception using a first spatial domain receive / receive filter / beam determined based on the first TCI state. At least one first DMRS antenna port of the first PDCCH reception can be quasi-co-located with a first reference signal indicated by the first TCI state.

[0369] In the example, 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 sets / groups of first CSI-RS resources. One or more first downlink channels / resources may be / include one or more first CSI-RS receptions.

[0370] One or more configuration parameters may indicate a field for the first CSI-RS resource that has a first value (e.g., 0) indicating the 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 radio device may receive CSI-RS via the first CSI-RS resource based on the first TCI state. For example, based on (e.g., in response to) one or more configuration parameters indicating a field for the first CSI-RS resource that has a first value indicating the first TCI state, the radio device may receive CSI-RS via the first CSI-RS resource. One or more first downlink channels / resources may be / include CSI-RS reception via the first CSI-RS resource.

[0371] One or more configuration parameters may indicate fields (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.) with a first value (e.g., 0, 00, 10, 11) for the first CSI-RS resource set / group. The radio device may receive CSI-RS v...

Claims

1. A method comprising: The wireless device receives one or more configuration parameters of the cell, wherein the one or more configuration parameters include: A list of non-periodic trigger states configured for non-periodic Channel State Information (CSI) reports; and Physical downlink shared channel (PDSCH) configuration parameters, which include the unified transport configuration indicator (TCI) status reference parameters that indicate the reference bandwidth portion (BWP) of the reference cell; Receive downlink control information (DCI) including a CSI request field, wherein the CSI request field indicates an aperiodic trigger state configuration in the aperiodic trigger state configuration list, and wherein the aperiodic trigger state configuration includes: At least one TCI status identifier indicating at least one TCI status indicated by downlink or joint TCI status list parameters of the reference BWP of the reference cell; and Resource set parameters, which indicate one or more reference signals; Based on the at least one TCI state indicated by the at least one TCI state identifier, receive the one or more reference signals; and Transmit a CSI report indicating the quality of one or more radio links for the one or more reference signals.

2. The method of claim 1, wherein each TCI status identifier in the at least one TCI status identifier indicates a corresponding TCI status in the at least one TCI status, and The CSI report includes the corresponding radio link quality for each of the one or more reference signals, which is part of the one or more radio link qualities.

3. The method according to any one of claims 1 or 2, wherein receiving the one or more reference signals includes measuring the radio link quality of the one or more reference signals.

4. The method according to any one of claims 1 to 3, wherein each of the one or more reference signals is received via a corresponding TCI state in the at least one TCI state indicated by the at least one TCI state identifier, and Each of the one or more reference signals is quasi-co-located with a reference signal indicated by the corresponding TCI state in the at least one TCI state indicated by the at least one TCI state identifier.

5. The method according to any one of claims 1 to 4, wherein the resource set parameter indicates a CSI reference signal (CSI-RS) resource set, and The one or more reference signals mentioned therein are one or more aperiodic CSI-RS.

6. The method according to any one of claims 1 to 5, wherein the DCI is configured to trigger the transmission of aperiodic CSI reports, and The one or more reference signals mentioned therein are associated with the cell.

7. The method according to any one of claims 1 to 6, wherein the unified TCI state reference parameter exists in the PDSCH configuration parameter, and the PDSCH configuration parameter does not include downlink or joint TCI state addition or modification parameters of the cell.

8. The method according to any one of claims 1 to 7, wherein the PDSCH configuration parameters include downlink or joint TCI state list parameters, and the PDSCH configuration parameters do not include TCI state list parameters, and The downlink or joint TCI status list parameters include the unified TCI status reference parameters.

9. The method according to any one of claims 1 to 8, wherein the unified TCI state reference parameter comprises: A cell index that identifies the reference cell; as well as The BWP index identifies the reference BWP.

10. The method according to any one of claims 1 to 9, further comprising: The wireless device receives one or more second configuration parameters of the reference cell, wherein the one or more second configuration parameters include: A second aperiodic trigger state configuration list for aperiodic CSI reports associated with the reference cell; and The PDSCH configuration parameters of the reference cell include the downlink or joint TCI status list parameters of the reference BWP of the reference cell; Receive a second DCI including a second CSI request field, wherein the second CSI request field indicates a second aperiodic trigger state configuration in the second aperiodic trigger state configuration list, and wherein the second aperiodic trigger state configuration includes: At least one second TCI state identifier, indicating at least one second TCI state indicated by the downlink or joint TCI state list parameters of the reference BWP of the reference cell; and The second resource set parameter indicates one or more second reference signals; Based on the at least one second TCI state indicated by the at least one second TCI state identifier, receive the one or more second reference signals; and Transmit a second CSI report indicating the quality of one or more radio links of the one or more second reference signals.

11. The method according to any one of claims 1 to 9, further comprising: The wireless device receives one or more second configuration parameters from the second cell, wherein the one or more second configuration parameters include: A second aperiodic trigger state configuration list for aperiodic CSI reports associated with the second cell; and The second cell's PDSCH configuration parameters include the TCI status list parameters of the second cell but exclude downlink or joint TCI status list parameters; Receive a second DCI including a second CSI request field, wherein the second CSI request field indicates a second aperiodic trigger state configuration in the second aperiodic trigger state configuration list, and wherein the second aperiodic trigger state configuration includes: At least one second TCI status identifier, indicating at least one second TCI status indicated by the TCI status list parameters of the second cell; and The second resource set parameter indicates one or more second reference signals; Based on the at least one second TCI state indicated by the at least one second TCI state identifier, receive the one or more second reference signals; and Transmit a second CSI report indicating the quality of one or more radio links of the one or more second reference signals.

12. The method of claim 11, wherein the TCI status list parameters of the second cell include TCI status addition or modification parameters for the second cell, and The downlink or joint TCI status list parameters of the reference BWP of the reference cell include the downlink or joint TCI status addition or modification parameters of the reference BWP of the reference cell.

13. A wireless device, comprising: One or more processors; as well as A memory that stores instructions, which, when executed by the one or more processors, cause the wireless device to perform the method according to any one of claims 1 to 12.

14. A system comprising: A wireless device configured to perform the method according to any one of claims 1 to 12; as well as A base station configured to transmit the one or more configuration parameters.

15. A computer-readable medium storing instructions that, when executed, cause a wireless device to perform the method according to any one of claims 1 to 12.

Images