Uplink / downlink scheduling under feedback-disabled / enabled hybrid automatic repeat request (HARQ) operations

Abstract

A method can include receiving, by a wireless device, a first downlink control information (DCI) indicating a physical uplink shared channel (PUSCH) transmission in a slot. The PUSCH transmission includes a hybrid automatic repeat request (HARQ) acknowledgement (ACK) information. The method can also include, based on a HARQ process being a feedback-disabled HARQ process, receiving, after the receiving of the first DCI and before the slot, a second DCI scheduling a physical downlink shared channel (PDSCH) associated with the HARQ process. The method can further include transmitting the PUSCH transmission comprising the HARQ-ACK information.

Description

TITLEUplink / Downlink Scheduling under Feedback-disabled / enabled Hybrid Automatic Repeat Request (HARQ) OperationsCROSS-REFERENCE TO RELATED APPLICATION

[0001] This application is related to and claims the benefit and priority of U.S. Provisional Patent Application No. 63 / 626,310, filed January 29, 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 BMPs 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. 11 B 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.

[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. 17 shows several DCI formats.

[0024] FIG. 18A shows an example of a non-terrestrial network (NTN).

[0025] FIG. 18B shows an example of an NTN with a transparent payload.

[0026] FIG. 18C shows an example of assistance information (e.g„ NTN assistance information) for maintenance of UL synchronization ata wireless device in an NTN.

[0027] FIG. 19 shows an example of downlink HARQ operation in a wireless communication system per an aspect of the present disclosure.

[0028] FIG. 20A, FIG. 20B, FIG. 21 A, and FIG. 21 B show examples of multiplexing of HARQ-ACK information in a RUSCH transmission.

[0029] FIG. 22A and FIG. 22B show examples of DRX operation with feedback-enabled HARQ processes in a nonterrestrial network.

[0030] FIG. 23A illustrates an example of DRX operation with a HARQ process with HARQ mode A in a nonterrestrial network.

[0031] FIG. 23B illustrates an example of DRX operation with a HARQ process with HARQ mode B in a nonterrestrial network.

[0032] FIG. 24 shows an example of UL / DL HARQ operation in a non-terrestrial network.

[0033] FIG. 25, FIG. 26, and FIG. 27 illustrate examples of UL / DL HARQ operations and per an aspect of an embodiment of the present disclosure

[0034] FIG. 28 illustrates an example flowchart of HARQ operation as per an aspect of an embodiment of the present disclosure.

[0035] FIG. 29 illustrates an example flowchart of HARQ operation as per an aspect of an embodiment of the present disclosure.

[0036] FIG. 30 illustrates an example flowchart of HARQ operation as per an aspect of an embodiment of the present disclosure.DETAILED DESCRIPTION

[0037] 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 describedexemplary 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.

[0038] 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.

[0039] 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 capabil ity(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 disclosed methods, for example, those wireless devices or base stations may perform based on older releases of LTE or 5G technology.

[0040] 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.

[0041] 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 = {celH , cell2} are: {celH }, {cell2}, and {celH, 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.

[0042] 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 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 that 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.

[0043] In this disclosure, parameters (or equally called, fields, or Information elements: lEs) 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.

[0044] 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.

[0045] 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) ora 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 LabVI E WMathScript. 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, applicationspecific 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.

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

[0047] 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.

[0048] 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.

[0049] 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 maybe a telephone, smartphone, tablet, computer, laptop, sensor, meter, wearable device, Internet of Things (loT) device, vehicle roadside unit (RSU), relay node, automobile, and / or any combination thereof. The term wirelessdevice encompasses other terminology, including user equipment (U E), user terminal (UT), access terminal (AT), mobile station, handset, wireless transmit and receive unit (WTRU), and / or wireless communication device.

[0050] 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 (g N B, 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 g N B Central Unit (gNB-CU) and at least one a g NB Distributed Unit (gNB-DU).

[0051] 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 base 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.

[0052] 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.

[0053] The RAN 104 maybe 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.

[0054] 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. 1 A, 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 be provisioned to implement 4G radio access technology or other radio access technologies, including non-3GPP radio access technologies.

[0055] FIG. 1 B 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.

[0056] 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).

[0057] 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- / i nter-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.

[0058] 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 and 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.

[0059] The 5G-CN 152 may include one or more additional network functions that are not shown in FIG. 1 B 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).

[0060] 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 g NBs, illustrated as g NB 160A and g NB 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.

[0061] 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 maybe 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. 1 B 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.

[0062] 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 maybe 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 interface management, UE context management, UE mobility management,transport of NAS messages, paging, PDU session management, and configuration transfer and / or warning message transmission.

[0063] The gNBs 160 may provide NR user plane and control plane protocol terminations towards the UEs 156 over the Uu interface. For example, the g NB 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.

[0064] 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. 1 B, one g N B 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.

[0065]

[0066] 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.

[0067] 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 maybe 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.

[0068] 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.

[0069] 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 flow 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 g NB 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.

[0070] 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-g NB 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.

[0071] 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.

[0072] 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.

[0073] 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 MAC222) 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.

[0074] 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.

[0075] 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 g N B 220. An uplink data flow through the NR user plane protocol stack may be similar to the downlink data flow depicted in FIG. 4A.

[0076] 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.

[0077] 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 to 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.

[0078] 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 thedemultiplexing process; a flag (F) for indicating the size of the SDU length field; and a reserved bit (R) field for future use.

[0079] FIG. 4B further illustrates MAC control elements (CEs) inserted into the MAC PDU by a MAC, such as MAC 223 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 maybe 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.

[0080] 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.

[0081] 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 logical 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 include, for example:

[0082] - 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;

[0083] -- 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;

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

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

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

[0087] 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 include, for example:

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

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

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

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

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

[0093] 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 include, for example:

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

[0095] - 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;

[0096] -- 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;

[0097] -- 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;

[0098] -- 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 (Rl), and scheduling requests (SR); and

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

[0100] 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.

[0101] 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.

[0102] 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 mayprovide 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.

[0103] 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 and 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.

[0104] 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. 2Aand 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_I DLE), and RRC inactive 606 (e.g., RRCJNACTIVE).

[0105] 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. 2Aand 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 stationsbased 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.

[0106] 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 maybe 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.

[0107] 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.

[0108] 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).

[0109] 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.

[0110] 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 maybelong 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.

[0111] 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.

[0112] A gNB, such as gNBs 160 in FIG. 1B, maybe 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 SOAP. A gNB-DU may comprise the RLC, the MAC, and the PHY.

[0113] 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 (PARR). 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.

[0114] 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.

[0115] 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 abaseline 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 ps. For example, NR defines numerologies with the following subcarrier spacing / cyclic prefix duration combinations: 15 kHz / 4.7 ps; 30 kHz / 2.3 ps; 60 kHz / 1.2 ps; 120 kHz / 059 ps; and 240 kHz / 0.29 ps.

[0116] 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 numerologyindependent 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.

[0117] 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.

[0118] 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

[0119] 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.

[0120] 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 serving 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.

[0121] 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.

[0122] 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.

[0123] 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).

[0124] 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.

[0125] A base station may semi-statical ly 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.

[0126] 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 timer 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.

[0127] In an example, a base station may semi-statical ly 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).

[0128] 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.

[0129] 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.

[0130] 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.

[0131] 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 be 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.

[0132] 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).

[0133] 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 aggregatemore downlink carriers than uplink carriers may be useful, for example, when the UE has more data traffic in the downlink than in the uplink.

[0134] 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).

[0135] 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 maybe 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).

[0136] 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-carrier scheduling. Uplink control information (e.g., HARQ acknowledgments and channel state feedback, such as CQI, PMI, and / or Rl) 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.

[0137] 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 UC1 1031, UC1 1032, and UC1 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 UC1 1071, UC1 1072, and UC1 1073, maybe 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 1010and 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.

[0138] 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.

[0139] 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.

[0140] 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. 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) I 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.

[0141] 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. 11 A). 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. 11 A 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.

[0142] 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 betransmitted 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.

[0143] 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 celldefining 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.

[0144] 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 the 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.

[0145] 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.

[0146] 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.

[0147] 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 spatialdirection using a first beam, and a second SS / PBCH block may be transmitted in a second spatial direction using a second beam.

[0148] 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.

[0149] 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 may 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.

[0150] 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.

[0151] 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 maybe 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.

[0152] 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.

[0153] 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 bemapped 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-MI MO, 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 a 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.

[0154] 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).

[0155] 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.

[0156] 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.

[0157] 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 maybe mapped over one or more OFDM symbols (e.g., one or twoadjacent 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 frequency 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.

[0158] 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.

[0159] 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.

[0160] 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 aretransmitted in a same slot, the UE may be configured to transmit SRS after a transmission of a PUSCH and a corresponding uplink DMRS.

[0161] 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, minislot, 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.

[0162] 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 colocated (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.

[0163] 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.

[0164] 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. 11 B 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, mbsfn- subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and / or other radio resource parameters.

[0165] The three beams illustrated in FIG. 11 B may be configured fora UE in a UE-specific configuration. Three beams are illustrated in FIG. 11 B (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.

[0166] 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.

[0167] 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 beam 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 (Rl).

[0168] 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.

[0169] FIG. 12B illustrates examples of three uplink beam management procedures: U 1 , 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.

[0170] 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).

[0171] 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.

[0172] 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 J DLE state and / or an RRCJNACTIVE 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.

[0173] 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 1 1311, a Msg 2 1312, a Msg 31313, and a Msg 4 1314. The Msg 1 1311 may include and / or be referred to as a preamble (or a random access preamble). The Msg 2 1312 may include and / or be referred to as a random access response (RAR).

[0174] 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 broadcastor 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_I NACTIVE state) The UE may determine, based on the one or more RACH parameters, a time-frequency resource and / or an uplink transmit power for transmission of the Msg 1 1311 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 4 1314.

[0175] 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 1 1311. 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-Configlndex). 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.

[0176] The one or more RACH parameters provided in the configuration message 1310 may be used to determine an uplink transmit power of Msg 1 1311 and / or Msg 3 1313. 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 1 1311 and the Msg 3 1313; and / or a power offset value between preamble groups. The one or more RACH parameters may indicate one or more thresholds based on which the 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).

[0177] The Msg 1 1311 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 31313. 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.

[0178] 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 3 1313. 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 1 1311 based on the association. The Msg 1 1311 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-OccasionMsklndex and / or ra-OccasionList) may indicate an association between the PRACH occasions and the one or more reference signals.

[0179] 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 preambleretransmission. 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).

[0180] The Msg 2 1312 received by the UE may include an RAR. In some scenarios, the Msg 2 1312 may include multiple RARs corresponding to multiple UEs. The Msg 2 1312 may be received after or in response to the transmitting of the Msg 1 1311. The Msg 2 1312 may be scheduled on the DL-SCH and indicated on a PDCCH using a random access RNTI (RA-RNTI). The Msg 2 1312 may indicate that the Msg 1 1311 was received by the base station. The Msg 2 1312 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 / ora 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 2 1312. The UE may 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 Typel -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:

[0181] RA-RNTI= 1 + sjd + 14 x tjd + 14 x 80 x fjd + 14 x 80 x 8 x ul_carrier_id, where sjd maybe an index of a first OFDM symbol of the PRACH occasion (e.g., 0 < sjd < 14), tjd may be an index of a first slot of the PRACH occasion in a system frame (e.g., 0 < tjd < 80), fjd may be an index of the PRACH occasion in the frequency domain (e.g., 0 < fjd < 8), and ul_carrierjd may be a UL carrier used for a preamble transmission (e.g., 0 for an NUL carrier, and 1 for an SUL carrier).

[0182] The UE may transmit the Msg 31313 in response to a successful reception of the Msg 2 1312 (e.g., using resources identified in the Msg 21312). The Msg 3 1313 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 anidentity of another the UE. To perform contention resolution, the UE may include a device identifier in the Msg 3 1313 (e.g., a C-RNTI if assigned, a TC-RNTI included in the Msg 2 1312, and / or any other suitable identifier).

[0183] The Msg 4 1314 may be received after or in response to the transmitting of the Msg 3 1313. If a C-RNTI was included in the Msg 3 1313, 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 3 1313 (e.g., if the UE is in an RRC_I DLE state or not otherwise connected to the base station), Msg 4 1314 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 3 1313, the UE may determine that the contention resolution is successful and / or the UE may determine that the random access procedure is successfully completed.

[0184] 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 1 1311 and / or the Msg 3 1313) may remain on the selected carrier. The UE may switch an uplink carrier during the random access procedure (e.g., between the Msg 1 1311 and the Msg 3 1313) in one or more cases. For example, the UE may determine and / or switch an uplink carrier for the Msg 1 1311 and / or the Msg 3 1313 based on a channel clear assessment (e.g., a listen- before-talk).

[0185] FIG. 13B illustrates a two-step contention-free random access procedure. Similar to the four-step contentionbased 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 1 1321 and a Msg 2 1322. The Msg 1 1321 and the Msg 2 1322 may be analogous in some respects to the Msg 1 1311 and a Msg 2 1312 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 3 1313 and / or the Msg 4 1314.

[0186] 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 1 1321. The UE may receive, from the base station via PDCCH and / or RRC, an indication of a preamble (e.g., ra-Preamblelndex).

[0187] 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.,recoverySearchSpaceld). 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 1 1321 and reception of a corresponding Msg 2 1322. 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 preamble 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.

[0188] FIG. 13C illustrates another two-step random access procedure. Similar to the random access procedures illustrated in FIGS. 13Aand 13B, a base station may, prior to initiation of the procedure, transmit a configuration message 1330 to the UE. The configuration message 1330 maybe 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.

[0189] 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 3 1313 illustrated in FIG. 13A. The transport block 1342 may comprise UCI (e.g., an SR, a HARQ AC K / 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 2 1312 (e.g., an RAR) illustrated in FIGS. 13A and 13B and / or the Msg 4 1314 illustrated in FIG. 13A.

[0190] 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.

[0191] 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.

[0192] 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 maytransmit 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 (eg., a C-RNTI ora TC-RNTI). The UE may determine that the two-step 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).

[0193] 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.

[0194] 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.

[0195] 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).

[0196] 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 3 1313 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), an Interruption RNTI (INT-RNTI), aSlot 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.

[0197] 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 J 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.

[0198] 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).

[0199] 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 timefrequency 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 ata 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.

[0200] 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 purpose 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. ACORESET 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.

[0201] 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 ata 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).

[0202] As shown in FIG 14B, the UE may determine a time-frequency resource fora 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).

[0203] 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 HARQ 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 aphysical uplink shared channel (PUSCH) . The UE may transmit the uplink control signaling via a PUCCH using one of several PUCCH formats.

[0204] 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.

[0205] 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 first 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”.

[0206] 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 for1_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.

[0207] 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.

[0208] 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.

[0209] 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, 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.

[0210] 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 (Ml MO) or multi-antenna processing, and / or the like.

[0211] 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 1522may implement layer 1 OSI functionality. Layer 1 may include a PHY layer with respect to FIG. 2A, FIG. 2 B, 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.

[0212] 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.

[0213] 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.

[0214] 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.

[0215] 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 powerto 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.

[0216] 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 may 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.

[0217] 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.

[0218] 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 complexvalued 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 timedomain 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.

[0219] 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.

[0220] 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,PC DP, 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.

[0221] 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 be 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 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.

[0222] 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.

[0223] 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 a value of reserved bits in a DL MAC PDU.

[0224] 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.

[0225] In an example, when a MAC subheader corresponds to a MAC SDU, a variable-sized MAC CE, or padding, the MAC subheader may comprise: a Reserve field (R field) with a one bit length; an Format filed (F field) with a one-bit length; a Logical Channel Identifier (LCID) field with a multi-bit length; a Length field (L field) with a multi-bit length, indicating the length of the corresponding MAC SDU or variable-size MAC CE in bytes, or a combination thereof. In an example, F field may indicate the size of the L field.

[0226] In an example, a MAC entity of the base station may transmit one or more MAC CEs (e.g., MAC CE commands) to a MAC entity of a wireless device. The one or more MAC CEs may 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 UE contention resolution identity MAC CE, a timing advance command MAC CE, a DRX command MAC CE, a Long DRX command MAC CE, an SCell 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 the base station to a MAC entity of the wireless device, may have an LCID in the MAC subheader corresponding to the MAC CE. In an example, a first MAC CE may have a first LCID in the MAC subheader that may be different than the second LCID in the MAC subheaderof a second MAC CE. For example, an LCID given by 111011 in a MAC subheader may indicate that the MAC CE associated with the MAC subheader is a Long DRX command MAC CE.

[0227] 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. The one or more MAC CEs may comprise at least one of: a short buffer status report (BSR) MAC CE, a long BSR MAC CE, a C-RNTI MAC CE, a configured grant confirmation MAC CE, a single entry PHR MAC CE, a multiple entry PHR MAC CE, a Short truncated BSR, and / or a Long truncated BSR. In an example, a MAC CE may have an LCID in the MAC subheader corresponding to the MAC CE. In an example, a first MAC CE may have a first LCID in the MAC subheader that may be different than the second LCID in the MAC subheader of a second MAC CE. For example, an LCID given by 111011 in a MAC subheader may indicate that a MAC CE associated with the MAC subheader is a short-truncated command MAC CE.

[0228] In carrier aggregation (CA), two or more component carriers (CCs) may be aggregated. The wireless device may, using the technique of CA, simultaneously receive or transmit on one or more CCs, depending on capabilities of the wireless device. In an example, the 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).

[0229] When configured with CA, the wireless device may have one RRC connection with a network. During an RRC connection establishment / re-establishment / handover, a cell providing NAS mobility information maybe a serving cell.During an RRC connection re-establish ment / handover procedure, a cell providing a security input may be the serving cell. In an example, the serving cell maybe a PCell.

[0230] In an example, the base station may transmit, to the wireless device, one or more messages. The one or more messages may comprise one or more RRC messages. For example, the one or more RRC messages may comprise one or more configuration parameters (e.g., one or more RRC configuration parameters).

[0231] In an example, the one or mor RRC configuration parameters may comprise configuration parameters of a plurality of one or more SCells, depending on capabilities of the wireless device. When configured with CA, the base station and / or the wireless device may employ an activation / deactivation mechanism of an SCell to improve battery or power consumption of the wireless device. When the wireless device is configured with one or more SCells, the base station may activate or deactivate at least one of the one or more SCells. Upon configuration of an SCell, the SCell may be deactivated unless the SCell state associated with the SCell is set to “activated” or “dormant.” The wireless device may activate / deactivate the SCell in response to receiving an SCell Activation / Deactivation MAC CE.

