Monitoring downlink control channels

Abstract

A wireless device receives one or more configuration parameters indicating that control channel monitoring is resumed after control channel monitoring skipping is started when the wireless device transmits a negative acknowledgment (NACK). The wireless device receives a downlink control information (DCI) indicating to skip control channel monitoring. The wireless device starts, after receiving the DCI, skipping the control channel monitoring. The wireless device transmits a first plurality of repetitions of a physical uplink shared channel (PUSCH) transmission. A second plurality of repetitions, of the first plurality of repetitions indicates a negative acknowledgement (NACK). The wireless device resumes monitoring, starting from a slot after a last symbol of an earliest repetition among the second plurality of repetitions, the control channel.

Description

TITLEMonitoring Downlink Control Channels CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 566,794, filed March 18, 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. 1 A and FIG. 1 B illustrate example mobile communication networks in which embodiments of the present disclosure may be implemented.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0017] FIG. 12A and FIG. 12B respectively illustrate examples of three downlink and uplink beam management procedures.

[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 COE-to-REG mapping for DOI 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. 160, and FIG. 16D illustrate example structures for uplink and downlink transmission.

[0023] FIG. 17A and FIG. 17B illustrate an aspect of an example embodiment according to the present disclosure.

[0024] FIG. 18A and FIG. 18B illustrate an aspect of an example embodiment according to the present disclosure.

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

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

[0027] FIG. 21A and FIG. 21 B illustrate an aspect of an example embodiment according to the present disclosure.

[0028] FIG. 22A, FIG. 22B, and FIG. 220 illustrate an aspect of an example embodiment according to the present disclosure.

[0029] FIG. 23A, FIG. 23B, and FIG. 230 illustrate an aspect of an example embodiment according to the present disclosure.

[0030] FIG. 24A, FIG. 24B, FIG. 240, and FIG. 24D illustrate an aspect of an example embodiment according to the present disclosure.

[0031] FIG. 25A and FIG. 25B illustrate an aspect of an example embodiment according to the present disclosure.

[0032] FIG. 26A and FIG. 26B illustrate an aspect of an example embodiment according to the present disclosure.

[0033] FIG. 27A and FIG. 27B illustrate an aspect of an example embodiment according to the present disclosure.

[0034] FIG. 28A and FIG. 28B illustrate an aspect of an example embodiment according to the present disclosure.

[0035] FIG. 29A and FIG. 29B illustrate an aspect of an example embodiment according to the present disclosure.

[0036] FIG. 30A and FIG. 30B illustrate an aspect of an example embodiment according to the present disclosure.

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

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

[0039] FIG. 33 illustrates an aspect of an example embodiment according to the present disclosure.

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

[0041] FIG. 35A and FIG. 35B illustrate an aspect of an example embodiment according to the present disclosure.

[0042] FIG. 36A and FIG. 36B illustrate an aspect of an example embodiment according to the present disclosure.

[0043] FIG. 37 illustrates an aspect of an example embodiment according to the present disclosure.

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

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

[0046] FIG. 40A and FIG. 40B illustrate an aspect of an example embodiment according to the present disclosure.

[0047] FIG. 41A and FIG. 41 B illustrate an aspect of an example embodiment according to the present disclosure.

[0048] FIG. 42A and FIG. 42B illustrate an aspect of an example embodiment according to the present disclosure.

[0049] FIG. 43A and FIG. 43B illustrate an aspect of an example embodiment according to the present disclosure.DETAILED DESCRIPTION

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

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

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

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

[0054] 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 “employin g / using” (or equally “employing / using at least”) is indicative that the phrase following the phrase“employin g / 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.

[0055] The term configured may relate to the capacity of a device whether the device is in an operational or non- operational state. Configured may refer to specific settings in a device that affect or implement the operational characteristics of the device whether the device is in an operational or non-operational state. In other words, the hardware, software, firmware, registers, memory values, and / or the like may be “configured” within a device, whether the device is in an operational or nonoperational state, to provide the device with specific characteristics. Terms such as “a control message to cause in a device” may mean 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.

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

[0057] 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 thatmay 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.

[0058] Many of the elements described in the disclosed embodiments may be implemented as modules. A module is defined here as an element that performs a defined function and has a defined interface to other elements. The modules described in this disclosure may be implemented in hardware, software in combination with hardware, firmware, wetware (e.g. hardware with a biological element) or a combination thereof, which may be behaviorally equivalent. For example, modules may be implemented as a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, MATLAB or the like) or a modeling / simulation program such as Simulink, Stateflow, GNU Octave, or LabVI EWMathScript. 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 (OPLDs). 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.

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

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

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

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

[0063] The RAN 104 may include one or more base stations (not shown). The term base station may be used throughout this disclosure to refer to and encompass a Node B (associated with UMTS and / or 3G standards), an Evolved Node B (eNB, associated with E-UTRA and / or 4G standards), a remote radio head (RRH), a baseband processing unit coupled to one or more RRHs, a repeater node or relay node used to extend the coverage area of a donor node, a Next Generation Evolved Node B (ng-eNB), a Generation Node B (gNB, associated with NR and / or 5G standards), an access point (AP, associated with, for example, Wi-Fi or any other suitable wireless communication standard), and / or any combination thereof. A base station may comprise at least one gNB Central Unit (gNB-CU) and at least one a gNB Distributed Unit (gNB-DU).

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

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

[0066] The RAN 104 may be deployed as a homogenous network of macrocell base stations that have similar antenna patterns and similar high-level transmit powers. The RAN 104 may be deployed as a heterogeneous network. In heterogeneous networks, small cell base stations may be used to provide small coverage areas, for example, coverage areas that overlap with the comparatively larger coverage areas provided by macrocell base stations. The small coverage areas may be provided in areas with high data traffic (or so-called “hotspots”) or in areas with weakmacrocell 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.

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

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

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

[0070] 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. 1 B 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 serveas an anchor point for intra-Zinter-Radio Access Technology (RAT) mobility, an external protocol (or packet) data unit (PDU) session point of interconnect to the one or more D Ns, 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.

[0071] 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 ON and a UE, and AS may refer to the functionality operating between the UE and a RAN.

[0072] The 5G-CN 152 may include one or more additional network functions that are not shown in FIG. 1B for the sake of clarity. For example, the 5G-CN 152 may include one or more of a Session Management Function (SMF), an NR Repository Function (NRF), a Policy Control Function (PCF), a Network Exposure Function (NEF), a Unified Data Management (UDM), an Application Function (AF), and / or an Authentication Server Function (AUSF).

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

[0074] As shown in FIG. 1 B, the gNBs 160 and / or the ng-eNBs 162 may be connected to the 5G-CN 152 by means of an NG interface and to other base stations by an Xn interface. The NG and Xn interfaces may be established using direct physical connections and / or indirect connections over an underlying transport network, such as an internet protocol (IP) transport network. The gNBs 160 and / or the ng-eNBs 162 may be connected to the UEs 156 by means of a Uu interface. For example, as illustrated in FIG. 1B, gNB 160A may be connected to the UE 156A by means of a Uu interface. The NG, Xn, and Uu interfaces are associated with a protocol stack. The protocol stacks associated with the interfaces may be used by the network elements in FIG. 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.

[0075] The gNBs 160 and / or the ng-eNBs 162 may be connected to one or more AMF / UPF functions of the 5G-CN 152, such as the AMF / UPF 158, by means of one or more NG interfaces. For example, the gNB 160A may beconnected 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-0 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.

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

[0077] 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 gNB or ng-eNB may be connected to multiple AMF / UPF nodes to provide redundancy and / or to load share across the multiple AMF / UPF nodes.

[0078] As discussed, an interface (e.g., Uu, Xn, and NG interfaces) between the network elements in FIG. 1 B 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.

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

[0080] 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 (MAGs) 212 and 222, radio link control layers (RLCs) 213 and 223, packet data convergence protocol layers (PDOPs) 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.

[0081] 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 gNB 220. The SDAP 215 at the UE 210 may be informed of the mapping between the QoS flows and the data radio bearers through reflective mapping or control signaling received from the gNB 220. For reflective mapping, the SDAP 225 at the gNB 220 may mark the downlink packets with a QoS flow indicator (QFI), which may be observed by the SDAP 215 at the UE 210 to determine the mapping / de-mapping between the QoS flows and the data radio bearers.

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

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

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

[0085] 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 ofdata units, belonging to the one or more logical channels, into / from Transport Blocks (TBs) delivered to / from the PHYs211 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 g N B 220 (at the MAC 222) for downlink and uplink. The MACs 212 and 222 may be configured to perform error correction through Hybrid Automatic Repeat Request (HARQ) (e.g., one HARQ entity per carrier in case of Carrier Aggregation (CA)), priority handling between logical channels of the UE 210 by means of logical channel prioritization, and / or padding. The MACs212 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.

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

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

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

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

[0090] FIG. 4B illustrates an example format of a MAC subheader in a MAC PDU. The MAC subheader includes: an SDU length field for indicating the length (e.g. , in bytes) of the MAC SDU to which the MAC subheader corresponds; a logical channel identifier (LCID) field for identifying the logical channel from which the MAC SDU originated to aid in the demultiplexing process; a flag (F) for indicating the size of the SDU length field; and a reserved bit (R) field for future use.

[0091] 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 may be used for in-band control signaling. Example MAC CEs include: scheduling-related MAC CEs, such as buffer status reports and power headroom reports; activation / deactivation MAC CEs, such as those for activation / deactivation of PDCP duplication detection, channel state information (CSI) reporting, sounding reference signal (SRS) transmission, and prior configured components; discontinuous reception (DRX) related MAC CEs; timing advance MAC CEs; and random access related MAC CEs. A MAC CE may be preceded by a MAC subheader with a similar format as described for MAC SDUs and may be identified with a reserved value in the LCID field that indicates the type of control information included in the MAC CE.

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

[0093] 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:

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

[0095] - a broadcast control channel (BOOH) 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;

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

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

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

[0099] T ransport 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:

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

[0101] - a broadcast channel (BOH) for carrying the MIB from the BCCH;

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

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

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

[0105] 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:

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

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

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

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

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

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

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

[0113] 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 MAGs 212 and 222, the RLCs 213 and 223, and the PDOPs 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.

[0114] 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 ON. The NAS protocols 217 and 237 may provide control plane functionality between the UE 210 and the AMF 230 via signaling messages, referred to as NAS messages. There is no direct path between the UE 210 and the AMF 230 through which the NAS messages can be transported. The NAS messages may be transported using the AS of the Uu and NG interfaces. NAS protocols 217 and 237 may provide control plane functionality such as authentication, security, connection setup, mobility management, and session management.

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

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

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

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

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

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

[0121] 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 mayperform a registration update with the ON to allow the ON to update the UE’s location and provide the UE with a new the UE registration area.

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

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

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

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

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

[0127] The duration of a slot may depend on the numerology used for the OFDM symbols of the slot. In NR, a flexible numerology is supported to accommodate different cell deployments (e.g., cells with carrier frequencies below 1 GHz up to cells with carrier frequencies in the mm-wave range). A numerology may be defined in terms of subcarrier spacing and cyclic prefix duration. For a numerology in NR, subcarrier spacings may be scaled up by powers of two from a baseline subcarrier spacing of 15 kHz, and cyclic prefix durations may be scaled down by powers of two from a baseline cyclic prefix duration of 4.7 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 / 0.59 ps; and 240 kHz / 0.29 ps.

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

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

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

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

[0132] 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 BMP may be defined by a subset of contiguous RBs on a carrier. A UEmay 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.

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

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

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

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

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

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

[0139] In an example, a base station may semi-statically configure a UE with one or more BWPs. A UE may switch an active BWP from a first BWP to a second BWP in response to receiving a DOI 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).

[0140] 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, DOI, expiration of a BWP inactivity timer, and / or an initiation of random access.

[0141] 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 DOI 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 DOI 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 DOI 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 DOI indicating BWP 902 as the active BWP.

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

[0143] To provide for greater data rates, two or more carriers can be aggregated and simultaneously transmitted to / from the same UE using carrier aggregation (GA). The aggregated carriers in GA may be referred to as component carriers (00s). When GA is used, there are a number of serving cells for the UE, one for a CO. The 00s may have three configurations in the frequency domain.

[0144] FIG. 10A illustrates the three GA configurations with two 00s. In the intraband, contiguous configuration 1002, the two 00s 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 00s are aggregated inthe 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).

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

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

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

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

[0149] 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 ormore 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, may be transmitted in the uplink of the PSCell 1061. In an example, if the aggregated cells depicted in FIG. 10B were not divided into the PUCCH group 1010 and the PUCCH group 1050, a single uplink PCell to transmit UCI relating to the downlink CCs, and the PCell may become overloaded. By dividing transmissions of UCI between the PCell 1021 and the PSCell 1061, overloading may be prevented.

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

[0151] In GA, 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.

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

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

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

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

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

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

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

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

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

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

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

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

[0164] 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-RSand 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.

[0165] Downlink DMRSs may be transmitted by a base station and used by a UE for channel estimation. For example, the downlink DMRS may be used for coherent demodulation of one or more downlink physical channels (e.g. , PDSCH). An NR network may support one or more variable and / or configurable DMRS patterns for data demodulation. At least one downlink DMRS configuration may support a front-loaded DMRS pattern. A front-loaded DMRS may be mapped over one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). A base station may semi- statically configure the UE with a number (e.g. a maximum number) of front-loaded DMRS symbols for PDSCH. A DMRS configuration may support one or more DMRS ports. For example, for single user-MIMO, a DMRS configuration may support up to eight orthogonal downlink DMRS ports per UE. For multiuser-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.

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

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

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

[0169] The UE may transmit an uplink DMRS to a base station for channel estimation. For example, the base station may use the uplink DMRS for coherent demodulation of one or more uplink physical channels. For example, the UE may transmit an uplink DMRS with a PUSCH and / or a PUCCH. The uplink DM-RS may span a range of frequencies that is similar to a range of frequencies associated with the corresponding physical channel. The base station may configure the UE with one or more uplink DMRS configurations. At least one DMRS configuration may support a front- loaded DMRS pattern. The front-loaded DMRS may be mapped over one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DMRSs may be configured to transmit at one or more symbols of a PUSCH and / or a PUCCH. The base station may semi-statically configure the UE with a number (e.g. maximum number) of front-loaded DMRS symbols for the PUSCH and / or the PUCCH, which the UE may use to schedule a single-symbol DMRS and / or a double-symbol DMRS. An NR network may support (e.g., for cyclic prefix orthogonal 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.

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

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

[0172] 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 maytransmit 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 DOI formats. In an example, at least one DOI 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 DOI formats. In an example, when PUSCH and SRS are transmitted in a same slot, the UE may be configured to transmit SRS after a transmission of a PUSCH and a corresponding uplink DMRS.

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

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

[0175] 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 (OS l-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.

[0176] 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, anumber of CSI-RS ports, a OS I -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.

[0177] The three beams illustrated in FIG. 11 B may be configured for a 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.

[0178] CSI-RSs such as those illustrated in FIG. 11 B (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.

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

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

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

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

[0183] 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 resourceand 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.

[0184] 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_I DLE state and / or an RRC_I NACTI VE 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 PUCOH 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.

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

[0186] The configuration message 1310 may be transmitted, for example, using one or more RRC messages. The one or more RRC messages may indicate one or more random access channel (RACH) parameters to the UE. The one or more RACH parameters may comprise at least one of following: general parameters for one or more random access procedures (e.g., RACH-configGeneral}; cell-specific parameters (e.g., RACH-ConfigCommon'); and / or dedicated parameters (e.g., RACH-configDedicated}. The base station may broadcast or multicast the one or more RRC messages to one or more UEs. The one or more RRC messages may be UE-specific (e.g., dedicated RRC messages transmitted to a UE in an RRC_CONNECTED state and / or in an RRCJNACTIVE 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 2 1312 and the Msg 41314.

[0187] 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 morereference 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.

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

[0189] 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 3 1313. The UE may measure an RSRP of one or more reference signals (e.g., SSBs and / or CSI-RSs) and determine at least one reference signal having an RSRP above an RSRP threshold (e.g., rsrp-ThresholdSSB and / or rsrp-ThresholdCSI-RS). The UE may select at least one preamble associated with the one or more reference signals and / or a selected preamble group, for example, if the association between the one or more preambles and the at least one reference signal is configured by an RRC message.

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

[0191] 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 preambletransmit 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_RAMP / NG_STEP) indicating a ramping step for the preamble retransmission. The ramping step may be an amount of incremental increase in uplink transmit power for a retransmission. The UE may ramp up the uplink transmit power if the UE determines a reference signal (e.g., SSB and / or CSI-RS) that is the same as a previous preamble transmission. The UE may count a number of preamble transmissions and / or retransmissions (e.g., PREAMBLE_TRANSMISSION_COUNTER). The UE may determine that a random access procedure completed unsuccessfully, for example, if the number of preamble transmissions exceeds a threshold configured by the one or more RACH parameters (e.g., preambleTransMax).

[0192] The Msg 2 1312 received by the UE may include an RAR. In some scenarios, the Msg 21312 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 21312 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 3 1313, and / or a Temporary Cell RNTI (TC-RNTI). After transmitting a preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor a PDCCH for the Msg 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:

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

[0194] The UE may transmit the Msg 3 1313 in response to a successful reception of the Msg 21312 (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 transmita 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 3 1313 and the Msg 41314) may be used to increase the likelihood that the UE does not incorrectly use an identity of another the UE. To perform contention resolution, the UE may include a device identifier in the Msg 3 1313 (e.g., a C-RNTI if assigned, a TC-RNTI included in the Msg 2 1312, and / or any other suitable identifier).

[0195] The Msg 41314 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 31313 (e.g., if the UE is in an RRC_IDLE state or not otherwise connected to the base station), Msg 41314 will be received using a DL-SCH associated with the TC-RNTI. If a MAC PDU is successfully decoded and a MAC PDU comprises the UE contention resolution identity MAC CE that matches or otherwise corresponds with the CCCH SDU sent (e.g., transmitted) in Msg 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.

[0196] 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 31313) 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 31313 based on a channel clear assessment (e.g., a listen- before-talk).

[0197] 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 21322. The Msg 1 1321 and the Msg 21322 may be analogous in some respects to the Msg 1 1311 and a Msg 21312 illustrated in FIG. 13A, respectively. As will be understood from FIGS. 13A and 13B, the contention- free random access procedure may not include messages analogous to the Msg 3 1313 and / or the Msg 41314.

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

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

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

[0201] 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 ACK / NACK, and / or the like). The UE may receive the Msg B 1332 after or in response to transmitting the Msg A 1331. The Msg B 1332 may comprise contents that are similar and / or equivalent to the contents of the Msg 2 1312 (e.g., an RAR) illustrated in FIGS. 13A and 13B and / or the Msg 41314 illustrated in FIG. 13A.

[0202] The UE may initiate the two-step random access procedure in FIG. 130 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.

[0203] 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 transportblock 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.

[0204] 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 (I MSI)). The base station may transmit the Msg B 1332 as a response to the Msg A 1331. The Msg B 1332 may comprise at least one of following: a preamble identifier; a timing advance command; a power control command; an uplink grant (e.g., a radio resource assignment and / or an MOS); a UE identifier for contention resolution; and / or an RNTI (e.g., a C-RNTI or a TC-RNTI). The UE may determine that the two-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).

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

