Resource Configuration for Non-Connected State

Abstract

Data may be communicated during the connected state of the wireless device using the configured resources. The wireless device may transition to an unconnected state (e.g., an inactive state, an idle state, a radio resource control (RRC)_INACTIVE state, and / or an RRC_IDLE state). A release message for transitioning the wireless device from the connected state may indicate at least one resource to use to enable the wireless device to transmit and / or receive data in the unconnected state. The at least one resource may be different from the resource used in the connected state.

Description

Technical Field

[0001] (Cross - Reference to Related Applications) This application claims the benefit of U.S. Provisional Patent Application No. 63 / 061,750, filed on August 05, 2020. The above - referenced application is hereby incorporated by reference in its entirety into this specification.

Background Art

[0002] Wireless devices typically transmit and receive data while in a connected state (e.g., radio resource control (RRC) connected state). Wireless devices typically do not transmit or receive data while in a non - active state (e.g., RRC non - active state) or an idle state (e.g., RRC idle state).

Summary of the Invention

[0003] In the following summary, a simplified overview of certain features is presented. This summary is not an extensive overview and is not intended to identify key or important elements.

[0004] The base station may configure resources for use by a wireless device during a connected state (e.g., RRC connected state). Data may be communicated during the connected state of the wireless device using the configured resources including resources associated with beams and / or reference signals. The wireless device may transition to a non-connected state (e.g., non-active state, idle state, RRC_INACTIVE state, and / or RRC_IDLE state) if, for example, 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 non-active state and / or idle state may indicate resource information that the wireless device may use to transmit and / or receive data in the non-active state and / or idle state. By including such information in the release message, the wireless device may be able to transmit and / or receive data such as small data transmissions (e.g., instant messaging, push notifications, sensor data, etc.) during the non-active state and / or idle state without the need to return to the connected state. Resources including beams and / or reference signals used during the connected state may, for example, not be suitable / efficient / effective / optimal / operable / etc. after the wireless device has transitioned to the non-connected state. The information in the release message may include resource information associated with other resources so that the wireless device may transmit and / or receive data using more suitable beams and / or resources, which may provide advantages such as reduced communication failures, reduced signaling overhead, reduced power consumption, and / or reduced latency.

[0005] These and other features and advantages will be described in more detail below.

Brief Description of the Drawings

[0006] Some features are shown in the accompanying drawings by way of example, and not as a limitation. In the drawings, like numerals refer to like elements.

Figure 1A

Figure 1B

Figure 2A

Figure 2B

Figure 3

Figure 4A

Figure 4B

Figure 5A

Figure 5B

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10A

Figure 10B

Figure 11A

Figure 11B

Figure 12A

Figure 12B

Figure 13A

Figure 13B

Figure 13C

Figure 14A

Figure 14B

Figure 15A

Figure 15B

Figure 16A

Figure 16B

Figure 16C

Figure 16D

Figure 17

Figure 18A

Figure 18B

Figure 19

Figure 20

Figure 21A

Figure 21B

Figure 22

Figure 23

Figure 24

Figure 25

Figure 26

Figure 27

Figure 28A

Figure 28B

Figure 29

Figure 30

Mode for Carrying Out the Invention

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

[0008] FIG. 1A shows 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 / administered / operated by a network operator. The communication network 100 may include one or more of a core network (CN) 102, a radio access network (RAN) 104, and / or a wireless device 106. The communication network 100 may include one or more data networks (DN) 108, and / or devices within the communication network 100 may communicate with (e.g., 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 operator-internal 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 one or more interfaces for the wireless device 106 to one or more DNs 108. As part of the interface function, the CN 102 may perform operations such as setting up an end-to-end connection between the wireless device 106 and one or more DNs 108, authenticating the wireless device 106, and providing / configuring a charging function.

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

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

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

[0012] A base station (e.g., in RAN104) may comprise one or more sets of antennas for wireless communication (e.g., via an air interface) with the wireless device 106. One or more base stations may each comprise a set of antennas (e.g., 3 sets or any other number of sets) for controlling a plurality of cells or sectors (e.g., 3 cells, 3 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 properly receive transmissions from a transmitter (e.g., a wireless device transmitter) operating within the cell. One or more cells of a base station (e.g., alone or in combination with other cells) may provide / configure wireless coverage to the wireless device 106 over a wide geographical area to support movement of the wireless device. A base station comprising 3 sectors (e.g., or n sectors, where n refers to any number n) may be referred to as a 3-sector site (e.g., or n-sector site) or a 3-sector base station (e.g., n-sector base station).

[0013] One or more base stations (e.g., in RAN104) may be implemented as a sectored site having more or less than 3 sectors. One or more base stations of RAN104 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 device / unit coupled to the RRH may be part of a centralized or cloud RAN architecture, for example, where the baseband processing device / unit can be centralized in a pool of baseband processing devices / units or can be virtualized. A repeater node may amplify and transmit (e.g., transmit, retransmit, rebroadcast, etc.) a wireless signal received from a donor node. A relay node may perform substantially the same / similar functions as a repeater node. A relay node may decode a wireless signal received from a donor node, for example, to remove noise before amplifying and transmitting the wireless signal.

[0014] RAN104 can be deployed as a homogeneous network of base stations (e.g., macrocell base stations) having similar antenna patterns and / or similar high-level transmission powers. RAN104 can 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 can be used to provide / configure a small coverage area, e.g., a coverage area that overlaps with a relatively large coverage area provided / configured by other base stations (e.g., macrocell base stations). The small coverage area can be provided / configured in an area having high data traffic (or so-called “hot spot”) or an area having weak macrocell coverage. Examples of small cell base stations can include, in decreasing order of coverage area, microcell base stations, picocell base stations, and femtocell base stations or home base stations.

[0015] The examples described in this specification can be used in various types of communications. For example, the communication can be by the Third-Generation Partnership Project (3GPP (registered trademark)) (e.g., one or more network elements similar to the network elements of the communication 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 can generate specifications for further generations of communication networks (e.g., 6G and / or any other generation of communication networks). The examples can be described in relation to one or more elements (e.g., RAN) of a 3GPP 5G network called next-generation RAN (NG-RAN), or any other communication network such as a 3GPP network and / or a non-3GPP network. The examples described herein can be applicable to other communication networks such as 3G and / or 4G networks, and communication networks that have not yet been finalized / specified (e.g., 3GPP 6G network), satellite communication networks, and / or any other communication network. NG-RAN can be provisioned to implement and update the 5G radio access technology called NR, and to implement other radio access technologies such as 4G radio access technology and / or other 3GPP and / or non-3GPP radio access technologies.

[0016] Figure 1B shows 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 / administered / executed by a network operator. The communication network 150 may comprise one or more of a CN 152 (e.g., a 5G core network (5G-CN)), a RAN 154 (e.g., an NG-RAN), and / or wireless devices 156A and 156B (collectively wireless devices 156). The communication network 150 may include one or more data networks (DN) 170, and / or devices within the communication network 150 may communicate with one or more DNs 170 (e.g., via the CN 152). These components may be implemented and operate in substantially the same or similar manner as the corresponding components described with respect to Figure 1A.

[0017] The CN 152 (e.g., 5G-CN) may provide / configure one or more interfaces to one or more DNs 170, such as a public DN (e.g., the Internet), a private DN, and / or an operator-internal DN, to the wireless device 156. As part of the interface function, the CN 152 (e.g., 5G-CN) may set up an end-to-end connection between the wireless device 156 and one or more DNs, authenticate the wireless device 156, and / or provide / configure a charging function. The CN 152 (e.g., 5G-CN) may have a service-based architecture that may be different from other CNs (e.g., 3GPP 4G CN, 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 an interface 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] CN152 (e.g., 5G-CN) may include an Access and Mobility Management Function (AMF) device 158A and / or a User Plane Function (UPF) device 158B, which may be separate components or a single component AMF / UPF device 158. The UPF device 158B may function 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 for supporting routing of traffic flows to one or more DNs 170, quality of service (QoS) handling for the user plane (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink traffic verification), downlink packet buffering, and / or downlink data notification triggering. The UPF device 158B may function as an anchor point for radio access technology (RAT) mobility within / across radio access technologies, an external protocol (or packet) data unit (PDU) session point for interconnecting to one or more DNs, and / or a branching point for supporting a multi-home PDU session. The wireless device 156 may be configured to receive services via a PDU session, which may be a logical connection between the wireless device and the DN.

[0019] The AMF device 158A can perform functions such as non-access stratum (NAS) signaling termination, NAS signaling security, access stratum (AS) security control, CN-to-CN node signaling for mobility between access networks (e.g., 3GPP access network and / or non-3GPP network), idle mode radio device reachability (e.g., idle mode UE reachability for control and execution of paging retransmission), registration area management, in-system and inter-system mobility support, access authentication, access authorization including roaming right check, mobility management control (e.g., subscription and policy), network slicing support, and / or session management function (SMF) selection. NAS can refer to functions operating between the CN and the radio device, and AS can refer to functions operating between the radio device and the RAN.

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

[0021] RAN 154 (e.g., NG-RAN) may communicate with a wireless device 156 via a 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 types of base stations (e.g., gNBs including gNB 160A and gNB 160B, collectively gNB 160) and / or one or more second types of 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. The base stations (e.g., gNB 160 and ng-eNB 162) may comprise one or more sets of antennas for wirelessly communicating (e.g., via an air interface) with the wireless device 156. One or more base stations (e.g., gNB 160 and / or ng-eNB 162) may include multiple sets of antennas for respectively controlling multiple cells (or sectors). The cells of the base stations (e.g., gNB 160 and ng-eNB 162) may provide wireless coverage to the wireless device 156 over a wide geographic area to support wireless device mobility.

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

[0023] One or more base stations (e.g., gNB 160 and / or ng-eNB 162) can communicate with one or more AMF / UPF devices, such as AMF / UPF 158, via one or more interfaces (e.g., the NG interface). A base station (e.g., gNB 160A) can communicate with the UPF 158B of AMF / UPF 158 via the NG user plane (NG-U) interface and / or be connected to the UPF 158B. The NG-U interface can provide / perform the delivery (e.g., unguaranteed 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) can communicate with an AMF device (e.g., AMF 158A) via the NG control plane (NG-C) interface and / or be connected to the AMF device. The NG-C interface can provide / perform, for example, NG interface management, radio device context management (e.g., UE context management), radio device mobility management (e.g., UE mobility management), NAS message transfer, paging, PDU session management, configuration transfer, and / or warning message transmission.

[0024] The wireless device can access the base station via an interface (e.g., the Uu interface) for user plane configuration and control plane configuration. The base station (e.g., gNB160) can provide user plane and control plane protocol terminations towards the wireless device 156 via the Uu interface. The base station (e.g., gNB160A) can provide user plane and control plane protocol terminations towards the wireless device 156A via the Uu interface associated with the first protocol stack. The base station (e.g., ng-eNB162) can provide Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminations to the wireless device 156 via the Uu interface (e.g., E-UTRA can refer to the 3GPP 4G radio access technology). The base station (e.g., ng-eNB162B) can provide UTRA user plane and control plane protocol terminations towards the wireless device 156B via the Uu interface associated with the second protocol stack. The user plane and control plane protocol terminations can include, for example, NR user plane and control plane protocol terminations, 4G user plane and control plane protocol terminations, etc.

[0025] CN152 (e.g., 5G-CN) can be configured to handle one or more radio accesses (e.g., NR, 4G, and / or any other radio access). It is also 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 non-standalone mode (e.g., non-standalone operation). In non-standalone mode / operation, the 4G core network can be used to provide (or at least support) control plane functions (e.g., initial access, mobility, and / or paging). Although only one AMF / UPF 158 is shown in Figure 1B, one or more base stations (e.g., one or more gNBs and / or one or more ng-eNBs) can be connected to multiple AMF / UPF nodes, for example, to provide redundancy and / or to perform load sharing across multiple AMF / UPF nodes.

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

[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., UE). Although one or more of the above types of devices may be referred to herein (e.g., UE, wireless device, computing device, 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). The apparatuses, systems, and / or methods described herein may generally be described as being implemented in one or more devices (e.g., wireless devices, base stations, eNB, gNB, computing devices, etc.) within one or more networks, but it can be understood that one or more features and steps may be implemented in any device and / or any network.

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

[0029] The user plane configuration (e.g., the NR user plane protocol stack) may include a plurality of 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, the physical layers (PHY) 211 and 221 may provide a transport service to the upper 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 media access control layer (MAC) 212, a radio link control layer (RLC) 213, a packet data convergence protocol layer (PDCP) 214, and / or a service data application protocol layer (SDAP) 215. The protocol layers above the PHY 221 may include a media access control layer (MAC) 222, a radio link control layer (RLC) 223, a packet data convergence protocol layer (PDCP) 224, and / or a service data application protocol layer (SDAP) 225. One or more of the four protocol layers above the PHY 211 may correspond to layer 2 or the data link layer of the OSI model. One or more of the four protocol layers above the PHY 221 may correspond to layer 2 or the data link layer of the OSI model.

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

[0031] PDCP (e.g., PDCP 214 and 224 shown in FIGS. 2A and 3) may perform 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). PDCP 214 and 224 may perform retransmission of undelivered packets, sequential delivery and packet reordering, and / or removal of duplicate received packets, due to, for example, handover (e.g., handover within a gNB). PDCP 214 and 224 may perform packet duplication, for example, to improve the likelihood that a packet is received. A receiver may receive packets in duplicate and remove the duplicate packets. Packet duplication may be useful for certain services such as services that require high reliability.

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

[0033] The RLC layer (e.g., RLC 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 not depend on numerology and / or Transmission Time Interval (TTI) duration (or other duration). The RLC layer (e.g., RLC 213 and 223) may provide / configure the RLC channel as a service to the PDCP layer (e.g., PDCP 214 and 224 respectively), as shown in FIG. 3.

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

[0035] The PHY layer (e.g., PHY 211 and 221) may perform mapping of transport channels to physical channels and / or digital and analog signal processing functions to transmit and / or receive information (e.g., via 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., PHY 211 and 221) may perform multi-antenna mapping. The PHY layer (e.g., PHY 211 and 221) may provide / configure one or more transport channels (e.g., transport channel 350) as a service to the MAC layer (e.g., MAC 212 and 222 respectively).

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

[0037] The downlink data flow may start, for example, when SDAP 225 receives three IP packets (or another number of IP packets) from one or more QoS flows and maps the three packets (or another number of packets) to radio bearers (e.g., radio bearers 402 and 404). SDAP 225 may map IP packets n and n + 1 to the first radio bearer 402 and IP packet m to the second radio bearer 404. To generate an SDAP PDU, an SDAP header (labeled "H" in front of each SDAP SDU shown in FIG. 4A) may be added to the IP packet, which may be referred to as a PDCP SDU. A data unit transferred between upper protocol layers may be referred to as a service data unit (SDU) of the lower protocol layer, and a data unit transferred between lower protocol layers may be referred to as a protocol data unit (PDU) of the upper protocol layer. As shown in FIG. 4A, a data unit from SDAP 225 may be an SDU (e.g., a PDCP SDU) of the lower protocol layer PDCP 224 or a PDU (e.g., an SDAP PDU) of SDAP 225.

[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 the corresponding header, and / or transfer each 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 transfer its output (e.g., the PDCP PDU which is an RLC SDU) to RLC 223. RLC 223 may optionally perform segmentation (e.g., as shown for IP packet m in FIG. 4A). RLC 223 may transfer 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 a number of RLC PDUs (MAC SDUs). MAC 222 may attach a MAC subheader to the RLC PDU (MAC SDU) to form a TB. The MAC subheader may be distributed over the MAC PDU (e.g., 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 the LTE configuration). The NR MAC PDU structure may reduce processing time and / or associated latency, for example, when the MAC PDU subheader is calculated before assembling the complete MAC PDU.

[0039] FIG. 4B shows an exemplary format of the MAC subheader within the MAC PDU. The MAC PDU may include a MAC subheader (H) and a MAC SDU. Each of the one or more MAC subheaders may include an SDU length field for indicating the length (e.g., in bytes) of the corresponding MAC SDU; a logical channel identifier (LCID) field for identifying / indicating the logical channel on which the MAC SDU was transmitted to assist the demultiplexing process; a flag (F) field for indicating the size of the SDU length field; and a reserved bit (R) field for future use.

[0040] One or more MAC control elements (CEs) can be added or inserted into the MAC PDU by a MAC layer such as MAC 223 or MAC 222. As shown in Figure 4B, two MAC CEs can be inserted / added in front of two MAC PDUs. The MAC CE can be inserted / added at the beginning of the MAC PDU for downlink transmission (as shown in Figure 4B). One or more MAC CEs can be inserted / added at the end of the MAC PDU for uplink transmission. The MAC CE can be used for bandwidth control signaling. Exemplary MAC CEs 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 duplication detection, channel state information (CSI) reporting, sounding reference signal (SRS) transmission, and preconfigured components); discontinuous reception (DRX)-related MAC CEs; timing advance MAC CEs; and random access-related MAC CEs. The MAC CE can be preceded by a MAC subheader having a format similar to that described for the MAC subheader of the MAC SDU and can be identified by a reserved value in the LCID field indicating the type of control information included in the corresponding MAC CE.

[0041] FIG. 5A shows an exemplary mapping for a downlink channel. The mapping of the uplink channel may include a mapping between channels for the downlink (e.g., logical channels, transport channels, and physical channels). FIG. 5B shows an exemplary mapping for the uplink channel. The mapping of the uplink channel may include a mapping between channels for the uplink (e.g., logical channels, transport channels, and physical channels). Information may be passed through / across channels between the RLC layer, the MAC layer, and the PHY layer of a protocol stack (e.g., an NR protocol stack). Logical channels may be used between the RLC layer and the MAC layer. Logical channels may be classified / indicated as control channels that can carry control and / or configuration information (e.g., in the NR control plane) or as traffic channels that can carry data (e.g., in the NR user plane). Logical channels may be classified / indicated 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 can be defined by the type of information it carries. A set of logical channels (e.g., in an NR configuration) may include one or more channels as described later. The paging control channel (PCCH) may contain / carry one or more paging messages used to page a wireless device whose location is not known to the network at the cell level. The broadcast control channel (BCCH) may contain / carry system information messages in the form of a master information block (MIB) and some system information blocks (SIB). The system information messages may be used by a wireless device to obtain information on how the cell is configured and how it operates within the cell. The common control channel (CCCH) may contain / carry control messages together with random access. The dedicated control channel (DCCH) may contain / carry control messages between a specific wireless device to configure the wireless device using configuration information. The dedicated traffic channel (DTCH) may contain / carry user data between a specific wireless device.

[0043] The transport channel can be used between the MAC layer and the PHY layer. The transport channel can be defined by how the information they carry is transmitted / conveyed (e.g., via the air interface). The set of transport channels (which can be defined by, for example, an NR configuration or any other configuration) can include one or more of the following channels. The paging channel (PCH) can include / carry paging messages generated from the PCCH. The broadcast channel (BCH) can include / carry the MIB from the BCCH. The downlink shared channel (DL-SCH) can include / carry downlink data and signaling messages including the SIB from the BCCH. The uplink shared channel (UL-SCH) can include / carry uplink data and signaling messages. The random access channel (RACH) can provide access to the network for a wireless device without prior scheduling.

[0044] The PHY layer may use physical channels to transfer information between processing levels of the PHY layer. The physical channels 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 the low-level operations of the PHY layer. The PHY layer may provide / transfer the control information to a lower level of the PHY layer via a physical control channel (e.g., referred to as the L1 / L2 control channel). The set of physical channels and physical control channels (which may be defined by an NR configuration or any other configuration) may include one or more of the following channels. The physical broadcast channel (PBCH) may include / carry the MIB from the BCH. The physical downlink shared channel (PDSCH) may include / carry downlink data and signaling messages from the DL-SCH, and paging messages from the PCH. The physical downlink control channel (PDCCH) may include / carry downlink control information (DCI) that may include downlink scheduling commands, uplink scheduling grants, and uplink power control commands. The physical uplink shared channel (PUSCH) may include / carry uplink data and signaling messages from the UL-SCH, and in some cases, uplink control information (UCI), as described below.The physical uplink control channel (PUCCH) can include / carry UCI which may include HARQ acknowledgment, channel quality indicator (CQI), pre-coding matrix indicator (PMI), rank indicator (RI), and scheduling request (SR). For random access, the physical random access channel (PRACH) can be used.

[0045] The physical layer can generate physical signals to support the low-level operations of the physical layer, which can be similar to physical control channels. As shown in FIGS. 5A and 5B, physical layer signals (e.g., which can be defined by an NR configuration or any other configuration) can 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 channel, transport channel, physical channel, etc.) can be used to execute functions related to a control plane protocol stack (e.g., NR control plane protocol stack). FIG. 2B shows an exemplary control plane configuration (e.g., NR control plane protocol stack). As shown in FIG. 2B, the control plane configuration (e.g., NR control plane protocol stack) can use one or more protocol layers (e.g., PHY211 and 221, MAC212 and 222, RLC213 and 223, and PDCP214 and 224) that are substantially the same / similar to an exemplary user plane configuration (e.g., NR user plane protocol stack). The same four protocol layers can include PHY211 and 221, MAC212 and 222, RLC213 and 223, and PDCP214 and 224. The control plane configuration (e.g., NR control plane stack) can have radio resource control (RRC) 216 and 226 and NAS protocol 217 and 237 at the top of the control plane configuration (e.g., NR control plane protocol stack) instead of having, for example, SDAP215 and 225. The control plane configuration can include an AMF230 that includes the NAS protocol 237.

[0047] The NAS protocols 217 and 237 can provide control plane functions between the radio device 210 and the AMF230 (e.g., AMF158A or any other AMF) and / or, more generally, between the radio device 210 and the CN (e.g., CN152 or any other CN). The NAS protocols 217 and 237 can provide control plane functions between the radio device 210 and the AMF230 via signaling messages called NAS messages. There may be no direct path through which NAS messages can be transmitted between the radio device 210 and the AMF230. The NAS messages can be transferred using the AS of the Uu interface and the NG interface. The NAS protocols 217 and 237 can provide control plane functions such as authentication, security, connection setup, mobility management, session management, and / or any other functions.

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

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

[0050] An RRC connection can be established for a wireless device. For example, this can be during the RRC connected state. During the RRC connected state (e.g., within RRC connection 602), the wireless device can have an established RRC context and at least one RRC connection with a base station. The base station can be similar to one of one or more base stations (e.g., one or more base stations of RAN 104 shown in FIG. 1A, one of gNB 160 or ng-eNB 162 shown in FIG. 1B, 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., establishing the RRC connection) can have an RRC context for the wireless device. The RRC context, which can be referred to as a wireless device context (e.g., UE context), can include parameters for communication between the wireless device and the base station. These parameters can include, for example, one or more of AS context; radio link configuration parameters; bearer configuration information (e.g., related to data radio bearers, signaling radio bearers, logical channels, QoS flows, and / or PDU sessions); security information; and / or layer configuration information (e.g., PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information). During the RRC connected state (e.g., RRC connection 602), the mobility of the wireless device can be managed / controlled by the RAN (e.g., RAN 104 or NG RAN 154). The wireless device can 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 can report these measurements to the serving base station (e.g., the base station currently serving the wireless device). The serving base station of the wireless device can, for example, request a handover to a cell of one of the neighboring base stations based on the reported measurements. The RRC state can transition from the RRC connected state (e.g., RRC connection 602) to the RRC idle state (e.g., RRC idle 606) via the connection release procedure 608.The RRC state can transition from an RRC connected state (e.g., RRC connection 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 a wireless device. For example, this may be during the RRC idle state. During the RRC idle state (e.g., RRC idle 606), an RRC context may not be established for the wireless device. During the RRC idle state (e.g., RRC idle 606), the wireless device may not have an RRC connection to a base station. During the 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., each discontinuous reception (DRX) cycle) to monitor paging messages (e.g., paging messages set by the RAN). The mobility of the wireless device may be managed by the wireless device via a cell reselection procedure. The RRC state can transition from an RRC idle state (e.g., RRC idle 606) to an RRC connected state (e.g., RRC connection 602) via a connection establishment procedure 612 that may include a random access procedure.

[0052] For a wireless device, a previously established RRC context can be maintained. For example, this can be during the RRC inactive state. During the RRC inactive state (e.g., RRC inactive 604), the previously established RRC context can be maintained at the wireless device and the base station. Maintaining the RRC context can enable a fast transition to the RRC connected state (e.g., RRC connected 602) with reduced signaling overhead as compared to the transition from the RRC idle state (e.g., RRC idle 606) to the RRC connected state. During the RRC inactive state (e.g., RRC inactive 604), the wireless device can enter a sleep state, and the mobility of the wireless device can be managed / controlled by the wireless device via cell reselection. The RRC state can transition from the RRC inactive state (e.g., RRC inactive 604) to the RRC connected state (e.g., RRC connected 602) via a connection resume procedure 614. The RRC state can transition from the RRC inactive state (e.g., RRC inactive 604) to the RRC idle state (e.g., RRC idle 606) via a connection release procedure 616 that can be the same as or similar to the connection release procedure 608.

[0053] The RRC state can be associated with a mobility management mechanism. Between the RRC idle state (e.g., RRC idle 606) and the RRC inactive state (e.g., RRC inactive 604), mobility can be managed / controlled by the wireless device via cell reselection. The purpose of mobility management between the RRC idle state (e.g., RRC idle 606) or the RRC inactive state (e.g., RRC inactive 604) can be to enable / allow the network to notify the wireless device of an event via a paging message without the need to broadcast the paging message across the entire mobile communication network. The mobility management mechanism used between the RRC idle state (e.g., RRC idle 606) or the RRC idle state (e.g., RRC inactive 604) can enable / allow the network to track the wireless device at the cell group level, for example, such that the paging message can be broadcast via the cells of the cell group in which the wireless device currently resides (instead of sending the paging message across the entire mobile communication network). The mobility management mechanism for the RRC idle state (e.g., RRC idle 606) and the RRC inactive state (e.g., RRC inactive 604) can track the wireless device at the cell group level. The mobility management mechanism can perform the tracking using, for example, different granularities of grouping. There can be multiple levels of cell group granularity (e.g., three levels of cell group granularity, namely, 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 can be used to track a wireless device (e.g., to track the location of the wireless device at the CN level). The CN (e.g., CN102, 5G CN152, or any other CN) can send a list of TAIs associated with a wireless device registration area (e.g., a UE registration area) to the wireless device. The wireless device, for example, when the wireless device moves to a cell associated with a TAI that may not be included in the list of TAIs associated with the UE registration area (e.g., via cell reselection), the CN can perform a registration update in the CN to update the location of the wireless device and enable the CN to provide a new UE registration area to the wireless device.

[0055] The RAN area can be used to track a wireless device (e.g., the location of the wireless device at the RAN level). For a wireless device in the RRC inactive state (e.g., RRC inactive 604), the wireless device can be assigned / provided / configured with a RAN notification area. The RAN notification area can include one or more cell identification information (e.g., a list of RAI and / or a list of TAI). The base station can belong to one or more RAN notification areas. The cell can belong to one or more RAN notification areas. For example, when the wireless device moves to a cell not included in the RAN notification area assigned / provided / configured to the wireless device (e.g., via cell reselection), the wireless device can perform a notification area update in the RAN to update the RAN notification area of the wireless device.

[0056] The base station storing the RRC context of the wireless device, or the last serving base station of the wireless device, can be referred to as an anchor base station. The anchor base station can maintain the RRC context of the wireless device at least during the period when the wireless device stays in the RAN notification area of the anchor base station and / or during the period when the wireless device stays in the RRC inactive state (e.g., RRC inactive 604).

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

[0058] Physical signals and physical channels (e.g., as described with respect to FIGS. 5A and 5B) can be mapped to one or more symbols (e.g., orthogonal frequency divisional multiplexing (OFDM) symbols in an NR configuration or any other symbol). OFDM is a multi-carrier communication scheme that transmits data over F orthogonal sub-carriers (or tones). The data can be mapped, for example, to a series of complex symbols (e.g., M-quadrature amplitude modulation (M-QAM) symbols or M-phase shift keying (M-PSK) symbols or any other modulation symbol), referred to as source symbols, prior to transmission of the data, and can be split into F parallel symbol streams. The F parallel symbol streams can be treated as if they were in the frequency domain. The F parallel symbols can be used as inputs to an Inverse Fast Fourier Transform (IFFT) block that converts them to the time domain. The IFFT block can take in F source symbols, one at a time, from each of the F parallel symbol streams. The IFFT block can modulate the amplitude and phase of one of the F sine basis functions corresponding to the F orthogonal sub-carriers using each source symbol. The output of the IFFT block can be F time domain samples representing the sum of the F orthogonal sub-carriers. The F time domain samples can form a single OFDM symbol. The OFDM symbol provided / output by the IFFT block can be transmitted over the air interface at the carrier frequency, for example, after one or more processes (e.g., addition of a cyclic prefix) and up-conversion. The F parallel symbol streams can be mixed, for example, using a Fast Fourier Transform (FFT) block prior to being processed by the IFFT block.This operation can be used by one or more wireless devices in the uplink to generate discrete Fourier transform (DFT)-precoded OFDM symbols and reduce the peak to average power ratio (PAPR). To recover the data mapped to the source symbols, an inverse process can be performed on the OFDM symbols at the receiver using an FFT block.

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

[0060] The duration of a slot may depend on the numerology used for the OFDM symbol 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 millimeter wave range). Flexible numerology may be supported, for example, in an NR configuration or any other radio configuration. Numerology may be defined with respect to subcarrier spacing and / or cyclic prefix duration. The subcarrier spacing may be scaled up by a power of 2 from a baseline subcarrier spacing of 15 kHz. The cyclic prefix duration may be scaled down by a power of 2 from a baseline cyclic prefix duration of 4.7 μs, for example, for the numerology in an NR configuration or any other radio configuration. Numerology may be defined by the following combinations of subcarrier spacing / cyclic prefix duration, namely, 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 combinations of subcarrier spacing / cyclic prefix duration.

[0061] A slot may have a fixed number / fixed number of OFDM symbols (e.g., 14 OFDM symbols). A numerology with a higher subcarrier spacing may have a shorter slot duration and more slots per subframe. Examples of numerically dependent slot durations and slot transmission structures per subframe are shown in FIG. 7 (a new numerology with a 240 kHz subcarrier spacing is not shown in FIG. 7). A subframe (e.g., in an NR configuration) may be used as a time reference independent of number. A slot may be used as a unit in which uplink transmission and downlink transmission are scheduled. Scheduling (e.g., in an NR configuration) may be separated from the slot duration. Scheduling may start at any OFDM symbol. Scheduling may continue over the number of symbols required for transmission, e.g., to support low latency. These partial slot transmissions may be referred to as mini-slot transmissions or sub-slot transmissions.

[0062] FIG. 8 shows an exemplary resource configuration for one or more carriers. This resource configuration may include slots in the time and frequency domains for an NR carrier or any other carrier. A slot may comprise resource elements (REs) and resource blocks (RBs). A resource element (RE) may be the smallest physical resource (e.g., in an NR configuration). An RE may span, for example, one subcarrier in the frequency domain and one OFDM symbol in the time domain, as shown in FIG. 8. An RB may span, for example, 12 consecutive REs in the frequency domain, as shown in FIG. 8. A carrier (e.g., an NR carrier) may be limited in width to a certain number of RBs and / or subcarriers (e.g., 275 RBs or 275×12 = 3300 subcarriers). When such a limitation is used, the carrier (e.g., an NR carrier) frequency may be limited based on the 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 400 MHz per carrier bandwidth limitation. Any other bandwidth may be set based on the bandwidth limitation per carrier.

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

[0064] The configuration of one or more bandwidth parts (BWPs) can support one or more wireless devices that cannot receive the full carrier bandwidth. A BWP can support, for example, bandwidth adaptation for such wireless devices that cannot receive the full carrier bandwidth. A BWP (e.g., a BWP in an NR configuration) can be defined by a subset of consecutive resource blocks (RBs) on a carrier. A wireless device can be configured 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) (e.g., via the RRC layer). One or more of the BWPs configured for a serving cell can be active, for example, at a given point in time. One or more BWPs can be referred to as the active BWPs of a serving cell. A serving cell can have, for example, one or more first active BWPs on an uplink carrier and one or more second active BWPs on a secondary uplink carrier 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 to an uplink BWP from a set of configured uplink BWPs (e.g., in the case of non-corresponding spectrum). The downlink BWP and the uplink BWP may be linked, for example, when the downlink BWP index of the downlink BWP is the same as the uplink BWP index of the uplink BWP. The wireless device may expect that the center frequency of the downlink BWP is the same as the center frequency of the uplink BWP (e.g., in the case of non-corresponding spectrum).

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

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

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

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

[0070] The base station may configure the wireless device using the BWP inactivity timer value. The wireless device may start or resume the BWP inactivity timer at any suitable time. The wireless device may start or resume the BWP inactivity timer, for example, when one or more conditions are met. The one or more conditions may include at least one of: the wireless device detecting a DCI indicating an active downlink BWP other than the default downlink BWP for paired spectrum operations; the wireless device detecting a DCI indicating an active downlink BWP other than the default downlink BWP for unpaired spectrum operations; and / or the wireless device detecting a DCI indicating an active uplink BWP other than the default uplink BWP for unpaired spectrum operations. For example, if the wireless device does not detect a DCI during a certain time interval (e.g., 1 ms or 0.5 ms), the wireless device may start / run the BWP inactivity timer towards 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 the active downlink BWP to the default downlink BWP, for example, when the BWP inactivity timer expires.

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

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

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

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

[0075] Two or more carriers may be aggregated and data may be transmitted / sent simultaneously between the same wireless device using carrier aggregation (CA) (e.g., to increase the data rate). The aggregated carriers in CA may be referred to as component carriers (CCs). For example, when CA is configured / used, there may be a number / 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] Figure 10A shows an exemplary CA configuration based on CCs. As shown in Figure 10A, three types of CA configurations may include an in-band (continuous) configuration 1002, an in-band (discontinuous) configuration 1004, and / or an inter-band configuration 1006. In the in-band (adjacent) configuration 1002, two CCs may be aggregated in the same frequency band (frequency band A) and may be placed directly adjacent to each other within the frequency band. In the in-band (discontinuous) configuration 1004, two CCs may be aggregated in the same frequency band (frequency band A), but may be separated from each other in the frequency band by a gap. In the inter-band configuration 1006, two CCs may be located in different frequency bands (e.g., frequency band A and frequency band B, respectively).

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

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

