Skip the random access procedure for LTM cell handover

Abstract

The wireless device can receive various control messages from the base station for cell handover. These control messages can indicate timing information and configure the wireless device to handover from a source cell to a target cell. If no timing information is indicated, the wireless device can measure the timing information and / or skip the random access procedure for the target cell.

Description

Cross-references to related applications

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 531,094, filed August 7, 2023. The entire contents of the application cited above are incorporated herein by reference. Background Technology

[0002] The wireless device communicates with the base station. The wireless device receives configuration parameters for communication via the cell. These configuration parameters include timing information. Summary of the Invention

[0003] The following summary presents a simplified overview of certain features. This summary is neither a comprehensive overview nor intended to identify important or key elements.

[0004] A wireless device can receive multiple control messages from a base station. In these control messages, one or more parameters enable the wireless device to measure timing information of the target cell (e.g., timing advance value), for example, rather than relying on timing information provided by the base station. The measured timing information can be used to improve the synchronization and / or efficiency of inter-cell handover. Control messages (e.g., cell handover commands) can be used to configure the wireless device to transition from a source cell to a target cell. If the cell handover command does not indicate timing information, the wireless device can independently measure the timing information of the target cell. The wireless device can use the measured timing information, for example, instead of performing random access procedures to obtain timing information, which can provide advantages such as reduced latency and / or improved efficiency of base station and / or inter-cell handover.

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

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

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

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

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

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

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

[0012] Figure 4BAn example format of the MAC subheader in a Media Access Control (MAC) protocol data unit (PDU) is shown.

[0013] Figure 5A An example mapping of the downlink channel is shown.

[0014] Figure 5B An example mapping of the uplink channel is shown.

[0015] Figure 6 Example Radio Resource Control (RRC) states and RRC state transitions are shown.

[0016] Figure 7 An example configuration of the frame is shown.

[0017] Figure 8 An example resource configuration for one or more carriers is shown.

[0018] Figure 9 An example configuration for the Bandwidth Part (BWP) is shown.

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

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

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

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

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

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

[0025] Figure 13A An example four-step random access procedure is shown.

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

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

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

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

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

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

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

[0033] Figure 17 An example of a mobility (LTM) procedure triggered by layer 1 (L1) or layer 2 (L2) is shown.

[0034] Figure 18 An example method for cell handover is shown.

[0035] Figure 19 An example method for cell handover is shown.

[0036] Figure 20 An example method for cell handover is shown. Detailed Implementation

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

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

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

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

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

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

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

[0044] RAN 104 can be deployed as a homogeneous network of base stations (e.g., macrocell base stations) with similar antenna patterns and / or similar high levels of transmission power. RAN 104 can also be deployed as a heterogeneous network of base stations (e.g., different base stations with different antenna patterns). In a heterogeneous network, small cell base stations can be used to provide / configure small coverage areas, such as coverage areas overlapping with relatively large coverage areas provided / configured by other base stations (e.g., macrocell base stations). Small coverage areas can be provided / configured in areas with high data traffic (or so-called "hot spots") or in areas with weak macrocell coverage. Examples of small cell base stations can include (in descending order of coverage area) microcell base stations, picocell base stations, femtocell base stations, or femtocell base stations.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0079] 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 devices 106, 210, or any other wireless device. The wireless device can be in at least one of a plurality of states, such as three RRC states, including RRC connected 602 (e.g., RRC_CONNECTED), RRC idle 606 (e.g., RRC_IDLE), and RRC inactive state 604 (e.g., RRC_INACTIVE). RRC inactive state 604 can mean that the RRC is connected but inactive.

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

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

[0082] Previously established RRC contexts can be maintained for radio devices. For example, this might occur during an RRC inactivity state. During an RRC inactivity state (e.g., RRC inactivity state 604), previously established RRC contexts can be maintained in both the radio device and the base station. Compared to a transition from an RRC idle state (e.g., RRC idle 606) to an RRC connected state (e.g., RRC connected 602), maintaining the RRC context allows for / permits a rapid transition to the RRC connected state (e.g., RRC connected 602) with reduced signaling overhead. During an RRC inactivity state (e.g., RRC inactivity state 604), the radio device can be in a sleep state, and its mobility can be managed / controlled by the radio device via cell reselection. The RRC state can transition from an RRC inactivity state (e.g., RRC inactivity state 604) to an RRC connected state (e.g., RRC connected 602) via a connection recovery procedure 614. The RRC state can be transitioned from an RRC inactive state (e.g., RRC inactive state 604) to an RRC idle state (e.g., RRC idle 606) via a connection release procedure 616 that is the same as or similar to connection release procedure 608.

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

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

[0085] RAN areas can be used to track radio devices (e.g., the location of radio devices at the RAN level). For radio devices in an RRC inactive state (e.g., RRC inactive state 604), RAN notification areas can be assigned / provided / configured to the radio device. RAN notification areas can include one or more cell identities (e.g., RAI lists and / or TAI lists). 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 radio device moves (e.g., via cell reselection) to a cell not included in a RAN notification area assigned / provided / configured to the radio device, the radio device can perform a notification area update with the RAN to update its RAN notification area.

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

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

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

[0089] 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 the System Frame Number (SFN) or any other value. An SFN can repeat for 1024 frames in a cycle. The duration of an NR frame may be 10 milliseconds (ms) and may include 10 subframes with a duration of 1 ms. Subframes may be divided into one or more time slots (e.g., depending on the parameter set and / or different subcarrier spacing). Each of the one or more time slots may include, for example, 14 OFDM symbols per slot. Any number of symbols, time slots, or durations can be used for any time interval.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0107] The network can configure the maximum number of CCs that can be aggregated (e.g., up to 32 CCs can be aggregated in NR, or any other number in other systems). Aggregated CCs can have the same or different bandwidths, subcarrier spacing, and / or duplex schemes (TDD, FDD, or any other duplex scheme). The serving cell for a radio device using CA can have downlink CCs. One or more uplink CCs can optionally be configured for the serving cell (e.g., for FDD). For example, if the radio 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.

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

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

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

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

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

[0113] The multicarrier nature of the PHY layer can be exposed / indicated to the MAC layer (e.g., in a CA configuration). HARQ entities can operate on the serving cell. Transport blocks can be generated based on assignment / granting per serving cell. Transport blocks and their potential HARQ retransmissions can be mapped to serving cells.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0127] A transmitter (e.g., a transmitter at a base station) may use a precoder matrix for a portion of the transmission bandwidth. The transmitter may use a first precoder matrix for a first bandwidth and a second precoder matrix for a second bandwidth. For example, the first and second precoder matrices may differ based on the difference between the first and second bandwidths. The wireless device may assume that the same precoder matrix is ​​used across a set of PRBs. This set of PRBs may be identified / indicated / identified as a Precoded Resource Block Group (PRG).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0143] Figure 13AAn example four-step random access procedure is shown. A four-step random access procedure may include a four-step contention-based random access procedure. Base station 1302 may, for example, send / transmit configuration message 1310 to radio device 1301 before initiating the random access procedure. The four-step random access procedure may include the transmission of four messages, including: a first message (e.g., Msg 11311), 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.

[0144] 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 radio device 1301. The one or more RACH parameters may include at least one of the following: general parameters for one or more random access procedures (e.g., RACH-configGeneral); cell-specific parameters (e.g., RACH-ConfigCommon); and / or dedicated parameters (e.g., RACH-configDedicated). Base station 1302 may send / transmit (e.g., broadcast or multicast) the one or more RRC messages to one or more radio devices. The one or more RRC messages may be radio device-specific. Radio device-specific RRC messages may be, for example, dedicated RRC messages sent / transmitted to radio device 1301 in an RRC connected (e.g., RRC_CONNECTED) state and / or in an RRC inactive (e.g., RRC_INACTIVE) state. The wireless device can determine time-frequency resources and / or uplink transmission power for transmitting a first message (e.g., Msg 1 1311) and / or a third message (e.g., Msg 3 1313) based on one or more of the RACH parameters. The wireless device 1301 can, for example, determine the receive timing and downlink channel for receiving a second message (e.g., Msg 2 1312) and a fourth message (e.g., Msg 4 1314) based on the one or more RACH parameters.

[0145] The one or more RACH parameters provided / configured / included in configuration message 1310 may indicate one or more physical RACH (PRACH) timings available for transmitting the first message (e.g., Msg 1 1311). The one or more PRACH timings may be predefined (e.g., via 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 timings (e.g., prach-ConfigIndex). The one or more RACH parameters may indicate an association between (a) one or more PRACH timings 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 of SS / PBCH blocks mapped to PRACH timings and / or the number of preambles mapped to SS / PBCH blocks.

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

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

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

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

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

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

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

[0153] Wireless device 1301 may, for example, send / transmit a third message (e.g., Msg 3 1313) based on (e.g., after or in response to) the successful reception of a second message (e.g., Msg 2 1312). This 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 base station 1302, and base station 1302 may send / transmit a RAR corresponding to wireless device 1301. For example, a conflict may occur if multiple wireless devices 1301 interpret the RAR as corresponding to themselves. Contention resolution (e.g., using a third message (e.g., Msg 3 1313) and a fourth message (e.g., Msg 4 1314)) may be used to increase the likelihood that wireless device 1301 will not mistakenly use the identity of another wireless device 1301. Wireless device 1301 may include a device identifier (e.g., TC RNTI in a second message (e.g., Msg 2 1312) if a C-RNTI is assigned, and / or any other suitable identifier) ​​in a third message (e.g., Msg 3 1313) for example, to perform contention resolution.

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

[0155] Wireless device 1301 may be configured with SUL carriers and / or NUL carriers. Initial access (e.g., random access) may be supported via an uplink carrier. Base station 1302 may configure multiple RACH configurations for wireless device 1301 (e.g., two separate RACH configurations, including one for the SUL carrier and another for the NUL carrier). For random access in a cell configured with an SUL carrier, the network 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 an NUL carrier) is below a broadcast threshold, wireless device 1301 may determine to use the SUL carrier. Uplink transmissions of random access procedures (e.g., a first message (e.g., Msg 1 1311) and / or a third message (e.g., Msg 3 1313)) may be maintained on or performed via the selected carrier. Wireless device 1301 can switch uplink carriers during random access procedures (e.g., between Msg 1 1311 and Msg 3 1313). Wireless device 1301 can determine and / or switch the uplink carrier for the first message (e.g., Msg 1 1311) and / or the third message (e.g., Msg 3 1313) based, for example, on channel idle assessment (e.g., listen-before-speak).

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

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

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

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

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

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

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

[0163] Transmit block 1342 may include data (e.g., delay-sensitive data), an identifier for radio device 1301, security information, and / or device information (e.g., International Mobile Subscriber Identity (IMSI)). Base station 1302 may send / transmit a second message (e.g., Msg B 1332) as a response to the first message (e.g., Msg A 1331). The second message (e.g., Msg B 1332) may include at least one of the following: a preamble identifier; a timing advance command; a power control command; uplink grant (e.g., radio resource allocation and / or MCS); a radio device identifier (e.g., a UE identifier for contention resolution); and / or an RNTI (e.g., a C-RNTI or 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 1301, and / or the identifier of the wireless device 1301 in the second message (e.g., Msg B 1332) corresponds to or matches the identifier of the wireless device 1301 in the first message (e.g., Msg A 1331) (e.g., transport block 1342), then the wireless device 1301 can determine that the two-step random access procedure has been successfully completed.

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

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

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

[0167] DCIs can be used for various purposes. The purpose can be indicated by the type of RNTI used to scramble the CRC parity bits. A DCI with CRC parity bits scrambled with the Paging RNTI (P-RNTI) can indicate paging information and / or system information change notifications. The P-RNTI can be predefined as hexadecimal "FFFE". A DCI with CRC parity bits scrambled with the System Information RNTI (SI-RNTI) can indicate broadcast transmission of system information. The SI-RNTI can be predefined as hexadecimal "FFFF". A DCI with CRC parity bits scrambled with the Random Access RNTI (RA-RNTI) can indicate a Random Access Response (RAR). A DCI with CRC parity bits scrambled with the Cell RNTI (C-RNTI) can indicate dynamically scheduled unicast transmissions and / or triggering of PDCCH ordered random access. A DCI with CRC parity bits scrambled with the Temporary Cell RNTI (TC-RNTI) can indicate contention resolution (e.g., similar to...). Figure 13A The Msg 3 shown is Msg 3 of 1313. Other RNTIs configured by the base station for the radio device may include the configured scheduling RNTI (CS RNTI), transmission power control PUCCH RNTI (TPC PUCCH-RNTI), transmission power control PUSCH RNTI (TPC-PUSCH-RNTI), transmission power control SRS RNTI (TPC-SRS-RNTI), interrupt RNTI (INT-RNTI), slot format indication RNTI (SFI-RNTI), semi-persistent CSI RNTI (SP-CSI-RNTI), modulation and coding scheme cell RNTI (MCS-C RNTI), etc.

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

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

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

[0171] 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., for the purpose of providing frequency diversity) or non-interleaved (e.g., for the purpose of facilitating interference coordination and / or frequency-selective transmission in the control channel). The base station can perform different or the same CCE-to-REG mapping for different CORESETs. CORESETs can be associated with CCE-to-REG mapping (e.g., via RRC configuration). CORESETs can be configured with antenna port QCL parameters. Antenna port QCL parameters can indicate the QCL information for DM-RS received via the PDCCH of the CORESET.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0195] The wireless device may, for example, receive one or more messages from a base station, the messages including one or more configuration parameters for a cell (e.g., LTM candidate cell, target cell, non-serving cell, LTM target cell, etc.) for LTM procedures. The wireless device may receive activation commands (e.g., MAC-CE, DCI, RRC messages, etc.) indicating cell handover for LTM procedures. The wireless device may, for example, hand over to the cell based on receiving the activation command indicating cell handover.

[0196] One or more configuration parameters may include TCI status parameters indicating the application of the CORESET (Control Resource Set) of the cell's downlink BWP. The TCI status parameters indicating the application of the CORESET may, for example, be set to 'none,' which indicates that the indicated TCI status is not applied to the CORESET. For example, an activation command may indicate a TCI status (e.g., combined / downlink TCI status). The activation command may include a TCI status field indicating / identifying the TCI status (e.g., TCI status ID). The activation command may include a TCI code point indicating the TCI status.

[0197] In at least some wireless communications, for example, if the TCI status parameter indicated by the CORESET application is set to 'none', the wireless device can monitor the downlink control channel (e.g., PDCCH) based on the TCI status indicated by the activation command, via the CORESET in the cell's downlink BWP and for receiving (e.g., DCI) the PDCCH. For example, after a cell handover (or after receiving an activation command), the wireless device can monitor the downlink control channel based on the TCI status, via the CORESET in the cell's downlink BWP and for receiving (e.g., DCI) the PDCCH. For example, the activation command can indicate at least two TCI states (e.g., at least two combined / downlink TCI states). This may be to support multiple transmit and receive points (TRPs) in the cell.

