Multiple SCG configuration in RRC inactive state

Abstract

Methods and apparatus for configuring a UE to store a plurality of SCG configurations while in an RRC inactive state. The apparatus requests, from each of the one or more target nodes, a validity time for each of the one or more candidate target SCG configurations for the UE. The apparatus transitions the UE to an RRC inactive state. The apparatus indicates the validity time for each of the one or more candidate target SCG configurations for each of the one or more target nodes.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. non-provisional patent application serial number 18 / 152,724, filed on January 10, 2023, entitled “MULTIPLE SCG CONFIGURATIONS INA RRC INACTIVE STATE,” which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to communication systems, and more particularly, to a user equipment (UE) configured to store multiple secondary cell group (SCG) configurations while in a radio resource control (RRC) inactive state.

[0004] introduction

[0005] Wireless communication systems are widely deployed to provide a variety of 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.

[0006] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continued mobile broadband evolution promulgated by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-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. Further improvements to 5G NR technology are needed. These improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the Invention

[0007] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of these aspects. This summary is not an extensive overview of all contemplated aspects. This summary does not identify key or critical elements of all aspects, nor does it delineate 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 will be presented later.

[0008] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a device at a UE. The apparatus may be a processor and / or modem at the UE or the UE itself. The apparatus receives an indication of a transition to a radio resource control (RRC) inactive state and a validity time for each candidate target secondary cell group (SCG) configuration in one or more candidate target secondary cell group (SCG) configurations. The apparatus performs measurements on one or more candidate target primary secondary cells (PSCells) associated with the one or more candidate target SCG configurations during the RRC inactive state.

[0009] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a device at a network node. The apparatus may be a processor and / or a modem at a network node or the network node itself. The apparatus requests a validity time for each candidate target secondary cell group (SCG) configuration for a user equipment (UE) from each of one or more target nodes. The apparatus transitions the UE to a radio resource control (RRC) inactive state. The apparatus indicates the validity time for each candidate target SCG configuration for each of the one or more target nodes in the one or more candidate target SCG configurations.

[0010] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a device at a network node. The apparatus may be a processor and / or a modem at the network node or the network node itself. The apparatus receives a request from a master node for a user equipment (UE) for a validity time configured for a candidate target secondary cell group (SCG) for the UE. The apparatus provides the validity time configured for the candidate target SCG for the UE to the master node for the UE.

[0011] To achieve the foregoing and related ends, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some illustrative features of one or more aspects. However, these features are indicative of only some of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0013] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0014] Figure 2B is a diagram illustrating an example of downlink (DL) channels within a subframe according to various aspects of the present disclosure.

[0015] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0016] Figure 2D is a diagram illustrating an example of uplink (UL) channels within a subframe according to various aspects of the present disclosure.

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

[0018] Figure 4 It is a call flow diagram of the signaling between the UE and the master node.

[0019] Figure 5 It is a call flow diagram of the signaling between the UE and the master node.

[0020] Figure 6A is a call flow diagram of signaling between the UE and the second master node.

[0021] Figure 6B is a call flow diagram of signaling between the UE and the second master node.

[0022] Figure 7 is a flow chart of a method of wireless communication.

[0023] Figure 8 is a flow chart of a method of wireless communication.

[0024] Figure 9 is a diagram illustrating an example of a hardware implementation for an example network entity.

[0025] Figure 10 is a flow chart of a method of wireless communication.

[0026] Figure 11 is a diagram illustrating an example of a hardware implementation for an example network entity.

[0027] Figure 12 is a flow chart of a method of wireless communication.

[0028] Figure 13 is a flow chart of a method of wireless communication.

[0029] Figure 14 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities. DETAILED DESCRIPTION

[0030] In a wireless communication system, dual connectivity (DC) allows a capable UE in RRC connected mode to simultaneously utilize resources from two cell groups, namely, a cell group associated with a master node (MN), referred to as a primary cell group (MCG), and a cell group associated with a secondary node (SN), referred to as a secondary cell group (SCG). The MN may be the base station or network entity to which the UE first connects, while the SN is the subsequent base station or network entity to which the UE may connect. DC may allow the UE to connect to the MCG via the MN and to the SCG via the SN.

[0031] Various aspects presented herein provide a configuration for a UE configured to store multiple SCG configurations while in an RRC inactive state. At least one advantage of the UE storing multiple SCG configurations is that upon resuming connectivity with the network, the UE can utilize one of the stored SCG configurations to resume DC operation in an efficient manner.

[0032] The detailed description set forth below in conjunction with the accompanying drawings is a description of various configurations and does not represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details to provide a thorough understanding of the various concepts. However, these concepts may be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0033] Several aspects of telecommunications systems are presented with reference to various apparatuses and methods. These apparatuses 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 can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0034] As an example, an element or any part of an element or any combination of elements can be implemented as a "processing system", which includes one or more processors. The example of a processor includes a microprocessor, a microcontroller, a graphics processing unit (GPU), a central processing unit (CPU), an application processor, a digital signal processor (DSP), a reduced instruction set computing (RISC) processor, a system on a chip (SoC), a baseband processor, a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, a gated logic component, a discrete hardware circuit and other suitable hardware configured to perform various functionalities described throughout this disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other terms, software should be broadly interpreted as meaning an instruction, an instruction set, a code, a code segment, a program code, a program, a subroutine, a software component, an application, a software application, a software package, a routine, a subroutine, an object, an executable file, a thread of execution, a process, a function or any combination thereof.

[0035] Thus, in one or more example aspects, specific 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 or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. A storage medium may be any available medium that can be accessed by a computer. As an example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these 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.

[0036] Although various aspects, specific implementations and / or use cases are described in this application by way of illustration of some examples, additional or different aspects, specific implementations and / or use cases may be produced in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein may be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, various aspects, specific implementations and / or use cases may be produced via integrated chip implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, devices that enable artificial intelligence (AI), etc.). Although some examples may or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Various aspects, specific implementations and / or use cases may be within the scope of chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the scope of aggregation, distribution or original equipment manufacturer (OEM) equipment or systems in conjunction with one or more technologies herein. In some actual settings, the equipment in conjunction with the various aspects and features described may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include multiple components for both analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The techniques described herein can be practiced in a wide variety of devices of various sizes, shapes, and configurations, including chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, and the like.

[0037] The deployment of a communication system (such as a 5G NR system) can be arranged in a variety of ways with various components or 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 network equipment (such as a base station (BS)) or one or more units (or one or more components) that perform base station functions can be implemented in a converged or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NRBS, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as a converged base station (also known as a standalone BS or a monolithic BS) or a decomposed base station.

[0038] A converged base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack that is physically or logically distributed between 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 across one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0039] Base station operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (a network configuration such as that initiated 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 virtually distributing functionality of at least one unit, which may enable flexibility in network design. Various units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0040] Figure 1 FIG1 is a diagram 100 illustrating an example of a wireless communication system and access network. The illustrated wireless communication system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110, which may 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. The CU 110 may communicate with one or more DUs 130 via corresponding midhaul links, such as the F1 interface. The DU 130 may communicate with one or more RUs 140 via corresponding fronthaul links. The RU 140 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0041] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO framework 105) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller that provides instructions to the communication interfaces of these units, may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive signals or transmit signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive and / or transmit signals to one or more of the other units via a wireless transmission medium.

[0042] In some aspects, the CU 110 may host one or more high-level control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is 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 specific implementations, the CU 110 may be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface such as an E1 interface. As needed, the CU 110 may be implemented to communicate with the DU 130 for network control and signaling.

[0043] The DU 130 may correspond to a logical unit that includes one or more base station functions for controlling 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 higher physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) based at least in part on a functional split, such as those defined by 3GPP. In some aspects, the DU 130 may also host one or more lower PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 130 or with control functions hosted by the CU 110.

[0044] Lower layer functionality may be implemented by one or more RUs 140. In some deployments, a RU 140 controlled by a DU 130 may correspond to a logical node that hosts RF processing functionality or low PHY layer functionality (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split, such as a lower layer functional split. In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, both real-time and non-real-time aspects of control plane communications and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the DU 130 and CU 110 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0045] The SMO framework 105 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 105 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 105 can be configured to interact with a cloud computing platform (such as Open Cloud (O-Cloud) 190) to perform network element lifecycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements may include, but are not limited to, the CU 110, DU 130, RU 140, and near-RT RIC 125. In some implementations, the SMO framework 105 can communicate with hardware aspects of the 4G RAN (such as the Open eNB (O-eNB) 111) via the O1 interface. Additionally, in some implementations, the SMO framework 105 can communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105 .

[0046] The non-RT RIC 115 may be configured to include logic that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 115 may be coupled to or in communication with the near-RT RIC 125 (e.g., via an A1 interface). The near-RT RIC 125 may be configured to include logic that enables near-real-time control and optimization of RAN elements and resources through data collection and actions over an interface (e.g., via an E2 interface) that connects one or more CUs 110, one or more DUs 130, or both, and an O-eNB with the near-RT RIC 125.

[0047] In some implementations, the non-RT RIC 115 may receive parameters or external enrichment information from an external server in order to generate an AI / ML model to be deployed in the near-RT RIC 125. This information may be utilized by the near-RT RIC 125 and may be received from a non-network data source or from a network function at the SMO framework 105 or the non-RT RIC 115. 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 in performance and employ AI / ML models to perform corrective actions through the SMO framework 105 (such as via reconfiguration of O1) or by creating RAN management policies (such as A1 policies).