[0232] For example, the base station may configure (e.g., via the one or more RRC messages / configuration parameters) the wireless device with uplink (UL) bandwidth parts (BWPs) and downlink (DL) BWPs to enable bandwidth adaptation (BA) on a PCell. If carrier aggregation (CA) is configured, the base station may further configure the wireless device with at least one DL BWP (i.e„ there may be no UL BWP 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. In paired spectrum (e.g., FDD), the base station and / or the wireless device may independently switch a DL BWP and an UL BWP. In unpaired spectrum (e.g., TDD), the base station and / or the wireless device may simultaneously switch the DL BWP and the UL BWP.

[0233] In an example, the base station and / or the wireless device may switch a BWP between configured BWPs by means of a DCI or a BWP invalidity timer. When the BWP invalidity timer is configured for the serving cell, the base station and / or the wireless device may switch the active BWP to a default BWP in response to the expiry of the BWP invalidity 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 ata time in the active serving cell. In an example, for TDD systems, one DL / UL BWP pair may be active ata time in the active serving cell. Operating on one UL BWP and one DL BWP (or one DL / UL pair) may improve the wireless device battery consumption. One or more BWPs other than the active UL BWP and the active DL BWP, which the wireless device may work on, may be deactivated. On the deactivated one or more BWPs, the wireless device may: not monitor PDCCH; and / or not transmit on PUCCH, PRACH, and UL-SCH. In an example, the MAC entity of the wireless device may apply normal operations on the 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. In an example, on the inactive BWP for each activated serving cell configured with a BWP, the MAC entity of the wireless device may: not transmit on UL-SCH; not transmit on RACH; not monitor a PDCCH; not transmit PUCCH; nottransmit S RS, 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.

[0234] In an example, a DCI addressed to an RNTI may comprise a CRC of the DCI being scrambled with the RNTI. The wireless device may monitor PDCCH addressed to (or for) the RNTI for detecting the DCI. For example, the PDCCH may carry (or be with) the DCI. In an example, the PDCCH may not carry the DCI.

[0235] In an example, a set of PDCCH candidates for the wireless device to monitor is defined in terms of one or more search space sets. A search space set may comprise a common search space (CSS) set, or a UE-specific search space (USS) set. The wireless device may monitor one or more PDCCH candidates in one or more of the following search space sets: a TypeO-PDCCH CSS set configured by pdcch-ConfigSI B 1 in MIB or by searchSpaceSIB 1 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 TypeOA-PDCCH CSS set configured by searchSpaceOtherSystemlnformation in PDCCH-ConfigCommon for a DCI format with CRC scrambled by the SI-RNTI on the primary cell of the MCG, a Typel-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 a I NT-RNTI, a SFI-RNTI, a TPC-PUSCH- RNTI, a TPC-PUCCH-RNTI, a TPC-SRS-RNTI, a CI-RNTI, ora power saving RNTI (PS-RNTI) and, only for the primary cell, a C-RNTI, a MCS-C-RNTI, ora CS-RNTI(s), and the USS set configured by SearchSpace in PDCCH-Config with searchSpaceType = ue-Specific for DCI formats with CRC scrambled by the C-RNTI, the MCS-C-RNTI, a SP-CSI- RNTI, the CS-RNTI(s), a SL-RNTI, a SL-CS-RNTI, ora SL-L-CS-RNTI.

[0236] In an example, the wireless device may monitor PDCCH (e.g., monitor the one or more PDCCH candidates) according to one or more configuration parameters of the search space set. For example, the search space set may comprise a plurality of search spaces (SSs). The wireless device may monitor the one or more PDCCH candidates in one or more CORESETs for detecting one or more DCIs. Monitoring the one or more PDCCH candidates may comprise decoding at least one PDCCH candidate of the one or more PDCCH candidates according to the monitored DCI formats. For example, monitoring the one or more PDCCH candidates may comprise decoding (e.g., blind decoding) a DCI content of the at least one PDCCH candidate via possible (or configured) PDCCH location(s), possible (or configured) PDCCH format(s), e.g., number of CCEs, number of PDCCH candidates in CSS set(s), and / or number of PDCCH candidates in the USS(s), and / or possible (or configured) DCI format(s).

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

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

[0239] FIG. 17 shows several DCI formats. For example, the base station may use the DCI formats to transmit downlink control information to the wireless device. In an example, the wireless device may use the DCI formats 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. As shown in FIG. 17, DCI format 0_0 may be used to schedule PUSCH in one cell. In an example, 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.

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

[0241] In the uplink, two schemes for transmission without a dynamic grant may be supported. The two schemes may differ in the way they are activated: 1) type 1 of the configured grant (or configured grant Type 1), where an uplink grant is provided by the one or more configuration parameters (e.g., Config uredGrantConfig), including activation of the grant, 2) configured grant Type 2 (or type 2 of the configured grant), where the transmission periodicity is provided by the one or more configuration parameters (e.g., ConfiguredGrantConfig) and L1 / L2 control signaling is used to activate / deactivate the transmission in a similar way as in the SPS. The two schemes may reduce control signaling overhead, and the latency before uplink data transmission, as no scheduling request-grant cycle is needed prior to data transmission. In an example of the configured grant Type 2, the one or more configuration parameters may indicate / configure the preconfigured periodicity and PDCCH activation may provide transmission parameters. Upon receiving the activation command, the wireless device may transmit according to the preconfigured periodicity, if, for example, there are data in the buffer. If there are no data to transmit, the wireless device may, similarly to theconfigured grant Type 1 , not transmit anything. The wireless device may acknowledge the activation / deactivation of configured grant Type 2 by sending a MAC control element in the uplink. In both schemes, it is possible to configure multiple wireless devices with overlapping time-frequency resources in the uplink. In this case, the network may differentiate between transmissions from different wireless devices. In an example, PUSCH resource allocation may be semi-statically configured by the one or more configuration parameters (e.g., ConfiguredGrantConfig).

