Scheduling multiple cells in a downlink control information

Abstract

A method can include receiving, by a wireless device, via a first cell, a downlink control information (DCI) format 0_3. The DCI can indicate scheduling of multiple physical uplink shared channels (PUSCHs) in multiple cells with one or more PUSCHs per cell of the multiple cells. The DCI can include a channel state information (CSI) request field. The method can also include performing aperiodic CSI reporting using a first PUSCH of a second cell of the multiple cells. The second cell can be with a smallest serving cell index among the multiple cells and the first PUSCH can be determined as a later scheduled PUSCH in response to two PUSCHs being scheduled by the DCI format 0_3 on the second cell or a penultimate scheduled PUSCH in response to more than two PUSCHs being scheduled by the DCI format 0_3 on the second cell.

Description

Docket No.: 24-1237PCT TITLE Scheduling Multiple Cells in a Downlink Control Information CROSS REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No.63 / 701,934, filed October 1, 2024, which is hereby incorporated by reference in its entirety. BRIEF DESCRIPTION OF THE DRAWINGS

[0002] Examples of several of the various embodiments of the present disclosure are described herein with reference to the drawings.

[0003] FIG.1A and FIG.1B illustrate example mobile communication networks in which embodiments of the present disclosure may be implemented.

[0004] FIG.2A and FIG.2B respectively illustrate a New Radio (NR) user plane and control plane protocol stack.

[0005] FIG.3 illustrates an example of services provided between protocol layers of the NR user plane protocol stack of FIG.2A.

[0006] FIG.4A illustrates an example downlink data flow through the NR user plane protocol stack of FIG. 2A.

[0007] FIG.4B illustrates an example format of a MAC subheader in a MAC PDU.

[0008] FIG.5A and FIG.5B respectively illustrate a mapping between logical channels, transport channels, and physical channels for the downlink and uplink.

[0009] FIG.6 is an example diagram showing RRC state transitions of a UE.

[0010] FIG.7 illustrates an example configuration of an NR frame into which OFDM symbols are grouped.

[0011] FIG.8 illustrates an example configuration of a slot in the time and frequency domain for an NR carrier.

[0012] FIG.9 illustrates an example of bandwidth adaptation using three configured BWPs for an NR carrier.

[0013] FIG.10A illustrates three carrier aggregation configurations with two component carriers.

[0014] FIG.10B illustrates an example of how aggregated cells may be configured into one or more PUCCH groups.

[0015] FIG.11A illustrates an example of an SS / PBCH block structure and location.

[0016] FIG.11B illustrates an example of CSI-RSs that are mapped in the time and frequency domains.

[0017] FIG.12A and FIG.12B respectively illustrate examples of three downlink and uplink beam management procedures.Docket No.: 24-1237PCT

[0018] FIG.13A, FIG.13B, and FIG.13C respectively illustrate a four-step contention-based random access procedure, a two-step contention-free random access procedure, and another two-step random access procedure.

[0019] FIG.14A illustrates an example of CORESET configurations for a bandwidth part.

[0020] FIG.14B illustrates an example of a CCE-to-REG mapping for DCI transmission on a CORESET and PDCCH processing.

[0021] FIG.15 illustrates an example of a wireless device in communication with a base station.

[0022] FIG.16A, FIG.16B, FIG.16C, and FIG.16D illustrate example structures for uplink and downlink transmission.

[0023] FIG.17A, FIG.17B, and FIG.17C illustrate aspects of example embodiments according to the present disclosure.

[0024] FIG.18A and FIG.18B illustrate aspects of example embodiments according to the present disclosure.

[0025] FIG.19 illustrates an aspect of an example embodiment according to the present disclosure.

[0026] FIG.20 illustrates an aspect of an example embodiment according to the present disclosure.

[0027] FIG.21A and FIG.21B illustrate aspects of example embodiments according to the present disclosure.

[0028] FIG.22 illustrates an aspect of an example embodiment according to the present disclosure.

[0029] FIG.23 illustrates an aspect of an example embodiment according to the present disclosure.

[0030] FIG.24 illustrates an aspect of an example embodiment according to the present disclosure.

[0031] FIG.25 illustrates an aspect of an example embodiment according to the present disclosure.

[0032] FIG.26 illustrates an aspect of an example embodiment according to the present disclosure.

[0033] FIG.27 illustrates an aspect of an example embodiment according to the present disclosure.

[0034] FIG.28 illustrates an aspect of an example embodiment according to the present disclosure.

[0035] FIG.29 illustrates an aspect of an example embodiment according to the present disclosure.

[0036] FIG.30 illustrates an aspect of an example embodiment according to the present disclosure.

[0037] FIG.31 illustrates an aspect of an example embodiment according to the present disclosure.

[0038] FIG.32 illustrates an aspect of an example embodiment according to the present disclosure.

[0039] FIG.33A and FIG.33B illustrate aspects of example embodiments according to the present disclosure.

[0040] FIG.34 illustrates an aspect of an example embodiment according to the present disclosure.

[0041] FIG.35 illustrates an aspect of an example embodiment according to the present disclosure.

[0042] FIG.36 illustrates an aspect of an example embodiment according to the present disclosure.Docket No.: 24-1237PCT

[0043] FIG.37A, FIG.37B, FIG.37C, and FIG.37D illustrate aspects of example embodiments according to the present disclosure.

[0044] FIG.38 illustrates an aspect of an example embodiment according to the present disclosure.

[0045] FIG.39 illustrates an aspect of an example embodiment according to the present disclosure. DETAILED DESCRIPTION

[0046] In the present disclosure, various embodiments are presented as examples of how the disclosed techniques may be implemented and / or how the disclosed techniques may be practiced in environments and scenarios. It will be apparent to persons skilled in the relevant art that various changes in form and detail can be made therein without departing from the scope. In fact, after reading the description, it will be apparent to one skilled in the relevant art how to implement alternative embodiments. The present embodiments should not be limited by any of the described exemplary embodiments. The embodiments of the present disclosure will be described with reference to the accompanying drawings. Limitations, features, and / or elements from the disclosed example embodiments may be combined to create further embodiments within the scope of the disclosure. Any figures which highlight the functionality and advantages, are presented for example purposes only. The disclosed architecture is sufficiently flexible and configurable, such that it may be utilized in ways other than that shown. For example, the actions listed in any flowchart may be re-ordered or only optionally used in some embodiments.

[0047] Embodiments may be configured to operate as needed. The disclosed mechanism may be performed when certain criteria are met, for example, in a wireless device, a base station, a radio environment, a network, a combination of the above, and / or the like. Example criteria may be based, at least in part, on for example, wireless device or network node configurations, traffic load, initial system set up, packet sizes, traffic characteristics, a combination of the above, and / or the like. When the one or more criteria are met, various example embodiments may be applied. Therefore, it may be possible to implement example embodiments that selectively implement disclosed protocols.

[0048] A base station may communicate with a mix of wireless devices. Wireless devices and / or base stations may support multiple technologies, and / or multiple releases of the same technology. Wireless devices may have some specific capability(ies) depending on wireless device category and / or capability(ies). When this disclosure refers to a base station communicating with a plurality of wireless devices, this disclosure may refer to a subset of the total wireless devices in a coverage area. This disclosure may refer to, for example, a plurality of wireless devices of a given LTE or 5G release with a given capability and in a given sector of the base station. The plurality of wireless devices in this disclosure may refer to a selected plurality of wireless devices, and / or a subset of total wireless devices in a coverage area which perform according to disclosed methods, and / or the like. There may be a plurality of base stations or a plurality of wireless devices in a coverage area that may not comply with the disclosedDocket No.: 24-1237PCT methods, for example, those wireless devices or base stations may perform based on older releases of LTE or 5G technology.

[0049] In this disclosure, “a” and “an” and similar phrases are to be interpreted as “at least one” and “one or more.” Similarly, any term that ends with the suffix “(s)” is to be interpreted as “at least one” and “one or more.” In this disclosure, the term “may” is to be interpreted as “may, for example.” In other words, the term “may” is indicative that the phrase following the term “may” is an example of one of a multitude of suitable possibilities that may, or may not, be employed by one or more of the various embodiments. The terms “comprises” and “consists of”, as used herein, enumerate one or more components of the element being described. The term “comprises” is interchangeable with “includes” and does not exclude unenumerated components from being included in the element being described. By contrast, “consists of” provides a complete enumeration of the one or more components of the element being described. The term “based on”, as used herein, should be interpreted as “based at least in part on” rather than, for example, “based solely on”. The term “and / or” as used herein represents any possible combination of enumerated elements. For example, “A, B, and / or C” may represent A; B; C; A and B; A and C; B and C; or A, B, and C.

[0050] If A and B are sets and every element of A is an element of B, A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B = {cell1, cell2} are: {cell1}, {cell2}, and {cell1, cell2}. The phrase “based on” (or equally “based at least on”) is indicative that the phrase following the term “based on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “in response to” (or equally “in response at least to”) is indicative that the phrase following the phrase “in response to” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “depending on” (or equally “depending at least to”) is indicative that the phrase following the phrase “depending on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “employing / using” (or equally “employing / using at least”) is indicative that the phrase following the phrase “employing / using” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments.

[0051] The term configured may relate to the capacity of a device whether the device is in an operational or non-operational state. Configured may refer to specific settings in a device that affect or implement the operational characteristics of the device whether the device is in an operational or non-operational state. In other words, the hardware, software, firmware, registers, memory values, and / or the like may be “configured” within a device, whether the device is in an operational or nonoperational state, to provide the device with specific characteristics. Terms such as “a control message to cause in a device” may mean thatDocket No.: 24-1237PCT a control message has parameters that may be used to configure specific characteristics or may be used to implement certain actions in the device, whether the device is in an operational or non-operational state.

[0052] In this disclosure, parameters (or equally called, fields, or Information elements: IEs) may comprise one or more information objects, and an information object may comprise one or more other objects. For example, if parameter (IE) N comprises parameter (IE) M, and parameter (IE) M comprises parameter (IE) K, and parameter (IE) K comprises parameter (information element) J. Then, for example, N comprises K, and N comprises J. In an example embodiment, when one or more messages comprise a plurality of parameters, it implies that a parameter in the plurality of parameters is in at least one of the one or more messages, but does not have to be in each of the one or more messages.

[0053] Many features presented are described as being optional through the use of “may” or the use of parentheses. For the sake of brevity and legibility, the present disclosure does not explicitly recite each and every permutation that may be obtained by choosing from the set of optional features. The present disclosure is to be interpreted as explicitly disclosing all such permutations. For example, a system described as having three optional features may be embodied in seven ways, namely with just one of the three possible features, with any two of the three possible features or with three of the three possible features.

[0054] Many of the elements described in the disclosed embodiments may be implemented as modules. A module is defined here as an element that performs a defined function and has a defined interface to other elements. The modules described in this disclosure may be implemented in hardware, software in combination with hardware, firmware, wetware (e.g., hardware with a biological element), or a combination thereof, which may be behaviorally equivalent. For example, modules may be implemented as a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, MATLAB or the like) or a modeling / simulation program such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript. It may be possible to implement modules using physical hardware that incorporates discrete or programmable analog, digital and / or quantum hardware. Examples of programmable hardware comprise: computers, microcontrollers, microprocessors, application-specific integrated circuits (ASICs); field programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers and microprocessors are programmed using languages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDs are often programmed using hardware description languages (HDL) such as VHSIC hardware description language (VHDL) or Verilog that configure connections between internal hardware modules with lesser functionality on a programmable device. The mentioned technologies are often used in combination to achieve the result of a functional module.Docket No.: 24-1237PCT

[0055] FIG.1A illustrates an example of a mobile communication network 100 in which embodiments of the present disclosure may be implemented. The mobile communication network 100 may be, for example, a public land mobile network (PLMN) run by a network operator. As illustrated in FIG.1A, the mobile communication network 100 includes a core network (CN) 102, a radio access network (RAN) 104, and a wireless device 106.

[0056] The CN 102 may provide the wireless device 106 with an interface to one or more data networks (DNs), such as public DNs (e.g., the Internet), private DNs, and / or intra-operator DNs. As part of the interface functionality, the CN 102 may set up end-to-end connections between the wireless device 106 and the one or more DNs, authenticate the wireless device 106, and provide charging functionality.

[0057] The RAN 104 may connect the CN 102 to the wireless device 106 through radio communications over an air interface. As part of the radio communications, the RAN 104 may provide scheduling, radio resource management, and retransmission protocols. The communication direction from the RAN 104 to the wireless device 106 over the air interface is known as the downlink and the communication direction from the wireless device 106 to the RAN 104 over the air interface is known as the uplink. Downlink transmissions may be separated from uplink transmissions using frequency division duplexing (FDD), time- division duplexing (TDD), and / or some combination of the two duplexing techniques.

[0058] The term wireless device may be used throughout this disclosure to refer to and encompass any mobile device or fixed (non-mobile) device for which wireless communication is needed or usable. For example, a wireless device may be a telephone, smart phone, tablet, computer, laptop, sensor, meter, wearable device, Internet of Things (IoT) device, vehicle roadside unit (RSU), relay node, automobile, and / or any combination thereof. The term wireless device encompasses other terminology, including user equipment (UE), user terminal (UT), access terminal (AT), mobile station, handset, wireless transmit and receive unit (WTRU), and / or wireless communication device.

[0059] The RAN 104 may include one or more base stations (not shown). The term base station may be used throughout this disclosure to refer to and encompass a Node B (associated with UMTS and / or 3G standards), an Evolved Node B (eNB, associated with E-UTRA and / or 4G standards), a remote radio head (RRH), a baseband processing unit coupled to one or more 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, associated with NR and / or 5G standards), an access point (AP, associated with, for example, Wi-Fi or any other suitable wireless communication standard), and / or any combination thereof. A base station may comprise at least one gNB Central Unit (gNB-CU) and at least one a gNB Distributed Unit (gNB-DU).

[0060] A base station included in the RAN 104 may include one or more sets of antennas for communicating with the wireless device 106 over the air interface. For example, one or more of the baseDocket No.: 24-1237PCT stations may include three sets of antennas to respectively control three cells (or sectors). The size of a cell may be determined by a range at which a receiver (e.g., a base station receiver) can successfully receive the transmissions from a transmitter (e.g., a wireless device transmitter) operating in the cell. Together, the cells of the base stations may provide radio coverage to the wireless device 106 over a wide geographic area to support wireless device mobility.

[0061] In addition to three-sector sites, other implementations of base stations are possible. For example, one or more of the base stations in the RAN 104 may be implemented as a sectored site with more or less than three sectors. One or more of the base stations in the RAN 104 may be implemented as an access point, as a baseband processing unit coupled to several remote radio heads (RRHs), and / or as a repeater or relay node used to extend the coverage area of a donor node. A baseband processing unit coupled to RRHs may be part of a centralized or cloud RAN architecture, where the baseband processing unit may be either centralized in a pool of baseband processing units or virtualized. A repeater node may amplify and rebroadcast a radio signal received from a donor node. A relay node may perform the same / similar functions as a repeater node but may decode the radio signal received from the donor node to remove noise before amplifying and rebroadcasting the radio signal.

[0062] The RAN 104 may be deployed as a homogenous network of macrocell base stations that have similar antenna patterns and similar high-level transmit powers. The RAN 104 may be deployed as a heterogeneous network. In heterogeneous networks, small cell base stations may be used to provide small coverage areas, for example, coverage areas that overlap with the comparatively larger coverage areas provided by macrocell base stations. The small coverage areas may be provided in areas with high data traffic (or so-called “hotspots”) or in areas with weak macrocell coverage. Examples of small cell base stations include, in order of decreasing coverage area, microcell base stations, picocell base stations, and femtocell base stations or home base stations.

[0063] The Third-Generation Partnership Project (3GPP) was formed in 1998 to provide global standardization of specifications for mobile communication networks similar to the mobile communication network 100 in FIG.1A. To date, 3GPP has produced specifications for three generations of mobile networks: a third generation (3G) network known as Universal Mobile Telecommunications System (UMTS), a fourth generation (4G) network known as Long-Term Evolution (LTE), and a fifth generation (5G) network known as 5G System (5GS). Embodiments of the present disclosure are described with reference to the RAN of a 3GPP 5G network, referred to as next-generation RAN (NG-RAN). Embodiments may be applicable to RANs of other mobile communication networks, such as the RAN 104 in FIG.1A, the RANs of earlier 3G and 4G networks, and those of future networks yet to be specified (e.g., a 3GPP 6G network). NG-RAN implements 5G radio access technology known as New Radio (NR) and may beDocket No.: 24-1237PCT provisioned to implement 4G radio access technology or other radio access technologies, including non- 3GPP radio access technologies.

[0064] FIG.1B illustrates another example mobile communication network 150 in which embodiments of the present disclosure may be implemented. Mobile communication network 150 may be, for example, a PLMN run by a network operator. As illustrated in FIG.1B, mobile communication network 150 includes a 5G core network (5G-CN) 152, an NG-RAN 154, and UEs 156A and 156B (collectively UEs 156). These components may be implemented and operate in the same or similar manner as corresponding components described with respect to FIG.1A.

[0065] The 5G-CN 152 provides the UEs 156 with an interface to one or more DNs, such as public DNs (e.g., the Internet), private DNs, and / or intra-operator DNs. As part of the interface functionality, the 5G-CN 152 may set up end-to-end connections between the UEs 156 and the one or more DNs, authenticate the UEs 156, and provide charging functionality. Compared to the CN of a 3GPP 4G network, the basis of the 5G-CN 152 may be a service-based architecture. This means that the architecture of the nodes making up the 5G-CN 152 may be defined as network functions that offer services via interfaces to other network functions. The network functions of the 5G-CN 152 may be implemented in several ways, including as network elements on dedicated or shared hardware, as software instances running on dedicated or shared hardware, or as virtualized functions instantiated on a platform (e.g., a cloud-based platform).

[0066] As illustrated in FIG.1B, the 5G-CN 152 includes an Access and Mobility Management Function (AMF) 158A and a User Plane Function (UPF) 158B, which are shown as one component AMF / UPF 158 in FIG.1B for ease of illustration. The UPF 158B may serve as a gateway between the NG-RAN 154 and the one or more DNs. The UPF 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 the one or more DNs, quality of service (QoS) handling for the user plane (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink traffic verification), downlink packet buffering, and downlink data notification triggering. The UPF 158B may serve as an anchor point for intra- / inter-Radio Access Technology (RAT) mobility, an external protocol (or packet) data unit (PDU) session point of interconnect to the one or more DNs, and / or a branching point to support a multi-homed PDU session. The UEs 156 may be configured to receive services through a PDU session, which is a logical connection between a UE and a DN.

[0067] The AMF 158A may perform functions such as Non-Access Stratum (NAS) signaling termination, NAS signaling security, Access Stratum (AS) security control, inter-CN node signaling for mobility between 3GPP access networks, idle mode UE reachability (e.g., control and execution of paging retransmission), registration area management, intra-system and inter-system mobility support, access authentication, access authorization including checking of roaming rights, mobility management control (subscription andDocket No.: 24-1237PCT policies), network slicing support, and / or session management function (SMF) selection. NAS may refer to the functionality operating between a CN and a UE, and AS may refer to the functionality operating between the UE and a RAN.

[0068] The 5G-CN 152 may include one or more additional network functions that are not shown in FIG. 1B for the sake of clarity. For example, the 5G-CN 152 may include one or more 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), and / or an Authentication Server Function (AUSF).

[0069] The NG-RAN 154 may connect the 5G-CN 152 to the UEs 156 through radio communications over the air interface. The NG-RAN 154 may include one or more gNBs, illustrated as gNB 160A and gNB 160B (collectively gNBs 160) and / or one or more ng-eNBs, illustrated as ng-eNB 162A and ng-eNB 162B (collectively ng-eNBs 162). The gNBs 160 and ng-eNBs 162 may be more generically referred to as base stations. The gNBs 160 and ng-eNBs 162 may include one or more sets of antennas for communicating with the UEs 156 over an air interface. For example, one or more of the gNBs 160 and / or one or more of the ng-eNBs 162 may include three sets of antennas to respectively control three cells (or sectors). Together, the cells of the gNBs 160 and the ng-eNBs 162 may provide radio coverage to the UEs 156 over a wide geographic area to support UE mobility.

[0070] As shown in FIG.1B, the gNBs 160 and / or the ng-eNBs 162 may be connected to the 5G-CN 152 by means of an NG interface and to other base stations by 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. The gNBs 160 and / or the ng-eNBs 162 may be connected to the UEs 156 by means of a Uu interface. For example, as illustrated in FIG.1B, gNB 160A may be connected to the UE 156A by means of a Uu interface. The NG, Xn, and Uu interfaces are associated with a protocol stack. The protocol stacks associated with the interfaces may be used by the network elements in FIG.1B to exchange data and signaling messages and may include two planes: a user plane and a control plane. The user plane may handle data of interest to a user. The control plane may handle signaling messages of interest to the network elements.

[0071] The gNBs 160 and / or the ng-eNBs 162 may be connected to one or more AMF / UPF functions of the 5G-CN 152, such as the AMF / UPF 158, by means of one or more NG interfaces. For example, the gNB 160A may be connected to the UPF 158B of the AMF / UPF 158 by means of an NG-User plane (NG-U) interface. The NG-U interface may provide delivery (e.g., non-guaranteed delivery) of user plane PDUs between the gNB 160A and the UPF 158B. The gNB 160A may be connected to the AMF 158A by means of an NG-Control plane (NG-C) interface. The NG-C interface may provide, for example, NG interfaceDocket No.: 24-1237PCT management, UE context management, UE mobility management, transport of NAS messages, paging, PDU session management, and configuration transfer and / or warning message transmission.

[0072] The gNBs 160 may provide NR user plane and control plane protocol terminations towards the UEs 156 over the Uu interface. For example, the gNB 160A may provide NR user plane and control plane protocol terminations toward the UE 156A over a Uu interface associated with a first protocol stack. The ng- eNBs 162 may provide Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminations towards the UEs 156 over a Uu interface, where E-UTRA refers to the 3GPP 4G radio-access technology. For example, the ng-eNB 162B may provide E-UTRA user plane and control plane protocol terminations towards the UE 156B over a Uu interface associated with a second protocol stack.

[0073] The 5G-CN 152 was described as being configured to handle NR and 4G radio accesses. It will be appreciated by one of ordinary skill in the art that it may be possible for NR to connect to a 4G core network in a mode known as “non-standalone operation.” In non-standalone operation, a 4G core network is used to provide (or at least support) control-plane functionality (e.g., initial access, mobility, and paging). Although only one AMF / UPF 158 is shown in FIG.1B, one gNB or ng-eNB may be connected to multiple AMF / UPF nodes to provide redundancy and / or to load share across the multiple AMF / UPF nodes.

[0074] As discussed, an interface (e.g., Uu, Xn, and NG interfaces) between the network elements in FIG. 1B may be associated with a protocol stack that the network elements use to exchange data and signaling messages. A protocol stack may include two planes: a user plane and a control plane. The user plane may handle data of interest to a user, and the control plane may handle signaling messages of interest to the network elements.

[0075] FIG.2A and FIG.2B respectively illustrate examples of NR user plane and NR control plane protocol stacks for the Uu interface that lies between a UE 210 and a gNB 220. The protocol stacks illustrated in FIG.2A and FIG.2B may be the same or similar to those used for the Uu interface between, for example, the UE 156A and the gNB 160A shown in FIG.1B.

[0076] FIG.2A illustrates a NR user plane protocol stack comprising five layers implemented in the UE 210 and the gNB 220. At the bottom of the protocol stack, physical layers (PHYs) 211 and 221 may provide transport services to the higher layers of the protocol stack and may correspond to layer 1 of the Open Systems Interconnection (OSI) model. The next four protocols above PHYs 211 and 221 comprise media access control layers (MACs) 212 and 222, radio link control layers (RLCs) 213 and 223, packet data convergence protocol layers (PDCPs) 214 and 224, and service data application protocol layers (SDAPs) 215 and 225. Together, these four protocols may make up layer 2, or the data link layer, of the OSI model.

[0077] FIG.3 illustrates an example of services provided between protocol layers of the NR user plane protocol stack. Starting from the top of FIG.2A and FIG.3, the SDAPs 215 and 225 may perform QoS flowDocket No.: 24-1237PCT handling. The UE 210 may receive services through a PDU session, which may be a logical connection between the UE 210 and a DN. The PDU session may have one or more QoS flows. A UPF of a CN (e.g., the UPF 158B) may map IP packets to the one or more QoS flows of the PDU session based on QoS requirements (e.g., in terms of delay, data rate, and / or error rate). The SDAPs 215 and 225 may perform mapping / de-mapping between the one or more QoS flows and one or more data radio bearers. The mapping / de-mapping between the QoS flows and the data radio bearers may be determined by the SDAP 225 at the gNB 220. The SDAP 215 at the UE 210 may be informed of the mapping between the QoS flows and the data radio bearers through reflective mapping or control signaling received from the gNB 220. For reflective mapping, the SDAP 225 at the gNB 220 may mark the downlink packets with a QoS flow indicator (QFI), which may be observed by the SDAP 215 at the UE 210 to determine the mapping / de-mapping between the QoS flows and the data radio bearers.

