Latency reduction for primary cell handover

Abstract

A base station may communicate with a wireless device. The message may be used for information indicating layer 1 and / or layer 2 triggered mobility (LTM) procedures. For example, a Media Access Control (MAC) Control Element (CE) may indicate various information, such as a target cell of an LTM procedure, whether a Random Access (RA) procedure is performed on the target cell, a TA value, BWPs of respective Bandwidth Parts (BWPs) of the target cell, and / or other information associated with the LTM procedure.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 410,914, filed September 28, 2022. The above-referenced application is hereby incorporated by reference in its entirety. Background Art

[0002] The base station can communicate with one or more wireless devices. The base station enables power saving operation of the one or more wireless devices. Summary of the Invention

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

[0004] A base station can communicate with a wireless device. Layer 1 and / or Layer 2 Triggered Mobility (LTM) procedures can be used to improve handover procedures. Messages can be used to indicate information about the LTM procedure. For example, a Medium Access Control (MAC) Control Element (CE) can indicate various information, such as the target cell for the LTM procedure, whether a random access (RA) procedure is to be performed on the target cell, the TA value, the bandwidth part (BWP) of the target cell, and / or other information associated with the LTM procedure. The base station can, for example, implement network energy conservation by implementing procedures to reduce latency during a primary cell handover.

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

[0006] In the accompanying drawings, some features are illustrated by way of example and not limitation. Like reference numerals refer to similar elements throughout the figures.

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

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

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

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

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

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

[0013] Figure 5A An exemplary mapping of downlink channels is shown.

[0014] Figure 5B An exemplary mapping of uplink channels is shown.

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

[0016] Figure 7 An exemplary configuration of a frame is shown.

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

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

[0019] Figure 10A An exemplary component carrier based carrier aggregation configuration is shown.

[0020] Figure 10B An exemplary group of cells is shown.

[0021] Figure 11A An exemplary mapping of one or more synchronization signal / physical broadcast channel (SS / PBCH) blocks is shown.

[0022] Figure 11B An exemplary mapping of one or more channel state information reference signals (CSI-RS) is shown.

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

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

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

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

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

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

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

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

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

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

[0033] Figure 17A 、 Figure 17B and Figure 17C An exemplary MAC subheader is shown.

[0034] Figure 18A and Figure 18B An exemplary MAC PDU is shown.

[0035] Figure 19 Example logical channel identifier (LCID) values are shown.

[0036] Figure 20 Exemplary LCID values are shown.

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

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

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

[0040] Figure 24A An exemplary master information block (MIB) message is shown.

[0041] Figure 24B An exemplary configuration of a CORESET is shown.

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

[0043] Figure 25 An example of a system information block (SIB) is shown.

[0044] Figure 26 Exemplary RRC configuration parameters are shown.

[0045] Figure 27 An exemplary configuration of the search space is shown.

[0046] Figure 28 Exemplary sleep management is shown.

[0047] Figure 29 An example of a DRX configuration for a wireless device is shown.

[0048] Figure 30 An example of a DRX configuration for a wireless device is shown.

[0049] Figure 31A and Figure 31B An example of power saving operation of a wireless device is shown.

[0050] Figure 32A and Figure 32B An example of search space set group (SSSG) switching for power saving of a wireless device is shown.

[0051] Figure 33 An example of physical downlink control channel (PDCCH) skipping for power saving of a wireless device is shown.

[0052] Figure 34 An example of a synchronization signal block (SSB) configuration is shown.

[0053] Figure 35 An example of SSB transmission by a base station is shown.

[0054] Figure 36 An example of SSB transmission by a base station is shown.

[0055] Figure 37A and Figure 37B An example of multiple transmission and reception point (TRP) configurations is shown.

[0056] Figure 38 An example of a layer 3 based switching procedure is shown.

[0057] Figure 39 An example of a radio resource control (RRC) message for layer 3 based exchange is shown.

[0058] Figure 40 An example of RRC messages for layer 3 based exchange is shown.

[0059] Figure 41 An example of a layer 3 based conditional switching procedure is shown.

[0060] Figure 42 Examples of RRC messages for the layer-based conditional exchange procedure are shown.

[0061] Figure 43 Examples of layer 1 or layer 2 based switching are shown.

[0062] Figure 44 An example of inter-cell beam management is shown.

[0063] Figure 45 An example of PCell switching for network energy saving is shown.

[0064] Figure 46A and Figure 46B An example of a timeline for PCell switching is shown.

[0065] Figure 47 An example of PCell switching / changing is shown.

[0066] Figure 48A 、 Figure 48B 、 Figure 48C and Figure 48D An example of a target PCell configuration for PCell switching / change is shown.

[0067] Figure 49A 、 Figure 49B and Figure 49C An example of a PCell switching indication command is shown.

[0068] Figure 50 An example of latency reduction employing a variable PDCCH handover command format is shown. DETAILED DESCRIPTION

[0069] The accompanying drawings and description provide examples. It should be understood that the examples shown and / or described in the accompanying drawings are non-exclusive, and that the features shown and described may be practiced in other examples. Examples of the operation of wireless communication systems that can be used in the field of multi-carrier communication systems are provided. More particularly, the techniques disclosed herein may relate to signaling for resource protection.

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

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

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

[0073] The RAN 104 may include one or more base stations (not shown). As used herein, the term "base station" may include one or more of the following: a base station, a node, a Node B (NB), an evolved Node B (eNB), a next-generation Node B (gNB), a next-generation evolved Node B (ng-eNB), a relay node (e.g., an integrated access and backhaul (IAB) node), a donor node (e.g., a donor eNB, a donor gNB, etc.), an access point (AP) (e.g., a Wi-Fi access point), a transmission and reception point (TRP), a computing device, a device capable of wireless communication, or any other device capable of sending and / or receiving signals. A base station may include one or more of the elements listed above. For example, a base station may include one or more TRPs. As other non-limiting examples, a base station may include, for example, one or more of: a Node B (e.g., associated with Universal Mobile Telecommunications System (UMTS) and / or third generation (3G) standards), an 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 relay node or relay node for extending 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, for example, Wi-Fi or any other suitable wireless communication standard), any other generation base station, and / or any combination thereof. A base station may include one or more devices, such as at least one base station central device (e.g., a gNB central unit (gNB-CU)) and at least one base station distributed device (e.g., a gNB distributed unit (gNB-DU)).

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

[0075] One or more base stations (e.g., in the RAN 104) may be implemented as sectorized sites with more or fewer than three sectors. One or more base stations in the RAN 104 may be implemented as an AP, a baseband processing device / unit coupled to several RRHs, and / or a repeater or relay node for extending 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, where, for example, the baseband processing device / unit may be centralized in a pool of baseband processing devices / units or virtualized. The relay node may amplify and transmit (e.g., transmit, retransmit, rebroadcast, etc.) radio signals received from the donor node. The relay node may perform substantially the same / similar functions as a relay node. The relay node may decode the radio signal received from the donor node, for example, to remove noise before amplifying and transmitting the radio signal.

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

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

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

[0079] The CN 152 (e.g., 5G-CN) may provide / configure one or more interfaces to one or more DNs 170 for one or more wireless devices 156. The one or more wireless devices 156 may communicate with one or more DNs 170, such as public DNs (e.g., the internet), private DNs, and / or intra-carrier DNs. As part of its interfacing functionality, the CN 152 (e.g., 5G-CN) may set up end-to-end connections between the one or more wireless devices 156 and the one or more DNs 170, authenticate the one or more wireless devices 156, and / or provide / configure charging functionality. The CN 152 (e.g., 5G-CN) may have a service-based architecture, which may differ from other CNs (e.g., such as 3GPP 4G CNs). The architecture of a node of the CN 152 (e.g., 5G-CN) may be defined as network functions that provide services to other network functions via interfaces. The network functions of CN 152 (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).

[0080] The CN 152 (e.g., 5G-CN) may include an access and mobility management function (AMF) device 158A and / or a user plane function (UPF) device 158B, which may be separate components or a single component AMF / UPF device 158. The UPF device 158B may serve as a gateway between the RAN 154 (e.g., NG-RAN) and 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, user plane quality of service (QoS) processing (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink traffic verification), downlink packet buffering, and / or downlink data notification triggering. The UPF device 158B may serve as an anchor point for intra- / inter-radio access technology (RAT) mobility, an external protocol (or packet) data unit (PDU) session point interconnecting with 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 a PDU session, which may be a logical connection between the wireless device and a DN.

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

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

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

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

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

[0086] A wireless device may access a base station via an interface (e.g., a Uu interface) for user plane and control plane configuration. A base station (e.g., gNB 160) may provide user plane and control plane protocol terminals to a wireless device 156 via the Uu interface. A base station (e.g., gNB 160A) may provide user plane and control plane protocol terminals to a wireless device 156A via 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 terminals (e.g., where E-UTRA may refer to 3GPP 4G radio access technology) to one or more wireless devices 156 via the Uu interface. A base station (e.g., ng-eNB 162B) may provide E-UTRA user plane and control plane protocol terminals to a wireless device 156B via the Uu interface associated with a second protocol stack. The user plane and control plane protocol terminals may include, for example, NR user plane and control plane protocol terminals, 4G user plane and control plane protocol terminals, and the like.

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

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

[0089] Figure 1A The communication network 100 and / or Figure 1BThe communication network 150 in the present disclosure may include any quantity and / or type of devices, such as, for example, computing devices, wireless devices, mobile devices, handsets, tablets, laptops, IoT devices, hotspots, cellular repeaters, computing devices, and / or, more generally, UEs. Although reference may be made herein to one or more of the aforementioned types of devices (e.g., UEs, wireless devices, computing devices, etc.), it should be understood that any device herein may include any one or more of the aforementioned types of devices or similar devices. The communication network and any other networks mentioned herein may include an LTE network, a 5G network, a satellite network, and / or any other network for wireless communication (e.g., any 3GPP network and / or any non-3GPP network). The apparatus, systems, and / or methods described herein may generally be described as being implemented on one or more devices (e.g., wireless devices, base stations, eNBs, gNBs, computing devices, etc.) in one or more networks, but it should be understood that one or more features and steps may be implemented in any device and / or any network.

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

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

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

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

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

[0095] 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 indicated 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 not depend on a parameter set and / or a transmission time interval (TTI) duration (or other duration). The RLC layer (e.g., RLC 213 and 223) may provide / configure an RLC channel 330 as a service to the PDCP layer (e.g., PDCP 214 and 224, respectively), such as Figure 3 As shown in .

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

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

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

[0099] For example, if SDAP 225 receives three IP packets (or other number of IP packets) from one or more QoS flows and maps the three packets (or other number of packets) to radio bearers (e.g., radio bearers 402 and 404), then downlink data flow can begin. SDAP 225 can map IP packets n and n+1 to the first radio bearer 402 and IP packet m to the second radio bearer 404. The SDAP header (in Figure 4A Each SDAP SDU shown in FIG is marked with an "H" before it) can be added to an IP packet to generate an SDAP PDU, which can be called a PDCP SDU. A data unit transmitted from / to a higher protocol layer can be called a service data unit (SDU) of a lower protocol layer, and a data unit transmitted to / from a lower protocol layer can be called a protocol data unit (PDU) of a higher protocol layer. Figure 4A As shown, the data units from SDAP 225 may be SDUs of the lower protocol layer PDCP 224 (eg, PDCP SDUs), and may be PDUs of SDAP 225 (eg, SDAP PDUs).

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

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

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

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

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

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

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

[0107] The PHY layer can generate physical signals to support the lower layer operations of the PHY layer, which can be similar to physical control channels. Figure 5A and Figure 5B As shown in , the physical layer signals (e.g., which may be defined 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.

[0108] 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). Figure 2B An exemplary control plane configuration (e.g., NR control plane protocol stack) is shown. Figure 2BAs shown in FIG, a control plane configuration (e.g., an NR control plane protocol stack) may use substantially the same / similar one or more protocol layers (e.g., PHY 211 and 221, MAC 212 and 222, RLC 213 and 223, and PDCP 214 and 224) as an exemplary user plane configuration (e.g., an NR user plane protocol stack). The similar four protocol layers may include PHY 211 and 221, MAC 212 and 222, RLC 213 and 223, and PDCP 214 and 224. The control plane configuration (e.g., an NR control plane 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., an NR control plane protocol stack), for example, instead of SDAP 215 and 225. The control plane configuration may include AMF 230, which includes NAS protocol 237.

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

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

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

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

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

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