[0048] At least one of the CU 110, DU 130, and RU 140 may be referred to as a base station 102. Thus, the base station 102 may include one or more of the CU 110, DU 130, and RU 140 (each component is indicated by a dotted line to indicate that 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 the UE 104. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network that includes both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group called a closed subscriber group (CSG). The communication link between the RU 140 and the UE 104 may include uplink (UL) (also known as reverse link) transmissions from the UE 104 to the RU 140 and / or downlink (DL) (also known as forward link) transmissions from the RU 140 to the UE 104. The communication link may utilize multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be over one or more carriers. The base station 102 / UE 104 may utilize spectrum of up to Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.) bandwidth for each carrier allocated in a carrier aggregation for a total of up to Yx MHz (x component carriers) for transmission in each direction. These carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL compared to UL). The component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0049] Some UEs 104 may communicate with each other using device-to-device (D2D) communication links 158. The D2D communication links 158 may use DL / UL wireless wide area network (WWAN) spectrum. The D2D communication links 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 accomplished through various wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0050] The wireless communication system may also include a Wi-Fi AP 150 that communicates with a UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in the 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the UE 104 / AP 150 may perform a clear channel assessment (CCA) to determine whether the channel is available before communicating.

[0051] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, 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 (interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0052] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz–24.25 GHz). Frequency bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation to more than 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.

[0053] In view of the above, unless otherwise specified, if the term "sub-6 GHz" or the like is used herein, it may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specified, if the term "millimeter wave" or the like is used herein, it may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

[0054] Base station 102 and UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. Base station 102 may transmit beamformed signals 182 to UE 104 in one or more transmit directions. UE 104 may receive beamformed signals from base station 102 in one or more receive directions. UE 104 may also transmit beamformed signals 184 to base station 102 in one or more transmit directions. Base station 102 may receive beamformed signals from UE 104 in one or more receive directions. Base station 102 / UE 104 may perform beam training to determine the optimal receive and transmit directions for each of base station 102 / UE 104. The transmit and receive directions of base station 102 may or may not be the same. The transmit and receive directions of UE 104 may or may not be the same.

[0055] The base station 102 may include and / or be referred to as a gNB, a Node B, an 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 transmit / receive point (TRP), a network node, a network entity, a network equipment, or some other suitable terminology. The base station 102 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, a converged (monolithic) base station having a baseband unit (BBU) (including a CU and a DU) and a RU, or as a disaggregated base station including one or more of a CU, a DU, and / or a RU. A collection of base stations that may include disaggregated base stations and / or converged base stations may be referred to as a next generation (NG) RAN (NG-RAN).

[0056] 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 a control node that handles signaling between the UE 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 identity handling, access authorization, and subscription management. The one or more location servers 168 are exemplified as including a gateway mobile location center (GMLC) 165 and a location management function (LMF) 166. However, in general, 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, LMF 166, Position Determination Entity (PDE), Serving Mobile Location Center (SMLC), Mobile Positioning Center (MPC), etc. The GMLC 165 and LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. The LMF 166 receives measurements and assistance information from the NG-RAN and UE 104 via the AMF 161 to calculate the location of the UE 104. The NG-RAN may utilize one or more positioning methods to determine the location of the UE 104. Locating the UE 104 may involve signal measurements, position estimates, and optionally velocity calculations based on these measurements. Signal measurements may be performed by the UE 104 and / or the serving base station 102. The measured signals 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), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / location systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR enhanced cell ID (NR E-CID) method, 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.

[0057] Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional device. Some of UE 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart rate monitors, etc.). UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more companion devices, such as in a device constellation arrangement. One or more of these devices may access the network collectively and / or individually.

[0058] Reference again Figure 1 In certain aspects, the UE 104 may include a validity component 198 configured to receive an indication of a transition to a radio resource control (RRC) inactive state and a validity time for each candidate target secondary cell group (SCG) configuration in one or more candidate target secondary cell group (SCG) configurations; and to perform measurements for one or more candidate target primary secondary cells (PSCells) associated with the one or more candidate target SCG configurations during the RRC inactive state.

[0059] Reference again Figure 1 In certain aspects, the base station 102 may include a validity component 199 configured to request a validity time for each of one or more candidate target secondary cell group (SCG) configurations for a user equipment (UE) from each of the one or more target nodes; transition the UE to a radio resource control (RRC) inactive state; and indicate a validity time for each of the one or more candidate target SCG configurations for each of the one or more target nodes.

[0060] Although the following description may focus 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.

[0061] Figure 2AFIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2D FIG280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL, or may be time division duplex (TDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL. Figure 2A 、 Figure 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are all DL and all UL, respectively. The other slot formats 2-61 include a mix of DL, UL, and flexible symbols. The UE is configured with the slot format via the received slot format indicator (SFI) (dynamically configured via DL control information (DCI) or semi-statically / statically configured via radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0062] Figures 2A to 2DThe frame structure is illustrated, and various aspects of the present disclosure are applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) can be divided into 10 equally sized subframes (1ms). Each subframe may include one or more time slots. A subframe may also include a mini-time slot, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For a normal CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 12 symbols. The symbols on the DL may be CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. The symbols on the UL 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 single-stream transmission). The number of time slots within a subframe is based on the CP and the parameter set. The parameter set defines the subcarrier spacing (SCS) (see Table 1). Symbol length / duration can be scaled with 1 / SCS.

[0063]

[0064] Table 1: Parameter set, SCS and CP

[0065] For normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Thus, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ time slots / subframe. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=4 is 240kHz. Symbol length / duration is inversely related to subcarrier spacing. Figures 2A to 2D An example is provided for a normal CP with 14 symbols per slot and a parameter set μ=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 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP may have a specific parameter set and CP (normal or extended).

[0066] A resource grid can be used to represent the frame structure. Each slot includes a resource block (RB) (also known as a physical RB (PRB)) that extends over 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.

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

[0068] Figure 2B Examples of various DL channels within a subframe of a frame are illustrated. 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 comprising six RE groups (REGs), each REG comprising 12 consecutive REs within an OFDM symbol of a RB. The PDCCH within a BWP may be referred to as a control resource set (CORESET). During a PDCCH monitoring opportunity on the CORESET, the UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space), where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies across the channel bandwidth. The primary synchronization signal (PSS) may be within symbol 2 of a specific subframe of the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and physical layer identity. The secondary synchronization signal (SSS) may be within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the physical 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 the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also known as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not sent over the PBCH (such as the system information block (SIB)), and paging messages.

[0069] like Figure 2CAs illustrated, some of the REs carry DM-RS (indicated as R for a specific configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may transmit the DM-RS of the physical uplink control channel (PUCCH) and the DM-RS of the physical uplink shared channel (PUSCH). The PUSCH DM-RS may be transmitted in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is transmitted and depending on the specific PUCCH format used, the PUCCH DM-RS may be transmitted in different configurations. The UE may transmit a sounding reference signal (SRS). The SRS may be transmitted in the last symbol of the subframe. The SRS may have a comb structure, and the UE may transmit the SRS on one of the teeth of the comb. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

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

[0071] Figure 33 is a block diagram of a base station 310 in an access network communicating with a UE 350. 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 2 includes 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, SIB), 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 delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), resegmentation 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.

[0072] The transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functionality associated with various signal processing functions. Layer 1, which includes the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping onto the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), and M-order quadrature amplitude modulation (M-QAM)). The coded and modulated symbols are then separated into parallel streams. Each stream is then mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time-domain OFDM symbol stream. The OFDM stream is spatially pre-coded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. The channel estimates may be derived from a reference signal and / 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 using a corresponding spatial stream for transmission.

[0073] At the UE 350, each receiver 354Rx receives a signal via its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to a 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 can 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 can be combined into a single OFDM symbol stream by the RX processor 356. 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, as well as the reference signal, are recovered and demodulated by determining the most likely signal constellation point transmitted by the base station 310. These soft decisions can be based on channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by base station 310. The data and control signals are then provided to a controller / processor 359, which implements layer 3 and layer 2 functionality.

[0074] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The 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, decryption, 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.

[0075] Similar to the functionality described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation 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.

[0076] Channel estimates derived by the channel estimator 358 based on 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 antennas 352 via separate transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

[0077] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318Rx receives a signal through its corresponding antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 370.

[0078] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The 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, decryption, header decompression, and 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.

[0079] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform a combined Figure 1 Aspects of the effectiveness component 198.

[0080] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform a combined Figure 1 Aspects of the effectiveness component 199.

[0081] In a wireless communication system, dual connectivity (DC) allows a capable UE in RRC connected mode to utilize resources from two cell groups simultaneously, i.e., a cell group associated with the MN, called the MCG, and a cell group associated with the SN, called the SCG. The MN and / or the SN may include a base station or any other network node or network entity described herein. The UE may be connected to each of the MN and the SN and transmit and / or receive data via both the MN and the SN. The MN may be the base station or network entity to which the UE first connects, and the SN is the subsequent base station or network entity to which the UE may connect. DC may allow the UE to connect to the MCG via the MN and to the SCG via the SN. Each of the MCG and the SCG may have a primary cell and may have multiple secondary cells. The primary cell of the MCG is the primary cell (PCell), and the primary cell of the SCG is the primary secondary cell (PSCell).

[0082] Various aspects presented herein provide a configuration for a UE configured to store multiple SCG configurations while in an RRC inactive state. At least one advantage of the UE storing multiple SCG configurations is that upon resuming connectivity with the network, the UE can utilize one of the stored SCG configurations to resume DC operation in an efficient manner. The UE can be configured with multiple SCG configurations based on a Conditional PSCell Addition (CPA) procedure, a Conditional PSCell Change (CPC) procedure, or an SCG Selective Activation procedure.

[0083] Figure 4 4 is a call flow diagram 400 of signaling between a UE 402 and a master node 404. The master node 404 may be configured to provide at least one cell. The UE 402 may be configured to communicate with the master node 404. For example, Figure 1 In the context of , master node 404 may correspond to base station 102 and UE 402 may correspond to at least UE 104. In another example, Figure 3 In the context of FIG, primary node 404 may correspond to base station 310 and UE 402 may correspond to UE 350. Diagram 400 also includes a secondary node (SN) 406, a target SN1 408, and a target SN2 410.