[0078] The PDCPs 214 and 224 may perform header compression / decompression to reduce the amount of data that needs to be transmitted over the air interface, ciphering / deciphering to prevent unauthorized decoding of data transmitted over the air interface, and integrity protection (to ensure control messages originate from intended sources. The PDCPs 214 and 224 may perform retransmissions of undelivered packets, in-sequence delivery and reordering of packets, and removal of packets received in duplicate due to, for example, an intra-gNB handover. The PDCPs 214 and 224 may perform packet duplication to improve the likelihood of the packet being received and, at the receiver, remove any duplicate packets. Packet duplication may be useful for services that require high reliability.

[0079] Although not shown in FIG.3, PDCPs 214 and 224 may perform mapping / de-mapping between a split radio bearer and RLC channels in a dual connectivity scenario. Dual connectivity is a technique that allows a UE to connect to two cells or, more generally, two cell groups: a master cell group (MCG) and a secondary cell group (SCG). A split bearer is when a single radio bearer, such as one of the radio bearers provided by the PDCPs 214 and 224 as a service to the SDAPs 215 and 225, is handled by cell groups in dual connectivity. The PDCPs 214 and 224 may map / de-map the split radio bearer between RLC channels belonging to cell groups.

[0080] The RLCs 213 and 223 may perform segmentation, retransmission through Automatic Repeat Request (ARQ), and removal of duplicate data units received from MACs 212 and 222, respectively. The RLCs 213 and 223 may support three transmission modes: transparent mode (TM); unacknowledged mode (UM); and acknowledged mode (AM). Based on the transmission mode an RLC is operating, the RLC may perform one or more of the noted functions. The RLC configuration may be per logical channel with no dependency on numerologies and / or Transmission Time Interval (TTI) durations. As shown in FIG.3, the RLCs 213 and 223 may provide RLC channels as a service to PDCPs 214 and 224, respectively.Docket No.: 24-1237PCT

[0081] The MACs 212 and 222 may perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. The multiplexing / demultiplexing may include multiplexing / demultiplexing of data units, belonging to the one or more logical channels, into / from Transport Blocks (TBs) delivered to / from the PHYs 211 and 221. The MAC 222 may be configured to perform scheduling, scheduling information reporting, and priority handling between UEs by means of dynamic scheduling. Scheduling may be performed in the gNB 220 (at the MAC 222) for downlink and uplink. The MACs 212 and 222 may be configured to perform error correction through Hybrid Automatic Repeat Request (HARQ) (e.g., one HARQ entity per carrier in case of Carrier Aggregation (CA)), priority handling between logical channels of the UE 210 by means of logical channel prioritization, and / or padding. The MACs 212 and 222 may support one or more numerologies and / or transmission timings. In an example, mapping restrictions in a logical channel prioritization may control which numerology and / or transmission timing a logical channel may use. As shown in FIG.3, the MACs 212 and 222 may provide logical channels as a service to the RLCs 213 and 223.

[0082] The PHYs 211 and 221 may perform mapping of transport channels to physical channels and digital and analog signal processing functions for sending and receiving information over the air interface. These digital and analog signal processing functions may include, for example, coding / decoding and modulation / demodulation. The PHYs 211 and 221 may perform multi-antenna mapping. As shown in FIG. 3, the PHYs 211 and 221 may provide one or more transport channels as a service to the MACs 212 and 222.

[0083] FIG.4A illustrates an example downlink data flow through the NR user plane protocol stack. FIG. 4A illustrates a downlink data flow of three IP packets (n, n+1, and m) through the NR user plane protocol stack to generate two TBs at the gNB 220. An uplink data flow through the NR user plane protocol stack may be similar to the downlink data flow depicted in FIG.4A.

[0084] The downlink data flow of FIG.4A begins when SDAP 225 receives the three IP packets from one or more QoS flows and maps the three packets to radio bearers. In FIG.4A, the SDAP 225 maps IP packets n and n+1 to a first radio bearer 402 and maps IP packet m to a second radio bearer 404. An SDAP header (labeled with an “H” in FIG.4A) is added to an IP packet. The data unit from / to a higher protocol layer is referred to as a service data unit (SDU) of the lower protocol layer and the data unit to / from a lower protocol layer is referred to as a protocol data unit (PDU) of the higher protocol layer. As shown in FIG.4A, the data unit from the SDAP 225 is an SDU of lower protocol layer PDCP 224 and is a PDU of the SDAP 225.

[0085] The remaining protocol layers in FIG.4A may perform their associated functionality (e.g., with respect to FIG.3), add corresponding headers, and forward their respective outputs to the next lower layer. For example, the PDCP 224 may perform IP-header compression and ciphering and forward its output toDocket No.: 24-1237PCT the RLC 223. The RLC 223 may optionally perform segmentation (e.g., as shown for IP packet m in FIG. 4A) and forward its output to the MAC 222. The MAC 222 may multiplex a number of RLC PDUs and may attach a MAC subheader to an RLC PDU to form a transport block. In NR, the MAC subheaders may be distributed across the MAC PDU, as illustrated in FIG.4A. In LTE, the MAC subheaders may be entirely located at the beginning of the MAC PDU. The NR MAC PDU structure may reduce processing time and associated latency because the MAC PDU subheaders may be computed before the full MAC PDU is assembled.

[0086] FIG.4B illustrates an example format of a MAC subheader in a MAC PDU. The MAC subheader includes: an SDU length field for indicating the length (e.g., in bytes) of the MAC SDU to which the MAC subheader corresponds; a logical channel identifier (LCID) field for identifying the logical channel from which the MAC SDU originated to aid 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.

[0087] FIG.4B further illustrates MAC control elements (CEs) inserted into the MAC PDU by a MAC, such as MAC 212 or MAC 222. For example, FIG.4B illustrates two MAC CEs inserted into the MAC PDU. MAC CEs may be inserted at the beginning of a MAC PDU for downlink transmissions (as shown in FIG.4B) and at the end of a MAC PDU for uplink transmissions. MAC CEs may be used for in-band control signaling. Example MAC CEs include: scheduling-related MAC CEs, such as buffer status reports and power headroom reports; activation / deactivation MAC CEs, such as those for activation / deactivation of PDCP duplication detection, channel state information (CSI) reporting, sounding reference signal (SRS) transmission, and prior configured components; discontinuous reception (DRX) related MAC CEs; timing advance MAC CEs; and random access related MAC CEs. A MAC CE may be preceded by a MAC subheader with a similar format as described for MAC SDUs and may be identified with a reserved value in the LCID field that indicates the type of control information included in the MAC CE.

[0088] Before describing the NR control plane protocol stack, logical channels, transport channels, and physical channels are first described as well as a mapping between the channel types. One or more of the channels may be used to carry out functions associated with the NR control plane protocol stack described later below.

[0089] FIG.5A and FIG.5B illustrate, for downlink and uplink respectively, a mapping between logical channels, transport channels, and physical channels. Information is passed through channels between the RLC, the MAC, and the PHY of the NR protocol stack. A logical channel may be used between the RLC and the MAC and may be classified as a control channel that carries control and configuration information in the NR control plane or as a traffic channel that carries data in the NR user plane. A logical channel may be classified as a dedicated logical channel that is dedicated to a specific UE or as a common logicalDocket No.: 24-1237PCT channel that may be used by more than one UE. A logical channel may also be defined by the type of information it carries. The set of logical channels defined by NR includes, for example:

[0090] -- a paging control channel (PCCH) for carrying paging messages used to page a UE whose location is not known to the network on a cell level;

[0091] -- a broadcast control channel (BCCH) for carrying system information messages in the form of a master information block (MIB) and several system information blocks (SIBs), wherein the system information messages may be used by the UEs to obtain information about how a cell is configured and how to operate within the cell;

[0092] -- a common control channel (CCCH) for carrying control messages together with random access;

[0093] -- a dedicated control channel (DCCH) for carrying control messages to / from a specific the UE to configure the UE; and

[0094] -- a dedicated traffic channel (DTCH) for carrying user data to / from a specific the UE.

[0095] Transport channels are used between the MAC and PHY layers and may be defined by how the information they carry is transmitted over the air interface. The set of transport channels defined by NR includes, for example:

[0096] -- a paging channel (PCH) for carrying paging messages that originated from the PCCH;

[0097] -- a broadcast channel (BCH) for carrying the MIB from the BCCH;

[0098] -- a downlink shared channel (DL-SCH) for carrying downlink data and signaling messages, including the SIBs from the BCCH;

[0099] -- an uplink shared channel (UL-SCH) for carrying uplink data and signaling messages; and

[0100] -- a random access channel (RACH) for allowing a UE to contact the network without any prior scheduling.

[0101] The PHY may use physical channels to pass information between processing levels of the PHY. A physical channel may have an associated set of time-frequency resources for carrying the information of one or more transport channels. The PHY may generate control information to support the low-level operation of the PHY and provide the control information to the lower levels of the PHY via physical control channels, known as L1 / L2 control channels. The set of physical channels and physical control channels defined by NR includes, for example:

[0102] -- a physical broadcast channel (PBCH) for carrying the MIB from the BCH;

[0103] -- a physical downlink shared channel (PDSCH) for carrying downlink data and signaling messages from the DL-SCH, as well as paging messages from the PCH;

[0104] -- a physical downlink control channel (PDCCH) for carrying downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling grants, and uplink power control commands;Docket No.: 24-1237PCT

[0105] -- a physical uplink shared channel (PUSCH) for carrying uplink data and signaling messages from the UL-SCH and in some instances uplink control information (UCI) as described below;

[0106] -- a physical uplink control channel (PUCCH) for carrying UCI, which may include HARQ acknowledgments, channel quality indicators (CQI), pre-coding matrix indicators (PMI), rank indicators (RI), and scheduling requests (SR); and

[0107] -- a physical random access channel (PRACH) for random access.

[0108] Similar to the physical control channels, the physical layer generates physical signals to support the low-level operation of the physical layer. As shown in FIG.5A and FIG.5B, the physical layer signals defined by NR include: primary synchronization signals (PSS), secondary synchronization signals (SSS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), sounding reference signals (SRS), and phase-tracking reference signals (PT-RS). These physical layer signals will be described in greater detail below.

[0109] FIG.2B illustrates an example NR control plane protocol stack. As shown in FIG.2B, the NR control plane protocol stack may use the same / similar first four protocol layers as the example NR user plane protocol stack. These four protocol layers include the PHYs 211 and 221, the MACs 212 and 222, the RLCs 213 and 223, and the PDCPs 214 and 224. Instead of having the SDAPs 215 and 225 at the top of the stack as in the NR user plane protocol stack, the NR control plane stack has radio resource controls (RRCs) 216 and 226 and NAS protocols 217 and 237 at the top of the NR control plane protocol stack.

[0110] The NAS protocols 217 and 237 may provide control plane functionality between the UE 210 and the AMF 230 (e.g., the AMF 158A) or, more generally, between the UE 210 and the CN. The NAS protocols 217 and 237 may provide control plane functionality between the UE 210 and the AMF 230 via signaling messages, referred to as NAS messages. There is no direct path between the UE 210 and the AMF 230 through which the NAS messages can be transported. The NAS messages may be transported using the AS of the Uu and NG interfaces. NAS protocols 217 and 237 may provide control plane functionality such as authentication, security, connection setup, mobility management, and session management.

[0111] The RRCs 216 and 226 may provide control plane functionality between the UE 210 and the gNB 220 or, more generally, between the UE 210 and the RAN. The RRCs 216 and 226 may provide control plane functionality between the UE 210 and the gNB 220 via signaling messages, referred to as RRC messages. RRC messages may be transmitted between the UE 210 and the RAN using signaling radio bearers and the same / similar PDCP, RLC, MAC, and PHY protocol layers. The MAC may multiplex control- plane and user-plane data into the same transport block (TB). The RRCs 216 and 226 may provide control plane functionality such as: broadcast of system information related to AS and NAS; paging initiated by the CN or the RAN; establishment, maintenance and release of an RRC connection between the UE 210 and the RAN; security functions including key management; establishment, configuration, maintenance andDocket No.: 24-1237PCT release of signaling radio bearers and data radio bearers; mobility functions; QoS management functions; the UE measurement reporting and control of the reporting; detection of and recovery from radio link failure (RLF); and / or NAS message transfer. As part of establishing an RRC connection, RRCs 216 and 226 may establish an RRC context, which may involve configuring parameters for communication between the UE 210 and the RAN.

[0112] FIG.6 is an example diagram showing RRC state transitions of a UE. The UE may be the same or similar to the wireless device 106 depicted in FIG.1A, the UE 210 depicted in FIG.2A and FIG.2B, or any other wireless device described in the present disclosure. As illustrated in FIG.6, a UE may be in at least one of three RRC states: RRC connected 602 (e.g., RRC_CONNECTED), RRC idle 604 (e.g., RRC_IDLE), and RRC inactive 606 (e.g., RRC_INACTIVE).

[0113] In RRC connected 602, the UE has an established RRC context and may have at least one RRC connection with a base station. The base station may be similar to one of the one or more base stations included in the RAN 104 depicted in FIG.1A, one of the gNBs 160 or ng-eNBs 162 depicted in FIG.1B, the gNB 220 depicted in FIG.2A and FIG.2B, or any other base station described in the present disclosure. The base station with which the UE is connected may have the RRC context for the UE. The RRC context, referred to as the UE context, may comprise parameters for communication between the UE and the base station. These parameters may include, for example: one or more AS contexts; one or more radio link configuration parameters; bearer configuration information (e.g., relating to a data radio bearer, signaling radio bearer, logical channel, QoS flow, and / or PDU session); security information; and / or PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information. While in RRC connected 602, mobility of the UE may be managed by the RAN (e.g., the RAN 104 or the NG-RAN 154). The UE may measure the signal levels (e.g., reference signal levels) from a serving cell and neighboring cells and report these measurements to the base station currently serving the UE. The UE’s serving base station may request a handover to a cell of one of the neighboring base stations based on the reported measurements. The RRC state may transition from RRC connected 602 to RRC idle 604 through a connection release procedure 608 or to RRC inactive 606 through a connection inactivation procedure 610.

[0114] In RRC idle 604, an RRC context may not be established for the UE. In RRC idle 604, the UE may not have an RRC connection with the base station. While in RRC idle 604, the UE may be in a sleep state for the majority of the time (e.g., to conserve battery power). The UE may wake up periodically (e.g., once in every discontinuous reception cycle) to monitor for paging messages from the RAN. Mobility of the UE may be managed by the UE through a procedure known as cell reselection. The RRC state may transition from RRC idle 604 to RRC connected 602 through a connection establishment procedure 612, which may involve a random access procedure as discussed in greater detail below.Docket No.: 24-1237PCT

[0115] In RRC inactive 606, the RRC context previously established is maintained in the UE and the base station. This allows for a fast transition to RRC connected 602 with reduced signaling overhead as compared to the transition from RRC idle 604 to RRC connected 602. While in RRC inactive 606, the UE may be in a sleep state and mobility of the UE may be managed by the UE through cell reselection. The RRC state may transition from RRC inactive 606 to RRC connected 602 through a connection resume procedure 614 or to RRC idle 604 though a connection release procedure 616 that may be the same as or similar to connection release procedure 608.

[0116] An RRC state may be associated with a mobility management mechanism. In RRC idle 604 and RRC inactive 606, mobility is managed by the UE through cell reselection. The purpose of mobility management in RRC idle 604 and RRC inactive 606 is to allow the network to be able to notify the UE of an event via a paging message without having to broadcast the paging message over the entire mobile communications network. The mobility management mechanism used in RRC idle 604 and RRC inactive 606 may allow the network to track the UE on a cell-group level so that the paging message may be broadcast over the cells of the cell group that the UE currently resides within instead of the entire mobile communication network. The mobility management mechanisms for RRC idle 604 and RRC inactive 606 track the UE on a cell-group level. They may do so using different granularities of grouping. For example, there may be 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, referred to as a tracking area and identified by a tracking area identifier (TAI).

[0117] Tracking areas may be used to track the UE at the CN level. The CN (e.g., the CN 102 or the 5G-CN 152) may provide the UE with a list of TAIs associated with a UE registration area. If the UE moves, through cell reselection, to a cell associated with a TAI not included in the list of TAIs associated with the UE registration area, the UE may perform a registration update with the CN to allow the CN to update the UE’s location and provide the UE with a new the UE registration area.

[0118] RAN areas may be used to track the UE at the RAN level. For a UE in RRC inactive 606 state, the UE may be assigned a RAN notification area. A RAN notification area may comprise one or more cell identities, a list of RAIs, or a list of TAIs. In an example, a base station may belong to one or more RAN notification areas. In an example, a cell may belong to one or more RAN notification areas. If the UE moves, through cell reselection, to a cell not included in the RAN notification area assigned to the UE, the UE may perform a notification area update with the RAN to update the UE’s RAN notification area.

[0119] A base station storing an RRC context for a UE or a last serving base station of the UE may be referred to as an anchor base station. An anchor base station may maintain an RRC context for the UE at least during a period of time that the UE stays in a RAN notification area of the anchor base station and / or during a period of time that the UE stays in RRC inactive 606.Docket No.: 24-1237PCT

[0120] A gNB, such as gNBs 160 in FIG.1B, may be split into two parts: a central unit (gNB-CU), and one or more distributed units (gNB-DU). A gNB-CU may be coupled to one or more gNB-DUs using an F1 interface. The gNB-CU may comprise the RRC, the PDCP, and the SDAP. A gNB-DU may comprise the RLC, the MAC, and the PHY.

[0121] In NR, the physical signals and physical channels (discussed with respect to FIG.5A and FIG.5B) may be mapped onto orthogonal frequency divisional multiplexing (OFDM) symbols. OFDM is a multicarrier communication scheme that transmits data over F orthogonal subcarriers (or tones). Before transmission, the data may be mapped to a series of complex symbols (e.g., M-quadrature amplitude modulation (M- QAM) or M-phase shift keying (M-PSK) symbols), referred to as source symbols, and divided into F parallel symbol streams. The F parallel symbol streams may be treated as though they are in the frequency domain and used as inputs to an Inverse Fast Fourier Transform (IFFT) block that transforms them into the time domain. The IFFT block may take in F source symbols at a time, one from each of the F parallel symbol streams, and use each source symbol to modulate the amplitude and phase of one of F sinusoidal basis functions that correspond to the F orthogonal subcarriers. The output of the IFFT block may be F time- domain samples that represent the summation of the F orthogonal subcarriers. The F time-domain samples may form a single OFDM symbol. After some processing (e.g., addition of a cyclic prefix) and up- conversion, an OFDM symbol provided by the IFFT block may be transmitted over the air interface on a carrier frequency. The F parallel symbol streams may be mixed using an FFT block before being processed by the IFFT block. This operation produces Discrete Fourier Transform (DFT)-precoded OFDM symbols and may be used by UEs in the uplink to reduce the peak to average power ratio (PAPR). Inverse processing may be performed on the OFDM symbol at a receiver using an FFT block to recover the data mapped to the source symbols.

[0122] FIG.7 illustrates an example configuration of an NR frame into which OFDM symbols are grouped. An NR frame may be identified by a system frame number (SFN). The SFN may repeat with a period of 1024 frames. As illustrated, one NR frame may be 10 milliseconds (ms) in duration and may include 10 subframes that are 1 ms in duration. A subframe may be divided into slots that include, for example, 14 OFDM symbols per slot.

[0123] The duration of a slot may depend on the numerology used for the OFDM symbols of the slot. In NR, a flexible numerology is supported to accommodate different cell deployments (e.g., cells with carrier frequencies below 1 GHz up to cells with carrier frequencies in the mm-wave range). A numerology may be defined in terms of subcarrier spacing and cyclic prefix duration. For a numerology in NR, subcarrier spacings may be scaled up by powers of two from a baseline subcarrier spacing of 15 kHz, and cyclic prefix durations may be scaled down by powers of two from a baseline cyclic prefix duration of 4.7 µs. ForDocket No.: 24-1237PCT example, NR defines numerologies with the following subcarrier spacing / cyclic prefix duration combinations: 15 kHz / 4.7 µs; 30 kHz / 2.3 µs; 60 kHz / 1.2 µs; 120 kHz / 0.59 µs; and 240 kHz / 0.29 µs.

[0124] A slot may have a fixed number of OFDM symbols (e.g., 14 OFDM symbols). A numerology with a higher subcarrier spacing has a shorter slot duration and, correspondingly, more slots per subframe. FIG.7 illustrates this numerology-dependent slot duration and slots-per-subframe transmission structure (the numerology with a subcarrier spacing of 240 kHz is not shown in FIG.7 for ease of illustration). A subframe in NR may be used as a numerology-independent time reference, while a slot may be used as the unit upon which uplink and downlink transmissions are scheduled. To support low latency, scheduling in NR may be decoupled from the slot duration and start at any OFDM symbol and last for as many symbols as needed for a transmission. These partial slot transmissions may be referred to as mini-slot or subslot transmissions.

[0125] FIG.8 illustrates an example configuration of a slot in the time and frequency domain for an NR carrier. The slot includes resource elements (REs) and resource blocks (RBs). An RE is the smallest physical resource in NR. An RE spans one OFDM symbol in the time domain by one subcarrier in the frequency domain as shown in FIG.8. An RB spans twelve consecutive REs in the frequency domain as shown in FIG.8. An NR carrier may be limited to a width of 275 RBs or 275×12 = 3300 subcarriers. Such a limitation, if used, may limit the NR carrier to 50, 100, 200, and 400 MHz for subcarrier spacings of 15, 30, 60, and 120 kHz, respectively, where the 400 MHz bandwidth may be set based on a 400 MHz per carrier bandwidth limit.

[0126] FIG.8 illustrates a single numerology being used across the entire bandwidth of the NR carrier. In other example configurations, multiple numerologies may be supported on the same carrier.

[0127] NR may support wide carrier bandwidths (e.g., up to 400 MHz for a subcarrier spacing of 120 kHz). Not all UEs may be able to receive the full carrier bandwidth (e.g., due to hardware limitations). Also, receiving the full carrier bandwidth may be prohibitive in terms of UE power consumption. In an example, to reduce power consumption and / or for other purposes, a UE may adapt the size of the UE’s receive bandwidth based on the amount of traffic the UE is scheduled to receive. This is referred to as bandwidth adaptation.

[0128] NR defines bandwidth parts (BWPs) to support UEs not capable of receiving the full carrier bandwidth and to support bandwidth adaptation. In an example, a BWP may be defined by a subset of contiguous RBs on a carrier. A UE may be configured (e.g., via RRC layer) with one or more downlink BWPs and one or more uplink BWPs per serving cell (e.g., up to four downlink BWPs and up to four uplink BWPs per serving cell). At a given time, one or more of the configured BWPs for a serving cell may be active. These one or more BWPs may be referred to as active BWPs of the serving cell. When a servingDocket No.: 24-1237PCT cell is configured with a secondary uplink carrier, the serving cell may have one or more first active BWPs in the uplink carrier and one or more second active BWPs in the secondary uplink carrier.

[0129] For unpaired spectra, a downlink BWP from a set of configured downlink BWPs may be linked with an uplink BWP from a set of configured uplink BWPs if a downlink BWP index of the downlink BWP and an uplink BWP index of the uplink BWP are the same. For unpaired spectra, a UE may expect that a center frequency for a downlink BWP is the same as a center frequency for an uplink BWP.

[0130] For a downlink BWP in a set of configured downlink BWPs on a primary cell (PCell), a base station may configure a UE with one or more control resource sets (CORESETs) for at least one search space. A search space is a set of locations in the time and frequency domains where the UE may find control information. The search space may be a UE-specific search space or a common search space (potentially usable by a plurality of UEs). For example, a base station may configure a UE with a common search space, on a PCell or on a primary secondary cell (PSCell), in an active downlink BWP.

[0131] For an uplink BWP in a set of configured uplink BWPs, a BS may configure a UE with one or more resource sets for one or more PUCCH transmissions. A UE may receive downlink receptions (e.g., PDCCH or PDSCH) in a downlink BWP according to a configured numerology (e.g., subcarrier spacing and cyclic prefix duration) for the downlink BWP. The UE may transmit uplink transmissions (e.g., PUCCH or PUSCH) in an uplink BWP according to a configured numerology (e.g., subcarrier spacing and cyclic prefix length for the uplink BWP).

[0132] One or more BWP indicator fields may be provided in Downlink Control Information (DCI). A value of a BWP indicator field may indicate which BWP in a set of configured BWPs is an active downlink BWP for one or more downlink receptions. The value of the one or more BWP indicator fields may indicate an active uplink BWP for one or more uplink transmissions.

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

[0134] A base station may configure a UE with a BWP inactivity timer value for a PCell. The UE may start or restart a BWP inactivity timer at any appropriate time. For example, the UE may start or restart the BWP inactivity timer (a) when the UE detects a DCI indicating an active downlink BWP other than a default downlink BWP for a paired spectra operation; or (b) when a UE detects a DCI indicating an active downlink BWP or active uplink BWP other than a default downlink BWP or uplink BWP for an unpaired spectra operation. If the UE does not detect DCI during an interval of time (e.g., 1 ms or 0.5 ms), the UE may run the BWP inactivity timer toward expiration (for example, increment from zero to the BWP inactivity timerDocket No.: 24-1237PCT value, or decrement from the BWP inactivity timer value to zero). When the BWP inactivity timer expires, the UE may switch from the active downlink BWP to the default downlink BWP.

[0135] In an example, a base station may semi-statically configure a UE with one or more BWPs. A UE may switch an active BWP from a first BWP to a second BWP in response to receiving a DCI indicating the second BWP as an active BWP and / or in response to an expiry of the BWP inactivity timer (e.g., if the second BWP is the default BWP).

[0136] Downlink and uplink BWP switching (where BWP switching refers to switching from a currently active BWP to a not currently active BWP) may be performed independently in paired spectra. In unpaired spectra, downlink and uplink BWP switching may be performed simultaneously. Switching between configured BWPs may occur based on RRC signaling, DCI, expiration of a BWP inactivity timer, and / or an initiation of random access.

[0137] FIG.9 illustrates an example of bandwidth adaptation using three configured BWPs for an NR carrier. A UE configured with the three BWPs may switch from one BWP to another BWP at a switching point. In the example illustrated in FIG.9, the BWPs include: a BWP 902 with a bandwidth of 40 MHz and a subcarrier spacing of 15 kHz; a BWP 904 with a bandwidth of 10 MHz and a subcarrier spacing of 15 kHz; and a BWP 906 with a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz. The BWP 902 may be an initial active BWP, and the BWP 904 may be a default BWP. The UE may switch between BWPs at switching points. In the example of FIG.9, the UE may switch from the BWP 902 to the BWP 904 at a switching point 908. The switching at the switching point 908 may occur for any suitable reason, for example, in response to an expiry of a BWP inactivity timer (indicating switching to the default BWP) and / or in response to receiving a DCI indicating BWP 904 as the active BWP. The UE may switch at a switching point 910 from active BWP 904 to BWP 906 in response to receiving a DCI indicating BWP 906 as the active BWP. The UE may switch at a switching point 912 from active BWP 906 to BWP 904 in response to an expiry of a BWP inactivity timer and / or in response to receiving a DCI indicating BWP 904 as the active BWP. The UE may switch at a switching point 914 from active BWP 904 to BWP 902 in response to receiving a DCI indicating BWP 902 as the active BWP.

[0138] If a UE is configured for a secondary cell with a default downlink BWP in a set of configured downlink BWPs and a timer value, UE procedures for switching BWPs on a secondary cell may be the same / similar as those on a primary cell. For example, the UE may use the timer value and the default downlink BWP for the secondary cell in the same / similar manner as the UE would use these values for a primary cell.

[0139] To provide for greater data rates, two or more carriers can be aggregated and simultaneously transmitted to / from the same UE using carrier aggregation (CA). The aggregated carriers in CA may beDocket No.: 24-1237PCT referred to as component carriers (CCs). When CA is used, there are a number of serving cells for the UE, one for a CC. The CCs may have three configurations in the frequency domain.

[0140] FIG.10A illustrates the three CA configurations with two CCs. In the intraband, contiguous configuration 1002, the two CCs are aggregated in the same frequency band (frequency band A) and are located directly adjacent to each other within the frequency band. In the intraband, non-contiguous configuration 1004, the two CCs are aggregated in the same frequency band (frequency band A) and are separated in the frequency band by a gap. In the interband configuration 1006, the two CCs are located in frequency bands (frequency band A and frequency band B).

[0141] In an example, up to 32 CCs may be aggregated. The aggregated CCs may have the same or different bandwidths, subcarrier spacing, and / or duplexing schemes (TDD or FDD). A serving cell for a UE using CA may have a downlink CC. For FDD, one or more uplink CCs may be optionally configured for a serving cell. The ability to aggregate more downlink carriers than uplink carriers may be useful, for example, when the UE has more data traffic in the downlink than in the uplink.

[0142] When CA is used, one of the aggregated cells for a UE may be referred to as a primary cell (PCell). The PCell may be the serving cell that the UE initially connects to at RRC connection establishment, reestablishment, and / or handover. The PCell may provide the UE with NAS mobility information and the security input. UEs may have different PCells. In the downlink, the carrier corresponding to the PCell may be referred to as the downlink primary CC (DL PCC). In the uplink, the carrier corresponding to the PCell may be referred to as the uplink primary CC (UL PCC). The other aggregated cells for the UE may be referred to as secondary cells (SCells). In an example, the SCells may be configured after the PCell is configured for the UE. For example, an SCell may be configured through an RRC Connection Reconfiguration procedure. In the downlink, the carrier corresponding to an SCell may be referred to as a downlink secondary CC (DL SCC). In the uplink, the carrier corresponding to the SCell may be referred to as the uplink secondary CC (UL SCC).

[0143] Configured SCells for a UE may be activated and deactivated based on, for example, traffic and channel conditions. Deactivation of an SCell may mean that PDCCH and PDSCH reception on the SCell is stopped and PUSCH, SRS, and CQI transmissions on the SCell are stopped. Configured SCells may be activated and deactivated using a MAC CE with respect to FIG.4B. For example, a MAC CE may use a bitmap (e.g., one bit per SCell) to indicate which SCells (e.g., in a subset of configured SCells) for the UE are activated or deactivated. Configured SCells may be deactivated in response to an expiration of an SCell deactivation timer (e.g., one SCell deactivation timer per SCell).

[0144] Downlink control information, such as scheduling assignments and scheduling grants, for a cell may be transmitted on the cell corresponding to the assignments and grants, which is known as self- scheduling. The DCI for the cell may be transmitted on another cell, which is known as cross-carrierDocket No.: 24-1237PCT scheduling. Uplink control information (e.g., HARQ acknowledgments and channel state feedback, such as CQI, PMI, and / or RI) for aggregated cells may be transmitted on the PUCCH of the PCell. For a larger number of aggregated downlink CCs, the PUCCH of the PCell may become overloaded. Cells may be divided into multiple PUCCH groups.

[0145] FIG.10B illustrates an example of how aggregated cells may be configured into one or more PUCCH groups. A PUCCH group 1010 and a PUCCH group 1050 may include one or more downlink CCs, respectively. In the example of FIG.10B, the PUCCH group 1010 includes three downlink CCs: a PCell 1011, an SCell 1012, and an SCell 1013. The PUCCH group 1050 includes three downlink CCs in the present example: a PCell 1051, an SCell 1052, and an SCell 1053. One or more uplink CCs may be configured as a PCell 1021, an SCell 1022, and an SCell 1023. One or more other uplink CCs may be configured as a primary SCell (PSCell) 1061, an SCell 1062, and an SCell 1063. Uplink control information (UCI) related to the downlink CCs of the PUCCH group 1010, shown as UCI 1031, UCI 1032, and UCI 1033, may be transmitted in the uplink of the PCell 1021. Uplink control information (UCI) related to the downlink CCs of the PUCCH group 1050, shown as UCI 1071, UCI 1072, and UCI 1073, may be transmitted in the uplink of the PSCell 1061. In an example, if the aggregated cells depicted in FIG.10B were not divided into the PUCCH group 1010 and the PUCCH group 1050, a single uplink PCell to transmit UCI relating to the downlink CCs, and the PCell may become overloaded. By dividing transmissions of UCI between the PCell 1021 and the PSCell 1061, overloading may be prevented.

[0146] A cell, comprising a downlink carrier and optionally an uplink carrier, may be assigned with a physical cell ID and a cell index. The physical cell ID or the cell index may identify a downlink carrier and / or an uplink carrier of the cell, for example, depending on the context in which the physical cell ID is used. A physical cell ID may be determined using a synchronization signal transmitted on a downlink component carrier. A cell index may be determined using RRC messages. In the disclosure, a physical cell ID may be referred to as a carrier ID, and a cell index may be referred to as a carrier index. For example, when the disclosure refers to a first physical cell ID for a first downlink carrier, the disclosure may mean the first physical cell ID is for a cell comprising the first downlink carrier. The same / similar concept may apply to, for example, a carrier activation. When the disclosure indicates that a first carrier is activated, the specification may mean that a cell comprising the first carrier is activated.

[0147] In CA, a multi-carrier nature of a PHY may be exposed to a MAC. In an example, a HARQ entity may operate on a serving cell. A transport block may be generated per assignment / grant per serving cell. A transport block and potential HARQ retransmissions of the transport block may be mapped to a serving cell.

[0148] In the downlink, a base station may transmit (e.g., unicast, multicast, and / or broadcast) one or more Reference Signals (RSs) to a UE (e.g., PSS, SSS, CSI-RS, DMRS, and / or PT-RS, as shown in FIG.Docket No.: 24-1237PCT 5A). In the uplink, the UE may transmit one or more RSs to the base station (e.g., DMRS, PT-RS, and / or SRS, as shown in FIG.5B). The PSS and the SSS may be transmitted by the base station and used by the UE to synchronize the UE to the base station. The PSS and the SSS may be provided in a synchronization signal (SS) / physical broadcast channel (PBCH) block that includes the PSS, the SSS, and the PBCH. The base station may periodically transmit a burst of SS / PBCH blocks.

[0149] FIG.11A illustrates an example of an SS / PBCH block's structure and location. A burst of SS / PBCH blocks may include one or more SS / PBCH blocks (e.g., 4 SS / PBCH blocks, as shown in FIG.11A). Bursts may be transmitted periodically (e.g., every 2 frames or 20 ms). A burst may be restricted to a half-frame (e.g., a first half-frame having a duration of 5 ms). It will be understood that FIG.11A is an example, and that these parameters (number of SS / PBCH blocks per burst, periodicity of bursts, position of burst within the frame) may be configured based on, for example: a carrier frequency of a cell in which the SS / PBCH block is transmitted; a numerology or subcarrier spacing of the cell; a configuration by the network (e.g., using RRC signaling); or any other suitable factor. In an example, the UE may assume a subcarrier spacing for the SS / PBCH block based on the carrier frequency being monitored, unless the radio network configured the UE to assume a different subcarrier spacing.

[0150] The SS / PBCH block may span one or more OFDM symbols in the time domain (e.g., 4 OFDM symbols, as shown in the example of FIG.11A) and may span one or more subcarriers in the frequency domain (e.g., 240 contiguous subcarriers). The PSS, the SSS, and the PBCH may have a common center frequency. The PSS may be transmitted first and may span, for example, 1 OFDM symbol and 127 subcarriers. The SSS may be transmitted after the PSS (e.g., two symbols later) and may span 1 OFDM symbol and 127 subcarriers. The PBCH may be transmitted after the PSS (e.g., across the next 3 OFDM symbols) and may span 240 subcarriers.

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

[0152] The SS / PBCH block may be used by the UE to determine one or more parameters of the cell. For example, the UE may determine a physical cell identifier (PCI) of the cell based on the sequences of theDocket No.: 24-1237PCT PSS and the SSS, respectively. The UE may determine a location of a frame boundary of the cell based on the location of the SS / PBCH block. For example, the SS / PBCH block may indicate that it has been transmitted in accordance with a transmission pattern, wherein a SS / PBCH block in the transmission pattern is a known distance from the frame boundary.

[0153] The PBCH may use a QPSK modulation and may use forward error correction (FEC). The FEC may use polar coding. One or more symbols spanned by the PBCH may carry one or more DMRSs for demodulation of the PBCH. The PBCH may include an indication of a current system frame number (SFN) of the cell and / or a SS / PBCH block timing index. These parameters may facilitate time synchronization of the UE to the base station. The PBCH may include a master information block (MIB) used to provide the UE with one or more parameters. The MIB may be used by the UE to locate remaining minimum system information (RMSI) associated with the cell. The RMSI may include a System Information Block Type 1 (SIB1). The SIB1 may contain information needed by the UE to access the cell. The UE may use one or more parameters of the MIB to monitor PDCCH, which may be used to schedule PDSCH. The PDSCH may include the SIB1. The SIB1 may be decoded using parameters provided in the MIB. The PBCH may indicate an absence of SIB1. Based on the PBCH indicating the absence of SIB1, the UE may be pointed to a frequency. The UE may search for an SS / PBCH block at the frequency to which the UE is pointed.

[0154] The UE may assume that one or more SS / PBCH blocks transmitted with a same SS / PBCH block index are quasi co-located (QCLed) (e.g., having the same / similar Doppler spread, Doppler shift, average gain, average delay, and / or spatial Rx parameters). The UE may not assume QCL for SS / PBCH block transmissions having different SS / PBCH block indices.

[0155] SS / PBCH blocks (e.g., those within a half-frame) may be transmitted in spatial directions (e.g., using different beams that span a coverage area of the cell). In an example, a first SS / PBCH block may be transmitted in a first spatial direction using a first beam, and a second SS / PBCH block may be transmitted in a second spatial direction using a second beam.

[0156] In an example, within a frequency span of a carrier, a base station may transmit a plurality of SS / PBCH blocks. In an example, a first PCI of a first SS / PBCH block of the plurality of SS / PBCH blocks may be different from a second PCI of a second SS / PBCH block of the plurality of SS / PBCH blocks. The PCIs of SS / PBCH blocks transmitted in different frequency locations may be different or the same.

[0157] The CSI-RS may be transmitted by the base station and used by the UE to acquire channel state information (CSI). The base station may configure the UE with one or more CSI-RSs for channel estimation or any other suitable purpose. The base station may configure a UE with one or more of the same / similar CSI-RSs. The UE may measure the one or more CSI-RSs. The UE may estimate a downlink channel state and / or generate a CSI report based on the measuring of the one or more downlink CSI-RSs. The UE mayDocket No.: 24-1237PCT provide the CSI report to the base station. The base station may use feedback provided by the UE (e.g., the estimated downlink channel state) to perform link adaptation.

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

[0159] The base station may configure the UE to report CSI measurements. The base station may configure the UE to provide CSI reports periodically, aperiodically, or semi-persistently. For periodic CSI reporting, the UE may be configured with a timing and / or periodicity of a plurality of CSI reports. For aperiodic CSI reporting, the base station may request a CSI report. For example, the base station may command the UE to measure a configured CSI-RS resource and provide a CSI report relating to the measurements. For semi-persistent CSI reporting, the base station may configure the UE to transmit periodically, and selectively activate or deactivate the periodic reporting. The base station may configure the UE with a CSI-RS resource set and CSI reports using RRC signaling.

[0160] The CSI-RS configuration may comprise one or more parameters indicating, for example, up to 32 antenna ports. The UE may be configured to employ the same OFDM symbols for a downlink CSI-RS and a control resource set (CORESET) when the downlink CSI-RS and CORESET are spatially QCLed and resource elements associated with the downlink CSI-RS are outside of the physical resource blocks (PRBs) configured for the CORESET. The UE may be configured to employ the same OFDM symbols for downlink CSI-RS and SS / PBCH blocks when the downlink CSI-RS and SS / PBCH blocks are spatially QCLed and resource elements associated with the downlink CSI-RS are outside of PRBs configured for the SS / PBCH blocks.

[0161] Downlink DMRSs may be transmitted by a base station and used by a UE for channel estimation. For example, the downlink DMRS may be used for coherent demodulation of one or more downlink physical channels (e.g., PDSCH). An NR network may support one or more variable and / or configurable DMRS patterns for data demodulation. At least one downlink DMRS configuration may support a front- loaded DMRS pattern. A front-loaded DMRS may be mapped over one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). A base station may semi-statically configure the UE with a number (e.g., a maximum number) of front-loaded DMRS symbols for PDSCH. A DMRS configuration may support one or more DMRS ports. For example, for single user-MIMO, a DMRS configuration may support up to eight orthogonal downlink DMRS ports per UE. For multiuser-MIMO, a DMRS configuration may support up to 4 orthogonal downlink DMRS ports per UE. A radio network may support (e.g., at least for CP-OFDM) a common DMRS structure for downlink and uplink, wherein a DMRS location, a DMRS pattern, and / or a scrambling sequence may be the same or different. The base station may transmit a downlink DMRS and aDocket No.: 24-1237PCT corresponding PDSCH using the same precoding matrix. The UE may use the one or more downlink DMRSs for coherent demodulation / channel estimation of the PDSCH.