[0115] 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 the RRC idle state (e.g., RRC idle 606) or during the 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 broadcasting the paging message across the entire mobile communication network. The mobility management mechanism used during the RRC idle state (e.g., RRC idle 606) or during the RRC inactive state (e.g., RRC inactive 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 across cells of the cell group in which the wireless device is currently camped (e.g., rather than sending the paging message across the entire mobile communication network). The mobility management mechanism for the RRC idle state (e.g., RRC idle 606) and the RRC inactive state (e.g., RRC inactive state 604) can track the wireless device at the cell group level. The mobility management mechanism can, for example, use different grouping granularities for tracking. There can be multiple levels of cell grouping granularity (e.g., three levels of cell grouping granularity: a single cell; cells within a RAN area identified by a RAN area identifier (RAI); and cells within a group of RAN areas referred to as a tracking area and identified by a tracking area identifier (TAI)).

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

[0117] RAN areas can be used to track wireless devices (e.g., the location of wireless devices at the RAN level). For wireless devices in an RRC inactive state (e.g., RRC inactive state 604), a RAN notification area can be assigned / provisioned / configured to the wireless device. A RAN notification area can include one or more cell identities (e.g., an RAI list and / or a TAI list). A base station can belong to one or more RAN notification areas. A cell can belong to one or more RAN notification areas. The wireless device can perform a notification area update with the RAN to update the RAN notification area of the wireless device, for example, if 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.

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

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

[0120] Physical signals and physical channels (e.g., Figure 5A and Figure 5BThe data (e.g., an Orthogonal Frequency Division Multiplexing (OFDM) symbol in an NR configuration or any other symbol) can be mapped onto one or more symbols (e.g., Orthogonal Frequency Division Multiplexing (OFDM) symbols in an NR configuration or any other symbol). OFDM is a multicarrier communication scheme that transmits / transmits data via F orthogonal subcarriers (or subcarriers). The data can be mapped onto a series of complex symbols, called source symbols (e.g., M Quadrature Amplitude Modulation (M-QAM) symbols, M Phase Shift Keying (M-PSK) symbols, or any other modulated symbol), and divided into F parallel symbol streams, for example, prior to data transmission. These F parallel symbol streams can be viewed as if they were in the frequency domain. These F parallel symbol streams can be used as input to an Inverse Fast Fourier Transform (IFFT) block, which transforms them into the time domain. The IFFT block can receive F source symbols at a time, one from each of the F parallel symbol streams. The IFFT block can use each source symbol to modulate the amplitude and phase of one of F sinusoidal basis functions corresponding to the F orthogonal subcarriers. The output of the IFFT block can be F time-domain samples representing the sum of the F orthogonal subcarriers. The F time domain samples may form a single OFDM symbol. The OFDM symbol provided / output by the IFFT block may be sent / transmitted over the air interface on a carrier frequency, for example, after one or more processes (e.g., adding a cyclic prefix) and up-conversion. For example, a Fast Fourier Transform (FFT) block may be used to mix the F parallel symbol streams before being processed by the IFFT block. This operation may produce a Discrete Fourier Transform (DFT) precoded OFDM symbol and may be used by one or more wireless devices in the uplink to reduce the Peak to Average Power Ratio (PAPR). The FFT block may be used at the receiver to perform inverse processing on the OFDM symbol to recover the data mapped to the source symbol.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0148] SS / PBCH blocks can span one or more OFDM symbols in the time domain (e.g., 4 OFDM symbols, such as Figure 11A As shown or any other number / number of symbols), and may span one or more subcarriers in the frequency domain (e.g., 240 consecutive subcarriers or any other number / number of subcarriers). The PSS, SSS, and PBCH may have a common center frequency. The PSS may be sent / transmitted first and may span, for example, 1 OFDM symbol and 127 subcarriers. The SSS may be sent / transmitted after the PSS (e.g., two symbols later) and may span 1 OFDM symbol and 127 subcarriers. The PBCH may be sent / transmitted after the PSS (e.g., across the next 3 OFDM symbols) and may span 240 subcarriers (e.g., after 1 OFDM symbol). Figure 11A ) and / or may span fewer than 240 subcarriers (e.g., in the second and fourth OFDM symbols shown). Figure 11A 3 OFDM symbol shown).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0166] Figure 11B An exemplary mapping of one or more CSI-RSs is shown. The CSI-RSs may be mapped in both the time domain and the frequency domain. Figure 11B Each rectangular block shown in may correspond to an RB within the bandwidth of the cell. The 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 through 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 the following: CSI-RS resource configuration identity; number of CSI-RS ports; CSI-LS configuration (e.g., symbol and RE positions in a subframe); CSI-RS subframe configuration (e.g., subframe position, offset, and periodicity in a radio frame); CSI-RS power parameter; CSI-RS sequence parameter; code division multiple access (CDM) type parameter; frequency density; transmission comb; QCL parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid); and / or other radio resource parameters.

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

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

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

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

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

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

[0173] The wireless device may measure the quality of a beam-pair link using, for example, one or more RSs, including 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 for the RS resource. The base station may indicate the QCL of one or more DM-RSs for the RS resource and a channel (e.g., a control channel, a shared data channel, etc.). For example, if the channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameters, fading, etc.) of a transmission from the RS resource to the wireless device are substantially the same or similar to the channel characteristics of a transmission from the channel to the wireless device, the RS resource and the one or more DM-RSs for the channel may be QCL.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0203] Figure 14B An example of CCE-to-REG mapping is shown. CCE-to-REG mapping for DCI transmission can be performed via CORESET and PDCCH processing. CCE-to-REG mapping can be interleaved (e.g., to provide frequency diversity) or non-interleaved (e.g., to facilitate interference coordination and / or frequency-selective transmission of control channels). A base station can perform different or identical CCE-to-REG mapping on different CORESETs. A CORESET can be associated with a CCE-to-REG mapping (e.g., via RRC configuration). A CORESET can be configured with an antenna port QCL parameter. The antenna port QCL parameter can indicate QCL information for DM-RS received via the CORESET's PDCCH.

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

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

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

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

[0208] The base station may send / transmit configuration parameters for multiple PUCCH resource sets to the 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 number 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, and / or a certain number (e.g., a maximum number) of UCI information bits, where the PUCCH resource is identified by a PUCCH resource identifier (e.g., pucch-resourceid). The wireless device may use one of the multiple PUCCH resources in the PUCCH resource set to send / transmit the UCI information bits. If multiple PUCCH resource sets are configured, the wireless device may select one of the multiple PUCCH resource sets based on, for example, the total bit length of the UCI information bits (e.g., HARQ-ACK, SR, and / or CSI). For example, if the total bit length of the UCI information bits is two bits or less, the wireless device may select the first PUCCH resource set with a PUCCH resource set index equal to "0." For example, if the total bit length of the UCI information bits is greater than two bits and less than or equal to the first configured value, the wireless device may select a second PUCCH resource set having a PUCCH resource set index equal to "1." For example, if the total bit length of the UCI information bits is greater than the first configured value and less than or equal to the second configured value, the wireless device may select a third PUCCH resource set having a PUCCH resource set index equal to "2." For example, if the total bit length of the UCI information bits is greater than the second configured value and less than or equal to a third value (e.g., 1406, 1706, or any other number of bits), the wireless device may select a fourth PUCCH resource set having a PUCCH resource set index equal to "3."

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

[0210] Figure 15AAn example of communication between a wireless device and a base station is shown. The wireless device 1502 and the base station 1504 may be part of a communication network, such as Figure 1A The communication network 100 shown in Figure 1B The communication network 150 shown in FIG. 1 or any other communication network. A communication network may include more than one wireless device and / or more than one base station, with Figure 15A The base stations are configured substantially the same or similarly to those shown in FIG.

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

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

[0213] Data to be transmitted to wireless device 1502 may be provided / transmitted / sent to transmission processing system 1510 of base station 1504, for example, after being processed by processing system 1508. Data to be transmitted to base station 1504 may be provided / transmitted / sent to transmission processing system 1520 of wireless device 1502, for example, after being processed by processing system 1518. Transmission processing system 1510 and transmission processing system 1520 may implement layer 1 OSI functions. Layer 1 may include, for example, information regarding Figure 2A 、 Figure 2B 、 Figure 3 and Figure 4AFor transport processing, the PHY layer may perform, for example, forward error correction coding of transport channels, interleaving, rate matching, mapping of transport channels to physical channels, modulation of physical channels, and multiple-input multiple-output (MIMO) or multi-antenna processing.

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

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

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

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

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

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

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

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

[0222] Figure 16B An exemplary structure for modulating and up-converting a baseband signal to a carrier frequency is shown. The baseband signal can be a complex-valued SC-FDMA, CP-OFDM baseband signal (or any other baseband signal) for an antenna port and / or a complex-valued physical random access channel (PRACH) baseband signal. For example, filtering can be performed / applied prior to transmission.

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

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

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

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

[0227] A base station can communicate with a wireless device via a wireless network (e.g., a communications network). The communication can utilize / adopt one or more radio technologies (e.g., new radio technologies, legacy radio technologies, and / or combinations thereof). The one or more radio technologies can include at least one of the following: one or more technologies related to the physical layer; one or more technologies related to the media access control layer; and / or one or more technologies related to the radio resource control layer. The one or more enhanced radio technologies described herein can improve the performance of the wireless network. For example, based on one or more configurations described herein, the system throughput, transmission efficiency of the wireless network, and / or the data rate of transmission can be increased. For example, based on one or more configurations described herein, the battery consumption of the wireless device can be reduced. For example, based on one or more configurations described herein, the latency of data transmission between the base station and the wireless device can be improved. For example, based on one or more configurations described herein, the network coverage of the wireless network can be increased.

[0228] 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 eight bits). The bit string may be represented by one or more tables, where the most significant bit may be the leftmost bit of the first row of the table, and the least significant bit may be the rightmost bit of the last row of the table. The bit string may be read from left to right and then in line reading order (e.g., from the topmost line of the table to the bottommost line of the table). The bit order of the parameter fields within the MAC PDU may be represented with the first and most significant bit being the leftmost bit and the last and least significant bit being the rightmost bit.

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

[0230] A MAC PDU can include one or more MAC subPDUs. A MAC subPDU within one or more MAC subPDUs can 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 any combination thereof. A MAC SDU can have a variable size. A MAC subheader can correspond to a MAC SDU, a MAC CE, or padding.

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

[0232] Figure 17A An example of a MAC subheader is shown. The MAC subheader may include an R field, an F field, an LCID field, and / or an L field. The LCID field may be six bits long (or any other number of bits). The L field may be eight bits long (or any other number of bits). Each of the R field and the F field may be one bit long (or any other number of bits). Figure 17B An example of a MAC subheader is shown. The MAC subheader may include an R field, an F field, an LCID field, and / or an L field. Figure 17AIn the MAC subheader shown in FIG, the LCID field may be six bits long (or any other number of bits), the R field may be one bit long (or any other number of bits), and the F field may be one bit long (or any other number of bits). The L field may be sixteen bits long (or any other number of bits, such as a length greater than sixteen bits). For example, if the MAC subheader corresponds to a fixed-size MAC CE or padding, the MAC subheader may include an R field having a two-bit length (or any other number of bits) and / or an LCID field having a multi-bit length (or a unit length). Figure 17C An example of a MAC subheader is shown. Figure 17C In the exemplary MAC subheader shown in , the LCID field may be six bits in length (or any other number of bits), and the R field may be two bits in length (or any other number of bits).

[0233] Figure 18A An example of a MAC PDU (eg, DL MAC PDU) is shown. Multiple MAC CEs (such as, Figure 18A ) can be placed together (e.g., within the same MAC PDU). A MAC subPDU including a MAC CE can be placed before (e.g., within a MAC PDU) any MAC subPDU including a MAC SDU or a MAC subPDU including padding. MAC CE 1 can be a fixed-size MAC CE that follows a first-type MAC subheader. The first-type MAC subheader can include an R field and an LCID field (e.g., similar to Figure 17C ). MAC CE 2 may be a variable-size MAC CE following 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 Figure 17A or Figure 17B The size of the MAC SDU following the second type MAC subheader may vary.

[0234] Figure 18B An example of a MAC PDU (eg, UL MAC PDU) is shown. Multiple MAC CEs (such as, Figure 18BMAC CEs 1 and 2 shown in FIG) can be placed together (e.g., within the same MAC PDU). A MAC subPDU including a MAC CE can be placed after all MAC subPDUs including a MAC SDU (e.g., within a MAC PDU). A MAC subPDU and / or a MAC subPDU including a MAC CE can be placed before a MAC subPDU including padding (e.g., within a MAC PDU). Similar to Figure 18A The MAC CE shown in Figure 18B The MAC CE 1 shown in FIG may be a fixed-size MAC CE following a first-type MAC subheader. The first-type MAC subheader may include an R field and an LCID field (e.g., similar to Figure 17C MAC CE shown in ). Similar to Figure 18A The MAC CE shown in Figure 18B The MAC CE 2 shown in FIG may be a variable-size MAC CE following 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 Figure 17A or Figure 17B The size of the MAC SDU following the second type MAC subheader may vary.

