Early time alignment acquisition for fast cell switching

Abstract

A wireless device may communicate via one or more cells. A cell switch command may be used to indicate a cell switch to the wireless device. Early time alignment acquisition may be performed before the cell switch command is transmitted or received. A deactivated initial uplink bandwidth portion may be used to transmit a preamble. The cell switch command may be used to activate the (deactivated) initial uplink bandwidth portion of the candidate cell. After activation, the initial uplink bandwidth portion may be used for uplink signal transmission via the cell.

Description

[Technical Field]

[0001] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 418,403, filed October 21, 2022. The above-referenced application is incorporated herein by reference in its entirety. [Background technology]

[0002] A wireless device communicates via one or more cells, and when the wireless device is relocated from a source cell to a target cell, the wireless device switches from the source cell to the target cell as a primary cell (PCell). Summary of the Invention

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

[0004] A wireless device may communicate via one or more cells. A cell switch command may be used to indicate a cell switch to the wireless device. Early time alignment acquisition may be performed before the cell switch command is transmitted or received. For example, a preamble may be transmitted to the target cell to acquire early time alignment before the cell switch. An uplink bandwidth portion of the target cell may not be activated before receiving the cell switch command, and as a result, it may be unclear which uplink bandwidth portion should be used by the wireless device for preamble transmission. For preamble transmission, one or more radio resource control messages including configuration parameters (e.g., for a Layer 1 and / or Layer 2 Triggered Mobility (LTM) procedure) may be received by the wireless device via the source cell. A deactivated initial uplink bandwidth portion may be used to transmit the preamble. The cell switch command may be used to activate the (deactivated) initial uplink bandwidth portion of the candidate cell. After activation, the initial uplink bandwidth portion may be used for uplink signal transmission via the cell. The wireless device may transmit the preamble over the frequency resources of the target cell according to the frequency reference point indicated by the message.

[0005] These and other features and advantages are described in more detail below. [Brief explanation of the drawings]

[0006] Certain features are illustrated by way of example, and not by way of limitation, in the accompanying drawings in which like numerals refer to like elements and in which:

[0007] [Figure 1A] 1 illustrates an exemplary communication network. [Figure 1B] 1 illustrates an exemplary communication network. [Figure 2A] 1 illustrates an exemplary user plane. [Figure 2B] 1 illustrates an exemplary control plane configuration. [Figure 3] 1 shows an example of a protocol layer. [Figure 4A] 1 illustrates an exemplary downlink data flow for a user plane configuration. [Figure 4B] 1 illustrates an example format of a media access control (MAC) subheader of a MAC protocol data unit (PDU). [Figure 5A] 1 illustrates an exemplary mapping of downlink channels. [Figure 5B] 1 illustrates an exemplary mapping of uplink channels. [Figure 6] 1 illustrates exemplary radio resource control (RRC) states and RRC state transitions. [Figure 7] 1 shows an exemplary configuration of a frame. [Figure 8] 1 illustrates an example resource configuration for one or more carriers. [Figure 9] 1 illustrates an exemplary configuration of a bandwidth portion (BWP). [Figure 10A] 1 illustrates an exemplary carrier aggregation configuration based on component carriers. [Figure 10B] 1 shows an exemplary group of cells. [Figure 11A] 1 illustrates an exemplary mapping of one or more synchronization signal / physical broadcast channel (SS / PBCH) blocks. [Figure 11B] 1 illustrates an example mapping of one or more channel state information reference signals (CSI-RS). [Figure 12A] 1 shows an example of a downlink beam management procedure. [Figure 12B] An example of an uplink beam management procedure is shown. [Figure 13A] 1 illustrates an exemplary four-step random access procedure. [Figure 13B] 1 illustrates an exemplary two-step random access procedure. [Figure 13C] 1 illustrates an exemplary two-step random access procedure. [Figure 14A] 1 shows an example of a control resource set (CORESET) configuration. [Figure 14B] 1 shows an example of a mapping of control channel elements to resource element groups (CCE to REG). [Figure 15A] 1 illustrates an example of communication between a wireless device and a base station. [Figure 15B] 1 illustrates exemplary elements of a computing device that may be used to implement any of the various devices described herein. [Figure 16A] 1 illustrates an example of uplink and downlink signal transmission. [Figure 16B] 1 illustrates an example of uplink and downlink signal transmission. [Figure 16C] 1 illustrates an example of uplink and downlink signal transmission. [Figure 16D] 1 illustrates an example of uplink and downlink signal transmission. [Figure 17A] 1 shows an exemplary MAC subheader. [Figure 17B] 1 shows an exemplary MAC subheader. [Figure 17C] 1 shows an exemplary MAC subheader. [Figure 18A] 1 shows an exemplary MAC PDU. [Figure 18B] 1 shows an exemplary MAC PDU. [Figure 19] 10 shows exemplary logical channel identifier (LCID) values. [Figure 20] Exemplary LCID values ​​are shown. [Figure 21A] 1 illustrates an exemplary secondary cell (SCell) activation / deactivation MAC Control Element (CE). [Figure 21B] 1 illustrates an exemplary secondary cell (SCell) activation / deactivation MAC Control Element (CE). [Figure 22] Here is an example of BWP activation / deactivation: [Figure 23] 1 shows examples of various downlink control information (DCI) formats. [Figure 24A] 1 illustrates an exemplary Master Information Block (MIB) message. [Figure 24B] 1 illustrates an exemplary configuration of CORESET. [Figure 24C] An example of the search space configuration is shown below. [Figure 25] An example of a system information block (SIB) is shown below. [Figure 26] 1 illustrates exemplary RRC configuration parameters. [Figure 27] 1 illustrates an exemplary configuration of a search space. [Figure 28] 1 illustrates an exemplary pause management. [Figure 29] 1 illustrates an example of a DRX configuration for a wireless device. [Figure 30] 1 illustrates an example of a DRX configuration for a wireless device. [Figure 31A] 1 illustrates an example of a power saving operation of a wireless device. [Figure 31B] 1 illustrates an example of a power saving operation of a wireless device. [Figure 32A] 1 illustrates an example of search space set group (SSSG) switching for power saving in a wireless device. [Figure 32B] 1 illustrates an example of search space set group (SSSG) switching for power saving in a wireless device. [Figure 33] 1 illustrates an example of physical downlink control channel (PDCCH) skipping for power saving in a wireless device. [Figure 34] An example of a synchronization signal block (SSB) configuration is shown below. [Figure 35] An example of SSB transmission from a base station is shown below. [Figure 36] An example of SSB transmission from a base station is shown below. [Figure 37A] 1 illustrates an example of a multiple transmit and receive point (TRP) configuration. [Figure 37B] 1 illustrates an example of a multiple transmit and receive point (TRP) configuration. [Figure 38] 1 illustrates an example of a layer 3 based handover procedure. [Figure 39] 1 illustrates an example of a Radio Resource Control (RRC) message for a Layer 3 based handover. [Figure 40]1 shows an example of RRC messages for Layer 3 based handover. [Figure 41] 1 illustrates an example of a layer 3 based conditional handover procedure. [Figure 42] 10 shows example RRC messages for a layer-based conditional handover procedure. [Figure 43] An example of a layer 1 or layer 2 based handover is shown. [Figure 44] An example of inter-cell beam management is shown. [Figure 45] 10 shows an example of PCell switching for network energy saving. [Figure 46A] An example of a PCell switching timeline is shown. [Figure 46B] An example of a PCell switching timeline is shown. [Figure 47] An example of PCell switching / modification is shown below. [Figure 48A] 1 shows an example of early time alignment acquisition for fast cell switching. [Figure 48B] 1 illustrates an exemplary method for early time alignment acquisition for fast cell switching. [Figure 49A] 10 shows an example of a target PCell configuration for PCell switching. [Figure 49B] 10 shows an example of a target PCell configuration for PCell switching. [Figure 49C] 10 shows an example of a target PCell configuration for PCell switching. [Figure 49D] 10 shows an example of a target PCell configuration for PCell switching. [Figure 50] 1 illustrates an example timeline for early time alignment acquisition for fast cell switching. [Figure 51] 1 illustrates an example timeline for early time alignment acquisition for fast cell switching. [Figure 52A] 1 shows an example of early time alignment acquisition for fast cell switching. [Figure 52B]1 illustrates an exemplary method for early time alignment acquisition for fast cell switching. DETAILED DESCRIPTION OF THE INVENTION

[0008] 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 that the features shown and described may be practiced in other examples. The examples are provided for the operation of a wireless communication system that may be used in the technical field of multi-carrier communication systems.

[0009] FIG. 1A illustrates an exemplary communication network 100. The communication network 100 may include a mobile communication network. The communication network 100 may include, for example, a public land mobile network (PLMN) operated / managed / run by a network operator. The communication network 100 may include one or more of a core network (CN) 102, a radio access network (RAN) 104, and / or wireless devices 106. The communication network 100 may include, and / or devices within the communication network 100 may communicate with, one or more data networks (DNs) 108 (e.g., via the CN 102). The wireless devices 106 may communicate with one or more DNs 108, such as public DNs (e.g., the Internet), private DNs, and / or intra-operator DNs. The wireless devices 106 may communicate with one or more DNs 108 via the RAN 104 and / or the CN 102. The CN 102 may provide / configure the wireless devices 106 with one or more interfaces to one or more DNs 108. As part of its interface functions, the CN 102 may set up an end-to-end connection between the wireless device 106 and one or more DNs 108, authenticate the wireless device 106, provide / configure charging functionality, etc.

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

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