[0206] 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 (DOI). In some scenarios, the PDCCH may be a group common PDCCH (GC-PDCCH) that is common to a group of UEs.

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

[0208] 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 1313illustrated in FIG. 13A). Other RNTIs configured to the UE by a base station may comprise a Configured Scheduling RNT I (CS-RNTI), a Transmit Power Control-PUCOH RNTI (TPC-PUCCH-RNTI), a Transmit Power Control-PUSCH RNTI (TPC-PUSCH-RNTI), a Transmit Power Control-SRS RNTI (TPC-SRS-RNTI), an Interruption RNTI (INT-RNTI), a Slot Format Indication RNTI (SFI-RNTI), a Semi-Persistent CSI RNTI (SP-CSI-RNTI), a Modulation and Coding Scheme Cell RNTI (MCS-C-RNTI), and / or the like.

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

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

[0211] 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 at a third symbol in the slot. A fourth CORESET 1404 occurs at the seventh symbol in the slot. CORESETs may have a different number of resource blocks in frequency domain.

[0212] 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 frequencydiversity) or a non-interleaved mapping (e.g., for the purposes of facilitating interference coordination and / or frequency- selective transmission of control channels). The base station may perform different or same CCE-to-REG mapping on different CORESETs. A CORESET may be associated with a CCE-to-REG mapping by RRC configuration. A CORESET may be configured with an antenna port quasi co-location (QCL) parameter. The antenna port GCL parameter may indicate QCL information of a demodulation reference signal (DMRS) for PDCCH reception in the CORESET.

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

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

[0215] 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 downlinktransmission. 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 (PUCOH) ora physical uplink shared channel (PUSCH). The UE may transmit the uplink control signaling via a PUCOH using one of several PUCOH formats.

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

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

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

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

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

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

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

[0223] At the base station 1504, a reception processing system 1512 may receive the uplink transmission from the wireless device 1502. At the wireless device 1502, a reception processing system 1522 may receive the downlink transmission from base station 1504. The reception processing system 1512 and the reception processing system 1522 may implement layer 1 OSI functionality. Layer 1 may include a PHY layer with respect to FIG. 2A, FIG. 2B, FIG. 3, and FIG. 4A. For receive processing, the PHY layer may perform, for example, error detection, forward error correction decoding, deinterleaving, demapping of transport channels to physical channels, demodulation of physical channels, Ml MO or multi-antenna processing, and / or the like.

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

[0225] The processing system 1508 and the processing system 1518 maybe 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.

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

[0227] 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). Theprocessing system 1508 and / or the processing system 1518 may receive user input data from and / or provide user output data to the one or more peripherals 1516 and / or the one or more peripherals 1526. The processing system 1518 in the wireless device 1502 may receive power from a power source and / or may be configured to distribute the power to the other components in the wireless device 1502. The power source may comprise one or more sources of power, for example, a battery, a solar cell, a fuel cell, or any combination thereof. The processing system 1508 and / or the processing system 1518 may be connected to a GPS chipset 1517 and a GPS chipset 1527, respectively. The GPS chipset 1517 and the GPS chipset 1527 may be configured to provide geographic location information of the wireless device 1502 and the base station 1504, respectively.

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

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

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

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

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

[0233] 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 (or expiration) of a random access response window timer, the time difference between two time stamps may be used. When a timer is restarted, a process for measurement of time window may be restarted. Other example implementations may be provided to restart a measurement of a time window.

[0234] A wireless device may receive (e.g., from a base station and / or via a cell), one or more messages. The one or more messages may comprise one or more RRC messages. The wireless device may receive at least one message of the one or more messages via / using one or more PDSCHs / TBs. The wireless device may receive at least one message of the one or more messages via / using one or more DOIs or control channels. The wireless device may receive at least one message of the one or more messages via / using one or more MAC CEs The one or more messages may comprise / indicate one or more configuration parameters for communicating (e.g., transmitting and / or receiving) one or more sign als / channels via the cell. The one or more channels / sign als may comprise one or more DL signals / channels, e.g., PDSCH / CSI-RS / PDCCH / SSB / WUS (wake up signal) or the like. The one or more channels / signals may comprise one or more UL signals / channels, e.g., PUSCH / SRS / PUCCH / WUS or the like.

[0235] The one or more configuration parameters may, for example, comprise / configure / indicate one or more serving cell (e.g., the one or more Serving Cells or the one or more cells) configuration parameters (e.g., ServingCellConfigCommon, Sen / ingCellConfigCommonSIB, and / or ServingCellConfig). The one or more serving cell configuration parameters may be for configuring one or more cells (e.g., the one or more Serving Cells). For example, the one or more cells may comprise a master (or primary) cell group (MSG) and / or a secondary cell group (SCG).

[0236] In some cases, a cell of the one or more cells may be a primary secondary cell (PSCell), or a primary cell (PCell), or a secondary cell (SCell), or a special cell (SpCell). In some other cases, a cell of the one or more cells may belong to a first cell group corresponding to a primary TAG (pTAG) or a second cell group corresponding to a secondary TAG (sTAG). For example, the one or more configuration parameters may configure the wireless device for multi-cell communication and / or carrier aggregation.

[0237] The one or more configuration parameters may comprise configuration parameters of one or more BWPs (e.g., one or more BWP configuration parameters). The one or more BWP configuration parameters may comprise parameters of the cell and one or more BWPs associated with the cell. Among the one or more BWPs, at least one BWP may be configured as the first active BWP (e.g., BWP 1), one BWP as the default BWP (e.g., BWP 0). In some cases, the wireless device may receive a command (e.g., an RRC message, a MAC CE or a DOI) to activate the cell at a slot. In some other cases (e.g., when the cell is a PCell), the wireless device may activate the cell (e.g., PCell) once the wireless device receives the command (e.g., the RRC message) comprising configuration parameters of the PCell. The wireless device may start monitoring a PDCCH (e.g., monitoring PDCCH candidates) on BWP 1, e.g., in response to activating the cell.

[0238] A wireless device may start (or restart) a BWP inactivity timer (e.g., bwp-lnactivityTimer) at an m-th slot in response to receiving a DCI indicating DL assignment on BWP 1. The wireless device may switch back to the default BWP (e.g., BWP 0) as an active BWP when the BWP inactivity timer expires, at s-th slot. The wireless device may deactivate the cell and / or stop the BWP inactivity timer when the sCell Deacti vationTi mer expires (e.g., if the cell is a SCell). In response to the cell being a PCell, the wireless device may not deactivate the cell and may not apply the sCell DeactivationTimer on the PCell.

[0239] A MAC entity may apply normal operations on an active (or activated) BWP for an activated serving cell (e.g., the cell). For example, on the activated BWP and via the cell the wireless device may perform at least one of the following: transmitting on UL-SCH (PUSCH transmission); transmitting on RACH (preamble transmission); monitoring a PDCCH; transmitting PUCCH; receiving DL-SCH (PDSCH reception); and / or (re-) initializing configured uplink grants of configured grant Type 1 or Type 2 according to a stored configuration. The one or more configuration parameters may configure / provide configured uplink grants of configured grant Type 1 or Type 2.

[0240] On an inactive (or deactivated or dormant) BWP of the cell (or for each activated serving cell configured with a BWP), the wireless device may perform at least one of the following: not transmit on UL-SCH; not transmit on RACH; not monitor a PDCCH; not transmit PUCCH; not transmit SRS, not receive DL-SCH; clear any configured downlink assignment and configured uplink grant of configured grant Type 2; and / or suspend any configured uplink grant of configured Type 1.

[0241] A DCI (or a control channel) addressed to an RNTI may comprise a CRC of the DCI being scrambled with the RNTI. The wireless device may monitor PDCCH (candidates) addressed to (or for) the RNTI for detecting the DCI. Thewireless device may detect the DCI / PDCCH during / via / using at least one PDCCH monitoring occasion. For example, the PDCCH may carry (or be with) the DCI.

[0242] The one or more configuration parameters may indicate / configure a set of (or at least one) PDCCH candidates for a wireless device to monitor. The wireless device may monitor the at least one PDCCH candidate based on one or more search space sets (SSSs) configured by the one or more configuration parameters (e.g., one or more PDCCH configuration parameters). A search space set of the one or more search space sets may comprise a CSS (common search space) set or a USS (UE-specific search space) set. For example, a wireless device may monitor the set of PDCCH candidates according to configuration parameters of a search space set (e.g., of the one or more SSSs). The wireless device may monitor a set of PDCCH candidates in one or more CORESETs (control resource sets) for detecting one or more DCIs. Monitoring the PDCCH (e.g., a set of PDCCH candidates) in the one or more CORESETs on the active DL BWP on each activated serving cell (configured with PDCCH monitoring) may be based on / be according to corresponding search space sets. In some examples, monitoring the PDCCH may imply receiving each PDCCH candidate of the set of PDCCH candidates and decoding each PDCCH candidate according to the monitored DCI formats.

[0243] When a PDCCH reception by the wireless device includes two PDCCH candidates from corresponding search space sets, a PDCCH monitoring occasion may comprise / be a union of PDCCH monitoring occasions for the two PDCCH candidates. A start / beginn ing of the PDCCH reception may be a start / beginn in g of an earlier PDCCH candidate (in time domain) of the two PDCCH candidates. An end of the PDCCH reception may be an end of the PDCCH candidate of the two PDCCH candidates that ends later (in time domain). For example, the PDCCH reception may include / comprise the two PDCCH candidates when the wireless device is not required (or expected) to monitor one of the two PDCCH candidates (e.g., due to UL slots or collision with SSB symbols or due to cell DTX operation).

[0244] A wireless device monitors PDCCH candidates in one or more of the following search spaces sets of the one or more search space sets: a TypeO-PDCCH CSS set configured by pdcch-ConfigSI B1 in MIB or by searchSpaceSI B1 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; and / or a TypeOA-PDCCH CSS set configured by searchSpaceOtherSystemlnformation in PDCCH-ConfigCommon for a DCI format with CRC scrambled by a SI-RNTI on the primary cell of the MCG; and / or 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; and / or 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; and / or a Type3-PDCCH CSS set configured by SearchSpace in PDCCH-Config with searchSpaceType = common for DCI formats with CRC scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, CI-RNTI, or PS-RNTI and, only for the primary cell, C-RNTI, MCS-C-RNTI, or CS-RNT I (s); and / or a USS set configured by SearchSpace in PDCCH-Config withsearchSpaceType = ue-Specific for DOI formats with ORC scrambled by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, CS- RNTI(s), SL-RNTI, SL-CS-RNTI, orSL-L-CS-RNTI.

[0245] A wireless device may determine a PDCCH monitoring occasion (of the at least one PDCCH monitoring occasion) on an active DL BWP based on the one or more PDCCH configuration parameters. The one or more PDCCH configuration parameters may be at least one of a PDCCH-Config and / or PDCCH-ConfigCommon and / or PDCCH- Servin gCel IConfig or the like. The one or more PDCCH configuration parameters may comprise at least one of the following: a PDCCH monitoring periodicity; and / or a PDCCH monitoring offset; and / or a PDCCH monitoring pattern within a slot. For a search space set (SSS) of the one or more SSSs, the wireless device may determine that the PDCCH monitoring occasion exists in a slot with number n^fin a frame with number nfif (nf•+ n^f- osmod ks= 0.is a number of slots in a frame when numerology pi is configured. osis a slot offset indicated in the one or more PDCCH configuration parameters. ksis the PDCCH monitoring periodicity indicated in the one or more PDCCH configuration parameters. In an example, the wireless device may monitor PDCCH candidates for the search space set for Tsconsecutive slots, starting from slot n^f. For example, the wireless device may not monitor the PDCCH candidates for search space set s for the next ks- Tsconsecutive slots, e.g., starting after n^f+ Ts.

[0246] Monitoring the PDCCH by the wireless device may comprise decoding one or more PDCCH candidates of the set of the PDCCH candidates according to the monitored DCI formats. Monitoring the PDCCH by the wireless device 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 SSSs, and / or number of PDCCH candidates in UE-specific SSSs) and possible (or configured) DCI formats. The decoding may be referred to as blind decoding.

[0247] Abase station may transmit control information to a wireless device using DCI formats. The wireless device may use the DCI formats for PDCCH monitoring or detecting DCIs in / d u ring the PDCCH monitoring occasions. Different DCI formats may comprise different DCI fields and / or have different DCI payload sizes. Different DCI formats may have different signaling purposes. In an example, DCI format 0_0 may be used to schedule PUSCH in one cell. DCI format 0_1 may be used to schedule one or multiple PUSCH in one cell or indicate CG-DFI (configured grant-Downlink Feedback Information) for configured grant PUSCH, etc. The DCI format(s) which the wireless device may monitor in a SS may be configured.

[0248] The one or more messages may comprise a MIB. A wireless device, based on receiving primary synchronization signal (PSS) and / or secondary synchronization signal (SSS), may receive the MIB via a PBCH. The MIB may indicate / configure six bits (systemFrameNumber) of system frame number (SFN); and / or subcarrier spacing indication (subCarrierSpacingCommon); and / or a frequency domain offset (ssb-SubcarrierOffset) between SSB and overall resource block grid in number of subcarriers; and / or an indication (cell Barred) indicating whether the cell isbared; and / or a DMRS position indication (dmrs-TypeA-Position) indicating position of DM-RS; and / or parameters of CORESET and an SSS (of the one or more SSSs) of a PDCOH (pdcch-ConfigSI B 1 ) comprising a common CORESET.

[0249] The pdcch-ConfigSI B1 may comprise a first parameter (e.g., controlResourceSetZero) indicating a common ControlResourceSet (CORESET) with ID #0 (e.g., CORESETSO) of an initial BWP of the cell. controlResourceSetZero may be an integer number between 0 and 15, e.g., identifying a configuration of CORESETSO. The wireless device may determine a SSB and CORESETSO multiplexing pattern, a number of RBs for CORESETSO, a number of symbols for CORESETSO, an RB offset for CORESETSO. The pdcch-ConfigSIB1 may comprise a second parameter (e.g., searchSpaceZero) indicating a common search space with ID #0 (e.g., SSS#0 of the one or more SSSs) of the initial BWP of the cell. searchSpaceZero may be an integer between 0 and 15, e.g., for identifying a configuration of SSS#0. Based on a value of the integer of searchSpaceZero, a wireless device may determine one or more parameters (e.g., 0, M) for slot determination of PDCOH monitoring, a first symbol index for PDCOH monitoring and / or a number of search spaces per slot.

[0250] Based on (or after) receiving the MIB, a wireless device may monitor PDCOH via the SSS#0 of CORESETSO for receiving a DOI scheduling / indicating a system information block 1 (SIB1). For example, the one or more messages may comprise the SIB1. The wireless device may receive the DOI with ORC scrambled with a system information radio network temporary identifier (SI-RNTI) dedicated for receiving the SIB1.