[0084] Diagram 400 shows the signaling flow for an example in which a UE resumes an RRC connection on the same primary node (eg, MN). Figure 4 This includes aspects in which a candidate target PSCell belongs to two target SNs (eg, target SN1 and target SN2). Figure 4 Aspects include examples in which the target SN1 and the target SN2 prepare candidate target PSCells for a first CPC configuration and a subsequent CPC configuration, respectively.

[0085] At 412, the network may perform a process for providing a configuration for SCG selective activation to the UE. UE 402 may receive the configuration for SCG selective activation from master node 404. At 414, master node 404 may determine to transition UE 402 to an RRC inactive state. For example, in instances where there is no traffic activity on an MCG or SCG associated with UE 402, master node 404 may determine to transition UE 402 to an RRC inactive state.

[0086] At 416, the master node 404 may request a validity time for each of the one or more candidate target SCG configurations for the UE. The master node may request a validity time for each of the one or more target SCG configurations for the UE from each of the one or more target nodes (e.g., 408, 410). Each of the one or more target nodes may obtain a request for the one or more candidate target SCG configurations from the master node. In an instance in which the master node determines that the UE should maintain information about the candidate target PSCell and its associated SCG and MCG configurations, the master node may request a validity time for each of the one or more candidate target SCG configurations. The validity time for the candidate target SCG configuration indicates a time for which the target SN may reserve corresponding resources for the UE.

[0087] At 418, the master node may obtain a validity time for each of the one or more candidate target SCG configurations for the UE. The master node may obtain a validity time for each of the one or more candidate target SCG configurations for the UE from each of the one or more target nodes. Each of the one or more target nodes may provide the master node with a corresponding validity time for each of the one or more candidate target SCG configurations for the UE. In some aspects, one or more of the one or more target nodes (e.g., 408, 410) may provide the one or more candidate target SCG configurations for the UE.

[0088] At 420, the master node may transition the UE 402 to an RRC inactive state. If there is no traffic activity on a master cell group (MCG) or SCG associated with the UE, the master node may transition the UE to an RRC inactive state. The master node may transition the UE to an RRC inactive state by providing an RRC release message to the UE. The UE may receive an indication of transitioning to an RRC inactive state. For example, the master node may provide an RRC release message to the UE commanding the UE to transition to an RRC inactive state. The UE may receive an RRC release message from the master node. At 422, the UE may transition to an RRC inactive state in response to receiving an indication of transitioning to an RRC inactive state. In some aspects, the RRC release message may include a validity time for a candidate target SCG configuration for the UE. The validity time for the candidate target SCG configuration provided to the UE by the master node may include a validity time obtained by the master node from each of one or more target nodes (e.g., 408, 410). The UE may receive a validity time for each candidate target SCG configuration in the candidate target SCG configuration from the master node. In some aspects, the RRC release message may include a configuration for measurements to be performed while the UE is in the RRC inactive state. In some aspects, the master node may determine a validity time for an associated MCG configuration and provide a corresponding validity time based on a validity time for an associated SCG configuration obtained from one or more target nodes. In some aspects, the RRC release message may include an early measurement configuration for configuring the UE to perform measurements while in the RRC inactive state.

[0089] At 424, the UE may maintain the candidate target SCG configuration while in the RRC inactive state. The UE may maintain the candidate target SCG configuration until the associated validity time has expired. When the validity time expires, the UE may discard the candidate target SCG configuration. The UE may maintain the candidate target SCG configuration and the associated target MCG configuration for the duration of the validity time of the candidate target SCG configuration. In some aspects, the UE may perform measurements for one or more candidate target PSCells associated with the one or more candidate target SCG configurations. The UE may perform measurements for one or more candidate target PSCells associated with the one or more candidate target SCG configurations during the RRC inactive state. For example, while the UE is in the RRC inactive state, the UE may measure one or more candidate target PSCells associated with the one or more target SCG configurations.

[0090] At 426, the UE may initiate an RRC recovery procedure. For example, the UE may send an RRC recovery request to the master node. The master node may obtain the RRC recovery request from the UE. In instances where the UE has data to send or is responding to being paged by the network, the UE may initiate an RRC recovery procedure.

[0091] In some aspects, for example, in 428, the UE may select a candidate target PSCell from among those PSCells whose validity time has not expired based on measurements performed according to an early measurement configuration. For example, at 430, the master node may provide an RRC recovery indication to the UE. The UE may receive an RRC recovery indication from the master node. The RRC recovery indication may include a security counter associated with a corresponding candidate target SCG configuration in one or more candidate target SCG configurations. The master node may provide the security counter to the UE. The master node may provide a security counter associated with a corresponding candidate target SCG configuration corresponding to a candidate target primary and secondary cell (PSCell) in one or more candidate target SCG configurations in response to a request to transition from an RRC inactive state to an RRC connected state. In some aspects, the security counter may be provided within the RRC recovery indication that transitions the UE from an RRC inactive state to an RRC connected state.

[0092] At 432, the UE may apply the candidate target SCG configuration. The UE may apply the candidate target SCG configuration based on measurements obtained when performing measurements based on the earlier measurement configuration while in the RRC inactive state. The UE may select the candidate target PSCell from among those PSCells whose validity time has not expired and based on measurements obtained when performing measurements based on the earlier measurement configuration while in the RRC inactive state. The UE may also apply the corresponding candidate target SCG configuration and may derive the SN key to be used based on the master node key and the security counter.

[0093] At 434, the UE may send an RRC recovery complete indication to the master node. The master node may obtain the RRC recovery complete indication from the UE. The RRC recovery complete indication may include a candidate target PSCell ID that identifies a candidate target PSCell selected by the UE for which the UE has restored the RRC connection. The RRC recovery complete indication may include a target node reconfiguration complete indication. At 436, in response to obtaining the RRC recovery complete indication from the UE, the master node may provide a target node reconfiguration complete indication to the target node based on the indicated candidate target PSCell ID provided by the UE. At 438, the UE may access the target PSCell and resume DC operation.

[0094] In some aspects, for example at 440, the master node may select a candidate target PSCell based on measurements performed according to an early measurement configuration. For example, at 442, in response to an RRC recovery request obtained from the UE, the master node may provide an RRC recovery indication to the UE. The UE may receive the RRC recovery indication from the master node. The RRC recovery indication may include a security counter associated with a corresponding candidate target SCG configuration in one or more candidate target SCG configurations. The master node may provide the security counter to the UE. The master node may provide a security counter associated with a corresponding candidate target SCG configuration corresponding to a candidate target primary and secondary cell (PSCell) in one or more candidate target SCG configurations in response to a request to transition from an RRC inactive state to an RRC connected state. In some aspects, the security counter may be provided within the RRC recovery indication that transitions the UE from the RRC inactive state to the RRC connected state. In some aspects, the RRC recovery indication may include a measurement report request. The measurement report request may be for measurements performed by the UE while in the RRC inactive state.

[0095] At 444, the UE may send a measurement report to the master node. The master node may obtain the measurement report from the UE. The measurement report may include measurements of one or more candidate target PSCells measured while the UE was in an RRC inactive state. The UE may send a measurement report of one or more candidate target PSCells based on the measurements performed while the UE was in an RRC inactive state. The UE may send the measurement report to the master node.

[0096] At 446, the master node may select a candidate target PSCell from those PSCells whose validity time has not expired based on the measurement report from the UE. The master node may perform a target node modification procedure and notify the selected candidate target PSCell as the selected candidate target PSCell for resumption with the UE.

[0097] At 448, the master node may provide an ID of a candidate target PSCell for operating in the RRC connected state. The master node may provide the ID of the candidate target PSCell for operating in the RRC connected state to the UE. The UE may receive the ID of the candidate target PSCell for operating in the RRC connected state from the master node. The master node may provide the ID of the candidate target PSCell for operating in the RRC connected state based on the measurement report. In some aspects, the master node may provide the ID of the candidate target PSCell via Layer 1 (L1) or Layer 2 (L2) signaling or via RRC reconfiguration.

[0098] At 450, the UE may resume the RRC connection using the selected candidate target SCG configuration by applying the candidate target SCG configuration. The UE may resume the RRC connection using the selected candidate target SCG configuration associated with the received candidate target PSCell ID from the set of one or more candidate target SCG configurations whose validity time has not expired. In such instances, the master node may select a candidate target PSCell for operation in the RRC connected state based on the measurement report.

[0099] At 452, the UE may send an indication of RRC reconfiguration completion to the master node in response to applying the candidate target SCG configuration. The master node may receive the indication of RRC reconfiguration completion from the UE. At 454, the master node may then provide the target node reconfiguration completion indication to the selected target node. At 456, the UE may access the target PSCell and resume DC operation.

[0100] Figure 5 5 is a call flow diagram 500 of signaling between a UE 502 and a master node 504. The master node 504 may be configured to provide at least one cell. The UE 502 may be configured to communicate with the master node 504. For example, Figure 1 In the context of , master node 504 may correspond to base station 102 and UE 502 may correspond to at least UE 104. In another example, Figure 3 In the context of , master node 504 may correspond to base station 310 and UE 502 may correspond to UE 350. Diagram 500 also includes a secondary node (SN) 506, a target SB1 508, a target SN2 510, and a target master node 511.

[0101] Diagram 500 shows the signaling flow for an example where a UE resumes an RRC connection on a different primary node. The signaling flow is similar to Figure 4 For example, from Figure 4 The signals 412, 414, 416, 418, 420, 422 and 424 correspond to the signals from Figure 5 The signaling of 512, 514, 516, 518, 520, 522 and 524 is described in detail and is not reproduced herein to reduce repetition. Figure 5 The discussion will start on 526.

