Beam management in multiple transmission and reception points

Abstract

A wireless device may communicate with a base station. A list of cells may be provided for a group of cells for simultaneous transmission of configuration indication updates (e.g., TCI updates). For example, if the wireless device receives a control command indicating that a transmission configuration indication state of one or more transmission / reception points of a plurality of transmission / reception points of a cell in a simultaneous transmission configuration indication update list is activated, the transmission configuration indication state of the plurality of transmission / reception points is updated. If so, the wireless device may switch from a multiple transmit / receive point mode (e.g., a multiple TRP mode) to a single transmit / receive point mode. For example, if the simultaneous transmission configuration indicates that a second cell in an update list is not served by at least one of the one or more transmission / reception points, the wireless device may switch from a multiple transmission / reception point mode to a single transmission / reception point mode.

Description

[0001] Cross-reference to related applications

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 422,750, filed on November 4, 2022. The above-referenced application is hereby incorporated by reference in its entirety. Background Art

[0003] The wireless device communicates with the base station based on a transmission configuration indicator (TCI) state. Summary of the Invention

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

[0005] A wireless device may communicate with a base station. A list of simultaneous transmission configuration indication update (e.g., TCI update) cells may be provided for a cell group. For example, if the wireless device receives a control command indicating activation of a transmission configuration indication state for one or more transmission / reception points among a plurality of transmission / reception points for cells in the simultaneous transmission configuration indication update list, the wireless device may switch from a multiple transmission / reception point mode (e.g., multiple TRP mode) to a single transmission / reception point mode. For example, if a second cell in the simultaneous transmission configuration indication update list is not served by at least one of the one or more transmission / reception points, the wireless device may switch from the multiple transmission / reception point mode to the single transmission / reception point mode. For example, the wireless device may not use the transmission configuration indication state for cells in the simultaneous transmission configuration indication update list that are not associated with at least one of the one or more transmission / reception points. The wireless device may use the transmission configuration indication state for cells (e.g., each cell) in the simultaneous transmission configuration indication update list that are associated with at least one of the one or more transmission / reception points.

[0006] These and other features and advantages are described in more detail below. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

[0013] Figure 4B An example format of a Medium Access Control (MAC) subheader in a MAC protocol data unit (PDU) is shown.

[0014] Figure 5A An example mapping of downlink channels is shown.

[0015] Figure 5B An example mapping of uplink channels is shown.

[0016] Figure 6 Example radio resource control (RRC) states and RRC state transitions are shown.

[0017] Figure 7 An example configuration of a frame is shown.

[0018] Figure 8 Example resource configurations for one or more carriers are shown.

[0019] Figure 9 An example configuration of a bandwidth part (BWP) is shown.

[0020] Figure 10A An example component carrier based carrier aggregation configuration is shown.

[0021] Figure 10B Example cell groups are shown.

[0022] Figure 11A Example mappings of one or more synchronization signal / physical broadcast channel (SS / PBCH) blocks are shown.

[0023] Figure 11B Example mappings of one or more channel state information reference signals (CSI-RS) are 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 example four-step random access procedure is shown.

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

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

[0029] Figure 14A An example of a control resource set (CORESET) configuration is shown.

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

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

[0032] Figure 15B Shown are example elements of a computing device that may be used to implement any of the various means described herein.

[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 simultaneous beam management is shown.

[0037] Figure 20 An example of simultaneous beam management is shown.

[0038] Figure 21 An example method of simultaneous beam management is shown.

[0039] Figure 22 An example of beam application is shown.

[0040] Figure 23 An example of beam application is shown.

[0041] Figure 24 An example method of beam application is shown.

[0042] Figure 25A and Figure 25B An example of SRS resource set mapping is shown. DETAILED DESCRIPTION

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

[0044] Figure 1A An example communication network 100 is shown. Communication network 100 may comprise a mobile communication network. Communication network 100 may comprise, 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 wireless devices 106. Communication network 100 may include one or more data networks (DNs) 108, and / or devices within communication network 100 may communicate with the one or more data networks (e.g., via CN 102). Wireless devices 106 may communicate with one or more DNs 108, such as public DNs (e.g., the Internet), private DNs, and / or intra-operator DNs. Wireless devices 106 may communicate with the one or more DNs 108 via RAN 104 and / or CN 102. CN 102 may provide / configure one or more interfaces for wireless devices 106 to interface with the one or more DNs 108. As part of the interface functionality, the CN 102 may set up an end-to-end connection between the wireless device 106 and the one or more DNs 108, authenticate the wireless device 106, provide / configure charging functionality, and the like.

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

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

[0047] The RAN 104 may include one or more base stations (not shown). As used herein, the term "base station" may include one or more of the following: a base station, a node, a Node B (NB), an evolved Node B (eNB), a gNB, an ng-eNB, a relay node (e.g., an integrated access and backhaul (IAB) node), a donor node (e.g., a donor eNB, a donor gNB, etc.), an access point (e.g., a Wi-Fi access point), a transmission and reception point (TRP), a computing device, a device capable of wireless communication, or any other device capable of sending and / or receiving signals. A base station may include one or more of each of the elements listed above. For example, a base station may include one or more TRPs. As other non-limiting examples, a base station may include, for example, one or more of: a Node B (e.g., associated with Universal Mobile Telecommunications System (UMTS) and / or third generation (3G) standards), an evolved Node B (eNB) (e.g., associated with Evolved Universal Terrestrial Radio Access (E-UTRA) and / or fourth generation (4G) standards), a remote radio head (RRH), a baseband processing unit coupled to one or more remote radio heads (RRHs), a relay node or relay node for extending the coverage area of ​​a donor node, a next generation evolved Node B (ng-eNB), a second generation Node B (gNB) (e.g., associated with NR and / or 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 base station, 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)).

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

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

[0050] The 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 transmit power. The 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, a small cell base station can be used to provide / configure a small coverage area, e.g., a coverage area that overlaps with a relatively larger coverage area provided / configured by another base station (e.g., a macrocell base station). The small coverage area can be provided / configured in areas with high data traffic (or so-called "hotspots") or in areas with weak macrocell coverage. Examples of small cell base stations can include (in descending order of coverage area) microcell base stations, picocell base stations, and femtocell base stations or home base stations.

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

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

[0053] The CN 152 (e.g., 5G-CN) may provide / configure one or more interfaces for wireless devices 156 to interface with one or more DNs 170 (e.g., public DNs (e.g., the internet), private DNs, and / or intra-carrier DNs). As part of this interface functionality, the CN 152 (e.g., 5G-CN) may set up end-to-end connections between the wireless device 156 and the one or more DNs, authenticate the wireless device 156, and / or provide / configure charging functionality. The CN 152 (e.g., 5G-CN) may have a service-based architecture that may differ from other CNs (e.g., 3GPP 4G CNs). The architecture of a node of the CN 152 (e.g., 5G-CN) may be defined as a network function that provides services to other network functions via interfaces. The network functions of the CN 152 (e.g., 5G CN) can be implemented in a number of ways, for example, as network elements on dedicated or shared hardware, as software instances running on dedicated or shared hardware, and / or as virtualized functions instantiated on a platform (e.g., a cloud-based platform).

[0054] The CN 152 (e.g., 5G-CN) may include an access and mobility management function (AMF) device 158A and / or a user plane function (UPF) device 158B, which may be separate components or a single component AMF / UPF device 158. The UPF device 158B may serve as a gateway between the RAN 154 (e.g., NG-RAN) and the one or more DNs 170. The UPF device 158B may perform functions such as packet routing and forwarding, packet inspection and user plane policy rule enforcement, traffic usage reporting, uplink classification to support routing of traffic flows to the one or more DNs 170, user plane quality of service (QoS) processing (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink traffic verification), downlink packet buffering, and / or downlink data notification triggering. The UPF device 158B may serve as an anchor point for intra- / inter-radio access technology (RAT) mobility, an external protocol (or packet) data unit (PDU) session point interconnecting with the one or more DNs, and / or a branch point supporting multi-homed PDU sessions. The wireless device 156 may be configured to receive services via a PDU session, which may be a logical connection between the wireless device and a DN.

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

[0056] CN 152 (e.g., 5G-CN) may be included in Figure 1B One or more additional network functions that may not be shown in the figure. The CN 152 (e.g., 5G-CN) may include one or more devices that implement at least one of the following: a session management function (SMF), an NR repository function (NRF), a policy control function (PCF), a network exposure function (NEF), a unified data management (UDM), an application function (AF), an authentication server function (AUSF), and / or any other functions.

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

[0058] A base station (e.g., gNB 160 and / or ng-eNB 162) may be connected to CN 152 (e.g., 5G CN) via a first interface (e.g., NG interface) and to other base stations via a second interface (e.g., Xn interface). The NG and Xn interfaces may be established using direct physical connections and / or indirect connections through an underlying transport network (e.g., an Internet Protocol (IP) transport network). A base station (e.g., gNB 160 and / or ng-eNB 162) may communicate with wireless device 156 via a third interface (e.g., Uu interface). A base station (e.g., gNB 160A) may communicate with wireless device 156A via a Uu interface. The NG, Xn, and Uu interfaces may be associated with protocol stacks. The protocol stacks associated with the interfaces may be provided by Figure 1B The network elements shown in FIG. 1 are used to exchange data and signaling messages. A protocol stack may include two planes: a user plane and a control plane. Any other number of planes (e.g., within a protocol stack) may be used. The user plane may process data of interest to users. The control plane may process signaling messages of interest to network elements.

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

[0060] A wireless device may access a base station via an interface (e.g., a Uu interface) for user plane and control plane configuration. A base station (e.g., gNB 160) may provide user plane and control plane protocol terminals to wireless device 156 via the Uu interface. A base station (e.g., gNB 160A) may provide user plane and control plane protocol terminals to wireless device 156A via the Uu interface associated with a first protocol stack. A base station (e.g., ng-eNB 162) may provide Evolved UMTS Terrestrial Radio Access (E UTRA) user plane and control plane protocol terminals (e.g., where E UTRA may refer to 3GPP 4G radio access technology) to wireless device 156 via the Uu interface. A base station (e.g., ng-eNB 162B) may provide E UTRA user plane and control plane protocol terminals to wireless device 156B via the Uu interface associated with a second protocol stack. 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, and the like.

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

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

[0063] Figure 1A The communication network 100 and / or Figure 1BThe communication network 150 in the present disclosure may include any quantity and / or type of devices, such as computing devices, wireless devices, mobile devices, handsets, tablets, laptops, Internet of Things (IoT) devices, hotspots, cellular repeaters, computing devices, and / or more generally, user equipment (e.g., UE). Although reference may be made herein to one or more of the aforementioned types of devices (e.g., UE, wireless device, computing device, etc.), it should be understood that any device herein may include any one or more of the aforementioned types of devices or similar devices. The communication network and any other networks mentioned herein may include an LTE network, a 5G network, a satellite network, and / or any other network for wireless communication (e.g., any 3GPP network and / or any non-3GPP network). The apparatus, 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, but it should be understood that one or more features and steps may be implemented in any device and / or any network.

[0064] Figure 2A An example user plane configuration is shown. The user plane configuration may include, for example, the NR user plane protocol stack. Figure 2B An example control plane configuration is shown. The control plane configuration may include, for example, an NR control plane protocol stack. One or more of the user plane configuration and / or the control plane configuration may utilize 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 in can be used with e.g. Figure 1B The protocol stack of the Uu interface between the wireless device 156A and the base station 160A shown in FIG. 1 is substantially the same or similar.