[0198] In at least some wireless communications, for example, if the TCI state parameter indicated by the CORESET application is set to 'none', the wireless device may monitor the downlink control channel (e.g., PDCCH) via the CORESET in the cell's downlink BWP based on at least two TCI states indicated by the activation command. This can be inefficient for, for example, a CORESET with a CORESET index equal to zero. The wireless device may not monitor the downlink control channel via a CORESET with a CORESET index equal to zero based on at least two TCI states. For example, if the wireless device and the base station are misaligned on the TCI states used by the wireless device to monitor a CORESET with a CORESET index equal to zero in at least two TCI states, the wireless device may not successfully receive the PDCCH via / in the CORESET. This can increase the bit error rate, increase retransmissions, and increase latency.

[0199] As described herein, for example, CORESET monitoring can be enhanced if the cell handover activation command indicates at least two TCI states. For instance, the activation command may include a field indicating one of at least two TCI states to monitor the CORESET of the cell's downlink BWP. The radio device can monitor the downlink control channel based on the TCI state indicated by the activation command via the CORESET in the cell's downlink BWP.

[0200] The radio device can monitor the downlink control channel via the CORESET in the cell's downlink BWP, for example, based on the TCI state with the lowest TCI state index among at least two TCI state indices. The radio device can also monitor the downlink control channel via the CORESET in the cell's downlink BWP, for example, based on the first TCI state that appears first in the set / vector / list of at least two TCI states (or is in the lower / higher octet in the activation command). This can reduce bit error rate, retransmissions, and / or latency.

[0201] In at least some wireless communications, if the activation command includes a timing advance command (or the value of a timing advance command) that is not set to a predefined value (e.g., FFF), the activation command may indicate the TCI state (or may include a TCI state field or TCI code point). The activation command may indicate, for example, the TCI state of an LTM without RACH (e.g., downlink TCI state, joint TCI state, or uplink TCI state).

[0202] In at least some wireless communications, if the activation command includes a timing advance command (or the value of the timing advance command) set to a predefined value (e.g., FFF), the activation command may not indicate the TCI state (or may not include a TCI state field or TCI code point). The wireless device may determine the spatial domain transmit / receive filter, for example, based on a random access procedure that can be initiated by an LTM procedure.

[0203] One or more configuration parameters may include parameters (e.g., enable-UE-TA) that enable the radio device to perform timing advance measurements on candidate cells (e.g., target cell, non-serving cell, neighboring cell, LTM candidate cell, etc.). The radio device may send (e.g., transmit) a radio device capability message to the base station, which may indicate the radio device's support for timing advance measurements on candidate cells.

[0204] For example, if a radio device receives an activation command indicating cell handover, the radio device can initiate a random access procedure for LTM procedures without relying on one or more configuration parameters, including parameters such as enable-UE-TA. The radio device can determine the cell's timing advance value without performing / initiating a random access procedure (e.g., a procedure without RACH).

[0205] For example, based on one or more configuration parameters, including parameters such as enable-UE-TA, the activation command may include a timing advance command (or the value of the timing advance command) set to a predefined value (e.g., FFF). In at least some wireless communications, if the timing advance command (or the value of the timing advance command) is set to a predefined value (e.g., FFF), the activation command may not indicate the TCI state. For example, if the radio device lacks knowledge of the spatial domain transmit / receive filters to be used after cell handover, it may be inefficient for RACH-free procedures. This can lead to increased bit error rates and decreased data rates.

[0206] For example, if one or more configuration parameters include a parameter (e.g., enable-UE-TA), the TCI status indication in the activation command can be enhanced. As described herein, if one or more configuration parameters include a parameter (e.g., enable-UE-TA), the activation command can indicate the TCI status (or may include a TCI status field or TCI code point). The activation command can indicate the TCI status (or may include a TCI status field or TCI code point) based, for example, on one or more configuration parameters including a parameter (e.g., enable-UE-TA). The base station can include / add the indication of the TCI status (e.g., TCI status field or TCI code point) based, for example, on one or more configuration parameters including a parameter (e.g., enable-UE-TA). This can reduce the bit error rate and / or increase the data rate.

[0207] In a Layer 1 (L1) / Layer 2 (L2) triggered Mobility Transaction (LTM) procedure, the base station can receive an L1 measurement report from the radio device. Based on the L1 measurement report, the base station can change the radio device's serving cell to a target cell (or candidate cell or LTM candidate cell) by sending / transmitting a cell handover command, which may be signaled via the MAC CE. The cell handover command may indicate an LTM candidate cell configuration that the base station may have previously prepared and sent / transmitted / provided to the radio device via RRC signaling. Based on the received cell handover command, the radio device can hand over to the target cell. The LTM procedure can be used to reduce mobility latency.

[0208] Cell handover commands can be triggered by a candidate configuration index containing the target cell. The radio device can then hand over to the target cell and apply the configuration that may be indicated by the candidate configuration index.

[0209] The base station may request the radio device to perform early timing advance (TA) acquisition of a candidate cell before cell handover, for example, via a PDCCH command and / or via UE-based TA measurement. Early TA acquisition can be triggered by a PDCCH command and / or via UE-based TA measurement. In UE-based TA measurement, the radio device may derive the TA value of the candidate cell, for example, based on the receiving (reception, Rx) timing difference between the current serving cell and the candidate cell, and the TA value of the current serving cell.

[0210] The base station can indicate in the cell handover command whether the radio device should use the RA procedure to access the target cell if the TA value is not provided / included in the cell handover command, or use the PUSCH transmission to access the target cell using the TA value indicated in the cell handover command. For LTM without RACH, the radio device can monitor the PDCCH during LTM cell handover to obtain dynamic scheduling from the target cell, or it can choose a configured grant timing associated with the beam indicated in the cell handover command.

[0211] A supervisory timer can be used to detect cell handover failures during the LTM procedure. For example, if the supervisory timer expires, the LTM procedure may fail. The radio device can, for example, initiate an RRC connection re-establishment procedure based on the expiration of the supervisory timer.

[0212] Cell handover commands can be transmitted in the MAC CE. Cell handover commands may include / contain / contain information required to perform LTM cell handover. LTM procedures may support, for example, intra-gNB DUs. LTM procedures may support, for example, intra-gNB CUs and inter-gNB DUs mobility. LTM procedures may support inter-frequency mobility, including mobility to inter-frequency cells that are not currently serving cells. The following scenarios can be supported: PCell change scenarios in non-CA, PCell change scenarios in carrier aggregation (CA), dual connectivity scenarios, and at least for PSCell changes without MN participation (e.g., intra-SN PSCell changes).

[0213] Figure 17 An example of an LTM program is shown. (See also: Regarding...) Figure 17The radio device 1701 (e.g., UE) may send a MeasurementReport 1710 (e.g., a MeasurementReport message) to the base station 1702 (e.g., a gNB). The base station 1702 may decide to configure LTM and may initiate candidate cell preparation. The base station 1702 may send (e.g., transmit) an RRCReconfiguration message 1720 to the radio device 1701, containing / including the LTM candidate cell configuration of one or more candidate cells. The radio device 1701 may store the LTM candidate cell configuration and may send (e.g., transmit) an RRCReconfigurationComplete message 1730 to the base station 1702.

[0214] Radio device 1701 may, for example, perform downlink (DL) synchronization 1740 with the candidate cell before receiving a cell handover command. Radio device 1701 may, for example, perform early TA acquisition of the candidate cell requested by base station 1702 before receiving a cell handover command. This can be accomplished via contention-free random access (CFRA) triggered by a PDCCH command from the source cell, after which radio device 1701 can send a preamble to the indicated candidate cell. Radio device 1701 may not receive RAR for the purpose of TA value acquisition and may indicate the TA value of the candidate cell in the cell handover command, for example, to minimize (or reduce) data interruption of the source cell due to CFRA of the candidate cell. Radio device 1701 may not maintain a TA timer for the candidate cell and may rely on network implementation to guarantee TA validity.

[0215] Wireless device 1701 can perform L1 measurements on configured candidate cells and can send (e.g., transmit) lower-layer measurement reports to base station 1702. Base station 1702 can decide to perform a cell handover to a target cell and can send (e.g., transmit) a MAC CE that triggers the cell handover by including a candidate configuration index of the target cell. Wireless device 1701 can handover to the target cell and can apply the configuration indicated by the candidate configuration index. If wireless device 1701 may not have a valid TA for the target cell, wireless device 1701 can perform a random access procedure for the target cell.

[0216] Radio device 1701 can complete the LTM cell handover procedure, for example, by sending an RRCReconfiguration Complete message 1730 to the target cell. If radio device 1701 has already performed the random access procedure in step 7, radio device 1701 can consider the LTM execution to have been successfully completed if the random access procedure has been successfully completed. For LTM without RACH, radio device 1701 can consider the LTM execution to have been successfully completed if it determines that the network has successfully received its first uplink (UL) data.

[0217] Figure 18 An example method of cell handover is illustrated. For example, wireless device 1801 can receive one or more messages. For example, wireless device 1801 can receive one or more messages from a base station. The base station can send (e.g., transmit) one or more messages. For example, wireless device 1801 can receive one or more messages from a relay node. For example, wireless device 1801 can receive one or more messages from another wireless device (e.g., TRP, vehicle, remote wireless head, etc.). One or more messages may include one or more configuration parameters 1810 (e.g., ...). Figure 18Configuration parameter 1810 at time T0. For example, one or more configuration parameters 1810 can be one or more RRC configuration parameters. One or more configuration parameters 1810 can be one or more RRC reconfiguration parameters (e.g., RRCReconfiguration, reconfigurationWithSync). For example, one or more messages can be one or more RRC messages. For example, one or more messages can be one or more RRC reconfiguration messages (e.g., RRCReconfiguration, reconfigurationWithSync). For example, one or more configuration parameters 1810 can be used for a cell. The cell can be, for example, a serving cell. For example, at least one of the configuration parameters 1810 can be used for a cell. For example, the cell can be a primary cell (PCell). For example, the cell can be a primary secondary cell (PSCell). For example, the cell can be a secondary cell (SCell). The cell can be a secondary cell configured with a PUCCH (e.g., PUCCH SCell). For example, the cell can be a special cell (SpCell). For dual connectivity (DC) operation, SpCell can refer to (or indicate) the PCell of the MCG or the PUCell of the SCG. For example, SpCell can refer to (or indicate) the PCell. For example, the cell could be the primary SCG cell (PSCell). For dual connectivity operation, if a reconfiguration and synchronization procedure is performed, the radio device 1801 could perform a random access procedure, for example, via the PSCell. For example, the cell could be a non-serving cell (e.g., a neighboring cell).

[0218] A cell can be a Layer 1 / Layer 2 triggered mobility (LTM) candidate cell. A cell can be a candidate cell for an LTM procedure. A cell can be a target cell for an LTM procedure. A cell can be an LTM target cell. A cell can be an LTM candidate cell. For example, a cell can be an unlicensed cell, operating, for example, in an unlicensed frequency band. For example, a cell can be a licensed cell, operating, for example, in a licensed frequency band. For example, a cell can operate in a first frequency range (FR1). FR1 can, for example, include frequency bands below 6 GHz. For example, a cell can operate in a second frequency range (FR2). FR2 can, for example, include frequency bands from 24 GHz to 52.6 GHz. For example, a cell can operate in a third frequency range (FR3). FR3 can, for example, include frequency bands from 52.6 GHz to 71 GHz. FR3 can, for example, include frequency bands starting at 52.6 GHz (or above 52.6 GHz).

[0219] One or more configuration parameters 1810 may indicate one or more control resource sets (CORESETs). One or more configuration parameters 1810 may indicate one or more CORESETs for a downlink BWP used in a cell. A downlink BWP may include one or more CORESETs. For example, one or more configuration parameters 1810 may indicate one or more CORESET indices / identifiers / indicators for one or more CORESETs (e.g., provided by the higher-level parameter ControlResourceSetId). For example, each CORESET in one or more CORESETs may be identified / indicated by a corresponding CORESET index / identifier / indicator in one or more CORESET indices. For example, a first CORESET in one or more CORESETs may be identified by a first CORESET index in one or more CORESET indices. A second CORESET in one or more CORESETs may be identified by a second CORESET index in one or more CORESET indices.

[0220] One or more configuration parameters 1810 can indicate multiple search space sets for a cell's downlink BWP (e.g., via a higher-layer parameter SearchSpace). For example, one or more configuration parameters 1810 can indicate multiple search space sets for a cell (e.g., via a higher-layer parameter SearchSpace). One or more configuration parameters 1810 can indicate multiple search space set indices / identifiers for the multiple search space sets (e.g., provided by a higher-layer parameter searchSpaceId). For example, each search space set in the multiple search space sets can be identified / indicated by a corresponding search space set index in the multiple search space set indices. For example, a first search space set in the multiple search space sets can be identified by a first search space set index in the multiple search space set indices. For example, a second search space set in the multiple search space sets can be identified by a second search space set index in the multiple search space set indices. For example, a search space set in the multiple search space sets can be associated with (or linked to) a CORESET in one or more CORESETs. For example, one or more configuration parameters 1810 may indicate a CORESET (and / or a CORESET index of a CORESET) for a search space set (e.g., provided by the higher-level parameter controlResourceSetId in the higher-level parameter SearchSpace). For example, associations (or links) may be one-to-one. A one-to-one association may include a search space set associated with (or linked to) the CORESET that is not associated with (or linked to) a second CORESET different from the CORESET. One or more CORESETs may include a second CORESET.

[0221] Wireless device 1801 can monitor PDCCH transmission / reception for DCI in / via one or more CORESETs. Monitoring PDCCH transmission / reception for DCI in a CORESET may include monitoring PDCCH candidates for DCI during PDCCH monitoring times associated with (or linked to) a search space set (or associated with) the CORESET. Multiple search space sets may include the search space sets. For example, based on the search space set being associated with (or linked to) the CORESET, wireless device 1801 can monitor PDCCH candidates for DCI during PDCCH monitoring times of the search space set in the CORESET. For example, based on the search space set being associated with (or linked to) the CORESET, wireless device 1801 can monitor PDCCH transmission / reception for DCI in the CORESET within the search space set.

[0222] Wireless device 1801 can monitor downlink control channels for a DCI in or via one or more CORESETs. Monitoring downlink control channels for a DCI in a CORESET may include monitoring one or more PDCCH candidates for the DCI in one or more PDCCH monitoring moments within one or more search space sets associated with the CORESET. Multiple search space sets may include the one or more search space sets. Wireless device 1801 can monitor corresponding PDCCH candidates for one or more PDCCH candidates in each of the one or more PDCCH monitoring moments for the DCI. One or more configuration parameters 1810 may indicate one or more PDCCH candidates for one or more search space sets. One or more configuration parameters 1810 may indicate corresponding PDCCH candidates among one or more PDCCH candidates for each of the one or more search space sets. Wireless device 1801 can determine one or more PDCCH monitoring moments for one or more search space sets based on one or more search space set configuration parameters (e.g., IE SearchSpace). One or more search space set configuration parameters can indicate one or more PDCCH monitoring periods for one or more search space sets (e.g., monitoringSlotPeriodicityAndOffset). One or more search space set configuration parameters can indicate a corresponding PDCCH monitoring period within one or more PDCCH monitoring periods for each of the one or more search space sets. Wireless device 1801 can determine one or more PDCCH monitoring times, for example, based on one or more PDCCH monitoring periods. One or more search space set configuration parameters can indicate PDCCH monitoring symbols for one or more search space sets (e.g., monitoringSymbolsWithinSlot). One or more search space set configuration parameters can indicate a corresponding PDCCH monitoring symbol within one or more search space sets (e.g., monitoringSymbolsWithinSlot). Wireless device 1801 can determine one or more PDCCH monitoring times, for example, based on PDCCH monitoring symbols.