[0102] At 526, the UE may initiate an RRC recovery procedure. For example, the UE may send an RRC recovery request to a different master node (e.g., 511) other than master node 504. The different master node may obtain the RRC recovery request from the UE. In instances where the UE has data to send or in response to being paged by the network, the UE may initiate an RRC recovery procedure. However, in Figure 5 In one embodiment, the UE is resuming an RRC connection on a different primary node than the primary node that transitioned the UE to the RRC inactive state. In instances where the different primary node has a stronger signal or a higher quality signal than the original primary node, the UE may request to resume the RRC connection on the different primary node. The different primary node may have a stronger signal or a higher quality signal due in part to the UE's mobility. For example, the UE may have moved away from the original primary node, such that the different primary node provides an enhanced signal compared to the signal of the original primary node.

[0103] At 528, the different master node may provide a second request for the UE context. The different master node may provide the second request 504 for the UE context to the original or last master node. The original or last master node 504 may obtain the second request for the UE context from the different master node. The original or last master node may obtain the second request for the UE context from the different master node in response to the first request to transition from the RRC inactive state to the RRC connected state. In some aspects, the original or last master node may include the last serving node, and the UE requests to restore connection with the different master node.

[0104] At 530, the original or last master node may provide the UE context to the different master node. The UE context may include at least one of the following: a source secondary node ID (e.g., 506), one or more target node IDs (e.g., 508, 510), and a validity time for each candidate target SCG configuration associated with each of the one or more target nodes in the one or more candidate target SCG configurations.

[0105] In some aspects, such as Figure 6A In diagram 600 of , the UE may select a candidate target PSCell from among those PSCells whose validity time has not expired based on measurements performed according to an early measurement configuration. For example, at 602, different secondary nodes may provide an RRC recovery indication to the UE. The UE may receive the RRC recovery indication from different master nodes. The RRC recovery indication may include a security counter associated with a corresponding candidate target SCG configuration in one or more candidate target SCG configurations. Different master nodes may provide the security counter to the UE. Different master nodes may provide, in response to a request to transition from an RRC inactive state to an RRC connected state, a security counter associated with a corresponding candidate target SCG configuration corresponding to the candidate target PSCell in one or more candidate target SCG configurations. In some aspects, the security counter may be provided within the RRC recovery indication that transitions the UE from the RRC inactive state to the RRC connected state.

[0106] At 604, the UE may apply the candidate target SCG configuration. The UE may apply the candidate target SCG configuration based on measurements obtained when performing measurements based on the earlier measurement configuration while in the RRC inactive state. The UE may select the candidate target PSCell from among those PSCells whose validity time has not expired and based on measurements obtained when performing measurements based on the earlier measurement configuration while in the RRC inactive state. The UE may also apply the corresponding candidate target SCG configuration and may derive the SN key to be used based on the master node key and the security counter.

[0107] At 606, the UE may send an RRC recovery complete indication to a different master node. The different master node may obtain the RRC recovery complete indication from the UE. The RRC recovery complete indication may include a candidate target PSCell ID, which identifies a candidate target PSCell selected by the UE, for which the UE has restored the RRC connection. The RRC recovery complete indication may include a target node reconfiguration complete indication. At 608, in response to obtaining the RRC recovery complete indication from the UE, the different master node may provide a target node reconfiguration complete indication to the target node based on the indicated candidate target PSCell ID provided by the UE. At 610, the UE may access the target PSCell and resume DC operation.

[0108] In some aspects, such as Figure 6B At 620 of the diagram, different master nodes may select a candidate target PSCell based on measurements performed according to an early measurement configuration. For example, at 622, in response to an RRC recovery request obtained from the UE, different master nodes may provide an RRC recovery indication to the UE. The UE may receive the RRC recovery indication from different master nodes. The RRC recovery indication may include a security counter associated with a corresponding candidate target SCG configuration in one or more candidate target SCG configurations. Different master nodes may provide the security counter to the UE. Different master nodes may provide a security counter associated with a corresponding candidate target SCG configuration corresponding to the candidate target PSCell in one or more candidate target SCG configurations in response to a request to transition from an RRC inactive state to an RRC connected state. In some aspects, the security counter may be provided within the RRC recovery indication that transitions the UE from the RRC inactive state to the RRC connected state. In some aspects, the RRC recovery indication may include a measurement report request. The measurement report request may be for measurements performed by the UE while in the RRC inactive state.

[0109] At 624, the UE may send measurement reports to different master nodes. The different master nodes may obtain measurement reports from the UE. The measurement reports may include measurements of one or more candidate target PSCells measured while the UE was in an RRC inactive state. The UE may send measurement reports of one or more candidate target PSCells based on the measurements performed while the UE was in an RRC inactive state. The UE may send measurement reports to different master nodes.

[0110] At 626, the different master nodes may provide the ID of the candidate target PSCell for operating in the RRC connected state. The different master nodes may provide the ID of the candidate target PSCell for operating in the RRC connected state to the UE. The UE may receive the ID of the candidate target PSCell for operating in the RRC connected state from the different master nodes. The different master nodes may provide the ID of the candidate target PSCell for operating in the RRC connected state based on the measurement report. In some aspects, the different master nodes may select the candidate target PSCell from those PSCells whose validity time has not expired based on the measurement report from the UE. In some aspects, the different master nodes may perform a target node modification procedure and notify the selected candidate target PSCell as the selected candidate target PSCell for recovery with the UE. In some aspects, the different master nodes may provide the ID of the candidate target PSCell via Layer 1 (L1) or Layer 2 (L2) signaling or via RRC reconfiguration.

[0111] At 628, the UE may resume the RRC connection using the selected candidate target SCG configuration by applying the candidate target SCG configuration. The UE may resume the RRC connection using the selected candidate target SCG configuration associated with the received candidate target PSCell ID from the set of one or more candidate target SCG configurations whose validity time has not expired. In such instances, different master nodes may select a candidate target PSCell for operation in the RRC connected state based on the measurement report.

[0112] At 630, the UE may send an indication of RRC reconfiguration completion to the different master node in response to applying the candidate target SCG configuration. The different master node may receive the indication of RRC reconfiguration completion from the UE. At 632, the different master node may then provide the target node reconfiguration completion indication to the selected target node. At 634, the UE may access the target PSCell and resume DC operation.

[0113] Figure 7700 is a flow chart of a method for wireless communication at a master node. The method may be performed by a base station (e.g., base station 102; network entity 902). One or more of the illustrated operations may be omitted, swapped, or performed simultaneously. The method may configure a UE to store multiple SCG configurations when in an RRC inactive state, allowing the UE to efficiently resume DC operation based on an SCG configuration from the stored multiple SCG configurations.

[0114] At 702, the master node may request a validity time for each of one or more candidate target SCG configurations for the UE, such as in conjunction with Figure 4 or Figure 5 For example, 702 may be performed by the validity component 199 of the network entity 902. The master node may request a validity time for each of the one or more target SCG configurations for the UE from each of the one or more target nodes.

[0115] At 704, the master node may determine to transition the UE to an RRC inactive state, such as in conjunction with Figure 4 or Figure 5 For example, 704 may be performed by the validity component 199 of the network entity 902. If there is no traffic activity on a master cell group (MCG) or SCG associated with the UE, the master node may determine to transition the UE to the RRC inactive state.

[0116] At 706, the master node may indicate a validity time for each of the one or more candidate target SCG configurations for each of the one or more target nodes, such as in conjunction with Figure 4 or Figure 5 As shown. For example, 706 may be performed by the validity component 199 of the network entity 902. The master node may indicate to the UE the validity time for each target SCG configuration in the one or more target SCG configurations. In some aspects, an indication of the validity time of each candidate target SCG configuration for each of the one or more target nodes in the one or more candidate target SCG configurations may be included in the RRC release indication. The RRC release indication may also include instructions for measuring one or more candidate target primary secondary cells (PSCells) associated with the one or more candidate target SCG configurations during the RRC inactive state. The RRC release indication may be provided to the UE by the master node so that the UE is informed of the validity time of each candidate target SCG configuration for each of the one or more target nodes in the one or more candidate target SCG configurations, and may measure one or more PSCells associated with the one or more candidate target SCG configurations when in the RRC inactive state.

[0117] Figure 8 800 is a flow chart of a method for wireless communication. The method may be performed by a base station (e.g., base station 102; network entity 902). One or more of the illustrated operations may be omitted, swapped, or performed simultaneously. The method may configure a UE to store multiple SCG configurations when in an RRC inactive state, allowing the UE to efficiently resume DC operation based on an SCG configuration from the stored multiple SCG configurations.

[0118] At 802, the master node may request a validity time for each of one or more candidate target SCG configurations for the UE, such as in conjunction with Figure 4 or Figure 5 For example, 802 may be performed by the validity component 199 of the network entity 902. The master node may request a validity time for each of the one or more target SCG configurations for the UE from each of the one or more target nodes.

[0119] At 804, the master node may obtain a validity time for each of the one or more candidate target SCG configurations for the UE, such as in conjunction with Figure 4 or Figure 5 For example, 804 may be performed by the validity component 199 of the network entity 902. The master node may obtain, from each of the one or more target nodes, a validity time for each of the one or more candidate target SCG configurations for the UE.

[0120] At 806, the master node may determine to transition the UE to an RRC inactive state, such as in conjunction with Figure 4 or Figure 5 As shown. For example, 806 can be performed by the validity component 199 of the network entity 902. If there is no traffic activity on the master cell group (MCG) or SCG associated with the UE, the master node can determine to transition the UE to the RRC inactive state. In some aspects, upon determining to transition the UE to the RRC inactive state, the master node can provide an RRC release indication to the UE at 807, such as in conjunction with Figure 4 or Figure 5 shown.

