Switching reference resource in low-band carrier aggregation with switching

The mechanism for efficient switching of reference resources in low-band carrier aggregation addresses inefficiencies by dynamically configuring BWPs and carrier aggregation, enhancing network performance and data throughput.

WO2026236667A2PCT designated stage Publication Date: 2026-11-12YI YUNJUNG +8
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/US2026/027378
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-08
Filing Date
2026-05-08
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing carrier aggregation techniques in low-band wireless communication networks face inefficiencies in switching reference resources, leading to suboptimal performance and resource utilization.

Method used

Implementing a mechanism for efficient switching of reference resources in low-band carrier aggregation by utilizing flexible bandwidth parts (BWPs) and dynamic configuration of carrier aggregation configurations, enabling adaptive resource allocation based on traffic load and device capabilities.

Benefits of technology

Enhances network performance by optimizing resource utilization and improving data throughput in low-band carrier aggregation scenarios.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure US2026027378_12112026_PF_FP_ABST
    Figure US2026027378_12112026_PF_FP_ABST
Patent Text Reader

Abstract

A method comprises receiving, by a wireless device, one or more first messages indicating a switching pattern of a carrier switching between a first cell and a second cell. The method further comprises receiving a second message indicating an activation of the second cell, and based on receiving the second message indicating the activation of the second cell, starting to apply the switching pattern.
Need to check novelty before this filing date? Find Prior Art

Description

Docket No.25-1079PCTTITLESwitching Reference Resource in Low-Band Carrier Aggregation with SwitchingCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 802,520, filed May 8, 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 fora bandwidth part.

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

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

[0022] FIG. 16A, FIG. 16B, FIG. 16C, and FIG. 16D illustrate example structures for uplink and downlink transmission.Docket No.25-1079PCT

[0023] FIG. 17 illustrates an aspect of an example embodiment according to the present disclosure.

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

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

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

[0027] FIG. 21 illustrates an aspect of an example embodiment according to the present disclosure.

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

[0029] FIGS. 23A and 23B illustrates an aspect of an example embodiment according to the present disclosure.

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

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

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

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

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

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

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

[0037] 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 givenDocket No.25-1079PCTLTE 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.

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

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

[0040] 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 toDocket No.25-1079PCTconfigure specific characteristics or may be used to implement certain actions in the device, whether the device is in an operational or non-operational state.

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

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

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

[0044] 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 bya 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.Docket No.25-1079PCT

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

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

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

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

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

[0050] 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 coverageDocket No.25-1079PCTarea 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.

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

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

[0053] FIG. 1B illustrates another example mobile communication network 150 in which embodiments of the present disclosure may be implemented. Mobile communication network 150 may be, for example, a PLMN run by a network operator. As illustrated in FIG. 1 B, 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.

[0054] 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 instancesDocket No.25-1079PCTrunning on dedicated or shared hardware, or as virtualized functions instantiated on a platform (e.g., a cloud-based platform).

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

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

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

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

[0059] 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 internetDocket No.25-1079PCTprotocol (IP) transport network. The gNBs 160 and / or the ng-eNBs 162 may be connected to the UEs 156 by means of a Uu interface. For example, as illustrated in FIG. 1B, gNB 160A maybe connected to the UE 156A by meansofa Uu interface. The NG, Xn, and Uu interfaces are associated with a protocol stack. The protocol stacks associated with the interfaces may be used by the network elements in FIG. 1 B to exchange data and signaling messages and may include two planes: a user plane and a control plane. The user plane may handle data of interest to a user. The control plane may handle signaling messages of interest to the network elements.

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

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

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

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

[0064] 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.Docket No.25-1079PCT

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

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

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

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

[0069] 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 acknowledgedDocket No.25-1079PCTmode (AM). Based on the transmission mode an RLC is operating, the RLC may perform one or more of the noted functions. The RLC configuration may be per logical channel with no dependency on numerologies and / or Transmission Time Interval (TTI) durations. As shown in FIG.3, the RLCs 213 and 223 may provide RLC channels as a service to PDCPs 214 and 224, respectively.

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

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

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

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

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

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

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

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

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

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

[0080] - 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;Docket No.25-1079PCT

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

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

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

[0084] 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 includes, for example:

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

[0086] - a broadcast channel (BCH) for carrying the MIBfrom the BCCH;

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

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

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

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

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

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

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

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

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

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

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

[0098] 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. TheseDocket No.25-1079PCTfour protocol layers include the PHYs 211 and 221, the MACs212 and 222, the RLCs213and 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.

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

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

[0101] 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 UE210 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., RRCJDLE), and RRC inactive 606 (e.g., RRCJNACTIVE).

[0102] In RRC connected 602, the UE has an established RRC context and may have at least one RRC connection with a base station. The base station may be similar to one of the one or more base stations included in the RAN 104 depicted in FIG. 1A, one of the gNBs 160 or ng-eNBs 162 depicted in FIG. 1B, the gNB 220 depicted in FIG. 2Aand FIG. 2B, or any other base station described in the present disclosure. The base station with which the UE is connected may have the RRC context for the UE. The RRC context, referred to as the UE context, may comprise parameters for communication between the UE and the base station. These parameters may include, for example: one or more AS contexts; one or more radio link configuration parameters; bearer configuration information (e.g., relating to a data radioDocket No.25-1079PCTbearer, signaling radio bearer, logical channel, QoS flow, and / or PDU session); security information; and / or PHY, MAC, RLC, PDCP, and / or SOAP 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.

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

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

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

[0106] Tracking areas may be used to track the UE at the CN level. The CN (e.g., the CN 102 or the 5G-CN 152) may provide the UE with a list of TAIs associated with a UE registration area. If the UE moves, through cell reselection, to a cell associated with a TAI not included in the list of TAIs associated with the UE registration area, the UE mayDocket No.25-1079PCTperform 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.

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

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

[0109] 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 SOAP. A gNB-DU may comprise the RLC, the MAC, and the PHY.

[0110] 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 Isa 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 maybe transmitted over the air interface on a carrier frequency. The F parallel symbol streams may be mixed using an FFT block before being processed by the IFFT block. This operation produces Discrete Fourier Transform (DFT)-precoded OFDM symbols and may be used by UEs in the uplink to reduce the peak to average power ratio (PARR). Inverse processing may be performed on the OFDM symbol at a receiver using an FFT block to recover the data mapped to the source symbols.

[0111] 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.Docket No.25-1079PCT

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

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

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

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

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

[0117] 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 theDocket No.25-1079PCTserving 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.

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

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

[0120] 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 (eg., subcarrier spacing and cyclic prefix length for the uplink BWP).

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

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

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

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

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

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

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

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

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

[0130] 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 aDocket No.25-1079PCTdownlink CC. For FDD, one or more uplink CDs 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.

[0131] 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 (PCC). In the uplink, the carrier corresponding to the PCell may be referred to as the uplink 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 (SCC). In the uplink, the carrier corresponding to the SCell may be referred to as the uplink SCC.

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

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

[0134] FIG. 10B illustrates an example of how aggregated cells may be configured into one or more PUCCH groups. A PUCCH group 1010 and a PUCCH group 1050 may include one or more downlink CCs, respectively. In the example of FIG. 10B, the PUCCH group 1010 includes three downlink CCs: a PCell 1011, an SCell 1012, and an SCell 1013. The PUCCH group 1050 includes three downlink CCs in the present example: a PCell 1051, an SCell 1052, and an SCell 1053. One or more uplink CCs may be configured as a PCell 1021, an SCell 1022, and an SCell 1023. One or more other uplink CCs may be configured as a primary SCell (PSCell) 1061, an SCell 1062, and an SCell 1063. Uplink control information (UCI) related to the downlink CCs of the PUCCH group 1010, shown as UC11031, UC11032, and UC11033, may be transmitted in the uplink of the PCell 1021. Uplink control information (UCI) related to the downlink CCs of the PUCCH group 1050, shown as 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 mayDocket No.25-1079PCTbecome overloaded. By dividing transmissions of UCI between the PCell 1021 and the PSCell 1061, overloading may be prevented.

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

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

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

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

[0139] 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 afterDocket No.25-1079PCTthe 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.

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

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

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

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

[0144] 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.Docket No.25-1079PCT

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

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

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

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

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

[0150] 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 configurationDocket No.25-1079PCTmay 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.

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

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

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

[0154] 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 orthogonalDocket No.25-1079PCTfrequency 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.

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

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

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

[0158] 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, miniDocket No.25-1079PCTslot, 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.

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

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

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

[0162] The three beams illustrated in FIG. 11 B may be configured for a UE in a UE-specific configuration. Three beams are illustrated in FIG. 11 B (beam #1 , beam #2, and beam #3), more or fewer beams may be configured. Beam #1 may be allocated with CSI-RS 1101 that may be transmitted in one or more subcarriers in an RB of a first symbol. Beam #2 may be allocated with CSI-RS 1102 that may be transmitted in one or more subcarriers in an RB of a second symbol. Beam #3 may be allocated with CSI-RS 1103 that may be transmitted in one or more subcarriers in an RB of a third symbol. By using frequency division multiplexing (FDM), a base station may use other subcarriers in a same RB (for example, those that are not used to transmit CSI-RS 1101) to transmit another CSI-RS associated with a beam forDocket No.25-1079PCTanother U E . 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.

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

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

[0165] FIG. 12A illustrates examples of three downlink beam management procedures: P1 , P2, and P3. Procedure P1 may enable a UE measurement on transmit (Tx) beamsofa 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.Docket No.25-1079PCT

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

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

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

[0169] A network (e.g., a gNB and / or an ng-eNB of a network) and / or the UE may initiate a random access procedure. A UE in an RRC_I DLE state and / or an 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 alignmentfor an SCell addition.Docket No.25-1079PCT

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

[0171] The configuration message 1310 may be transmitted, for example, using one or more RRC messages. The one or more RRC messages may indicate one or more random access channel (RACH) parameters to the UE. The one or more RACH parameters may comprise at least one of following: general parameters for one or more random access procedures (e.g., RACH-configGeneral); cell-specific parameters (e.g., RACH-Con figCommon) 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.

[0172] The one or more RACH parameters provided in the configuration message 1310 may indicate one or more Physical RACH (PRACH) occasions available for transmission of the Msg 1 1311. The one or more PRACH occasions may be predefined. The one or more RACH parameters may indicate one or more available sets of one or more PRACH occasions (e.g., prach-Configlndex). The one or more RACH parameters may indicate an association between (a) one or more PRACH occasions and (b) one or more reference signals. The one or more RACH parameters may indicate an association between (a) one or more preambles and (b) one or more reference signals. The one or more reference signals may be SS / PBCH blocks and / or CSI-RSs. For example, the one or more RACH parameters may indicate a number of SS / PBCH blocks mapped to a PRACH occasion and / or a number of preambles mapped to a SS / PBCH blocks.

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

[0174] The Msg 1 1311 may include one or more preamble transmissions (e.g., a preamble transmission and one or more preamble retransmissions). An RRC message may be used to configure one or more preamble groups (e.g.,Docket No.25-1079PCTgroup 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.

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

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

[0177] 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 maybe scheduled on the DL-SCH and indicated on a PDCCH using a random access RNTI (RA-RNTI). The Msg 21312 may indicate that the Msg 1 1311 was received by the base station. The Msg 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 / ora Temporary Cell RNTI (TC-RNTI). AfterDocket No. 25-1079PCTtransmitting 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:

[0178] RA-RNTI= 1 + sjd + 14 x tjd + 14 x 80 x fjd + 14 x 80 x 8 x ul_carrier_id, where sjd may be an index of a first OFDM symbol of the PRACH occasion (e.g., 0 < sjd < 14), tjd may be an index of a first slot of the PRACH occasion in a system frame (e.g., 0 s 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).

[0179] The UE may transmit the Msg 31313 in response to a successful reception of the Msg 2 1312 (e.g., using resources identified in the Msg 21312). The Msg 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).

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

[0181] 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. ForDocket No. 25-1079PCTrandom access in a cell configured with an SUL carrier, the network may indicate which carrier to use (NUL or SUL). The UE may determine the SUL carrier, for example, if a measured quality of one or more reference signals is lower than a broadcast threshold. Uplink transmissions of the random access procedure (e.g ., the Msg 1 1311 and / or the Msg 31313) may remain on the selected carrier. The UE may switch an uplink carrier during the random access procedure (e.g., between the Msg 1 1311 and the Msg 3 1313) in one or more cases. For example, the UE may determine and / or switch an uplink carrier for the Msg 1 1311 and / or the Msg 31313 based on a channel clear assessment (e.g., a listen-before-talk).

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

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

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

[0185] 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.Docket No. 25-1079PCT

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

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

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

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

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

[0191] 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 theDocket No.25-1079PCTPDCCH may be referred to as downlink control information (DC I) . In some scenarios, the PDCCH may be a group common PDCCH (GC-PDCCH) that is common to a group of UEs.

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

[0193] DCIs may be used for different purposes. A purpose may be indicated by the type of RNTI used to scramble the CRC parity bits. For example, a DCI having CRC parity bits scrambled with a paging RNTI (P-RNTI) may indicate paging information and / or a system information change notification. The P-RNTI may be predefined as "FFFE" in hexadecimal. A DCI having CRC parity bits scrambled with a system information RNTI (SI-RNTI) may indicate a broadcast transmission of the system information. The SI-RNTI may be predefined as “FFFF” in hexadecimal. A DCI having CRC parity bits scrambled with a random access RNTI (RA-RNTI) may indicate a random access response (RAR). A DCI having CRC parity bits scrambled with a cell RNTI (C-RNTI) may indicate a dynamically scheduled unicast transmission and / or a triggering of PDCCH-ordered random access. A DCI having CRC parity bits scrambled with a temporary cell RNTI (TC-RNTI) may indicate a contention resolution (e.g., a Msg 3 analogous to the Msg 31313 illustrated in FIG. 13A). Other RNTIs configured to the UE by a base station may comprise a Configured Scheduling RNTI (CS-RNTI), a Transmit Power Control-PUCCH RNTI (TPC-PUCCH-RNTI), a Transmit Power Control-PUSCH RNTI (TPC-PUSCH-RNTI), a Transmit Power Control-SRS RNTI (TPC-SRS-RNTI), 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.

[0194] 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 J may be used for notifying a group of UEs of a physical resource block and / or OFDM symbol where the UE may assume no transmission is intended to the UE. DCI format 2_2 may be used for transmission of a transmit power control (TPC) command for PUCCH or PUSCH. DCI format 2_3 may be used for transmission of a group of TPC commands for SRS transmissions by one or more UEs. DCI format(s) for new functions may be defined in future releases. DCI formats may have different DCI sizes, or may share the same DCI size.

[0195] 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 onDocket No.25-1079PCTresource 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).

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

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

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

[0199] 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 compriseDocket No.25-1079PCTdecoding 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)

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

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

[0202] 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 configuredDocket No. 25-1079PCTon an uplink BWP of a cell. A PUCCH resource set may be configured with a PUCCH resource set index, a plurality of PUCCH resources with a PUCCH resource being identified by a PUCCH resource identifier (e.g., pucch-Resourceid), and / or a number (e.g., a maximum number) of UCI information bits the UE may transmit using one of the plurality of PUCCH resources in the PUCCH resource set. When configured with a plurality of PUCCH resource sets, the UE may select one of the plurality of PUCCH resource sets based on a total bit length of the UCI information bits (e.g., HARQ-ACK, SR, and / or CSI). If the total bit length of UCI information bits is two or fewer, the UE may select a first PUCCH resource set having a PUCCH resource set index equal to “0”. If the total bit length of UCI information bits is greater than two and less than or equal to a first configured value, the UE may select a second PUCCH resource set having a PUCCH resource set index equal to "1”. If the total bit length of UCI information bits is greater than the first configured value and less than or equal to a second configured value, the UE may select a third PUCCH resource set having a PUCCH resource set index equal to “2”. If the total bit length of UCI information bits is greater than the second configured value and less than or equal to a third value (e.g., 1406), the UE may select a fourth PUCCH resource set having a PUCCH resource set index equal to "3”.

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

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

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

[0206] 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 maybeDocket No.25-1079PCTprovided 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.

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

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

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

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

[0211] 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 / orDocket No.25-1079PCTtransistor 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.

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

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

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

[0215] 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 ofDocket No.25-1079PCTcoded 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.

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

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

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

[0219] A base station may support a plurality of downlink frequency bands. The base station may config ure / operate a carrier in each of the plurality of downlink frequency bands. For example, the base station may support a first frequency band (e.g., n5, frequency range in 850 MHz). The base station may supporta second frequency band (e.g., n29, frequency range of 717 MHz to 728 MHz). A wireless device may support the first frequency band or the second frequency band. The wireless device may not support simultaneous reception via the first frequency band and theDocket No.25-1079PCTsecond frequency band. The wireless device may support reception via the first frequency band or the second frequency band at a time duration.

[0220] In an example, the base station may configure a carrier aggregation, of a first carrier of the first frequency and a second carrier of the second frequency, to the wireless device. The base station and the wireless device may communicate via the first carrier or the second carrier at a time duration based on a time-domain multiplexing (TDM) mechanism / pattern. 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 low-band (LB) carrier aggregation (CA) with switching, a LB-CA switching, a Carrier Switching, a carrier aggregation via switching, CA with switching, a TDM-ed CA, PCell carrier switching, DL / SDL, a CA with SDL, a CA with DL / SDL, a serving cell with DL / SDL, etc.

