RRM measurement in carrier switching scenario

Abstract

A method comprises performing, by a wireless device and during a time duration, a link recovery, wherein the time duration is based on a first number of candidate beam detection, (CBD) reference signal (CBD-RS) resource occasions, within a time window, overlapping with one or more slots, assigned to a first cell, based on a switching pattern for switching between the first cell and a second cell.

Description

Docket No.: 25-1062PCTTITLE RRM Measurement in Carrier Switching ScenarioCROSS-REFERENCE TO RELATED APPLICATIONS

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0021] FIG. 15 illustrates an example of a wireless device in communication with a base stationDocket No.: 25-1062PCT

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

[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] FIG. 22 illustrates an aspect of an example embodiment according to the present disclosure.

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

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

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

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

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

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

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

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

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

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

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

[0040] 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 theDocket No.: 25-1062PCTabove, 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.

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

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

[0043] If A and B are sets and every element of A is an element of B, A is called a subset of B. In this specification, only non-emptysetsand subsets are considered. For example, possible subsetsof B = {celH, cell2} are: {celH}, {cell2}, and {cell 1 , cell2}. The phrase “based on” (or equally “based at least on”) is indicative that the phrase following the term “based on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “in response to” (or equally “in response at least to”) is indicative that the phrase following the phrase “in response to” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “depending on” (or equally “depending at least to”) is indicative that the phrase following the phrase “depending on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “employing / using” (or equally “employing / using at least') is indicative that the phrase following the phraseDocket No.: 25-1062PCT“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.

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

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

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

[0047] 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,Docket No.: 25-1062PCTC++ 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.

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

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

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

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

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

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

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

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

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

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

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

[0059] As illustrated in FIG. 1B, the 5G-CN 152 includes an Access and Mobility Management Function (AMF) 158A and a User Plane Function (UPF) 158B, which are shown as one component AMF / U PF 158 in FIG. 1B for ease 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.

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

[0061] 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), anDocket No.: 25-1062PCTNR 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).

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

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

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

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

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

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

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

[0069] 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 (SDAP) layers (SDAPs) 215 and 225. Together, these four protocols may make up layer 2, or the data link layer, of the OSI model.

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

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

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

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

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

[0075] 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 211Docket No.: 25-1062PCTand 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 MAGs 212 and 222.

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

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

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

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

[0080] FIG. 4B further illustrates MAC control elements (CEs) inserted into the MAC PDU by a MAC, such as MAC 223 or MAC 222. For example, FIG. 4B illustrates two MAC CEs inserted into the MAC PDU. MAC CEs may be inserted at the beginning of a MAC PDU for downlink transmissions (as shown in FIG. 4B) and at the end of a MAC PDU for uplink transmissions. MAC CEs maybe used for in-band control signaling. Example MAC CEs include: scheduling-related MAC CEs, such as buffer status reports and power headroom reports; activation / deactivation MAC CEs, such as those for activation / deactivation of PDCP duplication detection, channel state information (CSI) reporting, sounding reference signal (SRS) transmission, and prior configured components; discontinuous reception (DRX)Docket No.: 25-1062PCTrelated 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0094] 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 theDocket No.: 25-1062PCTcontrol 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:

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

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

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

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

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

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

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

[0102] FIG. 2B illustrates an example NR control plane protocol stack. As shown in FIG. 2B, the NR control plane protocol stack may use the same / similar first four protocol layers as the example NR user plane protocol stack. These four protocol layers include the PHYs 211 and 221, the 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

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

[0104] 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 beDocket No.: 25-1062PCTtransmitted 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 (RLE); 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.

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

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

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

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

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

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

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

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

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

[0114] In NR, the physical signals and physical channels (discussed with respect to FIG. 5A and FIG. 5B) may be mapped onto orthogonal frequency divisional multiplexing (OFDM) symbols. OFDM is a multicarrier communication scheme that transmits data over F orthogonal subcarriers (or tones). Before transmission, the data may be mapped to a series of complex symbols (e.g., M-quadrature amplitude modulation (M-QAM) or M-phase shift keying (M-PSK) symbols), referred to as source symbols, and divided into F parallel symbol streams. The F parallel symbol streams may be treated as though they are in the frequency domain and used as inputs to an Inverse Fast Fourier Transform (IFFT) block that transforms them into the time domain. The IFFT block may take in F source symbols at a time, one from each of the F parallel symbol streams, and use each source symbol to modulate the amplitude and phase of one of F sinusoidal basis functions that correspond to the F orthogonal subcarriers. The output of the IFFT block may be F time-domain samples that represent the summation of the F orthogonal subcarriers. The F time-domain samples may form a single OFDM symbol. After some processing (e.g., addition of a cyclic prefix) and up-conversion, an OFDM symbol provided by the IFFT block 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.

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

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

[0117] 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 subcarrierDocket No.: 25-1062PCTspacing 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.

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

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

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

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

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

[0123] For a downlink BWP in a set of configured downlink BWPs on a primary cell (PCell), a base station may configure a UE with one or more control resource sets (CORESETs) for at least one search space. A search space is a set of locations in the time and frequency domains where the UE may find control information. The search space may be a UE-specific search space or a common search space (potentially usable by a plurality of UEs). For example, aDocket No.: 25-1062PCTbase 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.

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

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

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

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

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

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

[0130] FIG. 9 illustrates an example of bandwidth adaptation using three configured BWPs for an NR carrier. A UE configured with the three BWPs may switch from one BWP to another BWP ata switching point. In the example illustrated in FIG. 9, the BWPs include: a BWP 902 with a bandwidth of 40 MHz and a subcarrier spacing of 15 kHz; a BWP 904 with a bandwidth of 10 MHz and a subcarrier spacing of 15 kHz; and a BWP 906 with a bandwidth of 20 MHzDocket No.: 25-1062PCTand 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.

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

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

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

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

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

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

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

[0138] 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 may become overloaded. By dividing transmissions of UCI between the PCell 1021 and the PSCell 1061, overloading may be prevented.

[0139] 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, theDocket No.: 25-1062PCTdisclosure 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.

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

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

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

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

[0144] The location of the SS / PBCH block in the time and frequency domains may not be known to the UE (e.g., if the UE is searching for the cell). To find and select the cell, the UE may monitor a carrier for the PSS. For example, the UE may monitor a frequency location within the carrier. If the PSS is not found after a certain duration (e.g., 20 ms), the UE may search for the PSS at a different frequency location within the carrier, as indicated by a synchronization raster. If the PSS is found at a location in the time and frequency domains, the UE may determine, based on a known structure of the SS / PBCH block, the locations of the SSS and the PBCH, respectively. The SS / PBCH block may be a cell-Docket No.: 25-1062PCTdefining 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.

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

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

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

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

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

[0150] 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 measureDocket No.: 25-1062PCTthe 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.

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

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

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

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

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

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

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

[0158] 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 symbolsofa PUSCH and / or a PUCCH. The base station may semi-statically configure the UE with a number (e.g., maximum number) of front-loaded DMRS symbols for the PUSCH and / or the PUCCH, which the UE may use to schedule a single-symbol DMRS and / or a double-symbol DMRS. An NR network may support (e.g., for cyclic prefix orthogonal frequency division multiplexing (CP-OFDM)) a common DMRS structure for downlink and uplink, wherein a DMRS location, a DMRS pattern, and / or a scrambling sequence for the DMRS may be the same or different.

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

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

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

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

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

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

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

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

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

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

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

[0170] 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 ofDocket No.: 25-1062PCTone 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.

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

[0172] 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 (QC Led) with one or more DM-RSs of a channel (e.g., a control channel, a shared data channel, and / or the like). The RS resource and the one or more DMRSs of the channel may be QCLed when the channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameter, fading, and / or the like) from a transmission via the RS resource to the UE are similar or the same as the channel characteristics from a transmission via the channel to the UE.

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

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

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

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

[0177] 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).Docket No.: 25-1062PCT

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

[0179] 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-OccasionLisf) may indicate an association between the PRACH occasions and the one or more reference signals.

