Enhancements to musim procedures

Abstract

A method for wireless communication at a user equipment (UE) and related apparatus are provided. In the method, the UE selects, based on a tune away gap of an original carrier overlapping with an uplink transmission of the UE, one secondary component carrier (SCC) from one or more candidate SCCs of the UE. The UE further transmits, to a network entity, a medium access control (MAC) – control element (MACCE) including a request for a change of an uplink carrier of the uplink transmission from the original carrier to the one SCC.

Description

ENHANCEMENTS TO MUSIM PROCEDURESCROSS-REFERENCE TO RELATED APPLICATION

[0001] This application claims the benefit of U.S. Non-Provisional Patent Application Serial No. 18 / 737,497, entitled “ENHANCEMENTS TO MUSIM PROCEDURES” and filed on June 7, 2024, which is expressly incorporated by reference herein in its entirety.TECHNICAL FIELD

[0002] The present disclosure relates generally to communication systems and, more particularly, to the enhancements to multi -universal subscriber identity module (MUSIM) procedures in wireless communication.INTRODUCTION

[0003] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0004] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3 GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massivemachine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There exists a need for further improvements in 5G NR technology. These improvements may also be applicable to other multi-access technologies and the telecommunication standards that employ these technologies.BRIEF SUMMARY

[0005] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects. This summary neither identifies key or critical elements of all aspects nor delineates the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

[0006] In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided for wireless communication at a user equipment (UE). The apparatus may include at least one memory and at least one processor coupled to the at least one memory. Based at least in part on information stored in the at least one memory, the at least one processor, individually or in any combination, may be configured to select, based on a tune away gap of an original carrier overlapping with an uplink transmission of the UE, one secondary component carrier (SCC) from one or more candidate SCCs of the UE; and transmit, to a network entity, a medium access control (MAC) - control element (MAC-CE) including a request for the change of an uplink carrier of the uplink transmission from the original carrier to the one SCC.

[0007] In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided for wireless communication at a network entity. The apparatus may include at least one memory and at least one processor coupled to the at least one memory. Based at least in part on information stored in the at least one memory, the at least one processor, individually or in any combination, may be configured to receive, from a UE, a MAC-CE including a request for the change of an uplink carrier for an uplink transmission from an original carrier to an SCC; and communicate with the UE based on the request in the MAC-CE.

[0008] To the accomplishment of the foregoing and related ends, the one or more aspects may include the features hereinafter fully described and particularly pointed out in theclaims. The following description and the drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed.BRIEF DESCRIPTION OF THE DRAWINGS

[0009] FIG. l is a diagram illustrating an example of a wireless communication system and an access network.

[0010] FIG. 2A is a diagram illustrating an example of a first frame, in accordance with various aspects of the present disclosure.

[0011] FIG. 2B is a diagram illustrating an example of downlink (DL) channels within a subframe, in accordance with various aspects of the present disclosure.

[0012] FIG. 2C is a diagram illustrating an example of a second frame, in accordance with various aspects of the present disclosure.

[0013] FIG. 2D is a diagram illustrating an example of uplink (UL) channels within a subframe, in accordance with various aspects of the present disclosure.

[0014] FIG. 3 is a diagram illustrating an example of a base station and user equipment (UE) in an access network.

[0015] FIG. 4 is a diagram illustrating an example of uplink transmission disruptions due to the tune away gaps.

[0016] FIG. 5 is a diagram illustrating an example of an uplink carrier change in accordance with various aspects of the present disclosure.

[0017] FIG. 6 is a diagram illustrating an example of an uplink carrier change in accordance with various aspects of the present disclosure.

[0018] FIG. 7 is a call flow diagram illustrating a method of wireless communication in accordance with various aspects of the present disclosure.

[0019] FIG. 8 is a flowchart illustrating methods of wireless communication at a UE in accordance with various aspects of the present disclosure.

[0020] FIG. 9 is a flowchart illustrating methods of wireless communication at a network entity in accordance with various aspects of the present disclosure.

[0021] FIG. 10 is a diagram illustrating an example of a hardware implementation for an example apparatus and / or UE.

[0022] FIG. 11 is a diagram illustrating an example of a hardware implementation for an example network entity.DETAILED DESCRIPTION

[0023] To accommodate the rapidly growing mobile data usage and the demand for higher downlink (DL) and uplink (UL) throughputs, driven by end-user needs for services such as video calls, streaming services, and 4K content, the network operators are deploying higher order carrier configurations, enabling devices in connected mode to access multiple carriers. For example, the multi-universal subscriber identity module (MUSIM) operation modes have been widely adopted in mobile devices to improve the user experience. In MUSIM operation mode, user equipment (UE) may share the available radio frequency (RF) and modem resources between the dedicated (or default) data subscription (DDS) subscription operating in connected mode and the non-dedicated data subscription (non-DDS or n-DDS) subscription operating in idle mode. However, during page decoding, tune away (TA) gaps may occur in the n-DDS subscription, which may interrupt data flow on the DDS subscription. Example aspects presented herein provide methods and apparatus for improving MUSIM procedures in the presence of TA gaps.

[0024] Various aspects relate generally to wireless communication. Some aspects more specifically relate to the enhancements to MUSIM procedures in wireless communication. In some examples, the UE may select, based on a tune away gap of an original carrier overlapping with an uplink transmission of the UE, one secondary component carrier (SCC) from one or more candidate SCCs of the UE. The UE further transmits, to a network entity, a medium access control (MAC) - control element (MAC-CE) including a request for the change of an uplink carrier of the uplink transmission from the original carrier to the one SCC. In some aspects, the UE may select one or more compatible SCCs from the one or more candidate SCCs, where the one or more compatible SCCs are uplink capable and lack the tune away gap overlapping with the uplink transmission, and the UE may further select, based on a selection criterion for each compatible SCC of the one or more compatible SCCs, the one SCC from the one or more compatible SCCs.

[0025] Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In someexamples, by enabling the UE to request network reconfiguration and move the uplink to a carrier without resource conflicts due to the tune away, the described techniques may be used to minimize interruptions in uplink transmissions that may occur due to the tune away and avoid the data drops in channel state feedback (CSF), uplink control information (UCI), and sounding reference signals (SRSs), thereby maintaining a high DL and UL throughput in wireless communication.

[0026] The detailed description set forth below in connection with the drawings describes various configurations and does not represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

[0027] Several aspects of telecommunication systems are presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements”). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

[0028] By way of example, an element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes one or more processors. When multiple processors are implemented, the multiple processors may perform the functions individually or in combination. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software. Software, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise, shall be construed broadlyto mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.

[0029] Accordingly, in one or more example aspects, implementations, and / or use cases, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer. By way of example, such computer-readable media can include a random-access memory (RAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the types of computer- readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.

[0030] While aspects, implementations, and / or use cases are described in this application by illustration to some examples, additional or different aspects, implementations and / or use cases may come about in many different arrangements and scenarios. Aspects, implementations, and / or use cases described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, aspects, implementations, and / or use cases may come about via integrated chip implementations and other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, artificial intelligence (Al)-enabled devices, etc.). While some examples may or may not be specifically directed to use cases or applications, a wide assortment of applicability of described examples may occur. Aspects, implementations, and / or use cases may range a spectrum from chip-level or modular components to non-modular, non-chip- level implementations and further to aggregate, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more techniques herein. In some practical settings, devices incorporating described aspects and features may also include additional components and features for implementation and practice of claimed and described aspect. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes(e.g., hardware components including antenna, RF-chains, power amplifiers, modulators, buffer, processor(s), interleaver, adders / summers, etc.). Techniques described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc. of varying sizes, shapes, and constitution.

[0031] Deployment of communication systems, such as 5GNR systems, may be arranged in multiple manners with various components or constituent parts. In a 5G NR system, or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element, or a network equipment, such as a base station (BS), or one or more units (or one or more components) performing base station functionality, may be implemented in an aggregated or disaggregated architecture. For example, a BS (such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), a transmission reception point (TRP), or a cell, etc.) may be implemented as an aggregated base station (also known as a standalone BS or a monolithic BS) or a disaggregated base station.

[0032] An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other RAN nodes. The DUs may be implemented to communicate with one or more RUs. Each of the CU, DU and RU can be implemented as virtual units, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0033] Base station operation or network design may consider aggregation characteristics of base station functionality. For example, disaggregated base stations may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O- RAN (such as the network configuration sponsored by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Disaggregation may include distributing functionality across two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network design. The various units of thedisaggregated base station, or disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit.

[0034] FIG. 1 is a diagram 100 illustrating an example of a wireless communications system and an access network. The illustrated wireless communications system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that can communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated base station units (such as a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) 125 via an E2 link, or a Non-Real Time (Non-RT) RIC 115 associated with a Service Management and Orchestration (SMO) Framework 105, or both). A CU 110 may communicate with one or more DUs 130 via respective midhaul links, such as an Fl interface. The DUs 130 may communicate with one or more RUs 140 via respective fronthaul links. The RUs 140 may communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, the UE 104 may be simultaneously served by multiple RUs 140.