[0012] The RAN 104 may include one or more base stations (not shown). As used throughout, the term “base station” may include one or more of a base station, node, Node B (NB), Evolved Node B (eNB), Generation Node B (gNB), Next Generation Evolved Node B (ng-eNB), relay node (e.g., integrated access and backhaul (IAB) node, etc.), donor node (e.g., donor eNB, donor 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 another non-limiting example, a base station may include, for example, one or more of a Node B (e.g., associated with Universal Mobile Telecommunications System (UMTS) and / or third-generation (3G) standards), an eNB (e.g., associated with Evolved Universal Terrestrial Radio Access (E-UTRA) and / or fourth-generation (4G) standards), a Remote Radio Head (RRH), a baseband processing unit coupled to one or more RRHs, a repeater node or relay node used to extend the coverage area of ​​a donor node, an ng-eNB, a gNB (e.g., associated with New Radio (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 base station, and / or any combination thereof. A base station may include one or more devices, such as at least one base station central device (e.g., a gNB central unit (gNB-CU)) and at least one base station distribution device (e.g., a gNB distribution unit (gNB-DU)).

[0013] A base station (e.g., in the RAN 104) may include one or more sets of antennas for communicating wirelessly (e.g., over the air interface) with wireless devices 106. One or more base stations may include a set (e.g., a set of three or any other amount of sets) of antennas for respectively controlling multiple cells or sectors (e.g., three cells, three sectors, any other amount of cells, or any other amount of sectors). The size of a cell may be determined by the range over which a receiver (e.g., a base station receiver) can successfully receive a transmission from a transmitter (e.g., a wireless device transmitter) operating within the cell. One or more cells of a base station (e.g., alone or in combination with other cells) may provide / configure wireless coverage to wireless devices 106 over a wide geographic area to support wireless device mobility. A base station including three sectors (e.g., or n sectors, where n refers to any amount n) may be referred to as a three-sector site (e.g., or n-sector site) or a three-sector base station (e.g., n-sector base station).

[0014] One or more base stations (e.g., in the RAN 104) may be implemented as a sector site having more or less than three sectors. One or more base stations of the RAN 104 may be implemented as an AP, as a baseband processing device / unit coupled to multiple RRHs, and / or as a repeater or relay node used to extend the coverage area of ​​a node (e.g., a donor node). The baseband processing device / unit coupled to the RRHs may be part of a centralized or cloud RAN architecture, for example, where the baseband processing device / unit may be centralized within a pool of baseband processing devices / units or may be virtualized. A repeater node may amplify and transmit (e.g., transmit, retransmit, rebroadcast, etc.) a radio signal received from a donor node. A relay node may perform substantially the same / similar functions as a repeater node. A relay node may decode a radio signal received from a donor node, for example, to remove noise before amplifying and transmitting the radio signal.

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

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

[0017] FIG. 1B illustrates an exemplary communication network 150. The communication network may include a mobile communication network. The communication network 150 may include, for example, a PLMN operated / managed / executed by a network operator. The communication network 150 may include a CN 152 (e.g., a 5G Core Network (5G-CN)), a RAN 154 (e.g., an NG-RAN), and / or one or more wireless devices 156A and 156B (collectively, wireless devices 156). The communication network 150 may include one or more data networks (DNs) 170, and / or devices within the communication network 150 may communicate with them (e.g., via the CN 152). These components may be implemented and operate in substantially the same or similar manner as the corresponding components described in connection with FIG. 1A.

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

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

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

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

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

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

[0024] 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 with and / or connect to UPF 158B of AMF / UPF 158 via an NG user plane (NG-U) interface. The NG-U interface may provide / enforce delivery (e.g., non-guaranteed delivery) of user plane PDUs between a base station (e.g., gNB 160A) and a UPF device (e.g., UPF 158B). A base station (e.g., gNB 160A) may communicate with and / or connect to an AMF device (e.g., AMF 158A) via an NG control plane (NG-C) interface. The NG-C interface may provide / perform, for example, NG interface management, wireless device context management (e.g., UE context management), wireless device mobility management (e.g., UE mobility management), transport of NAS messages, paging, PDU session management, configuration transfer, and / or alert message transmission.

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

[0026] The CN 152 (e.g., 5G-CN) may be configured to handle one or more radio accesses (e.g., NR, 4G, and / or any other radio access). Also, an NR network / device (or any first network / device) may be capable of connecting 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 may be used to provide (or at least support) control plane functions (e.g., initial access, mobility, and / or paging). Although only one AMF / UPF 158 is shown in FIG. 1B, one or more base stations (e.g., one or more gNBs and / or one or more ng-eNBs) may be connected to multiple AMF / UPF nodes, e.g., to provide redundancy and / or load sharing across multiple AMF / UPF nodes.

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

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

[0029] FIG. 2A illustrates an exemplary user plane configuration. The user plane configuration may include, for example, an NR user plane protocol stack. FIG. 2B illustrates an exemplary control plane configuration. The control plane configuration may include, for example, an NR control plane protocol stack. One or more of the user plane configuration and / or control plane configuration may use a Uu interface, which may be between the wireless device 210 and the base station 220. The protocol stacks illustrated in FIGS. 2A and 2B may be substantially the same as or similar to those used for the Uu interface between the wireless device 156A and the base station 160A shown in FIG. 1B, for example.

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

[0031] FIG. 3 illustrates example protocol layers. The protocol layers may include, for example, protocol layers of an NR user plane protocol stack. One or more services may be provided between the protocol layers. An SDAP (e.g., SDAPS 215 and 225 shown in FIGS. 2A and 3) may perform QoS flow processing. A wireless device (e.g., wireless device 106, 156A, 156B, and 210) may receive services through / via a PDU session, which may be a logical connection between the wireless device and the DN. A PDU session may have one or more QoS flows 310. A UPF (e.g., UPF 158B) of the CN may map IP packets to one or more QoS flows 310 of the PDU session based on, for example, one or more QoS requirements (e.g., with respect to delay, data rate, error rate, and / or any other quality / service requirement). The SDAPs 215 and 225 may perform mapping / de-mapping between one or more QoS flows 310 and one or more radio bearers 320 (e.g., data radio bearers). The mapping / undemoping between one or more QoS flows 310 and radio bearers 320 may be determined by the SDAP 225 of the base station 220. The SDAP 215 of the wireless device 210 may be informed of the mapping between the QoS flows 310 and radio bearers 320 via reflected mapping and / or control signaling received from the base station 220. For reflected mapping, the SDAP 225 of the base station 220 may mark downlink packets with a QoS flow indicator (QFI) that may be monitored / detected / identified / indicated / observed by the SDAP 215 of the wireless device 210 to determine the mapping / undemoping between one or more QoS flows 310 and radio bearers 320.

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

[0033] The PDCP layer (e.g., PDCP 214 and 224) may perform mapping / undapping between split radio bearers and RLC channels (e.g., RLC channel 330) (e.g., in a dual connectivity scenario / configuration). Dual connectivity may refer to a technology that enables a wireless device to communicate with multiple cells (e.g., two cells), or more broadly, multiple cell groups, including a master cell group (MCG) and a secondary cell group (SCG). A split bearer may be configured and / or used, for example, when a single radio bearer (e.g., one of the radio bearers provided / configured by PDCP 214 and 224 as a service to SDAP 215 and 225) is handled by a cell group in dual connectivity. The PDCP 214 and 224 may map / undap the split radio bearer between the RLC channel 330 belonging to the cell group.

[0034] The RLC layer (e.g., RLC 213 and 223) may perform segmentation, retransmission via automatic repeat request (ARQ), and / or removal of duplicate data units received from the MAC layer (e.g., MAC 212 and 222, respectively). The RLC layer (e.g., RLC 213 and 223) may support multiple transmission modes (e.g., three transmission modes: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM)). The RLC layer (e.g., RLC 213 and 223) may perform one or more of the described functions, for example, based on the transmission mode in which the RLC layer (e.g., RLC 213 and 223) is operating. The RLC configuration may be per logical channel. The RLC configuration may be independent of numerology and / or transmission time interval (TTI) duration (or other duration). The RLC layer (eg, RLC 213 and 223) may provide / configure an RLC channel 330 as a service to the PDCP layer (eg, PDCP 214 and 224, respectively) as shown in FIG.

[0035] The MAC layer (e.g., MAC 212 and 222) may perform multiplexing / demultiplexing of logical channels 340 and / or mapping between logical channels 340 and transport channels 350. Multiplexing / demultiplexing may include multiplexing / demultiplexing of data units / data portions belonging to one or more logical channels 340 to / from transport blocks (TBs) delivered to / from the PHY layer (e.g., PHY 211 and 221, respectively). The MAC layer of the base station (e.g., MAC 222) may be configured to perform scheduling, scheduling information reporting, and / or priority handling between wireless devices via dynamic scheduling. Scheduling may be performed by the base station (e.g., base station 220 at MAC 222) for the downlink / uplink. The MAC layer (e.g., MACs 212 and 222) may be configured to perform error correction via hybrid automatic repeat request (HARQ) (e.g., one HARQ entity per carrier in the case of carrier aggregation (CA)), prioritized handling among the logical channels 340 of the wireless device 210 via logical channel prioritization, and / or padding. The MAC layer (e.g., MACs 212 and 222) may support one or more numerologies and / or transmission timings. Mapping restrictions in logical channel prioritization may control which numerologies and / or transmission timings a logical channel may use. The MAC layer (e.g., MACs 212 and 222) may provide / configure the logical channels 340 as services to the RLC layer (e.g., RLCs 213 and 223).

[0036] The PHY layer (e.g., PHYs 211 and 221) may, for example, perform mapping of transport channel 350 to physical channels and / or digital and analog signal processing functions to transmit and / or receive information (e.g., over the air interface). The digital and / or analog signal processing functions may include, for example, coding / decoding and / or modulation / demodulation. The PHY layer (e.g., PHYs 211 and 221) may perform multi-antenna mapping. The PHY layer (e.g., PHYs 211 and 221) may provide / configure one or more transport channels (e.g., transport channel 350) as services to the MAC layer (e.g., MACs 212 and 222, respectively).

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

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

[0039] Each protocol layer (e.g., a protocol layer as shown in FIG. 4A), or at least some of the protocol layers, may perform its own function (e.g., one or more functions of each protocol layer described with reference to FIG. 3), add a corresponding header, and / or forward its respective output to the next lower layer (e.g., its respective lower layer). PDCP 224 may perform IP header compression and / or encryption. PDCP 224 may forward its output (e.g., PDCP PDUs, which are RLC SDUs) to RLC 223. RLC 223 may optionally perform segmentation (e.g., as shown for IP packets in FIG. 4A). RLC 223 may forward its output (e.g., two RLC PDUs, which are two MAC SDUs, generated by adding respective subheaders to two SDU segments (SDU Segs)) to MAC 222. MAC 222 may multiplex several RLC PDUs (MAC SDUs). The MAC 222 may attach a MAC subheader to the RLC PDU (MAC SDU) to form a TB. The MAC subheader may be distributed throughout the MAC PDU (e.g., in an NR configuration, as shown in FIG. 4A). The MAC subheader may be located entirely at the beginning of the MAC PDU (e.g., in an LTE configuration). The NR MAC PDU structure may reduce processing time and / or associated delay, for example, if the MAC PDU subheader is calculated before assembling the complete MAC PDU.

[0040] 4B shows an example format of a MAC subheader in a MAC PDU. The MAC PDU may include a MAC subheader (H) and a MAC SDU. Each of the one or more MAC subheaders may include an SDU length field to indicate the length (e.g., bytes) of the MAC SDU to which the MAC subheader corresponds, a logical channel identifier (LCID) field to identify / indicate the logical channel on which the MAC SDU originated to assist in the demultiplexing process, a flag (F) to indicate the size of the SDU length field, and a reserved bit (R) field for future use.

[0041] One or more MAC Control Elements (CEs) may be added or inserted into a MAC PDU by a MAC layer, such as MAC 212 or MAC 222. As shown in FIG. 4B, two MAC CEs may be inserted / appended into a MAC PDU. A MAC CE may be inserted / appended to the beginning of a MAC PDU for downlink transmission (as shown in FIG. 4B). One or more MAC CEs may be inserted / appended to the end of a MAC PDU for uplink transmission. MAC CEs may be used for in-band control signaling. Exemplary MAC CEs may include scheduling-related MAC CEs such as buffer status reports and power headroom reports, activation / deactivation MAC CEs (e.g., MAC CEs for PDCP duplicate detection activation / deactivation, channel state information (CSI) reports, sounding reference signal (SRS) transmissions, and pre-configured components), discontinuous reception (DRX)-related MAC CEs, timing advance MAC CEs, and random access-related MAC CEs. The MAC CE may be preceded by a MAC subheader of a format similar to that described in MAC subheader for MAC SDUs and may be identified with a reserved value in the LCID field that indicates the type of control information contained in the corresponding MAC CE.

[0042] FIG. 5A shows an example mapping of downlink channels. The mapping of downlink channels may include mapping between downlink channels (e.g., logical channels, transport channels, and physical channels). FIG. 5B shows an example mapping of uplink channels. The mapping of uplink channels may include mapping between uplink channels (e.g., logical channels, transport channels, and physical channels). Information may be passed through / via channels between the RLC, MAC, and PHY layers of a protocol stack (e.g., an NR protocol stack). Logical channels may be used between the RLC and MAC layers. Logical channels may be classified / designated as control channels that can carry control and / or configuration information (e.g., in the NR control plane) or as traffic channels that can carry data (e.g., in the NR user plane). Logical channels may be classified / designated as dedicated logical channels that may be dedicated to a particular wireless device and / or as common logical channels that may be used by two or more wireless devices (e.g., a group of wireless devices).

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

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

[0045] The PHY layer may pass / transfer information between processing levels of the PHY layer using physical channels. A physical channel may include an associated set of time-frequency resources for carrying information for one or more transport channels. The PHY layer may generate control information to support lower-level operations of the PHY layer. The PHY layer may provide / transfer control information to lower levels of the PHY layer via physical control channels (e.g., referred to as L1 / L2 control channels). The set of physical channels and physical control channels (which may be defined, for example, by an NR configuration or any other configuration) may include one or more of the following channels: The Physical Broadcast Channel (PBCH) may include / carry MIBs from the BCH. The 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, as well as uplink control information (UCI) in some cases, as described below. The Physical Uplink Control Channel (PUCCH) may include / carry UCI, which may include HARQ acknowledgements, channel quality indicators (CQIs), precoding matrix indicators (PMIs), rank indicators (RIs), and scheduling requests (SRs). The Physical Random Access Channel (PRACH) may be used for random access.

[0046] The PHY layer may generate physical signals to support the low-level operations of the PHY layer, which may be similar to physical control channels. As shown in Figures 5A and 5B, the physical layer signals (which may be defined, for example, by an 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.

[0047] One or more of the channels (e.g., logical channels, transport channels, physical channels, etc.) may be used to perform functions associated with a control plane protocol stack (e.g., an NR control plane protocol stack). FIG. 2B illustrates an exemplary control plane configuration (e.g., an NR control plane protocol stack). As shown in FIG. 2B, the control plane configuration (e.g., an NR control plane protocol stack) may use one or more protocol layers (e.g., PHYs 211 and 221, MACs 212 and 222, RLCs 213 and 223, and PDCPs 214 and 224) that are substantially identical / similar to an exemplary user plane configuration (e.g., an NR user plane protocol stack). The similar four protocol layers may include PHYs 211 and 221, MACs 212 and 222, RLCs 213 and 223, and PDCPs 214 and 224. For example, instead of having SDAPs 215 and 225, the control plane configuration (e.g., NR control plane protocol stack) may have radio resource control (RRC) 216 and 226 and NAS protocols 217 and 237 on top of the control plane configuration (e.g., NR control plane protocol stack). The control plane configuration may include an AMF 230 that includes the NAS protocol 237.

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

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

[0050] 6 illustrates exemplary RRC states and RRC state transitions. The RRC state of a wireless device may be changed to another RRC state (e.g., RRC state transitions of a wireless device). The wireless device may be substantially identical to or similar to wireless device 106, 210, or any other wireless device. The wireless device may 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 may be RRC connected but inactive.

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

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

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

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

[0055] The tracking area may be used to track a wireless device (e.g., track the location of a wireless device at the CN level). A CN (e.g., CN 102, CN 152, or any other CN) may send a list of TAIs associated with wireless device registration areas (e.g., UE registration areas) to the wireless device. The wireless device may perform a registration update with the CN to enable the CN to update the location of the wireless device, for example, to provide the wireless device with a new wireless device registration area if the wireless device moves (e.g., via cell reselection) to a cell associated with a TAI that is not included in the list of TAIs associated with the wireless device registration area.

[0056] The RAN area may be used to track a wireless device (e.g., the location of the wireless device at the RAN level). For a wireless device in an RRC inactive state (e.g., RRC inactive 604), the wireless device may be assigned / provisioned / configured in a RAN notification area. The RAN notification area may include one or more cell identities (e.g., a list of RAIs and / or a list of TAIs). A base station may belong to one or more RAN notification areas. A cell may belong to one or more RAN notification areas. The wireless device may perform a notification area update with the RAN to update the RAN notification area of ​​the wireless device, for example, when the wireless device moves (e.g., via cell reselection) to a cell that is not included in the RAN notification area assigned / provisioned / configured to the wireless device.

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

[0058] A base station (e.g., gNB 160 in FIG. 1B or any other base station) may be divided into two parts: a central unit (e.g., a base station central unit such as a gNB-CU) and one or more distributed units (e.g., base station distributed units such as a gNB-DU). The base station central unit (CU) may 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 an RRC layer, a PDCP layer, and an SDAP layer. The base station distributed unit (DU) may include an RLC layer, a MAC layer, and a PHY layer.

[0059] Physical signals and physical channels (e.g., those described in connection with FIGS. 5A and 5B) may be mapped onto one or more symbols (e.g., orthogonal frequency division multiplexing (OFDM) symbols in an NR configuration, or any other symbols). OFDM may be a multicarrier communication scheme that transmits / transmits data over F orthogonal subcarriers (or tones). The data may be mapped to a series of complex symbols (e.g., M-quadrature amplitude modulation (M-QAM) symbols, M-phase shift keying (M-PSK) symbols, or any other modulation symbols), called source symbols, which are divided into F parallel symbol streams before transmission. The F parallel symbol streams may be treated as if they were in the frequency domain. The F parallel symbol streams may be used as input to an inverse fast Fourier transform (IFFT) block, which converts them to the time domain. The IFFT block may receive F source symbols at a time, one from each of the F parallel symbol streams. The IFFT block may use each source symbol to modulate the amplitude and phase of one of the F sinusoidal basis functions corresponding to the F orthogonal subcarriers. The output of the IFFT block may be F time-domain samples representing a sum of F orthogonal subcarriers. The F time-domain samples may form a single OFDM symbol. The OFDM symbols provided / output by the IFFT block may be transmitted / transmitted over the air interface at a carrier frequency, for example, after one or more processes (e.g., adding a cyclic prefix) and upconversion. The F parallel symbol streams may be mixed, for example, using a Fast Fourier Transform (FFT) block before being processed by the IFFT block. This operation may generate a Discrete Fourier Transform (DFT) precoded OFDM symbol, which may be used by one or more wireless devices in the uplink to reduce the peak-to-average power ratio (PAPR). To recover the data mapped to the source symbols, inverse processing may be performed on the OFDM symbols at the receiver using the FFT block.

[0060] FIG. 7 shows an example configuration of a frame. A frame may include, for example, an NR radio frame in which OFDM symbols may be grouped. A frame (e.g., an NR radio frame) may be identified / indicated by a system frame number (SFN) or any other value. The SFN may repeat for a period of 1024 frames. One NR radio frame may be 10 milliseconds (ms) in duration and may include 10 subframes, each of which is 1 ms in duration. A subframe may be divided into one or more slots (e.g., according to numerology and / or different subcarrier spacing). Each of the one or more slots may include, for example, 14 OFDM symbols per slot. Any amount of symbols, slots, or duration may be used for any time interval.

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

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

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

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

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

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

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

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

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

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

[0071] The base station may configure the wireless device with a BWP inactivity timer value for the PCell. The wireless device may start or restart the BWP inactivity timer at any appropriate time. The wireless device may start or restart the BWP inactivity timer, for example, if one or more conditions are met. The one or more conditions may include at least one of: the wireless device detecting a DCI indicating an active downlink BWP other than a default downlink BWP for paired spectrum operation; the wireless device detecting a DCI indicating an active downlink BWP other than a default downlink BWP for unpaired spectrum operation; and / or the wireless device detecting a DCI indicating an active uplink BWP other than a default uplink BWP for unpaired spectrum operation. The wireless device may start / run the BWP inactivity timer towards expiration (e.g., incrementing from zero to the BWP inactivity timer value or decrementing from the BWP inactivity timer value to zero), for example, if the wireless device does not detect a DCI within a time interval (e.g., 1 ms or 0.5 ms). The wireless device may switch from the active downlink BWP to the default downlink BWP, for example, if a BWP inactivity timer expires.

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

[0073] A downlink BWP switch may refer to switching an active downlink BWP from a first downlink BWP to a second downlink BWP (e.g., a second downlink BWP is activated and the first downlink BWP is deactivated). An uplink BWP switch may refer to switching an active uplink BWP from a first uplink BWP to a second uplink BWP (e.g., a second uplink BWP is activated and the first uplink BWP is deactivated). Downlink and uplink BWP switches may be performed independently (e.g., on paired spectrum / spectrum). Downlink and uplink BWP switches may be performed simultaneously (e.g., on unpaired spectrum / spectrum). Switching between configured BWPs may occur based on, for example, RRC signaling, DCI signaling, expiration of a BWP inactivity timer, and / or initiation of random access.

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

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

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

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

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

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

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

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

[0082] 10B shows an exemplary group of cells. Aggregation cells may be configured into one or more PUCCH groups (e.g., as shown in FIG. 10B). One or more cell groups or one or more uplink control channel groups (e.g., PUCCH group 1010 and PUCCH group 1050) may each 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 the PUCCH group 1010 may be configured as a PCell 1021 (e.g., a UL PCC), an SCell 1022 (e.g., a UL SCC), and an SCell 1023 (e.g., a UL SCC). One or more uplink CCs of the PUCCH group 1050 may be configured as a PUCCH SCell (or PSCell) 1061 (e.g., a UL SCC), an SCell 1062 (e.g., a UL SCC), and an SCell 1063 (e.g., a UL SCC). UCIs associated with the downlink CCs of the PUCCH group 1010, denoted as UCI 1031, UCI 1032, and UCI 1033, may be transmitted / transmitted via the uplink of the PCell 1021 (e.g., via the PUCCH of the PCell 1021). The UCIs associated with the downlink CCs of the PUCCH group 1050, denoted as UCI 1071, UCI 1072, and UCI 1073, may be transmitted / transmitted via the uplink of the PUCCH SCell (or PSCell) 1061 (eg, via the PUCCH of the PUCCH SCell 1061).A single uplink PCell may be configured to transmit / carry UCI related to six downlink CCs, for example, if the aggregation cell shown in Figure 10B is not divided into PUCCH group 1010 and PUCCH group 1050. PCell 1021 may become overloaded if, for example, UCIs 1031, 1032, 1033, 1071, 1072, and 1073 are transmitted / carried via PCell 1021. By splitting the transmission of UCI between PCell 1021 and PUCCH SCell (or PSCell) 1061, overloading can be prevented and / or reduced.

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

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

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

[0086] FIG. 11A shows an example mapping of one or more SS / PBCH blocks. A burst of SS / PBCH blocks may include one or more SS / PBCH blocks (e.g., four SS / PBCH blocks as shown in FIG. 11A). Bursts may be sent / transmitted periodically (e.g., every two frames, every 20 ms, or any other duration). Bursts may be limited to half frames (e.g., the first half frame having a duration of 5 ms). Such parameters (e.g., the number of SS / PBCH blocks per burst, the periodicity of the burst, the position of the burst within a frame) may be configured based on, for example, at least one of the carrier frequency of the cell in which the SS / PBCH block is sent / transmitted, the numerology or subcarrier spacing of the cell, configuration by the network (e.g., using RRC signaling), and / or any other suitable factor. The wireless device may assume subcarrier spacing for the SS / PBCH block based on the monitored carrier frequency, unless, for example, the wireless network configures the wireless device to assume a different subcarrier spacing.

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

[0088] The location of the SS / PBCH block in the time and frequency domains may not be known to the wireless device (e.g., when the wireless device is searching for a cell). The wireless device may monitor the carrier for a PSS, for example, to find and select a cell. The wireless device may monitor a frequency location within the carrier. If the wireless device does not find a PSS, for example, after a period of time (e.g., 20 ms), it may search for a PSS at a different frequency location within the carrier. The wireless device may search for a PSS at a different frequency location within the carrier, for example, as indicated by a synchronization raster. If the PSS is found at a location in the time and frequency domains, the wireless device may determine the location of the SSS and PBCH, respectively, 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). A primary cell may be associated with the CD-SSB. The CD-SSB may be located on the synchronization raster. Cell selection / search and / or reselection may be based on the CD-SSB.

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

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

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

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

[0093] The CSI-RS may be sent / transmitted by a base station and used by a wireless device to acquire / obtain / determine CSI. The base station may configure a wireless device with one or more CSI-RS for channel estimation or any other suitable purpose. The base station may configure a wireless device with one or more substantially identical / similar CSI-RS. The wireless device may measure one or more CSI-RS. The wireless device may estimate downlink channel conditions and / or generate a CSI report, for example, based on measurements of one or more downlink CSI-RS. The wireless device may send / transmit a CSI report to the base station (e.g., based on periodic CSI reports, semi-persistent CSI reports, and / or aperiodic CSI reports). The base station may perform link adaptation using feedback (e.g., estimated downlink channel conditions) provided by the wireless device.

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

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

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

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

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

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

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

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

[0102] One or more SRSs may be transmitted / transmitted by a wireless device to a base station for channel condition estimation, e.g., to support uplink channel-dependent scheduling and / or link adaptation. The SRS transmitted / transmitted by the wireless device may enable / enable the base station to estimate uplink channel conditions at one or more frequencies. A scheduler at the base station may use / employ the estimated uplink channel conditions to allocate one or more resource blocks for uplink PUSCH transmission for the wireless device. A base station may semi-statically configure a wireless device with one or more SRS resource sets. For an SRS resource set, the base station may configure the wireless device with one or more SRS resources. SRS resource set applicability may be configured, for example, by higher layer (e.g., RRC) parameters. SRS resources within an SRS resource set of one or more SRS resource sets (e.g., having substantially the same / similar time-domain behavior, periodic, aperiodic, and / or the like) may be transmitted / transmitted instantaneously (e.g., simultaneously), e.g., when higher layer parameters indicate beam management. A wireless device may transmit / transmit one or more SRS resources in an SRS resource set. A network (e.g., an NR network) may support aperiodic, periodic, and / or semi-persistent SRS transmission. 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. At least one DCI format may be used / adopted by the wireless device to select at least one of the one or more configured SRS resource sets. SRS trigger type 0 may refer to an SRS triggered based on higher layer signaling. SRS trigger type 1 may refer to an SRS triggered based on one or more DCI formats. A wireless device may be configured to transmit / transmit an SRS after transmission of a PUSCH and a corresponding uplink DM-RS, for example, when the PUSCH and SRS are transmitted / transmitted in the same slot.A base station may quasi-statistically configure a wireless device with one or more SRS configuration parameters indicating at least one of an SRS resource configuration identifier, a number of SRS ports, a time domain behavior of the SRS resource configuration (e.g., an indication of periodic, semi-persistent, or aperiodic SRS), slot, minislot, and / or subframe level periodicity, an offset for periodic and / or aperiodic SRS resources, a number of OFDM symbols in an SRS resource, a starting OFDM symbol of the SRS resource, an SRS bandwidth, a frequency hopping bandwidth, a cyclic shift, and / or an SRS sequence ID.

[0103] Antenna ports may be determined / defined such that a channel through which a symbol on an antenna port is conveyed can be inferred from a channel through which another symbol on the same antenna port is conveyed. For example, when a first symbol and a second symbol are transmitted / transmitted on the same antenna port, a receiver may infer / determine a channel (e.g., fade gain, multipath delay, and / or the like) for conveying a second symbol on an antenna port from a channel for conveying a first symbol on the antenna port. A first antenna port and a second antenna port may be referred to as QCL-ized, for example, when one or more large-scale characteristics of a channel through which a first symbol on the first antenna port is conveyed can be inferred / determined from a channel through which a second symbol on the second antenna port is conveyed. The one or more large-scale characteristics may include at least one of delay spread, Doppler spread, Doppler shift, average gain, average delay, and / or Rx parameters.

[0104] A channel using beamforming may require beam management. Beam management may include beam measurement, beam selection, and / or beam direction. A beam may be associated with one or more reference signals. A beam may be identified by one or more beamforming reference signals. A wireless device may perform downlink beam measurements and generate beam measurement reports, for example, based on one or more downlink reference signals (e.g., CSI-RS). A wireless device may perform a downlink beam measurement procedure, for example, after an RRC connection is set up with a base station.

[0105] Figure 11B shows an example mapping of one or more CSI-RSs. The CSI-RSs may be mapped in the time domain and the frequency domain. Each rectangular block shown in Figure 11B may correspond to an RB in the bandwidth of a cell. A base station may send / transmit one or more RRC messages including CSI-RS resource configuration parameters indicating one or more CSI-RSs. One or more of the parameters may be configured by higher layer signaling (e.g., RRC and / or MAC signaling) for CSI-RS resource configuration. One or more of the parameters may include at least one of a CSI-RS resource configuration identification, a number of CSI-RS ports, a CSI-RS configuration (e.g., symbol and RE location within a subframe), a CSI-RS subframe configuration (e.g., subframe location, offset, and radio frame periodicity), a CSI-RS power parameter, a CSI-RS sequence parameter, a code division multiplexing (CDM) type parameter, a frequency density, a transmit comb, a QCL parameter (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and / or other radio resource parameters.

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

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

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

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

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

[0111] A wireless device may initiate / start / perform a beam failure recovery (BFR) procedure, for example, based on detecting a beam failure. A wireless device may send / transmit a BFR request (e.g., a preamble, UCI, SR, MAC CE, and / or the like) based on, for example, initiating a BFR procedure. A wireless device may detect a beam failure, for example, based on determining that the quality of a beam pair link of an associated control channel is insufficient (e.g., having an error rate higher than an error rate threshold, a received signal power lower than a received signal power threshold, a timer expiring, and / or the like).

[0112] A wireless device may measure the quality of a beam pair link using one or more RSs, including, for example, one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more DM-RSs. The quality of the beam pair link may be based on one or more of a block error rate (BLER), an RSRP value, a signal-to-interference-plus-noise ratio (SINR) value, an RSRQ value, and / or a CSI value measured on the RS resource. A base station may indicate that an RS resource is QCLed with one or more DM-RSs of a channel (e.g., a control channel, a shared data channel, and / or the like). An RS resource and one or more DM-RSs of a channel may be QCLed, for example, if the channel characteristics (e.g., Doppler shift, Doppler spread, mean delay, delay spread, spatial Rx parameters, fading, and / or the like) transmitted to the wireless device via the RS resource are substantially the same as or similar to the channel characteristics transmitted to the wireless device via the channel.

[0113] A network (e.g., an NR network including a gNB and / or an ng-eNB) and / or a wireless device may initiate / start / perform a random access procedure. A wireless device in an RRC idle (e.g., RRC_IDLE) state and / or an RRC inactive (e.g., RRC_INACTIVE) state may initiate / perform a random access procedure to request connection setup to the network. A wireless device may initiate / start / perform a random access procedure from an RRC connected (e.g., RRC_CONNECTED) state. A wireless device may initiate / start / perform a random access procedure to request uplink resources (e.g., for uplink transmission of SR when there are no PUCCH resources available) and / or acquire / obtain / determine uplink timing (e.g., when the uplink synchronization state is asynchronous). A wireless device may initiate / start / perform a random access procedure to request one or more SIBs (e.g., SIB2, SIB3, or any other system information block, and / or similar). A wireless device may initiate / start / perform a random access procedure for a beam failure recovery request. The network may initiate / start / perform a random access procedure to establish time alignment for e.g. handover and / or SCell addition.

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

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

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

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

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

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

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

[0121] The second message (e.g., Msg2 1312) (e.g., received by the wireless device) may include an RAR. The second message (e.g., Msg2 1312) may include multiple RARs corresponding to multiple wireless devices. The second message (e.g., Msg2 1312) may be received, for example, based on (e.g., subsequently in response to) the transmission / transmission of the first message (e.g., Msg1 1311). The second message (e.g., Msg2 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., Msg2 1312) may indicate that the first message (e.g., Msg1 1311) has been received by the base station. The second message (e.g., Msg2 1312) may include a time alignment command that may be used by the wireless device to adjust its transmit timing, a scheduling grant for transmission of the third message (e.g., Msg3 1313), and / or a temporary cell RNTI (TC-RNTI). The wireless device may, for example, determine / start a time window (e.g., ra-ResponseWindow) in which to monitor the PDCCH for the second message (e.g., Msg2 1312) after transmitting / transmitting the first message (e.g., Msg1 1311) (e.g., a preamble). The wireless device may determine the start time of the time window based, for example, on the PRACH opportunity that the wireless device uses to transmit / transmit the first message (e.g., Msg1 1311) (e.g., a preamble). The wireless device may start the time window one or more symbols after the last symbol of the first message (e.g., Msg1 1311) including the preamble (e.g., the symbol at which the first message (e.g., Msg1 1311) including the preamble transmission is completed or is in the first PDCCH opportunity from the end of the preamble transmission). The one or more symbols may be determined based on numerology. The PDCCH may be mapped to a common search space (e.g., Type1-PDCCH common search space) configured by the RRC message.A wireless device may identify / determine the RAR, for example, based on the RNTI. The RNTI may be used in response to one or more events that initiate / start a random access procedure. A wireless device may use the RA-RNTI, for example, for one or more communications related to random access or any other purpose. The RA-RNTI may be associated with a PRACH opportunity on which the wireless device transmits / transmits a preamble. A wireless device may determine the RA-RNTI, for example, based on at least one of an OFDM symbol index, a slot index, a frequency domain index, and / or a UL carrier indicator of the PRACH opportunity. An exemplary RA-RNTI may be determined as follows: RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id, where s_id may be the index of the first OFDM symbol of the PRACH opportunity (e.g., 0≦s_id<14), t_id may be the index of the first slot of the PRACH opportunity in the system frame (e.g., 0≦t_id<80), f_id may be the index of the PRACH opportunity in the frequency domain (e.g., 0≦f_id<8), and ul_carrier_id may be the UL carrier used for preamble transmission (e.g., 0 for NUL carrier and 1 for SUL carrier).

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

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

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

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

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

[0127] The wireless device may start a time window (e.g., ra-ResponseWindow) for monitoring the PDCCH for the RAR, for example, based on (e.g., after or in response to) transmitting / transmitting a preamble. The base station may configure the wireless device with one or more beam failure recovery parameters, such as a separate time window and / or a separate PDCCH, in a search space indicated by an RRC message (e.g., recoverySearchSpaceId). The base station may configure one or more beam failure recovery parameters, for example, in association with a beam failure recovery request. The separate time window for monitoring the PDCCH and / or RAR may be configured to start after transmitting / transmitting the beam failure recovery request (e.g., the window may start any number of symbols and / or slots after transmitting / transmitting the beam failure recovery request). The wireless device may monitor PDCCH transmissions addressed to a Cell RNTI (C-RNTI) on the search space. During a two-step (e.g., contention-free) random access procedure, the wireless device may determine that the random access procedure is successful, for example, based on (e.g., after or in response to) sending / transmitting a first message (e.g., Msg1 1321) and receiving a corresponding second message (e.g., Msg2 1322). The wireless device may determine that the random access procedure is successfully completed, for example, if a PDCCH transmission is addressed to the corresponding C-RNTI. The wireless device may determine that the random access procedure is successfully completed, for example, if the wireless device receives an RAR including a preamble identifier corresponding to a preamble sent / transmitted by the wireless device and / or the RAR includes a MAC sub-PDU with the preamble identifier. The wireless device may determine the response as an indication of an acknowledgement to the SI request.

[0128] 13C shows an exemplary two-step random access procedure. Similar to the random access procedures shown in FIGS. 13A and 13B, the base station may send / transmit a configuration message 1330 to the wireless device prior to initiating the procedure. The configuration message 1330 may be similar in some respects to the configuration message 1310 and / or the configuration message 1320. The procedure shown in FIG. 13C 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)).

[0129] A first message (e.g., Msg A 1331) may be sent / transmitted in an uplink transmission by the wireless device. The first message (e.g., Msg A 1331) may include one or more transmissions of a preamble 1341 and / or one or more transmissions of a transport block 1342. The transport block 1342 may include content similar and / or equivalent to the content of the third message (e.g., Msg3 1313) (e.g., as shown in FIG. 13A). The transport block 1342 may include UCI (e.g., SR, HARQ ACK / NACK, and / or the like). The wireless device may receive a second message (e.g., Msg B 1332), for example, based on (e.g., subsequently in response to) sending / transmitting the first message (e.g., Msg A 1331). The second message (e.g., Msg B 1332) may include content similar and / or equivalent to the content of the second message (e.g., Msg2 1312) (e.g., the RAR shown in FIG. 13A), the content of the second message (e.g., Msg2 1322) (e.g., the RAR shown in FIG. 13B), and / or the content of the fourth message (e.g., Msg4 1314) (e.g., shown in FIG. 13A).

[0130] A wireless device may start / initiate a two-step random access procedure (e.g., the two-step random access procedure shown in FIG. 13C) for licensed and / or unlicensed spectrum. The wireless device may determine whether to start / initiate the two-step random access procedure based on one or more factors. The one or more factors may include at least one of the radio access technology in use (e.g., LTE, NR, and / or the like), whether the wireless device has a valid TA, the cell size, the RRC state of the wireless device, the type of spectrum (e.g., licensed vs. unlicensed), and / or any other suitable factor.

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

[0132] The transport block 1342 may include data (e.g., delay-sensitive data), a wireless 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., Msg B 1332) in response to the first message (e.g., Msg A 1331). The second message (e.g., Msg B 1332) may include at least one of a preamble identifier, a timing advance command, a power control command, an uplink grant (e.g., radio resource allocation and / or MCS), a wireless device identifier (e.g., a UE identifier for contention resolution), and / or an RNTI (e.g., C-RNTI or TC-RNTI). The wireless device may determine that the two-step random access procedure has been successfully completed, for example, if the preamble identifier of the second message (e.g., Msg B 1332) corresponds to or matches the preamble sent / transmitted by the wireless device, and / or if the identifier of the wireless device of the second message (e.g., Msg B 1332) corresponds to or matches the identifier of the wireless device (e.g., transport block 1342) of the first message (e.g., Msg A 1331).

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

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

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