[0235] The base station (eg, a MAC entity of the base station) may send / transmit one or more MAC CEs to the wireless device (eg, a MAC entity of the wireless device). Figure 19Example LCID values are shown. LCID values may be associated with one or more MAC CEs. LCID values may be associated with downlink channels, such as DL-SCH. The one or more MAC CEs may include at least one of the following: Semi-Persistent Zero Power CSI-RS (SP ZP CSI-RS) Resource Set Activation / Deactivation MAC CE; PUCCH Spatial Relationship Activation / Deactivation MAC CE; SP SRS Activation / Deactivation MAC CE; SP CSI Report on PUCCH Activation / Deactivation MAC CE; TCI Status Indication of Radio Device Specific (e.g., UE-Specific) PDCCH MAC CE; TCI Status Indication of Radio Device Specific (e.g., UE-Specific) PDSCH MAC CE; Aperiodic CSI Triggering State Subselection MAC CE, SP CSI-RS / CSI Interference Measurement (CSI-IM) Resource Set Activation / Deactivation MAC CE; Radio Device (e.g., UE) Contention Resolution Identity MAC CE; Timing Advance Command MAC CE; DRX Command MAC CE; Long DRX Command MAC CE; SCell Activation / Deactivation MAC CE (e.g., 1 octet); SCell Activation / Deactivation MAC CE (e.g., 4 octets); and / or 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., correspond 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 with an index value of "111011" in the MAC subheader may indicate that the MAC CE associated with the MAC subheader is a long DRX command MAC CE, e.g., a MAC CE associated with a downlink.

[0236] A wireless device (eg, a MAC entity of the wireless device) may send / transmit one or more MAC CEs to a base station (eg, a MAC entity of the base station). Figure 20Example LCID values that may be associated with one or more MAC CEs are shown. The LCID value may be associated with an uplink channel, such as the 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 multi-entry PHR MAC CE; a short truncated BSR; and / or a long truncated BSR. The MAC CE may be associated with (e.g., corresponding 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 with an index value of "111011" in the MAC subheader may indicate that the MAC CE associated with the MAC subheader is a short truncated command MAC CE, e.g., for a MAC CE associated with an uplink.

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

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

[0239] For example, if Cellular Carrier Access (CA) is configured, the base station and / or wireless device may use / adopt an SCell activation / deactivation mechanism. For example, 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. For example, if the wireless device is configured with one or more SCells, the base station may activate or deactivate at least one of the one or more SCells. An SCell may be deactivated unless, for example, the SCell state associated with the SCell is set to an active state (e.g., "active") or a dormant state (e.g., "dormant") after the SCell is configured.

[0240] The wireless device may activate / deactivate an SCell. The wireless device may activate / deactivate a cell based on (e.g., after 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 the one or more SCells. For example, if the aggregated cell has fewer than eight SCells, the SCell activation / deactivation MAC CE may correspond to one octet including seven fields associated with up to seven SCells, respectively. The SCell activation / deactivation MAC CE may include an R field. For example, if the aggregated cell has more than seven SCells, the SCell activation / deactivation MAC CE may include multiple octets including more than seven fields associated with more than seven SCells.

[0241] Figure 21A An exemplary SCell activation / deactivation MAC CE of one octet is shown. Figure 19 The first MAC PDU subheader (shown as '111010' in FIG) may indicate / identify a one-octet SCell activation / deactivation MAC CE. The one-octet SCell activation / deactivation MAC CE may have a fixed size. The one-octet SCell activation / deactivation MAC CE may comprise a single octet. The single octet may comprise a first number / number of C fields (e.g., seven or any other number / number) and a second number / number of R fields (e.g., one or any other number / number).

[0242] Figure 21B An exemplary SCell activation / deactivation MAC CE of four octets is shown. Figure 19 The second MAC PDU subheader (e.g., '111001' shown in FIG) may indicate / identify a four-octet SCell activation / deactivation MAC CE. The four-octet SCell activation / deactivation MAC CE may have a fixed size. The four-octet SCell activation / deactivation MAC CE may include four octets. The four octets may include a third number / number of C fields (e.g., 31 or any other number / number) and a fourth number / number of R fields (e.g., 1 or any other number / number).

[0243] like Figure 21A and / or Figure 21BAs shown in , for example, if an SCell having / corresponding to SCell index i is configured, the Ci field may indicate the activation / deactivation status of the SCell having / corresponding to SCell index i. For example, if the Ci field is set to one, the SCell having SCell index i may be activated. For example, if the Ci field is set to zero, the SCell having SCell index i may be deactivated. For example, if no SCell having SCell index i is configured, the wireless device may ignore the Ci field. The R field may indicate a reserved bit. The R field may be set to zero or any other value (for example, for other purposes).

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

[0245] The base station and / or wireless device can use DCI messages or a BWP inactivity timer to switch between configured BWPs. For example, 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 based on (e.g., after or in response to) the expiration of the BWP inactivity timer associated with the serving cell. The default BWP may be configured by the network. For example, if an FDD system is configured with BA, one UL BWP and one DL BWP for an uplink carrier (e.g., each uplink carrier) can be simultaneously active in the active serving cell. For example, for a TDD system, one DL / UL BWP pair can be simultaneously active in the active serving cell. Operating on one UL BWP and one DL BWP (or one DL / UL pair) can improve wireless device battery consumption. BWPs other than the one active UL BWP and one active DL BWP on which the wireless device can operate can be deactivated. The wireless device may not monitor, for example, PDCCH transmissions on deactivated BWPs. The wireless device may not send (eg, transmit) on the PUCCH, PRACH, and UL-SCH, for example, on a deactivated BWP.

[0246] A serving cell may be configured with up to a first number / quantity of BWPs (e.g., four). At any point in time, for example, upon activation of a serving cell, one BWP may be active. BWP switching within a serving cell may be used to activate an inactive BWP and deactivate an active BWP simultaneously. BWP switching may be controlled by a PDCCH transmission indicating a downlink assignment or 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) upon initiation of a random access procedure (e.g., after or in response to such initiation). For example, when adding an SpCell or activating an SCell, one BWP may initially be active without receiving a PDCCH transmission indicating a downlink assignment or uplink grant. The active BWP of a serving cell may be indicated by one or more configuration parameters (e.g., parameters of an RRC message) and / or PDCCH transmission. For unpaired spectrum, a DL BWP may be paired with a UL BWP, and BWP switching may be common for both UL and DL.

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

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

[0249] The wireless device (e.g., a MAC entity of the wireless device) may apply or use various operations on the active BWP of the activated serving cell configured with the BWP. The various operations may include at least one of: sending (e.g., transmitting) on the UL-SCH; sending (e.g., transmitting) on the RACH; monitoring PDCCH transmissions; sending (e.g., transmitting) the PUCCH; receiving the DL-SCH; and / or (re)initializing any suspended configured uplink grants for which grant type 1 is configured according to a stored configuration (if any).

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

[0251] For example, if a 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 wireless device may perform a BWP switch of the serving cell to the BWP indicated by the PDCCH transmission. For example, if the Bandwidth Part Indicator field is configured in DCI format 1_1, the Bandwidth Part Indicator field value may indicate an active DL BWP from a configured DL BWP set for DL reception. For example, if the Bandwidth Part Indicator field is configured in DCI format 0_1, the Bandwidth Part Indicator field value may indicate an active UL BWP from a configured UL BWP set for UL transmission.

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

[0253] For example, if the wireless device is configured for a secondary cell with a higher layer parameter (e.g., Default-DL-BWP) indicating a default DL BWP among configured DL BWPs, and the wireless device is configured with a higher layer parameter (e.g., bwp-InactivityTimer) indicating a timer value, then the procedure for the wireless device on the secondary cell may be substantially the same as the procedure on the 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 with a higher layer parameter (e.g., Active-BWP-DL-SCell) associated with a first active DL BWP and with a higher layer parameter (e.g., Active-BWP-UL-SCell) associated with a first active UL BWP on a secondary cell or carrier, then the wireless device may use the indicated DL BWP and the indicated UL BWP on the secondary cell as the first active DL BWP and the first active UL BWP, respectively, on the secondary cell or carrier.

[0254] 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 monitor PDCCH transmission candidates in one or more of the following search space sets: Type0-PDCCH CSS set configured by pdcch-ConfigSIB1 in the MIB or by searchSpaceSIB1 in PDCCH-ConfigCommon or by searchSpaceZero in PDCCH-ConfigCommon for DCI formats with CRC scrambled by the SI-RNTI on the primary cell of the MCG; Type0A-PDCCH CSS set configured by searchSpaceOtherSystemInformation in PDCCH-ConfigCommon for DCI formats with CRC scrambled by the SI-RNTI on the primary cell of the MCG; Type1-PDCCH CSS set configured by ra-SearchSpace in PDCCH-ConfigCommon for DCI formats with CRC scrambled by RA-RNTI, MsgB-RNTI, or TC-RNTI on the primary cell; Type2-PDCCH configured by pagingSearchSpace in PDCCH-ConfigCommon CSS set for DCI formats with CRC scrambled by the P-RNTI on the primary cell of the MCG; Type3-PDCCH CSS set configured by 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 one or more CS-RNTIs for the primary cell; and USS set configured by SearchSpace in PDCCH-Config with searchSpaceType = UE-specific, for DCI formats with CRC scrambled by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, one or more CS-RNTIs, SL-RNTI, SL-CS-RNTI or SL-L-CS-RNTI.

[0255] The wireless device may transmit configuration parameters (e.g., Figure 27The PDCCH transmission monitoring timing on the active DL BWP is determined by the one or more PDCCH transmission configuration parameters, wherein the one or more PDCCH transmission configuration parameters include at least one of the following: PDCCH transmission monitoring periodicity within a time slot; PDCCH transmission monitoring offset; or PDCCH transmission monitoring mode. For a search space set (SS s), if , the wireless device may determine that one or more PDCCH transmission monitoring opportunities exist in a number / quantity The number of frames with If the value μ is configured, then It can be the number / quantity of time slots in a frame. It can be the time slot offset indicated in the PDCCH transmission configuration parameter. The wireless device can monitor the PDCCH transmission periodicity indicated in the PDCCH transmission configuration parameter. Start The search space set of consecutive time slots contains PDCCH transmission candidates and may not monitor the next Search space set of consecutive time slots PDCCH transmission candidates. At the CCE aggregation level The USS can be determined by the CCE aggregation level The PDCCH transmission candidate set is defined.

[0256] For CORESET Associated search space set , the wireless device may determine the value corresponding to the carrier indicator field The time slot of the corresponding active DL BWP of the serving cell PDCCH transmission candidates in the search space set Aggregation level The CCE index is , where, for any CSS, ; For USS, , ,for , ,for , ,for , ,and ; ; It is CORESET From 0 to Number / quantization of numbered / quantized CCEs; if the wireless device is configured with the carrier indicator field of the serving cell for monitoring PDCCH transmission by CrossCarrierSchedulingConfig, then Is the Carrier Indicator field value; otherwise, contains, for any CSS, ; ,in is the number / quantity of PDCCH transmission candidates that the wireless device is configured to monitor corresponding to The search space set of the serving cell Aggregation level ; For any CSS, ; For USS, is the search space set CCE aggregation level of Overprovisioning The maximum value of the value; and for The RNTI value is C-RNTI.

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

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

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

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

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

[0262] Higher-layer parameters (e.g., pdcch-ConfigSIB1) may include a second parameter (e.g., searchSpaceZero). The second parameter may indicate the common search space for the cell's initial BWP. 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., between 0 and 15 or any other integer) may identify the configuration of search space 0.

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

[0264] The wireless device may monitor the PDCCH for receiving DCI. The wireless device may monitor the search space 0 of CORESET 0 for receiving DCI. The DCI may schedule SIB1. For example, the SIB1 message may be similar to Figure 25 The wireless device may receive the DCI with the CRC scrambled with the SI-RNTI dedicated to receiving SIB1.

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

[0266] The DownlinkConfigCommonSIB IE may include parameters of the initial downlink BWP of the serving cell (eg, SpCell) (eg, indicated via the initialDownlinkBWP IE). The parameters of the initial downlink BWP may be included in the BWP-DownlinkCommon IE (eg, as indicated in the Figure 26 ). The BWP-DownlinkCommon IE may be used to configure common parameters for the downlink BWP of the serving cell. The base station may configure parameters (e.g., locationAndBandwidth) such that the initial downlink BWP includes the entire CORESET (e.g., CORESET 0) of the serving cell in the frequency domain. The wireless device may use / apply the locationAndBandwidth parameter upon receipt of the parameter. The wireless device may use / apply the locationAndBandwidth parameter to determine the frequency location of the signal relative to the frequency, as indicated by the locationAndBandwidth. The wireless device may not maintain CORESET 0, for example, until after receiving an RRC setup message (e.g., RRCSetup), an RRC resume message (e.g., RRCResume), and / or an RRC re-establishment message (e.g., RRCReestablishment).

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

[0268] The parameter (eg, first-PDCCH-MonitoringOccasionOfPO) may be signaled in SIB1 to page in the initial DL BWP. The parameter first-PDCCH-MonitoringOccasionOfPO may be signaled in the corresponding BWP configuration, eg, to page in a DL BWP other than the initial DL BWP.

[0269] Figure 26 Example RRC configuration parameters are shown. 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 for the downlink BWP of the serving cell (e.g., the initial downlink BWP) to the wireless device (or devices). The one or more configuration parameters for the downlink BWP may include: one or more common BWP parameters for the downlink BWP, one or more cell-specific parameters for the PDCCH of the downlink BWP (e.g., in the pdcch-ConfigCommon IE), one or more cell-specific parameters for the PDSCH of the BWP (e.g., in the pdsch-ConfigCommon IE), and / or one or more other parameters. The pdcch-ConfigCommon IE may include parameters for CORESET 0 (e.g., indicated via the parameter controlResourceSetZero), which 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 in the MIB parameter pdcch-ConfigSIB1. The pdcch-ConfigCommon IE may include parameters for additional common control resource sets (e.g., in commonControlResourceSet) that may be configured and used for any common or radio-specific search spaces. For example, if the network configures commonControlResourceSet, the network may use a parameter ControlResourceSetId other than 0 for this ControlResourceSet. The network may configure commonControlResourceSet in SIB1 such that SIB1 is contained within the bandwidth of CORESET 0. The pdcch-ConfigCommon IE may include parameters for additional common search space lists (e.g., in communSearchSpaceList). The parameters for the search spaces may be based on Figure 27The pdcch-ConfigCommon IE may indicate, from the search space list, a search space for paging (e.g., via parameter pagingSearchSpace), a search space for random access procedure (e.g., via parameter ra-SearchSpace), a search space for SIB1 messages (e.g., via parameter searchSpaceSIB1), common search space 0 (e.g., via parameter searchSpaceZero), and / or one or more other search spaces.

[0270] A CORESET may be associated with a CORESET indicator / index (eg, via the parameter ControlResourceSetId). Figure 14A and / or Figure 14BThe example described above is implemented. CORESET index 0 may identify a common CORESET configured in the MIB and ServingCellConfigCommon (e.g., via the controlResourceSetZero indication). CORESET index 0 may not be used in the ControlResourceSet IE. CORESET indexes with other values may identify a CORESET configured by dedicated signaling or in SIB1. The controlResourceSetId may be unique within the BWP of the serving cell. A CORESET may be associated with a coresetPoolIndex indicating the index of the CORESET pool for 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 the number / number of symbols). Configuration parameters for a CORESET may include at least one of the following: 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 TCI is present in the DCI. A frequency resource indication (e.g., comprising a number of bits, such as 45 bits or any other number 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 number of RBs), where grouping begins with 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, while the remaining bits may sequentially correspond to the remaining RB groups. A bit set to 1 may indicate that the RB group corresponding to that bit is included in the frequency domain resources of a CORESET. Bits corresponding to a group of RBs that is not fully included in a BWP configured with a CORESET may be set to zero.

[0271] Figure 27An exemplary configuration of a search space is shown. The configuration of the search space may be within a SearchSpace IE. One or more search space configuration parameters for the search space may include at least one of the following: a search space ID (e.g., searchSpaceId); a core set 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); the number of candidates for the aggregation level (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 one or more symbols of a slot in which the wireless device may monitor for PDCCH on the search space. The control resource set ID may indicate / identify the core set on which the search space may be located.

[0272] A wireless device in an RRC idle state (e.g., RRC_IDLE) or an RRC inactive state (e.g., RRC_INACTIVE) may periodically monitor a PO for receiving one or more paging messages of 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 to prepare for data reception (e.g., a warm-up phase). The gap between the wake-up and the PO may be set to be sufficient to accommodate all processing requirements. After warm-up, the wireless device may perform timing acquisition and coarse synchronization from the SSB, frequency and time tracking, time and frequency offset compensation, and / or calibration of the local oscillator. 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 the configuration parameters of the PCCH configuration (e.g., as configured in SIB1). The configuration parameters of the PCCH configuration may be as described with respect to Figure 25 As stated.

[0273] Figure 28Example cell dormancy management is shown. Cell dormancy management may include transitions between a dormant state and a non-dormant state. Example transitions may be used for operations on an SCell. A base station may send / transmit one or more RRC messages to a wireless device. 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., BWP 3) may be configured as a non-dormant BWP, and / or a second BWP (e.g., BWP 1) may be configured as a dormant BWP. A default BWP (e.g., BWP 0) may be configured in the multiple BWPs. A non-dormant BWP may be a BWP that a wireless device may activate, for example, based on / in response to a transition of an SCell from a dormant state to a non-dormant state. A dormant BWP may be a BWP to which a wireless device may switch based on / in response to a transition of an SCell from a non-dormant state to a dormant state. Configuration parameters may indicate one or more search spaces and / or core sets configured on the non-dormant BWP. Configuration parameters may indicate no search space or no core set for the dormant BWP. The configuration parameter may indicate the CSI reporting configuration parameter of the dormant BWP.

