Power headroom reporting for fast primary cell switching

Abstract

A wireless device may receive a message indicating to switch cells, such as in a handover process, and the wireless device may take steps to switch cells. The time required to perform the switch may depend, for example, on the time it takes the wireless device to process the message, with different types of messages (e.g., messages at the Media Access Control—MAC—layer) being processed more quickly than others. The wireless device may quickly cancel a triggered Power Headroom Report (PHR) procedure for the old cell and trigger a PHR for the new cell based on receipt of such a message. The canceling and / or triggering may be performed without resetting the MAC entity of the wireless device.

Description

[Background technology]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to U.S. Provisional Patent Application No. 63 / 411,578, entitled "Power Headroom Report for Fast Primary Cell Switching," filed September 29, 2022, the contents of which are incorporated herein by reference in their entirety.

[0002] A wireless device, such as a mobile phone, may perform power headroom reporting to report the power characteristics of its transmissions. In the case of a handover, the wireless device may receive a radio resource configuration (RRC) message regarding the handover, and based on the RRC message, the wireless device may instruct its own medium access control (MAC) layer to cancel scheduled power headroom reporting in preparation for the handover. Summary of the Invention

[0003] The features described herein enable a wireless device to improve the speed at which it can process its power headroom report in a situation involving a handover from a source cell to another candidate cell. A MAC Control Element (CE) may be used to notify the radio of the handover (e.g., that the wireless device should switch from using the source cell as a primary cell (PCell) to using the candidate cell as the PCell). A power headroom report that was triggered but not yet transmitted to the source cell may be canceled by the wireless device based on the MAC CE. The power headroom report may be triggered on the candidate cell instead of the source cell. Processing this cancellation based on the MAC CE from the source cell may save time because processing of the MAC CE may be performed without waiting for receipt and processing of an RRC message.

[0004] The above summary provides a simplified overview of certain features. It is not an extensive overview and is not intended to identify key or critical elements. These and other features and advantages are described in more detail below.

[0005] Some examples of various embodiments of the present disclosure are described herein with reference to the drawings. [Brief explanation of the drawings]

[0006] [Figure 1A] 1 illustrates an exemplary communication network. [Figure 1B] 1 illustrates an exemplary communication network. [Figure 2A] 1 illustrates an exemplary user plane. [Figure 2B] 1 illustrates an exemplary control plane configuration. [Figure 3] 1 shows an example of a protocol layer. [Figure 4A] 1 illustrates an exemplary downlink data flow for a user plane configuration. [Figure 4B] 1 illustrates an example format of a media access control (MAC) subheader of a MAC protocol data unit (PDU). [Figure 5A] 1 illustrates an exemplary mapping of downlink channels. [Figure 5B] 1 illustrates an exemplary mapping of uplink channels. [Figure 6] 1 illustrates exemplary radio resource control (RRC) states and RRC state transitions. [Figure 7] 1 shows an exemplary configuration of a frame. [Figure 8] 1 illustrates an example resource configuration for one or more carriers. [Figure 9] 1 illustrates an exemplary configuration of a bandwidth portion (BWP). [Figure 10A] 1 illustrates an exemplary carrier aggregation configuration based on component carriers. [Figure 10B] 1 shows an exemplary group of cells. [Figure 11A] 1 illustrates an exemplary mapping of one or more synchronization signal / physical broadcast channel (SS / PBCH) blocks. [Figure 11B] 1 illustrates an example mapping of one or more channel state information reference signals (CSI-RS). [Figure 12A] 1 shows an example of a downlink beam management procedure. [Figure 12B] An example of an uplink beam management procedure is shown. [Figure 13A] 1 illustrates an exemplary four-step random access procedure. [Figure 13B] 1 illustrates an exemplary two-step random access procedure. [Figure 13C] 1 illustrates an exemplary two-step random access procedure. [Figure 14A] 1 shows an example of a control resource set (CORESET) configuration. [Figure 14B] 1 shows an example of a mapping of control channel elements to resource element groups (CCE to REG). [Figure 15A] 1 illustrates an example of communication between a wireless device and a base station. [Figure 15B] 1 illustrates exemplary elements of a computing device that may be used to implement any of the various devices described herein. [Figure 16A] 1 illustrates an example of uplink and downlink signal transmission. [Figure 16B] 1 illustrates an example of uplink and downlink signal transmission. [Figure 16C] 1 illustrates an example of uplink and downlink signal transmission. [Figure 16D] 1 illustrates an example of uplink and downlink signal transmission. [Figure 17] FIG. 1 illustrates a wireless device implementing an exemplary initial access procedure. [Figure 18] 10 is a table showing an example for determining a starting OFDM symbol index. [Figure 19]FIG. 1 illustrates an exemplary synchronization signal block (SSB) transmission of a cell, according to some embodiments. [Figure 20] FIG. 1 illustrates an exemplary SSB location indication in an SSB burst. [Figure 21A] FIG. 1 illustrates exemplary configuration parameters of a cell's Master Information Block (MIB). [Figure 21B] FIG. 10 is a diagram illustrating an example of the configuration of CORESET#0. [Figure 21C] FIG. 10 is a diagram illustrating an example of the configuration of SS#0. [Figure 22] FIG. 1 illustrates exemplary RRC configuration parameters for a system information block (SIB). [Figure 23] A figure showing an example of RRC configuration parameters (e.g., BWP-DownlinkCommon IE) in the initial downlink BWP of a serving cell. [Figure 24] FIG. 10 is a diagram illustrating an example of a search space configuration. [Figure 25] FIG. 10 is a diagram illustrating an example of BWP switching on a cell. [Figure 26] 1 is a table showing an example of a DCI format. [Figure 27] FIG. 1 illustrates an example embodiment of transitioning between dormant and non-dormant states on a SCell. [Figure 28A] 1 shows an example of a downlink (DL) MAC PDU. [Figure 28B] 1 shows an example of an uplink (UL) MAC PDU. [Figure 29A] 1 shows an example of a MAC subheader with an R field (reserved bit), an F field (flag bit), a logical channel identification (LCID) field, and an L field. [Figure 29B] 1 shows an example of a MAC subheader with R, F, LCID, and L fields. [Figure 29C] An example of such a MAC subheader is shown below, with the R and LCID fields, but without the L field. [Figure 30A]1 is a table illustrating an example of one or more MAC CEs identified by corresponding codepoints / indexes of an LCID. [Figure 30B] 1 is a table illustrating an example of one or more MAC CEs identified by corresponding codepoints / indexes of an LCID. [Figure 31A] An example of a 1-octet secondary cell (SCell) activation / deactivation MAC CE is shown below. [Figure 31B] An example of a 4-octet SCell activation / deactivation MAC CE is shown below. [Figure 32A] FIG. 1 illustrates two exemplary power headroom reports (PHRs). [Figure 32B] FIG. 1 illustrates an exemplary MAC subheader and corresponding MAC CE for carrying a PHR. [Figure 33A] 1 shows an example of a single-input PHR MAC CE. [Figure 33B] 1 shows an example of a multiple-input PHR MAC CE. [Figure 33C] 1 shows an example of a multiple-input PHR MAC CE. [Figure 34A] FIG. 1 illustrates an example of communication between a base station and a wireless device based on intra-cell transmission / reception points (TRPs). [Figure 34B] FIG. 1 illustrates an example of communication between a base station and a wireless device based on inter-cell TRP. [Figure 35] FIG. 1 illustrates an exemplary handover (HO) procedure. [Figure 36] FIG. 1 illustrates an exemplary RRC message for HO. [Figure 37] FIG. 1 illustrates an exemplary conditional handover (CHO) procedure. [Figure 38] 10 shows an example of an RRC message for CHO. [Figure 39] FIG. 1 illustrates an exemplary layer 1 / 2 triggered HO procedure. [Figure 40] 1 illustrates an exemplary Inter-Cell Beam Management (ICBM) procedure. [Figure 41]FIG. 1 illustrates an example of dynamic PCell switching for network energy saving. [Figure 42] 1 is a flow diagram of a method for triggering a PHR based on fast PCell switching (eg, based on L1 or L2 signaling). DETAILED DESCRIPTION OF THE INVENTION

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0045] The PHY layer may generate physical signals to support the low-level operations of the PHY layer, which may be similar to physical control channels. As shown in Figures 5A and 5B, the physical layer signals (which may be defined, for example, by an NR configuration or any other configuration) may include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DM-RS), an SRS, a phase tracking reference signal (PT RS), and / or any other signals.

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

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

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

[0049] 6 illustrates exemplary RRC states and RRC state transitions. The RRC state of a wireless device may be changed to another RRC state (e.g., RRC state transitions of a wireless device). The wireless device may be substantially identical to or similar to wireless device 106, 210, or any other wireless device. The wireless device may be in at least one of a plurality of states, such as three RRC states including RRC connected 602 (e.g., RRC_CONNECTED), RRC idle 606 (e.g., RRC_IDLE), and RRC inactive 604 (e.g., RRC_INACTIVE). RRC inactive 604 may be RRC connected but inactive.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0122] The wireless device may send / transmit a third message (e.g., Msg 3 1313), for example, based on (e.g., subsequently to, or in response to) 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 an RAR corresponding to the wireless device. Collisions may occur, for example, when multiple wireless devices interpret the RAR as corresponding to itself. Contention resolution (e.g., using the third message (e.g., Msg 3 1313) and the fourth message (e.g., Msg 4 1314)) may be used to increase the likelihood that a wireless device does not mistakenly use the identification information of another wireless device. The wireless device may include a device identifier in a third message (e.g., Msg3 1313) (e.g., the C-RNTI, if assigned, the TC RNTI included in the second message (e.g., Msg2 1312), and / or any other suitable identifier) ​​to, for example, perform contention resolution.

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

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

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

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

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

[0128] 13C shows an exemplary two-step random access procedure. Similar to the random access procedures shown in FIGS. 13A and 13B, the base station may send / transmit a configuration message 1330 to the wireless device prior to initiating the procedure. The configuration message 1330 may be similar in some respects to the configuration message 1310 and / or the configuration message 1320. The procedure shown in FIG. 13C may include the transmission of multiple messages (e.g., two messages including a first message (e.g., Msg A 1331) and a second message (e.g., Msg B 1332)).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0164] FIG. 17 is a diagram 1700 illustrating a wireless device (e.g., wireless device 106 of FIG. 1A or UE 156 of FIG. 1B) performing an exemplary initial access procedure to transition from an RRC idle state 1702 (e.g., RRC IDLE 606 of FIG. 6) to an RRC connected state 1704 (e.g., RRC CONNECTED 602 ​​of FIG. 6), where an RRC connection is established between the wireless device and a base station, e.g., with a serving cell (e.g., Primary Cell (PCell)) of the base station.

[0165] In one example, as part of the initial access procedure, the wireless device may perform downlink synchronization 1706 to receive from the base station based on the SSB 1720 (e.g., as illustrated in FIG. 11A and further described below). The wireless device may receive, via the PBCH, a master information block (MIB) that indicates (e.g., configures) CORESET#0 1722 (e.g., CORESET with index #0) of the initial DL BWP 1724 (e.g., with index #0 denoted as DL BWP#0), from which the wireless device may receive (e.g., acquire) SIB1 1708. In one example, SIB1 1708 may configure (indicative configuration parameters of) an initial DL BWP 1724 and / or an initial UL BWP 1726 (e.g., having index #0 denoted as UL BWP #0) where the wireless device performs random access 1710 (e.g., as illustrated in Figures 13A, 13B, and / or 13C) to establish an RRC connection with the base station's serving cell, after which the wireless device enters the RRC connected state 1704. For example, the wireless device may perform random access 1710 to request RRC connection setup using the initial DL / UL BWP configuration of SIB1. The base station may configure the frequency domain location and bandwidth of the initial DL BWP 1724 in SIB1 such that the initial DL BWP 1724 includes CORESET#0 1722 in the frequency domain.

[0166] Although diagram 1700 shows an example of an SSB monitored / received to perform initial access, which a wireless device may begin in RRC idle state 1702, SSB 1720 may be used by the wireless device for other purposes. In one example, a base station may periodically transmit / transmit one or more SSBs (such as SSB 1720) to a wireless device or multiple wireless devices. A wireless device (which may be in an RRC idle state, an RRC inactive state, or an RRC connected state) may use one or more SSBs for time and frequency synchronization with the base station's cell (e.g., a serving cell, such as a PCell or PSCell). As described with respect to FIG. 11A , SSBs include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a physical broadcast channel (PBCH), and / or a PBCH DM-RS. An SSB may occupy several (e.g., four) OFDM symbols as shown in FIG. 11A . A base station may transmit one or more SSBs in an SSB burst to enable beam sweeping, for example, for PSS / SSS and PBCH. An SSB burst includes a set of SSBs, with each SSB potentially transmitted on a different beam. In an SSB burst, the SSBs may be transmitted in a time-division multiplexed manner. In one example, an SSB burst may be limited to a 5-millisecond window and located in either the first or second half of a 10-millisecond radio frame. An SSB burst may be equivalently referred to as a transmission window (e.g., 5 milliseconds) in which a set of SSBs is transmitted.

[0167] The base station may indicate the transmission periodicity of the SSBs via an RRC message (e.g., ssb-PeriodicityServingCell in the ServingCellConfigCommonSIB of the SIB1 message, as shown in Figure 25). For example, candidate values ​​for the transmission periodicity may be in the range of {5 ms, 10 ms, 20 ms, 40 ms, 80 ms, 160 ms}. The maximum number of candidate SSBs in an SSB burst (L max ) may depend on the carrier frequency / band of the (serving) cell. c <=3GHz, L max = 4, where f cis the cell carrier frequency. 3GHz <f c <=6GHz, L max = 8. c >6GHz, L max =64, etc.

[0168] 18 is a table 1800 illustrating an example for determining a starting OFDM symbol index. The starting OFDM symbol index of a candidate SSB (e.g., occupying 4 OFDM symbols) within an SSB burst (5 ms) may depend on the subcarrier spacing (SCS) of the cell and the carrier frequency band. For example, table 1800 illustrates that the starting OFDM symbol index of an SSB in an SSB burst may be determined for a cell with a carrier frequency of 15 kHz and fc<3 GHz (e.g., L max = 4), the OFDM symbols within a half frame are indexed with the first symbol of the first slot being indexed as 0. The starting OFDM symbol index of the SSB in an SSB burst is 15 kHz and the carrier frequency is 3 GHz. <fc<6GHz(L max = 8), the starting positions are 2, 8, 16, 22, 30, 36, 44, and 50. In one example, if the base station is not transmitting SSBs with beamforming, the base station may transmit only one SSB by using the first SSB starting position.