[0162] In an example, a transmitter (e.g., a base station) may use a precoder matrices for a part of a transmission bandwidth. For example, 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 based on the first bandwidth being different from the second bandwidth. The UE may assume that a same precoding matrix is used across a set of PRBs. The set of PRBs may be denoted as a precoding resource block group (PRG).

[0163] A PDSCH may comprise one or more layers. The UE may assume that at least one symbol with DMRS is present on a layer of the one or more layers of the PDSCH. A higher layer may configure up to 3 DMRSs for the PDSCH.

[0164] Downlink PT-RS may be transmitted by a base station and used by a UE for phase-noise compensation. Whether a downlink PT-RS is present or not may depend on an RRC configuration. The presence and / or pattern of the downlink PT-RS may be configured on a UE-specific basis using a combination of RRC signaling and / or an association with one or more parameters employed for other purposes (e.g., modulation and coding scheme (MCS)), which may be indicated by DCI. When configured, a dynamic presence of a downlink PT-RS may be associated with one or more DCI parameters comprising at least MCS. An NR network may support a plurality of PT-RS densities defined in the time and / or frequency domains. When present, a frequency domain density may be associated with at least one configuration of a scheduled bandwidth. The UE may assume a same precoding for a DMRS port and a PT-RS port. A number of PT-RS ports may be fewer than a number of DMRS ports in a scheduled resource. Downlink PT-RS may be confined in the scheduled time / frequency duration for the UE. Downlink PT-RS may be transmitted on symbols to facilitate phase tracking at the receiver.

[0165] The UE may transmit an uplink DMRS to a base station for channel estimation. For example, the base station may use the uplink DMRS for coherent demodulation of one or more uplink physical channels. For example, the UE may transmit an uplink DMRS with a PUSCH and / or a PUCCH. The uplink DM-RS may span a range of frequencies that is similar to a range of frequencies associated with the corresponding physical channel. The base station may configure the UE with one or more uplink DMRS configurations. At least one DMRS configuration may support a front-loaded DMRS pattern. The front-loaded DMRS may be mapped over one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DMRSs may be configured to transmit at one or more symbols of a PUSCH and / or a PUCCH. The base station may semi-statically configure the UE with a number (e.g., maximum number) of front-loaded DMRS symbols for the PUSCH and / or the PUCCH, which the UE may use to schedule a single-symbol DMRS and / or a double-symbol DMRS. An NR network may support (e.g., for cyclic prefix orthogonal frequencyDocket No.: 24-1237PCT division multiplexing (CP-OFDM)) a common DMRS structure for downlink and uplink, wherein a DMRS location, a DMRS pattern, and / or a scrambling sequence for the DMRS may be the same or different.

[0166] A PUSCH may comprise one or more layers, and the UE may transmit at least one symbol with DMRS present on a layer of the one or more layers of the PUSCH. In an example, a higher layer may configure up to three DMRSs for the PUSCH.

[0167] Uplink PT-RS (which may be used by a base station for phase tracking and / or phase-noise compensation) may or may not be present depending on an RRC configuration of the UE. The presence and / or pattern of uplink PT-RS may be configured on a UE-specific basis by a combination of RRC signaling and / or one or more parameters employed for other purposes (e.g., Modulation and Coding Scheme (MCS)), which may be indicated by DCI. When configured, a dynamic presence of uplink PT-RS may be associated with one or more DCI parameters comprising at least MCS. A radio network may support a plurality of uplink PT-RS densities defined in time / frequency domain. When present, a frequency domain density may be associated with at least one configuration of a scheduled bandwidth. The UE may assume a same precoding for a DMRS port and a PT-RS port. A number of PT-RS ports may be fewer than a number of DMRS ports in a scheduled resource. For example, uplink PT-RS may be confined in the scheduled time / frequency duration for the UE.

[0168] SRS may be transmitted by a UE to a base station for channel state estimation to support uplink channel dependent scheduling and / or link adaptation. SRS transmitted by the UE may allow a base station to estimate an uplink channel state at one or more frequencies. A scheduler at the base station may employ the estimated uplink channel state to assign one or more resource blocks for an uplink PUSCH transmission from the UE. The base station may semi-statically configure the UE with one or more SRS resource sets. For an SRS resource set, the base station may configure the UE with one or more SRS resources. An SRS resource set applicability may be configured by a higher layer (e.g., RRC) parameter. For example, when a higher layer parameter indicates beam management, an SRS resource in an SRS resource set of the one or more SRS resource sets (e.g., with the same / similar time domain behavior, periodic, aperiodic, and / or the like) may be transmitted at a time instant (e.g., simultaneously). The UE may transmit one or more SRS resources in SRS resource sets. An NR network may support aperiodic, periodic and / or semi-persistent SRS transmissions. The UE may transmit SRS resources based on one or more trigger types, wherein the one or more trigger types may comprise higher layer signaling (e.g., RRC) and / or one or more DCI formats. In an example, at least one DCI format may be employed for the UE to select at least one of one or more configured SRS resource sets. An SRS trigger type 0 may refer to an SRS triggered based on a higher layer signaling. An SRS trigger type 1 may refer to an SRS triggered based on one or more DCI formats. In an example, when PUSCH and SRS are transmitted in a same slot, the UE may be configured to transmit SRS after a transmission of a PUSCH and a corresponding uplink DMRS.Docket No.: 24-1237PCT

[0169] The base station may semi-statically configure the UE with one or more SRS configuration parameters indicating at least one of following: a SRS resource configuration identifier; a number of SRS ports; time domain behavior of an SRS resource configuration (e.g., an indication of periodic, semi- persistent, or aperiodic SRS); slot, mini-slot, and / or subframe level periodicity; offset for a periodic and / or an aperiodic SRS resource; a number of OFDM symbols in an SRS resource; a starting OFDM symbol of an SRS resource; an SRS bandwidth; a frequency hopping bandwidth; a cyclic shift; and / or an SRS sequence ID.

[0170] An antenna port is defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed. If a first symbol and a second symbol are transmitted on the same antenna port, the receiver may infer the channel (e.g., fading gain, multipath delay, and / or the like) for conveying the second symbol on the antenna port, from the channel for conveying the first symbol on the antenna port. A first antenna port and a second antenna port may be referred to as quasi co-located (QCLed) if one or more large-scale properties of the channel over which a first symbol on the first antenna port is conveyed may be inferred from the channel over which a second symbol on a second antenna port is conveyed. The one or more large-scale properties may comprise at least one of: a delay spread; a Doppler spread; a Doppler shift; an average gain; an average delay; and / or spatial Receiving (Rx) parameters.

[0171] Channels that use beamforming require beam management. Beam management may comprise beam measurement, beam selection, and beam indication. A beam may be associated with one or more reference signals. For example, a beam may be identified by one or more beamformed reference signals. The UE may perform downlink beam measurement based on downlink reference signals (e.g., a channel state information reference signal (CSI-RS)) and generate a beam measurement report. The UE may perform the downlink beam measurement procedure after an RRC connection is set up with a base station.

[0172] FIG.11B illustrates an example of channel state information reference signals (CSI-RSs) that are mapped in the time and frequency domains. A square shown in FIG.11B may span a resource block (RB) within a bandwidth of a cell. A base station may transmit one or more RRC messages comprising CSI-RS resource configuration parameters indicating one or more CSI-RSs. One or more of the following parameters may be configured by higher layer signaling (e.g., RRC and / or MAC signaling) for a CSI-RS resource configuration: a CSI-RS resource configuration identity, a number of CSI-RS ports, a CSI-RS configuration (e.g., symbol and resource element (RE) locations in a subframe), a CSI-RS subframe configuration (e.g., subframe location, offset, and periodicity in a radio frame), a CSI-RS power parameter, a CSI-RS sequence parameter, a code division multiplexing (CDM) type parameter, a frequency density, a transmission comb, quasi co-location (QCL) parameters (e.g., QCL-scramblingidentity, crs-portscount,Docket No.: 24-1237PCT mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and / or other radio resource parameters.

[0173] The three beams illustrated in FIG.11B may be configured for a UE in a UE-specific configuration. Three beams are illustrated in FIG.11B (beam #1, beam #2, and beam #3), more or fewer beams may be configured. Beam #1 may be allocated with CSI-RS 1101 that may be transmitted in one or more subcarriers in an RB of a first symbol. Beam #2 may be allocated with CSI-RS 1102 that may be transmitted in one or more subcarriers in an RB of a second symbol. Beam #3 may be allocated with CSI- RS 1103 that may be transmitted in one or more subcarriers in an RB of a third symbol. By using frequency division multiplexing (FDM), a base station may use other subcarriers in a same RB (for example, those that are not used to transmit CSI-RS 1101) to transmit another CSI-RS associated with a beam for another UE. By using time domain multiplexing (TDM), beams used for the UE may be configured such that beams for the UE use symbols from beams of other UEs.

[0174] CSI-RSs such as those illustrated in FIG.11B (e.g., CSI-RS 1101, 1102, 1103) may be transmitted by the base station and used by the UE for one or more measurements. For example, the UE may measure a reference signal received power (RSRP) of configured CSI-RS resources. The base station may configure the UE with a reporting configuration and the UE may report the RSRP measurements to a network (for example, via one or more base stations) based on the reporting configuration. In an example, the base station may determine, based on the reported measurement results, one or more transmission configuration indication (TCI) states comprising a number of reference signals. In an example, the base station may indicate one or more TCI states to the UE (e.g., via RRC signaling, a MAC CE, and / or a DCI). The UE may receive a downlink transmission with a receive (Rx) beam determined based on the one or more TCI states. In an example, the UE may or may not have a capability of beam correspondence. If the UE has the capability of beam correspondence, the UE may determine a spatial domain filter of a transmit (Tx) beam based on a spatial domain filter of the corresponding Rx beam. If the UE does not have the capability of beam correspondence, the UE may perform an uplink beam selection procedure to determine the spatial domain filter of the Tx beam. The UE may perform the uplink beam selection procedure based on one or more sounding reference signal (SRS) resources configured to the UE by the base station. The base station may select and indicate uplink beams for the UE based on measurements of the one or more SRS resources transmitted by the UE.

[0175] In a beam management procedure, a UE may assess (e.g., measure) a channel quality of one or more beam pair links, a beam pair link comprising a transmitting beam transmitted by a base station and a receiving beam received by the UE. Based on the assessment, the UE may transmit a beam measurement report indicating one or more beam pair quality parameters comprising, e.g., one or more beamDocket No.: 24-1237PCT identifications (e.g., a beam index, a reference signal index, or the like), RSRP, a precoding matrix indicator (PMI), a channel quality indicator (CQI), and / or a rank indicator (RI).

[0176] FIG.12A illustrates examples of three downlink beam management procedures: P1, P2, and P3. Procedure P1 may enable a UE measurement on transmit (Tx) beams of a transmission reception point (TRP) (or multiple TRPs), e.g., to support a selection of one or more base station Tx beams and / or UE Rx beams (shown as ovals in the top row and bottom row, respectively, of P1). Beamforming at a TRP may comprise a Tx beam sweep for a set of beams (shown, in the top rows of P1 and P2, as ovals rotated in a counterclockwise direction indicated by the dashed arrow). Beamforming at a UE may comprise an Rx beam sweep for a set of beams (shown, in the bottom rows of P1 and P3, as ovals rotated in a clockwise direction indicated by the dashed arrow). Procedure P2 may be used to enable a UE measurement on Tx beams of a TRP (shown, in the top row of P2, as ovals rotated in a counterclockwise direction indicated by the dashed arrow). The UE and / or the base station may perform procedure P2 using a smaller set of beams than is used in procedure P1, or using narrower beams than the beams used in procedure P1. This may be referred to as beam refinement. The UE may perform procedure P3 for Rx beam determination by using the same Tx beam at the base station and sweeping an Rx beam at the UE.

[0177] FIG.12B illustrates examples of three uplink beam management procedures: U1, U2, and U3. Procedure U1 may be used to enable a base station to perform a measurement on Tx beams of a UE, e.g., to support a selection of one or more UE Tx beams and / or base station Rx beams (shown as ovals in the top row and bottom row, respectively, of U1). Beamforming at the UE may include, e.g., a Tx beam sweep from a set of beams (shown in the bottom rows of U1 and U3 as ovals rotated in a clockwise direction indicated by the dashed arrow). Beamforming at the base station may include, e.g., an Rx beam sweep from a set of beams (shown, in the top rows of U1 and U2, as ovals rotated in a counterclockwise direction indicated by the dashed arrow). Procedure U2 may be used to enable the base station to adjust its Rx beam when the UE uses a fixed Tx beam. The UE and / or the base station may perform procedure U2 using a smaller set of beams than is used in procedure P1, or using narrower beams than the beams used in procedure P1. This may be referred to as beam refinement The UE may perform procedure U3 to adjust its Tx beam when the base station uses a fixed Rx beam.

[0178] A UE may initiate a beam failure recovery (BFR) procedure based on detecting a beam failure. The UE may transmit a BFR request (e.g., a preamble, a UCI, an SR, a MAC CE, and / or the like) based on the initiating of the BFR procedure. The UE may detect the beam failure based on a determination that a quality of beam pair link(s) of an associated control channel is unsatisfactory (e.g., having an error rate higher than an error rate threshold, a received signal power lower than a received signal power threshold, an expiration of a timer, and / or the like).Docket No.: 24-1237PCT

[0179] The UE may measure a quality of a beam pair link using one or more reference signals (RSs) comprising one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more demodulation reference signals (DMRSs). A 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, a reference signal received quality (RSRQ) value, and / or a CSI value measured on RS resources. The base station may indicate that an RS resource is quasi co-located (QCLed) with one or more DM-RSs of a channel (e.g., a control channel, a shared data channel, and / or the like). The RS resource and the one or more DMRSs of the channel may be QCLed when the channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameter, fading, and / or the like) from a transmission via the RS resource to the UE are similar or the same as the channel characteristics from a transmission via the channel to the UE.

[0180] A network (e.g., a gNB and / or an ng-eNB of a network) and / or the UE may initiate a random access procedure. A UE in an RRC_IDLE state and / or an RRC_INACTIVE state may initiate the random access procedure to request a connection setup to a network. The UE may initiate the random access procedure from an RRC_CONNECTED state. The UE may initiate the random access procedure to request uplink resources (e.g., for uplink transmission of an SR when there is no PUCCH resource available) and / or acquire uplink timing (e.g., when uplink synchronization status is non-synchronized). The UE may initiate the random access procedure to request one or more system information blocks (SIBs) (e.g., other system information such as SIB2, SIB3, and / or the like). The UE may initiate the random access procedure for a beam failure recovery request. A network may initiate a random access procedure for a handover and / or for establishing time alignment for an SCell addition.

[0181] FIG.13A illustrates a four-step contention-based random access procedure. Prior to initiation of the procedure, a base station may transmit a configuration message 1310 to the UE. The procedure illustrated in FIG.13A comprises transmission of four messages: a Msg 11311, a Msg 21312, a Msg 31313, and a Msg 41314. The Msg 11311 may include and / or be referred to as a preamble (or a random access preamble). The Msg 21312 may include and / or be referred to as a random access response (RAR).

[0182] The configuration message 1310 may be transmitted, for example, using one or more RRC messages. The one or more RRC messages may indicate one or more random access channel (RACH) parameters to the UE. The one or more RACH parameters may comprise at least one of following: general parameters for one or more random access procedures (e.g., RACH-configGeneral); cell-specific parameters (e.g., RACH-ConfigCommon); and / or dedicated parameters (e.g., RACH-configDedicated). The base station may broadcast or multicast the one or more RRC messages to one or more UEs. The one or more RRC messages may be UE-specific (e.g., dedicated RRC messages transmitted to a UE in an RRC_CONNECTED state and / or in an RRC_INACTIVE state). The UE may determine, based on the oneDocket No.: 24-1237PCT or more RACH parameters, a time-frequency resource and / or an uplink transmit power for transmission of the Msg 11311 and / or the Msg 31313. Based on the one or more RACH parameters, the UE may determine a reception timing and a downlink channel for receiving the Msg 21312 and the Msg 41314.

[0183] The one or more RACH parameters provided in the configuration message 1310 may indicate one or more Physical RACH (PRACH) occasions available for transmission of the Msg 11311. The one or more PRACH occasions may be predefined. The one or more RACH parameters may indicate one or more available sets of one or more PRACH occasions (e.g., prach-ConfigIndex). The one or more RACH parameters may indicate an association between (a) one or more PRACH occasions 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-RSs. For example, the one or more RACH parameters may indicate a number of SS / PBCH blocks mapped to a PRACH occasion and / or a number of preambles mapped to a SS / PBCH blocks.

[0184] The one or more RACH parameters provided in the configuration message 1310 may be used to determine an uplink transmit power of Msg 11311 and / or Msg 31313. For example, the one or more RACH parameters may indicate a reference power for a 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. For example, the one or more RACH parameters may indicate: a power ramping step; a power offset between SSB and CSI-RS; a power offset between transmissions of the Msg 11311 and the Msg 31313; 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 UE may determine at least one reference signal (e.g., an SSB and / or CSI-RS) and / or an uplink carrier (e.g., a normal uplink (NUL) carrier and / or a supplemental uplink (SUL) carrier).

[0185] The Msg 11311 may include one or more preamble transmissions (e.g., a preamble transmission and one or more preamble retransmissions). An RRC message may be used to configure one or more preamble groups (e.g., group A and / or group B). A preamble group may comprise one or more preambles. The UE may determine the preamble group based on a pathloss measurement and / or a size of the Msg 3 1313. The UE may measure an RSRP of one or more reference signals (e.g., SSBs and / or CSI-RSs) and determine at least one reference signal having an RSRP above an RSRP threshold (e.g., rsrp- ThresholdSSB and / or rsrp-ThresholdCSI-RS). The UE may select at least one preamble associated with the one or more reference signals and / or a selected preamble group, for example, if the association between the one or more preambles and the at least one reference signal is configured by an RRC message.Docket No.: 24-1237PCT

[0186] The UE may determine the preamble based on the one or more RACH parameters provided in the configuration message 1310. For example, the UE may determine the preamble based on a pathloss measurement, an RSRP measurement, and / or a size of the Msg 31313. As another example, the one or more RACH parameters may indicate: a preamble format; a maximum number of preamble transmissions; and / or one or more thresholds for determining one or more preamble groups (e.g., group A and group B). A base station may use the one or more RACH parameters to configure the UE with an association between one or more preambles and one or more reference signals (e.g., SSBs and / or CSI-RSs). If the association is configured, the UE may determine the preamble to include in Msg 11311 based on the association. The Msg 11311 may be transmitted to the base station via one or more PRACH occasions. The UE may use one or more reference signals (e.g., SSBs and / or CSI-RSs) for selection of the preamble and for determining of the PRACH occasion. One or more RACH parameters (e.g., ra-ssb-OccasionMskIndex and / or ra-OccasionList) may indicate an association between the PRACH occasions and the one or more reference signals.

[0187] The UE may perform a preamble retransmission if no response is received following a preamble transmission. The UE may increase an uplink transmit power for the preamble retransmission. The UE may select an initial preamble transmit power based on a pathloss measurement and / or a target received preamble power configured by the network. The UE may determine to retransmit a preamble and may ramp up the uplink transmit power. The UE may receive one or more RACH parameters (e.g., PREAMBLE_POWER_RAMPING_STEP) indicating a ramping step for the preamble retransmission. The ramping step may be an amount of incremental increase in uplink transmit power for a retransmission. The UE may ramp up the uplink transmit power if the UE determines a reference signal (e.g., SSB and / or CSI- RS) that is the same as a previous preamble transmission. The UE may count a number of preamble transmissions and / or retransmissions (e.g., PREAMBLE_TRANSMISSION_COUNTER). The UE may determine that a random access procedure completed unsuccessfully, for example, if the number of preamble transmissions exceeds a threshold configured by the one or more RACH parameters (e.g., preambleTransMax).

[0188] The Msg 21312 received by the UE may include an RAR. In some scenarios, the Msg 21312 may include multiple RARs corresponding to multiple UEs. The Msg 21312 may be received after or in response to the transmitting of the Msg 11311. The Msg 21312 may be scheduled on the DL-SCH and indicated on a PDCCH using a random access RNTI (RA-RNTI). The Msg 21312 may indicate that the Msg 11311 was received by the base station. The Msg 21312 may include a time-alignment command that may be used by the UE to adjust the UE’s transmission timing, a scheduling grant for transmission of the Msg 31313, and / or a Temporary Cell RNTI (TC-RNTI). After transmitting a preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor a PDCCH for the Msg 21312. The UE mayDocket No.: 24-1237PCT determine when to start the time window based on a PRACH occasion that the UE uses to transmit the preamble. For example, the UE may start the time window one or more symbols after a last symbol of the preamble (e.g., at a first PDCCH occasion from an end of a preamble transmission). The one or more symbols may be determined based on a numerology. The PDCCH may be in a common search space (e.g., a Type1-PDCCH common search space) configured by an RRC message. The UE may identify the RAR based on a Radio Network Temporary Identifier (RNTI). RNTIs may be used depending on one or more events initiating the random access procedure. The UE may use random access RNTI (RA-RNTI). The RA-RNTI may be associated with PRACH occasions in which the UE transmits a preamble. For example, the UE may determine the RA-RNTI based on: an OFDM symbol index; a slot index; a frequency domain index; and / or a UL carrier indicator of the PRACH occasions. An example of RA-RNTI may be as follows:

[0189] RA-RNTI= 1 + s_id + 14 × t_id + 14 × 80 × f_id + 14 × 80 × 8 × ul_carrier_id, where s_id may be an index of a first OFDM symbol of the PRACH occasion (e.g., 0 ≤ s_id < 14), t_id may be an index of a first slot of the PRACH occasion in a system frame (e.g., 0 ≤ t_id < 80), f_id may be an index of the PRACH occasion in the frequency domain (e.g., 0 ≤ f_id < 8), and ul_carrier_id may be a UL carrier used for a preamble transmission (e.g., 0 for an NUL carrier, and 1 for an SUL carrier).

[0190] The UE may transmit the Msg 31313 in response to a successful reception of the Msg 21312 (e.g., using resources identified in the Msg 21312). The Msg 31313 may be used for contention resolution in, for example, the contention-based random access procedure illustrated in FIG.13A. In some scenarios, a plurality of UEs may transmit a same preamble to a base station and the base station may provide an RAR that corresponds to a UE. Collisions may occur if the plurality of UEs interpret the RAR as corresponding to themselves. Contention resolution (e.g., using the Msg 31313 and the Msg 41314) may be used to increase the likelihood that the UE does not incorrectly use an identity of another the UE. To perform contention resolution, the UE may include a device identifier in the Msg 31313 (e.g., a C-RNTI if assigned, a TC-RNTI included in the Msg 21312, and / or any other suitable identifier).

[0191] The Msg 41314 may be received after or in response to the transmitting of the Msg 31313. If a C-RNTI was included in the Msg 31313, the base station will address the UE on the PDCCH using the C-RNTI. If the UE's unique C-RNTI is detected on the PDCCH, the random access procedure is determined to be successfully completed. If a TC-RNTI is included in the Msg 31313 (e.g., if the UE is in an RRC_IDLE state or not otherwise connected to the base station), Msg 41314 will be received using a DL-SCH associated with the TC-RNTI. If a MAC PDU is successfully decoded and a MAC PDU comprises the UE contention resolution identity MAC CE that matches or otherwise corresponds with the CCCH SDU sent (e.g., transmitted) in Msg 31313, the UE may determine that the contention resolution is successful and / or the UE may determine that the random access procedure is successfully completed.Docket No.: 24-1237PCT

[0192] The UE may be configured with a supplementary uplink (SUL) carrier and a normal uplink (NUL) carrier. An initial access (e.g., random access procedure) may be supported in an uplink carrier. For example, a base station may configure the UE with two separate RACH configurations: one for an SUL carrier and the other for an NUL carrier. For random access in a cell configured with an SUL carrier, the network may indicate which carrier to use (NUL or SUL). The UE may determine the SUL carrier, for example, if a measured quality of one or more reference signals is lower than a broadcast threshold. Uplink transmissions of the random access procedure (e.g., the Msg 11311 and / or the Msg 31313) may remain on the selected carrier. The UE may switch an uplink carrier during the random access procedure (e.g., between the Msg 11311 and the Msg 31313) in one or more cases. For example, the UE may determine and / or switch an uplink carrier for the Msg 11311 and / or the Msg 31313 based on a channel clear assessment (e.g., a listen-before-talk).

[0193] FIG.13B illustrates a two-step contention-free random access procedure. Similar to the four-step contention-based random access procedure illustrated in FIG.13A, a base station may, prior to initiation of the procedure, transmit a configuration message 1320 to the UE. The configuration message 1320 may be analogous in some respects to the configuration message 1310. The procedure illustrated in FIG.13B comprises transmission of two messages: a Msg 11321 and a Msg 21322. The Msg 11321 and the Msg 2 1322 may be analogous in some respects to the Msg 11311 and a Msg 21312 illustrated in FIG.13A, respectively. As will be understood from FIGS.13A and 13B, the contention-free random access procedure may not include messages analogous to the Msg 31313 and / or the Msg 41314.

[0194] The contention-free random access procedure illustrated in FIG.13B may be initiated for a beam failure recovery, other SI request, SCell addition, and / or handover. For example, a base station may indicate or assign to the UE the preamble to be used for the Msg 11321. The UE may receive, from the base station via PDCCH and / or RRC, an indication of a preamble (e.g., ra-PreambleIndex).

[0195] After transmitting a preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor a PDCCH for the RAR. In the event of a beam failure recovery request, the base station may configure the UE with a separate time window and / or a separate PDCCH in a search space indicated by an RRC message (e.g., recoverySearchSpaceId). The UE may monitor for a PDCCH transmission addressed to a Cell RNTI (C-RNTI) on the search space. In the contention-free random access procedure illustrated in FIG.13B, the UE may determine that a random access procedure successfully completes after or in response to transmission of Msg 11321 and reception of a corresponding Msg 21322. The UE may determine that a random access procedure successfully completes, for example, if a PDCCH transmission is addressed to a C-RNTI. The UE may determine that a random access procedure successfully completes, for example, if the UE receives an RAR comprising a preamble identifier corresponding to a preambleDocket No.: 24-1237PCT transmitted by the UE and / or the RAR comprises a MAC sub-PDU with the preamble identifier. The UE may determine the response as an indication of an acknowledgement for an SI request.

[0196] FIG.13C illustrates another two-step random access procedure. Similar to the random access procedures illustrated in FIGS.13A and 13B, a base station may, prior to initiation of the procedure, transmit a configuration message 1330 to the UE. The configuration message 1330 may be analogous in some respects to the configuration message 1310 and / or the configuration message 1320. The procedure illustrated in FIG.13C comprises transmission of two messages: a Msg A 1331 and a Msg B 1332.

[0197] Msg A 1331 may be transmitted in an uplink transmission by the UE. Msg A 1331 may comprise one or more transmissions of a preamble 1341 and / or one or more transmissions of a transport block 1342. The transport block 1342 may comprise contents that are similar and / or equivalent to the contents of the Msg 31313 illustrated in FIG.13A. The transport block 1342 may comprise UCI (e.g., an SR, a HARQ ACK / NACK, and / or the like). The UE may receive the Msg B 1332 after or in response to transmitting the Msg A 1331. The Msg B 1332 may comprise contents that are similar and / or equivalent to the contents of the Msg 21312 (e.g., an RAR) illustrated in FIGS.13A and 13B and / or the Msg 41314 illustrated in FIG. 13A.

[0198] The UE may initiate the two-step random access procedure in FIG.13C for licensed spectrum and / or unlicensed spectrum. The UE may determine, based on one or more factors, whether to initiate the two-step random access procedure. The one or more factors may be: a radio access technology in use (e.g., LTE, NR, and / or the like); whether the UE has valid TA or not; a cell size; the UE’s RRC state; a type of spectrum (e.g., licensed vs. unlicensed); and / or any other suitable factors.

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

[0200] The transport block 1342 may comprise data (e.g., delay-sensitive data), an identifier of the UE, security information, and / or device information (e.g., an International Mobile Subscriber Identity (IMSI)). The base station may transmit the Msg B 1332 as a response to the Msg A 1331. The Msg B 1332 may comprise at least one of following: a preamble identifier; a timing advance command; a power control command; an uplink grant (e.g., a radio resource assignment and / or an MCS); a UE identifier for contention resolution; and / or an RNTI (e.g., a C-RNTI or a TC-RNTI). The UE may determine that the two-stepDocket No.: 24-1237PCT random access procedure is successfully completed if: a preamble identifier in the Msg B 1332 is matched to a preamble transmitted by the UE; and / or the identifier of the UE in Msg B 1332 is matched to the identifier of the UE in the Msg A 1331 (e.g., the transport block 1342).

[0201] A UE and a base station may exchange control signaling. The control signaling may be referred to as L1 / L2 control signaling and may originate from the PHY layer (e.g., layer 1) and / or the MAC layer (e.g., layer 2). The control signaling may comprise downlink control signaling transmitted from the base station to the UE and / or uplink control signaling transmitted from the UE to the base station.

[0202] The downlink control signaling may comprise: a downlink scheduling assignment; an uplink scheduling grant indicating uplink radio resources and / or a transport format; a slot format information; a preemption indication; a power control command; and / or any other suitable signaling. The UE may receive the downlink control signaling in a payload transmitted by the base station on a physical downlink control channel (PDCCH). The payload transmitted on the PDCCH may be referred to as downlink control information (DCI). In some scenarios, the PDCCH may be a group common PDCCH (GC-PDCCH) that is common to a group of UEs.

[0203] A base station may attach one or more cyclic redundancy check (CRC) parity bits to a DCI in order to facilitate detection of transmission errors. When the DCI is intended for a UE (or a group of the UEs), the base station may scramble the CRC parity bits with an identifier of the UE (or an identifier of the group of the UEs). Scrambling the CRC parity bits with the identifier may comprise Modulo-2 addition (or an exclusive OR operation) of the identifier value and the CRC parity bits. The identifier may comprise a 16-bit value of a radio network temporary identifier (RNTI).

[0204] DCIs may be used for different purposes. A purpose may be indicated by the type of RNTI used to scramble the CRC parity bits. For example, a DCI having CRC parity bits scrambled with a paging RNTI (P- RNTI) may indicate paging information and / or a system information change notification. The P-RNTI may be predefined as “FFFE” in hexadecimal. A DCI having CRC parity bits scrambled with a system information RNTI (SI-RNTI) may indicate a broadcast transmission of the system information. The SI-RNTI may be predefined as “FFFF” in hexadecimal. A DCI having CRC parity bits scrambled with a random access RNTI (RA-RNTI) may indicate a random access response (RAR). A DCI having CRC parity bits scrambled with a cell RNTI (C-RNTI) may indicate a dynamically scheduled unicast transmission and / or a triggering of PDCCH-ordered random access. A DCI having CRC parity bits scrambled with a temporary cell RNTI (TC-RNTI) may indicate a contention resolution (e.g., a Msg 3 analogous to the Msg 31313 illustrated in FIG.13A). Other RNTIs configured to the UE by a base station may comprise a Configured Scheduling RNTI (CS-RNTI), a Transmit Power Control-PUCCH RNTI (TPC-PUCCH-RNTI), a Transmit Power Control-PUSCH RNTI (TPC-PUSCH-RNTI), a Transmit Power Control-SRS RNTI (TPC-SRS-RNTI),Docket No.: 24-1237PCT an Interruption RNTI (INT-RNTI), a Slot Format Indication RNTI (SFI-RNTI), a Semi-Persistent CSI RNTI (SP-CSI-RNTI), a Modulation and Coding Scheme Cell RNTI (MCS-C-RNTI), and / or the like.

[0205] Depending on the purpose and / or content of a DCI, the base station may transmit the DCIs with one or more DCI formats. For example, DCI format 0_0 may be used for scheduling of PUSCH in a cell. DCI format 0_0 may be a fallback DCI format (e.g., with compact DCI payloads). DCI format 0_1 may be used for scheduling of PUSCH in a cell (e.g., with more DCI payloads than DCI format 0_0). DCI format 1_0 may be used for scheduling of PDSCH in a cell. DCI format 1_0 may be a fallback DCI format (e.g., with compact DCI payloads). DCI format 1_1 may be used for scheduling of PDSCH in a cell (e.g., with more DCI payloads than DCI format 1_0). DCI format 2_0 may be used for providing a slot format indication to a group of UEs. DCI format 2_1 may be used for notifying a group of UEs of a physical resource block and / or OFDM symbol where the UE may assume no transmission is intended to the UE. DCI format 2_2 may be used for transmission of a transmit power control (TPC) command for PUCCH or PUSCH. DCI format 2_3 may be used for transmission of a group of TPC commands for SRS transmissions by one or more UEs. DCI format(s) for new functions may be defined in future releases. DCI formats may have different DCI sizes, or may share the same DCI size.

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

[0207] FIG.14A illustrates an example of CORESET configurations for a bandwidth part. The base station may transmit a DCI via a PDCCH on one or more control resource sets (CORESETs). A CORESET may comprise a time-frequency resource in which the UE tries to decode a DCI using one or more search spaces. The base station may configure a CORESET in the time-frequency domain. In the example of FIG. 14A, a first CORESET 1401 and a second CORESET 1402 occur at the first symbol in a slot. The first CORESET 1401 overlaps with the second CORESET 1402 in the frequency domain. A third CORESET 1403 occurs at a third symbol in the slot. A fourth CORESET 1404 occurs at the seventh symbol in the slot. CORESETs may have a different number of resource blocks in frequency domain.

[0208] FIG.14B illustrates an example of a CCE-to-REG mapping for DCI transmission on a CORESET and PDCCH processing. The CCE-to-REG mapping may be an interleaved mapping (e.g., for the purposeDocket No.: 24-1237PCT of providing frequency diversity) or a non-interleaved mapping (e.g., for the purposes of facilitating interference coordination and / or frequency-selective transmission of control channels). The base station may perform different or same CCE-to-REG mapping on different CORESETs. A CORESET may be associated with a CCE-to-REG mapping by RRC configuration. A CORESET may be configured with an antenna port quasi co-location (QCL) parameter. The antenna port QCL parameter may indicate QCL information of a demodulation reference signal (DMRS) for PDCCH reception in the CORESET.

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

[0210] As shown in FIG.14B, the UE may determine a time-frequency resource for a CORESET based on RRC messages. The UE may determine a CCE-to-REG mapping (e.g., interleaved or non-interleaved, and / or mapping parameters) for the CORESET based on configuration parameters of the CORESET. The UE may determine a number (e.g., at most 10) of search space sets configured on the CORESET based on the RRC messages. The UE may monitor a set of PDCCH candidates according to configuration parameters of a search space set. The UE may monitor a set of PDCCH candidates in one or more CORESETs for detecting one or more DCIs. Monitoring may comprise decoding one or more PDCCH candidates of the set of the PDCCH candidates according to the monitored DCI formats. Monitoring may comprise decoding a DCI content of one or more PDCCH candidates with possible (or configured) PDCCH locations, possible (or configured) PDCCH formats (e.g., number of CCEs, number of PDCCH candidates in common search spaces, and / or number of PDCCH candidates in the UE-specific search spaces) and possible (or configured) DCI formats. The decoding may be referred to as blind decoding. The UE may determine a DCI as valid for the UE, in response to CRC checking (e.g., scrambled bits for CRC parity bits of the DCI matching a RNTI value). The UE may process information contained in the DCI (e.g., a scheduling assignment, an uplink grant, power control, a slot format indication, a downlink preemption, and / or the like).

[0211] The UE may transmit uplink control signaling (e.g., uplink control information (UCI)) to a base station. The uplink control signaling may comprise hybrid automatic repeat request (HARQ) acknowledgements for received DL-SCH transport blocks. The UE may transmit the HARQDocket No.: 24-1237PCT acknowledgements after receiving a DL-SCH transport block. Uplink control signaling may comprise channel state information (CSI) indicating channel quality of a physical downlink channel. The UE may transmit the CSI to the base station. The base station, based on the received CSI, may determine transmission format parameters (e.g., comprising multi-antenna and beamforming schemes) for a downlink transmission. Uplink control signaling may comprise scheduling requests (SR). The UE may transmit an SR indicating that uplink data is available for transmission to the base station. The UE may transmit a UCI (e.g., HARQ acknowledgements (HARQ-ACK), CSI report, SR, and the like) via a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH). The UE may transmit the uplink control signaling via a PUCCH using one of several PUCCH formats.