[0035] Each of the units, i.e., the CUs 110, the DUs 130, the RUs 140, as well as the Near- RT RICs 125, the Non-RT RICs 115, and the SMO Framework 105, may include one or more interfaces or be coupled to one or more interfaces configured to receive or to transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or to transmit signals over a wired transmission medium to one or more of the other units. Additionally, the units can include a wireless interface, which may include a receiver, a transmitter, or a transceiver (such as an RF transceiver), configured to receive or to transmit signals, or both, over a wireless transmission medium to one or more of the other units.

[0036] In some aspects, the CU 110 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 110. The CU 110 may be configured to handle user plane functionality (i.e., Central Unit - User Plane(CU-UP)), control plane functionality (i.e., Central Unit - Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 110 can be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as an El interface when implemented in an O-RAN configuration. The CU 110 can be implemented to communicate with the DU 130, as necessary, for network control and signaling.

[0037] The DU 130 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 140. In some aspects, the DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, demodulation, or the like) depending, at least in part, on a functional split, such as those defined by 3 GPP. In some aspects, the DU 130 may further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 130, or with the control functions hosted by the CU 110.

[0038] Lower-layer functionality can be implemented by one or more RUs 140. In some deployments, an RU 140, controlled by a DU 130, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like), or both, based at least in part on the functional split, such as a lower layer functional split. In such an architecture, the RU(s) 140 can be implemented to handle over the air (OTA) communication with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU(s) 140 can be controlled by the corresponding DU 130. In some scenarios, this configuration can enable the DU(s) 130 and the CU 110 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0039] The SMO Framework 105 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements that may be managed via an operations and maintenance interface (such as an 01 interface).For virtualized network elements, the SMO Framework 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an 02 interface). Such virtualized network elements can include, but are not limited to, CUs 110, DUs 130, RUs 140 and Near-RT RICs 125. In some implementations, the SMO Framework 105 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O- eNB) 111, via an 01 interface. Additionally, in some implementations, the SMO Framework 105 can communicate directly with one or more RUs 140 via an 01 interface. The SMO Framework 105 also may include a Non-RT RIC 115 configured to support functionality of the SMO Framework 105.

[0040] The Non-RT RIC 115 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence (Al) / machine learning (ML) (AI / ML) workflows including model training and updates, or policy-based guidance of applications / features in the Near- RT RIC 125. The Non-RT RIC 115 may be coupled to or communicate with (such as via an Al interface) the Near-RT RIC 125. The Near-RT RIC 125 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 110, one or more DUs 130, or both, as well as an O-eNB, with the Near-RT RIC 125.

[0041] In some implementations, to generate AI / ML models to be deployed in the Near-RT RIC 125, the Non-RT RIC 115 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 125 and may be received at the SMO Framework 105 or the Non-RT RIC 115 from non-network data sources or from network functions. In some examples, the Non-RT RIC 115 or the Near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 115 may monitor long-term trends and patterns for performance and employ AI / ML models to perform corrective actions through the SMO Framework 105 (such as reconfiguration via 01) or via creation of RAN management policies (such as Al policies).

[0042] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Accordingly, a base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component indicated with dotted lines to signifythat each component may or may not be included in the base station 102). The base station 102 provides an access point to the core network 120 for a UE 104. The base station 102 may include macrocells (high power cellular base station) and / or small cells (low power cellular base station). The small cells include femtocells, picocells, and microcells. A network that includes both small cell and macrocells may be known as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs), which may provide service to a restricted group known as a closed subscriber group (CSG). The communication links between the RUs 140 and the UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to an RU 140 and / or downlink (DL) (also referred to as forward link) transmissions from an RU 140 to a UE 104. The communication links may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication links may be through one or more carriers. The base station 102 / UEs 104 may use spectrum up to X MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Ex MHz (x component carriers) used for transmission in each direction. The carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL). The component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell).

[0043] Certain UEs 104 may communicate with each other using device-to-device (D2D) communication link 158. The D2D communication link 158 may use the DL / UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be through a variety of wireless D2D communications systems, such as for example, Bluetooth™ (Bluetooth is a trademark of the Bluetooth Special Interest Group (SIG)), Wi-Fi™ (Wi-Fi is a trademark of the Wi-Fi Alliance) based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0044] The wireless communications system may further include a Wi-Fi AP 150 in communication with UEs 104 (also referred to as Wi-Fi stations (STAs)) via communication link 154, e.g., in a 5 GHz unlicensed frequency spectrum or the like. When communicating in an unlicensed frequency spectrum, the UEs 104 / AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.

[0045] The electromagnetic spectrum is often subdivided, based on frequency / wavelength, into various classes, bands, channels, etc. In 5GNR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.

[0046] The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified an operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz - 24.25 GHz). Frequency bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, and thus may effectively extend features of FR1 and / or FR2 into midband frequencies. In addition, higher frequency bands are currently being explored to extend 5GNR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6 GHz - 71 GHz), FR4 (71 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0047] With the above aspects in mind, unless specifically stated otherwise, the term “sub-6 GHz” or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, the term “millimeter wave” or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

[0048] The base station 102 and the UE 104 may each include a plurality of antennas, such as antenna elements, antenna panels, and / or antenna arrays to facilitate beamforming.The base station 102 may transmit a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also transmit a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102 / UE 104 may perform beam training to determine the best receive and transmit directions for each of the base station 102 / UE 104. The transmit and receive directions for the base station 102 may or may not be the same. The transmit and receive directions for the UE 104 may or may not be the same.

[0049] The base station 102 may include and / or be referred to as a gNB, Node B, eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a TRP, network node, network entity, network equipment, or some other suitable terminology. The base station 102 can be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, an aggregated (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and an RU, or as a disaggregated base station including one or more of a CU, a DU, and / or an RU. The set of base stations, which may include disaggregated base stations and / or aggregated base stations, may be referred to as next generation (NG) RAN (NG-RAN).

[0050] The core network 120 may include an Access and Mobility Management Function (AMF) 161, a Session Management Function (SMF) 162, a User Plane Function (UPF) 163, a Unified Data Management (UDM) 164, one or more location servers 168, and other functional entities. The AMF 161 is the control node that processes the signaling between the UEs 104 and the core network 120. The AMF 161 supports registration management, connection management, mobility management, and other functions. The SMF 162 supports session management and other functions. The UPF 163 supports packet routing, packet forwarding, and other functions. The UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identification handling, access authorization, and subscription management. The one or more location servers 168 are illustrated as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. However, generally, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, theLMF 166, a position determination entity (PDE), a serving mobile location center (SMLC), a mobile positioning center (MPC), or the like. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) for accessing UE positioning information. The LMF 166 receives measurements and assistance information from the NG-RAN and the UE 104 via the AMF 161 to compute the position of the UE 104. The NG-RAN may utilize one or more positioning methods in order to determine the position of the UE 104. Positioning the UE 104 may involve signal measurements, a position estimate, and an optional velocity computation based on the measurements. The signal measurements may be made by the UE 104 and / or the base station 102 serving the UE 104. The signals measured may be based on one or more of a satellite positioning system (SPS) 170 (e.g., one or more of a Global Navigation Satellite System (GNSS), global position system (GPS), non-terrestrial network (NTN), or other satellite position / location system), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., barometric pressure sensor, motion sensor), NR enhanced cell ID (NRE-CID) methods, NR signals (e.g., multi -round trip time (Multi -RTT), DL angle- of-departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle-of-arrival (UL-AoA) positioning), and / or other systems / signals / sensors.

[0051] Examples of UEs 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, or any other similar functioning device. Some of the UEs 104 may be referred to as loT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc.). The UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more companion devices such as ina device constellation arrangement. One or more of these devices may collectively access the network and / or individually access the network.