[0169] FIG. 19 is a diagram 1900 that more particularly illustrates an exemplary SSB transmission by a base station. For example, these SSB transmissions may correspond to the SSB transmissions generally described with respect to SSB 1720 of FIG. 17 and / or FIG. 11A. As shown in the exemplary diagram 1900, the SSB transmission may be associated with (e.g., configured with) a subcarrier spacing (SCS) of the cell that is 15 kHz, the cell is configured with 3 GHz < fc <= 6 GHz, and the maximum number of candidate SSBs in an SSB burst is 8 (Lmax = 8). Based on the example of table 1800 of FIG. 18 showing a particular set of this configuration, the SSB start symbol indices may be determined to be 2, 8, 16, 22, 30, 36, 44, and 50. Thus, as shown in FIG. 1900, SSB #1 starts at symbol #2 out of 70 symbols of 5 milliseconds, SSB #2 starts at symbol #8, SSB #3 starts at symbol #16, SSB #4 starts at symbol #22, SSB #5 starts at symbol #30, SSB #6 starts at symbol #36, SSB #7 starts at symbol #44, and SSB #8 starts at symbol 50. As illustrated, the SSB burst is transmitted in the first half of a 10 - millisecond radio frame (not the second half as shown in FIG. 35).

[0170] The SSB burst (and for each SSB of the SSB burst) may be transmitted periodically. In the example of FIG. 19, the default periodicity of the SSB burst is, for example, 20 milliseconds before a wireless device receives the SIB1 message for initial access to the cell. The base station may transmit the SSB burst in the first 5 milliseconds of each 20 - millisecond period with a 20 - millisecond transmission periodicity of the SSB (or SSB burst). In this example, the base station does not transmit the SSB burst in the remaining 15 milliseconds of each 20 milliseconds.

[0171] The base station may transmit one or more RRC messages (e.g., SIB1) indicating cell-specific configuration parameters for SSB transmission. The cell-specific configuration parameters may include a transmission periodicity value for the SSB burst (ssb-PeriodicityServingCell) and the locations of some SSBs (e.g., active SSBs) among multiple candidate SSBs included in the SSB burst. The multiple candidate SSBs may be implemented based on the exemplary embodiment described above with respect to FIG. 18. The cell-specific configuration parameters may include a position indication of the SSBs within the SSB burst (e.g., ssb-PositionsInBurst). The position indication may include a first bitmap (e.g., groupPresence) and a second bitmap (e.g., inOneGroup) indicating the locations of some SSBs included in the SSB burst.

[0172] FIG. 20 is an exemplary diagram 2000 illustrating an exemplary embodiment of SSB location indication in an SSB burst. In diagram 2000, the maximum number of candidate SSBs in an SSB burst is 64. The candidate SSBs may include SSBs with indices 0 through 63. A first bitmap (groupPresence) (configured by the SIB1 message) may include several bits (e.g., 8), each corresponding to a respective SSB group of multiple SSBs (which may be the maximum number of candidate SSBs) in the SSB burst. In the example of FIG. 20, the first bit (e.g., the leftmost bit of the first bitmap) may correspond to the first SSB group, which includes the first SSB (having SSB index 0), the second SSB (having SSB index 1), ..., and the eighth SSB (having SSB index 7). The second bit (e.g., the second bit of the first bitmap) may correspond to a second SSB group including the 9th SSB (having SSB index 8), the 10th SSB (having SSB index 9), ..., and the 16th SSB (having SSB index 15). The last bit (e.g., the rightmost bit of the first bitmap) may correspond to an 8th SSB group including the 57th SSB (having SSB index 56), the 58th SSB (having SSB index 57), ..., and the 64th SSB (having SSB index 63), etc. As illustrated, an SSB may belong to at most one SSB group of the first SSB groups. A bit of the first bitmap may indicate whether the base station transmits the SSB group corresponding to the bit in an SSB burst. For example, setting a bit to a first value (e.g., 1) may indicate that the corresponding SSB group is transmitted by the base station in an SSB burst, and setting a bit to a second value (e.g., 0) may indicate that the corresponding SSB group is not transmitted by the base station in an SSB burst, or vice versa.

[0173] As shown in Figure 20, the second bitmap (inOneGroup) (configured by the SIB1 message) may include several bits (e.g., 8), each corresponding to a respective SSB group of multiple SSBs in the SSB burst. In the example of Figure 20, the first bit (e.g., the leftmost bit of the second bitmap) may correspond to the first SSB group, which includes the first SSB (having SSB index 0), the second SSB (having SSB index 8), ..., and the eighth SSB (having SSB index 56). The second bit (e.g., the second bit of the second bitmap) may correspond to the second SSB group, which includes the first SSB (having SSB index 1), the second SSB (having SSB index 9), ..., and the eighth SSB (having SSB index 57). The last bit (e.g., the rightmost bit of the second bitmap) may correspond to an eighth SSB group including the first SSB (having SSB index 7), the second SSB (having SSB index 15), ..., and the eighth SSB (having SSB index 63), etc. As illustrated, an SSB may belong to at most one SSB group of the second SSB group. A bit of the second bitmap may indicate whether the base station transmits the SSB group corresponding to the bit in an SSB burst. Setting a bit to a first value (e.g., 1) may indicate that the corresponding SSB group is transmitted by the base station in an SSB burst, and setting a bit to a second value (e.g., 0) may indicate that the corresponding SSB group is not transmitted by the base station in an SSB burst, or vice versa.

[0174] As shown in diagram 2000, a plurality of SSBs (e.g., having SSB indices of 0 to 63) may be grouped into a first SSB group for a first bitmap, each SSB including SSBs with consecutive SSB indices. A first SSB group of the first SSB group includes SSBs with SSB indices of 0 to 7, and a second SSB group includes SSB indices of 8 to 15. A plurality of SSBs may also be grouped into a second SSB group for a second bitmap, each SSB including SSBs with non-consecutive SSB indices. A first SSB group of the second SSB group includes SSBs with SSB indices {0, 8, 16, ... 56}, with an SSB index gap between two adjacent SSB indices of 8. A second SSB group of the second SSB group includes SSBs with SSB indices {1, 9, 17, ... 57}, etc.

[0175] If fc≦3 GHz, the maximum number of SSBs in an SS burst may be equal to 4, and the wireless device may determine that the four leftmost bits of the bitmap (e.g., the first bitmap and / or the second bitmap) are valid. The wireless device may ignore the four rightmost bits of the first bitmap and / or the second bitmap.

[0176] In the exemplary diagram 2000, 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}. Based on the grouping configuration of the first SSB group and the second SSB group, the base station may transmit SSBs with indices {0 1 16 17} within an SSB burst.