[0065] The user plane configuration (e.g., NR user plane protocol stack) may be included in the wireless device 210 and the base station 220 (e.g., Figure 2AThe protocol stack may include multiple layers (e.g., five layers or any other number of layers) implemented in a physical layer (e.g., five layers or any other number of layers) (as shown). At the bottom of the protocol stack, physical layers (PHY) 211 and 221 may provide transport services to higher layers of the protocol stack and may correspond to Layer 1 of the Open Systems Interconnection (OSI) model. Protocol layers above PHY 211 may include a media access control layer (MAC) 212, a radio link control layer (RLC) 213, a packet data convergence protocol layer (PDCP) 214, and / or a service data application protocol layer (SDAP) 215. Protocol layers above PHY 221 may include a media access control layer (MAC) 222, a radio link control layer (RLC) 223, a packet data convergence protocol layer (PDCP) 224, and / or a service data application protocol layer (SDAP) 225. One or more of the four protocol layers above PHY 211 may correspond to Layer 2, or the data link layer, of the OSI model. One or more of the four protocol layers above PHY 221 may correspond to Layer 2, or the data link layer, of the OSI model.

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

[0067] PDCP (e.g. Figure 2A and Figure 3 The PDCPs 214 and 224 (shown in FIG) 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, encryption / decryption to prevent unauthorized decoding of data transmitted (e.g., sent) over the air interface, and / or integrity protection (e.g., to ensure that control messages originate from the intended source). The PDCPs 214 and 224 can also perform retransmission of undelivered packets, in-sequence delivery and reordering of packets, and / or removal of duplicate packets received due to, for example, handovers (e.g., intra-gNB handovers). The PDCPs 214 and 224 can also perform packet duplication, for example, to increase the likelihood that a packet will be received. The receiver can receive packets repeatedly and remove any duplicate packets. Packet duplication can be used for certain services, such as those requiring high reliability.

[0068] The PDCP layer (e.g., PDCP 214 and 224) may perform mapping / demapping between separate radio bearers and RLC channels (e.g., RLC channel 330) (e.g., in dual connectivity scenarios / configurations). Dual connectivity may refer to a technology that allows a wireless 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 as a service for SDAP 215 and 225) is handled by a cell group in dual connectivity, a separate bearer may be configured and / or used. PDCP 214 and 224 may perform mapping / demapping between the separate radio bearer and the RLC channel 330 belonging to the cell group.

[0069] 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 noted functions, for example, based on the transmission mode in which the RLC layer is operating. The RLC configuration can be specific to each logical channel. The RLC configuration may not depend on a parameter set and / or a transmission time interval (TTI) duration (or other duration). The RLC layer (e.g., RLC 213 and 223) can provide / configure RLC channels as services to the PDCP layer (e.g., PDCP 214 and 224, respectively), such as Figure 3 shown.

[0070] The MAC layer (e.g., MAC 212 and 222) may perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. Multiplexing may include multiplexing data units / data portions belonging to one or more logical channels into transport blocks (TBs) delivered to the PHY layer (e.g., PHY 211 and 221, respectively), while demultiplexing may include demultiplexing data units / data portions from TBs 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 handling between wireless 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 prioritize logical channels between wireless device 210 via logical channel prioritization and / or padding. The MAC layer (e.g., MAC 212 and 222) may support one or more parameter sets and / or transmission timings. Mapping restrictions in logical channel prioritization may control the parameter sets and / or transmission timings that may be used by logical channels. The MAC layer (e.g., MAC 212 and 222) may provide / configure logical channels 340 as services for the RLC layer (e.g., RLC 213 and 223).

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

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

[0073] For example, if SDAP 225 receives three IP packets (or other number of IP packets) from one or more QoS flows and maps the three packets (or other number of packets) to radio bearers (e.g., radio bearers 402 and 404), then 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. SDAP header (in Figure 4A Each SDAP SDU shown in FIG is marked with an "H" before it) can be added to an IP packet to generate an SDAP PDU, which can be called a PDCP SDU. A data unit transmitted from / to a higher protocol layer can be called a service data unit (SDU) of a lower protocol layer, and a data unit transmitted to / from a lower protocol layer can be called a protocol data unit (PDU) of a higher protocol layer. Figure 4A As shown, the data units from SDAP 225 may be SDUs of the lower protocol layer PDCP 224 (eg, PDCP SDUs), and may be PDUs of SDAP 225 (eg, SDAP PDUs).

[0074] Each protocol layer (e.g. Figure 4A ) or at least some of the protocol layers may: perform their own functions (e.g., Figure 3 ), adds the corresponding header, and / or forwards 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 segmentation (e.g., as Figure 4A RLC 223 may forward its output (e.g., two RLC PDUs, which are two MAC SDUs generated by adding corresponding subheaders to two SDU segments (SDU segments)) to MAC 222. MAC 222 may multiplex a certain number of RLC PDUs (MAC SDUs). MAC 222 may attach a MAC subheader to the RLC PDU (MAC SDU) to form a TB. The MAC subheader may be distributed over the MAC PDU (e.g., as shown in FIG. 1 ). Figure 4AThe NR configuration shown in Figure 2 shows a MAC subheader located entirely at the beginning of the MAC PDU (e.g., in an LTE configuration). For example, if the MAC PDU subheader is calculated before assembling the full MAC PDU, the NR MAC PDU structure can reduce processing time and / or associated latency.

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

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

[0077] Figure 5A An example mapping of downlink channels is shown. The mapping of uplink channels may include mapping between downlink channels (eg, logical channels, transport channels, and physical channels). Figure 5BAn example mapping of uplink channels is shown. The mapping of uplink channels may include mappings between uplink channels (e.g., logical channels, transport channels, and physical channels). Information may be passed through / via channels between the RLC, MAC, and PHY layers of a protocol stack (e.g., an NR protocol stack). Logical channels may be used between the RLC and MAC layers. Logical channels may be categorized / indicated as control channels (e.g., in the NR control plane) that may carry control and / or configuration information, or traffic channels (e.g., in the NR user plane) that may carry data. Logical channels may be categorized / indicated as dedicated logical channels that may be dedicated to a specific radio device, and / or common logical channels that may be used by more than one radio device (e.g., a group of radio devices).

[0078] Logical channels can be defined by the type of information they carry. A set of logical channels (e.g., in a NR configuration) can include one or more channels described below. The Paging Control Channel (PCCH) can contain or carry one or more paging messages used to page wireless devices whose locations are unknown to the network at the cell level. The Broadcast Control Channel (BCCH) can contain or carry system information messages in the form of a Master Information Block (MIB) and several System Information Blocks (SIBs). Wireless devices can use system information messages to obtain information about how a cell is configured and how to operate within the cell. The Common Control Channel (CCCH) can contain or carry control messages associated with random access. The Dedicated Control Channel (DCCH) can contain or carry control messages to or from a specific wireless device to configure the wireless device with configuration information. The Dedicated Traffic Channel (DTCH) can contain or carry user data to or from a specific wireless device.

[0079] Transport channels can be used between the MAC and PHY layers. Transport channels can be defined by how the information they carry is sent / transmitted (e.g., via the air interface). The set of transport channels (e.g., defined by the NR configuration or any other configuration) can include one or more of the following channels. The Paging Channel (PCH) can contain / carry paging messages from the PCCH. The Broadcast Channel (BCH) can contain / carry the MIB from the BCCH. The Downlink Shared Channel (DL-SCH) can contain / carry downlink data and signaling messages, including the SIB from the BCCH. The Uplink Shared Channel (UL-SCH) can contain / carry uplink data and signaling messages. The Random Access Channel (RACH) can provide wireless devices with access to the network without any previous scheduling.

[0080] The PHY layer can use physical channels to communicate / transmit information between processing layers within the PHY layer. A physical channel may have an associated set of time-frequency resources for carrying information about one or more transport channels. The PHY layer may generate control information to support lower-layer operations of the PHY layer. The PHY layer may provide / transmit control information to lower layers of the PHY layer via physical control channels (e.g., referred to as L1 / L2 control channels). The set of physical channels and physical control channels (e.g., which may be defined by the NR configuration or any other configuration) may include one or more of the following channels: The Physical Broadcast Channel (PBCH) may include / carry the MIB from the BCH. The Physical Downlink Shared Channel (PDSCH) may include / carry downlink data and signaling messages from the DL-SCH, as well as paging messages from the PCH. The Physical Downlink Control Channel (PDCCH) may include / carry downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling grants, and uplink power control commands. The physical uplink shared channel (PUSCH) may contain / carry uplink data and signaling messages from the UL-SCH, and in some cases may contain uplink control information (UCI) as described below. The physical uplink control channel (PUCCH) may contain / 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) may be used for random access.

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

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

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

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

[0085] Figure 6 Example RRC states and RRC state transitions are shown. 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 device 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). The RRC inactive state 604 can be when the RRC is connected but inactive.

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

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

[0088] A previously established RRC context may be maintained for the wireless device. This may occur, for example, during an RRC inactive state. During the RRC inactive state (e.g., RRC inactive state 604), the previously established RRC context may be maintained in the wireless device and the base station. Maintaining the RRC context may enable / allow a faster transition to the RRC connected state (e.g., RRC connected 602) with reduced signaling overhead compared to a transition from an RRC idle state (e.g., RRC idle 606) to an RRC connected state (e.g., RRC connected 602). During the RRC inactive state (e.g., RRC inactive state 604), the wireless device may be in a sleep state, and the wireless device's mobility may be managed / controlled by the wireless device via cell reselection. The RRC state may transition from the RRC inactive state (e.g., RRC inactive state 604) to the RRC connected state (e.g., RRC connected 602) via a connection resumption procedure 614. The RRC state may transition from an RRC inactive state (eg, RRC inactive state 604 ) to an RRC idle state (eg, RRC idle 606 ) via a connection release procedure 616 , which may be the same as or similar to the connection release procedure 608 .

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

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

[0091] RAN areas can be used to track wireless devices (e.g., the location of wireless devices at the RAN level). For wireless devices in an RRC inactive state (e.g., RRC inactive state 604), a RAN notification area can be assigned / provisioned / configured to the wireless device. A RAN notification area can include one or more cell identities (e.g., an 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. For example, if a wireless device moves (e.g., via cell reselection) to a cell that is not included in the RAN notification area assigned / provisioned / configured to the wireless device, the wireless device can perform a notification area update with the RAN to update the RAN notification area of ​​the wireless device.

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

[0093] Base stations (e.g. Figure 1B The gNB 160 (or any other base station in the NR) 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., a base station distributed unit such as a gNB DU). The base station central unit (CU) can be coupled to one or more base station distributed units (DUs) using an F1 interface (e.g., the F1 interface defined in NR configurations). The base station CU can include the RRC, PDCP, and SDAP layers. The base station distributed unit (DU) can include the RLC, MAC, and PHY layers.

[0094] Physical signals and physical channels (e.g. Figure 5A and Figure 5BThe data (e.g., an Orthogonal Frequency Division Multiplexing (OFDM) symbol in an NR configuration or any other symbol) 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 sends / 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 Quadrature Amplitude Modulation (M-QAM) symbols or M Phase Shift Keying (M-PSK) symbols, or any other modulated symbol), and divided into F parallel symbol streams, for example, before data transmission. The F parallel symbol streams can be viewed as if they were in the frequency domain. The F parallel symbols can be used as input to an Inverse Fast Fourier Transform (IFFT) block, which 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 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 may form a single OFDM symbol. The OFDM symbol provided / output by the IFFT block may be sent / transmitted over the air interface on a carrier frequency, for example, after one or more processes (e.g., adding a cyclic prefix) and up-conversion. For example, a Fast Fourier Transform (FFT) block may be used to mix the F parallel symbol streams before being processed by the IFFT block. This operation may produce a Discrete Fourier Transform (DFT) precoded OFDM symbol and may be used by one or more wireless devices in the uplink to reduce the Peak to Average Power Ratio (PAPR). The FFT block may be used at the receiver to perform inverse processing on the OFDM symbol to recover the data mapped to the source symbol.

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

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

[0097] A slot may have a fixed number of OFDM symbols (e.g., 14 OFDM symbols). Parameter sets with higher subcarrier spacing may have shorter slot durations and more slots per subframe. Figure 7 An example of parameter set related slot duration and per-subframe slot transmission structure is shown in ( Figure 7 (The numerology with 240 kHz subcarrier spacing is not shown in Figure 2.) A subframe (e.g., in NR configurations) can be used as a numerology-independent time reference. A slot can be used as the unit for scheduling uplink and downlink transmissions. Scheduling (e.g., in NR configurations) can be decoupled from the slot duration. Scheduling can start at any OFDM symbol. Scheduling can last for as many symbols as required for the transmission, e.g., to support low latency. These partial slot transmissions can be referred to as mini-slots or sub-slot transmissions.

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

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

[0100] The configuration of one or more bandwidth parts (BWPs) can support one or more wireless devices that are unable to receive the full carrier bandwidth. BWPs can support bandwidth adaptation, for example, for such wireless devices that cannot receive the full carrier bandwidth. A BWP (e.g., a BWP in an NR configuration) can be defined by a subset of contiguous RBs on a carrier. A wireless device can be configured (e.g., via the RRC layer) with one or more downlink BWPs per serving cell and one or more uplink BWPs per serving cell (e.g., up to four downlink BWPs per serving cell and up to four uplink BWPs per serving cell). One or more of the configured BWPs for a 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 a serving cell is configured with a secondary uplink carrier, the serving cell may have one or more first active BWPs in the uplink carrier and one or more second active BWPs in the secondary uplink carrier.

[0101] A downlink BWP from a set of configured downlink BWPs can be linked with an uplink BWP from a set of configured uplink BWPs (e.g., for unpaired spectrum). For example, if the downlink BWP index of the downlink BWP and the uplink BWP index of the uplink BWP are the same, then the downlink BWP can be linked with the uplink BWP. 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).

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

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

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

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

[0106] 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. The one or more conditions may include at least one of the following: the wireless device detects DCI indicating an active downlink BWP other than the default downlink BWP for paired spectrum operation; the wireless device detects DCI indicating an active downlink BWP other than the default downlink BWP for unpaired spectrum operation; and / or the wireless device detects DCI indicating an active uplink BWP other than the default uplink BWP for unpaired spectrum operation. For example, if the wireless device does not detect DCI during a time interval (e.g., 1 ms or 0.5 ms), the wireless device may start / run the BWP inactivity timer nearing expiration (e.g., increasing from zero to the BWP inactivity timer value, or decreasing from the BWP inactivity timer value to zero). For example, if the BWP inactivity timer expires, the wireless device may switch from the active downlink BWP to the default downlink BWP.

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

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

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

[0110] For example, if a wireless device is configured for a secondary cell with a default downlink BWP and timer value from a set of configured downlink BWPs, the wireless device's procedures for switching BWPs on the secondary cell may be the same / similar to those on the primary cell. The wireless device can use the timer values ​​and default downlink BWP for the secondary cell in the same / similar manner as the wireless device uses the timer values ​​and / or default BWP for the primary cell. The timer value (e.g., BWP inactivity timer) can be configured for each cell (e.g., for one or more BWPs), for example, via RRC signaling or any other signaling. One or more active BWPs can be switched to another BWP, for example, based on the expiration of the BWP inactivity timer.

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

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

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

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

[0115] For example, the SCell configured for the wireless device may be activated or deactivated based on traffic and channel conditions. Deactivation of the SCell may cause the wireless device to stop receiving PDCCH and PDSCH on the SCell and transmitting PUSCH, SRS, and CQI on the SCell. For example, MAC CEs (e.g., Figure 4B The MAC CE may activate or deactivate the configured SCells. The MAC CE may use a bitmap (e.g., one bit per SCell) to indicate which SCells (e.g., within a subset of the configured SCells) for the wireless device are activated or deactivated. For example, the configured SCells may be deactivated based on (e.g., after or in response to) the expiration of an SCell deactivation timer (e.g., one SCell deactivation timer per SCell may be configured).

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

[0117] Figure 10B An example cell group is shown. Aggregated cells may be configured into one or more PUCCH groups (e.g., Figure 10BAs 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 the PUCCH group 1050 may be configured as a PUCCH SCell (or PSCell) 1061 (e.g., a UL SCC), SCell 1062 (e.g., a UL SCC), and SCell 1063 (e.g., a UL SCC). UCI associated with the downlink CCs of the PUCCH group 1010 may be transmitted / transmitted via the uplink of the PCell 1021 (e.g., via the PUCCH of the PCell 1021), as shown as UCI 1031, UCI 1032, and UCI 1033. UCI associated with the downlink CCs of the PUCCH group 1050 may be transmitted / transmitted via the uplink of the PUCCH SCell (or PSCell) 1061 (e.g., via the PUCCH of the PUCCH SCell 1061), as shown as UCI 1071, UCI 1072, and UCI 1073. For example, if Figure 10B If the aggregated cells shown in FIG are not divided into PUCCH group 1010 and PUCCH group 1050, a single uplink PCell can be configured to send / transmit UCI associated with six downlink CCs. For example, if UCI 1031, 1032, 1033, 1071, 1072, and 1073 are sent / transmitted via PCell 1021, PCell 1021 may become overloaded. By dividing the transmission of UCI between PCell 1021 and PUCCH SCell (or PSCell) 1061, overload can be prevented and / or reduced.

[0118] 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 cell including a downlink carrier and optionally an uplink carrier may be assigned a physical cell ID and a cell index. The physical cell ID or cell index may indicate / identify the downlink carrier and / or 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) sent / transmitted via a downlink component carrier. The cell index may be determined, for example, using one or more RRC messages. The physical cell ID may be referred to as a carrier ID, and the cell index may be referred to as a carrier index. A first physical cell ID for a first downlink carrier may refer to the first physical cell ID of a cell including the first downlink carrier. Substantially the same / similar concepts may apply, for example, to carrier activation. Activation of a first carrier may refer to activation of a cell including the first carrier.

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

[0120] For the downlink, a base station may send / transmit (e.g., unicast, multicast, and / or broadcast) one or more reference signals (RSs) (e.g., PSS, SSS, CSI-RS, DM-RS, and / or PT-RS) to one or more wireless devices. For the uplink, the one or more wireless devices may send / transmit one or more RSs (e.g., DM-RS, PT-RS, and / or SRS) to the base station. The PSS and SSS may be sent / transmitted by the base station and used by the one or more wireless devices to synchronize with the base station. A synchronization signal (SS) / physical broadcast channel (PBCH) block may contain the PSS, SSS, and PBCH. The base station may periodically send / transmit bursts of SS / PBCH blocks, which may be referred to as SSBs.

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

[0122] 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 may be sent / transmitted first and may span, for example, 1 OFDM symbol and 127 subcarriers. The SSS may be sent / transmitted after the PSS (for example, two symbols later) and may span 1 OFDM symbol and 127 subcarriers. The PBCH may be sent / transmitted after the PSS (for example, across the next 3 OFDM symbols) and may span 240 subcarriers (for example, after 1 OFDM symbol). Figure 11A ) and / or may span fewer than 240 subcarriers (e.g., in the second and fourth OFDM symbols shown). Figure 11A in the third OFDM symbol shown).

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

[0124] A wireless device may use SS / PBCH blocks to determine one or more parameters of a cell. For example, the wireless device may determine the physical cell identifier (PCI) of the cell based on the sequences of the PSS and SSS, respectively. For example, the wireless device may determine the location of the cell's frame boundary based on the location of the SS / PBCH blocks. The SS / PBCH blocks may indicate that they have been sent / transmitted according to a transmission mode. The SS / PBCH blocks in the transmission mode may be at a known distance from the frame boundary (e.g., a predefined distance configured by the RAN between one or more networks, one or more base stations, and one or more wireless devices).

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

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

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

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

[0129] 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 a 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 indicate to the wireless device that CSI-RS resources in a CSI-RS resource set are activated and / or deactivated.

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

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