[0221] FIG. 17 illustrates an example as per an aspect of an embodiment of the present disclosure. A base station (BS #120) may operate in a first frequency band and a second frequency band. The first frequency band may be a FDD band, where a downlink spectrum and an uplink spectrum are paired. The second frequency band may be a supplementary downlink band, a supplementary FDD band, or a downlink only FDD band, where only a downlink spectrum may be available. The first frequency band may be different from the second frequency band. BS #120 may configure a first carrier (Carrier#01730) in the first frequency band. The first carrier (Carrier#01730) may be a downlink carrier. BS #120 may configure a second carrier (Carrier #1 1740) in the second frequency band. The second carrier (Carrier #1 1740) may be a downlink carrier. BS #120 may configure an uplink carrier (Carrier#01730) in the first frequency band. The first carrier (Carrier#01730) may comprise the downlink carrier and the uplink carrier. BS #120 may configure a first cell that is a serving cell for a wireless device (UE #110). The first cell may comprise the first carrier and the uplink carrier. BS #120 may configure a second cell that is a serving cell for the wireless device. The second cell may comprise the second carrier. The first cell may be same as the second cell. In the example, the first carrier and the second carrier may be associated with a single serving cell. The first cell and the second cell may be different. In the example, the first cell is associated with the first carrier and the uplink carrier. The second cell is associated with the second carrier. The first cell may be a primary cell of a cell group (e.g., sPCell), a primary cell or a secondary cell. The second cell may be a secondary cell. The first cell and the second cell may belong to a same cell group (e.g., a master cell group or a secondary cell group). The first cell and the second cell may belong to a same timing advance group (TAG). The first cell and the second cell may be configured with one or more PUCCH cells, wherein the one or more PUCCH cells, commonly, are used for the first cell and the second cell. The first cell and the second cell may be configured as a carrier aggregation to the wireless device. The first cell and the second cell may be inter-band carrier aggregation. The first cell and the second cell may be configured with a low-band carrier aggregation based on a switching (e.g., LB-CA with switching, LB-CA switching, LB-CA via switching, LB-CAS, CA with switching, Switching based LB-CA, switching-LB-CA, etc).

[0222] The wireless device (UE #110) may not support simultaneous reception via the first carrier / cell and the second carrier / cell. The wireless device (UE #110) may not support simultaneous transmission via the first carrier / cell and reception via the second carrier / cee. The wireless device (UE #110) may not support simultaneous reception via theDocket No. 25-1079PCTfirst carrier / cell and transmission via the second carrier / cell. The wireless device (UE #110) may not support simultaneous transmission via the first carrier / cell and transmission via the second carrier / cell. The wireless device may tune its RF to either the first carrier / cell or the second carrier / cell at a given time (e.g., a slot). BS #120 may configure / indicate a TDM pattern (e.g., a carrier switching pattern, a LB-CA switching pattern, a LB-CA pattern, CA-switching-pattern) (e.g., tdm-pattern-carrier-switching). For example, the wireless device (UE #110) may be configured to switch between a first case (e.g., Case 1 1703 in FIG. 17) and a second case (e.g., Case 2 1705 in FIG. 17) based on the TDM pattern (e.g., the carrier switching pattern, the LB-CA switching pattern, the LB-CA pattern, CA-switching-pattern). For example, the wireless device and the base station may apply / use the first case during a first plurality of time durations (e.g., first time durations 1707 in FIG. 17) of the TDM pattern (e.g., the carrier switching pattern). For example, the first plurality of time durations (hereinafter, first time durations 1707) may comprise a slot n and a slot n+2 in FIG. 17. UE #110 may be expected to or may communicate with BS #120 via Carrier #0130 during the first time durations 1707.

[0223] The wireless device and the base station may apply / use the second case (Case 2 1705) during a second plurality of time durations (e.g., second time durations 1709) of the TDM pattern (e.g., the carrier switching pattern). For example, the second plurality of time durations (hereinafter second time durations 1709) may comprise slot n+1 and slot n+3 in FIG. 17. UE #110 may be expected to or may be configured to or may communicate with BS #120 via Carrier #1 1740 during the second time durations 1709.

[0224] Based on the TDM pattern (e.g., the carrier switching pattern), the first plurality of time durations and the second plurality of time durations may not overlap in time. For example, a time duration 101 may be a slot based on a subcarrier spacing (SCS) of the first cell or the first carrier. For example, the time duration 101 may be k1 slot(s) based on a SCS of the first carrier, based on a SCS of an active BWP of the first carrier, based on a reference SCS configured for the TDM pattern (e.g., the carrier switching pattern), based on a SCS of the second carrier, based on a smallest subcarrier spacing of one or more SCSs of the first carrier / cell, based on a SCS of an active BWP of the second carrier, and etc. In an example, the one or more messages may indicate a parameter (e.g., CSPatiernDuration) of the k1 (e.g., a size of a time duration in the TDM pattern / CS pattern).

[0225] Based on the first case (in Case 1 1703, or in Case 1), the wireless device may be configured / expected / required to (or may perform) receive downlink signals via the first carrier and transmit uplink signals via the uplink carrier. In Case 1 1703, UE #110 may be configured expected / required to (or may perform) receive and transmit signals via Carrier #0130. Based on the first case (in Case 1), the wireless device may be further configured / expected / required not to (or may not perform) receive downlink signal(s) via the second carrier / Carrier #1 1740.

[0226] Downlink signals may comprise one or more: synchronization signal and physical broadcast channel block (SSB), channel state information reference signal (CSI-RS), physical downlink control channel (PDCCH), downlink control information (DCI), DCI format, physical downlink shared channel (PDSCH), downlink data, data modulationDocket No.25-1079PCTreference signal (DM-RS), physical broadcast channel (PBCH), a low-power wakeup signal, a low-power synchronization signal, a paging early indication (PEI), downlink RS and / or channels and / or signals, etc.

[0227] Uplink signals may comprise one or more of: physical uplink control channel (PUCCH), uplink control information (UCI), CSI feedback / report, scheduling request (SR), physical uplink shared channel (PUSCH), uplink data, sounding reference signal (SRS), DM-RS, a first PUCCH for an UE-initiated beam report, a second PUCCH I a second PUSCH for the UE-initiated beam report, a PRACH, Msg3 PUSCH, Msg A PUSCH, msg1, msgA, a wake-up signal, uplink RS and / or channels and / or signals, etc.

[0228] Based on the second case (in Case 21705, in Case 2), the wireless device may be configured / expected / required not to (or may not perform) receive downlink signals via the first carrier / cell and may be configured / expected / required not to (or may not perform) transmit uplink signals via the first carrier / cell. In Case 21705, UE #110 may be configured to skip reception and transmission via Carrier #01730. Based on the second case (in Case 21705), the wireless device may be further configured / expected / required to (or may perform) receive downlink signal(s) via the Carrier #1 1740. In Case 21705, UE #110 may be configured to perform receiving downlink signals via Carrier#1 1740.

[0229] In the example, the wireless device may not perform any of the Case 1 or Case 2 during a switching time (e.g., LB-CA switching latency, LB-CA switching gap / delay, CA switching gap / latency / delay, switching gap / latency / delay, retuning gap / latency / delay, RF tuning gap / delay / latency, etc.) to switch from Case 1 to Case 2 or from Case 2 to Casel . The switching time may not overlap, in time, with the first time duration or the second time duration.

[0230] Alternati vely / additional ly / optional ly, if a wireless device supports simultaneous operation via the first carrier / cell and the second carrier / cell at a same time, a carrier switching between the first carrier of the first cell and the second carrier of the second cell may refer that the wireless device may perform Case 1 and Case 2 simultaneously where a TDM pattern / CS pattern may not be configured. In such a case, the first cell and the second cell are the same. Example embodiments of the specification may apply to such a case without applying the TDM / CS pattern between the first carrier and the second carrier of a same cell.

[0231] In the specification, a carrier may refer a downlink carrier or an uplink carrier or a paired carrier in a FDD band, an unpaired carrier in a TDD band. A cell may refer a serving cell. A cell may be configured with a downlink carrier, or a downlink carrier and an uplink carrier, or a downlink carrier and a supplementary downlink carrier and an uplink carrier, or a downlink carrier and an uplink carrier and an supplementary uplink carrier, or a downlink carrier and a supplementary downlink carrier and an uplink carrier and an supplementary uplink carrier. The cell may comprise zero, one or more of downlink carrier and zero, one or more uplink carriers.

[0232] In the specification, a wireless device may determine ‘A based on a TDM pattern (e.g., a carrier switching pattern) may refer at least one of: a) the wireless device may determine 'A' based on a carrier switching between the first carrier and the second carrier b) the wireless device may determine ‘A’ based on the first carrier and the second carrier being configured with a carrier switching; c) the wireless device may determine ‘A based on the first carrier andDocket No.25-1079PCTthe second carrier being associated with the first cell; d) the wireless device may determine 'A' based on the first carrier and the second carrier being associated with non-simultaneous carrier aggregation; e) the wireless device may determine 'A' based on the first carrier and the second carrier being configured with cross-carrier scheduling each other; f) the wireless device may determine 'A' based on the first carrier being enabled with a cross-carrier scheduled by the second carrier and the second carrier being enabled with a cross-carried scheduled by the first carrier; g) the wireless device may determine 'A' based on a TDM-ed / carrier-switching PDCCH monitoring across the first carrier and the second carrier; h) the wireless device may determine ‘A’ based on a PDCCH carrier switching, etc.

[0233] In the specification, a scheduling carrier / cell may refer a carrier / cell, where the wireless device monitors PDCCH candidates to receive DCIs. A scheduled carrier / cell may refer a carrier / cell, where the wireless device receives PDSCHs scheduled by the DCIs or transmits PUSCHs / PUCCHs scheduled by the DCIs. A cross-carrier scheduling may refer that the scheduling carrier / cell maybe 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.

[0234] In the specification, a bandwidth part may refer a contiguous set of frequency region within a carrier. A BWP of the carrier may be configured with a subcarrier spacing, and a starting PRB and a bandwidth of the BWP.

[0235] In the specification, a carrier may refer configuration parameters to receive downlink control channels and / or downlink data channels where the configuration parameters may be common to (or applied across) one or more BWPs of the carrier. The carrier may comprise the one or more BWPs. Each BWP of the one or more BWPs may comprise additional configuration parameters to receive downlink control channels and / or downlink data channels.

[0236] In the specification, 'A' indicates 'B' may refer that ‘A’ comprises parameter(s) indicating ‘B’ . A comprises ‘B’ IE may indicate that ‘A’ comprises / indicate value(s) corresponding to parameter(s) comprised in / of ‘B’ information element.

[0237] In an example, the carrier aggregation (e.g., the Carrier Switching) between the first carrier and the second carrier may be configured to the wireless device based on a first configuration option (e.g., Configuration 1) or a second configuration option (e.g., Configuration 2). With the first configuration option, the first carrier and the second carrier may be associated with a single serving cell (e.g., the first cell). Based on the first configuration option or when the first configuration option is used, the second cell may be same to the first cell. In the example, the first cell may be configured with the first (downlink) carrier and the second (downlink) carrier. With the second configuration option, the first carrier may be associated with a first serving cell and the second carrier may be associated with a second serving cell. The first (downlink) carrier may be configured for the first cell. The second (downlink) carrier may be configured for the second cell. In the second configuration option, the first cell may be different from the second cell. For example, a first serving cell index of the first cell may be different from a second serving cell index of the second cell.

[0238] FIGs. 18A and 18B illustrates the first configuration option (Configuration 1) and the second configuration option (Configuration 2) respectively. In the examples, BS #120 may operate / conf igu re the first carrier of the first cell and the second carrier of the second cell to UE #110. The first cell may be same as the second cell (e.g., with theDocket No.25-1079PCTConfiguration 1) or may be different from the second cell (e.g., with the Configuration 2). The first cell may be a primary cell or a secondary cell. The second cell, when different from the first cell, may be a secondary cell.

[0239] In an example, one or more first SCSs associated with the first cell (or the first carrier) may be same as one or more second SCSs associated with the second cell (or the second carrier). A first SCS of an active downlink BWP of the first carrier may be same as a second SCS of an active downlink BWP of the second carrier. A first BWP index of the active downlink BWP of the first carrier may be same as a second BWP index of the active downlink BWP of the second carrier.

[0240] Process 1801 of FIG. 18A illustrates an example embodiment of the Carrier Switching (e.g , the LB-CA with switching, LB-CA based on switching, etc) based on the first configuration option (Configuration 1). In the example, the second cell is same as the first cell. The first carrier and the second carrier may be associated with the first cell. UE #110 may receive message(s) 1852. Message(s) 1852 may be transmitted via a SIB1, one or more SIBx and / or RRC signaling e.g., from BS #120. UE #110 may receive message(s) 1852 via the first carrier of the first cell. The message(s) 1852 may comprise / indicate configuration parameters (e.g., ServingCellConfigCommon and / or ServingCellConfig, a serving cell config 1861) for / of the first cell. The configuration parameter (the serving cell config 1861) may indicate parameters (one or more first configuration parameters of a downlink carrier 1863, hereinafter 'first carrier config’) for the first carrier that is associated with / operating in a first frequency band. The first carrier may transmit cell-defining synchronization signal and physical broadcast channel (PBCH) block(s) (SSB(s)) (CD-SSB(s)). The first carrier may be configured with CD-SSB(s). A CD-SSB may refer a SSB that is transmitted via a channel raster of the first frequency band. The CD-SSB may comprise parameters indicating an initial downlink BWP of the first carrier / first cell. The CD-SSB may comprise parameters indicating a coreset with an index = 0 (e.g., coreset#0). The CD-SSB of the first carrier may be configured / indicated / scrambled with a first cell identifier (e.g., physcellld in ServingCellConfigCommon IE of the first cell or obtained during an initial access / cell search of the first cell) and a first center frequency (e.g., absoluteFreguencySSB in ServingCellConfigCommon IE or obtained during the initial access / cell search of the first cell). The first cell identifier may identify the first cell. For example, when the first cell is connected to UE #110 via an initial access, UE #110 may obtain the first cell identifier and the first center frequency via a cell search. For example, the configuration parameters may comprise the first cell identifier and the first center frequency (e.g., during handover, a scell addition, a secondary cell group addition, etc.).

[0241] The configuration parameters may, further, indicate parameters (one or more second configuration parameters of a supplementary downlink carrier 1865, hereinafter ‘second carrier config’) for the second carrier that is associated with / operating in a second frequency band. The second carrier may transmit non-cell-defining SSB(s) (NC D-SSB(s)) identifying a second cell identifier (additionalPCI in ServingCellConfig IE of the first cell, or add-physcellld in ServingCellConfigCommon IE) and a second center frequency (absolutePrequencySSB-additionalPCI in ServingCellConfig IE of the first cell). The second carrier config may comprise / indicate the second cell identifier and the second center frequency. An NCD-SSB may be transmitted via a non-channel raster of the second frequency band. An NCD-SSB may notindicate a scheduling information about a coreset with an index = 0 (e.g., coreset#0) for the secondDocket No.25-1079PCTcarrier. UE #110 may identify the NCD-SSB(s) of the second carrier, based on the configuration parameters. UE #110 may not obtain a SIB1 of the second carrier via the NCD-SSB(s). UE #110 may receive one or more RRC signaling comprising / indicating parameters of the SIB1 of the second carrier. For example, the second carrier may not transmit SIB1 messages. Based on the first carrier and the second carrier being associated with the first cell, parameters broadcasted via SIB1 of the first carrier or configuration parameters signaled for SIB1 parameters of the first carrier may be applied to the second carrier. Parameters of the first carrier SIB1 message may be applied to both the first carrier and the second carrier.

[0242] In the example, the first (downlink) carrier may be referred as a normal downlink carrier, a non-SDL carrier, a non-supplementary downlink carrier, a non-supplementary DL carrier, a downlink carrier, and / or the like. The second (downlink) carrier may be referred as a supplementary downlink carrier, an SDL carrier, an additional carrier, a nonnormal DL carrier, a non-normal downlink carrier, a unpaired downlink carrier, and / or the like.

[0243] In the example, the second cell identifier may be different from (or may be same) the first cell identifier. The second center frequency would be different from the first center frequency based on the first frequency band being different from the second frequency band. The configuration parameters may further indicate an uplink carrier of the first frequency band. The uplink carrier may be configured with a set of random access resources. The wireless device may receive, via the second carrier and a first PDSCH, a transport block (TB). The TB (or the first PDSCH) may be associated with a HARQ process. The first PDSCH carrying the TB may be scrambled based on the second cell identifier based on the first PDSCH being received via the second carrier. The wireless device may receive, via the first carrier, and a second PDSCH, the TB, that is associated with the HARQ process. A PDSCH carrying the TB may be scrambled based on the first cell identifier based on the second PDSCH being received via the first carrier. The HARQ process may be associated with the first cell and / or the first carrier of the first cell and / or the second carrier of the first cell or both the first carrier and the second carrier of the first cell. The wireless device may transmit uplink signals via the first cell using / based on the first cell identifier (e.g. , a PUSCH comprising the uplink signals may be scrambled using the first cell identifier). The first carrier and the second carrier may be linked for a carrier switching based on the first cell comprising the first carrier and the second carrier (or the first carrier and the second carrier being associated with a single serving cell / the first cell).

[0244] The configuration parameters (serving cell config 1861), for the first cell, may comprise one or more of followings.

[0245] A) the first cell identifier for the first carrier; and the second cell identifier for the second carrier; the first center frequency for the first carrier and the second center frequency for the second carrier. The first cell identifier may be used for a cell index / ID of the first cell. UE #110 may receive a DCI scrambled with a broadcast RNTI (such as system information RNTI (SI-RNTI), paging RNTI (P-RNTI), a random access RNTI (RA-RNTI)) based on the first cell identifier. UE #110 may receive one or more PDCCH candidates and / or DCI(s) via the one or more PDCCH candidates of a common search space (CSS) based on the first cell identifier. UE #110 may receive a DCI with a temporary cell RNTI (TC-RNTI) based on the first cell identifier. The second cell identifier of the first cell may be referred as ‘additional cellDocket No.25-1079PCTindex', ‘additional physical cell identifier1. UE #110 may receive a DCI, scrambled with a cell-RNTI (C-RNTI), via the second carrier based on the second cell identifier. UE #110 may receive a DCI, scrambled with the C-RNTI, via the first carrier based on the first cell identifier. UE #110 may use / consider the first cell identifier for downlink signals via the first carrier. UE #110 may use / consider the second cell identifier for downlink signals via the second carrier.

[0246] B) the first carrier config (the parameters of the first carrier, the one or more first configuration parameters of the downlink carrier 1863): The first carrier config may be received via downlinkConfigCommon via DownlinkConfigCommon IE comprised in a ServingCellConfigCommon IE of the first cell and / or downlinkConfig via DownlinkConfig IE comprised in a ServingCellConfig of the first cell. For example, the first carrier config may comprise / indicate a first initial downlink BWP of the first carrier, and / or parameters for receiving downlink control channels and / or downlink data channels via the first carrier. The first carrier config may be received via one or more broadcast message (e.g., SSB, MIB, SIB1 , SIBx, etc.). In the example, the first carrier may be referred as a normal downlink carrier of a serving cell, a downlink carrier of a serving cell, a serving cell, a cell, a paired downlink carrier of a serving cell, etc. In the example, downlinkConfigCommon may indicate common downlink configuration parameters of the serving cell, including the frequency information configuration and the initial downlink BWP common configuration. The parameters provided herein should match the parameters configured by MIB and SIB1 (if provided) of the serving cell, with the exception of controlResourceSetZero and searchSpaceZero which can be configured in ServingCellConfigCommon even if MIB indicates that they are absent.

[0247] C) the second carrier config (the parameters of the second carrier, the one or more second configuration parameters of the supplementary downlink carrier 1865): The second carrier config may be received via supplementarydownlinkConfigCommon via DownlinkConfigCommon IE comprised in the ServingCellConfigCommon IE of the first cell and / or supplementarydownlinkConfig via DownlinkConfig IE comprised in the ServingCellConfig of the first cell. For example, the second carrier (e.g., supplementarydownlinkConfigCommon, and / or supplementarydownlinkConfig) may comprise / indicate a second initial downlink BWP (e.g., supplementaryinitialDownlinkBWP via Downlink-ConfigCommon IE) of the second carrier, and / or parameters for receiving downlink control channels and / or downlink data channels via the second carrier. When the first cell is configured with the first carrier and the second carrier, this parameter / IE may be configured. Based on the presence or absence of the supplementarydownlinkConfigCommon (or the second downlink configuration common) and / or the second cell identifier (as in A), the wireless device may determine whether the first cell is associated with the first carrier (e.g., when the supplementarydownlinkConfigCommon is absent in the first cell configuration) or the first cell is associated with the first carrier and the second carrier (e.g., when the supplementarydownlinkConfigCommon is present in the first cell configuration). The second carrier may be referred as a supplementary downlink carrier of a serving cell, a supplementary downlink carrier of a serving cell, an additional serving cell, an additional carrier of a serving cell, an additional carrier of a cell, a supplementary downlink carrier of a cell, etc.

[0248] D) parameters for the uplink carrier of the first cell: The parameters of the uplink carrier may be received via uplinkConfigCommon via UplinkConfigCommon IE comprised in the ServingCellConfigCommon IE of the first cellDocket No.25-1079PCTand / or uplinkConfig via UplinkConfig IE comprised in the ServingCellConfig of the first cell. Additionally, if the first cell is configured with a supplementary uplink carrier, supplementaryuplinkConfigCommon and / or supplementaryuplinkConfig may be provided. For example, the parameters of the uplink carrier may comprise / indicate an initial uplink BWP of the uplink carrier, and / or parameters for transmitting uplink control channels and / or uplink data channels via the uplink carrier. The parameters of the uplink carrier may indicate the set of random access resources.

[0249] In the example, the uplink carrier may be paired with the first carrier. Frequency of the uplink carrier is a paired uplink spectrum of the first carrier in the first frequency band. The uplink carrier and the first carrier may be associated with the first cell. The uplink carrier may be a non-supplementary uplink carrier. The uplink carrier and the first carrier may be referred as the first cell. The uplink carrier and the first carrier may be referred as 'paired' spectrum. The uplink carrier may be referred as a paired uplink carrier to a normal downlink carrier of a serving cell, an uplink carrier of a serving cell, etc.

[0250] E) one or more configuration parameters for SSB(s) of the first carrier (e.g. , ssb-PositionsinBurst, ssb-periodicityServingCell). The wireless device may determine a periodicity and / or one or more SSBs of the first carrier based on the one or more configuration parameters for the SSB(s). The one or more configuration parameters for SSB(s) of the first carrier may comprise one or more of: the first cell identifier, the first center frequency, a first periodicity of the CD-SSB(s) (ssb-periodicityServingCell), and time domain resources of the CD-SSB(s) (ssb-PositionsinBurst).