[0136] DCIs may be used for different purposes. The purpose may be indicated by the type of RNTI used to scramble the CRC parity bits. A DCI with CRC parity bits scrambled with a paging RNTI (P-RNTI) may indicate paging information and / or system information change notification. The P-RNTI may be predefined as "FFFE" in hexadecimal. A DCI with CRC parity bits scrambled with a system information RNTI (SI-RNTI) may indicate a broadcast transmission of system information. The SI-RNTI may be predefined as "FFFF" in hexadecimal. A DCI with CRC parity bits scrambled with a random access RNTI (RA-RNTI) may indicate a random access response (RAR). A DCI with CRC parity bits scrambled with a cell RNTI (C-RNTI) may indicate a unicast transmission of dynamic scheduling and / or a random access of PDCCH order trigger. A DCI with CRC parity bits scrambled with the Temporary Cell RNTI (TC-RNTI) may indicate contention resolution (e.g., Msg3 similar to Msg3 1313 shown in FIG. 13A). Other RNTIs configured for the wireless device by the base station include a Configured Scheduling RNTI (CS RNTI), a Transmit Power Control PUCCH RNTI (TPC PUCCH-RNTI), a Transmit Power Control PUSCH RNTI (TPC-PUSCH-RNTI), a Transmit Power Control SRS RNTI (TPC-SRS-RNTI), an Interruption RNTI (INT-RNTI), a Slot Format Indicator RNTI (SFI-RNTI), a Semi-Persistent CSI RNTI (SP-CSI-RNTI), a Modulation and Coding Scheme Cell RNTI (MCS-C RNTI), and / or the like.

[0137] A base station may transmit / transmit DCI in one or more DCI formats, depending on, for example, the purpose and / or content of the DCI. DCI format 0_0 may be used for scheduling a PUSCH in a cell. DCI format 0_0 may be a fallback DCI format (e.g., having a compact DCI payload). DCI format 0_1 ​​may be used for scheduling a PUSCH in a cell (e.g., having a larger DCI payload than DCI format 0_0). DCI format 1_0 may be used for scheduling a PDSCH in a cell. DCI format 1_0 may be a fallback DCI format (e.g., having a compact DCI payload). DCI format 1_1 may be used for scheduling a PDSCH in a cell (e.g., having a larger DCI payload than DCI format 1_0). DCI format 2_0 may be used to provide slot format indication to a group of wireless devices. DCI format 2_1 may be used to inform / inform a group of wireless devices of physical resource blocks and / or OFDM symbols that the group of wireless devices may assume are not intended for the group of wireless devices. DCI format 2_2 may be used for transmitting transmit power control (TPC) commands for the PUCCH or PUSCH. DCI format 2_3 may be used for transmitting a group of TPC commands for SRS transmission by one or more wireless devices. DCI formats for new features may be defined in future releases. DCI formats may have different DCI sizes or share the same DCI size.

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

[0139] FIG. 14A shows an example of a CORESET configuration. The CORESET configuration may be for a bandwidth portion or any other frequency band. A base station may transmit / transmit DCI via a PDCCH on one or more CORESETs. A CORESET may include time-frequency resources on which a wireless device attempts to decode the DCI using one or more search spaces. A base station may configure the size and location of the CORESET in the time-frequency domain. The first CORESET 1401 and the second CORESET 1402 may occur or be configured / set at the first symbol in a slot. The first CORESET 1401 may overlap with the second CORESET 1402 in the frequency domain. The third CORESET 1403 may occur or be configured / set at the third symbol in a slot. The fourth CORESET 1404 may occur or be configured / set at the seventh symbol in a slot. The CORESETs may have different numbers of resource blocks in the frequency domain.

[0140] FIG. 14B shows an example of CCE-to-REG mapping. CCE-to-REG mapping may be implemented for DCI transmission via CORESET and PDCCH processing. CCE-to-REG mapping may be interleaved (e.g., to provide frequency diversity) or non-interleaved (e.g., to facilitate interference coordination and / or frequency-selective transmission of control channels). A base station may implement different or identical CCE-to-REG mappings in different CORESETs. A CORESET may be associated with a CCE-to-REG mapping (e.g., by RRC configuration). A CORESET may be configured with an antenna port QCL parameter. The QCL parameter of an antenna port may indicate QCL information of a DM-RS for PDCCH reception via CORESET.

[0141] A base station may send / transmit one or more RRC messages including configuration parameters of one or more CORESETs and one or more search space sets to a wireless device. The configuration parameters may indicate an 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). The configuration parameters may indicate at least one of: several PDCCH candidates to be monitored per aggregation level; a PDCCH monitoring periodicity and a PDCCH monitoring pattern; one or more DCI formats to be monitored by the wireless device; and / or whether the search space set is a common search space set or a wireless device-specific search space set (e.g., a UE-specific search space set). The set of CCEs in the common search space set may be predefined and known to the wireless device. The set of CCEs in the wireless device-specific search space set (e.g., a UE-specific search space set) may be configured based on, for example, an identity of the wireless device (e.g., a C-RNTI).

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

[0143] The wireless device may send / transmit uplink control signaling (e.g., UCI) to the base station. The uplink control signaling may include a HARQ acknowledgment for a received DL-SCH transport block. The wireless device may send / transmit the HARQ acknowledgment, for example, based on (e.g., subsequently in response to) receiving the DL-SCH transport block. The uplink control signaling may include CSI indicating the channel quality of the physical downlink channel. The wireless device may send / transmit the CSI to the base station. The base station may determine transmission format parameters (e.g., including multiple antennas and beamforming schemes) for the downlink transmission based on the received CSI. The uplink control signaling may include an 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 UCI (e.g., a HARQ acknowledgment (HARQ-ACK), a CSI report, an SR, etc.) via the PUCCH or the PUSCH. A wireless device may transmit / carry uplink control signaling over the PUCCH using one of several PUCCH formats.

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

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

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

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

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

[0149] For the downlink, data transmitted from the base station 1504 to the wireless device 1502 may be provided / forwarded / transmitted to the processing system 1508 of the base station 1504. The data may be provided / forwarded / transmitted to the processing system 1508 by, for example, a core network. For the uplink, data transmitted from the wireless device 1502 to the base station 1504 may be provided / forwarded / transmitted to the processing system 1518 of the wireless device 1502. The processing system 1508 and the processing system 1518 may implement Layer 3 and Layer 2 OSI functions to process the data for transmission. Layer 2 may include, for example, the SDAP layer, PDCP layer, RLC layer, and MAC layer described in connection with FIG. 2A, 2B, 3, and 4A. Layer 3 may include, for example, the RRC layer described in connection with FIG. 2B.

[0150] Data to be transmitted to the wireless device 1502 may be processed, for example, by processing system 1508 before being provided / forwarded / transmitted to transmit processing system 1510 of the base station 1504. Data to be transmitted to the base station 1504 may be processed, for example, by processing system 1518 before being provided / forwarded / transmitted to transmit processing system 1520 of the wireless device 1502. Transmit processing system 1510 and transmit processing system 1520 may implement the OSI functions of Layer 1. Layer 1 may comprise, for example, the PHY layer described in connection with FIGS. 2A, 2B, 3, and 4A. For transmit processing, the PHY layer may perform, for example, forward error correction coding of transport channels, interleaving, rate matching, mapping of transport channels to physical channels, modulation of physical channels, multiple-input multiple-output (MIMO) or multi-antenna processing, and / or the like.

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

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

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

[0154] Processing system 1508 and / or processing system 1518 may include one or more controllers and / or one or more processors. 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, on-board units, or any combination thereof. Processing system 1508 and / or processing system 1518 may perform at least one of signal coding / processing, data processing, power control, input / output processing, and / or any other functionality that may enable wireless device 1502 and / or base station 1504 to operate in a wireless environment.

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

[0156] 15B shows exemplary elements of a computing device that may be used to implement any of the various devices described herein, including, for example, base stations 160A, 160B, 162A, 162B, 220, 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 may execute instructions stored in random access memory (RAM) 1533, removable media 1534 (such as a USB drive, a compact disc (CD) or digital versatile disc (DVD), or a floppy disk drive), or any other desired storage medium. Instructions may also be stored on an attached (or internal) hard drive 1535. Computing device 1530 may also include a security processor (not shown) that may execute instructions of one or more computer programs to monitor processes running on processor 1531 and any processes requesting access to any hardware and / or software components of computing device 1530 (e.g., ROM 1532, RAM 1533, removable media 1534, hard drive 1535, device controller 1537, network interface 1539, GPS 1541, Bluetooth interface 1542, WiFi interface 1543, etc.). Computing device 1530 may include one or more output devices such as a display 1536 (e.g., a screen, display device, monitor, television, etc.) and may include one or more output device controllers 1537, such as a video processor. There may also be one or more user input devices 1538, such as a remote control, keyboard, mouse, touchscreen, microphone, etc. Computing device 1530 may also include one or more network interfaces, such as network interface 1539, which may be a wired interface, a wireless interface, or a combination of the two.The network interface 1539 may provide an interface through which the computing device 1530 communicates with a network 1540 (e.g., a RAN or any other network). The network interface 1539 may include a modem (e.g., a cable modem), and the external network 1540 may include a communications link, an external network, a home network, a provider's wireless, coaxial, fiber, or hybrid fiber / coaxial distribution system (e.g., a DOCSIS network), or any other desired network. Additionally, the computing device 1530 may include a location detection device such as a GPS microprocessor 1541 that may be configured to receive and process global positioning signals and, with possible assistance from external servers and antennas, determine the geographic location of the computing device 1530.

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

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

[0159] 16B shows an exemplary structure for modulation and upconversion of a baseband signal to a carrier frequency. The baseband signal may be a complex-valued SC-FDMA, CP-OFDM baseband signal (or any other baseband signal) for an antenna port and / or a complex-valued Physical Random Access Channel (PRACH) baseband signal. Filtering may be performed / employed, for example, before transmission.

[0160] 16C shows an example structure of a downlink transmission. The processing of the baseband signal representing the physical downlink channel may include / perform one or more functions. The one or more functions may include scrambling coded bits in a codeword to be 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 several transmission layers, precoding the complex-valued modulation symbols on the layers for transmission on the antenna ports, mapping the complex-valued modulation symbols of the antenna ports to resource elements, generating a complex-valued time-domain OFDM signal per antenna port, and / or the like. These functions are examples, and other mechanisms for downlink transmission may be implemented.

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