[0132] Downlink DM-RS may be sent / transmitted by a base station and received / used by wireless devices for channel estimation. Downlink DM-RS may be used for coherent demodulation of one or more downlink physical channels (e.g., PDSCH). A network (e.g., an NR network) may support one or more variable and / or configurable DM-RS patterns for data demodulation. At least one downlink DM-RS configuration may support a front-loaded DM-RS pattern. Front-loaded DM-RS may be mapped to one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). A base station may semi-statically configure a wireless device with a certain number / number (e.g., a maximum number / number) of front-loaded DM-RS symbols for PDSCH. A DM-RS configuration may support one or more DM-RS ports. A DM-RS configuration may support up to eight orthogonal downlink DM-RS ports per wireless device (e.g., for single-user MIMO). A DM-RS configuration may support up to four orthogonal downlink DM-RS ports per wireless device (e.g., for multi-user MIMO). The radio network may support a common DM-RS structure for downlink and uplink (e.g., at least for CP-OFDM). The DM-RS positions, DM-RS patterns, and / or scrambling sequences may be the same or different. The base station may, for example, use the same precoding matrix to send / transmit the downlink DM-RS and the corresponding PDSCH. The wireless device may use the one or more downlink DM-RSs for coherent demodulation / channel estimation of the PDSCH.

[0133] A transmitter (e.g., a base station's transmitter) may use a precoder matrix for a portion of a transmission bandwidth. The transmitter may use a first precoder matrix for a first bandwidth and a second precoder matrix for a second bandwidth. For example, the first precoder matrix and the second precoder matrix may be different because the first bandwidth is different from the second bandwidth. The wireless device may assume that the same precoding matrix is ​​used across a group of PRBs. The group of PRBs may be determined / indicated / identified / represented as a precoding resource block group (PRG).

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

[0135] For example, a wireless device may send / transmit uplink DM-RS to a base station for channel estimation. The base station may use the uplink DM-RS for coherent demodulation of one or more uplink physical channels. The wireless device may send / transmit the uplink DM-RS using the PUSCH and / or PUCCH. The uplink DM-RS may span a frequency range similar to the frequency range associated with the corresponding physical channel. The base station may configure one or more uplink DM-RS configurations for the wireless device. At least one DM-RS configuration may support a front-loaded DM-RS pattern. The front-loaded DM-RS may be mapped to one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). The one or more uplink DM-RS may be configured to be sent / transmitted on one or more symbols of the PUSCH and / or PUCCH. The base station may semi-statically configure the wireless device with a certain number / number (e.g., a maximum number / number) of front-loaded DM-RS symbols for the PUSCH and / or PUCCH, which the wireless device may use to schedule single-symbol DM-RS and / or dual-symbol DM-RS. A network (e.g., an NR network) may support a common DM-RS structure for downlink and uplink (e.g., for cyclic prefix orthogonal frequency division multiplexing (CP-OFDM)). The DM-RS positions, DM-RS patterns, and / or scrambling sequences of the DM-RSs may be substantially the same or different.

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

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

[0138] Antenna ports can be determined / defined such that the channel over which a symbol on the same antenna port is transmitted can be inferred from the channel over which another symbol on the same antenna port is transmitted. For example, if a first symbol and a second symbol are sent / 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 port from the channel used to transmit the first symbol on the antenna port. For example, if one or more large-scale properties of the channel over which the first symbol on the first antenna port is transmitted can be inferred from the channel over which the second symbol on the second antenna port is transmitted, the first and second antenna ports can be referred to as quasi-co-located (QCLed). The one or more large-scale properties may include at least one of the following: delay spread; Doppler spread; Doppler shift; average gain; average delay; and / or spatial receive (Rx) parameters.

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

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

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

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

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

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

[0145] 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) may be executed. Procedure U1 may be used to enable a base station to perform measurements on a wireless device's Tx beams (e.g., to support selection of one or more Tx beams for the wireless device and / or Rx beams for the base station). The Tx beams of the wireless device and the Rx beams of the base station are shown as ovals in the top row of U1 and the bottom row of U3, respectively. Beamforming (e.g., at the wireless device) may include one or more beam sweeps, such as Tx beam sweeps from a set of beams (shown as ovals rotating clockwise, indicated by dashed arrows, in the bottom row of U1 and U3). Beamforming (e.g., at the base station) may include one or more beam sweeps, such as Rx beam sweeps from a set of beams (shown as ovals rotating counterclockwise, indicated by dashed arrows, in the top row of U1 and U2). For example, if a wireless device (e.g., a UE) uses fixed transmit beams, procedure U2 can be used to enable the base station to adjust its transmit beams. The wireless device and / or base station can perform procedure U2, for example, to use a smaller set of beams than those used in procedure P1, or to use narrower beams than those used in procedure P1. Procedure U2 can be referred to as beam refinement. For example, if the base station uses fixed transmit beams, the wireless device can perform procedure U3 to adjust its transmit beams.

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

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

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

[0149] Figure 13AAn example four-step random access procedure is shown. The four-step random access procedure may include a four-step contention-based random access procedure. A base station may, for example, send / transmit a configuration message 1310 to a wireless device before initiating the random access procedure. The four-step random access procedure may include the transmission of four messages: 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.

[0150] Configuration message 1310 may be sent / transmitted, for example, using one or more RRC messages. The one or more RRC messages may indicate one or more random access channel (RACH) parameters to the wireless device. The one or more RACH parameters may include at least one of: common parameters (e.g., RACH-configGeneral) for one or more random access procedures; cell-specific parameters (e.g., RACH-ConfigCommon); and / or dedicated parameters (e.g., RACH-configDedicated). The base station may send / transmit (e.g., broadcast or multicast) the one or more RRC messages to one or more wireless devices. The one or more RRC messages may be wireless device-specific. The one or more wireless device-specific RRC messages may be, for example, dedicated RRC messages sent / transmitted to wireless devices in an RRC connected (e.g., RRC_CONNECTED) state and / or an RRC inactive (e.g., RRC_INACTIVE) state. The wireless device may determine time-frequency resources and / or uplink transmission power for transmitting the first message (e.g., Msg 1 1311) and / or the third message (e.g., Msg 3 1313) based on the one or more RACH parameters. The wireless device may determine, for example, reception timing and a 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.

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

[0152] The one or more RACH parameters provided / configured / included in the configuration message 1310 may be used to determine the uplink transmission power of the first message (e.g., Msg 1 1311) and / or the third message (e.g., Msg 3 1313). The one or more RACH parameters may indicate a reference power for preamble transmission (e.g., a received target power and / or initial power for the preamble transmission). One or more power offsets may be present, as indicated by the one or more RACH parameters. The one or more RACH parameters may indicate: a power ramp step; a power offset between the SSB and the CSI-RS; a power offset between the transmission of the first message (e.g., Msg 1 1311) and the third message (e.g., Msg 3 1313); and / or a power offset value between preamble groups. The one or more RACH parameters may indicate one or more thresholds, e.g., based on which the wireless device may determine at least one reference signal (e.g., SSB and / or CSI-RS) and / or uplink carrier (e.g., normal uplink (NUL) carrier and / or supplemental uplink (SUL) carrier).

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

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

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

[0156] A 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 (e.g., after or in response to) the transmission / transmission of the first message (e.g., Msg 1 1311). The second message (e.g., Msg 2 1312) may be scheduled on the DL-SCH and may be indicated by the PDCCH, 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 wireless device's transmission timing), a scheduling grant for transmitting a 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 opportunity used by the wireless device to send / transmit the first message (e.g., Msg 1 1311) (e.g., a preamble). The wireless device may begin the time window one or more symbols after the last symbol of the first message (e.g., Msg 1 1311) containing the preamble (e.g., the symbol in which the transmission of the first message (Msg 1 1311) containing the preamble is completed or the first PDCCH opportunity following the end of the preamble transmission). The one or more symbols may be determined based on a parameter set. The PDCCH may be mapped in a common search space (e.g., Type 1-PDCCH common search space) configured by an RRC message. The wireless device may identify / determine the RAR based on, for example, the RNTI. The Radio Network Temporary Identifier (RNTI) may be used based on one or more events that initiate / start a random access procedure. The wireless device may use the RA-RNTI, for example, for one or more communications associated with random access or any other purpose. The RA-RNTI may be associated with the PRACH opportunity in which the wireless device sent / transmitted the preamble. The wireless device may determine the RA-RNTI based on, for example, at least one of: an OFDM symbol index; a slot index; a frequency domain index; and / or a UL carrier indicator of the PRACH opportunity. An example RA-RNTI may be determined as follows:

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

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

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

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

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

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

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

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

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

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

[0167] The wireless device may start / initiate a two-step random access procedure for licensed spectrum and / or unlicensed spectrum (e.g., Figure 13C ). The wireless device may determine whether to start / initiate the two-step random access procedure based on one or more factors. The one or more factors may include at least one of: the radio access technology being used (e.g., LTE, NR, etc.); whether the wireless device has a valid TA; cell size; RRC state of the wireless device; spectrum type (e.g., licensed vs. unlicensed); and / or any other suitable factors.

[0168] The wireless device may determine 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 the two-step RACH parameters included in configuration message 1330. The RACH parameters may indicate the MCS, time-frequency resources, and / or power control used for preamble 1341 and / or transport block 1342. The time-frequency resources used to transmit preamble 1341 (e.g., PRACH) and the time-frequency resources used to transmit transport block 1342 (e.g., PUSCH) may be multiplexed using FDM, TDM, and / or CDM. The RACH parameters may enable the wireless device to determine the reception timing and downlink channel used to monitor and / or receive the second message (e.g., Msg B 1332).

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

[0170] A wireless device and a base station may 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 the MAC layer (e.g., Layer 2) of the wireless device or base station. This control signaling may include downlink control signaling sent / transmitted from the base station to the wireless device and / or uplink control signaling sent / transmitted from the wireless device to the base station.

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

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

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

[0174] A base station may send / transmit DCI using one or more DCI formats, for example, depending on the purpose and / or content of the DCI. DCI format 0_0 may be used to schedule the PUSCH in a cell. DCI format 0_0 may be a fallback DCI format (e.g., having a compact DCI payload). DCI format 0_1 ​​may be used to schedule the PUSCH in a cell (e.g., having a larger DCI payload than DCI format 0_0). DCI format 1_0 may be used to schedule the PDSCH in a cell. DCI format 1_0 may be a fallback DCI format (e.g., having a compact DCI payload). DCI format 1_1 may be used to schedule the PDSCH in a cell (e.g., having a larger DCI payload than DCI format 1_0). DCI format 2_0 may be used to provide a slot format indication to a group of wireless devices. DCI format 2_1 may be used to notify / inform a group of wireless devices of physical resource blocks and / or OFDM symbols, wherein the group of wireless devices may assume that no transmissions are intended for them. 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 transmissions of one or more wireless devices. DCI formats for new functionality may be defined in future releases. DCI formats can have different DCI sizes or can share the same DCI size.

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

[0176] Figure 14AAn example of a core set configuration is shown. A core set configuration can be used for a portion of a bandwidth or any other frequency band. A base station can send / transmit DCI via the PDCCH on one or more control resource sets (core sets). A core set may contain time-frequency resources that a wireless device attempts to decode DCI using one or more search spaces. The base station can configure the size and location of the core sets in the time-frequency domain. First core sets 1401 and second core sets 1402 may appear or be configured at the first symbol in a time slot. First core set 1401 may overlap with second core set 1402 in the frequency domain. Third core set 1403 may appear or be configured at the third symbol in a time slot. Fourth core set 1404 may appear or be configured at the seventh symbol in a time slot. Core sets may have different numbers of resource blocks in the frequency domain.

[0177] 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 (e.g., to provide frequency diversity) or non-interleaved (e.g., to facilitate interference coordination and / or frequency-selective transmission of control channels). A base station can perform different or identical CCE-to-REG mapping on different CORESETs. A CORESET can be associated with a CCE-to-REG mapping (e.g., via RRC configuration). A CORESET can be configured with an antenna port QCL parameter. The antenna port QCL parameter can indicate QCL information for DM-RS received via the CORESET's PDCCH.

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

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

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

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

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

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

[0184] Figure 15A An example communication between a wireless device and a base station is shown. 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 Figure 1B The communication network 150 shown in FIG. 1 or any other communication network. A communication network may include more than one wireless device and / or more than one base station, with Figure 15A The base stations are configured substantially the same or similarly to those shown in FIG.

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

[0186] For the downlink, data to be sent from the base station 1504 to the wireless device 1502 may be provided / transmitted / sent to the processing system 1508 of the base station 1504. The data may be provided / transmitted / sent to the processing system 1508 via, for example, the core network. For the uplink, data to be sent from the wireless device 1502 to the base station 1504 may be provided / transmitted / sent to the processing system 1518 of the wireless device 1502. The processing system 1508 and the processing system 1518 may implement layer 3 and layer 2 OSI functions to process data for transmission. Layer 2 may include, for example, information about Figure 2A 、 Figure 2B 、 Figure 3 and Figure 4A The SDAP layer, PDCP layer, RLC layer and MAC layer described in the previous section may be included in the following sections: Figure 2B Describes the RRC layer.

[0187] Data to be transmitted 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 transmitted 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 system 1510 and transmission processing system 1520 may implement layer 1 OSI functions. Layer 1 may include, for example, information regarding Figure 2A 、 Figure 2B 、 Figure 3 and Figure 4AFor transport processing, the PHY layer may perform, for example, forward error correction coding of transport channels, interleaving, rate matching, mapping of transport channels to physical channels, modulation of physical channels, and multiple-input multiple-output (MIMO) or multi-antenna processing.

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

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

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

[0191] The processing system 1508 and / or the processing system 1518 may include one or more controllers and / or one or more processors. The one or more controllers and / or one or more processors may include, for example, a general-purpose processor, a digital signal processor (DSP), a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) and / or other programmable logic device, discrete gate and / or transistor logic, discrete hardware components, on-board units, or any combination thereof. The processing system 1508 and / or the processing system 1518 may perform at least one of signal encoding / processing, data processing, power control, input / output processing, and / or any other functionality that may enable the wireless device 1502 and / or the base station 1504 to operate in a wireless environment.

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

[0193] Figure 15B1504, wireless devices 106, 156A, 156B, 210, and / or 1502, or any other base station, wireless device, AMF, UPF, network device, or computing device described herein. Computing device 1530 may include one or more processors 1531 that can execute instructions stored in random access memory (RAM) 1533, removable media 1534 (e.g., a universal serial bus (USB) drive, a compact disk (CD) or digital versatile disk (DVD), or a floppy disk drive), or any other desired storage medium. Instructions may also be stored in an attached (or internal) hard drive 1535. Computing device 1530 may also include a security processor (not shown) that can execute instructions from one or more computer programs to monitor processes executing on processor 1531 and any processes requesting access to any hardware and / or software components of computing device 1530 (e.g., ROM 1532, RAM 1533, removable media 1534, hard drive 1535, device controller 1537, network interface 1539, GPS 1541, Bluetooth interface 1542, WiFi interface 1543, etc.). Computing device 1530 may include one or more output devices, such as a display 1536 (e.g., a screen, display device, monitor, television, etc.), and 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, touch screen, microphone, etc. Computing device 1530 may also include one or more network interfaces (e.g., network interface 1539), which may be wired, wireless, or a combination of both. Network interface 1539 can provide an interface for computing device 1530 to communicate with network 1540 (e.g., a RAN or any other network). Network interface 1539 can include a modem (e.g., a cable modem), and external network 1540 can 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. In addition, computing device 1530 can include a location detection device, such as a global positioning system (GPS) microprocessor 1541, which can be configured to receive and process global positioning signals and determine the geographic location of computing device 1530, possibly with the help of an external server and antenna.

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

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

[0196] Figure 16B An example structure for modulating and upconverting 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) for an antenna port and / or a complex-valued physical random access channel (PRACH) baseband signal. For example, filtering can be performed / applied prior to transmission.

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

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