[0274] The active BWP for an SCell can be a dormant BWP, a non-dormant BWP, or a default BWP. The default BWP can be different from the dormant BWP. Configuration parameters can indicate one or more search spaces and / or one or more CORESETs configured on the default BWP. For example, if the BWP inactivity timer expires or upon receipt of a DCI indicating a switch to the default BWP, the wireless device can switch to the default BWP as the active BWP. The wireless device can perform (e.g., if the default BWP is the active BWP) at least one of the following: monitoring the PDCCH on the default BWP of the SCell; receiving PDSCH transmissions via the default BWP of the SCell; sending PUSCH transmissions via the default BWP of the SCell; sending SRS via the default BWP of the SCell; and / or sending CSI reports for the default BWP of the SCell (e.g., periodically, aperiodically, and / or semi-persistently). For example, if a dormant / non-dormant indication is received indicating the dormant state of the SCell, the wireless device can switch to the dormant BWP as the active BWP of the SCell. The wireless device may (e.g., based on / in response to switching to a dormant BWP) perform at least one of the following: avoid monitoring the PDCCH on the dormant BWP of the SCell (or avoid monitoring the PDCCH of the SCell if the SCell is cross-carrier scheduled by another cell); avoid receiving PDSCH transmissions via the dormant BWP of the SCell; avoid sending PUSCH transmissions via the dormant BWP of the SCell; avoid sending SRS via the dormant BWP of the SCell; and / or send CSI reports (e.g., periodic, aperiodic and / or semi-persistent CSI reports) of the dormant BWP of the SCell.

[0275] A base station may send / transmit DCI to a wireless device via PDCCH resources. The DCI may include a sleep / non-sleep indicator indicating the sleep state or non-sleep state of an SCell. The wireless device may (e.g., based on the sleep / non-sleep indicator indicating the sleep state of the SCell): transition the SCell to the sleep state (e.g., if the SCell was in the non-sleep state before receiving the DCI); or maintain the SCell in the sleep state (e.g., if the SCell was in the sleep state before receiving the DCI). Transitioning the SCell to the sleep state may include switching to the sleep BWP of the SCell (e.g., configured by the base station). The wireless device may (e.g., based on the sleep / non-sleep indicator indicating the non-sleep state of the SCell): transition the SCell to the non-sleep state (e.g., if the SCell was in the sleep state before receiving the DCI); or maintain the SCell in the non-sleep state (e.g., if the SCell was in the non-sleep state before receiving the DCI). Transitioning the SCell to the non-sleep state may include switching to the non-sleep BWP of the SCell (e.g., configured by the base station).

[0276] The wireless device may, for example, switch to a non-dormant BWP (e.g., BWP 3) configured by the base station as the active BWP for the SCell based on transitioning the SCell from a dormant state to a non-dormant state. The wireless device may perform (e.g., based on switching to the non-dormant BWP as the active BWP for the SCell) at least one of the following: monitoring the PDCCH on the active BWP for the SCell (or monitoring the PDCCH of the SCell if the SCell is configured for cross-carrier scheduling by another cell); receiving PDSCH transmissions via the active BWP for the SCell; and / or sending PUCCH transmissions, PUSCH transmissions, RACH transmissions, and / or SRS transmissions via the active BWP (e.g., if the active BWP is an uplink BWP).

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

[0278] DRX operation can be used by a wireless device to improve wireless device battery life. When DRX is configured, the wireless device may not continuously monitor downlink control channels, such as the PDCCH or EPDCCH. The base station may configure DRX operation with a DRX parameter set, for example, using RRC configuration. The DRX parameter set may be selected based on the application type, allowing the wireless device to reduce power and resource consumption. The wireless device may receive data packets with extended latency because the wireless device may be in a DRX sleep / off state when data arrives at the wireless device, and the base station may wait until the wireless device transitions to a DRX on state, for example, based on (e.g., after or in response to) configuring / activating DRX.

[0279] In DRX mode, for example, if there are no packets to receive, the wireless device may shut down most of its circuitry. The wireless device may not continuously monitor the PDCCH in DRX mode. For example, if DRX operation is not configured, the wireless device may continuously monitor the PDCCH. In this state, the wireless device monitors the downlink (DL) (or monitors the PDCCH), which is referred to as the DRX active state. The time in DRX mode when the wireless device is not monitoring / listening to the PDCCH is referred to as the DRX sleep state.

[0280] Figure 29An example DRX configuration for a wireless device is shown. A 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 of the DRX cycle (e.g., a DRX on duration). The second parameter may indicate a second time for a DRX sleep state of the DRX cycle (e.g., a DRX off duration). The one or more parameters may also include a DRX cycle duration. During the DRX active state, the wireless device may monitor the PDCCH on the serving cell to detect one or more DCIs. During the DRX sleep state, the wireless device may stop monitoring the PDCCH on the serving cell. For example, if multiple cells are active, the wireless device may monitor all PDCCHs on the multiple cells (or monitor all PDCCHs on the multiple cells) for the DRX active state. During the DRX off duration, the wireless device may stop monitoring all PDCCHs on the multiple cells (or monitor all PDCCHs on the multiple cells). The wireless device may repeat DRX operation according to the one or more DRX parameters.

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

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

[0283] The RRC can control 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., indicated as psf in the DRX configuration) and / or in milliseconds.

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

[0285] A timer (e.g., drx-Inactivity-Timer) may specify the duration that the wireless device may be active, for example, after successfully decoding a PDCCH indicating a new transmission (UL, DL, or SL). Upon receiving a PDCCH for a new transmission (UL, DL, or SL), this timer may be restarted. 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. For example, if the wireless device enters DRX mode, the cycle (e.g., drx-ShortCycle) may be the first type of DRX cycle to be followed (e.g., if configured). An IE (e.g., DRX-Config IE) may indicate the length of the short cycle. A 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 sleep mode (DRX-off). A timer (e.g., drx-HARQ-RTT-TimerDL) may specify the minimum duration from the time a new transmission is received, e.g., before the wireless device can 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 the maximum duration the wireless device can monitor the PDCCH, e.g., if the wireless device expects a retransmission from the eNodeB.

[0286] For example, based on (e.g., after or in response to) a configured DRX cycle, the active time may include a time when a scheduling request is sent on the PUCCH and is pending. Based on (e.g., after or in response to) a configured DRX cycle, the active time may include a time when an uplink grant for a pending HARQ retransmission may occur and data for a synchronous HARQ process exists in a corresponding HARQ buffer. For example, after successfully receiving a random access response for a preamble not selected by the MAC entity, for example, based on the configured DRX cycle, the active time may include a time when the PDCCH may indicate that a new transmission addressed to the C-RNTI of the MAC entity has not been received.

[0287] A timer, such as the 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 for the corresponding HARQ process (e.g., drx-RetransmissionTimerDL). A UL HARQ RTT timer (e.g., drx-HARQ-RTT-TimerUL) may expire in a subframe. The MAC entity may start a timer for the corresponding HARQ process (e.g., drx-RetransmissionTimerUL).

[0288] The wireless device may receive a DRX command MAC CE and / or a long DRX command MAC CE (e.g., based on the information provided herein regarding Figure 19 The example described). The MAC entity of the wireless device may, for example, stop a timer (e.g., drx-onDurationTimer) and / or stop another timer (e.g., drx-InactivityTimer) based on receiving a DRX command MAC CE and / or a long DRX command MAC CE. For example, if the inactivity timer (e.g., drx-InactivityTimer) expires and / or if a cycle is being configured, the MAC entity may start or restart a timer (e.g., drx-ShortCycleTimer) and / or may use a cycle (e.g., a short DRX cycle). For example, the MAC entity may use a cycle (e.g., a long DRX cycle).

[0289] 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 stop the timer (e.g., drx-ShortCycleTimer) and may use a long DRX cycle.

[0290] For example, if a short DRX cycle is used and [(SFN * 10) + number of subframes] 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 start of the subframe, where drx-SlotOffset may be a value (configured in the DRX configuration parameters) indicating, for example, a delay before starting the drx-onDurationTimer. For example, if a long DRX cycle is used and [(SFN * 10) + number of subframes] modulo (drx-longCycle) = drxStartOffset, the wireless device may, for example, start a timer (e.g., drx-onDurationTimer) after a value (e.g., drx-SlotOffset) from the start of a subframe, where drx-SlotOffset may be a value (configured in the DRX configuration parameters) indicating, for example, a delay before starting the drx-onDurationTimer.

