Configuration for wireless communication in inactive or idle states

Abstract

To provide methods, wireless devices, systems and computer-readable mediums which provide advantages such as reduced signaling overhead, reduced power consumption, and / or reduced latency.SOLUTION: A method comprises: receiving an RRC release message comprising an indication of a configured uplink grant to transmit uplink data via a cell and in an RRC inactive state; and, based on at least one system information block message indicating whether a second bandwidth part is configured for a wireless device for uplink data transmission, transmitting, in the RRC inactive state and using an initial bandwidth part instead of the second bandwidth part, uplink data via the configured uplink grant indicated by the RRC release message.SELECTED DRAWING: Figure 29

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims the benefit of U.S. Provisional Patent Application No. 63 / 044,538, filed June 26, 2020. The above-referenced applications are hereby incorporated by reference in their entireties. [Background technology]

[0002] A wireless device typically transmits and receives data during a connected state (e.g., a radio resource control (RRC) connected state). A wireless device typically does not transmit or receive data during an active state (e.g., an RRC inactive state) or an idle state (e.g., an RRC idle state). Summary of the Invention

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

[0004] The base station may configure resources for the wireless device to use during the connected state. Data may be communicated during the connected state of the wireless device using the configured resources. The wireless device may transition to the inactive and / or idle state, for example, if the wireless device does not have a certain amount of data (e.g., greater than a threshold) to transmit to the base station. A release message for transitioning the wireless device from the connected state to the inactive and / or idle state may indicate resource information that the wireless device may use to transmit and / or receive data in the inactive and / or idle state. By including such information in the release message, the wireless device may: During inactivity and / or idle states without the need to return to a connected state, It may be possible to send and / or receive data such as small data transmissions (e.g., instant messaging, push notifications, sensor data, etc.), which may provide advantages such as reduced signaling overhead, reduced power consumption, and / or reduced latency.

[0005] These and other features and advantages are described in greater detail below. Certain features are illustrated by way of example, and not by way of limitation, in the accompanying drawings in which like numerals refer to similar elements and in which: [Brief description of the drawings]

[0006] [Figure 1A] 1 illustrates an exemplary communications network. [Figure 1B] 1 illustrates an exemplary communications network. [Figure 2A] 1 illustrates an exemplary user plane. [Figure 2B] 1 illustrates an exemplary control plane configuration. [Diagram 3] 1 shows an example of a protocol layer. [Figure 4A] 1 illustrates an example downlink data flow for a user plane configuration. [Figure 4B] 1 illustrates an example format of a Medium Access Control (MAC) subheader in a MAC Protocol Data Unit (PDU). [Figure 5A] 1 illustrates an example mapping for a downlink channel. [Figure 5B] 1 illustrates an example mapping for uplink channels. [Figure 6] 1 illustrates exemplary radio resource control (RRC) states and RRC state transitions. [Figure 7] 2 illustrates an exemplary configuration of a frame. [Figure 8]1 illustrates an example resource configuration for one or more carriers. [Figure 9] 1 shows an exemplary configuration of a bandwidth part (BWP). [Figure 10A] 1 shows an example of a carrier aggregation configuration based on component carriers. [Figure 10B] 1 illustrates an exemplary cell group. [Figure 11A] 1 illustrates an example mapping of one or more synchronization signal / physical broadcast channel (SS / PBCH) blocks. [Figure 11B] 1 illustrates an example mapping of one or more channel state information reference signals (CSI-RS). [Figure 12A] 1 shows an example of a downlink beam management procedure. [Figure 12B] An example of an uplink beam management procedure is shown. [Figure 13A] 1 shows an exemplary four-step random access procedure. [Figure 13B] 1 illustrates an exemplary two-step random access procedure. [Figure 13C] 1 illustrates an exemplary two-step random access procedure. [Figure 14A] 1 shows an example of a control resource set (CORESET) configuration. [Figure 14B] 1 illustrates an example of control channel element to resource element group (CCE-to-REG) mapping. [Figure 15A] 1 illustrates an example of communication between a wireless device and a base station. [Figure 15B] 1 illustrates example elements of a computing device that may be used to implement any of the various devices described herein. [Figure 16A]1 illustrates an example of uplink and downlink signal transmission. [Figure 16B] 1 illustrates an example of uplink and downlink signal transmission. [Figure 16C] 1 illustrates an example of uplink and downlink signal transmission. [Figure 16D] 1 illustrates an example of uplink and downlink signal transmission. [Figure 17] 1 illustrates an example of resource availability for various states of a wireless device. [Figure 18A] 1 illustrates an example of configuration and / or activation of one or more radio resources. [Figure 18B] 1 illustrates an example of configuration and / or activation of one or more radio resources. [Figure 19] 1 shows an example of a resource configuration. [Figure 20] 1 shows an example of a resource configuration. [Figure 21A] An example of timing advance (TA) verification is shown below. [Figure 21B] An example of TA verification is shown below. [Figure 22] 1 illustrates an example of one or more radio resources in one or more bandwidth portions (BWPs). [Figure 23] 1 shows an example of beam management. [Figure 24] 1 illustrates an example of modifying one or more cell configuration parameters. [Diagram 25] 1 is an example of changing one or more cell configuration parameters. [Figure 26] 1 is an example of changing one or more cell configuration parameters. [Figure 27] 1 is an example of changing one or more cell configuration parameters. [Figure 28] 1 is an example of changing one or more cell configuration parameters. [Figure 29] 1 illustrates an example method for transmission in an RRC inactive state. [Diagram 30] 1 illustrates an example method for changing a wireless device configuration. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0007] The accompanying drawings and description provide examples. It should be understood that the examples shown and / or described in the drawings are non-exclusive, and the features shown and described may be implemented in other examples. An example is provided for the operation of a wireless communication system that may be used in the technical field of multi-carrier communication systems. More specifically, the technology disclosed herein may relate to transmission and / or reception configurations and signaling for wireless communication.

[0008] 1A illustrates an exemplary communication network 100. The communication network 100 may include a mobile communication network. The communication network 100 may include, for example, a public land mobile network (PLMN) operated / managed / run by a network operator. The communication network 100 may include one or more of a core network (CN) 102, a radio access network (RAN) 104, and / or wireless devices 106. The communication network 100 may include, for example, a cellular network (WAN) 104, a cellular network (WAN) 106, a cellular network (WAN) 108, a cellular network (WAN) 109, a cellular network (WAN) 110, a cellular network (WAN) 111, a cellular network (WAN) 112, a cellular network (WAN) 113, a cellular network (WAN) 114, a cellular network (WAN) 115, a cellular network (WAN) 116, a cellular network (WAN) 117, a cellular network (WAN) 118, a cellular network (WAN) 119, a cellular network (WAN) 120, a cellular network (WAN) 122, a cellular network (WAN) 124, a cellular network (WAN) 126, a cellular network (WAN) 128 ... The communication network 100 may include one or more data networks (DNs) 108 and / or devices in the communication network 100 may communicate with (e.g., the CN 102). The wireless device 106 may communicate with one or more DNs 108, such as a public DN (e.g., the Internet), a private DN, and / or an intra-operator DN. 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 the one or more DNs 108. As part of the interface function, the CN 102 may set up an end-to-end connection between the wireless device 106 and one or more DNs 108, authenticate the wireless device 106, provide / configure charging functionality, etc.

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

[0010] As used throughout, the term "wireless device" includes mobile devices, A wireless device may include one or more of a fixed (e.g., non-mobile) device in which wireless communication is configured or enabled, a computing device, a node, a wireless communication enabled device, or any other device capable of transmitting and / or receiving signals. By way of non-limiting example, a wireless device may be, for example, a telephone, a cell phone, a Wi-Fi phone, a smartphone, a tablet, a computer, Laptops, sensors, meters, wearable devices, Internet of Things (IoT) devices, hotspots, cellular repeaters, vehicular road side units (RSUs), relay nodes, automobiles, wireless user devices (e.g., This may include a user equipment (UE), a user terminal (UT), an access terminal (AT), a mobile station, a handset, a wireless transmit and receive unit (WTRU), a wireless communication device, and / or any combination thereof.

[0011] The RAN 104 may comprise one or more base stations (not shown). As used throughout, the term "base station" may refer to a base station, a node, a Node B (NB), an E-Node B, an (evolved NodeB, eNB), gNB, ng-eNB, relay node (e.g., integrated access and backhaul, IAB node), donor node (e.g., donor eNB, donor gNB, etc.), access point (e.g., Wi-Fi access point), transmission and reception point, A base station may comprise one or more of the following: a TRP, a computing device, a wireless communication enabled device, or any other device capable of transmitting and / or receiving signals. A base station may comprise one or more of each of the elements listed above. For example, a base station may include one or more TRPs. As other non-limiting examples, a base station may be, for example, 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 (UTRA) standards), a Node B (e.g., associated with UMTS and / or third-generation (3G) standards), an Evolved Node B (eNB) (e.g., associated with UMTS and / or third-generation (3G) standards), an Evolved Universal Terrestrial Radio Access (UTRA) standards, ... The donor node may comprise one or more of a base station, a remote radio head (RRH), a baseband processing unit connected to one or more remote radio heads (RRHs), a repeater node or a relay node used to extend the coverage area of ​​a donor node, a Next Generation Evolved Node B (ng-eNB), a Generation Node B (gNB) (e.g., associated with NR and / or fifth-generation (5G) standards), an access point (AP) (e.g., associated with Wi-Fi or any other suitable wireless communication standard), any other generation base station, and / or any combination thereof. A base station may include one or more devices, such as at least one base station central equipment (e.g., a gNB Central Unit (gNB-CU)) and at least one base station distributed equipment (e.g., a gNB Distributed Unit (gNB-DU)).