[0177] As described above with respect to FIG. 17 (and FIG. 11A), a base station may transmit a master information block (MIB) on the PBCH of an SSB 1720 to indicate configuration parameters (e.g., for CORESET#0 1722) for wireless devices monitoring the PDCCH to receive the SIB1 message 1708. The base station may transmit MIB messages with a transmission periodicity of 80 milliseconds (ms). The same MIB message may be repeated within 80 ms (according to the SSB periodicity). The content of the MIB message is the same over the 80 ms period. The same MIB is transmitted across all SSBs in the SS burst. The PBCH may indicate that an associated SIB1 is not present, in which case the wireless device may be designated another frequency on which to search for an SSB associated with SIB1, and a frequency range in which the wireless device may assume that an SSB associated with SIB1 is not present. The indicated frequency range may be limited to within the same operator's contiguous spectrum allocation in which the SSB is detected.

[0178] In one example, a base station may transmit a SIB1 message (e.g., SIB1 1708) with a periodicity of 160 milliseconds. The base station may transmit the same SIB1 message with a variable transmission repetition periodicity within the 160 millisecond period. The default transmission repetition periodicity of SIB1 may be 20 milliseconds. The base station may determine the actual transmission repetition periodicity based on the network implementation. In one example, for SSB and CORESET multiplexing pattern 1, the SIB1 repetition transmission periodicity is 20 milliseconds. For SSB and CORESET multiplexing pattern 2 or 3, the SIB1 transmission repetition periodicity is the same as the SSB periodicity. SIB1 may include information regarding the availability and scheduling of other SIBs (e.g., mapping of SIBs to SI messages, periodicity, SI window size), an indication of whether one or more SIBs are provided only upon request, and, in this case, configuration parameters needed by the wireless device to implement the SI request.

[0179] Figure 21A shows example configuration parameters 2100A of a Master Information Block (MIB) of a cell (e.g., a PCell). A wireless device may receive the MIB via a PBCH based on a Primary Synchronization Signal (PSS) and / or a Secondary Synchronization Signal (SSS), as described with respect to Figures 11A, 17, and 19. The configuration parameters 2100A of the MIB may include a system frame number (SFN) (systemFrameNumber), which may have 6 bits, a subcarrier spacing indication (subCarrierSpacingCommon), a frequency domain offset in number of subcarriers between the SSB and the overall resource block grid (ssb-SubcarrierOffset), an indication of whether the cell is barred (cellBarred), a DMRS position indication (dmrs-TypeA-Position) of the location of the DMRS, CORESET and SS parameters for the PDCCH including the common CORESET (pdcch-ConfigSIB1), a common search space, and required PDCCH parameters, etc.

[0180] The pdcch-ConfigSIB1 configuration parameters may include a first parameter (e.g., controlResourceSetZero) that indicates a common Control Resource Set (CORESET) having ID#0 (e.g., CORESET#0 1722 in FIG. 17) of the cell's initial BWP (e.g., initial DL BWP 1724 in FIG. 17). controlResourceSetZero may be an integer between 0 and 15. Each integer between 0 and 15 may identify a configuration of CORESET#0.

[0181] Figure 21B shows an example configuration 2100B of CORESET#0 (e.g., CORESET#0 1722 of Figure 17). As shown in Figure 21B, based on the integer value of controlResourceSetZero (shown in the "Index" column), the wireless device may determine the SSB and CORESET#0 multiplexing pattern, the number of RBs for CORESET#0, the number of symbols for CORESET#0, and / or the RB offset for CORESET#0.

[0182] FIG. 21C shows an example of a configuration 2100C of SS#0. As shown in FIG. 21C, based on the integer value of searchSpaceZero (shown in the "Index" column), the wireless device may determine one or more parameters (e.g., O, M) for slot determination of PDCCH monitoring, a first symbol index for PDCCH monitoring, and / or the number of search spaces per slot. pdcch-ConfigSIB1 may include a second parameter (e.g., searchSpaceZero) indicating a common search space with ID#0 (e.g., SS#0) of the cell's initial BWP. searchSpaceZero may be an integer from 0 to 15. Each integer from 0 to 15 may identify a configuration of SS#0.

[0183] Based on receiving the MIB (e.g., based on synchronization 1706 of FIG. 17), the wireless device may monitor the PDCCH over SS#0 of CORESET#0 (e.g., CORESET#0 1722) to receive DCI scheduling system information block 1 (SIB1) (e.g., SIB1 1708 of FIG. 17). The wireless device may receive DCI with a CRC scrambled with a system information-radio network temporary identifier (SI-RNTI) dedicated to receiving SIB1.

[0184] FIG. 22 illustrates example RRC configuration parameters 2200 of a system information block (SIB) (e.g., SIB 1708 of FIG. 17). The SIB (e.g., SIB1) may be transmitted via broadcast to (all) wireless devices within range of a base station (or the base station's primary cell). The SIB may include scheduling configuration information relevant when evaluating whether a wireless device is allowed to access a cell, information on paging configuration, and / or other system information. The SIB may include radio resource configuration information that is common to (all) wireless devices and barring information that applies to unified access control. The base station may transmit one or more SIB information messages to a wireless device (or multiple wireless devices). As shown in FIG. 22, parameters of the one or more SIB information messages may include one or more parameters for cell selection (cellSelectionInfo) associated with a serving cell (e.g., an SpCell, such as a PCell), one or more configuration parameters of the serving cell (e.g., in a ServingCellConfigCommonSIB IE), and one or more other parameters. The ServingCellConfigCommonSIB IE may include at least one of common downlink parameters of the serving cell (eg, DownlinkConfigCommonSIB IE), common uplink parameters of the serving cell (eg, UplinkConfigCommonSIB IE), and other parameters.

[0185] The DownlinkConfigCommonSIB IE may include parameters (e.g., initialDownlinkBWP IE) of the initial downlink BWP of the serving cell (e.g., SpCell). Parameters of the initial downlink BWP (e.g., initial DL BWP 1724) may be included in the BWP-DownlinkCommon IE (e.g., shown in diagram 2300 of FIG. 23). The BWP-DownlinkCommon IE may be used to configure common parameters of the downlink BWP of the serving cell. The base station may configure locationAndBandwidth so that the initial downlink BWP includes the entire CORESET#0 of this serving cell in the frequency domain. The wireless device may apply locationAndBandwidth upon reception of this field (e.g., to determine the frequency location of the signal described in association with this locationAndBandwidth) but retain CORESET#0 until after reception of an RRC message such as one of RRCSetup / RRCResume / RRCReestablishment.

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

[0187] The parameter first-PDCCH-MonitoringOccasionOfPO may be signaled in SIB1 for paging in an initial DL BWP. For paging in DL BWPs other than the initial DL BWP, the parameter first-PDCCH-MonitoringOccasionOfPO may be signaled in the corresponding BWP configuration.

[0188] FIG. 23 shows an example of RRC configuration parameters 2300 (e.g., BWP-DownlinkCommon IE) in an initial downlink BWP of a serving cell. A base station may transmit one or more configuration parameters of the downlink BWP of a serving cell to a wireless device (or multiple wireless devices). As shown in FIG. 23, the one or more configuration parameters of the initial downlink BWP may include one or more generic BWP parameters of the initial downlink BWP, one or more cell-specific parameters of the PDCCH of the initial downlink BWP (e.g., in the pdcch-ConfigCommon IE), one or more cell-specific parameters of the PDSCH of this BWP (e.g., in the pdsch-ConfigCommon IE), and one or more other parameters. The pdcch-ConfigCommon IE may include a parameter of COESET#0 (e.g., controlResourceSetZero) that may be used in any common or UE-specific search space. The value of controlResourceSetZero may be interpreted similarly to the corresponding bit in MIB pdcch-ConfigSIB1. The pdcch-ConfigCommon IE may include parameters for additional common control resource sets (e.g., in commonControlResourceSet) that can be configured and used for any common or UE-specific search spaces. If the network configures this field, it uses a ControlResourceSetId other than 0 for this ControlResourceSet. The network configures commonControlResourceSet in SIB1 so that SIB1 is contained within the bandwidth of CORESET#0. The pdcch-ConfigCommon IE may include parameters for a list of additional common search spaces (e.g., in commonSearchSpaceList). The search space parameters may be implemented based on the example of Figure 24.The pdcch-ConfigCommon IE may indicate a search space for paging (e.g., pagingSearchSpace), a search space for random access procedures (e.g., ra-SearchSpace), a search space for SIB1 messages (e.g., searchSpaceSIB1), common search space #0 (e.g., searchSpaceZero), and one or more other search spaces from a list of search spaces.

[0189] As shown in FIG. 23, a control resource set (CORESET) may be associated with a CORESET index (e.g., ControlResourceSetId). The CORESET may be implemented based on the exemplary embodiments described with reference to FIG. 14A and / or FIG. 14B. A CORESET index with a value of 0 may identify a common CORESET (e.g., CORESET#0 1722 in FIG. 17) configured in the MIB and ServingCellConfigCommon(controlResourceSetZero) and may not be used in the ControlResourceSet IE. A CORESET index with other values ​​may identify a CORESET configured by dedicated signaling or in SIB1. controlResourceSetId may be unique within the BWP of the serving cell. A CORESET may be associated with coresetPoolIndex, which indicates the index of the CORESET pool of the CORESET. A CORESET may be associated with a duration parameter (e.g., duration), which indicates the continuous duration of the CORESET in several symbols. As shown in FIG. 23 , the configuration parameters of a CORESET may include at least one of a frequency resource indication (e.g., frequencyDomainResources), a CCE-REG mapping type indicator (e.g., cce-REG-MappingType), multiple TCI states, an indicator indicating whether a TCI is present in a DCI, etc. The frequency resource indication, including a number of bits (e.g., 45 bits), may indicate frequency domain resources, where each bit of the indication corresponds to a group of six RBs, the grouping starting from the first RB group in a BWP of a cell (e.g., SpCell, SCell). The first (leftmost / most significant) bit may correspond to the first RB group of the BWP, etc. A bit set to 1 may indicate that the RB group corresponding to the bit belongs to the frequency domain resources of this CORESET. Bits corresponding to groups of RBs that are not completely contained in the BWP for which the CORESET is configured may be set to zero.

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

[0191] A wireless device in the RRC_IDLE or RRC_INACTIVE state may periodically monitor paging occasions (POs) to receive paging messages intended for the wireless device. Before monitoring POs, a wireless device in the RRC_IDLE or RRC_INACTIVE state may wake up before each PO to prepare components and / or activate everything in preparation for data reception (warm-up). The gap between wake-up and PO may be long enough to accommodate all processing requirements. After warm-up, the wireless device may perform timing acquisition and coarse synchronization from SSBs, frequency and time tracking, time and frequency offset compensation, and / or local oscillator calibration. Thereafter, the wireless device may monitor the PDCCH for paging DCI in one or more PDCCH monitoring occasions based on the configuration parameters of the PCCH configuration configured in SIB1. The configuration parameters of the PCCH configuration may be implemented based on the exemplary embodiment described above with reference to FIG. 22.

[0192] Returning to the example of FIG. 17 , based on successful random access 1710, the wireless device may report (e.g., transmit) UE capability information indicating whether the wireless device can support multiple BWPs. Based on the capability information, and for a wireless device in RRC connected state 1704, the base station may configure the wireless device with, for example, DL / UL BWP#1 1728 and 1730, DL / UL BWP#2 (e.g., DL BWP 1730), and a BWP inactivity timer. In time period 1712, the base station may configure / set DL / UL BWP#1 (which may have a larger bandwidth than DL / UL BWP#2) as the first active DL / UL BWP and DL BWP#2 (which has a smaller bandwidth than DL BWP#1) as the default DL BWP 1732. After RRC configuration, the first active DL BWP 1728 and the first active UL BWP 1730 may be activated for scheduling large amounts of data. During time period 1714, if the wireless device has no traffic requests and no scheduled uplink transmissions, the BWP inactivity timer may expire, at which time the wireless device may switch its active DL BWP to a default DL BWP 1732 (e.g., DL BWP#2). In the example of FIG. 17, during time period 1714, for an FDD system in which DL and UL BWPs may be switched independently, the active UL BWP 1730 may remain as UL BWP#1 and not be switched.

[0193] Generally, extending beyond the initial access scenario described in FIG. 17, a base station may configure a wireless device with an uplink (UL) bandwidth portion (BWP) and a downlink (DL) BWP to enable bandwidth adaptation (BA) on a PCell. If carrier aggregation is configured, the base station may further configure the wireless device with at least a DL BWP to enable BA on an SCell (i.e., there may be no UL BWP in the UL). For a PCell, the initial active BWP (e.g., initial DL BWP 1724 and / or initial UL BWP 1726 of FIG. 17) may be the first BWP used for initial access. For an SCell, the first active BWP may be the second BWP that the wireless device is configured to operate on when the SCell is activated. In paired spectrum (e.g., FDD), the base station and / or wireless device can independently switch between the DL BWP and the UL BWP. In unpaired spectrum (eg, TDD), a base station and / or a wireless device may simultaneously switch between DL BWP and UL BWP.

[0194] A base station and / or wireless device may switch between configured BWPs via a DCI or a BWP inactivity timer. If a BWP inactivity timer is configured for a serving cell, the base station and / or wireless device may switch the active BWP to a default BWP in response to expiration of the BWP inactivity timer associated with the serving cell. Note that in this context, the serving cell may refer to a PCell, SCell, PSCell, etc. The default BWP may be configured by the network (e.g., a base station). For an FDD system, when configured with a BA, one UL BWP and one DL BWP for each uplink carrier may be simultaneously active in an active serving cell. For a TDD system, one DL / UL BWP pair may be simultaneously active in an active serving cell. Operating with one UL BWP and one DL BWP (or one DL / UL pair) may improve battery consumption of a wireless device. BWPs other than the one active UL BWP and one active DL BWP on which the wireless device may operate may be stopped. In a disabled BWP, the wireless device may not monitor the PDCCH and / or may not transmit on the PUCCH, PRACH, and UL-SCH.

[0195] A serving cell may be configured with up to a first number (e.g., four) of BWPs. For an activated serving cell, there may be one active BWP at any time. BWP switching for a serving cell may be used to activate inactive BWPs and deactivate active BWPs at a time. BWP switching may be controlled by a PDCCH indicating a downlink assignment or an uplink grant. BWP switching may be controlled by a BWP inactivity timer (e.g., bwp-InactivityTimer). BWP switching may be controlled by a MAC entity in response to initiating a random access procedure (e.g., random access 1710). After adding an SpCell or activating an SCell, one BWP may be active initially without receiving a PDCCH transmission indicating a downlink assignment or an uplink grant. The active BWP of a serving cell may be indicated by RRC and / or PDCCH. In the case of unpaired spectrum, a DL BWP may be paired with a UL BWP, and BWP switching may be common for both UL and DL.

[0196] FIG. 25 shows an example of BWP switching 2500 on a cell (e.g., a PCell or SCell). In the illustrated example, at time 2510, a wireless device 2504 receives at least one RRC message from a base station 2502 including parameters of the cell and one or more BWPs associated with the cell. For example, the base station 2502 may configure the wireless device 2504 with four BWPs (BWPs 0, 1, 2, 3) on the cell 2506. The RRC messages may include an RRC connection reconfiguration message (e.g., RRCReconfiguration), an RRC connection reestablishment message (e.g., RRCReestablishment), and / or an RRC connection setup message (e.g., RRCSetup). Among the one or more BWPs, at least one BWP may be configured as a first active BWP (e.g., BWP1) and one BWP may be configured as a default BWP (e.g., BWP0). At time 2512, wireless device 2504 may receive a command (e.g., an RRC message, a MAC CE, or a DCI message) to activate the cell in the nth slot. If the cell is a PCell, wireless device 2504 may not receive a command to activate the cell, and instead, wireless device 2504 may activate the PCell, for example, when wireless device 2504 receives an RRC message including configuration parameters for the PCell. At time 2520, wireless device 2504 may begin monitoring the PDCCH on BWP 1 in response to activating the cell.

[0197] At time 2522, the wireless device 2504 may start (or restart) a BWP inactivity timer (e.g., bwp-InactivityTimer) at the mth slot in response to receiving a DCI indicating a DL allocation on BWP 1 at time 2512. At time 2524, the wireless device 2504 may switch back to the default BWP (e.g., BWP 0) as the active BWP if the BWP inactivity timer expires at the sth slot at time 2516. At time 2526, the wireless device 2504 may deactivate the cell and / or stop the BWP inactivity timer when the sCellDeactivationTimer expires (e.g., if the cell is an SCell) at time 2518. In response to the cell being a PCell, the wireless device may not deactivate the cell and may not apply the sCellDeactivationTimer on the PCell.

[0198] The MAC entity of the wireless device (e.g., wireless device 2504) may apply normal operations on the active BWP of the activated serving cell configured in the BWP, including transmitting on the UL-SCH, transmitting on the RACH, monitoring the PDCCH, transmitting the PUCCH, receiving the DL-SCH, and / or (re)initializing any suspended configured uplink grants of configured grant type 1, if any, according to the stored configuration.

[0199] On an inactive BWP of each activated serving cell configured with the BWP, the MAC entity may not transmit on the UL-SCH, may not transmit on the RACH, may not monitor the PDCCH, may not transmit the PUCCH, may not transmit the SRS, may not receive the DL-SCH, may clear any configured downlink assignments and configured uplink grants of configured grant type 2, and / or may suspend any configured uplink grants of configured type 1.

[0200] If the MAC entity receives a PDCCH for a BWP switch of the serving cell while a random access procedure associated with this serving cell is not in progress, the wireless device may perform a BWP switch to the BWP indicated by the PDCCH. If the bandwidth fraction indicator field value is configured with DCI format 1_1, the bandwidth fraction indicator field value may indicate an active DL BWP from the configured DL BWP set for DL ​​reception. If the bandwidth fraction indicator field is configured with DCI format 0_1, the bandwidth fraction indicator field value may indicate an active UL BWP from the configured UL BWP set for UL transmission.

[0201] For the primary cell, the wireless device may be provided with a default DL BWP from among the configured DL BWPs by the upper layer parameter Default-DL-BWP. If the wireless device is not provided with a default DL BWP by the upper layer parameter Default-DL-BWP, the default DL BWP is the initial active DL BWP. The wireless device may be provided with a timer value for the primary cell by the upper layer parameter bwp-InactivityTimer. If configured, the wireless device may increment the timer every 1 millisecond interval for frequency range 1 or every 0.5 milliseconds for frequency range 2 when operating if the wireless device may not detect DCI format 1_1 for paired spectrum operation or if the wireless device may not detect DCI format 1_1 or DCI format 0_1 ​​for unpaired spectrum operation during the interval.

[0202] If the wireless device is configured for a secondary cell with the higher layer parameter Default-DL-BWP indicating a default DL BWP among the configured DL BWPs, and the wireless device is configured with the higher layer parameter bwp-InactivityTimer indicating a timer value, the wireless device procedure on the secondary cell may be 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.

[0203] If a wireless device is configured with a first active DL BWP on a secondary cell or carrier (e.g., by the higher layer parameter Active-BWP-DL-SCell) and with a first active UL BWP (e.g., by the higher layer parameter Active-BWP-UL-SCell), 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 on the secondary cell or carrier, respectively.

[0204] The set of PDCCH candidates for a wireless device to monitor may be defined in terms of a PDCCH search space set. A search space set includes a CSS set or a USS set. When a wireless device selects one or more of the following search space sets, the wireless device selects one or more of the following search space sets: a Type0-PDCCH CSS set configured by pdcch-ConfigSIB1 in MIB, by searchSpaceSIB1 in PDCCH-ConfigCommon, or by searchSpaceZero in PDCCH-ConfigCommon for a DCI format having a CRC scrambled by SI-RNTI in the primary cell of the MCG; a Type0A-PDCCH CSS set configured by searchSpaceOtherSystemInformation in PDCCH-ConfigCommon for a DCI format having a CRC scrambled by SI-RNTI in the primary cell of the master cell group (MCG); or a Type1-PDCCH CSS set configured by ra-SearchSpace in PDCCH-ConfigCommon for a DCI format having a CRC scrambled by RA-RNTI, MsgB-RNTI, or TC-RNTI in the primary cell. Type2-PDCCH CSS set configured by the pagingSearchSpace in PDCCH-ConfigCommon for DCI formats with CRC scrambled by P-RNTI in the primary cell of the MCG. Type3-PDCCH CSS set configured by the SearchSpace in PDCCH-Config with searchSpaceType=common for DCI formats with CRC scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, CI-RNTI, or PS-RNTI, and C-RNTI, MCS-C-RNTI, or CS-RNTI for the primary cell only.Monitor PDCCH candidates in the CSS set and the USS set configured by the SearchSpace in PDCCH-Config with searchSpaceType=ue-Specific for DCI formats with CRC scrambled by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, CS-RNTI, SL-RNTI, SL-CS-RNTI, or SL-L-CS-RNTI.

[0205] The wireless device may determine the PDCCH monitoring opportunities on the active DL BWP based on one or more PDCCH transmission configuration parameters (e.g., based on the example embodiment of FIG. 24 ), including a PDCCH monitoring period, a PDCCH monitoring offset, and a PDCCH monitoring pattern within a slot.

[0206]

number

[0207] If so, the number of PDCCH monitoring opportunities is

[0208]

number

[0209] The number in the frame with

[0210]

number

[0211] , and determines that the object is in a slot having

[0212]

number

[0213]

number

[0214] is the slot offset indicated in the PDCCH configuration parameters (eg, based on the example embodiment of FIG. 24).

[0215]

number

[0216] is the PDCCH monitoring periodicity indicated in the PDCCH configuration parameters (e.g., based on the exemplary embodiment of FIG. 24).

[0217]

number

[0218] Starting with,

[0219]

number

[0220] Monitor PDCCH candidates for a search space set of consecutive slots and

[0221]

number

[0222] Do not monitor PDCCH candidates for the search space set s of consecutive slots.

[0223]

number

[0224] The USS is defined by a set of PDCCH candidates of CCE aggregation level L.

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

[0226]

number

[0227] Carrier indicator field value as

[0228]

number

[0229] The slot of the active DL BWP of the serving cell corresponding to

[0230]

number

[0231] PDCCH candidates in the search space set

[0232]

number

[0233] and for any CSS,

[0234]

number

[0235] and for U.S.S.

number

[0236] and

[0237]

number

[0238] and

[0239]

number

[0240] against

[0241]

number

[0242] and

[0243]

number

[0244]

number

[0245] and

[0246]

number

[0247] against

[0248]

number

[0249] and

[0250]

number

[0251] and

[0252]

number

[0253] and

[0254]

number

[0255] is the number / amount of CCE in CORESETp, and is 0~

[0256]

number

[0257] are numbered / quantified by

[0258]

number

[0259] is the carrier indicator field value if the wireless device is configured with the carrier indicator field by CrossCarrierSchedulingConfig for the serving cell whose PDCCH transmissions are monitored, otherwise for any CSS

[0260]

number

[0261]

number

[0262]

number

[0263] indicates that the wireless device

[0264]

number

[0265] is the number of PDCCH candidates configured to monitor aggregation level L of search space set s for a serving cell corresponding to

[0266]

number

[0267] And for USS,

[0268]

number

[0269] is constructed for the CCE aggregation level L of the search space set s.

[0270]

number

[0271] Spanning values

[0272]

number

[0273] is the maximum value of

[0274]

number

[0275] The RNTI value used is the C-RNTI.

[0276] A wireless device may monitor a set of PDCCH candidates according to configuration parameters of a search space set including multiple search spaces (SSs). The wireless device may monitor a set of PDCCH candidates in one or more CORESETs to detect one or more DCIs. The CORESET may be configured based on the example of FIG. 23. The monitoring may include decoding one or more PDCCH candidates of the set of PDCCH candidates according to the monitored DCI format. The monitoring may include decoding DCI content of one or more PDCCH candidates having possible (or configured) PDCCH positions, possible (or configured) PDCCH formats (e.g., the number of CCEs, the number of PDCCH candidates in a common SS, and / or the number of PDCCH candidates in a UE-specific SS), and possible (or configured) DCI formats. The decoding may be referred to as blind decoding.

[0277] FIG. 26 is a table 2600 illustrating examples of DCI formats that may be used by a base station to transmit control information to a wireless device or that may be used by a wireless device for PDCCH 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 a PUSCH in one cell. DCI format 0_1 ​​may be used to schedule one or more PUSCHs in one cell or to indicate CG-DFI (Configured Grant Downlink Feedback Information) for a configured grant PUSCH, etc. DCI formats that a wireless device may monitor at the SS may be configured.

[0278] FIG. 27 shows example 2700 of transitioning between a dormant state and a non-dormant state on an SCell. A base station may transmit one or more RRC messages including configuration parameters for the SCell to a wireless device, where the SCell includes multiple BWPs. Among the multiple BWPs, a first BWP (e.g., BWP 3 in FIG. 27) may be configured as a non-dormant BWP and / or a second BWP (e.g., BWP 1 in FIG. 27) may be configured as a dormant BWP. A default BWP (e.g., BWP 0 in FIG. 27) may be configured in the multiple BWPs. A non-dormant BWP may be a BWP that the wireless device may activate in response to transitioning the SCell from a dormant state to a non-dormant state. A dormant BWP may be a BWP that the wireless device may switch to in response to transitioning the SCell from a non-dormant state to a dormant state. The configuration parameters may indicate one or more search spaces and / or CORESETs configured on the non-dormant BWPs. The configuration parameters may indicate no search space or no CORESET configured on the dormant BWP. The configuration parameters may indicate CSI reporting configuration parameters for the dormant BWP.

[0279] The dormant BWP may differ from a default BWP, such as the default DL BWP 1732 of FIG. 17 or the default BWP described in connection with FIG. 25 above. The configuration parameters may indicate one or more search spaces or one or more CORESETs configured on the default BWP. If a BWP inactivity timer expires or a DCI indicating switching to the default BWP is received, the wireless device may switch to the default BWP as the active BWP. For example, when the default BWP is active, the wireless device may perform at least one of monitoring a PDCCH on the default BWP of the SCell, receiving a PDSCH on the default BWP of the SCell, transmitting a PUSCH on the default BWP of the SCell, transmitting an SRS on the default BWP of the SCell, and / or transmitting a CSI report to the default BWP of the SCell (e.g., in a periodic, aperiodic, and / or semi-persistent manner). If the wireless device receives a dormant / non-dormant indication indicating a dormant state of the SCell, the wireless device may switch to the dormant BWP as the active BWP of the SCell. In response to switching to the dormant BWP, the wireless device may perform at least one of: refrain from (e.g., stop) monitoring a PDCCH on the dormant BWP of the SCell (or for the SCell if the SCell is cross-carrier scheduled by another cell), refrain from (e.g., stop) receiving a PDSCH on the dormant BWP of the SCell, refrain from (e.g., stop) transmitting a PUSCH on the dormant BWP of the SCell, refrain from (stop) transmitting an SRS on the dormant BWP of the SCell, and / or (continuously) transmit a CSI report (e.g., periodic, aperiodic, and / or semi-persistent CSI report) for the dormant BWP of the SCell.

[0280] As shown in FIG. 27 , the base station may transmit a DCI to the wireless device via PDCCH resources, where the DCI includes a dormant / non-dormant indication indicating either a dormant or non-dormant state of the SCell. In response to the dormant / non-dormant indication indicating the dormant state of the SCell, the wireless device may transition the SCell to a dormant state if the SCell was in a non-dormant state before receiving the DCI, or may maintain the SCell in a dormant state if the SCell was in a dormant state before receiving the DCI. Transitioning the SCell to a dormant BWP (e.g., configured by the base station). In response to the dormant / non-dormant indication indicating the non-dormant state of the SCell, the wireless device may transition the SCell to a dormant BWP (e.g., configured by the base station) for the SCell. In response to the dormant / non-dormant indication indicating the non-dormant state of the SCell, the wireless device may transition the SCell to a non-dormant state if the SCell was in a dormant state before receiving the DCI, or may maintain the SCell in a non-dormant state if the SCell was in a non-dormant state before receiving the DCI. Transitioning the SCell to a non-dormant BWP (e.g., configured by the base station).

[0281] In response to transitioning the SCell from a dormant state to a non-dormant BWP configured by the base station as the active BWP for the SCell (e.g., BWP3 as shown in FIG. 27 ), the wireless device may switch to the non-dormant BWP configured by the base station as the active BWP for the SCell. Based on the switching to the non-dormant BWP as the active BWP for the SCell, the wireless device may perform at least one of monitoring a PDCCH on the active BWP for the SCell (or monitoring a PDCCH for the SCell if the SCell is configured to be cross-carrier scheduled by another cell), receiving a PDSCH on the active BWP for the SCell, and / or transmitting a PUCCH / PUSCH / RACH / SRS on the active BWP (e.g., if the active BWP is an uplink BWP).

[0282] In response to transitioning the SCell from a non-dormant state to a dormant state, the wireless device may switch to a dormant BWP configured by the base station (e.g., BWP1 for the SCell as shown in FIG. 27). Based on switching to the dormant BWP for the SCell, the wireless device may perform at least one of: refrain from monitoring the PDCCH on the dormant BWP of the SCell (or refrain from monitoring the PDCCH of the SCell if the SCell is configured to be cross-carrier scheduled by another cell); refrain from receiving the PDSCH on the dormant BWP of the SCell; refrain from transmitting PUCCH / PUSCH / RACH / SRS on the dormant BWP (e.g., if the dormant BWP is an uplink BWP); and / or transmit a CSI report for the dormant BWP of the SCell based on a CSI report configuration parameter configured on the dormant BWP of the SCell. Thus, energy savings may be achieved by the wireless device due to reduced monitoring and transmission of certain signals while the cell is in a dormant state.

[0283] In a 3GPP NR system, the main services and functions of the MAC (sub) layer of a wireless device (as described above with respect to MAC 212 / 222 in Figures 2, 3, and 4) may include mapping between logical channels and transport channels, multiplexing / demultiplexing of MAC SDUs belonging to one or different logical channels to / from transport blocks (TBs) delivered to / from the physical layer on the transport channels, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ) (e.g., one HARQ entity per cell in the case of carrier aggregation (CA)), priority handling between UEs through dynamic scheduling, priority handling between logical channels of one UE through logical channel prioritization, and padding. In one example, a single MAC entity may support multiple numerologies, transmission timings, and cells. Mapping restrictions in logical channel prioritization control which numerologies, cells, and transmission timings a logical channel may use. Different types of data transfer services are provided by the MAC. To accommodate different kinds of data transfer services, multiple types of logical channels are defined, e.g., each supporting the transfer of a specific type of information. Each logical channel type is defined by what type of information is transferred. Logical channels (e.g., as described above with respect to Figures 5A and 5B) are classified into two groups: control channels and traffic channels. Control channels are used to transfer only control plane information, and traffic channels are used to transfer only user plane information.

[0284] Services and features provided by the MAC (sub)layer (or MAC layer) of the wireless device and base station may be enabled based on communication (i.e., transmission and / or reception) of MAC PDUs, as described above with respect to FIGS. 4A and 4B. A base station may transmit one or more MAC PDUs to a wireless device. In one example, a MAC PDU may be a bit string whose length is byte-aligned (e.g., aligned to a multiple of 8 bits). In one embodiment, the bit string may be represented by a table with the most significant bit being the leftmost bit in the first row of the table and the least significant bit being the rightmost bit in the last row of the table. More generally, the bit string is read from left to right, then in row reading order. The bit order of the parameter field within the MAC PDU may be represented with the most significant bit first in the leftmost bit and the least significant bit last in the rightmost bit.

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

[0286] A MAC PDU may include one or more MAC sub-PDUs, where a MAC sub-PDU includes 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, or a combination thereof. The MAC SDU may be of variable size. The MAC subheader may correspond to a MAC SDU, a MAC CE, or padding.

[0287] If the MAC subheader corresponds to a MAC SDU, a variable-sized MAC CE, or padding, the MAC subheader may include an R (reserved) field having a length of 1 bit, an F field having a length of 1 bit, an LCID field having a length of multiple bits (and indicating a logical channel ID that identifies the logical channel instance of the corresponding MAC SDU / MAC CE / DL-SCH or UL-SCH padding), an L field having a length of multiple bits, or a combination thereof.

[0288] FIG. 28A shows an example of a DL MAC PDU. Multiple MAC CEs, such as MAC CEs 1 and 2, may be arranged together. A MAC sub-PDU containing a MAC CE may precede a MAC sub-PDU containing a MAC SDU or a MAC sub-PDU containing padding. In one example, each MAC CE / MAC SDU has a corresponding MAC sub-header. As described further below, the MAC sub-header has several formats depending on whether a MAC SDU, a fixed-size MAC CE, or a variable-size MAC CE is transmitted. FIG. 28B shows an example of a UL MAC PDU. Multiple MAC CEs, such as MAC CEs 1 and 2, may be arranged together. In one embodiment, a MAC sub-PDU containing a MAC CE may be arranged after all MAC sub-PDUs containing MAC SDUs. In addition, a MAC sub-PDU may be arranged before a MAC sub-PDU containing padding.

[0289] Figure 29A shows an example of a MAC subheader having an R field, an F field, an LCID field, and an L field. In the example MAC subheader of Figure 29A, the LCID field may be 6 bits long, and the L field may be 8 bits long. Figure 29B shows an example of a MAC subheader having an R field, an F field, an LCID field, and an L field. In the example MAC subheader shown in Figure 29B, the LCID field may be 6 bits long, and the L field may be 16 bits long. If the MAC subheader supports fixed-size MAC CE or padding, the MAC subheader may include a 2-bit R field and a multi-bit LCID field. Figure 29C shows an example of such a MAC subheader with the R and LCID fields but no L field. In the example MAC subheader shown in Figure 29C, the LCID field may be 6 bits long, and the R field may be 2 bits long.

[0290] Figure 30A shows a table 3000A including examples of one or more MAC CEs, identified by corresponding code points / indexes of LCIDs, that may be transmitted as one or more MAC CEs by a MAC entity of a wireless device to a MAC entity of a base station. For example, the one or more MAC CEs may include at least one of a short buffer status report (BSR) MAC CE (having an LCID index of 61), a long BSR MAC CE (having an LCID index of 62), a C-RNTI MAC CE (having an LCID index of 58), a configured grant confirmation MAC CE (having an LCID index of 55), a single-input PHR MAC CE (having an LCID index of 57), a multiple-input PHR MAC CE (having an LCID index of 56), etc. A MAC CE may have an LCID in a MAC subheader corresponding to the MAC CE. Different MAC CEs may have different LCIDs in the MAC subheaders corresponding to the MAC CE.

[0291] FIG. 30B shows a table 3000B containing examples of one or more MAC CEs, identified by corresponding codepoints / indexes of the LCID, that may be transmitted by the MAC entity of the base station to the MAC entity of the wireless device. The one or more MAC CEs include an SP ZP CSI-RS resource set activation / deactivation MAC CE (having an LCID index of 48), a PUCCH spatial relationship activation / deactivation MAC CE (having an LCID index of 49), an SP SRS activation / deactivation MAC CE (having an LCID index of 50), an SP CSI report for a PUCCH activation / deactivation MAC CE (having an LCID index of 51), a TCI state indication for a UE-specific PDCCH MAC CE (having an LCID index of 52), a TCI state indication for a UE-specific PDSCH MAC CE (having an LCID index of 53), an aperiodic CSI trigger state sub-selection MAC CE (having an LCID index of 54), an SP CSI-RS / CSI-IM resource set activation / deactivation MAC CE (having an LCID index of 55), a DRX command MAC CE (having an LCID index of 60), a Long DRX command MAC CE (having an LCID index of 59), an SCell activation / deactivation MAC CE (having an LCID index of 61), an SP CSI report for a PUCCH activation / deactivation MAC CE (having an LCID index of 62), an SP CSI report for a PDCCH MAC CE (having an LCID index of 63), an SP CSI report for a PDCCH MAC CE (having an LCID index of 64), an SP CSI report for a PDSCH MAC CE (having an LCID index of 65), an SP CSI report for a PDCCH MAC CE (having an LCID index of 66), an SP CSI report for a PDSCH MAC CE (having an LCID index of 67), an SP CSI report for a PDSCH MAC CE (having an LCID index of 68), an SP CSI report for a PDSCH MAC CE The MAC CE may include at least one of an LCID (1 octet) (having an LCID index of 58), an SCell Activation / Deactivation MAC CE (4 octets) (having an LCID index of 57), etc. In one example, a MAC CE, such as a MAC CE transmitted by a base station MAC entity to a wireless device MAC entity, may have an LCID in a MAC subheader corresponding to the MAC CE. Different MAC CEs may have different LCIDs in the MAC subheaders corresponding to the MAC CE.

[0292] In carrier aggregation (CA), as described above with respect to FIG. 10B, two or more component carriers (CCs) may be aggregated. Using CA techniques, a wireless device may simultaneously receive or transmit on one or more CCs depending on the capabilities of the wireless device. A wireless device may support CA for adjacent and / or non-adjacent CCs. CCs may be organized into cells. For example, CCs may be organized into one primary cell (PCell) and one or more secondary cells (SCells). When configured with CA, a wireless device may have one RRC connection with the network. During RRC connection establishment / re-establishment / handover, the cell providing NAS mobility information may be the serving cell. During RRC connection re-establishment / handover procedures, the cell providing security input may be the serving cell. The serving cell may indicate the PCell. The base station may send one or more messages to the wireless device including configuration parameters for one or more SCells depending on the capabilities of the wireless device.

[0293] When configured with CA, a base station and / or a wireless device may employ an SCell activation / deactivation mechanism to improve battery or power consumption of the wireless device. When a 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 as described above with respect to FIG. 27. After configuration of an SCell (by the wireless device or by the wireless device's base station), the SCell may remain deactivated unless the SCell state associated with the SCell is set to "activated" or "dormant." In response to receiving a SCell Activation / Deactivation MAC CE, the wireless device may activate / deactivate the SCell. The base station may transmit one or more messages including an SCell timer (e.g., sCellDeactivationTimer) to the wireless device. The wireless device may deactivate the SCell in response to expiration of the SCell timer.

[0294] Figure 31A shows an example of a one-octet SCell Activation / Deactivation MAC CE. A first MAC PDU subheader including a first LCID (e.g., the LCID with an index / codepoint of 58 in Figure 30B) may identify the 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 include a single octet. The single octet may include the number of first C fields (e.g., 7) and the number of second R fields (e.g., 1).

[0295] Figure 31B shows an example of a 4-octet SCell Activation / Deactivation MAC CE. A second MAC PDU subheader including a second LCID (e.g., the LCID with an index / codepoint of 57 in Figure 30B) may identify the 4-octet SCell Activation / Deactivation MAC CE. The 4-octet SCell Activation / Deactivation MAC CE may have a fixed size. The 4-octet SCell Activation / Deactivation MAC CE may include 4 octets. The 4 octets may include a third number of C fields (e.g., 31) and a fourth number of R fields (e.g., 1).

[0296] As shown in Figures 31A and / or 31B, C i The field may indicate the activation / deactivation state of the SCell with SCell index i if the SCell with SCell index i is configured. i If the field is set to 1, the SCell with SCell index i can be activated. i If the field is set to zero, the SCell with SCell index i may be deactivated. If there is no SCell configured with SCell index i, the wireless device i The R field may indicate a reserved bit and may be set to zero, for example.

[0297] When a wireless device receives an SCell Activation / Deactivation MAC CE activating an SCell (e.g., as shown in FIG. 31A or FIG. 31B), the wireless device may activate the SCell. In response to activating the SCell, the wireless device may perform operations including: SRS transmission on the SCell, CQI / PMI / RI / CRI reporting on the SCell, PDCCH monitoring on the SCell, PDCCH monitoring on the SCell, and / or PUCCH transmission on the SCell. In response to activating the SCell, the wireless device may start or restart a first SCell timer (e.g., sCellDeactivationTimer) associated with the SCell. The wireless device may start or restart the first SCell timer in the slot in which the SCell Activation / Deactivation MAC CE activating the SCell is received. In response to activating the SCell, the wireless device may (re)initialize one or more suspended configured uplink grants of configured grant type 1 associated with the SCell according to the stored configuration. In response to activating the SCell, the wireless device may trigger a power headroom report (PHR), as described further below.

[0298] If the wireless device receives an SCell Activation / Deactivation MAC CE that deactivates an activated SCell, the wireless device may deactivate the activated SCell. If a first SCell timer (e.g., sCellDeactivationTimer) associated with the activated SCell expires, the wireless device may deactivate the activated SCell. In response to deactivating the activated SCell, the wireless device may stop the first SCell timer associated with the activated SCell. In response to deactivating the activated SCell, the wireless device may clear one or more configured downlink assignments and / or one or more configured uplink grants of configured uplink grant type 2 associated with the activated SCell. In response to deactivating the activated SCell, the wireless device may suspend one or more configured uplink grants of configured uplink grant type 1 associated with the activated SCell and / or flush HARQ buffers associated with the activated SCell.

[0299] When an SCell is deactivated, the wireless device may not perform operations including transmitting an SRS on the SCell, reporting CQI / PMI / RI / CRI of the SCell, transmitting on a UL-SCH on the SCell, transmitting on a RACH on the SCell, monitoring at least one first PDCCH on the SCell, monitoring at least one second PDCCH on the SCell, and / or transmitting a PUCCH on the SCell. If the at least one first PDCCH on the activated SCell indicates an uplink grant or a downlink assignment, the wireless device may restart a first SCell timer (e.g., sCellDeactivationTimer) associated with the activated SCell. If at least one second PDCCH on a serving cell (e.g., a PCell or SCell configured with a PUCCH, i.e., a PUCCH SCell) that schedules the activated SCell indicates an uplink grant or a downlink allocation for the activated SCell, the wireless device may restart a first SCell timer (e.g., sCellDeactivationTimer) associated with the activated SCell. If the SCell is deactivated and there is an ongoing random access procedure on the SCell, the wireless device may terminate (or stop) the ongoing random access procedure on the SCell.

[0300] To efficiently utilize uplink radio resources, the MAC layer in the base station includes a dynamic resource scheduler that allocates physical layer uplink resources to multiple served wireless devices. The wireless device may measure data buffered in the wireless device's logical channel queue and transmit an uplink buffer status report (BSR) regarding the data to the base station to provide support for quality of service (QoS)-awake packet scheduling at the base station. In addition to the BSR transmission, the amount of transmit power available to each wireless device may also be relevant to the base station's uplink scheduler. For example, the base station may avoid scheduling a data rate to the wireless device that is higher than the uplink transmit power available to the wireless device. Thus, for the uplink, the wireless device may transmit a power headroom report (PHR) to the base station indicating the power headroom (PH) available to the UE, for example, when the wireless device is scheduled to transmit on the UL-SCH. This PHR may be used by the base station to allocate uplink resources among the multiple UEs so that the resources are efficiently utilized by the multiple UEs. That is, the base station may determine how much uplink bandwidth may be used per subframe wireless device based on the PHR, which allows the base station to avoid allocating resources that the wireless device may not use.

[0301] 32A illustrates two exemplary PHRs 3201A and 3201B transmitted by a wireless device to a base station. The PHRs indicate the maximum (per carrier) transmit power (P CMAX、C ) (or calculated or nominal UE maximum transmit power) and the measured (or estimated) transmit power for uplink transmission (e.g., P CMAX、C The PHR can be expressed as the difference between the maximum per-carrier transmission power PCMAX、C Because the PHR is not a measure of the difference between the PHR and the actual carrier transmit power, the PHR may be negative, indicating that the base station has scheduled a higher data rate than the wireless device can support given the available transmit power at the time of generating the PHR. Because the base station may configure the modulation and coding scheme and resource size to be used by the wireless device for uplink transmission in the duration corresponding to the PHR, the base station may determine a valid combination of modulation and coding scheme and resource size allocation (e.g., assuming a constant downlink path loss). For example, as shown in FIG. 32A, the PHR 201A may be calculated based on the PHR. CMAX、C 3206, and P CMAX、C 32A, the PHR 3201B may include a power headroom (PH) 3202A, which is the difference between P 3202 and the estimated UE uplink (e.g., PUSCH) transmit power 3204A. CMAX、C 3206, and P CMAX、C 3202B and the estimated UE uplink (e.g., PUSCH) transmit power 3204B. The UE uplink transmit power 3204B may include a power headroom (PH) 3202B, which is the difference between P CMAX、C 3206, PHR 3201B may exhibit a power headroom PH 3202B that is negative. CMAX、C If PHR 3201A is lower than 3206, then PHR 3201A may indicate a power headroom PH 3202A that is positive.

[0302] 32B shows an example MAC subheader 3212 and corresponding MAC CE 3210 for transmitting a PHR from a wireless device to a base station. The PHR may be transmitted (and reported) by the wireless device to the base station by configuring a PH value in the PHR MAC CE (e.g., MAC CE 3210) and transmitting the PHR MAC CE over an UL transmission resource. The MAC CE 3210 configures the PH 3214 and P for the serving cell (carrier). CMAX3216. MAC CE 3210 may include MPE 3218, where the PHR functionality is configured by the base station with MPE reporting based on parameter mpe-Reporting-FR2 and indicates power backoff to satisfy MPE FR2 requirements for a serving cell operating in FR2 if the serving cell operates in FR2. The PHR transmitted by the wireless device may be one of three types: Type 1 PHR, Type 2 PHR, or Type 3 PHR.

[0303] The Type 1 PHR specifies the nominal (or calculated) UE maximum transmit power (P on carrier c) that may be transmitted by the wireless device for each activated serving cell (e.g., PCell, SCell, PSCell, or SPCell). CMAX、C ) and the estimated (or measured) power for UL data transmission (UL-SCH). Type 1 PHR may indicate a PH that assumes transmission of only PUSCH on the carrier. P CMAX、C The value of P may be explicitly configured by the base station, but may be configured separately for normal uplink carriers and supplemental uplink carriers where both belong to the same cell (i.e., have the same associated downlink component carrier). Thus, the P used by the wireless device in generating the PHR CMAX、C 3216 is contained within the MAC CE 3210.

[0304] A Type 2 PHR is a PHR that specifies the nominal (or calculated) UE maximum transmit power (P on carrier c) that can be transmitted by the wireless device. CMAX、C ) and the estimated (or measured) power of the PUCCH transmission and UL data transmission (UL-SCH) on an SPCell (e.g., PCell or PSCell) of another MAC layer (e.g., LTE MAC in E-UTRAN New Radio dual Connectivity (EN-DC) or E-UTRA MAC when dual connectivity is configured). In other words, Type 2 PHR indicates PH based on simultaneous PUSCH and PUCCH reports.

[0305] The Type 3 PHR specifies the nominal (or calculated) UE maximum transmit power (P on carrier c) that may be transmitted by the wireless device for each activated serving cell (PCell, SCell, PSCell, or SpCell). CMAX、C ) and the estimated (or measured) power (on a component carrier) for a sounding reference signal (SRS) transmission. In other words, a Type 3 PHR may be used to handle SRS switching, i.e., SRS transmission on an uplink carrier on which the wireless device is not configured to transmit a PUSCH. This Type 3 PHR may enable the base station to evaluate the uplink quality of an alternative uplink carrier and (re)configure the wireless device to use this carrier for uplink transmission.

[0306] As described further below, the PHR may be transmitted via a PHR MAC CE. For example, with reference to FIG. 30A, the LCID in the MAC subheader 3212 may be an index / codepoint value (e.g., 57) that indicates that the corresponding MAC CE 3210 is a single-input PHR MAC CE. In the case of carrier aggregation or dual connectivity, multiple PHRs (for multiple corresponding serving cells) may be included within a single MAC CE. For example, with reference to FIG. 30A, the LCID in the MAC subheader 3212 may be an index / codepoint value (e.g., 54 or 56) that indicates that the corresponding MAC CE 3210 is a multiple-input PHR MAC CE (e.g., a 4-octet multiple-input PHR or a 1-octet multiple-input PHR).

[0307] PH 3214 may be a field (of MAC CE 3210, which is a PHR MAC CE) that indicates a PH level. For example, the value of field PH 3214 may be a 6-bit value, as shown in table 3220. The value of PH 3214 may correspond to one or more measured quantity values ​​of PH in dB. As shown, each possible value of PH 3214 may correspond to one or more measured quantity values ​​of PH in dB that do not overlap with the measured quantity values ​​in dB corresponding to other possible values ​​of PH. For example, a PH of 63 may correspond to a measured quantity value of 38 dB or greater, and a PH of 3 may correspond to a measured quantity value of −30 dB.

[0308] P CMAX、C 3216 may be a field (of MAC CE 3210, which is PHR MAC CE) used to calculate field PH 3214, as described above in FIG. 32A, and may be, for example, a 6-bit value. CMAX、C The values ​​in 3216 indicate nominal UE transmit power levels corresponding to values ​​of one or more measured quantities in dBm. Similar to table 3220, table 3222 also shows the P CMAX、C It shows that the 3216 different values ​​correspond to values ​​of one or more different (non-overlapping) measured quantities in dBm.

[0309] MPE 3218 may be a field (of MAC CE 3210, which is a PHR MAC CE) that indicates the applied power backoff to meet MPE requirements, if used (e.g., based on configured mpe-Reporting-Fr2 parameters and a serving cell operating in FR2).

[0310] The value of MPE 3218 may be, for example, 2 bits and corresponds to a measured P-MPR value in dB, as shown in table 3224. Similar to table 3220, table 3224 shows that different values ​​of MPE 3218 correspond to one or more different (non-overlapping) measured quantity values ​​in dB.

[0311] Figure 33A shows an example of a single-input PHR MAC CE. The single-input PHR MAC CE may have a fixed size including two octets, and includes a reserved (R) field (e.g., bits set to '0'), a PHR field (of type 1 for the PCell), and a P CMAX、f、c It contains the fields, which are as described above with respect to Figure 32B.

[0312] Figure 33B shows an example of a multiple-input PHR MAC CE (including one octet for c) where the highest serving cell index (ServCellIndex) of the serving cells with configured uplinks is less than 8, and Figure 33C shows an example of a multiple-input PHR MAC CE (e.g., including four octets for c) where the highest serving cell index of the serving cells with configured uplinks is 8 or greater. A multiple-input PHR MAC CE may be identified by a MAC PDU subheader with an LCID defined for multiple-input PHRs (e.g., as illustrated in Figure 30A). This may have a variable size and may include a bitmap (corresponding to the number of carriers c), a Type 2 PH field, and the associated PDUs of the SpCells of other MAC entities. CMAX、f、c field (if reported), the Type 1 PH field, and the associated P CMAX、f、c The multi-input PHR MAC CE in Figures 33B and 33C includes the associated P cell of the serving cell other than the PCell shown in the bitmap in ascending order based on ServCellIndex. CMAX、f、c It may further include one or more of a Type X PH field and an octet containing field (if reported), where X is either 1 or 3. If the highest ServCellIndex of the serving cells with configured uplinks is less than 8, a single octet bitmap is used to indicate the presence of PH per serving cell, otherwise 4 octets are used.

[0313] The presence of Type 2 PH fields for the SpCell of other MAC entities may be configured by the RRC parameter phr-Type2OtherCell with value 'True'.

[0314] The MAC entity of the wireless device may determine whether the PH value of the activated serving cell is based on the actual transmission or the reference format by considering downlink control information received prior to the PDCCH opportunity on which the first UL grant for a new transmission is received since the PHR was triggered.

[0315] Referring to Figures 33B and 33C, the PHR MAC CE may include the following fields: -C i Field: Indicates the presence of the PH field of the serving cell with ServCellIndex i (e.g., a C field set to '1' may indicate that the PH field of the serving cell with ServCellIndex i is reported, and '0' may indicate that the PH field of the serving cell with ServCellIndex i is not reported), - Reserved field (R): set to "0", - Virtual (V) field: Indicates whether the PH value is based on actual transmission or reference format. For Type 1 PH, V=0 may indicate actual transmission on PUSCH, and V=1 may indicate that the PUSCH reference format is used. For Type 2 PH, V=0 may indicate actual transmission on PUCCH, and V=1 may indicate that the PUCCH reference format is used. For Type 3 PH, V=0 may indicate actual transmission on SRS, and V=1 may indicate that the SRS reference format is used. Furthermore, for Type 1, Type 2, and Type 3 PH, V=0 indicates that the associated P CMAX、f、c V=1 indicates the presence of an octet containing a field, and V=1 indicates the presence of an octet containing the associated P CMAX、f、c It may indicate that the octet containing the field has been omitted, -PH field: indicates the power headroom level as illustrated in Figure 32B, - P field: indicates whether the wireless device (e.g., MAC entity) applies power backoff due to power management. If power backoff due to power management was not applied, the corresponding P CMAX、f、c If the field has a different value, the wireless device may set P=1. -P CMAX、f、c Field: The P field used in the calculation of the preceding PH field, as illustrated in Figure 32B. CMAX、f、c Or indicates p.

[0316] A wireless device may receive configuration parameters for a PHR via one or more messages (e.g., via RRC messages). For example, a base station may transmit these configuration parameters to control the PHR (e.g., when and / or what type of PHR is generated and transmitted) by the wireless device. For example, the configuration parameters may include one or more of the following configuration parameters for the PHR: -phr-PeriodicTimer: Indicates the value of the number of subframes for periodic PHR reporting. The value can be one of a set of values ​​(e.g., sf10 out of sf10, sf20, sf50, sf100, sf200, sf500, sf1000, infinity, where sf10 corresponds to 10 subframes, and so on). For example, expiration of the periodic power headroom reporting timer can trigger a power headroom reporting procedure. -phr-ProhibitTimer: indicates the value of the number of subframes for which power headroom reporting is prohibited. The value can be one of a set of values ​​(e.g., sf10 out of sf0, sf10, sf20, sf50, sf100, sf200, sf500, sf1000, where sf10 corresponds to 10 subframes, and so on). For example, if the power headroom report prohibit timer is running, the power headroom reporting procedure may not be triggered. -phr-Tx-PowerFactorChange: indicates the dB value for triggering a PHR report. The value may be one of a set of values ​​(e.g., dB1 corresponds to 1 dB, dB3 corresponds to 3 dB, etc.). The same value may apply to each serving cell (although the related functionality may be implemented independently for each cell). -phr-Type2OtherCell: Indicates whether the UE reports PHR Type 2 for the second cell (e.g., SpCell) of the second MAC entity / layer. For example, this parameter can be set to 'True' to indicate that PHR Type 2 is transmitted, or 'False' if the UE is not configured with an E-UTRA MAC entity. -twoPHRMode: indicates whether power headroom is enabled for two PHRs (e.g., each PHR can be associated with an SRS resource set) -mpe-ProhibitTimer: indicates the value of the number of subframes for MPE reporting. The value can be one of a set of values ​​(e.g., sf10 out of sf10, sf20, sf50, sf100, sf200, sf500, sf1000, infinity, where sf10 corresponds to 10 subframes, and so on). -mpe-Reporting-FR2: Indicates whether the UE reports the MPE P-MPR in the PHR MAC control element -mpe-ResourcePool: Contains a list of SSB / CSI-RS resources for P-MPR reporting. Each resource may be configured with the serving cell index for which the resource is configured for the UE. -mpe-Threshold: Indicates the value of the P-MPR threshold in dB for reporting MPE P-MPR when FR2 is configured. The same value may apply to each serving cell (although the related functionality may be implemented independently for each cell). -multiplePHR: Indicates whether power headroom is reported using a single-input PHR MAC control element or a multiple-input PHR MAC control element. For example, multiplePHR can be a Boolean value where "True" means to use a multiple-input PHR MAC control element and "False" means to use a single-input PHR MAC control element (or vice versa). The network (e.g., BS) can configure this field to "True" for MR-DC and UL CA for NR, and to "False" in all other cases. - numberOfN: Indicates the number of reported P-MPR values ​​in the PHR MAC CE. -phr-ModeOtherCG: If dual connectivity (DC) is configured, indicates the mode (e.g., real or virtual) used for PHR of activated cells that are part of another cell group (e.g., MCG or SCG). If the UE is configured with only one cell group (e.g., no DC), the UE may ignore the field.

[0317] A PHR may be triggered to be transmitted based on the satisfaction of one or more conditions (or events), as described below. For example, a PHR may be triggered to be reported periodically (e.g., by expiration of a periodic timer) or when triggered based on a threshold. For example, power headroom reporting via a PHR may be triggered periodically by the expiration of a periodic timer, e.g., the phr-PeriodicTimer, which may be configured with a value ranging from approximately 10 milliseconds to infinity. Power headroom reporting may be triggered based on a threshold, such as a path loss change. For example, an NR PHR may be triggered if the path loss has changed by more than phr-Tx-PowerFactorChange dB for at least one activated serving cell of any MAC entity used as the path loss criterion since the last transmission of the PHR at this MAC entity, when the phr-ProhibitTimer expires or has expired and the MAC entity has UL resources for a new transmission. The path loss variation for a cell evaluated above can be between the path loss currently measured using the current path loss criterion and the path loss measured at the transmission time of the last PHR transmission using the path loss criterion currently in use, regardless of whether the path loss criterion has changed.

[0318] PHR may be triggered upon configuration or reconfiguration of the PHR function by a higher layer (e.g., RRC) that is not used to disable the PHR function. For example, PHR may be triggered upon activation of an SCell of any MAC entity with a configured uplink or upon addition of a PSCell (i.e., when a PSCell is newly added or modified). For example, PHR may be triggered for any of the activated serving cells of any MAC entity with a configured uplink when the phr-ProhibitTimer expires or has expired, when the MAC entity has UL resources for a new transmission, there are UL resources allocated for transmission, or there is a PUCCH transmission on this cell, and the power management (P-MPR) of this cell is enabled. cThe required power backoff due to power management (enabled by phr-Tx-PowerFactorChange dB) has changed by more than phr-Tx-PowerFactorChange dB since the last transmission of the PHR when the MAC entity had UL resources allocated for transmission on this cell or PUCCH transmission. For example, the PHR may be triggered upon switching of an activated BWP from a dormant BWP to a non-dormant DL BWP for an SCell (e.g., any MAC entity with a configured uplink). A wireless device (e.g., a MAC entity) may be configured to avoid triggering a PHR when the required power backoff due to power management decreases only temporarily (e.g., by up to a threshold amount of time (e.g., tens of milliseconds)), and when the PHR is triggered by other triggering conditions, the PHR may be triggered by other triggering conditions. CMAX、f、c Reflecting such a temporary decrease in the value of / PH may be avoided. If an HARQ process is configured with the cg-RetransmissionTimer and a PHR is already included in a MAC PDU for transmission on a grant configured by this HARQ process, but has not yet been transmitted by lower layers, it is up to the wireless device implementation how to handle the PHR content.

[0319] As described further below, based on triggering the PHR, the wireless device may generate a PHR and transmit the PHR via the MAC CE. For example, the PHR may include at least a PH value and a nominal (or calculated) UE maximum transmit power (P on carrier c) that may be transmitted by the wireless device, as described with respect to Figures 32A and 32B. CMAX、C ) can be generated to include

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

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

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

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

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

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