[0052] Referring again to FIG. 1, in certain aspects, the UE 104 may include an uplink reconfiguration component 198. The uplink reconfiguration component 198 may be configured to select, based on a tune away gap of an original carrier overlapping with an uplink transmission of the UE, one secondary component carrier (SCC) from one or more candidate SCCs of the UE; and transmit, to a network entity, a medium access control (MAC) - control element (MAC-CE) including a request for a change of an uplink carrier of the uplink transmission from the original carrier to the one SCC. In certain aspects, the base station 102 may include an uplink reconfiguration component 199. The uplink reconfiguration component 199 may be configured to receive, from a user equipment (UE), a MAC-CE including a request for a change of an uplink carrier for an uplink transmission from an original carrier to an SCC; and communicate with the UE based on the request in the MAC-CE. Although the following description may be focused on 5G NR, the concepts described herein may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0053] FIG. 2A is a diagram 200 illustrating an example of a first subframe within a 5G NR frame structure. FIG. 2B is a diagram 230 illustrating an example of DL channels within a 5G NR subframe. FIG. 2C is a diagram 250 illustrating an example of a second subframe within a 5G NR frame structure. FIG. 2D is a diagram 280 illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplexed (FDD) in which for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated for either DL or UL, or may be time division duplexed (TDD) in which for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated for both DL and UL. In the examples provided by FIGs. 2A, 2C, the 5G NR frame structure is assumed to be TDD, with subframe 4 being configured with slot format 28 (with mostly DL), where D is DL, U is UL, and F is flexible for use between DL / UL, and subframe 3 being configured with slot format 1 (with all UL). While subframes 3, 4 are shown with slot formats 1, 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0, 1 are all DL, UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. UEs are configured with the slotformat (dynamically through DL control information (DCI), or semi- statically / statically through radio resource control (RRC) signaling) through a received slot format indicator (SFI). Note that the description infra applies also to a 5G NR frame structure that is TDD.

[0054] FIGs. 2A-2D illustrate a frame structure, and the aspects of the present disclosure may be applicable to other wireless communication technologies, which may have a different frame structure and / or different channels. A frame (10 ms) may be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include mini-slots, which may include 7, 4, or 2 symbols. Each slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each slot may include 14 symbols, and for extended CP, each slot may include 12 symbols. The symbols on DL may be CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. The symbols on LTL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (for power limited scenarios; limited to a single stream transmission). The number of slots within a subframe is based on the CP and the numerology. The numerology defines the subcarrier spacing (SCS) (see Table 1). The symbol length / duration may scale with 1 / SCS.Table 1: Numerology, SCS, and CP

[0055] For normal CP (14 symbols / slot), different numerologies p 0 to 4 allow for 1, 2, 4, 8, and 16 slots, respectively, per subframe. For extended CP, the numerology 2 allows for 4 slots per subframe. Accordingly, for normal CP and numerology p, there are 14symbols / slot and 2“ slots / subframe. The subcarrier spacing may be equal to 2 * 15 kHz, where is the numerology 0 to 4. As such, the numerology p=0 has a subcarrier spacing of 15 kHz and the numerology p=4 has a subcarrier spacing of 240 kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIGs. 2A-2D provide an example of normal CP with 14 symbols per slot and numerology p=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 ps. Within a set of frames, there may be one or more different bandwidth parts (BWPs) (see FIG. 2B) that are frequency division multiplexed. Each BWP may have a particular numerology and CP (normal or extended).

[0056] A resource grid may be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs)) that extends 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0057] As illustrated in FIG. 2A, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include demodulation RS (DM-RS) (indicated as R for one particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. The RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0058] FIG. 2B illustrates an example of various DL channels within a subframe of a frame. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within one BWP may be referred to as a control resource set (CORESET). A UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., common search space, UE-specific search space) during PDCCH monitoring occasions on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at greater and / or lower frequencies across the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of particular subframes of a frame. The PSS is used by a UE 104 to determine subframe / symbol timing and a physical layer identity. A secondary synchronization signal (SSS) may be within symbol 4 of particular subframes of a frame. The SSS is used by a UE to determine aphysical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI). Based on the PCI, the UE can determine the locations of the DM-RS. The physical broadcast channel (PBCH), which carries a master information block (MIB), may be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as SS block (SSB)). The MIB provides a number of RBs in the system bandwidth and a system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as system information blocks (SIBs), and paging messages.

[0059] As illustrated in FIG. 2C, some of the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may transmit DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH). The PUSCH DM-RS may be transmitted in the first one or two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether short or long PUCCHs are transmitted and depending on the particular PUCCH format used. The UE may transmit sounding reference signals (SRS). The SRS may be transmitted in the last symbol of a subframe. The SRS may have a comb structure, and a UE may transmit SRS on one of the combs. The SRS may be used by a base station for channel quality estimation to enable frequencydependent scheduling on the UL.

[0060] FIG. 2D illustrates an example of various UL channels within a subframe of a frame. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACK and / or negative ACK (NACK)). The PUSCH carries data, and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0061] FIG. 3 is a block diagram of a base station 310 in communication with a UE 350 in an access network. In the DL, Internet protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIBs), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0062] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding / decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The TX processor 316 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signaland / or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier with a respective spatial stream for transmission.

[0063] At the UE 350, each receiver 354Rx receives a signal through its respective antenna 352. Each receiver 354Rx recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they may be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions may be based on channel estimates computed by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 310 on the physical channel. The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functionality.

[0064] The controller / processor 359 can be associated with at least one memory 360 that stores program codes and data. The at least one memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0065] Similar to the functionality described in connection with the DL transmission by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression / decompression, and security (ciphering, deciphering, integrityprotection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0066] Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antenna 352 via separate transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a respective spatial stream for transmission.

[0067] The UL transmission is processed at the base station 310 in a manner similar to that described in connection with the receiver function at the UE 350. Each receiver 318Rx receives a signal through its respective antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to a RX processor 370.

[0068] The controller / processor 375 can be associated with at least one memory 376 that stores program codes and data. The at least one memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0069] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform aspects in connection with the uplink reconfiguration component 198 of FIG. 1.

[0070] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform aspects in connection with the uplink reconfiguration component 199 of FIG. 1.

[0071] Example aspects presented herein provide methods and apparatus that enable a UE to use a MAC-CE to indicate whether there is an UL transmission collision on a DDS component carrier (CC) over which n-DDS paging is monitored for MUSIMoperations. If such a collision will occur, the UE may autonomously move the UL configuration to another DDS CC so that the UL outage due to the collision to n-DDS paging monitoring may be avoided.

[0072] The mobile data usage and the demand for higher downlink (DL) and uplink (UL) throughputs, driven by end-user needs for services such as video calls, streaming services, and 4K content, have been growing rapidly. In response, the network operators are implementing higher order carrier configurations, enabling devices in connected mode to access multiple carriers. For example, the multi -universal subscriber identity module (MUSIM) operation modes have been widely adopted in mobile services to improve the user experiences. In MUSIM operation mode, user equipment (UE) may share the available radio frequency (RF) and modem resources between the DDS subscription operating in connected mode and the non-DDS (n- DDS) subscription operating in idle mode.

[0073] In MUSIM operation mode, a tune away (TA) gap may refer to a time period during which a UE temporarily switches away from its current communication channel or frequency to perform another operation without dropping the connection. For example, the TA gaps may occur in the non-DDS subscription (n-DDS Sub) to perform page decoding. This tune away gap, however, may interrupt data flow on the DDS subscription (DDS Sub).

[0074] FIG. 4 is a diagram 400 illustrating an example of uplink transmission disruptions due to the tune away gaps. As shown in FIG. 4, a DDS subscription (e.g., DDS 402) may be operating in higher order carrier configurations in both downlink (DL) and uplink (UL), such as configurations involving multiple carrier aggregation (CA) scenarios including 4 DL CA and 2 UL CA. For example, the DDS 402 may be operating with a primary component carrier (e.g., PCC 412) for DL and UL, a first secondary CC (e.g., SCC1 414) for DL and UL, a second secondary CC (e.g., SCC2 416) for DL, and a third secondary CC (e.g., SCC3 418) for DL, and the n-DDS Sub (e.g., n-DDS 420) may be decoding page with the carrier tune away (CTA), such as CTA 430, 432, 434, 436, being implemented on SCC1 414. In this scenario, the resources held by the SCC1 414 may be released and given to the n-DDS Sub (e.g., n-DDS 420) for page decoding activities. This tune away occasions (e.g., CTA 430, 432, 434, 436) may cause interruption in both downlink and uplink transmissions on SCC1 414, leading to potential data losses. For example, the interruption in uplink transmission maycause channel state feedback (CSF) / uplink control information (UCI) data drops and increased retransmissions, and the loss of sounding reference signal (SRS) data.

[0075] In some aspects, to reduce or avoid the disruptions to the transmission due to the tune away gap (e.g., CTA 430, 432, 434, 436), when a UE is operating on higher order component carriers (CCs) and has multiple uplink carriers (UL CAs) configured, the UE may request the network to move the UL transmissions to a carrier that does not have resource conflicts (e.g., resource conflict with a tune away gap). This can ensure seamless decoding of DL and UL data. In some examples, the UE may transmit the request through a new medium access control (MAC) - control element (MAC-CE).