[0180] The UE may perform a preamble retransmission if no response is received following a preamble transmission. The UE may increase an uplink transmit power for the preamble retransmission. The UE may select an initial preamble transmit power based on a pathloss measurement and / or a target received preamble power configured by the network. The UE may determine to retransmit a preamble and may ramp up the uplink transmit power The UE may receive one or more RACH parameters (e.g., PREAMBLE_POWER_RAMPING_STEP indicating a ramping step for the preamble retransmission. The ramping step may be an amount of incremental increase in uplink transmit power for a retransmission. The UE may ramp up the uplink transmit power if the UE determines a reference signal (e.g., SSB and / or CSI-RS) that is the same as a previous preamble transmission. The UE may count a number of preamble transmissions and / or retransmissions (e.g., PREAMBLE EANSMISSION-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., preambieTransMax;'.

[0181] 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 randomDocket No.: 25-1062PCTaccess 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 maybe used by the UE to adjust the UE's transmission timing, a scheduling grant for transmission of the Msg 31313, and / or a Temporary Cell RNTI (TC-RNTI). After transmitting a preamble, the UE may start a time window (e.g., ra-ResponseWndow) 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:

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

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

[0184] The Msg 41314 may be received after or in response to the transmitting of the Msg 31313. If a C-RNTI was included in the Msg 31313, the base station will address the UE on the PDCCH using the C-RNTI. If the UE's unique C-RNTI is detected on the PDCCH, the random access procedure is determined to be successfully completed. If a TC-RNTI is included in the Msg 31313 (e.g., if the UE is in an RRC_IDLE state or not otherwise connected to the base station), Msg 41314 will be received using a DL-SCH associated with the TC-RNTI. If a MAC PDU is successfully decoded and a MAC PDU comprises the UE contention resolution identity MAC CE that matches or otherwiseDocket No.: 25-1062PCTcorresponds 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.

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

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

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

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

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

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

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

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

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

[0194] 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 controlDocket No.: 25-1062PCTsignaling 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.

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

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

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

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

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

[0200] FIG. 14A illustrates an example of CORESET configurations fora 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.

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

[0202] The base station may transmit, to the UE, RRC messages comprising configuration parameters of one or more CORESETs and one or more search space sets. The configuration parameters may indicate an association between a search space set and a CORESET. A search space set may comprise a set of PDCCH candidates formed by CCEs ata given aggregation level. The configuration parameters may indicate: a number of PDCCH candidates to be monitored per aggregation level; a PDCCH monitoring periodicity and a PDCCH monitoring pattern; one or more DCI formats to be monitored by the UE; and / or whether a search space set is a common search space set or a UE-Docket No.: 25-1062PCTspecific 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).

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

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

[0205] 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 twoDocket No.: 25-1062PCTOFDM 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.

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

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

[0208] 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 may1Docket No.: 25-1062PCTinclude more than one UE and / or more than one base station, with the same or similar configuration as those shown in FIG. 15.

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

[0210] In the downlink, data to be sent to the wireless device 1502 from the base station 1504 may be provided to the processing system 1508 of the base station 1504. The data may be provided to the processing system 1508 by, for example, a core network. In the uplink, data to be sent to the base station 1504 from the wireless device 1502 maybe provided to the processing system 1518 of the wireless device 1502. The processing system 1508 and the processing system 1518 may implement layer 3 and layer 2 OSI functionality to process the data for transmission. Layer 2 may include an SDAP layer, a PDCP layer, an RLC layer, and a MAC layer, for example, with respect to FIG. 2A, FIG. 2B, FIG. 3, and FIG. 4A. Layer 3 may include an RRC layer as with respect to FIG. 2B.

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

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

[0213] 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 (eg., 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.Docket No.: 25-1062PCT

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

[0215] The processing system 1508 and / or the processing system 1518 may comprise one or more controllers and / or one or more processors. The one or more controllers and / or one or more processors may comprise, for example, a general-purpose processor, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) and / or other programmable logic device, discrete gate and / or transistor logic, discrete hardware components, an on-board unit, or any combination thereof. The processing system 1508 and / or the processing system 1518 may perform at least one of signal coding / processing, data processing, power control, input / output processing, and / or any other functionality that may enable the wireless device 1502 and the base station 1504 to operate in a wireless environment.

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

[0217] 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-valuedDocket No.: 25-1062PCTmodulation 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.

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

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

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

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

[0222] 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 toDocket No.: 25-1062PCTmeasure 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.

[0223] 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 the second frequency band. The wireless device may support reception via the first frequency band or the second frequency band at a time duration.

[0224] 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 (or a carrier switching (CS) mechanism / procedure / pattern, a TDM-ed CS mechanism / procedure / pattern, etc.). In the specification, the carrier aggregation of the first carrier and the second carrier based on the TDM mechanism / pattern (e.g., Carrier Switching pattern / procedure / mechanism) maybe referred as 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, CS, PCell-SCell CS, Linked CS cells, a low band carrier aggregation with a switching, etc.

[0225] In the specification, a carrier may refer a cell. A carrier switching between a first carrier and a second carrier is interchangeably used with a carrier switching between a first cell and a second cell. The first cell may comprise the first carrier. The first cell may be same as the first carrier. The second cell may comprise the second carrier. The second cell may be same as the second carrier.

[0226] FIG. 17 illustrates an example as per an aspect of an embodiment of the present disclosure. A base station (BS 2020) may operate (at least) 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. BS 2020 may configure a first carrier (Carrier#0130) in the first frequency band. The first carrier (Carrier © 130) may be a downlink carrier. BS 2020 may configure a second carrier (Carrier#1 140) in theDocket No.: 25-1062PCTsecond frequency band The second carrier (Carrier#1 140) may be a downlink carrier. BS 2020 may configure an uplink carrier (CarrierffO 130) in the first frequency band. The first carrier (CarriertfO 130) may comprise the downlink carrier and the uplink carrier. BS 2020 may configure a first cell that is a serving cell for a wireless device (UE 2010). The first cell may comprise the first carrier and the uplink carrier. BS 2020 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. In the example, the first cell is associated with the first carrier and / or the uplink carrier. The second cell is associated with the second carrier and / or a second uplink carrier. The first cell may be a primary cell of a cell group (e.g . , sPCell, PSCell, PCell), 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 may be configured with one or more CSSs (common search space sets). The wireless device may monitor SI-RNTI, P-RNTI, etc. via PDCCH candidates of the one or more CSSs of the first cell. 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.

[0227] The wireless device (UE 2010) may not support simultaneous reception via the first carrier and the second carrier. The wireless device (UE 2010) may support switching between the first carrier and the second carrier with a switching time less than a slot. The wireless device may indicate / transmit a capability (eg., carrierSwitchingSupport) for a band combination of the first frequency band and the second frequency band. Based on the capability, the base station may configure a carrier switching between the first carrier and the second carrier. In a time duration (e.g., a slot), the wireless device may receive either via the first carrier or the second carrier, wherein the time duration is not fully overlapping with a switching delay to switch between two carriers (e.g., from the first carrier / cell to the second carrier / cell or vice versa).

[0228] BS 2020 may configure / indicate a TDM pattern (e.g., a carrier switching pattern) (e.g., tdm-pattern-carrier-switching, carrier-switching-patern, CSpattern, csPattern, CS-TDMPatiern). For example, the wireless device (UE 2010) 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 a TDM pattern (e.g., a carrier 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 2010 may be expected to or may communicate with BS 2020 via Carrier #0130 (e.g., the first carrier) during the first time durations 1707.

[0229] The wireless device and the base station may apply / use the second case (Case 21705) during a second plurality of time durations (e.g., second time durations 1709) of the TDM pattern (e.g., the carrier switching pattern). ForDocket No.: 25-1062PCTexample, the second plurality of time durations (hereinafter second time durations 1709) may comprise slot n+1 and slot n+3 in FIG. 17. UE 2010 may be expected to or may be configured to or may communicate with BS 2020 via Carrier #1 140 during the second time durations 1709.

[0230] Based on the TDM pattern (e.g., the carrier switching pattern), the first plurality of time durations (e.g., the first time durations) and the second plurality of time durations (e.g., the second time durations) may not overlap in time. For example, a time duration 1701 may be a slot based on a subcarrier spacing (SCS) of the first cell or the first carrier. For example, the time duration 1701 may be k1 slot(s) based on one or more of: 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., CSPatternDuration) of the k1 (e.g., a size of a time duration in the TDM pattern / CS pattern).

[0231] 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. For example, the wireless device may perform the first case during the first time durations In Case 1 1703, UE 2010 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 maybe further configured / expected / required not to (or may not perform) receive downlink signal(s) via the second carrier / Carrier #1 140. The wireless device may not receive downlink signal(s) via the second carrier / Carrier#1 140 during the first time durations of the TDM / CS pattern.

[0232] 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 modulation reference signal (DM-RS), physical broadcast channel (PBCH), phase tracking reference signal (PT-RS), paging reference signal (PRS), measurement reference signals (e.g., LTM-CSI-RS), Msg B PDSCH, RAR, Msg 4 PDSCH, etc.

[0233] 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, PRACH, Msg1, MsgA, MsgA PUSCH, Msg 3 PUSCH, etc.

[0234] 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 and may be configured / expected / required not to (or may not perform) transmit uplink signals via the uplink carrier. The wireless device may not receive or transmit via the first cell based on the second case. In the example, the wireless device may not receive or transmit via the first cell during the second time durations of the TDM / CS pattern. In Case 21705, UE 2010 may be configured to skip reception and transmission via Carrier #0130. Based on the second case (in Case 2Docket No.: 25-1062PCT1705), the wireless device may be further configured / expected / required to (or may perform) receive downlink signal(s) via the second carrier / cell. In Case 21705, UE 2010 may be configured to perform receiving downlink signals via Carrier#1 140. In the example, UE 2010 may be configured to perform receiving downlink signals via Carrier#1 140 during the second time durations of the TDM / CS pattern.

[0235] In the example, the wireless device may not perform any of the Case 1 or Case 2 during a switching time 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. In another example, the switching time may be of the second time durations. The wireless device may skip receiving via the Carrier #1 140 during the switching gap of the second time durations.

[0236] Alternati vely / additional ly / optional ly, if a wireless device supports simultaneous operation via the first carrier and the second carrier 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.

[0237] In an example, the carrier aggregation / switching (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 2020 may operate / configure the first carrier of the first cell and the second carrier of the second cell to UE 2010. The first cell may be same as the second cell (e.g., with the Configuration 1) or maybe different from the second cell (eg., 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.Docket No.: 25-1062PCT

[0240] Process 1801 of FIG. 18A illustrates an example embodiment of the Carrier Switching 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 2010 may receive message(s) 1852. Message(s) 1852 may be transmitted via a SIB1, one ormoreSIBx and / or RRC signaling. UE 2010 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 config1) 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., coresetflO). 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 2010 via an initial access, UE 2010may 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) (NCD-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 (absoluteFrequencySSB-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 second carrier. UE 2010 may identify the NCD-SSB(s) of the second carrier, based on the configuration parameters. UE 2010 may not obtain a SIB1 of the second carrier via the NCD-SSB(s). UE2010 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 carrierDocket No.: 25-1062PCTmay 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 2010 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 2010 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 2010 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 cell index', 'additional physical cell identifier’. UE 2010may receive a DCI, scrambled with a cell-RNTI (C-RNTI), via the second carrier based on the second cell identifier. UE 2010 may receive a DCI, scrambled with the C-RNTI, via the first carrier based on the first cell identifier UE 2010 may use / consider the first cell identifier for downlink signals via the first carrier. UE 2010 may use / consider the second cell identifier for downlink signals via the second carrier.Docket No.: 25-1062PCT

[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 Sen / ingCellConfig 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 contro / ResourceSetZero and searchSpaceZero which can be configured in Sen / ingCellConfigCommon 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 cell and / 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 theDocket No.: 25-1062PCTuplink 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-Positions / nBurst, additional-ssb-periodicitySen / ingCell, 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 starting DM-RS symbol index may be broadcasted via the MIB (master information block) of the CD-SSB(s). UE 2010 may determine the first starting DM-RS symbol index being same as the starting DM-RS symbol index. The parameter mayDocket No.: 25-1062PCTindicate 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 2010may determine a DM-RS pattern I position of downlink signal(s) via the first carrier based on the starting DM-RS symbol index. Additionally / optionally, a second starting DM-RS symbol index (e.g., a second DM-RS typeA, dmrs-TypeA-Positi n2) 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 2010 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 2010 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 2010 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 carrier 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, ce / IBarred), 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-ConfigSIB1 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-1062PCT

[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-patern-carrier-switching) between the first carrier and the second carrier: in an example, a bitmap may be provided where a first value (e.g., ‘0’ or ‘T) 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 ‘O') 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 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 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.

[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:Docket No.: 25-1062PCT

[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 2010 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 2010 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 2010 may not apply the TDM pattern (e.g., the carrier switching pattern) in monitoring CD-SSB(s) of the first carrier. Alternatively, BS 2020 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 2010 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-ToMatehAraund, rateMatchPatternToAddModList) may be given / configured for the first carrier. Optionally / additionally, a second set of rate matching configuration parameters (lte-CRS-ToMatchAround2, additional-rateMatchPaternToAddModList) maybe 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, supplementaryfirstActiveDowninkBWP-ld may be configured, where the supplementaryfirstActiveDowninkBWP-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-1062PCTsupplementaryfirstActiveDownlinkBWP-id) and / or a default downlink BWP (e.g., a BWP with supplementarydefaultDownlinkBWP-id).

[0264] L) a measurement object (measObjectNR IE) 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 orC-2) the first initial downlink BWP (initialDownlinkBWP via BWP-DownlinkCommon IE) for the first carrier or the second initial downlink BWP (supplementaryinitia / DownlinkBWP 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 based on the second configuration option (Configuration 2). In the example, the first cell and the second cell are different. The first carrier may be associated with the first cell, and the second carrier may be associated with the second cell.

[0270] UE 2010 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 2010 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 188T). The first carrier-cell or the first serving cell config 1881 of the first cell may indicate parameters for the first carrier. The first serving cell config 1881 may comprise parameters for the uplink carrier. The first carrier and the uplink carrier may be paired spectrum in a FDD band. The first carrier may refer both the first carrier and the uplink carrier.Docket No.: 25-1062PCT

[0271] Message(s) 1872 may, additionally, indicate a second serving cell config 1885 (e.g., second configuration parameters via ServingCellConfigCommon 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. The second carrier 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.

[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 the second carrier-cell configuration may indicate / comprise one or moreof the parameters of A), (BorC), D), E), F), H), G), (J or K), B-1), B-2), L) 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), L). 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), L). 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 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 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 the TDM 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 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 secondDocket No.: 25-1062PCTtime durations 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, and 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). If the second cell is not active (e.g., the second cell is deactivated, in dormant state, or in cell DTX / DRX, a 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) 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 / a time duration, where a first value indicating the wireless device is configured to receive / transmit during the slot / the time duration via the first carrier, a second value indicating the. wireless device is configured to receive during the slot / the time duration via the second carrier, and the slot / the time duration is determined based on a predetermined subcarrier spacing (e.g., 15 kHz) or based on a reference subcarrier spacing; d) a linked cell index 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.

[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) for the 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 CellGroupConfig 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 CellGroupConfig. The TDM pattern (eg., the carrier switching pattern) may be comprised in a first ServingCellConfig of the first cell and / or a second ServingCellConfig of the second cell.Docket No.: 25-1062PCT

[0278] The CellGroupConfig 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 CellGroupConfig 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. The CSI-RS may be configured in CSI-ReportConfig IE and / or LTM-CSI-ReportConfig IE.

[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) maybe equal to a k2 times of a periodicity of the NCD-SSB (e.g., k1 = 1, 2, 0.5, 025 ...) ora second SMTC window of the second carrier. In an example, the first time durations may comprise one or more time durations / slots overlapping with the SMTC configuration(s) of the first carrier / cell and / or SSB transmission / occasion(s) of the first carrier / cell. When the second time durations do not comprise SMTC configuration(s) of the second carrier / cell or does not overlap completely with SSB transmission / occasion(s) of the second carrier / cell, the wireless device may use a measurement gap to measure the SSB transmission / occasion(s) of the second carrier / cell.

[0284] 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 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. TheDocket No.: 25-1062PCTwireless device may receive a retransmission of the TB via the second cell. The wireless device may transmit uplink signals via the first cell.

[0285] The cell DTX / DRX configuration may have a periodicity, an active time / duration in each periodicity. When the cell DTX / DRX is activated e.g., via L1 signaling, a base station may not transmit (during DTX inactive time, e.g., during outside of onDuration window of DRX configuration) or the wireless device may not receive during (DTX inactive time, outside of ‘Active Time') based on the cell DTX / DRX configuration. For example, the cell DTX / DRX configuration (e.g., via CellDTXDRX-Config IE) may comprise a on duration timer (e.g., ce / IDTXDRX-onDurationTImef), an offset (e.g., ce / IDTXDRX-CycleStarfOffset), a slot offset (e.g., cellDTXDRX-SlotOffsef), a cell DTXDRX configuration type (e.g., cellDTXDRXConfigType indicating one of DTX, DRX or both DTX and DRX), and / or a state of the cell DTX / DRX configuration (e.g., cellDTXDRXadiveationStatus). Each cell DTX / DRX may indicate applying a DTX without a DRX (e.g., set to 'DTX') or a DRX without a DTX (e.g., set to 'DRX') or both DTX and DRX (e.g., set to 'DTXDRX'). In an example, the wireless device may be configured with a carrier switching between a first carrier of a first cell and a second carrier of a second cell. The first cell may be different from the second cell. The wireless device may be configured with a TDM pattern (e.g., a carrier switching pattern) fora carrier switching (e.g. switching between Case 1 1703 in FIG. 17 via the first carrier of the first cell and Case 2 1705 in FIG 17 via the second carrier of the second cell) between the first carrier / first cell and the second carrier / second cell. The first cell may be configured with a first cell DTX / DRX configuration. The second cell may be configured with a second cell DTX / DRX configuration.

[0286] In an example, a wireless device may receive one or more messages (e.g., RRC, MAC CE, DCI) indicating a carrier switching (CS) pattern, for a carrier switching between a first cell and a second cell. In the example, a time duration, of the CS pattern, may be configured for communicating via the second cell. The wireless device may determine whether to receive and / or transmit signals (e.g., communicate with a base station), during the time duration, via the first cell based on the CS pattern and the one or conditions being met. The wireless device may communicate with the base station via the first cell or the second cell, during the time duration based on the determining.

[0287] For example, the one or more conditions may comprise one or more of : a) the second cell is non-active period of a cell DTX / DRX of the second cell during the time duration; b) the second cell is in dormant state during the time duration; c) a random access procedure, via the first cell, is ongoing during the time duration; d) the second cell is inactive / deactivated; e) a deactivation timer (e.g., scellDeadivationTimer) of the second cell expires before or at the time duration.

[0288] In an example, a dormant BWP of a cell may refer that a BWP configured by a base station via one or more RRC signaling. When the dormant BWP becomes active BWP of the cell, a wireless device may stop monitoring PDCCH on / for the cell but may continue performing CSI measurements, automatic gain control (AGC) and beam management if configured.

[0289] If the cell is configured with sCel / State (e.g., a status of the cell upon configuration) set to 'activated' upon the cell configuration (e.g., via ServingCellConfig) and if a first active downlink BWP firstActiveDownlinkBWP-ld') is set toDocket No.: 25-1062PCTnon-dormant BWP (e.g. , not a dormant BWP), the wireless device may activate the cell (e.g., a normal cell activation) and the wireless device may perform SRS transmission on the cell, CSI reporting for the cell, PDCCH monitoring on the cell, PUCCH transmission on the cell if configured. Otherwise (e.g., the HrstActiveDownlinkBWP-ld) is set to a dormant BWP, the wireless device may stop running a BWP inactivity timer (bwp-lnactivityTimei) of the cell if running.

[0290] For each SCell a dormant BWP may be configured with dormantBWP-ld by RRC signalling. Entering or leaving dormant BWP for S Cells is done by BWP switching per SCell or per dormancy SCell group based on instruction from PDCCH. The dormancy SCell group configurations are configured by RRC signalling. Upon reception of the PDCCH indicating leaving dormant BWP, the DL BWP indicated by firsiOutsideActiveTimeBWP-ld or by firstWithinActiveTimeBWP-ld is activated. Upon reception of the PDCCH indicating entering dormant BWP, the DL BWP indicated by dormantBWP-ld is activated. The dormant BWP configuration for SpCell or PUCCH SCell is not supported

[0291] If a BWP is activated and the active DL BWP for the cell is a dormant BWP, the wireless device may perform the followings.

[0292] A) stop the bwp-lnactivityTimer of this Serving Cell, if running

[0293] B) stop monitoring PDCCH candidates / PDCCHs on the BWP I cell

[0294] C) stop monitoring PDCCH candidates / PDCCHs for the BWP / cell (e.g., cross-carrier scheduled by other cells)

[0295] D) stop receive / skip receive downlink data (e.g., PDSCH) on the BWP / cell

[0296] E) stop reporting CSI feedback on the BWP. Report CSI reports, except for aperiodic CSI reports, for the BWP via another cell (e.g., PCell)

[0297] F) stop transmitting SRS on the BWP / cell

[0298] G) does not transmit uplink transmission (e.g., PUSCH) on the BWP / cell

[0299] H) does not transmit (P)RACH on the BWP / cell

[0300] I) does not transmit PUCCH on the BWP / cell

[0301] J) clear any configured grant PUSCH on the cell I BWP

[0302] K) suspend any configured grant associated with the cell

[0303] L) if the cell is configured as a scheduled cell in a multi-cell DCI (e.g., via a DCI format 1 _3, 0_3) of a multi-carrier-DC l-SetofCells (e.g., MC-DCI-SetOfCells) and with a search space for DCI to schedule multiple cells of the a same searchSpaceid as a serving cell in which the MC-DCI-SetOfCells containing the cell is configured, not monitor the PDCCH for scheduling multiple cells for the set of cells in MC-DCI-SetOfCells including the cell.