[0326] If the PDCCHs scheduling two PDSCHs are associated with different ControlResourceSets having different values ​​of CORESETPoolIndex, then for any two HARQ process IDs in a given scheduled cell, if a wireless device is scheduled to start receiving a first PDSCH starting at symbol j by a PDCCH associated with a value of CORESETpoolIndex ending at symbol i, then the wireless device may be scheduled to receive a PDSCH starting earlier than the end of the first PDSCH using a PDCCH associated with a different value of CORESETpoolIndex ending later than symbol i, and in the given scheduled cell, the wireless device may receive the first PDSCH in slot i, with its corresponding HARQ-ACK assigned to be transmitted in slot j, and a second PDSCH associated with a value of CORESETpoolIndex different from the value of the first PDSCH starting later than the first PDSCH, with its corresponding HARQ-ACK assigned to be transmitted in a slot prior to slot j.

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

[0328] FIG. 34B illustrates an example of communication between a base station (including multiple TRPs) and a wireless device (including a single panel or multiple panels) based on inter-cell TRP (or inter-PCI TRP). Unlike FIG. 34A, the multiple TRPs may be associated with (or belong to) different physical cells (cell 1 having PCI 1 and cell 2 having PCI 2), which may be associated with different PCIs and referred to as inter-cell TRP (or inter-PCI TRP). The cells may be the serving cell or a non-serving (neighboring) cell of the wireless device. When operating the inter-cell TRP of the wireless device, the base station may configure cell 2 having PCI 2 as part of cell 1 having PCI 1 (e.g., a second TRP having a second PCI different from the first PCI of the first TRP), in which case the wireless device may receive a first SSB from cell 1 having PCI 1 and a second SSB from cell 2 having PCI 2. The first SSB and the second SSB may have different configuration parameters, which may be implemented based on the example embodiments described above with respect to Figures 18, 19, and / or 20. According to the inter-cell TRP, a wireless device may receive a PDCCH / PDSCH and / or transmit a PUCCH / PUSCH on cell 1 including PCI1 and cell 2 including PCI2 having different TCI states (e.g., one associated with one of the first SSBs and the other associated with one of the second SSBs).

