Multicarrier switching pattern adaptation

Abstract

A method comprises receiving, by a wireless device, one or more configuration parameters indicating first time periods for first downlink receptions via a first cell and second time periods for second downlink receptions via a second cell. The method further comprises monitoring for and / or receiving the first downlink receptions via the first cell during one or more time periods of the second time periods.

Description

Docket No.: 25-1051 PCTTITLEMulticarrier Switching Pattern AdaptationCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 779,073, 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-1051 PCT

[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. 18 illustrates 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] FIGs. 24A and 24B illustrate aspects of example embodiments 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.

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

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

[0041] FIG. 35 illustrates an aspect of an example embodiment according to the present disclosure.

[0042] FIG. 36 illustrates an aspect of an example embodiment according to the present disclosure.

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

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

[0045] 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 andDocket No.: 25-1051 PCTconfigurable, 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.

[0046] Embodiments may be configured to operate as needed. The disclosed mechanism may be performed when certain criteria are met, for example, in a wireless device, a base station, a radio environment, a network, a combination of the above, and / or the like. Example criteria may be based, at least in part, on for example, wireless device or network node configurations, traffic load, initial system set up, packet sizes, traffic characteristics, a combination of the above, and / or the like. When the one or more criteria are met, various example embodiments may be applied.Therefore, it may be possible to implement example embodiments that selectively implement disclosed protocols.

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

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

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

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

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

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

[0053] 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 aDocket No.: 25-1051 PCTmodeling / simulation program such as Simulink, Stateflow, GNU Octave, or LabVI E WMathScript. It may be possible to implement modules using physical hardware that incorporates discrete or programmable analog, digital and / or quantum hardware. Examples of programmable hardware comprise: computers, microcontrollers, microprocessors, applicationspecific integrated circuits (ASICs); field programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers and microprocessors are programmed using languages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDs are often programmed using hardware description languages (HDL) such as VHSIC hardware description language (VHDL) or Verilog that configure connections between internal hardware modules with lesser functionality on a programmable device. The mentioned technologies are often used in combination to achieve the result of a functional module.

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

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

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

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

[0058] 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 aDocket No.: 25-1051 PCTdonor node, a Next Generation Evolved Node B (ng-eNB), a Generation Node B (g N B, associated with NR and / or 5G standards), an access point (AP, associated with, for example, Wi-Fi or any other suitable wireless communication standard), and / or any combination thereof. A base station may comprise at least one g N B Central Unit (gNB-CU) and at least one a g NB Distributed Unit (gNB-DU).

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

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

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

[0062] The Third-Generation Partnership Project (3GPP) was formed in 1998 to provide global standardization of specifications for mobile communication networks similarto 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 6GDocket No.: 25-1051 PCTnetwork). 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.

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

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

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

[0066] 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 / orDocket No.: 25-1051 PCTsession 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.

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

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

[0069] As shown in FIG 1B, the gNBs 160 and / or the ng-eNBs 162 may be connected to the 5G-CN 152 by means of an NG interface and to other base stations by an Xn interface. The NG and Xn interfaces may be established using direct physical connections and / or indirect connections over an underlying transport network, such as an internet protocol (IP) transport network. The gNBs 160 and / or the ng-eNBs 162 may be connected to the UEs 156 by means of a Uu interface. For example, as illustrated in FIG. 1B, gNB 160A maybe connected to the UE 156A by meansofa Uu interface. The NG, Xn, and Uu interfaces are associated with a protocol stack. The protocol stacks associated with the interfaces may be used by the network elements in FIG. 1 B to exchange data and signaling messages and may include two planes: a user plane and a control plane. The user plane may handle data of interest to a user. The control plane may handle signaling messages of interest to the network elements.

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

[0071] 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 EvolvedDocket No.: 25-1051 PCTUMTS 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.

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

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

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

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

[0076] 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.Docket No.: 25-1051 PCTFor reflective mapping, the SDAP 225 at the g NB 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.

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

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

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

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

[0081] The PHYs 211 and 221 may perform mapping of transport channels to physical channels and digital and analog signal processing functions for sending and receiving information over the air interface. These digital and analog signal processing functions may include, for example, coding / decoding and modulation / demodulation. The PHYs 211 and 221 may perform multi-antenna mapping. As shown in FIG.3, the PHYs 211 and 221 may provide one or more transport channels as a service to the MACs 212 and 222.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0099] - a random access channel (RACH) for allowing a UE to contact the network without any prior scheduling.Docket No.: 25-1051 PCT

[0100] The PHY may use physical channels to pass information between processing levels of the PHY. A physical channel may have an associated set of time-frequency resources for carrying the information of one or more transport channels. The PHY may generate control information to support the low-level operation of the PHY and provide the control information to the lower levels of the PHY via physical control channels, known as L1 / L2 control channels. The set of physical channels and physical control channels defined by NR include, for example:

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

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

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

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

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

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

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

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

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

[0110] The RRCs 216 and 226 may provide control plane functionality between the UE 210 and the gNB 220 or, more generally, between the UE 210 and the RAN. The RRCs 216 and 226 may provide control plane functionality between the UE 210 and the gNB 220 via signaling messages, referred to as RRC messages. RRC messages may be transmitted between the UE 210 and the RAN using signaling radio bearers and the same / similar PDCP, RLC, MAC, and PHY protocol layers. The MAC may multiplex control-plane and user-plane data into the same transport block (TB). The RRCs 216 and 226 may provide control plane functionality such as: broadcast of system information related to AS and NAS; paging initiated by the CN or the RAN; establishment, maintenance and release of an RRC connection between the UE 210 and the RAN; security functions including key management; establishment, configuration, maintenance and release of signaling radio bearers and data radio bearers; mobility functions; QoS management functions; the UE measurement reporting and control of the reporting; detection of and recovery from radio link failure (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.

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

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

[0113] 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 receptionDocket No.: 25-1051 PCTcycle) to monitor for paging messages from the RAN. Mobility of the UE maybe managed by the UE through a procedure known as cell reselection. The RRC state may transition from RRC idle 604 to RRC connected 602 through a connection establishment procedure 612, which may involve a random access procedure as discussed in greater detail below.

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

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

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

[0117] RAN areas may be used to track the UE at the RAN level. Fora UE in RRC inactive 606 state, the UE maybe 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.

[0118] 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 ofDocket No.: 25-1051 PCTtime 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.

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

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

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

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

[0123] A slot may have a fixed number of OFDM symbols (e.g., 14 OFDM symbols). A numerology with a higher subcarrier spacing has a shorter slot duration and, correspondingly, more slots per subframe. FIG. 7 illustrates this numerology-dependent slot duration and slots-per-subframe transmission structure (the numerology with a subcarrier spacing of 240 kHz is not shown in FIG.7 for ease of illustration). A subframe in NR may be used as a numerologyindependent time reference, while a slot may be used as the unit upon which uplink and downlink transmissions are scheduled. To support low latency, scheduling in NR may be decoupled from the slot duration and start at any OFDM symbol and last for as many symbols as needed for a transmission. These partial slot transmissions may be referred to as mini-slot or subslot transmissions.

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

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

[0126] NR may support wide carrier bandwidths (e.g., up to 400 MHz for a subcarrier spacing of 120 kHz). Notall UEs may be able to receive the full carrier bandwidth (e.g., due to hardware limitations). Also, receiving the full carrier bandwidth may be prohibitive in terms of UE power consumption. In an example, to reduce power consumption and / 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.

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

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

[0129] For a downlink BWP in a set of configured downlink BWPs on a primary cell (PCell), a base station may configure a UE with one or more control resource sets (CORESETs) for at least one search space. A search space is a set of locations in the time and frequency domains where the UE may find control information. The search space may be a UE-specific search space or a common search space (potentially usable by a plurality of UEs). For example, a base station may configure a UE with a common search space, on a PCell or on a primary secondary cell (PSCell), in an active downlink BWP.

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

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

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

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

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

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

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

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

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

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

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

[0141] 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 differentDocket No.: 25-1051 PCTPCells. In the downlink, the carrier corresponding to the PCell may be referred to as the downlink primary CC (DL PCC). In the uplink, the carrier corresponding to the PCell may be referred to as the uplink primary CC (UL PCC). The other aggregated cells for the UE may be referred to as secondary cells (SCells) . In an example, the SCells may be configured after the PCell is configured for the UE. For example, an SCell may be configured through an RRC Connection Reconfiguration procedure. In the downlink, the carrier corresponding to an SCell may be referred to as a downlink secondary CC (DL SCC). In the uplink, the carrier corresponding to the SCell may be referred to as the uplink secondary CC (ULSCC).

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

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

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

[0145] 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,Docket No.: 25-1051 PCTfor example, depending on the context in which the physical cell ID is used. A physical cell ID may be determined using a synchronization signal transmitted on a downlink component carrier. A cell index may be determined using RRC messages. In the disclosure, a physical cell ID may be referred to as a carrier ID, and a cell index may be referred to as a carrier index. For example, when the disclosure refers to a first physical cell ID for a first downlink carrier, the disclosure may mean the first physical cell ID is for a cell comprising the first downlink carrier. The same / similar concept may apply to, for example, a carrier activation. When the disclosure indicates that a first carrier is activated, the specification may mean that a cell comprising the first carrier is activated.

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

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

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

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

[0150] 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, theDocket No.: 25-1051 PCTUE may monitor a frequency location within the carrier If the PSS is not found after a certain duration (e.g . , 20 ms), the UE may search for the PSS at a different frequency location within the carrier, as indicated by a synchronization raster. If the PSS is found at a location in the time and frequency domains, the UE may determine, based on a known structure of the SS / PBCH block, the locations of the SSS and the PBCH, respectively. The SS / PBCH block may be a celldefining SS block (CD-SSB). In an example, a primary cell may be associated with a CD-SSB. The CD-SSB may be located on a synchronization raster. In an example, a cell selection / search and / or reselection may be based on the CD-SSB.

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

[0152] The PBCH may use a QPSK modulation and may use forward error correction (EEC). The EEC 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 (SEN) 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.

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

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

[0155] 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 aDocket No.: 25-1051 PCTsecond 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.

[0156] The CSI-RS may be transmitted by the base station and used by the UE to acquire channel state information (CSI). The base station may configure the UE with one or more CSI-RSs for channel estimation or any other suitable purpose. The base station may configure a UE with one or more of the same / similar CSI-RSs. The UE may measure the one or more CSI-RSs. The UE may estimate a downlink channel state and / or generate a CSI report based on the measuring of the one or more downlink CSI-RSs. The UE may provide the CSI report to the base station. The base station may use feedback provided by the UE (e.g., the estimated downlink channel state) to perform link adaptation.

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

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

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

[0160] 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 mayDocket No.: 25-1051 PCTsupport 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.

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

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

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

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

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

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

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

[0168] 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 domainDocket No.: 25-1051 PCTbehavior 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.

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

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

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

[0172] 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 aDocket No.: 25-1051 PCTthird 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.

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

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

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

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

[0177] A UE may initiate a beam failure recovery (BFR) procedure based on detecting a beam failure. The UE may transmit a BFR request (eg., 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).

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

[0179] 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 oneDocket No.: 25-1051 PCTor 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.

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

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

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

[0183] 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 UEDocket No.: 25-1051 PCTmay 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).

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

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

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

[0187] The Msg 2 1312 received by the UE may include an RAR. In some scenarios, the Msg 21312 may include multiple RARs corresponding to multiple UEs. The Msg 21312 may be received after or in response to the transmitting of the Msg 1 1311. The Msg 21312 maybe scheduled on the DL-SCH and indicated on a PDCCH using a random access RNTI (RA-RNTI). The Msg 2 1312 may indicate that the Msg 1 1311 was received by the base station. The Msg 21312 may include a time-alignment command that may be used by the UE to adjust the UE’s transmission timing, a scheduling grant for transmission of the Msg 31313, and / or a Temporary Cell RNTI (TC-RNTI). After transmitting a preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor a PDCCH for the Msg 21312. The UE may determine when to start the time window based on a PRACH occasion that the UE uses to transmit the preamble. For example, the UE may start the time window one or more symbols after a last symbol of the preamble (e.g , at a first PDCCH occasion from an end of a preamble transmission). The one or more symbols may be determined based on a numerology. The PDCCH may be in a common search space (e.g., a Typel -PDCCH common search space) configured by an RRC message. The UE may identify the RAR based on a Radio Network Temporary Identifier (RNTI). RNTIs may be used depending on one or more events initiating the random access procedure. The UE may use random access RNTI (RA-RNTI). The RA-RNTI may be associated with PRACH occasions in which the UE transmits a preamble. For example, the UE may determine the RA-RNTI based on: an OFDM symbol index; a slot index; a frequency domain index; and / or a UL carrier indicator of the PRACH occasions. An example of RA-RNTI may be as follows:

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

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

[0190] 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 baseDocket No.: 25-1051 PCTstation), Msg 4 1314 will be received using a DL-SCH associated with the TC-RNTI. If a MAC PDU is successfully decoded and a MAC PDU comprises the UE contention resolution identity MAC CE that matches or otherwise corresponds with the CCCH SDU sent (e.g., transmitted) in Msg 31313, the UE may determine that the contention resolution is successful and / or the UE may determine that the random access procedure is successfully completed.

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

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

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

[0194] 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 aDocket No.: 25-1051 PCTpreamble 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.

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

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

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

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

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

[0200] A UE and a base station may exchange control signaling. The control signaling may be referred to as L1 / L2 control signaling and may originate from the PHY layer (e.g., layer 1) and / or the MAC layer (e.g., layer 2). The control signaling may comprise downlink control signaling transmitted from the base station to the UE and / or uplink control signaling transmitted from the UE to the base station.

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

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

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

[0204] 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 (eg., 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 forDocket No.: 25-1051 PCTscheduling of PDSCH in a cell (e.g., with more DCI payloads than DCI format 1_0). DCI format 2_0 may be used for providing a slot format indication to a group of UEs. DCI format 2_1 may be used for notifying a group of UEs of a physical resource block and / or OFDM symbol where the UE may assume no transmission is intended to the UE. DCI format 2_2 may be used for transmission of a transmit power control (TPC) command for PUCCH or PUSCH. DCI format 2_3 may be used for transmission of a group of TPC commands for SRS transmissions by one or more UEs. DCI format(s) for new functions may be defined in future releases. DCI formats may have different DCI sizes, or may share the same DCI size.

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

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

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

[0208] 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 toDocket No.: 25-1051 PCTbe monitored per aggregation level; a PDCCH monitoring periodicity and a PDCCH monitoring pattern; one or more DCI formats to be monitored by the UE; and / or whether a search space set is a common search space set or a UE-specific search space set. A set of CCEs in the common search space set may be predefined and known to the UE. A set of CCEs in the UE-specific search space set may be configured based on the UE’s identity (e.g., C-RNTI).

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

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

[0211] 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 andDocket No.: 25-1051 PCTfourteen OFDM symbols and may include two or fewer bits. The UE may use PUCCH format 1 if the transmission is four or more symbols and the number of HARQ-ACK / SR bits is one or two. PUCCH format 2 may occupy one or two OFDM symbols and may include more than two bits. The UE may use PUCCH format 2 if the transmission is over one or two symbols and the number of UCI bits is two or more. PUCCH format 3 may occupy a number between four and fourteen OFDM symbols and may include more than two bits. The UE may use PUCCH format 3 if the transmission is four or more symbols, the number of UCI bits is two or more and PUCCH resource does not include an orthogonal cover code. PUCCH format 4 may occupy a number between four and fourteen OFDM symbols and may include more than two bits. The UE may use PUCCH format 4 if the transmission is four or more symbols, the number of UCI bits is two or more and the PUCCH resource includes an orthogonal cover code.

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

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

[0214] 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 15021Docket No.: 25-1051 PCTand one base station 1504 are illustrated in FIG. 15, but it will be understood that a mobile communication network may include more than one UE and / or more than one base station, with the same or similar configuration as those shown in FIG. 15.

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

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

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

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

[0219] 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 multiplexingDocket No.: 25-1051 PCT(e.g., single-user MIMO or multi-user MIMO), transmit / receive diversity, and / or beamforming. In other examples, the wireless device 1502 and / or the base station 1504 may have a single antenna.

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

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

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

[0223] FIG. 16A illustrates an example structure for uplink transmission A baseband signal representing a physical uplink shared channel may perform one or more functions. The one or more functions may comprise at least one of: scrambling; modulation of scrambled bits to generate complex-valued symbols; mapping of the complex-valued modulation symbols onto one or several transmission layers; transform precoding to generate complex-valued symbols; precoding of the complex-valued symbols; mapping of precoded complex-valued symbols to resource elements; generation of complex-valued time-domain Single Carrier-Frequency Division Multiple Access (SC-FDMA) or CP-OFDM signal for an antenna port; and / or the like. In an example, when transform precoding is enabled, a SC-FDMA signal for uplink transmission may be generated. In an example, when transform precoding is not enabled, a CP-OFDM signal for uplink transmission may be generated by FIG. 16A. These functions are illustrated as examples and it is anticipated that other mechanisms may be implemented in various embodiments

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

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

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

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

[0228] A timer may begin running once it is started and continue running until it is stopped or until it expires A timer may be started if it is not running or restarted if it is running. A timer may be associated with a value (e.g., the timer may be started or restarted from a value or may be started from zero and expire once it reaches the value). The duration of a timer may not be updated until the timer is stopped or expires (e.g., due to BWP switching). A timer may be used to measure a time period / window for a process. When the specification refers to an implementation and procedure related to one or more timers, it will be understood that there are multiple ways to implement the one or more timers. For example, it will be understood that one or more of the multiple ways to implement a timer may be used to measure a time period / window for the procedure. For example, a random access response window timer may be used for measuring a window of time for receiving a random access response. In an example, instead of starting and expiry (or expiration) of a random access response window timer, the time difference between two time stamps may be used. When a timer is restarted, a process for measurement of time window may be restarted. Other example implementations may be provided to restart a measurement of a time window.

[0229] 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 transmitted and / or received by the wireless device.

[0230] In an example, the signal may be a physical signal. For example, a physical signal may not include higher layer information (e.g., user and / or control data). An example of a physical signal is a reference signal. In another example, a signal may be referred to as a channel. For example, a channel may include (or carry) higher layer information (e.g., user and / or control data). A channel may be a data channel and / or a control channel. A channel may be an uplink channel and / or a downlink channel.

[0231] In an example, an uplink channel may also be referred to as an uplink physical channel. In an example, the downlink channel may also be referred to as a downlink physical channel. In an example, a downlink physical channel (or a downlink channel) may be a Physical Downlink Shared Channel (PDSCH), a Physical Downlink Control Channel (PDCCH), a Physical Broadcast Channel (PBCH), etc. In an example, an uplink physical channel (or an uplink channel) maybe a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), a Physical Random Access Channel (PRACH), etc.

[0232] A wireless device may transmit and / or receive a signal (e.g., a reference signal, a channel, etc.) in a cell. The cell may be associated with a base station. The cell may be a serving cell or a non-serving cell of the wireless device. The serving cell may also be referred to as a special cell (SpCell), a primary cell (PCell), a secondary cell (SCell), or a primary secondary cell group (SCG) cell (PSCell). The SpCell may also be referred to as the PCell or the PSCell. The non-serving cell may also be referred to as a neighboring cell ora neighbor cell.Docket No.: 25-1051 PCT

[0233] A PSCell or an SCell may be activated or deactivated. For example, a PCell may activate or deactivate a PSCell and / or an SCell. In another example, a PSCell may activate or deactivate an SCell. For example, a PSCell and / or an SCell may be deactivated for saving power of a wireless device. A PSCell while being activated may also be referred to as an activated PSCell. A PSCell while being deactivated may also be referred to as a deactivated PSCell. An SCell while being activated may also be referred to as an activated SCell. An SCell while being deactivated may also be referred to as a deactivated SCell.