[0076] FIG. 5 is a diagram 500 illustrating an example of an uplink carrier change in accordance with various aspects of the present disclosure. As shown in FIG. 5, a DDS subscription (e.g., DDS 502) may be operating with configurations involving multiple carrier aggregation (CA), including a PCC 512 for DL and UL, a first secondary CC (e.g., SCC1 514) for DL and UL, a second secondary CC (e.g., SCC2 516) for DL, and a third secondary CC (e.g., SCC3 518) for DL and UL, and the n-DDS Sub (e.g., n-DDS 520) may be decoding page with the carrier tune away (CTA) gap, such as tune away gaps 530, 532, 534, 536, being implemented on SCC1 514. In this example, if the UE identifies that there is no CTA on carriers such as SCC2 516 or SCC3 518, the UE have the UL carrier linked to either SCC2 516 or SCC3 518. For example, the UE may send a new MAC-CE to the network, and the new MAC-CE may include a request to change the uplink carrier from the original carrier (e.g., SCC1 514) to a different uplink a different carrier (e.g., SCC3 518). The new carrier (e.g., SCC3 518) may not have a resource conflict with the CTA gaps (e.g., tune away gaps 530, 532, 534, 536).

[0077] In some examples, upon receiving the UE’s request to change the uplink carrier (e.g., from SCC1 514 to SCC3 518) via the MAC-CE, the network (e.g., the base station) has the option to approve or reject this request. If the network approves the UE’s request to change the uplink carrier, the network may respond with a radio resource control (RRC) reconfiguration to transition the UL to the new carrier (e.g., SCC3 518) as specified by the UE in the MAC-CE. Subsequently, uplink transmissions may proceed on this new carrier (e.g., SCC3 518). On the other hand, if the network rejects the UE’s request to change the uplink carrier, the network may not send any response to the UE’s request (e.g., the network may refrain from responding to the UE’srequest), resulting in the continuation of uplink transmissions on the original carrier (e.g., SCC1 514).

[0078] In some aspects, if the UE does not receive a response from the network regarding theUE’s request to change the uplink carrier, it may retransmit the MAC-CE containing the request for the change of the uplink carrier. In some examples, the retransmission of the MAC-CE may be based on a timer. For example, the UE may initiate a timer associated with the change of the uplink carrier after the initial transmission the MAC- CE that includes the request for the change of the uplink carrier. If the UE has not received a response from the network upon the expiration of the timer, it may retransmit the MAC-CE. In some examples, the duration of the timer may be configured by the UE or the network. In some examples, the UE may retransmit the MAC-CE up to a maximum number of times (e.g., a threshold number of times), and the maximum number of retransmissions may be configured by the UE or the network.

[0079] In some aspects, if the UE identifies multiple SCCs that do not have CTA and therefore do not conflict with uplink transmissions, the UE may select one SCC from the multiple SCCs based on a selection criterion. In some examples, the selection criterion may include choosing one SCC that provides the best received signal reference power (RSRP), the lowest path loss, or the best performance metrics. The performance metrics may include, for example, the DL channel quality indicator (CQI), the DL rank, or the DL bandwidth (BW). For example, referring to FIG. 5, if the UE identifies that SCC2 516 and SCC3 518 do not have CTA and therefore do not conflict with uplink transmissions, the UE may select one SCC from the two SCCs (e.g., SCC2 516 and SCC3 518) based on, for example, the RSRP, the path loss, or the performance metrics associated with these two SCCs. The performance metrics may include, for example, the DL CQI, the DL rank, or the DL bandwidth.

[0080] FIG. 6 is a diagram 600 illustrating an example of an uplink carrier change in accordance with various aspects of the present disclosure. In FIG. 6, the UE 602 may communicate with the base station 604 in a multi-carrier configuration, which may include multiple secondary carriers, such as SCC1 614, SCC2 616, SCC3 618, among others. The UE 602 may transmit uplink transmissions to the base station 604 using an original carrier (e.g., SCC1 614). When the UE 602 determines one or more tune away gaps, such as tune away gaps 630, 632 in the original carrier (e.g., SCC1 614), which may conflict with uplink transmissions, the UE 602 may configure a MAC-CE to request to a change of the uplink carrier from the original carrier (e.g., SCC1 614)to a new carrier (e.g., SCC2 616) that does not have a resource conflict (e.g., do not have the tune away gaps). In some examples, when there are multiple carriers (e.g., SCC2 616, SCC3 618) that do not have a resource conflict, the UE 602 may select one carrier from the multiple carriers based on a selection criterion. For example, the UE 602 may select one carrier based on the best RSRP, the lowest pathloss, or the best performance metrics (e.g., the best DL CQI, DL rank, or DL bandwidth) among the multiple carriers.

[0081] For example, the UE 602 may send the MAC-CE at 620 to the base station 604 to request a change in the uplink carrier from the original carrier (e.g., SCC1 614) to the new carrier (e.g., SCC2 616). If the base station 604 approves the UE’s request to change the uplink carrier, as specified in the MAC-CE at 620, it may transmit an RRC message (e.g., an RRC reconfiguration message) to the UE 602 at 622. This message may indicate the change of the uplink carrier from the original carrier (e.g., SCC1 614) to the new carrier (e.g., SCC2 616). Upon receiving the RRC message from the base station 604, the UE 602 may begin uplink transmissions 624 using (at 626) the new carrier (e.g., SCC2 616). For example, the UE 602 may begin uplink transmissions 624 using the new carrier (e.g., SCC2 616) at time to 640. In some examples, after the time to 640, the UE 602 may use the original carrier (e.g., SCC1 614) to receive downlink transmissions from the base station 604. The capability for the UE 602 to request network reconfiguration and change the uplink to a carrier (e.g., SCC2 616) without resource conflicts due to the tune away helps to minimize interruptions to uplink transmissions, thereby maintaining high DL and UL throughput.

[0082] FIG. 7 is a call flow diagram 700 illustrating a method of wireless communication in accordance with various aspects of this present disclosure. Various aspects are described in connection with a UE 702 and a base station 704. The aspects may be performed by the UE 702 or the base station 704 in aggregation and / or by one or more components of a base station 704 (e.g., a CU 110, a DU 130, and / or an RU 140).

[0083] As shown in FIG. 7, at 706, a UE 702 may select, based on a tune away gap of an original carrier overlapping with an uplink transmission of the UE, one SCC from one or more candidate SCCs of the UE 702. For example, referring to FIG. 6, the UE 602 may select one SCC (e.g., SCC2 616) based on the tune away gap (e.g., tune away gaps 630, 632) of an original carrier (e.g., SCC1 614) overlapping with an uplink transmission of the UE 602.

[0084] At 708, the UE 702 may configure a MAC-CE based on the selected one SCC. For example, referring to FIG. 6, the MAC-CE may include a request for a change of an uplink carrier of the uplink transmission from the original carrier (e.g., SCC1 614) to the selected SCC (e.g., SCC2 616).

[0085] At 710, the UE 702 may transmit, to the base station 704, the MAC-CE that includes the request for a change of an uplink carrier of the uplink transmission from the original carrier to the one SCC.

[0086] At 712, after transmitting the MAC-CE to the base station 704 at 710, the UE 702 may monitor for a network configuration from the base station 704. The network configuration may be through an RRC message and may indicates the change of the uplink carrier.

[0087] In some aspects, at 714, the UE 702 may initiate a timer associated with the change of the uplink carrier after transmitting the MAC-CE that includes the request for the change of the uplink carrier at 710. In some examples, the UE 702 may retransmit the MAC-CE based on the timer if the UE 702 does not receive a response from the base station 704.

[0088] In some aspects, the base station 704 may approve the UE’s request to change the uplink carrier, as specified in the MAC-CE transmitted at 710. In that case, the base station 704 may, at 716, send a network configuration to the UE 702. In some examples, the network configuration may be via an RRC message and may indicate the change of the uplink carrier from the original carrier to the selected SCC. For example, referring to FIG. 6, the base station 604 may, at 622, send an RRC reconfiguration message to the UE 602 indicating the change of the uplink carrier (e.g., from SCC1 614 to SCC2 616).

[0089] At 716, upon receiving the network configuration from the base station at 716, the UE 702 may, at 718, perform uplink transmissions via the selected SCC, as specified in the MAC-CE at 710. For example, referring to FIG. 6, the UE 602 may perform uplink transmissions 624 via the selected SCC (e.g., SCC2 616), and the selected SCC (e.g., SCC 616) may be specified in the MAC-CE transmitted to the base station 604 at 620.

[0090] In some aspects, the base station 704 may reject the UE’s request to change the uplink carrier, as specified in the MAC-CE transmitted at 710. In that case, the base station 704 may, at 720, refrain from responding to the UE’s request.