[0329] The serving cell may be a cell (e.g., a PCell, SCell, PSCell, etc.) from which the wireless device receives SSB / CSI-RS / PDCCH / PDSCH and / or transmits PUCCH / PUSCH / SRS. The serving cell is identified by a serving cell index (e.g., ServCellIndex or SCellIndex configured in an RRC message).

[0330] A non-serving (or neighboring) cell may be a cell from which the wireless device does not receive the PDCCH / PDSCH and / or does not transmit the PUCCH / PUSCH / SRS. A non-serving cell has a physical cell identifier (PCI) that is different from the PCI of the serving cell. A non-serving cell may not be identified by a serving cell index (e.g., ServCellIndex or SCellIndex). A wireless device may rely on the SSB of a non-serving cell for Tx / Rx beam (or spatial domain filter) decisions (for the PDCCH / PDSCH / PUCCH / PUSCH / CSI-RS / SRS, etc., of the serving cell) 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 3GPP TS 38.331). A base station does not transmit an RRC message configuring the PDCCH / PDSCH / PUCCH / PUSCH / SRS resources of a non-serving cell for the wireless device.

[0331] As shown in FIG. 34B, for a particular wireless device, Cell 1 may be the serving cell and associated with a first TRP (TRP1). Cell 2 may be a non-serving (or neighboring) cell and 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 IEs) for multiple (non-serving or neighboring) cells relative to Cell 1, each additional PCI configuration corresponding to a (non-serving or neighboring) cell having a PCI value different from the PCI value of the serving cell, including an additional PCI index (AdditionalPCIIndex) identifying the additional PCI configuration, the PCI of the non-serving cell, an SSB periodicity indication, a position indication of the (candidate) SSB in the SSB burst, a transmit power indication for the SSB, etc. The configuration parameters for Cell 1 may further indicate multiple TCI states. Each TCI state of 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 the QCL type among the multiple QCL types, for example, when an SSB is transmitted via cell 1 (or in another serving cell). When an SSB of the TCI state is transmitted via a non-serving (neighboring) cell, the TCI state may be further associated with an additional PCI index (AdditionalPCIIndex) indicating the (non-serving or neighboring) cell configured with the SSB-MTC-AdditionalPCI IE. Similar to multiple TRPs within a cell, a wireless device may receive downlink signals and / or transmit uplink signals based on the TCI state (activation / indication) associated with the TRP. The difference between multiple TRPs within a cell and multiple TRPs between cells is that the reference RS of the TCI state for the serving cell may come from (or be transmitted via) the (non-serving or neighboring) cell in the case of an inter-cell multiple TRP configuration. SSB may be implemented based on the exemplary embodiments described above with respect to FIGS. 18, 19, and / or 20.