[0199] A wireless device may receive one or more messages (e.g., RRC messages) from a base station containing configuration parameters for multiple cells (e.g., a primary cell and one or more secondary cells). The wireless device may communicate with at least one base station (e.g., two or more base stations in dual connectivity) via the multiple cells. The one or more messages (e.g., as part of the configuration parameters) may include 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, and RRC layers and / or communication channels.

[0200] For example, a timer may begin running once started and continue running until it is stopped or expires. For example, if the timer is not running, the timer may be started, or if it is running, the timer may be restarted. A timer may be associated with a value (e.g., a timer may be started or restarted at a certain value, or may be started from zero and expire upon reaching the value). For example, the timer duration may not be updated until the timer is stopped or expires (e.g., due to a BWP handover). A timer may be used to measure a time period / window for a procedure. Regarding embodiments and / or procedures related to one or more timers or other parameters, it should be understood that there may be a variety of ways to implement the one or more timers or other parameters. One or more of these various ways of implementing a timer may be used to measure a time period / window for a procedure. A random access response window timer may be used to measure the time window for receiving a random access response. For example, rather than starting a random access response window timer and determining its expiration, the time difference between two timestamps may be used. For example, if the timer is restarted, the process for measuring the time window may be restarted. Other example embodiments may be configured / provided to restart the measurement of the time window.

[0201] A wireless device may receive one or more messages (e.g., RRC messages or RRC reconfiguration messages) from a base station. The one or more messages may include one or more configuration parameters. The one or more configuration parameters may indicate multiple core sets of a BWP (e.g., a downlink BWP) for a cell (e.g., a PSCell, an SCell).

[0202] In at least some wireless technologies, a wireless device may receive one or more messages (e.g., RRC messages, RRC reconfiguration messages, etc.) from a base station, the one or more messages including one or more configuration parameters. The wireless device may receive a control command (e.g., MAC CE, DCI) indicating activation of the TCI state (or TCI state index) of a cell in a group of cells (or in a concurrent TCI update list).

[0203] In at least some wireless technologies, a wireless device may use (e.g., apply) the (same) TCI state index of a BWP (e.g., each BWP) of each cell in the set of cells for uplink transmission and / or downlink reception. The wireless device may use the (same) TCI state index of each BWP of each cell in the set of cells for uplink transmission and / or downlink reception, for example, based on a control command as a MAC CE.

[0204] In at least some wireless technologies, a wireless device may use the same TCI state index for an active BWP (e.g., each active BWP) in a cell (e.g., each cell) in a set of cells for uplink transmission and / or downlink reception. The wireless device may use the same TCI state index for an active BWP (e.g., each active BWP) in a cell (e.g., each cell) in the set of cells for uplink transmission and / or downlink reception, for example, based on a control command as DCI. The wireless device may be served by multiple TRPs including a first TRP (or a first core set pool index) and a second TRP (or a second core set pool index). The control command may indicate activation of the TCI state (or TCI state index) of the second TRP of a cell, for example.

[0205] The BWP of the second cell in the group of cells may be associated with the first TRP. The BWP of the second cell may not be associated with the second TRP. The BWP may be, for example, an active BWP of the second cell. The BWP may be, for example, a deactivated / inactive BWP of the second cell.

[0206] In at least some wireless technologies, a wireless device may use a TCI state index activated for (or associated with) a second TRP for the BWPs (e.g., each BWP or each active BWP) of a cell (e.g., each cell) in the set of cells. For example, this may not be efficient if the BWP of the second cell is not associated with the second TRP (or is associated with a different core set pool index). Using the transmit / receive beams (or spatial domain filters) of the second TRP via the BWP of the second cell associated with the first TRP may not be efficient. For example, the first TRP and the second TRP may not be co-located. For example, the first TRP and the second TRP may experience different channel conditions. This may increase bit error rates, reduce data rates, increase latency in data communications, etc.

[0207] For example, if the BWPs of cells in the group of cells are associated with different TRPs, enhancements to simultaneous TCI states (or TCI state indexes) are described herein. For example, the wireless device may not use a TCI state index activated for (or associated with) a second TRP for the BWP of a second cell associated with a first TRP. Instead, the wireless device may use the TCI state index activated for (or associated with) the second TRP for the second BWP of a third cell associated with the second TRP (or associated with the same core set pool index). The group of cells may include the third cell. This may reduce bit error rates, increase data rates, reduce latency in data communications, and the like. The wireless device may receive multiple DCI messages indicating multiple TCI states for activated cells (or BWPs of cells). The DCI in the multiple DCI messages (e.g., each DCI message) may indicate activation of a corresponding TCI state from the multiple TCI states.

[0208] The wireless device may transmit a plurality of HARQ-ACK information associated with the plurality of DCI messages in a HARQ-ACK codebook. The HARQ-ACK information in the plurality of HARQ-ACK information (e.g., each HARQ-ACK information) may be associated with a corresponding DCI message in the plurality of DCI messages.

[0209] The wireless device may use the TCI state indicated by the DCI message in the plurality of DCI messages for uplink transmission and / or downlink reception via the cell (or the BWP of the cell). The plurality of TCI states may include a TCI state.

[0210] In at least some wireless technologies, the wireless device may determine / select, from among the plurality of DCIs, the DCI that the wireless device received / detected / monitored in a latest monitoring opportunity among the plurality of DCIs. For example, if there are multiple DCIs in the last monitoring opportunity, the wireless device may select, from among the plurality of DCIs, the DCI that the wireless device received / detected / monitored via a cell with a lowest cell index.

[0211] A wireless device may be served by multiple TRPs including a first TRP (or a first core set pool index) and / or a second TRP (or a second core set pool index). One or more first DCI messages in the multiple DCI messages may indicate activation of one or more first TCI states for the first TRP. The DCI in the one or more first DCI messages (e.g., each DCI message) may indicate activation of a corresponding TCI state in the one or more first TCI states for the first TRP. The multiple TCI states may include the one or more first TCI states.

[0212] One or more second DCI messages in the plurality of DCI messages may indicate one or more second TCI states for activating a second TRP. The DCI in the one or more second DCI messages (e.g., each DCI message) may indicate a TCI state in the one or more second TCI states for activating a second TRP. The plurality of TCI states may include the one or more second TCI states.

[0213] For example, the wireless device may transmit one or more first HARQ-ACK information associated with the one or more first DCIs and one or more second HARQ-ACK information associated with the one or more second DCIs in the same HARQ-ACK codebook. The multiple HARQ-ACK information may include the one or more first HARQ-ACK information and the one or more second HARQ-ACK information. In at least some wireless technologies, for uplink transmission and / or downlink reception, the wireless device may use the TCI state indicated by the DCI received / detected / monitored by the wireless device in the latest monitoring opportunity of the cell with the lowest cell index. For example, if the wireless device is served by multiple TRPs, this may not be efficient. For example, when the one or more first DCIs include DCI indicating a TCI state, the one or more first TCI states may include a TCI state. The TCI state may be associated with the first TRP. The DCI may indicate the TCI state that activates the first TRP. For example, the DCI received / detected / monitored in the latest monitoring opportunity of the cell with the lowest cell index may indicate the TCI state that activates the first TRP. The wireless device may transmit an uplink transmission using a spatial domain transmission filter / beam determined based on the TCI state (of the first TRP). For example, this may not be efficient if at least one of the uplink transmissions is associated with (or directed toward / toward) the second TRP. The second TRP may not receive the at least one uplink transmission based on the misaligned beam at the second TRP and the wireless device. Transmitting the at least one uplink transmission of the second TRP using (or associated with) the spatial domain transmission filter / beam of the first TRP may not be efficient.

[0214] For example, if the one or more first DCIs include a DCI indicating a TCI state, the wireless device may receive a downlink reception using a spatial domain reception / reception filter / beam determined based on the TCI state (of the first TRP). For example, this may not be efficient if at least one of the downlink receptions is associated with (or oriented toward) the second TRP. The wireless device may not receive the at least one downlink reception from the second TRP based on the second TRP and a misaligned beam at the wireless device. Receiving the at least one downlink reception of the second TRP using the spatial domain reception filter / beam of (or associated with) the first TRP may not be efficient. This may increase bit error rates, reduce data rates, increase latency in data communications, and increase retransmissions resulting in increased power consumption.

[0215] For example, if a wireless device is served by multiple TRPs, the improvements described herein may include advantages such as enhanced DCI determination / selection to utilize TCI states. The wireless device may determine / select, from among the one or more first DCI messages (e.g., not among the multiple DCI messages), a first DCI message received / detected / monitored by the wireless device in a latest monitoring opportunity among the first monitoring opportunities of the one or more first DCI messages. The wireless device may determine / select a first DCI from among the one or more first DCI messages indicating activation of the one or more first TCI states of the first TRP (or the same core set pool index or the first core set pool index). The wireless device may not use / compare one or more second DCI messages indicating activation of the one or more second TCI states of the second TRP (or the second core set pool index) for the TCI state determination / selection of the first TRP. The wireless device may not determine / select the first DCI from among the multiple DCI messages indicating activation of the multiple TCI states of the first and second TRPs.

[0216] For example, if multiple DCI messages are present in the last monitoring opportunity in the first monitoring opportunity, the wireless device may select a first DCI message from the multiple DCI messages that the wireless device receives / detects / monitors via a first cell having a lowest cell index. The wireless device may receive / detect / monitor multiple DCI messages via at least two cells. The first cell may have the lowest cell index among at least two cell indexes of the at least two cells. The at least two cells may include the first cell.

[0217] For example, if multiple DCI messages are present in the last monitoring occasion of the first monitoring occasion of the first cell with the lowest cell index, the wireless device may select the first DCI message that schedules the first PDSCH reception with the latest / earliest start / end time among the multiple DCI messages. The multiple DCI messages may schedule multiple PDSCH receptions including the first PDSCH reception. The multiple PDSCH receptions may have one or more start / end times. Each of the multiple PDSCH receptions may have a corresponding start / end time among the one or more start / end times. The first start / end time of the first PDSCH reception may be the latest (or earliest) of the one or more start / end times of the multiple PDSCH receptions. The one or more start / end times may include the first start / end time of the first PDSCH reception.

[0218] For uplink transmission associated with a first TRP (or a first core set pool index) and / or downlink reception associated with the first TRP (or a first core set pool index), the wireless device may use a first TCI state indicated by a first DCI message. The one or more first TCI states may include the first TCI state. For uplink transmission associated with a second TRP (or a second core set pool index) and / or downlink reception associated with the second TRP (or a second core set pool index), the wireless device may not use the first TCI state indicated by the first DCI.

[0219] The wireless device may determine / select, from the one or more second DCI messages (not from the multiple DCI messages), a second DCI message received / detected / monitored by the wireless device in a latest monitoring occasion among the second monitoring occasions of the one or more second DCI messages. The wireless device may determine / select, from the one or more second DCI messages, a second DCI message indicating activation of the one or more second TCI states for a second TRP (or the same core set pool index or a second core set pool index). The wireless device may not determine / select, using / comparing, the one or more first DCI messages indicating activation of the one or more first TCI states for the first TRP (or the first core set pool index) for the TCI state of the second TRP. The wireless device may not determine / select, from the multiple DCI messages indicating activation of the multiple TCI states for the first and second TRPs.

[0220] For example, if multiple DCI messages are present in the last monitoring opportunity in the second monitoring opportunity, the wireless device may select, from among the multiple DCI messages, a second DCI message that the wireless device receives / detects / monitors via a second cell having a lowest cell index. The wireless device may receive / detect / monitor multiple DCI messages via at least two cells. The second cell may have the lowest cell index among at least two cell indexes of the at least two cells. The at least two cells may include the second cell.

[0221] For example, if multiple DCI messages are present in the last monitoring occasion of the second monitoring occasion of the second cell with the lowest cell index, the wireless device may select a second DCI message that schedules a second PDSCH reception with the latest / earliest start / end time among the multiple DCI messages. The multiple DCI messages may schedule multiple PDSCH receptions including the second PDSCH reception. The multiple PDSCH receptions may have one or more start / end times. A PDSCH reception (e.g., each PDSCH reception) in the multiple PDSCH receptions may have a corresponding start / end time among the one or more start / end times. The first start / end time of the second PDSCH reception may be the latest (or earliest) of the one or more start / end times of the multiple PDSCH receptions. The one or more start / end times may include the first start / end time of the second PDSCH reception.

[0222] For uplink transmission associated with a second TRP (or a second core set pool index) and / or downlink reception associated with a second TRP (or a second core set pool index), the wireless device may use a second TCI state indicated by a second DCI message. The one or more second TCI states may include a second TCI state. For uplink transmission associated with a first TRP (or a first core set pool index) and / or downlink reception associated with a first TRP (or a first core set pool index), the wireless device may not use the second TCI state indicated by the second DCI message. The improvements described herein may include advantages such as reducing bit error rates, increasing data rates, reducing latency in data communications, and reducing retransmissions resulting in reduced power consumption.

[0223] Monitoring a core set associated with a recovery search space set based on candidate reference signals may result in successful completion of a beam failure recovery procedure. The wireless device may receive a DCI indicating successful completion of beam failure recovery. This may result in reduced RLF and / or increased data rate.

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

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

[0226] The one or more configuration parameters 1720 may be RRC reconfiguration parameters. The one or more configuration parameters 1720 may be for one or more cells. The one or more cells may include a cell. A cell may be, for example, a serving cell. At least one configuration parameter in the one or more configuration parameters 1720 may be for a cell. The cell may be a primary cell (PCell). The cell may be a primary secondary cell (PSCell). The cell may be a secondary cell (SCell). The cell may be a secondary cell configured with a PUCCH (e.g., a PUCCH SCell). The cell may be a special cell (SpCell). For dual connectivity (DC) operation, the SpCell may refer to (or indicate) the PCell of an MCG or the PSCell of an SCG. The SpCell may refer to (or indicate) the PCell. The cell may be a primary SCG cell (PSCell). For dual connectivity operation, if a synchronous reconfiguration procedure is performed, the wireless device may, for example, perform a random access procedure via the PSCell.

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

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

[0229] A cell may include multiple BWPs. The multiple BWPs may include one or more uplink BWPs, including the cell's uplink BWP (UL BWP). The multiple BWPs may include one or more downlink BWPs, including the cell's downlink BWP. A BWP in the multiple BWPs may be in one of an active state and an inactive state (or deactivated state). For example, when a downlink BWP in one of the one or more downlink BWPs is in an active state, the wireless device 1705 may monitor downlink channels and / or signals (e.g., PDCCH, DCI, CSI-RS, PDSCH) on, for, and / or via the downlink BWP. When a downlink BWP in one of the one or more downlink BWPs is in an active state, the wireless device 1705 may receive a PDSCH on, for, and / or via the downlink BWP. In the inactive state of a downlink BWP in the 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, and / or via the downlink BWP. In the inactive state of a downlink BWP in the one or more downlink BWPs, the wireless device may stop monitoring 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 a downlink BWP in the one or more downlink BWPs, the wireless device 1705 may not monitor and receive PDSCH on, for, and / or via the downlink BWP. In the inactive state of a downlink BWP of the one or more downlink BWPs, the wireless device 1705 may stop receiving the PDSCH on, for, and / or via the downlink BWP.

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

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

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

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

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

[0235] The subcarrier spacing value for the downlink BWP and / or uplink BWP may be and / or indicate, for example, 15 kHz (µ = 0). The subcarrier spacing value may be and / or indicate, for example, 30 kHz (µ = 1). The subcarrier spacing value may be and / or indicate, for example, 60 kHz (µ = 2). The subcarrier spacing value may be and / or indicate, for example, 120 kHz (µ = 3). The subcarrier spacing value may be and / or indicate, for example, 240 kHz (µ = 4). The subcarrier spacing value may be and / or indicate, for example, 480 kHz (µ = 5). The subcarrier spacing value may be and / or indicate, for example, 960 kHz (µ = 6). 480 kHz may be valid and / or applicable to FR3. 960 kHz may be valid and / or applicable to FR3. 240 kHz may be valid and / or applicable to FR3. 120 kHz may be valid and / or applicable to FR3.