[0304] In case, the cell is deactivated or a BWP (an active BWP of the cell) is deactivated, the wireless device may perform the followings:

[0305] A) the wireless device does not transmit uplink transmission (e.g., data) on the BWP or on the cell;

[0306] B) the wireless device does not transmit PRACH, PUCCH, SRS, CSI report on the BWP I cell

[0307] C) the wireless device does not monitor PDCCH on the BWP / cellDocket No.: 25-1062PCT

[0308] D) the wireless device does not transmit a CSI report for the BWP / cell

[0309] E) the wireless device does not receive downlink data on the BWP I cell

[0310] In an example, a wireless device detects a DCI format with SCell dormancy indication that indicates an active DL BWP change for an Scell in slot n of primary cell, the UE is not required to receive or transmit in the SCell during a time duration.

[0311] PDCCH indication

[0312] A wireless device configured with DRX mode operation may be provided the following configuration parameters for detection of a DCI format 2_6 in a PDCCH reception on the PCell or on the SpCell.

[0313] The configuration parameters for receiving / detecting the DCI format 2_6 may indicate one or more of:

[0314] a PS-RNTI for DCI format 2_6 by ps-RNTI (power saving RNTI);

[0315] a number of search space sets, by dci-Format2-6, to monitor PDCCH for detection of DCI format 2_6 on the active DL BWP of the PCell or of the SpCell according to a common search space;

[0316] a payload size for DCI format 2_6 by sizeDCI-2-6;

[0317] a location in DCI format 2_6 of a Wake-up indication bit by ps-PositionDCI-2-6, where a 'O' value for the Wakeup indication bit, when reported to higher layers, indicates to not start the drx-onDurationTimer tor the next long DRX cycle and a 'T value for the Wake-up indication bit, when reported to higher layers, indicates to start the drx-onDurationTimer for the next long DRX cycle

[0318] a bitmap, when the UE is provided a number of groups of configured SCells by dormancyGroupOutsideActiveTime, where the bitmap location is immediately after the Wake-up indication bit location, and the bitmap size is equal to the number of groups of configured SCells where each bit of the bitmap corresponds to a group of configured SCells from the number of groups of configured SCells, and the bitmap size is equal to the number of groups of configured SCells where each bit of the bitmap corresponds to a group of configured SCells from the number of groups of configured SCells; and a 'O' value for a bit of the bitmap indicates an active DL BWP, provided by dormantBWP-ld, for the wireless device for each activated SCell in the corresponding group of configured SCells; and a '1' value for a bit of the bitmap indicates a) an active DL BWP, provided by firstOutside AdiveTimeBWP-ld. for the wireless device for each activated SCell in the corresponding group of configured SCells, if a current active DL BWP is the dormant DL BWP; or b) a current active DL BWP, for the wireless device for each activated SCell in the corresponding group of configured SCells, if the current active DL BWP is not the dormant DL BWP; based on a) or b) the wireless device sets the active DL BWP to the indicated active DL BWP.

[0319] an offset by ps-Offset indicating a time, where the wireless device starts monitoring PDCCH for detection of DCI format 2_6 according to the number of search space sets, prior to a slot where the drx-onDurationTimer would start on the PCell or on the SpCell, where for each search space set, the PDCCH monitoring occasions are the ones in the first Tsslots indicated by duration, or Ts= 1 slot if duration is not provided, starting from the first slot of the first Tsslots and ending prior to the start of drx-onDurationTimer.Docket No.: 25-1062PCT

[0320] On PDCCH monitoring occasions associated with a same long DRX Cycle, a wireless device does not expect to detect more than one DCI format 2_6 with different values of the Wake-up indication bit for the UE or with different values of the bitmap for the wireless device. The wireless device may not monitor PDCCH for detecting DCI format 2_6 during ‘Active Time’ (e.g. , determined based on onDuration window) of a DRX configuration.

[0321] If a wireless device is provided search space sets to monitor PDCCH for detection of DCI format 0_1 / 0_3 / 1 _1 / 1_3 and if any of DCI format 0_1 / 0_3 / 1_1 / 1_3 includes a SCell dormancy indication field, the followings are used.

[0322] A) the SCell dormancy indication field is a bitmap with size equal to a number of groups of configured SCells, provided by dormancyGroupWithinAcHveTime; and

[0323] B) each bit of the bitmap corresponds to a group of configured SCells from the number of groups of configured SCells; and

[0324] C) if the wireless device detects a DCI format 0_1 / 1_1 that does not include a carrier indicator field, or a DCI format 0_1 / 1 J that includes a carrier indicator field with value equal to 0, and if the DCI format 0_1 does not indicate UL grant Type 2 release nor deactivate semi-persistent CSI report(s) on PUSCH, or if the DCI format 1 J does not indicate SPS PDSCH release, or if the DCI format 1_1 does not indicate a TCI state update without scheduling PDSCH reception, or if the wireless device detects a DCI format 0_3 / 1_3,

[0325] C-1)a'0' value for a bit of the bitmap indicates an active DL BWP, provided by dormantBWP-ld, for the wireless device for each activated SCell in the corresponding group of configured SCells; and

[0326] C-2)a value for a bit of the bitmap indicates a) an active DL BWP, provided by firstWithinActiveTimeBWP-Id, for the wireless device for each activated SCell in the corresponding group of configured SCells, if a current active DL BWP is the dormant DL BWP; and a current active DL BWP, for the wireless device for each activated SCell in the corresponding group of configured SCells, if the current active DL BWP is not the dormant DL BWP; and

[0327] C-3) the wireless device sets the active DL BWP to the indicated active DL BWP.

[0328] In an example, a wireless device may be configured for operation on the second cell according to one or both of a cell DTX operation and a cell DRX operation by a cell DTX / DRX configuration (e.g., CellDTXDRX-Config) for the second cell, the cell DTX / DRX configuration (e.g., CellDTXDRX-Config may be configured for the second cell. The cell DTX / DRX configuration may have / indicate / comprise a periodicity, an active time / onDuration window / active duration in each periodicity. The cell DTX / DRX configuration may be configured within a ServingCellConfig IE of the second cell A cell DTX / DRX configuration may be configured for each serving cell.

[0329] Additionally / alternati vely / optional ly, for one or more serving cells configured with cell DTX / DRX configuration(s), the wireless device may receive a cell DTX DCI config (e.g., cellDTX-DCI-Config IE). The cell DTX DCI config may be configured within a PhysicalCellGroupConfig IE. For example, the cell DTX DCI config (e.g., ce / IDTX-DCI-Config IE) may comprise / indicate a cell DTRX-RNTI (RNTI used for a DCI indicating activation / deactivation of cellDocket No.: 25-1062PCTDTX / DRX configurations) and a size of a DCI format 2_9 The DCI format 2_9 may be used to indicate activation / deactivation of one or more cell's DTX / DRX configurations.

[0330] When the cell DTX / DRX is activated e.g., via L1 signaling, a base station, via the second cell, may not transmit (during DTX inactive time) or the wireless device may not receive during (DTX inactive time) based on the cell DTX / DRX configuration. For example, the cell DTX / DRX configuration (e.g., via CellDTXDRX-Config IE) may comprise a on duration timer (e.g., cellDTXDRX-onDurationTImer), an offset (e.g., ce / IDTXDRX-CycleStartOffsef), a slot offset (e.g., cellDTXDRX-SlotOffsef), a cell DTXDRX configuration type (e.g., cellDTXDRXConfigType indicating one of DTX, DRX or both DTX and DRX), and / or a state of the cell DTX / DRX configuration (e.g., cellDTXDRXactiveationStatus). Each cell DTX / DRX may indicate applying a DTX without a DRX or a DRX without a DTX or both DTX and DRX.

[0331] In the example, the wireless device may receive a second cell DTX / DRX configuration (e.g., CellDTXDRX-Config IE) for the first cell. The second cell DTX / DRX configuration of the first cell may be given in addition to the cell DTX / DRX configuration of the second cell or alternatively to the cell DTX / DRX configuration of the second cell. A L1 signaling based on the DCI format 2_9 may be applicable to the first cell and / or the second cell based on the second cell DTX / DRX configuration (e.g., CellDTXDRX-Config IE) for the first cell and / or the cell DTX / DRX configuration (e.g., CellDTXDRX-Config IE) for the second cell.

[0332] In an example, the cell DTX DCI config (e.g., cellDTX-DCI-Config IE) may indicate the cell DTRX RNTI (e.g., cellDTRX-RNTi) that indicates a RNTI value used for scrambling CRC of a DCI format 2_9 for activating and / or deactivating cell DTX / DRX and / or NES mode for conditional handover indication. The cell DTX DCI config may indicate the size of the DCI format 2_9.

[0333] Configuration parameters of the second cell (e.g., ServingCellConfig IE) may comprise a parameter (e.g., cellDTXDRX-L1 activation) where the parameter indicates whether the second cell has enabled with L1 signaling based on the DCI format 2_9 for dynamic activation and / or deactivation of cell DTX / DRX configuration. The configuration parameters, of the second cell, may indicate one or more positions in a DCI (e.g., positionlnDCI-cellDTRX) that indicates a starting bit position of an information block of the DCI format 2_9 for the second cell

[0334] Note that first configuration parameters of the first cell (e.g., ServingCellConfig IE) of the first cell may indicate one or more of: ce!IDTXDRX-L1 activation, and position In DC 1-cellDTRX when the first cell is configured with a cell DTX / DRX config and / or L1 signaling based activation.

[0335] For the second cell and / or the first cell configured with the cell DTX / DRX config, the wireless device may be additionally provided by dci-Format2-9 in a Type3-PDCCH CSS set to monitor PDCCH for detection of DCI format 2_9 during ‘Active Time' (e.g., non-inactive periods, onDuration window).

[0336] The Type3-PDCCH CSS, configured with the DCI format 2_9 (e.g., by dci-Format2-9) may be configured on the first cell. The wireless device may monitor PDCCHs / PDCCH candidates via the Type3-PDCCH CSS (e.g., a CSS for one or more group common DCIs) via the first cell.Docket No.: 25-1062PCT

[0337] The wireless device may be, optionally / additionally, configured (e.g. , via RRC signaling) with a location in DCI format 2_9 by position / nDCI-cellDTRX of a cell DTX / DRX indication field for the second cell (or a secondary cell) and / or a NES-mode indication field for the PCell (e.g., the first cell, primary cell, SpCell).

[0338] The wireless device may apply one or more of the followings for the first cell and / or the second cell, wherein a serving cell refers the first cell and / or the second cell respectively;

[0339] if the wireless device is configured with both cell DTX operation and cell DRX operation for the serving cell and if cellDTX-DRX-L1 activation is provided, the cell DTX / DRX indication field includes two bits where the first bit indicates the cell DTX operation and the second bit indicates the cell DRX operation; or

[0340] if the wireless device is configured with only one of the cell DTX operation and cell DRX operation for the serving cell and if cellDTX-DRX-L1 activation is provided, the cell DTX / DRX indication field includes one bit indicating one of the cell DTX operation and cell DRX operation, respectively, for the serving cell, then

[0341] a 'O' value for a bit of the cell DTX / DRX indication field indicates deactivation of cell DTX or of cell DRX of the corresponding serving cell; and

[0342] a' 1 ' value for a bit of the cell DTX / DRX indication field indicates activation of cell DTX or of cell DRX.

[0343] In determining activation / deactivation of cell DTX / DRX, if the serving cell is configured with a SUL carrier, the cell DTX / DRX indication field indication for activation or deactivation of cell DRX applies to both the UL carrier and the SUL carrier of the serving cell.

[0344] When the first cell is a primary cell, and the primary cell is configured with a CS pattern, a base station may not enable network energy saving (NES) specific conditional handover execution condition (NES-specific CHO). The wireless device may not expect to be configured with ‘nesEvenf on the primary cell or for the DCI format 2_9 when the primary cell is enabled with the CS switching. The base station may not configure 'nesEven to the primary cell in case the base station configures the CS switching on the primary cell.

[0345] A wireless device may not expect to monitor PDCCH for detection of DCI format 2_9 on more than one serving cells of one cell group. The wireless device may receive / monitor PDCCH for detection of DCI format 2_9 on the first cell (or the primary cell) or the second cell (or the secondary cell).

[0346] FIG. 19 illustrates an example as per an example embodiment. The base station may configure a first cell (1stcell) and a second cell (2ndcell) to the wireless device. The base station may configure a carrier switching between the first cell and the second cell. The first cell may be a primary cell, a SpCell (primary cell of a SCG), 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. The first cell and the second cell maybe same to the first carrier (Carrier #0 in FIG. 17) and the second carrier (Carrier #1 in FIG.17) respectively. The first cell may comprise the first carrier. The second cell may comprise the second carrier. The first cell and the second cell may be same to the second carrier (Carrier #1 in FIG. 17) and the first carrier (Carrier #0 in FIG. 17) respectively. The first cell may comprise the second carrier. The second cell may comprise the first carrier. In case the first cell is the second carrier, ‘Case 21705' is applied to the first cell and ‘Case 1 1703' is applied to theDocket No.: 25-1062PCTsecond cell, and the first time durations 1707 applies to the second cell and the second time durations 1709 applies to the first cell. Example embodiments may be applied to the scenario (e.g the second cell is the first carrier and the first cell is the second carrier) by swapping the first cell and the second cell in below example embodiments.

[0347] For example, a CS pattern (e.g., a bitmap with ‘0101 ... 0101’ as shown in FIG. 19) maybe configured via a cell group configuration of the first cell and the second cell. The CS pattern may be configured via each serving cell configuration of the first cell and the second cell. The first cell in the example is a primary cell. At a time TO, the wireless device may establish a RRC connection via the first cell. The wireless device may be configured with one or more measurement gap patterns associated with the first cell and, optionally, with the second cell at least when the second cell becomes activated. A measurement gap pattern of the one or more measurement gap patterns may indicate a measurement gap duration per each interval with a periodicity. The wireless device may determine a measurement gap in each interval determined baes do on the periodicity (e.g., a measurement gap (MG) with the MG duration in every interval of P (the periodicity)).

[0348] For example, the wireless device may perform measurements on the second cell during the MG, at least while the second cell is being inactive (i.e. , the second cell is deactivated). The wireless device may skip receiving downlink control / data and / or transmitting uplink control / data with the first cell and, optionally, with the second cell, during the MG. The wireless device may perform measurements on one or more frequencies comprising a first frequency of the first cell and / or a second frequency of the second cell.

[0349] FIG. 19 shows an example of the CS pattern (e.g., 0101....0) where a value ‘0’ indicates a first time duration configured to communicate, via the first cell, with the base station and a value T indicates a second time duration configured to communicate, via the second cell, with the base station. During the first time duration, if the wireless device communicates with the base station via the first cell, the wireless device may not communicate with the base station via the second cell. During the second time duration, if the wireless device communicates with the base station via the second cell, the wireless device may not communicate with the base station via the first cell. In the example, a time duration may be one of a plurality of second time durations configured to communicate, via the second cell, with the base station. For example, the plurality of second time durations comprises the second time duration. For example, the time duration is the second time duration. In the example, a first plurality of time durations may be configured to communicate via the first cell, where the first plurality of time durations comprise the first time duration and a plurality of time durations indicated as ‘O' by the CS pattern. The second plurality of time durations may comprise the second time durations and a plurality of time durations indicated as ‘T by the CS pattern. The first plurality of time durations may be same as the first time durations 1707 in FIG. 17. The second plurality of time durations may be same as the second time durations 1709 in FIG. 17.

[0350] The wireless device (UE 2010) may receive a downlink control command (e.g., MAC CE, DCI, RRC) indicating the second cell is activated or indicate to activate the second cell before a time T1. Before activating the second cell, the wireless device may not apply the CS pattern between the first cell and the second cell, as the second cell is notDocket No.: 25-1062PCTactivated For example, in FIG. 19, between the time TO and the time T1, the wireless device may ignore the CS pattern and may assume time durations are available to the first cell and not available to the second cell. The time durations may overlap with the first plurality of time durations and the second plurality of time durations. The wireless device may skip communicating (receiving and / or transmitting control / data) via the first cell during one or more MGs of the one or more MG patterns during the time TO and the time T1. During the time TO and the time T1 , the CS pattern may be not activated or may not be used. The configured CS pattern may be effective or be used when both cells of the CS pattern are activated.

[0351] For example, the downlink control command may be a RRC signaling of configuration parameters of the second cell (e.g., SCellConfig). The configuration parameters may indicate an initial state of the second cell via a parameter (e.g., sCellState). The parameter may be set to ‘activated’. In response to the parameter setting to the 'activated', the wireless device may activate the second cell upon being configured with the second cell (e.g., upon receiving SCellConfig of the second cell). The downlink control command may be a MAC CE e.g., a SCell activation / deactivation MAC CE, indicating activation of the second cell. The downlink control command may be a SCell activation / deactivation DCI indicating activation of the second cell.

[0352] Aftera scell activation delay / latency since receiving the downlink control command, the wireless device may determine that the second cell is activated. When it is activated, if an active BWP of the second cell is a dormant BWP (e.g., the second cell is activated as a dormant state), the wireless device may determine that the second cell is in a first state (e.g., a power saving state, a dormant state, a non-active state, inactive period, inactive state). When it is activated, if an active BWP of the second cell is not a dormant BWP (e.g., the second cell is activated as non-dormant state), the wireless device may determine that the second cell is in a second state (e.g., a non-power saving state, a normal state, a non-dormant state, an active state, active period, etc.). For example, a secondary cell (e.g., the second cell) may have a state among one of the followings:

[0353] A) deactivated: when the secondary cell is not activated, the state of the secondary cell is deactivated / inactive;

[0354] B) the first state (or activated and the first state or inactive): when the secondary cell is activated, and the secondary cell is in inactive state or in the first state.