[0332] In the example of Figure 34B, Cell 1 is the serving cell for the wireless device. Cell 2 is a (non-serving or neighboring) cell associated with Cell 1 of the wireless device. Cell 2 may be the serving cell for a second wireless device. Cell 1 may be a (non-serving or neighboring) cell for the second wireless device. Different wireless devices may have different serving and non-serving / neighboring cells.

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

[0334] In the examples of Figures 34A and 34B, the wireless device may be provided with two TCI states, each corresponding to a TRP among multiple TRPs. A TCI state may be referred to as a channel-specific TCI state if the TCI state is used for a specific channel (e.g., PDSCH / PDCCH / PUCCH / PUSCH), and different channels may be associated with different channel-specific TCI states. A TCI state may be referred to as a unified TCI state if the TCI state is used for multiple channels (e.g., PDSCH / PDCCH / PUCCH / PUSCH), and 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 a unified TCI state for the wireless device.

[0335] 34A and 34B, for example, when a wireless device is close to the center of a cell, the base station may perform data / signaling transmission based on multiple TRPs within the cell (e.g., which may be referred to as Intra-cell M-TRPs or Intra-PCI M-TRPs) for the wireless device, having more data to deliver and / or requiring high reliability (e.g., for URLLC services). As shown in FIG. 34B, for example, when the wireless device is at the edge of the cell and is in (moves or is located in) the coverage of another cell (which may or may not be the wireless device's serving cell), the base station may perform data / signaling transmission based on multiple TRPs between cells (e.g., which may be referred to as Inter-cell M-TRPs or Inter-PCI M-TRPs) for the wireless device.

[0336] In at least some wireless communications, a base station may enable power saving operation of a wireless device and indicate to the wireless device whether to wake up during the next DRX On Duration to monitor the PDCCH, for example, based on BWP management (e.g., as shown in FIG. 25), an SCell dormancy mechanism (e.g., as shown in FIG. 27), a wake-up / sleep instruction, due to limited battery capacity of the wireless device, etc. However, when the base station indicates power saving operation of the wireless device (e.g., based on the exemplary embodiments described above with respect to FIG. 25 and FIG. 27), it may not be able to reduce power (and save energy) of the base station's network devices. For example, the base station may be required to periodically transmit some always-on downlink signals (e.g., SSB, MIB, SIB1, SIB2, periodic CSI-RS, etc.) during some periods even when there are no active wireless devices transmitting / receiving to / from the base station. A base station may be required to transmit these always-on downlink signals when the base station transitions a cell to a dormant state by switching the cell's active BWP to a dormant BWP, for example, based on the exemplary embodiment described above with respect to FIG. 27.

[0337] In at least some wireless communications, if a base station needs to reduce the periodicity of always-on downlink signal transmissions for network energy saving, the base station may transmit an RRC message (e.g., SIB1) indicating a longer periodicity of always-on downlink signal transmissions. Before deciding to power off (e.g., both RF modules and baseband units (BBUs)) for network energy saving, the base station may transmit an RRC reconfiguration message to each wireless device in a source cell (e.g., PCell) to indicate handover to a neighboring cell (e.g., a second PCell).

[0338] FIG. 35 shows an exemplary HO procedure from a source base station (e.g., a first PCell of a source gNB or base station) to a target base station (e.g., a second PCell of a target gNB or target base station) of a wireless device. For network-controlled mobility in RRC_CONNECTED, the PCell may be changed using an RRC connection reconfiguration message 3501 (e.g., RRCReconfiguration) including reconfigurationWithSync (NR specification) or mobilityControlInfo in the LTE specification (handover). The SCell may be changed using an RRC connection reconfiguration message 3501 with or without reconfigurationWithSync or mobilityControlInfo. The network (e.g., source gNB) may trigger the HO procedure based on, for example, radio conditions, load, QoS, UE category, and / or the like. The RRC connection reconfiguration message 3501 may be implemented based on the exemplary embodiments described below in FIGS. 36 and 37.

[0339] As shown in Figure 35, the network may configure the wireless device to perform measurement reporting (which may include configuring measurement gaps). Measurement reporting is a Layer 3 report, different from Layer 1 CSI reporting. The wireless device may transmit one or more measurement reports 3502 to the source gNB (or a source PCell of the source gNB). The network may initiate HO blindly, meaning it has not received a measurement report 3502 from the wireless device. Before sending message 3501 (which may be an HO message) to the wireless device, the source gNB may prepare one or more target cells. The source gNB may select a target PCell from the one or more target cells.

[0340] As shown in FIG. 35, based on one or more measurement reports 3502 from the wireless device, the source gNB may provide the target gNB with a list of candidate cells for each frequency for which measurement information is available, for example, to reduce the RSRP value (which may indicate the quality of the connection). The source gNB may also include the available measurement information for the cells provided in the list. The target gNB may determine which cells are configured for use after the HO, which may include cells other than those indicated by the source gNB. As shown in FIG. 35, the source gNB may transmit the above information in an HO request 3503 sent to the target gNB. The target gNB may respond with an HO acknowledgement (ACK) message 3504. In one example, in the HO ACK message 3504, the target gNB may indicate the access stratum configuration used in the target cell for the wireless device.

[0341] The source gNB may transparently (e.g., without changing the value / content) forward the HO ACK message 3504 (or information thereof) received from the target gNB to the wireless device. In the HO message 3501 sent to the wireless device, the RACH resource configuration may be configured for the wireless device to access a target cell within the target gNB. If necessary, the source gNB may initiate data forwarding of (a subset of) the dedicated radio bearers.

[0342] 35, after receiving the HO message 3501, the wireless device may start an HO timer (e.g., T304) with an initial timer value. The HO timer may be configured in the HO message 3501. Based on the HO message 3501, the wireless device may apply RRC parameters of the target PCell of the target gNB and / or the cell group (MCG / SCG) associated with the target PCell and perform downlink synchronization to the target gNB (e.g., as described above with respect to FIGS. 17-23). After or in response to performing downlink synchronization to the target gNB (e.g., searching for a suitable / detectable SSB from candidate SSBs configured on the target gNB, based on the examples of Figures 19 and / or 20), the wireless device may initiate random access (e.g., contention-free or contention-based, based on the examples of Figures 13A, 13B, and / or 13C) to access the target gNB on an available RACH opportunity according to the RACH resource selection, which may be configured in the RACH resource configuration (e.g., based on the example embodiment of Figure 37, described below). When allocating a dedicated preamble for random access in the target gNB, the RAN may ensure that a preamble is available from the first RACH opportunity that the wireless device may use.

[0343] The wireless device may release the RRC configuration parameters of the source PCell and the MCG / SCG associated with the source PCell.

[0344] HO triggered by receiving an RRC reconfiguration message (e.g., RRCReconfiguration) containing an HO command / message (e.g., by including reconfigurationWithSync (NR specification) or mobilityControlInfo in the LTE specification (handover)) is referred to as normal HO, or unconditional HO, in contrast to conditional HO (CHO), which is described below in Figure 38.

[0345] As shown in FIG. 35, the wireless device may transmit a preamble 3505 to the target gNB via a RACH resource. The RACH resource may be selected from multiple RACH resources (e.g., configured in the rach-ConfigDedicated IE shown in FIGS. 36 and 37) based on the SSB / CSI-RS measurements of the target gNB. The wireless device may select the (best, e.g., strongest or RSRP) SSB / CSI-RS of the configured SSB / CSI-RS of the target gNB. The wireless device then determines a RACH opportunity (e.g., a time domain resource, etc.) associated with the selected SSB / CSI-RS and determines a preamble associated with the selected SSB / CSI-RS.

[0346] The target gNB may receive a preamble 3505 transmitted from the wireless device. The target gNB may transmit a random access response (RAR) 3506 to the wireless device, where the RAR 3506 includes the preamble 3505 transmitted by the wireless device. The RAR 3506 may further include a TAC to be used for uplink transmission over the target PCell. In response to receiving the RAR 3506 including the preamble, the wireless device may complete the random access procedure. In response to completing the random access procedure, the wireless device may stop the HO timer (T304). The wireless device may transmit an RRC reconfiguration complete message 3507 to the target gNB after the random access procedure is completed or before completing the random access procedure. After completing the random access procedure toward the target gNB, the wireless device may apply a first part of the CQI reporting configuration, the SR configuration, and the SRS configuration, which does not require the wireless device to know the system frame number (SFN) of the target gNB. Once the wireless device has acquired the SFN of the target gNB after completing the random access procedure towards the target PCell, the wireless device may apply a second part of the measurement and radio resource configuration that requires the wireless device to know the SFN of the target gNB (e.g., measurement gaps, periodic CQI reporting, SR configuration, SRS configuration).

[0347] Based on the HO procedure (e.g., as shown in FIG. 35), for the purpose of network energy saving, the base station may instruct each wireless device in the source cell to perform a four-step or two-step RACH-based (contention-free) HO to a neighboring cell. After the wireless device completes the HO procedure to the neighboring cell, the base station may turn off (RF unit, BBU, etc.) for energy saving.

[0348] The RRC reconfiguration message 3501 received from the source base station includes configuration parameters of the PHR function (e.g., mac-CellGroupConfig, these parameters are described above with respect to Figures 32A and 32B). The wireless device (e.g., the RRL layer of the wireless device) may reset its MAC entity in response to these configuration parameters received in the RRC reconfiguration message 3501. Based on the RRC reconfiguration message 3501 processed by the RRC layer (e.g., upper layers of the wireless device), the PH function may be configured or reconfigured according to these configuration parameters, as described further below with respect to Figure 45. The resetting MAC entity may cause the triggered PHR procedure (e.g., for the old PCell and / or SCell) to be canceled. As described with respect to Figure 32B, the wireless device may trigger a PHR of the target PCell in response to the parameters of the PHR function being configured or reconfigured (e.g., by upper layers). After triggering the PHR, the wireless device may obtain a PH value and transmit the PHR via the PHR MAC CE 3508, as described further below with respect to Figure 45. The MAC entity may obtain uplink resources, such as an uplink grant (e.g., from the target PCell after the wireless device completes handover to the target PCell), and therefore the wireless device may transmit the PHR MAC CE 3508 after a successful RAR transmission or after transmitting an RRCReconfigurationComplete, after which the wireless device may establish an RRC connection with the target PCell.

[0349] FIG. 36 shows an example embodiment of an RRC message for HO. In the example of FIG. 36, the base station may transmit, and / or the wireless device may receive, an RRC reconfiguration message (e.g., RRCReconfiguration-IE) indicating an RRC connection modification. It may convey information for measurement configuration, mobility control, radio resource configuration (including RBs, MAC primary configuration, and physical channel configuration), and AS security configuration. The RRC reconfiguration message may include the configuration of a master cell group (masterCellGroup). The master cell group may be associated with an SpCell (SpCellConfig). If the SpCellConfig includes a reconfiguration with Sync (reconfigurationWithSync), the wireless device determines that the SpCell is the target PCell for HO. The reconfiguration with Sync (reconfigurationWithSync) may include cell common parameters (spCellConfigCommon) of the target PCell, an RNTI (newUE-Identity) that identifies the wireless device in the target PCell, a value of T304, dedicated RACH resources (rach-ConfigDedicated), etc. The dedicated RACH resources may include one or more RACH opportunities, one or more SSBs, one or more CSI-RS, one or more RA preamble indices, etc. The RRCReconfiguration message may include configuration parameters for the master cell group (masterCellGroup), which may include a MAC-CellGroupConfig IE containing configuration parameters for the PHR function (phr-Config), such as the PHR configuration parameters described above with respect to Figure 32B.

[0350] Performing HO triggered by receiving an RRC reconfiguration message including the reconfigurationWithSync IE may introduce HO delay (e.g., too slow HO), for example, when the wireless device is moving in a network deployed with multiple small cells (e.g., cell coverage of several hundred meters of cells). An improved HO mechanism based on measurement event trigger is proposed to reduce the HO delay. An example of this improved mechanism is shown in Figure 37.

[0351] Figure 37 illustrates an example embodiment of a conditional handover (CHO) procedure. As shown, a network (e.g., a base station, a source gNB) may configure a wireless device to perform measurement reporting (which may include configuring measurement gaps) for multiple neighboring cells (e.g., cells from candidate target gNB1, candidate target gNB2, etc.). Measurement reporting is a Layer 3 report, distinct from a Layer 1 CSI report. The wireless device may transmit one or more measurement reports 3701 to a source gNB (or source PCell).

[0352] As shown in FIG. 37, based on one or more measurement reports 3701 from the wireless device, the source gNB may provide the target gNB with a list of best cells for each frequency for which measurement information is available, e.g., to reduce RSRP. The source gNB may also include the available measurement information for the cells provided in the list. The target gNB may determine which cells are configured for use after the CHO, which may include cells other than those indicated by the source gNB. As shown in FIG. 37, the source gNB may transmit the above information in an HO request 3702 to the target gNB. The target gNB may respond with an HO request ACK message 3703. In the HO request ACK message 3703, the target gNB may indicate the access stratum configuration (e.g., the RRC configuration of the target cell) used in the target cell for the wireless device.

[0353] The source gNB may transparently (e.g., without changing the value / content) forward to the wireless device (3704) the handover information received from the target gNB (e.g., information contained in the HO Request ACK message 3703 or the RRC Reconfiguration message from the target gNB).

[0354] The source gNB may configure a CHO procedure that differs from a normal HO procedure (e.g., as shown in Figure 35 and / or Figure 36) by sending a conditional reconfiguration message 3704 (e.g., a conditionalReconfiguration IE in an RRC reconfiguration message, described below in Figure 38). The conditional reconfiguration message 3704 may include a list of candidate target PCells, each candidate target PCell being associated with dedicated RACH resources for the RA procedure if CHO is performed for the candidate target PCell, CHO execution conditions (or RRC reconfiguration conditions) for each of the candidate target PCells, etc. The CHO execution conditions may include measurement event A3 where the candidate target PCell becomes an offset amount better than the current PCell (e.g., the PCell of the source gNB), measurement event A4 where the candidate target PCell becomes better than an absolute threshold configured in the conditional reconfiguration message 3704, measurement event A5 where the current PCell becomes worse than a first absolute threshold and the candidate target PCell becomes better than a second absolute threshold, etc.

[0355] In the example of Figure 38, the wireless device may evaluate the (RRC) reconfiguration condition for the list of candidate target PCells and / or current / source PCells according to the received conditional reconfiguration message 3704 including the parameters of the CHO procedure. The wireless device may measure the RSRP / RSRQ of SSB / CSI-RS of each candidate target PCell in the list of candidate target PCells. Unlike the normal HO procedure described with respect to Figure 35, the wireless device does not perform HO to the target PCell in response to receiving the conditional reconfiguration message 3704 including the parameters of the CHO procedure. The wireless device may perform HO to the target PCell for CHO if the (RRC) reconfiguration condition for the target PCell is met (or satisfied). Otherwise, the wireless device may continue to evaluate the reconfiguration condition for the list of candidate target PCells, for example, until the expiration of the HO timer or until it receives an RRC reconfiguration indicating the end of the CHO procedure.

[0356] 37, in response to the reconfiguration condition of a first candidate target PCell (e.g., PCell1) being met or satisfied, the wireless device may perform a CHO procedure toward the first candidate target PCell. The wireless device may select one of multiple candidate target PCells if multiple candidate target PCells meet or satisfy the reconfiguration condition.

[0357] Performing the CHO procedure toward the first candidate target PCell may be the same as or similar to performing the HO procedure as shown in FIG. 35. By performing the CHO procedure, the wireless device may release RRC configuration parameters of the source PCell and the MCG associated with the source PCell, apply RRC configuration parameters of PCell1, reset the MAC (which may configure or reconfigure PHR functionality), implement the cell group configuration of the received MCG included in the RRC reconfiguration message for PCell1, and / or perform an RA procedure 3705 on PCell1, etc. A PHR may be triggered based on the selected target PCell. Similar to FIG. 35, the PHR may be transmitted (3706), e.g., via a MAC CE, using uplink resources (e.g., an uplink grant configured by the selected candidate PCell1). Thus, the PHR may be transmitted (3706), e.g., after the RA procedure 3705 is completed and / or after the wireless device transmits an RRCReconfigurationComplete message 3707 to the selected target gNB.

[0358] The MCG of the RRC reconfiguration message for PCell1 (e.g., included in messages 3703 and 3704) may be associated with the SpCell (SpCellConfig) on ​​the target gNB1. If sPCellConfig includes a reconfiguration with Sync (reconfigurationWithSync), the wireless device determines that the SpCell is the target PCell (PCell1) for HO. The reconfiguration with Sync (reconfigurationWithSync) may include cell common parameters (spCellConfigCommon) of the target PCell, an RNTI (newUE-Identity) that identifies the wireless device in the target PCell, a value of T304, dedicated RACH resources (rach-ConfigDedicated), etc. The dedicated RACH resources may include one or more RACH opportunities, one or more SSBs, one or more CSI-RS, one or more RA preamble indices, etc. The wireless device may perform cell group configuration of the received master cell group included in the RRC reconfiguration message for PCell1 on the target gNB1 according to the example embodiment described above with reference to FIG. 35.

[0359] Figure 38 shows an example of an RRC message for CHO. As shown, the base station may transmit, and / or the wireless device may receive, an RRC reconfiguration message (e.g., RRCReconfiguration-V1610-IE) indicating the RRC connection modification. The RRC reconfiguration message may be included in a (parent) RRC reconfiguration message (e.g., RRCReconfiguration-IE) as shown in Figure 36, and the (parent) RRC reconfiguration message may include a (L3 beam / cell) measurement configuration (e.g., measConfig IE).

[0360] In the example of Figure 38, an RRC reconfiguration message (e.g., RRCReconfiguration-V1610-IE) may include a conditional reconfiguration IE (conditionalReconfiguration IE). The conditional reconfiguration IE may include a list of conditional reconfigurations (condReconfigToAddModList). Each conditional reconfiguration corresponds to a respective candidate target cell (PCell) in the list of candidate target cells. For each conditional reconfiguration in the list of conditional reconfigurations, the base station may indicate one or more measurement events (condExecutionCond) for triggering CHO on the candidate target PCell, an RRC reconfiguration message (condRRCReconfig) for the candidate target cell (PCell) received by the source gNB from the target gNB via the X2 / Xn interface. The RRC reconfiguration message for the candidate target cell may be implemented based on the exemplary embodiment described above with respect to Figure 36. The RRC reconfiguration message may include a configuration of a master cell group (masterCellGroup) for the target gNB. The master cell group may be associated with an SpCell (SpCellConfig). If SpCellConfig includes reconfiguration with Sync (reconfigurationWithSync), the SpCell is the target PCell for performing CHO. The reconfiguration with Sync (reconfigurationWithSync) may include cell common parameters (spCellConfigCommon) of the target PCell, an RNTI (newUE-Identity) that identifies a wireless device in the target PCell, a value of T304, dedicated RACH resources (rach-ConfigDedicated), etc. The dedicated RACH resources may include one or more RACH opportunities, one or more SSBs, one or more CSI-RS, one or more RA preamble indices, etc. In one example, the master cell group (masterCellGroup) parameters may include a MAC-CellGroupConfig IE that includes configuration parameters (phr-Config) of the PHR function, such as the PHR configuration parameters described above with respect to FIG. 32B.

[0361] In the example of FIG. 38, the measurement event for triggering CHO on the candidate target PCell (condExecutionCond) is an execution condition that needs to be met (at the wireless device) to trigger the execution of the conditional reconfiguration of CHO. The measurement event indication may point to a measurement ID (MeasId) that identifies a measurement configuration from multiple measurement configurations configured by the source gNB (e.g., included in the measConfig IE). A measurement configuration may be associated with measurement events (or conditional events) for multiple measurement values. The conditional events may include conditional event A3, conditional event A4, and / or conditional event A5, etc. Conditional event A3 is that the candidate target PCell becomes an offset amount better than the current PCell (e.g., the PCell of the source gNB). Conditional event A4 is that the candidate target PCell becomes better than an absolute threshold configured in the RRC reconfiguration message. Conditional event A5 is that the current PCell becomes worse than a first absolute threshold and the candidate target PCell becomes better than a second absolute threshold, etc. In some embodiments, when a conditional reconfiguration of CHO to a selected target PCell (candidate PCell1) is performed, configuration parameters of the PHR function (e.g., included in mac-CellGroupConfig) may be reconfigured, which may trigger PHR for the selected target PCell. PHR for candidate PCell1 of target gNB1 may be triggered in response to a conditional reconfiguration of CHO for a selected target PCell being performed based on an RRC reconfiguration message, including configuration parameters for the PHR function (very similar to the HO procedure in FIG. 35) and / or the candidate target PCell (to be activated / used) selected as the PCell. For example, the conditional reconfiguration of CHO (and / or the selected target PCell) may cause the PHR function to be (re)configured by a higher layer (e.g., RRC layer).The MAC entity may obtain uplink resources, such as an uplink grant (e.g., from the target PCell after the wireless device completes handover to the target PCell), and thus the wireless device may transmit a PHR MAC CE after a successful RAR transmission or after transmitting an RRCReconfigurationComplete, after which the wireless device may establish an RRC connection with the target PCell.

[0362] Performing CHO by a wireless device decision based on evaluating reconfiguration conditions on multiple candidate target cells (long-term and / or layer 3 beam / cell measurements against one or more configured thresholds) may cause cell load imbalance and / or lead to CHO failure, such as when the target cell changes its configuration (e.g., network energy saving) during the CHO condition evaluation. An improved handover based on layer 1 / 2 signaling trigger is proposed in Figure 39. Layer 1 signaling may include DCI transmitted via PDCCH. Layer 2 signaling may include MAC CE scheduled by DCI. Layer 1 / 2 signaling is different from layer 3 signaling for HO / CHO, which includes RRC reconfiguration messages. Layer 1 / 2 triggering PCell exchange / switching may enhance CHO, but its impact on PHR should be considered.

[0363] Figure 39 illustrates an example of a Layer 1 / 2 triggered HO procedure. As shown in Figure 39, the network (e.g., base station, source gNB) may configure the wireless device to perform measurement reporting (which may include configuring measurement gaps) for multiple neighboring cells (e.g., cells from candidate target gNB1, candidate target gNB2, etc.). The measurement reporting is a Layer 3 report, distinct from the Layer 1 CSI reporting. The wireless device may transmit one or more measurement reports 3901 to the source gNB (or source PCell, cell 0 in Figure 42).

[0364] As shown in FIG. 39, based on one or more measurement reports from the wireless device, the source gNB may provide the target gNB with a list of (highest signal strength / quality) cells for each frequency for which measurement information is available, e.g., to reduce RSRP. The source gNB may also include the available measurement information of the cells provided in the list. The target gNB may determine which cells to configure for use after HO (as the target PCell and / or one or more SCells), which may include cells other than those indicated by the source gNB. As shown in FIG. 39, the source gNB may transmit the above information in an HO request 3902 to the target gNB (or multiple target gNBs). The target gNB may respond by sending an HO request ACK message 3903. In the HO request ACK message 3903, the target gNB may indicate the access stratum configuration (e.g., the RRC configuration of the target cell) used in the target cell for the wireless device.

[0365] The source gNB may transparently (e.g., without changing the value / content) forward to the wireless device (3904) the handover information received from the target gNB (e.g., information included in the HO Request ACK message 3903 or the RRC reconfiguration message from the target gNB, the cell group configuration IE of the target gNB, and / or the SpCell configuration IE of the target PCell / SCell of the target gNB).

[0366] The source gNB may configure a Layer 1 / 2 signaling-based HO (PCell switching / change, mobility, etc.) procedure that differs from the regular HO procedure (e.g., shown in Figures 35 and / or 36) and / or CHO procedure (e.g., shown in Figures 37 and / or 38) by including a Layer 1 / 2 candidate PCell configuration message (e.g., a newly defined candidates-L1L2-Config IE) in the RRC reconfiguration message 3904 from the source gNB. The Layer 1 / 2 candidate PCell configuration message may include a list of candidate target PCells, each of which is associated with dedicated RACH resources for the RA procedure, such as when Layer 1 / 2 signaling-based HO is triggered by Layer 1 / 2 signaling and performed for the candidate target PCell. There may be multiple options for the parameter configuration of the candidate target PCells.

[0367] As a first option for parameter configuration, for each candidate target PCell, the source gNB RRC reconfiguration message 3904 may include a candidate target gNB (encapsulated) RRC reconfiguration message (e.g., RRCReconfiguration) received by the source gNB from the candidate target gNB over the X2 / Xn interface. The candidate target gNB (encapsulated) RRC reconfiguration message may reuse the same signaling structure of the source gNB RRC reconfiguration message 3904, as shown in FIG.

[0368] As a second option for parameter configuration, for each candidate target PCell, the RRC reconfiguration message 3904 from the source gNB may include a candidate target gNB's (encapsulated) cell group configuration message (e.g., CellGroupConfig) received by the source gNB from the candidate target gNB over the X2 / Xn interface. The candidate target gNB's (encapsulated) cell group configuration message may reuse the same signaling structure of the source gNB's cell group configuration message, as shown in Figure 36. The second option may reduce the signaling overhead of the candidate target PCell's parameter configuration compared to the first option.

[0369] As a third option f...

Claims

1. 1. A method comprising: one or more radio resource control (RRC) messages, by the wireless device, a first parameter of the serving cell; and receiving one or more RRC messages including a second parameter of the one or more candidate cells; receiving a medium access control (MAC) control element (CE) indicating a switch from using the serving cell as a primary cell (PCell) to using a first candidate cell of the one or more candidate cells as a PCell; Based on receiving the MAC CE, switching from using the serving cell as a PCell to using the first candidate cell as a PCell; canceling a triggered power headroom report (PHR) for the serving cell.

2. The method of claim 1 , further comprising indicating to a higher layer of the wireless device that the MAC CE has been received.

3. triggering a second PHR to the first candidate cell; The method of claim 1 , further comprising: transmitting the second PHR after switching from the serving cell to the first candidate cell.

4. The method of claim 1 , further comprising triggering a second PHR to the first candidate cell without resetting a MAC entity of the wireless device.

5. 2. The method of claim 1, wherein the one or more RRC messages include an instruction to reset a MAC entity of the wireless device, and the method includes resetting the MAC entity of the wireless device by the wireless device and based on the MAC CE.

6. The method of claim 1 , further comprising starting a PHR timer based on transmitting a second PHR for the first candidate cell.

7. The method of claim 1 , wherein the MAC CE indicates activation of a secondary cell (SCell) associated with the first candidate cell.

8. The method of claim 1 , further comprising activating a secondary cell (SCell) based on receiving the MAC CE.

9. The method of claim 1 , further comprising transmitting a second PHR to the first candidate cell via the first candidate cell.

10. 2. The method of claim 1, further comprising: switching from using the serving cell as a PCell to using the first candidate cell as a PCell by maintaining first parameters of the serving cell without releasing the first parameters.

11. 2. The method of claim 1, further comprising: switching from using the serving cell as a PCell to using the first candidate cell as a PCell by skipping a random access (RA) procedure associated with the first candidate cell before transmitting a second PHR for the first candidate cell.

12. 1. A method comprising: receiving, by the wireless device, one or more radio resource control (RRC) messages including configuration parameters of the source cell and one or more candidate cells; triggering a first power headroom report (PHR) to the source cell; receiving a medium access control (MAC) control element (CE) indicating a switch from using the source cell as a primary cell (PCell) to using a first candidate cell of the one or more candidate cells as a PCell; and canceling the first PHR to the source cell based on receiving the MAC CE.

13. triggering a second PHR to the first candidate cell; The method of claim 12 , further comprising: transmitting the second PHR after switching from the source cell to the first candidate cell.

14. 13. The method of claim 12, further comprising triggering a second PHR to the first candidate cell without resetting a MAC entity of the wireless device.

15. 13. The method of claim 12, wherein the one or more RRC messages include an instruction to reset a MAC entity of the wireless device, and the method includes resetting the MAC entity of the wireless device by the wireless device and based on the MAC CE.

16. 13. The method of claim 12, further comprising: switching from using the source cell as a PCell to using the first candidate cell as a PCell by maintaining first parameters of the source cell without releasing the first parameters.

17. 13. The method of claim 12, further comprising: switching from using the source cell as a PCell to using the first candidate cell as a PCell by skipping a random access (RA) procedure associated with the first candidate cell before transmitting a second PHR for the first candidate cell.

18. 1. A method comprising: one or more radio resource control (RRC) messages, by the wireless device, parameters of the first cell; receiving one or more RRC messages including: information indicating not to reset a media access control (MAC) entity of the wireless device after receiving a MAC control element (MAC CE) indicating switching to use the first cell as a primary cell (PCell); and receiving a first MAC CE indicating a switch from using a second cell as a PCell to using the first cell as a PCell; based on receiving the first MAC CE and the one or more RRC messages; canceling a first power headroom report (PHR) for the second cell; and triggering a second PHR to the first cell.

19. 20. The method of claim 18, further comprising: switching from using the second cell as a PCell to using the first cell as a PCell by maintaining first parameters of the second cell without releasing the first parameters.

20. 20. The method of claim 18, further comprising: switching from using the second cell as a PCell to using the first cell as a PCell by skipping a random access (RA) procedure associated with the first cell before transmitting the second PHR.

Images