[0079] An SCell configured for a wireless device can be activated or deactivated, for example, based on traffic and channel conditions. Deactivation of the SCell can cause the wireless device to stop receiving PDCCH and PDSCH on the SCell, as well as transmitting PUSCH, SRS, and CQI on the SCell. The configured SCell can be activated or deactivated, for example, using a MAC CE (e.g., the MAC CE described with respect to FIG. 4B). The MAC CE can use a bitmap (e.g., 1 bit per SCell) to indicate which SCell(s) of the wireless device (e.g., in a subset of the configured SCell) are activated or deactivated. The configured SCell can be deactivated, for example, after the expiration of an SCell deactivation timer (e.g., based on or in response to the expiration) (e.g., one SCell deactivation timer can be configured per SCell).

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

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

[0082] A PCell may include a downlink carrier (e.g., PCell1011) and an uplink carrier (e.g., PCell1021). An SCell may include only a downlink carrier. A cell including a downlink carrier and optionally an uplink carrier may be assigned a physical cell ID and a cell index. The physical cell ID or cell index may indicate / identify the downlink carrier and / or uplink carrier of the cell, for example, according to the context in which the physical cell ID is used. The physical cell ID may be determined using, for example, a synchronization signal (e.g., PSS and / or SSS) transmitted by a downlink component carrier. The cell index may be determined using, for example, 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 including the first downlink carrier. Substantially the same / similar concepts may be applied, for example, to carrier activation. Activation of the first carrier may refer to activation of the cell including the first carrier.

[0083] The multi-carrier characteristics of the PHY layer can be disclosed / instructed to the MAC layer (e.g., in the CA configuration). The HARQ entity can operate in the serving cell. The transport block can be generated for each allocation / grant per serving cell. The transport block and potential HARQ retransmissions of the transport block can be mapped to the serving cell.

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

