Techniques for facilitating quality of experience enhancements for high mobility scenarios
By dynamically adjusting QoE configuration and reporting using HSDN status and UE mobility conditions in wireless communication systems, the problem of unstable communication quality of 5G NR technology in high mobility scenarios is solved, and resource utilization efficiency and targeted QoE are improved.
Patent Information
- Application Number
- CN202280095234.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-04-29
- Publication Date
- 2024-12-03
AI Technical Summary
The existing 5G NR technology is difficult to effectively manage the quality of experience (QoE) of user equipment (UE) under different mobility conditions in high mobility scenarios, resulting in unstable communication quality and low resource utilization efficiency.
By introducing high-speed private network (HSDN) status and UE mobility conditions in wireless communication systems, dynamically adjusting QoE configuration, collecting and reporting QoE information, ensuring that QoE measurement and reporting are distinguished between HSDN cells and non-HSDN cells, and improving targetedness and efficiency.
It improves communication quality and resource utilization efficiency in high mobility scenarios, ensures the targetedness and accuracy of QoE, and is suitable for UEs under different mobility conditions.
Smart Images

Figure CN119072941A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates generally to communication systems, and more particularly to wireless communication systems utilizing mobility management. Background Art
[0002] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. 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 telecommunication standards to provide a common protocol that enables different wireless devices to communicate at city, country, region, and even global levels. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third 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 communication (mMTC), and ultra-reliable low latency communication (URLLC). Certain aspects of 5G NR may be based on 4G Long Term Evolution (LTE) standards. It is necessary to further improve 5G NR technology. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention
[0004] The following presents a summary of the invention of one or more aspects in order to provide a basic understanding of these aspects. This summary of the invention is not an extensive review of all envisioned aspects. This summary of the invention neither identifies the key or important elements of all aspects, nor describes the scope of any or all aspects. Its only purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.
[0005] In one aspect of the present disclosure, a method, computer readable medium, and apparatus for wireless communication are provided. An apparatus may include a user equipment (UE). The example apparatus receives a quality of experience (QoE) configuration associated with a high-speed dedicated network (HSDN) indication from a network node. The apparatus collects QoE information based on at least one of a HSDN state of a cell or a mobility condition of the UE.
[0006] In another aspect of the present disclosure, a method, a computer-readable medium, and an apparatus for wireless communication are provided. An apparatus may include a network entity or a network node, such as a base station. The example apparatus obtains a QoE configuration associated with an HSDN indication from a core network component. The apparatus outputs a QoE configuration for a UE based on the UE being camped on a HSDN cell or based on a mobility condition of the UE.
[0007] In another aspect of the present disclosure, a method, a computer-readable medium, and an apparatus for wireless communication are provided. An apparatus may include a network entity or a network node, such as a base station. The example apparatus obtains information as a target cell in handover for a UE configured with a QoE configuration associated with an HSDN indication. The apparatus releases the QoE configuration for the UE.
[0008] In another aspect of the present disclosure, methods, computer-readable media, and apparatus for wireless communications are provided. An apparatus may include a network entity or network node, such as a base station. The example apparatus obtains a QoE configuration associated with an HSDN indication from a core network component. The apparatus outputs the QoE configuration to at least one UE, receives QoE information from the at least one UE, and reports QoE information to the core network component for each of the at least one UE, the QoE information including an indication of at least one of an association with a HSDN cell or a high mobility condition of the at least one UE.
[0009] To achieve the aforementioned and related purposes, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some exemplary features of one or more aspects. However, these features indicate only some of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS
[0010] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.
[0011] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.
[0012] Figure 2B is a diagram illustrating an example of DL channels within a subframe according to various aspects of the present disclosure.
[0013] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.
[0014] Figure 2D is a diagram illustrating an example of UL channels within a subframe according to various aspects of the present disclosure.
[0015] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.
[0016] Figure 4 An environment including a UE communicating with different network nodes is illustrated.
[0017] Figure 5 Example scenarios of HSDN capable UEs and non-HSDN capable UEs associated with high mobility and low mobility are illustrated.
[0018] Fig. 6A and Figure 6B Example aspects of UE mobility related to HSDN cells are illustrated.
[0019] Figure 7 An example environment is illustrated that facilitates providing QoE reporting in high mobility scenarios when a UE moves between different mobility scenarios.
[0020] Figure 8 An example communication flow including QoE configuration based on whether the UE is connected to the HSDN and / or is in a high mobility state is illustrated.
[0021] Fig. 9 An example communication flow including QoE configuration based on whether the UE is connected to the HSDN and / or is in a high mobility state is illustrated.
[0022] Fig.10 An example communication flow including QoE configuration related to the mobility of the UE is illustrated.
[0023] Fig.11 An example communication flow including QoE collection based on whether the UE is connected to the HSDN and / or is in a high mobility state is illustrated.
[0024] Fig.12 An example communication flow including QoE reporting based on whether the UE is connected to the HSDN and / or is in a high mobility state is illustrated.
[0025] Fig.13 An example communication flow including filtering QoE reports at a network is illustrated.
[0026] Fig.14 An example environment is illustrated that facilitates providing QoE reporting in high mobility scenarios when a UE moves between different mobility scenarios.
[0027] Fig.15A and Fig. 15B is a flow chart of a method of wireless communication.
[0028] Fig.16is a diagram illustrating an example of a hardware implementation for an example apparatus and / or UE.
[0029] Fig.17A and Fig. 17B is a flow chart of a method of wireless communication.
[0030] Fig.18 is a flow chart of a method of wireless communication.
[0031] Fig.19 is a flow chart of a method of wireless communication.
[0032] Fig. 20 is a diagram illustrating an example of a hardware implementation for an example network entity. DETAILED DESCRIPTION
[0033] Devices in a wireless communication system may have different mobility states. The same device may have different mobility states and different times. Examples of mobility states include normal mobility states, high mobility states (such as UE traveling on a high-speed train), and medium mobility states. In some aspects, one or more high-speed dedicated networks (HSDNs) may be provided for communicating with devices in high mobility states. The UE may be configured to provide QoE information to the network. The QoE of the UE may be affected by the type of cell (e.g., HSDN or non-HSDN) on which the UE performs QoE measurements and / or the mobility conditions of the UE. The various aspects given herein enable the collection and / or reporting of QoE information to be improved, and may enable more targeted information to be provided to the network. In some aspects, the network node may help obtain targeted QoE information by configuring the UE with a QoE configuration based on the UE residing on a HSDN cell, and not configuring the UE residing on a non-HSDN cell with a QoE configuration. This enables QoE measurement collection to be performed on HSDN cells instead of non-HSDN cells. In some aspects, a network node may provide a QoE configuration to a UE, regardless of whether the UE is camped on a HSDN cell or a non-HSDN cell. The UE may perform QoE measurements on a HSDN cell instead of a non-HSDN cell. In some aspects, the UE may provide QoE information to the network without distinguishing between HSDN cells and non-HSDN cells, and a wireless area network (RAN) may filter the QoE information reported by the UE to provide network components such as a measurement collection entity (MCE) with QoE information for HSDN cells instead of for non-HSDN cells.
[0034] A QoE configuration may be "set" or may be "released". When a QoE configuration is set, the QoE configuration is in an active state, and the UE may perform QoE collection (e.g., measure, calculate, and / or determine QoE information, which may also be referred to as "QoE metrics", "QoE measurements", or any other suitable name) according to the QoE configuration. When a QoE configuration is released, the QoE configuration is in an inactive state, and the UE may skip performing QoE collection of QoE information. For example, when the UE resides on a HSDN cell, the network node may set (e.g., activate) the QoE configuration, and when the UE resides on a non-HSDN cell, the network node may release (e.g., deactivate) the QoE configuration. In some examples, when the QoE configuration is set, the QoE configuration remains active until the QoE configuration is released. For example, a first cell may set a QoE configuration at the UE, and when the UE moves to a different cell, the UE may continue to perform QoE collection based on the QoE configuration until the second cell releases the QoE configuration. In some examples, when the network node is described as releasing the QoE configuration, the network node may send signaling to the UE to deactivate the QoE configuration at the UE. In some examples, when the UE is described as releasing the QoE configuration, the UE may stop performing QoE collection.
[0035] Information related to the mobility of the UE may be beneficial to the MCE, as different mobilities may be associated with different QoE levels. By having the UE or RAN report QoE information specific to the HSDN cell, the MCE may be helped to consider the QoE provided to the UE.
[0036] The specific embodiments described below in conjunction with the accompanying drawings are descriptions of various configurations and do not represent the only configurations in which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments 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.
[0037] Several aspects of telecommunication systems are presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.
[0038] As an example, an element or any part of an element or any combination of elements can be implemented as a "processing system", which includes one or more processors. The example of a processor includes a microprocessor, a microcontroller, a graphics processing unit (GPU), a central processing unit (CPU), an application processor, a digital signal processor (DSP), a reduced instruction set computing (RISC) processor, a system on a chip (SoC), a baseband processor, a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, a gate logic part, a discrete hardware circuit and other suitable hardware configured to perform various functions described throughout the present disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other terms, software should be broadly interpreted as meaning an instruction, an instruction set, a code, a code segment, a program code, a program, a subroutine, a software component, an application, a software application, a software package, a routine, a subroutine, an object, an executable, a thread of execution, a process, a function or any combination thereof.
[0039] Thus, 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 codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available media that can be accessed by a computer. For example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.
[0040] Although various aspects, specific implementations and / or use cases are described in this application by the illustration of some examples, additional or different aspects, specific implementations and use cases may be generated in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, various aspects, specific implementations and / or use cases can be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, devices that enable artificial intelligence (AI), etc.). Although some examples may or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Various aspects, specific implementations and / or use cases can be in the range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed or original equipment manufacturer (OEM) equipment or systems in conjunction with one or more technologies herein. In some actual settings, the equipment combined with the various aspects and features described may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include several components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The various techniques described herein can be practiced in a wide variety of devices of various sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, clustered or disaggregated components, end-user devices, etc.
[0041] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station (BS), or one or more units (or one or more components) that perform base station functionality) can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.
[0042] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).
[0043] Base station operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configuration such as that initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.
[0044] Figure 1 100 is a diagram illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a decomposed base station architecture. The decomposed base station architecture may include one or more CUs (e.g., CU 110), which may communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more decomposed base station units (such as a near real-time (near RT) RAN intelligent controller (RIC) (e.g., near RT RIC 125) via an E2 link, or a non-real-time (non-RT) RIC (e.g., non-RT RIC 115) associated with a service management and orchestration (SMO) framework (e.g., SMO framework 105), or both. CU 110 may communicate with one or more DUs (e.g., DU 130) via corresponding midhaul links (such as F1 interfaces). DU 130 may communicate with one or more RUs (e.g., RU 140) via corresponding fronthaul links. RU 140 may communicate with corresponding UEs (e.g., UE 104) via one or more radio frequency (RF) access links. In some implementations, UE 104 may be served by multiple RUs simultaneously.
[0045] Each of the units (i.e., CU (e.g., CU 110), DU (e.g., DU 130), RU (e.g., RU 140), and near-RT RIC (e.g., near-RT RIC 125), non-RT RIC (e.g., non-RT RIC 115), and SMO framework 105) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interfaces of these units may be configured to communicate with one or more of the other units via the transmission medium. For example, these units may include a wired interface configured to receive signals or transmit signals to one or more of the other units via the wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as an RF transceiver) configured to receive and / or transmit signals to one or more of the other units via a wireless transmission medium.
[0046] In some aspects, CU 110 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented as having an interface configured to communicate signals with other control functions hosted by CU 110. CU110 may be configured to handle user plane functions (i.e., central unit-user plane (CU-UP)), control plane functions (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 110 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 110 may be implemented to communicate with DU 130 for network control and signaling.
[0047] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs. In some aspects, DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to functional splits (such as those defined by 3GPP). In some aspects, DU 130 may also host one or more low PHY layers. Each layer (or module) may be implemented with an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.
[0048] Lower layer functionality may be implemented by one or more RUs. In some deployments, the RU 140 controlled by the DU 130 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.) or both based at least in part on functional splitting (such as lower layer functional splitting). In this architecture, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs (e.g., UE 104). In some specific implementations, the real-time and non-real-time aspects of the control plane and user plane communications with the RU 140 may be controlled by the corresponding DU. In some scenarios, this configuration may enable the DU and CU 110 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).
[0049] The SMO framework 105 may be configured to support RAN deployment and provision of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU, DU, RU, and near-RT RIC. In some specific implementations, the SMO framework 105 may communicate with hardware aspects of the 4G RAN such as an open eNB (O-eNB) 111 via the O1 interface. Additionally, in some specific implementations, the SMO framework 105 may communicate directly with one or more RUs via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105.
[0050] The non-RT RIC 115 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 115 may be coupled to or in communication with the near-RT RIC 125 (such as via an A1 interface). The near-RT RIC 125 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs, one or more DUs, or both, and the O-eNB with the near-RT RIC 125.
[0051] In some implementations, in order to generate an AI / ML model 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. Such information may be utilized by the near-RT RIC 125 and may be received from a non-network data source or from a network function at the SMO framework 105 or the non-RT RIC 115. In some examples, the non-RT RIC 115 or the near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 105 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).
[0052] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Therefore, the base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component is indicated by a dotted line to indicate that each component may be included in the base station 102 or may not be included in the base station). The base station 102 provides an access point to the core network 120 for the UE 104. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link between a RU (e.g., RU 140) and a UE (e.g., UE 104) may include an uplink (UL) (also referred to as a reverse link) transmission from UE 104 to RU 140 and / or a downlink (DL) (also referred to as a forward link) transmission from RU 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be through one or more carriers. For each carrier allocated in a carrier aggregation of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.) bandwidth. The carriers may be adjacent to each other or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). The component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).
[0053] Certain UEs may communicate with each other using device-to-device (D2D) communications (e.g., D2D communication links 158). D2D communication links 158 may use DL / UL wireless wide area network (WWAN) spectrum. D2D communication links 158 may use one or more side link channels, such as a physical side link broadcast channel (PSBCH), a physical side link discovery channel (PSDCH), a physical side link shared channel (PSSCH), and a physical side link control channel (PSCCH). D2D communications may be performed via a variety of wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi, LTE, or NR based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard.
[0054] The wireless communication system may also include a Wi-Fi AP 150 that communicates with a UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in a 5 GHz unlicensed spectrum, etc. When communicating in an unlicensed spectrum, the UE 104 / Wi-Fi AP 150 may perform a clear channel assessment (CCA) to determine whether a channel is available prior to communication.
[0055] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).
[0056] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6GHz-71GHz), FR4 (71GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.
[0057] In view of the above, unless otherwise specified, if the term "6 GHz or less" is used herein, it may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specified, if the term "millimeter wave" is used herein, it may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.
[0058] The base station 102 and the UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. The base station 102 may send a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also send a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of the base station 102 / UE 104. The transmit direction and receive direction of the base station 102 may be the same or different. The transmit direction and receive direction of the UE 104 may be the same or different.
[0059] The base station 102 may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), a network node, a network entity, a network equipment, or some other suitable term. The base station 102 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, a clustered (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and a RU, or as a decomposed base station including one or more of a CU, a DU, and / or a RU. A set of base stations that may include a decomposed base station and / or a clustered base station may be referred to as a next generation (NG) RAN (NG-RAN).
[0060] The core network 120 may include an access and mobility management function (AMF) (e.g., AMF 161), a session management function (SMF) (e.g., SMF 162), a user plane function (UPF) (e.g., UPF 163), a unified data management (UDM) (e.g., UDM 164), one or more location servers 168, and other functional entities. The AMF 161 is a control node that handles signaling between the UE 104 and the core network 120. The AMF 161 supports registration management, connection management, mobility management, and other functions. The SMF 162 supports session management and other functions. The UPF 163 supports packet routing, packet forwarding, and other functions. The UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. The one or more location servers 168 are illustrated as including a gateway mobile location center (GMLC) (e.g., GMLC 165) and a location management function (LMF) (e.g., LMF 166). However, in general, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, the LMF 166, the position determination entity (PDE), the serving mobile location center (SMLC), the mobile positioning center (MPC), etc. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. The LMF 166 receives measurements and assistance information from the NG-RAN and the UE 104 via the AMF 161 to calculate the location of the UE 104. The NG-RAN may determine the location of the UE 104 using one or more positioning methods. Positioning the UE 104 may involve signal measurements, position estimation, and optional speed calculations based on these measurements. Signal measurements may be performed by the UE 104 and / or a serving base station (e.g., base station 102). The measured signals may be based on a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / positioning systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR enhanced cell ID (NR E-CID) method, NR signals (e.g., multi-round trip time (multi-RTT), DL angle of departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning), and / or one or more of other systems / signals / sensors.
[0061] Examples of UE include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare equipment, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, user agents, mobile clients, clients, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more supporting devices, such as in a device constellation arrangement. One or more of these devices may access a network together and / or individually.
[0062] See again Figure 1In certain aspects, a device such as a UE 104 communicating with a base station may be configured to manage one or more aspects of wireless communication by facilitating QoE improvements for high mobility scenarios. For example, the UE 104 may include a QoE signaling component 198 configured to receive a QoE configuration associated with a HSDN indication from a network node and collect QoE information based on at least one of a HSDN state of a cell or a mobility condition of the UE. A network node such as a base station 102 or a component of a base station such as a CU 110, a DU 130, and / or a RU 140 may include a QoE configuration component 199. In some aspects, the QoE configuration component 199 may be configured to obtain a QoE configuration associated with a HSDN indication from a core network component and output a QoE configuration for the UE based on the UE camping on a HSDN cell or based on the mobility condition of the UE. In some aspects, the QoE configuration component 199 may be configured to obtain information as a target cell in handover for a UE configured with a QoE configuration associated with a HSDN indication, and release the QoE configuration for the UE. In some aspects, the QoE configuration component 199 may be configured to obtain a QoE configuration associated with the HSDN indication from a core network component, output the QoE configuration to at least one UE, receive QoE information from at least one UE, and report QoE information to the core network component for each of the at least one UE, the QoE information including an indication of at least one of an association with a HSDN cell or a high mobility condition of the at least one UE. Although the following description provides examples involving 5G NR, the concepts described herein may be applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM, and / or other wireless technologies.
[0063] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2D FIG280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL, or may be time division duplex (TDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL. Figure 2A , Figure 2CIn the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are both DL and both UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. The slot format is configured for the UE via a 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.
[0064] FIG. 2A to FIG. 2D The frame structure is illustrated, and various aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 subframes (1ms) of the same size. Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4 or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For a normal CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 12 symbols. The symbol on the DL may be a CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbol (also known as a single carrier frequency division multiple access (SC-FDMA) symbol) (for power-limited scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and parameter set. The parameter set defines the subcarrier spacing (SCS) and effectively defines the symbol length / duration, which is equal to 1 / SCS.
[0065]
[0066] For normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Thus, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ timeslots / subframe. The subcarrier spacing can be equal to 2 μ*15kHz, where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=4 is 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example is provided for a normal CP with 14 symbols per slot and a parameter set μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is about 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP may have a specific parameter set and CP (normal or extended).
[0067] A resource grid may be used to represent a frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.
[0068] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) (indicated as R for a particular configuration, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).
[0069] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on a CORESET, wherein 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. A primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. A secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the system frame number (SFN) and the number of RBs in the system bandwidth. The physical downlink shared channel (PDSCH) carries user data, broadcast system information such as system information blocks (SIBs) that are not sent via the PBCH, and paging messages.
[0070] like Figure 2C As illustrated, some of the REs carry DM-RS (indicated as R for a particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send a DM-RS for a physical uplink control channel (PUCCH) and a DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS may be sent in different configurations. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the comb structures in the comb structure. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.
[0071] Figure 2DExamples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.
[0072] Figure 3 is a block diagram illustrating an example of a first wireless device configured to exchange wireless communications with a second wireless device. Figure 3 In the illustrated example of , the first wireless device may include a base station 310, the second wireless device may include a UE 350, and the base station 310 may communicate with the UE 350 in an access network. Figure 3 As shown, base station 310 includes a transmit processor (TX processor 316), a transmitter 318Tx, a receiver 318Rx, an antenna 320, a receive processor (RX processor 370), a channel estimator 374, a controller / processor 375, and a memory 376. Example UE 350 includes antenna 352, a transmitter 354Tx, a receiver 354Rx, an RX processor 356, a channel estimator 358, a controller / processor 359, a memory 360, and a TX processor 368. In other examples, base station 310 and / or UE 350 may include additional or alternative components.
[0073] In the DL, Internet Protocol (IP) packets may be provided to the controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functions. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functions associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functions associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.
[0074] The TX processor 316 and the RX processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), 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 an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially pre-coded to generate multiple spatial streams. Channel estimates from channel estimator 374 may be used to determine coding and modulation schemes and for spatial processing. Channel estimates may be derived from reference signals and / or channel state feedback sent by UE 350. Each spatial stream may then be provided to a different antenna in antenna 320 via a separate transmitter (e.g., transmitter 318Tx). Each transmitter 318Tx may modulate a radio frequency (RF) carrier for transmission using a corresponding spatial stream.
[0075] At the UE 350, each receiver 354Rx receives a signal through its corresponding antenna in the antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to the RX processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If multiple spatial streams are destined for the UE 350, two or more of the multiple spatial streams can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbol on each subcarrier and the reference signal are recovered and demodulated by determining the most likely signal constellation point sent by the base station 310. These soft decisions can be based on the channel estimate calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by base station 310. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functions.
[0076] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.
[0077] Similar to the functions described in conjunction with DL transmission performed by the base station 310, the controller / processor 359 provides RRC layer functions associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functions associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.
[0078] Channel estimates derived by the channel estimator 358 from a reference signal or feedback sent by the base station 310 may be used by the TX processor 368 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different ones of the antennas 352 via separate transmitters (e.g., transmitter 354Tx). Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.
[0079] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318Rx receives a signal through its corresponding one of the antennas 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 370.
[0080] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.
[0081] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 The QoE signaling component 198 combines various aspects.
[0082] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to combine Figure 1 The QoE configuration component 199 is used to perform various aspects.
[0083] The UE may collect (e.g., measure, calculate, and / or determine) QoE metrics for one or more cells serving the UE. The metrics may evaluate how services facilitated by the UE are performed based on wireless communications with the cells. Examples of services include augmented reality (AR) services, mixed reality (MR) services, and multicast broadcast services (MBS). For example, a UE executing a VR application may collect metrics associated with the execution of the VR application. Example metrics may indicate whether the VR application is experiencing jitter, buffering, lag, etc. The metrics may then be evaluated to provide a quality of experience (QoE) associated with the VR application.
[0084] Various aspects disclosed herein provide techniques for providing QoE for high mobility scenarios. Examples of high mobility scenarios include UEs traveling at high speeds, such as on a high speed train (HST), or on a highway. When a UE is in a high mobility scenario, the UE may enter and leave a cell provided by a base station at high speed, and may therefore perform relatively frequent handovers (e.g., cell reselection procedures) between base stations. A high speed dedicated network (HSDN) is a network configured to serve UEs in high mobility scenarios. As used herein, the term "HSDN" may refer to a high speed dedicated network and / or a non-terrestrial network (NTN), in which a UE may be connected to a highly mobile satellite for a certain duration. In some examples in which a UE is connected to an NTN, the UE may be connected to a satellite for a short duration, but the communication may have a high Doppler.
[0085] The HSDN may be configured with one or more aspects to provide coverage to UEs in high mobility scenarios. For example, for cell reselection of a UE that is in a high mobility state and has the ability to connect to the HSDN (e.g., a HSDN capable UE), a cell serving the HSDN (e.g., a HSDN cell) may be associated with a higher priority than other cells.
[0086] In some aspects, a HSDN capable UE may or may not be configured to perform cell reselection while operating in an idle state ("RRC_IDLE") or an inactive state ("RRC_INACTIVE").
[0087] A cell may provide a 1-bit indication in a system information block (SIB) message (e.g., a "SIB1" message) to indicate that the cell is a HSDN cell. A HSDN cell may also be referred to as a "NR HSDN cell". A HSDN cell may also provide information about HSDN neighbor cells via corresponding SIBs for intra-frequency reselection, inter-frequency reselection, and / or inter-RAT reselection. A HSDN cell may provide information about HSDN neighbor cells in a HSDN neighbor cell list with a physical cell identity (PCI).
[0088] A UE with HSDN capability may perform cell reselection based on its mobility state. For example, a UE in a high mobility state may consider a HSDN cell to be the highest priority, such as higher than any other network configured priority. A UE not in a high mobility state (e.g., in a normal mobility state or a medium mobility state) may consider a HSDN cell to be the lowest priority, such as lower than the network configured priority.
[0089] The HSDN cell may provide one or more mobility state parameters that enable the UE to estimate the mobility state of the UE, for example, from a set of possible mobility states. Exemplary mobility states of the UE include "normal mobility state", "high mobility state" and "medium mobility state". The serving cell may broadcast one or more of the mobility state parameters via a SIB (such as a "SIB2" message). Examples of mobility state parameters include a duration parameter, a medium mobility state threshold, a high mobility state threshold, an additional period parameter and a cell count. The duration parameter (which may be referred to as a "TCRmax" parameter or any other name) indicates the duration for evaluating the allowed amount of cell reselection. The medium mobility state threshold, which may be referred to as an "NCR_M" parameter or any other name, indicates the maximum number of cell reselections entering the medium mobility state. The high mobility state threshold, which may be referred to as an "NCR_H" parameter or any other name, indicates the maximum number of cell reselections entering the high mobility state. The additional period parameter, which may be referred to as a "TCRmaxHyst" parameter or any other name, indicates an additional time period before the UE can enter the normal mobility state. The cell count parameter (which may be referred to as a "cellEquivalentSize" parameter or any other name) indicates the cell count number associated with the serving HSDN cell.
[0090] To determine its mobility state, the UE may default to a normal mobility state and determine the number of cell reselections. In an example where the UE is configured with a cellEquivalentSize parameter, the UE may use the number indicated by the cellEquivalentSize parameter as the number of cell reselections. Wherein in an example where the UE is not configured with a cellEquivalentSize parameter, the UE may count the number of cell reselections performed during a certain period of time based on the TCRmax parameter. When the number of cell reselections exceeds a medium mobility state threshold as indicated by the NCR_M parameter and does not exceed a high mobility state threshold as indicated by the NCR_H parameter, the UE may determine that it is in a medium mobility state. When the number of cell reselections exceeds a high mobility state threshold, the UE may determine that it is in a high mobility state, as indicated by the NCR_H parameter.
[0091] After determining its mobility state, the UE may enter the corresponding mobility state. For example, if criteria for a high mobility state are detected, the UE may enter the high mobility state, for example, by adjusting behaviors such as cell selection parameters or prioritization based on the mobility state determined for the UE. If criteria for a high mobility state are not detected and criteria for a medium mobility state are detected, the UE may enter the medium mobility state. If criteria for a high mobility state or a medium mobility state are not detected during an additional period as indicated by a TCRmaxHyst parameter, the UE may enter a normal mobility state. In some examples, when the UE is in a high mobility state or a medium mobility state, the UE may apply one or more speed-related scaling rules to measurements performed by the UE. For example, based on the mobility state of the UE, the UE may apply a speed-related scaling factor to an event timing parameter. Examples of speed-dependent scaling factors may include scaling factors for Qhyst (e.g., including scaling factors for high mobility states and scaling factors for medium mobility states), one or more reselection time scaling factors for one or more RATs (e.g., for one or more of NR such as "Treselection NR", EUTRA such as "Treselection EUTRA", UTRA such as "TreselectionUTRA", etc., a scaling factor for high mobility states and a scaling factor for medium mobility states). An event timing parameter, which may be referred to as a "timeToTrigger parameter" or any other name, may indicate a time during which a measurement report may be triggered when specific criteria for an event are met.
[0092] As an example of scaling factor application, if the UE is not in a medium or high mobility state, the UE may not apply scaling. If a high or medium mobility state is detected for the UE, the UE may add the corresponding scaling factor to Qhyst if transmitted on system information. For E-UTRAN, UTRAN, GERAN, CDMA2000 HRPD, CDMA2000 1xRTT or NR cells, the UE may multiply TreselectionRAT by the corresponding speed-dependent and RAT-dependent scaling factors if transmitted on system information. If scaling is applied, the UE may round the result up to the nearest second after scaling.
[0093] The network may provide the UE with information about the HSDN cell. As an example, the system information block may carry information indicating whether the cell is a HSDN cell, a cell equivalent size (e.g., the number of cell counts used for mobility state estimation of the cell), cell reselection information, intra-frequency neighboring HSDN cell information (e.g., a list of intra-frequency neighboring HSDN cells), a HSDN indication indicating whether there is a deployed HSDN cell on the downlink frequency indicated by the corresponding downlink carrier frequency parameter, and inter-frequency neighboring HSDN information (e.g., a list of inter-frequency neighboring HSDN cells).
[0094] In some aspects, if the received measurement configuration (e.g., which may be referred to as "measConfig") includes a speed state parameter (which may be referred to as "speedStatePars"), the parameter speedStatePars within the measurement configuration (which may be referred to as "VarMeasConfig") may be set to the received value of speedStatePars. The UE may adjust the value of the timeToTrigger parameter configured by the E-UTRAN based on the UE speed. The UE may apply 3 different levels between which to select. The UE may perform mobility state detection using mobility state detection with the following modifications: counting handovers instead of cell reselection; applying parameters applicable to RRC connected UEs as included in speedStatePars within VarMeasConfig. If a high mobility state is detected, the UE may use the timeToTrigger value multiplied by sf-High within VarMeasConfig. If a medium mobility state is detected, the UE may use the timeToTrigger value multiplied by sf-Medium within VarMeasConfig. Otherwise, the UE may not apply scaling.
[0095] Figure 4 An environment 400 including a UE communicating with different network nodes is illustrated, as presented herein. Figure 4In the illustrated example, environment 400 includes non-HSDN cell 410 and HSDN cell 420. These cells may be associated with physical cell identifiers (PCIs). For example, non-HSDN cell 410 may be associated with a first PCI ("PCI1"), while HSDN cell 420 may be associated with a second PCI ("PCI2"). Figure 4 4. Although not shown in the example of , a non-HSDN cell may be served by a non-HSDN network node and a HSDN cell may be served by a HSDN network node. Although a non-HSDN cell is illustrated as having a hexagonal shape and a HSDN cell is illustrated as having a rectangular shape, in other examples, the coverage area associated with a non-HSDN cell 410 and / or a HSDN cell 420 may be associated with a different shape.
[0096] like Figure 4 As shown, the non-HSDN cell 410 includes a first UE 404 ("UE1"), a second UE 406 ("UE2"), and a vehicle 408. The first UE 404 and the second UE 406 may camp on the non-HSDN cell 410. Figure 4 In the example of , the first UE 404 is located outside the vehicle 408, and the second UE 406 is located in the vehicle 408. The vehicle 408 can be stationary, can move at a low speed, or can move at a high speed. Therefore, the mobility state associated with the second UE 406 can be based on whether the vehicle 408 is stationary and the speed at which the vehicle 408 is traveling.
[0097] Figure 4 The HSDN cell 420 includes a third UE 422 ("UE3"), a fourth UE 424 ("UE4"), and an HST 426. Figure 4 As shown, the third UE 422 is located outside of the HST 426, and the fourth UE 424 is in the HST 426. The HST 426 can be in a mobile state or in a stationary state. Therefore, the mobility state associated with the fourth UE 424 can be based on whether the HST 426 is in a mobile state or a stationary state.
[0098] exist Figure 4In the example of , each of the UEs can be associated with high mobility or low mobility. As used herein, the term "high mobility" can refer to a scenario in which the UE meets the criteria associated with being in a high mobility state (e.g., the number of cell reselections exceeds a high mobility state threshold, as indicated by the NCR_H parameter). The term "high mobility" can also refer to a scenario in which the UE is traveling with relatively low mobility but on a high-speed vehicle. For example, the vehicle 408 can travel at a relatively slow speed compared to the HST 426. In such a scenario, the second UE 406 can be stationary, but can be associated with high mobility or low mobility based on the speed of the vehicle 408. In some examples, the vehicle 408 can be deployed as a mobile IAB node.
[0099] Figure 5 Depicted is an example table 500 illustrating example scenarios for HSDN-capable UEs and non-HSDN-capable UEs associated with high mobility and low mobility, as presented herein. Figure 5 All aspects are combined Figure 4 4. The example environment 400 of the present invention is described. In the first set of scenarios, the UE may be a HSDN-capable UE 502, and in the second set of scenarios, the UE may be a non-HSDN-capable UE 504. Examples of HSDN-capable UE 502 may include a UE having the ability to communicate via HSDN, such as a UE configured to communicate when on HST. Examples of non-HSDN-capable UE 504 may include a UE that does not have the ability to communicate via HSDN, such as a pedestrian UE or a vehicle UE.
[0100] like Figure 5 As shown, HSDN-capable UE 502 and non-HSDN-capable UE 504 may be in different scenarios based on whether the respective UE is associated with high mobility or low mobility, and whether the respective UE is connected to a HSDN cell or a non-HSDN cell (sometimes referred to herein as a "legacy network"). For example, in a first scenario 510 ("Case 1a"), HSDN-capable UE 502 may be connected to a HSDN cell and traveling at a high speed, such as connected to a Figure 4 Example fourth UE 424 of HSDN cell 420. In the second scenario 512 ("Case 1b"), HSDN-capable UE 502 may be connected to a HSDN cell and traveling at a low speed, such as connected to Figure 4 In a third scenario 514 ("Case 1c"), a HSDN capable UE 502 may connect to a non-HSDN cell and travel at high speed, such as to a non-HSDN cell. Figure 4In a fourth scenario 516 ("Case 1d"), a HSDN-capable UE 502 may be connected to a non-HSDN cell and traveling at a low speed, such as a second UE 406 connected to a non-HSDN cell. Figure 4 An example first UE 404 of a non-HSDN cell 410 is shown.
[0101] In a fifth scenario 520 ("Case 2a"), a non-HSDN capable UE 504 may connect to a HSDN cell and travel at high speed, such as connecting to a Figure 4 In a sixth scenario 522 ("Case 2b"), a non-HSDN capable UE 504 may connect to a HSDN cell and travel at a low speed, such as connecting to a Figure 4 In a seventh scenario 524 ("Case 2c"), a non-HSDN capable UE 504 may connect to a non-HSDN cell and travel at high speed, such as connecting to a Figure 4 In an eighth scenario 526 ("Case 2d"), a non-HSDN capable UE 504 may connect to a non-HSDN cell and travel at a low speed, such as connecting to a Figure 4 An example first UE 404 of a non-HSDN cell 410 is shown.
[0102] Various aspects disclosed herein provide techniques for providing QoE for high mobility scenarios. In some examples, the high mobility scenario may be associated with a UE connected to a HSDN cell, such as the example first scenario 510 or the example fifth scenario 520. In some examples, the high mobility scenario may be associated with a UE connected to a non-HSDN cell, such as the example third scenario 514 or the example seventh scenario 524. However, in scenarios where the UE is connected to a HSDN cell and is associated with low mobility (e.g., the example second scenario 512 or the example sixth scenario 522) or the UE is connected to a non-HSDN cell and is associated with low mobility (e.g., the example fourth scenario 516 or the example eighth scenario 526), various aspects disclosed herein may also improve QoE reporting.
[0103] As described above, the HSDN may be configured with one or more aspects to provide coverage to UEs in high mobility scenarios. For example, the HSDN may provide aspects that improve handovers between network nodes when in high mobility scenarios. Fig. 6A and Figure 6B An example deployment is illustrated in which the UE 604 may perform handover procedures in the HSDN. Fig. 6AAn example environment 600 is illustrated in which a UE 604 may perform handover procedures between different HSDN cells, as presented herein. Fig. 6A In the example of , the first network node 612 may provide coverage to an area associated with a first HSDN cell 610 ("PCI1"), and the second network node 622 may provide coverage to an area associated with a second HSDN cell 620 ("PCI2").
[0104] like Fig. 6A As shown, UE 604 may travel on HST 602 and travel from first HSDN cell 610 to second HSDN cell 620. In such a scenario, UE 604 may perform handover procedures with first network node 612 and second network node 622 when traveling from first HSDN cell 610 to second HSDN cell 620.
[0105] Figure 6B An example environment 650 is illustrated in which a UE 604 can perform handover procedures between different network nodes of a HSDN cell, as presented herein. Figure 6B In an example of , the HSDN cell 660 ("PCI3") may be a single frequency network (SFN) in which two or more network nodes provide coverage to the HSDN cell 660 and transmit the same signal on the same frequency at the same time. For example, the HSDN cell 660 includes a first network node 662 and a second network node 664. Aspects of the first network node 662 and the second network node 664 may be implemented by corresponding remote radio heads (RRHs) or RUs. In the HSDN cell 660, the UE 604 may receive the same signal from different network nodes. For example, the first network node 662 and the second network node 664 may be configured to transmit the same signal that the UE 604 may receive. In such a scenario, the UE 604 may perform a handover procedure with the first network node 662 and the second network node 664 while traveling within the HSDN cell 660.
[0106] Figure 7 An example environment 700 is illustrated that facilitates providing QoE reporting in a high mobility scenario when a UE 702 moves between different mobility scenarios, as presented herein. Figure 7 In the example of FIG. 7 , UE 702 may be a UE with HSDN capability, such as Figure 5 HSDN capable UE 502. UE 702 may also be located in a high mobility capable vehicle, such as an HST or a vehicle traveling on a highway.
[0107] like Figure 7As shown, environment 700 provides coverage to UEs traveling on path 704, which may be a railroad track or a road. For example, at time T1, UE 702 may be connected to a first network node 712 that provides coverage to a first cell 710 ("PCI1"), at time T2, UE 702 may be connected to a second network node 722 that provides coverage to a second cell 720 ("PCI2"), at time T3, UE 702 may be connected to a third network node 732 that provides coverage to a third cell 730 ("PCI3"), and at time T4, UE 702 may be connected to a fourth network node 742 that provides coverage to a fourth cell 740 ("PCI4"). Figure 7 As shown, the first cell 710 and the second cell 720 are HSDN cells, and the third cell 730 and the fourth cell 740 are non-HSDN cells.
[0108] exist Figure 7 In the example of FIG. 7 , UE 702 may be associated with different mobilities when traveling from first cell 710 to fourth cell 740. For example, at time T1, UE 702 may be traveling at full speed and associated with high mobility when connected to a HSDN cell, such as in conjunction with Figure 5 As described in the first scenario 510 of FIG. 1 , at time T2, UE 702 may be traveling at a low speed and associated with low mobility when connected to a HSDN cell, as described in conjunction with FIG. Figure 5 As described in the second scenario 512 of FIG. 5 . At time T3, UE 702 may be traveling at full speed and associated with high mobility when connected to a non-HSDN cell, as described in conjunction with FIG. Figure 5 At time T4, UE 702 may be traveling at a low speed and associated with low mobility when connected to a non-HSDN cell, as described in conjunction with the third scenario 514. Figure 5 As described in the fourth scene 516.
[0109] exist Figure 7 In an example of , UE 702 provides a QoE measurement report received by a measurement collection entity (MCE) (e.g., MCE 750). MCE 750 may include a network entity configured to receive the QoE measurement report. The QoE measurement report (sometimes referred to as a "QoE report") may include application layer measurements associated with different services (such as streaming services, AR services, MR services, and / or MBS services) from UE 702.
[0110] When the UE 702 travels from the first cell 710 to the fourth cell 740, the UE 702 may provide different QoE measurement reports. For example, the UE 702 may provide a first QoE measurement report 714 when connected to the first cell 710 at time T1, may provide a second QoE measurement report 724 when connected to the second cell 720 at time T2, may provide a third QoE measurement report 734 when connected to the third cell 730 at time T3, and may provide a fourth QoE measurement report 744 when connected to the fourth cell 740 at time T4. The respective QoE measurement reports may include QoE metrics measured by the UE 702 at the respective times. Examples of QoE metrics may include buffering levels, media-initiated play delays, and the like.
[0111] However, while the QoE measurement report may provide information collected at the application layer, the QoE measurement report may not provide information related to the mobility of the UE 702. For example, the QoE measurement report may not include information indicating whether the UE 702 is connected to a HSDN network or a non-HSDN network. The QoE measurement may additionally or alternatively not include information indicating whether the UE 702 is associated with high mobility or low mobility. Information related to the mobility of the UE 702 may be beneficial to the MCE 750 because different mobilities may be associated with different QoE levels.
[0112] Various aspects disclosed herein provide techniques for improving QoE measurement reporting in high mobility scenarios. The UE may be configured to collect measurements and provide a QoE measurement report based on a QoE configuration. The QoE configuration may be configured such that the QoE measurement report provides an indication of whether the measurement is associated with the UE being connected to a HSDN cell or the UE being in high mobility. Based on the information provided in the QoE measurement report, the MCE may process the received QoE measurement report accordingly. Various aspects may enable the UE and / or RAN to filter the collection or reporting of QoE information so as to provide QoE information for HSDN cells but not for non-HSDN cells.
[0113] In some examples, when the UE is camped on a HSDN cell or is in high mobility, the network may provide the UE with a QoE configuration such as Figure 5 The first scenario 510, the second scenario 512 and / or the third scenario 514 of the present invention. The network may not configure the QoE configuration for the UE camping on the non-HSDN cell. In such network-based aspects, the UE may be configured to collect measurements and provide QoE measurement reports when connected to the HSDN cell or in high mobility, and thus, the MCE may process the received QoE measurement reports accordingly.
[0114] In some examples, the network may provide a QoE configuration to the UE regardless of whether the UE is camped on a HSDN cell or a non-HSDN cell, and regardless of whether the UE is in high mobility or low mobility, such as Figure 5 The first scenario 510, the second scenario 512, the third scenario 514 and / or the fourth scenario 516 of FIG. However, the QoE configuration may configure the UE to collect measurements when the UE is connected to a HSDN cell or is in high mobility. In such UE-based aspects, the UE may be configured to provide a QoE measurement report when connected to a HSDN cell or a non-HSDN cell.
[0115] In some examples, the network may provide a QoE configuration to the UE regardless of whether the UE is camped on a HSDN cell or a non-HSDN cell, and regardless of whether the UE is in high mobility or low mobility, such as Figure 5 The first scenario 510, the second scenario 512, the third scenario 514 and / or the fourth scenario 516 of the present invention are described in detail. In addition, the UE may be configured to collect measurements and provide a QoE measurement report regardless of the type of cell in which the UE resides and the mobility of the UE. However, the network may perform filtering of the QoE measurement report based on an indication included in the QoE measurement report. For example, the QoE measurement report received at the MCE may include an HSDN indication indicating whether the UE is connected to a HSDN cell or a non-HSDN cell. The QoE measurement report may also include a mobility state indication indicating the mobility state of the UE. In some examples, when generating the QoE measurement report, the UE may include an HSDN indication and / or a mobility state indication. In some examples, when forwarding the QoE report from the UE to the MCE, the network may attach an HSDN indication and / or a mobility state indication. In such post-processing-based aspects, the MCE may filter the received QoE report based on the HSDN indication and the mobility state indication.
[0116] In a post-processing based solution, the QoE measurement report received at the MCE may be configured, for example, via a QoE configuration, to include a HSDN indicator indicating whether the UE is connected to a HSDN cell or a non-HSDN cell. The HSDN indicator may be a 1-bit indicator, where a first value indicates that the UE is connected to a HSDN cell and a second value indicates that the UE is connected to a non-HSDN cell. In some examples, the QoE measurement report may be additionally or alternatively configured to include a mobility state indicator indicating a mobility state of the UE.
[0117] Figure 8An example communication flow 800 involving a UE 804, a network node 802, and core network components such as an AMF 808 and an MCE 806 is illustrated, wherein the network node may filter a QoE configuration for a UE camped on a HSDN cell or in a high mobility state. The network node 802 may correspond to a RAN or a component of a RAN. The network node 802 may correspond to a base station (such as a base station 102 or a base station 310) or a component of a base station (such as a CU 110, a DU 130, or a RU 140).
[0118] As illustrated, the MCE may transmit a signaling-based (S-based) QoE configuration (e.g., S-based QoE configuration 812) with a HSDN indication 809 and / or a mobility indication 811 to the AMF 808. The HSDN indication indicates that the QoE configuration is for QoE associated with a HSDN cell and / or with the mobility state of the UE. At 810, the network node 802 determines whether the UE 804 is connected to a HSDN cell or is in a high mobility state. Figure 8 As shown, the AMF 808 sends the S-based QoE configuration 814 to the network node 802 along with the HSDN indication 809 and / or the mobility indication 811. In some examples, the AMF 808 may forward the S-based QoE configuration 812 to the network node 802 as the S-based QoE configuration 814. For example, the network node 802 may obtain (e.g., receive) the S-based QoE configuration 814 from the AMF 808. The network node 802 then configures the QoE configuration to the UE 804 based on whether the UE is camped on a HSDN cell or if the UE 804 is in a high mobility condition (e.g., as determined at 810). For example, if the UE 804 is camped on a non-HSDN cell or is not in a high mobility condition, the network node 802 may not configure the QoE configuration for the UE 804. Figure 8As shown, the network node 802 outputs (e.g., sends or communicates) a QoE configuration 816 that is received by the UE 804. At 818, the UE 804 collects QoE measurements based on the QoE configuration 816. For example, the UE 804 can measure QoE information, calculate QoE information, and / or determine QoE information based on the QoE configuration 816. The UE 804 sends a QoE measurement report 820 with the collected QoE measurements to the network node 802. The network node 802 provides a QoE measurement report 822 to the AMF 808. The AMF 808 provides a QoE measurement report 824 to the MCE 806. When MCE 806 provides HSDN indication 809 and / or mobility indication 811 to QoE configuration (eg, s-based QoE configuration 812), MCE 806 may know that QoE measurement reports based on s-based QoE configuration 812 are for HSDN and / or for UEs in high mobility state.
[0119] If UE 804 connects to a non-HSDN cell and / or if the UE's mobility state changes to a lower mobility state, UE 804 may release the QoE configuration, as illustrated at 826. For example, UE 804 may release QoE configuration 816 received from network node 802.
[0120] Fig. 9 An example communication flow 900 involving a UE 904, a network node 902, and a core network component such as an MCE 906 is illustrated, wherein the network node may filter a QoE configuration for a UE camped on a HSDN cell or in a high mobility state. The network node 902 may correspond to a RAN or a component of a RAN. The network node 902 may correspond to a base station (such as a base station 102 or a base station 310) or a component of a base station (such as a CU 110, a DU 130, or a RU 140).
[0121] As illustrated, the MCE 906 may output (eg, send or communicate) a QoE configuration 912, and the network node 902 may obtain (eg, receive) the QoE configuration 912. The QoE configuration 912 may include an HSDN indication 909 and / or a mobility indication 911. Figure 8 Compared with the s-based QoE configuration 812 in Fig. 9The QoE configuration 912 in may be a management-based (m-based) QoE configuration. The HSDN indication 909 and / or the mobility indication 911 indicate that the QoE configuration 912 is for a QoE associated with a HSDN cell and / or with a mobility state of the UE. At 910, the network node 902 determines whether the UE 904 is connected to a HSDN cell or is in a high mobility state. The network node 902 then configures the QoE configuration to one or more UEs (e.g., including the UE 904) based on whether the UE 904 resides on a HSDN cell or if the UE 904 is in a high mobility condition (e.g., as determined at 910). For example, the network node 902 may not configure a QoE configuration for the UE 901, which resides on a non-HSDN cell or is not in a high mobility condition. If the HSDN indication = true and / or if the mobility state = high, the network node 902 may select only those UEs that meet the regional condition for the m-based QoE configuration. If the UE is not currently in a HSDN cell or if the UE is not in a high mobility condition when the network node 902 receives the QoE configuration 912, the network node 902 may store the QoE configuration 912 and forward it to the target RAN when the UE moves.
[0122] like Fig. 9 As shown, the network node 902 outputs (e.g., sends or communicates) an m-based QoE configuration 916 received by the UE 904. At 918, the UE 904 collects QoE measurements based on the m-based QoE configuration 916. For example, the UE 904 can measure QoE information, calculate QoE information, and / or determine QoE information based on the m-based QoE configuration 916. The UE 904 sends a QoE measurement report 920 with the collected QoE measurements to the network node 902. At 922, the network node provides the QoE measurement report to the MCE. When the MCE provides the HSDN indication 909 and / or the mobility indication 911 to the QoE configuration, the MCE can know that the QoE measurement report based on the QoE configuration 912 is for the HSDN and / or for the UE in the high mobility state.
[0123] If the UE 904 connects to a non-HSDN cell and / or if the UE's mobility state changes to a lower mobility state, the UE 904 may release the QoE configuration, as illustrated at 926. For example, the UE 904 may release the QoE measurement report 920 received from the network node 902.
[0124] exist Figure 8 and Fig. 9In the example, QoE measurement collection is performed for HSDN cells or cells with high mobility, while QoE measurement collection is not performed for non-HSDN cells or cells with lower mobility. The QoE measurement report 920 will be transmitted from the HSDN cell or when the UE is in high mobility, because otherwise the QoE configuration is released.
[0125] Fig.10 An example communication flow 1000 involving a serving network node 1002 (which may also be referred to as a source network node) serving a UE 1004, a target network node 1006, and an operations management and maintenance (OAM) or AMF (e.g., OAM / AMF 1008) is illustrated. The serving network node 1002 and / or the target network node 1006 may each correspond to a RAN or a component of a RAN. The serving network node 1002 and / or the target network node 1006 may correspond to a base station (such as base station 102 or base station 310) or a component of a base station (such as CU 110, DU 130, or RU 140).
[0126] In response to the mobility of UE 1004 and / or the change of the mobility state of UE 1004, the network may initiate a handover of the UE from the serving network node 1002 to the target network node 1006. The serving network node 1002 may correspond to the serving network node 1002 and the target network node 1006, respectively. Figure 8 or Fig. 9 The network node 802 or the network node 902 may have previously provided the QoE configuration to the UE from the MCE, such as in conjunction with Figure 8 or Fig. 9 For example, the serving network node 1002 may have provided the UE 1004 with a QoE configuration 1014 for HSDN or high mobility conditions based on a QoE configuration 1012 obtained (e.g., received) from the OAM / AMF 1008 or the MCE, wherein the HSDN indication 1009 and / or the mobility state indication 1011 indicate that the QoE configuration is a measurement for HSDN or is in a high mobility state. Fig.10 As illustrated, the HSDN indication and / or the mobility indication may be propagated to the target network node 1006 during a handover procedure to the target network node 1006, for example, via the QoE configuration 1016 from the serving network node 1002 or the QoE configuration 1018 from the OAM / AMF 1008. As an example, the indication may be provided to the target network node 1006 during an Xn handover, an NG handover, or during an Xn retrieval of a UE context.
[0127] The target network node 1006 may release the QoE configuration based on one or more criteria or conditions. As an example, at 1020, the target network node 1006 may determine whether the conditions of the QoE configuration are met. As an example, if the target network node 1006 is outside the corresponding geographic area for the QoE configuration, the target network node 1006 may release the QoE configuration for the UE at 1022. At 1022, if the target network node provides a non-HSDN cell to which the UE is being handed over, the target network node 1006 may release the QoE configuration for the UE. If the UE is in a lower mobility condition than associated with the QoE configuration, the target network node 1006 may release the QoE configuration for the UE at 1022. In some aspects, if there is no ongoing session for the QoE configuration, the target network node 1006 may release the QoE configuration for the UE at 1022. Fig.10 It is illustrated that the target network node 1006 may indicate the release to the UE 1004 at 1024 .
[0128] Fig.11 An example communication flow 1100 is illustrated in which a UE 1104 may determine whether to collect and / or report QoE information. In some examples, the network may provide a QoE configuration to the UE regardless of whether the UE is camped on a HSDN cell or a non-HSDN cell, and regardless of whether the UE is in high mobility or low mobility, such as Figure 5 The first scene 510, the second scene 512, the third scene 514 and / or the fourth scene 516. Fig.11 The example MCE 1106 can provide a QoE configuration 1110, and the network node 1102 can obtain (e.g., receive) the QoE configuration 1110. The network node 1102 can correspond to a RAN or a component of a RAN. The network node 1102 can correspond to a base station (such as the base station 102 or the base station 310) or a component of a base station (such as the CU 110, the DU 130, or the RU 140). The QoE configuration 1110 can include an HSDN indication 1109 and / or a mobility state indication 1111, such as in conjunction with Figure 8 and Fig. 9 The network node 1102 can provide the QoE configuration to the UE 1104, for example, without determining whether the UE is camped on the HSDN or whether the UE is in a high mobility state, such as in Figure 8 and Fig. 91104. For example, the network node 1102 may output (e.g., send or communicate) a QoE configuration 1112 that is received by the UE 1104. However, the QoE configuration 1112 may configure the UE 1104 to collect measurements when the UE 1104 is connected to a HSDN cell or is in high mobility. The UE 1104 may be configured to provide a QoE measurement report when connected to a HSDN cell. The UE 1104 may be configured to provide a QoE measurement report when connected to a non-HSDN cell. Thus, the QoE configuration may be provided to the UE regardless of whether the UE is camped on a HSDN cell or a non-HSDN cell and / or whether the UE is in a high mobility condition or a low mobility condition.
[0129] Fig.11 An example is illustrated in which QoE measurement collection according to the QoE configuration 1112 may be performed on HSDN cells but not on non-HSDN cells.
[0130] In some aspects, at 1114, the UE access stratum (AS) layer (e.g., AS layer 1103) forwards the HSDN cell information and the UE mobility state to the application layer 1101 of the UE. The application layer 1101 performs QoE measurement collection only for HSDN cells and / or during a high mobility state of the UE 1104. As an example, at 1116, the application layer 1101 can determine that the UE 1104 is connected to the HSDN and / or is in a high mobility state. The application layer 1101 can then collect QoE measurements, as shown at 1118.
[0131] In some aspects, the AS layer 1103 may transmit commands to the application layer 1101 to start / resume or stop / pause QoE collection. These commands may be ATtention (AT) commands transmitted from the AS layer 1103 to the application layer 1101. In this example, the AS layer 1103 may determine whether the UE 1104 is connected to a HSDN cell and / or is in a high mobility state, and may provide commands to the application layer 1101. As an example, at 1118, based on the AS layer 1103 determining that the UE 1104 is connected to a HSDN cell and / or is in a high mobility state, the AS layer 1103 may transmit a command 1117 instructing the application layer 1101 to start collecting QoE measurements. For example, in response to the UE 1104 entering a non-HSDN cell or changing to a lower mobility state, the AS layer 1103 may transmit a command 1124 instructing the network node 1102 to suspend QoE collection. In response to UE 1104 entering another HSDN cell or changing to a high mobility state, AS layer 1103 may transmit a command 1128 to resume QoE collection of QoE information. In response to the command from AS layer 1103, application layer 1101 may collect QoE measurements, such as shown at 1118, and suspend or stop QoE measurements, such as shown at 1126. Fig.11 It is illustrated that the UE 1104 may report QoE measurements to the network node 1102, for example, via a QoE measurement report 1120. The network node 1102 may provide a QoE measurement report 1122 to the MCE 1106 based on the QoE measurement report 1120.
[0132] In some aspects, the UE may transmit QoE reports to the RAN from HSDN cells (eg, only from HSDN cells). Similarly, in some aspects, the UE may transmit QoE reports to the RAN only from non-HSDN cells, if preferred. Fig.12 An example communication flow 1200 is illustrated in which a UE 1204 may determine whether to report QoE information. In some aspects, the UE may also determine whether to collect QoE measurements, such as in conjunction with Fig.11 In some examples, the network may provide a QoE configuration to the UE regardless of whether the UE is camped on a HSDN cell or a non-HSDN cell, and regardless of whether the UE is in high mobility or low mobility, such as Figure 5 The first scene 510, the second scene 512, the third scene 514 and / or the fourth scene 516. Fig.12The example MCE 1206 can provide a QoE configuration 1210 to the network node 1202. The network node 1202 can correspond to a RAN or a component of a RAN. The network node 1202 can correspond to a base station (such as the base station 102 or the base station 310) or a component of a base station (such as the CU 110, the DU 130, or the RU 140). The QoE configuration 1210 can include a HSDN indication 1209 and / or a mobility state indication 1211, such as in conjunction with Figure 8 and Fig. 9 The network node 1202 may provide the QoE configuration 1212 to the UE 1204, for example, without determining whether the UE is camped on the HSDN or whether the UE is in a high mobility state, such as in Figure 8 and Fig. 9 However, the QoE configuration 1212 may configure the UE 1104 to report measurements when the UE 1204 is connected to a HSDN cell or is in high mobility. The UE 1204 may be configured to provide a QoE measurement report when connected to a HSDN cell. The UE 1204 may be configured to provide a QoE measurement report when connected to a non-HSDN cell. Thus, a QoE configuration may be provided to the UE regardless of whether the UE is camped on a HSDN cell or a non-HSDN cell and / or whether the UE is in a high mobility condition or a low mobility condition, and the UE may filter the QoE report based on the HSDN cell or the mobility state of the UE.
[0133] In some aspects, the AS layer 1203 may check whether the current cell is a HSDN cell (e.g., based on SIB1 from the cell) and / or whether the UE is in a high mobility state, and may transmit a QoE measurement report 1220 to the network node 1202 if the UE resides on a HSDN cell and / or is in a high mobility state (e.g., as determined at 1214).
[0134] If the UE resides on a non-HSDN cell, as shown at 1218, the AS layer 1103 may transmit a command 1224 to the application layer 1201 to suspend QoE reporting until the UE resides back on a HSDN cell and / or is in a high mobility state, discard (at 1226) QoE reports received from the application layer 1201 until the UE resides back on a HSDN cell and / or is in a high mobility state, or buffer (at 1226) QoE reports from the application layer 1201 in the AS layer 1203 memory until the UE resides back on a HSDN cell and / or is in a high mobility state.
[0135] In some aspects, at 1216, the AS layer 1203 may forward the HSDN cell information and / or mobility state information to the application layer 1201, for example, based on the determination at 1228. Then, at 1230, the application layer 1201 may determine whether the conditions for the QoE report are met. The application layer 1201 may report QoE data, such as QoE measurements 1232, in response to the UE camping on a HSDN cell or in a high mobility state, and may skip reporting if the UE camps on a non-HSDN cell or is in a lower mobility state. In some aspects, the QoE measurement report 1220 provided by the UE may be based on the determination of the application layer. Then, at 1222, the network node 1202 may provide the QoE measurement data to the MCE 1206.
[0136] In some examples, the network may provide a QoE configuration to the UE regardless of whether the UE is camped on a HSDN cell or a non-HSDN cell, and regardless of whether the UE is in high mobility or low mobility, such as Figure 5 The first scenario 510, the second scenario 512, the third scenario 514 and / or the fourth scenario 516. In addition, the UE may be configured to collect measurements and provide QoE measurement reports regardless of the type of cell in which the UE resides and the mobility of the UE. Fig.13 Example aspects are illustrated in which a network may perform filtering of QoE measurement reports based on indications included in the QoE measurement reports. Fig.13 An example communication flow 1300 is illustrated in which the MCE 1306 may provide a QoE configuration 1310 to a network node 1302. The network node 1302 may correspond to a RAN or a component of a RAN. The network node 1302 may correspond to a base station (such as the base station 102 or the base station 310) or a component of a base station (such as the CU 110, the DU 130, or the RU 140). The QoE configuration 1310 may include a HSDN indication 1309 and / or a mobility state indication 1311, such as in conjunction with Figure 8 and Fig. 9 The network node 1302 may provide the QoE configuration to the UE 1304 at 1312, for example, without determining whether the UE is camped on the HSDN or whether the UE is in a high mobility state, such as in Figure 8 and Fig. 9 UE 1304 may be configured to provide a QoE measurement report together with information that enables the network to identify whether the QoE measurement was made when the UE was connected to a HSDN cell and / or in a high mobility state.
[0137] For example, a QoE measurement report (e.g., a QoE measurement report 1320 or a QoE measurement report 1324 received at the network node 1302 or the MCE 1306) may include an HSDN indication indicating whether the UE 1204 is connected to a HSDN cell or a non-HSDN cell. The QoE measurement report (e.g., the QoE measurement report 1320 and / or the QoE measurement report 1324) may also include a mobility state indication indicating the mobility state of the UE 1304. In some examples, when generating the QoE measurement report, the UE 1304 may include the HSDN indication and / or the mobility state indication. In some examples, when forwarding the QoE report from the UE to the MCE, the network may attach the HSDN indication and / or the mobility state indication. In such a post-processing-based aspect, the MCE 1306 may filter the received QoE report (e.g., the QoE measurement report 1324) based on the HSDN indication and the mobility state indication.
[0138] QoE measurement collection and reporting at UE 1304 may be performed on both HSDN and non-HSDN cells and / or for different mobility conditions of the UE. UE 1304 may transmit QoE measurement reports 1320 from both HSDN cells and non-HSDN cells to network node 1302, and network node 1302 or MCE 1306 may filter the QoE reports based on additional information. Fig.14 Example aspects of such additional information are illustrated. In some aspects, the AS layer 1303 (e.g., RRC) at the UE 1304 can receive QoE measurements 1314 from the application layer 1301, and can add the HSDN indication and the mobility state (high / medium / normal mobility) at 1316, along with the QoE measurement report 1320 to be sent on the RRC. The network node 1302 filters the QoE reports at 1322, e.g., for "high mobility" and / or "HSDN indication = true", and forwards data for those QoE reports to the MCE 1306 (e.g., via the QoE measurement report 1324).
[0139] In some aspects, the application layer 1301 at the UE may add the HSDN indication and / or the UE mobility state (high / medium / normal mobility) indication to the QoE report container at 1318. The MCE 1306 may filter the desired QoE reports based on post-processing, as shown at 1326.
[0140] In some aspects, the network node 1302 may add the HSDN cell indication and / or the UE mobility state indication to the QoE information at 1322 prior to transmitting the QoE report to the MCE, eg, via the QoE measurement report 1324 .
[0141] The UE may report its "mobility state" to the network node 1302 via a self-organizing network (SON) / minimization of drive tests (MDT) report, which may be forwarded to a trace collection entity (TCE) along with timestamp information. The UE may also report the QoE along with timestamp information to the MCE 1306. In post-processing, the network may filter the QoE reports using the mobility state and timestamp information reported in conjunction with other information such as SON / MDT to filter the "high speed" QoE reports based on TCE-MCE interactions.
[0142] In a post-processing based solution, the QoE measurement report received at the MCE may be configured, for example, via a QoE configuration, to include a HSDN indicator indicating whether the UE is connected to a HSDN cell or a non-HSDN cell. The HSDN indicator may be a 1-bit indicator, where a first value indicates that the UE is connected to a HSDN cell and a second value indicates that the UE is connected to a non-HSDN cell. In some examples, the QoE measurement report may be additionally or alternatively configured to include a mobility state indicator indicating a mobility state of the UE.
[0143] Fig.14 An example environment 1400 is illustrated that facilitates providing QoE reporting in a high mobility scenario when a UE 1402 moves between different mobility scenarios, as presented herein. Fig.14 In the example of FIG. 1 , UE 1402 may be a UE with HSDN capability, such as Figure 5 HSDN capable UE 502. UE 1402 may also be located in a high mobility capable vehicle, such as an HST or a vehicle traveling on a highway.
[0144] Aspects of environment 1400 may be similar to Figure 7 1402. For example, UE 1402 may travel on path 1404. For example, at time T1, UE 1402 may connect to first network node 1412 that provides coverage to first cell 1410 ("PCI1"), at time T2, UE 1402 may connect to second network node 1422 that provides coverage to second cell 1420 ("PCI2"), at time T3, UE 1402 may connect to third network node 1432 that provides coverage to third cell 1430 ("PCI3"), and at time T4, UE 1402 may connect to fourth network node 1442 that provides coverage to fourth cell 1440 ("PCI4"). Similar to Figure 7In the example of FIG. 14 , the first cell 1410 and the second cell 1420 are HSDN cells, and the third cell 1430 and the fourth cell 1440 are non-HSDN cells.
[0145] exist Fig.14 In the example of , UE 1402 may satisfy the requirement of Figure 5 The criteria associated with the first scenario 510 may be satisfied when the UE 1402 is connected to the second network node 1422. Figure 5 The criteria associated with the second scenario 512 may be satisfied when UE 1402 is connected to the third network node 1432. Figure 5 The criteria associated with the third scenario 514 of the present invention may be met, and the criteria associated with the fourth scenario 516 may be met when the UE 1402 is connected to the fourth network node 1442.
[0146] like Fig.14 As shown, when UE 1402 moves on path 1404, MCE 1450 can receive QoE measurement reports generated by UE 1402. For example, MCE 1450 can receive a first QoE measurement report 1414 associated with a first cell 1410, can receive a second QoE measurement report 1424 associated with a second cell 1420, can receive a third QoE measurement report 1434 associated with a third cell 1430, and can receive a fourth QoE measurement report 1444 associated with a fourth cell 1440. The QoE measurement report can include a HSDN indicator 1460 and / or a mobility state indicator 1462, which provides cell and / or mobility information of UE 1402 to MCE 1450. For example, with respect to the first QoE measurement report 1414, the values of the HSDN indicator 1460 and the mobility state indicator 1462 indicate that the UE 1402 is connected to a HSDN cell (e.g., "HSDN indicator = true") and that the UE 1402 is in high mobility (e.g., "mobility state = high"). In a similar manner, the second QoE measurement report 1424 indicates that the UE 1402 is connected to a HSDN cell (e.g., "HSDN indicator = true") and that the UE 1402 is in low mobility (e.g., "mobility state = low"). The third QoE measurement report 1434 indicates that the UE 1402 is connected to a non-HSDN cell (e.g., "HSDN indicator = false") and that the UE 1402 is in high mobility (e.g., "mobility state = high"). The fourth QoE measurement report 1444 indicates that the UE 1402 is connected to a non-HSDN cell (eg, "HSDN indicator = false") and that the UE 1402 is in low mobility (eg, "mobility state = low").
[0147] Despite Fig.14 In the example of 1402, the mobility state of UE 1402 is indicated as "high" or "low", but in other examples, the mobility state indicator 1462 can indicate additional or alternative mobility states. For example, the mobility state indicator 1462 can indicate a high mobility state, a medium mobility state, or a normal mobility state.
[0148] The HSDN indicator 1460 and / or the mobility state indicator 1462 may be provided by the network and / or the UE. For example, the UE may transmit a report to the network, and the network transmits a report to the MCE.
[0149] In some aspects, the AS / RRC layer of the UE may add the HSDN indicator 1460 and the mobility state indicator 1462 with the QoE report. The UE may provide the QoE report, the HSDN indicator 1460, and the mobility state indicator 1462 to the network node via RRC signaling. The network may then filter the QoE reports for high mobility and / or HSDN cells and forward those QoE reports to the MCE.
[0150] In some aspects, the UE application layer may add the HSDN indicator 1460 and / or the mobility state indicator 1462. In this example, the UE may provide the indication in the QoE report container. The network may not know the value of the indicator and may simply forward the container to the MCE. The MCE may then perform filtering on the desired QoE report.
[0151] In some aspects, the network node may add a HSDN indicator and a mobility state indicator. The indication in the QoE measurement report received by the MCE may be provided by the network and / or the UE. When the UE provides an indication, the UE may provide an indication from the AS layer or the application layer of the UE.
[0152] Fig.15A 1500 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, UE 350; device 1604). The method may enable the UE to make a decision on whether to report QoE information based on the type of cell and / or the mobility state of the UE, which improves the QoE information provided to the network and increases the efficient use of radio resources for transmitting QoE information. The method may include combining Fig.11 and / or Fig.12 Aspects of description.
[0153] At 1502, the UE receives a QoE configuration associated with a HSDN indication from a network node. The reception may be performed, for example, by Fig.16The QoE signaling component 198 of the device 1604, the cellular RF transceiver 1622, and / or any of the one or more antennas 1680 may be performed. In some aspects, the UE may receive the QoE configuration regardless of whether the UE is camped on a HSDN cell or a non-HSDN cell. In some aspects, the UE may receive the QoE configuration regardless of the mobility state of the UE (e.g., whether the UE is in a higher mobility state or a lower mobility state).
[0154] At 1506, the UE collects QoE information based on at least one of the HSDN state of the cell or the mobility condition of the UE. In some aspects, the UE may collect QoE information for the HSDN cell and skip collecting QoE information for the non-HSDN cell. In some aspects, the UE may collect QoE information for at least one of the HSDN cell and the non-HSDN cell based on the high mobility condition of the UE. The collection may be performed, for example, by Fig.16 The QoE signaling component 198 of the device 1604 in the embodiment is executed. The UE can report the collected QoE information to the network.
[0155] Fig. 15B 1550 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, UE 350; device 1604). The method may enable the UE to make a decision on whether to report QoE information based on the type of cell and / or the mobility state of the UE, which improves the QoE information provided to the network and increases the efficient use of radio resources for transmitting QoE information. The method may include combining Fig.11 and / or Fig.12 Aspects of description.
[0156] At 1502, the UE receives a QoE configuration associated with a HSDN indication from a network node. The reception may be performed, for example, by Fig.16 The QoE signaling component 198 of the device 1604, the cellular RF transceiver 1622, and / or any of the one or more antennas 1680 may be performed. In some aspects, the UE may receive the QoE configuration regardless of whether the UE is camped on a HSDN cell or a non-HSDN cell. In some aspects, the UE may receive the QoE configuration regardless of the mobility state of the UE (e.g., whether the UE is in a higher mobility state or a lower mobility state).
[0157] At 1506, the UE collects QoE information based on at least one of the HSDN state of the cell or the mobility condition of the UE. In some aspects, the UE may collect QoE information for the HSDN cell and skip collecting QoE information for the non-HSDN cell. In some aspects, the UE may collect QoE information for at least one of the HSDN cell and the non-HSDN cell based on the high mobility condition of the UE. The collection may be performed, for example, by Fig.16 The QoE signaling component 198 of the device 1604 in the embodiment is executed. The UE can report the collected QoE information to the network.
[0158] As illustrated at 1504, in some aspects, the UE may forward the HSDN cell information or the UE mobility state information from the AS layer of the UE to the application layer of the UE. This forwarding may be performed, for example, by Fig.16 The QoE signaling component 198 of the device 1604 is executed.
[0159] As illustrated at 1510, the UE may suspend or stop the collection of QoE information in response to entering a non-HSDN cell or changing from a higher mobility state to a lower mobility state. The suspension or stop may be, for example, Fig.16 The QoE signaling component 198 of the device 1604 is executed.
[0160] As an example, illustrated at 1508, the UE may transmit a command from the AS layer of the UE to the application layer of the UE to suspend or stop the collection of QoE information. The command may be, for example, Fig.16 The QoE signaling component 198 of the device 1604 transmits.
[0161] As illustrated at 1512, the UE may discard the QoE information received from the application layer until the UE camps on the second HSDN cell. In other aspects, also as illustrated at 1512, the UE may buffer the QoE information from the application layer until the UE camps on the second HSDN cell. This discarding or buffering may be, for example, Fig.16 The QoE signaling component 198 of the device 1604 is executed.
[0162] The UE may report the collected QoE information, e.g., as illustrated at 1514. In some aspects, the UE may report the QoE information to the HSDN cell and skip reporting the QoE information to the non-HSDN cell. In some aspects, the UE may report the QoE information to the non-HSDN cell. As an example, the UE may report the QoE information to the non-HSDN cell but not to the HSDN cell. In some aspects, the UE may report the QoE information based on the QoE configuration and including an indication of at least one of an association with the HSDN cell or a high mobility condition of the UE. The report may be, for example, Fig.16 The QoE signaling component 198 of the device 1604 is executed.
[0163] Fig.161600 is a diagram illustrating an example of a hardware implementation for an apparatus 1604. The apparatus 1604 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1604 may include a cellular baseband processor 1624 (also referred to as a modem) coupled to one or more transceivers (e.g., a cellular RF transceiver 1622). The cellular baseband processor 1624 may include on-chip memory 1624'. In some aspects, the apparatus 1604 may also include one or more subscriber identity module (SIM) cards 1620 and an application processor 1606 coupled to a secure digital (SD) card 1608 and a screen 1610. The application processor 1606 may include on-chip memory 1606'. In some aspects, the device 1604 may also include a Bluetooth module 1612, a WLAN module 1614, an SPS module 1616 (e.g., a GNSS module), one or more sensor modules 1618 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial management unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1626, a power source 1630, and / or a camera 1632. The Bluetooth module 1612, the WLAN module 1614, and the SPS module 1616 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). The Bluetooth module 1612, the WLAN module 1614, and the SPS module 1616 may include their own dedicated antennas and / or communicate using one or more antennas 1680. The cellular baseband processor 1624 communicates with the UE 104 and / or with the RU associated with the network entity 1602 via one or more antennas 1680 through a transceiver (e.g., a cellular RF transceiver 1622). The cellular baseband processor 1624 and the application processor 1606 may each include a computer-readable medium / memory, such as an on-chip memory 1624' and an on-chip memory 1606', respectively. The additional memory module 1626 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory (e.g., on-chip memory 1624', on-chip memory 1606', and / or additional memory module 1626) may be non-transitory. The cellular baseband processor 1624 and the application processor 1606 are each responsible for general processing, including executing software stored on a computer-readable medium / memory. The software, when executed by the cellular baseband processor 1624 / application processor 1606, causes the cellular baseband processor 1624 / application processor 1606 to perform the various functions described above. The computer-readable medium / memory may also be used to store data that is manipulated by the cellular baseband processor 1624 / application processor 1606 when executing software.The cellular baseband processor 1624 / application processor 1606 may be a component of the UE 350 and may include the memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the device 1604 may be a processor chip (modem and / or application) and include only the cellular baseband processor 1624 and / or the application processor 1606, while in another configuration, the device 1604 may be the entire UE (e.g., see. Figure 3 350) and includes additional modules of device 1604.
[0164] As discussed above, the QoE signaling component 198 is configured to receive a QoE configuration associated with the HSDN indication from a network node, and the UE collects QoE information based on at least one of the HSDN state of the cell or the mobility condition of the UE. In some aspects, the QoE signaling component 198 may be further configured to forward HSDN cell information or UE mobility state information from the AS layer of the UE to the application layer of the UE; suspend or stop the collection of QoE information in response to entering a non-HSDN cell or changing from a higher mobility state to a lower mobility state; transmit a command to suspend or stop the collection of QoE information from the AS layer of the UE to the application layer of the UE; discard the QoE information received from the application layer until the UE resides on a second HSDN cell; buffer the QoE information from the application layer until the UE resides on the second HSDN cell; or report the collected QoE information, for example, as combined Fig. 15BAs described. The QoE signaling component 198 may be within the cellular baseband processor 1624, the application processor 1606, or within both the cellular baseband processor 1624 and the application processor 1606. The QoE signaling component 198 may be one or more hardware components that are specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination of the foregoing. As shown, the device 1604 may include a variety of components configured for various functions. In one configuration, the device 1604 (particularly the cellular baseband processor 1624 and / or the application processor 1606) includes: a component for receiving a QoE configuration associated with an HSDN indication from a network node; and a component for collecting QoE information based on at least one of the HSDN state of the cell or the mobility condition of the UE. The apparatus may also include a component for forwarding HSDN cell information or UE mobility state information from the AS layer of the UE to the application layer of the UE; a component for suspending or stopping the collection of QoE information in response to entering a non-HSDN cell or changing from a higher mobility state to a lower mobility state; a component for transmitting a command to suspend or stop the collection of QoE information from the AS layer of the UE to the application layer of the UE; a component for discarding QoE information received from the application layer until the UE resides on a second HSDN cell; a component for buffering QoE information from the application layer until the UE resides on a second HSDN cell; or a component for reporting the collected QoE information. The component may be a QoE signaling component 198 of the apparatus 1604 configured to perform the functions recited by the component. As described above, the apparatus 1604 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Therefore, in one configuration, the component may be a TX processor 368, an RX processor 356, and / or a controller / processor 359 configured to perform the functions recited by the component.
[0165] Fig.17A 1700 is a flowchart of a method of wireless communication. The method may be performed by a network entity or a network node (e.g., a base station or a component of a base station, such as base station 102, base station 310; CU 110, DU 130, RU 140; network entity 1602). The method may enable the network node to make a decision on whether to configure the UE to collect and / or report QoE information based on the type of cell and / or the mobility state of the UE, which improves the QoE information provided to the network and increases the efficient use of radio resources for transmitting QoE configuration and / or receiving QoE information. The method may include combining Figure 8 and / or Fig. 9 Aspects of description.
[0166] At 1702, the network node obtains a QoE configuration associated with the HSDN indication from a core network component. As an example, the network node may receive the QoE configuration associated with the HSDN from the core network component. In some aspects, the network node may be a RAN that receives the QoE configuration from the MCE via the AMF. In other aspects, the network node may be a RAN that receives the QoE configuration directly from the MCE. The obtaining may be performed, for example, by the QoE configuration component 199.
[0167] At 1704, the network node outputs (e.g., sends or communicates) a QoE configuration for the UE based on the UE camping on the HSDN cell or based on the mobility condition of the UE. In some aspects, the QoE configuration may be a configuration for a single UE, and the network node may output the QoE configuration to the UE based on the UE camping on the HSDN cell. As an example, the network node may send the QoE configuration to the UE. In some aspects, the QoE configuration may be a configuration for a single UE, and the network node may output the QoE configuration to the UE based on the UE satisfying the high mobility condition. In some aspects, the QoE configuration may be a configuration for multiple UEs, and the network node may output the QoE configuration to each UE camping on the HSDN cell. In some aspects, the QoE configuration may be a configuration for multiple UEs, and the network node may output the QoE configuration to each UE satisfying the high mobility condition. In some aspects, the network node may also output the QoE configuration to the UE based on the network node providing the HSDN cell. The output may be performed, for example, by the QoE configuration component 199.
[0168] Fig. 17B 1750 is a flowchart of a method of wireless communication. The method may be performed by a network entity or network node (e.g., a base station or a component of a base station, such as base station 102, base station 310; CU 110, DU 130, RU 140; network entity 1602). The method may enable the network node to make a decision on whether to configure the UE to collect and / or report QoE information based on the type of cell and / or the mobility state of the UE, which improves the QoE information provided to the network and increases the efficient use of radio resources for transmitting QoE configuration and / or receiving QoE information. The method may include combining Figure 8 and / or Fig. 9 Aspects of description.
[0169] At 1702, the network node obtains a QoE configuration associated with the HSDN indication from a core network component. As an example, the network node may receive the QoE configuration associated with the HSDN from the core network component. In some aspects, the network node may be a RAN that receives the QoE configuration from the MCE via the AMF. In other aspects, the network node may be a RAN that receives the QoE configuration directly from the MCE. The obtaining may be performed, for example, by the QoE configuration component 199.
[0170] At 1704, the network node outputs a QoE configuration for the UE based on the UE camping on the HSDN cell or based on the mobility condition of the UE. In some aspects, the QoE configuration may be a configuration for a single UE, and the network node may output the QoE configuration to the UE based on the UE camping on the HSDN cell. As an example, the network node may send the QoE configuration to the UE. In some aspects, the QoE configuration may be a configuration for a single UE, and the network node may output the QoE configuration to the UE based on the UE satisfying the high mobility condition. In some aspects, the QoE configuration may be a configuration for multiple UEs, and the network node may output the QoE configuration to each UE camping on the HSDN cell. In some aspects, the QoE configuration may be a configuration for multiple UEs, and the network node may output the QoE configuration to each UE satisfying the high mobility condition. In some aspects, the network node may also output the QoE configuration to the UE based on the network node providing the HSDN cell. The output may be performed, for example, by the QoE configuration component 199.
[0171] As illustrated at 1706, the network node may receive QoE information from at least one UE based on the QoE configuration. If the QoE configuration is for a single UE, the network node may receive QoE information from the single UE. If the QoE configuration is for multiple UEs, the network node may receive QoE information from multiple UEs. The receiving may be performed, for example, by the QoE configuration component 199. In some aspects, QoE measurement collection may be performed only on HSDN cells. In some aspects, QoE reports may be received only at HSDN cells or when the UE is in a specific mobility condition.
[0172] As illustrated at 1708, the network node can provide QoE information to the core network component based on the network node providing the HSDN cell. For example, the QoE information can include information for the HSDN cell but not for the non-HSDN cell. The providing can be performed, for example, by the QoE configuration component 199.
[0173] Fig.181800 is a flow chart of a method of wireless communication. The method may be performed by a network entity or a network node (e.g., a base station or a component of a base station, such as base station 102, base station 310; CU 110, DU 130, RU 140; network entity 1602). The method may enable the network node to make a decision on whether to release the UE from collecting and / or reporting QoE information based on the type of cell and / or the mobility state of the UE, which improves the QoE information provided to the network and increases the efficient use of radio resources for transmitting QoE configuration and / or receiving QoE information. The method may include combining Fig.10 Aspects of description.
[0174] At 1802, the network node obtains information as a target cell in handover for a UE configured with a QoE configuration associated with a HSDN indication. In some aspects, the information can be obtained as a target cell in handover, which includes a HSDN indication obtained in at least one of an Xn handover, an NG handover, or during an Xn UE context retrieval. The obtaining can be performed, for example, by the QoE configuration component 199.
[0175] At 1804, the network node releases the QoE configuration for the UE. In some aspects, the network node may release the QoE configuration for the UE based on the target cell being outside the area associated with the QoE configuration. In some aspects, the network node may release the QoE configuration for the UE based on the target cell being a non-HSDN cell. In some aspects, the network node may release the QoE configuration for the UE based on the UE failing to meet a mobility condition. In some aspects, the network node may release the QoE configuration for the UE based on the target cell not having an ongoing session with the UE for the QoE configuration. The release may be performed, for example, by the QoE configuration component 199.
[0176] Fig.19 1900 is a flowchart of a method of wireless communication. The method may be performed by a network entity or a network node (e.g., a base station or a component of a base station, such as base station 102, base station 310; CU 110, DU 130, RU 140; network entity 1602). The method may enable the network node to filter the collected QoE information received based on the type of cell and / or the mobility state of the UE, which improves the QoE information provided to the core network and increases the efficient use of radio resources for transmitting QoE configuration and / or receiving QoE information. The method may include combining Fig.13 and / or Fig.14 Aspects of description.
[0177] At 1902, the network node obtains a QoE configuration associated with the HSDN indication from a core network component. The obtaining may be performed, for example, by a QoE configuration component 199. The QoE configuration may be used to provide to the UE regardless of whether the UE is camped on a HSDN cell and / or whether the UE is in a higher mobility state or a lower mobility state.
[0178] At 1904, the network node outputs a QoE configuration to at least one UE. The network node may output a QoE configuration to a plurality of UEs, including one or more UEs being served by another cell and in a lower mobility condition. The outputting may be performed, for example, by the QoE configuration component 199.
[0179] At 1906, the network node receives QoE information from at least one UE. In some aspects, the network node may receive, along with the QoE information, an indication of at least one of an association with a HSDN cell or a high mobility condition of the at least one UE from an access stratum layer or an application layer of the at least one UE. The network node may receive the QoE information from UEs served by the HSDN cell and the non-HSDN cell and / or from UEs in a higher mobility state and a lower mobility state. The receiving may be performed, for example, by the QoE configuration component 199.
[0180] At 1908, the network node reports QoE information for each of the at least one UE to the core network component, the QoE information including an indication of at least one of an association with a HSDN cell or a high mobility condition of the at least one UE. In some aspects, the network node can filter the QoE information to report only information measured for the HSDN cell or for UEs in a higher mobility state. The reporting can be performed, for example, by the QoE configuration component 199.
[0181] Fig. 202000 is a diagram illustrating an example of a hardware implementation for a network entity 2002. The network entity 2002 may be a BS, a component of a BS, or may implement BS functionality. The network entity 2002 may include at least one of a CU 2010, a DU 2030, or a RU 2040. For example, depending on the layer functionality processed by the QoE configuration component 199, the network entity 2002 may include a CU 2010; both a CU 2010 and a DU 2030; each of a CU 2010, a DU 2030, and a RU 2040; a DU 2030; both a DU 2030 and a RU 2040; or a RU 2040. The CU 2010 may include a CU processor 2012. The CU processor 2012 may include an on-chip memory 2012'. In some aspects, an additional memory module 2014 and a communication interface 2018 may also be included. CU 2010 communicates with DU 2030 via a midhaul link such as an F1 interface. DU 2030 may include a DU processor 2032. DU processor 2032 may include on-chip memory 2032'. In some aspects, DU 2030 may also include additional memory modules 2034 and a communication interface 2038. DU 2030 communicates with RU 2040 via a fronthaul link. RU 2040 may include a RU processor 2042. RU processor 2042 may include on-chip memory 2042'. In some aspects, RU 2040 may also include additional memory modules 2044, one or more transceivers 2046, an antenna 2080, and a communication interface 2048. RU 2040 communicates with UE 104. On-chip memory (e.g., on-chip memory 2012', on-chip memory 2032', and / or on-chip memory 2042') and / or additional memory modules (e.g., additional memory module 2014, additional memory module 2034, and / or additional memory module 2044) can each be considered as a computer-readable medium / memory. Each computer-readable medium / memory can be non-transitory. Each of the CU processor 2012, the DU processor 2032, and the RU processor 2042 is responsible for general processing, including executing software stored on the computer-readable medium / memory. The software, when executed by the corresponding processor, enables 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 when executing the software.
[0182] As discussed above, in some aspects, the QoE configuration component 199 may be configured to obtain a QoE configuration associated with the HSDN indication from a core network component, and output a QoE configuration for the UE based on the UE camping on a HSDN cell or based on a mobility condition of the UE. In some aspects, the QoE configuration component 199 may be configured to receive only at a HSDN cell or when the UE is in a specific mobility condition; and provide QoE information to the core network component based on a network node providing the HSDN cell. In some aspects, the QoE configuration component 199 may be configured to obtain information as a target cell in handover for a UE configured with a QoE configuration associated with the HSDN indication, and release the QoE configuration for the UE. In some aspects, the QoE configuration component 199 may be configured to obtain a QoE configuration associated with the HSDN indication from a core network component; output the QoE configuration to at least one UE; receive QoE information from at least one UE; and report QoE information to the core network component for each of the at least one UE, the QoE information including an indication of at least one of an association with a HSDN cell or a high mobility condition of the at least one UE. The QoE configuration component 199 may be within one or more processors of one or more of the CU 2010, DU 2030, and RU 2040. The QoE configuration component 199 may be one or more hardware components specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination of the foregoing. The network entity 2002 may include a variety of components configured for various functions. In one configuration, the network entity 2002 includes a component for obtaining a QoE configuration associated with a HSDN indication from a core network component, and a component for outputting a QoE configuration for a UE based on the UE camping on a HSDN cell or based on a mobility condition of the UE. The device may also include a component for receiving QoE information from at least one UE based on the QoE configuration; and a component for providing the QoE information to the core network component based on a network node providing the HSDN cell. The device may include a component for obtaining information as a target cell in handover for a UE configured with a QoE configuration associated with the HSDN indication, and releasing the QoE configuration for the UE. In some aspects, the device may include a component for obtaining a QoE configuration associated with a HSDN indication from a core network component; a component for outputting the QoE configuration to at least one UE; a component for receiving QoE information from at least one UE; and a component for reporting QoE information to the core network component for each of the at least one UE, the QoE information including an indication of at least one of an association with a HSDN cell or a high mobility condition of the at least one UE.The means may be a QoE configuration component 199 of the network entity 2002 configured to perform the functions recited by the means. As described above, the network entity 2002 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, the means may be a TX processor 316, an RX processor 370, and / or a controller / processor 375 configured to perform the functions recited by the means.
[0183] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is merely an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart may be rearranged based on design preferences. Further, some blocks may be combined or omitted. The attached method claims provide the elements of the various blocks in a sample order, but are not limited to the specific order or hierarchy provided.
[0184] 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 can be applied to other aspects. Therefore, the claims are not limited to the various aspects described herein, but should be given the full scope consistent with the language claims. Unless otherwise specified, reference to an element in the singular form does not mean "one and only one", but "one or more". Terms such as "if", "when" and "while" do not mean a direct temporal relationship or reaction. That is, these phrases (such as "when ......") do not mean an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that if the conditions are met, the action will occur, but no specific or immediate time limit is required for the occurrence of the action. The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having advantages over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, 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" may 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 set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If the first device receives data from the second device or sends data to the second device, the data may be received / sent directly between the first device and the second device, or indirectly between the first device and the second device through a collection of devices. All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure that are known or will later be known to a person of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. Words such as "module", "mechanism", "element", "device", etc. cannot replace the word "component". Therefore, no claim element will be understood as a component plus function unless the element is explicitly stated using the phrase "component for..."
[0185] As used herein, the phrase "based on" should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be interpreted as "based at least on A" unless specifically stated differently.
[0186] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.
[0187] Aspect 1 is a method for wireless communication at a network node, the method comprising: obtaining a QoE configuration associated with a HSDN indication from a core network component; and outputting the QoE configuration for the UE based on the UE camping on a HSDN cell or based on a mobility condition of the UE.
[0188] Aspect 2 is a method according to aspect 1, further comprising the QoE configuration being a configuration for a single UE, and wherein the network node outputs the QoE configuration to the UE based on the UE camping on the HSDN cell.
[0189] Aspect 3 is a method according to any one of aspects 1 and 2, further comprising the QoE configuration being a configuration for a single UE, and wherein the network node outputs the QoE configuration to the UE based on the UE satisfying a high mobility condition.
[0190] Aspect 4 is a method according to aspect 1, further comprising the QoE configuration being a configuration for a plurality of UEs, and wherein the network node outputs the QoE configuration to each UE camping on the HSDN cell.
[0191] Aspect 5 is a method according to any one of aspects 1 and 4, further comprising the QoE configuration being a configuration for a plurality of UEs, and wherein the network node outputs the QoE configuration to each UE that satisfies a high mobility condition.
[0192] Aspect 6 is a method according to any one of aspects 1 to 5, further comprising the network node outputting the QoE configuration to the UE further based on the network node providing the HSDN cell.
[0193] Aspect 7 is a method according to any one of Aspects 1 to 6, further comprising: receiving QoE information from at least one UE based on the QoE configuration; and providing the QoE information to the core network component based on the network node providing the HSDN cell.
[0194] Aspect 8 is an apparatus for wireless communication at a network node, the apparatus comprising: at least one processor, the at least one processor being coupled to a memory and configured to implement any one of aspects 1 to 7.
[0195] In aspect 9, the apparatus of aspect 8 further comprises at least one antenna coupled to the at least one processor.
[0196] In aspect 10, the apparatus according to aspect 8 or 9 further comprises a transceiver coupled to the at least one processor.
[0197] Aspect 11 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 1 to 7.
[0198] In aspect 12, the apparatus according to aspect 11 further comprises at least one antenna coupled to the means for performing the method according to any one of aspects 1 to 7.
[0199] In aspect 13, the apparatus according to aspect 11 or 12 further comprises a transceiver coupled to the means for performing the method according to any one of aspects 1 to 7.
[0200] Aspect 14 is a non-transitory computer-readable storage medium storing computer-executable code, wherein the code, when executed, causes a processor to implement any one of aspects 1 to 7.
[0201] Aspect 15 is a method of wireless communication at a network node, the method comprising: obtaining information as a target cell in handover for a UE configured with a QoE configuration associated with a HSDN indication; and releasing the QoE configuration for the UE.
[0202] Aspect 16 is a method according to aspect 15, further comprising: releasing the QoE configuration for the UE based on the target cell being outside an area associated with the QoE configuration.
[0203] Aspect 17 is a method according to any one of aspects 15 and 16, further comprising: releasing the QoE configuration for the UE based on that the target cell is a non-HSDN cell.
[0204] Aspect 18 is a method according to any one of aspects 15 to 17, further comprising: releasing the QoE configuration for the UE based on the UE failing to meet a mobility condition.
[0205] Aspect 19 is a method according to any one of aspects 15 to 18, further comprising: releasing the QoE configuration for the UE based on the target cell having no ongoing session with the UE for the QoE configuration.
[0206] Aspect 20 is a method according to any one of aspects 15 to 19, further comprising: the information obtained as the target cell in the handover includes the HSDN indication, the HSDN indication being obtained in at least one of an Xn handover, an NG handover, or during an Xn UE context retrieval.
[0207] Aspect 21 is an apparatus for wireless communication at a network node, the apparatus comprising: at least one processor coupled to a memory and configured to implement any one of Aspects 15 to 20.
[0208] In aspect 22, the apparatus according to aspect 21 further comprises at least one antenna coupled to the at least one processor.
[0209] In aspect 23, the apparatus according to aspect 21 or 22 further comprises a transceiver coupled to the at least one processor.
[0210] Aspect 24 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 15 to 20.
[0211] In aspect 25, the apparatus according to aspect 24 further comprises at least one antenna coupled to the means for performing the method according to any one of aspects 15 to 20.
[0212] In aspect 26, the apparatus according to aspect 24 or 25 further comprises a transceiver coupled to the means for performing the method according to any one of aspects 15 to 20.
[0213] Aspect 27 is a non-transitory computer-readable storage medium storing computer-executable code, wherein the code, when executed, causes a processor to implement any one of aspects 15 to 20.
[0214] Aspect 28 is a method of wireless communication at a UE, the method comprising: receiving a QoE configuration associated with a HSDN indication from a network node; and collecting QoE information based on at least one of a HSDN state of a cell or a mobility condition of the UE.
[0215] Aspect 29 is a method according to aspect 28, further comprising: forwarding HSDN cell information or UE mobility state information from an AS layer of the UE to an application layer of the UE.
[0216] Aspect 30 is a method according to any one of aspects 28 and 29, further comprising: collecting the QoE information of HSDN cells and skipping collecting the QoE information of non-HSDN cells.
[0217] Aspect 31 is a method according to any one of aspects 28 and 29, further comprising: collecting the QoE information of at least one of a HSDN cell and a non-HSDN cell based on a high mobility condition of the UE.
[0218] Aspect 32 is a method according to any one of aspects 28 to 31, further comprising: suspending or stopping the collection of the QoE information in response to entering a non-HSDN cell or changing from a higher mobility state to a lower mobility state.
[0219] Aspect 33 is a method according to any one of aspects 28 to 32, further comprising: transmitting a command to suspend or stop the collection of the QoE information from the AS layer of the UE to the application layer of the UE.
[0220] Aspect 34 is a method according to any one of Aspects 28 to 33, further comprising at least one of the following: discarding the QoE information received from the application layer until the UE resides on the second HSDN cell, or buffering the QoE information from the application layer until the UE resides on the second HSDN cell.
[0221] Aspect 35 is a method according to any one of aspects 28 to 34, further comprising: reporting the QoE information to a HSDN cell, and skipping reporting the QoE information to a non-HSDN cell.
[0222] Aspect 36 is a method according to any one of aspects 28 to 34, further comprising: reporting the QoE information to a non-HSDN cell.
[0223] Aspect 37 is a method according to any one of aspects 28 to 36, further comprising: reporting the QoE information, the QoE information being based on the QoE configuration and comprising an indication of at least one of an association with a HSDN cell or a high mobility condition of the UE.
[0224] Aspect 38 is an apparatus for wireless communication at a UE, the apparatus comprising: at least one processor coupled to a memory and configured to implement any one of Aspects 28 to 37.
[0225] In aspect 39, the apparatus of aspect 38 further comprises at least one antenna coupled to the at least one processor.
[0226] In aspect 40, the apparatus according to aspect 38 or 39 further comprises a transceiver coupled to the at least one processor.
[0227] Aspect 41 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 28 to 37.
[0228] In aspect 42, the apparatus according to aspect 41 further comprises at least one antenna coupled to the means for performing the method according to any one of aspects 28 to 37.
[0229] In aspect 43, the apparatus according to aspect 41 or 42 further comprises a transceiver coupled to the means for performing the method according to any one of aspects 28 to 37.
[0230] Aspect 44 is a non-transitory computer-readable storage medium storing computer-executable code, wherein the code, when executed, causes a processor to implement any one of aspects 28 to 37.
[0231] Aspect 45 is a method for wireless communication at a network node, the method comprising: obtaining a QoE configuration associated with a HSDN indication from a core network component; outputting the QoE configuration to at least one UE; receiving QoE information from the at least one UE; and reporting the QoE information to the core network component for each of the at least one UE, the QoE information including an indication of at least one of an association with a HSDN cell or a high mobility condition of the at least one UE.
[0232] Aspect 46 is a method according to aspect 45, further comprising: receiving, together with the QoE information, from an access hierarchy layer or an application layer of the at least one UE, the indication of at least one of the association with the HSDN cell or the high mobility condition of the at least one UE.
[0233] Aspect 47 is a method according to any one of aspects 45 and 46, further comprising outputting the QoE configuration to a plurality of UEs, the plurality of UEs including one or more UEs being served by another cell and in a lower mobility condition.
[0234] Aspect 48 is an apparatus for wireless communication at a network node, the apparatus comprising: at least one processor coupled to a memory and configured to implement any one of aspects 45 to 47.
[0235] In aspect 49, the apparatus according to aspect 48 further comprises at least one antenna coupled to the at least one processor.
[0236] In aspect 50, the apparatus according to aspect 48 or 49 further comprises a transceiver coupled to the at least one processor.
[0237] Aspect 51 is an apparatus for wireless communication, comprising means for implementing any one of aspects 1 to 47.
[0238] In aspect 52, the apparatus according to aspect 51 further comprises at least one antenna coupled to the means for performing the method according to any one of aspects 45 to 47.
[0239] In aspect 53, the apparatus according to aspect 51 or 52 further comprises a transceiver coupled to the means for performing the method according to any one of aspects 45 to 47.
[0240] Aspect 54 is a non-transitory computer-readable storage medium storing computer-executable code, wherein the code, when executed, causes a processor to implement any one of aspects 45 to 47.
Claims
1. An apparatus for wireless communication at a network node, include: Memory; as well as at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: obtaining, from a core network component, a quality of experience (QoE) configuration associated with a high speed dedicated network (HSDN) indication; and The QoE configuration for a user equipment (UE) is output based on the UE camping on a HSDN cell or based on a mobility condition of the UE.
2. The apparatus of claim 1 , wherein the QoE configuration is for a configuration for a single UE, and wherein the at least one processor is configured to: The QoE configuration is output to the UE based on the UE camping on the HSDN cell.
3. The apparatus of claim 1 , wherein the QoE configuration is for a configuration for a single UE, and wherein the at least one processor is configured to: The QoE configuration is output to the UE based on the UE satisfying a high mobility condition.
4. The apparatus of claim 1 , wherein the QoE configuration is for a configuration for a plurality of UEs, and wherein the at least one processor is configured to: The QoE configuration is output to each UE camping on the HSDN cell.
5. The apparatus of claim 1 , wherein the QoE configuration is for a configuration for a plurality of UEs, and wherein the at least one processor is configured to: The QoE configuration is output to each UE that meets the high mobility condition.
6. The apparatus of claim 1, wherein the at least one processor is further configured to: The QoE configuration is output to the UE further based on the network node providing the HSDN cell.
7. The apparatus of claim 1, wherein the at least one processor is further configured to: receiving QoE information from at least one UE based on the QoE configuration; and The QoE information is provided to the core network component based on the network node providing the HSDN cell.
8. The apparatus of claim 1, further comprising a transceiver coupled to the at least one processor.
9. An apparatus for wireless communication at a network node, include: Memory; as well as at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: obtaining information of a target cell in handover for a user equipment (UE) configured with a quality of experience (QoE) configuration associated with a high speed private network (HSDN) indication; and The QoE configuration for the UE is released.
10. The apparatus of claim 9, wherein the at least one processor is configured to: The QoE configuration for the UE is released based on the target cell being outside an area associated with the QoE configuration.
11. The apparatus of claim 9, wherein the at least one processor is configured to: The QoE configuration for the UE is released based on the target cell being a non-HSDN cell.
12. The apparatus of claim 9, wherein the at least one processor is configured to: The QoE configuration for the UE is released based on the UE failing to satisfy a mobility condition.
13. The apparatus of claim 9, wherein the at least one processor is configured to: The QoE configuration for the UE is released based on the target cell not having an ongoing session with the UE for the QoE configuration.
14. The apparatus of claim 9, wherein the information obtained as the target cell in the handover comprises the HSDN indication, the HSDN indication being obtained in at least one of an Xn handover, a next generation (NG) handover, or during an Xn UE context retrieval.
15. The apparatus of claim 9, further comprising a transceiver coupled to the at least one processor.
16. An apparatus for wireless communication at a user equipment (UE), include: Memory; as well as at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: receiving a quality of experience (QoE) configuration associated with a high speed dedicated network (HSDN) indication from a network node; and QoE information is collected based on at least one of a HSDN status of a cell or a mobility condition of the UE.
17. The apparatus of claim 16, wherein the at least one processor is further configured to: HSDN cell information or UE mobility state information is forwarded from an access stratum (AS) layer of the UE to an application layer of the UE.
18. The apparatus of claim 16, wherein the at least one processor is configured to: The QoE information of the HSDN cells is collected, and the collection of the QoE information of the non-HSDN cells is skipped.
19. The apparatus of claim 16, wherein the at least one processor is configured to: The QoE information of at least one of a HSDN cell and a non-HSDN cell is collected based on a high mobility condition of the UE.
20. The apparatus of claim 16, wherein the at least one processor is further configured to: In response to entering a non-HSDN cell or changing from a higher mobility state to a lower mobility state, the collection of the QoE information is suspended or stopped.
21. The apparatus of claim 20, wherein the at least one processor is further configured to: A command to pause or stop the collection of the QoE information is transmitted from an access stratum (AS) layer of the UE to an application layer of the UE.
22. The apparatus of claim 20, wherein the at least one processor is further configured to perform at least one of the following: discarding the QoE information received from the application layer until the UE camps on a second HSDN cell, or The QoE information from the application layer is buffered until the UE camps on the second HSDN cell.
23. The apparatus of claim 16, wherein the at least one processor is further configured to: The QoE information is reported to the HSDN cell, and reporting of the QoE information to the non-HSDN cell is skipped.
24. The apparatus of claim 16, wherein the at least one processor is further configured to: The QoE information is reported to the non-HSDN cell.
25. The apparatus of claim 16, wherein the at least one processor is further configured to: The QoE information is reported, the QoE information being based on the QoE configuration and comprising an indication of at least one of an association with a HSDN cell or a high mobility condition of the UE.
26. The apparatus of claim 16, further comprising a transceiver coupled to the at least one processor.
27. An apparatus for wireless communication at a network node, include: Memory; as well as at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: obtaining, from a core network component, a quality of experience (QoE) configuration associated with a high-speed dedicated network (HSDN) indication; outputting the QoE configuration to at least one user equipment (UE); receiving QoE information from the at least one UE; as well as The QoE information is reported to the core network component for each of the at least one UE, the QoE information including an indication of at least one of an association with a HSDN cell or a high mobility condition of the at least one UE.
28. The apparatus of claim 27, wherein the at least one processor is further configured to: The indication of at least one of the association with the HSDN cell or the high mobility condition of the at least one UE is received from an access stratum layer or an application layer of the at least one UE along with the QoE information.
29. The apparatus of claim 27, wherein the at least one processor is configured to: The QoE configuration is output to a plurality of UEs, the plurality of UEs including one or more UEs being served by another cell and in a lower mobility condition.
30. The apparatus of claim 27, further comprising a transceiver coupled to the at least one processor.