[0162] A wireless device may receive one or more messages (e.g., RRC messages) from a base station that include configuration parameters for multiple cells (e.g., a primary cell, one or more secondary cells). The wireless device may communicate with at least one base station (e.g., two or more base stations for dual connectivity) via the multiple cells. The one or more messages (e.g., as part of the configuration parameters) may include PHY, MAC, RLC, PCDP, SDAP, and RRC layer parameters for configuring 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.

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

[0164] A base station may communicate with wireless devices via a wireless network (e.g., a communication network). The communication may use / employ one or more wireless technologies (e.g., new wireless technologies, legacy wireless technologies, and / or a combination thereof). The one or more wireless technologies may include at least one of one or more technologies associated with a physical layer, one or more technologies associated with a media access control layer, and / or one or more technologies associated with a radio resource control layer. One or more enhanced wireless technologies described herein may improve performance of a wireless network. System throughput, transmission efficiency, and / or transmission rate of a wireless network may be improved, for example, based on one or more configurations described herein. Battery consumption of a wireless device may be reduced, for example, based on one or more configurations described herein. Delay of data transmission between a base station and a wireless device may be improved, for example, based on one or more configurations described herein. Network coverage of a wireless network may be increased, for example, based on one or more configurations described herein.

[0165] A base station may send / transmit one or more MAC PDUs to a wireless device. A MAC PDU may be a bit string whose length is byte-aligned (e.g., aligned to a multiple of 8 bits). The bit string may be represented by one or more tables with the most significant bit being the leftmost bit in the first row of the table and the least significant bit being the rightmost bit in the last row of the table. The bit string may be read from left to right, then in line reading order (e.g., from the top line of the table to the bottom line of the table). The bit order of the parameter field within the MAC PDU may be represented with the most significant bit first in the leftmost bit and the least significant bit last in the rightmost bit.

[0166] The MAC SDU may be a bit string whose length is byte-aligned (e.g., aligned to a multiple of 8 bits). The MAC SDU may be included in the MAC PDU from the first bit onwards. The MAC CE may be a bit string whose length is byte-aligned (e.g., aligned to a multiple of 8 bits). The MAC subheader may be a bit string whose length is byte-aligned (e.g., aligned to a multiple of 8 bits). The MAC subheader may be located immediately before the corresponding MAC SDU, MAC CE, or padding. A wireless device (e.g., a MAC entity of a wireless device) may ignore the value of the reserved bit in a downlink (DL) MAC PDU.

[0167] A MAC PDU may include one or more MAC sub-PDUs. A MAC sub-PDU of the one or more MAC sub-PDUs may include a MAC subheader only (including padding), a MAC subheader and a MAC SDU, a MAC subheader and a MAC CE, a MAC subheader and padding, and / or a combination thereof. A MAC SDU may be of variable size. A MAC subheader may correspond to a MAC SDU, a MAC CE, or padding.

[0168] The MAC subheader may include, for example, an R field having a length of 1 bit, an F field having a length of 1 bit, an LCID field having a length of multiple bits, an L field having a length of multiple bits, and / or combinations thereof if the MAC subheader corresponds to a MAC SDU, a variable-sized MAC CE, or padding.

[0169] FIG. 17A shows an example of a MAC subheader. The MAC subheader may include an R field, an F field, an LCID field, and / or an L field. The LCID field may be 6 bits long (or any other amount of bits). The L field may be 8 bits long (or any other amount of bits). Each of the R field and the F field may be 1 bit long (or any other amount of bits). FIG. 17B shows an example of a MAC subheader. The MAC subheader may include an R field, an F field, an LCID field, and / or an L field. Similar to the MAC subheader shown in FIG. 17A, the LCID field may be 6 bits long (or any other amount of bits), the R field may be 1 bit long (or any other amount of bits), and the F field may be 1 bit long (or any other amount of bits). The L field may be 16 bits long (or any other amount of bits, such as longer than 16 bits). The MAC subheader may include an R field having a length of 2 bits (or any other amount of bits) and / or an LCID field having a multi-bit length (or a single-bit length), for example, if the MAC subheader corresponds to a fixed-size MAC CE or padding. Figure 17C shows an example of a MAC subheader. In the example MAC subheader shown in Figure 17C, the LCID field may be 6 bits long (or any other amount of bits), and the R field may be 2 bits long (or any other amount of bits).

[0170] FIG. 18A shows an example of a MAC PDU (e.g., a DL MAC PDU). Multiple MAC CEs, such as MAC CE1 and 2 shown in FIG. 18A, may be located together (e.g., located within the same MAC PDU). A MAC sub-PDU containing a MAC CE may be located before (e.g., located within) any MAC sub-PDU containing a MAC SDU or a MAC sub-PDU containing padding. MAC CE1 may be a fixed-size MAC CE conforming to a first-type MAC subheader. The first-type MAC subheader may include an R field and an LCID field (e.g., similar to the MAC CE shown in FIG. 17C). MAC CE2 may be a variable-size MAC CE conforming to a second-type MAC subheader. The second-type MAC subheader may include an R field, an F field, an LCID field, and an L field (e.g., similar to the MAC CE shown in FIG. 17A or 17B). The size of a MAC SDU conforming to a second-type MAC subheader may vary.

[0171] FIG. 18B shows an example of a MAC PDU (e.g., a UL MAC PDU). Multiple MAC CEs, such as MAC CE1 and 2 shown in FIG. 18B, may be located together (e.g., located within the same MAC PDU). A MAC sub-PDU containing a MAC CE may be located after all MAC sub-PDUs containing MAC SDUs (e.g., located within the MAC PDU). A MAC sub-PDU and / or a MAC sub-PDU containing a MAC CE may be located before a MAC sub-PDU containing padding (e.g., located within the MAC PDU). Similar to the MAC CE shown in FIG. 18A, MAC CE1 shown in FIG. 18B may be a fixed-size MAC CE conforming to a first-type MAC subheader. The first-type MAC subheader may include an R field and an LCID field (e.g., similar to the MAC CE shown in FIG. 17C). Similar to the MAC CE shown in FIG. 18A, MAC CE2 shown in FIG. 18B may be a variable-size MAC CE conforming to a second-type MAC subheader. The second type MAC subheader may include an R field, an F field, an LCID field, and an L field (e.g., similar to the MAC CE shown in Figure 17A or 17B). The size of the MAC SDU according to the second type MAC subheader may vary.

[0172] A base station (e.g., a MAC entity of a base station) may transmit / transmit one or more MAC CEs to a wireless device (e.g., a MAC entity of a wireless device). Figure 19 shows exemplary LCID values. An LCID value may be associated with one or more MAC CEs. An LCID value may be associated with a downlink channel, such as a DL-SCH. The one or more MAC CEs may include a semi-persistent zero power CSI-RS (SP ZP CSI-RS) resource set activation / deactivation MAC CE, a PUCCH spatial relationship activation / deactivation MAC CE, an SP SRS activation / deactivation MAC CE, an SP CSI report activation / deactivation MAC CE for PUCCH, a wireless device-specific (e.g., UE-specific) PDCCH TCI state indication MAC CE, a wireless device-specific (e.g., UE-specific) PDSCH TCI state indication MAC CE, an aperiodic CSI trigger state subselection MAC CE, an SP CSI-RS / CSI interference measurement (CSI-IM) resource set activation / deactivation MAC CE, a wireless 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, an SCell activation / deactivation MAC CE (e.g., 1 octet), and an SCell activation / deactivation MAC CE. The MAC CE may include at least one of a long DRX command MAC CE (e.g., 4 octets) and / or a duplicate activation / deactivation MAC CE. A MAC CE, such as a MAC CE sent / transmitted by a base station (e.g., a MAC entity of the base station) to a wireless device (e.g., a MAC entity of the wireless device), may be associated with (e.g., corresponds to) an LCID in a MAC subheader corresponding to the MAC CE. Different MAC CEs may correspond to different LCIDs in a MAC subheader corresponding to the MAC CE. An LCID having an index value "111011" in a MAC subheader may indicate that the MAC CE associated with the MAC subheader is a long DRX command MAC CE, e.g., with respect to a MAC CE associated with the downlink.

[0173] A wireless device (e.g., a MAC entity of the wireless device) may send / transmit one or more MAC CEs to a base station (e.g., a MAC entity of the base station). FIG. 20 shows example LCID values ​​that may be associated with one or more MAC CEs. The LCID values ​​may be associated with an uplink channel such as UL-SCH. The one or more MAC CEs may include at least one of a short buffer status report (BSR) MAC CE, a long BSR MAC CE, a C-RNTI MAC CE, a configured grant confirmation MAC CE, a single-entry power headroom report (PHR) MAC CE, a multiple-entry PHR MAC CE, a short truncated BSR, and / or a long truncated BSR. A MAC CE may be associated with (e.g., corresponds to) an LCID in a MAC subheader corresponding to the MAC CE. Different MAC CEs may correspond to different LCIDs in the MAC subheader corresponding to the MAC CE. An LCID having an index value of "111011" in a MAC subheader may indicate that the MAC CE associated with the MAC subheader is a short abbreviated command MAC CE, for example, with respect to a MAC CE associated with an uplink.

[0174] Two or more CCs may be aggregated, such as through carrier aggregation (CA). A wireless device may simultaneously receive and / or transmit data over one or more CCs (e.g., using CA techniques), depending on, for example, the capabilities of the wireless device. A wireless device may support CA for adjacent and / or non-adjacent CCs. CCs may be organized into cells. CCs may be organized into one PCell and one or more SCells.

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

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

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

[0178] Figure 21A shows an exemplary SCell activation / deactivation MAC CE of one octet. A first MAC PDU subheader including a first LCID (e.g., "111010" shown in Figure 19) may indicate / identify the SCell activation / deactivation MAC CE of one octet. The SCell activation / deactivation MAC CE of one octet may have a fixed size. The SCell activation / deactivation MAC CE of one octet may include a single octet. The single octet may include a first quantity / number C field (e.g., 7 or any other quantity / number) and a second quantity / number R field (e.g., 1 or any other quantity / number).

[0179] Figure 21B shows an exemplary SCell activation / deactivation MAC CE of 4 octets. A second MAC PDU subheader including a second LCID (e.g., "111001" shown in Figure 19) may indicate / identify the SCell activation / deactivation MAC CE of 4 octets. The SCell activation / deactivation MAC CE of 4 octets may have a fixed size. The SCell activation / deactivation MAC CE of 4 octets may include a third quantity / number C field (e.g., 31 or any other quantity / number) and a fourth quantity / number R field (e.g., 1 or any other quantity / number).

[0180] 21A and / or 21B, the Ci field may indicate an activation / deactivation state of a SCell having / corresponding SCell index i, for example, if the SCell having / corresponding SCell index i is configured. The SCell having SCell index i may be activated, for example, if the Ci field is set to 1. The SCell having SCell index i may be deactivated, for example, if the Ci field is set to zero. The wireless device may ignore the Ci field, for example, if there is no SCell configured with SCell index i. The R field may indicate a reserved bit. The R field may be set to zero or any other value (e.g., for other purposes).

[0181] A base station may configure a wireless device with an uplink (UL) BWP and a downlink (DL) BWP to enable bandwidth adaptation (BA) on a PCell. The base station may further configure the wireless device with at least a DL BWP to enable BA on an SCell, for example, when carrier aggregation is configured (i.e., there may be no UL BWP on the UL). The initial active BWP may be, for example, a first BWP used for initial access for the PCell. The first active BWP may be a second BWP that the wireless device is configured to operate on an SCell when the SCell is activated. The base station and / or the wireless device may individually switch between the DL BWP and the UL BWP, for example, in a paired spectrum (e.g., FDD). The base station and / or the wireless device may simultaneously switch between the DL BWP and the UL BWP, for example, in an unpaired spectrum (e.g., TDD).

[0182] A base station and / or wireless device can switch BWPs between configured BWPs using a DCI message or a BWP inactivity timer. If a BWP inactivity timer is configured for a serving cell, the base station and / or wireless device can switch the active BWP to a default BWP in response to expiration of the BWP inactivity timer associated with the serving cell. The default BWP can be configured by the network. One UL BWP and one DL BWP for an uplink carrier (e.g., each uplink carrier) can be simultaneously active in an active serving cell, for example, in an FDD system configured with BA. One DL / UL BWP pair can be simultaneously active in an active serving cell, for example, in a TDD system. Operating with one UL BWP and one DL BWP (or one DL / UL pair) can improve battery consumption of a wireless device. BWPs other than the one active UL BWP and one active DL BWP on which the wireless device may operate can be deactivated. The wireless device may not, for example, monitor PDCCH transmissions on the deactivated BWPs. The wireless device may not transmit (eg, transmit) on the PUCCH, PRACH, and UL-SCH, eg, on a stopped BWP.

[0183] A serving cell may be configured with up to a first number / amount (e.g., four) of BWPs. At any given time, for example, for an activated serving cell, there may be one active BWP. BWP switching for a serving cell may be used to activate inactive BWPs and deactivate active BWPs at a time. BWP switching may be controlled by a PDCCH transmission indicating a downlink assignment or an uplink grant. BWP switching may be controlled by a BWP inactivity timer (e.g., bwp-InactivityTimer). BWP switching may be controlled by a wireless device (e.g., a MAC entity of the wireless device) based on (e.g., after or in response to) the initiation of a random access procedure. One BWP may be active initially without receiving a PDCCH transmission indicating a downlink assignment or an uplink grant, for example, upon addition of an SpCell or activation of an SCell. The active BWP for a serving cell may be indicated by a configuration parameter (e.g., a parameter of an RRC message) and / or a PDCCH transmission. The DL BWP may be paired with a UL BWP for unpaired spectrum, and the BWP switching may be common for both UL and DL.

[0184] FIG. 22 shows an example of BWP activation / deactivation. BWP activation / deactivation may be on a cell (e.g., a PCell or SCell). BWP activation / deactivation may be associated with BWP switching (e.g., BWP switching may include BWP activation / deactivation). In step 2202, wireless device 2220 may receive (e.g., detect) at least one message (e.g., an RRC message) including cell parameters and one or more BWPs associated with the cell (e.g., from base station 2200). The RRC message may include at least one of an RRC connection reconfiguration message (e.g., RRCReconfiguration), an RRC connection re-establishment message (e.g., RRCRestablishment), and / or an RRC connection setup message (e.g., RRCSetup). Among the one or more BWPs, at least one BWP may be configured as a first active BWP (e.g., BWP1), and one BWP may be configured as a default BWP (e.g., BWP0). The wireless device 2220 may receive (e.g., detect) a command (e.g., an RRC message, a MAC CE, or a DCI message) in step 2204 to activate the cell in the nth slot. The wireless device 2220 may not receive (e.g., detect) a command to activate the cell, e.g., the PCell. The wireless device 2220 may activate the PCell in step 2212, for example, after the wireless device 2220 receives / detects an RRC message including configuration parameters for the PCell. The wireless device 2220 may start monitoring PDCCH transmissions on BWP1 based on (e.g., subsequently to, or in response to) activating the PCell in step 2212.

[0185] Based on (e.g., after or in response to) receiving DCI message 2206 indicating DL allocation on BWP1, wireless device 2220 may start (or restart) a BWP inactivity timer (e.g., bwp-InactivityTimer) at the mth slot in step 2214. Wireless device 2220 may switch to a default BWP (e.g., BWP0) as the active BWP in step 2216, for example, if the BWP inactivity timer expires at the sth slot in step 2208. In step 2210, wireless device 2220 may deactivate the cell and / or deactivate the BWP inactivity timer, for example, if a secondary cell deactivation timer (e.g., sCellDeactivationTimer) expires in step 2210 (e.g., if the cell is an SCell). The wireless device 2220 may not deactivate the cell, eg, may not apply or use a secondary cell deactivation timer (eg, sCellDeactivationTimer) on the PCell based on the cell being a PCell.

[0186] A wireless device (e.g., a MAC entity of the wireless device) may apply or use various operations on an active BWP for an activated serving cell configured in the BWP. The various operations may include at least one of transmitting (e.g., transmitting) on ​​an UL-SCH, transmitting (e.g., transmitting) on ​​a RACH, monitoring a PDCCH transmission, transmitting (e.g., transmitting) a PUCCH, receiving a DL-SCH, and / or (re)initializing configured uplink grants during any temporary deactivation of configured grant type 1, if any, according to a saved configuration.

[0187] The wireless device (e.g., a MAC entity of the wireless device) may not perform certain operations, for example, on an inactive BWP of an activated serving cell (e.g., each activated serving cell) configured with the BWP. The certain operations may include at least one of transmitting (e.g., transmitting) on ​​a UL-SCH, transmitting (e.g., transmitting) on ​​a RACH, monitoring a PDCCH transmission, transmitting (e.g., transmitting) a PUCCH, transmitting (e.g., transmitting) an SRS, or receiving a DL-SCH. The wireless device (e.g., a MAC entity of the wireless device) may clear configured downlink assignments and configured uplink grants of configured grant type 2 and / or temporarily deactivate any configured uplink grants of configured type 1, for example, on an inactive BWP of an activated serving cell (e.g., each activated serving cell) configured with the BWP.

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

[0189] The wireless device may be provided with a higher layer parameter, such as a default DL BWP (e.g., Default-DL-BWP) among the configured DL BWPs for the primary cell, for example. The default DL BWP may be an initial active DL BWP, 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 wireless device may be provided with a higher layer parameter, such as a value of a timer for the primary cell (e.g., bwp-InactivityTimer). The wireless device may increment a timer every 1 millisecond interval for frequency range 1 or every 0.5 milliseconds for frequency range 2 when operating, for example, if the wireless device may not detect DCI format 1_1 for paired spectrum operation, or if the wireless device may not detect DCI format 1_1 or DCI format 0_1 ​​for unpaired spectrum operation during the interval.

[0190] The procedure for a wireless device on a secondary cell may be substantially the same as the procedure on a primary cell, using the timer value of the secondary cell and the default DL BWP of the secondary cell, for example, if the wireless device is configured for the secondary cell with an upper layer parameter (e.g., Default-DL-BWP) indicating a default DL BWP among configured DL BWPs, and the wireless device is configured with an upper layer parameter (e.g., bwp-InactivityTimer) indicating a timer value. The wireless device may use the indicated DL BWP and indicated UL BWP on the secondary cell as the first active DL BWP and first active UL BWP on the secondary cell or carrier, respectively, for example, if the wireless device is configured with an upper layer parameter (e.g., Active-BWP-DL-SCell) associated with a first active DL BWP and an upper layer parameter (e.g., Active-BWP-UL-SCell) associated with a first active UL BWP on the secondary cell or carrier.

[0191] The set of PDCCH candidates for a wireless device to monitor may be referred to as a PDCCH search space set. The search space set may include a CSS set or a USS set. The wireless device may use one or more of the following search space sets: a Type0-PDCCH CSS set configured by pdcch-ConfigSIB1 in MIB, by searchSpaceSIB1 in PDCCH-ConfigCommon, or by searchSpaceZero in PDCCH-ConfigCommon for a DCI format having a CRC scrambled by SI-RNTI in the primary cell of the MCG; a Type0A-PDCCH CSS set configured by searchSpaceOtherSystemInformation in PDCCH-ConfigCommon for a DCI format having a CRC scrambled by SI-RNTI in the primary cell of the MCG; or a Type1-PDCCH CSS set configured by ra-SearchSpace in PDCCH-ConfigCommon for a DCI format having a CRC scrambled by RA-RNTI, MsgB-RNTI, or TC-RNTI in the primary cell. Type2-PDCCH CSS set configured by the pagingSearchSpace in PDCCH-ConfigCommon for DCI formats with CRC scrambled by P-RNTI in the primary cell of the MCG. Type3-PDCCH CSS set configured by the SearchSpace in PDCCH-Config with searchSpaceType=common for DCI formats 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 CS-RNTI in the primary cell.It may monitor PDCCH transmission candidates in the CSS set and the USS set configured by the SearchSpace in PDCCH-Config with searchSpaceType=ue-Specific for DCI formats having a CRC scrambled by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, CS-RNTI, SL-RNTI, SL-CS-RNTI, or SL-L-CS-RNTI.

