Timing Advance Reporting in Non-Terrestrial Networks

Abstract

Timing Advance (TA) reports may be used in wireless communications. TA report information may be provided by a wireless device to align timing between the wireless device and a base station, as in non-terrestrial networks. The TA report information may be transmitted via a Scheduling Report (SR) procedure, a Buffer Status Report (BSR) procedure, and / or a Random Access (RA) procedure. To avoid unnecessary transmission of TA report information, the TA report may be canceled based on one or more of receiving a timing offset and / or expiry of a timer.

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims the benefit of U.S. Provisional Patent Application No. 63 / 250,360, filed September 30, 2021. The above-referenced application is incorporated herein by reference in its entirety. [Background technology]

[0002] Timing advance (TA) is used by a wireless device while the wireless device is communicating with a base station. The wireless device determines a device-specific TA value that applies specifically to the wireless device. The wireless device transmits information associated with the device-specific TA value to the base station. Summary of the Invention

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

[0004] A wireless device may be synchronized (e.g., time-aligned) with a base station by using a timing advance (TA). As in non-terrestrial networks (NTNs), in at least some wireless communications, TA report information associated with a current TA (e.g., a device-specific TA) may be transmitted (e.g., by a wireless device) via a TA report procedure. The TA report information may be used (e.g., by a base station) to determine a timing offset. The timing offset may be provided to the wireless device to facilitate determination of an updated TA and / or uplink timing (e.g., either / both of which may be used by the wireless device for transmitting uplink signals). Rather than continuing the TA report (e.g., indefinitely and / or after the TA is no longer valid), a timer may be started based on the TA report procedure being triggered. The TA report procedure may be completed and / or canceled, for example, based on receiving a timing offset and / or expiration of a timer. In this manner, a wireless device may avoid unnecessarily transmitting TA report information, thus reducing power consumption and / or reducing interference to other wireless devices. Additionally or alternatively, a scheduling request (SR) procedure for TA reporting can be used to facilitate TA reporting. For example, at least one SR configuration parameter may correspond to TA reporting such that SR can be used to transmit TA report information without triggering a buffer status report (BSR) procedure. Transmitting TA report information using an SR procedure may provide advantages such as reduced overhead and / or reduced delay in transmitting TA report information.

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

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

[0007] [Figure 1A] FIG. 1A illustrates an embodiment of a communication network. [Figure 1B] FIG. 1B illustrates an embodiment of a communication network. [Figure 2A] FIG. 2A illustrates an exemplary user plane. [Figure 2B] FIG. 2B shows an example of a control plane configuration. [Figure 3] FIG. 3 shows an example of the protocol layers. [Figure 4A] FIG. 4A illustrates an example of a downlink data flow in a user plane configuration. [Figure 4B] FIG. 4B illustrates an example format of a Medium Access Control (MAC) subheader of a MAC Protocol Data Unit (PDU). [Figure 5A] FIG. 5A shows an example of downlink channel mapping. [Figure 5B] FIG. 5B shows an example of uplink channel mapping. [Figure 6] FIG. 6 illustrates an example of Radio Resource Control (RRC) states and RRC state transitions. [Figure 7] FIG. 7 shows an example of a frame configuration. [Figure 8] FIG. 8 illustrates an exemplary resource configuration for one or more carriers. [Figure 9] FIG. 9 shows an example of the configuration of the bandwidth portion (BWP). [Figure 10A] FIG. 10A illustrates an exemplary carrier aggregation configuration based on component carriers. [Figure 10B] FIG. 10B shows an example group of cells. [Figure 11A] FIG. 11A illustrates an example mapping of one or more synchronization signal / physical broadcast channel (SS / PBCH) blocks. [Figure 11B] FIG. 11B illustrates an example mapping of one or more channel state information reference signals (CSI-RS). [Figure 12A]FIG. 12A shows an example of a downlink beam management procedure. [Figure 12B] FIG. 12B shows an example of an uplink beam management procedure. [Figure 13A] FIG. 13A shows an example of a four-step random access procedure. [Figure 13B] FIG. 13B shows an example of a two-step random access procedure. [Figure 13C] FIG. 13C shows an example of a two-step random access procedure. [Figure 14A] FIG. 14A shows an example of a control resource set (CORESET) configuration. [Figure 14B] FIG. 14B illustrates an example of mapping of control channel elements to resource element groups (CCE-to-REG). [Figure 15A] FIG. 15A illustrates an example of communication between a wireless device and a base station. [Figure 15B] FIG. 15B illustrates exemplary elements of a computing device that may be used to implement any of the various devices described herein. [Figure 16A] FIG. 16A shows an example of uplink and downlink signal transmission. [Figure 16B] FIG. 16B shows an example of uplink and downlink signal transmission. [Figure 16C] FIG. 16C shows an example of uplink and downlink signal transmission. [Figure 16D] FIG. 16D shows an example of uplink and downlink signal transmission. [Figure 17] FIG. 17 shows examples of various downlink control information (DCI) formats. [Figure 18] FIG. 18 shows an example of a physical downlink shared channel (PDSCH) processing time. [Figure 19] FIG. 19 shows an example of the setup / processing time for the Physical Uplink Shared Channel (PUSCH). [Figure 20]FIG. 20 shows an example of a random access (RA) procedure. [Figure 21] FIG. 21 shows various non-terrestrial network (NTN) embodiments. [Figure 22] FIG. 22 shows exemplary communications in an NTN. [Figure 23] FIG. 23 shows an example of various propagation delays. [Figure 24] FIG. 24 shows an example of a timing advance (TA) report in NTN. [Figure 25] FIG. 25 shows an example of a TA report. [Figure 26] FIG. 26 shows an exemplary TA report. [Figure 27] FIG. 27 shows an example of a TA report. [Figure 28] FIG. 28 shows an example of a TA report. [Figure 29] FIG. 29 shows an example of a TA report. [Figure 30] FIG. 30 shows an example of a TA report. [Figure 31] FIG. 31 shows an example of a TA report. DETAILED DESCRIPTION OF THE INVENTION

[0008] The accompanying drawings and description provide examples. It should be understood that the examples shown in the drawings and / or description are non-exclusive, and that the features shown and described may be practiced in other embodiments. Examples are provided for the operation of a wireless communication system that may be used in the field of multi-carrier communication systems. More specifically, the techniques disclosed herein may relate to small data transmission (SDT) procedures for wireless communication.

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

[0010] The wireless device 106 may communicate with the RAN 104 via wireless communication over the 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 over the air interface may be referred to as the downlink and / or downlink communication direction. The communication direction from the wireless device 106 to the RAN 104 over the air interface may be referred to as the uplink and / or uplink communication direction. Downlink transmissions may be separated and / or distinguished from uplink transmissions based on, for example, at least one of frequency division duplexing (FDD), time division duplexing (TDD), any other duplexing scheme, and / or one or more combinations thereof.

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

[0012] The RAN 104 may include one or more base stations (not shown). As used throughout, the term “base station” may include one or more of a base station, node, Node B (NB), Evolved Node B (eNB), gNB, ng-eNB, relay node (e.g., integrated access and backhaul (IAB) node, etc.), donor node (e.g., donor eNB, donor gNB, etc.), access point (e.g., Wi-Fi access point, etc.), transmit / receive point (TRP), computing device, wireless communication enabled device, or other device capable of transmitting and / or receiving signals. A base station may include one or more of each of the above-listed elements. For example, a base station may include one or more TRPs. As other non-limiting examples, a base station may include, for example, one or more of a Node B (e.g., associated with Universal Mobile Telecommunications System (UMTS) and / or third-generation (3G) standards), an 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 coupled to one or more Remote Radio Heads (RRH), a repeater 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 other suitable wireless communication standards), other generation base stations, and / or any combination thereof. A base station may include one or more devices, such as at least one base station central device (e.g., a gNB central unit (gNB-CU)) and at least one base station distribution device (e.g., a gNB distribution unit (gNB-DU)).

[0013] A base station (e.g., in the RAN 104) may include one or more sets of antennas for communicating wirelessly (e.g., over the air interface) with wireless devices 106. One or more base stations may include a set of antennas (e.g., a set of three or any other number of sets) 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 cells of a base station (e.g., alone or in combination with other cells) may provide / configure wireless coverage to wireless devices 106 over a wide geographic area to support wireless device mobility. A base station including three sectors (e.g., or n sectors, where n refers to any 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., an n-sector base station).

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

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

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

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

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

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

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

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

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

[0023] A base station (e.g., gNB 160 and / or ng-eNBs 162) may be connected to the CN 152 (e.g., 5G CN) via a first interface (e.g., an NG interface) and may be connected to other base stations via a second interface (e.g., an Xn interface). The NG and Xn interfaces may be established using direct physical connections and / or indirect connections over an underlying transport network, such as an Internet Protocol (IP) transport network. A base station (e.g., gNB 160 and / or ng-eNBs 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): A user plane may handle data of interest to users. A control plane may handle signaling messages of interest to network elements.

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

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

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

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

[0028] 1A and / or 150 of FIG. 1BA may include any quantity / number 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 one or more of the above types of devices may be referenced herein (e.g., UEs, wireless devices, computing devices, etc.), it should be understood that any device herein may include any one or more of the above types of devices or similar devices. The communication networks, and any other networks referenced herein, may include LTE networks, 5G networks, satellite networks, and / or any other networks for wireless communication (e.g., any 3GPP network and / or any non-3GPP network). Although the apparatus, systems, and / or methods described herein may generally be described as being implemented in one or more apparatuses (e.g., radio apparatus, base stations, eNBs, gNBs, computing devices, etc.) in one or more networks, it will be understood that one or more features and steps may be implemented in any device and / or any network.

[0029] FIG. 2A illustrates an 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 of a 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 that may be between wireless device 210 and base station 220. The protocol stacks illustrated in FIG. 2A and FIG. 2B may be substantially the same as or similar to those used for the Uu interface between wireless device 156A and base station 160A shown in FIG. 1B, for example.

[0030] A user plane configuration (e.g., an NR user plane protocol stack) may include multiple layers (e.g., five 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 the upper layers of the protocol stack and may correspond to Layer 1 of the Open Systems Interconnection (OSI) model. Protocol layers above PHY 211 may include a 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. 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 211 may correspond to Layer 2 or the data link layer of the OSI model. One or more of the four protocol layers above PHY 221 may correspond to Layer 2 or the data link layer of the OSI model.

[0031] FIG. 3 illustrates 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., SDAPS 215 and 225 shown in FIGS. 2A and 3) may perform quality of service (QoS) flow processing. A wireless device (e.g., wireless device 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 CN's UPF (e.g., UPF 158B) 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 / undemoping between one or more QoS flows 310 and radio bearers 320 may be determined by the SDAP 225 of the base station 220. The SDAP 215 of the wireless device 210 may be informed of the mapping between the QoS flows 310 and radio bearers 320 via reflected mapping and / or control signaling received from the base station 220. For reflected mapping, the SDAP 225 of the base station 220 may mark downlink packets with a QoS flow indicator (QFI) that may be monitored / detected / identified / indicated / observed by the SDAP 215 of the wireless device 210 to determine the mapping / undemoping between one or more QoS flows 310 and radio bearers 320.

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

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

[0034] The RLC layer (e.g., RLC 213 and 223) may perform segmentation, retransmission via automatic repeat request (ARQ), and / or removal of duplicate data units received from the MAC layer (e.g., MAC 212 and 222, respectively). The RLC layer (e.g., RLC 213 and 223) may support multiple transmission modes (e.g., three transmission modes: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM)). The RLC layer may perform one or more of the indicated 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 period). The RLC layer (e.g., RLC 213 and 223) may provide / configure RLC channels as a service to the PDCP layer (e.g., PDCP 214 and 224, respectively) as shown in FIG. 3.

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

[0036] The PHY layer (e.g., PHYs 211 and 221) may 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 the air interface). The digital and / or analog signal processing functions may include, for example, encoding / decoding and / or modulation / demodulation. The PHY layer (e.g., PHYs 211 and 221) may also perform multi-antenna mapping. The PHY layer (e.g., PHYs 211 and 221) may provide / configure one or more transport channels (e.g., transport channel 350) as services to the MAC layer (e.g., MACs 212 and 222, respectively).

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

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

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

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

[0041] One or more MAC Control Elements (CEs) may be added or inserted into a MAC PDU by a MAC layer, such as MAC 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 at the beginning of a MAC PDU for downlink transmission (as shown in FIG. 4B). One or more MAC CEs may be inserted / appended at the end of a MAC PDU for uplink transmission. MAC CEs may be used for in-band control signaling. Examples of 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 of a format similar to that described in MAC subheader for MAC SDUs and may be identified with a reserved value in the LCID field indicating the type of control information contained in the corresponding MAC CE.

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

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

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

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

[0046] The 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 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.

[0047] One or more channels (e.g., logical channels, transport channels, physical channels, etc.) may be used to perform functions associated with a control plane protocol stack (e.g., an NR control plane protocol stack). FIG. 2B shows an example of a control plane configuration (e.g., an NR control plane protocol stack). In FIG. 2B, the control plane configuration (e.g., an NR control plane protocol stack) may use one or more substantially identical / similar protocol layers (e.g., PHYs 211 and 221, MACs 212 and 222, RLCs 213 and 223, and PDCPs 214 and 224) as an exemplary user plane configuration (e.g., an NR user plane protocol stack). The similar four protocol layers may include PHYs 211 and 221, MACs 212 and 222, RLCs 213 and 223, and PDCPs 214 and 224. 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), for example, instead of having SDAPs 215 and 225. The control plane configuration may include an AMF 230 that includes the NAS protocol 237.

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

[0049] The RRC layers 216 and 226 may provide / configure control plane functionality between the wireless device 210 and the base station 220, and / or more broadly, between the wireless device 210 and the RAN (e.g., the base station 220). The RRC layers 216 and 226 may provide / configure control plane functionality between the wireless device 210 and the base station 220 via signaling messages, which may be referred to as RRC messages. The RRC messages may be transmitted / conveyed 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: broadcast of system information related to the AS and NAS; paging initiated by the CN or RAN; establishment, maintenance, and release of an RRC connection between the wireless device 210 and the RAN (e.g., base station 220); security functions including key management; establishment, configuration, maintenance, and release of signaling and data radio bearers; mobility functions; QoS management functions; wireless device measurement reports (e.g., wireless device measurement reports) and control of reports; detection and recovery from radio link failure (RLF); and / or NAS message transfer functions. As part of establishing an RRC connection, the RRC layers 216 and 226 may establish an RRC context, which may involve configuration of parameters for communications between the wireless device 210 and the RAN (e.g., base station 220).

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

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

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

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

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

[0055] The tracking area may be used to track a wireless device (e.g., track the location of a wireless device at the CN level). A CN (e.g., CN 102, 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, e.g., to provide the wireless device with a new UE registration area if the wireless device moves (e.g., via cell reselection) to a cell associated with a TAI that is not included in the list of TAIs associated with the UE registration area.

[0056] The RAN area may be used to track a wireless device (e.g., its location at the RAN level). For a wireless device in an RRC inactive state (e.g., RRC inactive 604), the wireless device may be assigned / provisioned / configured 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. If the wireless device moves (e.g., via cell reselection) to a cell that is not included in the RAN notification area assigned / provisioned / configured to the wireless device, the notification area may be updated in the RAN to update the RAN notification area of the wireless device.

[0057] A base station that stores the RRC context for a wireless device or a last serving base station for a wireless device may be referred to as an anchor base station. The anchor base station may maintain the RRC context for the wireless device 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).

[0058] 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 gNB DUs). The base station central unit (CU) may be coupled to one or more base station distributed units (DUs) using an F1 interface (e.g., an F1 interface defined in the NR configuration). The base station CU may include an RRC layer, a PDCP layer, and an SDAP layer. The base station distributed unit (DU) may include an RLC layer, a MAC layer, and a PHY layer.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0073] Downlink BWP switching 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). Uplink BWP switching may refer to switching an active uplink BWP from a first uplink BWP to a second uplink BWP (e.g., the second uplink BWP is activated and the first uplink BWP is deactivated). Downlink and uplink BWP switching may occur independently (e.g., in paired spectrum / spectrum). Downlink and uplink BWP switching may occur simultaneously (e.g., in unpaired spectrum / spectrum). Switching between configured BWPs may occur based on, for example, RRC signaling, DCI signaling, expiration of a BWP inactivity timer, and / or initiation of random access.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0091] A wireless device may assume that one or more SS / PBCH blocks transmitted / communicated with the same SS / PBCH block index are approximately co-located (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., blocks within a half frame) may be transmitted / communicated in spatial directions (e.g., using different beams across a cell's coverage area). A first SS / PBCH block may be transmitted / communicated in a first spatial direction using a first beam, a second SS / PBCH block may be transmitted / communicated in a second spatial direction using a second beam, a third SS / PBCH block may be transmitted / communicated in a third spatial direction using a third beam, and a fourth SS / PBCH block may be transmitted / communicated in a fourth spatial direction using a fourth beam.

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

[0093] The CSI-RS may be transmitted / communicated by a base station and used by a wireless device to acquire / obtain / 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 / communicate a CSI report to the base station (e.g., based on periodic CSI reports, semi-persistent CSI reports, and / or aperiodic CSI reports). The base station may perform link adaptation using feedback (e.g., estimated downlink channel conditions) provided by the wireless device.

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

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

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

[0097] A downlink DM-RS may be transmitted / conveyed by a base station and received / used by a wireless device for channel estimation. The downlink DM-RS may be used for coherent demodulation of one or more downlink physical channels (e.g., PDSCH). A network (e.g., an NR network) may support one or more variable and / or configurable DM-RS patterns for data demodulation. At least one downlink DM-RS configuration may support a frontloaded DM-RS pattern. The frontloaded DM-RS may be mapped onto one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). A base station may semi-statically configure a wireless device with the number / quantity (e.g., maximum number / quantity) 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., for 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. A base station may transmit / convey a downlink DM-RS and a corresponding PDSCH, for example, using the same precoding matrix. A wireless device may use one or more downlink DM-RSs for coherent demodulation / channel estimation of the PDSCH.

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