[0236] One or more configuration parameters may indicate multiple control resource sets (core sets). The one or more configuration parameters may indicate the multiple core sets for a downlink BWP (e.g., an active downlink BWP) of a cell. A downlink BWP (e.g., an active downlink BWP) may contain the multiple core sets. The one or more configuration parameters may indicate multiple core set indices / identifiers and / or indicators for the multiple core sets (e.g., provided by a higher-layer parameter ControlResourceSetId). Each core set in the multiple core sets may be identified and / or indicated by a corresponding core set index in the multiple core set indices. A first core set in the multiple core sets may be identified by a first core set index in the multiple core set indices. A second core set 1858 in the multiple core sets may be identified by a second core set index in the multiple core set indices.

[0237] One or more configuration parameters 1720 may indicate one or more coreset pool indexes for a plurality of coresets (e.g., provided by a higher-layer parameter, CoresetPoolIndex). Each coreset in the plurality of coresets may be configured, indicated, and / or include the one or more configuration parameters by a corresponding coreset pool index from the one or more coreset pool indexes (e.g., 0, 1, etc.). The one or more configuration parameters 1720 may indicate, for each coreset in the plurality of coresets, a corresponding coreset pool index from the one or more coreset pool indexes. For example, the one or more configuration parameters 1720 may indicate a first coreset pool index 1825 (CoresetPoolIndex = 0) for a first coreset in the plurality of coresets. For example, the one or more configuration parameters may indicate a second coreset pool index 1845 (CoresetPoolIndex = 1) for a second coreset in the plurality of coresets. The one or more coreset pool indexes may include the first coreset pool index 1825 and the second coreset pool index 1845.

[0238] Additionally or alternatively, one or more configuration parameters 1720 may indicate a core set pool index for a core set in the plurality of core sets. The higher-layer parameter CoresetPoolIndex may not be present in the configuration parameters for the core set. 1805 The wireless device may determine a value (e.g., a default value) for the core set pool index of the core set as a first core set pool index 1825 (CoresetPoolIndex = 0). The first core set pool index 1825 (CoresetPoolIndex = 0) may be the core set pool index for the core set, for example, based on the one or more configuration parameters that do not indicate a core set pool index for a core set. The wireless device 1805 may determine a value (e.g., a default value) for the core set pool index of the core set as the first core set pool index 1825, for example, based on the one or more configuration parameters that do not indicate a core set pool index for a core set.

[0239] A first core set pool (e.g., core set pool 0) may include one or more first core sets, whose core set pool index may be equal to first core set pool index 1825 (e.g., CoresetPoolIndex = 0). One or more configuration parameters 1720 may indicate first core set pool index 1825 for each of the one or more first core sets in the first core set pool. The plurality of core sets may include the one or more first core sets.

[0240] A second core set pool (e.g., core set pool 1) may include one or more second core sets whose core set pool index is equal to second core set pool index 1845 (e.g., CoresetPoolIndex = 1). One or more configuration parameters 1720 may indicate, for each of the one or more second core sets in the second core set pool, the second core set pool index 1845. The plurality of core sets may include the one or more second core sets.

[0241] One or more configuration parameters 1820 may not indicate a core set pool index for a core set in the plurality of core sets. The wireless device 1805 may determine a default value for a core set pool index for a core set, for example, based on the one or more configuration parameters 1820 not indicating a core set pool index for a core set. The default value may be equal to zero (e.g., CoresetPoolIndex = 0). The default value may be equal to a first core set pool index 1825 (e.g., zero). The first core set pool may include a core set, for example, based on the one or more configuration parameters not indicating a core set pool index for a core set. Based on the default value of the core set pool index for the core set being equal to the first core set pool index 1825, the first core set pool may include the core set.

[0242] The first core set pool index 1825 of the first core set and the second core set pool index 1845 of the second core set 1858 may be the same. One or more configuration parameters may indicate the same core set pool index for the first core set and the second core set 1858. Multiple core sets may include the first core set and the second core set 1858. One or more core set pool indexes may include the first core set pool index 1825 and the second core set pool index 1845. The wireless device 1805 may group the first core set and the second core set 1858 into the same core set pool (e.g., CoresetPoolIndex = 0 or CoresetPoolIndex = 1), for example, based on the first core set pool index 1825 of the first core set and the second core set pool index 1840 of the second core set 1858 being the same. The first core set pool including the first core set and the second core set pool including the second core set 1858 may be the same, for example, based on the first core set pool index 1825 of the first core set and the second core set pool index 1840 of the second core set 1858 being the same.

[0243] The first core set pool index 1825 of the first core set and the second core set pool index 1840 of the second core set 1858 may be different. Multiple core sets may include the first core set and the second core set 1858. One or more core set pool indexes may include the first core set pool index 1825 and the second core set pool index 1840. The wireless device 1805 may group the first core set and the second core set 1858 into different core set pools, for example, based on the difference between the first core set pool index 1825 and the second core set pool index 1840 of the first core set and the second core set 1858. The wireless device 1805 may group the first core set into a first core set pool (e.g., CoresetPoolIndex = 0). The wireless device 1805 may group the second core set 1858 into a second core set pool (e.g., CoresetPoolIndex = 1) that is different from the first core set pool, for example, based on the difference between the first core set pool index 1825 and the second core set pool index 1840. The first core set pool and the second core set pool may be different, for example, based on the first core set pool index 1825 of the first core set and the second core set pool index 1840 of the second core set 1858 being different.

[0244] One or more configuration parameters 1820 may indicate at least two core set pool indices (e.g., 0 and 1) of a higher-layer parameter CORESETPoolIndex. The one or more configuration parameters 1820 may include the higher-layer parameter CORESETPoolIndex having and / or set to the at least two core set pool indices. The at least two core set pool indices may include a first core set pool index 1825 (e.g., 0) for one or more first core sets in the plurality of core sets. The at least two core set pool indices may include a second core set pool index 1840 (e.g., 1) that is different from the first core set pool index 1825 for one or more second core sets in the plurality of core sets. The one or more first core sets may include one or more third core sets in the plurality of core sets without a value for the higher-layer parameter CORESETPoolIndex. The one or more configuration parameters 1820 may not include the higher-layer parameter CORESETPoolIndex for the one or more third core sets.

[0245] A cell may include multiple transmission and reception points (TRPs). The multiple TRPs may serve the cell and / or wireless devices 1805 in, via, and / or within the cell. At least one of the multiple TRPs may serve the cell and / or wireless devices in, via, and / or within the cell. The multiple TRPs may include a first TRP and a second TRP. The first TRP may send (e.g., transmit) downlink transmissions and / or signals (e.g., PDSCH, PDCCH, DCI) via a first core set pool. Transmitting downlink transmissions and / or signals (e.g., PDCCH, DCI) via the first core set pool may include the first TRP transmitting downlink transmissions and / or signals via a first core set having a first core set index and / or associated with the first core set index. The first TRP may not send (e.g., transmit) downlink transmissions and / or signals (e.g., PDSCH, PDCCH, DCI) via the second core set pool. Not transmitting downlink transmissions and / or signals (e.g., PDSCH, PDCCH, DCI) via the second core set pool may include the first TRP not sending (e.g., transmitting) downlink transmissions and / or signals via a second core set 1858 having a second core set pool index and / or associated with the second core set pool index.

[0246] The second TRP may send (e.g., transmit) downlink transmissions and / or signals (e.g., PDSCH, PDCCH, DCI) via the second core set pool. Transmitting downlink transmissions and / or signals (e.g., PDCCH, DCI) via the second core set pool may include the second TRP sending (e.g., transmitting) downlink transmissions and / or signals via the second core set 1858 having a second core set pool index and / or being associated with the second core set pool index. The second TRP may not send (e.g., transmit) downlink transmissions and / or signals (e.g., PDCCH, DCI) via the first core set pool. Not transmitting downlink transmissions and / or signals (e.g., PDCCH, DCI) via the first core set pool may include the second TRP not sending (e.g., transmitting) downlink transmissions and / or signals via the first core set having a first core set pool index and / or being associated with the first core set pool index.

[0247] One or more configuration parameters may indicate multiple uplink resources (e.g., PUCCH resources, SRS resources, etc.). The one or more configuration parameters may indicate the multiple uplink resources for an uplink carrier workstation (e.g., an active uplink carrier workstation) for a cell. The uplink carrier workstation (e.g., an active uplink carrier workstation) for a cell (e.g., a NUL carrier, a SUL carrier) may include the multiple uplink resources. The multiple uplink resources may include, for example, multiple PUCCH resources. The multiple uplink resources may include, for example, multiple SRS resources. The multiple uplink resources may include, for example, multiple PUSCH resources.

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

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

[0250] One or more configuration parameters may indicate one or more uplink resource set and / or group indexes, identifiers, and / or indicators of one or more uplink resource sets and / or groups (e.g., provided by higher layer parameters PUCCH-ResourceGroupId, SRS-ResourceSetId). Each uplink resource set and / or group in the 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 the one or more uplink resource set and / or group indexes. A first uplink resource set and / or group in the one or more uplink resource sets and / or groups may be identified by a first uplink resource set and / or group index in the one or more uplink resource set and / or group indexes. A second uplink resource set and / or group in the one or more uplink resource sets and / or groups may be identified by a second uplink resource set and / or group index in the one or more uplink resource set and / or group indexes.

[0251] One or more configuration parameters may indicate one or more core set pool indexes for a plurality of uplink resources (e.g., provided by a higher-layer parameter CoresetPoolIndex). Each of the plurality of uplink resources may include the one or more configuration parameters, be configured and / or indicated by a corresponding core set pool index in the one or more core set pool indexes (e.g., 0, 1). The one or more configuration parameters may indicate a corresponding core set pool index in the one or more core set pool indexes for each of the plurality of uplink resources. For example, the one or more configuration parameters may indicate a first core set pool index (CoresetPoolIndex = 0) for a first uplink resource in the plurality of uplink resources. For example, the one or more configuration parameters may indicate a second core set pool index (CoresetPoolIndex = 1) for a second uplink resource in the plurality of uplink resources. The one or more core set pool indexes may include a first core set pool index and a second core set pool index.

[0252] One or more configuration parameters may not indicate a core set pool index for an uplink resource in the plurality of uplink resources. A higher-layer parameter, CoresetPoolIndex, may not be present in the configuration parameters for the uplink resource. The wireless device 1805 may determine a value (e.g., a default value) for the core set pool index for the uplink resource as a first core set pool index (CoresetPoolIndex = 0). The wireless device may determine a value (e.g., a default value) for the core set pool index for the uplink resource as the first core set pool index, for example, based on the one or more configuration parameters that do not indicate a core set pool index for the uplink resource. The first core set pool index (CoresetPoolIndex = 0) may be, for example, a core set pool index for the uplink resource based on the one or more configuration parameters that do not indicate a core set pool index for the uplink resource.

[0253] One or more configuration parameters may indicate at least two core set pool indices (e.g., 0 and 1) of a higher-layer parameter CORESETPoolIndex. The one or more configuration parameters may include the higher-layer parameter CORESETPoolIndex having and / or set to the at least two core set pool indices. The at least two core set pool indices may include a first core set pool index (e.g., 0) for one or more first uplink resources in the plurality of uplink resources. The at least two core set pool indices may include a second core set pool index (e.g., 1) that is different from the first core set pool index for one or more second uplink resources in the plurality of uplink resources. The one or more first uplink resources may include one or more third uplink resources in the plurality of uplink resources without a value for the higher-layer parameter CORESETPoolIndex. The one or more configuration parameters may not include the higher-layer parameter CORESETPoolIndex for the one or more third uplink resources.

[0254] A cell may include multiple transmission and reception points (TRPs). The multiple TRPs may serve the cell and / or wireless devices in, via, and / or within the cell. At least one of the multiple TRPs may serve the cell and / or wireless devices in, via, and / or within the cell. The multiple TRPs may include a first TRP and a second TRP.

[0255] The first TRP may receive an uplink transmission and / or signal (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) having a first core set pool index and / or associated with the first core set pool index via a first uplink resource among the multiple uplink resources. The first TRP may not receive an uplink transmission and / or signal (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) having a second core set pool index and / or associated with the second core set pool index via a second uplink resource among the multiple uplink resources.

[0256] The second TRP may receive an uplink transmission and / or signal (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) having a second core set pool index and / or associated with the second core set pool index via a second uplink resource among the multiple uplink resources. The second TRP may not receive an uplink transmission and / or signal (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) having a first core set pool index and / or associated with the first core set pool index via a first uplink resource among the multiple uplink resources.

[0257] One or more configuration parameters may indicate one or more core set pool indices (e.g., provided by a higher-layer parameter, CoresetPoolIndex) for one or more uplink resource sets and / or groups. Each of the one or more uplink resource sets and / or groups may include a corresponding core set pool index from the one or more core set pool indices (e.g., 0, 1), configured and / or indicated by the one or more configuration parameters. The one or more configuration parameters may indicate a corresponding core set pool index from the one or more core set pool indices for each of the one or more uplink resource sets and / or groups. For example, the one or more configuration parameters may indicate a first core set pool index 1825 (CoresetPoolIndex = 0) for a first uplink resource set and / or group in the one or more uplink resource sets and / or groups. For example, the one or more configuration parameters may indicate a second core set pool index 1845 (CoresetPoolIndex = 1) for a second uplink resource set and / or group in the one or more uplink resource sets and / or groups. The one or more core set pool indexes may include a first core set pool index and a second core set pool index.

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

[0259] One or more configuration parameters may indicate at least two core set pool indices (e.g., 0 and 1) of a higher-layer parameter CORESETPoolIndex. The one or more configuration parameters may include the higher-layer parameter CORESETPoolIndex having and / or set to the at least two core set pool indices. The at least two core set pool indices may include a first core set pool index (e.g., 0) for one or more first uplink resource sets and / or groups of the one or more uplink resource sets and / or groups. The at least two core set pool indices may include a second core set pool index (e.g., 1) that is different from the first core set pool index for one or more second uplink resource sets and / or groups of the one or more uplink resource sets and / or groups. The one or more first uplink resource sets and / or groups may include one or more third uplink resource sets and / or groups of the one or more uplink resource sets and / or groups without a value for the higher-layer parameter CORESETPoolIndex. The one or more configuration parameters may not include the higher-layer parameter CORESETPoolIndex for the one or more third uplink resource sets and / or groups.

[0260] A cell may include multiple transmission and reception points (TRPs). The multiple TRPs may serve the cell and / or wireless devices in the cell, via the cell / the cell. At least one of the multiple TRPs may serve the cell and / or wireless devices in the cell, via the cell, and / or the cell. The multiple TRPs may include a first TRP and a second TRP.

[0261] The first TRP may receive an uplink transmission and / or signal (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) having a first core set pool index and / or associated with the first core set pool index via the uplink resources of the first uplink resource set and / or group in the one or more uplink resource sets and / or groups. The first TRP may not receive an uplink transmission and / or signal (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) having a second core set pool index and / or associated with the second core set pool index via the uplink resources of the second uplink resource set and / or group in the one or more uplink resource sets and / or groups.

[0262] The second TRP may receive an uplink transmission and / or signal (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) having a second core set pool index and / or associated with the second core set pool index via a second uplink resource set in the one or more uplink resource sets and / or groups and / or uplink resources in the group. The second TRP may not receive an uplink transmission and / or signal (e.g., PUSCH, PUCCH, SRS, UCI, PRACH) having a first core set pool index and / or associated with the first core set pool index via a first uplink resource set in the one or more uplink resource sets and / or groups and / or uplink resources in the group.