[0192] The wireless device may determine the PDCCH transmission monitoring opportunity on the active DL BWP based on one or more PDCCH transmission configuration parameters (e.g., as described in connection with FIG. 27 ) including at least one of a PDCCH transmission monitoring period, a PDCCH transmission monitoring offset, or a PDCCH transmission monitoring pattern in a slot. For search space sets (SSs), the wireless device may determine whether the PDCCH transmission monitoring opportunity is

number

number

number

number

number

number

number

number

number

number

[0193] The wireless device may then, for a search space set s associated with CORESETp,

number

number

number

number

number

number

number

number

number

number

number

number

number

number

number

number

number

number

number

number

number

number

number

number

number

number

number

[0194] The wireless device may monitor a set of PDCCH transmission candidates according to configuration parameters of a search space set including multiple search spaces. The wireless device may monitor a set of PDCCH transmission candidates in one or more CORESETs to detect one or more DCI messages. The CORESET may be configured, for example, as described in connection with FIG. 26. The monitoring may include decoding one or more PDCCH transmission candidates in the set of PDCCH transmission candidates according to the monitored DCI format. The monitoring may include decoding DCI content of the one or more PDCCH transmission candidates in possible (or configured) PDCCH transmission locations, possible (or configured) PDCCH transmission formats (e.g., the number / amount of CCEs, the number / amount of PDCCH transmission candidates in a common search space, and / or the number / amount of PDCCH transmission candidates in a wireless device-specific search space (e.g., a UE-specific search space)), and possible (or configured) DCI formats. The decoding may be referred to as blind decoding. The possible DCI formats may be based on the example of FIG. 23.

[0195] FIG. 23 shows examples of various DCI formats. Various DCI formats may be used, for example, by a base station to transmit (e.g., carry) control information for PDCCH transmission monitoring (e.g., to and / or for use by a wireless device). 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 may be used to schedule PUSCH transmissions within a cell. DCI format 0_1 ​​may be used to schedule one or more PUSCH transmissions within a cell or to indicate CG-DFI (Configured Grant Downlink Feedback Information) for configured grant PUSCH transmissions, etc. DCI formats that a wireless device may monitor for reception via a search space may be configured.

[0196] Figure 24A shows an example MIB message. Figure 24A shows example configuration parameters of a MIB for a cell. The cell may be a PCell (or any other cell). The wireless device may receive the MIB via a PBCH. The wireless device may receive the MIB, for example, based on reception of a PSS and / or SSS. The configuration parameters of the MIB may include / indicate SFN (e.g., indicated via the higher layer parameter systemFrameNumber), a subcarrier spacing indication (e.g., indicated via the higher layer parameter subCarrierSpacingCommon), a frequency domain offset between the SSB and the full resource block grid in number of subcarriers (e.g., indicated via the higher layer parameter ssb-SubcarrierOffset), a parameter indicating whether a cell is barred (e.g., indicated via the higher layer parameter cellBarred), a DMRS position indication indicating the location of the DMRS (e.g., indicated via the higher layer parameter dmrs-TypeA-Position), parameters for the search space of CORESET and PDCCH including the common CORESET (e.g., indicated via the higher layer parameter pdcch-ConfigSIB1), the common search space and required PDCCH parameters, etc. Each of the higher layer parameters may be indicated via 1 or a bit. For example, SFN may be indicated using 6 bits (or any other bit amount).

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

[0198] 24B shows an example configuration of CORESET. CORESET may be CORESET0 (or any other CORESET). The wireless device may determine the SSB and CORESET0 multiplexing pattern, the amount / number of RBs in CORESET0, the amount / number of symbols in CORESET0, and the RB offset of CORESET0, for example, based on the value of a first parameter (e.g., controlResourceSetZero).

[0199] The higher layer parameter (e.g., pdcch-ConfigSIB1) may include a second parameter (e.g., searchSpaceZero). The second parameter may indicate a common search space for the initial BWP of the cells. The common search space may be associated with an indicator / index (e.g., 0, or any other indicator). For example, the common search space may be search space 0. The second parameter may be an integer between 0 and 15 (or any other integer). Each integer (e.g., 0 to 15, or any other integer) may identify a configuration of search space 0.

[0200] 24C shows an example configuration of the search space. The search space may be search space 0 (or any other search space). The wireless device may 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 amount / number of search spaces per slot, based on, for example, the value of a second parameter (e.g., searchSpaceZero). For example, for operation without shared spectrum channel access and SS / PBCH block and CORESET multiplexing pattern 1, the wireless device may monitor the PDCCH (e.g., in the Type0-PDCCH CSS set) over two slots. For an SS / PBCH block with index i, the wireless device may determine the index of the slot

number

number

number

number

number

number

number

number

number

number

[0201] The wireless device may monitor the PDCCH for receiving the DCI. The wireless device may monitor search space 0 of CORESET0 for receiving the DCI. The DCI may schedule SIB1. For example, the SIB1 message may be similar to that described in connection with FIG. 25. The wireless device may receive the DCI with a CRC scrambled with the SI-RNTI dedicated to receiving SIB1.

[0202] FIG. 25 shows an example SIB. The SIB may include one or more configuration parameters (e.g., RRC configuration parameters). The SIB (e.g., SIB1) may be transmitted / transmitted to one or more wireless devices. For example, the SIB may be broadcast to multiple wireless devices. The SIB may include information for evaluating / determining whether a wireless device is allowed to access a cell, information on paging configuration, and / or scheduling configuration of other system information. The SIB may include radio resource configuration information that may be common to multiple wireless devices and barring information used / applied for unified access control. The base station may transmit / transmit one or more SIB information messages to a wireless device (or multiple wireless devices). As shown in FIG. 25, parameters of the one or more SIB information messages may include one or more parameters for cell selection related to a serving cell (e.g., cellSelectionInfo), one or more configuration parameters of the serving cell (e.g., ServingCellConfigCommonSIB information element (IE)), and / or one or more other parameters. The ServingCellConfigCommonSIB IE may include at least one of common downlink parameters of the serving cell (e.g., DownlinkConfigCommonSIB IE), common uplink parameters of the serving cell (e.g., UplinkConfigCommonSIB IE), and / or other parameters.

[0203] The DownlinkConfigCommonSIB IE may include parameters of the initial downlink BWP (e.g., indicated via the initialDownlinkBWP IE) of the serving cell (e.g., SpCell). The parameters of the initial downlink BWP may be included in the BWP-DownlinkCommon IE (e.g., as shown in FIG. 26). The BWP-DownlinkCommon IE may be used to configure common parameters of the downlink BWP of the serving cell. The base station may configure parameters (e.g., locationAndBandwidth) such that the initial downlink BWP may include the entire CORESET (e.g., CORESET0) of the serving cell in the frequency domain. The wireless device may use / apply the parameter locationAndBandwidth based on reception of the parameters. The wireless device may use / apply the parameter locationAndBandwidth to determine the frequency location of the signal associated with the frequency indicated via locationAndBandwidth. The wireless device may maintain CORESET0 until after receiving, for example, an RRC setup message (e.g., RRCSetup), an RRC resumption message (e.g., RRCResume), and / or an RRC reestablishment message (e.g., RRCReestablishment).

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

[0205] A parameter (e.g., first-PDCCH-MonitoringOccasionOfPO) may be signaled in SIB1 for paging in an initial DL BWP. The parameter first-PDCCH-MonitoringOccasionOfPO may be signaled in a corresponding BWP configuration, e.g., for paging in a DL BWP other than the initial DL BWP.

[0206] Figure 26 shows example RRC configuration parameters. The configuration parameters may be RRC configuration parameters for the downlink BWP of the serving cell. The configuration parameters may be indicated via the higher layer parameter BWP-DownlinkCommon IE. The base station may send / transmit one or more configuration parameters of the downlink BWP of the serving cell (e.g., the initial downlink BWP) to the wireless device (or multiple wireless devices). The one or more configuration parameters of the downlink BWP may include one or more generic BWP parameters of the downlink BWP, one or more cell-specific parameters of the PDCCH of the downlink BWP (e.g., the pdcch-ConfigCommon IE), one or more cell-specific parameters of the PDSCH of the BWP (e.g., the pdsch-ConfigCommon IE), and / or one or more other parameters. The pdcch-ConfigCommon IE may include a parameter of CORESET0 (e.g., indicated via the parameter controlResourceSetZero) that may be used in any common or wireless device-specific search space. The value of controlResourceSetZero may be interpreted in the same manner as the corresponding bit of the MIB parameter pdcch-ConfigSIB1. The pdcch-ConfigCommon IE may include an additional common control resource set parameter (e.g., commonControlResourceSet) that may be configured and used for any common or wireless device-specific search space. For example, if the network configures a commonControlResourceSet, the network may use a non-zero parameter, ControlResourceSetId, for this ControlResourceSet. The network may configure the commonControlResourceSet in SIB1 such that SIB1 is contained within the bandwidth of CORESET0. The pdcch-ConfigCommon IE may include an additional common search space list parameter (e.g., commonSearchSpaceList). The search space parameters may be implemented based on the example of Figure 27.The pdcch-ConfigCommon IE may indicate, from a list of search spaces, a search space for paging (e.g., via the parameter pagingSearchSpace), a search space for random access procedures (e.g., via the parameter ra-SearchSpace), a search space for SIB1 messages (e.g., via the parameter searchSpaceSIB1), common search space 0 (e.g., via the parameter searchSpaceZero), and / or one or more other search spaces.

[0207] A CORESET may be associated with a CORESET indicator / index (e.g., indicated via the parameter ControlResourceSetId). The CORESET may be implemented based on the examples described in connection with Figures 14A and / or 14B. CORESET index 0 may identify a common CORESET configured in the MIB and ServingCellConfigCommon (e.g., indicated via controlResourceSetZero). CORESET index 0 may not be used in the ControlResourceSet IE. CORESET indexes with other values ​​may identify CORESETs configured by dedicated signaling or in SIB1. controlResourceSetId may be unique within the BWP of the serving cell. A CORESET may be associated with coresetPoolIndex, indicating the index of the CORESET pool of the CORESET. A CORESET may be associated with a duration parameter (e.g., duration), indicating the continuous duration of the CORESET (e.g., in terms of amount / number of symbols). The configuration parameters of the CORESET may include at least one of a frequency resource indication (e.g., frequencyDomainResources), a CCE-REG mapping type indicator (e.g., cce-REG-MappingType), multiple TCI states, and / or an indicator indicating whether a TCI is present in the DCI, etc. The frequency resource indication (e.g., including a quantity / number of bits, such as 45 bits, or any other quantity of bits) may indicate frequency domain resources. Each bit of the frequency resource indication may correspond to a group of RBs (e.g., 6 RBs, or any other quantity of RBs), where the grouping starts from the first RB group in the BWP of a cell (e.g., SpCell, SCell). For example, the first (e.g., leftmost, most significant) bit may correspond to the first RB group in the BWP, and the other bits correspond sequentially to other RB groups. A bit set to 1 may indicate that the RB group corresponding to the bit is included in the frequency domain resources of the CORESET.Bits corresponding to groups of RBs that are not entirely contained in the BWP from which the CORESET is constructed may be set to zero.

[0208] Figure 27 shows an example configuration of a search space. The configuration of the search space may be in a SearchSpace IE. One or more search space configuration parameters of the search space may include at least one of a search space ID (e.g., searchSpaceId), a CORESET indicator (ID) (e.g., controlResourceSetId), a monitoring slot periodicity and offset parameter (e.g., monitoringSlotPeriodicityAndOffset), a search space duration value (e.g., duration), a monitoring symbol indication (e.g., monitoringSymbolsWithinSlot), a quantity / number of aggregation level candidates (e.g., nrofCandidates), and / or a search space type (e.g., searchSpaceType) indicating a common search space type or a wireless device-specific search space type. The monitoring slot periodicity and offset parameter may indicate a slot (e.g., within a radio frame) and a slot offset (e.g., relative to the start of a radio frame) for PDCCH monitoring. The monitoring symbol indication may indicate a symbol of a slot at which the wireless device may monitor the PDCCH on the search space. The control resource set ID may indicate / identify a CORESET in which the search space may be located.

[0209] In an RRC idle state (e.g., RRC_IDLE) or an RRC inactive state (e.g., RRC_INACTIVE), the wireless device may periodically monitor a PO to receive a paging message for the wireless device. In the RRC idle state or the RRC inactive state, and before monitoring the PO, the wireless device may wake up at a time before each PO to prepare and / or activate (e.g., turn on) all components in preparation for data reception (e.g., a warm-up stage). The gap between the wake-up and the PO may be configured to be sufficient to accommodate all processing requirements. After warm-up, the wireless device may perform timing acquisition and coarse synchronization from SSBs, frequency and time tracking, time and frequency offset compensation, and / or local oscillator calibration. After warm-up, the wireless device may monitor the PDCCH for paging DCI via one or more PDCCH monitoring opportunities. The wireless device may monitor the PDCCH, for example, based on configuration parameters of the PCCH configuration (e.g., configured in SIB1). The configuration parameters of the PCCH configuration may be as described in connection with FIG.

[0210] FIG. 28 illustrates exemplary cell dormancy management. The cell dormancy management may include a transition between a dormant state and a non-dormant state. An exemplary transition may be for operation on an SCell. The base station may send / transmit one or more RRC messages to the wireless device. The one or more RRC messages may include configuration parameters for the SCell. The SCell may include multiple BWPs. Among the multiple BWPs, a first BWP (e.g., BWP3) may be configured as a non-dormant BWP and / or a second BWP (e.g., BWP1) may be configured as a dormant BWP. A default BWP (e.g., BWP0) may be configured with multiple BWPs. A non-dormant BWP may be a BWP that the wireless device may activate, for example, based on / in response to transitioning the SCell from a dormant state to a non-dormant state. A dormant BWP may be a BWP that the wireless device may switch to based on / in response to transitioning the SCell from a non-dormant state to a dormant state. The configuration parameters may indicate one or more search spaces and / or CORESETs configured on the non-dormant BWP. The configuration parameters may indicate no search space or no CORESET for the dormant BWP. The configuration parameters may indicate CSI reporting configuration parameters for the dormant BWP.

[0211] The active BWP of the SCell may be a dormant BWP, a non-dormant BWP, or a default BWP. The default BWP may differ from the dormant BWP. The configuration parameters may indicate one or more search spaces and / or one or more CORESETs configured on the default BWP. The wireless device may switch to the default BWP as the active BWP, for example, when a BWP inactivity timer expires or based on receiving a DCI indicating switching to the default BWP. The wireless device may perform at least one of monitoring a PDCCH on the default BWP of the SCell, receiving a PDSCH transmission via the default BWP of the SCell, transmitting a PUSCH transmission via the default BWP of the SCell, transmitting an SRS via the default BWP of the SCell, and / or transmitting a CSI report to the default BWP of the SCell (e.g., in a periodic, aperiodic, and / or semi-persistent manner) (e.g., when the default BWP is the active BWP). The wireless device may switch to a dormant BWP as the active BWP of the SCell, for example, when receiving a dormant / non-dormant indication indicating a dormant state of the SCell. The wireless device may (e.g., based on / in response to switching to the dormant BWP) perform at least one of: refrain from monitoring a PDCCH on the dormant BWP of the SCell (or for the SCell if the SCell is cross-carrier scheduled by another cell), refrain from receiving a PDSCH transmission over the dormant BWP of the SCell, refrain from transmitting a PUSCH transmission over the dormant BWP of the SCell, refrain from transmitting an SRS over the dormant BWP of the SCell, and / or transmit a CSI report (e.g., periodic, aperiodic, and / or semi-persistent CSI report) for the dormant BWP of the SCell.

[0212] The base station may transmit / transmit a DCI to the wireless device via PDCCH resources. The DCI may include a dormant / non-dormant indication indicating a dormant or non-dormant state of the SCell. The wireless device may transition the SCell to a dormant state (e.g., if the SCell is in a non-dormant state before receiving the DCI) or maintain the SCell in a dormant state (e.g., if the SCell is in a dormant state before receiving the DCI) (e.g., based on the dormant / non-dormant indication indicating the dormant state of the SCell). Transitioning the SCell to a dormant state may include switching to a dormant BWP (e.g., configured by the base station) for the SCell. The wireless device may transition the SCell to a non-dormant state (e.g., if the SCell is in a dormant state before receiving the DCI) or maintain the SCell in a non-dormant state (e.g., if the SCell is in a non-dormant state before receiving the DCI) (e.g., based on the dormant / non-dormant indication indicating the non-dormant state of the SCell). Transitioning the SCell to a non-dormant state may include switching to a non-dormant BWP (e.g., configured by the base station) for the SCell.

[0213] The wireless device may switch to a non-dormant BWP (e.g., BWP3) configured by the base station as the active BWP for the SCell, for example, based on transitioning the SCell from a dormant state to a non-dormant state. The wireless device may monitor a PDCCH on the active BWP for the SCell (or monitor a PDCCH for the SCell if the SCell is configured to be cross-carrier scheduled by another cell), receive a PDSCH transmission via the active BWP for the SCell, and / or perform at least one of a PUCCH transmission, a PUSCH transmission, a RACH transmission, and / or an SRS transmission via the active BWP (e.g., if the active BWP is an uplink BWP) (e.g., based on switching to a non-dormant BWP as the active BWP for the SCell).

[0214] The wireless device may switch to a dormant BWP (e.g., BWP1 for the SCell) configured by the base station, for example, based on transitioning the SCell from a non-dormant state to a dormant state. The wireless device may perform at least one of the following (e.g., based on switching to the dormant BWP for the SCell): refrain from monitoring a PDCCH on the dormant BWP for the SCell (or refrain from monitoring a PDCCH for the SCell if the SCell is configured to be cross-carrier scheduled by another cell), refrain from receiving a PDSCH transmission via the dormant BWP for the SCell, refrain from sending a PUCCH transmission, a PUSCH transmission, a RACH transmission, and / or an SRS transmission via the dormant BWP (e.g., if the dormant BWP is an uplink BWP), and / or send a CSI report for the dormant BWP for the SCell (e.g., based on a CSI report configuration parameter configured on the dormant BWP for the SCell).

[0215] DRX operation may be used by a wireless device to improve the battery life of the wireless device. When DRX is configured, the wireless device may discontinuously monitor a downlink control channel, e.g., a PDCCH or EPDCCH. A base station may configure DRX operation with a set of DRX parameters, e.g., using an RRC configuration. The set of DRX parameters may be selected based on an application type so that the wireless device may reduce power and resource consumption. The wireless device may receive data packets with an extended delay because the wireless device may be in a DRX sleep / off state upon data arrival at the wireless device and the base station may wait until the wireless device transitions to a DRX on state based on (e.g., after or in response to) DRX being configured / activated.

[0216] When in DRX mode, the wireless device may power down most of its circuitry, for example, when there are no packets to be received. The wireless device may discontinuously monitor the PDCCH in DRX mode. The wireless device may continuously monitor the PDCCH, for example, if DRX operation is not configured. At this point, the wireless device listens to the downlink (DL) (or monitors the PDCCH), which is referred to as the DRX active state. In DRX mode, the time when the wireless device is not listening / monitoring the PDCCH is referred to as the DRX sleep state.