[0091] In some aspects, if the UE 702 does not receive a response from the base station 704 regarding the UE’s request to change the uplink carrier, the UE 702 may, at 722,retransmit the MAC-CE containing the request for the change of the uplink carrier. In some examples, the retransmission of the MAC-CE may be based on the timer, which may be initiated at 714. For example, the UE 702 may retransmit the MAC-CE at 722 if the UE 702 has not received a response from the base station 704 at the expiration of the timer, and the duration of the timer may be configured by the UE 702 or the base station 704. In some examples, the UE 702 may retransmit the MAC-CE up to a maximum number of times (e.g., a threshold number of times), and the maximum number of retransmissions may be configured by the UE 702 or the base station 704.

[0092] In some aspects, if the base station 704 rejects the UE’s request to change the uplink carrier, the UE 702 may, at 724, continue the uplink transmissions using the original carrier.

[0093] FIG. 8 is a flowchart 800 illustrating methods of wireless communication at a UE in accordance with various aspects of the present disclosure. The method may be performed by a UE. The UE may be the UE 104, 350, 602, 702, or the apparatus 1004 in the hardware implementation of FIG. 10. By enabling the UE to request network reconfiguration and move the uplink to a carrier without resource conflicts due to the tune away, the methods minimize interruptions in uplink transmissions that may occur due to the tune away and avoid the data drops in CSF, UCI, and SRSs, thereby maintaining a high DL and UL throughput in wireless communication.

[0094] As shown in FIG. 8, at 802, the UE may select, based on a tune away gap of an original carrier overlapping with an uplink transmission of the UE, one SCC from one or more candidate SCCs of the UE. FIG. 5, FIG. 6, and FIG. 7 illustrate various aspects of the steps in connection with flowchart 800. For example, referring to FIG. 7, the UE 702 may select, at 706, based on a tune away gap of an original carrier overlapping with an uplink transmission of the UE 702, one SCC from one or more candidate SCCs of the UE 702. Referring to FIG. 5, the UE may select one SCC (e.g., SCC3 518) based on the tune away gap (e.g., tune away gaps 530, 532, 534, 536) of an original carrier (e.g., SCC1 514) overlapping with an uplink transmission of the UE. In some aspects, 802 may be performed by the uplink reconfiguration component 198.

[0095] At 804, the UE may transmit, to a network entity, a MAC-CE. The MAC-CE may include a request for the change of an uplink carrier of the uplink transmission from the original carrier to the one SCC. The network entity may be a base station, or a component of a base station, in the access network of FIG. 1 or a core network component (e.g., base station 102, 310, 604, 704; or the network entity 1002 in thehardware implementation of FIG. 10). For example, referring to FIG. 6 and FIG. 7, the UE 702 may transmit, at 710, to a network entity (base station 704), a MAC-CE. The MAC-CE may include a request for the change of an uplink carrier of the uplink transmission from the original carrier (e.g., SCC1 614) to the one SCC (e.g., SCC2 616). In some aspects, 802 may be performed by the uplink reconfiguration component 198.

[0096] In some aspects, the UE may configure the MAC-CE based on the selected one SCC. And to transmit the MAC-CE (at 802), the UE may transmit the configured MAC- CE. For example, referring to FIG. 7, the UE 702 may, at 708, configure the MAC- CE based on the selected one SCC (e.g., selected at 706). And the UE 702 may transmit the configured MAC-CE at 710.

[0097] In some aspects, to select the one SCC from the one or more candidate SCCs (at 802), the UE may select one or more compatible SCCs from the one or more candidate SCCs, and the one or more compatible SCCs may be uplink capable and may lack the tune away gap overlapping with the uplink transmission. In some aspects, to select the one SCC (802), the UE may select, based on the selection criterion for each compatible SCC of the one or more compatible SCCs, the one SCC from the one or more compatible SCCs. For example, referring to FIG. 6, the UE 602 may select one or more compatible SCCs (e.g., SCC2616, SCC3 618) from the one or more candidate SCCs, and the one or more compatible SCCs may be uplink capable and may lack the tune away gap overlapping with the uplink transmission. In some aspects, the UE 602 may select the one SCC (e.g., SCC2 616) based on the selection criterion for each compatible SCC of the one or more compatible SCCs (e.g., SCC2 616, SCC3 618).

[0098] In some aspects, the selection criterion may include one or more of: the RSRP, the pathloss, the DL CQI, the DL rank, or the DL bandwidth. For example, referring to FIG. 6, the selection criterion may include the RSRP, the pathloss, the DL CQI, the DL rank, or the DL bandwidth associated with each of the compatible SCCs (e.g., SCC2 616, SCC3 618).

[0099] In some aspects, after transmitting the MAC-CE, the UE may monitor for a network configuration from the network entity that indicates the change of the uplink carrier. In some aspects, the network configuration may be transmitted from the network entity via a radio resource control (RRC) message. For example, referring to FIG. 7, the UE 702 may, at 708, monitor for a network configuration from the network entity (base station 704) that indicates the change of the uplink carrier. In some aspects, thenetwork configuration may be transmitted, at 716, from the network entity (base station 704) via an RRC message.

[0100] In some aspects, the UE may receive, from the network entity, the network configuration based on monitoring for the network configuration; and transmit, based on the network configuration, the uplink transmission to the network entity using the one SCC. For example, referring to FIG. 7, the UE 702 may receive, at 716, from the network entity (base station 704), the network configuration based on monitoring for the network configuration; and transmit, at 718, based on the network configuration, the uplink transmission to the network entity using the one SCC. Referring to FIG. 6, the UE 602 may perform uplink transmissions 624 via the selected SCC (e.g., SCC2 616), and the selected SCC (e.g., SCC 616) may be specified in the MAC-CE transmitted to the base station 604 at 620.

[0101] In some aspects, in response to an absence of the network configuration, the UE may retransmit the MAC-CE. For example, referring to FIG. 7, the UE 702 may, at 722, retransmit the MAC-CE if the UE 702 has not received a response from the base station 704.

[0102] In some aspects, the UE may initiate a timer associated with the change of the uplink carrier after transmitting the MAC-CE including the request for the change of the uplink carrier (at 804), and the UE may retransmit the MAC-CE in response to the absence of the network configuration at an expiration of the timer. For example, referring to FIG. 7, the UE 702 may, at 714, initiate a timer associated with the change of the uplink carrier after transmitting the MAC-CE including the request for the change of the uplink carrier (at 710), and the UE 702 may retransmit the MAC-CE, at 722, if the UE 702 has not received a response from the network entity (base station 704) at the expiration of the timer.

[0103] In some aspects, the duration of the timer may be configured by the UE or the network entity. For example, referring to FIG. 7, the duration of the timer (the UE 702 initiated at 714) may be configured by the UE 702 or the network entity (base station 704).

[0104] In some aspects, the UE may retransmit the MAC-CE up to a threshold number of times. For example, referring to FIG. 7, the UE 702 may, at 722, retransmit the MAC- CE up to a threshold number of times.

[0105] In some aspects, the threshold number may be configured by the UE or the network entity. For example, referring to FIG. 7, the threshold number of the retransmission at 722 may be configured by the UE 702 or the network entity (base station 704).

[0106] In some aspects, the UE may communicate with the network entity based on the request in the MAC-CE. For example, referring to FIG. 7, the UE 702 may, at 718, communicate with the network entity (base station 704) based on the request in the MAC-CE. Referring to FIG. 6, the UE 602 may perform uplink transmissions 624 via the selected SCC (e.g., SCC2 616), and the selected SCC (e.g., SCC 616) may be specified in the MAC-CE transmitted to the base station 604 at 620.

[0107] FIG. 9 is a flowchart 900 illustrating methods of wireless communication at a network entity in accordance with various aspects of the present disclosure. The method may be performed by a network entity. The network entity may be a base station, or a component of a base station, in the access network of FIG. 1 or a core network component (e.g., base station 102, 310, 604, 704; or the network entity 1002 in the hardware implementation of FIG. 10). By enabling the UE to request network reconfiguration and move the uplink to a carrier without resource conflicts due to the tune away, the methods minimize interruptions in uplink transmissions that may occur due to the tune away and avoid the data drops in channel state feedback (CSF), uplink control information (UCI), and sounding reference signals (SRSs), thereby maintaining a high DL and UL throughput in wireless communication.