[0263] The wireless device may send (e.g., transmit) uplink transmissions and / or signals (e.g., PUSCH / PUCCH / SRS transmissions) via the uplink resources. The plurality of uplink resources may include uplink resources. An uplink resource set and / or group in the one or more uplink resource sets and / or groups may include uplink resources.

[0264] The wireless device 1805 may receive downlink control information (DCI) 1830 via a core set in the plurality of core sets that schedules, triggers, and / or indicates transmission of an uplink transmission and / or signal. The DCI 1830 may schedule, trigger, and / or indicate transmission of an uplink transmission and / or signal via uplink resources. The DCI may indicate the uplink resources. The DCI may include a field indicating the uplink resources.

[0265] The uplink transmission and / or signal may be a PUSCH transmission (e.g., a transport block). The uplink resource may be a PUSCH resource. DCI 1830 may schedule the transmission of the PUSCH transmission. The uplink transmission and / or signal may be a PUCCH transmission (e.g., HARQ-ACK information feedback). The uplink resource may be a PUCCH resource. DCI 1830 may schedule the reception of a transport block (e.g., PDSCH reception). The uplink transmission and / or signal may be HARQ-ACK information feedback for the transport block. The uplink transmission and / or signal may be an SRS. The uplink resource may be an SRS resource. DCI 1830 may schedule the transmission of the SRS. The SRS may be, for example, an aperiodic SRS.

[0266] The core set from which the wireless device 1805 receives DCI may be associated with a core set pool index. The one or more core set pool indexes may include a core set pool index. The one or more configuration parameters may indicate a core set pool index for the core set. The one or more configuration parameters may not indicate a core set pool index for the core set (CoresetPoolIndex = 0 or CoresetPoolIndex = 1). The value (e.g., a default value) of the core set pool index for the core set may be equal to a first core set pool index (CoresetPoolIndex = 0), for example, based on the one or more configuration parameters that do not indicate a core set pool index for the core set.

[0267] The uplink resource may be associated with a core set pool index. The uplink resource may be associated with a core set pool index, for example, based on receiving a DCI scheduling, triggering, and / or instructing transmission of an uplink transmission and / or signal via the uplink resource via the core set associated with the core set pool index.

[0268] An uplink resource set and / or group comprising uplink resources may be associated with a core set pool index. The uplink resource set and / or group may be associated with a core set pool index, for example, based on receiving a DCI for uplink resource scheduling, triggering and / or indicating transmission of uplink transmissions and / or signals in the uplink resource set and / or group (belonging to the uplink resource set and / or group) via the core set associated with the core set pool index. The uplink resource set and / or group may include one or more uplink resources, and the one or more uplink resources include uplink resources. The one or more uplink resources may be associated with a core set pool index, for example, based on an uplink resource set and / or group comprising the one or more uplink resources associated with the core set pool index. Each of the one or more uplink resources may be associated with a core set pool index, for example, based on an uplink resource set and / or group associated with the core set pool index.

[0269] An uplink transmission and / or signal may be associated with a core set pool index. The uplink transmission and / or signal may be associated with a core set pool index, for example, based on receiving DCI 1830 via a core set associated with the core set pool index that schedules, triggers, and / or indicates transmission of the uplink transmission and / or signal.

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

[0271] One or more configuration parameters 1820 may indicate multiple TCI states 1870, which indicate a unified TCI state for a cell. The one or more configuration parameters 1720 may include, for example, the one or more PDSCH configuration parameters for the downlink BWP of the cell. The one or more configuration parameters 1720 may indicate the multiple TCI states 1770 for the downlink BWP of the cell.

[0272] One or more configuration parameters 1720 may include, for example, one or more PDSCH configuration parameters for a second downlink BWP of a second cell. The one or more configuration parameters 1720 may indicate multiple TCI states 1770 for the second downlink BWP of the second cell. The one or more cells may include the second cell. The one or more configuration parameters may include, for the downlink BWP of the 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) that identifies (e.g., indicates) the second downlink BWP. The reference unified TCI state list parameter may include a cell index (e.g., ServCellIndex) that identifies (e.g., indicates) the second downlink BWP of the second cell. The second downlink BWP of the second cell may be a reference BWP of a reference cell for the cell's downlink BWP. The cell's downlink BWP may be a target BWP of a target cell. The one or more PDSCH configuration parameters of the downlink BWP of the cell may, for example, be based on the one or more configuration parameters without including a higher layer (e.g., RRC) parameter dl-OrJoint-TCIStateList, wherein the one or more configuration parameters include a reference unified TCI state list parameter for the downlink BWP of the cell.

[0273] One or more configuration parameters 1720 may include a unified TCI state type parameter (e.g., as described herein in Figure 17 The one or more configuration parameters may include one or more serving cell parameters (e.g., ServingCellConfig), and the one or more serving cell parameters may include a unified TCI state type parameter. The unified TCI state type parameter may indicate a unified TCI state type of the cell.

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

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

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

[0277] The one or more configuration parameters 1720 may include, for example, one or more uplink BWP configuration parameters of the uplink BWP of the cell. The one or more configuration parameters 1720 may indicate a second plurality of TCI states 1770 of the uplink BWP of the cell.

[0278] One or more configuration parameters 1720 may include, for example, one or more uplink BWP configuration parameters for a second uplink BWP of a second cell. The one or more configuration parameters 1720 may indicate a second plurality of TCI states 1770 for the second uplink BWP of the second cell. The one or more cells may include the second cell. The one or more configuration parameters 1720 may include, for the uplink BWP of the 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 a BWP index (e.g., BWP-Id) that identifies (e.g., indicates) the second uplink BWP. The reference unified TCI state list parameter may include a cell index (e.g., ServCellIndex) that identifies (e.g., indicates) the second cell.

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

[0280] The wireless device 1705 may utilize the multiple TCI states 1770 for downlink reception via the downlink BWP of the cell, for example, based on one or more configuration parameters 1720 indicating the multiple TCI states 1770 for the downlink BWP of the cell.

[0281] The wireless device 1705 may utilize the multiple TCI states 1770 for uplink transmission reception via the uplink BWP of the cell, for example, based on one or more configuration parameters 1720 indicating the multiple TCI states 1770 for the downlink BWP of the cell.

[0282] The wireless device 1705 may, for example, use a plurality of TCI states 1770 of the second downlink BWP of the second cell for downlink reception via the downlink BWP of the cell based on a reference unified TCI state list parameter indicating the second downlink BWP of the second cell for the downlink BWP of the cell. The wireless device 1705 may, for example, use the plurality of TCI states 1770 of the second downlink BWP of the second cell for uplink transmission reception via the uplink BWP of the cell based on a reference unified TCI state list parameter indicating the second downlink BWP of the second cell for the downlink BWP of the cell.

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

[0284] One or more configuration parameters 1720 may indicate a physical cell identifier (PCI) for a cell. The one or more configuration parameters 1720 may indicate one or more PCIs for the one or more cells. The one or more PCIs may include a PCI of a cell. The one or more configuration parameters 1720 may include a higher layer (e.g., RRC) parameter physCellId indicating the one or more PCIs for the one or more cells. The one or more configuration parameters may indicate a corresponding PCI among the one or more PCIs for each of the one or more cells. The one or more configuration parameters may include a higher layer (e.g., RRC) parameter physCellId indicating a corresponding PCI among the one or more PCIs for each of the one or more cells. The one or more configuration parameters may indicate a first PCI among the one or more PCIs for a first cell among the one or more cells. The first PCI may identify the physical cell identity of the first cell. The one or more configuration parameters may indicate a second PCI among the one or more PCIs for a second cell among the one or more cells. The second PCI may identify the physical cell identity of the second cell.

[0285] One or more configuration parameters may indicate a list of PCI sets (e.g., as described herein). Figure 17The one or more configuration parameters may include one or more serving cell parameters indicating a list of PCI sets (e.g., as described herein in Figure 17 The one or more serving cell parameters may include MIMO parameters (e.g., as described herein in Figure 17 The MIMOParam described in ), the MIMO parameter includes and / or indicates a list of PCI sets. The list of PCI sets may include at least one PCI set (e.g., Figure 17 A list of PCI sets may be associated with an SSB having a PCI that is different from the cell's PCI.

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

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

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

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

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

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

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

[0293] ● {2, PCI 2) may be a second PCI set in the list of PCI sets. '2' may be a second additional PCI index of the second PCI set. PCI 2 indicates a second PCI and / or identifies a second PCI, the second PCI indicating a second cell and / or identifying a second cell.

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

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

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

[0297] o The 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).

[0298] ○ The at least one PCI may include PCI 5, PCI 2, PCI 4, PCI 10 and / or PCI 21.

[0299] o The at least one cell may include a first cell, a second cell, a third cell, a fourth cell and / or a fifth cell.

[0300] ○ One or more cells may include the at least one cell and the cell.

[0301] The 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). The at least one PCI may include PCI 5, PCI 2, PCI 4, PCI 10, and / or PCI 21. The 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 the at least one cell and a cell.

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

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

[0304] 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 in the plurality of TCI states 1770. The additional PCI index may be absent (e.g., not present) in the configuration parameters for the one or more TCI states. The one or more configuration parameters 1720 may include configuration parameters for the one or more TCI states. The one or more TCI states in the plurality of TCI states may not be associated with an additional PCI index. The one or more TCI states may not include an additional PCI index. Each of the one or more TCI states may not include an additional PCI index. The one or more TCI states may be associated with a cell and / or a PCI of a cell, for example, based on the one or more configuration parameters, the one or more configuration parameters not indicating an additional PCI index for the one or more TCI states in the plurality of TCI states. The one or more TCI states may be associated with a cell and / or a PCI of a cell, for example, based on the one or more configuration parameters, the one or more configuration parameters not indicating an additional PCI index for each of the one or more TCI states. The one or more TCI states may be associated with a cell and / or a PCI of a cell, for example based on the one or more configuration parameters, the one or more configuration parameters not indicating an additional PCI index of the at least one additional PCI index for each TCI state in the one or more TCI states.

[0305] The wireless device 1705 may receive a control command 1730 (e.g., as described herein). Figure 17 MAC-CE, DCI, downlink control command / message, control command / message, unified TCI state activation / deactivation MAC CE, activation command at time T1, etc. described in

[0066] ). The control command 1730 may indicate activation of a subset 1780a of TCI states in a plurality of TCI states (e.g., DLorJoint-TCIStateList). The control command may also indicate activation of a subset 1780 of TCI states in a second plurality of TCI states (e.g., ul-TCI-StateList).

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

[0307] For example, in Figure 17 In the embodiment of the present invention, the subset of TCI states 1780a may include 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 state 5 and TCI state 8. The third TCI code point (e.g., TCI code point 110) may include and / or indicate TCI state 26 and TCI state 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.).

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

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

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

[0311] Figure 18 1805 may receive a first control command 1820 (e.g., as described herein). Figure 18The first control command 1820 may activate, select, indicate, update, and / or indicate activation of a first subset 1870a of TCI states in the plurality of TCI states 1770 (e.g., DL or Joint-TCIStateList). The first control command 1820 may activate, select, indicate, update, and / or indicate activation of a first subset 1870a of TCI states in the second plurality of TCI states 1770 (e.g., UL-TCIStateList).

[0312] The first control command 1820 may include a field (e.g., CoresetPoolID) with 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 be, for example, equal to zero. A first subset 1870a of TCI states may be associated with the first coreset pool index 1825. The first subset 1870a of TCI states may be associated with the first coreset pool index 1825, for example, based on the first control command 1820 indicating activation of the first subset 1870a of TCI states including a field with the first coreset pool index 1825. The wireless device may activate the first subset 1870a of TCI states for the first coreset pool index 1825.

[0313] The wireless device 1805 may map a first subset 1870a of TCI states to one or more first TCI code points 1870b. The wireless device 1805 may map corresponding TCI states in the first subset 1870a of TCI states to corresponding TCI code points in the one or more first TCI code points 1870b. The one or more first TCI code points 1870b may indicate and / or include the first subset 1870a of TCI states. Each TCI code point in the one or more first TCI code points 1870b may include, indicate, and / or map to a corresponding TCI state in the first subset 1870a of TCI states. Each TCI code point in the one or more first TCI code points 1870b may include, indicate, and / or map to one or more TCI states. The one or more first TCI code points 1870b may be associated with a first core set pool index 1825.

[0314] For example, in Figure 18In the embodiment of the present invention, the first subset of TCI states 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.).

[0315] The number of the one or more first TCI code points 1870b may be equal to one. The one or more first TCI code points 1870b may be a single TCI code point. The single TCI code point may indicate a first TCI state among a plurality of TCI states. The first subset of TCI states 1870a may be a first TCI state. The wireless device may, for example, not receive DCI indicating activation of one or more TCI states in the first subset of TCI states 1870a based on the number of the one or more first TCI code points 1870b being equal to one. The wireless device 1805 may, for example, not receive DCI indicating activation of one or more TCI states in the first subset of TCI states 1870a based on the first control command 1820 indicating the first TCI state.

[0316] The number of the one or more first TCI code points 1870b may be greater than one. The wireless 1805 device may access the first core set 1838 (eg, core set pool index 0) via a first core set 1838 pool index 1825 (eg, core set pool index 0). Figure 18 Core set 1 in receives first DCI 1830 (e.g., at Figure 181 at time T2 in ). The plurality of core sets may include a first core set 1838. The one or more configuration parameters may indicate a first core set pool index 1825 for the first core set 1838. The one or more configuration parameters may not indicate a core set pool index for the first core set 1838. The first core set 1838 may be associated with a first core set pool index 1825 (e.g., core set pool index 0), for example, based on the one or more configuration parameters, the one or more configuration parameters not indicating a core set pool index for the first core set 1838. A default value of the core set pool index for the first core set 1838 may be equal to the first core set pool index 1825 (e.g., core set pool index 0), for example, based on the one or more configuration parameters, the one or more configuration parameters not indicating a core set pool index for the first core set 1838.

[0317] First DCI 1830 (e.g., as described herein in Figure 18 The DCI 1) described in

[0065] may be, for example, DCI format 1_1. The first DCI 1830 may be, for example, DCI format 1_2. If x = 0, 1, 2, ..., the first DCI 1830 may be, for example, DCI format 1_x. If x = 0, 1, 2, ..., the first DCI 1830 may be, for example, DCI format 0_x.

[0318] The first DCI 1830 may include a first TCI field 1835. The first TCI field 1835 may indicate a first TCI code point among the one or more first TCI code points 1870b. The first TCI field 1835 may indicate a first TCI code point among the one or more first TCI code points 1870b associated with the first coreset pool index 1825, for example, based on receiving the first DCI 1830 via the first coreset 1838 having 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 may, for example, indicate the first TCI code point. The first TCI code point (e.g., 110) may indicate, include, and / or be mapped to a first TCI state (e.g., Figure 1826). The first subset of TCI states 1870a may include a first TCI state. The first DCI 1830 may activate and / or indicate activation of the first TCI state. The first DCI 1830 may indicate activation of the first TCI state. The first TCI field 1835 in the first DCI 1830 may indicate the first TCI state in the first subset of TCI states 1870a, for example, based on receiving the first DCI 1830 via the first coreset 1838 having the first coreset pool index 1825. The first TCI field 1835 in the first DCI 1830 may indicate the first TCI state in the first subset of TCI states 1870a, for example, based on the first control command 1820 indicating activation of the first subset of TCI states including a field having the first coreset pool index 1825 that may be the same as a field of the first coreset 1838.