[0085] FIG. 11A shows an example of the 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). The burst may be transmitted / transmitted periodically (e.g., every two frames, every 20 ms, or any other duration). The burst may be limited to a half-frame (e.g., the first half-frame having a 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 based on, for example, the carrier frequency of the cell in which the SS / PBCH block is transmitted / transmitted; the numerology or subcarrier spacing of the cell; the configuration by the network (e.g., using RRC signaling); and / or any other suitable factor, among at least one of them. The wireless device may take the subcarrier spacing of the SS / PBCH block based on the monitored carrier frequency, unless, for example, the wireless network configures the wireless device to take different subcarrier spacings.

[0086] The SS / PBCH block may span one or more OFDM symbols in the time domain (e.g., four OFDM symbols or any other number / quantity of symbols as shown in FIG. 11A) and one or more subcarriers in the frequency domain (e.g., 240 consecutive subcarriers, or any other number / quantity of subcarriers). The PSS, SSS, and PBCH may have a common center frequency. The PSS may be transmitted / transmitted first and may span, for example, one OFDM symbol and 127 subcarriers. The SSS may be transmitted / transmitted after the PSS (e.g., after 2 symbols) 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 also 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 positions of the SS / PBCH block in the time domain and the frequency domain may not be known to the wireless device (e.g., when the wireless device is searching for a cell). The wireless device may monitor a carrier for the PSS, for example, to find and select a cell. The wireless device may monitor the frequency position within the carrier. The wireless device may search for the PSS at different frequency positions 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 the PSS at different frequency positions within the carrier as indicated by, for example, a synchronization raster. The wireless device may determine the positions of the SSS and the PBCH respectively based on the known structure of the SS / PBCH block, for example, if the PSS is found at its position in the time domain and the frequency domain. 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 located on the synchronization raster. Cell selection / search and / or reselection may be based on the CD-SSB.

[0088] The SS / PBCH block may be used by the wireless device to determine one or more parameters of the cell. The wireless device may determine the physical cell identifier (PCI) of the cell based on the sequences of the PSS and the SSS respectively, for example. The wireless device may determine the position of the frame boundary of the cell based on the position of the SS / PBCH block, for example. The SS / PBCH block may indicate that it has been transmitted / transmitted according to a transmission pattern. The SS / PBCH block in the transmission pattern may be at a known distance from the frame boundary (e.g., a predefined distance for the 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 covered by the PBCH may include / carry one or more DM-RSs for demodulation of the PBCH. The PBCH may include an indication of the current system frame number (SFN) of the cell and / or the SS / PBCH block timing index. These parameters may facilitate time synchronization of the wireless device to the base station. The PBCH may include the master information block (MIB) used to transmit / transmit one or more parameters to the wireless device. The MIB may be used by the wireless device to find the remaining minimum system information (RMSI) associated with the cell. The RMSI may include the system information block type 1 (SIB1). The SIB1 may include information for the wireless device to access the cell. The wireless device may use one or more parameters of the MIB to monitor the PDCCH, which may be used to schedule the PDSCH. The PDSCH may include the SIB1. The SIB1 may be decoded using the parameters provided / included in the MIB. The PBCH may indicate the absence of the SIB1. The wireless device may indicate a frequency, for example, based on the absence of the SIB1 indicated by the PBCH. The wireless device may search for the SS / PBCH block at the frequency indicated by the wireless device.

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

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

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

[0093] The base station can configure the wireless device quasi-statically using one or more CSI-RS resource sets. The CSI-RS resources can be associated with their positions and periodicities in the time and frequency domains. The base station can selectively activate and / or deactivate the CSI-RS resources. The base station can indicate to the wireless device that the CSI-RS resources within the CSI-RS resource set are activated and / or deactivated.

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

[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, if the downlink CSI - RS and the CORESET are spatially QCLed and the resource elements associated with the downlink CSI - RS are outside the physical resource blocks (PRBs) configured for the CORESET, the wireless device may be configured to use / adopt the same OFDM symbol for the downlink CSI - RS and the CORESET. The wireless device may be configured to use / adopt the same OFDM symbol for the downlink CSI - RS and the SS / PBCH block, for example, if the downlink CSI - RS and the SS / PBCH block are spatially QCLed and the resource elements associated with the downlink CSI - RS are outside the PRBs configured for the SS / PBCH block.

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

[0097] A transmitter (e.g., a base station transmitter) may use a precoder matrix for a part of the transmission bandwidth. The transmitter may use a first precoder matrix for a first bandwidth and a second precoder matrix for a second bandwidth. The first precoder matrix and the second precoder matrix may be different, for example, based on the first bandwidth being different from the second bandwidth. A wireless device may assume that the same precoding matrix is used across a set of PRBs. The set of PRBs may be determined / illustrated / identified / shown 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 DM-RS exists on the layer of one or more layers of the PDSCH. The upper layer may constitute one or more DM-RSs for the PDSCH (for example, up to three DMRSs for the PDSCH). The downlink PT-RS is transmitted / sent by the base station and can be used by the wireless device, for example, for phase noise compensation. Whether the downlink PT-RS exists may depend on the RRC configuration. The existence and / or pattern of the downlink PT-RS can be configured on a wireless device-specific basis using, for example, a combination of RRC signaling and / or other purposes indicated by DCI (for example, modulation and coding scheme (MCS)) in association with one or more parameters used / employed. The dynamic existence of the downlink PT-RS, if configured, can be associated with one or more DCI parameters including at least the MCS. The network (for example, an NR network) may support a plurality of PT-RS densities defined in the time domain and / or frequency domain. The frequency domain density (if configured / existing) can be associated with at least one configuration of the scheduled bandwidth. The wireless device may assume the same precoding for the DM-RS port and the PT-RS port. The number / quantity of PT-RS ports may be less than or equal to the number / quantity of DM-RS ports within the scheduled resources. The downlink PT-RS can be configured / allocated / limited in the scheduled time / frequency duration for the wireless device. The downlink PT-RS can be transmitted / sent via symbols, for example, to facilitate phase tracking in the receiver.

[0099] A wireless device may transmit / send 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 / send the uplink DM-RS on PUSCH and / or PUCCH. The uplink DM-RS may cover a frequency range similar to the frequency range associated with the corresponding physical channel. The base station may configure the wireless device using one or more uplink DM-RS configurations. At least one DM-RS configuration may support a front-loaded DM-RS pattern. The front-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DM-RS may be configured to be transmitted / sent on one or more symbols of PUSCH and / or PUCCH. The base station may quasi-statically configure the wireless device using the number / amount (e.g., maximum number / amount) of front-loaded DM-RS symbols for PUSCH and / or PUCCH, which the wireless device may use for scheduling single-symbol DM-RS and / or double-symbol DM-RS. The network (e.g., an NR network) may support a common DM-RS structure for downlink and uplink (e.g., in the case of cyclic prefix orthogonal frequency division multiplexing (CP-OFDM)). The DM-RS position, DM-RS pattern, and / or DM-RS scrambling sequence may be substantially the same or different.

[0100] The PUSCH may include one or more layers. The wireless device may transmit / send at least one symbol together with the DM-RS present in one or more layers of the PUSCH. The upper layer may configure one or more DM-RSs (e.g., up to three DMRSs) for the PUSCH. The 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, for example, depending on the RRC configuration of the wireless device. The presence and / or pattern of the uplink PT-RS may be configured on a wireless device-specific basis (e.g., UE-specific basis) by a combination of one or more parameters configured / adopted for other purposes (e.g., MCS) indicated, for example, by RRC signaling and / or DCI. The dynamic presence of the uplink PT-RS, if configured, may be associated with one or more DCI parameters including at least the MCS. 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 the DM-RS ports and the PT-RS ports. The number / quantity of PT-RS ports may be less than the number / quantity of DM-RS ports within the scheduled resources. The uplink PT-RS may be configured / allocated / constrained within the scheduled time / frequency duration of the wireless device.

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

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

[0103] Channels that use 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, for example, one or more downlink reference signals (e.g., CSI-RS) and generate a beam measurement report. The wireless device may perform downlink beam measurement procedures, for example, after the RRC connection with the base station is set up.

[0104] Figure 11B shows an exemplary mapping of one or more CSI-RS. The CSI-RS may be mapped in the time domain and the frequency domain. Each rectangular block shown in Figure 11B may correspond to a resource block (RB) within the cell bandwidth. The base station may transmit / send 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 upper 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 CSI-RS resource configuration identification information, the number of CSI-RS ports, CSI-RS configuration (e.g., symbol and resource element (RE) positions within a subframe), CSI-RS subframe configuration (e.g., subframe position, offset, and periodicity in a radio frame), CSI-RS power parameters, CSI-RS sequence parameters, code division multiplexing (CDM) type parameters, frequency density, 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 can be configured for a wireless device with a configuration specific to the wireless device. Although three beams (beam #1, beam #2, and beam #3) are shown in FIG. 11B, more or fewer beams can be configured. For beam #1, CSI-RS 1101 that can be transmitted / retransmitted on one or more subcarriers within the RB of the first symbol can be allocated. For beam #2, CSI-RS 1102 that can be transmitted / retransmitted on one or more subcarriers within the RB of the second symbol can be allocated. For beam #3, CSI-RS 1103 that can be transmitted / retransmitted on one or more subcarriers within the RB of the third symbol can be allocated. The base station can use other subcarriers within the same RB (for example, those not used for transmitting / retransmitting 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 beams used for a wireless device can be configured such that, for example, by using time domain multiplexing (TDM), the beams for the wireless device use symbols different from the symbols used by the beams of other wireless devices. The wireless device can be served with beams of orthogonal symbols (for example, without overlapping symbols), for example, by using TDM.

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

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

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

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

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

[0111] The wireless device may measure the quality of the beam pair link using, for example, one or more reference signals (RSs) comprising one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more DM-RSs. The quality of the beam pair link may be based on one or more of a block error rate (BLER), an RSRP value, a signal to interference plus noise ratio (SINR) value, an RSRQ value, and / or a CSI value measured on the RS resource. The base station may indicate that the RS resource is quasi-co-located (QCL) with one or more DM-RSs of a channel (e.g., control channel, shared data channel, etc.). The RS resource of the channel and one or more DM-RSs may be QCL, 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 via the RS resource are similar or the same as the channel characteristics from a transmission to the wireless device via the channel.

[0112] A network (e.g., an NR network including a gNB and / or an ng-eNB) and / or a wireless device may initiate / start / perform a random access procedure. A wireless device in the RRC idle (e.g., RRC_IDLE) state and / or the 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 / start / perform a random access procedure from the RRC connected (e.g., RRC_CONNECTED) state. A wireless device may initiate / start / perform a random access procedure to request uplink resources (e.g., for SR uplink transmission when there are no available PUCCH resources) and / or to acquire / obtain / determine uplink timing (e.g., when the uplink synchronization status is asynchronous). A wireless device may initiate / start / perform a random access procedure to request one or more system information blocks (SIBs) (e.g., other system information blocks such as SIB2, SIB3). A wireless device may initiate / start / perform a random access procedure for 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 shows an exemplary 4-step random access procedure. The 4-step random access procedure may include a 4-step contention-based random access procedure. The base station may transmit / send a configuration message 1310 to the wireless device, for example, before starting the random access procedure. The 4-step random access procedure may include the transmission of four messages including a first message (e.g., Msg 1 1311), a second message (e.g., Msg 2 1312), a third message (e.g., Msg 3 1313), and a fourth message (e.g., Msg 4 1314). The first message (e.g., Msg 1 1311) may include a preamble (or a random access preamble). The first message (e.g., Msg 1 1311) may be referred to as a preamble. The second message (e.g., Msg 2 1312) may include a random access response (RAR). The second message (e.g., Msg 2 1312) may be referred to as an RAR.

[0114] The constituent message 1310 can be transmitted / sent, for example, using one or more RRC messages. The one or more RRC messages can indicate one or more random access channel (RACH) parameters to the wireless device. The one or more RACH parameters can include 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 can transmit / send (e.g., broadcast or multicast) the one or more RRC messages to one or more wireless devices. The one or more RRC messages can be device-specific. The one or more device-specific RRC messages can be, for example, dedicated RRC messages transmitted / sent to the wireless device in the RRC connected (e.g., RRC_CONNECTED) state and / or the RRC inactive (e.g., RRC_INACTIVE) state. The wireless device can determine time-frequency resources and / or uplink transmission power for the transmission of the first message (e.g., Msg 1 1311) and / or the third message (e.g., Msg 3 1313) based on the one or more RACH parameters. The wireless device can determine reception timing and a downlink channel for receiving the second message (e.g., Msg 2 1312) and the fourth message (e.g., Msg 4 1314) based on, for example, the one or more RACH parameters.

[0115] One or more RACH parameters provided / configured / included in the constitution message 1310 may indicate one or more physical RACH (PRACH) opportunities available for the transmission of the first message (e.g., Msg 1 1311). One or more PRACH opportunities may be predefined (e.g., by a network comprising one or more base stations). One or more RACH parameters may indicate one or more available sets among one or more PRACH opportunities (e.g., prach-ConfigIndex). One or more RACH parameters may indicate the association between (a) one or more PRACH opportunities and (b) one or more reference signals. One or more RACH parameters may indicate the association between (a) one or more preambles and (b) one or more reference signals. One or more reference signals may be SS / PBCH blocks and / or CSI-RS. One or more RACH parameters may indicate the number / quantity of SS / PBCH blocks mapped to the PRACH opportunity and / or the number / quantity of preambles mapped to the SS / PBCH block.

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

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

[0118] A wireless device may determine a preamble based on, for example, one or more RACH parameters provided / configured / included in a configuration message 1310. The wireless device may determine a preamble based on, for example, a path loss measurement value, an RSRP measurement value, and / or the size of a third message (e.g., Msg 3 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., Group A and Group B). The base station may use the one or more RACH parameters to configure the wireless device using an association between the one or more preambles and one or more reference signals (e.g., SSB and / or CSI-RS). The wireless device may determine a preamble included in a first message (e.g., Msg 1 1311) based on the association, for example, if the association is configured. The first message (e.g., Msg 1 1311) may be transmitted / sent 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 (e.g., ra-ssb-OccasionMskIndex and / or ra-Occasion list) may indicate an association between a PRACH opportunity and one or more reference signals.

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

[0120] The second message (e.g., Msg 2 1312) (e.g., received by a wireless device) may comprise a RAR. The second message (e.g., Msg 2 1312) may comprise a plurality of RARs corresponding to a plurality of wireless devices. The second message (e.g., Msg 2 1312) may be received, for example, after (e.g., based on or in response to) transmission of the first message (e.g., Msg 1 1311). The second message (e.g., Msg 2 1312) may be scheduled on the DL-SCH and may be indicated by the PDCCH using, for example, a random access radio network temporary identifier (RA RNTI). The second message (e.g., Msg 2 1312) may indicate that the first message (e.g., Msg 1 1311) has been received by the base station. The second message (e.g., Msg 2 1312) may comprise a timing alignment command used by the wireless device to adjust the transmission timing of the wireless device, a scheduling grant for transmission of a third message (e.g., Msg 3 1313), and / or a Temporary Cell RNTI (TC-RNTI). The wireless device may determine / start a time window (e.g., ra-ResponseWindow) for monitoring the PDCCH for the second message (e.g., Msg 2 1312) (e.g., preamble) after, for example, transmitting the first message (e.g., Msg 1 1311). The wireless device may determine the start time of the time window based on, for example, a PRACH opportunity used by the wireless device to transmit the first message (e.g., Msg 1 1311) (e.g., preamble). The wireless device may start in the time window one or more symbols after the last symbol of the first message (e.g., Msg 1 1311) comprising a preamble (e.g., the symbol in which the first message (e.g., Msg 1 1311) including the preamble transmission is completed, or in the first PDCCH opportunity since the end of the preamble transmission).One or more symbols may be determined based on numerology. The PDCCH may be mapped to a common search space (e.g., type 1-PDCCH common search space) configured by an RRC message. The wireless device may identify / determine the RAR, for example, based on an RNTI. A radio network temporary identifier (RNTI) may be used in response to one or more events that initiate / start a random access procedure. The wireless device may use the RA-RNTI, for example, for one or more communications associated with random access or any other purpose. The RA-RNTI may be associated with a PRACH opportunity in which the wireless device transmits / sends a preamble. The wireless device may determine the RA-RNTI based on, for example, at least one of an OFDM symbol index; a slot index; a frequency domain index; and / or a UL carrier indicator of the PRACH opportunity. An exemplary RA-RNTI may be determined as follows. RA-RNTI = 1 + s_id + 14×t_id + 14×80×f_id + 14×80×8×ul_carrier_id 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 transmit / send a third message (e.g., Msg 3 1313) (e.g., using the resources identified by Msg 2 1312) after (e.g., based on or in response to) the successful reception of a second message (e.g., Msg 2 1312). The third message (e.g., Msg 3 1313) may be used, for example, for contention resolution in contention-based random access procedures. A plurality of wireless devices may transmit / send the same preamble to the base station, and the base station may transmit / send a RAR corresponding to the wireless device. For example, a collision may occur if a plurality of wireless devices interpret the RAR as corresponding to themselves. Contention resolution (e.g., using the third message (e.g., Msg 3 1313) and the fourth message (e.g., Msg 4 1314)) may be used to increase the likelihood that a wireless device does not accidentally use the identification information of another wireless device. The wireless device may include a device identifier in the third message (e.g., Msg 3 1313) (e.g., C-RNTI if assigned, the TC RNTI included in the second message (e.g., Msg 2 1312), and / or any other suitable identifier) for performing contention resolution, for example.

[0122] The fourth message (e.g., Msg 4 1314) can be received, for example, after the transmission of the third message (e.g., Msg 3 1313) (e.g., based on or in response to the transmission). The base station can address the radio on the PDCCH using the C-RNTI, for example, if the C-RNTI was included in the third message (e.g., Msg 3 1313) (e.g., the base station can transmit the PDCCH to the radio device). The random access procedure can be determined to be completed successfully, for example, if the unique C-RNTI of the radio 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., Msg 3 1313) (e.g., if the radio device is in the RRC idle (e.g., RRC_IDLE) state or is not connected to the base station otherwise), the fourth message (e.g., Msg 4 1314) can be received using the DL-SCH associated with the TC-RNTI. For example, if the decoding of the MAC PDU is successful and the MAC PDU matches the CCCH SDU transmitted in the third message (e.g., Msg 3 1313) or contains the radio device contention resolution identification information MAC CE corresponding in another form, the radio device can determine that the contention resolution is successful and / or the radio device can determine that the random access procedure is completed successfully.

[0123] The wireless device may be composed of a SUL carrier and / or a NUL carrier. Initial access (e.g., random access) may be supported via an uplink carrier. The base station may configure the wireless device using multiple RACH configurations (e.g., two separate RACH configurations, one for the SUL carrier and the other for the NUL carrier). In the case of random access in a cell composed of a SUL carrier, the network may indicate which carrier to use (NUL or SUL). The wireless device may determine to use the SUL carrier, for example, when 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 uplink transmission of the random access procedure (e.g., the first message (e.g., Msg 1 1311) and / or the third message (e.g., Msg 3 1313)) may stay on the selected carrier or may be executed via the selected carrier. The wireless device may switch the uplink carrier during the random access procedure (e.g., between Msg 1 1311 and Msg 3 1313). The wireless device may determine and / or switch the uplink carrier for the first message (e.g., Msg 1 1311) and / or the third message (e.g., Msg 3 1313) based on, for example, a channel clear assessment (e.g., listen before talk).

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

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

[0126] A wireless device may start a time window (e.g., ra-ResponseWindow) to monitor the PDCCH for RAR, for example, after transmitting / sending a preamble (e.g., based on or in response to the transmission / sending). The base station may configure the wireless device using one or more beam failure recovery parameters such as a separate time window and / or a separate PDCCH within 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 relation to a beam failure recovery request. A separate time window for monitoring the PDCCH and / or RAR may be configured to start after transmitting / sending a beam failure recovery request (e.g., the window may start after transmitting the beam failure recovery request by any number of symbols and / or slots). The wireless device may monitor PDCCH transmissions addressed to the 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., Msg 1 1321) and determine that the random access procedure has succeeded after receiving the corresponding second message (e.g., Msg 2 1322) (e.g., based on or in response to it). The wireless device may determine that the random access procedure has completed successfully, for example, if the PDCCH transmission is addressed to the corresponding C-RNTI. The wireless device may determine that the random access procedure has completed successfully, for example, if the wireless device receives an RAR that includes a preamble identifier corresponding to the preamble transmitted / sent by the wireless device and / or if the RAR includes a MAC sub-PDU that includes a preamble identifier. The wireless device may determine this response as an indication of a confirmation response to the SI request.

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

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

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

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

[0131] Transport block 1342 may include data (e.g., delay-sensitive data), an identifier of a wireless device, security information, and / or device information (e.g., International Mobile Subscriber Identity (IMSI)). The base station may transmit / send a second message (e.g., Msg B 1332) as a 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., wireless resource allocation and / or MCS); an identifier of a wireless device (e.g., a UE identifier for contention resolution); and / or an RNTI (e.g., C-RNTI or TC-RNTI). The wireless device may determine that the two-step random access procedure has been successfully completed (e.g., for transport block 1342) if, for example, the preamble identifier in the second message (e.g., Msg B 1332) corresponds to or matches the preamble transmitted / sent 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 the PHY layer (e.g., layer 1) and / or the MAC layer (e.g., layer 2) of the wireless device or the base station. The control signaling may include downlink control signaling transmitted / sent from the base station to the wireless device and / or uplink control signaling transmitted / sent from the wireless device to the base station.

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

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

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

[0136] The base station may transmit / send DCI in one or more DCI formats, e.g., according to 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., having a compact DCI payload). DCI format 0_1 may be used for scheduling PUSCH in a cell (e.g., having more 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., having more DCI payload than DCI format 1_0). DCI format 2_0 may be used to provide a slot format indication to a group of wireless devices. DCI format 2_1 may be used to notify / inform a group of wireless devices of physical resource blocks and / or OFDM symbols, and the group of wireless devices may assume that transmission to the group of wireless devices is not intended. DCI format 2_2 may be used for the transmission of transmit power control (TPC) commands for PUCCH or PUSCH. DCI format 2_3 may be used for the transmission of a group of TPC commands for SRS transmission by one or more wireless devices. New function DCI formats may be defined in future releases. DCI formats may have different DCI sizes or may share the same DCI size.

