Logical channel prioritization for reporting delay information - Patents.com

Abstract

One or more methods, apparatus, computer-readable storage media, and systems for reporting delay information. One or more wireless devices may communicate with a base station in a wireless network. Logical channel configuration parameters may be used to trigger reporting procedures in the one or more wireless devices. Reports (e.g., reports of delay information) may be generated and transmitted to the base station based on the logical channel configuration parameters.

Description

[Background technology]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims the benefit of U.S. Provisional Application No. 63 / 446,119, filed February 16, 2023. The above-referenced application is incorporated herein by reference in its entirety.

[0002] In a wireless communication system, a wireless device communicates with a base station. The wireless device performs a reporting procedure to provide the base station and / or the network with information associated with communication data within the wireless device. Summary of the Invention

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

[0004] One or more wireless devices may communicate with a base station in a wireless network. Logical channel configuration parameters may be used to trigger reporting procedures in one or more wireless devices. Reports (e.g., reports of delay information and / or remaining time thresholds) may be generated based on the logical channel configuration parameters. The reports may enable one or more wireless devices to timely notify the base station of a delay budget for upload data. The base station may appropriately allocate sufficient upload resources for one or more wireless devices to transmit data efficiently (e.g., without wasting upload resources) before violating the delay budget for the upload data.

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

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

[0007] [Figure 1A] FIG. 1A illustrates an exemplary communication network. [Figure 1B] FIG. 1B illustrates an exemplary communication network. [Figure 2A] FIG. 2A illustrates an exemplary user plane. [Figure 2B] FIG. 2B illustrates an exemplary control plane configuration. [Figure 3] FIG. 3 shows an example of protocol layers. [Figure 4A] FIG. 4A illustrates an example downlink data flow for a user plane configuration. [Figure 4B] FIG. 4B illustrates an example format of a Medium Access Control (MAC) subheader within a MAC Protocol Data Unit (PDU). [Figure 5A] FIG. 5A shows an exemplary mapping of downlink channels. [Figure 5B] FIG. 5B shows an exemplary mapping of uplink channels. [Figure 6] FIG. 6 illustrates exemplary radio resource control (RRC) states and RRC state transitions. [Figure 7] FIG. 7 shows an exemplary structure of a frame. [Figure 8] FIG. 8 illustrates an exemplary resource configuration for one or more carriers. [Figure 9] FIG. 9 shows an exemplary configuration of a bandwidth portion (BWP). [Figure 10A] FIG. 10A illustrates an exemplary carrier aggregation configuration based on component carriers. [Figure 10B] FIG. 10B shows an exemplary group of cells. [Figure 11A] FIG. 11A illustrates an example mapping of one or more synchronization signal / physical broadcast channel (SS / PBCH) blocks. [Figure 11B]FIG. 11B illustrates an example mapping of one or more channel state information reference signals (CSI-RS). [Figure 12A] FIG. 12A shows an example of a downlink beam management procedure. [Figure 12B] FIG. 12B shows an example of an uplink beam management procedure. [Figure 13A] FIG. 13A shows an exemplary four-step random access procedure. [Figure 13B] FIG. 13B shows an exemplary two-step random access procedure. [Figure 13C] FIG. 13C shows an exemplary two-step random access procedure. [Figure 14A] FIG. 14A shows an example of a control resource set (CORESET) configuration. [Figure 14B] FIG. 14B illustrates an example of a control channel element to resource element group (CCE-to-REG) mapping. [Figure 15A] FIG. 15A illustrates an example of communication between a wireless device and a base station. [Figure 15B] FIG. 15B illustrates exemplary elements of a computing device that may be used to implement any of the various devices described herein. [Figure 16A] FIG. 16A shows an example of uplink and downlink signal transmission. [Figure 16B] FIG. 16B shows an example of uplink and downlink signal transmission. [Figure 16C] FIG. 16C shows an example of uplink and downlink signal transmission. [Figure 16D] FIG. 16D shows an example of uplink and downlink signal transmission. [Figure 17A] FIG. 17A illustrates a method / procedure for transmitting (eg, transmitting) delay information in a wireless communication system. [Figure 17B] FIG. 17B illustrates a method / procedure for transmitting (eg, transmitting) delay information in a wireless communication system. [Figure 18]FIG. 18 illustrates an embodiment of a logical channel prioritization (LCP) procedure in a wireless communication system. [Figure 19] FIG. 19 illustrates an exemplary embodiment of a Logical Channel Prioritization (LCP) procedure. [Figure 20] FIG. 20 shows an example of MAC CE priority (eg, logical channel priority) relative to delay information. [Figure 21] FIG. 21 illustrates an embodiment of a logical channel prioritization (LCP) procedure in a wireless communication system. [Figure 22] FIG. 22 illustrates an exemplary embodiment of a Logical Channel Prioritization (LCP) procedure. [Figure 23] FIG. 23 illustrates an example of enhanced BSR MAC CE priorities (eg, logical channel priorities). [Figure 24] FIG. 24 illustrates a method / procedure for prioritizing BSRs in a wireless communication system. [Figure 25] FIG. 25 illustrates an example of a Logical Channel Prioritization (LCP) procedure. [Figure 26] FIG. 26 illustrates an example of a Logical Channel Prioritization (LCP) procedure. [Figure 27] FIG. 27 illustrates an example of MAC CE priorities (eg, logical channel priorities) for prioritized BSRs. DETAILED DESCRIPTION OF THE INVENTION

[0008] The accompanying drawings and description provide examples. It should be understood that the examples shown and / or described in the drawings are non-exclusive and that the features shown and described may be practiced in other examples. An example is provided for the operation of a wireless communication system.

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

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

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

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

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

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

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

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

[0017] FIG. 1B shows an exemplary communication network 150. The communication network may include a mobile communication network. The communication network 150 may include, for example, a PLMN operated / managed / executed by a network operator. The communication network 150 may include a CN 152 (e.g., a 5G Core Network (5G-CN)), a RAN 154 (e.g., an NG-RAN), and / or one or more of wireless devices 156A and 156B (collectively, wireless devices 156). The communication network 150 may include one or more data networks (DNs) 170, and / or devices in the communication network 150 may communicate with one or more data networks (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 FIG. 1A.

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

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

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

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

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

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

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

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

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

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

[0028] 1A and / or 150 of FIG. 1B may include any quantity / number and / or types of devices, such as, for example, computing devices, wireless devices, mobile devices, handsets, tablets, laptops, Internet of Things (IoT) devices, hotspots, cellular repeaters, computing devices, and / or more generally, user equipment (e.g., UE). While one or more of the above types of devices may be referenced 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 networks, and other networks referenced herein, may include terrestrial networks (e.g., LTE networks, 5G networks, 6G networks), non-terrestrial networks (e.g., satellite networks), and / or other networks for wireless communication (e.g., any 3GPP network and / or any non-3GPP network). Although the apparatus, systems, and / or methods described herein may generally be described as being implemented in one or more devices (e.g., wireless devices, base stations, eNBs, gNBs, computing devices, etc.) in one or more networks, it will be understood that one or more features and steps may be implemented in any device and / or any network.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0088] The location of the SS / PBCH block in the time and frequency domains may not be known to the wireless device (e.g., when the wireless device is searching for a cell). The wireless device may monitor the carrier for a PSS, for example, to find and select a cell. The wireless device may monitor a frequency location within the carrier. If the wireless device does not find a PSS after a period of time (e.g., 20 milliseconds), for example, the wireless device may search for a PSS at a different frequency location within the carrier. The wireless device may search for a PSS at a different frequency location within the carrier, for example, as indicated by a synchronization raster. If the PSS is found at a location in the time and frequency domains, the wireless device may determine the location of the SSS and PBCH, respectively, for example, based on the known structure of the SS / PBCH block. The SS / PBCH block may be a cell-defined SS block (CD-SSB). 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0136] DCI messages may be used for various purposes. The purpose may be indicated by the type of RNTI used to scramble the CRC parity bits. A DCI with the CRC parity bits scrambled with the Paging RNTI (P-RNTI) may indicate paging information and / or system information change notification. The P-RNTI may be predefined as "FFFE" in hexadecimal. A DCI with the CRC parity bits scrambled with the System Information RNTI (SI-RNTI) may indicate a broadcast transmission of system information. The SI-RNTI may be predefined as "FFFF" in hexadecimal. A DCI with the CRC parity bits scrambled with the Random Access RNTI (RA-RNTI) may indicate a Random Access Response (RAR). A DCI with the CRC parity bits scrambled with the Cell RNTI (C-RNTI) may indicate a unicast transmission of dynamic scheduling and / or a random access of PDCCH order trigger. A DCI with CRC parity bits scrambled with the Temporary Cell RNTI (TC-RNTI) may indicate contention resolution (e.g., Msg3 similar to Msg3 1313 shown in FIG. 13A). Encodings of other RNTIs configured by the base station for the wireless device include a configured scheduling RNTI (CS RNTI), transmit power control PUCCH RNTI (TPC PUCCH-RNTI), transmit power control PUSCH RNTI (TPC-PUSCH-RNTI), transmit power control SRS RNTI (TPC-SRS-RNTI), Interruption RNTI (INT-RNTI), slot format indication RNTI (SFI-RNTI), semi-persistent CSI RNTI (SP-CSI-RNTI), modulation and coding scheme Cell RNTI (MCS-C RNTI), and / or the like.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0168] The MAC entity of the wireless device may transmit one or more MAC CEs to the MAC entity of the base station. The one or more MAC CEs may include at least one of a short buffer status report (BSR) MAC CE, a long BSR MAC CE, a C-RNTI MAC CE, a configured grant confirmation MAC CE, a single-entry PHR MAC CE, a multiple-entry PHR MAC CE, a short truncated BSR, and / or a long truncated BSR. The MAC CEs may have an LCID in a MAC subheader corresponding to the MAC CE. A first MAC CE may have a first LCID in a MAC subheader that may be different from a second LCID in a MAC subheader of a second MAC CE. For example, an LCID given by 111011 in a MAC subheader may indicate that the MAC CE associated with the MAC subheader is a short truncated command MAC CE.

[0169] In carrier aggregation (CA), two or more component carriers (CCs) may be aggregated. Using CA techniques, a wireless device may simultaneously receive or transmit on one or more CCs, depending on the capabilities of the wireless device. In one embodiment, a wireless device may support CA for adjacent and / or non-adjacent CCs. CCs may be organized into cells. For example, CCs may be organized into one primary cell (PCell) and one or more secondary cells (SCells). When configured with CA, a wireless device may have one RRC connection with the network. During RRC connection establishment / re-establishment / handover, the cell providing NAS mobility information may be the serving cell. During RRC connection re-establishment / handover procedures, the cell providing security input may be the serving cell. The serving cell may be the PCell. In one embodiment, a base station may send one or more messages (e.g., one or more downlink signals) to the wireless device. The one or more messages may include one or more RRC messages, e.g., one or more RRC configuration / reconfiguration messages. For example, one or more RRC messages may include one or more configuration parameters (eg, one or more RRC configuration parameters).

[0170] The one or more configuration parameters may include configuration parameters for one or more SCells, depending on the capabilities of the wireless device. When configured with CA, the base station and / or the wireless device may use an SCell activation / deactivation mechanism to improve battery or power consumption of the wireless device. When the wireless device is configured with one or more SCells, the base station may activate or deactivate at least one of the one or more SCells. When the SCell is configured, the base station may deactivate the SCell unless the SCell state associated with the SCell is set to "activated" or "dormant." The wireless device may activate / deactivate the SCell, for example, based on (e.g., in response to) receiving an SCell activation / deactivation MAC CE.

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

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

[0173] The DCI addressed to the RNTI may include a CRC of the DCI scrambled with the RNTI. The wireless device may monitor a PDCCH addressed to (or for) the RNTI to detect the DCI. For example, the PDCCH may carry (or may be along with) the DCI. The PDCCH may not carry the DCI.

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

[0175] The wireless device may monitor one or more PDCCH candidates according to one or more configuration parameters of a search space set. For example, the search space set may include multiple search spaces (SS). The wireless device may monitor one or more PDCCH candidates in one or more CORESETs to detect one or more DCIs. Monitoring the one or more PDCCH candidates may include decoding at least one PDCCH candidate of the one or more PDCCH candidates according to a monitored DCI format. For example, monitoring the one or more PDCCH candidates may include decoding (e.g., blind decoding) DCI content of the at least one PDCCH candidate via possible (or configured) PDCCH positions, possible (or configured) PDCCH formats (e.g., the number of CCEs, the number of PDCCH candidates in a CSS set), and / or the number of PDCCH candidates in a USS, and / or the possible (or configured) DCI formats.

[0176] The wireless device may receive a C-RNTI (e.g., via one or more previous transmissions) from the base station. For example, the one or more previous transmissions may include Msg2 1312, Msg4 1314, or MsgB 1332. The wireless device may monitor one or more PDCCH candidates for DCI format 0_0 and DCI format 1_0 with a CRC scrambled by the C-RNTI in the Type1-PDCCH CSS set, for example, if the wireless device is not provided with a Type3-PDCCH CSS set or a USS set and is provided with a Type1-PDCCH CSS set.

[0177] The one or more search space sets may correspond to one or more search parameters. For example, the one or more search space sets may correspond to one or more of searchSpaceZero, searchSpaceSIB1, searchSpaceOtherSystemInformation, pagingSearchSpace, ra-SearchSpace, and C-RNTI, MCS-C-RNTI, or CS-RNTI. The wireless device may monitor one or more PDCCH candidates for DCI format 0_0 and DCI format 1_0 with a CRC scrambled by the C-RNTI, MCS-C-RNTI, or CS-RNTI in one or more search space sets in a slot in which the wireless device monitors one or more PDCCH candidates for at least DCI format 0_0 or DCI format 1_0 with a CRC scrambled by the SI-RNTI, RA-RNTI, MSGB-RNTI, or P-RNTI.

[0178] A base station may use a DCI format to transmit (e.g., transmit) downlink control information (DCI) to a wireless device. The wireless device may use the DCI format for PDCCH monitoring. Different DCI formats may include different DCI fields and / or have different DCI payload sizes. Different DCI formats may have different signaling purposes. DCI format 0_0 may be used to schedule a PUSCH in one cell. DCI format 0_1 ​​may be used to schedule one or more PUSCHs in one cell or to indicate CG-DFI (configured grant downlink feedback information) for a configured grant PUSCH, etc.