[0319] The first TCI state may be associated with and / or activated for the first core set pool index 1825. The first TCI state may be associated with downlink and / or uplink reception and / or transmission associated with the first core set pool index 1825. The first TCI state may be associated with the downlink and / or uplink reception and / or transmission associated with the first core set pool index 1825, for example, based on receiving a first DCI 1830 indicating activation of the first TCI state via a first core set 1838 having the first core set pool index 1825.

[0320] The wireless device may 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 core set pool index 1825. The one or more configuration parameters may indicate the first core set pool index 1825 for a core set in the plurality of core sets. The wireless device may monitor a downlink control channel in the core set based on the first TCI state, e.g., based on (e.g., in response to) the one or more configuration parameters indicating the first core set pool index 1825 for the core set. The wireless device may receive DCI scheduling downlink signals (e.g., PDSCH transmission, transport block, DM-RS, CSI-RS, aperiodic CSI-RS) via the core set having the first core set pool index 1825. The plurality of core sets may include the core set. The downlink signal may be associated with the first core set pool index 1825, e.g., based on receiving DCI via the core set having the first core set pool index 1825. The wireless device may receive a downlink signal based on the first TCI state, e.g., based on (e.g., in response to) a downlink signal associated with the first core set pool index 1825. The wireless device may receive a downlink signal (e.g., a PDSCH transmission, a transport block, a DM-RS, a CSI-RS, an aperiodic CSI-RS) based on the first TCI state, e.g., based on (e.g., in response to) the one or more configuration parameters indicating the first core set pool index 1825 for the downlink signal and / or a resource set including the downlink signal.

[0321] The wireless device may apply the first TCI state to uplink transmissions associated with the first core set pool index 1825 (eg, PUSCH transmissions, transport blocks, PUCCH transmissions, SRS, etc.).

[0322] One or more configuration parameters may indicate a first core set pool index 1825 for uplink resources and / or uplink resource sets and / or groups comprising uplink resources. The wireless device 1805 may send (e.g., transmit) uplink signals (e.g., UCI, HARQ-ACK, SR, CSI report, SRS) via the uplink resources based on a first TCI state, e.g., based on (e.g., in response to) the one or more configuration parameters. The one or more configuration parameters indicate the first core set pool index 1825 for the uplink resources and / or uplink resource sets and / or groups comprising uplink resources. The uplink BWP (e.g., the active uplink BWP) of the cell may include uplink resources. The uplink resources may be, for example, PUCCH resources. The uplink signals may be UCI (e.g., UCI, HARQ-ACK, SR, CSI report). The uplink resources may be, for example, SRS resources. The uplink signals may be SRS. The uplink resources may be, for example, PUSCH resources. The uplink signal may be a PUSCH transmission (e.g., a transport block) of a configured uplink grant (e.g., a type 1 configured uplink grant). The transmission of the uplink signal via the uplink resource may be associated with a first core set pool index 1825, for example, based on the one or more configuration parameters indicating the first core set pool index 1825 for the uplink resource and / or an uplink resource set and / or group comprising the uplink resource.

[0323] The wireless device 1805 may receive DCI 1830 triggering and / or scheduling transmission of an uplink signal (e.g., a PUSCH transmission, a transport block, an SRS, or a HARQ-ACK) via a core set 1838 having a first core set pool index 1825. Multiple core sets may comprise a core set. The uplink signal may be associated with the first core set pool index 1825, for example, based on receiving DCI 1830 via the core set 1838 having the first core set pool index 1825. The wireless device may send (e.g., transmit) an uplink signal based on (e.g., in response to) the uplink signal associated with the first core set pool index 1825, based on a first TCI state.

[0324] The wireless device 1805 may receive a second control command 1840 1840 (e.g., as described herein). Figure 18

[00105] The second control command 1840 may activate, select, indicate, update, and / or indicate activation of a second subset 1880a of TCI states in the plurality of TCI states (e.g., DL or Joint-TCIStateList). The second control command 1840 may activate, select, indicate, update, and / or indicate activation of a second subset 1880a of TCI states in the second plurality of TCI states (e.g., UL-TCIStateList).

[0325] The second control command 1840 may include a command with a second core set pool index 1845 (e.g., Figure 18 The wireless device may also include a field (e.g., CoresetPoolID) containing a coreset pool index 1 in the wireless device. The value in the field may be equal to the second coreset pool index 1845. The second coreset pool index 1845 may be, for example, equal to one. A second subset of TCI states 1880a may be associated with the second coreset pool index 1845. The second subset of TCI states 1880a may be associated with the second coreset pool index 1845, for example, based on a second control command 1840 indicating activation of the second subset of TCI states 1880a including a field having the second coreset pool index 1845. The wireless device may activate the second subset of TCI states 1880a for the second coreset pool index 1845.

[0326] The wireless device 1805 may map a second subset 1880a of TCI states to one or more second TCI code points 1880b. The wireless device 1805 may map corresponding TCI states in the second subset 1880a of TCI states to corresponding TCI code points in the one or more second TCI code points 1880b. The one or more second TCI code points 1880b may indicate, include, and / or map to the second subset 1880a of TCI states. Each TCI code point in the one or more second TCI code points 1880b may include, indicate, and / or map to a corresponding TCI state in the second subset 1880a of TCI states. Each TCI code point in the one or more second TCI code points 1880b may include, indicate, and / or map to one or more TCI states. The one or more second TCI code points 1880b may be associated with a second core set pool index 1845.

[0327] For example, in Figure 18In the embodiment of the present invention, the second subset of TCI states 1880a may include 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.).

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

[0329] The number of the one or more second TCI code points 1880b may be greater than one. The wireless device 1805 may access the second core set 1858 (eg, core set pool index 1) via a second core set 1858 having a second core set 1858 pool index 1845 (eg, core set pool index 1). Figure 18 Core set 2 in the receiving device receives a second DCI 1850 (e.g., Figure 18 The one or more configuration parameters may indicate a second core set pool index 1845 for a second core set 1858. The plurality of core sets may include the second core set 1858.

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

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

[0332] The wireless device 1805 may 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 core set pool index 1845. One or more configuration parameters may indicate the second core set pool index 1845 for a core set in a plurality of core sets. The wireless device 1805 may monitor the downlink control channel in the core set based on the second TCI state, e.g., based on (e.g., in response to) the one or more configuration parameters indicating the second core set pool index 1845 for the core set. The wireless device 1805 may receive DCI scheduling downlink signals (e.g., PDSCH transmission, transport block, DM-RS, CSI-RS, aperiodic CSI-RS) via the core set having the second core set pool index 1845. The plurality of core sets may include the core set. The downlink signal may be associated with the second core set pool index 1845, e.g., based on receiving DCI via the core set having the second core set pool index 1845. The wireless device 1805 may receive a downlink signal based on the second TCI state, e.g., based on (e.g., in response to) a downlink signal associated with the second core set pool index 1845. The wireless device 1805 may receive a downlink signal (e.g., a PDSCH transmission, a transport block, a DM-RS, a CSI-RS, an aperiodic CSI-RS) based on the second TCI state, e.g., based on (e.g., in response to) the one or more configuration parameters indicating the second core set pool index 1845 for the downlink signal and / or a resource set including the downlink signal.

[0333] The wireless device 1805 may apply the second TCI state to uplink transmissions (e.g., PUSCH transmissions, transport blocks, PUCCH transmissions, SRS, etc.) associated with the second core set pool index 1845. One or more configuration parameters may indicate the second core set pool index 1845 for uplink resources and / or uplink resource sets and / or groups comprising uplink resources. The wireless device 1805 may send (e.g., transmit) uplink signals (e.g., UCI, HARQ-ACK, SR, CSI report, SRS) via the uplink resources based on the second TCI state, e.g., based on (e.g., in response to) the one or more configuration parameters indicating the second core set pool index 1845 for the uplink resources and / or uplink resource sets and / or groups comprising uplink resources. The uplink resources may be, for example, PUCCH resources. The uplink signal may be UCI (e.g., UCI, HARQ-ACK, SR, CSI report). The uplink resource may be, for example, an SRS resource. The uplink signal may be an SRS. The uplink resource may be, for example, a PUSCH resource. The uplink signal may be a PUSCH transmission (e.g., a transport block) of a configured uplink grant (e.g., a type 1 configured uplink grant). Sending (e.g., transmitting) the uplink signal via the uplink resource may be associated with a second core set pool index 1845, for example, based on the one or more configuration parameters indicating the second core set pool index 1845 for the uplink resource and / or an uplink resource set and / or group comprising the uplink resource.

[0334] The wireless device 1805 may receive DCI triggering and / or scheduling transmission of an uplink signal (e.g., PUSCH transmission, transport block, SRS, HARQ-ACK) via a core set having a second core set pool index 1845. Multiple core sets may include a core set. The uplink signal may be associated with the second core set pool index 1845, for example, based on receiving DCI via the core set having the second core set pool index 1845. The wireless device may send (e.g., transmit) an uplink signal based on (e.g., in response to) an uplink signal associated with the second core set pool index 1845, based on a second TCI state.

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

[0336] The first TCI state may be associated with the PCI of the cell. The first TCI state may not include the additional PCI index in the at least one additional PCI index. The additional PCI index may not be present in the configuration parameters of the first TCI state. The one or more configuration parameters may include the configuration parameters of the first TCI state. The first TCI state may be associated with the PCI of the cell, for example, based on the first TCI state not including the additional PCI index in the at least one additional PCI index. The first reference signal may be quasi-co-located with the first SS / PBCH block. The first reference signal may be the first SS / PBCH block. The first reference signal may be quasi-co-located with the first CSI-RS, which may be quasi-co-located with the first SS / PBCH block. The first SS / PBCH block may be associated with the cell. The first SS / PBCH block may be associated with the PCI of the cell. The one or more configuration parameters may indicate the first SS / PBCH block for the cell.

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

[0338] The second TCI state may include and / or indicate a second reference signal (e.g., CSI-RS, SSB / PBCH block, SRS, DM-RS). The second TCI state may include and / or indicate a second quasi-co-location type (e.g., QCL Type A, QCL Type B, QCL Type C, QCL Type D). The second TCI state may be associated with the PCI of the cell. The second TCI state may not include the additional PCI index of the at least one additional PCI index. The additional PCI index may not be present in the configuration parameters of the second TCI state. One or more configuration parameters may include configuration parameters of the second TCI state. The second TCI state may be associated with the PCI of the cell, for example, based on the second TCI state not including the additional PCI index of the at least one additional PCI index. The second reference signal may be quasi-co-located 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-located with a second CSI-RS, which may be quasi-co-located with the second SS / PBCH block. The second SS / PBCH block may be associated with the cell. The second SS / PBCH block may be associated with a PCI of the cell.The one or more configuration parameters may indicate a second SS / PBCH block for the cell.

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

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

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

[0342] A control command indicating activation of a subset of TCI states may include multiple fields. A first field among the multiple 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 the multiple 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., smaller than) the second octet. The first octet may be octet 5, and the second octet may be octet 6. The first octet may be octet 1, and the second octet may be octet 2. The first octet may be octet 9, and the second octet may be octet 10. The base station may sort the first TCI state index and the second TCI state index based on their ordinal position in the control command. For example, if n<m, octet n of the control command may contain a first TCI state index identifying (eg, indicating) a first TCI state, and octet m of the control command may contain a second TCI state index identifying (eg, indicating) a second TCI state.

[0343] A control command may indicate, map, and / or activate a set, list, and / or vector of at least two TCI states to a TCI code point. The control command may indicate the mapping, association, and / or activation of the set, list, and / or vector of at least two TCI states to a TCI code point. The at least two TCI states may include a first TCI state and a second TCI state. The first TCI state may occur first in the set, list, and / or vector of at least two TCI states. The first TCI state may be the first (e.g., the beginning, earliest, initial, etc.) TCI state in the set, list, and / or vector of at least two TCI states. The second TCI state may occur second in the set, list, and / or vector of at least two TCI states. The second TCI state may be the last (e.g., the latest, ending, 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], the first TCI state may be TCI state 5 and the second TCI state may be TCI state 8. For example, if the set, list and / or vector of the at least two TCI states = [TCI state 26, TCI state 61], the first TCI state may be TCI state 26 and the second TCI state may be TCI state 61.

[0344] The wireless device may apply a first TCI state to one or more first uplink channels and / or resources of a cell. Using the first TCI state with respect to the one or more first uplink channels / resources may include transmitting an uplink signal based on the first TCI state via the one or more first uplink channels / resources. The wireless device may send (e.g., transmit) an uplink signal based on the first TCI state via the one or more first uplink channels and / or resources. The wireless device may send (e.g., transmit) a corresponding uplink signal based on the first TCI state via each of the one or more first uplink channels and / or resources.

[0345] The wireless device may send (e.g., transmit) an uplink signal via one or more first uplink channels and / or resources at a transmission power determined based on a first TCI state. The wireless device may send (e.g., transmit) an uplink signal via each of the one or more first uplink channels and / or resources at a corresponding transmission power determined based on the first TCI state. The wireless device may send (e.g., transmit) the first uplink signal via a first uplink channel and / or resource of the one or more first uplink channels and / or resources at a first transmission power determined based on the first TCI state. The wireless device may determine the 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, indicated by, and / or included in the first TCI state. The wireless device may send (e.g., transmit) a second uplink signal via a second uplink channel and / or resource among the one or more first uplink channels and / or resources at a second transmission power determined based on the first TCI state. The wireless device may 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) associated with, mapped to, indicated by, and / or included in the first TCI state.

[0346] The wireless device may transmit (e.g., transfer) an uplink signal via one or more first uplink channels and / or resources using a first spatial domain transmit filter and / or beam determined based on a first TCI state. The wireless device may transmit (e.g., transfer) the corresponding uplink signal via each of the one or more first uplink channels and / or resources using the first spatial domain transmit filter and / or beam determined based on the first TCI state. The wireless device may transmit (e.g., transfer) the first uplink signal via a first uplink channel and / or resource of the one or more first uplink channels and / or resources using the first spatial domain transmit filter and / or beam determined based on the 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. The wireless device may transmit (e.g., transfer) the second uplink signal via a second uplink channel and / or resource of the one or more first uplink channels and / or resources using the first spatial domain transmit filter and / or beam determined based on the 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.

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

[0348] The wireless device 1805 may receive a first DCI 1830 scheduling a first PUSCH transmission via a first core set 1838. Multiple core sets may include the first core set 1838. The first DCI 1830 may include, for example, a field (e.g., an SRS resource set indicator field, a TRP field, a core set pool index field, an additional PCI index, a BFD set index, a unified TCI state indicator field, a joint TCI state indicator field, an uplink TCI state indicator field, a panel index, a capability set index, etc.) having a first value (e.g., 0, 00, 10, 11) indicating a first TCI state. The wireless device may send (e.g., transmit) the first PUSCH transmission based on (e.g., in response to) the first DCI 1830 including the field having the first value indicating the first TCI state. One or more first uplink channels and / or resources may include a PUSCH transmission scheduled by the DCI including the field having the first value. Each of the DCIs may schedule one or more of the PUSCH transmissions.

[0349] A first core set 1838 may be associated with a first core set pool index 1825 (e.g., CoresetPoolIndex = 0). One or more configuration parameters may indicate the first core set pool index 1825 for the first core set 1838. The one or more configuration parameters may not indicate a core set pool index for the first core set 1838. The wireless device may send (e.g., transmit) a first PUSCH transmission based on a first TCI state, e.g., based on (e.g., in response to) receiving a first DCI 1830 scheduling a first PUSCH transmission via the first core set 1838 having the first core set pool index 1825. One or more first uplink channels and / or resources may include the first PUSCH transmission. The one or more first uplink channels and / or resources may include a PUSCH transmission scheduled by the DCI received via the one or more first core sets having the first core set pool index 1825. The plurality of core sets may include the one or more first core sets.

