QOE-based network selection

Abstract

Apparatus and methods for QOE-based network selection are described. An apparatus is configured to obtain a set of cell metrics for cells associated with a UE. The set of cell metrics includes RSRP and at least one potential latency, number of layers, or service characteristics. The apparatus is configured to initiate or maintain a connection with the cell based on a combined metric satisfying a threshold condition, the combined metric based on the set of cell metrics. Another apparatus is configured to obtain a set of cell metrics for cells associated with a UE. The set of cell metrics includes RSRP and at least one potential latency, number of layers, or service characteristics. The apparatus is configured to initiate or maintain a connection of the UE to the cell based on a combined metric satisfying a threshold condition, the combined metric based on the set of cell metrics.

Description

Technical Field

[0001] This disclosure relates generally to communication systems, and more specifically to wireless communication utilizing cell selection. Background Technology

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0003] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, national, regional, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the Continuous Evolution of Mobile Broadband (CEM) program issued by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT),) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR can be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. Furthermore, these improvements can also be applied to other multiple access technologies and telecommunications standards that adopt these technologies. Summary of the Invention

[0004] The following is a simplified summary of one or more aspects to provide a basic understanding of these aspects. This summary is not a comprehensive overview of all conceived aspects. It neither identifies key or essential elements of all aspects nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed descriptions that follow.

[0005] In one aspect of this disclosure, a method, computer-readable medium, and apparatus are provided. The apparatus may be associated with, or may be a, a user equipment (UE). The apparatus is configured to obtain a set of cell metrics associated with the UE, wherein the set of cell metrics includes at least one of reference received signal power (RSRP) and potential delay, stratum number, or service characteristics. The apparatus is also configured to initiate or maintain a connection with the cell associated with the UE based on a combined metric satisfying a threshold condition, wherein the combined metric is based on the set of cell metrics.

[0006] In this respect, the method includes obtaining a set of cell metrics associated with the UE, wherein the set of cell metrics includes RSRP and at least one of potential latency, tier number, or service characteristics. The method also includes initiating or maintaining a connection with the cell associated with the UE based on a threshold condition met by a combination of metrics, wherein the combination of metrics is based on the set of cell metrics.

[0007] In another aspect of this disclosure, a method, computer-readable medium, and apparatus are provided. The apparatus is configured to obtain a set of cell metrics associated with a UE, wherein the set of cell metrics includes RSRP and at least one of potential latency, tier number, or service characteristics. The apparatus is also configured to initiate or maintain a connection from the UE to the cell associated with the UE based on a threshold condition met by a combined metric, wherein the combined metric is based on the set of cell metrics.

[0008] In this respect, the method includes obtaining a set of cell metrics associated with the UE, wherein the set of cell metrics includes RSRP and at least one of potential latency, tier number, or service characteristics. The method also includes initiating or maintaining a connection from the UE to the cell associated with the UE based on a threshold condition met by a combination of metrics, wherein the combination of metrics is based on the set of cell metrics.

[0009] To achieve the foregoing and related objectives, one or more aspects may include the features fully described below and specifically pointed out in the claims. The following description and drawings set forth some exemplary features of one or more aspects in detail. However, these features indicate only a few of the various ways in which the principles of the various aspects may be employed. Attached Figure Description

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

[0011] Figure 2A This is an illustration of an example of the first frame according to various aspects of this disclosure.

[0012] Figure 2B This is a diagram illustrating examples of downlink (DL) channels within a subframe according to various aspects of this disclosure.

[0013] Figure 2C This is an illustration of an example of a second frame according to various aspects of this disclosure.

[0014] Figure 2D This is a diagram illustrating examples of uplink (UL) channels within a subframe according to various aspects of this disclosure.

[0015] Figure 3 This is a diagram illustrating examples of base stations and user equipment (UEs) in an access network.

[0016] Figure 4 This is a diagram illustrating an example of cell selection based on signal quality.

[0017] Figure 5 This is a call flow diagram for wireless communication based on various aspects of this disclosure.

[0018] Figure 6 This is a diagram illustrating examples of user QOE-based cell selection according to various aspects of this disclosure.

[0019] Figure 7 This is a diagram illustrating examples of user QOE-based cell selection according to various aspects of this disclosure.

[0020] Figure 8 This is a diagram illustrating examples of user QOE-based cell selection according to various aspects of this disclosure.

[0021] Figure 9 This is a flowchart of a wireless communication method according to various aspects of this disclosure.

[0022] Figure 10 This is a flowchart of a wireless communication method according to various aspects of this disclosure.

[0023] Figure 11 This is a flowchart of a wireless communication method according to various aspects of this disclosure.

[0024] Figure 12 This is a flowchart of a wireless communication method according to various aspects of this disclosure.

[0025] Figure 13 These are illustrations illustrating specific hardware implementations used for example devices and / or network entities.

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

[0027] Figure 15 This is a diagram illustrating an example of a hardware implementation used for an example network entity. Detailed Implementation

[0028] Wireless communication networks (such as LTE networks and / or 5G NR networks) can be designed to support UE mobility. For example, wireless communication systems can support the use of RSRP as an indicator of signal quality. Based on signal quality, the network can determine whether to hand over the UE from one cell to another, which allows the UE to communicate with the new serving cell using higher quality signaling.

[0029] However, basing UE mobility on signal quality without other considerations may lead to scenarios where this approach fails to meet the user's expected experience. Furthermore, in geographical areas where TDD and FDD cells overlap, signal quality mobility does not consider how TDD and FDD cells can be applied to improve the user's QOE. As an example, gaming and voice calls in mobility can be user-sensitive applications, where bursts of low-latency and high-quality small random-size packet transmission are beneficial in gaming, while the regular periodicity of very high-quality unacknowledged pattern (UM) packets may be important in voice calls. Both applications can benefit from different types of serving cells. As another example, downloading data in mobility can benefit from the highest data rate that can complete the download in a short time to save power, while long travel times in mobility can benefit from keeping the UE in a very low-power mode while waiting for a charging opportunity.

[0030] The various aspects generally relate to wireless communication systems utilizing cell selection. Some aspects more specifically relate to QOE-based network / cell selection for a UE. In one example, a UE may be configured to obtain a set of cell metrics associated with the UE, wherein the set of cell metrics includes at least one of a Reference Signal Received Power (RSRP) and potential delay, tier number, or service characteristics. The UE may also be configured to initiate or maintain a connection to a cell associated with the UE based on a threshold condition met by a combination of metrics, wherein the combination of metrics is based on a set of cell metrics. In another example, a network node (e.g., a base station, gNB, etc.) may be configured to obtain a set of cell metrics associated with the UE, wherein the set of cell metrics includes at least one of a RSRP and potential delay, tier number, or service characteristics. The network node may also be configured to initiate or maintain a connection from the UE to a cell associated with the UE based on a threshold condition met by a combination of metrics, wherein the combination of metrics is based on a set of cell metrics. In some examples, in addition to or in lieu of RSRP considerations, the selection of the cell for serving the UE can be based on QOE, and the choice between TDD or FDD can be considered based on QOE metrics for both the user and UE sides, as well as for the service / application type of the provider.

[0031] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In one example, by taking into account QOE metrics associated with user and UE-side considerations as well as service / application types for the provider, the described techniques can be used to provide better cell selection for TDD and FDD utilization.

[0032] The detailed descriptions following, illustrated with reference to the accompanying drawings, describe various configurations and do not represent the only configurations in which the concepts described herein can be practiced. To provide a thorough understanding of the various concepts, the detailed descriptions include specific details. However, these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0033] Various apparatuses and methods are presented with reference to several aspects of a telecommunications system. These apparatuses and methods are described in detail below and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, “elements”). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0034] As an example, an element, any part of an element, or any combination of elements may be implemented as a "processing system" including one or more processors. When multiple processors are implemented, the multiple processors may perform functions individually or in combination. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic devices, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in the processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, or any combination thereof.

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

[0036] While aspects, implementations, and / or use cases are described herein by way of example, additional or different aspects, implementations, and / or use cases may arise in many different arrangements and scenarios. The aspects, implementations, and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, aspects, implementations, and / or use cases may arise via integrated chip implementations and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specific to a use case or application, the described examples may exhibit broad applicability. Aspects, implementations, and / or use cases can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the technologies described herein. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily involve multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or decomposed components, end-user equipment, etc., of various sizes, shapes, and configurations.

[0037] Communication systems, such as 5G NR systems, can be deployed in various ways with a variety of components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, radio access network (RAN) nodes, core network nodes, network elements or network equipment (such as base stations (BS)), or one or more units (or components) performing base station functions can be implemented in aggregated or decomposed architectures. For example, BSs (such as Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit / receive point (TRP), or cell, etc.) can be implemented as aggregated base stations (also known as standalone BS or monolithic BS) or decomposed base stations.

[0038] Aggregated base stations can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. Decentralized base stations can be configured to utilize a protocol stack that is physically or logically distributed across two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some respects, the CU may be implemented within a RAN node, and one or more DUs may co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0039] Base station operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be utilized in Integrated Access Backhaul (IAB) networks, Open Radio Access Networks (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)). Decomposition can include distributing functionality across two or more units in various physical locations, as well as virtually distributing the functionality of at least one unit, which enables flexibility in network design. The various units of a decomposed base station or decomposed RAN architecture can be configured to communicate wirelessly with at least one other unit.

[0040] Figure 1Figure 100 illustrates an example of a wireless communication system and access network. The illustrated wireless communication system includes a decomposed base station architecture. The decomposed base station architecture may include one or more CUs 110, which may communicate directly with the core network 120 via a backhaul link, or indirectly with the core network 120 via one or more decomposed base station units, such as a near real-time (near-RT) RAN Intelligent Controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a Service Management and Orchestration (SMO) framework 105, or both. CUs 110 may communicate with one or more DUs 130 via a corresponding midhaul link (such as an F1 interface). DUs 130 may communicate with one or more RUs 140 via a corresponding fronthaul link. RUs 140 may communicate with a corresponding UE 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0041] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO frame 105) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each unit in the unit, or an associated processor or controller providing instructions to the communication interfaces of these units, may be configured to communicate with one or more other units via transmission media. For example, these units may include wired interfaces configured to receive signals or transmit signals to one or more other units via wired transmission media. Additionally, these units may include wireless interfaces that may include receivers, transmitters, or transceivers (such as RF transceivers) configured to receive signals via wireless transmission media or transmit signals to one or more other units, or both.

[0042] In some aspects, the CU 110 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by the CU 110. The CU 110 can be configured to handle user plane functionality (i.e., Central Unit-User Plane (CU-UP)), control plane functionality (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 110 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 110 can be implemented to communicate with the DU 130 for network control and signaling, as needed.

[0043] DU 130 may correspond to a logic unit that includes one or more base station functions for controlling the operation of one or more RU 140s. In some aspects, DU 130 may at least partially host one or more of the Radio Link Control (RLC) layer, Media 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, etc.) according to functional splits (such as those defined by 3GPP). In some aspects, DU 130 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signaling with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

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

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

[0046] The non-RT RIC 115 can be configured to include logical functions enabling non-real-time control and optimization of RAN elements and resources, including artificial intelligence (AI) / machine learning (ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 125. The non-RT RIC 115 can be coupled to or communicate with the near-RT RIC 125, such as via an A1 interface. The near-RT RIC 125 can be configured to include logical functions enabling near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, through data collection and actions, connecting one or more CU 110s, one or more DU 130s, or both, and O-eNBs to the near-RT RIC 125.

[0047] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 125, the non-RT RIC 115 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 125 and may be received from non-network data sources or network functions at the SMO framework 105 or the non-RT RIC 115. In some examples, the non-RT RIC 115 or the near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 may monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions via the SMO framework 105 (such as reconfiguration via O1) or by creating RAN management policies (such as A1 policies).

[0048] At least one of CU 110, DU 130, and RU 140 may be referred to as base station 102. Therefore, base station 102 may include one or more of CU 110, DU 130, and RU 140 (each component is indicated by a dashed line to indicate that each component may or may not be included in base station 102). Base station 102 provides UE 104 with an access point to core network 120. Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Small cells include femtocells, picocells, and microcells. A network that includes both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include an evolved home node B (eNB) (HeNB), which can provide service to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) transmission (also known as reverse link) from UE 104 to RU 140 and / or downlink (DL) transmission (also known as forward link) transmission from RU 140 to UE 104. The communication link may utilize multiple-input multiple-output (MIMO) antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may use one or more carriers. For each direction, the total number of carriers used for transmission can be up to [number missing]. Yx MHz ( x For each carrier allocated in carrier aggregation (of component carriers), base station 102 / UE 104 can use up to [number] carriers. Y A spectrum with a bandwidth of MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.). Carriers may be adjacent to each other or may not be adjacent to each other. Carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell) and the secondary component carrier may be referred to as the secondary cell (SCell).

[0049] Some UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 can use DL / UL wireless wide area network (WWAN) spectrum. D2D communication link 158 can use one or more sidelink channels, such as Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). D2D communication can be performed through various wireless D2D communication systems, such as Bluetooth. ™ (Bluetooth is a trademark of the Bluetooth Special Interest Group (SIG), and is based on the IEEE 802.11 standard for Wi-Fi.) ™ (Wi-Fi is a trademark of the Wi-Fi Alliance), LTE, or NR.

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

[0051] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz to 7.125GHz) and FR2 (24.25GHz to 52.6GHz). Although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is often (interchangeably) referred to as the "sub-6GHz" band. Similar naming issues sometimes occur with FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although this is distinct from the Extremely High Frequency (EHF) band (30GHz to 300GHz) designated as "millimeter wave" by the International Telecommunication Union (ITU).

