Low band carrier aggregation with downlink switching

Abstract

A wireless device transmits, to a base station, a capability message indicating a switching time between communication via one or more frequency division duple (FDD) carriers and a supplementary downlink (SDL) carrier. The wireless device receives, from the base station, a plurality of configuration parameters. First configuration parameters indicating a primary cell configured with a first downlink carrier and a first uplink carrier. Second configuration parameters indicating a secondary cell configured with a second downlink carrier. Third configuration parameters indicating a low band carrier aggregation (LBCA) switch operation between the primary cell and the secondary cell. The third configuration parameters further indicate a duration of switching gap for the switch operation from the secondary cell to the primary cell. The duration is larger than or equal to a sum of a switching time and a timing advance (TA).

Description

Docket No.: 25-1052PCTTITLELow Band Carrier Aggregation with Downlink SwitchingCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 779,264, filed March 27, 2025, which is hereby incorporated by reference in its entirety.BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0023] FIG. 17A, FIG. 17B, FIG. 17C, FIG. 17D illustrates examples of uplink / downlink receptions / transmissions according to the present disclosure.

[0024] FIG. 18 illustrates an example of PDSCH processing time for the PDSCH processing capability 1 according to the present disclosure.

[0025] FIG. 19A illustrates an example of PDSCH processing time for the PDSCH processing capability 2 according to the present disclosure.

[0026] FIG. 19B illustrates an example of PUSCH processing time for the PUSCH processing capability 2 according to the present disclosure.

[0027] FIG. 20 illustrates an example of PUSCH processing time for the PUSCH processing capability 1 according to the present disclosure.

[0028] FIG. 21 illustrates an example of low-band carrier aggregation (LB CA) via switching according to the present disclosure.

[0029] FIG. 22 illustrates an example of low-band carrier aggregation (LB CA) via switching according to the present disclosure.

[0030] FIG. 23A, FIG. 23B, FIG. 23C illustrate examples of low-band carrier aggregation (LB CA) via switching according to the present disclosure.

[0031] FIG. 24A and FIG. 24B illustrate examples of UL / DL transmissions / receptions in low-band carrier aggregation (LB CA) via switching according to the present disclosure.

[0032] FIG. 24C illustrates an examples of UL / DL transmissions / receptions in low-band carrier aggregation (LB CA) via switching according to the present disclosure.

[0033] FIG. 25A and FIG. 25B illustrate examples of UL / DL transmissions / receptions in low-band carrier aggregation (LB CA) via switching according to the present disclosure.

[0034] FIG. 26A and FIG. 26B illustrates examples of UL / DL transmissions / receptions in low-band carrier aggregation (LB CA) via switching according to the present disclosure.

[0035] FIG. 27A and FIG. 27B illustrate examples of a carrier aggregation via downlink switching according to the present disclosure.

[0036] FIG. 28A and FIG. 28B illustrate examples of a carrier aggregation via downlink switching according to the present disclosure.

[0037] FIG. 29 illustrates an example of a carrier aggregation via downlink switching according to the present disclosure.Docket No.: 25-1052PCT

[0038] FIG. 30 illustrates an example of a carrier aggregation via downlink switching according to the present disclosure.

[0039] FIG. 31 illustrates an example of a carrier aggregation via downlink switching according to the present disclosure.DETAILED DESCRIPTION

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

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

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

[0043] 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 thisDocket No.: 25-1052PCTdisclosure, 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.

[0044] 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-emptysetsand subsets are considered. For example, possible subsetsof B = {celH, cell2} are: {celH}, {cell2}, and {cell 1 , cell2}. The phrase “based on” (or equally “based at least on”) is indicative that the phrase following the term “based on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “in response to” (or equally “in response at least to”) is indicative that the phrase following the phrase “in response to” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “depending on” (or equally “depending at least to”) is indicative that the phrase following the phrase “depending on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “employing / using” (or equally “employing / using at least') is indicative that the phrase following the phrase “employing / using” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments.

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

[0046] 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 pluralityDocket No.: 25-1052PCTof 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.

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

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

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

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

[0051] 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 airDocket No.: 25-1052PCTinterface 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.

[0052] The term wireless device may be used throughout this disclosure to refer to and encompass any mobile device or fixed (non-mobile) device for which wireless communication is needed or usable. For example, a wireless device maybe a telephone, smartphone, tablet, computer, laptop, sensor, meter, wearable device, Internet of Things (loT) device, vehicle roadside unit (RSU), relay node, automobile, and / or any combination thereof. The term 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.

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

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

[0055] 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.Docket No.: 25-1052PCT

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

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

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

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

[0060] 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 / U PF 158 in FIG. 1B for ease ofDocket No.: 25-1052PCTillustration. The UPF 158B may serve as a gateway between the NG-RAN 154 and the one or more DNs The UPF 158B may perform functions such as packet routing and forwarding, packet inspection and user plane policy rule enforcement, traffic usage reporting, uplink classification to support routing of traffic flows to the one or more DNs, quality of service (QoS) handling for the user plane (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink traffic verification), downlink packet buffering, and downlink data notification triggering. The UPF 158B may serve as an anchor point for intra- / i nter-Radio Access Technology (RAT) mobility, an external protocol (or packet) data unit (PDU) session point of interconnect to the one or more DNs, and / or a branching point to support a multi-homed PDU session. The UEs 156 may be configured to receive services through a PDU session, which is a logical connection between a UEanda DN.

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

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

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

[0064] As shown in FIG. 1B, the gNBs 160 and / or the ng-eNBs 162 may be connected to the 5G-CN 152 by means of an NG interface and to other base stations by an Xn interface. The NG and Xn interfaces may be established using direct physical connections and / or indirect connections over an underlying transport network, such as an internet protocol (IP) transport network. The gNBs 160 and / or the ng-eNBs 162 may be connected to the UEs 156 by means of a Uu interface. For example, as illustrated in FIG. 1 B, g NB 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 theDocket No.: 25-1052PCTinterfaces 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.

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

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

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

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

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

[0070] 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 theDocket No.: 25-1052PCThigher layers of the protocol stack and may correspond to layer 1 of the Open Systems Interconnection (OSI) model. The next four protocols above PHYs 211 and 221 comprise media access control layers (MACs) 212 and 222, radio link control layers (RLCs) 213 and 223, packet data convergence protocol layers (PDCPs) 214 and 224, and service data application protocol layers (SDAPs) 215 and 225. Together, these four protocols may make up layer 2, or the data link layer, of the OSI model.

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

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

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

[0074] 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 notedDocket No.: 25-1052PCTfunctions 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.

[0075] The MACs 212 and 222 may perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. The multiplexing / demultiplexing may include multiplexing / demultiplexing of data units, belonging to the one or more logical channels, into / from Transport Blocks (TBs) delivered to / from the PHYs 211 and 221. The MAC 222 may be configured to perform scheduling, scheduling information reporting, and priority handling between UEs by means of dynamic scheduling. Scheduling may be performed in the 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 MACs 212 and 222 may support one or more numerologies and / or transmission timings. In an example, mapping restrictions in a logical channel prioritization may control which numerology and / or transmission timing a logical channel may use. As shown in FIG. 3, the MACs 212 and 222 may provide logical channels as a service to the RLCs 213 and 223.

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

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

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

[0079] 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. TheDocket No.: 25-1052PCTMAC 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.

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

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

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

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

[0084] - a paging control channel (PCCH) for carrying paging messages used to page a UE whose location is not known to the network on a cell level;Docket No.: 25-1052PCT

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0102] 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 referenceDocket No.: 25-1052PCTsignals (CSI-RS), demodulation reference signals (DMRS), sounding reference signals (S RS), and phase-tracking reference signals (PT-RS). These physical layer signals will be described in greater detail below.

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

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

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

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

[0107] 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 104Docket No.: 25-1052PCTdepicted in FIG. 1A, one of the gNBs 160 or ng-eNBs 162 depicted in FIG. 1B, the gNB 220 depicted in FIG. 2Aand FIG. 2B, or any other base station described in the present disclosure. The base station with which the UE is connected may have the RRC context for the UE. The RRC context, referred to as the UE context, may comprise parameters for communication between the UE and the base station. These parameters may include, for example: one or more AS contexts; one or more radio link configuration parameters; bearer configuration information (e.g., relating to a data radio bearer, signaling radio bearer, logical channel, QoS flow, and / or PDU session); security information; and / or PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information. While in RRC connected 602, mobility of the UE may be managed by the RAN (e.g., the RAN 104 or the NG-RAN 154). The UE may measure the signal levels (e.g., reference signal levels) from a serving cell and neighboring cells and report these measurements to the base station currently serving the UE. The UE’s serving base station may request a handover to a cell of one of the neighboring base 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.

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

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

[0110] 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 identifierDocket No.: 25-1052PCT(RAI); and cells within a group of RAN areas, referred to as a tracking area and identified by a tracking area identifier (TAI).

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

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

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

[0114] AgNB, such asgNBs 160 in FIG. 1B, maybe split into two parts: a central unit (gNB-CU), and one or more distributed units (gNB-DU). A gNB-CU maybe 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.

[0115] 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 peakDocket No.: 25-1052PCTto 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.

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

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

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

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

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

[0121] NR may support wide carrier bandwidths (e.g., up to 400 MHz for a subcarrier spacing of 120 kHz). Notall 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 / orDocket No.: 25-1052PCTfor 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.

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

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

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

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

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

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

[0128] 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) whenDocket No.: 25-1052PCTthe UE detects a DCI indicating an active downlink BWP other than a default downlink BWP for a paired spectra operation; or (b) when a UE detects a DCI indicating an active downlink BWP or active uplink BWP other than a default downlink BWP or uplink BWP for an unpaired spectra operation. If the UE does not detect DCI during an interval of time (e.g., 1 ms or 0.5 ms), the UE may run the BWP inactivity timer toward expiration (for example, increment from zero to the BWP inactivity timer value, or decrement from the BWP inactivity timer value to zero). When the BWP inactivity timer expires, the UE may switch from the active downlink BWP to the default downlink BWP.

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

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

[0131] 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 ata switching point. In the example illustrated in FIG. 9, the BWPs include: a BWP 902 with a bandwidth of 40 MHz and a subcarrier spacing of 15 kHz; a BWP 904 with a bandwidth of 10 MHz and a subcarrier spacing of 15 kHz; and a BWP 906 with a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz. The BWP 902 may be an initial active BWP, and the BWP 904 may be a default BWP. The UE may switch between BWPs at switching points. In the example of FIG. 9, the UE may switch from the BWP 902 to the BWP 904 at a switching point 908. The switching at the switching point 908 may occur for any suitable reason, for example, in response to an expiry of a BWP inactivity timer (indicating switching to the default BWP) and / or in response to receiving a DCI indicating BWP 904 as the active BWP. The UE may switch at a switching point 910 from active BWP 904 to BWP 906 in response to receiving a DCI indicating BWP 906 as the active BWP. The UE may switch at a switching point 912 from active BWP 906 to BWP 904 in response to an expiry of a BWP inactivity timer and / or in response to receiving a DCI indicating BWP 904 as the active BWP. The UE may switch at a switching point 914 from active BWP 904 to BWP 902 in response to receiving a DCI indicating BWP 902 as the active BWP.

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

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

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

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

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

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

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

[0139] 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 exampleDocket No.: 25-1052PCTof FIG. 10B, the PUCCH group 1010 includes three downlink CCs: a PCell 1011, an SCell 1012, and an SCell 1013. The PUCCH group 1050 includes three downlink CCs in the present example: a PCell 1051, an SCell 1052, and an SCell 1053. One or more uplink CCs may be configured as a PCell 1021, an SCell 1022, and an SCell 1023. One or more other uplink CCs may be configured as a primary SCell (PSCell) 1061, an SCell 1062, and an SCell 1063. Uplink control information (UCI) related to the downlink CCs of the PUCCH group 1010, shown as UC11031, UC11032, and UC11033, maybe transmitted in the uplink of the PCell 1021. Uplink control information (UCI) related to the downlink CCs of the PUCCH group 1050, shown as UC11071, UC11072, and UC11073, maybe transmitted in the uplink of the PSCell 1061. In an example, if the aggregated cells depicted in FIG. 10B were not divided into the PUCCH group 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.

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

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

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

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

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

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

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

[0147] 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 mayDocket No.: 25-1052PCTindicate an absence of SIB1 Based on the PBCH indicating the absence of SIB1, the UE maybe pointed to a frequency. The UE may search for an SS / PBCH block at the frequency to which the UE is pointed.

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

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

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

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

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

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

[0154] 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 withDocket No.: 25-1052PCTthe downlink CSI -RS are outside of the physical resource blocks (PRBs) configured for the CORESET The UE may be configured to employ the same OFDM symbols for downlink CSI-RS and SS / PBCH blocks when the downlink CSI-RS and SS / PBCH blocks are spatially QCLed and resource elements associated with the downlink CSI-RS are outside of PRBs configured for the SS / PBCH blocks.

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

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

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

[0158] 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 beDocket No.: 25-1052PCTconfined in the scheduled time / frequency duration for the UE. Downlink PT-RS may be transmitted on symbols to facilitate phase tracking at the receiver.

[0159] The UE may transmit an uplink DMRS to a base station for channel estimation. For example, the base station may use the uplink DMRS for coherent demodulation of one or more uplink physical channels. For example, the UE may transmit an uplink DMRS with a PUSCH and / or a PUCCH. The uplink DM-RS may span a range of frequencies that is similar to a range of frequencies associated with the corresponding physical channel. The base station may configure the UE with one or more uplink DMRS configurations. At least one DMRS configuration may support a front-loaded DMRS pattern. The front-loaded DMRS maybe mapped over one or more OFDM symbols (e.g., one or 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.

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

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

[0162] 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 SRSDocket No.: 25-1052PCTresource in an SRS resource set of the one or more SRS resource sets (e.g , with the same / similar time domain behavior, periodic, aperiodic, and / or the like) may be transmitted at a time instant (e.g., simultaneously). The UE may transmit one or more SRS resources in SRS resource sets. An NR network may support aperiodic, periodic and / or semi-persistent SRS transmissions. The UE may transmit SRS resources based on one or more trigger types, wherein the one or more trigger types may comprise higher layer signaling (e.g., RRC) and / or one or more DCI formats. In an example, at least one DCI format may be employed for the UE to select at least one of one or more configured SRS resource sets. An SRS trigger type 0 may refer to an SRS triggered based on a higher layer signaling. An SRS trigger type 1 may refer to an SRS triggered based on one or more DCI formats. In an example, when RUSCH and SRS are transmitted in a same slot, the UE may be configured to transmit SRS after a transmission of a RUSCH and a corresponding uplink DMRS

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

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

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

[0166] 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 parametersDocket No.: 25-1052PCTindicating one or more CSI-RSs. One or more of the following parameters may be configured by higher layer signaling (e.g., RRC and / or MAC signaling) for a CSI-RS resource configuration: a CSI-RS resource configuration identity, a number of CSI-RS ports, a CSI-RS configuration (e.g., symbol and resource element (RE) locations in a subframe), a CSI-RS subframe configuration (e.g., subframe location, offset, and periodicity in a radio frame), a CSI-RS power parameter, a CSI-RS sequence parameter, a code division multiplexing (CDM) type parameter, a frequency density, a transmission comb, quasi co-location (QCL) parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and / or other radio resource parameters.

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

[0168] CSI-RSs such as those illustrated in FIG. 11 B (e.g., CSI-RS 1101, 1102, 1103) maybe 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.

[0169] 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 beamDocket No.: 25-1052PCTpair 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).

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

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

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

[0173] 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 CSIDocket No.: 25-1052PCTvalue measured on RS resources. The base station may indicate that an RS resource is quasi co-located (QC Led) with one or more DM-RSs of a channel (e.g., a control channel, a shared data channel, and / or the like). The RS resource and the one or more DMRSs of the channel may be QCLed when the channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameter, fading, and / or the like) from a transmission via the RS resource to the UE are similar or the same as the channel characteristics from a transmission via the channel to the UE.

[0174] 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 RRCJ DLE state and / or an RRCJNACTIVE state may initiate the random access procedure to request a connection setup to a network. The UE may initiate the random access procedure from an RRC_CONNECTED state. The UE may initiate the random access procedure to request uplink resources (e.g., for uplink transmission of an SR when there is no PUCCH resource available) and / or acquire uplink timing (e.g., when uplink synchronization status is non-synchronized). The UE may initiate the random access procedure to request one or more system information blocks (SIBs) (e.g., other system information such as SIB2, SIB3, and / or the like). The UE may initiate the random access procedure for a beam failure recovery request. A network may initiate a random access procedure for a handover and / or for establishing time alignment for an SCell addition.

[0175] 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 21312, 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 21312 may include and / or be referred to as a random access response (RAR).

[0176] 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 (eg., RACH-configGeneral); cell-specific parameters (e.g., RACH-ConfigCommon); and / or dedicated parameters (e.g., RACH-configDedicated). The base station may broadcastor multicast the one or more RRC messages to one or more UEs. The one or more RRC messages may be UE-specific (e.g., dedicated RRC messages transmitted to a UE in an RRC_CONNECTED state and / or in an RRC_I NACTIVE state). The UE may determine, based on the one or more RACH parameters, a time-frequency resource and / or an uplink transmit power for transmission of the Msg 1 1311 and / or the Msg 31313. Based on the one or more RACH parameters, the UE may determine a reception timing and a downlink channel for receiving the Msg 21312 and the Msg 41314.

[0177] 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 betweenDocket No.: 25-1052PCT(a) one or more PRACH occasions and (b) one or more reference signals. The one or more RACH parameters may indicate an association between (a) one or more preambles and (b) one or more reference signals. The one or more reference signals may be SS / PBCH blocks and / or CSI-RSs. For example, the one or more RACH parameters may indicate a number of SS / PBCH blocks mapped to a PRACH occasion and / or a number of preambles mapped to a SS / PBCH blocks.

[0178] 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 31313. For example, the one or more RACH parameters may indicate a reference power for a preamble transmission (e.g., a received target power and / or an initial power of the preamble transmission). There may be one or more power offsets indicated by the one or more RACH parameters. For example, the one or more RACH parameters may indicate: a power ramping step; a power offset between SSB and CSI-RS; a power offset between transmissions of the Msg 1 1311 and the Msg 31313; and / or a power offset value between preamble groups. The one or more RACH parameters may indicate one or more thresholds based on which the UE may determine at least one reference signal (e.g., an SSB and / or CSI-RS) and / or an uplink carrier (e.g., a normal uplink (NUL) carrier and / or a supplemental uplink (SUL) carrier).

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

[0180] The UE may determine the preamble based on the one or more RACH parameters provided in the configuration message 1310. For example, the UE may determine the preamble based on a pathloss measurement, an RSRP measurement, and / or a size of the Msg 31313. As another example, the one or more RACH parameters may indicate: a preamble format; a maximum number of preamble transmissions; and / or one or more thresholds for determining one or more preamble groups (eg., 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-OccasionLisf) may indicate an association between the PRACH occasions and the one or more reference signals.Docket No.: 25-1052PCT

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

[0182] The Msg 21312 received by the UE may include an RAR. In some scenarios, the Msg 21312 may include multiple RARs corresponding to multiple UEs. The Msg 21312 may be received after or in response to the transmitting of the Msg 1 1311. The Msg 21312 may be scheduled on the DL-SCHand 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 21312 may include a time-alignment command that may be used by the UE to adjust the UE's transmission timing, a scheduling grant for transmission of the Msg 31313, and / or a Temporary Cell RNTI (TC-RNTI). After transmitting a preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor a PDCCH for the Msg 21312. The UE 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:

[0183] RA-RNTI = 1 + sjd + 14 x tjd + 14 x 80 x fjd + 14 x 80 x 8 x ul_carrier_id, where s_id maybe an index of a first OFDM symbol of the PRACH occasion (e.g., 0 s sjd < 14), tjd may be an index of a first slot of the PRACH occasion in a system frame (e.g., 0 < tjd < 80), fjd may be an index of the PRACH occasion in the frequency domain (e.g., 0 < fjd < 8), and ul_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).Docket No.: 25-1052PCT

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

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

[0186] 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 (eg., 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).

[0187] 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 2 1312 illustrated in FIG. 13A, respectively. As will be understood from FIGS. 13A and 13B, the contention-free random access procedure may not include messages analogous to the Msg 31313 and / or the Msg 41314.Docket No.: 25-1052PCT

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

[0189] 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 21322. The UE may determine that a random access procedure successfully completes, for example, if a PDCCH transmission is addressed to a C-RNTI. The UE may determine that a random access procedure successfully completes, for example, if the UE receives an RAR comprising a preamble identifier corresponding to a 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.

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