[0212] There may be five PUCCH formats and the UE may determine a PUCCH format based on a size of the UCI (e.g., a number of uplink symbols of UCI transmission and a number of UCI bits). PUCCH format 0 may have a length of one or two OFDM symbols and may include two or fewer bits. The UE may transmit UCI in a PUCCH resource using PUCCH format 0 if the transmission is over one or two symbols and the number of HARQ-ACK information bits with positive or negative SR (HARQ-ACK / SR bits) is one or two. PUCCH format 1 may occupy a number between four and fourteen OFDM symbols and may include two or fewer bits. The UE may use PUCCH format 1 if the transmission is 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. The UE may use PUCCH format 2 if the transmission is over one or two symbols and the number of UCI bits is two or more. PUCCH format 3 may occupy a number between four and fourteen OFDM symbols and may include more than two bits. The UE may use PUCCH format 3 if the transmission is four or more symbols, the number of UCI bits is two or more and PUCCH resource does not include an orthogonal cover code. PUCCH format 4 may occupy a number between four and fourteen OFDM symbols and may include more than two bits. The UE may use PUCCH format 4 if the transmission is four or more symbols, the number of UCI bits is two or more and the PUCCH resource includes an orthogonal cover code.

[0213] The base station may transmit configuration parameters to the UE for a plurality of PUCCH resource sets using, for example, an RRC message. The plurality of PUCCH resource sets (e.g., up to four sets) may be configured on an uplink BWP of a cell. A PUCCH resource set may be configured with a PUCCH resource set index, a plurality of PUCCH resources with a PUCCH resource being identified by a PUCCH resource identifier (e.g., pucch-Resourceid), and / or a number (e.g., a maximum number) of UCI information bits the UE may transmit using one of the plurality of PUCCH resources in the PUCCH resource set. When configured with a plurality of PUCCH resource sets, the UE may select one of the plurality of PUCCH resource sets based on a total bit length of the UCI information bits (e.g., HARQ-ACK, SR, and / or CSI). If the total bit length of UCI information bits is two or fewer, the UE may select a firstDocket No.: 24-1237PCT PUCCH resource set having a PUCCH resource set index equal to “0”. If the total bit length of UCI information bits is greater than two and less than or equal to a first configured value, the UE may select a second PUCCH resource set having a PUCCH resource set index equal to “1”. If the total bit length of UCI information bits is greater than the first configured value and less than or equal to a second configured value, the UE may select a third PUCCH resource set having a PUCCH resource set index equal to “2”. If the total bit length of UCI information bits is greater than the second configured value and less than or equal to a third value (e.g., 1406), the UE may select a fourth PUCCH resource set having a PUCCH resource set index equal to “3”.

[0214] After determining a PUCCH resource set from a plurality of PUCCH resource sets, the UE may determine a PUCCH resource from the PUCCH resource set for UCI (HARQ-ACK, CSI, and / or SR) transmission. The UE may determine the PUCCH resource based on a PUCCH resource indicator in a DCI (e.g., with a DCI format 1_0 or DCI for 1_1) received on a PDCCH. A three-bit PUCCH resource indicator in the DCI may indicate one of eight PUCCH resources in the PUCCH resource set. Based on the PUCCH resource indicator, the UE may transmit the UCI (HARQ-ACK, CSI and / or SR) using a PUCCH resource indicated by the PUCCH resource indicator in the DCI.

[0215] FIG.15 illustrates an example of a wireless device 1502 in communication with a base station 1504 in accordance with embodiments of the present disclosure. The wireless device 1502 and base station 1504 may be part of a mobile communication network, such as the mobile communication network 100 illustrated in FIG.1A, the mobile communication network 150 illustrated in FIG.1B, or any other communication network. Only one wireless device 1502 and one base station 1504 are illustrated in FIG. 15, but it will be understood that a mobile communication network may include more than one UE and / or more than one base station, with the same or similar configuration as those shown in FIG.15.

[0216] The base station 1504 may connect the wireless device 1502 to a core network (not shown) through radio communications over the air interface (or radio interface) 1506. The communication direction from the base station 1504 to the wireless device 1502 over the air interface 1506 is known as the downlink, and the communication direction from the wireless device 1502 to the base station 1504 over the air interface is known as the uplink. Downlink transmissions may be separated from uplink transmissions using FDD, TDD, and / or some combination of the two duplexing techniques.

[0217] In the downlink, data to be sent to the wireless device 1502 from the base station 1504 may be provided to the processing system 1508 of the base station 1504. The data may be provided to the processing system 1508 by, for example, a core network. In the uplink, data to be sent to the base station 1504 from the wireless device 1502 may be provided 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 functionality to process the data for transmission. Layer 2 may include an SDAP layer, a PDCP layer,Docket No.: 24-1237PCT an RLC layer, and a MAC layer, for example, with respect to FIG.2A, FIG.2B, FIG.3, and FIG.4A. Layer 3 may include an RRC layer as with respect to FIG.2B.

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

[0219] At the base station 1504, a reception processing system 1512 may receive the uplink transmission from the wireless device 1502. At the wireless device 1502, a reception processing system 1522 may receive the downlink transmission from base station 1504. The reception processing system 1512 and the reception processing system 1522 may implement layer 1 OSI functionality. Layer 1 may include a PHY layer with respect to FIG.2A, FIG.2B, FIG.3, and FIG.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.

[0220] As shown in FIG.15, a wireless device 1502 and the base station 1504 may include multiple antennas. The multiple antennas may be used to perform 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. In other examples, the wireless device 1502 and / or the base station 1504 may have a single antenna.

[0221] The processing system 1508 and the processing system 1518 may be associated with a memory 1514 and a memory 1524, respectively. Memory 1514 and memory 1524 (e.g., one or more non-transitory computer readable mediums) may store computer program instructions or code that may be executed by the processing system 1508 and / or the processing system 1518 to carry out one or more of the functionalities discussed in the present application. Although not shown in FIG.15, the transmission processing system 1510, the transmission processing system 1520, the reception processing system 1512, and / or the reception processing system 1522 may be coupled to a memory (e.g., one or more non- transitory computer readable mediums) storing computer program instructions or code that may be executed to carry out one or more of their respective functionalities.Docket No.: 24-1237PCT

[0222] The processing system 1508 and / or the processing system 1518 may comprise one or more controllers and / or one or more processors. The one or more controllers and / or one or more processors may comprise, for example, a general-purpose processor, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) and / or other programmable logic device, discrete gate and / or transistor logic, discrete hardware components, an on- board unit, 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 the base station 1504 to operate in a wireless environment.

[0223] The processing system 1508 and / or the processing system 1518 may be connected to one or more peripherals 1516 and one or more peripherals 1526, respectively. The one or more peripherals 1516 and the one or more peripherals 1526 may include software and / or hardware that provide features and / or functionalities, for example, a speaker, a microphone, a keypad, a display, a touchpad, a power source, a satellite transceiver, a universal serial bus (USB) port, a hands-free headset, a frequency modulated (FM) radio unit, a media player, an Internet browser, an electronic control unit (e.g., for a motor 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 user input data from and / or provide user output data to the one or more peripherals 1516 and / or the one or more peripherals 1526. The processing system 1518 in the wireless device 1502 may receive power from a power source and / or may be configured to distribute the power to the other components in the wireless device 1502. The power source may comprise one or more sources of power, for example, a battery, a solar cell, a fuel cell, or any combination thereof. The processing system 1508 and / or the processing system 1518 may be connected to a GPS chipset 1517 and a GPS chipset 1527, respectively. The GPS chipset 1517 and the GPS chipset 1527 may be configured to provide geographic location information of the wireless device 1502 and the base station 1504, respectively.

[0224] FIG.16A illustrates an example structure for uplink transmission. A baseband signal representing a physical uplink shared channel may perform one or more functions. The one or more functions may comprise at least one of: scrambling; modulation of scrambled bits to generate complex-valued symbols; mapping of the 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 precoded complex-valued symbols to resource elements; generation of complex-valued time-domain Single Carrier-Frequency Division Multiple Access (SC-FDMA) or CP-OFDM signal for an antenna port; and / or the like. In an example, when transform precoding is enabled, a SC-FDMA signal for uplink transmission mayDocket No.: 24-1237PCT be generated. In an example, when transform precoding is not enabled, a CP-OFDM signal for uplink transmission may be generated by FIG.16A. These functions are illustrated as examples and it is anticipated that other mechanisms may be implemented in various embodiments.

[0225] FIG.16B illustrates an example structure for modulation and up-conversion of a baseband signal to a carrier frequency. The baseband signal may be a complex-valued SC-FDMA or CP-OFDM baseband signal for an antenna port and / or a complex-valued Physical Random Access Channel (PRACH) baseband signal. Filtering may be employed prior to transmission.

[0226] FIG.16C illustrates an example structure for downlink transmissions. A baseband signal representing a physical downlink channel may perform one or more functions. The one or more functions may comprise: scrambling of coded bits in a codeword to be transmitted on a physical channel; modulation of scrambled bits to generate complex-valued modulation symbols; mapping of the complex-valued modulation symbols onto one or several transmission layers; precoding of the complex-valued modulation symbols on a layer for transmission on the antenna ports; mapping of complex-valued modulation symbols for an antenna port to resource elements; generation of complex-valued time-domain OFDM signal for an antenna port; and / or the like. These functions are illustrated as examples and it is anticipated that other mechanisms may be implemented in various embodiments.

[0227] FIG.16D illustrates another example structure for modulation and up-conversion of a baseband signal to a carrier frequency. The baseband signal may be a complex-valued OFDM baseband signal for an antenna port. Filtering may be employed prior to transmission.

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

[0229] A timer may begin running once it is started and continue running until it is stopped or until it 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., the timer may be started or restarted from a value or may be started from zero and expire once it reaches the value). The duration of a timer 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 for a process. When the specification refers to an implementation and procedure related to one or more timers, it will beDocket No.: 24-1237PCT understood that there are multiple ways to implement the one or more timers. For example, it will be understood that one or more of the multiple ways to implement a timer may be used to measure a time period / window for the procedure. For example, a random access response window timer may be used for measuring a window of time for receiving a random access response. In an example, instead of starting and expiry (or expiration) of a random access response window timer, the time difference between two time stamps may be used. When a timer is restarted, a process for measurement of time window may be restarted. Other example implementations may be provided to restart a measurement of a time window.

[0230] A base station may transmit one or more MAC PDUs to a wireless device. In an example, a MAC PDU may be a bit string that is byte aligned (e.g., aligned to a multiple of eight bits) in length. In an example, bit strings may be represented by tables in which the most significant bit is the leftmost bit of the first line of the table, and the least significant bit is the rightmost bit on the last line of the table. More generally, the bit string may be read from left to right and then in the reading order of the lines. In an example, the bit order of a parameter field within a MAC PDU is represented with the first and most significant bit in the leftmost bit and the last and least significant bit in the rightmost bit.

[0231] In an example, a MAC SDU may be a bit string that is byte aligned (e.g., aligned to a multiple of eight bits) in length. In an example, a MAC SDU may be included in a MAC PDU from the first bit onward. A MAC CE may be a bit string that is byte aligned (e.g., aligned to a multiple of eight bits) in length. A MAC subheader may be a bit string that is byte aligned (e.g., aligned to a multiple of eight bits) in length. In an example, a MAC subheader may be placed immediately in front of a corresponding MAC SDU, MAC CE, or padding. A MAC entity may ignore the value of reserved bits in a DL MAC PDU.

[0232] In an example, a MAC PDU may comprise one or more MAC subPDUs. A MAC subPDU of the one or more MAC subPDUs may comprise: a MAC subheader only (including padding); a MAC subheader and a MAC SDU; a MAC subheader and a MAC CE; a MAC subheader and padding, or a combination thereof. The MAC SDU may be of variable size. A MAC subheader may correspond to a MAC SDU, a MAC CE, or padding.

[0233] In an example, when a MAC subheader corresponds to a MAC SDU, a variable-sized MAC CE, or padding, the MAC subheader may comprise: an R field with a one-bit length; an F field with a one-bit length; an LCID field with a multi-bit length; an L field with a multi-bit length, or a combination thereof.

[0234] FIG.17A shows an example of a MAC subheader with an R field, an F field, an LCID field, and an L field. In the example MAC subheader of FIG.17A, the LCID field may be six bits in length, and the L field may be eight bits in length. FIG.17B shows an example of a MAC subheader with an R field, an F field, an LCID field, and an L field. In the example MAC subheader shown in FIG.17B, the LCID field may be six bits in length, and the L field may be sixteen bits in length. When a MAC subheader corresponds to a fixed sized MAC CE or padding, the MAC subheader may comprise: an R field with a two-bit length and an LCIDDocket No.: 24-1237PCT field with a multi-bit length. FIG.17C shows an example of a MAC subheader with an R field and an LCID field. In the example MAC subheader shown in FIG.17C, the LCID field may be six bits in length, and the R field may be two bits in length.

[0235] FIG.18A shows an example of a DL MAC PDU. Multiple MAC CEs, such as MAC CE 1 and 2, may be placed together. A MAC subPDU, comprising a MAC CE, may be placed before: a MAC subPDU comprising a MAC SDU, or a MAC subPDU comprising padding. FIG.18B shows an example of a UL MAC PDU. Multiple MAC CEs, such as MAC CE 1 and 2, may be placed together. In an embodiment, a MAC subPDU comprising a MAC CE may be placed after all MAC subPDUs comprising a MAC SDU. In addition, the MAC subPDU may be placed before a MAC subPDU comprising padding.

[0236] In an example, a MAC entity of a base station may transmit one or more MAC CEs to a MAC entity of a wireless device. FIG.19 shows an example of multiple LCIDs that may be associated with one or more MAC CEs. The one or more MAC CEs comprise at least one of: a SP ZP CSI-RS Resource Set Activation / Deactivation MAC CE, a PUCCH spatial relation Activation / Deactivation MAC CE, a SP SRS Activation / Deactivation MAC CE, a SP CSI reporting on PUCCH Activation / Deactivation MAC CE, a TCI State Indication for UE-specific PDCCH MAC CE, a TCI State Indication for UE-specific PDSCH MAC CE, an Aperiodic CSI Trigger State Subselection MAC CE, a SP CSI-RS / CSI-IM Resource Set Activation / Deactivation MAC CE, a wireless device contention resolution identity MAC CE, a timing advance command MAC CE, a DRX command MAC CE, a Long DRX command MAC CE, an SCell activation / deactivation MAC CE (1 Octet), an SCell activation / deactivation MAC CE (4 Octet), and / or a duplication activation / deactivation MAC CE. In an example, a MAC CE, such as a MAC CE transmitted by a MAC entity of a base station to a MAC entity of a wireless device, may have an LCID in the MAC subheader corresponding to the MAC CE. Different MAC CE may have different LCID in the MAC subheader corresponding to the MAC CE. For example, an LCID given by 111011 in a MAC subheader may indicate that a MAC CE associated with the MAC subheader is a long DRX command MAC CE.

[0237] In an example, the MAC entity of the wireless device may transmit to the MAC entity of the base station one or more MAC CEs. FIG.20 shows an example of one or more MAC CEs. The one or more MAC CEs may comprise at least one of: a short buffer status report (BSR) MAC CE, a beam failure recovery (BFR) MAC CE, a truncated BFR MAC CE, a truncated enhanced BFR 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 etc. In an example, a MAC CE may have an LCID in the MAC subheader corresponding to the MAC CE. Different MAC CE may have different LCID in the MAC subheader corresponding to the MAC CE. For example, an LCID given by 43 in a MAC subheader may indicate that a MAC CE associated with the MAC subheader is a truncated enhanced BFR MAC CE.Docket No.: 24-1237PCT

[0238] In carrier aggregation (CA), two or more component carriers (CCs) may be aggregated. A wireless device may simultaneously receive or transmit on one or more CCs, depending on capabilities of the wireless device, using the technique of CA. In an embodiment, a wireless device may support CA for contiguous CCs and / or for non-contiguous 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 a network. During an RRC connection establishment / re-establishment / handover, a cell providing NAS mobility information may be a serving cell. During an RRC connection re-establishment / handover procedure, a cell providing a security input may be a serving cell. In an example, the serving cell may denote a PCell. In an example, a base station may transmit, to a wireless device, one or more messages comprising configuration parameters of a plurality of one or more SCells, depending on capabilities of the wireless device.

[0239] When configured with CA, a base station and / or a wireless device may employ an activation / deactivation mechanism of an SCell to improve battery or power consumption of the wireless device. When a wireless device is configured with one or more SCells, a base station may activate or deactivate at least one of the one or more SCells. Upon configuration of an SCell, the SCell may be deactivated unless an SCell state associated with the SCell is set to “activated” or “dormant”.

[0240] A wireless device may activate / deactivate an SCell in response to receiving an SCell Activation / Deactivation MAC CE (e.g., as shown in FIG.21A and / or FIG.21B which will be described later in this specification). In an example, a base station may transmit, to a wireless device, one or more messages comprising an SCell timer (e.g., sCellDeactivationTimer). In an example, a wireless device may deactivate an SCell in response to an expiry of the SCell timer.

[0241] When a wireless device receives an SCell Activation / Deactivation MAC CE activating an SCell, the wireless device may activate the SCell. In response to the activating the SCell, the wireless device may perform operations comprising SRS transmissions on the SCell; CQI / PMI / RI / CRI reporting for the SCell; PDCCH monitoring on the SCell; PDCCH monitoring for the SCell; and / or PUCCH transmissions on the SCell. In response to activating the SCell, the wireless device may start or restart a first SCell timer (e.g., sCellDeactivationTimer) associated with the SCell. The wireless device may start or restart the first SCell timer in the slot when the SCell Activation / Deactivation MAC CE activating the SCell has been received. In an example, in response to the activating the SCell, the wireless device may (re-)initialize one or more suspended configured uplink grants of a configured grant Type 1 associated with the SCell according to a stored configuration. In an example, in response to activating the SCell, the wireless device may trigger PHR.

[0242] When a wireless device receives an SCell Activation / Deactivation MAC CE deactivating an activated SCell, the wireless device may deactivate the activated SCell. In an example, when a first SCellDocket No.: 24-1237PCT timer (e.g., sCellDeactivationTimer) associated with an activated SCell expires, the wireless device may deactivate the activated SCell. In response to the deactivating the activated SCell, the wireless device may stop the first SCell timer associated with the activated SCell. In an example, in response to the deactivating the activated SCell, the wireless device may clear one or more configured downlink assignments and / or one or more configured uplink grants of a configured uplink grant Type 2 associated with the activated SCell. In an example, in response to the deactivating the activated SCell, the wireless device may: suspend one or more configured uplink grants of a configured uplink grant Type 1 associated with the activated SCell; and / or flush HARQ buffers associated with the activated SCell.

[0243] When an SCell is deactivated, a wireless device may not perform operations comprising: transmitting SRS on the SCell; reporting CQI / PMI / RI / CRI for the SCell; transmitting on UL-SCH on the SCell; transmitting on RACH on the SCell; monitoring at least one first PDCCH on the SCell; monitoring at least one second PDCCH for the SCell; and / or transmitting a PUCCH on the SCell. When at least one first PDCCH on an activated SCell indicates an uplink grant or a downlink assignment, a wireless device may restart a first SCell timer (e.g., sCellDeactivationTimer) associated with the activated SCell. In an example, when at least one second PDCCH on a serving cell (e.g., a PCell or an SCell configured with PUCCH, i.e., PUCCH SCell) scheduling the activated SCell indicates an uplink grant or a downlink assignment for the activated SCell, a wireless device may restart the first SCell timer (e.g., sCellDeactivationTimer) associated with the activated SCell. In an example, when an SCell is deactivated, if there is an ongoing random access procedure on the SCell, a wireless device may abort the ongoing random access procedure on the SCell.

[0244] FIG.21A shows an example of an SCell Activation / Deactivation MAC CE of one octet. A first MAC PDU subheader with a first LCID (e.g., ‘111010’ as shown in FIG.19) may identify the SCell Activation / Deactivation MAC CE of one octet. The SCell Activation / Deactivation MAC CE of one octet may have a fixed size. The SCell Activation / Deactivation MAC CE of one octet may comprise a single octet. The single octet may comprise a first number of C-fields (e.g., seven) and a second number of R-fields (e.g., one).

[0245] FIG.21B shows an example of an SCell Activation / Deactivation MAC CE of four octets. A second MAC PDU subheader with a second LCID (e.g., ‘111001’ as shown in FIG.19) may identify the SCell Activation / Deactivation MAC CE of four octets. The SCell Activation / Deactivation MAC CE of four octets may have a fixed size. The SCell Activation / Deactivation MAC CE of four octets may comprise four octets. The four octets may comprise a third number of C-fields (e.g., 31) and a fourth number of R-fields (e.g., 1).

[0246] In FIG.21A and / or FIG.21B, a Cifield may indicate an activation / deactivation status of an SCell with an SCell index i if an SCell with SCell index i is configured. In an example, when the Ci field is set to one, an SCell with an SCell index i may be activated. In an example, when the Cifield is set to zero, an SCell with an SCell index i may be deactivated. In an example, if there is no SCell configured with SCellDocket No.: 24-1237PCT index i, the wireless device may ignore the Ci field. In FIG.21A and FIG.21B, an R field may indicate a reserved bit. The R field may be set to zero.

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

[0248] In an example, a base station and / or a wireless device may switch a BWP between configured BWPs by means of a DCI or a BWP inactivity timer. When the BWP inactivity timer is configured for a serving cell, the base station and / or the wireless device may switch an active BWP to a default BWP in response to an expiry of the BWP inactivity timer associated with the serving cell. The default BWP may be configured by the network. In an example, for FDD systems, when configured with BA, one UL BWP for each uplink carrier and one DL BWP may be active at a time in an active serving cell. In an example, for TDD systems, one DL / UL BWP pair may be active at a time in an active serving cell. Operating on the one UL BWP and the one DL BWP (or the one DL / UL pair) may improve wireless device battery consumption. BWPs other than the one active UL BWP and the one active DL BWP that the wireless device may work on may be deactivated. On deactivated BWPs, the wireless device may: not monitor PDCCH; and / or not transmit on PUCCH, PRACH, and UL-SCH.

[0249] In an example, a serving cell may be configured with at most a first number (e.g., four) of BWPs. In an example, for an activated serving cell, there may be one active BWP at any point in time. In an example, a BWP switching for a serving cell may be used to activate an inactive BWP and deactivate an active BWP at a time. In an example, the BWP switching may be controlled by a PDCCH indicating a downlink assignment or an uplink grant. In an example, the BWP switching may be controlled by a BWP inactivity timer (e.g., bwp-InactivityTimer). In an example, the BWP switching may be controlled by a MAC entity in response to initiating a Random Access procedure. Upon addition of an SpCell or activation of an SCell, one BWP may be initially active without receiving a PDCCH indicating a downlink assignment or an uplink grant. The active BWP for a serving cell may be indicated by RRC and / or PDCCH. In an example, for unpaired spectrum, a DL BWP may be paired with a UL BWP, and BWP switching may be common for both UL and DL.Docket No.: 24-1237PCT