[0012] A base station (e.g., in the RAN 104) communicates wirelessly with the wireless device 106 (e.g., A base station may comprise one or more sets of antennas for communicating over an air interface. One or more base stations may comprise a set of antennas (e.g., three sets 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 within 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. A base station (e.g., One or more of the cells (alone or in combination with other cells) may provide / establish radio coverage to the wireless device 106 over a wide geographic area to support the movement of the wireless device. A base station with three sectors (e.g., or n sectors, where n refers to any number n) may be referred to as a three-sector site (e.g., or n-sector site) or a three-sector base station (e.g., n-sector base station).

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

[0014] The RAN 104 may be deployed as a homogeneous network of base stations (e.g., macrocell base stations) having similar antenna patterns and / or similar high-level transmission power. The RAN 104 may be arranged 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, e.g., coverage areas that overlap with relatively larger coverage areas provided / configured by other base stations (e.g., macrocell base stations). Small coverage areas may be provided / configured in areas with high data traffic (or so-called "hot spots") or areas with weak macrocell coverage. Examples of small cell base stations may include, in order of decreasing coverage area, microcell base stations, picocell base stations, and femtocell or home base stations.

[0015] The examples described herein may be used in various types of communications. For example, the communications may be communications by the Third-Generation Partnership Project (3GPP®) (e.g., one or more network elements similar to those of the communications network 100), by the Institute of Electrical and Electronics Engineers (IEEE), by the International Telecommunication Union (ITU), by the International Organization for Standardization (ISO), etc. 3GPP has produced specifications for multiple generations of mobile networks, namely, 3G networks known as UMTS, 4G networks known as Long-Term Evolution (LTE) and LTE Advanced (LTE-A), and 5G networks known as 5G System (5GS) and NR system. 3GPP may generate specifications for further generations of communications networks (e.g., 6G and / or any other generation of communications networks). Examples may be described in the context of one or more elements (e.g., RAN) of a 3GPP 5G network, referred to as a next-generation RAN (NG-RAN), or any other communication network, such as a 3GPP network and / or a non-3GPP network. Examples described herein may be applicable to other communication networks, such as 3G and / or 4G networks, as well as communication networks yet to be finalized / specified (e.g., a 3GPP 6G network), satellite communication networks, and / or any other communication network. The NG-RAN may be provisioned to implement and upgrade to a 5G radio access technology, referred to as NR, and to implement other radio access technologies, such as a 4G radio access technology and / or other 3GPP and / or non-3GPP radio access technologies.

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

[0017] CN152 (e.g., 5G-CN) is a public DN (e.g., the Internet), 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 private DNs and / or intra-operator DNs. As part of the interface functions, 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 functions. The CN 152 (e.g., 5G-CN) may be a service-based architecture that may differ from other CNs (e.g., 3GPP 4G CNs, etc.). The architecture of the nodes of the CN 152 (e.g., 5G-CN) may be defined as a network function that provides services via interfaces to other network functions. The network functions of 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).

[0018] The CN 152 (e.g., 5G-CN) may comprise an Access and Mobility Management Function (AMF) device 158A and / or a User Plane Function (UPF) device 158B, which may be separate components or one component 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 act as an anchor point for intra- / inter-Radio Access Technology (RAT) mobility, an external Protocol (or Packet) Data Unit (PDU) session point interconnecting one or more DNs, and / or a branching point to support multi-homed PDU sessions. The service may be configured to be received via a PDU session, which may be a logical connection between the wireless device and the DN.

[0019] The AMF device 158A may provide a number of functions, including Non-Access Stratum (NAS) signaling termination, NAS signaling security, Access Stratum (AS) security control, inter-CN node signaling for mobility between access networks (e.g., 3GPP access networks and / or non-3GPP networks), idle mode wireless device reachability (e.g., idle mode UE reachability for control and execution of paging retransmissions), registration area management, intra-system and inter-system mobility support, access authentication, access authorization including checking of roaming rights, mobility management control (e.g., subscription and policy), network slicing support, and / or may perform functions such as session management function (SMF) selection. The NAS may refer to a function that operates between the CN and the wireless device, and the AS may refer to a function that operates between the wireless device and the RAN.

[0020] CN 152 (e.g., 5G-CN) may comprise one or more additional network functions that may not be shown in Figure 1B. CN 152 (e.g., 5G-CN) may comprise one or more devices implementing 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 functions.

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

[0022] A base station (e.g., gNB 160 and / or ng-eNB 162) may be connected to CN 152 (e.g., 5G CN) via a first interface (e.g., NG interface) and to other base stations via a second interface (e.g., Xn interface). The NG and Xn interfaces may be established using direct physical connections and / or indirect connections via an underlying transport network, such as an internet protocol (IP) transport network. A base station (e.g., gNB 160 and / or ng-eNB 162) may communicate with wireless device 156 via a third interface (e.g., Uu interface). A base station (e.g., gNB 160A) may communicate with wireless device 156A via a Uu interface. The NG, Xn, and Uu interfaces may be associated with protocol stacks. The protocol stacks associated with the interfaces may be used by the network elements illustrated 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 (eg, in a protocol stack). The user plane may process data of interest to users, and the control plane may process signaling messages of interest to network elements.

[0023] One or more base stations (e.g., gNB 160 and / or ng-eNB 162) may communicate with one or more AMF / UPF devices, such as AMF / UPF 158, via one or more interfaces (e.g., NG interfaces). A base station (e.g., gNB 160A) may communicate with and / or be connected to UPF 158B of AMF / UPF 158 via an NG-User plane (NG-U) interface. The NG-U interface may provide / perform delivery (e.g., non-guaranteed delivery) of user plane PDUs between 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 be connected to an AMF device (e.g., AMF 158A) via an NG Control plane (NG-C) interface. The NG-C interface may include: For example, it may provide / perform NG interface management, wireless device context management (e.g., UE context management), wireless device mobility management (e.g., UE mobility management), NAS message transfer, paging, PDU session management, configuration transfer, and / or alert message transmission.

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

[0025] The CN 152 (e.g., 5G-CN) may be configured to handle one or more radio accesses (e.g., NR, 4G, and / or any other radio access). It may also be possible for an NR network / device (or any first network / device) to connect to a 4G core network / device (or any second network / device) in a non-standalone mode (e.g., non-standalone operation). In a non-standalone mode / operation, a 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 balancing across multiple AMF / UPF nodes.

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

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

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

[0029] A user plane configuration (e.g., an NR user plane protocol stack) may comprise multiple layers (e.g., five layers or any other number of layers) implemented in the wireless device 210 and the base station 220 (e.g., as shown in FIG. 2A). At the bottom of the protocol stack, a physical layer (PHY) 211 and 221 may provide transport services to the higher layers of the protocol stack and may correspond to layer 1 of the Open Systems Interconnection (OSI) model. The protocol layers above the 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. The upper protocol layers of 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 upper four protocol layers of PHY 211 may correspond to Layer 2 or the Data Link layer of the OSI model. One or more of the upper four protocol layers of PHY 221 may correspond to Layer 2 or the Data Link layer of the OSI model.

[0030] FIG. 3 illustrates an example of protocol layers. The protocol layers may include, for example, protocol layers of a 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 FIG. 2A and FIG. 3) may perform quality of service (QoS) flow processing. A wireless device (e.g., wireless devices 106, 156A, 156B, and 210) may receive a service via / through a PDU session, which may be a logical connection between a wireless device and a DN. A PDU session may have one or more QoS flows 310. A UPF (e.g., UPF 158B) of the CN may map IP packets to one or more QoS flows of a PDU session, for example, based on one or more QoS requirements (e.g., in terms of delay, data rate, error rate, and / or any other quality / service requirement). The SDAP 215 and 225 may: The SDAP 215 of the base station 220 may perform mapping / demapping between one or more QoS flows 310 and one or more radio bearers 320 (e.g., data radio bearers). The mapping / demapping between one or more QoS flows 310 and radio bearers 320 may be determined by the SDAP 225 of the base station 220. The SDAP 215 of the wireless device 210 may be informed of the mapping between the QoS flows 310 and radio bearers 320 via reflected mapping and / or control signaling received from the base station 220. In case of reflected mapping, the SDAP 225 of the base station 220 may mark downlink packets with a QoS flow indicator (QFI), which may be monitored / detected / identified / indicated / observed by the SDAP 215 of the wireless device 210 to determine the mapping / demapping between one or more QoS flows 310 and radio bearers 320.

[0031] The PDCPs (e.g., PDCPs 214 and 224 shown in Figures 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 / decryption 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). The PDCPs 214 and 224 may perform, for example, retransmission of packets that are not delivered due to handover (e.g., intra-gNB handover), in-order delivery and reordering of packets, and / or removal of duplicately received packets. The PDCPs 214 and 224 may perform, for example, packet duplication to improve the likelihood that a packet is received. A receiver may receive packets in duplicate and remove duplicate packets. Packet duplication may be useful for certain services, such as services that require high reliability.

[0032] The PDCP layers (e.g., PDCP 214 and 224) may perform mapping / demapping between split radio bearers and RLC channels (e.g., RLC channel 330) (e.g., in a dual connectivity scenario / configuration). Dual connectivity occurs when a wireless device is connected to multiple cells (e.g., two cells) or, more generally, to a master cell group. (master cell group, MCG) and secondary cell group (secondary cell group, The term may refer to a technique that enables a mobile station to communicate with multiple cell groups including a single radio bearer (e.g., one of the radio bearers provided / configured by the PDCPs 214 and 224 as a service to the SDAPs 215 and 225) in dual connectivity. A split bearer may be configured and / or used when a single radio bearer (e.g., one of the radio bearers provided / configured by the PDCPs 214 and 224 as a service to the SDAPs 215 and 225) is handled by a cell group in dual connectivity. The PDCPs 214 and 224 may map / demap the split radio bearer belonging to the cell group to / from the RCL channel 330.

[0033] The RCL layer (e.g., RCL 213 and 223) may perform segmentation, retransmission, and / or removal of duplicate data units received from the MAC layer (e.g., MAC 212 and 222, respectively) via Automatic Repeat Request (ARQ). The RLC layer (e.g., RLC 213 and 223) may support multiple transmission modes (e.g., three transmission modes: transparent mode (TM); unacknowledged mode (UM); and acknowledged mode (AM)). The RLC layer may perform one or more of the described functions, for example, based on the transmission mode in which the RLC layer is operating. The RLC configuration may be per logical channel. The RLC configuration may be based on the numerology and / or the Transmission Time Interval (TTI) duration. (or other duration). 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.

[0034] 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. The multiplexing / demultiplexing may include multiplexing / demultiplexing data units / portions belonging to one or more logical channels to / from a Transport Block (TB) 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 downlink / or uplink. The MAC layer (e.g., MAC 212 and 222) may perform Hybrid Automatic Repeat Request (HARQ) (e.g., Carrier Aggregation, The MAC layer (e.g., MACs 212 and 222) may be configured to perform priority handling among the logical channels of the wireless device 210 via logical channel prioritization and / or padding via the HARQ entity per carrier in case of CA). One or more numerologies and / or transmission timings may be supported. Mapping restrictions in logical channel prioritization 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).

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

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

[0037] A downlink data flow may begin, for example, when the SDAP 225 receives three IP packets (or other number of IP packets) from one or more QoS flows and maps the three packets (or other number of packets) to a radio bearer (e.g., radio bearers 402 and 404). 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. To generate an SDAP PDU, an SDAP header (labeled with an "H" before each SDAP SDU shown in FIG. 4A) may be added to the IP packet, which is The data units transferred to and from the higher protocol layers may be referred to as service data units (SDUs) of the lower protocol layers, and the data units transferred to and from the lower protocol layers may be referred to as protocol data units (PDUs) of the higher protocol layers. As shown in FIG. 4A, the data units from the SDAP 225 are transferred to and from the lower protocol layers PDCP 224 SDUs (e.g., The PDU may be a PDCP SDU, or may be a PDU of the SDAP 225 (e.g., an SDAP PDU).

[0038] Each protocol layer (e.g., the protocol layers shown in FIG. 4A ) or at least some of the protocol layers may perform its own function (e.g., one or more functions of each protocol layer described with respect to FIG. 3 ), add a corresponding header, and / or forward its respective output to the next lower layer (e.g., its respective lower layer). PDCP 224 may perform IP header compression and / or encryption. PDCP 224 may forward its output (e.g., PDCP PDUs that are RLC SDUs) to RLC 223. RLC 223 may optionally perform segmentation (e.g., as shown for IP packet m in FIG. 4A ). RLC 223 may forward its output (e.g., two RLC PDUs, which are two MAC SDUs, generated by adding respective subheaders to two SDU segments (SDU Segs)) to MAC 222. MAC 222 may multiplex multiple RLC PDUs (MAC SDUs). MAC 222 may attach MAC subheaders to the RLC PDUs (MAC SDUs) to form a TB. The MAC subheaders may be distributed across the MAC PDUs (e.g., in the NR configuration 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 latency, for example, if the MAC PDU subheaders are calculated before assembling the complete MAC PDU.

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

[0040] One or more MAC control elements (CEs) may be added or inserted into a MAC PDU by a MAC layer such as MAC 223 or MAC 222. As shown in FIG. 4B, two MAC CEs may be inserted / appended before two MAC PDUs. A MAC CE may be inserted / appended 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. A MAC CE may be used for bandwidth control signaling. Exemplary MAC CEs may include scheduling-related MAC CEs such as buffer status reports and power headroom reports; activation / deactivation MAC CEs (e.g., MAC CEs for activation / deactivation of PDCP duplicate detection, channel state information (CSI) reports, sounding reference signal (SRS) transmissions, and pre-configured components); discontinuous reception (DRX)-related MAC CEs; timing advance MAC CEs; and random access-related MAC CEs. The MAC CEs may be preceded by a MAC subheader having a format similar to that described for the MAC subheader of the MAC SDU, and may be identified with a reserved value in the LCID field indicating the type of control information included in the corresponding MAC CE.

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

[0042] A logical channel may be defined by the type of information it carries. The set of logical channels (e.g., in an NR configuration) may comprise one or more channels, as described below. A paging control channel (PCCH) may contain / transmit one or more paging messages used to page wireless devices whose locations are not known to the network at the cell level. A broadcast control channel (BCCH) may contain / transmit one or more paging messages used to page wireless devices whose locations are not known to the network at the cell level. A master information block (MIB ... The wireless devices may include / carry system information messages in the form of a MIB and several system information blocks (SIBs). The system information messages may be used by the wireless devices to obtain information about how the cell is configured and how to operate within the cell. The common control channel (CCCH) may comprise / transmit control messages along with random access. The dedicated control channel (DCCH) may include / transmit control messages to / from a specific wireless device to configure the wireless device with configuration information. The dedicated traffic channel (DTCH) may include / transmit user data to / from a specific wireless device.

[0043] Transport channels may be used between the MAC layer and the PHY layer. Transport channels may be defined by how the information they carry is transmitted / transmitted (e.g., over the air interface). The set of transport channels (which may be defined, e.g., by the NR configuration or any other configuration) may include one or more of the following channels: A paging channel (PCH) may include / transmit paging messages originating from the PCCH; A broadcast channel (BCH) may include / carry the MIB from the BCCH; A downlink shared channel (DL-SCH) may include / carry downlink data and signaling messages including the SIB from the BCCH; An uplink shared channel (UL-SCH) may include / carry uplink data and signaling messages; A random access channel (RACH) may provide wireless devices with access to the network without prior scheduling.

[0044] The PHY layer may use physical channels to pass / transfer information between processing levels of the PHY layer. A physical channel may have an associated set of time-frequency resources for carrying information of one or more transport channels. The PHY layer may generate control information to support low-level operation 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 the NR configuration or any other configuration) may comprise one or more of the following channels: A physical broadcast channel (PBCH) may include / carry the MIB from the BCH. A 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, and possibly uplink control information (UCI), as described below. The physical uplink control channel (PUCCH) may include / carry HARQ acknowledgements, channel quality indicator (CQI), pre-coding matrix indicator (PMI), rank indicator (RI), and other information. and a UCI, which may comprise a scheduling request (SR). For random access, a physical random access channel (PRACH) may be used.

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

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

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

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

[0049] 6 illustrates exemplary RRC states and RRC state transitions. The RRC state of a wireless device may be changed to another RRC state (e.g., RRC state transitions of a wireless device). The wireless device may be substantially the same as or similar to the 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). The RRC inactive 604 may be RRC connected but inactive.

[0050] An RRC connection may be established for the wireless device. For example, this may be during an RRC connected state. During an RRC connected state (e.g., during RRC connected 602), the wireless device has an established RRC context and may have at least one RRC connection with a base station. The base station may be similar to one of one or more base stations (e.g., one or more base stations of the RAN 104 shown in FIG. 1A, one of the gNB 160 or ng-eNB 162 shown in FIG. 1B, the base station 220 shown in FIGS. 2A and 2B, or any other base station). The base station to which the wireless device is connected (e.g., has established an RRC connection) may have an RRC context for the wireless device. The RRC context, which may be referred to as a wireless device context (e.g., a UE context), may include parameters for communication between the wireless device and the base station. These parameters may include, for example, one or more of the following: AS context; radio link configuration parameters; bearer configuration information (e.g., for 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 an RRC connected state (e.g., RRC connected 602), the mobility of the wireless device may be managed / controlled by a RAN (e.g., RAN 104 or NG RAN 154). The wireless device may measure received signal levels (e.g., reference signal level, reference signal received power, reference signal received quality, received signal strength indicator, etc.) based on one or more signals transmitted from the serving cell and neighboring cells. The wireless device may report these measurements to the serving base station (e.g., The RRC state may transition from an RRC connected state (e.g., RRC connected 602) to an RRC idle state (e.g., RRC idle 606) via a connection release procedure 608. The RRC state may transition from an RRC connected state (e.g., RRC connected 602) to an RRC inactive state (e.g., RRC inactive 604) via a connection deactivation procedure 610.

[0051] An RRC context may not be established for the wireless device. For example, This may be during an RRC idle state. During an RRC idle state (e.g., RRC idle 606), an RRC context may not be established for the wireless device. During an RRC idle state (e.g., RRC idle 606), the wireless device may not have an RRC connection with a base station. During an RRC idle state (e.g., RRC idle 606), the wireless device may be in a sleep state most of the time (e.g., to conserve battery power). The wireless device may wake up periodically (e.g., once 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 include a random access procedure.

[0052] For the wireless device, a previously established RRC context may be maintained. For example, this may be during an RRC Inactive state. During an RRC Inactive state (e.g., RRC Inactive 604), a previously established RRC context may be maintained in the wireless device and the base station. Maintaining the RRC context provides a transition from an RRC Idle state (e.g., RRC Idle 606) to an RRC Connected state (e.g., RRC Connected 602) with reduced signaling overhead as 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 may go to a sleep state and the mobility of the wireless device may be managed / controlled by the wireless device via cell reselection. The RRC state may transition from the RRC inactive state (e.g., RRC Inactive 604) to the RRC connected state (e.g., RRC Connected 602) via a Connection Resumption procedure 614. The RRC state may transition from the RRC inactive state (e.g., RRC Inactive 604) to the RRC idle state via a Connection Release procedure 616, which may be the same as or similar to the Connection Release procedure 608. (e.g., RRC Idle 606).

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

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

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

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

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

[0058] Physical signals and physical channels (e.g., as described with respect to Figures 5A and 5B) may be mapped to one or more symbols (e.g., orthogonal frequency divisional multiplexing (OFDM) symbols in a NR configuration or any other symbols). OFDM is a multi-carrier communication scheme that transmits / transmits data over F orthogonal subcarriers (or tones). The data is, for example, mapped to a series of complex symbols called source symbols (e.g., M-quadrature amplitude modulation (M-QAM) symbols or M-phase shift keying (M PSK) symbols or any other modulation symbols) before the transmission of the data, The F parallel symbols may be split into F parallel symbol streams. The F parallel symbol streams may be treated as if they were in the frequency domain. The F parallel symbols may be used as input to an Inverse Fast Fourier Transform (IFFT) block that converts them to the time domain. The IFFT block may take the F source symbols, one from each of the F parallel symbol streams at a time. 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 the sum of the F orthogonal subcarriers. The F time-domain samples may form a single OFDM symbol. The OFDM symbol provided / output by the IFFT block may be transmitted / transmitted over the air interface at a carrier frequency, for example, after one or more processes (e.g., adding a cyclic prefix) and up-conversion. The F parallel symbol streams may be mixed, for example, using a Fast Fourier Transform (FFT) block before being processed by the IFFT block. This operation may be used by one or more wireless devices in the uplink to generate Discrete Fourier Transform (DFT) precoded OFDM symbols to reduce the peak to average power ratio (PAPR). Inverse processing may be performed on the OFDM symbols at the receiver using an FFT block to recover the data mapped to the source symbols.

[0059] FIG. 7 illustrates an example configuration of a frame. The frame may comprise, for example, an NR radio frame in which OFDM symbols may be grouped. The frame (e.g., 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 of 1 ms in duration. The subframe may be divided into one or more slots (e.g., depending on numerology and / or different subcarrier spacing). Each of the one or more slots may include, for example, 14 OFDM symbols per slot. Any number of symbols, slots, or durations may be used over any time interval.

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

[0061] A slot may have a fixed number / number of OFDM symbols (e.g., 14 OFDM symbols). A numerology with higher subcarrier spacing may have a shorter slot duration and more slots per subframe. An example of a number-dependent slot duration and slot transmission structure per subframe is shown in FIG. 7 (a numerology with 240 kHz subcarrier spacing is not shown in FIG. 7). A subframe (e.g., in an NR configuration) may be used as a number-independent time reference. A slot may be used as a unit by which uplink and downlink transmissions are scheduled. Scheduling (e.g., in an NR configuration) may be decoupled from the slot duration. Scheduling may start at 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 minislot or subslot transmissions.

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

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

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

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

[0066] A base station may configure a wireless device with one or more control resource sets (CORESETS) for at least one search space. The base station may configure a wireless device with one or more CORESETS for a downlink BWP within a set of configured downlink BWPs on a primary cell (PCell) or a secondary cell (SCell). A search space may comprise a set of locations in the time and frequency domain where the wireless device may monitor / discover / detect / identify control information. A 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 a group of multiple wireless devices or wireless user devices). A base station may configure a group of wireless devices with a common search space on a PCell or a primary secondary cell (PSCell) in an active downlink BWP.

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

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

[0069] The base station, within the set of configured downlink BWPs associated with the PCell, A wireless device may be semi-statically configured with a default downlink BWP. 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 the wireless device. The wireless device may determine which BWP is the initial active downlink BWP based on, for example, a CORESET configuration obtained using the PBCH.

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

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

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

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

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

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

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

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

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

[0079] A configured SCell for a wireless device may be activated or deactivated based on, for example, traffic and channel conditions. Deactivation of a SCell may cause the wireless device to stop PDCCH and PDSCH reception on the SCell, and PUSCH, SRS, and CQI transmission on the SCell. A configured SCell may be, for example, A configured SCell may be deactivated using a MAC CE (e.g., the MAC CE described with respect to FIG. 4B). The MAC CE may indicate which SCells (e.g., in a subset of configured SCells) of the wireless device are to be 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 a SCell deactivation timer (e.g., one SCell deactivation timer may be configured per SCell).

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

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

[0082] A PCell may comprise a downlink carrier (e.g., PCell 1011) and an uplink carrier (e.g., PCell 1021). A 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, e.g., depending on the context in which the physical cell ID is used. The physical cell ID may, for example, indicate the synchronization signal transmitted / carried by the downlink component carrier. (e.g., PSS and / or SSS). 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. The first physical cell ID of the first downlink carrier may refer to the first physical cell ID of the cell that includes the first downlink carrier. Substantially the same / similar concept may be applied, for example, to carrier activation. Activation of the first carrier may refer to activation of the cell comprising the first carrier.

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

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

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

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

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

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

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

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

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

[0092] The CSI-RS may be transmitted / transmitted 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: For example, the wireless device may estimate downlink channel conditions and / or generate a CSI report based on measurements of one or more downlink CSI-RS. The wireless device may transmit / transmit the CSI report to the base station (e.g., based on periodic CSI reporting, semi-persistent CSI reporting, and / or aperiodic CSI reporting). The base station may use feedback provided by the wireless device (e.g., estimated downlink channel conditions) to perform link adaptation.

[0093] A base station 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.

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

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

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

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

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

[0099] The wireless device may transmit / transmit the uplink DM-RS to a base station, for example, for channel estimation. The base station may use the uplink DM-RS for coherent demodulation of one or more uplink physical channels. The wireless device may transmit / transmit the uplink DM-RS on a PUSCH and / or a PUCCH. The uplink DM-RS may include: It may span a range of frequencies similar to the range of frequencies associated with the corresponding physical channel. The 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 across one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DM-RS may be configured to transmit / transmit on one or more symbols of the PUSCH and / or PUCCH. The base station may semi-statically configure the wireless device with a number / amount (e.g., a maximum number / amount) of frontloaded DM-RS symbols for the PUSCH and / or PUCCH, which the wireless device may use to schedule single-symbol DM-RS and / or dual-symbol DM-RS. The 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 position, DM-RS pattern, and / or scrambling sequence of the DM-RS may be determined by: They may be substantially the same or different.

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

[0101] One or more SRSs may be sent / transmitted by the wireless device to the base station, for example, for channel condition estimation to support uplink channel dependent scheduling and / or link adaptation. The SRS sent / transmitted by the wireless device may enable the base station to estimate uplink channel conditions in one or more frequencies. A scheduler in the base station may use / be used with the estimated uplink channel conditions to allocate one or more resource blocks for uplink PUSCH transmission for the wireless device. The base station may semi-statically configure the wireless device with one or more SRS resource sets. For the SRS resource sets, the base station may: A wireless device may be configured with one or more SRS resources. SRS resource set applicability may be configured, for example, by higher layer (e.g., RRC) parameters. SRS resources in one or more SRS resource sets (e.g., with the same / similar time domain behavior, periodic, aperiodic, etc.) may be transmitted / transmitted at a point in time (e.g., simultaneously) if, for example, higher layer parameters indicate beam management. A wireless device may transmit / transmit one or more SRS resources in an SRS resource set. A network (e.g., an NR network) may support aperiodic, periodic, and / or semi-persistent SRS transmission. A wireless device may transmit / transmit SRS resources based, for example, on one or more trigger types. The one or more trigger types may be based on higher layer signaling. The SRS trigger type may include a PUSCH (e.g., RRC) and / or one or more DCI formats. At least one DCI format may be used / employed 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. The wireless device may be configured to transmit / transmit an SRS after transmission of a PUSCH and a corresponding uplink DM-RS, for example, if the PUSCH and SRS are transmitted / transmitted in the same slot. The base station may semi-statically configure the wireless device with one or more SRS configuration parameters indicating at least one of the following: an SRS resource configuration identifier; a number of SRS ports; a time domain behavior of the SRS resource configuration (e.g., an indication of periodic SRS, semi-persistent SRS, or aperiodic SRS); a slot, minislot, and / or subframe level periodicity; an offset of periodic SRS resources 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.

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

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

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

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

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

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

[0108] FIG. 12A illustrates an example of a downlink beam management procedure. One or more downlink beam management procedures (e.g., downlink beam management procedures P1, P2, and P3) may be performed. Procedure P1 may enable measurements (e.g., wireless device measurements) on the Tx beams 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 at the top and bottom of P1, respectively. Beamforming (e.g., at the TRP) may include a Tx beam sweep for a set of beams. (For example, the beam sweeps shown at the top of P1 and P2 are shown as ellipses rotated in a counterclockwise direction as indicated by the dashed arrows.) Beamforming (e.g., in a wireless device) may include an Rx beam sweep for a set of beams. (For example, the beam sweeps shown in the bottom rows of P1 and P3 are shown as ellipses rotated in the clockwise direction indicated by the dashed arrow.) Step P2 is the TRP Procedure P2 may be used to enable measurement (e.g., wireless device measurement) of the Tx beam of the base station (shown as an ellipse rotated in a counterclockwise direction indicated by the dashed arrow at the top of P2). The wireless device and / or base station may perform procedure P2, for example, using a smaller set of beams than the set of beams used in procedure P1, or using narrower beams than the beams used in procedure P1. Procedure P2 may be referred to as beam refinement. The wireless device may perform procedure P3 for Rx beam determination, for example, by using the same Tx beam of the base station and sweeping the Rx beam of the wireless device.

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

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

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

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

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

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

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

[0116] The one or more RACH parameters provided / configured / included in the configuration message 1310 may be included in a first message (e.g., Msg1 1311) and / or a third message (e.g., The one or more RACH parameters may be used to determine the uplink transmit power of the preamble transmission (e.g., Msg1 1311) and the third message (e.g., Msg3 1313). The one or more RACH parameters may indicate a reference power for the preamble transmission (e.g., a received target power and / or an initial power of the preamble transmission). There may be one or more power offsets indicated by the one or more RACH parameters. The one or more RACH parameters may indicate a power ramp step; a power offset between SSB and CSI-RS; a power offset between the transmission of the first message (e.g., Msg1 1311) and the third message (e.g., Msg3 1313); and / or a power offset value between the preamble groups, The one or more RACH parameters may, for example, 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 supplemental uplink (SUL) carrier).

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

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

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

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

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

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

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

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

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

[0126] The wireless device may, for example, after transmitting / transmitting a preamble (e.g., based on or in response to the transmission / transmission), monitor the PDCCH for the RAR. 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 the search space indicated by the 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. A separate time window for monitoring the PDCCH and / or RAR may be configured to start after transmitting / transmitting the beam failure recovery request (e.g., the window may start any number of symbols and / or slots after transmitting the beam failure recovery request). The wireless device may monitor PDCCH transmissions addressed to a Cell RNTI (C-RNTI) on the search space. During a two-step (e.g., contention-free) random access procedure, the wireless device may, for example, transmit a first message (e.g., Msg1 1321) and receive a corresponding second message (e.g., Msg2 1322) (e.g., based thereon). The wireless device may determine that the random access procedure was successful (or in response to the For example, the wireless device may determine that the random access procedure is successfully completed if the PDCCH transmission is addressed to the corresponding C-RNTI. The wireless device may determine that the random access procedure is successfully completed if, for example, the wireless device receives an RAR with a preamble identifier corresponding to a preamble sent / transmitted by the wireless device and / or the RAR comprises a MAC sub-PDU with the preamble identifier. The wireless device may determine this response as an indication of an acknowledgement to the SI request.

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

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

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

[0130] The wireless device may determine radio resources and / or uplink transmit power for the preamble 1341 and / or the transport block 1342 based on two-stage RACH parameters included in the configuration message 1330 (e.g., included in a first message (e.g., Msg A 1331)). The RACH parameters may indicate an MCS, time-frequency resources, and / or power control for the preamble 1341 and / or the 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 be included in the second message (e.g., Msg B 1331) based on two-stage RACH parameters included in the configuration message 1330 (e.g., included in a first message (e.g., Msg B 1331). B 1332)。 B 1332 may enable the determination of reception timing and downlink channel for monitoring and / or receiving.

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

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

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

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

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

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

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

[0138] FIG. 14A illustrates an example of a CORESET configuration. The CORESET configuration may be for a bandwidth portion or any other frequency band. The base station may transmit / transmit DCI via PDCCH on one or more control resource sets (CORESETs). The CORESET may comprise time-frequency resources where the wireless device attempts / attempts to decode the DCI using one or more search spaces. The 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 / configured 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 / configured at the third symbol in a slot. The fourth CORESET 1404 may occur or be configured / configured at the seventh symbol in a slot. The CORESETs may be: It may have a different number of resource blocks in the frequency domain.

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

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

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

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

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

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

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

[0146] FIG 15A illustrates an example 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 illustrated in FIG 1A, the communication network 150 illustrated in FIG 1B, or any other communication network. The communication network may include two or more wireless devices and / or two or more base stations having substantially the same or similar configuration as that illustrated in FIG 15A.

[0147] 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 a downlink. The direction of communication from the wireless device 1502 to the base station 1504 over the air interface may be referred to as an uplink. The downlink transmission may be separated from the uplink transmission, for example, using various duplexing schemes (e.g., FDD, TDD, and / or some combination of duplexing techniques).

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

[0149] Data to be transmitted to the wireless device 1502 may be provided / forwarded / transmitted to a transmission processing system 1510 of the base station 1504, for example, after being processed by the processing system 1508. Data to be transmitted to the base station 1504 may be provided / forwarded / transmitted to a transmission processing system 1520 of the wireless device 1502, for example, after being processed by the processing system 1518. The transmission processing system 1510 and the transmission processing system 1520 may implement layer 1 OSI functions. Layer 1 may comprise, for example, a PHY layer described in connection with FIGS. 2A, 2B, 3, and 4A. For transmission / 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, etc.

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

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

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

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

[0154] The processing system 1508 may be connected to one or more peripherals 1516. The processing system 1518 may be connected to one or more peripherals 1526. The one or more peripherals 1516 and the one or more peripherals 1526 may include, for example, a speaker, a microphone, a keypad, The wireless device 1502 may include software and / or hardware that provides functions and / or features such as a display, a touchpad, a power source, a satellite transceiver, a universal serial bus (USB) port, a hands-free headset, a frequency modulated (FM) radio unit, a media player, an Internet browser, an electronic control unit (e.g., for an automobile), and / or one or more sensors (e.g., an accelerometer, a gyroscope, a temperature sensor, a radar sensor, a lidar sensor, an ultrasonic sensor, a light sensor, a camera, etc.). The processing system 1508 and / or the processing system 1518 may receive input data (e.g., user input data) from one or more peripherals 1516 and / or one or more peripherals and / or provide output data (e.g., user output data) to one or more peripherals 1526. The processing system 1518 in the wireless device 1502 may be configured to receive power from a power source and / or distribute this power to other components in the wireless device 1502. The power source may include one or more power sources, such as a battery, a solar cell, a fuel cell, or any combination thereof. The processing system 1508 may be coupled to a Global Positioning System (GPS) chipset 1517. The processing system 1518 may be coupled to a Global Positioning System (GPS) chipset 1527. The GPS chipset 1517 and the GPS chipset 1527 may be configured to determine and provide geographic location information for the wireless device 1502 and the base station 1504, respectively.

[0155] 15B illustrates exemplary elements of a computing device that may be used to implement any of the various devices described herein, including, for example, base stations 160A, 160B, 162A, 162B, 220, and / or 1504, wireless devices 106, 156A, 156B, 210, and / or 1502, or any other base station, wireless device, AMF, UPF, network device, or computing device described herein. The computing device 1530 may include one or more processors 1531 that may execute instructions stored in random-access memory (RAM) 1533, removable media 1534 (e.g., a universal serial bus (USB) drive, a compact disk (CD) or digital versatile disk (DVD), or a floppy disk drive), or any other desired storage medium. Instructions may also be stored on an attached (or internal) hard drive 1535. The computing device 1530 may also include a security processor (not shown) that may execute instructions of one or more computer programs to monitor processes running on the processor 1531 as well as 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 controller 1537, network interface 1539, GPS 1541, Bluetooth interface 1542, WiFi interface 1543, etc.). The computing device 1530 may include one or more output devices such as a display 1536 (e.g., 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 controller, keyboard, mouse, touch screen, microphone, etc. The computing device 1530 may include a wired interface, a wireless interface, or a combination of the two. The computing device 1530 may include one or more network interfaces, such as a network interface 1539. 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 / coax distribution system (e.g., a DOCSIS network), or any other desired network. Additionally, the computing device 1530 may include a location detection device, such as a global positioning system (GPS) microprocessor 1541, which may be configured to receive and process global positioning signals and determine the geographic location of the computing device 1530, with possible assistance from an external server and antennas.

[0156] 15B may be a hardware configuration, the components shown may be implemented as software. Components of the computing device 1530 may be added, removed, or modified as desired. Changes may be made to combine, divide, etc. Additionally, the components may be implemented using the same computing devices and components (e.g., processor 1531, ROM storage 1532, display 1536, etc.) 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 executing computer-executable instructions stored on a computer-readable medium, as shown in Figure 15B. Some or all of the entities described herein may be software-based and may co-exist 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 be executed as software on a common computing device).

[0157] 16A shows an example structure for uplink transmission. The processing of the baseband signal representing the physical uplink shared channel may comprise / perform one or more functions, such as scrambling; modulating the scrambled bits to generate complex-valued symbols; mapping the complex-valued modulation symbols to one or more transmission layers; transforming precoding to generate complex-valued symbols; precoding the complex-valued symbols; mapping the precoded complex-valued symbols to resource elements; generating complex-valued time-domain Single Carrier-Frequency Division Multiple Access (SC-FDMA), CP-OFDM signals for antenna ports, or any other signals; The SC-FDMA signal for uplink transmission may include at least one of: For example, a CP-OFDM signal for uplink transmission may be generated when transform precoding is enabled. A CP-OFDM signal for uplink transmission may be generated when transform precoding is not enabled (e.g., as shown in FIG. 16A). These functions are examples and are: Other mechanisms for uplink transmission may be implemented.

[0158] 16B shows an example structure for modulating and up-converting 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 / used, for example, before transmission.

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

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

[0161] The wireless device may receive one or more messages (e.g., RRC messages) comprising configuration parameters for multiple cells (e.g., a primary cell, one or more secondary cells) from a base station. The wireless device may communicate with at least one base station (e.g., two or more base stations in dual connectivity) via the multiple cells. The one or more messages (e.g., as part of the configuration parameters) may include PHY, MAC, RLC, PCDP, SDAP, 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 values ​​of timers for the PHY, MAC, RLC, PCDP, SDAP, RRC layers, and / or communication channels.

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

[0163] The wireless device may operate in one or more states. The one or more states may include, for example, a connected state, a disconnected state, an active state, an inactive state, an idle state, a power saving state, and / or any other state. The one or more states may include RRC states such as RRC_CONNECTED, RRC_INACTIVE, RRC_IDLE, etc. The wireless device may switch / transition to / from one or more states. The wireless device may perform and / or be unable to perform one or more operations in a particular state. The wireless device may not perform (e.g., may not be permitted to perform or may be prohibited from performing) transmissions (e.g., uplink data transmissions) in the RRC_INACTIVE and / or RRC_IDLE states. In such cases, the wireless device may perform (e.g., set up, establish, re-establish, and / or resume) a connection to a network / device for transmission of DL data (e.g., mobile terminated (MT)) and / or UL data (e.g., mobile originated (MO)). The wireless device may perform one or more procedures (e.g., connection setup procedures) to perform a connection to a network / device in the RRC_INACTIVE state (and / or the RRC-IDLE state). The wireless device may perform one or more procedures (e.g., a connection setup or resumption procedure) during the time that DL data (e.g., mobile terminated (MT)) and / or UL data (e.g., mobile originated (MO)) are available for transmission (e.g., stored in a buffer). Based on the one or more procedures (e.g., after or in response to successful completion of a connection setup and / or resumption procedure): The RRC state of the wireless device may switch / transition to an RRC_CONNECTED state from an RRC_INACTIVE state (and / or from an RRC_IDLE state). In the RRC_CONNECTED state, the wireless device may receive (e.g., perform reception of) DL transmissions (e.g., receive DL data) and / or transmit UL transmissions (e.g., transmit UL data). The wireless device may, for example, switch / transition when DL data (e.g., to be received) and / or UL data (e.g., to be transmitted / transmitted) are not available (e.g., Such data is not stored in the buffer. In response to or in response thereto, the wireless device may switch / transition from the RRC_CONNECTED state to an RRC_INACTIVE state (and / or an RRC_IDLE state). To switch / transition from the RRC_CONNECTED state to the RRC_INACTIVE state, the wireless device may perform a connection release procedure. The connection release procedure (e.g., an RRC release procedure) includes: The connection release procedure may result in switching / transitioning an RRC state (e.g., of the wireless device) from an RRC_CONNECTED state to an RRC_INACTIVE state (and / or RRC_IDLE). The connection release procedure may include sending / transmitting one or more release messages (e.g., RRC release messages) by the base station and / or receiving by the wireless device. The one or more release messages may result in the release of resources previously indicated for use by the wireless device. The wireless device may lack sufficient resources to transmit / transmit one or more messages (e.g., data, payload, etc.) after switching / transitioning from the RRC_CONNECTED state. At least some resources (e.g., previously configured / active BWPs) may not be available for use by the wireless device in states other than RRC_CONNECTED. At least some resources (e.g., initial BWPs) may be insufficient and / or inefficient to use for transmitting / transmitting one or more messages. The wireless device may be required to establish / re-establish a connection in the RRC_CONNECTED state before being able to transmit / transmit one or more messages (e.g., data, payload, etc.).

[0164] Switching and / or transitioning wireless device states may require control signaling. Switching and / or transitioning between an RRC_INACTIVE state (and / or an RRC_IDLE state) and an RRC_CONNECTED state may require the wireless device to transmit / transmit and / or receive multiple control signals (e.g., RRC messages, MAC CE, and / or DCI messages) in one or more layers, which may include different layers. An RRC connection setup procedure may require the wireless device to transmit / transmit an RRC connection setup request to a base station and / or receive an RRC connection setup message (e.g., in response to the RRC connection setup request). An RRC connection resumption procedure may require the wireless device to transmit / transmit an RRC connection resumption request to a base station and / or receive an RRC connection resumption message (e.g., in response to the RRC connection resumption request). An RRC connection release procedure may require the wireless device to receive an RRC connection release request from a base station. At least some communications, such as for DL ​​and / or UL transmissions of small amounts of data (e.g., when available and / or arriving), may not be communicated efficiently during a period of time when the wireless device is in the RRC_INACTIVE state (and / or RRC_IDLE state). For example, it may be inefficient for the wireless device to establish (and / or resume) a connection to a network / device (e.g., switch / transition from the RRC_INACTIVE state and / or from the RRC_IDLE state to the RRC_CONNECTED state) and / or release a connection (e.g., switch / transition from the RRC_CONNECTED state to the RRC_INACTIVE and / or RRC_IDLE state) for the purpose of sending / transmitting DL and / or UL transmissions of small data in the RRC_CONNECTED state. Such small data transmissions and associated state switches / transitions may result in unnecessary power consumption and / or increased signaling overhead (e.g., by the wireless device).For example, signaling overhead (e.g., control signaling overhead) that may be required to send / transmit a message (e.g., data, payload, etc.) may be larger than (and / or comparable in size to) the message itself. State switches / transitions (e.g., RRC state switches / transitions) for relatively small and / or infrequent messages (e.g., DL and / or UL data packets) may cause unnecessary power consumption and / or signaling overhead for wireless devices.

[0165] Small and / or infrequent transmissions (e.g., data packets, payloads, etc.) may be required for various applications. Such small and / or infrequent transmissions (which may be referred to herein as small data transmissions (SDT)) may include, for example, traffic generated from smartphone applications and / or any wireless device applications, Instant Messaging (IM) services, heartbeat / keep-alive traffic from IM / email clients and / or other apps / applications, various applications, non-smartphone applications, wearable devices, positioning information / services, and the like. (e.g., vehicle-to-everything and / or location services), (e.g., temperature, The SDT may include sensors (for transmitting pressure readings periodically and / or in an event-triggered manner), smart meters and smart meter networks transmitting meter readings, multicast broadcast multimedia services (MBMs), and / or push notifications from any other wireless device communicating with one or more other devices (e.g., in a communications network). This may include transmissions over (e.g., geostationary equatorial orbit, low Earth orbit, and / or medium Earth orbit satellite systems) and / or non-terrestrial networks (NTNs), for example, to remote areas and / or to connect airborne and / or sea-based platforms (e.g., airships, unmanned aerial vehicles, and / or airships).

[0166] As described herein, a wireless device may be configured for one or more transmissions (e.g., SDT) in one or more states (e.g., RRC_INACTIVE and / or RRC_IDLE states) that may not be a connected state (e.g., RRC_CONNECTED). The wireless device may be configured to send / transmit one or more messages (e.g., perform uplink data transmission) in the RRC_INACTIVE state (and / or in the RRC_IDLE state). The one or more messages may include data traffic (e.g., in a DTCH) of the wireless device. The wireless device may send / transmit one or more data packets in the RRC_INACTIVE state (and / or in the RRC_IDLE state). The wireless device may receive scheduling information (e.g., one or more RRC messages) from a base station indicating one or more uplink radio resources in the RRC_INACTIVE state for the wireless device. The one or more uplink radio resources may include a BWP (and / or any other wireless resource) for use by the wireless device in an RRC_INACTIVE state and / or an RRC_IDLE state (e.g., an SDT BWP). The scheduling information may be provided in one or more release messages (e.g., an RRC release message). The message (e.g., an RRC release message) may include the scheduling information and information for switching / transitioning the state of the wireless device (e.g., from RRC_CONNECTED to RRC_INACTIVE and / or RRC_IDLE). The one or more uplink radio resources may be for infrequent data transmission (e.g., SDT). The one or more uplink radio resources may be for aperiodic data transmission (e.g., SDT). The one or more uplink radio resources may be for periodic data transmission (e.g., SDT). The wireless device may transmit / transmit one or more data packets over one or more radio resources during a time period when the wireless device's state is RRC_INACTIVE state (and / or RRC_IDLE state and / or any other state other than RRC_CONNECTED).The wireless device may not have to switch / transition its RRC state to RRC_CONNECTED to transmit / transmit one or more data packets via one or more radio resources. The wireless device may be configured to use one or more radio resources, for example, at least until it receives an instruction to release and / or reconfigure the one or more radio resources (e.g., a broadcast message indicating a change / reconfiguration of a configuration parameter of the wireless device). Uplink transmission via one or more radio resources in the RRC_INACTIVE state (and / or in the RRC_IDLE state) may be efficient and / or flexible (e.g., for low throughput short data bursts). Uplink transmission via one or more radio resources in the RRC_INACTIVE state (and / or in the RRC_IDLE state) may be efficient and / or flexible (e.g., for low throughput short data bursts). It may provide advantages such as more efficient signaling (e.g., signaling overhead may be smaller than payload / data). Uplink transmission over one or more radio resources in the RRC_INACTIVE state (and / or in the RRC_IDLE state) may reduce signaling overhead. Uplink transmission over one or more radio resources in the RRC_INACTIVE state (and / or in the RRC_IDLE state) may improve battery performance of the wireless device. For example, a wireless device with intermittent small data packets (e.g., SDT) in the RRC_INACTIVE state (and / or in the RRC_IDLE state) may benefit from such uplink transmission in the RRC_INACTIVE state (and / or in the RRC_IDLE state).

[0167] A particular type of message may configure (e.g., provide) scheduling information (e.g., one or more radio resources). The scheduling information may be beneficial to the wireless device (e.g., if the particular type of message includes radio configuration parameters of one or more radio resources dedicated to the wireless device). The radio configuration parameters dedicated to the wireless device may be determined / selected by the base station, which may provide benefits such as reduced battery power of the wireless device and / or improved reliability and / or latency of communication between the wireless device and the base station. A particular type of message may include a wireless device-specific RRC message (e.g., an RRC release message). A broadcast and / or multicast message (e.g., system information) may not include radio configuration parameters dedicated to the wireless device. A broadcast and / or multicast message (e.g., system information) may configure (e.g., provide) scheduling information of radio resources shared with multiple wireless devices (e.g., not dedicated to the wireless device). The scheduling information may be beneficial to the wireless device (e.g., if the wireless device receives a particular type of message when the wireless device performs SDT). A particular type of message may be determined based on recent radio channel conditions (e.g., The message may include scheduling information (e.g., one or more radio resources dedicated to the wireless device) determined (by the base station). The scheduling information may be determined based on recent radio channel conditions, which may improve reliability of communication between the wireless device and / or the base station. The message may include one or more release messages (e.g., RRC release messages) that may indicate a switch / transition to an RRC_INACTIVE state (and / or an RRC_IDLE state). The one or more release messages (e.g., RRC release messages) may include a last message (e.g., a wireless device-specific RRC message) that the wireless device may receive before the SDT and / or that includes scheduling information (e.g., one or more radio resources dedicated to the wireless device) that may be determined (e.g., by the base station) based on recent radio channel conditions before the SDT. An RRC reconfiguration message that the wireless device may receive in the RRC_CONNECTED state may be inappropriate for configuring (e.g., providing) the scheduling information (e.g., one or more radio resources). The wireless device may hold / maintain the RRC_CONNECTED state based on (e.g., after receiving or in response to receiving) the RRC reconfiguration message. The radio channel conditions when the wireless device may receive an RRC reconfiguration may differ from the radio channel conditions when the wireless device performs SDT in the RRC_INACITVE and / or RRC_IDLE states.

[0168] As described herein, uplink data transmission in the RRC_INACTIVE state may be interchangeable with uplink data transmission in the RRC_IDLE state. For example, procedures, configuration parameters, and / or feature descriptions that may be related to uplink data transmission in the RRC_INACTIVE state may be applicable and / or available to the RRC_IDLE state (e.g., unless specifically indicated for the RRC_IDLE state). Procedures, configuration parameters, and / or feature descriptions herein that may be related to uplink data transmission in the RRC_IDLE state may be applicable and / or available to the RRC_INACTIVE state (e.g., unless specifically indicated for the RRC_INACTIVE state). Procedures, configuration parameters, and / or descriptions herein that may be related to uplink data transmission in the RRC_INACTIVE state may be applicable and / or available to the RRC_IDLE state of a wireless device, for example, if the RRC_CONNECTED and / or RRC_IDLE states are at least the RRC states in which the wireless device may be configured to operate. Procedures, configuration parameters, and / or descriptions herein that may relate to uplink data transmission may be applicable and / or available to an RRC_INACTIVE and / or RRC_IDLE state of a wireless device, for example, where RRC_CONNECTED, RRC_INACTIVE, and / or RRC_IDLE states are at least three RRC states in which a wireless device may be configured to operate. References herein to RRC_INACTIVE may refer to any inactive state, such as any inactive state, of a wireless device. References herein to RRC_CONNECTED may refer to any connected state, such as any connected state of a wireless device to another communication device (e.g., a base station). References herein to RRC_IDLE may refer to any idle state, such as any idle state, of a wireless device.

[0169] FIG. 17 illustrates an example of resource availability for various states of a wireless device. The wireless device states may include, for example, RRC_CONNECTED, RRC_INACTIVE, RRC_IDLE, and / or any other states associated with connectivity, activity, power, etc. One or more data packet transmissions and / or other transmissions may occur (and / or be scheduled to occur) in the RRC_INACTIVE state (and / or the RRC_IDLE state). The transmissions may correspond to resources 1703 that may be available, scheduled, and / or configured. The one or more data packet transmissions may include any transmissions described herein. The wireless device 1702 may receive one or more RRC messages from the base station 1701 that configure the resources 1703. The resources 1703 may include uplink resources. Additionally or alternatively, the resources 1703 may include any combination of uplink resources, downlink resources, and / or sidelink resources. The uplink resources may be available and scheduled and / or configured in the RRC_INACTIVE state (and / or the RRC_IDLE state). The wireless device 1702 may determine whether to use (and / or start and / or activate) or stop using (and / or clear and / or suspend and / or deactivate) the resources 1703 based on the RRC state of the wireless device 1702. The wireless device 1702 may receive radio resource configuration parameters associated with one or more radio resources (e.g., uplink radio resources, resources 1703, etc.) that the wireless device 1702 may use in the RRC_INACTIVE state (and / or the RRC_IDLE state). The one or more radio resources may be configured (e.g., pre-configured). The one or more radio resources may be configured, for example, when the wireless device is in the RRC_CONNECTED state, the RRC_INACTIVE state, the RRC_IDLE state, and / or any other state.The wireless device 1702 may receive an RRC message including radio resource configuration parameters for one or more radio resources during the time the wireless device is in the RRC_CONNECTED state (eg, at step 1710). The wireless device may not initiate (and / or activate) one or more radio resources during the time the wireless device is in the RRC_CONNECTED state (e.g., in step 1710). The RRC release message may include radio resource configuration parameters for the one or more radio resources. The wireless device may initiate (and / or activate) the one or more radio resources based on (e.g., after and / or in response to) receiving a release message (e.g., an RRC release message). The wireless device may initiate (and / or activate and / or use) the one or more radio resources based on (e.g., after and / or in response to) the RRC state of the wireless device 1702 being in (and / or transitioning to) an RRC_INACTIVE state (and / or an RRC_IDLE state) (e.g., in step 1720). The wireless device 1702 may transmit / transmit one or more data packets (and / or any transmissions) over one or more radio resources during the time the RRC state is in the RRC_INACTIVE state (and / or the RRC_IDLE state) (e.g., while keeping the RRC state as these states). The wireless device 1702 may, for example, transmit / transmit one or more data packets (and / or any other transmissions) without transitioning (e.g., at step 1720) to an RRC_CONNECTED state. The wireless device 1702 may determine (e.g., at step 1730) to transition the RRC state from the RRC_INACTIVE state (and / or from the RRC_IDLE state). Based on (e.g., subsequently or in response to) switching / transitioning the RRC state to the RRC_CONNECTED state, the wireless device 1702 may determine to stop (and / or clear and / or suspend and / or deactivate) the use of one or more resources.

[0170] The wireless device 1702 may determine to switch / transition an RRC state (e.g., of the wireless device) to an RRC_INACTIVE state (and / or an RRC_IDLE state). The wireless device may determine to switch / transition an RRC state from an RRC_CONNECTED state. The wireless device 1702 may determine to switch / transition an RRC state to an RRC_INACTIVE state (and / or an RRC_IDLE state), for example, based on (e.g., after or in response to) receiving one or more RRC messages. The wireless device 1702 may receive one or more RRC messages (e.g., RRC release messages) from the base station 1701. The one or more RRC messages (e.g., RRC release messages) may indicate a release of an RRC connection (e.g., release from a network). Based on (e.g., after or in response to) receiving the RRC message, the wireless device 1702 may perform an RRC release procedure. The RRC release procedure may include release of one or more established radio bearers and / or configured radio resources. The RRC release procedure may include suspension of the RRC connection (e.g., if a signaling radio bearer (SRB) (e.g., SRB2) and / or at least one dedicated radio bearer (DRB) is set up) and / or suspension of established radio bearers. Based on (e.g., subsequently and / or in response to) receiving the RRC message (and / or performing the RRC release procedure), the wireless device 1702 may switch / transition (and / or decide to switch / transition) the RRC state of the wireless device from an RRC_CONNECTED state to an RRC_INACTIVE state (and / or an RRC_IDLE state).

[0171] The wireless device 1702 may determine to transition its RRC state from an RRC_INACTIVE state (and / or an RRC_IDLE state) to an RRC_CONNECTED state. The wireless device 1702 may perform a random access procedure to switch / transition to the RRC_CONNECTED state. The wireless device 1702 may perform (and / or initiate) a random access procedure for uplink transmission of uplink data that may be received during the RRC_INACTIVE state (and / or during the RRC_IDLE state). The wireless device 1702 may perform the random access procedure, for example, based on (e.g., after receiving or in response to receiving) a paging message in the RRC_INACTIVE state (and / or the RRC_IDLE state). The wireless device 1702 may monitor (e.g., periodically monitor) a downlink control channel for a paging message and / or any other message. The wireless device 1702 may receive a paging message from the base station 1701 (and / or from the network and / or from any communication device), which may indicate an identifier of the wireless device (e.g., a wireless device ID). The paging message may indicate that the wireless device 1702 should perform and / or initiate a random access procedure (e.g., to connect to the network and / or any communication device).

[0172] The wireless device may receive one or more RRC messages indicating one or more uplink radio resources. The wireless device may use one or more uplink radio resources in the RRC_INACTIVE (and / or RRC_IDLE) state. The one or more uplink radio resources in the RRC_INACTIVE (and / or RRC_IDLE) state may include resources for one-time use (e.g., for a single transmission) and / or resources for multiple use. The one or more uplink radio resources in the RRC_INACTIVE (and / or RRC_IDLE) state may include periodic resources (e.g., for one or more uplink transmissions). The one or more uplink radio resources in the RRC_INACTIVE (and / or RRC_IDLE) state may include preconfigured uplink resources (PURs). The one or more uplink grants indicating the one or more uplink radio resources in the RRC_INACTIVE (and / or RRC_IDLE) state may include configured grants and / or preconfigured grants. The configured and / or pre-configured grant may include multiple types of grants, such as a (pre-)configured grant type 1 and / or a (pre-)configured grant type 2. The one or more uplink radio resources determined (and / or indicated) by the (pre-)configured grant type 1 may not require an instruction to start / restart (and / or activate / reactivate) the one or more uplink radio resources (e.g., after or in response to receiving an RRC message indicating the one or more uplink radio resources in the RRC_INACTIVE (and / or RRC_IDLE) state). The wireless device may (re)start (and / or (re)activate) the one or more uplink radio resources based on (e.g., after or in response to receiving) an RRC message including a (pre-)configured grant type 1 indicating the one or more uplink radio resources in the RRC_INACTIVE (and / or RRC_IDLE) state.The one or more uplink radio resources determined (and / or indicated) by the (pre-)configured grant type 2 may require an instruction to (re)open (and / or (re)activate) the one or more uplink radio resources (e.g., after or in response to receiving an RRC message indicating the one or more uplink radio resources). The wireless device may not (re)open (and / or (re)activate) the one or more uplink radio resources based on (e.g., after or in response to receiving an RRC message with a (pre-)configured grant type 2 indicating the one or more uplink radio resources). The wireless device may (re)open (and / or (re)activate) the one or more uplink radio resources based on (e.g., after or in response to receiving) an instruction to (re)open (and / or (re)activate) the one or more uplink radio resources in the RRC_INACTIVE (and / or RRC_IDLE) state. The wireless device may receive the indication based on (e.g., after or in response to) receiving an RRC message including a (pre-)configured grant type 2 indicating one or more uplink radio resources. An uplink grant indicating one or more uplink radio resources in the RRC_INACTIVE (and / or RRC_IDLE) state may be referred to as a (pre-)configured grant having a particular type indicator (e.g., (pre-)configured grant type 3, 4, etc.). The (pre-)configured grant type 1 and / or the (pre-)configured grant type 2 may indicate one or more (e.g., periodic) uplink grants in the RRC_CONNECTED state. The (pre-)configured grant type 3 (and / or other types of (pre-)configured grants) may indicate one or more (e.g., periodic) uplink grants in the RRC_INACTIVE (and / or RRC_IDLE) state.

[0173] 18A illustrates an example of the configuration and / or activation of one or more radio resources. The one or more (pre-)configured grants may indicate one or more radio resources (e.g., uplink and / or downlink radio resources) in the RRC_INACTIVE state (and / or the RRC_IDLE state). The (pre-)configured grants may not require additional activation messages (e.g., DCI, MAC CE, and / or RRC) to activate (and / or initiate) the one or more uplink radio resources (and / or the (pre-)configured grants) (e.g., at 1803). The wireless device 1802 may receive one or more RRC messages including configuration parameters of the (pre)configured grants of the cell. The one or more RRC messages may include an RRC release message. Based on receiving the RRC message (e.g., after receiving Based on (e.g., after receiving or in response to receiving) one or more RRC messages, the wireless device 1802 may determine (and / or store) a (pre-)configured grant for the cell. Based on (e.g., after receiving or in response to receiving) one or more RRC messages, the wireless device 1802 may (re)open (or activate) the (pre-)configured grant. One or more uplink radio resources (and / or (pre-)configured grants) may be activated and / or started (and / or enabled) in an RRC_INACTIVE state. The wireless device may (re)open (and / or activate) the (pre-)configured grant to start at (and / or from) a time reference. The time reference may include a symbol, a slot, a subframe, a SFN, a hyper-SFN (H-SFN), and / or any indication. An H-SFN includes one or more SFNs (e.g., 1024 SFNs). The time reference may include one or more combinations of a symbol, a slot, a subframe, a SFN, a Hyper-SFN (H-SFN), and / or any designation. The time reference may include a symbol of a slot of an SFN of the H-SFN indicated by the configuration parameters (e.g., a time domain offset (e.g., indicating the H-SFN, SFN, and / or slot) and / or a symbol number S (e.g., indicating a symbol). The wireless device 1802 may determine that the (pre-)configured grant (re)occurs with / using the periodicity indicated by the configuration parameters. The wireless device may communicate with and / or make a connection to the network (and / or base station). The wireless device 1802 may perform an RRC connection setup procedure and / or an RRC connection resumption procedure to make the connection. The wireless device 1802 may send / transmit an RRC connection setup request (e.g., for an RRC connection setup procedure) and / or an RRC connection resumption request (e.g., for an RRC connection resumption procedure). The wireless device 1802 may receive a response from the base station 1801 indicating completion of making the RRC connection. The wireless device 1802 may receive an RRC connection setup completion (e.g., for an RRC connection setup procedure).The wireless device 1802 may receive an RRC connection resumption completion (e.g., for an RRC connection resumption procedure). One or more uplink radio resources (and / or (pre)configured grants) may be deactivated and / or suspended (cleared and / or disabled) in the RRC_CONNECTED state. One or more uplink radio resources. (and / or (pre)configured permissions) may be deactivated and / or suspended (cleared and / or disabled) based on (e.g., after or in response to) communicating with (and / or making a connection to) base station 1801 (e.g., after or in response to receiving an RRC connection setup and / or resumption completion).

[0174] FIG. 18B illustrates an example of configuration and / or activation of one or more radio resources. The one or more (pre-)configured grants may indicate one or more radio resources (e.g., uplink radio resources and / or downlink radio resources) in an RRC_INACTIVE state (and / or an RRC_IDLE state). The (pre-)configured grants of FIG. 18B may require additional activation messages (e.g., DCI, MAC CE, and / or RRC) that activate (and / or initiate) the one or more uplink radio resources (and / or the (pre-)configured grants) (e.g., at 1804). The wireless device 1812 may receive (e.g., 1805) one or more RRC messages including configuration parameters of the (pre-)configured grants of the cell. Based on (e.g., after receiving or in response to receiving) the one or more RRC messages, the wireless device may determine (and / or store) the (pre-)configured grants for the cell. The one or more RRC messages may include an RRC release message. Based on (e.g., after receiving or in response to) receiving one or more RRC messages, the wireless device may not (re)activate (or activate) the (pre-)configured grant (e.g., at 1804) (e.g., at least until the wireless device receives (e.g., additional) activation messages (e.g., DCI, MAC CE, and / or RRC). The wireless device may monitor the PDCCH in an RRC_INACTIVE state (and / or an RRC_IDLE state) to receive additional activation messages. Based on (e.g., after receiving or in response to) receiving an RRC message, the wireless device may receive (additional) activation messages (e.g., DCI, MAC CE, and / or RRC). The DCI message carried by the PDCCH may include the (additional) activation message. The MAC CE and / or RRC message received based on the downlink assignment of the DCI message carried by the PDCCH may include the (additional) activation message.The configuration parameters in the RRC message may indicate a time and / or frequency resource allocation for the PDCCH, a monitoring opportunity for the PDCCH, and / or a monitoring periodicity for the PDCCH. The wireless device may determine that the (pre-)configured grant (re)occurs with a periodicity indicated by the configuration parameters and / or a timing offset reference (e.g., H-SFN, SFN, slot and / or symbol). The wireless device may determine the SFN (e.g., for H-SFN), slot and / or symbol based on a reception timing of an additional activation message received via the PDCCH. The wireless device 1812 may receive a deactivation message that may indicate to deactivate and / or suspend (clear and / or disable) one or more uplink radio resources (and / or (pre-)configured grants). The wireless device 1812 may receive the deactivation message in an RRC_INACTIVE state (and / or in an RRC_IDLE state). The wireless device 1812 may communicate with (and / or make a connection to) a network (and / or a base station 1811). The wireless device 1812 may perform an RRC connection setup procedure and / or an RRC connection resumption procedure to communicate with (and / or make a connection to) the base station 1811. The wireless device 1812 may transmit / transmit an RRC connection setup request (e.g., for an RRC connection setup procedure) and / or an RRC connection resumption request (e.g., for an RRC connection resumption procedure). The wireless device 1812 may receive a response from the base station 1811 indicating completion of making the RRC connection. The wireless device 1812 may receive an RRC connection setup complete message (e.g., for an RRC connection setup procedure). The wireless device 1812 may receive an RRC connection resumption complete message (e.g., for an RRC connection resumption procedure). Based on making the connection. (e.g., thereafter or in response thereto), the RRC state of the wireless device 1812 is The wireless device 1812 may transition to an RRC_CONNECTED state. One or more uplink radio resources (and / or (pre-)configured grants) (e.g., 1806) may be deactivated and / or suspended (cleared and / or disabled) based on (e.g., after or in response to) the RRC state of the wireless device 1812 being in the RRC_CONNECTED state. One or more uplink radio resources (and / or (pre-)configured grants) may be deactivated and / or suspended (cleared and / or disabled) based on (e.g., after or in response to) making a connection to the base station 1811 (e.g., after or in response to receiving an RRC connection setup and / or resumption completion).

[0175] The one or more uplink radio resources in the RRC_INACTIVE (and / or RRC_IDLE) state may be configured by one or more higher layers (e.g., the RRC layer and / or the MAC layer). The wireless device 1812 may receive from the base station 1811 a message (e.g., an RRC message) including one or more configuration parameters for transmission of uplink data over the one or more uplink radio resources (e.g., 1806) in the RRC_INACTIVE (and / or RRC_IDLE) state.

[0176] The one or more configuration parameters may include and / or indicate an RNTI. The RNTI is for transmission of uplink data over one or more uplink radio resources in RRC_INACTIVE (and / or RRC_IDLE) state. The RNTI may be an identifier of the wireless device, such as a C-RNTI. The RNTI may include a C-RNTI. The RNTI may include a pre-configured uplink resource C-RNTI (e.g., PUR-C-RNTI and / or PUR-RNTI). The wireless device may monitor a PDCCH using the RNTI. The wireless device may monitor a PDCCH using the RNTI based on (e.g., after or in response to) a transmission of uplink data over one or more uplink radio resources. The wireless device may receive a DCI with / using a CRC scrambled by the RNTI over the PDCCH. The DCI may indicate a positive acknowledgement of a transmission of uplink data. The DCI may indicate a negative acknowledgement of a transmission of uplink data. The DCI may indicate a retransmission of a transmission of uplink data. The DCI may indicate an uplink grant for retransmission. The DCI may indicate updated parameter values ​​of one or more configuration parameters. The DCI may indicate a (e.g., new or updated) timing advance value for transmission of uplink data over one or more uplink radio resources in RRC_INACTIVE (and / or RRC_IDLE) state. The DCI may indicate a trigger / start of an RA procedure. The one or more configuration parameters may indicate a duration of a response window (e.g., exemplary parameter name: ResponseWindowSize). The wireless device may monitor the PDCCH for the duration of the response window to receive a response (e.g., DCI) to the transmission of data from the base station.

[0177] The one or more configuration parameters may indicate a number / amount of skipped uplink grants (and / or resource opportunities) (e.g., example parameter name: ImplicitReleaseAfter). The wireless device may decide, for example, to release (clear, deactivate, discard, and / or suspend) one or more uplink radio resources, uplink grants indicating one or more uplink radio resources, and / or one or more configuration parameters based on the indicated number / amount. This release (clear, deactivate, discard, and / or suspend) may be referred to as implicit resource release, implicit pre-configured uplink resource release, etc. The number / amount of skipped uplink grants (and / or resource opportunities) indicated by the one or more configuration parameters may include a number / amount of consecutive skipped (and / or empty) uplink grants (and / or resource opportunities). The wireless device may, for example, release (clear, deactivate, discard, and / or suspend) one or more uplink radio resources, uplink grants indicating the one or more uplink radio resources, and / or one or more configuration parameters based on (e.g., after or in response to) a determination that the wireless device may skip N opportunities (e.g., N consecutive opportunities) of one or more uplink radio resources or is unable to transmit an uplink packet over one or more uplink radio resources for N times (e.g., N=number of skipped uplink grants and / or resource opportunities). The wireless device may not apply (and / or use) an implicit resource release (e.g., an implicit pre-configured uplink resource release, etc.), for example, if the one or more configuration parameters do not include a parameter indicating the number of skipped uplink grants (and / or resource opportunities) (e.g., if ImplicitReleaseAfter is not present in the one or more configuration parameters). Any of the procedures described with respect to FIG. 18B may be applied to the procedures with respect to FIG. 18A, for example, for combined operation.Any of the procedures described with respect to FIG. 18A may be applied to the procedures with respect to FIG. 18B (e.g., the activation and / or initiation of resources at 1803 may be applied to the activation and / or initiation of resources at 1805 and / or 1806).

[0178] FIG. 19 illustrates an example of resource configuration. A base station 1901 may configure a wireless device 1902 with one or more resources (e.g., 1910) for transmission and / or reception (e.g., during an RRC_INACTIVE state and / or an RRC_IDLE state). The base station 1901 may configure a wireless device 1902 with one or more resources for uplink transmission 1903. One or more resources (e.g., for data packet transmission) in an RRC_INACTIVE state (and / or an RRC_IDLE state) may be configured and used for transmission / reception (e.g., at 1903), not configured and used for transmission reception (e.g., at 1904), and / or released after being configured (e.g., at 1905). The wireless device 1902 may receive one or more RRC messages configuring uplink resources (e.g., 1910). Uplink resources (eg, 1910) may be available, scheduled, and / or configured in the RRC_INACTIVE state (and / or the RRC_IDLE state). The wireless device 1902 may not transmit an uplink packet during one or more opportunities of the uplink resources (e.g., at 1904). The wireless device 1902 may count / determine the one or more opportunities. The wireless device 1902 may decide to release the uplink resources (e.g., at least one of release, clear, deactivate, and / or suspend). The wireless device 1902 may, for example, If the number / amount of one or more opportunities that the wireless device may skip (and / or not use to transmit an uplink packet) meets (e.g., is greater than or equal to) a threshold, the uplink resources may be released. The number / amount of one or more opportunities may be the number / amount of one or more consecutive opportunities of the uplink resources that the wireless device may skip (and / or may not use).

[0179] The wireless device may count / determine the number / amount of skipped uplink grants (and / or resource opportunities). The wireless device may count / determine the number / amount of skipped uplink grants, for example, to determine to release (e.g., clear, deactivate, discard, and / or suspend) one or more uplink radio resources, an uplink grant indicating one or more uplink radio resources, and / or one or more configuration parameters. m may be the number / amount of skipped uplink grants that the wireless device counts / determines. The wireless device may, for example, release one or more uplink radio resources, uplink grants, and / or one or more configuration parameters (e.g., when m meets / reaches a threshold (e.g., is equal to or greater than a threshold)). The threshold may be configurable by one or more configuration parameters (e.g., the threshold may be set to: The threshold may be 1, 2, 3, 4, 8, etc. The one or more configuration parameters may indicate that the threshold is not configured (e.g., the threshold may be disabled). The wireless device may determine, for example, that if the one or more configuration parameters do not comprise a threshold, then implicit resource release does not apply (e.g., is disabled).

[0180] The wireless device may use a counter to count / determine the number / amount of skipped uplink grants (and / or resource opportunities). The value of the counter may be referred to as m. The counter may be implemented in one or more ways. The value of the counter may be increased and / or decreased based on the implemented counter. The counter may be used to count / determine the number / amount of skipped uplink grants (and / or resource opportunities). The counter may include an up-counter that may count the number / amount of skipped uplink radio resources (and / or resource opportunities) in ascending order. The wireless device may decide to release (e.g., clear, deactivate, discard, and / or suspend) one or more uplink radio resources, uplink grants indicating one or more uplink radio resources, and / or one or more configuration parameters, for example, if the value of the counter m meets / reaches a threshold. The counter may include a down-counter that may count the number / amount of skipped uplink grants (and / or resource opportunities) in descending order. The wireless device may decide to release (e.g., clear, deactivate, discard, and / or suspend) one or more uplink radio resources, uplink grants indicating one or more uplink radio resources, and / or one or more configuration parameters, for example, if the value of the counter starts from a threshold (and / or a first predefined value) and reaches 0 (or a second amount and / or a predefined value). The wireless device may, for example, release (e.g., release) one or more uplink radio resources, uplink grants indicating one or more uplink radio resources, and / or one or more configuration parameters when a number of skipped uplink grants (and / or resource opportunities) counted by the wireless device reaches / met a threshold (e.g., for any type of counter, such as an up counter, a down counter, etc.). The device may decide to clear, deactivate, discard, and / or pause a counter (e.g., a description of an up counter may apply to a description of a down counter and / or a description of a down counter may apply to a description of an up counter).

[0181] The wireless device may determine to increase m based on at least one of the following: The wireless device may increase m, for example, if a radio resource opportunity of one or more uplink radio resources is not used (e.g., the wireless device may increase m if the wireless device does not transmit a data packet via a radio resource opportunity of one or more uplink radio resources). The wireless device may increase m, for example, if a radio resource opportunity of one or more uplink radio resources is not used during a time period when the wireless device is in an RRC_INACTIVE state (and / or an RRC_IDLE state). The wireless device may increase m (e.g., uplink grants and / or resource opportunities of one or more uplink radio resources that are skipped) if, for example, no MAC PDU is generated for the uplink grant and / or resource opportunity. The wireless device may increase m, for example, if a radio resource opportunity of one or more uplink radio resources is used (e.g., the wireless device transmits a data packet over a radio resource opportunity of one or more uplink radio resources) but no response corresponding to the data packet (e.g., one or more of a HARQ ACK, a HARQ NACK, an L2 (e.g., MAC CE) response, and / or an L3 (e.g., RRC message) response) is received. The wireless device may increase m if, for example, the wireless device skips a radio resource opportunity of one or more uplink radio resources due to a barring of access to a cell in which the one or more uplink radio resources are configured. The wireless device may increase m if the wireless device skips a radio resource opportunity for one or more uplink radio resources, for example, due to the wireless device being in a waiting time (and / or an extended waiting time). The waiting time (and / or extended waiting time) may indicate how many seconds the wireless device may wait (e.g., is required to wait) based on (e.g., after or in response to) receiving a rejection (e.g., an RRC connection rejection) and / or at least until an RRC connection request message is sent / transmitted.

[0182] The base station (and / or network) may maintain a counter to synchronize with the wireless device. The base station (and / or network) may decide to increase m based on at least the following: The base station (and / or network) may increase m, for example, if the base station does not receive an uplink packet via a radio resource opportunity of one or more uplink radio resources. The base station (e.g., network) may increase m, for example, during a time period when the wireless device is in an RRC_INACTIVE state (and / or an RRC_IDLE state). The base station (and / or network) may increase m, for example, if the base station (e.g., network) does not transmit / transmit a response (e.g., HARQ feedback (ACK and / or NACK)). The base station (and / or network) may increase m, for example, if the base station receives an uplink packet via a radio resource opportunity of one or more uplink radio resources but does not transmit / transmit a response to the uplink packet to the wireless device. The response may include HARQ ACK feedback. The response may include HARQ NACK feedback. The response may include an L2 response (e.g., a MAC CE) and / or an L3 response (e.g., an RRC message). The base station (and / or the network) may increase m, for example, if a radio resource opportunity for one or more uplink radio resources is skipped by the wireless device (e.g., due to a barring of access to a cell in which one or more uplink radio resources are configured). The base station (and / or the network) may increase m, for example, if the wireless device is waiting for a certain period of time. m may be increased if a radio resource opportunity for one or more uplink radio resources is skipped by the wireless device due to being in a waiting period (and / or an extended waiting period). The waiting period (and / or the extended waiting period) may indicate (e.g., define) how many seconds the wireless device waits based on (e.g., after or in response to) receiving an RRC connection rejection until at least an RRC connection request message is transmitted.

[0183] The wireless device may determine not to increase m based on at least one of the following: The wireless device may not increase m, for example, during a time period when the wireless device is in an RRC_CONNECTED state. The wireless device may not increase m, for example, based on (e.g., after or in response to) one or more uplink radio resources of the wireless device being suspended (e.g., inactive and / or cleared). The wireless device may not increase m, for example, during a time period when a timer (e.g., a prohibit timer) of the wireless device is running. The wireless device may determine the time before an access attempt is performed based on (e.g., when a prohibit timer expires) the prohibit timer. The time before an access attempt is performed may be determined based on (e.g., after or in response to) the access attempt being barred in an access barring check. The base station (and / or network) may maintain a counter to be synchronized with the wireless device. The base station (and / or network) may, for example, The base station (and / or network) may decide not to increase m based on at least the following: The base station (and / or network) may not increase m, for example, during a period of time when the wireless device is in an RRC_CONNECTED state The base station (and / or network) may decide not to increase m, for example, during a period of time when one or more uplink radio resources of the wireless device are suspended (e.g., deactivated, The base station (and / or network) may not increase m based on (e.g., after or in response to) the access attempt being enabled (and / or cleared). The base station (and / or network) may not increase m, for example, during a time period when a timer (e.g., a prohibit timer) of the wireless device is running. The wireless device may determine the time before an access attempt is made based on the prohibit timer (e.g., when the prohibit timer expires). The time before an access attempt is made may be determined based on (e.g., after or in response to) the access attempt being barred in an access barring check.

[0184] The wireless device may reset the counter based on at least one of the following: The wireless device may reset the counter (e.g., to 0, such as in the case of an up counter) based on (e.g., after or in response to) successful communication between the wireless device and the base station (and / or network). The wireless device may reset the counter (e.g., to 0, such as in the case of an up counter) based on (e.g., after or in response to) receiving an acknowledgment (e.g., an ACK message) corresponding to an uplink transmission over one or more uplink radio resources. The wireless device may reset the counter (e.g., to 0 in the case of an up counter, etc.). The wireless device may be in the RRC_INACTIVE (and / or RRC_IDLE) state. The wireless device may communicate with the base station in the RRC_INACTIVE (and / or RRC_IDLE) state. The wireless device may reset the counter (e.g., to 0, such as in the case of an up counter) based on (e.g., after or in response to) sending / transmitting an acknowledgment (e.g., an ACK message) corresponding to receipt of a downlink data packet from the wireless device (and / or the network). The wireless device may not reset the counter based on (e.g., after or in response to) a successful communication during the time period in which the wireless device is in the RRC_CONNECTED state.

[0185] The base station (and / or network) may reset the counter based on at least one of the following: The base station (and / or network) may reset (e.g., to 0, in the case of an up counter, etc.) based on (e.g., after or in response to) a successful communication between the wireless device and the base station (and / or network). ... confirmation response (e.g., an ACK message) corresponding to an uplink transmission performed by the wireless device over one or more uplink radio resources. The wireless device may perform uplink transmission in an RRC_INACTIVE (and / or RRC_IDLE) state. The base station (and / or network) may reset (e.g., to 0, in the case of an up counter, etc.) based on (e.g., after or in response to) a confirmation response (e.g., an ACK message) corresponding to a downlink data packet transmitted / transmitted to the wireless device during a time period in which the wireless device is in an RRC_INACTIVE (and / or RRC_IDLE) state. The base station (and / or network) may reset (e.g., to 0, such as in the case of an up counter) based on (e.g., after or in response to) receiving a ACK message from the wireless device. The base station (and / or network) may reset (e.g., to 0, such as in the case of an up counter) based on (e.g., after or in response to) successful communication during a time period in which the wireless device is in the RRC_CONNECTED state. The counter may not be reset (in response to the successful completion of the request).

[0186] The one or more configuration parameters may be used to adjust the time alignment timer for a cell (and / or a cell group that includes the cell) via a cell for which one or more uplink radio resources are configured in RRC_INACTIVE state (and / or RRC_IDLE state). The value of the TAT may indicate a value of a time alignment timer (TAT) (e.g., example parameter name: TimeAlignmentTimer). A cell group including the cell may be referred to as a timing advance group (TAG) and / or any other type of cell group. The value of the TAT may indicate a duration (e.g., how long) for which a timing advance offset value is valid and / or used to adjust uplink timing for uplink transmissions to the cell (and / or cells in the cell group). The value of the TAT may indicate / determine a duration (e.g., how long) for which the wireless device may determine cells (and / or cells belonging to the associated TAG) for which uplink time should be aligned. The wireless device may determine (and / or adjust) uplink timing for uplink transmissions (e.g., PRACH, PUSCH, SRS, and / or PUCCH transmissions) on / through the cell (and / or on / through the cells in the cell group) based on the timing advance offset value. The timing advance offset value may indicate how much (and / or how long) uplink timing for uplink transmissions is delayed or advanced for uplink synchronization. The wireless device may activate the TAT for a time interval (and / or duration) indicated by the value of the TAT. The wireless device may determine that the timing advance offset value is valid (and / or used) to adjust uplink timing for uplink transmissions on a cell (or a cell in a cell group) during the time period during which the TAT is running. The wireless device may determine that an uplink from the wireless device to a cell (e.g., a base station) is out of sync, for example, if a TAT associated with a cell group (e.g., TAG) to which the cell belongs is not activated and / or terminated. The wireless device may stop performing uplink transmissions on / through a cell (and / or on / through a cell in a cell group) if a TAT associated with a cell group (e.g., TAG) to which the cell belongs is not activated and / or terminated, for example.The wireless device may stop uplink transmission for a cell, for example, if an uplink transmission timing difference (e.g., a maximum uplink transmission timing difference) between TAGs (and / or other cell groups) of the wireless device or an uplink transmission timing difference between TAGs (and / or other cell groups) of any MAC entity (e.g., two MAC entities configured for dual connectivity) of the wireless device is exceeded. The wireless device may determine that a TAT associated with a cell has expired, for example, if an uplink timing difference between TAGs (and / or other cell groups) is exceeded. The wireless device may perform random access preamble transmission (and / or retransmission) and / or MSG A transmission (and / or retransmission), for example, if a TAT associated with a cell group (e.g., TAG) to which the cell belongs is not running and / or expires. The wireless device may start (and / or restart) the TAT based on (e.g., after receiving or in response to receiving) a timing advance command indicating a timing advance offset value (e.g., a new and / or updated timing advance offset value) of a cell (and / or a cell in a cell group). The timing advance command may be received as a MAC CE and / or a DCI. The timing advance command may indicate a timing advance offset value of a cell for which one or more uplink radio resources are in an RRC_INACTIVE state (and / or an RRC_IDLE state).

[0187] The wireless device may start (and / or restart) the time alignment timer based on (e.g., after or in response to) switching / transitioning to the RRC_INACTIVE state (and / or the RRC_IDLE state). The wireless device may start (and / or restart) the time alignment timer, for example, when the wireless device receives (and / or is configured with) one or more uplink radio resources for the RRC_INACTIVE (and / or the RRC_IDLE) state. The wireless device may start (and / or restart) the time alignment timer based on (e.g., after or in response to) receiving a configuration parameter associated with the time alignment timer (e.g., a timer value for the time alignment timer). The wireless device may start (and / or restart) a time alignment timer based on (e.g., after receiving or in response to receiving) the timing advance offset value. The wireless device may receive a lower layer control message (e.g., DCI or PDCCH) that may indicate the timing advance offset value. A MAC layer control message (e.g., MAC The wireless device may receive a CE and / or RAR. The wireless device may start (and / or restart) the time alignment timer based on receiving (e.g., after receiving or in response to receiving) a timing advance command MAC control element and / or a PDCCH message indicating a timing advance adjustment. The wireless device may determine that the timing advance offset value is valid for at least the time period that the TAT is operational. The wireless device may verify the TA value based on one or more verification conditions. The wireless device may start (and / or restart) the time alignment timer based on (e.g., after receiving or in response to) a determination that the TA is verified. The wireless device may: For example, the wireless device may determine that the TAT has expired when the TAT has run for the time interval (and / or duration) indicated by the value of the TAT. Based on the expiration of the TAT, the wireless device may determine that the timing advance offset value is invalid in response to the expiration.

[0188] The timing advance value may be referred to as a timing alignment value. The timing advance offset value may be referred to as a timing alignment offset value. The timing alignment timer may be referred to as one or more of a time alignment timer, a timing advance timer, and / or a time advance timer. The timing advance group may be referred to as a timing alignment group.

[0189] The one or more configuration parameters may indicate a number / amount of opportunities for one or more uplink radio resources (e.g., an example parameter name: NumOccasions). The number / amount of opportunities may indicate that one or more uplink radio resources are one-time use resources (or grants) for a single uplink transmission. The number / amount of opportunities may indicate that one or more uplink radio resources include multiple uplink radio resources. The number / amount of opportunities may be: It may indicate that the one or more uplink radio resources include one or more periodic radio resources.

[0190] The one or more configuration parameters may indicate a time domain resource allocation of one or more uplink radio resources. The one or more configuration parameters may indicate a periodicity (e.g., example parameter name: Periodicity) of one or more uplink radio resources in the RRC_INACTIVE (and / or RRC_IDLE) state. The one or more configuration parameters may include a time offset. The time offset may include a time domain offset relative to (and / or associated with) a time reference. The time reference may include a specific SFN (e.g., of H-SFN), a specific subframe number, a specific slot number, a specific symbol number, and / or combinations thereof. The time reference may include a predefined one (e.g., SFN=0 and / or H-SFN=0). The time reference may include a predefined value (e.g., SFN=0 and / or H-SFN=0), for example, if the field of the time reference is not present in the one or more configuration parameters. The wireless device may receive one or more uplink grants, for example, as indicated by the one or more configuration parameters. The one or more uplink grants may indicate one or more uplink radio resources. The one or more uplink radio resources may start at a symbol (of a slot of a SFN of a H-SFN) indicated by the time offset. The one or more uplink radio resources may include: The Nth uplink grant may occur periodically from the symbol using the N*periodicity. The wireless device may determine (e.g., sequentially) that an Nth uplink grant of the one or more uplink grants occurs in a transmission time interval (TTI, e.g., slot, minislot, symbol) based on the time offset and the N*periodicity. The time offset may be indicated / defined in terms of a number / amount of symbols, a number / amount of slots, a number / amount of subframes, a number / amount of SFNs, a number / amount of H-SFNs, and / or combinations thereof. The one or more configuration parameters may include a parameter timeDomainOffset, etc. The parameter (e.g., timeDomainOffset) may indicate a time offset that the wireless device receives from the base station. The one or more configuration parameters may include a parameter timeReferenceSFN, etc. (e.g., a time reference reference defined in terms of SFN and / or H-SFN). The parameter (e.g., timeReferenceSFN) may indicate SFN as a time reference used for determination of the time offset of the resource in the time domain. The SFN may repeat with a period of 1024 frames. The wireless device may receive one or more configuration parameters indicating timeReferenceSFN=0 via SFN=3. The parameter timeReferenceSFN=0 may indicate a time reference SFN=0 that is 3 SFNs before SFN=3. The parameter timeReferenceSFN=0 may indicate a time reference SFN=0 that is 1021 SFNs after SFN=3. The wireless device may determine the closest SFN having the indicated number / amount prior to receiving the configured grant configuration. The wireless device may determine that timeReferenceSFN=0 indicates a time reference SFN=0 that is 3 SFNs before SFN=3. The wireless device may determine (e.g., sequentially determine) that the Nth uplink grant occurs (and / or the uplink grant recurs) in a symbol where:

[0191] [(SFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot)+(slot number in frame×numberOfSymbolsPerSlot)+symbol number in slot]=(timeReferenceSFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot+timeDomainOffset×numberOfSymbolsPerSlot+S+N×periodicity) modulo(1024×numberOfSlotsPerFrame×numberOfSymbolsPerSlot). The parameter numberOfSlotsPerFrame may indicate the number / amount of slots in a frame. The parameter numberOfSymbolsPerSlot may indicate the number / amount of symbols in a slot. The parameter periodicity may indicate a periodicity of one or more uplink radio resources indicated by one or more configuration parameters. S may be a symbol number (and / or a symbol offset) indicated by one or more configuration parameters. The determination of the Nth uplink grant may indicate that the grant (e.g., a configured grant, a pre-configured grant, etc., as described in connection with FIG. 18A ) may not require an additional activation message (e.g., a DCI, MAC CE, and / or RRC) to activate (and / or initiate) one or more uplink radio resources (and / or grants, configured grants, pre-configured grants, etc.).The wireless device may determine that the Nth uplink grant occurs (and / or the uplink grant recurs) at a symbol where [(SFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot)+(number of slots in frame×numberOfSymbolsPerSlot)+number of symbols in slot]=[(SFNstart time×numberOfSlotsPerFrame×numberOfSymbolsPerSlot+slotstart time×numberOfSymbolsPerSlot+symbolstart time)+N×periodicity] modulo(1024×numberOfSlotsPerFrame×numberOfSymbolsPerSlot). The determination of the Nth uplink grant above may indicate that the grant (e.g., a configured grant, a pre-configured grant, etc., as described with respect to FIG. 18B ) requires an additional activation message (e.g., DCI, MAC CE, and / or RRC) that activates (and / or initiates) one or more uplink radio resources (and / or grants, configured grants, pre-configured grants, etc.). The SFNstart time, slotstart time, and symbolstart time may indicate (e.g., correspond to) the SFN, slot, and symbol, respectively, at which one or more uplink grants are initialized and / or reinitialized. The SFNstart time, slotstart time, and symbolstart time indicate (e.g., correspond to) the SFN, slot, and symbol, respectively, at which the wireless device receives an indication (e.g., DCI) to initialize (and / or reinitialize, activate, reactivate, etc.) one or more uplink grants. The SFNstart time, slotstart time, and symbolstart time may indicate (e.g., correspond to) the SFN, slot, and symbol, respectively, of a PUSCH transmission opportunity at which one or more uplink grants are initialized and / or reinitialized. The PUSCH transmission opportunity may indicate (e.g., correspond to) a first opportunity for PUSCH transmission at which one or more uplink grants are initialized and / or reinitialized.

[0192] The wireless device may start and / or resume transmission over one or more uplink radio resources in the RRC_INACTIVE (and / or RRC_IDLE) state. The wireless device may start and / or resume transmission over one or more uplink radio resources in the RRC_INACTIVE (and / or RRC_IDLE) state based on one or more conditions. The wireless device may receive a configuration parameter indicative of the one or more conditions. The wireless device may determine whether a cell in which one or more uplink radio resources in the RRC_INACTIVE (and / or RRC_IDLE) state are configured supports transmission over the one or more uplink radio resources. The wireless device may: The wireless device may receive one or more RRC messages (e.g., SIBs). The one or more RRC messages may include configuration parameters indicating whether / when the cell supports transmission over one or more uplink radio resources. The configuration parameters may indicate which types of transmissions are supported (and / or available) over the one or more uplink radio resources. The types may include control plane (CP) transmissions and / or user-plane (UP) transmissions. The configuration parameters may indicate (e.g., which) type of network to which the cell is connected supports transmission over one or more uplink radio resources. The wireless device may determine whether / when transmission over one or more uplink radio resources is supported in the cell based on, for example, the type of network to which the cell is connected. The type of network may include one or more generations and / or versions of a network system (e.g., 5G Core, Evolved Packet Core (EPC), 3GPP Rel. 15, 16, 17, prior / later releases, etc.) and / or one or more radio technologies (e.g., Wi-Fi, 5G, Bluetooth, satellite, etc.). The configuration parameters may indicate what type of spectrum (and / or frequency bands) supports transmission over one or more uplink radio resources. The type of spectrum may include licensed spectrum and / or unlicensed spectrum. The type of spectrum may include CBRS (Citizens Broadband Radio Service, The type of spectrum may include the 5G LTE Service band (e.g., wideband in the 3.5 GHz band). The type of spectrum may include the millimeter wave band (e.g., above the 30 GHz band). The configuration parameters in the RRC message may indicate a combination of the type of network, the type of spectrum, and / or the type of transmission. The parameter cp-PUR-5GC in the RRC message (e.g., the parameter value may be "true" / "false" or "enabled" / "disabled") may indicate whether / when CP transmission using PUR is supported in the cell (e.g., when connected to the 5G core network and / or any other network). The parameter cp-PUR-EPC in the RRC message (e.g., the parameter value may be "true" / "false" or "enabled" / "disabled") may indicate whether / when CP transmission using PUR is supported in the cell (e.g., when connected to the EPC). The wireless device may determine that PUR is supported in a cell (e.g., if / when connected to an EPC) if, for example, an RRC message received from the cell indicates cp-PUR-EPC="true" (or "enabled").

[0193] The wireless device may start and / or resume transmission over one or more uplink radio resources in the RRC_INACTIVE (and / or RRC_IDLE) state. The wireless device may start and / or resume transmission over one or more uplink radio resources in the RRC_INACTIVE (and / or RRC_IDLE) state based on, for example, one or more conditions. The wireless device may initiate and / or resume transmission over one or more uplink radio resources in the RRC_INACTIVE (and / or RRC_IDLE) state, for example, if at least one of the following conditions is satisfied: the wireless device has a valid configuration of one or more uplink radio resources, the wireless device has a valid timing advance value, the wireless device triggers an RRC connection establishment request, the wireless device triggers an RRC connection resumption request, the wireless device has a valid stored value of a security parameter (e.g., nextHopChainingCount provided in an RRCConnectionRelease message with a pause indication during a preceding pause procedure), the wireless device triggers an establishment or resumption request for a mobile-originated call and / or the establishment cause is mo-Data, mo-ExceptionData, or delayTolerantAccess, and / or the size of the MAC PDU (e.g., including total UL data) is expected to be less than or equal to a transport block size (TBS) configured for PUR.

[0194] The wireless device may determine whether the wireless device has a valid timing advance value based on one or more validation conditions (e.g., TAT-based validation and / or measurement-based validation). The wireless device may determine that a configuration of one or more uplink radio resources is valid based on, for example, a configuration parameter of the one or more uplink radio resources indicating validity of the configuration. The wireless device may receive one or more messages comprising the configuration parameter. The configuration may be determined to be valid, for example, if a field (e.g., config) in the message is set to setup (e.g., true). The configuration may be determined to be valid, for example, if a field (e.g., config) is set to release (e.g., false).

[0195] The wireless device may determine when a timing advance value is valid (or not valid) for transmission over one or more uplink radio resources in the RRC_INACTIVE (and / or RRC_IDLE) state based on one or more verification conditions. The one or more verification conditions may include TAT-based verification and / or measurement-based verification. The wireless device may determine to apply a condition configured from the one or more verification conditions. The wireless device may receive one or more messages including a configuration parameter for a first verification condition (e.g., TAT-based verification) of the one or more verification conditions. The message may not include a configuration parameter for a second verification condition (e.g., measurement-based verification) of the one or more verification conditions. The wireless device may determine when the timing advance value is valid (or not valid) based on the first verification condition. The wireless device may determine when the timing advance value is valid (or not valid) based on at least the first and second verification conditions, for example, if the message includes configuration parameters for the first and second verification conditions (e.g., TAT-based verification) and the second verification condition (e.g., measurement-based verification).

[0196] The wireless device may determine validity of a timing advance value based on the TAT, for example, for TAT-based validation. The wireless device may receive one or more RRC messages including a value of the TAT. The TAT may be for a cell (and / or a TAG including the cell) for which one or more uplink radio resources in an RRC_INACTIVE (and / or RRC_IDLE) state are configured. The wireless device may determine that a timing advance value for a transmission over one or more uplink radio resources is valid, for example, if the TAT is active. The wireless device may determine that validation of a timing advance value for a transmission is not based on the TAT, for example, if a value of the TAT is not configured (e.g., the RRC message does not include a value of the TAT).

[0197] FIG. 20 illustrates an example of a resource configuration. The resource configuration may be based on one or more timers. The wireless device 2002 may transmit / transmit (e.g., at 2003) one or more uplink transmissions to the base station 2001. The transmitting / transmitting one or more uplink transmissions may be based on a valid timing advance (TA) value. The transmitting / transmitting one or more uplink transmissions may be during a time period during which a time alignment timer (TAT) is running. The time period during which the TAT is running may be from a first period (e.g., 2004) when the TAT starts to a second period (e.g., 2005) when the TAT ends. The one or more uplink transmissions may occur during a time period during which the wireless device 2002 is in an RRC_INACTIVE state (and / or an RRC_IDLE state). The wireless device 2002 may receive one or more RRC messages including configuration parameters for uplink resources from the base station 2001 in an RRC_INACTIVE state (and / or an RRC_IDLE state). The uplink resources may be available, scheduled, and / or configured in the RRC_INACTIVE state (and / or the RRC_IDLE state). The wireless device 2002 may transmit / transmit an uplink packet via one or more opportunities of the uplink resources, for example, if a TA value for the transmission is verified (e.g., in 2003). The wireless device 2002 may determine (e.g., verify) a TA value as valid to be used for one or more data packet transmissions in the RRC_INACTIVE state (and / or the RRC_IDLE state), for example, if a TAT is activated (e.g., in 2004-2005). The wireless device 2002 may transmit / transmit data via one or more uplink resources in the RRC_INACTIVE state (and / or the RRC_IDLE state), for example, if the wireless device may determine (e.g., verify) a TA value as valid and / or if the TAT is activated. ... (e.g., verify) a TA value as valid to be used for one or more data packet transmissions in the RRC_INACTIVE state (and / or the RRC_IDLE state), for example, if a TAT is not activated. (and / or if the TAT expires), the wireless device 2002 may determine that the TA value is invalid. The wireless device 2002 may stop (e.g., be prohibited from performing) uplink transmissions over the uplink resources (e.g., at 2006), for example, at and / or after the time the TAT expires (e.g., at 2005).

[0198] The wireless device may determine the validity of the timing advance value based on measurements of DL RSs of a cell, for example, for measurement-based validation. The wireless device may determine when a timing advance value for transmission over one or more uplink radio resources is valid, for example, based on measurements of DL RSs of a cell for which one or more uplink radio resources are configured. The measurements of the DL RSs of the cell may be serving cell measurements (e.g., RSRP). The wireless device may receive one or more RRC messages including one or more thresholds of measurements. The wireless device may measure at least one DL RS received from a cell for which one or more uplink radio resources are configured, for example, a TRP. The at least one DL RS may include a synchronization signal and / or a CSI-RS. The measurements of the at least one DL RS may include an RSRP. The measurements of the at least one DL RS may include an RSRQ and / or an RSSI (Received Signal Strength Indicator). The wireless device may determine that a timing advance value for transmission over one or more uplink radio resources is valid, for example, if the measurements are within a range indicated by one or more thresholds. The wireless device may determine that a timing advance value for transmission over one or more uplink radio resources is valid, for example, if the measurement value has not changed beyond a range indicated by one or more thresholds since the wireless device measured the previous DL RS. The wireless device may measure the previous DL RS based on, for example, a measurement configuration that schedules the one or more measurements. The wireless device may measure the previous DL RS regardless of, for example, a resource allocation of uplink resources. The wireless device may measure the previous DL RS for the last TA verification that the wireless device performed for transmission over one or more uplink radio resources.

[0199] The one or more thresholds of the measurement may include an increase threshold and / or a decrease threshold. The increase threshold and / or decrease threshold may be based on (e.g., indicated / defined with respect to) RSRP, RSRQ, RSSI, and / or any combination thereof. The increase threshold and / or decrease threshold may indicate a threshold of change in the cell. The increase threshold and / or decrease threshold may indicate a range within which the wireless device determines that the TA value is valid (e.g., to be used for transmission over one or more uplink radio resources in RRC_INACTIVE (and / or RRC_IDLE)). The range may indicate an area of ​​the cell (e.g., a particular coverage tier in the cell, e.g., a central area, a cell edge area, etc.) within which the TA value may be used for transmission over one or more uplink radio resources in the RRC_INACTIVE (and / or RRC_IDLE) state.

[0200] The increase threshold and / or decrease threshold may indicate a threshold value in dBm or any other measurement unit. The wireless device may determine that the TA value is valid, for example, if the measured value of the DL RS of the cell is less than the increase threshold. The wireless device may determine that the TA value is valid, for example, if the measured value of the DL RS of the cell is greater than the decrease threshold.

[0201] FIG. 21A is an example of TA verification. A threshold value may be used to verify the RSRP value. The wireless device may receive one or more messages (e.g., RRC messages) that include an increase threshold value and / or a decrease threshold value. The increase threshold value and / or the decrease threshold value may be an absolute value of the threshold value (e.g., in dBm and / or any other unit of measurement). The TA value may be, for example, If the measurement (e.g., RSRP) is within an RSRP range indicated by the increase threshold and / or decrease threshold, it may be used for transmission on one or more radio resources in the RRC_INACTIVE (and / or RRC_IDLE) state. The wireless device may determine that the TA value is valid, for example, if the measurement (e.g., RSRP) is less than the increase threshold and / or greater than the decrease threshold.

[0202] The increase and / or decrease thresholds may, for example, indicate values ​​in dB for TA verification. The wireless device may determine that the TA value is valid, for example, if the measurement value of the DL RS of the cell has not increased beyond an increase threshold. The wireless device may determine that the TA value is valid, for example, if the measurement value of the DL RS of the cell has not decreased beyond a decrease threshold. The wireless device may determine how much the measurement value has changed (e.g., increased and / or decreased) based on one or more reference measurements. The one or more reference measurements may include one or more measurements performed for a last (e.g., most recent) TA verification. The last TA verification may be performed by the wireless device for transmission over one or more uplink radio resources in an RRC_INACTIVE (and / or RRC_IDLE) state.

[0203] FIG. 21B illustrates an example of TA validation. TA validation may be based on relative thresholds. A wireless device may receive one or more messages (e.g., RRC messages) including an increase threshold and / or a decrease threshold. The increase threshold and / or decrease threshold may be a threshold value relative to a reference measurement (e.g., in dB and / or any other measurement units). A wireless device may compare a measurement to the reference measurement, for example, when the wireless device determines whether a TA value used for a transmission is valid. A wireless device may determine that a TA value is valid, for example, when a measurement value of a DL RS of a cell has not increased beyond an increase threshold and / or when a measurement value of a DL RS of a cell has not decreased beyond a decrease threshold. A wireless device may determine that a TA value used for a transmission over one or more radio resources in an RRC_INACTIVE (and / or RRC_IDLE) state is valid, for example, when a measurement value of a DL RS of a cell has increased beyond an increase threshold and / or when a measurement value of a DL RS of a cell has decreased beyond a decrease threshold.

[0204] A wireless device may receive one or more messages including the increase threshold and the decrease threshold. A wireless device may use the increase threshold and / or the decrease threshold for TA validation. A wireless device may receive one or more messages including one of the increase threshold and / or the decrease threshold. A wireless device may use one of the increase threshold and / or the decrease threshold. A wireless device in a cell edge area may receive one or more messages including the increase threshold. A wireless device (e.g., in a cell center area) may receive a message including the decrease threshold. The increase and / or decrease thresholds may be absent in one or more messages. The wireless device may receive a message that does not include field values ​​for the increase and decrease thresholds. The wireless device may determine that TA validation is not based on measurements (e.g., RSRP, RSRP, and / or RSSI). TA validation based on changes in cell measurements (e.g., RSRP, RSRP, and / or RSSI) may not be applicable, for example, if the increase and / or decrease thresholds are not configured.

[0205] The wireless device may monitor the PDCCH identified / indicated by the RNTI during the response window. The wireless device may monitor the PDCCH identified / indicated by the RNTI during the response window, for example, after or in response to transmitting data over one or more uplink radio resources. The wireless device may receive one or more messages (e.g., RRC messages) indicating the RNTI and / or a size of the response window (e.g., example parameter name: ResponseWindowTimer). The response window may start from a reference time associated with transmitting data over one or more uplink radio resources. The reference time may include a transmission time interval (e.g., a frame, a subframe, a slot, and / or a symbol) during which the wireless device may transmit / transmit data over one or more uplink radio resources. The reference time may include the end of the corresponding PUSCH transmission (e.g., transmission of data over one or more uplink radio resources). The reference time may be at the first PDCCH opportunity from the end of the corresponding PUSCH transmission (e.g., transmission of data over one or more uplink radio resources). The reference time may include a time offset (e.g., predefined or RRC configured). The reference time may include a subframe (or slot) that may include the end of the corresponding PUSCH transmission plus a time offset. The reference time may include the first PDCCH opportunity from the end of the corresponding PUSCH transmission plus a time offset.

[0206] The wireless device may receive a control message (e.g., DCI) over the PDCCH during a time window (e.g., ResponseWindowTimer is running). The received control message (e.g., DCI) may be CRC-scrambled by an RNTI that the wireless device receives for transmission over one or more radio resources in an RRC_INACTIVE state (and / or an RRC_IDLE state). The control message (e.g., DCI) may include an uplink grant for retransmission of data. The wireless device may start and / or restart the time window (e.g., ResponseWindowTimer) based on (e.g., after receiving or in response to) receiving the uplink grant. The time window may start and / or restart at the last slot (and / or subframe, symbol, etc.) of the PUSCH transmission corresponding to the retransmission indicated by the uplink grant. The time window may start and / or restart at the first PDCCH opportunity from the end of the PUSCH transmission corresponding to the retransmission indicated by the uplink grant. The control message (e.g., DCI) may indicate an acknowledgement (e.g., L1 ACK) for the transmission of data over one or more radio resources in an RRC_INACTIVE state (and / or an RRC_IDLE state). The wireless device may decide to stop a time window (e.g., ResponseWindowTimer) and / or may determine that the transmission of data over one or more radio resources is successful. The control message (e.g., DCI) may include a downlink assignment of a PDSCH including a MAC PDU. The wireless device may decide to stop a time window (e.g., ResponseWindowTimer) and / or may determine that the transmission of data over one or more radio resources is successful, for example, if the wireless device successfully decodes the MAC PDU. The control message (e.g., The control message (DCI) may indicate a failure (e.g., fallback) of transmission of data. The wireless device may determine to stop the time window (e.g., ResponseWindowTimer) based on (e.g., after receiving or in response to receiving) a control message indicating a failure (e.g., fallback). For example, based on (e.g., after receiving or in response to receiving) a control message indicating a failure (e.g., fallback), the wireless device may determine that transmission of data over one or more radio resources has failed. The wireless device may initiate the random access procedure based on (e.g., after receiving or in response to receiving) a control message indicating a failure (e.g., a fallback). The wireless device may initiate the random access procedure based on (e.g., after receiving or in response to receiving) a control message indicating a failure (e.g., a fallback). The wireless device may determine that a time window (e.g., a ResponseWindowTimer) has expired. The wireless device may determine that a pre-configured uplink grant was skipped and / or that a PUR transmission failed based on (e.g., after receiving or in response to) the expiration of the time window.

[0207] The wireless device and / or base station may use HARQ operations and / or processes for one or more retransmissions of an uplink transmission in an RRC_INACTIVE state (and / or an RRC_IDLE state). The wireless device may transmit / transmit a data packet via one or more uplink radio resources configured for the RRC_INACTIVE state (and / or an RRC_IDLE state) (e.g., as shown / described with respect to FIG. 17). The wireless device may monitor the PDCCH, for example, based on (e.g., after transmitting or in response to) transmitting a data packet during a time period in which the RRC state is held as the RRC_INACTIVE state (and / or an RRC_IDLE state). The wireless device may receive a DCI via the PDCCH, which may indicate an uplink grant for retransmission of the data packet. The uplink grant may indicate one of the one or more uplink radio resources as the uplink radio resource for the retransmission. The uplink grant may indicate an uplink radio resource for the retransmission, which may be independent of (e.g., allocated separately from) the one or more uplink radio resources. The wireless device may, for example, receive an indication (e.g., a different type of DCI) indicating to perform an RA procedure. The wireless device may, for example, receive an indication (e.g., a different type of DCI) indicating to perform an RA procedure instead of receiving an uplink grant. The indication may indicate a failure to transmit a data packet. The wireless device may switch / transition to the RRC CONNECTED state, for example, by initiating and / or performing an RRC connection setup procedure and / or an RRC restart procedure. The wireless device may initiate (and / or perform) an RRC connection setup procedure and / or an RRC restart procedure based on the RA procedure. The wireless device may initiate the RA procedure based on receiving an indication (e.g., indicating that the wireless device performs an RA procedure). The wireless device may initiate the RA procedure based on receiving a paging message (e.g., indicating that the wireless device performs an RA procedure) and / or based on an uplink packet arrival.One or more uplink radio resources configured for the RRC_INACTIVE (and / or RRC_IDLE) state may not be used during a time period when the wireless device is in the RRC_CONNECTED state. The wireless device may not transmit / transmit (and / or may stop transmitting) data packets over one or more uplink radio resources when the RRC state is RRC_CONNECTED, for example. The wireless device may not transmit / transmit (and / or may stop transmitting) data packets over one or more uplink radio resources based on the one or more uplink radio resources configured for the RRC_INACTIVE (and / or RRC_IDLE) state and / or the RRC state being switched / transitioned to the RRC_CONNECTED state. The wireless device may release (e.g., clear, deactivate, suspend, and / or discard) an uplink grant indicating one or more uplink radio resources based on (e.g., after or in response thereto), one or more uplink radio resources configured for the RRC_INACTIVE (and / or RRC_IDLE) state and / or the RRC state being switched / transitioned to the RRC_CONNECTED state.

[0208] The wireless device may transmit / transmit one or more messages (e.g., an RRC message such as PURConfigurationRequest) that may request one or more parameters of a grant (e.g., a configured grant, a pre-configured grant, etc.) indicating one or more uplink radio resources in an RRC_INACTIVE state (and / or an RRC_IDLE state). The wireless device may initiate a procedure, e.g., a wireless device initiated procedure, to transmit the messages. The wireless device may transmit / transmit one or more messages, e.g., based on (e.g., after receiving or in response to receiving) a request from a base station for a base station initiated procedure. The wireless device may transmit / transmit one or more messages during a time period in which the wireless device is in any RRC state (e.g., RRC_CONNECTED, RRC_INACTIVE, and / or RRC_IDLE). The wireless device may transmit messages during a time period in which the wireless device is in a particular RRC state. The wireless device may transmit messages during a time period in which the wireless device is in an RRC_INACTIVE state (and / or an RRC_IDLE state). The wireless device may send / transmit one or more messages during a time period when the wireless device is in the RRC_CONNECTED state. The one or more messages may indicate data traffic information. The one or more messages may indicate a number / amount of opportunities for one or more uplink radio resources in the RRC_INACTIVE state (and / or the RRC_IDLE state), e.g., an exemplary parameter (e.g., requestedNumOccasions). The one or more messages may indicate a periodicity for one or more uplink radio resources in the RRC_INACTIVE state (and / or the RRC_IDLE state), e.g., an exemplary parameter (e.g., requestedPeriodicity). The one or more messages may indicate a TB size of a data packet to be sent / transmitted via one or more uplink radio resources in the RRC_INACTIVE state (and / or the RRC_IDLE state), e.g., an exemplary parameter (e.g., requestedTBS).The one or more messages may indicate a time offset, e.g., an example parameter (e.g., requestedTimeOffset), for one or more uplink radio resources in the RRC_INACTIVE state (and / or the RRC_IDLE state). The wireless device may not receive (e.g., do not expect to receive) a response to the message from the base station. The wireless device may receive from the base station one or more configuration parameters for transmission of uplink data over one or more uplink radio resources in the RRC_INACTIVE (and / or RRC_IDLE) state.

[0209] The wireless device may be configured with an operating band of the cell for transmission in the RRC_INACTIVE (and / or RRC_IDLE) state. The operating band for transmission may include a carrier bandwidth. The operating band may include a DL band and / or a UL band. The operating band for transmission may include a BWP. The BWP may include a DL BWP (e.g., a DL band) and / or a UL BWP (e.g., a UL band). The wireless device may receive one or more messages (e.g., an RRC message and / or an RRC release message) that include a configuration of the operating band for transmission / reception in the RRC_INACTIVE (and / or RRC_IDLE) state in the cell. The message may indicate a configuration based on the number / amount of RBs (and / or PRBs) and frequency location (e.g., center frequency location). The configuration may indicate a numerology (e.g., subcarrier spacing) to be used in the operating band. The configuration may indicate separate numerology (e.g., subcarrier spacing) for the DL band (e.g., DL BWP) and the UL band (e.g., UL BWP). The numerology (e.g., subcarrier spacing) configured for the DL band (e.g., DL BWP) and the UL band (e.g., UL BWP) may be different or the same.

[0210] The one or more messages may indicate the location and range (e.g., start, size, and / or center frequency and bandwidth, etc.) of the operating band. The location and / or range (e.g., start, size, and / or center frequency and bandwidth, etc.) of the operating band may be indicated / defined in terms of resource units (e.g., RBs and / or PRBs), e.g., as multiples of resource units. The location and / or range of the operating band may be at least a portion of one carrier of the cell. The one or more messages may indicate the location and / or range of the operating band based on a frequency offset and bandwidth relative to a center frequency of the carrier bandwidth of the cell. The one or more messages may indicate a center frequency (e.g., The location and extent of the operating band may be indicated based on the frequency offset relative to the initial BWP and the bandwidth of the operating band.

[0211] The one or more messages may indicate numerology information (e.g., μ and / or subcarrier spacing) to be used in the operating band. The wireless device may determine the RE structure from the numerology information. The messages may indicate the control channels (e.g., PDCCH and / or PUCCH), data channels (e.g., PDSCH and / or PUSCH), and / or reference signals (RSs). The one or more messages may include configuration parameters for the control channel, data channel, and / or reference signal (SSB, CSI-RS, and / or SRS). The one or more messages may indicate a frequency location of the control channel, data channel, and / or reference signal based on a frequency offset relative to a reference location in the operating band. The reference location may be a start (and / or end) point of the first RB that coincides with the start (and / or end) point of the operating band. One or more radio resources in the RRC_INACTIVE state (and / or RRC_IDLE state) may be allocated (e.g., using a frequency offset from the reference location) to a start point that includes a size indicated / defined in terms of a number of RBs (and / or PRBs). The wireless device may allocate the control channel, data channel, and / or reference signal (SSB, CSI-RS, and / or SRS) based on the determined RE structure. The location and / or size of the data channel and / or reference signal may be determined.

[0212] One or more radio resources in an RRC_INACTIVE state (and / or an RRC_IDLE state) may be allocated in an operating band including one or more sub-bands (e.g., BWP). One or more radio resources in an RRC_INACTIVE state (and / or an RRC_IDLE state) may be allocated to a specific sub-band in the operating band. One or more messages that the wireless device may receive may indicate an operating band including one or more sub-bands (e.g., BWP). The one or more messages may indicate one or more sub-bands having / using separate locations (e.g., frequency locations), sizes (e.g., bandwidths), and / or numerologies (e.g., subcarrier spacing). The RE structure for configuring one or more sub-bands may differ from the RE structure for configuring the operating band. The DL band (e.g., DL BWP) and the UL band (e.g., UL BWP) may be configured separately. The DL band and the UL band may have different configuration information, for example, with respect to frequency locations and numerologies (e.g., subcarrier spacing). The wireless device may receive DL control messages (e.g., DCI via PDCCH) and / or DL ​​data (e.g., transport blocks via PDSCH) based on information of the configured operating band (and / or sub-band) in the DL band. The wireless device may transmit UL control (e.g., PUCCH) and / or UL data (e.g., transport blocks via PUSCH) based on information of the configured operating band (and / or sub-band) in the UL band. One or more radio resources in the RRC_INACTIVE state (and / or RRC_IDLE state) may be allocated per sub-band. The frequency location and / or size of the one or more radio resources may be for the sub-band.

[0213] In the case of transmission over one or more radio resources in the RRC_INACTIVE state (and / or the RRC_IDLE state), the base station may send / transmit one or more messages (e.g., RRC messages) to the wireless device to configure configuration parameters. The configuration parameters may include: antenna ports to be used for transmission over one or more radio resources in the RRC_INACTIVE state (and / or the RRC_IDLE state); a DMRS configuration to be used for transmission over one or more radio resources in the RRC_INACTIVE state (and / or the RRC_IDLE state); a configured and / or preconfigured grant timer value (e.g., the configured and / or preconfigured grant timer may be a multiple of the periodicity); a frequency domain resource allocation; a frequency hopping configuration (e.g., intra-slot frequency hopping and / or inter-slot frequency hopping; if the field is absent, frequency hopping may not be configured), e.g., a frequency hopping offset to be used when frequency hopping is enabled; an MCS table that the wireless device may use for transmission over one or more radio resources in the RRC_INACTIVE state (and / or the RRC_IDLE state) for PUSCH transmissions (e.g., PUSCH transmissions with and / or without transform precoding); The wireless device may determine a predefined MCS (e.g., qam64, qam256, etc.), an MCS table, a modulation order, a code rate, and / or a TB size for transmission over one or more radio resources, a number / amount of HARQ processes configured for transmission over one or more radio resources in an RRC_INACTIVE state (and / or an RRC_IDLE state), uplink power control parameters for transmission over one or more radio resources, e.g., an indicator and / or index for closed loop uplink power control, one or more reference power values ​​(e.g., p0), and / or a path loss scaling value (e.g., Alpha), a periodicity of one or more radio resources, where for example a valid periodicity value may be determined (e.g., predefined) based on a numerology (e.g., subcarrier spacing) and / or the periodicity may be an absolute time value and / or may be defined in terms of a TTI (symbol, slot, subframe, system frame, and / or any combination thereof), a periodicity, an RBG size for PUSCH transmission over one or more radio resources, a redundancy version (RV) sequence (e.g., [0 2 3 1], [0 3 0 3]) for transmission over one or more radio resources, a number / amount of repetitions of transmission over one or more radio resources, an additional activation message (e.g., DCI, MAC , DMA, etc.) to activate one or more radio resources (e.g., as described / illustrated with respect to FIG. 18A and / or FIG. 18B ).Nth uplink grant), a time domain allocation indicating a starting symbol (e.g., a starting symbol number (or symbol offset) S used for determining the Nth uplink grant) and length L (e.g., the value of the time domain allocation can be a combination of the starting symbol and the length), a PUSCH mapping type for transmission over the one or more radio resources, a time domain offset defined with respect to a time reference (e.g., SFN=0 and / or timeReferenceSFN), and / or an indicator indicating whether a beta offset value is dynamically or semi-statically configured, where the beta offset value may be used to determine uplink power and / or UCI multiplexing of the PUSCH transmission over the one or more radio resources.

[0214] One or more radio resources may be configured with / using a particular BWP. The wireless device may receive one or more messages (e.g., RRC messages) including configuration parameters for the particular BWP. The particular BWP may include a DL BWP and / or a UL BWP. The configuration parameters may indicate a numerology (e.g., subcarrier spacing) to be used in the particular BWP. The configuration parameters may indicate a numerology to be applied to the DL BWP and / or the UL BWP. The configuration parameters may indicate a numerology to be applied to the DL BWP and / or the UL BWP, respectively. The numerology used in the DL BWP and / or the UL BWP may include a separate field and / or indicator indicating the numerology that may be used in the BWP. The configuration parameters may be the same or different. The configuration parameters may indicate radio resource configuration parameters of DL and / or UL control channels (e.g., PDCCH and / or PUCCH) used for transmission over one or more radio resources. The configuration parameters may include radio resource configuration parameters of DL and / or UL data channels (e.g., PDSCH and / or PUSCH) used for transmission over one or more radio resources. The DL control and / or data channels (e.g., PDCCH and / or PDSCH) may be configured within a DL BWP. The UL control and / or data channels (e.g., PUCCH and / or PUSCH) may be configured within a UL BWP.

[0215] The specific BWP may include an initial BWP. The DL BWP of the specific BWP may include an initial DL BWP. The UL BWP of the specific BWP may include an initial UL BWP. The specific BWP may be configured separately from the initial BWP. The DL BWP of the specific BWP may be different from the initial DL BWP. The UL BWP of the specific BWP may be different from the initial UL BWP. One or more radio resources may be associated with the DL BWP and / or the UL BWP. The PDCCH (e.g., ACK, NACK, and / or fallback response for the transmission over the one or more radio resources) and / or the PDSCH (e.g., RRC response for the RRC message transmitted over the one or more radio resources) associated with the transmission over the one or more radio resources may be configured with the DL BWP. The PUCCH (e.g., ACK and / or NACK response for the PDSCH) and / or the PUSCH (e.g., data over the one or more radio resources) associated with the transmission over the one or more radio resources may be configured with the UL BWP. The wireless device may determine that a particular BWP (e.g., DL BWP and / or UL BWP) includes an initial BWP and / or is an initial BWP (e.g., is an initial DL BWP and / or an initial UL BWP, respectively). For example, if a field indicating a configuration (e.g., frequency location, bandwidth, and / or numerology (e.g., subcarrier spacing)) of a particular BWP (e.g., different from the initial BWP) is absent in the configuration parameters indicating one or more radio resources, the wireless device may determine that a particular BWP (e.g., DL BWP and / or UL BWP) includes an initial BWP and / or is an initial BWP (e.g., is an initial DL BWP and / or an initial UL BWP, respectively).

[0216] The specific BWP may be the last BWP (e.g., the most recent BWP) that the wireless device used in the RRC_CONNECTED state. The DL BWP of the specific BWP may be the last DL BWP (e.g., the most recent DL BWP) that the wireless device used in the RRC_CONNECTED state. The UL BWP of the specific BWP may be the last UL BWP (e.g., the most recent UL BWP) that the wireless device used in the RRC_CONNECTED state. The wireless device may switch / transition from the RRC_CONNECTED state to the RRC_INACTIVE state (and / or the RRC_IDLE state). The BWP (e.g., the last DL BWP and / or the last UL BWP) that the wireless device uses in the RRC_CONNECTED state may be the last BWP that the wireless device switched / transitioned to the RRC_INACTIVE state. (and / or RRC_IDLE state). For example, the configuration (e.g., frequency location, bandwidth, and / or numerology) of a particular BWP (e.g., different from the last BWP) may be used. If a field indicating a subcarrier spacing (e.g., subcarrier spacing) is absent in the configuration parameters indicating one or more radio resources, the wireless device may determine that a particular BWP (e.g., a DL BWP and / or a UL BWP) is a BWP (e.g., the last DL BWP and / or the last UL BWP, respectively).

[0217] The specific BWP may be configured separately from the initial BWP. The DL BWP of the specific BWP may be different from the initial DL BWP. The UL BWP of the specific BWP may be different from the initial UL BWP. One or more radio resources may be associated with the DL BWP and / or the UL BWP. A PDCCH (e.g., The PUCCH (e.g., ACK and / or NACK responses to a PDSCH) and / or PUSCH (e.g., data over one or more radio resources) associated with a transmission over one or more radio resources may be configured with a DL BWP. The PUCCH (e.g., ACK and / or NACK responses to a PDSCH) and / or PUSCH (e.g., data over one or more radio resources) associated with a transmission over one or more radio resources may be configured with a UL BWP.

[0218] FIG. 22 illustrates an example of one or more radio resources in one or more BWPs. The one or more BWPs may include one or more DL BWPs and / or one or more UL BWPs (e.g., DL The initial BWP 2201 may include a broadcast message and / or a wireless device specific RRC message including a configuration parameter for the initial BWP 2201 (e.g., an initial DL BWP and / or an initial UL BWP). The wireless device may receive one or more messages (e.g., a broadcast message and / or a wireless device specific RRC message) including configuration parameters for the initial BWP 2201 (e.g., an initial DL BWP and / or an initial UL BWP). The initial BWP 2201 may be used / indicated / configured for cell search and / or initial / random access. The wireless device may receive an SSB (e.g., a cell-defined SSB) via the initial DL BWP. The wireless device may perform a random access procedure via the initial BWP. The wireless device may transmit Msg1, Msg3, and / or Msg A via the initial UL BWP. The wireless device may receive Msg2, Msg4, and / or Msg B via the initial DL BWP. One or more radio resources configured for transmission in the RRC_INACTIVE state (and / or the RRC_IDLE state) may be configured in a BWP different from the initial BWP. The BWP may be: The BWP may be the last BWP 2202 (e.g., the most recent BWP) that the wireless device may have used in the RRC_CONNECTED state (e.g., before switching / transitioning to the RRC_INACTIVE state and / or the RRC_IDLE state). A BWP (e.g., 2002) may be for transmission and / or reception for a wireless device in an RRC_INACTIVE state (and / or an RRC_IDLE state). A BWP (e.g., 2002) may include a BWP for a particular use and / or of a particular type (e.g., type of data, application, size, etc.). A BWP (e.g., 2002) may include an SDT BWP (e.g., a BWP for SDT). A BWP (e.g., 2002) may include an initial BWP 2201 and / or one or more other BWPs. A BWP (e.g., 2002) may include a subset of an initial BWP 2201, such as a BWP for a smaller portion of resources (e.g., SDT resources) relative to the resources of the initial BWP 2201. One or more radio resources for transmission may be configured in the UL BWP of the BWP. A PDCCH and / or a PDSCH may be configured in the DL BWP of the BWP. The wireless device may deactivate the BWP, for example, when the RRC state of the wireless device changes (e.g., to RRC_CONNECTED). One or more radio resources and / or PUCCH associated with transmissions in RRC_INACTIVE (and / or RRC_IDLE) may be configured in the initial UL BWP. PDCCH and / or PDSCH associated with transmissions in RRC_INACTIVE (and / or RRC_IDLE) may be configured in the initial DL BWP. The one or more messages may indicate whether the BWP is configured separately from the initial BWP.

[0219] A wireless device may perform downlink and / or uplink beam management (e.g., with a base station) in an RRC_INACTIVE state (and / or an RRC_IDLE state). Downlink and / or uplink beam management may include downlink and / or uplink beam measurement procedures, configuration and / or reconfiguration of one or more beams, beam activation of one or more beams, and / or beam selection from among one or more beams.

[0220] The indicator of the reference signal in the downlink and / or uplink beam management is The RRC_INACTIVE state (and / or the RRC_IDLE state) may indicate a beam (e.g., a TX beam and / or an RX beam of the wireless device) to use. The wireless device may receive one or more messages (e.g., an RRC message) including configuration parameters for one or more radio resources in the RRC_INACTIVE state (and / or the RRC_IDLE state). The configuration parameters may indicate one or more reference signals. The one or more reference signals may include an SSB indicated / identified by an SSB index / identifier, a CSI-RS indicated / identified by a CSI-RS index / identifier (and / or a CSI-RS resource index / identifier). The one or more reference signals may include an SRS identified by an SRS index / identifier (e.g., an SRS resource index / identifier, an SRS resource set index / identifier, and / or a combination thereof). The reference signals may indicate / indicate a particular beam. The SSB may indicate / indicate a wide beam. The CSI-RS may indicate / indicate a narrow beam. The SRS may represent / indicate the TX beam of the wireless device.

[0221] The configuration parameters in the one or more messages may include indicators indicating which reference signals are associated with which transmissions (e.g., PUSCH, PUCCH, and / or SRS) and / or receptions (e.g., PDCCH and / or PDSCH). The configuration parameters may include indicators indicating which reference signals are associated with data (e.g., PDSCH) and / or control signal (e.g., PDCCH) receptions in RRC_INACTIVE (and / or RRC_IDLE). The data and / or control signals may be associated with transmissions over one or more radio resources in the RRC_INACTIVE state (and / or RRC_IDLE state). The receptions may be for receiving responses to transmissions (e.g., RRC responses over PDSCH and / or L1 ACK / NACK / fallback over PDCCH). The indicator may include / indicate parameters for configuring a QCL relationship between one or more DL reference signals (e.g., SSB and / or CSI-RS) and a DM-RS port of a PDSCH, a DM-RS port of a PDCCH, and / or a CSI-RS port of a CSI-RS resource. The parameters may include one or more TCI states. The one or more TCI states (e.g., each of the one or more TCI states) may include at least one of one or more DL RS (e.g., SSB, CSI-RS, any combination thereof), a cell index / identifier, a BWP index / identifier, and / or a QCL relationship type (e.g., one or more large scale properties). The indicator may include: The TCI state may be a TCI state of a particular channel configuration (e.g., PDSCH, PDCCH (e.g., CORESET)). The PDSCH and / or PDCCH (e.g., CORESET) configuration may include at least one of one or more TCI states. The TCI state of the PDSCH may indicate a QCL relationship between one or more DL reference signals (e.g., SSB and / or CSI-RS) and the DM-RS port of the PDSCH. The wireless device may determine an RX beam used to receive data via the PDSCH based on the TCI state (e.g., the QCL relationship of the TCI state). The TCI state of the PDCCH may indicate a QCL relationship between one or more DL reference signals (e.g., SSB and / or CSI-RS) and the DM-RS port of the PDCCH. The wireless device may determine an RX beam used to receive control signals via the PDCCH based on the TCI state (e.g., the QCL relationship of the TCI state).

[0222] The wireless device may receive one or more messages that configure, reconfigure, update, and / or activate a TCI state (e.g., CORESET) of the PDSCH and / or PDCCH. A first control message (e.g., an RRC message) that the wireless device may receive may indicate at least one TCI state (e.g., CORESET) used for the PDSCH and / or PDCCH. First Control Message That the Wireless Device May Receive A first control message (e.g., an RRC message) that the wireless device may receive may indicate one or more TCI states. A second control message (e.g., another RRC message, DCI, and / or MAC CE) that the wireless device may receive may indicate at least one of one or more TCI states (e.g., CORESET) used for the PDSCH and / or PDCCH. A first control message (e.g., an RRC message) that the wireless device may receive may indicate one or more TCI states. A second control message (e.g., an RRC message, MAC CE, and / or DCI) that the wireless device may receive may indicate (and / or activate) at least a first of the one or more TCI states. A third control message (e.g., an RRC message, MAC CE, and / or DCI) that the wireless device may receive may indicate (and / or activate) at least a first of the one or more TCI states. The TCI state may indicate at least a second one of at least a first one of one or more TCI states (eg, CORESET) used for the PDSCH and / or PDCCH.

[0223] The wireless device may receive configuration parameters that include indicators indicating which reference signals are associated with data (e.g., PUSCH) and / or control signal (e.g., PUCCH) transmissions associated with transmissions over one or more radio resources. The indicators may include: The spatial relationship information may include spatial relationship information. The spatial relationship information may be for transmission via PUSCH, PUCCH, and / or SRS. The wireless device may determine (e.g., identify / indicate) the particular spatial relationship information based on an index and / or identifier of the particular spatial relationship information. The spatial relationship information may indicate at least one of a cell index / identifier, one or more DL RS (e.g., SSB, CSI-RS, and / or any combination thereof), an SRS resource index / identifier, a BWP index / identifier, a path loss reference RS index / identifier, and / or a power control parameter. The wireless device may determine an antenna port and / or a precoder to be used for transmission via PUSCH and / or PUCCH based on the spatial relationship information.

[0224] The indicator may include spatial relationship information of a particular channel configuration (e.g., srs-spatial-relation-information for PUSCH and / or pucch-spatial-relation-information for PUCCH). The PUSCH configuration may include at least one spatial relationship information. The PUCCH configuration may include at least one spatial relationship information. The spatial relationship information of the PUSCH may be different from that of the PUCCH. The spatial relationship information of the PUSCH may be the same as that of the PUCCH. The spatial relationship information of the PUSCH and PUCCH may be configured separately and / or independently. There may be one or more spatial relationship information that applies to (and / or is used for) the PUSCH and the PUCCH.

[0225] The wireless device may determine an antenna port and / or a precoder to be used for the PUSCH based on the spatial relationship information of the PUSCH. The wireless device may receive one or more messages including configuration parameters for transmission over one or more radio resources in an RRC_INACTIVE state (and / or an RRC_IDLE state). The configuration parameters The SRS resource indicator (e.g., an SRS resource indicator) may indicate an SRS resource of an SRS resource set. The SRS resource may include spatial relationship information. The wireless device may determine to use the same antenna port as the SRS port of the SRS resource for transmission over one or more radio resources. Based on the determination, the wireless device may transmit / transmit data over the one or more radio resources using the same antenna port.

[0226] The wireless device may determine one or more antenna ports and / or precoders to be used for the PUCCH based on the spatial relationship information of the PUCCH. The wireless device may receive one or more messages including configuration parameters for the PUCCH in an RRC_INACTIVE state (and / or an RRC_IDLE state). The wireless device may transmit / transmit uplink control signals via the PUCCH for HARQ feedback (e.g., ACK or NACK) to the PDSCH in an RRC_INACTIVE state (and / or an RRC_IDLE state) for SR transmission and / or measurement reporting. The configuration parameters (e.g., PUCCH spatial relationship information) may determine the spatial configuration (e.g., The wireless device may determine a spatial domain filter to be used for reception of the DL RS indicated by the spatial relationship information for a PUCCH transmission in the RRC_INACTIVE state (and / or the RRC_IDLE state). For example, if the spatial relationship information for the PUCCH includes an SSB index / identifier of the SSB, the wireless device may: The wireless device may transmit / transmit the PUCCH using the same spatial domain filter as for reception of SSB for the cell. The wireless device may transmit / transmit the PUCCH using the same spatial domain filter as for reception of CSI-RS for the cell, e.g., if the spatial relationship information for the PUCCH includes a CSI-RS index / identifier of CSI-RS (e.g., NZP-CSI-RS resource index / identifier). The wireless device may transmit / transmit the PUCCH using the same spatial domain filter as for transmission of SRS for the cell and / or UL BWP, e.g., if the spatial relationship information for the PUCCH includes an SRS index / identifier of SRS (e.g., SRS resource).

[0227] The wireless device configures spatial relationship information for the PUSCH, the PUCCH, and / or the SRS; A wireless device may receive one or more control messages that may reconfigure, update, and / or activate a PUSCH, PUCCH, and / or SRS. A first control message (e.g., an RRC message) that the wireless device may receive may indicate at least one of spatial relationship information used for PUSCH, PUCCH, and / or SRS. A first control message (e.g., an RRC message) that the wireless device may receive may indicate one or more of spatial relationship information. A second control message (e.g., another RRC message, DCI, and / or MAC CE) that the wireless device may receive may indicate at least one of the one or more of spatial relationship information used for PUSCH, PUCCH, and / or SRS. A first control message (e.g., an RRC message) that the wireless device may receive may indicate one or more of spatial relationship information. A second control message (e.g., an RRC message, MAC CE, and / or DCI) that the wireless device may receive may indicate (and / or activate) at least a first of the one or more of spatial relationship information. A third control message (e.g., an RRC message, a MAC CE, and / or a DCI) that the wireless device may receive may indicate at least a second of at least a first of the one or more spatial relationship information used for the PUSCH, the PUCCH, and / or the SRS.

[0228] 23 illustrates an example of beam management, which may include beam management for transmission and / or reception in an RRC_INACTIVE state (and / or an RRC_IDLE state). The RRC_INACTIVE (and / or RRC_IDLE) state may receive one or more messages 2303 comprising one or more configuration parameters for transmission / reception in the RRC_INACTIVE (and / or RRC_IDLE state). The one or more configuration parameters may indicate a configuration of radio resources for PUSCH, PDCCH, PDSCH and / or PUCCH to be used in the RRC_INACTIVE (and / or RRC_IDLE) state. The one or more configuration parameters may indicate one or more radio resources for uplink transmission (e.g., via PUSCH) in RRC_INACTIVE (and / or RRC_IDLE). The configuration parameters may indicate which beam (e.g., reference signal) is used for transmission / transmission (e.g., via PUSCH and / or PUCCH) or for reception (e.g., via PDSCH and / or PDCCH). At 2304, the wireless device 2302 may transmit / transmit data over one or more radio resources in an RRC_INACTIVE state (and / or an RRC_IDLE state) using the first beam. The wireless device 2302 may start monitoring a PDCCH (e.g., after 2304) using a third beam. At 2305, the wireless device 2302 may receive a DCI including a downlink assignment of a PDSCH over a PDCCH. At 2306, the wireless device 2302 may receive a PDSCH using a fourth beam. At 2307, the wireless device may transmit / transmit HARQ feedback (e.g., an ACK or NACK) over a PUCCH using the second beam. The base station 2301 may receive and / or transmit data using different beams and / or the same beam, e.g., a first beam for PUSCH reception, a second beam for PDCCH transmission, a third beam for PDSCH transmission, and / or a fourth beam for PUCCH reception. The wireless device 2302 may receive one or more second messages (e.g., RRC messages, MAC CE, DCI, and / or combinations thereof) that may reconfigure, change, activate / deactivate, and / or update the beam configuration of the PUSCH, PDCCH, PDSCH, and / or PUCCH.

[0229] The wireless device may perform one or more procedures in the RRC_INACTIVE state (and / or the RRC_IDLE state). The wireless device may perform a system information (SI) acquisition procedure, a cell selection and / or reselection procedure, a paging message reception, and / or a data transmission via one or more radio resources in RRC_INACTIVE (and / or RRC_IDLE). The wireless device may receive AS, NAS, and / or positioning assistance data information via the SI acquisition procedure. The wireless device (e.g., in RRC_IDLE and / or RRC_INACTIVE) may determine whether a valid version of (at least) the MIB and / or one or more SIBs (e.g., SIB1-SIB4, SIB5, and / or SIB11) is based on the SI acquisition procedure. The wireless device may initiate (and / or perform) an SI acquisition procedure based on cell selection (e.g., upon power-on), cell reselection, returning from out-of-coverage, after reconfiguration due to synchronization completion, after entering the network from another RAT, after / upon receipt of an indication that system information has changed (e.g., an indication in a short message received at a paging occasion), after / upon receipt of a Public Warning System (PWS) notification, after / upon receipt of a positioning request from higher layers, and / or if the wireless device does not have a valid version of the stored SIB.

[0230] By performing one or more procedures, the wireless device may receive cell configuration parameters of the cell (e.g., in a MIB and / or a SIB). The cell configuration parameters may indicate one or more radio resources for transmission in RRC_INACTIVE state (and / or RRC_IDLE state) that are configured for the wireless device. The wireless device may receive the MIB and / or a SIB (e.g., SIB1 and / or any SIB broadcast / multicast / unicast), for example, in an SI acquisition procedure. The MIB and / or SIB may indicate cell configuration parameters of the cell (e.g., numerology, UL / DL BWP configuration, transmitted SSBs, and / or random access configuration parameters). The values ​​of the cell configuration parameters may be the same as the values ​​that the wireless device may receive within a reference time. The reference time may be a time at which the wireless device may receive parameters (e.g., UL grants, periodicity, power control parameters, beam indicators, etc.) associated with one or more radio resources for transmission in RRC_INACTIVE (and / or RRC_IDLE). The reference time may be the time when the wireless device switches / transitions its RRC state from RRC_CONNECTED to RRC_INACTIVE (and / or RRC IDLE) and / or the time when the wireless device may receive an RRC release message. The reference time may be the time when the wireless device transmits / transmits data over one or more radio resources. The reference time may be the time when the wireless device performs the last SI acquisition procedure. One or more values ​​of cell configuration parameters of the cell may differ from values ​​received by the wireless device within the reference time.

[0231] FIG. 24 illustrates an example of changing one or more cell configuration parameters. Changing cell configuration parameters for a cell and / or wireless device in RRC_INACTIVE state (and / or RRC_IDLE state). Wireless device 2402 may receive one or more configuration parameters of one or more radio resources in RRC_INACTIVE state (and / or RRC_IDLE state) from base station 2401. The configuration parameters may include an indicator (e.g., TCI state and / or spatial relationship information) indicating which RS (e.g., SSB, CSI-RS, and / or SRS) is used to transmit and / or receive data (and / or control signals) in RRC_INACTIVE state (and / or RRC_IDLE state). The indicator may indicate that wireless device 2404 transmits / transmits data via one or more radio resources (e.g., 2404) based on an RS (e.g., RS4). The RS (e.g., RS4) may be an SSB and / or a CSI-RS. The wireless device 2402 may determine that the base station 2401 may transmit / transmit four RSs and / or any other amount of RSs (e.g., RS1, RS2, RS3, and RS4), for example, if the wireless device receives configuration parameters. The RSs (e.g., four RSs) may include candidate RSs (e.g., 2403) that the base station 2401 may transmit / transmit. The wireless device 2402 may determine the number / amount of candidate RSs based at least on a numerology (e.g., subcarrier spacing). The number / amount of candidate RSs may be predefined per numerology (e.g., subcarrier spacing). During a time period when the wireless device is in an RRC_INACTIVE state (and / or in an R...

Claims

1. 1. A method comprising: receiving, by a wireless device in a radio resource control (RRC) connected state, a radio resource control (RRC) release message, the RRC release message comprising: transitioning the wireless device from the RRC connected state to an RRC inactive state; a configured uplink grant for transmitting uplink data in the RRC inactive state; and receiving at least one synchronization signal block (SSB) of a plurality of SSBs, the at least one SSB indicating at least one SSB associated with the configured uplink grant; transitioning to the RRC inactive state based on the RRC release message; and transmitting uplink data via the configured uplink grant in the RRC inactive state based on the at least one SSB being associated with the configured uplink grant.

2. The method of claim 1 , wherein the configured uplink grant comprises a configured grant for a small data transmission.

3. The method of claim 1 or 2, wherein transmitting the uplink data comprises transmitting a small data transmission.

4. The method according to any one of claims 1 to 3, wherein the RRC release message indicates that the at least one SSB of the plurality of SSBs is associated with the configured uplink grant based on spatial relationship information.

5. The method according to any one of claims 1 to 4, wherein the plurality of SSBs includes a synchronization signal and a PBCH block.

6. The method according to any one of claims 1 to 5, wherein the RRC release message is a radio device specific message for the radio device.

7. The method according to any one of claims 1 to 6, wherein the RRC release message indicates release of an RRC connection.

8. The method according to any one of claims 1 to 7, wherein the RRC release message indicates a bandwidth portion of a cell, and the configured uplink grant is configured in said bandwidth portion.

9. The bandwidth portion is an initial bandwidth portion of the cell; or 9. The method of claim 8, further comprising at least one of: a small data transmission bandwidth portion;

10. The method according to claim 8 or 9, wherein the bandwidth portion is a bandwidth portion used for receiving the RRC release message.

11. based on receiving, by the wireless device in the RRC inactive state, a broadcast message indicating a change in at least one cell configuration parameter; Revoke a second configured uplink grant for transmission of uplink data in the RRC inactive state. The method of claim 10 further comprising:

12. The method of claim 11 , wherein the change comprises the absence of at least one of the plurality of SSBs associated with the configured uplink grant.

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

14. 1. A system comprising: A wireless device configured to perform the method according to any one of claims 1 to 12; a base station configured to transmit the RRC release message.

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

Images