[0355] 0) the second state (or activated and the second state or active): when the secondary cell is activated; and the secondary cell is in active state or in the second state.

[0356] In an example, the first state (e.g., inactive state, power-saving state) of the second cell, during a time window / duration, may be determined based on one or more of the followings:

[0357] 1) The second cell (or a secondary cell) is activated and the active BWP of the second cell is the dormant BWP during the time window / duration;

[0358] 2) The second cell (or a secondary cell) is activated and the time window / duration overlaps with a DRX inactive period of the second cellDocket No.: 25-1062PCT

[0359] 3) The second cell (or a secondary cell) is activated and the time window / duration overlaps, in time, with the second cell DTX / DRX inactive periods of the second cell

[0360] 4) the second cell becomes non-active period of a cell DTX / DRX of the second cell at start of the time window / duration;

[0361] 5) the second cell becomes dormant state at start of the time window / duration

[0362] 6) the second cell is outside of ‘Active Time' (e.g., outside of onDuration window, outside of non-inactive periods, outside of active periods), of DRX configuration and / or cell DTX / DRX configuration, during the time window / duration;

[0363] 7) the second cell is not fully active e.g., based on the second cell is in a default BWP (e.g., an active BWP of the second cell is the default BWP) during the time window / duration;

[0364] 8) one or more symbols are indicated as invalid by slot format indicator (SFI) DCI (e.g., DCI format 2_1).

[0365] In an example, the second state (e.g., active state, non-power saving state) of the second cell, during a time window / duration, may be determined based on one or more of the followings:

[0366] 1) The second cell (or a secondary cell) is activated and the active BWP of the second cell is not the dormant BWP during the time window / duration;

[0367] 2) The second cell (or a secondary cell) is activated and the time window / duration overlaps with a DRX active period (e.g., ‘Active Time’, onDuration window, non-inactive periods) of the second cell

[0368] 3) The second cell (or a secondary cell) is activated and the time window / duration overlaps, in time, with the second cell DTX / DRX active period (e.g., Active Time’, onDuration window, non-inactive periods) of the second cell

[0369] 4) the second cell becomes active period of a cell DTX / DRX of the second cell at start of the time window / duration;

[0370] 5) the second cell becomes non-dormant state at start of / duri ng the time window / duration

[0371] 6) the second cell is within of Active Time (e.g., onDuration window, non-inactive periods)’, of DRX configuration and / or cell DTX / DRX configuration, during the time window / duration;

[0372] 7) the second cell is fully active e.g., based on the second cell is not in a default BWP or a dormant BWP (e.g., an active BWP of the second cell is not the default BWP nor a dormant BWP) during the time window / duration;

[0373] 8) one or more symbols are indicated as downl in k / uplink by slot format indicator (SFI) DCI (e.g., DCI format 2_1) and / or TDD UL-DL configuration parameters (e.g., TDD-UL-DL-ConfigurationCommon, TDD-UL-DL-ConfigurationDedicated)

[0374] The second cell becomes 'deactivated' upon receiving a downlink control command (RRC, MAC CE, DCI) indicating deactivation of the second cell and / or a deactivation timer (e.g., scellDeactivationTimer) of the second cell expires.

[0375] At the time T1 , the wireless device may determine the second cell is activated. The time T1 may be an application gap (e.g., a scell activation latency / delay) after receiving the downlink control command. Based on an activeDocket No.: 25-1062PCTBWP of the second cell not being a dormant BWP at the time T1 , the wireless device may determine the second cell is in the second state (e.g., active state, non-power saving state). Based on the second cell being in the second state, the wireless device may (start to) apply the CS pattern between the first cell and the second cell. For example, in FIG. 19, between the time T1 and a time T2, the wireless device may communicate via the first cell or the second cell based on the CS pattern in each time duration. The wireless device may switch between communicating via the first cell and communicating via the second cell based on the applying the CS pattern. For example, during the time T 1 and the time T2, the wireless device may switch Case 1 1703 in FIG. 17 (e.g., communicate via the first cell) and Case 21705 in FIG. 17 (e.g., communicate via the second cell) based on the CS pattern.

[0376] For example, after the time T1 , the wireless device may communicate, via the first cell, during one or more time durations of the first plurality of time durations (i.e, the first time durations 1707). The first plurality of time durations may comprise time durations based on bits of the CS pattern indicating ‘O' (or'T). The first plurality of time durations may not overlap in time with the second plurality of time durations (i.e., the second time durations 1709). The second plurality of time durations may comprise time durations based on bits of the CS pattern indicating 'T (or '0).

[0377] At the time T2, the wireless device may determine a state of the second cell changes e.g., from the second state (e.g., active state, non-power saving state) to the first state (e.g., inactive state, power saving state). The wireless device determines a first time of state change (1ststate change) of the second cell. In the example, the wireless device determines that the state of the second cell changes from the second state (active) to the first state (inactive, powersaving).

[0378] For example, the wireless device may receive a first downlink control command (e.g., RRC, MAC CE, DCI) before the time T2 to trigger the change of the state. For example, the first downlink control command may be a BWP switching of the second cell from a non-dormant BWP to the dormant BWP of the second cell. After a BWP switching latency, at the time T2, the wireless device switches to the dormant BWP of the second cell. The state of the second cell becomes inactive based on the dormant BWP being the active BWP of the second cell. In another example, the first downlink control command may comprise a DCI format 2_6 indicating a DRX wake-up (e.g, Wake-up indication bit for a long DRX cycle), a dormancy outside ‘Active Time (e.g., onDuration window, non-inactive periods)' and / or the like. In another example, the first downlink control command may comprise a DCI based on a DCI format 0_1 / 0_3 / 1_1 / 1_3 and if any of DCI format 0_1 / 0_3 / 1 _1 / 1_3 includes a SCell dormancy indication field. In response to receiving the DCI indicating / comprising the SCell dormancy indication field, and the SCell dormancy indication field indicating to switching to the dormant BWP of the second cell (e.g., a bit, of the SCell dormancy indication field, corresponding to the second cell set to '0'), the wireless device may switch to the dormant BWP of the second cell as the active BWP. In response to the switching to the dormant BWP, the wireless device may determine the state of the second cell being changed to the second state.

[0379] In an example, the wireless device may receive configuration parameters for detection of a DCI format 2_6 in a PDCCH reception on the PCell or on the SpCell, where the first cell is the PCell or the SpCell. The configurationDocket No.: 25-1062PCTparameters may indicate the number of search space sets indicated with the dci-Format2-6, to monitor PDCCH for detection of DCI format 2_6 on the active DL BWP of the first cell. When the first cell is configured with the CS pattern, the base station may configure the search space sets such that monitoring occasion of the DCI format 2_6 do not overlap the second plurality of time durations. The base station may configure the monitoring occasions of the search space sets for the DCI format 2_6, where the monitoring occasions are contained with time durations (e.g. , the first plurality of time durations) configured / used / applied for communicating via the first cell. In an example, monitoring occasions of one or more CSSs of the first cell may not overlap with the second plurality of time durations. The base station may configure the one or more CSSs such that the monitoring occasions of the one or more CSSs of the first cell may be comprised within the time durations (e.g., the first plurality of time durations) configured / used / applied for communicating via the first cell. Alternatively, the wireless device may ignore the CS pattern and may monitor one or more monitoring occasions of the search space sets indicated with the dci-Format2-6 or monitoring occasions of the one or more CSSs of the first cell.

[0380] In an example, the wireless device may receive configuration parameters for detection of a DCI format 2_9 in a PDCCH reception on a serving cell, where the serving cell may be a primary cell or a secondary cell. The wireless device may not be configured to monitor the DCI format 2_9 via the second cell. The wireless device may not be configured to monitor the DCI format 2_9 via the first cell if there are a third serving cell that is not under a CS switching. Alternatively, the wireless device may be configured to monitor the DCI format 2_9 via the first cell that is the primary cell. The configuration parameters may indicate the number of search space sets indicated with the dci-Format2-9, to monitor PDCCH for detection of DCI format 2_9 on the active DL BWP of the first cell. When the first cell is configured with the CS pattern, the base station may configure the search space sets such that monitoring occasion of the DCI format 2_9 do not overlap the second plurality of time durations. The base station may configure the monitoring occasions of the search space sets for the DCI format 2_9 , where the monitoring occasions are contained with time durations (e.g., the first plurality of time durations) configured / used / applied for communicating via the first cell. Alternatively, the wireless device may ignore the CS pattern and may monitor one or more monitoring occasions of the search space sets indicated with the dci-Format2-9 or monitoring occasions of the one or more CSSs of the first cell.

[0381] Based on the state of the second cell changes from the second state to the first state, the wireless device may determine / perform / apply one or more followings.

[0382] A) stop applying the CS pattern. The wireless device may behave in a same manner before the second cell is activated. For example, the wireless device may communicate, via the first cell, with the base station. The wireless device may perform measurements (e.g., L1 measurements, RRM measurements, etc.) on the second cell using the measurement gap.

[0383] B) determine to use a second CS pattern. The base station may configure, e.g., via the one or more messages, the second CS pattern (e.g., CSPattem2). The wireless device may switch to the second CS pattern from the CS pattern and may follow the second CS pattern to communicate via either the first cell or the second cell duringDocket No.: 25-1062PCTthe time duration. In an example, the second CS pattern may indicate third time durations for receiving downlink signals via the first cell. The second CS pattern may indicate fourth time durations for receiving downlink signals via the second cell. The fourth time durations may be a subset of the second time durations. The third time durations may a superset of the first time durations.

[0384] C) keep applying the CS pattern. The wireless device may monitor / receive one or more reference signals (e.g., CSI-RS, SSB) during the plurality of second time durations via the second cell.

[0385] The base station may configure a behavior of A), B) or C) for the case when the second cell becomes in the second state.

[0386] FIG. 19 illustrates a case of A) in the above.

