Exposure detection and reporting for wireless communications

Abstract

To use one or more safety measures, such as maximum power exposure (MPE) reporting and / or related operations for one or more wireless communication devices for transmission and / or reception that may lead to potentially harmful exposure.SOLUTION: A wireless device 3415 transmits an uplink beam report 3435 in a communication network. The uplink beam report indicates that proximity to a human body or other living organism 3440 with a panel 1 of a plurality of panels is detected by the wireless device and / or that proximity to a human body is not detected for at least a panel 2 of the plurality of panels. The uplink beam report may be the same as or different from a CSI report. The wireless device 3415 performs proximity detection on one or more panels, such as the panel 1 and / or the panel 2. The wireless device 3415 triggers / initiates / sends, based on a measured P-MBR and / or a measured PHR, transmission of the uplink beam report.SELECTED DRAWING: Figure 34

Description

[Technical Field]

[0001] (CROSS-REFERENCE TO RELATED APPLICATIONS) This application claims the benefit of U.S. Provisional Patent Application No. 62 / 991,102, filed March 18, 2020, U.S. Provisional Patent Application No. 63 / 004,688, filed April 3, 2020, and U.S. Provisional Patent Application No. 63 / 012,342, filed April 20, 2020, each of which is incorporated herein by reference in its entirety. [Background technology]

[0002] Wireless communication can result in exposure to radio frequency electromagnetic fields. Limitations on exposure, such as power limits, may be imposed on wireless devices. Summary of the Invention

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

[0004] Wireless communications may use one or more devices for transmitting and / or receiving. Increasing the number of devices for transmitting and / or receiving, increasing the amount of wireless communications transmitted and received, and / or increasing the amount of power (and / or light used) for transmission and reception may increase the risk of potentially harmful and / or undesirable exposure to radio frequency electromagnetic fields. One or more safety measures may be implemented and / or required for wireless communication devices, such as reporting (e.g., maximum power exposure (MPE) reporting) and / or related actions that may reduce such exposure. Safety measures may be difficult to implement accurately and / or may require balancing exposure limits that may degrade device performance. For example, reduced power may result in transmission failures and / or increased reporting requirements may increase power usage. Wireless communications may be improved, for example, by implementing one or more safety measures while minimizing unnecessary reporting and / or other actions associated with the safety measures. A time window may be used to detect the amount of exposure instances. For example, a message indicating exposure may be sent based on the amount of exposure events during a time window that meets a threshold, to reduce unnecessary reporting and / or other operations and to meet safety measures. To improve synchronization between wireless devices and base stations in reporting, reports may be sent based on exposure detection and one or more messages for cell activation, bandwidth part (BWP) or other radio resource activation and / or switching, and / or discontinuous reception (DRX) or other state transitions, etc. Exposure reporting may be per panel using a power headroom report (PHR), such that panel-specific reports remain pending until sent in the PHR, to reduce signaling overhead in reporting.

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