[0291] Figure 30 An example of a DRX configuration for a wireless device is shown. A 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 for a DRX inactivity timer (e.g., drx-InactivityTimer), a second timer value for a HARQ RTT timer (e.g., drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL), and a third timer value for a HARQ retransmission timer (e.g., drx-RetransmissionTimerDL and / or drx-RetransmissionTimerUL).

[0292] The base station can send a PDCCH to a wireless device such as Figure 30The wireless device may send (e.g., transmit) a DCI (e.g., a first DCI) including a downlink assignment for a TB (as shown in FIG). The wireless device may, for example, start a drx-InactivityTimer based on (e.g., after or in response to) receiving the DCI. The wireless device may monitor the PDCCH, for example, for a running timer (e.g., drx-InactivityTimer). The wireless device may receive the TB based on receiving the DCI. The wireless device may send (e.g., transmit) a NACK to the base station when the TB is not successfully decoded. The wireless device may, for example, start a HARQ RTT timer (e.g., drx-HARQ-RTT-TimerDL) in the first symbol after the sending (e.g., transmission) of the NACK ends. The wireless device may stop a retransmission timer (e.g., drx-RetransmissionTimerDL) for the HARQ process corresponding to the TB. The wireless device may stop monitoring the PDCCH for one or more RNTIs affected by DRX operation, such as a running HARQ RTT timer. The one or more RNTIs may include C-RNTI, CI-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI and / or AI-RNTI.

[0293] For example, if the HARQ RTT timer expires (such as Figure 30 ), the wireless device may monitor the PDCCH and start a HARQ retransmission timer (e.g., drx-RetransmissionTimerDL). For example, if the HARQ retransmission timer is running, the wireless device monitoring the PDCCH may receive a second DCI scheduling retransmission of a TB (e.g., Figure 30 For example, if the second DCI is not received (eg, before the HARQ retransmission timer expires), the wireless device may stop monitoring the PDCCH.

[0294] Figure 31A Exemplary power save operation of a wireless device is shown. Figure 31A An exemplary power saving operation of the wireless device may be based on a wake-up indication. The base station may send / transmit one or more messages including parameters of a wake-up duration (e.g., a power saving duration or a power saving channel (PSCH) opportunity) to the wireless device. The wake-up duration may be located (e.g., starting) at a time that is the number / number of time slots (or symbols) before the DRX on duration of the DRX cycle. The number / number of time slots (or symbols) may be the gap between the wake-up duration and the DRX on duration. The DRX cycle may be based on information such as information about Figure 29 The example described herein is implemented in accordance with the present disclosure. The number of time slots may be configured in one or more RRC messages or may be predefined as a fixed value. The gaps may be used for at least one of: synchronization with a base station; measuring reference signals; and / or retuning RF parameters. The gaps may be determined based on the capabilities of the wireless device and / or the base station. Parameters 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 the PSCH). Parameters for the wake-up duration may include at least one of: a PSCH channel format (e.g., a parameter set, a DCI format, a PDCCH format); PSCH periodicity; a control resource set; and / or a PSCH search space. For example, if a parameter for the wake-up duration is configured, the wireless device may monitor the PSCH to receive a wake-up signal during the wake-up duration. For example, if a parameter for the PSCH timing is configured, the wireless device may monitor the PSCH to detect a wake-up indication during a PSCH timing / wake-up duration. The wireless device may, for example, wake up based on / in response to receiving a wake-up signal / channel (or a wake-up indication via the PSCH) to monitor the PDCCH during the DRX Active Time (e.g., including the DRX On Duration) of the next DRX cycle according to the DRX configuration. The wireless device may, for example, monitor the PDCCH during the DRX Active Time (e.g., while the drx-onDurationTimer is running) based on / in response to receiving a wake-up indication via the PSCH. If the wireless device does not receive a PDCCH transmission during the DRX Active Time, the wireless device may return to sleep. The wireless device may remain in sleep during the DRX Off Duration of the DRX cycle. 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 to skip PDCCH monitoring during the wake-up duration (or PSCH opportunity), the wireless device may skip monitoring the PDCCH during the DRX Active Time.

[0295] Figure 31B Exemplary power save operation of a wireless device is shown. Figure 31B The power saving operation of the wireless device may be based on a sleep entry indication. The wireless device may, for example, return to sleep during the DRX active time (e.g., during the next DRX on duration of the DRX cycle) based on / in response to receiving the sleep entry indication via the PSCH and skip monitoring the PDCCH. For example, if the wireless device does not receive a sleep entry indication via the PSCH during the wake duration, the wireless device may monitor the PDCCH during the DRX active time according to the configuration parameters of the DRX operation. Figure 31A and Figure 31B The power saving operation can reduce the power consumption of PDCCH monitoring during the DRX active time.

[0296] Power saving operations can be based on a combination of Figure 31A and Figure 31B The operations described. The base station may send / transmit a power saving indication in DCI via PSCH, the power saving indication indicating whether the wireless device may wake up within the next DRX on duration or skip the next DRX on duration. The wireless device may receive DCI via PSCH. The wireless device may wake up within the next DRX on duration, for example based on / in response to the power saving indication indicating that the wireless device may wake up within the next DRX on duration. The wireless device may monitor PDCCH within the next DRX on duration in response to waking up. The wireless device may go to sleep during the next DRX on duration or skip the next DRX on duration, for example based on / in response to the power saving indication indicating that the wireless device may skip (or go to sleep) within the next DRX on duration. The wireless device may skip monitoring PDCCH within the next DRX on duration, for example based on / in response to the power saving indication indicating that the wireless device should go to sleep within the next DRX on duration. About Figure 30 、 Figure 31A and / or Figure 31B The various examples described may be expanded and / or combined to further improve power consumption of wireless devices and / or signaling overhead of base stations.