[0251] The one or more configuration parameters may comprise configuration parameters of the SIBa. The SIB1 (and / or other SIBs, e.g., SIB2) may be transmitted to all wireless devices camping / residing in a cell in a broadcast way / manner. The SIB1 may contain information relevant when evaluating if a wireless device is allowed to access the cell, information of paging configuration and / or scheduling configuration of other system information (e.g., SIB2-25). The SIB1 may contain / include / comprise radio resource configuration information that is common for all wireless devices in the cell.

[0252] A base station may transmit to a wireless device (or a plurality of wireless devices) one or more SIBs (e.g., the SIB1 ). The one or more SIBs may indicate / provide the one or more configuration parameters. For example, one or more SIBs may configure / indicate at least one of the following: one or more parameters (e.g., cellSelection Info) for cell (re-)selection procedure; one or more configuration parameters of a serving cell (e.g., in ServingCellConfigOommonSIB IE); and one or more other parameters. The ServingCellConfigOommonSIB IE may comprise at least one of: common downlink parameters (e.g., in DownlinkConfigCommonSIB IE) of the serving cell; and / or common uplink parameters (e.g., in UplinkConfigCommonSIB IE) of the serving cell.

[0253] The DownlinkConfigCommonSIB IE may comprise parameters of an initial downlink BWP (initialDownlinkBWP IE) of the serving cell (e.g., SpCell). The parameters / configuration of the initial downlink BWP may be comprised in a BWP-DownlinkCommon IE. The BWP-DownlinkCommon IE may be used to configure common parameters of a downlink BWP of the serving cell. The base station may configure the locationAnd Bandwidth so that the initial downlink BWP contains the entire CORESETSO of this serving cell in the frequency domain. The wireless device may apply thelocationAnd Bandwidth upon reception of this field (e.g. , to determine the frequency position of signals described in relation to this locationAnd Bandwidth) but it keeps CORESETSO until after reception of RRCSetup / RRCResume / RRCReestablishment.

[0254] The DownlinkConfigCommonSIB IE may comprise parameters of a paging channel configuration. The parameters of the paging channel configuration may comprise a paging cycle value (T, by defaultPagingCycle IE); and / or a parameter (nAndPagingFrameOffset IE) indicating total number N) of paging frames (PFs) and paging frame offset (PF_offset) in a paging DRX cycle; and / or a number (Ns) for total paging occasions (POs) per PF; and / or a first PDCCH monitoring occasion indication parameter (firstPDCCH-MonitoringOccasionofPO IE) indicating a first PDCCH monitoring occasion for paging of each PO of a PF. The wireless device, based on parameters of a PCCH configuration, may monitor PDCCH for receiving paging message via the serving cell.

[0255] The one or more configuration parameters may comprise BWP-DownlinkCommon (I.E., e.g., configuration parameters of a downlink BWP of a serving cell. The one or more configuration parameters of a downlink BWP (e.g., the initial downlink BWP) of a serving cell may comprise at least one of the following: one or more generic BWP parameters of the downlink BWP; and / or the one or more PDCCH configuration parameters (e.g., one or more cell specific parameters for PDCCH of the downlink BWP (e.g., in pdcch-ConfigCommon IE); and / or one or more cell specific parameters for the PDSCH of this BWP (e.g., in pdsch-ConfigCommon IE). The pdcch-ConfigCommon IE may comprise parameters of COESET #0 (e.g., control ResourceSetZero) which may be used in any common or UE-specific search spaces. A value of the control ResourceSetZero may be interpreted like the corresponding bits in MIB pdcch- ConfigSI B1. A pdcch-ConfigCommon IE may comprise parameters (e.g., in commonControlResourceSet) of an additional common control resource set which may be configured and used for any common or UE-specific search space. If the network configures this field, it uses a ControlResourceSetld other than 0 for this Control ResourceSet. The network configures the commonControlResourceSet in SIB1 so that it is contained in the bandwidth of CORESETSO. A pdcch-ConfigCommon IE may comprise parameters (e.g., in commonSearchSpaceList) of a list of additional common search spaces. The one or more SSSs may comprise the list of additional common search spaces. A pdcch-ConfigCommon IE may indicate, from a list of search spaces, a search space for paging (e.g., pagingSearchSpace), a search space for random access procedure (e.g., ra-SearchSpace), a search space for SIB1 message (e.g., searchSpaceSI B1 ), a common search spaceSO (e.g., searchSpaceZero), and one or more other search spaces.

[0256] A control resource set (CORESET) may be associated with a CORESET index (e.g., ControlResourceSetld). A CORESET may be implemented based on example embodiments described above with respect to FIG. 14A and / or FIG. 14B. The CORESET index with a value of 0 may identify a common CORESET configured in MIB and in ServingCellConfigCommon (controlResourceSetZero) and may not be used in the Control ResourceSet IE. The CORESET index with other values may identify CORESETs configured by dedicated signaling or in SIB1. The ControlResourceSetld is unique among the BWPs of a serving cell. A CORESET may be associated withcoresetPoollndex indicating an index of a CORESET pool for the CORESET. A CORESET may be associated with a time duration parameter (e.g. , duration) indicating contiguous time duration of the CORESET in number of symbols. In an example, configuration parameters of a CORESET may comprise at least one of: frequency resource indication (e.g., frequencyDomainResources); and / or a COE-REG mapping type indicator (e.g., cce-REG-MappingType); and / or a plurality of TCI states; and / or an indicator indicating whether a TCI is present in a DCI. The frequency resource indication, comprising a number of bits (e.g., 45 bits), may indicate frequency domain resources, each bit of the indication corresponding to a group of 6 RBs, with grouping starting from the first RB group in a BWP of a cell (e.g., SpCell, SCell). The first (left-most, e.g., a most significant) bit may correspond to the first RB group in the BWP, and so on. A bit that is set to 1 may indicate that an RB group, corresponding to the bit, belongs to the frequency domain resource of this CORESET. Bits corresponding to a group of RBs not fully contained in the BWP within which the CORESET is configured may be set to zero. The one or more configuration parameters may comprise configuration parameters of CORESETs.

[0257] In some examples, monitoring the PDCCH candidates may comprise multi-slot PDCCH monitoring procedure.

[0258] A wireless device may transmit one or more UE-capability messages to a base station. The one or more UE- capability messages may comprise monitoringCapabilityConfig for a serving cell.

[0259] In one example, the wireless device may obtain (or derive or determine or calculate) an indication to monitor PDCCH on the active DL BWP of the serving cell for a maximum number of PDCCH candidates and non-overlapping CCEs per slot if monitoringCapabilityConfig = r15monitoringcapability (e.g., per-slot / slot-based PDCCH monitoring mode / state). For example, a capability for PDCCH monitoring per slot on an active DL BWP of the serving cell may be defined by a maximum number of PDCCH candidates and non-overlapped CCEs the wireless device is able to monitor per slot on the active DL BWP of the serving cell.

[0260] In another example, a wireless device may obtain (or derive or determine or calculate) an indication to monitor PDCCH on the active DL BWP of the serving cell for a maximum number of PDCCH candidates and non-overlapping CCEs per span if monitoringCapabilityConfig = r16monitoringcapability (e.g., per-span / span-based PDCCH monitoring mode / state). A capability for PDCCH monitoring per span on an active DL BWP of the serving cell may be defined by a maximum number of PDCCH candidates and non-overlapped CCEs the wireless device is able to monitor per span on the active DL BWP of the serving cell. For example, the UE-capability message may indicate a capability to monitor PDCCH according to one or more of the combinations (X, Y) = (2, 2), (4, 3), and (7, 3) per SCS configuration of p = 0 and p = 1. A span may be a number of consecutive symbols in a slot where the wireless device is configured (by the one or more PDCCH configuration parameters) to monitor PDCCH. Each PDCCH monitoring occasion is within one span. If a wireless device monitors PDCCH on the serving cell according to combination (X, Y), the wireless device supports PDCCH monitoring occasions in any symbol of a slot with minimum time separation of X symbols between the first symbol of two consecutive spans, including across slots. A span starts at a first symbol where a PDCCH monitoringoccasion starts and ends at a last symbol where a PDCCH monitoring occasion ends, where the number of symbols of the span is up to Y.

[0261] In yet another example, a wireless device may obtain (or derive or determine or calculate) an indication to monitor PDCCH on the active DL BWP of the serving cell for a maximum number of PDCCH candidates and nonoverlapping CCEs per group of Xsslots according to a predefined / preconfigured combination (Xs, Ks) if monitoringCapabilityConfig = r17monitoringcapability (e.g., multiple-slot / multi-slot or group-based PDCCH monitoring mode / state). In some embodiments, (Xs, Ys) = (4, 1) for p = 5 and (Xs, Ks) = (8, 1) for p = 6. For example, a capability for PDCCH monitoring per group of Xsslots according to combination (Xs, Ys) on an active DL BWP of the serving cell may be defined by a maximum number of PDCCH candidates and non-overlapped CCEs the wireless device is able to monitor per group of Xsslots according to combination (Xs, Ys) on the active DL BWP of the serving cell.

[0262] For SCS configuration p = 5 or p = 6, the UE-capability message may indicate a capability to monitor PDCCH according to one or more combinations (Xs, Ks), where Xsand Ksare numbers of consecutive slots. Groups of Xsslots are consecutive and non-overlapping and the Ksslots are within the Xsslots. A first group of Xsslots may start from a beginning / start of a subframe. The start of two consecutive groups of Ksslots may be separated by Xsslots.

[0263] Corresponding to / according to the multi-slot PDCCH monitoring mode (e.g., when the wireless device monitors PDCCH on the serving cell according to combination (Xs, Ks)), the wireless device may monitor PDCCH for Typel -PDCCH CSS set provided by dedicated higher layer signaling (e.g., dedicated RRC signaling of the one or more messages), Type3-PDCCH CSS sets, and USS sets in any slot of the Ksslots. Corresponding to / according to the multislot PDCCH monitoring mode, the wireless device may monitor PDCCH for Type0 / 0A / 2-PDCCH CSS set and Typel - PDCCH CSS set provided in SIB1 in any slot of the Xsslots. The wireless device may determine a number of monitored PDCCH candidates and the number of non-overlapped CCEs for combination (Xs, Ks) based on (all) SSSs (of the one or more SSSs) within the Xsslots. The wireless device may determine a number of monitored PDCCH candidates and the number of non-overlapped CCEs for combination (Xs, Ys) based on a maximum number ^PDCCHS, / 1°f monitored PDCCH candidates per group of Xsslots for combination (Xs, Ks) for a DL BWP with SCS configuration p e {5, 6} for the serving cell.

[0264] A wireless device may receive a transport block (TB) (e.g., in a PDSCH reception occasion) from a base station, e.g., via the serving cell. 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 moreconfiguration parameters (e.g., SPS-Config). 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 resu It / ou tcome of the TB).

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

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

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

[0268] 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. The wireless device may receive a first number of transport blocks (TBs or PDSCHs) 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.

[0269] 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 withan enabled HARQ-ACK information). The wireless device may transmit / send the Type-1 HARQ-ACK codebook corresponding to the second number of TBs / PDSCHs.

[0270] When a wireless device is configured with pdsch-HARQ-ACK-Codebook = semi-static, the wireless device may, via a serving cell, receive a DOI 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- HARQJeedback 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 / inapplicable 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-r 17 or dl-DataToUL-ACK-DCI-1-2-r17).

[0271] 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 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. The wireless device may not expect (or consider it as error) to multiplex the Type-2 HARQ-ACK codebook the HARQ-ACK information that is in response to the detection of the DCI format that does not include the counter DAI field.

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

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

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

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

[0276] 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^p, and a cyclic shift index set for a PUCCH transmission.

[0277] 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 intraSlotFrequencyHopping; an index of a first interlace by interlace 0, 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-lndicatedTCIState, 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.

[0278] 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, the wireless device may determine a PUCCH resource (e.g., for the PUCCH transmission) with index rPUCCH, 0 < rPUCCH< 15, as rPUCCH=2”CCE,° + 2 • APRI. NCCEis aL NCCE -I 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. APRIis a value of the PUCCH resource indicator field in the DCI format.

[0279] 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,

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

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

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

[0283] The slot (for transmission of PUCCH), e.g., slot n, may be a last / final / end ing / 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 the last / fin al / endin g / 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 + 2 / 1“ / 1;<'offset ■ / Toffset, k is provided by the PDSCH-to-HARQ_feedback timing indicator field, if present, in a DCI format activating the SPS PDSCH reception. / COffset 'sthe scheduling offset of an NTN (e.g., based on a cell-specific Koffset and / or a differential / UE-specific Koffset).

[0284] 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 + ■ / foffset. k is provided / configured / indicated by the one or more configuration parameters (e.g., by 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-v1700).

[0285] 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 +■offset. k is a number of slots and is indicated by the PDSCH-to-HARQ_feedback timing indicator field in the DCI format, if present, orprovided / configured / indicated by the one or more configuration parameters (e.g., dl-DataToUL-ACK, dl-DataToUL- ACK-M6, 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).

[0286] 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 OUC| (or OACK) HARQ-ACK information bits. The PUCCH resource determination may be 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, or a value of dl-DataToUL-ACK, or dl-DataToUL-ACK-r16, or dl-DataToUL-ACK-DCI-1 -2, or dl-DataToUL- ACK -r 17, or d l-DataTo U L-AC K -DCI- 1 -2-r17, or d 1-DataToU L-AC K-Mu IticastDC l-Form at4-1 , or d 1-DataToU L-AC K- 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 resou rceList 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 RPUCCH of resou rceList is larger than eight, when a wireless device sends / transmits / provides HARQ-ACK information in a PUCCH transmission in 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, or a 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), the wireless device may determine a PUCCH resource with index rPUCCH, 0 < rPUCCH< RPUCCH - 1. based on at least one of the following: NCCEp, e.g., a number of CCEs in CORESET p of the PDCCH reception for the DCI format; nCCEp, e.g., an index of a first CCE for the PDCCH reception; and / or APRI, e.g., a value of the PUCCH resource indicator field in the DCI format.

[0287] 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~^ ■ 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 ofP DSC H-ServingCellConfig is set to enable for the serving cell with the second DOI 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 |i = 1, N3= 9 for |i = 2; otherwise, N3= 8 for pi = 0, N3= 10 for pi = 1, N3= 17 for pi = 2, N3= 20 for pi = 3 , N3= 80 for pi = 5, and N3= 160 for pi = 6.

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

[0289] As shown in FIG. 17A and FIG. 17B, the wireless device may (from the base station, e.g., via the serving cell) receive a fifth DCI (DCI 5) indicating / scheduling a (reception / transmission of) a PDSCH / TB corresponding to a HARQ process. For example, the wireless device may receive the fifth DCI within / during / in a PDCCH monitoring occasion (e.g., a downlink control channel monitoring occasion). Although, in the example of FIG. 17A and FIG. 17B, the wireless device may receive both the fifth 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).

[0290] Further, although, in the example of FIG. 17A and FIG. 17B, reception of only one TB / PDSCH is shown, the fifth 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 fifth DCI.

[0291] For example, the fifth DCI may indicate a HARQ process number / ID / index / identifier of the HARQ process. Although in FIG. 17A and FIG. 17B, the fifth 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.

[0292] 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 slot m, e.g., m>=n) a sixth DCI (DCI 6) scheduling / indicating a PUSCH transmission in an occasion (e.g., in / within / during a slot p, e.g., p>=m).

[0293] The PUSCH transmission may be with at least one repetition (1 repetition).

[0294] The PUSCH transmission may be during / within a slot.

[0295] The PUSCH transmission may be with a plurality of repetitions (2, 4, 8 or more repetitions).

[0296] The PUSCH transmission may be with / during a plurality of slots (2, 4, 8 or more slots).

[0297] 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 sixth DCI and / or a 'Time domain resource assignment' field value m indicatedby the second DOI (e.g., K2). As shown in FIG. 17A and FIG. 17B, the occasion for the PUSCH transmission (e.g., the slot p) may be a PUCCH occasion / resource for transmission of at least one 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, e.g., based on at least one of a PUCCH resource indicator (PRI) of the fifth DCI and / or a reception occasion / slot of the TB / PDSCH and / or "PDSCH-to-HARQ_feedback timing indicator" filed of the fifth DCI. The at least one HARQ-ACK information may comprise the HARQ-ACK information.

[0298] In response to the PUCCH resource / occasion (for transmitting the at least one HARQ-ACK information) overlapping / collid in g (in time domain) with at least one symbol of the PUSCH resource / occasion, the wireless device may determine whether to multiplex the at least one 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).

[0299] The wireless device may determine the PUCCH resource / occasion based on the fifth DCI scheduling / triggering the TB / PDSCH reception.

[0300] FIG. 17A shows an example that the wireless device may multiplex the at least one 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. 17B shows an example that the wireless device may avoid / skip multiplexing (or not multiplex) the at least one 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 at least one HARQ-ACK information in the PUSCH transmission or not).

[0301] As shown in FIG. 17A, in response to the PUCCH resource / occasion colliding / overlapping 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 at least one HARQ-ACK information in the PUSCH transmission. The wireless device may multiplex the at least one HARQ-ACK information in the PUSCH transmission via / using rate matching or puncturing or other techniques).