[0006] Certain features are illustrated by way of example, and not by way of limitation, in the accompanying drawings in which like numerals refer to similar elements and in which: [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 exemplary format of a Medium Access Control (MAC) subheader in a MAC Protocol Data Unit (PDU). [Figure 5A] 1 illustrates an exemplary mapping for a downlink channel. [Figure 5B] 1 shows an example of uplink channel mapping. [Figure 6] 1 illustrates exemplary radio resource control (RRC) states and RRC state transitions. [Figure 7] An example of a frame configuration is shown below. [Figure 8] 1 illustrates an example resource configuration for one or more carriers. [Figure 9] 1 shows an exemplary configuration of a band part (BWP). [Figure 10A] 1 illustrates an example of a carrier aggregation configuration based on component carriers. [Figure 10B] 1 illustrates an exemplary cell group. [Figure 11A] 1 illustrates an example of a mapping of one or more synchronization signal / physical broadcast channel (SS / PBCH) blocks. [Figure 11B] 1 illustrates an example of mapping one or more channel state information reference signals (CSI-RS). [Figure 12A] 10 illustrates an example of a downlink ray management procedure. [Figure 12B] 1 illustrates an example of an uplink light management procedure. [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 illustrates an example of control channel element to resource element group (CCE-to-REG) mapping. [Figure 15A] 1 illustrates an example of communication between a wireless device and a base station. [Figure 15B] FIG. 1 illustrates exemplary elements of a computing device that may be used to implement any of the various devices described herein. [Figure 16A] 1 illustrates an example of uplink and downlink signal transmission. [Figure 16B] 1 illustrates an example of uplink and downlink signal transmission. [Figure 16C] 1 illustrates an example of uplink and downlink signal transmission. [Figure 16D] 1 illustrates an example of uplink and downlink signal transmission. [Figure 17A] 1 shows an exemplary MAC subheader. [Figure 17B] 1 shows an exemplary MAC subheader. [Figure 17C] 1 shows an exemplary MAC subheader. [Figure 18A] 1 shows an exemplary MAC PDU. [Figure 18B] 1 shows an exemplary MAC PDU. [Figure 19] Exemplary LCID values ​​are shown. [Figure 20] Exemplary LCID values ​​are shown. [Figure 21A]1 illustrates an exemplary SCell activation / deactivation MAC CE. [Figure 21B] 1 illustrates an exemplary SCell activation / deactivation MAC CE. [Figure 22] An example of bandwidth portion (BWP) management is shown below. [Figure 23] 10 illustrates an exemplary message comprising configuration parameters for a cell. [Figure 24] 10 shows an example of a message with configuration parameters for a search space. [Figure 25] 10 shows an example of a message comprising configuration parameters for a control resource set (CORESET). [Figure 26] 1 illustrates an example of wireless communication using multiple transmit / receive points (TRPs) and / or multiple panels. [Figure 27A] 1 illustrates an example of wireless communication using multiple TRPs and / or multiple panels. [Figure 27B] 1 shows an example of power reduction based on exposure. [Figure 28] 1 illustrates an exemplary method for exposure detection and / or reporting. [Figure 29] 1 illustrates an example of exposure instance detection for wireless communication. [Figure 30] 1 illustrates an exemplary method for coverage restoration and / or coverage loss mitigation. [Figure 31] 1 illustrates an exemplary method for coverage restoration and / or coverage loss mitigation. [Figure 32] 1 illustrates an exemplary method for coverage restoration and / or coverage loss mitigation. [Figure 33] 1 illustrates an example method for transmitting via configuration grants based on coverage loss. [Figure 34] Examples of P-MPR and / or PHR reports are shown. [Figure 35] 10 shows an example of an uplink ray report. [Figure 36] Examples of P-MPR and / or PHR reports are shown. [Figure 37]10 illustrates an example of uplink ray reporting and / or BWP switching. [Figure 38] 10 shows an example of an uplink ray report for a SCell. [Figure 39] An example of a DRX cycle is shown below. [Figure 40] 1 shows an example of a DRX configuration. [Figure 41A] 1 illustrates an example of power savings associated with a DRX configuration. [Figure 41B] 1 illustrates an example of power savings associated with a DRX configuration. [Figure 42] An example of power saving based on DCI instructions is shown below. [Figure 43A] 10 shows an example of uplink ray reporting using DRX. [Figure 43B] 10 shows an example of uplink ray reporting using DRX. [Figure 44] 10 shows an example of an uplink ray report using DRX. [Figure 45] 10 illustrates an exemplary method for uplink ray reporting in a power saving state. [Figure 46] 1 illustrates an example of a method for triggering a PHR procedure. [Figure 47] 1 illustrates an example method for PHR procedures. [Figure 48A] An example of a PHR is shown below. [Figure 48B] An example of a PHR is shown below. [Figure 48C] An example of a PHR is shown below. [Figure 49] An example of a multi-entry PHR MAC CE format is shown below. [Figure 50] 1 illustrates an exemplary method for SCell beam failure recovery (BFR). [Figure 51A] An example of the BFR MAC CE format is shown below. [Figure 51B] An example of the BFR MAC CE format is shown below. [Figure 52] 1 illustrates an example of prioritization of logical channels. [Figure 53] 10 shows an example of a power status report. [Figure 54] 10 shows an example of a condition for triggering a power status report. [Figure 55] 1 illustrates an exemplary method for power status reporting. [Figure 56A] 10 shows an example of a Panel Power Status Report MAC CE format. [Figure 56B] 10 shows an example of a Panel Power Status Report MAC CE format. [Figure 57] 10 shows an example of a Panel Power Status Report MAC CE format. [Figure 58] 10 shows an example of a power status report. [Figure 59] 1 illustrates an example method for SCell BFR procedure and / or power status reporting. [Figure 60] 10 shows an example of a Panel Power Status Report MAC CE format. DETAILED DESCRIPTION OF THE INVENTION

[0007] The accompanying drawings and description provide examples. It should be understood that the examples shown and / or described in the drawings are non-exclusive, and that the features shown and described may be implemented in other examples. Examples are provided for the operation of a wireless communication system that may be used in the field of multi-carrier communication systems. More particularly, the techniques disclosed herein may relate to wireless communication exposure detection and / or reporting.

[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 / operated by a network operator. The communication network 100 may comprise 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 one or more data networks (DNs) 108, and / or devices within the communication network 100 may communicate with (e.g., 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 the RAN 104 and / or the CN 104. 102, the CN 102 may communicate with one or more DNs 108. The CN 102 may provide / configure the wireless device 106 with one or more interfaces to one or more DNs 108. As part of its interfacing function, the CN 102 may set up end-to-end connections 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 over an air interface. The RAN 104 may communicate with the CN 102 via various communication methods (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 / via the air interface may be referred to as the downlink communication direction. The communication direction from the wireless device 106 to the RAN 104 via the air interface may be referred to as the uplink communication direction. The downlink transmission may be separated and / or distinguished from the 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 capable 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)), a user terminal (UT), 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 comprise 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), gNB, ng-eNB, relay node (e.g., integrated access and backhaul (IAB) node), donor node (e.g., donor eNB, donor gNB, etc.), access point (e.g., Wi-Fi access point), transmit and receive point (TRP), computing device, wireless communication enabled device, or any other device capable of transmitting and / or receiving signals. A base station may comprise one or more of each of the elements listed above. For example, a base station may include one or more TRPs. As other non-limiting examples, a base station may comprise, 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 Evolved Node B (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 connected to one or more Remote Radio Heads (RRHs), a repeater node or relay node used to extend the coverage area of ​​a donor node, a Next Generation Evolved Node B (ng-eNB), a Generation Node B (gNB) (e.g., associated with NR and / or fifth generation (5G) standards), an Access Point (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 equipment (e.g., a gNB central unit (gNB-CU)) and at least one base station distributed equipment (e.g., a gNB distributed 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 an air interface) with wireless devices 106. One or more base stations may include a set (e.g., three sets or any other number of sets) of antennas for respectively controlling multiple cells or sectors (e.g., three cells, three sectors, any other number of cells, or any other number of sectors). The size of a cell may be determined by the range over which a receiver (e.g., a base station receiver) can successfully receive a transmission from a transmitter (e.g., a wireless device transmitter) operating within the cell. One or more of the cells of a base station (e.g., alone or in combination with other cells) may provide / establish wireless coverage to wireless devices 106 over a wide geographic area to support wireless device mobility. A base station with three sectors (e.g., or n sectors, where n refers to any number 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 sectorized sites having more or less than three sectors. One or more base stations of the RAN 104 may be implemented as access points, as baseband processing devices / units coupled to several RRHs, and / or as repeater or relay nodes used to extend the coverage area of ​​a node (e.g., a donor node). The baseband processing devices / units coupled to the RRHs may be part of a centralized or cloud RAN architecture, for example, where the baseband processing devices / units may be concentrated into a pool of baseband processing devices / units or may be virtualized. A repeater node may amplify and transmit (e.g., transmit, retransmit, rebroadcast, etc.) radio signals received from a donor node. A relay node may perform substantially the same / similar functions as a repeater node. A relay node may decode radio signals received from a donor node, for example, to remove noise before amplifying and transmitting the radio signals.

[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. 104 may be arranged as a heterogeneous network of base stations (e.g., different base stations with 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 with high data traffic (or so-called "hot spots") or areas with 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 communications by the 3rd Generation Partnership Project (3GPP®) (e.g., one or more network elements similar to those of communications network 100), communications by the Institute of Electrical and Electronics Engineers (IEEE), communications by the International Telecommunications Union (ITU), communications by the International Organization for Standardization (ISO), etc. 3GPP produces specifications for multiple generations of mobile networks, namely, 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 further generations of communications networks (e.g., 6G and / or any other generation of communications networks). Examples may be described in connection with one or more elements (e.g., RAN) of a 3GPP 5G network, referred to as Next Generation RAN (NG-RAN), or any other communications network, such as a 3GPP network and / or a non-3GPP network. The examples described herein may be applicable to other communication networks, such as 3G and / or 4G networks, as well as communication networks yet to be finalized / specified (e.g., 3GPP 6G networks), satellite communication networks, and / or any other communication networks. NG-RANs may be provisioned to implement and upgrade to 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] 1B illustrates an exemplary communication network 150. The communication network may include a mobile communication network. The communication network 150 may comprise, for example, a PLMN operated / managed / run by a network operator. The communication network 150 may include a CN 1A , the communications network 150 may comprise one or more of a 5G core network (5G-CN) 152 (e.g., a 5G core network (5G-CN)), a RAN 154 (e.g., an NG-RAN), and / or wireless devices 156A and 156B (collectively wireless devices 156). The communications network 150 may include one or more data networks (DNs) 170, and / or devices within the communications network 150 may be in communication with (e.g., 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., a 5G-CN) may provide / configure one or more interfaces to the wireless device 156 to 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 functionality, the CN 152 (e.g., a 5G-CN) may set up an end-to-end connection between the wireless device 156 and one or more DNs, authenticate the wireless device 156, and / or provide / configure charging functionality. The CN 152 (e.g., a 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., a 5G-CN) may be defined as a network function that provides services via interfaces to other network functions. The network functions (e.g., 5G CN) of CN 152 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., a 5G-CN) may include an Access and Mobility Management Function (AMF) device 158A and / or a User Plane Function (UPF) device 158B, which may be separate components or a single component AMF / UPF device 158. The UPF device 158B may function as a gateway between the RAN 154 (e.g., an 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 triggering. The UPF device 158B can function as an anchor point for intra- / inter-radio access technology (RAT) mobility, an outer protocol (or packet) data unit (PDU) session point interconnecting one or more DNs, and / or a branching point to support multi-homed PDU sessions. The wireless device 156 can be configured to receive services via PDU sessions, which can be logical connections between the wireless device and the DNs.

[0019] The AMF device 158A may perform functions such as non-access stratum (NAS) signaling termination, NAS signaling security, access stratum (AS) security control, inter-CN node signaling for mobility between access networks (e.g., 3GPP access networks and / or non-3GPP networks), idle mode wireless device reachability (e.g., idle mode UE reachability for controlling and executing paging retransmissions), registration area management, intra-system and inter-system mobility support, access authentication, access authorization including checking roaming rights, mobility management control (e.g., subscription and policy), 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 comprise one or more additional network functions that may not be shown in Figure 1B. CN 152 (e.g., 5G-CN) may comprise 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 Publication 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., an NG-RAN) may communicate with wireless devices 156 over wireless communications (e.g., an air interface). The wireless devices 156 may communicate with the CN 152 via the RAN 154. The RAN 154 (e.g., an NG-RAN) may comprise one or more base stations of a first type (e.g., gNBs including gNBs 160A and 160B (collectively gNBs 160)) and / or one or more base stations of a second type (e.g., ng eNBs including ng-eNBs 162A and 162B (collectively ng eNBs 162)). The RAN 154 may comprise one or more base stations of any number of types. The gNBs 160 and ng eNBs 162 may be referred to as base stations. The base stations (e.g., the gNBs 160 and ng eNBs 162) may comprise one or more sets of antennas for communicating over wireless communications (e.g., an air interface) with the wireless devices 156. One or more base stations (e.g., gNB 160 and / or ng-eNB 162) may be equipped with multiple antenna sets to each control multiple cells (or sectors). The cells of the base stations (e.g., gNB 160 and 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., a 5G CN) via a first interface (e.g., an NG interface) and to other base stations via a second interface (e.g., an Xn interface). The NG and Xn interfaces may be established using a direct physical connection and / or an indirect connection via 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 number 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) communicate with one or more interfaces (e.g., NG interfaces) via the AMF / UPF A base station (e.g., gNB 160A) may communicate with and / or be connected to one or more AMF / UPF devices, such as AMF 158A, UPF 158B, of the AMF / UPF 158 via an NG user plane (NG-U) interface. The NG-U interface may provide / perform delivery (e.g., non-guaranteed delivery) of user plane PDUs between the base station (e.g., gNB 160A) and the UPF device (e.g., UPF 158B). A base station (e.g., gNB 160A) may communicate with and / or be connected to an AMF device (e.g., AMF 158A) via an NG control plane (NG-C) interface. The NG-C interface may provide / perform, for example, NG interface management, wireless device context management (e.g., UE context management), wireless device mobility management (e.g., UE mobility management), NAS message transfer, 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 terminations toward wireless device 156 via the Uu interface. A base station (e.g., gNB 160A) may provide user plane and control plane protocol terminations toward wireless device 156A via the Uu interface associated with a first protocol stack. A base station (e.g., ng-eNB 162) may provide Evolved UMTS Terrestrial Radio Access (E UTRA) user plane and control plane protocol terminations toward 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 UTRA user plane and control plane protocol terminations toward wireless device 156B via 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). It may also be possible for an NR network / device (or any first network / device) to connect to a 4G core network / device (or any second network / device) in a non-standalone mode (e.g., non-standalone operation). In non-standalone mode / operation, the 4G core network can be used to provide (or at least support) control plane functions (e.g., initial access, mobility, and / or paging). Although 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 balancing 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). The user plane may process data related to a user (e.g., data of interest to a user). The 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 comprise any number / quantity and / or types of devices, such as, for example, computing devices, wireless devices, mobile devices, handsets, tablets, laptops, Internet of Things (IoT) devices, hotspots, cellular repeaters, computing devices, and / or, more generally, user equipment (e.g., UEs). While reference may be made herein to one or more of the above types of devices (e.g., UEs, wireless devices, computing devices, etc.), it should be understood that any device herein may include any one or more of the 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 may be understood that one or more features and steps may be implemented in any device and / or any network.

[0028] FIG. 2A illustrates an example of a user plane configuration. The user plane configuration may include, for example, an NR user plane protocol stack. FIG. 2B illustrates an example 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 comprise multiple layers (e.g., five layers or any other number 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 higher layers in the protocol stack and may correspond to Layer 1 of the Open Systems Interconnection (OSI) model. The protocol layers above PHY 211 may comprise a medium 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. The protocol layers above PHY 221 may include a Medium 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 221 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 an example of 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. The SDAP (e.g., the SDAPS 215 and 225 shown in FIGS. 2A and 3) may perform quality of service (QoS) flow processing. A wireless device (e.g., wireless devices 106, 156A, 156B, and 210) may receive a service 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. The UPF (e.g., the UPF 158B) of the CN may map IP packets to one or more QoS flows 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 SDAP 215 and 225 may perform mapping / demapping between one or more QoS flows 310 and one or more radio bearers 320 (e.g., data radio bearers). The mapping / demapping 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 the radio bearers 320 via reflected mapping and / or control signaling received from the base station 220. In the case of reflected mapping, the SDAP 225 of the base station 220 may mark downlink packets with a QoS flow indicator (QFI) that can be monitored / detected / identified / indicated / observed by the SDAP 215 of the wireless device 210 to determine the mapping / demapping 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 packets that are not delivered due to, for example, handover (e.g., intra-gNB handover), in-order delivery and packet reordering, and / or removal of duplicately received packets. PDCPs 214 and 224 may perform packet duplication, for example, to improve the likelihood that a packet will be received. A receiver may receive packets duplicately and remove duplicate packets. Packet duplication may be useful for certain services, such as services that require high reliability.

[0032] The PDCP layer (e.g., PDCP 214 and 224) can perform mapping / demapping 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 technique that enables a wireless device to communicate with multiple cells (e.g., two cells) or, more generally, multiple cell groups including a master cell group (MCG) and a secondary cell group (SCG). 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, a split bearer can be configured and / or used. The PDCP 214 and 224 can map / demap between split radio bearers belonging to a cell group and the RLC channel 330.

[0033] The RLC layer (e.g., RCL 213 and 223) may perform segmentation, retransmission, and / or removal of duplicate data units received from the MAC layer (MAC 212 and 222, respectively) via automatic repeat request (ARQ). 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 may perform one or more of the described functions, for example, based on the transmission mode in which the RLC layer is operating. RLC configuration may be per logical channel. RLC configuration may be independent of numerology and / or transmission time interval (TTI) duration (or other duration). The RLC layer (e.g., RLC 213 and 223) may provide / configure RLC channels as services to the PDCP layer (e.g., PDCP 214 and 224, respectively), as shown in FIG. 3.

[0034] The MAC layer (e.g., MAC 212 and 222) can perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. Multiplexing / demultiplexing may include multiplexing / demultiplexing data units / portions belonging to one or more logical channels 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) can be configured to perform scheduling, scheduling information reporting, and / or priority handling between wireless devices via dynamic scheduling. Scheduling can be performed by the base station (e.g., base station 220 at MAC 222) for the downlink and / or uplink. The MAC layer (e.g., MAC 212 and 222) can be configured to perform logical channel prioritization and / or padding between logical channels of the wireless device 210 via hybrid automatic repeat request (HARQ) (e.g., one HARQ entity per carrier in the case of carrier aggregation (CA)). The MAC layer (e.g., MAC 212 and 222) can support one or more numerologies and / or transmission timings. Mapping restrictions in logical channel prioritization can control which numerologies and / or transmission timings a logical channel can use. The MAC layer (e.g., MAC 212 and 222) can provide / configure logical channels 340 as services to the RLC layer (e.g., RLC 213 and 223).

[0035] The PHY layer (e.g., PHYs 211 and 221) can perform, for example, mapping of transport channels to physical channels and / or digital and analog signal processing functions to transmit and / or receive information (e.g., over an air interface). The digital and / or analog signal processing functions can include, for example, coding / decoding and / or modulation / demodulation. The PHY layer (e.g., PHYs 211 and 221) can perform multi-antenna mapping. The PHY layer (e.g., PHYs 211 and 221) can 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 exemplary 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 illustrated 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 number of packets (e.g., three or any other quantity) may be determined from a second number of TBs (e.g., two or another quantity).

[0037] A downlink data flow may begin, for example, when SDAP 225 receives three IP packets (or other number of IP packets) from one or more QoS flows and maps the three packets (or other number of packets) to a radio bearer (e.g., radio bearers 402 and 404). SDAP 225 may map IP packets n and n+1 to the first radio bearer 402 and map IP packet m to the second radio bearer 404. An SDAP header (labeled with an "H" before each SDAP SDU shown in FIG. 4A) may be added to the IP packets to generate an SDAP PDU, which may be referred to as a PDCP SDU. Data units transferred to and from higher protocol layers may be referred to as service data units (SDUs) of the lower protocol layer, and data units transferred to and from lower protocol layers may be referred to as protocol data units (PDUs) of the higher protocol layer. 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 respect 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 packet m 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 multiple RLC PDUs (MAC SDUs). The MAC 222 can attach a MAC subheader to the RCL PDU (MAC SDU) to form a TB. The MAC subheader can be distributed across the MAC PDU (e.g., in the NR configuration shown in Figure 4A). The MAC subheader is completely The NR MAC PDU structure can reduce processing time and / or associated latency, 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., in 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 aid 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 223 or MAC 222. As shown in FIG. 4B, two MAC CEs may be inserted / appended before two MAC PDUs. 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 bandwidth 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. A MAC CE may be preceded by a MAC subheader having a format similar to that described for the MAC subheader of a MAC SDU and may be identified with a reserved value in the LCID field indicating the type of control information contained in the corresponding MAC CE.

[0041] FIG. 5A shows an example mapping for downlink channels. Mapping of uplink channels may include mapping between channels (e.g., logical channels, transport channels, and physical channels) for the downlink. FIG. 5B shows an example mapping for uplink channels. Mapping of uplink channels may include mapping between channels (e.g., logical channels, transport channels, and physical channels) for the uplink. Information may be passed over / via channels between the RLC layer, MAC layer, and PHY layer of a protocol stack (e.g., an NR protocol stack). Logical channels may be used between the RLC layer and the MAC layer. Logical channels may be classified / designated as control channels (e.g., in an NR control plane) that can carry control and / or configuration information or as traffic channels (e.g., in an NR user plane) that can carry data. 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. A set of logical channels (e.g., in an NR configuration) may comprise one or more channels described below. A paging control channel (PCCH) may include / transmit one or more paging messages used to page wireless devices whose locations are unknown to the network at the cell level. A broadcast control channel (BCCH) may include / carry system information messages in the form of a master information block (MIB) and several system information blocks (SIBs). 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. A common control channel (CCCH) may include / transmit control messages along with random access. A dedicated control channel (DCCH) may include / transmit control messages to / from specific wireless devices to configure the wireless devices with configuration information. A dedicated traffic channel (DTCH) may include / transmit 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 (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 / transmit paging messages originating 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 use physical channels to pass / transfer information between processing levels of the PHY layer. A physical channel may have an associated set of time-frequency resources for carrying information of one or more transport channels. The PHY layer may generate control information to support low-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 comprise one or more of the following channels: The Physical Broadcast Channel (PBCH) may include / carry the MIB from the BCH. The Physical Downlink Shared Channel (PDSCH) may include / carry downlink data and signaling messages from the DL-SCH 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 contain / carry uplink data and signaling messages from the UL-SCH, and possibly Uplink Control Information (UCI), as described below. The Physical Uplink Control Channel (PUCCH) may comprise / transmit UCI, which may comprise HARQ acknowledgments, Channel Quality Indicators (CQIs), Precoding Matrix Indicators (PMIs), Rank Indicators (RIs), and Scheduling Requests (SRs). For random access, the Physical Random Access Channel (PRACH) may be used.

[0045] The physical layer may generate physical signals to support low-level operations of the physical 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), a sounding reference signal (SRS), a phase tracking reference signal (PT RS), and / or any other signals.

[0046] One or more channels (e.g., logical channels, transport channels, physical channels, etc.) can be used to perform functions associated with a control plan 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) can 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 the same / similar to the exemplary user plane configuration (e.g., an NR user plane protocol stack). The four similar 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 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 AMF 230, which includes 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 CN (e.g., CN 152 or any other CN). NAS protocols 217 and 237 may provide control plane functions between wireless device 210 and AMF 230 via signaling messages called NAS messages. There may not be a direct path between wireless device 210 and AMF 230 over which NAS messages can 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 by signaling messages, which may be referred to as RRC messages. The RRC messages may be transmitted / 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 functions: 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 (e.g., wireless device measurement reporting) and reporting control; radio link failure (RLF) detection and recovery from radio link failure; and / or NAS message forwarding. As part of establishing an RRC connection, the RRC layers 216 and 226 may establish an RRC context, which may include setting 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 the same as 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 the wireless device. For example, this may be during an RRC connected state. During the RRC connected state (e.g., during RRC connected 602), the wireless device has an established RRC context and may have at least one RRC connection with a base station. The base station may be similar to one of 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 an 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: AS context; radio link configuration parameters; bearer configuration information (e.g., related to data radio bearers, signaling radio bearers, logical channels, QoS flows, and / or PDU sessions); security information; and / or layer configuration information (e.g., PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information). During the RRC connected state (e.g., RRC connected 602), the mobility of the wireless device may be managed / controlled by the RAN (e.g., RAN 104 or NG RAN 154). The wireless device may measure received signal levels (e.g., reference signal level, reference signal received power, reference signal received quality, received signal strength indicator, etc.) based on one or more signals transmitted from the serving cell and neighboring cells. The wireless device may report these measurements to its serving base station (e.g., the 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 most of the time (e.g., to conserve battery power). The wireless device may wake up periodically (e.g., once 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 include 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. Maintaining the RRC context may enable / enable a fast transition to an RRC connected state (e.g., RRC connected 602) with reduced signaling overhead compared to a transition from an RRC idle state (e.g., RRC idle 606) to an RRC connected state (e.g., RRC connected 602). During the RRC inactive state (e.g., RRC inactive 604), the wireless device may sleep, and the mobility of the wireless device may be managed / controlled by the wireless device via cell reselection. The RRC state may transition from the RRC inactive state (e.g., RRC inactive 604) to the RRC connected state (e.g., RRC connected 602) via a connection resumption procedure 614. The RRC state can transition from an RRC inactive state (e.g., RRC inactive 604) to an RRC idle state (e.g., RRC idle 606) via a connection release procedure 616, which can be the same as or similar to the connection release procedure 608.

[0053] The RRC states may be associated with mobility management mechanisms. During an RRC idle state (e.g., RRC idle 606) and an RRC inactive state (e.g., RRC inactive 604), mobility may be managed / controlled by the wireless device via cell reselection. The purpose of mobility management during an RRC idle state (e.g., RRC idle 606) or an RRC inactive state (e.g., RRC inactive 604) may be to enable / allow the network to notify the wireless device of an event via a paging message without having to broadcast the paging message throughout the entire mobile communication network. 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 (e.g., instead of sending a paging message throughout the entire mobile communication network), for example, so that a paging message may be broadcast through cells of the cell group in which the wireless device currently resides. Mobility management mechanisms for the RRC idle state (e.g., RRC idle 606) and the RRC inactive state (e.g., RRC inactive 604) can track wireless devices at a cell group level. The mobility management mechanism can, for example, perform tracking using different levels of grouping granularity. There can be multiple levels of cell grouping granularity (e.g., three levels of cell grouping granularity: individual cells; cells within a RAN area identified by a RAN Area Identifier (RAI); and cells within a group of RAN areas, called a tracking area and identified by a tracking area identifier (TAI)).

[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, 5G CN 152, or any other CN) may send a list of TAIs associated with a wireless device registration area (e.g., UE registration area) 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 and provide the wireless device with a new UE registration area, for example, when the wireless device moves (e.g., via cell reselection) to a cell associated with a TAI that may not be included in the list of TAIs associated with the UE registration area.

[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 / provided / configured with 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. For example, if the wireless device moves (e.g., via cell reselection) to a cell that is not included in the RAN notification area assigned / provided / configured to the wireless device, the wireless device may perform a notification area update with the RAN to update the RAN notification area of ​​the wireless device.

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

[0057] A base station (e.g., gNB 160 of 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 to one or more symbols (e.g., orthogonal frequency division multiplexing (OFDM) symbols in an NR configuration or any other symbols). OFDM is a multicarrier communication scheme that transmits / transmits data over F orthogonal subcarriers (or tones). For example, before transmitting the data, the data may be mapped to a series of complex symbols called source symbols (e.g., M-quadrature amplitude modulation (M-QAM) symbols, M-phase shift keying (M-PSK) symbols, or any other modulation symbols) and split into F parallel symbol streams. The F parallel symbol streams may be treated as if they were in the frequency domain. The F parallel symbols may be used as inputs to an inverse fast Fourier transform (IFFT) block, which converts them to the time domain. The IFFT block may take in 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 F sinusoidal basis functions corresponding to the F orthogonal subcarriers. The output of the IFFT block may be F time-domain samples representing the sum of F orthogonal subcarriers. The F time-domain samples may form a single OFDM symbol. The OFDM symbol provided / output by the IFFT block may be 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 be used by one or more wireless devices in the uplink to generate a discrete Fourier transform (DFT)-precoded OFDM symbol and reduce the peak-to-average power ratio (PAPR). Inverse processing may be performed on the OFDM symbol at the receiver using the FFT block to recover the data mapped to the source symbol.

[0059] FIG. 7 illustrates an example frame structure. A frame may comprise, for example, an NR radio frame into which OFDM symbols may be grouped. A frame (e.g., an NR radio frame) may be identified / indicated by a system frame number (SFN) or any other value. The SFN may repeat at a period of 1024 frames. One NR frame may be 10 milliseconds (ms) in duration and may include 10 subframes, each 1 ms in duration. The 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 number of symbols, slots, or durations may be used over 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 various deployments (e.g., from cells with carrier frequencies below 1 GHz to cells with carrier frequencies in the mmWave 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 μs, for example, for numerology in an NR configuration or any other radio configuration. The numerology may be defined for the following subcarrier spacing / cyclic prefix duration combinations: 15 kHz / 4.7 μs; 30 kHz / 2.3 μs; 60 kHz / 1.2 μs; 120 kHz / 0.59 μs; 240 kHz / 0.29 μs, and / or any other subcarrier spacing / cyclic prefix duration combination.

[0061] A slot can have a fixed number / number 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 number-dependent slot duration and slot-per-subframe transmission structure is shown in Figure 7 (a numerology with 240 kHz subcarrier spacing is not shown in Figure 7). A subframe (e.g., in an NR configuration) can be used as a number-independent time reference. A slot can be used as the unit by which uplink and downlink transmissions are scheduled. Scheduling (e.g., in an NR configuration) can be decoupled from the slot duration. Scheduling can start at any OFDM symbol. Scheduling can continue for as many symbols as necessary for transmission, e.g., to support low latency. These partial slot transmissions can be referred to as minislot or subslot transmissions.

[0062] FIG. 8 shows an example resource configuration of one or more carriers. This resource configuration may include slots in the time and frequency domains for an NR carrier or any other carrier. A slot may comprise resource elements (REs) and resource blocks (RBs). A resource element (RE) may be the smallest physical resource (e.g., in an NR configuration). An RE may span one OFDM symbol in the time domain by one subcarrier in the frequency domain, as illustrated in FIG. 8, for example. An RB may span 12 consecutive REs in the frequency domain, as illustrated in FIG. 8, for example. A carrier (e.g., an NR carrier) may be limited to a width of a certain number of RBs and / or subcarriers (e.g., 275 RBs or 275 × 12 = 3300 subcarriers). If such restrictions are used, the carrier (e.g., an NR carrier) frequency may be limited 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 per carrier bandwidth limit. 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., NR as shown in FIG. 8). In other example 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 can receive the entire carrier bandwidth (e.g., due to hardware limitations and / or different wireless device capabilities). Receiving and / or utilizing the entire carrier bandwidth may be prohibitive, for example, with respect to wireless device power consumption. A wireless device may adapt the size of its reception bandwidth (e.g., to reduce power consumption and / or for other purposes), for example, based on the amount of traffic the wireless device is scheduled to receive. Such adaptation may be referred to as bandwidth adaptation.

[0064] The configuration of one or more band portions (BWPs) can support one or more wireless devices that cannot receive the entire carrier bandwidth. The BWPs can, for example, support bandwidth adaptation for such wireless devices that cannot receive the entire carrier bandwidth. A BWP (e.g., a BWP in 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 at a given time, for example. 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., in the case of unpaired spectrum). A downlink BWP and an uplink BWP may be linked, for example, if 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., in the case of 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 within a set of configured downlink BWPs on a primary cell (PCell) or a secondary cell (SCell). A search space may comprise a set of locations in the time and frequency domains where the wireless device may 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) in an active downlink BWP.

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

[0068] One or more BWP indicator fields may be provided / included in the downlink control information (DCI). The value of the BWP indicator field may indicate which BWPs in the set of configured BWPs are active downlink BWPs for one or more downlink receptions. The value of the one or more BWP indicator fields may indicate active uplink BWPs 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 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 the default downlink BWP for paired spectrum operation; the wireless device detecting a DCI indicating an active downlink BWP other than the default downlink BWP for unpaired spectrum operation; and / or the wireless device detecting a DCI indicating an active uplink BWP other than the default uplink BWP for unpaired spectrum operation. For example, if the wireless device does not detect a DCI for a certain time interval (e.g., 1 ms or 0.5 ms), the wireless device may start / run the BWP inactivity timer towards a timeout (e.g., increment from 0 to the BWP activity timer value or decrement from the BWP inactivity timer value to 0). The wireless device may switch from an active downlink BWP to a 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 may 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., when the second BWP is a default BWP).

[0072] Switching a downlink BWP 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). Switching an uplink BWP 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). Switching between downlink BWPs and uplink BWPs may be performed independently (e.g., in paired spectrum / spectrum). Switching between downlink BWPs and uplink BWPs may be performed simultaneously (e.g., in unpaired spectrum / spectrum). Switching between configured BWPs may be based on, for example, RRC signaling, DCI signaling, BWP inactivity timer expiration, and / or random access initiation.

[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) can switch from one BWP to another at a switching 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 BWPs at a switching point. The wireless device may switch from BWP 902 to BWP 904 at switching point 908. The switch at switching point 908 may be made 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 active 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 active 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 active BWP 906 to BWP 904 at switch point 912, for example, after or in response to receiving a DCI indicating BWP 904 as the new active BWP.The wireless device may switch from the active BWP 902 to BWP 904 at switching point 914, for example, after or in response to receiving a DCI indicating BWP 904 as the new active BWP.

[0074] A wireless device procedure for switching BWPs on a secondary cell may be the same / similar to the procedure on a primary cell, for example, if the wireless device is configured for a secondary cell with default downlink BWPs and timer values ​​in the set of configured downlink BWPs. The wireless device may use the timer values ​​and default downlink BWPs of the secondary cell in the same / similar manner as the wireless device uses the timer values ​​and / or default BWPs of the primary cell. The timer values ​​(e.g., BWP inactivity timer) 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, for example, based on the expiration of a BWP inactivity timer.

[0075] Two or more carriers may be aggregated to simultaneously transmit / transmit data to / from the same wireless device using carrier aggregation (CA) (e.g., to increase the data rate). The aggregated carriers in CA may be referred to as component carriers (CCs). For example, when CA is configured / used, there may be a number / quantity of serving cells for the 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 CCs. As shown in FIG. 10A, three types of CA configurations may include an intra-band (contiguous) configuration 1002, an intra-band (discontiguous) configuration 1004, and / or an inter-band configuration 1006. In the intra-band (adjacent) configuration 1002, two CCs may be aggregated in the same frequency band (frequency band A) and located directly adjacent to each other within the frequency band. In the intra-band (discontiguous) configuration 1004, two CCs may be aggregated in the same frequency band (frequency band A) but separated from each other in the frequency band by a gap. In the inter-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 number of CCs that can be aggregated (e.g., up to 32 CCs may be aggregated in NR, or any other amount may be aggregated in other systems). The 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 a serving cell (e.g., in the case of 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 aggregated cells of a wireless device may be referred to as a primary cell (PCell), for example, if CA is configured. The PCell may be, for example, a serving cell that the radio initially connects to or accesses during or at RRC connection establishment, RRC connection re-establishment, and / or handover. The PCell may provide / configure NAS mobility information and security inputs to the wireless device. A wireless device may have different PCells. For the downlink, the carrier corresponding to the PCell is called the Downlink Primary CC (DL In the uplink, a carrier corresponding to a PCell may be referred to as an Uplink Primary CC (UL PCC). Other aggregated cells for a wireless device (e.g., associated with CCs other than DL PCC and UL PCC) may be referred to as Secondary Cells (SCells). An SCell may be configured, for example, after a PCell is configured for a wireless device. An SCell may be configured via an RRC connection reconfiguration procedure. In the downlink, a carrier corresponding to an SCell may be referred to as a Downlink Secondary CC (DL SCC). In the downlink, a carrier corresponding to an SCell may be referred to as a Downlink Secondary CC (UL SCC).

[0079] A configured SCell for a wireless device may be activated or deactivated based on, for example, traffic and channel conditions. Deactivation of a 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 use a bitmap (e.g., one bit per SCell) to indicate which SCells (e.g., in a subset of configured SCells) of the wireless device are activated or deactivated. A configured SCell may be deactivated, for example, based on (e.g., after or in response to) a timeout of an SCell deactivation timer (e.g., one SCell deactivation timer may be configured per SCell).

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

[0081] 10B shows an exemplary cell group. Aggregated 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, e.g., three downlink CCs: PCeL 1011 (e.g., DL PCC), SCeL 1012 (e.g., DL SCC), and SCeL 1013 (e.g., DL SCC). PUCCH group 1050 may include one or more downlink CCs, e.g., PUCCH The PUCCH group 1050 may include three downlink CCs: a SCell (or PSCell) 1051 (e.g., DL SCC), a SCell 1052 (e.g., DL SCC), and a 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., UL PCC), a SCell 1022 (e.g., UL SCC), and a SCell 1023 (e.g., UL SCC). One or more uplink CCs of the PUCCH group 1050 may be configured as a PUCCH The UCIs associated with downlink CCs of the PUCCH group 1050, 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 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 (e.g., 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 aggregated cell shown in Figure 10B is not divided into PUCCH group 1010 and PUCCH group 1050. PCell 1021 may be overloaded, for example, if UCIs 1031, 1032, 1033, 1071, 1072, and 1073 are transmitted / carried over PCell 1021. By splitting the transmission of UCI between PCell 1021 and PUCCH SCell (or PSCell) 1061, overloading may be prevented and / or reduced.

[0082] A PCell may comprise 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 / carried by 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 of a first downlink carrier may refer to the first physical cell ID of a cell including the first downlink carrier. Substantially the same / similar concept may be applied, for example, to carrier activation. Activation of a first carrier may refer to activation of a cell comprising the first carrier.

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

[0084] For the downlink, a base station may transmit / 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 transmit / transmit one or more RSs to a base station (e.g., DM-RS, PT-RS, and / or SRS). The PSS and SSS are transmitted / transmitted by a base station and may be 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 comprise a PSS, SSS, and PBCH. A base station may periodically transmit / transmit bursts of SS / PBCH blocks, which may be referred to as SSBs.

[0085] FIG. 11A shows an example of mapping one or more SS / PBCH blocks. A burst of SS / PBCH blocks may comprise one or more SS / PBCH blocks (e.g., four SS / PBCH blocks as shown in FIG. 11A). The burst may be transmitted periodically (e.g., every two frames, every 20 ms, or any other duration). The burst may be limited to a half-frame (e.g., the first half-frame having a 5 ms duration). Such parameters (e.g., the number of SS / PBCH blocks per burst, the periodicity of the burst, the position of the burst within the frame) may be configured based on at least one of the following: the carrier frequency of the cell in which the SS / PBCH block is 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, for example, use subcarrier spacing for the SS / PBCH block based on the monitored carrier frequency, unless the wireless network configures the wireless device to use different subcarrier spacing.

[0086] An SS / PBCH block may span one or more OFDM symbols in the time domain (e.g., four OFDM symbols as shown in FIG. 11A or any other number / quantity of symbols) and one or more subcarriers in the frequency domain (e.g., 240 consecutive subcarriers or any other number / quantity 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 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 a frequency location within the carrier. If the PSS is not found after a certain duration (e.g., 20 ms), for example, the wireless device 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, for example, the wireless device may determine the location of the SSS and PBCH, respectively, based on the known structure of the SS / PBCH block. The SS / PBCH block may be a cell-defined SS block (CD-SSB). The primary cell may be associated with 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 the location of a frame boundary of the cell, for example, based on the location of the SS / PBCH block. The SS / PBCH block may indicate that it was transmitted / transmitted according to a transmission pattern. The SS / PBCH block in the transmission pattern may be a known distance from the frame boundary (e.g., a predefined distance for a RAN configuration between one or more networks, one or more base stations, and one or more wireless devices).

[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 comprise / carry one or more DM-RS 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 comprise an MIB used to transmit / carry one or more parameters to the wireless device. The MIB may 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 that SIB1 is not present. The wireless device may be indicated a frequency based on, for example, the PBCH indicating that SIB1 is not present. The wireless device may search for an SS / PBCH block on the frequency to which the wireless device is indicated.

[0090] A wireless device may assume that one or more SS / PBCH blocks transmitted / transmitted using 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 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., within a half frame) may be transmitted / transmitted in the spatial direction (e.g., using different rays spanning the coverage area of ​​a cell). The first SS / PBCH block may be transmitted / transmitted in a first spatial direction using a first light ray, the second SS / PBCH block may be transmitted / transmitted in a second spatial direction using a second light ray, the third SS / PBCH block may be transmitted / transmitted in a third spatial direction using a third light ray, the fourth SS / PBCH block may be transmitted / transmitted in a fourth spatial direction using a fourth light ray, and so on.

[0091] For example, a base station may transmit multiple SS / PBCH blocks 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 at different frequency locations may be different or substantially the same.

[0092] The CSI-RS may be transmitted by a base station and used by a wireless device to obtain / acquire / determine channel state information (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 of the same / 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 transmit / transmit a CSI report to the base station (e.g., based on periodic CSI reporting, semi-persistent CSI reporting, and / or aperiodic CSI reporting). The base station may use feedback provided by the wireless device (e.g., estimated downlink channel conditions) to perform link adaptation.

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

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

[0095] The CSI-RS configuration may include, for example, one or more parameters indicating up to 32 antenna ports (or any other number of antenna ports). For example, if the downlink CSI-RS and CORESET are spatially QCLed and resource elements associated with the downlink CSI-RS are outside the physical resource block (PRB) configured for CORESET, the wireless device may be configured to use / use the same OFDM symbol for the downlink CSI-RS and CORESET. For example, if the downlink CSI-RS and SS / PBCH blocks are spatially QCLed and resource elements associated with the downlink CSI-RS are outside the PRB configured for the SS / PBCH block, the wireless device may be configured to use / use the same OFDM symbol for the downlink CSI-RS and 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 to one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). A base station may semi-statically configure a wireless device with 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 per wireless device (e.g., in the case of single-user MIMO). The DM-RS configuration may support up to four 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 position, DM-RS pattern, and / or scrambling sequence may be the same or different. The base station may, for example, transmit / transmit the downlink DM-RS and corresponding PDSCH using the same precoding matrix. The wireless device may use one or more downlink DM-RSs for coherent demodulation / channel estimation of the PDSCH.

[0097] A transmitter (e.g., a transmitter in a base station) 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 differ based on, for example, 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 / instantiated / identified / denoted as a precoding resource block group (PRG).

[0098] The PDSCH may include one or more layers. The 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). The downlink PT-RS is transmitted / transmitted by the base station and may be used by the wireless device, for example, for phase noise compensation. Whether a downlink PT-RS is present may depend on the RRC configuration. The presence and / or pattern of the downlink PT-RS may be configured on a wireless device-specific basis, for example, using a combination of RRC signaling and / or an association with one or more parameters used / employed for other purposes (e.g., modulation and coding scheme (MCS)) that may be indicated by DCI. The dynamic presence of the downlink PT-RS may be associated with one or more DCI parameters, including at least the MCS, if configured. A network (e.g., an NR network) may support multiple PT-RS densities defined in the time domain and / or the frequency domain. The frequency domain density (if configured / present) may be associated with at least one configuration of the scheduled bandwidth. The wireless device may assume the same precoding for DM-RS ports and PT-RS ports. The number / quantity of PT-RS ports may be less than the number / quantity of DM-RS ports in the scheduled resources. The downlink PT-RS may be configured / assigned / restricted at the 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. The base station may use the uplink DM-RS for coherent demodulation of one or more uplink physical channels. The 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. The base station may configure the 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 across 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, which the wireless device may use to schedule single-symbol DM-RS and / or dual-symbol DM-RS. A network (e.g., an NR network) may support a common DM-RS structure for the downlink and uplink (e.g., in the case of cyclic prefix orthogonal frequency division multiplexing (CP-OFDM)). The DM-RS positions, DM-RS patterns, and / or DM-RS scrambling sequences may be substantially the same or different.

[0100] The PUSCH may include one or more layers. A wireless device may transmit / transmit at least one symbol with a DM-RS present in 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 depending, for example, 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) by a combination of one or more parameters configured / adopted for other purposes (e.g., MCS) that may be indicated by RRC signaling and / or DCI. The dynamic presence of the uplink PT-RS may be associated with one or more DCI parameters, including at least MCS, if configured. A wireless network may support multiple uplink PT-RS densities defined in the time / frequency domain. The frequency-domain density (if configured / present) may be associated with at least one configuration of the scheduled bandwidth. The wireless device may assume the same precoding for the DM-RS and PT-RS ports. The number / quantity of PT-RS ports may be less than the number / quantity of DM-RS ports within the scheduled resources. The uplink PT-RS may be configured / allocated / restricted within the scheduled time / frequency duration of the wireless device.

[0101] One or more SRSs may be transmitted / transmitted by a wireless device to a base station, for example, for channel condition estimation to support uplink channel-dependent scheduling and / or link adaptation. The SRS transmitted / transmitted by the wireless device may enable the base station to estimate uplink channel conditions in one or more frequencies. A scheduler in the base station may use / be used to allocate one or more resource blocks for uplink PUSCH transmission for the wireless device. The base station may semi-statically configure the 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 one or more SRS resource sets (e.g., with the same / similar time-domain behavior, periodic, aperiodic, etc.) may be transmitted / transmitted at a certain point in time (e.g., simultaneously), for example, if higher layer parameters indicate light 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 an SRS resource, 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 / employed by a wireless device to select at least one of 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.The base station may semi-statically configure the wireless device with one or more SRS configuration parameters indicating at least one of the following: an SRS resource configuration identifier; the number of SRS ports; the time domain behavior of the SRS resource configuration (e.g., an indication of periodic, semi-persistent, or aperiodic SRS); slot, minislot, and / or subframe level periodicity; the offset of the periodic and / or aperiodic SRS resources; the number of OFDM symbols in the SRS resource; the starting OFDM symbol of the SRS resource; the SRS bandwidth; the frequency hopping bandwidth; the cyclic shift; and / or the SRS sequence ID.

[0102] Antenna ports may be determined / defined such that a channel on which a symbol on an antenna port is carried can be inferred from a channel on which another symbol on the same antenna port is carried. For example, when a first symbol and a second symbol are transmitted / transmitted on the same antenna port, a receiver can infer / determine a channel (e.g., fading gain, multipath delay, etc.) on which a second symbol on an antenna port is carried from a channel on which a first symbol on the antenna port is carried. For example, a first antenna port and a second antenna port may be referred to as quasi-colocated (QCLed) if one or more large-scale characteristics of a channel on which a first symbol on the first antenna port is carried can be inferred from a channel on which a second symbol on the second antenna port is carried. The one or more large-scale characteristics may include at least one of the following: delay spread; Doppler spread; Doppler shift; average gain; average delay; and / or spatial receive (Rx) parameters.

[0103] A channel using beamforming may require beam management. The 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 beam-formed reference signals. A wireless device may perform downlink beam measurement based on one or more downlink reference signals (e.g., CSI-RS) and generate a beam measurement report, for example. A wireless device may perform a downlink beam measurement procedure, for example, after an RRC connection with a base station is set up.

[0104] Figure 11B shows an example of mapping one or more CSI-RSs. The CSI-RSs may be mapped to the time domain and the frequency domain. Each rectangular block shown in Figure 11B may correspond to a resource block (RB) in the bandwidth of a cell. The base station may send / transmit one or more RRC messages including CSI-RS resource configuration parameters indicating one or more CSI-RSs. One or more of the parameters may be configured 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 resource element (RE) position within a subframe), a CSI-RS subframe configuration (e.g., subframe position, offset, and periodicity in a radio frame), a CSI-RS power parameter, a CSI-RS sequence parameter, a code division multiplexing (CDM) type parameter, a frequency density, a transmit comb, a quasi-colocation (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 light rays may be configured for a wireless device in a wireless device-specific configuration. Although three light rays (light ray #1, light ray #2, and light ray #3) are shown in FIG. 11B, more or fewer light rays may be configured. Light ray #1 may be assigned CSI-RS 1101, which may be transmitted / transmitted on one or more subcarriers in the RB of the first symbol. Light ray #2 may be assigned CSI-RS 1102, which may be transmitted / transmitted on one or more subcarriers in the RB of the second symbol. Light ray #3 may be assigned CSI-RS 1103, which may be transmitted / transmitted on one or more subcarriers in the RB of the third symbol. The base station may transmit another CSI-RS associated with a light ray for another wireless device using other subcarriers in the same RB (e.g., one not used to transmit / transmit CSI-RS 1101), for example, by using frequency division multiplexing (FDM). The light beams used for the wireless devices may be configured to use different symbols than those used by the light beams of other wireless devices, e.g., by using time domain multiplexing (TDM). Wireless devices may be served with light beams of orthogonal symbols (e.g., no overlapping symbols), e.g., 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 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 using an Rx ray determined based on the one or more TCI states. The wireless device may or may not have ray-enabled capability. If the wireless device has ray-enabled capability, the wireless device may determine a spatial domain filter for a transmit (Tx) ray, for example, based on the spatial domain filter of the corresponding Rx ray. The wireless device may perform an uplink ray selection procedure to determine a spatial domain filter for the Tx ray, for example, if the wireless device does not have ray support capability. The wireless device may perform the uplink ray selection procedure based on, for example, one or more sounding reference signal (SRS) resources configured to the wireless device by a base station. The base station may select and direct an uplink ray 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 a base station and an Rx beam of the wireless device. The Tx beam of the base station may transmit / carry downlink signals, and the Rx beam of the wireless device may receive downlink signals. The wireless device may transmit / transmit a beam measurement report, for example, 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 identification information (e.g., beam index, reference signal index, etc.), RSRP, precoding matrix indicator (PMI), channel quality indicator (CQI), and / or rank indicator (RI).

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

[0109] 12B illustrates an example of an uplink ray management procedure. One or more uplink ray management procedures (e.g., uplink ray 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 ray (e.g., to support selection of one or more Tx ray(s) of the wireless device and / or an Rx ray of the base station). The Tx ray(s) of the wireless device and the Rx ray(s) of the base station are shown as ellipses at the top and bottom of U1, respectively. Beamforming (e.g., at the wireless device) may include one or more ray sweeps, e.g., a Tx ray sweep from a set of rays (shown as ellipses rotated in a clockwise direction indicated by dashed arrows at the bottom of U1 and U3). Beamforming (e.g., at a base station) can include one or more ray sweeps, e.g., Rx ray sweeps from a set of rays (shown at the top of U1 and U2 as ellipses rotated in a counterclockwise direction indicated by dashed arrows). For example, if a wireless device (e.g., UE) uses fixed Tx rays, procedure U2 can be used to allow the base station to adjust its Rx rays. The wireless device and / or base station can perform procedure U2, e.g., using a smaller set of rays than the set of rays used in procedure P1, or using narrower rays than the rays used in procedure P1. Procedure U2 may also be referred to as ray refinement. The wireless device can perform procedure U3 to adjust its Tx rays, e.g., if the base station uses fixed Rx rays.

[0110] A wireless device may initiate / start / perform a beam fault recovery (BFR) procedure, for example, based on detecting a beam fault. The wireless device may send / transmit a BFR request (e.g., a preamble, UCI, SR, MAC CE, etc.) based on initiating a BFR procedure. The wireless device may detect a beam fault, for example, based on determining that the quality of the 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 timeout, etc.).

[0111] A wireless device may measure the quality of an optical pair link using one or more reference signals (RSs) comprising, 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 optical pair link may be based on one or more of a block error rate (BLER), an RSRP value, a signal-to-interference-and-noise ratio (SINR) value, an RSRQ value, and / or a CSI value measured on the RS resources. A base station may indicate that an RS resource is QCL'd with one or more DM-RSs of a channel (e.g., a control channel, a shared data channel, etc.). The RS resource and one or more DM-RSs of a channel may be QCL'd, for example, if channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameters, fading, etc.) from a transmission to the wireless device over the RS resource are similar or the same as channel characteristics from a transmission to the wireless device over 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 / initiate / 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 / initiate / perform a random access procedure from an RRC connected (e.g., RRC_CONNECTED) state. A wireless device may initiate / initiate / perform a random access procedure to request uplink resources (e.g., for uplink transmission of SR when there are no available PUCCH resources) and / or to acquire / obtain / determine uplink timing (e.g., when the uplink synchronization state is asynchronous). A wireless device may initiate / initiate / perform a random access procedure to request one or more system information blocks (SIBs) (e.g., other system information blocks such as SIB2, SIB3, etc.). A wireless device may initiate / initiate / perform a random access procedure for a beam failure recovery request. The network may initiate / start / perform a random access procedure, for example, for handover and / or to establish time alignment for SCell addition.

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

[0114] The configuration message 1310 may be transmitted / transmitted, for example, using one or more RRC messages. The one or more RRC messages may indicate one or more random access channel (RACH) parameters to the wireless device. The one or more RACH parameters may comprise at least one of: general parameters for one or more random access procedures (e.g., RACH-configGeneral); cell-specific parameters (e.g., RACH-ConfigCommon); and / or dedicated parameters (e.g., RACH-configDedicated). The base station may 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 the wireless device in an RRC connected (e.g., RRC_CONNECTED) state and / or an RRC inactive (e.g., RRC_INACTIVE) state. The wireless device may determine time-frequency resources and / or uplink transmit power for transmission of the first message (e.g., Msg 1 1311) and / or the third message (e.g., Msg 3 1313) based on one or more RACH parameters. The wireless device may determine receive timing and downlink channels for receiving the second message (e.g., Msg 2 1312) and the fourth message (e.g., Msg 4 1314) based on, for example, one or more RACH parameters.

[0115] The one or more RACH parameters provided / configured / included in the configuration message 1310 may indicate one or more physical RACH (PRACH) opportunities available for transmission of the first message (e.g., Msg 1 1311). The one or more PRACH opportunities may be predefined (e.g., by a network including one or more base stations). The one or more RACH parameters may indicate one or more available sets of one or more PRACH opportunities (e.g., prach-ConfigIndex). The one or more RACH parameters may indicate an association between (a) one or more PRACH opportunities and (b) one or more reference signals. The one or more RACH parameters may indicate an association between (a) one or more preambles and (b) one or more reference signals. The one or more reference signals may be SS / PBCH blocks and / or CSI-RS. The one or more RACH parameters may indicate the number / quantity of SS / PBCH blocks mapped to the PRACH opportunities and / or the number / quantity 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 transmit power of the first message (e.g., Msg 1 1311) and / or the third message (e.g., Msg 3 1313). The one or more RACH parameters may indicate a reference power for the preamble transmission (e.g., a received target power and / or an initial power for 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 ramp step; a power offset between SSB and CSI-RS; a power offset between the transmission of the first message (e.g., Msg 1 1311) and the third message (e.g., Msg 3 1313); and / or a power offset value between preamble groups. The one or more RACH parameters may indicate, for example, one or more thresholds based on which the wireless device may determine at least one reference signal (e.g., SSB and / or CSI-RS) and / or uplink carrier (e.g., a normal uplink (NUL) carrier and / or a supplemental uplink (SUL) carrier).

[0117] The first message (e.g., Msg 1 1311) may comprise 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., A group and / or B group). 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 a size of the third message (e.g., Msg 3 1313). The wireless device may measure the RSRP of one or more reference signals (e.g., SSB and / or CSI-RS) and determine at least one reference signal having an RSRP above an RSRP threshold (e.g., rsrp-ThresholdSSB and / or rsrp-ThresholdCSI-RS). 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, path loss measurements, RSRP measurements, and / or a third message (e.g., Msg 3 The base station may determine a preamble based on the size of the PRACH parameters (e.g., Msg 1 1313). The one or more RACH parameters may indicate a preamble format; a maximum number of preamble transmissions; and / or one or more thresholds for determining one or more preamble groups (e.g., A group and B group). 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 a preamble to be included in a first message (e.g., Msg 1 1311) based on, for example, the association, if configured. The first message (e.g., Msg 1 1311) may be transmitted / transmitted to the base station via one or more PRACH opportunities. The wireless device may use one or more reference signals (e.g., SSB and / or CSI-RS) for preamble selection and PRACH opportunity determination. One or more RACH parameters (eg, ra-ssb-OccasionMskIndex and / or ra-Occasion list) may indicate an association between a PRACH occasion and one or more reference signals.

[0119] The wireless device may perform a preamble retransmission, for example, if no response is received (e.g., after or in response to) a preamble transmission based on the preamble transmission (e.g., over a period of time, such as a monitoring window for monitoring the 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 set by the network. The wireless device may decide to retransmit / retransmit the preamble and 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 an incremental increase in the uplink transmit power for the retransmission. 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 ramp up the uplink transmit power. The wireless device may, for example, count the number / amount of preamble transmissions and / or retransmissions using a counter parameter (e.g., PREAMBLE_TRANSMISSION_COUNTER). The wireless device may determine that the random access procedure has completed unsuccessfully, for example, if the amount / number of preamble transmissions exceeds a threshold set by one or more RACH parameters (e.g., preambleTransMax) without receiving a successful response (e.g., RAR).

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

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

[0122] The fourth message (e.g., Msg 4 1314) may be received, for example, based on (e.g., after or in response to) the transmission / transmission of the third message (e.g., Msg 3 1313). The base station may address the radio on a PDCCH using the C-RNTI, for example, if the C-RNTI was included in the third message (e.g., Msg 3 1313) (e.g., the base station may transmit a PDCCH to the wireless device). The random access procedure may be determined to have completed 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). For example, if the TC RNTI is included in the third message (e.g., Msg 3 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), the wireless device may receive a fourth message (e.g., Msg 4 1314) using the DL-SCH associated with the TC RNTI. For example, if the MAC PDU is successfully decoded and the MAC PDU includes a wireless device contention resolution identity MAC CE that matches or otherwise corresponds to the CCCH SDU sent / transmitted in the third message (e.g., Msg 3 1313), the wireless device may determine that contention resolution was successful and / or the wireless device may determine that the random access procedure was successfully completed.

[0123] The wireless device may be configured with an SUL carrier and / or a NUL carrier. Initial access (e.g., random access) may be supported over an uplink carrier. The base station may configure the wireless device with multiple RACH configurations (e.g., two separate RACH configurations, one for the SUL carrier and the other for the NUL carrier). For random access in a cell configured with an SUL carrier, the network may indicate which carrier to use (NUL or SUL). 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., Msg 1 1311) and / or the third message (e.g., Msg 3 1313)) may remain on or be performed over the selected carrier. The wireless device may select the first message (e.g., Msg 1 1311) and / or the third message (e.g., Msg 3 1313) during the random access procedure (e.g., Msg 1 1312). The wireless device may switch uplink carriers for the first message (e.g., Msg 1 1311) and / or the third message (e.g., Msg 3 1313) based on, for example, a channel clearance assessment (e.g., listen-before-talk).

[0124] 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, the base station may send / transmit a configuration message 1320 to the 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., Msg 1 1321) and a second message (e.g., Msg 2 1322). The first message (e.g., Msg 1 1321) may be a The second message (e.g., Msg 1 1321) and the third message (e.g., Msg 2 1322) may be similar in some respects to the first message (e.g., Msg 1 1311) and the second message (e.g., Msg 2 1312), respectively. A two-step contention-free random access procedure may not include messages similar to the third message (e.g., Msg 3 1313) and / or the fourth message (e.g., Msg 4 1314).