[0251] F) one or more second configuration parameters for SSB(s) of the second carrier (e.g., additional-ssb-PositionsinBurst, additional-ssb-periodicityServingCell, or ssb-PositionslnBurst2, ssb-periodicityServingCell2). The wireless device may determine a second periodicity and / or one or more second SSBs (NCD-SSB(s)) (e.g., determine positions / resources, mapping, indexes of the one or more second SSB(s) of the second carrier based on the one or more second configuration parameters for SSB(s) of the second carrier. When the one or more second configuration parameters for SSB(s) of the second carrier are absent (or are not configured via the first cell configuration), the. wireless device may determine / apply the one or more configuration parameters for SSB(s) (CD-SSB(s)) of the first carrier to determine the second periodicity and / or the one or more second SSB(s) of the second carrier. More specifically, the wireless device may determine that the first periodicity of the CD-SSB(s) of the first carrier may be same to the second periodicity of the NCD-SSB(s) of the second carrier. The wireless device may determine a number of transmitted CD-SSB(s), of the first carrier and in a SSB burst, is same to a number of NCD-SSB(s), of the second carrier and in a SSB burst. The wireless device may determine time domain positions / resources (e.g., symbol / slot index of each NCD-SSB) of NCD-SSB(s) of the second carrier as same to positions / resources of CD-SSB(s) of the first carrier.

[0252] G) a starting DM-RS symbol index (e.g., dmrs TypeA position, dmrs-TypeA-Position) for the first carrier: this parameter may indicate a starting symbol index of a DM-RS, based on a type A of a PDSCH transmission, for a PDSCH / PUSCH received / transmitted via the first carrier / uplink carrier respectively. In the example, the CD-SSB(s) of the first carrier may indicate a first starting DM-RS symbol index (e.g., dmrs-TypeA-Position), where the first startingDocket No.25-1079PCTDM-RS symbol index may be broadcasted via the MIB (master information block) of the CD-SSB(s). UE #110 may determine the first starting DM-RS symbol index being same as the starting DM-RS symbol index. The parameter may indicate either ‘pos2’ (starting from a OFDM symbol with index 2 (e.g., third OFDM symbol in a slot)) or 'pos3' (starting from a OFDM symbol with index 3 (e.g., fourth OFDM symbol in a slot)). The parameter may indicate position of (first) DM-RS for downlink via the first carrier. UE #110 may determine a DM-RS pattern I position of downlink signal(s) via the first carrier based on the starting DM-RS symbol index. Additional ly / optional ly, a second starting DM-RS symbol index (e.g., a second DM-RS typeA, dmrs-TypeA-Position2) may be configured, via the ServingCellConfigCommon (1861) of the first cell, for the second carrier. If the second starting DM-RS symbol index is not present / configured via the first cell configuration, the wireless device may apply the starting DM-RS symbol index for both the first carrier and the second carrier. If the second starting DM-RS symbol index indicates a value, the wireless device may use the value to determine a DM-RS pattern / position for downlink signal(s) via the second carrier. In an example, the NCD-SSB(s) of the second carrier may indicate a third starting DM-RS symbol index (e.g., dmrs-TypeA-Position in MIB of the second carrier). MIB of the second carrier, carried via the NCD-SSB(s) may indicate the third starting DM-RS symbol index. In the example, if the second starting DM-RS symbol index is different from the third starting DM-RS symbol index, UE #110 may determine / apply the second starting DM-RS symbol index for receiving downlink data channels via the second carrier. In the example, if the starting DM-RS symbol index is different from the third starting DM-RS symbol index, UE #110 may determine / apply the starting DM-RS symbol index for receiving downlink data channels via the second carrier. In an example, a duration of a coreset of the second carrier may not exceed the starting DM-RS symbol index (e.g., the duration may be smaller or equal to the starting DM-RS symbol index) based on the carrier switching between the first carrier and the second carrier. For example, the duration of 3 (e.g., 3 symbols) may be configured when the starting DM-RS symbol index indicating ‘pos3’. Otherwise, the duration may be one of {1 , 2}. In an example, the second carrier, based on the supplementary downlink carrier, may not broadcast MIB. In an example, UE #110 may ignore MIB of the second carrier based on the second carrier being the supplementary downlink carrier of the first cell.

[0253] In an example, either with the first configuration option (Configuration 1) or with the second configuration option (Configuration 2), a first subcarrier spacing common (e.g., subCarrierSpacingCommon), in the MIB of the CD-SSB(s) of the first carre of the first cell, may be same as a second subcarrier spacing common (e.g., subCarrierSpacingCommon), in the MIB of the NCD-SSB(s) of the second cell. In an example, a first parameter (e.g., dmrs-TypeA-Position, cellBarred), in the MIB of the CD-SSB(s) of the first carrier of the first cell, maybe same as a second parameter (e.g., dmrs-TypeA-Position), in the MIB of the NCD-SSB(s) of the second carrier of the second cell. In an example, NCD-SSB(s) of the second carrier may not schedule a coreset#0 of the second carrier. For example, a pdcch-ConfigSIB1 of the MIB of the NCD-SSB(s) of the second carrier may indicate a field of ssb-SubcarrierOffset as a value indicating that SIB1 is absent. The field pdcch-ConfigSIB1 of the MIB of the second carrier may indicate the frequency positions where the UE may find SS / PBCH block with SIB1 or the frequency range where the network does not provide SS / PBCH block with SIB. For example, the field pdcch-ContigSIB1 of the MIB of the second carrier may indicate the first center frequency of the CD-SSB(s) of the first carrier.Docket No.25-1079PCT

[0254] H) a second synchronization signal (SSS) power (e.g., ss-PBCH-BlockPower): Average EPRE of the resources elements that carry secondary synchronization signals (SSS) in dBm that the base station used for a CD-SSB transmission via the first carrier. Additionally / optionally, a second SSS power (e.g., additional-ss-PBCH-BlockPower, or ss-PBCH-BlockPower2) may be configured / indicated for the second carrier. When the second SSS power is provided, the wireless device may use the second SSS power for determining a power for a NCD-SSB transmission via the second carrier. When the second SSS power is not provided, the wireless device may use the SSS power, of the first carrier, for determining a power for a SSB transmission via the second carrier. The ServingCellConfigCommon of the first cell may indicate the first SSS power (e.g., ss-PBCH-BlockPower) used for the CD-SSB(s) of the first carrier and the second SSS power (e.g., additional-ss-PBCH-BlockPower) used for the NCD-SSB(s) of the second carrier. In an example, the first SSS power may be comprised in the ServingCellConfigCommon (e.g., cell common parameters) of the first cell. The second SSS power may be comprised / configured in the ServingCellConfig (e.g., UE-specific cell-common parameters) of the first cell.

[0255] I) the TDM pattern (e.g., the carrier switching pattern) (e.g., tdm-pattern-carrier-switching) between the first carrier and the second carrier: in an example, a bitmap maybe provided where a first value (e.g., ‘0’ or '1') of a bit of the bitmap may indicate that the wireless device performs the Case 1 (the first case) via a corresponding slot determined based on an index of the bit in the bitmap, and a second value (e.g., '1' or '0') of the bit of the bitmap may indicate that the wireless device performs the Case 2 (the second case) during the corresponding slot. A slot may be referred as a time duration, a time window, a time occasion, a TDM slot, a TDM unit, etc. The wireless device may determine the corresponding slot based on a size / periodicity of the bitmap and the index of the bit in the bitmap. For example, if the size / periodicity of the bitmap is 20 (or 20mec) and the index is 4, the corresponding slot may be 4thslot in every 20msec (e.g., SEN = 0 with slot index = 3, SEN = 2 with slot index = 3, SEN =4 with slot index = 3, etc.). In an example, the TDM pattern (e.g., the carrier switching pattern) may be provided via a set of {a starting slot, a starting symbol, an ending slot, an ending symbol, a periodicity). For example, the wireless device may determine one or more first time durations (i.e., (a subset of) first time durations 1707 in FIG. 17) of the TDM pattern (e.g., the carrier switching pattern) based on the set of {the starting slot, the starting symbol, the ending slot, the ending symbol) that repeats based on the periodicity. For example, the one or more time duration may comprise time duration(s) overlapping, in time, with resources between [the starting symbol of the starting slot, the ending system of the ending slot]. The wireless device may determine one or more second time durations (i.e., (a subset of) second time durations 1709 in FIG. 17) of the TDM pattern (e.g., the carrier switching pattern), wherein each time duration of the one or more second time durations comprise one or more sy mbols / slots (time duration (s)) not indicated / determined based on the set of {the starting slot, the starting symbol, the ending slot, the ending symbol) or present outside of the one or more first time durations. The one or more first time durations may be a subset or may fully overlap (or fully be contained within) first time durations 1707. The one or more second time durations may be a subset or may fully overlap (or fully be contained within) second time durations 1709.Docket No.25-1079PCT

[0256] In an example, the configuration parameters (the serving cell config 1861) of the first cell may comprise / indicate a bitmap of the TDM pattern (e.g the carrier switching pattern). A bit of the bitmap may indicate:

[0257] a first value indicating the wireless device is configured to receive / transmit during the slot via the first carrier, a second value indicating the. wireless device is configured to receive during the slot via the second carrier, and the slot is determined based on a predetermined subcarrier spacing (e.g., 15 kHz) or based on a reference subcarrier spacing. UE #110 may determine whether to apply the TDM pattern (e.g., the carrier switching pattern) or perform the carrier switching between the first carrier and the second carrier based on the serving cell config 1861 comprising the bitmap.

[0258] For example, UE #110 may monitor the CD-SSB(s) of the first carrier during a time duration that may overlap, in time, with the second plurality of time durations. UE #110 may not apply the TDM pattern (e.g., the carrier switching pattern) in monitoring CD-SSB(s) of the first carrier. Alternatively, BS1920 may transmit / configure the TDM pattern (e.g., the carrier switching pattern) such that the second plurality of time durations may not overlap, in time, with the CD-SSB(s) transmission via the first carrier.

[0259] In the first configuration option, UE #110 may determine that the first carrier and the second carrier is linked based on the first carrier and the second carrier being configured for the first cell or being associated with the first cell or being indicated for the first cell (e.g., a single serving cell) or parameters of the first carrier and the second carrier are comprised in the serving cell config 1861 of the first cell.

[0260] Additionally, a first set of rate matching configuration parameters (Ite-CRS-ToMatehAround, rateMatchPatternToAddModList) may be given / configured for the first carrier. Optionall / additionally, a second set of rate matching configuration parmaeters {lte-CRS-ToMatchAround2, addHoinal-rateMatchPatternToAddModList) may be given / configured for the second carrier.

[0261] The serving cell config 1861 may further comprise additional parameters indicating one or more of the followings. The additional parameters may be comprised in the ServingCellConfig IE of the first cell. One or more of the additional parameters, if applicable, may update value(s) of configured parameters of the first cell.

[0262] J) one or more first downlink BWPs of the first carrier: this may configure the one or more first BWPs for the first carrier. The one or more first BWPs may not comprise the first initial downlink BWP of the first carrier. Additionally, for the first cell / carrier, one or more uplink BWPs of the uplink carrier may be configured / indicated. The one or more first downlink BWPs may comprise an active downlink BWP (activated up on the first cell activation) of the first carrier (e.g., a BWP with an index of firstActiveDownlinkBWP-id) and / or a default downlink BWP (e.g., a BWP with de faultDownlinkB WP-id) .

[0263] K) one or more second downlink BWPs of the second carrier: this may configure the one or more second BWPs for the first carrier. The one or more second BWPs may comprise the second initial downlink BWP of the second carrier. For the second carrier, supplementaryfirstActiveDown'nkBWP-ld may be configured, where the supplementaryfirstActiveDowninkBlVP-ld indicates one BWP index of one or more BWP indexes of the one or more second BWPs. The one or more second downlink BWPs may comprise an active downlink BWP (activated up on the first cell activation in Configuration 11) of the first carrier (e.g., a BWP with an index ofDocket No.25-1079PCTsupplementaryfirstActiveDownlinkBWP-id) and / or a default downlink BWP (e.g., a BWP with supplementarydefaultDownlinkBWP-id).

[0264] L) a measurement object indicating measurements (e.g., L3 RRM, RRM) of the first cell.

[0265] For the first carrier and the second carrier respectively, the following parameters may be configured.

[0266] B-1) or C-1) one or more parameters fora downlink frequency information (e.g., frequencylnfoDL via FrequencylnfoDL IE): the one or more parameters may indicate an absolute frequency of SSB (e.g., a center frequency of a SSB transmission, absoluteFrequencySSB), a frequency band information (e.g., frequencyBandList), a starting PRB location of the carrier (e.g., the first carrier or the second carrier) (e.g., absoluteFrequencyPointA), and / or one or more subcarrier spacing values that the carrier supports (e.g., scs-SpecificCarrierList). In the example, a first scs-SpecificCarrierList of the first carrier may be same to a second scs-SpecificCarrierList of the second carrier.

[0267] B-2 or C-2) the first initial downlink BWP (initialDownlinkBWP via BWP-DownlinkCommon IE) for the first carrier or the second initial downlink BWP 'supplementaryinitialDownlinkBWP via BWP-DownlinkCommon IE) for the second carrier. The first initial downlink BWP or the second initial downlink BWP may indicate a subcarrier spacing, a bandwidth, a frequency location of the BWP (e.g., via a BWP IE), and parameters for receiving downlink control channels (e.g., pdcch-ConfigCommon) and / or parameters for receiving downlink data channels (e.g., pdsch-ConfigCommon). The pdcch-ConfigCommon may indicate cell specific parameters for the PDCCH of this BWP. This field is absent for a dormant BWP. The pdsch-ConfigCommon may indicate cell specific parameters for the PDSCH of this BWP.

[0268] In an example, the first initial BWP of the first carrier may comprise / indicate a first pdcch-ConfigCommon. The second initial BWP of the second carrier may comprise / indicate a second pdcch-ConfigCommon. Each of the first pdcch-ConfigCommon and the second pdcch-ConfigCommon may indicate one or more of the following one or more coresets and / or one or more search spaces.

[0269] Process 1803 of FIG. 18B illustrates an example embodiment of the Carrier Switching (e.g., LB-CA based on switching, LB-CA with switching, carrier aggregation with switching, etc.) based on the second configuration option (Configuration 2). In the example, the first cell and the second cell are different. A first cell index of the first cell may be different from a second cell index of the second cell. The first cell index and the second cell index may refer two serving indexes configured to UE #110. The first cell may be a primary cell. The second cell may be a secondary cell. The first carrier may be associated with the first cell, and the second carrier may be associated with the second cell.

[0270] UE #110 may receive message(s) 1872. Message(s) 1872 may be transmitted via one or more SIB1 s, one or more SIBx and / or one or more RRC messages. For example, Message(s) 1872 may be transmitted via the first cell and / or the second cell. UE #110 may receive message(s) 1872 via the first carrier of the first cell. Message(s) 1872 may indicate a first serving cell config 1881 (e.g., first configuration parameters via ServingCellConfigCommon IE, ServingCellConfigCommonSIBI IE, ServingCellConfig IE) of the first cell via a first common serving cell configuration of the first cell (hereinafter 'first carrier-cell configuration’ or1the first serving cell config 1881’). The first carrier-cell or the first serving cell config 1881 of the first cell may indicate parameters for the first carrier / cell. The first serving cell configDocket No.25-1079PCT1881 may comprise parameters for the uplink carrier. The first carrier and the uplink carrier may be paired spectrum in a first FDD band. The first carrier may refer both the first carrier and the uplink carrier.

[0271] Message(s) 1872 may, additionally, indicate a second serving cell config 1885 (e.g., second configuration parameters via SeivingCellConfigCommon IE, ServingCellConfigCommonSIBI IE, and / or ServingCellConfig IE) of the second cell via a second common serving cell configuration of the second cell (hereinafter ‘second carrier-cell configuration’, 'the second serving cell config 1885'). The second carrier-cell or the second serving cell config 1885 of the second cell may indicate parameters for the second carrier / cell. The second carrier / cell may be a supplement downlink carrier, where no corresponding uplink carrier may be defined in a second FDD band. The second FDD band may only comprise the supplement downlink carrier / spectrum without a paired uplink spectrum. The first FDD band may be different from the second FDD band. The first cell and the second cell may operate in intra-band or may not operate in a same band.

[0272] Message(s) 1872 may, additionally, comprise one or more parameters, for the carrier switching. The one or more parameters may indicate the first cell and the second cell are linked for the carrier switching. For example, the HARQ process may be shared for the first carrier, of the first cell, and the second carrier, of the second cell, based on the carrier switching, based on the first cell and the second cell being linked for the carrier switching.

[0273] Each of the first carrier-cell configuration (or first serving cell config 1881 ) or the second carrier-cell configuration (or second serving cell config 1885) may indicate / comprise, respectively, one or more of the parameters of A), (B or C), D), E), F), H), G), (J or K), B-1), B-2) of the above. For example, the first serving cell config 1881 comprises one or more first configuration parameters of the first carrier 1883. For example, the first serving cell config 1781 comprises one or more of: A), B), D), E), F), G), H), J). The one or more first configuration parameters of the first carrier 1883 (hereinafter ‘a first downlink carrier config’) may be based on B). The first downlink carrier config may comprise B-1) and B-2). For example, the second serving cell config 1885 comprises one or more second configuration parameters of the second carrier 1887. For example, the first serving cell config 1885 comprises one or more of A), C), E), F), G), H), K). The one or more second configuration parameters of the second carrier 1785 may be based on C), and may comprise C-1) and C-2).

[0274] For example, the first serving cell config 1881 may indicate the first carrier transmitting the CD-SSB(s) with the first cell identifier. The second serving cell config 1885 may indicate the second carrier transmitting the NCD-SSB(s) with the second cell identifier. The first serving cell config 1881 may indicate the uplink carrier of the first cell, where the uplink carrier is configured with the set of random access resources. In the example, the second cell identifier may be same or different from the first cell identifier.

[0275] For example, for the first serving cell config 1881, the TDM pattern (e.g., the carrier switching pattern) I) may be configured / provided. The TDM pattern (e.g., the carrier switching pattern) I) may be configured in / via a CellGroupConfig IE of the first cell and the second cell. The TDM pattern (e.g., the carrier switching pattern) I) may be configured in / via the PhysicalCellGroupConfig IE of the first cell and the second cell. The wireless device may determine / apply the TDM pattern (e.g , the carrier switching pattern) via the first cell and the second cell based on theDocket No.25-1079PCTTDM pattern (e.g., the carrier switching pattern) configured for the first cell. Additionally / alternatively, a second TDM pattern (e.g., the carrier switching pattern), based on I) may be given / provided for the second cell via the second serving cell config 1885. The wireless device may determine the one or more first time durations or first time durations 1707 for the first cell based on the TDM pattern (e.g., the carrier switching pattern) I). The wireless device may determine the one or more second time durations or second time durations 1709 for for the second cell based on the second TDM pattern (e.g., the carrier switching pattern). The wireless device may determine the one or more first time durations do not overlap, in time, with the one or more second time durations. In an example, the wireless device may apply the TDM pattern (e.g., the carrier switching pattern) and / or the second TDM pattern (e.g., the carrier switching pattern) when the second cell is active (e.g., the second cell is activated, current active BWP is not a dormant BWP, the second cell is not under cell DTX / DRX, the second cell is not under beam recovery or link recovery, etc.). The wireless device may perform the Case 1 1703 in FIG. 17 and Case 21705 in FIG. 17 based on the TDM pattern (e.g., the carrier switching pattern) (and / or the second TDM pattern (e.g., the second carrier switching pattern)) based on / in response to the applying the TDM pattern (e.g., the carrier switching pattern). UE #110 may apply Case 1 1703 during the one or more first time durations. UE #110 may apply Case 21705 during the one or more second time durations. If the second cell is not active (e.g., deactivated, in dormant state, or in outside of active time of cell DTX / DRX, a beam recovery, uplink sync recovery, etc.), the wireless device may not apply (or may ignore) the TDM pattern (e.g., the carrier switching pattern). The wireless device may perform the Case 1 1703 in FIG. 17 in response to I based on not applying or ignoring the TDM pattern (e.g., the carrier switching pattern). In an example, when the TDM pattern (e.g., the carrier switching pattern) is not applied for the second cell (e.g., Case 21705 in FIG. 17 is not used), the wireless device may be configured with a measurement gap to perform a measurement on the second cell.

[0276] For example, Message(s) 1872 (or Message(s) 1852) may indicate a cell group configuration (CellGroupConfig IE) of a cell group, wherein the cell group comprises the first cell and the second cell. The cell group configuration (CellGroupConfig IE) may comprise / indicate a) a cell group index indicating an index of a cell group, wherein the cell group comprises the first cell and the second cell; b) a primary cell index indicating a cell index of the first cell; c) a bitmap of the TDM pattern (e.g., the carrier switching pattern), wherein a bit of the bitmap indicates, for a slot, where a first value indicating the wireless device is configured to receive / transmit during the slot via the first carrier, a second value indicating the. wireless device is configured to receive during the slot via the second carrier, and the slot is determined based on a predetermined subcarrier spacing (e.g., 15 kHz) or based on a reference subcarrier spacing; d) a linked cell index (e.g., LB-CA switching cell index, LB-CA-switching-cel l-index, li nked-cell-index, LB-CA-linked-cell-i ndex, etc.) indicates a second cell index of the second cell. The wireless device may determine that the first cell and the second cell are linked for a carrier switching based on the linked cell index indicating the second cell and the primary cell index indicating the first cell (or the first cell being the primary cell).