[0121] At 808, the master node may indicate a validity time for each candidate target SCG configuration for each of the one or more target nodes in the one or more candidate target SCG configurations, such as in conjunction with Figure 4 or Figure 5As shown. For example, 808 may be performed by the validity component 199 of the network entity 902. The master node may indicate to the UE the validity time for each target SCG configuration in the one or more target SCG configurations. In some aspects, an indication of the validity time of each candidate target SCG configuration for each of the one or more target nodes in the one or more candidate target SCG configurations may be included in the RRC release indication. The RRC release indication may also include instructions for measuring one or more candidate target primary and secondary cells (PSCells) associated with the one or more candidate target SCG configurations during the RRC inactive state. The RRC release indication may be provided to the UE by the master node so that the UE is informed of the validity time of each candidate target SCG configuration for each of the one or more target nodes in the one or more candidate target SCG configurations, and may measure one or more PSCells associated with the one or more candidate target SCG configurations when in the RRC inactive state.

[0122] At 810, the master node may provide a security counter associated with a corresponding candidate target SCG configuration in one or more candidate target SCG configurations, such as in conjunction with Figure 4 As shown. For example, 810 may be performed by the validity component 199 of the network entity 902. The master node may provide a security counter to the UE. The master node may provide a security counter associated with a corresponding candidate target SCG configuration corresponding to a candidate target primary and secondary cell (PSCell) in one or more candidate target SCG configurations in response to a request to transition from an RRC inactive state to an RRC connected state. The UE may send a request to the master node to transition from an RRC inactive state to an RRC connected state. In some aspects, the security counter may be provided within an RRC recovery indication that transitions the UE from an RRC inactive state to an RRC connected state.

[0123] At 812, the master node may obtain the ID of the candidate target PSCell, such as Figure 4 For example, 812 may be performed by the validity component 199 of the network entity 902. The master node may obtain the ID of the candidate target PSCell selected by the UE for operation in the RRC connected state.

[0124] At 814, the master node may obtain measurement reports of one or more candidate target PSCells, such as Figure 4 For example, 814 may be performed by the validity component 199 of the network entity 902. The master node may obtain measurement reports of one or more candidate target PSCells based on measurements performed when the UE is in the RRC inactive state.

[0125] At 816, the master node may provide an ID of a candidate target PSCell for operation in the RRC connected state, such as in conjunction with Figure 4 As shown. For example, 816 can be performed by the validity component 199 of the network entity 902. The master node can provide the ID of the candidate target PSCell for operation in the RRC connected state based on the measurement report. The measurement report includes measurements of one or more candidate target PSCells when the UE is in the RRC inactive state.

[0126] At 818, the master node may obtain a second request for UE context, such as in conjunction with Figure 5 As shown. For example, 818 can be performed by validity component 199 of network entity 902. The master node can obtain a second request for UE context from a second master node in response to the first request to transition from the RRC inactive state to the RRC connected state. In some aspects, the master node can include a last serving node, and the UE requests to resume connection with the second master node.

[0127] At 820, the master node may provide the UE context to the second master node, such as in conjunction with Figure 5 For example, 820 may be performed by the validity component 199 of the network entity 902. The UE context may include at least one of the following: a source secondary node ID, one or more target node IDs, and a validity time for each candidate target SCG configuration associated with each of the one or more target nodes in the one or more candidate target SCG configurations.

[0128] Figure 9Figure 900 illustrates an example hardware implementation for a network entity 902. Network entity 902 may be a base station (BS), a component of a BS, or may implement BS functionality. Network entity 902 may include at least one of a CU 910, a DU 930, or a RU 940. For example, depending on the layer functionality handled by component 199, network entity 902 may include a CU 910; both the CU 910 and the DU 930; each of the CU 910, the DU 930, and the RU 940; the DU 930; both the DU 930 and the RU 940; or the RU 940. CU 910 may include a CU processor 912. CU processor 912 may include on-chip memory 912′. In some aspects, CU 910 may also include an additional memory module 914 and a communication interface 918. CU 910 communicates with DU 930 via a midhaul link, such as an F1 interface. DU 930 may include a DU processor 932. The DU processor 932 may include on-chip memory 932'. In some aspects, the DU 930 may also include an additional memory module 934 and a communication interface 938. The DU 930 communicates with the RU 940 via a fronthaul link. The RU 940 may include a RU processor 942. The RU processor 942 may include on-chip memory 942'. In some aspects, the RU 940 may also include an additional memory module 944, one or more transceivers 946, an antenna 980, and a communication interface 948. The RU 940 communicates with the UE 104. The on-chip memories 912', 932', 942' and the additional memory modules 914, 934, 944 may each be considered a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. Each of the processors 912, 932, 942 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the corresponding processor, the software enables the processor to perform the various functions described above. The computer-readable medium / memory may also be used to store data that is manipulated by the processor when executing software.

[0129] As discussed above, component 199 is configured to request a validity time for each of one or more candidate target SCG configurations for the UE from each of one or more target nodes; transition the UE to an RRC inactive state; and indicate a validity time for each of the one or more candidate target SCG configurations for each of the one or more target nodes. Component 199 may be within one or more processors of one or more of CU 910, DU 930, and RU 940. Component 199 may be one or more hardware components specifically configured to perform the stated process / algorithms, implemented by one or more processors configured to perform the stated process / algorithms, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. The network entity 902 may include a variety of components configured for various functions. In one configuration, the network entity 902 includes a component for requesting a validity time for each of the one or more candidate target SCG configurations for the UE from each of the one or more target nodes. The network entity includes a component for transitioning the UE to an RRC inactive state. The network entity includes a component for indicating a validity time of each candidate target SCG configuration for each of one or more target nodes in one or more candidate target SCG configurations. The network entity includes a component for obtaining a validity time of each candidate target SCG configuration for the one or more candidate target SCG configurations for the UE from each of the one or more target nodes. The network entity also includes a component for providing an RRC release indication to the UE. The indication of the validity time of each candidate target SCG configuration for each of the one or more target nodes in the one or more candidate target SCG configurations is included within the RRC release. The network entity also includes a component for providing a security counter associated with a corresponding candidate target SCG configuration corresponding to a candidate target PSCell in the one or more candidate target SCG configurations in response to a request to transition from the RRC inactive state to the RRC connected state. The network entity also includes a component for obtaining an ID of a candidate target PSCell selected by the UE for operation in the RRC connected state. The network entity further includes means for obtaining measurement reports of one or more candidate target PSCells based on measurements performed while the UE is in an RRC inactive state. The network entity further includes means for providing IDs of candidate target PSCells for operation in an RRC connected state based on the measurement reports. The network entity further includes means for obtaining a second request for a UE context from a second master node in response to the first request to transition from the RRC inactive state to the RRC connected state.The network entity also includes a component for providing a UE context to the second primary node, the UE context including at least one of the following: a source secondary node ID, one or more target node IDs, and a validity time for each candidate target SCG configuration associated with each of the one or more target nodes in the one or more candidate target SCG configurations. The component may be a component 199 of the network entity 902 configured to perform the functions recited by the component. As described above, the network entity 902 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Therefore, in one configuration, the component may be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions recited by the component.

[0130] Figure 10 1000 is a flow chart of a method for wireless communication at a secondary node. The method may be performed by a base station (e.g., base station 102a; network entity 1102). One or more of the illustrated operations may be omitted, swapped, or performed simultaneously. The method may allow a UE to efficiently resume DC operation based on multiple SCG configurations stored at the UE while in an RRC inactive state.

[0131] At 1002, the secondary node may obtain a request for a validity time for a candidate target SCG configuration for the UE, such as in conjunction with Figure 4 or Figure 5 For example, 1002 may be performed by the validity component 197 of the network entity 1102. The secondary node may obtain a request for a validity time for a candidate target SCG configuration for the UE from the primary node of the UE.

[0132] At 1004, the secondary node may provide a validity time for a candidate target SCG configuration for the UE, such as in conjunction with Figure 4 or Figure 5 For example, 1004 may be performed by the validity component 197 of the network entity 1102. The secondary node may provide the primary node for the UE with the validity time configured for the candidate target SCG for the UE.

[0133] Figure 11Diagram 1100 illustrates an example hardware implementation for a network entity 1102. Network entity 1102 may be a base station (BS), a component of a BS, or may implement BS functionality. Network entity 1102 may include at least one of a CU 1110, a DU 1130, or a RU 1140. For example, depending on the layer functionality handled by component 199, network entity 1102 may include a CU 1110; both CU 1110 and DU 1130; each of CU 1110, DU 1130, and RU 1140; DU 1130; both DU 1130 and RU 1140; or RU 1140. CU 1110 may include a CU processor 1112. CU processor 1112 may include on-chip memory 1112′. In some aspects, CU 1110 may also include an additional memory module 1114 and a communication interface 1118. The CU 1110 communicates with the DU 1130 via a midhaul link, such as the F1 interface. The DU 1130 may include a DU processor 1132. The DU processor 1132 may include on-chip memory 1132′. In some aspects, the DU 1130 may also include an additional memory module 1134 and a communication interface 1138. The DU 1130 communicates with the RU 1140 via a fronthaul link. The RU 1140 may include a RU processor 1142. The RU processor 1142 may include on-chip memory 1142′. In some aspects, the RU 1140 may also include an additional memory module 1144, one or more transceivers 1146, an antenna 1180, and a communication interface 1148. The RU 1140 communicates with the UE 104. The on-chip memories 1112′, 1132′, 1142′ and the additional memory modules 1114, 1134, 1144 may each be considered a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. Each of processors 1112, 1132, and 1142 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the corresponding processor, the software causes the processor to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0134] As discussed above, component 199 is configured to obtain a request for a validity time for a candidate target SCG configuration for the UE from the master node of the UE; and provide the validity time for the candidate target SCG configuration for the UE to the master node for the UE. Component 199 may be within one or more processors of one or more of CU 1110, DU 1130, and RU 1140. Component 199 may be one or more hardware components that are specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to perform the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. The network entity 1102 may include a variety of components configured for various functions. In one configuration, the network entity 1102 includes a component for receiving a request for a validity time for a candidate target SCG configuration for the UE from the master node of the UE. The network entity includes a component for providing the validity time for the candidate target SCG configuration for the UE to the master node of the UE. A means may be a component 199 of the network entity 1102 configured to perform the functions recited by the means. As described above, the network entity 1102 may include the TX processor 316, the RX processor 370, and the controller / processor 375. Thus, 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.