[0052] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR studies have designated the operating bands for these mid-band frequencies as the frequency range designation FR3 (7.125 GHz to 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to mid-band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been designated as the frequency range designations FR2-2 (52.6 GHz to 71 GHz), FR4 (71 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher bands falls within the EHF band.

[0053] In view of the above, unless otherwise specified, the term "below 6 GHz" as used herein can broadly refer to frequencies less than 6 GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise specified, the term "millimeter wave" as used herein can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, FR4, FR2-2 and / or FR5, or within the EHF band.

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

[0055] Base station 102 may include and / or be referred to as gNB, Node B, eNB, access point, base transceiver, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), TRP, network node, network entity, network equipment, or some other suitable terminology. Base station 102 may be implemented as an integrated access and backhaul (IAB) node, relay node, sidelink node, aggregated (monolithic) base station with baseband units (BBU) (including CU and DU) and RU, or may be implemented as a decomposed base station including one or more of CU, DU, and / or RU. A collection of base stations that may include decomposed base stations and / or aggregated base stations may be referred to as Next Generation (NG) RAN (NG-RAN).

[0056] The core network 120 may include Access and Mobility Management Function (AMF) 161, Session Management Function (SMF) 162, User Plane Function (UPF) 163, Unified Data Management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is the control node that handles signaling between UE 104 and the core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports authentication and key agreement (AKA) credential generation, user identity processing, access authorization, and subscription management. One or more location servers 168 are exemplified as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. However, generally, one or more location servers 168 may include one or more location / positioning servers, which may include one or more of GMLC 165, LMF 166, Position Determination Entity (PDE), Serving Mobile Location Center (SMLC), Mobile Location Center (MPC), etc. GMLC 165 and LMF 166 support UE location services. GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE location information. LMF 166 receives measurement and auxiliary information from NG-RAN and UE 104 via AMF 161 to calculate the location of UE 104. NG-RAN may use one or more positioning methods to determine the location of UE 104. Positioning UE 104 may involve signal measurement, location estimation, and optional speed calculation based on these measurements. Signal measurement may be performed by UE 104 and / or base station 102 serving UE 104. The measured signals may be based on one or more of the following: Satellite Positioning System (SPS) 170 (e.g., one or more of Global Navigation Satellite System (GNSS), Global Positioning System (GPS), Non-Terrestrial Network (NTN) or other satellite positioning / location systems), LTE signals, Wireless Local Area Network (WLAN) signals, Bluetooth signals, Terrestrial Beacon System (TBS), sensor-based information (e.g., barometric pressure sensor, motion sensor), NR Enhanced Cell ID (NR E-CID) method, NR signals (e.g., multiple round-trip time (multiple RTT), DL departure angle (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning) and / or other systems / signals / sensors.

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

[0058] Refer again Figure 1In some aspects, UE 104 may have a QOE-based selection component 198 (“Component 198”), which is configured to obtain a set of cell metrics associated with the UE, wherein the set of cell metrics includes RSRP and at least one of potential delay, tier number, or service characteristics. Component 198 may also be configured to initiate or maintain a connection with the cell associated with the UE based on a threshold condition met by a combined metric, wherein the combined metric is based on the set of cell metrics. Component 198 may be configured to receive a QOE request associated with the set of cell metrics from a network node or network entity before obtaining the set of cell metrics. Component 198 may be configured to send an indication to the cell based on a threshold condition met by a combined metric, for the network node, before initiating or maintaining a connection with the cell. In some aspects, base station 102 may have a QOE-based selection component 199 (“Component 199”), which is configured to obtain a set of cell metrics associated with the UE, wherein the set of cell metrics includes RSRP and at least one of potential delay, tier number, or service characteristics. Component 199 can also be configured to initiate or maintain a connection between the UE and a cell associated with the UE based on a threshold condition met by a combined metric, wherein the combined metric is based on a set of cell metrics. Component 199 can be configured to receive a QOE request associated with the cell metric set from a network entity before obtaining the cell metric set. Component 199 can be configured to send an indication to the UE and, before initiating or maintaining a connection with the cell, based on a threshold condition met by the combined metric. Therefore, the aspects of QOE-based network / cell selection for the UE described herein provide better cell selection for TDD and FDD utilization by considering QOE metrics associated with both the user and UE sides, as well as considerations for the provider's service / application type, because OEMs or service / application providers may be very concerned with considering the user experience in their radio device solutions to optimize for different scenarios and improve user experience.

[0059] Figure 2A Figure 200 illustrates an example of the first subframe within a 5G NR frame structure. Figure 2B Figure 230 illustrates an example of a DL channel within a 5G NR subframe. Figure 2C Figure 250 is an example of a second subframe within a 5G NR frame structure. Figure 2D Figure 280 illustrates an example of a UL channel within a 5G NR subframe. The 5G NR frame structure can be Frequency Division Duplex (FDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to either DL or UL) or Time Division Duplex (TDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to both DL and UL). Figure 2A , Figure 2C In the provided example, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible and can be used between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28 respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are both DL and UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The UE is configured using the slot format via the received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0060] Figures 2A to 2D The frame structure is illustrated, and aspects of this disclosure are applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 equal-sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include micro-time slots, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each time slot may include 14 symbols, and for extended CP, each time slot may include 12 symbols. Symbols on the DL may be CP Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the UL may be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and a parameter set. The parameter set defines the subcarrier spacing (SCS) (see Table 1). Symbol length / duration can be scaled using 1 / SCS.

[0061] Table 1: Parameter Set, SCS, and CP For a normal CP (14 symbols / slot), different parameter sets µ 0 through 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For an extended CP, parameter set 2 allows 4 slots per subframe. Therefore, for a normal CP and parameter set µ, there are 14 symbols / slot and 2... µ One time slot / subframe. Subcarrier spacing can be equal to ,in The parameter sets are 0 to 4. Therefore, the subcarrier spacing is 15 kHz for parameter set µ=0 and 240 kHz for parameter set µ=4. The symbol length / duration is negatively correlated with the subcarrier spacing. Figures 2A to 2D Examples of a normal frequency division multiplexing (CP) with 14 symbols per time slot and a parameter set of µ=2 with 4 time slots per subframe are provided. The time slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within the frame set, there may be one or more distinct bandwidth portions (BWPs) of frequency division multiplexing (see [link to relevant documentation]). Figure 2B Each BWP can have a specific set of parameters and CP (normal or extended).

[0062] A resource grid can be used to represent the frame structure. Each time slot consists of a resource block (RB) extending for 12 consecutive subcarriers (also known as a physical RB (PRB)). The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

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

[0064] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE comprising six RE Groups (REGs), each REG comprising 12 consecutive REs in the OFDM symbol of the RB. A PDCCH within a BWP can be referred to as a Control Resource Set (CORESET). The UE is configured to monitor PDCCH candidates in the PDCCH search space (e.g., the common search space, the UE-specific search space) during PDCCH monitoring timing on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. The Primary Synchronization Signal (PSS) may be located within symbol 2 of a specific subframe of the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and physical layer identification. The Secondary Synchronization Signal (SSS) may be located within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the Physical Layer Cell Identifier Group Number and radio frame timing. Based on the Physical Layer Identifier and the Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The Physical Broadcast Channel (PBCH), carrying the Master Information Block (MIB), can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block (also known as an SS block (SSB)). The MIB provides the System Frame Number (SFN) and the number of Restricted Frames (RBs) in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as System Information Blocks (SIBs)), and paging messages.

[0065] like Figure 2C As illustrated, some REs in the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the first or first two symbols of the PUSCH. Depending on whether a short or long PUCCH is transmitted and depending on the specific PUCCH format used, the PUCCH DM-RS can be transmitted in different configurations. The UE can transmit a Sounding Reference Signal (SRS). The SRS can be transmitted in the last symbol of a subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the comb teeth. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0066] Figure 2DExamples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), pre-decoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUCCH carries data and may additionally be used to carry buffer status reports (BSR), power clearance reports (PHR), and / or UCIs.

[0067] Figure 3 This is a block diagram illustrating communication between base station 310 and UE 350 in the access network. In the DL, Internet Protocol (IP) packets can be provided to controller / processor 375. Controller / processor 375 implements Layer 3 and Layer 2 functionality. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the delivery of upper-layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority ordering.

[0068] Transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) decoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. TX processor 316 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to OFDM subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and then combined using inverse fast Fourier transform (IFFT) to produce a physical channel carrying a stream of time-domain OFDM symbols. The OFDM stream undergoes spatial pre-decoding to generate multiple spatial streams. Channel estimation from channel estimator 374 can be used to determine the decoding and modulation scheme, as well as for spatial processing. The channel estimation can be derived from a reference signal transmitted by UE 350 and / or channel condition feedback. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx can utilize the corresponding spatial stream to modulate a radio frequency (RF) carrier for transmission.

[0069] At UE 350, each receiver 354Rx receives signals via its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides that information to the receive (RX) processor 356. The TX processor 368 and RX processor 356 implement Layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for UE 350. If multiple spatial streams are destined for UE 350, the RX processor 356 can combine them into a single OFDM symbol stream. The RX processor 356 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal consists of a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, along with the reference signal, are recovered and demodulated by determining the most probable signal constellation points transmitted by base station 310. These soft decisions can be based on a channel estimate calculated by channel estimator 358. The soft decision is then decoded and deinterleaved to recover the data and control signals originally transmitted by base station 310 on the physical channel. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functionality.

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

[0071] Similar to the functionality described in conjunction with DL transmission performed by base station 310, controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connectivity, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with upper-layer PDU delivery, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority ordering.

[0072] The TX processor 368 can use the channel estimate derived from the reference signal or feedback transmitted by the channel estimator 358 from the base station 310 to select an appropriate decoding and modulation scheme and facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via individual transmitters 354Tx. Each transmitter 354Tx can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0073] UL transmission is processed at base station 310 in a manner similar to that described in conjunction with the receiver function at UE 350. Each receiver 318Rx receives signals via its corresponding antenna 320. Each receiver 318Rx recovers the information modulated onto the RF carrier and provides that information to RX processor 370.

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

[0075] At least one of the TX processor 368, RX processor 356, and controller / processor 359 can be configured to perform coupling. Figure 1 Various aspects of component 198. At least one of the TX processor 316, RX processor 370, and controller / processor 375 can be configured to perform combined Figure 1 The components of 199 in all aspects.

[0076] Wireless communication systems can support the use of RSRP as an indicator of signal quality. Based on signal quality, the network can determine when to hand over a UE from one cell to another, allowing the UE to communicate with the new serving cell or base station (e.g., a gNB or other types of base stations) using higher quality signaling. However, basing UE mobility on signal quality without other considerations may lead to scenarios where this approach fails to meet the user's expected experience. Furthermore, in geographical areas where TDD and FDD cells overlap, signal quality mobility does not consider how TDD and FDD cells can be applied to improve the user's QOE. As an example, gaming and voice calls in mobility can be user-sensitive applications, where bursts of low-latency and high-quality small random-size packet transmissions are beneficial in gaming, while regular periodicity with very high-quality UM packets may be important in voice calls. Both applications can benefit from different types of serving cells. As another example, downloading data in mobility can benefit from the highest data rate that can be completed in a short time to save power, while long travel times in mobility can benefit from keeping the UE in a very low-power mode while waiting for a charging opportunity.

[0077] Figure 4 Figure 400 illustrates an example of cell selection based on signal quality. Figure 400 shows cell selection that can be performed by network nodes (e.g., base stations, gNBs, etc.) and / or by the UE based on RSRP or similar / equivalent measurements.

[0078] Database (DB) 402 may include one or more entries for cells that can serve a UE. Cells in DB 402 may be populated / stored therein based on historical measurements, etc. Cells selected from DB 402 can be used to perform signal quality calculation 404. For example, signal quality calculation 404 may represent the signal quality between the selected cell and the UE, and may correspond to RSRP.

[0079] Based on signal quality calculation 404, evaluation 406 can be performed. Signal quality calculation 404 can be evaluated against evaluation 406 to determine whether signal quality calculation 404 meets signal quality threshold conditions or standards (criteria). As an example, absolute levels of RSRP, relative levels of RSRP, etc., can be considered against evaluation 406. Then, it can be determined whether to initiate event triggering 408 based on the evaluation. For example, if the RSRP of the selected cell's signal quality calculation 404 is shown in evaluation 406 to be greater than that of other cells in DB 402, or is shown to meet / exceed the configured threshold for RSRP, event triggering 408 can be initiated, and a handover report 410 indicating a move to the selected cell can be sent.

[0080] Conversely, if assessment 406 indicates that the current serving cell has a better RSRP, the selected cell does not meet / exceeds a threshold, or the signal quality of the selected cell is lower than that of other cells, then event trigger 408 can be omitted, and a different cell can be selected from the processable DB 402. In this way, cell selection for mobility can be performed based on signal quality / RSRP without other considerations.

[0081] This paper addresses aspects of QOE-based network / cell selection for UEs and provides superior cell selection, for example, for TDD and FDD utilization, by considering QOE metrics associated with both user and UE-side considerations, as well as service / application types for the provider. Therefore, aspects of this paper allow for the use of various parameters, such as but not limited to signal-to-noise ratio (SNR), target cell bandwidth, potential latency, strata number, etc., during handover, taking into account QOE considerations for network / cell selection (e.g., TDD and / or FDD cells).

[0082] For example, in gaming mode, lower latency may be more beneficial for UE and QOE than throughput. In real-world implementations of wireless communication networks, different bandwidth coverages may exist for various configurations, such as FDD and TDD. TDD has a wide bandwidth but a higher carrier frequency, which makes TDD coverage less than FDD coverage in gaming scenarios. For mobile gaming, various factors allow for the selection of FDD cells to serve the UE for a better user experience than TDD, at least because of fewer cell handovers and shorter round-trip times (RTTs), where total bandwidth may not be an issue. As another example, frequency cell handovers can directly impact voice quality during voice calls. Furthermore, to guarantee call quality, the network can schedule very low modulation and decoding schemes (MCS), which reduces the block error rate (BLER). Therefore, common mobility parameters may not be the optimal choice for voice calls.