[0302] The wireless device may determine to multiplex the at least one HARQ-ACK information (e.g., ACK / NACK value corresponding to the TB / PDSCH with the enabled HARQ-ACK information) in the PUSCH transmission based on a downlink assignment index / indicator / ID (ADI or UL-ADI or a tDAI) field (with value V) of the sixth 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 VTUQA| = 1), the wireless device may determine to multiplex the at least one HARQ-ACK information in the PUSCH transmission.

[0303] In the example of FIG. 17A and / or FIG. 17B, the at least one HARQ-ACK information may comprise a first NACK value. For example, the wireless device may u nsuccessfu lly / incorrectly decode the TB / PDSCH scheduled by the fifth DOI.

[0304] In other examples, the at least one HARQ-ACK information may comprise a first ACK value. For example, the wireless device may successfully / correctly decode the TB / PDSCH scheduled by the fifth DCI.

[0305] The wireless device may determine whether 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 sixth 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 VTUQA| = 1), the wireless device may determine the at least one multiplexing condition being satisfied.

[0306] In another example, when the one or more configuration parameters configure / indicate the Type-2 (semistatic) HARQ-ACK codebook and the DAI value is not equal to 4 (e.g., V<4 or VTUQA| < 4), the wireless device may determine to multiplex the at least one HARQ-ACK information in the PUSCH transmission. 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 VTUQA| < 4), the wireless device may determine the at least one multiplexing condition being satisfied.

[0307] In response to the at least one multiplexing condition being satisfied, the wireless device may multiplex the at least one HARQ-ACK information in the PUSCH. In response to the at least one multiplexing condition being satisfied, the wireless device transmit the PUSCH transmission (comprising the at least one HARQ-ACK information) and / or drop the transmission of the PUCCH.

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

[0309] 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 VTUQA| (or V).

[0310] As shown in FIG. 17B, 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 VTUQA| = 0), e.g., the at least one multiplexing condition not being satisfied, the wireless device may avoid / skip / ignore multiplexing (or determine not to multiplex) the at least one HARQ-ACK information in the PUSCH transmission. As shown in FIG. 17B, when the one or more configuration parameters configure / indicate the Type-1 (semi-static) HARQ-ACK codebook and the DAI value is zero (e.g., V=0 or VTUQA| = 0), the wireless device may determine the at least one multiplexing condition not being satisfied.

[0311] 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 VTUQA| = 4), the wireless device may determine the at least one multiplexing condition not being satisfied. 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 VTUQA| = 4), e.g., the at least one multiplexing condition not being satisfied, the wireless device may avoid / skip / ignore multiplexing (or determine not to multiplex) multiplex the at least one HARQ-ACK information in the PUSCH transmission.

[0312] In response to not multiplexing the HARQ-ACK information in the PUSCH, 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).

[0313] In response to 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).

[0314] PUCCH and PUSCH transmissions may be of the same priority index (e.g., priority index of zero or priority index of 1).

[0315] In other implementations, PUCCH and PUSCH transmissions may be of different priority indexes. For example, priority index of the PUCCH transmission may be smaller than the priority index of the PUSCH transmission. In another example, the priority index of the PUCCH transmission being greater / larger than the priority index of the PUSCH transmission.

[0316] In some examples, for a PUCCH with a first priority index and a 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.

[0317] In some other examples, for a 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. The first priority index may be different than the second priority index.

[0318] In some other examples, for a 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. The first priority index may be the same as the second priority index.

[0319] FIG. 18A, and FIG. 18B 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 the at least one HARQ-ACK information.

[0320] 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 sixth DOI (triggering transmission of the PUSCH). The wireless device may (based on failing to detect the fifth DOI during / within the at least one PDCCH monitoring occasion) may not be able to determine the PUCCH resource. The wireless device may (based on failing to detect the fifth DCI during / within the at least one PDCCH monitoring occasion) may not be able to determine / identify whether the PDSCH / TB is scheduled or not or PDSCH / TB reception occasion. When the wireless device fails to detect / receive the fifth DCI during / within the at least one PDCCH monitoring occasion, the wireless device may determine / identify the PUCCH occasion based on the second DCI and / or the one or more configuration parameters.

[0321] As shown in FIG. 18A, and FIG. 18B, the PUSCH occasion / resource may not collide with the PUCCH resource (as the wireless device is not able to determine the PUCCH resource / occasion due to failure in detecting the fifth DCI). Based on the sixth DCI indicating the DAI value V and the PUSCH occasion, the wireless device may determine the at least one DCI (e.g., the fifth 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 fifth DCI).

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

[0323] Corresponding to FIG. 18A, and FIG. 18B, although the wireless device fails to detect the fifth DCI, the wireless device may, based on the sixth 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). Although the wireless device fails to detect the fifth DCI, the wireless device may, based on the sixth DCI indicating the DAI value V, determine whether the at least one multiplexing condition is being satisfied or not.

[0324] The base station based on indicating the DAI filed in the sixth DCI allows the wireless device to determine that itfailed / missed detecting the fifth DCI. Indicating the DAI filed in the sixth DCI may improve robustness against DCI miss detection of the at least one DCI (e.g., the fifth DCI).

[0325] As shown in FIG. 18A, 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 sixth DCI) the at least one DCI (the fifth 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 multiplexing 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 sixth 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 VTUQA| < 4); and / or the DAI filed of the sixth DOI 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

[0326] The wireless device may multiplex the at least one HARQ-ACK 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 at least one multiplexing condition being satisfied. The at least one HARQ-ACK information may comprise a second NACK value. The second NACK value is based on not receiving / detecting the at least one DCI (the fifth DCI) and / or the at least one TB / PDSCH (scheduled by the fifth DCI). The second NACK value may correspond to / associated with / for a PDCCH monitoring occasion of the at least one PDCCH monitoring occasion when the wireless device fails to detect the at least one DCI in / during the PDCCH monitoring occasion of the at least one PDCCH monitoring occasion.

[0327] The at least one HARQ-ACK information may comprise a second HARQ-ACK information. The second HARQ-ACK information may comprise the second NACK value.

[0328] As shown in FIG. 18B, 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 sixth DCI) the at least one DCI (the fifth 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 multiplexing indication (mux-HARQ- ACK-withoutPUCCH-onPUSCH); and / or the DAI filed of the sixth 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 VTUQA| = 4); and / or the DAI filed of the sixth DCI indicating a DAI value equal to 0 (e.g., when the one or more configuration parameters configure / indicate the Type-1 HARQ-ACK codebook and the DAI value is equal

[0329] Based on the at least one multiplexing condition being satisfied, the wireless device may multiplex the at least one HARQ information comprising the second NACK value in the PUSCH transmission.

[0330] Based on the first multiplexing indication not being indicated / configured (by the one or more configuration parameters), the wireless device may determine the at least one multiplexing condition not being satisfied. Based on the first multiplexing indication not being indicated / configured (by the one or more configuration parameters), the wireless device may determine multiplexing of the at least one HARQ-ACK information without PUCCH (resource) on PUSCH transmission not being enabled / indicated / allowed. Based on the first multiplexing indication not being indicated / configured (by the one or more configuration parameters), the wireless device may determine multiplexing of the at least one HARQ-ACK information without PUCCH (resource) on PUSCH transmission being disabled.

[0331] In some examples, 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 PDSCH / TB receptions.

[0332] Although not shown in FIG. 17A and / or FIG. 17B and / or FIG. 18A and / or FIG. 18B, 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 is a CG-PUSCH transmission and / or the PUSCH transmission is not scheduled the sixth DCI. The sixth DCI may activate a Type-2 configured grant configuration.

[0333] 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') and the PUCCH occasion overlaps with the PUSCH transmission (e.g., the CG-PUSCH transmission), 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 at least one 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.

[0334] In other implementations (not shown in FIG. 17A and / or FIG. 17B and / or FIG. 18A and / or FIG. 18B), the sixth DCI may not comprise / include a DAI filed. 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') and the PUCCH occasion overlaps with the PUSCH transmission scheduled by the sixth DCI 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.

[0335] 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-HARQ_feedback 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. The one or more configuration parameters may comprise / indicate dl-DataToUL-ACK or dl-DataToUL-ACK- r16. The one or more configuration parameters may comprise / indicate dl-DataToUL-ACK-r17 if the PDSCH-to- HARQJeedback timing indicator field is not present in DCI format 1_1 or DCI format 1_3. The one or more configuration parameters may comprise / indicate a 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. The one or more configuration parameters may comprise / indicate a value of dl-DataToUL-ACK if the PDSCH-to-HARQ_feedback timing indicator field is not present in DCI format 4_2.

[0336] The TCI state update may be based on receiving an eighth DCI. The eight DCI may indicate the TCI state.

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

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

[0339] The at least one multiplexing condition may not be satisfied based on the PUCCH occasion / resource (or the at least one HARQ-ACK information) being only associated / corresponding to receiving only a 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. For example, the one or more configuration parameters may configure / indicate pdsch-HARQ-ACK- Codebook = 'semi-static' for unicast / multicast receptions.

[0340] When the Type-1 HARQ-ACK codebook is configured and V=0 (e.g., the DAI filed of the sixth DCI is 0, e.g., VTUQA| = 0), the wireless device may determine the at least one multiplexing condition being satisfied based on at least one of the following: receiving only a SPS PDSCH release; and / or receiving only unicast SPS PDSCH(s) associated with transport blocks having enabled HARQ-ACK information report; and / or receiving only a TCI state update; and / or receiving 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; and / or receiving only multicast SPS PDSCH(s) with transport blocks having enabled associated HARQ-ACK information report or scheduled by a DCI format 4 J (e.g., with a counter DAI field value of 1) having enabled associated HARQ-ACK information report.

[0341] 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 at least one of the following: a value VTU^ of the DAI field (e.g., V) associated with the unicast HARQ-ACK information being VTU^ = 1 and / or a value VTU^ of the DAI field associated with the multicast HARQ-ACK information being VTU^ = 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) comprising the at least one HARQ-ACK information.

[0342] 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 at least one of the following: a value VTU^ of the DAI field (e.g., V) associated with the unicast HARQ-ACK information being VTU^ = 0 and / or a value VTUQ“ of the DAI field associated with the multicast HARQ-ACK information being VTUQ“ = 0.

[0343] For pdsch-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 PUSCH transmission not being scheduled by a DOI format (e.g., the sixth DOI), e.g., the PUSCH transmission is a CG-PUSCH transmission; and / or the PUSCH transmission being scheduled by a DCI format (e.g., the sixth DCI) not including / comprising a DAI field; and / or not receiving (e.g., prior to / before or no later than the sixth 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 sixth 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 sixth 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 sixth DCI) at least one SPS PDSCH reception corresponding to feedback-enabled HARQ processes.

[0344] For pdsch-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 sixth DCI) that includes / comprises a (or at least one) DAI field for unicast / multicast PDSCH receptions with value VTUQA| = 4 (e.g., V=4); and / or the wireless device not receiving, prior to / before / no later than the sixth 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 sixth 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 sixth 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 sixth 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 sixth DCI) at least one SPS PDSCH reception corresponding to feedback-enabled HARQ processes.

[0345] For pdsch-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 being satisfied based on at least one of the following: the PUSCH transmission not being scheduled by a DCI format (e.g., the sixth 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 sixth DCI) notincluding / comprising a DAI field; and / or receiving (e.g., prior to / before or no later than the sixth DOI and within / during PDCOH monitoring occasions) at least one DOI formats scheduling PDSCH / TB receptions; and / or receiving (e.g., prior to / before or no later than the sixth DOI and within / during PDCOH monitoring occasions) a DOI 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 sixth DOI) at least one (all) SPS PDSCH reception corresponding to feedbackdisabled HARQ processes; and / or receiving (e.g., prior to / before or no later than the sixth DOI) at least one SPS PDSCH reception corresponding to feedback-enabled HARQ processes.

[0346] For pdsch-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 sixth DCI) that includes / comprises a (or at least one) DAI field for u nicast / mu Iticast PDSCH receptions with value VTUQA| < 4 (e.g., V<4 or not equal to 4); and / or the wireless device receiving, prior to / before / no later than the sixth 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 sixth 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 sixth 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 sixth 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 sixth DCI) at least one SPS PDSCH reception corresponding to feedback-enabled HARQ processes.

[0347] A wireless device may, in response to the at least one multiplexing condition 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) comprising the at least one HARQ-ACK information.

[0348] 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 / unicast) Type-1 HARQ-ACK codebook. For example, the wireless device may generate the (multicast / unicast) Type-1 HARQ-ACK codebook based on the at least one HARQ-ACK codebook generation condition being satisfied.

[0349] Based on the at least one multiplexing condition not being satisfied, the wireless device may determine the at least one HARQ-ACK codebook generation condition not being satisfied. Based on the at least one multiplexingcondition not being satisfied, the wireless device may avoid / skip / ignore generating / creating / producing / building / constructing (or not generate) a Type-1 HARQ-ACK codebook.

[0350] 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 the at least one HARQ-ACK information in the PUSCH transmission. Based on the at least one multiplexing condition being satisfied, 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.

[0351] In some implementations, for transmission of the PUSCH, a wireless device may determine the at least one HARQ-ACK codebook generation condition being satisfied or not. 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.

[0352] 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 sixth 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 sixth DCI); and / or only a TCI state update (e.g., the eights DCI) being received (e.g., prior to / before receiving the sixth 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_1 with counter DAI field value of 1 on the PCell being received (e.g., prior to / before receiving the sixth DCI).

[0353] 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 sixth 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 sixth DCI); and / or no TCI state update (e.g., via the eighth DCI) being received (e.g., prior to / before receiving the sixth 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 J with counter DAI field value of 1 on the PCell being received (e.g., prior to / before receiving the sixth DCI).

[0354] 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 sixth 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 format 4_1 with counter DAI field value of not equal to 1 on the PCell being received (e.g., prior to / before receiving the sixth DCI).

[0355] 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 at least one HARQ-ACK information). 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, the HARQ- ACK information 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 of the at least one HARQ-ACK information corresponding to PDSCH reception or SPS PDSCH release or TCI state update (e.g., the eights DCI) that the wireless device detects in a PDCCH monitoring occasion that starts after receiving / detecting the sixth DCI (e.g., in / during a PDCCH monitoring occasion that the wireless device detects the sixth DCI format scheduling / activating / triggering the PUSCH transmission).

[0356] 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 one or more of the following: failing to receive (or detect) a first / initial / starting SPS-PDSCH reception of the SPS-PDSCH receptions; and / or the one or more configuration parameters indicating / configuring harq-feedbackEnablingforSPSactive = 'enabled'; and / or a HARQ process corresponding to the first / initial / starting SPS-PDSCH reception occasion being a feedback-disabled HARQ process.

[0357] After receiving a DCI activating SPS-PDSCH receptions, the wireless device may, based on the at least one multiplexing condition being satisfied, multiplex the at least one HARQ-ACK information comprising a third NACK value in the CG-PUSCH transmission. The third NACK value may correspond to failing to receive (or detect) a first / initial / starting SPS-PDSCH reception when the one or more configuration parameters indicates / configures harq- feedbackEnablingforSPSactive = 'enabled' and a HARQ process corresponding to the first / initial / starting SPS-PDSCH reception occasion is the feedback-disabled HARQ process.

[0358] A DAI field of the fifth DCI may correspond to a unicast HARQ-ACK information () of the at least one HARQ- ACK information. The fifth DCI may schedule / indicate unicast PDSCH / TB receptions.

[0359] A DAI field of the fifth DCI may correspond to a multicast HARQ-ACK information of the at least one HARQ- ACK. The fifth DCI may schedule / indicate multicast PDSCH / TB receptions.

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