[0277] For either the first Configuration option 1801 or the second configuration option 1803, the following example embodiments illustrate options for the TDM pattern (e.g., the carrier switching pattern) I) being configured to the wireless device. In an example, the wireless device may receive the TDM pattern (e.g., the carrier switching pattern) forDocket No.25-1079PCTthe first cell and / or the second cell via SIB1 of the first cell, via RRC message(s) and / or MAC CE / DCI signaling. The TDM pattern (e.g., the carrier switching pattern) may be comprised in a ServingCellConfigCommon of the first cell. The TDM pattern (e.g., the carrier switching pattern) may be comprised in a Ce / IGroupConfig of the first cell and the second cell. The TDM pattern (e.g., the carrier switching pattern) may be comprised in a PhysicalCellGroupConfig of the Ce / IGroupConfig. The TDM pattern (e.g., the carrier switching pattern) may be comprised in a first ServingCellConfig of the first cell and / or a second ServingCellConfig of the second cell.

[0278] The Ce / IGroupConfig may be used to configure a master cell group or a second cell group, where the first cell and the second cell belong to. A cell group may comprise of one MAC entity and a set of logical channels associated with a RLC entities and a primary cell (SpCell, PCell) and zero, one or more secondary cells (SCells). Parameters of the Ce / IGroupConfig may be applied to the primary cell and the zero, one or more secondary cells. For example, the TDM pattern (e.g., the carrier switching pattern) may be applied to the first cell for reception and transmission time domain resources. The TDM pattern (e.g., the carrier switching pattern) may be applied to the first cell for measuring downlink signals of the first cell such as CSI-RS, NZP-CSI-RS, ZP-CSI-RS, SSB, etc. The TDM pattern (e.g., the carrier switching pattern) may be applied to PUCCH transmissions, of a third cell, via the first cell, where the third cell belongs to the same cell group to the first cell.

[0279] The PhysicalCellGroupConfig may comprise configuration parameters of the cell group for example related to a physical layer (L1). The PhysicalCellGroupConfig may comprise / indicate one or more of:

[0280] a) a first cell index indicating the first cell (e.g., tdm-carrier-switching-celllndex);

[0281] b) a second cell index indicating the second cell (e.g., tdm-carrier-switching-Celllndex-LinkedCell):

[0282] c) the TDM pattern (e.g., the carrier switching pattern) applied to the first cell and the second cell.

[0283] In an example, a first periodicity of the TDM pattern (e.g., the carrier switching pattern) may be equal to a k1 times of a periodicity of the CD-SSB (e.g., k1 = 1, 2, .., 0.5, 0.25 ...) or a first SSB measurement timing configuration (SMTC) window of the first carrier. In an example, a first periodicity of the TDM pattern (e.g., the carrier switching pattern) may be equal to a k2 times of a periodicity of the NCD-SSB (e.g., k1 = 1, 2, .., 0.5, 0.25 ...) ora second SMTC window of the second carrier. In an example, the first periodicity of the TDM pattern may be one of {40msec, 80msec, 20msec, 10msec, 5msec, 160msec).

[0284] In an example, a time duration of first time durations 1703 or of the one or more first time durations may be greater than or equal to a slot. A time duration of second time durations 1709 or of the one or more second time durations may be greater than or equal to a slot. The slot may be determined based on 15 kHz subcarrier spacing and maybe 1msec. UE #2010 may not expect that a slot overlaps, in time, with both first time durations 1703 and second time durations 1709.

[0285] In an example, UE #110 may determine the TDM pattern and switching gap for the switching based on a downlink timing (e.g., DL reception time) of the first cell (e.g., PCell).

[0286] For the TDM pattern, a location of a switching gap / latency may present one or more of the followings:Docket No.25-1079PCT

[0287] A) For switching from the second carrier to first carrier, the switching gap is always assumed at the “switch from” carrier, i.e., the second carrier.

[0288] B) For switching from the first carrier to the second carrier, one or more of the followings:

[0289] B-1) Switching gap may be present at the “switch from" carrier, i.e., the first carrier

[0290] B-2) BS #120 may configure whether the switching gap is at the first carrier or the second carrier

[0291] B-3) Switching gap may be present at the second carrier

[0292] B-4) if a current time duration assigned to the second carrier is longer than 1 slot, switching gap to switch to the first carrier is placed at the end of the current time duration. Otherwise, switching gap is placed at a next slot to the current time duration, where the next slot is assigned to the first carrier by the TDM pattern. The switching gap may be same or different between a) from the first carrier to the second carrier and b) from the second carrier to the first carrier. BS #120 may schedule downlink and / or uplink such that a scheduled data may not overlap with the switching gap. For example, a switching gap from the second carrier to the first carrier, a switching gap may be placed at an end of a slot of a time duration assigned to the second carrier. The switching gap may be determined based on a RF switching and an uplink timing advance value (e.g., a sum of RF retuning latency and a UL TA).

[0293] In an example embodiment, the wireless device may receive message(s) 1872 indicating configuration parameters for the carrier switching. The configuration parameters may indicate the first cell that is associated with / operating in the first frequency band. The first cell may comprise the first carrier and the uplink. The first cell may comprise the first carrier and the first carrier may comprise the downlink carrier and the uplink carrier. The first carrier may be the downlink carrier. The configuration parameters may indicate the second cell that is associated with / operating in the second frequency band. The second cell may comprise the second carrier. The second carrier may be a downlink carrier. The configuration parameters may indicate / comprise one or more parameters indicating that the first cell and the second cell are linked for the carrier switching. The wireless device may share a HARQ process between the first cell and the second cell based on the first cell and the second cell being linked. The wireless device may receive an initial transmission of a TB via the first cell. The TB may be associated with the HARQ process. The wireless device may receive a retransmission of the TB via the second cell. The wireless device may transmit uplink signals via the first cell.

[0294] In the specification, a carrier may refer a downlink carrier or an uplink carrier or a paired carrier in a FDD band, an unpaired carrier in a TDD band. A cell may refer a serving cell. A cell may be configured with a downlink carrier, or a downlink carrier and an uplink carrier, or a downlink carrier and a supplementary downlink carrier and an uplink carrier, or a downlink carrier and an uplink carrier and an supplementary uplink carrier, or a downlink carrier and a supplementary downlink carrier and an uplink carrier and an supplementary uplink carrier.

[0295] In the specification, a wireless device may determine A based on a TDM pattern (e.g., a carrier switching pattern) may refer at least one of: a) the wireless device may determine A based on a carrier switching between the first carrier and the second carrier b) the wireless device may determine A based on the first carrier and the second carrier being configured with a carrier switching; c) the wireless device may determine A based on the first carrier and theDocket No.25-1079PCTsecond carrier being associated with the first cell; d) the wireless device may determine A based on the first carrier and the second carrier being associated with non-simultaneous carrier aggregation; e) the wireless device may determine A based on the first carrier and the second carrier being configured with cross-carrier scheduling each other; f) the wireless device may determine A based on the first carrier being enabled with a cross-carrier scheduled by the second carrier and the second carrier being enabled with a cross-carried scheduled by the first carrier; g) the wireless device may determine A based on a TDM-ed / carrier-switching PDCCH monitoring across the first carrier and the second carrier; h) the wireless device may determine A based on a PDCCH carrier switching, etc.

[0296] FIG. 19 illustrates an example embodiment of a CSI reporting framework. For example, a wireless device may transmit an uplink signal / transmission / channel (e.g., UL transmission 1924) comprising one or more CSI reports. Each of the one or more CSI reports may comprise measurement result(s) based on one or more CSI resources / CSI resource sets (e.g., CSI resource #1 1912, CSI resource #21922). Each CSI resource / resource set (e.g., via CSI-ResourceConfig IE) may be periodically transmitted (e.g., periodicity 1952 for CSI resource #1 1912, periodicity 1954 for CSI resource #21914). The wireless device may receive a CSI report trigger / CSI trigger (e.g., DC11922) for an aperiodic CSI report via a downlink command control (e.g., DCI, MAC CE).

[0297] In an example, the wireless device may receive one or more RRC messages indicating configuration parameters for one or more CSI reports (e.g., CSI-ReportConfig IE) for a cell. Each report (e.g., a CSI-ReportConfig) of the one or more CSI reports may indicate one or more CSI-RS resources. For example, a CSI report of the one or more CSI reports may indicate a set of CSI resources for channel measurements e.g., by a CSI-ResourceConfig IE (e.g., CSI-ResportConfig may comprise a CSI-ResourceConfigld for resourcesForChanne / Measurement). The CSI report may indicate ‘carrier’ that indicates in which serving cell the CSI-ResourceConfig (e.g., indicating CSI resource #1 1912 or indicating CSI resource #21914 or comprising both CSI resource #1 1912 and CSI resource #21914) indicates are transmitted. If the 'carrier' field is absent, the CSI-ResourceConfig are on the same serving cell with the CSI report. The CSI-ReportConfig IE may indicate a reportQuantity field being set to one of: “none”, “cri-RI-PMI-CQI”, “cri-RI-i 1”, ”cri-RI-i1 -CQI”, “cri-RI-CQI”, “cri-RSRP”, ”ssb-lndex-RSRP”, “cri-RI-LI-PMI-CQI”, “cri-SI NR-r16” and “ssb-lndex-SI NR-r16”, “cri-RSRP-lndex-r17”, “ssb-lndex-RSRP-lndex-r17”, “cri-SINR-lndex-r17", “ssb-lndex-SINR-lndex-r17”, and “TDCP-r18”.

[0298] For example, the CSI report may indicate a first CSI resource configuration using the resourcesForChanne / Measurement field and a second CSI resource configuration using the resourcesForPrediction field. The first and second CSI resource configurations may indicate the one or more RSs using CSI-ResourceConfig lEs.

[0299] The CSI-ResourceConfig may comprise / indicate one or more of: a CSI-ResourceConfigld (e.g., an index for the CSI-ResourceConfig); a list of CSI resource set (e.g., csi- RS- ResourceSetList), where the list of CSI resource set may indicate a list of non-zero-power CSI-RS-SSB (e.g., SSB as CSI-RS) or a list of nzp-CSI-RS; a B WP-ld (e.g., a BWP index for a BWP which the CSI-RS associated with this CSI-ResourceConfig are located); resourceType (e.g., aperiodic, semipersistent, periodic) to indicate time domain behavior of resource configuration of this CSI-ResourceConfigDocket No.25-1079PCT

[0300] For aperiodic CSI report (e.g., reportConfigType of the CSI report is indicated as ‘aperiodic’), reporting / transmitting the CSI report is triggered by DCI format 0_1 / 0_3 or by DCI format 0_2, by applying the higher layer parameter reportTriggerSizeDC 1-0-2 (in DCI format 0_1 / 0_3) or reportTriggerSize (in DCI format 0_2).

[0301] A CSI report may comprise one or more CSIs. A CSI may consist of Channel Quality Indicator (CQI), precoding matrix indicator (PMI), CSI-RS resource indicator (CRI), SS / PBCH Block Resource indicator (SSBRI), layer indicator (LI), rank indicator (Rl), L1-RSRP, L1 -SI NR, Capabilityindex or time-domain channel properties (TDCP).

[0302] For CQI, PMI, CRI, SSBRI, LI, Rl, L1-RSRP, L1-SINR, Capabilityindex, TDCP a UE is configured by higher layers with N>1 CS (-ReportConfig Reporting Settings and / or X>1 LTM-CSI-ReportConfig Reporting Settings, M>1 CSI-ResourceConfig Resource Settings and / or Y>1 LTM-CSI-ResourceConfig Resource Settings, and one or two list(s) of trigger states (given by the higher layer parameters CSI-AperiodicTriggerStateList and CSI-SemiPersistentOnPUSCH-TriggerStateList). Each trigger state in CSI-AperiodicTriggerStateList may contain / comprise a list of associated CSI-ReportContigs or LTM-CSI-ReportConfigs indicating the Resource Set IDs for channel and optionally for interference where a Resource Set for interference may be present for a Report Setting given by a CSI-ReportConfig and a trigger state additionally contains one or more csi-ReportSubConfigID if the associated CSI-ReportConfig configured with a list of sub-configurations. Each trigger state in CSI-SemiPersistentOnPUSCH-TriggerStateList may comprise one associated CSI-ReportConfig or LTM-CSI-ReportConfig, and a trigger state additionally may comprise one or more csi-ReportSubConfigID if the associated CSI-ReportConfig is configured with a list of sub-configurations.

[0303] Reporting Settings

[0304] For the CSI report, the wireless device may determine a CSI reference resource.

[0305] The CSI reference resource of a cell may be determined / defined based on one or more of the followings.

[0306] A) In the frequency domain, the CSI reference resource is defined by the group of downlink physical resource blocks corresponding to the band to which the derived CSI relates

[0307] B) In the time domain, the CSI reference resource (e.g., time duration / instance / slot ‘A 1902’) for a CSI reporting in uplink slot n' (e.g., time duration / instance ‘B 1904’) is defined by a single downlink slot (e.g., time 2^DLduration / instance / slot ‘A 1902’) n - nCSI ref- K0^set■ nKoffset, where KOffSetis a parameter configured by higher layer as specified in clause 4.2 of [6 TS 38.213], and where -Koffsejsthe subcarrier spacing configuration for ^offsetavalue °f 0 for frequency range 1.

[0308] For B), n is determined as where w= +iNslot, offset, UL >iNslot,offset,DL ■ 2^L 2^offset,UL 2fi°ffset’DLand ^and / ^are the subcarrier spacing configurations for DL and UL, respectively, andoffsetand y / offsetare determined by higher-layer configured ca-SlotOffset for the cells transmitting the uplink and downlink. In a LB-CA with a switching (or aDocket No.25-1079PCTCA with a switching), or when serving cells in a CA are synchronized and have a same numerology, n may be uplink slot n'.

[0309] B-1) For B), in case the CSI report is configured with 'periodic' or semi-persistent CSI reporting (e.g., reportConfigType indicates 'periodic' or ‘semiPersistentPUSC H' or ‘semiPersistentOnPUCC H'),

[0310] B-1 -1 ) if a single CSI-RS / SSB resource is configured for channel measurement (e.g., the CSI-ResourceConfig copmrises / indicates a single CSI-RS orSSB), ncs / _ref(e.g., C 1906) is the smallest value greater than or equal to 4 • 2toL(e.g., 4 with 15 kHz SCS of a cell), such that it corresponds to a valid downlink slot; or

[0311] B-1-2) if multiple CSI-RS / SSB resources are configured for channel measurement ncs / _ref(e.g., C 1906) is the smallest value greater than or equal to 5-2^ (e.g., 5 with 15 kHz SCS of a cell), such that it corresponds to a valid downlink slot

[0312] B-2) For B), in case the CSI report is configured with 'aperiodic' (e.g., reportConfigType indicates 'aperiodic'),

[0313] B-2-1) where for aperiodic CSI reporting, if the wireless device is indicated by the DCI to report CSI in the same slot as the CSI request, ncsi_ret (e.g., C 1906) is such that the reference resource is in the same valid downlink slot as the corresponding CSI request, otherwise ncs / _ref(e.g., C 1906) is the smallest value greater than or equal to |_Z / A^J, such that slot n- ncsi_ref(e.g., C 1906) corresponds to a valid downlink slot, where Z' (e.g., a CSI processing delay) corresponds to the delay requirement;

[0314] B-3) when periodic or semi-persistent CSI-RS / CSI-IM or SSB is used for channel / interference measurements (e.g., resourceType of CSI-ResourceConfig indicates semi-persistent or periodic), the wireless device may not measure channel / interference on the CSI-RS / CSI-I M / SSB whose last OFDM symbol is received less than Z' symbols (e.g., the CSI processing delay) before transmission time of the first OFDM symbol of the aperiodic CSI reporting. The base station may indicate or trigger aperiodic CSI reporting such that the wireless device may measure channel / interference on the CSI-RS / CSI-I M / SSB whose last OFDM symbol is received up to Z'symbols (e.g., the CSI processing delay) before transmission time of the first OFDM symbol of the aperiodic CSI reporting. The processing delay is described in later of the specification.

[0315] A slot in a serving cell may be considered to be a valid downlink slot if it satisfies a) it comprises at least one higher layer configured downlink or flexible symbol, and b) it does not fall within a measurement gap for that wireless device. The measurement gap maybe determined based on a measurement gap pattern associated with the cell.

[0316] If there is no valid downlink slot for the CSI reference resource corresponding to a CSI Report Setting in the cell, CSI reporting is omitted for the serving cell in uplink slot n'. The wireless device may drop reporting I transmitting of the CSI reporting in the uplink slot n'.

[0317] Fora CSI report with reportQuantity not set to ‘ssb-lndex-RSRP’, ‘ssb-lndex-SINR’, ‘ssb-lndex-RSRP-lndex’ or ‘ssb-l ndex-SI N R-lndex’, after the CSI report (re)configuration, serving cell activation, BWP change, or activation of SP-CSI, the wireless device may report a CSI report after receiving at least one CSI-RS transmission occasion for channel measurement and CSI-RS and / or CSI-IM occasion for interference measurement no later than CSI referenceDocket No.25-1079PCTresource. If the wireless device may not receive either the CSI-RS transmission occasion for channel measurement or CSI-RS and / or CSI-IM occasion for interference measurement no later than CSI reference resource, the wireless device may drop the CSI report and may not transmit the CSI report.

[0318] For a CSI report configuration containing a list of sub-configurations provided by csi-ReportSubConfigList, after the CSI report (re)configuration, serving cell activation, BWP change, or activation of SP-CSI, the wireless device may report a CSI report including one or more sub-reports if the wireless device has received at least one CSI-RS transmission occasion for channel measurement and CSI-RS and / or CSI-IM occasion for interference measurement, per sub-configuration, no later than CSI reference resource and may drop the report otherwise, where the subconfiguration is the activated / triggered one for AP / SP-CSI reporting, or the configured one for P-CSI reporting.

[0319] For a CSI-ReportConfig configured with two Resource Groups and N Resource Pairs for channel measurement in the corresponding CSI-RS Resource Set, as described in below, after the CSI report (re)configuration, serving cell activation, BWP change, or activation of SP-CSI, the wireless device may report a CSI report if the wireless device has received at least one CSI-RS transmission occasion for each of the CSI-RS resources in the corresponding CSI-RS Resource Set for channel measurement and one CSI-IM occasion for each of the CSI-IM resources in the corresponding Resource Set for interference measurement no later than the CSI reference resource and within the same DRX Active Time when DRX is configured, and may drop the report otherwise (e.g., has not received CSI-RS transmission or CSI-IM occasion).

[0320] Fora CSi-ReportConfig configured with codebookType set to 'typell-CJT-r18' or 'typell-C JT-PortSelection-r18', after the CSI report (re)configuration, serving cell activation, BWP change, or activation of SP-CSI, the wireless device may report a CSI report, if the wireless device has received at least one CSI-RS transmission occasion for each of the CSI-RS resources in the corresponding CSI-RS Resource Set for channel measurement and one CSI-RS and / or CSI-IM resource transmission occasion for the CSI-RS and / or CSI-IM resource in the corresponding Resource Set for interference measurement no later than the CSI reference resource and within the same DRX Active Time, when DRX is configured, and may drop the report otherwise.