[0250] FIG.22 shows an example of BWP switching on a cell (e.g., PCell or SCell). In an example, a wireless device may receive, from a base station, at least one RRC message comprising parameters of a cell and one or more BWPs associated with the cell. The RRC message may comprise: RRC connection reconfiguration message (e.g., RRCReconfiguration); RRC connection reestablishment message (e.g., RRCReestablishment); and / or RRC connection setup message (e.g., RRCSetup). Among the one or more BWPs, at least one BWP may be configured as the first active BWP (e.g., BWP 1), one BWP as the default BWP (e.g., BWP 0). The wireless device may receive a command (e.g., RRC message, MAC CE or DCI) to activate the cell at an nth slot. In case the cell is a PCell, the wireless device may not receive the command activating the cell, for example, the wireless device may activate the PCell once the wireless device receives RRC message comprising configuration parameters of the PCell. The wireless device may start monitoring a PDCCH on BWP 1 in response to activating the cell.

[0251] In an example, the wireless device may start (or restart) a BWP inactivity timer (e.g., bwp- InactivityTimer) at an mthslot in response to receiving a DCI indicating DL assignment on BWP 1. The wireless device may switch back to the default BWP (e.g., BWP 0) as an active BWP when the BWP inactivity timer expires, at sthslot. The wireless device may deactivate the cell and / or stop the BWP inactivity timer when the sCellDeactivationTimer expires (e.g., if the cell is a SCell). In response to the cell being a PCell, the wireless device may not deactivate the cell and may not apply the sCellDeactivationTimer on the PCell.

[0252] In an example, a MAC entity may apply normal operations, on an active BWP for an activated serving cell configured with a BWP, comprising: transmitting on UL-SCH; transmitting on RACH; monitoring a PDCCH; transmitting PUCCH; receiving DL-SCH; and / or (re-) initializing any suspended configured uplink grants of configured grant Type 1 according to a stored configuration, if any.

[0253] In an example, on an inactive BWP for each activated serving cell configured with a BWP, a MAC entity may: not transmit on UL-SCH; not transmit on RACH; not monitor a PDCCH; not transmit PUCCH; not transmit SRS, not receive DL-SCH; clear any configured downlink assignment and configured uplink grant of configured grant Type 2; and / or suspend any configured uplink grant of configured Type 1.

[0254] In an example, if a MAC entity receives a PDCCH for a BWP switching of a serving cell while a Random Access procedure associated with this serving cell is not ongoing, a wireless device may perform the BWP switching to a BWP indicated by the PDCCH. In an example, if a bandwidth part indicator field is configured in DCI format 1_1, the bandwidth part indicator field value may indicate the active DL BWP, from the configured DL BWP set, for DL receptions. In an example, if a bandwidth part indicator field is configured in DCI format 0_1, the bandwidth part indicator field value may indicate the active UL BWP, from the configured UL BWP set, for UL transmissions.Docket No.: 24-1237PCT

[0255] In an example, for a primary cell, a wireless device may be provided by a higher layer parameter Default-DL-BWP a default DL BWP among the configured DL BWPs. If a wireless device is not provided a default DL BWP by the higher layer parameter Default-DL-BWP, the default DL BWP is the initial active DL BWP. In an example, a wireless device may be provided by higher layer parameter bwp-InactivityTimer, a timer value for the primary cell. If configured, the wireless device may increment the timer, if running, every interval of 1 millisecond for frequency range 1 or every 0.5 milliseconds for frequency range 2 if the wireless device may not detect a DCI format 1_1 for paired spectrum operation or if the wireless device may not detect a DCI format 1_1 or DCI format 0_1 for unpaired spectrum operation during the interval.

[0256] In an example, if a wireless device is configured for a secondary cell with higher layer parameter Default-DL-BWP indicating a default DL BWP among the configured DL BWPs and the wireless device is configured with higher layer parameter bwp-InactivityTimer indicating a timer value, the wireless device procedures on the secondary cell may be same as on the primary cell using the timer value for the secondary cell and the default DL BWP for the secondary cell.

[0257] In an example, if a wireless device is configured by higher layer parameter Active-BWP-DL-SCell a first active DL BWP and by higher layer parameter Active-BWP-UL-SCell a first active UL BWP on a secondary cell or carrier, the wireless device may use the indicated DL BWP and the indicated UL BWP on the secondary cell as the respective first active DL BWP and first active UL BWP on the secondary cell or carrier.

[0258] In an example, a set of PDCCH candidates for a wireless device to monitor is defined in terms of PDCCH search space sets. A search space set comprises a CSS set or a USS set. A wireless device monitors PDCCH candidates in one or more of the following search spaces 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 with CRC scrambled by a SI-RNTI on the primary cell of the MCG, a Type0A-PDCCH CSS set configured by searchSpaceOtherSystemInformation in PDCCH-ConfigCommon for a DCI format with CRC scrambled by a SI-RNTI on the primary cell of the MCG, a Type1-PDCCH CSS set configured by ra-SearchSpace in PDCCH-ConfigCommon for a DCI format with CRC scrambled by a RA-RNTI, a MsgB-RNTI, or a TC-RNTI on the primary cell, a Type2- PDCCH CSS set configured by pagingSearchSpace in PDCCH-ConfigCommon for a DCI format with CRC scrambled by a P-RNTI on the primary cell of the MCG, a Type3-PDCCH CSS set configured by 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, only for the primary cell, C-RNTI, MCS-C-RNTI, or CS-RNTI(s), and a USS set configured by 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(s), SL-RNTI, SL-CS-RNTI, or SL-L-CS-RNTI.Docket No.: 24-1237PCT

[0259] In an example, a wireless device determines a PDCCH monitoring occasion on an active DL BWP based on one or more PDCCH configuration parameters (e.g., based on examples of FIG.25 which will be described later) comprising: a PDCCH monitoring periodicity, a PDCCH monitoring offset, and a PDCCH monitoring pattern within a slot. For a search space set (SS s), the wireless device determines that a ^ PDCCH monitoring occasion(s) exists in a slot with number ^^,^in a frame with number ^^if ^^ ⋅ ^frame,^ + ^^ − ^ ^ ^^^ ^ = 0. ^frame,^^ slot ^,^ ^ ^ slot is a number of slots in a frame when numerology µ isconfiguration parameters (e.g., based on examples of. in the PDCCH configuration parameters based on examples of FIG.25). The wireless device monitors PDCCH candidates for the search space set ^ for ^ consecutive slots, starting from slot ^ , and does not monitor PDCCH candidates for search space^ ^,^set ^ for the next ^ − ^ consecutive slots. In an example, a USS at CCE aggregation level ^ ∈^ ^^ ^1,  2,  4,  8,  16 is defined by a set of PDCCH candidates for CCE aggregation level ^.

[0260] In an example, a wireless device decides, for a search space set ^ associated with CORESET ^, CCE indexes for aggregation level ^ corresponding to PDCCH candidate ^ of the search space set in^,^^^^ slot ^ for an active DL BWP of a serving cell corresponding to carrier indicator field value ^ as ^ ⋅^^^,^$%,&⋅'CCE,(^^" " "⁄ + + ^ ^^^ ^ ^ + 4, where, = 0 for any CSS; = ^^ # . / 0 23(,) ^^ CCE,! !,^ !,^s,f s,f s,fforCCEs, numbered from 0 to ^ − 1, in CORESET ^; ^ is the carrier indicator field value if theCCE,! ^^wireless device is configured with a carrier indicator field by CrossCarrierSchedulingConfig for the serving ()) cell on which PDCCH is monitored; otherwise, including for any CSS, ^ = 0; ^ = 0, ... , < −^^ ^,^ ^,^^^ ^^())1, where < is the number of PDCCH candidates the wireless device is())^ of a search space set ^ for a serving cell corresponding to ^ ; for any CSS, < =^^ ^,max()) ()) ())< ; for a USS, < is the maximum of < over all configured ^ values for a CCE aggregation^^^,^^,max^,0 ^^used for ^ is the C-RNTI.RNTI

[0261] In an example, a wireless device may monitor a set of PDCCH candidates according to configuration parameters of a search space set comprising a plurality of search spaces (SSs). The wireless device may monitor a set of PDCCH candidates in one or more CORESETs for detecting one or more DCIs. A CORESET may be configured based on the examples of FIG.25 which will be described later.

[0262] In an example, monitoring a set of PDCCH candidates may comprise decoding one or more PDCCH candidates of the set of the PDCCH candidates according to the monitored DCI formats.Docket No.: 24-1237PCT Monitoring may comprise decoding a DCI content of one or more PDCCH candidates with possible (or configured) PDCCH locations, possible (or configured) PDCCH formats (e.g., number of CCEs, number of PDCCH candidates in common SSs, and / or number of PDCCH candidates in the UE-specific SSs) and possible (or configured) DCI formats. The decoding may be referred to as blind decoding. The possible DCI formats may be based on example embodiments of FIG.23.

[0263] FIG.23 shows examples of DCI formats which may be used by a base station to transmit control information to a wireless device or used by the wireless device for PDCCH monitoring. Different DCI formats may comprise different DCI fields and / or have different DCI payload sizes. Different DCI formats may have different signaling purposes.

[0264] In an example, DCI format 0_0 may be used to schedule PUSCH in one cell. DCI format 0_1 may be used to schedule one or multiple PUSCH in one cell or indicate CG-DFI (configured grant-Downlink Feedback Information) for configured grant PUSCH, etc. The DCI format(s) which the wireless device monitors in a SS may be configured.

[0265] In the example of FIG.23, DCI format 0_3 may be used to schedule one PUSCH in one cell, or multiple PUSCHs in multiple cells with one PUSCH per cell. DCI format 1_3 may be used to schedule one PDSCH in one cell, or multiple PDSCHs in multiple cells with one PDSCH per cell.

[0266] FIG.24 shows an example of RRC configuration of a serving cell. In an example, a base station may transmit to a wireless device one or more RRC messages comprising configuration parameters of a serving cell in a ServingCellConfig IE. ServingCellConfig IE is used to configure (add or modify) the wireless device with a serving cell, which may be the SpCell or an SCell of an MCG or SCG. The configuration parameters are mostly wireless device specific but partly also cell specific (e.g., in additionally configured bandwidth parts). Reconfiguration between a PUCCH and PUCCHless SCell is only supported using an SCell release and add.

[0267] In the example of FIG.24, one or more parameters configured in ServingCellConfig IE may indicate a plurality of BWPs (e.g., downlink BWPs and / or uplink BWPs) of the cell, CSI measurement configuration (csi-MeasConfg), uplink configuration (uplinkConfig), cross carrier scheduling configuration (crossCarrierSchedulingConfigRelease-r17) for single-cell cross-carrier scheduling, and / or multi-cell scheduling (mc-DCI-SetOfCellsToAddModList-r18).

[0268] In an example, each downlink BWP of the serving cell may be associated with BWP specific PDCCH / PDSCH parameters (configured in BWP-DownlinkDedicatd IE, and / or PDCCH-Config IE as shown in FIG.25 and / or FIG.26 which will be described later). A downlink BWP may be activated or deactivated based on examples of FIG.22.

[0269] In an example, uplinkConfig may indicate one or more uplink BWPs configured on the serving cell. Each uplink BWP of the serving cell may be associated with BWP specific PUSCH parameters (configuredDocket No.: 24-1237PCT in PUSCH-Config IE as shown in FIG.27 which will be described later). An uplink BWP may be activated or deactivated based on examples of FIG.22.

[0270] In the example of FIG.24, mc-DCI-SetOfCellsToAddModList-r18 IE is configured for Rel.18 multi- carrier / cell scheduling and may comprise a plurality of carrier / cell sets, for multi-cell PDSCH / PUSCH scheduling from the serving cell, with each set comprising a number of carriers / cells defined by MC-DCI- SetOfCells-r18 IE. The maximum number of sets may be equal to or less than maxNrofSetsOfCells-r18 which is reported as UE capability. Up to 4 sets of cells may be configured per PUCCH group (wherein PUCCH transmissions for cells configured with the same PUCCH group are transmitted via the same PUCCH cell). When mc-DCI-SetOfCellsToAddModList-r18 IE is configured to a SCell, PCell cannot be included in either ScheduledCellListDCI-1-3 or ScheduledCellListDCI-0-3.

[0271] In the example of FIG.24, MC-DCI-SetOfCells-r18 IE comprises a cell / carrier set ID (e.g., setOfCellsId-r18) identifying the cell set, a nCI value (e.g., nCI-Value-r18) identifying the cell set for search space candidate determination, a list of scheduled cells (each identified by a respective serving cell index) (e.g., scheduledCellListDCI-1-3-r18 for PDSCH scheduling, and / or scheduledCellListDCI-0-3-r18 for PUSCH scheduling), a list of scheduled cell combo (each identified by a respective serving cell index) (e.g., scheduledCellComboListDCI-1-3-r18 for PDSCH scheduling, and / or scheduledCellComboListDCI-0-3-r18 for PUSCH scheduling), a PDSCH TDRA field index list (e.g., tdra-FieldIndexListDCI-1-3-r18), a PUSCH TDRA field index list (e.g., tdra-FieldIndexListDCI-0-3-r18), etc.

[0272] In the example of FIG.24, scheduledCellListDCI-1-3-r18 and / or scheduledCellListDCI-0-3-r18 configures the list of possible co-scheduled cells (which are scheduled cells by the same DCI) in the set for DL scheduling via DCI format 1_3 and DCI format 0_3 respectively. The serving cells in the list are in ascending order of serving cell indices and are mapped to index {0, 1, 2, 3} in the set. Total number of cells within the same set of cells i.e., in scheduledCellListDCI-1-3 and scheduledCellListDCI-0-3, is up to 4.

[0273] In the example of FIG.24, scheduledCellComboListDCI-1-3-r18 and / or scheduledCellComboListDCI-0-3-r18 configures the table for combinations of co-scheduled cells for DL scheduling via DCI format 1_3 and DCI format 0_3, respectively.

[0274] In the example of FIG.24, tdra-FieldIndexListDCI-1-3-r18 configures each row of the joint TDRA field table for DL scheduling via DCI format 1_3 containing the applicable TDRA field indexes for multiple BWPs / cells, where the TDRA index for a BWP of a cell points to a corresponding TDRA in the TDRA table applicable for DCI format 1_1, the order of TDRA index in each row refers the BWP-Id for a cell and the order of cells in scheduledCellListDCI-1-3 (i.e., first TDRA index in a row is for the smallest BWP-Id that can be scheduled by the DCI format 1_3, as specified in TS 38.212, of the first cell in scheduledCellListDCI-1-3, second TDRA index in a row is for the second smallest BWP-Id that can be scheduled by the DCI format 1_3, as specified in 38.212, of the first cell and so on ), and the number ofDocket No.: 24-1237PCT TDRA indices in a row of TDRA-FieldIndexDCI-1-3 should be the same as the total number of BWPs that can be scheduled by the DCI format 1_3, as specified in 38.212, across cells included in scheduledCellListDCI-1-3.

[0275] In the example of FIG.24, tdra-FieldIndexListDCI-0-3-r18 configures each row of the joint TDRA field table for UL scheduling via DCI format 0_3 containing the applicable TDRA field indexes for multiple BWPs / cells, where the TDRA index for a BWP of a cell points to a corresponding TDRA in the TDRA table applicable for DCI format 0_1, the order of TDRA index in each row refers the BWP-Id for a cell and the order of cells in scheduledCellListDCI-0-3 (i.e., first TDRA index in a row is for the smallest BWP-Id that can be scheduled by the DCI format 0_3, as specified in TS 38.212, of the first cell in scheduledCellListDCI-0-3, second TDRA index in a row is for the second smallest BWP-Id that can be scheduled by the DCI format 0_3, as specified in 38.212, of the first cell and so on ), and the number of TDRA indices in a row of TDRA-FieldIndexDCI-01-3 should be the same as the total number of BWPs that can be scheduled by the DCI format 0_3, as specified in 38.212, across cells included in scheduledCellListDCI-0-3.

[0276] FIG.25 shows an example of PDCCH configuration parameters associated with a BWP of a serving cell. In an example, a base station may transmit to a wireless device one or more RRC messages comprising configuration parameters of a BWP of a serving cell in a BWP-DownlinkDedicated IE. BWP- DownlinkDedicated IE is used to configure the common parameters of a downlink BWP. They are "cell specific" and the network ensures the necessary alignment with corresponding parameters of other wireless devices. The common parameters of the initial bandwidth part of the PCell are also provided via system information. For all other serving cells, the network provides the common parameters via dedicated signaling. BWP-DownlinkDedicated IE of a BWP may be associated with BWP specific PDCCH configuration (pdcch-Config) and / or BWP specific PDSCH configuration (pdsch-Config).

[0277] In the example of FIG.25, pdcch-Config IE configure / indicate a plurality of control resources sets (controlResourceSetToAddModList IE) for PDCCH monitoring on the BWP, a plurality of search spaces (searchSpaceToAddList IE) where search space may be configured as shown in FIG.26 which will be described later.

[0278] In the example of FIG.25, a control resource set (configured by ControlResourceSet IE) may be associated with a control resource set identifier, frequency domain resource indication, time domain duration, CCE-to-REG mapping type indication, etc.

[0279] FIG.26 shows an example of search space configuration parameters. In an example, a base station may transmit to a wireless device one or more RRC messages comprising configuration parameters of a search space of a BWP of a serving cell in a SearchSpace IE. SearchSpace IE is used to define / indicate / configure how / where to search for PDCCH candidates. Each search space is associatedDocket No.: 24-1237PCT with one ControlResourceSet. For a scheduled SCell in the case of cross carrier scheduling, except for nrofCandidates, all the optional fields are absent (regardless of their presence conditions). For a scheduled SpCell in the case of the cross carrier scheduling, if the search space is linked to another search space in the scheduling SCell, all the optional fields of this search space in the scheduled SpCell are absent (regardless of their presence conditions) except for nrofCandidates.

[0280] In the example of FIG.26, for multi-cell scheduling by a DCI, a search space may be configured with DCI formats for the multi-cell scheduling, e.g., indicated by dci-FormatsMC-r18. dci-FormatsMC-r18 may indicate whether DCI format 0_3 only, DCI format 1_3 only, or both DCI format 0_3 and 1_3 are supported on the BWP of the serving cell.

[0281] FIG.27 shows an example of PUSCH configuration parameters of an uplink BWP of a serving cell. In an example, a base station may transmit to a wireless device one or more RRC messages comprising configuration parameters of a PUSCH of an uplink BWP of a serving cell in a PUSCH-Config IE.

[0282] In the example of FIG.27, PUSCH-Config IE of an uplink BWP of a serving cell may indicate a resource allocation type (resourceAllocation) for the PUSCH of the BWP, a plurality of PUSCH time domain allocation lists (e.g., pusch-TimeDomainAllocationList, pusch-TimeDomainAllocationListDCI-0-1-r16, pusch-TimeDomainAllocationListDCI-0-2-r16, pusch-TimeDomainAllocationListForMultiPuSCH-r16) for time-domain configurations for timing of UL assignment to UL data, and a PUSCH configuration for DCI format 0_3 (pusch-ConfigDCI-0-3-r18), etc.

[0283] In the example of FIG.27, the field pusch-TimeDomainAllocationList (with or without suffix) applies to DCI format 0_0, DCI format 0_1 and DCI format 0_3 if the field pusch- TimeDomainAllocationListDCI-0-1 is not configured.

[0284] In the example of FIG.27, pusch-TimeDomainAllocationList comprises a plurality of pdsch- TimeDomainAllocation, each associated with K2, mapping type indication, and startingSymbolAndLength indication. pusch-TimeDomainAllocationList may be used for single-PUSCH scheduling based on examples of FIG.28 which will be described later in this specification.

[0285] In the example of FIG.27, pusch-TimeDomainAllocationListForMultiPuSCH-r16 is used to setup or release a PUSCH-TimeDomainResourceAllocaitonList-r16. PUSCH-TimeDomainResourceAllocaitonList- r16 comprises a list of PUSCH-TimeDomainResourceAllocation-r16, wherein each entry of the list, corresponding to a pushcAllocationList-r16, comprises a plurality of PUSCH TDRA configurations, with each PUSCH TDRA configuration corresponds to a respective PUSCH of multiple PUSCHs scheduled for the BWP of the serving cell. Each PUSCH TDRA configuration may be indicated by PUSCH-Allocation- r16. pusch-TimeDomainAllocationListForMultiPuSCH-r16 may be used for multi-PUSCH scheduling based on examples of FIG.29 which will be described later in this specification.Docket No.: 24-1237PCT

[0286] In an example, pusch-ConfigDCI-0-3-r18 is used to configure PUSCH configurations of the BWP of the serving cell for multi-cell scheduling from another serving cell or a scheduling cell. The pusch- ConfigDCI-0-3-r18 may comprise a resource allocation type (resourceAllocationDCI-0-3-r18) of the PUSCH allocation when scheduled by DCI format 0_3, a number of bits for RV (numberOfBitsForRV-DCI-0-3-r18) in DCI format 0_3 scheduling the PUSCH of this BWP of this co-scheduled cell, a number of bits for HARQ process number (harq-ProcessNumberSzieDCI-0-3-r18) in DCI format 0_3 scheduling the PUSCH of this BWP of this co-scheduled cell, etc.

[0287] FIG.28 shows an example of single PUSCH scheduling on a serving cell. In an example, a base station may transmit to a wireless device RRC message(s) comprising configuration parameters of a PUSCH on a BWP of a cell. The configuration parameters may comprise a list of PUSCH resource allocation configurations (e.g., pusch-TimeDomainAllocaitonList IE or pusch-TimeDomainAllocaitonList-r16 IE, etc., as shown in FIG.27) for single-PUSCH scheduling on the BWP.

[0288] In the example of FIG.28, the list may comprise a number of entries indicating PUSCH time domain resource allocation in a slot. Each entry of the list may comprise a K2 value indicating a slot offset, for a second slot on which a PUSCH is transmitted, from a first slot on which a DCI corresponding to the PUSCH is transmitted. Each entry of the list may further comprise one or more starting symbol and length indications indicating a starting symbol (S) of the slot of the PDSCH and a length (L) of a number of symbols of the PUSCH in the slot. The total number of the entries in the list may be 4, 8, 16, 32, 64, etc.

[0289] In an example, a base station may transmit to a wireless device a DCI (e.g., DCI format 0_0 / 0_1 / 0_2…) comprising a time domain resource allocation (TDRA) field indicating an entry of the list for PUSCH time domain resource indication. The TDRA field may have 2 bits if the total number of the entries is 4, 3 bits if the total number is 8, 4 bits if the total number is 16, etc.

[0290] As shown in FIG.28, DCI1 may comprise the TDRA field indicating the second entry of the list. The second entry of the list may indicate K2=2, S=2 and L=9. In response to receiving the DCI1 with the TDRA field in slot x, the wireless device may determine PUSCH scheduled by the DCI1 is in slot x+2 (e.g., K2=2), with 2nd symbol (e.g., S=2) of the slot as starting symbol of the PUSCH and a total number of symbols of the PUSCH as 9 (e.g., L=9). Based on determined PUSCH resources in slot x+2, the wireless device may transmit the TB via the PUSCH resources.

[0291] FIG.29 shows an example of multiple-PUSCH scheduling on a serving cell. In an example, a base station may transmit to a wireless device RRC message(s) comprising configuration parameters of PUSCH on a BWP of a cell. The configuration parameters may comprise a list of PUSCH resource allocation configurations (e.g., pusch-TimeDomainAllocaitonListForMultiPUSCH-r16 IE as shown in FIG.27) for multi- PUSCH scheduling on the BWP.Docket No.: 24-1237PCT

[0292] In the example of FIG.29, the list may comprise a first number of entries indicating PUSCH time domain resource allocation in a second number of (consecutive or non-consecutive) slots. The total (the first) number of the entries in the list may be 4, 8, 16, 32, 64, etc. Each entry of the list may comprise, for each PUSCH of the multiple PUSCHs, a K2 value indicating a slot offset for a starting slot on which a corresponding PUSCH is transmitted, after a first slot on which a DCI scheduling the multiple PUSCHs of a serving cell is transmitted. Each entry of the list may further comprise, for each PUSCH of the multiple PUSCHs, a starting symbol and a length indication. Each starting symbol and length indication may indicate a starting symbol (S) of a slot of a corresponding PUSCH and a length (L) of a number of symbols of the PUSCH in the slot. The wireless device may determine, based on a PUSCH mapping type, whether the PUSCH is configured with normal CP or extended CP, and / or indicated S and L, a combination of S and L as valid PUSCH allocation based on some predefined criteria (e.g., based on Table 6.1.2.1-1 of TS 38.214).

[0293] In an example, the second number may indicate how many PUSCHs a DCI may schedule on the serving cell. The second number may be configured in the RRC messages (or predefined as a fixed value) for PUSCH configuration. The second number may be determined based on the maximum number of schedulable (or valid) PUSCHs among all entries of the list.

[0294] As shown in FIG.29, the first set {K2, S, L} of entry 1, may indicate, K2=1, S=1, and L=9 for PUSCH 1. The second set {K2, S, L} of entry 1, may indicate, K2=2, S=1, and L=10 for PUSCH 2. The third set {K2, S, L} of entry 1, may indicate, K2=3, S=1, and L=9 for PUSCH 3., etc.

[0295] As shown in FIG.29, the first set {K2, S, L} of entry 2, may indicate, K2=1, S=2, and L=9 for PUSCH 1. The second set {K2, S, L} of entry 2, may indicate, K2=2, S=2, and L=10 for PUSCH 2. The third set {K2, S, L} of entry 2, may indicate, K2=3, S=2, and L=9 for PUSCH 3., etc.

[0296] In an example, a base station may transmit to a wireless device a DCI (e.g., DCI1 in FIG.29) scheduling multiple PUSCHs on a serving cell and comprising a TDRA field indicating an entry of the list for PUSCH time domain resource indication. The TDRA field may have 2 bits if the total number of the entries is 4, 3 bits if the total number is 8, 4 bits if the total number is 16, etc. The DCI may be with a DCI format 0_1 for multiple PUSCH scheduling on a serving cell. Similarly for multiple PDSCH scheduling on the serving cell, the DCI may be with a DCI format 1_1. Different DCI formats may be implemented based on examples of FIG.23.

[0297] As shown in FIG.29, DCI1 may comprise the TDRA field indicating the second entry of the list. The second entry of the list may indicate K2=1, S=2 and L=9 for PUSCH 1, K2=2, S=2 and L=10 for PUSCH 2, K2=3, S=2 and L=9 for PUSCH 3, etc. In response to receiving the DCI1 with the TDRA field, e.g., in slot x, the wireless device may determine slots, with the multiple PUSCHs scheduled by the DCI1, comprise slot x+1, x+2, x+3, etc. (e.g., K2=1 for PUSCH 1, K2=2 for PUSCH 2 and K2=3 for PUSCH 3).Docket No.: 24-1237PCT

[0298] In the example of FIG.29, the first PUSCH of the multiple PUSCHs may be in slot x+1. The first PUSCH may be with 2nd symbol (e.g., S=2) of slot x+1 as starting symbol of the first PUSCH and a total number of symbols of the first PUSCH as 9 (e.g., L=9). The second PUSCH of the multiple PUSCHs may be in slot x+2, with 2nd symbol (e.g., S=2) of slot x+2 as starting symbol of the second PUSCH and a total number of symbols of the second PUSCH as 10 (e.g., L=10). The third PUSCH of the multiple PUSCHs may be in slot x+3, with 2nd symbol (e.g., S=2) of slot x+3 as starting symbol of the third PUSCH and a total number of symbols of the third PUSCH as 9 (e.g., L=9).

[0299] Based on determined multiple PUSCHs on a serving cell, the wireless device may transmit a plurality of TBs via the multiple PUSCHs of the serving cell, each TB being transmitted in a corresponding PUSCH of the multiple PUSCHs.

[0300] FIG.30 shows an example of multiple PDSCH / PUSCH scheduling on multiple cells with one PDSCH / PUSCH per cell. Although the description below for FIG.30 is applied for PDSCH, the example of FIG.30 may be similarly applied for multiple PUSCH scheduling on multiple cells with one PUSCH per cell.

[0301] In an example, to support multiple PDSCH scheduling on multiple cells with one PDSCH per cell (similarly for multiple PUSCH scheduling on multiple cells with one PUSCH per cell), a base station may configure PDCCH / PDSCH parameters on a serving / scheduling cell and one or more co-scheduled cells, based on examples of FIG.24, FIG.25, FIG.26 and / or FIG.27. In an example, the serving / scheduling cell may be configured with MC-DCI-SetOfCells-r18 based on examples of FIG.24. A BWP of the serving / scheduling cell may be associated with a search space configured with dci-FormatsMC-r18 based on examples of FIG.25 and / or FIG.26. PUSCH configuration of one or more BWPs of each co-scheduled cell may be associated with PUSCH-ConfigDCI-0-3-r18 based on examples of FIG.27, etc.

[0302] In the example of FIG.30, a base station may transmit to a wireless device a DCI with DCI format 1_3 scheduling multiple PDSCHs on multiple cells with one PDSCH per cell. The DCI format 1_3 may comprise a plurality of DCI fields. The plurality of DCI fields may comprise a scheduled cell set indicator, a scheduled cells indicator, a BWP ID, a time domain resource allocation / assignment (TDRA) field etc. The plurality of DCI fields may further comprise an NDI field, an RV field and / or a HARQ process number field, etc.

[0303] In an example, a base station may transmit to a wireless device a DCI with DCI format 0_3 scheduling multiple PUSCHs on multiple cells with one PUSCH per cell. The DCI format 0_3 may comprise a plurality of DCI fields. The plurality of DCI fields may comprise a scheduled cell set indicator, a scheduled cells indicator, a BWP ID, a TDRA field etc. The plurality of DCI fields may further comprise an NDI field, an RV field and / or a HARQ process number field, etc.

[0304] In an example, the scheduled cell set indicator, of the DCI format, comprises =log2 ^^>?@ bits, where ^^>?is the number of cell sets which are configured by MC-DCI-SetofCellsToAddModList (as shownDocket No.: 24-1237PCT in FIG.24) to be respectively scheduled by DCI format 0_3 / 1_3 from the cell on which this format is carried by PDCCH. If present, this field is used to indicate the scheduled cell set according to Table 7.3.1.1.4-1 of TS 38.212; otherwise, the scheduled cell set is the cell set configured to be scheduled by DCI format 0_3 / 1_3 from the cell by MC-DCI-SetofCellsToAddModList. In an example, the scheduled cell set indicator mapped to 0 indicates that the cells configured by the 1stentry in scheduledCellComboListDCI-1-3 (e.g., configured on the serving / scheduling cell as shown in FIG.24) are indicated. The scheduled cell set indicator mapped to 1 indicates that the cells configured by the 2ndentry in scheduledCellComboListDCI-1- are indicated, and so on.

[0305] In an example, the scheduled cells indicator, of the DCI format, may comprise=log2 AB)@bits indicating the scheduled cells in the scheduled cell set indicated by the scheduled cell set indicator, whereAB)is the number of entries in the scheduledCellComboListDCI-1-3 (as shown in FIG.24). only one entry is configured in the scheduledCellComboListDCI-1-3, the scheduled cells are the cells configured by scheduledCellComboListDCI-1-3. The scheduled cells indicator may be zero bit (or be absent in DCI format 1_3) if the scheduledCellComboListDCI-1-3 for the scheduled cell set is not configured.

