Candidate cell configuration update for non-connected user equipments
By pre-providing candidate cell configurations to non-connected UEs, the transition from an inactive to a connected state is optimized, reducing overhead and latency, thus enhancing the quality of service and user experience in wireless communications systems.
Patent Information
- Application Number
- PCT/CN2025/095301
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-16
- Publication Date
- 2026-11-19
AI Technical Summary
In wireless communications systems, particularly for non-connected user equipments (UEs), the transition from an inactive state to a connected state involves significant overhead and latency due to the need for the network to provide carrier aggregation configuration again, which is inefficient and delays the transition process.
Providing non-connected UEs with an updated candidate cell configuration in advance, either upon request or autonomously by the network, to facilitate a seamless transition to a connected state, thereby reducing the need for real-time retrieval of UE context and candidate cell configuration.
This approach reduces overhead and latency, improving the quality of service and user experience by enabling more efficient transitions and minimizing network delays.
Smart Images

Figure CN2025095301_19112026_PF_FP_ABST
Abstract
Description
CANDIDATE CELL CONFIGURATION UPDATE FOR NON-CONNECTED USER EQUIPMENTSField of the Disclosure
[0001] Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for candidate cell configuration updates for non-connected user equipments (UEs) . Description of Related Art
[0002] Wireless communications systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts, or other similar types of services. These wireless communications systems may employ multiple-access technologies capable of supporting communications with multiple users by sharing available wireless communications system resources with those users.
[0003] Although wireless communications systems have made great technological advancements over many years, challenges still exist. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and wireless receivers. Accordingly, there is a continuous desire to improve the technical performance of wireless communications systems, including, for example: improving speed and data carrying capacity of communications, improving efficiency of the use of shared communications mediums, reducing power used by transmitters and receivers while performing communications, improving reliability of wireless communications, avoiding redundant transmissions and / or receptions and related processing, improving the coverage area of wireless communications, increasing the number and types of devices that can access wireless communications systems, increasing the ability for different types of devices to intercommunicate, increasing the number and type of wireless communications mediums available for use, and the like. Consequently, there exists a need for further improvements in wireless communications systems to overcome the aforementioned technical challenges and others.SUMMARY
[0004] One aspect provides a method for wireless communications at a wireless node. The method includes obtaining first configuration information for a first set of one or more candidate cells; obtaining, while the wireless node is in a non-connected state, second configuration information for a second set of one or more candidate cells, wherein the second set includes at least one candidate cell that is not in the first set; and participating in a procedure, with a candidate cell in the second set, to transition to a connected state.
[0005] Another aspect provides a method for wireless communications. The method includes outputting, to a wireless node, first configuration information for a first set of one or more candidate cells; and outputting, to the wireless node while the wireless node is in a non-connected state, second configuration information for a second set of one or more candidate cells, wherein the second set includes at least one candidate cell that is not in the first set.
[0006] Other aspects provide: an apparatus operable, configured, or otherwise adapted to perform any one or more of the aforementioned methods and / or those described elsewhere herein; a non-transitory, computer-readable media comprising instructions that, when executed (e.g., directly, indirectly, after pre-processing, without pre-processing) by one or more processors of an apparatus, cause the apparatus to perform the aforementioned methods as well as those described elsewhere herein; a computer program product embodied on a computer-readable storage medium comprising code for performing the aforementioned methods as well as those described elsewhere herein; and / or an apparatus comprising means for performing the aforementioned methods as well as those described elsewhere herein. By way of example, an apparatus may comprise a processing system, a device with a processing system, or processing systems cooperating over one or more networks.
[0007] The following description and the appended figures set forth certain features for purposes of illustration.BRIEF DESCRIPTION OF DRAWINGS
[0008] The appended figures depict certain features of the various aspects described herein and are not to be considered limiting of the scope of this disclosure.
[0009] FIG. 1 depicts an example wireless communications network.
[0010] FIG. 2 depicts an example disaggregated base station architecture.
[0011] FIG. 3 depicts aspects of an example base station and an example user equipment.
[0012] FIGS. 4A, 4B, 4C, and 4D depict various example aspects of data structures for a wireless communications network.
[0013] FIG. 5 depicts an example scenario with a pre-configured candidate cell set.
[0014] FIG. 6 depicts an example of user equipment (UE) mobility.
[0015] FIG. 7 depicts an example lower-layer triggered mobility (LTM) report without differential reporting.
[0016] FIG. 8 depicts an example scenario with a pre-configured candidate cell set.
[0017] FIG. 9 depicts a call flow diagram illustrating a radio resource control (RRC) resume procedure for an inactive UE transitioning to a connected state.
[0018] FIG. 10 depicts an example scenario with a pre-configured candidate cell set, where the UE moves outside of a coverage area of the pre-configured candidate cell set and requests an update, in accordance with aspects of the present disclosure.
[0019] FIG. 11 depicts an example scenario with a pre-configured candidate cell set, where the UE moves outside of a coverage area of the pre-configured candidate cell set and receives a network-autonomous update, in accordance with aspects of the present disclosure.
[0020] FIG. 12 depicts a call flow diagram illustrating techniques for candidate cell configuration updates for non-connected UEs, in accordance with aspects of the present disclosure.
[0021] FIG. 13 depicts a method for wireless communications.
[0022] FIG. 14 depicts a method for wireless communications.
[0023] FIG. 15 depicts aspects of an example communications device.DETAILED DESCRIPTION
[0024] Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for candidate cell configuration updates for non-connected UEs.
[0025] In advanced wireless systems (e.g., 5G) , mobility procedures are in place to help maintain network connections for a user equipment (UE) as it moves between the coverage areas of different cells. Mobility procedures generally refer to mechanisms that allow a UE to transition from being served by a source cell to being served by a target / candidate cell, which may generally be referred to as handover.
[0026] In some cases, for physical layer (PHY or Layer 1 / L1) and / or medium access control layer (MAC or Layer 2 / L2) , also referred to as L1 / L2 triggered mobility (LTM) , as a UE moves, a new serving cell (e.g. a primary cell (Pcell) ) may be selected (e.g., reselected) for handover among a set of pre-configured candidate cells based on measurements of reference signal (RS) made at the physical (PHY or L1) layer (referred to as L1 measurements) for those cells. The RSs are typically sent with different beams. To facilitate a handover decision, the UE may generate beam reports containing information about the received signal quality from the different beams of the serving cell and / or candidate cells. These beam reports may then be sent to a serving cell. For example, such beam reports may include measurements (e.g., reference signal (RS) receive power (RSRP) , signal to interference and noise ratio (SINR) ) for Mbeams for each of L (serving and / or candidate) cells. Thus, the reports may include M x L total measurements.
[0027] In UE initiated handover procedures (e.g., conditional handover (CHO) or C-LTM) candidate cell configurations are provided for neighbor cell sites. A connected UE in mobility will store those candidate cell configurations (e.g., including carrier aggregation (CA) configuration information) and use one particular candidate cell configuration when initiating handover to the corresponding cell site.
[0028] Once a connected UE transitions to an inactive mode, the candidate cell configuration for connected UE mobility is released (e.g., after receiving the RRCRelease with SuspendConfig) . If a large amount of traffic arrives later, the inactive UE may initiate an RRC resume procedure to the current camped cell. In such cases, the network (e.g., a gNB) may have to provide a CA configuration again for the current camped cell, which increases overhead and latency. In addition, the UE's transition to a connected state from an inactive state using RRC resume is more efficient than a transition to a connected state from an idle state using an RRC setup procedure. Therefore, it may be beneficial to further optimize the transition from an inactive state to a connected state.
[0029] Aspects of the present disclosure provide signaling mechanisms that may support candidate cell configuration updates for non-connected UEs (e.g., in an inactive or idle state) . For example, in accordance with aspects of the present disclosure, a UE in a non-connected mode may be provided with an updated candidate cell configuration for a set of new candidate cells in advance (e.g., before initiating the connected mode transition to one of the new candidate cells) . In some aspects, this update may be based on a request from a UE in a non-connected mode (e.g., based on certain trigger conditions such as UE location) or may be autonomously provided by the network. Additionally, the network may provide UE context information to the set of new candidate cells in the updated candidate cell configuration.
[0030] Utilization of the techniques disclosed herein may reduce overhead and latency associated with retrieval of UE context by a current camped cell and sending / applying the candidate cell configuration based on UE capability. By reducing overhead and latency, overall quality of service (QoS) and quality of experience (QoE) may be improved for end users. Introduction to Wireless Communications Networks
[0031] The techniques and methods described herein may be used for various wireless communications networks. While aspects may be described herein using terminology commonly associated with 3G, 4G, and / or 5G wireless technologies, aspects of the present disclosure may likewise be applicable to other communications systems and standards not explicitly mentioned herein.
[0032] FIG. 1 depicts an example of a wireless communications network 100, in which aspects described herein may be implemented.
[0033] Generally, wireless communications network 100 includes various network entities (alternatively, network elements or network nodes) . A network entity is generally a communications device and / or a communications function performed by a communications device (e.g., a user equipment (UE) , a base station (BS) , a component of a BS, a server, etc. ) . For example, various functions of a network as well as various devices associated with and interacting with a network may be considered network entities. Further, wireless communications network 100 includes terrestrial aspects, such as ground-based network entities (e.g., BSs 102) , and non-terrestrial aspects, such as satellite 140 and aircraft 145, which may include network entities on-board (e.g., one or more BSs) capable of communicating with other network elements (e.g., terrestrial BSs) and user equipments.
[0034] In the depicted example, wireless communications network 100 includes BSs 102, UEs 104, and one or more core networks, such as an Evolved Packet Core (EPC) 160 and 5G Core (5GC) network 190, which interoperate to provide communications services over various communications links, including wired and wireless links.
[0035] FIG. 1 depicts various example UEs 104, which may more generally include: a cellular phone, smart phone, session initiation protocol (SIP) phone, laptop, personal digital assistant (PDA) , satellite radio, global positioning system, multimedia device, video device, digital audio player, camera, game console, tablet, smart device, wearable device, vehicle, electric meter, gas pump, large or small kitchen appliance, healthcare device, implant, sensor / actuator, display, internet of things (IoT) devices, always on (AON) devices, edge processing devices, or other similar devices. UEs 104 may also be referred to more generally as a mobile device, a wireless device, a wireless communications device, a station, a mobile station, a subscriber station, a mobile subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a remote device, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, and others.
[0036] BSs 102 wirelessly communicate with (e.g., transmit signals to or receive signals from) UEs 104 via communications links 120. The communications links 120 between BSs 102 and UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to a BS 102 and / or downlink (DL) (also referred to as forward link) transmissions from a BS 102 to a UE 104. The communications links 120 may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity in various aspects.
[0037] BSs 102 may generally include: a NodeB, enhanced NodeB (eNB) , next generation enhanced NodeB (ng-eNB) , next generation NodeB (gNB or gNodeB) , access point, base transceiver station, radio base station, radio transceiver, transceiver function, transmission reception point, and / or others. Each of BSs 102 may provide communications coverage for a respective geographic coverage area 110, which may sometimes be referred to as a cell, and which may overlap in some cases (e.g., small cell 102' may have a coverage area 110' that overlaps the coverage area 110 of a macro cell) . A BS may, for example, provide communications coverage for a macro cell (covering relatively large geographic area) , a pico cell (covering relatively smaller geographic area, such as a sports stadium) , a femto cell (relatively smaller geographic area (e.g., a home) ) , and / or other types of cells.
[0038] While BSs 102 are depicted in various aspects as unitary communications devices, BSs 102 may be implemented in various configurations. For example, one or more components of a base station may be disaggregated, including a central unit (CU) , one or more distributed units (DUs) , one or more radio units (RUs) , a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) , or a Non-Real Time (Non-RT) RIC, to name a few examples. In another example, various aspects of a base station may be virtualized. More generally, a base station (e.g., BS 102) may include components that are located at a single physical location or components located at various physical locations. In examples in which a base station includes components that are located at various physical locations, the various components may each perform functions such that, collectively, the various components achieve functionality that is similar to a base station that is located at a single physical location. In some aspects, a base station including components that are located at various physical locations may be referred to as a disaggregated radio access network architecture, such as an Open RAN (O-RAN) or Virtualized RAN (VRAN) architecture. FIG. 2 depicts and describes an example disaggregated base station architecture.
[0039] Different BSs 102 within wireless communications network 100 may also be configured to support different radio access technologies, such as 3G, 4G, and / or 5G. For example, BSs 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) ) may interface with the EPC 160 through first backhaul links 132 (e.g., an S1 interface) . BSs 102 configured for 5G (e.g., 5G NR or Next Generation RAN (NG-RAN) ) may interface with 5GC 190 through second backhaul links 184. BSs 102 may communicate directly or indirectly (e.g., through the EPC 160 or 5GC 190) with each other over third backhaul links 134 (e.g., X2 interface) , which may be wired or wireless.
[0040] Wireless communications network 100 may subdivide the electromagnetic spectrum into various classes, bands, channels, or other features. In some aspects, the subdivision is provided based on wavelength and frequency, where frequency may also be referred to as a carrier, a subcarrier, a frequency channel, a tone, or a subband. For example, 3 GPP currently defines Frequency Range 1 (FR 1) as including 410 MHz -7125 MHz, which is often referred to (interchangeably) as “Sub-6 GHz” . Similarly, 3GPP currently defines Frequency Range 2 (FR2) as including 24,250 MHz -71,000 MHz, which is sometimes referred to (interchangeably) as a “millimeter wave” ( “mmW” or “mmWave” ) . In some cases, FR2 may be further defined in terms of sub-ranges, such as a first sub-range FR2-1 including 24, 250 MHz -52, 600 MHz and a second sub-range FR2-2 including 52,600 MHz -71,000 MHz. A base station configured to communicate using mmWave / near mmWave radio frequency bands (e.g., a mmWave base station such as BS 180) may utilize beamforming (e.g., 182) with a UE (e.g., 104) to improve path loss and range.
[0041] The communications links 120 between BSs 102 and, for example, UEs 104, may be through one or more carriers, which may have different bandwidths (e.g., 5, 10, 15, 20, 100, 400, and / or other MHz) , and which may be aggregated in various aspects. Carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL) .
[0042] Communications using higher frequency bands may have higher path loss and a shorter range compared to lower frequency communications. Accordingly, certain base stations (e.g., 180 in FIG. 1) may utilize beamforming 182 with a UE 104 to improve path loss and range. For example, BS 180 and the UE 104 may each include a plurality of antennas, such as antenna elements, antenna panels, and / or antenna arrays to facilitate the beamforming. In some cases, BS 180 may transmit a beamformed signal to UE 104 in one or more transmit directions 182'. UE 104 may receive the beamformed signal from the BS 180 in one or more receive directions 182” . UE 104 may also transmit a beamformed signal to the BS 180 in one or more transmit directions 182” . BS 180 may also receive the beamformed signal from UE 104 in one or more receive directions 182'. BS 180 and UE 104 may then perform beam training to determine the best receive and transmit directions for each of BS 180 and UE 104. Notably, the transmit and receive directions for BS 180 may or may not be the same. Similarly, the transmit and receive directions for UE 104 may or may not be the same.
[0043] Wireless communications network 100 further includes a Wi-Fi AP 150 in communication with Wi-Fi stations (STAs) 152 via communications links 154 in, for example, a 2.4 GHz and / or 5 GHz unlicensed frequency spectrum.
[0044] Certain UEs 104 may communicate with each other using device-to-device (D2D) communications link 158. D2D communications link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH) , a physical sidelink discovery channel (PSDCH) , a physical sidelink shared channel (PSSCH) , a physical sidelink control channel (PSCCH) , and / or a physical sidelink feedback channel (PSFCH) .
[0045] EPC 160 may include various functional components, including: a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and / or a Packet Data Network (PDN) Gateway 172, such as in the depicted example. MME 162 may be in communication with a Home Subscriber Server (HSS) 174. MME 162 is the control node that processes the signaling between the UEs 104 and the EPC 160. Generally, MME 162 provides bearer and connection management.
[0046] Generally, user Internet protocol (IP) packets are transferred through Serving Gateway 166, which itself is connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation as well as other functions. PDN Gateway 172 and the BM-SC 170 are connected to IP Services 176, which may include, for example, the Internet, an intranet, an IP Multimedia Subsystem (IMS) , a Packet Switched (PS) streaming service, and / or other IP services.
[0047] BM-SC 170 may provide functions for MBMS user service provisioning and delivery. BM-SC 170 may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN) , and / or may be used to schedule MBMS transmissions. MBMS Gateway 168 may be used to distribute MBMS traffic to the BSs 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and / or may be responsible for session management (start / stop) and for collecting eMBMS related charging information.
[0048] 5GC 190 may include various functional components, including: an Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. AMF 192 may be in communication with Unified Data Management (UDM) 196.
[0049] AMF 192 is a control node that processes signaling between UEs 104 and 5 GC 190. AMF 192 provides, for example, quality of service (QoS) flow and session management.
[0050] Intemet protocol (IP) packets are transferred through UPF 195, which is connected to the IP Services 197, and which provides UE IP address allocation as well as other functions for 5GC 190. IP Services 197 may include, for example, the Internet, an intranet, an IMS, a PS streaming service, and / or other IP services.
[0051] In various aspects, a network entity or network node can be implemented as an aggregated base station, as a disaggregated base station, a component of a base station, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, to name a few examples.
[0052] FIG. 2 depicts an example disaggregated base station 200 architecture. The disaggregated base station 200 architecture may include one or more central units (CUs) 210 that can communicate directly with a core network 220 via a backhaul link, or indirectly with the core network 220 through one or more disaggregated base station units (such as a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) 225 via an E2 link, or a Non-Real Time (Non-RT) RIC 215 associated with a Service Management and Orchestration (SMO) Framework 205, or both) . A CU 210 may communicate with one or more distributed units (DUs) 230 via respective midhaul links, such as an F 1 interface. The DUs 230 may communicate with one or more radio units (RUs) 240 via respective fronthaul links. The RUs 240 may communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, the UE 104 may be simultaneously served by multiple RUs 240.
[0053] Each of the units, e.g., the CUs 210, the DUs 230, the RUs 240, as well as the Near-RT RICs 225, the Non-RT RICs 215 and the SMO Framework 205, may include one or more interfaces 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 providing instructions to the communications interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or transmit signals over a wired transmission medium to one or more of the other units. Additionally or alternatively, the units can include a wireless interface, which may include a receiver, a transmitter or transceiver (such as a radio frequency (RF) transceiver) , configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.
[0054] In some aspects, the CU 210 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC) , packet data convergence protocol (PDCP) , service data adaptation protocol (SDAP) , or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 210. The CU 210 may be configured to handle user plane functionality (e.g., Central Unit -User Plane (CU-UP) ) , control plane functionality (e.g., Central Unit -Control Plane (CU-CP) ) , or a combination thereof. In some implementations, the CU 210 can be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as the E1 interface when implemented in an O-RAN configuration. The CU 210 can be implemented to communicate with the DU 230, as necessary, for network control and signaling.
[0055] The DU 230 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 240. In some aspects, the DU 230 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, or the like) depending, at least in part, on a functional split, such as those defined by the 3rd Generation Partnership Project (3GPP) . In some aspects, the DU 230 may further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 230, or with the control functions hosted by the CU 210.
[0056] Lower-layer functionality can be implemented by one or more RUs 240. In some deployments, an RU 240, controlled by a DU 230, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (such as performing fast Fourier transform (FFT) , inverse FFT (iFFT) , digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like) , or both, based at least in part on the functional split, such as a lower layer functional split. In such an architecture, the RU (s) 240 can be implemented to handle over the air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control and user plane communications with the RU (s) 240 can be controlled by the corresponding DU 230. In some scenarios, this configuration can enable the DU(s) 230 and the CU 210 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.
[0057] The SMO Framework 205 may be configured to support RAN deployment and provisioning ofnon-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 205 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements which may be managed via an operations and maintenance interface (such as an O1 interface) . For virtualized network elements, the SMO Framework 205 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 290) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface) . Such virtualized network elements can include, but are not limited to, CUs 210, DUs 230, RUs 240 and Near-RT RICs 225. In some implementations, the SMO Framework 205 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 211, via an O1 interface. Additionally, in some implementations, the SMO Framework 205 can communicate directly with one or more RUs 240 via an O1 interface. The SMO Framework 205 also may include a Non-RT RIC 215 configured to support functionality of the SMO Framework 205.
[0058] The Non-RT RIC 215 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, Artificial Intelligence / Machine Learning (AI / ML) workflows including model training and updates, or policy-based guidance of applications / features in the Near-RT RIC 225. The Non-RT RIC 215 may be coupled to or communicate with (such as via an A1 interface) the Near-RT RIC 225. The Near-RT RIC 225 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 210, one or more DUs 230, or both, as well as an O-eNB, with the Near-RT RIC 225.
[0059] In some implementations, to generate AI / ML models to be deployed in the Near-RT RIC 225, the Non-RT RIC 215 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 225 and may be received at the SMO Framework 205 or the Non-RT RIC 215 from non-network data sources or from network functions. In some examples, the Non-RT RIC 215 or the Near-RT RIC 225 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 215 may monitor long-term trends and patterns for performance and employ AI / ML models to perform corrective actions through the SMO Framework 205 (such as reconfiguration via O1) or via creation of RAN management policies (such as A1 policies) .
[0060] FIG. 3 depicts aspects of an example BS 102 and a UE 104.
[0061] Generally, BS 102 includes various processors (e.g., 320, 330, 338, and 340) , antennas 334a-t (collectively 334) , transceivers 332a-t (collectively 332) , which include modulators and demodulators, and other aspects, which enable wireless transmission of data (e.g., data source 312) and wireless reception of data (e.g., data sink 339) . For example, BS 102 may send and receive data between BS 102 and UE 104. BS 102 includes controller / processor 340, which may be configured to implement various functions described herein related to wireless communications.
[0062] Generally, UE 104 includes various processors (e.g., 358, 364, 366, and 380) , antennas 352a-r (collectively 352) , transceivers 354a-r (collectively 354) , which include modulators and demodulators, and other aspects, which enable wireless transmission of data (e.g., retrieved from data source 362) and wireless reception of data (e.g., provided to data sink 360) . UE 104 includes controller / processor 380, which may be configured to implement various functions described herein related to wireless communications.
[0063] In regards to an example downlink transmission, BS 102 includes a transmit processor 320 that may receive data from a data source 312 and control information from a controller / processor 340. The control information may be for the physical broadcast channel (PBCH) , physical control format indicator channel (PCFICH) , physical HARQ indicator channel (PHICH) , physical downlink control channel (PDCCH) , group common PDCCH (GC PDCCH) , and / or others. The data may be for the physical downlink shared channel (PDSCH) , in some examples.
[0064] Transmit processor 320 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. Transmit processor 320 may also generate reference symbols, such as for the primary synchronization signal (PSS) , secondary synchronization signal (SSS) , PBCH demodulation reference signal (DMRS) , and channel state information reference signal (CSI-RS) .
[0065] Transmit (TX) multiple-input multiple-output (MIMO) processor 330 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and / or the reference symbols, if applicable, and may provide output symbol streams to the modulators (MODs) in transceivers 332a-332t. Each modulator in transceivers 332a-332t may process a respective output symbol stream to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. Downlink signals from the modulators in transceivers 332a-332t may be transmitted via the antennas 334a-334t, respectively.
[0066] In order to receive the downlink transmission, UE 104 includes antennas 352a-352r that may receive the downlink signals from the BS 102 and may provide received signals to the demodulators (DEMODs) in transceivers 354a-354r, respectively. Each demodulator in transceivers 354a-354r may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator may further process the input samples to obtain received symbols.
[0067] MIMO detector 356 may obtain received symbols from all the demodulators in transceivers 354a-354r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. Receive processor 358 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 104 to a data sink 360, and provide decoded control information to a controller / processor 380.
[0068] In regards to an example uplink transmission, UE 104 further includes a transmit processor 364 that may receive and process data (e.g., for the PUSCH) from a data source 362 and control information (e.g., for the physical uplink control channel (PUCCH) ) from the controller / processor 380. Transmit processor 364 may also generate reference symbols for a reference signal (e.g., for the sounding reference signal (SRS) ) . The symbols from the transmit processor 364 may be precoded by a TX MIMO processor 366 if applicable, further processed by the modulators in transceivers 354a-354r (e.g., for SC-FDM) , and transmitted to BS 102.
[0069] AtBS 102, the uplink signals from UE 104 maybe receivedby antennas 334a-t, processed by the demodulators in transceivers 332a-332t, detected by a MIMO detector 336 if applicable, and further processed by a receive processor 338 to obtain decoded data and control information sent by UE 104. Receive processor 338 may provide the decoded data to a data sink 339 and the decoded control information to the controller / processor 340.
[0070] Memories 342 and 382 may store data and program codes for BS 102 and UE 104, respectively.
[0071] Scheduler 344 may schedule UEs for data transmission on the downlink and / or uplink.
[0072] In various aspects, BS 102 may be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” may refer to various mechanisms of outputting data, such as outputting data from data source 312, scheduler 344, memory 342, transmit processor 320, controller / processor 340, TX MIMO processor 330, transceivers 332a-t, antenna 334a-t, and / or other aspects described herein. Similarly, “receiving” may refer to various mechanisms of obtaining data, such as obtaining data from antennas 334a-t, transceivers 332a-t, RX MIMO detector 336, controller / processor 340, receive processor 338, scheduler 344, memory 342, and / or other aspects described herein.
[0073] In various aspects, UE 104 may likewise be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” may refer to various mechanisms of outputting data, such as outputting data from data source 362, memory 382, transmit processor 364, controller / processor 380, TX MIMO processor 366, transceivers 354a-t, antenna 352a-t, and / or other aspects described herein. Similarly, “receiving” may refer to various mechanisms of obtaining data, such as obtaining data from antennas 352a-t, transceivers 354a-t, RX MIMO detector 356, controller / processor 380, receive processor 358, memory 382, and / or other aspects described herein.
[0074] In some aspects, one or more processors may be configured to perform various operations, such as those associated with the methods described herein, and transmit (output) to or receive (obtain) data from another interface that is configured to transmit or receive, respectively, the data.
[0075] FIGS. 4A, 4B, 4C, and 4D depict aspects of data structures for a wireless communications network, such as wireless communications network 100 of FIG. 1.
[0076] In particular, FIG. 4A is a diagram 400 illustrating an example of a first sub frame within a 5G (e.g., 5 G NR) frame structure, FIG. 4B is a diagram 430 illustrating an example of DL channels within a 5G subframe, FIG. 4C is a diagram 450 illustrating an example of a second subframe within a 5G frame structure, and FIG. 4D is a diagram 480 illustrating an example of UL channels within a 5G subframe.
[0077] Wireless communications systems may utilize orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) on the uplink and downlink. Such systems may also support half-duplex operation using time division duplexing (TDD) . OFDM and single-carrier frequency division multiplexing (SC-FDM) partition the system bandwidth (e.g., as depicted in FIGS. 4B and 4D) into multiple orthogonal subcarriers. Each subcarrier may be modulated with data. Modulation symbols may be sent in the frequency domain with OFDM and / or in the time domain with SC-FDM.
[0078] A wireless communications frame structure may be frequency division duplex (FDD) , in which, for a particular set of subcarriers, subframes within the set ofsubcarriers are dedicated for either DL or UL. Wireless communications frame structures may also be time division duplex (TDD) , in which, for a particular set of subcarriers, subframes within the set of subcarriers are dedicated for both DL and UL.
[0079] In FIG. 4A and 4C, the wireless communications frame structure is TDD where D is DL, U is UL, and X is flexible for use between DL / UL. UEs may be configured with a slot format through a received slot format indicator (SFI) (dynamically through DL control information (DCI) , or semi-statically / statically through radio resource control (RRC) signaling) . In the depicted examples, a 10 ms frame is divided into 10 equally sized 1 ms subframes. Each subframe may include one or more time slots. In some examples, each slot may include 7 or 14 symbols, depending on the slot format. Subframes may also include mini-slots, which generally have fewer symbols than an entire slot. Other wireless communications technologies may have a different frame structure and / or different channels.
[0080] In certain aspects, the number of slots within a subframe is based on a slot configuration and a numerology. For example, for slot configuration 0, different numerologies (μ) 0 to 6 allow for 1, 2, 4, 8, 16, 32, and 64 slots, respectively, per subframe. For slot configuration 1, different numerologies 0 to 2 allow for 2, 4, and 8 slots, respectively, per subframe. Accordingly, for slot configuration 0 and numerology μ, there are 14 symbols / slot and 2μ slots / subframe. The subcarrier spacing and symbol length / duration are a function of the numerology. The subcarrier spacing may be equal to 2μ x 15 kHz, where μ is the numerology 0 to 6. As such, the numerology μ = 0 has a subcarrier spacing of 15 kHz and the numerology μ = 6 has a subcarrier spacing of 960 kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIGS. 4A, 4B, 4C, and 4D provide an example of slot configuration 0 with 14 symbols per slot and numerology μ = 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.
[0081] As depicted in FIGS. 4A, 4B, 4C, and 4D, a resource grid may be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs) ) that extends, for example, 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.
[0082] As illustrated in FIG. 4A, some of the REs carry reference (pilot) signals (RS) for a UE (e.g., UE 104 of FIGS. 1 and 3) . The RS may include demodulation RS (DMRS) and / or channel state information reference signals (CSI-RS) for channel estimation at the UE.The RS may also include beam measurement RS (BRS) , beam refinement RS (BRRS) , and / or phase tracking RS (PT-RS) .
[0083] FIG. 4B illustrates an example of various DL channels within a subframe of a frame. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) , each CCE including, for example, nine RE groups (REGs) , each REG including, for example, four consecutive REs in an OFDM symbol.
[0084] A primary synchronization signal (PSS) may be within symbol 2 of particular subframes of a frame. The PSS is used by a UE (e.g., 104 of FIGS. 1 and 3) to determine subframe / symbol timing and a physical layer identity.
[0085] A secondary synchronization signal (SSS) may be within symbol 4 of particular subframes of a frame. The SSS is used by a UE to determine a physical layer cell identity group number and radio frame timing.
[0086] Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI) . Based on the PCI, the UE can determine the locations of the aforementioned DMRS. The physical broadcast channel (PBCH) , which carries a master information block (MIB) , may be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block. The MIB provides a number of RBs in the system bandwidth and a system frame number (SFN) . The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as system information blocks (SIBs) , and / or paging messages.
[0087] As illustrated in FIG. 4C, some of the REs carry DMRS (indicated as R for one particular configuration, but other DMRS configurations are possible) for channel estimation at the base station. The UE may transmit DMRS for the PUCCH and DMRS for the PUSCH. The PUSCH DMRS may be transmitted, for example, in the first one or two symbols of the PUSCH. The PUCCH DMRS may be transmitted in different configurations depending on whether short or long PUCCHs are transmitted and depending on the particular PUCCH format used. UE 104 may transmit sounding reference signals (SRS) . The SRS may be transmitted, for example, in the last symbol of a subframe. The SRS may have a comb structure, and a UE may transmit SRS on one of the combs. The SRS may be used by a base station for channel quality estimation to enable frequency-dependent scheduling on the UL.
[0088] FIG. 4D illustrates an example of various UL channels within a subframe of a frame. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI) , such as scheduling requests, a channel quality indicator (CQI) , a precoding matrix indicator (PMI) , a rank indicator (RI) , and HARQ ACK / NACK feedback. The PUSCH carries data, and may additionally be used to carry a buffer status report (BSR) , a power headroom report (PHR) , and / or UCI. Overview of Lower-layer Triggered Mobility (LTM)
[0089] Dynamic mobility signaling may be beneficial in the scenario illustrated in FIG. 5, where a UE may move between a preconfigured set 500 of candidate cells. In the illustrated example, the UE moves from a first cell (e.g., an old serving / primary cell) to a new serving candidate cell. In this case, the UE may not receive data or control information in the candidate cell, but may transmit a PRACH in order to facilitate timing adjustment for the new candidate cell before a cell change.
[0090] As noted above, dynamic mobility signaling (e.g., L1 and / or L2-centric mobility or LTM) may lead to more efficient intra-cell and inter-cell mobility with reduced latency.
[0091] The general concept of LTM signaling may be understood with reference to the example scenario 600 shown in FIG. 6. As illustrated, the network may configure (e.g., via RRC signaling) , a set of cells for L1 / L2 mobility (referred to herein as an L1 / L2 Mobility Configured cell set) . At any given time, the network may also configure (via L1 / L2 signaling) an L1 / L2 Mobility Activated cell set, which refers to a group of cells in the configured set that are activated and can be readily used for data and control transfer. The network may also configure (signal) an L1 / L2 Mobility Deactivated cell set, which refers to a group of cells in the configured set that are deactivated and can be readily activated by L1 / L2 signaling.
[0092] L1 / L2 signaling may be used for mobility management of the activated set. For example, L1 / L2 signaling may be used to activate / deactivate cells in the set, select beams within the activated cells, and update / switch a primary cell (PCell) . This dynamic signaling may help provide seamless mobility within the activated cells in the set. In other words, as the UE moves, the cells from the set are deactivated and activated by L1 / L2 signaling. The cells to activate and deactivate may be based on various factors, such as signal quality (measurements) and loading.
[0093] As in the example illustrated in FIG. 6, in some cases, all cells in the L1 / L2 Mobility Configured cell set may belong to the same DU 630 ofa CU 610. This may be similar to carrier aggregation (CA) , but cells may be on the same carrier frequencies. The size of the cell set configured for L1 / L2 mobility signaling may vary. In general, the cell set size may be selected to be large enough to cover a meaningful mobility area.
[0094] In some cases, the UE may be provided with a subset of deactivated cells, as a candidate cell set, from which the UE could autonomously choose to add to the activated cell set. The decision of whether to add a cell from the candidate cell set to the activated cell set may be a based various factors, such as measured channel quality and loading information. In some cases, the ability for the UE to autonomously choose to add to the activated cell set may be similar to a UE decision when configured for Conditional Handover (CHO) for fast and efficient addition of the prepared cells.
[0095] As illustrated in FIG. 6, each cell may be served by an RU. Each of the RUs may have multi-carrier (N CCs) support. In such cases, each CC may be a cell (e.g., Cell 2 and Cell 2' may be different CCs of the same RU) . In such cases, activation / deactivation can be done in groups of carriers (cells) .
[0096] For PCell management, L1 / L2 signaling may be used to set (select) the PCell out of the preconfigured options within the activated cell set. In some cases, L3 mobility may be used for PCell change (L3 handover) when a new PCell is not from the activated cell set for L1 / L2 mobility. In such cases, RRC signaling may update the set of cells for L1 / L2 mobility at L3 handover.
[0097] In some cases, physical layer (Layer 1 or L1) measurement may be enhanced for L1 / L2 mobility, where a serving cell can be changed via L1 / L2 signalling based on L1 measurement, and both synchronous and asynchronous source and target cells may be considered.
[0098] Various mechanisms and procedures of L1 / L2 based inter-cell mobility may be specified for mobility latency reduction. These may include configuration and maintenance for multiple candidate cells to allow fast application of configurations for candidate cells. Dynamic switching mechanisms among candidate serving cells (including SpCell and SCell) may be supported for the potential applicable scenarios based on L1 / L2 signaling.
[0099] L1 enhancements for inter-cell beam management, may include L1 measurement and reporting, as well as beam indication. Timing Advance (TA) management and CU-DU interface signaling may also be provided to support L1 / L2 mobility.
[0100] L1 / L2 based inter-cell mobility procedures may be applicable to a variety of scenarios. These scenarios may include standalone, CA and new radio-dual connectivity (NR-DC) cases with serving cell change within one cell group (CG) , intra-distributed unit (DU) cases and intra-central unit (CU) inter-DU cases, intra-frequency and inter-frequency scenarios, both FR1 and FR2 scenarios, and scenarios where source and target cells may be synchronized or non-synchronized.
[0101] As noted above, a UE may generate beam reports containing information about the received signal quality of RSs transmitted from the different beams of the serving cell and / or candidate cells, facilitating handover decisions. These beam reports may then be sent to the serving cell (base station) . For example, such beam reports may include measurements for Mbeams for each of L (serving and / or candidate) cells.
[0102] The UE may provide the report to a serving cell, facilitating handover decisions and mobility procedures. The differential reporting may include various formats, increasing the number of beams that may be reported while significantly reducing overhead associated with processing the beam report.
[0103] FIG. 7 depicts an example LTM report. As illustrated at 702, a single LTM report may include measurements for Mbeams for each of L configured (e.g., or activated, if introduced) cells. In some cases, the selection of the M beams may be determined at a UE.
[0104] Maximum values of M and L (e.g., the total number of beams that may be reported in a single LTM report) may be based on UE capability. For example, in some cases, M *L = 4 beams may be supported as a UE capability. In some cases, the values of M and L may be configured to the UE in a reporting configuration.
[0105] As illustrated in FIG. 7, the example LTM report indicates an absolute RSRP value associated with each beam. As noted above, these conventional techniques for beam reporting limit the number of beams that may be included in the report, and are associated with significant overhead. Aspects Related to Candidate Cell Configuration Updates for Non-Connected UEs
[0106] As noted above, in UE initiated handover procedures (e.g., conditional handover (CHO) or C-LTM) , candidate cell configurations may be provided for neighbor cell sites. This may be understood, for example, in diagram 800 of FIG. 8 where the candidate cell configurations may be provided for neighbor cell cites represented by the corresponding candidate PCell PCI 0-6 within the circle representing an (e.g., coverage) area 802. A connected UE in mobility will store those candidate cell configurations (e.g., including carrier aggregation (CA) configuration information) and use one particular candidate cell configuration when initiating handover to the corresponding cell site.
[0107] Once a connected UE transitions to an inactive mode, (all of the configured) candidate cell configuration (s) for connected UE mobility are typically released (e.g., after receiving the RRCRelease with SuspendConfig) . If a large amount of traffic arrives later, the inactive UE may initiate an RRC resume procedure to the current camped cell (e.g., PCI 4 in diagram 800 of FIG. 8) .
[0108] FIG. 9 depicts a call flow diagram 900 illustrating a radio resource control (RRC) resume procedure for an inactive UE transitioning to a connected state. When a large amount of traffic arrives for a UE in the RRC inactive state, the inactive UE may initiate an RRC resume procedure to the current camped cell. The RRC resume procedure includes the following major steps.
[0109] Via message 1 (Msg1) , a physical random access channel (PRACH) preamble, the UE initiates the random access procedure with the current camped cell.
[0110] In message 2 (Msg2) , the current cell responds with a random access response (RAR) , allowing the UE to proceed with the RRC resume request.
[0111] In message 3 (Msg3) , the inactive UE transmits an RRC resume request to the current camped cell. This message includes the UE's inactive radio network temporary identifier (I-RNTI) . Based on the I-RNTI, the current camped cell retrieves the UE context from the original gNB, as shown at 902.
[0112] In message 4 (Msg4) , the current cell transmits the RRC resume message to the UE. This message includes the master cell group (MCG) configuration, which is determined based on the UE capability.
[0113] In message 5 (Msg5) , the inactive UE transmits the RRC resume complete message, indicating completion of the resume procedure and application of the configuration. This message may also include an early measurement report. Based on the early measurement report, the current camped cell may determine which secondary cell (s) (SCell (s) ) should be activated in the MCG, and may transmit MCG SCell activation signaling to the UE, as shown at 904.
[0114] After the RRC resume procedure is complete, data can flow over the activated cells (one or more PCells and SCells) in the MCG, as shown at 906. Ifneeded, the gNB may perform further configuration for the secondary cell group (SCG) .
[0115] As illustrated, after initial signaling (Msg1 and Msg2) , Msg3 carries the I-RNTI from the UE to the current camped PCell. The PCell retrieves the UE context from the original gNB. Msg4 is then sent to the UE with the MCG configuration. In Msg5, the UE sends the RRC resume complete message, which may include the early measurement report. This is followed by activation of SCells in the MCG and the beginning of data flow over the MCG.
[0116] In such a scenario illustrated by call flow diagram 900 of FIG. 9, the network (e.g., a gNB) may have to provide a CA configuration again for the current camped cell, which increases overhead and latency. In addition, the UE's transition to a connected state from an inactive state using RRC resume is more efficient than a transition to a connected state from an idle state using an RRC setup procedure. Therefore, it may be beneficial to further optimize the transition from an inactive state to a connected state.
[0117] Aspects of the present disclosure provide signaling mechanisms that may support candidate cell configuration updates for non-connected UEs (e.g., in an inactive or idle state) . For example, in accordance with aspects of the present disclosure, a UE in a non-connected mode may be provided with an updated candidate cell configuration for a set of new candidate cells in advance (e.g., before initiating the connected mode transition to one of the new candidate cells) . Additionally, the network may provide UE context information to the set of new candidate cells in the updated candidate cell configuration, which may help speed transition to a new cell.
[0118] In some aspects, the updated candidate cell configuration for a set of new candidate cells may be provided based on a request from a UE in a non-connected mode (e.g., based on certain trigger conditions such as UE location) . This may be understood with reference to FIG. 10, which depicts an example scenario 1000 with a pre-configured candidate cell set, where the UE moves outside of a coverage area of the pre-configured candidate cell set and requests an update, in accordance with aspects of the present disclosure.
[0119] As illustrated in FIG. 10, when the UE is in connected mode, it receives candidate cell configurations for PCI 0-6 in the circle. Later the UE transitions to a non-connected mode and moves to PCI 8. As illustrated, the (non-connected state) UE has moved outside of a coverage area 802 of the pre-configured candidate cell set.
[0120] In this case, gNB can provide the updated candidate cell configuration (s) (e.g., for PCI 4, 7, 8, 9, etc. ) that are neighboring / nearby / around the UE. The candidate cell configuration contains all necessary configuration information that enables corresponding candidate cells to become serving cells and to serve the UE (once it has transitioned to the connected mode) . For example, the candidate cell configuration represented by PCI X of the corresponding PCell may include configurations for all (related) cells enabling CA, dual connectivity (DC) , and / or dual stack operation.
[0121] As illustrated at 1002, the non-connected UE may request a candidate cell configuration update. In some aspects, the request can be triggered by certain events defined in wireless communications standards specifications, or may be configured by the network. According to a first option, a non-connected UE can request the update if it is moving outside the coverage of any measured candidate cell in currently stored candidate cell configurations. As illustrated in FIG. 10, for example, a non-connected UE can send the request to the currently camped cell with PCI 8, since it is moving outside the coverage of any measured candidate cell in currently stored candidate cell configurations (e.g., represented by PCI 0-6 in the circle) .
[0122] In some aspects, a UE may be defined / considered as outside coverage of a measured candidate cell if a corresponding cell or beam metric is below a certain threshold, which can be defined by standards specifications or by the network. The network can also specify a set of RS resources per measured candidate cell for the cell / beam metric evaluation (e.g., a set of SSBs) .
[0123] In some aspects, the set of measured candidate cells can be a subset of the total candidate cells in currently stored candidate cell configurations (e.g., only a PCell per candidate cell configuration may be measured) .
[0124] In some aspects, a timer may be set such that the UE may send the request only when it is outside the coverage area of any measured candidate cell for more than X ms (e.g., whose value may be determined / defined by wireless communication standards specifications or the network) .
[0125] In some aspects, a non-connected UE may request the update if moving outside a specific area. For example, the area can be a new radio access network (RAN) defined area (e.g., a RAN Notification Area (RNA) ) , which is different from the RAN defined area where the current candidate cell configuration is received. This option may be more advantageous for an inactive UE, which may perform a RAN-based Notification Area Update (RNAU) when moving into a new RNA. In such cases, for example, the request to update the candidate cell configuration can be piggybacked in or sent together with the RNAU message.
[0126] In some aspects, the area can be a new core network defined area (e.g., a Tracking Area (TA) ) , which is different from the core network defined area where the current candidate cell configuration is received. This option may be more advantageous for an idle UE, which may perform a Tracking Area Update (TAU) when moving into a new TA. In such cases, the request to update the candidate cell configuration can be piggybacked in or sent together with the TAU message.
[0127] In some aspects, the area can be a certain geographic area, which may be identified by one or more coordinates or cell IDs. For example, the area can include the physical area of all candidate cells in the currently stored candidate cell configurations.
[0128] In some aspects, the area can be the coverage of any measured candidate cell in the currently stored candidate cell configuration which contains the cell that previously delivered the current candidate cell configurations to the UE. For example, the non-connected UE can send the request to the currently camped cell if it is moving outside the coverage of the cell represented by PCI 0, which previously delivered the current candidate cell configuration to the UE.
[0129] In some aspects, the non-connected UE can request the candidate cell configuration update once a timer expires (e.g., where the timer duration begins at the reception of the currently stored candidate cell configurations) . For example, a timer duration value (e.g., which may be defined / determined by standards specifications or by the network) may start when the UE receives the currently stored candidate cell configurations.
[0130] In some aspects, the non-connected UE can request the candidate cell configuration update based on recent or future traffic activity. For example, the non-connected UE can transmit a request if a transferred amount of DL data and / or UL data exceeds a threshold in the previous X ms or is predicted (e.g., using a machine learning (ML) model) to exceed a threshold in future X ms.
[0131] In some aspects, the request may be based on any combination of options described above, jointly. For example, the UE can transmit the request if: 1) it moves outside a specific area for X ms, 2) a timer expires since the reception of the currently stored candidate cell configurations, AND 3) there is traffic activity in the previous Y ms meeting or exceeding a defined threshold.
[0132] In some aspects, the request may contain / convey various information. The request may include, for example, the UE ID or corresponding RNTI in a non-connected mode (e.g., I-RNTI) , based on which the request receiving cell can identify the UE.
[0133] The request may include a candidate cell configuration update version ID, based on which the network can identify the content of the currently stored candidate cell configurations at the UE.
[0134] The request may include assistance information to the network regarding the new candidate cells to be included in the updated candidate cell configurations, which may be based on UE-side artificial intelligence (AI) / ML prediction (e.g., with a corresponding confidence level) . The assistance information may be regarding, for example, a geographic area, path, or a set of PCIs that the requesting UE may stay, travel, or visit in the next X sec.
[0135] The request may include assistance information to the network regarding experienced or predicted traffic activity / statistics, which may be based on UE-side artificial intelligence (AI) / ML prediction (e.g., with a corresponding confidence level) . For example, the assistance information may be regarding a DL and / or UL traffic pattern or amount of such traffic experienced in the previous X ms or predicted in the future X ms.
[0136] Returning to FIG. 10, as illustrated at 1004, the network (e.g., a gNB) may provide updated candidate cell configuration (s) to the non-connected UE, in response to the request. Thus, instead of releasing the stored candidate cell configuration, UE in non-connected state can be provided with updated candidate cell configuration.
[0137] Alternatively, the updated candidate cell configuration for a set of new candidate cells may be autonomously provided by the network to the non-connected UE. This option may be understood with reference to FIG. 11, which depicts an example scenario 1100 with a pre-configured candidate cell set, where the UE moves outside of a coverage area of the pre-configured candidate cell set and receives a network-autonomous update, in accordance with aspects of the present disclosure.
[0138] As illustrated, the (non-connected state) UE has moved outside of a coverage area 802 of the pre-configured candidate cell set.
[0139] As illustrated at 1102, the network (e.g., a gNB) may (autonomously) provide updated candidate cell configuration (s) to the non-connected UE. In some aspects, the gNB can page / request the UE for a certain action, such as a RAN-based Notification Area Update (RNAU) or a Tracking Area Update (TAU) . After the UE performs such an action, the gNB can provide the updated candidate cell configurations in the response.
[0140] As described above with reference to FIG. 10, a UE in a non-connected mode may request to update the candidate cell configuration in certain conditions (e.g. moving outside the coverage of currently stored candidate cells, which become obsolete) . As noted above, in some aspects, a UE in a non-connected mode can be provided with (by the network autonomously or based on a request) the updated candidate cell configuration for a set of new candidate cells in advance, (e.g., before initiating the connected mode transition to one of those new candidate cells) which may speed up the transition to connected mode.
[0141] FIG. 12 depicts a call flow diagram 1200 illustrating techniques for candidate cell configuration updates for non-connected UEs, in accordance with aspects of the present disclosure. In some aspects, the UE shown in FIG. 12 may be an example of the UE 104 depicted and described with respect to FIGS. 1 and 3. In some aspects, the network entity (e.g., current camped PCell) shown in FIG. 12 may be an example of the BS 102 (e.g., a gNB) depicted and described with respect to FIGS. 1 and 3 or a disaggregated base station depicted and described with respect to FIG. 2.
[0142] Based on a request (or autonomously) , the network may provide a new set of candidate cell configurations (e.g., for a set of promising candidate cells based on the current UE’s location) to both the UE and those new candidate cells, as well as delivering UE context to those candidate cells, as shown at 1202.
[0143] The updated candidate cell configurations and corresponding UE context may be also provided to the corresponding candidate cells (e.g. the current camped cell when the UE later requests to transition to an RRC connected state upon the arrival of large amount of traffic) . As shown at 1202, the early candidate cell configuration update and UE context delivery may be performed before the non-connected UE initiates (e.g., in Msg1) of a random access procedure with a current camped cell, and before the non-connected UE initiates the RRC transition (e.g., in Msg3 described below) .
[0144] An advantage of this approach is that when the UE later initiates the transition to connected mode with the current camped cell, that cell is likely to be in the updated candidate cell configurations, which can reduce overhead and latency associated with retrieval of UE context by a current camped cell and sending / applying the candidate cell configuration based on UE capability (e.g., RRC resume in Msg4, resume complete in Msg5, as well as later SCell / SCG activation fiom the network) .
[0145] Similarly to call flow diagram 900, call flow diagram 1200 illustrates the non-connected UE initiating (Msg1) the random access procedure with the current camped cell, and the current cell responding (Msg2) with a random access response, allowing the UE to proceed with the RRC resume request.
[0146] In message 3 (Msg3) , the non-connected UE initiates the transition to RRC connected mode by transmitting signaling indicating a fast RRC transition request, which may include a UE ID, a corresponding RNTI (e.g., I-RNTI) , and the candidate cell configuration update version ID. The inclusion of such information may allow the network to identify the UE and the currently stored candidate cell configuration contents.
[0147] Based on the early updated candidate cell configuration as well as early measurement results, the non-connected UE can directly indicate or recommend activated SCells for DL / UL CA and / or SCG in the updated candidate cell configuration.
[0148] In some aspects, a UE-based cell activation signaling (e.g., a command or recommendation) can be sent together with the RRC transition request to the current camped cell (e.g. in Msg3) . This reduces overhead and latency (e.g., at the network) associated with a separate cell activation command. If the UE-based cell
[0149] In some aspects, when the UE transmits a UE-based cell activation recommendation, the gNB may modify the activated SCells / SCG in a later response.
[0150] In some aspects, the RRC transition request may be RRC resume signaling (e.g., for an inactive UE) or RRC setup signaling (e.g., for an idle UE) . After the RRC resume / setup procedure is complete, data can flow over the activated cells in the MCG, as illustrated.
[0151] As shown, the techniques illustrated in call flow diagram 1200 of FIG. 12 reduce overhead and latency associated with retrieval of UE context by a current camped cell and sending / applying the candidate cell configuration, as compared to the techniques described with reference to call flow diagram 900 of FIG. 9. As illustrated in FIG. 12 for example, the currently camped PCell does not need to retrieve UE context (902) from the original gNB after Msg3. Additionally, Msg4, Msg5, and MCG SCell activation signaling 904 may not be transmitted (omitted entirely) when utilizing the techniques disclosed herein.
[0152] In some aspects, a UE may indicate capability information to the network, indicating its capability to support early candidate cell configuration updates in a non-connected mode. In some aspects, such capability information may include additional details, such as a maximum quantity of stored candidate cell configurations in a non-connected mode (e.g., which may be different from that for connected mode mobility) . Such capability information may further indicate certain supported cell operation types for each candidate cell configuration, including single cell operation, intra-band CA, inter-band co-located CA, inter-band non-co-located CA, dual connectivity (DC) , and dual stack operations.
[0153] In some aspects, the indicated maximum quantity of stored candidate cell configurations may depend on the cell operation type per candidate cell configuration (e.g., more candidate cell configurations can be stored if each candidate cell configuration is only for a single cell operation) . In some aspects, the capability information may be indicated per UE, per band, per band combination (BC) , per feature set (FS) , or per feature set per carrier (FSPC) .
[0154] As described herein, a non-connected state may describe / include an idle state, an inactive state, or any other state in which a UE lacks an active radio resource control (RRC) connection.
[0155] Utilization of the techniques disclosed herein may reduce overhead and latency associated with retrieval of UE context by a current camped cell and sending / applying the candidate cell configuration based on UE capability. By reducing overhead and latency, overall quality of service (QoS) and quality of experience (QoE) may be improved for end users. Example Operations
[0156] FIG. 13 shows an example of a method 1300 of wireless communications at a wireless node, such as a UE 104 of FIGS. 1 and 3.
[0157] Method 1300 begins at step 1305 with obtaining first configuration information for a first set of one or more candidate cells. In some cases, the operations of this step refer to, or may be performed by, circuitry for obtaining and / or code for obtaining as described with reference to FIG. 15.
[0158] Method 1300 then proceeds to step 1310 with obtaining, while the wireless node is in a non-connected state, second configuration information for a second set of one or more candidate cells, wherein the second set includes at least one candidate cell that is not in the first set. In some cases, the operations of this step refer to, or may be performed by, circuitry for obtaining and / or code for obtaining as described with reference to FIG. 15.
[0159] Method 1300 then proceeds to step 1315 with participating in a procedure, with a candidate cell in the second set, to transition to a connected state. In some cases, the operations of this step refer to, or may be performed by, circuitry for participating and / or code for participating as described with reference to FIG. 15.
[0160] In some aspects, the method 1300 further includes outputting a request while in the non-connected state, wherein the second configuration is obtained after outputting the request. In some cases, the operations of this step refer to, or may be performed by, circuitry for outputting and / or code for outputting as described with reference to FIG. 15.
[0161] In some aspects, the request is output when at least one condition is met.
[0162] In some aspects, the at least one condition is at least one of: configured by a network entity; or defined by a wireless communications standard specification.
[0163] In some aspects, the at least one condition is considered met if the wireless node moves outside of an area.
[0164] In some aspects, the method 1300 further includes setting a timer after the wireless node moves outside of the area, wherein the at least one condition is considered met if the wireless node is outside of the area for a duration associated with the timer. In some cases, the operations of this step refer to, or may be performed by, circuitry for setting and / or code for setting as described with reference to FIG. 15.
[0165] In some aspects, the method 1300 further includes setting a timer after the wireless node obtains the second configuration information, wherein the at least one condition is considered met when a duration of the timer expires. In some cases, the operations of this step refer to, or may be performed by, circuitry for setting and / or code for setting as described with reference to FIG. 15.
[0166] In some aspects, the method 1300 further includes obtaining signaling configuring the wireless node with the duration associated with the timer. In some cases, the operations of this step refer to, or may be performed by, circuitry for obtaining and / or code for obtaining as described with reference to FIG. 15.
[0167] In some aspects, the at least one condition is based on at least one of: historic traffic meeting or exceeding a threshold, or future traffic meeting or exceeding a threshold.
[0168] In some aspects, the area comprises: a radio access network (RAN) notification area (RNA) , a tracking area (TA) , a geographical area, or a coverage area associated with the first set of one or more candidate cells.
[0169] In some aspects, the request conveys at least one of: an identifier (ID) associated with the wireless node, a radio network temporary identifier (RNTI) , or a candidate cell configuration update version ID.
[0170] In some aspects, the request includes information indicating at least one of: predicted one or more target candidate cells, or historical or predicted traffic.
[0171] In some aspects, the method 1300 further includes obtaining a message. In some cases, the operations of this step refer to, or may be performed by, circuitry for obtaining and / or code for obtaining as described with reference to FIG. 15.
[0172] In some aspects, the method 1300 further includes outputting a response to the message, wherein the second configuration information is obtained after outputting the response. In some cases, the operations of this step refer to, or may be performed by, circuitry for outputting and / or code for outputting as described with reference to FIG. 15.
[0173] In some aspects, the response comprises a radio access network (RAN) -based notification area update (RNAU) or a tracking area update (TAU) .
[0174] In some aspects, the non-connected state comprises a state in which the wireless node lacks an active radio resource control (RRC) connection.
[0175] In some aspects, the second configuration information for the second set of one or more candidate cells comprises a candidate cell configuration for each of the one or more candidate cells in the second set.
[0176] In some aspects, each candidate cell configuration: is configured to enable a candidate cell to serve the wireless node as a serving cell, and is configured to configure a candidate cell for at least one of carrier aggregation (CA) operation, dual connectivity (DC) operation, or dual stack operation.
[0177] In some aspects, participating in the procedure comprises outputting signaling indicating at least one of: a request to transition to the connected state, or cell activation message for at least one candidate cell of the second set.
[0178] In some aspects, the request to transition to the connected state conveys at least one of: an identifier (ID) associated with the wireless node, a radio network temporary identifier (RNTI) , or a candidate cell configuration update version ID.
[0179] In some aspects, the method 1300 further includes outputting signaling indicating a capability of the wireless node to support one or more candidate cell configuration updates while the wireless node is operating in a non-connected mode, wherein the second configuration information is obtained after indication of the capability. In some cases, the operations of this step refer to, or may be performed by, circuitry for outputting and / or code for outputting as described with reference to FIG. 15.
[0180] In some aspects, the signaling indicates at least one of: a maximum quantity of one or more candidate cell configurations that the wireless node is capable of storing, or a capability of the wireless node to support at least one of single cell operation, carrier aggregation (CA) operation, dual connectivity (DC) operation, or dual stack operation.
[0181] In one aspect, method 1300, or any aspect related to it, may be performed by an apparatus, such as communications device 1500 of FIG. 15, which includes various components operable, configured, or adapted to perform the method 1300. Communications device 1500 is described below in further detail.
[0182] Note that FIG. 13 is just one example of a method, and other methods including fewer, additional, or alternative steps are possible consistent with this disclosure.
[0183] FIG. 14 shows an example of a method 1400 of wireless communication at a wireless node, such as a BS 102 of FIGS. 1 and 3, or a disaggregated base station as discussed with respect to FIG. 2.
[0184] Method 1400 begins at step 1405 with outputting, to a wireless node, first configuration information for a first set of one or more candidate cells. In some cases, the operations of this step refer to, or may be performed by, circuitry for outputting and / or code for outputting as described with reference to FIG. 15.
[0185] Method 1400 then proceeds to step 1410 with outputting, to the wireless node while the wireless node is in a non-connected state, second configuration information for a second set of one or more candidate cells, wherein the second set includes at least one candidate cell that is not in the first set. In some cases, the operations of this step refer to, or may be performed by, circuitry for outputting and / or code for outputting as described with reference to FIG. 15.
[0186] In some aspects, the method 1400 further includes obtaining a request, from the wireless node while the wireless node in the non-connected state, wherein the second configuration is output after outputting the request. In some cases, the operations of this step refer to, or may be performed by, circuitry for obtaining and / or code for obtaining as described with reference to FIG. 15.
[0187] In some aspects, the request conveys at least one of: an identifier (ID) associated with the wireless node, a radio network temporary identifier (RNTI) , or a candidate cell configuration update version ID.
[0188] In some aspects, the request includes information indicating at least one of: predicted one or more target candidate cells, or historical or predicted traffic.
[0189] In some aspects, the method 1400 further includes outputting a message. In some cases, the operations of this step refer to, or may be performed by, circuitry for outputting and / or code for outputting as described with reference to FIG. 15.
[0190] In some aspects, the method 1400 further includes obtaining a response to the message, wherein the second configuration information is obtained after obtaining the response. In some cases, the operations of this step refer to, or may be performed by, circuitry for obtaining and / or code for obtaining as described with reference to FIG. 15.
[0191] In some aspects, the response comprises a radio access network (RAN) -based notification area update (RNAU) or a tracking area update (TAU) .
[0192] In some aspects, the non-connected state comprises a state in which the wireless node lacks an active radio resource control (RRC) connection.
[0193] In some aspects, the second configuration information for the second set of one or more candidate cells comprises a candidate cell configuration for each of the one or more candidate cells in the second set.
[0194] In some aspects, each candidate cell configuration: is configured to enable a candidate cell to serve the wireless node as a serving cell, and is configured to configure a candidate cell for at least one of carrier aggregation (CA) operation, dual connectivity (DC) operation, or dual stack operation.
[0195] In some aspects, the method 1400 further includes obtaining signaling indicating a capability of the wireless node to support one or more candidate cell configuration updates while the wireless node is operating in a non-connected mode, wherein the second configuration information is output after obtaining the indication of the capability. In some cases, the operations of this step refer to, or may be performed by, circuitry for obtaining and / or code for obtaining as described with reference to FIG. 15.
[0196] In some aspects, the signaling indicates at least one of: a maximum quantity of one or more candidate cell configurations that the wireless node is capable of storing, or a capability of the wireless node to support at least one of single cell operation, carrier aggregation (CA) operation, dual connectivity (DC) operation, or dual stack operation.
[0197] In one aspect, method 1400, or any aspect related to it, may be performed by an apparatus, such as communications device 1500 of FIG. 15, which includes various components operable, configured, or adapted to perform the method 1400. Communications device 1500 is described below in further detail.
[0198] Note that FIG. 14 is just one example of a method, and other methods including fewer, additional, or alternative steps are possible consistent with this disclosure. Example Communications Device (s)
[0199] FIG. 15 depicts aspects of an example communications device 1500. In some aspects, communications device 1500 is a user equipment, such as UE 104 described above with respect to FIGS. 1 and 3. In some aspects, communications device 1500 is a network entity, such as BS 102 of FIGS. 1 and 3, or a disaggregated base station as discussed with respect to FIG. 2.
[0200] The communications device 1500 includes a processing system 1505 coupled to the transceiver 1565 (e.g., a transmitter and / or a receiver) . In some aspects (e.g., when communications device 1500 is a network entity) , processing system 1505 may be coupled to a network interface 1575 that is configured to obtain and send signals for the communications device 1500 via communication link (s) , such as a backhaul link, midhaul link, and / or fronthaul link as described herein, such as with respect to FIG. 2. The transceiver 1565 is configured to transmit and receive signals for the communications device 1500 via the antenna 1570, such as the various signals as described herein. The processing system 1505 may be configured to perform processing functions for the communications device 1500, including processing signals received and / or to be transmitted by the communications device 1500.
[0201] The processing system 1505 includes one or more processors 1510. In various aspects, the one or more processors 1510 may be representative of one or more of receive processor 358, transmit processor 364, TX MIMO processor 366, and / or controller / processor 380, as described with respect to FIG. 3. In various aspects, one or more processors 1510 may be representative of one or more of receive processor 338, transmit processor 320, TX MIMO processor 330, and / or controller / processor 340, as described with respect to FIG. 3. The one or more processors 1510 are coupled to a computer-readable medium / memory 1535 via a bus 1560. In certain aspects, the computer-readable medium / memory 1535 is configured to store instructions (e.g., computer-executable code) that when executed by the one or more processors 1510, cause the one or more processors 1510 to perform the method 1300 described with respect to FIG. 13, or any aspect related to it; and the method 1400 described with respect to FIG. 14, or any aspect related to it. Note that reference to a processor performing a function of communications device 1500 may include one or more processors 1510 performing that function of communications device 1500.
[0202] In the depicted example, computer-readable medium / memory 1535 stores code (e.g., executable instructions) , such as code for obtaining 1540, code for participating 1545, code for outputting 1550, and code for setting 1555. Processing of the code for obtaining 1540, code for participating 1545, code for outputting 1550, and code for setting 1555 may cause the communications device 1500 to perform the method 1300 described with respect to FIG. 13, or any aspect related to it; and the method 1400 described with respect to FIG. 14, or any aspect related to it.
[0203] The one or more processors 1510 include circuitry configured to implement (e.g., execute) the code stored in the computer-readable medium / memory 1535, including circuitry for obtaining 1515, circuitry for participating 1520, circuitry for outputting 1525, and circuitry for setting 1530. Processing with circuitry for obtaining 1515, circuitry for participating 1520, circuitry for outputting 1525, and circuitry for setting 1530 may cause the communications device 1500 to perform the method 1300 described with respect to FIG. 13, or any aspect related to it; and the method 1400 described with respect to FIG. 14, or any aspect related to it.
[0204] Various components of the communications device 1500 may provide means for performing the method 1300 described with respect to FIG. 13, or any aspect related to it; and the method 1400 described with respect to FIG. 14, or any aspect related to it. For example, means for transmitting, sending or outputting for transmission may include transceivers 354 and / or antenna (s) 352 of the UE 104 illustrated in FIG. 3, transceivers 332 and / or antenna (s) 334 of the BS 102 illustrated in FIG. 3, and / or the transceiver 1565 and the antenna 1570 of the communications device 1500 in FIG. 15. Means for receiving or obtaining may include transceivers 354 and / or antenna (s) 352 of the UE 104 illustrated in FIG. 3, transceivers 332 and / or antenna (s) 334 of the BS 102 illustrated in FIG. 3, and / or the transceiver 1565 and the antenna 1570 of the communications device 1500 in FIG. 15. Example Clauses
[0205] Implementation examples are described in the following numbered clauses:
[0206] Clause 1: A method for wireless communications at a wireless node, comprising: obtaining first configuration information for a first set of one or more candidate cells; obtaining, while the wireless node is in a non-connected state, second configuration information for a second set of one or more candidate cells, wherein the second set includes at least one candidate cell that is not in the first set; and participating in a procedure, with a candidate cell in the second set, to transition to a connected state.
[0207] Clause 2: The method of Clause 1, further comprising: outputting a request while in the non-connected state, wherein the second configuration is obtained after outputting the request.
[0208] Clause 3: The method of Clause 2, wherein: the request is output when at least one condition is met.
[0209] Clause 4: The method of Clause 3, wherein the at least one condition is at least one of: configured by a network entity; or defined by a wireless connunications standard specification.
[0210] Clause 5: The method of Clause 3, wherein the at least one condition is considered met if the wireless node moves outside of an area.
[0211] Clause 6: The method of Clause 5, further comprising at least one of: setting a timer after the wireless node moves outside of the area, wherein the at least one condition is considered met if the wireless node is outside of the area for a duration associated with the timer; and setting a timer after the wireless node obtains the second configuration information, wherein the at least one condition is considered met when a duration of the timer expires.
[0212] Clause 7: The method of Clause 6, further comprising: obtaining signaling configuring the wireless node with the duration associated with the timer.
[0213] Clause 8: The method of Clause 5, wherein the at least one condition is based on at least one of: historic traffic meeting or exceeding a threshold, or future traffic meeting or exceeding a threshold.
[0214] Clause 9: The method of Clause 5, wherein the area comprises: a radio access network (RAN) notification area (RNA) , a tracking area (TA) , a geographical area, or a coverage area associated with the first set of one or more candidate cells.
[0215] Clause 10: The method of Clause 2, wherein the request conveys at least one of: an identifier (ID) associated with the wireless node, a radio network temporary identifier (RNTI) , or a candidate cell configuration update version ID.
[0216] Clause 11: The method of Clause 2, wherein the request includes information indicating at least one of: predicted one or more target candidate cells, or historical or predicted traffic.
[0217] Clause 12: The method of any one of Clauses 1-11, further comprising: obtaining a message; and outputting a response to the message, wherein the second configuration information is obtained after outputting the response.
[0218] Clause 13: The method of Clause 12, wherein the response comprises a radio access network (RAN) -based notification area update (RNAU) or a tracking area update (TAU) .
[0219] Clause 14: The method of any one of Clauses 1-13, wherein the non-connected state comprises a state in which the wireless node lacks an active radio resource control (RRC) connection.
[0220] Clause 15: The method of any one of Clauses 1-14, wherein the second configuration information for the second set of one or more candidate cells comprises a candidate cell configuration for each of the one or more candidate cells in the second set.
[0221] Clause 16: The method of Clause 15, wherein each candidate cell configuration: is configured to enable a candidate cell to serve the wireless node as a serving cell, and is configured to configure a candidate cell for at least one of carrier aggregation (CA) operation, dual connectivity (DC) operation, or dual stack operation.
[0222] Clause 17: The method of any one of Clauses 1-16, wherein participating in the procedure comprises outputting signaling indicating at least one of: a request to transition to the connected state, or cell activation message for at least one candidate cell of the second set.
[0223] Clause 18: The method of Clause 17, wherein the request to transition to the connected state conveys at least one of: an identifier (ID) associated with the wireless node, a radio network temporary identifier (RNTI) , or a candidate cell configuration update version ID.
[0224] Clause 19: The method of any one of Clauses 1-18, further comprising outputting signaling indicating a capability of the wireless node to support one or more candidate cell configuration updates while the wireless node is operating in a non-connected mode, wherein the second configuration information is obtained after indication of the capability.
[0225] Clause 20: The method of Clause 19, wherein the signaling indicates at least one of: a maximum quantity of one or more candidate cell configurations that the wireless node is capable of storing, or a capability of the wireless node to support at least one of single cell operation, carrier aggregation (CA) operation, dual connectivity (DC) operation, or dual stack operation.
[0226] Clause 21: A method for wireless communications, comprising: outputting, to a wireless node, first configuration information for a first set of one or more candidate cells; and outputting, to the wireless node while the wireless node is in a non-connected state, second configuration information for a second set of one or more candidate cells, wherein the second set includes at least one candidate cell that is not in the first set.
[0227] Clause 22: The method of Clause 21, further comprising: obtaining a request, from the wireless node while the wireless node in the non-connected state, wherein the second configuration is output after outputting the request.
[0228] Clause 23: The method of Clause 22, wherein the request conveys at least one of: an identifier (ID) associated with the wireless node, a radio network temporary identifier (RNTI) , or a candidate cell configuration update version ID.
[0229] Clause 24: The method of Clause 22, wherein the request includes information indicating at least one of: predicted one or more target candidate cells, or historical or predicted traffic.
[0230] Clause 25: The method of any one of Clauses 21-24, further comprising: outputting a message; and obtaining a response to the message, wherein the second configuration information is obtained after obtaining the response.
[0231] Clause 26: The method of Clause 25, wherein the response comprises a radio access network (RAN) -based notification area update (RNAU) or a tracking area update (TAU) .
[0232] Clause 27: The method of any one of Clauses 21-26, wherein the non-connected state comprises a state in which the wireless node lacks an active radio resource control (RRC) connection.
[0233] Clause 28: The method of any one of Clauses 21-27, wherein the second configuration information for the second set of one or more candidate cells comprises a candidate cell configuration for each of the one or more candidate cells in the second set.
[0234] Clause 29: The method of Clause 28, wherein each candidate cell configuration: is configured to enable a candidate cell to serve the wireless node as a serving cell, and is configured to configure a candidate cell for at least one of carrier aggregation (CA) operation, dual connectivity (DC) operation, or dual stack operation.
[0235] Clause 30: The method of any one of Clauses 21-29, further comprising obtaining signaling indicating a capability of the wireless node to support one or more candidate cell configuration updates while the wireless node is operating in a non-connected mode, wherein the second configuration information is output after obtaining the indication of the capability.
[0236] Clause 31: The method of Clause 30, wherein the signaling indicates at least one of: a maximum quantity of one or more candidate cell configurations that the wireless node is capable of storing, or a capability of the wireless node to support at least one of single cell operation, carrier aggregation (CA) operation, dual connectivity (DC) operation, or dual stack operation.
[0237] Clause 32: An apparatus, comprising: at least one memory comprising executable instructions; and at least one processor configured to execute the executable instructions to cause the apparatus to perform a method in accordance with any combination of Clauses 1-31.
[0238] Clause 33: An apparatus, comprising means for performing a method in accordance with any combination of Clauses 1-31.
[0239] Clause 34: A non-transitory computer-readable medium comprising executable instructions that, when executed by at least one processor of an apparatus, cause the apparatus to perform a method in accordance with any combination of Clauses 1-31.
[0240] Clause 35: A computer program product embodied on a computer-readable storage medium comprising code for performing a method in accordance with any combination of Clauses 1-31.
[0241] Clause 36: A wireless node (e.g., a UE) , comprising at least one transceiver; at least one memory comprising executable instructions; and at least one processor configured to execute the executable instructions to cause the apparatus to perform a method in accordance with any combination of Clauses 1-20, wherein the at least one transceiver is configured to receive the first configuration information and the second configuration information.
[0242] Clause 37: A wireless node (e.g., a network entity) , comprising at least one transceiver; at least one memory comprising executable instructions; and at least one processor configured to execute the executable instructions to cause the apparatus to perform a method in accordance with any combination of Clauses 21-31, wherein the at least one transceiver is configured to transmit the first configuration information and the second configuration information. Additional Considerations
[0243] The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples discussed herein are not limiting of the scope, applicability, or aspects set forth in the claims. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. For example, changes may be made in the function and arrangement of elements discussed without departing from the scope of the disclosure. Various examples may omit, substitute, or add various procedures or components as appropriate. For instance, the methods described may be performed in an order different from that described, and various actions may be added, omitted, or combined. Also, features described with respect to some examples may be combined in some other examples. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method that is practiced using other structure, functionality, or structure and functionality in addition to, or other than, the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.
[0244] The various illustrative logical blocks, modules and circuits described in connection with the present disclosure may be implemented or performed with a general purpose processor, a graphics processing unit (GPU) , a neural processing unit (NPU) , a digital signal processor (DSP) , an ASIC, a field programmable gate array (FPGA) or other programmable logic device (PLD) , discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, a system on a chip (SoC) , or any other such configuration.
[0245] As used herein, “a processor, ” “at least one processor” or “one or more processors” generally refers to a single processor configured to perform one or multiple operations or multiple processors configured to collectively perform one or more operations. In the case of multiple processors, performance of the one or more operations could be divided amongst different processors, though one processor may perform multiple operations, and multiple processors could collectively perform a single operation. Similarly, “a memory, ” “at least one memory” or “one or more memories” generally refers to a single memory configured to store data and / or instructions, multiple memories configured to collectively store data and / or instructions.
[0246] In some cases, rather than actually transmitting a signal, an apparatus (e.g., a wireless node or device) may have an interface to output the signal for transmission. For example, a processor may output a signal, via a bus interface, to a radio frequency (RF) front end for transmission. Accordingly, a means for outputting may include such an interface as an alternative (or in addition) to a transmitter or transceiver. Similarly, rather than actually receiving a signal, an apparatus (e.g., a wireless node or device) may have an interface to obtain a signal from another device. For example, a processor may obtain (or receive) a signal, via a bus interface, from an RF front end for reception. Accordingly, a means for obtaining may include such an interface as an alternative (or in addition) to a receiver or transceiver.
[0247] While the present disclosure may describe certain operations as being performed by one type of wireless node, the same or similar operations may also be performed by another type of wireless node. For example, operations performed by a user equipment (UE) may also (or instead) be performed by a network entity (e.g., a base station or unit of a disaggregated base station) . Similarly, operations performed by a network entity may also (or instead) be performed by a UE.
[0248] Further, while the present disclosure may describe certain types of communications between different types of wireless nodes (e.g., between a network entity and a UE) , the same or similar types of communications may occur between same types of wireless nodes (e.g., between network entities or between UEs, in a peer-to-peer scenario) . Further, communications may occur in reverse order than described.
[0249] Means for obtaining, means for participating, and means for outputting may comprise one or more processors, such as one or more of the processors described above with reference to FIG. 15.
[0250] As used herein, a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c) .
[0251] As used herein, the term “determining” encompasses a wide variety of actions. For example, “determining” may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database or another data structure) , ascertaining and the like. Also, “determining” may include receiving (e.g., receiving information) , accessing (e.g., accessing data in a memory) and the like. Also, “determining” may include resolving, selecting, choosing, establishing and the like.
[0252] The methods disclosed herein comprise one or more actions for achieving the methods. The method actions may be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order of actions is specified, the order and / or use of specific actions may be modified without departing from the scope of the claims. Further, the various operations of methods described above may be performed by any suitable means capable of performing the corresponding functions. The means may include various hardware and / or software component (s) and / or module (s) , including, but not limited to a circuit, an application specific integrated circuit (ASIC) , or processor. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, or functions, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
[0253] The following claims are not intended to be limited to the aspects shown herein, but are to be accorded the full scope consistent with the language of the claims. Within a claim, reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more. ” Unless specifically stated otherwise, the term “some” refers to one or more. No claim element is to be construed under the provisions of 35 U.S.C. § 112 (f) unless the element is expressly recited using the phrase “means for” . All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims.
Claims
1.An apparatus for wireless communications, comprising:at least one memory comprising computer-executable instructions; andone or more processors configured to execute the computer-executable instructions to cause the apparatus to:obtain first configuration information for a first set of one or more candidate cells;obtain, while the apparatus is in a non-connected state, second configuration information for a second set of one or more candidate cells, wherein the second set includes at least one candidate cell that is not in the first set; andparticipate in a procedure, with a candidate cell in the second set, to transition to a connected state.2.The apparatus of claim 1, wherein the one or more processors are further configured to cause the apparatus to:output a request while in the non-connected state, wherein the second configuration is obtained after outputting the request.3.The apparatus of claim 2, wherein:the request is output when at least one condition is met.4.The apparatus of claim 3, wherein the at least one condition is at least one of:configured by a network entity; ordefined by a wireless communications standard specification.5.The apparatus of claim 3, wherein the at least one condition is considered met if the apparatus moves outside of an area.6.The apparatus of claim 5, wherein the one or more processors are further configured to cause the apparatus to at least one of:set a timer after the apparatus moves outside of the area, wherein the at least one condition is considered met if the apparatus is outside of the area for a duration associated with the timer; orset a timer after the apparatus obtains the second configuration information, wherein the at least one condition is considered met when a duration of the timer expires.7.The apparatus of claim 6, wherein the one or more processors are further configured to cause the apparatus to:obtain signaling configuring the apparatus with the duration associated with the timer.8.The apparatus of claim 5, wherein the at least one condition is based on at least one of:historic traffic meeting or exceeding a threshold, orfuture traffic meeting or exceeding a threshold.9.The apparatus of claim 5, wherein the area comprises:a radio access network (RAN) notification area (RNA) ,a tracking area (TA) ,a geographical area, ora coverage area associated with the first set of one or more candidate cells.10.The apparatus of claim 2, wherein the request conveys at least one of:an identifier (ID) associated with the apparatus,a radio network temporary identifier (RNTI) , ora candidate cell configuration update version ID.11.The apparatus of claim 2, wherein the request includes information indicating at least one of:predicted one or more target candidate cells, orhistorical or predicted traffic.12.The apparatus of claim 1, wherein the one or more processors are further configured to cause the apparatus to:obtain a message; andoutput a response to the message, wherein the second configuration information is obtained after outputting the response.13.The apparatus of claim 12, wherein the response comprises a radio access network (RAN) -based notification area update (RNAU) or a tracking area update (TAU) .14.The apparatus of claim 1, wherein the non-connected state comprises a state in which the apparatus lacks an active radio resource control (RRC) connection.15.The apparatus of claim 1, wherein the second configuration information for the second set of one or more candidate cells comprises a candidate cell configuration for each of the one or more candidate cells in the second set.16.The apparatus of claim 15, wherein each candidate cell configuration:is configured to enable a candidate cell to serve the apparatus as a serving cell, andis configured to configure a candidate cell for at least one of carrier aggregation (CA) operation, dual connectivity (DC) operation, or dual stack operation.17.The apparatus of claim 1, wherein in order to participate in the procedure, the one or more processors are configured to cause the apparatus to output signaling indicating at least one of:a request to transition to the connected state, orcell activation message for at least one candidate cell of the second set.18.The apparatus of claim 17, wherein the request to transition to the connected state conveys at least one of:an identifier (ID) associated with the apparatus,a radio network temporary identifier (RNTI) , ora candidate cell configuration update version ID.19.The apparatus of claim 1, wherein the one or more processors are further configured to cause the apparatus to output signaling indicating a capability of the apparatus to support one or more candidate cell configuration updates while the apparatus is operating in a non-connected mode, wherein the second configuration information is obtained after indication of the capability.20.The apparatus of claim 19, wherein the signaling indicates at least one of:a maximum quantity of one or more candidate cell configurations that the apparatus is capable of storing, ora capability of the apparatus to support at least one of single cell operation, carrier aggregation (CA) operation, dual connectivity (DC) operation, or dual stack operation.21.The apparatus of claim 20, further comprising at least one transceiver configured to receive the first configuration information and the second configuration information, wherein the apparatus is configured as a user equipment (UE) .22.An apparatus for wireless communications, comprising:at least one memory comprising computer-executable instructions; andone or more processors configured to execute the computer-executable instructions to cause the apparatus to:output, to a wireless node, first configuration information for a first set of one or more candidate cells; andoutput, to the wireless node while the wireless node is in a non-connected state, second configuration information for a second set of one or more candidate cells, wherein the second set includes at least one candidate cell that is not in the first set.23.The apparatus of claim 22, wherein the one or more processors are further configured to cause the apparatus to:obtain a request, from the wireless node while the wireless node in the non-connected state, wherein the second configuration is output after outputting the request.24.The apparatus of claim 23, wherein the request conveys at least one of:an identifier (ID) associated with the wireless node,a radio network temporary identifier (RNTI) , ora candidate cell configuration update version ID.25.The apparatus of claim 23, wherein the request includes information indicating at least one of:predicted one or more target candidate cells, orhistorical or predicted traffic.26.The apparatus of claim 22, wherein the one or more processors are further configured to cause the apparatus to:output a message; andobtain a response to the message, wherein the second configuration information is obtained after obtaining the response.27.The apparatus of claim 26, wherein the response comprises a radio access network (RAN) -based notification area update (RNAU) or a tracking area update (TAU) .28.The apparatus of claim 22, wherein the non-connected state comprises a state in which the wireless node lacks an active radio resource control (RRC) connection.29.The apparatus of claim 22, wherein the second configuration information for the second set of one or more candidate cells comprises a candidate cell configuration for each of the one or more candidate cells in the second set.30.The apparatus of claim 29, wherein each candidate cell configuration:is configured to enable a candidate cell to serve the wireless node as a serving cell, andis configured to configure a candidate cell for at least one of carrier aggregation (CA) operation, dual connectivity (DC) operation, or dual stack operation.31.The apparatus of claim 22, wherein the one or more processors are further configured to cause the apparatus to obtain signaling indicating a capability of the wireless node to support one or more candidate cell configuration updates while the wireless node is operating in a non-connected mode, wherein the second configuration information is output after obtaining the indication of the capability.32.The apparatus of claim 31, wherein the signaling indicates at least one of:a maximum quantity of one or more candidate cell configurations that the wireless node is capable of storing, ora capability of the wireless node to support at least one of single cell operation, carrier aggregation (CA) operation, dual connectivity (DC) operation, or dual stack operation.33.The apparatus of claim 22, further comprising at least one transceiver configured to transmit the first configuration information and the second configuration information, wherein the apparatus is configured as a network entity.