[0321] For a CSI-ReportConfig configured with codebookType set to 'typel l-Doppler-r18' or 'typel l-Doppler-PortSelection-r18', after the CSI report (re)configuration, serving cell activation, BWP change, or activation of SP-CSI, the wireless device may report a CSI report, if the wireless device has received at least one aperiodic or Kpperiodic or semipersistent consecutive CSI-RS transmission occasions (e.g., Kpoccasions of CSI resource #1 1912) for each CSI-RS resource in the corresponding CSI-RS Resource Set for channel measurement and one CSI-RS and / or CSI-IM resource transmission occasion (e.g., one occasion of CSI resource #21914) for the CSI-RS and / or CSI-IM resource in the corresponding Resource Set for interference measurement no later than the CSI reference resource (e.g., time instance ‘A 1902) and within the same DRX Active Time, when DRX is configured, and may drop the report otherwise. The value of Kp6 {1,2,4} is indicated by a UE capability.Docket No.25-1079PCT

[0322] For a CSI-ReportConfig configured with the higher layer parameter reportQuantity set to 'tdcp', after the CSI report (re)configuration, serving cell activation, BWP change, the wireless device may report a CSI report, if the wireless device has received at least one CSI-RS transmission occasion for each CSI-RS resource (e.g., one occasion of CSI resource #1 1912 and one occasion of CSI resource #21914) in the KTRSCSI-RS Resource Sets (e.g., a first CSI-RS resource set comprising CSI resource #1 1912 and a second CSI-RS resource set comprising CSI resource #2 1914, where KTRSis 2) of the CSI-RS Resource Setting for channel measurement no later than the CSI reference resource (e.g., the time instance / slot ‘A 1902’) within the same DRX active time, when DRX is configured, and drop the report otherwise.

[0323] When DRX is configured, the wireless device may report a CSI report with the reportQuantity not set to ‘ssb-I ndex-RSRP', ‘ssb-l ndex-S I N R’, ‘ssb-lndex-RSRP-lndex’ or ‘ssb-l ndex-S I N R-lndex’, if the wireless device has received at least one CSI-RS transmission occasion for channel measurement and CSI-RS and / or CSI-IM occasion for interference measurement in DRX Active Time no later than CSI reference resource and may drop the report otherwise.

[0324] When DRX is configured, for a CSI report configuration containing a list of sub-configurations provided by csi-ReportSubConfigList, the wireless device may report a CSI report including one or more sub-reports, if the wireless device has received at least one CSI-RS transmission occasion for channel measurement and CSI-RS and / or CSI-IM occasion for interference measurement in DRX Active Time, per sub-configuration, no later than CSI reference resource (e.g., the time instance / slot ‘A 1902') and drops the report otherwise, where the sub-configuration is the activated / triggered one for AP / SP-CS I reporting, or the configured one for P-CSI reporting. When the wireless device is configured to monitor DCI format 2_6 and if the wireless device configured by higher layer parameter ps-TransmitOtherPeriodicCSI to report CSI with the higher layer parameter reportConfigType set to 'periodic' and reportQuantity set to quantities other than 'cri-RSRP', 'ssb-lndex-RSRP', 'cri-RSRP- Index', and 'ssb-lndex-RSRP-lndex ' when drx-onDurationTimer is not started, the wireless device may report CSI with the reportQuantity not set to ‘ssb-lndex-SI NR’ or 'ssb-lndex-SINR-lndex' during the time duration indicated by drx-onDurationTimer in DRX-Config also outside active time according to the procedure, if the wireless device has received at least one CSI-RS transmission occasion for channel measurement and CSI-RS (e.g., a transmission occasion of CSI resource #1 1912) and / or CSI-IM occasion (e.g, a transmission occasion of CSI resource #21914) for interference measurement during the time duration indicated by drx-onDurationTimer in DRX-Config outside DRX active time or in DRX Active Time.no later than CSI reference resource (e.g., the time instance / slot ‘A 1902') and may drop the report otherwise.

[0325] For a CSI report configuration containing a list of sub-configurations provided by csi-ReportSubConfigList, when the wireless device is configured to monitor DCI format 2_6 and if the wireless device is configured by higher layer parameter ps-TransmitOtherPeriodicCSI to report CSI with the higher layer parameter reportConfigType set to 'periodic' and reportQuantity set to quantities other than 'cri-RSRP', 'ssb-lndex-RSRP', 'cri-RSRP- Index', and 'ssb-lndex-RSRP- Index' when drx-onDurationTimer is not started, the wireless device may report a CSI report including one or more sub-reports during the time duration indicated by drx-onDurationTimer in DRX-Config also outside active time, if the wireless device has received at least one CSI-RS transmission occasion for channel measurement and CSI-RSDocket No.25-1079PCTand / or CSI-IM occasion for interference measurement during the time duration indicated by drx-onDurationTimer in DRX-Config outside DRX active time or in DRX Active Time, per sub-configuration, no later than CSI reference resource and may drop the report otherwise, where the sub-configuration is the configured one for P-CS I reporting.

[0326] When the wireless device is configured to monitor DCI format 2_6 and if the wireless device is configured by higher layer parameter ps-TransmitPeriodicL1-RSRP to report L1-RSRP with the higher layer parameter reportConfigType set to 'periodic' and reportQuantity set to 'cri-RS RP', 'ssb-lndex-RSRP', 'cri-RSRP- Index', or 'ssb-Index-RSRP- Index' when drx-onDurationTimer is not started, the wireless device may report L1-RSRP during the time duration indicated by drx-onDuration Timer in DRX-Config also outside active time and when reportQuantity set to 'cri-RSRP' or 'cri-RSRP- Index' if the wireless device has received at least one CSI-RS transmission occasion for channel measurement during the time duration indicated by drx-onDurationTimer in DRX-Config outside DRX active time or in DRX Active Time no later than CSI reference resource and may drop the report otherwise.

[0327] For the CSI report configuration in CSTReportConfig associated with the higher layer parameter reportQuantity comprising at least ' Rl', the wireless device may report a CSI report if the wireless device has received at least one CSI-RS transmission occasion of each periodic CSI-RS resource or semi-persistent CSI-RS resource on a serving cell with cell DTX activated for channel measurement and / or interference measurement in active periods of cell DTX of the serving cell no later than CSI reference resource, and the wireless device may drops the CSI report otherwise.

[0328] In an example, the bs may not configure such that a NZP CSI-RS resource for channel measurement overlaps with CSI-IM resource for interference measurement or NZP CSI -RS resource for interference measurement for each wireless device.

[0329] For L1-RSRP computation, the wireless device may be configured with CSI-RS resources, SS / PBCH Block resources or both CSI-RS and SS / PBCH block resources, when resource-wise quasi co-located with 'type C and 'typeD' when applicable, and the wireless device may be configured with CSI-RS resource setting up to 16 CSI-RS resource sets having up to 64 resources within each set. The total number of different CSI-RS resources over all resource sets is no more than 128.

[0330] If the higher layer parameter timeRestrictionForChannelMeasurements in CSI-ReportConfig is set to "notConfigured", the wireless device may derive the channel measurements for computing L1-RSRP value reported in uplink slot n based on the SS / PBCH or NZP CSI-RS, no later than the CSI reference resource associated with the CSI resource setting.

[0331] If the higher layer parameter timeRestrictionForChanne / Measurements in CSi-ReportConfig is set to “Configured", the wireless device may derive the channel measurements for computing L1-RSRP reported in uplink slot n based on the most recent, no later than the CSI reference resource, occasion of SS / PBCH or NZP CSI-RS associated with the CSI resource setting.

[0332] Resource SettingsDocket No.25-1079PCT

[0333] Each CSI Resource Setting CSI-ResourceConfig may comprise a configuration of a list of S^1 CSI Resource Sets (given by higher layer parameter csi-RS-ResourceSetList), where the list is comprised of references to either or both of NZP CSI-RS resource set(s) and SS / PBCH block set(s) or the list is comprised of references to CSI-IM resource set(s). Each CSI Resource Setting is located in the DL BWP identified by the higher layer parameter BWP-id, and all CSI Resource Settings linked to a CSI Report Setting have the same DL BWP.

[0334] The time domain behavior of the CSI-RS resources within a CSI Resource Setting may be indicated by the higher layer parameter resource Type and may be set to one of: aperiodic, periodic, and semi-persistent. For periodic and semi-persistent CSI Resource Settings, when the wireless device is configured with groupBasedBeamReporting-r17 or groupBasedBeamReporting-v18, the number of CSI Resource Sets configured is S=2. For other cases, the number of CSI-RS Resource Sets configured is limited to S=1, except for periodic CSI Resource Settings, when the UE is configured with TDCP reporting, for which the number of CSI-RS Resource Sets in the CSI Resource Setting for channel measurement is KTRSG {1,2,3} and all the CSI-RS Resource Sets are configured with the higher layer parameter trs-lnfo.

[0335] For periodic and semi-persistent CSI Resource Settings, the configured periodicity and slot offset is given in the numerology of its associated DL BWP, as given by BWP-id. When a wireless device is configured with multiple CS / -ResourceConfigs consisting / comprising the same NZP CSI-RS resource ID, the same time domain behavior may be configured for the CSI-ResourceConfigs When a wireless device is configured with multiple CSI-ResourceConfigs consisting of / comprising the same CSI-IM resource ID, the same time-domain behavior may be configured for the CSI-ResourceConfigs. All CSI Resource Settings linked to a CSI Report Setting may have the same time domain behavior (e.g., periodic, semi-periodic, or aperiodic).

[0336] The following may be configured via higher layer signaling for one or more CSI Resource Settings for channel and interference measurement:

[0337] A) CSI-IM resource for interference measurement;

[0338] B) NZP CSI-RS resource for interference measurement; and / or

[0339] C) NZP CSI-RS resource for channel measurement

[0340] The wireless device may assume that the NZP CSI-RS resource(s) for channel measurement and the CSI-IM resource(s) for interference measurement configured for one CSI reporting are resource-wise QCLed with respect to 'typeD'. When NZP CSI-RS resource(s) is used for interference measurement, the wireless device may assume that the NZP CSI-RS resource for channel measurement and the CSI- IM resource or NZP CSI-RS resource(s) for interference measurement configured for one CSI reporting are QCLed with respect to 'typeD'.

[0341] For TDCP measurement, one periodic CSI Resource Setting is configured, and the Resource Setting is for channel measurement on CSI-RS for tracking.

[0342] Resource Setting configuration

[0343] For aperiodic CSI, each trigger state configured using the higher layer parameter CSI-AperiodicTriggerState may be associated with one or multiple CSI-ReportConfig where the CSI-ReportConfig not configured withDocket No.25-1079PCTgroupBasedBeamReporting-r17 or groupBasedBeamReporting-v18 and it is linked to periodic, or semi-persistent, or aperiodic resource setting(s). For the aperiodic CSI, when one Resource Setting (e.g., CSI resource #1 1912) is configured, the Resource Setting (given by higher layer parameter resourcesForChanne / Measurement) is for channel measurement for L1-RSRP or for channel and interference measurement for L1-SINR computation. For the aperiodic CSI, when two Resource Settings are configured, the first one Resource Setting (e.g., CSI resource #1 1912) (given by higher layer parameter resourcesForChanne / Measurement) is for channel measurement and the second one (e.g., CSI resource #21914) (given by either higher layer parameter csi-IM-ResourcesForlnterference or higher layer parameter nzp-CSI-RS-ResourcesForlnterference) is for interference measurement performed on CSI-IM or on NZP CSI-RS. For the aperiodic CSI, when three Resource Settings are configured, the first Resource Setting (higher layer parameter resourcesForChanne / Measurement) is for channel measurement, the second one (given by higher layer parameter csi-IM-ResourcesForlnterference) is for CSI-IM based interference measurement and the third one (given by higher layer parameter nzp-CSI-RS-ResourcesForlnterference) is for NZP CSI-RS based interference measurement.

[0344] For aperiodic CSI, a wireless device configured with a CSI-ReportConfig with the higher layer parameter reportQuantity set to 'tdcp' may be expected to be configured with one CSI Resource Setting (given by higher layer parameter resourcesForChanne / Measurement). The CSI Resource Setting may be periodic, with KTRSe {1, 2, 3} CSI-RS Resource Sets (e.g., a first CSI-RS resource set comprising CSI resource #1 1912 and a second CSI-RS resource set comprising CSI resource #21914, where KTRSis 2) configured with higher layer parameter trs-lnfo. The support of KTRS= 2 or 3 is subject to UE capability indication. For a periodic CSI-ResourceConfig, the wireless device may assume that all the CSI-RS resources in the KTRSCSI-RS Resource Sets share the same QCL-TypeA / C and, if applicable, TypeD. The wireless device may expect that all the CSI-RS resources in the CSI-RS Resource Set(s) are configured with the same bandwidth and subcarrier locations. The wireless device configured with a CSI-ReportConfig with the higher layer parameter reportQuantity set to 'tdcp' may be not expected to be configured with interference measurement on CSI-IM and / or NZP-CSI-RS.

[0345] For aperiodic CSI, a wireless device, that is configured with a CSI-ReportConfig with the higher layer parameter reportQuantity set to 'tdcp', may be configured with one CSI Resource Setting (given by higher layer parameter resourcesForChanne / Measurement). The wireless device may not be configured with interference measurement on CSI-IM and / or NZP-CSI-RS. The CSI Resource Setting may be periodic, with KTRSe {1, 2, 3} CSI-RS Resource Sets (e.g., a first CSI-RS resource set comprising CSI resource #1 1912 and a second CSI-RS resource set comprising CSI resource #21914, where KrRSis 2) configured with higher layer parameter frs-lnfo. The support of KTRS= 2 or 3 is subject to UE capability indication. For a periodic CSI-ResourceConfig, the wireless device may assume that all the CSI-RS resources in the KTRSCSI-RS Resource Sets share the same QCL-TypeA / C and, if applicable, TypeD. The wireless device may expect that all the CSI-RS resources in the CSI-RS Resource Set(s) are configured with the same bandwidth and subcarrier locations.

[0346] The wireless device may be configured with one CSI-RS resource in resource set for channel measurement for a CSI-ReportConfig with the higher layer parameter codebookType set to 'typell', 'typel l-PortSelection', 'typell-r16',Docket No.25-1079PCT'typell-PortSelection-r16', or'typell-PortSelection-r17'. A wireless device may be configured with up to 64 NZP CSI-RS resources and / or SS / PBCH block resources in resource setting for channel measurement for a CSI-ReportConfig with the higher layer parameter reportQuantity set to 'none', 'cri-RI-CQI', 'cri-RSRP', 'ssb-lndex-RS RP', 'cri-SINR' or 'ssb-Index-SINR', 'cri-RSRP- Index', 'ssb-lndex-RSRP- Index', 'cri-SINR- Index' or 'ssb-lndex-SINR- Index'. If interference measurement is performed on CSI-IM, each CSI-RS resource for channel measurement is resource-wise associated with a CSI-IM resource by the ordering of the CSI-RS resource and CSI-IM resource in the corresponding resource sets. The number of CSI-RS resources for channel measurement equals to the number of CSI-IM resources.

[0347] The wireless device, that is configured with a CSI-ReportConfig with the higher layer parameter reportQuantity set to 'cri-RI-PMI-CQI' and codebookType set to 'typell-CJT-r18' or 'typel l-C JT-PortSelection-r18', may be configured with 1 < K < 4 CSI-RS resources in a resource set for channel measurement. If interference measurement is performed on CSI-IM, only one resource is configured in the corresponding csi-IM-ResourceSet. If interference measurement is performed on NZP CSI-RS, only one resource is configured in the corresponding NZP-CSI-RS-ResourceSet for interference measurement.

[0348] The wireless device, that is configured with a CSI-ReportConfig with the higher layer parameter N4 and reportQuantity set to 'cri-RI-PMI-CQI', may be configured with K e {4,8,12} aperiodic CSI-RS resources or with a single periodic or semi-persistent CSI-RS resource in the resource set for channel measurement. For an aperiodic CSI-RS resource set for channel measurement, the K CSI-RS resources (e.g., CSI resource #1 1912 and CSI resource #2 1914, where K is 2) are triggered by the same triggering instance and the separation between two consecutive CSI-RS resources is m e {1,2} slots (e.g., CSI resource #1912 and CSI resource #1914 are in a same slot if m = 1 or in adjacent slots if m =2), which is configured by higher layer parameter in the NZP-CSi-RS-ResourceSet (e.g., NZP-CSI-RS-ResourceSet comprising / indicating CSI resource #1912 and CSI resource #1914). The K aperiodic CSI-RS resources are transmitted following the order of the CSI-RS resource IDs configured in the CSI-RS resource set. The wireless device may assume that the antenna port with the same port index of the K aperiodic CSI-RS resources is the same. If interference measurement is performed on CSI-IM, only one resource is configured in the corresponding csi-IM-ResourceSet. If interference measurement is performed on NZP CSI-RS, only one resource is configured in the corresponding NZP-CSi-RS-ResourceSet for interference measurement. In case m is 1, the two consecutive CSI-RS resources are in a same slot. In case m is 2, the two consecutive CSI-RS sources are in consecutive slots.

[0349] UE procedure for receiving reference signals

[0350] CSI-RS reception procedure

[0351] If the wireless device is configured with DRX, and also the wireless device is configured to monitor DC I format 2_6 and configured by higher layer parameter ps-TransmitOtherPeriodicCSI to report CSI with the higher layer parameter reportConfigType set to 'periodic' and reportQuantity set to quantities other than 'cri-RSRP' and 'ssb-lndex-RSRP' when drx-onDurationTimer in DRX-Config is not started, the most recent CSI measurement occasion occurs in DRX active time or during the time duration indicated by drx-onDurationTimer in DRX-Config also outside DRX active time for CSI to be reported.Docket No.25-1079PCT

[0352] If the wireless device is configured with DRX, and also the wireless device is configured to monitor DC I format 2_6 and configured by higher layer parameter ps-TransmitPeriodicL1-RSRP to report L1-RSRP with the higher layer parameter reportConfigType set to 'periodic' and reportQuantity set to cri-RSRP when drx-onDurationTimer in DRX-Config is not started, the most recent CSI measurement occasion occurs in DRX active time or during the time duration indicated by drx-onDurationTimer in DRX-Config also outside DRX active time for CSI to be reported.

[0353] If the wireless device is configured with DRX, and also the wireless device is configured to monitor DC I format 2_6 and configured by higher layer parameter ps-TransmitPeriodicL1-RSRP to report L1-RSRP with the higher layer parameter reportConfigType set to 'periodic' and reportQuantity set to cri-RSRP when drx-onDurationTimer in DRX-Config is not started, the most recent CSI measurement occasion occurs in DRX active time or during the time duration indicated by drx-onDurationTimer in DRX-Config also outside DRX active time for CSI to be reported.

[0354] If the wireless device is configured with DRX and may not be configured with the above conditions (e.g., to monitor DCI format 2_6 and one of ps-TransmitOtherPeriodicCSI, ps-TransmitPeriodicL1-RSRP, and ps-TransmitPeriodicL1-RSRP), the wireless device may report CSI based on most recent CSI measurement occasion occurs in DRX active time.

[0355] Subject to UE capability, the wireless device, if it is configured with a CSI-ReportConfig with the higher layer parameter N4 and reportQuantity set to 'cri-RI-PMI-CQI', may support UE-side CSI prediction. The reported PMI indicates predicted precoder matrices associated with N4consecutive slot intervals, each with duration of d slots, where the value of W46 {1,2 ,4,8} is configured by higher layer parameter N4. If the wireless device is configured with an aperiodic CSI-RS resource set for channel measurement, the value, in number of slots, of the time unit d e {1, m} may be configured by higher layer parameter d, where m is 1 or 2 (e.g., same slot or adjacent slots). If the wireless device is configured with a periodic or semi-persistent CSI-RS resource set for channel measurement, the value of d is equal to the periodicity of the CSI-RS resource. The earliest of the W4slot intervals starts at slot I = n + 6, where n is the uplink slot (e.g., the time instance / slot ‘B 1904’) in which the CSI is reported and the slot offset 6 e{-ncs,ref, 0,1,2} is configured by higher layer parameter delta, where nCSi ref is based on a CSI reference resource and the value 6 = -ncsl refmay be configured subject to UE capability,

[0356] For W4= 1, the wireless device may report a predicted PMI for slot interval [1,1 + d - 1] and the slot offset value 6 = -nCSI ref may be configured if d > 1. The wireless device may be configured with W4= 1 if the higher layer parameter codebookType is set to 'typel l-Doppler-r18', or 'typel l-Doppler-PortSelection-r18'. The reported CQI is associated with slot I and the reported PMI.

[0357] For / 4> 1, the wireless device may report a PMI which indicates predicted precoder matrices associated with slot intervals [I + j • d, I + (J + 1) • d - 1], for j = 0, ... , N4- 1. The wireless device may be configured with N4> 1 if the higher layer parameter codebookType is set to 'typel l-Doppler-r18'. The wireless device, that is configured by higher layer parameter TDCQ / to report X e {1,2} CQIs for each subband in the CSI reporting band, if cqi-Formatlndicator is set to 'subbandCQ I', or X 6 {1,2} CQIs for the entire CSI reporting band, if cqi-FormatlndicatorDocket No.25-1079PCTis set to 'widebandCQI1. For X = 2, the second CQI may comprise a 4-bit wideband CQI index and, if subband CQI reporting is configured, a 2-bit subband CQI index, may be calculated independently from the first CQI and the two CQIs may be reported in the same CSI report.

[0358] CSI processing delay

[0359] When the CSI request field on a DCI triggers a CSI report(s) on PUSCH, the wireless device may provide a valid CSI report for the n-th triggered report if the following conditions are met:

[0360] A) if the first uplink symbol to carry the corresponding CSI report(s) including the effect of the timing advance, starts no earlier than at symbol Zref, and

[0361] B) if the first uplink symbol to carry the n-th CSI report including the effect of the timing advance, starts no earlier than at symbol Zrerfn

[0362] In A) and B), Zref may be defined / determined as the next uplink symbol with its CP startingT = (Z)(2048+144) • K '1TC+rmAafter the end of the last symbol of the PDCCH triggering the CSI report(s). ZrerfnJ may be defined / determined as the next uplink symbol with its CP starting = (Z ')(2O48 + 144) • K2-A-T after the end of the last symbol in time of the latest of: aperiodic CSI-RS resource for channel measurements, aperiodic CSI-IM used for interference measurements, and aperiodic NZP CSI-RS for interference measurement for a CS / -ReportConfig, or for all triggered sub-configurations if CSI-ReportConfig contains multiple sub-configurations, when aperiodic CSI-RS is used for channel measurement for the n-th triggered CSI report, and where mth is a switching delay with a CSI computation delay requirement 1.