[0234] In an example, a wireless device may receive, from a base station, a message, e.g., an RRC, a MAC-CE, or a DCI command. The message may be associated with an activation (an activation status or state) or a deactivation (or deactivation status or state) of a PSCell and / or and SCell. The wireless device may activate or deactivate the PSCell and / or the SCell based on the message. The wireless device may communicate on a PSCell while the PSCell is activated. The wireless device may not communicate (or may interrupt communications) on a PSCell while the PSCell is deactivated. The wireless device may communicate on an SCell while the SCell is activated. The wireless device may not communicate (or may interrupt communications) on an SCell while the SCell is deactivated.

[0235] A node (e.g., a base station) may configure a wireless device with two or more carrier frequencies (or serving carrier frequencies), e.g., in a multicarrier operation. The multicarrier (MC) operation may also be referred to as a band combination or a band aggregation. The multicarrier (MC) operation may include a carrier aggregation (CA), a dual connectivity (DC), a multi-connectivity (MuC), etc. A CA may include a primary component carrier (PCC) and one or more secondary component carriers (SCC). A PCC may be referred to as a carrier frequency of a PCell. The PCC may be associated with (or may comprise) a PCell and one or more neighbor cells (e.g. non-serving cells). An SCC may be referred to as a carrier frequency of an SCell. The SCC may be associated with (or may comprise) an SCell and one or more neighbor cells.

[0236] A dual connectivity may include two or more cell groups (CGs). A CG may be a master cell group (MCG) or a secondary cell group (SCG). A dual connectivity may include an MCG and a SCG. In an example, the one or more carrier frequencies may belong to, or may be associated with a CG (e.g., a MCG, SCG, etc.). An MCG includes at least one carrier frequency, e.g., a PCC. The MCG may also include one or more SCCs. An SCG includes at least one carrier frequency, e.g., a primary secondary cell group (SCG) component carrier (PSCC) or a primary secondary SCG carrier (PSC). The SCG may also include one or more SCCs. A PSCC may also be referred to as a carrier frequency of a PSCell. The PSCC may be associated with (or may comprise) a PSCell and one or more neighbor cells. For example, the MCG may comprise at least one serving cell (e.g., a PCell). The SCG may also comprise at least one serving cell (e.g., a PSCell).

[0237] FIG. 17 illustrates an example of a measurement 1700, over a measurement time 1702, of one or more samples 1704 per an aspect of the present disclosure.

[0238] In the example of FIG. 17, a wireless device may perform measurement 1700 based on a reference signal (RS). The reference signal (RS) may be an uplink reference signal (UL RS), and / or a downlink reference signal (DLDocket No.: 25-1051 PCTRS). For example, the wireless device may obtain one or more samples 1704 based on the reference signal. For example, the wireless device may obtain each one of the one or more samples 1704 by measuring the reference signal. In an example, the wireless device may obtain one or more samples 1704 periodically, e.g., once every 40 ms, etc.

[0239] In an example, the periodicity of obtaining one or more samples 1704 may correspond to a periodicity of the UL RS (e.g., a periodicity of a sounding reference signal (SRS)), and / or a periodicity of the DL RS (e.g., a periodicity of an synchronization signal (SS)Zphysical broadcast channel (PBCH) block (SSB), a positioning reference signal (PRS), an SS / PBCH Block Measurement Timing Configuration (SMTC) period, a positioning reference signal (PRS) resource periodicity, a PRS resource set periodicity, a channel state indicator-reference signal (CSI-RS) resource periodicity, etc.) A node (e.g., a base station, a location server, a transmission reception point (TRP), etc.) may configure the wireless device with an UL RS and / or a DL RS using a reference signal configuration (e.g., via a radio resource control (RRC) message, an LTE positioning protocol (LPP) message, etc.). The reference signal configuration may comprise one or more parameters, e.g., a reference signal index or identifier, a reference signal duration or occasion or window, a reference signal periodicity, a time offset, etc. The wireless device may transmit the UL RS.

[0240] The node (e.g., a base station) may further configure the wireless device with a discontinuous reception (DRX) cycle via RRC, e.g., to reduce power consumption of the wireless device. For example, the wireless device may transmit the UL RS based on the DRX cycle. In an example, the wireless device may transmit the UL RS once every DRX cycle. In an example, the wireless device may obtain sample 1704 based on the DRX cycle. For example, the wireless device may obtain sample 1704 once every K 11 *Tdrx, where Tdrx is a length of the DRX cycle. In an example, K11=1. In another example, K11 > 1, e.g., K11=4.

[0241] The wireless device may obtain each sample, of the one or more samples 1704 over at least one timefrequency resource comprising the reference signal. For example, the time-frequency resource may comprise a duration of the reference signal and a bandwidth of the reference signal. In an example, the time-frequency resource may comprise one or more resource elements, e.g., one or more subcarriers within a symbol. In an example, the timefrequency resource may comprise one or more resource blocks within a slot. A resource block (RB) may also be referred to as a physical resource block (PRB), a virtual resource block (VRB), a channel, or a time-frequency channel.

[0242] As illustrated in the example of FIG. 17, the wireless device may obtain, determine, estimate, or calculate measurement 1700 over measurement time 1702 based on the obtained one or more samples 1704. Measurement time 1702 may also be referred to as a measurement period, a physical layer (L1) measurement period, a cell identified period, a measurement window, a measurement time window, a physical layer measurement period, a positioning measurement period, an evaluation period, an observation time, a calculation time, or an estimation time. For example, the wireless device may obtain measurement 1700 by combining two or more samples, of the one or more samples 1704, over measurement time 1702.Docket No.: 25-1051 PCT

[0243] In an example, measurement time 1702 may be a requirement. In an example, the requirement may be predefined. In another example, the wireless device may determine the requirement based on one or more parameters (e.g., one or more scaling factors). In an example, the one or more parameters may be pre-defined. In another example, the wireless device may receive from a node (e.g., a base station), the one or more parameters, e.g., via an RRC message. The requirement may also be referred to as (or associated with or part of or belong to) a measurement requirement, a radio resource management (RRM) requirement, a mobility measurement requirement, a positioning measurement requirement. The wireless device may fulfill (or meet) the requirement.

[0244] In an example, the wireless device may combine two or more samples, of the one or more samples 1704, over measurement time 1702 based on a function. The function may also be referred to as an operation or a relation. Examples of the function may be a sum, an average (or a mean), a weighted average, a median, a product, a ratio, an X11thpercentile, ceiling, floor, etc. Examples of X11 are 90thpercentile, 95thpercentile, etc.

[0245] In the example of FIG. 17, in an example, measurement time 1702 may correspond to a duration over which the node may obtain one or more samples 1704. For example, measurement time 1702 may be 200 ms based on five samples, of the one or more samples 1704. Each one of the five samples may be obtained with a periodicity of 40 ms. In another example, measurement time 1702 may further include a processing time, e.g, for combining the samples, of the one or more samples 1704. The processing time may also be referred to as a margin (or an allowance or a compensation), an impairment margin, or an implementation margin. For example, measurement time 1702 maybe 250 ms based on the five samples, of the one or more samples 1704, each having a periodicity of 40 ms and measurement time 1702 comprising the processing time of 50 ms.

[0246] In the example of FIG. 17, the wireless device may perform measurement 1700 over measurement time 1702 with a certain measurement accuracy. An example of the measurement accuracy of measurement 1700 over measurement time 1702 may be ± X12 dB (e.g., ± 3 dB) compared to an ideal signal measurement. Another example of the measurement accuracy of measurement 1700 over measurement time 1702 maybe ± X13 ns (e.g., ± 100 ns) compared to an ideal timing measurement. The measurement accuracy of measurement 1700 may depend on (or impacted by) one or more conditions.

[0247] In an example, a condition may comprise a speed of the wireless device. In an example, a condition may comprise a speed range of the wireless device. In another example, a condition may comprise one or more radio channel characteristics. In an example a radio channel characteristic may comprise a Doppler frequency In an example a radio channel characteristic may comprise a Doppler spectrum or a Doppler spread. In an example a radio channel characteristic may comprise a channel delay spread. In an example a radio channel characteristic may comprise a channel coherence time. The ideal signal measurement, or the ideal timing measurement, may also be referred to as a baseline measurement or a perfect measurement. The ideal signal measurement, or the ideal timing measurement may not include estimation errors, or impairments associated with the wireless device. Examples of theDocket No.: 25-1051 PCTestimation errors, or impairments, are channel estimation errors, computational errors (e.g., when combining two or more samples, of the one or more samples 1704), etc.

[0248] A measurement (e.g., measurement 1700) may be an intra-frequency measurement, an inter-frequency measurement, or an inter-radio access technology (RAT) measurement. 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.

[0249] In an example, the inter-RAT measurement may be associated with one or more cells of an inter-RAT carrier. For example, a serving carrier of a wireless device may be associated with (or belong to) a first RAT. In this example, the inter-RAT carrier may be associated with a second RAT. In an example, the first RAT may be a next generation radio (NR) and the second RAT may be a long term evolution (LTE). In another example, the first RAT may be LTE and the second RAT may be NR. In an example, the inter-RAT carrier may also be referred to as a non-serving carrier frequency of a wireless device. In another example, the inter-RAT carrier may also be referred to as a serving carrier frequency (of the second RAT, e.g., in dual connectivity) of a wireless device.

[0250] A measurement (e.g., measurement 1700) 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, 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, 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.

[0251] A wireless device may maintain a radio link based on the radio link monitoring. The radio link may be between the wireless device and a base station. A wireless device may maintain, recover, or switch a beam. The beam may be a reference signal (e.g., an SSB, a CSI-RS, a PRS, etc.) associated with a direction. The beam may also be referred to as a lobe. In an example, the beam may also be referred to as a receive beam (e.g., a beam received by a wireless device from a certain direction). In another example, the beam may also be referred to as a transmit beam (e.g., a beam transmitted by a base station toward a certain direction). The direction may be based on (or determined by or characterized by) an angle in an azimuth plane and / or an angle in a zenith plane. The azimuth plane may also be referred to as a horizontal plane. The zenith plane may also be referred to as an elevation plane or a vertical plane. The beam may be between the wireless device and a base station.Docket No.: 25-1051 PCT

[0252] The radio link and / or the beam may be related to a cell associated with the base station. The cell may be a serving cell such as a spCell, a PCell, a PSCell, or an SCell. The beam may also be referred to as a beam of a cell, a cell beam, ora serving cell beam, a spCell beam, a PCell beam, a PSCell beam, an SCell beam, etc.

[0253] A measurement associated with the layer 3 mobility procedure may be referred to as a layer 3 measurement. The layer 3 measurement may also be referred to as a layer 3 mobility measurement, a mobility measurement, or a 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. Measurement 1700 (e.g., the RSRP) for layer 3 mobility procedure may be based on N11 number of samples, of one or more samples 1704 and over measurement time 1702. 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.

[0254] 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 L1 radio 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. Measurement 1700 (e.g., the L1-RSRP) for LTM procedure may be based on N12 number of samples, of one or more samples 1704 and over measurement time 1702. 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 ora MAC-CE.