[0242] In an example, the wireless device may support a baseline processing time / capability. For example, the wireless device may support additional aggressive / faster processing time / capability. In an example, the wireless device may report to the base station a processing capability, e.g., per sub-carrier spacing. In an example, a PDSCH processing time may be considered to determine, by a wireless device, a first uplink symbol of a PUCCH (e.g., determined at least based on a HARQ-ACK timing K1 and one or more PUCCH resources to be used and including the effect of the timing advance) comprising the HARQ-ACK information of the PDSCH scheduled by a DCI. In an example, the first uplink symbol of the PUCCH may not start earlier than a time gap (e.g., Tprocafter a last symbol of the PDSCH reception associated with the HARQ-ACK information. In an example, the first uplink symbol of the PUCCH which carries the HARQ-ACK information may start no earlier than at symbol L1, where L1 is defined as the next uplink symbol with its Cyclic Prefix (CP) starting after the time gap Tproc 1after the end of the last symbol of the PDSCH.

[0243] In an example, a PUSCH preparation / processing time may be considered for determining the transmission time of an UL data. For example, if the first uplink symbol in the PUSCH allocation for a transport block (including DM- RS) is no earlier than at symbol L2, the wireless device may perform transmitting the PUSCH. In an example, the symbol L2 may be determined, by a wireless device, at least based on a slot offset (e.g., K2), SLIV of the PUSCH allocation indicated by time domain resource assignment of a scheduling DCI. In an example, the symbol L2 may be specified as the next uplink symbol with its CP starting after a time gap with length Tproc 2after the end of the reception of the last symbol of the PDCCH carrying the DCI scheduling the PUSCH.

[0244] FIG. 18A shows an example of a non-terrestrial network (NTN). FIG. 18B shows an example of an NTN with a transparent payload. FIG. 18C shows an example of assistance information (e.g., NTN assistance information) for maintenance of UL synchronization ata wireless device in an NTN. A non-terrestrial network (NTN) network (e.g., a satellite network) may be a network or a network segment (e.g., an NG-RAN consisting of gNBs) for providing nonterrestrial NR access to wireless devices. The NTN may use a space-borne vehicle to embark a transmission equipment relay node (e.g., radio remote unit or a transparent payload) or a base station (or a regenerative payload). While a terrestrial network is a network located on the surface of the earth, an NTN may be a network which uses an NTN node (e.g., a satellite) as an access network, a backhaul interface network, or both. In an example, an NTN may comprise one or more NTN nodes (or payloads and / or space-borne vehicles), each of which may provide connectivity functions, between the service link and the feeder link. As shown in FIG. 18B, a base station may, via the service link,transmit broadcast channels / signals (e.g., system information blocks, e.g., SIBx, x=1 , 2, .... 19, ...), multicast channels / signals, and / or dedicated channels / signals to wireless devices, e.g., via one or more cells / beams.

[0245] An NTN node may embark a bent pipe payload (e.g., a transparent payload) or a regenerative payload. The NTN node may have capability to store information / data received from the wireless devices and / or the base stations and forward the stored information / data to receivers (and / or other NTN platforms), e.g., a store and forward (S&F) NTN scenario. The NTN node with the transparent payload may comprise transmitter / receiver circuitries without the capability of on-board digital signal processing (e.g., modulation and / or coding) and connect to a base station (e.g., a base station of an NTN or the NTN base station or a non-terrestrial access point) via a feeder link. In some respects, as shown in FIG. 18A, the base station (e.g., a gNB / eNB) may further comprise the transparent NTN node, the feeder link, and / or a gateway (e.g., an NTN gateway). The gateway may be an earth station that is located at the surface of the earth, providing connectivity to the NTN payload using a feeder link. In some examples, the NTN node with the regenerative payload (e.g., the base station of the NTN or the NTN base station) may comprise functionalities of a base station, e.g., the on-board processing used to demodulate and decode the received signal and / or regenerate the signal before sending / transmitting it back to the earth. In some respects, the base station (e.g., the gNB) may further comprise the regenerative NTN node, the feeder link, and / or the gateway (e.g., the NTN gateway).

[0246] In some examples, the NTN node may be a satellite, a balloon, an air ship, an airplane, an unmanned aircraft system (UAS), an unmanned aerial vehicle (UAV), a drone, or the like. For example, the UAS may be a blimp, a high- altitude platform station (HAPS), e.g., an airborne vehicle embarking the NTN payload placed at an altitude between 8 and 50 km, or a pseudo satellite station. In an example, a satellite may be placed into a low-earth orbit (LEO) at an altitude between 250 km to 1500 km, with orbital periods ranging from 90 - 130 minutes. From the perspective of a given point on the surface of the earth, the position of the LEO satellite may change. In an example, a satellite may be placed into a medium-earth orbit (MEO) at an altitude between 5000 to 20000 km, with orbital periods ranging from 2 hours to 14 hours. In an example, a satellite may be placed into a geostationary satellite earth orbit (GEO) at 35,786 km altitude, and directly above the equator. From the perspective of a given point on the surface of the earth, the position of the GEO satellite may not change.

[0247] FIG. 18B shows an example of an NTN with a transparent NTN platform. Although FIG. 18B only shows an example of the NTN with the transparent NTN platform / payload / node, embodiments of FIG. 18B may be applicable for an NTN with a regenerative NTN platform or a store and forward (S&F) NTN scenario. As shown in FIG. 18B, the NTN node (e.g., the satellite) may forward a received signal (or stored data / information) from the NTN gateway on the ground back to the earth over the feeder link. In an example, the gateway and the base station may not be collocated or may be collocated. The NTN node may forward a received signal (or data) to the wireless device or the base station from another NTN node, e.g., over inter-link satellite communication links.

[0248] The NTN node may generate one or more beams over a given area (e.g., a coverage area or a cell). The footprint of a beam (or the cell) may be referred to as a spotbeam. For example, the footprint of a cell / beam may moveover the Earth’s surface with the satellite movement (e.g a LEO with moving cells or a HAPS with moving cells). The footprint of a cell / beam may be Earth fixed (e.g., quasi-earth-fixed) with some beam pointing mechanism used by the satellite to compensate for its motion (e.g., a LEO with earth fixed cells). The size of a spotbeam (e.g., diameter of the spotbeam and / or cell and / or coverage area) may range from tens of kilometers (e.g., 50 km - 200 km) to a few thousand kilometers (e.g., 3500 km). For example, the size of the spotbeam may depend on the system design.

[0249] A propagation delay (e.g., a round-trip propagation delay or a round-trip transmission delay) may be an amount of time it takes for the head of the signal to travel from a sender (e.g., the base station or the NTN node) to a receiver (e.g., the wireless device) and / or vice versa. The propagation delay may vary depending on a change in distance between the sender and the receiver, e.g., due to movement of the NTN node, movement of the wireless device, a change of an inter-satellite link, and / or feeder link switching. One-way latency / delay may be an amount of time required to propagate through a telecommunication system from the sender (e.g., the base station) to the receiver (e g., the wireless device). For the transparent NTN, the round-trip propagation delay (RTD or RTT or UE-gNB RTT) may comprise service link delay (e.g., between the NTN node and the wireless device), feeder link delay (e.g., between the NTN gateway and the NTN node), and / or between the gateway and the base station (e.g., in the case the gateway and the NTN base station are not collocated). For example, the UE-gNB RTT (or the RTD) may be twice of the one-way delay between the wireless device and the base station. In case of a GEO satellite with the transparent payload, the RTD may be approximately 556 milliseconds. A (maximum) RTD of a LEO satellite with the transparent payload and altitude of 600 km is approximately 25.77 milliseconds and with altitude of 1200 km is approximately 41.77 milliseconds. In an example, the RTD of a terrestrial network (e.g., NR, E-UTRA, LTE) may be negligible compared to the RTD of an NTN scenario (e.g., the RTD of a terrestrial network may be less than 1 millisecond).

[0250] A differential delay within a beam / cell of a NTN node may depend on, for example, the maximum diameter of the beam / cell footprint at nadir. For example, the differential delay withing the beam / cell may correspond to a maximum delay link in FIG. 18B. In an example, the differential delay may imply the maximum difference between communication latency that two wireless devices, e.g., a first wireless device (UE1) that is located close to the center of the cell / beam and a second wireless device (UE2) that is located close to the edge of the cell / beam in FIG. 18B, may experience while communicating with the base station via the NTN node. The first wireless device may experience a smaller RTD compared to the second wireless device. The link with a maximum propagation delay (e.g., the maximum delay link) may experience the highest propagation delay (or the maximum RTD) in the cell / beam. In an example, the differential delay may imply a difference between the maximum delay of the cell / beam and a minimum delay of the cell / beam. In an example, the service link to a cell / beam center may experience the minimum propagation delay in the cell / beam. Depending on implementation, for a LEO satellite, the differential delay may be at least 3.12 milliseconds and may increase up to 8 milliseconds. In an example of a GEO satellite, depending on implementation, the differential delay may be as large as 32 milliseconds.

[0251] FIG. 18C shows as example of the NTN assistance information (e.g., for maintaining the UL synchronization). A base station may transmit to a wireless device the NTN assistance information via an NTN-specific SIB (e.g., SIB19 or SIB31 ) 1800. In another example, common configuration parameters of a serving cell may comprise the NTN assistance information, e.g., an NTN-config (e.g., ntn-Config-r17, e.g., corresponding to the serving cell with a first PCI). The one or more configuration parameters may comprise the common configuration parameters of the serving cell (e.g., IE ServingCellConfigCommon). The serving cell may belong to the NTN. The wireless device may communicate with the base station via the serving cell (of the NTN). The Serving cell may be a first / source cell (with / identified by, a first PCI) and / or a second / target cell (with / identified by a second PCI). In one example, the base station may transmit to the wireless device the common configuration parameters of the serving cell via a system broadcast information (e.g., SIB1) or an RRC reconfiguration message (e.g., a handover message). For example, the base station may transmit the common configuration parameters of the serving cell via one or more RRC messages (e g., RRC setup message, RRC establishment message, RRC re-establishment message, and / or RRC reconfiguration message). The base station may transmit the common configuration parameters of the serving cell during the initial access procedure and / or the handover procedure.

[0252] The NTN assistance information may comprise a first set of NTN configuration parameters. For example, the first set of NTN configuration parameters may comprise at least one NTN-config (e.g., ntn-config-r17 1820). The at least one NTN-config may correspond to a cell (e.g., the serving cell) of the NTN and / or a non-serving cell of the NTN (e.g., a target cell or a neighbor cell of the NTN). The at least one NTN-config may correspond to a serving NTN node (satellite) or a target NTN node (satellite). Each NTN-config (e.g., ntn-Config 1820) of the at least one NTN-config may correspond to a cell (e.g., the serving cell or a neighbor cell of the NTN) with a corresponding physical cell ID (PCI). The wireless device may be in an RRC_CONNECTED state / mode or in an RRC inactive state / mode or in an RRC idle state (or mode).

[0253] As shown in FIG. 18C, the first set of NTN configuration parameters may comprise NTN-configs of one or more NTN neighbor cells (e.g., via ntn-NeighCellConfigList IE or ntn-NeighCellConfigListExt IE or the like) 1810. Each NTN neighbor cell of the one or more NTN neighbor cells may have its unique PCI. For example, the at least one NTN- config may comprise the one or more NTN neighbor cells. For example, the ntn-Neigh Cell ConfigList (and / or ntn- NeighCellConfigListExt) may indicate / provide / configure a list of NTN neighbor cells (e.g., the one or more NTN neighbor cells) including their corresponding ntn-Config(s), carrier frequency and PhysCel I Id (PCI).

[0254] The NTN assistance information (e.g., the first set of NTN configuration parameters) may comprise the NTN- config of the common configuration parameters of the serving cell (e.g., a first NTN configuration parameters) The first NTN configuration parameters (e.g., a first NTN-config of the at least one NTN-config) may correspond to the first PCI or the first cell (e.g., the source cell). When the common configuration parameters of the serving cell correspond to the RRC setup message (and / or the RRC establishment message and / or RRC re-establishment message), the NTN-config of the common configuration parameters of the serving cell may correspond to the source cell. When the commonconfiguration parameters of the serving cell correspond to the RRC reconfiguration message, the NTN-config of the common configuration parameters of the serving cell may correspond to the target cell (e.g., a second NTN configuration parameters e.g., a second NTN-config of the at least one NTN-config). The second NTN configuration parameters (e.g., the second NTN-config of the at least one NTN-config) may correspond to the second PCI or the second cell (e.g., the target cell).

[0255] An NTN-config (ntn-Config) of the at least one NTN-config may indicate / configure / provide parameters needed for the wireless device to access NR / LTE (or a 6G system) via NTN access. Each / an NTN-config of the at least one NTN-config (e.g., NTN-config-r171820) may comprise at least one of the following (or a combination of thereof): corresponding ephemeris parameters (or data / information) of an NTN node (e.g., the satellite ephemeris data, e.g., ephemerisinfo); and / or one or more common delay / TA parameters (e.g., ta-lnfo), e.g., comprising at least one of TACommon, TACommonDrift, TACommonDriftVariation; and / or a cell-specific scheduling offset (e.g., cellSpecificKoffset or Koffset, e.g., Kcenoffset) in number of slots for a given subcarrier spacing (e.g., pknffoot), e.g., 15 KHz; and / or MAC-layer scheduling offset (e.g., kmac or K-Mac) in number of slots for a given subcarrier spacing (e.g., pKmao), e.g., 15 KHz, indicating a portion of a feeder link delay that the base station may pre-compensate, e.g., when UL / DL configurations are not aligned at the base station; and / or epoch time for applying the NTN-config (e.g., epochTime); and / or a validity duration of the NTN-config (e.g., ntn-U ISyncVal idityDuration) indicating a maximum duration (e.g., in seconds) that the NTN-config stays valid (e.g., a maximum duration that the wireless device stays UL synchronized with the serving cell without (re-)acquiring / reading the SIB 19 of the serving cell); and / or one or more antenna polarization mode(s) (e.g., vertical horizontal, right-hand circular, or left-hand circular) for UL / DL communications (e.g., ntn-PolarizationUL / ntn-Polarization DL); and / or a first indication / parameter (e.g., ta-Report-r17). For example, the MAC-layer scheduling offset may be 0, e.g., when the K-Mac is absent from (is not indicated / configured by) the NTN config of the serving cell. For example, in an NTN scenario with the transparent NTN node, when the UL frame and the DL frame are aligned at the base station, the K-Mac may be absent from the NTN- config of the serving cell. The validity duration may indicate (a maximum / longest) validity period of the (satellite) ephemeris data / information and / or the TA parameters of an NTN-config (e.g., the NTN-config of the serving cell).

[0256] As shown in FIG. 18C, the NTN-specific SIB (e.g., the SIB19) may further comprise t-Service indicating a time information on when a cell (e.g., the serving cell) provided via the NTN system (e.g., an NTN node / payload / platform) is going to stop serving the area it is currently covering. t-Service field of the SIB19 may apply for both service link switches in NTN quasi-Earth fixed system and feeder link switches for both NTN quasi-Earth fixed and Earth moving system. An exact stop time that the serving NTN node terminates / stops / fin ishes serving the cell of the NTN may be between the time indicated by the value of t-Service minus 1 and the time indicated by the value of t-Service.

[0257] In some examples, the NTN-specific SIB (e.g., the SIB19) may further comprise t-ServiceStart indicating a time information on when a target satellite (of the serving cell) is going to start serving the area currently covered by aserving / source satellite (of the serving cell). Switching from the source satellite to the target satellite (e.g., the feeder link / service link switch or a satellite switch) may not comprise performing / triggering / starting a handover / reconfiguration procedure, e.g., a hard / soft satellite switch with resynchronization (e.g., a PCI unchanged service / feeder link switch or a service / feeder link switch without changing PCI of the serving cell or satellite / service link / feeder link switch without performing handover or satellite / service link / feeder link switch without reconfiguration) or a hard / soft satellite switch without reconfiguration. For example, when the SIB19 indicates / comprises a satSwitch With ReSync, the wireless device may determine the switching from the source satellite (with a first NTN-config of the at least one NTN config) to the target satellite (with a second NTN-config of the at least one NTN config) does not comprise (or is not based on) performing / triggering / starting the handover / reconfiguration procedure. When the SIB19 does not indicate / comprise / configure the satSwitchWith ReSync (e.g., the satSwitchWithReSync is absent from the SIB19), the wireless device may determine the switching from the source satellite to the target satellite comprises (or is based on) performing / triggering / starting the handover / reconfiguration procedure. The satSwitchWithReSync may indicate / configure / provide parameters for / corresponding to the target satellite that the wireless device may use / require to perform the satellite switch with re-synchronization. This satSwitchWithReSync may only be present in an NTN cell and its presence indicates that satellite switch without PCI change is supported in the cell.

[0258] Upon / in response to / after / based on receiving the NTN-specific SIB (SIB19) in / via an NTN cell, a wireless device may start or restart an NTN validity / val idation ti mer / window / period (e.g., a validity timer or timer T430) for the serving cell with a timer value set to ntn-U I SyncValidity Du ration (of an NTN-config, e.g., of the at least one NTN-config) for the serving cell from the subframe indicated by epochTime (of the NTN-config) for the serving cell. If the SIB19 comprises either SatSwitchWithReSync and / or t-Service, the wireless device supports a hard satellite switch with resynchronization (e.g., the PCI unchanged service / feeder link switch), and if t-ServiceStart is included in / indicated by the SatSwitchWithReSync of the SIB19 and the wireless device supports the soft satellite switch with resynchronization, the wireless device may perform / initiate / execute / start the satellite switch with resynchronization between a time indicated by the t-ServiceStart and a time indicated by the t-Service for the serving cell. If the SIB19 comprises either SatSwitchWithReSync and / or t-Service, the wireless device supports a hard satellite switch with resynchronization (e.g., the PCI unchanged service / feeder link switch), and if t-ServiceStart is not included in / indicated by the SatSwitchWithReSync of the SIB19 or the wireless device does not support the soft satellite switch with resynchronization, the wireless device may perform / initiate / execute / start the satellite switch with resynchronization at a time indicated by the t-Service for the serving cell.

[0259] For performing / initiating / executing / starting the satellite switch with re-synchronization (e.g., in the RRC_CONNECTED state / mode), the wireless device may perform at least one of the following: stop / expiring the validity timer (e.g., timer T430) if running; and / or inform / notifying (or sending an indication to) lower layers of the wireless device (e.g., the MAC layer) that UL synchronization is lost due to satellite switch with re-synchronization; and / or starting / initiating / performing re-synchronizing to a downlink (DL) of the serving cell of (e.g., an SpCell served by)the target satellite (e.g., the target satellite corresponding to the second NTN config, e.g. , an ntn-Config inSatS witch With ReSync of the SIB19); and / or starting the validity timer (e.g., the timer T430) with the timer value set to ntn- Ul SyncVa lidity Duration from the subframe indicated by epochTime in the second NTN-config; and / or informing the lower layers when / that the UL synchronization is obtained.

[0260] For performing / initiating / executing / starting the satellite switch with reconfiguration (e.g., the handover procedure) and when the target cell is part of the NTN, the wireless device may start timer T430 with the timer value set to ntn-UISyncValidity Duration from the subframe indicated by epochTime, according to a third NTN-Config of the at least one NTN config (e.g., corresponding to / of the target cell).

[0261] Upon or in response to acquiring / receiving an NTN-config (e.g., the first / second or third NTN-config) of the serving cell (e.g., upon reception of the SIB19 and / or upon reception of RRCReconfiguration message for the target cell including reconfigurationWithSync and / or upon conditional reconfiguration execution, e.g., when applying a stored RRCReconfiguration message for a target cell including reconfigurationWithSync), the wireless device may start / restart the validity (or validation) duration / timer / window / period (e.g., T430 timer) of the serving cell. For example, the wireless device may start the validity timer based the epoch time indicated by the NTN-config of the serving cell, e.g., the wireless device may start the validity timer from a subframe indicated by the epoch time. The wireless device may set an initial value of the T430 timer by ntn-UISyncValidityDuration of the NTN-config of the serving cell. The wireless device may stop the validity timer of the serving cell (e.g., a source cell or first cell) upon reception of the RRCReconfiguration message for the target cell (e.g., a second cell and / or a target serving cell) including reconfigurationWithSync and / or upon conditional reconfiguration execution, e.g., when applying a stored RRCReconfiguration message for the target cell including reconfigurationWithSync.

[0262] In an example, in response to determining that the validity duration being expired, the wireless device may stop UL transmissions (e.g., of PUSCH / PUCCH / SRS / PRACH signals / channels) via the serving cell and / or flush HARQ buffers of one or more HARQ processes. The wireless device may, in response to the expiry of the validity timer / du ration, suspend / halt (any / all) UL transmissions until acquiring the SIB19 (of the serving cell or a target cell or a target satellite). For example, the wireless device may acquire the SIB19 of the serving cell to receive an update NTN assistance information 1800. The wireless device may receive an update (satellite) ephemeris data / information and / or update common TA parameters. The wireless device may, prior to expiry of the validity duration of the serving cell and to reduce interruption in UL transmissions, (re-)acquire the SIB19 in order to have valid (estimate of) the open-loop TA value of the serving cell (valid TA value).

[0263] In an example, upon the expiry of the validity duration of the serving cell and when the wireless device is not able to (re-)acquire the SIB19 (of the serving cell), the wireless device may become UL unsynchronized with the base station of the serving cell, e.g., for UL communication with the base station via the serving cell.

[0264] To maintain uplink orthogonality in a serving cell, transmissions from different wireless devices in a cell / beam (e.g., the first wireless device and the second wireless device in FIG. 18B) may need to be time-aligned at the basestation and / or the NTN node (e.g. , satellite). The cell may be the serving cell. In an example, time al ig nment / synchronization may be achieved by using different timing advance (TA) values at different wireless devices to compensate for their different propagation delays (or RTDs). As shown in FIG. 18B, for UL transmissions, the first wireless device may use the first TA value (e.g., TA_1 ) and the second wireless device may use the second TA value (TAJ).

[0265] FIG. 19 shows an example of downlink HARQ operation in a wireless communication system per an aspect of the present disclosure. The wireless device may communicate with a base station via an NTN node or a serving cell of the NTN. In some examples, the serving cell may be part of terrestrial network. The wireless device may be in an RRC connected (or RRC inactive / idle) state / mode. As shown the wireless device may receive the one or more messages (vis the serving cell and / or from the base station), e.g., RRC messages or MAC CE or DCIs, comprising the one or more configuration parameters. The one or more configuration parameters may, for example, comprise the NTN assistance information (e.g., the NTN-config)

[0266] As shown in FIG. 19, the wireless device may receive a transport block (TB) (e.g., in a PDSCH reception occasion) from the base station, e.g., via the serving cell. For example, the wireless device may receive (from the base station, e.g., via the serving cell) a DCI (e.g., in / within / during a PDCCH monitoring occasion) scheduling / indicating the transmission / reception of the TB / PDSCH. The TB / PDSCH may correspond to (or be associated with a HARQ process with a HARQ process ID / index / identifier / number). For example, the DCI may indicate the HARQ process ID (or the HARQ process), e.g., via a "HARQ process number" field. In other examples, when the PDSCH is an SPS-PDSCH, the wireless device may determine the HARQ process ID based on reception occasion / slot / symbol of the PDSCH and / or the one or more configuration parameters (e.g., SPS-Config). As shown in FIG. 19, the wireless device may, via a PUCCH / PUSCH resource, transmit a HARQ-ACK information, corresponding to the HARQ process, in response to the receiving the TB / PDSCH (e.g., decoding result / outcome of the TB).

[0267] For example, based on decoding result of the TB (e.g., in the PDSCH reception) and / or configuration parameters (e.g., whether the HARQ process corresponding to the TB is a feedback-enabled or feedback-disabled and / or HARQ codebook), the wireless device may determine whether to transmit HARQ-ACK information (via PUCCH / PUSCH) and / or ACK / NACK value of the HARQ-ACK information. The wireless device may determine a slot for transmission of HARQ-ACK information (and / or PUCCH / PUSCH resource) based on the one or more configuration parameters (e.g., PUSCH-Config / PUCCH-Config / SPS-config) and / or the DCI scheduling the TB.

[0268] The one or more configuration parameters (e.g., IE PDSCH-ServingCellConfig) may configure a wireless device with a first plurality of HARQ processes (e.g., nrofHARQ-ProcessesForPDSCH), e.g., for receiving PDSCHs / TBs in DL of a serving cell. When nrofHARQ-ProcessesForPDSCH is absent from the one or more configuration parameters (e.g., IE PDSCH-ServingCellConfig), a number of the first plurality of HARQ processes may be 8 or 4 or 12 or the like (e.g., a default / predefined value). The one or more configuration parameters may configure / indicate (e.g., via downl i nkHARQ-FeedbackDisabled) whether a (DL) HARQ process of the first HARQ processes is a feedback-enabledHARQ process (e.g., a HARQ process with enabled HARQ-ACK information) or a feedback-disabled HARQ process (e.g,, a HARQ process with disabled HARQ-ACK information). For example, the downlinkHARQ-FeedbackDisabled may indicate a bitmap with a length of 32 bits. A first / leftmost bit of downlinkHARQ-FeedbackDisabled may correspond to HARQ process ID 0 (of the first plurality of HARQ processes), a next bit to HARQ process ID 1 (of the first plurality of HARQ processes) and so on.

[0269] For example, an n-th bit (n>=0) of the downlinkHARQ-FeedbackDisabled set to one may indicate / identify / configure the n-th HARQ process of the first plurality of HARQ processes with disabled DL HARQ feedback (e.g., the n-th HARQ process is with disabled HARQ-ACK information. As shown in FIG. 19, in response to receiving a TB / PDSCH corresponding to / associated with the n-th HARQ process with disabled DL HARQ feedback, the wireless device may not transmit / send / provide HARQ-ACK information. In some cases, in response to receiving a TB / PDSCH corresponding to / associated with the n-th HARQ process with disabled DL HARQ feedback and a Type-1 (semi-static) HARQ-ACK codebook being configured, the wireless device may transmit a HARQ-ACK information with a predefined value (e.g., NACK or ACK) regardless of decoding result of the TB. In some other cases, in response to receiving a TB / PDSCH corresponding to / associated with the n-th HARQ process with disabled DL HARQ feedback and a Type-2 (dynamic) HARQ-ACK codebook being configured, the wireless device may avoid transmitting a HARQ-ACK information.

[0270] In another example, an n-th bit (n>=0) of the downlinkHARQ-FeedbackDisabled set to 0 may indicate / identify / configure the n-th HARQ process of the first plurality of HARQ processes with enabled DL HARQ feedback (e.g., the n-th HARQ process is with enabled HARQ-ACK information. As shown in FIG. 19, in response to receiving a TB / PDSCH corresponding to / associated with the n-th HARQ process with enabled DL HARQ feedback, the wireless device may transmit / send / provide HARQ-ACK information (e.g., based on semi-static / dynamic HARQ-ACK codebook). The wireless device may determine value of HARQ-ACK information based on decoding result of the TB / PDSCH (e.g., ACK when the TB / PDSCH is correctly / successfully decoded and NACK when the TB / PDSCH is incorrectly / successfully decoded).

[0271] For example, the one or more configuration parameters (e.g., IE PhysicalCellGroupConfig) may configure a wireless device with pdsch-HARQ-ACK-Codebook = semi-static (e.g., a semi-static HARQ codebook). The semi-static HARQ codebook may be a Type 1 HARQ codebook (or a Type-1 HARQ-ACK codebook). The semi-static HARQ codebook may correspond to unicast and / or multicast operation (PDSCHs). For example, a wireless device may generate a Type-1 HARQ-ACK codebook considering only one of respective unicast or multicast configurations for PDSCH receptions or for PDCCH monitoring for detection of DCI formats.

[0272] In an example, when a wireless device is configured with pdsch-HARQ-ACK-Codebook = semi-static, the wireless device may not transmit / provide (or send) a Type-1 HARQ-ACK codebook based on the Type-1 HARQ-ACK codebook includes only HARQ-ACK information for transport blocks associated with HARQ processes with disabled HARQ-ACK information. For example, the wireless device may receive a first number of transport blocks (TBs orPDSCHs) wherein each TB / PDSCH of the first number of TBs / PDSCHs correspond to a feedback-disabled HARQ process (e.g. , each TB / PDSCH of the first number of TBs / PDSCHs is associated with a HARQ process with disabled HARQ-ACK information). The wireless device may not transmit / send the Type-1 HARQ-ACK codebook corresponding to the first number of TBs / PDSCHs.

[0273] When a wireless device is configured with pdsch-HARQ-ACK-Codebook = semi-static, the wireless device may transmit / provide (or send) a Type-1 HARQ-ACK codebook based on the Type-1 HARQ-ACK codebook includes at least one HARQ-ACK information for a transport block associated with a HARQ process with enabled HARQ-ACK information. For example, the wireless device may receive a second number of transport blocks (TBs or PDSCHs) wherein at least one TB / PDSCH of the second number of TBs / PDSCHs correspond to a feedback-enabled HARQ process (e.g., at least one TB / PDSCH of the second number of TBs / PDSCHs is associated with a HARQ process with enabled HARQ-ACK information). The wireless device may transmit / send the Type-1 HARQ-ACK codebook corresponding to the second number of TBs / PDSCHs.

[0274] If a wireless device is provided downlinkHARQ-FeedbackDisabled indicating disabled HARQ-ACK information for a HARQ process associated with a transport block in PDSCH reception occasion m on a serving cell c, the wireless device may report / transmit / send a NACK value for a HARQ-ACK information bit corresponding to the transport block in a Type-1 HARQ-ACK codebook. If the wireless device is provided downlinkHARQ-FeedbackDisabled indicating enabled HARQ-ACK information for a HARQ process associated with a transport block in PDSCH reception occasion m on a serving cell c, the wireless device may report / transmit / send a HARQ-ACK information bit corresponding to the transport block in a Type-1 HARQ-ACK codebook based on decoding result / outcome of the transport block.

[0275] If a wireless device is provided downlinkHARQ-FeedbackDisabled indicating disabled HARQ-ACK information for a HARQ process associated with a transport block in PDSCH reception occasion m on a serving cell c and if the wireless device is provided PDSCH-CodeBlockGroupTransmission (via the one or more configuration parameters), the wireless device may report NACK values for HARQ-ACK information bits corresponding to CBGs of the transport block in the Type-1 HARQ-ACK codebook. If a wireless device is provided downlinkHARQ-FeedbackDisabled indicating enabled HARQ-ACK information for a HARQ process associated with a transport block in PDSCH reception occasion m on a serving cell c and if the wireless device is provided PDSCH-CodeBlockGroupTransmission (via the one or more configuration parameters), the wireless device may report / transmit / send (via PUCCH / PUSCH) HARQ-ACK information bits corresponding to CBGs of the transport block in the Type-1 HARQ-ACK codebook based on decoding results / outcomes of the CBGs of the transport block.

[0276] If a wireless device is provided downlinkHARQ-FeedbackDisabled indicating disabled HARQ-ACK information for a HARQ process associated with a transport block in PDSCH reception occasion m on a serving cell c and if the wireless device is provided harq-feedbackEnablingforSPSactive = 'enabled' (via the one or more configuration parameters), the wireless device may consider a HARQ process associated with a transport block in afirst / starting / initial / earliest SPS PDSCH reception, after an activation of SPS PDSCH receptions, to have enabled HARQ-ACK information, e.g. , the wireless device may transmit / send / provide (via PUCCH / PUSCH) a HARQ-ACK information bit according to a decoding outcome for the transport block in the first SPS PDSCH reception, e.g , if successfully decoding the transport block in the first SPS PDSCH reception the HARQ-ACK information bit is an ACK value and if unsuccessfully decoding the transport block in the first SPS PDSCH reception the HARQ-ACK information bit is a NACK value.

[0277] If a wireless device is provided downlinkHARQ-FeedbackDisabled indicating disabled HARQ-ACK information for a HARQ process associated with a transport block in PDSCH reception occasion m on a serving cell c and if the wireless device is not provided harq-feedbackEnablingforSPSactive = 'enabled' (e.g., harq- feedbackEnablingforSPSactive = 'disabled'), the wireless device may consider a HARQ process associated with a transport block in a first / starting / initial / earliest SPS PDSCH reception, after an activation of SPS PDSCH receptions, to have disabled HARQ-ACK information, e.g., the wireless device may not transmit / send (e.g., avoid / ignore / skip transmitting / sending / providing) a HARQ-ACK information bit according to a decoding outcome for the transport block in the first SPS PDSCH reception.

[0278] When a wireless device is configured with pdsch-HARQ-ACK-Codebook = semi-static, the wireless device may, via a serving cell, receive a DCI (see FIG. 19) indicating a PDSCH reception or SPS PDSCH release or TCI state update. For example, the wireless device may determine a slot for reporting / transmitting / sending a HARQ-ACK information (via PUCCH / PUSCH) for a corresponding PDSCH reception or SPS PDSCH release or TCI state update (indicated by the DCI or DCI format). The wireless device may determine the slot based on the DCI (e.g., a value of a PDSCH-to-HARQ_feedback timing indicator field in the corresponding DCI). For example, the value of the PDSCH-to- HARQJeedback timing indicator field in the corresponding DCI may be an applicable value (integer value) or a non- applicable / inappl icable value (e.g., a non-integer value). If the PDSCH-to-HARQ_feedback timing indicator field is not present in the DCI or if a PDSCH reception corresponds to an SPS PDSCH reception (configured via SPS-Config), the wireless device may determine the slot (for report (or transmit or send) the HARQ-ACK information for the corresponding PDSCH reception or SPS PDSCH release or TCI state update) based on the one or more configuration parameters (e.g., dl-DataToUL-ACK or dl-DataToUL-ACK-r16 or dl-DataToUL-ACK-DCI-1 -2 or dl-DataToUL-ACK-r17 ordl-DataToUL-ACK-DCI-1-2-r17).

[0279] For example, the one or more configuration parameters may configure a wireless device with a Type-2 HARQ- ACK codebook (e.g., pdsch-HARQ-ACK-Codebook = dynamic or with pdsch-HARQ-ACK-Codebook-r16). Based on the DCI in FIG. 19 comprising a counter DAI filed, the wireless device may not multiplex (e.g., avoid multiplexing) in a Type-2 HARQ-ACK codebook a HARQ-ACK information corresponding to the TB / PDSCH scheduled by the DCI. For example, the wireless device may not expect (or consider it as error) to multiplex the Type-2 HARQ-ACK codebook theHARQ-ACK information that is in response to the detection of the DCI format that does not include the counter DAI field.

[0280] When the downlinkHARQ-FeedbackDisabled indicates a disabled HARQ-ACK information for a HARQ process associated with a transport block for PDCCH monitoring occasion m or for SPS PDSCH receptions on serving cell c, the wireless device may not multiplex a HARQ-ACK information bit corresponding to the transport block in a Type-2 HARQ-ACK codebook. For example, when the wireless device is configured with a Type-2 HARQ-ACK codebook, the wireless device may not transmit the HARQ-ACK information bit corresponding to the transport block associated with a feedback-disabled HARQ process. When the wireless device is configured with a Type-2 HARQ-ACK codebook, the wireless device may transmit a Type-2 HARQ-ACK codebook not comprising the HARQ-ACK information bit corresponding to the transport block associated with a feedback-disabled HARQ process.

[0281] When the downlinkHARQ-FeedbackDisabled indicates an enabled HARQ-ACK information for a HARQ process associated with a transport block for PDCCH monitoring occasion m or for SPS PDSCH receptions on serving cell c, the wireless device may multiplex a HARQ-ACK information bit corresponding to the transport block in a Type-2 HARQ-ACK codebook. For example, when the wireless device is configured with a Type-2 HARQ-ACK codebook, the wireless device may transmit (via PUCCH / PUSCH) the HARQ-ACK information bit corresponding to the transport block associated with a feedback-enabled HARQ process. When the wireless device is configured with a Type-2 HARQ-ACK codebook, the wireless device may transmit (via PUCCH / PUSCH) a Type-2 HARQ-ACK codebook comprising the HARQ-ACK information bit corresponding to the transport block associated with a feedback-enabled HARQ process.

[0282] When the wireless device is configured with a Type-2 HARQ-ACK codebook, if the downlinkHARQ- FeedbackDisabled indicates a disabled HARQ-ACK information for a HARQ process associated with a transport block for PDCCH monitoring occasion m or for SPS PDSCH receptions on serving cell c and if the wireless device is provided PDSCH-CodeBlockGroupTransmission, the wireless device may not multiplex HARQ-ACK information bits corresponding to CBGs of the transport block in the Type-2 HARQ-ACK codebook.

[0283] When the wireless device is configured with a Type-2 HARQ-ACK codebook, if the downlinkHARQ- FeedbackDisabled indicates an enabled HARQ-ACK information for a HARQ process associated with a transport block for PDCCH monitoring occasion m or for SPS PDSCH receptions on serving cell c and if the wireless device is provided PDSCH-CodeBlockGroupTransmission, the wireless device may multiplex HARQ-ACK information bits corresponding to CBGs of the transport block in the Type-2 HARQ-ACK codebook. For example, the wireless device may transmit (via PUCCH / PUSCH) the HARQ-ACK information bits corresponding to CBGs of the transport block. The wireless device may transmit (via PUCCH / PUSCH) the Type-2 HARQ-ACK codebook.

[0284] When the wireless device is configured with a Type-2 HARQ-ACK codebook, if the downlinkHARQ- FeedbackDisabled indicating a disabled HARQ-ACK information for a HARQ process associated with a transport block for PDCCH monitoring occasion m or for SPS PDSCH receptions on serving cell c and if the wireless device is providedharq-feedbackEnabl ingforSPSacti ve = 'enabled1, the wireless device may consider a HARQ process associated with a transport block in a first SPS PDSCH reception, after an activation of SPS PDSCH receptions, to have enabled HARQ- ACK information and the wireless device may provide / transmit / send (via PUCCH / PUSCH) a HARQ-ACK information bit according to a decoding outcome for the transport block in the first SPS PDSCH reception. When the wireless device is configured with a Type-2 HARQ-ACK codebook, if the downlinkHARQ-FeedbackDisabled indicating a disabled HARQ- ACK information for a HARQ process associated with a transport block for PDCCH monitoring occasion m or for SPS PDSCH receptions on serving cell c and if the wireless device is provided harq-feedbackEnablingforS PSactive = 'disabled', the wireless device may not consider a HARQ process associated with a transport block in a first SPS PDSCH reception, after an activation of SPS PDSCH receptions, to have enabled HARQ-ACK information (e.g., the wireless device consider the HARQ process associated with the transport block in the first SPS PDSCH reception to have disabled HARQ-ACK information).

[0285] If a wireless device is indicated to not provide multicast HARQ-ACK information associated with PDCCH monitoring occasion m or for SPS PDSCH receptions on serving cell c, the wireless device may not multiplex corresponding HARQ-ACK information bits in a Type-2 HARQ-ACK codebook.

[0286] As shown in FIG. 19, the one or more configuration parameters may configure common PUCCH resource(s) (e g., common PUCCH resource configuration) and / or dedicated PUCCH resource(s) (e g., dedicated PUCCH resource configuration) for transmission of a HARQ-ACK information (or Type-1 / 2 HARQ-ACK codebooks). For example, when a wireless device does not have the dedicated PUCCH resource configuration (e.g., provided by PUCCH-ResourceSet in PUCCH-Config), a PUCCH resource set (for transmission of the HARQ-ACK information on PUCCH in an initial UL BWP) may be provided by pucch-ResourceCommon through an index to a row of a configuration table (e.g., common PUCCH resource configuration).

[0287] A PUCCH resource set may comprise one or more PUCCH resources (e.g., sixteen resources). Each PUCCH resource / resource set may correspond to a PUCCH format, a first symbol, a duration, a PRB offset RB “, and a cyclic shift index set for a PUCCH transmission.

[0288] A PUCCH resource of a dedicated PUCCH resource set may include at least one of the following: a PUCCH resource index provided by pucch-Resourceld; an index of a first PRB prior to frequency hopping or for no frequency hopping by startingPRB; an index of the first PRB after frequency hopping by secondHopPRB; an indication for intraslot frequency hopping by i ntraSlotFrequencyHoppi ng ; an index of a first interlace by interlaceO, if a UE is provided uselnterlacePUCCH-PUSCH in BWP-UplinkDedicated; if provided, an index of a second interlace by interlacel, if a UE is provided uselnterlacePUCCH-PUSCH in BWP-UplinkDedicated; an index of an RB set by rb-Setlndex, if a UE is provided uselnterlacePUCCH-PUSCH in BWP-UplinkDedicated;an indication for applying one or both of TCI-State or TCI-UL-State by apply-lndicatedTCI State, if provided; and / or a configuration for a PUCCH format provided by format. For example, the PUCCH-Config may configure up to 4 dedicated PUCCH resource sets.

[0289] For example, if a wireless device provides / transmits / sends a HARQ-ACK information in a PUCCH transmission in response to detecting a DCI format scheduling a PDSCH reception (see, e.g., FIG. 19), the wireless device may determine a PUCCH resource (e.g., for the PUCCH transmission) with index rPUCCH, 0 < rPUCCH< 15, as fpuccH = + 2 • ApR|, where NCCPis a number of CCEs in a CORESET of a PDCCH reception with the DCI format, nCCE 0is the index of a first CCE for the PDCCH reception, and APrais a value of the PUCCH resource indicator field in the DCI format. If a wireless device provides / transmits / sends a HARQ-ACK information in a PUCCH transmission in response to detecting a DCI format having associated HARQ-ACK information without scheduling a PDSCH reception, the wireless device may determine a PUCCH resource (e.g., for the PUCCH transmission) with index rPUCCH, 0 < rPUCCH< 15,

[0290] For example, the wireless device may (to transmit the HARQ-ACK information via the PUCCH / PUSCH) determine a PUCCH resource. The wireless device may determine the PUCCH resource for a PUCCH transmission in the slot using a PUCCH resource indicator field in the DCI format that schedules the (multicast or unicast) PDSCH / TB reception, e.g., regardless of whether or not the PDSCH reception provides the transport block for a HARQ process with disabled HARQ-ACK information or enabled HARQ-ACK information (e.g., as indicated by downlinkHARQ- FeedbackDisabled). In some case, the wireless device may determine the slot the PUCCH transmission, e.g., regardless of whether or not the PDSCH reception provides the transport block for a HARQ process with disabled HARQ-ACK information or enabled HARQ-ACK information (e.g., as indicated by downlinkH ARQ- FeedbackDisabled) . For example, corresponding to a TB received / indicated by / via a PDSCH reception, the wireless device may determine the PUCCH resource and / or the slot for the PUCCH transmission regardless (or irrespective) of whether the corresponding HARQ process of the TB being a feedback-enabled HARQ process or a feedback-disabled HARQ process. For example, for determining the PUCCH resource and / or the slot for the PUCCH transmission, the wireless device may assume (or determine or consider) to generate HARQ-ACK information regardless of whether or not the PDSCH reception provides a transport block for a HARQ process with disabled HARQ-ACK information as indicated by downlinkHARQ-FeedbackDisabled. For transmitting the HACK-ACK information, the wireless device may determine a number of HARQ-ACK information bits OACKand a corresponding set of PUCCH resources. If OACK= 0, the wireless device may not transmit a PUCCH that only includes HARQ-ACK information bits.

[0291] For example, the wireless device may not expect to transmit (or avoid transmitting) more than one PUCCH with HARQ-ACK information in the slot per priority index, e.g., if the wireless device is not provided (e.g., via the one or more configuration parameters) ackNackFeedbackMode = separate.

[0292] For example, the slot (for transmission of PUCCH), e.g., slot n, may be a last / final / endi ng / latest UL slot for PUCCH transmission that overlaps with a PDSCH reception or with a PDCCH reception providing a DCI format having associated HARQ-ACK information without scheduling a PDSCH reception. For example, the slot n may be thelast / final / ending / latest UL slot for PUCCH transmission that overlaps with the DL slot nDfor the PDSCH reception or with the DL slot nDfor the PDCCH reception in case of a DCI format that triggers a HARQ-ACK information report and does not schedule a PDSCH reception. For a SPS PDSCH reception ending in DL slot nD, the wireless device may transmit the PUCCH in an UL slot n + k■ / fsetwhere k is provided by the PDSCH-to-HARQJeedback timing indicator field, if present, in a DCI format activating the SPS PDSCH reception. / <offsetis the scheduling offset of the NTN (e.g., based on the cell-specific Koffset and / or the differential / UE-specific Koffset). If the wireless device detects a DCI format that does not include a PDSCH-to-HARQ_feedback timing indicator field and schedules a PDSCH reception or activates a SPS PDSCH reception ending in DL slot nD, the wireless device may provide (or send / transmit) corresponding HARQ-ACK information in a PUCCH transmission within UL slot n + k +■ Koffsetwhere k is provided / configured / indicated by the one or more configuration parameters (e.g., by dl-DataTo UL-ACK , or dl- DataToUL-ACK-r16, or dl-DataToUL-ACK-DCI-1-2, or dl-DataToUL-ACK-r17, or dl-DataToUL-ACK-DCI-1-2-r17, or dl- DataToUL-ACK-v1700). If the wireless device detects a DCI format scheduling a number of PDSCH receptions ending in DL slot nDor if the UE detects a DCI format generating a HARQ-ACK information bit and does not schedule a PDSCH reception through a PDCCH reception ending in DL slot nD, the wireless device may send / transmit (or provide) corresponding HARQ-ACK information in a PUCCH transmission within UL slot n + k +■ Koffset, where k is a number of slots and is indicated by the PDSCH-to-HARQ_feedback timing indicator field in the DCI format, if present, or provided / configured / indicated by the one or more configuration parameters (e.g., dl-DataToU L-AC K , dl-DataTo UL- ACK-r16, or dl-DataToUL-ACK-DCI-1-2, or dl-DataToUL-ACK-r17, or dl-DataToUL-ACK-DCI-1-2-r17, or dl-DataToUL- ACK-V1700).

[0293] In an example, for a PUCCH transmission with HARQ-ACK information, a wireless device may determine a PUCCH resource on a cell of the PUCCH transmission (e.g., the serving cell) after determining a set of PUCCH resources for Oua(or OACK) HARQ-ACK information bits. The PUCCH resource determination maybe based on a PUCCH resource indicator (PRI) field (if present) of the DCI. The DCI may be a last / final / ending DCI (or DCI format) (e.g., excluding the SPS activation DCI, among the DCI formats that have a value of a PDSCH-to-HARQ_feedback timing indicator field, if present, ora value of dl-DataToUL-ACK, or dl-DataToUL-ACK-r16, or dl-DataToUL-ACK-DCI-1 - 2, or dl-DataToUL-ACK-r17, or dl-DataToUL-ACK-DCI-1 -2-r17, or dl-DataToUL-ACK-MulticastDCI-Format4-1 , or dl- DataToUL-ACK-v1700, indicating a same slot for the PUCCH transmission) that the wireless device detects and for which the wireless device transmits corresponding HARQ-ACK information in the PUCCH. The PUCCH resource indicator field values may map to values of a set of PUCCH resource indexes (defined / configured via the one or more configuration parameters) for a PUCCH resource indicator field of 3 bits, e.g., provided / configured / indicated by resourceList for PUCCH resources from a set of PUCCH resources provided by PUCCH-ResourceSet with a maximum of eight PUCCH resources. For example, for a first set of PUCCH resources and when the size RPUCCHof resourceList is larger than eight, when a wireless device sends / transmits / provides HARQ-ACK information in a PUCCH transmissionin response to detecting a last DCI format (e.g., the DCI indicating the PRI) in a PDCCH reception, (e.g. , excluding the SPS activation DCI, among DCI formats with a value of the PDSCH-to-HARQ_feedback timing indicator field, if present, ora value of dl-DataTolIL-ACK, or dl-DataTollL-ACK-r16, or dl-DataToUL-ACK-DCI-1-2, or dl-DataTolIL- AC K-r17, or dl-DataToUL-ACK-DCI-1 -2-r17, or dl-DataToUL-ACK-MulticastDCI-Format4-1, or dl-DataToUL-AC K- v1700, indicating a same slot for the PUCCH transmission), the wireless device may determine a PUCCH resource with index rPUCCH, 0 < rPUCCH< RPUCCH - 1. based on at least one of the following: NCCE p, e.g., a number of CCEs in CORESET p of the PDCCH reception for the DCI format; nCCE p, e.g., an index of a first CCE for the PDCCH reception; and / or APra, e.g., a value of the PUCCH resource indicator field in the DCI format.

[0294] For example, if a wireless device determines a first resource for a PUCCH transmission with HARQ-ACK information corresponding only to a PDSCH reception without a corresponding PDCCH or detects a first DCI format indicating a first resource for a PUCCH transmission with corresponding HARQ-ACK information in a slot and also detects at a later time a second DCI format indicating a second resource for a PUCCH transmission with corresponding HARQ-ACK information in the slot, the wireless device may not multiplex HARQ-ACK information corresponding to the second DCI format in a PUCCH resource in the slot if the PDCCH reception that includes the second DCI format is not earlier than a timing gap (e.g., N3■ (2048 + 144) ■ K ■ 2”p■ Tc) from the beginning of a first symbol of the first resource for PUCCH transmission in the slot, p may correspond to the smallest SCS configuration among the SCS configurations of the PDCCHs providing the DCI formats and the SCS configuration of the PUCCH. If processingType2Enabled of PDSCH-ServingCellConfig is set to enable for the serving cell with the second DCI format and for all serving cells with corresponding HARQ-ACK information multiplexed in the PUCCH transmission in the slot, N3= 3 for pi = 0, N3= 4.5 for p = 1, N3= 9 for p = 2; otherwise, N3= 8 for p = 0, N3= 10 for p = 1, N3= 17 for p = 2, N3= 20 for p = 3, N3= 80 for p = 5, and N3= 160 for p = 6.

[0295] FIG. 20A, FIG. 20B, FIG. 21 A, and FIG. 21 B show examples of multiplexing of HARQ-ACK information in a PUSCH transmission. Although not shown in FIG. 20A, FIG. 20B, FIG. 21A, and FIG. 21B, similar to FIG. 19, the wireless device may receive (e.g., via the serving cell) the one or more configuration parameters. Embodiments of FIG. 20A, FIG. 20B, FIG. 21 A, and FIG. 21 B may be used for the transmission of the HARQ-ACK information via the PUSCH in FIG. 19. Embodiment of FIG. 19, discussed above, may be used to determine PUCCH resource / occasion for transmission of the HARQ-ACK information.

[0296] As shown in FIG. 20A and FIG. 20B, the wireless device may (from the base station, e.g., via the serving cell) receive a first DCI (DC11) indicating / scheduling a (reception / transmission of) a PDSCH / TB corresponding to a HARQ process. For example, the wireless device may receive the first DCI within / during / in a PDCCH monitoring occasion (e.g., a downlink control channel monitoring occasion). Although, in the example of FIG. 20A and FIG. 20B, the wireless device may receive both the first DCI and the TB / PDSCH within / during a slot n, it is understood that the wireless device may receive the TB / PDSCH in / during / within another occasion / slot (e.g., slot n+i, i>=1 ).

[0297] Further, although, in the example of FIG. 20A and FIG. 20B, reception of only one TB / PDSCH is shown, the first DCI may schedule M (e.g., M>1) TBs / PDSCHs. PUCCH occasion / resource in / during slot p may correspond to the M scheduled TBs / PDSCHs by the first DCI.

[0298] For example, the first DCI may indicate a HARQ process number / l D / i ndex / identifier of the HARQ process. As shown in FIG. 20A and FIG. 20B, the HARQ process may be a feedback-enabled HARQ process (e.g., the HARQ process has enabled HARQ-ACK information). For example, the first DCI may indicate the HARQ process being a feedback-enabled HARQ process and / or the one or more configuration parameters may configure / indicate the HARQ process as the feedback-enabled HARQ process. For example, when the one or more configuration parameters configures / indicates the HARQ process as the feedback-disabled HARQ process, the first DCI may indicate the HARQ process being a feedback-enabled HARQ process (e.g., the first DCI changes / updates / modifies state / mode of the HARQ process from the feedback-disabled to the feedback-enabled).

[0299] Although in FIG. 20A and FIG. 20B, the first DCI schedules / indicates (or triggers) the PDSCH / TB transmission / reception, in some implementations, the PDSCH / TB transmission / reception may correspond to a configured / semi-persistent PDSCH transmission / reception (e.g., based on SPS-Config and / or when the first DCI activates an SPS PDSCH transmission / reception). For example, the wireless device may determine the HARQ process based on the SPS PDSCH transmission / reception occasion / symbol and / or the SPS-Config and / or the first DCI (activating / triggering) the TB / PDSCH reception.

[0300] For example, the wireless device may (e.g., from the base station, e.g., via the serving cell, receive (e.g., in / within / during a slotm, e.g., m>=n) a second DCI scheduling / indicating a PUSCH transmission in an occasion (e.g., in / within / during a slotp, e.g., p>=m). For example, for the scheduled PUSCH on the serving cell, the wireless device may determine the occasion (e.g , the slot p) based on a reception occasion of the second DCI and / or a 'Time domain resource assignment' field value m indicated by the second DCI (e.g., K2) and / or the scheduling offset (e.g., K0^set=Kceii,offset ~ KUE, offset)’ and / or the NTN-config (e.g., the current TA value of the wireless device). As shown in FIG. 20A and FIG. 20B, the occasion for the PUSCH transmission (e.g., the slot p) may be a PUCCH occasion / resource for transmission of the HARQ-ACK information of the TB / PDSCH (e.g., corresponding to the HARQ process). The wireless device may determine the PUCCH occasion / resource as discussed above in relation to embodiment of FIG. 19, e.g., based on at least one of a PUCCH resource indicator (PRI) of the first DCI and / or a reception occasion / slot of the TB / PDSCH and / or "PDSCH-to-HARQ_feedback timing indicator" filed of the first DCI and / or the scheduling offset (e.g., ^offset - Kceii,offset ~KuE,offset)< and / or the NTN-config (e.g., the current TA value of the wireless device).

[0301] For example, in response to the PUCCH resource / occasion (for transmitting the HARQ-ACK information) overlapping / colliding (in time domain) with at least one symbol of the PUSCH resource / occasion, the wireless device may determine whether to multiplex the HARQ-ACK information in the PUSCH transmission (e.g., based on at least one multiplexing condition being satisfied) or not (e.g., based on at least one multiplexing condition not being satisfied).The wireless device may determine the PUCCH resource / occasion based on the first DCI scheduling / triggering the TB / PDSCH reception.

[0302] FIG. 20A shows an example that the wireless device may multiplex the HARQ-ACK information in the PUSCH transmission (and drop the PUCCH transmission), e.g., in response to the at least one multiplexing condition being satisfied. FIG. 20B shows an example that the wireless device may avoid / skip multiplexing (or not multiplex) the HARQ- ACK information in (or into or on) the PUSCH transmission (and drop the PUCCH transmission), e.g., in response to the at least one multiplexing condition not being satisfied. The rest of the present disclosure may provide various examples for determining whether the at least one multiplexing condition is satisfied or is not satisfied (or whether to multiple the HARQ-ACK information in the PUSCH transmission or not).

[0303] As shown in FIG. 20A, in response to the PUCCH resource / occasion collide in time domain (e.g., in at least one symbol) with the occasion (e.g., PUSCH resource) for transmission of the PUSCH and / or the at least one multiplexing condition being satisfied, the wireless device may multiplex the HARQ-ACK information in the PUSCH transmission (e.g., via rate matching or puncturing or other techniques). For example, the wireless device may determine to multiplex HARQ-ACK information (e.g., ACK / NACK value corresponding to the TB / PDSCH with the enabled HARQ-ACK information) in the PUSCH transmission (and / or determine the at least one multiplexing condition being satisfied) based on a downlink assignment index / indicator / ID (ADI or UL-ADI or a tDAI) field (with value V) of the second DCI and / or HARQ-ACK codebook (e.g., Type-1 / Type-2 HARQ-ACK codebook). In one example, when the one or more configuration parameters configure / indicate the Type-1 (semi-static) HARQ-ACK codebook and the DAI value is one (e.g., V=1 or vY_LDA| = 1), the wireless device may determine to multiplex HARQ-ACK information in the PUSCH transmission (and / or determine the at least one multiplexing condition being satisfied) In another example, when the one or more configuration parameters configure / indicate the Type-2 (semi-static) HARQ-ACK codebook and the DAI value is not equal to 4 (e.g., V<4 or 7^ < 4), the wireless device may determine to multiplex HARQ-ACK information in the PUSCH transmission (and / or determine the at least one multiplexing condition being satisfied). In response to multiplexing the HARQ-ACK information in the PUSCH (and / or the at least one multiplexing condition being satisfied), the wireless device may transmit the PUSCH transmission (comprising the HARQ-ACK information) and drop the transmission of the PUCCH.

[0304] When the one or more configuration parameters configure / indicate the Type-1 (semi-static) HARQ-ACK codebook, = 0 (or V=0) if the PUSCH transmission is scheduled by the second DCI format that includes a DAI field and the DAI field (1 bit) is set to 'O'. \4JLDA| = 1 (or V=1 ) if the PUSCH transmission is scheduled by the second DCI format that includes a DAI field and the DAI field is set to ' 1 '.

[0305] When the one or more configuration parameters configure / indicate the Type-2 (semi-static) HARQ-ACK codebook, the DAI field (e.g., 1 or 2 or 4 bits) may indicate the value of VLDA| (or V).

[0306] As shown in FIG. 20 B, when the one or more configuration parameters configure / indicate the Type-1 (semistatic) HARQ-ACK codebook and the DAI value is zero (e.g., V=0 or= 0), the wireless device may avoid / skip / ignore multiplexing (or determine to not to multiplex) the HARQ-ACK information in the RUSCH transmission (and / or determine the at least one multiplexing condition not being satisfied). In another example, when the one or more configuration parameters configure / indicate the Type-2 (dynamic) HARQ-ACK codebook and the DAI value is equal to 4 (e.g., V=4 or= 4), the wireless device may avoid / skip / ignore multiplexing (or determine not to multiplex) multiplex HARQ-ACK information in the RUSCH transmission (and / or determine the at least one multiplexing condition not being satisfied). In response to not multiplexing the HARQ-ACK information in the RUSCH (and / or the at least one multiplexing condition not being satisfied), the wireless device may transmit the PUSCH transmission (not comprising the HARQ-ACK information) and drop the transmission of the PUCCH (e.g., only in the at least one symbol).

[0307] In some implementations, PUCCH and PUSCH transmissions may be of the same priority index. In other implementations, PUCCH and PUSCH transmissions may be of different priority indexes (e.g., priority index of the PUCCH transmission being smaller than the priority index of the PUSCH transmission or priority index of the PUCCH transmission being greater than the priority index of the PUSCH transmission) For example, the one or more configuration).

[0308] In some examples, for a PUCCH with a first priority index and PUSCH with a second priority index, the one or more configuration parameters may not indicate / configure / provide (or allow) simultaneous transmissions of the PUSCH and PUCCH, e.g., in / during the at least one symbol. In some other examples, fora PUCCH with a first priority index and PUSCH with a second priority index, the one or more configuration parameters may indicate / configure / provide (or allow), e.g., via simultaneousPUCCH-PUSCH, simultaneous transmissions of the PUSCH and PUCCH, e.g., in / during the at least one symbol.

[0309] FIG. 21A, and FIG. 21 B show examples of scenarios that the wireless device may fail / miss detecting / receiving at least one DCI (e.g., comprising the first DCI) during / within / in at least one PDCCH monitoring occasion (e.g., slot n). The wireless device may determine the PUSCH transmission occasion (in the slot p) not overlapping with any PUCCH carrying HARQ-ACK information. For example, the at least one PDCCH monitoring occasion may be prior to / before (or later than) a PDCCH monitoring occasion that the wireless device receives / detects the second DCI (triggering transmission of the PUSCH). The wireless device may (based on failing to detect the first DCI du ring / with i n the at least one PDCCH monitoring occasion) may not be able to determine the PUCCH resource. When the wireless device fails to detect / receive the first DCI during / within the at least one PDCCH monitoring occasion, the wireless device may determine / identify the PUCCH occasion based on the second DCI. As shown in FIG. 21A, and FIG. 21 B, the PUSCH occasion / resource may not collide with the PUCCH resource (as the wireless device is notable to determine the PUCCH resource / occasion due to failure in detecting the first DCI). For example, based on the second DCI indicatingthe DAI value V and the PUSCH occasion, the wireless device may determine the at least one DCI (e.g., the first DCI) being missed (or not being detected) during / within the at least one PDCCH monitoring occasion. In some cases, the one or more configuration parameters may configure at least one slot (e.g., slot p) with PUCCH resources / occasions for possible PUCCH transmissions (e.g., indicated by the first DCI).

[0310] Corresponding to FIG. 21 A and FIG. 21 B, the wireless device may determine the PUSCH transmission (comprising HARQ-ACK information) not overlapping (in time domain) with a PUCCH transmission for the HARQ-ACK information. For example, the wireless device may determine the PUSCH transmission (comprising HARQ-ACK information) not overlapping (in time domain) with a PUCCH transmission for the HARQ-ACK information not corresponding to at least one TB / PDSCH reception.

[0311] Corresponding to FIG. 21 A and FIG. 21 B, although the wireless device fails to detect the first DCI, the wireless device may, based on the second DCI indicating the DAI value V, determine whether to multiplex the HARQ- ACK information into / on the PUSCH transmission or not (or whether the at least one multiplexing condition being satisfied or not). For example, the base station based on indicating the DAI filed in the second DCI allows the wireless device to determine that it may fail / miss detecting the first DCI (e.g., to improve robustness against DCI miss detection).

[0312] As shown in FIG. 21 A, the wireless device may determine the at least one multiplexing condition being satisfied based on: not receiving / detecting (e.g., prior to / before or no later than receiving the second DCI) the at least one DCI (the first DCI) during / within the at least one PDCCH monitoring occasion (scheduling at least one TB / PDSCH); and / or the one or more configuration parameters indicating / configuring a first indication (mux-HARQ-ACK- withoutPUCCH-onPUSCH) enabling / allowing / configuring multiplexing of HARQ-ACK information without PUCCH (resource) on PUSCH transmission; and / or the DAI filed of the second DCI indicating a DAI value smaller than 4 (e.g., when the one or more configuration parameters configure / indicate the Type-2 (dynamic) HARQ-ACK codebook and the DAI value is not equal to 4 (e.g., V<4 or VTLD| < 4); and / or the DAI filed of the second DCI indicating a DAI value equal to 1 (e.g., when the one or more configuration parameters configure / indicate the Type-1 HARQ-ACK codebook and the DAI value is equal to 1 (e.g., V=1 or v .LDA, - 1). The wireless device may multiplex the HARQ information bits with NACK values (e.g., for each PDCCH monitoring occasion of the at least one PDCCH monitoring occasion) in the PUSCH transmission.

[0313] For example, as shown in FIG. 21 B, the wireless device may determine the at least one multiplexing condition not being satisfied based on: not receiving / detecting (e.g., prior to / before or no later than receiving the second DCI) the at least one DCI (the first DCI) during / within the at least one PDCCH monitoring occasion (scheduling the at least one TB / PDSCH); and / or the one or more configuration parameters not indicating / configuring the first indication (mux- HARQ-ACK-withoutPUCCH-onPUSCH); and / or the DAI filed of the second DCI indicating a DAI value equal to 4 (e.g., when the one or more configuration parameters configure / indicate the Type-2 (dynamic) HARQ-ACK codebook and the DAI value is equal to 4 (e.g., V=4 or VTLCA= 4); and / or the DAI filed of the second DCI indicating a DAI value equal to0 (e.g., when the one or more configuration parameters configure / indicate the Type-1 HARQ-ACK codebook and the DAI value is equal to 0 (e.g., V=0 or VTLCA= 0). The wireless device may multiplex the HARQ information bits with NACK values (e.g., for each PDCCH monitoring occasion of the at least one PDCCH monitoring occasion) in the PUSCH transmission. Based on the first indication not being indicated / configured, the wireless device may determine the at least one multiplexing condition not being satisfied (e.g., multiplexing of HARQ-ACK information without PUCCH (resource) on PUSCH transmission not being enabled / indicated / allowed).

[0314] The wireless device may determine the at least one multiplexing condition not being satisfied based on the one or more configuration parameters not providing / indicating / configuring the Type-1 HARQ-ACK codebook (e.g., when the wireless device is not provided pdsch-HARQ-ACK-Codebook = 'semi-static'), e.g., for unicast or multicast HARQ- ACK information.

[0315] Although not shown in FIG. 20A and / or FIG. 20B and / or FIG. 21A and / or FIG. 21 B, in some implementations, the PUSCH transmission may be based on a configured grant configuration (e.g., CG-Config of the one or more configuration parameters), e.g., the PUSCH transmission Isa CG-PUSCH transmission and / or the PUSCH transmission is not scheduled by a DCI format (e.g., the second DCI). For example, the second DCI may activate a Type-2 configured grant configuration. In other implementations (not shown in FIG. 20A and / or FIG. 20B and / or FIG. 21 A and / or FIG. 21 B), the second DCI may not comprise / include a DAI filed.

[0316] When the one or more configuration parameters do not provide / indicate / configure the Type-1 HARQ-ACK codebook (e.g., when the wireless device is not provided pdsch-HARQ-ACK-Codebook = 'semi-static'), e.g., for unicast and / or multicast HARQ-ACK information, and the PUCCH occasion overlaps with the PUSCH transmission (e.g., the CG-PUSCH transmission, e.g., the PUSCH transmission that is not scheduled by a DCI format) or in the PUSCH transmission that is scheduled by the second DCI format that does not include / indicate / comprise a DAI field, the wireless device may determine whether the at least one multiplexing condition being satisfied or not. For example, the at least one multiplexing condition not being satisfied based on the PUCCH resource / occasion (corresponding to the HARQ-ACK information) not being associated with / correspond to at least one of the following: a DCI indicating a SPS PDSCH release; and / or a DCI indicating a TCI state update; and / or receiving at least one SPS-PDSCH reception. In response to receiving at least one SPS-PDSCH or a DCI indicating a SPS PDSCH release or a DCI indicating a TCI state update, the wireless device may determine the PUCCH occasion based on a value of a respective PDSCH-to- HARQJeedback timing indicator field in a DCI format scheduling / triggering / activating the SPS-PDSCH reception or the SPS PDSCH release or the TCI state update, and / or the one or more configuration parameters (e.g., dl-DataToUL-ACK or dl-DataToUL-ACK-r16 or dl-DataToUL-ACK-r17 if the PDSCH-to-HARQ_feedback timing indicator field is not present in DCI format 1_1 or DCI format 1_3; or on the value of dl-DataToUL-ACK-DCI-1 -2 or dl-DataToUL-ACK-DCI-1 -2-r17 if the PDSCH-to-HARQ_feedback timing indicator field is not present in DCI format 1_2; or the value of di - DataToUL- ACK if the PDSCH-to-HARQ_feedback timing indicator field is not present in DCI format 4_2).

[0317] In one example, the at least one multiplexing condition may not be satisfied based on each SPS-PDSCH of the at least one SPS-PDSCH being associated with / correspond to feedback-enabled HARQ process. In another example, the at least one multiplexing condition may not be satisfied based on each SPS-PDSCH of the at least one SPS-PDSCH being associated with / correspond to feedback-disabled HARQ process.

[0318] The at least one multiplexing condition may not be satisfied based on the PUCCH occasion / resource (or the HARQ-ACK information) being only associated / corresponding to receiving onlya SPS PDSCH release, or only the at least one SPS PDSCH reception, or only a PDSCH that is scheduled by DCI format 1_0 with a counter DAI field value of 1 if the UE is provided pdsch-HARQ-ACK-Codebook = 'semi-static' for unicast HARQ-ACK information, or is scheduled by DCI format 4_1 with a counter DAI field value of 1 if the UE is provided pdsch-HARQ-ACK-Codebook = 'semi-static' for multicast HARQ-ACK information.

[0319] For example, when the Type-1 HARQ-ACK codebook (for unicast / multicast HARQ-ACK information) is configured and V=0 (e.g., the DAI filed of the second DCI is 0, e.g ., VTLDA= 0), the wireless device may determine the at least one multiplexing condition being satisfied based on receiving only a SPS PDSCH release, or only unicast SPS PDSCH(s) associated with transport blocks having enabled HARQ-ACK information report, or only a TCI state update, or only receiving a PDSCH that is scheduled by a DCI format 1_0 (e.g., with a counter DAI field value of 1) having enabled associated HARQ-ACK information report, or only receiving multicast SPS PDSCH(s) with transport blocks having enabled associated HARQ-ACK information report or scheduled by a DCI format 4_1 (e.g., with a counter DAI field value of 1) having enabled associated HARQ-ACK information report.

[0320] For pdsch-HARQ-ACK-Codebook = 'semi-static' (e.g., Type-1 HARQ-ACK codebook) for both unicast (e.g., unicast TB / PDSCH) and multicast (e.g., multicast TB / PDSCH) HARQ-ACK information, when the one or more configuration parameters indicate / configure fdmed-Reception Multicast, the wireless device may determine the at least one multiplexing condition being satisfied based on a value VJ.LDA| of the DAI field (e.g., V) associated with the unicast HARQ-ACK information being V^i = 1 and / or a value 7^ of the DAI field associated with the multicast HARQ- ACK information being V^i = 1. For example, the wireless device may, in response to the at least one multiplexing condition being satisfied and / or at least one HARQ-ACK codebook generation condition being satisfied, generate the (multicast / unicast) Type-1 HARQ-ACK codebook (e.g., by replacing harq-ACK-SpatialBundlingPUCCH by / with harq- ACK-SpatialBundlingPUSCH).

[0321] For example, for pdsch-HARQ-ACK-Codebook = 'semi-static' (e.g., Type-1 HARQ-ACK codebook) for both unicast (e.g., unicast TB / PDSCH) and multicast (e.g., multicast TB / PDSCH) HARQ-ACK information, when the one or more configuration parameters indicate / configure fdmed-Reception Multicast, the wireless device may determine the at least one multiplexing condition not being satisfied based on a value 7^ °f the DAI field (e.g., V) associated with theunicast HARQ-ACK information being= 0 and / or a value of the DAI field associated with the multicastHARQ-ACK information being

[0322] Forpdsch-HARQ-ACK-Codebook = 'dynamic' (e.g., Type-2 HARQ-ACK codebook), e.g., for both unicast (e.g., unicast TB / PDSCH) and multicast (e.g., multicast TB / PDSCH) HARQ-ACK information, the wireless device may determine the at least one multiplexing condition not being satisfied based on at least one of the following: the RUSCH transmission not being scheduled by a DCI format (e.g., the second DCI), e.g., the PUSCH transmission is a CG- PUSCH transmission; and / or the PUSCH transmission being scheduled by a DCI format (e.g., the second DCI) not including / comprising a DAI field; and / or not receiving (e.g., prior to / before or no later than the second DCI and within / during PDCCH monitoring occasions) at least one DCI formats scheduling PDSCH / TB receptions; and / or not receiving (e.g., prior to / before or no later than the second DCI and within / during PDCCH monitoring occasions) a DCI format having associated HARQ-ACK information without scheduling a PDSCH reception, e.g., on any serving cell c; and / or receiving (e.g., prior to / before or no later than the second DCI) at least one (all) SPS PDSCH reception corresponding to feedback-disabled HARQ processes; and / or not receiving (e.g., prior to / before or no later than the second DCI) at least one SPS PDSCH reception corresponding to feedback-enabled HARQ processes.

[0323] Forpdsch-HARQ-ACK-Codebook = 'dynamic' (e.g., Type-2 HARQ-ACK codebook), e.g., for both unicast (e.g., unicast TB / PDSCH) and multicast (e.g., multicast TB / PDSCH) HARQ-ACK information (e.g., regardless of whether the one or more configuration parameters configure / indicate / provide PDSCH-CodeBlockGroupTransmission), the wireless device may determine the at least one multiplexing condition not being satisfied based on: the wireless device being scheduled for a PUSCH transmission by DCI format (e.g., the second DCI) that includes / comprises a (or at least one) DAI field for unicast / multicast PDSCH receptions with value VLDA| = 4 (e.g., V=4); and / or the wireless device not receiving, prior to / before / no later than the second Cl and during / within (any) PDCCH monitoring occasions, at least one (unicast / multicast) DCI (format) scheduling / triggering / indicating PDSCH reception(s) providing transport blocks with enabled HARQ-ACK information; and / or the wireless device receiving, prior to / before / no later than the second Cl and during / within (any) PDCCH monitoring occasions, at least one (unicast / multicast) DCI (format) scheduling / triggering / indicating (only) PDSCH reception(s) providing transport blocks with disabled HARQ-ACK information; and / or the wireless device not receiving, prior to / before / no later than the second Cl and during / within (any) PDCCH monitoring occasions, at least one (unicast / multicast) DCI (format) having associated HARQ-ACK information without scheduling PDSCH receptions on any serving cell c; and / or receiving (e.g., prior to / before or no later than the second DCI) at least one (all) SPS PDSCH reception corresponding to feedback-disabled HARQ processes; and / or not receiving (e.g., prior to / before or no later than the second DCI) at least one SPS PDSCH reception corresponding to feedback-enabled HARQ processes.

[0324] Forpdsch-HARQ-ACK-Codebook = 'dynamic' (e.g., Type-2 HARQ-ACK codebook), e.g., for both unicast (e.g., unicast TB / PDSCH) and multicast (e.g., multicast TB / PDSCH) HARQ-ACK information, the wireless device maydetermine the at least one multiplexing condition being satisfied based on at least one of the following: the PUSCH transmission not being scheduled by a DCI format (e.g., the second DCI), e.g., the PUSCH transmission is a CG- PUSCH transmission; and / or the PUSCH transmission being scheduled by a DCI format (e.g., the second DCI) not including / comprising a DAI field; and / or receiving (e.g., prior to / before or no later than the second DCI and within / during PDCCH monitoring occasions) at least one DCI formats scheduling PDSCH / TB receptions; and / or receiving (e.g., prior to / before or no later than the second DCI and within / during PDCCH monitoring occasions) a DCI format having associated HARQ-ACK information without scheduling a PDSCH reception, e.g., on any serving cell c; and / or not receiving (e.g., prior to / before or no later than the second DCI) at least one (all) SPS PDSCH reception corresponding to feedback-disabled HARQ processes; and / or receiving (e.g., prior to / before or no later than the second DCI) at least one SPS PDSCH reception corresponding to feedback-enabled HARQ processes.

[0325] Forpdsch-HARQ-ACK-Codebook = 'dynamic' (e.g., Type-2 HARQ-ACK codebook), e.g., for both unicast (e.g., unicast TB / PDSCH) and multicast (e.g., multicast TB / PDSCH) HARQ-ACK information (e.g., regardless of whether the one or more configuration parameters configure / indicate / provide PDSCH-CodeBlockGroupTransmission), the wireless device may determine the at least one multiplexing condition being satisfied based on: the wireless device being scheduled for a PUSCH transmission by DCI format (e.g., the second DCI) that includes / comprises a (or at least one) DAI field for unicast / multicast PDSCH receptions with value VLDA| < 4 (e.g., V<4 or not equal to 4); and / or the wireless device receiving, prior to / before / no later than the second Cl and during / within (any) PDCCH monitoring occasions, at least one (unicast / multicast) DCI (format) scheduling / triggering / indicating PDSCH reception(s) providing transport blocks with enabled HARQ-ACK information; and / or the wireless device not receiving, prior to / before / no later than the second Cl and during / within (any) PDCCH monitoring occasions, at least one (unicast / multicast) DCI (format) scheduling / triggering / indicating (only) PDSCH reception(s) providing transport blocks with disabled HARQ-ACK information; and / or the wireless device receiving, prior to / before / no later than the second Cl and during / within (any) PDCCH monitoring occasions, at least one (unicast / multicast) DCI (format) having associated HARQ-ACK information without scheduling PDSCH receptions on any serving cell c; and / or not receiving (e.g., prior to / before or no later than the second DCI) at least one (all) SPS PDSCH reception corresponding to feedback-disabled HARQ processes; and / or receiving (e.g., prior to / before or no later than the second DCI) at least one SPS PDSCH reception corresponding to feedback-enabled HARQ processes.

[0326] A wireless device may, in response to the at least one multiplexing condition not being satisfied and / or the at least one HARQ-ACK codebook generation condition being satisfied, generate the (multicast / unicast) Type-1 / Type-2 HARQ-ACK codebook (e.g., by replacing harq-ACK-SpatialBundlingPUCCH by / with harq-ACK- SpatialBundlingPUSCH).

[0327] In an example, e.g., in response to the at least one multiplexing condition not being satisfied, a wireless device may determine whether to generate the (multicast / un icast) Type-1 HARQ-ACK codebook based on the at least one HARQ-ACK codebook generation condition being satisfied.

[0328] Based on the at least one multiplexing condition not being satisfied, the wireless device may avoid / skip / ignore generating / creating / producing / building / constructing (or not generate) a Type-1 HARQ-ACK codebook, e.g., the wireless device may determine the at least one HARQ-ACK codebook generation condition not being satisfied. Based on the at least one multiplexing condition being satisfied, the wireless device may generate (or create or produce or build or construct) the Type-1 HARQ-ACK codebook for multiplexing in the RUSCH transmission (e.g., the wireless device may determine the at least one HARQ-ACK codebook generation condition being satisfied). For example, the wireless device may generate the Type-1 / Type-2 HARQ-ACK codebook using harq-ACK-SpatialBundlingPUSCH.

[0329] In some implementations, in FIG. 20A and FIG. 20B, for transmission of the RUSCH, a wireless device may determine the at least one HARQ-ACK codebook generation condition being satisfied or not. For example, the wireless device may determine the at least one HARQ-ACK codebook generation condition being satisfied based on the at least one multiplexing condition being satisfied. In another example, the wireless device may determine the at least one HARQ-ACK codebook generation condition being satisfied based on at least one of the following: the at least one multiplexing condition not being satisfied; and / or only a unicast or a multicast SPS PDSCH release (indication) being received (e.g., prior to / before receiving the second DCI); and / or only unicast SPS PDSCH(s) or multicast SPS PDSCH(s) having enabled associated HARQ-ACK information reports being received (e.g., prior to / before receiving the second DCI); and / or only a TCI state update being received (e.g., prior to / before receiving the second DCI); and / or a PDSCH with enabled associated HARQ-ACK information report that is scheduled by a DCI format 1_0 or a DCI format 4 J with counter DAI field value of 1 on the PCell being received (e.g., prior to / before receiving the second DCI).

[0330] In yet another example, the wireless device may determine the at least one HARQ-ACK codebook generation condition not being satisfied based on at least one of the following: the at least one multiplexing condition not being satisfied; and / or no unicast and / or multicast SPS PDSCH release (indication) being received (e.g., prior to / before receiving the second DCI); and / or no unicast SPS PDSCH(s) and / or multicast SPS PDSCH(s) having enabled associated HARQ-ACK information reports being received (e.g., prior to / before receiving the second DCI); and / or no TCI state update being received (e.g., prior to / before receiving the second DCI); and / or no PDSCH with enabled associated HARQ-ACK information report that is scheduled by a DCI format 1_0 or a DCI format 4_1 with counter DAI field value of 1 on the PCell being received (e.g., prior to / before receiving the second DCI).

[0331] In yet another example, the wireless device may determine the at least one HARQ-ACK codebook generation condition not being satisfied based on at least one of the following: the at least one multiplexing condition not being satisfied; and / or at least one unicast SPS PDSCH(s) (and / or multicast SPS PDSCH(s)) having disabled associated HARQ-ACK information reports being received (e.g., prior to / before receiving the second DCI); and / or at least one PDSCH with disabled associated HARQ-ACK information report that is scheduled by a DCI format 1_0 or a DCI format4 J with counter DAI field value of not equal to 1 on the PCell being received (e.g prior to / before receiving the second DCI).

[0332] For example, in response to the at least one HARQ-ACK codebook generation condition being satisfied, the wireless device may generate (Type-1 or Type-2) HARQ-ACK codebook (comprising the HARQ-ACK information bit(s)). For example, forpdsch-HARQ-ACK-Codebook = 'semi-static' (e.g., Type-1 HARQ-ACK codebook) for both unicast (e.g., unicast TB / PDSCH) and multicast (e.g., multicast TB / PDSCH) HARQ-ACK information, the HARQ-ACK information bit(s) may correspond to unicast or multicast HARQ-ACK information. For generating the Type-1 HARQ- ACK codebook, the wireless device may set to NACK value in the HARQ-ACK codebook any HARQ-ACK information corresponding to PDSCH reception or SPS PDSCH release or TCI state update that the wireless device detects in a PDCCH monitoring occasion that starts after receiving / detecting the second DCI (e.g., in / during a PDCCH monitoring occasion that the wireless device detects the second DCI format scheduling / activating / triggering the PUSCH transmission).

[0333] In an example embodiment, the wireless device may, after receiving a DCI activating SPS-PDSCH receptions, determine the at least one multiplexing condition being satisfied based on failing to receive (or detect) a first / initial / starting SPS-PDSCH reception of the SPS-PDSCH receptions; the one or more configuration parameters indicating / configuring harq-feedbackEnablingforSPSactive = 'enabled'; and a HARQ process corresponding to the first / initial / starting SPS-PDSCH reception occasion being a feedback-disabled HARQ process. For example, after receiving a DCI activating SPS-PDSCH receptions, the wireless device may, based on the at least one multiplexing condition being satisfied, multiplex a NACK value (corresponding to failing to receive (or detect) a first / initial / starting SPS-PDSCH reception when the one or more configuration parameters indicates / configures harq- feedbackEnabli ngforS PSacti ve = 'enabled' and a HARQ process corresponding to the first / initial / starting SPS-PDSCH reception occasion is the feedback-disabled HARQ process) in the CG-PUSCH transmission.

[0334] If a wireless device is provided / configured with (e.g., via the one or more configuration parameters) pdsch- HARQ-ACK-Codebook = 'semi-static' for unicast and / or multicast HARQ-ACK information, and determine to multiplex HARQ-ACK information in a PUSCH transmission that is not scheduled by a DCI format or is scheduled by a DCI format that does not include a DAI field (e.g., based on the one or more multiplexing condition being satisfied), then if the wireless device is not received any PDSCH, excluding a first / initial / starting SPS-PDSCH reception after an activation of SPS PDSCH receptions, when the transport block in the first SPS-PDSCH has disabled HARQ-ACK information and the wireless device is also provided harq-feedbackEnabli ngforS PSactive = 'enabled1, or SPS PDSCH release or TCI state update that the wireless device multiplexes corresponding HARQ-ACK information in the PUSCH (e.g., based on a value of a respective PDSCH-to-HARQ_feedback timing indicator field in a DCI format scheduling the PDSCH reception or the SPS PDSCH release or the TCI state update, or on the value of dl-DataTo UL-AC K or dl- DataToUL-ACK-r16 or dl-DataToUL-ACK-r17 if the PDSCH-to-HARQ_feedback timing indicator field is not present in DCI format 1_1 or DCI format 1_3, or on the value of dl-DataToUL-ACK-DCI-1-2 or dl-DataToUL-ACK-DCI-1 -2-r17 ifthe PDSCH-to-HARQ_feedback timing indicator field is not present in DCI format 1_2 and the UE is provided pdsch- HARQ-ACK-Codebook = 'semi-static' for unicast HARQ-ACK information, or on the value of dl-DataToU L-AC K if the PDSCH-to-HARQ_feedback timing indicator field is not present in DCI format 4_2 and the UE is provided pdsch- HARQ-ACK-Codebook = 'semi-static' for multicast HARQ-ACK information, in any of the Mcoccasions for candidate PDSCH receptions by a DCI format or SPS PDSCH on any serving cell c), the wireless device may not multiplex HARQ-ACK information in the PUSCH transmission.

[0335] A DAI field of the first DCI may correspond to the unicast HARQ-ACK information (corresponding to unicast PDSCH / TB receptions) or may correspond to the multicast HARQ-ACK information (corresponding to multicast PDSCH / TB receptions.

[0336] In an example, when a wireless device multiplexes aperiodic CSI in the PUSCH transmission comprising HARQ-ACK information, the wireless device may transmit the PUSCH and avoid transmitting (or drop) the PUCCH transmission.

[0337] When a wireless device transmits the PUSCH transmission (scheduled by a DCI format, e.g., the second DCI, that includes a DAI field) over multiple slots, in response to determining the at least one multiplexing condition being satisfied, the value of the DAI field (V) may be applicable for multiplexing HARQ-ACK information in the PUSCH transmission in any slot from the multiple slots where the wireless device may multiplex the HARQ-ACK information.

[0338] The one or more configuration parameters (downlinkH ARQ-FeedbackDisabled) may indicate / configure a disabled HARQ-ACK information for a HARQ process. A wireless device may transmit a Msg A, comprising a preamble / PRACH and / or a PUSCH, of a 2-step RA procedure. In response to the transmission of the Msg A, the wireless device may, after a UE-gNB RTT from the PUSCH transmission of the Msg A, start response window (e.g., msgB-ResponseWindow) for monitoring PDCCH candidates for detecting a DCI format 1_0 with CRC scrambled by a corresponding MsgB-RNTI. In existing technologies, in response to detecting a DCI format 1_0 with CRC scrambled by a C-RNTI, within / during the response window, indicating / scheduling receiving a transport block in a corresponding PDSCH corresponding to the HARQ process, the wireless device may transmit a PUCCH / PUSCH with HARQ-ACK information having ACK value based on the wireless device correctly detects the transport block or NACK value based on the wireless device incorrectly detects the transport block and the time alignment timer is running. Implementation of existing technologies may result in misalignment between the wireless device and the base station during an ongoing 2-step RA procedure. The base station, by disabling the HARQ-ACK information for the HARQ process, may not expect to receive the PUCCH / PUSCH comprising the HARQ-ACK information of the transport block corresponding to the HARQ process. Nevertheless, the implementation of existing technologies may allow the wireless device to incorrectly bypass the one or more configuration parameters (downlinkHARQ-FeedbackDisabled) indicating the disabled HARQ- ACK information for the HARQ process for the transport block during the 2-step RA procedure.

[0339] In an example embodiment, a wireless device may transmit a Msg A, comprising a preamble / PRACH and a PUSCH, of a 2 -step RA procedure. In response to the transmission of the Msg A, the wireless device may, after a UE- gNB RTT from the PUSCH transmission of the Msg A, start response window (e.g., msgB-ResponseWindow) for monitoring PDCCH candidates for detecting a DCI format 1_0 with CRC scrambled by a corresponding MsgB-RNTI. In response to detecting a DCI format 1_0 with CRC scrambled by a C-RNTI, within / during the response window, indicating / scheduling receiving a transport block in a corresponding PDSCH and the one or more configuration parameters (downlinkH ARQ- FeedbackDisabled) indicating a disabled HARQ-ACK information for a HARQ process associated with the transport block in the PDSCH reception, the wireless device may avoid / ignore / transmitting (or not transmit) a HARQ-ACK information bit corresponding to the transport block. In response to detecting a DCI format 1_0 with CRC scrambled by a C-RNTI, within / during the response window, indicating / scheduling receiving a transport block in a corresponding PDSCH and the one or more configuration parameters (downlinkHARQ-FeedbackDisabled) indicating a disabled HARQ-ACK information for a HARQ process associated with the transport block in the PDSCH reception, the wireless device may not transmit the HARQ-ACK information (e.g., via PUCCH / PUSCH) corresponding to the transport block. In response to detecting a DCI format 1_0 with CRC scrambled by a C-RNTI, within / during the response window, indicating / scheduling receiving a transport block in a corresponding PDSCH and the one or more configuration parameters (downlinkHARQ-FeedbackDisabled) indicating an enabled HARQ-ACK information fora HARQ process associated with the transport block in the PDSCH reception, the wireless device may transmit a HARQ- ACK information bit corresponding to the transport block based on decoding result / outcome of the transport block (e.g., ACK value when the transport block is successfully decoded and NACK value when the transport block is unsuccessfully decoded).

[0340] In an example embodiment, a wireless device may transmit a Msg A, comprising a preamble / PRACH, of a 2- step RA procedure. In response to the transmission of the Msg A, the wireless device may, after a UE-gNB RTT from a PUSCH occasion mapped to a PRACH occasion of the Msg A, start response window (e.g., msgB-ResponseWindow) for monitoring PDCCH candidates for detecting a DCI format 1_0 with CRC scrambled by a corresponding MsgB-RNTI. In response to detecting a DCI format 1_0 with CRC scrambled by a C-RNTI, within / during the response window, indicating / scheduling receiving a transport block in a corresponding PDSCH and the one or more configuration parameters (downlinkHARQ-FeedbackDisabled) indicating a disabled HARQ-ACK information for a HARQ process associated with the transport block in the PDSCH reception, the wireless device may avoid / ignore / transmitting (or not transmit) a HARQ-ACK information bit corresponding to the transport block. In response to detecting a DCI format 1_0 with CRC scrambled by a C-RNTI, within / during the response window, indicating / scheduling receiving a transport block in a corresponding PDSCH and the one or more configuration parameters (downlinkHARQ-FeedbackDisabled) indicating an enabled HARQ-ACK information for a HARQ process associated with the transport block in the PDSCH reception, the wireless device may transmit a HARQ-ACK information bit corresponding to the transport block based ondecoding result / outcome of the transport block (e.g . , ACK value when the transport block is successfully decoded and NACK value when the transport block is unsuccessfully decoded).

[0341] FIG. 22A and FIG. 22B show examples of DRX operation with feedback-enabled HARQ processes in a nonterrestrial network. FIG. 23A illustrates an example of DRX operation with a HARQ process with HARQ mode A in a non-terrestrial network. FIG. 23B illustrates an example of DRX operation with a HARQ process with HARQ mode B in a non-terrestrial network. For example, embodiments of FIG. 22A and FIG. 22B and / or FIG. 23A and FIG. 23B demonstrate impact of HARQ operation (e.g., transmission of HARQ-ACK information via / using PUCCH / PUSCH as discussed above in combination with FIG. 19 and / or FIG. 20A and / or FIG. 20B and / or FIG. 21A and / or FIG. 21 B) on the DRX operation, e.g., how the HARQ operation impact DRX active time (e.g., PDCCH monitoring) of the DRX operation (or configuration).

[0342] The one or more configuration parameters may comprise one or more DRX configuration parameters (e.g., DRX-Config). The one or more DRX configuration parameters may configure the wireless device with DRX operation. In an example, the one or more DRX configuration parameters may configure / control PDCCH monitoring or the DRX active time of the DRX operation. For example, when in an RRC_CONNECTED state, if the DRX operation is configured (e.g., the DRX is configured or a DRX cycle is configured), for all the activated Serving Cells (e.g., the serving cell), the MAC entity of the wireless device may monitor the PDCCH discontinuously using the DRX operation. Otherwise, the MAC entity may monitor the PDCCH continuously. The DRX configuration may be a UE-specific (or UE- based) DRX configuration. The DRX configuration may be a cell-specific (or cell-based) DRX configuration. The DRX configuration may be for unicast or multicast UL / DL transmissions.

[0343] Under / using the DRX operation, a wireless device may use the DRX configuration while communicating with the base station in the serving cell. For example, a MAC entity (or the MAC layer) of the wireless device, when using the DRX operation, may control the PDCCH monitoring activity of the MAC entity, e.g., the wireless device may monitor the PDCCH for at least one RNTI corresponding to the DRX operation. The at least one RNTI may comprise one or more of the following: C-RNTI, cancelation indication RNTI (CI-RNTI), configured scheduling RNTI (CS-RNTI), interruption RNTI (INT-RNTI), slot format indication RNTI (SFI-RNTI), semi-persistent channel state information RNTI (SP-CSI-RNTI), transmit power control physical uplink control channel RNTI (TPC-PUCCH-RNTI), transmit power control physical shared channel RNTI (TPC-PUSCH-RNTI), transmit power control sounding reference signal RNTI (TPC-SRS-RNTI), or availability indicator RNTI (AI-RNTI).

[0344] The one or more DRX configuration parameters may comprise: DRX on duration timer / period / window (e.g., drx-on DurationTi mer) indicating a duration at the beginning of a DRX cycle, drx-SlotOffset indicating a delay before starting the DRX on duration timer, DRX inactivity timer / period / window (e.g., drx-lnactivity Timer) indicating a duration after a PDCCH occasion in which the PDCCH indicates a new UL or DL transmission for the MAC entity, DRX retransmission timer of DL (e.g., drx-RetransmissionTimerDL), per DL HARQ process except for the broadcast process, indicating a maximum duration until a DL retransmission is received, DRX retransmission timer of UL (e.g., drx-RetransmissionTimerUL), per UL HARQ process, indicating a maximum duration until a grant for UL retransmission is received, drx-Long CycleStartOffset indicating a Long DRX cycle and drx-StartOffset which defines a subframe where a Long and Short DRX cycle starts, drx-ShortCycle for a Short DRX cycle, drx-ShortCycleTimer indicating a duration the wireless device may follow the Short DRX cycle, drx-HARQ-RTT-TimerDL (per DL HARQ process except for the broadcast process) indicating a minimum duration before a DL assignment for HARQ retransmission is expected by the MAC entity, drx-HARQ-RTT-TimerUL (per UL HARQ process) indicating a minimum duration before an UL HARQ retransmission grant is expected by the MAC entity.

[0345] In an example, the one or more DRX configuration parameters may configure the Serving Cells (e.g., the serving cell) two DRX groups with separate DRX parameters. When a secondary DRX group is not configured, there may be only one DRX group (e.g., a DRX group) and the Serving Cells (e.g., the serving cell) may belong to the DRX group. When the two DRX groups are configured (e.g., the DRX group and a second DRX group), each Serving Cell (e g., the serving cell) is uniquely assigned (or belongs) to either of the DRX group or the second DRX group. The DRX configuration parameters that are separately configured for each DRX group are: the DRX on duration timer (e.g., the drx-onDurationTimer) and / or the DRX inactivity timer (e.g., the drx-lnactivityTimer). The one or more DRX configuration parameters that are common to the two DRX groups are: drx-SlotOffset, drx-RetransmissionTi merDL, drx- RetransmissionTi merU L, drx-LongCycleStartOffset, drx-ShortCycle (optional), drx-ShortCycleTimer (optional), drx- HARQ-RTT-TimerDL, and drx-HARQ-RTT-TimerUL.

[0346] For example, when the DRX operation is configured, the wireless device may be in an on duration of the DRX operation (e.g., a DRX on duration) or an off duration of the DRX operation (e.g., a DRX off duration). For example, the DRX on duration may start based on starting the DRX on duration timer / period. For example, when the wireless device is not in the DRX on duration, the wireless device may be in the DRX off duration (e.g , outside of the DRX on duration). For example, the DRX off duration may stop based on starting the DRX on duration timer. For example, the wireless device may switch / transit from the DRX on duration to the DRX off duration based on stopping the DRX on duration timer. For example, the wireless device may switch / transit from the DRX off duration to the DRX on duration based on starting the DRX on duration.

[0347] In an example, when the DRX operation is configured, the wireless device may determine whether the wireless device is in an active time (or a DRX active state or Active Time) of the DRX operation. For example, the active time of the DRX operation may specify the active time for the serving cell (or the Serving Cells) in the DRX group. For example, the wireless device may determine that the active time of the DRX operation (e.g., the active time for the serving cell in the DRX group) comprises the DRX on duration.

[0348] For example, the wireless device may determine that the active time for the serving cell in the DRX group comprises the time while: the DRX on duration timer (e.g., drx-onDurationTimer) or the DRX inactivity timer (e.g., drx- lnactivityTimer) configured for the DRX group is running; or the DRX retransmission timer of DL (e.g., drx-RetransmissionTimerDL) or the DRX retransmission timer of the UL (e.g., drx-RetransmissionTimerUL) is running onany of the Serving Cells (e.g. , the serving cell) in the DRX group; or a contention resolution timer (e.g., ra- ContentionResolutionTimer) or a message B (MsgB) response window (e.g., msgB-ResponseWindow) is running; ora scheduling request (SR) is sent / transmitted on PUCCH and is pending; or a PDCCH indicating a new transmission addressed to the C-RNTI not being received after successful reception of a random access response (RAR) for a Random Access Preamble (or a preamble 1311 / 1321 / 1341) that is not selected by the MAC entity among the contention-based Random Access Preamble(s); and / or there is an ongoing RACH-less LTM cell switch; and / or there is an ongoing RACH-less handover (e.g., in an NTN). If the Serving Cell is part of a non-terrestrial network, the DRX active time (or Active time) may start after the Scheduling Request transmission that is performed when the SR_COUNTER is 0 for all the SR configurations with pending SR(s) plus the UE-gNB RTT.

[0349] For example, when the wireless device is outside the active time for the serving cell in the DRX group, the wireless device may be in a DRX inactive state / time (or a DRX non-active time or a DRX non-active state). When the wireless device is in the DRX inactive state / time, the wireless device may not monitor the PDCCH candidates (with / during the PDCCH monitoring occasion) for / using / based on the at least one RNTI. For example, when the wireless device is in the active time for the serving cell in the DRX group, the wireless device may be in the DRX active state / time. When the wireless device is in the DRX active state / time, the wireless device may monitor the PDCCH candidates (with / during the PDCCH monitoring occasion) for / using / based on the at least one RNTI.

[0350] As shown in FIG. 22A and FIG. 22B and FIG. 23A and FIG. 23B, when the wireless device is in the DRX active time (e.g., when a DRX group is in Active Time), the wireless device may monitor the PDCCH (candidates) on the Serving Cells in the DRX group, e.g., for the at least one RNTI.

[0351] In the example of FIG. 22A and FIG. 22B, during the DRX active time / state, e.g., based on a drx timer (e.g., a drx-RetransmissionTimerDL / drx-RetransmissionTimerUL corresponding to a HARQ process and / or a drx on duration timer or a drx inactivity timer) being running, the wireless device may receive / detect a first DCI (DC1 1 or a first PDCCH). For example, while the drx timer is running the wireless device may monitor PDCCH (monitor PDCCH candidates) based on / using the at least one RNTI. The first DCI may indicate / schedule / trigger / activate a TB / PDSCH reception (or at least one TB / PDSCH), e.g., the first DCI / PDCCH indicates a (new) DL (re-)transmission. For example, the first DCI may (via a 'HARQ process number1field) indicate a HARQ process of the first plurality of HARQ processes corresponding to TB / PDSCH reception. The TB / PDSCH may comprise at least one repetition. For example, the TB may comprise a MAC PDU.

[0352] Although FIG. 22A and FIG. 22B show examples that the TB / PDSCH reception is scheduled / triggered by the first DCI (e.g., TB / PDSCH is received based on a dynamic DL assignment indicated by the first DCI), embodiments of FIG. 22A and FIG. 22B may equally be applicable for the case that the wireless device the wireless device may receive the TB / PDSCH based on the SPS-Config, e.g., TB is received in / during an SPS-PDSCH reception. For example, the wireless device may receive the TB / PDSCH based on a configured (or semi-persistent) DL assignment (e.g., SPS- PDSCH). When the TB / PDSCH reception is the SPS-PDSCH reception (e.g., based on the SPS configuration), thewireless device may determine the HARQ process based on the time domain resources of the SPS-PDSCH reception (e.g., slot / symbol of the SPS-PDSCH reception).

[0353] Based on the serving cell being configured with downlinkHARQ-FeedbackDisabled (e.g. , via the one or more configuration parameters) and / or a corresponding HARQ process of the TB / PDSCH being with HARQ feedback enabled (e.g., the TB / PDSCH being associated with the feedback-enabled HARQ process), the wireless device may set / initialize a HARQ-RTT-TimerDL-NTN for the corresponding HARQ process (of the TB / PDSCH) equal to a drx- HARQ-RTT-TimerDL (corresponding to the DRX configuration or the DRX operation) plus a latest / most recent available UE-gNB RTT value (RTT). After setting the HARQ-RTT-TimerDL-NTN (e.g., for the corresponding HARQ process), the wireless device may start the HARQ-RTT-TimerDL-NTN (e.g., for the corresponding HARQ process) in a first / starting / earliest / initial symbol after an end of the corresponding transmission carrying the DL HARQ feedback. For example, as shown in FIG. 22A, the wireless device may start the HARQ-RTT-TimerDL-NTN for the corresponding HARQ process after a (last / final / ending) symbol of PUCCH / PUSCH comprising the HARQ-ACK information. In the examples of FIG. 22A, the HARQ-ACK information bit is / comprises a NACK value based on not receiving (or not successfully decoding) the TB / PDSCH scheduled by the first DCI. In the examples of FIG. 22B, the HARQ-ACK information bit is / comprises an ACK value based on successfully decoding / receiving the TB / PDSCH scheduled by the first DCI. As shown in FIG. 22A and FIG. 22B, based on receiving the first DCI, the wireless device may stop the drx- RetransmissionTimerDL for the corresponding HARQ process (or for at least one HARQ process whose HARQ feedback is reported). Based on receiving the first DCI, the wireless device may start / restart the drx inactivity timer of the DRX operation.

[0354] In the examples of FIG. 22A, based on an expiry of the HARQ-RTT-TimerDL-NTN (e.g., for the corresponding HARQ process) and / or the TB / PDSCH (e.g., data of the corresponding HARQ process) not being successfully decoded (or failing to successfully decoding the TB / PDSCH), the wireless device may start the drx-RetransmissionTimerDL for the corresponding HARQ process in a first / initial / starting symbol after symbol after the expiry of HARQ-RTT-TimerDL- NTN. While the drx-RetransmissionTimerDL (e.g., for the corresponding HARQ process) is running, the wireless device may monitor PDCCH candidates (in / during the PDDCH monitoring occasions) based on the at least one RNTI. For example, While the drx-RetransmissionTimerDL (e.g., for the corresponding HARQ process) is running, the wireless device may receive a second DCI (DCI 2 in FIG. 22A) indicating a retransmission of the TB / PDSCH (e.g., NDI filed of the second DCI not being toggled) corresponding to the feedback-enabled HARQ process (that is indicated by the first DCI). As shown in FIG. 22A, the wireless device may receive the retransmission of the TB / PDSCH scheduled by the second DCI (via the serving cell).

[0355] In the examples of FIG. 22B, based on an expiry of the HARQ-RTT-TimerDL-NTN (e.g., for the corresponding HARQ process) and / or the TB / PDSCH (e.g., data of the corresponding HARQ process) being successfully (or correctly) decoded, the wireless device may avoid starting (or not start) the drx-RetransmissionTimerDL for the corresponding HARQ process.

[0356] Based on the serving cell being configured with downlinkHARQ-FeedbackDisabled (e.g. , via the one or more configuration parameters) and / or the corresponding HARQ process of the TB / PDSCH being with HARQ feedback disabled (e.g., the TB / PDSCH being associated with the feedback-disabled HARQ process), the wireless device may avoid / skip setting / initializing (or not set / initialize) the HARQ-RTT-TimerDL-NTN for the corresponding HARQ process (of the TB / PDSCH). For example, based on the serving cell being configured with downlinkHARQ-FeedbackDisabled (e.g., via the one or more configuration parameters) and / or the corresponding HARQ process of the TB / PDSCH being with HARQ feedback disabled (e.g., the TB / PDSCH being associated with the feedback-disabled HARQ process), the wireless device may avoid / skip starting (or not start) the HARQ-RTT-TimerDL-NTN (e.g., for the corresponding HARQ process) in a first / starting / earliest / initial symbol after an end of the corresponding transmission carrying the DL HARQ feedback (e.g., regardless of whether the DL HARQ feedback, e.g., HARQ-ACK information, is NACK or ACK).

[0357] For example, based on the serving cell being configured with downlinkHARQ-FeedbackDisabled (e.g., via the one or more configuration parameters) and / or the corresponding HARQ process of the TB / PDSCH being with HARQ feedback disabled (e.g., the TB / PDSCH being associated with the feedback-disabled HARQ process), the wireless device may avoid start / restarti ng (or not start) the drx-HARQ-RTT-TimerDL for the corresponding HARQ process in a first / starting / earliest / initial symbol after the end of the corresponding transmission carrying the DL HARQ feedback (e.g., after a last / final / ending symbol of PUCCH / PUSCH comprising the HARQ-ACK information). In an example embodiment, based on the serving cell being configured with downlinkHARQ-FeedbackDisabled (e.g., via the one or more configuration parameters) and / or the corresponding HARQ process of the TB / PDSCH being with HARQ feedback disabled (e.g., the TB / PDSCH being associated with the feedback-disabled HARQ process), the wireless device may avoid stopping (or not stop) the drx-HARQ-RTT-TimerDL for the corresponding HARQ process in response to receiving the first DCI. When the corresponding HARQ process of the TB / PDSCH is with HARQ feedback disabled (e.g., the TB / PDSCH being associated with the feedback-disabled HARQ process), the wireless device may receive a second DCI (indicating retransmission of the TB / PDSCH) while the drx inactivity timer of the DRX operation is running.

[0358] Based on the serving cell not being configured with downlinkHARQ-FeedbackDisabled (e.g., via the one or more configuration parameters), the wireless device may start / restart the drx-HARQ-RTT-TimerDL for the corresponding HARQ process in a first / starti ng / earl iest / i nitial symbol after the end of the corresponding transmission carrying the DL HARQ feedback (e.g., after a last / final / ending symbol of PUCCH / PUSCH comprising the HARQ-ACK information).

[0359] In the example of FIG. 23A and FIG. 23B, the first DCI may indicate / schedule / trigger / activate a TB / PUSCH transmission (or at least one TB / PUSCH transmission), e.g., the first DC l / PDCC H indicates a (new) UL (retransmission. For example, the first DCI may (via a 'HARQ process number1field) indicate a HARQ process of the second plurality of HARQ processes corresponding to TB / PUSCH transmission. The TB / PUSCH may comprise at least one repetition. For example, the TB may comprise a MAC PDU. Although FIG. 23A and FIG. 23B show examples that the TB / PUSCH transmission is scheduled / triggered by the first DCI (e.g., TB / PDSCH is transmitted based on adynamic UL grant indicated by the first DC I), embodiments of FIG. 23A and FIG. 23B may equally be applicable for the case that the wireless device may transmit the TB / PDSC H based on the configured grant configuration, e.g. , TB is transmitted in / during CG-PUSCH transmission occasion of the CG configuration. For example, the wireless device may transmit the TB / PDSCH based on a configured UL assignment (e.g., CG-PUSCH). When the TB / PUSCH transmission is the CG-PUSCH transmission (e.g., based on the CG configuration), the wireless device may determine the HARQ process based on the time domain resources of the CG-PUSCH transmission (e.g., slot / symbol of the CG-PUSCH transmission).

[0360] The one or more configuration parameters (e.g., IE PUSCH-ServingCellConfig) may configure a wireless device with a second plurality of HARQ processes (e.g., nrofHARQ-ProcessesForPUSCH), e.g., for transmitting PUSCHs / TBs in UL of a serving cell. When nrofHARQ-ProcessesForPUSCH is absent from the one or more configuration parameters (e.g., IE PUSCH-ServingCellConfig), a number of the second plurality of HARQ processes may be 8 or 4 or 12 or the like (e.g., a default / predefined value).

[0361] The one or more configuration parameters may configure / indicate (e.g., via uplinkHARQ-Mode) whether a (UL) HARQ process of the second HARQ processes is with a HARQmodeA or HARQmodeAB. For example, uplinkHARQ-Mode may indicate / provide configuration to set HARQmodeA or HARQmodeB per (UL) HARQ process of the second plurality of HARQ processes.

[0362] When a HARQ mode of a HARQ process (of the second plurality of HARQ processes) is set to HARQmodeA (as shown in FIG. 23A), the wireless device determine the base station may retransmit a TB / PUSCH corresponding to the HARQ process based on decoding result of the TB / PUSCH at the base station, e.g., the base station may wait to receive the TB / PUSCH from the wireless device and then schedule a retransmission of the TB / PUSCH by the wireless device if the TB / PUSCH is unsuccessfully decoded (e.g., non-blind retransmission of the TB / PUSCH).

[0363] When a HARQ mode of a HARQ process (of the second plurality of HARQ processes) is set to HARQmodeB (as shown in FIG. 23B), the wireless device determine the base station may retransmit a TB / PUSCH corresponding to the HARQ process regardless of decoding result of the TB / PUSCH at the base station, e.g., the base station may not wait to receive the TB / PUSCH from the wireless device to schedule a retransmission of the TB / PUSCH by the wireless device (e.g., blind retransmission of the PUSCH / TB).

[0364] FIG. 23A and FIG. 23B show examples of DRX operation when the uplinkHARQ-Mode is configured.

[0365] As shown in FIG. 23A, based on the serving cell being configured with uplinkHARQ-Mode (e.g., via the one or more configuration parameters) and / or a corresponding HARQ process of the TB / PUSCH transmission being configured as / with HARQmodeA (e.g., the TB / PUSCH being associated with a HARQ process with mode HARQmodeA), the wireless device may set / initialize a HARQ-RTT-TimerUL-NTN for the corresponding HARQ process (of the TB / PUSCH) equal to a drx-HARQ-RTT-TimerUL (corresponding to the DRX configuration or the DRX operation) plus a latest / most recent available UE-gNB RTT value (RTT). After setting the HARQ-RTT-TimerUL-NTN (e.g., for the corresponding HARQ process), the wireless device may start the HARQ-RTT-TimerUL-NTN (e.g., for thecorresponding HARQ process) in a first / starting / earliest / initial transmission of the TB / PUSCH (e.g., within a bundle of transmissions / repetitions and if drx-LastTransmissionUL is configured via the one or more configuration parameters) or in a last / final / ending / latest transmission of the TB / PUSCH (e.g., within a bundle of transmissions / repetitions and if drx- LastTransmissionUL is not configured via the one or more configuration parameters). For example, as shown in FIG. 23A, the wireless device may start the HARQ-RTT-TimerUL-NTN for the corresponding HARQ process after a (last / final / ending) symbol of PUSCH comprising the TB / MAC PDU. As shown in FIG. 23A and FIG. 23B, based on receiving the first DCI, the wireless device may stop the drx-RetransmissionTimerUL for the corresponding HARQ process.

[0366] In the examples of FIG. 23A, based on an expiry of the HARQ-RTT-TimerUL-NTN (e.g., for the corresponding HARQ process with HARQmodeA), the wireless device may start the drx-RetransmissionTimerUL for the corresponding HARQ process in a first / initial / starting symbol after symbol after the expiry of HARQ-RTT-TimerUL-NTN. While the drx- RetransmissionTimerUL (e.g., for the corresponding HARQ process) is running, the wireless device may monitor PDCCH candidates (in / during the PDDCH monitoring occasions) based on the at least one RNTI. For example, while the drx-RetransmissionTimerUL (e.g., for the corresponding HARQ process) is running, the wireless device may receive a second DCI (DCI 2 in FIG. 23A) indicating a retransmission of the TB / PUSCH (e.g., NDI filed of the second DCI not being toggled) corresponding to the HARQ process with the HARQmodeA (that is indicated by the first DCI). For example, the base station may transmit the second DCI to the wireless device based on unsuccessfully decoding / receiving the PUSCH / TB. As shown in FIG. 23A, the wireless device may transmit the retransmission of the TB / PUSCH scheduled by the second DCI (via the serving cell).

[0367] As shown in FIG. 23B, based on the serving cell being configured with uplinkHARQ-Mode (e.g., via the one or more configuration parameters) and / or a corresponding HARQ process of the TB / PUSCH transmission being configured as / with HARQmodeB (e.g., the TB / PUSCH being associated with a HARQ process with mode HARQmodeB), the wireless device may avoid / skip setting / initializing (or not set / initialize) a HARQ-RTT-TimerUL-NTN for the corresponding HARQ process (of the TB / PUSCH). For example, based on the serving cell being configured with uplinkHARQ-Mode (e.g., via the one or more configuration parameters) and / or a corresponding HARQ process of the TB / PUSCH transmission being configured as / with HARQmodeB (e.g., the TB / PUSCH being associated with a HARQ process with mode HARQmodeB), the wireless device may avoid / skip starting (or not start) the HARQ-RTT-TimerUL- NTN for the corresponding HARQ process (of the TB / PUSCH).

[0368] Based on the serving cell being configured with uplinkHARQ-Mode (e.g., via the one or more configuration parameters) and / or a corresponding HARQ process of the TB / PUSCH transmission being configured as / with HARQmodeB (e.g., the TB / PUSCH being associated with a HARQ process with mode HARQmodeB), the wireless device may avoid / skip / ignore starting / restarting (or not start) the drx-RetransmissionTimerUL for the corresponding HARQ process (of the TB / PUSCH). When the corresponding HARQ process of the TB / PUSCH is with theHARQmodeB, the wireless device may receive a second DCI (indicating retransmission of the TB / PUSCH) while thedrx inactivity timer of the DRX operation is running. For example, the base station may transmit the second DCI to the wireless device before receiving the receiving the PUSCH / TB from the wireless device (e.g., transmitting the second DCI indicating retransmission of the PUSCH / TB may not be based on the decoding result / outcome of the PUSCH / TB at the base station).

[0369] For example, based on the serving cell not being configured with upli nkH ARQ-Mode (e.g. , via the one or more configuration parameters), the wireless device may start the HARQ-RTT-TimerUL (e.g., for the corresponding HARQ process) in a first / starting / earliest / initial transmission of the TB / PUSCH (e.g., within a bundle of transmissions / repetitions and if drx-LastTransmissionUL is configured via the one or more configuration parameters) or in a last / final / ending / latest transmission of the TB / PUSCH (e.g., within a bundle of transmissions / repetitions and if drx- LastTransmissionUL is not configured via the one or more configuration parameters).

[0370] FIG. 24 shows an example of UL / DL HARQ operation in a non-terrestrial network. Embodiment of FIG. 24 may correspond to a combination of embodiments of FIG. 19 and / or FIG. 20A. For example, a wireless device may receive a first PDSCH (from a base station via a serving cell of an NTN). The first PDSCH (or TB) may correspond to a first HARQ process (of the first plurality of HARQ processes). The first HARQ process may be a feedback-enabled HARQ process. The wireless device may generate a HARQ-ACK information corresponding to the first PDSCH (or the first HARQ process). The first PDSCH may be an SPS-PDSCH or a PDSCH scheduled by a first DCI (not shown in FIG. 24).

[0371] As shown in FIG. 24, the wireless device may receive (e.g., in / within / during a slot q) a second DCI scheduling / indicating / triggering / activating a PUSCH transmission from the base station, e.g., via the serving cell of the NTN. The second DCI may schedule the PUSCH transmission in an occasion (e.g., in / within / during a slotp, e.g., p>=q). For example, the second DCI may indicate a DAI value V (via a DAI filed of the second DCI). In some other cases (not shown in FIG. 24) the second DCI may not indicate the DAI value (e.g., the second DCI may not have a DAI field). The wireless device may determine the occasion (e.g., slot p) overlaps / collides (in time domain, e.g., in at least one symbol) with a PUCCH occasion / resource for transmission of HARQ-ACK information (e.g., corresponding to the first PDSCH). For the scheduled PUSCH on the serving cell, the wireless device may determine the occasion (e.g., the slot p) based on a reception occasion of the second DCI (e.g., a last / ending / final / lates symbol of the slot m) and / or a 'Time domain resource assignment' field value m indicated by the second DCI (e.g., K2) and / or the scheduling offset (e.g., KOffSet= KceuiOffSet- KUEoffSet), and / or the NTN-config (e.g., the current TA value of the wireless device). For example, a difference (e.g., in number of slots / symbols / subframes or in unit of milliseconds) between the reception of the second DCI (or the last symbol of the second DCI), e.g., in the slot m, and the PUSCH transmission occasion (e.g., slot m) may be the first timing gap. The wireless device may determine the first timing gap based on the 'Time domain resource assignment' field value m indicated by the second DCI (e.g., K2) and / or the scheduling offset (e.g.,Offset = een, off set ~ ^UE, offset)> and / or the NTN-config (e.g., the current TA value of the wireless device). For example, the first timing gap may be Koffset+ K2- TA.

[0372] For example, the occasion for the PUSCH transmission (e.g., the slot p) may be a PUCCH occasion / resource for transmission of the HARQ-ACK information of the first TB / PDSCH (e.g., corresponding to the first HARQ process). The wireless device may determine the PUCCH occasion / resource as discussed above in relation to embodiment of FIG. 19, e.g., based on at least one of a PUCCH resource indicator (PRI) of the first DCI (e.g., scheduling / indicating the first PDSCH / TB) and / or a reception occasion / slot of the first TB / PDSCH and / or "PDSCH-to-HARQ_feedback timing indicator" filed of the first DCI and / or the scheduling offset (e.g., KOffset= Kceil 0^set- KUEfiffset), and / or the NTN-config (e.g., the current TA value of the wireless device). In response to the PUCCH resource / occasion (for transmitting the HARQ-ACK information) overlapping / colliding (in time domain) with at least one symbol of the PUSCH resource / occasion, the wireless device may determine to multiplex the HARQ-ACK information (corresponding to the first PDSCH) in the PUSCH transmission (e.g., based on at least one multiplexing condition being satisfied).

[0373] As shown in FIG. 24, e.g., when the one or more configuration parameters configure / indicate the Type-2 HARQ-ACK codebook, the wireless device may, after the receiving the second DCI and prior to / before the PUSCH transmission (e.g., during the first timing gap), not expect to detect / receive a DCI format (e.g., a third DCI) scheduling a second PDSCH / TB reception or having associated HARQ-ACK information report without scheduling a third PDSCH reception, and indicating a resource for a PUCCH transmission with corresponding the HARQ-ACK information (e.g., comprising / carrying the HARQ-ACK information) in the slot p. For example, in response to receiving the third DCI during the first timing gap, the wireless device may discard the third DCI (e.g., consider the third DCI inapplicable or error) based on the third DCI scheduling the second PDSCH reception or having associated HARQ-ACK information report without scheduling a third PDSCH reception; the third DCI indicating the resource for the PUCCH transmission with corresponding the HARQ-ACK information (e.g., comprising / carrying the HARQ-ACK information) in the slot p; the at least one multiplexing condition being satisfied (e.g., the PUSCH transmission comprises the HARQ-ACK information); and / or the one or more configuration parameters configuring / indicating the Type-2 HARQ-ACK codebook.

[0374] In existing technologies, the base station may not transmit the third DCI, e.g., after transmitting the second DCI and prior to receiving the PUSCH transmission (e.g., during a first duration / window), to the wireless device. This allows the wireless device to correctly determine, e.g., when receiving the second DCI and / or before Tproc2 after receiving the second DCI, a size of a Type-2 HARQ-ACK codebook (and resources for the HARQ-ACK information) for multiplexing in the PUSCH transmission. The base station may, by not transmitting the third DCI to the wireless device, e.g., after transmitting the second DCI and prior to receiving the PUSCH transmission (e.g., during the first duration / window), reduces complexity of the wireless device and / or misalignment between the wireless device and the base station. Compared to an NTN with a large propagation delay (e.g., 10-600 ms), in a terrestrial network (e.g., with at most 1 ms propagation delay), the first duration may be short (e.g., at most K2 slots / ms). Compared to an NTN witha large propagation delay (e.g., 10-600 ms), in a terrestrial network (e.g., with at most 1 ms propagation delay), the first duration may be (almost) equal to the first timing gap, e.g., there may not be misalignment between the wireless device and the base station.

[0375] In existing technologies, in an NTN with a large propagation delay (e.g., 10-600 ms), due to scheduling restriction(s) at the base station (as discussed above in relation to FIG. 24), e.g., by not transmitting the third DCI to the wireless device, e.g., after transmitting the second DCI and prior to receiving the PUSCH transmission (e.g., during the first duration / window), spectral efficiency / data rate of the wireless device may reduce. In existing technologies, in an NTN with a large propagation delay (e.g., 10-600 ms), there may be misalignment between the wireless device and the base station, e.g., as the first duration / window is much larger than the first timing gap (e.g., first duration > RTT + first timing gap), and / or as the base station may not determine the first time gap (e.g., the base station may not determine correctly / accurately when the wireless device transmits the PUSCH, e.g., the base station may not be aware of the TA value of the wireless device).

[0376] For example, even when the first window / duration (or a length of the first window) is (almost) equal to the first timing gap (e.g., when the base station is aware of the TA value of the wireless device, e.g., when the wireless device reports / transmits TA value to the base station, e.g., via the TA report procedure), the first timing gap may substantially be larger than a maximum value of K2, e.g., 15 slots, (e.g., which indicates a maximum length of the first duration in a terrestrial network), e.g., when the base station does not indicate the differential Koffset to the wireless device. When the base station is aware of the TA value of the wireless device (e.g., when the wireless device reports / transmits TA value to the base station, e.g., via the TA report procedure) and / or when the wireless device is not indicated the differential Koffset, the first timing gap may be at least Kcell,offset-TA, which depending on the location of the wireless device in the serving cell, may be at most 30 slots. Therefore, the first timing gap may be at most 30 slots / ms larger / greater than a maximum length of the first duration in a terrestrial network.

[0377] In other cases, the first window / duration (or a length of the first window) may be larger than the first timing gap, e.g., when the base station is not aware of the TA value of the wireless device (e.g., when the wireless device does not report / transmit the TA value to the base station, e.g., via the TA report procedure). For example, the length of the first window may be based on (or equal to) the cell-specific Koffset (Kcell, offset), e.g., 15-600 slots / ms.

[0378] In an NTN with long propagation delay, to improve UL / DL efficiency / data rate of the wireless device, there is a need to improve UL / DL scheduling / HARQ operation.

[0379] Embodiments of the present disclosure are related to an approach for determining whether (or when) to transmit, to a wireless device by a base station, a third DCI scheduling a PDSCH reception after transmitting a second DCI, to the wireless device, scheduling a PUSCH transmission based on whether the PDSCH reception corresponds to a feedback-enabled HARQ process or a feedback-disabled HARQ process. Some embodiments of the present disclosure are related to an approach for determining PUCCH resource / occasion for a PUCCH transmission indicatedby the third DCI based on whether the PDSCH reception corresponds to a feedback-enabled HARQ process or a feedback-disabled HARQ process. These and other features of the present disclosure are described further below.

[0380] In an example embodiment, a base station may transmit, to a wireless device, a second DCI scheduling a PUSCH transmission. The base station may, after transmitting the second DCI and prior to receiving the PUSCH transmission comprising the HARQ-ACK information (or during the first timing gap / first duration from transmitting the second DCI), determine whether to transmit a third DCI scheduling a second PDSCH / TB reception based on whether the second PDSCH / TB reception correspond to a feedback-enabled HARQ process or a feedback-disabled HARQ process, e.g., whether the second PDSCH / TB reception has an enabled HARQ-ACK information or a disabled HARQ- ACK information. The third DCI may indicate a PUCCH resource / occasion (e.g., via a PRI filed with a PRI value) for a PUCCH transmission (corresponding to a HARQ process of the second PDSCH) during / in the PUSCH transmission occasion (e.g., in a slot p).

[0381] In an example embodiment, in response to the second PDSCH / TB reception corresponding to the feedbackdisabled HARQ process, the base station may, after the transmitting the second DCI and before receiving the PUSCH transmission from the wireless device (or during a first timing gap / first duration from transmitting the second DCI), transmit to the wireless device the third DCI indicating the feedback disabled HARQ process and scheduling the second TB / PDSCH.

[0382] In an example embodiment, in response to the second PDSCH / TB reception corresponding to the feedback- enabled HARQ process, the base station may, after the transmitting the second DCI and before receiving the PUSCH transmission from the wireless device (or during a first timing gap / first duration from transmitting the second DCI), not transmit (or avoid transmitting) to the wireless device a fourth DCI indicating the feedback enabled HARQ process and scheduling a third TB / PDSCH. The fourth DCI may indicate a PUCCH resource / occasion (e.g., via a PRI filed with a PRI value) for a PUCCH transmission (corresponding to a HARQ process of the third PDSCH). The PUCCH transmission may not collide / overlap with the PUSCH transmission. For example, in response to the second PDSCH / TB reception corresponding to the feedback-enabled HARQ process, the base station may, after receiving the PUSCH transmission from the wireless device (or during a first timing gap / first duration from transmitting the second DCI), transmit to the wireless device the fourth DCI indicating the feedback enabled HARQ process and scheduling the third TB / PDSCH.

[0383] In an example embodiment, a wireless device may receive, from the base station, the second DCI scheduling the PUSCH transmission in the slot p. The wireless device may, after the receiving the second DCI and prior to transmitting the PUSCH comprising the HARQ-ACK information (or during a first timing gap from receiving the second DCI), determine whether to receive (or not consider as an error or not drop or no consider an invalid control information indicated by) the third DCI scheduling the second PDSCH / TB reception based on whether the second PDSCH / TB reception correspond to a feedback-enabled HARQ process or a feedback-disabled HARQ process, e.g., whether the second PDSCH / TB reception has an enabled HARQ-ACK information ora disabled HARQ-ACK information.

[0384] In an example embodiment, in response to the second PDSCH / TB reception corresponding to the feedbackdisabled HARQ process, the wireless device may, after the receiving the second DCI and before the PUSCH transmission, receive the third DCI indicating the feedback disabled HARQ process and scheduling the second TB / PDSCH. The wireless device may determine a PUCCH occasion / resource indicated by the third DCI (e.g. , via a PRI field of the third DCI) overlaps / col lides (in time domain) with the PUSCH transmission. The wireless device may transmit the PUSCH transmission (to the base station) comprising the HARQ-ACK information. For example, the HARQ-ACK information may not comprise the second HARQ-ACK information corresponding to the second TB / PDSCH.

[0385] In an example embodiment, in response to the second PDSCH / TB reception corresponding to the feedback- enabled HARQ process, wireless device may, after the receiving the second DCI and before the PUSCH transmission, not receive (or consider as an error or drop or consider an invalid control information indicated by) the fourth DCI indicating the feedback enabled HARQ process and scheduling the third TB / PDSCH. For example, in response to the second PDSCH / TB reception corresponding to the feedback-enabled HARQ process, the wireless device may, after receiving the PUSCH transmission, receive the fourth DCI indicating the feedback enabled HARQ process and scheduling the third TB / PDSCH. The wireless device may transmit the PUSCH transmission (from the wireless device) comprising the HARQ-ACK information. For example, the HARQ-ACK information may not comprise the third HARQ- ACK information corresponding to the third TB / PDSCH.

[0386] In an example embodiment, a wireless device may receive, from the base station, the second DCI scheduling the PUSCH transmission in the slot p. The wireless device may, based on a PUSCH transmission comprising the HARQ-ACK information, determine whether to receive / detect, before the PUSCH transmission (or during the first timing gap from the receiving the second DCI), a third DCI scheduling a second PDSCH / TB reception (and / or indicating a PUCCH resource / occasion fora PUCCH transmission overlapping / colliding with the PUSCH transmission in the slotp) based on whether the second PDSCH reception is associated with a feedback-enabled HARQ process or a feedbackdisabled HARQ process. For example, based on the second PDSCH reception being associated with (or corresponding to) a feedback-enabled HARQ process, the wireless device may determine to not receive (or discard / drop) the third DCI, e.g., consider a control information / parameters / values of the third DCI being invalid or consider the third DCI as an error or being invalidated.

[0387] In an example embodiment, a wireless device may receive, from the base station, the second DCI scheduling the PUSCH transmission in the slot p. The wireless device may, based on a PUSCH transmission comprising the HARQ-ACK information, determine whether to receive (or decode), before the PUSCH transmission (or during the first timing gap from the receiving the second DCI), a second PDSCH / TB reception scheduled a third DCI (indicating a PUCCH resource / occasion fora PUCCH transmission overlapping / colliding with the PUSCH transmission in the slotp) based on whether the second PDSCH reception is associated with a feedback-enabled HARQ process or a feedbackdisabled HARQ process. Based on the second PDSCH reception being associated with (or corresponding to) afeedback-enabled HARQ process, the wireless device may determine to not receive (or not decode), before the PUSCH transmission (or during the first timing gap from the receiving the second DC I) , the second PDSCH / TB scheduled by the third DCI . Based on the second PDSCH reception being associated with (or corresponding to) a feedback-disabled HAR...

Claims

CLAIMSWhat is claimed is:

1. A method comprising: receiving, by a wireless device, a first downlink control information ( DC I) indicating a physical uplink shared channel (PUSCH) transmission in a slot, wherein the PUSCH transmission comprises a hybrid automatic repeat request (HARQ) acknowledgement (ACK) information; based on a HARQ process being a feedback-disabled HARQ process, receiving, after the receiving of the first DCI and before the slot, a second DCI scheduling a physical downlink shared channel (PDSCH) associated with the HARQ process; and transmitting the PUSCH transmission comprising the HARQ-ACK information.

2. The method of claim 1 , wherein the HARQ-ACK information does not comprise a second HARQ-ACK information corresponding to the PDSCH.

3. The method of any one of claims 1 to 2, further comprising receiving one or more radio resource control (RRC) configuration parameters indicating: one or more first HARQ processes with disabled HARQ feedback, wherein the one or more first HARQ processes comprise the HARQ process; and one or more second HARQ processes with enabled HARQ feedback.

4. The method of claim 3, wherein the one or more RRC configuration parameters further indicate a Type 2 HARQ- ACK codebook.

5. The method of any one of claims 1 to 4, further comprising: generating the second HARQ-ACK information corresponding to the PDSCH; and not multiplexing the second HARQ-ACK information corresponding to the PDSCH into the HARQ-ACK information based on the HARQ process being the feedback-disabled HARQ process.

6. The method of claim 5, wherein the generating the second HARQ-ACK information is based on the Type 2 HARQ-ACK codebook.

7. The method of any one of claims 5 to 6, wherein the first DCI indicates a physical uplink control channel (PUCCH) resource in the slot, wherein the PUCCH resource is for the second HARQ-ACK information.

8. The method of claim 7, wherein the PUCCH resource overlaps, in time domain, with a transmission occasion of the PUSCH in the slot.

9. The method of any one of claims 7 to 8, further comprising determining: the PUSCH transmission comprising the HARQ-ACK information; and the PUCCH resource being in the slot.

10. The method of any one of claims 4 to 9, further comprising:generating the Type 2 HARQ-ACK codebook comparing the HARQ-ACK information; and multiplexing the Type 2 HARQ-ACK codebook in the RUSCH transmission.

11. The method of any one of claims 1 to 10, further comprising receiving the PDSCH scheduled by the second DCI.

12. The method of any one of claims 1 to 11 , wherein the second DCI does not activate a semi-persistent PDSCH.

13. The method of any one of claims 1 to 12, wherein: the second DCI activates a semi-persistent PDSCH, wherein the receiving PDSCH comprises receiving a first SPS PDSCH reception after activation; and the one or more RRC configuration parameters does not comprise a parameter indicating enabling of a HARQ feedback for the first SPS PDSCH after activation.

14. The method of any one of claims 1 to 13, further comprising based on a second HARQ process being a feedback- enabled HARQ process, receiving, after the slot, a third DCI scheduling a second PDSCH associated with the second HARQ process.

15. The method of claim 14, wherein the one or more second HARQ processes comprises the second HARQ process.

16. The method of any one of claims 1 to 15, further comprising: receiving one or more RRC configuration parameters indicating a Type 1 HARQ-ACK codebook; receiving, a fourth DCI indicating a second PUSCH transmission in a second slot, wherein the second PUSCH transmission comprises the Type 1 HARQ-ACK codebook comprising a third HARQ-ACK information; based on a third HARQ process being a feedback-disabled HARQ process and the second PUSCH transmission comprising the Type 1 HARQ-ACK codebook, receiving, after the second slot, a fifth DCI scheduling a third PDSCH associated with the third HARQ process; and transmitting the second PUSCH transmission comprising the Type 1 HARQ-ACK codebook.

17. The method of claim 16, wherein the fifth DCI indicates a second PUCCH resource in a third slot, wherein the second PUCCH resource is for a fourth HARQ-ACK information corresponding to the third PDSCH.

18. The method of any one of claims 16 to 17, further comprising generating a second Type 1 HARQ-ACK codebook comprising a third HARQ-ACK information corresponding to the third PDSCH.

19. The method of any one of claims 1 to 18, further comprising: receiving one or more RRC configuration parameters comprising a parameter for enabling of a HARQ feedback for a first SPS PDSCH after activation; receiving, a sixth DCI indicating a third PUSCH transmission in a fourth slot, wherein the third PUSCH transmission comprises a fifth HARQ-ACK information;based on a fourth HARQ process being a feedback-disabled HARQ process and the one or more RRC configuration parameters comprising the parameter, receiving, after the fourth slot, a seventh DCI activating SPS PDSCH; and transmitting the third PUSCH transmission comprising the fifth HARQ-ACK information.

20. A method comprising: receiving, by a wireless device, a first downlink control information (DCI) indicating a physical uplink shared channel (PUSCH) transmission in a slot, wherein the PUSCH transmission comprises a hybrid automatic repeat request (HARQ) acknowledgement (ACK) information; based on a HARQ process being a feedback-enabled HARQ process, receiving, after the slot, a second DCI scheduling a physical downlink shared channel (PDSCH) associated with the HARQ process; and transmitting the PUSCH transmission comprising the HARQ-ACK information.

21. A method comprising: receiving, by a wireless device, one or more RRC configuration parameters indicating a Type 1 HARQ- ACK codebook; receiving, a first DCI indicating a PUSCH transmission in a slot, wherein the PUSCH transmission comprises the Type 1 HARQ-ACK codebook comprising a HARQ-ACK information; based on a HARQ process being a feedback-disabled HARQ process and the PUSCH transmission comprising the Type 1 HARQ-ACK codebook, receiving, after the slot, a second DCI scheduling a PDSCH associated with the HARQ process; and transmitting the PUSCH transmission comprising the Type 1 HARQ-ACK codebook.

22. A method comprising: receiving, by a wireless device, one or more RRC configuration parameters indicating a Type 2 HARQ- ACK codebook; receiving, a first DCI indicating a PUSCH transmission in a slot, wherein the PUSCH transmission comprises the Type 2 HARQ-ACK codebook comprising a HARQ-ACK information; based on a HARQ process being a feedback-disabled HARQ process and the PUSCH transmission comprising the Type 2 HARQ-ACK codebook, receiving, after the receiving of the first DCI and before the slot, a second DCI scheduling a PDSCH associated with the HARQ process; and transmitting the PUSCH transmission comprising the Type 2 HARQ-ACK codebook.

23. A method comprising: receiving, by a wireless device, one or more RRC configuration parameters comprising a parameter for enabling of a HARQ feedback for a first SPS PDSCH after activation; receiving, a first DCI indicating a PUSCH transmission in a slot, wherein the PUSCH transmission comprises a HARQ-ACK information;based on a HARQ process being a feedback-disabled HARQ process and the one or more RRC configuration parameters comprising the parameter, receiving, after the slot, a second DCI activating a SPS PDSCH; and transmitting the PUSCH transmission comprising the HARQ-ACK information.

24. A method comprising: receiving, by a wireless device, one or more RRC configuration parameters indicating a HARQ process being a feedback-disabled HARQ process; receiving, a first DCI indicating a PUSCH transmission in a slot, wherein the PUSCH transmission comprises a HARQ-ACK information; based on the HARQ process being the feedback-disabled HARQ process and the one or more RRC configuration parameters not comprising a parameter, receiving, after the receiving of the first DCI and before the slot, a second DCI activating a SPS PDSCH, wherein the parameter enables of a HARQ feedback for a first SPS PDSCH after activation; and transmitting the PUSCH transmission comprising the HARQ-ACK information.

25. A method comprising: transmitting, by a base station to a wireless device, a first downlink control information (DCI) indicating a physical uplink shared channel (PUSCH) transmission in a slot, wherein the PUSCH transmission comprises a hybrid automatic repeat request (HARQ) acknowledgement (ACK) information; based on a HARQ process being a feedback-disabled HARQ process, transmitting, to the wireless device and after the transmitting of the first DCI and before the slot, a second DCI scheduling a physical downlink shared channel (PDSCH) associated with the HARQ process; and receiving, from the wireless device, the PUSCH transmission comprising the HARQ-ACK information.

26. The method of claim 25, wherein the HARQ-ACK information does not comprise a second HARQ-ACK information corresponding to the PDSCH.

27. The method of any one of claims 25 to 26, further comprising transmitting, to the wireless device, one or more radio resource control (RRC) configuration parameters indicating: one or more first HARQ processes with disabled HARQ feedback, wherein the one or more first HARQ processes comprise the HARQ process; and one or more second HARQ processes with enabled HARQ feedback.

28. The method of claim 27, wherein the first DCI indicates a physical uplink control channel (PUCCH) resource in the slot, wherein the PUCCH resource is for the second HARQ-ACK information.

29. The method of any one of claims 25 to 28, further comprising determining: the PUSCH transmission comprising the HARQ-ACK information; and the PUCCH resource being in the slot.

30. The method of any one of claims 25 to 29, further comprising transmitting, to the wireless device, the PDSCH scheduled by the second DCI .

31. The method of any one of claims 25 to 30, wherein the second DCI does not activate a semi-persistent PDSCH.

32. The method of any one of claims 25 to 31, wherein: the second DCI activates a semi-persistent PDSCH, wherein the transmitting the PDSCH comprising transmitting a first SPS PDSCH reception after activation; and the one or more RRC configuration parameters does not comprise a parameter indicating enabling of a HARQ feedback for the first SPS PDSCH after activation.

33. The method of any one of claims 25 to 32, further comprising based on a second HARQ process being a feedback-enabled HARQ process, transmitting, to the wireless device and after the slot, a third DCI scheduling a second PDSCH associated with the second HARQ process.

34. The method of claim 33, wherein the one or more second HARQ processes comprises the second HARQ process.

35. The method of any one of claims 25 to 34, further comprising: transmitting, to the wireless device, one or more RRC configuration parameters indicating a Type 1 HARQ-ACK codebook; transmitting, to the wireless device, a fourth DCI indicating a second PUSCH transmission in a second slot, wherein the second PUSCH transmission comprises the Type 1 HARQ-ACK codebook comprising a third HARQ-ACK information; based on a third HARQ process being a feedback-disabled HARQ process and the second PUSCH transmission comprising the Type 1 HARQ-ACK codebook, transmitting, to the wireless device and after the second slot, a fifth DCI scheduling a third PDSCH associated with the third HARQ process; and receiving, from the wireless device, the second PUSCH transmission comprising the Type 1 HARQ-ACK codebook.

36. The method of claim 35, wherein the fifth DCI indicates a second PUCCH resource in a third slot, wherein the second PUCCH resource is for a fourth HARQ-ACK information corresponding to the third PDSCH.

37. The method of any one of claims 25 to 36, further comprising: transmitting, to the wireless device, one or more RRC configuration parameters comprising a parameter for enabling of a HARQ feedback for a first SPS PDSCH after activation; transmitting, to the wireless device, a sixth DCI indicating a third PUSCH transmission in a fourth slot, wherein the third PUSCH transmission comprises a fifth HARQ-ACK information; based on a fourth HARQ process being a feedback-disabled HARQ process and the one or more RRC configuration parameters comprising the parameter, transmitting, to the wireless device and after the fourth slot, a seventh DCI activating SPS PDSCH; andreceiving, from the wireless device, the third PUSCH transmission comprising the fifth HARQ-ACK information.

38. 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 37.

39. 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 37.

Images