Network power saving for wireless communication management

Abstract

A wireless device may communicate with a base station via a cell. A wireless device may notify the base station whether the wireless device supports power saving operation. Based on the notification, the wireless device may be enabled or activated to perform the power saving operation.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 455,864, filed March 30, 2023. The entire application cited above is hereby incorporated by reference. Background Technology

[0003] Wireless devices communicate with base stations via cells. Base stations are configured with wireless devices for various operating modes. Summary of the Invention

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

[0005] One or more parameters can indicate wireless device capabilities, such as those for one or more power-saving operations. For example, a first parameter might indicate whether the wireless device supports cell discontinuous transmission configuration via radio resource messaging, a second parameter might indicate whether the wireless device supports activating cell discontinuous transmission via downlink control information, and / or any other parameters might indicate whether the wireless device supports any other configurations associated with power saving. Based on the indicated wireless device capabilities, the wireless device can be configured and / or activated for one or more power-saving operations.

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

[0007] The accompanying drawings illustrate some features by way of example rather than limitation. The same reference numerals in the drawings refer to the same elements.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0034] Figure 17A , Figure 17B and Figure 17C An example MAC subheader is shown.

[0035] Figure 18A and Figure 18B An example MAC PDU is shown.

[0036] Figure 19 Example Logical Channel Identifier (LCID) values ​​are shown.

[0037] Figure 20 Example LCID values ​​are shown.

[0038] Figure 21A and Figure 21B An example secondary cell (SCell) activation / deactivation MAC control element (CE) is shown.

[0039] Figure 22 An example of BWP activation / deactivation is shown.

[0040] Figure 23 Examples of various downlink control information (DCI) formats are shown.

[0041] Figure 24A An example Master Message Block (MIB) message is shown.

[0042] Figure 24B An example configuration for CORESET is shown.

[0043] Figure 24C An example of search space configuration is shown.

[0044] Figure 25 An example of a System Information Block (SIB) is shown.

[0045] Figure 26 Example RRC configuration parameters are shown.

[0046] Figure 27 An example configuration of the search space is shown.

[0047] Figure 28 An example of a Synchronization Signal Block (SSB) configuration is shown.

[0048] Figure 29 An example of SSB transmission at a base station is shown.

[0049] Figure 30 An example of discontinuous reception (DRX) operation for a wireless device is shown.

[0050] Figure 31 An example of DRX operation for wireless devices is shown.

[0051] Figure 32A and Figure 32B An example of power-saving operation of a wireless device is shown.

[0052] Figure 33A and Figure 33B Examples of several TRP configurations are shown.

[0053] Figure 34 An example of a Layer 3-based handover procedure is shown.

[0054] Figure 35 An example of a Radio Resource Control (RRC) message for Layer 3-based handover is shown.

[0055] Figure 36 An example of an RRC message for layer 3-based handover is shown.

[0056] Figure 37 An example of a layer 3-based conditional handover procedure is shown.

[0057] Figure 38 An example of an RRC message used for a layer-based conditional handover procedure is shown.

[0058] Figure 39 An example of handover based on layer 1 or layer 2 is shown.

[0059] Figure 40 An example of inter-cell beam management is shown.

[0060] Figure 41 An example of mobility triggered by Layer 1 or Layer 2 with early CSI reports is shown.

[0061] Figure 42 A sample RRC message used for CSI reporting is shown.

[0062] Figure 43 A sample RRC message used for CSI reporting is shown.

[0063] Figure 44A sample RRC message used for CSI reporting is shown.

[0064] Figure 45 Examples of Cell Discontinuous Transmission (C-DTX) operation and User Equipment Discontinuous Reception (U-DRX) operation are shown.

[0065] Figure 46 Examples of C-DTX and U-DRX configurations are shown.

[0066] Figure 47 Examples of C-DTX and U-DRX configurations are shown.

[0067] Figure 48 Examples of C-DTX and U-DRX configurations are shown.

[0068] Figure 49A and Figure 49B An example of the C-DTX enable / disable command is shown.

[0069] Figure 50 An example problem illustrating network energy saving using mobility management is shown.

[0070] Figure 51 An example of using mobility management for network energy saving is shown. Detailed Implementation

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

[0072] 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 carrier-internal DNs. Radio device 106 may communicate with one or more DNs 108 via RAN 104 and / or via CN 102. CN 102 may provide / configure one or more interfaces to 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.

[0073] Radio device 106 can communicate with RAN 104 via radio communication through / via 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 / via air interface can be referred to as downlink and / or downlink communication direction. The communication direction from radio device 106 to RAN 104 via / via 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.

[0074] As used throughout, the term "wireless device" can include one or more of the following: mobile devices, fixed (e.g., non-mobile) devices configured or capable of wireless communication, computing devices, nodes, devices capable of wireless communication, or any other devices capable of transmitting and / or receiving signals. As a non-limiting example, a wireless device can include, for example: telephones, cellular phones, Wi-Fi phones, smartphones, tablet computers, computers, laptop computers, sensors, instruments, wearable devices, Internet of Things (IoT) devices, hotspots, cellular repeaters, vehicle roadside units (RSUs), relay nodes, automobiles, wireless user equipment (e.g., user equipment (UE), user terminal (UT), etc.), access terminals (AT), mobile stations, handheld devices, wireless transmit and receive units (WTRUs), wireless communication devices, and / or any combination thereof.

[0075] 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), first-generation Node B (base station / gNB), next-generation evolved Node B (ng-eNB), relay node (e.g., integrated access and backhaul (IAB) node), donor node (e.g., donor eNB, donor base station / gNB, etc.), access point (AP) (e.g., Wi-Fi access point), transmit / 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 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 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, an ng-eNB, a base station / gNB (e.g., associated with New Radio Interface (NR) and / or fifth-generation (5G) standards), an AP (e.g., associated with 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 base station / gNB central unit (gNB-CU)) and at least one base station distributed device (e.g., a base station / gNB distributed unit (gNB-DU)).

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

[0077] 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 APs, 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.

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

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

[0080] 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 may be configured to communicate with... Figure 1A The corresponding components are implemented and operated in essentially the same or similar manner.

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

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

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

[0084] 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 functions.

[0085] 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., a base station / gNB including base station / gNB 160A and base station / gNB 160B (collectively referred to as base station / gNB160)) and / or one or more second-type base stations (e.g., an ng-eNB 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. Base station / gNB 160 and / or ng-eNB 162 may be referred to as a base station. Base stations (e.g., gNB 160 and / or ng-gNB 162) may include one or more sets of antennas for wireless communication (e.g., through an air interface) with one or more radio devices 156. 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 / or ng-eNB 162) can provide radio coverage to one or more wireless devices 156 over a wide geographical area to support wireless device mobility.

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

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

[0088] Wireless devices can access base stations via interfaces (e.g., Uu interfaces) for user plane and control plane configuration. A base station (e.g., gNB 160) can provide user plane and control plane protocol terminals to wireless device 156 via the Uu interface. A base station (e.g., gNB 160A) can provide user plane and control plane protocol terminals to wireless device 156A via a Uu interface associated with a first protocol stack. A base station (e.g., ng-eNB 162) can provide E-UTRA user plane and control plane protocol terminals (e.g., where E-UTRA may refer to 3GPP 4G radio access technology) to one or more wireless devices 156 via the Uu interface. A base station (e.g., ng-eNB 162B) can provide E-UTRA user plane and control plane protocol terminals to wireless device 156B via a Uu interface associated with a second protocol stack. User plane and control plane protocol terminals may include, for example, NR user plane and control plane protocol terminals, 4G user plane and control plane protocol terminals, etc.

[0089] CN 152 (e.g., 5G-CN) can be configured to handle one or more radio accesses (e.g., NR, 4G, and / or any other radio access). The NR network / device (or any first network / device) can also be connected to a 4G core network / device (or any second network / device) in a non-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.

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

[0091] Figure 1A The communication network 100 and / or Figure 1BThe communication network 150 may include any number and / or type of devices, such as, for example, computing devices, wireless devices, mobile devices, handheld devices, tablet computers, laptop computers, IoT devices, hotspots, cellular repeaters, computing devices, and / or more generally, UEs. 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, 6G 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.

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

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

[0094] 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 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 one or more QoS streams 310 of the PDU session, for example, based on one or more QoS requirements (e.g., based on latency, data rate, bit error rate, and / or any other quality / service requirements). SDAPs 215 and 225 can perform mapping / demapping between one or more QoS streams 310 and one or more radio bearers 320 (e.g., data radio bearers). The mapping / demapping between 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 the 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.

[0095] 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., handover within a gNB). 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.

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

[0097] The RLC layers (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 layers (e.g., MAC 212 and 222, respectively). The RLC layers (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 layers (e.g., RLC 213 and 223) can perform one or more of the indicated functions, for example, based on the transmission mode in which the RLC layers (e.g., RLC 213 and 223) are 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 layers (e.g., RLC 213 and 223) can provide / configure RLC channel 330 as a service for the PDCP layers (e.g., PDCP 214 and 224, respectively), such as... Figure 3 As shown in the image.

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

[0099] The PHY layers (e.g., PHY 211 and 221) can perform mapping from transport channel 350 to physical channels 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 layers (e.g., PHY 211 and 221) can perform multi-antenna mapping. The PHY layers (e.g., PHY 211 and 221) can provide / configure one or more transport channels (e.g., transport channel 350) as services for the MAC layers (e.g., MAC 212 and 222, respectively).

[0100] 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 4AAs 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 4A The 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).

[0101] 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 to / from lower protocol layers can be called higher protocol layer Protocol Data Units (PDUs). For example... Figure 4A As shown, the data unit from SDAP 225 can be an SDU (e.g., PDCP SDU) of the lower protocol layer PDCP 224, and can also be a PDU (e.g., SDAP PDU) of SDAP 225.

[0102] 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 subheadings to two SDU segments) to MAC 222. MAC 222 can multiplex multiple RLC PDUs (MAC SDUs). MAC 222 can attach MAC subheadings to RLC PDUs (MAC SDUs) to form a TB. MAC subheadings 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.

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

[0104] One or more MAC control elements (CEs) can be added to or inserted into a MAC PDU through a MAC layer (such as MAC 212 or MAC 222). Figure 4B As shown, two MAC CEs can be inserted / added to a MAC PDU. MAC CEs can be inserted / added at the beginning of a MAC PDU for downlink transmission (e.g., ...). Figure 4B(As shown). One or more MAC CEs 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.

[0105] 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 5B An 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 particular wireless device, and / or shared logical channels that can be used by more than one wireless device (e.g., a group of wireless devices).

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

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

[0108] The PHY layer can use physical channels to pass / transmit information between processing layers of the PHY layer. Physical channels may include an associated set of time and frequency resources for carrying information about 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 Layer 1 or Layer 2 control channels, such as L1 or L2, Layer 1 / Layer 2, L1 / L2, Layer 1 or Layer 2, L1 / 2, etc.). The set of physical channels and physical control channels (e.g., defined by NR configuration or any other configuration) may include one or more of the following channels: Physical Broadcast Channel (PBCH) may include / carry MIBs from the BCH. Physical Downlink Shared Channel (PDSCH) may include / carry downlink data and signaling messages from the DL-SCH and paging messages from the PCH. The Physical Downlink Control Channel (PDCCH) may include / carry Downlink Control Information (DCI), which may include downlink scheduling commands, uplink scheduling grants, and uplink power control commands. The Physical Uplink Shared Channel (PUSCH) may include / carry uplink data and signaling messages from the UL-SCH, and in some cases 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 Indicator (CQI), Precoding Matrix Indicator (PMI), Rank Indicator (RI), and Scheduling Request (SR). The Physical Random Access Channel (PRACH) can be used for random access.

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

[0110] One or more of the channels (e.g., logical channels, transport channels, physical channels, etc.) can be used to perform functions associated with the control plane 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). Four similar protocol layers could 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 protocol stack) could 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 could include AMF 230, which includes NAS protocol 237.

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

[0112] 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 substantially 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 reporting and reporting; 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 parameters for communication between radio device 210 and RAN (e.g., base station 220).

[0113] 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 604 (e.g., RRC_INACTIVE). RRC inactive 604 can mean that the RRC is connected but inactive.

[0114] 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 or more base stations (e.g., Figure 1A One or more base stations of RAN 104 shown, Figure 1BOne of the base stations shown: gNB 160 or ng-eNB 162. 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, for example: 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, RAN 154, or any other RAN). 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 cell to be handed over to one of the neighboring base stations 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 604) via a connection inactivity procedure 610.

[0115] 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 per 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.

[0116] 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 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 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 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 604) to an RRC idle state (e.g., RRC idle 606) via a connection release procedure 616 that is substantially the same as or similar to the connection release procedure 608.

[0117] RRC states can be associated with mobility management mechanisms. During RRC idle states (e.g., RRC Idle 606) and RRC inactive states (e.g., RRC Inactive 604), mobility can be managed / controlled by 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 604) can be to enable / permit the network to notify the radio device of events via paging messages without broadcasting paging messages across the entire mobile network. Mobility management mechanisms used during RRC idle states (e.g., RRC Idle 606) or RRC inactive states (e.g., RRC Inactive 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 over the cell group in which the radio device currently resides (e.g., instead of sending paging messages over the entire mobile network). Mobility management mechanisms for RRC idle states (e.g., RRC idle 606) and RRC inactive states (e.g., RRC inactive 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)).

[0118] 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, CN 152, or any other CN) can send a list of TAIs associated with the radio device's registration area (e.g., the UE registration area) to the radio device. The radio device can perform a registration update with the CN to allow the CN to update the radio device's location and provide the radio device with a new radio device registration area, for example, if the radio device moves (e.g., via cell reselection) to a cell associated with a TAI that may not be included in the list of TAIs associated with the radio device's registration area.

[0119] 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 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). Base stations can belong to one or more RAN notification areas. Cells can belong to one or more RAN notification areas. For example, if a radio device moves (e.g., via cell reselection) to a cell that is 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 the radio device's RAN notification area.

[0120] 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 604).

[0121] 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 gNB-CU) and one or more distributed units (e.g., base station distributed units, such as 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.

[0122] 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 can be a multicarrier communication scheme that transmits / transmits data via F orthogonal subcarriers (or subcarriers). 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 symbol streams can be used as input to an Inverse Fast Fourier Transform (IFFT) block that transforms them into the time domain. The IFFT block can receive F source symbols at a time, receiving one source symbol from each of the F parallel symbol streams. The IFFT block can use each source symbol to modulate the amplitude and phase of a function corresponding to one of the F sinusoidal basis functions of 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). Inverse processing of the OFDM symbols can be performed at the receiver using the FFT block to recover the data mapped to the source symbols.

[0123] 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. The frame (e.g., an NR radio frame) may be identified / indicated by a System Frame Number (SFN) or any other value. The SFN may repeat in a period of 1024 frames. The duration of an NR radio 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.

[0124] The duration of a time slot can depend on the parameter set of the OFDM symbols used for the time slot. For example, flexible parameter sets can be supported to accommodate different deployments (e.g., cells with carrier frequencies below 1 GHz to cells with carrier frequencies in the millimeter-wave range). For example, flexible parameter sets can be supported in NR configurations or any other radio 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.

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

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

[0127] It can be on a carrier (e.g.) Figure 8 A single set of parameters is used across the entire bandwidth of the NR carrier shown. In other example configurations, multiple sets of parameters 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.

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

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

[0130] 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 downlink BWP in a set of configured downlink BWPs on a primary cell (PCell) or secondary cell (SCell). The search space can include a set of locations in the time and frequency domains where the radio device can monitor / find / detect / identify control information. The search space can be a radio device-specific search space (e.g., a UE-specific search space) or a common search space (e.g., possibly used by multiple radio devices or a group of radio user equipments). The base station can configure a common search space for a group of radio devices in active downlink BWPs on a PCell or primary / secondary cell (PSCell).

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

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

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

[0134] The base station can configure a BWP inactivity timer value for the PCell for the wireless device. The wireless device can start or restart the BWP inactivity timer at any appropriate time. For example, the wireless device can start or restart the BWP inactivity timer if one or more conditions are met. The one or more conditions may include at least one of the following: the wireless device detects 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.

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

[0136] 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). Configured BWP handovers can occur, for example, based on RRC signaling, DCI signaling, the expiration of a BWP inactivity timer, and / or the initiation of random access.