[0255] Examples of the one or more positioning measurements may include a reference signal time difference (RSTD); an UE Rx-Tx time difference measurement; a round trip time (RTT); a multi-RTT; a carrier phase measurement (CPP); a channel impulse response (CIR); a time of arrival (TOA); a reference signal received power (RSRP); a reference signal received path power (RSRPP); a positioning reference signal - reference signal received power (PRS-RSRP); a positioning reference signal - reference signal received path power (PRS-RSRPP); an angle of arrival (AOA); an angle of departure (AOD); a power delay profile (PDP); a delay profile (DP), etc. In an example, the wireless device may transmit to a location server (e.g., a location management function (LMF)), one or more positioning measurements via a positioning protocol (e.g., an LTE positioning protocol (LPP).

[0256] Examples of one or more measurements for an interference management procedure may be a Received Signal Strength Indicator (RSSI), a cross link interference (CLI) - Received Signal Strength Indicator (CLI-RSSI), etc. The interference management procedure may also be referred to as an interference mitigation procedure, an interference reduction procedure, etc.

[0257] The radio link monitoring procedure may include an in-sync (IS) detection and / or an out-of-sync (DOS) detection. The IS and the DOS detection may be based on a measurement (e.g., measurement 1700 in FIG. 17). Measurement 1700 for the radio link monitoring procedure (e.g., the OOS and IS detection) may be a radio link quality (e.g., a signal to noise ratio (SNR), a signal to noise and interference (SINR), an RSRQ, etc.). The radio link qualityDocket No.: 25-1051 PCTmay also be referred to as a channel quality, a link quality, a downlink radio link quality, a downlink quality, etc.Measurement 1700 (e.g., the radio link quality) for the radio link monitoring procedure maybe based on N13 number of samples, of one or more samples 1704 and over measurement time 1702. In an example, N13 maybe 20 for the OOS detection and 10 for the IS detection. Measurement time 1702 for the OOS detection may also be referred to as an evaluation period or an OOS evaluation period. Measurement time 1702 for the IS detection may also be referred to as an evaluation period or an IS evaluation period. A radio link failure (RLF) may be based on one or more OOS detections. For example, a wireless device may start a radio link failure (RLF) timer (e.g., T310) based on detecting one or more OOS detections, e.g., one or more consecutive (or successive) OOS detections. In an example, the wireless device may trigger a radio link failure based on the RLF timer, e.g., upon expiry of the RLF timer. In an example, the wireless device may indicate (or inform) the RLF to a higher layer of the wireless device.

[0258] The link recovery procedure may include a beam failure detection (BFD), a candidate beam detection (CBD), a layer-1 reference signal received power (L1-RSRP), and / or a layer-1 signal to interference and noise ratio (L1-SINR). The BFD, the CBD, the L1-RSRP, and the L-SINR may be based on a measurement (e.g., measurement 1700 in FIG.17). Measurement 1700 for the link recovery procedure (e.g., the BFD detection) may be a radio link quality (e.g., a signal to noise ratio (SNR), a signal to noise and interference (SINR), an RSRQ, etc). The radio link quality may also be referred to as a channel quality, a link quality, etc. Measurement 1700 (e.g., the radio link quality) for the radio link monitoring procedure may be based on N14 number of samples, of one or more samples 1704 and over measurement time 1702. In an example, N14 may be 10 for the BFD detection. Measurement time 1702 for the BFD detection may also be referred to as an evaluation period or a BFD evaluation period. Measurement 1700 for the link recovery procedure (e.g., the CBD detection) may be a signal strength (e.g., an RSRP, a path loss, an L1-RSRP, etc.).

[0259] In an example, a wireless device may estimate a radio link quality (e.g., measurement 1700 (e.g., an SNR, an SINR, a L1-RSRP, etc.)) on a reference signal (e.g., radio link monitoring - reference signal (RLM-RS), a link recovery procedure - reference signal (LRP-RS), etc.) over an evaluation period (e.g., measurement time 1702). The wireless device may compare the radio link quality with one or more thresholds. For example, the wireless device may assess (or determine or monitor or evaluate) a quality of a cell (e.g., a PCell, a PSCell, a spCell, or an SCell) based on comparing the radio link quality with the one or more quality thresholds.

[0260] The radio link failure, the out of synchronization (OOS) detection, the beam failure, the beam failure detection, or the candidate beam detection or may also be referred to as a radio link problem (RLP).

[0261] The wireless device may further receive from a base station, a measurement configuration, e.g., via an RRC signaling, an LPP signaling, etc. The measurement configuration may also be referred to as assistance data or assistance information. The measurement configuration may include one or more measurement objects (MOs), and / or may be referred to as a measurement object (MO). The measurement configuration (or the MO) may include a reference signal configuration (or a configuration of a reference signal). The reference signal configuration may be associated with one or more cells. The one or more cells may belong to (or operate on) a carrier frequency.Docket No.: 25-1051 PCT

[0262] The reference signal configuration may comprise (or include or indicate) one or more parameters associated with (or related to) a reference signal (RS). Examples of the one or more parameters may be a cell identifier (e.g., a physical cell ID (PCI), a cell global ID (CGI), etc.), a type of the reference signal (e.g., an SSB, a CSI-RS, a PRS, etc.), a reference signal index or identifier, a reference signal duration (or an occasion or a window or a measurement window), a reference signal periodicity (or a reference signal occasion periodicity), a time offset, a bandwidth, a numerology (e.g., a subcarrier spacing, a cyclic prefix (CP) length), a time resource (e.g., a symbol, a slot, etc.), etc.

[0263] In an example, the reference signal may be a downlink reference signal, e.g., transmitted by a base station. For example, the reference signal may be transmitted in one or more cells, e.g., in a serving cell and one or more neighbor cells of the wireless device. The one or more cells may be operated, managed, or served by one or more network nodes, e.g., one or more base stations

[0264] Examples of the downlink reference signals 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 Measurement Timing Configuration (SMTC), etc. The SMTC may also be referred to as SSB burst. The SSB may also be referred to as a synchronization signal block (SSB). Each SSB may include a primary synchronization signal (PSS), a secondary synchronization signal (SSS) and a physical broadcast channel (PBCH) within 4 successive symbols.

[0265] The SMTC configuration may be associated with (or comprise) one or more SMTC parameters, e.g. a SMTC index or identifier, a SMTC duration or window, a SMTC periodicity, a SMTC time offset, etc. The SMTC may comprise (or include) one or more SSBs. For example, one or multiple SSBs may be comprised within a SMTC duration. The SMTC occasion may occur with a periodicity (e.g., the SMTC period), e.g., every 5 ms, 10 ms, 20 ms, 40 ms, 80 ms, 160 ms, etc.

[0266] In another example, the reference signal may be an uplink reference signal, e.g., transmitted by the wireless device. Examples of the uplink reference signals may be an SRS, a DMRS, etc. For example, the wireless device may transmit the uplink reference signals (e.g., an SRS) in a serving cell of the wireless device.

[0267] In an example, the wireless device may further receive from a base station, a measurement configuration for one or more measurements (e.g., a cell identification, a RSRP, a RSRQ, a SINR, a global cell ID (CGI), a radio link monitoring, a link recovery procedure, etc.). In another example, the wireless device may further receive, from a location server, a measurement configuration (e.g., an assistance data or an assistance information) for one or more positioning measurements (e.g., a RSTD, a UE Rx-Tx time difference, an AOA, an AOD, a CPP, a PD, a PDP, a CIR, a PRS-RSRP, a PRS-RSRPP, etc.).

[0268] In an example, the measurement configuration may further include information about (or associated with) one or more carrier frequencies. The one or more carrier frequencies are associated with (or related to) the one or more measurements included in the measurement configuration.Docket No.: 25-1051 PCT

[0269] The carrier frequency may also be referred to as a carrier, a frequency, a component carrier (CC), a layer, a frequency layer, frequency channel, positioning frequency layer (PFL), etc. The carrier frequency may belong to a frequency band. The frequency band may include one or multiple carrier frequencies. The number of the carrier frequencies within a frequency band may depend on a passband (e.g., length of the band in frequency domain) and / or a bandwidth of the carrier frequencies and / or a raster (e.g., a point in frequency where a carrier frequency may be centered, etc.). The raster may be referred to as a channel raster, a synchronization raster, etc.

[0270] The information about (or associated with) the one or more carrier frequencies may be indicated by a channel number or an identifier. In example, the channel number or the identifier may be pre-defined. For example, the channel number may be an absolute radio frequency channel number (ARFCN). Examples of the ARFCN may be E-UTRA ARFCN (EARFCN), NR ARFCN (NR-ARFCN), etc.

[0271] For example, a carrier frequency associated with a CSI-RS based measurements (e.g., a CSI-RSRP, a CSI-RSRQ, a CSI-SINR, a CSI-SNR, a radio link quality, a BFD, a CBD, a L1-RSRP, a L1-SINR, etc.) maybe indicated by a CSI-RS ARFCN, e.g., in the measurement configuration.

[0272] For example, a carrier frequency (e.g., ssbFrequency) associated with SSB based measurements (e.g., SS-RSRP, SS-RSRQ, SS-SINR, SS-SINR, a radio link quality, a BFD, a CBD, a L1-RSRP, a L1-SINR, etc.) maybe indicated by an SSB ARFCN, e.g., in the measurement configuration. For example, the SSB ARFCN (e.g., ARFCN-ValueNR) may indicate a frequency location within a bandwidth of an SSB. For example, the SSB may include 20 resource blocks enumerated from a resource block # 0 to a resource block # 19. In an example, the indicated frequency location (e.g., a SSB ARFCN) may correspond to a resource element # 0 within a resource block # 0 of the resource blocks of the SSB.

[0273] FIG. 18 illustrates an example of a measurement gap pattern (MGP) 1800 per an aspect of the present disclosure. In the example of FIG. 18, MGP 1800 includes two or more gaps. A wireless device performs a measurement (e.g., measurement 1700 in FIG. 17) during a gap of (or belonging to) MGP 1800.

[0274] The wireless device may not communicate (e.g., transmit and / or receive) with a base station during the gap. The wireless device may communicate (e.g., transmit and / or receive) with a base station outside the gap. The gap may also be referred to as a measurement gap. A length or duration of the measurement gap may be referred to as a measurement gap length (MGL) 1802. MGL 1802 may also be referred to as a gap length or a gap duration. In an example, MGL 1802 may be 1.5 ms, 3 ms, 3.5 ms, 4 ms, 5.5 ms, 6 ms, 10 ms, 20 ms, 10 ms, 20 ms, or any other reasonable time duration.

[0275] The start timings of any two successive (or consecutive) gaps in MGP 1800 may be separated (in time) by a measurement gap repetition period (MGRP) 1804. MGRP 1804 may also be referred to as a gap periodicity, a gap period, or a measurement gap periodicity. In an example, MGRP 1804 may be 20 ms, 40 ms, 80 ms, 160 ms, 320 ms, 640 ms, 1280 ms, 2480 ms, or any other reasonable time duration. One or more MGPs 1800 (e.g., a set of MGL and / or MGRP) may be pre-defined.Docket No.: 25-1051 PCT

[0276] MGP 1800 may be associated with an identifier. The identifier may also be referred to as a gap ID or a measurement gap pattern ID, e.g., MGP 1800 ID. For example, a wireless device may identify one or more parameters (e.g., MGL 1802, MGRP 1804, etc.) associated with MGP 1800 based on the identifier. Examples of the identifier (e.g., MGP 1800 ID) may be 0, 1, 2, 3, 4, 6, 7, etc. For example, each identifier may correspond to or refer to a set of MGL 1802 and MGRP 1804. For example, MGP 1800 ID # 0 may correspond to MGL 1802 of 6 ms and MGRP 1804 of 40 ms. In another example, MGP 1800 ID # 1 may correspond to MGL 1802 of 6 ms and MGRP 1804 of 80 ms.

[0277] 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, e.g., during MGL 1802. 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, or cancelling the signal.

[0278] In an example, a measurement gap pattern (e.g., MGP 1800) may be associated with a cell group (CG), a frequency range (FR), or a group of carrier frequencies. A wireless device may be configured with one or more carrier frequencies. A CG may be a master cell group (MCG) or a secondary cell group (SCG). A dual connectivity includes an MCG and an SCG. In an example, the one or more carrier frequencies may belong to, or may be associated with a CG (e.g., an MCG, an SCG, etc.). An MCG includes at least one carrier frequency, e.g., a primary component carrier (PCC). An SCG includes at least one carrier frequency, e.g., a primary secondary component carrier (PSCC).

[0279] An FR 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.

[0280] In an example, a measurement gap pattern (e.g., MGP 1800) associated with a CG may be referred to as a per CG measurement gap pattern (per CG MGP) (e.g., a per CG MGP 1800) ora 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 (e.g., MGL 1802) of a per CG MGP 1800.

[0281] In an example, a measurement gap pattern (e.g., MGP 1800) associated with a FR may be referred to as a per FR measurement gap pattern (per FR MGP) (e.g., a per FR MGP 1800) or a per FR gap. For 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 an FR during a measurement gap (e.g., MGL 1802) of a per FR MGP 1800.Docket No.: 25-1051 PCT

[0282] In another example, a measurement gap pattern (e.g., MGP 1800) maybe referred to as a peruser equipment (UE) measurement gap pattern (per UE MGP) (e.g., a per UE MGP 1800) ora per UE gap. For example, a measurement gap pattern (e.g., MGP 1800) not associated with a CG, PR, or a group of carrier frequencies may be referred to as a per UE measurement gap pattern (e.g., a per UE MGP 1800) 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 (e.g., MGL 1802) of per a UE MGP 1800.

[0283] In an example, a wireless device may receive, from a base station, one or more gap configuration parameters associated with (or for setting up) MGP 1800. The one or more gap configuration parameters may also be referred to as one or more measurement gap configuration parameters, one or more measurement configuration parameters, one or more configuration parameters, or one or more measurement gap parameters For example, the wireless device may receive an RRC message that includes the one or more gap configuration parameters.

[0284] In an example, the wireless device may receive the one or more gap configuration parameters in a measurement gap configuration (e.g., MeasGapConfig) via an RRC message. The measurement gap configuration (e.g., MeasGapConfig) may specify the measurement gap configuration and may setup or release measurement gaps (or one or more measurement gap patterns). The measurement gap configuration (e.g., MeasGapConfig) may be comprised in a measurement configuration message (e.g., MeasConfig).

[0285] The gap configuration parameters may include one of MGL 1802 and MGRP 1804 or both of MGL 1802 and MGRP 1804. The gap configuration parameters may alternatively, or further include MGL 1802 ID. The configuration parameters further include a timing advance, an offset, etc., associated with MGP 1800. The timing advance may also be referred to as a measurement gap timing advance. In an example, the timing advance may be 0 ms, 0.25 ms, 0.5 ms, 0.75 ms, 1 ms, etc. The offset may also be referred to as a gap offset, a subframe offset, a time offset, or a measurement gap offset. In an example, the offset may be an integer (e.g., a unitless parameter). In an example, the offset may vary between 0 to 159, e.g., with a resolution of 1.

[0286] The wireless device may set up, configure, or start MGP 1800 based on the one or more configuration parameters. For example, the wireless device may setup (or start or configure) a measurement gap of the MGP 1800 starting from a time resource comprised in a radio frame. A duration (or a length) of the measurement gap may be according to MGL 1802. The time resource may be a symbol, a slot, a subframe, or a frame. For example, the radio frame (e.g., 10 ms in length) may include 10 subframes (e.g., each of 1 ms in length). The time resource may be identified by a time resource number (e.g., a subframe number ranging from 0 to 9). The radio frame may be identified by a radio frame number (e.g., a system frame number (SFN) ranging from 0 to 1023).

[0287] In an example, the wireless device may setup (or start or configure) each measurement gap of the measurement gaps of the MGP 1800 in a time resource within a radio frame based on one or more conditions. For example, the measurement gap may start in a radio frame identified by an SFN satisfying an SFN condition. An example of the SFN condition may be: SFN mod T^FLOOR (gapOffset / 10); and T=MGRP / 10 gapOffset, where theDocket No.: 25-1051 PCTMGRP may be according to MGRP 1804, and gapOffset may be according to the offset (or the gap offset) as described above.

[0288] For example, the measurement gap (e.g., MGL 1802) may start from a time resource (e.g., a subframe) identified by a time resource number (e.g., a subframe number) satisfying a subframe condition. The time resource may also be referred to as a first time resource (or a first subframe) of the measurement gap (e.g., MGL 1802). An example of the subframe condition may be: subframe=gapOffset mod 10, where the gapOffset may be according to the offset (or the gap offset) as described above. In an example, MGRP 1804 and a gap offset may correspond to 40 ms and 0 respectively. In this example, the wireless device may determine SFNs of radio frames corresponding to 4, 8, 12, 16, 20, 24, 28, and so on, and a subframe number corresponding to 0. In this example, the wireless device may setup a measurement gap (e.g., of length MGL 1802 and belonging to MGP 1800) starting from a subframe number #0 in radio frames with SFNs corresponding to 4, 8, 12, 16, 20, 24, 28, and so on.

[0289] FIG. 19 illustrates an example of a reference signal (RS) transmission 1900 per an aspect of the present disclosure. In the example of FIG. 19, RS transmission 1900 may comprise a periodic transmission of a reference signal (RS) 1960.

[0290] As shown in FIG 19, RS 1960 may be associated with a periodicity 1964 and a bandwidth 1962. For example, start timings of any two successive (or consecutive) reference signals in RS 1960 may be separated (in time) by periodicity 1964. For example, a base station may transmit RS 1960 periodically with periodicity 1964 and over bandwidth 1962.

[0291] An active bandwidth part (BWP) 1920 may be associated with a bandwidth 1922. For example, frequencies of active BWP 1920 maybe within a bandwidth 1922. Active BWP 1920 maybe active (or activated) during a time period 1924. Active BWP 1920 maybe associated with a serving cell (e.g., a PCell, a PSCell, or an SCell) of a wireless device. During time period 1924, bandwidth 1962 of RS 1960 may be outside bandwidth 1922 of active BWP 1920. At a time instance, active BWP 1920 may switch (or transform or change) to an active bandwidth part (BWP) 1940. Active BWP 1940 may also be associated with the serving cell (e.g., a PCell, a PSCell, or an SCell) of the wireless device. Active BWP 1940 comprises frequencies within a bandwidth 1942. During time period 1944, bandwidth 1962 of RS 1960 may be within (or inside) bandwidth 1942 of active BWP 1940. Bandwidth 1922 and bandwidth 1942 may be within (or inside) a bandwidth of the serving cell.

[0292] During time period 1924, the wireless device may perform communications in the serving cell over frequencies within bandwidth 1922. During time period 1924, the wireless device may not receive RS 1960 within bandwidth 1922. During time period 1944, the wireless device may perform communications in the serving cell over frequencies within bandwidth 1942. During time period 1944, the wireless device may also receive RS 1960 over bandwidth 1962 and inside bandwidth 1942.

[0293] The wireless device may perform a measurement (e.g., measurement 1700 in FIG. 17) based on RS 1960. Examples of RS 1960 may be an SSB, an SMTC, a CSI-RS, or a PRS (as described above).Docket No.: 25-1051 PCT

[0294] A wireless device may receive from a base station, one or more parameters associated with (or defining) one or more bandwidth parts (BWPs) (e.g., up to 4 BWPs). The one or more bandwidth parts (BWPs) may be associated with a cell, e.g., a PCell, a PSCell, or an SCell. The wireless device may configure (or store information associated with) the one or more BWPs based on the one or more parameters. The one or more parameters may be comprised in an RRC message. Examples of the one or more parameters may be an identifier of a BWP of the one or more BWPs, a bandwidth (e.g., a number of resource blocks), a frequency location, a numerology (e.g., a cyclic prefix, a subcarrier spacing, etc.), a timer, etc.

[0295] The frequency location of a BWP may be indicated by an offset in frequency domain. The offset may be between a reference frequency and a lowest usable subcarrier within a bandwidth of the BWP. In an example, the offset may be expressed (or defined) in terms of number of frequency resources (e.g., PRBs). In an example, the reference frequency may be the lowest subcarrier of a reference frequency resource. An example, the reference frequency resource may be a common resource block # 0 of a carrier frequency. The reference frequency may also be referred to as Point A.

[0296] One of the one or more BWPs may be active ata time (e.g., active BWP 1920 or active BWP 1940). In an example, the wireless device may receive from a base station, a message, e.g., via an RRC, a MAC-CE, or a DCI command. For example, the wireless device may switch between BWPs (e.g., from active BWP 1920 to active BWP 1940 or vice versa) based on the message. For example, the message may trigger the wireless device to switch between the BWPs. In an example, the wireless device may receive the message before time instance 1926. In another example, the wireless device may switch between BWPs (e.g., from active BWP 1920 to active BWP 1940 or vice versa) based on a timer, e.g., upon expiration of the timer (e.g., bwp-lnactivity Timer). For example, the timer may expire before time instance 1926. A switch between BWPs may also be referred to as an active bandwidth part switching.

[0297] FIG. 20 illustrates an example of a pre-configured measurement gap pattern (P-MGP) 2000 as per an aspect of an embodiment of the present disclosure.

[0298] In the example of FIG. 20, P-MGP 2000 includes two or more gaps. The length (or duration) of a gap of the two or more gaps may be referred to as a measurement gap length (MGL) 2002. The start timings of any two successive gaps in P-MGP 2000 may be separated (in time) by a measurement gap repetition period (MGRP) 2004. MGL 2002 and MGRP 2004 maybe implemented according to the example embodiments in FIG. 18 (e.g., MGL 1802 and MGRP 1804).

[0299] Ata time instance 2022, a triggering condition 2020 may occur. In response to triggering condition 2020, a wireless device may deactivate one or more gaps, of the two or more gaps, during a time period 2026. For example, one or more deactivated gaps 2024 may be within time period 2026.

[0300] During each deactivated gap, of the one or more deactivated gaps 2024, the wireless device may communicate in a cell (e.g., a serving cell, a PCell, a PSCell, an SCell, etc.). For example, during each activated gap, ofDocket No.: 25-1051 PCTthe one or more deactivated gaps 2044, the wireless device may not interrupt communication in the cell. For example, during each deactivated gap, of the one or more deactivated gaps 2024, the wireless device may transmit signals (e.g., a PUSCH, a PUCCH, a PRACH, etc.) in the cell and / or may receive signals (e.g., a PDCCH, a PDSCH, etc.) in the cell. For example, during each deactivated gap, of the one or more deactivated gaps 2044, the wireless device may also perform a measurement (e.g., measurement 1700 in FIG. 17). The measurement may also be referred to as a measurement without (or outside) a gap (or without a measurement gap). For example, during each deactivated gap, of the one or more deactivated gaps 2024, the wireless device may perform the measurement without the gap.

[0301] In an example, a wireless device may receive a first message. For example, triggering condition 2020 may be based on the first message, e.g., a DCI, a MAC-CE, or an RRC message. In an example, the first message may switch (or indicate or be related to a switching of) a BWP (e.g , from active BWP 1920 to active BWP 1940 in FIG. 19). In an example, the first message may activate or deactivate (or indicate or be related to an activation or a deactivation of) a cell (e.g., an SCell). In yet example, the first message may add or remove a measurement object (or indicate or be related to an addition or a removal of) a measurement object. In yet another example, the first message may add, release, or change (or indicate or be related to an addition, a release or a change of) a cell (e.g., an SCell). The cell may be associated with a multicarrier operation (e.g., a carrier aggregation, a dual connectivity, etc.).

[0302] In another example, triggering condition 2020 may be based on (or associated with) a first pre-defined rule. For example, the wireless device may switch a BWP (e.g., from active BWP 1920 to active BWP 1940 in FIG. 19) based on the pre-defined rule (e.g., upon an expiration of a timer, e.g., bwp-lnactivityTimer).

[0303] Ata time instance 2042, a triggering condition 2040 may occur. In response to triggering condition 2040, a wireless device may activate one or more gaps, of the two or more gaps, during a time period 2046. For example, one or more deactivated gaps 2044 may be within time period 2046.

[0304] During each activated gap, of the one or more deactivated gaps 2044, the wireless device may not communicate in a cell (e.g., a serving cell, a PCell, a PSCell, an SCell, etc.). For example, during each activated gap, of the one or more deactivated gaps 2044, the wireless device may interrupt communications in the cell. In an example, during each activated gap, of the one or more activated gaps 2044, the wireless device may not transmit signals in the cell and / or may not receive signals in the cell. In another example, during each activated gap, of the one or more activated gaps 2044, the wireless device may perform a measurement (e.g., measurement 1700 in FIG. 17). The measurement may also be referred to as a measurement with (or inside) a gap (or with a measurement gap). For example, during each activated gap, of the one or more activated gaps 2044, the wireless device may perform the measurement with the gap.

[0305] In an example, a wireless device may receive a second message. For example, triggering condition 2040 may be based on the second message, e.g., a DCI, a MAC-CE, or an RRC message. In an example, the second message may switch (or indicate or be related to a switching of) a BWP (e.g., from active BWP 1920 to active BWP 1940 in FIG.19). In an example, the second message may activate or deactivate (or indicate or be related to an activation or aDocket No.: 25-1051 PCTdeactivation of) a cell (e.g , an SCell). In yet example, the second message may add or remove a measurement object (or indicate or be related to an addition or a removal of) a measurement object. In yet another example, the second message may add, release, or change (or indicate or be related to an addition, a release or a change of) a cell (e.g., an SCell). The cell may be associated with a multicarrier operation (e.g., a carrier aggregation, a dual connectivity, etc.).

[0306] In another example, triggering condition 2040 may be based on (or associated with) a second pre-defined rule. For example, the wireless device may switch a BWP (e.g., from active BWP 1920 to active BWP 1940 in FIG. 19) based on the second pre-defined rule (e.g., upon an expiration of a timer, e.g., bwp-lnactivityTimer).

[0307] In an example, a wireless device may receive, from a base station, one or more gap configuration parameters associated with (or for setting up or starting) P-MGP 2000. The one or more gap configuration parameters may be according to the example embodiments in FIG. 19 (e.g., the one or more gap configuration parameters). The wireless device may set up, configure, or start P-MGP 2000 based on the one or more gap configuration parameters according to the example embodiments in FIG. 19. P-MGP 2000 may also be referred to as a pre-configured measurement gap (e.g., Pre-MG).

[0308] FIG. 21 illustrates an example of a network controlled small gap (NCSG) pattern 2100 as per an aspect of an embodiment of the present disclosure

[0309] In the example of FIG. 21, NCSG pattern 2100 includes two or more time periods 2120. Each time period, of the two or more time periods 2120, includes a visible interruption length (VIL) 2122, a measurement length (ML) 2124, and a VIL 2126. For example, each time period, of the two or more time periods 2120, maybe a sum of VIL 2122, ML 2124, and VIL 2126. In an example, VIL 2122, ML 2124, and / or VIL 2126 may depend on a numerology (e.g., a subcarrier spacing, a CP length, a slot length, a symbol length, etc.). In an example, VIL 2122, ML 2124, and / or VIL 2126 may depend on a frequency range (e.g., FR1, FR2, etc.).

[0310] In an example, ML 2124 may be 1 ms, 2 ms, 3 ms, 4 ms, 5 ms, or any other reasonable time duration. In an example, VIL 2122 or VIL 2126 may be expressed (or defined) in terms of a number of time resources (e.g., X11 symbols, X12 slots, X12 subframes, etc.). For example, VIL 2122 or VIL 2126 maybe 1 slot, 2 slots, 3 slots, 4 slots, 8 slots, or any other reasonable time duration. In another example, VIL 2122 or VIL 2126 may be expressed in terms of time units (e.g., X13 ms). For example, VIL 2122 or VIL 2126 maybe 0.25 ms, 0.5 ms, 1 ms, 2 ms, or any other reasonable time duration.

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

[0312] NCSG pattern 2100 may be associated with an identifier. The identifier may also be referred to as an NCSG ID, e.g , an ID of NCSG pattern 2100. For example, a wireless device may identify one or more parameters (e.g , VIL 2122, ML 2124, VIL 2126, and / or VIRP 2140) associated with NCSG pattern 2100 based on the identifier. Examples ofDocket No.: 25-1051 PCTthe identifier (e.g., the ID of NCSG pattern 2100) may be 0, 1, 2, 3, 4, 6, 7, etc. For example, each identifier may correspond to or refer to a setof VIL 2122, ML 2124, VIL 2126, and VI RP 2140. For example, ID # 0 of NCSG pattern 2100 may correspond to ML 2124 of 5 ms and VI RP 2140 of 40 ms. In another example, ID # 1 of NCSG pattern 2100 may correspond to ML 2124 of 5 ms and VI RP 2140 of 80 ms.

[0313] A wireless device may communicate in a cell (e.g., a PCell, a PSCell, an activated SCell, etc.) during ML 2124. For example, during ML 2124, the wireless device may not interruption communications in the cell. For example, during ML 2124, the wireless device may transmit signals in the cell and / or may receive signals in the cell. The wireless device may also perform a measurement (e.g., measurement 1700 in FIG. 17) during ML 2124. The measurement may also be referred to as a measurement without (or outside) a gap (or without a measurement gap).

[0314] The wireless device may interrupt communications during a gap. The gap may also be referred to as a small gap, a visible gap, a known gap, an interruption duration, a visible interruption duration, ora 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 2122 or VIL 2126. For example, during VIL 2122 and VIL 2126, 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.

[0315] For example, during VIL 2122, the wireless device may extend (or expand or enlarge) the bandwidth of the wireless device. In another example, during VIL 2122, the wireless device may change the frequency location of the oscillator of the wireless device. For example, during VIL 2126, the wireless device may reduce (or shorten) the bandwidth of the wireless device. In another example, during VIL 2126, the wireless device may change the frequency location of the oscillator of the wireless device.

[0316] In an example, an NCSG pattern (e.g., NCSG pattern 2100) may be associated with a cell group (CG), a frequency range (FR), ora group of carrier frequencies. In an example, an NCSG pattern (e.g., NCSG pattern 2100) associated with a CG may be referred to as a per-CG NCSG pattern or a per-CG NCSG. 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 VIL 2122 and VIL 2126 of a per-CG NCSG pattern.

[0317] In an example, an NCSG pattern (e.g., NCSG pattern 2100) associated with a FR may be referred to as a per FR NCSG pattern or a per FR NCSG. For 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 an FR during a VIL 2122 and VIL 2126 of a per FR NCSG pattern.

[0318] In another example, an NCSG pattern (e.g., NCSG pattern 2100) may be referred to as a per user equipment (UE) NCSG pattern ora per UE NCSG. For example, an NCSG pattern (e.g, NCSG pattern 2100) not associated with a CG, FR, or a group of carrier frequencies may be referred to as a per UE NCSG pattern or a per UE NCSG. In anDocket No.: 25-1051 PCTexample, 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 during VIL 2122 and VIL 2126 of per a UE NCSG pattern.

[0319] In an example, a wireless device may receive, from a base station, one or more configuration parameters associated with (or for setting up or start) NCSG pattern 2100. The one or more configuration parameters may also be referred to as one or more NCSG configuration parameters, one or more measurement configuration parameters, or one or more configuration parameters, or one or more gap configuration parameters. For example, the wireless device may receive an RRC message that includes the one or more configuration parameters.

[0320] The wireless device may set up, configure, or start NCSG pattern 2100 based on the one or more configuration parameters. For example, the wireless device may setup (or start or configure) NCSG pattern 2100. For example, NCSG pattern 2100 may start from a time resource comprised in a radio frame. The time resource may be, e.g., a slot number, a subframe number, etc. The radio frame may be identified by a radio frame number (e.g., a system frame number (SFN) ranging from 0 to 1023). In an example, the wireless device may setup (or start or configure) each time period, of the two or more time periods 2120, of the NCSG pattern 2100 in a time resource within a radio frame. The time resource and the radio frame may be based on one or more conditions. The one or more conditions may be implemented according to the example embodiments in FIG. 18 (eg., the one or more conditions for MGP 1800).

[0321] FIG. 22 illustrates an example of an on-demand reference signal (OD-RS) 2200 transmission as per an aspect of an embodiment of the present disclosure.

[0322] OD-RS 2200 may be associated with a cell (e.g., a PCell, a PSCell, an SCell, a neighbor cell, etc.). For example, the cell may transmit OD-RS 2200. As illustrated in FIG. 22, OD-RS 2200 may be associated with (or defined by) a bandwidth 2202, a periodicity 2242, and a periodicity 2262.

[0323] During a time period 2220, the cell may not transmit OD-RS 2200. For example, OD-RS 2200 may be deactivated (or inactive or in a deactivated state) during time period 2220. In another example, during time period 2220, a status (or a state or an activation status or an activation state) of OD-RS 2200 may also be referred to as (or set to or regarded as) deactivated.

[0324] Ata time instance 2204, the cell may initiate (or trigger or start or commence) transmission of OD-RS 2200. During a time period 2240, the cell may transmit OD-RS 2200. During time period 2240, OD-RS 2200 may be associated with periodicity 2242. For example, during time period 2240, the cell may transmit OD-RS 2200 based on periodicity 2242. Starting from a time instance 2206 and during time period 2260, OD-RS 2200 may be associated with periodicity 2260. In an example, at time instance 2206, a periodicity of OD-RS 2200 may change from periodicity 2242 to periodicity 2262. For example, during time period 2260, the cell may transmit OD-RS 2200 based on periodicity 2262.

[0325] In an example, periodicity 2242 may be longer than periodicity 2262. For example, OD-RS 2200 may be activated (or active or in an activated state) during time period 2240 and time period 2260. In another example, during time period 2240 and time period 2260, a status (or a state or an activation status or an activation state) of OD-RSDocket No.: 25-1051 PCT2200 may also be referred to as (or set to or regarded as) activated. Periodicity 2242 and periodicity 2262 may be 5 ms, 10 ms, 20 ms, 40 ms, 80 ms, 160ms, or any other reasonable time duration.

[0326] In an example, a wireless device may receive from a node, one or more parameters (e.g., via an RRC message) associated with (or defining) OD-RS 2200. Examples of the one or more parameters may indicate (or comprise) bandwidth 2202, periodicity 2242, periodicity 2262, a time offset, a frequency (e.g., an ARFCN of an SSB), a transmission duration of OD-RS 2200, a transmit power, an index of OD-RS 2200 (e.g., a time location in burst), etc. The wireless device may store the one or more parameters. For example, the wireless device may pre-configure OD-RS 2200 based on the one or more parameters. In an example, the one or more parameters may not indicate the status of OD-RS 2200. In another example, OD-RS 2200 may be associated with a default activation status. For example, based on a reception of the one or more parameters, the wireless device may assume that OD-RS 2200 is deactivated.

[0327] In an example, the wireless device may determine the activation status of OD-RS 2200 based on an indication. For example, the wireless device may receive from a node, the indication (e.g., an RRC message, a MAC-CE, ora DCI command). In an example, the indication maybe initiated by the node. In another example, the indication may be in response to (or based on) a request from the wireless device. The request may be an RRC message, a MAC-CE, or a DCI command. For example, the wireless device may transmit to the node, the request for activating or deactivating OD-RS 2200. The indication and the request may be

[0328] The indication may indicate the activation status of the OD-RS 2200 in the cell. For example, the node may transmit the indication at a time instance, T11. For example, the wireless device may receive the indication at a time instance T12, where, e.g., T12 a T11. For example, the cell may change the activation status of OD-RS 2200 (e.g., activate or deactivate OD-RS 2200) at a time instance T13, where, e.g., T13 & T11. The wireless device may determine based on the indication, the activation status of the OD-RS 2200 not later than ata time instance, T14, where, e.g., T14 > T13.

[0329] In another example, the wireless device may determine the activation status of OD-RS 2200 based on a predefined rule. For example, the wireless device may determine the activation status of OD-RS 2200 based on one or more time periods. For example, during a first time duration (T15), OD-RS 2200 may be activated, e.g., the activation status of OD-RS 2200 may be activated. In another example, during a second time duration (T16), OD-RS 2200 may be deactivated, e.g., the activation status of OD-RS 2200 may be deactivated. In an example, the node may indicate to the wireless device, the first time duration and / or the second time duration. In another example, the first time duration and / or the second time duration may be pre-defined. For example, during the second time duration, the cell may be in a discontinuous transmission (DTX) mode (e.g., a cell DTX mode). In another example, during the first time duration, the cell may not be in the DTX mode. In the DTX node, the cell may not transmit signals.

[0330] In an example, OD-RS 2200 may be a cell defining on-demand RS (CD-OD-RS) (e.g., a CD-OD-SSB). In another example, OD-RS 2200 may be a non-cell defining on-demand RS (NCD-OD-RS) (e.g., an NCD-OD-SSB). ADocket No.: 25-1051 PCTcell defining SSB (CD-SSB) may be associated with a remaining minimum system information (RMSI). A non-cell defining SSB (NCD-SSB) may not be associated with an RMSI. For example, a system information block 1 (e.g., SIB1) may also be referred to as the RMSI.

[0331] In an example, OD-RS 2200 may be associated with a raster (e.g., a synchronization raster). For example, frequencies of OD-RS 2200 may be located at the synchronization raster in a frequency domain. In yet another example, OD-RS 2200 may not be associated with the raster (e.g., the synchronization raster). For example, frequencies of OD-RS 2200 may not be located at the synchronization raster in a frequency domain.

[0332] OD-RS 2200 may also be referred to as a temporary reference signal, an on-demand SSB (OD-SSB), a temporary SSB, an on-demand CSI-RS (OD-CSI-RS), an on-demand SMTC, an on-demand positioning reference signal (OD-PRS), etc The reference signal may be implemented according to the example embodiments described above (e.g., the reference signal, the downlink reference signal (DL RS), the SSB, the SMTC, the CSI-RS, and the PRS).

[0333] In an example, a wireless device may perform a measurement (e.g., measurement 1700 in FIG. 17) on a reference signal (RS) during one or more measurement gaps in (or of) a measurement gap pattern. The RS may be according to the example embodiments described in FIG 17 (e.g., the reference signal) and / or in FIG.22 (e.g., OD-RS 2200). The measurement gap pattern may be implemented according to the example embodiments in FIG. 18 (e.g., MGP 1800), in FIG. 20 (e.g., P-MGP 2000), and / or in FIG. 21 (e.g., NCSG pattern 2100).

[0334] FIG. 23 illustrates an example of NR frequency ranges 2300, comprising Frequency Range 1 (FR1) 2320 and Frequency Range 2 (FR2) 2340, per an aspect of the present disclosure.

[0335] In the example of FIG. 23, the frequencies within FR12320 are lower than frequencies within FR22340. FR1 2320 may be referred to as a low band or a mid-band frequency range. FR22340 may be referred to as a millimeter wave frequency range or simply a millimeter frequency range.

[0336] In the example of FIG. 23, FR12320 includes frequencies from a frequency 2302 (e.g., 410 MHz) up to a frequency 2304 (e.g., 7125 MHz). Frequency 2302 may be referred to as a starting frequency of FR12320, and frequency 2304 may be referred to as an ending frequency of FR12320.

[0337] In the example of FIG. 23, FR22340 includes frequency from a frequency 2306 (e.g., 24.25 GHz) up to a frequency 2308 (e.g., 71 GHz). Frequency 2306 may be referred to as a starting frequency of FR22340, and frequency 2308 may be referred to as an ending frequency of FR22308.

[0338] In an example, FR22340 may further comprise sub-FR2 frequency ranges. For example, FR22340 may comprise an FR2-12310 and an FR2-22312. The frequencies within FR2-12310 are lower than frequencies within FR2-22312. In an example, FR2-12310 includes frequencies from frequency 2306 (e.g., 24.25 GHz) up to a frequency 2314 (e.g., 52.6 GHz). In an example, FR2-22312 includes frequencies from frequency 2314 (e.g., 52.6 GHz) upto frequency 2308 (e.g., 71 GHz).Docket No.: 25-1051 PCT

[0339] Although FIG.23 illustrates an example in which NR frequency ranges 2300 comprises FR12320 and FR2 2340, the present disclosure is not particularly limited to this example. For example, there may be other frequencies between FR12320 and FR22340. In an example, one or more frequencies between FR12320 and FR22340 may belong to another frequency range, such as Frequency Range 3 (FR3). In another example, FR22340 may be extended to include one or more frequencies between FR12320 and FR22340.

[0340] FIGs. 24A and 24B illustrate examples of FR1 bands 2420 and FR2 bands 2440 per an aspect of the present disclosure. FR1 bands 2420 belong to, or are within, FR12320, e.g., in FIG.23. FR1 bands 2440 belong to, or are within, FR22340, e.g., in FIG. 23.

[0341] In the example of FIG. 24A, FR1 bands 2420 may be identified by their respective identifiers e.g., n1, n2, n3, and so on. The identifier (e.g., n1 , n2, etc.) may also be referred to as a band indicator, a band identifier, a band number, etc. A band may also be referred to as a frequency band, an operating band, an operating frequency band, a transmission band, etc. A wireless device may receive, from a base station, an identifier of a band, e.g., via an RRC signaling message. A node (e.g., a base station, a gNB, a gNB-DU, a gNB-CU, a TRP, etc.) may transmit, to another node (e.g., a base station, a gNB, a gNB-DU, a gNB-CU, a TRP, a location server, a core network node, etc.), an identifier of a band, e.g., via an XnAP, an F1AP, an NGAP, or an NRPPa signaling message.

[0342] As discussed above, FR1 bands 2420 belong to or are within the FR12320 (e.g., in FIG. 23). A wireless device may communicate (e.g., transmit and / or receive signals) with a base station on a carrier frequency within FR1 2320 belonging to one or more FR1 bands 2420. A wireless device may further perform a measurement on one or more cells of a carrier frequency. The carrier frequency may be within FR12320. For example, the carrier frequency may belong to one or more FR1 bands 2420. A wireless device may perform a measurement on a signal (e.g., UL RS, DL RS, etc.,). The wireless device may receive and / or transmit the signal in a cell of a carrier frequency within FR1 2320 (e.g., in FIG. 23). For example, the carrier frequency may belong to one or more FR1 bands 2420.

[0343] In the example of FIG. 24A, a band in FR1 bands 2420 may be a frequency division duplex (FDD) band, a half-duplex FDD (HD-FDD) band, a supplemental downlink (SDL) band, a time division duplex (TDD) band, or a supplemental uplink (SUL) band. The FDD band may also be referred to as a full duplex FDD (FD-FDD) band.

[0344] At different times in a TDD operation, a wireless device may transmit an uplink (UL) signal and receive a downlink (DL) signal on the same carrier frequency. At different times in a TDD operation, a base station may transmit a DL signal and receive an UL signal on the same carrier frequency.

[0345] In an FDD (or FD-FDD) operation, a wireless device may simultaneously (e.g., at the same time) transmit an UL signal on an uplink carrier frequency and receive a downlink signal on a downlink carrier frequency. In an FDD (or FD-FDD) operation, a base station may simultaneously (e.g., at the same time) transmit a DL signal on a DL carrier frequency and receive an UL signal on an UL carrier frequency.Docket No.: 25-1051 PCT

[0346] At different times in an HD-FDD operation, a wireless device may transmit an UL signal on an uplink carrier frequency and receive a downlink signal on a downlink carrier frequency. At different times in an HD-FDD operation, a base station may transmit a DL signal on a DL carrier frequency and receive an UL signal on an UL carrier frequency.

[0347] In a multicarrier operation, a wireless device may use an SDL band (and / or an SUL band) with an FDD-FDD, a HD-FDD, or a TDD band. Examples of the multicarrier (MC) operation may be carrier aggregation (CA), multiconnectivity (MuC), dual connectivity (DC), etc.

[0348] In the example of FIG. 24B, similar to FR1 bands 2420, FR2 bands 2440 may also be identified by their respective identifiers, e.g., n257, n258, n259, and so on. A wireless device may communicate (e.g., transmit, and / or receive signals) with a base station on a carrier frequency within FR22340 (e.g., in FIG.23) belonging to one or more FR2 bands 2440. A wireless device may further perform a measurement on one or more cells of a carrier frequency within FR22340 (e.g., in FIG. 23) belonging to one or more FR2 bands 2440. A node may further perform a measurement on a signal (e.g., an UL RS, a DL RS, etc.) transmitted in a cell of a carrier frequency within FR22340 (e.g., in FIG. 23) belonging to one or more FR2 bands 2440.

[0349] In the example of FIG. 24B, FR2 bands 2440 are TDD bands. In an example, an FR2 band, of FR2 bands 2440, may also be an FDD (or FD-FDD) band, a HD-FDD band, an SDL band, or an SUL band As discussed above, FR2 bands 2440 belong to, or are within the FR22340 (e.g., in FIG. 23). In the example of FIG.24B, bands with identifiers from n257 to n262 in FR2 bands 2440 belong to, or are within the FR2-12310 (e.g., in FIG. 23). In the example of FIG.24B, band n263 in the FR2 bands 2440 belongs to, or is within, the FR2-22312 (e.g., in FIG. 23).

[0350] FIG. 25 illustrates an example of a procedure for a capability transfer 2500 per an aspect of the present disclosure. The procedure for capability transfer 2500 may also be referred to as a signaling flow. Capability transfer 2500 is performed between a wireless device 2520 and a node 2540. Capability transfer 2500 may also be referred to as a user equipment (UE) capability transfer.

[0351] Wireless device 2520 may communicate with node 2540. The communication between wireless device 2520 and node 2540 may be based on one or more messages. Before such communication between wireless device 2520 and node 2540, node 2540 may configure or request wireless device 2520 to transmit a capability. The capability may include or may be associated with a measurement gap pattern (MGR). For example, node 2540 may transmit one, or more RRC messages including one, or more configuration parameters for wireless device 2520 to transmit a capability associated with one or more MGPs. In another example, the capability may include or may be associated with one or more bands (e.g., one or more FR1 bands 2420 in FIG. 24A and / or one or more FR2 bands 2440 in FIG.24B).

[0352] In another example, node 2540 may transmit to wireless device 2520, a capability inquiry 2502 (e.g., UECapabilityEnquiry). Capability inquiry 2502 may be an RRC message. Capability inquiry 2502 may also be referred to as a capability request message, an inquiry message, or a radio access capability inquiry. Capability inquiry 2502 may indicate a request for wireless device 2520 to transmit to node 2540, the capability of wireless device 2520 associated with one or more MGPs. Wireless device 2520 may transmit to node 2540, capability information 2504 (e.g.,Docket No.: 25-1051 PCTUECapabilitylnformation) including (or indicating) the one or more MGPs, in response to, or based on capability inquiry 2502 (e.g., UECapabilityEnquiry).

[0353] In another example, capability inquiry 2502 may indicate a request for wireless device 2520 to transmit to node 2540, the capability of wireless device 2520 associated with one or more bands. Wireless device 2520 may transmit to node 2540, capability information 2504 (e.g., UECapabilitylnformation) including (or indicating) the one or more bands, in response to, or based on capability inquiry 2502 (e.g., UECapabilityEnquiry).

[0354] The one or more MGPs maybe implemented according to the example embodiments in FIG. 18 (e.g., MGP 1800), in FIG.20 (e.g., P-MGP2000), and / or in FIG.21 (e.g., NCSG pattern 2100). The one or more bands maybe implemented according to the example embodiments in FIG. 24A (e.g., FR1 bands 2420) and / or in FIG. 24B (e.g., FR2 bands).

[0355] FIG. 26 illustrates an example of a procedure for assistance information transfer 2600 between a wireless device 2620 and a node 2640 per an aspect of the present disclosure. The procedure for assistance information transfer 2600 may also be referred to as a signaling flow. The procedure for assistance information transfer 2600 may also be referred to as a UE assistance information procedure.

[0356] Wireless device 2620 may communicate with node 2640. The communication between wireless device 2620 and node 2640 may be based on one or more messages. Before such communication between wireless device 2620 and node 2640, node 2640 may configure or request wireless device 2620 to transmit assistance information. The assistance information may include or may be associated with a measurement gap pattern (MGP), overheating, a multiFix operation, delay budget report, etc. For example, node 2640 may transmit one, or more RRC messages including one, or more configuration parameters for wireless device 2620 to transmit assistance information associated with one or more MGPs, overheating, a multi-Rx operation, delay budget report, etc.

[0357] In another example, node 2640 may transmit to wireless device 2620, RRC reconfiguration 2602 (e.g., RRC reconfiguration). RRC reconfiguration 2602 (e.g., RRC reconfiguration) may be an RRC message. RRC reconfiguration 2602 (e.g., RRC reconfiguration) may also be referred to as an assistance information request message or a UE assistance information (UAI) request message. RRC reconfiguration 2602 (e.g., RRC reconfiguration) may indicate a request for wireless device 2620 to transmit to node 2640, the assistance information of wireless device 2620 associated with one or more MGPs. RRC reconfiguration 2602 (e.g., RRC reconfiguration) may comprise (or include) one or more other configurations (eg., otherConfig).

[0358] For example, the one or more other configurations (e.g., otherConfig) may comprise (or include) a request for the assistance information (e.g., overheatingAssistanceConfig, idc-AssistanceConfig, delayBudgetReportingConfig, etc.). The request for the assistance information may further comprise (or include) a timer (e.g., T345, T346a, T346b, T346c, T346d, etc.) associated with the assistance information. The timer (e.g., T345) may also be referred to as a prohibit timer. Wireless device 2620 may start the timer (e.g., T345, T346a, T346b, T346c, T346d, etc.) based on (or in response to) the request for the assistance information.Docket No.: 25-1051 PCT

[0359] Wireless device 2620 may transmit to node 2640, assistance information 2604 (e.g., UE assistance information), in response to, or based on the one or more other configurations (e.g., otherConfig) comprised in RRC reconfiguration 2602 (e.g., RRC reconfiguration). In an example, wireless device 2620 may transmit assistance information 2604 upon expiration of the timer (e.g., T345). In another example, wireless device 2620 may transmit assistance information 2604 based on assistance information 2604 being changed compared to previous assistance information 2604. In yet another example, wireless device 2620 may transmit assistance information 2604 based on assistance information 2604 being changed compared to previous assistance information 2604, and the timer (e.g., T345m T345, T346a, T346b, T346c, T346d, etc.) being expired.

[0360] The one or more MGPs may be implemented according to the example embodiments in FIG. 18 (e.g., MGP 1800), in FIG.20 (e.g., P-MGP 2000), and / or in FIG.21 (e.g., NCSG pattern 2100).

[0361] FIG. 27 illustrates an example of a band combination 2700 of a band 2720 and a band 2780 per an aspect of the present disclosure. Band combination 2700 may also be referred to as a multicarrier (MC) operation (e.g., a carrier aggregation).

[0362] The multicarrier (MC) operation may be implemented according to the example embodiments described above (eg., the MC operation). For example, band 2720 may be associated with a serving cell (e.g., a PCell, a PSCell, an SCell, etc.) of a wireless device. In an example, band 2720 may be associated with another (e.g., a second) serving cell (e.g., a PCell, a PSCell, an SCell, etc.) of the wireless device. Band 2720 and band 2780 may be implemented according to the example embodiments in FIG.24A (e.g., FR1 bands 2420) and / or in FIG.24B (e.g., FR2 bands 2440).

[0363] In an example of FIG.27, band 2720 may comprise an uplink (UL) band 2730 and a downlink (DL) band 2740. UL band 2730 may also be referred to as an UL portion (or part or section or segment) of band 2720 in a frequency domain. DL band 2740 may also be referred to as a DL portion (or part or section or segment) of band 2720 in a frequency domain. UL band 2730 may include UL frequencies from a frequency 2732 up to a frequency 2734. DL band 2740 may include DL frequencies from a frequency 2742 up to a frequency 2744. A wireless device may transmit a signal on (or via or over) an UL frequency within UL band 2730. A wireless device may receive a signal on (or via or over) a DL frequency within DL band 2740. In an example, band 2720 may be an FDD band or a HD-FDD band.

[0364] In an example of FIG.27, Band 2780 may comprise an uplink (UL) band 2750 and a downlink (DL) band 2760. UL band 2750 may also be referred to as an UL portion (or part or section or segment) of band 2780 in a frequency domain. DL band 2760 may also be referred to as a DL portion (or part or section or segment) of band 2780 in a frequency domain. UL band 2750 may include UL frequencies from a frequency 2752 up to a frequency 2754. DL band 2760 may include DL frequencies from a frequency 2762 up to a frequency 2764. A wireless device may transmit a signal on (or via or over) an UL frequency within UL band 2750. A wireless device may receive a signal on (or via or over) a DL frequency within DL band 2760. In an example, band 2780 may be an FDD band or a HD-FDD band. The FDD band and the HD-FDD band may be implemented according to the example embodiments in FIG 24A (e.g., the FDD band and the HD-FDD band).Docket No.: 25-1051 PCT

[0365] In an example of FIG.27, Band 2720 and band 2780 may be within a bandwidth 2790. Bandwidth 2790 may include frequencies (e.g., UL frequencies and / or DL frequencies) from a frequency 2792 up to a frequency 2794. Bandwidth 2790 may be expressed (or defined) in terms of one or more frequency resources (e.g., X11 resource blocks). In another example, bandwidth 2790 may be expressed (or defined) in terms of one or more frequency units (e.g., X12 MHz).

[0366] In an example, a wireless device may be associated with an antenna. The antenna may also be referred to as a transmit (Tx) antenna, a receive (Rx) antenna, or a transmit-receive (TX-RX or TX / RX) antenna. The antenna may also be referred to as an antenna port, an antenna array (or an array of antenna elements), an antenna element, a radiating element, etc. In an example, bandwidth 2790 maybe associated with the antenna. In another example, bandwidth 2790 may also be referred to as a bandwidth of antenna (or an antenna bandwidth or a radio frequency (RF) bandwidth of antenna).

[0367] The wireless device may transmit UL signals over an UL frequency using (or via) the antenna (e.g., the Tx antenna or the Tx / Rx antenna). In another example, the wireless device may receive DL signals over a DL frequency using (or via) the antenna (e.g., the Rx antenna or the Tx / Rx antenna). The UL frequency and the DL frequency may be within bandwidth 2790.

[0368] In an example, band 2720 may be band n26 (e.g., an FDD band) and band 2780 may be band n 106 (e.g., an FDD band). For example, in band n26, frequency 2732 may be 814 MHz, frequency 2734 may be 849 MHz, frequency 2742 may be 859 MHz, and frequency 2744 may be 894 MHz. For example, UL band 2730 of band n26 may be 35 MHz (e.g , 849-814 MHz) and DL band 2740 of band n26 maybe 35 MHz (e.g , 894-859 MHz). In another example, in band n106, frequency 2752 may be 896 MHz, frequency 2754 may be 901 MHz, frequency 2762 may be 935 MHz, and frequency 2764 may be 940 MHz. For example, ULband 2750 of band n26 may be 5 MHz (e.g., 901-896 MHz) and DL band 2760 of band n26 may be 5 MHz (e.g., 940-935 MHz). In this example, frequency 2792 may be 814 MHz and frequency 2794 may be 940 MHz. For example, bandwidth 2790 maybe 120 MHz (e.g., 940-814 MHz).

[0369] FIG. 28 illustrates an example of a band combination 2800 of a band 2820 and a band 2880 per an aspect of the present disclosure. Band combination 2800 may also be referred to as a multicarrier (MC) operation (e.g., a carrier aggregation).

[0370] The multicarrier (MC) operation may be implemented according to the example embodiments described above (eg., the MC operation). For example, band 2820 may be associated with a serving cell (e.g., an SCell, etc.) of a wireless device. In an example, band 2880 may be associated with another (e.g., a second) serving cell (e.g., a PCell, a PSCell, an SCell, etc.) of the wireless device. Band 2820 and band 2880 may be implemented according to the example embodiments in FIG. 24A (e.g., FR1 bands 2420) and / or in FIG.24B (e.g., FR2 bands 2440).

[0371] In an example of FIG.28, band 2820 may comprise a downlink (DL) band 2840. DL band 2840 may also be referred to as a DL portion (or part or section or segment) of band 2820 in a frequency domain. DL band 2840 may include DL frequencies from a frequency 2842 up to a frequency 2844. A wireless device may receive a signal on (orDocket No.: 25-1051 PCTvia or over) a DL frequency within DL band 2840. In an example, band 2820 may be an SDL band. The SDL band may be implemented according to the example embodiments in FIG.24A (e.g., the SDL band).

[0372] In an example of FIG.28, Band 2880 may comprise an uplink (UL) band 2850 and a downlink (DL) band 2860. UL band 2850 may also be referred to as an UL portion (or part or section or segment) of band 2880 in a frequency domain. DL band 2860 may also be referred to as a DL portion (or part or section or segment) of band 2880 in a frequency domain. UL band 2850 may include UL frequencies from a frequency 2852 up to a frequency 2854. DL band 2860 may include DL frequencies from a frequency 2862 up to a frequency 2864. A wireless device may transmit a signal on (or via or over) an UL frequency within UL band 2850. A wireless device may receive a signal on (or via or over) a DL frequency within DL band 2860.

[0373] In an example, band 2880 may be an FDD band or a HD-FDD band. The FDD band and the HD-FDD band may be implemented according to the example embodiments in FIG.24A (e.g., the FDD band and the HD-FDD band) and / or in FIG.27 (e.g., band 2720 and band 2780).

[0374] In an example of FIG.28, Band 2820 and band 2880 may be within a bandwidth 2890. Bandwidth 2890 may include frequencies (e.g., UL frequencies and / or DL frequencies) from a frequency 2892 up to a frequency 2894. Bandwidth 2890 may be expressed (or defined) in terms of one or more frequency resources (e.g, X13 resource blocks). In another example, bandwidth 2890 may be expressed (or defined) in terms of one or more frequency units (e.g., X14 MHz).

[0375] In an example, a wireless device may be associated with an antenna. The antenna may be implemented according to the example embodiments in FIG.28 (e.g., the antenna). In an example, bandwidth 2890 may be associated with the antenna. In another example, bandwidth 2890 may also be referred to as a bandwidth of antenna (or an antenna bandwidth ora radio frequency (RF) bandwidth of antenna).

[0376] The wireless device may transmit UL signals over an UL frequency using (or via) the antenna (e.g., the Tx antenna or the Tx / Rx antenna). In another example, the wireless device may receive DL signals over a DL frequency using (or via) the antenna (e.g., the Rx antenna or the Tx / Rx antenna). The UL frequency and the DL frequency may be within bandwidth 2890.

[0377] In an example, band 2820 may be band n29 (e.g., an SDL band) and band 2880 may be band n5 (e.g., an FDD band). For example, in band n29, frequency 2842 may be 717 MHz and frequency 2844 maybe 728 MHz. For example, DL band 2840 of band n29 maybe 11 MHz (e.g., 728-717 MHz). In another example, in band n5, frequency 2852 may be 824 MHz, frequency 2854 may be 849 MHz, frequency 2862 may be 869 MHz, and frequency 2864 may be 894 MHz. For example, UL band 2850 of band n5 may be 25 MHz (e.g., 849-824 MHz) and DL band 2860 of band n5 maybe 25 MHz (e.g., 894-869 MHz). In this example, frequency 2892 maybe717 MHz and frequency 2894 maybe 894 MHz. For example, bandwidth 2890 maybe 177 MHz (e.g., 894-717 MHz).Docket No.: 25-1051 PCT

[0378] FIG. 29 illustrates an example of a band combination 2900 of a band 2920 and a band 2980 per an aspect of the present disclosure. Band combination 2900 may also be referred to as a multicarrier (MC) operation (e.g, a carrier aggregation).

[0379] The multicarrier (MC) operation may be implemented according to the example embodiments described above (e.g., the MC operation). For example, band 2920 may be associated with a serving cell (e.g., an SCell, etc.) of a wireless device. In an example, band 2980 may be associated with another (e.g., a second) serving cell (e.g., a PCell, a PSCell, an SCell, etc.) of the wireless device. Band 2920 and band 2980 may be implemented according to the example embodiments in FIG. 24A (e.g., FR1 bands 2420) and / or in FIG.24B (e.g., FR2 bands 2440).

[0380] In an example of FIG.29, band 2920 may comprise a downlink (DL) band 2940. DL band 2940 may also be referred to as a DL portion (or part or section or segment) of band 2920 in a frequency domain. DL band 2940 may include DL frequencies from a frequency 2942 up to a frequency 2944. A wireless device may receive a signal on (or via or over) a DL frequency within DL band 2940. In an example, band 2920 may be an SDL band. The SDL band may be implemented according to the example embodiments in FIG.24A (e.g., the SDL band) and / or in FIG. 28 (e.g., band 2820).

[0381] In an example of FIG.29, Band 2980 may comprise an uplink (UL) band 2950 and a downlink (DL) band 2960. UL band 2950 may also be referred to as an UL portion (or part or section or segment) of band 2980 in a frequency domain. DL band 2960 may also be referred to as a DL portion (or part or section or segment) of band 2980 in a frequency domain. UL band 2950 may include UL frequencies from a frequency 2952 up to a frequency 2954. DL band 2960 may include DL frequencies from a frequency 2962 up to a frequency 2964. A wireless device may transmit a signal on (or via or over) an UL frequency within UL band 2950. A wireless device may receive a signal on (or via or over) a DL frequency within DL band 2960.

[0382] A difference between frequency 2954 and frequency 2962 (e.g., frequency 2962 - frequency 2954) may also be referred to as a duplex gap of band 2980. The duplex gap may also be referred to as a distance (in frequency domain) between the last (or end) frequency of UL band 2950 and the first frequency of DL band 2960. As shown in FIG. 29, band 2920 is (or frequencies of band 2920) within the duplex gap of band 2980.

[0383] In an example, band 2980 may be an FDD band or a HD-FDD band. The FDD band and the HD-FDD band may be implemented according to the example embodiments in FIG.24A (e.g., the FDD band and the HD-FDD band), in FIG.27 (e.g., band 2720 and band 2780), and / or in FIG. 28 (e.g , band 2880).

[0384] In an example of FIG.29, Band 2920 and band 2980 may be within a bandwidth 2990. Bandwidth 2990 may include frequencies (e.g., UL frequencies and / or DL frequencies) from a frequency 2992 up to a frequency 2994. Bandwidth 2990 may be expressed (or defined) in terms of one or more frequency resources (e.g., X13 resource blocks). In another example, bandwidth 2990 may be expressed (or defined) in terms of one or more frequency units (eg, X14 MHz).Docket No.: 25-1051 PCT

[0385] In an example, a wireless device may be associated with an antenna. The antenna may be implemented according to the example embodiments in FIG.29 (e.g, the antenna). In an example, bandwidth 2990 may be associated with the antenna. In another example, bandwidth 2990 may also be referred to as a bandwidth of antenna (or an antenna bandwidth ora radio frequency (RF) bandwidth of antenna).

[0386] The wireless device may transmit UL signals over an UL frequency using (or via) the antenna (e.g., the Tx antenna or the Tx / Rx antenna). In another example, the wireless device may receive DL signals over a DL frequency using (or via) the antenna (e.g., the Rx antenna or the Tx / Rx antenna). The UL frequency and the DL frequency may be within bandwidth 2990.

[0387] In an example, band 2920 may be band n29 (e.g., an SDL band) and band 2980 may be band n12 (e.g., an FDD band). For example, in band n29, frequency 2942 may be 717 MHz and frequency 2944 maybe 729 MHz. For example, DL band 2940 of band n29 maybe 11 MHz (e.g., 729-717 MHz). In another example, in band n12, frequency 2952 may be 699 MHz, frequency 2954 may be 716 MHz, frequency 2962 may be 729 MHz, and frequency 2964 may be 746 MHz. For example, UL band 2950 of band n12 maybe 17 MHz (e.g., 716-699 MHz) and DL band 2960 of band n12 maybe 17 MHz (e.g., 746-729 MHz). In this example, frequency 2992 maybe 717 MHz and frequency 2994 may be 746 MHz. For example, bandwidth 2990 may be 29 MHz (e.g., 746-717 MHz)

[0388] A base station may configure a wireless device with two or more carrier frequencies (e.g., a first carrier frequency and a second carrier frequency), e.g., in a multicarrier (MC) operation. The first carrier frequency and the second carrier frequency may be associated with (or belong to) different bands. For example, the first carrier frequency may be associated with (or belong to) a first band. In another example, the second carrier frequency may be associated with (or belong to) a second band.

[0389] The MC operation may be implemented according to the example embodiments described above, in FIG.27 (e.g., band combination 2700), in FIG.28 (e.g., band combination 2800), and / or in FIG. 29 (e.g., band combination 2900). The first band and the second band may be implemented according to the example embodiments described in FIG. 24A (e.g, FR1 bands 2420) and / or in FIG.24B (e.g, FR1 bands 2440).

[0390] The wireless device may be associated with a first cell (e.g, a PCell) and a second cell (e.g, an SCell). In an example, a first cell may operate on (or belong to) the first carrier frequency. In another example, a second cell may operate on (or belong to) the second carrier frequency. In an example, a multicarrier (MC) operation (e.g, carrier aggregation), during the same time resource (eg, a symbol, a slot, a subframe, etc.), the wireless device, based on a capability of the wireless device, may receive (e.g, both) first signals via the first cell and the second signals via the second cell. In another example, of the multicarrier (MC) operation (e.g, carrier aggregation), during a time resource (e.g, a symbol, a slot, a subframe, etc.), the wireless device, based on a capability of the wireless device, may receive either first signals via the first cell or the second signals via the second cell.

[0391] The physical size of an antenna (e.g, length of the antenna, diameter of antenna, etc,) may depend on (or influenced by or impacted by or associated with) a wavelength of a carrier frequency. For example, the physical size ofDocket No.: 25-1051 PCTantenna increases as the carrier frequency decreases in frequency (or increase in the wavelength). For example, at frequencies below a frequency threshold (e.g. , frequencies below 1 GHz), implementation of multiple antennas may increase form factor (e.g., physical size, layout, shape, etc.) of the wireless device. To reduce cost, complexity, and physical size of the wireless device, for multicarrier operation at frequencies below the frequency threshold, the wireless device may use (or apply or employ or implement) the same antenna for receiving first signals via the first cell and the second signals via the second cell.

[0392] In an example, the difference between the first carrier frequency and the second carrier frequency may be larger than a frequency difference threshold (e.g., 100 MHz). For example, for receiving the first signals and the second signals during the same time resource, a bandwidth of the antenna may also be larger than the frequency difference threshold. The complexity, cost, and / or power consumption of the wireless device may increase based on the bandwidth of the antenna being larger than the frequency difference threshold. An antenna associated with a bandwidth larger than the frequency difference threshold may be referred to as a wideband (or a wide bandwidth) antenna.

[0393] An antenna associated with a bandwidth smaller than, or equal to, the frequency difference threshold may be referred to as a narrowband (or a narrow bandwidth) antenna. To reduce complexity, cost, and / or power consumption of the wireless device, the wireless device may use (or implement or employ) the narrow band antenna. For example, at different times, the wireless device may receive the first signals and the second signals using the same antenna (e.g., the narrow band antenna). For example, the wireless device may receive the first signals in first time periods and the second signals in second time periods. The first time periods and the second time periods may be referred to as (or belong to or associated with) a time-domain (TD) patten. The first time periods and the second time periods may not overlap in time. In the MC operation based on the TD pattern, the wireless device may not receive (in the time domain) the first signals and / or the second signals, at the same time. Several procedures related to a radio link of the wireless device (e.g., an RLM, a BFD, a CBD, etc.) may be based on (or performed on) reference signals of the first cell and / or the second cell. The wireless device may detect a radio link problem (e.g., a beam failure, a radio link failure, etc.) based on measurements on the reference signals (e.g., an SSB, a CSI-RS, etc.). The measurements may be implemented according to the example embodiments in FIG. 17 (e.g., measurement 1700).

[0394] In response to the radio link problem (e.g., a beam failure, a radio link failure, etc.), the wireless device may initiate a radio link recovery procedure (e.g., a beam failure recovery, an RRC connection re-establishment, etc.). For example, during the radio link recovery procedure associated with the second cell (e.g., an SCell), the wireless device may monitor the first signals of the first cell (e.g., a PCell) and the second signals of the second cell (e.g., the SCell). In existing technologies (e.g., using the TD-pattern for the MC operation), the performance of the radio link recovery procedure may be degraded. For example, the wireless device may not be capable of measuring on reference signals (e.g., an SSB) of a PCell transmitted during time resources allocated to an SCell. For example, due to inability to measure on some of the reference signals, a time period of the radio link recovery procedure may increase AnDocket No.: 25-1051 PCTincrease in the time period of the radio link recovery procedure may reduce throughput (e.g . , reduce user bit rate and / or increase packet transmission delay).

[0395] A wireless device may initiate an uplink transmission associated with a procedure (e.g., a beam failure recovery procedure, a measurement report, etc.,) of a second cell (e.g., an SCell) or a neighbor cell. As one example, the uplink transmission may be a request (e.g., a scheduling request) for uplink resources for transmitting a message. The wireless device may be associated with at least two cells (e.g., a first cell (e.g., a PCell) and the second cell) in a multi-carrier (MC) operation with a TD pattern. In existing technologies (e.g., using a time domain (TD) pattern for the MC operation as described above), the performance of the procedure may be degraded when the wireless device is associated with at least two cell (e.g., in MC operation). For example, a time period of the procedure may increase when the wireless device is associated with the at least two cells (e.g., and communicating on the at least two cells at different times). An increase in the time period of the procedure may reduce throughput (e.g., reduce user bit rate and / or increase packet transmission delay).

[0396] Embodiments of the present disclosure are related to an approach for solving the problems described above. These and other features of the present disclosure are described further below.

[0397] In an example embodiment, a wireless device may receive one or more configuration parameters. The one or more configuration parameters may indicate first time periods for first downlink receptions via a first cell, and second time periods for second downlink receptions via a second cell. The wireless device may transmit, via the first cell, an uplink transmission for an operation associated with the second cell or a third cell. The wireless device, based on the uplink transmission and during at least one second time period of the second time periods: may cancel (or not monitor or skip) the second downlink receptions via the second cell, and may monitor (or receive) the first downlink receptions via the first cell.

[0398] As another example embodiment, a node (e.g., a base station) may transmit to a wireless device, one or more configuration parameters. The one or more configuration parameters may indicate first time periods for first downlink transmissions via a first cell, and second time periods for second downlink transmissions via a second cell. The node may receive, from the wireless device, an uplink transmission for an operation associated with the second cell or a third cell. The node, based on reception of the uplink transmission and during at least one second time period of the second time periods, may not transmit the second downlink transmissions via the second cell, and transmit the first downlink transmissions via the first cell.

[0399] Based on the example embodiment, in response to the uplink transmission associated with the procedure, the wireless device has greater flexibility to monitor / receive the first signals via the first cell (e.g., during the first time periods and the second time periods) even though the wireless device is associated with the TD-pattern (e.g., with specific time periods for receiving signals on each cell). This may enable more continuous communication, via the first cell (e.g., to expedite performing a follow-up procedure of the operation associated with the second cell, between the wireless device and network when the wireless device is associated with the TD-pattern in MC operation of two cells.Docket No.: 25-1051 PCTFor example, time duration of a response (e.g an allocation of UL resources, a scheduling grant, etc.) from a node (e.g. , a base station) may be reduced. Based on the example embodiment, the time period to complete the operation (e.g., beam failure recovery) maybe reduced.

[0400] Similarly, based on the example embodiment, the node (e.g., a base station) will have flexibility to transmit to the wireless device, a response (e.g., a scheduling grant) corresponding to the uplink transmission, via the first cell (e.g., a PCell), during the first time periods and the second time periods. The time duration over which the node may send the response to the wireless device will be reduced.

[0401] As another example, a wireless device may detect a radio link problem (e.g., a radio link failure, a measurement report, etc.,) on a first cell (e.g., a PCell). The wireless device may detect the radio link problem based on reference signals (e.g., an SSB) of the PCell. In existing technologies (e.g., using a time domain (TD) pattern for the MC operation as described above), the wireless device may miss (e.g., not receive or not detect) the reference signals on the first cell, e.g., due to the reference signals overlapping with the second time periods for the second downlink receptions on the second cell (e.g., an SCell). During a radio link recovery procedure (e.g., in response to the radio link problem), missing the reference signals of the first cell may delay the radio link recovery procedure. For example, a time period of the procedure (e.g , the radio link recovery procedure) may increase. An increase in the time period of the procedure (e.g., radio link recovery procedure) may reduce throughput (e.g., reduce user bit rate and / or increase packet transmission delay).

[0402] In an example embodiment, a wireless device may receive one or more configuration parameters. The one or more configuration parameters may indicate first time periods for first downlink receptions via a first cell, and second time periods for second downlink receptions via a second cell. The wireless device may determine (e.g., detect, identify, etc.) a radio link problem on the first cell. The wireless device, based on the determined radio link problem, may cancel / skip the second downlink receptions, on the second serving cell, during at least one second time period of the second time periods.

[0403] In an example embodiment, a node (eg., a base station) may transmit to a wireless device, one or more configuration parameters. The one or more configuration parameters may indicate first time periods for first downlink transmissions via a first cell, and second time periods for second downlink transmissions via a second cell. The node may receive, from the wireless device, an uplink signal indicating a radio link problem on the first cell. The node, based on the received uplink signal, may not transmit the second downlink transmissions, on the second cell, during at least one second time period of the second time periods.

[0404] Based on the example embodiment, in response to detecting the radio link problem (e.g., a radio link failure) on the first cell (e.g., a PCell), the wireless device is capable of monitoring / receiving the reference signals on the PCell without any interruption, even though the wireless device is associated with the TD-pattern. For example, by cancelling the second downlink receptions during the second time periods, the wireless device may receive the reference signalsDocket No.: 25-1051 PCTon the PCell without any interruption. Based on the example embodiment, the time period to complete the radio link problem recovery procedure (e.g., an RRC connection re-establishment) may be reduced.

[0405] Based on the example embodiment, the node (e.g., a base station) may stop transmitting to the wireless device, the second downlink transmissions, via the second cell, during the radio link problem recovery procedure. For example, downlink resources (e.g., a PDCCH / PDSCH transmissions) will not be wasted.

[0406] A wireless device may be associated with more than two cells in MC operation discussed in the examples above. For example, the wireless device may be associated with three or more cells in a multi-carrier (MC) operation. The wireless device may receive / monitor signals via the three or more cells based on a time-domain (TD) pattern (as described above). The wireless device may transmit an uplink signal (e.g., associated with one of the three or more cells) associated with a (eg., critical) procedure (e.g., a beam failure, etc.). A node (e.g., a base station) may transmit a response corresponding to the uplink signal. In existing technologies, the wireless device is not aware of which cell, among the three or more cells, the wireless device is to use for receiving the response. This may cause the wireless device may monitor signals on each of the three or more cells for the response. Time duration to receive the response may increase. The wireless device may also miss the response. Time duration to complete the critical procedure may increase.

[0407] In an example embodiment, a wireless device may receive one or more configuration parameters. The one or more configuration parameters may indicate first time periods for first downlink receptions via a first cell, second time periods for second downlink receptions via a second cell, and third time periods for third downlink receptions via a third cell. The wireless device may transmit an uplink signal The wireless device, based on the transmission of uplink signal, may determine, for a response corresponding to the uplink signal, to cancel (or not monitor or skip) one or more downlink receptions during one or more time periods among: the second downlink receptions via the second cell during at least one second time period of the second time periods; and / or the third downlink receptions via the third cell during at least one third time period of the third time periods. The wireless device, based on the determine, may receive the response, via the first cell, during the one or more time periods.

[0408] In an example embodiment, a node (e.g., a base station) may transmit to a wireless device one or more configuration parameters. The one or more configuration parameters may indicate first time periods for first downlink transmissions via a first cell, second time periods for second downlink transmissions via a second cell, and third time periods for third downlink transmissions via a third cell. The node may receive an uplink signal from the wireless device. The node, based on the reception of uplink signal and for a response corresponding to the uplink signal, the wireless device may determine not to transmit one or more downlink transmissions during one or more time periods among: the second downlink transmissions via the second cell during at least one second time period of the second time periods; and / or the third downlink transmissions via the third cell during at least one third time period of the third time periods. The node may transmit the response to the wireless device, via the first cell, during the one or more time periods.Docket No.: 25-1051 PCT

[0409] Based on the example embodiment, the wireless device has greater flexibility of determining a cell (e.g., the first cell) on which the wireless device is to monitor / receive the response. This may enable more continuous communication, via the first cell (e.g., to receive the response) when the wireless device is associated with the TD-pattern in MC operation of two cells. The solution of the embodiment may reduce the power consumption of the wireless device, e.g., the time to receive the response may not increase.

[0410] Similarly, based on the example embodiment, the node (e.g., the base station) will be capable to determine the one or more time periods, during which the wireless device is to monitor / receive the response, via the cell. Based on the solution, the node is not expected to resend the response. The base station resources will not be wasted.

[0411] As one example, the procedure may be a beam link recovery procedure. For example, a wireless device may initiate a beam link recovery procedure associated with a second cell (e.g., an SCell). During the beam failure recovery procedure associated with the second cell, the wireless device may monitor first signals of the first cell (e.g., a PCell) and second signals of the second cell (e.g., the SCell), for receiving an allocation of uplink resources. In existing technologies (e.g., using the TD-pattern for the MC operation), the time performance of the beam failure recovery procedure may be degraded. For example, a time period of the beam failure recovery procedure may increase. An increase in the time period of the radio link recovery procedure may reduce throughput (e.g., reduce user bit rate and / or increase packet transmission delay).

[0412] Embodiments of the present disclosure are related to an approach for solving the problems described above. These and other features of the present disclosure are described further below.

[0413] In an example embodiment, a wireless device may receive one or more configuration parameters. The one or more configuration parameters may indicate first time periods for first downlink receptions via a first cell, and second time periods for second downlink receptions via a second cell. The wireless device may transmit, during a first time duration and via the first cell, a scheduling request indicating a beam failure of the second cell. The wireless device, may determine a beam failure recovery, of the second cell, being completed at a second time. The wireless device, during a time interval between the first time duration and the second time, may: cancel (or not monitor or skip) the second downlink receptions, via the second cell, during at least one second time period of the second time periods; and monitor (or receive) the first downlink receptions, via the first cell, during at least one second time period of the second time periods.

[0414] In an example embodiment, a node (eg., a base station) may transmit to a wireless device, one or more configuration parameters. The one or more configuration parameters may indicate first time periods for first downlink transmissions via a first cell, and second time periods for second downlink transmissions via a second cell. The node may receive from the wireless device, via the first cell and during a first time duration, a scheduling request indicating a beam failure of the second cell. The node may determine that the wireless device may complete a beam failure recovery, of the second cell, at a second time. During a time interval between the first time duration and the second time, the node may not transmit the second downlink transmissions, via the second cell, during at least one secondDocket No.: 25-1051 PCTtime period of the second time periods; and may transmit the first downlink receptions, via the first cell, during at least one second time period of the second time periods.

[0415] Based on the example embodiment, the wireless device has greater flexibility of completing the beam failure recovery procedure during a defined time interval, even though the wireless device is associated with the TD-pattern for the MC operation of two cells. For example, time duration to complete the beam failure recovery procedure will not exceed the defined time interval. The wireless device will be capable of resuming communications on the second cell (e.g., the SCell) after the defined time interval.

[0416] Similarly, the example embodiment will enable an alignment between the node (e.g., a base station) and the wireless device, during the beam failure recovery procedure associated with the second cell (e.g., the SCell). For example, the node (e.g., a base station) will be capable of transmitting to the wireless device, the response (e.g., a scheduling grant) corresponding to the scheduling request for beam failure recovery procedure, via the first cell (e.g., a PCell), during the defined time interval. The time to resume communications with the wireless device (e.g., after the beam failure recovery procedure) will be reduced.

[0417] A wireless device may detect a radio link problem (e.g., a radio link failure, a measurement report, etc.) on a first cell (e.g., a PCell). The wireless device may monitor reference signals on the first cell in response to detecting the radio link problem. The node (e.g., a base station) may not be aware of the time when the wireless device has detected the radio link problem.

[0418] In an example embodiment, a wireless device may receive one or more configuration parameters. The one or more configuration parameters may indicate first time periods for first downlink receptions via a first cell, and second time periods for second downlink receptions via a second cell. The wireless device may determine (e.g., detect, identify, etc.) a radio link problem on the first cell. The wireless device, based on the determined radio link problem, may: transmit an uplink signal for the radio link problem; cancel (or not monitor or skip) the second downlink receptions, on the second serving cell, during at least one second time period of the second time periods; and receive (or monitor) the first downlink receptions, on the first serving cell, during the at least one second time period.

[0419] In an example embodiment, a node may transmit to a wireless device, one or more configuration parameters. The one or more configuration parameters may indicate first time periods for first downlink transmissions via a first cell, and second time periods for second downlink transmissions via a second cell. The node may receive, from the wireless device, an uplink signal indicating a radio link problem on the first cell. The node, based on the received uplink signal and during at least one second time period of the second time periods, may not transmit the second downlink transmissions on the second cell; and transmit the first downlink transmissions on the first serving cell.

[0420] Based on the example embodiment, the node (e.g., the base station) and the wireless device will be aligned (e.g., based on the uplink signal) regarding when (e.g., the second time period) the wireless device is going to cancel the second downlink receptions via the second cell and receive the first downlink receptions via the first cell. The solution avoids wastage of resources. For example, the node may not transmit the second downlink receptions to theDocket No.: 25-1051 PCTwireless device, during the second time period. The node may allocate / schedule the resources toother wireless device(s), during the second time period.

[0421] A wireless device may be associated with three or more cells in a multi-carrier (MC) operation. The wireless device may receive / monitor signals via the three or more cells based on a time-domain (TD) pattern (as described above). The wireless device may transmit an uplink signal (e.g., associated with one of the three or more cells) associated with a critical procedure (e.g., a beam failure, etc.). A node (e.g., a base station) may transmit a response corresponding to the uplink signal. In existing technologies, the wireless device is not aware of the cell, among the three or more cells, for receiving the response. The wireless device may monitor signals on the three or more cells for the response. Time duration to receive the response may increase. The wireless device may also miss the response. Time duration to complete the critical procedure may increase.

[0422] In an example embodiment, a wireless device may receive one or more configuration parameters. The one or more configuration parameters may indicate first time periods for first downlink receptions via a first cell, second time periods for second downlink receptions via a second cell, and third time periods for third downlink receptions via a third cell. The wireless device may receive a message. The wireless device may transmit an uplink signal. The wireless device, based on the received message, may determine, for a response corresponding to the uplink signal, to cancel (or not monitor or skip) one or more downlink receptions during one or more time periods among: the second downlink receptions via the second cell during at least one second time period of the second time periods; and / or the third downlink receptions via the third cell during at least one third time period of the third time periods. The wireless device, based on the determine, may receive the response, via the first cell, during the one or more time periods.

[0423] In an example embodiment, a node may transmit to a wireless device one or more configuration parameters. The one or more configuration parameters may indicate first time periods for first downlink transmissions via a first cell, second time periods for second downlink transmissions via a second cell, and third time periods for third downlink transmissions via a third cell. The node may transmit a message to the wireless device. The node may receive an uplink signal from the wireless device. The node, based on the message, and fora response corresponding to the uplink signal, may not transmit one or more downlink transmissions during one or more time periods among: the second downlink transmissions via the second cell during at least one second time period of the second time periods; and / or the third downlink transmissions via the third cell during at least one third time period of the third time periods. The node may transmit the response to the wireless device, via the first cell, during the one or more time periods.

[0424] Based on the example embodiment, the wireless device determines a cell (e.g., the first cell) on which the wireless device is to monitor / receive the response, based on the message from the node (e.g., a base station). Firstly, the message enables an alignment between the node and the wireless device regarding the one or more time periods, during which the wireless device is to monitor / receive the response, via the first cell (e.g., a PCell) . Based on the solution of the embodiment, the wireless is not expected to miss the response. Secondly, based on the exampleDocket No.: 25-1051 PCTembodiment, the node will have the flexibility to decide whether the one or more time periods are associated with the second cell (e.g., a first SCell) and / or the third cell (e.g., a second SCell).

[0425] FIG. 30 illustrates an example of a multicarrier (MC) operation 3000 associated with a wireless device as per an aspect of an embodiment of the present disclosure. The wireless device may use MC operation 3000 for receiving signals from a cell 3010 and a cell 3020. MC operation 3000 may be implemented according to the example embodiments described above (e.g., the MC operation). The features illustrated in FIG. 30 maybe combined with any of the features previously discussed with reference to FIGs. 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, and / or 29.

[0426] As shown in FIG. 30, the wireless device may be associated with cell 3010 operating on (or belonging to) a frequency 3012, and cell 3020 operating on (or belonging to) a frequency 3022. For example, cell 3010 and cell 3020 may be serving cells of the wireless device (e.g , in MC operation 3000). In an example, cell 3010 may be an SpCell (e.g., a PCell ora PSCell) and cell 3020 maybe an SCell. In another example, cell 3010 may be an SCell and cell 3020 may be an SpCell (e.g., a PCell or a PSCell). For example, the wireless device may communicate with a node via cell 3010 and cell 3020.

[0427] In an example, the node may be a RAN node. The RAN node may also be referred to as a next generation RAN (NG-RAN) node. Examples of the RAN node may be a base station, a g N B, a central unit of a base station (e.g, a gNB central unit (gNB-CU)), a distribution unit of a base station (e.g., a g N B distribution unit (gNB-DU)), a transmission reception point (TRP), etc.

[0428] In an example, frequency 3012 of cell 3010 may be associated with (or belong to) a first band, and frequency 3022 of cell 3020 may be associated with (or belong to) a second band Frequency 3012 and frequency 3022 may be indicated by (or addressed by) a frequency channel number (or a frequency channel identifier), e.g., an ARFCN, an NR-ARFCN, etc. Frequency 3012 and frequency 3022 may be downlink (DL) frequencies (or DL carrier frequencies). In an example, cell 3010 may also be associated with an uplink (UL) frequency, such as, e.g., a first UL frequency (or a first UL carrier frequency). In another example, cell 3020 may also be associated with an UL frequency, such as, e.g., a second UL frequency (ora second UL carrier frequency).

[0429] Frequency 3012, frequency 3022, the first UL frequency, and / or the second UL frequency, may be implemented according to the example embodiments described above (e.g., the carrier frequency). The first band, associated with frequency 3012, and the second band, associated with frequency 3022, may be implemented according to the example embodiments in FIG.24A (e.g., FR1 bands 2420) and / or FIG. 24B (eg., FR2 bands 2440).

[0430] In an example, the first band may be an FDD band, and the second band may be an SDL band. In another example, the first band may be an FDD band, and the second band may also be an FDD band. For example, the first band, the second band, and MC operation 3000 may be implemented according to the example embodiments in FIG.27 (e.g., band 2720, band 2780, and band combination 2700), FIG. 28 (e.g., band 2820, band 2880, and band combination 2800), and / or FIG. 29 (e.g., band 2920, band 2980, and band combination 2900).Docket No.: 25-1051 PCT

[0431] The wireless device may receive one or more configuration parameters from the node For example, the wireless devices may receive one or more configuration parameters from the node via RRC signaling, a MAC-CE, etc. The one or more configuration parameters may indicate (or comprise or include or identify) one or more time periods 3040 and one or more time periods 3042. For example, a cell group configuration message (e.g., CellGroupConfig) or an RRC connection reconfiguration message (e.g., RRCConnectionReconfiguration) may comprise (or include or indicate), the one or more configuration parameters.

[0432] During one or more time periods 3040, the wireless device may monitor 3014 signals 3016 on cell 3010. During one or more time periods 3042, the wireless device may monitor 3024 signals 3026 on cell 3020. Monitor 3014 signals 3016 may also be referred to as receiving (or monitoring or decoding, or intended to receive) signals 3016. Monitor 3024 signals 3026 may also be referred to as receiving (or monitoring or decoding, or intended to receive) signals 3026.

[0433] One or more time periods 3040 do not overlap (in time) with one or more time periods 3042. In an example, during one or more time periods 3040, the wireless device may not monitor 3024 signals 3026 on cell 3020. In another example, during one or more time periods 3042, the wireless device may not monitor 3014 signals 3016 on cell 3010.

[0434] In an example, signals 3016 and signals 3026 may be referred to as downlink receptions, downlink channels, or downlink reference signals (e.g., an SSB, a CSI-RS, a PRS, a DMRS, etc.). For example, the wireless device may receive signals 3016 and signals 3026 (e.g., the downlink receptions) via (or on or over or through) the downlink channels. In an example, the wireless device may receive signals 3016 via (or on or over or through) a DL control channel and / or via (or on or over or through) a DL data channel. In another example, the wireless device may receive signals 3026 via (or on or over or through) a DL control channel and / or via (or on or over or through) a DL data channel. Examples of the DL control channel may be a physical downlink control channel (PDCCH) or a physical broadcast channel (PBCH). An example of the DL data channel may be a physical downlink shared channel (PDSCH).

[0435] In an example, during one or more time periods 3040, the wireless device may transmit (or send) first uplink (UL) signals on (or via) cell 3010. In another example, during one or more time periods 3042, the wireless device may transmit (or send) second uplink (UL) signals on (or via) cell 3020.

[0436] In an example, the first UL signals and the second UL signals may be referred to as uplink transmissions, uplink channels, or uplink reference signals (e.g., an SRS, a DMRS, etc.). For example, the wireless device may transmit the first UL signals and the second UL via (or on or over or through) the uplink channels. In an example, the wireless device may transmit the first UL signals via (or on or over or through) an UL control channel and / or via (or on or over or through) an UL data channel. In another example, the wireless device may transmit the second UL signals via (or on or over or through) an UL control channel and / or via (or on or over or through) an UL data channel. Examples of the UL control channel may be a physical uplink control channel (PUCCH) or a physical random access channel (PRACH). An example of the UL data channel may be a physical uplink shared channel (PUSCH).Docket No.: 25-1051 PCT

[0437] Each time period, of one or more time periods 3040, may be expressed (or defined) in terms of one or more time units (e.g., X21 ms) and / or one or more time resources (e.g., X22 symbols, X23 slots, X24 subframes, etc.). Each time period, of one or more time periods 3042, may be expressed (or defined) in terms of one or more time units (e.g., X25 ms) and / or one or more time resources (e.g., X26 symbols, X27 slots, X28 subframes, etc.).

[0438] The start timings of any two successive (or consecutive) time periods 3040 may be separated (in time) by a periodicity 3044. The start timings of any two successive (or consecutive) time periods 3042 may be separated (in time) by periodicity 3044. For example, periodicity 3044 may be referred to as a periodicity (or a period or a time period repetition period) of one or more time periods 3040, and / or one or more time periods 3042. The one or more configuration parameters may indicate (or comprise or include or identify) periodicity 3044.

[0439] The one or more time periods 3040 and the one or more time periods 3042 may be associated with (or may form, create, or indicate) a first pattern. The first pattern may also be referred to as a first multicarrier (MC) pattern, a time domain (TD) pattern, a time domain resource pattern, a time domain multiplexing (TDM) pattern, a TDM resource pattern, a TDM restriction pattern, a semi-static pattern, a carrier switching pattern, etc. In an example, periodicity 3044 may be associated with the first pattern. In an example, the first pattern may be associated with an identifier (e.g., a pattern identifier). For example, the one or more configuration parameters may indicate (or comprise or include or identify) the first pattern, (e.g., the identifier of the first pattern). In an example, the one or more configuration parameters may indicate (or include) an association, between the one or more time periods 3040 and cell 3010, and / or between the one or more time periods 3042 and cell 3020.

[0440] In an example, the wireless device may start applying (or using) the first pattern based on (or from) a reference time. For example, the wireless device may start (or initiate) monitoring (or receiving) of signals 3016 and / or signals 3026) based on (or during or by using) the first pattern from the reference time. In another example, the wireless device may start (or initiate) transmission of the first signals and / or the second signals based on (or during or by using) the first pattern from the reference time.

[0441] In an example, the reference time may be based on the one or more configuration parameters. The one or more configuration parameters may indicate the first pattern. For example, the wireless device may receive (or acquire or complete reception of) the one or more configuration parameters at (or by) the reference time. For example, the reference time may be the end of a reference time resource (e.g., a symbol, a slot, a subframe, a frame, etc.). During the reference time resource, the wireless device may receive (or complete reception of) the one or more configuration parameters.

[0442] In another example, the reference time may start X31 number of time resources (e.g., symbols, slots, subframes, frames, etc.) from (or after or since) the end of the reference time resource (e.g., during which the wireless device may receive (or complete reception of) the one or more configuration parameters). In yet another example, the reference time may be based on a configuration (or start) of MC operation 3000. For example, the reference time may be based on the configuration of an SCell (e.g., cell 3020) belonging to (or associated with) MC operation 3000. ForDocket No.: 25-1051 PCTexample, the wireless device may receive from a node, a message, at (or by or X32 number of time resources before (or prior to)) the reference time. The message may indicate the SCell (e.g., one or more parameters of the SCell).

[0443] In yet another example, the reference time may be predefined (e.g., SFN number #X33, a Coordinated Universal Time (UTC) time, etc.). In yet another example, the wireless device may receive from the node, the reference time. For example, the one or more configuration parameters may indicate (or comprise or provide) the reference time.

[0444] As shown in FIG. 30, ata time 3056, the wireless device may transmit an uplink (UL) message 3018 via (or on or through or in) cell 3010 (e.g., to the node). For example, time 3056 may be referred to as the ending time of UL message 3018. For example, the wireless device may transmit UL message 3018 during a time duration. Time 3056 may be the end (or an ending time or an ending time instance) of the time duration. In an example, UL message 3018 may be associated with an operation on cell 3020

[0445] In an example, the wireless devices may transmit, to the node, UL message 3018 via an RRC signaling, a MAC-CE, an uplink control information (UCI), etc. For example, the wireless device may transmit UL message 3018 via (or on) an uplink control channel and / or an uplink data channel. In an example, the uplink control channel may be a physical uplink control channel (PUCCH). In another example, the uplink data channel may be a physical uplink shared channel (RUSCH).

[0446] Although UL message 3018 as illustrated in FIG. 30 is associated with cell 3020, the present disclosure is not particularly limited to this example. As another example, UL message 3018 may be associated with a cell other than cell 3020, such as a third cell. The third cell may be referred to as a neighbor cell, a non-serving cell, etc. In an example, the third cell may belong to (or operate on) frequency 3012, frequency 3022, or a third DL carrier frequency. The third cell may also be associated with a third UL carrier frequency. In an example, the third UL carrier frequency may belong to (or operate) on the first band, the second band, or a third band. The third band is according to the example embodiments in FIG. 24A (e.g., FR1 bands 2420) and / or in FIG. 24B (e.g., FR2 bands 2440).

[0447] During a time period 3052 (e.g., between a time 3050 and a time 3054), the wireless device may skip 3028 signals 3026 on cell 3020. Skip 3028 signals 3026 may also be referred to as canceling (or cancelation of or not receiving or not monitoring or abandoning or discarding, or suspending reception of) signals 3026. During time period 3052, the wireless device may (e.g., instead) monitor signals 3016 on cell 3010. Time period 3052 may comprise (or include) at least one time period, of one or more time periods 3042. In another example, time period 3052 may comprise (or include) at least one time period, of one or more time periods 3040, and at least one time period, of one or more time periods 3042. For example, during the at least one time period of, one or more time periods 3042, the wireless device may skip 3028 signals 3026.

[0448] As illustrated in FIG. 30, time period 3052 may start at time 3050 and end at time 3054. Although the example of FIG. 30 shows that time period 3052 starts at time 3050, the start may be at another time. For example, time period 3052 may start at time 3056. Similarly, time period 3052 may start from the transmission of UL message 3018. In an example, time period 3052 may start at time 3056 and end at time 3054.Docket No.: 25-1051 PCT

[0449] The wireless device may monitor 3024 signals 3026 on cell 3020 after time 3054 (e.g after the end of time period 3052).

[0450] In an example, during a time period between time 3056 and time 3054, the wireless device may discard (or suspend or cancel) the first pattern, and monitor (or use or receive signals 3016 and signals 3026) based on a second pattern. Discarding the first pattern and using the second pattern may also be referred to as a switching (or changing) a pattern (e.g., from the first pattern to the second pattern).

[0451] In an example, the wireless device may receive the one or more configuration parameters indicating (or comprising) the second pattern. The second pattern may comprise a first time period, a second time period, and a periodicity of the first time period and the second time period. For example, during a time period between time 3056 and time 3054, the wireless device may monitor 3014 signals 3016 on cell 3010 over the first time period. In another example, during a time period between time 3056 and time 3054, the wireless device may monitor 3024 signals 3026 on cell 3020 over the second time period.

[0452] In an example, the wireless device may receive the one or more configuration parameters indicating (or comprising) the second pattern in response to UL message 3018. In another example, the wireless device may receive the one or more configuration parameters indicating (or comprising) the second pattern prior to time 3056 (e.g., a preconfiguration of the second pattern).

[0453] In an example, the wireless device may be associated with (or apply or be configured with) the first pattern and / or the second pattern regardless of a discontinuous reception (DRX) cycle. In an example, the wireless device may be associated with (or apply or be configured with) the first pattern and / or the second pattern regardless of a periodicity of the DRX cycle. For example, the wireless device may be associated with (or apply or be configured with) the first pattern and / or the second pattern, and the DRX cycle. In another example, the wireless device may be associated with (or apply or be configured with) the first pattern and / or the second pattern, and not with the DRX cycle.

[0454] UL message 3018 may be referred to as an uplink signal, an uplink transmission, an uplink indication, an uplink indicator, or an uplink flag. In an example, UL message 3018 may be associated with (or indicate) the operation on cell 3020 or the third cell. For example, UL message 3018 may comprise (or indicate or include, or be associated with) a scheduling request (SR), a link failure, a measurement gap pattern (MGR), a report (e.g., an out of range report, a measurement report, a resource status report, a radio resource report, a traffic resource report, etc.), or a measurement event (e.g., an event A1, an event A2, an event A3, an event A6, etc.).

[0455] For example, the operation may be (or related to or pertaining to) the SR, the link failure, the MGP, the report, or the measurement event. The wireless device may trigger, detect, determine, or identify the operation. For example, the wireless device may transmit UL message 3018 based on (or in response to) the operation (or triggering of the operation or detection of the operation).

[0456] For example, UL message 3018 may comprise (or indicate or identify or comprise, or reflect) at least one of: a transmission of an indication of a link failure of cell 3020; a scheduling request (SR) to request an uplink resource forDocket No.: 25-1051 PCTthe transmission of the indication of the link failure of cell 3020; a request to initiate an activation of a measurement gap pattern (MGP) of (or for or associated with) cell 3020 or the third cell; a SR to request an uplink resource for requesting to initiate the activation (or setting up) of the MGP of cell 3020 or the third cell; a request to initiate a deactivation (or release) of the MGP of cell 3020 or the third cell; a SR to request an uplink resource for requesting to initiate the deactivation (or release) of the MGP of (or for or associated with) cell 3020 or the third cell; a request to modify one or more parameters of the MGP of (or for or associated with) cell 3020 or the third cell; a SR to request an uplink resource for requesting to modify the one or more parameters of the MGP of (or for or associated with) cell 3020 or the third cell; a SR to request an uplink resource for transmitting a buffer status report of cell 3020; a SR to request an uplink resource for transmitting a delay status report of cell 3020; a SR to request an uplink resource for transmitting a positioning measurement report of cell 3020 or the third cell; a SR to request an uplink resource for transmitting an out of range report of cell 3020 or the third cell; a SR to request an uplink resource for transmitting a measurement event of cell 3020 or the third cell; or a SR to request an uplink resource for transmitting an indication of a cell group (CG) failure.

[0457] In an example, the link failure may comprise (or indicate) at least one of: a radio link failure (RLF), a beam failure (BF) (or a beam failure detection (BFD) or detection of the BF), a candidate beam detection (CBD), an unknown transmission configuration indication (TCI) state, or an unknown cell 3020 or the third cell. In an example, UL message 3018 may comprise an identifier of a beam, an identifierof a TCI, an identifier (e.g., a PCI, a CGI, etc.) of cell 3020 or the third cell.

[0458] The radio link failure, the beam failure (or a detection of the BF), and the candidate beam (or a detection of the CB) maybe implemented according to the example embodiments in FIG. 17 (e.g., the radio link failure, the beam failure detection, and the candidate beam detection).

[0459] A cell (e.g., cell 3020 or the third cell) may become known or unknown over time. A cell (e.g., cell 3020 or the third cell) being known may also be referred to as a known cell (e.g., known cell 3020 or the known third cell). The cell (eg., cell 3020 or the third cell) being unknown may also be referred to as an unknown cell (e.g., unknown cell 3020 or the unknown third cell).

[0460] For example, the cell (e.g., cell 3020 or the third cell) may be known based on the wireless device may have met one or more cell criteria. In another example, the cell (e.g., cell 3020 or the third cell) may be unknown (or not known) based on the wireless device does not meet at least one of the one or more cell criteria

[0461] One of the one or more cell criteria may be that the wireless device has sent (e.g., to the node) a measurement report during a predetermined time, such as the last X31 seconds. In an example, the measurement report may comprise a measurement (e.g., a layer-3 measurement such as an RSRP, an RSRQ, an SINR, etc.). The measurement report may also be referred to as a layer-3 (L3) measurement report, a valid measurement report, or a valid L3 measurement report. In an example, X31 may depend on a frequency range (FR) of (or associated with) the cell (e.g., cell 3020 or the third cell). In an example, X31 may be a predetermined time, such as 5 seconds. In anotherDocket No.: 25-1051 PCTexample, X31 may be a predetermined time, such as 5 seconds for FR1 and 3 seconds for FR2. The FR, the FR1, and the FR2, may be implemented according to the example embodiments in FIG. 23 (e.g., NR frequency ranges 2300, FR1 2320, and FR22340).

[0462] Another one of the one or more cell criteria may be that, during a predetermined time, such as the last X31 seconds, a requirement associated with the cell (e.g., cell 3020 or the third cell) being met by the wireless device. In an example, the requirement may be referred to as a cell identification requirement. In example, the cell identification requirement may be referred to as an acquisition (or a detection) of a PCI of the cell (e.g., cell 3020 or the third cell). In example, the cell identification requirement may be referred to as synchronization with respect to the cell (e.g., cell 3020 or the third cell). The synchronization may be referred to as time and / or frequency synchronization.

[0463] The wireless device may receive a message (e.g., an RRC, a MAC-CE, etc.) indicating one or more TCI states of the serving cell. In an example, the TCI state of the serving cell may be associated with one or more channels (e.g., a PDSCH, a PDCCH, a PUSCH, or a PUCCH). The wireless device may transmit signals and / or receive signals in the serving cell based on the one or more channels. In an example, the TCI state may be known based on one or more TCI state criteria being met by the wireless device. In another example, the TCI state may be unknown based on at least one of the one or more TCI state criteria not being met by the wireless device.

[0464] One of the one or more TCI state criteria being that a TCI state switch command being received within a predetermined time, such asX32 ms (e.g., 1280 ms) upon the last transmission of a reference signal (e.g., an SSB) for a beam reporting or measurement. Another one of the one or more TCI state criteria being that the wireless device has sent at least one L1-RSRP report for the target TCI state before a reception (by the wireless device) of the TCI state switch command. Yet another one of the one or more TCI state criteria being that the TCI state remains detectable during a TCI state switching period. The RS (e.g., an SSB) associated with the TCI state may remain detectable during the TCI switching period based on that a signal quality (e.g., an SINR, an RSRQ, etc.) being larger than a signal quality threshold (e.g., -3 dB).

[0465] In an example, the MGP may be for performing a measurement, e.g., a positioning measurement, a mobility measurement, etc. The measurement may be implemented according to the example embodiments in FIG. 17 (e.g., measurement 1700). The MGP may also be referred to as a pre-configured MGP. In an example, an activation status of the MGP may be activated (or on or active) or deactivated (or off or inactive). The wireless device may perform the measurement based on (or using or during) the MGP while the activation status of the MGP is activated. The wireless device may not perform the measurement based on (or using or during) the MGP while the activation status of the MGP is deactivated.

[0466] In an example, based on UL message 3018, the wireless device may request the node, to change the activation status of the MGP, e.g., from activated to deactivated or vice versa. For example, UL message 3018 may be a MAC-CE (e.g., Positioning Measurement Gap Activation / Deactivation Request MAC CE). In an example, UL message 3018 may comprise an identifier of the MGP, a type of the MGP (e.g., a per UE MGP, a per FR MGP, etc.),Docket No.: 25-1051 PCTan identifier (e.g , a PCI, a CGI, a serving cell index (e.g., ServCellfndex), etc.) of cell 3020 or the third cell, etc. The MGP may be implemented according to the example embodiments in FIG. 18 (e.g., MGP 1800), in FIG. 20 (e.g., P-MGP 2000), and / or in FIG. 21 (e.g., NCSG pattern 2100).

[0467] In an example, the wireless device may transmit to the node, buffer status (or the buffer status report) based on the buffer status reporting (BSR) procedure, e.g., via a MAC-CE. The BSR may indicate information about (or associated with) uplink data volume in a MAC entity of the wireless device. The BSR may be associated with one or more channels (e.g., logical channels). In an example, the wireless device may transmit (or trigger) the BSR based on uplink data being available for one or more logical channels or logical channel groups (LCGs).

[0468] In another example, the wireless device may transmit (or trigger) the BSR based on uplink data being available for one or more logical channels being larger than a BSR threshold. In yet another example, the wireless device may transmit (or trigger) the BSR based on an expiry of a timer (e.g., retxBSR-Timer, periodicBSR-Timer, etc.) associated with the BSR. uplink data being available for one or more logical channels being larger than a BSR threshold.

[0469] In an example, the wireless device may transmit to the node, delay status (or the delay status report) based on the delay status reporting (DSR) procedure, e.g., via a MAC-CE. The DSR may indicate information about (or associated with) delay status of one or more logical channels or logical channel groups (LCGs). In an example, the wireless device may transmit (or trigger) the DSR based on that the remaining time of data (e.g., service data units (SDUs)) for LCGs being below a discard threshold (e.g., remainingTimeThreshold).

[0470] In an example, the out of range (OoR) report may also be referred to as an invalid report of a measurement (or an invalid measurement or an OoR measurement). For example, the wireless device may transmit to the node, the OoR report based on a measurement (e.g., a CQI, an L1-RSRP, an RSRP, an RSRQ, an RSTD, a PRS-RSRP, etc.) being below a first reportable threshold. In another example, the wireless device may transmit to the node, the OoR report based on the measurement being above a second reportable threshold. In another example, the wireless device may transmit to the node, the OoR report based on the measurement being (or may correspond to) the lowest reportable value.

[0471] In an example, a CQI value corresponding to the lowest index (e.g., index # 0) may correspond to (or indicate) the OoR report. In another example, an RSRP value above X41 dBm (e.g., -31 dBm) may correspond to the OoR report. In yet another example, an RSRP value below X42 dBm (e.g., -156 dBm) may correspond to the OoR report.

[0472] In an example, the wireless device may trigger a measurement event based on a measurement (e.g., an RSRP) and an event threshold. The wireless device may transmit the measurement event (e.g., an A2) based on (or in response to) the trigger. For example, wireless device may transmit the measurement event (e.g., an A2) based on the measurement on cell 3020 being below the event threshold.

[0473] The CG may be associated with a dual connectivity or a multi-connectivity The CG may be referred to as a master cell group (MCG) or a secondary cell group (SCG). In an example, the cell group (CG) may comprise (or beDocket No.: 25-1051 PCTassociated with) cell 3020 The CG may be an MCG or an SCG. The CG, the MCG, or the SCG may be implemented according to the example embodiments described above (e.g., the CG, the MCG, or the SCG).

[0474] In an example, the wireless device may detect the CG failure (e.g., an SCG failure) based on one or more CG failure criteria. Examples of the one or more CG failure criteria may be a radio link failure of a radio link associated with a special cell (SpCell) (e.g., a PCell or an PSCell), a beam failure of a beam associated with the spCell (e.g., while the CG being deactivated), a failure of reconfiguration of the CG with synchronization, a configuration failure of the CG, or an integrity check failure of the CG.

[0475] In an example, during time period 3052 and in response to UL message 3018, the wireless device may receive from the node, an uplink resource corresponding to the SR. In an example, during time period 3052, the wireless device may complete (or finish) a procedure associated with (or corresponding to) the operation For example, the wireless device may transmit to the node, an UL message (e.g., via cell 3010) on the uplink resource, to complete the procedure.

[0476] The procedure (corresponding to the operation) may comprise at least one of: a link failure recovery procedure; an activation of the measurement gap pattern (MGR); a deactivation (or release) of the MGR; a modification of one or more parameters of the MGP; a transmission of the buffer status report; a transmission of the delay status report; a transmission of the positioning measurement report; a transmission of the out of range (OoR) report; a transmission of the measurement event; and / or a transmission of the indication of cell group (CG) failure.

[0477] In an example, the link failure recovery procedure may be referred to as a beam failure recovery procedure, a link recovery procedure, or a radio link failure recovery procedure (e.g., an RRC connection re-establishment, etc.).

[0478] In an example, the UL message (e.g., Beam Failure Recovery MAC CE) may comprise (or include or indicate) an identifier of cell 3020 (e.g., a PCI, a serving cell index (e.g., ServCelllndex associated with a beam for which a beam failure is detected by the wireless device, an indication of the beam (e.g., an identifier of the beam or a reference signal associated with the beam), an indication of a candidate beam (e.g., an identifier of the beam or a reference signal associated with the beam), a measurement of the candidate beam (e.g., an L1-RSRP), etc.

[0479] In one example, time period 3052 may be pre-defined. For example, time period may be associated with (or depend on) the operation. In an example, time period 3052 may be based on the duration of the beam failure recovery procedure. For example, at time 3054, the wireless device may complete the beam failure recovery procedure. In another example, time period 3052 may be based on the activation of the MGP or the deactivation of the MGP. For example, time 3054 may be the end of a duration (e.g., a time resource, e.g., a slot, a subframe, etc.) in which the wireless device may receive, from the node, a MAC-CE indicating the activation or the deactivation of the MGP. In another example, time period 3052 may be based on the BSR or the DSR report. For example, time 3054 may be the end of a duration (e.g., a time resource) in which the wireless device may transmit (or send), to the node, the BSR report or the DSR report.Docket No.: 25-1051 PCT

[0480] In another example, the wireless device may receive time period 3052 from the node, e.g., via an RRC message. For example, the one or more configuration parameters may indicate time period 3052. In an example, time period 3052 maybe a timer, e.g., Z11 ms. In an example, time period 3052 may be a counter, e.g., Z12 number of time periods, of one or more time periods 3042. The wireless device may start the timer (or the counter) at time 3056 (e.g., when transmitting UL message 3018. The timer may expire at time 3054.

[0481] In an example, after time 3054 and during one or more time periods 3042, the wireless device may monitor 3024 signals 3026 on cell 3020. In another example, after time 3054 and during one or more time periods 3040, the wireless device may monitor 3014 signals 3016 on cell 3010. For example, after time 3054 and during one or more time periods 3042, the wireless device may not skip 3028 signals 3026 on cell 3020.

[0482] In an example, a medium access control (MAC) entity may be configured by RRC per Serving Cell or per beam failure detection reference signal (BFD-RS) set with a beam failure recovery (BFR) procedure. The BFR may be used by the wireless device for indicating to (or to indicate or to inform) the serving base station (e.g., a g N B) of new reference signals (e.g., a SSB ora CSI-RS) when a beam failure is detected (by the wireless device) on the serving SSB(s) / CSI-RS(s). The wireless device may detect the beam failure based on counting beam failure instance indication (eg., a number of beam failure detections) from the lower layers (e.g., a physical layer) to the MAC entity.

[0483] In an example, a time domain pattern (TD pattern) may be configured by an RRC for a PCell and an SCell of the wireless device. In an example, the wireless device may trigger the Beam Failure Recovery (BFR) procedure on (or for or related to or associated with) the serving cell (e.g., an SCell, a SpCell, a PSCell, etc.). The MAC entity may instruct (or indicate or request) the lower layer (e.g., the physical layer) to suspend reception on the SCell until the completion of the Beam Failure Recovery (BFR) procedure.

[0484] FIG. 31 illustrates an example of a multicarrier (MC) operation 3100 associated with a wireless device as per an aspect of an embodiment of the present disclosure. The wireless device may use MC operation 3100 for receiving signals from a cell 3110 and a cell 3120. MC operation 3100 may be implemented according to the example embodiments described above (e.g, the MC operation). The features illustrated in FIG. 31 maybe combined with any of the features previously discussed with reference to FIGs. 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, and / or 30.

[0485] As shown in FIG. 31 , the wireless device may be associated with cell 3110 operating on (or belonging to) a frequency 3112, and cell 3120 operating on (or belonging to) a frequency 3122. For example, cell 3110 and cell 3120 may be serving cells of the wireless device (e.g , in MC operation 3100). In an example, cell 3110 may be an SpCell (e.g., a PCell ora PSCell) and cell 3120 maybe an SCell. In another example, cell 3110 may be an SCell and cell 3120 may be an SpCell (e.g., a PCell or a PSCell). For example, the wireless device may communicate with a node via cell 3110 and cell 3120.

[0486] In an example, the node may be a RAN node. The RAN node may be implemented according to the example embodiments in FIG.30 (e.g., the RAN node).Docket No.: 25-1051 PCT

[0487] In an example, frequency 3112 of cell 3110 may be associated with (or belong to) a first band, and frequency 3122 of cell 3120 may be associated with (or belong to) a second band. Frequency 3112 and frequency 3122 may be indicated by (or addressed by) a frequency channel number (or a frequency channel identifier), e.g., an ARFCN, an NR-ARFCN, etc. Frequency 3112 and frequency 3122 may be downlink (DL) frequencies (or DL carrier frequencies). In an example, cell 3110 may also be associated with an uplink (UL) frequency, such as e.g., a first UL frequency (or a first UL carrier frequency). In another example, cell 3120 may also be associated with an UL frequency, such as e.g., a second UL frequency (ora second UL carrier frequency).

[0488] Frequency 3112, frequency 3122, the first UL frequency, and / or the second UL frequency, maybe implemented according to the example embodiments described above (e.g., the carrier frequency) and / or in FIG. 30 (eg., Frequency 3012, frequency 3022, the first UL frequency, and the second UL frequency). The first band, associated with frequency 3112, and the second band, associated with frequency 3122, may be implemented, according to the example embodiments in FIG.24A (e.g., FR1 bands 2420), FIG. 24B (e.g., FR2 bands 2440), and / or FIG. 30 (e.g., the first band and the second band).

[0489] In an example, the first band may be an FDD band, and the second band may be an SDL band. In another example, the first band may be an FDD band, and the second band may also be an FDD band. For example, the first band, the second band, and MC operation 3100 may be implemented according to the example embodiments in FIG.27 (e.g., band 2720, band 2780, and band combination 2700), FIG. 28 (e.g., band 2820, band 2880, and band combination 2800), FIG. 29 (e.g., band 2920, band 2980, and band combination 2900), and / or FIG. 30 (e.g., the first band, the second band, and MC operation 3000).

[0490] The wireless device may receive one or more configuration parameters from the node. For example, the wireless devices may receive one or more configuration parameters from the node via an RRC signaling, a MAC-CE, etc. The one or more configurati...

Claims

Docket No.: 25-1051 PCTCLAIMS1. A method comprising:receiving, by a wireless device, one or more configuration parameters indicating:first time periods for first downlink receptions via a first cell; andsecond time periods for second downlink receptions via a second cell;transmitting, via the first cell, a scheduling request indicating a beam failure of the second cell; determining a beam failure recovery, of the second cell, being completed at a second time; and during a time interval between a first time starting from the transmission of the scheduling request and the second time:cancelling and / or skipping the second downlink receptions via the second cell during one or more time periods of the second time periods; andmonitoring for and / or receiving the first downlink receptions via the first cell during the one or more time periods.

2. A method comprising:receiving, by a wireless device, one or more configuration parameters indicating:first time periods for first downlink receptions via a first cell; andsecond time periods for second downlink receptions via a second cell; andmonitoring for and / or receiving the first downlink receptions via the first cell during one or more time periods of the second time periods.

3. The method of claim 2, further comprising cancelling and / or skipping the second downlink receptions via the second cell during the one or more time periods of the second time periods.

4. The method of claim 2 or 3, wherein, during a time interval between a first time starting from a transmission of a scheduling request and a second time:the first downlink receptions via the first cell are monitored for and / or received during the one or more time periods of the second time periods; and / orthe second downlink receptions via the second cell are cancelled and / or skipped during the one or more time periods of the second time periods.

5. The method of claim 4, further comprising determining a beam failure recovery, of the second cell, being completed at the second time.

6. The method of claim 4 or 5, further comprising transmitting, via the first cell, the scheduling request indicating a beam failure of the second cell.

7. The method of claim 6, further comprising completing a beam failure recovery procedure, for the beam failure of the second cell, during the time interval or at the second time.

8. The method of any one of claims 4-7, further comprising monitoring for and / or receiving:Docket No.: 25-1051 PCTthe first downlink receptions via the first cell during at least one first time period of the first time periods; and the second downlink receptions via the second cell during at least one second time period of the second time periods.

9. The method of any one of claims 2-8, wherein:the first cell is a special cell (SpCell); andthe second cell is a secondary cell (SCell).

10. The method of any one of claims 2-9, wherein:the first cell is associated with a frequency division duplex (FDD) operation, andthe second cell is associated with a supplemental downlink operation;the first cell and the second cell are associated with a frequency division duplex (FDD) operation;the first cell and the second cell are associated with a multicarrier (MC) operation that is one of a carrier aggregation, a dual connectivity, or a multi-connectivity.

11. The method of any one of claims 2-10, wherein:the one or more configuration parameters are received from a node;the node is a base station, a gNode B, a gNodeB-central unit (gNode B-CU), or a g NodeB-distribution unit (gNode B-DU).

12. The method of any one of claims 2-11 , wherein receiving the one or more configuration parameters comprises receiving one, of a radio resource control (RRC) message, a medium access control (MAC) control element (CE) message, ora downlink control information (DCI) message, comprising the one or more configuration parameters.

13. The method of any one of claims 4-12, wherein the scheduling request comprises a MAC CE message.

14. The method of any one of claims 4-13, wherein:the scheduling request is transmitted via an uplink control channel or an uplink data channel; and the uplink control channel is a physical uplink control channel (PUCCH) ora physical uplink shared channel (PUSCH).

15. The method of any one of claims 2-14, wherein:the first downlink receptions comprise at least one of a downlink data channel or a downlink control channel; the second downlink receptions comprise at least one of a downlink data channel or a downlink control channel; the downlink data channel is a physical downlink shared channel (PDSCH); andthe downlink control channel is a physical downlink control channel (PDCCH).

16. A method comprising:receiving, by a wireless device, one or more configuration parameters indicating:first time periods for first downlink receptions via a first cell; andsecond time periods for second downlink receptions via a second cell;based on a measurement on the first cell, determining a radio link problem on the first cell;Docket No.: 25-1051 PCTbased on the determining:cancelling and / or skipping the second downlink receptions via the second serving cell during at least one second time period of the second time periods; andmonitoring for and / or receiving the first downlink receptions via the first cell during the at least one second time period of the second time periods; andtransmitting an uplink signal indicating the radio link problem, wherein the uplink signal comprises at least one of:a measurement report triggered based on one or more measurement events;an out-of-range report of the first cell; and / ora link failure report of the first cell.

17. A method comprising:receiving, by a wireless device, one or more configuration parameters indicating:first time periods for first downlink receptions via a first cell; andsecond time periods for second downlink receptions via a second cell;determining a radio link problem on the first cell; andbased on the determining, cancelling and / or skipping the second downlink receptions via the second cell during at least one second time period of the second time periods.

18. The method of claim 17, further comprising, based on the determining, monitoring for and / or receiving the first downlink receptions via the first cell during the at least one second time period of the second time periods.

19. The method of claim 17 or 18, wherein the radio link problem on the first cell is determined, based on a measurement on the first cell.

20. The method of any one of claims 17-19, further comprising transmitting an uplink signal indicating the radio link problem.

21. The method of claim 20, wherein the uplink signal comprises at least one of:a measurement report triggered based on one or more measurement events;an out-of-range report of the first cell; and / ora link failure report of the first cell.

22. The method of any one of claims 17-21, further comprising monitoring for and / or receiving one or more signals via a third cell during the at least one second time period of the second time periods.

23. The method of any one of claims 20-22, wherein:the uplink signal is transmitted at a first time; andthe at least one second time period is between the first time and a second time.Docket No.: 25-1051 PCT24. The method of any one of claims 17-23, further comprising monitoring for and / or receiving the first downlink receptions via the first cell during at least one first time period of the first time periods, wherein the at least one first time period is during the time interval.

25. The method of claim 23 or 24, further comprising, after the second time, monitoring for and / or receiving:the first downlink receptions via the first cell during at least one first time period of the first time periods; and the second downlink receptions via the second cell during at least one second time period of the second time periods.

26. The method of any one of claims 17-25, wherein:the one or more configuration parameters indicate:third time periods for the first downlink receptions via the first cell; andfourth time periods for the second downlink receptions via the second cell;the third time periods comprise the at least one second time period; andthe fourth time periods do not comprise the at least one second time period.

27. The method of claim 26, further comprising, during the time interval, monitoring for and / or receiving:the first downlink receptions via the first cell during at least one first time period of the third time periods; and the second downlink receptions via the second cell during at least one second time period of the fourth time periods.

28. The method of any one of claims 17-27, further comprising:transmitting a first report triggered based on a measurement of the second cell; andbased on the transmitting and during at least one third time period of the second time periods, cancelling and / or skipping the second downlink receptions via the second cell during the at least one third time period of the second time periods, wherein the first report comprises / indicates / associated with at least one of:a measurement report triggered based on one or more measurement events;an out of range report of the first cell; and / ora link failure of the first cell.

29. The method of claim 28, further comprising monitoring for and / or receiving the first downlink receptions via the first cell during the at least one third time period of the second time periods.

30. The method of claim 28 or 29, further comprising monitoring for and / or receiving first signals via a fourth cell during the at least one third time period of the second time periods.

31. The method of any of claims 28-30, wherein:the first report is transmitted at a third time; andthe at least one third time period is during a first time interval between the third time and a fourth time.Docket No.: 25-1051 PCT32. The method of claim 31 , further comprising monitoring for and / or receiving the first downlink receptions via the first cell during at least one first time period of the first time periods, wherein the at least one first time period is during the first time interval.

33. The method of claim 31 or 32, further comprising, after the fourth time, monitoring for and / or receiving:the first downlink receptions via the first cell during at least one first time period of the first time periods; and the second downlink receptions via the second cell during at least one second time period of the second time periods.

34. The method of any one of claims 17-33, wherein:the first cell is a special cell (SpCell) associated with a frequency division duplex (FDD) operation; and the second cell is a secondary cell (SCell) associated with a supplemental downlink operation or the FDD operation.

35. The method of any one of claims 30-34, wherein:the third cell is a neighbor cell or a non-serving cell; andthe fourth cell is a neighbor cell or a non-serving cell.

36. A method comprising:receiving, by a wireless device, one or more configuration parameters indicating:first time periods for first downlink receptions via a first cell;second time periods for second downlink receptions via a second cell; andthird time periods for third downlink receptions via a third cell;transmitting an uplink signal;based on transmitting the uplink signal, determining, fora response corresponding to the uplink signal, to cancel or skip one or more downlink receptions during one or more time periods among:the second downlink receptions via the second cell during at least one second time period of the second time periods; and / orthe third downlink receptions via the third cell during at least one third time period of the third time periods; andbased on the determining, receiving the response via the first cell during the one or more time periods, wherein the response is received via the first cell during the at least one second time period and / or the at least one third time period.

37. The method of claim 36, further comprising:receiving, from a node, a message comprising at least one of an identifier of cell, an index of cell, an identifier of frequency band, a frequency channel number, or a bit map; anddetermining, based on the message, whether to cancel and / or skip:the second downlink receptions via the second cell during the at least one second time period; and / orDocket No.: 25-1051 PCTthe third downlink receptions via the third cell during the at least one third time period.

38. The method of claim 36 or 37, further comprising:determining, based on a pre-defined rule, whether to cancel and / or skip:the second downlink receptions via the second cell during the at least one second time period; and / or the third downlink receptions via the third cell during the at least one third time period, wherein the predefined rule is associated with at least one of a bandwidth, a frequency band, a frequency range, a bandwidth of an active bandwidth part, a type of reference signal, or a type of cell; andcancelling / skipping:the second downlink receptions via the second cell during the at least one second time period, wherein a first bandwidth of the second cell is larger than a second bandwidth of the third cell; orthe third downlink receptions via the third cell during the at least one third time period, wherein the second bandwidth of the third cell is larger than the first bandwidth of the second cell.

39. The method of any one of claims 36-38, further comprising cancelling and / or skipping one or more of:the second downlink receptions via the second cell during the at least one second time period, wherein the at least one second time period is longer than the at least one third time period;the third downlink receptions via the third cell during the at least one third time period, wherein the at least one third time period is longer than the at least one second time period;the second downlink receptions via the second cell during the at least one second time period, wherein the at least one second time period starts before the at least one third time period; orthe third downlink receptions via the third cell during the at least one third time period, wherein the at least one third time period starts before the at least one second time period.

40. The method of any one of claims 36-39, wherein:the uplink signal is at least one of a preamble, an uplink control channel, or an uplink data channel;the uplink signal is for an operation associated with the first cell, the second cell, third cell, or a fourth cell; the operation comprises / indicates at least one of:a scheduling request to request an uplink resource;a beam failure;a candidate beam detection;a radio link failure;an expiry of a timer;an invalidity of a timing advance;a request for a measurement gap pattern (MG P);a request to release the MGP;a request for an activation of the MGP;Docket No.: 25-1051 PCTa request for a deactivation of the MGP;an unknown transmission control indication (TCI) state; ora cell group failure.

41. The method of any one of claims 36-40, wherein:the uplink signal is transmitted is at a first time;the response is received at a second time;a procedure associated with the operation is completed during a time interval between the first time and the second time; andthe procedure comprises / indicates at least one of:a beam failure recovery;an activation of a measurement gap pattern (MGP);a deactivation / release of the MGP;a modification of one or more parameters of the MGP;a transmission of a buffer status report;a transmission of a delay status report;a transmission of a positioning measurement report;a transmission of an out of range report;a transmission of a measurement event;a transmission of an indication of unknown transmission control indication (TCI) state; and / or a transmission of an indication of cell group failure.

42. The method of any one of claims 36-41, wherein:the response is a random access response, a downlink control channel, or a downlink data channel; the response indicates at least one of a beam, a reference signal, an uplink grant, a timing advance command, duration of a timer, an identifier of a cell, a transmission control indication (TCI) state, an identifier of a measurement gap pattern (MGP), an activation of the MGP, or a deactivation of the MGP; andthe response is received during the time interval.

43. The method of claim 41 or 42, further comprising, after the second time, monitoring for and / or receiving:the first downlink receptions via the first cell during at least one first time period of the first time periods; the second downlink receptions via the second cell during at least one second time period of the second time periods; and / orthe third downlink receptions via the third cell during at least one third time period of the third time periods.

44. An apparatus comprising:one or more processors; andDocket No.: 25-1051 PCTmemory storing instructions that, when executed by the one or more processors, cause the apparatus to perform the method of any one of claims 1-43.

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

Images