[0137] The base station may process the DCI, for example, after scrambling the DCI with an RNTI, by channel coding (e.g., polar coding), rate matching, scrambling, and / or QPSK modulation. The base station may map the coded and modulated DCI to the resource elements used and / or configured for the PDCCH. The base station may transmit / send the DCI via a PDCCH that occupies 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 the 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 the resource elements may be based on the mapping of the CCEs and REGs (e.g., the mapping from CCEs to REGs).

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

[0139] FIG. 14B shows an example of the mapping from CCE to REG. The mapping from CCE to REG can be performed for DCI transmission by CORESET and PDCCH processing. The mapping from CCE to REG can be interleaved mapping (e.g., for the purpose of providing frequency diversity) or non-interleaved mapping (e.g., for the purpose of facilitating interference adjustment of the control channel and / or frequency selective transmission). The base station can perform different or the same mapping from CCE to REG for different CORESETs. The CORESET can be associated with the CCE-REG mapping (e.g., by RRC configuration). The CORESET can be configured with antenna port QCL parameters. The antenna port QCL parameters can indicate the QCL information of the DM-RS for PDCCH reception via the CORESET.

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

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

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

[0143] Multiple PUCCH formats (e.g., five PUCCH formats) may exist. A wireless device may determine the PUCCH format, for example, based on the size of the UCI (e.g., the number / amount of uplink symbols of the UCI transmission and the number of UCI bits). PUCCH format 0 may have a length of one or two OFDM symbols and may comprise two or fewer bits. The wireless device may use PUCCH format 0 to transmit the UCI via the PUCCH resource, for example, when the transmission is on / through one or two symbols and the number / amount of HARQ-ACK information bits (HARQ-ACK / SR bits) having positive or negative SR is 1 or 2. PUCCH format 1 may occupy several OFDM symbols (e.g., between 4 and 14 OFDM symbols) and may include two or fewer bits. The wireless device may use PUCCH format 1, for example, when the transmission is on / via four or more symbols and the number of HARQ-ACK / SR bits is 1 or 2. PUCCH format 2 occupies one or two OFDM symbols and may comprise three or more bits. The wireless device may use PUCCH format 2, for example, when the transmission is on / via one or two symbols and the number / amount of UCI bits is 2 or more. PUCCH format 3 may occupy several OFDM symbols (e.g., between 4 and 14 OFDM symbols) and may comprise three or more bits. The wireless device may use PUCCH format 3, for example, when the transmission is four or more symbols, the number / amount of UCI bits is 2 or more, and the PUCCH resource does not have an orthogonal cover code (OCC). PUCCH format 4 may occupy several OFDM symbols (e.g., 4 to 14 OFDM symbols) and may comprise three or more bits. The wireless device may use PUCCH format 4, for example, when the transmission is four or more symbols, the number / amount of UCI bits is 2 or more, and the PUCCH resource has an OCC.

[0144] The base station may transmit / configure the configuration parameters for a plurality of PUCCH resource sets to the wireless device, for example, using RRC messages. A plurality of 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. A PUCCH resource set may be configured using a PUCCH resource set index, a plurality of PUCCH resources identified by a PUCCH resource identifier (e.g., pucch-Resourceid), and / or the number (e.g., the maximum number) of UCI information bits that the wireless device may transmit / configure using one of the plurality of PUCCH resources within the PUCCH resource set. The wireless device may select one of the plurality of PUCCH resource sets, for example, based on the total bit length of the UCI information bits (e.g., HARQ-ACK, SR, and / or CSI) when configured using a plurality of PUCCH resource sets. The wireless device may select a first PUCCH resource set having a PUCCH resource set index equal to "0" if, for example, the total bit length of the UCI information bits is 2 or less. The wireless device may select a second PUCCH resource set having a PUCCH resource set index equal to "1" if, for example, the total bit length of the UCI information bits is greater than 2 and less than or equal to a first configured value. The wireless device may select a third PUCCH resource set having a PUCCH resource set index equal to "2" if, for example, the total bit length of the UCI information bits is greater than the first configured value and less than or equal to a second configured value. The wireless device may select a fourth PUCCH resource set having a PUCCH resource set index equal to "3" if, for example, the total bit length of the UCI information bits is greater than the second configured value and less than or equal to a third value (e.g., 1406, 1706, or any other number of bits).

[0145] A wireless device may 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. For example, the wireless device may determine the PUCCH resource based on a PUCCH resource indicator in DCI received on / via a PDCCH (e.g., DCI accompanied by DCI format 1_0 or 1_1). The n-bit (e.g., 3-bit) PUCCH resource indicator in the DCI may indicate one of a plurality (e.g., 8) of PUCCH resources within the PUCCH resource set. For example, the wireless device may use the PUCCH resource indicated by the PUCCH resource indicator in the DCI based on the PUCCH resource indicator to transmit / send UCI (HARQ-ACK, CSI, and / or SR).

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

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

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

[0149] Data to be transmitted to the wireless device 1502 can be provided / transferred / sent to the 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 can be provided / transferred / sent to the 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 can implement layer 1 OSI functions. Layer 1 can include, for example, the PHY layer described in connection with FIGS. 2A, 2B, 3, and 4A. For transmission / transmission processing, the PHY layer can perform, for example, forward error correction coding of the transport channel, interleaving, rate matching, mapping of the transport channel to the physical channel, modulation of the physical channel, multiple-input multiple-output (MIMO) or multi-antenna processing, etc.

[0150] The receiving processing system 1512 of the base station 1504 can receive uplink transmissions from the wireless device 1502. The receiving processing system 1512 of the base station 1504 can include one or more TRPs. The receiving processing system 1522 of the wireless device 1502 can receive downlink transmissions from the base station 1504. The receiving processing system 1522 of the wireless device 1502 can include one or more antenna panels. The receiving processing system 1512 and the receiving processing system 1522 can implement layer 1 OSI functions. Layer 1 can include, for example, the PHY layer described in relation to FIGS. 2A, 2B, 3, and 4A. For receiving processing, the PHY layer can 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 can include a plurality of antennas (e.g., a plurality of antenna panels, a plurality of TRPs, etc.). The wireless device 1502 can include a plurality of antennas (e.g., a plurality of antenna panels, etc.). The plurality of antennas can be used to perform one or more MIMO or multi-antenna technologies 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 can have a single antenna.

[0152] Processing system 1508 and processing system 1518 may each be associated with a memory 1514 and a memory 1524. Memories 1514 and 1524 (e.g., one or more non-transitory computer-readable media) may store computer program instructions or code that may be executed by processing system 1508 and / or processing system 1518 to perform one or more of the functions (e.g., one or more of the functions described herein, as well as other functions of a general computer, processor, memory, and / or other peripheral devices). Transmission processing system 1510 and / or reception processing system 1512 may be coupled to a 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. Transmission processing system 1520 and / or reception 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] Processing system 1508 and / or processing system 1518 may comprise one or more controllers and / or one or more processors. The one or more controllers and / or one or more processors may include, for example, a general-purpose processor, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) and / or other programmable logic device, discrete gates and / or transistor logic, discrete hardware components, an on-board unit, or any combination thereof. Processing system 1508 and / or processing system 1518 may perform at least one of signal coding / processing, data processing, power control, input / output processing, and / or any other function that may enable wireless device 1502 and / or base station 1504 to operate in a wireless environment.

[0154] The processing system 1508 can be connected to one or more peripheral devices 1516. The processing system 1518 can be connected to one or more peripheral devices 1526. The one or more peripheral devices 1516 and the one or more peripheral devices 1526 can be, for example, speakers, microphones, keypads, displays, touch pads, power supplies, satellite transceivers, universal serial bus (USB) ports, hands-free headsets, frequency modulated (FM) radio units, media players, Internet browsers, electronic control units (e.g., for automobiles), and / or one or more sensors (e.g., accelerometers, gyroscopes, temperature sensors, radar sensors, lidar sensors, ultrasonic sensors, optical sensors, cameras, etc.), and may include software and / or hardware that provide such functions and / or capabilities. The processing system 1508 and / or the processing system 1518 can receive input data (e.g., user input data) from the one or more peripheral devices 1516 and / or the one or more peripheral devices, and / or provide output data (e.g., user output data) to the one or more peripheral devices 1526. The processing system 1518 in the wireless device 1502 can 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 can include one or more power sources, such as batteries, solar cells, fuel cells, or any combination thereof. The processing system 1508 can be connected to a Global Positioning System (GPS) chipset 1517. The processing system 1518 can be connected to a Global Positioning System (GPS) chipset 1527. The GPS chipset 1517 and the GPS chipset 1527 can be configured to determine and provide the geographical location information of the wireless device 1502 and the base station 1504, respectively.