[0179] Semi-persistent scheduling (SPS) may be supported on the downlink. The wireless device may be configured with a data transmission periodicity using one or more configuration parameters (e.g., SPS-Config). Activation of semi-persistent scheduling may be performed using a PDCCH with a CS-RNTI (e.g., receiving a PDCCH transmission addressed to / by the CS-RNTI). The PDCCH may carry necessary information regarding time-frequency resources and other parameters. The HARQ process number / ID may be derived, for example, from the time when downlink data transmission begins. Upon activation of semi-persistent scheduling, the wireless device may receive downlink transmissions periodically according to the data transmission periodicity using one or more transmission parameters indicated in the PDCCH that activates semi-persistent scheduling.

[0180] In the uplink, two schemes for dynamic grant-free transmission may be supported. The two schemes may differ in how they are activated: 1) configured grant (or configured grant type 1), where the uplink grant includes one or more configuration parameters (e.g., configuredGrantConfig) to activate the grant; and 2) configured grant type 2 (or configured grant type 2), where transmission periodicity uses one or more configuration parameters (e.g., configuredGrantConfig) and L1 / L2 control signaling to activate / deactivate transmission in a manner similar to SPS. The two schemes may reduce control signaling overhead and / or delay before uplink data transmission because a scheduling request grant cycle is not required before data transmission. In a configured grant type 2 embodiment, the one or more configuration parameters may indicate / configure a preconfigured periodicity, and PDCCH activation may provide the transmission parameters. Upon receiving the activation command, the wireless device may transmit (e.g., transmit) according to the preconfigured periodicity if there is data in the buffer. Similar to configured grant type 1, a wireless device may not transmit (e.g., transmit) anything if it has no data to send. A wireless device may acknowledge activation / deactivation of configured grant type 2 by sending a MAC control element in the uplink. In either scheme, multiple wireless devices may be configured with overlapping time-frequency resources in the uplink. In this case, the network may distinguish between transmissions from different wireless devices. PUSCH resource allocation may be semi-statically configured by one or more configuration parameters (e.g., ConfiguredGrantConfig).

[0181] The wireless device may support a baseline processing time / capability. The wireless device may support additional aggressive / faster processing times / capabilities. The wireless device may report its processing capabilities (e.g., per subcarrier interval) to the base station. The PDSCH processing time may be taken into account by the wireless device to determine the first uplink symbol of the PUCCH (e.g., determined based on at least the HARQ-ACK timing K1 and one or more PUCCH resources used, including the effect of timing advance) that contains HARQ-ACK information for the PDSCH scheduled by the DCI. The first uplink symbol of the PUCCH may be determined based on the time gap (e.g., T proc,1 ) The first uplink symbol of the PUCCH carrying the HARQ-ACK information can start from symbol L1, where L1 is the time gap T after the end of the last symbol of the PDSCH. proc,1 It may be defined as the next uplink symbol with a cyclic prefix (CP) starting after.

[0182] The PUSCH preparation / processing time may be taken into account to determine the transmission time of the UL data. The wireless device may transmit (e.g., transmit) the PUSCH if the first uplink symbol of the PUSCH allocation of the transport block (including DM-RS) does not precede symbol L2. Symbol L2 may be determined by the wireless device based on at least the slot offset (e.g., K2), the SLIV of the PUSCH allocation indicated by the time domain resource allocation of the scheduling DCI. Symbol L2 is determined by the wireless device based on the length T after the end of reception of the last symbol of the PDCCH carrying the DCI scheduling the PUSCH. proc,2 The CP may be specified as the next uplink symbol with that CP, starting after the time gap with .

[0183] The wireless device may perform a logical channel prioritization (LCP) procedure when a new transmission is performed. The one or more configuration parameters may include, for example, one or more logical channel (LCH) configuration parameters (e.g., IELogicalChannelConfig) to configure the logical channel parameters. The wireless device may determine (e.g., control) scheduling of uplink data based on the one or more LCH configuration parameters, for example, for each logical channel of multiple logical channels, per MAC entity of the wireless device. For example, the one or more LCH configuration parameters may include, for example, a priority value (e.g., priority) corresponding to each logical channel of multiple logical channels, where an increasing priority value indicates a lower priority level, prioritizedBitRate (e.g., setting a prioritized bit rate (PBR)), and / or bucketSizeDuration (e.g., setting a bucket size duration (BSD)).The one or more LCH configuration parameters may indicate a mapping restriction for each logical channel of the plurality of logical channels, the one or more LCH configuration parameters may indicate an allowed subcarrier spacing for transmission of a MAC PDU / TB corresponding to a logical channel of the plurality of logical channels, and / or the one or more LCH configuration parameters may indicate a maximum PUSCH duration allowed .... The allowedPHY-PriorityIndex of one or more LCH configuration parameters may indicate the configured grant allowed for the transmission of the MAC PDU / TB, and / or the allowedPHY-PriorityIndex of one or more LCH configuration parameters may indicate the allowed PHY priority index of the dynamic grant for the transmission of the MAC PDU / TB corresponding to a logical channel among the multiple logical channels.

[0184] The wireless device may maintain one or more variables for performing the LCP procedure. For example, the one or more variables may include Bj corresponding to logical channel j of multiple logical channels. The wireless device may initialize Bj of logical channel j to zero when logical channel j is established. The wireless device may increment Bj by the product of PHR × T before each instance of the LCP procedure. T may be the time elapsed since Bj was last incremented. The wireless device may, for example, set Bj to the bucket size (e.g., PHR × BSD) if the value of Bj is greater than the bucket size. The instance (e.g., exact moment) when the wireless device updates Bj between LCP procedures may be up to the wireless device implementation, for example, as long as Bj is current at the time the grant is processed by LCP.

[0185] A wireless device for performing an LCP procedure may select one or more logical channels from a plurality of logical channels and / or allocate resources to the one or more logical channels. The wireless device may select one or more logical channels when a new transmission is to be performed. For example, the wireless device may select one or more logical channels based on a mapping constraint for each logical channel (e.g., a subcarrier spacing index, a PUSCH transmission duration, cell information, and / or a priority index) of the plurality of logical channels. The wireless device may receive uplink transmission information (e.g., a dynamic grant and / or a configured grant) indicating a subcarrier spacing index, a PUSCH transmission duration, cell information, and / or a priority index for a corresponding scheduled uplink transmission.

[0186] The wireless device may select one or more logical channels for each UL grant (e.g., a dynamic grant and / or a configured grant) that may satisfy at least one (e.g., all) of the following conditions: The set of allowed subcarrier spacing index values ​​in the allowedSCS-List, if configured, may include a subcarrier spacing index associated with the UL grant; the maxPUSCH-Duration, if configured, may be greater than or equal to the PUSCH transmission duration associated with the UL grant; the configuredGrantType1Allowed, if configured, may be set to true for an UL grant that is configured grant type 1; the allowedServingCells, if configured, may include cell information associated with the UL grant (e.g., allowedServingCells may not apply to logical channels associated with a DRB configured with PDCP overlap (e.g., CA overlap) within the same MAC entity of the wireless device if CA overlap is disabled for this DRB within this MAC entity of the wireless device); the allowedCG-List, if configured, may include a configured grant index associated with the UL grant, and / or the allowedPHY-PriorityIndex, if configured, may include a priority index associated with the dynamic UL grant.

[0187] A wireless device may maintain multiple active (e.g., activated) protocol stacks, for example, during handover and / or dual connectivity. For example, for a handover, the target wireless device (e.g., a MAC entity of the wireless device) may not select a logical channel corresponding to a non-dual active (activated) protocol stack DRB for an uplink grant received in a random access response or an uplink grant for transmission of an MSGA payload, for example, before successful completion of a random access procedure initiated for a dual active (activated) protocol stack handover.

[0188] The wireless device may allocate (and / or determine) resources to one or more logical channels when a new transmission is performed. The wireless device may allocate resources to one or more logical channels as follows: The wireless device may allocate resources to one or more logical channels selected (e.g., in accordance with the present disclosure) for UL grants with Bj>0 in decreasing order of priority (e.g., of one or more logical channels). The wireless device may allocate resources to data (e.g., all data) that may be available for transmission on a logical channel before filling the PLB of a lower priority logical channel if the PRR of the logical channel of one or more logical channels is set to a predefined specific value (e.g., infinity). The wireless device may reduce Bj by the total size of MAC SDUs provided to logical channel j of one or more logical channels. The wireless device may process one or more logical channels in decreasing order of priority.

[0189] The wireless device may determine the value of Bj as negative. The wireless device may determine which order grant to process when the wireless device is scheduled to transmit (e.g., transmit) multiple MAC PDUs simultaneously or when the wireless device receives multiple UL grants within one or more matching PDCCH opportunities (i.e., different serving cells). The wireless device may not segment an RLC SDU (or a partially transmitted / conveyed SDU or a retransmitted / retransmitted RLC PDU) if the entire SDU (or a partially transmitted / conveyed SDU or a retransmitted / retransmitted RLC PDU) fits into the remaining resources of the associated wireless device (e.g., the MAC entity of the wireless device). When the UE segments an RLC SDU from a logical channel, it may maximize the size of the segment to fill the grant of the associated wireless device (e.g., the MAC entity of the wireless device) as much as possible. The wireless device may maximize the transmission of data. A wireless device may not send (e.g., transmit) a padding BSR and / or only padding if it receives and / or has a UL grant size of 8 bytes or more while the wireless device has data available and is authorized to transmit.

[0190] A wireless device may not generate a MAC PDU for a HARQ entity if the wireless device is configured with enhancedSkipUplinkTxDynamic with a value true and the grant indicated to the HARQ entity is addressed to a C-RNTI, and / or if the wireless device (e.g., a MAC entity of the wireless device) is configured with enhancedSkipUplinkTxDynamic with a value true and the grant indicated to the HARQ entity is a configured uplink grant, and / or if the wireless device is not configured with lch-based Prioritization, and / or if there is no UCI multiplexed on this PUSCH transmission, and / or if there is no aperiodic CSI requested for this PUSCH transmission, and / or if the MAC PDU does not contain a MAC SDU, and / or if the MAC PDU contains only periodic BSRs and no data is available for any logical channel group (LCG), or if the MAC PDU contains only padding BSRs. The wireless device may not generate a MAC PDU for a HARQ entity if the wireless device is configured with skipUplinkTxDynamic with the value true and the grant indicated to the HARQ entity is addressed to the C-RNTI or is a configured uplink grant, and / or there is no aperiodic CSI requested for this PUSCH transmission, and / or the MAC PDU does not contain a MAC SDU, and / or the MAC PDU contains only periodic BSRs and no data is available for the LCG, or the MAC PDU contains only padding BSRs.

[0191] The wireless device may determine a priority for one or more logical channels. For example, the wireless device may prioritize one or more logical channels according to the following order (e.g., highest priority listed first): - data from the C-RNTI MAC CE or UL-CCCH, - a configured Grant Confirmation MAC CE or a BFR MAC CE or a multi-entry configured Grant Confirmation MAC CE; - Sidelink configured grant confirmation MAC CE, - LBT failure MAC CE, - the MAC CE of the SL-BSR that takes precedence in accordance with clause 5.22.1.6; - MAC CE of the BSR, excluding the BSR included for padding, - Single entry PHR MAC CE or multiple entry PHR MAC CE, - MAC CE for the amount (e.g., number) of guard symbols desired, - MAC CE for preemptive BSR, - MAC CE for SL-BSR, except for SL-BSR with SL-BSR priority and SL-BSR included for padding, - data from any logical channel except data from UL-CCCH; - MAC CE for recommended bitrate query - the MAC CE of the BSR, included in the padding, - MAC CE for SL-BSR included in padding.

[0192] The wireless device may determine a prioritization of the configured grant confirmation MAC CE, the multiple-entry configured grant confirmation MAC CE, and the BFR MAC CE. The wireless device may prioritize any listed MAC CE in a higher order than data from any logical channel, except for data from the UL-CCCH over transmissions of NR sidelink communications, for example.

[0193] The wireless device may multiplex the MAC CE and MAC SDU within the MAC PDU. The wireless device may not change the contents of the MAC PDU after being configured to transmit, for example, with a dynamic uplink grant (e.g., regardless of the LBT result).

[0194] The wireless device may perform a buffer status reporting (BSR) procedure to provide a base station (e.g., a serving base station) and / or the network with information regarding UL data volumes within the MAC entity of the wireless device. The wireless device may receive a message (e.g., an RRC message and / or system information) indicating values ​​of parameters of the BSR procedure.

[0195] The message may include information elements indicating values ​​of the following parameters: periodic BSR timer, retransmission BSR timer, logical channel SR delay timer, applied logical channel SR delay timer, logical channel SR mask, and / or logical channel group. For example, the logicalChannelSR-DelayTimer (e.g., logical channel SR delay timer) may have a value for the amount (e.g., number) of subframes. A value of sf20 may correspond to 20 subframes, a value of sf40 may correspond to 40 subframes, and so on. The periodicBSR-Timer (e.g., periodic BSR timer) may have a value for the amount (e.g., number) of subframes. A value of sf1 may correspond to 1 subframe, a value of sf5 may correspond to 5 subframes, and so on. The retxBSR-Timer (e.g., retransmission BSR timer) may have a value for the amount (e.g., number) of subframes. A value of sf10 may correspond to 10 subframes, a value of sf20 may correspond to 20 subframes, and so on.

[0196] The BSR configuration (e.g., BSR-config) may include a logicalChannelSR-DelayTimer, a periodicBSR-Timer, and / or a retxBSR-Timer. The BSR configuration may be per MAC entity of the wireless device. The wireless device may receive a message including a first BSR configuration of a first wireless device (e.g., a MAC entity of the wireless device) in a master (e.g., primary) cell group and / or a second BSR configuration of a second wireless device (e.g., a MAC entity of the wireless device) in a secondary cell group.

[0197] The logicalChannelSR-Mask (e.g., logical channel SR mask) may control SR triggering if a type1 or type2 configured uplink grant is configured. A value of 'true' for logicalChannelSR-Mask may indicate that SR masking is configured for this logical channel. A value of 'false' for logicalEthernetSR-mask may indicate that SR masking is not configured for this logical channel. The logicalChannelSR-DelayTimerApplied (e.g., logical channel SR delay timer applied) may indicate whether to apply a delay timer to SR transmissions for this logical channel. The value may be set to false in the message if the logicalChannelSR-DelayTimer is not in the BSR configuration (e.g., BSR-Config). The logicalChannelGroup (e.g., logical channel group) may be the ID (e.g., index and / or identifier) ​​of the logical channel group to which the logical channel belongs.