[0306] In an example, a BWP indicator field, of the DCI format, comprises a number of bits, where the number is determined as =log2^CDE,$FG@, where ^ $FG $FGCDE,$FG = ^CDE,HH^ + 1 if ^CDE,HH^ ≤ 3,^C$DFGE,HH^is the DLacross all the cells configured by higher layer parameter scheduledCellListDCI-1-3 in the scheduled cell set, in which case the bandwidth part indicator is equivalent to the ascending order of the $FG $FG higher layer parameter BWP-Id. Otherwise (if ^ > 3), ^ = ^ , in which case theCDE,$FGCDE,HH^ CDE,HH^bandwidth part indicator is defined in Table 7.3.1.1.2-1 of TS 38.212. In an example, the field is only applicable to a scheduled cell with the number of configured DL BWPs larger than 1, including the initial DL bandwidth part, and is applied to the applicable scheduled cells in the scheduled cell set independently. If the wireless device does not support active BWP change via DCI, the wireless device ignores this bit field. If this field indicates a code point that does not correspond to a configured BWP of a scheduled cell, the wireless device ignores this bit field for the scheduled cell, and operates on the active BWP of the scheduled cell.

[0307] In an example, the TDRA field, of the DCI format, comprise log (A ) bits, where A is = @KBHL KBHL2 the number of entries in the tdra-FieldIndexListDCI-1-3 (as shown field is used to indicatean entry in the tdra-FieldIndexListDCI-1-3 according to Table 7.3.1.2.4-2 of TS 38.212. Each entry in the tdra-FieldIndexListDCI-1-3 contains the ‘Time domain resource assignment (TDRA)’ index for each BWP of each cell in the scheduled cell set, where the ‘TDRA’ indexes for all the cells are placed according to an ascending order of a serving cell index, and the ‘TDRA’ indexes for all the BWPs of a cell are placed according to an ascending order of the higher layer parameter BWP-Id. PDSCH TDRA table determinationDocket No.: 24-1237PCT based on the TDRA field for DCI format 1_3 may be illustrated based on examples of FIG.33A and FIG. 33B which will be described later in this specification.

[0308] Based on the example of FIG.30, when the wireless device receives the DCI format 0_3 / 1_3, the wireless device may receive multiple PDSCHs on the co-scheduled cells (or transmit multiple PUSCHs on the co-scheduled cells), where each co-scheduled cell is scheduled with at most one PDSCH / PUSCH. The PDSCH / PUSCH for each co-scheduled cell may be determined based on the TDRA field of DCI format 0_3 / 1_3 as shown FIG.31.

[0309] FIG.31 shows an example of TDRA determination for multiple PUSCH scheduling on multiple cells with one PUSCH per cell. In the example of FIG.31, and based on examples of FIG.24, MC-DCI- SetOfCells-r18 of a serving / scheduling cell may be configured with a tdra-FieldIndexListDCI-0-3-r18 IE (as shown in FIG.24).

[0310] In the example of FIG.31, each entry in the tdra-FieldIndexListDCI-0-3 contains the TDRA index for each BWP of each cell in the scheduled cell set, where the TDRA indexes for all the cells are placed according to an ascending order of a serving cell index, and the TDRA indexes for all the BWPs of a cell are placed according to an ascending order of the higher layer parameter BWP-Id. In the example FIG.31, the first TDRA index (TDRA#1), located the leftmost of each entry, is used for TDRA index indication for BWP 1 of cell 1, the second TDRA index (TDRA#2), located the second leftmost of each entry, is used for TDRA index indication for BWP 2 of cell 1, etc.

[0311] In the example of FIG.31, when the wireless device receives the DCI format 0_3, the wireless device determines, for an active BWP of each co-scheduled cell, K2, S and L for PUSCH transmission on the active BWP of the corresponding co-scheduled cell.

[0312] For example, when the TDRA field indicates entry 1 of tdra-FieldIndexListDCI-0-3, if the active BWP of cell 1 is BWP 1 (indicated by the BWP ID of DCI format 0_3), the wireless device uses the TDRA table configured for DCI format 0_1 (scheduling single PUSCH on cell 1) on BWP 1 of cell 1 (1stTDRA table, as shown in FIG.31, which is a pusch-TimeDomainAllocationList based on examples of FIG.27). The wireless device determines K2, S and L based on TDRA#1 indicated for BWP1 of Cell 1 in entry 1 of tdra-FieldIndexListDCI-0-3. In an example, when TDRA#1 indicates the 2ndentry, the wireless device may determine that K2=2, S=2 and L=9 for PUSCH transmission on BWP 1 of cell 1.

[0313] In an example, if the active BWP of cell 1 is BWP 2 (indicated by the BWP ID of DCI format 0_3), the wireless device uses the TDRA table configured for DCI format 1_1 (scheduling single PUSCH on cell 1) on BWP 2 of cell 1 (2ndTDRA table, as shown in FIG.31, which is a pusch-TimeDomainAllocationList based on examples of FIG.27). The wireless device determines K2, S and L based on TDRA#2 indicated for BWP2 of Cell 1 in entry 1 of tdra-FieldIndexListDCI-0-3. In an example, when TDRA#2 indicates the 1stDocket No.: 24-1237PCT entry, the wireless device may determine that K2=1, S=2 and L=12 for PUSCH transmission on BWP 2 of cell 1.

[0314] In an example, the wireless device, based on the examples described above, determines for each co-scheduled cell, K2, S and L for a PUSCH transmission on a respective cell (or active BWP of a respective cell).

[0315] In this specification, scheduling, by a single DCI with a DCI format (received via a serving / scheduling cell), multiple PDSCHs / PUSCHs on multiple cells with one PDSCH / PUSCH per cell (wherein the multiple cells have the same SCS and / or are the same carrier type (licensed / unlicensed, FR1 / FR2 / FR2-2)), may be referred to as Type 1 multi-cell scheduling. In Rel.183GPP specification, this DCI format may comprise DCI format 1_3 for PDSCH scheduling and / or DCI format 0_3 for PUSCH scheduling.

[0316] In an example, due to limited time unit for Rel-18 multi-carrier scheduling, some important use cases were excluded from Rel-18, e.g., different SCSs among co-scheduled cells, different carrier types among co-scheduled cells. Co-scheduled carriers with different SCSs have high commercial needs for operators, e.g., 3.5GHz TDD + Sub-3GHz FDD, FR1 + FR2, etc.

[0317] Furthermore, two DCI formats were introduced in Rel-18, as DCI format 0_3 and 1_3 for Type 1 multi-cell scheduling. Each DCI format 0_3 or 1_3 can schedule up to 4 cells with limitation of a single PUSCH or PDSCH per scheduled cell. In Rel-17, for FR2 with high SCS, multi-PDSCH / PUSCH scheduling was introduced, i.e., up to 8 PUSCHs or PDSCHs on a single serving cell can be scheduled by a single DCI format 0_1 or 1_1, in order to save UE power consumption and reduce PDCCH overhead.

[0318] In an example, it may be desired to support, in 3GPP Rel.19, multiple-cell multi-PDSCH / PUSCH scheduling without (or by removing) the limitations of Rel.18 multi-cell scheduling. Example of Rel.19 multi- cell multi-PDSCH / PUSCH scheduling may be illustrated based on examples of FIG.32.

[0319] In the example of FIG.32, a serving / scheduling cell may be configured with a SCS different from one or more co-scheduled cells, e.g., CC1 with 30KHz SCS, CC2 with 15KHz SCS, CC3 with 60KHz SCS and CC4 with 120KHz SCS, where CC1 co-schedules CC2, CC3 and CC4, together with CC1 or not together with CC1. CC1 may be configured in the same frequency range (FR) or different FR(s) of CC2, CC3 and / or CC4. In the example of FIG.32, CC1 may be co-scheduled with a single PDSCH, CC2 may be co-scheduled with two PDSCHs, CC3 with three PDSCHs, and / or CC4 with four PDSCHs, wherein different co-scheduled cells may be co-scheduled with different number of PDSCHs. Example of FIG.32 may further reduce power consumption of a wireless device for PDCCH monitoring / processing when multiple carriers / cells are configured with different FRs / SCSs, compared with Rel.18 multi-cell multi- PDSCH / PUSCH scheduling with limitations (e.g., one PDSCH / PUSCH per cell, same carrier type, same SCS among co-scheduled cells).Docket No.: 24-1237PCT

[0320] In an example, some 3GPP paper disclosed that it is straightforward to combine multi-cell scheduling and multi-PDSCH / PUSCH scheduling in Rel-19 to fully exploit the gain of power saving and PDCCH overhead reduction so that one DCI format 0_3 or 1_3 can schedule multiple cells with one or multiple PUSCHs / PDSCHs per scheduled cell. Some 3GPP paper disclose that this is especially useful when the scheduling cell in FR1 with a lower SCS schedules multiple cells in FR2 with higher SCS.

[0321] In this specification, scheduling, by a single DCI with a DCI format (received via a serving / scheduling cell), multiple PDSCHs / PUSCHs on multiple cells with at least a first cell being scheduled with at least two PDSCHs / PUSCHs (wherein the multiple cells have the same / different SCS(s) and / or are the same / different carrier type(s) (licensed / unlicensed, FR1 / FR2 / FR2-2)), may be referred to as Type 2 multi-cell scheduling. This DCI format may reuse the existing DCI format 1_3 for PDSCH scheduling and / or DCI format 0_3 for PUSCH scheduling.

[0322] In existing technologies, power saving of a wireless device may be enabled during active-time (of a DRX configuration if the DRX is configured) via cross-slot scheduling. cross-slot scheduling may facilitate the wireless device to achieve power saving with the assumption that the wireless device will not be scheduled to receive PDSCH, triggered to receive A-CSI or transmit a PUSCH scheduled by the PDCCH until the minimum scheduling offsets K0 and K2. Dynamic adaptation of the minimum scheduling offsets K0 and K2 is controlled by PDCCH.

[0323] In an example, K2 is a time offset between a DCI and a PUSCH scheduled by the DCI, e.g., based on examples of FIG.28. Similarly, K0 is a time offset between a DCI and a PDSCH scheduled by the DCI.

[0324] In an example, the minimum scheduling offsets K0 and K2 may be configured by RRC message for a serving cell or a BWP of a serving cell. In an example, the minimum scheduling offsets K2 (MinSchedulingOffsetK2-Values) may be configured for an UL BWP of the serving cell based on examples of FIG.27. Similarly, the minimum scheduling offsets K0 (MinSchedulingOffsetK0-Values) may be configured in PDSCH configuration of a DL BWP of the serving cell.

[0325] In this specification, a minimum scheduling offset K0 may be referred to as K0min.

[0326] In this specification, a minimum scheduling offset K2 may be referred to as K2min.

[0327] In existing technologies, a DCI (e.g., DCI format 0_1 / 1_1 / 0_3 / 1_3) may comprise a 'Minimum applicable scheduling offset indicator' field indicating an applicable K0min / K2min.1 bit indication of the 'Minimum applicable scheduling offset indicator' field is used to determine the minimum applicable K0 for the active DL BWP and the minimum applicable K2 value for the active UL BWP, if configured respectively, e.g., according to Table 7.3.1.1.2-33 of TS 38.214. In an example, the bit set to ‘0’ may indicate that the first value of MinSchedulingOffsetK0-Values (and / or MinSchedulingOffsetK1-Values) is applicable. The bit set to ‘1’ may indicate that the second value of MinSchedulingOffsetK0-Values (and / or MinSchedulingOffsetK1-Values) is applicable. If the minimum applicable K0 is indicated, the minimumDocket No.: 24-1237PCT applicable value of the aperiodic CSI-RS triggering offset for an active DL BWP shall be the same as the minimum applicable K0 value.

[0328] In existing technologies, when a wireless device is configured with minimumSchedulingOffsetK0 in an active DL BWP, the wireless device applies a minimum scheduling offset restriction indicated by the 'Minimum applicable scheduling offset indicator' field in DCI format 0_1, 0_3, 1_1 or 1_3, if the same field is available. When the wireless device is configured with minimumSchedulingOffsetK0 in an active DL BWP and it has not received 'Minimum applicable scheduling offset indicator' field in DCI format 0_1, 0_3, 1_1 or 1_3, the wireless device applies a minimum scheduling offset restriction indicated based on 'Minimum applicable scheduling offset indicator' value '0'.

[0329] In existing technologies, when the minimum scheduling offset restriction is applied the wireless device is not expected to be scheduled with a DCI in slot n to receive a PDSCH scheduled with C-RNTI, ′CS- N I r C - - N 2"R T o M S C R TI with K0 smaller than MN0$O^ ⋅2"P, where K0minand Q are the applied minimum scheduling offset restriction and the DL BWP of the scheduled cell when receivingthe DCI in slot n, respectively, and Q′is the numerology of the new active DL BWP in case of active DL BWP change in the scheduled cell and is equal to Q, otherwise.

[0330] In existing technologies, the minimum scheduling offset restriction is not applied when PDSCH transmission is scheduled with C-RNTI, CS-RNTI or MCS-C-RNTI in common search space associated with CORESET0 and default PDSCH time domain resource allocation is used, in the search space set provided by recoverySearchSpaceId when monitoring PDCCH or when PDSCH transmission is scheduled with SI-RNTI, MSGB-RNTI or RA-RNTI.

[0331] In existing technologies, when the wireless device is configured with minimumSchedulingOffsetK2 in an active UL BWP, the wireless device applies a minimum scheduling offset restriction indicated by the 'Minimum applicable scheduling offset indicator' field in DCI format 0_1, 0_3, 1_1 or 1_3 if the same field is available.

[0332] When the wireless device is configured with minimumSchedulingOffsetK2 in an active UL BWP and it has not received 'Minimum applicable scheduling offset indicator' field in DCI format 0_1, 0_3, 1_1 or 1_3, the wireless device applies a minimum scheduling offset restriction indicated based on 'Minimum applicable scheduling offset indicator' value '0'.

[0333] When the minimum scheduling offset restriction is applied, the wireless device is not expected to be scheduled with a DCI in slot n to transmit a PUSCH scheduled with C-RNTI, CS-RNTI, MCS-C-RNTI or ′SP- S- N I ih s 2"C I R T wt K2 maller than MN2$O^ ⋅P, where K2minand Q are the applied minimum scheduling offset restriction and the numerology ofUL BWP of the scheduled cell when receiving the DCI inDocket No.: 24-1237PCT slot n, respectively, and Q′is the numerology of the new active UL BWP in case of active UL BWP change in the scheduled cell and is equal to Q, otherwise. The minimum scheduling offset restriction is not applied when PUSCH transmission is scheduled by RAR UL grant or fallbackRAR UL grant for RACH procedure, or when PUSCH is scheduled with TC-RNTI.

[0334] In an example, the wireless device may determine, for processing the DCI indicating the change of minimum scheduling offset restriction, an application delay of the change of the minimum scheduling offset restriction when the wireless device receives a DCI indicating a change of K0min / K2min.

[0335] FIG.33A and FIG.33B show examples of application delays for K0min / K2minwhen receiving DCI indicating the K0min / K2min.

[0336] In an example, when a wireless device is scheduled with DCI format 0_1, 0_3, 1_1 or 1_3 with a 'Minimum applicable scheduling offset indicator' field in slot n, the wireless device determines the K0min and K2min values, if configured respectively, to be applied, while the previously applied K0min and / or K2min values are applied until the new values take effect.

[0337] In the example of FIG.33A, if the DCI in slot n indicating a change of K0min / K2min also indicates an active DL (UL) BWP change of a serving cell (a scheduling cell or a scheduled cell), the indicated K0min(K2min) value in the new active DL (UL) BWP, if configured, is applied from the slot (e.g., n1 as shown in FIG.33A) indicated by the slot offset value of the time domain resource assignment field in the DCI. The wireless device does not expect to be scheduled with DCI format 0_1, 0_3, 1_1 or 1_3 with 'Minimum applicable scheduling offset indicator' field indicating another change to K0min or K2min for the same active BWP of the scheduled cell before slot n+X of the scheduling cell.

[0338] In an example, if the DCI does not indicate the active DL / UL BWP change of a serving cell (a scheduling cell or a scheduled cell), change of applied minimum scheduling offset restriction indication carried by DCI in slot n, is applied in slot n+X (e.g., n2 as shown in FIG.33B) of the scheduling cell, based on examples of FIG.33B.

[0339] In the example of FIG.33B, when the DCI format 0_1, 0_3, 1_1 or 1_3 with 'Minimum applicable scheduling offset indicator' field indicating a change to the applied K0min or K2min is contained within the first three symbols of slot n, the value of application delay X is determined by, R = ^ST ^UN0$O^VWX ∙2"Z[^^\[]^\^ , where K0minOld is the currently applied K0min value of the active DLif minimumSchedulingOffsetK0 is not configured for the active DL BWP in the scheduled cell. Zµ is determined by the subcarrier spacing of the active DL BWP in the scheduling cell in slot n, and in Table 5.3.1-1 of TS 38.214 (which is shown in FIG.34 of this specification), and µPDCCHand µPDSCHare the sub-carrier spacing configurations for PDCCH of the active DL BWP in the scheduling cell and PDSCH of the active DL BWP in the scheduled cell, respectively, in slot n.Docket No.: 24-1237PCT

[0340] In an example, after indication of a change to the applied K0min or K2min of the scheduled cell in slot n of the scheduling cell, if there is an active DL BWP change in the scheduling cell before slot n+X, the new K0min and / or K2min values are applied from the first slot no earlier than the start of slot n+X based on the sub- carrier spacing configuration of the active DL BWP in the scheduling cell in slot n.

[0341] FIG.34 shows an example of values of Zµ for application of K0min / K2min.

[0342] In an example, directly combining existing Rel.18 multi-cell scheduling (based on DCI format 1_3 / 0_3) and existing Rel.17 single-cell multi-PDSCH / PUSCH scheduling (based on DCI format 0_1 / 1_1) for Rel.19 Type 2 multi-cell scheduling as proposed by some 3GPP paper may cause misalignment between the base station and the wireless device, e.g., regarding scheduling offset restriction (K0min / K2min) and / or A-CSI report.

[0343] In an example, a wireless device may or may not support Type 1 multi-cell scheduling. The wireless device may or may not support Type 2 multi-cell scheduling. A base station may or may not perform Type 1 multi-cell scheduling. The base station may or may not perform Type 2 multi-cell scheduling.

[0344] In existing technologies, a wireless device, when receiving, at slot n, a DCI scheduling PDSCH / PUSCH and indicating K0min / K2min, applies the indicated K0min / K2minfrom the slot indicated by the slot offset value of the TDRA field in the DCI for the serving cell if there is active BWP change (indicated by the DCI) for a serving cell. Otherwise (if there is no active BWP change indicated by the DCI for the serving cell), the wireless device may apply the indicated K0min / K2minfrom slot n+X (X is determined based on FIG. 33B and / or FIG.34) of the scheduling cell. Existing technologies may not work for DCI format (e.g., DCI format 1_1 / 0_1) scheduling multiple PDSCHs / PUSCHs on a serving cell, or for DCI format (e.g., DCI format 1_3 / 0_3) scheduling multiple PDSCHs / PUSCHs on multiple cells.

[0345] Taking DCI format 1_1 / 0_1 (scheduling multiple PDSCHs / PUSCHs on a serving cell) as an example, when receiving a DCI (e.g., DCI format 0_1 / 1_1) scheduling multiple PDSCHs / PUSCHs on a serving cell, a TDRA field of the DCI may indicate a plurality of TDRA indexes, each index corresponding to a respective PDSCH / PUSCH of the multiple PDSCHs / PUSCHs as shown in FIG.29. When The DCI also indicates an applicable K0min / K2min (where the DCI indicates or does not indicate an active BWP change for the serving cell), the wireless device, by implementing existing technologies, may have difficulties in determining an application delay of the K0min / K2min since different PDSCHs / PUSCHs may be associated with different slot offset values, compared with a single slot offset value associated with single PDSCH / PUSCH in legacy scenario. Different from legacy scenario where a single slot offset value is associated with single PDSCH / PUSCH, when multiple PDSCHs / PUSCHs scheduled by a DCI, the wireless device, by implementing existing technologies, may have difficulties in determining which one of the multiple PDSCHs / PUSCHs is used to determine the application delay. Existing technologies may causeDocket No.: 24-1237PCT misalignment between the base station and the wireless device regarding the application delay of the K0min / K2min. There is a need to ensure alignment between the base station and the wireless device regarding a timing for application of scheduling offset restriction when multiple PDSCHs / PUSCHs are scheduled by a DCI.

[0346] Taking DCI format 1_3 / 0_3 (indicating Type 2 multi-cell scheduling as shown in FIG.32) as an example, when receiving a DCI (e.g., DCI format 0_3 / 1_3) indicating Type 2 multi-cell scheduling on multiple serving cells, a TDRA field of the DCI may indicate a plurality of TDRA configurations, each TDRA configuration corresponding to a respective BWP of each cell of the multiple cells and indicating an entry of a TDRA table configured for multiple PDSCHs / PUSCHs scheduling on the BWP of the corresponding cell. Each entry of the TDRA table may indicate a plurality of slot offsets for the multiple PDSCHs / PUSCHs on the BWP as shown in FIG.29. When The DCI also indicates an applicable K0min / K2min (where the DCI indicates or does not indicate an active BWP change for the multiple cells), the wireless device, by implementing existing technologies, may have difficulties in determining an application delay of the K0min / K2minbecause: 1) different PDSCHs / PUSCHs on the same serving cell may be associated with different slot offset values; 2) different PDSCHs / PUSCHs on different cells may be associated with different slot offset values; 3) there may be BWP change for some cells of the multiple cells and there may be no BWP change for other cells of the multiple cells; and / or 4) different cells may be associated with different SCS values. Existing technologies may cause misalignment between the base station and the wireless device regarding the application delay of the K0min / K2min. There is a need to ensure alignment between the base station and the wireless device regarding a timing for application of scheduling offset restriction when Type 2 multi-cell scheduling is configured.

[0347] In existing technologies, a wireless device performs A-CSI reporting using PUSCH on a serving cell upon successful decoding of a DCI format 0_1 or DCI format 0_2 which triggers an aperiodic CSI trigger state. The wireless device performs A-CSI reporting using PUSCH on the serving cell with the smallest serving cell index scheduled by DCI format 0_3 which triggers an aperiodic CSI trigger state.

[0348] In existing technologies, when a DCI format 0_1 schedules two PUSCH allocations, the aperiodic CSI report is carried on the second scheduled PUSCH. When a DCI format 0_1 schedules more than two PUSCH allocations, the aperiodic CSI report is carried on the penultimate scheduled PUSCH.

[0349] However, existing technologies for A-CSI report may not work for DCI format 0_3 indicating Type 2 multi-cell scheduling. When DCI format 0_3 indicates Type 2 multi-cell scheduling, each co-scheduled cell may be associated with more than one PUSCH. In this case, if the DCI format 0_3 comprises A-CSI request field triggering A-CSI trigger state, the wireless device, based on existing technologies, may have difficulties in determining which PUSCH of which cell, among multiple PUSCHs of multiple cells, is used for the A-CSI report. Existing technologies may cause misalignment between the base station and the wirelessDocket No.: 24-1237PCT device regarding the A-CSI report. Existing technologies may increase reception error of the A-CSI report and / or data reception error at the base station.

[0350] In one or more example embodiments, a wireless device receives, in a first slot, a DCI indicating an active BWP change for a first cell, a plurality of PDSCHs / PUSCHs on the first cell and a scheduling offset restriction. The wireless device switches to a first BWP of the first cell as the active BWP of the first cell. The wireless device applies, for the first BWP, the scheduling offset restriction starting from a second slot determined based on a first slot offset corresponding to the first / earliest PDSCH / PUSCH of the plurality of PDSCHs / PUSCHs of the first cell.

[0351] In one or more example embodiments, a wireless device receives, in a first slot, a DCI indicating an active BWP change for a first cell. The DCI further schedules a plurality of physical shared channels on the first cell. The DCI comprises a time domain resource allocation field indicating a plurality of slot offsets, each corresponding to a respective one of the plurality of physical shared channels. The DCI further comprises a scheduling offset restriction field indicating a value of a scheduling offset restriction. The wireless device switches to a first BWP of the first cell, as the active BWP of the first cell. The wireless device applies, for the first BWP, the scheduling offset restriction starting from a second slot determined based on a first slot offset, of the plurality of slot offsets, corresponding to the earliest physical shared channel of the plurality of physical shared channels.

[0352] In one or more example embodiments, when receiving, in slot n, a DCI scheduling multiple PDSCHs / PUSCHs on a serving cell and comprising a ‘Minimum applicable scheduling offset indicator’ field, if the DCI indicates active DL (UL) BWP change for the serving cell, the wireless device applies the indicated K0min(K2min) value (indicated by the ‘Minimum applicable scheduling offset indicator’ field of the DCI) in a new active DL (UL) BWP of the serving cell from the slot determined by the slot offset value corresponding to the first / earliest PDSCH / PUSCH of the multiple PDSCH / PUSCHs scheduled by the DCI for the serving cell.

[0353] In one or more example embodiments, when receiving, in slot n, a DCI with a DCI format 0_3 / 1_3, scheduling multiple PDSCHs / PUSCHs on serving cells (Type 2 multi-cell scheduling) and comprising a ‘Minimum applicable scheduling offset indicator’ field, if the DCI indicates active DL (UL) BWP change(s) for at least one of the serving cells, the wireless device applies the indicated K0min(K2min) value (by the ‘Minimum applicable scheduling offset indicator’ field) in a new active DL (UL) BWP of the at least one of the serving cells from the slot determined by the slot offset value corresponding to the first / earliest PDSCH / PUSCH of the multiple PDSCH / PUSCHs scheduled by the DCI format for the at least one of the serving cells. The application may be performed per cell of the serving cells if the BWP change is performed on more than one cell of the serving cells.Docket No.: 24-1237PCT

[0354] In one or more example embodiments, when receiving, in slot n, a DCI with a DCI format 0_3 / 1_3, scheduling multiple PDSCHs / PUSCHs on serving cells (e.g., Type 2 multi-cell scheduling) and comprising a ‘Minimum applicable scheduling offset indicator’ field, if the DCI indicates active DL (UL) BWP change(s) for one or more cells of the serving cells, the wireless device applies the indicated K0min (K2min) value (by the ‘Minimum applicable scheduling offset indicator’ field) in a new active DL (UL) BWP of a first cell of the one or more cells from the slot determined by the slot offset value corresponding to the first / earliest PDSCH / PUSCH of the multiple PDSCH / PUSCHs scheduled by the DCI for the first cell. The wireless device determines / selects the first cell with the smallest serving cell index, among the one or more cells, for the application of K0min / K2min. The application may be performed on the serving cell with the smallest serving cell index if the BWP change is performed on more than one cell (comprising the serving cell with the smallest serving cell index) of the serving cells.

[0355] In one or more example embodiments, when receiving, in slot n, a DCI with a DCI format 0_3 / 1_3, scheduling multiple PDSCHs / PUSCHs on serving cells (e.g., Type 2 multi-cell scheduling) and comprising a ‘Minimum applicable scheduling offset indicator’ field, if the DCI does not indicate active DL (UL) BWP change(s) for the serving cells (or any of the serving cells), the wireless device applies the indicated K0min / K2minvalue (indicated by the ‘Minimum applicable scheduling offset indicator’ field) in the scheduling cell (on which the wireless device receives the DCI) from the slot n+X. "Z[^^\

[0356] In one or more example embodiments, R = ^ST ^max ^UN0$O^VWX,O ∙ 22"Z[]^\`^^, _^^ wherei=1,2…., ^aB>)WW, K0minOld,i is the currently appliedcell and is zero, if minimumSchedulingOffsetK0 is not configured for the active DL BWP in the ithscheduled cell. ^aB>)WWis the total number of co-scheduled cells in a serving cell set configured for the DCI format 0_3 / 1_3. Zµis determined by the subcarrier spacing of the active DL BWP in the scheduling cell in slot n, and µPDCCHand µPDSCHi are the sub-carrier spacing configurations for PDCCH of the active DL BWP in the scheduling cell and PDSCH of the active DL BWP in the ithscheduled cell, respectively, in slot n.

[0357] In one or more example embodiments, a wireless device performs A-CSI reporting using PUSCH on serving cell upon successful decoding of a DCI format 0_1 or DCI format 0_2 which triggers an aperiodic CSI trigger state. The wireless device performs A-CSI reporting using PUSCH on the serving cell with the smallest serving cell index scheduled by DCI format 0_3 which triggers an aperiodic CSI trigger state. When two PUSCH allocations are scheduled by DCI format 0_3 for the serving cell with the smallest serving cell index, the aperiodic CSI report is carried on the second scheduled PUSCH. When more than two PUSCH allocations are scheduled by DCI format 0_3 for the serving cell with the smallest serving cell index, the aperiodic CSI report is carried on the penultimate scheduled PUSCH.

[0358] FIG.35 shows an example embodiment of application delay of scheduling offset restriction.Docket No.: 24-1237PCT

[0359] In the example of FIG.35, a wireless device may receive from a base station in a first slot (e.g., T0), a DCI scheduling multiple physical shared channels on a serving cell.

[0360] In an example, the multiple physical shared channels may comprise PDSCH1 / PUSCH1, PDSCH2 / PUSCH2, PDSCH3 / PUSCH3. Each of the multiple physical shared channels starts at a respective slot offset after the first slot, e.g., PDSCH1 / PUSCH1 starts at T1, PDSCH2 / PUSCH2 starts at T2, PDSCH3 / PUSCH3 starts at T3, etc.

[0361] In an example, the DCI comprises a TDRA field that indicates 1stslot offset between T1 and T0, 2ndslot offset between T2 and T0, 3rdslot offset between T3 and T0, etc. The TDRA field may be implemented based on examples of FIG.29, FIG.31 and / or FIG.32.

[0362] In an example, the DCI comprises a scheduling offset restriction indicator indicating a value of scheduling offset restriction. The scheduling offset restriction indicator may be a 'Minimum applicable scheduling offset indicator' field implemented based on examples of FIG.33A and / or FIG.33B. The scheduling offset restriction indicator may indicate an applicable K0min / K2min.

[0363] In an example, the DCI may indicate an active BWP change / switching (from an old / first BWP to a new / second BWP as the active BWP) for the serving cell. The active BWP change / switching may be implemented based on examples of FIG.22.

[0364] In the example of FIG.35, based on receiving the DCI at T0, the wireless device applies, for the serving cell (or the new BWP of the serving cell), the scheduling offset restriction (K0min / K2min) starting from a second slot determined based on a first slot offset corresponding to the earliest physical shared channel of the first plurality of physical shared channels of the serving cell. In the example of FIG.35, the earliest physical shared channel may be PDSCH1 / PUSCH1 at T1. The wireless device may start to apply the indicated K0min / K2min from T1 (the beginning of the slot T1) on the serving cell.

[0365] In an example embodiment, applying the K0min / K2min for the serving cell (or the new BWP of the serving cell) comprises the wireless device not being expected to be scheduled with a DCI in a first downlink slot to receive / transmit in a second downlink / uplink slot a physical shared channel (of the serving cell) scheduled by the DCI, wherein a time gap between the first downlink slot and the second downlink / uplink slot is smaller than the value of the scheduling offset restriction.

[0366] In an example embodiment, applying the K0min / K2minfor the serving cell (or the new BWP of the serving cell) comprises the wireless device being expected to be scheduled with a DCI in a first downlink slot to receive in a second downlink slot a physical shared channel (of the serving cell) scheduled by the DCI, wherein a time gap between the first downlink slot and the second downlink slot is equal to or greater than the value of the scheduling offset restriction.