[0363] If the PUSCH indicated by the DCI is overlapping with another PUCCH or PUSCH, then the CSI report(s) may be multiplexed, otherwise the CSI report(s) may be transmitted on the PUSCH indicated by the DCI.

[0364] When the CS / request field on a DCI triggers a CSI report(s) on PUSCH, if the first uplink symbol (e.g., a first symbol / a starting time of the time slot ‘B 1904') to carry the corresponding CSI report(s) including the effect of the timing advance, starts earlier than at symbol Zret, the wireless device may ignore the scheduling DCI if no HARQ-ACK or transport block is multiplexed on the PUSCH. When the CSI requestfield on a DCI triggers a CSI report(s) on PUSCH, if the first uplink symbol to carry the n-th CSI report including the effect of the timing advance, starts earlier than at symbol Z’ref(n), the wireless device may ignore the scheduling DCI if the number of triggered reports is one and no HARQ-ACK or transport block is multiplexed on the PUSCH or the wireless device may not update the CSI for the n-th triggered CSI report. When the PDCCH reception includes two PDCCH candidates from two respective search space sets for the purpose of determining the last symbol of the PDCCH triggering the CSI report(s), the PDCCH candidate that ends later in time is used.

[0365] Z, Z' and may be defined as:

[0366] Z = max (Z (m)') and Z' - max (Z'(m)), where M is the number of updated CSI report(s),m=0,...,M-l m=0,...,Af-l(Z(m), Z'(m)) corresponds to the m-th updated CSI report and is defined asDocket No.25-1079PCT

[0367] - (Z1(Z[) of the table 1 if max{ PPDCCH, PCSI-RS, UL} < 3 and if the CSI is triggered without a PUSCH with either transport block or HARQ-ACK or both when L = 0 CPUs are occupied and the CSI to be transmitted is a single CSI and corresponds to wideband frequency-granularity where the CSI corresponds to at most 4 CSI-RS ports in a single resource without CRI report and where CodebookType is set to 'typel-SinglePanel' or where reportQuantity is set to 'cri-RI-CQI1, or

[0368] - (Z1(Zj) of the table 2 if the CSI to be transmitted corresponds to wideband frequency-granularity where the CSI corresponds to at most 4 CSI-RS ports in a single resource without CRI report and where CodebookType is set to 'typel-SinglePanel' or where reportQuantity is set to 'cri-RI-CQI', or

[0369] - (ZlfZ}") of the table 2 if the CSI to be transmitted corresponds to wideband frequency-granularity where the reportQuantity is set to 'ssb-l ndex-SI N R', 'cri-SINR', 'ssb-lndex-SINR- Index or 'cri-SINR- Index or

[0370] - (Z3, Z3) of the table 2 if reportQuantity is set to 'cri-RSRP', 'ssb-lndex-RSRP', 'cri-RSRP- Index' or 'ssb-Index-RSRP- Index ', where Xp is according to UE reported capability beamReportTiming and KB / is according to UE reported capability beamSwitchTiming

[0371] - (Z2,Z2) or (Z2+ Z2, 2Z2), according to UE reported capability, with (Z2, Z2) of table 2, if CodebookType is set to 'typel l-C JT-r18' or 'typel l-C JT-PortSelection-r18' and the corresponding NZP-CSI-RS-ResourceSetfor channel measurement is configured with 1 < NTRP< 4 resources, or

[0372] - (Z2+ 14( / < - l)m, Z2), with (Z2, Z2) of table 2, if the CSI report is configured with X4= 1, CodebookType is set to 'typel l-Doppler-r18' or 'typel l-Doppler-PortSelection-r18' and the corresponding NZP-CSI-RS-ResourceSet for channel measurement is aperiodic with K CSI-RS resources, or

[0373] - (Z2+ iv, Z2), with (Z2lZ2) of table 2, if the CSI report is configured with N4= 1, CodebookType is set to 'typell-Doppler-r18' or 'typel l-Doppler-PortSelection-r18' and the corresponding NZP-CSI-RS-ResourceSettor channel measurement is periodic or semi-persistent with a single CSI-RS resource, or

[0374] - (Z2+ 14(X - l)m, Z2) or (Z2+ 14(X - l)m + Z2, 2Z2), according to UE reported capability, with (Z2lZ2) of table 2, if the CSI report is configured with N4> 1, CodebookType is set to 'typel l-Doppler-r18' and the corresponding NZP-CSI-RS-ResourceSet for channel measurement is aperiodic with K CSI-RS resources, or

[0375] - (Z2+ w, Z2) or (Z2+ w + Z2, 2Z2), according to UE reported capability, with (Z2, Z2) of table 2, if the CSI report is configured with N4> 1, CodebookType is set to 'typel l-Doppler-r18' and the corresponding NZP-CSI-RS-ResourceSet for channel measurement is periodic or semi-persistent with a single CSI-RS resource, or

[0376] - otherwise, (Z2, Z2) of table 5.4-2

[0377] p of table 1 and table 2 corresponds to the min (PPDCCH, PCSI-RS, PUL) where the PPDCCH corresponds to the subcarrier spacing of the PDCCH with which the DCI was transmitted and pur corresponds to the subcarrier spacing of the PUSCH with which the CSI report is to be transmitted and PCSI-RS corresponds to the minimum subcarrier spacing of the aperiodic CSI-RS triggered by the DCIDocket No.25-1079PCT

[0378] For a CSI report corresponding to a CSI-ReportConfig that contains a list of sub-configurations, provided by [csi-ReportSubConfigListJ, (Z2lZ2) of table 2 may be applicable.Table 1: CSI computation delay requirement 1Zf [symbols]AZi Z'70 10 81 13 112 25 213 43 36Table 2: CSI computation delay requirement 2Z; [symbols] Zi- [symbols] Z3[symbols] AZi Zi Z2Z2Z3Z30 22 16 40 37 22 Xo 1 33 30 72 69 33 X2 44 42 141 140 min(44,X2+ KBi) x23 97 85 152 140 min(97, X3+ KB?) X35 388 340 608 560 min(388, X5+ X5KB3)6 776 680 1216 1120 min(776, X6+ X6KB4)

[0379] Certain challenges may arise in wireless communication systems. For instance, there maybe a scenario where a user equipment (UE) is configured with low band carrier aggregation (LB-CA), involving dynamic switching between a primary cell (PCell) and a secondary cell (SCell). In LB-CA, the UE is configured to transmit and / or receive data in the PCell and the SCell during their respective allocated time intervals. In such a scenario, a conflict may occur when a time interval allocated to one cell for LB-CA overlaps with the time interval for receiving and measuring a channel state information (CSI) reference signal of the other cell. Specifically, this conflict may arise when an SCell time interval in LB-CA (i.e., the time interval allocated to the SCell for LB-CA) overlaps with the PCell's CSI reference resource in time domain, or when a PCell time interval in LB-CA (i.e., the time interval allocated to the PCell for LB-CA) overlaps with the SCell’s CSI reference resource in time domain. These overlaps may prevent the UE from either successfully receiving and measuring the CSI reference signal of the respective cell or successfully communicating in the respective cell in LB-CA, thereby potentially resulting in communication failures or degraded performance.

[0380] In order to solve this problem, according to an example of the embodiment of this disclosure, there is provided a method comprising receiving, by a wireless device, one or more configuration parameters indicating: a low-bandDocket No.25-1079PCTcarrier aggregation (LB-CA) which is based on switching between a first cell and a second cell, a channel state information (CS I ) report configuration of the first cell, and a measurement gap associated with the first cell. The method further comprises, based on the CSI report configuration of the first cell, determining a CSI reference resource for a CSI report for the first cell. The CSI reference resource does not overlap with: the measurement gap associated with the first cell, and a time slot allocated to the second cell for the LB-CA. The method further comprises performing a measurement on the CSI reference resource, and transmitting the CSI report, for the first cell, indicating a result of the measurement on the CSI reference resource.

[0381] In another example of the embodiment, there is provided a method comprising receiving, by a wireless device, one or more configuration parameters indicating a carrier aggregation (CA) which is based on switching between a first cell and a second cell. The method further comprises transmitting a CSI report for the first cell, wherein the CSI report is based on a channel state information (CSI) reference resource which does not overlap with a time slot allocated to the second cell for the CA.

[0382] In a different example of the embodiment, there is provided a method comprising receiving, by a wireless device, one or more configuration parameters indicating a low-band carrier aggregation (LB-CA) which is based on switching between a primary cell (PCell) and a secondary cell (SCell). The method further comprises receiving a downlink control command activating the SCell, and, based on the receiving the downlink control command, determining a first channel state information (CSI) reference resource for the SCell. The first CSI reference resource for the SCell overlaps a time slot assigned to the PCell for the LB-CA, and the SCell is inactive during the time slot. The method further comprises performing measurement on the first CSI reference resource, and transmitting a CSI report including a result of the measurement. The method further comprises, based on the transmitting the CSI report, activating the SCell, and determining a second CSI reference resource for the SCell. The second CSI reference resource does not overlap with a time slot assigned to the PCell, for the CA.

[0383] In a different example of the embodiment, there is provided a method comprising transmitting, by a wireless device, a channel state information (CSI) report including a result of measurement based on a CSI reference resource for a first cell. The first cell is configured with a carrier aggregation (CA) which is based on switching between the first cell and a second cell. The CSI reference resource overlaps with a time slot assigned to the second cell for the CA, and the first cell is inactive during the time slot.

[0384] In a different example of the embodiment, there is provided a method comprising receiving, by a wireless device, one or more configuration parameters indicating: a low-band carrier aggregation (LB-CA) which is based on switching between a first cell and a second cell, and a measurement gap associated with the first cell. The method further comprises determining whether to transmit a channel state information (CSI) report for the first cell, based on whether a CSI reference resource, corresponding to the CSI report, overlaps with: a time slot assigned to the first cell for the LB-CA or a time slot assigned to the second cell for the LB-CA. The method further comprises, based on the determining, either: transmitting the CSI report or dropping the CSI report.Docket No.25-1079PCT

[0385] In a different example of the embodiment, there is provided a method comprising either transmitting or dropping, by a wireless device, a channel state information (C S I) report for a first cell, based on whether a CSI reference resource corresponding to the CSI report overlaps with: a time slot assigned to the first cell for a carrier aggregation (CA) which is based on switching between the first cell and a second cell or a time slot assigned to the second cell for the CA.

[0386] As mentioned above, there may be scenarios where LB-CA is configured for a first and a second LB-CA cell. More specifically, LB-CA may involve switching between the two cells. In such cases, the UE may be configured to communicate with the first LB-CA cell only during the first LB-CA time slots, and with the second LB-CA cell only during the second LB-CA time slots.

[0387] In this scenario, by configuring the CSI reference resource of the first LB-CA cell to avoid overlapping, in time domain, with any of the second LB-CA time slots allocated to the second LB-CA cell, the UE can reliably receive and measure a CSI reference signal of the first LB-CA cell, using the CSI reference resource, without interference caused by the UE attempting to communicate via the second LB-CA cell. This successful measurement of the CSI reference signal of the first LB-CA cell allows the UE to later establish a stable communication channel via the first LB-CA cell.

[0388] Alternatively, the UE may drop a CSI report for the first LB-CA cell if the corresponding CSI reference resource of the first LB-CA cell overlaps with any of the second LB-CA time slots allocated to the second LB-CA cell and / or if the CSI reference resource is invalid. This prevents potential conflicts between transmission of the CSI report for the first LB-CA cell and communication via the second LB-CA cell during the second LB-CA time slots, and thus enables the UE to maintain successful communication via the second LB-CA cell during the second LB-CA time slots.

[0389] There may also be scenarios where the second LB-CA cell is inactive while the UE is scheduled to receive and measure its CSI reference signal. Since this measurement is crucial for activating the second LB-CA cell, if the CSI reference resource overlaps with any of the first LB-CA time slots, the UE may prioritize receiving and measuring the CSI reference signal of the second LB-CA cell over communication via the first LB-CA cell. This prioritization ensures that the UE obtains the necessary CSI measurements to support proper activation of the second LB-CA cell.Alternatively, or additionally, the duration for activating the inactive second LB-CA cell may be determined based on the switching time for switching between the first and second LB-CA cells for LB-CA. This ensures the UE has sufficient time to activate the inactive second LB-CA cell, allowing to achieve a smooth and effective activation process.

[0390] FIG. 21 shows an exemplary scenario 2100 where the embodiment of this disclosure can be applied. In scenario 2100, UE 2110 is configured to communicate with a base station (BS) 2120 in / via a first cell (“1stCell”) and a second cell (“2ndCell"). In one example, the first cell is a primary cell (PCell) of UE 2110, and the second cell is a secondary cell (SCell) of UE 2110. In another example, the first cell is an SCell of UE 2110, and the second cell Isa PCell of UE 2110. In this disclosure, the expression “A / B” is used to mean "A and / or B.” For example, “communicating in / via the first cell” refers to communicating in, via, or both in and via the first cell. Accordingly, any instance of “communicating in” may be replaced with “communicating via,” and vice versa.Docket No. 25-1079PCT

[0391] Each of the first cell and the second cell may be configured with a carrier aggregation (CA) (e.g., a low-band carrier aggregation, also referred to as “LB-CA”) that is based on a CA switching pattern of switching between the first cell and the second cell. FIG. 21 shows an example of a CA switching pattern 2130. In this disclosure, the CA switching pattern may also be referred to as a time division multiplexing (TDM) pattern, a time domain multiplexing (TDM) pattern, a carrier switching (CS) pattern, or simply a CS. FIG. 17 shows details of an example of the CA switching pattern.

[0392] As shown in FIG. 21, according to CA switching pattern 2130, UE 2110 may communicate with BS 2120 via the first cell (but not via the second cell) during a first set of time slots 2122, 2126, and 2130, and via the second cell (but not via the first cell) during a second set of time slots 2124, 2128, and 2132. In other words, UE 2110 may communicate with BS 2120 in either the first or second cell in a time division manner. In this disclosure, the CA switching pattern may also be referred to as a time division multiplexing (TDM) pattern, a time domain multiplexing (TDM) pattern, a carrier switching (CS) pattern, or simply a CS.

[0393] Even though FIG. 21 shows that the length of a time interval allocated to either the first cell or the second cell for CA is same as the length of a slot (a.k.a., “a time slot”), the length of the time interval may be different from the length of a slot. As illustrated in FIG. 21, each slot consists of a certain number (e.g., 14) symbols 2104 (e.g., orthogonal frequency-division multiplexing (OFDM) symbols).

[0394] UE 2110 may be configured with a configuration of a CSI report (a.k.a., a “CSI report configuration”) that specifies one or more CSI reference resources. For example, as shown in FIG 21, UE 2110 is configured with a CSI report configuration for the first cell, which may indicate a first CSI reference resource candidate occupying symbol 2104a, a second CSI reference resource candidate occupying symbol 2104b, and a third CSI reference resource candidate occupying symbol 2104c. Although each CSI reference resource candidate spans a number of symbols (e.g., 1 or more) in the time domain and a number of subcarriers (e.g., 1 or more) in the frequency domain, FIG. 21 illustrates only the time-domain aspect for simplicity. Furthermore, while FIG. 21 depicts each CSI reference resource candidate as occupying the third symbol within each slot, in practice, a CSI reference resource candidate may occupy any one or more symbols within a slot. UE 2110 may select one of the CSI reference resource candidates as a CSI reference resource to use for receiving reference signal(s) (e.g., SSB, CSI-RS(s), etc.). For simple explanation purpose, in this disclosure, CS I - RS will be used as an example of the reference signal(s).

[0395] The CSI reference resource indicates the latest time at which UE 2110 can receive CSI-RS(s). Thus, UE 2110 may receive CSI-RS(s) before or at the time slot indicated by the CSI reference resource. In other words, UE 2110 may not receive any CSI-RS(s) during the time slot indicated by the CSI reference resource. However, for simple explanation purpose, in this disclosure, it will be assumed that UE 2110 receives a CSI-RS during a time slot indicated by the CSI-RS reference resource.

[0396] In scenario 2100 shown in FIG. 21, UE 2110 may select, as a CSI reference resource, a CSI reference resource candidate occupying symbol 2104b, to receive and measure a CSI reference signal (CSI-RS) 2102b, and transmit a CSI report 2106, for the first cell, indicating a result of the measurement of CSI-RS 2102b.Docket No.25-1079PCT

[0397] However, as shown in FIG. 21 , when UE 2110 is configured with CA based on CA switching pattern 2130, there may be instances where the selected CSI reference resource (e.g., the CSI reference resource candidate occupying symbol 2104b) overlaps with time slot 2124 allocated / assigned to the second cell for the CA. In this case, there is a conflict during time slot 2124, between receiving and measuring CSI-RS 2102b for CSI report 2106 for the first cell and communicating via the second cell. For instance, during time slot 2124, UE 2110 may be unable to measure CSI-RS 2102b (as indicated by the “X" mark in FIG. 21), as the time slot is allocated to UE 2110, according to CA switching pattern 2130, for communicating with BS 2120 via the second cell.

[0398] To address this issue, an example of the embodiment of this disclosure provides a method The method comprises receiving, by UE 2110, configuration parameter(s) (i.e., one or more configuration parameters) indicating carrier aggregation (CA) which is based on switching between the first and second cells— for example, according to CA switching pattern 2130. In one example, the configuration parameter(s) may indicate a configuration of a cell group comprising the first cell and the second cell, and the configuration of the cell group may indicate that the first and second cells are configured with CA that is based on switching between the first and second cells. Details of the configuration parameter(s) are explained with respect to FIG. 18.

[0399] The method further comprises transmitting a CSI report (e.g., CSI report 2106) based on a CSI reference resource that does not overlap with (i.e., does not fall within) a time slot allocated / assigned to the second cell for the CA. In this disclosure, the terms “allocated” and “assigned” are used interchangeably, as are “time slot” and “slot.”

[0400] More specifically, in one example, UE 2110 selects / determines a CSI reference resource, corresponding to the CSI report, from a list of CSI reference resource candidates (e.g., one or more slots). Each CSI reference resource candidate (e.g., the one or more slots) may be at K slot(s) before a slot where the wireless device transmits the CSI report. K may be determined based on a UE processing time required for the CSI report.

[0401] For example, K may be 0 or non-integer value for aperiodic CSI report. In another example, K may be a constant value for a periodic CSI report. The CSI reference resource may indicate of the latest slot from among one or more slots during which the wireless device may / can receive and measure a CSI reference signal (e.g., SSB, CSI-RS), via a CSI resource for the CSI report, of the first cell (i.e., for performing measurement on the selected CSI reference resource). In other words, after the slot indicated by the CSI reference resource, UE 2110 may not receive any CSI-RS (meaning that the slot indicated by the CSI reference resource is the last slot where UE 2110 can receive any CSI-RS).

[0402] In the example of FIG. 21 , UE 2110 may select / determine, from the CSI reference resource candidates, a CSI reference resource (e.g., slot 2126 that occurs K slot(s) before slot 2132, in the example, K is 3) that does not overlap with any time slot allocated to the second cell for the CA. As briefly mentioned above, during the time slot(s) allocated to the second cell for the CA, UE 2110 maybe unable to communicate with BS 2120 via the first cell, and thus UE 2110 may be unable to receive and measure the CSI-RS of the first cell. Thus, by determining (e.g., selecting) a CSI reference resource (e.g., the CSI reference resource occupying symbol 2140c) such that it does not overlap with any time slot allocated to the second cell for the CA, UE 2110 may receive and measure the CSI-RS successfully (i.e., perform measurement on the CSI-RS resource successfully) (as indicated by the mark “O” in FIG 21).Docket No.25-1079PCT

[0403] As explained above, in one example, in selecting a CSI reference resource for a CSI report (e.g., CSI report 2106) for the first cell, there is a restriction of not selecting the CSI reference resource that overlaps with any time slot allocated to the second cell for the CA. However, in a different example, there may be an additional restriction: the selected CSI reference resource may also be required not to overlap with a measurement gap associated with the first cell. In other words, UE 2110 may select a CSI reference resource that avoids overlapping with both any (ora time slot or one) of the time slots allocated to the second cell for CA and the measurement gap associated with the first cell. The rationale is that during the measurement gap associated with the first cell, UE 2110 may be restricted from communicating via either the first or the second cell, and may be limited to performing measurements for the first cell only. Therefore, the CSI reference resource for receiving and measuring the C SI- RS of the second cell should not overlap with the measurement gap associated with the first cell. In one example, the configuration parameter(s) that UE 2110 received indicate the measurement gap associated with the first cell. In another example, in addition or instead of any one or more of the above two conditions, there may be a different condition— that the CSI reference resource must be a downlink slot. Thus, in one example, UE 2110 may select / determine the CSI reference resource such that the CSI reference resources a) occurs K slot(s) before the CSI report; b) does not overlap with time slots assigned to the second cell; c) does not overlap with a measurement gap associated with the first cell; d) is a downlink slot.

[0404] As mentioned above, when UE 2110 selects a CSI reference resource for a CSI report for the first cell (e.g., CSI report 2106), the CSI reference resource is selected from a list of CSI reference resource candidates. In one example, this list of CSI reference resource candidates may be generated based on (or may be indicated by) the configuration parameter(s) (e.g., a CSI processing time, a minimum scheduling offset, reportConfigType of CSI-ReportConfig IE of the CSI report, reportQuantity, etc) that UE 2110 received.

[0405] In one example, the configuration parameter(s) may indicate a CSI report configuration of the first cell, and UE 2110 may select a CSI reference resource for a CSI report for the first cell, based on the CSI report configuration of the first cell. More specifically, in one example, the CSI report configuration of the first cell may indicate a plurality of CSI reference resource candidates for the first cell, and UE 2110 may select a CSI reference resource from among the plurality of CSI reference resource candidates.

[0406] After determining a CSI reference resource (e.g., the CSI reference resource occupying symbol 2104c) fora CSI report for the first cell, UE 2110 may perform a measurement on the CSI reference resource (e.g., receiving and measuring CSI-RS 2102c), and transmita CSI report (e.g., CSI report 2106) for the first cell. The transmitted CSI report may indicate a result of the measurement on the CSI reference resource.

[0407] There may be different ways of determining (e.g., selecting), for a CSI report for the first cell, a CSI reference resource (e.g., the CSI reference resource occupying symbol 2104c) that does not overlap with any (or a time slot or one) of the time slots allocated to the second cell (e.g., time slots 2124, 2128, and 2132). One of the ways is UE 2110 selecting a CSI reference resource for a CSI report for the first cell, based on 1) a number of CSI reference slots (e.g., ncsijef) and 2) a time duration during which the CSI report for the first cell is scheduled to be transmitted. Note that a frame is a numberof subframes within 10msec, where a subframe is Imsecwindow / duration. Each subframe mayDocket No. 25-1079PCThave 2Au number of slot(s), where u is 0 for 15 kHz subcarrier spacing of the first cell, 1 for 30 kHz, 2 for 60 kHz, 4 for 120 kHz, etc. In the specification, a subcarrier spacing of the first cell may be considered as 15 kHz (e.g., a subframe comprises a slot). It is extended to other subcarrier spacing e.g., based on a scaling the number of CSI reference slots (e.g., Kfor 15 kHz, K * 2Au for a subcarrier spacing that is 2Au * 15 kHz).

[0408] More specifically, in one example, UE 2110 may receive a downlink control command (e.g., RRC for P-CSI, MAC CE for SP-CSI, DCI for A-CSI) scheduling an uplink (UL) transmission comprising a CSI report for the first cell (e.g., CSI report 2106). As shown in FIG. 21, the UL transmission comprising CSI report 2106 is scheduled to be transmitted during a time slot 2132. After receiving the downlink control command, UE 2110 may select a CSI reference resource in a time slot that occurs at least a number of CSI reference slots (e.g., ncsi.ref) before the scheduled time slot (e.g., time slot 2132) for the uplink transmission containing the CSI report for the first cell.

[0409] For example, in scenario 2100 illustrated in FIG. 21, assume that the number of CSI reference slots (e.g., ncsLref. K) is three. In this case, slot 2126 (e.g., the beginning of slot 2126) occurs three slots before time slot 2132 (e.g., the beginning of slot 2132), during which the uplink transmission containing CSI report 2106 is scheduled. Accordingly, the CSI reference resource of slot 2126 (i.e., a slot occurring K slot(s) before the CSI report) is selected for generating CSI report 2106 for the first cell.

[0410] On the other hand, if the number of CSI reference slots (K) is four, then slot 2124 may be considered as the CSI reference resource, which occurs four slots before slot 2132 (e.g., a number of slots between the beginning of slot 2124 and the beginning of slot 2132 is four). Accordingly, the CSI reference resource candidate occupying symbol 2104b would be a candidate for the CSI reference resource. However, as previously explained, since the CSI reference resource candidate occupying symbol 2104b overlaps with slot 2124, which is allocated to the second cell for CA, it may be excluded from being selected for CSI report 2106. In this case, the CSI reference resource candidate occupying symbol 2104a, located in the nearest preceding slot not allocated to the second cell (i.e., slot 2122), is selected instead for generating CSI report 2106.

[0411] In one example, the number of CSI reference slots is not fixed. Rather, UE 2110 may determine the number of CSI reference slots, based on various factors. For instance, the number of CSI reference slots may depend on the type of CSI report. To illustrate how the number of CSI reference slots is determined, CSI report 2106 will be used as an example.

[0412] As discussed above, the configuration parameter(s) that UE 2110 receives may indicate the CSI report configuration. In one example, the CSI report configuration may comprise a field (e.g., the “reportConfigType" IE) indicating the type of CSI report 2106. In this example, UE 2110 may determine the number of CSI reference slots, based on whether the indicated type of CSI report 2106 is 1) either a periodic CSI report or a semi-persistent CSI report, or 2) an aperiodic CSI report.

[0413] More specifically, when the indicated type of CSI report 2106 is either a periodic CSI report (e.g., the "reportConfigType" IE = periodic) or a semi-persistent CSI report (e.g., the “reportConfigType'’ IE = semiPersistentPUSCH or semiPersistentPUCCH), UE 2110 may determine the number of CSI reference slots, basedDocket No. 25-1079PCTon whether the CSI report configuration indicates (or comprises a field indicating) CSI resources for both a channel measurement (e.g . , the "resourcesForChannelMeasuremenf IE being present in the "report config”') and an interference measurement (e.g., the "csi-IM-ResourcesForlnterference" IE or the “nzp-CSI-RS-ResourcesForlnterference” is absent). Note that in this disclosure, the term “based on” is used interchangeably with “when,” “if,” “in response to," and “in case.”

[0414] For instance, when the indicated type of CSI report 2106 is either a periodic CSI report or a semi-persistent CSI report, UE 2110 may determine that the number of CSI reference slots is a first value (e.g., 4 slots, or 4 * 2Au DL, e.g., 4 for 15 kHz, 8 for 30 kHz, 16 for 60 kHz, etc), based on the CSI report configuration indicates only CSI resource(s) for a channel measurement but not CSI resource(s) for an interference measurement, or a second value (e.g., 5 slots, or 5 *2AuDL, e.g., 5 for 15 kHz, 10 for 30 kHz, 20 for 60 kHz, etc) based on the CSI report configuration indicates both CSI resource(s) for a channel measurement and CSI resource(s) for an interference measurement.

[0415] On the other hand, when the indicated type of CSI report 2106 is an aperiodic CSI report (e.g., the “reportConfigType" IE = aperiodic), UE 2110 may determine the number of CSI reference slots, based on 1) CSI processing time (e.g., Z') and 2) a number of symbols (e.g., 14) included in a single time slot, if a slot of reception of a DCI triggering the aperiodic CSI report and a of the CSI report are different.

[0416] For example, UE 2110 may receive the DCI triggering the aperiodic CSI report. Based on the DCI, UE2110 may transmit the CSI report. The slot of the reception of the DCI may be same as the slot of the uplink transmission comprising the CSI report. In such a case, UE 2110 may determine the common slot (i.e., the same slot) as the CSI reference resource. Otherwise (i.e., the two slots are different), the below example embodiments may be applied.

[0417] UE 2110 may determine the number of CSI reference slots, based on 1) CSI processing time (e.g., Z’) and 2) the number of symbols (e.g., 14) included in a single time slot. In an example, the first cell is the secondary cell, and the second cell is the primary cell. UE 2110 may transmit the CSI report via the primary cell (the second cell) for the secondary cell (the first cell). In response to / based on a first DCI indicating / triggering a first CSI report for the secondary cell (e.g., the first cell), UE 2110 may determine that a slot, when UE 2110 receives the first DCI, and a slot, when UE 2110 transmits the first CSI report, are different. In contrast, in response to I based on a second DCI indicating / triggering a second CSI report for the primary cell (e.g., the second cell), UE 2110 may determine that a slot, when UE 2110 receives the second DCI, and a slot when UE 2110 transmits the second CSI report, maybe different or same. For example, the CSI processing time (Z1) may be determined based on whether the CSI report is for the primary cell or the secondary cell. For example, in case the CSI report is for the secondary cell and the secondary cell does not have an uplink carrier, UE 2110 may need to switch to the primary cell for transmitting the CSI report. Thus, the CSI processing time may require a low-band carrier aggregation (LB-CA) switching gap or a gap to switch from the secondary cell to the primary cell. Thus, the CSI processing (Z') may be increased by the LB-CA switching gap. For example, in a same scenario, a first CSI processing time for the primary cell is 28 symbols, for a second CSI processing time for the secondary cell may be 28 + G where G is a number of symbols for the LB-CA switching gap. In an example, a set of CSI processing times for the secondary cell may be determined based on a second set of CSIDocket No.25-1079PCTprocessing times for the primary cell, wherein each of the set of CSI processing time may be a sum of each of the second set of CSI processing times and G. The G may indicate the gap to switch from the secondary cell to the primary cell with a consideration of a maximum timing advance value of the primary cell. For example, the G may be configured by BS 2120. For example, the G may be pre-configured for each frequency range or a subcarrier spacing that the secondary cell is used / operating. For example, the G may be 4 in FR1 and / or with 15 kHz SCS. Alternatively, the G maybe added to the CSI processing time Z' for any CSI reportfor the secondary cell. UE 2110 may determine a value of the G, based on the gap to switch from the secondary cell to the primary cell. The gap may be determined I configured by BS 2120. The gap may comprise a RF tunning from the secondary cell to the primary cell and a timing advance value for the primary cell.

[0418] In order to determine the number of CSI reference slots when the indicated type of CSI report 2106 is an aperiodic CSI report, a comparison value may be used. More specifically, the number of CSI reference slots may be determined such that it is greater than or equal to the comparison value, and an latest CSI reference slot, that is one of candidate CSI reference resources and is positioned (or occurs) the number of CSI reference slots before a first slot where the CSI report is transmitted, must be valid and / or must satisfy condition(s). The earliest CSI reference slot may be referred as a CSI reference resource for the corresponding CSI report (i.e., the CSI report on the first slot e.g., slot 2132). The candidate CSI reference resources may comprise one or more slots that occurs before floor (Z714) slots from the first slot (slot 2132)

[0419] The condition(s) may comprise one or more of: the latest CSI reference slot is a downlink time slot, does not overlap with the measurement gap associated with the first cell, and / or does not overlap with a time slot allocated to the second cell for CA (and / or overlaps with a time slot allocated to the first cell for CA). In one example, the condition(s) are condition(s) for the earliest CSI reference slot to be valid.

[0420] For example, if Z' is 28 symbols, the comparison value is two, then the number of CSI reference slots may be two or more. In this case, the candidate CSI reference resources comprise slot 2128, 2126, 2124 and 2122, where each of the candidate CSI reference resources occurs two slots before slot 2132. A first number of CSI reference slots corresponding to slot 2128 is 2 (e.g., a gap between slot 2128 and slot 2132), and a second number of CSI reference slots corresponding to slot 2126 is 3 and so on. Among a list of number of CSI reference slots of the candidate CSI reference resources, the wireless device may select a smallest number, from the list of number of CSI reference slots, where corresponding slot satisfies the above mentioned condition(s). For example, the wireless device may not determine slot 2128 (e.g., the first number of CSI reference slots is 2) as the latest CSI reference slot as slot 2128 overlaps a time slot assigned to the second cell. The wireless device may determine slot 2126 (e.g., the second number of CSI reference slots is 3) as the latest CSI reference slot as it overlaps with a time slot assigned to the first cell. In this case, slot 2126 is the CSI reference resource, and the number of CSI reference slots is 3. The wireless device may determine latest CSI reference resource from the candidate CSI reference resources such that the number of reference CSI slots becomes a smallest among possible values for a corresponding CSI report.Docket No.25-1079PCT

[0421] Though not shown in FIG.21, in the example, it is assumed that slot 2126 is a downlink slot that does not overlap with the measurement gap associated with the first cell. In case, slot 2126 is not a downlink slot or overlaps with a measurement gap, UE 2110 may determine slot 2122 as the CSI reference resource that overlaps with a time slot assigned to the first cell. In this case, the number of CSI reference slots is 5.

[0422] Until UE 2110 identifies the latest slot satisfying the above mentioned condition(s), UE 2110 may compare / check each of the candidate CSI reference resources. It is noted that a minimum value that the number of CSI reference slots is determined based on Z’. The number of CSI reference slots may be determined as a smallest value greater than or equal than the comparison value, such that a slot, corresponding to the number of CSI reference slots, satisfying the above mentioned condition(s) (e.g., a downlink slot, not overlapping with a measurement gap, overlapping with a time slot assigned to the first cell for a CSI report for the first cell, overlapping with a time slot assigned to the second cell to a CSI report for the second cell).

[0423] In one example, the above method of determining the number of CSI reference slots when the indicated type of CSI report 2106 is an aperiodic CSI report can be summarized as follows:

[0424] First, UE 2110 obtains the comparison value.

[0425] Second, UE 2110 uses this comparison value as the initial number of CSI reference slots.

[0426] Third, UE 2110 checks whether the slot immediately preceding the earliest slot among the initial CSI reference slots (hereinafter referred to as the “first slot”) satisfies the required condition(s).

[0427] Fourth, if the first slot satisfies the condition(s), the comparison value is finalized as the number of CSI reference slots. If not, UE 2110 checks the slot immediately before the first slot (the “second slot”) to determine if it satisfies the condition(s).

[0428] Fifth, if the second slot satisfies the condition(s), the final number of CSI reference slots is set to comparison value + 1. If not, UE 2110 continues by checking the slot immediately preceding the second slot (the “third slot”).

[0429] Sixth, if the third slot satisfies the condition(s), the final number of CSI reference slots is set to comparison value + 2. If not, UE 2110 checks the slot immediately before the third slot (the “fourth slot”).

[0430] This checking process continues iteratively, with UE 2110 evaluating the slot immediately preceding the most recently checked slot, until a slot is found that satisfies the condition(s).

[0431] As mentioned above, the above method of determining the number of CSI reference slots when the indicated type of CSI report 2106 is an aperiodic CSI report is an example, and other method can be used for determining the number of CSI reference slots.

[0432] In one example, UE 2110 may determine the comparison value based on the CSI processing time and the I B Inumber of symbols included in a single slot. For instance, A = l-l, where A is the comparison value, B is the CSI processing time, and C is the number of symbols included in a single time slot.

[0433] As discussed above, in one example of the embodiment, UE 2110 may be configured to select a CSI reference resource for reporting CSI for the first cell such that the selected resource does not overlap with any timeDocket No.25-1079PCTslots allocated to the second cell for CA— i.e., time slots used by UE 2110 to communicate via the second cell.Similarly, UE 2110 may be configured to select / determine a CSI reference resource for reporting CSI for the second cell such that the selected resource does not overlap with any time slots allocated to the first cell for CA— i.e., time slots used by UE 2110 to communicate via the first cell. Note that a CSI report for the first cell or the second cell may be transmitted via / on the first cell (e.g. , a primary cell) or a third cell (e.g ., a PUCCH cell, a piggyback on a PUSCH).

[0434] In another example of the embodiment, UE 2110 may select a CSI reference resource for the first cell without enforcing this restriction (e.g., based on whether the CSI reference resource overlaps with a time slot allocated for the first cell or not) but if the selected resource overlaps with any time slots assigned to the second cell for CA, UE 2110 may drop the CSI report (i.e., it does not receive or measure the CS I -RS in the selected reference resource) for the first cell.

[0435] A method according this example of the embodiment may comprise either transmitting or dropping, by UE 2110, a CSI report (e.g., CSI report 2106) for the first cell, based on whether a CSI reference resource corresponding to the CSI report overlaps with any (or a time slot or one) of the time slots allocated to the first cell for CA or any (or a time slot or one) of the time slots allocated to the second cell for the CA.

[0436] More specifically, UE 2110 may determine whether to transmit the scheduled CSI report for the first cell, during a time duration, based on whether the CSI reference resource corresponding to the scheduled CSI report overlaps with any (or a time slot or one) of the time slots allocated to the first cell for CA or any (or a time slot or one) of the time slots allocated to the second cell for CA. Based on this determination, UE 2110 may drop or transmit the scheduled CSI report.

[0437] In one example, UE 2110 may transmit the scheduled CSI report for the first cell when the corresponding CSI reference resource overlaps with any (or a time slot or one) of the time slots allocated to the first cell for CA. On the contrary, UE 2110 may drop the scheduled CSI report for the first cell when the corresponding CSI reference resource overlaps with any (or a time slot or one) of the time slots allocated to the second cell for CA.

[0438] For instance, in scenario 2100, if CSI report 2106 is for the first cell and the CSI reference resource corresponding to CSI report 2106 is slot 2126 determined based on a number of CSI reference slots (e.g., 3), UE 2110 may transmit the scheduled CSI report 2106 for the first cell because the corresponding CSI reference resource overlaps with slot 2126 allocated to the first cell for CA. In one example, even when the corresponding CSI reference resource overlaps with slot 2126 allocated to the first cell for CA, if the corresponding CSI reference resource (e.g., slot 2126) overlaps with the measurement gap associated with the first cell, UE 2110 may skip or drop the scheduled CSI report 2106 for the first cell.

[0439] On the contrary, if CSI report 2106 is for the first cell and the CSI reference resource corresponding to CSI report 2106 is slot 2128 (e.g., a number of CSI reference slots is 2), UE 2110 may drop (and / or skip) the scheduled CSI report 2106 for the first cell because the corresponding CSI reference resource overlaps with slot 2128 allocated to the second cell for CA (and / or because the corresponding CSI reference resource overlaps with the measurement gap associated with the first cell).Docket No.25-1079PCT

[0440] This example embodiment may be used only for periodic CSI report and / or semi-periodic CSI report. For example, incase of periodic CSI, where a minimum number of CSI reference slots is 4, if a slot with an index n -4 overlaps with a time slot assigned to the second cell, UE 2110 may drop the periodic CSI report for the first cell. For aperiodic CSI report, UE 2110 may determine a number of CSI reference slots such that a corresponding slot or a CSI reference resource satisfies the above mentioned condition(s) (e.g., a slot is a downlink slot, is not overlapping with a measurement gap and is overlapping with a time duration assigned to the first cell).

[0441] Alternatively, this example may be used only for aperiodic CSI report. For example, UE 2110 may determine / select a slot as a CSI reference resource for the aperiodic CSI report based on 1 ) the slot is a downlink slot and; 2) the slot is not overlapping with a measurement gap. UE 2110 may not consider the CA switching pattern for the CSI reference resource for the aperiodic CSI report. If the determi ned / selected CSI reference resource overlaps with time duration assigned to the second cell, UE 2110 may drop the aperiodic CSI report. UE 2110 may determine / select a CSI reference resource for periodic CSI report or semi-persistent CSI report based on the above mentioned condition(s) (e.g., a slot is a downlink slot, is not overlapping with a measurement gap and is overlapping with a time duration assigned to the first cell).

[0442] In the example of the embodiment above, UE 2110 may drop a scheduled CSI report (e.g., CSI report 2106) for one cell if the corresponding CSI reference resource overlaps with any time slot allocated to another cell for CA. In other words, UE 2110 may prioritize performing communication via one cell— by following a CA switching pattern (e.g., CA switching pattern 2130)— over performing CSI-RS measurements for another cell.

[0443] In contrast, in another example of the embodiment, UE 2110 may prioritize performing CSI-RS measurements for one cell over performing communication via another cell by following a CA switching pattern (e.g., CA switching pattern 2130).

[0444] This type of prioritization may be particularly beneficial when the cell being measured is inactive. For instance, consider a case where a CSI report (e.g., CSI report 2106) is scheduled for the first cell (e.g., an SCell) that is currently inactive. In this scenario, performing the CSI-RS measurement for the first cell may be important— or even critical— for activating the first cell, as the measurement result could inform whether and how the first cell should be reactivated.

[0445] Accordingly, an example of the embodiment of this disclosure provides a method The method may comprise transmitting, by UE 2110, a CSI report including a result of measurement based on a CSI reference resource for the first cell (e.g., SCell) when the first cell is inactive, even if the CSI reference resource for the first cell overlaps with a (or any) time slot allocated to the second cell (e.g., PCell) for CA. In other words, regardless of whether the CSI reference resource for the first cell overlaps with a (or any) time slot allocated, for the CA, to the first cell or the second cell, UE 2110 may be configured to perform a measurement on the CSI resource for the first cell when the first cell in inactive or the first cell is being activated. For example, UE 2110 may perform activation of the first cell during an activation time duration. The activation time duration may comprise a delay to perform a CSI report. During the activation time, UE 2110 may be configured to perform a measurement on the CSI resource for the first cell, regardless of whether the CSIDocket No.25-1079PCTreference resource for the first cell overlaps with a (or any) time slot allocated, for the CA, to the first cell or the second cell.

[0446] In one example, UE 2110 may determine whether the first cell (e.g. , SCell) is inactive. If the first cell is inactive, UE 2110 may disregard the CA switching pattern and perform the CSI -RS measurement on the CSI reference resource during a given time slot— regardless of whether that time slot is allocated to the second cell for CA. Indeed, UE 2110 may ignore the CA switching pattern while the first cell remains inactive, and begin following the CA switching pattern once the first cell becomes active. For example, UE 2110 may receive a downlink control command (e.g., RRC, MAC CE, DCI) indicating an activation the first cell (e.g., the secondary cell) UE 2110 may transmit a HARQ-ACK feedback corresponding to the downlink control command at / during a first time. For example, UE 2110 may complete an activation of the first cell before a first time delay (e.g., a SCell activation delay) since the first time. UE 2110 may complete the activation of the first cell, based on / in response to transmitting a valid CSI report (e.g., via an uplink transmission) for the first cell. The valid CSI report may comprise a Continuous Quality Improvement (CQI) which value is non-out-of-range (e.g., a valid CQI). The first time delay may comprise delay to perform time and / or frequency tracking and report / transmit a valid CSI report.

[0447] During the first cell being inactive or being activated or during the first time delay (e.g., the SCell activation delay), UE 2110 may determine a slot as a CSI reference resource based on 1) the slot is a downlink slot and; 2) the slot is not overlapping with a measurement gap; and 3) the slot occurs before a smallest number of CSI reference slots (e.g., 4 *2Au in case of periodic CSI report with one CSI reference signal, floor (Z714) in case of aperiodic CSI report).