[0387] Before a time T3, the wireless device may receive a second downlink control command indicating a second state change of the second cell e.g., from the first state (e.g., power-saving state) to the second state (e.g., active state). For example, the second downlink control command may be based on a same DCI format to the first downlink control command (e.g., a L1 signaling of DRX activation / deactivation with a DCI format 2_6, a cell DTX / DRX activation / deactivation with a DCI format 2_9, a scheduling DCI indicating activating / deactivating dormancy (e.g., SCell dormancy indication field in a scheduling DCI format, DCI format 0_1 / 0_3 / 1_1 / 1_3 and if any of DCI format 0_1 / 0_3 / 1 _1 / 1_3 includes a SCell dormancy indication field), a scheduling DCI indicating a BWP switching, RRC signaling, and / or MAC CE. Based on the second downlink control command, the wireless device may determine the state of the second cell being the second state at the time T3. Based on the second cell becoming ‘active’ state (e.g., during ‘Active Time' of DRX / DTX, non-dormant BWP), the wireless device may resume applying the CS pattern. For example, after the time T3, the wireless device may switch between Case 1 1703 and Case 21705 based on the CS pattern.

[0388] In an example, a wireless device may use a measurement procedure for obtaining a measurement. In an example, using the measurement procedure may also be referred to as applying the measurement procedure. In an example, obtaining a measurement may also be referred to as performing the measurement. In an example, the measurement procedure may comprise performing a measurement based on a signal. In an example, the measurement procedure in a wireless device may comprise performing a measurement based on a signal received by the wireless device. An example of a signal comprises a reference signal. Examples of a reference signal may be a SS / PBCH block (SSB), a CSI-RS, a positioning reference signal (PRS), a radio link monitoring reference signal (RLM-RS) (e.g., a SSB, a CSI-RS, etc.), a tracking reference signal (TRS), a DMRS, a SS / PBCH Block burst, a beam failure detection RS (BFD-RS), a beam recovery candidate RS (CBD-RS) etc. The SSB may also be referred to as a synchronization signal block (SSB). A wireless device may perform a measurement based on one or more measurement samples, where each measurement sample may correspond to a reception of one or more RSs in a time duration and determining measurement result(s) based on the reception. The wireless device may perform average,Docket No.: 25-1062PCTweighted average, and / or summation of the one or more measurement samples over a measurement time period, where the measurement time period may be determined based on a periodicity of a measurement RS transmission.

[0389] A measurement may be an intra-frequency measurement, an inter-frequency measurement, or an inter-radio access technology (RAT) measurement. A measurement may be a L3 RRM measurement, L1 beam management (BM) measurement, L1 radio link monitoring (RLM) measurement, L3 gap-less RRM measurement, etc. A measurement may be configured with a measurement object (e.g. , measObject) and / or a measurement report (e.g. , reportConfig). For example, the measurement object and / or measurement report may indicate a RS used for the measurement, one or more reporting metrics / results (e.g., SINR, RSRP, RSRQ, etc.). For example, a measurement may be configured with a CSI report configuration and / or a CSI resource (e.g., L1-RSRP). In an example, the intra-frequency measurement may be associated with one or more cells of an intra-frequency carrier. The intra-frequency carrier may also be referred to as a serving carrier frequency (e.g., a PCC, a PSCC, or an SCC) of a wireless device. In an example, the inter-frequency measurement may be associated with one or more cells of an inter-frequency carrier. The inter-frequency carrier may also be referred to as a non-serving carrier frequency of a wireless device. A wireless device may perform an intra-frequency measurements for one or more SSBs of one or more neighbor cells, where center frequency(s) of the one or more SSBs may be assumed to be the same as a center frequency of a serving cell SSB, and two subcarrier spacings of the one or more SSBs and the serving cell SSB may be assumed to be the same.

[0390] A measurement may be related to (or performed for) a procedure. Examples of the procedure may be a mobility procedure, a positioning procedure, a radio link procedure, a beam management (BM), an interference management procedure, a self-organizing network (SON) procedure (or a SON function), etc. The mobility procedure may also be referred to as a layer 3 (L3) mobility procedure or an L1-L2 triggered mobility (LTM) procedure. The positioning procedure may also be referred to as a positioning measurement procedure. The radio link procedure may also be referred to as a radio link operation. The radio link procedure may comprise a radio link monitoring (RLM) procedure, and / or a beam management (BM) procedure. The BM procedure may also be referred to as a link recovery procedure (LRP), or a beam recovery procedure, or a beam failure recovery procedure.

[0391] A measurement associated with the layer 3 mobility procedure may be referred to as a layer 3 (L3) measurement or layer 3 radio resource measurement (RRM). The layer 3 measurement may also be referred to as a layer 3 mobility measurement, a mobility measurement, ora radio resource management (RRM) measurement. Examples of the one or more layer 3 measurements may include a pathloss; a reference signal received power (RSRP); a reference signal received quality (RSRQ); a signal to interference and noise ratio (SINR), etc. A measurement (e.g., the RSRP) for layer 3 mobility procedure may be based on N11 number of samples, of one or more samples and over a measurement time. In an example, the wireless device may transmit to a base station, the one or more layer 3 (L3) measurements, e.g., via an RRC message.

[0392] A measurement associated with the LTM procedure may be referred to as a layer 1 (L1) measurement The L1 measurement may also be referred to as a layer 1 (L1) mobility measurement, LTM mobility measurement, an L1Docket No.: 25-1062PCTradio resource management (RRM) measurement, or an LTM RRM. Examples of the one or more layer 1 measurements may include a layer-1 - reference signal received power (L1-RSRP); a layer 1 - a reference signal received quality (L1-RSRQ); a layer 1 - a signal to interference and noise ratio (L1-SINR), etc. A measurement (e.g., the L1-RSRP) for LTM procedure may be based on N12 number of samples, of one or more samples and over a measurement time. In an example, the wireless device may transmit to a base station, the one or more layer 1 (L1) measurements, e.g., via an RRC message or a MAC-CE or an UCI. A L1 measurement may comprise one or more of : L1-RSRP, L1-RSRP, L1-SINR, CSI report, periodic CSI report, semi-persistent CSI report, aperiodic CSI report, etc.

[0393] In an example, a wireless device may receive one or more RRC messages indicating configuration parameters of a ServingCellConfig for a serving cell. The configuration parameters of the ServingCellConfig may comprise one or more parameters indicating: a) TDD DL / UL dedicated configuration (tdd-UL-DL-ConfigurationDedicated}', b) initial downlink BWP initialDownlinkBWP),' c) one or more downlink BWPs; d) a BWP index of a first active downlink BWP (firstActiveDownlinkBWP-ld}; e) a timer of a BWP inactivity (bwp-lnactivityTimer}; f) a default BWP defaultDownlinkBWP-ld}; g) uplink configurations (uplinkConfig} for an uplink carrier; h) uplink configurations (supplementaryUplink) for a supplemental uplink carrier; i) PDCCH configuration (pdcch-ServingCellConfig}; j} PDSCH configuration (pdsch-ServingCellConfig); k) CSI measurement configurations (csr-MeasConfig}; I) secondary cell deactivation timer (sCellDeactivationTimer}; m) TAG id tag-id)] n) a measurement object of the serving cell (servingCel / Mo}; o) dormant BWP l.dormantBWP-Config} p) additional PCI (additiona / PCI-ToAddModLisf}; q) a slot offset between a PCell and the serving cell (ca-SlotOffset); r) cell DTX and / or DRX configuration(s) (ce / IDTX-DRX-Config}

[0394] The additionalPCI-ToAddModList may indicate list of information for the additional SSB with different PCI than the serving cell PCI. The additional SSBs with different PCIs are not used for serving cell quality derivation.

[0395] The bwp-lnactivityTimer may indicate a duration in ms after which the wireless device falls back to the default BWP (indicated by a defaultDownlinkBWP-ld). When the network releases the timer configuration, the wireless device stops the timer without switching to the default BWP.

[0396] The ca-SlotOffset may indicate a slot offset between the primary cell (PCell / PSCel I) and the serving cell in unaligned frame boundary with slot alignment and partial SEN alignment inter-band CA. Based on this field, the wireless device determines the time offset of the serving cell. The granularity of this field is determined by the reference SCS for the slot offset (i.e. the maximum of PCell / PSCell lowest SCS among all the configured SCSs in DL / UL SCS-SpecificCarrierList in ServingCellConfigCommon or ServingCellConfigCommonSIB and this serving cell's lowest SCS among all the configured SCSs in DL / UL SCS-SpedficCarrierList in ServingCellConfigCommon or ServingCellConfigCommonSIB}. The Network configures at most single non-zero offset duration in ms (independent on SCS) among CCs in the unaligned CA configuration. If the field is absent, the wireless device applies the value of 0.

[0397] The cellDTX-DRX-Config may configure cell DTX / DRX for the serving cell A maximum of two cell DTX / DRX patterns can be configured per MAC entity for different serving cells. The two configured patterns are aligned, that theDocket No.: 25-1062PCTstart and slot offset are common and the periodicity of one pattern is an integer multiple of the other. Cell DTX is configured only when connected mode DRX is configured,

[0398] The defaultDownlinkBWP-ld may indicate an ID of the downlink bandwidth part to be used upon expiry of the BWP inactivity timer. This field is UE specific. When the field is absent the wireless device uses the initial BWP as default BWP. The initial bandwidth part is referred to by BWP-ld = 0.

[0399] The dormantBWP-Config may refer dormant BWP configuration for an SCell / the serving cell. This field may be configured only fora (non-PUCCH) SCell.

[0400] The firstActiveDownlinkBWP-id may indicate an ID of a DL BWP to be activated or to be used for RLM, BPD and measurements if included in an RRC Reconfiguration message contained in an NR or E-UTRA RRC message indicating that the SCG is deactivated, upon performing the RRC (re-)configuration. If the field is absent, the RRC (reconfiguration does not impose a BWP switch. If the field is absent for the PSCell at SCG deactivation, the UE considers the previously activated DL BWP as the BWP to be used for RLM, BPD and measurements. If the field is absent for the PSCell at SCG activation, the DL BWP to be activated is the DL BWP previously to be used for RLM, BPD and measurements. If configured for an SCell, this field contains the ID of the downlink bandwidth part to be used upon activation of an SCell. The initial bandwidth part is referred to by BWP-ld = 0. Upon reconfiguration with reconfigurationWithSync, the network sets the firstActiveDownlinkBWPdd and firstActiveUplinkBV / P-ici to the same value.

[0401] The initia / DownlinkBWP may indicate a dedicated (UE-specific) configuration for an initial downlink bandwidthpart (i.e., DL BWP#0). If any of the optional lEsare configured within this IE, the wireless device may consider the BWP#0 to be an RRC configured BWP (from UE capability viewpoint). Otherwise, the wireless device may not consider the BWP#0 as an RRC configured BWP (from UE capability viewpoint). Network always configures the wireless device with a value for this field if no other BWPs are configured.

[0402] The pdsch-ServingCellConfig may indicate PDSCH related parameters that are not BWP-specific.

[0403] The sCe / IDeactivationTimer may indicate SCell deactivation timer. If the field is absent, the UE applies the value infinity.

[0404] The servingCel / MO may indicate measObjectld of the MeasObjectNR in MeasConfig which is associated to the serving cell. For this MeasObjectNR, the following relationship applies between this MeasObjectNR and frequencylnfoDL in ServingCellConfigCommon / ServingCellConfigCommonSIB of the serving cell: if ssbFrequency is configured, its value is the same as the absoluteFrequencySSB and if csi-rs-ResourceConfigMobility is configured, the value of its subcarrierSpacing is present in one entry of the scs-SpecificCamerList, csi-RS-CellListMobility includes an entry corresponding to the serving cell (with cellld equal to physCellld in Sen / ingCellConfigCommon) and the frequency range indicated by the csi-rs-MeasurementBW of the entry in csi-RS-CellListMobility is included in the frequency range indicated by in the entry of the scs-SpecificCarrierList.

[0405] The tag-id may indicate a timing advance group identifier.Docket No.: 25-1062PCT

[0406] The uplinkConfig may be provided only when uplinkConfigCommon is configured in ServingCellConfgCommon or ServingCellConfigCommonSIB. Addition or release of this field can only be done upon SCell addition or release (respectively).

[0407] Each downlink BWP of the one or more downlink BWPs may comprise configuration parameters of a) identifier of a BWP; b) configuration parameters common to the one or more downlink BWPs; c) configuration parameters (BWP-DownlinkDedicated) specific to the each downlink BWP.

[0408] The BWP-DownlinkDedicated may be used to configure a UE-specific and / or a BWP-specific parameters of a downlink BWP. The BWP-DownlinkDedicated may comprise a measurement object (servingCel / MO) that is used when the corresponding BWP becomes an active BWP of the serving cell. The BWP-DownlinkDedicated may comprise configuration parameters (preConfGapStatus) indicating whether pre-configured measurement gap(s) (i.e. the gaps configured with preContiglnd) are activated or deactivated upon the switch to this BWP. If this field is configured, the wireless device may apply network-controlled mechanism for activation and deactivation of the pre-configured measurement gaps, otherwise the wireless device may apply the autonomous activation / deactivation mechanism. The first / leftmost bit corresponds to the measurement gap with gap ID 1 , the second bit corresponds to measurement gap with gap ID 2, and so on. Value 0 indicates that the corresponding pre-configured measurement gap is deactivated while value 1 indicates that the corresponding pre-configured measurement gap is activated. The wireless device may ignore the bit if the corresponding measurement gap is not a pre-configured measurement gap. The BWP-DownlinkDedicated may comprise configuration parameters indicating NCD-SSB(s) of the serving cell within the corresponding BWP (nonCellDefiningSSB). If the nonCellDefiningSSB is configured, the wireless device operating in this BWP uses this SSB (NCD-SSB) for the purposes for which it would otherwise have used the CD-SSB of the serving cell (e.g. obtaining sync, measurements, RLM, BFD, beam management). Furthermore, other parts of the BWP configuration that refer to an SSB (e.g. the "SSB" configured in the QCL-Info IE; the "ssb-lndex" configured in the RadioLinkMonitoringRS; CFRA-SSB-Resource; PRACH-ResourceDedicatedBFR) refer implicitly to this NCD-SSB.

[0409] The NCD-SSB has the same values for the properties (e.g., ssb-PositionsInBurst, PCI, ssb-PBCH-BlockPower) of the corresponding CD-SSB apart from the values of the properties configured in the NonCellDefinlngSSB-r17 IE. In the MIB associated with this NCD-SSB, the systemFrameNumber field indicates the frame boundary and frame number of the NCD-SSB. The subCarrierSpacingCommon and dmrs-TypeA-Position field in the MIBs associated with CD-SSB and NCD-SSB in the same cell are configured with the same values, respectively

[0410] One or more configuration parameters of a MeasObjectNR (e.g., measObject) that is indicated by MeasObjectNR-ld may comprise one or more parameters of: a) a frequency location of a SSB (ssb Frequency); b) a subcarrier spacing of the SSB (ssbSubcarrierSpacing); c) a first SS measurement configuration time configuration(SMTC) (smtcl); d) a second SMTC (smtc ); e) reference frequency for CSI-RS (refFreqCSI-RS); f) RS configuration (referenceSignalConfig); g) associated measurement gap index (associatedMeasGapSSB); h) associated measurement gap for CSI-RS (associatedMeasGapCSIRS); I) a frequency band information for the measurementDocket No.: 25-1062PCTobject (freqBandlndicatorNR); j) a measurement cycle for a secondary cell (measCycleSCell); k) a measurement sequence (measSequence);

[0411] The associatedMeasGapSSB may indicate an associated measurement gap for SSB measuring identified by ssb-ConfigMobility (comprised in referenceSignalConfig) in this measurement object. When multiple MeasObjectNR with the same SSB frequency are configured, the network configures the same measurement gap ID in this field for each MeasObjectNR. If this field is absent, the associated measurement gap is the gap configured via gapFRI , gapFR2, orgapUE.

[0412] The associatedMeasGapCSI-RS may indicate an associated measurement gap for CSI-RS measuring identified by csi-rs-ResourceConfigMobility (comprised in referenceSignalConfig) in this measurement object. If this field is absent, the associated measurement gap is the gap configured via gapFRI , gap FR2, or gapUE.

[0413] The freqBandlndicatorNR may indicate a frequency band in which the SSB and / or CSI-RS indicated in this MeasObjectNR are located and according to which the wireless device may perform the RRM measurements. This field is always provided when the network configures measurements with this MeasObjectNR.

[0414] The measCycleSCell may be used only when an SCell (the serving cell) is configured on the frequency indicated by the measObjectNR and is in deactivated state. The base station may configure the parameter whenever an SCell is configured on the frequency indicated by the measObjectNR, but the field may also be signal led / configured when an SCell is not configured. Value sf 160 corresponds to 160 sub-frames, value sf256 corresponds to 256 subframes and so on.

[0415] The measSequence may indicate a recommended sequence for intra / inter-RAT intra / inter-frequency measurement. Value 1 means the corresponding frequency is measured firstly. Value 2 means the corresponding frequency is measured secondly and so on. If more than one frequency is configured with the same value, it means no recommended sequence among these frequencies. If not provided, it means there is no recommended sequence for the corresponding frequency. This field is only configured for NR standalone or if the measObject is associated to the MCG.

[0416] The smtcl may indicate a primary measurement timing configuration based on a SMTC.