[0083] In another example, for high-volume downloads in mobility scenarios, users might expect to download data as quickly as possible while signal quality is good. In this case, if a TDD cell is available as a candidate for handover, switching to such a cell to achieve high throughput and complete the download in a shorter time might be far better, as this is more power-efficient in terms of mobility than longer downloads, since edge cell downloads may be inefficient in terms of both power and spectrum. Furthermore, in low-power situations (such as long travel times, locations with few / no charging options, etc.), if the UE battery is running low or experiencing reduced power, the user might want to keep the UE powered / active until the next charging opportunity. Here, signal quality might not be an issue, and paging reception, measurements, cell handover, etc., might need to be minimized to save power, and common mobility control using RSRP cannot cover such scenarios without other considerations.

[0084] The aspects of network / cell selection for QOE-based applications described in this paper enable UEs to perform network / cell selection to improve QOE. As an example, FDD and TDD networks / cells can overlap, for example, in urban areas. FDD typically offers better coverage and lower latency, while TDD offers greater bandwidth. For low-latency and small-packet services such as voice calls and gaming, selecting FDD cells to improve QOE may be preferred. For high-throughput services such as video or downloads, selecting TDD cells to improve QOE may be preferred. Generally, the aspects allow for the selection of FDD cells in edge cell scenarios and TDD cells in near-cell scenarios. The aspects also allow for the pre-transmission of service / application type indicators to the modem before the service / application begins. Therefore, new metrics for cell selection can be defined in the aspects from different dimensions, such as combined metrics, including but not limited to: Default Signal Quality Responsibility (RSRP), Potential Capacity (SNR) (such as the bandwidth of the target cell), Potential Latency, Layer Number, and Service / Application Characteristics. For default quality, if the UE has no stored history, RSRP bias can be added to different absolute radio frequency channel numbers (ARFCNs), and data structures such as DBs, tables, and linked tables can be maintained to store the bias for each ARFCN. For potential capacity, channel capacity can be calculated when default SNR and bandwidth information are available. For potential latency, this metric can be calculated based on the RTT of the frame configuration or latency measurement history. RSRP bias can be defined according to latency levels. As an example, latency level 1 can be a critical latency <20ms; latency level 2 can be a voice latency <40ms; latency level 3 can be a game latency <100ms; and so on. For service characteristics that may include high throughput, low latency, low power, etc., gating triggers for the biases defined above can be used in the implementation. G(For example, the value "1" or "-1"). Therefore, the newly defined combinatorial measure can be... Therefore, the aspects of QOE-based network / cell selection for UEs described in this paper provide better cell selection, for example, for TDD and FDD utilization, by considering QOE metrics associated with user and UE-side considerations as well as service / application types for the provider.

[0085] Figure 5 Call flowchart 500 illustrates wireless communication in various aspects. Call flowchart 500 illustrates QOE-based network / cell selection at a wireless device (e.g., UE 502) communicating with cells (such as network nodes, e.g., base station 504, such as gNB or other types of base stations, as shown) in various aspects. The aspects described for base station 504 can be performed by the base station in an aggregated manner and / or by one or more components of the base station in a decomposed manner. Additionally or alternatively, these aspects can be performed autonomously by UE 502 in addition to and / or as a substitute for the operation of base station 504. In each aspect, base station 504 can be configured to provide at least one cell and can be a serving cell, a candidate / target cell, and / or a neighboring cell.

[0086] In the illustrated aspects, UE 502 may be configured to receive a QOE request 506 associated with the cell metric set from a network node (e.g., a base station 504 configured to transmit / provide it) before obtaining the cell metric set. In each aspect, the QOE request 506 may include one or more features of a service / application to be utilized by UE 502, and may also or alternatively include service triggers (e.g., triggers from a service provider / OEM associated with the service / application). Service triggers may include, but are not limited to, a set of service features as indicated herein, and / or another indication of the cell, cell type, absolute radio frequency channel number (ARFCN), etc., to be used by UE 502 for the service / application. In each aspect, the service trigger may be provided by a network entity (e.g., an OEM server, etc.) and may be provided to UE 502 via base station 504 or another communication path. That is, in each aspect, the QOE request 506 may indicate to UE 502 various features desired by the service / application to improve or maximize QOE, which allows UE 502 to select the cell most suitable for the service / application.

[0087] UE 502 can be configured to obtain (at 508) a set of cell metrics associated with the cell to which UE 502 is located. In various aspects, the set of cell metrics may include RSRP and potential latency, tier number, and / or service characteristics. In various aspects, service characteristics may be one or more of low latency, high throughput, and / or low power. The tier number may be one or more tiers of the wireless communication system architecture (e.g., LTE, 5G NR, 5G+, 6G, etc.) utilized by the service / application, and potential latency may be a value of some type of delay experienced by UE 502 (e.g., round-trip time (RTT) and end-to-end (E2E) time, UE latency, etc.). Cell metrics may be obtained (at 508) from QOE request 506, through measurements at UE 502 or elsewhere (e.g., at least one measurement associated with the cell), and / or from base station 504, another base station, network entity, etc.

[0088] UE 502 can be configured to send / provide indication 510 of a cell to base station 504. That is, in various aspects, UE 502 can be configured to send / provide indication 510 of a cell to a network node (e.g., base station 504) before initiating or maintaining a connection with the cell. In various aspects, the combined metric can be based on a set of cell metrics, and the indication 510 of the cell can be based on the combined metric satisfying a threshold condition.

[0089] UE 502 can be configured to initiate or maintain (at 512) a connection with a cell associated with UE 502 based on a threshold condition met by a combined metric. As noted above, the combined metric can be based on a set of cell metrics. In various respects, the combined metric can be determined / computed based on a weighted representation of the set of cell metrics, and this weighting can be determined based on service characteristics (e.g., type, condition, etc.), QOE request 506, etc. That is, the combined metric can be based on a set of cell metrics using a combination of at least one corresponding weighted representation of RSRP and at least one of potential delay, tier number, or service characteristics. In various respects, the corresponding weighted representation can be based on a weighted value for the UE's idle mode and / or a weighted value for the UE's connected mode.

[0090] In various respects, UE 502 can be configured to select a cell from a data structure maintained by UE 502 before initiating or maintaining (at 512) a connection. In various respects, the cell may be associated in the data structure with at least one of the following: ARFCN, TDD indication for the cell, FDD indication for the cell, measurement associated with the cell, etc. UE 502 can also be configured to reorder the cells and at least one additional cell in the data structure maintained by UE 502 based on combined metrics and QOE request 506. UE 502 can be configured to select a cell from the data structure maintained by UE 502 after reordering the cells and at least one additional cell, as described in further detail below.

[0091] Figure 5 This illustrates that UE 502 can maintain a connection with a cell (e.g., with base station 504) based on a combined metric. As an example, the UE can send or receive communication with the cell 514. In some aspects, based on the combined metric, UE 502 can initiate a connection with a different cell (e.g., a second cell 505), as shown at 516. UE 502 can send or receive communication with the second cell 505 518 after the connection is established.

[0092] Figure 6 Figure 600 illustrates examples of user QOE-based cell selection in various aspects. Figure 600 shows the ranking of cells used for measurement and acquisition in various aspects when service / application is waiting, and this ranking can be performed by the UE and / or network nodes (e.g., base stations, gNBs, etc.) in various configurations envisioned herein.

[0093] For example, DB 610 can be maintained by the UE and / or network nodes. Although DB is shown as a data structure for illustrative purposes and by way of example, other data structures (e.g., tables, linked tables, etc.) are also conceivable in various aspects. DB 610 can be used to sort according to service / application type. DB 610 can store one or more ARFCNs, TDD indications, FDD indications, measurements, etc., associated with different cells to which UE mobility / maintenance can be performed (e.g., different types of serving cells (PCell, SPCell, etc.), neighboring cells (SCell), etc.).

[0094] As shown in the figure, a QOE request 602 can be received. The QOE request 602 can indicate the service features and / or service triggers of a service / application to be utilized by the UE. The QOE request 602 can be received by the UE from a network node and / or network entity associated with the service / application to be utilized by the UE (e.g., as a service trigger from an OEM server in the core network or otherwise located). In various respects, request 602 can be received by a network node.