[0137] 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 the active BWP (e.g., 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 the active BWP (e.g., 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 the active BWP (e.g., 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 may, for example, switch from the active BWP (e.g., 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.

[0138] The radio device procedure for handing over a BWP on a secondary cell can be substantially the same as / similar to the procedure on the primary cell, for example, if the radio device is configured for a secondary cell with a default downlink BWP and timer values ​​from a set of configured downlink BWPs. The radio device can use timer values ​​and the default downlink BWP for the secondary cell in a substantially the same / similar manner as the radio device uses timer values ​​and / or the default downlink 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, for example, hand over to another BWP based on the expiration of the BWP inactivity timer.

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

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

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

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

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

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

[0145] Figure 10B An example cell group is shown. Aggregated cells can be configured into one or more PUCCH groups (e.g., such as...). Figure 10B(As shown). One or more cell groups or one or more uplink control channel groups (e.g., PUCCH group 1010 and PUCCH group 1050) may each include one or more downlink CCs. PUCCH group 1010 may include one or more downlink CCs, for example, three downlink CCs: PCell 1011 (e.g., DL PCC), SCell 1012 (e.g., DL SCC), and SCell 1013 (e.g., DL SCC). PUCCH group 1050 may include one or more downlink CCs, for example, three downlink CCs: PUCCH SCell (or PSCell) 1051 (e.g., DL SCC), SCell 1052 (e.g., DL SCC), and SCell 1053 (e.g., DL SCC). One or more uplink CCs of PUCCH group 1010 may be configured as PCell 1021 (e.g., UL PCC), SCell 1022 (e.g., UL SCC), and SCell 1023 (e.g., 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.

[0146] 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 used / applied to, for example, carrier activation. The activation of the first carrier may refer to the activation of the cell that includes the first carrier.

[0147] 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 for each assignment / grant for each serving cell. Transport blocks and potential HARQ retransmissions of transport blocks can be mapped to the serving cell.

[0148] For the downlink, the base station may send / transmit (e.g., unicast, multicast, and / or broadcast) one or more 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.

[0149] 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). Bursts can be sent / transmitted periodically (e.g., every 2 frames, 20 milliseconds, or any other duration). Bursts can be limited to half-frames (e.g., a first half-frame lasting 5 ms). Such parameters (e.g., the number of SS / PBCH blocks per burst, the periodicity of the burst, the position of the burst within a frame) can be configured, for example, based on at least one of the following: the carrier frequency of the cell in which the SS / PBCH blocks are sent / transmitted; the parameter set or subcarrier spacing of the cell; configuration by the network (e.g., using RRC signaling); and / or any other suitable factors. For example, unless the wireless network configures the wireless device to assume different subcarrier spacings, the wireless device can assume the subcarrier spacing of the SS / PBCH blocks based on the monitored carrier frequency.

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

[0151] The radio device may not know the location of the SS / PBCH block in the time and frequency domains (e.g., if the radio device is searching for a cell). For example, the radio device can monitor the carrier of the PSS 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, respectively, for example, based on the known structure of the SS / PBCH block. The SS / PBCH block may be a cell-defined SS block (CD-SSB). The primary cell may be associated with a CD-SSB. The CD-SSB may be located on a synchronization grating. Cell selection / search and / or reselection may be based on the CD-SSB.

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

[0153] 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 an 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 Minimal 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.

[0154] 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 reception (Rx) parameters). A wireless device may not assume QCL for the transmission 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 the 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.

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

[0156] CSI-RS can be sent / transmitted by the base station and used by the wireless device to acquire / obtain / determine 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 substantially identical / 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.

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

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

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

[0160] 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 (or any other number of orthogonal downlink DM-RS ports) (e.g., for single-user MIMO). The DM-RS configuration can support up to four orthogonal downlink DM-RS ports per radio device (or any other number of orthogonal downlink DM-RS ports) (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. DM-RS locations, DM-RS modes, and / or scrambling sequences can be substantially 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.

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

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

[0163] For example, a wireless device can transmit / transmit uplink DM-RS to a base station for channel estimation. The base station can use the uplink DM-RS for coherent demodulation of one or more uplink physical channels. The wireless device can utilize PUSCH and / or PUCCH to 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 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.

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

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

[0166] 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 port from the channel used to transmit the first symbol on the antenna port. For example, if one or more large-scale properties can be inferred / determined from the channel transmitting the second symbol on the second antenna port, the first antenna port and the second antenna port can be referred to as QCLs. One or more large-scale properties can include at least one of the following: delay spread; Doppler spread; Doppler shift; average gain; average delay; and / or spatial Rx parameter.

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

[0168] 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 11B Each rectangular block shown may correspond to an 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 may be configured via higher-layer signaling (e.g., RRC and / or MAC signaling) used for CSI-RS resource configuration. One or more parameters may include at least one of the following: CSI-RS resource configuration identity; number of CSI-RS ports; CSI-LS configuration (e.g., symbols and RE positions in subframes); CSI-RS subframe configuration (e.g., subframe position, offset, and periodicity in radio frames); CSI-RS power parameters; CSI-RS sequence parameters; Code Division Multiple Access (CDM) type parameters; frequency density; transport comb; QCL parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid); and / or other radio resource parameters.

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

[0170] CSI-RS (e.g., CSI-RS 1101, 1102, 1103) can be transmitted / transmitted by a base station and used by a wireless device for one or more measurements. The wireless device can measure the Reference Signal Received Power (RSRP) of the configured CSI-RS resources. The base station can configure a reporting configuration for the wireless device, and the wireless device can report 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 Indication (TCI) states, including multiple 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 capabilities. If the wireless device has beam-matching capabilities, 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 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.

[0171] A wireless device can, for example, determine / evaluate (e.g., measure) the channel quality of one or more beampup links in a beam management procedure. A beampup link may include a base station's Tx beam and a wireless device's Rx beam. The base station's Tx beam can transmit / transmit downlink signals, and the wireless device's Rx beam can receive downlink signals. For example, the wireless device can transmit / transmit a beam measurement report based on 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, PMI, CQI, and / or RI.

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

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

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

[0175] A wireless device may, for example, use one or more RSs 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 measurements of the RS resources: block error rate (BLER), RSRP value, signal-to-interference-plus-noise ratio (SINR) value, RSRQ value, and / or CSI value. A base station may indicate the QCL (Quick Closed) of the RS resources and one or more DM-RSs for a channel (e.g., a control channel, a shared data channel, etc.). For example, if the channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameter, fading, etc.) from transmission via the RS resources to the wireless device are substantially the same or similar to the channel characteristics from transmission via the channel to the wireless device, then the RS resources and one or more DM-RSs for the channel may be QCLed.

[0176] Networks (e.g., NR networks including base stations / 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) state and / or an RRC inactive state (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 SIBs (e.g., any 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 establishment time alignments for SCells.

[0177] 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. The base station may, for example, send / transmit configuration message 1310 to the radio device before initiating the random access procedure. The four-step random access procedure may include the transmission of four messages, including: a first message (e.g., Msg 1 1311), a second message (e.g., Msg 2 1312), a third message (e.g., Msg 3 1313), and a fourth message (e.g., Msg 4 1314). The first message (e.g., Msg 1 1311) may include a preamble (or random access preamble). The first message (e.g., Msg 1 1311) may be referred to as a preamble. The second message (e.g., Msg 2 1312) may include a random access response (RAR). The second message (e.g., Msg 2 1312) may be referred to as a RAR.

[0178] 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 RACH parameters to the radio device. 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). The base station 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 devices in an RRC connected (e.g., RRC_CONNECTED) state and / or an RRC inactive (e.g., RRC_INACTIVE) state. The radio device may 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 the one or more RACH parameters. The wireless device may determine the receive timing and downlink channel for receiving the second message (e.g., Msg 2 1312) and the fourth message (e.g., Msg 4 1314) based, for example, on one or more of the RACH parameters.

[0179] One or more RACH parameters provided / configured / included in configuration message 1310 may indicate one or more 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 the association between (a) one or more PRACH timings and (b) one or more reference signals. The one or more RACH parameters may indicate the 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.

[0180] 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: a power ramp-up step; a power offset between the SSB and CSI-RS; a 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 a power offset value between preamble groups. The one or more RACH parameters may indicate one or more thresholds. For example, a wireless device may determine at least one reference signal (e.g., SSB and / or CSI-RS) and / or uplink carrier (e.g., normal uplink (NUL) carrier and / or supplementary uplink (SUL) carrier) based on the one or more thresholds.

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

[0182] For example, a wireless device may determine a preamble based on one or more RACH parameters provided / configured / included in configuration message 1310. The wireless device may determine the preamble based, for example, path loss measurement results, RSRP measurement results, and / or the size of a third message (e.g., Msg 3 1313). One or more RACH parameters may indicate at least one of the following: preamble format; 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). A base station may use one or more RACH parameters to configure a wireless device having associations between one or more preambles and one or more reference signals (e.g., SSB and / or CSI-RS). For example, if an association is configured, the wireless device may determine, based on the association, that a preamble should be included in a first message (e.g., Msg 1 1311). The first message (e.g., Msg 1 1311) may be sent / transmitted to the base station via one or more PRACH timings. The wireless device may use one or more reference signals (e.g., SSB and / or CSI-RS) to select the preamble and determine the PRACH timing. One or more RACH parameters (e.g., ra-ssb-OccasionMskIndex and / or ra-OccasionList) may indicate the association between the PRACH timing and the one or more reference signals.

[0183] 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), the wireless device can perform a preamble retransmission. The wireless device can increase the uplink transmission power for preamble retransmission. The wireless device can select the initial preamble transmission power, for example, based on path loss measurements and / or the target receive preamble power configured by the network. The wireless device can determine to retransmit / re-transmit the preamble and can ramp up the uplink transmission power. The wireless device can receive one or more RACH parameters (e.g., PREAMBLE_POWER_RAMPING_STEP) indicating the ramp step for preamble retransmission. The ramp step can be an incremental increase in the uplink transmission power for retransmission. For example, if the wireless device determines that the same reference signal (e.g., SSB and / or CSI-RS) is used as in the previous preamble transmission, the wireless device can ramp up the uplink transmission power. The wireless device 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), the wireless device may determine that the random access procedure did not complete successfully.

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

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

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

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

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

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

[0190] Figure 13BA two-step random access procedure is illustrated. This two-step random access procedure may include a two-step contention-free random access procedure. Similar to a four-step contention-based random access procedure, the base station may send / transmit configuration message 1320 to the radio device before initiating the procedure. Configuration message 1320 may be similar 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).

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

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

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

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

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

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

[0197] Transport block 1342 may include data (e.g., delay-sensitive data), a radio device identifier, security information, and / or device information (e.g., International Mobile Subscriber Identity (IMSI)). The base station may send / transmit a second message (e.g., MsgB 1332) as a response to the first message (e.g., Msg A 1331). The second message (e.g., Msg B 1332) may include at least one of the following: a preamble identifier; a timing advance command; a power control command; uplink 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 TC-RNTI). For example, if the preamble identifier in the second message (e.g., Msg B 1332) corresponds to or matches the preamble sent / transmitted by the wireless device and / or the identifier of the wireless device in the second message (e.g., Msg B 1332) corresponds to or matches the identifier of the wireless device in the first message (e.g., Msg A 1331) (e.g., transport block 1342), then the wireless device can determine that the two-step random access procedure was successfully completed.

[0198] The wireless device and the base station can exchange control signaling (e.g., control information). Control signaling can be referred to as Layer 1 or Layer 2 (e.g., L1 or L2, Layer 1 / Layer 2, L1 / L2, Layer 1 or Layer 2, L1 / 2, Layer 1 / 2, etc.) control signaling and can 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 can 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.

[0199] 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 the DCI. The PDCCH may be a group common PDCCH (GC-PDCCH) shared by a group of radio devices. The GC-PDCCH may be scrambled by a group common RNTI.

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

[0201] DCIs can be used for various purposes. The purpose can be indicated by the type of RNTI used to scramble the CRC parity bits. A DCI with CRC parity bits scrambled with a paging RNTI (P-RNTI) can indicate paging information and / or system information change notifications. A P-RNTI can be predefined as "FFFE" in hexadecimal. A DCI with CRC parity bits scrambled with a system information RNTI (SI-RNTI) can indicate broadcast transmission of system information. A SI-RNTI can be predefined as "FFFF" in hexadecimal. A DCI with CRC parity bits scrambled with a random access RNTI (RA-RNTI) can indicate a random access response (RAR). A DCI with CRC parity bits scrambled with a cell RNTI (C-RNTI) can indicate the triggering of random access for dynamically scheduled unicast transmissions and / or PDCCH commands. A DCI with CRC parity bits scrambled with a temporary cell RNTI (TC-RNTI) can indicate contention resolution (e.g., similar to...). Figure 13A The Msg3 in Msg3 1313 shown is an example. Other RNTIs configured by the base station for the radio device may include 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.

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

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

[0204] 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 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 of resource blocks in the frequency domain.

[0205] Figure 14B An example of CCE-to-REG mapping is shown. CCE-to-REG mapping for DCI transmission can be performed via CORESET and PDCCH processing. CCE-to-REG mapping can be interleaved mapping (e.g., for the purpose of providing frequency diversity) or non-interleaved mapping (e.g., for the purpose of facilitating interference coordination and / or frequency-selective transmission of the control channel). The base station can perform different or the same CCE-to-REG mapping on different CORESETs. CORESETs can be associated with CCE-to-REG mapping (e.g., via RRC configuration). CORESETs can be configured with antenna port QCL parameters. Antenna port QCL parameters can indicate the QCL information for DM-RS received via the PDCCH of the CORESET.

[0206] The base station may send / transmit one or more RRC messages to the radio device, including configuration parameters for one or more CORESETs and one or more search space sets. These configuration parameters may indicate the association between the search space set and the CORESET. The search space set may include a set of PDCCH candidates formed by CCEs (e.g., at a given aggregation level). These configuration parameters may indicate at least one of the following: the number of PDCCH candidates to be monitored 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 may 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) may be configured, for example, based on the radio device's identity (e.g., C-RNTI).

[0207] like Figure 14B As shown, the wireless device can determine the time and frequency resources for the CORESET based on one or more RRC messages. For example, the wireless device can determine the CCE-to-REG mapping (e.g., interleaved or non-interleaved and / or mapping parameters) for the CORESET based on the CORESET's configuration parameters. The wireless device can determine, for example, the number of search space sets configured on / for the CORESET (e.g., up to 10) based on the one or more RRC messages. The wireless device can monitor the PDCCH candidate set according to the configuration parameters of the search space set. The wireless device can monitor the PDCCH candidate set in one or more CORESETs to detect one or more DCIs. Monitoring may include decoding one or more PDCCH candidates in the monitored DCI format. Monitoring may include decoding the DCI content of one or more PDCCH candidates using possible (or configured) PDCCH locations, possible (or configured) PDCCH formats (e.g., the number of CCEs, the number of PDCCH candidates in the common search space, and / or the number of PDCCH candidates in the 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.).

[0208] The wireless device can send / transmit uplink control signaling (e.g., UCI) to the base station. The uplink control signaling may include HARQ acknowledgments for received DL-SCH transport blocks. The wireless 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). The uplink control signaling may include a Channel Quality Indicator (CSI) indicating the channel quality of the physical downlink channel. The wireless device may send / transmit the CSI to the base station. Based on the received CSI, the base station may determine transmission format parameters (e.g., including multiple antennas and beamforming schemes) for downlink transmission. The uplink control signaling may include a Reporting Message (SR). The wireless device may send / transmit an SR indicating that uplink data is available for transmission to the base station. The wireless device may send / transmit UCIs (e.g., HARQ acknowledgments, CSI reports, SRs, etc.) via PUCCH or PUSCH. The wireless device may use one of several PUCCH formats to send / transmit uplink control signaling via PUCCH.

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

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

[0211] For example, after determining a set of PUCCH resources for UCI (HARQ-ACK, CSI, and / or SR) transmission from multiple PUCCH resource sets, the radio device can determine PUCCH resources from said PUCCH resource set. The radio device can determine the PUCCH resources, for example, based on the PUCCH resource indicator in a DCI (e.g., a DCI with DCI format 1_0 or for 1_1) received on / via the PDCCH. An n-bit (e.g., three-bit) PUCCH resource indicator in the DCI can indicate one of a plurality (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) based on the PUCCH resource indicator.

[0212] Figure 15AAn example of communication between a wireless device and a base station is shown. 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.

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

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

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

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

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

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

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

[0220] 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 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 output data) / provide output data (e.g., user output data) from and / or to the one or more peripheral devices 1516 and / or 1526. The processing system 1518 in the wireless device 1502 can receive power from a power source and / or can be configured to distribute power to other components in the wireless device 1502. The power source may include one or more power sources, such as a battery, solar cell, fuel cell, or any combination thereof. The processing system 1508 may be connected to a Global Positioning System (GPS) chipset 1517. The processing system 1518 may be connected to a Global Positioning System (GPS) chipset 1527. The GPS chipset 1517 and GPS chipset 1527 may be configured, respectively, to determine and provide geographic location information for the wireless device 1502 and the base station 1504.