[0223] One or more configuration parameters 1810 may indicate one or more CORESET indices for multiple search space sets (e.g., provided by the higher-level parameter controlResourceSetId in the higher-level parameter SearchSpace). For example, each search space set in the multiple search space sets may be associated with (or linked to) a corresponding CORESET in one or more CORESETs. For example, one or more configuration parameters 1810 may indicate a first CORESET index for a first CORESET for a first search space set. One or more configuration parameters 1810 may indicate a first CORESET index for a first CORESET in the CORESET index field of the first search space set (e.g., provided by the higher-level parameter controlResourceSetId in the higher-level parameter SearchSpace). Based on one or more configuration parameters 1810 indicating a first CORESET index for a first CORESET for a first search space set, the first search space set may be associated with (or linked to) a first CORESET. For example, one or more configuration parameters 1810 may indicate a first CORESET index for a first CORESET for a second search space set. One or more configuration parameters 1810 may indicate the first CORESET index of the first CORESET in the CORESET index field of the second search space set (e.g., provided by the higher-level parameter controlResourceSetId in the higher-level parameter SearchSpace). Based on one or more configuration parameters 1810 indicating the first CORESET index of the first CORESET for the second search space set, the second search space set may be associated with (or linked to) the first CORESET. For example, one or more configuration parameters 1810 may indicate the second CORESET index of the second CORESET for the first search space set. Based on one or more configuration parameters 1810 indicating the second CORESET index of the second CORESET for the first search space set, the first search space set may be associated with (or linked to) the second CORESET. For example, one or more configuration parameters 1810 may indicate the second CORESET index of the second CORESET for the second search space set. Based on one or more configuration parameters 1810 indicating the second CORESET index of the second CORESET for the second search space set, the second search space set may be associated with (or linked to) the second CORESET.

[0224] One or more first search space sets among multiple search space sets can be common search space (CSS) sets. One or more configuration parameters 1810 can include a search space type parameter (e.g., searchSpaceType) equal to or set to 'CSS' (or 'common') for one or more first search space sets. One or more configuration parameters 1810 can include a search space type parameter equal to or set to 'CSS' for each search space set among one or more first search space sets. One or more configuration parameters 1810 can include a corresponding search space type parameter equal to or set to 'CSS' for each search space set among one or more first search space sets.

[0225] The CSS set can include the Type0-PDCCH CSS set (configured by pdcch-ConfigSIB1 in the MIB, searchSpaceSIB1 in PDCCH-ConfigCommon, or searchSpaceZero in PDCCH-ConfigCommon). The wireless device can monitor PDCCH transmission / reception in the Type0-PDCCH CSS set for DCI formats with CRCs scrambled by SI-RNTI. The CSS set can include the Type0A-PDCCH CSS set (configured by searchSpaceOtherSystemInformation in PDCCH-ConfigCommon). The wireless device can monitor PDCCH transmission / reception in the Type0A-PDCCH CSS set for DCI formats with CRCs scrambled by SI-RNTI. The CSS set can include the Type1-PDCCH CSS set (configured by ra-SearchSpace in PDCCH-ConfigCommon). The wireless device can monitor PDCCH transmission / reception in the Type1-PDCCH CSS set for DCI formats with CRCs scrambled by RA-RNTI, MsgB-RNTI, or TC-RNTI. The CSS set can include the Type2-PDCCH CSS set (configured by pagingSearchSpace in PDCCH-ConfigCommon). The wireless device can monitor PDCCH transmission / reception in the Type2-PDCCH CSS set for DCI formats with CRCs scrambled by P-RNTI. The CSS set can include the Type3-PDCCH CSS set (configured by SearchSpace in PDCCH-Config, where searchSpaceType = common). The wireless device can monitor PDCCH transmission / reception in the Type3-PDCCH CSS set for DCI formats with CRCs scrambled by RNTI. RNTI can be, for example, INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, or CI-RNTI. RNTI can be, for example, C-RNTI, MCS-C-RNTI, CS-RNTI, or PS-RNTI. For instance, if the cell is a primary cell, the RNTI can be C-RNTI, MCS-C-RNTI, CS-RNTI, or PS-RNTI.

[0226] One or more second search space sets among multiple search space sets can be user-specific search space (USS) sets. One or more configuration parameters 1810 can include a search space type parameter (e.g., searchSpaceType) equal to or set to 'USS' (or 'user-specific') for one or more second search space sets. One or more configuration parameters 1810 can include a search space type parameter equal to or set to 'USS' for each search space set among one or more second search space sets. One or more configuration parameters 1810 can include a corresponding search space type parameter equal to or set to 'USS' for each search space set among one or more second search space sets. The wireless device can monitor PDCCH transmission / reception in the USS set for a DCI format with a CRC scrambled by RNTI. The USS set can include a USS set. The RNTI can be, for example, C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, CS-RNTI, SL-RNTI, SL-CS-RNTI, or SL semi-persistent scheduling V-RNTI.

[0227] One or more CORESETs may include a CORESET. The CORESET index in one or more CORESET indices may be indicated / identified by the CORESET. The CORESET index may, for example, be equal to zero (e.g., CORESET 0 1800, indicated by the higher-level parameter controlResourceSetZero). The CORESET index may, for example, be different from zero.

[0228] One or more search space sets among multiple search space sets can be associated with (or linked to) a CORESET in one or more CORESETs. A CORESET can be indicated / identified by a CORESET index in one or more CORESET indices. One or more configuration parameters 1810 can indicate a CORESET (or a CORESET index of a CORESET) for one or more search space sets. One or more configuration parameters 1810 can indicate one or more search space sets for a CORESET. A wireless device can monitor one or more PDCCH candidates in a CORESET for a DCI. A wireless device can monitor one or more PDCCH candidates for a DCI in one or more PDCCH monitoring moments of one or more search space sets. One or more PDCCH monitoring moments can be associated with one or more search space sets. Each PDCCH monitoring moment in one or more PDCCH monitoring moments can be associated with a corresponding search space set in one or more search space sets. Each search space set in one or more search space sets can be associated with a corresponding PDCCH monitoring moment in one or more PDCCH monitoring moments. One or more configuration parameters 1810 can indicate one or more PDCCH candidates for one or more search space sets. One or more configuration parameters 1810 can indicate the corresponding PDCCH candidate from one or more PDCCH candidates for each of one or more search space sets.

[0229] At least one search space set in one or more search space sets of CORESET can be a CSS set other than the Type3-PDCCH CSS set. One or more first search space sets in multiple search space sets can include at least one search space set. A CSS set can include at least one search space set. CORESET can be associated with one or more CSS sets other than the Type3-PDCCH CSS set. For example, a CSS set can be at least: Type0-PDCCH CSS set, Type0A-PDCCH CSS set, Type0B-PDCCH CSS set, Type1-PDCCH CSS set, Type1A-PDCCH CSS set, Type2-PDCCH CSS set, or Type2A-PDCCH CSS set. For example, one or more search space sets can be / include the Type0-PDCCH CSS set and the USS set. At least one search space set is the Type0-PDCCH CSS set. For example, one or more search space sets can be / include the Type1-PDCCH CSS set, Type2-PDCCH CSS set, Type3-PDCCH CSS set, and the USS set. At least one search space set is the Type1-PDCCH CSS set and the Type2-PDCCH CSS set.

[0230] A search space set in one or more search space sets of CORESET (or associated with CORESET) can be a CSS set. At least one search space set can be / includes a CSS set. One or more configuration parameters 1810 can indicate a search space set index (e.g., searchSpaceID) for a CSS set. Multiple search space set indexes / identifiers can include search space set indexes.

[0231] One or more configuration parameters 1810 may include one or more common downlink control channel parameters (e.g., PDCCH-ConfigCommon). For example, one or more common downlink control channel parameters may include search space parameters that indicate / configure the CSS set. The search space parameter may be, for example, pdcch-ConfigSIB1 in the master information block (MIB). The search space parameter may be, for example, searchSpaceSIB1. The search space parameter may be, for example, searchSpaceZero. The search space parameter may be, for example, searchSpaceOtherSystemInformation. The search space parameter may be, for example, pagingSearchSpace. For example, the search space set index of the CSS set may be equal to zero (e.g., searchSpaceID = 0, searchSpaceZero). For example, the search space set index of the CSS set may be different from zero. For example, CORESET may be associated with a CSS set having search space set indices (e.g., configured / indicated by searchSpaceZero) of a Type0-PDCCH CSS set, a Type0A-PDCCH CSS set, and / or a Type2-PDCCH CSS set. For example, a CSS set can be a Type0-PDCCH CSS set (e.g., indicated / configured by pdcch-ConfigSIB1 in MIB, searchSpaceSIB1 in PDCCH-ConfigCommon, and searchSpaceZero in PDCCH-ConfigCommon). For example, a CSS set can be a Type0A-PDCCH CSS set (e.g., indicated / configured by searchSpaceOtherSystemInformation in PDCCH-ConfigCommon). For example, a CSS set can be a Type2-PDCCH CSS set (e.g., indicated / configured by pagingSearchSpace in PDCCH-ConfigCommon). For example, each search space set in one or more search space sets of a CORESET can be a USS set. A CORESET may not be associated with any CSS set other than the Type3-PDCCH CSS set. One or more second search space sets in multiple search space sets may include one or more search space sets. A USS set may include one or more search space sets. A CORESET may be associated with one or more USS sets and / or the Type3-PDCCH CSS set.

[0232] One or more configuration parameters 1810 may indicate / include TCI state parameters (e.g., apply-IndicatedTCIState) for CORESET. For example, CORESET (e.g., Figure 18 The TCI status parameter indicated by the application of CORESET 0 1800 can be set to 'None'. For example, CORESET (e.g., Figure 18 The TCI status parameter indicated by the application of CORESET 1 can be set to 'first'. For example, CORESET (e.g., Figure 18 The TCI status parameter indicated by the application of CORESET 1 can be set to 'second'. For example, CORESET (e.g., Figure 18 The TCI status parameter indicated by the application of CORESET 1) can be set to 'both'.

[0233] A CORESET application indication TCI status parameter set to 'first' indicates that the first indicated TCI status of at least two indicated TCI statuses should be applied to the CORESET. The radio device can monitor the downlink control channel via the CORESET based on the first indicated TCI status. A CORESET application indication TCI status parameter set to 'second' indicates that the second indicated TCI status of at least two indicated TCI statuses should be applied to the CORESET. The radio device can monitor the downlink control channel via the CORESET based on the second indicated TCI status. A CORESET application indication TCI status parameter set to 'both' indicates that both the first indicated TCI status and the second indicated TCI status of at least two indicated TCI statuses should be applied to the CORESET. The radio device can monitor the downlink control channel via the CORESET based on the TCI status of each of the at least two indicated TCI statuses. A CORESET application indication TCI status parameter set to 'none' indicates that no indicated TCI status of any of the at least two indicated TCI statuses should be applied to the CORESET. A CORESET application indication TCI status parameter set to 'None' can indicate that the indicated TCI status of at least two indicated TCI statuses should not be applied to the CORESET. The radio device can monitor the downlink control channel via the CORESET based on the TCI status indicated / activated by the MAC-CE. The base station can, for example, send (e.g., transmit) a MAC-CE activating the TCI status of the CORESET based on the CORESET application indication TCI status parameter set to 'None'. The MAC-CE can indicate the activation of the CORESET's TCI status.

[0234] A cell may include multiple Transmit and Receive Points (TRPs). Multiple TRPs may serve the cell (or may serve radio devices within / via the cell). Multiple TRPs may include a first TRP and a second TRP.

[0235] One or more configuration parameters 1810 may indicate multiple TCI states. One or more configuration parameters may indicate a list 1802 of TCI states that includes multiple TCI states (e.g., provided by a higher-level (e.g., RRC) parameter dl-OrJoint-TCIStateList). One or more configuration parameters 1810 may include, for example, one or more PDSCH configuration parameters (e.g., PDSCH-Config) indicating multiple TCI states. For example, in... Figure 18 In the TCI, there are multiple TCI states: TCI state 0, TCI state 1, TCI state 2, ... and TCI state M.

[0236] One or more configuration parameters 1810 can indicate multiple TCI state indices / identifiers / identities (e.g., TCI-StateId) for multiple TCI states. One or more configuration parameters 1810 can indicate a corresponding TCI state index among multiple TCI state indices for each of the multiple TCI states. Each of the multiple TCI states can be indicated / identified by a corresponding TCI state index among multiple TCI state indices. For example, one or more configuration parameters 1810 can indicate a first TCI state index among multiple TCI state indices for a first TCI state. One or more configuration parameters 1810 can indicate a second TCI state index among multiple TCI state indices for a second TCI state.

[0237] One or more configuration parameters 1810 can indicate multiple TCI states, which indicate a unified TCI state for the cell. One or more configuration parameters 1810 may include, for example, one or more PDSCH configuration parameters for the cell's downlink BWP. One or more configuration parameters 1810 can indicate multiple TCI states for the cell's downlink BWP.

[0238] One or more configuration parameters 1810 may include, for example, one or more PDSCH configuration parameters for a second downlink BWP of a second cell. One or more configuration parameters 1810 indicate multiple TCI states of the second downlink BWP of the second cell. One or more configuration parameters 1810 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) identifying / indicating the second downlink BWP. The reference unified TCI state list parameter may include a cell index (e.g., ServCellIndex) identifying / indicating 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 downlink BWP of the cell may be a target BWP of the target cell. For example, the downlink BWP for a cell may include a reference to the unified TCI state list parameter based on one or more configuration parameters 1810. One or more PDSCH configuration parameters of the cell's downlink BWP may not include the higher-layer (e.g., RRC) parameter dl-OrJoint-TCIStateList.

[0239] One or more configuration parameters 1810 may include a unified TCI state type parameter (e.g., unifiedtci-StateType). One or more configuration parameters 1810 may include one or more serving cell parameters (e.g., ServingCellConfig), which include the unified TCI state type parameter. The unified TCI state type parameter may indicate the unified TCI state type of the cell. For example, the unified TCI state type parameter may be set to "joint". The radio device may, for example, use / apply multiple TCI states (e.g., provided / indicated by dl-OrJoint-TCIStateList) for / to both uplink transmissions (e.g., PUSCH / PUCCH / SRS transmissions) and downlink receptions (e.g., PDCCH / PDSCH / CSI-RS receptions) of the cell, based on one or more configuration parameters 1810 including the unified TCI state type parameter set to "joint". For example, the unified TCI state type parameter may be set to "separate". The radio device may, for example, include a unified TCI state type parameter set to "separate" based on one or more configuration parameters 1810, to use / apply multiple TCI states (e.g., provided / indicated by the higher-layer parameter dl-OrJoint-TCIStateList) for / apply to downlink reception (e.g., PDCCH / PDSCH / CSI-RS reception) of the cell. The radio device may, for example, not use / apply multiple TCI states for / apply to uplink transmission (e.g., PUSCH / PUCCH / SRS transmission) of the cell based on one or more configuration parameters 1810, including a unified TCI state type parameter set to "separate".

[0240] One or more configuration parameters 1810 can indicate a second or more TCI states. One or more configuration parameters 1810 can indicate an uplink TCI state list 1802 that includes the second or more TCI states (e.g., provided / indicated by the higher-layer parameter ul-TCI-StateList). One or more configuration parameters 1810 can include, for example, one or more uplink BWP configuration parameters for indicating the second or more TCI states. For example, in Figure 18 In the middle, the second and multiple TCI states are TCI state 1, TCI state 2, ... and TCI state M.

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

[0242] One or more configuration parameters 1810 may include, for example, one or more uplink BWP configuration parameters for a second uplink BWP of a second cell. One or more configuration parameters indicate a second plurality of TCI states for the second uplink BWP of the second cell. One or more configuration parameters 1810 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) identifying / indicating the second uplink BWP. The reference unified TCI state list parameter may include a cell index (e.g., ServCellIndex) identifying / indicating the second cell. The second uplink BWP of the second cell may be a reference BWP of a reference cell for the cell's uplink BWP. The uplink BWP of the cell may be a target BWP of the target cell. For example, the uplink BWP for a cell based on one or more configuration parameters 1810 includes a reference to the unified TCI state list parameter. One or more uplink BWP configuration parameters for the cell's uplink BWP may not include higher-layer (e.g., RRC) parameters ul-TCI-StateList.

[0243] The radio device may, for example, use / apply a second plurality of TCI states for uplink transmissions (e.g., PUSCH / PUCCH / SRS transmissions) of the cell based on one or more configuration parameters 1810, including a unified TCI state type parameter set to "separate". The radio device may, for example, not use / apply the second plurality of TCI states for downlink receptions (e.g., PDCCH / PDSCH / CSI-RS receptions) of the cell based on one or more configuration parameters 1810, including a unified TCI state type parameter set to "separate". For example, the radio device may, for example, use the plurality of TCI states of the cell's downlink BWP for downlink reception via the cell's downlink BWP, indicating the plurality of TCI states based on one or more configuration parameters 1810. For example, the radio device may, for example, use the plurality of TCI states of the cell's downlink BWP for uplink transmission reception via the cell's uplink BWP, indicating the plurality of TCI states based on one or more configuration parameters 1810. For example, a wireless device may, for instance, instruct a second downlink BWP of a second cell for a cell based on reference to a unified TCI state list parameter, and use multiple TCI states of the second downlink BWP of the second cell for downlink reception via the cell's downlink BWP. Similarly, a wireless device may, for instance, instruct a second downlink BWP of a second cell for a cell based on reference to a unified TCI state list parameter, and use multiple TCI states of the second downlink BWP of the second cell for uplink transmission and reception via the cell's uplink BWP.

[0244] The wireless device may, for example, indicate a second plurality of TCI states of the uplink BWP of a cell based on one or more configuration parameters 1810, and use the second plurality of TCI states for uplink transmission and reception via the uplink BWP of the cell. For example, the wireless device may, for example, indicate a second uplink BWP of a second cell for the uplink BWP of a second cell based on reference to a unified TCI state list parameter, and use the second plurality of TCI states of the second uplink BWP of the second cell for uplink transmission and reception via the uplink BWP of the second cell.

[0245] The wireless device can receive activation commands (e.g., MAC-CE, DCI, RRC, control commands, downlink control commands / messages, unified TCI state activation / deactivation MAC CE, candidate cell TCI state activation / deactivation MAC CE, etc.). For example, the activation command can indicate the activation of a subset of TCI states from multiple TCI states (e.g., DLorJoint-TCIStateList). For example, the activation command can indicate the activation of a subset of TCI states from a second set of TCI states (e.g., ul-TCI-StateList). The base station can activate and / or deactivate the TCI states of LTM candidate cells, for example, by sending / transmitting activation commands (e.g., candidate cell TCI state activation / deactivation MAC CE). LTM candidate cells may include cells.

[0246] A wireless device can map a subset of TCI states to one or more TCI code points. An activation command can indicate the mapping of a subset of TCI states to one or more TCI code points. A wireless device can map a corresponding TCI state in a subset of TCI states to a corresponding TCI code point in one or more TCI code points. One or more TCI code points can indicate / include a subset of TCI states. Each TCI code point in one or more TCI code points can indicate (or be mapped to) a corresponding TCI state in a subset of TCI states. Each TCI code point in one or more TCI code points can indicate / include (or be mapped to) one or more TCI states. For example, a subset of TCI states could be TCI state 4, TCI state 5, TCI state 8, TCI state 26, and TCI state 61. One or more TCI code points can be / 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 / indicate TCI state 4. The second TCI code point (e.g., TCI code point 001) may include / indicate TCI states 5 and 8. The third TCI code point (e.g., TCI code point 110) may include / indicate TCI states 26 and 61. The fourth TCI code point (e.g., TCI code point 111) may include / indicate TCI state 26. For example, 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 combined TCI states, two uplink TCI states, two downlink TCI states, etc.). For example, the number of one or more TCI code points may be equal to one. One or more TCI code points may be a (single) TCI code point. For example, the number of one or more TCI code points can be greater than one.