[0191] Msg A 1331 may be transmitted in an uplink transmission by the UE. Msg A 1331 may comprise one or more transmissions of a preamble 1341 and / or one or more transmissions of a transport block 1342. The transport block 1342 may comprise contents that are similar and / or equivalent to the contents of the Msg 31313 illustrated in FIG. 13A. The transport block 1342 may comprise UCI (e.g., an SR, a HARQACK / 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. 13Aand 13B and / or the Msg 41314 illustrated in FIG. 13A.

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

[0193] 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 theDocket No.: 25-1052PCTMsg A 1331. The RACH parameters may indicate a modulation and coding schemes (MGS), a time-frequency resource, and / or a power control for the preamble 1341 and / or the transport block 1342. A time-frequency resource for transmission of the preamble 1341 (e.g., a PRACH) and a time-frequency resource for transmission of the transport block 1342 (e.g., a PUSCH) may be multiplexed using FDM, TDM, and / or CDM. The RACH parameters may enable the UE to determine a reception timing and a downlink channel for monitoring for and / or receiving Msg B 1332.

[0194] The transport block 1342 may comprise data (e.g., delay-sensitive data), an identifier of the UE, security information, and / or device information (e.g., an International Mobile Subscriber Identity (IMSI)). The base station may transmit the Msg B 1332 as a response to the Msg A 1331. The Msg B 1332 may comprise at least one of following: a preamble identifier; a timing advance command; a power control command; an uplink grant (e.g., a radio resource assignment and / or an MGS); a UE identifier for contention resolution; and / or an RNTI (eg., 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).

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

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

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

[0198] 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 responseDocket No.: 25-1052PCT(RAR). A DCI having CRC parity bits scrambled with a cell RNTI (C-RNTI) may indicate a dynamically scheduled unicast transmission and / or a triggering of PDCCH-ordered random access. A DCI having CRC parity bits scrambled with a temporary cell RNTI (TC-RNTI) may indicate a contention resolution (e.g., a Msg 3 analogous to the Msg 31313 illustrated in FIG. 13A). Other RNTIs configured to the UE by a base station may comprise a Configured Scheduling RNTI (CS-RNTI), a Transmit Power Control-PUCCH RNTI (TPC-PUCCH-RNTI), a Transmit Power Control-PUSCH RNTI (TPC-PUSCH-RNTI), a Transmit Power Control-SRS RNTI (TPC-SRS-RNTI), 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.

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

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

[0201] 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 1402Docket No.: 25-1052PCTin the frequency domain. A third CORESET 1403 occurs ata third symbol in the slot. A fourth CORESET 1404 occurs at the seventh symbol in the slot. CORESETs may have a different number of resource blocks in frequency domain.

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

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

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

[0205] 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-Docket No.: 25-1052PCTSCH transport blocks. The UE may transmit the HARQ acknowledgements after receiving a DL-SCH transport block. Uplink control signaling may comprise channel state information (CSI) indicating channel quality of a physical downlink channel. The UE may transmit the CSI to the base station. The base station, based on the received CSI, may determine transmission format parameters (e.g., comprising multi-antenna and beamforming schemes) for a downlink transmission. Uplink control signaling may comprise scheduling requests (SR). The UE may transmit an SR indicating that uplink data is available for transmission to the base station. The UE may transmit a UCI (e.g., HARQ acknowledgements (HARQ-ACK), CSI report, SR, and the like) via a physical uplink control channel (PUCCH) or a physical uplink shared channel (RUSCH). The UE may transmit the uplink control signaling via a PUCCH using one of several PUCCH formats.

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

[0207] 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 configured1Docket No.: 25-1052PCTvalue 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”.

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

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

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

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

[0212] 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 processingDocket No.: 25-1052PCTsystem 1520 may implement layer 1 OSI functionality. Layer 1 may include a PHY layer with respect to FIG. 2A, FIG 2 B , FIG.3, and FIG. 4A. For transmit processing, the PHY layer may perform, for example, forward error correction coding of transport channels, interleaving, rate matching, mapping of transport channels to physical channels, modulation of physical channel, multiple-input multiple-output (Ml MO) or multi-antenna processing, and / or the like.

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

[0214] As shown in FIG. 15, a wireless device 1502 and the base station 1504 may include multiple antennas. The multiple antennas may be used to perform one or more MIMO or multi-antenna techniques, such as spatial multiplexing (e.g., single-user MIMO or multi-user MIMO), transmit / receive diversity, and / or beamforming. In other examples, the wireless device 1502 and / or the base station 1504 may have a single antenna.

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

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

[0217] 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,Docket No.: 25-1052PCTa speaker, a microphone, a keypad, a display, a touchpad, a power source, a satellite transceiver, a universal serial bus (USB) port, a hands-free headset, a frequency modulated ( FM) radio unit, a media player, an Internet browser, an electronic control unit (e.g. , for a motor vehicle), and / or one or more sensors (e.g. , an accelerometer, a gyroscope, a temperature sensor, a radar sensor, a lidar sensor, an ultrasonic sensor, a light sensor, a camera, and / or the like). The processing system 1508 and / or the processing system 1518 may receive user input data from and / or provide user output data to the one or more peripherals 1516 and / or the one or more peripherals 1526. The processing system 1518 in the wireless device 1502 may receive power from a power source and / or may be configured to distribute the power to the other components in the wireless device 1502. The power source may comprise one or more sources of power, for example, a battery, a solar cell, a fuel cell, or any combination thereof. The processing system 1508 and / or the processing system 1518 may be connected to a GPS chipset 1517 and a GPS chipset 1527, respectively. The GPS chipset 1517 and the GPS chipset 1527 may be configured to provide geographic location information of the wireless device 1502 and the base station 1504, respectively.

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

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

[0220] 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.Docket No.: 25-1052PCT

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

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

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

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

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

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

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

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

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

[0230] A base station may transmit one or more messages to a wireless device. The one or more messages may comprise the one or more MAC PDUs. The wireless device may receive at least one message of the one or more messages via / using one or more PDSCHs / TBs.

[0231] The one or more messages may comprise one or more RRC messages. The one or more RRC messages may comprise at least one RRC connection / establishment / configu ration / setup message. The one or more RRC messages may comprise at least one RRC recon nection / reestablish ment / reconfigu ration message. The one or more RRC messages may comprise at least one RRC release message.

[0232] The one or more messages may comprise one or more MAC CEs. The one or more messages may comprise one or more DCIs.

[0233] The one or more messages may comprise one or more commands (e.g., control commands) for UL / DL communications. The one or more messages may comprise one or more configuration parameters. The one or more configuration parameters may correspond to one or more signals / channels. The one or more channels / signals 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.

[0234] The one or more messages may configure the wireless device with a carrier aggregation (CA) operation. In the carrier aggregation (operation), two or more component carriers (CCs) may be aggregated. Each carrier may be also referred to by / as a cell (e.g., serving cell). The cell may be a secondary cell (SCell) ora primary cell (PCell). The wireless device may, using the technique of CA, may simultaneously receive or transmit on one or more CCs (depending on capabilities of the wireless device) or perform an UL carrier switch (e.g., Tx switch or Tx carrier switch) for transmitting on a carrier of a plurality of CCs. The one or more configuration parameters may configure / indicate the plurality of CCs. In an example, the wireless device may support CA for contiguous CCs of the plurality of CCs and / or for non-contiguous CCs of the plurality of CCs. In some implementations, the plurality of CCs may be organized / grouped into one or more cells, e.g., a combination of the primary cell (PCell) and one or more secondary cells (SCells). A component carrier may be also referred to as a carrier or a band.

[0235] The one or more configuration parameters may, for example via one or more serving cell configuration parameters, comprise / configure / indicate the one or more cells (e.g., ServingCellConfigCommon, ServingCellConfigCommonSI B, and / or ServingCellConfig). The one or more cells may comprise one or more serving cell (e.g., the one or more Serving Cells). 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 aDocket No.: 25-1052PCTsecondary TAG (sTAG). For example, at least one carrier of the plurality of carriers may be associated / correspond to a cell of the one or more cells, e.g., the one or more configuration parameters configure the at least one carrier for the cell.

[0237] In an example, the one or more cells may comprise the one or more SCells, depending on capabilities of the wireless device. When configured with th eCA, the base station and / or the wireless device may employ an activation / deactivation mechanism of an SCell of the one or more SCell to improve battery or power consumption of the wireless device. When the wireless device is configured with the one or more SCells, the base station may activate or deactivate (e.g., via MAC CE or DCI) at least one of the one or more SCells. Upon configuration of an SCell (e.g., via the one or more serving cell configuration parameters), the SCell may be deactivated unless the SCell state associated with the SCell is set to "activated" or "dormant', via a DCI or MAC CE. The wireless device may activate / deactivate the SCell in response to receiving an SCell Activation / Deactivation MAC CE.

[0238] For example, the base station may configure (e.g., via the one or more RRC messages / configuration parameters) the wireless device with one or more bandwidth parts (BWPs). The one or more BWPs may, corresponding to each cell of the one or more cells, comprise one or more uplink (UL) bandwidth parts (BWPs) and / or one or more downlink (DL) BWPs. For the cell (e.g., a PCell), an initial active BWP may be a first BWP used for initial access. In paired spectrum (e.g., an FDD carrier / cell), the base station and / or the wireless device may independently switch a DL BWP (of the one or more BWPs) and an UL BWP (of the one or more BWPs) configured for the cell. In unpaired spectrum (e.g., a TDD carrier / cell), the base station and / or the wireless device may simultaneously switch the DL BWP and the UL BWP. In the present disclosure, a BWP on the one or more BWPs may be an UL BWP or a DL BWP.

[0239] The one or more configuration parameters may comprise one or more BWP configuration parameters to configure / indicate the one or more BWPs of a (each) cell of the one or more cells. 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 DCI) 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.

[0240] A wireless device may start (or restart) a BWP inactivity timer (e.g., bwp- Inactivity Timer) 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 sCellDeactivationTimer expires (e.g., if the cell IsaDocket No.: 25-1052PCTSCell). In response to the cell being a PCell, the wireless device may not deactivate the cell and may not apply the sCellDeactivationTimer on the PCell.

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

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

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

[0244] The one or more configuration parameters (e.g., the one or more BWP configuration parameters, e.g., BWP-DownlinkCommon and / or BWP-DownlinkDedicated) may comprise one or more PDCCH configuration parameters (e.g., PDCCH-ConfigCommon and / or PDCCH-Config and / or PDCCH-ConfigSI B 1 and / or PDCCH-ServingCellConfig). The one or more PDCCH configuration parameters may be for receiving / detecting PDCCHs / DCIs via a BWP (of the one or more BWPs) on a cell / carrier (of the one or more cells / a plurality of carriers). For example, the one or more PDCCH configuration parameters may configure each BWP (of the one or more BWPs configured for the cell / carrier) of the cell / carrier with corresponding PDCCH-Config and / or PDSCH-ConfigCommon for receiving PDCCHs via the BWP on the cell / carrier. the one or more PDCCH configuration parameters (e.g., PDCCH-ServingCellConfig) may comprise at least one PDCCH configuration parameter common across all BWPs of the one or more BWPs of the cell / carrier. For receiving PDCCHs, by the wireless device and via a BWP (of the one or more BWPs) on a cell / carrier (of the one or more cells / a plurality of carriers), may be based on the one or more PDCCH configuration parameters (e.g., PDCCH-ConfigCommon and / or PDCCH-Config) corresponding to the BWP.