[0198] The logical channel configuration for a particular logical channel may include logicalSR-Mask, logicalChannelSR-DelayTimerApplied, and / or logicalChannelGroup. A value of 'true' for logicalChannelSR-Mask may indicate that SR masking is configured for the particular logical channel. A value of 'false' for logicalChannelSR-Mask may indicate that SR masking is not configured for the particular logical channel. logicalChannelSR-DelayTimerApplied (e.g., logical channel SR delay timer applied) may indicate whether to apply a delay timer to SR transmissions for the particular logical channel. The value of logicalChannelSR-DelayTimerApplied may be set to false in the message if logicalChannelSR-DelayTimer is not in the BSR configuration. logicalChannelGroup (e.g., logical channel group) may be the ID (e.g., index and / or identifier) ​​of the logical channel group to which the particular logical channel belongs.

[0199] Each logical channel (LC) may be assigned (e.g., associated) with a logical channel group (LCG) using logicalChannelGroup. The amount (e.g., number) of LCGs configured in a wireless device may be limited. The maximum amount (e.g., number) of configurable LCGs may be predefined and / or configured by an RRC message. The maximum amount (e.g., number) of LCGs may be 2, 4, 8, and / or any integer. The MAC entity of the wireless device may determine the amount of UL data available for a logical channel according to a data volume calculation procedure.

[0200] The wireless device may trigger a BSR when at least one of one or more events occurs. The one or more events may include a first event in which UL data becomes available to the MAC entity of the wireless device for a logical channel belonging to an LCG, and / or the UL data may belong to a logical channel with a higher priority than the priority of any logical channel belonging to any LCG that contains available UL data. The one or more events may include a second event in which UL data becomes available to the MAC entity of the wireless device for a logical channel belonging to an LCG, and / or none of the logical channels belonging to an LCG contains any available UL data, for example, when the UL data becomes available. The triggered BSR is based on the first event and / or the second event and may be referred to hereinafter as a regular BSR. The one or more events may include one in which UL resources may be allocated, and the amount (e.g., number) of padding bits is equal to or greater than the size of the buffer status report MAC CE plus its subheader, in which case the BSR is referred to hereinafter as a padding BSR. For example, the one or more events may include an event where the retxBSR-Timer expires and / or at least one of the logical channels belonging to the LCG includes UL data, in which case the BSR is hereinafter referred to as a regular BSR. For example, the one or more events may include an event where the periodicBSR-Timer expires, in which case the BSR is hereinafter referred to as a periodic BSR. For example, each logical channel may trigger a separate regular BSR, e.g., when regular BSR triggering events occur simultaneously for multiple logical channels.

[0201] The MAC entity of the wireless device may, for regular BSR, start or restart the logicalChannelSR-DelayTimer if the BSR is triggered for a logical channel for which logicalChannelSR-DelayTimerApplied has a value of true configured by higher layers (e.g., by an RRC message). The MAC entity of the wireless device, for regular BSR, may, when running, stop the logicalChannelSR-DelayTimer if the BSR is triggered for a logical channel for which logicalChannelSR-DelayTimerApplied has a value of true not configured by higher layers (e.g., by an RRC message) (e.g., logicalChannelSR-DelayTimerApplied has a value of false configured and / or logicalChannelSR-DelayTimerApplied is not present in the message).

[0202] The MAC entity of the wireless device may report a long BSR for all LCGs that have data available for transmission if multiple LCGs have data available for transmission and a MAC PDU containing a BSR is constructed for regular and / or periodic BSR. For regular and / or periodic BSR, the MAC entity of the wireless device may report a short BSR if multiple LCGs do not have data available for transmission and a MAC PDU containing a BSR is constructed, and / or if a single LCG has data available for transmission and a MAC PDU containing a BSR is constructed.

[0203] In the case of a padding BSR, the MAC entity of the wireless device may report a long BSR for one or more LCGs (e.g., all LCGs) that have data available for transmission if the amount (e.g., number) of padding bits is equal to or greater than the long BSR plus the size of its subheader. There may be cases of a padding BSR where the amount (e.g., number) of padding bits may be equal to or greater than the short BSR plus the size of its subheader and / or less than the long BSR plus the size of its subheader. The MAC entity of the wireless device may report a short BSR if multiple LCGs have no data available for transmission and a BSR is constructed, and / or if a single LCG has data available for transmission and a BSR is constructed. The MAC entity of the wireless device may report a short, shortened BSR for an LCG with data available for transmission using the highest priority logical channel if multiple LCGs have data available for transmission and a BSR is constructed, and / or if the amount (e.g., number) of padding bits is equal to the short BSR plus the size of its subheader.

[0204] The MAC entity of the wireless device may report the long and shortened BSRs of the LCGs using the logical channels that have data available for transmission in decreasing order of the highest priority logical channels (with or without data available for transmission) in each of these LCGs, and in order of LCG ID if the priorities are equal, e.g., if multiple LCGs have data available for transmission when the BSR is constructed and / or if the amount (e.g., number) of padding bits is not equal to the size of the short BSR plus its subheader.

[0205] For a BSR triggered by the expiration of the retxBSR-Timer, the wireless device (e.g., a MAC entity of the wireless device) may determine that the logical channel that triggered the BSR is the highest-priority logical channel that has data available for transmission at the time the BSR was triggered. The MAC entity of the wireless device (e.g., a buffer status reporting procedure triggered by the wireless device) may determine whether at least one BSR has been triggered and / or canceled. The wireless device may determine that at least one BSR is pending if at least one BSR has been triggered and / or canceled.

[0206] Based on (e.g., in response to) at least one BSR being pending (e.g., not being triggered and / or canceled), the wireless device may determine whether UL-SCH resources are available for a new transmission and / or whether the UL-SCH resources can accommodate the BSR MAC CE plus its subheader as a result of logical channel prioritization. The BSR MAC CE may include and / or indicate at least one BSR.

[0207] The wireless device may perform a multiplexing and assembly procedure to generate a BSR MAC CE if at least one BSR is pending (e.g., not triggered and / or canceled), if UL-SCH resources are available for a new transmission, and / or if the UL-SCH resources can accommodate the BSR MAC CE plus its subheader as a result of logical channel prioritization. The wireless device may further start or restart the periodicBSR-Timer and / or start or restart the retxBSR-Timer if at least one BSR is pending (e.g., not triggered and / or canceled), if UL-SCH resources are available for a new transmission, and / or if the UL-SCH resources can accommodate the BSR MAC CE plus its subheader as a result of logical channel prioritization. The wireless device may not start or restart the periodicBSR-Timer (e.g., may skip starting or restarting) if the generated BSR (e.g., all generated BSRs) are long or short abbreviated BSRs, if at least one BSR is pending (e.g., has not been triggered and / or canceled), if UL-SCH resources are available for new transmissions, and / or if UL-SCH resources can accommodate the BSR MAC CE plus its subheader as a result of logical channel prioritization.

[0208] The wireless device may trigger a scheduling request if at least one BSR is pending (e.g., not triggered and / or canceled). The wireless device may trigger a scheduling request if at least one BSR is pending (e.g., not triggered and / or canceled), if a regular BSR is triggered and the logicalChannelSR-DelayTimer is not running, and / or if there are no UL-SCH resources available for a new transmission. The wireless device may trigger a scheduling request if at least one BSR is pending (e.g., not triggered and / or canceled), if a regular BSR is triggered and the logicalChannelSR-DelayTimer is not running, and / or if a regular BSR is configured in an uplink grant for which the wireless device (e.g., a MAC entity of the wireless device) is configured and the logicalChannelSR-Mask is set to false and the regular BSR is triggered for a logical channel for which the logicalChannelSR-Mask is set to false. The wireless device may trigger a scheduling request if at least one BSR is pending (e.g., not triggered and / or canceled), if a regular BSR is triggered and the logicalChannelSR-DelayTimer is not running, and / or if the UL-SCH resources available for new transmissions do not satisfy the LCP mapping restrictions configured for the logical channel that triggered the BSR.

[0209] A wireless device may determine that a UL-SCH resource is available if the MAC entity of the wireless device has configured, received, and / or determined an uplink grant. A UL-SCH resource determined as available may be available for use at the time the UL-SCH resource is determined as available. A UL-SCH resource determined as available may not be available for use at the time the UL-SCH resource is determined as available. If the UL-SCH resource overlaps with other resources (e.g., SSB transmissions) and / or is invalid, a UL-SCH resource determined as available may not be available for use at the time the UL-SCH resource is determined as available.

[0210] A MAC PDU may include at least one (e.g., at most one) BSR MAC CE. If one or more BSRs are triggered by multiple events, a MAC PDU may include at least one (e.g., at most one) BSR MAC CE. A wireless device may select a BSR from one or more BSRs and / or multiplex a MAC PDU including at least one (e.g., at most one) BSR MAC CE corresponding to the selected BSR. A wireless device may select a BSR from one or more BSRs based on the priority of the one or more BSRs. A regular BSR may have priority over a padding BSR. A periodic BSR may have priority over a padding BSR.

[0211] The MAC entity of the wireless device may start or restart the retxBSR-Timer upon receiving a grant for transmission of new data (and / or retransmission of data) on the UL-SCH (e.g., any UL-SCH). The MAC entity of the wireless device may cancel one or more (e.g., all) triggered BSRs if the UL grant can accommodate pending data available for transmission (e.g., all pending data) and / or if the BSR MAC CE is not sufficient to accommodate its additional subheader. All BSRs triggered before MAC PDU assembly are canceled when the MAC PDU is sent (e.g., transmitted), and this PDU includes a long or short BSR MAC CE that includes buffer status up to (and including) the last event that triggered a BSR before MAC PDU assembly.

[0212] The wireless device may perform MAC PDU assembly at any time between the reception of the uplink grant and the actual transmission of the corresponding MAC PDU. The wireless device may trigger BSR and SR after (e.g., in response to) the assembly of a MAC PDU that may include a BSR MAC CE and / or before the transmission of this MAC PDU. The wireless device may trigger BSR and SR during the assembly of the MAC PDU.

[0213] A wireless device may trigger and / or send (e.g., transmit) a scheduling request (SR) to request UL-SCH resources for a transmission (e.g., a new transmission). The MAC entity of the wireless device may be configured with zero, one, or multiple SR configurations. An SR configuration may include a set of PUCCH resources for SRs across different BWPs and / or cells. The wireless device may receive a message (e.g., an RRC message and / or system information) indicating and / or configuring one or more PUCCH resources for SRs per BWP for a logical channel, for beam failure recovery (e.g., secondary cell beam failure recovery), and / or for consistent LBT failure recovery. The wireless device for a logical channel may receive a message (e.g., an RRC message and / or system information) indicating and / or configuring at most one PUCCH resource for SRs per BWP. The wireless device may receive a message (e.g., an RRC message and / or system information) indicating and / or configuring at most one PUCCH resource for SRs per BWP for beam failure recovery (e.g., secondary cell beam failure recovery). The wireless device may receive a message (eg, an RRC message and / or system information) indicating and / or configuring at most one PUCCH resource for SR per BWP for consistent LBT failure recovery.

[0214] Each SR configuration may correspond to one or more logical channels and / or SCell beam failure recovery and / or consistent LBT failure recovery (e.g., may be configured by an RRC message). Each logical channel, SCell beam failure recovery, and / or consistent LBT failure recovery may be mapped to zero or one SR configuration (e.g., may be configured by an RRC message). The wireless device may determine the SR configuration of the logical channel that triggered the BSR or SCell beam failure recovery or consistent LBT failure recovery as the corresponding SR configuration of the triggered SR (if such a configuration exists). The wireless device may use any SR configuration for an SR triggered by a preemptive BSR.

[0215] The wireless device may receive a message (e.g., an RRC message and / or system information). The message may include configuration parameters associated with the SR procedure. The configuration parameters for the SR procedure may include an sr-ProhibitTimer and / or an sr-TransMax. The SR configuration (e.g., each SR configuration) may include a schedulingRequestId (e.g., a scheduling request index and / or identifier), an sr-ProhibitTimer (e.g., per SR configuration), and / or an sr-TransMax (e.g., per SR configuration) of the SR configuration. The schedulingRequestId may be used to change the SR configuration and / or to indicate the SR configuration to which the logical channel is mapped in LogicalChannelConfig and the SR configuration to which the scheduling request resource is used in SchedulingRequestresourceConfig. The sr-ProhibitTimer may be a timer for SR transmissions on the PUCCH. The value of the sr-ProhibitTimer may be in milliseconds (or any time unit, such as seconds, milliseconds, etc.). The value ms1 may correspond to 1 ms, the value ms2 may correspond to 2 ms, and so on. The wireless device may decide to apply a value of 0 if the sr-ProhibitTimer field in the SR configuration is not present. sr-TransMax may be the (e.g., maximum) amount (e.g., number) of SR transmissions, for example, the wireless device may be allowed to transmit SRs. The value n4 of sr-TransMax may correspond to 4, the value n8 may correspond to 8, and so on.

[0216] The wireless device may maintain one or more variables used for the scheduling request procedure. The one or more variables may include a counter, for example, an SR_COUNTER that counts the amount (e.g., number) of triggered SRs and / or the amount (e.g., number) of triggered and / or pending SR transmissions. The wireless device may maintain an SR_COUNTER for each SR configuration. When an SR is triggered and there are no other pending SRs corresponding to the same SR configuration, the wireless device may set the SR_COUNTER of the corresponding SR configuration to 0 (or any initial value). When an SR is triggered, the wireless device may determine the SR as pending until it is canceled.

[0217] The wireless device may, for example, cancel pending SRs (e.g., all pending SRs) for BSRs triggered per the BSR procedure prior to MAC PDU assembly, and / or may stop each respective sr-ProhibitTimer, for example, when the wireless device transmits a MAC PDU that includes a long and / or short BSR MAC CE that includes buffer status up to and including the last event that triggered a BSR prior to MAC PDU assembly. The wireless device may cancel pending SRs (e.g., all pending SRs) for BSRs triggered per the BSR procedure and stop each respective sr-ProhibitTimer, for example, when the UL grant accommodates pending data that can be transmitted (e.g., all pending data).