[0155] FIG. 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. 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. The instructions may also be stored in an attached (or internal) hard drive 1535. Further, computing device 1530 may include a security processor (not shown), which may execute instructions of one or more computer programs to monitor processes executed on processor 1531 and any process that requests access to any hardware and / or software components of computing device 1530 (e.g., ROM 1532, RAM 1533, removable media 1534, hard drive 1535, device controller 1537, network interface 1539, GPS 1541, Bluetooth interface 1542, WiFi interface 1543, etc.). Computing device 1530 may include one or more output devices, such as a display 1536 (e.g., a screen, a display device, a monitor, a 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, a keyboard, a mouse, a touch screen, a microphone, etc.The computing device 1530 may include one or more network interfaces, such as a network interface 1539, which may be a wired interface, a wireless interface, or a combination of the two. The network interface 1539 may provide an interface for the computing device 1530 to communicate with a network 1540 (e.g., a RAN, or any other network). The network interface 1539 may include a modem (e.g., a cable modem), and the external network 1540 may include a communication link, an external network, a home network, the provider's wireless, coaxial, fiber, or hybrid fiber / coaxial distribution system (e.g., a DOCSIS network), or any other desired network. Additionally, the computing device 1530 may include a location detection device, such as a Global Positioning System (GPS) microprocessor 1541, which may be configured to receive and process Global Positioning Signals and determine the geographical location of the computing device 1530 using possible assistance from external servers and antennas.

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

[0157] FIG. 16A shows an exemplary structure for uplink transmission. The processing of the baseband signal representing the physical uplink shared channel may comprise / perform one or more functions. The one or more functions may include at least one of scrambling; modulation of the scrambled bits to generate complex-valued symbols; mapping of the complex-valued modulated symbols to one or more transmission layers; converting pre-coding to generate complex-valued symbols; pre-coding of the complex-valued symbols; mapping of the pre-coded complex-valued symbols to resource elements; generation of 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 be generated, for example, when transform pre-coding is enabled. The CP-OFDM signal for uplink transmission may be generated, for example, when transform pre-coding is not enabled (e.g., as shown in FIG. 16A). These functions are examples, and other mechanisms for uplink transmission may be implemented.

[0158] FIG. 16B shows an exemplary structure for modulation of the baseband signal to the carrier frequency and up-conversion. The baseband signal may be a complex-valued SC-FDMA, CP-OFDM baseband signal (or any other baseband signal) for antenna ports, and / or a complex-valued physical random access channel (PRACH) baseband signal. Filtering may be performed / adopted, for example, before transmission.

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

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

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

[0162] A timer, for example, when started, may start operating and may continue operating until stopped or until ended. A timer may be started when not operating, and may be resumed when operating. A timer may be associated with a value (e.g., the timer may start or resume from a value and may end when starting from 0 and reaching the value). The duration of the timer may not need to be updated, for example, until the timer stops or ends (e.g., due to a BWP switch). A timer may be used to measure the period / window of a process. It can be understood that there may be multiple ways to implement one or more timers or other parameters with respect to the implementation and / or procedure related to one or more timers or other parameters. The period / window of a treatment may be measured using one or more of the multiple ways to implement a timer. A random access response window timer may be used to measure the time window for receiving a random access response. The time difference between two timestamps may be used, for example, instead of starting a random access response window timer and determining the timeout of the timer. The process for measuring the time window may be resumed, for example, when the timer is resumed. Other exemplary implementations may be configured / provided to resume measuring the time window.

[0163] A wireless device can operate in one or more states. The one or more states can 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 can include RRC states such as RRC_CONNECTED, RRC_INACTIVE, RRC_IDLE. The wireless device can switch / transition to / from one or more states. The wireless device can perform one or more operations in a particular state and / or may not be able to perform them. The wireless device may not perform a transmission (e.g., uplink data transmission) in a non-RRC_CONNECTED state (e.g., RRC_INACTIVE state and / or RRC_IDLE state) (e.g., it may not be permitted to perform the transmission or may prohibit the transmission). In such a case, the wireless device can establish a connection to the network / device (e.g., set up, establish, re-establish, and / or resume) for the transmission of DL data (e.g., mobile terminated, MT) and / or UL data (e.g., mobile originated, MO). The wireless device can execute one or more procedures (e.g., connection setup procedures) to establish a connection to the network / device in a non-RRC_CONNECTED state. The wireless device can execute one or more procedures (e.g., connection setup or resume procedures) if DL data (e.g., mobile terminated, MT) and / or UL data (e.g., mobile originated, MO) is available for transmission (e.g., stored in a buffer). Based on one or more procedures (e.g., after successfully completing or in response to a connection setup and / or resume procedure), the RRC state of the wireless device can switch / transition from a non-RRC_CONNECTED state to an RRC_CONNECTED state. The wireless device can receive a DL transmission (e.g., perform the reception) (e.g., receive DL data) and / or transmit a UL transmission (e.g., transmit / transmit UL data) in the RRC_CONNECTED state.A wireless device may switch / transition from the RRC_CONNECTED state to a non-RRC_CONNECTED state based on, for example, DL data (e.g., received) and / or UL data (e.g., transmitted / sent) not being available (e.g., such data not being stored in a buffer). To switch / transition from the RRC_CONNECTED state to a non-RRC_CONNECTED state, the wireless device may perform a connection release procedure. The connection release procedure (e.g., an RRC release procedure) may result in switching / transitioning the RRC state of the wireless device from the RRC_CONNECTED state to a non-RRC_CONNECTED state. The connection release procedure may include transmitting / sending, by a base station, and / or receiving, by the wireless device, one or more release messages (e.g., an RRC release message). The one or more release messages may result in the release of resources previously indicated for use by the wireless device. After switching / transitioning from the RRC_CONNECTED state, the wireless device may lack sufficient resources for transmitting / sending one or more messages (e.g., data, payload, etc.). At least some resources (e.g., previously configured / active BWPs) may not be available for use by the wireless device in a state other than RRC_CONNECTED. At least some resources (e.g., initial BWP) may be insufficient and / or inefficient for use in transmitting / sending one or more messages. The wireless device may be required to establish / re-establish a connection in the RRC_CONNECTED state before it becomes possible to transmit / send one or more messages (e.g., data, payload, etc.).

[0164] Switching and / or transitioning the wireless device state may require control signaling. Switching and / or transitioning between the non-RRC_CONNECTED state and the RRC_CONNECTED state may require the wireless device to send / transmit and / or receive multiple control signals (e.g., RRC messages, MAC CE, and / or DCI messages) in one or more layers that may include different layers. The RRC connection setup procedure may require the wireless device to send / transmit an RRC connection setup request to the base station and / or receive an RRC connection setup message (e.g., as a response to the RRC connection setup request). The RRC connection resume procedure may require the wireless device to send / transmit an RRC connection resume request to the base station and / or receive an RRC connection resume message (e.g., as a response to the RRC connection resume request). The RRC connection release procedure may require the wireless device to receive an RRC connection release request from the base station. At least some communications, such as DL and / or UL transmissions of a small amount of data (e.g., available and / or upon arrival), may not be communicated efficiently if the wireless device may be in the non-RRC_CONNECTED state. For example, it may be inefficient for the wireless device to establish (and / or resume) a connection to the network / device (e.g., switch / transition from the non-RRC_CONNECTED state to the RRC_CONNECTED state) and / or release the connection (e.g., switch / transition from the RRC_CONNECTED state to the RRC_CONNECTED 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 switching / transitioning may result in unnecessary power consumption and / or an increase in signaling overhead (e.g., by the wireless device). For example, the 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 of equal size to) the message itself.State switching / transition (e.g., RRC state switching / transition) 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 a wireless device.

[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 transmission (SDT)) may include, for example, traffic generated from smartphone applications and / or any wireless device applications, instant messaging (IM) services, IM / email clients, and / or heartbeat / keep-alive traffic from other apps / applications, various applications, non-smartphone applications, wearable devices, positioning information / services (e.g., vehicle-to-everything and / or location-based services), sensors (e.g., for periodically and / or event-triggered transmitting / transmitting temperature, pressure readings), smart meters and smart meter networks that transmit meter readings, multicast broadcast multimedia services (MBMs), and / or push notifications from any other wireless device that communicates with one or more other devices (e.g., in a communication network). SDT may include transmissions for connections to, for example, remote areas and / or aerial and / or maritime platforms (e.g., airships, drones, and / or balloons) via satellites (e.g., geostationary equatorial orbit, low Earth orbit, and / or medium Earth orbit satellite systems) and / or non-terrestrial networks (NTN).

[0166] As described in this specification, a wireless device may be configured for one or more transmissions (e.g., SDT) in one or more states (e.g., RRC_INACTIVE state and / or RRC_IDLE state) that may not be in a connected state (e.g., RRC_CONNECTED). The wireless device may be configured to transmit / send one or more messages (e.g., perform uplink data transmission) in a non-RRC_CONNECTED state. The one or more messages may include data traffic of the wireless device (e.g., during DTCH). The wireless device may transmit / send one or more data packets in a non-RRC_CONNECTED 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 for the wireless device in a non-RRC_CONNECTED state. The one or more uplink radio resources may include a BWP (and / or any other radio resource) (e.g., SDT BWP) for use by the wireless device in a non-RRC_CONNECTED state. The scheduling information may be provided in one or more release messages (e.g., RRC release message). A message (e.g., RRC release message) may include the scheduling information and information for switching / transitioning the state of the wireless device (e.g., from the RRC_CONNECTED state to the non-RRC_CONNECTED state). The one or more uplink radio resources may be for low-frequency 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 / send one or more data packets via one or more radio resources during a time period when the state of the wireless device is a non-RRC_CONNECTED state (e.g., RRC_INACTIVE state and / or RRC_IDLE state and / or any other state that is not RRC_CONNECTED).The wireless device may not switch / transition its RRC state to RRC_CONNECTED in order to transmit / transfer 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, until it receives an instruction (e.g., a broadcast message indicating a change / reconfiguration of the configuration parameters of the wireless device) to release and / or reconfigure one or more radio resources. Uplink transmission via one or more radio resources in the non-RRC_CONNECTED state may be efficient and / or flexible (e.g., in the case of low throughput short data bursts). Uplink transmission via one or more radio resources in the non-RRC_CONNECTED state may offer advantages such as more efficient signaling (e.g., the signaling overhead may be smaller than the payload / data). Uplink transmission via one or more radio resources in the non-RRC_CONNECTED state may reduce the signaling overhead. Uplink transmission via one or more radio resources in the non-RRC_CONNECTED state may improve the battery performance of the wireless device. For example, a wireless device having intermittent small data packets (e.g., SDT) in the non-RRC_CONNECTED state may benefit from such uplink transmission in the non-RRC_CONNECTED state.

[0167] As described in this specification, 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 for the RRC_IDLE state (e.g., unless specifically indicated for the RRC_IDLE state). Procedures, configuration parameters, and / or feature descriptions in this specification that may be related to uplink data transmission in the RRC_IDLE state may be applicable and / or available for the RRC_INACTIVE state (e.g., unless specifically indicated for the RRC_INACTIVE state). Procedures, configuration parameters, and / or descriptions in this specification that may be related to uplink data transmission in the RRC_INACTIVE state may be applicable and / or available for the RRC_IDLE state of the wireless device, for example, if the RRC_CONNECTED and / or RRC_IDLE state is at least an RRC state in which the wireless device can be configured to operate. Procedures, configuration parameters, and / or descriptions in this specification that may be related to uplink data transmission may be applicable and / or available for the RRC_INACTIVE and / or RRC_IDLE states of the wireless device, for example, if the RRC_CONNECTED, RRC_INACTIVE, and / or RRC_IDLE states are at least three RRC states in which the wireless device can be configured to operate. References to RRC_INACTIVE in this specification may refer to any inactive state, such as any inactive state of the wireless device. References to RRC_CONNECTED in this specification may refer to any connection state, such as any connection state of the wireless device to another communication device (e.g., a base station). References to RRC_IDLE in this specification may refer to any idle state, such as any idle state of the wireless device.

[0168] Figure 17 shows an example of resource availability for various states of a wireless device. The wireless device state may include, for example, RRC_CONNECTED, RRC_INACTIVE, RRC_IDLE, and / or any other state associated with connectivity, activity, power, etc. One or more data packet transmissions and / or other transmissions may occur (and / or may be scheduled to occur) in the RRC_INACTIVE state (and / or RRC_IDLE state). The transmission may correspond to a resource 1703 that is available, schedulable, and / or configurable. One or more data packet transmissions may include any transmission described herein. The wireless device 1702 may receive one or more RRC messages from the base station 1701 that configure the resource 1703. The resource 1703 may include an uplink resource. Additionally or alternatively, the resource 1703 may include any combination of uplink resources, downlink resources, and / or sidelink resources. The uplink resource is available, schedulable, and / or configurable in a non-RRC_CONNECTED 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 resource 1703 based on the RRC state of the wireless device 1702. The wireless device 1702 may receive wireless resource configuration parameters associated with one or more wireless resources (e.g., uplink wireless resources, resource 1703, etc.) that the wireless device 1702 may use in a non-RRC_CONNECTED state. One or more wireless resources may be configured (e.g., pre-configured). One or more wireless resources may be configured, for example, when the wireless device is in the RRC_CONNECTED state, RRC_INACTIVE state, RRC_IDLE state, and / or any other state.Wireless device 1702 may receive an RRC message including radio resource configuration parameters of one or more radio resources over a period of time when the wireless device is in the RRC_CONNECTED state (e.g., at step 1710). The wireless device may not start (and / or may not activate) one or more radio resources over a period of time when the wireless device is in the RRC_CONNECTED state (e.g., at step 1710). The RRC release message may include radio resource configuration parameters of one or more radio resources. Based on receiving a release message (e.g., an RRC release message) (e.g., after receiving and / or in response to receiving), the wireless device may start (and / or activate) one or more radio resources. Based on (e.g., after and / or in response to) the RRC state of wireless device 1702 being in a non-RRC_CONNECTED state (and / or transitioning thereto) (e.g., at step 1720), the wireless device may start (and / or activate and / or use) one or more radio resources. When the RRC state is in a non-RRC_CONNECTED state (e.g., when the RRC state is maintained as this state), wireless device 1702 may transmit / transmit one or more data packets (and / or any transmission) via one or more radio resources. Wireless device 1702 may transmit / transmit one or more data packets (and / or any other transmission) without transitioning to the RRC_CONNECTED state (e.g., at step 1720). Wireless device 1702 may determine to transition the RRC state from the non-RRC_CONNECTED state to the RRC_CONNECTED state (e.g., at step 1730). Based on switching / transitioning the RRC state to the RRC_CONNECTED state (e.g., after or in response thereto), wireless device 1702 may determine to stop (and / or clear and / or suspend and / or deactivate) the use of one or more resources.

[0169] The wireless device 1702 may determine to switch / transition the RRC state (e.g., of the wireless device) to a non-RRC_CONNECTED state. The wireless device may determine to switch / transition the RRC state from the RRC_CONNECTED state. The wireless device 1702 may determine to switch / transition the RRC state to a non-RRC_CONNECTED state, for example, based on receiving one or more RRC messages (e.g., thereafter, or in response thereto). The wireless device 1702 may receive one or more RRC messages (e.g., an RRC release message) from the base station 1701. One or more RRC messages (e.g., an RRC release message) may indicate the release of the RRC connection (e.g., release from the network). Based on receiving the RRC message (e.g., after receiving it, or in response to receiving it), the wireless device 1702 may execute an RRC release procedure. The RRC release procedure may include the release of one or more established radio bearers and / or configured radio resources. The RRC release procedure may include the suspension of the RRC connection (e.g., when a signaling radio bearer (SRB) (e.g., SRB2) and / or at least one dedicated radio bearer (DRB) is set up), and / or the suspension of an established radio bearer. Based on receiving the RRC message (and / or executing the RRC release procedure) (e.g., thereafter, and / or in response thereto), the wireless device 1702 may switch / transition (and / or determine to switch / transition) the RRC state of the wireless device from the RRC_CONNECTED state to a non-RRC_CONNECTED state.

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

[0171] Wireless device 1702 may receive a message including one or more configurations. A configuration among the one or more configurations may include an identifier (or index) of the configuration. Each of the one or more configurations may include wireless resource configuration parameters of one or more uplink wireless resources that wireless device 1702 may use in a non-RRC_CONNECTED state.

[0172] A 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 a non-RRC_CONNECTED state (e.g., RRC_INACTIVE state and / or RRC_IDLE state). The one or more uplink radio resources in the non-RRC_CONNECTED state may include one-time use resources (e.g., for a single transmission) and / or resources for multiple uses. The one or more uplink radio resources in the non-RRC_CONNECTED state may include periodic resources (e.g., for one or more uplink transmissions). The one or more uplink radio resources in the non-RRC_CONNECTED state may include preconfigured uplink resources (PUR). One or more uplink grants indicating one or more uplink radio resources in the non-RRC_CONNECTED state may include configured grants and / or preconfigured grants. The configured and / or preconfigured grants may include multiple types of grants, such as (pre)configured grant type 1 and / or (pre)configured grant type 2. One or more uplink radio resources determined (and / or indicated) by the (pre)configured grant type 1 may not require an indication to start / resume (and / or activate / reactivate) one or more uplink radio resources (e.g., after receiving, or in response to receiving, an RRC message indicating one or more uplink radio resources in the non-RRC_CONNECTED state). The wireless device may (re)open (and / or (re)activate) one or more uplink radio resources based on receiving an RRC message including the (pre)configured grant type 1 indicating one or more uplink radio resources in the non-RRC_CONNECTED state (e.g., after receiving, or in response to receiving).One or more uplink radio resources determined (and / or indicated) by a pre-configured permission type 2 may require an instruction to (re)open (and / or (re)activate) one or more uplink radio resources (e.g., after receiving or in response to receiving an RRC message indicating one or more uplink radio resources). The wireless device may not (re)open (and / or (re)activate) one or more uplink radio resources based on (e.g., after receiving or in response to receiving an RRC message having a pre-configured permission type 2 indicating one or more uplink radio resources). The wireless device may (re)open (and / or (re)activate) one or more uplink radio resources based on receiving an instruction to do so (e.g., after receiving or in response to receiving) in the non-RRC_CONNECTED state. The wireless device may receive an instruction based on receiving an RRC message including a pre-configured permission type 2 indicating one or more uplink radio resources (e.g., after receiving or in response to receiving). An uplink permission indicating one or more uplink radio resources in the non-RRC_CONNECTED state may be referred to as a pre-configured permission having a specific type indicator (e.g., pre-configured permission type 3, 4, etc.). The pre-configured permission type 1 and / or the pre-configured permission type 2 may indicate one or more (e.g., periodic) uplink permissions in the RRC_CONNECTED state. The pre-configured permission type 3 (and / or other types of pre-configured permissions) may indicate one or more (e.g., periodic) uplink permissions in the non-RRC_CONNECTED state.

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

[0174] Figure 18B shows an example of the configuration and / or activation of one or more radio resources. One or more (pre-)configured grants may indicate one or more radio resources (e.g., uplink radio resources and / or downlink radio resources) in a non-RRC_CONNECTED state (e.g., RRC_INACTIVE state and / or RRC_IDLE state). The (pre-)configured grant in Figure 18B may require an additional activation message (e.g., DCI, MAC CE, and / or RRC) to activate (and / or start) one or more uplink radio resources (and / or (pre-)configured grants) (e.g., at 1804). The wireless device 1812 may receive one or more RRC messages including the configuration parameters of the (pre-)configured grant of the cell (e.g., at 1805). Based on receiving one or more RRC messages (e.g., after receiving or in response to receiving), the wireless device may determine (and / or store) the (pre-)configured grant for the cell. The one or more RRC messages may include an RRC release message. Based on receiving one or more RRC messages (e.g., after receiving or in response to receiving), the wireless device may not (re-)open (or activate) the (pre-)configured grant (e.g., at 1804) (e.g., at least until the wireless device receives an additional activation message (e.g., DCI, MAC CE, and / or RRC)). The wireless device may monitor the PDCCH in the non-RRC_CONNECTED state to receive an additional activation message. The wireless device may receive an (additional) activation message (e.g., DCI, MAC CE, and / or RRC) based on receiving an RRC message (e.g., after receiving or in response to receiving). The DCI message carried by the PDCCH may include an (additional) activation message. The MAC CE and / or RRC message received based on the downlink allocation of the DCI message carried by the PDCCH may include an (additional) activation message.The configuration parameters within the RRC message may indicate the time and / or frequency resource allocation of the PDCCH, the monitoring opportunity of the PDCCH, and / or the monitoring periodicity of the PDCCH. The wireless device may determine that the (pre-)configured grant occurs (re-)periodically with the periodicity indicated by the configuration parameters and / or the timing offset reference (e.g., H-SFN, SFN, slot, and / or symbol). The wireless device may determine the SFN, slot, and / or symbol (e.g., of the H-SFN) based on the reception timing of the additional activation message received via the PDCCH. The wireless device 1812 may receive a deactivation message indicating deactivating and / or suspending (clearing, and / or invalidating) one or more uplink radio resources (and / or the (pre-)configured grant). The wireless device 1812 may receive the deactivation message in the non-RRC_CONNECTED state. The wireless device 1812 may communicate with (and / or establish a connection to) the network (and / or the base station 1811). The wireless device 1812 may execute the RRC connection setup procedure and / or the RRC connection resume procedure to communicate with (and / or establish a connection to) the base station 1811. The wireless device 1812 may transmit / send an RRC connection setup request (e.g., for the RRC connection setup procedure) and / or an RRC connection resume request (e.g., for the RRC connection resume procedure). The wireless device 1812 may receive a response from the base station 1811 indicating the completion of establishing the RRC connection. The wireless device 1812 may receive an RRC connection setup completion message (e.g., for the RRC connection setup procedure). The wireless device 1812 may receive an RRC connection resume completion message (e.g., for the RRC connection resume procedure). Based on establishing the connection (e.g., thereafter, or in response thereto), the RRC state of the wireless device 1812 may transition to the 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 invalidated) based on the fact that the RRC state of the wireless device 1812 is the RRC_CONNECTED state (e.g., thereafter, or in response thereto). One or more uplink radio resources (and / or (pre-)configured grants) may be deactivated and / or suspended (cleared, and / or invalidated) based on establishing a connection to the base station 1811 (e.g., thereafter, or in response thereto) (e.g., after receiving and / or in response to receiving RRC connection setup and / or resume completion).

[0175] One or more uplink radio resources in a non-RRC_CONNECTED state may be configured by one or more upper layers (e.g., the RRC layer and / or the MAC layer). The wireless device 1812 may receive a message (e.g., an RRC message) from the base station 1811 that includes one or more configuration parameters for uplink data transmission via one or more uplink radio resources (e.g., 1806) in a non-RRC_CONNECTED state.

[0176] One or more configuration parameters may include and / or indicate an RNTI. The RNTI is for the transmission of uplink data via one or more uplink radio resources in the non-RRC_CONNECTED state. The RNTI may be an identifier of a 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 the PDCCH using the RNTI. The wireless device may monitor the PDCCH using the RNTI based on the transmission of uplink data via one or more uplink radio resources (e.g., after the transmission or in response to the transmission). The wireless device may receive, via the PDCCH, DCI having / using a CRC scrambled by the RNTI. The DCI may indicate a positive acknowledgment response for the transmission of uplink data. The DCI may indicate a negative acknowledgment response for the transmission of uplink data. The DCI may indicate a retransmission of the transmission of uplink data. The DCI may indicate an uplink grant for retransmission. The DCI may indicate an updated parameter value of one or more configuration parameters. The DCI may indicate a (e.g., new or updated) timing advance value for the transmission of uplink data via one or more uplink radio resources in the non-RRC_CONNECTED state. The DCI may indicate the trigger / initiation of an RA procedure. One or more configuration parameters may indicate the duration of a response window (e.g., exemplary parameter name: ResponseWindowSize). The wireless device may monitor the PDCCH over the duration of the response window to receive a response (e.g., DCI) from the base station for the transmission of data.