[0448] In some scenarios, UE 2110 may activate the first cell after, or in response to, transmitting the scheduled CSI report. Once the first cell is activated, and if UE 2110 needs to determine a new CSI reference resource for an additional CSI report for the first cell, it may select the new CSI reference resource to avoid overlapping with any time slot allocated to the second cell. During the first cell being active or after the first cell being activated, UE 2110 may determine a slot as a CSI reference resource based on 1 ) the slot is a downlink slot and; 2) the slot is not overlapping with a measurement gap; 3) the slot overlaps with a time duration assigned to the first cell based on the CS switching pattern; and 4) the slot occurs before a smallest number of CSI reference slots (e.g., 4 * 2Au in case of periodic CSI report with one CSI reference signal, floor (Z714) in case of aperiodic CSI report).

[0449] Alternatively, UE 2110 may simply drop the additional scheduled CSI report.

[0450] As explained above, in case the first cell is inactive, UE 2110 may perform a measurement on the corresponding CSI reference resource for a scheduled CSI report for the first cell, even when the CSI reference resource overlaps with a (or any) time slot allocated to the second cell for CA. However, in one example, the selection of the CSI reference resource may be subject to a restriction. For instance, the CSI reference resource does not (or should not) overlap with a physical uplink control channel (PUCCH) transmission which is via the primary cell (e.g., the second cell). If it overlaps with the PUCCH transmission which is via the primary cell, UE 2110 may drop the scheduled CSI report.Docket No. 25-1079PCT