[0218] The MAC entity of the wireless device may, for each pending SR that is not triggered according to the BSR procedure of the serving cell, cancel the pending SR and stop the corresponding sr-ProhibitTimer (e.g., if running) if this SR was triggered by a preemptive BSR procedure before MAC PDU assembly and / or a MAC PDU containing an associated preemptive BSR MAC CE is transmitted. The wireless device (e.g., the MAC entity of the wireless device) may, for each pending SR that is not triggered according to the BSR procedure of the serving cell, cancel the pending SR and stop the corresponding sr-ProhibitTimer (e.g., if running) if this SR was triggered by beam failure recovery of the SCell and / or a MAC PDU is transmitted that contains a BFR MAC CE or a shortened BFR MAC CE that contains beam failure recovery information for this SCell. The wireless device (e.g., a MAC entity of the wireless device) may, for each pending SR that is not triggered according to the BSR procedure of the serving cell, cancel the pending SR and stop the corresponding sr-ProhibitTimer (e.g., if running) if this SR is triggered by beam failure recovery of an SCell and this SCell is deactivated. The wireless device (e.g., a MAC entity of the wireless device) may, for each pending SR that is not triggered according to the BSR procedure of the serving cell, cancel the pending SR and stop the corresponding sr-ProhibitTimer (e.g., if running) if this SR is triggered by consistent LBT failure recovery of a cell (e.g., SCell), a MAC PDU is sent (e.g., transmitted), and the MAC PDU includes an LBT failure MAC CE that indicates a consistent LBT failure for this cell (e.g., SCell).For each pending SR that is not triggered according to the BSR procedure of the serving cell, the wireless device (e.g., a MAC entity of the wireless device) may cancel the pending SR and stop the corresponding sr-ProhibitTimer (e.g., if running) if this SR is triggered by a consistent LBT failure recovery of a cell (e.g., an SCell) and the triggered consistent LBT failures (e.g., all triggered consistent LBT failures) for this cell (e.g., an SCell) are canceled.

[0219] The wireless device may determine that one or more PUCCH resources are valid if they are scheduled on a BWP that is active at the time of the SR transmission opportunity. The wireless device (e.g., a MAC entity of the wireless device) may initiate a random access procedure on the cell (e.g., SpCell) and cancel the pending SR if, for each pending SR, at least one SR is pending and / or the wireless device (e.g., a MAC entity of the wireless device) does not have a valid PUCCH resource configured for the pending SR.

[0220] For each pending SR and / or for an SR configuration corresponding to the pending SR, the MAC entity may determine whether one or more first conditions for signaling an SR on one valid PUCCH resource for the SR are satisfied if at least one SR is pending, and / or if the wireless device (e.g., the MAC entity of the wireless device) has a valid PUCCH resource configured for the pending SR, and / or if the wireless device (e.g., the MAC entity of the wireless device) has an SR transmission opportunity on a valid PUCCH resource for the configured SR. The one or more first conditions may include that the sr-ProhibitTimer is not running at the time of the SR transmission opportunity and / or that the PUCCH resource for the SR transmission opportunity does not overlap with a measurement gap.

[0221] The wireless device may further check at least one of the one or more second conditions to be met to signal an SR on one valid PUCCH resource for the SR. The one or more second conditions may include a PUCCH resource (for the SR transmission opportunity) that does not overlap with either an UL-SCH resource or an SL-SCH resource. The one or more second conditions may include a condition such that the wireless device (e.g., a MAC entity of the wireless device) can perform this SR transmission simultaneously with the transmission of an SL-SCH resource. The one or more second conditions may include the following conditions: the wireless device (e.g., a MAC entity of the wireless device) is configured with UL-SCH prioritization; the PUCCH resource of the SR transmission opportunity does not overlap with the PUSCH period of the uplink grant received in the random access response or the PUSCH period of the uplink grant addressed to the temporary C-RNTI or the PUSCH period of the MSGA payload; the PUCCH resource of the SR transmission opportunity of the triggered pending SR overlaps with other UL-SCH resources; the physical layer can signal the SR with one valid PUCCH resource for the SR; the priority of the logical channel that triggered the SR is higher than the priority of the uplink grant of the UL-SCH resource that has not yet been released; and / or the priority of the uplink grant is determined. The one or more second conditions may include the following conditions: sl-PrioritizationThres and / or ul-PrioritizationThres are set, the PUCCH resources of the SR transmission opportunity of the triggered pending SR overlap with any UL-SCH resources carrying the MAC PDU, the determined priority value of the triggered SR is lower than sl-PrioritizationThres, the highest priority value of the logical channel in the MAC PDU is equal to or greater than ul-PrioritizationThres, and / or the MAC PDU is not prioritized by higher layers.The one or more second conditions may include a condition that the SL-SCH resource overlaps with a PUCCH resource of an SR transmission opportunity for a triggered pending SR, the wireless device (e.g., a MAC entity of the wireless device) cannot perform this SR transmission simultaneously with the transmission of the SL-SCH resource, and / or the transmission on the SL-SCH resource is not prioritized or the priority value of the logical channel that triggered the SR is lower than ul-PrioritizationThres (if configured). The one or more second conditions may include a condition that the SL-SCH resource overlaps with a PUCCH resource of an SR transmission opportunity for a triggered pending SR, the wireless device (e.g., a MAC entity of the wireless device) cannot perform this SR transmission simultaneously with the transmission of the SL-SCH resource, or the determined priority of the triggered SR is higher than the priority of the MAC PDU determined for the SL-SCH resource.

[0222] The wireless device may determine an SR transmission as a prioritized SR transmission if at least one of one or more first conditions is met and / or at least one of one or more second conditions is met. The wireless device may determine another overlapping uplink grant as a non-prioritized uplink grant if at least one of one or more conditions is met and / or at least one of one or more second conditions is met. The wireless device may stop the setconfiguredGrantTimer for a corresponding HARQ process of a non-prioritized uplink grant if at least one of the one or more conditions is met and / or at least one of the one or more second conditions is met and / or if the non-prioritized uplink grant is a configured uplink grant configured with autonomous Tx for which PUSCH has already started.

[0223] The wireless device may instruct the physical layer to send a signal for SR on one valid PUCCH resource for SR when at least one of one or more conditions is satisfied and / or when at least one of one or more second conditions is satisfied and / or when SR_COUNTER < sr-TransMax. The wireless device may increment SR_COUNTER by 1 and / or start sr-ProhibitTimer when at least one of one or more conditions is satisfied and / or when at least one of one or more second conditions is satisfied and / or when SR_COUNTER < sr-TransMax and / or when an LBT failure indication is not received from the lower layer. The wireless device may increment SR_COUNTER by 1 and / or may not start sr-ProhibitTimer when at least one of one or more conditions is satisfied and / or when at least one of one or more second conditions is satisfied and / or when SR_COUNTER < sr-TransMax and / or when an LBT failure indication is not received from the lower layer and / or when lbt-FailureRecoveryConfig is not configured.

[0224] When at least one of one or more conditions is satisfied and / or when at least one of one or more second conditions is satisfied and / or when SR_COUNTER ≥ sr-TransMax, the MAC entity of the wireless device notifies the RRC layer of the wireless device to release PUCCH for one or more cells (e.g., all serving cells), notifies RRC to release SRS for one or more cells (e.g., all serving cells), clears the configured downlink assignment and uplink grant, clears the PUSCH resources for semi-persistent CSI reporting, starts a random access procedure on a cell (e.g., SpCell), and / or cancels one or more pending SRs (e.g., all pending SRs).

[0225] The wireless device may determine an SR transmission as a reduced priority SR transmission if at least one of the one or more conditions is met. The wireless device may determine an SR transmission as a reduced priority SR transmission if at least one of the one or more conditions is met and / or if one or more second conditions are not met (e.g., all).

[0226] The wireless device may select which valid PUCCH resource for SR to signal to SR when the wireless device (e.g., a MAC entity of the wireless device) has multiple overlapping valid PUCCH resources for the SR transmission opportunity. The wireless device may not select which valid PUCCH resource for SR for beam failure recovery (e.g., of an Scell) to signal to SR when the wireless device (e.g., a MAC entity of the wireless device) has multiple overlapping valid PUCCH resources for the SR transmission opportunity. The wireless device may increment the SR_COUNTER once for the associated SR configuration when multiple individual SRs trigger instructions from the wireless device (e.g., a MAC entity of the wireless device) to the PHY layer to signal to SR on the same valid PUCCH resource.

[0227] The wireless device may stop an ongoing random access procedure (e.g., if any) due to a pending SR for a BSR initiated by the wireless device (e.g., a MAC entity of the wireless device) before MAC PDU assembly and for which no valid PUCCH resources are configured if the MAC PDU is sent (e.g., transmitted) using an UL grant other than the UL grant provided by the random access response or the UL grant determined for the transmission of an MSGA payload, and / or this PDU includes a BSR MAC CE that includes buffer status up to (and including) the last event that triggered a BSR before MAC PDU assembly. The wireless device may stop an ongoing random access procedure (e.g., if any) due to a pending SR for a BSR initiated by the wireless device (e.g., a MAC entity of the wireless device) before MAC PDU assembly and for which no valid PUCCH resources are configured, if the UL grant can accommodate the pending data available for transmission (e.g., all pending data).

[0228] Augmented reality (XR) can refer to all combined real and virtual environments and human-machine interactions generated by computer technology and wearables. XR can be an umbrella term for different types of reality, such as virtual reality (VR), augmented reality (AR), mixed reality (MR), and / or cloud gaming. XR applications can provide a sense of being surrounded by a virtual environment (e.g., immersion) and / or being physically and spatially located within a virtual environment (e.g., presence). The acronym XR can refer to the equipment, applications, and features used for VR, AR, cloud gaming, and / or MR, such as HMDs for VR, optical see-through glasses and camera see-through HMDs for AR and MR, and mobile devices with positional tracking and cameras. An XR device can be a wireless device that runs / uses / implements one or more XR features / applications / use cases (e.g., AR). An XR device can be a wireless device with XR equipment running one or more XR services. An XR device may send (e.g., transmit) or receive (e.g., to / from a base station) XR data / packets / traffic.

[0229] Some XR use cases (e.g., cloud gaming and / or VR) may be characterized by quasi-periodic traffic (e.g., 45 / 60 / 90 / 120 frames per second (FPS)) with possible jitter and / or non-integer periodicity. For example, frame rates for XR video vary from 30 frames per second up to 90 or 120 frames per second, with a typical minimum of 60 for VR. In some other cases, jitter may be up to several milliseconds (e.g., 4 milliseconds, 8 milliseconds, 10 milliseconds, or more, depending on the application, network latency, and / or video coding standard). XR use cases may require high data rates in the DL (e.g., for transmitting video streams and / or audio data) combined with frequent UL data (i.e., attitude / control updates or attitude information) and / or UL video streams. Both DL and UL traffic are also characterized by relatively strict packet delay budgets (PDBs). For example, the PDB for attitude / control updates may be approximately 4 milliseconds. In some applications, the PDB for DL / UL video streams may be 10 ms, 20 ms, or 30 ms. For example, the latency of the action of the angular reflex or rotational vestibulo-ocular reflex is known to be approximately 10 ms or in the range of 7-15 ms. In other embodiments, an inter-motion photon delay of less than 10-20 ms (e.g., a PDB of less than 10-20 ms) may be required.

[0230] The bitrate of an XR use case (or application) may be between 10 and 200 Mbps, depending on the frame rate, resolution, and codec efficiency. The volume of DL / UL data (or bitrate) over a traffic period (or data burst or burst of PDU sets) may vary. In a first traffic period (or data burst), the volume of the DL video stream may be a first value (e.g., 100 Mbytes), and in a second traffic period (or data burst), the volume of the DL video stream may be a second value (e.g., 50 Mbytes). A data burst may include a set of multiple PDUs (SDAP / PDCP / RLC / MAC PDUs) generated and transmitted by an application over a short period (e.g., traffic period). A data burst may include one or more PDU sets and / or one or more data packets (e.g., IP packets) and / or one or more PDSCH bundles and / or one or more PDUs from at least one PDU set. A PDU set (or PDU set or PDU set / bundle / collection) may include one or more PDUs carrying a payload of a unit of information generated at the application level (e.g., a frame or video slice for an RRM service). The PDU set information (e.g., corresponding to a PDU) may indicate / include at least one of a PDU set identifier, a starting (or earliest / starting / initial) PDU and an ending (or latest / last / ending) PDU of the PDU set, a PDU serial number (SN) of a PDU in the PDU set, a PDU set size, a PDU set importance, and / or an end of data burst indication (e.g., indicating the end of a data burst). For example, an end of data burst indication may correspond to an ending PDU. An end of data burst indication may indicate the last / final / ending / latest PDU in a data burst.

[0231] The network (e.g., base station) and / or wireless device may not know (or be able to accurately measure) the instantaneous jitter value / range and / or the volume of UL / DL traffic (e.g., within each traffic period) in advance. The network (e.g., base station) and / or wireless device may determine / measure one or more statistics / characteristics (e.g., mean, variance, probability density function, etc.) of jitter and / or the volume of UL / DL data (or bit rate) through statistical measurements (and / or AI / ML methods).

[0232] The PDU set-related assistance information (e.g., provided to the wireless device and / or the user plane of the base station via the control plane) may define / indicate one or more pieces of assistance information corresponding to the PDU set. The PDU set information and / or the PDU set-related assistance information may enable XR-aware operation of the RAN (e.g., the user plane of the base station and / or the wireless device). The PDU set-related assistance information may include PDU set QoS parameters and / or burst (or XR data or data burst or PDU set) periodicity, e.g., periodicity for quasi-periodic traffic such as 45 / 60 / 90 / 120 FPS. The PDU set QoS parameters (e.g., provided to the wireless device and / or the user plane of the base station via the control plane) corresponding to the PDU set may include at least one of the following: PDU Set Delay Budget (PSDB), PDU Set Error Rate (PSER), and / or PDU Set Integration Indicator (PSII). The PDU Set Delay Budget (PSDB) of a PDU set may indicate / define / measure the delay of a PDU set (or PDU sets) between a wireless device and the N6 termination point in the UPF. The PSDB of a PDU set may indicate the time between the reception of the first / initial / starting / earliest PDU (e.g., Start PDU) of the PDU set and the successful delivery of the last / final / ending / latest PDU (e.g., End PDU) of the PDU set. For a particular 5QI, the value of the PSDB may be the same on the UL and DL. For 3GPP access, the PSDB may be used to support the configuration of scheduling and link layer functions (e.g., setting the scheduling priority weight and HARQ target operating point). A PDU set may be considered / determined lost if the PDU set is delayed more than the PSDB (e.g., if the corresponding QoS flow does not exceed a GBR QoS flow using GFBR and / or delay-critical resource types). The PSDB of a PDU set may depend on the PDBs (e.g., minimum / maximum PDBs, etc.) of the PDUs of the PDU set.

[0233] The PDU Set Error Rate (PSER) of a PDU set may define / indicate an upper limit on the error rate of the PDU set. An upper layer (e.g., RLC / PDCP / SDAP layer) of a sender (e.g., a base station and / or a wireless device) may process the PDU set and determine whether all of the PDUs in the PDU set are successfully delivered to the upper layer (e.g., PDCP / RLC / SDAP layer) by the corresponding receiver.