[0245] The following shows an example of the one or more PDCCH configuration parameters:Docket No.: 25-1052PCTPDCCH-ConfigThe IE PDCCH-Config is used to configure UE specific PDCCH parameters or MBS multicast PDCCH parameters such as control resource sets (CORESET), search spaces and additional parameters for acquiring the PDCCH. If this IE is used for the scheduled SCell in case of cross carrier scheduling, the fields other than searchSpacesToAddModList and searchSpacesToReleaseList are absent. If the IE is used for a dormant BWP, the fields other than controlResourceSetToAddModList and controlResourceSetToReleaseList are absent. If this IE is used for MBS CFR, the field downlinkPreemptiom,tpc-PUSCH, tpc-SRS, up / inkCancellation, monitoringCapabilityConfig, and searchSpaceSwitchConfig are absent.PDCCH-Config information element-ASN1 START- TAG-PDCCH-CONFIG-STARTPDCCH-Config ::= SEQUENCE {controlResourceSetToAddModList SEQU E NC E(S IZE (1..3)) OF ControlResourceSetOPTIONAL, - Need NcontrolResourceSetToReleaseList SEQUE NC E(SIZE (1..3)) OF Control ResourceSetldOPTIONAL, - Need NsearchSpacesT oAdd Mod Li st SEQUENCE(SIZE (1..10)) OF SearchSpace OPTIONAL, - Need NsearchSpacesToReleaseList SEQUENCE(SIZE (1..10)) OF SearchSpaceld OPTIONAL, - Need NdownlinkPreemption SetupRelease { DownlinkPreemption } OPTIONAL, - Need Mtpc-PUSCH SetupRelease { PUSCH-TPC-CommandConfig } OPTIONAL, - Need Mtpc-PUCCH SetupRelease { PUCCH-TPC-CommandConfig } OPTIONAL, - Need Mtpc-SRS SetupRelease { SRS-TPC-CommandConfig) OPTIONAL, - Need[[controlResourceSetToAddModListSizeExt-v1610 SEQUENCE (SIZE (1..2)) OF Control ResourceSet OPTIONAL, - Need NDocket No.: 25-1052PCTcontrolResourceSetToReleaseListSizeExt-r16 SEQUENCE (SIZE (1 .5)) OF ControlResourceSetld-r16 OPTIONAL, -NeedNsearchSpacesToAddModListExt-r16 SEQUENCE(SIZE (1..10)) OF SearchSpaceExt-r16 OPTIONAL, - Need NuplinkCancellation-r16 SetupRelease { UplinkCancellation-r16 } OPTIONAL, - Need MmonitoringCapabilityConfig-r16 ENUMERATED { r15monitoringcapability,r16monitoringcapability } OPTIONAL, - Need MsearchSpaceSwitchConfig-r16 SearchSpaceSwitchConfig-r16 OPTIONAL - Need R]].[[searchSpacesToAddModListExt-v1700 SEQ UE NCE(SI ZE (1..10)) OF SearchSpaceExt-v1700 OPTIONAL, - Need NmonitoringCapabilityConfig-v1710 ENUMERATED { r17monitoringcapability } OPTIONAL, - - Need MsearchSpaceSwitchConfig-r17 SearchSpaceSwitchConfig-r17 OPTIONAL, - Need Rpdcch-SkippingDurationList-r17 SEQU E NCE(SIZE (1 .3)) OF SCS-SpecificDuration-r17OPTIONAL - NeedR]],[[pdcch-MonitoringResumptionAfterNack-r18 ENUMERATED {true} OPTIONAL, - Need RsearchSpacesToAddModListExt-v1800 SEQ UE NCE(SI ZE (1..10)) OF SearchSpaceExt-v1800 OPTIONAL - Need N11SearchSpaceSwitchConfig-r16 ::= SEQUENCE {cellGroupsForSwitchList-r16 SEQUENCE(SIZE (1..4)) OF CellGroupForSwitch-r16OPTIONAL, - Need RsearchSpaceSwitchDelay-r16 INTEGER (10..52) OPTIONAL - Need RDocket No.: 25-1052PCTSearchSpaceSwitchConfig-r17 : SEQUENCE {searchSpaceSwitchTimer-r17 SCS-SpecificDuration-r17 OPTIONAL, - NeedsearchSpaceSwitchDelay-r17 INTEGER (10..52) OPTIONAL - NeedRCellGroupForSwitch-r16 ::= SEQUENCE(SIZE (1..16)) OF ServCell IndexSCS-SpecificDuration-r17 ::= INTEGER (1..166)-TAG-PDCCH-CONFIG-STOP-ASN1STOPcontrolResourceSetToAddModList, controlResourceSetToAddModListSizeExtList of UE specifically configured Control Resource Sets (CORESETs) to be used by the UE. The UE shall consider entries in controlResourceSetToAddModList and in controlResourceSetToAddModListSizeExt as a single list, i.e. an entry created using controlResourceSetToAddModList can be modified using controlResourceSetToAddModListSizeExt (or deleted using controlResourceSetToReleaseListSizeExt) and vice- versa. In case network reconfigures control resource set with the same ControlResourceSetld as used for commonControlResourceSet or commonControlResourceSetExt configured via PDCCH-ConfigCommon or via SIB20, the configuration from PDCCH-Config always takes precedence and should not be updated by the UE based on servingCellConfigCommon or based on SIB20.controlResourceSetToReleaseList, controlResourceSetToReleaseListSizeExtList of UE specifically configured Control Resource Sets (CORESETs) to be released by the UE. This field only applies to CORESETs configured by controlResourceSetToAddModList or controlResourceSetToAddModListSizeExt and does not release the field commonControlResourceSet configured by PDCCH-ConfigCommon and commonControlResourceSetExt configured by SIB20.

[0246] The one or more PDCCH configuration parameters may configure / indicate a set of PDCCH candidates for the wireless device to monitor via / in terms of one or more search space sets. For example, the one or more PDCCH configuration parameters may configure / indicate the one or more search space sets. A search space set of the one or more search space sets may comprise a common search space (CSS) set, or a UE-specific search space (USS) set The wireless device may monitor one or more PDCCH candidates (of the set of PDCCH candidates) in one or more of the search space sets.Docket No.: 25-1052PCT

[0247] A search space set may be a TypeO-PDCCH CSS set configured by the pdcch-ConfigSIB1 (e.g., in MIB) or by searchSpaceSIBI in the PDCCH-ConfigCommon or by searchSpaceZero in the PDCCH-ConfigCommon.

[0248] A search space set may be a TypeOA-PDCCH CSS set configured by searchSpaceOtherSystemlnformation in the PDCCH-ConfigCommon for a DCI format with CRC scrambled by the SI-RNTI on the primary cell of the MCG.

[0249] A search space set may be a Typel-PDCCH CSS set configured by ra-SearchSpace in the PDCCH-ConfigCommon fora DCI format with CRC scrambled by a RA-RNTI, a MSGB-RNTI, ora TC-RNTI on the primary cell.

[0250] A search space set may be a Type2-PDCCH CSS set configured by pagingSearchSpace in the PDCCH-ConfigCommon for a DCI format with CRC scrambled by a P-RNTI on the primary cell of the MCG.

[0251] A search space set may be a Type3-PDCCH CSS set configured by SearchSpace in the PDCCH-Config with searchSpaceType = common for DCI formats with CRC scrambled by at least one RNTI. The at least one RNTI may comprise one of the following: an I NT-RNTI, an SFI-RNTI, a TPC-PUSCH-RNTI, a TPC-PUCCH-RNTI, a TPC-SRS-RNTI, a CI-RNTI, or a power saving RNTI (PS-RNTI) and, only for the primary cell, a C-RNTI, a MCS-C-RNTI, or a CS-RNTI(s).

[0252] A search space set may be a a USS set configured by SearchSpace in the PDCCH-Config with searchSpaceType = ue-Specific for DCI formats with CRC scrambled by the C-RNTI, the MCS-C-RNTI, a SP-CSI-RNTI, the CS-RNTI(s), a SL-RNTI, a SL-CS-RNTI, ora SL-L-CS-RNTI.

[0253] To receive DCIs (or PDCCHs), the wireless device may monitor the one or more PDCCH candidates in one or more CORESETs for detecting one or more DCIs. The one or more PDCCH configuration parameters may configure / indicate the one or more CORESETs. Monitoring the one or more PDCCH candidates (for receiving DCIs or PDCCHs) may comprise decoding at least one PDCCH candidate of the one or more PDCCH candidates according to the monitored DCI formats. For example, monitoring the one or more PDCCH candidates may comprise decoding (e.g., blind decoding) a DCI content of the at least one PDCCH candidate via possible (or configured) PDCCH location(s), possible (or configured) PDCCH format(s), e.g., number of CCEs, number of PDCCH candidates in CSS set(s), and / or number of PDCCH candidates in the USS(s), and / or possible (or configured) DCI format(s).

[0254] For example, a DCI (e.g., a DCI format) may be a scheduling DCI. The DCI may schedule on or more UL transmissions via a cell / carrier. The cell may be one of the one or more cells. The carrier may be one or the plurality of carriers. Alternatively, the DCI may schedule one or more DL receptions via the cell / carrier.

[0255] In the specification, a scheduling carrier / cell may refer to a carrier / cell, where the wireless device monitors PDCCH candidates to receive DCIs. A scheduled carrier / cell may refer to a carrier / cell, where the wireless device receives PDSCHs scheduled by the DCIs or transmits PUSCHs / PUCCHs / SRSs scheduled by the DCIs. As discussed also above, a cross-carrier scheduling may refer that the scheduling carrier / cell may be different from the scheduled carrier / cell. A self-carrier scheduling may refer that the scheduling carrier / cell may be same to the scheduled carrier / cell.Docket No.: 25-1052PCT

[0256] In one example, the DCI may be a self-carrier scheduling DCI, e.g . , the DCI may be used for a self-carrier scheduling. In the self-carrier scheduling, a scheduling cell (or equivalently a scheduling carrier) is the same as the scheduled cell (or equivalently a scheduled carrier). The wireless device may receive, via the cell / carrier (e.g., the scheduling cell / carrier), the DCI scheduling the one or more UL transmissions via the cell / carrier (e.g., the scheduled cell / carrier) and / or the one or more DL receptions via the cell / carrier (e.g., the scheduled cell / carrier).

[0257] In the self-carrier scheduling: Receiving (by the wireless device) the DCI is via the active DL BWP of the one or more BWPs (corresponding / associated with the scheduling cell / carrier); and / or Receiving (by the wireless device) the one or more DL receptions is via the active DL BWP of the one or more BWPs (corresponding / associated with the scheduling cell / carrier); and / or Transmitting (by the wireless device) the one or more UL transmissions is via the active UL BWP of the one or more BWPs (corresponding / associated with the scheduling cell / carrier).

[0258] In another example, the DCI may be a cross-carrier scheduling DCI, e.g., the DCI may be used for a crosscarrier scheduling via a carrier indicator field (CIF) of the DCI. In the cross-carrier scheduling, the scheduling cell is different than the scheduled cell (e.g., indicated by the CIF field of the DCI). The wireless device may receive, via the cell / carrier (e.g., the scheduling cell / carrier), the DCI (e.g., comprising the CIF field) scheduling the one or more UL transmissions via a second cell / carrier (of the one or more cells and / or the plurality of CCs), e.g., the scheduled cell / carrier, and / or the one or more DL receptions via the second cell / carrier (e.g., the scheduled cell / carrier).

[0259] In the cross-carrier scheduling: Receiving (by the wireless device) the DCI (e.g., comprising a carrier indicator field (CIF)) is via the active DL BWP of the one or more BWPs (corresponding / associated with the scheduling cell / carrier); and / or Receiving (by the wireless device) the one or more DL receptions is via an active DL BWP of the one or more BWPs (corresponding / associated with the scheduled cell / carrier indicated by the CIF field of the DCI); and / or Transmitting (by the wireless device) the one or more UL transmissions is via an active UL BWP of the one or more BWPs (corresponding / associated with the scheduled cell / carrier indicated by the CIF field of the DCI).

[0260] The one or more configuration parameters (e.g., ServingCellConfig) may comprise / indicate / configure the cross-carrier scheduling for the cell / carrier (e.g., a serving cell), e.g., via cross-carrier scheduling configuration (e.g., CrossCarrierSchedulingConfig). The following shows an example of the cross-carrier scheduling:Docket No.: 25-1052PCTCrossCarrierSchedulingConfigThe IE CrossCarrierSchedulingConfig is used to specify the configuration when the cross-carrier scheduling is used in a cell.CrossCarrierSchedulingConfig information element-ASN1 START-TAG-CROSSCARRIERSCHEDULINGCONFIG-STARTCrossCarrierSchedulingConfig ::= SEQUENCE {schedulingCelllnfo CHOICE {own SEQUENCE { - Cross carrier scheduling: scheduling cell cif-Presence BOOLEANother SEQUENCE { - Cross carrier scheduling: scheduled cell schedulingCellld ServCelllndex,cif-lnSchedulingCell INTEGER (1..7)[[carrierlndicatorSize-r16 SEQUENCE {carrierlndicatorSizeDCI-1 -2-r16 INTEGER (0.3),carrierlndicatorSizeDCI-0-2-r16 INTEGER (0..3)OPTIONAL, -Cond CIF-PRESENCE enableDefaultBeamForCCS-r16 ENUMERATED {enabled} OPTIONAL - Need S 11,[[ccs-BlindDetectionSplit-r17 ENUMERATED {oneSeventh, threeFourteenth, twoSeventh, threeSeventh, oneHalf, fourSeventh, fiveSeventh, sparel} OPTIONAL - NeedR11-TAG-CROSSCARRIERSCHEDULINGCONFIG-STOP-ASN1STOPDocket No.: 25-1052PCTcarrierlndicatorSizeDCI-0-2, carrierlndicatorSizeDCI-1-2Configures the number of bits for the field of carrier indicator in PDCCH DCI format 0_2 / 1_2. The field carrierlndicatorSizeDC 1-0-2 refers to DCI format 0_2 and the field carrierlndicatorSizeDC 1-1 -2 refers to DCI format 1_2, respectively.ccs-BlindDetectionSplitIndicates the share of blind detection candidates and non-overlapping CCEs for PDCCH monitoring on an SpCell and an SCell when cross-carrier scheduling is configured from the SCell for the SpCell. The network only configures this field when it sets the field other for an SpCell, i.e., when it configures cross-carrier scheduling of the SpCell by a PDCCH on an Scell.cif-PresenceThe field is used to indicate whether carrier indicator field is present (value true) or not (value false) in PDCCH DCI formats. If cif-Presence is set to true, the CIF value indicating a grant or assignment for this cell is 0.cif-ln SchedulingCellThe field indicates the CIF value used in the scheduling cell to indicate a grant or assignment applicable for this cell. If configured for an SpCell, the non-fallback DCI formats on the SpCell include same number of CIF bits as the corresponding non-fallback DCI formats on the scheduling cell, and the CIF bits are considered reserved. otherParameters for cross-carrier scheduling. If configured for an SpCell, the SpCell can be scheduled by the PDCCH on another SCell as well as by the PDCCH on the SpCell. If configured for an SCell, the SCell is scheduled by a PDDCH on another cell.ownParameters for self-scheduling, i.e., a serving cell is scheduled by its own PDCCH.schedulingCellldIf configured for an SpCell, this field indicates which SCell, in addition to the SpCell, signals the downlink allocations and uplink grants, if applicable, for the concerned SpCell. If configured for an Scell, this field indicates which cell signals the downlink allocations and uplink grants, if applicable, for the concerned SCell. In case the UE is configured with DC, the scheduling cell is part of the same cell group (i.e. MCG or SCG) as the scheduled cell. In case the UE is configured with two PUCCH groups, the scheduling cell and the scheduled cell are within the same PUCCH group. If drx-ConfigSecondaryGroup is configured in the MAC-CellGroupConfig associated with this serving cell, the scheduling cell and the scheduled cell belong to the same Frequency Range. In addition, the serving cell with an aperiodic CSI trigger and the PUSCH resource scheduled for the report are on the same carrier and serving cell, but the cell for which CSI is reported may belong to the same or a differentDocket No.: 25-1052PCTFrequency Range. The network should not trigger a CSI request for a serving cell in the other Frequency Range when that serving cell is outside Active Time.

[0261] The cross-carrier scheduling configuration (of the cell / carrier) may indicate whether the cell / carrier (e.g . , the serving cell) is cross-carrier scheduled by another cell / carrier (e.g., another serving cell) or whether the cell / carrier cross-carrier schedules another cell / carrier (e.g., another serving cell), e.g., the second cell / carrier.

[0262] When the cross-carrier scheduling configuration (of the cell / carrier) indicates the cell / carrier (e.g., the serving cell) is cross-carrier scheduled by a third cell / carrier (e.g., a third serving cell of the one or more cells or a third carrier of the plurality of CCs), the wireless device may receive the DCI (e.g., comprising a carrier indicator field (GIF)) via the third cell / carrier scheduling the one or more DL / UL receptions / transmissions on / via the cell / carrier, e.g., the scheduled cell may the cell / carrier and the scheduling cell / carrier may be the third cell / carrier (e.g., the GIF field indicates the cell / carrier for the one or more DL / UL receptions / transmissions). The third cell / carrier may be the second cell / carrier. The third cell / carrier may be different than the second cell / carrier.

[0263] When the cross-carrier scheduling configuration (of the cell / carrier) indicates the cell / carrier cross-carrier schedules another cell / carrier (e.g., another serving cell), e.g., the second cell / carrier, the wireless device may receive the DCI (e.g., comprising the carrier indicator field (GIF)) via the cell / carrier scheduling the one or more DL / UL receptions transmissions on / via the second cell / carrier, e.g., the scheduled cell may be the second cell / carrier and the scheduling cell / carrier may be the cell / carrier (e.g., the GIF field indicates the second cell / carrier for the one or more DL / UL receptions / transmissions).

[0264] The cross-carrier scheduling configuration (of the cell / carrier) may configure / indicate / comprise, e.g., via a scheduling cell information (e.g., schedul ingCel II nfo), a first field (cif-Presence). The first field of the cross-carrier scheduling configuration may be with a Boolean value (value true or value false). The first field of the cross-carrier scheduling configuration may indicate whether a carrier indicator field (GIF) is present (value true) or not (value false) in the DCI (e.g., PDCCH DCI formats). If the first field is set false, the carrier indicator filed may not be present in the DCI. If cif-Presence is set to true, the GIF value indicated by the DCI indicating a grant or assignment for this cell is 0.

[0265] If the field other is configured for an SpCell (i.e., the SpCell is cross-carrier scheduled by another serving cell), the SpCell can be additionally scheduled by the PDCCH on the SpCell

[0266] In present disclosure, the one or more DL receptions may comprise PDSCHs. A PDSCH may be an SPS PDSCH (e.g., configured / indicated by a configured downlink assignment) ora dynamically scheduled PDSCH (e.g., according to dynamic grant provided / indicated by the scheduling DCI). For example, the one or more configuration parameters (e.g., via BWP-DownlinkDedicated) may comprise one or more semi-persistent scheduling (SPS) configuration parameters for receiving SPS PDSCHs via a BWP (of the one or more BWPs) on a cell / carrier (of the one or more cells / a plurality of carriers). A SPS configuration of the one or more SPS configurations may be a unicast SPS configuration or a multicast SPS configuration.Docket No.: 25-1052PCT

[0267] A SPS configuration may comprise at least one of the following: SPS configuration ID / index; and / or a periodicity of the corresponding DL SPS; and / or a HARQ codebook ID indicating a HARQ-ACK codebook index for a corresponding HARQ-ACK codebook for SPS PDSCH and ACK for SPS PDSCH release; and / or a modulation and coding scheme table corresponding to the DL SPS; a number of repetitions for the SPS PDSCH (e.g. , pdsch-Aggregation Factor); and / or nrofHARQ-Processes indicating a number of HARQ processes for the DL SPS.

[0268] The base station may transmit to the wireless device the DCI (e.g., an activating DCI) with a CS-RNTI (or a G-CS-RNTI) for activating the SPS configuration. The wireless device may receive a PDCCH providing / with the DCI. For example, the wireless device may validate the DCI / PDCCH to determine the DCI activating the SPS configuration. An NDI field of the DCI may set to 0. A DPI flag field of the DCI may set to 0. The activating DCI may be the scheduling DCI.

[0269] When the one or more SPS configuration parameters configure at least two SPS configurations, a HARQ process number / ID field of the DCI may indicate a SPS configuration index of the SPS configuration of the at least two SPS configurations.

[0270] After the SPS configuration being activated (based on the DCI), the wireless device may receive DL data (via the BWP where the SPS configuration is provided) via / using configured DL assignments configured by the SPS configuration and the DCI. The DCI may indicate frequency resources (e.g., “Frequency domain resource assignment” field of the DCI) and / or VRB-to-PRB mapping and / or rate matching indicator for receiving the SPS PDSCH(s). The DCI may indicate time domain resources (e.g., via a 'Time domain resource assignment' field of the activating DCI). The time domain resources may indicate a row of a time domain resource allocation table (TDRA) configured by the one or more configuration parameters.

[0271] When the SPS configuration is activated, the wireless device may receive a first SPS PDSCH, e.g., a PDSCH scheduled by DCI format 1 J or 1_2 in PDCCH with CRC scrambled by CS-RNTI with NDI=0. The wireless device may receive SPS PDSCHs after the first SPS PDSCH PDSCH(s), e.g., PDSCHs scheduled without corresponding PDCCH transmission using the SPS configuration (e.g., sps-Config) and activated by the activating DCI

[0272] The wireless device may receive SPS PDSCH (comprising the first SPS PDSCH and the SPS PDSCHs after the first SPS PDSCH PDSCH(s)) using / via a same symbol allocation across the pdsch-Aggregation Factor. The wireless device may use the pdsch-Aggregation Factor indicated by the SPS configuration or by pdsch-config of the one or more configuration parameters. The wireless device may expect that a TB is repeated within each symbol allocation among each of the pdsch-Agg regation Factor consecutive slots and the PDSCH is limited to a single transmission layer.

[0273] The one or more configuration parameters (e.g., the one or more BWP configuration parameters, e.g., BWP-DownlinkCommon and / or BWP-DownlinkDedicated) may comprise one or more PDSCH configuration parameters (e.g., PDSCH-ConfigCommon and / or PDSCH-Config) for receiving PDSCHs via a BWP (of the one or more BWPs) on a cel l / carrier (of the one or more cells / a plurality of carriers). For example, the one or more configuration parameters may configure each BWP (of the one or more BWPs configured for the cell / carrier) of the cell / carrier with correspondingDocket No.: 25-1052PCTPDSCH-ConfigCommon and / or PDSCH-Config for receiving PDSCHs via the BWP on the cell / carrier. Receiving PDSCHs, by the wireless device and via a BWP (of the one or more BWPs) on a cell / carrier (of the one or more cells / a plurality of carriers), may be based on the one or more PDSCH configuration parameters (e.g., PDSCH-ConfigCommon and / or PDSCH-Config) corresponding to the BWP.

[0274] The one or more PDSCH configuration parameters may comprise one or more cell-specific PDSCH configuration parameters (of the cell / carrier) and / or one or more UE-specific PDSCH configuration parameters. The one or more PDSCH configuration parameters may configure / indicate at least one of the following: DM-RS configuration; and / or TCI configuration; and / or time domain resource allocation (pdsch-TimeDomainAllocationList); and / or a resource allocation in frequency domain (resourceAllocation and / or resourceAllocationDCI-1 -2); and / or the like. The one or more PDSCH configuration parameters may indicate / comprise a DL resource allocation scheme (resourceAllocation and / or resourceAllocation DC 1-1 -2) for receiving (SPS) PDSCHs. The DL resource allocation (scheme) may be a resource allocation type 0 (e.g., resourceAllocationTypeO or a type 0 resource allocation) or a resource allocation type 1 (e.g., resourceAl locationType 1 or a type 1 resource allocation). The wireless device may receive, during a symbol / slot of a plurality of symbols / slots, (SPS) PDSCHs based on the configured / indicated resource allocation scheme.

[0275] The following shows an example of the one or more PDSCH configuration parameters:Docket No.: 25-1052PCTPDSCH-ConfigThe PDSCH-Config IE is used to configure the UE specific PDSCH parameters. If this IE is used for MBS CFR, the following fields shall be absent: tci-StatesToAddModList, tci-StatesToReleaseList, zp-CSI-RS- ResourceToAddModList, minimumSchedulingOffsetKO, antennaPortsFieldPresenceDCI-1-2, aperiodicZP-CSi- RS-ResourceSetsToAddModListDCI-1-2, aperiodicZP-CSI-RS-ResourceSetsToReleaseUstDCI-1-2, dmrs- DownlinkForPDSCH-MappingTypeA-DCI-1-2, dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2, dmrs- SequencelnitializationDCI-1-2, harq-ProcessNumberSizeDCI-1-2, mcs-TableDCI-1-2, numberOfBitsForRV-DCI- 1-2, pdsch-AggregationFactor, pdsch-TimeDomainA / locationListDCI-1-2, prb-BundlingTypeDCI-1-2, prioritylndicatorDCI- 1 -2, rateMatchPatternGroup 1 DC 1-1 -2, rateMatchPattern Group2DC I- 1 -2, resourceAllocationType1Granu!arityDCI-1-2, vrb-ToPRB-lnterleaverDCI-1-2, referenceOfSLIVDCI-1-2, resource AllocationDCI-1 -2, dataScramblingldentityPDSCH2-r16, repetition SchemeConfig, pdsch-ConfigDCI-1 -3.PDSCH-Config information element-ASN1 START- TAG-PDSCH-CONFIG-STARTPDSCH-Config ::= SEQUENCE {dataScramblingldentityPDSCH INTEGER (0.1023) OPTIONAL, - NeedSdmrs-DownlinkForPDSCH-MappingTypeA SetupRelease { DMRS-DownlinkConfig }OPTIONAL, - Need Mdmrs-DownlinkForPDSCH-MappingTypeB SetupRelease { DMRS-DownlinkConfig }OPTIONAL, - Need Mtci-StatesToAddModList SEQUENCE (SIZE(1..maxNrofTCI-States)) OFTCI-State OPTIONAL, - Need Ntci-StatesToReleaseList SEQUENCE (SIZE(1..maxNrofTCI-States)) OF TCI-Stateld OPTIONAL, - Need Nvrb-ToPRB-lnterleaver ENUMERATED {n2, n4} OPTIONAL, - NeedSresourceAl location ENUMERATED { resourceAllocationTypeO, resourceAllocationTypel, dynamicSwitch},pdsch-TimeDomainAllocationList SetupRelease { PDSCH-TimeDomainResourceAllocationList} OPTIONAL, - Need MDocket No.: 25-1052PCTpdsch-AggregationFactor ENUMERATED { n2, n4, n8 } OPTIONAL, - Need SrateMatchPatternToAddModList SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPattern OPTIONAL, -- Need NrateMatchPatternToReleaseList SEQUENCE (SIZE (1.. maxNrofRateMatchPatterns)) OF RateMatchPatternld OPTIONAL, - Need NrateMatchPatternGroupI RateMatchPatternGroup OPTIONAL, - Need RrateMatchPatternGroup2 RateMatchPatternGroup OPTIONAL, - Need Rrbg-Size ENUMERATED {config 1 , config2},mcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, - Need SmaxNrofCodeWordsScheduledByDCI ENUMERATED {n 1 , n2}OPTIONAL, - Need Rprb-BundlingType CHOICE {staticBundling SEQUENCE {bundleSize ENUMERATED { n4, wideband} OPTIONAL - Need SdynamicBundling SEQUENCE }bundleSizeSetl ENUMERATED { n4, wideband, n2-wideband, n4-wideband } OPTIONAL, - Need SbundleSizeSet2 ENUMERATED { n4, wideband} OPTIONAL - Need Szp-CSI-RS-ResourceToAddModList SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-Resources)) OF ZP-CSI-RS-ResourceOPTIONAL, - Need Nzp-C S I- RS-Resou rceT o ReleaseList SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-Resources)) OFZP- CSI-RS-ResourceldDocket No.: 25-1052PCTOPTIONAL, -NeedNaperiodic-ZP-CSI-RS-ResourceSetsToAddModList SEQUENCE (SIZE (1..maxNrofZP-CSI-RS- ResourceSets)) OF ZP-CSI-RS-ResourceSetOPTIONAL, - NeedNaperiodic-ZP-CSI-RS-ResourceSetsToReleaseList SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSetldOPTIONAL, - NeedNsp-ZP-CSI-RS-ResourceSetsToAddModList SEQUENCE (SIZE (1.. maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSetOPTIONAL, - NeedNsp-ZP-CSI-RS-ResourceSetsToReleaseList SEQUENCE (SIZE (1.. maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSetldOPTIONAL, - NeedNp-ZP-CSI-RS-ResourceSet SetupRelease { ZP-CSI-RS-ResourceSet }OPTIONAL, -NeedM[[maxMIMO-Layers-r16 SetupRelease { MaxMIMO-LayersDL-r16 } OPTIONAL, - Need MminimumSchedulingOffsetKO-r16 SetupRelease { MinSchedulingOffsetKO-Values-rl 6 } OPTIONAL, - Need M- Start of the parameters for DCI format 1_2 introduced in V16.1.0antennaPortsFieldPresenceDCI-1 -2-r16 ENUMERATED {enabled} OPTIONAL, - Need SaperiodicZP-CSI-RS-ResourceSetsToAddModListDCI-1-2-r16 SEQUENCE (SIZE (1,.maxNrofZP-CSI-RS- ResourceSets)) OF ZP-CSI-RS-ResourceSetOPTIONAL, - NeedN aperiodicZP-CSI-RS-ResourceSetsToReleaseListDCI-1-2-r16 SEQUENCE (SIZE (1..maxNrofZP-CSI-RS- ResourceSets)) OF ZP-CSI-RS-ResourceSetldOPTIONAL, - NeedNdmrs-DownlinkForPDSCH-MappingTypeA-DCI-1 -2-r16 SetupRelease { DMRS-DownlinkConfig } OPTIONAL, - Need MDocket No.: 25-1052PCTdmrs-DownlinkForPDSCH-MappingTypeB-DCI-1 -2-r16 SetupRelease { DMRS-DownlinkConfig } OPTIONAL, - Need Mdmrs-SequencelnitializationDCI-1 -2-r16 ENUMERATED {enabled} OPTIONAL, - Need Sharq-ProcessNumberSizeDCI-1-2-r16 INTEGER (0..4) OPTIONAL, - Need Rmcs-TableDCI-1-2-r16 ENUMERATED {qam256, qam64LowSE}OPTIONAL, - Need SnumberOfBitsForRV-DC 1-1 -2-r 16 INTEGER (0..2) OPTIONAL, - Need Rpdsch-TimeDomainAllocationListDCI-1 -2-r16 SetupRelease { PDSCH-TimeDomainResourceAllocationList- r16 }OPTIONAL, - Need Mprb-BundlingTypeDCI-1-2-r16 CHOICE {staticBundling-r16 SEQUENCE {bundleSize-r16 ENUMERATED { n4, wideband } OPTIONAL - Need SdynamicBundling-r16 SEQUENCE {bundleSizeSetl -r16 ENUMERATED { n4, wideband, n2-wideband, n4-wideband } OPTIONAL, - Need SbundleSizeSet2-r16 ENUMERATED { n4, wideband } OPTIONAL - Need SOPTIONAL, - Need Rpriori tylndicatorDCI-1-2-r16 ENUMERATED {enabled} OPTIONAL, - Need SrateMatchPatternGroupI DCI-1-2-r16 RateMatchPatternGroup OPTIONAL, - Need RrateMatchPatternGroup2DCI-1-2-r16 RateMatchPatternGroup OPTIONAL, - Need RresourceAllocationType1GranularityDCI-1-2-r16 ENUMERATED {n2,n4,n8,n16}OPTIONAL, - Need SDocket No.: 25-1052PCTvrb-ToPRB-lnterleaverDCI-1-2-r16 ENUMERATED {n2, n4} OPTIONAL, - NeedSreferenceOfSLIVDCI-1 -2-r16 ENUMERATED {enabled} OPTIONAL, - NeedSresourceAllocationDCI-1-2-r16 ENUMERATED { resourceAllocationTypeO, resourceAllocationTypel, dynamicSwitch}OPTIONAL, - NeedM-- End of the parameters for DCI format 1_2 introduced in V16.1.0prioritylndicatorDCI-1-1-r16 ENUMERATED {enabled} OPTIONAL, - NeedSdataScramblingldentityPDSCH2-r16 INTEGER (0..1023) OPTIONAL, - Need Rpdsch-TimeDomainAllocationList-r16 SetupRelease { PDSCH-TimeDomainResourceAllocationList-r16 } OPTIONAL, - Need MrepetitionSchemeConfig-r16 SetupRelease { RepetitionSchemeConfig-r16} OPTIONAL - Need M]],[[repetitionSchemeConfig-vl 630 SetupRelease { RepetitionSchemeConfig-v1630}OPTIONAL - Need M[[pdsch-HARQ-ACK-OneShotFeedbackDCI-1-2-r17 ENUMERATED {enabled}OPTIONAL, - Need Rpdsch-HARQ-ACK-EnhType3DCI-1 -2-r17 ENUMERATED {enabled}OPTIONAL, - Need Rpdsch-HARQ-ACK-EnhType3DCI-Field-1-2-r17 ENUMERATED {enabled}OPTIONAL, - Need Rpdsch-HARQ-ACK-RetxDCI-1-2-r17 ENUMERATED {enabled} OPTIONAL, - Need Rpucch-sSCellDynDCI-1-2-r17 ENUMERATED {enabled} OPTIONAL, - Need Rdl-OrJointTCI-StateList-r17 CHOICE {Docket No.: 25-1052PCTSEQUENCE {dl-OrJointTCI-StateToAddModList-r17 SEQUENCE (SIZE (1..maxNrofTCI-States)) OF TCI-State OPTIONAL, - Need Ndl-OrJointTCI-StateToReleaseList-r17 SEQUENCE (SIZE (1..maxNrofTC I -States)) OF TCI-Stateld OPTIONAL - Need NunifiedTCI-StateRef-r17 ServingCellAndBWP-ld-r17OPTIONAL, - Need R beamAppTime-r17 ENUMERATED {n1 , n2, n4, n7, n14, n28, n42, n56, n70, n84, n98, n112, n224, n336, spare2,sparel} OPTIONAL, - Need Rdummy SetupRelease { Dummy-TDRA-List } OPTIONAL, - Need Mdmrs-FD-OCC-DisabledForRank1-PDSCH-r17 ENUMERATED {true}OPTIONAL, - Need Rmi ni mu mScheduli ng OffsetKO-r17 SetupRelease { MinSchedulingOffsetKO-Values-r17 } OPTIONAL, - Need Mharq-ProcessNumberSizeDCI-1 -2-v1700 INTEGER (0..5) OPTIONAL, - Need Rharq-ProcessNumberSizeDCI-1 -1 -r17 INTEGER (5) OPTIONAL, - Need Rmcs-Table-r17 ENUMERATED {qam1024} OPTIONAL, - Need Rmcs-TableDCI-1-2-r17 ENUMERATED {qam1024} OPTIONAL, Need RxOverheadMulticast-r17 ENUMERATED {xOh6, xOh12, xOh18} OPTIONAL, - Need SprioritylndicatorDCI-4-2-r17 ENUMERATED {enabled} OPTIONAL, - Need SsizeDCI-4-2-r17 INTEGER (2O..maxDCI-4-2-Size-r17) OPTIONAL - Need RDocket No.: 25-1052PCTpdsch-TimeDomainAllocationl_istForMultiPDSCH-r17 SetupRelease { MultiPDSCH-TDRA-List-r17 } OPTIONAL - Need M]],[[advancedReceiver-MU-MIMO-r18 SetupRelease { AdvancedReceiver-MU-MIMO-r18 } OPTIONAL, - Need Mpdsch-ConfigDCI-1 -3-r18 SetupRelease { PDSCH-ConfigDCI-1 -3-r18 } OPTIONAL - Need M]]RateMatchPatternGroup SEQUENCE (SIZE (1,.maxNrofRateMatchPatternsPerGroup)) OF CHOICEcellLevel RateMatchPatternld,bwpLevel RateMatchPatternldMinSchedulingOffsetKO-Values-r16 ::= SEQUENCE (SIZE (1..maxNrOfMinSchedulingOffsetValues-r16)) OF I NTEGER (0.. max KO-Schedul I ngOffset-r16)MinSchedulingOffsetKO-Values-r17 ::= SEQUENCE (SIZE (1..maxNrOfMinSchedulingOffsetValues-r16)) OF I NTEGER (0.. maxKO-Schedul I ngOffset-r17)MaxMIMO-LayersDL-r16 ::= INTEGER (1..8)PDSCH-ConfigDCI-1 -3-r18 ::= SEQUENCE {resou rceAl location DC I -1 -3- r 18 ENUMERATED {resourceAllocationTypeO, resourceAllocationTypel, dynamicSwitch}OPTIONAL, - Need Mrbg-SizeDCI-1-3-r18 ENUMERATED {configl, configZ, config3, sparel} OPTIONAL, - Cond DCI-1-3resourceAllocationType1GranularityDCI-1-3-r18 ENUMERATED {n2,n4,n8,n16}OPTIONAL, - Need SDocket No.: 25-1052PCTnumberOfBitsForRV-DCI-1-3-r18 INTEGER (0..2) OPTIONAL, - Need Rharq-ProcessNumberSizeDCI-1-3-r18 INTEGER (0..5) OPTIONAL - Need R-TAG-PDSCH-CONFIG-STOP-ASN1STOFdl-OrJointTCI-StateToAddModListA list of Transmission Configuration Indicator (TCI) states indicating a transmission configuration which includes QCL-relationships between the DL RSs in one RS set and the PDSCH DMRS ports, PDCCH DMRS ports, and CSI-RS, and in case of join mode, also the PUSCH, PUCCH and SRS.dmrs-DownlinkForPDSCH-MappingTypeA, dmrs-DownlinkForPDSCH-IVIappingTypeA-DCI-1-2 DMRS configuration for PDSCH transmissions using PDSCH mapping type A (chosen dynamically via PDSCH- TimeDomainResourceAllocation). Only the fields dmrs-Type, dmrs-AdditionalPosition and maxLength may be set differently for mapping type A and B. The field dmrs-DownlinkForPDSCH-MappingTypeA applies to DCI formats 1 J and 1 _3, and the field dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2 applies to DCI format 1_2.dmrs-DownlinkForPDSCH-MappingTypeB, dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2 DMRS configuration for PDSCH transmissions using PDSCH mapping type B (chosen dynamically via PDSCH- TimeDomainResourceAllocation). Only the fields dmrs-Type, dmrs-AdditionalPosition and maxLength may be set differently for mapping type A and B. The field dmrs-DownlinkForPDSCH-MappingTypeB applies to DCI formats 1 J and 1 _3, and the field dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2 applies to DCI format 1_2.pdsch-AggregationFactorNumber of repetitions for data. When the field is absent in PDSCH-Config which is not used for MBS CFR, the UE applies the value 1.pdsch-HARQ-ACK-EnhType3DCI-1-2When configured, enhanced Type 3 HARQ-ACK codebook triggering by DCI format 1_2 is enabled.pdsch-HARQ-ACK-EnhType3DCI-Field-1-2Enables the enhanced Type 3 codebook through a new DCI field to indicate the enhanced Type 3 HARQ-ACK codebook in DCI format 1_2 if the more than one enhanced Type 3 HARQ-ACK codebook is configured for the primary PUCCH cell group.Docket No.: 25-1052PCTpdsch-HARQ-ACK-OneShotFeedbackDCI-1-2When configured, DCI format 1_2 can request the UE to report A / N for all HARQ processes and all component carriers configured in the PUCCH group.

[0276] The one or more configuration parameters (e.g., the one or more BWP configuration parameters, e.g., BWP-UplinkCommon and / or BWP-UplinkDedicated) may comprise one or more PUSCH configuration parameters (e.g., PUSCH-ConfigCommon and / or PUSCH-Config) for transmitting PUSCHs via a BWP (of the one or more BWPs) on a cell / carrier (of the one or more cells / a plurality of carriers). For example, the one or more configuration parameters may configure each BWP (of the one or more BWPs configured for the cell / carrier) of the cell / carrier with corresponding PUSCH-ConfigCommon and / or PUSCH-Config for transmitting PUSCHs via the BWP on the cell / carrier. Transmitting PUSCHs, by the wireless device and via a BWP (of the one or more BWPs) on a cell / carrier (of the one or more cells / a plurality of carriers), may be based on the one or more PUSCH configuration parameters (e.g., PUSCH-ConfigCommon and / or PUSCH-Config) corresponding to the BWP.

[0277] The one or more PUSCH configuration parameters may comprise one or more cell-specific PUSCH configuration parameters (of the cell / carrier) and / or one or more UE-specific PUSCH configuration parameters. The one or more PUSCH configuration parameters may configure / indicate at least one of the following: DM-RS configuration; and / or TCI configuration; and / or time domain resource allocation (pusch-TimeDomainAllocationList); and / or the like.

[0278] The following shows an example of the one or more PUSCH configuration parameters:Docket No.: 25-1052PCTPUSCH-ConfigThe IE PUSCH-Config is used to configure the UE specific PUSCH parameters applicable to a particular BWP.PUSCH-Config information element-ASN1 START-TAG-PUSCH-CONFIG-STARTPUSCH-Config ::= SEQUENCE {dataScramblingldentityPUSCH INTEGER (0..1023) OPTIONAL, - NeedStxConfig ENUMERATED {codebook, nonCodebook} OPTIONAL, - Needsdmrs-UplinkForPUSCH-MappingTypeA SetupRelease { DMRS-UplinkConfig }OPTIONAL, - Need Mdmrs-UplinkForPUSCH-MappingTypeB SetupRelease { DMRS-UplinkConfig }OPTIONAL, - Need Mpusch-PowerControl PUSCH-PowerControl OPTIONAL, - Need MfrequencyHopping ENUMERATED {intraSlot, interSlot} OPTIONAL, - NeedSfrequencyHoppingOffsetLists SEQUENCE (SIZE (1..4)) OF INTEGER (1.. maxNrofPhysicalResourceBlocks-1)OPTIONAL, - NeedM resourceAl location ENUMERATED { resourceAllocationTypeO, resourceAllocationTypel, dynamicSwitch},pusch-TimeDomainAllocationList SetupRelease { PU SC H-TimeDomain ResourceAllocationList } OPTIONAL, - Need Mpusch-AggregationFactor ENUMERATED { n2, n4, n8 } OPTIONAL, - NeedSmcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, - NeedSmcs-TableTransformPrecoder ENUMERATED {qam256, qam64LowSE}OPTIONAL, - NeedSDocket No.: 25-1052PCTtransformPrecoder ENUMERATED {enabled, disabled} OPTIONAL, - Need ScodebookSubset ENUMERATED {fullyAndPartialAndNonCoherent, partialAndNonCoherent, noncoherent}OPTIONAL, - Cond codebookBased max Rank INTEGER (1..4) OPTIONAL, - Cond codebookBasedrbg-Size ENUMERATED { config2} OPTIONAL, - Need S uci-OnPUSCH SetupRelease { UCI-OnPUSCH} OPTIONAL, - Need M tp-pi2BPSK ENUMERATED {enabled} OPTIONAL, - Need S[[mi ni mu mScheduli ng OffsetK2-r16 SetupRelease { MinSchedulingOffsetK2-Values-r16 } OPTIONAL, - Need Mul-AccessConfigListDCI-0-1 -r16 SetupRelease { UL-AccessConfigListDCI-0-1 -r16 } OPTIONAL, - Need M- Start of the parameters for DCI format 0_2 introduced in V16.1.0harq-ProcessNumberSizeDCI-0-2-r16 INTEGER (0..4) OPTIONAL, - Need Rdmrs-SequencelnitializationDCI-0-2-r16 ENUMERATED {enabled} OPTIONAL, - Need SnumberOfBitsForRV-DC l-0-2-r16 INTEGER (0..2) OPTIONAL, - Need R antennaPortsFieldPresenceDCI-0-2-r16 ENUMERATED {enabled} OPTIONAL, - Need Sdmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2-r16 SetupRelease { DMRS-UplinkConfig } OPTIONAL, - Need Mdmrs-UplinkForPUSCH-MappingTypeB-DCI-0-2-r16 SetupRelease { DMRS-UplinkConfig } OPTIONAL, - Need MfrequencyHoppingDCI-0-2-r16 CHOICE {pusch-RepTypeA ENUMERATED {intraSlot, interSlot},pusch-RepTypeB ENUMERATED {interRepetition, interSlot}OPTIONAL, - Need S frequencyHoppingOffsetListsDCI-0-2-r16 SetupRelease { FrequencyHoppingOffsetListsDCI-0-2-r16} OPTIONAL, - Need MDocket No.: 25-1052PCTcodebookSubsetDCI-0-2-r16 ENUMERATED {fullyAndPartialAndNonCoherent, partialAndNonCoherent, noncoherent}OPTIONAL, -- Cond codebookBased invalidSymbolPatternlndicatorDCI-0-2-r16 ENUMERATED {enabled} OPTIONAL, - NeedSmaxRankDCI-0-2-r16 INTEGER (1..4) OPTIONAL, -Cond codebookBasedmcs-TableDCI-0-2-r16 ENUMERATED {qam256, qam64LowSE} OPTIONAL, - - Need Smcs-TableT ransformPrecoderDCI-0-2-r16 ENUMERATED {qam256, qam64LowSE} OPTIONAL, - NeedSpriori tylndicatorDCI-0-2-r16 ENUMERATED {enabled} OPTIONAL, - Need Spusch-RepTypelndicatorDCI-0-2-r16 ENUMERATED { pusch-RepTypeA, pusch-RepTypeB} OPTIONAL, - Need Rresou rceAl location DC I -0-2- r16 ENUMERATED { resourceAllocationTypeO,resourceAl locationTypel , dynamicSwitch}OPTIONAL, - Need M resourceAllocationTypel GranularityDCI-0-2-r16 ENUMERATED { n2,n4,n8,n16 }OPTIONAL, - NeedSuci-OnPUSCH-ListDCI-0-2-r16 SetupRelease { UCI-OnPUSCH-ListDCI-0-2-r16} OPTIONAL, - Need Mpusch-TimeDomainAllocationListDCI-0-2-r16 SetupRelease { PUSCH- TimeDomainResourceAllocationList-r16 }OPTIONAL, - Need M- End of the parameters for DCI format 0_2 introduced in V16.1.0- Start of the parameters for DCI format 0_1 introduced in V16.1.0pusch-TimeDomainAllocationListDCI-0-1 -r16 SetupRelease { PUSCH- TimeDomainResourceAllocationList-r16 }OPTIONAL, - Need M invalidSymbolPatternlndicatorDCI-0-1-r16 ENUMERATED {enabled} OPTIONAL, - NeedSprioritylndicatorDCI-0-1-r16 ENUMERATED {enabled} OPTIONAL, - NeedDocket No.: 25-1052PCTpusch-RepTypelndicatorDCI-0-1 -r16 ENUMERATED { pusch-RepTypeA, pusch-RepTypeB} OPTIONAL, - Need Rfrequency Hopping DC I -0- 1 -r16 ENUMERATED {interRepetition, interSlot} OPTIONAL, - Cond RepTypeBuci-OnPUSCH-ListDCI-0-1-r16 SetupRelease { UCI-OnPUSCH-ListDCI-0-1-r16 } OPTIONAL, - Need M-- End of the parameters for DCI format 0_1 introduced in V16.1.0invalidSymbolPattern-r16 lnvalidSymbolPattern-r16 OPTIONAL, - NeedS pusch-PowerControl-v1610 SetupRelease {PUSCH-PowerControl-v1610} OPTIONAL, - Need Mul-FullPowerTransmission-r16 ENUMERATED {fullpower, fullpowerModel , fullpowerMode2} OPTIONAL, - Need Rpusch-TimeDomainAllocationListForMultiPUSCH-r16 SetupRelease { PUSCH- TimeDomainResourceAllocationList-r16 }OPTIONAL, - Need M numberOflnvalidSymbolsForDL-UL-Switching-r16 INTEGER (1..4) OPTIONAL - Cond RepTypeB2ul-AccessConfigListDCI-0-2-r17 SetupRelease { UL-AccessConfigListDCI-0-2-r17 } OPTIONAL, -- Need MbetaOffsetsCross PriO-r 17 SetupRelease { BetaOffsetsCrossPriSel-r17 } OPTIONAL, -- Need MbetaOffsetsCrossPri1-r17 SetupRelease { BetaOffsetsCrossPriSel-r17 } OPTIONAL, -- Need MbetaOffsetsCrossPriODCI-0-2-r17 SetupRelease { BetaOffsetsCrossPriSelDCI-0-2-r17 } OPTIONAL, - Need MbetaOffsetsCrossPri 1 DCI-0-2-r17 SetupRelease { BetaOffsetsCrossPriSelDCI-0-2-r17 } OPTIONAL, - Need MmappingPattern-r17 ENUMERATED {cyclicMapping, sequential Mapping} OPTIONAL, - Cond SRSsetssecondTPCFieldDCI-0-1 -r17 ENUMERATED {enabled} OPTIONAL, - Need RDocket No.: 25-1052PCTsecondTPCFieldDCI-0-2-r17 ENUMERATED {enabled} OPTIONAL, - Need RsequenceOffsetForRV-r17 INTEGER (0..3) OPTIONAL, - Need R ul-AccessConfigListDCI-0-1-r17 SetupRelease { UL-AccessConfigListDCI-0-1 -r17 } OPTIONAL, - Need Mmi ni mu mScheduli ng OffsetK 2-r17 SetupRelease { MinSchedulingOffsetK2-Values-r17 } OPTIONAL, - Need Maval lableSlotCounting-r17 ENUMERATED {enabled} OPTIONAL, - Need Sdmrs-BundlingPUSCH-Config-r17 SetupRelease { DMRS-BundlingPUSCH-Config-r17 } OPTIONAL, - Need Mharq-ProcessNumberSizeDCI-0-2-v1700 INTEGER (5) OPTIONAL, - Need Rharq-ProcessNumberSizeDC l-O- 1 -r17 INTEGER (5) OPTIONAL, - Need Rmpe-ResourcePoolToAddModList-r17 SEQUENCE (SIZE(1..maxMPE-Resources-r17)) OF MPE- Resource-r17 OPTIONAL, - Need Nmpe-ResourcePoolToReleaseList-r17 SEQUENCE (SIZE(1..maxMPE-Resources-r17)) OF MPE- Resourceld-r17 OPTIONAL - Need NmaxRank-v1810 INTEGER (5.,8) OPTIONAL, - Need R sTx-2Panel-r18 ENUMERATED {enabled} OPTIONAL, - Need R multipanelSchemeSDM-r18 SDM-Scheme-r18 OPTIONAL, - Need R multipanelSchemeSFN-r18 SFN-Scheme-r18 OPTIONAL, - Need R codebookTypeUL-r18 SetupRelease { CodebookTypeUL-r18 } OPTIONAL, - Need Mapplyl ndicatedT C l-State-r18 ENUMERATED {first, second} OPTIONAL, - Need RdynamicTransformPrecoderFieldPresenceDCI-0-1-r18 ENUMERATED {enabled}OPTIONAL, - Need RdynamicTransformPrecoderFieldPresenceDCI-0-2-r18 ENUMERATED {enabled}OPTIONAL, - Need RDocket No.: 25-1052PCTpusch-ConfigDCI-0-3-r18 SetupRelease { PUSCH-ConfigDCI-0-3-r18 } OPTIONAL - Need MUCI-OnPUSCH ::= SEQUENCE {betaOffsets CHOICE {dynamic SEQUENCE (SIZE (4)) OF BetaOffsets,semiStatic Beta OffsetsOPTIONAL, - Need Mscaling ENUMERATED { f0p5, f0p65, f0p8, f1 }MinSchedulingOffsetK2-Values-r16 ::= SEQUENCE (SIZE (1 ,.maxNrOfMinSchedulingOffsetValues-r16)) OF INTEGER (0..maxK2-SchedulingOffset-r16)MinSchedulingOffsetK2-Values-r17 ::= SEQUENCE (SIZE (1..maxNrOfMinSchedulingOffsetValues-r16)) OF INTEGER (0..maxK2-SchedulingOffset-r17)UCI-OnPUSCH-DCI-0-2-r16 ::= SEQUENCE {betaOffsetsDCI-0-2-r16 CHOICE {dynamicDCI-0-2-r16 CHOICE {oneBit-r16 SEQUENCE (SIZE (2)) OF BetaOffsets,twoBits-r16 SEQUENCE (SIZE (4)) OF BetaOffsetssemiStaticDCI-0-2-r16 BetaOffsetsOPTIONAL, -NeedMscalingDCI-0-2-r16 ENUMERATED { f0p5, f0p65, f0p8, f1 }FrequencyHoppingOffsetListsDCI-0-2-r16 ::= SEQUENCE (SIZE (1..4)) OF INTEGER (1.. maxNrofPhysicalResourceBlocks-1)UCI-OnPUSCH-ListDCI-0-2-r16 ::= SEQUENCE (SIZE (1..2)) OF UCI-OnPUSCH-DCI-0-2-r16Docket No.: 25-1052PCTUCI-OnPUSCH-ListDCI-0-1-r16 ::= SEQUENCE (SIZE (1..2)) OF UCI-OnPUSCHUL-AccessConfigListDC 1-0-1 -r16 ::= SEQUENCE (SIZE (1..64)) OF INTEGER (0..63)UL-AccessConfigListDC 1-0-1 -r17 ::= SEQUENCE (SIZE (1..3)) OF INTEGER (0..2)UL-AccessConfigListDC I-0-2-M 7 ::= SEQUENCE (SIZE (1..64)) OF INTEGER (0..63) BetaOffsetsCrossPriSel-r17 ::= CHOICE {dynamic-r17 SEQUENCE (SIZE (4)) OF BetaOffsetsCrossPri-r17,se mi Static-r 17 BetaOffsetsC ross Pri -r 17BetaOffsetsCrossPriSelDCI-0-2-r17 ::= CHOICE {dynamicDCI-0-2-r17 CHOICE {oneBit-r17 SEQUENCE (SIZE (2)) OF BetaOffsetsCrossPri-r17,twoBits-r17 SEQUENCE (SIZE (4)) OF BetaOffsetsCrossPri-r17semiStaticDC l-0-2-r17 BetaOffsetsC ross Pri -r 17MPE-Resource-r17 ::= SEQUENCE {mpe-Resourceld-r17 MPE-Resourceld-r17,cell-r17 ServCelllndex OPTIONAL, - Need R additionalPCI-r17 AdditionalPCIIndex-r17 OPTIONAL, - Need R mpe-ReferenceSignal-r17 CHOICE {csi-RS-Resource-r17 NZP-C SI- RS-Resourcel d ,ssb-Resource-r17 SSB-lndexMPE-Resourceld-r17 ::= INTEGER (1,.maxMPE-Resources-r17)Docket No.: 25-1052PCTSDM-Scheme-r18 ::= SEQUENCE {maxRankSDM-r18 INTEGER (1..2) OPTIONAL, -NeedR maxRankSDM-DCI-0-2-r18 INTEGER (1..2) OPTIONAL -NeedRSFN-Scheme-r18 ::= SEQUENCE!maxRankSFN-r18 INTEGER (1..2) OPTIONAL, -Need R maxRankSFN-DCI-0-2-r18 INTEGER (1..2) OPTIONAL - Need RCodebookTypeUL-r18 ::= CHOICE {codebookl -r18 ENUMERATED {ng1n4n1, ng1n2n2},codebook2-r18 ENUMERATED {ng2},codebook3-r18 ENUMERATED {ng4},codebook4-r18 ENUMERATED {ng8}PUSCH-ConfigDCI-0-3-r18 ::= SEQUENCE {resourceAllocationDCI-0-3-r18 ENUMERATED {resourceAllocationTypeO, resourceAllocationTypel, dynamicSwitch}OPTIONAL, - NeedMrbg-SizeDCI-0-3-r18 ENUMERATED {config2, config3} OPTIONAL, - NeedSresourceAllocationTypel GranularityDCI-0-3-r18 ENUMERATED {n2,n4,n8,n16}OPTIONAL, - NeedSnumberOfBitsForRV-DCI-0-3-r18 INTEGER (0.2) OPTIONAL, - Need Rharq-ProcessNumberSizeDCI-0-3-r18 INTEGER (0..5) OPTIONAL, - Need Ruci-OnPUSCH-ListDCI-0-3-r18 SetupRelease { UC l-OnPUSCH-ListDCI-O-1 -r16 } OPTIONAL - NeedMDocket No.: 25-1052PCT- TAG-PUSCH-CONFIG-STOP-ASN1STOPPUSCH-Config field descriptionsavailableSlotCountingIndicate whether PUSCH repetitions counted on the basis of available slots is enabled. If the field is absent, PUSCH repetitions counted on the basis of available slots is disabled.dmrs-BundlingPUSCH-ConfigConfigure the parameters for DMRS bundling for PUSCH. In this release, this is not applicable to FR2-2.dmrs-UplinkForPUSCH-MappingTypeA, dmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2DMRS configuration for PUSCH transmissions using PUSCH mapping type A (chosen dynamically via PUSCH- TimeDomainResourceAllocation). Only the fields dmrs-Type, dmrs-AdditionalPosition and maxLength may be set differently for mapping type A and B. The field dmrs-UplinkForPUSCH-MappingTypeA applies to DCI formats 0_1 and 0_3, and the field dmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2 applies to DCI format 0_2.dmrs-UplinkForPUSCH-MappingTypeB, dmrs-UplinkForPUSCH-MappingTypeB-DCI-0-2DMRS configuration for PUSCH transmissions using PUSCH mapping type B (chosen dynamically via PUSCH- TimeDomainResourceAllocation). Only the fields dmrs-Type, dmrs-AdditionalPosition and maxLength may be set differently for mapping type A and B. The field dmrs-UplinkForPUSCH-MappingTypeB applies to DCI formats 0_1 and 0_3, and the field dmrs-UplinkForPUSCH-MappingTypeB-DCI-0-2 applies to DCI format 0_2.pusch-TimeDomainAllocationListList of time domain allocations for timing of UL assignment to UL data. The field pusch-TimeDomainAllocationList applies to DCI format 0_0, or DCI formats 0_1 and 0_3 when the field pusch-TimeDomainAllocationListDCI-0-1 is not configured. The network does not configure the pusch-TimeDomainAllocationList (without suffix) simultaneously with the pusch-TimeDomainAllocationListDCI-0-2-r16 or pusch-TimeDomainAllocationListDCI-O- 1-r16 or pusch-TimeDomainAllocationListForMultiPUSCH-r16.pusch-TimeDomainAllocationListForMultiPUSCHConfiguration of the time domain resource allocation (TDRA) table for multiple PUSCH. The network configures at most 64 rows in this TDRA table in PUSCH-TimeDomainResourceAllocationList-r16 configured by this field. This field is not configured simultaneously with pusch-AggregationFactor. The network does not configure the pusch-TimeDomainAllocationListForMultiPUSCH-r16 simultaneously with the pusch- TimeDomainAllocationListDCI-0-1-r16. The network does not configure the pusch- TimeDomainAllocationListForMultiPUSCH-r16 simultaneously with the numberOfSlotsTBoMS-r17.Docket No.: 25-1052PCTresourceAllocation, resourceAllocationDCI-0-2Configuration of resource allocation type 0 and resource allocation type 1 for non-fallback DCI. The field resourceAllocation applies to DCI format 0_1 and the field resourceAllocationDCI-0-2 applies to DCI format 0_2. resourceAllocationType1GranularityDCI-0-2Configures the scheduling granularity applicable for both the starting point and length indication for resource allocation type 1 in DCI format 0_2. If this field is absent, the granularity is 1 PRB.

[0279] The one or more configuration parameters (e.g., the one or more BWP configuration parameters, e.g., BWP-UplinkCommon and / or B WP-UplinkDedicated) may comprise one or more PUCCH configuration parameters (e.g., PUCCH-ConfigCommon and / or PUCCH-Config) for transmitting PUCCHs via a BWP (of the one or more BWPs) on a cell / carrier (of the one or more cells / a plurality of carriers). For example, the one or more configuration parameters may configure each BWP (of the one or more BWPs configured for the cell / carrier) of the cell / carrier with corresponding PUCCH-ConfigCommon and / or PUCCH-Config for transmitting PUCCHs via the BWP on the cell / carrier. Transmitting PUCCHs, by the wireless device and via a BWP (of the one or more BWPs) on a cell / carrier (of the one or more cells / a plurality of carriers), may be based on the one or more PUCCH configuration parameters (e.g., PUCCH-ConfigCommon and / or PUCCH-Config) corresponding to the BWP. The one or more PUCCH configuration parameters may comprise one or more cell-specific PUCCH configuration parameters (of the cell / carrier) and / or one or more UE-specific PUCCH configuration parameters. The one or more PUCCH configuration parameters may configure / indicate a plurality of PUCCH resources for transmitting PUCCHs.

[0280] The following shows an example of the one or more PUCCH configuration parameters:Docket No.: 25-1052PCTPUCCH-ConfigThe IE PUCCH-Config is used to configure UE specific PUCCH parameters (per BWP).PUCCH-Config information element-ASN1 START-TAG-PUCCH-CONFIG-STARTPUCCH-Config ::= SEQUENCE!resourceSetToAddModList SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceSets)) OF PUCCH- ResourceSet OPTIONAL, -- Need NresourceSetToReleaseList SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceSets)) OF PUCCH- ResourceSetld OPTIONAL, -- Need NresourceToAddModList SEQUENCE (SIZE (L.maxNrofPUCCH-Resources)) OF PUCCH- Resource OPTIONAL, - Need NresourceToReleaseList SEQUENCE (SIZE (1..maxNrofPUCCH-Resources)J OF PUCCH- Resourceld OPTIONAL, -- Need Nformatl SetupRelease { PUCCH-FormatConfig } OPTIONAL, - Need Mformat2 SetupRelease { PUCCH-FormatConfig } OPTIONAL, - Need Mformats SetupRelease { PUCCH-FormatConfig } OPTIONAL, - Need Mformat4 SetupRelease { PUCCH-FormatConfig } OPTIONAL, - Need MschedulingRequestResourceToAddModList SEQUENCE (SIZE (t.maxNrofSR-Resources)) OF SchedulingRequestResourceConfigOPTIONAL, - Need N schedulingRequestResourceToReleaseList SEQUENCE (SIZE (1,.maxNrofSR-Resources)) OF SchedulingRequestResourceldOPTIONAL, - Need Nmulti-CSI-PUCCH-ResourceList SEQUENCE (SIZE (1..2)) OF PUCCH-Resourceld OPTIONAL, - Need Mdl-DataToUL-ACK SEQUENCE (SIZE (1..8)) OF INTEGER (0..15)OPTIONAL, - Need MDocket No.: 25-1052PCTspatialRelationlnfoToAddModList SEQUENCE (SIZE (1. maxNrofSpatialRelationlnfos)) OF PUCCH- SpatialRelationlnfoOPTIONAL, - Need N spatialRelationlnfoToReleaseList SEQUENCE (SIZE (1.. maxNrofSpatialRelationlnfos)) OF PUCCH- SpatialRelationlnfoldOPTIONAL, - Need Npucch-PowerControl PUCCH-PowerControl OPTIONAL, -- Need M[[resourceToAddModListExt-v1610 SEQUENCE (SIZE (1..maxNrofPUCCH-Resources)) OF PUCCH- ResourceExt-v1610 OPTIONAL, -- Need Ndl-DataToUL-ACK-r16 SetupRelease { DL-DataToUL-ACK-r16 } OPTIONAL, - Need Mul-AccessConfigListDCI-1-1 -r16 SetupRelease { UL-AccessConfigListDCI-1 -1 -r16 }OPTIONAL, - Need MsubslotLengthForPUCCH-r16 CHOICE {normalCP-r16 ENUMERATED {n2,n7},extendedCP-r16 ENUMERATED {n2,n6}OPTIONAL, - Need Rdl-DataToUL-ACK-DCI-1-2-r16 SetupRelease { DL-DataToUL-ACK-DCI-1-2-r16}OPTIONAL, - Need MnumberOfBitsForPUCCH-ResourcelndicatorDCI-1-2-r16 INTEGER (0..3)OPTIONAL, - Need Rdmrs-UplinkTransformPrecodingPUCCH-r16 ENUMERATED {enabled}OPTIONAL, - Cond PI2-BPSKspatial Relationl nfoToAddModListSizeExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatial RelationlnfosDiff- r16)) OF PUCCH-SpatialRelationlnfoOPTIONAL, - Need N spatialRelationlnfoToReleaseListSizeExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatialRelationlnfosDiff-r16)) OF PUCCH-SpatialRelationlnfoldOPTIONAL, - Need N spatialRelationlnfoToAddModListExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatialRelationlnfos-r16)) OF PUCCH-SpatialRelationlnfoExt-r16Docket No.: 25-1052PCTOPTIONAL, - Need Nspatial Relationl nfoToReleaseListExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatial Relationl nfos-r16)) OF PUCC H-SpatialRelationlnfold-r16 OPTIONAL, - Need N resourceGroupToAddModList-r16 SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceGroups-r16)) OF PUCCH-ResourceGroup-r16OPTIONAL, - Need N resourceGroupToReleaseList-r16 SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceGroups-r16)) OF PUCCH-ResourceGroupld-r16OPTIONAL, - Need Nsps-PUCCH-AN-List-r16 SetupRelease { SPS-PUCCH-AN-List-r16 }OPTIONAL, - Need MschedulingRequestResourceToAddModListExt-v1610 SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceConfigExt-v1610OPTIONAL- Need N]].[[format0-r17 SetupRelease { PUCCH-FormatConfig } OPTIONAL, - Need Mformat2Ext-r17 SetupRelease { PUCCH-FormatConfigExt-r17 } OPTIONAL, - Need Mformat3Ext-r17 SetupRelease { PUCCH-FormatConfigExt-r17 } OPTIONAL, - Need Mformat4Ext-r17 SetupRelease { PUCCH-FormatConfigExt-r17 } OPTIONAL, - Need Mul-AccessConfigListDCI-1 -2-r17 SetupRelease { UL-AccessConfigListDCI-1 -2-r17 } OPTIONAL, - Need MmappingPattern-r17 ENUMERATED {cyclicMapping, sequential Mapping}OPTIONAL, - Need RpowerControlSetlnfoToAddModList-r17 SEQUENCE (SIZE (1..maxNrofPowerControlSetlnfos-r17)) OF PUCCH-PowerControlSetlnfo-r17OPTIONAL, - Need N powerControlSetlnfoToReleaseList-r17 SEQUENCE (SIZE (1 ,.maxNrofPowerControlSetlnfos-r17)) OF PUCCH-PowerControlSetlnfold-r17OPTIONAL, - Need NDocket No.: 25-1052PCTsecondTPCFieldDCI-1 -1-r17 ENUMERATED {enabled} OPTIONAL, - Need RsecondTPCFieldDCI-1 -2-r17 ENUMERATED {enabled} OPTIONAL, - Need Rdl-DataToUL-ACK-r17 SetupRelease { DL-DataToUL-ACK-r17 } OPTIONAL, - Need Mdl-DataToUL-ACK-DCI-1 -2-r17 SetupRelease { DL-DataToUL-ACK-DCIOPTIONAL, - Need Mul-AccessConfigListDCI-1-1-r17 SetupRelease { UL-AccessConfigListDCIOPTIONAL, - Need MschedulingRequestResourceToAddModListExt-v1700 SEQUENCE (SIZE (1,.maxNrofSR-Resources)) OF SchedulingRequestResourceConfigExt-v1700OPTIONAL, - Need Ndmrs-BundlingPUCCH-Config-r17 SetupRelease { DMRS-BundlingPUCCH-Config-r17 } OPTIONAL, - Need Mdl-DataToUL-AC K-v1700 SetupRelease { DL-DataToUL-ACK-v1700 }OPTIONAL, - Need Mdl-DataToUL-ACK-MulticastDCI-Format4-1-r17 SetupRelease { DL-DataToUL-ACK-MulticastDCI-Format4-1- r17 } OPTIONAL, - Need Msps-PUCCH-AN-ListMulticast-r17 SetupRelease { SPS-PUCCH-AN-List-r16 }OPTIONAL - Need MPUCCH-FormatConfig ::= SEQUENCE {InterslotFrequencyHopping ENUMERATED {enabled} OPTIONAL, - Need RadditionalDMRS ENUMERATED {true} OPTIONAL, - Need R maxCodeRate PUCCH-MaxCodeRate OPTIONAL, - Need RnrofSIots ENUMERATED {n2,n4,n8} OPTIONAL, - Need S pi2BPSK ENUMERATED {enabled} OPTIONAL, - Need R simultaneousHARQ-AC K-CSI ENUMERATED {true} OPTIONAL - Need RDocket No.: 25-1052PCTPUCCH-FormatConfigExt-r17 SEQUENCE {maxCodeRateLP-r17 PUCCH-MaxCodeRate OPTIONAL, - Need RPUCCH-MaxCodeRate ::= ENUMERATED {zeroDot08, zeroDotl 5, zeroDot25, zeroDot35, zeroDot45, zeroDot60, zeroDot80}- A set with one or more PUCCH resourcesPUCCH-ResourceSet::= SEQUENCE {pucch-ResourceSetld PUCCH-ResourceSetld,resourceList SEQUENCE (SIZE (1„maxNrofPUCCH-ResourcesPerSet)) OF PUCCH- Resourceld,maxPayloadSize INTEGER (4..256) OPTIONAL - NeedRPUCCH-ResourceSetld ::= INTEGER (0..maxNrofPUCCH-ResourceSets-1)PUCCH-Resource ::= SEQUENCE {pucch-Resourceld PUCCH-Resourceld,startingPRB PRB-ld,IntraSlotFrequencyHopping ENUMERATED { enabled } OPTIONAL, - Need RsecondHopPRB PRB-ld OPTIONAL, - Need R format CHOICE {formatO PUCCH-formatO,formatl PUCCH-formatl,format? PUCCH-format2,formats PUCCH-format3,format4 PUCCH-format4Docket No.: 25-1052PCTPUCCH-ResourceExt-v1610 SEQUENCE {interlaceAllocation-r16 SEQUENCE}rb-Setlndex-r16 INTEGER (0..4),interlace0-r16 CHOICE {scs15 INTEGER (0..9),scs30 INTEGER (0..4)OPTIONAL, -NeedRformat-v1610 CHOICE {interlace1-v1610 INTEGER (0..9),occ-v1610 SEQUENCE {occ-Length-v1610 ENUMERATED {n2,n4} OPTIONAL, - Need Mocc-lndex-v1610 ENUMERATED {n0,n1,n2,n3} OPTIONAL - Need MOPTIONAL, - Need R[[format-v1700 SEQUENCE }nrofPRBs-r17 INTEGER (1..16)OPTIONAL, - Need Rpucch-RepetitionNrofSlots-r17 ENUMERATED { n1,n2,n4,n8 } OPTIONAL - - Need R11,11applyl ndicatedT C l-State-r18 ENUMERATED {first, second, both, sparel }OPTIONAL, - Need RmultipanelSFN-Scheme-r18 ENUMERATED {enabled} OPTIONAL, - Need Rdl-DataToUL-ACK-r18 SetupRelease { DL-DataToUL-ACK-r18 } OPTIONAL, -- Need MDocket No.: 25-1052PCTdl-DataTolIL-AC K-DCI-1 -2-r18 SetupRelease { DL-DataToUL-ACK-DCI-1-2-r18} OPTIONAL -NeedM]]PUCCH-Resourceld ::= INTEGER (0..maxNrofPUCCH-Resources-1)PUCCH-formatO ::= SEQUENCE {InitialCyclicShift INTEGER(0..11),nrofSymbols INTEGER (1..2),starting Symbol I ndex I N TE G E R(0..13)PUCCH-formatl ::= SEQUENCE!InitialCyclicShift INTEGER(0..11),nrofSymbols INTEGER (4..14),starting Symbol I ndex I N TE G ER(0..10 ) ,timeDomainOCC INTEGER(0..6)PUCCH-format2 ::= SEQUENCE!nrofPRBs INTEGER (1..16),nrofSymbols INTEGER (1..2),starting Symbol I ndex I N TE G ER(0..13)PUCCH-format3 ::= SEQUENCE!nrofPRBs INTEGER (1..16),nrofSymbols INTEGER (4..14),starting Symbol I ndex I N TE G ER(0..10 )PUCCH-format4 ::= SEQUENCE!Docket No.: 25-1052PCTnrofSymbols INTEGER (4..14),occ-Length ENUMERATED {n2,n4},occ-lndex ENUMERATED {n0,n1,n2,n3},startingSymbollndex INTEGER(O..1O)PUCCH-ResourceGroup-r16 ::= SEQUENCE {pucch-ResourceGroupld-r16 PUCCH-ResourceGroupld-r16,resourcePerGroupList-r16 SEQUENCE (SIZE (1..maxNrofPUCCH-ResourcesPerGroup-r16)) OF PUCCH-ResourceldPUCCH-ResourceGroupld-r16 ::= INTEGER (0..maxNrofPUCCH-ResourceGroups-1-r16)DL-DataToUL-ACK-r16 ::= SEQUENCE (SIZE (1..8)) OF INTEGER (-1..15)DL-DataTollL-ACK-r17 ::= SEQUENCE (SIZE (1..8)) OF INTEGER (-1..127)DL-DataToUL-ACK-v1700 ::= SEQUENCE (SIZE (1..8)) OF INTEGER (16..31)DL-DataTollL-ACK-r18 ::= SEQUENCE (SIZE (1..8)) OF INTEGER (0..31)DL-DataToUL-AC K-DCI- 1 -2-r16 ::= SEQUENCE (SIZE (1..8)) OF INTEGER (0..15)DL-DataToUL-ACK-DCI-1-2-r17 SEQUENCE (SIZE (1..8)) OF INTEGER (0..127)DL-DataToUL-ACK-DCI-1-2-r18 SEQUENCE (SIZE (1..8)) OF INTEGER (0..31)UL-AccessConfigListDCI-1 -1-r16 SEQUENCE (SIZE (1..16)) OF INTEGER (0..15)U L-AccessConfigListDC I - 1 -2-r 17 SEQUENCE (SIZE (1..16)) OF INTEGER (0..15)UL-AccessConfigListDCI-1 -1-r17 SEQUENCE (SIZE (1..3)) OF INTEGER (0..2)Docket No.: 25-1052PCTDL-DataToUL-ACK-MulticastDCI-Format4-1 -r17 ::= SEQUENCE (SIZE (1..8)) OF INTEGER (0..15)-TAG-PUCCH-CONFIG-STOP-ASN1STOPdl-DataToUL-ACK,dl-DataToUL-ACK-DCI-1-2List of timing for given PDSCH to the DL ACK. The field dl-DataTbUL-ACK applies to DCI format 1 J and the field dl-DataToUL-ACK-DCI-1-2 applies to DCI format 1_2. The dl-DataToUL-ACK-v1700 is applicable for NTN and dl-DataToUL-ACK-r17'\s applicable for FR2-2. The dl-DataToUL-ACK-r18 is applicable for ATG. If dl- DataToUL-ACK-r16 or dl-DataToUL-ACK-r17 or dl-DataToUL-ACK-v1700 or dl-DataToUL-ACK-r18 is signalled, UE shall ignore the d!-DataToUL-ACK (without suffix). The value -1 corresponds to "inapplicable value" for the case where the A / N feedback timing is not explicitly included at the time of scheduling PDSCH. The fields dl- DataToUL-ACK-r17 and dl-DataToUL-ACK-DCI-1-2-r17 are only applicable for SCS of 480 kHz or 960 kHz. The field dl-DataToUL-ACK-r18 applies to DCI format 1 J and the field dl-DataToUL-ACK-DCI-1-2-r18 applies to DCI format 1_2.dl-DataToUL-ACK-MulticastDCI-Format4-1List of timing for given group-common PDSCH to the DL ACK. The field dl-DataToUL-ACK-MulticastDciFormat4- 1 applies to DCI format 4_1 for MBS multicast.sps-PUCCH-AN-ListIndicates a list of PUCCH resources for DL SPS HARQ ACK. The field maxPayloadSize is absent for the first and the last SPS-PUCCH-AN in the list. If configured, this overrides n1PUCCH-AN in SPS-config.sps-PUCCH-AN-ListMulticastThe field is used to configure the list of PUCCH resources per HARQ ACK codebook for MBS multicast.simultaneousHARQ-ACK-CSIIf the field is present, the UE uses simultaneous transmission of CSI and HARQ-ACK feedback with or without SR with PUCCH Format 2, 3 or 4. When the field is absent the UE applies the value off. The field is not applicable for format 0 and 1.pucch-ResourceldIdentifier of the PUCCH resource.resourceListPUCCH resources of formatO and format! are only allowed in the first PUCCH resource set, i.e., in a PUCCH- ResourceSet with pucch-ResourceSetld = 0. This set may contain between 1 and 32 resources. PUCCH resources of format2, formats and format4 are only allowed in a PUCCH-ResourceSet with pucch-ResourceSetld > 0. If present, these sets contain between 1 and 8 resources each. The UE chooses a PUCCH-Resource fromDocket No.: 25-1052PCTthis list. Note that this list contains only a list of resource IDs. The actual resources are configured in PUCCH- Config.

[0281] For example, the wireless device may transmit (to the base station) one or more capability ( UE-capabi lity) messages. The one or more capability messages may comprise / indicate a first set of capabilities. The first set of capabilities may comprise at least one UE capability for operations in the one or more cells and / or via the plurality of CCs.

[0282] FIG. 17A, FIG. 17B, FIG. 17C and FIG. 17D show examples of uplink / downlink receptions / transmissions. FIG.17A and / or FIG. 17B may show examples of a PDSCH processing procedure for receiving DL channels (e.g., PDSCH). In the present disclosure, the PDSCH processing procedure may also be referred to by a PDSCH reception procedure or DL reception procedure or a DL processing procedure or a PDSCH preparation procedure.

[0283] In the present disclosure, receiving the PDSCH may be referred to by “processing the PDSCH” or “decoding the PDSCH”. For example, receiving the PDSCH may comprise processing and / or decoding a data / transport block (TB) provided by / carried by the PDSCH.

[0284] As shown in FIG. 17Aand FIG. 17B, the base station may transmit the DCI (in a PDCCH with the SCS PDCCH) t° toe wireless device indicating / scheduling / triggering at least one PDSCH (reception). The DCI may be the scheduling DCI. The DCI may be a first DL command (or equivalently a first DL message or a first DL signal). The DCI may be a first control channel. The wireless device may receive the scheduling DCI via the serving cell (e.g., CC 1 of the plurality of carriers / cell 1 of the one or more cells).

[0285] The scheduling DCI may indicate a HARQ-ACK timing K1 (e.g., via a field PDSCH-to-HARQ_feedback timing indicator of the scheduling DCI). The wireless device may, based on the HARQ-ACK timing K1 and a PUCCH resource of the plurality of PUCCH resources indicated / configured by the one or more PUCCH configuration parameters, determine a PUCCH (transmission occasion) for transmitting a HARQ-ACK information corresponding to / associated with the PDSCH. Determining the PUCCH transmission occasion may further be based on a timing advance (TA), e.g., an effect of the TA for advancing / delaying an UL frame with respect to the DL frame. The PUCCH transmission may comprise the HARQ-ACK information (i.e., a valid HARQ-ACK message comprising the HARQ-ACK information) of / corresponding to the PDSCH. The PUCCH transmission occasion my comprise symbols configured / indicated for the PUCCH resource.

[0286] As shown in FIG. 17A, the transmission of the PUCCH (e.g., with numerology / CC fiUL) is via the serving cell (e.g., the cell 1 of the one or more cells or the CC1 of the one or more CCs). The PUCCH transmission occasion may correspond to / with respect to (e.g., from a timing perspective) an UL frame / configuration of the wireless device corresponding to the cell 1 / carrier 1.Docket No.: 25-1052PCT

[0287] As shown in FIG 17B, the transmission of the PUCCH is via a second serving cell (e.g., a cell 2 of the one or more cells or a CC2 of the one or more CCs). The PUCCH transmission occasion may correspond to / with respect to (e.g., from a timing perspective) an UL frame / configuration of the wireless device corresponding to the cell 2 / carrier 2.

[0288] Corresponding to FIG. 17A and / or FIG. 17B, the PDSCH processing procedure may further comprise determining (by the wireless device and / or the base station) whether a first processing condition is satisfied or not.

[0289] The first processing condition may be satisfied (or met) based on the fi rst / initial / starting / earl iest (uplink) symbol of the PUCCH starting no earlier than at symbol L1. The symbol L1 may be a next (uplink) symbol (with its CP) starting after a second timing gap (e.g., Tproc1) after a last / final / ending / latest symbol of the PDSCH reception (carrying the TB). The first processing condition may be satisfied (or met) based on the first / initial / starting / earliest (uplink) symbol of the PUCCH starting after the symbol L1. The first processing condition may be satisfied (or met) based on a timing difference between the first / initial / starting / earliest (uplink) symbol of the PUCCH (comprising the HARQ-ACK information of / corresponding to the PDSCH) and the last / final / ending / latest symbol of the PDSCH reception being larger / greater / longer than or equal to the second timing gap. The first processing condition may not be satisfied (or met) based on the timing difference between the first / initial / starting / earliest (uplink) symbol of the PUCCH (comprising the HARQ-ACK information of / corresponding to the PDSCH) and the last / final / ending / latest symbol of the PDSCH reception being smaller / shorter / lower than the second timing gap.

[0290] As shown in FIG. 17A and FIG. 17B, the first uplink symbol of the PUCCH is after (or not start earlier than) the second timing gap (eg., Tprocafter the last / final / ending / latest symbol of the PDSCH reception associated with the HARQ-ACK information. Based on the first processing condition being satisfied, the wireless device may (via the cell 1 / Carrier 1 in FIG. 17A or the Cell 2 / Carrier 2 in FIG. 17B) transmit the PUCCH carrying the (valid) HARQ-ACK information (message) corresponding to the PDSCH reception. The HARQ-ACK information may comprise a positive acknowledgement (e.g., correct decoding of the TB indicated / provided by the PDSCH) or a negative acknowledgement (e.g., incorrect decoding of the TB indicated / provided by the PDSCH).

[0291] Based on the first processing condition being satisfied, the wireless device may provide the valid HARQ-ACK information (message) corresponding to the PDSCH reception.

[0292] Alternatively, the first processing condition may not be satisfied (or not met) based on the first / initial / starti ng / earliest (uplink) symbol of the PUCCH starting earlier than at symbol L1. The first processing condition may not be satisfied based on the first / i nitial / starting / earl iest (uplink) symbol of the PUCCH starting before the symbol L1. The first processing condition may not be satisfied (or met) based a first / i nitial / starti ng / earliest (uplink) symbol of the PUCCH (e.g., the PUCCH transmission occasion) starting earlier than the second timing gap (e.g., Tproc1) later than a last / final / ending / latest symbol of the PDSCH reception. The first processing condition maybe not satisfied (or met) based on the fi rst / i nitial / starting / earliest (uplink) symbol of the PUCCH being during / within the second timing gap after the last / final / ending / latest symbol of the PDSCH reception.Docket No.: 25-1052PCT

[0293] Based on the first processing condition not being satisfied, the wireless device may avoid / refrain transmitting the PUCCH carrying the (valid) HARQ-ACK information (message) corresponding to the PDSCH reception. Based on the first processing condition not being satisfied, the wireless device may avoid / refrain providing the vali HARQ-ACK information (message) corresponding to the PDSCH reception.

[0294] The PDSCH processing procedure may comprise determining the second timing gap. For example, according to / for the PDSCH processing procedure, the wireless device may determine the second timing gap as Tproc= ( + d- + d2+ d3)(2048 + 144) •• Tc+ Text. The wireless device may determine (value of) parameter N1 (for determining the second timing gap Tpr0Ci1) based on / with accordance to a UE processing capability. The UE processing capability may be a UE processing 2 (e.g., a UE processing capability 2, e.g., advanced or aggressive PDSCH capability) and / or a UE capability 1 (e.g., a UE processing capability 1, e.g., baseline / default PDSCH capability).

[0295] For example, when the first set of capabilities indicates the UE processing capability 2 (e.g, the wireless device supports the UE processing capability 2), the PDSCH processing procedure may comprise determining the second timing gap based on the UE processing capability 2, e.g., the wireless device determines N1 from a second set of values for N1 (provided via / in a second PDSCH processing table) associated with an SCS pi. Based on the first set of capabilities do not indicate the UE processing capability 2 (e.g., the wireless device does not support the UE processing capability 2), the PDSCH processing procedure may comprise determining the second timing gap based on the UE processing capability 1 , e.g., the wireless device determines N1 (for determining second first timing gap) from a first set of values for N1 (provided via / in a first PDSCH processing table) associated with an SCS pi.

[0296] FIG. 18 shows an example of PDSCH processing time for the PDSCH processing capability 1. Values provided in FIG. 18 maybe an example of the first PDSCH processing table (e.g., table 5.3.1 for UE processing capability 1). In some embodiments in the present disclosure, the PDSCH processing time for the PDSCH processing capability 1 may be indicated by the first PDSCH processing table. Other examples for the first PDSCH processing table are also possible although not shown / discussed here.

[0297] FIG. 19A shows an example of PDSCH processing time for the PDSCH processing capability 2. Vaues provided in FIG. 19A maybe an example of the second PDSCH processing table (e.g., table 5.3.2 for UE processing capability 2). In some embodiments in the present disclosure, the PDSCH processing time for the PDSCH processing capability 2 in FIG. 19A maybe indicated by the second PDSCH processing table. Other examples for the second PDSCH processing table are also possible although not shown / discussed here.

[0298] As shown in FIG 18, for the PDSCH processing capability 1, the first PDSCH processing table may provide / indicate the first set of values for N1 (in number of symbols) for the PDSCH processing time. Each value of the first set of values for N1 may correspond to a subcarrier spacing (SCS) / numerology pi. The SCS may correspond to an SCS of the PDSCH (e.g., IIPDSCH) and / or a SCS of a PDCCH scheduling / indicating the PDCCH (e.g., dpoccHl and / or an SCS of the UL (e.g., fUL). Parameter N1,0 in FIG. 18 maybe 14 symbols or 13 symbols.Docket No.: 25-1052PCT

[0299] The PDSCH processing capability 1 may indicate the first set of values for N1 (in a number of symbols) associated with the numerology p (e.g., of the serving cell ora DL carrier or a DL BWP ora PDSCH). The first set of values maybe 8 or 10 or 17 or 20 or 80 or 160 respectively for numerology p (e.g., pPDSCH) of 0, 1, 2, 3, 5, 6. The PDSCH processing capability 2 may indicate the second set of values for N1 (in a number of symbols) associated with the numerology p (e.g., of the serving cell or a DL carrier or a DL BWP or a PDSCH). The second set of values may be 3 or 4.5 or 9 respectively for the numerology p (e.g., pPDSCH) of 0, 1 , 2.

[0300] As shown in FIG. 19A, for the PDSCH processing capability 2, the second PDSCH processing table may provide / indicate the second set of values for N1 (in number of symbols) for the PDSCH processing time. Each value of the second set of values for N1 may correspond to the subcarrier spacing (SCS) / numerology p. The SCS may correspond to the SCS of the PDSCH (e.g., ^PDSCH) and / or the SCS of a PDCCH scheduling / indicating the PDCCH (e.g., UPDCCHY) and / or the SCS of the UL (e.g., fiUL). Comparing FIG. 18 and FIG. 19A, corresponding to each numerology p, a value of the second set of values for N1 (provided by the second PDSCH processing table in FIG. 19A) is smaller than the corresponding value of the first set of values for N1 (provided by the first PDSCH processing table in FIG. 18)

[0301] Fora given numerology p for receiving the PDSCH, when the wireless device follows the UE processing capability 2, processing the PDSCH may be faster (more efficient) than when the wireless device follows the UE processing capability 1. For a given numerology p for receiving PDSCHs, when the wireless device follows the UE processing capability 2, processing PDSCHs may be faster (more efficient) than when the wireless device follows the UE processing capability 1. Receiving PDSCHs based on (or according or following) the UE processing capability 2 may result in enhancing efficiency (e.g., reducing DL transmission delay / latency) compared to processing PDSCHs based on the UE processing capability 1.

[0302] In some implementations, the PDSCH processing procedure (for processing the PDSCH) may comprise determining (by the wireless device) whether to process (or receives or decodes) the PDSCH based on the UE processing capability 1 or the UE processing capability 2.

[0303] In one example, in response to the first set of capabilities comprisi ng / i ndicati ng the UE processing 2, the PDSCH processing procedure may comprise processing the PDSCH according to the UE processing capability 2 based on the one or more configuration parameters (e.g., PDSCH-ServingCellConfig) enabling a processing type 2. For example, the one or more configuration parameters (e.g., PDSCH-ServingCellConfig) may comprise a parameter processingType2Enabled to enable the processing type 2 (e.g., when processingType2Enabled is set to 'enable').

[0304] In another example, in response to the first set of capabilities comprising / indicating the UE processing 2, the PDSCH processing procedure may comprise processing the PDSCH according to the UE processing capability 1 based on the one or more configuration parameters (e.g., PDSCH-ServingCellConfig) not enabling the processing type 2. Optionally, the one or more configuration parameters may not enable the processing type 2 based on the one or more configuration parameters (e.g., PDSCH-ServingCellConfig) not comprising / indicating the parameterDocket No.: 25-1052PCTprocessingType2Enabled (e.g., the parameter processingType2Enabled being absent from the one or more configuration parameters). Alternatively, the one or more configuration parameters may not enable the processing type 2 based on the one or more configuration parameters (e.g., PDSC H-ServingCellConfig) disabling the processing type 2 (e.g., when processingType2Enabled is set to 'disable').

[0305] In the present disclosure, corresponding to the PDSCH processing procedure and when the wireless device processes (or receives or decodes) the PDSCH based on the UE processing capability 1 , the wireless device may follow the UE processing capability 1 for receiving (e.g., processing / decoding) the PDSCH. When the wireless device processes (or receives or decodes) the PDSCH based on the UE processing capability 1 , the wireless device may process the PDSCH according to the UE processing capability 1.

[0306] In the present disclosure, corresponding to the PDSCH processing procedure and when the wireless device processes (or receives or decodes) the PDSCH based on the UE processing capability 2, the wireless device may follow the UE processing capability 2 for receiving (e.g., processing / decoding) the PDSCH. When the wireless device processes (or receives or decodes) the PDSCH based on the UE processing capability 2, the wireless device may process the PDSCH according to the UE processing capability 2.

[0307] Determining the first timing gap may be based on an additional processing delay d3. For example, the one or more configuration parameters may indicate the additional processing delay when the first set of capabilities indicate the UE processing capability 2. In some implementations, for the UE processing capability 2, the wireless device may determine the additional processing delay is zero (d3=0).

[0308] Additionally, the wireless device may determine the values of d-. and d2(in the second timing gap formula) based on at least one of the following: a number of PDSCH symbols allocated (e.g., a length of the PDSCH [symbols]) L (e.g., by time domain resource allocation table in the one or more PDSCH configuration parameters); and / or whether the PDSCH is a mapping Type A or a mapping Type B; and / or whether the PUCCH (associated with the PDSCH) overlaps with another PUCCH or PUSCH; and / or overlapping symbols between scheduling PDCCH (carrying the DCI scheduling the PDSCH) and the PDSCH; and / or whether the scheduling PDCCH is associated with a 3-symbol CORESET or not; and / or whether an uplink switching gap is triggered for the PUCCH or not.

[0309] For example, based on the uplink switching gap being triggered for the PUCCH (as shown in FIG. 17B), the wireless device may determine the second timing gap based on a first switching gap duration for an uplink (carrier) switching, e.g., Tswitcfl-UL>0. The switching gap duration may be (determined by or be) an uplink switching gap / duration / windowWTx1.Tx2to switch from the first carrier (CC 1 in FIG. 17B) to the second carrier (CC2 in FIG. 17B). For example, when the uplink switching gap is triggered for the PUCCH carrying the HARQ-ACK information corresponding to the PDSCH, the second timing gap may be Tswitch-UL+ Tproc-\ . The wireless device may determine the first processing condition not being satisfied based on the uplink switching gap being triggered for the PUCCH and the first uplink symbol of the PUCCH starting earlier than the duration of Tswitch-UL+ Tprocfrom the last symbol of the PDCCH carrying the DCI scheduling the PDSCH.Docket No.: 25-1052PCT

[0310] The first switching gap may also be referred to by an uplink switching gap.

[0311] Compared to FIG. 17B, FIG. 17A shows an example that the uplink switching gap is not triggered for the PUCCH, e.g., the second timing gap is not based on the first switching gap duration, e.g., Tswitch-UL=0 or the second timing gap is equal to Tproc,\ .

[0312] For example, the uplink switching may comprise switching from a first CC (the CC1) to a second CC (the CC2). For example, the uplink switching may comprise switching from the service cell (the cell 1) to a second serving cell (the cell 2).

[0313] Alternatively, corresponding to FIG. 17B, the wireless device may determine the first processing condition not being satisfied based on the uplink switching gap being triggered for the PUCCH and the first uplink symbol of the PUCCH starting earlier than the duration of Tswitch-UL+ Tprocfrom the last symbol of the PDSCH. Based on the first processing condition not being satisfied, the wireless device may not expect to transmit (via the C C2 / Cell 2) the PUCCH carrying the HARQ-ACK information for the PDSCH.

[0314] The uplink switching may be referred to as uplink carrier switching or Tx switching or the like. The scheduling DCI may trigger the uplink switching gap for the PUCCH (e.g., via the carrier indicator field of the DCI). The uplink carrier switching shown in FIG. 17B may bean example of a dynamic UL nTx-mTx(e.g., n=1 and m=2 or n=2 and m=2). For example, the first set of capabilities may comprise at least one UL switching capability (e.g., ULTxSwitchingBandPair-r16, ULTxSwitchingBandPair-v1700).

[0315] The at least one UL switching capability may indicate (e.g., via uplinkTxSwitchingPeriod-r16 and / or uplinkTxSwitchingPeriod2T2T-r17) a length / value of the uplink switching gap (e.g., the first switching gap duration). In one example, the length / value of the uplink switching gap may be a length / value of an UL Tx switching period of nTx-mTx(e.g., 2Tx-2Tx) switching per pair of UL bands (e.g., CC1 and CC2) per band combination, e.g., when the dynamic UL Tx switching (eg., 2Tx-2TX or 1 Tx-2Tx) is configured, e.g., when the one or more configuration parameters (e.g., CellGroupConfig and / or ServingCellConfig) enable / indicate / configure uplinkTxSwitching-2T-Mode. In another example, if / when the one or more configuration parameters does not enable / indicate / configure uplinkTxSwitching-2T-Mode (e.g., the uplinkTxSwitching-2T-Mode is absent from one or more configuration parameters), the one or more configuration parameters (e.g., uplinkTxSwitchingPeriod in ULTxSwitching BandPair or switching PeriodConfigForBandPair in uplinkTxSwitchingMoreBands) may indicate / configure the length / value of the uplink switching gap.

[0316] For example, the one or more configuration parameters, e.g., uplinkTxSwitching or uplinkTxSwitchingMoreBands may configure the wireless device with the uplink switching (e.g., the uplink carrier switching). When the one or more configuration parameters configure / indicate the uplink switching, the wireless device may omit / discard / avoid uplink transmissions via at least one cell / CC (carrier) of the one or more cells / the plurality of carriers (e.g. configured for uplink switching by the one or more configuration parameters and / or the first set of capabilities) during the uplink switching gap WTx1-Tx2.Docket No.: 25-1052PCT

[0317] FIG. 17C and / or FIG. 17D may show examples of a PUSCH processing procedure for receiving DL channels (e.g. , PDSCH). In the present disclosure, the PUSCH processing procedure may also be referred to by a PUSCH transmission procedure or an UL transmission procedure or an UL processing procedure.

[0318] For example, the wireless device may transmit (via the Cell 1 / CC1 or the Cell 2 / CC 2) a PUSCH (based on the PUSCH transmission procedure). Transmitting the PUSCH maybe via an active UL BWP corresponding to the active DL BWP) of the one or more BWPs, e.g., corresponding to the Cell 1 / CC1 or the Cell 2 / CC 2. The wireless device may transmit the PUSCH in / during a PUSCH transmission occasion.

[0319] In one example, the PUSCH transmission may comprise / carry at least one transport block (TB) (or a MAC PDU), e.g., the PUSCH transmission may be with the at least one TB. For example, the PUSCH may be with UL-SCH.

[0320] In another example, the PUSCH transmission may not comprise / carry a TB, e.g., the PUSCH transmission may not be with the TB. For example, the PUSCH may be without UL-SCH. For example, the PUSCH transmission may be for transmitting the at least one TB and no CSI report. In another example, the PUSCH transmission may be for transmitting the at least one TB and at least one CSI report.

[0321] The one or more configuration parameters may comprise. The PUSCH transmission (transmission power or spatial filter) may be based on the one or more PUSCH configuration parameters. The PUSCH transmission may be based on the one or more PUSCH configuration parameters (e.g., PUSCH-Config and / or PUSC H-ServingCellConfig) and / or one or more RACH configuration parameters (e.g., comprising msgA-PUSCH-Config), e.g., for transmission of MsgA PUSCH and / or msg3 PUSCH.

[0322] The one or more configuration parameters may comprise one or more CG configuration parameters. The one or more CG configuration parameters may configure / indicate at least one CG configuration (e.g., configuredGrantConfig). For example, the CG configuration may comprise a Type 1 CG configuration (rrc-ConfiguredUplinkGrant). The PUSCH transmission may be based on the one or more CG configuration parameters (e.g., a CG configuration of the at least one CG configuration).

[0323] The PUSCH transmission may be scheduled / triggered / indicated by a second DL command (or equivalently a second DL message ora second DL signal). The second DL command (or message or signal) may be the DC I (e.g., the scheduling DCI) scrambled by a first RNTI (e.g., C-RNTI or MCS-RNTI or the like). The wireless device may receive the second DL command during / in within a PDCCH reception occasion (e.g., a PDCCH monitoring occasion comprising / indicating the DCI), e.g., configured by the one or more PDCCH configuration parameters. The first DL command may be / comprise a RAR message or a fallback RAR message (scheduling / indicating a Msg3 PUSCH transmission, e.g., the PUSCH is the Msg3 PUSCH). The wireless device may receive the first DL command comprising a scheduling grant (e.g., an UL grant) for transmitting the PUSCH. The UL grant may be dynamically indicated by the first DL command.

[0324] In some examples, the UL grant may be a configured UL grant (e.g., CG grant Type 2), e.g., the PUSCH may be a CG PUSCH (e.g., a CG Type 2 PUSCH). For example, the first DCI may activate the CG Type 2 PUSCHDocket No.: 25-1052PCTtransmission (e.g., activates the CG configuration). The CG configuration may be a Type 2 CG configuration (e.g., when configuredGrantConfig does not include the rrc-ConfiguredllplinkGrant). Type 2 CG configuration may also be referred to by a CG Type 2 configuration. The CG PUSCH may, for example, be based on a CG Type 1 PUSCH. The CG configuration may be a Type 1 CG configuration (e.g., when configuredGrantConfig includes rrc-ConfiguredllplinkGrant). Type 1 CG configuration may also be referred to by a CG Type 1 configuration.

[0325] The PUSCH may be a MsgA PUSCH. For example, the wireless device may transmit the PUSCH based on the one or more PRACH configuration parameters (e.g., msgA-PUSCH-Config and / or msgA-MCS).

[0326] The PUSCH transmission may be without repetitions.

[0327] The PUSCH transmission may be with PUSCH repetitions. For example, transmitting the second TB may be based on PUSCH repetition Type B or PUSCH repetition Type A. The one or more PUSCH configuration parameters and / or the second DL command may configure / indicate the PUSCH repetition Type B or PUSCH repetition Type A, e.g., a type of PUSCH repetition (e.g., whether the PUSCH repetition is the PUSCH repetition Type B or PUSCH repetition Type A and / or a number of repetitions of the PUSCH repetition) and / or frequency hopping (e.g., inter-slot or intra-slot).

[0328] The one or more PUSCH configuration parameters (e.g., PUSCH-Config and / or PUSCH-ServingCellConfig) may further configure the number of slots for TB processing (e.g., numberOfSIotsTBoMS). The number of slots for TB processing may correspond to a PUSCH transmission with a TB over multi-slot (multiple slots) and may be indicated by the numberOfSIotsTBoMS. For example, the wireless device may determine the number of slots for TB processing is 1 (when the numberOfSIotsTBoMS is not configured).

[0329] The PUSCH transmission procedure may comprise determining a total number of (OFDM) symbols of the PUSCH Nsym corresponding to the PUSCH transmission occasion. The PUSCH transmission occasion may also be interchangeably referred to by a PUSCH allocation for a TB. The PUSCH transmission occasion may comprise / indude DM-RS (symbols) allocated / configured for the PUSCH transmission. Determining the PUSCH transmission occasion may be based on the timing advance (TA), e.g., the effect of the TA for advancing / delaying an UL frame with respect to the DL frame.

[0330] The PUSCH transmission occasion may comprise Nsym symbols allocated / scheduled for the PUSCH (e.g., indicated / configured by the one or more PUSCH configuration parameters and / or the second DL command), e.g., the wireless device may transmit the PUSCH during the Nsym symbols. For example, the total number of OFDM symbols of the PUSCH maybe a length of the PUSCH (L= Nsym) in symbols, wherein l=0, 1, 2,..., L-1 maybe OFDM symbol index of the scheduled PUSCH. The total number of symbols of the PUSCH may comprise (all) symbols (OFDM symbols) used for DM-RS.

[0331] For the PUSCH transmission with repetition Type B the Nsym symbols may comprise the total number of symbols for each nominal repetitio of the PUSCH without segmentation.Docket No.: 25-1052PCT

[0332] For the PUSCH transmission with repetition Type A the Nsym symbols may comprise the total number of symbols for each repetitio of the PUSCH.

[0333] The total number of OFDM symbols of the PUSCH may be a number of consecutive symbols L counting from a symbol S allocated for the PUSCH. The wireless device may determine L and S from a start and length indicator SLIV. The start and length indicator SLIV may indicate a start (e.g. , initial / fi rst / ea rl iest / starting symbol) of the PUSCH transmission occasion and the length of the PUSCH, e.g., Nsym symbols. The SLIV may correspond to a row (or an indexed row) of (or to) a resource allocation table (e.g., indicated / configured by the one or more PUSCH configuration parameters and / or the second DL command). The resource allocation table may be a time domain resource allocation table. The resource allocation table may comprise resource allocation configuration in time domain.

[0334] For example, the second DL command may indicate the row (or a row index). The second DL command may comprise a TDRA field indicating the row index (m). The TDRA field may be a “Time domain resource assignment” field of the DCI or a “PUSCH time resource allocation” field of the RAR / fallback RAR message. The TDRA filed of the DCI may indicate the start and length indicator SLIV indicating the start (e.g., initial / first / earliest / starting symbol) of the PUSCH transmission occasion and the length of the PUSCH, e.g., Nsym symbols. For the PUSCH transmission procedure, the wireless device may determine the SLIV (for determining the length of the PUSCH) based on the TDRA field of the second DL command.

[0335] As shown in FIG. 17C, the transmission of the PUSCH (e.g., with numerology / CC fiUL) is via the serving cell (e.g., the cell 1 of the one or more cells or the CC1 of the one or more CCs). The PUSCH transmission occasion may correspond to / with respect to (e.g., from a timing perspective) an UL frame / configuration of the wireless device corresponding to the cell 1 / carrier 1.

[0336] As shown in FIG. 17D, the transmission of the PUSCH is via the second serving cell (e.g., a cell 2 of the one or more cells or a CC2 of the one or more CCs). The PUSCH transmission occasion may correspond to / with respect to (e.g., from a timing perspective) an UL frame / configuration of the wireless device corresponding to the cell 2 / carrier 2.

[0337] Corresponding to FIG. 17C and / or FIG. 17D, the PUSCH processing procedure (e.g., the PUSCH transmission procedure) may further comprise determining (by the wireless device and / or the base station) whether a second processing condition is satisfied or not.

[0338] The second processing condition may be satisfied (or met) based on the first / initial / starting / earl iest (uplink) symbol of the PUSCH starting no earlier than at symbol L2. The symbol L2 may be a next (uplink) symbol (with its CP) starting after a fourth timing gap (e.g., Tproc2) after a last / final / ending / latest symbol of the PDCCH reception (carrying the DCI). The symbol L2 may be a next (uplink) symbol (with its CP) starting after the fourth timing gap (e.g., Tpr0C / 2) after the last / final / ending / latest symbol of the PDCCH monitoring occasion that the wireless device detects the DCI scheduling the PUSCH transmission.

[0339] The second processing condition maybe satisfied (or met) based on the first / initial / starting / earliest (uplink) symbol of the PUSCH (allocation) starting after the symbol L2. The second processing condition may be satisfied (orDocket No.: 25-1052PCTmet) based on the first / initial / starting / earliest (uplink) symbol of the PUSCH transmission occasion starting after the symbol L2. The second processing condition may be satisfied (or met) based on a timing difference between the first / initial / starting / earl iest (uplink) symbol of the PUSCH (comprising the TB) and the last / final / ending / latest symbol of the PDCCH reception (e.g., the PDCCH monitoring occasion) being larger / greater / longer than or equal to the fourth timing gap. The second processing condition may be satisfied (or met) based on the timing difference between the fi rst / initial / starti ng / earl iest (uplink) symbol of the PUSCH and the last / final / ending / latest symbol of the PDCCH monitoring occasion being larger / greater / longer than the fourth timing gap.

[0340] As shown in FIG. 17C and FIG. 17D, the first uplink symbol of the PUSCH (allocation or the transmission occasion) is after (or not start earlier than) the fourth timing gap (e.g., Tproc 2) after the last / final / ending / latest symbol of the PDCCH reception. Based on the second processing condition being satisfied, the wireless device may (via the cell 1 / Carrier 1 in FIG. 17C or the Cell 2 / Carrier 2 in FIG. 17D) transmit the PUSCH carrying the TB (e.g., transmit the TB).

[0341] Alternatively, the second processing condition may not be satisfied (or not met) based on the first / initial / starti ng / earliest (uplink) symbol of the PUSCH (allocation) starting before or prior to the symbol L2. The second processing condition may not be satisfied based on the fi rst / in itial / starting / earliest (uplink) symbol of the PUSCH transmission occasion starting before or prior to the symbol L2. The second processing condition may not be satisfied based on the timing difference between the first / initial / starting / earliest (uplink) symbol of the PUSCH (comprising the TB) and the last / final / ending / latest symbol of the PDCCH reception (e.g., the PDCCH monitoring occasion) being smaller / shorter than or equal to the fourth timing gap. The second processing condition may not be satisfied based on the timing difference between the first / initial / starting / earliest (uplink) symbol of the PUSCH and the last / final / ending / latest symbol of the PDCCH monitoring occasion being smaller / shorter / lower than the fourth timing gap.

[0342] The second processing condition may not be satisfied (or not met) based on the first / i n itial / starting / earliest (uplink) symbol of the PUSCH (allocation or the transmission occasion) starting earlier than at symbol L2 The second processing condition maybe satisfied based on the first / initial / starting / earliest (uplink) symbol of the PUSCH (allocation or the transmission occasion) starting before the symbol L2. The second processing condition may not be satisfied (or met) based a first / in itial / starting / earliest (uplink) symbol of the PUSCH transmission occasion starting earlier than the fourth timing gap (e.g., Tproc2) later than the last / final / ending / latest symbol of the PDCCH reception (e.g., the PDCCH monitoring occasion). The second processing condition may be not satisfied (or met) based on the first / initial / starting / earl iest (uplink) symbol of the PUSCH transmission occasion being during / within the fourth timing gap after the last / final / ending / latest symbol of the PDCCH reception (e.g., the PDCCH monitoring occasion).

[0343] Based on the second processing condition not being satisfied, the wireless device may avoid / refrain transmitting the PUSCH carrying the TB (e.g., the wireless device may ignore / avoid the second DL command).

[0344] The PUSCH processing procedure (or the PUSCH transmission procedure) may comprise determining the fourth timing gap. For example, according to / for the PUSCH processing procedure, the wireless device may determineDocket No.: 25-1052PCTthe fourth timing gap as Tproc2= max^(N2+ d2j + d2) (2048 + 144) • K2'M’ Tc+ Text + Tswitch-ULld2:2)-The wireless device may determine d2,i to be equal to 0 or 1 (depending on whether a first symbol of the PUSCH transmission / allocation comprises DM-RS only or not). The wireless device may determine Text=0 when the PUSCH transmission is notpartof a shared spectrum channel access (in FR1). In the present disclosure, the PUSCH transmission is notpartof a shared spectrum channel access (in FR1), e.g., Text=0. The wireless device may determine d2based on priorities of the PUSCH and PUCCH(s) that are overlapping with the PUSCH transmission. For example, when the priority of the PUSCH is higher than a priority of PUCCH and the wireless device may not be able to simultaneously transmit PUSCH and PUCCH, the wireless device may determine / set d2>0, e.g., based on an indication value provided by the first set of capabilities. In the present disclosure, the wireless device may set d2- 0.

[0345] Parameter d22= 0 when the second DL command (scheduling the PUSCH transmission) not indicating a BWP switch (from a first BWP of the one or more BWPs that the wireless device receives the second DL command to a second BWP of the one or more BWPs for transmitting the PUSCH transmission). When the second DL command (scheduling the PUSCH transmission) indicators / triggers the BWP switch (from the first BWP of the one or more BWPs that the wireless device receives the second DL command to the second BWP of the one or more BWPs for transmitting the PUSCH transmission), d may be equal to a BWP switching delay (e.g., TBWPswitchDeiay) in a number of slots. The BWP switching delay may be based on a first SCS of the first BWP (e.g., configured by the one or more configuration parameters) and a second SCD of the second BWP (e.g., configured by the one or more configuration parameters). In the present disclosure, the wireless device may set d2>2= 0.

[0346] The wireless device may determine (value of) parameter N2 (for determining the fourth timing gap Tproc,2) based on / with accordance to the UE processing capability. The UE processing capability may be the UE processing 2 (e.g., the UE processing capability 2, e.g., advanced or aggressive PUSCH capability) and / or the UE capability 1 (e.g., the UE processing capability 1 e.g., baseline / default PUSCH capability).

[0347] For example, when the first set of capabilities indicates the UE processing capability 2 (e.g., the wireless device supports the UE processing capability 2), the PUSCH processing procedure may comprise determining the fourth timing gap based on the UE processing capability 2, e.g., the wireless device determines N2 from a second set of values for N2 (provided via / in a second PUSCH processing table) associated with an SCS p. Based on the first set of capabilities do not indicate the UE processing capability 2 (e.g., the wireless device does not support the UE processing capability 2), the PUSCH processing procedure may comprise determining the fourth timing gap based on the UE processing capability 1 , e.g., the wireless device determines N2 (for determining fourth first timing gap) from a first set of values for N1 (provided via / in a first PUSCHH processing table) associated with an SCS p.

[0348] FIG. 19B shows an example of PUSCH processing time for the PUSCH processing capability 2. Vaues provided in FIG. 19B maybe an example of the second PUSCH processing table (e.g., table 6.4.2 for UE processing capability 2). In some embodiments in the present disclosure, the PUSCH processing time for the PUSCH processingDocket No.: 25-1052PCTcapability 2 in FIG. 19B maybe indicated by the second PUSCH processing table. Other examples for the second PUSCH processing table are also possible although not shown / discussed here.

[0349] FIG. 20 shows an example of PUSCH processing time for the PUSCH processing capability 1. Values provided in FIG.20 may be an example of the first PUSCH processing table (e.g., table 6.4.1 for UE processing capability 1). In some embodiments in the present disclosure, the PUSCH processing time for the PUSCH processing capability 1 may be indicated by the first PUSCH processing table. Other examples for the first PUSCH processing table are also possible although not shown / discussed here.

[0350] As shown in FIG. 20, for the PUSCH processing capability 1, the first PUSCH processing table may provide / indicate the first set of values for N2 (in number of symbols) for the PUSCH processing (or preparation) time. Each value of the first set of values for N2 may correspond to a subcarrier spacing (SCS) / numerology pi The SCS may correspond to an SCS of the PUSCH (e.g., HPUSCH and / or a SCS of a PDCCH scheduling / indicating the PDCCH (e.g., APDCCW)) and / or an SCS of the UL (e.g., fiUL).

[0351] The PUSCH processing capability 1 may indicate the first set of values for N2 (in a number of symbols) associated with the numerology p (e.g., of the serving cell ora DL carrier or a DL BWP ora PUSCH). The first set of values for N2 maybe 10 or 12 or 23 or 36 or 144 or 288 respectively for numerology p (e.g., pPUSCH) of 0, 1, 2, 3, 5, 6. The PUSCH processing capability 2 may indicate the second set of values for N2 (in a number of symbols) associated with the numerology p (e.g., of the serving cell or a DL carrier or a DL BWP or a PDSCH). The second set of values may be 5 or 5.5 or 11 respectively for the numerology p (e.g., pPUSCH) of 0, 1,2.

[0352] As shown in FIG 19B, for the PUSCH processing capability 2, the second PUSCH processing table may provide / indicate the second set of values for N2 (in number of symbols) for the PUSCH processing time. Each value of the second set of values for N2 may correspond to the subcarrier spacing (SCS) / numerology p. The SCS may correspond to the SCS of the PUSCH (e.g., HPUSCH) and / or the SCS of a PDCCH scheduling / indicating the PDCCH (eg., / J-PDCCH)) and / or the SCS of the UL (e.g., fUL). Comparing FIG. 20 and FIG. 19B, corresponding to each numerology p, a value of the second set of values for N2 (provided by the second PUSCH processing table in FIG. 19B) is smaller than the corresponding value of the first set of values for N2 (provided by the first PUSCH processing table in FIG. 20).

[0353] In some implementations, the PUSCH processing procedure (for processing the PUSCH) may comprise determining (by the wireless device) whether to process (or transmits) the PUSCH based on the UE processing capability 1 or the UE processing capability 2.

[0354] In one example, in response to the first set of capabilities comprisi ng / i ndicati ng the UE processing 2, the PUSCH processing procedure may comprise processing the PUSCH according to the UE processing capability 2 based on the one or more configuration parameters (e.g., PUSCH-ServingCellConfig) enabling a processing type 2. For example, the one or more configuration parameters (e.g., PUS CH-Servi ng Cel I Config) may comprise a parameter processingType2Enabled to enable the processing type 2 (e.g., when processingType2Enabled is set to 'enable').Docket No.: 25-1052PCT

[0355] In another example, in response to the first set of capabilities comprising / indicating the UE processing 2, the PUSCH processing procedure may comprise processing the PUSCH according to the UE processing capability 1 based on the one or more configuration parameters (e.g., PUSCH-ServingCellConfig) not enabling the processing type 2. Optionally, the one or more configuration parameters may not enable the processing type 2 based on the one or more configuration parameters (e.g., PUSCH-ServingCellConfig) not comprising / indicating the parameter processingType2Enabled (e.g., the parameter processingType2Enabled being absent from the one or more configuration parameters). Alternatively, the one or more configuration parameters may not enable the processing type 2 based on the one or more configuration parameters (e.g., PUSC H-ServingCellConfig) disabling the processing type 2 (e.g., when processingType2Enabled is set to 'disable').

[0356] In the present disclosure, corresponding to the PUSCH processing procedure and when the wireless device processes (or transmits) the PUSCH based on the UE processing capability 1 , the wireless device may follow the UE processing capability 1 for transmitting (e.g., processing or preparing) the PUSCH / TB. When the wireless device processes (or transmits) the PUSCH based on the UE processing capability 1 , the wireless device may process the PUSCH according to the UE processing capability 1.

[0357] In the present disclosure, corresponding to the PUSCH processing procedure and when the wireless device processes (or transmits) the PUSCH based on the UE processing capability 2, the wireless device may follow the UE processing capability 2 for transmitting (e.g., processing or preparing) the PUSCH / TB. When the wireless device processes (or transmits) the PUSCH based on the UE processing capability 2, the wireless device may process the PUSCH according to the UE processing capability 2

[0358] In the example of FIG. 17C, as the uplink switching gap is not triggered for the PUSCH transmission (e.g., the second DL command does not trigger the uplink switching gap or the TX switching), the wireless device may determine swi.tcli.-UL ~ 0.

[0359] In the example of FIG. 17D, as the uplink switching gap is triggered for the PUSCH transmission (e.g., the second DL command trigger the uplink switching gap or the TX switching), the wireless device may determine Tswitch-uL > 0. wherein the 'Tswitc?1_ is equal to the first switching gap duration. For example, when the uplink switching gap is triggered for the PUSCH transmission and the one or more configuration parameters indicate / configure a dual UL (e.g., uplinkTxSwitchingOption set of ‘dualUL’) for uplink carrier aggregation among the first CC (with an UL SCS Of H-UL, carrier]) ^nd the Second CC (with an UL SCS of ^UL:carrierl): P-UL ~ carrier]: ftuL, carried) ■

[0360] Low-band (LB) spectrum supports substantial traffic volumes in both urban (indoor) and rural areas, resulting in congestion that significantly degrades customer experience. Low-band single DL (SDL) bands (or equivalently SDL low bands) are underutilized due to their close frequency proximity to other low bands, complicating their aggregation for CA. Conversely, the SDL low bands may be located far from another low-band carrier (e.g., FDD carries in low band), rendering the wireless device antenna design impractical or complex. To address these practical challenges inDocket No.: 25-1052PCTthe wireless device implementation, a switched Low-Band to Low-Band Carrier Aggregation operation, e.g. , Low-Band Carrier Aggregation via switching (LB CA via switching or equivalently switching for LB CA operation) is proposed.

[0361] FIG. 21, FIG. 22, FIG. 23A, FIG. 23B, and FIG. 23C, show examples of low-band carrier aggregation (LB CA) via switching. The switching in FIG. 21, FIG. 22, FIG. 23A, FIG. 23B, and FIG.23C maybe a DL switching, e.g., to switch from an FDD-DL carrier to a single / supplementary DL (e.g., SDL) carrier or to switch from the SDL carrier to the FDD-DL carrier. FIG.21, FIG. 22, FIG. 23A, FIG. 23B, and FIG.23C provides examples of the DL switching. FIG. 21, FIG. 22, FIG. 23A, FIG. 23B, and FIG. 23C also shows an example of a band combination (e.g., FDD-SDL band combination) for the LB CA operation via switching (e.g., LB-LB carrier aggregation via switching). The switching for the LB CA operation may be an Rx switching (an example shown in FIG.22).

[0362] The base station and / or the wireless device may support a plurality of downlink frequency bands. The base station and / or the base station may configure / operate a carrier in each of the plurality of downlink frequency bands. For example, the base station and / or the wireless device may support a first frequency band (e.g., n5, frequency range in 850 MHz). The first frequency band may comprise a first DL carrier (e.g., the FDD-DL carrier) and a first uplink carrier (e.g., an FDD-UL carrier) corresponding to the first DL carrier. The one or more configuration parameters may configure / indicate the first DL carrier (e.g., the FDD-DL carrier) and the first uplink carrier (e.g., the FDD-UL carrier) corresponding to the first DL carrier. For example, a first serving cell (e.g., a PCell, e.g., Cell 1) of the one or mor cells may comprise (or be configured with) the first DL carrier (e.g., the FDD-DL carrier) and the first uplink carrier (e.g., the FDD-UL carrier) paired / linked / corresponding to the first DL carrier.

[0363] In the present disclosure, a first carrier (of the plurality of CCs) may interchangeably be referred to as the first DL carrier or an FDD carrier. The FDD carrier may comprise UL (e.g., the first UL carrier) and DL (e.g., the first DL carrier). The first carrier may also be understood as the first cell (e.g., the PCell and / or the first cell and / or the first serving cell and / or the Cell 1). For example, the Cell 1 may comprise (or be configured by the one or more configuration parameters) with the first carrier.

[0364] The base station and / or the wireless device may support a second frequency band (e.g., n29, frequency range of 717 MHz to 728 MHz). The second frequency band may comprise a second DL carrier (e.g., the SDL carrier). The second frequency band may not comprise a second UL carrier corresponding to the second DL carrier. The one or more configuration parameters may configure / indicate the second DL carrier (e.g., the SDL carrier) without configuring / indicating / activating the second uplink carrier In one implementation of the LB CA (operation) via switching (e.g., CA_n5A-n29A band combination), the first serving cell (e.g., the PCell, e.g., the Cell 1) may further comprise the second DL carrier as a supplementary carrier for the first DL carrier. In another implementation of the LB CA (operation) via switching, a secondary cell (e.g., an SCell, e.g., a Cell 2, of the one or more cells) may comprise / be configured with the second DL carrier (e.g., the SDL carrier). The SCell may only comprise the SDL carrier (e.g., without the second UL carrier).Docket No.: 25-1052PCT

[0365] In the present disclosure, the second carrier (of the plurality of CCs) may interchangeably refer to as the second DL carrier or the SDL carrier. The SDL carrier may only comprise DL (e.g., the second DL carrier). The second carrier may also be equivalent to the SCell (e.g., a second serving cell or the Cell 2 or a second cell). For example, the Cell 2 may comprise (or be configured by the one or more configuration parameters) the second carrier.

[0366] In one example of the LB CA (operation, e.g., the LB CA via switching), the first cell may be the same as the second cell (e.g., with the same cell identifier / ID / index), e.g., the first serving cell is configured (e.g., by the one or more configuration parameters) with two DL carriers (e.g., the FDD-DL and the SDL carriers) and a single UL carrier (e.g., the FDD-UL carrier) and the one or more configuration parameters configure / indicate the first carrier and the second carrier for the LB CA operation via switching. For this example, the LB CA operation via switching may comprise switching between the first carrier (of the first cell) and the second carrier (of the first cell) (Case 2-to-Case 1 switching and Case 1-to-Case 2 switching) and / or switching between the first DL carrier (of the first cell) and the second DL carrier (of the first cell) (Case 2-to-Case 1 switching and Case 1-to-Case 2 switching).

[0367] In another example of the LB CA (operation, e.g., the LB CA via switching), the first cell may be different than the second cell (e.g., with the different cell identifiers / IDs / indexes), e.g., the first serving cell is configured (e.g., by the one or more configuration parameters) with the first DL carrier (e.g, the FDD-DL) and the first UL carrier (eg., the FDD-UL carrier) and the second serving cell is only configured (e.g., by the one or more configuration parameters) with the second DL carrier (e.g., the SDL) and the one or more configuration parameters configure / indicate the first carrier / first cell and the second carrier / second cell for the LB CA operation via switching. For this example, the LB CA operation via switching may comprise switching between the first cell and the second cell (Case 2-to-Case 1 switching and Case 1-to-Case 2 switching) and / or switching between the first carrier and the second carrier (Case 2-to-Case 1 switching and Case 1-to-Case 2 switching) and / or switching between the first DL carrier and the second DL carrier (Case 2-to-Case 1 switching and Case 1-to-Case 2 switching).

[0368] The first frequency band may be / comprise an FDD band, where a downlink spectrum (e.g., the first DL carrier) and an uplink spectrum (e.g., the first UL carrier) are paired / linked. The second frequency band may be / comprise a supplementary downlink band / carrier, a supplementary FDD band / carrier, or a downlink only FDD band / carrier, where only a downlink spectrum (e.g., the SDL carrier) may be available for the DL receptions.

[0369] In some embodiments of the present disclosure, the first carrier and the second carrier may be associated with a single serving cell (e.g., the Cell 1 or the Cell 2).

[0370] In some embodiments of the present disclosure, the first cell (the cell 1) is associated with the first carrier and the first uplink carrier. The second cell (the cell 2) is associated with the second carrier.

[0371] The first cell may be a primary cell of a cell group (e.g., the MCG or the SCG), a primary cell of the one or more cells or a first secondary cell of the one or more cells.

[0372] The second cell may be a second secondary cell of the one or more cells.Docket No.: 25-1052PCT

[0373] The first cell and the second cell may belong to a same cell group (e.g., the master cell group or the secondary cell group).

[0374] The first cell and the second cell may belong to a same timing advance group (TAG), e.g., the pTAG or the STAG.

[0375] Corresponding to the LB CA, as shown in FIG. 21 , FIG.22, FIG.23A, FIG. 23B, and FIG. 23C, the wireless device may support the first frequency band and / or the second frequency band via / based on the DL switching, e.g., the wireless device may not support (or has capability for) simultaneous (e.g., during a first time duration, see FIG. 22) reception(s) in the DL via the first frequency band and the second frequency band. Corresponding to the LB CA, the wireless device may support DL reception(s) only either via / on the first frequency band or the second frequency band during / within a second time duration (as shown in FIG.22). As shown in FIG. 21, the base station and the wireless device may communicate (in UL and / or DL) via the first DL carrier and / or the first UL carrier during / at occurrences of the first time duration or communicate in only DL via the second DL carrier during / at occurrences of the second time duration. As seen, the first time duration and the second time duration may not overlap with each other (in time). The first time duration may correspond to ON duration of the first carrier (e.g., operation on the first carrier is enabled) and OFF duration of the second carrier (e.g., operation on the second carrier is disabled). The second time duration may correspond to an OFF duration of the first carrier (e.g., operation on the first carrier is disabled) and the ON duration of the second carrier (e.g., operation on the second carrier is enabled).

[0376] In the present disclosure, as shown in FIG.21 and / or FIG. 22, the LB CA may be an example of CA in DL according to DL switching, e.g., for switching (periodically) between the first time duration and the second time duration according to / based on a switching pattern. The switching between the first time duration and the second time duration may be based on the switching pattern, e.g., a time-domain multiplexing (TDM) pattern (or mechanism e.g., tdm-pattern-carrier-switching), see FIG. 22 for an example. The TDM pattern may be a semi-static (SP) pattern, e.g., a semi-static switching pattern. The TDM pattern (e.g., the switching pattern) may indicate / configure a time mask. Compared to the Tx switching discussed above (which may be triggered dynamically via a DCI for UL transmissions), the DL switching (for the LB CA operation shown FIG.21, FIG. 22, FIG.23A, FIG. 23B, and FIG. 23C) is triggered / initiated / executed semi-statically / periodically (e.g., not dynamically) according to the semi-static switching pattern (e.g., the switching pattern). The one or more configuration parameters (e.g., for the LB CA via switching) may configure / indicate the TDM pattern for the DL switching (e.g., the SP pattern or the switching pattern). The TDM pattern may be a pattern for the downlink carrier switching or a carrier switching for downlink (e.g., LB CA operation via switching).

[0377] In the specification, the carrier aggregation of the first carrier and the second carrier based on the TDM mechanism / pattern (e.g., Carrier Switching) may be referred as a Carrier Switching, a carrier aggregation via switching, CA with switching, and / or the LB CA via switching, or a TDM-ed CA, PCell carrier switching, DL / SDL switching, a CADocket No.: 25-1052PCTwith SDL, a CA with DL / SDL, a serving cell with DL / SDL or a switching scheme for LB CA, etc. Other terminologies are also possible though not mentioned here.

[0378] As shown in FIG. 21 and FIG. 22, each occurrence of the first time duration may correspond to Case 1 (e.g., Case 1 operation of the LB CA). Corresponding / according to Case 1, during each occurrence of the first time duration the wireless device may transmit (to the base station, UL signals / channels (UL transmissions, e.g., PRACH / SRS / PUSCH / PUCCH) via the first UL carrier and / or receive (from the base station) DL signals / channels (DL receptions, e.g., PDCCH / CSI-RS / SSB / PDSCH) via the first DL carrier (e.g., using a first Rx chain).Corresponding / according to Case 1 , symbols / slots overlapping / al located for each occurrence of the first time duration may be unavailable / invalid (in time / frequency domain) for receiving (from the base station) DL signals / channels (DL receptions, e.g., PDCCH / CSI-RS / SSB / PDSCH) via the second DL carrier (e.g., using a second Rx chain).Corresponding / according to Case 1 , symbols / slots overlapping / al located for each occurrence of the first time duration may only be avai lable / val id (in time / frequency domain) for receiving (from the base station) DL signals / channels (DL receptions, e.g., PDCCH / CSI-RS / SSB / PDSCH) via the first DL carrier. Corresponding / according to Case 1, symbols / slots overlappi ng / al located for each occurrence of the first time duration may be available / valid (in time / frequency domain) for transmitting (to the base station) UL signals / channels (UL transmissions, eg., PRACH / SRS / PUSCH / PUCCH) via the first UL carrier.

[0379] As shown in FIG. 21 and FIG. 22, each occurrence of the second time duration may correspond to Case 2 (e.g., Case 2 operation of the LB CA). Corresponding / according to Case 2, during each occurrence of the second time duration the wireless device may skip / ignore / avoid transmitting, e.g., not transmit, (to the base station, UL signals / channels (UL transmissions, e.g., PRACH / SRS / PUSCH / PUCCH) via the first UL carrier and only receive (from the base station) DL signals / channels (DL receptions, e.g., PDCCH / CSI-RS / SSB / PDSCH) via the second DL carrier. Corresponding / according to Case 2, symbols / slots overlapping / allocated for each occurrence of the second time duration may be unavailable / invalid (in time / frequency domain) for receiving (from the base station) DL signals / channels (DL receptions, e.g., PDCCH / CSI-RS / SSB / PDSCH) via the first DL carrier. Corresponding / according to Case 2, symbols / slots overlapping / allocated for each occurrence of the second time duration may only be available / valid (in time / frequency domain) for receiving (from the base station) DL signals / channels (DL receptions, e.g., PDCCH / CSI-RS / SSB / PDSCH) via the second DL carrier. Corresponding / according to Case 2, symbols / slots overlapping / allocated for each occurrence of the second time duration may be unavailable (in time / frequency domain) for transmitting (to the base station) UL signals / channels (UL transmissions, e.g., PRACH / SRS / PUSCH / PUCCH) via the first UL carrier.

[0380] FIG. 22 further shows that Case 1 corresponds to / is associated with Rx / Tx (the first Rx chain for DL operations and an Tx chain for UL operations) on the first carrier (e.g., the first DL carrier, e.g., the FDD-DL carrier, and the first UL carrier, e.g., the FDD-UL carrier) and no Rx operation on the second carrier (e.g. the SDL carrier). As discussed above, switching from Case 2 to Case 1 (e.g., the DL switching for LB CA) may comprise switching anDocket No.: 25-1052PCTantenna connector of the wireless device to an RF Rx circuitry (e.g., LO / LNA, mixer, filters, or the like) tuned / allocated / designed for the first carrier (e.g., Carrier 1) for the DL receptions via the first DL carrier and the UL transmissions via the first UL carrier. Case 2 corresponds to / is associated with a second Rx chain for DL operations (e.g., without any Tx chain for UL operation) on the second carrier (e.g., the second DL carrier, e.g., the SDL carrier) and no Rx / Tx operation on the first carrier. For example, switching from Case 1 to Case 2 (e.g., the DL switching for LB CA) may comprise switching an antenna connector of the wireless device to an RF Rx circuitry (e.g., LO / LNA, mixer, filters, or the like) tuned / allocated / designed for the second carrier (e.g., Carrier 2) for the DL receptions via the second DL carrier. Switching from Case 2 to Case 1 may also be referred to as Case 2-to-Case 1 switching. Switching from Case 1 to Case 2 may also be referred to as Case 1-to-Case 2 switching. For the DL switching there may be several options (Option 1 and Option 2) for the wireless device.

[0381] In some implementations (Option 1), some components of the RF Rx circuitry (e.g., LO / LNA / PLL and / or filters) may be exclusively dedicated for the DL receptions via the Carrier 2 or the DL receptions via the Carrier 1 , e.g., switching may comprise actual switching in hardware from the first Rx chain (dedicated for the Carrie 1) to the second Rx chain (dedicated for the Carrier 2) and returning the RF Rx circuitry with accordance to Case 1 or Case 2.

[0382] In some other implementations (Option 2), some components of the RF Rx circuitry (e.g., LO / LNA or some filters) may be shared / common for the DL receptions via the Carrier 2 or the DL receptions via the Carrier 1, e.g., switching may comprise returning shared components of the RF Rx circuitry with accordance to Case 1 or Case 2.

[0383] For example, under a first option (Option 1 ) for the wireless device architecture (e.g., a first option for a reference UE architecture for LB CA operation via switching), each Rx chain (corresponding to each carrier, e.g., a first Rx chain for the first DL carrier and a second Rx chain for the second DL carrier) has its exclusive (not shared) filters, LNA, local oscillator (LO) and phase locked loop (PLL). For the first option for the reference UE architecture for LB CA operation via switching: Case 1 uses the first Rx chain and Case 2 uses the second Rx chain; and Case 2-to-Case 1 switching is switching the antenna connector to switch from the second Rx chain to the first Rx chain (e.g., retuning the corresponding fi Iter / LO / LN A and / or PLL); and Case 1 -to-Case 2 switching is switching the antenna connector to switch from the first Rx chain to the second Rx chain (e.g., retuning the corresponding filter / LO / LNA and / or PLL).

[0384] For example, under a second option (Option 2) for the wireless device architecture (e.g., a second option for the reference UE architecture for LB CA operation via switching), each Rx chain (corresponding to each carrier, e.g., a first Rx chain for the first DL carrier and a second Rx chain for the second DL carrier) has its exclusive (not shared) filters. The LNA, the local oscillator (LO) and the phase locked loop (PLL) are shared for both Case 1 and Case 2. For the first option for the reference UE architecture for LB CA operation via switching: Case 1 uses the first Rx chain and Case 2 uses the second Rx chain while the LNA, the local oscillator (LO) and the phase locked loop (PLL) are shared for both Case 1 and Case 2; and Case 2-to-Case 1 switching is switching the antenna connector to switch from the second Rx chain to the first Rx chain (e.g., retuning the corresponding filter); and Case 1-to-Case 2 switching isDocket No.: 25-1052PCTswitching the antenna connector to switch from the first Rx chain to the second Rx chain (e.g., retuning the corresponding filter).

[0385] The switching pattern (e.g., the TDM pattern) for the LB CA operation via switching may further indicate / configure the first time duration and / or the second time duration. The first time duration may be the same as the second time duration (e.g., when the switching pattern only indicate a single time duration for the first time duration). The first time duration may be different than the second time duration (e.g., when the switching pattern indicates two time durations one for the first time duration and one or the second time duration). For example, the switching pattern may indicate a length (e.g., in number of slots / symbols / subframes or ms) of the first time duration and / or a length (e.g., in number of slots / symbols / subframes or ms) of the second time duration. For example, the length of the first time duration may be equal to the length of the second time duration. In another example, the length of the first time duration may be different than (e.g., longer or alternatively shorter than) the length of the second time duration.

[0386] For example, the first set of capabilities may indicate a first value (e.g., in number of slots / symbols / subframes or ms) for the length of the first time duration. The first value may be a minimum / default length of the first time duration. For example, the first value may be m slots (e.g., m=1, 2, 3.. ) or n symbols (n=10, 11, 12, ...or the like) orx ms (e.g., 10 ms or 20 ms or the like). The wireless device may expect that the configured / indicated length for the first time duration (by the one or more configuration parameters for the LB CA operation via the switching) to be larger than or equal to the indicated first value for the length of the first time duration. When one or more configuration parameters for the LB CA operation via the switching does not indicate value for the length of the first time duration, the wireless device may determine the length of the first time duration is the first value indicated by the first set of capabilities. When m=1 or when n<15 symbols (e.g., the first value is equal to single slot), the first set of capabilities (or the indicated first value via the first set of capabilities) may indicate the wireless device may support the LB CA operation via switching in a slot-based manner / mechanism for the carrier switching. When m>1 or when n> 14 symbols, the first set of capabilities (or the indicated first value via the first set of capabilities) may indicate the wireless device may not support the LB CA operation via switching in a slot-based manner / mechanism (or the wireless device may support the LB CA operation via switching in a multi-slot based manner / mechanism) for the carrier switching.

[0387] Additionally and / or alternatively, the first set of capabilities may indicate a second value (e.g., in number of slots / symbols / subframes or ms) for the length of the second time duration. The second value may be a minimum / default length of the second time duration. For example, the second value maybe m slots (e.g., m=1, 2, 3... ) orn symbols (n=10, 11, 12, ...or the like) orx ms (e.g., 10 ms or 20 ms or the like). The wireless device may expect that the configured / indicated length for the second time duration (by the one or more configuration parameters for the LB CA operation via the switching) to be larger than or equal to the indicated second value for the length of the second time duration. When one or more configuration parameters for the LB CA operation via the switching does not indicate value for the length of the second time duration, the wireless device may determine the length of the second timeDocket No.: 25-1052PCTduration is the second value indicated by the first set of capabilities. When m=1 or when n< 15 symbols (e.g., the second value is equal to single slot), the first set of capabilities (or the indicated second value via the first set of capabilities) may indicate the wireless device may support the LB CA operation via switching in a slot-based manner / mechanism for the carrier switching. When m>1 or when n> 14 symbols, the first set of capabilities (or the indicated second value via the first set of capabilities) may indicate the wireless device may not support the LB CA operation via switching in a slot-based manner / mechanism (or the wireless device may support the LB CA operation via switching in a multi-slot based manner / mechanism) for the carrier switching.

[0388] In the present disclosure, occurrences of the first time duration may comprise a first plurality of windows / durations that the wireless device and / or the base station operates the LB CA based on / with accordance to Case 1. Each occurrence of the first time duration may correspond to each window / duration of the first plurality of windows / durations that the wireless device and / or the base station operates the LB CA based on / with accordance to Case 1. An occurrence of the first time duration (corresponding to a window / duration of the first plurality of windows / durations) may comprise a time duration (or an elapse of time or a time distance) from a time point / instate when a Case 2-to-Case 1 switching occurred / completed / triggered / initiated until / to a time point / instance when the Case 1-to-Case 2 switching occurred / completed / triggered / initiated.

[0389] In the present disclosure, occurrences of the second time duration may comprise a second plurality of windows / durations that the wireless device and / or the base station operates the LB CA based on / with accordance to Case 2. Each occurrence of the second time duration may correspond to each window / duration of the second plurality of windows / durations that the wireless device and / or the base station operates the LB CA based on / with accordance to Case 2. An occurrence of the second time duration (corresponding to a window / duration of the second plurality of windows / durations) may comprise a time duration (or an elapse of time or a time distance) from a time point / instate when a Case 1-to-Case 2 switching occurred / completed / triggered / initiated until / to a time point / instance when the Case 2-to-Case 1 switching occurred / completed / triggered / initiated.

[0390] When the length of the first time duration is not indicated (by the switching pattern), the wireless device may determine the length of the first time duration is equal to the length of the second time duration indicated by the switching pattern.

[0391] When the length of the second time duration is not indicated (by the switching pattern), the wireless device may determine the length of the second time duration is equal to the length of the first time duration indicated by the switching pattern.

[0392] When the length of the first time duration is not indicated (by the switching pattern), the wireless device may determine the length of the first time duration is equal to a first number of slots / subframes of the first cell (e.g., with accordance to an SCS of the first DL carrier). The first number of slots / subframes may be one or two or the like. The first number of slots / subframes may be preconfigured.Docket No.: 25-1052PCT

[0393] When the length of the first time duration is not indicated (by the switching pattern), the wireless device may determine the length of the first time duration is equal to a first number of slots / subframes of the second cell (e.g . , with accordance to an SCS of the second DL carrier).

[0394] When the length of the second time duration is not indicated (by the switching pattern), the wireless device may determine the length of the second time duration is equal to a second number of slots / subframes of the second cell (e.g., with accordance to an SCS of the second DL carrier). The first number of slots / subframes may be one or two or the like. The second number of slots / subframes may be preconfigured.

[0395] When the length of the second time duration is not indicated (by the switching pattern), the wireless device may determine the length of the second time duration is equal to a second number of slots / subframes of the first cell (eg., with accordance to an SCS of the first DL carrier).

[0396] The switching pattern may indicate / configure a periodicity of the first timer duration and / or a periodicity of the second time duration. The wireless device may determine occurrences of the first time duration based on the periodicity of the first timer duration and / or the length of the first time duration. The wireless device may determine occurrences of the second time duration based on the periodicity of the second time duration and / or the length of the second time duration.

[0397] FIG. 23A, FIG. 23B, and / or FIG. 23C shows that the DL switching may also comprise a DL switching gap (or a DL switching period or a DL switching duration or a DL switching window), e.g., with a length of Tswitch-DL(e.g., in ms / micro second / symbols or the like). For example, the one or more configuration parameters may configure / indicate the DL switching gap The DL switching (e.g., Rx switching for the LB CA, e.g., from the first Rx chain to the second Rx chain and vise versa) may be during the DL switching gap. During the DL switching gap, the wireless device may switch the antenna connector (with accordance to Case 1 or Case 2) and / or retune / recalibrate LO and / or LNA or mixer or filters (e.g., depending on the first option or the second option is used for the reference UE architecture for the LB CA operation via switching). For example, during the DL switching gap, the wireless device may not be able to perform UL / DL transmissions / receptions via the first carrier and DL receptions via the second carrier, e.g., no Rx / Tx on the first carrier and no Rx on the second carrier. The DL switching gap may comprise muted / blanked symbols for UL transmissions if UL frame timing of the first cell / first UL carrier overlap with the DL switching period. For example, the wireless device may avoid transmitting UL signals / chan nels during the muted / blanked symbols.

[0398] In some cases, the first set of capabilities may indicate the DL switching gap. For example, the first set of capabilities may indicate that the wireless device is capable of the LB CA operation via the switching.

[0399] The first set of capabilities may further indicate a UE architecture for the LB CA operation via switching, e.g., whether the UE architecture is based on the first option (Option 1 ) for the LB CA operation via switching or whether the UE architecture is based on the second option (Option 2) for the LB CA operation via switching.

[0400] The first set of capabilities may further indicate whether components of the RF Rx circuitry (e.g., LO / LNA or some filters) are exclusively dedicated for the DL receptions via the Carrier 2 or the DL receptions via the Carrier 1Docket No.: 25-1052PCT(e.g., whether the DL switching comprises actual switching in hardware from the first Rx chain to the second Rx chain and returning the RF Rx circuitry with accordance to Case 1 or Case 2), e.g., the first option for the UE architecture for the LB CA operation via switching, or are shared / common for the DL receptions via the Carrier 2 or the DL receptions via the Carrier 1, e.g., a single Rx chain is shared for the DL receptions via the Carrier 2 or the DL receptions via the Carrier land the switching may comprise returning the RF Rx circuitry with accordance to Case 1 or Case 2, e.g., the second option for the UE architecture for the LB CA operation via switching. When the components of the RF Rx circuitry (e.g., LO / LNA or some filters) are exclusively dedicated for the DL receptions via the Carrier 2 or the DL receptions via the Carrier 1 (e.g., the first option for the UE architecture for the LB CA operation via switching), the DL switching gap may be shorter / smaller than when components of the RF Rx circuitry (e.g., local oscillator LO / LNA or some filters) are shared / common for the DL receptions via the Carrier 2 or the DL receptions via the Carrier 1 (e.g., the second option for the UE architecture for the LB CA operation via switching).

[0401] The first set of capabilities may further indicate a value for the length of the DL switching gap (e.g., corresponding to the indicated UE architecture for the LB CA operation via switching). In some cases of some embodiments of the present disclosure, the wireless device may set / determine the length of the downlink switching gap TSwitch-DL based on / equal to the indicated value for the length of the DL switching gap via the first set of capabilities.

[0402] In some cases of some embodiments of the present disclosure, the base station may use the indicated value for the length of the DL switching gap via the first set of capabilities (received from the wireless device) to configure a value for the length of the DL switching gap. For example, the one or more configuration parameters (configuring the LB CA operation via switching) for the first cell may indicate / configure / comprise the value for the length of the DL switching gap. The wireless device may expect that the indicated DL switching gap via the one or more configuration parameters to be longer than or equal to the indicated / supported DL switching gap via the first set of capabilities.

[0403] Although the LB CA operation via switching is a UE-specific operation, because the UL frame timing (e.g., with respect to the DL frame timing of the first cell / first carrier and / or the DL frame timing of the second cel l / second carrier), the base station may set / determine the value / length of the DL switching gap based on a maximum / nominal round-trip transmission (RTT) delay in the first cell. For example, the length of the DL switching gap may be larger than a maximum value of the TA in the first cell and / or a value of a TA_offset (e.g., N_TAoffset) configured / indicated by the one or more configuration parameters corresponding to the first cell. When the length of the DL switching gap may be larger than the maximum value of the TA in the first cell and / or the value of TA_offset, the UL frame timing (e.g., with respect to the DL frame timing of the first cell / first carrier and / or the DL frame timing of the second cell / second carrier) obtained based on the TA command may not result in UL transmissions during the second time duration and / or the DL switching period.

[0404] FIG. 23A, FIG. 23B, and FIG. 23C show different implementations of the DL switching (e.g., the DL carrier switching). Other implementations of the DL switching are also possible although not shown in FIG. 23A, FIG. 23B, and FIG. 23C.Docket No.: 25-1052PCT

[0405] In the example of FIG. 23A, the DL switching gap is always located in / at a switch-from carrier, e.g., when switching from Case 2 to Case 1 the DL switching gap is located in the second carrier (e.g., when the SDL carrier is the switch-from carrier) and when switching from Case 1 to Case 2 the DL switching gap is located in the first carrier (e.g., when the FDD carrier is the switch-from carrier). As seen from FIG. 23A, a last / final / ending portion of each occurrence of the second time duration and the first time duration is allocated for the DL switching gap (e.g., to perform the DL switching).

[0406] Corresponding to the example of FIG. 23A, the first set of capabilities may indicate a capability / preference / support for locating the DL switching gap in the switch-from carrier, e.g., when switching from Case 2 to Case 1 the DL switching gap is located in the second carrier (e.g., when the SDL carrier is the switch-from carrier) and when switching from Case 1 to Case 2 the DL switching gap is located in the first carrier (e.g., when the FDD carrier is the switch-from carrier).

[0407] Alternatively, corresponding to the example of FIG. 23A, the one or more configuration parameters (for the LB CA operation via switching) may indicate the location of the DL switching gap in the switch-from carrier, e.g., when switching from Case 2 to Case 1 the DL switching gap is located in the second carrier (e.g., when the SDL carrier is the switch-from carrier) and when switching from Case 1 to Case 2 the DL switching gap is located in the first carrier (e.g., when the FDD carrier is the switch-from carrier).

[0408] In the example of FIG. 23B, the DL switching gap is always located in the second carrier, e.g., when switching from Case 2 to Case 1 the DL switching gap is located in the second carrier and when switching from Case 1 to Case 2 the DL switching gap is located in the second carrier. As seen from FIG. 23A, a last / final / ending portion of each occurrence of the second time duration is allocated for the DL switching gap (e.g., to perform the DL switching for switching from Case 2 to Case 1) and an initial / starting portion of each occurrence of the second time duration is allocated for the DL sw...

Claims

Docket No.: 25-1052PCTCLAIMSWhat is claimed is:

1. A method comprising:transmitting, by a wireless device to a base station, a capability message indicating a switching time between communication via one or more frequency division duple (FDD) carriers and a supplementary downlink (SDL) carrier; andreceiving, from the base station, a plurality of configuration parameters comprising:first configuration parameters indicating a primary cell configured with a first downlink carrier and a first uplink carrier;second configuration parameters indicating a secondary cell configured with a second downlink carrier; andthird configuration parameters indicating:a low band carrier aggregation (LBC A) switch operation between the primary cell and the secondary cell; anda duration of a switching gap for the switch operation from the secondary cell to the primary cell, wherein the duration is larger than or equal to a sum of a switching time and a timing advance (TA).

2. A method comprising:receiving, by a wireless device, one or more configuration parameters indicating a duration of switching gap for a low band carrier aggregation (LBCA) switch operation between a primary cell and a secondary cell, wherein the duration is based on a switching time between communication via one or more frequency division duple (FDD) carriers and a supplementary downlink (SDL) carrier.

3. The method of any one of claims 2, further comprising transmitting, by the wireless device to a base station, a capability message indicating the switching time between communication via the one or more FDD carriers and the SDL carrier4. The method of any one of claims 2 to 3, wherein the one or more configuration parameters further indicates that the primary cell is configured with a first downlink carrier and a first uplink carrier.

5. The method of claim 4, wherein the first uplink carrier is a paired uplink carrier for the first downlink carrier.

6. The method of any one of claims 2 to 5, wherein the one or more configuration parameters further indicate that the secondary cell is configured with a second downlink carrier.

7. The method of claim 6, wherein the second downlink carrier is without a paired uplink carrier.

8. The method of any one of claims 2 to 7, wherein the one or more configuration parameters comprise third configuration parameters indicating the LBCA switch operation between the primary cell and the secondary cell.Docket No.: 25-1052PCT9. The method of claim 8, wherein the third configuration parameters indicate the duration of switching gap for the switch operation from the secondary cell to the primary cell.

10. The method of claim 9, wherein the duration is larger than or equal to the switching time.

11. The method of any one of claims 9 to 10, wherein the duration is larger than or equal to a timing advance (TA).

12. The method of any one of claims 9 to 11 , wherein the duration is larger than or equal to a sum of the switching time and the TA.

13. The method of any one of claims 8 to 12, wherein the third configuration parameters indicate the duration of switching gap for the switch operation from the primary cell to the secondary cell.

14. The method of claim 13, wherein the duration is larger than or equal to the switching time.

15. The method of any one of claims 8 to 14, wherein the third configuration parameters indicate a switching pattern between the primary cell and the secondary cell.

16. The method of claim 15, wherein the switching pattern indicates Tx / Rx on the primary cell in a first time duration.

17. The method of claim 16, wherein the first time duration comprises a first number of slots.

18. The method of any one of claims 15 to 17, wherein the switching pattern indicates receptions on the secondary cell in a second time duration.

19. The method of claim 18, wherein the second time duration comprises a second number of slots.

20. The method of any one of claims 15 to 19, wherein a periodicity of the switching pattern is a first value.

21. The method of any one of claims 2 to 17, wherein the primary cell is an FDD carrier.

22. The method of any one of claims 2 to 21 , wherein the secondary cell is an SDL carrier.

23. The method of any one of claims 2 to 22, wherein the communication via the one or more FDD carriers comprises transmissions and receptions (Tx / Rx) on the one or more FDD carriers and no receptions on the SDL carrier.

24. The method of claim 23, wherein the communication via the one or more FDD carrier comprises a first operation mode of the LBCA switch operation.

25. The method of any one of claims 23 to 24, wherein the communication via the one or more FDD carrier corresponds to a first case (Case 1) of the LBCA switch operation.

26. The method of any one of claims 2 to 25, wherein the communication via the SDL carrier comprises receptions (Rx) on the SDL carrier and no transmissions and receptions (Tx / Rx) on the one or more FDD carriers.

27. The method of claim 26, wherein the communication via the SDL carrier comprises a second operation mode of the LBCA switch operation.

28. The method of any one of claims 26 to 27, wherein the communication via the SDL carrier corresponds to a second case (Case 2) of the LBCA switch operation.

29. The method of any one of claims 2 to 28, wherein the switching time, between communication via the one or more FDD carriers and the SDL carrier, comprises a length of the switching time between communication via the one or more FDD carriers and the SDL carrier.Docket No.: 25-1052PCT30. A method comprising:receiving, by a wireless device, one or more configuration parameters indicating:a primary cell configured with a first downlink carrier and an uplink carrier;a secondary cell configured with a second downlink carrier; anda low band carrier aggregation (LBCA) switch operation between the primary cell and the secondary cell; andtransmitting, via at least one resource, an uplink control channel with an acknowledgement for a downlink channel received via the secondary cell, wherein:the at least one resource of the uplink control channel starts no earlier than an uplink symbol starting after a timing gap after an end of a last symbol of the downlink channel; and the timing gap is determined based on a switching time for the LBCA switch operation.

31. The method of claim 30, wherein the one or more configuration parameters indicate a duration of switching gap for the switch operation between the secondary cell to the primary cell.

32. The method of claim 31 , wherein the switching time for the LBCA switch operation is equal the duration.

33. The method of any one of claims 30 to 32, further comprising switching from the secondary cell to the primary cell.

34. The method of any one of claims 30 to 33, further comprising receiving the downlink channel via the secondary cell.

35. The method of any one of claims 30 to 34, wherein the one or more configuration parameters indicate a switching pattern between the primary cell and the secondary cell.

36. The method of claim 35, wherein the switching pattern indicates transmissions and receptions (Tx / Rx) on the primary cell in a first time duration.

37. The method of claim 36, wherein the first time duration comprises a first number of slots.

38. The method of any one of claims 35 to 37, wherein the switching pattern indicates receptions on the secondary cell in a second time duration.

39. The method of claim 38, wherein the second time duration comprises a second number of slots.

40. The method of any one of claims 38 to 39, wherein the receiving the downlink channel is during the second time duration41. The method of any one of claims 36 to 40, wherein the transmitting the uplink control channel is during the first time duration.

42. The method of any one of claims 30 to 41, wherein the downlink channel is a physical downlink shared channel (PDSCH) carrying a transport block (TB).

43. The method of claim 42, wherein the acknowledgment is for the transport block.Docket No.: 25-1052PCT44. The method of any one of claims 30 to 43, wherein the uplink control channel is a physical uplink control channel (PUCCH).

45. The method of any one of claims 30 to 44, wherein the timing gap is based on a physical downlink shared channel (PDSCH) processing time.

46. The method of claim 45, wherein the timing gap is a summation of the PDSCH processing time and the switching time for the LBCA switch operation.

47. The method of any one of claims 30 to 46, wherein the transmitting the uplink control channel is based on the at least one resource of the uplink control channel starting no earlier than the uplink symbol starting after the timing gap after the end of the last symbol of the downlink channel.

48. The method of any one of claims 30 to 47, further comprising receiving, via the second cell, a downlink control channel scheduling a downlink channel reception.

49. An apparatus comprising:one or more processors; andmemory 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