[0177] One or more configuration parameters may indicate the number / quantity of skipped uplink grants (and / or resource opportunities) (e.g., exemplary parameter name: ImplicitReleaseAfter). The wireless device may, for example, based on the indicated number / quantity, release (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. 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 / quantity of skipped uplink grants (and / or resource opportunities) indicated by one or more configuration parameters may include the number / quantity of consecutive skipped (and / or empty) uplink grants (and / or resource opportunities). The wireless device may, for example, based on a determination that the wireless device may skip N opportunities (e.g., N consecutive opportunities) for one or more uplink radio resources or may not transmit / send uplink packets over one or more uplink radio resources over N times (e.g., N = the number of skipped uplink grants and / or resource opportunities) (e.g., after the determination or in response to the determination), release (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. The wireless device may, for example, not apply (and / or use) implicit resource release (e.g., implicit pre-configured uplink resource release, etc.) if 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 does not exist in 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 operations.Any of the procedures described with respect to FIG. 18A may be applicable to the procedures with respect to FIG. 18B (for example, the activation and / or start of a resource at 1803 may be applicable to the activation and / or start of a resource at 1805 and / or 1806).

[0178] FIG. 19 shows an example of a resource configuration. The base station 1901 may configure the wireless device 1902 using one or more resources (e.g., 1910) for transmission and / or reception (for example, in the non-RRC_CONNECTED state). The base station 1901 may configure the wireless device 1902 using one or more resources for uplink transmission 1903. One or more resources in the non-RRC_CONNECTED state (for example, for data packet transmission) are configured and used for transmission / reception (for example, at 1903), not configured and used for transmission / reception (for example, at 1904), and / or may be released after being configured (for example, at 1905). The wireless device 1902 may receive one or more RRC messages configuring an uplink resource (e.g., 1910). The uplink resource (e.g., 1910) may be available, scheduled, and / or configured in the non-RRC_CONNECTED state. The wireless device 1902 may not transmit / transfer uplink packets over one or more opportunities of the uplink resources (for example, at 1904). The wireless device 1902 may count / determine one or more opportunities. The wireless device 1902 may determine to release the uplink resource (for example, may determine at least one of release, clear, deactivation, and / or suspension). The wireless device 1902 may release the uplink resource if, for example, the number / quantity of one or more opportunities that the wireless device may skip (and / or not use for transmitting / transferring uplink packets) meets a threshold (for example, is above the threshold). The number / quantity of one or more opportunities may be the number / quantity 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, for example, count / determine the number / amount of skipped uplink grants 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 indicate the number / amount of skipped uplink grants (and / or resource opportunities) that the wireless device counts / determines. The wireless device may, for example, determine to release (e.g., clear, deactivate, discard, and / or suspend) one or more uplink radio resources, an uplink grant, and / or one or more configuration parameters if m meets / reaches a threshold (e.g., is greater than or equal to the threshold). The threshold may be configurable by one or more configuration parameters (e.g., the threshold may be 1, 2, 3, 4, 8, etc.). One or more configuration parameters may indicate that the threshold is not configured (e.g., the threshold may be invalidated). The wireless device may, for example, determine that implicit resource release is not applied (e.g., is invalidated) if one or more configuration parameters do not have a threshold.

[0180] The wireless device may count / determine the number / amount of skipped uplink grants (and / or resource opportunities) using / by using a counter. 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 increase and / or decrease based on the implemented counter. The counter may include an up-counter that may count the number / amount of skipped uplink grants (and / or resource opportunities) in ascending order. The wireless device may determine to release (e.g., clear, deactivate, discard, and / or suspend) one or more uplink wireless resources, an uplink grant indicating one or more uplink wireless resources, and / or one or more configuration parameters when, for example, the value of 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 determine to release (e.g., clear, deactivate, discard, and / or suspend) one or more uplink wireless resources, an uplink grant indicating one or more uplink wireless resources, and / or one or more configuration parameters when, for example, the value of the counter starts from a threshold (and / or a first predetermined value) and reaches 0 (or a second amount and / or predetermined value). The wireless device may determine to release (e.g., clear, deactivate, discard, and / or suspend) one or more uplink wireless resources, an uplink grant indicating one or more uplink wireless resources, and / or one or more configuration parameters when, for example, the number of skipped uplink grants (and / or resource opportunities) counted by the wireless device reaches / meets a threshold (for any type of counter, e.g., an up-counter, a down-counter, etc.). The description of the counter in this specification may apply to any type of counter (e.g., the description regarding the up-counter may apply to the description regarding the down-counter, and / or the description regarding the down-counter may apply to the description regarding the up-counter).

[0181] The wireless device may determine to increase m based on at least one of the following. For example, the wireless device may increase m if the wireless resource opportunity of one or more uplink wireless resources is not used (e.g., if the wireless device does not transmit / transmit data packets via the wireless resource opportunity of one or more uplink wireless resources, the wireless device may increase m). For example, the wireless device may increase m if the wireless resource opportunity of one or more uplink wireless resources is not used during a time period when the wireless device is in the non-RRC_CONNECTED state. For example, the wireless device may increase m (e.g., the uplink grant and / or resource opportunity of one or more skipped uplink wireless resources) if no MAC PDU is generated for the uplink grant and / or resource opportunity. For example, the wireless device may increase m if the wireless resource opportunity of one or more uplink wireless resources is used (e.g., the wireless device transmits / transmits data packets via the wireless resource opportunity of one or more uplink wireless resources), but no response corresponding to the data packet (e.g., one or more of HARQ ACK, HARQ NACK, L2 (e.g., MAC CE) response, and / or L3 (e.g., RRC message) response) is received. For example, the wireless device may increase m if the wireless device skips the wireless resource opportunity of one or more uplink wireless resources due to access prohibition to the cell in which one or more uplink wireless resources are configured. For example, the wireless device may increase m if the wireless device skips the wireless resource opportunity of one or more uplink wireless resources due to the wireless device being in a waiting time (and / or extended waiting time). The waiting time (and / or extended waiting time) may indicate how many seconds the wireless device can wait (e.g., whether it is necessary to wait) based on the reception of a rejection (e.g., RRC connection rejection) (e.g., after reception or in response to reception) and / or until at least an RRC connection request message is transmitted / 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 determine to increment m based on at least the following. The base station (and / or network) may increment m, for example, if the base station does not receive an uplink packet via the wireless resource opportunity of one or more uplink wireless resources. The base station (and / or network) may increment m, for example, during a time period when the wireless device is in the RRC_CONNECTED state. The base station (and / or network) may increment m, for example, if the base station (e.g., the network) does not transmit / send a response (e.g., HARQ feedback (ACK and / or NACK)). The base station (and / or network) may increment m, for example, if the base station receives an uplink packet via the wireless resource opportunity of one or more uplink wireless resources but does not transmit / send a response to the uplink packet to the wireless device. The response may include a HARQ ACK feedback. The response may include a HARQ NACK feedback. The response may include an L2 response (e.g., MAC CE) and / or an L3 response (e.g., RRC message). The base station (and / or network) may increment m, for example, if the wireless resource opportunity of one or more uplink wireless resources is skipped by the wireless device (e.g., due to access prohibition to the cell in which one or more uplink wireless resources are configured). The base station (and / or network) may increment m, for example, if the wireless resource opportunity of one or more uplink wireless resources is skipped by the wireless device due to the wireless device being in a waiting time (and / or an extended waiting time). The waiting time (and / or the extended waiting time) may indicate (e.g., may be defined) how many seconds the wireless device waits based on the reception of an RRC connection rejection (e.g., after the reception, or in response to the reception) 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. For example, the wireless device may not increase m during a time period when the wireless device is in the RRC_CONNECTED state. For example, the wireless device may not increase m based on (e.g., after or in response to) one or more uplink radio resources of the wireless device being suspended (e.g., deactivated and / or cleared). For example, the wireless device may not increase m during a time period when a timer (e.g., a prohibition timer) of the wireless device is operating. The wireless device may determine the time before an access attempt is executed based on a prohibition timer (e.g., when the prohibition timer expires). The time before an access attempt is executed may be determined based on (e.g., after or in response to) the access attempt being prohibited in an access prohibition check. The base station (and / or network) may maintain a counter to synchronize with the wireless device. The base station (and / or network) may determine not to increase m based on at least the following, for example. For example, the base station (and / or network) may not increase m during a time period when the wireless device is in the RRC_CONNECTED state. For example, the base station (and / or network) may not increase m based on (e.g., after or in response to) one or more uplink radio resources of the wireless device being suspended (e.g., deactivated and / or cleared). For example, the base station (and / or network) may not increase m during a time period when a timer (e.g., a prohibition timer) of the wireless device is operating. The wireless device may determine the time before an access attempt is executed based on a prohibition timer (e.g., when the prohibition timer expires). The time before an access attempt is executed may be determined based on (e.g., after or in response to) the access attempt being prohibited in an access prohibition check.

[0184] The wireless device may reset a counter based on at least one of the following. The wireless device may reset the counter (e.g., to 0 in the case of an up-counter) based on the success of communication between the wireless device and the base station (and / or network) (e.g., after success or in response to success). The wireless device may reset the counter (e.g., to 0 in the case of an up-counter) based on receiving an acknowledgment response (e.g., an ACK message) corresponding to an uplink transmission via one or more uplink radio resources (e.g., after receiving or in response to receiving). The wireless device may be in a non-RRC_CONNECTED state. The wireless device may reset the counter (e.g., to 0 in the case of an up-counter) based on transmitting / sending an acknowledgment response (e.g., an ACK message) corresponding to receiving a downlink data packet from the base station (and / or network) in the non-RRC_CONNECTED state (e.g., after transmitting / sending or in response to transmitting / sending). When the wireless device is in the RRC_CONNECTED state, the wireless device may not reset the counter based on successful communication (e.g., after communication or in response to communication).

[0185] The base station (and / or network) may reset a 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) based on successful communication between the wireless device and the base station (and / or network) (e.g., after or in response to the communication). The base station (and / or network) may reset the counter (e.g., to 0 in the case of an up-counter) based on transmitting / sending a confirmation response (e.g., an ACK message) corresponding to an uplink transmission performed by the wireless device via one or more uplink radio resources (e.g., after or in response to the transmitting / sending). The wireless device may perform an uplink transmission in the non-RRC_CONNECTED state. The base station (and / or network) may reset (e.g., to 0 in the case of an up-counter) based on receiving from the wireless device a confirmation response (e.g., an ACK message) corresponding to a downlink data packet transmitted / sent to the wireless device during a time period when the wireless device is in the non-RRC_CONNECTED state (e.g., after or in response to the receiving). The base station (and / or network) may not reset the counter based on successful communication (e.g., after or in response to success) during a time period when the wireless device is in the RRC_CONNECTED state.

[0186] One or more configuration parameters may indicate, in a non-RRC_CONNECTED state, the value of a time alignment timer (TAT) for a cell (and / or a cell group including the cell) via one or more uplink radio resources configured in the cell (e.g., exemplary parameter name: TimeAlignmentTimer). The 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 the duration (e.g., how long) for which the timing advance offset value is valid and / or is used to adjust the uplink timing for uplink transmission to the cell (and / or cells in the cell group). The value of the TAT may indicate / determine the duration (e.g., how long) for which the radio device may determine the cell (and / or cells belonging to the associated TAG) for which the uplink time should be aligned. The radio device may determine (and / or adjust) the uplink timing for uplink transmission (e.g., PRACH, PUSCH, SRS, and / or PUCCH transmission) on / through the cell (and / or on / through 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) the uplink timing for uplink transmission is delayed or advanced for uplink synchronization. The radio device may operate the TAT for a time interval (and / or duration) indicated by the value of the TAT. The radio device may determine that the timing advance offset value is valid (and / or used) to adjust the uplink timing for uplink transmission on the cell (or cells in the cell group) during the time period when the TAT is operating. The radio device may determine that, for example, the uplink from the radio device to the cell (e.g., base station) is out of synchronization when the TAT associated with the cell group (e.g., TAG) to which the cell belongs is not operating and / or has ended.The wireless device may stop performing uplink transmissions on / through the cell (and / or on / through cells in the cell group) when, for example, the TAT associated with the cell group (e.g., TAG) to which the cell belongs is not operating and / or has ended. The wireless device may stop uplink transmissions to the cell when, for example, the uplink transmission timing difference (e.g., maximum uplink transmission timing difference) between the TAGs of the wireless device (and / or other cell groups), or the uplink transmission timing difference between the TAGs of any MAC entity of the wireless device (e.g., two MAC entities configured for dual connectivity) (and / or other cell groups), is exceeded. The wireless device may determine that the TAT associated with the cell has ended when, for example, the uplink timing difference between the 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) when, for example, the TAT associated with the cell group (e.g., TAG) to which the cell belongs is not operating and / or has ended. The wireless device may start (and / or resume) the TAT based on receiving a timing advance command indicating the timing advance offset value of the cell (and / or cells in the cell group) (e.g., new and / or updated timing advance offset value) (e.g., after receiving it, or in response to receiving it). The timing advance command may be received as a MAC CE and / or DCI. The timing advance command may indicate the timing advance offset value of a cell in which one or more uplink radio resources are in the non-RRC_CONNECTED state.

[0187] A wireless device may start (and / or resume) a timing alignment timer based on a switch / transition to a non-RRC_CONNECTED state (e.g., after the switch / transition or in response to the switch / transition). The wireless device may start (and / or resume) the timing alignment timer, for example, when the wireless device receives (and / or is configured using) one or more uplink radio resources for the non-RRC_CONNECTED state. The wireless device may start (and / or resume) the timing alignment timer based on receiving (e.g., after receiving or in response to receiving) configuration parameters associated with the timing alignment timer (e.g., the timer value of the timing alignment timer). The wireless device may start (and / or resume) the timing alignment timer based on receiving (e.g., after receiving or in response to receiving) a timing advance offset value. The wireless device may receive a lower layer control message (e.g., DCI or PDCCH) that may indicate a timing advance offset value. The wireless device may receive a MAC layer control message (e.g., MAC CE and / or RAR) that may indicate a timing advance offset value. The wireless device may start (and / or resume) the timing 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 during which TAT is operating. The wireless device may verify the TA value based on one or more verification conditions. The wireless device may start (and / or resume) the timing alignment timer based on a determination that TA has been verified (e.g., after the determination or in response to the determination). The wireless device may determine that TAT has ended, for example, if TAT has been operating over a time interval (and / or duration) indicated by the value of TAT. The wireless device may determine that the timing advance offset value is invalid based on the end of TAT (e.g., after the end or in response to the end).

[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] One or more configuration parameters may indicate the number / amount of opportunities for one or more uplink radio resources (e.g., exemplary parameter name: NumOccasions). The number / amount of opportunities may indicate that one or more uplink radio resources are single-use resources (or grants) for a single uplink transmission. The number / amount of opportunities may indicate that one or more uplink radio resources include a plurality of uplink radio resources. The number / amount of opportunities may indicate that one or more uplink radio resources include one or more periodic radio resources.

[0190] One or more configuration parameters may indicate the time-domain resource allocation of one or more uplink radio resources. One or more configuration parameters may indicate the periodicity (e.g., exemplary parameter name: Periodicity) of one or more uplink radio resources in the non-RRC_CONNECTED state. One or more configuration parameters may include a time offset. The time offset may include a time-domain offset with respect to (and / or related to) a time reference. The time reference may include a specific SFN (e.g., H-SFN), a specific subframe number, a specific slot number, a specific symbol number, and / or a combination 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) if, for example, the field of the time reference does not exist in one or more configuration parameters. The wireless device may receive one or more uplink grants indicated by one or more configuration parameters, for example. One or more uplink grants may indicate one or more uplink radio resources. One or more uplink radio resources may start from a symbol (of a slot of the SFN of the H-SFN) indicated by the time offset. One or more uplink radio resources may occur periodically from the symbol using the periodicity. The wireless device may determine (e.g., sequentially determine) that the Nth uplink grant among one or more uplink grants occurs in a transmission time interval (TTI, e.g., slot, mini-slot, symbol) based on the time offset and N * periodicity. The time offset may be indicated / defined in terms of the number / quantity of symbols, the number / quantity of slots, the number / quantity of subframes, the number / quantity of SFNs, the number / quantity of H-SFNs, and / or a combination thereof. One or more configuration parameters may include a parameter such as timeDomainOffset. The parameter (e.g., timeDomainOffset) may indicate the time offset received by the wireless device from the base station. One or more configuration parameters may include a parameter such as timeReferenceSFN (e.g., a time reference reference defined with respect to SFN and / or H-SFN).A parameter (e.g., timeReferenceSFN) may indicate an SFN as a time reference used for determining the time offset of a resource in the time domain. The SFN may repeat over a period of 1024 frames. A 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 / quantity 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 that the Nth uplink grant occurs (and / or recurs) in a symbol in the following case (e.g., sequentially determine).

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