[0108] As shown in FIG. 9, at 902, the network entity may receive, from a UE, a MAC-CE. The MAC-CE may include a request for the change of an uplink carrier for an uplink transmission from an original carrier to an SCC. The UE may be the UE 104, 350, 602, 702, or the apparatus 1004 in the hardware implementation of FIG. 10. FIG. 5, FIG. 6, and FIG. 7 illustrate various aspects of the steps in connection with flowchart 900. For example, referring to FIG. 7, the network entity (base station 704) may receive, at 710, from a UE 702, a MAC-CE. The MAC-CE may include a request for the change of an uplink carrier for an uplink transmission from an original carrier to an SCC. In some aspects, 902 may be performed by the uplink reconfiguration component 199. Referring to FIG. 6, the MAC-CE (transmitted at 620) may include a request for the change of an uplink carrier for an uplink transmission from an original carrier (e.g., SCC1 614) to an SCC (e.g., SCC2 616).

[0109] At 904, the network entity may communicate with the UE based on the request in the MAC-CE. For example, referring to FIG. 7, the network entity (base station 704) may, at 718, communicate with the UE 702 based on the request in the MAC-CE. Referring to FIG. 6, the UE 602 may perform uplink transmissions 624 via the selected SCC (e.g., SCC2616), and the selected SCC (e.g., SCC 616) may be specified in the MAC-CE transmitted to the base station 604 at 620. In some aspects, 904 may be performed by the uplink reconfiguration component 199.

[0110] In some aspects, the original carrier may have a tune away gap overlapping with the uplink transmission, and the SCC may lack the tune away gap overlapping with the uplink transmission. For example, referring to FIG. 5, the original carrier (e.g., SCC1 514) may have a tune away gap (e.g., tune away gaps 530, 532, 534, 536) overlapping with the uplink transmission, and the SCC (e.g., SCC3 518) may lack the tune away gap overlapping with the uplink transmission.[OHl] In some aspects, to communicate with the UE (at 904), the network entity may transmit, for the UE, a network configuration indicating the change of the uplink carrier from the original carrier to the SCC. For example, referring to FIG. 7, the network entity (base station 704) may transmit, at 716, for the UE 702, a network configuration indicating the change of the uplink carrier from the original carrier to the SCC.

[0112] In some aspects, to transmit the network configuration (at 902), the network entity may transmit the network configuration via an RRC message. For example, referring to FIG. 7, the network entity (base station 704) may transmit the network configuration, at 716, via an RRC message. Referring to FIG. 6, the network entity (base station 604) may transmit the network configuration, at 622, via an RRC message (e.g., an RRC reconfiguration message).

[0113] In some aspects, the network entity may receive, from the UE, the uplink transmission via the SCC. For example, referring to FIG. 7, the network entity (base station 704) may receive, at 718, from the UE 702, the uplink transmission via the SCC.

[0114] In some aspects, to communicate with the UE (at 904), the network entity may refrain from responding to the MAC-CE. For example, referring to FIG. 7, if the network entity (base station 704) rejects the UE’s request to change the uplink carrier, the network entity (base station 704) may, at 720, refrain from responding to the MAC- CE.

[0115] In some aspects, the network entity may receive, from the UE, the uplink transmission via the original carrier. For example, referring to FIG. 7, if the network entity (base station 704) rejects the UE’s request to change the uplink carrier, the network entity (base station 704) may, at 724, receive, from the UE 702, the uplink transmission via the original carrier. Referring to FIG. 6, the original carrier may be SCC1 614.

[0116] FIG. 10 is a diagram 1000 illustrating an example of a hardware implementation for an apparatus 1004. The apparatus 1004 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1004 may include at least one cellular baseband processor (or processing circuitry) 1024 (also referred to as a modem) coupled to one or more transceivers 1022 (e.g., cellular RF transceiver). The cellular baseband processor(s) (or processing circuitry) 1024 may include at least one on-chip memory (or memory circuitry) 1024'. In some aspects, the apparatus 1004 may further include one or more subscriber identity modules (SIM) cards 1020 and at least one application processor (or processing circuitry) 1006 coupled to a secure digital (SD) card 1008 and a screen 1010. The application processor(s) (or processing circuitry) 1006 may include on-chip memory (or memory circuitry) 1006'. In some aspects, the apparatus 1004 may further include a Bluetooth module 1012, a WLAN module 1014, an SPS module 1016 (e.g., GNSS module), one or more sensor modules 1018 (e.g., barometric pressure sensor / altimeter; motion sensor such as inertial measurement unit (IMU), gyroscope, and / or accelerometer(s); magnetometer, audio and / or other technologies used for positioning), additional memory modules 1026, a power supply 1030, and / or a camera 1032. The Bluetooth module 1012, the WLAN module 1014, and the SPS module 1016 may include an on-chip transceiver (TRX) (or in some cases, just a receiver (RX)). The Bluetooth module 1012, the WLAN module 1014, and the SPS module 1016 may include their own dedicated antennas and / or utilize the antennas 1080 for communication. The cellular baseband processor(s) (or processing circuitry) 1024 communicates through the transceiver(s) 1022 via one or more antennas 1080 with the UE 104 and / or with an RU associated with a network entity 1002. The cellular baseband processor(s) (or processing circuitry) 1024 and the application processor(s) (or processing circuitry) 1006 may each include a computer-readable medium / memory (or memory circuitry) 1024', 1006', respectively. The additional memory modules 1026 may also be considered a computer-readable medium / memory (or memory circuitry). Each computer-readable medium / memory (or memory circuitry) 1024', 1006', 1026 may be non-transitory. The cellular baseband processor(s) (or processing circuitry) 1024 and the application processor(s) (or processing circuitry) 1006 are each responsible for general processing, including the execution of software stored on the computer-readable medium / memory (or memory circuitry). The software, when executed by the cellular baseband processor(s) (or processing circuitry) 1024 / application processor(s) (orprocessing circuitry) 1006, causes the cellular baseband processor(s) (or processing circuitry) 1024 / application processor(s) (or processing circuitry) 1006 to perform the various functions described supra. The cellular baseband processor(s) (or processing circuitry) 1024 and the application processor(s) (or processing circuitry) 1006 are configured to perform the various functions described supra based at least in part of the information stored in the memory (or memory circuitry). That is, the cellular baseband processor(s) (or processing circuitry) 1024 and the application processor(s) (or processing circuitry) 1006 may be configured to perform a first subset of the various functions described supra without information stored in the memory and may be configured to perform a second subset of the various functions described supra based on the information stored in the memory. The computer-readable medium / memory (or memory circuitry) may also be used for storing data that is manipulated by the cellular baseband processor(s) (or processing circuitry) 1024 / application processor(s) (or processing circuitry) 1006 when executing software. The cellular baseband processor(s) (or processing circuitry) 1024 / application processor(s) (or processing circuitry) 1006 may be a component of the UE 350 and may include the at least one memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the apparatus 1004 may be at least one processor chip (modem and / or application) and include just the cellular baseband processor(s) (or processing circuitry) 1024 and / or the application processor(s) (or processing circuitry) 1006, and in another configuration, the apparatus 1004 may be the entire UE (e.g., see UE 350 of FIG. 3) and include the additional modules of the apparatus 1004.

[0117] As discussed supra, the component 198 may be configured to select, based on a tune away gap of an original carrier overlapping with an uplink transmission of the UE, one SCC from one or more candidate SCCs of the UE; and transmit, to a network entity, a MAC-CE including a request for a change of an uplink carrier of the uplink transmission from the original carrier to the one SCC. The component 198 may be further configured to perform any of the aspects described in connection with the flowchart in FIG. 8, and / or performed by the UE 702 in FIG. 7. The component 198 may be within the cellular baseband processor(s) (or processing circuitry) 1024, the application processor(s) (or processing circuitry) 1006, or both the cellular baseband processor(s) (or processing circuitry) 1024 and the application processor(s) (or processing circuitry) 1006. The component 198 may be one or more hardwarecomponents specifically configured to carry out the stated processes / algorithm, implemented by one or more processors configured to perform the stated processes / algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may perform the stated processes / algorithm individually or in combination. As shown, the apparatus 1004 may include a variety of components configured for various functions. In one configuration, the apparatus 1004, and in particular the cellular baseband processor(s) (or processing circuitry) 1024 and / or the application processor(s) (or processing circuitry) 1006, includes means for selecting, based on a tune away gap of an original carrier overlapping with an uplink transmission of the UE, one SCC from one or more candidate SCCs of the UE, and means for transmitting, to a network entity, a MAC-CE including a request for a change of an uplink carrier of the uplink transmission from the original carrier to the one SCC. The apparatus 1004 may further include means for performing any of the aspects described in connection with the flowchart in FIG. 8, and / or aspects performed by the UE 702 in FIG. 7. The means may be the component 198 of the apparatus 1004 configured to perform the functions recited by the means. As described supra, the apparatus 1004 may include the TX processor 368, the RX processor 356, and the controller / processor 359. As such, in one configuration, the means may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by the means.