[0135] Figure 12 1200 is a flow chart of a method for wireless communication. The method may be performed by a UE (e.g., UE 104; device 1404). One or more of the illustrated operations may be omitted, swapped, or performed simultaneously. The method may configure the UE to store multiple SCG configurations when in an RRC inactive state, allowing the UE to efficiently resume DC operation based on an SCG configuration from the stored multiple SCG configurations.

[0136] At 1202, the UE may receive an indication of transitioning to an RRC inactive state and a validity time for each of one or more candidate target SCG configurations, such as in conjunction with Figure 4 or Figure 5 For example, 1202 may be performed by the validity component 198 of the apparatus 1404. The UE may receive an indication of transitioning to the RRC inactive state and a validity time for each of the one or more candidate target SCG configurations from the master node.

[0137] At 1204, the UE may perform measurements on one or more candidate target PSCells associated with one or more candidate target SCG configurations, such as in conjunction with Figure 4 or Figure 5 As shown. For example, 1204 can be performed by the validity component 198 of the device 1404. The UE can perform measurements on one or more candidate target PSCells associated with one or more candidate target SCG configurations during the RRC inactive state. For example, when the UE is in the RRC inactive state, the UE can measure one or more candidate target PSCells associated with one or more target SCG configurations.

[0138] Figure 13 1300 is a flow chart of a method for wireless communication. The method may be performed by a UE (e.g., UE 104; apparatus 1404). One or more of the illustrated operations may be omitted, swapped, or performed simultaneously. The method may configure the UE to store multiple SCG configurations while in an RRC inactive state, allowing the UE to efficiently resume DC operation based on an SCG configuration from the stored multiple SCG configurations.

[0139] At 1302, the UE may receive an indication of transitioning to an RRC inactive state and a validity time for each of one or more candidate target SCG configurations, such as in conjunction with Figure 4 or Figure 5 For example, 1302 may be performed by the validity component 198 of the apparatus 1404. The UE may receive an indication of transitioning to the RRC inactive state and a validity time for each of the one or more candidate target SCG configurations from the master node.

[0140] At 1304, the UE may perform measurements on one or more candidate target PSCells associated with one or more candidate target SCG configurations, such as in conjunction with Figure 4 or Figure 5 As shown. For example, 1304 can be performed by the validity component 198 of the device 1404. The UE can perform measurements on one or more candidate target PSCells associated with one or more candidate target SCG configurations during the RRC inactive state. For example, when the UE is in the RRC inactive state, the UE can measure one or more candidate target PSCells associated with one or more target SCG configurations.

[0141] At 1306, the UE may discard the candidate target SCG configuration, such as in conjunction with Figure 4 or Figure 5 For example, 1306 may be performed by the validity component 198 of the device 1404. The UE may maintain the candidate target SCG configuration for a duration of the corresponding validity time, and then discard the candidate target SCG configuration after expiration of the corresponding validity time.

[0142] At 1308, the UE may receive a security counter associated with a corresponding candidate target SCG configuration of the one or more candidate target SCG configurations, such as in conjunction with Figure 4 、 Figure 6A or Figure 6B As shown. For example, 1308 may be performed by the validity component 198 of the device 1404. The UE may receive a security counter associated with a corresponding candidate target SCG configuration corresponding to the candidate target PSCell in one or more candidate target SCG configurations. The UE may receive a security counter associated with a corresponding candidate target SCG configuration corresponding to the candidate target PSCell in one or more candidate target SCG configurations in response to sending a request to transition from an RRC inactive state to an RRC connected state. In some aspects, the security counter may be provided within an RRC recovery indication that transitions the UE from the RRC inactive state to the RRC connected state. The UE may receive an RRC recovery indication from the master node.

[0143] At 1310, the UE may utilize the selected candidate target SCG configuration to resume the RRC connection, such as in conjunction with Figure 4 For example, 1310 may be performed by the validity component 198 of the device 1404. The UE may resume the RRC connection using a selected candidate target SCG configuration from a set of one or more candidate target SCG configurations whose validity time has not expired. The UE may select the selected candidate target SCG configuration.

[0144] At 1312, the UE may send a measurement report of one or more candidate target PSCells, such as in conjunction with Figure 4 For example, 1312 may be performed by the validity component 198 of the apparatus 1404. The UE may send a measurement report of one or more candidate target PSCells based on measurements performed when the UE is in an RRC inactive state. The UE may send the measurement report to the master node.

[0145] At 1314, the UE may receive an ID of a candidate target PSCell for operation in the RRC connected state, such as in conjunction with Figure 4 For example, 1314 may be performed by validation component 198 of apparatus 1404. The UE may receive an ID of a candidate target PSCell for operation in an RRC connected state based on the measurement report provided to the master node.

[0146] At 1316, the UE may utilize the selected candidate target SCG configuration to resume the RRC connection, such as in conjunction with Figure 4As shown. For example, 1316 can be performed by validity component 198 of device 1404. The UE can resume the RRC connection using a selected candidate target SCG configuration associated with the received candidate target PSCell ID from a set of one or more candidate target SCG configurations whose validity time has not expired. In such an example, the master node can select a candidate target PSCell for operation in the RRC connected state based on the measurement report.

[0147] At 1318, the UE may utilize the selected candidate target SCG configuration to resume the RRC connection, such as in conjunction with Figure 6A As shown. For example, 1318 may be performed by the validity component 198 of the device 1404. The UE may restore the RRC connection using a selected candidate target SCG configuration from a set of one or more candidate target SCG configurations whose validity time has not expired. In such instances, the UE may select the selected candidate target SCG configuration. For example, the UE may select the selected candidate target SCG configuration based on measurements obtained when the UE is in an RRC inactive state. In some aspects, a request to transition from an RRC inactive state to an RRC connected state may be sent to a second master node instead of the master node. Because the second master node has a greater signal strength than the master node, the UE may send a request to transition to an RRC connected state to the second master node. The UE may receive a security counter from the second master node in response to sending a request to transition from an RRC inactive state to an RRC connected state. In some aspects, a selected candidate target PSCell associated with the candidate target SCG configuration selected by the UE is provided to the second master node.

[0148] At 1320, the UE may receive the selected candidate target SCG configuration, such as in conjunction with Figure 6B For example, 1320 may be performed by the validity component 198 of the apparatus 1404. The UE may receive, from the second master node, a selected candidate target SCG configuration from a set of one or more candidate target SCG configurations whose validity time has not expired.

[0149] At 1322, the UE may resume the RRC connection, such as in conjunction with Figure 6B As shown. For example, 1322 can be performed by the validity component 198 of the device 1404. The UE can utilize the selected candidate target SCG configuration to resume the RRC connection. In some aspects, the request to transition from the RRC inactive state to the RRC connected state can be sent to the second master node instead of the master node. In such aspects, the security counter can be received from the second master node.

[0150] Figure 1414 is a diagram illustrating an example of a hardware implementation for an apparatus 1404. The apparatus 1404 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1404 may include a cellular baseband processor 1424 (also referred to as a modem) coupled to one or more transceivers 1422 (e.g., a cellular RF transceiver). The cellular baseband processor 1424 may include on-chip memory 1424′. In some aspects, the apparatus 1404 may also include one or more subscriber identity module (SIM) cards 1420 and an application processor 1406 coupled to a secure digital (SD) card 1408 and a screen 1410. The application processor 1406 may include on-chip memory 1406′. In some aspects, the device 1404 may also include a Bluetooth module 1412, a WLAN module 1414, an SPS module 1416 (e.g., a GNSS module), one or more sensor modules 1418 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1426, a power source 1430, and / or a camera 1432. The Bluetooth module 1412, the WLAN module 1414, and the SPS module 1416 may include an on-chip transceiver (TRX) (or, in some cases, only a receiver (RX)). The Bluetooth module 1412, the WLAN module 1414, and the SPS module 1416 may include their own dedicated antennas and / or utilize an antenna 1480 for communication. The cellular baseband processor 1424 communicates with the UE 104 and / or RUs associated with the network entity 1402 via the transceiver 1422 via one or more antennas 1480. The cellular baseband processor 1424 and the application processor 1406 may each include computer-readable media / memory 1424', 1406', respectively. The additional memory module 1426 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1424', 1406', 1426 may be non-transitory. The cellular baseband processor 1424 and the application processor 1406 are each responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the cellular baseband processor 1424 / application processor 1406, this software enables the cellular baseband processor 1424 / application processor 1406 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 1424 / application processor 1406 when executing the software.The cellular baseband processor 1424 / application processor 1406 may be a component of the UE 350 and may include the 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 device 1404 may be a processor chip (modem and / or applications) and include only the cellular baseband processor 1424 and / or the application processor 1406, and in another configuration, the device 1404 may be the entire UE (e.g., see ). Figure 3 350) and includes additional modules of device 1404.