[0125] 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 for the first message (e.g., Msg 1 1321). The wireless device may receive an indication from the base station via PDCCH and / or RRC indicating the preamble (e.g., ra-PreambleIndex).

[0126] The wireless device may start a time window (e.g., ra-ResponseWindow) to monitor the PDCCH for RAR, for example, based on transmitting / transmitting a preamble (e.g., after or in response to the transmission / transmission). 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 within 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) over the search space. During a two-step (e.g., contention-free) random access procedure, the wireless device may determine that the random access procedure is successful, for example, based on (e.g., after or in response to) sending / transmitting a first message (e.g., Msg 1 1321) and receiving a corresponding second message (e.g., Msg 2 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 comprising a preamble identifier corresponding to a preamble sent / transmitted by the wireless device and / or if the RAR comprises a MAC sub-PDU comprising the preamble identifier. The wireless device may determine this response as an indication of acknowledgment to the SI request.

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

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

[0129] A wireless device may initiate / 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 initiate / 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, etc.); 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 or unlicensed); and / or any other suitable factor.

[0130] The wireless device may determine radio resources and / or uplink transmit power for the preamble 1341 and / or transport block 1342 based on two-stage RACH parameters included in the configuration message 1330 (e.g., included in the first message (e.g., Msg A 1331)). The RACH parameters may indicate MCS, time-frequency resources, and / or power control for the preamble 1341 and / or transport block 1342. The time-frequency resources (e.g., PRACH) for transmission of the preamble 1341 and the time-frequency resources (e.g., PUSCH) for transmission of the transport block 1342 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).