[0247] One or more configuration parameters may include one or more LTM configuration parameters. One or more LTM configuration parameters may indicate a list of candidate cell configurations (e.g., ltm-CandidateTo AddModList). One or more LTM configuration parameters may indicate a corresponding LTM candidate index / identifier for each candidate cell configuration in the candidate cell configuration list (e.g., ltm-CandidateId). For example, one or more LTM configuration parameters may indicate a first LTM candidate index / identifier for a first candidate cell configuration in the candidate cell configuration list. The first LTM candidate index / identifier may indicate a first candidate cell configuration (e.g., LTM candidate cell configuration). One or more LTM configuration parameters may indicate a second LTM candidate index / identifier for a second candidate cell configuration in the candidate cell configuration list. The second LTM candidate index / identifier may indicate a second candidate cell configuration (e.g., LTM candidate cell configuration). One or more LTM configuration parameters may indicate a corresponding RRC reconfiguration message for configuring / corresponding to an LTM candidate cell for each candidate cell configuration in the candidate cell configuration list.

[0248] The wireless device can receive activation commands (e.g., MAC-CE, DCI, RRC, control commands, downlink control commands / messages, LTM cell handover commands, etc.). Activation commands (e.g., Figure 18 The first control command at time T1 in the LTM protocol can, for example, indicate a cell handover to a cell (e.g., candidate cell, LTM candidate cell) for an LTM handover (or LTM procedure). The base station can instruct the radio device to perform a cell handover in / for an LTM procedure by sending / transmitting an activation command (e.g., LTM Cell Handover Command MAC CE). The radio device can receive the activation command indicating the cell handover via / on the serving cell in PDSCH reception. The activation command may include multiple fields.

[0249] The first of the multiple fields may include an LTM candidate index / identifier (e.g., ltm-CandidateId) that indicates / identifies a candidate cell configuration (e.g., LTM candidate cell configuration) in the candidate cell configuration list. The LTM candidate index / identifier may indicate / identify the candidate cell configuration (e.g., RRC reconfiguration) that the radio device will apply for cell handover to a cell (e.g., for LTM handover).

[0250] One or more of the second fields can indicate at least two TCI states (e.g., Figure 18The at least two TCI states (e.g., first TCI state 1811 and second TCI state 1822) can be, for example, at least two joint TCI states. The at least two TCI states can, for example, at least two downlink TCI states. The at least two TCI states can include a first TCI state (e.g., first TCI state 1811) and a second TCI state (e.g., second TCI state). One or more of the second fields can indicate / activate at least two TCI states for a cell (or for an LTM target cell).

[0251] At least two TCI states can be / indicate at least two unified TCI states, for example, for applicable transmissions and / or receptions via / on the cell. At least two TCI states can be / indicate at least two unified combined / downlink TCI states, for example, for applicable downlink receptions (e.g., PDCCH reception, PDSCH reception, CSI-RS) via / on the cell.

[0252] Multiple TCI states in a TCI state list 1802 (e.g., dl-OrJoint-TCIStateList) may include at least two TCI states. For example, a subset of TCI states may include at least two TCI states. A first TCI state index among multiple TCI state indices / identifiers / identifiers may indicate / identify a first TCI state (e.g., first TCI state 1811). A second TCI state index among multiple TCI state indices / identifiers / identifiers may indicate / identify a second TCI state (e.g., second TCI state). For example, one or more second fields may include at least two TCI state indices identifying at least two TCI states. Each of the at least two TCI state indices may identify a corresponding TCI state among the at least two TCI states. The at least two TCI state indices may include a first TCI state index identifying a first TCI state and a second TCI state index identifying a second TCI state. Multiple TCI state indices of multiple TCI states may include at least two TCI state indices. One or more second fields may include a first field (e.g., TCI status ID) and a second field (e.g., TCI status ID 2), the first field including a first TCI status index identifying a first TCI status, and the second field including a second TCI status index identifying a second TCI status.

[0253] The first field, including the first TCI status index, may appear in / be in the first octet of the activation command indicating cell handover (or be located in the first octet). The second field, including the second TCI status index, may appear in / be in the second octet of the activation command indicating cell handover (or be located in the second octet). The first octet may be lower than / less than / less than the second octet. For example, the first octet may be octet 5, and the second octet may be octet 6. For example, the first octet may be octet 1, and the second octet may be octet 2. For example, the first octet may be octet 9, and the second octet may be octet 10. The base station may sort the first and second TCI status indices according to (or based on) their sequential position in the activation command. For example, the octet n of the activation command may include a first TCI state index that identifies / indicates the first TCI state, and the octet m of the activation command may include a second TCI state index that identifies / indicates the second TCI state, where n < m.

[0254] The activation command indicating cell handover may include a list / set / vector of at least two TCI states. The first TCI state in the list / set / vector of at least two TCI states may appear first in the list / set / vector of at least two TCI states. The first TCI state may be the first / starting / earliest / initial TCI state in the list / set / vector of at least two TCI states. The second TCI state in the list / set / vector of at least two TCI states may appear second in the list / set / vector of at least two TCI states. The second TCI state may be the last / latest / ending TCI state in the list / set / vector of at least two TCI states. For example, if the list / set / vector of at least two TCI states = [TCI state 5, TCI state 8], then the first TCI state is TCI state 5 and the second TCI state is TCI state 8. For example, if the list / set / vector of at least two TCI states = [TCI state 26, TCI state 61], then the first TCI state is TCI state 26 and the second TCI state is TCI state 61.

[0255] One or more second fields may be second fields. A second field may include / indicate a TCI code point among one or more TCI code points. For example, if the second field is equal to / set to '001', then the second field may indicate a second TCI code point (e.g., TCI code point 001) among one or more TCI code points. At least two TCI states in (or indicated by or mapped to) the second TCI code point (e.g., TCI code point 001) may include / are TCI state 5 and TCI state 8. For example, if the second field is equal to / set to '110', then the second field may indicate a third TCI code point (e.g., TCI code point 110) among one or more TCI code points. At least two TCI states in (or indicated by or mapped to) the third TCI code point may include / are TCI state 26 and TCI state 61.

[0256] For example, the activation command may not include the second field if the number of one or more TCI code points is equal to one. For example, the activation command may not include the second field if one or more TCI code points are (single) TCI code points. For example, after performing a cell handover to a cell, the radio device may apply one or more TCI states from a single TCI code point to uplink transmission and / or downlink reception via the cell. A subset of TCI states may include one or more TCI states.

[0257] For example, if the number of one or more TCI code points is greater than one, the activation command may include a second field. For example, if the one or more TCI code points are multiple TCI code points, the activation command may include a second field.

[0258] The third field among multiple fields may include a cell index (e.g., ServCellIndex) that indicates / identifies the cell. One or more configuration parameters can indicate the cell index for a cell.

[0259] The fourth field among the multiple fields may include a BWP index (e.g., BWP-id) that indicates / identifies the downlink BWP of the cell. One or more configuration parameters may indicate the BWP index for the downlink BWP.

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

[0261] The second TCI state can be the second unified TCI state (or can be used interchangeably with the second unified TCI state). The second TCI state can be the second combined TCI state (or can be used interchangeably with the second combined TCI state). The second TCI state can be the second downlink TCI state (or can be used interchangeably with the second downlink TCI state). The second TCI state can be the second combined / downlink TCI state (or can be used interchangeably with the second combined / downlink TCI state). The second TCI state can be the second uplink TCI state (or can be used interchangeably with the second uplink TCI state).

[0262] An activation command indicating the activation of a subset of TCI states may include multiple fields. The first field among these fields may indicate a first TCI state. For example, the first field may include a first TCI state index indicating / identifying the first TCI state. The first field may appear in / be in (or be located in) the first octet of the activation command. A second field among these fields may indicate a second TCI state. For example, the second field may include a second TCI state index indicating / identifying the second TCI state. The second field may appear in / be in (or be located in) the second octet of the activation command. The first octet may be lower than / less than / less than the second octet. For example, the first octet may be octet 5, and the second octet may be octet 6. For example, the first octet may be octet 1, and the second octet may be octet 2. For example, the first octet may be octet 9, and the second octet may be octet 10. The base station can sort the first TCI state index and the second TCI state index according to (or based on) the sequential position in the activation command. For example, the octet n of the activation command may include the first TCI state index that identifies / indicates the first TCI state, and the octet m of the activation command may include the second TCI state index that identifies / indicates the second TCI state, where n < m.

[0263] An activation command indicating the activation of a subset of TCI states can indicate / map / activate a list / set / vector of at least two TCI states for one or more TCI code points. The activation command can indicate a mapping / association / activation of the list / set / vector of at least two TCI states to the TCI code point. The at least two TCI states can include a first TCI state and a second TCI state. The first TCI state may appear first in the list / set / vector of at least two TCI states. The first TCI state may be the first / starting / earliest / initial TCI state in the list / set / vector of at least two TCI states. The second TCI state may appear second in the list / set / vector of at least two TCI states. The second TCI state may be the last / latest / ending TCI state in the list / set / vector of at least two TCI states. For example, if the list / set / vector of at least two TCI states = [TCI state 5, TCI state 8], then the first TCI state is TCI state 5 and the second TCI state is TCI state 8. For example, if a list / set / vector of at least two TCI states = [TCI state 26, TCI state 61], then the first TCI state is TCI state 26 and the second TCI state is TCI state 61.

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

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

[0266] The wireless device may transmit (e.g., transmit) an uplink transmission (e.g., PUCCH transmission, PUSCH transmission) having / carrying / indicating / including HARQ-ACK information feedback / bits for PDSCH reception during an uplink transmission timing (e.g., PUCCH transmission timing, PUSCH transmission timing), wherein the HARQ-ACK information feedback / bits include / contain / indicate / provide an activation command for cell handover. The wireless device may apply at least two TCI states (start) from a first / start / earliest time slot in the activation command for downlink reception and / or uplink transmission via the cell, the first / start / earliest time slot being the duration (or time gap or application time) following the last symbol of the uplink transmission (or uplink transmission timing). For example, the duration (or time gap or application time) may be fixed / predefined / preset. For example, one or more configuration parameters 1810 may indicate the duration (or time gap or application time). For example, wireless device 1801 may send (e.g., transmit) a wireless device (e.g., user equipment (UE)) capability message to a base station indicating the duration (or time gap or application time).

[0267] Wireless device 1801 can target DCI and via cell CORESET, for example based on at least two TCI states in the activation command (e.g., Figure 18 The PDCCH is monitored using the TCI states (first TCI state 1811 and second TCI state 1822) in the PDCCH, and the activation command can indicate cell handover. The radio device 1801 can monitor the PDCCH via CORESET, for example, based on the TCI state, for example, starting from the first / starting / earliest time slot.

[0268] Wireless device 1801 may, for example, switch to a cell as the primary cell (or as the target cell) based on receiving an activation command indicating cell handover to a cell. Wireless device 1801 may, for example, switch to a cell as the serving cell based on receiving an activation command indicating cell handover to a cell. Wireless device 1801 may, for example, activate a cell as the serving cell based on receiving an activation command indicating cell handover to a cell. Wireless device 1801 may, for example, switch from the current serving / primary cell to a cell as the new serving / primary cell based on receiving an activation command indicating cell handover to a cell.

[0269] The wireless device can monitor the PDCCH via CORESET, for example, after cell handover, based on the TCI state. The TCI state can be, for example, the default TCI state. The TCI state can be, for example, a joint TCI state among at least two joint TCI states. The TCI state can be, for example, a downlink TCI state among at least two downlink TCI states.

[0270] The radio device can receive DCI via the cell's CORESET, for example, based on the TCI state of at least two TCI states. Radio device 1801 can receive DCI via CORESET, for example, in or after the first / starting / earliest time slot, for example, based on the TCI state. Radio device 1801 can receive DCI via CORESET, for example, after cell handover, for example, based on the TCI state.

[0271] For example, based on (e.g., in response to) one or more configuration parameters including an application indication TCI status parameter of CORESET set to 'none', a wireless device can monitor the PDCCH based on the TCI status via CORESET.

[0272] For example, based on (e.g., in response to) one or more configuration parameters including an application indication TCI status parameter of CORESET set to 'none', a wireless device can receive DCI via CORESET based on the TCI status.

[0273] For example, based on (e.g., in response to) a CORESET index equal to zero, a wireless device can monitor the PDCCH via a CORESET-based TCI state. A wireless device can monitor the PDCCH via a CORESET-based TCI state where the CORESET index is zero.

[0274] For example, based on (e.g., in response to) a CORESET index equal to zero, a wireless device can receive DCI via a CORESET based on a TCI state. A wireless device can receive DCI via a CORESET with a CORESET index equal to zero based on a TCI state.

[0275] For example, if at least one search space set in one or more search space sets of CORESET is a CSS set other than the Type3-PDCCH CSS set, the wireless device can monitor the PDCCH based on the TCI state via CORESET. The wireless device can monitor the PDCCH based on the TCI state via CORESET associated with a CSS set other than the Type3-PDCCH CSS set. The CORESET index of CORESET can, for example, be different from zero. The CORESET index of CORESET can, for example, be equal to zero.

[0276] For example, if at least one search space set in one or more search space sets of CORESET is a CSS set other than the Type3-PDCCH CSS set, the wireless device can receive DCI via CORESET based on TCI state. The wireless device can receive DCI via CORESET based on TCI state associated with a CSS set other than the Type3-PDCCH CSS set. The CORESET index of CORESET can, for example, be different from zero. The CORESET index of CORESET can, for example, be equal to zero.

[0277] For example, based on (e.g., in response to) a CSS set associated with (or mapped to) a CORESET whose search space set index is zero (e.g., searchSpaceID = 0, searchSpaceZero), a wireless device can monitor the PDCCH based on the TCI state via the CORESET. The wireless device can monitor the PDCCH based on the TCI state via a CORESET associated with (or mapped to) a CSS set whose search space set index is zero. The CORESET index of the CORESET may, for example, be different from zero. The CORESET index of the CORESET may, for example, be equal to zero.

[0278] For example, based on (e.g., in response to) a CSS set associated with (or mapped to) a CORESET whose search space set index is zero (e.g., searchSpaceID = 0, searchSpaceZero), a wireless device can receive a DCI state based on a TCI state via a CORESET. The wireless device can receive a DCI state based on a TCI state via a CORESET associated with (or mapped to) a CSS set whose search space set index is zero. The CORESET index of the CORESET may, for example, be different from zero. The CORESET index of the CORESET may, for example, be equal to zero.

[0279] For example, a wireless device can monitor the PDCCH based on the TCI state via the CORESET, based on (e.g., in response to) a CSS set configured by pdcch-ConfigSIB1 in the MIB, searchSpaceSIB1, searchSpaceZero, searchSpaceOtherSystemInformation, or pagingSearchSpace in PDCCH-ConfigCommon. For example, a wireless device can monitor the PDCCH based on the TCI state via the CORESET, based on (e.g., in response to) a CSS set configured by at least one of the following: pdcch-ConfigSIB1 in the MIB, searchSpaceSIB1, searchSpaceZero, searchSpaceOtherSystemInformation, or pagingSearchSpace in PDCCH-ConfigCommon. A wireless device can monitor the PDCCH based on the TCI state via a CORESET associated with a CSS set configured by at least one of the following: pdcch-ConfigSIB1, searchSpaceSIB1, searchSpaceZero, searchSpaceOtherSystemInformation, or pagingSearchSpace. The CORESET index of a CORESET can, for example, be equal to zero. The CORESET index of a CORESET can, for example, be different from zero.

[0280] For example, a wireless device can receive DCI based on a CORESET associated with a CSS set configured by pdcch-ConfigSIB1 in the MIB, searchSpaceSIB1, searchSpaceZero, searchSpaceOtherSystemInformation, or pagingSearchSpace in the PDCCH-ConfigCommon. For example, a wireless device can receive DCI based on a CORESET associated with a CSS set configured by at least one of the following: pdcch-ConfigSIB1 in the MIB, searchSpaceSIB1, searchSpaceZero, searchSpaceOtherSystemInformation, or pagingSearchSpace in the PDCCH-ConfigCommon. A wireless device can receive DCI based on a TCI state via a CORESET associated with a CSS set configured by at least one of the following: pdcch-ConfigSIB1, searchSpaceSIB1, searchSpaceZero, searchSpaceOtherSystemInformation, or pagingSearchSpace. The CORESET index of a CORESET can, for example, be equal to zero. The CORESET index of a CORESET can, for example, be different from zero.

[0281] For example, based on (e.g., in response to) the CSS set (or CSS set of CORESET) associated with CORESET being a Type0-PDCCH CSS set, a Type0A-PDCCH CSS set, or a Type2-PDCCH CSS set, the wireless device can monitor the PDCCH based on the TCI state via CORESET. For example, based on (e.g., in response to) the CSS set (or CSS set of CORESET) associated with CORESET being at least one of the following: a Type0-PDCCH CSS set, a Type0A-PDCCH CSS set, and a Type2-PDCCH CSS set, the wireless device can monitor the PDCCH based on the TCI state via CORESET. For example, based on (e.g., in response to) CORESET being associated with a CSS set that is at least one of the following: a Type0-PDCCH CSS set, a Type0A-PDCCH CSS set, and a Type2-PDCCH CSS set, the wireless device can monitor the PDCCH based on the TCI state via CORESET. The wireless device can monitor the PDCCH based on the TCI state via a CORESET associated with at least one of the following CSS sets: Type 0-PDCCH CSS set, Type 0A-PDCCH CSS set, and Type 2-PDCCH CSS set. The CORESET index of the CORESET can, for example, be equal to zero. The CORESET index of the CORESET can, for example, be different from zero.

[0282] For example, based on (e.g., in response to) the CSS set associated with CORESET (or the CSS set of CORESET) being a Type0-PDCCH CSS set, a Type0A-PDCCH CSS set, or a Type2-PDCCH CSS set, a wireless device can receive DCI via CORESET based on TCI state. For example, based on (e.g., in response to) the CSS set associated with CORESET (or the CSS set of CORESET) being at least one of the following: a Type0-PDCCH CSS set, a Type0A-PDCCH CSS set, and a Type2-PDCCH CSS set, a wireless device can receive DCI via CORESET based on TCI state. For example, based on (e.g., in response to) CORESET being associated with a CSS set that is at least one of the following: a Type0-PDCCH CSS set, a Type0A-PDCCH CSS set, and a Type2-PDCCH CSS set, a wireless device can receive DCI via CORESET based on TCI state. The wireless device can receive DCI based on TCI status via a CORESET associated with at least one of the following CSS sets: Type 0-PDCCH CSS set, Type 0A-PDCCH CSS set, and Type 2-PDCCH CSS set. The CORESET index of the CORESET can, for example, be equal to zero. The CORESET index of the CORESET can, for example, be different from zero.

[0283] One or more configuration parameters may not indicate the SFN scheme for the cell's downlink control channel (e.g., sfnSchemePdcch). For example, based on (e.g., in response to) one or more configuration parameters not indicating the SFN scheme for the cell's downlink control channel (e.g., sfnSchemePdcch), the radio device can monitor the PDCCH via CORESET based on the TCI state. For example, based on (e.g., in response to) one or more configuration parameters not indicating the SFN scheme for the cell's downlink control channel (e.g., sfnSchemePdcch), the radio device can receive the DCI via CORESET based on the TCI state.

[0284] A wireless device can receive a DCI in a CORESET via a PDCCH. A wireless device can receive a PDCCH with / carrying a DCI in / via a CORESET. A wireless device can receive a PDCCH with / carrying a DCI in / via a CORESET and based on a TCI state. At least one DM-RS antenna port (e.g., PDCCH reception) of a PDCCH with a DCI can be quasi-co-located with a reference signal indicated by a TCI state. At least one DM-RS antenna port (e.g., PDCCH reception) of a PDCCH with a DCI can be quasi-co-located with a reference signal of a quasi-co-location type indicated by a TCI state. For example, if the TCI state is a first TCI state, at least one DM-RS antenna port (e.g., PDCCH reception) of a PDCCH with a DCI can be quasi-co-located with a first reference signal indicated by a first TCI state. At least one DM-RS antenna port (e.g., PDCCH reception) of a PDCCH with a DCI can be quasi-co-located with a first reference signal of a first quasi-co-location type indicated by a first TCI state. For example, if the TCI state is the second TCI state, at least one DM-RS antenna port (e.g., PDCCH receiver) of a PDCCH with DCI can be quasi-co-located with a second reference signal indicated by the second TCI state. At least one DM-RS antenna port (e.g., PDCCH receiver) of a PDCCH with DCI can be quasi-co-located with a second reference signal with respect to the second quasi-co-location type indicated by the second TCI state.

[0285] Wireless device 1801 can monitor PDCCH via CORESET, for example, based on TCI status, until it receives a third TCI status indicating CORESET (e.g., Figure 18 The activation of the second activation command (e.g., the third TCI state 1833 in the third TCI state) is the activation of the second activation command. Figure 18 The second control command 1830 at time T2, MAC-CE, DCI, RRC, control command, downlink control command / message, control command / message, UE-specific PDCCH MAC CE TCI status indication, etc.

[0286] For example, based on (e.g., in response to) receiving a second activation command indicating activation of the third TCI state 1833 (e.g., a second control command 1830), the wireless device 1801 can monitor the PDCCH via CORESET based on the third TCI state 1833. The wireless device 1801 can, for example, monitor the PDCCH via CORESET based on the third TCI state after receiving the second activation command indicating activation of the third TCI state. The wireless device 1801 can, for example, initiate PDCCH monitoring via CORESET based on the third TCI state after receiving the second activation command indicating activation of the third TCI state.

[0287] Wireless device 1801 can receive DCI via CORESET based on TCI state, for example, until it receives a third TCI state instructing CORESET (e.g., Figure 18 The activation of the second activation command (e.g., the third TCI state 1833 in the third TCI state) is the activation of the second activation command. Figure 18 The second control command at time T2, MAC-CE, DCI, RRC, control command, downlink control command / message, control command / message, UE-specific PDCCH MAC CE TCI status indication, etc.

[0288] For example, based on (e.g., in response to) receiving a second activation command indicating activation of a third TCI state, radio device 1801 can receive DCI via CORESET based on the third TCI state. For example, after receiving a second activation command indicating activation of a third TCI state, radio device can receive DCI via CORESET based on the third TCI state. For example, after receiving a second activation command indicating activation of a third TCI state, radio device can initiate DCI reception via CORESET based on the third TCI state. For example, the activation command indicating cell handover may include fields. Multiple fields of the activation command may include said fields.

[0289] The field can be, for example, a TCI selection field. The field can be, for example, a TCI indicator field. The field can be, for example, a TCI status selection field. The field can be, for example, a TCI status indicator field. The field can be, for example, a CORESET pool index field. The field can be, for example, a TRP field. The field can be, for example, an SRS resource set indicator field. The field can be, for example, a 1-bit field. The first value of the field (e.g., 0) can indicate a first TCI state. For example, based on the field being set to / equal to the first value in the activation command, the TCI state can be the first TCI state.

[0290] For example, based on (e.g., in response to) a field in an activation command being set to / equal to a first value, wireless device 1801 can monitor the PDCCH via CORESET, for example, based on a first TCI state. For example, based on (e.g., in response to) a field in an activation command being set to / equal to a first value, wireless device 1801 can receive the DCI via CORESET, for example, based on a first TCI state. A second value (e.g., 1) of the field can indicate a second TCI state. For example, based on a field in an activation command being set to / equal to a second value, the TCI state can be a second TCI state.

[0291] For example, based on (e.g., in response to) a field in an activation command being set to / equal to a second value, wireless device 1801 can monitor the PDCCH via CORESET, for example, based on a second TCI state. For example, based on (e.g., in response to) a field in an activation command being set to / equal to a second value, wireless device 1801 can receive the DCI via CORESET, for example, based on a second TCI state. For example, the TCI state index of at least two TCI states can be the lowest / smallest among at least two TCI state indices of at least two TCI states. The TCI state index of the TCI state can be the lowest / smallest among the first TCI state index of the first TCI state and the second TCI state index of the second TCI state. At least two TCI state indices can include the TCI state index of the TCI state. For example, based on (e.g., in response to) the TCI state index of the TCI state being the lowest / smallest among at least two TCI state indices of at least two TCI states, wireless device 1801 can monitor the PDCCH via CORESET, for example, based on the TCI state of at least two TCI states. For example, based on (e.g., in response to) the TCI state index being the lowest / smallest among at least two TCI state indices, the wireless device 1801 can receive DCI via CORESET, for example, based on the TCI state among at least two TCI states. For example, the first TCI state index of the first TCI state may be lower / less than the second TCI state index of the second TCI state. Based on the first TCI state index being lower / less than the second TCI state index of the second TCI state, the TCI state may be the first TCI state.

[0292] For example, based on (e.g., in response to) a first TCI state index being lower than / less than a second TCI state index of a second TCI state, the wireless device 1801 can monitor the PDCCH via CORESET based on the first TCI state. For example, based on (e.g., in response to) a first TCI state index being lower than / less than a second TCI state index of a second TCI state, the wireless device 1801 can receive the DCI via CORESET based on the first TCI state. For example, the second TCI state index of the second TCI state can be lower than / less than the first TCI state index of the first TCI state. Based on the second TCI state index being lower than / less than the first TCI state index of the first TCI state, the TCI state can be the second TCI state.

[0293] For example, based on (e.g., in response to) a second TCI state index being lower than / less than a first TCI state index of a first TCI state, the wireless device 1801 can monitor the PDCCH via CORESET, for example, based on the second TCI state. For example, based on (e.g., in response to) a second TCI state index being lower than / less than a first TCI state index of a first TCI state, the wireless device 1801 can receive the DCI via CORESET, for example, based on the second TCI state. For example, the TCI state index of at least two TCI states can be the highest / largest among at least two TCI state indices of at least two TCI states. The TCI state index of the TCI state can be the highest / largest among the first TCI state index of the first TCI state and the second TCI state index of the second TCI state. At least two TCI state indices can include the TCI state index of the TCI state.

[0294] For example, based on (e.g., in response to) the highest / largest TCI state index among at least two TCI state indices, the wireless device 1801 can monitor the PDCCH via CORESET, for example, based on the TCI state among at least two TCI states. For example, based on (e.g., in response to) the highest / largest TCI state index among at least two TCI state indices, the wireless device 1801 can receive the DCI via CORESET, for example, based on the TCI state among at least two TCI states. For example, the first TCI state index of the first TCI state can be greater than / higher than the second TCI state index of the second TCI state. Based on the first TCI state index being greater than / higher than the second TCI state index of the second TCI state, the TCI state can be the first TCI state.

[0295] For example, based on (e.g., in response to) a first TCI state index being greater than / higher than a second TCI state index of a second TCI state, the wireless device 1801 can monitor the PDCCH via CORESET based on the first TCI state. For example, based on (e.g., in response to) a first TCI state index being greater than / higher than a second TCI state index of a second TCI state, the wireless device 1801 can receive the DCI via CORESET based on the first TCI state. For example, the second TCI state index of the second TCI state can be greater than / higher than the first TCI state index of the first TCI state. Based on the second TCI state index being greater than / higher than the first TCI state index of the first TCI state, the TCI state can be the second TCI state.

[0296] For example, based on (e.g., in response to) a second TCI state index being greater than / higher than a first TCI state index of a first TCI state, wireless device 1801 can monitor the PDCCH via CORESET, for example, based on the second TCI state. For example, based on (e.g., in response to) a second TCI state index being greater than / higher than a first TCI state index of a first TCI state, wireless device 1801 can receive the DCI via CORESET, for example, based on the second TCI state.

[0297] The activation command indicating cell handover may include a first octet and a second octet. The first octet includes a first TCI state index indicating / identifying a first TCI state, and the second octet includes a second TCI state index indicating / identifying a second TCI state. The activation command indicating cell handover may have a first octet and a second octet, the first octet including / identifying a first TCI state index indicating / identifying a first TCI state, and the second octet including / identifying a second TCI state index indicating a second TCI state. The activation command indicating cell handover may include a first field in the first octet, the first field including the first TCI state index. The activation command indicating cell handover may include a second field in the second octet, the second field including the second TCI state index. The first octet in the activation command may include / identify a first TCI state index indicating / identifying a first TCI state. The second octet in the activation command may include a second TCI state index that indicates / identifies the second TCI state. For example, the TCI state may be the first TCI state if the first octet, which includes / indicates the first TCI state index, is lower / fewer / smaller than the second octet, which includes / indicates the second TCI state index. Similarly, the TCI state may be the first TCI state if the first TCI state index has a higher ordinal position than the second TCI state index (e.g., a lower octet in the activation command).

[0298] For example, based on (e.g., in response to) a first octet including / indicating a first TCI state index that indicates a first TCI state being lower / fewer / smaller than a second octet including / indicating a second TCI state index that indicates a second TCI state, wireless device 1801 can monitor the PDCCH via CORESET based on the first TCI state. For example, based on (e.g., in response to) a first TCI state index having a higher ordinal position than a second TCI state index of the second TCI state (e.g., a lower octet in an activation command), wireless device 1801 can monitor the PDCCH via CORESET based on the first TCI state.

[0299] For example, based on (e.g., in response to) a first octet including / indicating a first TCI state index of a first TCI state being lower / fewer / smaller than a second octet including / indicating a second TCI state index of a second TCI state, radio device 1801 can receive DCI via CORESET based on the first TCI state. For example, based on (e.g., in response to) a first TCI state index of a first TCI state having a higher ordinal position than a second TCI state index of a second TCI state (e.g., a lower octet in an activation command), radio device 1801 can receive DCI via CORESET based on the first TCI state. For example, a TCI state can be the first TCI state, for example, based on the first TCI state appearing first in a list / set / vector of at least two TCI states in an activation command indicating cell handover.

[0300] For example, based on (e.g., in response to) the first TCI state appearing first in a list / set / vector of at least two TCI states in an activation command indicating cell handover, radio device 1801 can monitor the PDCCH via CORESET, for example, based on the first TCI state. For example, based on (e.g., in response to) the first TCI state appearing first in a list / set / vector of at least two TCI states in an activation command indicating cell handover, radio device 1801 can receive the DCI via CORESET, for example, based on the first TCI state.

[0301] An activation command indicating the activation of a subset of TCI states may include a first octet and a second octet. The first octet includes a first TCI state index indicating / identifying the first TCI state, and the second octet includes a second TCI state index indicating / identifying the second TCI state. An activation command indicating the activation of a subset of TCI states may also have a first octet and a second octet. The first octet includes a first TCI state index indicating / identifying the first TCI state, and the second octet includes a second TCI state index indicating / identifying the second TCI state. An activation command indicating the activation of a subset of TCI states may include a first field in the first octet, the first field including the first TCI state index. An activation command indicating the activation of a subset of TCI states may include a second field in the second octet, the second field including the second TCI state index. The first octet in the activation command may include a first TCI state index indicating the first TCI state. The second octet in the activation command may include a second TCI state index indicating the second TCI state.

[0302] For example, a TCI state can be a first TCI state if the first octet of the first TCI state index, which includes / indicates a first TCI state state, is lower / fewer / smaller than the second octet of the second TCI state index, which includes / indicates a second TCI state state. For example, a TCI state can be a first TCI state if the first TCI state index has a higher ordinal position than the second TCI state index (e.g., a lower octet in an activation command).

[0303] For example, based on (e.g., in response to) a first octet including / indicating a first TCI state index that indicates a first TCI state being lower / fewer / smaller than a second octet including / indicating a second TCI state index that indicates a second TCI state, wireless device 1801 can monitor the PDCCH via CORESET based on the first TCI state. For example, based on (e.g., in response to) a first TCI state index having a higher ordinal position than a second TCI state index of the second TCI state (e.g., a lower octet in an activation command), wireless device 1801 can monitor the PDCCH via CORESET based on the first TCI state.

[0304] For example, based on (e.g., in response to) a first octet including / indicating a first TCI state index of a first TCI state being lower / fewer / smaller than a second octet including / indicating a second TCI state index of a second TCI state, wireless device 1801 can receive DCI via CORESET based on the first TCI state. For example, based on (e.g., in response to) a first TCI state index of a first TCI state having a higher ordinal position than a second TCI state index of a second TCI state (e.g., a lower octet in an activation command), wireless device 1801 can receive DCI via CORESET based on the first TCI state. For example, a TCI state can be the first TCI state, for example, based on the first TCI state appearing first in a list / set / vector of at least two TCI states in an activation command indicating the activation of a subset of TCI states.

[0305] For example, based on (e.g., in response to) the fact that a first TCI state appears first in a list / set / vector of at least two TCI states in an activation command indicating the activation of a subset of TCI states, wireless device 1801 can monitor the PDCCH via CORESET, for example, based on the first TCI state. For example, based on (e.g., in response to) the fact that a first TCI state appears first in a list / set / vector of at least two TCI states in an activation command indicating the activation of a subset of TCI states, wireless device 1801 can receive the DCI via CORESET, for example, based on the first TCI state.

[0306] The wireless device can target the DCI and, via the cell's CORESET, based on at least two TCI states in the activation command indicating cell handover (e.g., Figure 18 The PDCCH is monitored using the first TCI state 1811 and the second TCI state 1822. The radio device can monitor the PDCCH based on each of the at least two TCI states, for the DCI and via the cell's CORESET. The radio device can monitor the PDCCH based on both the DCI and the cell's CORESET. The radio device can monitor the PDCCH based on at least two TCI states via the CORESET, for example, starting from the first / starting / earliest time slot. The radio device can monitor the PDCCH based on at least two TCI states via the CORESET, for example, after handover to the cell.

[0307] A radio device can receive DCI based on at least two TCI states via the cell's CORESET. A radio device can receive DCI based on each of the at least two TCI states via the cell's CORESET. A radio device can receive DCI based on both of the at least two TCI states via the cell's CORESET. A radio device can receive DCI based on at least two TCI states via the CORESET, for example, in or after the first / starting / earliest time slot. A radio device can receive DCI based on at least two TCI states via the CORESET, for example, after handover to a cell.

[0308] One or more configuration parameters can indicate the SFN scheme for the downlink control channel (e.g., sfnSchemePdcch) of the cell. For example, based on (e.g., in response to) one or more configuration parameters indicating the SFN scheme for the downlink control channel (e.g., sfnSchemePdcch) of the cell, the radio device can monitor the PDCCH via CORESET, for example, based on at least two TCI states. For example, based on (e.g., in response to) one or more configuration parameters indicating the SFN scheme for the downlink control channel (e.g., sfnSchemePdcch) of the cell, the radio device can receive DCI via CORESET, for example, based on at least two TCI states.

[0309] For example, based on (e.g., in response to) one or more configuration parameters including an application indication TCI status parameter of CORESET set to 'none', a wireless device can monitor the PDCCH via CORESET based on at least two TCI states.

[0310] For example, based on (e.g., in response to) one or more configuration parameters including an application indication TCI state parameter of CORESET set to 'none', a wireless device can receive DCI via CORESET based on at least two TCI states.

[0311] For example, based on (e.g., in response to) a CORESET index that is not zero, a wireless device can monitor the PDCCH via a CORESET based on at least two TCI states. A wireless device can monitor the PDCCH via a CORESET with a CORESET index that is not zero, based on at least two TCI states.

[0312] For example, based on (e.g., in response to) a CORESET index that is different from zero, a wireless device can receive DCI via a CORESET based on at least two TCI states. A wireless device can receive DCI via a CORESET with a CORESET index that is different from zero, based on at least two TCI states.

[0313] For example, if at least one search space set in one or more search space sets of CORESET is a CSS set other than the Type3-PDCCH CSS set, the wireless device can monitor the PDCCH via at least two TCI states based on CORESET. The wireless device can monitor the PDCCH via CORESET associated with a CSS set other than the Type3-PDCCH CSS set, based on at least two TCI states. The CORESET index of CORESET can be, for example, different from zero. The TCI state parameter of CORESET application indication can be, for example, set to 'none'.

[0314] For example, if at least one search space set in one or more search space sets of CORESET is a CSS set other than the Type3-PDCCH CSS set, the wireless device can receive DCI via CORESET based on at least two TCI states. The wireless device can receive DCI via CORESET associated with a CSS set other than the Type3-PDCCH CSS set, based on at least two TCI states. The CORESET index of CORESET can be, for example, different from zero. The TCI state parameter of the application indication of CORESET can be, for example, set to 'none'.

[0315] For example, a wireless device can monitor the PDCCH via CORESET based on at least two TCI states, based on (e.g., in response to) CORESET not being associated with a CSS set configured by pdcch-ConfigSIB1 in the MIB, searchSpaceSIB1, searchSpaceZero, searchSpaceOtherSystemInformation, or pagingSearchSpace in PDCCH-ConfigCommon. The wireless device can monitor the PDCCH based on at least two TCI states via a CORESET that is not associated with a CSS set configured by at least one of the following: pdcch-ConfigSIB1, searchSpaceSIB1, searchSpaceZero, searchSpaceOther SystemInformation, or pagingSearchSpace. The CORESET index of the CORESET can, for example, be equal to zero. The TCI state parameter indicated by the application of the CORESET can, for example, be set to 'none'.

[0316] For example, based on (e.g., in response to) CORESET not being associated with a CSS set configured by pdcch-ConfigSIB1 in the MIB, searchSpaceSIB1, searchSpaceZero, searchSpaceOtherSystemInformation, or pagingSearchSpace in PDCCH-ConfigCommon, the wireless device 1801 may receive DCI via CORESET based on at least two TCI states. Wireless device 1801 can receive DCI based on at least two TCI states via a CORESET not associated with a CSS set configured by at least one of the following: pdcch-ConfigSIB1, searchSpaceSIB1, searchSpaceZero, searchSpaceOther SystemInformation, or pagingSearchSpace. The CORESET index of the CORESET can, for example, be equal to zero. The TCI state parameter of the CORESET application indication can, for example, be set to 'none'.

[0317] For example, based on (e.g., in response to) a CORESET associated with at least one of the following CSS sets: Type0-PDCCH CSS set, Type0A-PDCCH CSS set, and Type2-PDCCH CSS set, the wireless device 1801 can monitor the PDCCH based on at least two TCI states via the CORESET. The wireless device 1801 can also monitor the PDCCH based on at least two TCI states via a CORESET not associated with at least one of the following CSS sets: Type0-PDCCH CSS set, Type0A-PDCCH CSS set, and Type2-PDCCH CSS set. The CORESET index of the CORESET can, for example, be equal to zero. The TCI state parameter of the CORESET application indication can, for example, be set to 'none'.

[0318] For example, based on (e.g., in response to) the CORESET not being associated with a CSS set that is at least one of the following: Type0-PDCCH CSS set, Type0A-PDCCH CSS set, and Type2-PDCCH CSS set, the wireless device 1801 can receive DCI via the CORESET based on at least two TCI states. The wireless device 1801 can receive DCI via a CORESET not associated with a CSS set that is at least one of the following: Type0-PDCCH CSS set, Type0A-PDCCH CSS set, and Type2-PDCCH CSS set, based on at least two TCI states. The CORESET index of the CORESET can, for example, be equal to zero. The TCI state parameter of the CORESET application indication can, for example, be set to 'none'.

[0319] Wireless device 1801 can receive DCI in a CORESET via PDCCH. Wireless device 1801 can receive PDCCH with / carrying DCI in / via a CORESET. Wireless device 1801 can receive PDCCH with / carrying DCI in / via a CORESET and based on at least two TCI states.

[0320] At least one first DM-RS antenna port (e.g., PDCCH receiver) of a PDCCH with DCI can be quasi-co-located with a first reference signal indicated by a first TCI state. At least one first DM-RS antenna port (e.g., PDCCH receiver) of a PDCCH with DCI can be quasi-co-located with a first reference signal with respect to a first quasi-co-location type indicated by a first TCI state.

[0321] At least one second DM-RS antenna port (e.g., PDCCH receiver) of a PDCCH with DCI can be quasi-co-located with a second reference signal indicated by a second TCI state. At least one second DM-RS antenna port (e.g., PDCCH receiver) of a PDCCH with DCI can be quasi-co-located with a second reference signal with respect to a second quasi-co-location type indicated by a second TCI state. At least one first DM-RS antenna port and at least one first DM-RS antenna port can be, for example, identical. At least one first DM-RS antenna port and at least one first DM-RS antenna port can be, for example, different.

[0322] At least one DM-RS antenna port (e.g., PDCCH receiver) of a PDCCH with DCI can be quasi-co-located with both a first reference signal indicated by a first TCI state and a second reference signal indicated by a second TCI state. At least one DM-RS antenna port (e.g., PDCCH receiver) of a PDCCH with DCI can be quasi-co-located with both the first reference signal of a first quasi-co-location type and the second reference signal of a second quasi-co-location type.

[0323] CORESET (e.g., Figure 18 The TCI state parameter indicated by the application of CORESET 1 in the cell can be set to 'first'. The wireless device 1801 can, for DCI and via the cell's CORESET, set at least two TCI states (e.g., ...) in the activation command indicating cell handover. Figure 18 The first TCI state (e.g., the first TCI state 1811 and the second TCI state 1822) in the first TCI state (e.g., Figure 18 The radio device 1801 can monitor the PDCCH based on the first TCI state (1811) via CORESET, for example, starting from the first / starting / earliest time slot. The radio device 1801 can also monitor the PDCCH based on the first TCI state via CORESET, for example, after cell handover.

[0324] For example, if the TCI status parameter, based on (e.g., in response to) the application indication of CORESET, is set to 'first', the radio device 1801 can monitor the PDCCH based on the first TCI status for DCI and via the cell's CORESET. Alternatively, if one or more configuration parameters, including the application indication TCI status parameter, are set to 'first' based on (e.g., in response to) CORESET, the radio device 1801 can monitor the PDCCH based on the first TCI status for DCI and via the cell's CORESET.

[0325] Radio device 1801 can receive DCI based on the first TCI state among at least two TCI states via the cell's CORESET. Radio device 1801 can receive DCI based on the first TCI state via CORESET, for example, in or after the first / start / earliest time slot. Radio device 1801 can receive DCI based on the first TCI state via CORESET, for example, after handover to the cell.

[0326] For example, based on (e.g., in response to) CORESET, one or more configuration parameters including application-indicating TCI status parameters are set to 'first', the wireless device 1801 can receive DCI via CORESET based on the first TCI status.

[0327] At least one DM-RS antenna port (e.g., PDCCH receiver) of a PDCCH with DCI can be quasi-co-located with a first reference signal indicated by a first TCI state. At least one DM-RS antenna port (e.g., PDCCH receiver) of a PDCCH with DCI can be quasi-co-located with a first reference signal with respect to a first quasi-co-location type indicated by a first TCI state.

[0328] CORESET (e.g., Figure 18 The TCI state parameter indicated by the application of CORESET 1 in the cell can be set to 'second'. The radio device 1801 can, for DCI and via the cell's CORESET, set at least two TCI states (e.g., ...) in the activation command indicating cell handover. Figure 18 The second TCI state (e.g., the first TCI state 1811 and the second TCI state 1822) in the first TCI state 1811 and the second TCI state 1822) Figure 18 The radio device 1801 can monitor the PDCCH based on the second TCI state (1822) via CORESET, for example, starting from the first / starting / earliest time slot. The radio device 1801 can also monitor the PDCCH based on the second TCI state via CORESET, for example, after cell handover.

[0329] For example, if the TCI status parameter, based on (e.g., in response to) the application indication of CORESET, is set to 'second', the radio device 1801 can monitor the PDCCH based on the second TCI status for DCI and via the cell's CORESET. Alternatively, if one or more configuration parameters, including the application indication TCI status parameter, are set to 'second' based on (e.g., in response to) CORESET, the radio device 1801 can monitor the PDCCH based on the second TCI status for DCI and via the cell's CORESET.

[0330] Radio device 1801 can receive DCI based on the second TCI state among at least two TCI states via the cell's CORESET. Radio device 1801 can receive DCI based on the second TCI state via CORESET, for example, in or after the first / starting / earliest time slot. Radio device 1801 can receive DCI based on the second TCI state via CORESET, for example, after handover to the cell.

[0331] For example, based on (e.g., in response to) CORESET, one or more configuration parameters including application-indicating TCI status parameters are set to 'second', the wireless device 1801 can receive DCI via CORESET based on the second TCI status.

[0332] At least one DM-RS antenna port (e.g., PDCCH receiver) of a PDCCH with DCI can be quasi-co-located with a second reference signal indicated by a second TCI state. At least one DM-RS antenna port (e.g., PDCCH receiver) of a PDCCH with DCI can be quasi-co-located with a second reference signal with respect to a second quasi-co-location type indicated by a second TCI state.

[0333] CORESET (e.g., Figure 18 The TCI state parameter indicated by the application of CORESET 1 in the cell can be set to 'both'. The radio device 1801 can, for DCI and via the cell's CORESET, base its activation command indicating cell handover on at least two TCI states (e.g., ...). Figure 18 The radio device 1801 monitors the PDCCH based on each of the at least two TCI states (1811 and 1822) in the DCI and via the cell's CORESET. The radio device 1801 can monitor the PDCCH based on both the DCI and the cell's CORESET. The radio device 1801 can monitor the PDCCH based on at least two TCI states via the CORESET, for example, starting from the first / starting / earliest time slot. The radio device 1801 can monitor the PDCCH based on at least two TCI states via the CORESET, for example, after handover to the cell.

[0334] For example, if the TCI status parameter based on (e.g., in response to) the application indication of CORESET is set to 'both', the radio device 1801 can monitor the PDCCH based on at least two TCI states for DCI and via the cell's CORESET. For example, if one or more configuration parameters including the application indication TCI status parameter of CORESET are set to 'both', the radio device 1801 can monitor the PDCCH based on at least two TCI states for DCI and via the cell's CORESET.

[0335] Radio device 1801 can receive DCI based on at least two TCI states via the cell's CORESET. Radio device 1801 can receive DCI based on each of the at least two TCI states via the cell's CORESET. Radio device 1801 can receive DCI based on both of the at least two TCI states via the cell's CORESET. Radio device 1801 can receive DCI based on at least two TCI states via the CORESET, for example, in or after the first / starting / earliest time slot. Radio device 1801 can receive DCI based on at least two TCI states via the CORESET, for example, after handover to a cell.

[0336] For example, if one or more configuration parameters, including application-indicating TCI status parameters, of CORESET are set to 'both', wireless device 1801 can receive DCI via CORESET based on at least two TCI states. Alternatively, if the application-indicating TCI status parameters of CORESET are set to 'none', wireless device 1801 can receive DCI via CORESET based on at least two TCI states.

[0337] At least one DM-RS antenna port (e.g., PDCCH receiver) of a PDCCH with DCI can be quasi-co-located with a first reference signal indicated by a first TCI state and a second reference signal indicated by a second TCI state. At least one DM-RS antenna port (e.g., PDCCH receiver) of a PDCCH with DCI can be quasi-co-located with a first reference signal of a first quasi-co-location type indicated by a first TCI state and with a second reference signal of a second quasi-co-location type indicated by a second TCI state.

[0338] At least one first DM-RS antenna port (e.g., PDCCH receiver) of a PDCCH with DCI can be quasi-co-located with a first reference signal indicated by a first TCI state. At least one second DM-RS antenna port (e.g., PDCCH receiver) of a PDCCH with DCI can be quasi-co-located with a second reference signal indicated by a second TCI state. At least one first DM-RS antenna port (e.g., PDCCH receiver) of a PDCCH with DCI can be quasi-co-located with a first reference signal of a first quasi-co-location type indicated by a first TCI state. At least one second DM-RS antenna port (e.g., PDCCH receiver) of a PDCCH with DCI can be quasi-co-located with a second reference signal of a second quasi-co-location type indicated by a second TCI state.

[0339] Figure 19 An example method for cell handover is illustrated. A radio device may receive one or more messages, which include one or more configuration parameters. A base station may send (e.g., transmit) one or more messages to the radio device. The one or more configuration parameters may include TCI status parameters indicating the application of CORESET in / on the cell.

[0340] In step 1910, the radio device may receive an activation command indicating a cell handover to a cell (e.g., a primary cell performing an LTM procedure). The base station may send (e.g., transmit) an activation command for the LTM procedure. The activation command may indicate at least two TCI states. The at least two TCI states may indicate / are at least two unified TCI states. The at least two TCI states may be at least two indicated TCI states. The at least two TCI states may be, for example, at least two joint TCI states. The at least two TCI states may be, for example, at least two downlink TCI states. The at least two TCI states may include a first TCI state and a second TCI state. The radio device may, for example, handover to the primary cell based on receiving the activation command. The radio device may, for example, handover from the current primary cell to the primary cell based on receiving the activation command. The base station may, for example, handover to the primary cell based on sending (e.g., transmitting) the activation command. The base station may, for example, handover from the current primary cell to the primary cell based on sending (e.g., transmitting) the activation command.

[0341] In step 1920, if the TCI state parameter of the CORESET application indication can be set to 'none', indicating that the indicated TCI state of at least two TCI states is not applied to the CORESET, then step 1940 can be performed. In step 1940, for example, based on (e.g., in response to) the TCI state parameter of the CORESET application indication being set to 'none', the radio device can monitor the PDCCH for DCI and in / via the cell's CORESET, for example, based on the TCI states of at least two TCI states. The TCI state may include (or) for example, a default TCI state.

[0342] For example, if the TCI status parameter is set to 'none' based on (e.g., in response to) the application indication of the CORESET, the radio device can receive DCI in / via the cell's CORESET, for example, based on the TCI status of at least two TCI states. Similarly, if the radio device receives DCI in / via the cell's CORESET based on (e.g., in response to) an activation command indicating at least two TCI states, the radio device can receive DCI in / via the cell's CORESET, for example, based on the TCI status of at least two TCI states.

[0343] For example, based on (e.g., in response to) the application indication of the CORESET, the TCI state parameter is set to 'none', and the radio device can receive PDCCH reception in / via the cell's CORESET, based on the TCI states in at least two TCI states. PDCCH reception may include / indicate DCI. At least one DM-RS antenna port for PDCCH reception via the CORESET can be quasi-co-located with a reference signal indicated / provided by the TCI state. For example, based on (e.g., in response to) the application indication of the CORESET, the TCI state parameter is set to 'none', and the base station can transmit (e.g., transmit) DCI in / via the cell's CORESET, based on the TCI states in at least two TCI states. The base station can transmit (e.g., transmit) DCI in / via the cell's CORESET, the DCI having / using a spatial domain transmission filter / beam determined based on the reference signal indicated by the TCI state. For example, if the TCI state parameter is set to 'none' based on (e.g., in response to) the application indication of the CORESET, the base station can transmit (e.g., transmit) PDCCH transmissions in / via the cell's CORESET, based on the TCI states of at least two TCI states. Similarly, if the base station is based on (e.g., in response to) an activation command indicating at least two TCI states, the base station can transmit (e.g., transmit) DCI in / via the cell's CORESET, based on the TCI states of at least two TCI states.

[0344] Wireless devices can be, for example, based on Figure 18 The base station may determine the TCI state among at least two TCI states using one or more criteria discussed herein (e.g., the first TCI state, the TCI state with the lowest TCI state index, an activation command including a field with a value indicating the TCI state, etc.). Figure 18 One or more criteria discussed in the document (e.g., the first TCI state, the TCI state with the lowest TCI state index, the activation command including a field with a value indicating the TCI state, etc.) are used to determine the TCI state among at least two TCI states.

[0345] One or more configuration parameters may indicate a CORESET index for the CORESET. The CORESET index may be equal to zero. The CORESET index may be associated with at least one of the following: a Type 0 CSS set, a Type 0ACSS set, and a Type 2 CSS set. The CORESET index may not be equal to zero. The CORESET may be associated with one or more common search space (CSS) sets that are different from the Type3PDCCH CSS set. The CORESET may not be associated with the Type3PDCCH CSS set.

[0346] In step 1920, if the TCI status parameter of the CORESET application indication might not be set to 'None', indicating that the indicated TCI status of at least two TCI states is not applied to the CORESET, then step 1930 can be performed. For example, the TCI status parameter of the CORESET application indication might be set to 'First', indicating that the first TCI status of at least two TCI states is applied to the CORESET.

[0347] In step 1930, for example, based on (e.g., in response to) the application indication TCI state parameter of the CORESET being set to 'first', the radio device can monitor the PDCCH for the DCI and in / via the cell's CORESET, for example, based on the first TCI state of at least two TCI states. For example, based on (e.g., in response to) the application indication TCI state parameter of the CORESET being set to 'first', the radio device can receive the DCI in / via the cell's CORESET, for example, based on the first TCI state of at least two TCI states. For example, based on (e.g., in response to) the application indication TCI state parameter of the CORESET being set to 'first', the base station can transmit (e.g., transmit) the DCI in / via the cell's CORESET, for example, based on the first TCI state of at least two TCI states. For example, the application indication TCI state parameter of the CORESET can be set to 'second', indicating that the second TCI state of at least two TCI states is applied to the CORESET. For example, if the TCI state parameter based on (e.g., in response to) the application indication of CORESET is set to 'second', the radio device can monitor the PDCCH for DCI and in / via the cell's CORESET, for example, based on the second TCI state of at least two TCI states. For example, if the TCI state parameter based on (e.g., in response to) the application indication of CORESET is set to 'second', the radio device can receive DCI in / via the cell's CORESET, for example, based on the second TCI state of at least two TCI states. For example, if the TCI state parameter based on (e.g., in response to) the application indication of CORESET is set to 'second', the base station can transmit (e.g., transmit) DCI in / via the cell's CORESET, for example, based on the second TCI state of at least two TCI states. For example, the TCI state parameter of the application indication of CORESET can be set to 'both', indicating that at least two TCI states are applied to the CORESET. For example, based on (e.g., in response to) the application indication of CORESET, the TCI state parameter is set to 'both', and the radio device can monitor the PDCCH for DCI and in / via the cell's CORESET, for example, based on at least two TCI states.For example, based on (e.g., in response to) the application indication of CORESET, the TCI state parameter is set to 'both', and the radio device can monitor the PDCCH for DCI and in / via the cell's CORESET, for example, based on at least two TCI states. For example, based on (e.g., in response to) the application indication of CORESET, the TCI state parameter is set to 'both', and the radio device can receive DCI in / via the cell's CORESET, for example, based on at least two TCI states. For example, based on (e.g., in response to) the application indication of CORESET, the TCI state parameter is set to 'both', and the radio device can receive DCI in / via the cell's CORESET, for example, based on each of at least two TCI states. For example, based on (e.g., in response to) the application indication of CORESET, the TCI state parameter is set to 'both', and the radio device can receive DCI in / via the cell's CORESET, for example, based on at least two TCI states. For example, if the TCI state parameter based on (e.g., in response to) the application indication of the CORESET is set to 'both', the base station can transmit (e.g., transfer) the DCI in / via the cell's CORESET, for example, based on at least two TCI states. For example, if the TCI state parameter based on (e.g., in response to) the application indication of the CORESET is set to 'both', the base station can transmit (e.g., transfer) the DCI in / via the cell's CORESET, for example, based on each of at least two TCI states. For example, if the TCI state parameter based on (e.g., in response to) the application indication of the CORESET is set to 'both', the base station can transmit (e.g., transfer) the DCI in / via the cell's CORESET, for example, based on both of at least two TCI states.

[0348] Configuration can be provided / instructed to the radio device via one or more LTM-CSI report configuration parameters (e.g., LTM-CSI-ReportConfig) for reporting the number of cells and the number of SS / PBCH blocks per cell (or including / including said number) of L1-RSRP measurements based on the number of cells. One or more configuration parameters may include one or more LTM-CSI report configuration parameters. The number of cells may be one or more candidate cells (or one or more LTM candidate cells or one or more target cells) in the LTM procedure.

[0349] At least two TCI states (e.g., a first TCI-State and a second TCI-State) can be provided / indicated for a radio device in the dl-OrJointTCI-StateList via MAC CE (e.g., LTM cell handover command MAC CE) received in the PDSCH of the serving cell. The at least two TCI states can indicate the uniform TCI state applicable to reception or transmission on cells (e.g., LTM candidate cells or candidate / target cells) based on the number / scale of cells. The at least two TCI states may include a first TCI state (e.g., a first TCI-State) and a second TCI state (e.g., a second TCI-State).

[0350] If the radio device is instructed by the MAC CE to provide HARQ-ACK information for PDSCH reception for providing the MAC CE, starting from the first / earliest time slot of the duration / gap following the last symbol of an uplink transmission (e.g., PUCCH or PUSCH), the radio device may apply at least two TCI states (e.g., a first TCI-State and a second TCI-State). For a CORESET with index 0, or a CORESET other than one with index 0 (which is associated with at least a CSS set other than the Type 3-PDCCH CSS set, and for said CORESET, apply-IndicatedTCIState = 'None'), if at least two TCI states are provided / indicated to the radio device by the MAC CE, the radio device may assume that the DM-RS antenna port in the CORESET for PDCCH reception is quasi-co-located with the reference signal provided / indicated by the first TCI state (e.g., the first TCI-State). A cell may include a CORESET. The wireless device can receive PDCCH reception via CORESET based on the first TCI state (e.g., the first TCI-State) of at least two TCI states.

[0351] The base station may send (e.g., transmit) one or more messages to the radio device that include one or more configuration parameters. The one or more configuration parameters may include one or more LTM-CSI report configuration parameters (e.g., LTM-CSI-ReportConfig) for reporting the number of cells and the number of SS / PBCH blocks per cell based on the number of cells (or including / including said number of cells) L1-RSRP measurements. The radio device may receive one or more messages that include one or more configuration parameters, including one or more LTM-CSI report configuration parameters. The number of cells may be one or more candidate cells (or one or more LTM candidate cells or one or more target cells) in the LTM procedure.

[0352] A base station may send (e.g., transmit) a MAC CE (e.g., an LTM cell handover command MAC CE) to a radio device during PDSCH transmission on the serving cell. The radio device may receive the MAC CE during PDSCH reception. The MAC CE may indicate at least two TCI states (e.g., a first TCI-State and a second TCI-State) in the dl-OrJointTCI-StateList. The at least two TCI states may indicate the uniform TCI states applicable to reception or transmission on cells (e.g., LTM candidate cells or candidate / target cells) based on the number / scale of cells. The at least two TCI states may include a first TCI state (e.g., a first TCI-State) and a second TCI state (e.g., a second TCI-State).

[0353] Using HARQ-ACK information for providing / including / contains MAC CE PDSCH transmissions, the base station can apply at least two TCI states (e.g., first TCI-State and second TCI-State) starting from the first / start / earliest time slot of the duration / gap following the last symbol of uplink reception (e.g., PUCCH or PUSCH reception). Using HARQ-ACK information for providing / including / contains MAC CE PDSCH receptions, the radio device can apply at least two TCI states (e.g., first TCI-State and second TCI-State) starting from the first / start / earliest time slot of the duration / gap following the last symbol of uplink transmission (e.g., PUCCH or PUSCH transmission).

[0354] For a CORESET with index 0, or a CORESET other than one with index 0 (which is associated with at least a CSS set other than the Type3-PDCCH CSS set, and for said CORESET, apply-IndicatedTCIState = 'None'), if the base station transmits (e.g., transmits) a MAC CE indicating at least two TCI states, the base station may assume that the DM-RS antenna port in the CORESET for PDCCH transmission is quasi-co-located with a reference signal provided / indicated by the first TCI state (e.g., the first TCI-State) of the at least two TCI states. The base station may transmit (e.g., transmit) PDCCH transmissions via the CORESET based on the first TCI state (e.g., the first TCI-State). The base station may utilize / use a spatial domain transmission filter / beam determined based on the reference signal provided / indicated by the first TCI state (e.g., the first TCI-State) to transmit (e.g., transmit) PDCCH transmissions via the CORESET. A cell may include a CORESET. The cell's downlink BWP may include a CORESET. One or more configuration parameters may include apply-IndicatedTCIState = 'None' for CORESET.

[0355] For a CORESET with index 0 (and for said CORESET, apply-IndicatedTCIState = 'None'), if the base station transmits (e.g., transmits) a MAC CE indicating at least two TCI states, the base station may assume that the DM-RS antenna port in the CORESET for PDCCH transmission is quasi-co-located with a reference signal provided / indicated by the first TCI state (e.g., the first TCI-State) of the at least two TCI states. The base station may transmit (e.g., transmit) PDCCH transmissions via the CORESET based on the first TCI state (e.g., the first TCI-State). The base station may utilize / use a spatial domain transmission filter / beam determined based on the reference signal provided / indicated by the first TCI state (e.g., the first TCI-State) to transmit (e.g., transmit) PDCCH transmissions via the CORESET. A cell may include a CORESET. The cell's downlink BWP may include a CORESET. One or more configuration parameters may include apply-IndicatedTCIState = 'None' for the CORESET.

[0356] For any CORESET other than the one with index 0 (which is associated with at least one CSS set other than the Type3-PDCCH CSS set, and for that CORESET, apply-IndicatedTCIState = 'None'), if the base station transmits (e.g., transmits) a MAC CE indicating at least two TCI states, the base station may assume that the DM-RS antenna port in the CORESET used for PDCCH transmission is quasi-co-located with a reference signal provided / indicated by the first TCI state (e.g., the first TCI-State) of the at least two TCI states. The base station may transmit (e.g., transmit) PDCCH transmissions via the CORESET based on the first TCI state (e.g., the first TCI-State). The base station may utilize / use a spatial domain transmission filter / beam determined based on the reference signal provided / indicated by the first TCI state (e.g., the first TCI-State) to transmit (e.g., transmit) PDCCH transmissions via the CORESET. A cell may include a CORESET. The cell's downlink BWP may include a CORESET. One or more configuration parameters may include apply-IndicatedTCIState = 'None' for CORESET.

[0357] For a CORESET with index 0, or a CORESET other than one with index 0 (which is associated with at least a CSS set other than the Type3-PDCCH CSS set, and for said CORESET, apply-IndicatedTCIState = 'None'), if the radio device receives a MAC CE indicating at least two TCI states, the radio device may assume that the DM-RS antenna port in the CORESET for PDCCH reception is quasi-co-located with a reference signal provided / indicated by the first TCI state (e.g., the first TCI-State) of the at least two TCI states. The radio device may receive PDCCH reception via the CORESET based on the first TCI state (e.g., the first TCI-State). A cell may include a CORESET. The downlink BWP of the cell may include a CORESET. One or more configuration parameters may include apply-IndicatedTCIState = 'None' for the CORESET.

[0358] For a CORESET with index 0 (and for that CORESET, apply-IndicatedTCIState = 'None'), if the radio device receives a MAC CE indicating at least two TCI states, the radio device may assume that the DM-RS antenna port in the CORESET for PDCCH reception is quasi-co-located with a reference signal provided / indicated by the first TCI state (e.g., the first TCI-State) of the at least two TCI states. The radio device may receive PDCCH reception via the CORESET based on the first TCI state (e.g., the first TCI-State). A cell may include a CORESET. The downlink BWP of the cell may include a CORESET. One or more configuration parameters may include apply-IndicatedTCIState = 'None' for the CORESET.

[0359] For any CORESET other than the one with index 0 (which is associated with at least one CSS set other than the Type3-PDCCH CSS set, and for that CORESET, apply-IndicatedTCIState = 'None'), if the radio device receives a MAC CE indicating at least two TCI states, the radio device may assume that the DM-RS antenna port in the CORESET for PDCCH reception is quasi-co-located with a reference signal provided / indicated by the first TCI state (e.g., the first TCI-State) of the at least two TCI states. The radio device may receive PDCCH reception via the CORESET based on the first TCI state (e.g., the first TCI-State). A cell may include a CORESET. The downlink BWP of the cell may include a CORESET. One or more configuration parameters may include apply-IndicatedTCIState = 'None' for the CORESET.

[0360] The activation command instructing cell handover may include a timing advance command with a value. Multiple fields of the activation command may include the timing advance command. For example, the timing advance command in the activation command may be set to / used as a predefined value (e.g., FFF, 000). The predefined value may be, for example, a hexadecimal value. The value of the timing advance command may be set to / equal to / used as a predefined value. For example, the timing advance command in the activation command may not be set to / used as a predefined value (e.g., FFF, 000). The predefined value may be, for example, a hexadecimal value. The timing advance command in the activation command may be set to a value different from the predefined value. The value of the timing advance command may be different from the predefined value.

[0361] One or more configuration parameters may include parameters (e.g., enable-UE-TA) that enable the radio device to perform timing advance measurements on candidate cells (e.g., target cell, non-serving cell, neighboring cell, LTM candidate cell, etc.). For example, one or more configuration parameters may contain the parameter that enables the radio device to perform timing advance measurements on candidate cells. For example, setting the parameter to 'enabled' enables the radio device to perform timing advance measurements on candidate cells.

[0362] A radio device may send (e.g., transmit) a radio device capability message to a base station, the radio device capability message indicating the radio device's support for timing advance measurement of candidate cells. For example, one or more configuration parameters may not include a parameter (e.g., enable-UE-TA) that enables the radio device to perform timing advance measurement of candidate cells (e.g., target cell, non-serving cell, neighboring cell, LTM candidate cell, etc.). For example, the absence of the parameter in one or more configuration parameters may prevent the radio device from performing timing advance measurement of candidate cells. For example, setting the parameter to 'disabled' may prevent the radio device from performing timing advance measurement of candidate cells.

[0363] A radio device can determine the timing advance value of a cell (or candidate / target / non-serving cell). The radio device can determine the cell's timing advance value, for example, based on a second timing advance value of the serving cell and the received reference signal timing difference (RSTD) between the serving cell and the cell. The cell's timing advance value can be equal to the serving cell's second timing advance value plus twice the received RSTD. The serving cell and the cell can be synchronized (e.g., synchronizing the target and source DUs). The serving cell and the cell can be synchronized, for example, based on the received RSTD within a cyclic prefix (CP).

[0364] For example, based on one or more configuration parameters including parameters that enable timing advance measurement of a cell (e.g., enable-UE-TA), the timing advance command in the activation command can be set to a predefined value. For example, if one or more configuration parameters include parameters that enable timing advance measurement of a cell (e.g., enable-UE-TA), the timing advance command in the activation command may not be set to / is a predefined value. The value of the timing advance command may differ from the predefined value. The value of the timing advance command may indicate / be an incremental value (or network compensation factor or timing adjustment amount) used to control the timing adjustment amount applied by the radio device to determine the timing advance value of the cell. The serving cell and the cell may not be (ideally / precisely) synchronized (e.g., asynchronous target and source DU). The radio device may determine the timing advance value of the cell, for example, based on a second timing advance value of the serving cell, the received RSTD, and the value of the timing advance command (e.g., incremental value, network compensation factor, timing adjustment amount).

[0365] In at least some wireless communications, the timing advance value of a candidate cell (e.g., a target cell) can be used, for example, for cell handover. If a wireless device receives a cell handover command that can indicate the timing advance value of a candidate cell, the wireless device may not need to execute random access procedures. However, if the cell handover command does not indicate a timing advance value (e.g., the timing advance value is set to a predefined value), the wireless device may not know whether it should execute random access procedures for cell handover (e.g., LTM cell handover). The wireless device can use its implementation to determine the timing advance value of the candidate cell. Continuously executing random access procedures for cell handover, even if the wireless device can have the timing advance value of the candidate cell, can be inefficient.

[0366] As described herein, multiple control messages from the base station can improve the efficiency of the cell handover process. For example, parameters in the control messages (e.g., enable-UE-TA) can enable the radio device to measure timing information (e.g., timing advance value) of the candidate cell. If the radio device is configured to measure the timing information (e.g., timing advance value) of the candidate cell, for example, before or during cell handover (e.g., LTM procedure), the radio device can skip the random access procedure based on the received parameter (e.g., enable-UE-TA). For example, the radio device can measure the timing information (e.g., timing advance value) of the candidate cell and handover to the candidate cell using the measured tim...

Claims

1. A method comprising: The wireless device receives one or more configuration parameters, including a timing advance parameter, which is configured to enable the wireless device to perform timing advance measurements on mobility (LTM) candidate cells triggered by Layer 1 or Layer 2. Receive an LTM cell handover command, the LTM cell handover command including an indication that there is no valid timing adjustment available for the timing advance group of the LTM candidate cell; as well as Based on one or more configuration parameters, including timing advance parameters configured to enable the radio device to perform the timing advance measurement on the LTM candidate cell, the random access procedure for LTM cell handover is skipped.

2. The method of claim 1, further comprising switching to the LTM candidate cell, wherein the LTM cell handover command instructs the radio device to switch from the serving cell to the LTM candidate cell.

3. The method according to any one of claims 1 to 2, wherein the LTM cell handover command includes a timing advance command value, and wherein the timing advance command value is set to a predefined value to indicate that there is no effective timing adjustment available for the timing advance group of the LTM candidate cell.

4. The method according to any one of claims 1 to 3, wherein the predefined value is a hexadecimal value corresponding to FFF.

5. The method according to any one of claims 1 to 4, wherein receiving the LTM cell handover command includes receiving an LTM cell handover command Media Access Control (MAC) element (CE).

6. The method according to any one of claims 1 to 5, further comprising performing the LTM cell handover and applying a timing advance value based on one or more measurements performed by the radio device.

7. The method according to any one of claims 1 to 6, wherein the random access procedure for skipping the LTM cell handover is further based on the LTM cell handover command including the indication that there is no value for timing adjustment of the timing advance group that can be used for the LTM candidate cell.

8. The method according to any one of claims 1 to 7, wherein skipping the random access procedure comprises: Determine not to initiate the random access procedure for the handover of the LTM cell; or It is determined that no random access preamble will be sent for the handover of the LTM cell.

9. The method according to any one of claims 1 to 8, further comprising sending a radio device capability message to a base station, the radio device capability message indicating that the radio device supports the timing advance measurement of the LTM candidate cell.

10. The method according to any one of claims 1 to 9, further comprising determining the timing advance of the LTM candidate cell.

11. The method according to any one of claims 1 to 10, wherein the timing advance for determining the LTM candidate cell is based on: The advance time for serving the community; and The received reference signal timing difference between the serving cell and the LTM candidate cell.

12. The method according to any one of claims 1 to 11, further comprising: The MAC layer of the wireless device instructs the radio resource control layer of the wireless device to skip the random access procedure used for the LTM cell handover.

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

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

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

Images