[0151] As discussed above, component 198 is configured to receive an indication of a transition to an RRC inactive state and a validity time for each of one or more candidate target SCG configurations; and, during the RRC inactive state, perform measurements for one or more candidate target PSCells associated with the one or more candidate target SCG configurations. Component 198 may be within the cellular baseband processor 1424, the application processor 1406, or both the cellular baseband processor 1424 and the application processor 1406. Component 198 may be one or more hardware components specifically configured to perform the stated processes / algorithms, implemented by one or more processors configured to perform the stated processes / algorithms, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, apparatus 1404 may include a variety of components configured for various functions. In one configuration, the apparatus 1404, and specifically the cellular baseband processor 1424 and / or the application processor 1406, includes means for receiving an indication of a transition to an RRC inactive state and a validity time for each of one or more candidate target SCG configurations. The apparatus includes means for performing measurements for one or more candidate target PSCells associated with the one or more candidate target SCG configurations during the RRC inactive state. The apparatus also includes means for discarding the candidate target SCG configurations after expiration of the corresponding validity time. The apparatus also includes means for receiving, in response to sending a request to transition from the RRC inactive state to the RRC connected state, a security counter associated with a corresponding candidate target SCG configuration of the one or more candidate target SCG configurations corresponding to the candidate target PSCell. The apparatus also includes means for resuming the RRC connection using a selected candidate target SCG configuration from a set of one or more candidate target SCG configurations whose validity time has not expired, wherein the UE selects the selected candidate target SCG configuration. The apparatus also includes means for sending a measurement report of the one or more candidate target PSCells based on the measurements performed while the UE was in the RRC inactive state. The apparatus further includes means for receiving, based on the measurement report, an ID of a candidate target PSCell for operation in an RRC connected state. The apparatus further includes means for resuming the RRC connection using the selected candidate target SCG configuration associated with the received candidate target PSCell ID from a set of one or more candidate target SCG configurations whose validity time has not expired. The apparatus further includes means for resuming the RRC connection using the selected candidate target SCG configuration from the set of one or more candidate target SCG configurations whose validity time has not expired, wherein the UE selects the selected candidate target SCG configuration.The apparatus further comprises a component for receiving, from a second master node, a selected candidate target SCG configuration from a set of one or more candidate target SCG configurations whose validity time has not expired. The apparatus further comprises a component for restoring the RRC connection using the selected candidate target SCG configuration. The component may be the component 198 of the apparatus 1404 configured to perform the functions recited by the component. As described above, the apparatus 1404 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, in one configuration, the component may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by the component.

[0152] Various aspects presented herein provide a configuration for a UE that is configured to store multiple SCG configurations while in an RRC inactive state. At least one advantage of the UE storing multiple SCG configurations is that, upon resuming connection with the network, the UE may utilize one of the stored SCG configurations to resume DC operation in an efficient manner. The primary node may provide the UE with a validity time for each candidate target SCG configuration for each of the one or more target nodes in the one or more candidate target SCG configurations. While in the RRC inactive state, the UE may maintain the one or more candidate target SCG configurations until the corresponding validity time has expired. The UE storing one or more candidate target SCG configurations while in the RRC inactive state may allow the UE to resume connection with the secondary node based on the one or more candidate target SCG configurations.

[0153] It should be understood that the specific order or hierarchy of blocks in the disclosed process / flowchart is merely illustrative of an exemplary method. It should be understood that the specific order or hierarchy of blocks in the process / flowchart may be rearranged based on design preferences. In addition, some blocks may be combined or omitted. The accompanying method claims provide elements of the various blocks in a sample order, but are not limited to the specific order or hierarchy provided.

[0154] The foregoing 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 apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the aspects described herein, but should be given the full scope consistent with the language claims. Unless otherwise specified, references to elements in the singular do not mean "one and only one", but "one or more". Terms such as "if", "when" and "while" do not imply a direct temporal relationship or reaction. That is, these phrases, such as "when...", do not mean immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that if the conditions are met, the action will occur, but there is no need for a specific or immediate time limit for the action to occur. The word "exemplary" is used herein to mean "used as an example, instance or illustration". Any aspect described as "exemplary" herein is not necessarily to be interpreted as preferred or having advantages over other aspects. Unless otherwise specified, 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, which may include multiple As, multiple Bs, or multiple Cs. 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 only A, only B, only C, A and B, A and C, B and C, or A, B, and C, where any such combination may include one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If a first device receives data from a second device or sends data to a second device, the data may be received / sent directly between the first device and the second device, or indirectly between the first device and the second device through a collection of devices. A device configured to "output" data (such as, transmit, signal, or message) may, for example, send the data with a transceiver, or may transmit the data to a device that sends the data. A device configured to "obtain" data (such as, transmit, signal, or message) may, for example, receive the data with a transceiver, or may obtain the data from a device that receives the data. All structural and functional equivalents of the elements of the various aspects described throughout this disclosure that are known or later become known to those of ordinary skill in the art are expressly incorporated herein by reference and are encompassed by the claims.Furthermore, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly recited in the claims. Words such as "module," "mechanism," "element," and "device" are not intended to replace the word "component." Thus, no claim element is to be construed as part-plus-function unless the element is explicitly recited using the phrase "means for..."

[0155] As used herein, the phrase "based on" should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be interpreted as "based at least on A" unless specifically stated differently.

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

[0157] Aspect 1 is a method for wireless communication at a master node, the method comprising: requesting a validity time for each candidate target SCG configuration in one or more candidate target SCG configurations for a UE from each of one or more target nodes; transitioning the UE to an RRC inactive state; and indicating to the UE the validity time for each candidate target SCG configuration in the one or more candidate target SCG configurations for each of the one or more target nodes.

[0158] Aspect 2 is a method according to aspect 1, the method further comprising: obtaining the validity time of each candidate target SCG configuration in the one or more candidate target SCG configurations for the UE from each of the one or more target nodes.

[0159] Aspect 3 is a method according to any one of Aspects 1 and 2, wherein the method further includes: transitioning the UE to the RRC inactive state further includes: providing an RRC release indication to the UE, wherein an indication of the validity time of each candidate target SCG configuration for each target node in the one or more target nodes in the one or more candidate target SCG configurations is included in the RRC release indication.

[0160] Aspect 4 is a method according to any one of Aspects 1 to 3, wherein the method further includes: the RRC release indication also includes instructions for measuring one or more candidate target PSCells associated with the one or more candidate target SCG configurations during the RRC inactive state.

[0161] Aspect 5 is a method according to any one of Aspects 1 to 4, further comprising: in response to a request to transition from the RRC inactive state to the RRC connected state, providing a security counter associated with a corresponding candidate target SCG configuration corresponding to a candidate target PSCell in the one or more candidate target SCG configurations.

[0162] Aspect 6 is a method according to any one of aspects 1 to 5, the method further comprising: the security counter is provided within an RRC recovery indication that transitions the UE from the RRC inactive state to the RRC connected state.

[0163] Aspect 7 is a method according to any one of aspects 1 to 6, the method further comprising: obtaining an ID of the candidate target PSCell selected by the UE for operating in the RRC connected state.

[0164] Aspect 8 is a method according to any one of Aspects 1 to 7, the method further comprising: obtaining measurement reports of one or more candidate target PSCells based on measurements performed when the UE is in the RRC inactive state; and providing an ID of the candidate target PSCell for operating in the RRC connected state based on the measurement report.

[0165] Aspect 9 is a method according to any one of Aspects 1 to 8, the method further comprising: obtaining a second request for a UE context from a second master node in response to a first request to transition from the RRC inactive state to the RRC connected state; and providing the UE context to the second master node, the UE context including at least one of the following: a source secondary node ID, one or more target node IDs, and the validity time for each candidate target SCG configuration associated with each of the one or more target nodes in the one or more candidate target SCG configurations.

[0166] Aspect 10 is a method according to any one of aspects 1 to 9, further comprising: the master node is a last serving node, and the UE requests to resume connection with the second master node.

[0167] Aspect 11 is an apparatus for wireless communication at a master node, the apparatus comprising at least one processor coupled to a memory and at least one transceiver, the at least one processor configured to implement any one of aspects 1 to 10.

[0168] Aspect 12 is an apparatus for wireless communication at a master node, the apparatus comprising means for implementing any one of aspects 1 to 10.

[0169] Aspect 13 is a computer-readable medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 1 to 10.

[0170] Aspect 14 is a method for wireless communication at a secondary node, the method comprising: receiving a request for a validity time of a candidate target SCG configuration for a UE from a primary node for the UE; and providing the validity time of the candidate target SCG configuration for the UE to the primary node for the UE.

[0171] Aspect 15 is an apparatus for wireless communication at a master node, the apparatus comprising at least one processor coupled to a memory and at least one transceiver, the at least one processor configured to implement aspect 14.

[0172] Aspect 16 is an apparatus for wireless communication at a master node, the apparatus comprising means for implementing aspect 14.

[0173] Aspect 17 is a computer-readable medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement aspect 14.

[0174] Aspect 18 is a method for wireless communication at a UE, the method comprising: receiving an indication of a transition to an RRC inactive state and a validity time for one or more candidate target SCG configurations; and performing measurements for one or more candidate target PSCells associated with the one or more candidate target SCG configurations during the RRC inactive state.

[0175] Aspect 19 is the method according to aspect 18, further comprising: discarding the candidate target SCG configuration after expiration of the corresponding validity time.

[0176] Aspect 20 is a method according to any one of Aspects 18 and 19, further comprising: in response to sending a request to transition from the RRC inactive state to the RRC connected state, receiving a security counter associated with a corresponding candidate target SCG configuration corresponding to a candidate target PSCell in the one or more candidate target SCG configurations.

[0177] Aspect 21 is a method according to any one of Aspects 18 to 20, the method further comprising: restoring the RRC connection using a selected candidate target SCG configuration from the set of one or more candidate target SCG configurations whose validity time has not expired, wherein the UE selects the selected candidate target SCG configuration.

[0178] Aspect 22 is a method according to any one of aspects 18 to 21, the method further comprising: the security counter is provided within an RRC resume indication that transitions the UE from the RRC inactive state to the RRC connected state.