[0131] 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)). A wireless device may transmit / 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., a C-RNTI or TC-RNTI). The wireless device may, for example, determine whether the preamble identifier in the second message (e.g., Msg B 1332) is a preamble identifier and / or a second message (e.g., Msg B 1332) transmitted / transmitted by the wireless device. If the identifier of the wireless device in the first message (e.g., Msg A 1332) corresponds to or matches the identifier of the wireless device in the second message (e.g., Msg A 1331), it can be determined that the two-step random access procedure has been successfully completed (e.g., transport block 1342).

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

[0133] 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 appropriate 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 and received via the PDCCH may be referred to as downlink control information (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.

[0134] The base station may append one or more cyclic redundancy check (CRC) parity bits to the DCI, for example, to facilitate detection of transmission errors. The base station may scramble the CRC parity bits with an identifier of the wireless device (or an identifier of a group of wireless devices), for example, if the DCI is intended for a 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.

[0135] 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 the triggering of a dynamically scheduled unicast transmission and / or a PDCCH ordered random access. A DCI having CRC parity bits scrambled with the Temporary Cell RNTI (TC-RNTI) may indicate contention resolution (e.g., Msg 3 similar to Msg 3 1313 shown in FIG. 13A). Other RNTIs configured for the wireless device by the base station may include a Configured Scheduling RNTI (CS RNTI), a Transmit Power Control PUCCH RNTI (TPC PUCCH-RNTI), a Transmit Power Control PUSCH RNTI (TPC-PUSCH-RNTI), a Transmit Power Control SRS RNTI (TPC-SRS-RNTI), an Interruption RNTI (INT-RNTI), a Slot Format Indication RNTI (SFI-RNTI), a Semi-Persistent CSI RNTI (SP-CSI-RNTI), a Modulation and Coding Scheme Cell RNTI (MCS-C RNTI), etc.

[0136] 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., with a compact DCI payload). DCI format 0_1 ​​may be used for scheduling a PUSCH in a cell (e.g., with 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., with a compact DCI payload). DCI format 1_1 may be used for scheduling a PDSCH in a cell (e.g., with 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 can be used to signal / indicate physical resource blocks and / or OFDM symbols to a group of wireless devices, which can assume that no transmission to the group of wireless devices is intended. DCI format 2_2 can be used for transmission of transmit power control (TPC) commands for PUCCH or PUSCH. DCI format 2_3 can be used for transmission of 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 may share the same DCI size.

[0137] The base station may process the DCI with channel coding (e.g., polar 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 to resource elements used and / or configured for the PDCCH. The base station may transmit / transmit the DCI via the 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 (called an aggregation level) may be 1, 2, 4, 8, 16, and / or any other suitable number. A CCE may include several (e.g., 6) resource element groups (REGs). A REG may comprise a resource block within an OFDM symbol. The mapping of the coded and modulated DCI to resource elements may be based on a mapping of CCEs and REGs (e.g., a CCE-to-REG mapping).

[0138] FIG. 14A shows an example of a CORESET configuration. The CORESET configuration may be for a band portion or any other frequency band. A base station may transmit / transmit DCI via a PDCCH on one or more control resource sets (CORESETs). A CORESET may comprise time-frequency resources in which a wireless device attempts / attempts to decode the DCI using one or more search spaces. A base station may configure the size and location of the CORESETs in the time-frequency domain. A first CORESET 1401 and a 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. A third CORESET 1403 may occur or be configured / set at the third symbol in a slot. A 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.

[0139] FIG. 14B shows an example of CCE-to-REG mapping. CCE-to-REG mapping may be performed for DCI transmission with 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 perform different or the same CCE-to-REG mapping for different CORESETs. A CORESET may be associated with a CCE-REG mapping (e.g., by RRC configuration). A CORESET may be configured with an antenna port QCL parameter. The antenna port QCL parameter may indicate QCL information of a DM-RS for PDCCH reception via a CORESET.

[0140] The base station may send / transmit one or more RRC messages to the wireless device comprising configuration parameters of one or more CORESETs and one or more search space sets. The configuration parameters may indicate an association between the search space set and the CORESET. The search space set may comprise a set of PDCCH candidates formed by CCEs (e.g., at a given aggregation level). The configuration parameters may indicate at least one of: the number of PDCCH candidates to be monitored per aggregation level; a PDCCH monitoring periodicity and a PDCCH monitoring pattern; one or more DCI formats to be monitored by the wireless device; and / or whether the search space set is a common search space set or a wireless device-specific search space set (e.g., a UE-specific search space set). The set of CCEs in the common search space set may be predefined and known to the wireless device. The set of CCEs in 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).

[0141] As shown in FIG. 14B , the wireless device may determine time-frequency resources for the CORESET based on one or more RRC messages. The wireless device may determine a CCE-to-REG mapping (e.g., interleaved or non-interleaved, and / or mapping parameters) for the CORESET based on, for example, configuration parameters of the CORESET. The wireless device may determine the number of search space sets (e.g., up to 10) configured for the CORESET based on, for example, 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 having possible (or configured) PDCCH locations, possible (or configured) PDCCH formats (e.g., the number of CCEs, the number of PDCCH candidates in a common search space, and / or the 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 that the DCI is valid for the wireless device based on (e.g., after or in response to) a CRC check (e.g., scrambling bits for 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, etc.).

[0142] The wireless device may send / transmit uplink control signaling (e.g., UCI) to the base station. The uplink control signaling may comprise a HARQ acknowledgment for a received DL-SCH transport block. The wireless device may send / transmit the HARQ acknowledgment, for example, based on (e.g., after or in response to) receiving the DL-SCH transport block. The uplink control signaling may comprise CSI indicating channel quality of a physical downlink channel. The wireless device may send / transmit the CSI to the base station. The base station may determine transmit format parameters (e.g., including multi-antenna and beamforming schemes) for downlink transmission based on the received CSI. The uplink control signaling may include a scheduling request (SR). The wireless device may send / transmit the SR indicating that uplink data is available for transmission to the base station. The wireless device may send / transmit UCI (e.g., a HARQ acknowledgement (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.

[0143] There may be multiple PUCCH formats (e.g., five PUCCH formats). A wireless device may determine a PUCCH format based, for example, on the size of the UCI (e.g., the number / amount of uplink symbols for UCI transmission and the number of UCI bits). PUCCH format 0 may have a length of one or two OFDM symbols and may comprise two or fewer bits. A wireless device may transmit / transmit UCI over PUCCH resources using PUCCH format 0, for example, if the transmission is on / via one or two symbols and the number / amount of HARQ-ACK information bits with positive or negative SR (HARQ-ACK / SR bits) is one or two. PUCCH format 1 may occupy several 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 is on / via four or more symbols and the number of HARQ-ACK / SR bits is one or two. PUCCH format 2 may occupy one or two OFDM symbols and comprise three or more bits. A wireless device may use PUCCH format 2, for example, when a transmission is over / via one or two symbols and the number / amount of UCI bits is two or more. PUCCH format 3 may occupy several OFDM symbols (e.g., between 4 and 14 OFDM symbols) and comprise three or more bits. A wireless device may use PUCCH format 3, for example, when a transmission is four or more symbols, the number / amount of UCI bits is two or more, and the PUCCH resource does not comprise an orthogonal cover code (OCC). PUCCH format 4 may occupy several OFDM symbols (e.g., between 4 and 14 OFDM symbols) and comprise three or more bits. A wireless device may use PUCCH format 4, for example, when a transmission is four or more symbols, the number / amount of UCI bits is two or more, and the PUCCH resource comprises an OCC.

[0144] A base station may transmit / transmit configuration parameters for 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 number of sets in other systems) may be configured in 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 the number (e.g., maximum number) of UCI information bits that the wireless device may transmit / transmit using one of the multiple PUCCH resources in the PUCCH resource set. If configured with multiple PUCCH resource sets, the wireless device may select one of the multiple PUCCH resource sets based on, for example, the total bit length of the UCI information bits (e.g., HARQ-ACK, SR, and / or CSI). For example, if the wireless device is configured with multiple PUCCH resource sets, the wireless device may select the first PUCCH resource set with 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 configured 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 the first configured value and less than or equal to a second configured 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 the second configured value and less than or equal to a third value (e.g., 1406, 1706, or any other number of bits).

[0145] 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 received on / via a PDCCH (e.g., with DCI of DCI format 1_0 or 1_1). An n-bit (e.g., 3-bit) PUCCH resource indicator in the DCI may indicate one of multiple (e.g., 8) PUCCH resources in the PUCCH resource set. Based on, for example, the PUCCH resource indicator, the wireless device may transmit / transmit UCI (HARQ-ACK, CSI, and / or SR) using the PUCCH resource indicated by the PUCCH resource indicator in the DCI.

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

[0147] The base station 1504 can 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 transmissions may be separated from the uplink transmissions using, for example, various duplexing schemes (e.g., FDD, TDD, and / or some combination of duplexing techniques).

[0148] For the downlink, data to be 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 to be transmitted from the wireless device 1502 to the base station 1504 may be provided / forwarded / transmitted to the processing system 1518 of the wireless device 1502. The processing system 1508 and the processing system 1518 may implement Layer 3 and Layer 2 OSI functions to process the data for transmission. Layer 2 may include, for example, the SDAP layer, PDCP layer, RLC layer, and MAC layer described with respect to FIGS. 2A, 2B, 3, and 4A. Layer 3 may include, for example, the RRC layer described with respect to FIG. 2B.

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

[0150] 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 comprise 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 comprise one or more antenna panels. The receive processing system 1512 and the receive processing system 1522 may implement Layer 1 OSI functions. Layer 1 may include, for example, the PHY layer described in connection with FIGS. 2A, 2B, 3, and 4A. For receive processing, the PHY layer may perform, for example, error detection, forward error correction decoding, deinterleaving, demapping of transport channels to physical channels, demodulation of physical channels, MIMO or multi-antenna processing, etc.

[0151] The base station 1504 may be equipped with multiple antennas (e.g., multiple antenna panels, multiple TRPs, etc.). The wireless device 1502 may be equipped with 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.

[0152] 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, as well as other functions of computers, processors, memories, and / or other peripherals in general). 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 stores 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 can be executed to perform one or more of their respective functions.

[0153] Processing system 1508 and / or processing system 1518 may comprise 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.

[0154] The processing system 1508 may be connected to one or more peripherals 1516. The processing system 1518 may be connected to one or more peripherals 1526. The one or more peripherals 1516 and the one or more peripherals 1526 may comprise software and / or hardware that provides functionality and / or features such as, for example, 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 an automobile), 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, etc.). The processing system 1508 and / or the processing system 1518 may receive input data (e.g., user input data) from the one or more peripherals 1516 and / or the one or more peripherals and / or provide output data (e.g., user output data) to the one or more peripherals 1526. A processing system 1518 in the wireless device 1502 may be configured to receive power from a power source and / or distribute this power to other components in 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.

[0155] 15B illustrates 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 capable of executing instructions stored in random access memory (RAM) 1533, removable media 1534 (e.g., a universal serial bus (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. The computing device 1530 may also include a security processor (not shown) that can execute instructions of one or more computer programs to monitor processes running on the processor 1531 and any processes that request access to any hardware and / or software components of the 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.). The computing device 1530 may include one or more output devices such as a display 1536 (e.g., a screen, display device, monitor, television, etc.) and one or more output device controllers 1537, such as a video processor. There may also be one or more user input devices 1538, such as a remote control, keyboard, mouse, touch screen, microphone, etc.The computing device 1530 may include one or more network interfaces, such as a network interface 1539, which may be a wired interface, a wireless interface, or a combination thereof. The network interface 1539 may provide an interface for the computing device 1530 to communicate 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 global positioning system (GPS) microprocessor 1541, which may be configured to receive and process global positioning signals and, with possible assistance from an external server and antenna, determine the geographic location of the computing device 1530.

[0156] While the example of FIG. 15B may be a hardware configuration, the depicted components may also be implemented as software. Changes can be made to add, remove, combine, divide, etc., components of computing device 1530 as desired. Furthermore, components may be implemented using basic computing devices and components, and the same components (e.g., processor 1531, ROM storage 1532, display 1536, etc.) can be used to implement any of the other computing devices and components described herein. For example, the various components described herein can 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 or coexist on a common physical platform (e.g., a requesting entity may be a separate software process and program from subordinate entities, both of which may be executed as software on a common computing device).

[0157] FIG. 16A shows an example structure for uplink transmission. Processing of a baseband signal representing a physical uplink shared channel may comprise / perform one or more functions. The one or more functions may include at least one of: scrambling; modulating scrambled bits to generate complex-valued symbols; mapping complex-valued modulation symbols to one or more transmission layers; transform precoding to generate complex-valued symbols; precoding the complex-valued symbols; mapping the precoded complex-valued symbols to resource elements; generating a complex-valued time-domain single-carrier frequency division multiple access (SC-FDMA), CP-OFDM signal for an antenna port, or any other signal. 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.

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

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

[0160] 16D shows an exemplary structure for modulating and upconverting 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 / used, for example, before transmission.

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

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

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

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

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

[0166] A MAC PDU may contain one or more MAC subPDUs. A MAC subPDU of the one or more MAC subPDUs may include a MAC subheader only (including padding); a MAC subheader and a MAC SDU; a MAC subheader and a MAC CE; and / or a MAC subheader and padding. A MAC SDU may be of variable size. A MAC subheader may correspond to a MAC SDU, a MAC CE, or padding.

[0167] The MAC subheader may include an R field having a length of 1 bit; an F field having a length of 1 bit; an LCID field having a length of multiple bits; and / or It may contain an L field of multiple bits in length if it supports SDUs, variable size MAC CEs, or padding.

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

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

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

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

[0172] A wireless device (e.g., a MAC entity of the wireless device) can transmit / transmit one or more MAC CEs to a base station (e.g., a MAC entity of the base station). Figure 20 shows exemplary LCID values ​​that can be associated with one or more MAC CEs. The LCID values ​​can be associated with uplink channels such as UL-SCH. The one or more MAC CEs can include a short buffer status report (BSR) MAC CE, a long BSR MAC CE, a long BSR MAC CE, a short Buffer Status Report (BSR) MAC CE, a long BSR MAC CE, a long Buffer Status Report (BSR) ... The MAC subheader may include at least one of a MAC CE, a C-RNTI MAC CE, a Configuration Authorization Confirmation MAC CE, a single-entry Power Headroom Report (PHR) MAC CE, a multi-entry PHR MAC CE, a short truncated BSR, and / or a long truncated BSR. The MAC CE may be associated with (e.g., may correspond to) an LCID in a MAC subheader corresponding to the MAC CE. Different MAC CEs may correspond to different LCIDs in a MAC subheader corresponding to the MAC CE. An LCID having an index value of "111011" in a MAC subheader may indicate that the MAC CE associated with the MAC subheader is, for example, a short truncated command MAC CE for a MAC CE associated with the uplink.

[0173] As in carrier aggregation (CA), two or more component carriers (CCs) may be aggregated. A wireless device may simultaneously receive and / or transmit data over one or more CCs, depending, for example, on the capabilities of the wireless device (e.g., using CA techniques). A wireless device may support CA for contiguous and / or non-contiguous CCs. CCs may be organized into cells. CCs may be organized into one PCell and one or more SCells.

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

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

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

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

[0178] FIG. 21B shows an exemplary SCell activation / deactivation MAC of 4 octets. 19 )。 The second MAC PDU subheader including the second LCID (e.g., "111001" shown in FIG. 19 ) may indicate / identify a 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 comprise a third number / quantity C field (e.g., 31 or any other number / quantity) and a fourth number / quantity R field (e.g., 1 or any other number / quantity).

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

[0180] The base station may send / transmit one or more messages including an SCell timer (e.g., sCellDeactivationTimer) to the wireless device. The wireless device may deactivate the SCell, for example, based on (e.g., after or in response to) expiration of the SCell timer. An SCell configured with an uplink control channel (e.g., a PUCCH SCell) may not be configured with an SCell timer. Other SCells (e.g., except for SCells configured with an uplink control channel) may run SCell timers.

[0181] For example, if the wireless device receives an SCell activation / deactivation MAC CE that activates the SCell, the wireless device may activate the SCell. The wireless device may perform one or more first operations, for example, based on (e.g., after or in response to) the activation of the SCell. The one or more first operations may include at least one of: SRS transmission on / via the SCell; CQI / PMI / RI / CSI-RS resource indicator (CRI) reporting for the SCell; PDCCH monitoring on / via the SCell; PDCCH monitoring of the SCell (e.g., on / via a PCell or another SCell); and / or PUCCH transmission on / via the SCell.

[0182] The wireless device may, for example, start or restart a first SCell timer (e.g., sCellDeactivationTimer) associated with the SCell based on (e.g., after or in response to) activation of the SCell. The wireless device may, for example, start or restart the first SCell timer in a slot in which an SCell activation / deactivation MAC CE activating the SCell was received. The wireless device may, for example, (re)initialize one or more suspended configured uplink grants of a configuration grant (e.g., configuration grant type 1) associated with the SCell according to a stored configuration based on (e.g., after or in response to) activation of the SCell. The wireless device may, for example, trigger a PHR based on (e.g., after or in response to) activation of the SCell.

[0183] The wireless device may deactivate an activated SCell, for example, when the wireless device receives an SCell activation / deactivation MAC CE. The wireless device may deactivate an activated SCell, for example, when a first SCell timer (e.g., sCellDeactivationTimer) associated with the activated SCell expires. The wireless device may, for example, stop the first SCell timer associated with the activated SCell based on (e.g., after or in response to) the deactivation of the activated SCell. The wireless device may, for example, clear one or more configured downlink assignments and / or one or more configured uplink grants of a configured grant (e.g., configured uplink grant type 2) associated with the activated SCell based on (e.g., after or in response to) the deactivation of the activated SCell. For example, based on (e.g., after or in response to) deactivation of an activated SCel, the wireless device may suspend one or more configured uplink grants (e.g., configured uplink grant type 1) associated with the activated SCel and / or flush a HARQ buffer associated with the activated SCel.

[0184] The wireless device may not perform one or more second operations, for example, if the SCell is deactivated. The one or more second operations may include at least one of: sending / transmitting SRS on / via the SCell; reporting CQI / PMI / RI / CRI for the SCell; sending / transmitting UL-SCH on / via the SCell; sending / transmitting RACH on / via the SCell; monitoring at least one first PDCCH on / via the SCell; monitoring at least one second PDCCH of the SCell (e.g., on / via a PCell or another SCell); and / or sending / transmitting PUCCH on / via the SCell.

[0185] For example, if at least one first PDCCH of 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. The wireless device may, for example, restart a first SCell timer (e.g., sCellDeactivationTimer) associated with the activated SCell if at least one second PDCCH on / via a serving cell (e.g., a PCell or SCell configured in a PUCCH, i.e., a PUCCH SCell) scheduling the activated SCell indicates an uplink grant or a downlink assignment for the activated SCell. The wireless device may, for example, abort an ongoing random access procedure on the SCell if the SCell is deactivated and if there is an ongoing random access procedure on the SCell.

[0186] A base station may configure a wireless device with an uplink (UL) band part (BWP) and / or a downlink (DL) BWP, for example, to enable bandwidth adaptation (BA) on a PCell. The base station may further configure the wireless device with at least a DL BWP (e.g., there may be no UL BWP on the UL) to enable BA on an SCell, for example, if carrier aggregation is configured for the wireless device. For a PCell, the initial active BWP may be a first BWP used for initial access. For an SCell, the first active BWP may be a second BWP that the wireless device is configured to operate on the SCell when the SCell is activated.

[0187] A base station and / or wireless device may independently switch between DL BWP and / or UL BWP, e.g., in a paired spectrum (e.g., FDD), and may simultaneously switch between DL BWP and UL BWP, e.g., in an unpaired spectrum (e.g., TDD).

[0188] The base station and / or wireless device can switch BWPs between configured BWPs, for example, based on a DCI or a BWP inactivity timer. The base station and / or wireless device may switch an active BWP to a default BWP based on (e.g., upon or upon) expiration of a BWP inactivity timer associated with the serving cell, for example, if a BWP inactivity timer is configured for the serving cell. The default BWP may be configured by the network (e.g., via one or more RRC messages).

[0189] One UL BWP and one DL BWP for each uplink carrier may be active at a time in an active serving cell, for example, when configured with BA, in the case of an FDD system. One DL / UL BWP pair may be active at a time in an active serving cell, for example, in the case of a TDD system. Operating with one UL BWP and one DL BWP (or one DL / UL pair) may improve battery consumption efficiency of a wireless device. BWPs (e.g., configured for and / or operable by a wireless device) other than one active UL BWP and one active DL BWP may be deactivated. The wireless device may not monitor the PDCCH on / via the deactivated BWPs and / or may not transmit / transmit on / via the deactivated BWPs, PUCCH, PRACH, and / or UL-SCH. A serving cell may be configured with up to a first number / quantity (e.g., four or any other number / quantity) of BWPs. For example, for an activated serving cell, there may be one active BWP at any given time.