[0099] The PDSCH may include one or more layers. A wireless device may assume that at least one symbol with a DM-RS is present on one or more layers of the PDSCH. Higher layers may configure one or more DM-RSs for the PDSCH (e.g., up to three DM-RSs for the PDSCH). A downlink PT-RS may be transmitted / conveyed by a base station and may be used by a wireless device, for example, for phase noise compensation. Whether a downlink PT-RS is present may depend on 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, if configured, may be associated with one or more DCI parameters, including at least the MCS. A network (e.g., an NR network) may support multiple PT-RS densities defined in the time and / or frequency domains. The frequency domain density (configuration / if present) may be associated with at least one configuration of the scheduled bandwidth. The wireless device may assume the same precoding for DM-RS ports and PT-RS ports. The quantity / number of PT-RS ports may be smaller than the quantity / number of DM-RS ports in the scheduled resources. The downlink PT-RS may be configured / assigned / restricted with a scheduled time / frequency duration for the wireless device. The downlink PT-RS may be transmitted / conveyed via symbols, for example, to facilitate phase tracking at the receiver.

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

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

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

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

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

[0105] FIG. 11B shows an example of mapping one or more CSI-RSs. The CSI-RSs may be mapped in the time domain and the frequency domain. Each rectangular block shown in FIG. 11B may correspond to a resource block (RB) in the bandwidth of a cell. A base station may transmit / convey one or more RRC messages including CSI-RS resource configuration parameters indicating one or more CSI-RSs. The one or more parameters may be configured by higher layer signaling (e.g., RRC and / or MAC signaling) for CSI-RS resource configuration. The one or more parameters may include at least one of a CSI-RS resource configuration identity, a number of CSI-RS ports, a CSI-RS configuration (e.g., symbol and resource element (RE) location within a subframe), a CSI-RS subframe configuration (e.g., subframe location, offset, and radio frame periodicity), a CSI-RS power parameter, a CSI-RS sequence parameter, a code division multiplexing (CDM) type parameter, a frequency density, a transmit comb, a 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.

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

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

[0108] A wireless device may determine / evaluate (e.g., measure) the channel quality of one or more beam pair links, for example, in a beam management procedure. The beam pair link may include a Tx beam of the base station and an Rx beam of the wireless device. The Tx beam of the base station may transmit / convey downlink signals, and the Rx beam of the wireless device may receive downlink signals. The wireless device may transmit / convey 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 identifications (e.g., beam index, reference signal index, or the like), RSRP, precoding matrix indicator (PMI), channel quality indicator (CQI), and / or rank indicator (RI).

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

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

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

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

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

[0114] FIG. 13A shows an example of a 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 transmit / convey a configuration message 1310 to a wireless device, for example, 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 include a preamble (or random access preamble). The first message (e.g., Msg 1 1311) may also be referred to as a preamble. The second message (e.g., Msg 2 1312) may be included as a random access response (RAR). The second message (eg, Msg 2 1312) may be called RAR.

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

[0116] 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 transmitting 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 quantity / number of SS / PBCH blocks mapped to the PRACH opportunities and / or the quantity / number of preambles mapped to the SS / PBCH blocks.

[0117] One or more RACH parameters provided / configured / included in the configuration message 1310 may be used to determine the uplink transmit power of the first message (e.g., 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 of the preamble transmission). There may be one or more power offsets indicated by the one or more RACH parameters. The one or more RACH parameters may indicate a power ramping step, a power offset between SSB and CSI-RS, a power offset between the transmission of the first message (e.g., Msg 1 1311) and the third message (e.g., Msg 3 1313), and / or a power offset value between preamble groups. The one or more RACH parameters may indicate one or more thresholds 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 complementary uplink (SUL) carrier), for example.

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

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

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

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

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

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

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

[0125] FIG. 13B illustrates a two-step random access procedure. The two-step random access procedure may include a two-step contention-free random access procedure. Similar to the four-step contention-based random access procedure, the base station may transmit / convey 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 transmitting two messages: a first message (e.g., Msg 1 1321) and a second message (e.g., Msg 2 1322). The first message (e.g., Msg 1 1321) and the second message (e.g., Msg 2 1322) may be similar 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 (eg, Msg 3 1313) and / or the fourth message (eg, Msg 4 1314).

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