[0234] The PDU Set Integration Indication (PSII) of a PDU set may define / indicate / measure whether all PDUs of the PDU set are required for use of the PDU set by the application layer. All PDUs in a PDU set may be required by the application layer that uses the corresponding information units. The application layer may still recover all or part of the information units if some PDUs of the PDU set are missing. A PDU set may include one or more data packets (e.g., IP packets) or may correspond to upper layer SDUs / PDUs (e.g., PDCP / RLC / SDAP / MAC layers).

[0235] There may be various methods, procedures, and alternatives for mapping PDU sets to QoS flows (e.g., at the NAS) and / or mapping QoS flows to DRBs (e.g., at the Access Stratum (AS)), one-to-one mapping between PDU set types and QoS flows at the NAS and one-to-one mapping between QoS flows and DRBs at the AS, one-to-one mapping between PDU set types and QoS flows at the NAS and multiplexing QoS flows on one DRB at the AS, multiplexing PDU sets on one QoS flow at the NAS and one-to-one mapping between QoS flows and DRBs at the AS, and / or N-multiplexing of PDU sets on one QoS flow at the NAS and demultiplexing PDU sets from one QoS flow on multiple DRBs at the AS. The wireless device and / or base station may map one or more PDU sets in a DRB to logical channels in a one-to-one mapping, where the PDCP layer maps one or more PDU sets to one logical channel, or in a one-to-many mapping, where the PDCP layer maps one or more PDU sets to one or more logical channels.

[0236] A wireless device (e.g., an XR device) may report / send / transmit delay information (or delay budget) of UL (pending) data (e.g., XR data / traffic including one or more PDUs or one or more PDU sets) to a base station. The delay information may include a delay budget / remaining time (e.g., PDB) of one or more PDUs. The delay information may include, for example, a PDU set delay budget (PSDB) of one or more PDU sets. By reporting / sending / transmitting the UL data delay information, the base station may be able to properly / timely schedule the wireless device to transmit the UL data before a violation of the UL data delay budget (e.g., a violation of the PDB of one or more PDUs or the PSDB of one or more PDU sets). The base station may schedule transmission of a first PDU of one or more PDUs with a smaller remaining time (e.g., and / or a smaller / narrower delay budget, e.g., 10 ms) before a second PDU of one or more PDUs with a longer remaining time (e.g., and / or a larger / longer / later delay budget, e.g., 30 ms).

[0237] The base station may configure the wireless device with one or more new BSR tables (e.g., Tables 6.2.1-2 and 6.2.1-2b, which differ from the Release 15-17 BSR tables of 3GPP® TR 38.321) and / or predefined (compressed) BSR formulas. The one or more new BSR tables (or predefined BSR formulas) may enable the wireless device to calculate / report data volume (BSR) with more precision (e.g., more refined data volume information) compared to the conventional BSR tables of 3GPP® TR 38.321 (e.g., Tables 6.2.1-2 and 6.2.1-2b). The wireless device may derive / generate / calculate an enhanced BSR report (e.g., an enhanced short / long BSR and / or an enhanced shortened BSR and / or an enhanced short / long shortened BSR, etc.) using UL pending data for a specific logical channel (e.g., one or more logical channels corresponding to an XR stream / flow and / or one or more PDU sets or one or more PDUs) based on the new BSR table or a predefined BSR formula. The enhanced BSR report may include data volume information for a first set of logical channels (e.g., based on the conventional BSR table and / or the new BSR table and / or a predetermined BSR formula) and delay budget / information (or remaining time) for a second (or first) set of logical channels. Using the enhanced BSR report, the base station may more efficiently / timely allocate UL resources (e.g., time and frequency) to wireless devices for transmission of UL data.

[0238] Without timely notifying the base station about delay information (e.g., remaining time) of the UL pending data, the base station may schedule the wireless device to transmit (e.g., transmit) the first PDU after violating the delay budget for the first PDU, which may reduce quality of service (e.g., increase the PSER of the PDU set). The improvements described herein for at least some procedures (e.g., LCP procedures in the wireless device) may enable the wireless device to timely notify the base station about the delay budget for the UL data. The base station may unnecessarily allocate UL resources to the wireless device to transmit (e.g., transmit) UL data without timely transmitting / reporting an enhanced BSR. At least some wireless communications may result in wasted UL resources. The improvements described herein for at least some procedures (e.g., LCP procedures in the wireless device) may provide various such benefits, such as reducing the PSER of the PDU set (e.g., improving quality of service), reducing the likelihood of PSDB violations, improving the user experience (e.g., improving video / screen freezes), and / or improving resource efficiency for transmitting UL data. Enhancements to LCP procedures that enable wireless devices to transmit / report extended BSR MAC CEs to a base station in a timely manner to improve UL spectral efficiency or data transmission delay may be achieved by the embodiments described herein.

[0239] The wireless device may transmit (e.g., transmit) a MAC PDU including at least one of a first MAC CE and a second MAC CE via a first MAC control element (CE) over at least one uplink shared channel (UL-SCH) resource to transmit (e.g., transmit) delay information corresponding to one or more logical channels. The wireless device may determine a prioritization of the logical channel of the first MAC CE and the logical channel of the second MAC CE. The wireless device may trigger a delay reporting procedure to transmit (e.g., transmit) the delay information. The wireless device may determine that the priority of the logical channel of the first MAC CE is equal to or greater than the priority of the logical channel of the second MAC CE, and the second MAC CE is different from the first MAC CE. The wireless device may initially multiplex the first MAC CE in the MAC PDU based on which at least one UL-SCH accommodates the first MAC CE. The wireless device may multiplex a second MAC CE in the MAC PDU based on at least one UL-SCH accommodating the first MAC CE after multiplexing the first MAC CE in the MAC PDU. The wireless device may avoid / skip multiplexing a second MAC CE in the MAC PDU based on at least one UL-SCH not accommodating the first MAC CE after multiplexing the first MAC CE in the MAC PDU.

[0240] The wireless device may determine that the priority of the logical channel of the first MAC CE is equal to or greater than the priority of the logical channel of the second MAC CE and that at least one UL-SCH resource accommodates the first MAC CE. The wireless device may multiplex the first MAC CE in a MAC PDU (e.g., the MAC PDU includes the first MAC CE and the second MAC CE) before multiplexing the second MAC CE in the MAC PDU to transmit (e.g., transmit) the MAC PDU. The wireless device may skip / avoid multiplexing the second MAC CE in the MAC PDU based on the at least one UL-SCH resource not corresponding to the second MAC CE (e.g., the MAC PDU includes the first MAC CE but not the second MAC CE).

[0241] The wireless device may determine that the priority of the logical channel of the first MAC CE is less than or equal to the priority of the logical channel of the second MAC CE and that at least one UL-SCH resource accommodates the second MAC CE. The wireless device may multiplex the second MAC CE in the MAC PDU before multiplexing the first MAC CE in the MAC PDU (e.g., the MAC PDU includes the first MAC CE and the second MAC CE). The wireless device may avoid / skip multiplexing the first MAC CE in the MAC PDU based on at least one UL-SCH resource not accommodating the first MAC CE (e.g., the MAC PDU includes the second MAC CE but not the first MAC CE).

[0242] The wireless device may determine that the first MAC CE has a higher priority than first pending data of one or more logical channels (e.g., excluding data from the UL-CCCH). The MAC PDU may not include the first pending data of one or more logical channels.

[0243] The second MAC CE may be at least one of a MAC CE for LBT failure, a MAC CE for Timing Advance Report (TAR), a MAC CE for Buffer Status Report (BSR), a MAC CE for Power Headroom Report (PHR), a MAC CE for locating a measurement gap activation / deactivation request, a MAC CE for the amount (e.g., number) of desired guard symbols, and / or a MAC CE for Case 6 timing request. The BSR may not include a padding BSR. The BSR may be at least one of an extended BSR, a preemptive BSR, an extended preemptive BSR, and a sidelink (SL)-BSR. The SL-BSR may have priority over the logical channel prioritization (LCP) procedure. The PHR may be at least one of a single-entry PHR, an enhanced single-entry PHR, a multiple-entry PHR, and / or an enhanced multiple-entry PHR.

[0244] The wireless device may trigger an enhanced buffer status report (BSR) based on (e.g., in response to) arrival of first uplink data corresponding to one or more first logical channels for transmitting (e.g., transmitting) the enhanced BSR via a first medium access control (MAC) control element (CE). The wireless device may transmit (e.g., transmit) a MAC PDU including at least one of the first MAC CE and the second MAC CE via at least one UL-SCH resource, where the transmission (e.g., transmission) is based on prioritization of the logical channel of the first MAC CE and the logical channel of the second MAC CE. The wireless device may determine that the first MAC CE has a higher priority than the first uplink data of the one or more logical channels. The MAC PDU may not include the first uplink data of the one or more logical channels.

[0245] The wireless device may determine that the priority of the logical channel of the first MAC CE is equal to or greater than the priority of the logical channel of the second MAC CE and that at least one UL-SCH resource accommodates the first MAC CE. The wireless device may multiplex the first MAC CE in a MAC PDU (e.g., the MAC PDU includes the first MAC CE and the second MAC CE) before multiplexing the second MAC CE in the MAC PDU. The wireless device may avoid / skip multiplexing the second MAC CE in a MAC PDU (e.g., the MAC PDU includes the first MAC CE but not the second MAC CE) based on at least one UL-SCH resource not corresponding to the second MAC CE.

[0246] The wireless device may determine that the priority of the logical channel of the first MAC CE is less than or equal to the priority of the logical channel of the second MAC CE and that at least one UL-SCH resource accommodates the second MAC CE. The wireless device may multiplex the second MAC CE in a MAC PDU (e.g., the MAC PDU includes the first MAC CE and the second MAC CE) before multiplexing the first MAC CE in a MAC PDU. The wireless device may avoid / skip multiplexing the first MAC CE in a MAC PDU (e.g., the MAC PDU may include the second MAC CE and not the first MAC CE) based on at least one UL-SCH resource not corresponding to the first MAC CE.

[0247] The second MAC CE may be for a second BSR corresponding to second uplink data of one or more second logical channels. The wireless device may determine that at least one of the following is satisfied: a data volume size of the first uplink data is larger than a data volume size of the second uplink data, and / or the data volume size of the first uplink data is larger than a threshold, and / or the data volume size of the second uplink data is smaller than a threshold, and / or the (quantization) granularity of the buffer size level of the enhanced BSR is smaller than the (quantization) granularity of the buffer size level of the second BSR, and / or the buffer size level of the second BSR is derived based on a conventional BSR table (e.g., Table 6.2.1-2 of 3GPP® TR 38.321 or Table 6.2.1-2b of 3GPP® TR 38.321), and / or the buffer size level of the enhanced BSR is derived based on a conventional BSR table (e.g., Table 6.2.1-2 of 3GPP® TR 38.321 or Table 6.2.1-2b of 3GPP® TR 38.321). The BSR is not derived based on Table 6.2.1-2b) of 38.321 and / or the enhanced BSR includes delay information for the first uplink data.

[0248] The wireless device may trigger a first buffer status report (BSR) based on (e.g., in response to) arrival of first uplink data corresponding to one or more first logical channels. The wireless device may prioritize the first BSR for a logical channel prioritization (LCP) procedure based on (e.g., in response to) at least one BSR prioritization rule being satisfied. The wireless device may transmit (e.g., transmit) a MAC PDU including at least one of the first BSR and the first MAC CE for a second MAC CE based on (e.g., in response to) prioritizing the first BSR for the LCP procedure and via at least one UL-SCH resource, the transmission (e.g., transmission) being based on prioritization of the logical channel of the first MAC CE and the logical channel of the second MAC CE. The at least one BSR prioritization rule may be satisfied based on at least one of the following: the data size volume of the first uplink data of the first BSR is based on a first BSR table, and the first BSR table is different from a conventional BSR table (e.g., Table 6.2.1-2 of 3GPP® TR 38.321 or Table 6.2.1-2b of 3GPP® TR 38.321); the first BSR includes delay information of one or more first logical channels; the data size volume of the first uplink data is greater than a threshold; the first uplink data includes an end PDU of a PDU set; the delay budget / remaining time of a PDU of the PDU set is less than a threshold; and / or at least one UL-SCH resource does not accommodate a first BSR corresponding to one or more logical channels, and the one or more logical channels are prioritized.

[0249] The wireless device may determine whether at least one BSR prioritization rule is satisfied based on PDU set information of at least one PDU set corresponding to the first uplink data. The wireless device may determine whether at least one BSR prioritization rule is satisfied based on PDU set-related assistance information of the at least one PDU set. The PDU set-related assistance information may include a PDU set integration indication (PSII) of the at least one PDU set. The at least one BSR prioritization rule may be satisfied in response to the PSII of the PDU set indicating that all PDUs of the PDU set are required for use of the PDU set by an application layer. The PDU set-related assistance information may include a PDU set delay budget (PSDB) of the at least one PDU set. The at least one BSR prioritization rule may be satisfied in response to the PSDB of the PDU set being less than a threshold.

[0250] FIG. 17A illustrates a flowchart of a method / procedure for transmitting (e.g., transmitting) delay information in a wireless communication system according to an aspect of the present disclosure. FIG. 17A may illustrate an example embodiment for multiplexing and assembling a MAC PDU including a MAC CE for the delay information. FIG. 17A may illustrate an example embodiment for determining whether to generate a MAC CE for the delay information to perform a new UL transmission. The wireless device may be in an RRC inactive state / mode (e.g., an RRC_INACTIVE / IDLE state), and / or an RRC idle mode / state (e.g., an RRC_IDLE state), and / or an RRC connected state / mode (e.g., an RRC_CONNECTED state).

[0251] The wireless device shown in step 1702 of FIG. 17A may trigger a delay reporting procedure to transmit (e.g., transmit) delay information corresponding to one or more logical channels. The wireless device may transmit (e.g., transmit) the delay information via a first MAC CE. The first MAC CE may be a MAC CE for / corresponding to the delay information (e.g., a MAC CE for the delay information). The wireless device may transmit (e.g., transmit) a MAC PDU including at least one of the first MAC CE and the second MAC CE in step 1704. The wireless device may determine a prioritization of the logical channels of the first MAC CE and the logical channels of the second MAC CE for transmitting (e.g., transmitting) the delay information via at least one uplink shared channel (UL-SCH) resource. The transmission of the MAC PDU may correspond to a new UL transmission.

[0252] The exemplary embodiments may enable a wireless device to appropriately generate / send / transmit a MAC CE for delay information to report / send delay information of one or more logical channels to a base station. The exemplary embodiments may improve the LCP procedure to determine the priority / order of a first MAC CE (e.g., a MAC CE for delay information).