[0179] Aspect 23 is a method according to any one of Aspects 18 to 22, the method further comprising: sending a measurement report of one or more candidate target PSCells based on the measurements performed when the UE is in the RRC inactive state; receiving the ID of the candidate target PSCell for operating in the RRC connected state based on the measurement report; and restoring the RRC connection using a selected candidate target SCG configuration associated with the received candidate target PSCell ID from the set of one or more candidate target SCG configurations whose validity time has not expired.

[0180] Aspect 24 is a method according to any one of Aspects 18 to 23, the method further comprising: the request to transition from the RRC inactive state to the RRC connected state is sent to a second master node, wherein the security counter is received from the second master node, and the method further comprises: restoring the RRC connection using a selected candidate target SCG configuration from the set of one or more candidate target SCG configurations whose validity time has not expired, wherein the UE selects the selected candidate target SCG configuration.

[0181] Aspect 25 is a method according to any one of aspects 18 to 24, the method further comprising: a selected candidate target PSCell associated with the candidate target SCG configuration selected by the UE is provided to the second master node.

[0182] Aspect 26 is a method according to any one of Aspects 18 to 25, the method further comprising: the request to transition from the RRC inactive state to the RRC connected state is sent to a second master node, wherein the security counter is received from the second master node, the method further comprising: receiving from the second master node a selected candidate target SCG configuration from the set of one or more candidate target SCG configurations whose validity time has not expired; and restoring the RRC connection using the selected candidate target SCG configuration.

[0183] Aspect 27 is an apparatus for wireless communication at a UE, the apparatus comprising: at least one processor coupled to a memory and at least one transceiver, the at least one processor configured to implement any one of aspects 18 to 26.

[0184] Aspect 28 is an apparatus for wireless communication at a UE, the apparatus comprising: means for implementing any one of aspects 18 to 26.

[0185] Aspect 29 is a computer-readable medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 18 to 26.

Claims

1. An apparatus for wireless communication at a master node, the apparatus comprising: Memory; and at least one processor coupled to the memory and, based at least in part on information stored in the memory, configured to: requesting, from each of the one or more target nodes, a validity time for each of one or more candidate target secondary cell group (SCG) configurations for a user equipment (UE); transitioning the UE to a radio resource control (RRC) inactive state; as well as The validity time of each candidate target SCG configuration for each target node in the one or more target nodes is indicated to the UE.

2. The apparatus according to claim 1, further comprising: A transceiver is coupled to the at least one processor.

3. The apparatus of claim 1 , wherein the at least one processor is configured to: The validity time for each of the one or more candidate target SCG configurations for the UE is obtained from each of the one or more target nodes.

4. The apparatus of claim 1 , wherein to transition the UE to the RRC inactive state, the at least one processor is configured to: An RRC release indication is provided to the UE, including an indication of the validity time for each candidate target SCG configuration in the one or more candidate target SCG configurations for each target node in the one or more target nodes within the RRC release indication.

5. The apparatus of claim 4, wherein the RRC release indication further comprises instructions for measuring one or more candidate target primary secondary cells (PSCells) associated with the one or more candidate target SCG configurations during the RRC inactive state.

6. The apparatus of claim 1 , wherein the at least one processor is configured to: In response to the request to transition from the RRC inactive state to the RRC connected state, a safety counter associated with a respective candidate target SCG configuration corresponding to a candidate target primary secondary cell (PSCell) among the one or more candidate target SCG configurations is provided.

7. The apparatus of claim 6, wherein the safety counter is provided within an RRC resume indication that transitions the UE from the RRC inactive state to the RRC connected state.

8. The apparatus of claim 6, wherein the at least one processor is configured to: An identifier (ID) of the candidate target PSCell selected by the UE for operation in the RRC connected state is obtained.

9. The apparatus of claim 6, wherein the at least one processor is configured to: obtaining measurement reports of one or more candidate target PSCells based on measurements performed while the UE is in the RRC inactive state; and An identifier (ID) of the candidate target PSCell for operating in the RRC connected state is provided based on the measurement report.

10. The apparatus of claim 1 , wherein the at least one processor is configured to: obtaining, in response to the first request to transition from the RRC inactive state to the RRC connected state, a second request for a UE context from a second master node; and The UE context is provided to the second master node, wherein the UE context includes at least one of the following: a source secondary node identifier (ID), one or more target node IDs, and the validity time of each candidate target SCG configuration associated with each of the one or more target nodes in the one or more candidate target SCG configurations.

11. The apparatus of claim 10, wherein the primary node is a last serving node, and the UE requests to resume connection with the second primary node.

12. A method for wireless communication at a master node, the method comprising: requesting, from each of the one or more target nodes, a validity time for each of one or more candidate target secondary cell group (SCG) configurations for a user equipment (UE); transitioning the UE to a radio resource control (RRC) inactive state; as well as The validity time of each candidate target SCG configuration for each target node in the one or more target nodes is indicated to the UE.

13. The method according to claim 12, further comprising: The validity time for each of the one or more candidate target SCG configurations for the UE is obtained from each of the one or more target nodes.

14. The method of claim 12, wherein transitioning the UE to the RRC inactive state further comprises: An RRC release indication is provided to the UE, including an indication of the validity time for each candidate target SCG configuration in the one or more candidate target SCG configurations for each target node in the one or more target nodes within the RRC release indication.

15. The method of claim 14, wherein the RRC release indication further comprises instructions for measuring one or more candidate target primary secondary cells (PSCells) associated with the one or more candidate target SCG configurations during the RRC inactive state.

16. The method according to claim 12, further comprising: In response to a request to transition from the RRC inactive state to the RRC connected state, a security counter associated with a corresponding candidate target SCG configuration corresponding to a candidate target primary secondary cell (PSCell) in the one or more candidate target SCG configurations is provided, wherein the security counter is provided within an RRC recovery indication for transitioning the UE from the RRC inactive state to the RRC connected state.

17. The method according to claim 16, further comprising: An identifier (ID) of the candidate target PSCell selected by the UE for operation in the RRC connected state is obtained.

18. The method according to claim 16, further comprising: obtaining measurement reports of one or more candidate target PSCells based on measurements performed while the UE is in the RRC inactive state; as well as An identifier (ID) of the candidate target PSCell for operating in the RRC connected state is provided based on the measurement report.

19. The method according to claim 12, further comprising: obtaining, in response to the first request to transition from the RRC inactive state to the RRC connected state, a second request for a UE context from a second master node; as well as The UE context is provided to the second master node, the UE context including at least one of: a source secondary node identifier (ID), one or more target node IDs, and the validity time of each candidate target SCG configuration associated with each of the one or more target nodes in the one or more candidate target SCG configurations, wherein the master node is the last serving node and the UE requests to resume the connection with the second master node.

20. An apparatus for wireless communication at a secondary node, the apparatus comprising: Memory; and at least one processor coupled to the memory and, based at least in part on information stored in the memory, configured to: receiving a request from a master node for a user equipment (UE) for a validity time configured for a candidate target secondary cell group (SCG) for the UE; and The validity time configured for the candidate target SCG for the UE is provided to the master node for the UE.

21. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and at least one processor coupled to the memory and, based at least in part on information stored in the memory, configured to: receiving an indication of transitioning to a radio resource control (RRC) inactive state and a validity time configured for one or more candidate target secondary cell groups (SCGs); as well as During the RRC inactive state, measurements are performed on one or more candidate target primary secondary cells (PSCells) associated with the one or more candidate target SCG configurations.

22. The apparatus according to claim 21, further comprising: A transceiver is coupled to the at least one processor.

23. The apparatus of claim 21 , wherein the at least one processor is configured to: The candidate target SCG configuration is discarded after expiration of the corresponding validity time.

24. The apparatus of claim 21 , wherein the at least one processor is configured to: In response to sending a request to transition from the RRC inactive state to the RRC connected state, a safety counter associated with a respective candidate target SCG configuration corresponding to a candidate target primary secondary cell (PSCell) of the one or more candidate target SCG configurations is received.

25. The apparatus of claim 24, wherein the at least one processor is configured to: The RRC connection is resumed using a selected candidate target SCG configuration from the set of one or more candidate target SCG configurations whose validity time has not expired, wherein the UE selects the selected candidate target SCG configuration.

26. The apparatus of claim 24, wherein the safety counter is provided within an RRC resume indication that transitions the UE from the RRC inactive state to the RRC connected state.

27. The apparatus of claim 24, wherein the at least one processor is configured to: sending measurement reports of one or more candidate target PSCells based on the measurements performed while the UE is in the RRC inactive state; receiving an identifier (ID) of the candidate target PSCell for operating in the RRC connected state based on the measurement report; as well as The RRC connection is resumed using a selected candidate target SCG configuration associated with the received candidate target PSCell ID from the set of one or more candidate target SCG configurations whose validity time has not expired.

28. The apparatus of claim 24, wherein the request to transition from the RRC inactive state to the RRC connected state is sent to a second master node, wherein the security counter is received from the second master node, wherein the at least one processor is configured to: The RRC connection is resumed using a selected candidate target SCG configuration from the set of one or more candidate target SCG configurations whose validity time has not expired, wherein the UE selects the selected candidate target SCG configuration.

29. The apparatus of claim 28, wherein a selected candidate target PSCell associated with the candidate target SCG configuration selected by the UE is provided to the second master node.

30. The apparatus of claim 24, wherein the request to transition from the RRC inactive state to the RRC connected state is sent to a second master node, wherein the security counter is received from the second master node, wherein the at least one processor is configured to: receiving, from the second master node, a selected candidate target SCG configuration from the set of one or more candidate target SCG configurations whose validity time has not expired; and The RRC connection is restored using the selected candidate target SCG configuration.

Images