[0118] FIG. 11 is a diagram 1100 illustrating an example of a hardware implementation for a network entity 1102. The network entity 1102 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1102 may include at least one of a CU 1110, a DU 1130, or an RU 1140. For example, depending on the layer functionality handled by the component 199, the network entity 1102 may include the CU 1110; both the CU 1110 and the DU 1130; each of the CU 1110, the DU 1130, and the RU 1140; the DU 1130; both the DU 1130 and the RU 1140; or the RU 1140. The CU 1110 may include at least one CU processor (or processing circuitry) 1112. The CU processor(s) (or processing circuitry) 1112 may include on-chip memory (or memory circuitry) 1112'. In some aspects, the CU 1110 may further include additional memory modules 1114 and a communications interface 1118. The CU 1110 communicates with the DU 1130 through a midhaul link, such as an Fl interface. The DU 1130 may include at least one DU processor (or processing circuitry) 1132. TheDU processor(s) (or processing circuitry) 1132 may include on-chip memory (or memory circuitry) 1132'. In some aspects, the DU 1130 may further include additional memory modules 1134 and a communications interface 1138. The DU 1130 communicates with the RU 1140 through a fronthaul link. The RU 1140 may include at least one RU processor (or processing circuitry) 1142. The RU processor(s) (or processing circuitry) 1142 may include on-chip memory (or memory circuitry) 1142'. In some aspects, the RU 1140 may further include additional memory modules 1144, one or more transceivers 1146, antennas 1180, and a communications interface 1148. The RU 1140 communicates with the UE 104. The on-chip memory (or memory circuitry) 1112', 1132', 1142' and the additional memory modules 1114, 1134, 1144 may each be considered a computer-readable medium / memory (or memory circuitry). Each computer-readable medium / memory (or memory circuitry) may be non-transitory. Each of the processors (or processing circuitry) 1112, 1132, 1142 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory (or memory circuitry). The software, when executed by the corresponding processor(s) (or processing circuitry) causes the processor(s) (or processing circuitry) to perform the various functions described supra. The computer-readable medium / memory (or memory circuitry) may also be used for storing data that is manipulated by the processor(s) (or processing circuitry) when executing software.

[0119] As discussed supra, the component 199 may be configured to receive, from a UE, a MAC-CE including a request for a change of an uplink carrier for an uplink transmission from an original carrier to an SCC; and communicate with the UE based on the request in the MAC-CE. The component 199 may be further configured to perform any of the aspects described in connection with the flowchart in FIG. 9, and / or performed by the base station 704 in FIG. 7. The component 199 may be within one or more processors (or processing circuitry) of one or more of the CU 1110, DU 1130, and the RU 1140. The component 199 may be one or more hardware components specifically configured to carry out the stated processes / algorithm, implemented by one or more processors configured to perform the stated processes / algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may perform the stated processes / algorithm individually or in combination. The network entity 1102 may include a variety ofcomponents configured for various functions. In one configuration, the network entity 1102 includes means for receiving, from a UE, a MAC-CE including a request for a change of an uplink carrier for an uplink transmission from an original carrier to an SCC, and means for communicating with the UE based on the request in the MAC- CE. The network entity 1102 may further include means for performing any of the aspects described in connection with the flowchart in FIG. 9, and / or aspects performed by the base station 704 in FIG. 7. The means may be the component 199 of the network entity 1102 configured to perform the functions recited by the means. As described supra, the network entity 1102 may include the TX processor 316, the RX processor 370, and the controller / processor 375. As such, in one configuration, the means may be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions recited by the means.

[0120] This disclosure provides a method for wireless communication at a UE. The method may include selecting, based on a tune away gap of an original carrier overlapping with an uplink transmission of the UE, one SCC from one or more candidate SCCs of the UE; and transmitting, to a network entity, a MAC-CE including a request for a change of an uplink carrier of the uplink transmission from the original carrier to the one SCC. By enabling the UE to request network reconfiguration and move the uplink to a carrier without resource conflicts due to the tune away, the methods minimize interruptions in uplink transmissions that may occur due to the tune away and avoid the data drops in CSF, UCI, and SRSs, thereby maintaining a high DL and UL throughput in wireless communication.

[0121] It is understood that the specific order or hierarchy of blocks in the processes / flowcharts disclosed is an illustration of example approaches. Based upon design preferences, it is understood that the specific order or hierarchy of blocks in the processes / flowcharts may be rearranged. Further, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, and are not limited to the specific order or hierarchy presented.

[0122] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects described herein, but are to be accorded the full scope consistent with the language claims. Reference to an element in the singular does not mean “one and only one”unless specifically so stated, but rather “one or more.” Terms such as “if,” “when,” and “while” do not imply an immediate temporal relationship or reaction. That is, these phrases, e.g., “when,” do not imply an immediate action in response to or during the occurrence of an action, but simply imply that if a condition is met then an action will occur, but without requiring a specific or immediate time constraint for the action to occur. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof’ include any combination of A, B, and / or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof’ may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C. Sets should be interpreted as a set of elements where the elements number one or more. Accordingly, for a set of X, X would include one or more elements. When at least one processor is configured to perform a set of functions, the at least one processor, individually or in any combination, is configured to perform the set of functions. Accordingly, each processor of the at least one processor may be configured to perform a particular subset of the set of functions, where the subset is the full set, a proper subset of the set, or an empty subset of the set. A processor may be referred to as processor circuitry. A memory / memory module may be referred to as memory circuitry. If a first apparatus receives data from or transmits data to a second apparatus, the data may be received / transmitted directly between the first and second apparatuses, or indirectly between the first and second apparatuses through a set of apparatuses. A device configured to “output” data or “provide” data, such as a transmission, signal, or message, may transmit the data, for example with a transceiver, or may send the data to a device that transmits the data. A device configured to “obtain” data, such as a transmission, signal, or message, may receive, for example with a transceiver, or may obtain the data from a device that receives the data. Information stored in a memory includes instructions and / or data. All structural and functional equivalents tothe elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are encompassed by the claims. Moreover, nothing disclosed herein is dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The words “module,” “mechanism,” “element,” “device,” and the like may not be a substitute for the word “means.” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for.”

[0123] As used herein, the phrase “based on” shall not be construed as a reference to a closed set of information, one or more conditions, one or more factors, or the like. In other words, the phrase “based on A” (where “A” may be information, a condition, a factor, or the like) shall be construed as “based at least on A” unless specifically recited differently.

[0124] The following aspects are illustrative only and may be combined with other aspects or teachings described herein, without limitation.

[0125] Aspect 1 is a method of wireless communication at a UE. The method includes selecting, based on a tune away gap of an original carrier overlapping with an uplink transmission of the UE, one secondary component carrier (SCC) from one or more candidate SCCs of the UE; and transmitting, to a network entity, a medium access control (MAC) - control element (MAC-CE) comprising a request for a change of an uplink carrier of the uplink transmission from the original carrier to the one SCC.

[0126] Aspect 2 is the method of aspect 1, where the method further includes configuring the MAC-CE based on the selected one SCC, and wherein transmitting the MAC-CE comprises transmitting the configured MAC-CE.

[0127] Aspect 3 is the method of any of aspects 1 to 2, wherein selecting the one SCC from the one or more candidate SCCs comprises: selecting one or more compatible SCCs from the one or more candidate SCCs, wherein the one or more compatible SCCs are uplink capable and lack the tune away gap overlapping with the uplink transmission, and wherein selecting the one SCC comprises selecting, based on a selection criterion for each compatible SCC of the one or more compatible SCCs, the one SCC from the one or more compatible SCCs.

[0128] Aspect 4 is the method of aspect 3, wherein the selection criterion includes one or more of: a reference signal received power (RSRP), a pathloss, a downlink (DL) channel quality indicator (CQI), a DL rank, or a DL bandwidth.

[0129] Aspect 5 is the method of any of aspects 1 to 4, where the method further includes monitoring for a network configuration via a radio resource control (RRC) message from the network entity that indicates the change of the uplink carrier.

[0130] Aspect 6 is the method of aspect 5, where the method further includes receiving, from the network entity, the network configuration based on monitoring for the network configuration; and transmitting, based on the network configuration, the uplink transmission to the network entity using the one SCC.

[0131] Aspect 7 is the method of aspect 5, where the method further includes retransmitting, in response to an absence of the network configuration, the MAC-CE.

[0132] Aspect 8 is the method of aspect 7, where the method further includes initiating a timer associated with the change of the uplink carrier after transmitting the MAC-CE comprising the request for the change of the uplink carrier, and wherein retransmitting the MAC-CE comprises: retransmitting, in response to the absence of the network configuration at an expiration of the timer, the MAC-CE.

[0133] Aspect 9 is the method of aspect 8, wherein a duration of the timer is configured by the UE or the network entity.