[0417] The smtc2 may indicate an additional measurement timing configuration based on a SMTC. If smtc2 is present, for cells indicated in the pci-List parameter in smtc2 in the same MeasObjectNR, the wireless device may determine / setup an additional SS / PBCH block measurement timing configuration (SMTC) in accordance with the received periodicity parameter in the smtc2 configuration and use the Offset (derived from parameter periodicityAndOffset) and duration parameter from the smtcl configuration. The first subframe of each SMTC occasion occurs at an SFN and subframe of the NR SpCell meeting the above condition.

[0418] The referenceSignalConfig may indicate / configure RS configuration for SS / PBCH block and CSI-RS. The referenceSignalConfig may comprise one or more of SSB mobility configurations (ssb-ConfigMobility) and / or CSI-RS mobility configurations (csi-rs-ResourceMobility). The ssb-ConfigMobility may comprise one or more SSB configurationsDocket No.: 25-1062PCTfor measurement. Each of the one or more SSB configurations may comprise a) a flag to indicate to derive a SSB index from a cell (deriveSSB-lndexFromCell); b) a cell index to derive a SSB index (deriveSSB-lndexFromCelllnter); c) SSBs to measure (ssb-ToMeasure).

[0419] The deriveSSB-lndexFromCell may indicate this field as true (1), a wireless device may assume SEN and frame boundary alignment across cells on the same frequency carrier. Hence, if the wireless device is configured with a serving cell for which (absoluteFrequencySSB, subcarrierSpacing) in ServingCellConfigCommon is equal to (ssbFrequency. ssbSubcarrierSpacing) in this MeasObjectNR this field indicates whether the wireless device may be able to utilize the timing of this serving cell to derive the index of SS block transmitted by neighbour cell. Otherwise, this field indicates whether the wireless device may use the timing of any detected cell on that target frequency to derive the SSB index of all neighbour cells on that frequency.

[0420] The deriveSSB-lndexFromCelllnter may indicate whether a wireless device may assume SEN and frame boundary alignment between the reference serving cell indicated by ServCelllndex and all neighbour cells in this MeasObjectNR. This field also indicates that the wireless device can utilize the timing of the reference serving cell indicated by ServCelllndex to derive the index of SS block transmitted by all inter-frequency neighbour cells on the frequency indicated by the MeasObjectNR When this field is included, the network should set deriveSSB-IndexFromCell to true.

[0421] The ssb-ToMeasure may indicate a set of SS blocks to be measured within the SMTC measurement duration. The first / leftmost bit corresponds to SS / PBCH block index 0, the second bit corresponds to SS / PBCH block index 1 , and so on. Value 0 in the bitmap indicates that the corresponding SS / PBCH block is not to be measured while value 1 indicates that the corresponding SS / PBCH block is to be measured. When the field is not configured the wireless device measures on all SS blocks indicated by a ssbPositionsInBurst. Regardless of the value of this field, SS / PBCH blocks outside of the applicable SMTC are not to be measured.

[0422] A wireless device may be configured with a measurement gap configuration (MeasGapConfig) that may indicate one or more measurement gap (MG) configurations, where configuration parameters of a MG [GapConfig] may comprise one or more of: a measurement gap index / identifier (measGap / d), a measurement gap periodicity {mgrp}, and a gap offset (gapOffset). The measurement gap index / identifier indicates an identifier of the MG configuration (when the wireless device may be configured with one or more MGs). The measurement gap periodicity may indicate a measurement gap repetition periodic of the MG

[0423] In an example, a wireless device may interrupt a communication between the wireless device and a base station (e.g., at least partially) during a measurement gap. In an example, an interruption of the communication may comprise, the wireless device not receiving a signal from the base station, and / or the wireless device not transmitting a signal to the base station. In an example, a wireless device not receiving a signal may also be referred to as losing or not decoding the signal. In an example, a wireless device not transmitting a signal may also be referred to as dropping, abandoning, discarding, skipping or cancelling a transmission of the signal / channel. The interruption maybe supportedDocket No.: 25-1062PCTby the wireless device based on one or more network controlled small gap (NCSG) In case, the NCSG is not present / configured (e.g., ncsglnd-r17 is not indicated), the mgrp indicates the MG repetition period. If the NCSG is present / configured, the mgrp may indicate a visible interruption repetition period (VIRP) of NCSG pattern, where the wireless device is allowed to be interrupted during the VIRP.

[0424] The gap offset (gapOffeef) may indicate a starting point of a visible interruption length (VIL1 ) that occurs before a MG. A measurement gap length (mg / ) may indicate a length of the MG in msec. If ncsglnd-r17 is not present, the measurement gap length may be determined based on one or more predetermined values. If ncsglnd-r17 is present, the measurement gap length may indicate a measurement length (ML) in a NCSG pattern.

[0425] In an example, a measurement gap pattern may be associated with a cell group (CG), a frequency range (PR), or a group of carrier frequencies. An PR may be referred to as a frequency range # 1 (FR1 ) or a frequency range #2 (FR2). In an example, the one or more carrier frequencies may belong to, or may be associated with a FR (e.g., a FR1 , FR2, etc.). The frequencies within FR1 may be lower than frequencies within FR2. FR1 may be referred to as a low band or a mid-band frequency range. FR2 may be referred to as a millimeter wave frequency range or simply a millimeter frequency range. For example, FR1 may include frequencies from 410 MHz up to 7125 MHz. FR2 may include frequencies from 24.25 GHz up to 71 GHz.

[0426] In an example, a measurement gap associated with a CG may be referred to as a per CG measurement gap pattern or a per CG gap. In an example, a wireless device may interrupt a communication between the wireless device and a base station (e.g., at least partially) on one or more carrier frequencies belonging to a CG during a measurement gap of a per CG MG.

[0427] In an example, a measurement gap associated with a FR may be referred to as a per FR measurement gap pattern or a per FR gap. For example, a wireless device may interrupt a communication between the wireless device and a base station (e.g., at least partially) on one or more carrier frequencies belonging to an FR during a measurement gap of a per FR MG.

[0428] In another example, a measurement gap may be referred to as a per user equipment (UE) measurement gap pattern or a per UE gap. For example, a measurement gap pattern not associated with a CG, FR, or a group of carrier frequencies may be referred to as a per UE measurement gap pattern or a per UE gap. In an example, a wireless device may interrupt a communication between the wireless device and a base station (e.g., at least partially) on one or more carrier frequencies during a measurement gap of per a UE MG.

[0429] In an example, a network controlled small gap (NCSG) pattern may comprise two or more time periods. Each time period, of the two or more sub-time periods, includes a (starting / first) visible interruption length (VIL), a measurement length (ML), and a (endling / second) VIL. In an example, ML may be 1 ms, 2 ms, 3 ms, 4 ms, 5 ms, or any other reasonable time duration. In an example, VIL may be expressed (or defined) in terms of a number of time resources (e.g., X11 symbols, X12 slots, X12 subframes, etc.).Docket No.: 25-1062PCT

[0430] The start timings of any two successive VILs, of the two or more VILs, may be separated (in time) by a visible interruption repetition period (VI RP). For example, the start timings of any two successive time periods, of the two or more time periods, maybe separated (in time) by VIRP. In an example, VI RP may be 20 ms, 40 ms, 80 ms, 160 ms, or any other reasonable time duration.

[0431] A NCSG pattern may be associated / configured with an identifier. The identifier may also be referred to as an NCSG ID. A wireless device may communicate in a cell (e.g., a PCell, a PSCell, an activated SCell, etc.) during ML. The wireless device may be expected to support communication (e.g., receive / transmit) with a base station during ML. The wireless device may also perform a measurement during ML. The measurement may also be referred to as a measurement without (or outside) a gap (or without a measurement gap).

[0432] The wireless device may interrupt communications during a gap. The gap may also be referred to as a small gap, a visible gap (VIL), a known gap, an interruption duration, a visible interruption duration, or a known interruption duration. A length or duration of the gap (or the small gap or the visible interruption duration) may be referred to as VIL. For example, during a VIL, the wireless device may tune (or retune or change or modify or reconfigure or adapt) one or more parameters associated with a transceiver (e.g., a receiver and / or a transmitter) of the wireless device. The transceiver may also be referred to as a radio frequency (RF) front end or a radio transceiver. For example, the one or more parameters may be a bandwidth, a center frequency, a frequency location of an oscillator (e.g., a local oscillator (LO)) in a frequency domain, etc.

[0433] In an example, a wireless device may be configured a NCSG pattern for each cell group (CG) (CG NCSG), and / or for a single pattern for the wireless device (UE NCSG), and / or for each frequency range (e.g., FR1 , FR2) (FR NCSG). In an example, an NCSG pattern associated with a CG may be referred to as a CG NCSG pattern. In an example, an NCSG pattern associated with the wireless device may be referred to as a UE NCSG pattern. In an example, an NCSG pattern associated with a FR may be referred to as a FR NCSG pattern. In an example, a wireless device may interrupt communications between the wireless device and a base station (e.g., at least partially) on one or more carrier frequencies belonging to a CG during VILs based on a corresponding CG NCSG pattern. The wireless device may be configured with one or more NCSG patterns, where each of the one or more NCSG pattern is either a UE NCSG, a CG-NCSG, or FR-NCSG.

[0434] In an example, downlink radio link quality of a primary cell is monitored by a wireless device for the purpose of indicating out-of-sync / in-sync status to higher layers The wireless device is not required to monitor the downlink radio link quality in DL BWPs other than the active DL BWP on the primary cell unless the wireless device indicates a capability bwpOperationMeasWthoutlnterrupt. The wireless device may monitor radio link quality within the active BWP. If the active DL BWP is the initial DL BWP and for SS / PBCH block and CORESET multiplexing pattern 2 or 3, the wireless device is expected to perform RLM using the associated SS / PBCH block when the associated SS / PBCH block index is provided by RadioLinkMonitoringRS. The primary cell may be a PCell of a master cell group or a PSCell of a secondary cell group. A wireless device may be configured for each DL BWP of a SpCell (e.g., PCell of MCG, PSCell ofDocket No.: 25-1062PCTSCG) with a set of resource indexes, through a corresponding set of RadioLinkMonitoringRS, for radio link monitoring by failureDetectionResources. The wireless device is provided either a CSI-RS resource configuration index, by csi-RS-Index, or a SS / PBCH block index, by ssb-lndex. The wireless device may be configured with up to WLR-RLMRadioLinkMonitoringRS for link recovery procedures and for radio link monitoring. From the WLR-RLMRadioLinkMonitoringRS, up to WRLMRadioLinkMonitoringRS may be used for radio link monitoring and up to two RadioLinkMonitoringRS may be used for link recovery procedures. The wireless device may determine one or more RSs for the radio link monitoring based on one or more coresets configured for the primary cell. If a wireless device is configured with multiple DL BWPs for a serving cell (e.g ., the primary cell), the wireless device performs RLM using the RS(s) corresponding to resource indexes provided by RadioLinkMonitoringRS for the active DL BWP or, if RadioLinkMonitoringRS is not provided for the active DL BWP, using the RS(s) provided for the active TCI state for PDCCH receptions in CORESETs on the active DL BWP. In non-DRX mode operation, the physical layer in the wireless device assesses once per indication period the radio link quality, evaluated over the previous time period against thresholds (Qout and Qin) configured by rlmlnSyncOutOfSyncThreshold. The wireless device determines the indication period as the maximum between the shortest periodicity for radio link monitoring resources and 10 msec. In DRX mode operation, the physical layer in the wireless device assesses once per indication period the radio link quality, evaluated over the previous time period against thresholds (Qout and Q,n) provided by rlmlnSyncOutOfSyncThreshold. The wireless device determines the indication period as the maximum between the shortest periodicity for radio link monitoring resources and the DRX period. The physical layer in the wireless device indicates, in frames where the radio link quality is assessed, out-of-sync to higher layers when the radio link quality is worse than the threshold Qout for all resources in the set of resources for radio link monitoring. When the radio link quality is better than the threshold Qjnfor any resource in the set of resources for radio link monitoring, the physical layer in the wireless device indicates, in frames where the radio link quality is assessed, in-sync to higher layers.

[0435] A wireless device may be provided, for each BWP of a serving cell, a set q0of periodic CSI-RS resource configuration indexes by failureDetectionResourcesToAddModList and a set of periodic CSI-RS resource configuration indexes and / or SS / PBCH block indexes by candidateBeamRSList or candidateBeamRSListExt or candidateBeamRS-Listfor radio link quality measurements on the BWP of the serving cell. Instead of the sets q0and qltfor each BWP of a serving cell, the wireless device may be provided respective two sets q00and q01of periodic CSI-RS resource configuration indexes by failureDetectionSetl and failureDetectionSet2 that may be activated by a MAC CE and corresponding two sets q10andof periodic CSI-RS resource configuration indexes and / or SS / PBCH block indexes by candidateBeamRS-List and candidateBeamRS-List2, respectively, for radio link quality measurements on the BWP of the serving cell. The set q00is associated with the set q10and the set q01is associated with the set Qi.r

[0436] In non-DRX mode operation, the physical layer in the wireless device provides an indication to higher layers when the radio link quality for all corresponding resource configurations in the set q0, or in the set q00or q01, that theDocket No.: 25-1062PCTwireless device uses to assess the radio link quality is worse than the threshold Qout.LR . The physical layer informs the higher layers when the radio link quality is worse than the threshold Qout.LR with a periodicity determined by the maximum between the shortest periodicity among the SS / PBCH blocks on the PCell or the PSCell and / or the periodic CSI-RS configurations in the set q0, q00, or q01that the wireless device uses to assess the radio link quality and 2 msec. In DRX mode operation, the physical layer provides an indication to higher layers when the radio link quality is worse than the threshold Qout.LR with a periodicity based on a measurement requirement.

[0437] A wireless device may be provided, by schedulingRequest / D-BFR-SCell, a configuration for PUCCH transmission with a link recovery request (LRR) for the wireless device to transmit PUCCH. If the PCell or the PSCell is associated with sets00and q1;0, and with sets q0,i and q1:1, the UE can be provided by schedulingRequestID-BFR a first configuration for PUCCH transmission with a LRR and, if the UE provides twoLRRcapability, the wireless device may be provided by schedulingRequest / D-BFR2 a second configuration for PUCCH transmission with a LRR. If the wireless device is provided only the first configuration, the wireless device transmits a PUCCH with LRR for either set o,oorQo,i- th® wireless device is provided both the first and second configurations, the wireless device uses the first configuration to transmit a PUCCH with LRR associated with set qOfiand the second configuration to transmit a PUCCH with LRR associated with set q01.

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

[0439] 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 / enabled with a carrier switching; c) the wireless device may determine ‘A’ based on the first carrier and the 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 reception (across carriers) in a 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.

[0440] 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 deviceDocket No.: 25-1062PCTreceives 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.

[0441] In the specification, a bandwidth 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.

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

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

[0444] In the specification, DownlinkConfigCommon IE may refer DownlinkConfigCommonSIB IE.ServingCellConfigCommmon IE may refer Sen / ingCellConfigCommonSIB IE.

[0445] In the specification, a TDM pattern may be referred as a carrier switching pattern (e.g., carrierSwitchingPattern, CSPattem), a pattern fora carrier switching, a switching pattern, a time domain resource pattern, a cell switching pattern, TX-RX / RX pattern, PCell / SCell switching pattern, etc.