[0253] FIG. 17B shows a flowchart of a method / procedure for transmitting (e.g., transmitting) delay information in a wireless communication system according to an aspect of the present disclosure. FIG. 17B may show an example embodiment for multiplexing and assembling a MAC PDU including a MAC CE for the delay information. FIG. 17B may show an example embodiment for determining whether to generate a MAC CE for the delay information, e.g., for performing a new UL transmission. The wireless device may be in an RRC inactive state / mode (e.g., RRC_INACTIVE / IDLE state), and / or an RRC idle mode / state (e.g., RRC_IDLE state), and / or an RRC connected state / mode (e.g., RRC_CONNECTED state). The wireless device in step 1712 may trigger a delay reporting procedure to transmit (e.g., transmit) delay information corresponding to one or more logical channels.

[0254] The wireless device shown in step 1714 of Figure 17B may determine that the priority of the logical channel of the first MAC CE is equal to or greater than the priority of the logical channel of the second MAC CE. The wireless device may determine that the priority of the first MAC CE is lower / not lower than the priority of the second MAC CE. The second MAC CE may be different from the first MAC CE.

[0255] The wireless device in step 1716 may first multiplex the first MAC CE in the MAC PDU based on at least one UL-SCH resource accommodating the first MAC CE. After multiplexing the first MAC CE in the MAC PDU, the wireless device may multiplex the second MAC CE in the MAC PDU in step 1720 based on a determination of whether at least one UL-SCH resource accommodates the second MAC CE and its subheader (step 1718). Example embodiments may enable the wireless device to appropriately generate / send / transmit a MAC CE for delay information based on a priority / order of the first MAC CE and / or whether at least one UL-SCH resource accommodates the second MAC CE (step 1722). For example, the wireless device may determine at least one UL-SCH to accommodate the second MAC CE (plus its subheader) based on the (available) bit amount (e.g., number) in / of at least one UL-SCH resource being greater than the (decoded / modulated information) bits of the first MAC CE (plus its subheader). The wireless device may avoid / skip multiplexing the second MAC CE in the MAC PDU based on determining whether the at least one UL-SCH does not accommodate the second MAC CE and its subheader after multiplexing the first MAC CE in the MAC PDU (step 1718) in step 1724. The wireless device may transmit (e.g., transmit) the MAC PDU including the first MAC CE if the wireless device avoids / skips multiplexing the second MAC CE in the MAC PDU (step 1726).

[0256] The wireless device may determine that the priority of the logical channel of the first MAC CE is equal to or greater than the priority of the logical channel of the second MAC CE and that at least one UL-SCH resource accommodates the first MAC CE. The wireless device may multiplex the first MAC CE in a MAC PDU (e.g., the MAC PDU includes the first MAC CE and the second MAC CE) before multiplexing the second MAC CE in the MAC PDU to transmit (e.g., transmit) the MAC PDU. The wireless device may skip / avoid multiplexing the second MAC CE in the MAC PDU based on the at least one UL-SCH resource not corresponding to the second MAC CE (e.g., the MAC PDU includes the first MAC CE but not the second MAC CE).

[0257] The wireless device may determine that the priority of the logical channel of the first MAC CE is less than or equal to the priority of the logical channel of the second MAC CE and that at least one UL-SCH resource accommodates the second MAC CE (plus its subheader). The wireless device may multiplex the second MAC CE in the MAC PDU before multiplexing the first MAC CE in the MAC PDU (e.g., the MAC PDU includes the first MAC CE and the second MAC CE). The wireless device may transmit (e.g., transmit) a MAC PDU including the first MAC CE and the second MAC CE based on at least one UL-SCH resource accommodating the first MAC CE and the second MAC CE. The wireless device may avoid / skip multiplexing the first MAC CE in the MAC PDU based on at least one UL-SCH resource not accommodating the first MAC CE (e.g., the MAC PDU includes the second MAC CE but not the first MAC CE).

[0258] The second MAC CE may be at least one of a MAC CE for a Timing Advance Report (TAR), a MAC CE for a Buffer Status Report (BSR), a MAC CE for a Power Headroom Report (PHR), a MAC CE for locating a measurement gap activation / deactivation request, a MAC CE for the amount (e.g., number) of desired guard symbols, and / or a MAC CE for a Case 6 timing request. The BSR may not include a padding BSR. The BSR may be at least one of an extended BSR, a preemptive BSR, an extended preemptive BSR, and / or a sidelink (SL)-BSR. The SL-BSR may have priority over a logical channel prioritization (LCP) procedure. The PHR may be at least one of a single-entry PHR, an enhanced single-entry PHR, a multiple-entry PHR, and / or an enhanced multiple-entry PHR.

[0259] FIG. 18 illustrates an example embodiment of a logical channel prioritization (LCP) procedure in a wireless communication system according to an aspect of the present disclosure. FIG. 19 illustrates an example embodiment of a logical channel prioritization (LCP) procedure in a wireless communication system according to an aspect of the present disclosure. FIG. 20 illustrates an example embodiment of MAC CE priorities (e.g., logical channel priorities) with respect to delay information according to an aspect of the present disclosure. FIG. 20 may illustrate several examples of MAC CE priorities / orders with respect to delay information compared to UL MAC CEs (e.g., LBT failure MAC CEs, BSR MAC CEs, etc.).

[0260] 18-20 may illustrate example implementations of methods / procedures for transmitting (e.g., transmitting) delay information in one or more PDUs at a wireless device (e.g., an XR device) and / or receiving the delay information at a base station. FIGS. 18-20 may illustrate example embodiments for multiplexing and assembling a MAC PDU including a MAC CE for the delay information. FIGS. 18-20 may illustrate example embodiments for determining whether to generate a MAC CE for the delay information, e.g., for performing a new UL transmission. The wireless device may be in an RRC inactive state / mode (e.g., RRC_INACTIVE / IDLE state), and / or an RRC idle mode / state (e.g., RRC_IDLE state), and / or an RRC connected state / mode (e.g., RRC_CONNECTED state).

[0261] As shown in step 1802 of FIG. 18 and step 1902 of FIG. 19, a wireless device (e.g., UE 1820, UE 1920) may receive one or more configuration parameters (e.g., one or more RRC configuration parameters) from a base station (e.g., BS 1822, BS 1922). The one or more configuration parameters may include, for example, one or more serving cell (e.g., one or more serving cell or cell) configuration parameters (e.g., ServingCellConfigCommon, ServingCellConfigCommonSIB, and / or ServingCellConfig) for configuring one or more cells (e.g., one or more serving cells). The one or more cells may comprise a master (or primary) cell group (MSG) and / or a secondary cell group (SCG). A cell of the one or more cells may be a primary secondary cell (PSCell), or a primary cell (PCell), or a secondary cell (SCell), or a special cell (SpCell). The cells of the one or more cells may belong to a first cell group corresponding to a primary TAG (pTAG) or a second cell group corresponding to a secondary TAG (sTAG). The one or more configuration parameters may configure the wireless device for multi-cell communication and / or carrier aggregation (CA).

[0262] The one or more configuration parameters (e.g., one or more RRC configuration parameters) may include, for example, one or more BWP configuration parameters (e.g., BWP-DownlinkDedicatedIE) of the downlink (DL) BWP of the serving cell (e.g., initial downlink BWP) and / or one or more UL BWP of the serving cell. The one or more WBP configuration parameters (e.g., of the downlink BWP) may include one or more PDCCH configuration parameters (e.g., for the PDCCH of the downlink BWP, e.g., in pdcch-ConfigIE and / or PDCCH-ServingCellConfigIE applicable to all downlink BWPs of the serving cell). The one or more configuration parameters may include MAC parameters (e.g., MAC-CellGroupConfig) of a cell group (e.g., primary cell group and / or secondary cell group). The one or more configuration parameters may include one or more logical channel (LCH) configuration parameters (e.g., IElogicalConfig) for configuring multiple logical channels. The one or more configuration parameters may include one or more BSR configuration parameters (e.g., BSR-Config).

[0263] As shown in Figures 18 and 19, the multiple logical channels may include one or more logical channels. One or more configuration parameters may configure / enable the wireless device to send / report / transmit (pending) delay information of UL data to the base station. The pending UL data may belong to one or more logical channels. All logical channels of one or more logical channels may have data for UL transmission. At least one logical channel of the one or more logical channels may have data for UL transmission. The wireless device may trigger a BSR due to UL data of one or more logical channels (e.g., at least one logical channel of one or more logical channels).

[0264] The wireless device may transmit (e.g., transmit) delay information based on a first MAC CE (e.g., a MAC CE for delay information). The first MAC CE may be for transmitting (e.g., transmitting) remaining times for one or more logical channels / one or more PDUs / at least one PDU set. A first logical channel among the plurality of logical channels may correspond to the first MAC CE. The first MAC CE may have a first LCID / eLCID. An index corresponding to the first LCID may be between 37 and 42, or may be 47. An index corresponding to the first LCID may be different from at least one of 45, 45, 59, 60, 61, 62, and / or 63. An index / codepoint corresponding to the first eLCID may be between 64 and 292. An index / codepoint corresponding to the first eLCID may be different from at least one of 309, 310, 311, 312, 313, and / or 319.

[0265] The first MAC CE may include one or more fields. The one or more fields may include one or more IDs / identifiers of the one or more logical channels and / or an ID / identifier of the first LCG. The one or more fields may include one or more first values ​​and / or one or more second values. The one or more fields may include a first indicator / measurement / indication and / or a second indicator / measurement / indication. The one or more fields may include a delay budget / time remaining for at least one logical channel of the one or more logical channels. The delay budget / time remaining for at least one logical channel of the one or more logical channels may be less than a threshold (e.g., configured by one or more configuration parameters). At least one logical channel of the one or more logical channels may have pending data for transmission.

[0266] The wireless device may perform / transmit a new UL transmission to the base station via at least one UL-SCH (available) resource, as shown in Figures 18 and 19. For example, the at least one UL-SCH resource may not be for a retransmission of an UL transmission. The at least one UL-SCH resource may correspond to a Type 1 / Type 2 configured grant PUSCH resource and / or a dynamic grant PUSCH resource (e.g., scheduled by a scheduling DCI). For example, the wireless device (e.g., UE 1820, UE 1920) may receive a DCI indicating at least one UL-SCH resource (e.g., an UL grant) after / in response to / after a delay report (procedure), e.g., to trigger transmission of delay information (steps 1804, 1904). In some other cases, the at least one UL-SCH resource may be part of a random access procedure (e.g., Msg3 / MsgA PUSCH resource).

[0267] The wireless device may perform a multiplexing and assembly procedure (MAP) to perform a new UL transmission. By performing MAP, the wireless device may multiplex / construct at least one MAC SDU and at least one MAC CE (of a UL MAC CE) within a MAC PDU. The wireless device may determine whether to generate / produce / construct a first MAC CE. The at least one MAC CE may include the first MAC CE based on whether the first MAC CE is generated / produced. The at least one MAC CE may not include the first MAC CE based on whether the first MAC CE is not generated / produced. As shown in step 1806 of FIG. 18 and step 1906 of FIG. 19, the wireless device (e.g., UE 1820, UE 1920) may determine whether at least one UL-SCH resource for the new UL transmission can accommodate the first MAC CE (plus its subheader), for example, as a result of / based on logical channel prioritization (LCP), in order to determine whether to generate / produce / construct the first MAC CE.

[0268] As shown in step 1808 of FIG. 18 , a wireless device (e.g., UE 1820) may instruct a MAP to generate / produce / construct a first MAC CE based on (e.g., in response to) at least one UL-SCH resource for a new UL transmission containing a first MAC CE (plus its subheader) of at least one MAC CE (e.g., as a result of / based on an LCP procedure). The wireless device may multiplex / construct the first MAC CE and MAC SDU within a MAC PDU, e.g., the MAC PDU may include the first MAC CE. The wireless device (e.g., UE 1820) may transmit (e.g., transmit) a MAC PDU including the first MAC CE to a base station (e.g., BS 1822) via at least one UL-SCH resource (step 1810). The wireless device may transmit the first MAC CE via at least one UL-SCH resource.

[0269] As shown in step 1908 of FIG. 19 , a wireless device (e.g., UE 1920) may not instruct (or skip / avoid instructing) the MAP to generate / produce / construct a first MAC CE based on (e.g., in response to) at least one UL-SCH resource for a new UL transmission not accommodating the first MAC CE (plus its subheader) of at least one MAC CE (e.g., as a result of / based on an LCP procedure). The wireless device may not multiplex / construct (or skip / avoid multiplexing) the first MAC CE and MAC SDU within a MAC PDU (e.g., the MAC PDU may not include the first MAC CE). The wireless device (e.g., UE 1920) may transmit (e.g., transmit) a MAC PDU that does not include the first MAC CE via at least one UL-SCH resource to a base station (e.g., BS 1922) (step 1910). The wireless device may refrain from transmitting (e.g., transmit) the first MAC CE via at least one UL-SCH resource.

[0270] A wireless device implementing an LCP for transmission / generation of a first MAC CE (e.g., a MAC CE for delay information) may determine an order (or priority) of the first MAC CE among a UL MAC CE (e.g., at least one MAC CE) and / or multiple logical channels. The wireless device may determine that the first MAC CE is prioritized among / from the at least one MAC CE. The logical channel of the first MAC CE has a higher priority than other MAC CEs of the at least one MAC CE. The wireless device may generate the first MAC CE before / before generating other MAC CEs of the at least one MAC CE (e.g., the wireless device may generate the first MAC CE after generating the other MAC CEs of the at least one MAC CE). The first MAC CE may be listed above other MAC CEs of the at least one MAC CE. Figure 20 shows some examples of possible orders / priorities of the first MAC CE compared to (among) the UL MAC CE.

[0271] As shown in FIG. 18 , as a result of / based on the LCP procedure, a wireless device (e.g., UE 1820) may determine that at least one UL-SCH resource for a new UL transmission accommodates a first MAC CE (plus its subheader) of at least one MAC CE, but not other MAC CEs of the at least one MAC CE (e.g., a third MAC CE of the UL MAC CE). The wireless device may instruct the MAP to generate the first MAC CE (e.g., not generate other MAC CEs of the at least one MAC CE). The wireless device may multiplex the first MAC CE and MAC SDUs within a MAC PDU (e.g., a MAC PDU may include the first MAC CE but not other MAC CEs of the at least one MAC CE). As shown in FIG. 18 , the wireless device may transmit (e.g., transmit) a MAC PDU via at least one UL-SCH resource. The MAC PDU may include at least one MAC SDU. The MAC PDU may not include any MAC SDUs (e.g., the MAC PDU may include the first MAC CE).