[0190] BWP switching of the serving cell can be used to activate an inactive BWP and / or deactivate an active BWP at once. BWP switching can be controlled by a PDCCH indicating a downlink assignment and / or an uplink grant. BWP switching can also be controlled by a BWP inactivity timer (e.g., bwp-InactivityTimer). BWP switching can also be controlled by a base station and / or a wireless device (e.g., a MAC entity of the base station and / or wireless device), for example, based on (e.g., after or in response to) the initiation of a random access procedure. A BWP can be initially active, for example, after the addition of an SpCell or the activation of an SCell, without receiving a PDCCH indicating a downlink assignment or an uplink grant. The active BWP of the serving cell can also be indicated by an RRC message and / or a PDCCH. A DL BWP can be paired with a UL BWP, and BWP switching can be common to both UL and DL, for example, in the case of unpaired spectrum.

[0191] FIG. 22 shows an example of BWP management. BWP management may include BWP switching (e.g., a switch of an SCell). The wireless device may receive one or more RRC messages 2210 including parameters of the SCell and one or more BWP configurations associated with the SCell. The one or more RRC messages 2210 may include at least one of an RRC connection reconfiguration message (e.g., RRCReconfiguration); an RRC connection re-establishment message (e.g., RRCRestablishment); and / or an RRC connection setup message (e.g., RRCSetup). Of the one or more BWPs, at least one BWP may be configured as a first active BWP (e.g., BWP1 shown in FIG. 22), and one BWP may be configured as a default BWP (e.g., BWP0 shown in FIG. 22). The wireless device may receive an activation indication 2220 (e.g., a command, a MAC CE) to activate the SCell (e.g., during the nth slot). The wireless device may start an SCell deactivation timer (e.g., sCellDeactivationTimer), start CSI-related operations for the SCell, and / or start CSI-related operations for the first active BWP for the SCell. The wireless device may start monitoring the PDCCH on / via BWP1, for example, based on (e.g., after or in response to) activation of the SCell.

[0192] The wireless device may, for example, start or restart a BWP inactivity timer (e.g., bwp-InactivityTimer) (e.g., during the mth slot) based on (e.g., after or in response to) receiving DCI 2230 indicating a DL allocation in BWP1. The wireless device may, for example, switch to a default BWP (e.g., BWP 0) as the active BWP when the BWP inactivity timer expires (e.g., during the sth slot). The wireless device may deactivate the SCell and / or stop the BWP inactivity timer when, for example, the sCellDeactivationTimer expires.

[0193] Using the BWP inactivity timer can further reduce power consumption of a wireless device, for example, when the wireless device is configured with multiple cells and / or one or more cells with a wide bandwidth (e.g., 1 GHz). The wireless device can transmit / transmit or receive only via a narrow-bandwidth BWP (e.g., 5 MHz) on a PCell or SCell, for example, when there is no activity on the active BWP. The wireless device can determine expiration of the BWP inactivity timer (e.g., during the sth slot). The wireless device can, for example, switch an active BWP (e.g., BWP1) to a default BWP (e.g., BWP0) based on (e.g., after or in response to) expiration of the BWP inactivity timer.

[0194] A wireless device (e.g., a MAC entity of the wireless device) may apply normal operations to an active BWP for an activated serving cell configured with the BWP. The normal operations may include at least one of transmitting on / via the UL-SCH, transmitting on / via the RACH, monitoring the PDCCH, transmitting / via the PUCCH, and / or receiving the DL-SCH, and / or (re)initializing pending configured uplink grants (e.g., configuration grant type 1) according to a stored configuration, if any.

[0195] A wireless device (e.g., a MAC entity of the wireless device) may not perform one or more operations with / via an inactive BWP, for example, for each activated serving cell configured with a BWP. The one or more operations not performed by the wireless device (e.g., a MAC entity of the wireless device) may include at least one of: transmitting on / via an UL-SCH; transmitting on / via an RACH; monitoring a PDCCH; transmitting / transmitting a PUCCH; transmitting / transmitting an SRS and receiving a DL-SCH; clearing any configured downlink assignment and / or configured uplink grant of a configuration grant (e.g., configuration grant type 2); and / or suspending any configured uplink grant of a configuration grant (e.g., configured type 1).

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

[0197] The wireless device may be provided with a default DL BWP among the configured DL BWPs, for example, for the primary cell and / or the secondary cell, by a higher layer parameter (e.g., default-DL-BWP). The default DL BWP may be an initial active DL BWP, for example, if the wireless device is not provided with a default DL BWP by a higher layer parameter (e.g., default-DL-BWP).

[0198] The wireless device may be provided with a timer value for the primary cell by a higher layer parameter (e.g., bwp-InactivityTimer). The wireless device may increment the configured timer (if operational), for example, every 1 millisecond interval for frequency range 1, every 0.5 millisecond interval for frequency range 2, or any other interval for another frequency range. The wireless device may increment the configured timer, for example, if the wireless device does not detect DCI format 1_1 for paired spectrum operation, or if the wireless device does not detect DCI format 1_1 or DCI format 0_1 ​​for unpaired spectrum operation during an interval. The wireless device may receive a deactivation indication 2240 (e.g., a command, a MAC CE) to deactivate one or more SCells. The wireless device may, for example, stop the BWP inactivity timer and / or deactivate one or more SCells based on (e.g., after or in response to) receiving the deactivation indication 2240.

[0199] The wireless device procedure on the secondary cell may be the same as or similar to the wireless device procedure on the primary cell, for example, if the wireless device is configured for the secondary cell with higher layer parameters (e.g., default-DL-BWP) indicating a default DL BWP among the configured DL BWPs and / or the wireless device is configured with higher layer parameters (e.g., bwp-InactivityTimer) indicating a timer value. The wireless device may perform the same or similar procedure using, for example, the timer value of the secondary cell and / or the default DL BWP of the secondary cell. For example, if the wireless device is configured with a first active DL BWP by higher layer parameters (e.g., Active-BWP-DL-SCell) and a first active UL BWP on a secondary cell or carrier by higher layer parameters (e.g., Active-BWP-UL-SCell), the wireless device may use the indicated DL BWP and indicated UL BWP on the secondary cell as the first active DL BWP and first active UL BWP on the secondary cell or carrier, respectively.

[0200] Figure 23 shows an example message comprising cell configuration parameters. The message may include an RRC message. The message may comprise a serving cell configuration information element. The configuration parameters may include at least one of TDD configuration parameters (e.g., tdd-UL-DL-ConfigurationDedicated, TDD-UL-DL-ConfigDedicated), an initial BWP ID, multiple DL BWPs, multiple UL BWPs, a first active BWP, a BWP inactivity timer, an SCell inactivity timer, and / or a cross-carrier scheduling configuration information element (e.g., CrossCarrierSchedulingConfig). The message may include one or more algorithms (e.g., computer code or subroutines) for determining the ServingCellConfig information element and / or the CrossCarrierSchedulingConfig information element. The information element ServingCellConfig (e.g., ServingCellConfigIE) may be used to configure (e.g., add or modify) a wireless device with a serving cell. The serving cell may be an SpCell and / or an SCell of an MCG or SCG. The configuration parameters may be wireless device-specific and / or cell-specific. Reconfiguration between PUCCH and PUCCHless SCell may be supported, for example, using SCell release and add. For example, if cross-carrier scheduling is used in a cell, the information element CrossCarrierSchedulingConfig may be used to specify the configuration parameters. The configuration parameters may include one or more PDCCH configuration parameters of the first cell and / or one or more PDCCH configuration parameters of the second cell. The PDCCH configuration parameters may comprise one or more of a control resource set, a search space (configured in the SearchSpace IE), a downlink preemption indication, a PUSCH power control parameter, a PUCCH power control parameter, and / or an SRS power control parameter.

[0201] Figure 24 shows an example of a message comprising configuration parameters for a search space. The message may include an RRC message. The search space information element (e.g., SearchSpace IE) may define / indicate how and / or where to search for PDCCH candidates. Each search space may be associated with at least one ControlResourceSet. For scheduled cells using cross-carrier scheduling, except for nrofCandidates, the optional fields shown in Figure 24 may not be present. The one or more search space configuration parameters of a 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 / quantity of candidates at aggregation level 2445 (nrofCandidates), and / or an SS type indicating a common SS type or a wireless device-specific (e.g., UE-specific) SS type (searchSpaceType). The monitoring slot periodicity and offset parameters may indicate a slot (e.g., in a radio frame) and / or 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 / indicate a control resource set in which the SS may be located. The searchSpaceId 2420 may identify / indicate a search space (e.g., a set of PDCCH candidates for the wireless device to monitor). Each search space may comprise a set of control elements at different aggregation levels that may determine the number / quantity of candidates to decode at one or more aggregation levels.The condition SearchSpaceId equal to 0 may identify / indicate searchSpaceZero, which may be configured via PBCH (MIB) or ServingCellConfigCommon and may not be used in the SearchSpace IE. searchSpaceId may be unique among BWPs of a serving cell. Search spaces with the same searchSpaceId in a scheduled cell and a scheduling cell (e.g., for cross-carrier scheduling) may be linked together. The wireless device may apply a search space to a scheduled cell, for example, when a DL BWP is active in which linked search spaces are configured in both the scheduling cell and the scheduled cell.

[0202] Figure 25 shows an example of a message including configuration parameters of a control resource set (CORESET). This message may comprise an RRC message. A base station may transmit / transmit one or more configuration parameters of the CORESET to a wireless device. The information element ControlResourceSet can be used to configure a time / frequency CORESET for searching for DCI. The configuration parameters can include at least one of a CORESET ID that identifies / indicates the CORESET, a frequency resource indication, a duration parameter indicating the number / amount of symbols in the CORESET, a CCE-REG mapping type indicator (not shown in Figure 25), multiple TCI states (e.g., tci-StatesPDCCH-ToAddList), an indicator indicating whether a TCI is present in the DCI (e.g., tci-PresentinDCI), etc. A controlResourceSetId value of 0 can identify / indicate a common CORESET configured in the MIB and / or ServingCellConfigCommon(controlResourceSetZero). The value through maxNrofControlResourceSets-1 may identify / indicate the CORESET configured in dedicated signaling and / or SB 1. controlResourceSetId may be unique among BWPs of a serving cell. A frequency resource indication including a number / amount of bits (e.g., 45 bits or any other number of bits) may indicate frequency domain resources. Each bit of the indication matrix may correspond to a group of 6 RBs (and / or any other number of RBs), for example, with the grouping starting from the first RB group in the BWP of a cell (e.g., SpCell, SCell). The first (e.g., leftmost / most significant) bit may correspond to the first RB group in the BWP, etc. A bit set to 1 may indicate that the RB group corresponding to that bit belongs to the frequency domain resources of the CORESET. Bits corresponding to groups of RBs that are not completely included in the BWP for which the CORESET is configured may be set to 0.The duration parameter may correspond to the Layer 1 parameter CORESET-Duration and / or can define / indicate a contiguous duration in number / amount of symbols of CORESET using an integer range ranging from 1 to maxCoReSetDuration. The CCE-REG mapping type indicator may provide a selection of the mapping method from control channel elements (CCEs) to resource element groups (REGs). A CCE may include the number / amount of resource element groups (REGs) (e.g., 6). A REG may comprise a resource block within an OFDM symbol. The mapping of coded and modulated DCI to resource elements can be based on the CCE and REG mapping (e.g., CCE to REG mapping). The tci-StatesPDCCH-ToAddList parameter may include a subset of TCI states defined / indicated in pdsch-Config, which may be included in BWP-DownlinkDedicated corresponding to the serving cell and / or DL ​​BWP to which the ControlResourceSet belongs. A subset of TCI states may be used to provide a QCL relationship between DL reference signals (RSs) and PDCCH DMRS ports in one RS set (e.g., TCI-State). The network may configure (e.g., at most) maxNrofTCI-StatesPDCCH entries. The tci-PresentinDCI parameter may indicate whether the TCI field is present in the DL-related DCI. If this field is not present, the wireless device may consider / determine that the TCI is not present / disabled. The network may set the TCI field to valid for the Control Resource Set used for cross-carrier scheduling in the scheduling cell (e.g., if cross-carrier scheduling is used).

[0203] The wireless device may monitor a set of PDCCH candidates. The set of PDCCH candidates may be defined in terms of a PDCCH search space set. The search space set may include a CSS set and / or a USS set. The wireless device may monitor PDCCH candidates in one or more of the following search space sets: a Type 0-PDCCH CSS set, a Type 0A-PDCCH CSS set, a Type 1-PDCCH CSS set, a Type 2-PDCCH CSS set, a Type 3-PDCCH CSS set, a USS set, and / or any other type of CSS set and / or USS set. The Type 0-PDCCH CSS set may be configured, for example, by pdcch-ConfigSIB1 in MIB and / or by searchSpaceSIB1 in PDCCH-ConfigCommon and / or by searchSpaceZero in PDCCH-ConfigCommon for a DCI format with CRC scrambled by SI-RNTI on the primary cell of the MCG. The Type-0A-PDCCH CSS set may be configured, for example, by searchSpaceOtherSystemInformation in PDCCH-ConfigCommon for DCI formats with CRC scrambled by SI-RNTI on the primary cell of the MCG. The Type-1-PDCCH CSS set may be configured, for example, by ra-SearchSpace in PDCCH-ConfigCommon for DCI formats with CRC scrambled by RA-RNTI or TC-RNTI on the primary cell. The Type-2-PDCCH CSS set may be configured, for example, by pagingSearchSpace in PDCCH-ConfigCommon for DCI formats with CRC scrambled by P-RNTI on the primary cell of the MCG.The Type 3-PDCCH CSS set may be configured by a SearchSpace in the PDCCH-Config with searchSpaceType=common, for example, for DCI formats with a CRC scrambled by the INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, and / or TPC-SRS-RNTI (e.g., C-RNTI, MCS-C-RNTI, and / or CS-RNTI for the primary cell only). The USS set may be configured by a SearchSpace in the PDCCH-Config with searchSpaceType=ue-Specific, for example, for DCI formats with a CRC scrambled by the C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, or CS-RNTI(s).

[0204] The wireless device may determine a PDCCH monitoring opportunity. The wireless device may determine a PDCCH monitoring opportunity, for example, in an active DL BWP. The wireless device may determine the PDCCH monitoring opportunity based on one or more PDCCH configuration parameters including a PDCCH monitoring period in a slot, a PDCCH monitoring offset, and / or a PDCCH monitoring pattern. For a search space set (SS s), the wireless device may, for example,

[0205]

number

[0206]

number

[0207]

number

[0208]

number

[0209] The wireless device may determine a CCE index for a slot for an active DL BWP of a serving cell corresponding to a carrier indication field value nCI for a search space set s associated with CORESETp.

[0210]

number

[0211]

number

[0212]

number

[0213]

number

[0214]

number

[0215]

number

[0216]

number

[0217]

number

[0218]

number

[0219]

number

[0220]

number

[0221] The wireless device may monitor a set of PDCCH candidates according to one or more configuration parameters. The configuration parameters may be for 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 of several DCI messages. 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 (and / or configured) PDCCH locations, possible (and / or configured) PDCCH formats (e.g., number / amount of CCEs, number / amount of PDCCH candidates in a common SS, and / or number / amount of PDCCH candidates in a UE-specific SS), and / or possible (and / or configured) DCI formats. The decoding may be referred to as blind decoding.