[0217] FIG. 29 shows an example of a DRX configuration of a wireless device. The base station may 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 a DRX active state (e.g., DRX on duration) of the DRX cycle. The second parameter may indicate a second time for a DRX sleep state (e.g., DRX off duration) of the DRX cycle. The one or more parameters may further include a duration of the DRX cycle. In the DRX active state, the wireless device may monitor the PDCCH to detect one or more DCIs on the serving cell. In the DRX sleep state, the wireless device may deactivate monitoring the PDCCH on the serving cell. The wireless device may monitor all PDCCHs on (or for) multiple cells for the DRX active state, for example, when multiple cells are in the active state. During the DRX off duration, the wireless device may deactivate monitoring all PDCCHs on (or for) multiple cells. The wireless device may repeat DRX operations according to one or more DRX parameters.

[0218] DRX may be beneficial to a base station. For example, if DRX is not configured, a wireless device may transmit (e.g., transmit) periodic CSI and / or SRS frequently (e.g., based on a configuration). With DRX, during DRX-off periods, a wireless device may not transmit (e.g., transmit) periodic CSI and / or SRS. The base station may allocate these resources to other wireless devices to improve resource utilization efficiency.

[0219] The MAC entity may be configured by RRC with a DRX function that controls the wireless device's downlink control channel (e.g., PDCCH) monitoring activity for multiple RNTIs for the MAC entity. The multiple RNTIs may include at least one of a C-RNTI, a CS-RNTI, an INT-RNTI, a SP-CSI-RNTI, an SFI-RNTI, a TPC-PUCCH-RNTI, a TPC-PUSCH-RNTI, a semi-persistent scheduling C-RNTI, an eIMTA-RNTI, an SL-RNTI, an SL-V-RNTI, a CC-RNTI, or an SRS-TPC-RNTI. The MAC entity may discontinuously monitor the PDCCH using DRX operation (e.g., if DRX is configured), e.g., based on being RRC_CONNECTED; otherwise, the MAC entity may continuously monitor the PDCCH.

[0220] The RRC may control the DRX operation by configuring multiple timers. The multiple 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 of a short DRX configuration (e.g., drx-ShortCycle and / or drx-ShortCycleTimer), and one or more parameters of a long DRX configuration (e.g., drx-LongCycle). The time granularity of the DRX timers may be in units of PDCCH subframes (e.g., denoted as psf in the DRX configuration) and / or in units of milliseconds.

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

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

[0223] The active time may include the time when a scheduling request is transmitted on the PUCCH and is pending, e.g., based on (e.g., thereafter or in response to) a DRX cycle being configured. Based on (e.g., thereafter or in response to) a DRX cycle being configured, the active time may include the time when an uplink grant for a pending HARQ retransmission may occur and data is present in the corresponding HARQ buffer for a synchronous HARQ process. The active time may include the time when, e.g., based on (e.g., based on) a DRX cycle being configured, the PDCCH may indicate that no new transmissions addressed to the C-RNTI of the MAC entity have been received after successful reception of a random access response to a preamble not selected by the MAC entity.

[0224] A timer such as a DL HARQ RTT timer (e.g., drx-HARQ-RTT-TimerDL) may expire in a subframe, and data for the corresponding HARQ process may not be successfully decoded. The MAC entity may start a timer (e.g., drx-RetransmissionTimerDL) for the corresponding HARQ process. A UL HARQ RTT timer (e.g., drx-HARQ-RTT-TimerUL) may expire in a subframe. The MAC entity may start a timer (e.g., drx-RetransmissionTimerUL) for the corresponding HARQ process.

[0225] A wireless device may receive a DRX command MAC CE and / or a long DRX command MAC CE (e.g., based on the example described herein with respect to FIG. 19). A MAC entity of the wireless device may, for example, deactivate a timer (e.g., drx-onDurationTimer) and / or deactivate another timer (e.g., drx-InactivityTimer) based on receiving the DRX command MAC CE and / or the long DRX command MAC CE. The MAC entity may start or restart a timer (e.g., drx-ShortCycleTimer) and / or use a cycle (e.g., a short DRX cycle), for example, when an inactivity timer (e.g., drx-InactivityTimer) expires and / or if a cycle is configured. For example, the MAC entity may use a cycle (e.g., a long DRX cycle).

[0226] A timer (e.g., drx-ShortCycleTimer) may expire in a subframe. The MAC entity may use a cycle (e.g., a long DRX cycle). A long DRX command MAC Control element may be received. The MAC entity may deactivate the timer (e.g., drx-ShortCycleTimer) and use a long DRX cycle.

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

[0228] 30 shows an example of a DRX configuration for a wireless device. The base station may send (e.g., transmit) an RRC message including configuration parameters for DRX operation. The configuration parameters may include a first timer value of a DRX inactivity timer (e.g., drx-InactivityTimer), a second timer value of a HARQ RTT timer (e.g., drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL), and a third timer value of a HARQ retransmission timer (e.g., drx-RetransmissionTimerDL and / or drx-RetransmissionTimerUL).

[0229] The base station may send (e.g., transmit) a DCI (e.g., a first DCI) including a downlink allocation for the TB to the wireless device via the PDCCH (as shown in FIG. 30). The wireless device may start a drx-InactivityTimer, for example, based on (e.g., subsequently or in response to) receiving the DCI. The wireless device may monitor the PDCCH, for example, for the execution of a timer (e.g., the drx-InactivityTimer). The wireless device may receive the TB based on receiving the DCI. If the wireless device fails to decode the TB, it may send (e.g., transmit) a NACK to the base station. The wireless device may start a HARQ RTT timer (e.g., drx-HARQ-RTT-TimerDL) at the first symbol after finishing sending (e.g., transmitting) the NACK. The wireless device may deactivate a retransmission timer (e.g., drx-RetransmissionTimerDL) for the HARQ process corresponding to the TB. The wireless device may deactivate monitoring the PDCCH for one or more RNTIs affected by the DRX operation, e.g., for running a HARQ RTT timer. The one or more RNTIs may include a C-RNTI, a CI-RNTI, a CS-RNTI, an INT-RNTI, an SFI-RNTI, a SP-CSI-RNTI, a TPC-PUCCH-RNTI, a TPC-PUSCH-RNTI, a TPC-SRS-RNTI, and / or an AI-RNTI.

[0230] The wireless device may monitor the PDCCH and start the HARQ retransmission timer (e.g., drx-RetransmissionTimerDL), for example, when the HARQ RTT timer expires (as shown in FIG. 30). To monitor the PDCCH, the wireless device may receive a second DCI (e.g., the second DCI in FIG. 30) that schedules a retransmission of the TB, for example, when the HARQ retransmission timer is running. The wireless device may deactivate monitoring the PDCCH, for example, when it does not receive the second DCI (e.g., before the HARQ retransmission timer expires).

[0231] FIG. 31A illustrates an example power save operation of a wireless device. The example power save operation of FIG. 31A may be based on a wake-up instruction. The base station may send / transmit one or more messages to the wireless device including a parameter for a wake-up duration (e.g., a power save duration or a power save channel (PSCH) opportunity). The wake-up duration may be located (e.g., starts) at a time that is an amount / number of slots (or symbols) before the DRX on duration of the DRX cycle. The amount / number of slots (or symbols) may be a gap between the wake-up duration and the DRX on duration. The DRX cycle may be implemented based on an example such as that described in connection with FIG. 29. The amount of slots may be configured in one or more RRC messages or may be predefined as a fixed value. The gap may be used for at least one of synchronization with the base station, measuring a reference signal, and / or retuning RF parameters. The gap may be determined based on the capabilities of the wireless device and / or the base station. The parameter for the wake-up duration may be predefined without RRC configuration. The wake-up mechanism may be based on a wake-up indication (e.g., via PSCH). The wake-up duration parameter may include at least one of a PSCH channel format (e.g., numerology, DCI format, PDCCH format), a PSCH periodicity, a control resource set, and / or a search space of the PSCH. For example, when configured with the wake-up duration parameter, the wireless device may monitor the PSCH to receive a wake-up signal during the wake-up duration. For example, when configured with the PSCH opportunity parameter, the wireless device may monitor the PSCH to detect a wake-up indication during the PSCH opportunity / wake-up duration. For example, based on / in response to receiving a wake-up signal / channel (or a wake-up indication via PSCH), the wireless device may wake up to monitor the PDCCH in a DRX active time (e.g., including the DRX on duration) of the next DRX cycle according to the DRX configuration.The wireless device may monitor the PDCCH during the DRX active time (e.g., when the drx-onDurationTimer is running), e.g., based on / in response to receiving a wake-up indication via the PSCH. The wireless device may return to sleep if the wireless device does not receive a PDCCH transmission during the DRX active time. The wireless device may remain in the sleep state during the DRX off duration of the DRX cycle. The wireless device may skip monitoring the PDCCH during the DRX active time, for example, if the wireless device does not receive a wake-up signal / channel (or a wake-up indication via the PSCH) during the wake-up duration (or PSCH opportunity). The wireless device may skip monitoring the PDCCH during the DRX active time, for example, if the wireless device receives an indication indicating to skip PDCCH monitoring during the wake-up duration (or PSCH opportunity).

[0232] Figure 31B shows example power saving operations of a wireless device. The power saving operations of Figure 31B may be based on an instruction to go to sleep. The wireless device may return to sleep and skip monitoring the PDCCH during the DRX active time (e.g., during the next DRX on duration of a DRX cycle) based on / in response to receiving an instruction to go to sleep, for example, via the PSCH. The wireless device may monitor the PDCCH during the DRX active time in accordance with configuration parameters of the DRX operation, for example, if the wireless device does not receive an instruction to go to sleep via the PSCH during the wake-up duration. The power saving mechanisms of Figures 31A and 31B may reduce power consumption for PDCCH monitoring during the DRX active time.

[0233] The power save operation may be based on combining the operations described in connection with Figures 31A and 31B. The base station may transmit / transmit a power save indication in a DCI via a PSCH indicating whether the wireless device will wake up for the next DRX on duration or may skip the next DRX on duration. The wireless device may receive the DCI via the PSCH. The wireless device may wake up for the next DRX on duration, for example, based on / in response to a power save indication indicating that the wireless device may wake up for the next DRX on duration. In response to waking up, the wireless device may monitor the PDCCH for the next DRX on duration. The wireless device may go to sleep for the next DRX on duration or skip the next DRX on duration, for example, based on / in response to a power save indication indicating that the wireless device may skip (or go to sleep) for the next DRX on duration. The wireless device may skip monitoring the PDCCH for the next DRX on duration, for example, based on / in response to a power save indication indicating that the wireless device should go to sleep for the next DRX on duration. The various examples described in connection with Figures 30, 31A, and / or 31B may be extended and / or combined to further improve power consumption of wireless devices and / or signaling overhead of base stations.

[0234] FIG. 32A illustrates an example of SSSG switching for power saving of a wireless device. The example of FIG. 32A may include an exemplary DCI format. The DCI format may correspond to DCI format 2_0 and may include one or more search space set group (or SSSG) switch indications (or SSSG switch flags). DCI format 2_0 may include one or more slot format indicators (e.g., slot format indicator 1, slot format indicator 2, ... slot format indicator N), one or more available RB set indicators, one or more channel occupation time (COT) duration indications, and / or one or more SSSG switch flags. Each of the one or more SSSG switch flags may correspond to a respective cell group of a plurality of cell groups. Each cell group of the plurality of cell groups may include one or more cells. An SSSG switch flag among the one or more SSSG switch flags corresponding to a cell group may indicate a switch from a first SSSG to a second SSSG for each cell of the cell group, for example, when the SSSG switch flag is set to a first value. The SSSG switch flag may indicate a switch from the second SSSG to the first SSSG for each cell of the cell group, for example, when the SSSG switch flag is set to a second value.

[0235] 32B illustrates an example of SSSG switching for power saving of a wireless device. The SSSG switching may be based on DCI (e.g., corresponding to DCI format 2_0 or other DCI formats described in connection with FIG. 23). A wireless device 3004 may receive a configuration 3006 of an SSSG for a BWP of a cell. The configuration 3006 may include multiple parameters. The configuration 3006 may be via RRC messaging and / or SIB1 messaging.

[0236] The wireless device 3004 may be provided / indicated a group indicator / index of a search space set (e.g., a Type3-PDCCH CSS set, a USS set, or any other type of search space set) by a parameter for PDCCH monitoring on the serving cell (e.g., searchSpaceGroupIdList, as described in connection with FIG. 27).

[0237] The wireless device 3004 may or may not be provided / indicated the search space set parameter searchSpaceGroupIdList. The SSSG switching described in connection with FIG. 32B may not be applicable to PDCCH monitoring on a search space, for example, if the search space set is not configured in searchSpaceGroupIdList. The wireless device 3004 may monitor the search space set on the BWP without switching from the search space set for PDCCH monitoring, for example, if the search space set is not configured in searchSpaceGroupIdList.

[0238] The SSSG switching illustrated in FIG. 32B may use / apply all serving cells in each group, for example, if the wireless device 3004 is provided / indicated with a parameter cellGroupsForSwitchList indicating one or more groups of serving cells (e.g., as described in connection with FIG. 26). The SSSG switching described in connection with FIG. 32B may use / apply only serving cells for which the wireless device 3004 is provided / indicated with the parameter searchSpaceGroupIdList, for example, if the wireless device 3004 is not provided / indicated with the parameter cellGroupsForSwitchList. The wireless device 3004 may reset PDCCH monitoring according to a search space set having a particular group index (e.g., group index 0) if the wireless device 3004 is provided / indicated with the parameter searchSpaceGroupIdList.

[0239] The wireless device 3004 may select a certain quantity / number of symbols based on the wireless device processing capability (e.g., wireless device processing capability 1, wireless device processing capability 2, etc.) and the subcarrier spacing (SCS) configuration μ.

number

number

number

number

number

number

number

[0240] The wireless device 3004 may be provided / indicated with the parameter searchSpaceSwitchTimer (in units of slots, e.g., as shown in FIG. 26). The parameter searchSpaceSwitchTimer may include a timer value for a serving cell for which the wireless device 3004 is provided with the parameter searchSpaceGroupIdList, or may be for a set of serving cells indicated by the parameter cellGroupsForSwitchList (e.g., if provided). The wireless device 3004 may decrement the timer value by 1 after each slot based on a reference SCS configuration μ, which is the smallest SCS configuration μ among all configured downlink BWPs in the serving cell or set of serving cells. The wireless device 3004 may maintain the reference SCS configuration during the timer decrement procedure.

[0241] The parameter searchSpaceSwitchTimer may be defined as a slot-based value. The parameter searchSpaceSwitchTimer may indicate the duration for monitoring the PDCCH in the active downlink BWP of the serving cell before moving to the default search space group (e.g., search space group 0). The timer value may be based on the SCS. For example, if the SCS is 15 kHz, a valid timer value may be one of {1, ..., 20}. For example, if the SCS is 30 kHz, a valid timer value may be one of {1, ..., 40}. For example, if the SCS is 60 kHz, a valid timer value may be one of {1, ..., 80}. The base station may configure the same timer value for all serving cells in the same cell group, as indicated by the parameter CellGroupForSwitch.

[0242] The wireless device 3004 may monitor the PDCCH on a first SSSG (e.g., a search space set with group index 0) based on the configuration of the SSSG of the cell's BWP (e.g., via configuration 3006) (e.g., step 3012). The wireless device 3004 may be provided / indicated with a SearchSpaceSwitchTrigger that indicates the location of the serving cell's SSSG switch flag field present in the DCI (e.g., a DCI corresponding to DCI format 2_0). The parameter SearchSpaceSwitchTrigger may be configured as shown in FIG. 27.

[0243] The wireless device 3004 may receive a DCI 3008 (e.g., having DCI format 2_0). The DCI 3008 may indicate an SSSG switch for the cell, for example, if the value of an SSSG switch flag field in the DCI 3008 is 1 (or any other predefined value). The wireless device 3004 may switch to a second SSSG for PDCCH monitoring (e.g., step 3014). The wireless device 3004 may start monitoring the PDCCH on the second SSSG (e.g., search space set with group index 1) and deactivate monitoring the PDCCH on the first SSSG (or search space set with group index 0) for the serving cell. The wireless device 3004 may start monitoring the PDCCH on the second SSSG (e.g., search space set with group index 1) and deactivate monitoring the PDCCH on the first SSSG (or search space set with group index 0) for the serving cell for at least 10 seconds after the last symbol of the PDCCH that includes the DCI.

number

[0244] The wireless device 3004 may monitor the PDCCH on a second SSSG (e.g., a search space set with group index 1) based on the SSSG configuration of the cell's BWP. The wireless device 3004 may be indicated the location of the serving cell's SSSG switch flag field in the DCI (e.g., corresponding to DCI format 2_0) via a parameter SearchSpaceSwitchTrigger. The wireless device 3004 may receive the DCI. The DCI may indicate an SSSG switch for the cell, for example, if the value of the SSSG switch flag field in the DCI is 0. The wireless device 3004 may start monitoring the PDCCH on the search space set with group index 0 and deactivate monitoring the PDCCH on the serving cell's search space set with group index 1, for example, if the value of the SSSG switch flag field in the DCI is 0. The wireless device 3004 may start monitoring the PDCCH on the search space set with group index 0 and deactivate monitoring the PDCCH on the serving cell's search space set with group index 1 for at least 1 symbol after the last symbol of the PDCCH including the DCI.

number

[0245] The wireless device 3004 may, for example, start monitoring the PDCCH for the serving cell on the second SSSG (e.g., search space set with group index 1) and deactivate monitoring the PDCCH on the first SSSG (e.g., search space set with group index 0) if the wireless device 3004 initially monitors the PDCCH for the serving cell on the first SSSG. The wireless device 3004 may deactivate monitoring the PDCCH on the first SSSG (e.g., search space set with group index 0) at least one slot after the timer expires or after the last symbol of the remaining channel occupancy period of the serving cell (e.g., as indicated by DCI 3008).

number

[0246] The wireless device 3004 may be provided / indicated with the parameter SearchSpaceSwitchTrigger for the serving cell, or may not be provided / indicated. For example, the parameter SearchSpaceSwitchTrigger may not be present in a configuration parameter corresponding to SlotFormatIndicator (e.g., SlotFormatIndicator is configured to monitor a group-common PDCCH in Slot-Format-Indicators (SFI)). The DCI 3008 (e.g., corresponding to DCI format 2_0) may not include an SSSG switch flag field, for example, based on the parameter SearchSpaceSwitchTrigger not being provided. The wireless device 3004 may start monitoring the PDCCH on a second SSSG (e.g., a search space set with group index 1) and deactivate monitoring the PDCCH according to the first SSSG (e.g., a search space set with group index 0) for the serving cell, for example, if the parameter SearchSpaceSwitchTrigger is not provided and the wireless device 3004 detects a DCI based on monitoring the PDCCH on the first SSSG. The wireless device 3004 begins monitoring the PDCCH on the second SSSG and receives at least one PDCCH symbol after the last symbol of the PDCCH that contains DCI.

number

[0247] The wireless device 3004 may be provided / indicated with the parameter SearchSpaceSwitchTrigger for the serving cell, or may not be provided / indicated. The wireless device 3004 may, for example, start monitoring the PDCCH for the serving cell according to the second SSSG (e.g., search space set with group index 1) and deactivate monitoring the PDCCH according to the first SSSG (e.g., search space set with group index 0) for the serving cell if the parameter SearchSpaceSwitchTrigger is not provided and the wireless device 3004 initially monitors the PDCCH for the serving cell according to the first SSSG. The wireless device 3004 may start monitoring the PDCCH for the serving cell according to the second SSSG and deactivate monitoring the PDCCH according to the first SSSG (e.g., search space set with group index 0) for at least one slot after the timer expires.