[0272] As shown in FIG. 19 , as a result of / based on the LCP procedure, a wireless device (e.g., UE 1920) may determine at least one UL-SCH resource for a new UL transmission that does not accommodate a first MAC CE (plus its subheader) of the at least one MAC CE but accommodates another MAC CE of the at least one MAC CE (e.g., a second MAC CE of the UL MAC CE). The wireless device may avoid / skip instructing the MAP to generate the first MAC CE. The wireless device may avoid / skip multiplexing the first MAC CE and MAC SDU within a MAC PDU (e.g., a MAC PDU may include the other MAC CE of the at least one MAC CE and not the first MAC CE). The wireless device may transmit (e.g., transmit) the MAC PDU via at least one UL-SCH resource as shown in FIG. 19 .

[0273] A wireless device (e.g., UE 1920) may determine / identify a second MAC CE of an UL MAC CE having a higher / greater / greater / greater priority / order than the first MAC CE, as shown in FIG. 19 (e.g., the priority of the logical channel of the second MAC CE is equal to or greater than the priority of the logical channel of the first MAC CE). The at least one MAC CE may include the second MAC CE. The at least one MAC CE may not include the second MAC CE. The wireless device may determine, as a result of / based on the LCP procedure, that at least one UL-SCH resource for a new UL transmission accommodates the second MAC CE (plus its subheader) of the at least one MAC CE and does not accommodate the first MAC CE (plus its subheader) of the at least one MAC CE. The wireless device may instruct the MAP to generate the second MAC CE. The wireless device may multiplex the second MAC CE and the MAC SDU within a MAC PDU (e.g., the MAC PDU may not include the first MAC CE but may include the second MAC CE). The wireless device may transmit (e.g., transmit) the MAC PDU via at least one UL-SCH resource.

[0274] The wireless device may, for example, determine that at least one UL-SCH resource accommodates the first MAC CE plus its subheader after multiplexing the second MAC CE in the MAC PDU. The wireless device may instruct the MAP to generate the first MAC CE. The wireless device may multiplex the first MAC CE and a MAC SDU in the MAC PDU (e.g., the MAC PDU may include both the first MAC CE and the second MAC CE).

[0275] A wireless device (e.g., UE 1820) may determine / identify a third MAC CE of an UL MAC CE having a lower / smaller priority / order than the first MAC CE (e.g., the priority of the logical channel of the first MAC CE is equal to or greater than the priority of the logical channel of the third MAC CE), as shown in FIG. 18. The at least one MAC CE may include the third MAC CE. The at least one MAC CE may not include the third MAC CE. The wireless device may determine, as a result of / based on the LCP procedure, that at least one UL-SCH resource for a new UL transmission accommodates the first MAC CE (plus its subheader) of the at least one MAC CE but not the third MAC CE (plus its subheader) of the at least one MAC CE. The wireless device may instruct the MAP to generate the first MAC CE. The wireless device may multiplex the first MAC CE and MAC SDU within a MAC PDU (e.g., the MAC PDU may include the first MAC CE but not the third MAC CE). The wireless device may transmit (e.g., transmit) a MAC PDU over at least one UL-SCH resource, and the at least one MAC CE may not include a third MAC CE.

[0276] For example, the wireless device may determine that at least one UL-SCH resource accommodates a third MAC CE plus its subheader after multiplexing the first MAC CE in a MAC PDU. The wireless device may instruct the MAP to generate the third MAC CE. The wireless device may multiplex the third MAC CE and a MAC SDU in a MAC PDU (e.g., the MAC PDU may include both the first MAC CE and the third MAC CE).

[0277] The second MAC CE may be an LBT failure MAC CE when an LBT failure indication is received from a lower layer (physical layer) of the wireless device to the MAC layer of the wireless device, as shown in Case 1 of FIG. 20. The wireless device may determine that the priority / order of the LBT failure MAC CE is greater / higher (or equal to, or not lower) than the priority / order of the first MAC CE. The LBT failure MAC CE may have a greater / higher priority than the first MAC CE if the LBT failure provides more important information (e.g., wireless medium availability) to the base station (compared to the first MAC CE). In the case of an LBT failure, the base station may not be able to schedule the wireless device even though delay information is indicated to the base station. The wireless device may determine that the priority / order of the first MAC CE is greater / higher (or equal to, or not lower) than the priority / order of the LBT failure MAC CE. The third MAC CE may be a MAC CE for a timing advance report when the timing advance report (TAR) procedure determines that at least one TAR is triggered and not canceled. The wireless device may determine that the priority / order of the MAC CE for the timing advance report is lower (or equal to, or not higher than) the priority of the first MAC CE. The MAC CE for the timing advance report may have a lower / smaller priority than the first MAC CE because the delay information may provide more important information to the base station (for scheduling and / or radio resource management) (e.g., if the PSII of the PDU set indicates that all PDUs of the PDU set are required for use of the PDU set by the application layer and / or if the remaining time of the ending PDU is less than a threshold value, e.g., 10 ms).

[0278] The second MAC CE may be the MAC CE for the timing advance report if the TAR procedure determines that at least one TAR is triggered and not canceled, as shown in Case 2 of FIG. 20. The wireless device may determine that the priority / order of the MAC CE for the timing advance report is greater / higher (or equal to, or not lower) than the priority / order of the first MAC CE. The MAC CE for the timing advance report may have a higher / greater priority than the first MAC CE if this allows the base station to measure / estimate the round-trip transmission delay (RTT) between the wireless device and the base station and / or improve the efficiency of UL transmission (e.g., lower UL transmission delay). The third MAC CE may be the MAC CE for the ranked SL-BSR (e.g., prioritized according to clause 5.22.1.6 of 3GPP TS 38.321). The wireless device may determine the regular and / or periodic SL-BSR to be triggered. The wireless device may determine that the priority / order of the MAC CE of the prioritized SL-BSR is lower (or equal to, or not higher than) the priority / order of the first MAC CE. The MAC CE for the prioritized SL-BSR may have a lower / smaller priority than the first MAC CE if, for an XR application, violation of the delay budget of a PDU (e.g., an end PDU) of the PDU set may result in the inapplicability of the PDU set (e.g., if the PSII of the PDU set indicates that all PDUs of the PDU set are required for use of the PDU set by the application layer).

[0279] As shown in Case 3 of Figure 20, the second MAC CE may be the MAC CE for the prioritized SL-BSR when a regular and / or periodic SL-BSR is triggered. The wireless device may determine that the priority / order of the second MAC CE for the prioritized SL-BSR is greater / higher (or equal to, or not lower) than the priority / order of the first MAC CE. The MAC CE for the prioritized SL-BSR may have a higher priority than the first MAC CE as prioritized sidelink (SL) pending data. The third MAC CE may be the MAC CE for a BSR (e.g., regular BSR and / or preemptive BSR and / or SL BSR) when a BSR is triggered. The MAC CE for the BSR may be at least one of a BSR MAC CE, and / or a short / long BSR MAC CE, and / or a truncated BSR MAC CE, and / or a short / long truncated BSR MAC CE, and / or an extended BSR MAC CE, and / or a MAC CE for an enhanced BSR, and / or a MAC CE for an (extended) preemptive BSR, and / or a MAC CE for an SL-BSR (excluding prioritized SL-BSRs and SL-BSRs included for padding). The BSR may not include a padding BSR (e.g., a MAC CE of a BSR included for padding and / or a MAC CE of an SL-BSR included for padding). The wireless device may determine that the priority / order of a MAC CE for a BSR is lower (or equal to, or not greater than) the priority / order of the first MAC CE. The MAC CE for the BSR may have a lower / lesser priority than the first MAC CE if violation of the delay budget of the PDUs of the PDU set for the XR application may result in the inapplicability of the PDU set (e.g., if the PSII of the PDU set indicates that all PDUs of the PDU set are required for use of the PDU set by the application layer).

[0280] As shown in Case 4 of FIG. 20, the second MAC CE may be the MAC CE of the BSR if the BSR is triggered. The wireless device may determine that the priority / order of the MAC CE for the BSR is greater / higher (or equal to, or not lower) than the priority / order of the first MAC CE. The MAC CE of the BSR may have a higher priority than the first MAC CE if the volume of pending data in the wireless device's buffer (e.g., via the BSR MAC CE) may provide more important information to the base station (e.g., for scheduling). The third MAC CE may be the MAC CE for the power headroom (PHR) (e.g., the third MAC CE is the MAC CE for the PHR). The wireless device may determine that the PHR is triggered. The MAC CE for the PHR may be the MAC CE for the extended PHR. The MAC CE for the PHR may be the MAC CE for the single-entry PHR and / or the MAC CE for the multi-entry PHR. The wireless device may determine that the priority / order of the MAC CE for the PHR is lower (or equal to, or not higher than) the priority of the first MAC CE. The MAC CE for the PHR may have a lower / smaller priority than the first MAC CE if violation of the delay budget of the PDUs of the PDU set for the XR application may result in the inapplicability of the PDU set (e.g., if the PSII of the PDU set indicates that all PDUs of the PDU set are required for use of the PDU set by the application layer).

[0281] The second MAC CE may be the MAC CE of the PHR. The wireless device may determine that the PHR is triggered. The wireless device may determine that the priority / order of the MAC CE for the PHR is greater / higher (or equal to, or not lower) than the priority of the first MAC CE. The MAC CE for the PHR may have a higher priority than the first MAC CE because the power headroom of the wireless device may provide more important information (e.g., the transmit power of the wireless device) to the base station (e.g., for scheduling and / or power efficiency / battery life of the wireless device). The third MAC CE may be a MAC CE for locating a measurement gap activation / deactivation request. The wireless device may determine that upper layers of the wireless device are triggered to transmit a positioning measurement gap activation / deactivation request. The wireless device may determine that the priority / order of the MAC CE for locating a measurement gap activation / deactivation request is lower (or equal to, or not greater) than the priority / order of the first MAC CE. The MAC CE for locating the measurement gap activation / deactivation request may have a lower / lesser priority than the first MAC CE if violation of the PDU delay budget of the PDUs configured for the XR application may result in the inapplicability of the PDU set (e.g., if the PSII of the PDU set indicates that all PDUs of the PDU set are required for use of the PDU set by the application layer).