[0192] The wireless device may initiate and / or resume transmission via one or more uplink radio resources in the non-RRC_CONNECTED state. The wireless device may initiate and / or resume transmission via one or more uplink radio resources in the non-RRC_CONNECTED state based on one or more conditions. The wireless device may receive configuration parameters indicating one or more conditions. The wireless device may determine whether a cell in which one or more uplink radio resources in the non-RRC_CONNECTED state are configured supports transmission via the one or more uplink radio resources. The wireless device may receive one or more RRC messages (e.g., SIB). The one or more RRC messages may include configuration parameters indicating whether and / or under what circumstances the cell supports transmission via the one or more uplink radio resources. The configuration parameters may indicate which type of transmission (and / or is available) is supported via the one or more uplink radio resources. The type may include control plane (CP) transmission and / or user-plane (UP) transmission. The configuration parameters may indicate which type of network (e.g., which) the cell is connected to supports transmission via the one or more uplink radio resources. The wireless device may determine whether and / or under what circumstances transmission via the 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 in a network system (e.g., 5G Core, Evolved Packet Core (EPC), 3GPP Rel.15, 16, 17, prior / subsequent releases, etc.) and / or one or more radio technologies (e.g., Wifi, 5G, Bluetooth, satellite, etc.). The configuration parameters may indicate which type of spectrum (and / or frequency band) supports transmission via the one or more uplink radio resources. The type of spectrum may include licensed spectrum and / or unlicensed spectrum.The type of spectrum may include the CBRS (Citizens Broadband Radio Service) band (e.g., the broadband of the 3.5 GHz band). The type of spectrum may include the millimeter wave band (e.g., exceeding 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 CP transmission using PUR is supported in the cell / when it is supported (e.g., when connected to a 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 CP transmission using PUR is supported in the cell / when it is supported (e.g., when connected to the EPC). The wireless device may determine that PUR is supported in the cell, for example, when the RRC message received from the cell indicates cp-PUR-EPC = "true" (or "enabled") (e.g., when connected to the EPC).

[0193] A wireless device may initiate and / or resume transmission via one or more uplink radio resources in a non-RRC_CONNECTED state. The wireless device may initiate and / or resume transmission via one or more uplink radio resources in a non-RRC_CONNECTED state, for example, based on one or more conditions. The wireless device may initiate and / or resume transmission via one or more uplink radio resources in a non-RRC_CONNECTED 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 a request to establish an RRC connection; the wireless device triggers a request to resume an RRC connection; the wireless device has a stored value of a valid security parameter (e.g., the nextHopChainingCount provided in an RRCConnectionRelease message with a suspension indication if a previous suspension procedure is active); the wireless device triggers an establishment or resume request for a mobile originating call and / or the establishment cause is mo-Data, mo-ExceptionData, or delayTolerantAccess; and / or the size of the MAC PDU (including, for example, total UL data) is expected to be less than or equal to the transport block size (TBS) configured for PUR.

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

[0195] A wireless device may determine whether a timing advance value is valid (or not) for transmission via one or more uplink radio resources in the RRC_CONNECTED 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 among the one or more verification conditions. The wireless device may receive one or more messages comprising the configuration parameters of a first verification condition (e.g., TAT-based verification) among the one or more verification conditions. The message may not include the configuration parameters of a second verification condition (e.g., measurement-based verification) among the one or more verification conditions. The wireless device may determine whether the timing advance value is valid (or not) based on the first verification condition. The wireless device may, for example, determine whether the timing advance value is valid (or not) based on at least the first verification condition and the second verification condition if the message includes the configuration parameters of the first verification condition (e.g., TAT-based verification) and the second verification condition (e.g., measurement-based verification).

[0196] A wireless device may determine the validity of a timing advance value based on TAT, for example, for TAT-based verification. The wireless device may receive one or more RRC messages including the value of TAT. TAT may be for a cell (and / or a TAG including the cell) in which one or more uplink radio resources are configured in the non-RRC_CONNECTED state. The wireless device may determine that a timing advance value for transmission via one or more uplink radio resources is valid, for example, when TAT is operative. The wireless device may determine that verification of a timing advance value for transmission is not based on TAT, for example, when the value of TAT is not configured (for example, the RRC message does not include the value of TAT).

[0197] Figure 20 shows an example of a resource configuration. The resource configuration may be based on one or more timers. The wireless device 2002 may transmit / send one or more uplink transmissions to the base station 2001 (e.g., at 2003). Transmitting / sending one or more uplink transmissions may be based on a valid timing advance (TA) value. Transmitting / sending one or more uplink transmissions may be during a time period when the time alignment timer (TAT) is operating. The time period during which the TAT is operating may be from a first period (e.g., 2004) when the TAT starts to a second period (e.g., 2005) when the TAT ends. One or more uplink transmissions may occur during a time period when the wireless device 2002 is in the non-RRC_CONNECTED state. The wireless device 2002 may receive from the base station 2001 one or more RRC messages including configuration parameters of uplink resources in the non-RRC_CONNECTED state. The uplink resources are available and may be scheduled and / or configured in the non-RRC_CONNECTED state. The wireless device 2002 may transmit / send uplink packets via one or more opportunities of the uplink resources, for example, when the TA value for transmission is verified (e.g., at 2003). The wireless device 2002 may determine (e.g., verify) the TA value as valid for use in transmitting one or more data packet transmissions in the non-RRC_CONNECTED state, for example, when the TAT is operating (e.g., at 2004 - 2005). The wireless device 2002 may transmit / send data via one or more uplink resources in the non-RRC_CONNECTED state, for example, when the wireless device may determine (e.g., verify) that the TA value is valid and / or when the TAT is operating. The wireless device 2002 may determine that the TA value is invalid, for example, when the TAT is not operating (and / or when the TAT ends). The wireless device 2002 may stop (e.g., it may be prohibited from performing) uplink transmissions via the uplink resources at the time when the TAT ends (e.g., 2005) and / or thereafter (e.g., at 2006).

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

[0199] One or more thresholds of the measurement may include an increase threshold and / or a decrease threshold. The increase threshold and / or the decrease threshold may indicate a threshold for a change in the measured value of at least one DL RS in the cell. The increase threshold and / or the decrease threshold may indicate a range in which the wireless device determines that the TA value is valid (for example, for use in transmission via one or more uplink radio resources in the non-RRC_CONNECTED state). The range may indicate an area of the cell (for example, a specific coverage tier in the cell, such as the central area, the cell edge area, etc.) in which the TA value can be used for transmission via one or more uplink radio resources in the non-RRC_CONNECTED state.

[0200] The increase threshold and / or the 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 or equal to the decrease 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 higher than the increase threshold and / or if the measured value of the DL RS of the cell is lower than the decrease threshold.

[0201] Figure 21A is an example of TA verification. The threshold value can be used to verify the RSRP value. The wireless device may receive one or more messages (e.g., RRC message) including an increase threshold value and / or a decrease threshold value. The increase threshold value and / or the decrease threshold value may be the absolute value of the threshold value (e.g., in dBm and / or any other measurement unit). The TA value can be used for transmission on one or more radio resources in the non-RRC_CONNECTED state, for example, when the measured value (e.g., RSRP) is within the RSRP range indicated by the increase threshold value and / or the decrease threshold value. The wireless device may determine that the TA value is valid, for example, when the measured value (e.g., RSRP) is less than the increase threshold value and / or greater than (or equal to) the decrease threshold value. The wireless device may determine that the TA value is valid, for example, when the measured value (e.g., RSRP) is higher than (or equal to) the increase threshold value and / or lower than the decrease threshold value.

[0202] The increase threshold value and / or the decrease threshold value may indicate a value in dB units, for example, for TA verification. The wireless device may determine that the TA value is valid, for example, when the measured value of the DL RS of the cell does not increase beyond the increase threshold value. The wireless device may determine that the TA value is valid, for example, when the measured value of the DL RS of the cell does not decrease beyond the decrease threshold value. The wireless device may determine that the TA value is invalid, for example, when the measured value of the DL RS of the cell increases beyond the increase threshold value and / or when the measured value of the DL RS of the cell decreases beyond the decrease threshold value. The wireless device may determine how much the measured value has changed (e.g., not increased and / or not decreased) based on one or more reference measurement values. The one or more reference measurement values may include one or more measurement values performed for the last (e.g., most recent) TA verification. The last TA verification may be performed by the wireless device for transmission via one or more uplink radio resources in the non-RRC_CONNECTED state.

[0203] FIG. 21B shows an example of TA verification. TA verification can be based on relative thresholds. The wireless device can receive one or more messages (e.g., RRC messages) including an increase threshold and / or a decrease threshold. The increase threshold and / or the decrease threshold can be a value of the threshold relative to a reference measurement value (e.g., in dB and / or any other measurement unit). The wireless device can compare the measurement value with the reference measurement value, for example, when determining whether the TA value used for transmission is valid. The wireless device can determine that the TA value is valid, for example, if the measurement value of the DL RS of the cell does not increase beyond the increase threshold and / or if the measurement value of the DL RS of the cell does not decrease beyond the decrease threshold. The wireless device can determine that the TA value used for transmission via one or more radio resources in the non-RRC_CONNECTED state is valid, for example, if the measurement value of the DL RS of the cell increases beyond the increase threshold and / or if the measurement value of the DL RS of the cell decreases beyond the decrease threshold.

[0204] FIG. 22 shows an exemplary geographical view of a measurement value change related to one or more thresholds, for example, a first threshold and / or a second threshold. The distance between cell 2201 and wireless device 2202 and the measurement value of the signal strength (e.g., RSRP) of the DL RS transmitted from cell 2201 may have an inverse proportional relationship. The greater the distance between cell 2201 and wireless device 2202, the smaller the measurement value (e.g., RSRP) of the DL RS. The measurement value may become larger, for example, when wireless device 2202 gets closer to cell 2201. Wireless device 2202 may determine that the TA value is invalid for use in transmission, for example, when the measurement value (and / or the change in the measurement value) is greater than a first threshold (e.g., an increase threshold, a ceiling threshold, an upper limit threshold, etc.). The measurement value may become smaller, for example, when wireless device 2202 moves away from cell 2201. Wireless device 2202 may determine that the TA value is invalid for use in transmission when the measurement value of the received signal strength (and / or the change in the measurement value) is sometimes less than a second threshold (e.g., a decrease threshold, a floor threshold, a lower limit threshold, etc.). Wireless device 2202 may determine that the TA value is valid, for example, when wireless device 2202 moves around and the distance from cell 2201 is maintained within a range that satisfies a condition that the measurement value (e.g., the measured RSRP value) is equal to or greater than the second threshold but equal to or less than the first threshold. The measurement value (and / or the change in the measurement value) may be equal to or greater than the second threshold and equal to or less than the first threshold, for example, for the wireless device to use a valid TA.

[0205] A wireless device may receive one or more messages including an increase threshold and a decrease threshold. The wireless device may use the increase threshold and / or the decrease threshold for TA verification. The wireless device may receive one or more messages including one of the increase threshold and / or the decrease threshold. The 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 threshold and / or the decrease threshold may be absent in one or more messages. The wireless device may receive a message not including field values for the increase threshold and the decrease threshold. The wireless device may determine that TA verification is not based on measurement values (e.g., RSRP, RSRP, and / or RSSI). TA verification based on a change in cell measurement values (e.g., RSRP, RSRP, and / or RSSI) may not be applicable, for example, if the increase threshold and / or the decrease threshold are not configured.

[0206] 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 transmitting or in response to transmitting data via one or more uplink radio resources. The wireless device may receive one or more messages (e.g., RRC message) indicating the RNTI and / or the size of the response window (e.g., exemplary parameter name: ResponseWindowTimer). The response window may start from a reference time associated with transmitting / data transmission via one or more uplink radio resources. The reference time may include a transmission time interval (e.g., frame, subframe, slot, and / or symbol) in which the wireless device may transmit data via one or more uplink radio resources. The reference time may include the end of the corresponding PUSCH transmission (e.g., transmission of data via 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 via one or more uplink radio resources). The reference time may include a time offset (e.g., pre-defined or RRC-configured). The reference time may include a subframe (or slot) including the addition of the time offset to the end of the corresponding PUSCH transmission. The reference time may include the first PDCCH opportunity from the addition of the time offset to the end of the corresponding PUSCH transmission.

[0207] A wireless device may receive a control message (e.g., DCI) via PDCCH during a time window (e.g., when the ResponseWindowTimer is active). The received control message (e.g., DCI) may be CRC scrambled by the RNTI received by the wireless device for transmission over one or more radio resources in the non-RRC_CONNECTED state. The control message (e.g., DCI) may include an uplink grant for retransmission of data. The wireless device may start and / or resume a time window (e.g., ResponseWindowTimer) based on receiving the uplink grant (e.g., after receiving it, or in response to receiving it). The time window may start and / or resume 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 resume 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 response (e.g., L1 ACK) for data transmission over one or more radio resources in the non-RRC_CONNECTED state. The wireless device may decide to stop the time window (e.g., ResponseWindowTimer) and / or may decide that data transmission over one or more radio resources was successful. The control message (e.g., DCI) may include a downlink allocation of a PDSCH containing a MAC PDU. The wireless device may decide to stop the time window (e.g., ResponseWindowTimer) and / or may decide that data transmission over one or more radio resources was successful, for example, if the wireless device successfully decodes the MAC PDU. The control message (e.g., DCI) may indicate a failure of data transmission (e.g., fallback). The wireless device may decide to stop the time window (e.g., ResponseWindowTimer) based on receiving a control message indicating a failure (e.g., fallback), for example, after receiving it, or in response to receiving it).A wireless device may determine that data transmission via one or more wireless resources has failed, for example, based on receiving a control message indicating a failure (e.g., fallback), such as after receiving it or in response to receiving it. The wireless device may initiate a random access procedure, for example, based on receiving a control message indicating a failure (e.g., fallback), such as after receiving it or in response to receiving it. The wireless device may initiate a random access procedure, for example, based on receiving a control message indicating a failure (e.g., fallback), such as after receiving it or in response to receiving it. The wireless device may determine that a time window (e.g., ResponseWindowTimer) has ended. The wireless device may determine, based on the end of the time window (e.g., after ending or in response to ending), that a preconfigured uplink grant has been skipped and / or that a PUR transmission has failed.

[0208] A wireless device and / or a base station may use a HARQ operation and / or process for one or more retransmissions of uplink transmissions in a non-RRC_CONNECTED state. The wireless device may transmit / send data packets via one or more uplink radio resources configured for a non-RRC_CONNECTED state (e.g., as shown / described with respect to FIG. 17). The wireless device may monitor the PDCCH, for example, based on (e.g., in response to) transmitting / sending data packets during a time period when the RRC state is maintained as the non-RRC_CONNECTED state. The wireless device may receive DCI indicating an uplink grant for retransmission of the data packet via the PDCCH. The uplink grant may indicate one of the one or more uplink radio resources as an uplink radio resource for retransmission. The uplink grant may indicate an uplink radio resource that may be independent of (e.g., allocated separately from) the one or more uplink radio resources for retransmission. The wireless device may receive an instruction (e.g., a different type of DCI) indicating to perform an RA procedure, for example. The wireless device may receive an instruction (e.g., a different type of DCI) indicating to perform an RA procedure, for example, instead of receiving an uplink grant. The instruction may indicate a failure of transmission of the data packet. The wireless device may switch / transition to the RRC_CONNECTED state by starting and / or performing an RRC connection setup procedure and / or an RRC resume procedure, for example. The wireless device may start (and / or perform) an RRC connection setup procedure and / or an RRC resume procedure based on the RA procedure. The wireless device may start the RA procedure based on receiving an instruction (e.g., indicating that the wireless device performs the RA procedure). The wireless device may start the RA procedure based on receiving a paging message (e.g., indicating that the wireless device performs the RA procedure) and / or based on arrival of an uplink packet. The one or more uplink radio resources configured for a non-RRC_CONNECTED state may not be used during a time period when the wireless device is in the RRC_CONNECTED state.A wireless device may not transmit (and / or may stop transmitting) data packets via one or more uplink radio resources, for example, when the RRC state is RRC_CONNECTED. 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 one or more uplink radio resources configured for a non-RRC_CONNECTED state and / or based on the RRC state being switched / transitioned to the RRC_CONNECTED state (e.g., thereafter, or in response thereto). The wireless device may suspend an uplink grant indicating one or more uplink radio resources based on one or more uplink radio resources configured for a non-RRC_CONNECTED state and / or based on the RRC state being switched / transitioned to the RRC_CONNECTED state (e.g., thereafter, or in response thereto).

[0209] A wireless device may send / transmit one or more messages (e.g., an RRC message such as a 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 a non-RRC_CONNECTED state (e.g., an RRC_INACTIVE state and / or an RRC_IDLE state). The wireless device may initiate a procedure, e.g., a wireless device startup procedure, to send / transmit the message. The wireless device may send / transmit one or more messages based on receiving a request from the base station for a procedure initiated by the base station, e.g., after receiving it or in response to receiving it. The wireless device may send / transmit one or more messages during a time period when the wireless device is in any RRC state (e.g., RRC_CONNECTED, RRC_INACTIVE, and / or RRC_IDLE). The wireless device may send / transmit a message during a time period when the wireless device is in a particular RRC state. The wireless device may send / transmit a message during a time period when the wireless device is in a non-RRC_CONNECTED state. The wireless device may send / transmit one or more messages during a time period when the wireless device is in an RRC_CONNECTED state. The one or more messages may indicate data traffic information. The one or more messages may indicate the number / amount of opportunities of one or more uplink radio resources in a non-RRC_CONNECTED state, e.g., an exemplary parameter (e.g., requestedNumOccasions). The one or more messages may indicate the periodicity of one or more uplink radio resources in a non-RRC_CONNECTED state, e.g., an exemplary parameter (e.g., requestedPeriodicity). The one or more messages may indicate the TB size of a data packet transmitted / sent via one or more uplink radio resources in a non-RRC_CONNECTED state, e.g., an exemplary parameter (e.g., requestedTBS).One or more messages may indicate a time offset for one or more uplink radio resources in a non-RRC_CONNECTED state, e.g., an exemplary parameter (e.g., requestedTimeOffset). The wireless device may not receive (e.g., does 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 uplink data transmission via one or more uplink radio resources in a non-RRC_CONNECTED state.

[0210] The wireless device may be configured using the operating band of the cell for transmission in a non-RRC_CONNECTED state. The operating band for transmission may include the carrier bandwidth. The operating band may include the DL band and / or the UL band. The operating band for transmission may include a BWP. The BWP may include a DL BWP (e.g., DL band) and / or a UL BWP (e.g., UL band). The wireless device may receive one or more messages (e.g., an RRC message and / or an RRC release message) including a configuration of the operating band for transmission / reception in a non-RRC_CONNECTED state in the cell. The message may indicate a configuration based on the number / amount of RBs (and / or PRBs) and the frequency position (e.g., the location of the center frequency). The configuration may indicate the numerology (e.g., subcarrier spacing) used in the operating band. The configuration may indicate separate numerologies (e.g., subcarrier spacing) for the DL band (e.g., DL BWP) and the UL band (e.g., UL BWP). The numerologies (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.

[0211] One or more messages may indicate the position and range of the operating band (e.g., start, size, and / or center frequency and bandwidth, etc.). The position and / or range of the operating band (e.g., start, size, and / or center frequency and bandwidth, etc.) may be indicated / defined with respect to a resource unit (e.g., RB and / or PRB), for example, as a multiple of the resource unit. The position and / or range of the operating band may be at least a part of one carrier of a cell. One or more messages may indicate the position and / or range of the operating band based on the frequency offset and bandwidth with respect to the center frequency of the carrier bandwidth of the cell. One or more messages may indicate the position and range of the operating band based on the frequency offset with respect to the center frequency (e.g., initial BWP) where the synchronization signal detected by the wireless device is located and the bandwidth of the operating band.

[0212] One or more messages may indicate the numerology information (e.g., μ and / or subcarrier spacing) used in the operating band. The wireless device may determine the RE structure from the numerology information. The message may include configuration parameters of a control channel (e.g., PDCCH and / or PUCCH), a data channel (e.g., PDSCH and / or PUSCH), and / or a reference signal (SSB, CSI-RS, and / or SRS). One or more messages may indicate the frequency position of a control channel, a data channel, and / or a reference signal based on the frequency offset with respect to a reference position within the operating band. The reference position may be the 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 non-RRC_CONNECTED state may be allocated to a start point (e.g., using the frequency offset from the reference position) that includes a size indicated / defined with respect to the number of RBs (and / or PRBs). The wireless device may determine the position and / or size of a control channel, a data channel, and / or a reference signal based on the determined RE structure.

[0213] One or more radio resources in the non-RRC_CONNECTED state may be allocated in an operating band that includes one or more sub-bands (e.g., BWP). One or more radio resources in the non-RRC_CONNECTED state may be allocated to a specific sub-band within the operating band. One or more messages that a wireless device may receive may indicate an operating band that includes one or more sub-bands (e.g., BWP). One or more messages may indicate one or more sub-bands having / using separate positions (e.g., with respect to frequency position), sizes (e.g., with respect to bandwidth), and / or numerologies (e.g., with respect to sub-carrier spacing). The RE structure for configuring one or more sub-bands may be different 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, e.g., with respect to frequency position and numerology (e.g., sub-carrier 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 about the operating band (and / or sub-bands) configured in the DL band. The wireless device may transmit / send UL control (e.g., PUCCH) and / or UL data (e.g., transport blocks via PUSCH) based on information about the operating band (and / or sub-bands) configured in the UL band. One or more radio resources in the non-RRC_CONNECTED state may be allocated per sub-band. The frequency position and / or size of one or more radio resources may be related to the sub-band.

[0214] In the case of transmission via one or more radio resources in the non-RRC_CONNECTED state, the base station may transmit / send one or more messages (e.g., RRC messages) to the radio device to configure configuration parameters. The configuration parameters include the antenna port used for transmission via one or more radio resources in the non-RRC_CONNECTED state, the DMRS configuration, configuration and / or pre-configured permission timer value (e.g., the configured and / or pre-configured permission timer may be a multiple of the period) used for transmission via one or more radio resources in the non-RRC_CONNECTED state, the frequency domain resource allocation, the frequency hopping configuration (e.g., intra-slot frequency hopping and / or inter-slot frequency hopping, and if the field does not exist, the frequency hopping may not be configured), e.g., the frequency hopping offset used when the frequency hopping is enabled, the MCS table for which the radio device may use transmission via one or more radio resources in the non-RRC_CONNECTED state for PUSCH transmission (e.g., PUSCH transmission with and / or without transform precoding), e.g., if the field is absent, the radio device may determine a pre-defined MCS (e.g., qam64, qam256, etc.), the MCS table, the modulation order, code rate, and / or TB size of the transmission via one or more radio resources, the number / quantity of HARQ processes configured for transmission via one or more radio resources in the non-RRC_CONNECTED state, the uplink power control parameters for the transmission via one or more radio resources, e.g., the indicator and / or index of the closed-loop uplink power control, one or more reference power values (e.g., p0), and / or the path loss scaling value (e.g., Alpha), the periodicity of one or more radio resources, e.g., the valid periodicity value may be determined (e.g., pre-defined) based on the numerology (e.g., subcarrier spacing), and / or the periodicity may be an absolute time value, and / or may be defined with respect to the TTI (symbol, slot, subframe, system frame, and / or any combination thereof), the periodicity.RBG size for PUSCH transmission via one or more radio resources, redundancy version (RV) sequences (e.g., [0 2 3 1], [0 3 0 3]) for transmission via one or more radio resources, number / amount of repetitions of transmission via one or more radio resources, activation type indicator indicating whether / if an additional activation message (e.g., DCI, MAC CE, and / or RRC) is required to activate one or more radio resources (e.g., as described / illustrated with respect to FIGS. 18A and / or 18B), SRS resource indicator indicating the SRS resources used, time domain allocation indicating a start symbol (e.g., start symbol number (or symbol offset) S used to determine the Nth uplink grant) and a length L (e.g., the value of the time domain allocation can be a combination of a start symbol and a length), PUSCH mapping type for transmission via one or more radio resources, time domain offset defined for a time reference (e.g., SFN = 0 and / or timeReferenceSFN), and / or an indicator indicating whether the beta offset value is configured dynamically or semi-statically, where the beta offset value can be used to determine uplink power and / or UCI multiplexing for PUSCH transmission via one or more radio resources, and may include one or more fields indicating at least one of the indicators.,

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

[0216] A specific BWP may include the initial BWP. The DL BWP of a specific BWP may include the initial DL BWP. The UL BWP of a specific BWP may include the initial UL BWP. A specific BWP may be configured separately from the initial BWP. The DL BWP of a specific BWP may be different from the initial DL BWP. The UL BWP of a 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 related to the transmission via one or more radio resources (e.g., ACK, NACK, and / or fallback response for the transmission via one or more radio resources), and / or the PDSCH (e.g., RRC response for the RRC message transmitted / transmitted via one or more radio resources) may be configured with the DL BWP. The PUCCH related to the transmission via one or more radio resources (e.g., ACK and / or NACK response for the PDSCH) and / or the PUSCH (e.g., data via one or more radio resources) may be configured with the UL BWP. The wireless device may determine that a specific BWP (e.g., DL BWP and / or UL BWP) includes the initial BWP, and / or that the specific BWP is the initial BWP (e.g., the initial DL BWP and / or the initial UL BWP, respectively). For example, if a field indicating the configuration of a specific BWP (e.g., frequency position, bandwidth, and / or numerology (e.g., subcarrier spacing)) (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 specific BWP (e.g., DL BWP and / or UL BWP) includes the initial BWP, and / or that the specific BWP is the initial BWP (e.g., the initial DL BWP and / or the initial UL BWP, respectively).

[0217] A particular BWP can be the last BWP (e.g., the most recent BWP) used by the wireless device in the RRC_CONNECTED state. The DL BWP of the particular BWP can be the last DL BWP (e.g., the most recent DL BWP) used by the wireless device in the RRC_CONNECTED state. The UL BWP of the particular BWP can be the last UL BWP (e.g., the most recent UL BWP) used by the wireless device in the RRC_CONNECTED state. The wireless device can switch / transition from the RRC_CONNECTED state to the non-RRC_CONNECTED state. The BWP (e.g., the last DL BWP and / or the last UL BWP) used by the wireless device in the RRC_CONNECTED state can be switched / transitioned to the switched / transitioned non-RRC_CONNECTED state. For example, if a field indicating the configuration of a particular BWP (e.g., frequency position, bandwidth, and / or numerology (e.g., subcarrier spacing)), which is different from the last BWP for example, is absent in the configuration parameters indicating one or more radio resources, the wireless device can determine that the particular BWP (e.g., the DL BWP and / or the UL BWP) is the BWP (e.g., the last DL BWP and / or the last UL BWP respectively).

[0218] A particular BWP can be configured separately from the initial BWP. The DL BWP of the particular BWP can be different from the initial DL BWP. The UL BWP of the particular BWP can be different from the initial UL BWP. One or more radio resources can be associated with the DL BWP and / or the UL BWP. The PDCCH related to the transmission via one or more radio resources (e.g., ACK, NACK, and / or fallback response for the transmission via one or more radio resources), and / or the PDSCH (e.g., RRC response for the RRC message transmitted / transmitted via one or more radio resources) can be configured with the DL BWP. The PUCCH related to the transmission via one or more radio resources (e.g., ACK and / or NACK response for the PDSCH), and / or the PUSCH (e.g., data via one or more radio resources) can be configured with the UL BWP.

[0219] FIG. 23 shows 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 BWP and / or UL BWP). The wireless device may receive one or more messages (e.g., broadcast message and / or RRC message specific to the wireless device) including configuration parameters of the initial BWP 2301 (e.g., initial DL BWP and / or initial UL BWP). The initial BWP 2301 may be used / instructed / configured for cell search and / or initial / random access. The wireless device may receive an SSB (e.g., cell-defining SSB) via the initial DL BWP. The wireless device may execute a random access procedure via the initial BWP. The wireless device may transmit / send 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 non-RRC_CONNECTED state may be configured in a BWP different from the initial BWP. The BWP may be the last BWP 2302 (e.g., the most recent BWP) that the wireless device may have used while in the RRC_CONNECTED state (e.g., before switching / transitioning to the non-RRC_CONNECTED state). The BWP (e.g., 2302) may be for transmission and / or reception for the wireless device in the non-RRC_CONNECTED state. The BWP (e.g., 2302) may include a BWP for a specific use and / or a specific type (e.g., type of data, application, size, etc.). The BWP (e.g., 2302) may include an SDT BWP (e.g., BWP for SDT). The BWP (e.g., 2302) may include the initial BWP 2201 and / or one or more other BWPs. The BWP (e.g., 2302) may include a subset of the initial BWP 2201, such as a BWP for a smaller portion of the resources (e.g., SDT resources) with respect to the resources of the initial BWP 2301. One or more radio resources for transmission may be configured in the UL BWP of the BWP. The PDCCH and / or PDSCH may be configured in the DL BWP of the BWP.A wireless device may deactivate a BWP, for example, when the RRC state of the wireless device changes (e.g., to the RRC_CONNECTED state). One or more radio resources and / or PUCCH associated with transmissions in the non-RRC_CONNECTED state may be configured in the initial UL BWP. The PDCCH and / or PDSCH associated with transmissions in the non-RRC_CONNECTED state may be configured in the initial DL BWP. One or more messages may indicate whether the BWP is configured separately from the initial BWP.

[0220] A wireless device may perform downlink and / or uplink beam management (e.g., with a base station) in the non-RRC_CONNECTED state. The 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. The downlink and / or uplink beam management may include beam failure detection and / or beam failure recovery procedures.

[0221] Indicators of reference signals in downlink and / or uplink beam management may indicate beams (e.g., TX beam and / or RX beam of a wireless device) to be used in the non-RRC_CONNECTED state. A wireless device may receive one or more messages (e.g., RRC messages) including configuration parameters of one or more radio resources in the non-RRC_CONNECTED state. The configuration parameters may indicate one or more reference signals. The one or more reference signals may include SSBs indicated / identified by SSB indexes / identifiers, CSI-RSs indicated / identified by CSI-RS indexes / identifiers (and / or CSI-RS resource indexes / identifiers). The one or more reference signals may include SRSs identified by SRS indexes / identifiers (e.g., SRS resource indexes / identifiers, SRS resource set indexes / identifiers, and / or combinations thereof). A reference signal may represent / show a specific beam. An SSB may represent / show a wide beam. A CSI-RS may represent / show a narrow beam. An SRS may represent / show the TX beam of a wireless device.

[0222] Configuration parameters within one or more messages may include an indicator indicating which reference signals are associated with which transmission (e.g., PUSCH, PUCCH, and / or SRS) and / or reception (e.g., PDCCH and / or PDSCH). The reference signals may be configured for radio link monitoring, radio link recovery, and / or transmission and / or reception in the non-RRC_CONNECTED state. The configuration parameters may include an indicator indicating which reference signals are associated with data (e.g., PDSCH) and / or control signal (e.g., PDCCH) reception in the non-RRC_CONNECTED state. The data and / or control signals may be associated with transmission via one or more radio resources in the non-RRC_CONNECTED state. Reception may be for receiving a response to the transmission (e.g., RRC response via PDSCH and / or L1 ACK / NACK / fallback via PDCCH). The indicator may include / show parameters for configuring the QCL relationship between one or more DL reference signals (e.g., SSB and / or CSI-RS) and the DM-RS ports of PDSCH, the DM-RS ports of PDCCH, and / or the CSI-RS ports of CSI-RS resources. The parameters may include one or more TCI states. 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 RSs (e.g., SSB, CSI-RS, any combination thereof), cell index / identifier, BWP index / identifier, and / or QCL relationship type (e.g., one or more large-scale properties). The indicator may be the TCI state of a specific channel configuration (e.g., PDSCH, PDCCH (e.g., CORESET)). The PDSCH and / or PDCCH (e.g., CORESET) configuration may include at least one of the one or more TCI states. The TCI state of PDSCH may indicate the QCL relationship between one or more DL reference signals (e.g., SSB and / or CSI-RS) and the DM-RS ports of PDSCH. The radio device may determine the RX beam used to receive data via PDSCH based on the TCI state (e.g., the QCL relationship of the TCI state).The TCI state of the PDCCH may indicate the QCL relationship between one or more DL reference signals (e.g., SSB and / or CSI-RS) and the DM-RS ports of the PDCCH. The wireless device may determine the RX beam used to receive control signals via the PDCCH based on the TCI state (e.g., the QCL relationship of the TCI state).

[0223] The wireless device may receive one or more messages that configure, reconfigure, update, and / or activate the 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. 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 the 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 one 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 at least a second one of at least a first one of the one or more TCI states (e.g., CORESET) used for the PDSCH and / or PDCCH.

[0224] A wireless device may receive configuration parameters including an indicator indicating which reference signals are associated with the transmission of data (e.g., PUSCH) and / or control signals (e.g., PUCCH) associated with transmission via one or more wireless resources. The indicator may include spatial relation information. The spatial relation information may be for transmission via PUSCH, PUCCH, and / or SRS. The wireless device may determine (e.g., identify / indicate) specific spatial relation information based on an index and / or identifier of the specific spatial relation information. The spatial relation information may indicate at least one of a cell index / identifier, one or more DL RSs (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 used for transmission via PUSCH and / or PUCCH based on the spatial relation information.

[0225] The indicator may include spatial relation information for a specific 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 piece of spatial relation information. The PUCCH configuration may include at least one piece of spatial relation information. The spatial relation information for PUSCH may be different from that of PUCCH. The spatial relation information for PUSCH may be the same as that of PUCCH. The spatial relation information for PUSCH and PUCCH may be configured separately and / or independently. There may be one or more pieces of spatial relation information applied to (and / or used for) PUSCH and PUCCH.

[0226] The wireless device may determine the antenna port and / or precoder used for PUSCH based on the spatial relation information of PUSCH. The wireless device may receive one or more messages including configuration parameters for transmission via one or more radio resources in the non-RRC_CONNECTED state. The configuration parameters (e.g., SRS resource indicator) may indicate the SRS resources of the SRS resource set. The SRS resources may include spatial relation information. The wireless device may determine to use the same antenna port as the SRS port of the SRS resource for transmission via one or more radio resources. The wireless device may transmit / send data via one or more radio resources using the same antenna port based on the determination.

[0227] The wireless device may determine one or more antenna ports and / or precoders used for the PUCCH based on the spatial relation information of the PUCCH. The wireless device may receive one or more messages including the configuration parameters of the PUCCH in the non-RRC_CONNECTED state. The wireless device may transmit / send uplink control signals via the PUCCH for SR transmission and / or measurement reporting, and for HARQ feedback (e.g., ACK or NACK) to the PDSCH in the non-RRC_CONNECTED state. The configuration parameters (e.g., PUCCH spatial relation information) may indicate spatial settings (e.g., precoder and / or spatial region filter) for PUCCH transmission and / or parameters for PUCCH power control. The wireless device may determine a spatial region filter used for receiving the DL RS indicated by the spatial relation information for PUCCH transmission in the non-RRC_CONNECTED state. The wireless device may transmit / send the PUCCH using the same spatial region filter as that for receiving the SSB of the cell when, for example, the spatial relation information for the PUCCH includes the SSB index / identifier of the SSB. The wireless device may transmit / send the PUCCH using the same spatial region filter as that for receiving the CSI-RS of the cell when, for example, the spatial relation information for the PUCCH includes the CSI-RS index / identifier (e.g., NZP-CSI-RS resource index / identifier) of the CSI-RS. The wireless device may transmit / send the PUCCH using the same spatial region filter as that for transmitting the SRS for the cell and / or UL BWP when, for example, the spatial relation information for the PUCCH includes the SRS index / identifier of the SRS (e.g., SRS resource).

[0228] The wireless device may receive one or more messages that can configure, reconfigure, update, and / or activate spatial relation information of 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 spatial relation 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 spatial relation 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 one or more spatial relation 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 spatial relation 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 one of one or more spatial relation information. A third control message (e.g., an RRC message, MAC CE, and / or DCI) that the wireless device may receive may indicate at least a second one of at least a first one of one or more spatial relation information used for PUSCH, PUCCH, and / or SRS.

[0229] FIG. 24 shows an example of beam management. The beam management may include beam management for transmission and / or reception in the non-RRC_CONNECTED state. The wireless device 2402 may receive from the base station 2401 one or more messages including one or more configuration parameters 2403 for transmission / reception in the non-RRC_CONNECTED state. The one or more configuration parameters may indicate the configuration of radio resources for PUSCH, PDCCH, PDSCH, and / or PUCCH used in the non-RRC_CONNECTED state (e.g., RRC_INACTIVE state 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 the non-RRC_CONNECTED state. 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 2404, the wireless device 2402 may transmit / data via one or more radio resources (e.g., PUSCH) in the non-RRC_CONNECTED state using the first beam. The wireless device 2402 may start monitoring the PDCCH using the third beam (e.g., after 2404). At 2405, the wireless device 2402 may receive DCI including a downlink assignment for PDSCH via the PDCCH. At 2406, the wireless device 2402 may receive the PDSCH using the fourth beam. At 2407, the wireless device may transmit / transmit HARQ feedback (e.g., ACK or NACK) using the second beam via the PUCCH. The base station 2401 may receive and / or transmit / data using different beams and / or the same beam, e.g., the first beam for PUSCH reception, the second beam for PDCCH transmission, the third beam for PDSCH transmission, and / or the fourth beam for PUCCH reception.The wireless device 2402 may receive one or more other 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 PUSCH, PDCCH, PDSCH, and / or PUCCH.

[0230] Multiple beams may be used, for example, in multi-beam operation. A cell (e.g., the cell of base station 2401) may transmit / send multiple DL RSs (e.g., multiple SSBs, CSI / RS, etc.) using multiple beams (e.g., the TX beams of the cell). One or more radio resources for use in a non-connected state (e.g., non-active state, idle state, and / or non-RRC_CONNECTED state) may be configured in the cell. One or more radio resources may be configured using multiple beams. One or more channels (e.g., PDCCH, PDSCH, PUSCH, and / or PUCCH) for transmission and / or reception in a non-connected state may be associated with a first beam among the multiple beams. The wireless device 2402 may receive a message (e.g., an RRC message, MAC CE, DCI, and / or any combination thereof) including one or more radio resource configuration parameters 2403 indicating the association between one or more channels and the first beam. The one or more radio resource configuration parameters 2403 may indicate that the beam configuration of the channel (e.g., TCI state and / or spatial relation information) includes a first DL RS among the multiple DL RSs. The first DL RS may represent and / or indicate the first beam, as shown in FIG. 24. One of the multiple DL RSs may be associated with one or more channels (e.g., PDCCH, PDSCH, PUSCH, and / or PUCCH). The wireless device 2402 may determine the antenna port and / or precoder (e.g., spatial domain filter) used for transmission and / or reception performed via the channel based on the association. The wireless device 2402 may determine the antenna port and / or precoder (e.g., spatial domain filter) for receiving, for example, the first DL RS.

[0231] Wireless device 2402 can perform one or more beam block detection and / or beam block recovery procedures while in a disconnected state. The beam block detection and / or beam block recovery procedures may each be referred to as a wireless link monitoring and / or link recovery procedure, respectively. Wireless device 2402 can determine beam block detection via a wireless link monitoring procedure. Wireless device 2402 can perform a beam block recovery procedure to determine a better beam as a link recovery procedure. Wireless device 2402 can perform beam block detection and / or beam block recovery procedures in relation to a cell that can be a cell composed of one or more uplink radio resources while wireless device 2402 is in a disconnected state.

[0232] Wireless device 2402 may receive a message (e.g., an RRC message) containing one or more configuration parameters 2403 of one or more radio resources of a cell, for example, before transitioning to a disconnected state and / or while in a disconnected state (e.g., during the disconnected state). The one or more configuration parameters 2403 may indicate one or more reference signals of the cell. The one or more reference signals may include one or more reference signals of the cell, for example, an SSB identified by an SSB index / identifier of the cell, or a CSI-RS identified by a CSI-RS index / identifier (and / or CSI-RS resource index / identifier) of the cell. 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 signal may indicate a specific beam used for cell beam obstruction detection and / or beam obstruction recovery procedures. The SSB may represent and / or indicate a wide beam of the cell, the CSI-RS may represent and / or indicate a narrow beam of the cell, and the SRS may represent and / or indicate a TX beam of the wireless device 2402. The wireless device 2402 may determine a reference signal associated with a specific channel as a reference signal used for beam obstruction detection and / or beam obstruction recovery procedures. The specific channel may include the PDCCH of the cell. The specific channel may include one or more uplink radio resources (e.g., PUSCH) used for uplink transmission during a disconnected state (e.g., an inactive state, an idle state, and / or a non-RRC-CONNECTED state) / in a disconnected state.

[0233] One or more configuration parameters 2403 within the message may include an indicator indicating which reference signals are associated with cell radio link monitoring (e.g., beam failure detection procedure) and / or cell link recovery (e.g., beam failure recovery procedure). The radio link monitoring and / or link recovery may be for transmission and / or reception in the non-connected state / during the non-connected state. The reference signal configured for radio link monitoring may be referred to as radio link monitoring RS and / or beam failure detection resource (or, DL RS). The wireless device 2402 may determine beam failure detection of the cell's beam, for example, based on monitoring (and / or measuring) the beam measurement quantity (e.g., RSRP, RSRQ, RSSI, BLER, etc.) of the reference signal configured for radio link monitoring. One or more reference signals may be configured for radio link recovery. The one or more reference signals configured for radio link recovery may be referred to as candidate beam RS and / or candidate resource. The wireless device 2402 may select / indicate one of the reference signals configured for radio link recovery as a candidate beam for recovering the beam-to-link. The wireless device 2402 may determine one of the reference signals, for example, based on the beam measurement quantity (e.g., RSRP, RSRQ, RSSI, BLER, etc.) of the reference signal configured for radio link recovery.

[0234] The wireless device 2402 may execute a beam failure detection procedure after receiving, or in response to receiving, an RRC message (e.g., an RRC release message) including, for example, the configuration parameters 2403 of the cell's beam failure detection procedure. The wireless device 2402 may determine, based on the beam failure detection procedure, whether the current beam (e.g., DL RS) used for at least one of the cell's transmission and / or reception is in a normal operating state. The wireless device 2402 may detect a beam failure, for example, if the current beam is not in a normal operating state (e.g., detect the number / quantity of beam failure instances over a certain time period). The wireless device 2402 may detect and / or determine a beam failure associated with at least one configured beam (e.g., DL RS) of the cell. At least one configured beam (e.g., DL RS) may be used for transmission (e.g., PUSCH and / or PUCCH) via one or more uplink radio resources of the cell during / while in a disconnected state (e.g., a non-active state, an idle state, and / or a non-RRC_CONNECTED state). At least one configured beam (e.g., DL RS) may be used for reception from the cell via PDCCH and / or PDSCH while in a disconnected state. A beam failure may involve at least one configured beam (e.g., DL RS) failing. The wireless device 2402 may determine a beam failure on / of at ...

Claims

1. A method comprising: receiving, by a wireless device in a Radio Resource Control (RRC) connected state, a release message indicating a plurality of configured uplink resources, wherein the release message indicates transitioning from the RRC connected state to the RRC inactive state, each of the plurality of configured uplink resources being associated with a Downlink Reference Signal (DL RS) among a plurality of DL RSs, a Radio Network Temporary Identifier (RNTI) being associated with the plurality of configured uplink resources and being different from a Cell - Radio Network Temporary Identifier (C - RNTI), and a power threshold associated with time alignment verification; transitioning from the RRC connected state to the RRC inactive state based on the release message; selecting, based on a received power value of a first DL RS among the plurality of DL RSs satisfying a second threshold, a configured uplink resource associated with the first DL RS among the plurality of configured uplink resources; transmitting, by the wireless device in the RRC inactive state, a transport block via the configured uplink resource using the power threshold based on time alignment verification of the configured uplink resource; and monitoring a downlink control channel using the C - RNTI and the RNTI associated with the plurality of configured uplink resources after transmitting the transport block.

2. wherein the release message is an RRC release message; the plurality of configured uplink resources are configured by a plurality of configured grants; the method according to claim 1, wherein the plurality of DL RSs includes at least one Synchronization Signal Physical Broadcast Channel Block (SSB).

3. further comprising selecting the first DL RS, The method according to claim 1 or 2, wherein the selecting of the first DL RS is based on a determination to transmit uplink data in the RRC inactive state.

4. The method according to any one of claims 1 to 3, wherein the release message indicates the second threshold.

5. The release message indicates spatial relationship information associated with the configured uplink resource, The method according to any one of claims 1 to 4, wherein the release message indicates an association between the plurality of configured uplink resources and the plurality of DL RSs.

6. The method according to any one of claims 1 to 5, wherein the release message indicates a transmission configuration indication state associated with the configured uplink resource.

7. The method according to any one of claims 1 to 6, further comprising determining a spatial region filter associated with the first DL RS for transmitting the transport block based on the selection of the first DL RS.

8. The method according to any one of claims 1 to 7, further comprising selecting a second configured uplink resource among the plurality of configured uplink resources, which is associated with the second DL RS, based on the received power value of the second DL RS among the plurality of DL RSs satisfying the second threshold.

9. The method according to claim 8, further comprising transmitting a second transport block via the second configured uplink resource by the wireless device in the RRC inactive state.

10. Further comprising selecting, based on at least one beam obstruction associated with the first DL RS, a second DL RS associated with a second configured uplink resource among the plurality of configured uplink resources among the plurality of DL RSs, the method according to any one of claims 1 to 9.

11. The release message is The configured uplink resource associated with first spatial relation information including the first DL RS, and A second configured uplink resource associated with second spatial relation information including a second DL RS among the plurality of DL RSs, the method according to any one of claims 1 to 10.

12. Transmitting a preamble via the configured uplink resource; Receiving a response associated with the preamble; Further comprising transitioning to a second RRC connection state based on the response, the method according to any one of claims 1 to 11.

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

14. 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 release message.

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

Images