number

[0248] The wireless device 3004 may switch back to the first SSSG for PDCCH monitoring (e.g., step 3016), for example, based on / after expiration of a timer. The wireless device 3004 may start monitoring the PDCCH on the first SSSG and deactivate monitoring the PDCCH on the second SSSG, for example, based on expiration of a timer. The wireless device 3004 may receive a second DCI 3010 based on the PDCCH monitoring. The second DCI 3010 may schedule a TB via a PDSCH. The wireless device 3004 may receive a TB via the PDSCH and based on the scheduling indicated via the second DCI 3010 (e.g., step 3018).

[0249] The wireless device 3004 may determine the slot and symbol within the slot to start or deactivate PDCCH monitoring on the search space set of serving cells for which the wireless device 3004 provides / indicates the parameter searchSpaceGroupIdList. The wireless device 3004 may start or deactivate PDCCH monitoring on the search space set of serving cells if the parameter cellGroupsForSwitchList is provided / indicated for the set of serving cells based on the smallest SCS configuration μ among all configured downlink BWPs. A downlink BWP may exist in the serving cell or set of serving cells, and if present, may exist in the serving cell for which the wireless device 3004 receives a PDCCH transmission and detects the corresponding DCI format 2_0 (e.g., triggering start or stop of PDCCH monitoring on the search space set).

[0250] FIG. 33 illustrates example PDCCH skipping for power saving of a wireless device. A base station 3302 may send / transmit one or more RRC messages including configuration parameters 3306 to a wireless device 3304. The configuration parameters 3306 may be for a PDCCH for a BWP of the cell (e.g., as described in connection with FIG. 26 and / or FIG. 27). The wireless device 3304 may, for example, monitor the PDCCH on the BWP based on the PDCCH configuration parameters 3306. The BWP may be a downlink BWP that may be in an active state. The wireless device 3304 may activate the BWP as described in connection with FIG. 22.

[0251] The wireless device 3304 may receive a first DCI 3308 indicating to skip (e.g., monitor / receive via) the PDCCH within a time window 3316. The time value (e.g., duration) of the time window 3316 may be indicated by the first DCI 3308 or configured by one or more RRC messages. The wireless device 3304 may stop monitoring the PDCCH over the BWP, for example, based on / in response to receiving the first DCI 3308. Stopping monitoring the PDCCH over the BWP may include stopping monitoring the PDCCH over one or more SSSGs configured over the BWP. The wireless device 3304 may maintain an active state of the BWP. The first DCI 3308 may not indicate an active BWP switch. The base station 3302 may, for example, not transmit / transmit a PDCCH transmission to the wireless device 3304 during / during the time window 3316 (or when a timer associated with the time window 3316 is running).

[0252] The wireless device 3304 may resume PDCCH monitoring over the BWP, e.g., based on / after expiration of the time window 3316. The wireless device 3304 may receive a second DCI 3312 scheduling a TB over a PDSCH, e.g., based on resuming PDCCH monitoring. The wireless device 3304 may receive a TB over a PDSCH scheduled by the second DCI 3312. The base station 3302 may send / transmit the second DCI 3312 to the wireless device 3304, e.g., based on / in response to expiration of the time window 3316.

[0253] A base station may transmit / transmit one or more SSBs to a wireless device or multiple wireless devices (e.g., periodically). A wireless device (in an RRC idle state, an RRC inactive state, or an RRC connected state) may use one or more SSBs for time and frequency synchronization with the base station's cell. SSBs including PSS, SSS, PBCH, and / or PBCH DM-RS may be transmitted / transmitted (e.g., as described in connection with FIG. 11A). An SSB may occupy a certain amount / number (e.g., four, or any other amount) of OFDM symbols. A base station may transmit / transmit one or more SSBs in an SSB burst (e.g., to enable beam sweeping for PSS / SSS and PBCH). An SSB burst may include a set of SSBs, with each SSB potentially transmitted via a corresponding different beam. In an SSB burst, the SSBs may be transmitted using time division multiplexing. An SSB burst may be within a time window (e.g., a 5 ms window, or a window of any other duration) and may be located in either the first or second half of a radio frame (e.g., having a duration of 10 ms, or any other duration). An SSB burst may be equivalently referred to as a transmission window (e.g., 5 ms, or any other duration) in which a set of SSBs is transmitted.

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

[0255] Figure 34 shows an example of an SSB configuration. Figure 34 shows an example table for determining the starting OFDM symbol index of a candidate SSB. The OFDM starting symbol can be determined as a function of the SCS and carrier frequency. For example, the starting OFDM symbol index of an SSB in an SSB burst can be determined for a 15 kHz SCS and carrier frequency f c <3GHz (e.g., L max = 4), the starting OFDM symbol index for the SSB in an SSB burst can be 2, 8, 16, and 22. The OFDM symbols within a half frame can be indexed with the first symbol of the first slot being indexed as 0. The starting OFDM symbol index for the SSB in an SSB burst can be 15 kHz and a carrier frequency of 3 GHz. <f c <6GHz(L max= 8), the starting OFDM symbol indexes can be 2, 8, 16, 22, 30, 36, 44, and 50. The starting OFDM symbol indexes for other SCSs and carrier frequencies can be determined similarly according to the table shown in Figure 34. A base station can transmit / transmit only one SSB by using the first SSB starting position, for example, if the base station is not transmitting the SSB with beamforming.

[0256] Figure 35 shows an example of a base station's SSB transmission. The SCS of the cell may be 15 kHz, and the cell may be 3 GHz. <f c Carrier frequency f<=6GHz c The maximum amount of candidate SSBs in an SSB burst can be configured using, for example, f c Based on the value of 8(L max = 8). The starting symbol of an SSB transmission may be determined according to the table shown in Figure 34. SSB #1 may start at symbol 2 (of the 70 symbols contained in a 5 ms half-frame), SSB #2 may start at symbol #8, SSB #3 may start at symbol #16, SSB #4 may start at symbol #22, SSB #5 may start at symbol #30, SSB #6 may start at symbol #36, SSB #7 may start at symbol #44, and SSB #8 may start at symbol #50. SSB bursts may be transmitted in the first half (and not the second half) of a radio frame (which has a duration of 10 ms).

[0257] An SSB burst (and each SSB in an SSB burst) may be transmitted / transmitted with periodicity. The default periodicity of an SSB burst may be 20 ms (e.g., as shown in FIG. 35, or any other duration). The default transmission periodicity may be, for example, the periodicity before a wireless device can receive an SIB1 message for initial access of a cell. For example, a base station may transmit / transmit an SSB burst in the first 5 ms of each 20 ms period with a transmission periodicity of 20 ms for an SSB (or SSB burst). The base station may not transmit / transmit an SSB burst in the remaining 15 ms of each 20 ms period.

[0258] The base station may send / transmit an RRC message (e.g., SIB1 message) indicating cell-specific configuration parameters for SSB transmission. The cell-specific configuration parameters may include values ​​for the transmission periodicity of the SSB burst (e.g., parameter ssb-PeriodicityServingCell) and the location (e.g., presence) of an SSB (e.g., active SSB) among multiple candidate SSBs within the SSB burst. The multiple candidate SSBs (e.g., starting symbols of the candidate SSBs) may be determined as described in connection with Figure 34. The cell-specific configuration parameters may include a position indication of the SSB within the SSB burst (e.g., parameter ssb-PositionsInBurst). The position indication may include a first bitmap (e.g., groupPresence) and a second bitmap (e.g., inOneGroup) indicating the location / presence of the SSB in the SSB burst.

[0259] Carrier frequency f c The SCS may determine the maximum amount of candidate SSBs in an SSB burst (e.g., as described in connection with FIG. 34). A position indication (e.g., parameter ssb-PositionsInBurst) may indicate an SSB (e.g., active SSB, position of active SSB) among multiple candidate SSBs to be transmitted / transmitted in an SSB burst (e.g., as further described in connection with FIG. 36). The base station may use the position indication (e.g., parameter ssb-PositionsInBurst) to indicate the active SSBs and / or the amount of active SSBs transmitted in an SSB burst. The position indication may be transmitted by the base station, for example, via an RRC message and / or DCI.

[0260] FIG. 36 shows an example of a base station's SSB transmission. The SSB location indication may be in the form of an indication of the presence of an SSB group among multiple SSB groups. Each group may contain a subset of multiple candidate SSBs in an SSB burst (e.g., the maximum possible amount of candidate SSBs). For example, the maximum possible amount of candidate SSBs in an SSB burst may be equal to 64 (e.g., SCS=120 kHz or 240 kHz, and f c >6 GHz). The candidate SSBs within an SSB burst may include SSBs with indices 0 to 63. The candidate SSBs within an SSB burst may be divided into SSB groups.

[0261] The first bitmap (e.g., parameter groupPresence) may include a certain amount of bits (e.g., 8, or any other amount). The first bitmap may be configured / indicated by the SIB1 message. Each bit of the first bitmap may correspond to a respective one of the SSB groups. As shown in Figure 36, the first bit (e.g., the leftmost bit of the first bitmap) may correspond to the first SSB group including the first SSB (having SSB index 0), the second SSB (having SSB index 1), ..., and the eighth SSB (having SSB index 7). The second bit (e.g., the second bit of the first bitmap) may correspond to the second SSB group including the ninth SSB (having SSB index 8), the tenth SSB (having SSB index 9), ..., and the sixteenth SSB (having SSB index 15). The last bit (e.g., the rightmost bit of the first bitmap) may correspond to an eighth SSB group, which includes the 57th SSB (having SSB index 56), the 58th SSB (having SSB index 57), ..., and the 64th SSB (having SSB index 63), etc. An SSB may belong to / correspond to at most one SSB group from the first SSB group. A bit of the first bitmap may indicate whether the base station may transmit / transmit the SSB group corresponding to the bit in an SSB burst. A bit set to a first value (e.g., 1) may indicate that the corresponding SSB group may be transmitted / transmitted by the base station in an SSB burst. A bit set to a second value (e.g., 0) may indicate that the corresponding SSB group is not transmitted / transmitted by the base station in an SSB burst, or vice versa.

[0262] The second bitmap (e.g., parameter inOneGroup) may include a certain amount of bits (e.g., 8, or any other amount). Each bit of the second bitmap may correspond to a respective one of the SSB groups. The first bit (e.g., the leftmost bit of the second bitmap) may correspond to the first SSB group, which includes the first SSB (having SSB index 0), the second SSB (having SSB index 8), ..., and the eighth SSB (having SSB index 56). The second bit (e.g., the second bit of the second bitmap) may correspond to the second SSB group, which includes the first SSB (having SSB index 1), the second SSB (having SSB index 9), ..., and the eighth SSB (having SSB index 57). The last bit (e.g., the rightmost bit of the second bitmap) may correspond to an eighth SSB group, including the first SSB (having SSB index 7), the second SSB (having SSB index 15), ..., and the eighth SSB (having SSB index 63), etc. An SSB may belong to / correspond to at most one SSB group from the second SSB group. A bit of the second bitmap may indicate whether the base station may transmit / transmit the SSB group corresponding to the bit in an SSB burst. A bit set to a first value (e.g., 1) may indicate that the corresponding SSB group is transmitted / transmitted by the base station in an SSB burst. A bit set to a second value (e.g., 0) may indicate that the corresponding SSB group is not transmitted / transmitted by the base station in an SSB burst, or vice versa.

[0263] A plurality of SSBs (e.g., having SSB indices of 0 to 63) may be grouped into a first SSB group for a first bitmap. Each of the first SSB groups may include SSBs with consecutive SSB indices. A first of the first SSB groups may include SSBs with SSB indices of 0 to 7, and a second of the first SSB groups may include SSB indices of 8 to 15. A plurality of SSBs may also be grouped into a second SSB group for a second bitmap. Each of the second SSB groups may include SSBs with non-consecutive SSB indices. A first of the second SSB groups may include SSBs with SSB indices {0, 8, 16, ... 56}. A second of the second SSB groups may include SSBs with SSB indices {1, 9, 17, ... 57}, etc. The SSB index gap between two adjacent SSB indices in the second SSB group may be equal to 8 (or any other value).

[0264] Not all bits in the first and second bitmaps may be considered to determine whether an SSB group is transmitted / transmitted. The maximum amount of SSBs in an SSB burst is f c For ≤ 3 GHz, it may be equal to 4 (e.g., according to FIG. 34). The wireless device may determine that the four leftmost bits of a bitmap (e.g., the first bitmap and / or the second bitmap) are valid. The wireless device may ignore the four rightmost bits of the first bitmap and / or the second bitmap.

[0265] As shown in Figure 36, the first bitmap may be indicated by the base station as {1 0 1 0 0 0 0 0}, and the second bitmap may be indicated as {1 1 0 0 0 0 0 0}. The base station may, for example, transmit SSBs at index {0 1 16 17} within an SSB burst based on the grouping configuration of the first SSB group and the second SSB group and further based on the first bitmap and the second bitmap.

[0266] The base station may transmit / transmit a MIB via the PBCH. The MIB may indicate configuration parameters (e.g., for CORESET0) for wireless devices monitoring the PDCCH to schedule SIB1 messages. The base station may transmit / transmit MIB messages with an 80 ms transmission periodicity (or any other first periodicity). The same MIB message may be repeated within 80 ms (according to the SSB periodicity). The content of the MIB message may be the same over an 80 ms period. The same MIB may be transmitted / transmitted across all SSBs in an SSB burst. A PBCH transmission (e.g., a MIB) may indicate that an associated SIB1 does not exist. For example, if a PBCH transmission indicates that an associated SIB1 does not exist, the wireless device may be specified / indicated another frequency on which to search for an SSB associated with SIB1 and a frequency range in which the wireless device can assume that an SSB associated with SIB1 does not exist. The indicated frequency range may be limited to within the same operator's contiguous spectrum allocation in which an SSB is detected.

[0267] The base station may transmit / transmit the SIB1 message with a periodicity of 160 ms (or any other second periodicity). The base station may transmit the same SIB1 message with a variable transmission repetition periodicity within 160 ms. The default transmission repetition period of SIB1 may be 20 ms (or any other third periodicity). The base station may determine the actual transmission repetition periodicity based on the network implementation. The SIB1 repetition transmission period may be 20 ms, for example, for SSB and CORESET multiplexing pattern 1. The SIB1 transmission repetition period may be the same as the SSB period, for example, for SSB and CORESET multiplexing pattern 2 or 3. SIB1 may include information regarding the availability and scheduling of other SIBs (e.g., mapping of SIBs to system information (SI) messages, periodicity, SI window size), and / or an indication of whether one or more SIBs are provided only upon request. Configuration parameters required by the wireless device to implement SI requests may be indicated in SIB1 if one or more SIBs are provided only upon request.

[0268] A base station may enable power-saving operation of a wireless device due to a limited battery capacity of the wireless device. The base station may enable power-saving operation of the wireless device based on, for example, active BWP management (as shown in FIG. 22), an SCell dormancy mechanism (as shown in FIG. 28), a wake-up / go-sleep indication (as shown in FIG. 31A and / or FIG. 31B), SSSG switching on active BWP (e.g., as shown in FIG. 32A and / or FIG. 32B), and / or PDCCH skipping (as shown in FIG. 33). The base station may not be able to save energy from the base station's perspective (e.g., when the base station needs to periodically transmit / transmit some always-on downlink signals (e.g., SSB, MIB, SIB1, SIB2, periodic CSI-RS, etc.) in some periods even when there are no active wireless devices transmitting / transmitting to / from the base station) when, for example, the base station indicates power saving operation of the wireless devices (e.g., based on the examples described herein with respect to Figures 22, 28, 31A, 31B, 32A, 32B, and / or 33). The base station may be required to periodically transmit / transmit some always-on downlink signals (e.g., SSB, MIB, SIB1, SIB2, periodic CSI-RS, etc.) when, for example, the base station transitions a cell to a dormant state by switching the cell's active BWP to a dormant BWP (e.g., as described with respect to Figure 28).

[0269] For example, if the base station needs to reduce the periodicity of the always-on downlink signal transmission, the base station may send / transmit an RRC message (e.g., SIB1) indicating a longer periodicity of the always-on downlink signal transmission. For example, before deciding to power off (e.g., both the RF module and the baseband unit (BBU)) for energy saving, the base station may send / transmit an RRC reconfiguration message to wireless devices in the source cell (e.g., each wireless device in the source cell) to indicate a handover to a neighboring cell. The wireless devices in the source cell (e.g., each wireless device in the source cell) may perform a four-step or two-step RACH procedure to perform a handover to a neighboring cell and then disconnect / terminate the RRC connection with the source cell. For example, the base station may turn off (e.g., the RF unit and BBU) for energy saving after the wireless devices complete the handover procedure to the neighboring cell. Sending / transmitting an RRC message indicating a change in the periodicity of an always-on downlink signal and / or sending (e.g., transmitting) an RRC message requesting a handover may not be efficient, e.g., considering the dynamic and fast-changing traffic patterns of different wireless devices in 5G systems and / or future systems.

[0270] In at least some wireless communications, network energy-saving operations may include shutting down some cells and / or reducing the periodicity of SSBs / SIB1 / SIB2, which may differ from power-saving operations for wireless devices as described herein with respect to Figures 22, 28, 31A, 31B, 32A, 32B, and / or 33, with or without beam sweeping. Shutting down cells (in whole or in part) may lead to adverse effects on data transmission delays and / or power consumption in the access process. Existing SSBs may be modified toward lighter versions, for example, by carrying no or minimal information, such as PSS, which may be referred to as "light SSBs." This "light SSB" may be combined with other techniques, such as infrequent SSB transmissions (e.g., periodicity > 20 ms) and / or "on-demand SSBs," which are SSB transmissions triggered by the wireless device via an UL trigger signal. The base station may transmit / transmit this "light SSB," and the wireless device may, for example, monitor this "light SSB" and react by transmitting / transmitting an uplink trigger signal if a wireless device is present attempting to access the network. The base station may, for example, begin transmitting / transmitting the complete SSB based on receiving the uplink trigger signal. The network may, for example, adjust its SSB transmission configuration to respond to the wireless device's instructions after receiving the uplink trigger signal.

[0271] Network energy saving operations may include BS DTX configurations / modes / states / operations (e.g., similar to wireless device DRX configurations, such as those described herein with respect to Figures 29, 30, 31A, and / or 31B). For BS DTX operations, the base station may (periodically) power on a cell (or multiple cells) for a first duration and then power off the cell for a second duration. During the first duration that the cell is powered on (or in the first power state / mode), the base station may transmit / transmit periodic downlink signals (e.g., SIB / SSB / CSI-RS / TRS), a downlink control channel (PDCCH), a downlink shared channel (PDSCH), etc. During a second duration in which the cell is powered off (or in a second power state / mode), the base station may reduce the transmit power / bandwidth / beam of the periodic downlink signal, stop transmitting the periodic downlink signal, and / or stop transmitting the PDCCH / PDSCH. The base station may perform a periodic DTX operation, for example, by configuring the periodicity of a DTX cycle to include a first duration of a power-on state and a second duration of a power-off state. The base station may perform a one-shot DTX operation, for example, by indicating a duration of the one-shot DTX operation, which duration includes a first duration of a power-on state and a second duration of a power-off state.