[0451] In summary, when the first cell is being activated, UE 2110 may be configured to switch to the first cell during one or more measurement occasions for the first cell. UE 210 may be configured to stay on the second cell in other time occasions / slots. The one or more measurement occasions may be determined based on one or more slots where UE 2110 is configured to receive / monitor SSB(s) of the first cell and / or reference signals (e.g., SSB, CSI-RS) for CSI report(s) of the first cell. The CSI report(s) may comprise one or more periodic CSI reports for the first cell. For each measurement occasion of the one or more measurement occasions, UE 2110 is configured to switch to the first cell. For example, if each measurement occasion requires X symbols to monitor (e.g., 4 symbols of a SSB, or a slot comprising a SSB, X = 4, X = 1, X = 14), before a start of X symbols and / or after an end of X symbols, UE 2110 may switch from the second cell to the first cell and / or switch from the second cell to the second cell.

[0452] In an example, UE 2110 may receive the downlink control command (e.g., MAC CE) indicating the activation of the first cell at a first slot (e.g., a slot index = i). In response to receiving the downlink control command, in an example, UE 2110 may start to perform measurements on CSI reference signals for the one or more periodic CSI reports for the first cell. In this example, the one or more measurement occasions may comprise one or more slots and / or one or more transmission occasions of periodic CSI-RS / SSB resource, associated with the one or more periodic CSI reports, occurring after the first slot until the first cell is activated (or until the valid CSI report is sent).

[0453] In another example, UE 2110 may transmit a PUCCH transmission or an uplink transmission comprising a HARQ-ACK feedback corresponding to the downlink control command at a second slot (e.g., a slot index = n). UE 2110 may transmit, at / on the slot n, the PUCCH transmission or the uplink transmission fora PDSCH of the activation indication of the downlink control command. After K slots since the second slot (e.g., the slot n), UE 2110 may start to perform the one or more periodic CSI reports. K may be determined as 3 * 2Au + 1 (4 in case of 15 kHz subcarrier spacing). After / at n+K (e.g., 4 slots after transmitting the PUCCH or the HARQ-ACK feedback), UE 2110 starts to perform CSI measurement based on the one or more periodic CSI reports. In this example, the one or more measurement occasions may comprise one or more slots and / or one or more transmission occasions of periodic CSI-RS / SSB resource, associated with the one or more periodic CSI reports, occurring after a slot with an index of n+K (e.g., K slots after the second slot) until the first cell is activated (or until the valid CSI report is sent).

[0454] In another example, UE 2110 may complete time and / or frequency tracking for the first cell and may be ready for communicate via the first cell at a third slot that is occurring after the slot with the index n+K (e.g., K slots after the second slot). After / at the third slot (e.g., after being ready for measuring SSB / CSI-RS via the first cell), UE 2110 starts to perform CSI measurement based on the one or more periodic CSI reports. In this example, the one or more measurement occasions may comprise one or more slots and / or one or more transmission occasions of periodic CSI-RS / SSB resource, associated with the one or more periodic CSI reports, occurring after a slot with an index of n+K (e.g., K slots after the second slot) until the first cell is activated (or until the valid CSI report is sent).

[0455] In an example, if an accession, of the one or more measurement occasions overlap, with the uplink transmission of the valid CSI report, UE 2110 may skip measuring SSB / CSI-RS of the first cell during the occasion.Docket No.25-1079PCT

[0456] In an example, when a secondary cell deactivation timer (sCellDeactivationTimer) is configured for the first cell and the secondary cell deactivation timer expires, UE 2110 may skip switching to the first cell after the secondary cell deactivation timer expires. UE 2110 may not perform CSI measurements on / for the first cell in response to the secondary cell deactivation timer expires.

[0457] FIG. 24 shows a method 2400 according to an example of the embodiment. Method 2400 may begin with step 2402. Step 2402 comprises receiving, by a wireless device, one or more configuration parameters indicating a carrier aggregation (CA) (e.g., a low-band CA (“LB-CA”)) which is based on switching between a first cell and a second cell. Step 2404 comprises transmitting a CSI report for the first cell. The CSI report is based on a channel state information (CSI) reference resource which does not overlap with (e.g., does not fall within) a time slot (e.g., any time slot) allocated to the second cell for the CA.

[0458] In this disclosure, the terms “allocated” and “assigned” are used interchangeably, as are “time slot” and “slot.” Accordingly, any instance of “allocated” may be substituted with “assigned,” and any instance of “time slot” may be substituted with “slot."

[0459] In this disclosure, carrier aggregation (CA) based on switching between the first and second cells may be referred to as time division multiplexing (TDM). The switching pattern between the two cells may be described as a TDM pattern or a carrier aggregation (CA) switching pattern.

[0460] In this disclosure, the term “based on” is intended to encompass the meanings of “if,” “when,” “in response to," and “only if.” Accordingly, any use of “based on” may be interpreted or substituted with any of these expressions, as appropriate.

[0461] In one example, the one or more configuration parameters indicate a measurement gap associated with the first cell; and the CSI reference resource does not overlap with the measurement gap associated with the first cell.

[0462] In one example, the one or more configuration parameters indicate a CSI report configuration of the first cell; and the method comprises determining, based on the CSI report configuration of the first cell, the CSI reference resource for the CSI report for the first cell.

[0463] In one example, the method comprises performing a measurement based on the CSI reference resource; and transmitting the CSI report, for the first cell, indicating a result of the measurement on the CSI reference resource.

[0464] In one example, the performing the measurement on one or more CSI resources (e.g., resource of receiving one or more CSI-RSs and / or SSBs) wherein the one or more CSI resources occurring...

Claims

1. Docket No.25-1079PCTCLAIMS1. A method comprising:receiving, by a wireless device, one or more configuration parameters comprising:a low-band carrier aggregation (LB-CA) switching pattern of a carrier switching between a primary cell (PCell) and a secondary cell (SCell); anda configuration of one or more channel state information reference signals (CSI-RSs) of the SCell; receiving, during a first slot, a medium access control (MAC) control element (CE) indicating an activation of the SCell;based on receiving the MAC CE indicating the activation of the SCell, starting to apply the LB-CA switching pattern during a second slot that is after the first slot, wherein the second slot is based on:the first slot during which the MAC CE indicating the activation of the SCell is received; and a hybrid automatic repeat request (HARQ) feedback time for transmitting a HARQ-Acknowledgement feedback (HARQ-AC K) corresponding to the MAC CE;during a time duration, allocated to the SCell, in the LB-CA switching pattern, receiving and / or measuring the one or more CSI-RSs of the SCell; andbased on the receiving the MAC CE indicating the activation of the SCell, transmitting a CSI report of the one or more CSI-RSs of the SCell.

2. A method comprising:receiving, by a wireless device, one or more first messages indicating a switching pattern of a carrier switching between a first cell and a second cell;receiving a second message indicating an activation of the second cell; andbased on receiving the second message indicating the activation of the second cell, starting to apply the switching pattern.

3. The method of claim 2, wherein:the second message is received by the wireless device during a first time duration; andthe switching pattern is started to be applied by the wireless device during a second time duration that is after the first time duration; andthe second time duration is based on the first time duration.

4. The method of claim 3, wherein:the first time duration is a first slot; andthe second time duration is a second slot.

5. The method of claim 3 or 4, wherein the second time duration is based on:the first time duration during which the second message indicating the activation of the second cell is received; andDocket No. 25-1079PCTa hybrid automatic repeat request (HARQ) feedback time for transmitting a HARQ-Acknowledgement feedback (HARQ-ACK) corresponding to the second message.

6. The method of any one of claims 2-5, wherein the second message is a medium access control (MAC) control element (CE).

7. The method of any one of claims 2-6, wherein:the first cell is a primary cell (PCell); andthe second cell is a secondary cell (SCell).

8. The method of any one of claims 2-7, wherein the one or more first messages comprise one or more configuration parameters comprising:the carrier switching pattern of the carrier switching between the first cell and the second cell; and a configuration of one or more channel state information reference signals (CSI-RSs) of the second cell.

9. The method of claim 8, further comprising:during a time duration, allocated to the second cell, in the switching pattern, receiving and / or measuring the one or more CSI-RSs of the second cell; andbased on the receiving the second message indicating the activation of the second cell, transmitting a CSI report of the one or more CSI-RSs of the second cell.

10. The method of any one of claims 2-9, wherein the carrier switching pattern is a low-band carrier aggregation (LB- CA) switching pattern.

11. The method of any one of claims 3-10, wherein the second time duration is further based on:a constant delay of 3 msec; anda processing delay of 1 msec.

12. The method of claim 11 , wherein the second time duration is after a sum, of the HARQ feedback time, the constant delay and the processing delay, from the first time duration.

13. The method of any one of claims 5-12, wherein:the HARQ feedback time is in a number of slots;the constant delay is in a number of slots in 3msec; andthe processing delay is a number of slots in 1msec.

14. The method of claim 13, wherein a size of a slot is 1 msec.

15. The method of any one of claims 2-14, wherein a subcarrier spacing of the second cell is 15 kHz.

16. The method of any one of claims 2-15, wherein a subcarrier spacing of the first cell is 15 kHz.

17. The method of any one of claims 2-16, wherein the switching pattern indicates:a first plurality of slots, allocated to the first cell, during which the wireless device is configured to communicate in the first cell; anda second plurality of slots, allocated to the second cell, during which the wireless device is configured to communicate in the second cell.Docket No. 25-1079PCT18. The method of any one of claims 9-17, wherein:the time duration allocated to the second cell in the switching pattern comprises one or more slots; and each slot, of the one or more slots, is assigned to the second cell in the switching pattern.

19. The method of claim 17 or 18, wherein the time duration allocated to the second cell in the switching pattern overlaps with at least one of the second plurality of slots.

20. The method of any one of claims 9-19, wherein the time duration allocated to the second cell in the switching pattern occurs:no earlier than the second time duration; andno later than a third time duration, wherein the third time duration is based on:the first time duration during which the second message indicating the activation of the second cell is received;the HARQ feedback time for transmitting HARQ-ACK corresponding to the second message; an activation delay for the activation of the second cell; anda CSI reporting delay for the CSI report.

21. The method of claim 20, wherein the third time duration is after a sum, of the HARQ feedback time, the activation delay, and the CSI reporting delay, from the first time duration.

22. The method of claim 20 or 21, wherein the CSI reporting delay comprises one or more of:a first delay to measure or acquire a first available CSI reference resource; anda second delay of a user equipment (UE) processing time for the CSI report.

23. The method of claim 22, wherein the first available CSI reference resource overlaps with the time duration allocated to the second cell in the switching pattern and / or the second plurality of slots.

24. The method of any one of claims 9-23, wherein:the CSI report comprises a measurement result of the one or more CSI-RSs of the second cell; and the measurement result of the one or more CSI-RSs of the second cell comprises a CSI.

25. The method of any one of claims 9-24, wherein the one or more CSI-RSs are one or more periodic CSI-RSs or aperiodic CSI-RSs.

26. The method of any one of claims 2-25, wherein the switching pattern is started to be applied, based on receiving the second message indicating the activation of the second cell, before performing one or more actions corresponding to the activation of the second cell.

27. The method of claim 26, wherein the performing the one or more actions comprise at least one of:the receiving and / or the measuring of the one or more CSI-RSs of the second cell; andthe transmitting of the CSI report of the one or more CSI-RS of the second cell.

28. The method of clai m 27 , where! n :the CSI report is based on the receiving and / or the measuring of the one or more CSI-RSs of the second cell; andDocket No.25-1079PCTthe method further comprises receiving and / or monitoring one or more synchronization signal block(s) of the second cell.

29. A method comprising:receiving, by a wireless device, one or more configuration parameters indicating:a low-band carrier aggregation (LB-CA) switching pattern of a carrier switching between a first cell and a second cell;a channel state information (CSI) report configuration of the first cell; anda measurement gap associated with the first cell;based on the CSI report configuration of the first cell, determining a CSI reference resource for a CSI report for the first cell, wherein the CSI reference resource does not overlap with:the measurement gap associated with the first cell; anda time slot, allocated to the second cell, in the LB-CA switching pattern;performing a measurement on the CSI reference resource; andtransmitting the CSI report, for the first cell, indicating a result of the measurement on the CSI reference resource.

30. A method comprising transmitting, by a wireless device, a channel state information (CSI) report for a first cell, wherein:the CSI report for the first cell indicates a result of a measurement on a CSI reference resource; and the CSI reference resource does not overlap with a time slot allocated, to a second cell, in a switching pattern of a carrier switching between the first cell and the second cell.

31. The method of claim 30, further comprising receiving, by the wireless device, one or more configuration parameters indicating:the switching pattern of the carrier switching between the first cell and the second cell;a CSI report configuration of the first cell; anda measurement gap associated with the first cell.

32. The method of claim 31 , wherein the CSI reference resource does not overlap with the measurement gap associated with the first cell.

33. The method of claim 31 or 32, further comprising, based on the CSI report configuration of the first cell, determining the CSI reference resource for the CSI report for the first cell.

34. The method of any one of claims 30-33, further comprising performing the measurement on the CSI reference resource.

35. The method of any one of claims 30-34, wherein the carrier switching pattern is a low-band carrier aggregation (LB-CA) switching pattern.Docket No.25-1079PCT36. The method of any one of claims 30-35, comprising receiving a downlink control command scheduling an uplink (UL) transmission comprising the CSI report, wherein the UL transmission is scheduled to be transmitted during a first time duration.

37. The method of any one of claims 30-36, wherein:the CSI reference resource overlaps with a second time duration; andthe second time duration is at least a number of CSI reference slots before the first time duration.

38. The method of claim 37, wherein a gap or a number of slots between a beginning of the second time duration and a beginning of the first time duration is equal to the number of CSI reference slots.

39. The method of any one of claims 30-38, wherein:the time slot, allocated to the second cell, in the switching pattern does not overlap with a carrier switching gap; andthe wireless device is configured to switch between the first cell and the second cell during the carrier switching gap.

40. The method of any one of claims 30-39, wherein the time slot, allocated to the second cell, in the switching pattern does not overlap with a second time slot, allocated to the first cell, in the switching pattern.

41. The method of any one of claims 30-40, further comprising communicating via the second cell during the time slot, allocated to the second cell, in the switching pattern, wherein the communicating comprises:transmitting one or more UL signals via the second cell; and / orreceiving one or more DL signals via the second cell.

42. The method of any one of claims 30-41, wherein:the CSI report configuration of the first cell indicates a type of the CSI report;the type of the CSI report is either a periodic CSI report or a semi-persistent CSI report;the CSI report configuration comprises a field indicating one or more CSI resources for a channel measurement;the CSI report configuration does not indicate any CSI resource for an interference measurement; and a number of CSI reference slots is a first number of slots.

43. The method of claim 42, further comprising determining the number of CSI reference slots, based on the indicated type of the CSI report being aperiodic CSI report.

44. The method of claim 42 or 43, wherein the number of CSI reference slots is the first number of slots, based on one or more of:the indicated type of the CSI report is either a periodic CSI report or a semi-persistent CSI report;the CSI report configuration comprising a field indicating one or more CSI resources for a channel measurement; andthe CSI report configuration not indicating any CSI resource for an interference measurement.Docket No.25-1079PCT45. The method of any one of claims 36-44, wherein the downlink control command comprises one or more of: a radio resource control message, a downlink control information (DCI), a medium access control control element (MAC CE), and aperiodic CSI triggering.

46. 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 -45.

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