[0127] The wireless device may start a time window (e.g., ra-Response window) for monitoring the PDCCH for RAR, for example, after (e.g., based on or in response to) transmitting (e.g., transmitting) a preamble. The base station may configure the wireless device with one or more beam failure recovery parameters, such as a separate time window and / or a separate PDCCH, in a search space indicated by an RRC message (e.g., recoverySearchSpaceId). The base station may configure one or more beam failure recovery parameters, for example, in association with a beam failure recovery request. The separate time window for monitoring the PDCCH and / or RAR may be configured to start after transmitting (e.g., transmitting) the beam failure recovery request (e.g., the window may start any number of symbols and / or slots after transmitting (e.g., transmitting) the beam failure recovery request). The wireless device may monitor for PDCCH transmissions addressed to a Cell RNTI (C-RNTI) on the search space. During a two-step (e.g., contention-free) random access procedure, a wireless device may determine that the random access procedure is successful after (e.g., based on or in response to) sending (e.g., 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 including a preamble identifier corresponding to a preamble transmitted / communicated by the wireless device and / or the RAR includes a MAC sub-PDU having the preamble identifier. The wireless device may determine the response as an indication of an acknowledgment to the SI request.

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

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

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

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

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

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

[0134] The downlink control signaling may include at least one of a downlink scheduling assignment, an uplink scheduling grant indicating uplink radio resources and / or transport formats, slot format information, a preemption indication, a power control command, and / or any other suitable signaling. A wireless device may receive the downlink control signaling in a payload transmitted / conveyed via a PDCCH by a base station. The payload transmitted / conveyed 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.

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

[0136] DCI messages may be used for various purposes. The purpose may be indicated by the type of RNTI used to scramble the CRC parity bits. A DCI with the CRC parity bits scrambled with the 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 the CRC parity bits scrambled with the 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 the CRC parity bits scrambled with the Random Access RNTI (RA-RNTI) may indicate a Random Access Response (RAR). A DCI with the CRC parity bits scrambled with the Cell RNTI (C-RNTI) may indicate a unicast transmission of dynamic scheduling and / or a random access of PDCCH order trigger. A DCI with CRC parity bits scrambled with the Temporary Cell RNTI (TC-RNTI) may indicate contention resolution (e.g., Msg 3 similar to Msg 3 1313 shown in FIG. 13A). Encodings of other RNTIs configured by the base station for the wireless device include a configured scheduling RNTI (CS RNTI), transmit power control PUCCH RNTI (TPC PUCCH-RNTI), transmit power control PUSCH RNTI (TPC-PUSCH-RNTI), transmit power control SRS RNTI (TPC-SRS-RNTI), Interruption RNTI (INT-RNTI), slot format indication RNTI (SFI-RNTI), semi-persistent CSI RNTI (SP-CSI-RNTI), modulation and coding scheme Cell RNTI (MCS-C RNTI), and / or the like.

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

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

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

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

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

[0142] In FIG. 14B, the wireless device may determine time-frequency resources of the CORESET based on one or more RRC messages. The wireless device may determine CCE-to-REG mapping (e.g., interleaved or non-interleaved, and / or mapping parameters) of the CORESET, for example, based on configuration parameters of the CORESET. The wireless device may determine several (e.g., up to 10) search space sets configured on / for the CORESET, for example, based on one or more RRC messages. The wireless device may monitor a set of PDCCH candidates according to 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 DCI messages. Monitoring may include decoding one or more PDCCH candidates of the set of PDCCH candidates according to the monitored DCI format. The monitoring may include decoding DCI content of one or more PDCCH candidates in possible (or configured) PDCCH positions, 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 the DCI to be valid for the wireless device, for example, after (e.g., based on or in response to) a CRC check (e.g., scrambling bits of the CRC parity bits of the DCI that match the RNTI value). The wireless device may process information included in the DCI (e.g., scheduling assignment, uplink grant, power control, slot format indication, downlink preemption, and / or the like).

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

[0144] There may be multiple PUCCH formats (e.g., five PUCCH formats). The wireless device may determine the PUCCH format based on, for example, the size of the UCI (e.g., the quantity / number 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 include two or fewer bits. The wireless device may use PUCCH format 0 to transmit / convey UCI over PUCCH resources, for example, if the transmission spans one or two symbols and the number / number 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 4 and 14 OFDM symbols) and may include two or fewer bits. The wireless device may use PUCCH format 1, for example, if the transmission spans 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 may include more than two bits. A wireless device may use PUCCH format 2, for example, when a transmission spans one or two symbols and the number of UCI bits is two or more. PUCCH format 3 may occupy several OFDM symbols (e.g., between 4 and 14 OFDM symbols) and may include more than two bits. A wireless device may use PUCCH format 3, for example, when a transmission is four or more symbols, the number of UCI bits is two or more, and the PUCCH resource does not include an orthogonal cover code (OCC). PUCCH format 4 may occupy several OFDM symbols (e.g., between 4 and 14 OFDM symbols) and may include more than two bits. A wireless device may use PUCCH format 4, for example, when a transmission is four or more symbols, the number of UCI bits is two or more, and the PUCCH resource includes an OCC.

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

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

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

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

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

[0150] Data to be transmitted to wireless device 1502 may be processed by, for example, processing system 1508 before being 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 before being 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 include, for example, the PHY layer described with respect to FIGS. 2A, 2B, 3, and 4A. For transmit / transmission processing, the PHY layer may perform, for example, forward error correction coding of transport channels, interleaving, rate matching, mapping of transport channels to physical channels, modulation of physical channels, multiple-input multiple-output (MIMO) or multi-antenna processing, and / or the like.

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

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

[0153] Processing system 1508 and processing system 1518 may be associated with memory 1514 and memory 1524, respectively. Memory 1514 and memory 1524 (e.g., one or more non-transitory computer-readable media) may store computer program instructions or code that may be executed by processing system 1508 and / or processing system 1518, respectively, to perform one or more functions (e.g., one or more functions described herein and 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 store computer program instructions or code that may be executed to perform one or more of their respective functions. The transmit processing system 1520 and / or the receive processing system 1522 may be coupled to memory 1524 and / or another memory (e.g., one or more non-transitory computer-readable media) that stores computer program instructions or code that may be executed to perform one or more of their respective functions.

[0154] The processing system 1508 and / or the processing system 1518 may include one or more controllers and / or one or more processors. The one or more controllers and / or the 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. The processing system 1508 and / or the 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 the wireless device 1502 and / or the base station 1504 to operate in a wireless environment.

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

[0156] 15B shows exemplary elements of a computing device that may be used to implement any of the various devices described herein, including, for example, base station 160A, 160B, 162A, 162B, 220, and / or 1504, wireless device 106, 156A, 156B, 210, and / or 1502, or any other base station, wireless device, AMF, UPF, network device, or computing device described herein. The computing device 1530 may include one or more processors 1531 that may execute instructions stored in random access memory (RAM) 1533, removable media 1534 (such as a universal serial bus (USB) drive, compact disc (CD) or digital versatile disc (DVD), or 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 may execute instructions of one or more computer programs to monitor processes running on the processor 1531 and any processes requesting access to any hardware and / or software components of the computing device 1530 (e.g., ROM 1532, RAM 1533, removable media 1534, hard drive 1535, device controllers 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 may include one or more output device controllers 1537, such as a video processor. There may also be one or more user input devices 1538, such as a remote control, keyboard, mouse, touchscreen, microphone, etc.The computing device 1530 may also include one or more network interfaces, such as a network interface 1539, which may be a wired interface, a wireless interface, or a combination of the two. The network interface 1539 may provide an interface 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 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 external servers and antennas, determine the geographic location of the computing device 1530.

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

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

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

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

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

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

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

[0164] A base station may transmit one or more MAC PDUs to a wireless device. In one embodiment, a MAC PDU may be a bit string whose length is byte-aligned (e.g., aligned to a multiple of 8 bits). In one embodiment, the bit string may be represented by a table in which the most significant bit is the leftmost bit of the first row of the table and the least significant bit is the rightmost bit of the last row of the table. More generally, the bit string is read from left to right, then in the order in which the rows are read. In one embodiment, the bit order of the parameter fields in a MAC PDU is represented by the most significant bit first in the leftmost bit and the least significant bit last in the rightmost bit. In one embodiment, a MAC SDU may be included in a MAC PDU from the first bit onward. A MAC Control Element (CE) may be a bit string whose length is byte-aligned (e.g., aligned to a multiple of 8 bits). In one embodiment, a MAC subheader may be a bit string whose length is byte-aligned (e.g., aligned to a multiple of 8 bits). In one embodiment, a MAC subheader may be positioned immediately before the corresponding MAC SDU, MAC CE, or padding.

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

[0166] In one embodiment, if the MAC subheader corresponds to a MAC SDU, a variable-sized MAC CE, or padding, the MAC subheader may include a reserved field (R field) having a 1-bit length, a format field (F field) having a 1-bit length, a logical channel identifier (LCID) field having a multi-bit length, a length field (L field) having a multi-bit length indicating the length in bytes of the corresponding MAC SDU or variable-sized MAC CE, or a combination thereof. In one embodiment, the F field may indicate the size of the L field.

[0167] In one embodiment, the base station MAC entity may send one or more MAC CEs to the wireless device MAC entity. In one embodiment, the one or more MAC CEs may include at least one of an SP ZP CSI-RS resource set activate / deactivate MAC CE, a PUCCH spatial relationship activate / deactivate MAC CE, an SP SRS activate / deactivate MAC CE, an SP CSI report activate / deactivate MAC CE for PUCCH, a UE-specific PDCCH TCI status indication MAC CE, a UE-specific PDSCH TCI status indication MAC CE, an aperiodic CSI trigger state sub-selection MAC CE, an SP CSI-RS / CSI-IM resource set activate / deactivate MAC CE, a UE contention resolution identity MAC CE, a timing advance command MAC CE, a DRX command MAC CE, a long DRX command MAC CE, a secondary cell (SCell) activate / deactivate MAC CE (1 octet), a SCell activate / deactivate MAC CE (4 octets), and / or a duplication activate / deactivate MAC CE. In one embodiment, a MAC CE, such as a MAC CE transmitted by a base station MAC entity to a wireless device MAC entity, may have an LCID in a MAC subheader corresponding to the MAC CE. Different MAC CEs may have different LCIDs in the MAC subheader corresponding to the MAC CE. For example, an LCID given by 111011 in a MAC subheader may indicate that the MAC CE associated with the MAC subheader is a Long DRX command MAC CE.

[0168] In one embodiment, the MAC entity of the wireless device may transmit one or more MAC CEs to the MAC entity of the base station. The one or more MAC CEs may include at least one of a short buffer status report (BSR) MAC CE, a long BSR MAC CE, a C-RNTI MAC CE, a configured grant confirmation MAC CE, a single-entry PHR MAC CE, a multiple-entry PHR MAC CE, a short truncated BSR, and / or a long truncated BSR. In one embodiment, the MAC CE may have an LCID in a MAC subheader corresponding to the MAC CE. Different MAC CEs may have different LCIDs in the MAC subheader corresponding to the MAC CE. For example, an LCID given by 111011 in a MAC subheader may indicate that the MAC CE associated with the MAC subheader is a short barring command MAC CE. For example, the PUCCH resources used to transmit (e.g., transmit) a semi-persistent report, CSI report, for the PUCCH may be configured by reportConfigType. Semi-persistent reporting on the PUCCH may be activated by a MAC CE activation command to select one of the semi-persistent reporting configurations for use by the wireless device on the PUCCH.

[0169] In carrier aggregation (CA), two or more component carriers (CCs) may be aggregated. Using CA, a wireless device may simultaneously receive or transmit on one or more CCs, depending on the capabilities of the wireless device. In one embodiment, a wireless device may support CA for adjacent and / or non-adjacent CCs. CCs may be organized into cells. For example, a CC may be organized into one primary cell (PCell) and one or more SCells. When configured with CA, a wireless device may have one RRC connection with the network. In one embodiment, a base station may send one or more messages to a wireless device containing configuration parameters for one or more SCells, depending on the capabilities of the wireless device. When configured with CA, a base station and / or wireless device may use an SCell activation / deactivation mechanism to improve battery or power consumption of the wireless device. When a wireless device is configured with one or more SCells, the base station may activate or deactivate at least one of the one or more SCells. An SCell may be deactivated unless the SCell state associated with the SCell is set to "activated" or "dormant" upon SCell configuration. In response to receiving the SCell Activation / Deactivation MAC CE, the wireless device may activate / deactivate the SCell.

[0170] A base station may configure a wireless device with an uplink (UL) bandwidth portion (BWP) and a downlink (DL) BWP to enable bandwidth adaptation (BA) on a PCell. If carrier aggregation is configured, the base station may further configure the wireless device with at least a DL BWP to enable BA on a SCell (i.e., there may be no UL BWP on the UL). For a PCell, the initial active BWP may be the first BWP used for initial access. In paired spectrum (e.g., FDD), the base station and / or wireless device may switch between the DL BWP and the UL BWP independently. In unpaired spectrum (e.g., TDD), the base station and / or wireless device may switch between the DL BWP and the UL BWP simultaneously.

[0171] In one embodiment, a base station and / or wireless device can switch between configured BWPs via a DCI or a BWP inactivity timer. If a BWP inactivity timer is configured for a serving cell, the base station and / or wireless device can switch the active BWP to a default BWP in response to expiration of the BWP inactivity timer associated with the serving cell. The default BWP can be configured by the network. In one embodiment, for an FDD system, if configured with BA, one UL BWP and one DL BWP for each uplink carrier can be simultaneously active in the active serving cell. In one embodiment, for a TDD system, one DL / UL BWP pair can be simultaneously active in the active serving cell. Operating with one UL BWP and one DL BWP (or one DL / UL pair) can improve battery consumption for the wireless device. BWPs other than the one active UL BWP and one active DL BWP on which the wireless device can operate can be deactivated. In a suspended BWP, the wireless device may not monitor the PDCCH and / or may not transmit on the PUCCH, PRACH, and UL-SCH. In one embodiment, the MAC entity may apply normal operations to an active BWP for an active serving cell configured in the BWP, including transmitting (e.g., transmitting) on the UL-SCH, transmitting (e.g., transmitting) on the RACH, monitoring the PDCCH, transmitting (e.g., transmitting) on the PUCCH, receiving the DL-SCH, and / or (re)initializing suspended configured uplink grants of configured grant type 1 according to a saved configuration, if any.In one embodiment, on an inactive BWP of each activated serving cell configured in the BWP, the MAC entity may not transmit on the RACH, may not monitor the PDCCH, may not transmit the PUCCH, may not transmit the SRS, may not receive the DL-SCH, may clear any configured downlink assignments and configured uplink grants of configured grant type 2, and / or may suspend any configured uplink grants of configured type 1.

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

[0173] In one example, a wireless device may monitor a set of PDCCH candidates according to configuration parameters of a search space set including multiple search spaces (SSs). The wireless device may monitor the 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 formats. The monitoring may include decoding DCI content of one or more PDCCH candidates having possible (or configured) PDCCH positions, possible (or configured) PDCCH formats (e.g., the number of CCEs, the number of PDCCH candidates in a common SS, and / or the number of PDCCH candidates in a UE-specific SS), and possible (or configured) DCI formats. The decoding may be referred to as blind decoding.

[0174] FIG. 17 shows examples of various DCI formats. The various DCI formats may be used, for example, by a base station to transmit (e.g., transmit) control information (e.g., to a wireless device) and / or for use by a wireless device. The control information may be used for PDCCH monitoring. Different DCI formats may include different DCI fields and / or have different DCI payload sizes. Different DCI formats may have different signaling purposes. DCI format 0_0 may be used to schedule PUSCH transmissions within a cell. DCI format 0_1 may be used to schedule one or more PUSCH transmissions within a cell and / or indicate configured grant downlink feedback information (CG-DFI) for configured grant PUSCH transmissions, etc. A priority index may be provided by a priority indicator field. The priority index may be provided, for example, if the wireless device monitors the PDCCH for DCI detection (e.g., detection of DCI corresponding to DCI format 0_1, DCI format 1_1, DCI format 0_2, and / or DCI format 1_2) in an active DL BWP. The first DCI format (e.g., DCI format 0_1 and / or DCI format 0_2) may schedule a PUSCH transmission of any priority, and / or the second DCI format (e.g., DCI format 1_1 and / or DCI format 1_2) may schedule a PDSCH reception, for example, if the wireless device indicates an ability to monitor the PDCCH in an active UL BWP for detection of the first DCI format and / or the second DCI format. The second DCI format (e.g., DCI format 1_1 and / or DCI format 1_2) may trigger a PUCCH transmission with corresponding HARQ-ACK information of any priority. DCI format 1_1 may trigger PUCCH transmission with corresponding HARQ-ACK information of any priority.

[0175] A wireless device may assume that a flexibility symbol in a CORESET configured for the wireless device for PDCCH monitoring is a downlink symbol. The wireless device may assume that a flexibility symbol is a downlink symbol, for example, if the wireless device does not detect a slot format indicator (SFI) indicator / index field value in a DCI (e.g., DCI format 2_0) that indicates one or more symbols of a slot as flexible or uplink, and / or if the wireless device does not detect a DCI (e.g., DCI format 0_0, DCI format 0_1, DCI format 1_0, DCI format 1_1, or DCI format 2_3) that indicates the wireless device to transmit / carry an SRS, a PUSCH transmission, a PUCCH transmission, and / or a PRACH transmission in one or more symbols.

[0176] A wireless device may receive a scheduled downlink transmission via a DCI. The wireless device may attempt to decode a transport block (TB) that the downlink transmission carries. The decoding attempt may be based on receiving the scheduled downlink transmission via the DCI. The decoding attempt may occur, for example, based on (e.g., subsequent to) a soft combination with a previous attempt / reception of the TB. One or more new downlink transmissions may be scheduled in the same framework as one or more downlink retransmissions. The wireless device may determine whether a downlink transmission is a new transmission or a retransmission, for example, based on a new data indicator (NDI) field in the DCI that indicates / schedules the downlink transmission. The time gap / interval / offset (e.g., K1) from downlink data reception (e.g., via DL-SCH resources) to transmission of a HARQ ACK / NACK corresponding to the downlink data may be fixed. For example, the time gap may include one or more subframes, slots, and / or symbols. This scheme with predefined timing instants for HARQ ACK / NACK may not mix well with dynamic TDD and / or unlicensed operation. A more flexible scheme that can dynamically control HARQ ACK / NACK transmission timing may be adopted. For example, the DCI format may include a PDSCH-to-HARQ_feedback timing field to control and / or indicate the transmission timing of the HARQ ACK / NACK corresponding to data scheduled by the DCI in an uplink transmission (e.g., PUCCH). The PDSCH-to-HARQ_feedback timing field in the DCI may be used as an index for one or more indices of a K1 value in a predefined and / or RRC configuration table (e.g., HARQ timing table). The K1 value may provide information about the gap / interval / offset between the first time of downlink data reception and the second time for transmitting (e.g., transmitting) the HARQ ACK / NACK.A wireless device may determine resources for a HARQ ACK / NACK transmission (e.g., frequency resources, PUCCH format, and / or code domain) based on, for example, the position of a PDCCH (e.g., a starting control channel element (CCE) index) carrying a DCI format. The DCI format may include a field (e.g., a PUCCH resource indicator (PRI) field) indicating frequency resources for uplink transmission of the HARQ ACK / NACK transmission. The PRI field may be an index that selects one of multiple predefined and / or RRC-configured PUCCH resource sets.

[0177] A wireless device may be scheduled to transmit (e.g., transmit) a TB without a CSI report. A wireless device may be scheduled to transmit (e.g., transmit) a TB and one or more CSI reports for a PUSCH via a DCI. A "Time Domain Resource Allocation" field value m of the DCI may provide a row index m+1 in an allocated table. The indexed row may define a slot offset K2, a start and length indicator SLIV (or a start symbol S and an allocation length L), a PUSCH mapping type, and / or a repetition number (e.g., if numberOfRepetitions is present in the resource allocation table) applied to the PUSCH transmission. A wireless device may be scheduled to transmit (e.g., transmit) a PUSCH without a TB and with one or more CSI reports via a "CSI Request" field on the DCI. A "Time Domain Resource Allocation" field value m of the DCI may provide a row index m+1 in an allocated table. The indexed row may define a start and length indicator SLIV (or a start symbol S and an allocation length L). The wireless device may determine the PUSCH mapping type and K2 value to be applied to the PUSCH transmission, for example, based on one or more higher layer parameters. K2 may indicate the slot in which the wireless device transmits (e.g., transmits) the first PUSCH of multiple PUSCHs, for example, if pusch-Config includes rows indicating resource allocations for 2 to 8 consecutive PUSCHs. Each PUSCH may have a distinct SLIV and / or mapping type. The number of scheduled PUSCHs may be signaled by the number of valid SLIVs indicated in a row of pusch-TimeDomainAllocationListForMultiPUSCH signaled in DCI format 0_1.

[0178] A wireless device may be configured with minimumSchedulingOffsetK2, for example, in an active UL BWP. minimumSchedulingOffsetK2 (e.g., in an active UL BWP) may apply the minimum scheduling offset restriction indicated by the "minimum applicable scheduling offset indicator" field in DCI format 0_1 or DCI format 1_1. If the wireless device is configured with minumminimumSchedulingOffsetK2 in an active UL BWP and does not receive the "minimum applicable scheduling offset indicator" field in DCI format 0_1 or 1_1, for example, the wireless device may apply the minimum scheduling offset restriction indicated based on the "minimum applicable scheduling offset indicator" value of "0". If the minimum scheduling offset restriction is applied, the wireless device may:

number

[0179] Semi-persistent scheduling (SPS) may be supported on the downlink, and wireless devices may be configured with data transmission periodicity using RRC signaling. Activation of semi-persistent scheduling may be performed using the PDCCH. For example, the CS-RNTI may be used for dynamic scheduling. The PDCCH may carry information associated with time-frequency resources and other parameters. The HARQ process number / ID may be derived, for example, from the time when downlink data transmission begins. The wireless device may receive downlink transmissions periodically after activation of semi-persistent scheduling. The downlink transmissions may be received, for example, according to an RRC-configured periodicity. The RRC-configured periodicity may be included in the transmission parameters indicated in the PDCCH that activates the transmission.

[0180] In the uplink, two schemes for transmission without dynamic grants may be supported. The two schemes may differ in how they are activated. The first scheme may be activated by configured grant type 1 (or type 1 configured grant), where the uplink grant is provided by RRC, including the activation grant. The second scheme may be activated by configured grant type 2 (or type 2 configured grant), where the transmission periodicity is provided by RRC and / or L1 / L2 control signaling is used to activate / stop transmission in a manner similar to that for the downlink. The two schemes may reduce control signaling overhead and / or delay before uplink data transmission because no scheduling request grant cycle is required before data transmission. Configured grant type 2 may be similar to downlink SPS. RRC signaling may be used to configure the periodicity. PDCCH activation may provide transmission parameters. After receiving the activation command, the wireless device may transmit (e.g., transmit) the data in the buffer based on, for example, a preconfigured periodicity. If there is no data in the buffer, the wireless device cannot send (e.g., transmit) anything, as with Type 1. The wireless device may confirm Type 2 activation / deactivation by sending a MAC CE on the uplink. In both schemes, multiple wireless devices may be configured with overlapping time-frequency resources in the uplink. The network may distinguish transmissions from different wireless devices, for example, when multiple wireless devices are configured with overlapping time-frequency resources in the uplink. The PUSCH resource allocation may be semi-statically configured, for example, by the higher layer parameter configuredGrantConfig in the BWP-UplinkDedicated information element.

[0181] The wireless device may support a baseline processing time / capability and / or additional aggressive / faster processing time / capability. The wireless device may report its processing capability (e.g., per subcarrier interval) to the base station. The wireless device may determine the first uplink symbol of the PUCCH (e.g., determined based on the HARQ-ACK timing K1, the one or more PUCCH resources used, and / or the effect of TA) that includes HARQ-ACK information for the PDSCH (e.g., scheduled by DCI), for example, based on the PDSCH processing time. The first uplink symbol of the PUCCH may be a time gap (e.g., T proc,1 ) or later. The first uplink symbol of the PUCCH carrying HARQ-ACK information may start at or after the start of symbol L1, where L1 is defined as the next uplink symbol with its cyclic prefix (CP) starting after the time gap after the end of the last symbol of the PDSCH. The time gap is T proc,1 =(N1+d 1,1 +d2)(2048+144).a1. The parameter a1 may depend on the numerology μ. The time gap may be given based on the wireless device PDSCH processing capability in the corresponding frequency band. d 1,1 may depend on the PDSCH mapping (eg, mapping type A or mapping type B) and the length of the PDSCH (number of symbols). The wireless device may set d2=0.

[0182] Figure 18 shows exemplary PDSCH processing times. Table 1 shows the PDSCH decoding time (referred to as "N1") for PDSCH processing capability 1. Table 2 shows the PDSCH decoding time N1 for PDSCH processing capability 2. For example, any other processing capability may be used, which may correspond to any other PDSCH processing time. The PDSCH decoding time N1 may be expressed in terms of the number of symbols. The PDSCH decoding time N1 may be for different numerologies. As shown in Figure 18, for PDSCH processing capability 1, the PDSCH decoding time N1 is greater than 14 OFDM symbols when the SCS is higher than 60 kHz (μ = 2). For PDSCH processing capability 2, the PDSCH decoding time N1 is 9 OFDM symbols for a 60 kHz SCS. The PDSCH decoding time N1 for 480 kHz and 960 kHz SCSs may be greater than 14 OFDM symbols (1 slot). N1 may be based on μ for each wireless device processing capability, where μ is PDCCH , μ PDSCH , μ UL μ PDCCH may correspond to the subcarrier spacing of the PDCCH that schedules the PDSCH, and μ PDSCH may correspond to the subcarrier spacing of the scheduled PDSCH, and μ UL may correspond to the subcarrier spacing of the uplink channel over which the HARQ-ACK is transmitted.

[0183] The transmission time of the UL data may be determined, for example, based on the PUSCH preparation / processing time. The wireless device may transmit (e.g., transmit) the PUSCH, for example, if the first uplink symbol in the PUSCH assignment for the transport block (including DM-RS) is not earlier than symbol L2. Symbol L2 may be determined (e.g., by the wireless device) based on the slot offset (e.g., K2), the SLIV of the PUSCH assignment indicated by the time domain resource allocation of the scheduling DCI. K2 and / or the SLIV may be described in connection with FIG. 17. Symbol L2 may be a slot offset of length T proc,2 =max((N2+d2,1 +d2)(2048+144).a1,d 2,2 ), where N2 may be described in connection with FIG. 19 below. The time gap may start after the end of reception of the last symbol of the PDCCH carrying DCI scheduling the PUSCH. If the wireless device, for example, determines that the first symbol of the PUSCH allocation consists of only DM-RS, then d 2,1 = 0, otherwise d 2,1 = 1. The parameter a1 may depend on the numerology μ. The numerology μ may be set to μ UL and / or μ PDCCH may correspond to and / or depend on

[0184] Figure 19 shows an example of PUSCH preparation / processing times. Table 3 shows exemplary PUSCH preparation / processing times in number of slots (referred to as "N2") for a wireless device having PUSCH timing capability 1. Table 4 shows exemplary PUSCH preparation / processing times in number of slots (N2) for a wireless device having PUSCH timing capability 2. PUSCH timing capabilities 1 and 2 may be described in relation to Figure 18. N2 may depend on numerology μ, where μ may correspond to the subcarrier spacing of the downlink of a PDCCH carrying DCI that schedules the PUSCH transmission. Numerology μ may correspond to the subcarrier spacing of the uplink channel on which the PUSCH is transmitted.

[0185] A wireless device may decode a PDSCH in a serving cell scheduled by a PDCCH with a C-RNTI, CS-RNTI, or MCS-C-RNTI and one or more PDSCHs received in the same serving cell (e.g., via CA) based on the corresponding PDCCH transmission, e.g., if the PDSCHs partially or completely overlap in time. A wireless device may decode a PDSCH without a corresponding PDCCH transmission, e.g., if the PDCCH scheduling the PDSCH ends at least 14 symbols before the earliest starting symbol of the PDSCH. The symbol duration may be determined, e.g., based on the minimum numerology between the scheduling PDCCH and the PDSCH. A wireless device may refrain from decoding a PDSCH scheduled with a C-RNTI, MCS-C-RNTI, or CS-RNTI if another PDSCH in the same cell scheduled with, e.g., an RA-RNTI or MSGB-RNTI, partially or completely overlaps in time. Unless the wireless device generates a transport block based on detecting a PDCCH having a configured DCI format 0_0, 0_1, or 0_2, the wireless device may transmit (e.g., transmit) a corresponding PUSCH as indicated by that DCI.

[0186] A wireless device may be configured with one or more SRS resource configuration parameters. The one or more SRS resource configuration parameters may indicate the configuration of an SRS resource set. The higher layer parameter sourceType of SRS-Resource or SRS-PosResource may be set to “aperiodic” (for aperiodic SRS transmission). The wireless device may receive a downlink DCI, a group-common DCI, or an uplink DCI-based command in which a code point of the DCI may trigger one or more SRS resource sets. The minimum time interval between the last symbol of the PDCCH and the first symbol of the SRS resource that triggers aperiodic SRS transmission may be determined based on, for example, N2 symbols and / or an additional duration for BWP switching when the SRS in a resource set with use is configured for codebook or antenna switching. The minimum time interval between the last symbol of the PDCCH and the first symbol of the SRS resource that triggers aperiodic SRS transmission may be set to, for example, N2 + 14 symbols, or N2 + 14 plus an additional duration for BWP switching when the SRS in a resource set with use is configured for other values. For example, if the wireless device receives a DCI that triggers an aperiodic SRS for slot n, and the SRS is configured with the higher layer parameter SRS-PosResource, the wireless device may transmit (e.g., transmit) all aperiodic SRS resources in each of the triggered SRS resource sets for slot m. Slot m may be determined (e.g., by the wireless device) based on the higher layer parameter slotOffset for each aperiodic SRS resource in each triggered SRS resource set, the subcarrier spacing of the triggered SRS transmission, the subcarrier spacing configuration for the triggered SRS, and / or the subcarrier spacing of the PDCCH carrying the triggered command.

[0187] A wireless device may adjust the uplink timing of PUSCH / SRS / PUCCH transmissions on serving cells (e.g., all serving cells) in a TA group (TAG), for example, after or in response to receiving a TAC MAC CE for the TAG. The TAC MAC CE for the TAG may indicate a change in uplink timing relative to the current uplink timing of the TAG. The wireless device may receive Msg2 1312 (or MsgB 1332) including a TA command field (e.g., an absolute TA command field). The wireless device may set the TA value with an initial value based on the received TA command (e.g., the absolute TAC MAC CE). After initial access, the TAC MAC CE for the TAG may indicate an adjustment to the TA value (e.g., the current TA value). Adjusting the current TA value by a positive amount (e.g., received via the TAC MAC CE) may indicate advancing the uplink transmission timing of the TAG by the corresponding amount. An adjustment of the current TA value by a negative amount (received via the TAC MAC CE) may indicate to delay the uplink transmission timing of the TAG by the corresponding amount.

[0188] A base station may configure (e.g., via RRC) a timeAlignmentTimer (e.g., per TAG) for maintaining UL time alignment. The timeAlignmentTimer may control the period during which serving cells belonging to the associated TAG are considered (e.g., by the MAC entity) as uplink time aligned.

[0189] After or in response to receiving the TAC MAC CE, the wireless device may apply a TA command to the indicated TAG and start (or restart) the timeAlignmentTimer associated with the indicated TAG. If a TA command may be received in a random access response message (e.g., Msg2 1312) for a serving cell belonging to the TAG or in MsgB 1321 for an SpCell, the wireless device may apply the TA command for this TAG and start or restart the timeAlignmentTimer associated with this TAG. If an absolute TA command is received (based on or in response to a MSGA transmission including a C-RNTI MAC CE), the wireless device may apply a TA command to the primary TAG and start (or restart) the timeAlignmentTimer associated with the primary TAG.

[0190] If the timeAlignmentTimer expires, the wireless device may perform at least one of the following based on the timeAlignmentTimer being associated with the primary TAG: flush the HARQ buffer of the serving cell (e.g., all HARQ buffers for all serving cells); if configured, send an RRC to release the PUCCH of the serving cell (e.g., all serving cells); if configured, send an RRC to release the SRS of the serving cell (e.g., all serving cells); clear the configured downlink assignment and the configured uplink grant; clear the PUSCH resources for semi-persistent CSI reporting; determine to run timeAlignmentTimers (which may correspond, for example, to a secondary TAG) when they expire; maintain one or more current TA values for one or more TAGs (e.g., all TAGs). The wireless device may have multiple running timeAlignmentTimers. The wireless device may, for example, determine / assume that each timeAlignmentTimer (eg, associated with a secondary TAG) has expired if a first timeAlignmentTimer (eg, associated with a primary TAG) has expired.

[0191] If the timeAlignmentTimer expires, the wireless device may perform at least one of the following based on the timeAlignmentTimer being associated with the secondary TAG: flush HARQ buffers (e.g., all HARQ buffers), send an RRC to release the PUCCH if configured, send an RRC to release the SRS if configured, clear configured downlink assignments and configured uplink grants, clear PUSCH resources for semi-persistent CSI reporting, and / or maintain the current TA value for this secondary TAG.

[0192] The wireless device may perform random access preamble (e.g., Msg1 1311) and / or MsgA 1331 transmissions to the serving cell if the timeAlignmentTimer associated with the TAG to which the serving cell belongs is not running. The wireless device may transmit random access preamble (e.g., Msg1 1311) and / or MsgA 1331 transmissions on the SpCell if the timeAlignmentTimer associated with the primary TAG is not running. The wireless device may refrain from making other uplink transmissions to the serving cell if the timeAlignmentTimer associated with the TAG to which the serving cell belongs is not running.

[0193] The one or more timing relationships (e.g., with respect to a TA value) may include one or more MAC CE timing relationships and / or one or more UL timing relationships. The one or more timing relationships may be based on one or more timing relationship rules. The one or more timing relationship rules may indicate an UL transmission timing adjustment (e.g., based on a TA value) and / or uplink timing for PUSCH / SRS / PUCCH transmission. The one or more timing relationship rules may indicate a MAC CE activation time (or wireless device assumption in a downlink or uplink configuration), for example, based on the reception time / opportunity of a PDSCH carrying the MAC CE on the downlink. The MAC CE may be activated X milliseconds after the wireless device transmits (e.g., transmits) a HARQ-ACK corresponding to the PDSCH.

[0194] The one or more timing relationship rules may indicate the transmission timing of one or more UL grants (e.g., PUSCH, aperiodic SRS, and / or SRS reporting via PUSCH). The UL grants may be indicated by DCI. The one or more timing relationship rules may indicate the transmission timing of UL transmissions (e.g., PUSCH, SRS, PUCCH). The UL transmissions may include a RAR UL grant, a fallbackRAR UL grant, and / or a PUSCH scheduled by a PUCCH with HARQ-ACK information (e.g., in response to a successRAR). The wireless device may receive a TAC MAC CE on uplink slot n. The one or more timing relationship rules may indicate adjustment of UL transmission based on uplink slot n+k+1, where k may be determined based on the PDSCH processing time of PDSCH processing capability 1 (e.g., as shown in Table 1 of FIG. 18), the PUSCH preparation time of PUSCH timing capability 1 (e.g., as shown in Table 3 of FIG. 19), and / or a maximum TA value that may be provided via a TAC MAC CE. The TAC MAC CE may include 12 bits. The one or more timing relationship rules may indicate transmission timing of UL transmissions scheduled by a RAR UL grant, a fallbackRAR UL grant, and / or a PUCCH with HARQ-ACK information (e.g., in response to a successRAR).

[0195] The wireless device may receive a MAC CE wake-up command in the downlink for one of one or more TCI states. The wireless device may transmit (e.g., transmit) a PUCCH with HARQ-ACK information (e.g., for a PDSCH that provides the wake-up command in slot k). One or more timing relationship rules may determine whether the wireless device transmits a PUCCH with HARQ-ACK information for slot k.

number

[0196] The wireless device may receive a PDSCH carrying a wake-up command in the downlink indicating a semi-persistent reporting configuration. The wireless device may transmit (e.g., transmit) a PUCCH with HARQ-ACK information in uplink slot n corresponding to the PDSCH. One or more timing relationship rules may determine whether the indicated semi-persistent reporting configuration is configured in slot n.

number

[0197] A wireless device may receive an activation command for one or more CSI-RS resource sets for channel measurements and / or CSI-IM / NZP CSI-RS resource sets for interference measurements (e.g., associated with one or more configured CSI resource configurations). The wireless device may transmit (e.g., transmit) a PUCCH with HARQ-ACK information in uplink slot n corresponding to a PDSCH carrying the selection command in the downlink. One or more timing relationship rules may determine whether corresponding actions and / or wireless device assumptions (e.g., corresponding to quasi-co-location assumptions provided by a list of references to one of the TCI-States per activated resource) for CSI-RS / CSI-IM transmissions occur in slot n.

number

number

[0198] The wireless device may transmit (e.g., transmit) a PUCCH with HARQ-ACK information in slot n corresponding to a PDSCH carrying a wake-up command indicating that the wireless device performs semi-persistent CSI reporting for the PUCCH.

number

[0199] A wireless device may receive a wake-up command for an SRS resource. The wireless device may transmit (e.g., transmit) a PUCCH with HARQ-ACK information in slot n corresponding to a PDSCH carrying the wake-up command for slot n. One or more timing relationship rules may determine whether the action time of the wake-up command (and / or wireless device assumption for SRS transmission corresponding to a configured SRS resource set) is within the time range of slot n.

number

[0200] A wireless device may receive a stop command for an activated SRS resource set. The wireless device may transmit (e.g., transmit) a PUCCH with HARQ-ACK information in slot n corresponding to a PDSCH carrying the stop command. One or more timing relationship rules may determine whether an action time for the stop command (and / or wireless device assumption regarding stopping SRS transmission) corresponding to the deactivated SRS resource set occurs in slot n.

number

[0201] The wireless device may transmit (e.g., transmit) a PUCCH with HARQ-ACK information in uplink slot n corresponding to a PDSCH carrying a ZP CSI-RS resource set activation MAC CE for one or more ZP CSI-RS resources. The one or more timing relationship rules may determine whether the corresponding action times (and / or wireless device assumptions regarding PDSCH resource element mapping) of the ZP CSI-RS resource set activation MAC CEs corresponding to the activated one or more ZP CSI-RS resources occur in slot n.

number

number

[0202] A wireless device may be configured with buffer status reporting (BSR) configuration parameters, which may include at least one of a periodic BSR timer (e.g., periodicBSR-Timer), a BSR retransmission timer (e.g., retxBSR-Timer), an SR delay timer application indicator (e.g., logicalChannelSR-DelayTimerApplied), an SR delay timer (e.g., logicalChannelSR-DelayTimer), an SR mask parameter (e.g., logicalnelSR-Mask), or a logical channel group (LCG) group indicator (e.g., logicalGroup).

[0203] A wireless device may trigger a first BSR based on (e.g., in response to) the wireless device's MAC entity having new UL data available for a logical channel (LCH). The LCH may belong to an LCG. The new UL data may belong to an LCH with a higher priority than the priority of other LCHs containing available UL data belonging to other LCGs. Alternatively, the new UL data may belong to the only LCH containing currently available UL data. The first BSR procedure may be referred to herein as a normal BSR (or a first type of BSR).

[0204] The wireless device may trigger a second BSR based on (e.g., in response to) being allocated UL resources and the number of padding bits being equal to or greater than the size of the BSR MAC CE plus its subheader, for example. The second BSR may be referred to herein as a padding BSR (or a second type of BSR).

[0205] The wireless device may trigger a third BSR based on (e.g., in response to) expiration of a timer (e.g., retxBSR-Timer) and / or an LCH belonging to an LCG that includes UL data. The third BSR may be the same type of BSR as the first BSR procedure. The third BSR may be referred to herein as a regular BSR. The MAC entity of the wireless device may restart the retxBSR-Timer after or in response to receiving an UL grant for transmission of new data on any UL-SCH. The MAC entity of the wireless device may determine that the LCH that triggered the third BSR is the highest priority LCH with data available for transmission at the time the BSR was triggered (e.g., for a BSR triggered by expiration of a BSR retransmission timer (e.g., retxBSR-Timer)). The wireless device may trigger a fourth BSR based on (e.g., in response to) expiration of a timer (e.g., periodicBSR-Timer). The fourth BSR may be referred to herein as a periodic BSR (or a third type BSR).

[0206] The wireless device may start or restart an SR delay timer (e.g., logicalChannelSR-DelayTimer) based on (e.g., in response to) a BSR being triggered for a first LCH. The first LCH may be associated with logicalChannelSR-DelayTimerApplied set to a value of true. The wireless device may refrain from triggering an SR for a pending BSR based, for example, on determining that the associated SR delay timer is running. The wireless device may stop a running SR delay timer based, for example, on (e.g., in response to) a BSR being triggered for a second LCH for which logicalChannelSR-DelayTimerApplied is not configured or is set to a value of false.

[0207] The wireless device may report a long BSR to the LCGs that have data available for transmission (e.g., all LCGs), for example, based on (e.g., in response to) two or more LCGs having data available for transmission when a MAC PDU that includes a BSR (e.g., a regular BSR or a periodic BSR) is constructed. The wireless device may report a short BSR based on, for example, less than or equal to the LCGs that have data available for transmission when a MAC PDU that includes a BSR is constructed.

[0208] The wireless device may report a short abbreviated BSR to the LCG with the highest priority logical channel among the LCGs with data available for transmission when the BSR (e.g., padding BSR) is constructed, for example, if the number of padding bits is greater than or equal to the size of the short BSR plus its subheader but less than the size of the long BSR plus its subheader, and / or the number of padding bits is equal to the size of the short BSR plus its subheader.

[0209] The wireless device may report the long shortened BSR of the LCG having the LCH with data available for transmission based on decreasing order starting from the highest priority LCH (with or without data available for transmission) if two or more LCGs have data available for transmission when the BSR (e.g., padding BSR) is constructed and / or if the number of padding bits is greater than or equal to the size of the short BSR plus its subheaders but less than the size of the long BSR plus its subheaders. If two or more LCGs have equal priority, transmission may further be based on ascending order of LCGID.

[0210] A wireless device may report a short BSR if the number of padding bits is equal to or greater than the size of the short BSR plus its subheaders but less than the size of the long BSR plus its subheaders, and / or if at most one LCG has data available for transmission when the BSR (e.g., padding BSR) is constructed. A wireless device may report a long BSR for all LCGs that have data available for transmission if the number of padding bits is equal to or greater than the size of the long BSR plus its subheaders.

[0211] The wireless device may trigger the multiplexing and assembly procedures to generate a BSR MAC CE, start (or restart) a periodic BSR timer (e.g., periodicBSR-Timer), and / or start (or restart) a BSR retransmission timer (e.g., retxBSR-Timer) based on (e.g., in response to) at least one BSR being triggered and not canceled, and / or UL-SCH resources being available for a new transmission, and the UL-SCH resources accommodating the BSR MAC CE plus its subheader as a result of logical channel prioritization. The wireless device may refrain from triggering the multiplexing and assembly procedures to generate a BSR MAC CE, start (or restart) a periodic BSR timer (e.g., periodicBSR-Timer), and / or start (or restart) a BSR retransmission timer (e.g., retxBSR-Timer) if, for example, all generated BSRs are long BSRs or all generated BSRs are short, truncated BSRs.

[0212] The wireless device may trigger an SR based on (e.g., in response to) at least one BSR being triggered and not canceled, a normal BSR for at least one BSR being triggered and the logicalChannelSR-DelayTimer associated with the LCH for the normal BSR not running, and / or UL-SCH resources not being available for a new transmission. The UL-SCH not being available for a new transmission may include the MAC entity being configured with a configured uplink grant and a normal BSR being triggered for an LCH with the logicalChannelSR-Mask set to false, or the UL-SCH resources available for a new transmission not satisfying the LCP mapping restrictions configured for the LCH that triggered the BSR.

[0213] A wireless device may determine that a UL-SCH resource is available if the MAC entity of the wireless device has an active configuration for one of the configured uplink grant types (Type 0 or Type 1) and / or if the MAC entity receives a dynamic uplink grant. A wireless device may determine that one or more UL-SCH resources are available if the MAC entity is configured with a received and / or determined uplink grant. If a MAC entity determines that a UL-SCH resource is available (e.g., at a given time), this does not necessarily mean that the UL-SCH resource is usable at that time.

[0214] A MAC PDU may contain at most one BSR MAC CE if multiple events triggered the BSR. Regular and periodic BSRs may have priority (e.g., higher priority) over padding BSRs. A wireless device may cancel a triggered BSR (e.g., all triggered BSRs) if the UL grant can accommodate all pending data available for transmission but is not large enough to accommodate the BSR MAC CE plus its subheader. A wireless device may cancel a triggered BSR (e.g., all BSRs) before MAC PDU assembly, for example, if the MAC PDU is to be transmitted (e.g., transmitted), the MAC PDU contains a long or short BSR MAC CE, and the BSR MAC CE contains buffer status up to (and including) the last event that triggered a BSR before MAC PDU assembly.

[0215] MAC PDU assembly can occur at any time between uplink grant reception and the actual transmission of the corresponding MAC PDU. BSR and SR can be triggered after assembly of the MAC PDU containing the BSR MAC CE, but before transmission of this MAC PDU. BSR and SR can be triggered during MAC PDU assembly.

[0216] A base station may send (e.g., transmit) to a wireless device one or more RRC messages including configuration parameters of one or more PUCCH resources and / or configuration parameters of multiple SR configurations. A first SR configuration of the multiple SR configurations may correspond to one or more first LCHs of the multiple LCHs. A base station may send (e.g., transmit) to a wireless device at least one message including parameters indicating one or more SR configurations. Each SR configuration may correspond to one or more LCHs. Each logical channel may be mapped to one or less SR configurations. The SR configuration of an LCH that triggers a BSR may be considered as the corresponding SR configuration of the triggered SR.

[0217] The one or more configuration parameters may include at least one of an SR prohibit timer (e.g., sr_ProhibitTimer), a maximum number of SR transmissions (e.g., sr_TransMax), a parameter indicating the periodicity and offset of SR transmissions in slots (e.g., periodicityAndOffset) of PUCCH transmissions carrying SR, and / or a PUCCH resource, the number of symbols of PUCCH transmission (e.g., nrofSymbols). The SR configuration may include a set of PUCCH resources for SR. The set of PUCCH resources may be on and / or correspond to one or more BWPs and / or one or more cells. In a BWP, at most one PUCCH resource for SR may be configured. The wireless device may be configured with a priority index of 0 or a priority index of 1 for SR (e.g., by phy-PriorityIndex in SchedulingRequestResourceConfig). If the wireless device is not provided with a priority index for SR, the priority index may be 0.

[0218] The wireless device may trigger a BSR based on (e.g., in response to) data becoming available for the LCH. The wireless device may determine that the SR configuration for the LCH that triggers the BSR is the corresponding SR configuration for the triggered SR. The wireless device may trigger an SR (e.g., an SR for the BSR) that requests UL-SCH resources when the wireless device has a new transmission. The wireless device may determine the SR as pending after the SR is triggered and until the SR is canceled. One or more pending SRs (e.g., all pending SRs) may be canceled, for example, if one or more UL grants contain one or more pending data (e.g., all pending data) available for transmission.

[0219] The SR prohibit timer may be a duration during which the radio is not permitted to transmit (e.g., transmit) SRs. The wireless device may remain active while the sr_ProhibitTimer is running and may monitor the PDCCH to detect DCI indicating an uplink scheduling grant. The maximum number of SR transmissions (e.g., sr_TransMax) may be the maximum number of SRs the wireless device is permitted to transmit (send).

[0220] The wireless device may determine whether at least one valid PUCCH resource for a pending SR is available for SR transmission. The wireless device may initiate an RA procedure on a PCell or a PSCell, for example, based on determining that a valid PUCCH resource is unavailable. The wireless device may cancel a pending SR, for example, based on initiating an RA procedure. The wireless device may determine that at least one valid PUCCH resource for a pending SR is available, for example, if the at least one valid PUCCH resource does not overlap with a measurement gap. The wireless device may determine to transmit an SR on the at least one valid PUCCH resource, for example, based on the periodicity and offset of a corresponding SR configuration. The wireless device may transmit (e.g., transmit) a PUCCH using PUCCH format 0 or PUCCH format 1, for example, based on the PUCCH configuration.

[0221] The wireless device may determine not to transmit another SR (e.g., refrain from transmitting) based on determining that the SR prohibit timer is running. The wireless device may wait for another SR transmission after the SR prohibit timer expires. The wireless device may maintain an SR transmission counter (e.g., SR_COUNTER) associated with the SR configuration to count the number of times an SR is transmitted (or retransmitted). The wireless device may set the SR_COUNTER of the SR configuration to a first value (e.g., 0), for example, when an SR for the SR configuration is triggered and there are no other SRs pending corresponding to the same SR configuration.

[0222] If the SR prohibit timer is not running and the SR_COUNTER is less than the maximum number of SR transmissions, the wireless device may instruct its physical layer to transmit (e.g., signal) an SR on at least one valid PUCCH resource for the pending SR, increment the SR_COUNTER (e.g., by one), and start the SR prohibit timer. The wireless device may, for example, start monitoring the PDCCH to detect DCI for uplink grants (e.g., while the SR prohibit timer is running) based on (e.g., in response to) the SR being transmitted. The wireless device may, for example, cancel the pending SR and / or stop the SR prohibit timer if one or more uplink grants are received that may contain pending data available for transmission (e.g., all pending data).

[0223] The wireless device may cancel pending SRs (e.g., all pending SRs) for BSRs triggered prior to MAC PDU assembly and / or stop each respective sr-ProhibitTimer based on (e.g., after or in response to) a MAC PDU being transmitted, the MAC PDU including a long or short BSR MAC CE including buffer status up to (and including) the last event that triggered a BSR prior to MAC PDU assembly. The wireless device may cancel pending SRs (e.g., all pending SRs) for BSRs and stop each respective sr-ProhibitTimer by determining that an UL grant accommodates all pending data available for transmission.

[0224] If an uplink grant containing all pending data available for transmission is not received by the expiration of the SR prohibit timer, the wireless device may repeat one or more actions including determining at least one valid PUCCH resource for transmitting an SR, checking whether the SR prohibit timer is running, whether the SR_COUNTER is greater than or equal to the maximum number of SR transmissions, incrementing the SR_COUNTER, transmitting (e.g., transmitting) an SR, starting the SR prohibit timer, and / or monitoring the PDCCH for an uplink grant.

[0225] The wireless device may, for example, determine that the SR_COUNTER indicates a number greater than or equal to the maximum number of SR transmissions, release the PUCCH and / or SR for one or more serving cells, clear one or more configured downlink assignments and / or uplink grants, initiate an RA procedure on the PCell, and / or cancel a pending SR.

[0226] A wireless device (e.g., a MAC entity of the wireless device) may terminate an ongoing RA procedure based, for example, on the fact that a pending SR does not have valid PUCCH resources configured and the SR was initiated by the MAC entity of the wireless device prior to MAC PDU assembly. A wireless device may terminate an ongoing RA procedure based, for example, on the fact that an SR for a BSR is not configured with valid PUCCH resources. An ongoing RA procedure may be canceled after or in response to transmitting (e.g., transmitting) a MAC PDU via a first UL grant (e.g., other than an UL grant provided by the RAR of the RA procedure). The MAC PDU may include a BSR MAC CE containing buffer status up to (and including) the last event that triggered a BSR prior to MAC PDU assembly. An ongoing RA procedure may be canceled when an UL grant containing all pending data available for transmission is received.

[0227] FIG. 20 illustrates an example of an RA procedure. Multiple uplink carriers and multiple RA types may be configured. In step 2001, a base station may send (e.g., transmit) one or more RACH configuration messages (e.g., RRC messages) including one or more parameters for a RACH configuration. The one or more RACH configuration messages may be configured with messages 1310, 1320, and / or 1330, as described in connection with FIG. 13. The one or more RACH configuration messages may be received before the start of the RA procedure. The cell may include an SUL and / or a NUL. The RACH configuration may indicate a two-step RA and / or a four-step RA. A wireless device may receive configuration parameters from a base station indicating different (e.g., independent) PRACH opportunities between the two-step RA and the four-step RA. A base station may configure one or more PRACH opportunities shared between the two-step RA and the four-step RA, and separate preambles for the two-step RA and the four-step RA. A wireless device may be configured with a four-step RACH configuration regardless of whether a two-step RACH configuration is present. A wireless device may select which type of RACH (2-step or 4-step) to use to initiate an RA procedure if the base station configures the wireless device with both 4-step and 2-step RACH resources / configurations. A wireless device that supports 2-step RA may select the 2-step RA type if, for example, the received target power for preamble and PUSCH transmissions can be achieved. A wireless device may select between the 2-step RA type and the 2-step RA type based on RSRP.

[0228] The one or more RACH configuration messages may include one or more common configuration parameters (e.g., RA-ConfigCommon IE and / or RA-ConfigCommonTwoStepRA-r16 IE) and / or one or more configuration parameters (e.g., MsgA-PUSCH-Config IE) for configuring MsgA 1331. The one or more RACH configuration messages may include generic configuration parameters (e.g., RACH-ConfigGeneric IE or RACH-ConfigGenericTwoStepRA IE), one or more cell-specific random access configuration messages (e.g., RACH-ConfigCommon and / or RACH-ConfigGeneric), and / or one or more dedicated random access configuration messages (e.g., RACH-ConfigDedicated). The MsgA-PUSCH-Config IE may include a list of MsgA PUSCH resources (e.g., msgA-PUSCH-ResourceList) that the wireless device may use when performing MsgA 1331 transmissions. The MsgA payload may include a BSR MAC CE, a Power Headroom Report (PHR) MAC CE, an RRC message, and / or a connection request.

[0229] A lower layer (e.g., physical layer) of the wireless device may receive one or more SS / PBCH block indices and / or one or more PRACH transmission parameters from a higher layer (e.g., MAC layer). The one or more PRACH transmission parameters may indicate a PRACH preamble format, a preamble index, a corresponding RA-RNTI (or MSGB-RNTI), time and / or frequency resources for PRACH preamble transmission, and / or parameters for determining one or more PRACH preamble sequences and a shift in PRACH preamble sequence set (e.g., set type). The physical layer may provide one or more corresponding sets of RSRP measurements and / or one or more indications to the higher layer (e.g., MAC layer).

[0230] In step 2005, the wireless device may trigger an RA procedure based on, for example, one or more RACH configuration messages. The wireless device may trigger the RA procedure based on (e.g., in response to) receiving an RRC reconfiguration message (e.g., from a base station) for initial access to a cell, a positioning procedure, an uplink coverage recovery procedure, initiation of beam failure recovery, handover to a second cell, receiving a PDCCH order (e.g., from a base station), resynchronizing the wireless device's status (e.g., after new data arrives and the radio status becomes out of sync), new data arriving in the wireless device's buffer and no scheduling request (SR) resources configured, and / or pending data existing in the wireless device's buffer and the wireless device reaching a maximum allowed number of times to transmit (e.g., retransmit) an SR (e.g., in the event of an SR failure). The MAC entity of the wireless device may limit the number of ongoing RA procedures to one at a given time. If an RA procedure is in progress and a new RA procedure is triggered, the wireless device may decide (e.g., based on the implementation of the wireless device) whether to continue the ongoing RA procedure or start (or initialize) a new RA procedure.

[0231] In step 2010, the wireless device may initiate an RA procedure based on (e.g., in response to) the RA procedure being triggered. Initializing the RA procedure may include at least one of step 2020, determining a carrier (SUL or NUL) for performing the RA procedure (e.g., based on a measured RSRP), step 2030, selecting an RA type for performing the RA procedure (e.g., determining a two-step RA type or a four-step RA type), and / or step 2040, initializing one or more RA parameters (e.g., variables) specific to the selected RA type. The wireless device may use the one or more parameters for the initiated RA procedure. The one or more parameters may include at least one of the following: RA_TYPE, PREAMBLE_INDEX, PREAMBLE_TRANSMISSION_COUNTER, PREAMBLE_POWER_RAMPING_COUNTER, PREAMBLE_POWER_RAMPING_STEP, PREAMBLE_RECEIVED_TARGET_POWER, PREAMBLE_BACKOFF, PCMAX, SCALING_FACTOR_BI, POWER_OFFSET_2STEP_RA, MSGA_PREAMBLE_POWER_RAMPING_STEP, and TEMPORARY_C-RNTI. The wireless device may set one or more of the RA procedure parameters. The wireless device may set the value of PCMAX based on, for example, the selected carrier (SUL or NUL). After the wireless device initiates the RA procedure 2010, it may flush the Msg3 buffer. After the wireless device triggers the RA procedure 2010, it may flush the MsgA buffer.

[0232] In step 2050, the wireless device may perform an RA procedure, for example, using the selected RA resource having the selected RA carrier and RA type. The RA procedure may be performed after the RA procedure is initiated. If the RA procedure is a four-step RA procedure, performing the RA procedure may include one or more of selecting an RA resource and transmitting (e.g., transmitting) one or more PRACH preambles, monitoring one or more PDCCHs to receive one or more random access responses (RARs), one or more retransmissions of one or more PRACH preambles, transmitting an Msg3, and / or a contention resolution procedure. If the RA procedure is a two-step RA procedure, performing the RA procedure may include one or more of: selecting an RA resource; transmitting (e.g., transmitting) one or more PRACH preambles and / or one or more MsgA payloads; monitoring one or more PDCCHs to receive one or more RARs; one or more retransmissions of one or more PRACH preambles and / or MsgA payloads; switching to a four-step RA procedure; and / or performing a fallback procedure (e.g., transmitting Msg3 based on receiving MsgB including a fallback MAC sub-PDU).

[0233] Referring back to step 2030, the wireless device may select an RA type, for example, after selecting an uplink carrier (e.g., SUL or NUL). The wireless device may select the RA type based on one or more of an RSRP value, a delay requirement, a distance to a serving (or target) base station, and / or a logical channel priority that triggers a BSR. The wireless device may select a two-step RA type (e.g., RA_TYPE=2-stepRA) to perform an RA procedure on the selected uplink carrier, for example, if the RSRP is greater than an RSRP threshold. The wireless device may select a four-step RA type to perform an RA procedure, for example, if the RA procedure is triggered / initiated for system information (SI) acquisition.

[0234] Referring back to step 2040, for example, after determining the RA type, the wireless device may initialize one or more RA parameters specific to the selected RA type. The wireless device may initialize one or more parameters of the RA procedure (e.g., a transmission counter, a transmit timer, a transmit power setting, and / or a response window). If the selected RA type is a two-step RA procedure (i.e., RA_TYPE=2-stepRA), the one or more RA parameters may include at least the following: PREAMBLE_POWER_RAMPING_STEP, msgA-TransMax, preambleTransMax, and / or SCALING_FACTOR_BI. If the selected RA type is a four-step RA procedure (i.e., RA_TYPE=4-stepRA), the one or more RA parameters may include at least the following: PREAMBLE_POWER_RAMPING_STEP, preambleTransMax, and / or SCALING_FACTOR_BI. If the selected RA type is a two-step RA procedure (ie, RA_TYPE=2-stepRA), the wireless device may set PREAMBLE_POWER_RAMPING_STEP to msgA-PreamblePowerRampingStep.

[0235] The wireless device may set POWER_OFFSET_2STEP_RA based on at least one or more configuration parameters, for example, if the RA_type is switched from 2-step RA to 4-step RA during an ongoing / current RA procedure. The at least one or more configuration parameters may include PREAMBLE_POWER_RAMPING_COUNTER and / or PREAMBLE_POWER_RAMPING_STEP. The wireless device may initialize RA variables specific to the 4-step RA type (described in connection with step 2040) and perform the RA procedure (described in connection with step 2050), for example, based on (and in response to) switching the RA type from 2-step RA to 4-step RA during the ongoing / current RA procedure.

[0236] The wireless device may perform a RAP transmission based on, for example, a selected PREABLE_INDEX and / or PRACH opportunity. The wireless device may perform a RAP transmission based on a selected preamble index and PRACH opportunity, and / or may perform a MsgA payload transmission based on a selected MsgA PUSCH opportunity. For example, the wireless device may increment PREAMBLE_POWER_RAMPING_COUNTER (e.g., by one or the next value) based on, for example, not receiving a notification from a lower layer (e.g., a physical layer) to pause the power ramping counter and / or based on the selected SSB and / or CSI-RS not being changed (e.g., the same as the previous RAP transmission). The counter step size may be predefined and / or semi-statically configured.

[0237] The wireless device may start an RAR window (e.g., ra-ResponseWindow or msgB-ResponseWindow) at the first downlink control channel opportunity, for example, from the end of a RAP transmission (e.g., Msg1 1311 or Msg1 1321 for a four-step RA procedure) or from the end MsgA payload transmission (e.g., TB 1342 for a two-step RA procedure). The wireless device may monitor a first DCI for the SpCell RAR identified by a particular RNTI (e.g., a Random Access Radio Network Temporary Identifier (RA-RNTI), a Temporary Cell Radio Network Temporary Identifier (TC-RNTI), a C-RNTI, and / or an MSGB-RNTI), for example, while the RAR window is running. The first DCI may include at least one of one or more of an RA preamble index, an SS / PBCH index, a PRACH mask index, an UL / SUL indicator, a frequency and time domain resource allocation, a modulation and / or a coding scheme. A wireless device may monitor a set of candidates for one or more downlink control channels in a Type1-PDCCH common search space set, which may be configured by one or more search space sets (e.g., ra-searchSpace of PDCCH-ConfigCommon).

[0238] In a two-step RA procedure, a wireless device may receive two separate responses corresponding to the MsgA transmission. The two responses may include a first response to the RAP (e.g., MsgA preamble) transmission and a second response to the transmission of one or more TBs (e.g., MsgA payload). The wireless device may monitor the PDCCH (e.g., a common search space and / or a wireless device-specific search space) to detect the first response. The first response may be based on, for example, a time and / or frequency index of a PRACH resource on which the wireless device may transmit (e.g., transmit) the RAP and may include an MSGB-RNTI. The wireless device may monitor the common search space and / or the wireless device-specific search space to detect the second response.

[0239] The wireless device may transmit (e.g., transmit) an MsgA preamble (e.g., as part of an MsgA transmission) based on, for example, determining that the corresponding PRACH or MsgA preamble is not mapped to a valid MsgA PUSCH opportunity. The wireless device may detect a first DCI having a CRC scrambled by the corresponding MSGB-RNTI during the RAR window based on determining that the MsgA preamble is mapped to an invalid MsgA PUSCH opportunity.

[0240] The wireless device may receive a PDCCH, for example, based on the RA-RNTI or MSGB-RNTI. The PDCCH may indicate a downlink allocation, for example, based on the wireless device receiving one or more TBs including a MAC PDU. The MAC PDU may include at least one MAC sub-PDU with a corresponding subheader. The subheader may include an RA preamble identifier (e.g., RAPID) that matches a preamble that the wireless device sends (e.g., transmits) to the base station. The wireless device may determine that RAR reception is successful, for example, if a PDCCH (e.g., indicating / scheduling a MAC PDU and / or at least one MAC sub-PDU) is received. The at least one MAC sub-PDU may include a RAPID. The RAPID may correspond to a random access procedure initiated by the wireless device based on an SI request.

[0241] The wireless device may stop an RAR window (e.g., ra-ResponseWindow or msgB-ResponseWindow) after and / or in response to receiving one or more RARs, and the RARs are determined to be successful. Reception of one or more RARs may be determined to be successful, for example, if the one or more RARs include a RAPID corresponding to a preamble that the wireless device transmits (e.g., transmits) to the base station (e.g., an MsgA preamble). The one or more RARs may include an uplink grant indicating one or more uplink resources granted to the wireless device. The wireless device may transmit (e.g., transmit) one or more transport blocks (e.g., Msg3) via the one or more uplink resources. The wireless device may use the downlink assignment to identify parameters for decoding / detecting one or more TBs. The downlink assignment may indicate at least one of a time and / or frequency resource allocation for a PDSCH carrying one or more TBs and / or the size of the PDSCH and / or MCS.

[0242] The RAR message may be in the form of a MAC PDU containing one or more MAC sub-PDUs and / or optional padding. The MAC sub-PDU may include at least one of a MAC sub-header with a backoff indicator, a MAC sub-header with RAPID (e.g., an acknowledgment for an SI request), and / or a MAC sub-header with RAPID and a MAC RAR. The MAC RAR may be a fixed size and may include at least one of an R field that may indicate reserved bits, a TAC MAC CE field that may indicate an index value TA (e.g., to control the amount of timing adjustment), a UL grant field that may indicate resources to be used on the uplink, and / or an RNTI field (e.g., a temporary C-RNTI and / or C-RNTI) that may indicate an identity used during the RA procedure. In the case of a two-step RA procedure, the RAR may include at least one of a wireless device contention resolution identity, an RV ID for one or more TB retransmissions, and / or a successful decoding failure indicator for one or more TB transmissions.

[0243] The wireless device may determine that RAR reception is not successful, for example, based on determining that at least one RAR including one or more RAPIDs matching the transmitted PREAMBLE_INDEX is not received until the expiration of the RAR window. The wireless device may perform one or more retransmissions of one or more PRACH preambles during the RA procedure, for example, based on (e.g., in response thereto and / or thereafter) determining that RAR reception is not successful. The wireless device may determine to retransmit one or more MsgAs (e.g., MsgA preambles and / or MsgA payloads) based on (e.g., in response thereto) not receiving at least one MsgB until the expiration of the RAR window. At least one MsgB may include a contention resolution identifier that the wireless device may have included in the MsgA payload during a previous transmission. The wireless device may determine to retransmit one or more preambles of MsgAs, for example, based on (e.g., in response thereto) determining that contention resolution is not successful. The wireless device may determine whether the contention resolution was successful based on, for example, Msg 3 for a four-step RA procedure and / or MsgB for a two-step RA procedure.

[0244] The wireless device may start a contention resolution timer (e.g., ra-ContentionResolutionTimer). The wireless device may restart the contention resolution timer with each HARQ retransmission of the first symbol after the end of the Msg3 1313 transmission (e.g., after the wireless device sends (e.g., transmits) Msg3 to the base station). The wireless device may determine that contention resolution is not successful, e.g., based on not receiving a contention resolution indication until the contention resolution timer expires. The wireless device may discard the TEMPRARY_C-RNTI indicated by Msg2 1312 (or MsgB 1332), e.g., after or in response to expiration of the contention resolution timer (and / or after or in response to a failed contention resolution determination).

[0245] The wireless device may fall back from a two-step RA procedure to a four-step RA procedure, for example, based on an explicit and / or implicit indication of MsgB (e.g., based on receiving a fallbackRAR message). The implicit indication of MsgB may include an RNTI used to detect the PDCCH (e.g., RA-RNTI or MSGB-RNTI) that schedules MsgB. The wireless device may send (e.g., transmit) Msg3, for example, after receiving the fallback message or in response thereto (e.g., via resources indicated by an UL grant for MsgB). The wireless device may follow the four-step RA procedure (e.g., starting a contention resolution timer and / or determining whether contention resolution was successful or unsuccessful).

[0246] The wireless device may delay retransmission of one or more of Msg 1 1311, Msg 1 1321, or Msg A 1331 for a particular period of time (e.g., a backoff time). The wireless device may apply the period of time (e.g., a backoff time) to the retransmissions, for example, based on or in response to the RA procedure being contention-based random access (CBRA) (e.g., the preamble is selected by the MAC entity of the wireless device) and / or based on determining that the RA procedure is not complete, e.g., after or in response to successful RAR reception. The backoff time to the retransmissions may be applied (e.g., by the wireless device) based on determining that the RA procedure is not complete after or in response to a contention resolution failure. The wireless device may set the backoff time to 0 milliseconds if the RA procedure is initiated as described in connection with step 2010. The wireless device may set (or update) the backoff time based on, for example, PREAMBLE_BACKOFF, determined by the value of the backoff indicator (BI) field of the MAC sub-PDU, and / or one or more RRC messages indicating a scaling factor (e.g., SCALING_FACTOR_BI). The wireless device may determine the backoff time based on, for example, a uniform distribution between 0 and PREAMBLE_BACKOFF.

[0247] The wireless device may initiate a four-step RA procedure. The wireless device may transmit (e.g., transmit) a preamble (e.g., Msg1 1311) and / or monitor an RAR window to receive Msg2. Msg2 may schedule the transmission of Msg3, which includes a C-RNTI MAC CE. The wireless device may detect a PDCCH addressed to the C-RNTI, for example, while a contention resolution timer (e.g., ra-ContentionResolutionTimer) is running. Based on (e.g., in response to) determining that the RA procedure was initiated by a higher layer (e.g., a MAC sublayer or an RRC sublayer), the wireless device may indicate successful completion of the four-step RA procedure and / or a PDCCH addressed to the C-RNTI indicating an UL grant for a new transmission.

[0248] The wireless device may include a CCCH SDU in Msg3. The wireless device may detect a PDCCH addressed in TEMPORARY_C-RNTI, for example, while the contention resolution timer is running. The wireless device may indicate successful completion of the four-step RA procedure based on (e.g., in response to) determining that Msg4, including the MAC CE's contention resolution identity, matches the CCCH SDU in Msg3.

[0249] The wireless device may initiate a two-step RA procedure. The wireless device may send (e.g., transmit) a C-RNTI (e.g., a C-RNTI MAC CE indicating the C-RNTI) via MsgA. The wireless device may monitor the downlink control channel with the C-RNTI and / or MSGB-RNTI (or RA-RNTI). The wireless device may stop monitoring the downlink control channel with the C-RNTI and / or MSGB-RNTI (or RA-RNTI), for example, based on (e.g., after or in response to) receiving a PDCCH addressed to the C-RNTI. The PDCCH may include a DCI including a downlink assignment. The wireless device may receive a PDSCH (e.g., a MAC PDU), for example, based on the DCI. The received PDSCH (e.g., a MAC PDU) may include a TA command (e.g., a TA MAC CE). The wireless device may stop monitoring the downlink control channel with the C-RNTI and / or MSGB-RNTI (or RA-RNTI), e.g., based on (e.g., after or in response to) receiving a PDCCH addressed to the C-RNTI and / or corresponding PDSCH (or MAC CE) that includes a TA command. The wireless device may determine, e.g., based on reception of the PDCCH, that the two-step RA procedure has completed successfully, that reception of the MsgB has completed successfully, and / or that contention resolution has completed successfully.

[0250] The wireless device may receive at least one response (e.g., a PDCCH addressed to the C-RNTI and / or a PDCCH addressed to the MSGB-RNTI), for example, while monitoring the msgB-ResponseWindow. The wireless device may determine that the two-step RA procedure has completed successfully, for example, based on detecting a PDCCH addressed to the C-RNTI (e.g., included in the MsgA). The PDCCH may indicate a PDSCH (e.g., via a downlink assignment in the DCI) that includes a TA command. The wireless device may determine that the two-step RA procedure has completed successfully, for example, based on determining that a PDCCH addressed to the C-RNTI (e.g., included in the MsgA) is detected. The PDCCH may indicate a PDSCH (e.g., via a downlink assignment in the DCI) that includes an UL grant (e.g., if the wireless device is already synchronized). The PDCCH addressed to the C-RNTI may include an indication of a successful response. The wireless device may detect and / or receive a PDCCH addressed to the MSGB-RNTI. The wireless device may receive and / or decode the PDSCH, for example, based on the downlink assignment (e.g., a response to MsgA). The response to MsgA may include a preamble identifier (e.g., RAPID) that matches the preamble identifier of the preamble that the wireless device sent (e.g., transmitted) to the base station via MsgA. The response to MsgA may include an explicit or implicit indicator indicating a successful RAR or a fallback RAR (e.g., a fallbackRAR MAC sub-PDU). The wireless device may determine that the two-step RA procedure has completed successfully, for example, based on MsgA including a fallbackRAR MAC sub-PDU and / or determining that the RAP was not selected by the MAC entity from among the contention-based RAPs. The wireless device may process the received TA command (e.g., TA MAC CE) and / or UL grant value. The wireless device may indicate the received TA command and / or UL grant value to a lower layer (e.g., the physical layer).

[0251] The wireless device may maintain a counter that counts the number of preamble transmissions (e.g., PREAMBLE_TRANSMISSION_COUNTER). The wireless device may increment the counter by the value of the counter step (e.g., by 1) based on, for example, the RAR reception failing (e.g., thereafter, or in response thereto), and / or based on the contention resolution failing (e.g., thereafter, or in response thereto). The wireless device may determine that the RA procedure has failed. The MAC entity of the wireless device may indicate an RA problem to the upper layer based on, for example, determining that the number of preamble transmissions has reached a configured value (e.g., PREAMBLE_TRANSMISSION_COUNTER = preambleTransMax + 1) (e.g., thereafter, or in response thereto). The wireless device may determine that the RA procedure is not complete. One or more retransmissions of one or more of Msg1 1311, Msg1 1321, or Msg A 1331 may be performed based on, for example, determining that the number of preamble transmissions is less than a configured value (e.g., PREAMBLE_TRANSMISSION_COUNTER < preambleTransMax + 1) (e.g., in response thereto).

[0252] Figure 21 illustrates various NTN platforms. An NTN (e.g., a satellite network) may use spacecraft to carry communications equipment relay nodes (e.g., radio remote units) or base stations (e.g., an NTN base station). An NTN may include a network or network segment. A terrestrial network may be a network located on the Earth's surface. An NTN may be a network that uses NTN nodes (e.g., satellites) as an access network, a backhaul interface network, or both. An NTN may include one or more NTN nodes (or spacecraft). An NTN node may carry a bent-pipe payload (e.g., a transparent payload) or a regenerative payload. An NTN node with a transparent payload may include transmitter / receiver circuitry without onboard signal processing (e.g., digital signal processing such as modulation and / or encoding). An NTN node may include a regenerative payload (e.g., an NTN base station) transmitter / receiver circuitry with onboard processing capacity. The onboard processing capacity may be used to demodulate and / or decode received signals and / or regenerate signals before transmitting them to Earth.

[0253] NTN nodes may include satellites, balloons, aircraft, high altitude platform stations (HAPS), and / or unmanned aerial systems (UAS). For example, the UAS may be a limp, a quasi-geostationary (or geostationary) HAPS, or a pseudosatellite station (e.g., a HAPS). Satellites may be deployed in low Earth orbit (LEO) at altitudes between 250 km and 1500 km with orbital periods ranging from 90 to 130 minutes. From the perspective of a given point on the Earth's surface, the location of a LEO satellite may change. Satellites may be deployed in medium Earth orbit (MEO) at altitudes between 5000 and 20000 km with orbital periods ranging from 2 hours to 14 hours. Satellites may be deployed in geosynchronous Earth orbit (GEO) at an altitude of 35,786 km and directly above the equator. From the perspective of a given point on the Earth's surface, the location of a GEO may not move.

[0254] FIG. 22 illustrates exemplary communications in an NTN. An NTN may include one or more transparent NTN platforms (e.g., nodes). An NTN node (e.g., a satellite) may forward received signals from another satellite (e.g., via an inter-link satellite communication link) or a gateway on the ground (e.g., via a feeder communication link) to Earth. The gateway may be collocated with a base station (e.g., an NTN base station) or may be located separately from the base station. An NTN node may forward received signals from a radio device on Earth to another NTN node or a terrestrial gateway. The signals may be forwarded with amplification and / or a shift between the service link frequency (point or bandwidth) and the feeder link frequency.

[0255] An NTN node may generate one or more beams over a given area (e.g., a coverage area or cell). The footprint of a beam (or cell) may be referred to as a spot beam. The cell / beam footprint may move on the Earth's surface due to satellite movement (e.g., LEO with a moving cell or HAPS with a moving cell). The cell / beam footprint may be Earth-fixed with some beam-pointing mechanism used by the satellite to compensate for satellite movement (e.g., LEO with an Earth-fixed cell). As shown in Figure 21, the size of the spot beam may depend on the system design and can range from tens of kilometers to thousands of kilometers.

[0256] Propagation delay (e.g., between a satellite and the ground, or between multiple satellites) may be the amount of time it takes for a signal head to travel from a source (e.g., an NTN base station or NTN node) to a receiver (e.g., a wireless device), or vice versa. For the uplink, the source may be a wireless device and the receiver may be a base station / access network (e.g., an NTN base station). For the downlink, the source may be a base station / access network (e.g., an NTN base station) and the receiver may be a wireless device. Propagation delay may change as the distance between the sender and receiver changes (e.g., due to movement of the NTN node, movement of the wireless device, inter-satellite links, and / or feeder link switching).

[0257] One or more reference points may be used in the NTN architecture. The configuration of the one or more reference points may indicate uplink timing synchronization (e.g., whether UL and DL frames are aligned at the base station), delay pre-compensation by the base station for UL communications, delay pre-compensation by the wireless device for UL communications, and / or epoch time for satellite ephemeris data. The one or more reference points in the NTN may enable the wireless device to perform one or more of: determining (e.g., estimating / calculating / measuring) a propagation delay (e.g., in a service link), determining (e.g., maintaining / tracking) a propagation delay (or RTD), and / or determining the transmit timing of a UL transmission scheduled by a DCI or the action time of a MAC CE.

[0258] A base station may configure reference point 2201 at a cell / beam center (Case 1). In Case 1, reference point 2201 may be on the ground. Reference point 2201 may have a higher altitude than the wireless devices in the cell / beam (e.g., to minimize propagation delay from the NTN node or base station to reference point 2201 in the cell / beam). Reference point 2201 may have an altitude above civil aviation flight height. A base station may configure reference point 2202 at an NTN node (Case 2). In Case 2, uplink timing synchronization may be achieved at the NTN node, for example, if the UL and DL frames are not aligned at the base station. A base station may configure reference point 2203 in a feeder link between an NTN node and a gateway (Case 3). In Case 3, a base station may configure the location of reference point 2203 so that the propagation delay pre-compensated by the base station remains fixed despite movement of the NTN node (e.g., a LEO satellite with an Earth-fixed cell). The base station may configure a reference point 2204 at the gateway (Case 4). In Case 4, the reference point 2204 may be considered an auxiliary reference point so as not to expose the location of the gateway to the wireless device (e.g., for security reasons). The wireless device may determine (e.g., measure / calculate) the feeder link delay without knowledge of the exact location of the gateway by determining the auxiliary reference point and a preset compensation time window. The base station may configure a reference point 2205 at the base station (Case 5). In Case 5, the UL frame and the DL frame may be aligned at the base station (e.g., an NTN base station).

[0259] The propagation delay between the base station and the reference point in FIG. 22 may be referred to as the common delay of the cell / beam (e.g., the delay experienced by all wireless devices in the cell / beam). The base station may provide a value for the common delay to all wireless devices in the cell / beam, for example, via broadcast signaling (e.g., SIB1). A GNSS-capable wireless device may need to estimate the propagation delay (or service link delay) based on one or more measurements. The propagation delay may include the common delay and one or more other delays. The one or more measurements may indicate GNSS-acquired position information of the wireless device. The one or more measurements may enable the wireless device to determine (e.g., calculate / estimate) the propagation delay using the GNSS-acquired position and satellite ephemeris data / information. The one or more measurements may enable the wireless device to determine (e.g., calculate / estimate) the propagation delay using the GNSS-acquired position and one or more reference points. The one or more measurements may enable the wireless device to determine, estimate / calculate the propagation delay via one or more timestamps (e.g., the timestamps of configured broadcast signals). The one or more measurements may enable the wireless device to determine (e.g., estimate / measure) a variation rate at which the common delay changes over a period of time. The wireless device may determine (e.g., calculate) a drift rate of the common delay based on, for example, the determined (e.g., estimated / measured) rate of variation of the common delay. The one or more measurements may enable the wireless device to determine (e.g., estimate / measure) a variation rate (e.g., using satellite ephemeris data) at which the service link delay may change over a period of time. The wireless device may determine (e.g., calculate) a drift rate of the service link delay based on the determined (e.g., estimated / measured) rate of variation of the service link delay. For wireless devices without GNSS capability (or when GNSS accuracy cannot be precise), the base station may configure the common delay equal to the maximum link of the cell / beam. The common delay may be for a group of wireless devices without GNSS capability.Additionally or alternatively, the common delay may be a portion of the propagation delay experienced by a group of wireless devices (eg, the feeder link delay plus a portion of the service link delay).

[0260] The differential delay within a satellite beam / cell may be determined (e.g., calculated) based on, for example, the maximum diameter (e.g., maximum delay link) of the beam / cell footprint at its nadir. The differential delay may indicate the maximum difference between communication delays that two wireless devices may experience while communicating with an NTN node (e.g., an NTN base station). As described herein, an NTN node (e.g., an NTN base station) may include one or more terrestrial base stations and / or satellite base stations. The differential delay may indicate the difference between communication delays experienced by wireless device 2210 and wireless device 2220. Wireless device 2210 may be located near the center of the cell / beam. Wireless device 2220 may be located near the edge of the cell / beam. Wireless device 2210 may experience a smaller RTD compared to wireless device 2220. A link to the edge of the cell / beam may experience the maximum propagation delay in the cell / beam. A link to the center of the cell / beam may experience the minimum propagation delay in the cell / beam. For a LEO satellite, the differential RTD may be 3.12 milliseconds.

[0261] The base station may not configure the reference point. The wireless device may assume the reference point is located at an NTN node based on determining that the reference point is not configured by the base station. The base station may indicate a portion of the propagation delay that the wireless device is expected to pre-compensate for. The indication may be transmitted via the BSI. The wireless device may pre-compensate for the service link delay and / or a portion of the service link delay based on determining that one or more reference points are not configured.

[0262] FIG. 23 shows an example of various propagation delays. The various propagation delays may correspond to NTN nodes at different altitudes. The propagation delay may refer to one-way delay. The one-way delay may be, for example, the amount of time required for a signal to propagate through a communication system, from a transmitter to a receiver. For a transparent NTN, the RTD may include the service link delay (e.g., between the NTN node and the wireless device), the feeder link delay (e.g., between the NTN gateway and the NTN node), and / or the delay between the gateway and the base station (e.g., if the gateway and NTN base station are not co-located). The RTD may be, for example, four times the one-way delay for a GEO satellite with a transparent payload. For example, as shown in FIG. 23, the one-way delay may be between the wireless device and the satellite, and the RTD may be four times the one-way delay. Additionally or alternatively, if the one-way delay corresponds to the delay between the wireless device and the base station, the RTD may be twice the one-way delay. For example, the one-way delay for a GEO satellite may be 138.9 milliseconds. The RDT for a GEO satellite may be approximately 556 milliseconds. The RTD of a terrestrial network may be less than 1 millisecond. The RTD of a GEO satellite may be hundreds of times longer than that of a terrestrial network. The RTD of a terrestrial network (e.g., NR, E-UTRA, LTE) may be negligible compared to the RTD of an NTN. In at least some systems, the maximum RTD for a LEO satellite with a transparent payload at an altitude of 600 km may be 25.77 milliseconds, and / or for a LEO satellite with a transparent payload at an altitude of 1200 km, the maximum RTD may be 41.77 milliseconds.

[0263] FIG. 24 illustrates an example of a timing advance (TA) report in a non-terrestrial network (NTN). A TA report procedure may be triggered when at least one condition is met. A wireless device may transmit TA report information (e.g., to a base station). The wireless device may transmit the TA report information, for example, based on the triggered TA report procedure. The base station may transmit a timing offset (e.g., a device-specific timing offset) (e.g., based on the TA report information). The timing offset may be used to determine a device-specific timing offset. The device-specific timing offset may be used as a TA while the wireless device is communicating with a base station, for example, in an NTN.

[0264] In step 2410, the wireless device may receive one or more configuration messages from the base station (e.g., at or after time T0). The one or more configuration messages may include one or more first configuration messages, one or more second configuration messages, and / or one or more third configuration messages. The one or more configuration parameters may be received via a broadcast information system (SIB). The one or more first configuration messages may include / indicate one or more of the following configuration parameters: PUCCH resources, RACH configuration, one or more BSR configurations, multiple SR configurations, and / or multiple configured grant configurations. The second configuration message may include / indicate one or more configuration parameters that facilitate and / or manage the determination (e.g., calculation) of propagation delay and / or TA (e.g., at the wireless device). The second configuration message may include one or more satellite ephemeris parameters, one or more common delay (e.g., network-controlled common delay) parameters, one or more TA parameters, one or more reference points, one or more validity periods (also referred to as validity windows, verification periods, and / or verification windows), one or more timing offset parameters, and / or one or more TA margins. The one or more third configuration messages may include one or more TA report configuration parameters.

[0265] The one or more timing offset parameters may include one or more first timing offset parameters (e.g., first timing offset parameters) corresponding to a cell-specific propagation delay. A base station may determine (e.g., calculate or configure) the first timing offset parameters as a function of a maximum propagation delay of the cell. A wireless device may determine (e.g., calculate or maintain) a cell / beam-specific timing offset, for example, based on the first timing offset parameters. A wireless device may determine (e.g., track, update, or maintain) a cell / beam-specific timing offset based on receiving the first timing offset parameters from a base station. The first timing offset parameters may be updated by the base station.

[0266] The one or more timing offset parameters may include a second timing offset parameter corresponding to one or more beam-specific timing offsets. Each of the one or more beam-specific timing offsets may correspond to one or more maximum propagation delays of one or more corresponding beams within the cell. The nth input of the one or more beam-specific timing offsets may correspond to the maximum propagation delay of the nth beam (e.g., a virtual beam) of the cell, for example, if the cell includes two or more beams indexed by n. The nth input of the one or more beam-specific timing offsets may indicate the difference between the maximum propagation delay of the cell (e.g., indicated in the first timing offset parameter) and the maximum propagation delay of the nth beam of the cell. The wireless device may determine the cell / beam-specific timing offset based on, for example, the second timing offset parameter and / or the first timing offset parameter. The wireless device may determine the cell-specific timing offset or the beam-specific timing offset based on, for example, a beam indicator / index indicating a beam used for communication with a base station (or NTN node) within the cell.

[0267] The one or more timing offset parameters may include one or more third timing offset parameters (e.g., third timing offsets). The third timing offset parameter may indicate a portion of propagation delay that the base station may pre-compensate for, for example, in an NTN scenario with transparent NTN nodes and / or when the UL and DL frames are not aligned at the base station. The third timing offset parameter may indicate a difference between the UL frame timing and the DL frame timing, for example, when the UL and / or DL frames are not aligned at the base station. The third timing offset parameter may not be present in the second configuration parameters, for example, in an NTN with transparent NTN nodes. The wireless device may set the K_mac timing offset to 0 based on determining that the third timing offset parameter is not indicated in the second configuration message.

[0268] The one or more reference points may be used by a wireless device to determine uplink timing synchronization, determine (e.g., measure or calculate) feeder link delay (e.g., without knowing the location of the gateway), determine service link delay (or a portion of the service link delay), determine UL / DL frame alignment, and / or determine (e.g., measure) the epoch time of satellite ephemeris parameters.

[0269] The one or more validity periods may include a first validity period indicating a validity period during which position (e.g., location) information in the GNSS acquisition data is considered accurate. The first validity period may indicate a maximum period during which the acquired GNSS position information is valid (e.g., conforming to required accuracy requirements and / or maximum allowable error). The GNSS position information may be acquired by the wireless device. The wireless device may restart the first validity period based on (e.g., in response to, or thereafter) acquiring new GNSS position information (e.g., data). The wireless device may acquire new GNSS position information (e.g., based on determining that the first validity period has expired). The wireless device may (re)initiate the first validity period / window if (e.g., thereafter) new GNSS position information is acquired.

[0270] Transmissions from different wireless devices within a cell / beam may be time-aligned at the base station and / or NTN node (e.g., satellite) to maintain uplink orthogonality. Time alignment / synchronization may be achieved by using different TA values at different wireless devices to compensate for their different propagation delays (e.g., RTD). A wireless device may determine (e.g., calculate / measure / maintain) a current TA value (and / or round-trip transmission delay (RTT) between the wireless device and the base station), for example, based on a combination of closed-loop TA procedure / control and open-loop TA procedure / control. The closed-loop TA procedure / control may be based on receiving a TA (e.g., absolute TA) command. The TA command may be received from a base station. The TA command may be received from a MAC CE or Msg2 1312 (or MsgB 1332). A wireless device may determine (e.g., maintain / calculate) a closed-loop TA value based on receiving (e.g., in response to, or after) each TA command MAC CE. The open-loop TA procedure / control may be based on the GNSS-acquired position of the wireless device and / or the second configuration message. Combining the closed-loop TA control / procedure and the open-loop TA procedure / control may include, for example, resetting the closed-loop TA value (e.g., the accumulated closed-loop TA value) to a predefined value (e.g., 0) when a new GNSS-acquired position becomes available and / or when the wireless device acquires (e.g., reads) the second configuration message. Combining the closed-loop TA control and the open-loop TA control may include adding the open-loop TA value (e.g., derived / calculated based on the open-loop TA procedure / control) to the closed-loop TA value (or a portion of the closed-loop TA procedure / control).

[0271] The one or more TA margins (if provided) may be used by the wireless device to compensate for one or more errors induced, for example, while measuring / calculating (e.g., autonomously) the propagation delay and / or current TA value at the wireless device. The base station may configure the one or more TA margins based on pre-correction accuracy requirements and / or UL timing synchronization requirements. The wireless device may adjust its current TA value based on the one or more TA margins, for example, to transmit (e.g., transmit) a preamble in an RA procedure. If the one or more TA margins are not provided, the wireless device may expect to receive a TA command (e.g., via the TAC field of Msg2 1312 or MsgB 1332) with either a positive value (e.g., via a bipolar TA command field) or a negative value to account for an underestimation or overestimation of the propagation delay at the wireless device, respectively.

[0272] The satellite almanac parameters may include satellite ephemeris information (e.g., data), an epoch time of the satellite ephemeris information, a second validity period, and / or one or more drift rates corresponding to the satellite ephemeris information. The one or more drift rates may indicate one or more fluctuation rates of the satellite position / movement associated with orbital decay / atmospheric drag. The wireless device may use the satellite ephemeris parameters to determine (e.g., measure / calculate / maintain) the satellite's movement pattern, determine (e.g., estimate / measure) the service link delay, and / or adjust the current TA value (e.g., via an open-loop TA procedure / control). The wireless device may determine, for example, based on an implemented orbit predictor / propagator model. The one or more drift rates may include a drift rate (e.g., first-order drift rate), a rate of fluctuation of the drift rate (e.g., second-order drift rate), and / or a rate of fluctuation of the second-order drift rate (e.g., third-order drift rate). The satellite ephemeris information may be configured in one or more satellite ephemeris formats.

[0273] The wireless device may determine (e.g., maintain / calculate / update) a propagation delay (e.g., service link delay or open-loop TA value). The determination may be based on one or more satellite ephemeris parameters (e.g., one or more drift rates). The second validity period may indicate a validity time of the ephemeris (e.g., satellite almanac) parameters. The wireless device may skip frequent acquisition (e.g., reading) of the second configuration message during the second validity period. The wireless device may not acquire new satellite ephemeris data during the second validity period. The second validity period may indicate (e.g., specify) a maximum period (e.g., corresponding to an orbit predictor / propagator model the wireless device is using to determine a maximum tolerable error in determining the propagation delay and / or open-loop TA value) during which the wireless device will not update (e.g., read or acquire) the satellite ephemeris parameters. The wireless device may start (e.g., restart) a timer corresponding to the second validity period, e.g., based on (in response to, or after) acquiring new satellite ephemeris data.

[0274] The one or more TA parameters may indicate a common TA (e.g., common delay), a third validity period (e.g., common TA verification period), and / or one or more higher-order (e.g., first-order, second-order, and / or third-order) drift rates of the common TA. The common TA may be indicated based on a predefined granularity, e.g., one slot or a TAC MAC CE granularity. The third validity period may indicate a maximum period during which the wireless device does not need to acquire the common TA or the open-loop TA. The third validity period may indicate a maximum period during which the wireless device does not acquire a new second configuration message. If the third validity period is not present in the second configuration message, the wireless device may set the third validity period, e.g., based on the second validity period. The second-order drift rate of the common TA may indicate a rate of variation at which the drift rate of the common TA changes over a predefined period (e.g., the third validity period). The tertiary drift rate of the common TA may exhibit a rate of variation corresponding to the secondary drift rate of the common TA, whereby the secondary drift rate of the common TA changes over a predefined period (e.g., a third valid period).

[0275] The wireless device may initiate (e.g., re-initiate) the second validity period, for example, based on (e.g., thereafter or in response to) receiving / reading new satellite ephemeris parameters. The wireless device may initiate (e.g., re-initiate) the third validity period, for example, based on (e.g., thereafter or in response to) reading / receiving new common TA parameters and / or a new common TA. The wireless device may initiate (e.g., re-initiate) the first validity period, for example, based on (e.g., thereafter or in response to) obtaining new position information for the wireless device using GNSS data.

[0276] The wireless device may obtain updated satellite ephemeris information based on (e.g., in response to, or after) determining that the second validity period has expired. The wireless device may obtain updated common TA based on (e.g., in response to, or after) determining that, for example, the third validity period has expired. The wireless device may obtain updated GNSS position information based on (e.g., in response to, or after) determining that, for example, the first validity period / window has expired.

[0277] The wireless device may determine (e.g., calculate / measure / update) a current TA value (e.g., open-loop procedure / control) based on (e.g., in response to, or after) receiving (e.g., reading) updated satellite ephemeris information, updated common TA, and / or updated GNSS position information. The wireless device may update the current TA value based on, for example, a closed-loop TA procedure / control. The closed-loop TA procedure / control may be based, for example, on receiving a TAC MAC CE.

[0278] The wireless device may set the common TA to zero, for example, based on (e.g., in response to, or subsequently to) determining that the common TA parameter is not present in the second configuration message. The wireless device may not pre-compensate the common TA, for example, if UL timing synchronization is maintained at the NTN node. The wireless device may not pre-compensate the common TA, for example, for an NTN with a transparent payload NTN node (e.g., a LEO satellite).

[0279] The base station may periodically broadcast (e.g., every 160 milliseconds) the second configuration message and / or the third configuration message (e.g., via an SIB). The wireless device may determine not to acquire and / or read the second configuration message, for example, based on determining that the second validity period (and / or the third validity period) is configured and that the second validity period (and / or the third validity period) is greater than the periodicity (e.g., broadcast) at which the second configuration message is transmitted. The wireless device may determine not to read and / or acquire the second configuration message, for example, when the second validity period (and / or the third validity period) is executed. The periodicity at which the wireless device may acquire the second configuration message may be determined (e.g., by the wireless device) based, for example, on whether one or more drift rates (e.g., one or more drift rates of satellite ephemeris parameters and / or one or more drift rates of common TA parameters) are configured. The wireless device may, for example, skip reading / acquiring the second configuration message for a time window during which the inaccuracy of the currently maintained / estimated propagation delay is deemed acceptable if one or more drift rates of the common TA (and / or one or more drift rates of the satellite ephemeris parameters) are configured. The wireless device may, for example, periodically acquire the second configuration message based on determining that the second validity period (and / or the third validity period) is not configured.

[0280] The wireless device may (e.g., autonomously) determine (e.g., adjust / update / recalculate) a current TA value based on, for example, one or more drift rates (if provided). The base station may reduce signaling overhead (e.g., to calculate / maintain an open-loop TA value) by providing (via the second configuration message) at least one or more drift rates and / or at least one or more variation rates. The wireless device may determine (e.g., maintain / track) a change in propagation delay (or open-loop TA value) over a period of time (e.g., 3 seconds). The wireless device may determine (maintain / track) a change in propagation delay (or open-loop TA value) over a long period of time (e.g., 35 seconds) if, for example, one or more drift rates are provided and one or more variation rates for one or more drift rates are provided. The change in propagation delay may depend on how many drift rates are configured (e.g., 3 seconds may be used if one drift rate is configured, 35 seconds may be used if three drift rates are configured, or any other amount of drift rate may correspond to any other duration). Additionally or alternatively, a validity timer (e.g., a second validity timer, a third validity timer, or an nth validity timer, where n can be any quantity) may indicate a value of a change in propagation delay. The base station may indicate one or more configuration parameters (e.g., to increase the ability of the wireless device to determine (e.g., track / maintain) the change in propagation delay). The one or more configuration parameters may correspond to a third order approximation of feeder link delay, a third order approximation of satellite motion, a third order approximation of common delay, etc.

[0281] In step 2420, the wireless device may transmit (e.g., transmit) TA report information to the base station. The TA report information may include device-specific TA information. The TA report information may be based on the wireless device's current TA value and / or location information of the wireless device. The TA report information may indicate one or more of the following: the current TA value, a portion of the propagation delay calculated / measured autonomously by the wireless device, a portion of the propagation delay pre-compensated by the wireless device, a service link delay, a propagation delay between the wireless device and a configured reference point (e.g., shown based on one or more reference points as described in connection with FIG. 22 ), a difference between a measurement calculated by the wireless device (based on the current TA value) and a device-specific timing offset, a difference between the calculated measurement and a cell / beam-specific timing offset, a propagation delay between the base station and the wireless device, an open-loop TA value, a portion of the open-loop TA value (e.g., a portion calculated / maintained autonomously by the wireless device), location information of the wireless device, a difference between a cell / beam-specific timing offset and the current TA value, and / or a difference between a device-specific timing offset and the current TA value. The location information of the wireless device may include a quantified location of the wireless device or a change in the location of the wireless device. The description provided regarding the TA report information should not be considered limiting to the examples provided in this disclosure, and those skilled in the art will recognize that variations of the TA report information may also be applied to the examples described herein.

[0282] A wireless device may send (e.g., transmit) TA report information via a MAC CE command (e.g., TA report MAC CE) or RRC signaling (e.g., an RRC reconfiguration message). The TA report information may be sent, for example, based on a network request (e.g., a MAC CE command and / or DCI) or during initial access. As discussed in more detail below, the TA report information may also be based on a triggered TA reporting procedure.

[0283] A base station may configure a logical channel for the TA report information (e.g., corresponding to RRC signaling or a MAC CE command). A base station may configure the logical channel for the TA report information with a preset priority. A wireless device may transmit (e.g., transmit) the TA report information 2420 / 2460 via available UL-SCH resources. The availability of UL-SCH resources for transmitting (e.g., transmitting) the TA report information may be based on, for example, a logical channel prioritization procedure. A configured grant (e.g., Type 1 and / or Type 2), a random access procedure, and / or an SR for a BSR procedure may be used to transmit (e.g., transmit) the TA report information.

[0284] To send (e.g., transmit) TA report information during initial access (e.g., while the wireless device is performing / initiating random access in RRC_IDLE and / or RRC_INACTIVE state), the wireless device may be configured to send (e.g., transmit) the TA report information to the base station via an RA procedure. The configuration may be based on information in a third configuration message. The wireless device may be configured to not send TA report information to the base station via an RA procedure, for example, when the wireless device is in RRC_CONNECTED mode.

[0285] In step 2430, the wireless device may receive a timing offset. The timing offset may be received from a base station. For example, as shown in FIG. 24, the wireless device may receive the timing offset at time T2. The timing offset may be determined (e.g., calculated) by the base station based on, for example, TA report information (e.g., received from the wireless device).

[0286] A base station may calculate a timing offset based on, for example, location information of a wireless device. The base station may provide a timing offset to, for example, improve UL data transmission efficiency (e.g., reduce transmission delay) of a wireless device. For example, when a wireless device is located near a cell center or a beam center (e.g., wireless device 1 in FIG. 22), the difference between the cell / beam-specific timing offset and the propagation delay of the wireless device may be significant (e.g., close to the differential delay of the cell / beam).

[0287] The wireless device may receive a message (e.g., an RRC message or a MAC CE command) including updated information corresponding to (e.g., indicating) the timing offset, for example, in response to the TA report information. The updated information (e.g., timing offset 2430 and / or timing offset 2470) may indicate the difference between the cell / beam-specific timing offset and the timing offset, or the difference between the device-specific timing offset and the timing offset. The base station may determine / calculate the device-specific timing offset. The device-specific timing offset may be greater than the wireless device's current / previous TA value and / or less than the cell-specific timing offset.

[0288] The timing offset may be indicated by a message (e.g., RRC signaling or a MAC CE command). The RRC signaling may include an RRC reconfiguration message. The MAC CE command may include a timing offset MAC CE command (e.g., a Koffset_UE MAC CE command).

[0289] In step 2440, the wireless device may determine (e.g., maintain, set, or calculate) a device-specific timing offset (e.g., Koffset_UE) based on the timing offset. The timing offset may be the same as the device-specific timing offset. The received timing offset may be different from the device-specific timing offset.

[0290] The wireless device may determine that the device-specific timing offset is unavailable / not maintained, for example, at time T2 when the wireless device receives timing offset 2430. The device-specific timing offset may be available / maintained after the initial access procedure and / or before time T2. The device-specific timing offset may not be available / maintained to the wireless device at time T2, for example, if the wireless device discarded / deleted the wireless device-specific timing offset by time T2 and / or if the wireless device did not receive a timing offset from the base station via one or more previous communications.

[0291] The wireless device may calculate a device-specific timing offset, for example, based on (e.g., in response to, or after) receiving a timing offset. For example, the wireless device may determine a device-specific timing offset based on a timing offset from a base station. The wireless device may determine (e.g., maintain / calculate) a device-specific timing offset based on a timing offset from the base station, a previous device-specific timing offset, a third timing offset parameter, and / or a cell / beam-specific timing offset. For example, the wireless device may determine a new device-specific offset from a previous / current device-specific offset (e.g., a maintained / available device-specific timing offset) and the timing offset received from the base station.

[0292] The wireless device may be configured to report TA report information in response to or after a report request (e.g., DCI or MAC CE) received from a base station based on a third configuration message (e.g., a TA report configuration message). The configuration may occur while the wireless device is in an RRC_CONNECTED state. The wireless device may determine (e.g., calculate / measure) a current TA and transmit the TA report information, e.g., based on the report request. The wireless device may be configured to periodically report the TA report information, e.g., based on the third configuration message. The third configuration message may indicate the periodicity at which the TA report information is transmitted (e.g., transmitted) and / or the UL-SCH resource (e.g., a Type 1 or Type 2 configured grant) for transmitting (e.g., transmitting) the TA report information.

[0293] The third message may indicate at least one TA condition for triggering the TA reporting procedure. For example, the at least one TA condition may include a first TA condition corresponding to a change in the current TA value and / or a second TA condition corresponding to a difference between the device-specific timing offset and the current TA value. The change in the current TA value may be determined, for example, based on the difference between the current TA value and a previous TA value. The previous TA value may be determined (e.g., calculated / measured) before the current TA value. For example, the previous TA value may correspond to the last TA reporting information. The TA reporting procedure may be triggered based on a first TA condition, for example, that the current TA value is greater (or less) than the previous TA value (e.g., if the variation between the current TA value and the previous TA value is greater than a threshold value) and / or that the change in the current TA value is greater (or less) than a threshold value. The TA reporting procedure may be triggered based on a second TA condition, for example, that the difference between the device-specific timing offset and the current TA value is less than a second threshold value.

[0294] At step 2450, the wireless device may trigger a TA reporting procedure at time T3, e.g., based on at least one TA condition being met. At step 2460, the wireless device may send (e.g., transmit) TA report information, e.g., based on the triggered TA report. The TA report information may be sent using available UL-SCH resources. Step 2460 may be implemented similarly to that described in step 2420. At step 2470, the wireless device may receive a timing offset. Step 2470 may be implemented similarly to that described in step 2430. At step 2480, the wireless device may determine a device-specific timing offset. Step 2480 may be implemented similarly to step 2440.

[0295] The cell / beam-specific timing offset and / or device-specific timing offset may be used by the wireless device to ensure / guarantee causality of uplink grants (e.g., scheduled by DCI). The wireless device may use the cell / beam-specific timing offset and / or device-specific timing offset to determine the timing of UL transmissions. The UL transmissions may be scheduled by DCI, HARQ-ACK / NACK on the PUCCH corresponding to the PDSCH scheduled by the DCI, HARQ-ACK on the PUCCH corresponding to the stop of semi-persistent scheduling indicated via the PDCCH, transmission opportunities of configured grants (e.g., type 2 configured grants), and / or PRACH opportunities for transmission of preambles ordered by the PDCCH.

[0296] The wireless device may use the cell / beam-specific timing offset (if available or maintained) to determine the transmission timing of one or more of: a random access response (RAR) grant-scheduled PUSCH (e.g., based on or in response to receiving Msg2 1312 in a four-step RA procedure), a fallbackRAR grant-scheduled PUSCH (e.g., based on or in response to receiving MsgB 1332 in a two-step RA procedure), an Msg3 1313 retransmission scheduled by DCI format 0_0 with / having CRC parity bits scrambled by TC-RNTI, a HARQ-ACK on the PUCCH indicating successful contention resolution, and / or a PRACH opportunity for the transmission of a preamble ordered by the PDCCH. The contention resolution PDSCH may be scheduled by DCI format 0_1 with CRC parity bits scrambled by the TC-RNTI in an RA procedure or by DCI format 0_1 with / with CRC parity bits scrambled by the TC-RNTI in a two-step RA procedure.

[0297] If a cell / beam-specific timing offset and / or a device-specific timing offset is available / maintained, the wireless device may refrain from using the beam-specific timing offset to determine the scheduling time of the PUSCH transmission. The PUSCH transmission may be scheduled by one or more of the RAR UL grant, the fallbackRAR UL grant for the RACH procedure, and / or the PUSCH grant scheduled by the PDCCH addressed to the TC-RNTI. The wireless device may use the device-specific timing offset (if available or maintained) to determine the scheduling / transmission time of a scheduled RAR grant or fallbackRAR grant, the transmission timing of an aperiodic SRS scheduled by the first DCI, the transmission timing of a CSI report via a PUSCH scheduled by the second DCI with respect to the CSI reference resource timing corresponding to the CSI reference resource timing, the HARQ-ACK / NACK on the PUCCH corresponding to the contention resolution PDSCH scheduled by detecting the third DCI, the HARQ-ACK on the PUCCH corresponding to the stop of semi-persistent scheduling indicated via the PDCCH, and / or the UL grant that cannot be one or more of the first transmission opportunities of a configured grant (e.g., a type 2 configured grant) (e.g., the wireless device may need to use the cell-specific timing offset even if a device-specific timing offset is indicated, for example, in the following cases): The third DCI may be DCI format 0_1 with / having CRC parity bits scrambled by the TC-RNTI or DCI format 0_1 with / having CRC parity bits scrambled by the TC-RNTI.

[0298] The wireless device may use a device-specific timing offset (if available or maintained) to determine the scheduling timing of an UL grant scheduled by a PDCCH. The UL grant may be scrambled / addressed by a C-RNTI, MCS-RNTI, or CS-RNTI. The wireless device may use a device-specific timing offset (if available or maintained) to determine the scheduling timing of a HARQ-ACK / NACK on a PUCCH scheduled by a PDCCH that is not addressed by at least one of a TC-RNTI, RA-RNTI, and / or MSGB-RNTI.

[0299] The wireless device may obtain (ensure / guarantee) the correct activation time (or radio assumption in the downlink configuration, or radio assumption in the uplink configuration) of a MAC CE command (e.g., PUCCH spatial related activation / deactivation MAC CE, semi-persistent CSI report for PUCCH activation / deactivation MAC CE, TAC MAC CE, periodic CSI trigger state sub-selection), for example, based on at least a cell / beam-specific timing offset, a device-specific timing offset, and / or a reception time of a PDSCH carrying the MAC CE command in the downlink configuration.

[0300] When the wireless device transmits (e.g., transmits) a PUCCH with HARQ-ACK information in uplink slot n (e.g., based on a TA value) corresponding to a PDSCH carrying a MAC CE command on the uplink configuration, the wireless device's actions and / or assumptions regarding the downlink configuration are

number

number

[0301] The actions and / or assumptions of the radio device on the uplink configuration are

number

number

Claims

1. 1. A method comprising: receiving, by the wireless device, one or more scheduling request (SR) configuration parameters corresponding to the timing advance (TA) report; triggering an SR based on the one or more SR configuration parameters and based on a triggered TA reporting procedure; transmitting the triggered SR over an uplink channel.

2. receiving an indication of the duration; starting a timer corresponding to the duration based on the triggered TA reporting procedure; the expiration of said timer, or 10. The method of claim 1, further comprising: canceling the triggered TA reporting procedure based at least one of receiving a timing offset from a base station.

3. transmitting a Medium Access Control (MAC) Protocol Data Unit (PDU) including TA report information associated with the triggered TA report procedure; or 10. The method of claim 1, further comprising at least one of transmitting a MAC Control Element (MAC CE) including TA report information associated with the triggered TA reporting procedure.

4. receiving the one or more SR configuration parameters corresponding to a TA report includes receiving one or more RRC messages; 4. The method of claim 3, wherein the RRC message includes the one or more SR configuration parameters corresponding to a TA report and one or more second SR configuration parameters corresponding to a TA report.

5. 2. The method of claim 1, further comprising transmitting TA report information associated with the triggered TA reporting procedure, wherein the transmitting of the TA report information is by the wireless device to a base station and via a non-terrestrial network (NTN).

6. transmitting TA report information associated with the triggered TA reporting procedure, the TA report information comprising: a current TA value associated with the wireless device; a propagation delay associated with communication between the wireless device and a base station; a propagation delay associated with communications between the wireless device and a reference point in the network; the location of the wireless device; or The method of claim 1 , including at least one device-specific timing offset associated with the wireless device.

7. receiving a timing offset; 10. The method of claim 1, further comprising: canceling the triggered TA reporting procedure based on the reception of the timing offset.

8. 1. A method comprising: transmitting, by the base station, one or more scheduling request (SR) configuration parameters corresponding to the timing advance (TA) report; receiving a first SR for transmission of TA report information; transmitting an uplink grant indicating an uplink channel based on the first SR; receiving the TA report information via the uplink channel.

9. transmitting an indication of the duration; starting a timer corresponding to said duration based on a triggered TA reporting procedure; the expiration of said timer, or 10. The method of claim 8, further comprising: canceling the triggered TA reporting procedure based on at least one of transmitting a timing offset to a wireless device.

10. receiving the TA report information, receiving a Medium Access Control (MAC) Protocol Data Unit (PDU) containing the TA report information; or 10. The method of claim 8, comprising at least one of receiving a MAC Control Element (MAC CE) including the TA report information.

11. The method of claim 10, wherein transmitting the one or more SR configuration parameters corresponding to a TA report comprises transmitting one or more RRC messages; 11. The method of claim 10, wherein the RRC message includes the one or more SR configuration parameters corresponding to a TA report and one or more second SR configuration parameters corresponding to a TA report.

12. 10. The method of claim 8, wherein the receiving the TA report information is by the base station, from a wireless device, and via a non-terrestrial network (NTN).

13. one or more processors; and when executed by the one or more processors, the computing device: A memory storing instructions for carrying out the method of any one of claims 1 to 7.

14. 1. A system comprising: A wireless device configured to perform the method according to any one of claims 1 to 7; A base station configured to implement the method of any one of claims 8 to 12.

15. At runtime, A computer readable storage medium having stored thereon instructions for carrying out the method of any one of claims 1 to 7.

Images