[0367] In an example, when the physical shared channel is a PDSCH and when the wireless device applies the scheduling offset restriction on a serving cell, the wireless device may expect that the time gapDocket No.: 24-1237PCT between a first downlink slot on which a DCI is received and a second downlink slot of the serving cell on which a PDSCH scheduled by the DCI is equal to or greater than the value of K0min. In this case, the wireless device, based on the application of the scheduling offset restrictions, may avoid (or stop) buffering PDSCH symbols (or for possible PDSCH decoding) on / for the serving cell when receiving the DCI and before a slot determined by K0min, therefore reducing power consumption of the wireless device.

[0368] In an example, when the physical shared channel is a PUSCH and when the wireless device applies the scheduling offset restriction on a serving cell, the wireless device may expect that the time gap between a first downlink slot on which a DCI is received and a second uplink slot of the serving cell on which a PUSCH scheduled by the DCI is equal to or greater than the value of K2min. In this case, the wireless device, based on the application of the scheduling offset restrictions, may avoid (or stop) preparing PUSCH symbols (or for possible PUSCH transmission) on / for the serving cell when receiving the DCI and before a slot determined by K2min, therefore reducing power consumption of the wireless device.

[0369] In an example, the 'Minimum applicable scheduling offset indicator' field of the DCI may indicate an applicable value of K0min / K2minfrom a plurality of values of K0min / K2minconfigured by RRC messages. The plurality of values of K0min / K2min may be implemented based on examples of FIG.27.

[0370] In an example, the 'Minimum applicable scheduling offset indicator' field of the DCI may indicate a change of both K0minand K2min, a change of K0minonly, or a change of K2minonly.

[0371] In an example, the DCI may be associated with a DCI format comprising at least one of: DCI format 0_1, DCI format 0_3, DCI format 1_1 and DCI format 1_3.

[0372] By implementing examples of FIG.35, when both BWP change and scheduling offset restriction are indicated by a DCI scheduling multiple PDSCHs / PUSCHs on a serving cell, a wireless device and a base station determine that the indicated scheduling offset restriction is applied from a slot determined based on the first / earliest PDSCH / PUSCH of the multiple PDSCHs / PUSCHs of the serving cell. Example embodiments may align the wireless device and the base station regarding when to apply the scheduling offset restriction (or the application delay of the scheduling offset restriction), therefore reducing power consumption of the wireless device for PDCCH monitoring and / or reducing possibilities of miss-detecting a DCI when scheduling offset restriction is applied, since the wireless device may implement different PDCCH monitoring and / or PDSCH buffering / PUSCH preparing strategies / operations / configurations before the application of the scheduling offset restriction and after the application of the scheduling offset restriction.

[0373] In an example embodiment, when the DCI does not indicate BWP change on the serving cell, the wireless device applies K0min / K2min from a slot determined by n+X. X may be implemented based on examples of FIG.33B and / or FIG.34.Docket No.: 24-1237PCT

[0374] Example embodiments of FIG.35 may be extended to Type 2 multi-cell scheduling for further reducing power consumption of the wireless device when carrier aggregation is configured for the wireless device.

[0375] FIG.36 illustrates an example as per an aspect of an embodiment of the present disclosure, e.g., based on examples of FIG.35.

[0376] In the example of FIG.36, a wireless device may receive from a base station in a first slot (e.g., T0), a DCI scheduling multiple physical shared channels on multiple cells.

[0377] In an example, the DCI may be DCI format 0_3 for scheduling multiple PUSCHs on multiple cells.

[0378] In an example, the DCI may be DCI format 1_3 for scheduling multiple PDSCHs on multiple cells.

[0379] In an example, the multiple cells may comprise CC 1, CC 2, CC 3, etc.

[0380] In an example, the DCI may indicate Type 2 multi-cell scheduling on the multiple cells.

[0381] For Type 2 multi-cell scheduling on the multiple cells, each cell may be scheduled with one or more PDSCHs / PUSCHs, e.g., CC 1 scheduled with single PDSCH / PUSCH, CC 2 scheduled with two PDSCHs / PUSCHs (e.g., PDSCH1 / PUSCH1, PDSCH2 / PUSCH2), CC 3 scheduled with three PDSCHs (e.g., PDSCH1 / PUSCH1, PDSCH2 / PUSCH2, PDSCH3 / PUSCH3), etc.

[0382] In an example, CC 1 is associated with a first SCS (e.g., 30KHz), CC 2 is associated with a second SCS (e.g., 15KHz), CC 3 is associated with a third SCS (e.g., 120KHz), etc. Note that the SCS value for each CC may be same or may be different. The specific values of SCS in FIG.36 are for illustrative purposes.

[0383] In an example, a TDRA field of the DCI may indicate, for each cell, one or more slot offset values, corresponding to the one or more PDSCHs / PUSCHs of the respective cell.

[0384] In an example embodiment, the wireless device receives from the base station one or more (RRC) messages comprising one or more first parameters indicating whether the DCI configured on a serving cell (e.g., CC 1) is used to indicate / perform Type 1 multi-cell scheduling or Type 2 multi-cell scheduling.

[0385] In an example embodiment, the one or more RRC messages comprise second parameters of the one or more co-scheduled cells (e.g., CC 1, CC 2, CC 3, etc.).

[0386] In an example, the second parameters of CC 1 comprise a first PDSCH / PUSCH time domain allocation list for single-PDSCH / PUSCH scheduling for CC 1 and / or a second PDSCH / PUSCH time domain allocation list for multiple-PDSCH / PUSCH scheduling for CC 1. The second parameters of CC 2 comprise a first PDSCH / PUSCH time domain allocation list for single-PDSCH / PUSCH scheduling for CC 2 and / or a second PDSCH / PUSCH time domain allocation list for multiple-PDSCH / PUSCH scheduling for CC 2, etc.

[0387] In an example embodiment, the wireless device receives the DCI comprising a TDRA field. The TDRA field comprises a plurality of TDRA indexes comprising a first TDRA index associated with CC 1, a second TDRA index associated with CC 2, a third TDRA index associated with CC 3, etc.Docket No.: 24-1237PCT

[0388] In an example, the first TDRA index, based on the one or more first parameters, indicates an entry of the first PDSCH / PUSCH TDRA list of CC 1 or an entry of the second PDSCH / PUSCH time domain allocation list of CC 1.

[0389] In an example, the second TDRA index, based on the one or more first parameters, indicates an entry of the first PDSCH / PUSCH TDRA list of CC 2 or an entry of the second PDSCH / PUSCH time domain allocation list associated with CC 2. The third TDRA index, based on the one or more first parameters, indicates an entry of the first PDSCH / PUSCH TDRA list of CC 3 or an entry of the second PDSCH / PUSCH time domain allocation list associated with CC 3, etc.

[0390] In an example, for a serving cell (e.g., CC 1, CC 2, CC 3, etc.), each entry of the first PUSCH time domain allocation list for single-PDSCH / PUSCH scheduling comprises at least one of: a K2 value indicating a slot offset between the PUSCH and the DCI, a PUSCH mapping indication and a start symbol and length indicator.

[0391] In an example, for a serving cell (e.g., CC 1, CC 2, CC 3, etc.), each entry of the first PDSCH time domain allocation list for single-PDSCH scheduling comprises at least one of: a K0 value indicating a slot offset between the PDSCH and the DCI, a PDSCH mapping indication and a start symbol and length indicator.

[0392] In an example, for a serving cell (e.g., CC 1, CC 2, CC 3, etc.), each entry of the second PUSCH time domain allocation list for multi-PUSCH scheduling comprises a plurality of PUSCH TDRA configurations, each PUSCH TDRA configuration corresponding to a respective PUSCH of multiple PUSCHs, wherein each PUSCH TDRA configuration is associated with at least one of: a K2 value indicating a slot offset between the DCI and the corresponding PUSCH, a PUSCH mapping indication and a start symbol and length indicator.

[0393] In an example, for a serving cell (e.g., CC 1, CC 2, CC 3, etc.), each entry of the second PDSCH time domain allocation list for multi- PDSCH scheduling comprises a plurality of PDSCH TDRA configurations, each PDSCH TDRA configuration corresponding to a respective PDSCH of multiple PDSCHs, wherein each PDSCH TDRA configuration is associated with at least one of: a K0 value indicating a slot offset between the DCI and the corresponding PDSCH, a PDSCH mapping indication and a start symbol and length indicator.

[0394] In an example embodiment, a Type 1 multi-cell scheduling comprises scheduling, by the DCI, multiple PDSCHs / PUSCHs on multiple cells (e.g., CC 1, CC 2, CC 3, etc.) with one PDSCH / PUSCH per cell.

[0395] In an example embodiment, a Type 2 multi-cell scheduling comprises scheduling, by the DCI, multiple PDSCHs / PUSCHs on multiple cells with at least one cell scheduled with at least twoDocket No.: 24-1237PCT PDSCHs / PUSCHs (e.g., CC 2 scheduled with 2 PDSCHs / PUSCHs, CC 3 scheduled with 3 PDSCHs / PUSCHs in the example of FIG.36).

[0396] In the example of FIG.36, PDSCH / PUSCH of CC 1 starts from T1. Slot offset between T1 and T0 may be indicated by the TDRA field for CC 1.

[0397] In the example of FIG.36, PDSCH1 / PUSCH1 of CC 2 starts from T2. Slot offset between T2 and T0 may be indicated by the TDRA field for CC 2.

[0398] In the example of FIG.36, PDSCH1 / PUSCH1 of CC 3 starts from T3. Slot offset between T3 and T0 may be indicated by the TDRA field for CC 3.

[0399] In the example of FIG.36, the DCI comprises a scheduling offset restriction indicator indicating a value of scheduling offset restriction. The scheduling offset restriction indicator may be a 'Minimum applicable scheduling offset indicator' field implemented based on examples of FIG.33A and / or FIG.33B. The scheduling offset restriction indicator may indicate an applicable K0min / K2min. The 'Minimum applicable scheduling offset indicator' field may be comprised in the DCI format based on RRC parameters (e.g., minimumScehdulingOffsetK0DCI-1-3-r18, minimumScehdulingOffsetK0DCI-0-3-r18) according to examples of FIG.24.

[0400] In an example, the DCI may indicate an active BWP change / switching (from an old / first BWP to a new / second BWP as the active BWP) for one or more cells, e.g., based on examples of FIG.30. The active BWP change / switching may be implemented based on examples of FIG.22.

[0401] In an example, the DCI may indicate an active BWP change / switching for some cells and may not indicate active BWP change / switching for other cells.

[0402] In an example, BWP indicator field of the DCI may be set to “01” indicating 2ndconfigured BWP is the new active BWP.

[0403] In an example, if the current (before receiving the DCI) active BWP of CC 1 is the 1stconfigured BWP for CC 1 in serving cell configuration parameters of CC 1, in response to receiving the DCI, the wireless device changes active BWP for CC 1 from the 1stconfigured BWP of CC 1 to the 2ndconfigured BWP of CC 1.

[0404] In an example, if the current active BWP of CC 2 is the 1stconfigured BWP for CC 2 in serving cell configuration parameters of CC 2, in response to receiving the DCI, the wireless device changes active BWP of CC 2 from the 1stconfigured BWP of CC 2 to the 2ndconfigured BWP of CC 2.

[0405] In an example, if the current active BWP of CC 3 is the 3rdconfigured BWP for CC 3 in serving cell configuration parameters of CC 3, in response to receiving the DCI, the wireless device changes active BWP of CC 2 from the 3rdconfigured BWP of CC 3 to the 2ndconfigured BWP of CC 3.Docket No.: 24-1237PCT

[0406] The examples described above are for illustration purposes. When the wireless device receives the DCI, the wireless device may or may not change active BWP for one or more serving cells, e.g., based on current active BWPs of the one or more serving cells and the BWP indicator field of the DCI.

[0407] In the example of FIG.36, based on receiving the DCI at T0, the wireless device applies, for CC 1 (or the new BWP of CC 1 if the BWP changes for CC 1), the scheduling offset restriction (K0min / K2min) starting from a slot determined based on a slot offset corresponding to the PDSCH / PUSCH of CC 1. The wireless device may start to apply the indicated K0min / K2min(configured for the new BWP of CC 1) from T1 (the beginning of the slot T1) for CC 1.

[0408] In the example of FIG.36, based on receiving the DCI at T0, the wireless device applies, for CC 2 (or the new BWP of CC 2 if the BWP changes for CC 2), the scheduling offset restriction (K0min / K2min) starting from a slot determined based on a slot offset corresponding to the first / earliest PDSCH / PUSCH (which is PDSCH1 / PUSCH1 in the example of FIG.36) of CC 2. The wireless device may start to apply the indicated K0min / K2min (configured for the new BWP of CC 2) from T2 (the beginning of the slot T2) for CC 2.

[0409] In the example of FIG.36, based on receiving the DCI at T0, the wireless device applies, for CC 3 (or the new BWP of CC 3 if the BWP changes for CC 3), the scheduling offset restriction (K0min / K2min) starting from a slot determined based on a slot offset corresponding to the first / earliest PDSCH / PUSCH (which is PDSCH1 / PUSCH1 in the example of FIG.36) of CC 3. The wireless device may start to apply the indicated K0min / K2min from T3 (the beginning of the slot T3) for CC 3.

[0410] In an example, the 'Minimum applicable scheduling offset indicator' field of the DCI may indicate, for each cell of the multiple cells, an applicable value of K0min / K2min from a plurality of values of K0min / K2min configured for a corresponding cell by RRC messages. The plurality of values of K0min / K2minconfigured for each cell may be implemented based on examples of FIG.27.

[0411] In an example, the 'Minimum applicable scheduling offset indicator' field of the DCI may indicate a change of both K0minand K2min, a change of K0minonly, or a change of K2minonly.

[0412] In an example, the DCI may be associated with a DCI format comprising at least one of: DCI format 0_3 and DCI format 1_3.

[0413] In an example, if the DCI does not indicate an active BWP change for CC 2, the wireless device may not apply the scheduling offset restriction (and / or change / update) on CC 2 upon receiving the DCI.

[0414] In an example, if the DCI does not indicate an active BWP change for CC 3, the wireless device may not apply the changed scheduling offset restriction (and / or change / update) on CC 3 upon receiving the DCI.

[0415] In an example, if the DCI does not indicate active BWP change for any co-scheduled cells (e.g., CC 2 and CC 3 in the example of FIG.36), the wireless device applies the K0min / K2minon the schedulingDocket No.: 24-1237PCT cell (which is CC 1 in the example of FIG.36) from a slot determined by T0+X. X may be implemented based on examples of FIG.33B and / or FIG.34.

[0416] In an example embodiment, the DCI received on CC 1 may not indicate PDSCHs / PUSCHs scheduling for CC 1. In this case, the actions described above with respect to CC 1 may be omitted. If the DCI does not indicate active BWP change for any co-scheduled cells (e.g., CC 2 and CC 3 in the example of FIG.36), the wireless device applies the K0min / K2min on the scheduling cell (which is CC 1 in the example of FIG.36) from a slot determined by n+X. X may be implemented based on examples of FIG.33B and / or FIG.34.

[0417] Example embodiments of FIG.36 may be further improved for reducing implementation complexity for a wireless device. Instead of performing / applying scheduling offset restriction per cell when receiving the DCI indicating Type 2 multi-cell scheduling, the wireless device may perform / apply the scheduling offset restrict on a reference cell of the multiple cells (e.g., CC 1, CC 2, CC 3, etc.).

[0418] In an example embodiment, the reference cell may be a serving cell with the smallest serving cell index among the multiple cells. When the DCI (e.g., the DCI format 0_3 / 1_3 as shown in FIG.36) indicates an active BWP change / switching for the reference cell, the wireless device applies the scheduling offset restriction from a slot determined based on the first slot offset value corresponding to the first / earliest PDSCH / PUSCH of the multiple PDSCHs / PUSCHs scheduling on the reference cell. When the DCI does not indicate an active BWP change / switching for the reference cell, the wireless device applies the scheduling offset restriction from a slot determined based on X (as shown in FIG.33B) on the scheduling cell (CC 0). In an example, the reference cell may or may not be the scheduling cell based on whether the scheduling cell is configured with the smallest serving cell index.