[0350] The wireless device may transmit a first PUSCH transmission at a first transmission power determined based on a first TCI state. The wireless device may transmit the first PUSCH transmission with a first spatial domain transmit filter / beam determined based on the first TCI state.

[0351] One or more configuration parameters may indicate a field (e.g., an SRS resource set indicator field, a TRP field, a core set pool index field, an additional PCI index, a BFD set index, a unified TCI state indicator field, a joint TCI state indicator field, an uplink TCI state indicator field, a panel index, a capability set index, etc.) having a first value (e.g., 0, 00, 10, 11) for a configured uplink grant. The wireless device may send (e.g., transmit) a PUSCH transmission of the configured uplink grant based on the first TCI state, for example, based on (e.g., in response to) the one or more configuration parameters, wherein the one or more configuration parameters indicate a field having a first value indicating the first TCI state for the configured uplink grant. The configured uplink grant may be, for example, a type 1 configured uplink grant. The one or more first uplink channels and / or resources may include a PUSCH transmission of the configured uplink grant.

[0352] The wireless device may transmit a configured uplink grant PUSCH transmission at a first transmission power determined based on a first TCI state. The wireless device may transmit a configured uplink grant PUSCH transmission with a first spatial domain transmit filter / beam determined based on the first TCI state.

[0353] The one or more first uplink channels and / or resources may include a PUCCH. The one or more first uplink channels and / or resources may include one or more first PUCCH resources. The one or more first uplink channels and / or resources may include one or more first PUCCH resource sets and / or groups. The one or more first uplink channels and / or resources may include one or more first PUCCH transmissions.

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

[0355] The wireless device may transmit an uplink signal via a first PUCCH resource at a first transmission power determined based on a first TCI state. The wireless device may transmit an uplink signal via the first PUCCH resource using a first spatial domain transmission filter / beam determined based on the first TCI state.

[0356] One or more configuration parameters may indicate a field (e.g., an SRS resource set indicator field, a TRP field, a core set pool index field, an additional PCI index, a BFD set index, a unified TCI state indicator field, a joint TCI state indicator field, an uplink TCI state indicator field, a panel index, a capability set index, etc.) having a first value (e.g., 0, 00, 10, 11) indicating a first TCI state for a first PUCCH resource set and / or group. The wireless device may send (e.g., transmit) an uplink signal (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 state, for example, based on (e.g., in response to) the one or more configuration parameters indicating a field having a first value indicating the first TCI state for the first PUCCH resource set and / or group. The wireless device may send (e.g., transmit) a corresponding uplink signal (e.g., SR, HARQ-ACK, CSI report, uplink control information) based on the first TCI state, e.g., based on (e.g., in response to) the one or more configuration parameters indicating a field having a first value indicating the first TCI state for the first PUCCH resource set and / or group. The one or more first uplink channels and / or resources may include a PUCCH transmission via each PUCCH resource in the first PUCCH resource set and / or group.

[0357] The wireless device may transmit an uplink signal via a PUCCH resource at a first transmission power determined based on a first TCI state. The wireless device may transmit an uplink signal via a PUCCH resource using a first spatial domain transmission filter / beam determined based on the first TCI state.

[0358] The wireless device may receive, via a first core set 1838, a first DCI 1830 that triggers and / or schedules transmission of a first PUCCH transmission (e.g., a HARQ-ACK feedback transmission). The first DCI 1830 may, for example, schedule PDSCH reception. The first DCI 1830 may, for example, indicate SCell inactivity. The first DCI 1830 may, for example, indicate SPS PDSCH release. The first DCI 1830 may, for example, indicate activation of a unified TCI state. The multiple core sets may include the first core set 1838. The first DCI 1830 may include, for example, a field (e.g., an SRS resource set indicator field, a TRP field, a core set pool index field, an additional PCI index, a BFD set index, a unified TCI state indicator field, a joint TCI state indicator field, an uplink TCI state indicator field, a panel index, a capability set index, etc.) having a first value (e.g., 0, 00, 10, 11) indicating a first TCI state. The wireless device may send (e.g., transmit) a first PUCCH transmission based on a first TCI state, e.g., based on (e.g., in response to) a first DCI 1830 including a field with a first value indicating the first TCI state. The one or more first uplink channels and / or resources may include a PUCCH transmission triggered and / or scheduled by the DCI including the field with the first value.

[0359] A first core set 1838 may be associated with a first core set pool index 1825 (e.g., CoresetPoolIndex = 0). One or more configuration parameters may indicate the first core set pool index 1825 for the first core set 1838. The one or more configuration parameters may not indicate a core set pool index for the first core set 1838. The wireless device may send (e.g., transmit) a first PUCCH transmission based on a first TCI state, for example, based on (e.g., in response to) receiving a first DCI 1830 triggering and / or scheduling a first PUCCH transmission via the first core set 1838 having the first core set pool index 1825. The one or more first uplink channels and / or resources may include a PUCCH transmission triggered and / or scheduled by the DCI received via the one or more first core sets having the first core set pool index 1825. The plurality of core sets may include one or more first core sets.

[0360] The wireless device may transmit a first PUCCH transmission at a first transmission power determined based on a first TCI state. The wireless device may transmit the first PUCCH transmission with a first spatial domain transmit filter / beam determined based on the first TCI state.

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

[0362] One or more configuration parameters may indicate, for a first SRS resource, a field (e.g., an SRS resource set indicator field, a TRP field, a core set pool index field, an additional PCI index, a BFD set index, a unified TCI state indicator field, a joint TCI state indicator field, an uplink TCI state indicator field, a panel index, a capability set index, etc.) having a first value (e.g., 0) indicating a first TCI state. The wireless device may send (e.g., transmit) an SRS via the first SRS resource based on the first TCI state, for example, based on (e.g., in response to) the one or more configuration parameters, wherein the one or more configuration parameters indicate, for the first SRS resource, a field having a first value that may indicate the first TCI state. The one or more first uplink channels and / or resources may include an SRS transmission via the first SRS resource.

[0363] The wireless device may transmit the SRS via the first SRS resource with a first transmission power determined based on the first TCI state. The wireless device may transmit the SRS via the first SRS resource with a first spatial domain transmission filter / beam determined based on the first TCI state.

[0364] One or more configuration parameters may indicate, for a first SRS resource set and / or group, a field (e.g., an SRS resource set indicator field, a TRP field, a core set pool index field, an additional PCI index, a BFD set index, a unified TCI state indicator field, a joint TCI state indicator field, an uplink TCI state indicator field, a panel index, a capability set index, etc.) having a first value (e.g., 0, 00, 10, 11) indicating a first TCI state. The wireless device may send (e.g., transmit) an SRS via SRS resources in the first SRS resource set and / or group based on the first TCI state, for example, based on (e.g., in response to) the one or more configuration parameters, wherein the one or more configuration parameters indicate, for the first SRS resource set and / or group, a field having a first value that may indicate the first TCI state. The wireless device may send (e.g., transmit) a corresponding SRS via each SRS resource in a first SRS resource set and / or group based on the first TCI state, e.g., based on (e.g., in response to) one or more configuration parameters indicating, for the first SRS resource set and / or group, a field having a first value that may indicate the first TCI state. The one or more first uplink channels and / or resources may include an SRS transmission via each SRS resource in the first SRS resource set and / or group.

[0365] The wireless device may transmit the SRS via the SRS resource at a first transmission power determined based on the first TCI state. The wireless device may transmit the SRS via the SRS resource with a first spatial domain transmission filter / beam determined based on the first TCI state.

[0366] The wireless device 1805 may receive a first DCI 1830 triggering and / or scheduling transmission of an SRS via a first core set 1838. The SRS may be, for example, an aperiodic SRS. The SRS may be, for example, a semi-persistent SRS. The multiple core sets may include the first core set 1838. The first DCI 1830 may include, for example, a field (e.g., an SRS resource set indicator field, a TRP field, a core set pool index field, an additional PCI index, a BFD set index, a unified TCI state indicator field, a joint TCI state indicator field, an uplink TCI state indicator field, a panel index, a capability set index, etc.) having a first value (e.g., 0, 00, 10, 11) indicating a first TCI state. The wireless device 1805 may send (e.g., transmit) an SRS based on the first TCI state, e.g., based on (e.g., in response to) the first DCI 1830 including a field having a first value indicating the first TCI state. The one or more first uplink channels and / or resources may include SRS transmission triggered and / or scheduled by a DCI including a field having a first value.

[0367] A first core set 1838 may be associated with a first core set pool index 1825 (e.g., CoresetPoolIndex = 0). One or more configuration parameters may indicate the first core set pool index 1825 for the first core set 1838. The one or more configuration parameters may not indicate a core set pool index for the first core set 1838. The wireless device may send (e.g., transmit) an SRS based on a first TCI state, for example, based on (e.g., in response to) receiving a first DCI 1830 triggering and / or scheduling transmission of an SRS via the first core set 1838 having the first core set pool index 1825. One or more first uplink channels and / or resources may include SRS transmissions triggered and / or scheduled by DCI received via the one or more first core sets having the first core set pool index 1825. Multiple core sets may include one or more first core sets.

[0368] The wireless device may transmit the SRS at a first transmission power determined based on, for example, a first TCI state. The wireless device may transmit the SRS using, for example, a first spatial domain transmission filter / beam determined based on, for example, a first TCI state.

[0369] The wireless device may use (e.g., apply) a first TCI state to one or more first downlink channels and / or resources of a cell. Using (e.g., applying) the first TCI state to the one or more first downlink channels / resources may include receiving a downlink signal based on the first TCI state via the one or more first downlink channels / resources. The wireless device may receive a downlink signal based on the first TCI state via the one or more first downlink channels / resources. The wireless device may receive a corresponding one of the downlink signals based on the first TCI state via a downlink channel / resource (e.g., each downlink channel / resource) of the one or more first downlink channels / resources.

[0370] The wireless device may receive a downlink signal via the 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 may receive the corresponding downlink signal via a downlink channel / resource (e.g., each downlink channel / resource) among the one or more first downlink channels / resources using the first spatial domain receive / receive filter / beam determined based on the first TCI state. For example, the wireless device may receive the first downlink signal via a first downlink channel / resource among the one or more first downlink channels / resources using the first spatial domain receive / receive filter / beam determined based on the first TCI state. For example, at least one DMRS antenna port of the first downlink signal may be quasi-co-located with a first reference signal indicated by the first TCI state. The wireless device may receive a second downlink signal via a second downlink channel / resource among the one or more first downlink channels / resources using the first spatial domain receive / receive filter / beam determined based on the first TCI state. For example, at least one DMRS antenna port of the second downlink signal may be quasi-co-located with the first reference signal indicated by the first TCI state.

[0371] The one or more first downlink channels / resources may be / include a PDSCH. The one or more first downlink channels / resources may be / include one or more first PDSCH resources. The one or more first downlink channels / resources may be / include one or more first PDSCH transmissions.

[0372] A wireless device may receive a first DCI scheduling a first PDSCH reception via a first core set. The multiple core sets may include the first core set. The first DCI may include, for example, a field (e.g., an SRS resource set indicator field, a TRP field, a core set pool index field, an additional PCI index, a BFD set index, a unified TCI state indicator field, a joint TCI state indicator field, an uplink TCI state indicator field, a panel index, a capability set index, etc.) having a first value (e.g., 0, 00, 10, 11) indicating a first TCI state. The wireless device may receive / perform a first PDSCH reception based on the first TCI state, e.g., based on the first DCI including a field having the first value indicating the first TCI state. The one or more first downlink channels / resources may be / include a PDSCH reception scheduled by the DCI including a field having the first value. The DCI in the DCI (e.g., each DCI) may schedule one or more PDSCH receptions in the PDSCH reception.

[0373] The first core set may be associated with a first core set pool index (e.g., CoresetPoolIndex = 0). For example, the one or more configuration parameters may indicate the first core set pool index for the first core set. For example, the one or more configuration parameters may not indicate the core set pool index for the first core set. The wireless device may receive / perform a first PDSCH reception based on a first TCI state, for example, based on a first DCI receiving a scheduling first PDSCH reception via the first core set having the first core set pool index. The one or more first downlink channels / resources may be / include a first PDSCH reception. The one or more first downlink channels / resources may be / include a PDSCH reception scheduled by a DCI received via one or more first core sets having the first core set pool index. The multiple core...

Claims

1. A method comprising: receiving, by a wireless device, one or more messages including one or more configuration parameters indicating a simultaneous transmission configuration indication (TCI) update cell list for a plurality of cells, wherein at least a first cell of the plurality of cells is associated with at least a first control resource set (core set) pool index and a second core set pool index; receiving a control command instructing activation of one or more TCI states of cells in the simultaneous TCI update cell list, wherein the one or more TCI states are associated with the first core set pool index; as well as An uplink signal is transmitted via one or more cells in the simultaneous TCI update list, the one or more cells being configured with one or more downlink bandwidth parts, the one or more downlink bandwidth parts including a coreset associated with the first coreset pool index.

2. The method of claim 1 , wherein the transmitting the uplink signal comprises transmitting the uplink signal using at least one of: a spatial domain transfer filter associated with the one or more TCI states; or A transmission power is determined based on the one or more TCI states.

3. The method according to any one of claims 1 to 2, wherein the one or more configuration parameters indicate: a first sounding reference signal (SRS) resource set index of a first SRS resource set; A second SRS resource set index of a second SRS resource set; a first control core set pool index of one or more first core sets; as well as A second coreset pool index of one or more second coresets.

4. The method according to any one of claims 1 to 3, further comprising transmitting, via the cell and based on the first SRS resource set index being lower than the second SRS resource set index: a first physical uplink shared channel (PUSCH) transmission, the first PUSCH transmission being associated with the first core set pool index based on the first SRS resource set; and A second PUSCH transmission is associated with the second core set pool index based on the second SRS resource set.

5. The method according to any one of claims 1 to 4, further comprising: receiving a plurality of indications of downlink control information (DCI) in one or more monitoring occasions of one or more cells, wherein each DCI of the plurality of DCIs indicates a transmission configuration indicator (TCI) state of a core set pool index of one or more core set pool indexes; transmitting hybrid automatic repeat request acknowledgement (HARQ-ACK) information associated with DCI of one or more DCIs of the plurality of DCIs, the DCI being received in a latest of the one or more monitoring occasions of a cell of the one or more cells having a lowest cell index, wherein the one or more DCIs indicate one or more TCI states of a core set pool index of the one or more core set pool indexes; and A TCI state is transmitted among the one or more TCI states indicated by the DCI for transmission associated with the core set pool index.

6. The method according to any one of claims 1 to 5, wherein the one or more configuration parameters indicate, for the first core set: First core set index; Common Search Space (CSS) sets; and Transmission Configuration Indication (TCI) indicator field.

7. The method of any one of claims 1 to 6, further comprising setting a value of the TCI indicator field to one of a first value and a second value, wherein the setting is based on: Type0-PDCCH CSS set; Type0A-PDCCH CSS set; and Type2-PDCCH CSS set.

8. The method according to any one of claims 1 to 7, wherein the receiving the control command is performed via a coreset associated with the first coreset pool index.

9. The method of any one of claims 1 to 8, wherein one or more bandwidth parts (BWPs) of the one or more cells are associated with the first core set pool index, and wherein each of the one or more BWPs is associated with a different cell of the one or more cells.

10. The method according to any one of claims 1 to 9, further comprising using the one or more TCI states for the uplink signal of one or more determined cells.

11. The method according to any one of claims 1 to 10, wherein the using is based on the one or more cells associated with the first core set pool index.

12. The method according to any one of claims 1 to 11, wherein the using is based on the simultaneous TCI update list comprising the one or more cells.

13. A computing device comprising: one or more processors; and A memory storing instructions that, when executed by the one or more processors, cause the computing 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; and A base station is configured to send the one or more messages.

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

Images