[0361] When a wireless device transmits the PUSCH transmission (scheduled by a DCI format, e.g., the sixth 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 applicable for multiplexing the at least one HARQ-ACK information in the PUSCH transmission in any slot from the multiple slots where the wireless device may multiplex the HARQ-ACK information.

[0362] FIG. 19 shows an example of configuration of a search space (e.g., SearchSpace IE). FIG. 19 may show an example of configuration parameters configuring SSS groups. FIG. 20 shows an example of search space switching procedure per an aspect of an embodiment of the present disclosure. As shown in FIG. 20, a wireless device may receive the one or more configuration parameters from a base station. The one or more configuration parameters may comprise the one or more PDCCH configuration parameters and / or the configuration parameters configuring SSS groups. The configuration parameters configuring SSS groups may comprise / be one or more SSS configuration parameters. For example, the one or more SSS configuration parameters may comprise configuration of the search space. The one or more configuration parameters (e.g., the one or more PDCCH configuration parameters) may comprise the one or more SSS configuration parameters. Monitoring the PDCCH in FIG. 20 may be based on the preslot or per-span or multi-slot PDCCH monitoring mode / state.

[0363] The one or more SSS configuration parameters may, for example, comprise at least one of: a search space ID (searchSpaceld); and / or a control resource set ID (control ResourceSetld); and / or a monitoring slot periodicity and offset parameter (monitoringSlotPeriodicityAndOffset); and / or a search space time duration value (duration); and / or a monitoring symbol indication (mon itoringSymbolsWith inSlot); and / or a number of candidates for an aggregation level (nrofCandidates); and / or a SSS type (e.g., the CSS or the USS). The monitoring slot periodicity and offset parameter may indicate slots (e.g., in a radio frame) and slot offset (e.g., related to a starting of a radio frame) for PDCCH monitoring for the per-slot / per-span / multi-slot modes / states. The monitoring symbol indication may indicate on / during which symbol(s) of a slot a wireless device may monitor PDCCH on the SSS. The control resource set ID may identify a control resource set on which the SSS may be located.

[0364] As shown in FIG. 19 and FIG. 20, the one or more SSS configuration parameters may indicate / configure one or more SSS groups. For example, the one or more SSS configuration parameters may indicate / configure a list (or plurality) of search space group indexes (or IDs / identifies) that the SSS (with the search space ID) is associated with. A search space group index (or a group index) of the list of the search space group indexes may correspond to / be for the SSS group for PDCCH monitoring on the serving cell. For example, A search space group index (or a group index) of the list of the search space group indexes may correspond to / be for an SSS (e.g., a Type3-PDCCH CSS set, a USS set, or any other type of search space set) of an SSS group. The group index / ID may be 0 or 1 or 2 or the like, e.g., depending on how many search space groups are configured by the one or more SSS configuration parameters.

[0365] The one or more PDCCH configuration parameters (e.g., PDCCH-Config) may indicate / configure a first plurality of cell groups (e.g., cellGroupsForSwitchList) for SSS switching procedure / purpose. The first plurality of cell groups may indicate / provide / configure a list of serving cells which are bundled for the search space group switching purpose. A serving cell of the first plurality of cell groups may belong to only one cell group CellGroupForS witch. The base station / network may configure a same list cellGroupsForSwitchList for all configured BWPs of the serving cells in the same cell group CellGroupForSwitch.

[0366] In an example, the one or more SSS configuration parameters may indicate / comprise a search space (SS) switch (or switching) delay (searchSpaceSwitch Delay) with a number of symbols PswitCh ■ The SS switch delay may indicate a switching delay (or offset or gap), e.g., in a number of symbols, for switching among SSSs corresponding to the search space group indexes. The base station may determine the SS switch delay a processing capability of the wireless device (e.g., wireless device processing capability 1, wireless device processing capability 2, etc.) and / or SOS configuration |i. In an example, PSWitCh=25 for a processing capability 1 and p=0, Pswitch=25 for a processing capability 1 and |i=1, PSWitCh=25 for a processing capability 1 and |i=2, PSWitCh =10 f°r aprocessing capability 2 and |i=0, PSWjtch =12 for a processing capability 2 and p=1 , and PSWitCh =22 for a processing capability 2 and |i=2, etc.

[0367] When the searchSpaceGroupIdList for a search space set is not configured / indicated, the wireless device may monitor the search space set on a BWP, without switching away from the search space set for PDCOH monitoring. As also shown in FIG. 20, if the cellGrou psForSwitch List is configured / indicates, the wireless device may switch across / among / between the search space groups (e.g., only to a serving cell for which the wireless device is provided searchSpaceGroupIdList), e.g., based on control information (e.g., a DOI) or RRC configuration.

[0368] As shown in FIG. 20, initially or after the receiving the one or more SSS configuration parameters (e.g., RRC configuration), the wireless device may monitor the PDCOH (candidates / occasions) based on (or using or according to) a first SSS group of the one or more SSS groups. For example, monitoring the PDCOH on the first SSS group may be based on the one or more PDCOH configuration parameters of a BWP of a cell (e.g., the serving cell). The first SSS group may be a default SSS group. The first SSS group may have a first SSS group index / ID. The first SSS group I D / index may be 0. The wireless device may reset the PDCOH monitoring according to search space sets with group index 0 of the list of search space group indexes (searchSpaceGroupIdList).

[0369] As shown in FIG. 20, while the wireless device is monitoring the PDCOH according to / on the first SSS group, the wireless device may receive (from the base station) a first DOI. The first DOI may indicate / trigger a SSS group switching. For example, the first DOI may indicate switching from the first SSS group to a second SSS group. For example, the wireless device may, based on the first DOI, switch from the first SSS group to a second SSS group. In response to the first DOI, the wireless device may start monitoring the PDCOH (candidates / occasions) the SS switch delay after receiving the first DOI according to the second SSS group. The wireless device may, based on the first DOI, stop monitoring the PDCOH (candidates / occasions) according to the first SSS group.

[0370] The first DOI may have a DOI format. The DOI format may be a DOI format 0_1 or 0_2 or 1 J or 1_2 or the like. The first DOI may schedule / indicate / trigger a PDSCH reception or a PUSCH transmission. For example, the first DOI may comprise a first field. The first filed may indicate a value or a first indication (e.g., SSS switch indication or SSS group switch indication). The first field may be a “PDCOH monitoring adaptation indication”. The first filed may indicate 0 or 1 or 2 bits. The second SSS group may be different than the first SSS group. For example, the second SSS group may have a second SSS group I D / index. The second SSS group ID may be different than the first SSS group ID.

[0371] The PDCCH monitoring adaptation field of the first DOI may indicates to the wireless device to start PDCCH monitoring according to search space sets with a second group index (e.g., the second SSS group) and stop PDCCH monitoring according to search space sets with the first group index (e.g., the first SSS group).

[0372] In some cases, the first DCI may be a group-common DCI. For example, the first DCI may have a DCI format 2_0. The DCI format 2_0 may comprise one or more SSS group (or SSSG) switching indications (or search space set group switching flags). The DCI format 2_0 may comprise at least one of the following: one or more slot format indicator (e.g., slot format indicator 1, slot format indicator 2, ... slot format indicator N); and / or one or more available RB set indicators; and / or one or more COT duration indications, and / or the one or more SSS group switching flags. Each of the one or more SSS group switching flags may correspond to a respective cell group of the first plurality of cell groups. Each cell group of the plurality of cell groups may comprise one or more cells. The one or more cells may comprise the serving cell. A SSS group switching flag with a first value may indicate switching from the first SSS group to the second SSS group for each cell (e.g., the serving cell) of the cell group. The SSS group switching flag with a second value may indicate a switching from the second SSS group to the first SSS group for each cell (e.g., the serving cell) of the cell group. As also shown in FIG. 19, the one or more SSS configuration parameters may comprise / indicate an SS switch trigger (SearchSpaceSwitchTrigger). The SS switch trigger may indicate / configure a location of a search space set group switching flag field for a serving cell (of the first plurality of cell groups) in a DCI format 2_0.

[0373] As also shown in FIG. 20, when / z e {0, 1, 2, 3} (e.g., for per-slot or per-span PDCCH monitoring mode or regime or state), based on / in response to the first DCI, the wireless device may apply the first indication at a beginning / start of a fi rst / ini tial / earliest / startin g slot that is at least the SS switch delay (e.g., PswitCh symbols) after a last / fin al / endin g / latest symbol of a PDCCH reception (or PDCCH monitoring occasion) providing the first DCI format with the PDCCH monitoring adaptation field. For example, the wireless device may detect / receive the first DCI in / during the PDCCH monitoring in a slot n. The wireless device may switch from the first SSS group to the second SSS group at the beginning of a slot n+3. The wireless device may, based on the first DCI and at the beginning of the slot n+3, switch from the first SSS group to the second SSS group for monitoring PDCCH after the switch delay from the PDCCH reception in the slot n.

[0374] As also shown in FIG. 20, when / z e {5, 6} (e.g., for multi-slot PDCCH monitoring mode or regime or state), based on / in response to the first DCI, the wireless device may apply the first indication at a beginning / start of a first / initial / earliest / starting slot, of a slot group of Xsslots, that is at least the SS switch delay (e.g., PswitCh symbols) after a last / final / ending / latest symbol of a PDCCH reception (or PDCCH monitoring occasion) providing the first DCI format with the PDCCH monitoring adaptation field. For example, the wireless device may detect / receive the first DCI in / during the PDCCH monitoring in a slot n in a slot group n comprising Xsslots. The wireless device may switch from the first SSS group to the second SSS group at the beginning of the first slot of a slot group n+3 comprising Xsslots. The wireless device may, based on the first DCI and at the beginning of the first slot of the slot group n+3, switch fromthe first SSS group to the second SSS group for monitoring PDCCH after the switch delay from the PDCCH reception in the slot group n+3. As shown in FIG. 20, when / z e {5, 6}, the first slot of the slot group n+3 may be a slot n+11.

[0375] In some implementations, the one or more SSS configuration parameters may indicate / comprise an SS switch (or switching) timer (or window or duration or period) (searchSpaceSwitchTimer) in units of slots. The SS switch timer may indicate a timer value for a serving cell that the wireless device is provided searchSpaceGroupId List. For example, the SS switch timer may indicate a timer value for a set of serving cells of the first plurality of cell groups (cellGroupsForSwitchList). The searchSpaceSwitchTimer may be defined as a value in unit of slots for monitoring PDCCH in the active DL BWP of the serving cell before moving to the default SSS group (e.g., the SSS group 0). For 15 kHz SCS, a valid timer value for the SS switch timer may be one of {1. ... , 20}. For 30 kHz SCS, a valid timer value for the SS switch timer may be one of {1 , .... 40}. For 60kHz SCS, a valid timer value for the SS switch timer may be oneof {1, .... 80}. In an example, the base station may configure a same timer value for all serving cells in the same CellGroupForSwitch of the first plurality of cell groups.

[0376] As shown in FIG. 20, the wireless device may start the SS switch timer based on receiving the first DCI. The wireless device may set the SS switch timer with a value indicate by the one or more SSS configuration parameters (searchSpaceSwitchTimer), e.g., is response to receiving the first DCI. The wireless device may, based on the first DCI indicating the switching from the first SSS group to the second SSS group, set the SS switch timer with the value indicate by the one or more SSS configuration parameters (searchSpaceSwitchTimer). The wireless device may start the SS switch timer the SS switch delay symbols after the PDCCH monitoring occasion providing the first DCI. For example, the wireless device may start the SS switch timer in the slot n+3 when / z e {0, 1, 2, 3} or the slot n+11 when / z e {5, 6}. The wireless device may start the SS switch timer based on the first DCI indicating switching from the first SSS group to the second SSS group. The Wireless device may monitor the PDCCH according the second SSS group while the SS switch timer is running (not being expired or stopped).

[0377] The wireless device may decrement the timer value of the SS switch timer by one after each slot based on a reference subcarrier spacing (SCS) configuration (e.g., CSC_ref) . In the present disclosure, decrementing the timer value of the SS switch timer by one after each slot may be referred by “SS switch timer decrement procedure”. The SS switch timer decrement procedure may comprise keep running the SS switch timer and / or decrementing the SS switch timer while it is running. The wireless device may determine the reference SCS configuration based on a smallest / lowest / minimum SCS configuration |i among all configured DL BWPs in the serving cell. For example, the wireless device may determine the reference SCS configuration based on the smallest SCS configuration |i among all configured DL BWPs in the set of serving cells. The set of serving cells may be configured by the first plurality of cell groups.

[0378] The wireless device may maintain the reference SCS configuration during the SS switch timer decrement procedure. The wireless device may avoid changing / updating the reference SCS configuration to a first SCS configuration during the SS switch timer decrement procedure. For example, while the SS switch timer is running, alength of the slot (in ms) for decrementing the SS switch timer may be based on the reference SOS configuration. In another example, while the SS switch timer is running, the wireless device may use the same reference SOS configuration for decrementing the SS switch timer by one after each slot. In yet another example, while the SS switch timer is running, the wireless device may not use two different reference SOS configuration (e.g., the reference SOS configuration and the first SOS configuration) for decrementing the SS switch timer by one after each slot.

[0379] In response to an expiry of the SS switch timer, the wireless device may switch from the second SSS group to the first SSS group. For example, the wireless device may switch to the first SSS group from the second SSS group after the SS switch delay from the expiry of the SS switch timer.

[0380] In response to an expiry of the SS switch timer, the wireless device may start monitoring the PDCOH according to the first SSS group. For example, the wireless device may start monitoring the PDCOH according the first SSS group after the SS switch delay from the expiry of the SS switch timer. The wireless device may stop monitoring the PDCOH according to the second SS group in response to the expiry of the SS switch timer.

[0381] When n e {0, 1, 2, 3} (e.g., for per-slot or per-span PDCCH monitoring mode or regime or state or mechanism), based on / in response to an expiry of the SS switch timer in a first symbol, the wireless device may switch from the second SSS group to the first SSS group at a beginning / start of a f irst / in itial / earl iest / starting slot that is at least the SS switch delay (e.g., PswitCh symbols) after the first symbol. For example, the wireless device may determine the SSS switch timer being expired in the first symbol (e.g., symbol 5 or the like) of a slot r. The wireless device may switch from the second SSS group to the first SSS group at the beginning of a slot q. The slot q may be at least the SS switch delay from the first symbol of the slot r.

[0382] When n e {5, 6} (e.g., for multi-slot PDCCH monitoring mode or regime or state or mechanism), based on / in response to the expiry of the SS switch timer in the first symbol, the wireless device may switch from the second SSS group to the first SSS group at a beginning / start of a first / in itial / earliest / startin g slot, of a slot group of Xsslots, that is at least the SS switch delay (e.g., PswitCh symbols) after the first symbol.

[0383] The base station may, during the SS switch delay from the expiry of the SS switch timer, not transmit (or avoid transmitting) a third DCI indicating switching from the first SSS group to the second SSS group.

[0384] Alternatively, the base station may, during the SS switch delay from the expiry of the SS switch timer, transmit the third DCI indicating switching from the first SSS group to the second SSS group. For example, the wireless device may, from the base station and during / within the SS switch delay from the expiry of the SS switch timer, receive the third DCI. The wireless device may, during the SS switch delay from the expiry of the SS switch timer, avoid / ignore switching from the first SSS group to the second SSS group.

[0385] In some implementations, the wireless device may avoid / skip starting (or not start) the SS switch timer based on the first DCI indicating switching from the second SSS group to the default SSS group (e.g., the SSS group with index 0).

[0386] FIG. 21 A shows a flowchart of a PDCOH monitoring according to search space sets per an aspect of an embodiment of the present disclosure. Embodiment of FIG. 21 A may provide one or more additional aspects (steps) of / for embodiment of FIG. 20 discussed above. Similar to embodiment of FIG. 20, the wireless device may receive the first DOI indicating switching from a first SSS group to a second SSS group. For example, the wireless device may receive the first DOI while monitoring the PDCOH according to the first SSS group. In response to the first DOI, the wireless device may determine an occasion for switching from the first SSS group to the second SSS group. The occasion may be a symbol in a slot. For example, the wireless device may determine the slot and / or the symbol in the slot. The wireless device may determine the occasion corresponding to a serving cell. The wireless device may receive a PDCOH during a PDCOH monitoring occasion in / via the serving cell. The wireless device may detect during the PDCOH monitoring the first DOI indicating the switching from the first SSS group to the second SSS group. For example, the DOI may have the DOI format 2_0. In one example, the one or more SSS configuration parameters (e.g., search SpaceGroupIdList) may indicate the serving cell. In another example, the one or more SSS configuration parameters (e.g., cellGroupsForSwitchList) may indicate / configure the set of serving cells (e.g., the first plurality of cell groups).

[0387] The wireless device may start monitoring PDCCH according to the second SSS group starting from the occasion. The wireless device may stop monitoring PDCCH according to the first SSS group no later than the occasion. As shown in FIG. 21A, the wireless device may determine the occasion based on the reference SCS and / or a maximum / largest / greatestXs. In one implementation, when / if / z e {0, 1, 2, 3}, the wireless device may determine occasion based on the smallest CSC configuration |i among all configured DL BWPs in the serving cell and / or the set of serving cells. In another implementation, when / if the SCS configuration / z among all configured DL BWPs in the set of serving cells is not equal to 6 (or is smaller than 6, e.g., / z < 6), the wireless device may determine the occasion based on the smallest CSC configuration p among all configured DL BWPs in the serving cell and / or the set of serving cells. In yet another implementation, when / if the SCS configuration / z among all configured DL BWPs in the set of serving cells equals to 6 (e.g., / z = 6), the wireless device may determine the occasion based on the maxi mu m / largest / greatest Xs.

[0388] In some cases, the determined occasion (based on / using the embodiment of FIG. 21A) may be the slot n+3 or the slot n+11 in FIG. 20.

[0389] FIG. 21A shows a flowchart of a PDCCH monitoring according to search space sets per an aspect of an embodiment of the present disclosure.

[0390] FIG. 21 B shows a flowchart of a search space switch timer per an aspect of an embodiment of the present disclosure. Embodiment of FIG. 21 B may provide one or more additional aspects (steps) of / for embodiment of FIG. 20 discussed above. Although not shown in FIG. 21 B, the wireless device may receive the one or more PDCCH configuration parameters (via the serving cell). For example, the one or more SSS configuration parameters may indicate / configure group indexes for a Type3-PDCCH CSS set or an USS set by searchSpaceGroupldList-r17.

[0391] The one or more SSS configuration parameters may configure / indicate the timer value by searchSpaceSwitchTimer-r17 for PDCCH monitoring (of / on) an active DL BWP of / for / corresponding to on a serving cell. The wireless device may determine the SS switch timer being running. For example, the wireless device may start the SS switch timer according to embodiment of FIG. 20 discussed above.

[0392] While the SS switch timer is running, the wireless device may perform the SS switch timer decrement procedure. While the SS switch timer is running and during (or at a start / beginning) of a first slot (of the active downlink BWP of the serving cell), the wireless device may, to perform the SS switch timer decrement procedure and may determine whether to decrement the SS switch timer (e.g., by one) or no. As shown in FIG. 21 B, the wireless device may determine whether a second DOI during the first slot being detected / received or not. For example, the second DOI may have a DOI format (e.g., DOI format 1 J or 1_2 or the like). The second DOI may have a ORO scrambled by a first RNTI. The first RNTI may be one of C-RNTI / CS-RNTI / MOS-C-RNTI / G-RNTI for multicast / G-CS-RNTI. The second DOI may not be a group-common DOI (e.g., DOI format 2_0). The second DOI may not indicate a switching SSS group (e.g., from the second SSS group to a third SSS group). The second DOI may not comprise the first filed. In some cases, the bit width of the first field of the second DOI may be 0.

[0393] The wireless device may detect the second DOI during / within / in a PDCCH monitoring occasion of / in the first slot. As shown in FIG. 21 B, in response to detecting the second DCI while the SS switch timer is running, the wireless device may reset (or restart) the SS switch timer after the first slot of the active DL BWP of the serving cell. In an example embodiment, the wireless device may reset the SS switch timer after the first slot based on the reference SCS configuration. For example, in response to detecting the second DCI while the SS switch timer is running, the wireless device may restart / reset the SS switch timer decrement procedure. The wireless device may, after resetting the SS switch timer, decrement the timer value of the SS switch timer by one after each slot (as discussed above related to embodiment of FIG. 20) based on the reference SCS configuration.

[0394] In an example embodiment, the wireless device may maintain the reference SCS configuration in response to resetting the SS switch timer. For example, the SS switch timer decrement procedure may comprise resetting the SS switch timer in response to detecting the second DCI. The wireless device may keep using the determined reference SCS configuration after the resetting the SS switch timer. This allows the wireless device to improve efficiency of search space switching procedure while the SS switch timer is running. Without embodiment of FIG. 21 B, the wireless device may, in response to detecting the second DCI, (re-)determine a new reference SCS configuration and start using the new reference SCS configuration after the resetting the SS switch timer. By using the embodiment of FIG. 21 B, the wireless device may avoid recalcu lating / redeterm inin g the new reference SCS configuration whenever the SS switch timer is reset (or restart) in response to detecting the second DCI. By using the embodiment of FIG. 21 B, processing complexity of the wireless device for SSS switching may reduce.

[0395] As shown in FIG. 21 B, when the wireless device does not detect the second DOI during / within / in a PDCOH monitoring occasion of / in the first slot, the wireless device may keep preforming the SS switch timer decrement procedure.

[0396] FIG. 22A shows an example of search space switch procedure. Embodiment of FIG. 22A may correspond to when n e {5, 6}, e.g., multi-slot PDCOH monitoring mode or regime or state or mechanism. For example, the one or more SSS configuration parameters may indicate / configure the SS switch timer and the SS switch delay (e.g., with length of at least PswitCh symbols). Embodiment of FIG. 22A may provide one or more additional aspects (steps) for / of embodiment of FIG. 20 discussed above.

[0397] FIG. 22A may show an example of determination of whether to switch among search spaces for PDCOH monitoring in response to receiving the third DCI in a second slot (slot m) of a second slot group (e.g., a slot group n+2 in FIG. 22A). Each slot group (e.g., the second slot group or a first slot group) may comprise Xsslots. For example, the wireless device may receive the third DCI in a PDCOH monitoring occasion of / in / during the second slot. As seen in FIG. 22A, the wireless device may determine the SS switch timer being expired in a first slot (e.g., Slot n) of the first slot group (slot group n). In response to receiving the third DCI indicating switching from the first SSS group to the second SSS group, the wireless device may determine whether to switch from the first SSS group to the second SSS group based on whether the second slot is after (or later than) a starting (or initial) slot of a third slot group (slot group n+3 in FIG. 22A) or not. The starting slot of the third slot group (of Xsslots) may be slot q in FIG. 22A. The starting slot of the third slot group may be a beginning / start of a fi rst / ini tial / earliest / starting slot, of the third slot group of Xsslots, that is at least the SS switch delay (e.g., PswitCh symbols) after the expiry occasion / slot / symbol of the SS switch timer (e.g., the first slot). The starting slot of the third slot group may be a beginning / start of a first / initial / earliest / starting slot, of the third slot group of Xsslots, that is at least the SS switch delay (e.g., PswitCh symbols) after a last / ending / final / latest symbol of the first slot.

[0398] In an example embodiment, based on the second slot being before (or prior to or no later than) the third slot, the wireless device may avoid / skip / ignore switching from the first SSS group to the second SSS group. Based on the second slot being before (or prior to or no later than) the third slot, the wireless device may monitor PDCCH according to the first SSS group.

[0399] In an example embodiment, based on the second slot being after (or later than) the third slot, the wireless device may switch from the first SSS group to the second SSS group. Based on the second slot being after (or later than) the third slot, the wireless device may monitor PDCCH according to the second SSS group.

[0400] Using the embodiment of FIG. 22A may allow the wireless device to properly determine whether switch from the first SSS group to the second SSS group based on: the expiry occasion of the SS switch timer and the second slot (where the wireless device receives the second DCI). Without embodiment of FIG. 22A, the wireless device may mistakenly switch to the second SS group, which may reduce efficiency of the PDCCH monitoring or increasing complexing of wireless device.

[0401] FIG. 22B shows an example of search space switch procedure. Embodiment of FIG. 22B may correspond to when n e {5, 6}, e.g., multi-slot PDCCH monitoring mode or regime or state or mechanism. For example, the one or more SSS configuration parameters may the SS switch delay (e.g., with length of at least PswitCh symbols). Embodiment of FIG. 22B may provide one or more additional aspects (steps) for / of embodiment of FIG. 20 discussed above. Embodiment of FIG. 22B may provide one or more additional aspects (steps) for / of embodiment of FIG. 21A discussed above.

[0402] FIG. 22B may show an example of determination of whether to switch among search spaces for PDCCH monitoring in response to receiving the third DCI in a second slot (slot m) of a second slot group (e.g., a slot group n+2 in FIG. 22B). Each slot group (e.g., the second slot group or a first slot group) may comprise Xsslots. For example, the wireless device may receive the third DCI in a second PDCCH monitoring occasion of / in / during the second slot. As seen in FIG. 22B, the wireless device may receive the first DCI in a first slot (e.g., Slot n) of the first slot group (slot group n). For example, the wireless device may receive the first DCI in / during a first PDCCH monitoring occasion in / during the first slot.

[0403] Both the first DCI and the third DCI may comprise the first field.

[0404] The first filed of the first DCI may be with a first value. The first value may indicate to switch from the first SSS group to the second SSS group. The first value may indicate a start of PDCCH monitoring according to the SSSs with the second group index (e.g., the second SSS group) and stop of PDCCH monitoring according to the SSSs with the first group index (e.g., the first SSS group). The second group index may be different than the first group index.

[0405] The first filed of the second DCI may be with a second value. The second value may be different than the first value. The second value may indicate to switch from the first SSS group to a third SSS group. The second value may indicate a start of PDCCH monitoring according to the SSSs with a third group index (e.g., a third SSS group) and stop of PDCCH monitoring according to the SSSs with the first group index (e.g., the first SSS group). The third group index may be different than the second group index. The third group index may be different than the first group index.

[0406] In response to receiving the third DCI indicating switching from the first SSS group to the third SSS group, the wireless device may determine whether to switch from the first SSS group to the third SSS group based on whether the second slot is after (or later than) a starting (or initial) slot of a third slot group (slot group n+3 in FIG. 22B) or not. The starting slot of the third slot group (of Xsslots) may be slot q in FIG. 22B. The starting slot of the third slot group may be a beginning / start of a first / in itial / earliest / startin g slot, of the third slot group of Xsslots, that is at least the SS switch delay (e.g., PswitCh symbols) after the first PDCCH monitoring occasion (e.g., the first slot). The starting slot of the third slot group may be a beginning / start of a fi rst / ini tial / earliest / starting slot, of the third slot group of Xsslots, that is at least the SS switch delay (e.g., PswitCh symbols) after a last / endin g / fi nal / latest symbol of the first slot / P DCCH monitoring occasion.

[0407] In an example embodiment, based on the second slot being before (or prior to or no later than) the third slot and the first value being different than the second value, the wireless device may avoid / skip / ignore switching from thefirst SSS group to the third SSS group. Based on the second slot being before (or prior to or no later than) the third slot and the first value being different than the second value, the wireless device may monitor PDCCH according to the second SSS group from the starting slot of the third slot group. Based on the second slot being before (or prior to or no later than) the third slot and the first value being different than the second value, the wireless device may ignore the first filed of the third DOI.

[0408] Using the embodiment of FIG. 22 B may allow the wireless device to properly switch from the first SSS group to the second SSS group. Without embodiment of FIG. 22B, the wireless device may mistakenly switch to the third SS group (in response to receiving the third DOI), which may reduce efficiency of the PDCCH monitoring or increasing complexing of wireless device.

[0409] FIG. 22C shows an example of PDCCH skipping per an aspect of an embodiment of the present disclosure. The one or more configuration parameters (e.g., the one or more PDCCH configuration parameters) may configure a wireless device to skip (or avoid / stop / terminate) monitoring downlink control channels. To skip monitoring downlink control channels may comprise to skip monitoring PDCCH or to skip PDCCH monitoring or avoid monitoring the PDCCH. To skip monitoring downlink control channels may comprise skipping of the PDCCH monitoring. To skip monitoring downlink control channels may comprise skipping the control channels monitoring. Embodiment of FIG. 22C may provide one or more additional aspects to embodiments of FIG. 20, FIG. 21 A, FIG. 21 B discussed above. In an example, the wireless device may perform PDCCH skipping mechanism for power saving operation.

[0410] The one or more PDCCH configuration parameters (e.g., the PDCCH-Config) may comprise at least one skipping duration / window / period (e.g., pdcch-SkippingDuration List) for PDCCH skipping. The at least one skipping duration (e.g., pdcch-SkippingDuration List) may indicate one or more (PDCCH or control channel) skipping values corresponding to skipping duration in unit of slots (or symbols or ms). For the 15kHz SCS, for each value of the one or more skipping values, only a first 26 skipping values are valid and correspond to {1, 2, 3, .... 20, 30, 40, 50, 60, 80, 100} slots (or symbols or ms). For the 30kHz SCS, for each value of the one or more skipping values, only a first 46 skipping values are valid and correspond to {1, 2, 3, .... 40, 60, 80, 100, 120, 160, 200} slots (or symbols or ms). For the 60kHz SCS, for each value of the one or more skipping values, only the first 86 skipping values are valid and correspond to {1 , 2, 3, .... 80, 120, 160, 200, 240, 320, 400}. For the 120kHz SCS, for each value of the one or more skipping values, the 166 skipping values correspond to {1, 2, 3, .... 160, 240, 320, 400, 480, 640, 800} slots (or symbols or ms). For the 480kHz SCS, for each value of the one or more skipping values, the 166 skipping values correspond to {4, 8, 12, .... 640, 960, 1280, 1600, 1920, 2560, 3200}. For the 960kHz SCS, for each value of the one or more skipping values, the 166 values correspond to {8, 16, 24, .... 1280, 1920, 2560, 3200, 3840, 5120, 6400} slots (or symbols or ms).

[0411] In response to receiving a second indication, the wireless device may skip monitoring PDCCH during the skipping duration on the active DL BWP of a cell (e.g., a serving cell, e.g., a SpCell). The second indication may be a skipping indication. The second indication may indicate skipping PDCCH monitoring for a skipping duration / window(e.g., in a number of slots), of the at least one skipping duration. The second indication may be different than the first indication. The second indication may be based on receiving a fourth DOI in FIG. 220. For example, the fourth DOI may comprise the first filed (e.g., the 'PDCCH monitoring adaptation indication’ filed). The first filed may provide the second indication. The first filed may indicate the skipping duration for the skipping monitoring the PDCCH. In some cases, the first filed may only indicate the first indication or the second indication.

[0412] When the one or more PDCCH configuration parameters configure both the SSS switching procedure and PDCCH skipping procedure, the wireless device may, based on predefined rules, determine whether the first filed is indicating the first indication or the second indication.

[0413] When the one or more PDCCH configuration parameters configure only the SSS switching procedure (e.g., the one or more SSS configuration parameters are provided), the wireless device may determine the first filed is indicating the first indication.

[0414] When the one or more PDCCH configuration parameters configure only the PDCCH procedure (e.g., the one or more SSS configuration parameters are not provided), the wireless device may determine the first filed is indicating the second indication.

[0415] As shown in FIG. 22C, the wireless device may receive the fourth DCI indicating skipping PDCCH with a skipping duration / window (e.g., indicated via the 'PDCCH monitoring adaptation indication’ field). A time value for the skipping window may be indicated by the fourth DCI or configured by the one or more PDCCH configuration parameters (e.g., the at least one skipping duration / window). In response to receiving the fourth DCI, the wireless device may stop monitoring PDCCH on the BWP (e.g., of the serving cell). Stopping monitoring PDCCH on the BWP may comprise stopping monitoring PDCCH (candidates) on one or more SSS groups configured on / for the BWP. The wireless device may maintain an active state of the BWP. The fourth DCI may not indicate an active BWP switching.

[0416] During the skipping window / duration (or when a timer associated with the skipping window is running or not being expired), e.g., during the skipping duration from receiving the fourth DCI, the base station may not transmit PDCCHs / DCIs to the wireless device.

[0417] When the skipping duration expires, the wireless device may resume PDCCH monitoring on the BWP. Resuming PDCCH monitoring may comprise terminating / stopping / cancelling the PDCCH skipping. Resuming PDCCH monitoring may comprise resuming monitoring control channels. Based on / after resuming PDCCH monitoring, the wireless device may receive PDCCHs / DCIs from the base station. In response to an expiry of the skipping window expiring, the base station may transmit one or more PDCCHs / DCIs to the wireless device.

[0418] When the PDCCH monitoring adaptation field of the fourth DCI indicates / includes the second indication, the wireless device may start skipping of PDCCH monitoring (e.g., or stop monitoring the PDCCH) at the beginning of a first / initial / starting slot that is after the last / final / ending symbol of a PDCCH reception providing the fourth DCI. The second indication may indicate to a wireless device to skip PDCCH monitoring for the skipping duration on the active DL BWP of a serving cell. The skipping duration may start from the first / initial / starting slot that is after thelast / final / ending symbol of the PDCCH reception. The wireless device may skip monitoring the PDCCH during the skipping duration from the receiving the fourth DOI.

[0419] If the wireless device transmits a PUCCH providing a positive SR before the wireless device detects / receives the fourth DOI (with the first filed indicating the second indication), the wireless device may monitor PDCCH regardless of PDCCH skipping indication. The second indication may indicate to the wireless device to skip PDCCH monitoring for the skipping duration on the active DL BWP of the serving cell. The wireless device may ignore the second indication based on the positive SR being transmitted prior to receiving the fourth DCI. The wireless device may, after transmitting the positive SR prior to receiving the fourth DCI, monitor the PDCCH on all serving cells of the corresponding Cell Group when / while the SR is pending (when the SR is not cancelled).

[0420] As shown in FIG. 22C, if the wireless device transmits a PUCCH providing a second positive SR after the wireless device detects / receives the fourth DCI indicating the second indication, the wireless device may resume PDCCH monitoring (or stop / terminate the PDCCH skipping) starting at the beginning of a first / initial / earliest slot that is after a last / fin al / end in g / latest symbol of the PUCCH transmission in all serving cells of the corresponding Cell Group.

[0421] After the wireless device detects / receives the fourth DCI and in response to cancelling a pending SR, the wireless device may resume PDCCH monitoring in all serving cells of the corresponding Cell Group.

[0422] The one or more configuration parameters may indicate pdcchMomitoringResumptionAfterNack for terminating PDCCH skipping after transmission of a NACK via PUCCH / PUSCH. When the pdcchMomitoringResumptionAfterNack is configured / indicates and after receiving the fourth DCI, if the wireless device transmits a PUCCH / PUSCH comprising / providing the first HARQ-ACK information of the at least one HARQ-ACK information, the wireless device terminates PDCCH skipping.

[0423] The first HARQ-ACK information may comprise / indicate the first NACK value (or the first NACK) associated with a PDSCH reception (see also FIG. 17A and / or FIG. 17B). The first NACK value may indicate the wireless device unsuccessfully / incorrectly decode / receive the PDSCH. The first NACK value may indicate the wireless device unsuccessfully / incorrectly decode / receive the TB provided in the PDSCH reception.

[0424] The PDSCH may be scheduled / indicated by a fifth DCI (not shown in FIG. 22C) in a PDCCH reception (of the at least one PDCCH monitoring occasion) on the serving cell. For example, the fourth DCI may be different than the fifth DCI. The wireless device may receive the fifth DCI prior to receiving the fourth DCI.

[0425] The wireless device may receive the fourth DCI in a same slot that the wireless device receives the fourth DCI.

[0426] The PDSCH may be scheduled by the fourth DCI. For example, the fourth DCI may be the fifth DCI. For example, the PDSCH is scheduled by the fourth DCI indicating the second indication.

[0427] The first HARQ-ACK information may comprise the first NACK value. The first HARQ-ACK information may correspond to the PDSCH reception indicated by the fifth DCI. For example, based on unsuccessfully / incorrectlyreceiving / decoding the PDSCH reception (or a transport block provided by the PDSCH), the wireless device may set the first HARQ-ACK information to a NACK (e.g., the first NACK value).

[0428] Although in FIG. 22C the PDSCH occasion (or reception slot / symbol) is after the fourth DCI reception occasion, in some examples, the PDSCH occasion (or reception slot / symbol) may be before or prior to the fourth DCI reception occasion.

[0429] For example, the fifth DCI may indicate a HARQ process number corresponding to / associated with the PDSCH reception. The first NACK value may correspond to / associated with the HARQ process number indicated by the fifth DCI. The first NACK value may be based on decoding result of the PDSCH. When the PDSCH is unsuccessfully / incorrectly decoded / received, the wireless device may generate the first NACK value in the at least one HARQ-ACK information for transmission to the base station.

[0430] The wireless device (as also discussed above in connection with FIG. 17A or FIG. 17B), determine the at least one multiplexing condition being satisfied. The wireless device may multiplex the first NACK in the PUSCH transmission.

[0431] In response to transmitting the PUCCH / PUSCH comprising the first NACK value while the skipping duration is running, the wireless device may terminate PDCCH skipping starting from a beginning of a first / starting / initial / earliest slot that is after a last symbol of the PUCCH or PUSCH transmission on the serving cell. In response to transmitting the PUCCH / PUSCH comprising the first NACK value while the skipping duration is running, the wireless device may resume / start PDCCH monitoring starting from the beginning of the first / starting / in itial / earliest slot that is after the last symbol of the PUCCH or PUSCH transmission on the serving cell.

[0432] In response to transmitting the PUCCH / PUSCH not comprising the first NACK value while the skipping duration is running, the wireless device may not resume / start PDCCH monitoring. In response to transmitting the PUCCH / PUSCH comprising an ACK value while the skipping duration is running, the wireless device may not resume / start PDCCH monitoring. In response to transmitting the PUCCH / PUSCH not comprising the first HARQ-ACK information while the skipping duration is running, the wireless device may not resume / start PDCCH monitoring.

[0433] The first HARQ-ACK information may comprise the second ACK value.

[0434] The second ACK value may be the first ACK value.

[0435] Alternatively, the second ACK value may be different than the first ACK value.

[0436] For example, based on successfu lly / correctly receiving / decoding the PDSCH reception (or a transport block provided by the PDSCH), the wireless device may set the first HARQ-ACK information to the ACK.

[0437] If a DRX group of the serving cell is configured (e.g., when the one or more configuration parameters comprise DRX-Config) and the wireless device enters outside Active Time of a DRX operation / group, the wireless device may terminate PDCCH skipping for the serving cell.

[0438] For example, the PUSCH transmission may be dynamically scheduled by an UL grant in the sixth DCI.

[0439] The PUSCH transmission may correspond to a configured grant Type 1 or Type 2 configured by one or more CG configuration parameters. The one or more configuration parameters may comprise the one or more CG configuration parameters. For example, the one or more CG configuration parameters may configure / indicate the configured grant Type1 / Type2. The sixth DOI may activate the Tyep2 configured grant.

[0440] The sixth DOI may be different than the fourth DOI. For example, the sixth DOI may be received by the wireless device prior to receiving the fourth DOI.

[0441] In some examples, the sixth DOI is the fourth DOI. The sixth DOI scheduling the PUSCH transmission and indicating the second indication.

[0442] The configured grant Type 1 PUSCH transmission may be semi-statically configured by the one or more RRC messages. Upon the reception the one or more RRC messages comprising configuredGrantConfig including rrc- ConfiguredUplinkGrant without the detection of an UL grant in a DCI, the wireless device may start using the configured grant Type 1 PUSCH transmission. The configured grant Type 2 PUSCH transmission is semi-persistently scheduled by an UL grant configured by configuredGrantConfig and / or a valid activation DCI after the configuredGrantConfig not including rrc-ConfiguredUplinkGrant. If the one or more CG configuration parameters configured / indicate configuredGrantConfigToAddModList, more than one configured grant configuration of configured grant Type 1 and / or configured grant Type 2 may be active at the same time on an active BWP of a serving cell.

[0443] FIG. 23A shows an example of PDCCH monitoring. Embodiment of FIG. 23A may be based on a combination of embodiment of FIG. 20 and FIG. 22C discussed above. In some aspect, embodiment of FIG. 23A may provide one or more additional aspects (or enhancements) for the PDCCH skipping procedure and / or search space switch procedures.

[0444] As shown while the SS switch timer is running (not being expired) the wireless device may monitor the PDCCH (candidates) according to the second SSS group. For example, the wireless device may receive the fourth DCI indicating the second indication during the SS switch timer is running. As also discussed above in relation to FIG. 22C, based on receiving the fourth DCI, the wireless device may start the skipping duration. The wireless device may, based on the fourth DCI, start skipping the PDCCH monitoring while the SS switch timer is running. In response to the expiry of the SS switch timer and while the skipping duration is running, the wireless device may switch from the second SSS group to the first SSS group no later than the SS switch delay and / or no later than an expiry of the skipping duration.

[0445] In the example of FIG. 23A, as the SS switch delay after the expiry of the SS switch timer is prior to (or no later than) the expiry of the skipping duration, the wireless device may switch from the second SSS group to the first SSS group in response to the expiry of the skipping duration. In response to the expiry of the skipping duration, the wireless device may start monitoring the PDCCH according to the first SSS group. However, existing technologies (e.g., embodiment of FIG. 23A) may result in unnecessary delay in switching from the second SSS group to the first SSS group when the SS switch timer expires.

[0446] In existing technologies, as also discussed above in accordance with embodiments of FIG. 18A and / or FIG. 18B, the wireless device may multiplex the second NACK value in the PUSCH transmission. For example, the second NACK value may correspond to not detecting the at least one DCI (e.g., the fifth DCI) during / withing the at least one PDCCH monitoring occasion. For example, the wireless device may determine the at least one multiplexing condition being satisfied. The PUSCH transmission may be during the skipping duration. The at least one PDCCH monitoring occasion may be prior to the starting of the skipping duration (e.g., receiving the fourth DCI).

[0447] Based on receiving the PUSCH transmission comprising the second NACK value, the base station may not be able to distinguish between whether the wireless device unsuccessfully decoded the PDSCH or failed to detect the fifth DCI. The base station may transmit one or more DCIs in response to receiving the PUSCH transmission comprising the second NACK value. As the wireless device keeps skipping the PDCCH monitoring after the PUSCH transmission comprising the second NACK value the wireless device may fail to receive the one or more DCIs transmitted by the base station. Implementation of existing technologies may reduce efficiency of DL transmissions. Enhancements in PDCCH skipping may improve efficiency of DL transmissions and / or improve alignment between the wireless device and / or the base station.

[0448] FIG. 23B shows an example of PDCCH skipping per an aspect of an embodiment of the present disclosure. Embodiment of FIG. 23B provides one or more enhancements for the PDCCH skipping procedure with respect to embodiment of FIG. 22C. Using embodiment of FIG. 23B, possible misalignment between the base station and / or the wireless device may reduce. Using embodiment of FIG. 23B, efficiency of DL transmissions may improve. As also discussed above in relation to FIG. 22C, the wireless device may receive from the base station the one or more configuration parameters.

[0449] For example, the wireless device may receive the fourth DCI indicating the second indication. In response to receiving a second indication, the wireless device may skip monitoring PDCCH during the skipping duration on the active DL BWP of a cell (e.g., a serving cell, e.g., a SpCell).

[0450] The wireless device may receive the fourth DCI after (in time domain) a last symbol / slot of the at least one PDCCH monitoring occasion. For example, the wireless device may not receive the fourth DCI in the at least one PDCCH monitoring occasion. The wireless device may determine no DCI being detected / receive during / in / associated with the at least one PDCCH monitoring occasion. For example, the wireless device may fail to detect / receive the at least one DCI (e.g., the fifth DCI) during / in / associated with the at least one PDCCH monitoring occasion.

[0451] In other examples, the wireless device may receive the fourth DCI in the at least one PDCCH monitoring occasion. Besides the fourth DCI, the wireless device may determine no DCI being detected / receive during / in / associated with the at least one PDCCH monitoring occasion. For example, the wireless device may fail to detect / receive the at least one DCI (e.g., the fifth DCI) during / in / associated with the at least one PDCCH monitoring occasion. For example, the wireless device may only detect / receive the fourth DCI during the at least one PDCCH monitoring occasion. The fourth DCI may indicate / schedule the PUSCH transmission during the kipping duration.

[0452] In other examples, the wireless device may receive the sixth DOI in the at least one PDCCH monitoring occasion. Besides the sixth DOI, the wireless device may determine no DOI being detected / receive during / in / associated with the at least one PDCCH monitoring occasion. For example, the wireless device may fail to detect / receive the at least one DCI (e.g., the fifth DCI) during / in / associated with the at least one PDCCH monitoring occasion. For example, the wireless device may only detect / receive the sixth DCI during the at least one PDCCH monitoring occasion. The sixth DCI may indicate / schedule the PUSCH transmission during the kipping duration.

[0453] The wireless device may determine the at least one multiplexing condition being satisfied. For example, the wireless device may multiplex the at least one HARQ-ACK information in the PUSCH transmission. The at least one HARQ-ACK information may comprise the second HARQ-ACK information. The second HARQ-ACK information may comprise the second NACK value.

[0454] For multiplexing the second NACK value in the PUSCH, the wireless device may determine the at least one multiplexing condition being satisfied (as discussed above in embodiments of FIG. 18A and / or FIG. 18B). As also shown in FIG. 23B, the second NACK value may correspond to / associated with the at least one PDCCH monitoring occasion. The wireless device may not detect / receive the at least one DCI (e.g., the fifth DCI) during / within / in the at least one PDCCH monitoring occasion. The wireless device may not detect / receive the at least one DCI (e.g., the fifth DCI) during / within / in the at least one PDCCH monitoring occasion scheduling at least one PDSCH / TB reception.

[0455] The wireless device may multiplex the at least one HARQ-ACK information comprising the second NACK value in the PUSCH. The wireless device may transmit the PUSCH comprising the at least one HARQ-ACK information comprising the second NACK value.

[0456] In an example embodiment, in response to transmitting the PUSCH transmission comprising the second NACK value, the wireless device may resume the PDCCH monitoring.

[0457] In an example embodiment, in response to transmitting the PUSCH transmission comprising the second NACK value, the wireless device may resume / start PDCCH monitoring starting from the beginning of the first / starting / in itial / earliest slot that is after the last symbol of the PUSCH transmission comprising the second NACK value.

[0458] When the pdcchMomitoringResumptionAfterNack is configured / indicates and after receiving the fourth DCI, in response to transmitting the PUSCH transmission comprising / providing the second HARQ-ACK information (e.g., the second NACK value) of the at least one HARQ-ACK information, the wireless device may resume the PDCCH monitoring.

[0459] In an example embodiment, in response to transmitting the PUSCH transmission comprising the second NACK value, the wireless device may terminate the skipping of the PDCCH monitoring.

[0460] In an example embodiment, in response to transmitting the PUSCH transmission comprising the second NACK value, the wireless device may terminate the skipping of the PDCCH monitoring starting from the beginning ofthe first / startin g / ini tial / earliest slot that is after the last symbol of the PUSCH transmission comprising the second NACK value.

[0461] When the pdcchMomitoringResumptionAfterNack is configured / indicates and after receiving the fourth DOI, based on transmitting the PUSCH transmission comprising / providing the second HARQ-ACK information (e.g., the second NACK value) of the at least one HARQ-ACK information, the wireless device may terminate the PDCCH skipping.

[0462] The base station may transmit one or more PDCCHs / DCIs to the wireless device. Based on / after resuming PDCCH monitoring, the wireless device may receive PDCCHs / DCIs from the base station. Some embodiments of the present disclosure may improve the DL efficiency of the wireless device.

[0463] In response to transmitting the PUCCH / PUSCH comprising the second NACK value while the skipping duration is running, the wireless device may terminate PDCCH skipping starting from a beginning of a first / starting / initial / earliest slot that is after a last symbol of the PUCCH or PUSCH transmission on the serving cell.

[0464] In response to transmitting the PUCCH / PUSCH comprising the second NACK value while the skipping duration is running, the wireless device may resume / start PDCCH monitoring starting from the beginning of the first / starting / in itial / earliest slot that is after the last symbol of the PUCCH or PUSCH transmission on the serving cell.

[0465] In response to transmitting the PUCCH / PUSCH not comprising the second NACK value while the skipping duration is running, the wireless device may not resume / start PDCCH monitoring.

[0466] In existing technologies, the wireless device may after the transmission of the positive SR and / or the first / second NACK value during the skipping duration and during the SS switch timer is running, may switch to the first / default SSS group for monitoring the PDCCH. For example, the wireless device may reset the PDCCH monitoring according to the SSS group with the group index 0. Existing technologies may result in inefficient PDCCH monitoring after the transmission of the positive SR and / or the first / second NACK value during the skipping duration and during the SS switch timer is running. Existing technologies may result in misalignment between the wireless device and the base station after the transmission of the positive SR and / or the first / second NACK value during the skipping duration and during the SS switch timer is running.

[0467] FIG. 23C shows an example of PDCCH monitoring. Embodiment of FIG. 23C may provide one or more enhancements for the for the PDCCH skipping procedure and / or search space switch procedures described in FIG. 23A and / or FIG. 23B. Using the embodiment of FIG. 23C, the wireless device may be able to properly (by reducing misalignment between the base station and the wireless device) switch from the second SSS group to the first SSS group in response to the expiry of the SS switch timer. For example, the wireless device may after the transmission of the SR and / or the first / second NACK value resume monitoring the PDCCH according to the second SSS group.

[0468] As shown while the SS switch timer is running (not being expired) the wireless device may monitor the PDCCH (candidates) according to the second SSS group. For example, the wireless device may receive the fourth DCI indicating the second indication during the SS switch timer is running. As also discussed above in relation to FIG. 22C,based on receiving the fourth DOI, the wireless device may start the skipping duration. The wireless device may, based on the fourth DOI, start skipping the PDCCH monitoring while the SS switch timer is running. As shown in FIG. 23B and similar to FIG. 220, while the skipping duration is running, the wireless device may transmit the second positive SR (on PUCCH) or the at least one HARQ-ACK information.

[0469] The at least one HARQ-ACK information may comprise the first NACK value.

[0470] Alternatively, the at least one HARQ-ACK information may comprise the second NACK value.

[0471] In some scenarios, the wireless device may transmit the PUCCH comprising the at least one HARQ-ACK information.

[0472] For example, the wireless device may determine the at least one multiplexing condition being satisfied.

[0473] For multiplexing the first NACK value in the PUSCH, the wireless device may determine the at least one multiplexing condition being satisfied (as discussed above in embodiments of FIG. 17A and / or FIG. 17B). The at least one HARQ-ACK information may comprise the first NACK value. The first NACK value may correspond to / associated with the PDSCH reception scheduled by the fifth DCI.

[0474] For multiplexing the second NACK value in the PUSCH, the wireless device may determine the at least one multiplexing condition being satisfied (as discussed above in embodiments of FIG. 18A and / or FIG. 18B). The at least one HARQ-ACK information may comprise the second NACK value. As also shown in FIG. 23B, the second NACK value may correspond to / associated with the at least one PDCCH monitoring occasion. The wireless device may not detect / receive the at least one DCI (e.g., the fifth DCI) during / within / in the at least one PDCCH monitoring occasion.

[0475] The wireless device may multiplex the at least one HARQ-ACK information in the PUSCH. The wireless device may transmit the PUSCH comprising the at least one HARQ-ACK information.

[0476] The wireless device may terminate the PDCCH skipping in response to the transmission of the second positive SR or the at least one HARQ-ACK information comprising the first NACK value or the second NACK value.

[0477] In one example the fifth DCI may be the fourth DCI.

[0478] In another example, the fifth DCI may be different than the fourth DCI.

[0479] In yet another example, the fourth DCI may be different than the sixth DCI.

[0480] In yet another example, the fourth DCI may be the sixth DCI.

[0481] In an example embodiment, in response to the expiry of the SS switch timer and while the skipping duration is running (not being expired), the wireless device may switch from the second SSS group to the first SSS group after transmitting the second positive SR (on PUCCH) or the first NACK value (on PUCCH or PUSCH).

[0482] In an example embodiment, in response to the expiry of the SS switch timer after receiving the fourth DCI indicating the second indication, the wireless device may switch from the second SSS group to the first SSS group after transmitting the second positive SR (on PUCCH) or the first NACK value (on PUCCH or PUSCH).

[0483] As shown in FIG. 230, in response to transmitting the second positive SR (on PUCOH) or the first / second NACK value (on PUCOH or PUSCH) after the receiving the fourth DOI and the expiry of the SS switch timer, the wireless device may switch from the second SSS group to the first SSS group.

[0484] As shown in FIG. 230, in response to transmitting the second positive SR (on PUCCH) or the first / second NACK value (on PUCCH or PUSCH) after the receiving the fourth DOI and the expiry of the SS switch timer, the wireless device may start monitoring PDCCH according to the first SSS group.

[0485] Some embodiments of the present disclosure may allow the wireless device to properly determine whether to switch from the second SSS group to the first SSS group in response to transmitting the SR and / or the first / second NACK value.

[0486] FIG. 24A shows a flowchart of a procedure for PDCCH skipping procedure. Embodiment of FIG. 24A may further provide one or more additional enhancements for the PDCCH skipping discussed in FIG. 22C and / or FIG. 23C above. Using the embodiment of FIG. 24A, the wireless device may be able to properly stop / expire the skipping duration, e.g. , in order to avoid unnecessarily postponing the search space switching procedure. Embodiment of FIG. 24A may provide an alternative for embodiment of FIG. 23C.

[0487] As shown in FIG. 24A, the wireless device may receive the fourth DCI indication the second indication. The wireless device may start skipping of the PDCCH monitoring for the skipping duration indicated by the second indication.

[0488] Based on transmitting a PUCCH providing the second positive SR after the wireless device detects / receives the fourth DCI indicating the second indication, the wireless device may stop / expire the skipping duration.

[0489] In an example embodiment, the wireless device may, after cancelling the pending SR after receiving the fourth DCI, stop / expire the skipping duration.

[0490] In response to transmitting the PUCCH / PUSCH comprising / providing the first NACK value associated with a PDSCH reception that is scheduled by the fifth DCI, the wireless device stop / expire the skipping duration. The wireless device may receive the fifth DCI in a PDCCH reception on the serving cell.

[0491] In response to transmitting the PUCCH / PUSCH not comprising the first NACK value (associated with the PDSCH reception that is schedule by the fifth DCI) while the skipping duration is running, the wireless device may not stop / expire the skipping duration.

[0492] In response to transmitting the PUCCH / PUSCH not comprising the first HARQ-ACK information (associated with the PDSCH reception that is schedule by the fifth DCI) while the skipping duration is running, the wireless device may not stop / expire the skipping duration. The wireless device may receive the fifth DCI in a PDCCH reception on the serving cell.

[0493] In response to transmitting the PUCCH / PUSCH not comprising the first NACK value (associated with the PDSCH reception that is schedule by the fifth DCI) while the skipping duration is running, the wireless device may keep the skipping duration running. The wireless device may receive the fifth DCI in a PDCCH reception on the serving cell.

[0494] In response to transmitting the PUCCH / PUSCH not comprising the first HARQ-ACK information (associated with the PDSCH reception that is schedule by the fifth DOI) while the skipping duration is running, the wireless device may keep the skipping duration running. The wireless device may receive the fifth DOI in a PDCCH reception on the serving cell.

[0495] In response to transmitting PUSCH comprising / providing the second NACK value (associated with the at least one PDCCH monitoring occasion without detecting the at least one DCI scheduling a PDSCH / TB reception) while the skipping duration is running, the wireless device stop / expire the skipping duration. The wireless device may fail to receive the at least one DCI (e.g., the fifth DCI) in a PDCCH reception of the at least one PDCCH monitoring occasion on the serving cell.

[0496] In response to transmitting the PUSCH not comprising the second NACK value (associated with the at least one PDCCH monitoring occasion without detecting the at least one DCI scheduling a PDSCH / TB reception) while the skipping duration is running, the wireless device may not stop / expire the skipping duration. The wireless device may fail to receive the at least one DCI (e.g., the fifth DCI) in a PDCCH reception of the at least one PDCCH monitoring occasion on the serving cell.

[0497] In response to transmitting the PUSCH not comprising the second HARQ-ACK information (associated with the at least one PDCCH monitoring occasion without detecting the at least one DCI scheduling a PDSCH / TB reception) while the skipping duration is running, the wireless device may not stop / expire the skipping duration. The wireless device may fail to receive the at least one DCI (e.g., the fifth DCI) in a PDCCH reception of the at least one PDCCH monitoring occasion on the serving cell.

[0498] In response to transmitting the PUSCH not comprising the second NACK value (associated with the at least one PDCCH monitoring occasion without detecting the at least one DCI scheduling a PDSCH / TB reception) while the skipping duration is running, the wireless device may keep the skipping duration running. The wireless device may fail to receive the at least one DCI (e.g., the fifth DCI) in a PDCCH reception of the at least one PDCCH monitoring occasion on the serving cell.

[0499] For example, the one or more configuration parameters may configure / indicate the pdcchMomitoringResumptionAfterNack is configured / indicates.

[0500] Embodiments of FIG. 24A may allow the wireless device to properly (e.g., reducing misalignment between the wireless device and the base station) to expire / stop the skipping duration.

[0501] In the present disclosure, <KCT> may refer to 88888.

[0502] FIG. 24B shows an example of PDCCH skipping per an aspect of an embodiment of the present disclosure. Embodiment of FIG. 24B may provide one or more additional aspects with respect to embodiment of FIG. 22C described above. For example, embodiment of FIG. 24B may provide more details regarding the termination of the PDCCH skipping after the transmission of the PUSCH comprising the at least one HARQ-ACK information. The at leastone HARQ-ACK information may comprise at least one of the first NACK value and / or the second NACK value. The wireless device may, for example, determine the at least one multiplexing condition being satisfied.

[0503] As shown in FIG. 24B, the first NACK value may correspond to a PDSCH. Although not shown in FIG. 24B, the wireless device may receive the fifth DCI (from the base station) indicating / scheduling the PDSCH. In the example of FIG. 24B, the wireless device may unsuccessfully decode / receive the PDSCH. For example, the wireless device may determine the first HARQ-ACK information of the at least one HARQ-ACK information. The first HARQ-ACK information may correspond to the PDSCH having the first NACK value. The wireless device may multiplex (or include or insert) the first HARQ-ACK information with the first NACK value in the PUSCH transmission (see FIG. 24D for an example of multiplexing).

[0504] The second NACK value may correspond to the at least one PDCCH monitoring occasion. The wireless device may not receive (or fail to detect) the at least one DCI (e.g., the fifth DCI) scheduling the PDSCH / TB reception du ring / in the at least one PDCCH monitoring occasion.

[0505] As shown in FIG. 24B, the PUSCH transmission may be over / in a plurality of slots (multiple slots) and / or with a plurality of repetitions. The plurality of repetitions of the PUSCH transmission may be performed during / over / in the plurality of slots. As FIG. 24B shows, the plurality of repetitions of the PUSCH transmission is for transmitting a same data / packet / TB.

[0506] FIG. 24D, shows an example of a PUSCH transmission over the plurality of slots / repetitions. For example, the wireless device may transmit the PUSCH transmission based on the one or more configuration parameters (e.g., configured grant configuration or PUSCH configuration). In some examples, the PUSCH transmission may be based on a configured uplink grant (e.g., configured by a Type 1 configured grant configuration or a Type 2 configured grant configuration).

[0507] The configured uplink grant may indicate at least one of the following: time resource; frequency resource; repetition number; redundancy version; modulation and condition scheme; power configuration; and / or antenna port. In some other examples, the PUSCH transmission may be in response to receiving a DCI (e.g., the fourth DCI or the sixth DCI) scheduling / triggering / activating / indicating the PUSCH transmission. The DCI may comprise / indicate a dynamic uplink grant for the PUSCH transmission. The dynamic grant may comprise at least one of the following: time resource; frequency resource; antenna port; HARQ process number; redundancy version; antenna port; and / or the like. All repetitions of the PUSCH transmission may correspond to a single HARQ process and / or a single TB / packet.

[0508] The PUSCH transmission may comprise a plurality of repetitions (e.g., 6 repetitions) over the plurality of slots. The PUSCH may be with a repetition type A. The PUSCH may be with repetition type B. The one or more configuration parameters (or the DCI scheduling the PUSCH transmission) may configure / indicate whether the PUSCH is with the repetition Type A or the repetition Type B.

[0509] Although FIG. 24D shows an example of PUSCH transmission in an unpaired spectrum / band (e.g., TDD band / mode / duplex), similar configur...

Claims

CLAIMSWhat is claimed is:

1. A method comprising: receiving, by a wireless device, one or more configuration parameters indicating that control channel monitoring is resumed after control channel monitoring skipping is started when the wireless device transmits a negative acknowledgment (NACK); receiving a downlink control information (DOI) indicating to skip control channel monitoring; starting, after receiving the DOI, skipping the control channel monitoring; transmitting a first plurality of repetitions of a physical uplink shared channel (PUSCH) transmission, wherein a second plurality of repetitions, of the first plurality of repetitions indicates a negative acknowledgement (NACK); and resuming monitoring, starting from a slot after a last symbol of an earliest repetition among the second plurality of repetitions, the control channel.

2. A method comprising: transmitting, by a wireless device, a first plurality of transmissions, wherein a second plurality of transmissions, of the first plurality of transmissions, indicates a negative acknowledgement (NACK); and monitoring, starting from a slot after a last symbol of an earliest transmission among the second plurality of transmissions, a control channel.

3. The method of claim 2, further comprising: receiving, by the wireless device, a downlink control information (DCI) indicating to skip control channel monitoring; and starting, after receiving the DCI, skipping the monitoring of the control channel.

4. The method of any one of claims 2 to 3, wherein the first plurality of transmissions comprise a first plurality of repetitions of a physical uplink shared channel (PUSCH) transmission.

5. The method of claim 4, wherein the first plurality of repetitions use: a PUSCH repetition Type A; or a PUSCH repetition Type B.

6. The method of any one of claims 2 to 5, wherein: the second plurality of transmissions comprise a second plurality of repetitions of a PUSCH transmission; and the earliest transmission is an earliest repetition among the second plurality of repetitions of the PUSCH transmission.

7. The method of any one of claims 2 to 6, wherein the first plurality of transmissions comprise PUSCH transmissions.

8. The method of any one of claims 2 to 7, wherein: the second plurality of transmissions comprise PUSCH transmissions; andthe earliest transmission is an earliest PUSCH transmission among the second plurality of PUSCH transmissions.

9. The method of any one of claims 2 to 8, wherein the NACK corresponds to a physical downlink shared channel (PDSCH) reception.

10. The method of any one of claims 3 to 9, wherein the DOI schedules a PDSCH reception.

11. The method of any one of claims 3 to 10, further comprising receiving a second DCI.

12. The method of claim 11, wherein the second DCI schedules a PDSCH reception.

13. The method of any one of claims 11 to 12, wherein the second DCI schedules the first plurality of transmissions.

14. The method of any one of claims 3 to 11 , wherein: the skipping of the control channel monitoring is for a first duration; and the first duration is indicated by the DCI.

15. The method of claim 14, further comprising: starting, based on the DCI, the first duration indicated by the DCI; and stopping or expiring the duration in response to resuming the control channel monitoring.

16. The method of any one of claims 4 to 15, wherein the DCI schedules the PUSCH transmission.

17. The method of any one of claims 3 to 16, wherein the DCI schedules the plurality of transmissions.

18. The method of any one of claims 3 to 17, wherein the DCI indicates a downlink assignment indication (DAI).

19. The method of claim 18, wherein: the DAI is not 4; and the NACK is generated based on a Type 2 hybrid automatic repeat request (HARQ)-ACK codebook.

20. The method of claim 18, wherein: the DAI is not 1; and the NACK is generated based on a Type 1 HARQ-ACK codebook.

21. The method of any one of claims 2 to 20, wherein the slot after the last symbol of the earliest transmission is a next sequential slot after the last symbol of the earliest transmission.

22. The method of any one of claims 2 to 21 , wherein monitoring the control channel comprises: resuming monitoring the control channel; or terminating skipping of the control channel monitoring.

23. The method of any one of claims 2 to 22, wherein: the NACK corresponds to at least one physical downlink control channel (PDCCH) monitoring occasion; and the wireless device does not detect a second DCI in the at least one PDCCH monitoring occasion.

24. The method of any one of claims 4 to 23, wherein the PUSCH transmission corresponds to: a Type 1 configured grant; or a Type 2 configured grant.

25. The method of any one of claims 4 to 24, further comprising receiving a third DOI scheduling the PUSCH transmission.

26. The method of claim 25, wherein the third DOI indicates a second DAI.

27. The method of claim 26, wherein: the second DAI is not 4; and the NACK is generated based on a Type 2 hybrid automatic repeat request (HARQ)-ACK codebook.

28. The method of claim 26, wherein: the second DAI is not 1; and the NACK is generated based on a Type 1 hybrid automatic repeat request (HARQ)-ACK codebook.

29. The method of any one of claims 2 to 28, wherein the second plurality of transmissions overlap with a physical uplink control channel (PUCCH) resource with the NACK.

30. The method of claim 29, further comprising multiplexing the NACK in the second plurality transmissions.

31. The method of any one of claims 4 to 30, wherein the PUSCH transmission is on a serving cell.

32. The method of claim 31 , wherein skipping control channel monitoring is on an active downlink bandwidth part of the serving cell.

33. The method of any one of claims 31 to 32, wherein resuming the control channel monitoring is on the serving cell.

34. The method of any one of claims 2 to 33, wherein control channel monitoring comprises PDCCH monitoring.

35. The method of any one of claims 2 to 34, further comprising receiving one or more configuration parameters.

36. The method of claim 35, wherein the one or more configuration parameters indicate that control channel monitoring is resumed after control channel monitoring skipping is started when the wireless device transmits a NACK.

37. The method of claim 35, wherein resuming the control channel monitoring is further based on the one or more configuration parameters.

38. The method of any one of claims 35 to 37, wherein the one or more configuration parameters indicate a first parameter indicating that control channel monitoring is resumed after control channel monitoring skipping is started when the wireless device transmits the NACK due to incorrectly decoding a PDSCH.

39. The method of any one of claims 35 to 38, wherein the one or more configuration parameters indicate a second parameter indicating that control channel monitoring is resumed after control channel monitoring skipping is started when the wireless device transmits a NACK due to not detecting a DCI format in a PDCCH monitoring occasion.

40. The method of any one of claims 35 to 39, wherein the one or more configuration parameters indicate a third parameter indicating that control channel monitoring is resumed after an earliest repetition of a PUSCH transmission with a NACK.

41. The method of claim 40, wherein the resuming the control channel monitoring after the earliest repetition among the second plurality of repetitions is further based on the one or more configuration parameters indicate the third parameter.

42. A method comprising: receiving, by a wireless device, a downlink control information (DOI) indicating a transmission communication indication (TCI) state; transmitting a first plurality of transmissions, wherein a second plurality of transmissions, of the first plurality of transmissions, indicates a positive acknowledgement (ACK) corresponding to the DCI; and applying, after a first gap from a slot after a last symbol of an earliest transmission of the second plurality of transmissions, the TCI state.

43. The method of claim 42, wherein: the first plurality of transmissions comprise a first plurality of repetitions of a physical uplink shared channel (PUSCH) transmission; the second plurality of transmissions comprise a second plurality of repetitions of the PUSCH transmission; and the earliest transmission is an earliest repetition of the second plurality of repetitions of the PUSCH transmission.

44. The method of claim 42, wherein: the first plurality of transmissions comprise a first plurality of physical uplink shared channel (PUSCH) transmissions; the second plurality of transmissions comprise a second plurality of PUSCH transmissions; and the earliest transmission is an earliest PUSCH transmission of the second plurality of PUSCH transmissions.

45. The method of any one of claims 42 to 44, further comprising receiving, after applying the TCI state and based on the TCI state, at least one of: physical downlink control channel (PDCCH) receptions; physical downlink shared channel (PDSCH) receptions; or channel state information (CSI) reference signal (RS) resources.

46. The method of claim 45, wherein: a demodulation reference signal (DM-RS) port of the PDCCH receptions corresponds to a RS associated with the TCI state; one or more DM-RS ports of the PDSCH corresponds to at least one RS associated with the TCI state; or one or more CSI RS ports of the CSI RS resources corresponds to at least one RS associated with the TCI state.

47. The method of any one of claims 42 to 46, further comprising transmitting, after applying the TCI state and based on the TCI state, at least one of:PUSCH transmissions; physical uplink control channel (PUCCH) transmissions; or sounding reference signal (SRS).

48. The method of claim 47, wherein: the TCI state indicates an uplink transmission (TX) spatial filter for transmitting the PUSCH transmissions; the TCI state indicates an uplink TX spatial filter for transmitting the PUCCH transmissions; or the TCI state indicates an uplink TX spatial filter for transmitting the SRS.

49. 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 48.

50. 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 48.

Images