[0134] Aspect 10 is the method of aspect 7, wherein retransmitting the MAC-CE comprises: retransmitting the MAC-CE up to a threshold number of times.

[0135] Aspect 11 is the method of aspect 10, wherein the threshold number is configured by the UE or the network entity.

[0136] Aspect 12 is the method of any of aspects 1 to 11, where the method further includes communicating with the network entity based on the request in the MAC-CE.

[0137] Aspect 13 is an apparatus for wireless communication at a UE, comprising: a processing system that includes processor circuitry and memory circuitry that stores code and is coupled with the processor circuitry, the processing system configured to cause the UE to perform the method of one or more of aspects 1-12.

[0138] Aspect 14 is an apparatus for wireless communication at a UE, comprising: at least one memory; and at least one processor coupled to the at least one memory and, where the at least one processor, individually or in any combination, is configured to perform the method of any of aspects 1-12.

[0139] Aspect 15 is the apparatus for wireless communication at a UE, comprising means for performing each step in the method of any of aspects 1-12.

[0140] Aspect 16 is an apparatus of any of aspects 13-15, further comprising a transceiver configured to receive or to transmit in association with the method of any of aspects 1-12.

[0141] Aspect 17 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer executable code at a UE, the code when executed by at least one processor causes the at least one processor to, individually or in any combination, perform the method of any of aspects 1-12.

[0142] Aspect 18 is a method of wireless communication at a network entity. The method includes receiving, from a user equipment (UE), a medium access control (MAC) - control element (MAC-CE) comprising a request for a change of an uplink carrier for an uplink transmission from an original carrier to a secondary component carrier (SCC); and communicating with the UE based on the request in the MAC-CE.

[0143] Aspect 19 is the method of aspect 18, wherein the original carrier has a tune away gap overlapping with the uplink transmission, and wherein the SCC lacks the tune away gap overlapping with the uplink transmission.

[0144] Aspect 20 is the method of any of aspects 18 to 19, wherein communicating with the UE comprises: transmitting, for the UE, a network configuration indicating the change of the uplink carrier from the original carrier to the SCC.

[0145] Aspect 21 is the method of aspect 20, wherein transmitting the network configuration comprises: transmitting the network configuration via a radio resource control (RRC) message.

[0146] Aspect 22 is the method of aspect 20, where the method further includes receiving, from the UE, the uplink transmission via the SCC.

[0147] Aspect 23 is the method of aspect 18, wherein communicating with the UE comprises: refraining from responding to the MAC-CE.

[0148] Aspect 24 is the method of aspect 23, where the method further includes receiving, from the UE, the uplink transmission via the original carrier.

[0149] Aspect 25 is an apparatus for wireless communication at a network entity, comprising: a processing system that includes processor circuitry and memory circuitry that stores code and is coupled with the processor circuitry, the processing system configured to cause the network entity to perform the method of one or more of aspects 18-24.

[0150] Aspect 26 is an apparatus for wireless communication at a network entity, comprising: at least one memory; and at least one processor coupled to the at least one memoryand, where the at least one processor, individually or in any combination, is configured to perform the method of any of aspects 18-24.

[0151] Aspect 27 is the apparatus for wireless communication at a network entity, comprising means for performing each step in the method of any of aspects 18-24.

[0152] Aspect 28 is an apparatus of any of aspects 25-27, further comprising a transceiver configured to receive or to transmit in association with the method of any of aspects 18-24.

[0153] Aspect 29 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer executable code at a network entity, the code when executed by at least one processor causes the at least one processor to, individually or in any combination, perform the method of any of aspects 18-24.

Claims

CLAIMSWHAT IS CLAIMED IS:

1. An apparatus for wireless communication at a user equipment (UE), comprising: at least one memory; and at least one processor coupled to the at least one memory and, based at least in part on information stored in the at least one memory, the at least one processor, individually or in any combination, is configured to: select, based on a tune away gap of an original carrier overlapping with an uplink transmission of the UE, one secondary component carrier (SCC) from one or more candidate SCCs of the UE; and transmit, to a network entity, a medium access control (MAC) - control element (MAC-CE) comprising a request for a change of an uplink carrier of the uplink transmission from the original carrier to the one SCC.

2. The apparatus of claim 1, further comprising a transceiver coupled to the at least one processor, wherein the at least one processor, individually or in any combination, is further configured to: configure the MAC-CE based on the selected one SCC, and wherein to transmit the MAC-CE, the at least one processor, individually or in any combination, is configured to: transmit, via the transceiver, the configured MAC-CE.

3. The apparatus of claim 1, wherein to select the one SCC from the one or more candidate SCCs, the at least one processor, individually or in any combination, is configured to: select one or more compatible SCCs from the one or more candidate SCCs, wherein the one or more compatible SCCs are uplink capable and lack the tune away gap overlapping with the uplink transmission, and wherein to select the one SCC, the at least one processor, individually or in any combination, is configured to:select, based on a selection criterion for each compatible SCC of the one or more compatible SCCs, the one SCC from the one or more compatible SCCs.

4. The apparatus of claim 3, wherein the selection criterion includes one or more of: a reference signal received power (RSRP), a pathloss, a downlink (DL) channel quality indicator (CQI), a DL rank, or a DL bandwidth.

5. The apparatus of claim 1, wherein the at least one processor, individually or in any combination, is further configured to: monitor for a network configuration via a radio resource control (RRC) message from the network entity that indicates the change of the uplink carrier.

6. The apparatus of claim 5, wherein the at least one processor, individually or in any combination, is further configured to: receive, from the network entity, the network configuration based on monitoring for the network configuration; and transmit, based on the network configuration, the uplink transmission to the network entity using the one SCC.

7. The apparatus of claim 5, wherein the at least one processor, individually or in any combination, is further configured to: retransmit, in response to an absence of the network configuration, the MAC-CE.

8. The apparatus of claim 7, wherein the at least one processor, individually or in any combination, is further configured to: initiate a timer associated with the change of the uplink carrier after being configured to transmit the MAC-CE comprising the request for the change of the uplinkcarrier, and wherein to retransmit the MAC-CE, the at least one processor, individually or in any combination, is configured to: retransmit, in response to the absence of the network configuration at an expiration of the timer, the MAC-CE.

9. The apparatus of claim 8, wherein a duration of the timer is configured by the UE or the network entity.

10. The apparatus of claim 7, wherein to retransmit the MAC-CE, the at least one processor, individually or in any combination, is configured to: retransmit the MAC-CE up to a threshold number of times.

11. The apparatus of claim 10, wherein the threshold number is configured by the UE or the network entity.

12. The apparatus of claim 1, wherein the at least one processor, individually or in any combination, is further configured to: communicate with the network entity based on the request in the MAC-CE.

13. An apparatus for wireless communication at a network entity, comprising: at least one memory; and at least one processor coupled to the at least one memory and, based at least in part on information stored in the at least one memory, the at least one processor, individually or in any combination, is configured to: receive, from a user equipment (UE), a medium access control (MAC) - control element (MAC-CE) comprising a request for a change of an uplink carrier for an uplink transmission from an original carrier to a secondary component carrier (SCC); and communicate with the UE based on the request in the MAC-CE.

14. The apparatus of claim 13, further comprising a transceiver coupled to the at least one processor, wherein to receive the MAC-CE, the at least one processor, individuallyor in any combination, is configured to receive the MAC-CE via the transceiver, wherein the original carrier has a tune away gap overlapping with the uplink transmission, and wherein the SCC lacks the tune away gap overlapping with the uplink transmission.

15. The apparatus of claim 14, wherein to communicate with the UE, the at least one processor, individually or in any combination, is configured to: transmit, for the UE, a network configuration indicating the change of the uplink carrier from the original carrier to the SCC.

16. The apparatus of claim 15, wherein to transmit the network configuration, the at least one processor, individually or in any combination, is configured to: transmit the network configuration via a radio resource control (RRC) message.

17. The apparatus of claim 15, wherein the at least one processor, individually or in any combination, is further configured to: receive, from the UE, the uplink transmission via the SCC.

18. The apparatus of claim 13, wherein to communicate with the UE, the at least one processor, individually or in any combination, is configured to: refrain from responding to the MAC-CE.

19. The apparatus of claim 18, wherein the at least one processor, individually or in any combination, is further configured to: receive, from the UE, the uplink transmission via the original carrier.

20. A method of wireless communication at a user equipment (UE), comprising: selecting, based on a tune away gap of an original carrier overlapping with an uplink transmission of the UE, one secondary component carrier (SCC) from one or more candidate SCCs of the UE; andtransmitting, to a network entity, a medium access control (MAC) - control element (MAC-CE) comprising a request for a change of an uplink carrier of the uplink transmission from the original carrier to the one SCC.

Images