[0297] Figure 32A An example of SSSG switching for power saving of a wireless device is shown. Figure 32AExamples 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) switching indicators (or SSSG switching 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 occupancy time (COT) duration indicators, and / or one or more SSSG switching flags. Each of the one or more SSSG switching flags may correspond to a corresponding cell group in a plurality of cell groups. Each cell group in the plurality of cell groups may include one or more cells. For example, if the SSSG switching flag is set to a first value, the SSSG switching flag corresponding to the cell group in the one or more SSSG switching flags may indicate that each cell in the cell group is switching from the first SSSG to the second SSSG. For example, if the SSSG switching flag is set to a second value, the SSSG switching flag may indicate that each cell in the cell group is switching from the second SSSG to the first SSSG.

[0298] Figure 32B An example of SSSG switching for power saving of a wireless device is shown. SSSG switching can be based on DCI (e.g., corresponding to DCI format 2_0 or as described in relation to Figure 23 The wireless device 3004 may receive a configuration 3006 of the SSSG of the BWP of the cell. The configuration 3006 may include multiple parameters. The configuration 3006 may be delivered via RRC messaging and / or SIB1 messaging.

[0299] The wireless device 3004 can monitor the parameters (e.g., searchSpaceGroupIdList, such as the parameters about Figure 27 The search space set (eg, Type 3-PDCCH CSS set, USS set, or any other type of search space set) may be provided / indicated with a group indicator / index of the search space set.

[0300] The wireless device 3004 may or may not be provided / indicated with the searchSpaceGroupIdList parameter of the search space set. For example, if the search space set is not configured with searchSpaceGroupIdList, then Figure 32B The SSSG switching may not be applicable for PDCCH monitoring on a search space. For example, if the search space set is not configured with searchSpaceGroupIdList, the wireless device 3004 can monitor the search space set on the BWP without switching out of the search space set for PDCCH monitoring.

[0301] For example, if the wireless device 3004 is provided / indicated with a parameter cellGroupsForSwitchList indicating one or more serving cell groups (e.g., as described in relation to Figure 26 As described above), then Figure 32B The SSSG switching shown in FIG can be used / applied to all serving cells in each group. For example, if the wireless device 3004 is not provided / indicated with the parameter cellGroupsForSwitchList, then as described in Figure 32B The SSSG handover described above may only be used / applied to serving cells for which the wireless device 3004 is provided / indicated with the parameter searchSpaceGroupIdList. For example, if the wireless device 3004 is provided / indicated with the parameter searchSpaceGroupIdList, the wireless device 3004 may reset PDCCH monitoring according to a search space set having a specific group index (e.g., group index 0).

[0302] The wireless device 3004 can be configured based on the wireless device processing capability (e.g., wireless device processing capability 1, wireless device processing capability 2, etc.) and subcarrier spacing (SCS). and is provided / indicated with a quantity / number having a symbol The searchSpaceSwitchDelay parameter (e.g. Figure 26 For SCS configuration The wireless device processing capability 1 can be used / applied unless the wireless device 3004 indicates support for wireless device processing capability 2. For example, for wireless device capabilities 1 and =0, Can be 25 for wireless device capabilities 1 and =1, Can be 25 for wireless device capabilities 1 and =2, Can be 25 for wireless device capability 2 and =0, Can be 10, for wireless device capabilities 2 and =1, can be 12, and for wireless device capabilities 2 and =2, It can be 22 and so on.

[0303] The wireless device 3004 may be provided / indicated with a parameter searchSpaceSwitchTimer (in time slots, e.g., Figure 26). The parameter searchSpaceSwitchTimer may have a timer value for the serving cells 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 one after each time slot based on a reference SCS configuration, which is the minimum SCS configuration among all configured downlink BWPs in the serving cell or in the set of serving cells. The wireless device 3004 may maintain the reference SCS configuration during the timer decrement procedure.

[0304] The parameter searchSpaceSwitchTimer can be defined as a value in time slots. The parameter searchSpaceSwitchTimer can indicate the duration used to monitor 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 can be based on the SCS. For example, if the SCS is 15 kHz, the valid timer value can be one of {1, …, 20}. For example, if the SCS is 30 kHz, the valid timer value can be one of {1, …, 40}. For example, if the SCS is 60 kHz, the valid timer value can be one of {1, …, 80}. The base station can configure the same timer value for all serving cells in the same cell group, as indicated by the parameter CellGroupForSwitch.

[0305] The wireless device 3004 may monitor (e.g., step 3012) 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 BWP of the cell (e.g., via configuration 3006). The wireless device 3004 may be provided / indicated with a SearchSpaceSwitchTrigger that indicates the location of the SSSG switch flag field of the serving cell as present in the DCI (e.g., a DCI corresponding to DCI format 2_0). The parameter SearchSpaceSwitchTrigger may be as follows: Figure 27 Configure as shown in .

[0306] The wireless device 3004 may receive a DCI 3008 (e.g., having a DCI format 2_0). For example, if the value of the SSSG switch flag field in the DCI 3008 is 1 (or any other predefined value), the DCI 3008 may indicate an SSSG switch of the cell. The wireless device 3004 may switch (e.g., step 3014) to a second SSSG for PDCCH monitoring. The wireless device 3004 may start monitoring the PDCCH on the second SSSG (e.g., a search space set with a group index of 1) of the serving cell and stop monitoring the PDCCH on the first SSSG (or a search space set with a group index of 0). The wireless device 3004 may start monitoring the PDCCH on the second SSSG (e.g., a search space set with a group index of 1) and stop monitoring the PDCCH on the first SSSG in a first time slot that is at least 100 ms after the last symbol of the PDCCH including the DCI. symbols. The wireless device 3004 may, for example, initiate a window (e.g., initiate a search space switch timer) based on switching to the second SSSG. The wireless device 3004 may, for example, set a timer value of the search space switch timer to a value provided / indicated by the parameter searchSpaceSwitchTimer based on receiving the DCI.

[0307] The wireless device 3004 may monitor the PDCCH on the second SSSG (e.g., the search space set with group index 1) based on the configuration of the SSSG of the BWP of the cell. The wireless device 3004 may be indicated the location of the SSSG switch flag field in the DCI (e.g., corresponding to DCI format 2_0) of the serving cell via the parameter SearchSpaceSwitchTrigger. The wireless device 3004 may receive the DCI. For example, if the value of the SSSG switch flag field in the DCI is 0, the DCI may indicate an SSSG switch of 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 of the serving cell and stop monitoring the PDCCH on the search space set with group index 1. The wireless device 3004 may start monitoring the PDCCH on the search space set with group index 0 and stop monitoring the PDCCH on the search space set with group index 1 in a first time slot that is at least 100 ms after the last symbol of the PDCCH including the DCI. symbols.

[0308] For example, if the wireless device 3004 initially monitors the PDCCH of the serving cell on a first SSSG, the wireless device 3004 may begin monitoring the PDCCH of the serving cell on a second SSSG (e.g., a search space set with group index 1) and stop monitoring the PDCCH of the first SSSG (e.g., a search space set with group index 0). The wireless device 3004 may begin monitoring the PDCCH of the serving cell on the second SSSG and stop monitoring the PDCCH on the first SSSG at the beginning of a first time slot that is at least one time slot after the timer expires or after the last symbol of the remaining channel occupancy duration of the serving cell (e.g., as indicated by the DCI 3008). symbols.

[0309] The wireless device 3004 may or may not be provided / indicated with the parameter SearchSpaceSwitchTrigger for the serving cell. For example, the parameter SearchSpaceSwitchTrigger may not be present in the configuration parameters corresponding to SlotFormatIndicator (e.g., where SlotFormatIndicator is configured to monitor Group-Common-PDCCH for Slot-Format-Indicator (SFI)). For example, based on the absence of the parameter SearchSpaceSwitchTrigger, the DCI 3008 (e.g., corresponding to DCI format 2_0) may not include an SSSG switch flag field. For example, if the parameter SearchSpaceSwitchTrigger is not provided, and if the wireless device 3004 detects the DCI based on monitoring the PDCCH on the first SSSG, the wireless device 3004 may begin monitoring the PDCCH on the second SSSG (e.g., the search space set with group index 1) of the serving cell and stop monitoring the PDCCH on the first SSSG (e.g., the search space set with group index 0). The wireless device 3004 may start monitoring the PDCCH on the second SSSG in a first time slot that is at least 10 seconds after the last symbol of the PDCCH including the DCI and stop monitoring the PDCCH on the first SSSG. For example, if the wireless device 3004 detects DCI based on monitoring the PDCCH in any search space set, the wireless device 3004 may set the timer value to the value provided by the parameter searchSpaceSwitchTimer (or restart the timer).

[0310] The wireless device 3004 may or may not be provided / indicated with the parameter SearchSpaceSwitchTrigger for the serving cell. For example, if the parameter SearchSpaceSwitchTrigger is not provided, and if the wireless device 3004 initially monitors the PDCCH of the serving cell according to the first SSSG, the wireless device 3004 may begin monitoring the PDCCH of the serving cell according to the second SSSG (e.g., the search space set with group index 1) and stop monitoring the PDCCH of the serving cell according to the first SSSG (e.g., the search space set with group index 0). The wireless device 3004 may begin monitoring the PDCCH of the serving cell according to the second SSSG at the beginning of a first time slot that is at least 10 seconds after the time slot at which the timer expires, and stop monitoring the PDCCH according to the first SSSG. For example, if the wireless device 3004 is provided with a search space set to monitor the PDCCH for detecting DCI format 2_0, the wireless device 3004 may start monitoring the PDCCH of the serving cell according to the second SSSG after the last symbol indicated by DCI format 2_0 for the remaining channel occupancy duration of the serving cell, and stop monitoring the PDCCH according to the first SSSG.

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

[0312] The wireless device 3004 may determine the time slot and the symbol in the time slot to start or stop PDCCH monitoring on the search space set for the serving cell to which the wireless device 3004 is provided / instructed with the parameter searchSpaceGroupIdList. If the parameter cellGroupsForSwitchList is configured based on the minimum SCS among all configured downlink BWPs If a set of serving cells is provided / indicated for the wireless device 3004, the wireless device 3004 may start or stop PDCCH monitoring on the search space set for the serving cells. The downlink BWP may be in the serving cell or in the set of serving cells, and, if available, in the serving cell in which the wireless device 3004 receives a PDCCH transmission and detects the corresponding DCI format 2_0 (e.g., triggering the start or stop of PDCCH monitoring on the search space set).

[0313] Figure 33 An exemplary PDCCH skipping for power saving of a wireless device is shown. The base station 3302 may send / transmit one or more RRC messages including configuration parameters 3306 to the wireless device 3304. The configuration parameters 3306 may be used for the PDCCH of the BWP of the cell (e.g., as described in relation to Figure 26 and / or Figure 27 The wireless device 3304 may monitor the PDCCH on the BWP, for example, based on the configuration parameters 3306 of the PDCCH. The BWP may be a downlink BWP, which may be in an active state. The wireless device 3304 may activate the BWP, as described with respect to Figure 22 As stated.

[0314] The wireless device 3304 may receive a first DCI 3308 indicating that PDCCH skipping (e.g., via PDCCH monitoring / reception) is to be performed 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, for example, stop monitoring the PDCCH on the BWP based on / in response to receiving the first DCI 3308. Stopping monitoring the PDCCH on the BWP may include stopping monitoring the PDCCH on one or more SSSGs configured on the BWP. The wireless device 3304 may maintain the active state of the BWP. The first DCI 3308 may not indicate an active BWP switching. The base station 3302 may not send / transmit a PDCCH transmission to the wireless device 3304, for example, within / during the time window 3316 (or while a timer associated with the time window 3316 is running).

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

[0316] The base station may (e.g., periodically) send / transmit one or more SSBs to a wireless device or multiple wireless devices. The wireless device (in RRC idle state, RRC inactive state, or RRC connected state) may use one or more SSBs to synchronize time and frequency with the cell of the base station. The SSBs may include PSS, SSS, PBCH, and / or PBCH DM-RS (e.g., as described in relation to Figure 11A As described above). The SSB may occupy a certain number / number (e.g., 4 or any other number) of OFDM symbols. The base station may send / transmit one or more SSBs in an SSB burst (e.g., to enable beam sweeping of PSS / SSS and PBCH). An SSB burst may include a group of SSBs, where each SSB may be transmitted via a corresponding different beam. The SSBs in an SSB burst may be transmitted using time division multiplexing. The 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 the first half or in the second half of a radio frame (e.g., having a duration of 10 ms or any other duration). An SSB burst may equivalently be referred to as a transmission window (e.g., 5 ms or any other duration) for transmitting a group of SSBs.

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

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

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

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

[0321] The base station may send / transmit an RRC message (e.g., a SIB1 message) indicating cell-specific configuration parameters for SSB transmission. The cell-specific configuration parameters may include a value for a transmission periodicity of an SSB burst (e.g., a parameter ssb-PeriodicityServingCell) and a position (e.g., presence) of an SSB (e.g., an active SSB) among a plurality of candidate SSBs in an SSB burst. The plurality of candidate SSBs (e.g., a starting symbol of a candidate SSB) may be as described with respect to Figure 34 The cell-specific configuration parameter may include an indication of the position of the SSB in 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 position / presence of the SSB in the SSB burst.

[0322] Carrier frequency f c and SCS may determine the maximum number of candidate SSBs in an SSB burst (e.g., as described with respect to Figure 34 The position indication (e.g., parameter ssb-PositionsInBurst) may indicate which of a plurality of candidate SSBs is to be sent / transmitted in an SSB burst (e.g., as described in relation to Figure 36 The base station may indicate the active SSBs and / or the number of active SSBs transmitted in an SSB burst using a position indication (e.g., parameter ssb-PositionsInBurst). The position indication may be transmitted by the base station, for example, via an RRC message and / or DCI.

[0323] Figure 36 An example of an SSB transmission by a base station is shown. The indication of the SSB position may be in the form of an indication of the presence of an SSB group in a plurality of SSB groups. Each group may include a subset of a plurality of candidate SSBs in an SSB burst (e.g., a maximum possible number of candidate SSBs). For example, the maximum possible number of candidate SSBs in an SSB burst may be equal to 64 (e.g., for SCS = 120 kHz or 240 kHz, and f c> 6 GHz). Candidate SSBs in an SSB burst may include SSBs with indices 0 to 63. Candidate SSBs in an SSB burst may be divided into SSB groups.

[0324] The first bitmap (e.g., parameter groupPresence) may include a number of bits (e.g., 8 or any other number). The first bitmap may be configured / indicated by the SIB1 message. Each bit of the first bitmap may correspond to a corresponding group in the SSB group. Figure 36 As shown in FIG, the first bit (e.g., the leftmost bit of the first bitmap) may correspond to the first SSB group including the first SSB (with SSB index 0), the second SSB (with SSB index 1), ..., and the 8th SSB (with SSB index 7). The second bit (e.g., the second bit of the first bitmap) may correspond to the second SSB group including the 9th SSB (with SSB index 8), the 10th SSB (with SSB index 9), ..., and the 16th SSB (with SSB index 15). The last bit (e.g., the rightmost bit of the first bitmap) may correspond to the 8th SSB group including the 57th SSB (with SSB index 56), the 58th SSB (with SSB index 57), ..., and the 64th SSB (with SSB index 63), and so on. An SSB may belong to or correspond to at most one SSB group in the first SSB group. A bit of the first bitmap may indicate whether the base station may send / transmit the SSB group corresponding to that bit in an SSB burst. A bit set to a first value (e.g., 1) may indicate that the corresponding SSB group may be sent / transmitted by the base station in an SSB burst. A bit set to the second value (eg, 0) may indicate that the corresponding SSB group is not sent / transmitted by the base station in an SSB burst, or vice versa.

[0325] The second bitmap (e.g., parameter inOneGroup) may include a number of bits (e.g., 8 or any other number). Each bit of the second bitmap may correspond to a corresponding group in the SSB group. The first bit (e.g., the leftmost bit of the second bitmap) may correspond to the first SSB group including the first SSB (with SSB index 0), the second SSB (with SSB index 8), ..., and the 8th SSB (with SSB index 56). The second bit (e.g., the second bit of the second bitmap) may correspond to the second SSB group including the first SSB (with SSB index 1), the second SSB (with SSB index 9), ..., and the 8th SSB (with SSB index 57). The last bit (e.g., the rightmost bit of the second bitmap) may correspond to the 8th SSB group including the first SSB (with SSB index 7), the second SSB (with SSB index 15), ..., and the 8th SSB (with SSB index 63), and so on. An SSB may belong to or correspond to at most one SSB group in the second SSB group. A bit of the second bitmap may indicate whether the base station can transmit the SSB group corresponding to that bit in an SSB burst. A bit set to a first value (e.g., 1) may indicate that the corresponding SSB group is sent / 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 sent / transmitted by the base station in an SSB burst, or vice versa.

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

[0327] Not all bits of the first and second bitmaps may be considered for determining whether to send / transmit an SSB group. Figure 34 ), the maximum number of SSBs within an SSB burst may be equal to four. The wireless device may determine that the four leftmost bits of a bitmap (e.g., the first bitmap and / or the second bitmap) are significant. The wireless device may ignore the four rightmost bits of the first bitmap and / or the second bitmap.

[0328] like Figure 36 As shown in , 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, send / transmit the SSB having an index {0 1 16 17} in the 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.

[0329] The base station may send / transmit the MIB via the PBCH. The MIB may indicate configuration parameters for wireless devices to monitor the PDCCH for scheduling SIB1 messages (e.g., for CORESET 0). The base station may send / transmit the MIB message with an 80 ms transmission periodicity (or any other first periodicity). The same MIB message may be repeated within 80 ms (depending on the SSB periodicity). The content of the MIB message may be identical within the 80 ms period. The same MIB may be sent / transmitted over all SSBs within an SSB burst. The PBCH transmission (e.g., the MIB) may indicate the absence of an associated SIB1. For example, if the PBCH transmission indicates the absence of an associated SIB1, the wireless device may be directed to / indicate another frequency range from which to search for an SSB associated with SIB1, and the wireless device may assume the absence of an SSB associated with SIB1. The indicated frequency range may be limited to a contiguous spectrum allocation of the same operator in which the SSB was detected.

[0330] The base station may send / transmit SIB1 messages 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 periodicity for SIB1 may be 20 ms (or any other third periodicity). The base station may determine the actual transmission repetition periodicity based on network implementation. For example, for SSB and CORESET reuse mode 1, the SIB1 repetition transmission periodicity may be 20 ms. For example, for SSB and CORESET reuse modes 2 or 3, the SIB1 transmission repetition periodicity may be the same as the SSB period. SIB1 may include information regarding the availability and scheduling of other SIBs (e.g., SIB to system information (SI) message mapping, periodicity, SI window size) and / or an indication of whether one or more SIBs are provided only on demand. If one or more SIBs are provided only on demand, the configuration parameters required for the wireless device to perform SI requests may be indicated in SIB1.

[0331] Due to the limited battery capacity of the wireless device, the base station may enable power saving operation of the wireless device. The base station may, for example, enable power saving operation of the wireless device based on active BWP management (such as Figure 22), SCell sleep mechanisms (such as Figure 28 ), wake-up / go-to-sleep indication (such as Figure 31A and / or Figure 31B ), SSSG switching on active BWP (such as Figure 32A and / Figure 32B ) and / or PDCCH skipping (such as Figure 33 For example, if a power saving operation of a wireless device is instructed (e.g., based on the instructions herein regarding Figure 22 、 Figure 28 、 Figure 31A 、 Figure 31B 、 Figure 32A 、 Figure 32B and / or Figure 33 For example, if the base station is required to periodically send / transmit some downlink signals (e.g., SSB, MIB, SIB1, SIB2, periodic CSI-RS, etc.) that are always on during a certain time period, even if there are no active wireless devices sending / transmitting to and / or receiving from the base station during the time period), from the perspective of the base station, the base station may not be able to save energy (e.g., if the base station is required to periodically send / transmit some downlink signals (e.g., SSB, MIB, SIB1, SIB2, periodic CSI-RS, etc.) that are always on during a certain time period). For example, if the base station transitions a cell to a dormant state by switching the active BWP of the cell to a dormant BWP (e.g., such as with respect to Figure 28 As mentioned above), the base station may need to periodically send / transmit some downlink signals that are always on (for example, SSB, MIB, SIB1, SIB2, periodic CSI-RS, etc.).

[0332] For example, if a base station needs to reduce the periodicity of always-on downlink signal transmissions, the base station may send / transmit an RRC message (e.g., SIB1) indicating a longer periodicity for always-on downlink signal transmissions. The base station may send / transmit an RRC reconfiguration message to wireless devices in a source cell (e.g., each wireless device in the source cell) to indicate a switch to a neighboring cell, for example, before determining to power down (e.g., both the RF module and baseband unit (BBU)) to conserve energy. The wireless devices in the source cell (e.g., each wireless device in the source cell) may perform a 4-step or 2-step RACH procedure to switch to the neighboring cell and then terminate / tear the RRC connection with the source cell. The base station may, for example, power down (RF components, BBU, etc.) after the wireless devices complete the switch procedure to the neighboring cell to conserve energy. For example, given the dynamic and rapidly changing traffic patterns of different wireless devices in 5G systems and / or future systems, sending / transmitting an RRC message indicating a change in the periodicity of the always-on downlink signal and / or sending (e.g., transmitting) an RRC message requesting a switch (to a neighboring cell) may not be effective.

[0333] In at least some wireless communications, network energy saving operations may include turning off some cells with or without beam scanning and / or reducing the periodicity of SSB / SIB1 / SIB2, which may be consistent with, for example, the present disclosure regarding Figure 22 、 Figure 28 、 Figure 31A 、 Figure 31B 、 Figure 32A 、 Figure 32B and / or Figure 33 The power saving operation of the wireless device described above differs. Shutting down a cell (either fully or partially) may negatively impact data transmission latency and / or power consumption during the access process. Existing SSBs can be modified toward a lighter version by carrying no or minimal information, such as the PSS, which may be referred to as "light SSB." This "light SSB" can be combined with other techniques, such as less frequent SSB transmissions (e.g., with a periodicity > 20 msec) and / or "on-demand SSB," where "on-demand SSB" is an SSB transmission triggered by a wireless device via an uplink trigger signal. A base station can send / transmit this "light SSB," and if, for example, a wireless device detects this "light SSB" and attempts to access the network, the wireless device can react by sending / transmitting an uplink trigger signal. The base station can, for example, initiate the transmission of a full-fledged SSB based on receipt of an uplink trigger signal. For example, after receiving the uplink trigger signal, the network can adjust the SSB transmission configuration in response to the wireless device's instructions.

[0334] Network energy saving operations may include BS DTX configuration / mode / state / operation (e.g., similar to radio DRX configurations, such as those described herein with respect to Figure 29 、 Figure 30 、 Figure 31A and / or Figure 31BFor BS DTX operation, the base station may (periodically) power on a cell (or cells) for a first duration and then power off the cells for a second duration. During the first duration while the cells are powered on (or in a first power state / mode), the base station may send / transmit periodic downlink signals (e.g., SIB / SSB / CSI-RS / TRS), a downlink control channel (PDCCH), a downlink shared channel (PDSCH), etc. During the second duration while the cells are powered off (or in a second power state / mode), the base station may reduce the transmission power / bandwidth / beam of the periodic downlink signals, cease transmission of the periodic downlink signals, and / or cease transmission of the PDCCH / PDSCH. The base station may periodically perform DTX operation, for example, by configuring a DTX cycle periodicity, where the periodicity includes a first duration of the powered-on state and a second duration of the powered-off state. The base station may perform a one-time DTX operation, for example, by indicating a duration for the one-time DTX operation, where the duration includes the first duration of the powered-on state and the second duration of the powered-off state.

[0335] In at least some wireless communications, a base station may be in base station DTX mode / operation / configuration for a given cell and operating in a given pattern (e.g., DTX on-duration and DTX off-duration in a DTX cycle). A wireless device may determine to use the base station DTX mode as its DRX mode in the cell. The network may not need to individually configure DRX for each wireless device in the cell. Requiring all wireless devices in the cell to use the same DRX pattern may increase power consumption by the wireless devices. For example, if the DTX on-duration (cell is powered on) is configured with a long period (10 ms, 100 ms, or even longer), wireless devices in the cell (e.g., all wireless devices in the cell) may be required to monitor the PDCCH for the long period, even if one or more wireless devices in the cell have a relatively small amount of data to send / transmit and / or receive during the long period. For example, if the base station is in DTX operation, power consumption by the wireless device may be increased in at least some wireless communications.

[0336] For example, if a base station is in DTX operation, a wireless device may be configured with both a cell-level (and / or base station-level) DTX configuration and a wireless device-specific DRX configuration to further improve power consumption of the wireless device. The wireless device-specific DRX configuration may be configured with / associated with a first pattern (e.g., an on / off cycle) that is different from / associated with a second pattern (e.g., an on / off cycle) of the cell-level DTX configuration. For example, if both cell-level DTX operation and wireless device-specific DRX operation are performed for one or more cells, the wireless device may not be aligned with the base station regarding cell status, PDCCH monitoring, CSI reporting, DRX-related timers, etc. For example, if both cell-level DTX operation and wireless device-specific DRX operation are performed, the 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 latency. The improvements described herein may provide coordinated cell DTX operations and wireless device-specific DRX operations, specifically, coordinated cell status management, PDCCH monitoring, CSI reporting, and / or DRX-related timer management, etc., to reduce power consumption of wireless devices and / or base stations, to reduce uplink interference, and / or to reduce data transmission delays.

[0337] A wireless device may determine that a cell is in a first power state (e.g., a powered-on state or a first power mode) after / based on receiving a first message indicating configuration parameters for a cell DTX configuration / operation, and, for example, before receiving a second message indicating activation of 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, for example, before sending / transmits 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. For example, if cell-level DTX operation is configured and not yet enabled, the wireless device may align with the base station regarding whether the cell is in a powered-on state (or the first power state / mode) or a powered-off state (or the second power state / mode). Aligning the cell's (power) state / mode between the wireless device and the base station may provide advantages such as improved power consumption for the wireless device and / or improved CSI reporting quality.

[0338] Radio-specific DRX operation may be enabled for a first duration while the cell is in a DTX-on duration of the cell's DTX configuration, and / or disabled (e.g., not performed) for a second duration while the cell is in a DTX-off duration of the cell's DTX configuration. For example, if a first time slot is within the DTX-on duration of the cell, enabling / performing radio-specific DRX operation may include starting a DRX-on duration timer for radio-specific DRX operation in the first time slot. For example, if a second time slot is within the DTX-off duration of the cell, disabling / not performing radio-specific DRX operation may include stopping / disabling the DRX-on duration timer for radio-specific DRX operation in the second time slot. Enabling radio-specific DRX operation during the time the cell is in a DTX-on state (and / or disabling / not performing radio-specific DRX operation during the time the cell is in a DTX-off state) may provide advantages such as improved power consumption and / or more efficient use of resources.

[0339] The wireless device may switch from the RRC Idle state to the RRC Active state without having received a network power saving indication for the cell from the base station. Determining whether the cell is in a non-power saving state, for example, by the wireless device before receiving a MAC CE / DCI indicating activation of the DTX mode, may include the cell periodically powering on for a first period and then powering off for a second period. For example, if the wireless device is in a DRX-off state when the base station submits the network power saving indication in the DCI, the network power saving states of the cell between the wireless device and the base station may be misaligned. For example, the wireless device monitors the PDCCH for DCI with an RNTI dedicated for the network power saving indication, regardless of whether the wireless device is in a DRX-active state. Wireless device power consumption may increase based on the wireless device being in a DRX-active state, which may occur due to a running DRX On Duration timer. If the wireless device receives a network power saving indication, the DRX On Duration timer may be stopped, for example, by the wireless device. If the cell is in a powered-off state based on the cell's DTX configuration, the DRX On Duration timer may be stopped, for example, by the wireless device. If the timer is not running while the cell is in a powered-on state based on the cell's DTX configuration, the DRX On Duration timer may be started, for example, by the wireless device. For example, if a wireless device is configured with multiple DRX cell groups, where each cell group (e.g., each cell group) is configured with a cell group-specific DRX configuration, the wireless device may have difficulty determining whether to apply a network power saving indication. One or more of the multiple DRX cell groups may be determined by the wireless device based on, for example, at least one of: the first cell on which the network power saving indication was received; the content of the network power saving indication; and / or other factors. Operating in the manner described herein may provide advantages such as energy / bandwidth savings, indicating cell DTX status to the wireless device, coordinating DTX and DRX, and / or more efficient use of communication resources.

[0340] In at least some wireless technologies, network energy saving operations may include turning off some cells with or without beam scanning and / or reducing the periodicity of SSB / SIB1 / SIB2, which may be consistent with, for example, the present disclosure regarding Figure 22 、 Figure 28 、 Figure 31A 、 Figure 31B 、 Figure 32A 、 Figure 32B and / or Figure 33The power saving operation of the wireless device described is different. Turning off a cell (full or partial) may negatively impact data transmission latency and / or power consumption during the access process. Another option may include modifying the SSB to a lighter version by carrying no or minimal information, such as the PSS, which may be referred to as "light SSB." This "light SSB" can be combined with other techniques, such as less frequent SSB transmissions (e.g., with a periodicity > 20 msec) or "on-demand SSB," where "on-demand SSB" is an SSB transmission triggered by the UE via an uplink trigger signal. For example, a base station may transmit this "light SSB," and if a wireless device detects this "light SSB" and attempts 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 a full-fledged SSB. In an example, after receiving the uplink trigger signal, the network may adjust the SSB transmission configuration in response to the wireless device's instructions.

[0341] A base station may be equipped with multiple transmission reception points (TRPs) to improve spectral efficiency and / or transmission robustness. The base station may transmit DL signals / channels via multiple TRPs within a cell and / or via multiple TRPs between cells. A base station may be equipped with more than one TRP. The first TRP may be physically located at a different place from the 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), the backhaul link being an ideal backhaul link with zero or negligible transmission delay, or the backhaul link being a non-ideal backhaul link. The first TRP may be implemented with antenna elements, RF chains, and / or baseband processors that are independently configured / managed from the second TRP.

[0342] Figure 37A and Figure 37B An example of multiple transmission and reception point (TRP) configurations is shown. Figure 37A This section illustrates an example of intra-cell TRP-based communication between a base station (equipped with multiple TRPs) and a wireless device (equipped with a single panel or multiple panels). Utilizing multiple TRPs for transmission and reception can improve system throughput and / or transmission robustness for high-frequency (e.g., above 6 GHz) wireless communications. Multiple TRPs can be associated with the same physical cell identifier (PCI). Multiple TRPs sharing a cell's PDCCH / PDSCH / PUCCH / PUSCH resources are referred to as intra-cell TRPs (or intra-PCI TRPs).

[0343] A TRP among a plurality of TRPs of a base station may be indicated / identified by at least one of the following: a TRP identifier (ID); a virtual cell index; or a reference signal index (or group index). In an example, in a cell, a TRP may be indexed by a control resource set (core set) group (or pool) of a core set group (e.g., Figure 26 The TRP may be identified by a CORESETPoolIndex (shown in FIG. 1 ) on a core set from the core set group on which DCI is transmitted from the base station. 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 for a TCI state group. The TCI state group may include at least one TCI state used by a wireless device to receive a downlink TB or by a base station to transmit a downlink TB.

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

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

[0346] For a ControlResourceSet without a CORESETPoolIndex, the wireless device may assume (or determine) that the ControlResourceSet is assigned a CORESETPoolIndex of 0. For example, if the wireless device is scheduled using fully / partially / non-overlapping PDSCH in the time and frequency domains, the scheduling information for receiving the PDSCH is indicated and carried only by the corresponding PDCCH. It is expected that the wireless device will schedule using the same active BWP and the same SCS. When the wireless device is scheduled using fully / partially overlapping PDSCH in the time and frequency domains, the wireless device may schedule using up to two codewords simultaneously.

[0347] For example, if the PDCCHs that schedule two PDSCHs are associated with different ControlResourceSets with different CORESETPoolIndex values, the wireless device may be allowed to perform the following operations: for any two HARQ process IDs in a given scheduled cell, if the wireless device is scheduled to receive a first PDSCH starting with symbol j via a PDCCH associated with a value of CORESETpoolIndex that ends with symbol i, the wireless device may be scheduled to receive a PDSCH that starts earlier than the end of the first PDSCH using a PDCCH associated with a different value of CORESETpoolIndex that ends later than symbol i; in the given scheduled cell, the wireless device may receive the first PDSCH in time slot i, where the corresponding HARQ-ACK is assigned to be transmitted in time slot j; and a second PDSCH associated with a CORESETpoolIndex value different from the value of the first PDSCH, which starts earlier than the first PDSCH, where its corresponding HARQ-ACK is assigned to be transmitted in a time slot prior to time slot j.

[0348] For example, if a wireless device configured by a higher layer parameter PDCCH-Config contains two different values of CORESETPoolIndex in a 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 ports of the PDSCH associated with the value of CORESETPoolIndex of the serving cell are quasi-co-located with one or more RSs relative to one or more QCL parameters for the quasi-co-location indication of the PDCCH of the CORESET associated with the monitored search space with the lowest CORESET-ID in the CORESET, the CORESET configured with the same CORESETPoolIndex value as the PDCCH scheduling the PDSCH in the latest timeslot in which one or more CORESETs associated with the same CORESETPoolIndex value as the PDCCH scheduling the PDSCH within the active BWP of the serving cell are monitored by the wireless device. For example, if the offset between the reception of the DL DCI and the corresponding PDSCH is less than the threshold timeDurationForQCL, and at least one configured TCI state of the serving cell on which the PDSCH is scheduled contains 'QCL-TypeD', and at least one TCI code point indicates two TCI states, the wireless device may assume that the DM-RS ports of the PDSCH of the serving cell are quasi-co-located with one or more RSs relative to one or more QCL parameters associated with the TCI state corresponding to the lowest code point among the TCI code points containing two different TCI states.

[0349] Figure 37BAn example of communication between a base station (equipped with multiple TRPs) and a wireless device (equipped with a single panel or multiple panels) based on an inter-cell TRP (or inter-PCI TRP) is shown. In this case, the multiple TRPs can be associated with different PCIs. The multiple TRPs can be associated with (or belong to) different physical cells (cell 1 with PCI 1 and cell 2 with PCI 2), which can be referred to as inter-cell TRPs (or inter-PCI TRPs). The cell can be a serving cell or a non-serving (neighboring) cell of the wireless device. The base station can configure cell 2 with PCI 2 as a part of cell 1 with PCI 1 (e.g., a second TRP with a second PCI different from the first PCI of the first TRP), in which case, for example, if the inter-cell TRP of the wireless device is operated, the wireless device can receive a first SSB from cell 1 with PCI 1 and a second SSB from cell 2 with PCI 2. The first SSB and the second SSB can have different configuration parameters, where the configuration parameters can be such as those described herein with respect to Figure 34 、 Figure 35 and / or Figure 36 With inter-cell TRP, a wireless device may receive PDCCH / PDSCH and / or transmit PUCCH / PUSCH in different TCI states on cell 1 with PCI 1 and cell 2 with PCI 2 (e.g., one associated with one of the first SSBs, the other associated with one of the second SSBs, etc.).

[0350] A serving cell may be a cell (e.g., PCell, SCell, PSCell, etc.) on which a wireless device receives SSB / CSI-RS / PDCCH / PDSCH and / or transmits PUCCH / PUSCH / SRS, etc. A serving cell may be identified by a serving cell index (e.g., ServCellIndex or SCellIndex configured in an RRC message). A non-serving (or neighboring) cell may be a cell on which a wireless device does not receive PDCCH / PDSCH and / or does not transmit PUCCH / PUSCH / SRS, etc. A non-serving cell may have a physical cell identifier (PCI) different from that of a serving cell. A non-serving cell may not be identified by a serving cell index (e.g., ServCellIndex or SCellIndex). For example, if the TCI state of the serving cell is associated with the SSB of the non-serving cell (e.g., in the TCI state IE of TS 38.331), the wireless device may rely on the SSB of the non-serving cell for Tx / Rx beam (or spatial domain filter) determination (for the PDCCH / PDSCH / PUCCH / PUSCH / CSI-RS / SRS, etc. of the serving cell). The base station may not transmit an RRC message to configure the PDCCH / PDSCH / PUCCH / PUSCH / SRS resources of the non-serving cell of the wireless device.

[0351] For a particular wireless device, cell 1 may be a serving cell and may be associated with a first TRP (TRP 1). Cell 2 may be a non-serving (or neighboring) cell and may be associated with a second TRP. The base station may transmit 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 IE) for multiple (non-serving or neighboring) cells of cell 1. Each additional PCI configuration corresponds to a (non-serving or neighboring) cell having a PCI value different from that of the serving cell and includes: an additional PCI index (AdditionalPCIIndex) identifying the additional PCI configuration; the PCI of the non-serving cell; an SSB periodicity indication; an indication of the position of a (candidate) SSB in an SSB burst; an indication of the transmit power of the SSB; and the like. The configuration parameters for cell 1 may also indicate multiple TCI states. For example, if the SSB is transmitted via cell 1 (or in another serving cell), the 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 multiple QCL types. For example, if the SSB of the TCI state is transmitted via a non-serving (neighboring) cell, the TCI state may also be associated with an additional PCI index (AdditionalPCIIndex) indicating the (non-serving or neighboring) cell configured in the SSB-MTC-AdditionalPCI IE. Similar to multiple TRPs within a cell, the wireless device may receive downlink signals and / or transmit uplink signals based on the TCI state (activated / indicated) associated with the TRP. The difference between multiple TRPs within a cell and multiple TRPs between cells may be that, for the latter case, the reference RS for the TCI state of the serving cell may come from the (non-serving or neighboring) cell (or transmitted via the cell). The SSB may be based on the information provided herein regarding Figure 34 、 Figure 35 and / or Figure 36 The examples described are implemented.

[0352] 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 for 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 cells and non-serving / neighboring cells.

[0353] The base station may use two TRPs for transmission to the wireless device via cell 1. The base station may indicate (via a DCI / MAC CE) a first TCI state associated with an SSB / CSI-RS transmitted via cell 1 (or another serving cell) for the first transmission to the wireless device (via the PDCCH / PDSCH / PUSCH / PUCCH / SRS resources of cell 1). The base station may indicate (via the same DCI / MAC CE or another DCI / MAC CE) a second TCI state associated with a second SSB transmitted via cell 2 (which is a non-serving / neighboring cell indicated by the AdditionalPCIIndex in the TCI configuration parameter) for the second transmission to the wireless device (via the 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 can be from the serving cell and the other can be from a non-serving / neighboring cell) can avoid performing a time-consuming handover (HO) between cell 1 and cell 2 and improve coverage if the wireless device is moving at the edge of cell 1 and cell 2.

[0354] The wireless device may be provided with two TCI states, each TCI state corresponding to a TRP in a plurality of TRPs (e.g., such as Figure 37A and Figure 37B When a TCI state is used for a specific channel (e.g., PDSCH / PDCCH / PUCCH / PUSCH), the TCI state may be referred to as a channel-specific TCI state, where different channels may be associated with different channel-specific TCI states. When a TCI state is used for multiple channels (e.g., PDSCH / PDCCH / PUCCH / PUSCH), the TCI state may be referred to as a unified TCI state, where different channels may be associated with the same unified TCI state. The base station may transmit an RRC message indicating whether the TCI state is the unified TCI state for the wireless device.

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

[0356] In at least some techniques, a base station may, due to the limited battery capacity of a wireless device, for example, based on BWP management (e.g., such as regarding Figure 22 described above), SCell sleep mechanisms (e.g., such as Figure 28 as described), wake-up / go-to-sleep instructions (e.g., such as Figure 31A and / or Figure 31B ), SSSG switching on active BWP (e.g., such as Figure 32A and / Figure 32B described) and / or PDCCH skipping (e.g., such as Figure 33 as described above) to enable power saving operation of the wireless device.

[0357] For example, if a power saving operation of a wireless device is instructed (e.g., such as regarding Figure 22 、 Figure 28 、 Figure 31A 、 Figure 31B 、 Figure 32A 、 Figure 32B and / or Figure 33 As described above), from the perspective of the base station, the base station may not be able to save energy, for example, if the base station is required to periodically transmit some always-on downlink signals (e.g., SSB, MIB, SIB1, SIB2, periodic CSI-RS, etc.) within a certain time period, even if there are no active wireless devices transmitting to and / or receiving from the base station during the time period. For example, if the base station transitions a cell to a dormant state by switching the cell's active BWP to a dormant BWP, such as described above with respect to Figure 28 As described above, the base station may be required to periodi...

Claims

1. A method comprising: A medium access control (MAC) control element (CE) is received by the wireless device triggering a layer 1 or layer 2 triggered mobility (LTM) procedure, the MAC CE including: A first field indicating a first cell among a number of candidate cells; and A second field indicating at least one bandwidth part (BWP) of the first cell; and During the LTM procedure, handing over a source cell to the first cell, wherein the handing over comprises: The at least one BWP is activated.

2. The method according to claim 1, further comprising: receiving one or more radio resource control (RRC) messages including configuration parameters of candidate cells for the LTM procedure; receiving, via the MAC CE, a second field including a timing advance command (TAC); as well as An uplink signal is transmitted using the TAC via a primary cell (PCell) and based on handing over the source cell to the first cell of the LTM procedure.

3. The method according to claim 1, further comprising: receiving, via the MAC CE, an indication of a third field indicating a timing advance command (TAC); as well as Switching a primary cell (PCell) from the first cell to a second cell, wherein the switching is based on the second field indicating skipping of a random access (RA) procedure, and wherein the switching comprises: Skip executing the RA procedure; as well as At least one transport block is transmitted based on the TAC and via the second cell.

4. The method according to claim 1, wherein the switching comprises: ceasing to receive downlink transmissions via the source cell; as well as Receiving downlink transmissions via the first cell begins. 5 . The method of claim 1 , wherein the switching further comprises transmitting at least one transport block via the at least one BWP after activating the at least one BWP. 6 . The method according to claim 1 , wherein the MAC CE further comprises a third field indicating whether a random access (RA) procedure is performed on the first cell during the handover. The method according to claim 1 , wherein the handover further comprises releasing configuration parameters of the source cell. 8 . The method of claim 1 , wherein the MAC CE includes a fourth field indicating a synchronization signal block (SSB) index.

9. The method of claim 1 , further comprising performing an RA procedure comprising at least one of: transmitting a preamble to the first cell; monitoring a physical downlink control channel (PDCCH) for receiving a random access response (RAR) corresponding to a preamble; receiving the RAR during the monitoring of the PDCCH; or The RA procedure is completed based on receiving the RAR. 10 . The method of claim 1 , further comprising performing an RA procedure on the first cell based on a fourth field indicating an SSB index.

11. The method of claim 1 , wherein the transmitting the at least one transport block comprises transmitting the at least one transport block via a physical uplink shared channel (PUSCH), via a primary cell (PCell), and using TAC-based uplink timing adjustment.

12. A method comprising: receiving, by the wireless device and via the source cell, one or more radio resource control (RRC) messages including configuration parameters of candidate cells for a layer 1 or layer 2 triggered mobility (LTM) procedure; Receiving a medium access control (MAC) control element (CE) that triggers the LTM procedure, wherein the MAC CE includes: a first field comprising a first number of bits indicating a first candidate cell among the candidate cells, wherein the first number of bits corresponds to the number of the candidate cells; as well as The second field includes a timing advance command (TAC); and An uplink signal is transmitted using the TAC via a primary cell (PCell) and the first candidate cell based on a handover from a source cell to the LTM procedure. 13 . The method of claim 12 , wherein the MAC CE includes a third field indicating a Transmission Configuration Indication (TCI) status, wherein the wireless device transmits the uplink signal based on the TCI status.

14. The method of claim 12, wherein the switching from the source to the first candidate cell comprises: ceasing to receive downlink transmissions via the source cell; as well as Receiving downlink transmissions via the first candidate cell begins.

15. The method of claim 12, wherein the switching from the source cell to the first candidate cell comprises releasing configuration parameters of the source cell.

16. The method of claim 12, wherein the transmitting the at least one transport block comprises transmitting the at least one transport block via a physical uplink shared channel (PUSCH), via the PCell, and using uplink timing adjustment based on the TAC.

17. A method comprising: receiving, by the wireless device via the first cell, one or more parameters of a first number of candidate cells for a layer 1 or layer 2 triggered mobility (LTM) procedure; receiving a control element that triggers the LTM program, the control element comprising: a first field comprising a second number of bits indicating a second cell of the first number of candidate cells, wherein the second number is determined based on the first number; A second field indicating whether to skip a random access (RA) procedure for the second cell; and The third field indicates the timing advance command (TAC); Switching a primary cell (PCell) from the first cell to the second cell, wherein the switching is based on the second field indicating skipping of performing the RA procedure, and wherein the switching comprises: skipping execution of the RA procedure; and At least one transport block is transmitted based on the TAC and via the second cell.

18. The method according to claim 17, wherein the switching from the first cell to the second cell comprises: ceasing to receive downlink transmissions via the first cell; as well as Receiving downlink transmissions via the second cell begins. The method of claim 17 , wherein the switching from the first cell to the second cell comprises releasing configuration parameters of the first cell.

20. The method of claim 17, wherein the MAC CE includes a third field indicating a first bandwidth part (BWP) among a plurality of BWPs of the first candidate cell.

Images