[0419] In an example embodiment, the determination of the value X implemented above and according to the example of FIG.33B and / or FIG.34 may be further improved for reducing power consumption of the wireless device or reducing implementation complexity by taking into account different co-scheduled cells being associated with different SCSs and different K0min / K2min.0 2 ] 2"Z[^^\[ 4 0 In one or more example embodiments, R = ^ST ^max ^UN0$O^VWX,O ∙ 2"Z[]^\`^^, _^^ wherei=1,2…., ^aB>)WW. K0minOld,i is the currently appliedcell and is zero, if minimumSchedulingOffsetK0 is not configured for the active DL BWP in the ithscheduled cell. ^aB>)WWis the total number of co-scheduled cells in a serving cell set configured for the DCI format 0_3 / 1_3, e.g., based on examples of FIG.24. Zµ is determined by the SCS value of the active DL BWP in the scheduling cell in slot n according to FIG.34. µPDCCH is the SCS configuration for PDCCH of the active DL BWP in the scheduling cell, in slot n. µPDSCHiis the SCS configuration of PDSCH of the active DL BWP in the ithscheduled cell, in slot n.Docket No.: 24-1237PCT

[0421] FIG.37A, FIG.37B, FIG.37C and FIG.37D show examples of A-CSI report transmission on PUSCH.

[0422] In the example of FIG.37A, in response to receiving a DCI format 0_1 (or DCI format 0_2) scheduling a PUSCH transmission of a serving cell and comprising a CSI request field trigging A-CSI trigger state, a wireless device performs A-CSI reporting using the PUSCH on the serving cell. The wireless device transmits the A-CSI report multiplexed with a TB on the PUSCH. In an example, the A-CSI report multiplexed the TB may be based on puncturing some symbols of the PUSCH (for the transmission of the A-CSI report) or rate-matching of the TB, e.g., based on indication of the base station.

[0423] In an example, the CSI request field may indicate one of a plurality of A-CSI trigger states (e.g., CSI-AperiodicTriggerStateList) configured by RRC for A-CSI reporting, e.g., based on examples of FIG.24.

[0424] In the example of FIG.37B, in response to receiving a DCI format 0_1 scheduling two PUSCH transmissions of a serving cell and comprising a CSI request field trigging A-CSI trigger state, the wireless device transmits the A-CSI report multiplexed with a TB on the second scheduled PUSCH. The A-CSI report is not transmitted on the first scheduled PUSCH. In an example, the A-CSI report multiplexed the TB may be based on puncturing some symbols or rate-matching, e.g., based on indication of the base station.

[0425] In the example of FIG.37C, in response to receiving a DCI format 0_1 scheduling N (N>2) PUSCH transmissions of a serving cell and comprising a CSI request field trigging A-CSI trigger state, the wireless device transmits the A-CSI report multiplexed with a TB on the penultimate scheduled PUSCH (e.g., the second-last PUSCH, (N-1)thPUSCH as shown in FIG 37B). The A-CSI report is not transmitted on other scheduled PUSCHs. In an example, the A-CSI report multiplexed the TB may be based on puncturing some symbols or rate-matching, e.g., based on indication of the base station.

[0426] In the example of FIG.37D, in response to receiving a DCI format 0_3 scheduling multiple PUSCHs on multiple cells (e.g., CC 1, CC 2, CC 3, etc.) with one PUSCH per cell and comprising a CSI request field trigging A-CSI trigger state, the wireless device transmits the A-CSI report multiplexed with a TB on PUSCH of a serving cell with the smallest serving cell index (e.g., CC 1 which is configured with the smallest serving cell index among the multiple cells). The A-CSI report is not transmitted on PUSCHs of other cells. In an example, the A-CSI report multiplexed the TB may be based on puncturing some symbols or rate-matching, e.g., based on indication of the base station.

[0427] However, existing technologies for A-CSI report as shown in FIG.37A, FIG.37B, FIG.37C and / or FIG.37D may not work for DCI format 0_3 indicating Type 2 multi-cell scheduling. When DCI format 0_3 indicates Type 2 multi-cell scheduling, each co-scheduled cell may be associated with more than one PUSCH. In this case, if the DCI format 0_3 comprises A-CSI request field triggering A-CSI trigger state, the wireless device, based on existing technologies (defined for DCI format 0_1 / 0_2 / 0_3), may have difficulties in determining which PUSCH of which cell, among multiple PUSCHs of multiple cells, is used for the A-CSIDocket No.: 24-1237PCT report. Existing technologies may cause misalignment between the base station and the wireless device regarding the A-CSI report. Existing technologies may increase reception error of the A-CSI report and / or data reception error at the base station.

[0428] FIG.38 illustrates an example as per an aspect of an embodiment of the present disclosure.

[0429] In the example of FIG.38, a wireless device may receive from a base station a DCI format 0_3 comprising A-CSI request field triggering an A-CSI trigger state.

[0430] In the example of FIG.38, the wireless device determines whether the DCI format 0_3 indicates Type 2 multi-cell scheduling. The wireless device may determine whether the DCI format 0_3 indicates Type 2 multi-cell scheduling based on configuration parameters of RRC messages received from the base station according to examples described above with respect to FIG.36 and / or other aspects of this specification if applicable.

[0431] In the example of FIG.38, the wireless device determines that the DCI format 0_3 indicates Type 1 multi-cell scheduling. In response to determining that the DCI format 0_3 indicates Type 1 multi-cell scheduling, the wireless device transmits A-CSI report via PUSCH of a cell, wherein the PUSCH and the cell are determined based on legacy procedure(s) defined for DCI format 0_3, e.g., based on examples of FIG.37D.

[0432] In the example of FIG.38, the wireless device determines that the DCI format 0_3 indicates Type 2 multi-cell scheduling. When the DCI format 0_3 indicates Type 2 multi-cell scheduling, different cells may be scheduled with one or more PUSCHs (e.g., as shown in FIG.36).

[0433] In an example, the wireless device may determine a serving cell with the smallest serving cell index (e.g., 1stcell as shown in FIG.38) among the multiple cells.

[0434] In the example of FIG.38, in response to the DCI format 0_3 indicating a single PUSCH on 1stcell, the wireless device transmits an A-CSI report via the single PUSCH of 1stcell (where the A-CSI report is multiplexed with a TB via the PUSCH of 1stcell), by implementing existing technologies defined for DCI format 0_1 / 0_2 scheduling single PUSCH as shown in FIG.37A.

[0435] In the example of FIG.38, in response to the DCI format 0_3 indicating two PUSCHs on 1stcell, the wireless device transmits an A-CSI report via the second scheduled PUSCH of 1stcell (where the A-CSI report is multiplexed with a TB via the second scheduled PUSCH of 1stcell), by implementing existing technologies defined for DCI format 0_1 scheduling two PUSCHs as shown in FIG.37B. In an example, the second scheduled PUSCH may have less data payload than the first scheduled PUSCH, which may allow the wireless device to multiplex A-CSI report on the second scheduled PUSCH.

[0436] In the example of FIG.38, in response to the DCI format 0_3 indicating N (N>2) PUSCHs on 1stcell, the wireless device transmits an A-CSI report via the penultimate scheduled PUSCH of 1stcell (where the A-CSI report is multiplexed with a TB via the penultimate scheduled PUSCH of 1stcell), byDocket No.: 24-1237PCT implementing existing technologies defined for DCI format 0_1 scheduling two PUSCHs as shown in FIG. 37C.

[0437] In an example embodiment, the wireless device determines a number of PUSCHs of 1stcell scheduled by the DCI format 0_3 based on examples of FIG.36. The wireless device may determine the number as a number of (valid) TDRA configurations (or a number of columns as shown in FIG.29) indicated by an entry of TDRA table / list associated with 1stcell (or an active BWP of 1stcell).

[0438] FIG.39 shows an example embodiment of A-CSI reporting based on examples of FIG.38.

[0439] In an example, a wireless device may be configured with multiple cells by the base station in one or more RRC messages. In the example of FIG.39, CC 1 is configured with a serving cell index#1 and SCS 1, CC 2 is configured with a serving cell index#2 and SCS 2, CC 3 is configured with a serving cell index#3 and SCS 3, etc.

[0440] In an example, the wireless device may receive a DCI format 0_3 indicating Type 2 multi-cell multi- PUSCH scheduling on the multiple cells, e.g., based on examples of FIG.32. The DCI format 0_3 may further indicate A-CSI report.

[0441] In the example of FIG.39, the wireless device may determine CC 3 is configured with the smallest serving cell index among the multiple cells based on the serving cell index#3 being the smallest one among serving cell index#1, serving cell index#2, serving cell index#3, etc.

[0442] In the example of FIG.39, in response to the DCI format indicating a single PUSCH transmission on CC 3, the wireless device transmits the A-CSI report via PUSCH 1 of CC 3.

[0443] In the example of FIG.39, in response to the DCI format indicating two PUSCH transmissions on CC 3, the wireless device transmits the A-CSI report via PUSCH 2 of CC 3.

[0444] In the example of FIG.39, in response to the DCI format indicating more than two PUSCH transmissions on CC 3, the wireless device transmits the A-CSI report via the penultimate scheduled PUSCH (which is the (N-1)thPUSCH if N PUSCHs are scheduled on CC 3) of CC 3.

[0445] In an example embodiment, the wireless device determines a number of PUSCHs of CC 3 scheduled by the DCI format 0_3 based on examples of FIG.36. The wireless device may determine the number as a number of (valid) TDRA configurations (or a number of columns as shown in FIG.29) indicated by an entry of TDRA table / list associated with CC 3 (or an active BWP of CC 3).

[0446] Based on examples of FIG.38 and / or FIG.39, a wireless device and a base station may be aligned on which PUSCH of which cell is used for A-CSI report when the A-CSI report is triggered by DCI format indicating Type 2 multi-cell scheduling. Example embodiments may reduce PUSCH and / or A-CSI report reception error rate and / or reduce power consumption of the wireless device (for possible retransmission of PUSCH and / or A-CSI report).Docket No.: 24-1237PCT

[0447] Examples of FIG.38 and / or FIG.39 may require the wireless device to select PUSCH based on the total number of scheduled PUSCHs of a serving cell. To further simplify the procedure and / or reduce implementation complexity of the wireless device, the wireless device may always use the first / earliest PUSCH or the last PUSCH of the number of scheduled PUSCHs of the serving cell for the A-CSI reporting.

[0448] The one or more example embodiments of FIG.35, FIG.36, FIG.38 and / or FIG.39 may be further combined to improve power consumption of the wireless device or reduce implementation complexity of the wireless device, wherein upon receiving DCI format indicating scheduling offset restriction and A-CSI report and Type 2 multi-cell scheduling, the wireless device may determine an application delay of the scheduling offset restriction based on example of FIG.35 and / or FIG.36 and / or determine a PUSCH (and / or a cell) for the A-CSI report based on examples of FIG.38 and / or FIG.39.

[0449] In one or more example embodiments, when a DCI with a DCI format 0_1 / 0_3 / 1_1 / 1_3, scheduling multiple PDSCHs / PUSCHs on one or more serving cells and comprising a ‘Minimum applicable scheduling offset indicator’ field, received by a wireless device in slot n also indicates active DL (UL) BWP change(s) for at least one of the one or more serving cells, the indicated K0min(K2min) value (by the ‘Minimum applicable scheduling offset indicator’ field) in a new active DL (UL) BWP of the at least one of the one or more serving cells, if configured, is applied from the slot determined by the slot offset value corresponding to the first / earliest PDSCH / PUSCH of the multiple PDSCH / PUSCHs scheduled by the DCI format for the at least one of one or more serving cells. In an example, the application of the scheduling offset restriction may be performed per cell of the one or more serving cells if the BWP change is performed on more than one cell of the one or more serving cells.

[0450] In an example embodiment, if a DCI, comprising a ‘Minimum applicable scheduling offset indicator’ field, in slot n indicates an active DL (UL) BWP change for a serving cell, the indicated K0min (K2min) value in the new active DL (UL) BWP, if configured, is applied from the slot indicated by the slot offset value of the time domain resource assignment field in the DCI or determined by the slot offset value corresponding to the first / earliest PDSCH / PUSCH of more than one PDSCH / PUSCH scheduled by the DCI format for the serving cell. Otherwise, change of applied minimum scheduling offset restriction indication carried by DCI in slot n, is applied in slot n+X of the scheduling cell.

[0451] In one or more example embodiments, when a DCI with a DCI format 0_1 / 0_3 / 1_1 / 1_3, scheduling multiple PDSCHs / PUSCHs on one or more serving cells and comprising a ‘Minimum applicable scheduling offset indicator’ field, received by a wireless device in slot n does not indicate active DL (UL) BWP change(s) for the one or more serving cells (e.g., including the scheduling cell and the co-scheduled cells), the wireless device applies the change of applied minimum scheduling offset restriction in slot n+X of the scheduling cell.Docket No.: 24-1237PCT

[0452] In one or more example embodiments, when a DCI with a DCI format 0_1 / 0_3 / 1_1 / 1_3, scheduling multiple PDSCHs / PUSCHs on a plurality of serving cells and comprising a ‘Minimum applicable scheduling offset indicator’ field, received by a wireless device in slot n also indicates active DL (UL) BWP change(s) for one or more serving cells of the plurality of serving cells, the indicated K0min (K2min) value (by the ‘Minimum applicable scheduling offset indicator’ field) in a new active DL (UL) BWP, if configured, is applied from the slot determined by the slot offset value corresponding to the first PDSCH / PUSCH of more than one PDSCH / PUSCH of a serving cell with the smallest serving cell index scheduled by the DCI format.

[0453] In one or more example embodiments, when a DCI with a DCI format 0_1 / 0_3 / 1_1 / 1_3, scheduling multiple PDSCHs / PUSCHs on multiple serving cells and comprising a ‘Minimum applicable scheduling offset indicator’ field, received by the wireless device in slot n, does not indicate an active DL (UL) BWP change for one or more serving cells, the wireless device applies the indicated K0min (K2min) value (by the ‘Minimum applicable scheduling offset indicator’ field) in slot n+X of the scheduling cell. "Z[^^\

[0454] In an example embodiment, R = ^ST ^max ^UN ∙ 2 ^, _ . i=1,2…., ^B)0$O^VWX,O 2"Z[]^\`^ ^^ a>WW(which is a total number of co- isthe currently applied K0minvalue of zero, minimumSchedulingOffsetK0 is not configured for the active DL BWP in the ithscheduled cell. Zµ is determined by the SCS of the active DL BWP in the scheduling cell in slot n. Zµis given in Table 5.3.1-1 of TS 38.214 which is also shown in FIG.34. µPDCCH is the SCS of PDCCH of the active DL BWP of the scheduling cell in slot n. µPDSCHiis the SCS of PDSCH of the active DL BWP of the ithscheduled cell in slot n.

[0455] In one or more example embodiments, a wireless device determines whether a received DCI format 0_3 indicates a Type 1 multi-cell scheduling or Type 2 multi-cell scheduling.

[0456] In an example embodiment, when the wireless device determines that the DCI format 0_3 indicates a Type 1 multi-cell scheduling on multiple cells and also triggers aperiodic CSI trigger state, the wireless device performs aperiodic CSI reporting using PUSCH on the serving cell with the smallest serving cell index among the multiple cells.

[0457] In an example embodiment, when the wireless device determines that the DCI format 0_3 indicates a Type 1 multi-cell scheduling on multiple cells and also triggers an aperiodic CSI trigger state, if the serving cell with the smallest cell index, among the multiple cells, is scheduled with one PUSCH, the aperiodic CSI report is carried on the scheduled PUSCH. If the serving cell with the smallest cell index, among the multiple cells, is scheduled with two PUSCHs, the aperiodic CSI report is carried on the second scheduled PUSCH of the two PUSCHs. If the serving cell with the smallest cell index, among the multiple cells, is scheduled with more than two PUSCHs, the aperiodic CSI report is carried on the penultimate scheduled PUSCH of the more than two PUSCHs.Docket No.: 24-1237PCT

[0458] Based on examples of FIG.35, FIG.36, FIG.37A, FIG.37B, FIG.37C, FIG.37D, FIG.38 and / or FIG.39, one or more example embodiments comprise receiving by a wireless device from a base station in a first slot, a DCI indicating an active BWP change for a first cell. The DCI further indicates a plurality of physical shared channels on the first cell, wherein each of the plurality of physical shared channels starts at a respective slot offset after the first slot. The DCI further indicates a scheduling offset restriction. The wireless device switches to a first BWP of the first cell, as the active BWP of the first cell. The wireless device applies, for the first BWP, the scheduling offset restriction starting from a second slot determined based on a first slot offset corresponding to the earliest physical shared channel of the plurality of physical shared channels.

[0459] Based on examples of FIG.35, FIG.36, FIG.37A, FIG.37B, FIG.37C, FIG.37D, FIG.38 and / or FIG.39, one or more example embodiments comprise receiving by a wireless device from a base station in a first slot, a DCI indicating an active BWP change for a first cell. The DCI further schedules a plurality of physical shared channels on the first cell. The DCI comprises a time domain resource allocation field indicating a plurality of slot offsets, each corresponding to a respective one of the plurality of physical shared channels. The DCI further comprises a scheduling offset restriction field indicating a value of a scheduling offset restriction. The wireless device switches to a first BWP of the first cell, as the active BWP of the first cell. The wireless device applies, for the first BWP, the scheduling offset restriction starting from a second slot determined based on a first slot offset, of the plurality of slot offsets, corresponding to the earliest physical shared channel of the plurality of physical shared channels.

[0460] Based on examples of FIG.35, FIG.36, FIG.37A, FIG.37B, FIG.37C, FIG.37D, FIG.38 and / or FIG.39, one or more example embodiments comprise receiving by a wireless device from a base station in a first slot and via a serving cell, a DCI scheduling a first plurality of physical shared channels on a first cell, wherein each of the first plurality of physical shared channels starts at a respective slot offset after the first slot. The DCI further schedules a second plurality of physical shared channels on a second cell, wherein each of the second plurality of physical shared channels starts at a respective slot offset after the first slot. The DCI further comprises a scheduling offset restriction indicator indicating a value of scheduling offset restriction. The wireless device applies, for the first cell, the scheduling offset restriction starting from a second slot determined based on a first slot offset corresponding to the earliest physical shared channel of the first plurality of physical shared channels of the first cell.

[0461] According to an example embodiment, the wireless device applies, for the second cell, the scheduling offset restriction starting from a third slot indicated by a second slot offset associated with the earliest physical shared channel of the one or more second physical shared channels of the second cell.

[0462] According to an example embodiment, the plurality of physical shared channels comprises a plurality of physical downlink shared channels (PDSCHs).Docket No.: 24-1237PCT

[0463] According to an example embodiment, the plurality of physical shared channels comprises a plurality of physical uplink shared channels (PUSCHs).

[0464] According to an example embodiment, applying the scheduling offset restriction for the first cell comprising the wireless device not being expected to be scheduled with a DCI in a first downlink slot to receive in a second downlink slot a physical shared channel scheduled by the DCI, wherein a time gap between the first downlink slot and the second downlink slot is smaller than the value of the scheduling offset restriction.

[0465] According to an example embodiment, applying the scheduling offset restriction for the first cell comprising the wireless device being expected to be scheduled with a DCI in a first downlink slot to receive in a second downlink slot a physical shared channel scheduled by the DCI, wherein a time gap between the first downlink slot and the second downlink slot is equal to or greater than the value of the scheduling offset restriction.

[0466] According to an example embodiment, the wireless device receives from the base station one or more (RRC) messages comprising one or more first parameters indicating whether the DCI configured on the serving cell is used to indicate / perform Type 1 multi-cell scheduling or Type 2 multi-cell scheduling. The one or more RRC messages comprise second parameters of the first cell. The second parameters indicate a first physical shared channel time domain allocation list for single- physical shared channel scheduling and a second physical shared channel time domain allocation list for multiple- physical shared channel scheduling.

[0467] According to an example embodiment, the wireless device receives the DCI comprising a TDRA field. The TDRA field comprises a plurality of TDRA indexes comprising a first TDRA index associated with the first cell and a second TDRA index associated with the second cell. The first TDRA index, based on the one or more first parameters, indicates an entry of the first physical shared channel time domain allocation list or an entry of the second physical shared channel time domain allocation list.

[0468] According to an example embodiment, the wireless device receives from the base station one or more (RRC) messages comprising one or more first parameters indicating whether a DCI format for the DCI configured on the serving cell is used to indicate / perform Type 2 multi-cell scheduling. The one or more RRC messages comprise second parameters of the first cell. The second parameters indicate a second physical shared channel time domain allocation list for multiple- physical shared channel scheduling.

[0469] According to an example embodiment, the DCI comprises a TDRA field. The TDRA field comprises a plurality of TDRA indexes comprising a first TDRA index associated with the first cell and a second TDRA index associated with the second cell. The first TDRA index, based on the one or more first parameters, indicates an entry of the second physical shared channel time domain allocation list.Docket No.: 24-1237PCT

[0470] According to an example embodiment, the wireless device receives from the base station one or more (RRC) messages indicating a DCI format for the DCI, configured on the serving cell, used for Type 2 multi-cell scheduling. The one or more RRC messages further indicate a physical shared channel time domain allocation list for multiple- physical shared channel scheduling of the first cell.

[0471] According to an example embodiment, the DCI comprises a TDRA field. The TDRA field comprises a plurality of TDRA indexes comprising a first TDRA index associated with the first cell and a second TDRA index associated with the second cell. The first TDRA index indicates an entry of the physical shared channel time domain allocation list of the first cell.

[0472] According to an example embodiment, a Type 1 multi-cell scheduling comprises scheduling, by the DCI, multiple physical shared channels on multiple cells, comprising the first cell and the second cell, with one physical shared channel per cell.

[0473] According to an example embodiment, a Type 2 multi-cell scheduling comprises scheduling, by the DCI, multiple physical shared channels on multiple cells, comprising the first cell and the second cell, with at least one cell scheduled with at least two physical shared channels.

[0474] According to an example embodiment, for the Type 1 multi-cell scheduling, the multiple cells are configured with at least one of: a same carrier type and a SCS value.

[0475] According to an example embodiment, a carrier type comprises whether the cell is deployed in licensed band or in unlicensed band.

[0476] According to an example embodiment, a carrier type comprises a frequency range where the cell is deployed.

[0477] According to an example embodiment, for the Type 2 multi-cell scheduling, the multiple cells comprise at least two cells configured with different carrier types and / or different subcarrier spacing values.

[0478] According to an example embodiment, the multiple cells comprise the serving cell.

[0479] According to an example embodiment, the serving cell is deployed in a first frequency range.

[0480] According to an example embodiment, the first cell and / or the second cell is deployed in a second frequency range.

[0481] According to an example embodiment, the serving cell, the first cell and / or the second cell are configured with different SCS values.

[0482] According to an example embodiment, the wireless device monitors a PDCCH on the serving cell for receiving the DCI format.

[0483] According to an example embodiment, each entry of the first physical shared channel time domain allocation list for single- physical shared channel scheduling comprises at least one of: a k2 value indicating a slot offset between the PUSCH and the DCI, a PUSCH mapping indication and a start symbol and length indicator.Docket No.: 24-1237PCT

[0484] According to an example embodiment, each entry of the first physical shared channel time domain allocation list for single- physical shared channel scheduling comprises at least one of: a k0 value indicating a slot offset between the PDSCH and the DCI, a PDSCH mapping indication and a start symbol and length indicator.

[0485] According to an example embodiment, each entry of the second physical shared channel time domain allocation list for multi-physical shared channel scheduling comprises a plurality of physical shared channel TDRA configurations, each physical shared channel TDRA configuration corresponding to a respective physical shared channel of multiple physical shared channels, wherein each physical shared channel TDRA configuration is associated with at least one of: a k2 value indicating a slot offset between the DCI and the corresponding PUSCH, a PUSCH mapping indication and a start symbol and length indicator.

[0486] According to an example embodiment, each entry of the second physical shared channel time domain allocation list for multi-physical shared channel scheduling comprises a plurality of physical shared channel TDRA configurations, each physical shared channel TDRA configuration corresponding to a respective physical shared channel of multiple physical shared channels, wherein each physical shared channel TDRA configuration is associated with at least one of: a k0 value indicating a slot offset between the DCI and the corresponding PDSCH, a PDSCH mapping indication and a start symbol and length indicator.

[0487] According to an example embodiment, the first physical shared channel time domain allocation list is configured on a first BWP of one or more BWPs of the first cell.

[0488] According to an example embodiment, the second physical shared time domain allocation list is configured on the first BWP of one or more BWPs of the first cell.

[0489] According to an example embodiment, the DCI is received with DCI format 0_1 / 1_1.

[0490] According to an example embodiment, the first DCI format is DCI format 0_3 / 1_3.

[0491] According to an example embodiment, the multiple cells do not comprise the serving cell.

[0492] According to an example embodiment, the wireless device determines whether the DCI format used for the DCI indicates Type 1 multi-cell scheduling or Type 2 multi-cell scheduling based on the one or more RRC messages.

[0493] According to an example embodiment, the wireless device determines an application of the first physical shared channel time domain allocation list based on the DCI format indicating Type 1 multi-cell scheduling.

[0494] According to an example embodiment, the wireless device determines an application of the second physical shared channel time domain list based on the DCI format indicating Type 2 multi-cell scheduling.Docket No.: 24-1237PCT

[0495] According to an example embodiment, the wireless device receives from the base station one or more RRC messages comprising one or more first scheduling offset restriction values for a first BWP of the first cell, wherein the scheduling offset restriction indicator of the DCI indicates one of the one or more scheduling offset restriction values.

[0496] According to an example embodiment, the one or more first scheduling offset values comprise one or more minimum PDSCH scheduling offset values for PDSCH scheduling on the first BWP of the first cell.

[0497] According to an example embodiment, the one or more first scheduling offset values comprise one or more minimum PUSCH scheduling offset values for PUSCH scheduling on the first BWP of the first cell.

[0498] According to an example embodiment, the wireless device applies, on the first BWP of the first cell and starting from the second slot, the scheduling offset restriction with a first value, indicated by the scheduling offset restriction indicator, from the one or more first scheduling offset restriction values corresponding to the first BWP of the first cell.

[0499] According to an example embodiment, the one or more RRC messages comprise one or more second scheduling offset restriction values for a second BWP of the second cell, wherein the scheduling offset restriction indicator of the DCI indicates one of the one or more scheduling offset restriction values.

[0500] According to an example embodiment, the one or more second scheduling offset values comprise one or more minimum PDSCH scheduling offset values for PDSCH scheduling on the second BWP of the second cell.

[0501] According to an example embodiment, the one or more second scheduling offset values comprise one or more minimum PUSCH scheduling offset values for PUSCH scheduling on the second BWP of the second cell.

[0502] According to an example embodiment, the wireless device applies, on the second BWP cell of the second cell and starting from the third slot, the scheduling offset restriction with a first value, indicated by the scheduling offset restriction indicator, from the one or more second scheduling offset restriction values corresponding to the second BWP of the second cell.

[0503] According to an example embodiment, the DCI comprises a BWP indicator field.

[0504] According to an example embodiment, the wireless device switches an active BWP of the first cell to the first BWP of the first cell based on receiving the DCI comprising the BWP indicator field indicating the first BWP of the first cell.

[0505] According to an example embodiment, the wireless device applies the scheduling offset restriction on the first BWP of the first cell after / based on switching an active BWP of the first cell to the first BWP of the first cell or based on the DCI indicating the active BWP change for the first cell.Docket No.: 24-1237PCT

[0506] According to an example embodiment, the wireless device switches an active BWP of the second cell to the second BWP of the second cell based on receiving the DCI comprising the BWP indicator field indicating the second BWP of the second cell.

[0507] According to an example embodiment, the wireless device applies the scheduling offset restriction on the second BWP of the second cell after switching an active BWP of the second cell to the second BWP of the second cell or based on the DCI indicating the active BWP change for the second cell.

[0508] According to an example embodiment, the wireless device transmits to the base station, one or more second RRC messages comprising wireless device’s radio access capability information comprising one or more parameters indicating whether the wireless device supports Type 1 multi-cell scheduling or Type 2 multi-cell scheduling.

[0509] According to an example embodiment, the one or more parameters are per frequency band indicated.

[0510] According to an example embodiment, the one or more parameters are per frequency band combination indicated.

[0511] According to an example embodiment, the one or more parameters are per frequency range indicated.

[0512] According to an example embodiment, the one or more parameters are per frequency range combination indicated.

[0513] According to an example embodiment, a frequency range combination comprises at least one of: FR1+FR 2, FR1+FR2-2, FR2+FR2-2 and FR1+FR2+FR2-2.

[0514] According to an example embodiment, a frequency range combination being set to FR1+FR2 comprises: the scheduling cell being configured on FR1 and one or more scheduled cells being configured on FR2.

[0515] According to an example embodiment, a frequency range combination being set to FR1+FR2+FR2-2 comprises: the scheduling cell being configured on FR1, one or more first scheduled cells being configured on FR2 and one or more second scheduled cells being configured on FR2-2.

[0516] According to an example embodiment, the one or more parameters is per SCS combination indicated.

[0517] According to an example embodiment, a SCS combination comprises at least one of: 15KHz + 30KHz, 15KHz + 60KHz, 15KHz + 120KHz, 15KHz + 480KHz, 15KHz + 960KHz and 15KHz+60KHz+960KHz.

[0518] According to an example embodiment, a SCS combination being set to 15KHz+30KHz comprises: the scheduling cell being configured with 15KHz SCS and one or more scheduled cells being configured with 30KHz SCS.Docket No.: 24-1237PCT

[0519] According to an example embodiment, a SCS combination being set to 15KHz+60KHz+960KHz comprises: the scheduling cell being configured with 15KHz SCS, one or more first scheduled cells being configured with 60KHz SCS and one or more second scheduled cells being configured with 960KHz SCS.

[0520] According to an example embodiment, the one or more parameters indicate whether the wireless device supports Type 2 multi-cell scheduling with the scheduling cell being configured in licensed band and / or one or more scheduled cells being configured in unlicensed band.

[0521] According to an example embodiment, the one or more parameters indicate a (maximum / supported) number of different SCS values configured for multiple cells on which the wireless device supports Type 2 multi-cell scheduling.

[0522] According to an example embodiment, the one or more parameters indicate a (maximum / supported) number of frequency ranges configured for multiple cells on which the wireless device supports Type 2 multi-cell scheduling.

[0523] According to an example embodiment, the one or more parameters indicates whether the wireless device supports Type 1 multi-cell scheduling or Type 2 multi-cell scheduling multiple cells comprising the scheduling cell.

[0524] According to an example embodiment, the one or more parameters indicates whether the wireless device supports Type 1 multi-cell scheduling or Type 2 multi-cell scheduling multiple cells not comprising the scheduling cell.

[0525] According to an example embodiment, the one or more parameters indicates whether the wireless device supports Type 1 multi-cell scheduling or Type 2 multi-cell scheduling multiple cells configured within the same PUCCH group.

[0526] According to an example embodiment, the one or more parameters indicates whether the wireless device supports Type 1 multi-cell scheduling or Type 2 multi-cell scheduling multiple cells configured within the same cell group (e.g., MCG, or SCG).

[0527] According to an example embodiment, the one or more parameters indicates whether the wireless device supports Type 1 multi-cell scheduling or Type 2 multi-cell scheduling multiple cells configured with the same timing advanced group (TAG).

[0528] Based on examples of FIG.35, FIG.36, FIG.37A, FIG.37B, FIG.37C, FIG.37D, FIG.38 and / or FIG.39, one or more example embodiments comprise receiving, by a wireless device and in a first slot, a DCI. The DCI schedules a plurality of physical shared channels on a plurality of cells, wherein each of the plurality of cells is associated with one or more respective physical shared channels. The DCI comprises a scheduling offset restriction indicator indicating a value of scheduling offset restriction. The wireless device applies, for a first cell of the plurality of cells, the scheduling offset restriction starting from a second slotDocket No.: 24-1237PCT determined based on a first slot offset associated with a first physical shared channel of one or more physical shared channels associated with the first cell.

[0529] According to an example embodiment, the first physical shared channel, among the one or more physical shared channels of the first cell, is associated with the smallest slot offset.

[0530] According to an example embodiment, the first physical shared channel is a physical shared channel, among the one or more physical shared channels associated with the first cell, starting first.

[0531] According to an example embodiment, the first physical shared channel is a physical shared channel with the largest slot offset among the one or more physical shared channels associated with the first cell.

[0532] According to an example embodiment, the first physical shared channel is a physical shared channel, among the one or more physical shared channels associated with the first cell, ending last.

[0533] According to an example embodiment, the plurality of physical shared channels comprises a plurality of physical downlink shared channels (PDSCHs).

[0534] According to an example embodiment, the plurality of physical shared channels comprises a plurality of physical uplink shared channels (PUSCHs).

[0535] According to an example embodiment, the first cell is a serving cell, among the plurality of cells with the smallest cell index.

[0536] According to an example embodiment, the first cell is a scheduling cell on which the wireless device receives the downlink control information.

[0537] According to an example embodiment, the time gap between the first slot and the second slot is a number of slots, wherein the number is indicated by the first slot offset.

[0538] According to an example embodiment, the DCI is a DCI format 1_3 or DCI format 0_3.

[0539] Based on examples of FIG.35, FIG.36, FIG.37A, FIG.37B, FIG.37C, FIG.37D, FIG.38 and / or FIG.39, one or more example embodiments comprise receiving, by a wireless device via an active BWP of a scheduling cell, a DCI. The DCI indicates a plurality of physical shared channels on a plurality of cells. The DCI indicates a value of a scheduling offset restriction. The wireless device applying, on the active BWP of the scheduling cell, the scheduling offset restriction starting from a second slot, wherein the second slot is determined as a maximum of: a predefined value for applying the scheduling offset restriction on the active BWP of the scheduling cell and a maximum value. The maximum value is determined based on: a plurality of scheduling offset restriction values with each corresponding to an active BWP of a respective cell of the plurality of cells, a SCS value of a PDCCH of the active BWP of the scheduling cell on which the DCI is received, and a plurality of SCS values, each corresponding to a physical shared channel of the active BWP of a respective cell of the plurality of cells.Docket No.: 24-1237PCT

[0540] Based on examples of FIG.35, FIG.36, FIG.37A, FIG.37B, FIG.37C, FIG.37D, FIG.38 and / or FIG.39, one or more example embodiments comprise receiving, by a wireless device and via a serving cell, in a first slot, a DCI. The DCI schedules one or more PUSCHs on multiple cells. Each of the multiple cells is scheduled with at least one PUSCH. A first cell of the multiple cells is scheduled with at least two PUSCHs. The DCI further comprises a CSI request field triggering an aperiodic CSI trigger state. The wireless device performs aperiodic CSI reporting using a first PUSCH of the at least two PUSCHs of the first cell based on the first cell being associated with the smallest cell index of the multiple cells and based on receiving the DCI.

[0541] According to an example embodiment, the first PUSCH is the earliest PUSCH of the at least two PUSCHs of the first cell.

[0542] According to an example embodiment, the first PUSCH is the last PUSCH of the at least two PUSCHs of the first cell.

[0543] According to an example embodiment, the first PUSCH is the penultimate PUSCH of the at least two PUSCHs of the first cell.

[0544] Based on examples of FIG.35, FIG.36, FIG.37A, FIG.37B, FIG.37C, FIG.37D, FIG.38 and / or FIG.39, one or more example embodiments comprise receiving, by a wireless device and via a serving cell, in a first slot, a DCI. The DCI schedules one or more PUSCHs on multiple cells. Each of the multiple cells is scheduled with at least one PUSCH. A first cell of the multiple cells is scheduled with at least two PUSCHs. The DCI comprises a CSI request field triggering an aperiodic CSI trigger state. The wireless device performs, based on the first cell being associated with the smallest cell index of the multiple cells, aperiodic CSI reporting using: the penultimate PUSCH of the at least two PUSCHs of the first cell in response to the at least two PUSCHs comprising at least three PUSCHs or the second PUSCH of the at least two PUSCHs of the first cell in response to the at least two PUSCHs comprising two PUSCHs.

Claims

Docket No.: 24-1237PCT CLAIMS 1. A method comprising: receiving, by a wireless device and via a first cell, a downlink control information (DCI) format 0_3: indicating scheduling of multiple physical uplink shared channels (PUSCHs) in multiple cells with one or more PUSCHs per cell of the multiple cells, wherein each cell of the multiple cells is associated with a respective serving cell index; and comprising a channel state information (CS) request field triggering an aperiodic CSI trigger state; and performing, based on the aperiodic CSI trigger state, aperiodic CSI reporting using a first PUSCH of a second cell of the multiple cells, wherein: the second cell is determined with a smallest serving cell index among the multiple cells scheduled by the DCI format 0_3; and the first PUSCH is determined as one of: ^ a scheduled PUSCH of the second cell in response to at most one PUSCH being scheduled by the DCI format 0_3 on the second cell; ^ a later scheduled PUSCH in response to two PUSCHs being scheduled by the DCI format 0_3 on the second cell; and ^ a penultimate scheduled PUSCH in response to more than two PUSCHs being scheduled by the DCI format 0_3 on the second cell.

2. A method comprising: receiving, by a wireless device, via a first cell, a downlink control information (DCI) format 0_3: indicating scheduling of multiple physical uplink shared channels (PUSCHs) in multiple cells with one or more PUSCHs per cell of the multiple cells; and comprising a channel state information (CSI) request field; and performing aperiodic CSI reporting using a first PUSCH of a second cell of the multiple cells, wherein: the second cell is with a smallest serving cell index among the multiple cells; and the first PUSCH is determined as: ^ a later scheduled PUSCH in response to two PUSCHs being scheduled by the DCI format 0_3 on the second cell; or ^ a penultimate scheduled PUSCH in response to more than two PUSCHs being scheduled by the DCI format 0_3 on the second cell.

3. The method of claim 1 or 2, further comprising receiving, by the wireless device from a base station, one or more first radio resource control (RRC) messages comprising:Docket No.: 24-1237PCT first configuration parameters of a physical downlink control channel (PDCCH) associated with the DCI format 0_3 of a first bandwidth part (BWP) of the first cell; second configuration parameters of PUSCHs of a second BWP of the second cell; and third configuration parameters of PUSCHs of a third BWP of a third cell.

4. The method of claim 3, wherein the DCI format 0_3, indicating the scheduling of the multiple PUSCHs of the multiple cells, comprises the DCI format 0_3 scheduling: one or more first PUSCHs of the second cell; and one or more second PUSCHs of the third cell.

5. The method of claim 4, wherein: the first cell is associated with a first subcarrier spacing (SCS) value and a first frequency range (FR); the second cell is associated with a second SCS value and a second FR; and the third cell is associated with a third SCS value and a third FR.

6. The method of claim 5, wherein the second SCS value is different from the third SCS value.

7. The method of claim 5 or 6, wherein the second FR is different from the third FR.

8. The method of any one of claims 3 to 7, wherein the second configuration parameters indicate a first PUSCH time domain resource allocation (TDRA) table comprising a first plurality of rows, used for the DCI format 0_3 scheduling the multiple PUSCHs of the multiple cells, associated with the second cell.

9. The method of claim 8, wherein each entry / row of the first plurality of rows of the first PUSCH TDRA table comprises a first plurality of PUSCH TDRA configurations, each PUSCH TDRA configuration corresponding to a respective PUSCH of a first plurality of PUSCHs on the second BWP of the second cell, wherein each PUSCH TDRA configuration is associated with at least one of: a k2 value indicating a slot offset between the DCI format 0_3 and the corresponding PUSCH; a PUSCH mapping indication; and a start symbol and length indicator.

10. The method of claim 9, wherein the wireless device determines, a number of the one or more first PUSCHs scheduled, by the DCI format 0_3, of the second cell, based on a number of valid PUSCH time domain resource allocations comprised in a row of the first PUSCH time domain resource allocation table associated with the second cell, wherein the row is indicated by the DCI format 0_3.

11. The method of any one of claims 8 to 10, wherein the one or more first RRC messages comprise a second PUSCH TDRA table comprising a second plurality of rows, used for a DCI format 0_1 scheduling a second plurality of PUSCHs of a single cell, associated with the second cell, wherein the second PUSCH TDRA table is different from the first PUSCH TDRA table.Docket No.: 24-1237PCT 12. The method of claim 11, wherein each entry / row of the second plurality of rows of the second PUSCH TDRA table comprises a second plurality of PUSCH TDRA configurations, each PUSCH TDRA configuration corresponding to a respective PUSCH of the second plurality of PUSCHs on the second BWP of the second cell, wherein each PUSCH TDRA configuration is associated with at least one of: a k2 value indicating a slot offset between the DCI format 0_1 and the corresponding PUSCH; a PUSCH mapping indication; and a start symbol and length indicator.

13. The method of claim 11 or 12, wherein the wireless device determines the first PUSCH TDRA table is applied for a receptions of the one or more first PUSCHs of the second cell, based on the DCI format 0_3 being received.

14. The method of claim 13, wherein the wireless device determines the second PUSCH TDRA table is not applied for the receptions of the one or more first PUSCHs of the second cell, based on the DCI format 0_3 being received.

15. The method of any one of claims 3 to 14, wherein the third configuration parameters indicate a PUSCH TDRA table for scheduling, by the DCI format 0_3, a second plurality of PUSCHs on the third BWP of the third cell.

16. The method of any one of claims 3 to 15, wherein the first configuration parameters indicate at least one of: a search space associated with the DCI format 0_3; and a control resource set.

17. The method of claim 16, further comprising monitoring, for a reception of the DCI format 0_3 and in response to the first BWP being an active BWP of the first cell, the PDCCH on the first BWP of the first cell according to the first configuration parameters.

18. The method of claim 17, wherein the wireless device receives the DCI format 0_3 based on monitoring the PDCCH on the first BWP of the first cell.

19. The method of claim 18, wherein the DCI format 0_3 comprises a scheduled cell set indicator and a scheduled cells indicator, wherein the scheduled cell set indicator and the scheduled cells indicator indicate: the second cell; and the third cell.

20. The method of claim 18 or 19, wherein the DCI format 0_3 comprises a BWP indicator, or BWP indicator field, indicating: the second BWP of the second cell; and the third BWP of the third cell.Docket No.: 24-1237PCT 21. The method of claim 20, further comprising, based on the BWP indicator, or BWP indicator field: switching to the second BWP of the second cell an active BWP of the second cell; and switching to the third BWP of the third cell as an active BWP of the third cell.

22. The method of any one of claims 18 to 21, wherein the DCI format 0_3 comprises a time domain resource allocation (TDRA) field indicating: time domain resource allocations of the one or more first PUSCHs of the second BWP of the second cell; and time domain resource allocations of the one or more second PUSCHs of the third BWP of the third cell.

23. The method of claim 22, wherein: the TDRA field comprises a plurality of TDRA indexes with each TDRA index corresponding to a respective one of the multiple cells, wherein the plurality of TDRA indexes comprises a first TDRA index associated with the second cell and a second TDRA index associated with the third cell; and the first TDRA index indicates an entry / row of a first PUSCH TDRA table for the second cell.

24. The method of claim 23, further comprising, based on receiving the DCI format 0_3 via the first BWP of the first cell: transmitting the one or more first PUSCHs on the second BWP of the second cell; and transmitting the one or more second PUSCHs on the third BWP of the third cell.

25. The method of claim 24, wherein the wireless device transmits aperiodic CSI report, for the aperiodic CSI reporting, in one of the one or more first PUSCHs indicated for the second cell, on the second BWP of the second cell, wherein the one of the one or more first PUSCHs is the first PUSCH determined as one of: a scheduled PUSCH of the second cell in response to at most one PUSCH being scheduled by the DCI format 0_3 on the second cell; a later scheduled PUSCH in response to two PUSCHs being scheduled by the DCI format 0_3 on the second cell; and a penultimate scheduled PUSCH in response to more than two PUSCHs being scheduled by the DCI format 0_3 on the second cell.

26. The method of any one of claims 3 to 25, further comprising transmitting from the wireless device to a base station, one or more second RRC messages comprising wireless device’s radio access capability information.

27. The method of claim 26, wherein the one or more first RRC messages are based on the one or more second RRC messages.Docket No.: 24-1237PCT 28. The method of claim 26 or 27, wherein the one or more second RRC messages comprise one or more parameters indicating: a first SCS value, a first SCS value and a first SCS value; and a second FR, a second FR and a second FR, for which the wireless device supports a reception of DCI format 0_3, on the first cell, scheduling the multiple PUSCHs of the second cell and a third cell, wherein: the first cell is associated with the first SCS value and the first FR; the second cell is associated with the second SCS value and the second FR; and the third cell is associated with the third SCS value and the third FR.

29. The method of claim 28, wherein: the first cell is associated with a first carrier type; the second cell is associated with a second carrier type; and the third cell is associated with a third carrier type different from the second carrier type.

30. The method of claim 29, wherein a carrier type indicates whether a cell is in licensed band or unlicensed band.

31. The method of claim 29 or 30, wherein a carrier type indicates a FR of a cell.

32. The method of any one of claims 28 to 31, wherein the one or more parameters indicate a frequency band combination for which the wireless device supports the reception of DCI format 0_3, on the first cell, scheduling multiple PUSCHs of the second cell and the third cell.

33. The method of any one of claims 28 to 32, wherein the one or more parameters indicate a maximum number of FR combinations for which the wireless device supports the reception of DCI format 0_3, on the first cell, scheduling multiple PUSCHs of the second cell and the third cell.

34. The method of any one of claims 28 to 33, wherein the one or more parameters indicate a maximum number of SCS value combinations for which the wireless device supports the reception of DCI format 0_3, on the first cell, scheduling multiple PUSCHs of the second cell and the third cell.

35. The method of any one of claims 28 to 34, wherein the one or more parameters indicate one or more carrier type combinations for which the wireless device supports the reception of DCI format 0_3, on the first cell, scheduling multiple PUSCHs of the second cell and the third cell.

36. The method of any one of claims 28 to 35, wherein the one or more parameters indicate a maximum number of cells on which DCI format 0_3 schedules multiple PUSCHs on the cells.

37. The method of any one of claims 28 to 36, wherein the one or more parameters indicate a maximum number of PUSCHs of a plurality of cells for which the wireless device supports the reception of DCI format 0_3, on the first cell, scheduling multiple PUSCHs on the plurality of cells comprising the second cell and the third cell.Docket No.: 24-1237PCT 38. The method of any one of claims 28 to 37, wherein the one or more parameters indicate a maximum number of PUSCHs on the second cell or the third cell for which the wireless device supports the reception of DCI format 0_3, on the first cell, scheduling multiple PUSCHs of the second cell and the third cell.

39. An apparatus comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the apparatus to perform the method of any one of claims 1 to 38.

40. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors of an apparatus, cause the apparatus to perform the method of any one of claims 1 to 38.

Images