[0282] The second MAC CE may be a MAC CE for positioning a measurement gap activation / deactivation request. The wireless device may determine that an upper layer of the wireless device is triggered to send a positioning measurement gap activation / deactivation request. The wireless device may determine that the priority / order of the MAC CE for positioning the measurement gap activation / deactivation request is greater / higher (or equal to, or not lower) than the priority / order of the first MAC CE. The MAC CE for positioning the measurement gap activation / deactivation request may have a higher priority than the first MAC CE if activating / deactivating a measurement gap (e.g., for positioning) can provide resource efficiency and / or positioning efficiency / accuracy. The third MAC CE may be at least one of a desired guard symbol quantity (e.g., number) MAC CE (e.g., an IAB-MT on a child node, e.g., a wireless device, may notify a parent IAB-DU or IAB donor DU of the desired guard symbol quantity (e.g., number) via a desired guard symbol MAC CE), a Case 6 timing request MAC CE, an IAB-MT recommended beam indication MAC CE, a desired IAB-MT PSD range MAC CE, and / or a desired DL Tx power adjustment MAC CE. The wireless device may determine that the priority / order of the third MAC CE is lower (or equal to, or not greater than) the priority / order of the first MAC CE if a violation of the PDU delay budget of a PDU set configured for an XR application may result in the inapplicability of the PDU set (e.g., if the PDU set's PSII indicates that all PDUs in the PDU set are required for use of the PDU set by the application layer).

[0283] The wireless device may determine that the priority / order of data from multiple logical channels (excluding the UL-CCCH) is lower than (or equal to, or not higher than) the priority / order of the first MAC CE. The wireless device may determine that the priority / order of data from one or more logical channels (e.g., data of an XR application) is lower than (or equal to, or not higher than) the priority / order of the first MAC CE. Timely sending (e.g., transmitting) the first MAC CE for the XR application may reduce the likelihood of violating the delay budget of the PDUs of the PDU set (e.g., when the PSII of the PDU set indicates that all PDUs of the PDU set are required for use of the PDU set by the application layer).

[0284] The wireless device may determine that the priority / order of one or more logical channels (e.g., data of an XR application or PDU set) and / or data from multiple logical channels (excluding the UL-CCCH) is higher (or equal to, or not lower) than the priority / order of the first MAC CE. The wireless device may determine that the priority / order of data from multiple logical channels (excluding the UL-CCCH) is higher (or equal to, or not lower) than the priority / order of the first MAC CE. The wireless device may determine that XR data is available on one or more logical channels. Sending (e.g., transmitting) the data of the XR application in a timely manner may reduce the likelihood of violating the delay budget of the PDUs of the PDU set (e.g., if the PSII of the PDU set indicates that all PDUs of the PDU set are required for use of the PDU set by the application layer).

[0285] The wireless device may determine that the priority / order of the first MAC CE is higher (or equal to, or not lower) than the priority / order of the padding BSR (e.g., a BSR included / included in the padding). The padding BSR may include an SL-BSR that is included / included in the padding (e.g., a padding SL-BSR). The wireless device for an XR application may trigger the transmission of delay information (e.g., via generation of the first MAC CE) instead of triggering the padding BSR (e.g., to send / transmit the MAC CE of the BSR included in the padding). Timely transmission (e.g., transmission) of the delay information may reduce the possibility of violating the delay budget of the PDUs of the PDU set (e.g., when the PSII of the PDU set indicates that all PDUs of the PDU set are required for use of the PDU set by the application layer).

[0286] The one or more logical channels may belong to at least one logical channel group (LCG), e.g., a first LCG having a first LCG identifier. A first logical channel of the one or more logical channels may have an indication to indicate / enable / send reports of delay information for corresponding UL pending data of the first logical channel. A second logical channel of the plurality of logical channels (excluding the one or more logical channels) may not have an indication to indicate / enable / send reports of delay information for corresponding UL pending data of the second logical channel.

[0287] The wireless device may determine that UL data may be available / pending in a buffer of the wireless device (e.g., corresponding to one or more logical channels). The UL (pending) data may include one or more PDUs of at least one PDU set. The UL data may include one or more PDUs (e.g., a PDU set or at least one PDU set). The at least one PDU set may correspond to (or be associated with) one or more logical channels. The UL (pending) data may correspond to at least one of an XR QoS flow and / or an XR video stream and / or XR audio data and / or XR pause / control information.

[0288] One or more configuration parameters may configure the wireless device to report / send / transmit delay information for one or more logical channels (and / or one or more PDUs and / or at least one PDU set). The delay information may indicate to (or inform) the base station of a delay budget / remaining time for pending data in the wireless device's buffer (e.g., and / or how much data is buffered in the wireless device relative to the delay budget / remaining information). The UL data may correspond to XR data / traffic (e.g., XR QoS flow and / or XR video stream and / or XR audio data and / or XR pause / control information).

[0289] The UL data may correspond to one or more XR QoS flows and / or streams. The UL data may correspond to one or more logical channels of a plurality of logical channels. The one or more logical channels may correspond to (or be associated with) one or more XR QoS flows and / or streams. The wireless device may determine the delay information based on / using PDU set information (e.g., of / corresponding to one or more PDUs and / or at least one PDU set). The wireless device may determine the delay information based on / using PDU set-related assistance information (e.g., of / corresponding to one or more PDUs and / or at least one PDU set).

[0290] The delay information may include, for example, a delay budget / remaining time (e.g., PDB) of one or more PDUs. The delay information may indicate / include one or more second values ​​corresponding to the delay budget / remaining time of one or more PDUs. The wireless device may determine / calculate the remaining time / delay information of one or more PDUs to determine the one or more second values. The one or more second values ​​may indicate / measure / indicate the remaining time until a violation / expiration of the PDU delay budget of one or more PDUs. The one or more second values ​​may indicate / measure / indicate the remaining time for one or more PDUs to be dropped by the wireless device. The PDU may be the end PDU of one or more PDUs (e.g., at least one PDU set). The PDU may be the start PDU of one or more PDUs (e.g., at least one PDU set). The PDU may be any PDU of one or more PDUs (e.g., at least one PDU set). The PDU may have a first PDU SN / ID / number / identifier. A PDU set of the at least one PDU set may have a first PDU set identifier. The delay information may depend on a PDU set importance of the at least one PDU set. The wireless device may determine that the value of the one or more second values ​​is less than a threshold (e.g., configured by one or more configured parameters). The wireless device may determine that the value of the one or more second values ​​is less than a threshold (e.g., configured by one or more configured parameters).

[0291] The wireless device may determine / measure delay information based on PDU set-related assistance information (e.g., of / corresponding to one or more PDUs and / or at least one PDU set). The delay information may include a second measurement / metric / value / indication (e.g., minimum / shortest / smallest, and / or maximum / largest / longest, and / or average) of one or more second values ​​(e.g., remaining time / delay budget of one or more PDUs of at least one PDU set) if the PDU Set Integrated Indication (PSII) of the PDU set indicates that all PDUs of the PDU set are required for use of the PDU set by the application layer. The wireless device may determine that the measurement / metric / value / indication is less than a threshold. The threshold may be set by one or more configuration parameters.

[0292] The delay information may include / indicate one or more first values ​​corresponding to, for example, a PDU set delay budget (PSDB) for the at least one PDU set. The wireless device may determine / calculate remaining time / delay information for the at least one PDU set to determine the one or more first values. The values ​​of the one or more first values ​​may indicate / measure / indicate a remaining time until a delay budget (e.g., for a PDU set of the at least one PDU set) is violated / expired. The values ​​of the one or more first values ​​may indicate / measure / indicate a remaining time for a PDU set of the at least one PDU set to be dropped / ignored by the wireless device (or become irrelevant to the application layer of the wireless device). The wireless device may determine that the values ​​of the one or more first values ​​are less than a threshold (e.g., configured by one or more configured parameters).

[0293] The delay information may include a first measurement / metric / value / indication (e.g., minimum / shortest / smallest, and / or maximum / largest / longest, and / or average) of one or more first values ​​(e.g., remaining time / delay budget for one or more PDU sets) if the PDU Set Integrated Indication (PSII) of the PDU set indicates that all PDUs of the PDU set are required for use of the PDU set by the application layer. The wireless device may determine that the measurement / metric / value / indication is less than a threshold. One or more configuration parameters may configure the threshold, remaining time / delay budget (e.g., PSDB) of at least one PDU set.

[0294] Each value of the one or more first / second values ​​may be expressed in milliseconds. Each value of the one or more first / second values ​​may be expressed in a quantity (e.g., number) of slots / subframes / symbols. The slot / subframe / symbol duration for representing each value of the one or more first / second values ​​may be based on a default (or predefined) numerology / SCS (e.g., 15 KHz, or 30 KHz, or 60 KHz, etc.). One or more configuration parameters may indicate the default numerology / SCS.

[0295] The wireless device may determine that a delay reporting procedure is triggered to send (e.g., transmit) delay information. The wireless device may determine that the delay reporting procedure is not canceled. The wireless device may attempt to send (e.g., transmit) delay information based on (e.g., in response to) the delay reporting procedure being triggered (and not canceled) (e.g., the triggered delay reporting procedure is pending). The wireless device may cancel a triggered delay reporting procedure based on (e.g., in response to) sending (e.g., transmitting) delay information (e.g., a first MAC CE or an RRC message including delay information). The wireless device may cancel a triggered delay reporting procedure based on (e.g., in response to) sending (e.g., transmitting) UL data (e.g., of one or more logical channels) to a base station. The wireless device may trigger a delay reporting procedure based on determining that a BSR corresponding to UL data (e.g., of one or more logical channels) is triggered and not canceled. The triggering of the delay reporting may be based on (e.g., in response to / after) a triggering BSR corresponding to the UL data. The wireless device may cancel a triggered deferred reporting procedure based on (e.g., in response to) a BSR corresponding to UL data being canceled. The wireless device may cancel a triggered deferred reporting procedure based on sending (e.g., transmitting) a first MAC CE. The MAC PDU including the first MAC CE may not include UL data for one or more logical channels.

[0296] The wireless device may cancel a triggered delay reporting procedure based on (e.g., in response to) dropping UL data (e.g., one or more logical channels). The wireless device may determine that PDUs of one or more PDUs are to be dropped at the RLC layer and / or the PDCP layer and / or the MAC layer (of the wireless device and / or the base station). The wireless device may determine that PDUs of at least one PDU set are to be dropped at the RLC layer and / or the PDCP layer and / or the MAC layer (of the wireless device and / or the base station). The RLC / PDCP layer of the wireless device may send a drop indication to the MAC layer of the wireless device. The drop indication may indicate that UL data (e.g., PDUs and / or PDU sets) are to be dropped at the RLC / PDCP layer of the wireless device. The MAC layer of the wireless device may cancel a triggered delay reporting procedure based on (e.g., in response to) receiving the drop indication.

[0297] The wireless device may send (e.g., transmit) a UL message including UE capability information / parameters / message to the base station. The UE capability message may include (or indicate to the base station) a capability to determine / calculate / derive delay information. The UE capability message may include (or indicate to the base station) a capability to transmit the first MAC CE. The wireless device may not expect to transmit (e.g., transmit) the first MAC CE (or delay information) to the base station based on (e.g., responding to) a sending (e.g., transmitting) UE capability that does not indicate a capability to determine / calculate / derive delay information and / or transmit (e.g., transmit) delay information.

[0298] The wireless device may transmit (e.g., transmit) the delay information to the base station via an RRC message. The wireless device may transmit (e.g., transmit) assistance information including the delay information to the base station. One or more configuration parameters may indicate whether the delay information is transmitted (e.g., transmitted) based on the first MAC CE or the RRC message.

[0299] When a serving cell accommodates / remains a large number (e.g., 10 or more) of wireless devices with XR traffic communicating with the base station, the base station may enable / configure the wireless devices (and / or other wireless devices in the serving cell) to report / send / transmit delay information to the base station. The base station may use the delay information of the wireless devices (and / or other wireless devices in the serving cell) to schedule the wireless devices (and / or share UL resources among wireless devices) based on the buffer status (e.g., including data volume and / or data delay information) of the wireless devices (and / or other wireless devices in the serving cell). This may improve UL resource efficiency and increase the amount (e.g., number) of satisfied wireless devices.

[0300] The remainder of one or more PDUs (e.g., already received) may be useless / redundant if the PDU(s) of the one or more PDUs have not been received (at the base station). By enabling / configuring the wireless device to transmit (e.g., transmit) delay information, UL transmissions may become more efficient by reducing the likelihood that the remaining PDUs will be used / less redundant.

[0301] The embodiments described herein may enable a wireless device to appropriately generate / send / transmit a MAC CE for delay information to report / transmit delay information of UL data to a base station. The embodiments described herein may provide advantages such as improving an LCP procedure to determine the priority / order of MAC CEs for delay information. By appropriately receiving a MAC CE for delay information, the base station may timely allocate UL resources to the wireless device (e.g., via a scheduling DCI) to transmit UL data before violating the delay budget of the UL data.

[0302] FIG. 21 illustrates an example embodiment of a logical channel prioritization (LCP) procedure in a wireless communication system according to an aspect of the present disclosure. FIG. 22 illustrates an example embodiment of a logical channel prioritization (LCP) procedure in a wireless communication system according to an aspect of the present disclosure. FIG. 23 illustrates an example embodiment of enhanced BSR MAC CE priorities (e.g., logical channel priorities) according to an aspect of the present disclosure. FIG. 23 may illustrate several examples of the priority / order of enhanced BSR MAC CEs compared to other UL MAC CEs (e.g., LBT-failed MAC CEs, BSR MAC CEs, etc.).

[0303] 21-23 may illustrate example implementations of methods / procedures for, for example, sending (e.g., transmitting) an enhanced buffer size level (in bytes) for a filed n-bit buffer size (e.g., n>8 or n>5) of one or more PDUs in a wireless device (e.g., an XR device) and / or receiving an enhanced BSR at a base station. FIGS. 21-23 may illustrate example embodiments for multiplexing and assembly of MAC PDUs including an enhanced BSR MAC CE. FIGS. 21-23 may illustrate example embodiments for determining whether to generate an enhanced BSR MAC CE or not to perform a new UL transmission. The wireless device may be in an RRC inactive state / mode (e.g., RRC_INACTIVE / IDLE state), and / or an RRC idle mode / state (e.g., RRC_IDLE state), and / or an RRC connected state / mode (e.g., RRC_CONNECTED state). Similar to the embodiments of Figures 18 and 19, as shown in step 2102 of Figure 21 and step 2202 of Figure 22, a wireless device (e.g., UE2120, UE2220) may receive one or more configuration parameters from a base station (e.g., BS2122, BS2222).

[0304] As shown in step 2104 of FIG. 21 and step 2204 of FIG. 22, a wireless device (e.g., UE 2120, UE 2220) may trigger a BSR (e.g., due to arrival / pending of first UL data in one or more logical channels). The wirele...

Claims

1. 1. A method comprising: By wireless devices, delay information for one or more logical channels; and receiving one or more radio resource control configuration parameters indicative of a threshold associated with the delay information; transmitting the indication of the delay information based on a remaining time associated with data for transmission that meets the threshold.

2. wherein the transmitting the indication of the delay information includes transmitting a Medium Access Control (MAC) Control Element (CE) Packet Data Unit (PDU) including a first MAC CE, the method comprising: determining a first MAC CE including delay information associated with the one or more logical channels for a delay reporting procedure; In the MAC PDU, a first logical channel associated with the first MAC CE has a higher priority than a second logical channel associated with a second MAC CE associated with a triggered Buffer Status Report (BSR); and 2. The method of claim 1, further comprising: multiplexing the first MAC CE based on at least one uplink shared channel (UL-SCH) resource accommodating the first MAC CE.

3. determining the delay information based on a minimum remaining time of at least one packet of a logical channel group associated with the data for transmission, the logical channel group including at least one logical channel of the one or more logical channels; The method of claim 1 or 2, wherein the remaining time meeting the threshold comprises the remaining time being less than the threshold.

4. the indication includes a first medium access control (MAC) control element (CE), and the priority of a first logical channel in the first MAC CE is: the priority of the second logical channel of the MAC CE for a Buffer Status Report (BSR), the BSR being a prioritized Sidelink (SL)-BSR; and The method according to any one of claims 1 to 3, wherein the priority of the third logical channel of the MAC CE for Timing Advance Report (TAR) is lower than the priority of the third logical channel.

5. the indication includes a first medium access control (MAC) control element (CE), the first MAC CE including a buffer size corresponding to a first logical channel; the one or more radio resource control configuration parameters indicate a first Buffer Status Report (BSR) table of a plurality of BSR tables for use by at least one logical channel, the first BSR table being compared to a second BSR table of the plurality of BSR tables to enable a refined BSR; The method of any one of claims 1 to 4, wherein the buffer size corresponding to the first logical channel within the at least one logical channel is based on the first BSR table.

6. Indication of the ability to transmit delay information; an indication of the ability to trigger said delayed reporting procedure; or and an indication of a capability to determine a delay budget associated with the one or more logical channels.

7. The method comprises: a first medium access control (MAC) control element (CE) in a MAC packet data unit (PDU), a logical channel of the first MAC CE has a higher priority than a logical channel of a second MAC CE, the second MAC CE corresponding to a triggered buffer status report (BSR); and The method of any one of claims 1 to 6, further comprising multiplexing based on which at least one uplink shared channel (UL-SCH) resource accommodates the first MAC CE.

8. The method comprises: the first MAC CE in a MAC packet data unit (PDU), a logical channel of the first MAC CE has a lower priority than a logical channel of a second MAC CE, and the second MAC CE supports a triggered Listen-Before-Talk (LBT) procedure; and 8. The method of claim 1, further comprising: multiplexing based on which at least one uplink shared channel (UL-SCH) resource accommodates the first MAC CE and the second MAC CE.

9. transmitting the indication of the delay information the remaining time corresponding to at least one packet of the logical channel group, or The buffer size is a first buffer status report (BSR) table based on arrival of first data on a first logical channel; or 9. The method of claim 1, further comprising transmitting at least one of: a buffer size based on at least one of the second BSR table; and a buffer size based on arrival of second data on a second logical channel.

10. the one or more radio resource control configuration parameters indicate a first Buffer Status Report (BSR) table of a plurality of BSR tables for use by at least one logical channel; 10. The method of claim 1, wherein the first BSR table is compared with a second BSR table of the plurality of BSR tables to enable a refined BSR.

11. The method of any one of claims 1 to 10, wherein said transmitting said first MAC CE comprises triggering a scheduling request (SR).

12. The method of any one of claims 1 to 11, wherein the one or more radio resource control configuration parameters configure the wireless device to trigger the delayed reporting of the one or more logical channels.

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

14. 1. A system comprising: A wireless device configured to perform the method of any one of claims 1 to 12; a base station configured to transmit the one or more radio resource control configuration parameters to the wireless device.

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

Images