[0446] In the specification, a downlink carrier (DL) carrier (or a first carrier, a first cell) may be referred as an anchor carrier, an anchor DL carrier, a main carrier, an anchor cell, a main cell, a primary-role cell, a primary carrier, etc. In the specification, a supplementary carrier (DL) carrier (or a second carrier, a second cell) may be referred as a non-anchor carrier, an non-anchor DL carrier, a supplementary carrier, a non-anchor cell, a non-main cell, a secondary-role cell, a secondary carrier, etc.

[0447] In the specification, a carrier may be referred as a subband (e.g., a DL carrier is a DL subband, a UL carrier is a UL subband). For example, a cell may comprise a DL carrier that comprises a plurality of DL subbands and / or one or more UL subbands, where each of the plurality of DL subbands may correspond to a first carrier or a second carrier of the specification, and one of the one or more UL subbands may correspond to an uplink carrier of the specification.

[0448] In the specification, a switching gap maybe referred as a switching latency, a gap, a switching processing time, a RF switching latency, a carrier switching delay, a carrier switching latency, a CS switching gap, a CS gap, etc.

[0449] Certain challenges arise when a carrier switching (CS) pattern is used for switching between multiple cells— e.g., a first cell and a second cell— for a user equipment (UE), also known as a wireless device (WD).

[0450] Typically, the CS pattern defines two sets of time durations: a first set for the UE to communicate via the first cell and a second set for the UE to communicate via the second cell. As a result, when the CS pattern is in use, the UE may be restricted from receiving signals via the second cell during the first set of time durations and from receiving signals via the first cell during the second set of time durations. This configuration may cause an issue when the UE needs to measure reference signals. Specifically, for example, if the periodicity of receiving reference signals via theDocket No.: 25-1062PCTsecond cell differs from the periodicity of the second set of time durations, a scenario may arise where a reference signal is received via the second cell during one or more of the first set of time durations. However, since the UE is restricted from receiving signals via the second cell during the first set of time durations, the UE may be unable to receive and / or measure the reference signal. Missing the reference signal may result in the UE generating inaccurate measurement results and / or may impact measurement requirements of the UE.

[0451] The above issue assumes that the second cell is active. However, an additional challenge may arise when the second cell is in a power saving state (e.g., the first state, inactive state, etc.; refer to FIG. 18) such as a dormant state. In such scenario, even during the second set of time durations, the UE may not be able to receive reference signals via the second cell. For example, the UE may be configured to not fol low / apply the CS pattern when the second cell is in the power saving state, and, in such case, according to existing technologies, the UE may not be able to monitor the reference signals of the second cell when the second cell is in the power-saving state. In other words, at any given time when the second cell is in the power-saving state, the UE may be configured to receive reference signals solely via the first cell, regardless of whether the time period of receiving the reference signals overlaps with the first or second set of time durations of the CS pattern. As a result, the UE may be unable to measure the reference signals via the second cell.

[0452] In order to solve the above described problems, according to an embodiment of this disclosure, one or more measurement patterns is configured for the UE. Each measurement pattern may comprise multiple measurement time durations, during each of which the UE is able to measure reference signal(s) via the second cell, even if the measurement time duration overlaps with any of the first set of time durations and / or even if the measurement time duration does not overlap with any of the second set of time durations. Additionally or alternatively, each measurement pattern may comprise multiple measurement time durations, during each of which the UE is able to measure reference signal(s) via the first cell, even if the measurement time duration overlaps with any of the second set of time durations and / or even if the measurement time duration does not overlap with any of the first set of time durations.

[0453] In other words, according to an embodiment, a measurement pattern takes precedence over the CS pattern, enabling the UE to receive and measure the reference signal(s) via the first cell or the second cell, during a time duration, even when the time duration does not overlap with the first set of time durations of the CS pattern or the second set of time durations of the CS pattern.

[0454] More specifically, in an example of an embodiment of this disclosure, a method is provided. The method may comprise receiving, by a wireless device, one or more messages indicating a carrier switching pattern for switching between a first cell and a second cell. The method may also comprise measuring a reference signal of the second cell during a time duration. Instead of or in addition to measuring the reference signal of the second cell during the time duration, the method may comprise not measuring or skip measuring a reference signal of the first cell during the time duration, not transmitting or skip transmitting an uplink signal via the first cell during the time duration, and / or not communicating or skip communicating with the first cell during the time duration. The carrier switching pattern mayDocket No.: 25-1062PCTindicate the second cell during the time duration. The time duration may overlap with a measurement time duration of a measurement pattern for the second cell.

[0455] In another example of the embodiment of this disclosure, a different method is provided. The method may comprise receiving, by a wireless device, one or more messages indicating: i) a carrier switching pattern for switching between a primary cell (PCell) and a secondary cell (SCell) and ii) a measurement pattern for the SCell, wherein the measurement pattern is different from a measurement gap associated with the PCell and the SCell. The method also comprises measuring a reference signal of the SCell during a time duration. The time duration may overlap with a measurement time duration of the measurement pattern, and the carrier switching pattern may indicate the PCell during the time duration.

[0456] In a different example of the embodiment of this disclosure, a method is provided The method may comprise receiving, by a wireless device, one or more messages indicating a carrier switching pattern indicating: first time durations for communicating via a first cell; and second time durations for communicating via a second cell. The method also comprises, during a time duration, either communicating via the first cell or measuring a reference signal of the second cell, based on: whether the time duration overlaps with a serving cell measurement pattern, whether the time duration overlaps with either one of the first time durations or one of the second time durations, and whether the second cell is in a power saving state or in an active state.

[0457] In a different example of the embodiment of this disclosure, a method is provided. The method may comprise receiving, by a wireless device, one or more messages indicating: a carrier switching pattern indicating: first time durations configured for communicating via a first cell and second time durations configured for communicating via a second cell. The one or more messages may also indicate a serving cell measurement pattern for the second cell. The serving cell measurement pattern may be different from a measurement gap associated with the first cell and the second cell. The method further comprises performing one or more of: measuring, during the serving cell measurement pattern, a reference signal of the second cell and / or skipping measuring, during a second time duration of the second time durations and while the second cell is in a dormant state, the reference signal of the second cell, based on the second time duration not overlapping with the serving cell measurement pattern. The serving cell measurement pattern may overlap, in time, with a first time duration of the first time durations.

[0458] Configuring the measurement pattern for the UE to measure the reference signal(s) via the second cell ensures the UE to receive the reference signal(s) via the second cell during a time duration regardless of whether the time duration overlaps with any of the first set of time durations and regardless of whether the second cell is in an active state (e.g., non-power saving state, the second state, etc.; refer to FIG. 18) or in a power saving state (refer FIG. 18). Similarly, configuring the measurement pattern for the UE to measure the reference signal(s) via the first cell ensures the UE to receive the reference signal(s) via the first cell during a time duration regardless of whether the time duration overlaps with any of the second set of time durations.Docket No.: 25-1062PCT

[0459] FIG. 20 shows an example of CS pattern 2030. As shown in FIG. 20, CS pattern 2030 is for switching between a first cell (a.k.a., "1st cell”) 2040 and a second cell (a.k.a., “2ndcell”) 2050. More specifically, CS pattern 2030 indicates first cell 2040 during a first set of time durations (“TDs”) 2031, 2033, 2035, and 2037 and indicates second cell 2050 during a second set of TDs 2032, 2034, 2036, and 2038.

[0460] Note that, in this disclosure, a TD may also be referred to as a “time slot,” a “time period,” a “time window,” a “slot,” a “period,” and / or a “window.”

[0461] As shown in FIG. 20, the two sets of TDs are alternatively arranged in time, indicating that the two sets of TDs do not overlap in time. This means that UE 2010 may be configured not to communicate with a base station (“BS”) 2020 via first cell 2040 and second cell 2050 simultaneously.

[0462] In CS pattern 2030, UE 2010 is configured / allowed to communicate with (e.g., receiving a signal from, transmitting a signal to, and / or measuring a signal transmitted from, monitoring resources for a signal, etc.) BS 2020 via first cell 2040, during TDs 2031, 2033, 2035, and 2037. Similarly, UE 2010 is configured / allowed to communicate with BS 2020 via second cell 2050, which is in an active state, during TDs 2032, 2034, 2036, and 2038. Note that, in this disclosure, the expression “A / B” means “A and / or B.” For instance, the expression “configured / allowed” means “configured and / or allowed.”

[0463] In this disclosure, “active state” (e.g., a non-PS state, non-power saving state, the second state, refer FIG. 18) in which a cell is in during a time duration may comprise one or more of: a) a non-power saving state; b) a state in which an active bandwidth part (BWP) of the cell is a non-dormant BWP; c) a state in which an UE is configured to receive data (e.g., downlink control / data, PDCCH / PDSCH) via the cell and / or transmit data (e.g., uplink control / data, reference signal such as SRS, PUCCH / PUSCH / PRACH / SRS) during the time duration; and / or d) a state in which an UE is not allowed to skip communicating with a base station via the cell during the time duration.

[0464] In CS pattern 2030, UE 2010 is not allowed / configured to communicate with BS 2020 via first cell 2040, during TDs 2032, 2034, 2036, and 2038. Similarly, UE 2010 is not allowed / configured to communicate with BS 2020 via second cell 2050, during TDs 2031, 2033, 2035, and 2037. For instance, as illustrated in FIG. 20, during TDs 2033 and 2037, UE 2010 may not be allowed / configured to measure reference signals (“RSs”) 2054 and 2060 of second cell 2050 because CS pattern 2030 indicates first cell during TDs 2033 and 2037.

[0465] The periodicity of TDs 2031 , 2033, 2035, and 2037 and the periodicity of TDs 2032, 2034, 2036, and 2038 may be the same or different. However, for simple explanation purpose, it will be assumed that the two periodicities are the same, and they will be referred to as “Pcs-Pattem” (e.g., 20 ms).

[0466] As shown in FIG. 20, BS 2020 is configured to periodically transmit RSs 2052, 2054, 2056, 2058, and 2060 of second cell 2050. The RSs of second cell 2050 may have a periodicity of “PRS” (e.g., 13 ms). Note that, for simple referencing purpose, RSs 2052, 2054, 2056, 2058, and 2060 may be referred to as a single RS as they may correspond to multiple (e.g., repeated and periodic / aperiodic) transmissions / retransmissions of the same reference signal.Docket No.: 25-1062PCT

[0467] As discussed above, when CS pattern 2030 is configured and in use, and when second cell 2050 is in the active state, UE 2010 may be configured / allowed to measure RSs of second cell 2050, during TDs 2032, 2034, 2036, and 2038 but not during TDs 2031, 2033, 2035, and 2037 because CS pattern 2030 indicates first cell 2040 during TDs 2031, 2033, 2035, and 2037. However, because Pcs-Pattem (e.g., 20 ms) and PRS (e.g., 13 ms) are different, as the transmission of the RSs of second cell 2050 progresses, some of the RSs of second cell 2050 may be transmitted during TDs 2031, 2033, 2035, and 2037. For instance, while three RSs 2052, 2056, and 2058 of second cell 2050 are transmitted during TDs 2032, 2034, and 2036, the remaining two RSs 2054 and 2060 of second cell 2050 are transmitted during TDs 2033 and 2037. However, because, in CS pattern 2030, UE 2010 is configured / allowed to measure RSs of second cell 2050 only during TDs 2032, 2034, 2036, and 2038, UE 2010 may be unable to measure RSs 2054 and 2060.

[0468] As discussed above, the problem of being unable to communicate with BS 2020 via second cell 2050 may occur when second cell 2050 is in the active state. However, the problem may also occur when second cell 2050 is in a power saving (PS) state. This is illustrated in FIG.21.

[0469] In this disclosure, "PS state” (e.g., power saving state, inactive state, non-active state, the first state, refer FIG.18) in which a cell is in during a TD may comprise one or more of: a) a dormant state based on an active BWP of the cell being a dormant BWP during the time duration; b) a state in which inactive period(s), of cell discontinuous transmission and reception (C-DTX / DRX) pattern associated-with / of the cell, overlaps with the TD; c) a deactivated state that is based on the cell being deactivated; and / or d) a state in which inactive period(s), of a DRX pattern associated-with / of the cell overlaps with the TD