[0221] 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 and / or 1504, wireless devices 106, 156A, 156B, 210 and / or 1502, or any other base station, wireless device, AMF, UPF, network device, or computing device described herein. The computing device 1530 may include one or more processors 1531 that can execute instructions stored in random access memory (RAM) 1533, removable media 1534 (such as a USB drive, optical disc (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 the computing device 1530 with an interface to communicate with network 1540 (e.g., RAN or any other network). Network interface 1539 may include a modem (e.g., a cable modem), and external network 1540 may include a communication link, an external network, a home network, a provider's wireless, coaxial cable, fiber optic, or hybrid fiber / coaxial cable distribution system (e.g., a DOCSIS network), or any other desired network. Additionally, computing device 1530 may include a location detection device, such as a GPS microprocessor 1541, which can be configured to receive and process global positioning signals and determine the geographic location of computing device 1530 with possible assistance from external servers and antennas.

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

[0223] 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 complex-valued modulated symbols onto one or more transport layers; transform precoding to generate complex-valued symbols; precoding the complex-valued symbols; mapping the precoded complex-valued symbols to resource elements; generating complex-valued time-domain single-carrier frequency division multiple access (SC-FDMA), CP-OFDM signals for antenna ports, or any other signals; and so on. For example, if transform precoding is enabled, an SC-FDMA signal for uplink transmission can be generated. For example, if transform precoding is not enabled (e.g., as...), Figure 16A As shown, CP-OFDM signals for uplink transmission can then be generated. These functions are examples, and other mechanisms for uplink transmission can be implemented.

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

[0225] 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; and so on. These functions are examples, and other mechanisms for downlink transmission can be implemented.

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

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

[0228] A timer can, for example, begin running after its start and continue running until it stops or 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 start from zero and expire after reaching that value). For example, the duration of a timer may not be updated until it stops or expires (e.g., due to a BWP switch). A timer can be used to measure time periods / windows used in a process. Regarding implementations and / or procedures associated with one or more timers or other parameters, it should be understood that there are multiple ways to implement the one or more timers or other parameters. One or more of the multiple ways of implementing a timer can be used to measure time periods / windows used in a program. A random access response window timer can be used to measure a time window for receiving a random access response. For example, instead of starting the random access response window timer and determining its expiration, the time difference between two timestamps can be used. For example, if the timer is restarted, the process used to measure the time window can be restarted. Other example implementations can be configured / provided to restart the measurement of the time window.

[0229] Base stations can communicate with wireless devices via a wireless network (e.g., a communication network). Communication may use / emulate one or more radio technologies (e.g., new radio technologies, traditional radio technologies, and / or combinations thereof). The one or more radio technologies may include at least one of the following: one or more technologies related to the physical layer; one or more technologies related to the media access control layer; and / or one or more technologies related to the radio resource control layer. One or more enhanced radio technologies described herein can improve the performance of the wireless network. System throughput, wireless network transmission efficiency, and / or data transmission rate can be improved, for example, based on one or more configurations described herein. Battery consumption of the wireless device can be reduced, for example, based on one or more configurations described herein. Data transmission latency between the base station and the wireless device can be improved, for example, based on one or more configurations described herein. Network coverage of the wireless network can be increased, for example, based on one or more configurations described herein.

[0230] A base station can send / transmit one or more MAC PDUs to a wireless device. A MAC PDU can be a bit string of byte-aligned length (e.g., aligned to multiples of octets). The bit string can be represented by one or more tables, where the most significant bit can be the leftmost bit of the first row of the table, and the least significant bit can be the rightmost bit of the last row of the table. The bit string can be read from left to right, followed by line-by-line reading order (e.g., from the top line of the table to the bottom line of the table). The bit order of parameter fields within a MAC PDU can be represented using the first and most significant bits of the leftmost position and the last and least significant bits of the rightmost position.

[0231] A MAC SDU can be a bit string whose length is byte-aligned (e.g., aligned to multiples of octets). A MAC SDU may be included in a MAC PDU starting from the first bit. A MAC CE can be a bit string whose length is byte-aligned (e.g., aligned to multiples of octets). A MAC subheader can be a bit string whose length is byte-aligned (e.g., aligned to multiples of octets). A MAC subheader may be placed immediately before the corresponding MAC SDU, MAC CE, or padding. A wireless device (e.g., the MAC entity of the wireless device) may omit the values ​​of reserved bits in the downlink (DL) MAC PDU.

[0232] A MAC PDU may include one or more MAC subPDUs. A MAC subPDU within one or more MAC subPDUs may include: a MAC subheader only (containing padding); a MAC subheader and a MAC SDU; a MAC subheader and a MAC CE; a MAC subheader and padding; and / or combinations thereof. A MAC SDU may have a variable size. A MAC subheader may correspond to a MAC SDU, a MAC CE, or padding.

[0233] For example, if the MAC subheader corresponds to a MAC SDU, a variable-size MAC CE, or padding, the MAC subheader may include: an R field with a one-bit length; an F field with a one-bit length; an LCID field with a multi-bit length; an L field with a multi-bit length; and / or a combination thereof.

[0234] Figure 17A An example of a MAC subheader is shown. A MAC subheader may include an R field, an F field, an LCID field, and / or an L field. The LCID field can be six bits long (or any other number of bits). The L field can be eight bits long (or any other number of bits). Each of the R and F fields can be one bit long (or any other number of bits). Figure 17B An example of a MAC subheader is shown. A MAC subheader may include an R field, an F field, an LCID field, and / or an L field. Similar to... Figure 17AThe MAC subheader shown can have an LCID field that is six bits long (or any other number of bits), an R field that is one bit long (or any other number of bits), and an F field that is one bit long (or any other number of bits). The L field can be sixteen bits long (or any other number of bits, such as a length greater than sixteen bits). For example, if the MAC subheader corresponds to a fixed-size MAC CE or padding, the MAC subheader can include: an R field with a length of two bits (or any other number of bits), and / or an LCID field with a length of multiple bits (or a unit length). Figure 17C An example of a MAC subheader is shown. Figure 17C In the example MAC subheader shown, the LCID field can be six bits long (or any other number of bits), and the R field can be two bits long (or any other number of bits).

[0235] Figure 18A An example of a MAC PDU (e.g., a DL MAC PDU) is shown. Multiple MAC CEs (such as...) are also shown. Figure 18A MAC CEs 1 and 2 shown can be placed together (e.g., within the same MAC PDU). A MAC subPDU including a MAC CE can be placed before any MAC subPDU including a MAC SDU or before a MAC subPDU including padding (e.g., within the MAC PDU). MAC CE 1 can be a fixed-size MAC CE that conforms to a Type 1 MAC subheader. A Type 1 MAC subheader may include an R field and an LCID field (e.g., similar to...). Figure 17C The MAC CE shown is an example of a MAC CE 2. MAC CE 2 can be a variable-size MAC CE that conforms to a Type 2 MAC subheader. The Type 2 MAC subheader may include an R field, an F field, an LCID field, and an L field (e.g., similar to...). Figure 17A or Figure 17B The MAC CE shown is an example. The size of the MACSDU, which follows the second type of MAC subheader, can vary.

[0236] Figure 18B An example of a MAC PDU (e.g., a UL MAC PDU) is shown. Multiple MAC CEs (such as...) Figure 18BMAC CEs 1 and 2 shown can be placed together (e.g., within the same MAC PDU). A MAC subPDU including a MAC CE can be placed after all MAC subPDUs including a MAC SDU (e.g., within a MAC PDU). A MAC subPDU including a MAC CE and / or a MAC subPDU can be placed before a MAC subPDU including a filler (e.g., within a MAC PDU). Similar to... Figure 18A The MAC CE shown Figure 18B The MAC CE 1 shown can be a fixed-size MAC CE that conforms to a Type 1 MAC subheader. The Type 1 MAC subheader may include an R field and an LCID field (e.g., similar to...). Figure 17C The MAC CE shown is similar to... Figure 18A The MAC CE shown Figure 18B The MAC CE 2 shown can be a variable-size MAC CE that conforms to a Type II MAC subheader. The Type II MAC subheader may include an R field, an F field, an LCID field, and an L field (e.g., similar to...). Figure 17A or Figure 17B The MAC CE shown is an example. The size of the MAC SDU that follows the second type of MAC subheader can vary.

[0237] A base station (e.g., the MAC entity of a base station) may send / transmit one or more MAC CEs to a wireless device (e.g., the MAC entity of a wireless device). Figure 19Example LCID values ​​are shown. An LCID value can be associated with one or more MAC CEs. An LCID value can also be associated with a downlink channel, such as DL-SCH. One or more MAC CEs may include at least one of the following: a semi-persistent zero-power CSI-RS (SP ZP CSI-RS) resource set activation / deactivation MAC CE; a PUCCH spatial relation activation / deactivation MAC CE; an SP SRS activation / deactivation MAC CE; an SP CSI report regarding a PUCCH activation / deactivation MAC CE; a radio device-specific (e.g., UE-specific) PDCCH MAC CE TCI status indication; a radio device-specific (e.g., UE-specific) PDSCH MAC CE TCI status indication; an aperiodic CSI trigger state subselect MAC CE; an SP CSI-RS / CSI interference measurement (CSI-IM) resource set activation / deactivation MAC CE; a radio device (e.g., UE) contention resolution identity MAC CE; a timing advance command MAC CE; a DRX command MAC CE; a long DRX command MAC CE; a SCell activation / deactivation MAC CE (e.g., one octet); a SCell activation / deactivation MAC CE. CE (e.g., 4 octets); and / or copy activation / deactivation of MAC CE. MAC CEs, such as those sent / transmitted by a base station (e.g., the MAC entity of the base station) to a wireless device (e.g., the MAC entity of the wireless device), can be associated with an LCID in the MAC subheader corresponding to the MAC CE (e.g., the LCID corresponding to the LCID). Different MAC CEs can correspond to different LCIDs in the MAC subheader corresponding to the MAC CE. An LCID with the index value "111011" in the MAC subheader can indicate that the MAC CE associated with the MAC subheader is a long DRX command MAC CE, for example, a MAC CE associated with a downlink.

[0238] A wireless device (e.g., the MAC entity of the wireless device) may send / transmit one or more MAC CEs to a base station (e.g., the MAC entity of the base station). Figure 20Example LCID values ​​that can be associated with one or more MAC CEs are shown. LCID values ​​can be associated with uplink channels, such as UL-SCH. One or more MAC CEs can include at least one of the following: Short Buffer Status Report (BSR) MAC CE; Long BSR MAC CE; C-RNTI MAC CE; Configured Acknowledgment MAC CE; Single Entry Power Headroom Report (PHR) MAC CE; Multi-Entry PHR MAC CE; Short Truncated BSR; and / or Long Truncated BSR. MAC CEs can be associated with an LCID in the MAC subheader corresponding to the MAC CE (e.g., corresponding to the LCID). Different MAC CEs can correspond to different LCIDs in the MAC subheader corresponding to the MAC CE. An LCID with the index value "111011" in the MAC subheader can indicate that the MAC CE associated with the MAC subheader is a Short Truncated Command MAC CE, for example, for an uplink-associated MAC CE.

[0239] Two or more CCs can be aggregated, such as in carrier aggregation (CA). A wireless device can, for example, receive and / or transmit data simultaneously via one or more CCs, depending on its capabilities (e.g., using CA techniques). The wireless device can support CA for consecutive CCs and / or for non-consecutive CCs. CCs can be organized into cells. CCs can be organized into one PCell and one or more SCells.

[0240] For example, if the wireless device is configured with a CA, the wireless device can have an RRC connection with the network (e.g., an RRC connection). During RRC connection establishment / re-establishment / handover, the cell providing / transmitting / configuring NAS mobility information can be the serving cell. During the RRC connection re-establishment / handover procedure, the cell providing / transmitting / configuring security input can be the serving cell. The serving cell can be a PCell. The base station can, for example, depending on the capabilities of the wireless device, send / transmit one or more messages to the wireless device including configuration parameters for multiple SCells.

[0241] For example, if CA is configured, the base station and / or wireless device can use / adopt an SCell activation / deactivation mechanism. For example, the base station and / or wireless device can use / adopt an SCell activation / deactivation mechanism to improve the battery usage and / or power consumption of the wireless device. For example, if the wireless device is configured with one or more SCells, the base station can activate or deactivate at least one of the one or more SCells. An SCell can be deactivated unless, for example, the SCell state associated with it is set to an active state (e.g., "activated") or a dormant state (e.g., "dormant") after the SCell is configured.

[0242] A radio device can activate / deactivate a SCell. The radio device can activate / deactivate a cell based on receiving a SCell activation / deactivation MAC CE (e.g., after or in response to this). The SCell activation / deactivation MAC CE may each include one or more fields associated with one or more SCells to indicate the activation or deactivation of one or more SCells. For example, if the aggregated cell has fewer than eight SCells, the SCell activation / deactivation MAC CE may correspond to an octet including seven fields associated with at most seven SCells. The SCell activation / deactivation MAC CE may include an R field. For example, if the aggregated cell has more than seven SCells, the SCell activation / deactivation MAC CE may include multiple octets including more than seven fields associated with more than seven SCells.

[0243] Figure 21A An example SCell activation / deactivation MAC CE of an octet is shown. This includes the first LCID (e.g., as shown in the image). Figure 19 The first MAC PDU subheader (shown as '111010') can indicate / identify an octet of SCell activation / deactivation MAC CE. An octet of SCell activation / deactivation MAC CE can have a fixed size. An octet of SCell activation / deactivation MAC CE can comprise a single octet. A single octet can comprise a first quantity of C fields (e.g., seven or any other quantity) and a second quantity of R fields (e.g., one or any other quantity).

[0244] Figure 21B An example SCell activation / deactivation MAC CE with four octets is shown. This includes a second LCID (e.g., as shown in the image). Figure 19 The second MAC PDU subheader (shown as '111001') can indicate / identify a four-octet SCell activation / deactivation MAC CE. The four-octet SCell activation / deactivation MAC CE can have a fixed size. The four-octet SCell activation / deactivation MAC CE can include four octets. The four octets can include a third quantity / number of C fields (e.g., 31 or any other quantity / number) and a fourth quantity / number of R fields (e.g., 1 or any other quantity / number).

[0245] like Figure 21A and / or Figure 21BAs shown, for example, if an SCell with / corresponding to SCell index i is configured, the Ci field can indicate the active / deactivated state of the SCell with / corresponding to SCell index i. For example, if the Ci field is set to one, the SCell with SCell index i can be activated. For example, if the Ci field is set to zero, the SCell with SCell index i can be deactivated. For example, if no SCell with SCell index i is configured, the wireless device can ignore the Ci field. The R field can indicate reserved bits. The R field can be set to zero or any other value (e.g., for other purposes).

[0246] A base station can configure uplink (UL) BWPs and downlink (DL) BWPs for a radio device to enable bandwidth adaptation (BA) on a PCell. For example, if carrier aggregation is configured, the base station can also configure at least one or more DL BWPs for the radio device (i.e., a UL BWP may not be present in the UL) to enable BA on a SCell. For example, for a PCell, the initial active BWP can be a first BWP for initial access. The first active BWP can be a second BWP configured for the radio device to operate on the SCell when the SCell is activated. For example, in paired spectrum (e.g., FDD), the base station and / or the radio device can independently switch between the DL BWP and the UL BWP. For example, in unpaired spectrum (e.g., TDD), the base station and / or the radio device can simultaneously switch between the DL BWP and the UL BWP.

[0247] Base stations and / or radio devices can switch BWPs between configured BWPs using DCI messages or BWP inactivity timers. For example, if a BWP inactivity timer is configured for the serving cell, the base station and / or radio device can switch the active BWP to the default BWP based on the expiration of the BWP inactivity timer associated with the serving cell (e.g., after or in response to this). The default BWP can be configured by the network. For example, if an FDD system is configured with BA, one UL BWP and one DL BWP for uplink carriers (e.g., per uplink carrier) can be active simultaneously in the active serving cell. For example, in a TDD system, one DL / UL BWP pair can be active simultaneously in the active serving cell. Operating on one UL BWP and one DL BWP (or one DL / UL pair) can improve radio device battery consumption. BWPs other than one active UL BWP and one active DL BWP that the radio device can operate on can be deactivated. The radio device can choose not to monitor, for example, PDCCH transmissions on the deactivated BWP. The wireless device may not transmit (e.g., transmit) on, for example, the PUCCH, PRACH, and UL-SCH on the BWP.

[0248] A serving cell can be configured with a maximum number of BWPs (e.g., four). At any given time, for example, for an active serving cell, there can be one active BWP. BWP handover of the serving cell can be used to activate an inactive BWP and deactivate an active BWP. BWP handover can be controlled by PDCCH transmissions indicating downlink assignment or uplink permission. BWP handover can be controlled by a BWP inactivity timer (e.g., bwp-InactivityTimer). BWP handover can be controlled by the radio device (e.g., the radio device's MAC entity) based on initiating a random access procedure (e.g., after or in response to this). For example, when adding a SpCell or activating an SCell, a BWP can initially be active without receiving PDCCH transmissions indicating downlink assignment or uplink permission. The active BWP of the serving cell can be indicated by one or more configuration parameters (e.g., parameters of RRC messages) and / or PDCCH transmissions. For unpaired spectrum, a DL BWP can be paired with a UL BWP, and BWP handover may be common to both UL and DL.

[0249] Figure 22An example of BWP activation / deactivation is shown. BWP activation / deactivation can occur on a cell (e.g., PCell or SCell). BWP activation / deactivation can be associated with BWP handover (e.g., BWP handover may include BWP activation / deactivation). At step 2202 (e.g., from base station 2200), radio device 2220 may receive (e.g., detect) at least one message (e.g., RRC message) including cell parameters and one or more BWPs associated with the cell. The RRC message may include at least one of the following: an RRC connection reconfiguration message (e.g., RRCReconfiguration); an RRC connection establishment message (e.g., RRCEestablishment); and / or an RRC connection setup message (e.g., RRCSetup). Of the one or more BWPs, at least one BWP may be configured as the first active BWP (e.g., BWP 1), and one BWP may be configured as the default BWP (e.g., BWP 0). At step 2204, radio device 2220 may receive (e.g., detect) a command (e.g., RRC message, MAC CE, or DCI message) to activate the cell in the nth time slot. Wireless device 2220 may not receive (e.g., detect) a command to activate a cell (e.g., PCell). Wireless device 2220 may activate PCell at step 2212, for example, after wireless device 2220 receives / detects an RRC message including configuration parameters of PCell. Wireless device 2220 may begin monitoring PDCCH transmissions on BWP 1 based on (e.g., after or in response to) activating PCell at step 2212.

[0250] Wireless device 2220 may, at step 2214, start (or restart) a BWP inactivity timer (e.g., bwp-InactivityTimer) in the m-th time slot based on receiving a DCI message 2206 indicating DL assignment on BWP 1 (e.g., after or in response to this). For example, if the BWP inactivity timer expires in the s-th time slot at step 2208, wireless device 2220 may switch back to the default BWP (e.g., BWP 0) as the active BWP at step 2216. For example, if the secondary cell deactivation timer (e.g., sCellDeactivationTimer) expires at step 2210 (e.g., if the cell is SCell), then at step 2210, wireless device 2220 may deactivate the cell and / or stop the BWP inactivity timer. For example, based on the cell being PCell, wireless device 2220 may not deactivate the cell and may not apply or use the secondary cell deactivation timer (e.g., sCellDeactivationTimer) on PCell.

[0251] A radio device (e.g., the MAC entity of the radio device) can apply or use various operations on the active BWP of an active serving cell configured with a BWP. These operations can include at least one of the following: transmitting (e.g., transporting) on ​​the UL-SCH; transmitting (e.g., transporting) on ​​the RACH; monitoring PDCCH transport; transmitting (e.g., transporting) the PUCCH; receiving the DL-SCH; and / or (re)initializing any suspended configured uplink permission of type 1 configured according to the stored configuration (if any).

[0252] A radio device (e.g., the MAC entity of the radio device) may, for example, not perform certain operations on an inactive BWP configured with a BWP in an active serving cell (e.g., each active serving cell). These operations may include at least one of the following: transmitting (e.g., transporting) on ​​the UL-SCH; transmitting (e.g., transporting) on ​​the RACH; monitoring PDCCH transport; transmitting (e.g., transporting) the PUCCH; transmitting (e.g., transporting) the SRS; or receiving the DL-SCH. A radio device (e.g., the MAC entity of the radio device) may, for example, clear any configured downlink assignments and configured uplink permissions of type 2 configured on an inactive BWP configured with a BWP in an active serving cell (e.g., each active serving cell), and / or suspend any configured uplink permissions of type 1 configured.

[0253] For example, if a radio device (e.g., the MAC entity of the radio device) receives / detects a PDCCH transmission for BWP handover and the random access procedure associated with the serving cell is not in progress, the radio device can perform a BWP handover of the serving cell to the BWP indicated by the PDCCH transmission. For example, if the bandwidth portion indicator field is configured in DCI format 1_1, the bandwidth portion indicator field value can indicate an active DL BWP from the configured DL BWP set for DL ​​reception. For example, if the bandwidth portion indicator field is configured in DCI format 0_1, the bandwidth portion indicator field value can indicate an active UL BWP from the configured UL BWP set for UL transmission.

[0254] The wireless device can be provided by higher-layer parameters, such as a default DLBWP (e.g., Default-DL-BWP) in the configured DL BWP of the primary cell. For example, if the wireless device is not provided with a default DL BWP by a higher-layer parameter (e.g., Default-DL-BWP), the default DL BWP can be the initial active DL BWP. The wireless device can have higher-layer parameters, such as the value of a timer of the primary cell (e.g., bwp-InactivityTimer). For example, if the wireless device may not detect DCI format 1_1 for paired spectrum operation during every 1-millisecond interval in frequency range 1 or every 0.5-millisecond interval in frequency range 2, or if the wireless device may not detect DCI format 1_1 or DCI format 0_1 ​​for unpaired spectrum operation during said interval, the wireless device can increment a timer (if it is running) in said interval.

[0255] For example, if a radio device is configured for a secondary cell having higher-layer parameters (e.g., Default-DL-BWP) indicating the default DL BWP in a configured DL BWP, and the radio device is configured with higher-layer parameters (e.g., bwp-InactivityTimer) indicating a timer value, the procedure for the radio device on the secondary cell can be substantially the same as the procedure on the primary cell using the timer value and the default DL BWP of the secondary cell. For example, if the radio device is configured with higher-layer parameters (e.g., Active-BWP-DL-SCell) associated with a first active DL BWP and higher-layer parameters (e.g., Active-BWP-UL-SCell) associated with a first active UL BWP on the secondary cell or carrier, the radio device can use the indicated DL BWP and the indicated UL BWP on the secondary cell as the first active DL BWP and the first active UL BWP on the secondary cell or carrier, respectively.

[0256] The set of PDCCH candidates for monitoring by wireless devices can be referred to as the PDCCH search space set. The search space set may include a CSS set or a USS set. The wireless device can monitor PDCCH transmission candidates in one or more of the following search space sets: Type 0-PDCCH CSS set configured by pdcch-ConfigSIB1 in the MIB, or searchSpaceSIB1 in PDCCH-ConfigCommon, or searchSpaceZero in PDCCH-ConfigCommon, for a DCI format with a CRC scrambled by SI-RNTI on the primary cell of the MCG; Type 0A-PDCCH CSS set configured by searchSpaceOtherSystemInformation in PDCCH-ConfigCommon, for a DCI format with a CRC scrambled by SI-RNTI on the primary cell of the MCG; Type 1-PDCCH CSS set configured by ra-SearchSpace in PDCCH-ConfigCommon, for a DCI format with a CRC scrambled by RA-RNTI, MsgB-RNTI, or TC-RNTI on the primary cell; and Type 2-PDCCH configured by pagingSearchSpace in PDCCH-ConfigCommon. A CSS set for DCI format with CRC scrambled by P-RNTI on the primary cell of the MCG; a Type3-PDCCH CSS set configured with SearchSpace in common PDCCH-Config for DCI format with CRC scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, CI-RNTI or PS-RNTI and C-RNTI, MCS-C-RNTI or one or more CS-RNTI for the primary cell; and a USS set configured with SearchSpace in UE-specific PDCCH-Config for DCI format with CRC scrambled by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, one or more CS-RNTI, SL-RNTI, SL-CS-RNTI or SL-L-CS-RNTI.

[0257] Wireless devices can transmit configuration parameters (e.g., about) based on one or more PDCCHs. Figure 27The timing of PDCCH transmission monitoring on the active DL BWP is determined by the aforementioned parameters, wherein the one or more PDCCH transmission configuration parameters include at least one of the following: PDCCH transmission monitoring periodicity within a time slot; PDCCH transmission monitoring offset; or PDCCH transmission monitoring mode. For the search space set (SSs), if... Then the wireless device can determine one or more PDCCH transmission monitoring opportunities when there is a number / quantity The number / quantity of frames In the time slot. If the value µ is configured, then It can be the number / quantity of time slots in a frame. It can be the time slot offset indicated in the PDCCH transmission configuration parameters. This can be the PDCCH transmission monitoring periodicity indicated in the PDCCH transmission configuration parameters. The wireless device can monitor the transmission from the time slot. The beginning The search space set of PDCCH transmission candidates for consecutive time slots, and can be used without monitoring the next one. Search space set of continuous time slots PDCCH transport candidates. At the CCE aggregation level. The USS can be aggregated by CCE level. The set of PDCCH transmission candidates is defined.

[0258] Regarding CORESET Related search space set The wireless device can determine the value corresponding to the carrier indicator field. The corresponding service cell's activity DL BWP time slot PDCCH transport candidates in the search space set Aggregation level The CCE index as For any CSS, For USS, , ,for , ,for , ,for , ,and ; ; It is in CORESET From 0 to Number / quantization of CCEs; if the radio device is configured with the carrier indicator field of the serving cell for monitoring PDCCH transmissions by CrossCarrierSchedulingConfig, then It is the carrier indicator field value; otherwise, it contains the value for any CSS. ; ,in This refers to the number / quantity of PDCCH transmission candidates, which the wireless device is configured to monitor. Search space set of service communities Aggregation level For any CSS, For USS, It is a search space set CCE aggregation level of Over-configuration The maximum value; and used for The RNTI value is C-RNTI.

[0259] A wireless device can monitor a set of PDCCH transmission candidates based on configuration parameters of a search space set that includes multiple search spaces. The wireless device can monitor one or more PDCCH transmission candidate sets in a CORESET to detect one or more DCI messages. A CORESET can be, for example, as per [reference to...] Figure 26 The configuration is described above. Monitoring may include decoding one or more PDCCH transmission candidates in the monitored DCI format. Monitoring may include decoding the DCI content of one or more PDCCH transmission candidates using possible (or configured) PDCCH transmission locations, possible (or configured) PDCCH transmission formats (e.g., the number of CCEs, the number of PDCCH transmission candidates in the common search space, and / or the number of PDCCH transmission candidates in the radio device-specific search space (e.g., the UE-specific search space)) and possible (or configured) DCI formats. Decoding may be referred to as blind decoding. Possible DCI formats may be based on Figure 23 Examples.

[0260] Figure 23Examples of various DCI formats are shown. Various DCI formats can be used, for example, by a base station to send (e.g., transmit) control information (e.g., to a radio device and / or to be used by the radio device) for PDCCH transmission monitoring. Different DCI formats may include different DCI fields and / or have different DCI payload sizes. Different DCI formats may have different signaling purposes. DCI format 0_0 can be used to schedule PUSCH transmissions in a cell. DCI format 0_1 ​​can be used to schedule one or more PUSCH transmissions in a cell or to indicate CG-DFI (Configured Downlink Feedback Information) for PUSCH transmissions that have been configured to be permitted. One or more DCI formats can be configured for the radio device to monitor for reception via the search space.

[0261] Figure 24A A sample MIB message is shown. Figure 24A Example configuration parameters for a cell's MIB are shown. The cell can be a PCell (or any other cell). The radio device can receive the MIB via the PBCH. The radio device can receive the MIB, for example, based on the receipt of the PSS and / or SSS. The configuration parameters of the MIB may include / indicate the SFN (e.g., indicated via the higher-layer parameter systemFrameNumber), subcarrier spacing indication (e.g., indicated via the higher-layer parameter subCarrierSpacingCommon), frequency domain offset between the SSB and the total resource block grid in the number of subcarriers (e.g., indicated via the higher-layer parameter ssb-SubcarrierOffset), parameters indicating whether the cell is prohibited (e.g., indicated via the higher-layer parameter cellBarred), DMRS position indication indicating the position of the DMRS (e.g., indicated via the higher-layer parameter dmrs-TypeA-Position), parameters including the CORESET of the common CORESET and the search space of the PDCCH (e.g., indicated via the higher-layer parameter pdcch-ConfigSIB1), the common search space, and necessary PDCCH parameters, etc. Each of the higher-layer parameters may be indicated via one or more bits. For example, 6 bits (or any other number of bits) can be used to indicate an SFN.

[0262] Configuration parameters (e.g., pdcch-ConfigSIB1) may include a first parameter (e.g., controlResourceSetZero) indicating the common CORESET of the cell's initial BWP. The common CORESET can be associated with an indicator / index (e.g., 0 or any other indicator). For example, the common CORESET could be CORESET 0. The first parameter can be an integer between 0 and 15 (or any other integer). Each integer (e.g., between 0 and 15, or any other integer) can indicate / identify the configuration of CORESET 0.

[0263] Figure 24B An example configuration of CORESET is shown. CORESET can be CORESET 0 (or any other CORESET). The wireless device can determine, for example, the SSB and CORESET 0 multiplexing mode, the number of RBs in CORESET 0, the number of symbols in CORESET 0, and the RB offset of CORESET 0 based on the value of a first parameter (e.g., controlResourceSetZero).

[0264] Higher-level parameters (e.g., pdcch-ConfigSIB1) may include a second parameter (e.g., searchSpaceZero). This second parameter can indicate the common search space for the cell's initial BWP. The common search space can be associated with an indicator / index (e.g., 0 or any other indicator). For example, the common search space could be search space 0. The second parameter can be an integer between 0 and 15 (or any other integer). Each integer (e.g., between 0 and 15, or any other integer) can identify the configuration of search space 0.

[0265] Figure 24C An example configuration of the search space is shown. The search space can be search space 0 (or any other search space). The wireless device can determine one or more parameters (e.g., O, M) for slot determination for PDCCH monitoring, the first symbol indicator / index for PDCCH monitoring, and / or the number of search spaces per slot, for example, based on the value of a second parameter (e.g., searchSpaceZero). For example, for operation without shared spectrum channel access, and for SS / PBCH blocks and CORESET multiplexing mode 1, the wireless device can monitor the PDCCH in two slots (e.g., in the Type 0-PDCCH CSS set). For those with an index... The SS / PBCH block allows wireless devices to transmit time slots. The index is determined as Time slot It can be in the condition that meets the requirements (For example, if) ) of SFN In the frame, or in the frame with Meet the conditions (For example, if) In the SFN frame, where the SCS is received based on the PDCCH in CORESET, .

[0266] The wireless device can monitor the PDCCH used for receiving DCI. The wireless device can monitor search space 0 for receiving DCI at CORESET 0. DCI can schedule SIB1. For example, an SIB1 message can resemble... Figure 25 The aforementioned message. The wireless device can receive a DCI with a CRC scrambled using SI-RNTI scrambled specifically for receiving SIB1.

[0267] Figure 25 An example SIB is shown. A SIB may include one or more configuration parameters (e.g., RRC configuration parameters). A SIB (e.g., SIB1) may be sent / transmitted to one or more radio devices. For example, an SIB may be broadcast to multiple radio devices. A SIB may contain scheduling configurations for evaluating / determining whether radio device access to the cell is permitted, paging configuration information, and / or other system information. A SIB may include radio resource configuration information that may be common to multiple radio devices, and prohibition information used / applied to unified access control. A base station may send / transmit one or more SIB information messages to radio devices (or multiple radio devices). Figure 25 As shown, the parameters of one or more SIB information messages may include: one or more parameters related to cell selection associated with the serving cell (e.g., cellSelectionInfo), one or more configuration parameters of the serving cell (e.g., in the ServingCellConfigCommonSIB information element (IE)), and / or one or more other parameters. The ServingCellConfigCommonSIB IE may include at least one of the following: common downlink parameters of the serving cell (e.g., in the DownlinkConfigCommonSIB IE); common uplink parameters of the serving cell (e.g., in the UplinkConfigCommonSIB IE); and / or other parameters.

[0268] The DownlinkConfigCommonSIB IE can include parameters of the initial downlink BWP for the serving cell (e.g., SpCell) (e.g., indicated via the initialDownlinkBWP IE). The parameters of the initial downlink BWP can be included in the BWP-DownlinkCommon IE (e.g., as shown in the image). Figure 26 (As shown in the diagram). The BWP-DownlinkCommon IE can be used to configure common parameters for the downlink BWP of the serving cell. The base station can configure parameters (e.g., locationAndBandwidth) such that the initial downlink BWP can include the entire CORESET of the serving cell in the frequency domain (e.g., CORESET 0). The radio device can use / apply the locationAndBandwidth parameter based on the received parameters. The radio device can use / apply the locationAndBandwidth parameter to determine the frequency position of the signal relative to the frequency, as indicated by locationAndBandwidth. The radio device may, for example, maintain CORESET 0 until, after receiving an RRC setup message (e.g., RRCSetup), an RRC recovery message (e.g., RRCResume), and / or an RRC reconstruction message (e.g., RRCReestablishment).

[0269] The DownlinkConfigCommonSIB IE can include parameters for paging channel configuration. These parameters may include a paging cycle value (T, e.g., indicated by the defaultPagingCycle IE), a parameter indicating the total number / count of paging frames (PFs) in a paging DRX cycle (N) (e.g., indicated by the nAndPagingFrameOffset IE) and the paging frame offset (e.g., indicated by the PF_offset parameter), a total number / count of paging opportunities (POs) per PF (N), and a first PDCCH monitoring opportunity indication parameter (e.g., firstPDCCH-MonitoringOcasionOfPO IE) indicating the first PDCCH monitoring opportunity for paging per PO of a PF. The wireless device can monitor the PDCCH used to receive paging messages, for example, based on parameters configured in the PCCH.

[0270] The parameter (e.g., first-PDCCH-MonitoringOccasionOfPO) can be signaled in SIB1 to page in the initial DL BWP. The parameter first-PDCCH-MonitoringOccasionOfPO can also be signaled in the corresponding BWP configuration, for example, to page in a DL BWP other than the initial DL BWP.

[0271] Figure 26 Example RRC configuration parameters are shown. Configuration parameters can be RRC configuration parameters for the serving cell's downlink BWP. Configuration parameters can be indicated via the higher-layer parameter BWP-DownlinkCommon IE. The base station can send / transmit one or more configuration parameters for the serving cell's downlink BWP (e.g., the initial downlink BWP) to radio devices (or multiple radio devices). One or more configuration parameters for the downlink BWP can include: one or more general BWP parameters for the downlink BWP, one or more cell-specific parameters for the downlink BWP's PDCCH (e.g., in pdcch-ConfigCommon IE), one or more cell-specific parameters for the BWP's PDSCH (e.g., in pdsch-ConfigCommon IE), and / or one or more other parameters. pdcch-ConfigCommon IE can include parameters of CORESET 0 (e.g., indicated via the parameter controlResourceSetZero), which can be used in any common or radio device-specific search space. The value of controlResourceSetZero can be interpreted in the same way as the corresponding bit in the MIB parameter pdcch-ConfigSIB1. The pdcch-ConfigCommon IE can include parameters for additional common control resource sets (e.g., in commonControlResourceSet), which can be configured and used for any common or radio device-specific search space. For example, if the network configures a commonControlResourceSet, the network can use the ControlResourceSetId parameter (except 0) for this ControlResourceSet. The network can configure a commonControlResourceSet in SIB1 such that SIB1 is included within the bandwidth of CORESET 0. The pdcch-ConfigCommon IE can include parameters for additional public search space lists (e.g., in commonSearchSpaceList). Search space parameters can be based on... Figure 27Example implementation. The pdcch-ConfigCommon IE can indicate the search space for paging (e.g., via the pagingSearchSpace parameter), the search space for random access procedures (e.g., via the ra-SearchSpace parameter), the search space for SIB1 messages (e.g., via the searchSpaceSIB1 parameter), the common search space 0 (e.g., via the searchSpaceZero parameter), and / or one or more other search spaces from the list of search spaces.

[0272] CORESET can be associated with a CORESET indicator / index (e.g., via the parameter ControlResourceSetId). CORESET can be based on... Figure 14A and / or Figure 14BImplemented according to the example described. CORESET index 0 may identify a common CORESET configured in the MIB and in ServingCellConfigCommon (e.g., indicated via controlResourceSetZero). CORESET index 0 may not be used in ControlResourceSetIE. CORESET indexes with other values ​​may identify CORESETs configured by dedicated signaling or in SIB1. controlResourceSetId may be unique in the BWP of the serving cell. CORESET may be associated with coresetPoolIndex, which is the index of the CORESET pool indicating the CORESET. CORESET may be associated with a duration parameter (e.g., duration) indicating the continuous duration of the CORESET (e.g., based on the number / count of symbols). Configuration parameters for CORESET may include at least one of the following: frequency resource indication (e.g., frequencyDomainResources), CCE-REG mapping type indicator (e.g., cce-REG-MappingType), multiple TCI states and / or indicators indicating the presence of TCI in DCI, etc. Frequency resource indicators (e.g., including the number of bits, such as 45 bits or any other number of bits) can indicate frequency domain resources. Each bit of the frequency resource indicator can correspond to a group of RBs (e.g., 6 RBs or any other number of RBs), where the grouping starts from the first RB group in the BWP of the cell (e.g., SpCell, SCell). For example, the first (e.g., leftmost, most significant) bit can correspond to the first RB group in the BWP, and the other bits sequentially correspond to other RB groups. A bit set to 1 can indicate that the RB group corresponding to that bit is included in the frequency domain resources of the CORESET. Bits corresponding to a group of RBs that are not fully included in the BWP configured with the CORESET can be set to zero.

[0273] Figure 27An example configuration of the search space is shown. The search space configuration can be within the SearchSpace IE. One or more search space configuration parameters can include at least one of the following: search space ID (e.g., searchSpaceId); CORESET indicator (ID) (e.g., controlResourceSetId); monitoring slot periodicity and offset parameters (e.g., monitoringSlotPeriodicityAndOffset); search space duration value (e.g., duration); monitoring symbol indication (e.g., monitoringSymbolsWithinSlot); the number / count of candidates at the aggregation level (e.g., nrofCandidates); and / or the search space type indicating a common search space type or a radio device-specific search space type (e.g., searchSpaceType). The monitoring slot periodicity and offset parameters can indicate the slot used for PDCCH monitoring (e.g., within a radio frame) and the slot offset (e.g., related to the start of a radio frame). The monitoring symbol indication can indicate one or more symbols of a slot where a radio device can monitor the PDCCH on the search space. The control resource set ID can indicate / identify the CORESET on which the search space can reside.

[0274] A radio device in an RRC idle state (e.g., RRC_IDLE) or an RRC inactive state (e.g., RRC_INACTIVE) can periodically monitor the Points of Interest (POs) for receiving one or more paging messages from the radio device. While in an RRC idle or inactive state and before monitoring a PO, the radio device can wake up at a time prior to each PO to prepare and / or activate (e.g., turn on) all components in preparation for data reception (e.g., warm-up phase). The interval between wake-up and PO can be set sufficiently to accommodate all processing requirements. After warm-up, the radio device can perform timing acquisition and coarse synchronization from the SSB, frequency and time tracking, time and frequency offset compensation, and / or local oscillator calibration. After warm-up, the radio device can monitor the PDCCH for paging DCI via one or more PDCCH monitoring opportunities. The radio device can monitor the PDCCH, for example, based on configuration parameters of the PCCH configuration (e.g., as configured in SIB1). The configuration parameters of the PCCH configuration can be as follows regarding... Figure 25 As stated above.

[0275] A base station may (e.g., periodically) send / transmit one or more SSBs to a radio device or multiple radio devices. A radio device (in an RRC idle state, an RRC inactive state, or an RRC connected state) may use one or more SSBs to synchronize time and frequency with the base station's cell. SSBs including PSS, SSS, PBCH, and / or PBCH DM-RS (e.g., regarding...) may be sent / transmitted. Figure 11A The SSB can occupy a number of OFDM symbols (e.g., 4 or any other number). The base station can transmit one or more SSBs within an SSB burst (e.g., to enable beam sweeping of PSS / SSS and PBCH). An SSB burst can include a set of SSBs, where each SSB may be transmitted via a corresponding different beam. SSBs within an SSB burst can be transmitted using time-division multiplexing. An SSB burst can occur within a time window (e.g., a 5 ms window or any other duration) and can be located in the first or second half of a radio frame (e.g., with a duration of 10 ms or any other duration). An SSB burst can be equivalently referred to as a transmission window (e.g., 5 ms or any other duration) for transmitting a set of SSBs.

[0276] The base station can indicate the transmission periodicity of the SSB via RRC messages (e.g., SIB1 messages). For example, transmission periodicity can be indicated using messages such as SIB1 messages (e.g., ...). Figure 25 The parameter `ssb-PeriodicityServingCell` in `ServingCellConfigCommonSIB` (as shown in the image) indicates the periodicity. Candidate values ​​for the periodicity can be in the range {5ms, 10ms, 20ms, 40ms, 80ms, 160ms}. The periodicity can have any other value. The maximum number / scale of candidate SSBs within an SSB burst (L...) max This can depend on the cell's carrier frequency / band. For example, if f c <=3GHz, then L max =4. If 3GHz <f c <=6GHz, then L max =8. If f c >=6GHz, then L max =64, etc., where f c It can be the cell's carrier frequency. The starting OFDM symbol indicator / index of a candidate SSB (e.g., occupying 4 OFDM symbols) within an SSB burst (e.g., included in a 5 ms time window) can depend on the cell's SCS and carrier frequency band.

[0277] Figure 28 An example of an SSB configuration is shown. Figure 28 An example table for determining the starting OFDM symbol index of a candidate SSB is shown. The OFDM starting symbol can be determined based on the SCS and carrier frequency. For example, for a cell configured with 15 kHz SCS and carrier frequency fc < 3 GHz (e.g., L max = 4), the starting OFDM symbol index of the SSB in the SSB burst can be 2, 8, 16, and 22. The OFDM symbols in a half-frame can be indexed, where the first symbol of the first slot is indexed as 0. For a cell configured with 15 kHz and carrier frequency 3 GHz < fc < 6 GHz (L max = 8), the starting OFDM symbol index of the SSB in the SSB burst can be 2, 8, 16, 22, 30, 36, 44, and 50. The starting OFDM symbol indices for other SCS and carrier frequencies can be determined similarly according to Figure 28 the table shown. For example, if the base station does not use beamforming to transmit the SSB, the base station can transmit only one SSB by using the first SSB starting position.

[0278] Figure 29 An example of the base station's SSB transmission is shown. The SCS of the cell can be 15 kHz, and the cell can be configured with a carrier frequency f c such that 3 GHz < fc <= 6 GHz. For example, based on the value of f c the maximum number of candidate SSBs in the SSB burst can be 8 (L max = 8). The starting symbol for SSB transmission can be determined according to Figure 28 the table shown. SSB#1 can start at symbol 2 (among the 70 symbols in the 5 ms half-frame), SSB#2 can start at symbol #8, SSB#3 can start at symbol #16, SSB#4 can start at symbol #22, SSB#5 can start at symbol #30, SSB#6 can start at symbol #36, SSB#7 can start at symbol #44, and SSB#8 can start at symbol 50. The SSB burst can be transmitted in the first half (instead of the second half) of the radio frame (with a 10 ms duration).

[0279] The SSB burst (and each SSB of the SSB burst) can be transmitted periodically. The default periodicity of the SSB burst can be 20 ms (e.g., as Figure 29As shown in the diagram, or any other duration). The default transmission periodicity can be, for example, a periodicity prior to the time before the radio device can receive the SIB1 message for initial access to the cell. For example, a base station with a 20 ms transmission periodicity of SSB (or SSB burst) may send / transmit the SSB burst within the first 5 ms of each 20 ms period. The base station may not send / transmit the SSB burst within the remaining 15 ms of each 20 ms period.

[0280] The base station can send / transmit an RRC message (e.g., an SIB1 message) indicating cell-specific configuration parameters for SSB transmission. Cell-specific configuration parameters may include the value of the transmission periodicity of the SSB burst (e.g., the parameter ssb-PeriodicityServingCell) and the position (e.g., presence) of an SSB among multiple candidate SSBs in the SSB burst. The multiple candidate SSBs (e.g., the start symbol of the candidate SSB) can be determined, as per [the relevant information]. Figure 28 The cell-specific configuration parameters may include location indicators of SSBs within an SSB burst (e.g., the parameter ssb-PositionsInBurst). Location indicators may include a first bitmap (e.g., groupPresence) and a second bitmap (e.g., inOneGroup) indicating the location / presence of SSBs within the SSB burst.

[0281] Figure 30 An example of DRX configuration for a radio device is shown. The base station can send (e.g., transmit) an RRC message including one or more DRX parameters for a DRX cycle. The one or more parameters may include a first parameter and / or a second parameter. The first parameter may indicate a first time / window value for the DRX activity state of the DRX cycle (e.g., DRX on duration). The second parameter may indicate a second time for the DRX sleep state of the DRX cycle (e.g., DRX off duration). The one or more parameters may further include the duration of the DRX cycle. For a DRX activity state, the radio device can monitor the PDCCH to detect one or more DCIs on the serving cell. For a DRX sleep state, the radio device can stop monitoring the PDCCH on the serving cell. For example, if multiple cells are active, the radio device can monitor all PDCCHs on (or for multiple cells) of multiple cells for a DRX activity state. During the DRX off duration, the radio device can stop monitoring all PDCCHs on (or for multiple cells) of multiple cells. The radio device can repeat DRX operations based on the one or more DRX parameters.

[0282] DRX can be beneficial to base stations. For example, without DRX configured, radio devices can frequently (e.g., based on configuration) transmit periodic CSI and / or SRS. With DRX, radio devices can refrain from transmitting periodic CSI and / or SRS during DRX off periods. Base stations can then allocate these resources to other radio devices to improve resource utilization.

[0283] A MAC entity may be configured with DRX functionality via RRC. The DRX functionality controls the downlink control channel (e.g., PDCCH) of the radio device to monitor the activity of multiple RNTIs of the MAC entity. These multiple RNTIs may include at least one of the following: C-RNTI; CS-RNTI; INT-RNTI; SP-CSI-RNTI; SFI-RNTI; TPC-PUCCH-RNTI; TPC-PUSCH-RNTI; semi-persistent scheduling C-RNTI; eIMTA-RNTI; SL-RNTI; SL-V-RNTI; CC-RNTI; or SRS-TPC-RNTI. The MAC entity may monitor the PDCCH discontinuously, for example, based on RRC_CONNECTED (e.g., if DRX is configured); otherwise, the MAC entity may monitor the PDCCH continuously.

[0284] RRC can control DRX operation by configuring multiple timers. These timers may include: a DRX on-duration timer (e.g., drx-onDurationTimer); a DRX inactivity timer (e.g., drx-InactivityTimer); a downlink DRX HARQ round-trip time (RTT) timer (e.g., drx-HARQ-RTT-TimerDL); an uplink DRX HARQ RTT timer (e.g., drx-HARQ-RTT-TimerUL); a downlink retransmission timer (e.g., drx-RetransmissionTimerDL); an uplink retransmission timer (e.g., drx-RetransmissionTimerUL); one or more parameters for a short DRX configuration (e.g., drx-ShortCycle and / or drx-ShortCycleTimer); and one or more parameters for a long DRX configuration (e.g., drx-LongCycle). The time granularity of the DRX timers can be a PDCCH subframe (e.g., indicated as psf in the DRX configuration) and / or milliseconds.

[0285] Based on the DRX cycle configuration, the active time of a DRX operation can include the time during which at least one timer is running. At least one timer can include drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, and / or mac-ContentionResolutionTimer. For the active time of a DRX operation, the wireless device can monitor the PDCCH using RNTIs affected by the DRX operation. RNTIs can include C-RNTI, CI-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI, and / or AI-RNTI.

[0286] A timer (e.g., drx-Inactivity-Timer) can specify the duration for which the wireless device can be active, for example, after successfully decoding a PDCCH indicating a new transmission (UL, DL, or SL). This timer can be restarted upon receiving a PDCCH for a new transmission (UL, DL, or SL). The wireless device can transition to DRX mode (e.g., using a short DRX cycle or a long DRX cycle) based on the expiration of this timer. For example, if the wireless device enters DRX mode, the cycle (e.g., drx-ShortCycle) can be the first type of DRX cycle that needs to be followed (e.g., if configured). An IE (e.g., DRX-Config IE) can indicate the length of the short cycle. A timer (e.g., drx-ShortCycleTimer) can be represented as a multiple of a cycle (e.g., shortDRX-Cycle). A timer can indicate, for example, the number of initial DRX cycles following a short DRX cycle before entering a long DRX cycle. A timer (e.g., drx-onDurationTimer) can specify the duration at which a DRX cycle begins (e.g., DRX is enabled). A timer (e.g., drx-onDurationTimer) can indicate the duration, for example, before entering sleep mode (DRX is disabled). A timer (e.g., drx-HARQ-RTT-TimerDL) can specify the minimum duration from the time a new transmission is received, for example, before the wireless device can anticipate a retransmission of the same packet. The timer can be fixed and may not be configured by RRC. For example, if the wireless device anticipates a retransmission from the eNodeB, a timer (e.g., drx-RetransmissionTimerDL) can indicate the maximum duration for which the wireless device can monitor the PDCCH.

[0287] The active time can include the time during which a scheduling request is sent on the PUCCH and is pending, for example, configured based on a DRX cycle (e.g., after or in response to this). Based on a DRX cycle configuration (e.g., after or in response to this), the active time can include the time during which uplink permission for pending HARQ retransmissions can occur and data exists in the corresponding HARQ buffer used to synchronize the HARQ process. For example, after successfully receiving a random access response with a preamble not selected by the MAC entity, the active time can include the time during which the PDCCH can indicate that a new transmission addressing the MAC entity's C-RNTI has not yet been received, for example, based on a DRX cycle configuration.

[0288] Timers such as DL HARQ RTT timers (e.g., drx-HARQ-RTT-TimerDL) may expire in a subframe, and data from the corresponding HARQ process may fail to be decoded. A MAC entity can start a timer for the corresponding HARQ process (e.g., drx-RetransmissionTimerDL). UL HARQ RTT timers (e.g., drx-HARQ-RTT-TimerUL) may also expire in a subframe. A MAC entity can start a timer for the corresponding HARQ process (e.g., drx-RetransmissionTimerUL).

[0289] The wireless device can receive DRX command MAC CE and / or long DRX command MAC CE (e.g., based on this document regarding...). Figure 19 (Example described). The MAC entity of a wireless device can, for example, stop a timer (e.g., drx-onDurationTimer) and / or stop another timer (e.g., drx-InactivityTimer) based on receiving a DRX command MAC CE and / or a long DRX command MAC CE. For example, if an inactive timer (e.g., drx-InactivityTimer) expires and / or if a loop (e.g., a short DRX loop) is configured, the MAC entity can start or restart a timer (e.g., drx-ShortCycleTimer) and / or use a loop. For example, the MAC entity can use a loop (e.g., a long DRX loop).

[0290] Timers (e.g., drx-ShortCycleTimer) may expire in a subframe. MAC entities can use loops (e.g., long DRX loops). MAC control elements can receive long DRX commands. MAC entities can stop timers (e.g., drx-ShortCycleTimer) and can use long DRX loops.

[0291] The wireless device can, for example, start a timer (e.g., drx-onDurationTimer) after a value (e.g., drx-SlotOffset) from the start of a subframe, where drx-SlotOffset can be a value indicating, for example, the delay before starting drx-onDurationTimer (configured in the DRX configuration parameters), for example, if a short DRX cycle is used, and [(SFN*10)+subframe number] modulo (drx-ShortCycle) = (drxStartOffset) modulo (drx-ShortCycle). The wireless device can start a timer (e.g., drx-onDurationTimer) after a value (e.g., drx-SlotOffset) from the start of a subframe, where drx-SlotOffset can be a value indicating, for example, the delay before starting drx-onDurationTimer (configured in the DRX configuration parameters), for example, if a long DRX cycle is used and [(SFN*10)+subframe number] modulo (drx-LongCycle) = drxStartOffset.

[0292] Figure 31 An example of DRX configuration for a wireless device is shown. The base station may send (e.g., transmit) an RRC message that includes configuration parameters for DRX operation. The configuration parameters may include a first timer value for a DRX inactivity timer (e.g., drx-InactivityTimer), a second timer value for a HARQ RTT timer (e.g., drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL), and a third timer value for a HARQ retransmission timer (e.g., drx-RetransmissionTimerDL and / or drx-RetransmissionTimerUL).

[0293] Base stations can transmit signals to wireless devices (such as...) via PDCCH Figure 31The radio device transmits (e.g., transmits) a downlink-assigned DCI (e.g., a first DCI) that includes the TB. The radio device may, for example, start a drx-InactivityTimer based on the received DCI (e.g., after or in response to it). The radio device may monitor the PDCCH, for example, for a running timer (e.g., drx-InactivityTimer). The radio device may receive the TB based on the received DCI. The radio device may send (e.g., transmit) a NACK to the base station if decoding of the TB is unsuccessful. The radio device may, for example, start a HARQ RTT timer (e.g., drx-HARQ-RTT-TimerDL) in the first symbol after the completion of the NACK transmission (e.g., transmission). The radio device may stop the retransmission timer (e.g., drx-RetransmissionTimerDL) corresponding to the HARQ process of the TB. The radio device may stop monitoring the PDCCH of one or more RNTIs affected by DRX operation, for example, for a running HARQ RTT timer. The one or more RNTIs may include C-RNTI, CI-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI and / or AI-RNTI.

[0294] For example, if the HARQ RTT timer expires (such as...) Figure 31 As shown), the wireless device can monitor the PDCCH and start a HARQ retransmission timer (e.g., drx-RetransmissionTimerDL). For example, if the HARQ retransmission timer is running, the wireless device used to monitor the PDCCH can receive a second DCI that schedules retransmissions of the TB (e.g., Figure 31 (The second DCI in the process). For example, if the second DCI is not received (e.g., before the HARQ retransmission timer expires), the wireless device can stop monitoring the PDCCH.

[0295] Figure 32A An example power-saving operation for a wireless device is shown. Figure 32AExample power-saving operations can be based on wake-up indications. The base station can send / transmit one or more messages to the wireless device including parameters such as the wake-up duration (e.g., power-saving duration or power-saving channel (PSCH) timing). The wake-up duration can be a certain number of time slots (or symbols) preceding the DRX-on duration of the DRX cycle (e.g., starting from said time). The number of time slots (or symbols) can be the gap between the wake-up duration and the DRX-on duration. The DRX cycle can be based on, for example, regarding... Figure 30 The examples described are used for implementation. The number of time slots can be configured in one or more RRC messages, or can be predefined as a fixed value. Slots can be used for at least one of the following: synchronization with the base station, measuring reference signals, and / or retuning RF parameters. Slots can be determined based on the capabilities of the radio device and / or the base station. The wake-up duration parameter can be predefined without RRC configuration. The wake-up mechanism can be based on a wake-up indication (e.g., via PSCH). The wake-up duration parameter can include at least one of the following: PSCH channel format (e.g., parameter set, DCI format, PDCCH format), PSCH periodicity, control resource set, and / or PSCH search space. For example, if a wake-up duration parameter is configured, the radio device can monitor the PSCH to receive a wake-up signal during the wake-up duration. For example, if a PSCH timing parameter is configured, the radio device can monitor the PSCH to detect a wake-up indication during the PSCH timing / wake-up duration. A wireless device may wake up to monitor the PDCCH during the DRX active time (e.g., including the DRX on duration) of the next DRX cycle, based on / in response to receiving a wake-up signal / channel (or receiving a wake-up indication via the PSCH). The wireless device may also monitor the PDCCH during the DRX active time (e.g., when the drx-onDurationTimer is running), based on / in response to receiving a wake-up indication via the PSCH. If the wireless device does not receive a PDCCH transmission during the DRX active time, it may return to sleep. The wireless device may remain in sleep mode during the DRX off duration of a DRX cycle. For example, if the wireless device does not receive a wake-up signal / channel (or does not receive a wake-up indication via the PSCH) during the wake-up duration (or PSCH timing), it may skip monitoring the PDCCH during the DRX active time. Similarly, if the wireless device receives an indication to skip PDCCH monitoring during the wake-up duration (or PSCH timing), it may skip monitoring the PDCCH during the DRX active time.

[0296] Figure 32B An example power-saving operation for a wireless device is shown. Figure 32BPower-saving operation can be based on a sleep entry indication. The wireless device can, for example, return to sleep and skip monitoring the PDCCH during the DRX active period (e.g., during the next DRX on duration of a DRX cycle) based on / in response to receiving a sleep entry indication via the PSCH. For example, if the wireless device does not receive a sleep entry indication via the PSCH during the wake-up duration, the wireless device can monitor the PDCCH during the DRX active period according to the configuration parameters of DRX operation. Figure 32A and Figure 32B The power-saving mechanism can reduce the power consumption of PDCCH monitoring during DRX activity periods.

[0297] Power-saving operation can be based on a combination of... Figure 32A and Figure 32B The described operation. The base station can send / transmit a power-saving indication in the DCI via the PSCH, the power-saving indication indicating whether the wireless device can wake up during the next DRX on-duration or skip the next DRX on-duration. The wireless device can receive the DCI via the PSCH. The wireless device can, for example, indicate, based on / in response to the power-saving indication, that the wireless device can wake up during the next DRX on-duration and wake up during the next DRX on-duration. The wireless device can, in response to waking up, monitor the PDCCH during the next DRX on-duration. The wireless device can, for example, indicate, based on / in response to the power-saving indication, that the wireless device can skip the next DRX on-duration (or enter sleep during the next DRX on-duration) and enter sleep or skip the next DRX on-duration during the next DRX on-duration. The wireless device can, for example, indicate, based on / in response to the power-saving indication that the wireless device will enter sleep during the next DRX on-duration and skip monitoring the PDCCH during the next DRX on-duration. Regarding Figure 31 , Figure 32A and / or Figure 32B The various examples described can be extended and / or combined to further improve the power consumption of wireless devices and / or the signaling overhead of base stations.

[0298] A base station can be equipped with multiple Transmitter Points (TRPs) to improve spectral efficiency and / or transmission robustness. The base station can transmit DL signals / channels via multiple TRPs within a cell and / or via multiple TRPs between cells. A base station can be equipped with more than one TRP. The first TRP can be physically located at a different location than the second TRP. The first TRP can be connected to the second TRP via a backhaul link (e.g., a wired or wireless link), which can be an ideal backhaul link with zero or negligible transmission delay, or a non-ideal backhaul link. The first TRP can be implemented using antenna elements, an RF chain, and / or a baseband processor configured / managed independently of the second TRP.

[0299] Figure 33A and Figure 33B An example of multiple Transmitter Receiver Point (TRP) configurations is shown. Figure 33A An example of intra-cell TRP-based communication between a base station (equipped with multiple TRPs) and a wireless device (equipped with a single panel or multiple panels) is illustrated. Utilizing multiple TRPs for transmission and reception can improve system throughput and / or transmission robustness in high-frequency (e.g., above 6 GHz) wireless communications. Multiple TRPs can be associated with the same Physical Cell Identifier (PCI). Multiple TRPs sharing the cell's PDCCH / PDSCH / PUCCH / PUSCH resources can be referred to as intra-cell TRPs (or PCI-based TRPs).

[0300] A TRP among multiple TRPs of a base station can be indicated / identified by at least one of the following: TRP identifier (ID); virtual cell index; or reference signal index (or group index). In the example, within a cell, the TRP can be indexed by the coreset group (or pool) of the control resource set (coreset) group (e.g., as shown in the example). Figure 26 The CORESETPoolIndex shown is an identifier from which the DCI is transmitted from the base station on the coreset in the coreset group. The TRP ID of the TRP may include the TRP index indicated in the DCI. The TRP ID of the TRP may include the TCI state group index of the TCI state group. The TCI state group may include at least one TCI state in which the radio device uses its downlink TB to receive downlink TB or the base station uses its downlink TB to transmit downlink TB.

[0301] A base station can transmit one or more RRC messages to a radio device, the RRC messages including configuration parameters for multiple CORESETs on a cell (or a cell's BWP). One of the multiple CORESETs (e.g., each of the multiple CORESETs) can be identified by a CORESET index and can be associated with (or configured with) a CORESET pool (or group) index. One or more CORESETs with the same CORESET pool index can indicate that a DCI received on one or more CORESETs is transmitted from the same TRP among multiple TRPs of the base station. The radio device can determine the receive beam (or spatial domain filter) of the PDCCH / PDSCH based on the TCI indication (e.g., the DCI) and the CORESET pool index associated with the CORESET of the DCI.

[0302] For example, if a wireless device receives one or more RRC messages (e.g., PDCCH-Config IE) in a ControlResourceSet IE that include a first CORESET pool index (e.g., CORESETPoolIndex) value and a second CORESET pool index, the wireless device can receive multiple PDCCHs that schedule fully overlapping / partially overlapping / non-overlapping PDSCHs in both the time and frequency domains. The wireless device can only determine the reception of fully / partially overlapping PDSCHs in the time domain if the PDCCHs scheduling two PDSCHs are associated with different ControlResourceSets having different CORESETPoolIndex values.

[0303] For a ControlResourceSet that does not have a CORESETPoolIndex, the wireless device can assume (or determine) that the ControlResourceSet is assigned a CORESETPoolIndex of 0. For example, if the wireless device uses fully / partially / non-overlapping PDSCHs for scheduling in both the time and frequency domains, the scheduling information for receiving the PDSCH is indicated and carried only by the corresponding PDCCH. It can be expected that the wireless device uses the same active BWP and the same SCS for scheduling. When the wireless device uses fully / partially overlapping PDSCHs for scheduling in both the time and frequency domains, the wireless device can use a maximum of two codewords for scheduling simultaneously.

[0304] For example, if a PDCCH that schedules two PDSCHs is associated with different ControlResourceSets having different CORESETPoolIndex values, the radio device may be permitted to perform the following operations: for any two HARQ procedure IDs in a given scheduled cell, if the radio device is scheduled to begin receiving a first PDSCH starting with symbol j via a PDCCH associated with a value of CORESETpoolIndex ending with symbol i, the radio device may be scheduled to receive a PDSCH that begins earlier than the end of the first PDSCH using a PDCCH associated with a different value of CORESETpoolIndex ending later than symbol i; in a given scheduled cell, the radio device may receive the first PDSCH in slot i, where the corresponding HARQ-ACK is assigned to be transmitted in slot j; and a second PDSCH associated with a value of CORESETpoolIndex different from the value of the first PDSCH, which begins earlier than the first PDSCH, where its corresponding HARQ-ACK is assigned to be transmitted in a slot preceding slot j.

[0305] For example, if a radio device configured by the higher-layer parameter PDCCH-Config contains two different values ​​for CORESETPoolIndex in ControlResourceSet, in both cases, when tci-PresentInDCI is set to 'enabled' and tci-PresentInDCI is not configured in RRC connection mode, for example, if the offset between the reception of DL DCI and the corresponding PDSCH is less than the threshold timeDurationForQCL, the radio device can assume that the DM-RS port of the PDSCH associated with the value of CORESETPoolIndex of the serving cell is co-located with one or more QCL parameters relative to one or more RS quasi-co-located indicators for the PDCCH quasi-co-location indication of the CORESET associated with the monitored search space with the lowest CORESET-ID in the CORESET, which is configured in the latest time slot with the same CORESETPoolIndex value as the PDCCH that schedules the PDSCH, in which the radio device monitors one or more CORESETs associated with the same CORESETPoolIndex value as the PDCCH of the PDSCH in the active BWP of the serving cell. For example, if the offset between the received DL DCI and the corresponding PDSCH is less than the threshold timeDurationForQCL, and at least one configured TCI state of the serving cell whose PDSCH is scheduled contains 'QCL-TypeD', and at least one TCI code point indicates two TCI states, then the radio device may assume that the DM-RS port of the serving cell's PDSCH is quasi-co-located with one or more RS quasi-co-located relative to one or more QCL parameters associated with the TCI state corresponding to the lowest code point containing two different TCI states in the TCI code point.

[0306] Figure 33BAn example of communication between a base station (equipped with multiple TRPs) and a wireless device (equipped with a single panel or multiple panels) based on an inter-cell TRP (or inter-PCI TRP) is illustrated. In this case, the multiple TRPs may be associated with different PCIs. The multiple TRPs may be associated with (or belong to) different physical cells (cell 1 with PCI 1 and cell 2 with PCI 2), which can be referred to as an inter-cell TRP (or inter-PCI TRP). The cell may be the serving cell or a non-serving (neighboring) cell of the wireless device. The base station may configure cell 2 with PCI 2 as part of cell 1 with PCI 1 (e.g., a second TRP with a second PCI different from the first TRP's first PCI). In this case, for example, if the inter-cell TRP of the wireless device is operated, the wireless device can receive a first SSB from cell 1 with PCI 1 and a second SSB from cell 2 with PCI 2. The first SSB and the second SSB may have different configuration parameters, wherein configuration parameters, such as those described herein, can be implemented. Figure 28 , Figure 29 and / or Figure 30 As described above, by using inter-cell TRP, a radio device can receive PDCCH / PDSCH and / or transmit PUCCH / PUSCH in different TCI states on cell 1 with PCI 1 and cell 2 with PCI 2 (e.g., one associated with one of the first SSBs, the other associated with one of the second SSBs, etc.).

[0307] A serving cell can be a cell (e.g., PCell, SCell, PSCell, etc.) on which a radio device receives SSB / CSI-RS / PDCCH / PDSCH and / or transmits PUCCH / PUSCH / SRS, etc. A serving cell can be identified by a serving cell index (e.g., ServCellIndex or SCellIndex configured in an RRC message). For a radio device in RRC_CONNECTED and without a CA / DC configured, there may be only one serving cell, including the primary cell. For a radio device in RRC_CONNECTED and with a CA / DC configured, the term "serving cell" can be used to refer to a set of cells including the primary cell and all secondary cells. For a radio device with a CA configured, a cell that provides additional radio resources above the primary cell can be called a secondary cell. A non-serving (or neighboring) cell can be a cell on which a radio device does not receive MIB / SIB / PDCCH / PDSCH and / or transmit PUCCH / PUSCH / SRS, etc. A non-serving cell can have a different PCI than the serving cell. Non-serving cells may not be identified (or associated with) by a serving cell index (e.g., ServCellIndex or SCellIndex). For example, if the serving cell's TCI state is associated with the non-serving cell's SSB (e.g., in the TCI state IE of TS 38.331), the radio device may rely on the non-serving cell's SSB for Tx / Rx beam (or spatial domain filter) determination (for the serving cell's PDCCH / PDSCH / PUCCH / PUSCH / CSI-RS / SRS, etc.). The base station may not transmit RRC messages configuring the resources of the non-serving cell's PDCCH / PDSCH / PUCCH / PUSCH / SRS.

[0308] For a given radio device, cell 1 can be the serving cell and can be associated with a first TRP (TRP 1). Cell 2 can be a non-serving (or neighboring) cell and can be associated with a second TRP. The base station can transmit one or more RRC messages to the radio device, including configuration parameters for cell 1. The configuration parameters for cell 1 can indicate multiple additional PCI configurations (e.g., SSB-MTC-AdditionalPCI IE) for multiple (non-serving or neighboring) cells of cell 1, each additional PCI configuration corresponding to a (non-serving or neighboring) cell with a PCI value different from that of the serving cell, and includes: an additional PCI index (AdditionalPCIIndex) identifying the additional PCI configuration, the PCI of the non-serving cell, an SSB periodicity indication, a location indication of (candidate) SSBs in an SSB burst, an SSB transmission power indication, etc. The configuration parameters for cell 1 can also indicate multiple TCI states. For example, if the SSB is transmitted via cell 1 (or in another serving cell), the TCI states among multiple TCI states (e.g., each TCI state) can be associated with one or more TCI parameters including a TCI state identifier identifying the TCI state, one or more QCL information parameters including an SSB index identifying the SSB, and a QCL type indicator indicating the QCL type among multiple QCL types. For example, if the SSB with a TCI state is transmitted via a non-serving (neighboring) cell, the TCI state can also be associated with an Additional PCI index (AdditionalPCIIndex) indicating the (non-serving or neighboring) cell configured in the SSB-MTC-AdditionalPCI IE. Similar to multiple TRPs within a cell, a radio device can receive downlink signals and / or transmit uplink signals based on the TCI state (activation / indication) associated with the TRP. The difference between multiple TRPs within a cell and multiple TRPs between cells can be that, in the latter case, the reference RS for the serving cell's TCI state can come from (non-serving or neighboring) cells (or be transmitted via said cells). The SSB can be based on the provisions of this document regarding Figure 28 , Figure 29 and / or Figure 30 The example described is used for implementation.

[0309] Cell 1 can be the serving cell of a wireless device. Cell 2 can be a (non-serving or neighboring) cell associated with Cell 1 of the wireless device. Cell 2 can be the serving cell of a second wireless device. Cell 1 can be a (non-serving or neighboring) cell of the second wireless device. Different wireless devices can have different serving cells and non-serving / neighboring cells.

[0310] The base station can use two TRPs to transmit to the radio device via cell 1. The base station can (via DCI / MAC CE) indicate a first TCI state associated with an SSB / CSI-RS transmitted via cell 1 (or another serving cell) for a first transmission to the radio device (via cell 1's PDCCH / PDSCH / PUSCH / PUCCH / SRS resources). The base station can (via the same DCI / MAC CE or another DCI / MAC CE) indicate a second TCI state associated with a second SSB transmitted via cell 2 (which is a non-serving / neighboring cell indicated by the AdditionalPCIIndex in the TCI configuration parameters) for a second transmission to the radio device (via cell 1's PDCCH / PDSCH / PUSCH / PUCCH / SRS resources). The second SSB transmitted via cell 2 can be different from the first SSB transmitted via cell 1. Using two TCI states from two TRPs (one from the serving cell and the other from a non-serving / neighboring cell) can avoid time-consuming handover (HO) between cell 1 and cell 2, and improve coverage if the radio device is moving at the edge of cell 1 and cell 2.

[0311] The wireless device can provide two TCI states, each TCI state corresponding to one of a plurality of TRPs (e.g., regarding...). Figure 33A and Figure 33B (As described). When a TCI state is used for a specific channel (e.g., PDSCH / PDCCH / PUCCH / PUSCH), the TCI state can be referred to as a channel-specific TCI state, where different channels can be associated with different channel-specific TCI states. When a TCI state is used for multiple channels (e.g., PDSCH / PDCCH / PUCCH / PUSCH), the TCI state can be referred to as a unified TCI state, where different channels can be associated with the same unified TCI state. The base station can transmit an RRC message indicating whether the TCI state is a unified TCI state of the radio device.

[0312] For example, if the wireless device is located near the center of the cell, has more data to deliver, and / or requires high reliability (e.g., for URLLC services), such as regarding... Figure 33A and Figure 33BAs described, the base station can perform data / signaling transmissions based on multiple intra-cell TRPs (e.g., which may be referred to as intra-cell M-TRPs or intra-PCI M-TRPs) of the radio device. For example, when the radio device is at the edge of a cell and within the coverage area (moving or located) of another cell (which may or may not be the serving cell of the radio device), the base station can perform data / signaling transmissions based on multiple inter-cell TRPs of the radio device (e.g., which may be referred to as inter-cell M-TRPs or inter-PCI M-TRPs).

[0313] In at least some technologies, due to the limited battery capacity of wireless devices, base stations can, for example, be based on BWP management, SCell sleep mechanisms, and wake / sleep indications associated with DRX (e.g., based on the above regarding...). Figure 32A and / or Figure 32B The described example embodiments, SSSG switching and / or PDCCH skipping on the active BWP, enable power-saving operation of the wireless device.

[0314] For example, if a wireless device is instructed to perform power-saving operations, from the base station's perspective, the base station may not be able to save energy (e.g., if the base station needs to periodically send / transmit some always-on downlink signals (e.g., SSB, MIB, SIB1, SIB2, periodic CSI-RS, etc.) during a certain period of time, even if no active wireless device wants to send / transmit to and / or receive from the base station during that period). For example, if the base station transitions a cell to a dormant state by switching the cell's active BWP to a dormant BWP, the base station may need to periodically send / transmit some always-on downlink signals (e.g., SSB, MIB, SIB1, SIB2, periodic CSI-RS, etc.).

[0315] For example, if a base station needs to reduce the periodicity of always-on downlink signal transmission, the base station can send / transmit a longer-period RRC message (e.g., SIB1) indicating always-on downlink signal transmission. The base station can send / transmit RRC reconfiguration messages to radio devices in the source cell (e.g., each radio device in the source cell) to indicate handover to neighboring cells, for example, before determining power outages (e.g., both the RF module and the baseband unit (BBU)) for energy saving. Handover (HO) procedures can be implemented (e.g., as described herein). Figure 34 (As described).

[0316] A cell operating in Network Energy Saving (NES) mode can be called a Network Energy Saving (NES) cell. Base stations can transmit (e.g., use) less power, less bandwidth, fewer antenna ports / TRPs, and fewer PDSCH / PDCCHs via NES cells. A non-NES cell is a cell that does not operate in NES mode. Base stations can transmit (e.g., use) at full power, full bandwidth, and with more channels via non-NES cells.

[0317] Figure 34 An example of a Layer 3-based handover procedure is shown. Figure 34 An example of performing a HO procedure from a source base station (e.g., gNB) to a target base station for a wireless device is shown.

[0318] For network-controlled mobility in RRC_CONNECTED, an RRC connection reconfiguration message (e.g., RRCReconfiguration) can be used to change the PCell, which contains `reconfigurationWithSync` (in the NR specification) or `mobilityControlInfo` in the LTE specification (handover). One or more SCells can be changed using an RRC connection reconfiguration message with or without `reconfigurationWithSync` or `mobilityControlInfo`. The network can trigger HO procedures, for example, based on radio conditions, load, QoS, UE category, etc. RRC connection reconfiguration messages, such as those described herein, can be implemented. Figure 35 and Figure 36 As described.

[0319] The network can configure the radio device to perform measurement reporting (potentially including the configuration of measurement gaps (MG)). The measurement report is a Layer 3 report, distinct from a Layer 1 CSI report. The radio device (e.g., radio device 3402) can transmit one or more measurement reports 3410 to the source base station (e.g., source gNB / base station 3404) (and / or source PCell). The network can, for example, blindly initiate a HO (House of Interest) without having received a measurement report from the radio device. The source base station (e.g., gNB) can, for example, prepare one or more target cells before sending an HO message to the radio device. The source base station (e.g., gNB) can select the target PCell.

[0320] A source base station (e.g., gNB) may provide a list of the best cells (e.g., in descending order of RSRP values) with available measurement information on each frequency to a target base station (e.g., target base station 3406), for example, based on one or more measurement reports from the radio device. The source base station may also include available measurement information for the cells provided in the list. The target base station may determine which cells are configured for use after the HO (Ho) request, which may include cells other than those indicated by the source base station. The source base station may transmit an HO request 3412 to the target base station. The target base station may respond with an HO message 3414 (e.g., a handover request ACK). In the HO message, the target base station may indicate the access layer configuration to be used in the target cell of the radio device.

[0321] The source base station (e.g., gNB) can transparently (e.g., by not changing values / content) forward HO messages / information received from the target base station to the radio device. Within the HO message, RACH resource configuration can be set to allow the radio device to access the cell in the target base station. Where appropriate, the source base station can initiate data forwarding for a subset of dedicated radio bearers.

[0322] The wireless device can, for example, start the HO timer with an initial timer value after receiving the HO message (e.g., T304). The HO timer can be configured in the HO message. Based on the HO message, the wireless device can apply the RRC parameters of the target PCell and / or the cell group (MCG / SCG) associated with the target PCell of the target base station, and perform downlink synchronization with the target base station. This downlink synchronization with the target base station involves (e.g., searching for suitable / detectable SSBs from the candidate SSBs configured on the target base station, such as regarding...) Figure 28 and / or Figure 29 Following or in response to this, the wireless device may initiate random access (e.g., contention-free or contention-based, such as regarding...). Figure 13A , Figure 13B and / or Figure 13C The procedure described attempts to access a target base station (e.g., a gNB) at an available RACH time, based on RACH resources, where the available RACH time can be configured in the RACH resource configuration (e.g., as described in this document). Figure 36 (As described). For example, if a dedicated preamble is assigned for random access in a target base station (e.g., gNB), the RAN can ensure that the preamble is available from the first RACH opportunity that the radio device can use.

[0323] After executing an HO to the target PCell, the wireless device can activate the uplink BWP configured with firstActiveUplinkBWP-Id and / or the downlink BWP configured with firstActiveDownlinkBWP-Id on the target PCell. The wireless device can perform RACH procedures, for example, based on the RRC parameters of the target PCell and / or complete downlink synchronization with the target PCell (e.g., regarding...). Figure 13A , Figure 13B and / or Figure 13C To perform UL synchronization, as described above, the uplink BWP of the target PCell can be used. Performing UL synchronization may include the active uplink BWP (e.g., a BWP configured as firstActiveUplinkBWP-id, such as regarding...) via the target PCell's uplink BWP. Figure 35 (As described) transmits a preamble in the active downlink BWP (e.g., a BWP configured as firstActiveDownlinkBWP-id, such as regarding Figure 35 The device monitors the PDCCH (as described) to receive the RAR, which includes the TA (Transmission Acquisition Target) for PUSCH / PUCCH transmission via the target PCell, receives the RAR, and / or obtains the TA. The wireless device may obtain the TA for PUSCH / PUCCH transmission via the target PCell, for example, based on the completion of UL synchronization (e.g., afterward). For example, by adjusting the uplink transmission timing using the TA, the wireless device can transmit PUSCH / PUCCH via the target PCell. Adjusting the uplink transmission timing may include advancing or delaying the transmission by an amount indicated by the value of the TA, for example, to ensure that the uplink signal received at the target PCell is aligned (in the time domain) with the uplink signal transmitted from other wireless devices.

[0324] The wireless device can release the RRC configuration parameters of the source PCell and the MCG / SCG associated with the source PCell. A HO triggered by receiving an RRC reconfiguration message 3416 (e.g., RRCReconfiguration) that includes a HO command / message (e.g., via reconfigurationWithSync (in the NR specification) or mobilityControlInfo (handover) in the LTE specification) is referred to as a normal HO, unconditional HO, and related to the provisions of this document. Figure 37 The conditions HO (CHO) described are different.

[0325] The wireless device can transmit (e.g., transmit) preamble 3418 to a target base station (e.g., gNB) via RACH resources. RACH resources can be selected from multiple RACH resources based on the target base station's SSB / CSI-RS measurements (e.g., configured in a RACH-ConfigDedicated IE, such as regarding...). Figure 35 and Figure 36 (As described). The wireless device can select the (optimal) SSB / CSI-RS of the configured SSB / CSI-RS of the target base station (e.g., gNB). The wireless device can select an SSB / CSI-RS from the configured SSB / CSI-RS of the target base station (e.g., gNB) whose RSRP value is greater than the RSRP threshold configured for the RA procedure. The wireless device then determines the RACH timing (e.g., time domain resources, etc.) associated with the selected SSB / CSI-RS and determines the preamble associated with the selected SSB / CSI-RS.

[0326] The target base station (e.g., gNB) can receive a preamble transmitted from the radio device. The target base station can transmit a Random Access Response (RAR) 3420 to the radio device, wherein the RAR includes the preamble transmitted by the radio device. The RAR may also include a TAC to be used for uplink transmission via the target PCell. The radio device can complete the random access procedure, for example, based on (e.g., in response to) receiving the RAR including the preamble. The radio device can stop the HO timer (T304), for example, based on (e.g., in response to) completing the random access procedure. The radio device can transmit an RRC reconfiguration completion message 3422 to the target base station after or before completing the random access procedure. After completing the random access procedure with the target base station, the radio device can apply the first part of the CQI report configuration, SR configuration, and SRS configuration, which does not require the radio device to know the target base station's System Frame Number (SFN). For example, based on the completion of a random access procedure on the target PCell (e.g., after or in response to this), the wireless device may apply the measurement and radio resource configuration required by the target base station's SFN after acquiring the target base station's SFN. The wireless device may know a second part of the target base station's SFN (e.g., MG, periodic CQI report, SR configuration, SRS configuration).

[0327] For network energy conservation purposes, the base station can, for example, instruct each radio device in the source cell to perform a 4-step or 2-step RACH-based (contention-free) HO procedure to neighboring cells. After the radio device completes the HO procedure to the neighboring cell, the base station can shut down (RF components and BBU, etc.) to conserve energy.

[0328] Figure 35 An example of a Radio Resource Control (RRC) message for Layer 3-based handover is shown. Figure 35 An example of an RRC message for HO is shown. The base station may transmit and / or the radio device may receive an RRC reconfiguration message (e.g., RRCReconfiguration-IE) indicating an RRC connection modification. This message may convey information for measurement configuration, mobility control, radio resource configuration (including RB, MAC master configuration, and physical channel configuration), and AS security configuration. The RRC reconfiguration message may include the configuration of the master cell group. The master cell group may be associated with an SpCell (SpCellConfig). When SpCellConfig includes a reconfiguration with synchronization (reconfigurationWithSync), the radio device determines that SpCell is the target PCell for HO. The reconfiguration with synchronization (reconfigurationWithSync) may include the target PCell's cell common parameters (spCellConfigCommon), the RNTI (newUE-Identity) identifying the radio device in the target PCell, the T304 value, dedicated RACH resources (rach-ConfigDedicated), etc. In the example, dedicated RACH resources may include one or more RACH timings, one or more SSBs, one or more CSI-RS, one or more RA preamble indices, etc.

[0329] Figure 36 An example of an RRC message for layer 3-based handover is shown. Figure 35 An example of an RRC message for configuring RACH resources for a HO procedure is shown. The reconfigurationWithSync IE includes a dedicated RACH resource indicated by rach-ConfigDedicatedIE (e.g., regarding...). Figure 35 (As described).

[0330] Such as rach-ConfigDedicated IE (e.g.) Figure 36The IE (as shown) may include contention-free RA resources indicated by the CFRA IE. The CFRA IE may include multiple times indicated by the rach-ConfigGeneric IE, ssb-perRACH-Occasion IE, and multiple resources associated with SSBs (indicated by the ssb IE) and / or CSI-RS (indicated by the csirs IE). IEs such as the ssb-perRACH-Occasion IE may indicate the number of SSBs for each RACH time. IEs such as the rach-ConfigGeneric IE may indicate the configuration of the CFRA time. The wireless device may omit the preambleReceivedTargetPower, preambleTransMax, powerRampingStep, and ra-ResponseWindow signals transmitted in this field and use the corresponding values ​​provided in RACH-ConfigCommon.

[0331] For example, if multiple resources of a CFRA configured in the reconfigurationWithSync IE are associated with an SSB, then the resources (resource IEs) include the SSB IEs (e.g., Figure 36 (As shown). The SSB IE can include a CFRA SSB resource list (ssb-ResourceList) and an indication of the PRACH timing mask index (ra-ssb-OccasionMaskIndex). One or more of the CFRA SSB resource lists (e.g., each one in the CFRA SSB resource list) can include an SSB index, an RA preamble index, etc. The ra-ssb-OccasionMaskIndex can indicate the PRACH mask index used for RA resource selection. The mask can be valid for all SSB resources signaled in the ssb-ResourceList.

[0332] For example, if multiple resources of CFRA configured in the reconfigurationWithSync IE are associated with CSI-RS, then the resources (resource IEs) can include csirs IEs. csirs IEs can include the CFRA CSI-RS resource list (csirs-ResourceList) and the RSRP threshold (rsrp-ThresholdCSI-RS). One or more of the CFRA CSI-RS resource lists (e.g., each one in the CFRA CSI-RS resource list) can include a CSI-RS index, an RA occasion list (ra-OccasionList), an RA preamble index, etc.

[0333] For example, if a wireless device is moving within a network with multiple small cells (e.g., a cell coverage area of ​​several hundred meters), performing a home homing (HO) triggered by receiving an RRC reconfiguration message including a reconfigurationWithSync IE can introduce HO latency (e.g., too late HO). An improved HO mechanism based on measurement event triggering is proposed to reduce HO latency, such as the one discussed in this paper. Figure 37 As described.

[0334] Figure 37 An example of a layer 3-based conditional handover procedure is shown. Figure 37 An example of a Conditional Handover (CHO) procedure is shown. In the example, the network (e.g., a base station, a source gNB) can configure a radio device to perform measurement reports (possibly including MG configuration) on multiple neighboring cells (e.g., cells from candidate target base station 1, candidate target base station 2, etc.). The measurement report can be a Layer 3 report, which differs from a Layer 1 CSI report. The radio device can transmit one or more measurement reports 3705 to the source base station (e.g., the gNB) (or the source PCell).

[0335] The source base station (e.g., gNB) may provide the target base station with a list of the best cells available for each frequency, for example, based on one or more measurement reports from the radio device, in descending order of RSRP. The source base station may also include available measurement information for the cells provided in the list. The target base station may determine which cells are configured for use after a CHO, which may include cells other than those indicated by the source base station. In the example, the source base station may transmit an HO 3710 request to the target base station. The target base station may respond with an HO message 3715. In the HO message, for example, the target base station may indicate the access stratum configuration (e.g., the RRC configuration of the target cell) to be used in the target cell of the radio device.

[0336] The source base station (e.g., gNB) can transparently (e.g., by not changing values / content) forward handover messages / information received from the target base station (e.g., included in the target base station's RRC reconfiguration message) to the radio device. The source base station can also do so by including a conditional reconfiguration message (e.g., conditionalReconfigurationIE in the RRC reconfiguration message, which will later be...). Figure 38 (as described in the text) to configure procedures different from normal HO procedures (e.g., regarding...) Figure 34 , Figure 35 and / or Figure 36The CHO procedure 3720 (described above) may include a list of candidate target PCells, each of which is associated with a dedicated RACH resource for the RA procedure when a CHO is performed on a candidate target PCell. CHO execution conditions (or RRC reconfiguration conditions) may also be configured for each of the candidate target PCells. CHO execution conditions may include a measurement event A3 in which a candidate target PCell becomes better than the current PCell (e.g., the PCell of the source gNB) by an offset; a measurement event A4 in which a candidate target PCell becomes better than an absolute threshold configured in the RRC reconfiguration message; a measurement event A5 in which the current PCell becomes worse than a first absolute threshold and the candidate target PCell becomes better than a second absolute threshold; and so on.

[0337] Based on the received RRC reconfiguration message including the parameters of the CHO procedure, such as Figure 37 The wireless device shown can evaluate the (RRC) reconfiguration conditions of a list of 3725 candidate target PCells and / or the current / source PCell. The wireless device can measure the RSRP / RSRQ of the SSB / CSI-RS for each candidate target PCell in the candidate target PCell list. (Different from regarding...) Figure 34 In the described normal HO procedure, the wireless device can perform the HO to the target PCell without responding to receiving an RRC reconfiguration message that includes parameters of the CHO procedure. For example, if the (RRC) reconfiguration condition 3730 of the target PCell is met (or satisfied), the wireless device can perform the HO for the target PCell against the CHO. The wireless device can maintain the evaluation of the reconfiguration condition 3725 of the candidate target PCell list, for example, until the HO timer expires or an RRC reconfiguration indicating the termination of the CHO procedure is received.

[0338] like Figure 37 The wireless device shown can, for example, perform a CHO procedure on a first candidate target PCell (e.g., in response to) based on the achievement or satisfaction of a reconfiguration condition of the first candidate target PCell (e.g., PCell 1). When multiple candidate target PCells have satisfied or achieved reconfiguration conditions, the wireless device can select one of the multiple candidate target PCells 3735 through its implementation.

[0339] Executing the CHO procedure against the first candidate target PCell can be related to, for example, regarding Figure 34The HO procedure is performed in the same or similar manner as described. By executing the CHO procedure, the wireless device can release the RRC configuration parameters of the source PCell and the MCG associated with the source PCell, apply the RRC configuration parameters of PCell 1, reset the MAC, perform cell group configuration on the received MCG included in the RRC reconfiguration message of PCell 1, and / or perform RA procedure 3740 on PCell 1, etc.

[0340] The MCG of the RRC reconfiguration message for PCell 1 can be associated with the SpCell (SpCellConfig) on ​​the target base station 1. For example, if sPCellConfig includes a reconfiguration with synchronization (reconfigurationWithSync), the radio device can determine that SpCell is the target PCell (PCell 1) for HO. The reconfiguration with synchronization (reconfigurationWithSync) can include the target PCell's cell common parameters (spCellConfigCommon), the RNTI (newUE-Identity) identifying the radio device in the target PCell, the value of T304, dedicated RACH resources (rach-ConfigDedicated), etc. Dedicated RACH resources can include one or more RACH timings, one or more SSBs, one or more CSI-RS, one or more RA preamble indices, etc. The radio device can perform cell group configuration, such as regarding the received primary cell group included in the RRC reconfiguration message 3745 (e.g., RRCReconfigurationComplete) for PCell 1 on the target base station 1. Figure 34 As described.

[0341] Figure 38 An example of an RRC message used for a layer-based conditional handover procedure is shown. Figure 38 An example of a CHO RRC message is shown. The base station can transmit and / or the wireless device can receive an RRC reconfiguration message (e.g., RRCReconfiguration-V1610-IE) indicating an RRC connection modification. The RRC reconfiguration message can be included in the (parent) RRC reconfiguration message (e.g., RRCReconfiguration-IE), such as regarding... Figure 35 As described, the (parent) RRC reconfiguration message may include (L3 beam / cell) measurement configuration (e.g., measConfig IE).

[0342] Figure 38The RRC reconfiguration message (e.g., RRCReconfiguration-V1610-IE) may include a conditional reconfiguration IE. The conditional reconfiguration IE may include a conditional reconfiguration list (condReconfigToAddModList). Each conditional reconfiguration corresponds to a specific candidate target cell (PCell) in the candidate target cell list. For each conditional reconfiguration in the conditional reconfiguration list, the base station may indicate one or more measurement events (condExecutionCond) to trigger a CHO on the candidate target PCell, and an RRC reconfiguration message (condRRCReconfig) received by the source base station (e.g., gNB) from the target base station via the X2 / Xn interface for the candidate target cell (PCell). The RRC reconfiguration message for the candidate target cell can be implemented, such as regarding... Figure 35 and / or Figure 36 As described. The RRC reconfiguration message may include the configuration of the target base station's master cell group. The master cell group may be associated with an SpCell (SpCellConfig). For example, if sPCellConfig includes a reconfiguration with synchronization (reconfigurationWithSync), then the SpCell may be the target PCell used to perform the CHO. The reconfiguration with synchronization (reconfigurationWithSync) may include the target PCell's cell common parameters (spCellConfigCommon), the RNTI (newUE-Identity) identifying the radio device in the target PCell, the T304 value, dedicated RACH resources (rach-ConfigDedicated), etc. Dedicated RACH resources may include one or more RACH timings, one or more SSBs, one or more CSI-RSs, one or more RA preamble indices, etc.

[0343] Figure 38The measurement event (condExecutionCond) used to trigger a CHO on a candidate target PCell can be an execution condition that needs to be met (at the radio device) to trigger the execution of a conditional reconfiguration for the CHO. The measurement event indicator can point to a measurement ID (MeasId) that identifies a measurement configuration configured by the source base station among multiple measurement configurations (e.g., included in measConfigIE). The measurement configuration can be associated with measurement events (or conditional events) for multiple measurements. Conditional events can include conditional events A3, A4, and / or A5, etc. Conditional event A3 is when the candidate target PCell becomes better than the current PCell (e.g., the PCell of the source base station / gNB) by an offset. Conditional event A4 is when the candidate target PCell becomes better than the absolute threshold configured in the RRC reconfiguration message. Conditional event A5 is when the current PCell becomes worse than a first absolute threshold and the candidate target PCell becomes better than a second absolute threshold, etc.

[0344] The decision by the wireless device to perform CHO based on the evaluation of reconfiguration conditions on multiple candidate target cells (long-term and / or layer 3 beam / cell measurements against one or more configured thresholds) may lead to load imbalance on the cells, and / or CHO failure if the target cell changes its configuration during the CHO condition evaluation (e.g., for network power saving). This article is about Figure 39 An improved handover triggered by Layer 1 or Layer 2 signaling is described. Layer 1 or Layer 2 triggered handover may be referred to as a Layer 1 or Layer 2 triggered Mobility Transaction (LTM) procedure. Layer 1 signaling may include DCI transmitted via PDCCH. Layer 2 signaling may include MAC CE scheduled by DCI. For HO / CHO, Layer 1 or Layer 2 signaling differs from Layer 3 signaling, which includes RRC reconfiguration messages.

[0345] Figure 39 Examples of handover based on layer 1 or layer 2 are shown. For example, Figure 39 An example of a HO procedure triggered by layer 1 or layer 2 is shown. For example, Figure 39 An example of Layer 1 or Layer-triggered mobility is shown. The network (e.g., source base station / gNB 3904) can configure a radio device (e.g., radio device 3902) to perform measurement reports (possibly including MG configuration) on multiple neighboring cells (e.g., cells from candidate target base station 13906, candidate target base station 2 3908, etc.). The measurement report can be a Layer 3 report, different from a Layer 1 CSI report. The radio device can transmit one or more measurement reports 3920 to the source base station (or source PCell, in...) Figure 39 (The middle part is the community 0).

[0346] The source base station (e.g., gNB) may provide the target base station with a list of the best cells on each frequency for which measurement information is available, for example, based on one or more measurement reports from the radio device, in descending order of RSRP. The source base station may also include available measurement information for the cells provided in the list. The target base station may determine which cells are configured for use after the CHO (as the target PCell, and / or one or more SCells), and these cells may include cells other than those indicated by the source base station. The source base station may transmit HO Request 3922 to the target base station. The target base station may respond with an HO message (e.g., HO Request ACK 3924). In the HO message, the target base station may indicate the access stratum configuration (e.g., the RRC configuration of the target cell) to be used in the target cell of the radio device.

[0347] The source base station can transparently (e.g., by not changing the values / content) forward HO messages / information received from the target base station (e.g., contained in the target base station's RRC reconfiguration message, the target base station's cell group configuration IE, and / or the target PCell / SCell's SpCell configuration IE of the target base station / gNB) to the radio device.

[0348] The source base station can configure a different procedure than the normal HO procedure (e.g., regarding...) by including a Layer 1 or Layer 2 candidate PCell configuration message 3926 (e.g., a newly defined candidates-L1L2-Config IE) in its RRC reconfiguration message (e.g., regarding...). Figure 34 , Figure 35 and / or Figure 36 (as described) and / or CHO procedures (e.g., for example, regarding Figure 37 and / or Figure 38 The described procedure is a Layer 1 or Layer 2 signaling-based HO (PCell handover / change, mobility, etc.) procedure. The Layer 1 or Layer 2 candidate PCell configuration message 3926 may include a list of candidate target PCells. When a Layer 1 or Layer 2 signaling-based HO is triggered by Layer 1 or Layer 2 signaling and executed on candidate target PCells, each candidate target PCell is associated with a dedicated RACH resource for the RA procedure. The parameter configuration of the candidate target PCells can have multiple options.

[0349] As a first option in parameter configuration, for each candidate target PCell, the RRC reconfiguration message of the source base station (e.g., gNB) may include an encapsulated RRC reconfiguration message (e.g., RRCReconfiguration) received by the source base station from the candidate target base station via the X2 / Xn interface. The encapsulated RRC reconfiguration message of the candidate target base station (e.g., gNB) may reuse the same signaling structure as the source base station's RRC reconfiguration message, such as regarding... Figure 35 and / or Figure 36 As described.

[0350] As a second option for parameter configuration, for each candidate target PCell, the RRC reconfiguration message of the source base station (e.g., gNB) may include the (encapsulated) cell group configuration message (e.g., CellGroupConfig) received by the source base station from the candidate target base station (e.g., gNB) via the X2 / Xn interface. The (encapsulated) cell group configuration message of the candidate target base station (e.g., gNB) may reuse the same signaling structure (e.g., regarding the cell group configuration message of the source base station (e.g., gNB)). Figure 35 and / or Figure 36 (As described). Compared to the first option, the second option can reduce the signaling overhead of parameter configuration for candidate target PCells.

[0351] As a third option for parameter configuration, for each candidate target PCell, the RRC reconfiguration message of the source base station (e.g., gNB) may include an encapsulated SpCell configuration message (e.g., SpCellConfig) received by the source base station from the candidate target base station via the X2 / Xn interface. The encapsulated SpCell configuration message of the candidate target base station may reuse the same signaling structure as the source base station's SpCell configuration message, such as regarding... Figure 35 and / or Figure 36 As described. Compared to the second option, the third option can reduce the signaling overhead of parameter configuration for candidate target PCells.

[0352] For each candidate target PCell (e.g., each candidate target PCell), the source base station may indicate cell common and / or radio device specific parameters (e.g., SSB / CSI-RS, BWP, RACH resources, PDCCH / PDSCH / PUCCH / PUSCH resources, etc.). Based on the received RRC reconfiguration message including parameters from a HO procedure based on Layer 1 or Layer 2 signaling, the radio device may perform Layer 1 or Layer 2 measurement reports (CSI / beams) on the list of candidate target PCells and / or the current PCell. Layer 1 or Layer 2 measurement reports may include Layer 1 RSRP, Layer 1 RSRQ, PMI, RI, Layer 1 SINR, CQI, etc. Layer 1 or Layer 2 measurement reports 3928 may be transmitted to the source base station periodically as configured by the source base station (e.g., gNB). A Layer 1 or Layer 2 measurement report may be triggered when the CSI / beam measurement of a candidate target PCell is greater than a threshold or larger than the current PCell (by an offset).

[0353] Figure 39 The base station can perform an inter-cell beam management (ICBM) procedure before transmitting (e.g., a transmission) Layer 1 or Layer 2 signaling that triggers a HO procedure, including switching the PCell from the source base station (e.g., gNB) to the target base station. The ICBM procedure allows the base station and radio devices to use the resources (time / frequency / spatial) of the target base station (or its PCell / SCell) without performing the HO procedure on the target base station, thus reducing the frequency of HO procedure execution. The ICBM procedure can also allow the base station and radio devices to synchronize time / frequency / beam to the target PCell of the target base station before performing the HO, which can reduce HO latency. ICBM can be implemented, as described in this paper regarding... Figure 40 As described.

[0354] Figure 39 The source base station may, for example, send (e.g., transmit) a first DCI / MAC CE 3930 to the radio device based on an ICBM configuration procedure (e.g., in response to this), the first DCI / MAC CE configuring / indicating a first candidate target cell (e.g., cell 1) in the candidate target cells (PCell / SCell) as a neighboring or non-serving cell of the radio device other than the current PCell (e.g., cell 0). The base station may select the first candidate target cell from the candidate target cells based on a Layer 1 or Layer 2 measurement report from the radio device.

[0355] The first DCI / MAC CE (e.g., activating the TCI state) can indicate that, in addition to the reference RS associated with the second TCI state originating from the current PCell (cell 0), the reference RS associated with the first TCI state (e.g., SSB / CSI-RS) originates from the first candidate target cell (cell 1) (e.g., by associating the reference RS with an additional PCI of cell 1 that differs from the PCI of cell 0). The association between the reference signal and the TCI state can be based on the above regarding... Figure 31 Implemented using the example described in B. Activating the TCI state by the DCI and / or MAC CE using the RS of a neighboring (non-serving) cell as a reference RS allows the base station to use the beams of the neighboring cell to transmit downlink signals / channels or receive uplink signals / channels, and / or use the beams of the current cell for transmission / reception without performing HO to the neighboring cell for transmission / reception.

[0356] The wireless device may, for example, apply a first TCI state and a second TCI state to downlink reception and / or uplink transmission 3932 based on receiving a first DCI / MAC CE (e.g., in response to this). Applying the first TCI state and the second TCI state to downlink reception may include: receiving (from cell 1) PDCCH / PDSCH / CSI-RS using the same receive beam / filter as used for receiving reference signals transmitted from cell 1, based on the first TCI state (or associated therewith); and receiving (from cell 0) PDCCH / PDSCH / CSI-RS using the same receive beam / filter as used for receiving reference signals transmitted from cell 0, based on the second TCI state (or associated therewith). Applying the first TCI state and the second TCI state to uplink transmission may include: according to the first TCI state (or associated therewith), using the same transmission beam / filter as the transmission beam / filter used to receive the reference signal transmitted from cell 1 to transmit (via cell 1) PUCCH / PUSCH / SRS; and according to the second TCI state (or associated therewith), using the same transmission beam / filter as the transmission beam / filter used to receive the reference signal transmitted from cell 0 to transmit (via cell 0) PUCCH / PUSCH / SRS.

[0357] The base station can skip executing the ICBM procedure before transmitting Layer 1 or Layer 2 signaling that triggers the HO procedure. For example, when beamforming is not used in the target PCell, if there are no one or more good SSBs from the target PCell, if there are no available radio resources from the target PCell to accommodate the radio device, and / or when the radio device does not support ICBM and / or when the base station does not support ICBM, the base station can skip executing the ICBM procedure.

[0358] The source base station can determine to hand over the radio device from the source base station (cell 0) to the target base station (cell 1). The source base station can determine the handover based on load / service conditions, CSI / beam reports from the target base station (e.g., gNB), the location / trajectory of the radio device, network power-saving strategies (e.g., the source base station determines to shut down cell 0 and / or one or more SCells to save power), etc.

[0359] Figure 39 The source base station can send (e.g., transmit) a second DCI / MAC CE 3934 instructing the PCell to change from the current PCell (cell 0) to a new cell (e.g., cell 1). The new cell can be one of the neighboring (non-serving) cells used in the ICBM procedure (e.g., indicated by the first DCI / MAC CE). Figure 39 In the example, the new cell could be cell 1. For example, if ICBM procedures are supported and / or configured, the radio device may have already synchronized with the target base station on which beam should be used for transmission / reception via the target base station before executing the HO procedure indicated by the source base station, for example. This differs from layer 3 signaling-based (C)HO (such as...). Figure 34 and / or Figure 37 As shown), the wireless device needs to synchronize with the target base station after performing HO / CHO and then obtain an indication of the new beam to be used for the target base station.

[0360] When the ICBM procedure is not configured / supported / indicated / activated for a new cell, the new cell can be one of several neighboring (non-serving) cells included in the L1 beam / CSI report, such as having the best measurement report, having the closest distance to the wireless device, etc., the wireless device can, for example, based on receiving... Figure 39 The second DCI / MAC CE (e.g., in response to this) changes the PCell from cell 0 to cell 1. The radio device can apply the (stored / received) RRC parameters of the target PCell (cell 1) (included in RRCReconfiguration, CellGroupConfig, and / or SpCellConfig IE) to the current PCell.

[0361] If the wireless device has already synchronized with the target PCell based on the ICBM procedure, for example, if the ICBM is configured / supported / indicated / activated before receiving the second DCI / MAC CE, the wireless device can skip downlink (time / frequency / beam) synchronization (e.g., monitoring MIB / SSB / SIB and / or selecting SSB as the reference for downlink reception and / or uplink transmission). For example, when the target PCell is close to the source PCell, or the uplink TA is the same or similar for both the source and target PCells, or the dedicated RACH resource is not configured in the target PCell's RRC reconfiguration message, the wireless device can skip performing the RA procedure on the target PCell before transmitting to and / or receiving from the target PCell. The wireless device can perform downlink synchronization (SSB / PBCH / SIB monitoring), can perform uplink synchronization (RA procedure) 3936 for HO based on Layer 1 or Layer 2 signaling (e.g., when ICBM is not configured / indicated / supported / activated), and / or can send RRCReconfigurationComplete 3938 to the target base station 1, as such regarding Figure 34 , Figure 35 , Figure 36 , Figure 37 and / or Figure 38 As described, this is what is done for HO / CHO based on Layer 3 signaling.

[0362] Figure 40 An example of inter-cell beam management is shown. Figure 40 An example of an ICBM procedure is shown. A first radio device (radio device 1) may be within the coverage area of ​​cell 0 deployed under a first node (e.g., base station A or TRP A). Radio device 1 is not within the coverage area of ​​cell 1 deployed under a second node (e.g., base station B or TRP B). Cell 0 and cell 1 have different PCIs. Radio device 1 may use an RS (e.g., RS1) transmitted from cell 0 as a reference RS for its TCI state (which is determined by beam / spatial domain filters used for downlink reception and / or uplink transmission (Tx / Rx-based TCI state 0 associated with RS1)). Radio device 1 may not use an RS (e.g., RS2 and / or RS3) transmitted from cell 1 as a reference RS for its TCI state. A radio device 1 configured with a TCI state associated with an RS of a serving cell having a first PCI but not with an RS of another cell having a second PCI different from the first PCI may be referred to herein as a radio device (e.g., UE) without (configured / activated) ICBM.

[0363] Figure 40The second wireless device (wireless device 2) can be within the coverage area of ​​cell 0 deployed below the first node (e.g., base station A or TRPA). Wireless device 2 is also within the coverage area of ​​cell 1 deployed below the second node (e.g., base station B or TRP B). Cell 0 and cell 1 have different PCIs. Wireless device 2 can use an RS (e.g., RS2) transmitted from cell 0 as a reference RS for a first TCI state (which is used for beam / spatial domain filter determination for downlink reception and / or uplink transmission via cell 0 (Tx / Rx-based TCI state 1 associated with RS2)). Wireless device 2 can use an RS (e.g., RS3) transmitted from cell 1 as a reference RS for a second TCI state (which is used for beam / spatial domain filter determination for downlink reception and / or uplink transmission via cell 1 (Tx / Rx-based TCI state 2 associated with RS3)). A radio device 2 configured with a first TCI state associated with an RS serving a cell having a first PCI and a second TCI state associated with an RS having a second PCI different from the first PCI can be referred to herein as a radio device (e.g., UE) with (configured / activated) ICBM.

[0364] For example, if base station B or TRP B receives an uplink signal / channel with a second TCI state, it can forward the uplink signal / channel to base station A or TRPA for processing. Base stations such as base station A or TRP A can forward downlink signals / channels to base station B or TRP B for transmission to the radio device along with the second TCI state. Cell 1, having a second PCI different from the first PCI of cell 0, can be considered / configured as part of cell 0 of radio device 2 (e.g., a second TRP having a second PCI different from the first PCI of the first TRP), for example, regarding... Figure 33B As described above. If, for example, cell 1 is configured as part of cell 0, then cell 0 and cell 1 can belong to the same DU (or base station-DU (e.g., gNB0DU)). The base station-DU can be based, for example, on the above description regarding... Figure 1A and / or Figure 1B Implemented as described in the example. PDCCH / PDSCH / PUCCH / PUSCH resources can be shared between cell 1 and cell 0 in a manner transparent to radio device 2. The SSB / CSI-RS of cell 0 may not share the same resources as the SSB / CSI-RS of cell 1. The SSB / CSI-RS of cell 0 may have different configuration parameters (e.g., number of beams, periodicity, transmission power, etc.) than the SSB / CSI-RS of cell 1.

[0365] For example, when cell 1 is configured as a candidate target cell, such as regarding Figure 35 and / or Figure 38 As described, cell 1, having a second PCI different from the first PCI of cell 0, can be considered / configured as a separate cell different from cell 0 of radio device 2. If, for example, cell 1 is configured as a separate cell from cell 0, then cell 0 and cell 1 can belong to different DUs (or base station-DUs (e.g., gNB-DUs)) associated with the same CU (or base station-CU (e.g., gNB-CU)) or different CUs. The base station-DU and / or base station-CU can be, for example, based on information about Figure 1A and / or Figure 1B Implemented as described in the example. Cell resources (SSB / CSI-RS / PDCCH / PDSCH / PUCCH / PUSCH) may not be shared between Cell 1 and Cell 0. Cell 1 has cell resource configuration parameters that are different from (or independent of) the cell resource configuration parameters of Cell 0.

[0366] In at least some technologies, the base station can configure the RRC configuration parameters (SSB, RACH resources, MAC parameters, PHY cell common and / or UE specific parameters, such as...) of the target PCell for the radio device. Figure 35 , Figure 36 and / or Figure 38 As shown), this is used to perform a (C)HO from the source PCell to the target PCell. When performing a (C)HO on the target PCell, the radio device can use the received / stored RRC configuration parameters. The radio device can begin performing downlink synchronization on the target PCell (e.g., by time / frequency alignment, for example, by monitoring the SSB configured on the target PCell according to 3GPP TS 38.213 Section 4 - Synchronization Procedure). The radio device can begin performing uplink synchronization, for example, based on the completion of downlink synchronization (e.g., afterward), for example, by initiating a RACH resource initiation (CF)RA procedure based on the RACH resource initiation (CF)RA procedure configured on the target PCell. The radio device can receive a timing advance (TA) command in the RAR corresponding to the preamble transmitted by the radio device.

[0367] In at least some technologies, in order to send (e.g., transmit) a preamble for a CFRA procedure, multiple beams are used by a base station for SSB transmission (e.g., regarding...). Figure 28 and / or Figure 29 When described, the wireless device can, based on the RSRP value of the first SSB being greater than the RSRP threshold, access RACH resources (e.g., regarding...) on the target PCell. Figure 36The first SSB is selected from a plurality of candidate SSBs configured as described. The radio device can determine a preamble with a preamble index associated with the selected first SSB based on RACH resource configuration parameters. The radio device can, for example, determine the corresponding preamble index in the PRACH timing based on the selection of the first SSB (e.g., afterward) as specified by the RACH-ConfigDedicated IE (e.g., regarding...). Figure 36 The ra-ssb-OccasionMaskIndex configured in the description specifies the next available PRACH timing for the selected first SSB, as permitted by the constraints. The radio device can transmit a preamble to the target PCell via the determined PRACH timing. The radio device can monitor the target PCell's PDCCH to receive the RAR corresponding to the preamble. The radio device can receive the RAR including the preamble index and / or TA command. The radio device can complete the CFRA procedure. CFRA procedures, such as those concerning... Figure 13B As described. The wireless device may, for example, receive beam indications (or TCI status indications) from the target PCell for PDCCH / PDSCH / CSI-RS reception and / or PUCCH / PUSCH / SRS transmission for the target PCell based on the completion of a CFRA procedure (e.g., after which). The wireless device may apply the beam (or TCI status) to the PDCCH / PDSCH / CSI-RS reception and / or PUCCH / PUSCH / SRS transmission for the target PCell. In at least some techniques, the wireless device may, for example, perform downlink synchronization and uplink synchronization, and beam alignment / management via the target PCell based on receiving an HO command (e.g., an RRC reconfiguration with ReconfigurationWithSync IE) (e.g., after which). Performing downlink synchronization, uplink synchronization, and / or beam alignment can be time-consuming.

[0368] Configurations for reporting (e.g., CSI reporting) (e.g., Layer 1 CSI reporting) (e.g., RS configuration) can be configured within the serving cell configuration of a cell (e.g., each cell). These configurations can be configured in messages, such as in RRC messages (e.g., ServingCellConfig). Different serving cells can be configured differently (e.g., with different RS configurations). A similar principle can be used for other HOs and CHOs (e.g., Layer 3-based HOs and CHOs), allowing each candidate cell to be configured with different sett...

Claims

1. A method comprising: The wireless device receives a first message including a request associated with the capabilities of the wireless device; Send a second message indicating the capabilities of the wireless device, wherein the second message includes: The first parameter indicates whether the wireless device supports cell discontinuous transmission (DTX) configuration via Radio Resource Control (RRC) messaging; and The second parameter indicates whether the wireless device supports activating the cell DTX configuration via downlink control information (DCI); Receive an RRC message including the configuration parameters of the cell's DTX configuration; and Receive the activated DCI indicating the DTX configuration of the cell.

2. The method according to claim 1, comprising: The wireless device receives at least one third message, the at least one third message including: A third parameter of the first and second cells associated with a mobility (LTM) procedure triggered at layer 1 / 2, wherein the first cell is the serving primary cell (PCell) and the second cell is a candidate PCell; and The fourth parameter for cell DTX operation; The LTM procedure is triggered based on the receipt of the at least one third message; Receive a command instructing the activation of the cell's DTX operation associated with at least one of the following: The first cell; or The second community; and The LTM procedure is cancelled based on the activation of the cell DTX operation.

3. The method according to any one of claims 1 to 2, comprising: The channel state information (CSI) reporting procedure is triggered by the wireless device based on measurements of at least one reference signal from a first cell and at least one reference signal from a second cell, wherein the first cell is a source cell and the second cell is a candidate cell. as well as The CSI reporting procedure is canceled during the inactive period of the cell DTX cycle and based on the activation of the cell DTX cycle.

4. A method comprising: The base station sends a first message that includes a request related to the capabilities of the wireless device; Receive a second message indicating the capabilities of the wireless device, wherein the second message includes: The first parameter indicates whether the wireless device supports cell discontinuous transmission (DTX) configuration via radio resource control (RRC) messaging; as well as The second parameter indicates whether the wireless device supports activating the cell DTX configuration via downlink control information (DCI); Send an RRC message including the configuration parameters of the cell's DTX configuration; and Send the DCI indicating the activation of the cell's DTX configuration.

5. The method according to any one of claims 1 to 4, further comprising: Based on the activated DCI indicating the cell's DTX configuration, a Network Energy Saving (NES) operation is initiated.

6. The method according to any one of claims 1 to 5, wherein the second message further comprises: An indication of a second capability of the wireless device, wherein the second capability is associated with power-saving operation of the wireless device; as well as The third parameter indicates whether the wireless device supports a wireless device-specific discontinuous reception (DRX) configuration for multiple cells.

7. The method according to any one of claims 1 to 6, wherein: The RRC message further includes a radio device-specific discontinuous reception (DRX) configuration for the plurality of cells.

8. The method according to any one of claims 1 to 7, wherein: The configuration parameters of the cell DTX configuration include at least one parameter indicating that the cell DTX configuration is at least one of the following: Activated by DCI; or Activated by DCI.

9. The method according to any one of claims 1 to 8, wherein: The DCI that is activated is a group common DCI that addresses multiple wireless devices including the wireless device.

10. The method according to any one of claims 1 to 9, wherein: The RRC message further includes an index for the search space of the DCI associated with the activation of the cell's DTX configuration.

11. The method according to any one of claims 1 to 10, wherein the RRC message further includes a Radio Network Temporary Identifier (RNTI) for the DCI associated with the activation of the cell DTX configuration.

12. The method according to any one of claims 1 to 11, wherein the configuration parameters of the cell DTX configuration include at least one of the following: The length of the DTX activity period in the cell DTX cycle; The periodic value of the cell's DTX cycle; or The starting offset of the cell's DTX cycle.

13. A computing 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 computing device to perform the method according to any one of claims 1 to 12.

14. A system comprising: A wireless device configured to perform the method according to any one of claims 1 to 3 or 5 to 12; as well as A base station configured to perform the method according to any one of claims 4 to 12.

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