[0095] Based on the QOE request, metric calculation 604 can be performed on the selected cell maintained by DB 610. In various respects, the metric calculation can result in a newly defined combined metric, which can be equal to As noted herein, it is based on a combination of a set of cell metrics (potential latency, number of strata, service characteristics, etc.) and RSRP values. In some aspects, at least one corresponding weighted representation of potential latency, number of strata, service characteristics, etc., can be used to obtain a combined metric in metric calculation 604. The corresponding weighted representation may be associated with a service characteristic and / or service trigger indicated by QOE request 602, and the service characteristic may be low latency, high throughput, low power, etc. In various aspects, metric calculation 604 may include obtaining (e.g., in Figure 8 (508 in the text) is one or more parts of the cell metric set associated with the cell of the UE.

[0096] Based on metric calculation 604, DB 610 can be reordered 606, for example, by the UE / network node. In one example, reordering can sort the entries in DB 610 such that cells corresponding to the combined metric from metric calculation 604 are prioritized for selection / maintenance based on the combined metric. Reordering 606 can be performed using indexes, tags, etc., of DB 610. In various aspects, selected cells can be sorted / prioritized based on metric calculation 604. It can be determined 608 whether all cells have been calculated for metric calculation 604. If not all cells have been calculated, another cell from DB 610 undergoes calculation 604; if all cells have been calculated, evaluation 612 is used to evaluate, for example, the cells selected from DB 610 based on reordering 606 against threshold criteria. Evaluation 612 can determine whether the combined metric meets the threshold conditions that indicate the selected cells provide better / optimal QOE for the application / service. In various aspects, absolute levels of combined metrics, relative levels of combined metrics, etc., can be used.

[0097] If the selected cell passes evaluation 612, an event trigger 614 is determined, and in various respects, a report 616 can be provided from the UE to the network node, and vice versa. Report 616 can be an indication of the selected cell used to initiate / maintain a connection for the UE. If the serving cell is the selected cell associated with event trigger 614, a connection to the serving cell can be maintained for the UE; if a different cell is associated with event trigger 614, a connection to that different cell can be initiated for the UE. That is, based on the combined metric of the cell satisfying one or more threshold criteria for the service / application type, the UE can move to a cell different from its current serving cell, or the UE can maintain its connection to its current serving cell. If the selected cell fails evaluation 612, the selected cell is not associated with event trigger 614, and a cell different from DB 610 can be selected, which may undergo reordering 606, etc.

[0098] In some respects, when a QOE request returns a 602 indicating service triggering, and / or when no QOE considerations are available, the default consideration set can be used to gate the triggering. G Set to zero, and the DB 610 can use RSRP to fall back to a second set of signal quality considerations (which may be referred to as the default signal quality considerations) for cell selection. In various respects, the default set of signal quality considerations can be configured by the OEM (e.g., service / application provider).

[0099] As noted above, the weighted representation of the metrics in the cell metric set can be used for metric calculation 604 based on weighted values ​​to obtain the combined metric. In each respect, the corresponding weighted representation can be based on the weighted value for the UE's idle mode and / or based on the weighted value for the UE's connected mode.

[0100] In idle mode, the weighting value may include a positive weighting value associated with at least one of the RSRP or number of tiers that meets the throughput threshold, or a negative weighting value associated with at least one of the RSRP or number of tiers that fails to meet the throughput threshold. The weighting value may include a positive weighting value associated with the potential latency that meets the latency threshold, or a negative weighting value associated with the potential latency that fails to meet the latency threshold. When the service characteristic is at least one of low latency, high throughput, or low power, the weighting value may include a positive weighting value associated with the service characteristic that meets the characteristic threshold, or a negative weighting value associated with the service characteristic that fails to meet the characteristic threshold.

[0101] For example, in idle mode, public mobility metrics are added. Furthermore, RSRP can be used because cell coverage can be primarily governed by UL signaling. Therefore, in all respects, a positive RSRP bias can be added on TDD when RSRP is good, and conversely, a negative bias can be added when RSRP is below a threshold. For Idle-to-Connection (I2C) candidates, I2C bias can be maintained as defined according to different QOE characteristics / expectations. For high throughput, the bias metric can be defined based on capacity. For example, The weights can be defined as enabling / disabling biases based on the QOE level: For low latency, the deviation can be defined based on RTT: ,in For low power, the metric deviation can be defined based on RSRP and SNR: ,in Therefore, the final combined metric used for cell selection can be: +Normal metric. The UE can be configured to select a cell based on a final metric before initiating its connection to the cell, and the metric setting ensures that the UE directly selects its current serving cell in low-latency mode.

[0102] In connected mode, the weighting value may include a positive weighting function associated with at least one of the RSRP or number of tiers that meets the throughput threshold, or a negative weighting function associated with at least one of the RSRP or number of tiers that fails to meet the throughput threshold. The weighting value may include a negative weighting function associated with the potential latency that meets the latency threshold, or a positive weighting function associated with the potential latency that fails to meet the latency threshold. When the service characteristic is at least one of low latency, high throughput, or low power, the weighting value may include a positive weighting function associated with the service characteristic that meets the characteristic threshold, or a negative weighting function associated with the service characteristic that fails to meet the characteristic threshold.

[0103] For example, in connected mode, public mobility metrics are added. The UE can be configured to sort measurement frequencies according to the order of combined metrics defined in the acquisition. Multiple deviation values, "unmeasured time," can be added to the measurement sorting. For example, in connected mode, the measurement period can be different for different frequencies. If the sorted frequencies are used for the measurement order, cells with different measurement periods can therefore also have different priorities. That is, a longer period can correspond to a lower priority, and therefore, a bias can be added to the results. Here, the low latency bias can be negative, where... , And T is the actual latency characteristic (e.g., in milliseconds, such as for fine-tuning). In connected mode, compared to idle mode, the UE can be configured to directly initiate a service / application, and then, based on the service QOE characteristics, the UE can be configured to trigger a mobility event. The weights of the deviations can also differ from those in idle mode. They can be functions of the QOE characteristics / considerations: ,in This is the previously defined level, and the weight values ​​are to incorporate non-linear gains for qualitative changes or conflict considerations. For example, if the UE is in FDD and the service / application has significant capacity considerations, a fast cell handover can be triggered quickly. However, for low latency considerations, the UE can be configured to hand over to a cell when the latency of the current cell cannot actually meet such considerations. That is, when Therefore, in this case, the final combined metric used for cell selection can be... +Normal measurement.

[0104] Figure 7 Figure 700 illustrates examples of user QOE-based cell selection in various aspects. Figure 700 shows how policies 710 for UE behavior such as cell handover, power saving, network kick-out, etc., can be based on pattern detection 702, condition detection 704, and other metrics 706, in addition to QOE requests 708 and associated cell metrics.

[0105] Pattern detection 702 can be associated with access point (AP) sensors, modem RSRP, history (e.g., in the database), and can be based on channel conditions, specific environments, different UE operating modes, etc. Condition detection 704 can be based on data (e.g., data TX / RX delay, etc.), 3GPP access layer (AS) conditions (e.g., access failure, ping-pong cell handover, etc.), PHY conditions (e.g., low SNR, low rank, etc.), etc. Other metrics 706 can be associated with UE capabilities (e.g., UE capabilities provided to the network), or can be network-related (e.g., RSRP / Reference Signal Received Quality (RSRQ) / Measurement Report (MR) thresholds (e.g., MR provided to the network by the UE), etc.).

[0106] As described herein, a QOE request 708 may be associated with a service trigger (e.g., from an OEM) and / or with a service type / feature (e.g., voice, gaming, low latency mode (LLM), throughput) for a service and / or application to be utilized by the UE. For example, a QOE request 708 may indicate one or more performance characteristics, such as, but not limited to, time or service latency characteristics / limits (e.g., 40ms, 100ms, 200ms, 1 second, etc.), service characteristics (such as maximum throughput or throughput range), power savings, etc.

[0107] In addition to QOE request 708 and its associated cell metrics, policy 710 may be determined based on a combination of pattern detection 702, condition detection 704 and / or other metrics 706. For example, policy 710 may include cell handover (e.g., mobility control, etc.), power saving methods, network problem migration (e.g., probe, overwrite, etc.), and so on.

[0108] Figure 8 This is a diagram 800 illustrating examples of user QOE-based cell selection in various aspects. Diagram 800 can be... Figure 5 The call flow diagram 500 illustrates one aspect of this. Figure 800 shows the communication between UE 802, base station 804, and network entity 814. Network entity 814 may be a server or other type of device and may be located in the core network associated with UE 802 / base station 804 or otherwise.

[0109] In one configuration, Figure 800 illustrates an aspect of the functionality performed by reference network entity 814 and base station 804 for QOE-based network / cell selection for UE 802. As noted above, one or more aspects of UE-based user QOE-based cell selection can be performed by network nodes. Network entity 814 can be configured to provide a QOE request 806 associated with a set of cell metrics associated with cells of UE 802, and base station 804 can be configured to receive this QOE request. In some aspects, for example, as Figure 5 As shown, base station 804 can then provide QOE request 806 to UE 802.

[0110] In various aspects, QOE request 806 may include one or more features of a service / application to be utilized by UE 802, and may also or alternatively include service triggers (e.g., triggers from a service provider / OEM associated with the service / application). Service triggers may include, but are not limited to, a set of service features as indicated herein, and / or another indication of the cell, cell type, absolute radio frequency channel number (ARFCN), etc., to be used by UE 802 for the service / application. In various aspects, service triggers may be provided by network entities such as network entity 814 (e.g., OEM server, etc.). That is, in various aspects, QOE request 806 may indicate to base station 804 various features desired by the service / application to improve or maximize QOE, which allows base station 804 to select the cell most suitable for the service / application for UE 802.

[0111] In all respects, as shown in Figure 800, base station 804 can be configured to obtain (at 808) using QOE request 806 (e.g., as shown in Figure 800). Figure 5The cell metric set associated with UE 802 (similarly described at 508) refers to the cell associated with UE 802. In various aspects, the cell metric set may include RSRP and potential latency, tier number, and / or service characteristics. In various aspects, service characteristics may be one or more of low latency, high throughput, and / or low power. The tier number may be one or more tiers of the wireless communication system architecture (e.g., LTE, 5G NR, 5G+, 6G, etc.) utilized by the service / application, and potential latency may be a value of some type of latency experienced by UE 802 (e.g., round-trip time (RTT) and end-to-end (E2E) time, UE latency, etc.). Cell metrics may be obtained from QOE request 806, through measurements at UE 802 and / or elsewhere (e.g., at least one measurement associated with the cell), and / or from base station 804, another base station, network entity 814, etc. Therefore, base station 804 can be configured so that UE 802 selects cells that meet the threshold conditions of QOE associated with the service / application, as referenced above. Figure 5 , Figure 6 Described similarly.

[0112] Base station 804 can be configured to send / provide indication 810 of a cell to UE 802. That is, in various respects, base station 804 can be configured to send / provide indication 810 of a cell to UE 802 before initiating or maintaining a connection with the cell. In various respects, the combined metric can be based on a set of cell metrics, and the indication 810 of the cell can be based on the combined metric satisfying a threshold condition.

[0113] Therefore, base station 804 and / or UE 802 can be configured to initiate or maintain (at 812) a connection with the cell associated with UE 802 based on a combined metric satisfying a threshold condition, as described herein. Figure 5 The same applies to UE 502. In various aspects, base station 804, configured to send / provide indication 810 to UE 802 regarding a cell, can be a portion that initiates or maintains (at 812) a connection with a cell associated with UE 802 based on a combined metric satisfying a threshold condition. As noted above, the combined metric may be based on a set of cell metrics. In various aspects, the combined metric may be determined / calculated based on a weighted representation of the set of cell metrics, and this weighting may be determined based on service characteristics (e.g., type, conditions, etc.), QOE request 806, etc. That is, the combined metric may be based on a set of cell metrics using a combination of at least one corresponding weighted representation of RSRP and at least one of potential delay, tier number, or service characteristics. In various aspects, the corresponding weighted representation may be based on a weighted value for the UE's idle mode and / or a weighted value for the UE's connected mode.

[0114] In another configuration, Figure 800 is an aspect of network entity 814 providing QOE request 806' to UE 802. QOE request 806' may be the same as or similar to the QOE request 806 described herein provided to UE 802 by base station 804. In this configuration, the network entity may provide QOE request 806' to UE 802 using communication outside of base station 804. As an example, in addition to base station 804 providing QOE request 806 to UE 802, or as an alternative (e.g., for...), other configurations may also be provided. Figure 5 (As illustrated in QOE request 506 in the example), this can be performed by network entity 814.

[0115] Figure 9 This is a flowchart 900 of a method for wireless communication in various aspects. The method can be performed by a UE (e.g., UE 104, 502, 802; device 1304). In some aspects, the method may include combining... Figure 5 The communication process described in the document covers various aspects and / or Figure 6 , Figure 7 , Figure 8 The methods described herein can be used for QOE-based network / cell selection and provide improvements in UE cell mobility / maintenance by considering QOE metrics associated with both the user and UE sides, as well as the provider's service / application type. These improvements enable the UE to perform optimal cell selection, for example, for TDD and FDD utilization, as OEMs or service / application providers may be highly concerned with considering the user experience in their radio device solutions to optimize for different scenarios and improve the user experience.

[0116] At position 902, the UE obtains a set of cell metrics associated with the cell, wherein the set of cell metrics includes at least one of potential latency, tier number, or service characteristics. As an example, this acquisition can be achieved by... Figure 13 It is performed by one or more of the components 198, transceiver 1322 and / or antenna 1380. Figure 5 An example is shown where UE 502 obtains such a set of cell metrics from a network node (e.g., base station 504).

[0117] UE 502 can be configured to receive a QOE request 506 associated with the cell metric set from a network node (e.g., a base station 504 configured to transmit / provide) before obtaining the cell metric set. Figure 6 602 in the middle; Figure 7 708 in the middle; Figure 8 In the context of 806 and 806'). In various aspects, QOE requests 506 (e.g., Figure 6 602 in the middle; Figure 7 708 in the middle; Figure 8The 806, 806' in the document may include one or more features of a service / application to be utilized by UE 502, and may also or alternatively include a service trigger (e.g., a trigger from a service provider / OEM associated with the service / application). The service trigger may include, but is not limited to, a set of service features as indicated herein, and / or another indication of the cell, cell type, absolute radio frequency channel number (ARFCN), etc., to be used by UE 502 for the service / application. In various aspects, the service trigger may be provided by a network entity (e.g., an OEM server, etc.) and may be provided to UE 502 via base station 504 or another communication path. That is, in various aspects, QOE request 506 (e.g., Figure 6 602 in the middle; Figure 7 708 in the middle; Figure 8 The 806 and 806' in the UE 502 can indicate various characteristics desired by the service / application in order to improve or maximize QOE, which allows the UE 502 to select the cell that is best suited for the service / application.

[0118] UE 502 can be configured to obtain (at 508) (e.g., Figure 6 (604 in the table) is the set of cell metrics associated with the cell of UE 502. In various aspects, the set of cell metrics may include RSRP and potential latency, tier number, and / or service characteristics. In various aspects, service characteristics may be one or more of low latency, high throughput, and / or low power. The tier number may be one or more tiers of the wireless communication system architecture (e.g., LTE, 5G NR, 5G+, 6G, etc.) utilized by the service / application, and potential latency may be a value of some type of delay experienced by UE 502 (e.g., round-trip time (RTT) and end-to-end (E2E) time, UE latency, etc.). Cell metrics may (at 508) (e.g., Figure 6 (604 in the middle) from QOE request 506 (e.g., Figure 6 602 in the middle; Figure 7 708 in the middle; Figure 8 The measurements are obtained from 806, 806' in the UE, through measurements at UE 502 or elsewhere (e.g., at least one measurement associated with the cell), and / or from base station 504, another base station, network entity, etc.

[0119] At 904, the UE initiates or maintains a connection with the cell associated with the UE based on a combined metric that meets a threshold condition, where the combined metric is based on a set of cell metrics. As an example, this initiation or maintenance could be achieved by... Figure 13 It is performed by one or more of the components 198, transceiver 1322 and / or antenna 1380. Figure 5 An example is shown where UE 502 initiates or maintains a connection to a cell based on combined metrics.

[0120] In various respects, UE 502 can be configured to retrieve data from a data structure maintained by UE 502 (e.g., before initiating or maintaining (at 512) a connection. Figure 6 Cells can be selected from 610 in the data structure. In various aspects, cells can be selected from data structures (e.g., Figure 6 UE 502 can also be configured to be based on combined metrics (e.g., ...). This is associated with at least one of the following: ARFCN, TDD indication for the cell, FDD indication for the cell, cell-related measurements, etc. Figure 6 604 in the middle) and QOE request 506 (e.g., Figure 6 602 in the middle; Figure 7 708 in the middle; Figure 8 (806, 806') to the data structure maintained by UE 502 (e.g., Figure 6 The cells in 610) and at least one additional cell are reordered (e.g., in Figure 6 (at position 606 in the text). UE 502 can be configured to reorder cells and at least one additional cell (e.g., in...). Figure 6 (at position 606 in the code) after the data structure maintained by UE 502 (e.g., Figure 6 In 610), a cell is selected. UE 502 can be configured to send / provide an indication 510 of the cell to base station 504. That is, in all aspects, UE 502 can be configured to send / provide an indication 510 of the cell to network nodes (e.g., base station 504) before initiating or maintaining a connection with the cell. In all aspects, combined metrics (e.g., Figure 6 604 in the text can be based on a set of cell metrics, and the indication of a cell 510 can be based on a combined metric (e.g., Figure 6 604 in the middle) meets the threshold condition (e.g., Figure 6 (612 and 614 in the middle).

[0121] UE 502 can be configured to be based on combined metrics (e.g., Figure 6 604 in the middle) meets the threshold condition (e.g., Figure 6 (612, 614) to initiate or maintain (at 512) a connection with the cell associated with UE 502. As noted above, combined metrics (e.g., Figure 6 (604 in the original text) can be based on a set of cell metrics. In various respects, the combined metric (e.g., ...) can be determined / computed based on a weighted representation of the set of cell metrics. Figure 6 The 604 error can be returned, and can also be based on service characteristics (e.g., type, conditions, etc.) or a QOE request (e.g., 506 error). Figure 6 602 in the middle; Figure 7708 in the middle; Figure 8 The weighting is determined by factors such as 806 and 806'. In other words, the combined metric (e.g., ...) Figure 6 (604) can be based on a set of cell metrics using a combination of at least one corresponding weighted representation of RSRP with at least one of potential delay, tier number, or service characteristics. In each respect, the corresponding weighted representation can be based on a weighted value for the UE's idle mode and / or a weighted value for the UE's connected mode.

[0122] Figure 10 This is a flowchart 1000 of a method for wireless communication in various aspects. The method can be performed by a UE (e.g., UE 104, 502, 802; device 1304). In some aspects, the method may include combining... Figure 5 The communication process described in the document covers various aspects and / or Figure 6 , Figure 7 , Figure 8 The methods described herein can be used for QOE-based network / cell selection and provide improvements in UE cell mobility / maintenance by considering QOE metrics associated with both the user and UE sides, as well as the provider's service / application type. These improvements enable the UE to perform optimal cell selection, for example, for TDD and FDD utilization, as OEMs or service / application providers may be highly concerned with considering the user experience in their radio device solutions to optimize for different scenarios and improve the user experience.

[0123] At position 1002, before obtaining the cell metric set, the UE receives a QOE request associated with the cell metric set from a network node or network entity. As an example, this reception could be achieved by... Figure 13 It is performed by one or more of the components 198, transceiver 1322 and / or antenna 1380. Figure 5 An example is shown where UE 502 receives a QOE request from a network node (e.g., base station 504).

[0124] UE 502 can be configured to receive a QOE request 506 associated with the cell metric set from a network node (e.g., a base station 504 configured to transmit / provide) before obtaining the cell metric set. Figure 6 602 in the middle; Figure 7 708 in the middle; Figure 8 In the context of 806 and 806'). In various aspects, QOE requests 506 (e.g., Figure 6 602 in the middle; Figure 7 708 in the middle; Figure 8The 806, 806' in the document may include one or more features of a service / application to be utilized by UE 502, and may also or alternatively include a service trigger (e.g., a trigger from a service provider / OEM associated with the service / application). The service trigger may include, but is not limited to, a set of service features as indicated herein, and / or another indication of the cell, cell type, absolute radio frequency channel number (ARFCN), etc., to be used by UE 502 for the service / application. In various aspects, the service trigger may be provided by a network entity (e.g., an OEM server, etc.) and may be provided to UE 502 via base station 504 or another communication path. That is, in various aspects, QOE request 506 (e.g., Figure 6 602 in the middle; Figure 7 708 in the middle; Figure 8 The 806 and 806' in the UE 502 can indicate various characteristics desired by the service / application in order to improve or maximize QOE, which allows the UE 502 to select the cell that is best suited for the service / application.

[0125] At position 1004, the UE obtains a set of cell metrics associated with the cell, wherein the set of cell metrics includes at least one of potential latency, tier number, or service characteristics. As an example, this acquisition can be achieved by... Figure 13 It is performed by one or more of the components 198, transceiver 1322 and / or antenna 1380. Figure 5 An example is shown where UE 502 obtains such a set of cell metrics from a network node (e.g., base station 504).

[0126] UE 502 can be configured to obtain (at 508) a set of cell metrics associated with the cell of UE 502. In various aspects, the set of cell metrics may include RSRP and potential latency, tier number, and / or service characteristics. In various aspects, service characteristics may be one or more of low latency, high throughput, and / or low power. The tier number may be one or more tiers of the wireless communication system architecture (e.g., LTE, 5G NR, 5G+, 6G, etc.) utilized by the service / application, and potential latency may be a value of some type of delay experienced by UE 502 (e.g., round-trip time (RTT) and end-to-end (E2E) time, UE latency, etc.). Cell metrics can be requested from QOE 506 (e.g., Figure 6 602 in the middle; Figure 7 708 in the middle; Figure 8 The measurements are obtained from 806, 806' in the UE, through measurements at UE502 or elsewhere (e.g., at least one measurement associated with the cell), and / or from base station 504, another base station, network entity, etc.

[0127] At point 1006, the UE sends an indication to the cell based on a combined metric satisfying a threshold condition, targeting a network node and before initiating or maintaining a connection with the cell. As an example, this transmission could be performed by... Figure 13 It is performed by one or more of the components 198, transceiver 1322 and / or antenna 1380. Figure 5 An example is shown where UE 502 sends such an instruction to a network node (e.g., base station 504) regarding the cell.

[0128] In various respects, UE 502 can be configured to retrieve data from a data structure maintained by UE 502 (e.g., before initiating or maintaining (at 512) a connection. Figure 6 Cells can be selected from 610 in the data structure. In various aspects, cells can be selected from data structures (e.g., Figure 6 UE 502 can also be configured to be based on combined metrics (e.g., ...). This is associated with at least one of the following: ARFCN, TDD indication for the cell, FDD indication for the cell, cell-related measurements, etc. Figure 6 604 in the middle) and QOE request 506 (e.g., Figure 6 602 in the middle; Figure 7 708 in the middle; Figure 8 (806, 806') to the data structure maintained by UE 502 (e.g., Figure 6 The cells in 610) and at least one additional cell are reordered (e.g., in Figure 6 (at position 606 in the text). UE 502 can be configured to reorder cells and at least one additional cell (e.g., in...). Figure 6 (at position 606 in the code) after the data structure maintained by UE 502 (e.g., Figure 6 In 610), a cell is selected. UE 502 can be configured to send / provide an indication 510 of the cell to base station 504. That is, in all aspects, UE 502 can be configured to send / provide an indication 510 of the cell to network nodes (e.g., base station 504) before initiating or maintaining a connection with the cell. In all aspects, combined metrics (e.g., Figure 6 604 in the text can be based on a set of cell metrics, and the indication of a cell 510 can be based on a combined metric (e.g., Figure 6 604 in the middle) meets the threshold condition (e.g., Figure 6 (612 and 614 in the middle).

[0129] At point 1008, the UE initiates or maintains a connection with the cell associated with the UE based on a combined metric that meets a threshold condition, where the combined metric is based on a set of cell metrics. As an example, this initiation or maintenance could be achieved by... Figure 13It is performed by one or more of the components 198, transceiver 1322 and / or antenna 1380. Figure 5 An example is shown where UE 502 initiates or maintains a connection to a cell based on combined metrics.

[0130] UE 502 can be configured to be based on combined metrics (e.g., Figure 6 604 in the middle) meets the threshold condition (e.g., Figure 6 (612, 614) to initiate or maintain (at 512) a connection with the cell associated with UE 502. As noted above, combined metrics (e.g., Figure 6 (604 in the original text) can be based on a set of cell metrics. In various respects, the combined metric (e.g., ...) can be determined / computed based on a weighted representation of the set of cell metrics. Figure 6 The 604 error can be returned, and can also be based on service characteristics (e.g., type, conditions, etc.) or a QOE request (e.g., 506 error). Figure 6 602 in the middle; Figure 7 708 in the middle; Figure 8 The weighting is determined by factors such as 806 and 806'. In other words, the combined metric (e.g., ...) Figure 6 (604) can be based on a set of cell metrics using a combination of at least one corresponding weighted representation of RSRP with at least one of potential delay, tier number, or service characteristics. In each respect, the corresponding weighted representation can be based on a weighted value for the UE's idle mode and / or a weighted value for the UE's connected mode.

[0131] Figure 11 This is a flowchart 1100 of a method for wireless communication in various aspects. The method can be performed by network nodes / network entities (e.g., base stations 102, 504, 804; network entities 1302, 1402, 1560). In some aspects, the method may include combining... Figure 5 The communication process described in the document covers various aspects and / or Figure 6 , Figure 7 , Figure 8 The methods described herein can be used for QOE-based network / cell selection and provide improvements in UE cell mobility / maintenance by considering QOE metrics associated with the user and UE sides, as well as the provider's service / application type. These improvements enable UE / network nodes to perform optimal cell selection, for example, for TDD and FDD utilization, as OEMs or service / application providers may be highly concerned with considering the user experience in their radio device solutions to optimize for different scenarios and improve user experience.

[0132] At 1102, the network node obtains a set of cell metrics for the cell associated with the UE, wherein the set of cell metrics includes RSRP and at least one of potential latency, tier number, or service characteristics. As an example, this acquisition may be at least partially derived from... Figure 13 Components 199, transceiver 1446, and / or antenna 1480, Figure 15 It may be performed by one or more of the components 199 and / or network interface 1580. Figures 6 to 8 An example is shown where base station 804 obtains a set of cell metrics from a network entity (e.g., network entity 814).

[0133] In one configuration, Figure 800 illustrates an aspect of the functionality performed by reference network entity 814 and base station 804 for QOE-based network / cell selection for UE 802. As noted above, one or more aspects of UE-based user QOE-based cell selection can be performed by network nodes. Network entity 814 can be configured to provide QOE request 806 (e.g., Figure 5 506 in the middle; Figure 6 602 in the middle; Figure 7 (708 in the original text), this QOE request is associated with a set of cell metrics associated with the cell of UE 802, and base station 804 can be configured to receive this QOE request. In some aspects, for example, such as Figure 5 As shown, base station 804 can then send a QOE request to 806 (e.g., Figure 5 506 in the middle; Figure 6 602 in the middle; Figure 7 708 in the document is provided to UE 802. In various aspects, QOE request 806 (e.g., Figure 5 506 in the middle; Figure 6 602 in the middle; Figure 7 708 in the document may include one or more features of a service / application to be utilized by UE 802, and may also or alternatively include service triggers (e.g., triggers from a service provider / OEM associated with the service / application). Service triggers may include, but are not limited to, a set of service features as indicated herein, and / or another indication of the cell, cell type, absolute radio frequency channel number (ARFCN), etc., to be used by UE 802 for the service / application. In various respects, service triggers may be provided by a network entity such as network entity 814 (e.g., an OEM server, etc.). That is, in various respects, QOE request 806 (e.g., Figure 5 506 in the middle; Figure 6 602 in the middle; Figure 7 (708) can instruct base station 804 on various characteristics desired by the service / application in order to improve or maximize QOE, which enables base station 804 to select the cell most suitable for the service / application for UE 802.

[0134] In various respects, as shown in Figure 800, base station 804 can be configured to utilize QOE to request 806 (e.g., Figure 5 506 in the middle; Figure 6 602 in the middle; Figure 7 (708 in the middle) to obtain (at 808) (for example, as Figure 5 The cell metric set associated with UE 802 (similarly described for UE 502 at 508) is described in various ways. In each aspect, the cell metric set may include RSRP and potential latency, tier number, and / or service characteristics. In each aspect, service characteristics may be one or more of low latency, high throughput, and / or low power. The tier number may be one or more tiers of the wireless communication system architecture (e.g., LTE, 5G NR, 5G+, 6G, etc.) utilized by the service / application, and potential latency may be a value of some type of latency experienced by UE 802 (e.g., round-trip time (RTT) and end-to-end (E2E) time, UE latency, etc.). Cell metrics can be obtained from QOE request 806 (e.g., Figure 5 506 in the middle; Figure 6 602 in the middle; Figure 7 The measurement is obtained from 708 in the UE 802, through measurements at UE 802 and / or elsewhere (e.g., at least one measurement associated with the cell), and / or from base station 804, another base station, network entity 814, etc. Therefore, base station 804 can be configured to allow UE 802 to select and satisfy threshold conditions for QOE associated with the service / application (e.g., ...). Figure 6 The residential areas (612 and 614) are as mentioned above. Figure 5 , Figure 6 Described similarly.

[0135] At 1104, the network node initiates or maintains a connection from the UE to the cell associated with the UE based on a combined metric that satisfies a threshold condition, wherein the combined metric is based on a set of cell metrics. As an example, this initiation / maintenance may be at least partially determined by… Figure 13 Components 199, transceiver 1446, and / or antenna 1480, Figure 15 It may be performed by one or more of the components 199 and / or network interface 1580. Figures 6 to 8 An example is shown where base station 804 initiates / maintains a connection for a UE (e.g., UE 802).

[0136] Base station 804 can be configured to send / provide indication 810 of the cell to UE 802. That is, in various aspects, base station 804 can be configured to send / provide indication 810 of the cell to UE 802 before initiating or maintaining a connection with the cell. In various aspects, combined metrics (e.g., Figure 6604 in the text can be based on a set of cell metrics, and the indication of a cell 810 can be based on a combined metric (e.g., Figure 6 604 in the middle) meets the threshold condition (e.g., Figure 6 (612, 614 in the original text). Therefore, base station 804 and / or UE 802 can be configured to be based on combined metrics (e.g., Figure 6 604 in the middle) meets the threshold condition (e.g., Figure 6 (612, 614) to initiate or maintain (at 812) a connection with the cell associated with UE 802, as described in this document. Figure 5 UE502 is described similarly. In various respects, the base station 804, configured to send / provide indications 810 of the cell to UE 802, can be based on combined metrics (e.g., Figure 6 604 in the middle) meets the threshold condition (e.g., Figure 6 The portion of 612, 614 in the diagram is used to initiate or maintain (at 812) a connection with the cell associated with UE 802. As noted above, combined metrics (e.g., Figure 6 (604 in the original text) can be based on a set of cell metrics. In various respects, the combined metric (e.g., ...) can be determined / computed based on a weighted representation of the set of cell metrics. Figure 6 The 604 error can be returned, and can also be based on service characteristics (e.g., type, conditions, etc.) or a QOE request (e.g., 806 error). Figure 5 506 in the middle; Figure 6 602 in the middle; Figure 7 The weighting is determined by factors such as 708 in the model. That is, the combined metric (e.g., ...) Figure 6 (604) can be based on a set of cell metrics using a combination of at least one corresponding weighted representation of RSRP with at least one of potential delay, tier number, or service characteristics. In each respect, the corresponding weighted representation can be based on a weighted value for the UE's idle mode and / or a weighted value for the UE's connected mode.

[0137] Figure 12 This is a flowchart 1200 of a method for wireless communication in various aspects. The method can be performed by network nodes / network entities (e.g., base stations 102, 504, 804; network entities 1302, 1402, 1560). In some aspects, the method may include combining... Figure 5 The communication process described in the document covers various aspects and / or Figure 6 , Figure 7 , Figure 8The methods described herein can be used for QOE-based network / cell selection and provide improvements in UE cell mobility / maintenance by considering QOE metrics associated with the user and UE sides, as well as the provider's service / application type. These improvements enable UE / network nodes to perform optimal cell selection, for example, for TDD and FDD utilization, as OEMs or service / application providers may be highly concerned with considering the user experience in their radio device solutions to optimize for different scenarios and improve user experience.

[0138] At 1202, before obtaining the cell metric set, the network node receives a QOE request associated with the cell metric set from the network entity. As an example, this reception may be at least partially handled by… Figure 13 Components 199, transceiver 1446, and / or antenna 1480, Figure 15 It may be performed by one or more of the components 199 and / or network interface 1580. Figures 6 to 8 An example is shown where base station 804 receives a QOE request from a network entity (e.g., network entity 814).

[0139] In one configuration, Figure 800 illustrates an aspect of the functionality performed by reference network entity 814 and base station 804 for QOE-based network / cell selection for UE 802. As noted above, one or more aspects of UE-based user QOE-based cell selection can be performed by network nodes. Network entity 814 can be configured to provide QOE request 806 (e.g., Figure 5 506 in the middle; Figure 6 602 in the middle; Figure 7 (708 in the original text), this QOE request is associated with a set of cell metrics associated with the cell of UE 802, and base station 804 can be configured to receive this QOE request. In some aspects, for example, such as Figure 5 As shown, base station 804 can then send a QOE request to 806 (e.g., Figure 5 506 in the middle; Figure 6 602 in the middle; Figure 7 708 in the document is provided to UE 802. In various aspects, QOE request 806 (e.g., Figure 5 506 in the middle; Figure 6 602 in the middle; Figure 7708 in the document may include one or more features of a service / application to be utilized by UE 802, and may also or alternatively include service triggers (e.g., triggers from a service provider / OEM associated with the service / application). Service triggers may include, but are not limited to, a set of service features as indicated herein, and / or another indication of the cell, cell type, absolute radio frequency channel number (ARFCN), etc., to be used by UE 802 for the service / application. In various respects, service triggers may be provided by a network entity such as network entity 814 (e.g., an OEM server, etc.). That is, in various respects, QOE request 806 (e.g., Figure 5 506 in the middle; Figure 6 602 in the middle; Figure 7 (708) can instruct base station 804 on various characteristics desired by the service / application in order to improve or maximize QOE, which enables base station 804 to select the cell most suitable for the service / application for UE 802.

[0140] At 1204, the network node obtains a set of cell metrics for the cell associated with the UE, wherein the set of cell metrics includes RSRP and at least one of potential latency, tier number, or service characteristics. As an example, this acquisition may be at least partially derived from... Figure 13 Components 199, transceiver 1446, and / or antenna 1480, Figure 15 It may be performed by one or more of the components 199 and / or network interface 1580. Figures 6 to 8 An example is shown where base station 804 obtains a set of cell metrics from a network entity (e.g., network entity 814).

[0141] In various respects, as shown in Figure 800, base station 804 can be configured to utilize QOE to request 806 (e.g., Figure 5 506 in the middle; Figure 6 602 in the middle; Figure 7 (708 in the middle) to obtain (at 808) (for example, as Figure 5 The cell metric set associated with UE 802 (similarly described for UE 502 at 508) is described in various ways. In each aspect, the cell metric set may include RSRP and potential latency, tier number, and / or service characteristics. In each aspect, service characteristics may be one or more of low latency, high throughput, and / or low power. The tier number may be one or more tiers of the wireless communication system architecture (e.g., LTE, 5G NR, 5G+, 6G, etc.) utilized by the service / application, and potential latency may be a value of some type of latency experienced by UE 802 (e.g., round-trip time (RTT) and end-to-end (E2E) time, UE latency, etc.). Cell metrics can be obtained from QOE request 806 (e.g., Figure 5 506 in the middle; Figure 6602 in the middle; Figure 7 The measurement is obtained from 708 in the UE 802, through measurements at UE 802 and / or elsewhere (e.g., at least one measurement associated with the cell), and / or from base station 804, another base station, network entity 814, etc. Therefore, base station 804 can be configured to allow UE 802 to select and satisfy threshold conditions for QOE associated with the service / application (e.g., ...). Figure 6 The residential areas (612 and 614) are as mentioned above. Figure 5 , Figure 6 Described similarly.

[0142] At point 1206, the network node sends an indication to the cell based on a combined metric satisfying a threshold condition, before initiating or maintaining a connection with the cell, for the UE. As an example, this transmission may be at least partially... Figure 13 Components 199, transceiver 1446, and / or antenna 1480, Figure 15 It may be performed by one or more of the components 199 and / or network interface 1580. Figures 6 to 8 An example is shown where base station 804 sends an instruction about the cell to UE (e.g., UE 802).

[0143] Base station 804 can be configured to send / provide indication 810 of the cell to UE 802. That is, in various aspects, base station 804 can be configured to send / provide indication 810 of the cell to UE 802 before initiating or maintaining a connection with the cell. In various aspects, combined metrics (e.g., Figure 6 604 in the text can be based on a set of cell metrics, and the indication of a cell 810 can be based on a combined metric (e.g., Figure 6 604 in the middle) meets the threshold condition (e.g., Figure 6 (612 and 614 in the middle).

[0144] At point 1208, the network node initiates or maintains a connection from the UE to the cell associated with the UE based on a combined metric that satisfies a threshold condition, wherein the combined metric is based on a set of cell metrics. As an example, this initiation / maintenance may be at least partially determined by… Figure 13 Components 199, transceiver 1446, and / or antenna 1480, Figure 15 It may be performed by one or more of the components 199 and / or network interface 1580. Figures 6 to 8 An example is shown where base station 804 initiates / maintains a connection for a UE (e.g., UE 802).

[0145] Therefore, base station 804 and / or UE 802 can be configured to base their systems on combined metrics (e.g., Figure 6 604 in the middle) meets the threshold condition (e.g., Figure 6(612, 614) to initiate or maintain (at 812) a connection with the cell associated with UE 802, as described in this document. Figure 5 UE 502 is described similarly. In various respects, base station 804, configured to send / provide indication 810 of the cell to UE 802, can be based on combined metrics (e.g., Figure 6 604 in the middle) meets the threshold condition (e.g., Figure 6 The portion of 612, 614 in the diagram is used to initiate or maintain (at 812) a connection with the cell associated with UE 802. As noted above, combined metrics (e.g., Figure 6 (604 in the original text) can be based on a set of cell metrics. In various respects, the combined metric (e.g., ...) can be determined / computed based on a weighted representation of the set of cell metrics. Figure 6 The 604 error can be returned, and can also be based on service characteristics (e.g., type, conditions, etc.) or a QOE request (e.g., 806 error). Figure 5 506 in the middle; Figure 6 602 in the middle; Figure 7 The weighting is determined by factors such as 708 in the model. That is, the combined metric (e.g., ...) Figure 6 (604) can be based on a set of cell metrics using a combination of at least one corresponding weighted representation of RSRP with at least one of potential delay, tier number, or service characteristics. In each respect, the corresponding weighted representation can be based on a weighted value for the UE's idle mode and / or a weighted value for the UE's connected mode.

[0146] Figure 13Figure 1300 illustrates an example of a hardware implementation for device 1304. Device 1304 may be a UE, a component of a UE, or implement UE functionality. In some aspects, device 1304 may include at least one cellular baseband processor 1324 (also referred to as a modem) coupled to one or more transceivers 1322 (e.g., cellular RF transceivers). Cellular baseband processor 1324 may include at least one on-chip memory 1324'. In some aspects, device 1304 may also include one or more Subscriber Identity Module (SIM) cards 1320 and at least one application processor 1306 coupled to a Secure Digital Card (SD) card 1308 and a screen 1310. Application processor 1306 may include on-chip memory 1306'. In some aspects, device 1304 may also include a Bluetooth module 1312, a WLAN module 1314, an SPS module 1316 (e.g., a GNSS module), one or more sensor modules 1318 (e.g., a barometric pressure sensor / altimeter; motion sensors such as an inertial measurement unit (IMU), gyroscope, and / or accelerometer; light detection and ranging (LIDAR), radio-assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), magnetometer, audio, and / or other technologies for positioning), an additional memory module 1326, a power supply 1330, and / or a camera 1332. Bluetooth module 1312, WLAN module 1314, and SPS module 1316 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). Bluetooth module 1312, WLAN module 1314, and SPS module 1316 may include their own dedicated antennas and / or communicate using antenna 1380. Cellular baseband processor 1324 communicates with UE 104 and / or RU associated with network entity 1302 via transceiver 1322 through one or more antennas 1380. Cellular baseband processor 1324 and application processor 1306 may each include computer-readable media / memory 1324', 1306'. Additional memory module 1326 may also be considered as computer-readable media / memory. Each computer-readable media / memory 1324', 1306', 1326 may be non-transitory. Cellular baseband processor 1324 and application processor 1306 are each responsible for general processing, including the execution of software stored on the computer-readable media / memory. When executed by cellular baseband processor 1324 / application processor 1306, the software causes cellular baseband processor 1324 / application processor 1306 to perform the various functions described above. Cellular baseband processor 1324 and application processor 1306 are configured to perform the various functions described above based at least in part on information stored in memory.In other words, the cellular baseband processor 1324 and application processor 1306 can be configured to perform a first subset of the various functions described above without information stored in memory, and can be configured to perform a second subset of the various functions described above based on information stored in memory. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 1324 / application processor 1306 during software execution. The cellular baseband processor 1324 / application processor 1306 can be a component of the UE 350 and can include at least one of a memory 360 and / or at least one of a TX processor 368, an RX processor 356, and a controller / processor 359. In one configuration, the device 1304 can be at least one processor chip (modem and / or application) and includes only the cellular baseband processor 1324 and / or application processor 1306, while in another configuration, the device 1304 can be the entire UE (e.g., see [link]). Figure 3 The UE350 includes an additional module of the device 1304.

[0147] As discussed above, component 198 can be configured to obtain a set of cell metrics associated with the UE, wherein the set of cell metrics includes RSRP and at least one of potential delay, tier number, or service characteristics. Component 198 can also be configured to initiate or maintain a connection with the cell associated with the UE based on a threshold condition met by the combined metrics, wherein the combined metrics are based on the set of cell metrics. Component 198 can be configured to receive a QOE request associated with the set of cell metrics from a network node or network entity before obtaining the set of cell metrics. Component 198 can be configured to send an indication to the cell to a network node based on a threshold condition met by the combined metrics before initiating or maintaining a connection with the cell. Component 198 can also be configured to perform a combination... Figures 9 to 12 Any aspect described in the flowchart of any of the above and / or by the UE for any aspect Figures 4 to 8Any aspect of the process / algorithm performed by any of the processors. Component 198 may reside within cellular baseband processor 1324, application processor 1306, or both cellular baseband processor 1324 and application processor 1306. Component 198 may be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may execute the stated process / algorithm individually or in combination. As shown, apparatus 1304 may include a variety of components configured for various functions. In one configuration, apparatus 1304 (and particularly cellular baseband processor 1324 and / or application processor 1306) may include components for obtaining a set of cell metrics associated with the UE, wherein the set of cell metrics includes RSRP and at least one of potential delay, tier number, or service characteristics. In this configuration, device 1304 (and particularly cellular baseband processor 1324 and / or application processor 1306) may include components for initiating or maintaining a connection with a cell associated with the UE based on a combined metric satisfying a threshold condition, wherein the combined metric is based on a set of cell metrics. In one configuration, device 1304 (and particularly cellular baseband processor 1324 and / or application processor 1306) may include components for receiving a QOE request associated with a set of cell metrics from a network node or network entity before obtaining the set of cell metrics. In one configuration, device 1304 (and particularly cellular baseband processor 1324 and / or application processor 1306) may include components for sending an indication to a cell to a network node and before initiating or maintaining a connection with the cell based on a combined metric satisfying a threshold condition. These components may be components 198 of device 1304 configured to perform the functions described therein. As described above, device 1304 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Therefore, in one configuration, these components may be a TX processor 368, an RX processor 356, and / or a controller / processor 359 configured to perform the functions described therein.

[0148] Figure 14Figure 1400 illustrates an example of a hardware implementation for network entity 1402. Network entity 1402 may be a BS, a component of a BS, or implement BS functionality. Network entity 1402 may include at least one of CU 1410, DU 1430, or RU 1440. For example, depending on the layer functionality handled by component 199, network entity 1402 may include CU 1410; both CU 1410 and DU 1430; each of CU 1410, DU 1430, and RU 1440; DU 1430; both DU 1430 and RU 1440; or RU 1440. CU 1410 may include at least one CU processor 1412. CU processor 1412 may include on-chip memory 1412'. In some aspects, CU 1410 may also include an additional memory module 1414 and a communication interface 1418. CU1410 communicates with DU 1430 via a midhaul link, such as an F1 interface. DU 1430 may include at least one DU processor 1432. DU processor 1432 may include on-chip memory 1432'. In some aspects, DU 1430 may also include an additional memory module 1434 and a communication interface 1438. DU 1430 communicates with RU 1440 via a fronthaul link. RU 1440 may include at least one RU processor 1442. RU processor 1442 may include on-chip memory 1442'. In some aspects, RU 1440 may also include an additional memory module 1444, one or more transceivers 1446, an antenna 1480, and a communication interface 1448. RU 1440 communicates with UE 104. On-chip memories 1412', 1432', 1442' and additional memory modules 1414, 1434, 1444 may each be considered as computer-readable media / memory. Each computer-readable medium / memory can be non-transitory. Each of processors 1412, 1432, and 1442 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the corresponding processor, the software causes the processor to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the processor while executing the software.

[0149] As discussed above, component 199 can be configured to obtain a set of cell metrics associated with the UE, wherein the set of cell metrics includes RSRP and at least one of potential latency, tier number, or service characteristics. Component 199 can also be configured to initiate or maintain a connection between the UE and the cell associated with the UE based on a threshold condition met by the combined metrics, wherein the combined metrics are based on the set of cell metrics. Component 199 can be configured to receive a QOE request associated with the cell metric set from a network entity before obtaining the set of cell metrics. Component 199 can be configured to send an indication to the cell for the UE and before initiating or maintaining a connection with the cell based on a threshold condition met by the combined metrics. Component 199 can also be configured to perform a combination... Figures 9 to 12 Any aspect described in the flowchart of any of the above, and / or by the network node / base station. Figures 4 to 8 Any aspect of the process / algorithm performed by any of the components. Component 199 may be within one or more processors of one or more of CU 1410, DU 1430, and RU 1440. Component 199 may be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may execute the stated process / algorithm individually or in combination. Network entity 1402 may include a variety of components configured for various functions. In one configuration, network entity 1402 may include components for obtaining a set of cell metrics associated with the UE, wherein the set of cell metrics includes RSRP and at least one of potential latency, tier number, or service characteristics. In this configuration, network entity 1402 may include components for initiating or maintaining a connection between the UE and the cell associated with the UE based on a threshold condition met by a combined metric, wherein the combined metric is based on the set of cell metrics. In one configuration, network entity 1402 may include components for receiving a QOE request associated with the cell metric set from the network entity before obtaining the cell metric set. In one configuration, network entity 1402 may include components for sending an indication to the UE and, before initiating or maintaining a connection with the cell, based on a threshold condition being met by the combined metric. These components may be components 199 of network entity 1402 configured to perform the functions described therein. As described above, network entity 1402 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Therefore, in one configuration, these components may be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions described therein.

[0150] Figure 15 Figure 1500 illustrates an example of a hardware implementation for network entity 1560. In one example, network entity 1560 may be within core network 120. Network entity 1560 may include at least one network processor 1512. Network processor 1512 may include on-chip memory 1512'. In some aspects, network entity 1560 may also include an additional memory module 1514. Network entity 1560 communicates directly (e.g., via a backhaul link) or indirectly (e.g., via RIC) with CU 1502 and / or UE 104 via network interface 1580. On-chip memory 1512' and additional memory module 1514 may each be considered as computer-readable media / memory. Each computer-readable media / memory may be non-transitory. Network processor 1512 is responsible for general processing, including executing software stored on the computer-readable media / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described above. The computer-readable media / memory may also be used to store data manipulated by the processor when executing the software.

[0151] As discussed above, component 199 can be configured to obtain a set of cell metrics associated with the UE, wherein the set of cell metrics includes RSRP and at least one of potential latency, tier number, or service characteristics. Component 199 can also be configured to initiate or maintain a connection between the UE and the cell associated with the UE based on a threshold condition met by the combined metrics, wherein the combined metrics are based on the set of cell metrics. Component 199 can be configured to receive a QOE request associated with the cell metric set from a network entity before obtaining the set of cell metrics. Component 199 can be configured to send an indication to the cell for the UE and before initiating or maintaining a connection with the cell based on a threshold condition met by the combined metrics. Component 199 can also be configured to perform a combination... Figures 9 to 12 Any aspect described in the flowchart of any of the above, and / or by the network node / base station. Figures 4 to 8Any aspect of the process / algorithm performed by any of the components. Component 199 may be within network processor 1512. Component 199 may be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may execute the stated process / algorithm individually or in combination. Network entity 1560 may include a variety of components configured for various functions. In one configuration, network entity 1560 may include components for obtaining a set of cell metrics associated with the UE, wherein the set of cell metrics includes RSRP and at least one of potential latency, tier number, or service characteristics. In this configuration, network entity 1560 may include components for initiating or maintaining a connection between the UE and the cell associated with the UE based on a threshold condition met by a combined metric, wherein the combined metric is based on the set of cell metrics. In one configuration, network entity 1560 may include components for receiving a QOE request associated with the set of cell metrics from a network entity before obtaining the set of cell metrics. In one configuration, network entity 1560 may include components for sending an indication to the cell to the UE and to the cell based on a combined metric satisfying a threshold condition before initiating or maintaining a connection with the cell. These components may be components 199 of network entity 1560 configured to perform the functions described therein.

[0152] Wireless communication systems can support the use of RSRP as an indicator of signal quality. Based on signal quality, the network can determine whether to hand over the UE from one cell to another, allowing the UE to communicate with the new serving base station / gNB using higher quality signaling. However, basing UE mobility on signal quality without other considerations may lead to scenarios where this approach fails to meet the user's expected experience. Furthermore, in geographical areas where TDD and FDD cells overlap, signal quality mobility does not consider how TDD and FDD cells can be applied to improve the user's QOE. As an example, gaming and voice calls in mobility can be user-sensitive applications, where bursts of low-latency and high-quality small random-size packet transmissions are beneficial in gaming, while regular periodicity with very high-quality UM packets may be important in voice calls. Both applications can benefit from different types of serving cells. As another example, downloading data in mobility can benefit from the highest data rate that can be completed in a short time to save power, while long travel times in mobility can benefit from keeping the UE in a very low-power mode while waiting for a charging opportunity.

[0153] The various aspects generally relate to wireless communication systems utilizing cell selection. Some aspects more specifically relate to QOE-based network / cell selection for UEs (e.g., for TDD and / or FDD cells). In one example, a UE may be configured to obtain a set of cell metrics associated with the UE, wherein the set of cell metrics includes at least one of a Reference Signal Received Power (RSRP) and potential delay, stratum number, or service characteristics. The UE may also be configured to initiate or maintain a connection to a cell associated with the UE based on a threshold condition met by a combined metric, wherein the combined metric is based on a set of cell metrics. In another example, a network node (e.g., a base station, gNB, etc.) may be configured to obtain a set of cell metrics associated with the UE, wherein the set of cell metrics includes at least one of a RSRP and potential delay, stratum number, or service characteristics. The network node may also be configured to initiate or maintain a connection from the UE to a cell associated with the UE based on a threshold condition met by a combined metric, wherein the combined metric is based on a set of cell metrics. In some examples, in addition to RSPR considerations or in lieu of RSRP considerations, the selection of the cell for serving the UE can be based on QOE, and the choice between TDD or FDD can be considered based on QOE metrics for the user and UE sides as well as for the service / application type of the provider.

[0154] This article addresses various aspects of QOE-based network / cell selection for UEs by considering QOE metrics associated with both the user and UE sides, as well as the provider's service / application type, to provide better cell selection for, for example, TDD and FDD utilization.

[0155] It should be understood that the specific order or hierarchy of the boxes in the disclosed process / flowcharts is merely an example of the exemplary method. It should be understood that the specific order or hierarchy of the boxes in the process / flowcharts may be rearranged based on design preferences. Furthermore, some boxes may be combined or omitted. The appended method claims present the elements of various boxes in a sample order, but are not limited to the given specific order or hierarchy.

[0156] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the aspects described herein but should be given the full scope consistent with the language of the claims. Unless specifically stated otherwise, references to elements in the singular form do not mean “one and only one” but rather “one or more.” Terms such as “if,” “when,” and “simultaneously” do not imply a direct temporal relationship or reaction. That is, these phrases, such as “when,” do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply suggest that if a condition is met, then the action will occur, without requiring a specific or immediate time limit for the occurrence of the action. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or superior to other aspects. Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" can be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a group of elements, where the elements are numbered one or more. Therefore, for a set of X, X will include one or more elements. When at least one processor is configured to execute a set of functions, that at least one processor is configured to execute that set of functions individually or in any combination. Therefore, each of the at least one processor can be configured to perform a specific subset of the set of functions, wherein the subset is the complete set, a suitable subset of the set, or an empty subset of the set. If the first device receives data from or sends data to the second device, data can be received / sent directly between the first and second devices, or indirectly between the first and second devices through a set of devices. A device configured to “output” data (such as transmission, signal, or message) can, for example, transmit the data using a transceiver, or can transmit the data to the device that sent the data.A device configured to "acquire" data (such as, transmit, signal, or message) may, for example, receive the data using a transceiver, or may obtain the data from a device that receives the data. Information stored in memory includes instructions and / or data. All structural and functional equivalents of the elements throughout the various aspects described herein that are known to those skilled in the art or will later be known are expressly incorporated herein by reference and are covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is explicitly recited in the claims. The words "module," "mechanism," "element," "device," etc., cannot replace the word "component." Therefore, no claim element will be construed as a functional component unless the element is explicitly recited using the phrase "component for..."

[0157] As used in this article, the phrase “based on” should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase “based on A” (where “A” can be information, conditions, factors, etc.) should be interpreted as “based on at least A”, unless otherwise stated otherwise.

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

[0159] Aspect 1 is a method for wireless communication at a user equipment (UE), the method comprising: obtaining a set of cell metrics associated with the UE, wherein the set of cell metrics includes at least one of reference signal received power (RSRP) and potential delay, layer number, or service characteristics; and initiating or maintaining a connection with the cell associated with the UE based on a combined metric satisfying a threshold condition, wherein the combined metric is based on the set of cell metrics.

[0160] Aspect 2 is the method according to aspect 1, wherein obtaining the cell metric set comprises: obtaining the cell metric set from at least one of a Quality of Experience (QOE) request or at least one measurement associated with the cell; wherein the combined metric is based on the cell metric set using a combination of at least one corresponding weighted representation of the RSRP and at least one of the potential delay, the number of tiers, or the service characteristics.

[0161] Aspect 3 is the method according to aspect 2, the method further comprising: receiving, from a network node or network entity, a QOE request associated with the cell metric set before obtaining the cell metric set; and sending an indication to the network node, based on the combined metric satisfying the threshold condition, before initiating or maintaining the connection with the cell.

[0162] Aspect 4 is the method according to aspect 2, wherein the QOE request indicates the service feature or the service trigger, and wherein at least one corresponding weighted representation is associated with the service feature or the service trigger; and wherein the service feature is at least one of low latency, high throughput, or low power, or wherein the service trigger indicates the service feature.

[0163] Aspect 5 is the method according to aspect 2, wherein initiating or maintaining the connection with the cell includes: prior to initiating or maintaining the connection, selecting the cell from a data structure maintained by the UE, wherein the cell in the data structure is associated with at least one of an absolute radio frequency channel number (ARFCN), a time division duplex (TDD) indication, a frequency division duplex (FDD) indication, or at least one of the measurements associated with the cell.

[0164] Aspect 6 is the method according to aspect 5, wherein selecting the cell from the data structure maintained by the UE comprises: reordering the cell and at least one additional cell in the data structure maintained by the UE based on the combined metric and the QOE request; and selecting the cell from the data structure maintained by the UE after reordering the cell and the at least one additional cell.

[0165] Aspect 7 is the method according to any one of Aspects 2 to 6, wherein each of the at least one corresponding weighted representations is based on a first weighted value for the idle mode of the UE or a second weighted value for the connected mode of the UE.

[0166] Aspect 8 is the method according to aspect 7, wherein the first weighting value includes a positive weighting value associated with at least one of the RSRP or the number of layers that meets the throughput threshold, or a negative weighting value associated with at least one of the RSRP or the number of layers that fails to meet the throughput threshold.

[0167] Aspect 9 is the method according to any one of Aspects 7 and 8, wherein the first weighting value includes a positive weighting value associated with the potential delay that satisfies the delay threshold, or a negative weighting value associated with the potential delay that fails to satisfy the delay threshold.

[0168] Aspect 10 is the method according to any one of Aspects 7 to 9, wherein the service characteristic is at least one of low latency, high throughput, or low power; wherein the first weighting value includes a positive weighting value associated with the service characteristic that satisfies the characteristic threshold, or a negative weighting value associated with the service characteristic that fails to satisfy the characteristic threshold.

[0169] Aspect 11 is the method according to aspect 7, wherein the second weighting value includes a positive weighting function associated with at least one of the RSRP or the number of layers that meets the throughput threshold, or a negative weighting function associated with at least one of the RSRP or the number of layers that fails to meet the throughput threshold.

[0170] Aspect 12 is the method according to any one of Aspects 7 and 11, wherein the second weighting value comprises a negative weighting function associated with the potential delay that satisfies the delay threshold, or a positive weighting function associated with the potential delay that fails to satisfy the delay threshold.

[0171] Aspect 13 is the method according to any one of Aspects 7, 11 and 12, wherein the service characteristic is at least one of low latency, high throughput, or low power; wherein the second weighting value includes a positive weighting function associated with the service characteristic that satisfies the characteristic threshold, or a negative weighting function associated with the service characteristic that fails to satisfy the characteristic threshold.

[0172] Aspect 14 is a method for wireless communication at a network node, the method comprising: obtaining a set of cell metrics associated with a user equipment (UE), wherein the set of cell metrics includes at least one of reference signal received power (RSRP) and potential delay, layer number, or service characteristics; and initiating or maintaining a connection from the UE to the cell associated with the UE based on a combined metric satisfying a threshold condition, wherein the combined metric is based on the set of cell metrics.

[0173] Aspect 15 is the method according to aspect 14, wherein obtaining the cell metric set comprises: obtaining the cell metric set from at least one of a Quality of Experience (QOE) request or at least one measurement associated with the cell; wherein the combined metric is based on the cell metric set using a combination of at least one corresponding weighted representation of the RSRP and at least one of the potential delay, the number of tiers, or the service characteristics.

[0174] Aspect 16 is the method according to aspect 15, the method further comprising: receiving, from a network entity, the QOE request associated with the cell metric set before obtaining the cell metric set; and sending an indication to the cell based on the combined metric satisfying the threshold condition for the UE before initiating or maintaining the connection with the cell.

[0175] Aspect 17 is the method according to aspect 16, wherein the QOE request indicates the service feature or service trigger, and wherein the at least one corresponding weighted representation is associated with the service feature or the service trigger; and wherein the service feature is at least one of low latency, high throughput, or low power, or wherein the service trigger indicates the service feature as a default feature associated with the network entity.

[0176] Aspect 18 is the method according to aspect 15, wherein initiating or maintaining the connection with the cell includes: prior to initiating or maintaining the connection, selecting the cell from a data structure maintained by the network node, wherein the cell in the data structure is associated with at least one of an absolute radio frequency channel number (ARFCN), a time division duplex (TDD) indication, a frequency division duplex (FDD) indication, or at least one of the measurements associated with the cell.

[0177] Aspect 19 is the method according to aspect 18, wherein selecting the cell from the data structure maintained by the network node comprises: reordering the cell and at least one additional cell in the data structure maintained by the network node based on the combined metric and the QOE request; and selecting the cell from the data structure maintained by the network node after reordering the cell and the at least one additional cell.

[0178] Aspect 20 is a method according to any one of aspects 15 to 19, wherein each of the at least one corresponding weighted representations is based on a first weighted value for the idle mode of the UE or a second weighted value for the connected mode of the UE.

[0179] Aspect 21 is the method according to aspect 20, wherein the first weighting value includes a positive weighting value associated with at least one of the RSRP or the number of layers that meets the throughput threshold, or a negative weighting value associated with at least one of the RSRP or the number of layers that fails to meet the throughput threshold.

[0180] Aspect 22 is the method according to any one of aspects 20 and 21, wherein the first weighting value includes a positive weighting value associated with the potential delay that satisfies the delay threshold, or a negative weighting value associated with the potential delay that fails to satisfy the delay threshold.

[0181] Aspect 23 is the method according to any one of Aspects 20 to 22, wherein the service characteristic is at least one of low latency, high throughput, or low power; wherein the first weighting value includes a positive weighting value associated with the service characteristic that satisfies the characteristic threshold, or a negative weighting value associated with the service characteristic that fails to satisfy the characteristic threshold.

[0182] Aspect 24 is the method according to aspect 20, wherein the second weighting value includes a positive weighting function associated with at least one of the RSRP or the number of layers that meets the throughput threshold, or a negative weighting function associated with at least one of the RSRP or the number of layers that fails to meet the throughput threshold.

[0183] Aspect 25 is the method according to any one of aspects 20 and 24, wherein the second weighting value comprises a negative weighting function associated with the potential delay that satisfies the delay threshold, or a positive weighting function associated with the potential delay that fails to satisfy the delay threshold.

[0184] Aspect 26 is the method according to any one of Aspects 20, 24 and 25, wherein the service characteristic is at least one of low latency, high throughput, or low power; wherein the second weighting value includes a positive weighting function associated with the service characteristic that satisfies the characteristic threshold, or a negative weighting function associated with the service characteristic that fails to satisfy the characteristic threshold.

[0185] Aspect 27 is an apparatus for wireless communication, the apparatus including components for implementing any one of aspects 1 to 13.

[0186] Aspect 28 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer-executable code that, when executed by at least one processor, causes the at least one processor to implement any one of aspects 1 to 13.

[0187] Aspect 29 is an apparatus for wireless communication at a network node. The apparatus includes: a memory; and at least one processor coupled to the memory and based at least in part on information stored in the memory, the at least one processor being configured to implement any one of aspects 1 to 13.

[0188] Aspect 30 is the apparatus according to aspect 29, the apparatus further comprising at least one of a transceiver or an antenna coupled to the at least one processor.

[0189] Aspect 31 is an apparatus for wireless communication, the apparatus including components for implementing any one of aspects 14 to 26.

[0190] Aspect 32 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer-executable code that, when executed by at least one processor, causes the at least one processor to implement any one of aspects 14 to 26.

[0191] Aspect 33 is an apparatus for wireless communication at a network node. The apparatus includes: a memory; and at least one processor coupled to the memory and based at least in part on information stored in the memory, the at least one processor being configured to implement any one of aspects 14 to 26.

[0192] Aspect 34 is the apparatus according to aspect 32, the apparatus further comprising at least one of a transceiver or an antenna coupled to the at least one processor.

[0193] Aspect 35 is an apparatus for wireless communication at a UE, the apparatus comprising: at least one memory; and at least one processor coupled to the at least one memory and based at least in part on information stored in the at least one memory, the at least one processor being configured individually or in any combination to perform the method according to any one of aspects 1 to 13.

[0194] Aspect 36 is an apparatus for wireless communication at a UE, the apparatus comprising components for performing each step of the method according to any one of aspects 1 to 13.

[0195] Aspect 37 is an apparatus according to any one of aspects 35 and 36, the apparatus further comprising a transceiver configured to receive or transmit in association with the method according to any one of aspects 1 to 13.

[0196] Aspect 38 is a computer-readable medium storing computer-executable code at a UE, the code causing the at least one processor to perform the method according to any one of aspects 1 to 13 when executed by at least one processor.

[0197] Aspect 39 is an apparatus for wireless communication at a network node, the apparatus comprising: at least one memory; and at least one processor coupled to the at least one memory and based at least in part on information stored in the at least one memory, the at least one processor being configured individually or in any combination to perform the method according to any one of aspects 14 to 26.

[0198] Aspect 40 is an apparatus for wireless communication at a network node, the apparatus comprising components for performing each step of the method according to any one of aspects 14 to 26.

[0199] Aspect 41 is an apparatus according to any one of aspects 39 and 40, the apparatus further comprising a transceiver configured to receive or transmit in association with the method according to any one of aspects 14 to 26.

[0200] Aspect 42 is a computer-readable medium storing computer-executable code at a network node, the code causing the at least one processor to perform the method according to any one of aspects 14 to 26 when executed by at least one processor.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: At least one memory; and At least one processor, coupled to the at least one memory, and configured individually or in any combination, based at least in part on information stored in the at least one memory, to: Obtain a set of cell metrics associated with the UE, wherein the set of cell metrics includes at least one of reference signal received power (RSRP) and potential delay, layer number, or service characteristics; as well as A connection to the cell associated with the UE is initiated or maintained based on a combined metric that meets a threshold condition, wherein the combined metric is based on the set of cell metrics.

2. The apparatus of claim 1, wherein, in order to obtain the cell metric set, the at least one processor is configured individually or in any combination to: The set of cell metrics is obtained from at least one of a Quality of Experience (QOE) request or at least one of at least one measurement associated with the cell; The combined metric is based on a set of cell metrics that use a combination of at least one of the RSRP and at least one of the potential delay, the number of layers, or the service characteristics.

3. The apparatus of claim 2, wherein the at least one processor is further configured, alone or in any combination, to: Before obtaining the cell metric set, receive the QOE request associated with the cell metric set from a network node or network entity; and For the network node and before initiating or maintaining the connection with the cell, an indication to the cell is sent based on the combined metric satisfying the threshold condition.

4. The apparatus of claim 2, wherein the QOE request indicates the service feature or service trigger, and wherein the at least one corresponding weighted representation is associated with the service feature or the service trigger; and The service characteristic mentioned is at least one of low latency, high throughput, or low power, or The service trigger indicates the service characteristic.

5. The apparatus of claim 2, wherein, in order to initiate or maintain the connection with the cell, the at least one processor is configured individually or in any combination to: Before initiating or maintaining the connection, the cell is selected from a data structure maintained by the UE, wherein the cell is associated in the data structure with at least one of the absolute radio frequency channel number (ARFCN), time division duplex (TDD) indication, frequency division duplex (FDD) indication, or at least one of the measurements associated with the cell.

6. The apparatus of claim 5, wherein, in order to select the cell from the data structure maintained by the UE, the at least one processor is configured individually or in any combination to: The cells and at least one additional cell in the data structure maintained by the UE are reordered based on the combined metric and the QOE request; and The cell is selected from the data structure maintained by the UE after the cell and the at least one additional cell are reordered.

7. The apparatus of claim 2, wherein each of the at least one corresponding weighted representations is based on a first weighted value for the idle mode of the UE or a second weighted value for the connected mode of the UE.

8. The apparatus of claim 7, wherein the first weighting value comprises a positive weighting value associated with at least one of the RSRP or the number of layers that satisfies the throughput threshold, or a negative weighting value associated with at least one of the RSRP or the number of layers that fails to satisfy the throughput threshold.

9. The apparatus of claim 7, wherein the first weighting value includes a positive weighting value associated with the potential delay that satisfies the delay threshold, or a negative weighting value associated with the potential delay that fails to satisfy the delay threshold.

10. The apparatus of claim 7, wherein the service characteristic is at least one of low latency, high throughput, or low power. The first weighted value includes a positive weighted value associated with the service characteristic that meets the characteristic threshold, or a negative weighted value associated with the service characteristic that fails to meet the characteristic threshold.

11. The apparatus of claim 7, wherein the second weighting value comprises a positive weighting function associated with at least one of the RSRP or the number of layers that satisfies the throughput threshold, or a negative weighting function associated with at least one of the RSRP or the number of layers that fails to satisfy the throughput threshold.

12. The apparatus of claim 7, wherein the second weighting value comprises a negative weighting function associated with the potential delay that satisfies the delay threshold, or a positive weighting function associated with the potential delay that fails to satisfy the delay threshold.

13. The apparatus of claim 7, wherein the service characteristic is at least one of low latency, high throughput, or low power; The second weighting value includes a positive weighting function associated with the service characteristic that meets the characteristic threshold, or a negative weighting function associated with the service characteristic that fails to meet the characteristic threshold.

14. An apparatus for wireless communication at a network node, the apparatus comprising: At least one memory; and At least one processor, coupled to the at least one memory, and configured individually or in any combination, based at least in part on information stored in the at least one memory, to: Obtain a set of cell metrics associated with a cell for a user equipment (UE), wherein the set of cell metrics includes at least one of reference signal received power (RSRP) and potential delay, layer number, or service characteristics; as well as The UE initiates or maintains a connection to the cell associated with the UE based on a combined metric that meets a threshold condition, wherein the combined metric is based on the cell metric set.

15. The apparatus of claim 14, wherein, in order to obtain the cell metric set, the at least one processor is configured individually or in any combination to: The set of cell metrics is obtained from at least one of a Quality of Experience (QOE) request or at least one of at least one measurement associated with the cell; The combined metric is based on a set of cell metrics that use a combination of at least one of the RSRP and at least one of the potential delay, the number of layers, or the service characteristics.

16. The apparatus of claim 15, wherein the at least one processor is further configured, alone or in any combination, to: Before obtaining the cell metric set, the QOE request associated with the cell metric set is received from the network entity; and For the UE, and before initiating or maintaining the connection with the cell, an indication to the cell is sent based on the combined metric satisfying the threshold condition.

17. The apparatus of claim 16, wherein the QOE request indicates the service feature or service trigger, and wherein the at least one corresponding weighted representation is associated with the service feature or the service trigger; and The service characteristic mentioned is at least one of low latency, high throughput, or low power, or The service trigger indication is the service characteristic that is the default characteristic associated with the network entity.

18. The apparatus of claim 15, wherein, in order to initiate or maintain the connection with the cell, the at least one processor is configured individually or in any combination to: Before initiating or maintaining the connection, the cell is selected from a data structure maintained by the network node, wherein the cell is associated in the data structure with at least one of the absolute radio frequency channel number (ARFCN), time division duplex (TDD) indication, frequency division duplex (FDD) indication, or at least one of the measurements associated with the cell.

19. The apparatus of claim 18, wherein, in order to select the cell from the data structure maintained by the network node, the at least one processor is configured individually or in any combination to: The cells and at least one additional cell in the data structure maintained by the network node are reordered based on the combined metric and the QOE request; and The cell is selected from the data structure maintained by the network node after the cell and the at least one additional cell are reordered.

20. The apparatus of claim 15, wherein each of the at least one corresponding weighted representations is based on a first weighted value for the idle mode of the UE or a second weighted value for the connected mode of the UE.

21. The apparatus of claim 20, wherein the first weighting value comprises a positive weighting value associated with at least one of the RSRP or the number of layers that satisfies the throughput threshold, or a negative weighting value associated with at least one of the RSRP or the number of layers that fails to satisfy the throughput threshold.

22. The apparatus of claim 20, wherein the first weighting value includes a positive weighting value associated with the potential delay that satisfies the delay threshold, or a negative weighting value associated with the potential delay that fails to satisfy the delay threshold.

23. The apparatus of claim 20, wherein the service characteristic is at least one of low latency, high throughput, or low power; The first weighted value includes a positive weighted value associated with the service characteristic that meets the characteristic threshold, or a negative weighted value associated with the service characteristic that fails to meet the characteristic threshold.

24. The apparatus of claim 20, wherein the second weighting value comprises a positive weighting function associated with at least one of the RSRP or the number of layers that satisfies the throughput threshold, or a negative weighting function associated with at least one of the RSRP or the number of layers that fails to satisfy the throughput threshold.

25. The apparatus of claim 20, wherein the second weighting value comprises a negative weighting function associated with the potential delay that satisfies the delay threshold, or a positive weighting function associated with the potential delay that fails to satisfy the delay threshold.

26. The apparatus of claim 20, wherein the service characteristic is at least one of low latency, high throughput, or low power; The second weighting value includes a positive weighting function associated with the service characteristic that meets the characteristic threshold, or a negative weighting function associated with the service characteristic that fails to meet the characteristic threshold.

27. A method for conducting wireless communication at a user equipment (UE), the method comprising: Obtain a set of cell metrics associated with the UE, wherein the set of cell metrics includes at least one of reference signal received power (RSRP) and potential delay, layer number, or service characteristics; as well as A connection to the cell associated with the UE is initiated or maintained based on a combined metric that meets a threshold condition, wherein the combined metric is based on the set of cell metrics.

28. The method of claim 27, wherein obtaining the cell metric set comprises: The set of cell metrics is obtained from at least one of a Quality of Experience (QOE) request or at least one of at least one measurement associated with the cell; The combined metric is based on a set of cell metrics that use a combination of at least one of the RSRP and at least one of the potential delay, the number of layers, or the service characteristics.

29. A method for wireless communication at a network node, the method comprising: Obtain a set of cell metrics associated with a cell for a user equipment (UE), wherein the set of cell metrics includes at least one of reference signal received power (RSRP) and potential delay, layer number, or service characteristics; as well as The UE initiates or maintains a connection to the cell associated with the UE based on a combined metric that meets a threshold condition, wherein the combined metric is based on the cell metric set.

30. The method of claim 29, wherein obtaining the cell metric set comprises: The set of cell metrics is obtained from at least one of a Quality of Experience (QOE) request or at least one of at least one measurement associated with the cell; The combined metric is based on a set of cell metrics that use a combination of at least one of the RSRP and at least one of the potential delay, the number of layers, or the service characteristics.

Images