[0272] In at least some wireless communications, a base station may operate in a BS DTX mode / operation / configuration for a given cell and with a given pattern (e.g., DTX on duration and DTX off duration in a DTX cycle). A wireless device may decide to use the BS DTX pattern in the cell as its DRX pattern. The network may not need to configure DRX separately for each wireless device in the cell. Requiring all wireless devices in a cell to use the same DRX pattern may increase power consumption of the wireless devices. Wireless devices in a cell (e.g., all wireless devices in a cell) may be required to monitor the PDCCH for a long period of time, for example, if the DTX on duration (the cell is powered on) is configured for a long period of time (10 ms, 100 ms, or even longer), even if there are wireless devices in the cell with a low volume of data to be transmitted / transmitted and / or received within the long period of time. At least some wireless communications may increase power consumption of wireless devices, for example, when the base station is in DTX operation.

[0273] A wireless device may be configured with both a cell-level (and / or BS-level) DTX configuration and a wireless device-specific DRX configuration to further improve power consumption of the wireless device, for example, when the base station is in DTX operation. The wireless device-specific DRX configuration may be configured with / associated with a first pattern (e.g., on / off duration) that is different from a second pattern (e.g., on / off duration) of the cell-level DTX configuration. For example, when the wireless device performs both cell-level DTX operation and wireless device-specific DRX operation on a cell, the wireless device may not be aligned with the base station with respect to cell status, PDCCH monitoring, CSI reporting, DRX-related timers, etc. Misalignment between the wireless device and the base station may increase power consumption of the wireless device and / or the base station, increase uplink interference, and / or increase data transmission delay, for example, when performing cell-level DTX operation and wireless device-specific DRX operation. The improvements described herein may provide for coordinating cell DTX operations and wireless device-specific DRX operations, in particular coordinating cell state management, PDCCH monitoring, CSI reporting, and / or DRX-related timer management, etc., to reduce power consumption of wireless devices and / or base stations, reduce uplink interference, and / or reduce data transmission delays.

[0274] The wireless device may determine that the cell is in a first power state (e.g., a power-on state or a first power mode) after / based on receiving a first message indicating configuration parameters of the cell DTX configuration / operation and before receiving a second message indicating, for example, enabling the cell DTX configuration / operation. For example, the cell may remain in the first power state after the base station sends / transmits the first message and before, for example, sending / transmitting the second message. The wireless device may perform DRX operation according to a wireless device-specific DRX configuration, for example, based on the cell being in the first power state. The wireless device may align with the base station regarding whether the cell is in a power-on state (or a first power state / mode) or a power-off state (or a second power state / mode), for example, if cell-level DTX operation is configured and not enabled. Cell (power) state / mode alignment between the wireless device and the base station may provide benefits such as improved power consumption of the wireless device and / or improved CSI reporting quality.

[0275] A wireless device-specific DRX operation may be enabled during a first duration when the cell is in DTX for the duration of the cell DTX configuration, and / or may be disabled (e.g., not implemented) during a second duration when the cell is in the DTX-off duration of the cell DTX configuration. Enabling / implementing a wireless device-specific DRX operation may include, for example, starting a DRX-on duration timer of the wireless device-specific DRX operation in a first slot if the first slot is within the DTX-on duration of the cell. Disabling / not implementing a wireless device-specific DRX operation may include, for example, stopping / disabling a DRX-on duration timer of the wireless device-specific DRX operation in a second slot if the second slot is within the DTX-off duration of the cell. Enabling a wireless device-specific DRX operation during a time when the cell is in a DTX-on state (and / or disabling / not implementing a wireless device-specific DRX operation during a time when the cell is in a DTX-off state) may provide advantages such as improved power consumption and / or more efficient use of resources.

[0276] A wireless device switching from an RRC idle state to an RRC active state may not yet have received a network energy saving indication for the base station's cell. Determining whether the cell is in a non-energy saving state, for example, before receiving a MAC CE / DCI by the wireless device indicating DTX mode enablement, may include powering on the cell for a first time and then periodically powering off the cell for a second time. The network energy saving state of the cell between the wireless device and the base station may be shifted, for example, if the wireless device is in a DRX off state when the base station transmits a network energy saving indication in the DCI. For example, the wireless device monitors the PDCCH for the DCI using an RNTI dedicated to the network energy saving indication, regardless of whether the wireless device is in a DRX active state. The power consumption of the wireless device may increase based on the wireless device being in a DRX active time, which may occur due to the execution of a DRX on duration timer. The DRX on duration timer may be stopped by the wireless device, for example, when the wireless device receives a network energy saving indication. The DRX on duration timer may be stopped by the wireless device, for example, when the cell is in a power-off state based on the cell's DTX configuration. The DRX on duration timer may be started by the wireless device, for example, if the timer is not running when the cell is in a power-on state based on the cell's DTX configuration. The wireless device may have difficulty determining whether to apply a network energy saving instruction, for example, when a cell group (e.g., each cell group) consists of multiple DRX cell groups configured with cell-group-specific DRX configurations. One or more of the multiple DRX cell groups may be determined by the wireless device, for example, based on at least one of the first cell from which a network energy saving instruction is received, the content of the network energy saving instruction, and / or other factors. Operating in the manner described herein may provide advantages such as saving energy / bandwidth, indicating cell DTX status to the wireless device, coordinating DTX and DRX, and / or more efficient use of communication resources.

[0277] For at least some wireless technologies, network energy-saving operations may include shutting down some cells or reducing the periodicity of SSB / SIB1 / SIB2, which may differ from power-saving operations, with or without beam sweeping, for wireless devices as described herein with respect to Figures 22, 28, 31A, 31B, 32A, 32B, and / or 33. Shutting down cells (in whole or in part) may lead to adverse effects on data transmission delays and / or power consumption during the access process. Another option may include modifying the SSB toward a lighter version, for example, by carrying no or minimal information such as PSS, which may be referred to as a "light SSB." This "light SSB" may be combined with other technologies, such as infrequent SSB transmissions (e.g., periodicity > 20 ms) or "on-demand SSB," which is an SSB transmission triggered by the UE via an UL trigger signal. As an example, the base station may transmit this "light SSB," and if there is a wireless device monitoring this "light SSB" and attempting to access the network, the wireless device may respond by transmitting an uplink trigger signal. Upon receiving the uplink trigger signal, the base station may begin transmitting the complete SSB. In one example, after receiving the uplink trigger signal, the network may adjust its SSB transmission configuration to respond to the wireless device's instructions.

[0278] A base station may have multiple transmit / receive points (TRPs) to improve spectral efficiency and / or transmission robustness. A base station may transmit DL signals / channels via multiple TRPs within a cell and / or via multiple TRPs between cells. A base station may have two or more TRPs. A first TRP may be physically located at a different location from a second TRP. The first TRP may be connected to the second TRP via a backhaul link (e.g., a wired link or a wireless link), where the backhaul link may be an ideal backhaul link with zero or negligible transmission delay, or the backhaul link may be a non-ideal backhaul link. The first TRP may be implemented using antenna elements, RF chains, and / or baseband processors that are configured / managed independently from the second TRP.

[0279] 37A and 37B show examples of multiple transmit and receive point (TRP) configurations. FIG. 37A shows an example of communication between a base station (with multiple TRPs) and a wireless device (with a single panel or multiple panels) based on intra-cell TRPs. Transmission and reception by multiple TRPs may improve system throughput and / or transmission robustness for wireless communications at high frequencies (e.g., above 6 GHz). Multiple TRPs may be associated with the same physical cell identifier (PCI). Multiple TRPs that share the PDCCH / PDSCH / PUCCH / PUSCH resources of a cell may be referred to as intra-cell TRPs (or intra-PCI TRPs).

[0280] A TRP among a plurality of TRPs of a base station may be indicated / identified by at least one of a TRP identifier (ID), a virtual cell index, or a reference signal index (or group index). In one example, in a cell, a TRP may be identified by a control resource set (core set) group (or pool) index (e.g., CORESETPoolIndex as shown in FIG. 26) of a core set group from which a DCI is transmitted from a base station on the core set. The TRP ID of the TRP may include the TRP index indicated in the DCI. The TRP ID of the TRP may include a TCI state group index of a TCI state group. The TCI state group may include at least one TCI state in which a wireless device receives a downlink TB or a base station transmits a downlink TB.

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

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

[0283] A wireless device may assume (or determine) that a ControlResourceSet is assigned CORESETPoolIndex as 0 for a ControlResourceSet without a CORESETPoolIndex. Scheduling information for receiving a PDSCH is indicated and carried only by the corresponding PDCCH, for example, when a wireless device is scheduled with a PDSCH that is fully / partially / non-overlapping in the time and frequency domain. A wireless device may be expected to be scheduled with the same active BWP and the same SCS. A wireless device may be simultaneously scheduled with at most two codewords when a wireless device is scheduled with a PDSCH that is fully / partially overlapping in the time and frequency domain.

[0284] A wireless device may be enabled to perform the following operations, for example, if PDCCHs scheduling two PDSCHs are associated with different Control Resource Sets having different values ​​of CORESETPoolIndex, then for any two HARQ process IDs in a given scheduled cell, if a wireless device is scheduled to start receiving a first PDSCH starting at symbol j via a PDCCH associated with a value of CORESETpoolIndex ending at symbol i, the wireless device may be scheduled to receive a PDSCH starting earlier than the end of the first PDSCH using a PDCCH associated with a different value of CORESETpoolIndex ending later than symbol i, and in the given scheduled cell, the wireless device may receive the first PDSCH in slot i, with its corresponding HARQ-ACK 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 starting later than the first PDSCH, with its corresponding HARQ-ACK assigned to be transmitted in a slot prior to slot j.

[0285] For example, in the case of a wireless device configured by the higher layer parameter PDCCH-Config including two different values ​​of CORESETPoolIndex in ControlResourceSet, for both cases when tci-PresentInDCI is set to "enabled" and tci-PresentInDCI is not configured in RRC connected mode, for example, if the offset between reception of the DL DCI and the corresponding PDSCH is less than a threshold timeDurationForQCL, the wireless device may assume that the DM-RS port of the PDSCH associated with the value of CORESETPoolIndex of the serving cell is quasi-co-located with the RS with respect to the QCL parameter used for the PDCCH quasi-co-location indication of the CORESET associated with the monitored search space having the lowest CORESET-ID among the CORESETs configured with the same value of CORESETPoolIndex as the PDCCH scheduling that PDSCH in the active BWP of the serving cell in the most recent slot monitored by the wireless device, where one or more CORESETs associated with the same value of CORESETPoolIndex as the PDCCH scheduling that PDSCH in the serving cell's active BWP are configured with the same value of CORESETPoolIndex as the PDCCH scheduling that PDSCH. For example, if the offset between reception of the DL DCI and the corresponding PDSCH is less than a threshold timeDurationForQCL, and at least one configured TCI state for the serving cell of the scheduled PDSCH includes “QCL-TypeD”, and at least one TCI codepoint indicates two TCI states, the wireless device may assume that the DM-RS port of the PDSCH of the serving cell is quasi-co-located with the RS with respect to the QCL parameter associated with the TCI state corresponding to the lowest codepoint among the TCI codepoints that include two different TCI states.

[0286] FIG. 37B illustrates an example of communication between a base station (with multiple TRPs) and a wireless device (with a single panel or multiple panels) based on inter-cell TRP (or inter-PCI TRP). 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 may be referred to as inter-cell TRPs (or inter-PCI TRPs). The cells 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 (e.g., a second TRP with a second PCI different from the first PCI of the first TRP) as part of cell 1 with PCI 1. In this case, the wireless device may receive a first SSB from cell 1 with PCI 1 and a second SSB from cell 2 with PCI 2, for example, when operating the wireless device's inter-cell TRP. The first SSB and the second SSB may have different configuration parameters, which may be implemented as described herein with respect to Figures 34, 35, and / or 36. According to inter-cell TRP, a wireless device may receive a PDCCH / PDSCH and / or transmit a PUCCH / PUSCH on cell 1 including PCI1 and cell 2 including PCI2 having different TCI states (e.g., one associated with one of the first SSBs and the other associated with one of the second SSBs).

[0287] A serving cell may be a cell (e.g., a PCell, SCell, PSCell, etc.) from which a wireless device receives SSB / CSI-RS / PDCCH / PDSCH and / or transmits PUCCH / PUSCH / SRS. A serving cell may be identified by a serving cell index (e.g., ServCellIndex or SCellIndex configured in an RRC message). For an RRC_CONNECTED wireless device not configured with CA / DC, there may be only one serving cell, including the primary cell. For an RRC_CONNECTED wireless device configured with CA / DC, the term "serving cell" may be used to refer to a set of cells including the special cell and all secondary cells. For a wireless device configured with CA, a cell that provides additional radio resources above the special cell may be referred to as a secondary cell. A non-serving (or neighboring) cell may be a cell from which a wireless device does not receive MIB / SIB / PDCCH / PDSCH and / or transmit PUCCH / PUSCH / SRS, etc. A non-serving cell may have a physical cell identifier (PCI) that is different from the serving cell's PCI. A non-serving cell may not be identified by (or in association with) a serving cell index (e.g., ServCellIndex or SCellIndex). A wireless device may rely on a non-serving cell's SSB for Tx / Rx beam (or spatial domain filter) decisions (for the serving cell's PDCCH / PDSCH / PUCCH / PUSCH / CSI-RS / SRS, etc.), for example, if the serving cell's TCI status is associated with the non-serving cell's SSB (e.g., in the TCI Status IE of TS38.331). A base station may not send an RRC message configuring the non-serving cell's PDCCH / PDSCH / PUCCH / PUSCH / SRS resources for a wireless device.

[0288] For a particular wireless device, Cell 1 may be a serving cell and may be associated with a first TRP (TRP1). Cell 2 may be a non-serving (or neighboring) cell and may be associated with a second TRP. The base station may send one or more RRC messages including configuration parameters for Cell 1 to the wireless device. The configuration parameters for Cell 1 may indicate multiple additional PCI configurations (e.g., SSB-MTC-AdditionalPCI IEs) for multiple (non-serving or neighboring) cells relative to Cell 1, each additional PCI configuration corresponding to a (non-serving or neighboring) cell having a PCI value different from the PCI value of the serving cell, including an additional PCI index (AdditionalPCIIndex) identifying the additional PCI configuration, the PCI of the non-serving cell, an SSB periodicity indication, a position indication of the (candidate) SSB in the SSB burst, a transmit power indication for the SSB, etc. The configuration parameters for Cell 1 may further indicate multiple TCI states. A TCI state (e.g., each TCI state) among the multiple TCI states may 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 a QCL type among the multiple QCL types, for example, when an SSB is transmitted via cell 1 (or in another serving cell). For example, when an SSB of the TCI state is transmitted via a non-serving (neighboring) cell, the TCI state may be further 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 wireless device may 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 may be that the reference RS of the TCI state for the serving cell may come from (or be transmitted via) the (non-serving or neighboring) cell in the latter case. The SSB may be implemented based on the examples described herein with respect to Figures 34, 35, and / or 36.

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

[0290] The base station may use both TRPs for transmission to the wireless device via Cell 1. The base station may indicate (by DCI / MAC CE) a first TCI state associated with an SSB / CSI-RS transmitted via Cell 1 (or another serving cell) for a first transmission to the wireless device (via PDCCH / PDSCH / PUSCH / PUCCH / SRS resources of Cell 1). The base station may indicate (by the same DCI / MAC CE or a different DCI / MAC CE) a second TCI state associated with a second SSB transmitted via Cell 2 (which is a non-serving / neighboring cell as indicated by the AdditionalPCIIndex of the TCI configuration parameter) for a second transmission to the wireless device (via PDCCH / PDSCH / PUSCH / PUCCH / SRS resources of Cell 1). The second SSB transmitted via Cell 2 may be different from the first SSB transmitted via Cell 1. Using two TCI states from two TRPs (one may be from the serving cell and another one may be from a non-serving / neighboring cell) may avoid performing time-consuming handovers (HO) between Cell 1 and Cell 2 and may improve coverage when the wireless device is moving at the edge of Cell 1 and Cell 2.

[0291] A wireless device may be provided with two TCI states, each corresponding to a TRP among multiple TRPs (e.g., as described in connection with Figures 37A and 37B). A TCI state may be referred to as a channel-specific TCI state when the TCI state is used for a specific channel (e.g., PDSCH / PDCCH / PUCCH / PUSCH), and different channels may be associated with different channel-specific TCI states. A TCI state may be referred to as a unified TCI state when the TCI state is use...

Claims

1. 1. A method comprising: receiving, by a wireless device, one or more Radio Resource Control (RRC) messages including configuration parameters of a candidate cell for a Layer 1 or Layer 2 Triggered Mobility (LTM) procedure, the configuration parameters indicating frequency resources associated with an early uplink synchronization procedure of the candidate cell; receiving a Physical Downlink Control Channel (PDCCH) order indicating transmission of a preamble via the candidate cell for the early uplink synchronization procedure; transmitting the preamble over the frequency resources of the candidate cell; receiving a medium access control (MAC) control element (CE) indicating a switch from a source cell to the candidate cell for the LTM procedure.

2. The method of claim 1 , wherein the configuration parameter indicates an initial uplink bandwidth portion of the candidate cell.

3. activating an initial uplink BWP of the candidate cell based on a switch from the source cell to the candidate cell as a PCell; The method of claim 1 or 2, further comprising: transmitting at least one signal via the activated initial uplink BWP of the PCell.

4. transmitting the preamble a frequency starting point indication indicating a frequency offset of a Physical Random Access Channel (PRACH) transmission opportunity for the preamble; and The method according to any one of claims 1 to 3, comprising transmitting the preamble on a frequency resource based on a starting PRB of a deactivated initial uplink BWP.

5. 1. A method comprising: transmitting, by a base station, one or more Radio Resource Control (RRC) messages including configuration parameters of a candidate cell for a Layer 1 or Layer 2 Triggered Mobility (LTM) procedure, the configuration parameters indicating frequency resources associated with an early uplink synchronization procedure of the candidate cell; transmitting a Physical Downlink Control Channel (PDCCH) order indicating transmission of a preamble via the candidate cell for the early uplink synchronization procedure; transmitting a medium access control (MAC) control element (CE) indicating a switch from a source cell to the candidate cell for the LTM procedure.

6. The method of any one of claims 1 to 5, wherein the source cell and the candidate cell are in different Time Alignment Groups (TAGs).

7. The method according to any one of claims 1 to 6, wherein the MAC CE further indicates a Time Alignment Command (TAC) for the candidate cell, and transmitting at least one signal is based on the TAC.

8. 8. The method of claim 1, wherein the configuration parameters of the candidate cell include a frequency resource indication for a deactivated initial uplink BWP, the frequency resource indication indicating a starting physical resource block (PRB) and a quantity of PRBs for the deactivated initial uplink BWP.

9. The method according to any one of claims 1 to 8, wherein the PDCCH order includes a cell indication indicating the candidate cell.

10. The method according to any one of claims 1 to 9, wherein the PDCCH order includes a synchronization signal block (SSB) index indicating an SSB among a plurality of SSBs of the candidate cell.

11. 11. The method of claim 1, wherein receiving the MAC CE indicating the switch from the source cell as a PCell to the candidate cell is based on a Time Alignment Timer (TAT) of the candidate cell not running.

12. The method according to any one of claims 1 to 11, further comprising: keeping an initial uplink BWP deactivated during transmission of the preamble.

13. 1. A computing device comprising: one or more processors; a memory storing instructions that, when executed by said one or more processors, cause said computing device to perform the method of any one of claims 1 to 12.

14. 1. A system comprising: A wireless device configured to perform the method of any one of claims 1 to 12; the wireless device configured to receive at least one message from a base station.

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

Images