[0470] As shown in FIG. 21, when second cell 2050 is in the PS state, UE 2010 may not be allowed / configured to communicate with (e.g., receiving a signal from, transmitting a signal to, and / or measuring a signal transmitted from, etc.) BS 2020 via second cell 2050 during a TD, regardless of whether CS pattern 2030 indicates first cell 2040 or second cell 2050 during the TD. More specifically, even during TDs 2032, 2034, 2036, and 2038 of CS pattern 2030, UE 2010 may not be allowed / configured to communicate with BS 2020 via second cell 2050. Indeed, when second cell 2050 is in the PS state, UE 2010 may not be able to communicate via second cell 2050. For example, when second cell 2050 is in the PS state, UE 2010 may consider that CS pattern 2030 is disabled or not being used or not being applied. When CS pattern 2030 is not used, UE 2010 may communicate via first cell 2040 and may not communicate via second cell 2050. In the example, UE 2010 may determine first cell 2040 to communicate during second cell 2050 being the PS state based on one or more conditions being satisfied. In the example, UE 2010 may determine to disable CS pattern 2030 based on the one or more conditions being satisfied. The one or more conditions may comprise one or more of: a) a first cell index of first cell 2040 may be lower than a second cell index of second cell 2040; b) first cell 2040 may be configured with an uplink carrier; c) first cell 2040 may be a primary cell of a cell group; e) first cell 2040 may be a PUCCH-cell of a cell group; f) first cell 2040 may be configured with PUCCH resources; g) second cell 2050 may not be configured with an uplink carrier; h) second cell 2050 may be a secondary cell of a cell group; I) second cellDocket No.: 25-1062PCT2050 may not be a PUCCH-cell of a cell group; j) second cell 2050 may not be configured with PUCCH resources; k) BS 2020 may transmit configuration parameter(s) (e.g., ovem'dingCSPattemOnDormantState) (e.g., via RRC, MAC CE, DCI) indicating to disable CS pattern 2030 when second cell 2040 is in PS state.

[0471] In order to solve the above described problems, according to an embodiment of this disclosure, a process 2200 shown in FIG. 22 is provided. Process 2200 may begin with step 2202.

[0472] Step 2202 comprises UE 2010 receiving message(s) 2222 indicating CS pattern 2030 for switching between first cell 2040 and second cell 2050. Note that, in this disclosure, the expression “element(s)” means one or more elements. For instance, “message(s)" means one or more messages.

[0473] There are different ways for message(s) 2222 to indicate CS pattern 2030. For instance, the message(s) may comprise configuration parameter(s) of first cell 2040, second cell 2050, and / or a cell group including first cell 2040 and / or second cell 2050, and the configuration parameter(s) may indicate 1) the periodicity of CS pattern 2030 and 2) a bitmap within / associated with / for each TD of CS pattern 2030. The bitmap in each TD may indicate whether the corresponding TD is for first cell 2040 or second cell 2050. For instance, in FIG. 20, a bitmap within / associated with / for each of TDs 2031, 2033, 2035, and 2037 may indicate first cell (e.g., ‘0’ or ‘1’, a first value) 2040 while a bitmap within / associated with / for each of TDs 2032, 2034, 2036, and 2038 may indicate second cell 2050 (e.g., ‘T or ‘O', a second value).

[0474] First cell 2040 may be a primary cell (PCell) of UE 2010 and second cell 2050 may be a secondary cell (SCell) of UE 2010. Both first cell 2040 and second cell 2050 may be the serving cells of UE 2010. For instance, first cell 2040 may be a primary serving cell of UE 2010 while second cell 2050 may be a secondary / additional serving cell of UE 2010. Both first cell 2040 and second cell 2050 may be secondary cells of UE 2010. Both first cell 2040 and second cell 2050 may belong to a timing-advance group (TAG) and / or may belong to a cell group (CG).

[0475] After receiving message(s) 2222, in step 2204, UE 2010 may measure RS(s) (e.g., CSI-RS or SSB) of second cell 2050 during a TD 2224. Note that even though, for simple explanation purpose, measuring RS(s) is used as an example of an operation performed by UE 2010 during a time duration, different operation(s) may be performed by UE 2010 instead of or in addition to measuring RS(s). For instance, in this disclosure, any instance of measuring RS(s) may be replaced with receiving signal(s), transmitting signal(s), receiving RS(s), communicating with BS 2020, etc.

[0476] Examples of measuring RS(s) include but are not limited to performing an L1 measurement of channel state information reference signal (CSI-RS) or SSB for L1 reference signal received power (L1-RSRP) and performing measurements for L1-SINR, beam management, candidate beam measurement, beam failure detection (BFD) RS measurement, radio link failure (RLM) RS measurement, link failure (e.g., link recovery RS) measurement, CSI measurement, automatic gain control (AGC), beam management, synchronization signal block (SSB) measurements, RSRP, RSRQ, LTM L3 condition handover measurement, LTM condition handover, LTM measurement, L3 measurements, positioning, etc.Docket No.: 25-1062PCT

[0477] L1-RSRP may refer a L1 measurement to measure a reference signal received power (RSRP) by receiving the RS (e.g., CSI-RS, SSB). L1-SINR may refer a L1 measurement to measure signal-to-noise ratio (SINR) of the received RS. L1 may refer that the wireless device may use a L1 filter to accumulate and / or determine measurement results across multiple measurements on the RS over a measurement window (e.g., 3 samples of SSB occasion / transmission or CSI-RS transmission). Beam management may refer any measurement (e.g., L1 measurement) to support a beam management (e.g., beam recovery, beam change, etc.). Beam management may comprise measurements on candidate beam RSs (e.g., candidate beam detection RS, CBD-RS, RSs configured via candidateBeamRSList IE), on beam failure detection RSs (e.g., BFD-RSs, RSs configured via failureDetectionResourcesToAddModList, RadioLinkMonitoringRS, failureDetectionResources). The BFD-RS measurements may refer those measurements on RSs configured for beam failure detection. The wireless device may determine in-sync or out-of-sync based on a quality of the measurements on the RSs. Based on the BFD-RS measurements, the wireless device may determine a beam failure detection and / or may determine a beam failure and / or may initiate a beam failure recovery procedure. The RLM-RS measurements may refer those measurements on RSs configured for a radio link failure (e.g., RadioLinkMonitoringRS). Based on the measurements, the wireless device may determine a radio link failure on a cell The link failure RSs measurements may refer those measurements on RSs configured for a beam failure and / or a link failure (e.g., RLM). The RSs may be configured by failureDetectionResourcesToAddModList, RadioLinkMonitoringRS, failureDetectionResources IE.

[0478] The CSI measurement may refer a CSI report configured by a CSI-ReportContig IE. A CSi-ReportConfig IE may indicate a report type (e.g , a periodic, a semi-persistent, an aperiodic) and / or CSI-RS resources for measurement and / ora report quantity (e.g., L1-RSRP, CQI, PMI, etc.).

[0479] The AGC may be used to update RF's synchronization and filter to receive downlink data and / or transmit uplink data. SSB measurements may refer L1 measurement and / or L3 measurements based on SSB (e.g., monitoring / measuring on SSB). RSRP may refer a L3 measurement to obtain a RSRP on a RS (e.g., CSI-RS, SSB). The L3 measurement may refer that the wireless device uses L3 filter to accumulate and / or determine measurement results across multiple measurements on the RS over a measurement window (e.g. 5 times over a SMTC periodicity, measCycleSCell for deactivated SCell). RSRQ may refer a L3 RSRQ measurement where RSRQ refers a received signal received quality, UE 2010 may measure RSRP on RS(s) and also measure interference on RS(s). Based on the RSRP and the interference, UE 2010 may determine the RSRQ. LTM L3 conditional handover measurement may refer one or more L3 / L1 measurements configured to support a condition handover for L3 LTM. LTM condition handover measurements may refer one or more L1 measurements configured to support a conditional handover for LTM. LTM measurements may refer L1 / L3 measurements configured to support LTM procedure. Positioning may refer measurements on positioning related RSs (e.g., positioning reference signal, PRS, positioning processing window, etc.)Docket No.: 25-1062PCT

[0480] Furthermo...

Claims

1. Docket No.: 25-1062PCTCLAIMS1. A method comprising:receiving, by a wireless device, one or more radio resource control (RRC) messages indicating:a bitmap indicating a switching pattern for switching between a first cell and a second cell;a scheduling request (SR) configuration for a link recovery request of the first cell indicating:a physical uplink control channel (PUCCH) resource; anda first periodicity of the SR configuration;one or more beam failure detection reference signals of the first cell; andone or more synchronization signal blocks (SSBs) of the first cell with a second periodicity, as one or more candidate beam detection reference signals (CBD-RSs) of the second cell;determining a beam failure based on the one or more beam failure detection reference signals; performing, during a time duration, a link recovery for the second cell, wherein the time duration is based on:the first periodicity of the SR configuration; anda CBD evaluation period, wherein the CBD evaluation period is based on:the second periodicity of the one or more SSBs;a total number of CBD-RS resource occasions within a time window; and a first number of CBD-RS resource occasions, within the time window, overlapping with one or more slots assigned to the second cell based on the bitmap indicating the switching pattern; and transmitting, via the PUCCH resource and during the time duration, a scheduling request indicating the link recovery request.

2. A method comprising performing, by a wireless device and during a time duration, a link recovery, wherein the time duration is based on a first number of candidate beam detection, (CBD) reference signal (CBD-RS) resource occasions, within a time window, overlapping with one or more slots, assigned to a first cell, based on a switching pattern for switching between the first cell and a second cell.

3. The method of claim 2, wherein:the time duration is based on a CBD evaluation period; andthe CBD evaluation period is based on the first number of CBD-RS resource occasions.

4. The method of claim 3, wherein the CBD evaluation period is further based on:a periodicity of one or more synchronization signal blocks, SSBs; anda total number of CBD-RS resource occasions within the time window.

5. The method of any one of claims 2-4, wherein the time duration is further based on a periodicity of physical uplink control channel, PUCCH, transmission configured with a scheduling request, SR, fora beam failure recovery; and 6. The method of any one of claims 2-5, further comprising determining the time duration.

7. The method of any one of claims 2-6, wherein the link recovery is for the first cell.Docket No.: 25-1062PCT8. The method of any one of claims 5-7, wherein:performing the link recovery comprises transmitting, during the time duration and via the PUCCH transmission, the SR for the beam failure recovery; andthe SR for the beam failure recovery indicates the link recovery request.

9. The method of any one of claims 2-8, further comprising determining a beam failure based on one or more beam failure detection reference signals (BFD-RSs), wherein the link recover is performed based on determining the beam failure.

10. The method of claim 9, wherein the one or more BFD-RSs are of the first cell.

11. The method of any one of claims 2-10, further comprising receiving, by the wireless device, one or more radio resource control (RRC) messages indicating one or more of:a bitmap indicating the switching pattern for switching between the first cell and the second cell;an SR configuration, for the link recovery request, indicating:a PUCCH resource for the PUCCH transmission; anda periodicity of SR indicating the periodicity of the PUCCH transmission;the one or more BFD-RSs; andthe one or more SSBs as one or more CBD-RSs.

12. The method of claim 11, wherein:the one or more SSBs are of the first cell; andthe one or more CBD-RSs are of the first cell.

13. The method of claim 11, wherein:a first bit value, for a first slot, in the bitmap indicates that the wireless device is configured to transmit and / or receive via the second cell in the first slot; anda second bit value, for a second slot, in the bitmap indicates that the wireless device is configured to receive via the first cell in the second slot.

14. The method of any one of claims 2-13, wherein:the second cell is a primary cell operating in a frequency duplex division (FDD) band;the first cell is a secondary cell operating in a supplementary downlink (SDL) band; andthe first cell and the second cell belong to a cell group.

15. The method of any one of claims 11-14, wherein the one or more RRC messages comprising:a parameter indicating an index of the SR configuration, wherein the wireless device uses the SR configuration upon determining the beam failure based on the one or more BFD-RSs;one or more parameters indicating the bitmap indicating the switching pattern;one or more parameters indicating the one or more BFD-RSs; andone or more parameters indicating the one or more CBD-RSs.Docket No.: 25-1062PCT16. The method of any one of claims 11-15, wherein the one or more RRC messages comprise a plurality of parameters, of the SR configuration, comprising:a parameter indicating an index of PUCCH configuration for the PUCCH resource; andone or more parameters indicating the periodicity of SR, wherein the periodicity of SR is the periodicity of the PUCCH transmission.

17. The method of any one of claims 9-16, wherein the determining the beam failure based on the one or more BFD- RSs comprises determining the beam failure based on measurement results of the one or more BFD-RSs.

18. The method of claim 17, wherein the measurement results comprise one or more of:a layer 1 reference signal received power (L1-RSRP);a layer 1 reference signal received quality (L1-RSRQ); anda layer 1 signal to interference and noise ratio (L1-SINR).

19. The method of any one of claims 2-18, wherein the one or more slots assigned to the first cell based on the bitmap comprises that a respective bit value, for each of the one or more slots, in the bitmap indicates that the wireless device is configured to receive via the first cell in the slot.

20. The method of any one of claims 5-19, wherein:the time duration for the link recovery request comprises an allowed time duration in which the wireless device transmits the PUCCH transmission with the link recovery request after the beam failure recovery is triggered on the first cell; andthe PUCCH transmission comprises the transmitting the SR via the PUCCH resource.

21. The method of any one of claims 11-20, wherein the transmitting the SR is:via the second cell; andduring a slot, wherein the slot is assigned to the second cell based on the bitmap indicating the switching pattern.

22. The method of claim 21 , wherein the slot assigned to the second cell based on the bitmap comprises that a bit value, for the slot, in the bitmap indicates that the wireless device is configured to transmit and / or receive via the second cell in the slot.

23. A method comprising:receiving, by a wireless device, one or more messages indicating:a carrier switching pattern for switching between a primary cell (PCell) and a secondary cell (SCell); anda measurement pattern for the SCell, wherein the measurement pattern is different from a measurement gap associated with the PCell and the SCell; andmeasuring a reference signal of the SCell during a time duration, wherein:the time duration overlaps with a measurement time duration of the measurement pattern; andDocket No.: 25-1062PCTthe carrier switching pattern indicates the PCell during the time duration.

24. A method comprising:receiving, by a wireless device, one or more messages indicating a carrier switching pattern for switching between a first cell and a second cell; andmeasuring a reference signal of the second cell during a time duration, wherein:the time duration overlaps with a measurement time duration of a measurement pattern for the second cell; and / orthe carrier switching pattern indicates the second cell during the time duration.

25. The method of claim 24, wherein:the first cell is a primary cell (PCell); andthe second cell is a secondary cell (SCell).

26. The method of claim 24 or 25, wherein the one or more messages indicate the measurement pattern for the second cell.

27. The method of any one of claims 24-[0545], wherein the measurement pattern for the second cell is different from one or more measurement gaps associated with the first cell and the second cell.

28. The method of any one of claims 24-27, wherein:the carrier switching pattern indicates the first cell during the time duration; andthe time duration overlaps with a measurement time duration of the measurement pattern for the second cell.

29. The method of any one of claims 24-28, wherein:the time duration is a first time duration;the method comprises measuring a reference signal of the first cell during a second time duration;a reference signal of the second cell is not measured during the second time duration;the second cell is in an active state during the second time duration; andthe second time duration overlaps with a measurement time duration of a measurement pattern for the first cell.

30. The method of claim 29, wherein the second time duration overlaps with a measurement time duration of the measurement pattern for the second cell.

31. The method of claim 29 or [0558], wherein the carrier switching pattern indicates the second cell during the second time duration.

32. The method of any one of claims 29-31, wherein:the reference signal of the second cell is measured during the time duration and / or a reference signal of the first cell is not measured during the time duration;the second cell is in an inactive period of a discontinuous transmission scheme (DTX) during the time duration or in a power saving state during the time duration; andDocket No.: 25-1062PCTthe time duration does not overlap with a measurement time duration of a measurement pattern for the first cell.

33. The method of claim 32, wherein the time duration overlaps with a measurement time duration of a measurement pattern for the second cell.

34. The method of any one of claims 24-33, wherein:the carrier switching pattern indicates the second cell during the time duration;the one or more measurement gaps comprise a measurement gap for the first cell and / or a measurement gap for the second cell; andthe time duration does not overlap with the measurement gap for the first cell and / or the measurement gap for the second cell.

35. The method of claim 34, wherein:the time duration is a first duration;the carrier switching pattern indicates either the first cell or the second cell during a second time duration; the second time duration at least partially overlaps with the measurement gap for the first cell and / or the measurement gap for the second cell; andno downlink signal is received via the first cell and / or the second cell during the at least partially overlapped portion of the second time duration, wherein the downlink signal comprises downlink control and / or downlink data.

36. The method of claim 35, wherein the second time duration overlaps with a measurement time duration of the measurement pattern for the second cell and / or a measurement time duration of a measurement pattern for the first cell.

37. The method of any one of claims 24-36, wherein:the one or more messages comprise one or more configuration parameters of the second cell; and the one or more configuration parameters indicate the measurement pattern for the second cell.

38. The method of any one of claims 24-37, wherein:the one or more messages comprise one or more configuration parameters of a cell group including the second cell; andthe one or more configuration parameters comprise one or more configuration parameters indicating the measurement pattern for the second cell.

39. The method of claim 37 or 38, wherein the measurement pattern is different from a synchronization signal block (SSB) measurement transmission configuration (SMTC) of the second cell .

40. The method of any one of claims 24-39, wherein:the one or more messages indicate an SMTC of the second cell; andDocket No.: 25-1062PCTthe method comprises determining, based on the SMTC of the second cell, the measurement pattern for the second cell41. The method of any one of claims 2-40, wherein the first number of CBD-RS resource occasions, within the time window, overlaps with a measurement gap.

42. 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 -41.

43. 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-41.

Images