[0222] FIG. 26 illustrates an example of wireless communication using multiple transmit / receive points (TRPs) and / or multiple panels. As used herein, a TRP can refer to any transmitter / receiver device (e.g., in a base station and / or any other computing device). As used herein, a panel and / or antenna panel can refer to any transmitter / receiver device (e.g., in a wireless device and / or any other computing device). A base station 2610 uses multiple TRPs (e.g., TRP1 2615 and TRP2 2620). TRP1 may be identified by a first CORESET pool index, and TRP2 may be identified by a second CORESET pool index. A wireless device 2625 may be equipped with two or more panels (e.g., panel 1 2630 and panel 2 2635). Transmitting and receiving with multiple TRPs and / or multiple panels can improve system throughput and / or transmission robustness for wireless communications at high frequencies (e.g., above 6 GHz). As shown in FIG. 26, a base station 2610 may include multiple TRPs 2615 and 2620. The base station 2610 may include TRP1, which includes configuration parameters for multiple CORESETs on the cell (or BWP of the cell). 2615 or TRP2 2620 can be sent / transmitted to the wireless device 2625 via an RRC message. A wireless device 2625 having a TCI indication (e.g., DCI) 2635 is within proximity to TRP1 2640 and proximity to TRP2 2645. Each of the multiple CORESETs may be identified by a CORESET index and 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 CORESET is transmitted / transmitted from the same TRP among the multiple TRPs of the base station 2610. The wireless device 2625 may determine a receive ray (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 of the DCI.

[0223] A TRP of a plurality of TRPs of a base station may be identified / indicated by at least one of a TRP identifier (ID), a cell index, and / or a reference signal index. The TRP ID of a TRP may include a control resource set group (and / or pool) index (e.g., CORESETPoolIndex) of a control resource set group on which a DCI is transmitted / transmitted from the base station. The TRP ID of a TRP may include a TRP index indicated in the DCI. The TRP ID of a 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 and / or a base station transmits / transmits a downlink TB.

[0224] A wireless device may receive one or more PDCCHs scheduling fully / partially / non-overlapping PDSCHs in the time and frequency domains. The wireless device may receive one or more RRC messages (e.g., PDCCH-Config IEs) comprising a first CORESET pool index (e.g., CORESETPoolIndex) value and / or a second CORESET pool index (e.g., in a ControlResourceSet IE). The wireless device may determine reception of fully / partially overlapped PDSCHs in the time domain, for example, when the PDCCHs scheduling the two PDSCHs are associated with different control resource sets (e.g., ControlResourceSets) comprising different values ​​of the CORESET pool index (e.g., CORESETPoolIndex).

[0225] A wireless device may be configured to determine that a control resource set (e.g., ControlResourceSet) is assigned a core set pool index (e.g., CORESETPoolIndex) as 0 (or any other value) for a control resource set (e.g., ControlResourceSet) without / without lacing the core set pool index (e.g., CORESETPoolIndex). Scheduling information for receiving PDSCH transmissions may be indicated and / or carried by a corresponding PDCCH, for example, if the wireless device is scheduled with a full / partial / non-overlapping PDSCH in the time and frequency domain. The wireless device may be expected to be scheduled with the same active BWP and the same SCS. For example, if the wireless device is scheduled with a fully / partially overlapping PDSCH in the time and frequency domain, the wireless device may be scheduled with multiple codewords (e.g., two, or any other number, such as a maximum of two) simultaneously.

[0226] A wireless device may be permitted to perform one or more of the following operations, for example, when PDCCH transmissions scheduling two PDSCHs are associated with different control resource sets (e.g., ControlResourceSet) having different values ​​of a collocation pool index (e.g., CORESETPoolIndex): For example, for any two HARQ process IDs in a given scheduled cell, a wireless device may be scheduled to receive a PDSCH transmission that starts earlier than the end of the first PDSCH transmission with a PDCCH transmission associated with a different value of the collocation pool index (e.g., CORESETpoolIndex) that ends later than symbol i, for example, if the wireless device is scheduled to start receiving a first PDSCH transmission starting at symbol j with a PDCCH transmission associated with a value of the collocation pool index (e.g., CORESETpoolIndex) that ends later than symbol i. A wireless device may receive (e.g., in a given scheduled cell) in slot i a first PDSCH transmission with a corresponding HARQ-ACK assigned to be sent / transmitted in slot j and a second PDSCH transmission associated with a different CoreSet pool index (e.g., CORESETpoolIndex) value than the first PDSCH transmission, starting later than the first PDSCH transmission with a corresponding HARQ-ACK assigned to be sent / transmitted in a slot prior to slot j.

[0227] A wireless device configured by higher layer parameters (e.g., PDCCH-Config) may include two different values ​​of a coreset pool index (e.g., CORESETPoolIndex) in a control resource set (e.g., ControlResourceSet), for example, when a TCI indication (e.g., tci-PresentInDCI) is enabled (e.g., tci-PresentInDCI is set to “enabled”) and / or when a TCI indication (e.g., tci-PresentInDCI) is not configured in RRC connected mode. The wireless device may assume / determine that the DM-RS port of the PDSCH associated with a value of the collocation pool index (e.g., CORESETPoolIndex) of the serving cell is pseudo-co-located with the RS with respect to the QCL parameter, for example, if the offset between the reception of the DL DCI and the corresponding PDSCH transmission is less than a threshold value (e.g., timeDurationForQCL). The QCL parameter may be used for PDCCH pseudo-co-location indication of a CORESET associated with a monitored search space having the lowest CORESET-ID among the CORESETs. A CORESET is configured with a collocation pool index (e.g., CORESETPoolIndex) with the same value as the PDCCH transmission scheduling for which the PDSCH transmits. A PDCCH transmission is scheduled in the latest slot for one or more CORESETs associated with a collocation pool index (e.g., CORESETPoolIndex) with the same value as the PDCCH transmission scheduling for which the PDSCH transmissions within the active BWP of the serving cell are monitored by the wireless device. The offset between the receipt of the DCI and the corresponding PDSCH transmission may be less than a threshold (e.g., timeDurationForQCL), and at least one configured TCI state for the serving cell of the scheduled PDSCH may include a QCL type (e.g., 'QCL-TypeD').The wireless device may be configured to determine that a DM-RS port of a PDSCH of a serving cell is quasi-co-located with an RS with respect to a QCL parameter associated with a TCI state, for example, if at least one TCI codepoint indicates two TCI states, where the TCI state may correspond to the lowest codepoint among the TCI codepoints that include two different TCI states.

[0228] A wireless device (e.g., when configured with multiple panels) may determine to activate (or select) at least one of the multiple panels to receive downlink signals / channels transmitted / transmitted from one of the base station's multiple TRPs. The activation / selection of at least one of the multiple panels may be based on receiving downlink signaling indicating the activation / selection. The activation / selection may be performed (e.g., automatically) based on a measurement of downlink channel quality of one or more reference signals transmitted / transmitted from the base station. The wireless device may apply a spatial domain filter for transmission / transmission from a panel of the multiple panels to one of the base station's multiple TRPs. The panel and / or spatial domain filter may be determined based on at least one of a UL TCI indication of the DCI, a panel ID in the DCI, an SRI indication of the DCI, a CORESET pool index of the CORESET for receiving the DCI, etc.

[0229] For example, when the wireless device receives a DCI indicating an uplink grant, the wireless device may determine a panel and / or a transmit ray (and / or a spatial-domain transmit filter) on the panel. The panel may be indicated (e.g., explicitly indicated) by a panel ID included in the DCI. The panel may be indicated (e.g., implicitly indicated) by an SRSID (and / or SRS group / pool index), a ULTCI pool index of a ULTCI for uplink transmission, and / or a CORESET pool index of a CORESET for receiving the DCI.

[0230] A wireless device may use at least one of the multiple panels to communicate with a base station. A wireless device may use at least one of the multiple panels, for example, when using a high frequency / frequency range (e.g., above 6 GHz, or any other frequency / frequency). A wireless device may be required to comply with applicable RF exposure requirements. The RF exposure requirements may include one or more maximum permissible exposure (MPE) parameters associated with a frequency and / or frequency range. The one or more MPE parameters associated with a frequency / frequency range may include a maximum (or permissible) electric field strength value (E) in V / m, a maximum (or permissible) magnetic field strength value (H) in A / m, a maximum (or permissible) magnetic field strength value (H) in mW / cm 2 The RF exposure requirements may include a maximum (or allowable) power density value (S) in units of Hz and / or an average time value in units of minutes. Any other variables and any other units of measurement may be used for one or more of the MPE parameters. RF exposure requirements may be based on 68 / f 1.05 is defined / shown as the allowable power density averaged over minutes, where f is the value of the carrier frequency in GHz (e.g., the frequency of FR2). The averaging period can be about 2 minutes at 28 GHz and / or about 1.45 minutes at 39 GHz. Any averaging period can be used. Any allowable power density average may be used over any duration and / or at any carrier frequency.

[0231] FIG. 27A illustrates an example of wireless communication using multiple TRPs and / or multiple panels (e.g., antennas, antenna panels, etc.). One or more devices (e.g., using TRPs and / or panels) may be configured to detect uplink coverage loss and / or maximum power exposure (MPE)-related issues. The wireless communication system 2700 may include at least one base station 2710, one or more TRPs (e.g., TRP1 2715 and TRP2 2720), and / or at least one wireless device 2725. The wireless device 2725 may include one or more panels (e.g., panel 1 2730 and panel 2 2735). The wireless device may determine / detect / sense that a human body (or soft object, living organism, etc.) 2740 may be present in proximity (e.g., within a threshold distance and / or within the path of a light beam for transmission / reception) to a first panel 2730 (e.g., panel 1) of the wireless device 2725. The radio may determine / detect / sense the absence of a human body 2740 (and / or determine / detect / not sense the presence of a human body) in proximity (e.g., within a threshold distance and / or in the path of the light beam for transmission / reception) to the second panel 2735 (e.g., panel 2) of the wireless device 2725. The wireless device 2725 may determine / detect / sense the proximity of a human body using one or more sensors (e.g., which may be installed on the wireless device 2725). The wireless device 2725 may determine / detect / sense the proximity of a human body 2740 based on one or more instructions from, for example, another wireless device or a base station (e.g., base station 2710). The wireless device 2725 may reduce (e.g., automatically or based on one or more conditions) its transmit power (e.g., maximum transmit power) via the first panel 2730, for example, to comply with one or more RF exposure requirements based on one or more MPE parameters at the operating frequency / frequency. Reducing transmit power (e.g., maximum transmit power) may result in uplink coverage loss. For example, if the wireless device 2725 is located at or near the edge of the coverage area of ​​the base station 2710 (e.g., at or near the cell edge), uplink coverage loss may be particularly undesirable.The wireless device 2725 may use the second panel 2735 (e.g., panel 2) to transmit / transmit an uplink signal / channel to the base station 2710 (e.g., instead of reducing the transmit power (e.g., maximum transmit power) via the first panel 2730 to comply with RF exposure requirements). The wireless device 2725 may use the second panel 2735, for example, if the second panel 2735 is not in close proximity to a human body 2740. Transmitting via the second panel 2735 may relax the transmit power restriction (e.g., reduce the transmit power restriction requirement) to comply with one or more RF exposure requirements. For example, by using the second panel 2735, the wireless device 2725 may be able to transmit / transmit a message to the base station 2710 (e.g., via TRP2 2720) without reducing the transmit power (e.g., by using the maximum transmit power). The wireless device 2725 may indicate (e.g., to the base station 2710) that an object (e.g., a human body) has been detected in proximity to a first active panel (e.g., panel 1 2730) and / or that no object (e.g., a human body) has been detected in proximity to a second panel (e.g., panel 2 2735). The wireless device 2725 may indicate that one or more objects are in proximity to one or more panels (e.g., active panels, inactive panels, etc.), e.g., to avoid uplink coverage loss as a result of compliance with one or more RF exposure requirements. The base station 2710 may send / transmit a message / command, e.g., directing an active panel switch from the first panel (e.g., panel 1 2730) to the second panel (e.g., panel 2 2735). The base station 2710 may send / transmit a message / command based on (e.g., after or in response to) receiving one or more indications from the wireless device 2725 (e.g., indicating that one or more objects are in proximity to one or more panels associated with the wireless device 2725), for example.

[0232] A wireless device may automatically reduce its maximum output power for transmitting / transmitting a signal or channel to a base station by complying with RF exposure requirements based on proximity detection. The maximum output power reduction due to compliance with RF exposure requirements may be referred to as a maximum transmit power reduction (P-MPR). For various examples, the wireless device may reduce its P-MPR for carrier f of serving cell c by: f,c For example, the wireless device may apply a P-MPR for carrier f of serving cell c. f,c to help ensure (and / or increase the likelihood of) compliance with applicable electromagnetic power density exposure requirements and / or address unwanted emissions and / or self-protection requirements, for example, based on simultaneous transmissions in multiple RATs (e.g., for conditions that may or may not be within the scope of one or more 3GPP RAN specifications). f,c P-MPR may be applied to help ensure (and / or increase the likelihood of) compliance with applicable electromagnetic power density exposure requirements, for example, based on proximity detection being used to address requirements that may require a lower maximum output power. f,c may be 0 dB, for example, for wireless device conformance testing.

[0233] A wireless device may reduce output power (e.g., maximum output power) due to modulation order. The wireless device may transmit / transmit a bandwidth configuration, a waveform type, and / or one or more allocations (e.g., narrow allocations). The amount of output power reduction (e.g., maximum output power reduction) due to implementing a modulation order, bandwidth, and / or waveform type, etc., may be referred to as a maximum power reduction (MPR). In the above example, the cause of MPR may be different from the cause of P-MPR.

[0234] A wireless device may be signaled by a base station with one or more (e.g., additional) emission requirements. Each emission requirement (and / or each additional emission requirement) may be associated with a unique network signaling (NS) value. The NS value may be indicated in signaling (e.g., RRC signaling) by the frequency band of the applicable operating band (e.g., an NR frequency band number or any other frequency band indication). The NS value may also be indicated in a field (e.g., as an associated value indicated in an additionalSpectrumEmission field). A wireless device may, for example, reduce power to meet one or more requirements (e.g., each emission requirement). This reduced power may be referred to as the maximum allowable transmit power reduction (A-MPR).

[0235] The wireless device may determine the maximum output power (e.g., P CMAX,f,c The wireless device may set, for example, a power value for the P-MPR, MPR, A-MPR, the power class of the wireless device, and / or the maximum effective isotropic radiated power (EIRP) of the wireless device. max ) the maximum output power can be configured based on one or more of the following: P CMAX,f,c may be defined as the output power available to a reference point of a given transmitter branch that corresponds to the reference point of the upper layer filtered RSRP measurement. The wireless device may calculate the corresponding measured peak EIRP P UMAX,f,c The maximum output power (e.g., P CMAX,f,c ) can be set. P 電力クラス -MAX(MAX(MPR f,c ,A-MPR f,c )+ΔMB P,n ,P-MPR f,c )- MAX{T(MAX(MPR f,c ,A-MPR f,c )),T(PMPR f,c )}≦P UMAX,f,c ≦EIRP maxis. The corresponding measured total radiated power (e.g., P TMAX,f,c ) is P TMAX、f、c ≦TRP max The variable P 電力クラス may indicate a power value corresponding to the power class of the wireless device. max MPR can indicate the maximum applicable EIRP. f,c A-MPR may denote the MPR applicable to the modulation order, bandwidth, and / or waveform type associated with frequency f on cell c. f,c may indicate the maximum allowable transmit power reduction indicated by the base station. P,n may indicate peak EIRP relaxation. max may indicate the maximum total radiated power of the power class of the wireless device.

[0236] A wireless device may transmit one or more RRC messages indicating a capability parameter (e.g., maxUplinkDutyCycle-FR2 for a UE) to facilitate electromagnetic power density exposure requirements. The wireless device may transmit one or more messages indicating a capability parameter in addition to, for example, a power reduction indication (e.g., MPR, A-MPR, and / or P-MPR). The wireless device may, for example, comply with uplink scheduling and / or P-MPR if a capability parameter field (e.g., maxUplinkDutyCycle-FR2) for the wireless device is present and / or if the percentage of uplink symbols transmitted within a certain duration (e.g., within any one-second evaluation period) is greater than a threshold (e.g., maxUplinkDutyCycle-FR2). f,c For example, if a field for a wireless device capability parameter (e.g., maxUplinkDutyCycle-FR2) is not present, compliance with electromagnetic power density exposure requirements may be ensured by scaling down the power density and / or by other actions.

[0237] Wireless communications may use one or more devices for transmission and / or reception. For example, a wireless device may use one or more antenna panels and / or any other device for transmission and / or reception of wireless communications. A base station may use one or more TRPs and / or any other device for transmission and / or reception of wireless communications. Increasing the number of devices for transmission / reception, increasing the amount of wireless communications transmitted / received, and / or increasing the amount of power (and / or light used) for transmission / reception may increase the risk of potentially harmful and / or undesirable exposure to radio frequency (RF) electromagnetic fields. For example, one or more safety measures may be implemented and / or required for wireless communication devices to reduce the amount / likelihood of exposure to potentially harmful and / or undesirable RF electromagnetic fields. Maximum power exposure (MPE) and / or any other limits on exposure may be implemented and / or required (e.g., by the Federal Communications Commission (FCC) and / or any other regulatory or standardization body). Such exposure limits and / or restrictions may include frequency ranges (e.g., MHz, GHz, etc.), electric field strengths (e.g., in V / m), magnetic field strengths (e.g., in A / m), power densities (e.g., in mW / cm 2 The MPE requirement may be based on one or more of: millimeter wave (mW / area, etc.), and / or any combination of millimeter wave (mmWave) radiation exposure to a human (and / or any other living organism) over a certain duration. For example, the MPE requirement may be based on the amount of millimeter wave (mmWave) radiation exposure to a human (and / or any other living organism) over a certain duration. For example, transmit power may need to be reduced if a human is in close proximity (e.g., within a threshold range) to a transmitter / receiver that would otherwise exceed the MPE requirement / limit (e.g., an antenna panel on a wireless device transmitting a wireless signal via a beam of light at a level that could exceed the MPE).

[0238] Figure 27B shows an example of power reduction based on exposure. A wireless device (and / or any other device, such as a base station, IoT device, core network device, etc.) may have a maximum transmit power 2701 (e.g., maximum UE Tx power) for transmissions for which no MPE (or other exposure requirement / limit) is identified. This maximum transmit power is P CMAXand / or may correspond to any other indication of maximum transmit power (e.g., maximum allowed transmit power). The wireless device transmit power may include the power allocated to the first message (e.g., data transmission), shown as 2701B (e.g., UE Tx power), and the remaining / residual power (e.g., the difference between the wireless device's maximum transmit power and the estimated power for uplink transmission), shown as 2701A. The wireless device may determine one or more MPE instances, which may result in a requirement for a reduction in transmit power, such as, for example, a maximum power reduction (MPR) 2702 due to the one or more MPE instances. The MPR 2702 may include a reduction in transmit power from a first level 2702A (e.g., at or near the maximum transmit power 2701) to a second level 2702B. The residual (or remaining) power 2711A (e.g., the difference between the reduced maximum transmit power 2702B and the estimated power for uplink transmission) 2711B may be reduced due to MPE detection. Based on the MPE indication, the wireless device may be required to reduce its transmit power by the amount of MPR 2702, for example, to a maximum transmit power 2701 (e.g., maximum UE Tx power), which may be less than the maximum transmit power 2711 for transmissions for which no MPE is identified / indicated. A power reduction based on the exposure indication and / or a report on exposure may degrade the performance of the wireless device (and / or any other device, such as a base station, IoT device, core network device, etc.). For example, based on the power reduction, one or more messages may not be successfully transmitted / received. A wireless device (or any other type of multiple transmit / receive device) configured with multiple antenna panels may trigger a switch to / from another panel (or another transmit / receive device), which may result in increased latency, increased power consumption by the wireless device, and / or increased interference with other wireless transmissions (e.g., by other wireless devices). The wireless device may increase its power consumption based, for example, on a requirement for exposure reporting (e.g., an additional message to report the exposure indication).

[0239] The P-MPR may be greater than the MPR or A-MPR, for example, in high-frequency conditions. Reducing the maximum output power due to the P-MPR to comply with RF exposure requirements may reduce uplink coverage. Reducing the maximum output power for uplink transmission may not impact downlink coverage. A mismatch between downlink and uplink coverage may occur, for example, due to compliance with one or more MPE requirements. Uplink coverage loss due to compliance with an MPE requirement may generally be referred to as an MPE-related issue. At least some wireless devices may be configured to switch (e.g., automatically switch) from a first panel to a second panel to avoid reducing the maximum output power based on, for example, an MPE detection (e.g., when the wireless device detects that a human body is in proximity (or there is a soft object) to the first panel of the wireless device). The wireless device may transmit / transmit per-ray and / or per-panel power headroom (PHR) MAC CE reports to the base station to facilitate base station handling of MPE-related issues. The base station may send an instruction / command to the wireless device to switch from the first panel to the second panel, for example, based on per-ray and / or per-panel PHR reports. The wireless device may send an instruction to the base station indicating uplink coverage issues in the first panel, for example, due to MPE-related issues. The wireless device may send an instruction to the base station indicating that the second panel is better than the first panel (e.g., in terms of applicable power reduction). At least some wireless devices may prematurely switch back and forth between the first and second panels, for example, due to the dynamic presence of a human body in a certain area (e.g., within a threshold vicinity of the wireless device's panel). Such wireless devices may require increased processing time to respond to and / or address the presence (e.g., dynamic presence) of a human body in an area (e.g., within a threshold vicinity of the wireless device's panel) that may result in a loss of uplink coverage.Such wireless devices may unnecessarily and / or frequently report MPE-related problems to a base station, which may increase signaling overhead and / or increase power consumption by the wireless device.

[0240] As described herein, improvement can be achieved, for example, by implementing one or more safety actions (e.g., MPE reporting, applying MPR, etc.) while minimizing unnecessary reporting (e.g., MPE reporting) and / or other actions related to the safety action (e.g., MPR power reduction). A time window can be used to detect the amount of exposure instances (e.g., MPE indication). The amount may be compared to a threshold to determine, for example, whether one or more safety actions must be implemented (e.g., MPE reporting, applying MPR). The base station may transmit a message (e.g., an RRC message) to the wireless device comprising one or more indications (e.g., configuration parameters) of the time window and / or threshold. For example, the base station may transmit a message (e.g., MPE report) indicating exposure based on the amount of exposure events during the time window that meets a threshold (e.g., the amount of MPE exposure indications that exceed the threshold during the time window), so that unnecessary reporting and / or other actions can be reduced and the safety action can be satisfied. Based on (e.g., after or in response to) detection of one or more exposures (e.g., MPE(s)), the wireless device may send / transmit to the base station an exposure indication (e.g., MPE report) in a transmission including one or more of a preamble (e.g., via a RACH resource associated with the MPE report of a particular antenna panel), a scheduling request (e.g., via a PUCCH resource associated with the MPE report of a particular antenna panel), a sounding reference signal (e.g., via a dedicated SRS associated with the MPE report of a particular panel), and / or any other message (e.g., via a PUCCH).

[0241] A wireless device may be configured to comply with one or more MPE requirements. A wireless device may comply with one or more MPE requirements while maintaining reliable coverage (e.g., for uplink and / or downlink). A wireless device may include one or more panels (e.g., antenna panels, antennas, etc.) for transmitting and / or receiving over wireless communications. A base station may set / determine one or more MPE detection windows (and / or MPE detection timers) for one or more wireless devices. A base station may configure / determine one or more thresholds for MPE detection. A base station may transmit one or more messages to a wireless device including one or more instructions indicating one or more MPE detection windows and / or one or more thresholds. A wireless device may determine one or more MPE detection windows and / or one or more thresholds (e.g., for detecting an MPE occurrence). The wireless device may trigger an uplink coverage recovery signal transmission based on (e.g., after or in response to) detecting at least one of the number / amount of MPE instances within an MPE detection window, an MPE detection timer running and / or not expiring, and / or the detected number / amount of MPE instances during the MPE detection window meeting (e.g., being equal to or greater than) a threshold. The wireless device may detect an MPE instance based on, for example, a P-MPR value of one or more panels, a duty cycle of one or more panels, and / or a combined value of the P-MPR and RSRP of each of the one or more panels. A wireless communication system may include a base station that uses dedicated RACH resources for uplink coverage recovery and a wireless device that triggers a RACH procedure via the dedicated RACH resources. The wireless device may trigger / initiate a RACH procedure based on, for example, detecting the number / amount of MPE instances (e.g., meeting a threshold). The base station may configure dedicated SR resources for uplink coverage recovery. The wireless device may trigger / send an SR via a dedicated SR resource, for example, based on (e.g., after or in response to) detecting the number / amount of MPE instances (e.g., meeting a threshold).The base station may configure a dedicated SRS for uplink coverage recovery. The wireless device may trigger / transmit transmission of the dedicated SRS, for example, based on (e.g., after or in response to) detecting the number / amount of MPE instances (e.g., meeting a threshold). The wireless device may trigger / transmit transmission of an RRC message (e.g., a UE assistance message). The assistance message may indicate that an uplink coverage loss is occurring (or has occurred) on a first panel of multiple panels of the wireless device. The message may be based on (e.g., transmitted after or in response to) the wireless device detecting the number / amount of MPE instances on the first panel (e.g., meeting a threshold). The base station may transmit / configure a dedicated configuration grant for uplink coverage recovery (and / or uplink coverage loss mitigation). The wireless device may transmit / transmit an uplink TB with transmission repetition via the dedicated configuration grant and / or transmit power reduction that may be based on (e.g., transmitted after or in response to) detecting the number / amount of MPE instances (e.g., meeting a threshold). As described herein, uplink coverage may be improved based on, for example, MPE detection and / or reporting (e.g., due to the dynamic presence of a human body near a wireless device).

[0242] FIG. 28 illustrates an example method for exposure detection and / or reporting. The method can include coverage loss mitigation. The method can improve MPE detection and / or reporting. The base station 2810 may send / transmit one or more messages 2820 (e.g., one or more RRC messages) comprising configuration parameters to the wireless device 2815. The configuration parameters can be for MPE detection 2825 and / or uplink coverage restoration and / or uplink coverage loss mitigation. The configuration parameters can include one or more of a length (e.g., duration) and / or threshold (e.g., for triggering uplink coverage restoration signal transmission) of the MPE detection (or measurement) window 2830. The length of the MPE detection window 2830 may be in units of milliseconds, seconds, or minutes; minislots, slots, or frames; or any other period (e.g., any duration amount). The threshold can be a number / quantity greater than or equal to one (or any other number / quantity). Configuration parameters for uplink coverage restoration (and / or uplink coverage loss mitigation) may be implemented based on the examples of FIG. 31, FIG. 32, and / or FIG. 33 described herein. The wireless device 2815 may initiate detection of a first MPE instance 2835 based on configuration parameters associated with one or more MPE detections. The MPE instance may be detected based on one or more examples of FIG. 29 described herein. As referred to herein, an MPE instance may include any exposure detection. An exposure detection may include, for example, an acceptable exposure detection (e.g., an exposure detection and / or duration below a threshold in a measurement), an unacceptable exposure detection (e.g., an exposure detection above a threshold in a measurement and / or duration), and / or any combination thereof. The MPE detection window 2830 may be configured, predefined, and / or preconfigured with a fixed window size (and / or a variable window size based on one or more conditions). The width of the detection window 2830 may be defined / dictated by the detection of the first MPE instance 2835 and / or the detection of a number / amount of MPE instances greater than a threshold 2840 .The threshold for triggering the uplink coverage restoration signal transmission 2845 can be configured, predefined, and / or pre-configured with a fixed value (and / or a variable value based on one or more conditions). The value can be 1 or any number / quantity greater than 1. The one or more configuration messages 2820 can include configuration parameters for the uplink coverage restoration signal 2845.

[0243] The wireless device may detect the first MPE instance. The wireless device may start an MPE detection window, for example, based on detecting the first MPE instance (e.g., after or in response to detection). The wireless device may not start an MPE detection window, for example, based on not detecting the first MPE instance (e.g., after or in response to non-detection). The wireless device may detect the number / quantity of MPE instances within / during the MPE detection window. The number / quantity of MPE instances may be consecutive. Consecutive MPE instances may be defined / indicated as MPE instances occurring in consecutive measurement (and / or detection) intervals. Consecutive MPE instances may occur at a fixed time interval, for example, a fixed time interval after a previous MPE instance. For example, a third consecutive MPE instance may occur at the same time interval after a second consecutive MPE instance, relative to the time interval of the second consecutive MPE instance occurring after the first consecutive MPE instance. Consecutive MPE instances may occur during a shorter time interval than non-consecutive MPE instances. The time window / interval for consecutive MPE instances may be of any duration, such as 100 seconds, during which consecutive MPE instances may be detected at periodic portions thereof, such as every 1 second of the 100-second time window / interval (or any other duration). Detecting consecutive MPE instances may indicate the constant presence of a human body in the vicinity (e.g., within a threshold distance / area) of the wireless device. The wireless device may trigger transmission of an uplink coverage restoration signal, for example, based on detecting (e.g., after or in response to) the number / quantity of MPE instances within / during the MPE detection window and / or based on the number / quantity meeting (e.g., greater than) a threshold. The uplink coverage restoration signal may be implemented based on the examples of Figures 31, 33, and / or 34 described herein.

[0244] A wireless device may detect sporadic MPE instances, for example, when a human body moves near the wireless device. Detecting sporadic MPE instances may not necessarily cause uplink coverage loss based on MPE requirements (e.g., due to compliance with MPE requirements). By defining thresholds and / or evaluation windows, a wireless device may avoid unnecessarily triggering an uplink coverage restoration process. By implementing and / or utilizing thresholds and / or evaluation windows, a wireless device may achieve benefits such as improved power consumption efficiency, improved uplink throughput, and / or reduced uplink transmission latency.

[0245] FIG. 29 illustrates an example of exposure instance detection for wireless communication. The exposure instance detection may be for a wireless device using multiple TRPs and / or multiple panels to communicate with a base station. Table 2900 illustrates an example of maximum power exposure (MPE) instance detection for wireless communication of a wireless device 2910 using multiple panels (e.g., antenna panels, antennas, transceiver devices, etc.) including a first panel 2915 and at least a second panel 2910. Although an example is illustrated in table 2900, MPE instances and corresponding threshold conditions other than those illustrated in table 2900 may be used. The first panel 2915 and / or the second panel 2920 may be activated. For example, the wireless device 2910 may transmit / transmit an uplink signal via the first panel 2915 during a first period if the first panel 2915 is activated. The wireless device 2910 may transmit / transmit an uplink signal via the second panel 2920 during a second period if the second panel is activated. The wireless device 2910 may detect an MPE instance based on measurements of the first panel 2915 and / or the second panel 2920. Table 2900 shows multiple examples of MPE instance conditions (e.g., 2901A, 2902A, 2903A, and 2904A) that may be detected and corresponding threshold conditions (e.g., 2901B, 2902B, 2903B, and 2904B) for detection by the wireless device 2910. The elements of table 2900 are based on the cell's uplink duty cycle. The cell's uplink duty cycle may be defined / indicated as a percentage or number of uplink symbols transmitted / transmitted via the cell within / during an evaluation period (e.g., milliseconds, seconds, or any other duration or period). The uplink duty cycle may be evaluated for each panel, for example, when the wireless device 2910 switches uplink transmission between the first panel 2915 and the second panel 2920. The first uplink duty cycle of the first panel may be defined / indicated as the percentage or number of uplink symbols sent / transmitted via the first panel within / during an evaluation period.The second uplink duty cycle of the second panel 2920 may be defined / indicated as the percentage or number of uplink symbols sent / transmitted via the second panel within / during an evaluation period.

[0246] The wireless device 2910 may detect an MPE instance (e.g., 2901A) based on a first uplink duty cycle of the first panel 2915 and a second uplink duty cycle of the second panel 2920. For example, if the following threshold conditions occur (e.g., 2901B): the first uplink duty cycle evaluated by the first panel 2915 is greater than a threshold and / or the second uplink duty cycle evaluated by the second panel 2920 is less than a threshold, the MPE instance (e.g., 2901A) may be efficiently detected and / or resolved.

[0247] The wireless device may determine whether to apply a P-MPR value based on a joint evaluation of the first uplink duty cycle of the first panel and the second uplink duty cycle of at least the second panel. The wireless device 2910 may detect an MPE instance (e.g., 2902A) based on, for example, the first P-MPR of the first panel 2915 and the second P-MPR of the second panel 2920. For example, if the following threshold conditions occur (e.g., 2902B): the P-MPR via the first panel 2915 is greater than a threshold and / or the P-MPR via the second panel 2920 is less than a threshold (e.g., 2902B), the MPE instance may be efficiently detected and / or resolved. The first uplink duty cycle and the second uplink duty cycle may be evaluated during the same evaluation period. The wireless device 2910 may determine to apply a P-MPR value based on the sum of the first uplink duty cycle and the second uplink duty cycle being greater than a threshold (e.g., maxUplinkDutyCycle-PC2-FR1, maxUplinkDutyCycle-FR2, etc.). The wireless device 2910 may determine to apply a P-MPR value based on which of the first uplink duty cycle and the second uplink duty cycle is greater than a threshold. The wireless device 2910 may apply the P-MPR based on at least one of the first uplink duty cycle, the second uplink duty cycle, the maximum of the first uplink duty cycle and the second uplink duty cycle, and / or the first uplink duty cycle and the second uplink duty cycle. The wireless device 2910 may apply P-MBP based on at least one or more conditions provided by configuration information (e.g., one or more RRC messages, DCI, MAC CE, etc.), and / or the one or more conditions may be predefined (e.g., preconfigured in the wireless device 2910).

[0248] The wireless device 2910 may detect an MPE instance based on (e.g., after or in response to) determining that a first uplink duty cycle evaluated in a first panel 2915 (e.g., within / during an evaluation period) is greater than a threshold and / or based on determining that a second uplink duty cycle evaluated in at least a second panel 2920 (e.g., within / during an evaluation period) is less than a threshold. The threshold may be a parameter determined based on a capability parameter associated with the wireless device 2910. The wireless device 2910 may send / transmit one or more capability messages (e.g., UECapabilityInformation IE) comprising the threshold to a base station. The wireless device 2910 may send / transmit one or more capability messages (e.g., RRC messages) based on (e.g., after or in response to) receiving one or more messages (e.g., RRC messages) indicating a capability inquiry (e.g., UECapabilityEnquiry IE) from a base station, for example. The threshold value may be indicated by a duty cycle parameter (e.g., maxUplinkDutyCycle of UECapabilityInformation). The duty cycle parameter (e.g., maxUplinkDutyCycle) may indicate, for example, a percentage or amount (e.g., a maximum percentage or amount) of symbols during an evaluation period (e.g., 1 second or any other duration) that may be scheduled for uplink transmission, which may help ensure compliance with applicable electromagnetic power density exposure requirements (e.g., provided by one or more regulatory bodies, standardization bodies, etc.). The wireless device 2910 may determine, for example, that an uplink coverage loss may occur at the first panel 2915 if the first uplink duty cycle of the first panel 2915 is greater than the threshold value. The uplink coverage loss may result from application of P-MPR at the first panel 2915 (e.g., based on proximity detection near or in the direction of the first panel).The wireless device 2910 may determine that an uplink coverage loss is less likely to occur on the second panel 2920 than on the first panel 2915, for example, if the second uplink duty cycle of the second panel 2920 is less than a threshold. The wireless device may detect (or declare) an MPE instance based on (e.g., after or in response to) the first uplink duty cycle evaluated on the first panel 2915 being greater than a threshold and / or the second uplink duty cycle evaluated on the second panel 2920 (e.g., within / during an evaluation period) being less than a threshold.

[0249] The wireless device 2910 may detect / determine an MPE instance based on a first P-MPR of the first panel and a second P-MPR of at least a second panel. The wireless device 2910 may determine the P-MPR based on at least one of two requirements: compliance with applicable electromagnetic power density exposure requirements, and / or compliance with applicable electromagnetic power density exposure requirements based on proximity detection used to address unwanted emissions / self-protection requirements based on simultaneous transmission in multiple RATs (e.g., in cases where conditions may exceed the scope of 3GPP RAN specifications or other requirements), and / or address one or more requirements requiring lower maximum output power. For example, if the wireless device 2910 determines to transmit via the first panel 2915, the wireless device 2910 may determine a first value of the first P-MPR of the first panel 2915 based on the two requirements that apply to the first panel 2915. For example, if the wireless device 2910 determines to transmit via the second panel 2920, the wireless device 2910 may determine a second value of the second P-MPR of the second panel 2920 based on two requirements that apply to the second panel 2920. The wireless device 2910 may detect (and / or declare / indicate) an MPE instance based on the first P-MPR of the first panel 2915 being greater than a threshold and / or the second P-MPR of the second panel 2920 being less than a threshold (e.g., after or in response to being less than). The threshold may be a power reduction value that may be determined based on wireless device capabilities.

[0250] The wireless device may send / transmit one or more wireless device capability messages (e.g., UECapabilityInformation IE, RRC message, etc.) comprising a threshold value (e.g., associated with one or more MPE instances) to the base station. The wireless device may send / transmit capabilities via one or more messages (e.g., RRC messages) based on (e.g., after or in response to) receiving a capability inquiry / request (e.g., UECapabilityEnquiry IE) from the base station, for example. The threshold value may indicate a P-MPR value. The wireless device may determine that uplink coverage loss may occur at the panel (e.g., due to compliance with one or more MPE requirements based on proximity detection), for example, if the applied P-MPR value is greater than the threshold value. The wireless device may determine that uplink coverage loss is unlikely to occur at the panel, for example, if the applied P-MPR value is less than the threshold value.

[0251] The wireless device may determine that an uplink coverage loss may occur in the first panel and / or may not occur in the second panel, for example, if the wireless device determines that the first P-MPR of the first panel is greater than a threshold and / or if the wireless device determines that the second P-MPR of the second panel is less than a threshold. The wireless device may detect an MPE instance based on a comparison between the first P-MPR of the first panel and the second P-MPR of the second panel. For example, if the wireless device determines that the first P-MPR of the first panel is higher than the second P-MPR of the second panel, the wireless device may determine that an uplink coverage loss is more likely to occur in the first panel than in the second panel. For example, the wireless device may trigger / initiate transmission of an uplink coverage restoration signal (e.g., based on the examples described with respect to Figures 31, 32 and / or 33) if the wireless device detects the number / amount of MPE instances occurring in the first panel or the second panel (e.g., within a detection window such as described with respect to Figure 28).

[0252] The wireless device 2910 may detect an MPE instance based on a change in a first P-MPR of a first panel and a change in a second P-MPR of a second panel (e.g., 2903A). The P-MPR change may be determined for each panel. The wireless device 2910 may determine a change in the P-MPR of a panel based on a comparison of a P-MPR determined for a most recent (or current) uplink transmission (e.g., before / before the most recent uplink transmission) with a P-MPR determined for a previous uplink transmission. The wireless device 2910 may detect an MPE instance based on the change in the first P-MPR value being greater than a threshold and / or the change in the second P-MPR value being less than a threshold (e.g., after or in response to being less than a threshold) (e.g., 2903B). The threshold may be a power reduction value that may be determined based on wireless device capabilities.

[0253] The wireless device may send / transmit one or more wireless device capability messages (e.g., UECapabilityInformation IE, RRC message, etc.) comprising a threshold value (e.g., associated with an MPE instance) to the base station. The wireless device may send / transmit the capability message based on (e.g., after or in response to) receiving one or more messages (e.g., RRC messages) from the base station indicating a capability request (e.g., UECapabilityEnquiry IE). The threshold value may indicate a P-MPR change value. The wireless device may determine, for example, that an uplink coverage loss may occur in the panel (e.g., due to compliance with an MPE requirement based on proximity detection) if the P-MPR change applied by the wireless device is greater than the threshold value. The wireless device may determine, for example, that an uplink coverage loss may not occur in the panel (e.g., due to compliance with an MPE requirement based on proximity detection) if the P-MPR change applied by the wireless device is less than the threshold value.

[0254] The wireless device may detect an MPE instance based on a comparison between a first change in the first P-MPR of the first panel and a second change in the second P-MPR of the second panel. The wireless device may determine that an uplink coverage loss is more likely to occur in the first panel than in the second panel, for example, if the wireless device determines that the first change in the first P-MPR of the first panel is greater than the second change in the second P-MPR of the second panel. The wireless device may trigger / initiate transmission of an uplink coverage restoration signal (e.g., based on the examples described with respect to Figures 31, 32, and / or 33) when, for example, the wireless device detects / determines the number / amount of MPE instances occurring in the first panel or the second panel (e.g., within a detection window such as that described with respect to Figure 28).

[0255] The wireless device 2910 may detect / determine an MPE instance based on a first P-MPR and a first RSRP of a first panel 2915 and a second P-MPR and a second RSRP of a second panel 2920 (e.g., 2904A). The P-MPR may be determined based on one or more examples described herein. The RSRP may be defined / indicated as a linear average of the power contributions of the resource elements of the antenna ports carrying the reference signals (e.g., SSB and / or CSI-RS) configured for the RSRP measurement within the measurement frequency bandwidth at the configured reference signal occasion. The first frequency range (e.g., FR 1) The reference point may be an antenna connector of the wireless device 2910. The RSRP of a second frequency range (e.g., FR2) may be measured based on a composite signal from an antenna element corresponding to a receive branch (e.g., a designated receive branch). The first RSRP of the first panel 2915 may be measured on the RS received via the first panel 2915. The second RSRP of the second panel 2920 may be measured on the RS received via the second panel 2920. The first RSRP may be the same as or different from the second RSRP. The wireless device 2910 may detect an MPE instance based on the combined value of the first P-MPR and the first RSRP of the first panel 2915 being less than a threshold and / or the combined value of the second P-MPR and the second RSRP of the second panel 2920 being greater than a threshold (e.g., 2904B). The combined value of RSRP and P-MPR may be determined as the value of RSRP minus the value of P-MPR (e.g., where the value of P-MPR is greater than or equal to 0). The threshold value may be determined based on wireless device capabilities.

[0256] The wireless device may send / transmit one or more wireless device capability messages (e.g., UECapabilityInformation IE, RRC message, etc.) comprising a threshold value to the base station. The wireless device may send / transmit the capability message based on (e.g., after or in response to) receiving one or more messages (e.g., RRC messages) from the base station indicating a capability request (e.g., UECapabilityEnquiry IE). The threshold value may indicate a combined RSRP and P-MPR value. The wireless device may determine that uplink coverage loss may occur at the panel (e.g., due to compliance with proximity detection-based MPE requirements) if, for example, the combined value of the measured RSRP value and the applied P-MPR value at the panel is less than the threshold value. The wireless device may determine that uplink coverage loss may not occur at the panel if, for example, the combined value of the measured RSRP value and the applied P-MPR value at the panel is greater than the threshold value.

[0257] The wireless device may detect an MPE instance based on a comparison of a first combined value of a first P-MPR and a first RSRP of a first panel with a second combined value of a second P-MPR and a second RSRP of a second panel. For example, if the wireless device determines that the first combined value of the first panel is smaller than the second combined value of the second panel, the wireless device may determine that an uplink coverage loss is more likely to occur in the first panel than in the second panel. For example, if the wireless device detects / determines the number / amount of MPE instances occurring in the first panel or the second panel (e.g., within a detection window such as that described with respect to FIG. 28), the wireless device may trigger / initiate transmission of an uplink coverage restoration signal (e.g., based on the examples described with respect to FIG. 31, FIG. 32, and / or FIG. 33).

[0258] One or more of the examples described with reference to FIG. 29 may be combined to detect an MPE instance. The wireless device may detect an MPE instance based on a joint evaluation of one or more of the uplink duty cycle, P-MPR, and / or RSRP on the panels. The wireless device may detect an MPE instance based on at least one of: a first uplink duty cycle of a first panel being greater than a first threshold, and / or a first P-MPR of the first panel being greater than a second threshold, and / or a second uplink duty cycle of a second panel being less than the first threshold, and / or a second P-MPR of the second panel being less than a second threshold. The wireless device may detect the MPE instance based on at least one of: a first uplink duty cycle of the first panel being greater than a first threshold; and / or a combined value of the first P-MPR and the first RSRP of the first panel being greater than a second threshold; and / or a second uplink duty cycle of the second panel being less than the first threshold; and / or a combined value of the second P-MPR and the second RSRP of the second panel being less than a second threshold.

[0259] FIG. 30 illustrates an example method for coverage restoration and / or coverage loss mitigation. Method 3000 may include uplink coverage restoration and / or coverage loss mitigation. In step 3010, the wireless device may start a detection timer (e.g., an MPE detection timer) based on initializing coverage restoration. In step 3015, the wireless device may determine whether an exposure instance (e.g., an MPE instance) is detected. If an exposure instance is not detected (e.g., step 3020), the wireless device may repeat step 3015. In step 3025, the wireless device may increment a coverage restoration counter. In step 3030, the wireless device may determine whether a CR counter is greater than a certain amount and / or whether a CR timer is running. The amount may be pre-configured, pre-stored, and / or provided in one or more configuration parameters received from a base station or another wireless device. If the CR counter is not greater than the amount (e.g., step 3035), the wireless device may repeat step 3015 to determine whether an exposure instance has been detected. In step 3040, the wireless device may reset the CR counter and / or stop the detection timer. In step 3050, the wireless device may trigger / initiate / transmit transmission of a CR signal. The CR signal may be associated with reporting one or more MPE indications.

[0260] The base station may transmit / transmit one or more messages (e.g., RRC messages) including configuration parameters for uplink coverage recovery to the wireless device. The configuration parameters may include a timer value of an MPE detection timer and / or a number / quantity for triggering uplink coverage recovery signal transmission. The wireless device may start the MPE detection timer using the timer value. The wireless device may start the MPE detection timer based on detecting a first MPE instance. The wireless device may set an MPE detection counter to a first value (e.g., 0 or 1) based on detecting the first MPE instance. The wireless device may detect the first MPE instance based on one or more conditions s (e.g., as described with respect to FIG. 29). The MPE detection timer and / or number / quantity may be configured separately and / or independently from the BFR timer and / or number / quantity for triggering a BFR procedure.

[0261] The wireless device may determine whether a second MPE instance is detected. Based on whether the second MPE instance is detected, the wireless device may increment an MPE detection counter by a value (e.g., 1 or any other value). The wireless device may continue to detect MPE instances in the next measurement period, for example, if the second MPE instance is not detected. The wireless device may not increment the MPE detection counter, for example, if the second MPE instance is not detected. The wireless device may determine whether the MPE detection counter is greater than or equal to a number / quantum (e.g., which may be configured by one or more RRC messages), for example, if the MPE detection timer is running and based on the detection of the second MPE instance. The wireless device may continue to detect one or more MPE instances in the next measurement period (e.g., based on the example described with respect to FIG. 29), for example, if the MPE detection counter is not greater than or equal to the number / quantity and / or if the MPE detection timer is running. The wireless device may continue detecting MPE instances in the next measurement period (e.g., based on the example described with respect to FIG. 29) and / or reset the MPE detection timer and / or MPE detection counter, e.g., if the MPE detection counter is not equal to or greater than the number / amount and / or the MPE detection timer has expired. The wireless device may trigger / start / stop uplink coverage restoration signal transmission, e.g., if the MPE detection counter is equal to or greater than the number / amount and / or the MPE detection timer is running. The uplink coverage restoration signal transmission may be performed based on the examples described with respect to FIG. 31, FIG. 32, and / or FIG. 33.

[0262] FIG. 31 illustrates an example method for coverage restoration and / or coverage loss mitigation. A random access channel (RACH) can be used for uplink coverage restoration and / or uplink coverage loss mitigation. One or more uplink coverage restoration signal transmissions can be transmitted / transmitted by a wireless device 3115. The wireless device 3115 can be configured with one or more panels (e.g., antenna panels, antennas, transceiver devices, etc.) that can detect and / or mitigate uplink coverage loss. The coverage loss can be the result of compliance with one or more MPE requirements. The uplink coverage restoration signal transmissions can comprise one or more transmissions of a preamble over RACH resources.

[0263] The base station 3110 may send / transmit to the wireless device 3115 one or more messages (e.g., RRC messages) 3120 comprising configuration parameters of RACH resources for uplink coverage recovery. The RACH resources for uplink coverage recovery procedures may be configured separately or independently from the RACH resources for random access procedures (e.g., initial access, beam failure recovery, and / or handover). The RACH resources may be configured per BWP or per cell. The one or more configuration parameters of the RACH resources may include at least one of a PRACH configuration index, one or more frequency domain allocation parameters, a maximum number / amount of preamble transmissions, a power ramping step, an RA response window, one or more preambles, a number / amount of SSBs per RACH opportunity, a number / amount of preamble-based contentions per SSB, a subcarrier spacing indicator, a PRACH root sequence index, an RSRP threshold, a contention resolution timer, a CSI-RS index, and / or an SSB index. Separately or independently configuring the RACH resources for the uplink coverage recovery procedure from the RACH resources for the random access procedure can be implemented by a message (e.g., an RRC message) including a first RACH resource for the uplink coverage recovery procedure and a second RACH resource for the random access procedure. The RACH resources for the uplink coverage recovery procedure can be contention-free RACH resources dedicated to the wireless device. The RACH resources for the uplink coverage recovery procedure can be contention-based RACH resources for the wireless device.

[0264] The one or more messages may configure panel-specific RACH resources for the uplink coverage recovery procedure. The one or more messages may include configuration parameters for a first RACH resource associated with a first panel of the multiple panels associated with the wireless device 3115 and a second RACH resource associated with a second panel of the multiple panels associated with the wireless device 3115. The wireless device 3115 may determine to send / transmit an uplink coverage recovery signal / message 3135 via the first RACH resource and / or via the second RACH resource, for example, based on detecting the number / amount of MPE instances (e.g., during the time window 3125). The uplink coverage recovery signal / message 3135 may comprise a preamble for the first RACH resource and / or the second RACH resource.

[0265] The wireless device 3115 may detect the number / amount of MPE instances (e.g., during the time window 3125), for example, based on the examples described in connection with Figures 28, 29, and / or 30. In step 3130, the wireless device 3115 may trigger / initiate a RACH procedure based on the RACH resources configured for the uplink coverage recovery procedure. The wireless device 3115 may trigger / initiate the RACH procedure, for example, based on detecting the number / amount of MPE instances (e.g., after or in response to the detection). The wireless device may transmit / transmit a preamble indicating uplink coverage recovery information (e.g., 3135) via the RACH resources. The uplink coverage recovery information may include uplink coverage loss occurring in the first (or most recently used) active panel and / or uplink coverage loss not occurring in the second (or non-most recently used) active panel.

[0266] For example, if the wireless device 3115 is configured with multiple RACH resources, the wireless device 3115 may trigger a RACH procedure based on the number / quantity of MPE instances being detected in one of the multiple panels. Here, each RACH resource may be associated with a corresponding panel of the multiple panels. The wireless device 3115 may select a RACH resource from the multiple RACH resources. The selected RACH resource may be associated with an active panel of the multiple panels in which the wireless device 3115 detects no MPE instances or in which the wireless device 3115 can detect a number / quantity of MPE instances (e.g., the number / quantity may be less than a threshold based on a configuration indicated by the base station 3110). The selected RACH resource may be associated with an active panel of the multiple panels in which the wireless device 3115 can detect a number / quantity of MPE instances (e.g., the number / quantity may be greater than a threshold based on a configuration indicated by the base station 3110). The wireless device 3115 may transmit / transmit a preamble associated with the selected RACH resource. The preamble sent / transmitted over the selected RACH resource may indicate that the first active panel has uplink coverage loss (e.g., due to compliance with MPE requirements) and / or that the second active panel does not have uplink coverage loss.

[0267] In step 3145, the wireless device 3115 may monitor the PDCCH. The wireless device 3115 may monitor the PDCCH to receive a response (e.g., 3135) related to sending / transmitting the preamble. The wireless device 3135 may receive the response 3140. The response 3140 may include DCI on the control resource set and / or search space via the PDCCH. The response 3140 may be a response to the preamble. The search space and / or control resource set (e.g., based on the examples described with respect to FIG. 24 and / or FIG. 25) may be configured by the base station 3110 for uplink coverage recovery. The search space and / or control resource set for the uplink coverage recovery procedure may be configured separately and / or independently from the search space and / or control resource set for other purposes (e.g., downlink / uplink scheduling, BFR procedures, power control, slot format indication, preemption indication, etc.). The wireless device 3115 may receive the response 3140. The response 3140 (e.g., DCI) may indicate a panel that may be different from the most recent active panel. By using the panel indicated in the response 3140, the wireless device may avoid and / or minimize / reduce uplink coverage loss (e.g., based on proximity detection). Based on receiving the response 3140 (e.g., DCI), the wireless device may remove the RACH procedure (e.g., this may have been initiated in step 3130). The wireless device 3115 may repeat the transmission / transmission of the uplink coverage recovery signal / message 3135 (e.g., preamble) over the selected RACH resource and / or retransmit / retransmit the preamble and / or repeat monitoring the PDCCH for a response (e.g., 3145), for example, if the wireless device 3115 does not receive a response (e.g., response 3140).The wireless device 3115 may indicate uplink coverage loss information by transmitting / transmitting a preamble over a RACH resource based on detecting uplink coverage loss (e.g., due to compliance with MPE requirements when the wireless device detects a human body in proximity to the wireless device). The wireless device 3115 may indicate uplink coverage loss information by transmitting / transmitting a preamble over a RACH resource based on detecting uplink coverage loss on a first panel of the wireless device and / or based on not detecting uplink coverage loss on a second panel of the wireless device 3115. The base station 3110 may recognize (e.g., determine) uplink coverage loss (on one of the multiple panels of the wireless device) based, for example, on receiving a preamble over a RACH resource dedicated for uplink coverage recovery procedures. The base station can correspondingly send / transmit a message (e.g., DCI) indicating a panel switch from a first panel having uplink coverage loss to a panel without uplink coverage loss, e.g., based on receiving a preamble over the RACH resources. The procedures described herein can timely improve uplink coverage, e.g., to comply with MPE requirements based on proximity detection.

[0268] FIG. 32 shows an example method for coverage restoration and / or coverage loss mitigation. Scheduling requests (SRs) may be used for uplink coverage restoration and / or uplink coverage loss mitigation. The uplink coverage restoration signal transmission may comprise one or more transmissions of scheduling requests (SRs) over PUCCH resources. The base station 3210 may transmit / transmit one or more messages 3220 (e.g., RRC messages) comprising configuration parameters of multiple SR configurations to the wireless device 3215. Each SR configuration may be associated (or identified / indicated) with an SR ID. The one or more configuration parameters of the SR configuration may include at least one of an SR ID, an SR inhibit timer, and / or a maximum number / amount of SR transmissions. The PUCCH resources associated with the SR configuration may be indicated in the message (e.g., in a SchedulingRequestResourceConfig IE). The message (e.g., SchedulingRequestResourceConfig IE) may comprise at least one of an SR resource ID, an SR ID, a periodicity and / or offset parameter, and / or a PUCCH resource ID. The PUCCH resource ID may identify / indicate a PUCCH resource on which the wireless device 3215 may transmit / transmit at least one SR. One or more of the multiple SR configurations may be for an uplink grant request. At least one SR configuration may be dedicated for uplink coverage recovery. The at least one dedicated SR configuration may be indicated in the configuration parameters of the uplink coverage recovery procedure. The at least one dedicated SR configuration may be configured per BWP, per cell, and / or per frequency / frequency.

[0269] The one or more messages 3220 may configure panel-specific SRs configured for uplink coverage recovery. If the wireless device is equipped with multiple panels, the one or more RRC messages may include configuration parameters for a first SR configuration associated with a first panel of the multiple panels and a second SR configuration associated with a second panel of the multiple panels. The wireless device 3215 may determine to transmit / transmit the uplink coverage recovery signal 3235 via a first PUCCH resource of the first SR configuration or a second PUCCH resource of the second SR configuration.

[0270] The wireless device 3215 may detect / determine the number / amount of MPE instances (e.g., during the time window 3225). The wireless device 3225 may determine / determine the number / amount of MPE instances, for example, based on the examples described with respect to FIG. 28, FIG. 29, and / or FIG. 30. In step 3230, the wireless device 3215 may trigger / initiate an SR procedure based on an SR configuration set for uplink coverage recovery. The wireless device 3215 may trigger / initiate the SR procedure, for example, based on detecting the number / amount of MPE instances (e.g., during the time window 3225). The wireless device 3215 may transmit / transmit an SR 3235 (e.g., a positive SR) indicating uplink coverage recovery information via the PUCCH resource. The uplink coverage recovery information may include uplink coverage problems occurring on the first (or most recent) active panel and / or uplink coverage problems not occurring on the second (or less recent) active panel.

[0271] The wireless device may trigger an SR procedure (e.g., at 3230) based on the number / amount of MPE instances being detected in one of the multiple panels, for example, when the wireless device 3215 is configured with multiple SR configurations. Each SR configuration may be associated with a corresponding panel of the multiple panels. The wireless device 3215 may select an SR configuration from the multiple SR configurations. The selected SR configuration may be associated with an active panel of the multiple panels in which the wireless device detects no MPE instances or in which the wireless device detects / determines the number / amount of MPE instances (e.g., the number / amount may be below a threshold). The selected SR configuration may be associated with an active panel of the multiple panels in which the wireless device detects / determines the number / amount of MPE instances (e.g., the number / amount may be greater than a threshold). The wireless device may transmit / transmit an SR 3235 via a PUCCH resource associated with the selected SR configuration. The SR being transmitted / transmitted via the PUCCH resources of the selected SR configuration may indicate that the first active panel has uplink coverage loss (e.g., due to compliance with MPE requirements) and / or that the second active panel does not have uplink coverage loss.

[0272] The wireless device 3215 may monitor the PDCCH (e.g., based on or after transmitting the SR 3235). The wireless device may monitor the PDCCH, for example, to receive a response 3240 to the SR. The response 3240 may include a DCI. The wireless device 3215 may receive the response 3240 via the PDCCH on a dedicated control resource set and / or a dedicated search space. The response 3240 (e.g., a DCI) may indicate a panel that may be different from the most recent active panel. The wireless device 3215 may, for example, avoid and / or reduce / minimize uplink coverage loss (e.g., based on proximity detection) by using the indicated panel (e.g., after receiving the response 3240). In step 3245, the wireless device 3215 may remove the triggered SR (e.g., cancel a configured / scheduled retransmission of the SR 3235), for example, based on receiving the response 3240. The wireless device 3215 may, for example, repeat transmitting / transmitting an SR over the PUCCH resources of the selected SR configuration and / or monitoring the PDCCH for a response based on not receiving a response 3240 (e.g., based on not receiving a DCI in response to the SR 3235). The wireless device 3215 may indicate uplink coverage loss information by, for example, transmitting / transmitting an SR over the PUCCH resources based on detecting uplink coverage loss (e.g., due to compliance with MPE requirements if the wireless device detects a human body in proximity to the wireless device). The wireless device 3215 may indicate uplink coverage loss information by, for example, transmitting / transmitting an SR over the PUCCH resources based on detecting uplink coverage loss on a first panel of the wireless device and not detecting uplink coverage loss on a second panel of the wireless device. The base station 3210 may recognize (e.g., determine) an uplink coverage loss (e.g., in one of multiple panels of a wireless device) based on, for example, receiving an SR via a PUCCH resource of an SR configuration dedicated for uplink coverage recovery.The base station 3210 can correspondingly send / transmit a message (e.g., DCI, RRC, MAC CE, etc.) indicating a panel switch from a first panel having uplink coverage loss to a second panel without uplink coverage loss, e.g., based on receiving the SR via the PUCCH resource. As described herein, improvements can result in reduced uplink coverage restoration signaling and / or latency (e.g., due to compliance with MPE requirements based on proximity detection).

[0273] The base station 3210 may send / transmit one or more messages 3220 (e.g., RRC messages) comprising configuration parameters of multiple SRS resources (or SRS resource sets) to the wireless device 3215. The one or more configuration parameters of the SRS resources may include at least one of an SRS ID, a number of SRS ports, one or more transmission comb parameters, a resource mapping indicator, one or more frequency domain parameters, a resource type indicator, an SRS sequence ID, and / or one or more SRS spatial relationship information parameters (e.g., a reference signal index, a BWP ID, and a cell ID). One or more SRS resources may be dedicated for uplink transmission based on uplink coverage loss (e.g., due to compliance with MPE requirements). Dedicated SRS resources for uplink transmission based on uplink coverage loss may be configured per cell and / or per frequency / frequency per configured BWP. The dedicated SRS resources (or resource sets) for uplink transmission may be configured with frequency radio resources smaller than the frequency radio resources of SRS for normal uplink transmission (e.g., without uplink coverage loss). A dedicated SRS resource (or resource set) for uplink transmission may be configured with a smaller number / amount of antenna ports than an SRS for normal uplink transmission (e.g., without uplink coverage loss). A dedicated SRS resource (or resource set) for uplink transmission may be configured with a smaller number / amount of antenna ports than an SRS for normal uplink transmission (e.g., without uplink coverage loss).

[0274] The wireless device 3215 may detect / determine the number / amount of MPE instances (e.g., during time window 3225), for example, based on the examples described in connection with FIG. 28, FIG. 29, and / or FIG. 30. The wireless device 3215 may transmit / transmit a first SRS 3235 configured for uplink transmission, for example, based on an uplink coverage loss (e.g., due to compliance with MPE requirements) (e.g., after or in response to detecting / determining the number / amount of MPE instances). The transmission of the first SRS may indicate that the wireless device 3215 has experienced an uplink coverage loss. The wireless device 3215 may prioritize a first SRS transmission over a second SRS, for example, based on the first SRS transmission overlapping in time with the second SRS transmission (e.g., a non-periodic SRS triggered by DCI, or a periodic SRS for CSI acquisition or beam management, or a semi-persistent SRS triggered by MAC CE). Prioritizing the first SRS transmission over the second SRS may include reducing the transmission power of the second SRS, dropping the transmission of the second SRS, and / or transmitting / transmitting the first SRS.

[0275] For example, if the wireless device 3215 is configured with multiple SRS resources, the wireless device 3215 may transmit / transmit one or more of the multiple SRS resources based on the number / quantity of MPE instances detected / determined in one or more of the multiple panels. Each SRS resource may be associated with a corresponding panel among the multiple panels. The wireless device 3215 may select an SRS from the multiple SRS resources. The selected SRS resource may be associated with an active panel among the multiple panels in which the wireless device 3215 does not detect one or more MPE instances, or in which the wireless device 3215 detects a number / quantity of MPE instances (e.g., the number / quantity may be less than a threshold). The selected SRS resource may be associated with an active panel among the multiple panels in which the wireless device 3215 can detect / determine a number / quantity of MPE instances (e.g., the number / quantity may be greater than a threshold). The wireless device 3215 may transmit / transmit the SRS via the selected SRS resource. The SRS sent / transmitted via the selected SRS resource may indicate that the first active panel has uplink coverage loss (e.g., due to compliance with MPE requirements) and / or that the second active panel has no uplink coverage loss. The base station 3210 may recognize (e.g., determine) the uplink coverage loss occurring in the active panel, for example, based on receiving the SRS 3235. The base station 3210 may send / transmit a message / command instructing an active panel switch, for example, based on receiving the SRS 3235.

[0276] The wireless device may trigger transmission of assistance information comprising uplink coverage loss information. The wireless device may trigger transmission of the assistance information including the uplink coverage loss information, for example, based on detecting / determining the number / quantity of MPE instances (e.g., based on the examples described with respect to Figures 28, 29, and / or 30). The wireless device may send / transmit a message (e.g., an RRC message) including the assistance information (e.g., a UEAssistanceInformation IE) and the uplink coverage loss information. The uplink coverage loss information may include at least one of a first ID indicating a panel with uplink coverage loss, a second ID indicating a panel without uplink coverage loss, a P-MPR value of the currently active panel, a combined value of P-MPR and RSRP of the currently active panel, a BWP ID indicating a BWP with uplink coverage loss, and a cell ID indicating a cell with uplink coverage loss. The base station may send / transmit a message / command (e.g., an RRC message, a MAC CE, and / or a DCI) instructing an active panel switch based on, for example, receiving assistance information (e.g., a UEAssistanceInformation IE) from the wireless device. The uplink coverage loss information may include at least one of: a first ID identifying a first panel, a P-MPR value associated with the first panel, an RSRP value associated with the first panel, a joint P-MPR value and an RSRP value of the first panel, at least a second ID identifying at least a second panel, a P-MPR value associated with the at least second panel, an RSRP value associated with the at least second panel, a joint P-MPR value, and an RSRP value of the at least second panel. The base station may send / transmit a message / command (e.g., an RRC message, a MAC CE, and / or a DCI) instructing an active panel switch based on, for example, receiving assistance information (e.g., a UEAssistanceInformation IE) from the wireless device.

[0277] FIG. 33 shows an example method for transmission via configuration grant based on coverage loss. If a wireless device 3315 may detect uplink coverage loss (e.g., due to compliance with MPE requirements), the base station 3310 may transmit / transmit one or more messages 3320 (e.g., one or more RRC messages) to the wireless device 3315. The one or more messages 3320 may include configuration parameters of multiple configuration grants (CGs) for uplink coverage recovery (CR). Each CG may be associated with and / or identified / indicated by a CG ID. The one or more configuration parameters of the CG may include at least one of a frequency hopping indicator, a DMRS configuration, an indicator of an MCS table and transmit form precoder, a UCI on a PUSCH configuration, a resource allocation indication, an RBG size, a power control loop indicator, a number / amount of HARQ processes, a number / amount of repetitions, a sequence of repeated RVs, a periodicity, one or more time domain resources, one or more frequency domain resources, etc. One or more of the multiple CGs may be dedicated for uplink transmissions based on uplink coverage loss (e.g., due to compliance with MPE requirements). The dedicated CGs for uplink transmissions based on uplink coverage loss may be configured per BWP, per cell, and / or per frequency / frequency. The dedicated CGs for uplink transmissions may be configured wi...

Claims

1. 1. A method comprising: receiving, by a wireless device, an exposure reporting configuration including at least one maximum permissible exposure (MPE) threshold; determining an uplink transmit power reduction value to meet the exposure requirement; and transmitting a power headroom report (PHR) based on the threshold meeting the MPE threshold; The power headroom report (PHR) may include: a first field indicating a PHR value associated with the cell; a second field indicating the uplink transmission power reduction value; a third field indicating a maximum transmit power.

2. Determining the uplink transmit power reduction value includes: a reference signal received power associated with a first panel of the cell; a transmission signal format for transmission through said first panel; or The method of claim 1 , comprising determining the uplink transmit power reduction value based on at least one of a proximity detection associated with the first panel.

3. The PHR is a PHR value associated with a first panel of said cell; the index of the first panel; a maximum reduction in transmit power associated with the first panel; a maximum output amount of transmit power associated with the first panel; or The method of claim 1 , further comprising at least one of an uplink duty cycle value associated with the first panel.

4. 2. The method of claim 1, further comprising: determining a PHR value associated with a first panel of the cell based on a maximum transmit power reduction (MPR), the MPR being associated with at least one of a modulation order or a bandwidth.

5. the maximum allowable reduction in transmit power (A-MPR) indicated by the base station, or 2. The method of claim 1, further comprising: determining a PHR value associated with the first panel of the cell based on at least one of a power-controlled MPR (P-MPR) associated with proximity detection of the first panel of the cell.

6. The PHR is a Medium Access Control (MAC) Control Element (CE) that includes a number of octets; the first field is a power headroom (PH) field corresponding to 6 bits of a first octet of the plurality of octets; the second field includes two bits of a second octet of the plurality of octets; 2. The method of claim 1, wherein the third field corresponds to the remaining six bits of the second octet of the plurality of octets.

7. The PHR further includes a fourth field indicating a power state; 7. The method of claim 6, wherein the fourth field corresponds to one bit of the remaining two bits of the first octet of the plurality of octets.

8. 8. The method of claim 7, wherein a first value of the fourth field indicates a power state, and the uplink transmit power reduction value corresponds to a power backoff value of the power state.

9. The transmitting of the PHR includes: The method of claim 1 , comprising triggering the PHR based on the uplink transmit power reduction value being greater than the MPE threshold.

10. The method of claim 9 , further comprising canceling the triggered PHR after transmitting the PHR.

11. 2. The method of claim 1, wherein the PHR includes a single-entry PHR Medium Access Control (MAC) Control Element (CE) associated with a Logical Channel Identifier (LCID) value of a MAC subheader.

12. receiving a configuration including physical uplink control channel (PUCCH) resources associated with an MPE report; transmitting a scheduling request via the PUCCH resource; The method of claim 1 , further comprising: receiving an uplink grant for transmission of the PHR based on the scheduling request.

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

14. 1. A system comprising: A wireless device configured to implement the method according to any one of claims 1 to 12; and a computing device configured to transmit the exposure reporting configuration.

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

Images