Quality of experience metrics for dual connectivity modes

By introducing RVQoE configurations and measurement reports between MN and SN in dual connectivity, the patent addresses the challenge of optimizing user experience and network performance in wireless communication systems, leading to enhanced QoE.

CN119072940APending Publication Date: 2024-12-03QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280095217.8
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

Technical Problem

Existing wireless communication systems lack effective methods for managing quality of experience (QoE) metrics in dual connectivity modes, particularly in scenarios involving multiple radio access networks, which can lead to suboptimal user experience and network performance.

Method used

Implementing radio access network visible quality of experience (RVQoE) configurations and measurement reports between a master node (MN) and a secondary node (SN) in dual connectivity mode, enabling dynamic adjustment and optimization of network performance based on user experience metrics.

Benefits of technology

Enhances user experience and network performance by allowing for real-time adjustments and optimizations in dual connectivity scenarios, improving overall QoE in wireless communication systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119072940A_ABST
    Figure CN119072940A_ABST
Patent Text Reader

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive one or more radio access network quality of visual experience (RVQoE) configurations from at least one of a primary node (MN) or a secondary node (SN), where the UE operates in a dual connectivity mode with the MN and the SN. The UE may send at least one RVQoE measurement report to at least one of the MN or the SN based at least in part on the one or more RVQoE configurations. Numerous other aspects are described.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Aspects of the present disclosure relate generally to wireless communications and techniques and apparatus for quality of experience metrics for dual connectivity modes, including radio access network visible quality of experience metrics for dual connectivity modes. Background Art

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). 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, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0003] A wireless network may include one or more base stations that support communication for a user equipment (UE) or multiple UEs. A UE may communicate with a base station via downlink and uplink communications. A "downlink" (or "DL") refers to the communication link from a base station to a UE, and an "uplink" (or "UL") refers to the communication link from a UE to a base station.

[0004] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR), which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with a cyclic prefix (CP) on the downlink, CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and better integrate with other open standards. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0005] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include receiving one or more radio access network visual quality of experience (RVQoE) configurations from at least one of a master node (MN) or a secondary node (SN), wherein the UE operates in a dual connectivity mode with the MN and the SN. The method may include sending at least one RVQoE measurement report to at least one of the MN or the SN based at least in part on the one or more RVQoE configurations.

[0006] Some aspects described herein relate to a method of wireless communication performed by a MN. The method may include sending one or more RVQoE configurations to a UE, wherein the UE operates in a dual connectivity mode with the MN and a SN. The method may include receiving at least one RVQoE measurement report from the UE based at least in part on the one or more RVQoE configurations.

[0007] Some aspects described herein relate to an apparatus for wireless communication at a UE. The apparatus may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive one or more RVQoE configurations from at least one of a MN or a SN, wherein the UE operates in a dual connectivity mode with the MN and the SN. The one or more processors may be configured to send at least one RVQoE measurement report to at least one of the MN or the SN based at least in part on the one or more RVQoE configurations.

[0008] Some aspects described herein relate to an apparatus for wireless communication at a MN. The apparatus may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send one or more RVQoE configurations to a UE, wherein the UE operates in a dual connectivity mode with a MN and a SN. The one or more processors may be configured to receive at least one RVQoE measurement report from the UE based at least in part on the one or more RVQoE configurations.

[0009] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive one or more RVQoE configurations from at least one of a MN or a SN, wherein the UE operates in a dual connectivity mode with the MN and the SN. The instruction set, when executed by one or more processors of the UE, may cause the UE to send at least one RVQoE measurement report to at least one of the MN or the SN based at least in part on the one or more RVQoE configurations.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a MN. When executed by one or more processors, one or more instructions of the instruction set, when executed by one or more processors of the MN, may cause the MN to send one or more RVQoE configurations to a UE, wherein the UE operates in a dual connectivity mode with the MN and a SN. The instruction set, when executed by one or more processors of the MN, may cause the MN to receive at least one RVQoE measurement report from the UE based at least in part on the one or more RVQoE configurations.

[0011] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving one or more RVQoE configurations from at least one of a MN or a SN, wherein the apparatus operates in a dual connectivity mode with the MN and the SN. The apparatus may include means for sending at least one RVQoE measurement report to at least one of the MN or the SN based at least in part on the one or more RVQoE configurations.

[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending one or more RVQoE configurations to a UE, wherein the UE operates in a dual connectivity mode with the apparatus and a SN. The apparatus may include means for receiving at least one RVQoE measurement report from the UE based at least in part on the one or more RVQoE configurations.

[0013] Aspects of the present invention generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices and / or processing systems as fully described herein with reference to the accompanying drawings and descriptions and as illustrated in the accompanying drawings and descriptions.

[0014] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following detailed description may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of protection of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims.

[0015] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user equipment, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence equipment). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0017] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0018] Figure 2 is a diagram illustrating an example of communication between a base station and a user equipment (UE) in a wireless network according to the present disclosure.

[0019] Figure 3 is a diagram illustrating an example of an open radio access network architecture according to the present disclosure.

[0020] Figure 4 is a diagram illustrating an example of dual connectivity according to the present disclosure.

[0021] Figure 5 is a diagram illustrating an example of a quality of experience configuration and reporting process according to the present disclosure.

[0022] Figures 6 to 10is a diagram illustrating an example associated with configuration of quality of experience of dual connectivity mode and / or radio access network visible quality of experience measurement according to the present disclosure.

[0023] Fig.11 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0024] Fig.12 is a diagram illustrating an example process performed, for example, by a master node according to the present disclosure.

[0025] Figure 13 to Figure 14 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0026] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be construed as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of protection of the present disclosure will be fully conveyed to those skilled in the art. It should be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such a device or method implemented using other structures, functions, or structures and functions other than the various aspects of the present disclosure set forth herein or different from the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0027] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a 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.

[0028] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applied to other RATs, such as 3G RAT, 4G RAT, and / or post-5G RATs (e.g., 6G).

[0029] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, among other examples. The wireless network 100 may include one or more base stations 110 (shown as BS110a, BS110b, BS110c, and BS110d), a user equipment (UE) 120 or multiple UEs 120 (shown as UE120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other network entities. The base station 110 is an entity that communicates with the UE 120. Base station 110 (sometimes referred to as BS) may include, for example, an NR base station, an LTE base station, a B node, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and / or a transmit receive point (TRP). Figure 1 In some other aspects, the functionality of base station 110 may be decomposed according to an open radio access network (O-RAN) architecture, etc., which will be combined with Figure 3 Each base station 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​a base station 110 and / or a base station subsystem serving the coverage area, depending on the context in which the term is used.

[0030] The base station 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A base station 110 for a macro cell may be referred to as a macro base station. A base station 110 for a pico cell may be referred to as a pico base station. A base station 110 for a femto cell may be referred to as a femto base station or a home base station. In Figure 1 In the example shown in , BS 110a may be a macro base station for macro cell 102a, BS 110b may be a pico base station for pico cell 102b, and BS 110c may be a femto base station for femto cell 102c. A base station may support one or more (eg, three) cells.

[0031] In some examples, the cell may not necessarily be stationary, and the geographic area of ​​the cell may move according to the location of the mobile base station 110 (e.g., a mobile base station). In some examples, the base stations 110 can be interconnected with each other and / or to one or more other base stations 110 or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces, such as direct physical connections or virtual networks, using any suitable transport network.

[0032] The wireless network 100 may include one or more relay stations. A relay station is an entity that can receive transmissions of data from an upstream station (e.g., a base station 110 or a UE 120) and transmit transmissions of data to a downstream station (e.g., a UE 120 or a base station 110). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1 In the example shown in FIG, BS 110d (eg, a relay base station) can communicate with BS 110a (eg, a macro base station) and UE 120d to facilitate communication between BS 110a and UE 120d. Base station 110 that relays communication may be referred to as a relay station, relay base station, repeater, etc.

[0033] The wireless network 100 may be a heterogeneous network that includes different types of base stations 110, such as macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0034] A network controller 130 may be coupled to or in communication with a set of base stations 110 and may provide coordination and control for these base stations 110. The network controller 130 may communicate with the base stations 110 via backhaul communication links. The base stations 110 may communicate directly with each other or indirectly via wireless or wired backhaul links.

[0035] UE 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. UE 120 may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, and / or any other suitable device configured to communicate via a wireless medium.

[0036] Some UEs 120 may be considered as machine type communication (MTC) UEs or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that may communicate with a base station, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included in a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operationally coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0037] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, an air interface, etc. Frequency may be referred to as a carrier, a frequency channel, etc. In a given geographic area, each frequency may support a single RAT to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0038] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more side link channels (e.g., without using base station 110 as an intermediary to communicate with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110.

[0039] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. 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). It should be understood that, although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the “below 6 GHz” band in various documents and articles. Similar naming issues sometimes occur with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0040] The 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 the FR1 characteristics and / or FR2 characteristics, so 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 FR4a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0041] In view of the above examples, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term can be broadly referred to as frequencies that may be below 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term can be broadly referred to as frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0042] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive one or more radio access network visual quality of experience (RVQoE) configurations from at least one of a primary node (MN) or a secondary node (SN), wherein the UE operates in a dual connectivity mode with the MN and the SN; and send at least one RVQoE measurement report to at least one of the MN or the SN based at least in part on the one or more RVQoE configurations. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0043] In some aspects, the MN and / or SN described elsewhere herein may correspond to the base station 110. The MN and / or SN may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may send one or more RVQoE configurations to a UE (e.g., UE 120), wherein the UE operates in a dual connectivity mode with the MN and the SN; and receive at least one RVQoE measurement report from the UE based at least in part on the one or more RVQoE configurations. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0044] As indicated above, Figure 1 Other examples can be found in the Figure 1 The examples described are different.

[0045] Figure 2 2 is a diagram illustrating an example 200 of base station 110 communicating with UE 120 in wireless network 100 according to the present disclosure. Base station 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T ≥ 1). UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R ≥ 1).

[0046] At the base station 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQI) received from the UE 120. The base station 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may further process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0047] At the UE 120, a set of antennas 252 (shown as antennas 252a through 252r) may receive downlink signals from the base station 110 and / or other base stations 110, and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a through 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0048] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the base station 110 via the communication unit 294.

[0049] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include, or may be included within, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0050] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the base station 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, reference Figures 6 to 14 )Aspects of any of the methods described herein.

[0051] At the base station 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component of the modem 232 shown as DEMOD), detected by the MIMO detector 236 where applicable, and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The base station 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the base station 110 may include a modulator and a demodulator. In some examples, the base station 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform operations described herein (e.g., with reference to Figures 6 to 14 )Aspects of any of the methods described herein.

[0052] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2Any other component in may perform one or more techniques associated with RVQoE metrics for dual connectivity mode, as described in more detail elsewhere herein. In some aspects, the MN described herein is Figure 2 The base station 110 shown in FIG. 1 is included in the base station 110, or includes one or more components of the base station 110. The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Fig.11 Process 1100, Fig.12 1200 and / or other processes described herein. Memory 242 and memory 282 may store data and program codes for base station 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, one or more instructions, when executed by one or more processors of base station 110 and / or UE 120 (e.g., directly, or after compilation, conversion, and / or interpretation), may cause one or more processors, UE 120, and / or base station 110 to perform or direct, for example, Fig.11 Process 1100, Fig.12 The process 1200 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, among others.

[0053] In some aspects, the UE 120 includes means for receiving one or more RVQoE configurations from at least one of the MN or the SN, wherein the UE operates in a dual connectivity mode with the MN and the SN; and / or means for sending at least one RVQoE measurement report to at least one of the MN or the SN based at least in part on the one or more RVQoE configurations. Means for the UE 120 to perform operations described herein may include, for example, one or more of the communications manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0054] In some aspects, the MN (which may correspond to the base station 110) includes means for sending one or more RVQoE configurations to a UE (e.g., UE 120), wherein the UE operates in a dual connectivity mode with the MN and the SN; and / or means for receiving at least one RVQoE measurement report from the UE based at least in part on the one or more RVQoE configurations. In some aspects, means for the MN to perform operations described herein may include, for example, one or more of the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0055] Although Figure 2 The blocks in the 200 and 210 are shown as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0056] As indicated above, Figure 2 Other examples can be found in the Figure 2 The examples described are different.

[0057] Figure 3 3 is a diagram illustrating an example 300 of an O-RAN architecture according to the present disclosure. Figure 3 As shown, the O-RAN architecture may include a central unit (CU) 310 that communicates with a core network 320 via a backhaul link. In addition, the CU 310 may communicate with one or more distributed units (DU) 330 via corresponding midhaul links. The DU 330 may each communicate with one or more radio units (RU) 340 via a corresponding fronthaul link, and the RU 340 may each communicate with a corresponding UE 120 via a radio frequency (RF) access link. The DU 330 and the RU 340 may also be referred to as an O-RAN DU (O-DU) 330 and an O-RAN RU (O-RU) 340, respectively.

[0058] In some aspects, the DU 330 and the RU 340 may be implemented according to a functional split architecture, wherein the functionality of a base station 110 (e.g., an eNB or gNB) is provided by the DU 330 and one or more RUs 340 that communicate via a fronthaul link. Thus, as described herein, the base station 110 may include a DU 330 and one or more RUs 340, which may be co-located or geographically distributed. In some aspects, the DU 330 and the associated RU 340 may communicate via the fronthaul link to exchange real-time control plane information via a lower layer split (LLS) control plane (LLS-C) interface, non-real-time management information via an LLS management plane (LLS-M) interface, and / or user plane information via an LLS user plane (LLS-U) interface.

[0059] Thus, the DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. For example, in some aspects, the DU 330 may host a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (e.g., forward error correction (FEC) encoding and decoding, scrambling, and / or modulation and demodulation) based at least in part on the lower layer functional split. Higher layer control functions (such as packet data convergence protocol (PDCP), radio resource control (RRC), and / or service data adaptation protocol (SDAP)) may be hosted by the CU 310. Based at least in part on the lower layer functional split, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions and low PHY layer functions (e.g., fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, and / or physical random access channel (PRACH) extraction and filtering). Thus, in the O-RAN architecture, the RU 340 handles all over-the-air (OTA) communications with the UE 120, and the real-time and non-real-time aspects of the control plane and user plane communications with the RU 340 are controlled by the corresponding DU 330, which enables the DU 330 and CU 310 to be implemented in a cloud-based RAN architecture. In some aspects, the UE 120 can operate in a dual connectivity mode with more than one base station 110, CU 310, DU 330, RU 340, or similar network nodes or entities, which will be discussed below in conjunction with Figure 4 Describe in more detail.

[0060] As indicated above, Figure 3 Other examples can be found in the Figure 3 The examples described are different.

[0061] Figure 4 is a diagram illustrating an example 400 of dual connectivity according to the present disclosure. Figure 4The example shown is for Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA)-NR Dual Connectivity (ENDC) mode. In ENDC mode, UE 120 communicates using LTE RAT on a primary cell group (MCG), and UE 120 communicates using NR RAT on a secondary cell group (SCG). However, the various aspects described herein may be applicable to ENDC mode (e.g., where the MCG is associated with the LTE RAT and the SCG is associated with the NR RAT), NR-E-UTRA Dual Connectivity (NEDC) mode (e.g., where the MCG is associated with the NR RAT and the SCG is associated with the LTE RAT), NR Dual Connectivity (NRDC) mode (e.g., where the MCG is associated with the NR RAT and the SCG is also associated with the NR RAT), or another dual connectivity mode (e.g., where the MCG is associated with the first RAT and the SCG is associated with one of the first RAT or the second RAT). ENDC mode is sometimes referred to as NR or 5G non-standalone (NSA) mode. Thus, as used herein, “dual connectivity mode” may refer to an ENDC mode, a NEDC mode, an NRDC mode, and / or another type of dual connectivity mode.

[0062] like Figure 4 As shown, UE 120 can communicate with eNB (e.g., 4G base station 110, CU 310, DU 330, RU 340 or other LTE network node or entity, which is sometimes referred to as MN) and gNB (e.g., 5G base station 110, CU 310, DU 330, RU 340 or other 5G network node or entity, which is sometimes referred to as SN)), and the eNB and gNB can communicate (e.g., directly or indirectly) with a 4G / LTE core network, which is shown as an evolved packet core (EPC) including a mobility management entity (MME), a packet data network gateway (PGW), a serving gateway (SGW) and / or other devices. In NRDC mode (e.g., a mode in which both MN and SN are associated with corresponding 5G base stations 110, CU 310, DU 330, RU 340, or other network nodes or entities) or other dual connectivity modes, MN and SN may communicate with a 5G core network including a multi-cell / multicast coordination entity (MCE), a tracking collection entity (TCE), or similar devices. Figure 4 In the present invention, PGW and SGW are collectively referred to as P / SGW. In some aspects, the eNB and gNB may be co-located at the same base station 110 or other network entity. In some aspects, the eNB and gNB may be included in different base stations 110 or network entities (e.g., they may not be co-located).

[0063] As in Figure 4As further shown in , in some aspects, a wireless network that permits operation in 5G NSA mode may use an MCG for a first RAT (e.g., an LTE RAT or 4G RAT in the depicted example, but which may be an NR RAT or 5G RAT in other examples) and an SCG for a second RAT (e.g., an NR RAT or 5G RAT) to permit such operation. In this scenario, the UE 120 may communicate with the eNB via the MCG and may communicate with the gNB via the SCG. In some aspects, the MCG may anchor the network connection between the UE 120 and the core network (e.g., for mobility, coverage, and / or control plane information), and the SCG may be added as an additional carrier to increase throughput (e.g., for data services and / or user plane information). In some aspects, the gNB and the eNB may not pass user plane information between each other. In some other aspects, the MN and the SN may communicate with each other, such as in conjunction with Figure 5 Described in more detail. In some aspects, a UE 120 operating in dual connectivity mode may be connected concurrently with an LTE base station 110 or other network entity (e.g., an eNB) and an NR base station 110 or other network entity (e.g., a gNB) (e.g., in the case of ENDC or NEDC), or may be connected concurrently with one or more base stations 110 or other network entities using the same RAT (e.g., in the case of NRDC). In some aspects, an MCG may be associated with a first frequency band (e.g., a sub-6 GHz band and / or an FR1 band), and an SCG may be associated with a second frequency band (e.g., a millimeter wave band and / or an FR2 band).

[0064] The UE 120 may communicate via the MCG and the SCG using one or more radio bearers (e.g., data radio bearers (DRBs) and / or signaling radio bearers (SRBs)). For example, the UE 120 may send or receive data via the MCG and / or the SCG using one or more DRBs. Similarly, the UE 120 may transmit or receive control information (e.g., RRC information and / or measurement reports) using one or more SRBs. In some aspects, one or more types of SRBs may be used for communication between the UE 120 and the MN, and different one or more types of SRBs may be used for communication between the UE 120 and the SN. For example, a type 0 SRB (e.g., SRB0), a type 1 SRB (e.g., SRB1), and / or a type 2 SRB (e.g., SRB2) may be used for communication between the UE 120 and the MN, and a type 3 SRB (e.g., SRB3) may be used for communication between the UE 120 and the SN. In some aspects, a radio bearer may be dedicated to a specific cell group (e.g., a radio bearer may be an MCG bearer or an SCG bearer). In some aspects, the radio bearer may be a split radio bearer. A split radio bearer may be split in the uplink and / or downlink. For example, a DRB may be split on the downlink (e.g., the UE 120 may receive downlink information for the MCG or SCG in the DRB) but not split on the uplink (e.g., the uplink may not be split from the primary path to the MCG or SCG such that the UE 120 transmits in the uplink only on the primary path). In some aspects, the DRB may be split from the primary path to the MCG or SCG on the uplink. The DRB split in the uplink may use the primary path to send data until the size of the uplink send buffer meets the uplink data split threshold. If the uplink send buffer meets the uplink data split threshold, the UE 120 may use the DRB to send data to the MCG or SCG.

[0065] In some aspects, the UE 120 may measure one or more quality of experience (QoE) metrics and report the measurements to one or more of the MN, SN, and / or the core network via the MCG, the SCG, or both the MCG and the SCG. Figure 5 Let's describe various aspects of QoE measurement in more detail.

[0066] As indicated above, Figure 4 Other examples can be found in the Figure 4 The examples described are different.

[0067] Figure 5 is a diagram illustrating an example 500 of a QoE configuration and reporting process according to the present disclosure. Figure 5As shown, various network entities and devices and layers within these devices can communicate with each other through a wireless network (e.g., wireless network 100), etc. For example, TCE / MCE entities (e.g., TCE / MCE 505), operations, execution and management (OAM) entities (e.g., OAM 510), core network (CN) entities (e.g., CN 515), RAN entities (e.g., RAN 520) (in some aspects, it can be a NG-RAN entity such as base station 110, CU 310, DU 330, RU 340 or similar entity), UE access layer (AS) layer or entity (e.g., USAS 525) and / or UE application (APP) layer or entity (e.g., UE APP 530) can communicate with each other. In some aspects, UE AS 525 and UE APP 530 can be associated with UE 120.

[0068] As shown in step 0, the UE AS 525 may report capability information of the UE 120 to the RAN 520. For example, the capability information may be reported during an initial access procedure, and the capability information may include information about the types of QoE metrics that the UE 120 is capable of measuring, etc. As shown in step 1, in a signaling-based NR QoE activation procedure, the OAM 510 may configure the CN 515 with QoE measurement information, sometimes referred to as a QoE measurement configuration. As shown in step 2a, in a signaling-based NR QoE activation procedure, the CN 515 may activate the QoE measurement procedure by forwarding the QoE measurement configuration to the RAN 520. Alternatively, in a management-based activation procedure, as shown in step 2b, the OAM 510 may activate the QoE measurement procedure by forwarding the QoE measurement configuration directly to the RAN 520. In other words, in the signaling-based NR QoE activation procedure, the CN 515 may initiate activation of QoE measurements, as configured by the OAM entity 510, while in the management-based NR QoE activation procedure, the RAN 520 may initiate activation of QoE measurements, as configured by the OAM 510. In some aspects, the OAM 510 may configure and / or activate multiple simultaneous QoE measurements.

[0069] As shown in step 3, the RAN 520 may send an RRC configuration message including a QoE measurement configuration to the UE 120 (and more specifically, to the UE AS 525). As shown in step 4, the UE AS 525 may send an attention (AT) command or the like including the QoE measurement configuration to the UE APP 530. The UE APP 530 may perform one or more QoE measurements based at least in part on the QoE measurement configuration, and as shown in step 5, the UE APP 530 may send an attention (AT) command or the like to the UE AS 525, the command including a QoE report including one or more QoE measurements and / or one or more QoE metrics. As shown in step 6, the UE AS 525 may send an RRC message or the like including a QoE report to the RAN 520. And as shown in step 7, the RAN 520 may send the QoE report to the TCE / MCE 505.

[0070] In these aspects, the QoE measurements may be provided from the UE 120 (and more specifically, from the UEAS 525) to the RAN 520 within a compressed XML file or the like. In this regard, the QoE measurements are transparent to the RAN 520. However, in some aspects, the RAN 520 may need to utilize the QoE measurements at the RAN level. For example, it may be beneficial for the RAN 520 to use the QoE measurements for purposes such as QoE-aware scheduling, QoE-aware load balancing, link adaptation, post-handover mobility decision evaluation, and the like. This requires the RAN 520 to parse, decode, and / or analyze the compressed XML file or the like in order to utilize the QoE measurements, which may be a cumbersome task. Furthermore, when a UE (e.g., UE 120) is operating in a dual connectivity mode, such as in conjunction with the above, the QoE measurements may be used to perform tasks such as performing a multi-port operation. Figure 4 As described, each QoE measurement may only be related to a RAN entity associated with the connectivity associated with a particular application, which may be difficult to determine by the RAN 520. As a result, the RAN 520 must consume a large amount of power, computing, and other resources to use the QoE measurements for QoE-aware scheduling, QoE-aware load balancing, link adaptation, post-handover mobility decision evaluation, and similar purposes, or abandon the use of the QoE measurements, resulting in inefficient use of network resources.

[0071] Some techniques and apparatus described herein enable one or more RAN entities connected to or otherwise associated with a UE operating in dual connectivity mode to configure, receive and / or use QoE measurements. More specifically, some techniques and apparatus described herein implement RVQoE metrics so that the measurements do not need to be parsed, decoded, etc. in order to utilize the QoE measurements at one or more RAN entities. Some techniques and apparatus described herein enable one or more RAN entities (e.g., MN and SN) operating in dual connectivity mode to configure QoE measurements made by the UE to receive reports of the QoE measurements from the UE. In some aspects, the UE can receive one or more QoE and / or RVQoE configurations from at least one of the MN or SN associated with the dual connectivity mode of the UE. For example, the UE may receive a common QoE and / or RVQoE configuration applicable to both the MN and the SN from one of the MN or the SN, the UE may receive a MN-specific QoE and / or RVQoE configuration and / or a SN-specific QoE and / or RVQoE configuration from one of the MN or the SN, or the UE may receive a MN-specific QoE and / or RVQoE configuration from the MN and a SN-specific QoE and / or RVQoE configuration from the SN. In some aspects, the UE may send at least one QoE and / or RVQoE measurement report to at least one of the MN or the SN based at least in part on the one or more QoE and / or RVQoE configurations. In this manner, the MN and / or the SN may effectively configure the UE to perform QoE measurements. In addition, the MN and / or the SN may receive one or more RVQoE measurement reports from a UE operating in a dual connectivity mode, thereby enabling QoE-aware scheduling, QoE-aware load balancing, link adaptation, post-handover mobility decision evaluation, and similar determinations. Therefore, the UE, MN and / or SN can save computing, power, network and / or communication resources that might otherwise be consumed to parse, decode and analyze QoE measurement information, and one or more network entities can beneficially utilize QoE measurements to make determinations associated with resource scheduling, load balancing, link adaptation, mobility decisions and the like, thereby achieving efficient use of network resources.

[0072] As indicated above, Figure 5 Other examples can be found in the Figure 5 The examples described are different.

[0073] Figure 6 6 is a diagram illustrating an example 600 associated with configuration of QoE and / or RVQoE measurements for dual connectivity mode according to the present disclosure. Figure 6, UE 605 may communicate with MN 610 and SN 615. For example, UE 605 may operate in a dual connectivity mode (e.g., NRDC or other dual connectivity modes), in which UE 605 is connected or intended to be connected to both MN 610 and SN 615, and thus, in some aspects, UE 605 may communicate with each of MN 610 and SN 615 via one or more DRBs, SRBs, etc. UE 605 may correspond to any UE described herein, such as UE 120. In addition, MN 610 and SN 715 may correspond to any network entity described herein, such as base station 110, CU 310, DU 330, RU 340, RAN 520, or similar network entities. Although for ease of discussion, the RVQoE configuration, measurement, and reporting are described in conjunction with Figure 6 , but in some other aspects, UE 605 can be configured to measure and report QoE metrics in a substantially similar manner, such as in conjunction with Figures 7 to 10 Described in more detail.

[0074] As shown by reference numerals 620 and 625, UE 605 may receive one or more RVQoE configurations from MN 610 and / or SN 615, respectively. In some aspects, the one or more RVQoE configurations may configure one or more RVQoE measurements performed by UE 605, and in some aspects, may configure a period for performing the one or more RVQoE measurements. In some aspects, the configured RVQoE measurements may be associated with QoE metrics that UE 605 is capable of measuring. In this regard, in some aspects, UE 605 may send capability information to MN 610 and / or SN 615 indicating which QoE metrics UE 605 is capable of measuring. For example, the capability information may be combined with Figure 5 In some aspects, the configured RVQoE measurement may be associated with one or more of a buffer level metric, an average throughput metric, a playout delay metric, or a playlist metric.

[0075] The buffer level metric may indicate a list of buffer occupancy level measurements associated with one or more applications during playout at normal speed. The buffer level may be indicated in milliseconds, which may indicate the playout duration for which media data for all active media components is available starting from the current playout time. In some aspects, the buffer level metric may also include the measurement time of the buffer level. The average throughput metric may indicate the average throughput observed by the client during the measurement interval. The playout delay metric may indicate the time in milliseconds from the acquisition of the first media segment or sub-segment, and the time to retrieve the media from the client buffer. And the playlist metric may indicate a list of playback periods, which may be the time interval between a user action and the end of playback or a failure that stops playback (whichever occurs first).

[0076] In some aspects, the UE 605 may receive one or more RVQoE configurations from only one of the MN 610 or the SN 615, while in some other aspects, the UE 605 may receive one or more RVQoE configurations from both the MN 610 (as indicated by reference numeral 620) and the SN 615 (as indicated by reference numeral 625). For example, in some aspects, the UE 605 may receive a common RVQoE configuration from the MN 610. The common RVQoE configuration may be an RVQoE configuration that is applicable to both MN connectivity and SN connectivity and does not additionally include a MN-specific component or a SN-specific component. Figure 7 Aspects of a common RVQoE configuration are described in more detail.

[0077] In some other aspects, the one or more RVQoE configurations received by UE 605 may include a MN-specific RVQoE configuration and a SN-specific RVQoE configuration. That is, the one or more RVQoE configurations may include a configuration of RVQoE measurements and / or metrics requested by MN 610 (e.g., a MN-specific RVQoE configuration) and a configuration of RVQoE measurements and / or metrics requested by SN 615 (e.g., a SN-specific RVQoE configuration). In these aspects, MN 610 may provide information to SN 615, which SN 615 uses to generate an SN-specific RVQoE configuration, which is sometimes referred to herein as RVQoE assistance information. For example, in some aspects, the SN-specific RVQoE configuration may be based at least in part on a list of available RVQoE configurations provided by MN 610 to SN 615. In conjunction with Figures 7 to 10 Further details regarding RVQoE assistance information are described.

[0078] In some aspects, the UE 605 may receive the MN-specific RVQoE configuration and the SN-specific RVQoE configuration from a single RAN node (e.g., from one of the MN 610 or the SN 615) and / or in a single message (e.g., the message indicated by reference numeral 620 or one of the messages indicated by reference numeral 625), while in some other aspects, the MN-specific RVQoE configuration and the SN-specific RVQoE configuration may be received by the UE 605 from multiple RAN nodes (e.g., from both the MN 610 and the SN 615) and / or in multiple messages (e.g., in both the message indicated by reference numeral 620 and the message indicated by reference numeral 625). For example, in some aspects, the SN 615 may send the SN-specific RVQoE configuration to the MN 610, and the MN 610 may accordingly send the MN-specific RVQoE configuration and the SN-specific RVQoE configuration to the UE 605 via the message indicated by reference numeral 620 (e.g., in some aspects, the MN-specific RVQoE configuration and the SN-specific RVQoE configuration may be received from the MN 610). In these aspects, the SN 615 may send the SN-specific RVQoE configuration information to the MN 610 via an Xn Application (XnAP) protocol information element (IE), and the MN 610 may generate the one or more RVQoE configurations based at least in part on the SN-specific RVQoE configuration information contained in the XnAP protocol IE. Alternatively, the SN 615 may send the SN-specific RVQoE configuration to the MN 610 via a cell group (CG) container, and the MN 610 may forward the CG container (including the SN-specific RVQoE configuration) to the UE 605 via the message indicated by reference numeral 620. In conjunction with Figures 8 to 10 Aspects in which a MN-specific RVQoE configuration and a SN-specific RVQoE configuration may be received from the MN 610 are described in more detail.

[0079] In some other aspects, the SN 615 may send the SN-specific RVQoE configuration directly to the UE 605 via the message indicated by reference numeral 625, and the MN 610 may send the MN-specific RVQoE configuration to the UE 605 via the message indicated by reference numeral 620 (e.g., in some aspects, receive the MN-specific RVQoE configuration from the MN 610 and receive the SN-specific RVQoE configuration from the SN 615). For example, the SN 615 may send the SN-specific RVQoE configuration to the UE 605 via SRB3, etc.

[0080] Additionally or alternatively, the MN 610 may generate a MN-specific RVQoE configuration based at least in part on the RVQoE assistance received from the UE 605, and / or the SN 615 may generate a SN-specific RVQoE configuration based at least in part on the RVQoE assistance received from the UE 605. For example, the UE 605 may send an indication to one or both of the MN 610 and the SN 615 that a first set of one or more RVQoE configurations is associated with the MN 610 and a second set of one or more RVQoE configurations is associated with the SN 615. In these aspects, the MN-specific RVQoE configuration and / or the SN-specific RVQoE configuration may be based at least in part on the UE providing an indication that the first set of one or more RVQoE configurations is associated with the MN and the second set of one or more RVQoE configurations is associated with the SN. Figures 8 to 10 Aspects of receiving MN-specific RVQoE configuration and SN-specific RVQoE configuration from MN 610 and SN 615, respectively, are described in more detail.

[0081] As indicated by reference numeral 630, in some aspects, the UE 605 may collect at least one RVQoE metric based at least in part on one or more RVQoE configurations received from the MN 610 and / or the SN 615. For example, and as described above, the UE 605 may collect one or more of a buffer level metric, an average throughput metric, a playout delay metric, a playlist metric, or another RVQoE metric. Further, in some aspects, the UE 605 may determine whether each RVQoE configuration is associated with one of MN connectivity or SN connectivity. In other words, the UE 605 may determine whether an application associated with each collected RVQoE metric is operating on a MN interface or a SN interface. In conjunction with Figures 7 to 10 Aspects of determining whether each RVQoE configuration is associated with one of MN connectivity or SN connectivity are described in more detail.

[0082] As shown by reference numerals 635 and 640, in some aspects, the UE 605 may send at least one RVQoE measurement report based at least in part on one or more RVQoE configurations to at least one of the MN 610 or the SN 615. In some aspects, the UE 605 may send the one or more RVQoE measurement reports to only one of the MN 610 or the SN 615, while in some other aspects, the UE 605 may send the one or more RVQoE measurement reports to the MN 610 (as shown by reference numeral 635) and send the one or more RVQoE measurement reports to the SN 615 (as shown by reference numeral 640). For example, the UE 605 may send the RVQoE measurement report associated with an application operating on the MN interface to the MN 610 (as shown by reference numeral 635), and the UE 605 may send the RVQoE measurement report associated with an application operating on the SN interface to the SN 615 (as shown by reference numeral 640).

[0083] In aspects of sending the one or more RVQoE measurement reports only to one of the MN 610 or the SN 615, the UE 605 may provide interface information so that one of the MN 610 or the SN 615 may forward the applicable RVQoE measurement report to the other of the MN 610 or the SN 615. For example, the at least one RVQoE measurement report may include a first RVQoE measurement report associated with the MN 610 and a second RVQoE measurement report associated with the SN 615. In some aspects, the UE 605 may send the first RVQoE measurement report and the second RVQoE measurement report to the MN 610, and may additionally send at least one of interface information or bearer information indicating that the first RVQoE measurement report is associated with the MN 610 and / or the second RVQoE measurement report is associated with the SN 615. The at least one interface information or bearer information may be any information used by the MN 610 to map the measurement report to MN connectivity and / or SN connectivity. For example, at least one of the interface information or the bearer information may include at least one of: an indication of one of MN connectivity or SN connectivity associated with each RVQoE measurement report, an indication of one of an MCG bearer or an SCG bearer associated with each RVQoE measurement report, an indication of one of an MCG branch of a split bearer or an SCG branch of a split bearer associated with each RVQoE measurement report, a bearer identifier associated with each RVQoE measurement report, a packet data unit (PDU) session identifier associated with each RVQoE measurement report, or a quality of service (QoS) flow identifier associated with each RVQoE measurement report. In this way, the MN 610 can determine which RVQoE measurement reports are applicable to the SN connectivity and, accordingly, forward the applicable RVQoE measurement reports to the SN 615. In conjunction with Figures 7 to 10 Steps 7, 8, and 9a of EMBODIMENT 3 describe aspects of mapping RVQoE measurement reports to each of MN 610 and SN 615 and forwarding applicable measurement reports to SN 615 in more detail.

[0084] In some other aspects, the UE 605 may determine which RVQoE configurations are applicable to each of the MN 610 and the SN 615 (as described in conjunction with reference numeral 630), and may therefore directly send an RVQoE measurement report associated with MN connectivity to the MN 610, and send an RVQoE measurement report associated with SN connectivity to the SN 615. In other words, in some aspects, the at least one RVQoE measurement report may include a first RVQoE measurement report associated with the MN 610 and a second RVQoE measurement report associated with the SN 615, and the UE 605 may send the first RVQoE measurement report to the MN 610, and send the second RVQoE measurement report to the SN 615. Figures 7 to 10 Steps 7, 8, and 9b of EMBODIMENT 3 describe aspects of mapping RVQoE measurement reports to each of MN 610 and SN 615 and sending applicable measurement reports to MN 610 and SN 615 in more detail.

[0085] In some aspects, one or more of a RAN node (e.g., MN 610 or SN 615), a RVQoE configuration, an application operating at UE 605, or a RVQoE measurement report and / or metric may be associated with an RRC identifier to map the RVQoE measurement report to the corresponding connectivity, etc. For example, in some aspects, the one or more RVQoE configurations may include a MN-specific RVQoE configuration and an SN-specific RVQoE configuration, as described. In these aspects, the MN-specific RVQoE configuration may be associated with a first set of one or more RRC identifiers, and the SN-specific RVQoE configuration may be associated with a second set of one or more RRC identifiers. In some aspects, the RRC identifier associated with the MN 610 and / or the MN-specific RVQoE configuration may not overlap with the RRC identifier associated with the SN 615 and / or the SN-specific RVQoE configuration, while in some other aspects, one or more RRC identifiers associated with the MN 610 and / or the MN-specific RVQoE configuration may overlap with one or more RRC identifiers associated with the SN 615 and / or the SN-specific RVQoE configuration.

[0086] For example, in some aspects, a first set of one or more RRC identifiers (e.g., a set of RRC identifiers associated with a MN-specific RVQoE configuration) may include a first RRC identifier, and a second set of one or more RRC identifiers (e.g., a set of RRC identifiers associated with a SN-specific RVQoE configuration) may include a second RRC identifier different from the first RRC identifier. In these aspects, the UE 605 may report RVQoE measurements to each of the MN 610 and the SN 615 only when the corresponding MN / SN-specific RVQoE configuration indicates an RRC identifier and the RRC identifier is associated with an application operating on the corresponding MN / SN interface. In other words, in some aspects, the UE 605 may report a first RVQoE measurement report associated with the first RRC identifier to the MN based at least in part on the application associated with the first RRC identifier being associated with MN connectivity, and / or the UE 605 may report a second RVQoE measurement report associated with the second RRC identifier to the SN based at least in part on the application associated with the second RRC identifier being associated with SN connectivity.

[0087] In some aspects, when the MN / SN-specific RVQoE configuration indicates an RRC identifier, but the RRC identifier is associated with an application operating on another interface, the UE 605 may forgo reporting the RVQoE measurement report, or may report the RVQoE measurement report to another RAN node (e.g., the other of the MN 610 or the SN 615). In other words, in some aspects, the UE 605 may forgo reporting a first RVQoE measurement report associated with a second RRC identifier (e.g., an RRC identifier indicated by the SN-specific RVQoE configuration) based at least in part on the application associated with the second RRC identifier being associated with MN connectivity, or the UE 605 may report the first RVQoE measurement report associated with the second RRC identifier to the MN 610 based at least in part on the application associated with the second RRC identifier being associated with MN connectivity. In aspects where the UE 605 reports the RVQoE measurement report to another RAN node, the UE 605 may indicate that the RVQoE measurement report is configured by a different RAN node. Returning to the above example, if UE 605 reports a first RVQoE measurement report associated with a second RRC identifier to MN 610 based at least in part on an application associated with the second RRC identifier being associated with MN connectivity, UE 605 may also indicate that the first RVQoE measurement report is configured by SN 615 (e.g., by an SN-specific RVQoE configuration indication).

[0088] Alternatively, and as described, in some aspects, one or more RRC identifiers associated with the MN 610 and / or the MN-specific RVQoE configuration may overlap with one or more RRC identifiers associated with the SN 615 and / or the SN-specific RVQoE configuration. For example, both the first set of one or more RRC identifiers (e.g., the set of RRC identifiers associated with the MN-specific RVQoE configuration) and the second set of one or more RRC identifiers (e.g., the set of identifiers associated with the SN-specific RVQoE configuration) may include the first RRC identifier. In these aspects, the UE 605 may use only the RVQoE configuration from the predetermined RAN node (e.g., the MN 610), or may use only the most recently received RVQoE configuration, or may determine which RVQoE configuration to use for each RVQoE metric based at least in part on the connectivity of the application associated with the RVQoE metric, etc.

[0089] More specifically, in some aspects, when both the first set of one or more RRC identifiers and the second set of one or more RRC identifiers include the first RRC identifier, the UE 605 may send a MN-specific RVQoE configuration (e.g., a configuration of a predetermined node may be sent, in this example, the predetermined node is MN 610) from the AS layer of the UE 605 to the APP layer of the UE 605. Alternatively, when both the first set of one or more RRC identifiers and the second set of one or more RRC identifiers include the first RRC identifier, the UE 605 may send a most recently received RVQoE configuration of a MN-specific RVQoE configuration or a SN-specific RVQoE configuration from the AS layer of the UE 605 to the APP layer of the UE 605. Alternatively, when both the first set of one or more RRC identifiers and the second set of one or more RRC identifiers include the first RRC identifier, UE 605 may send an MN-specific RVQoE configuration and an SN-specific RVQoE configuration from the AS layer of UE 605 to the APP layer of UE 605, and UE 605 (e.g., the APP layer of UE 605) may determine whether to use the MN-specific RVQoE configuration and the SN-specific RVQoE configuration based at least in part on the connectivity of an application associated with the first RRC identifier.

[0090] In these aspects, the UE 605 may report the RVQoE measurement report only to each of the MN 610 and the SN 615 associated with the corresponding connectivity. For example, in some aspects, both the first set of one or more RRC identifiers and the second set of one or more RRC identifiers may include a first RRC identifier and a second RRC identifier. In these aspects, the UE 605 may report a first RVQoE measurement report associated with the first RRC identifier to the MN 610 based at least in part on an application associated with the first RRC identifier being associated with MN connectivity, and the UE 605 may report a second RVQoE measurement report associated with the second RRC identifier to the SN 615 based at least in part on an application associated with the second RRC identifier being associated with SN connectivity. In conjunction with Fig. 9 Various aspects of RRC identifier processing are described in more detail.

[0091] Based at least in part on the UE 605 operating in the dual connectivity mode receiving the RVQoE configuration and reporting the RVQoE measurement report, the UE 605, the MN 610, and / or the SN 615 can save computational, power, network, and / or communication resources that might otherwise be consumed to parse, decode, and forward the QoE measurement report when needed by one of the MN 610 or the SN 615. For example, based at least in part on the UE 605 receiving the RVQoE configuration and reporting the RVQoE measurement report to the MN 610 and / or the SN 615, the UE 605, the MN 610, and / or the SN 615 can efficiently and effectively utilize certain RVQoE measurements for QoE-aware scheduling, QoE-aware load balancing, link adaptation, post-handover mobility decision evaluation, etc., which can save resources that would otherwise be consumed to parse, decode, and forward the QoE measurements at the AN node.

[0092] As indicated above, Figure 6 Other examples can be found in the Figure 6 The examples described are different.

[0093] Figure 7 is a diagram illustrating another example 700 associated with configuration of QoE and / or RVQoE measurements for dual connectivity mode according to the present disclosure. Figure 7As shown, the UE APP layer or entity (e.g., UE APP 705) can communicate with the UE AS layer or entity (e.g., UE AS 710), wherein the UE APP 705 and the UE AS 710 are associated with the same UE (e.g., UE 605). In addition, the UE 605 can operate in a dual connectivity mode (e.g., NRDC mode, etc.), thereby communicating with the SN 720 (e.g., base station 110, CU 310, DU 330 and RU 340, SN 615 or similar network entity) and the MN 725 (e.g., base station 110, CU 310, DU 330 and RU 340, MN 610 or similar network entity) through a wireless network (e.g., wireless network 100). In some aspects, the SN 720 and / or the MN 725 can correspond to a RAN entity (e.g., an NG-RAN entity), such as in conjunction with Figure 5 The RAN entity 520 is depicted. The UE 605, SN 720 and / or MN 725 may also communicate with components of the core network such as an MCE entity (eg, MCE 730).

[0094] like Figure 7 As shown in step 1 of , in some aspects, the MCE 730 may configure the MN 725 with a QoE configuration. The QoE configuration may include a plurality of different QoE measurements and / or metrics for the UE 605 to measure. In some aspects, collecting QoE measurements and / or metrics may be referred to as QoE Measurement Collection (QMC), and thus, in some aspects, such as Figure 7 The configuration and / or related parameters and information shown in step 1 of the embodiment may be referred to as QMC information. Figure 5 As described, if the UE 605 measures such QoE measurements and / or metrics without additional configuration (e.g., without receiving the one or more RVQoE configurations), the QoE measurements and / or metrics may be transparent to the MN 725 and / or SN 720 because they may be reported in a compressed XML file, etc. In this regard, the MN 725 and / or SN 720 may additionally configure the UE 605 with one or more RVQoE configurations so that the UE 605 may provide the RVQoE measurements and / or metrics to the MN 725 and / or SN 720. In this regard, the QoE configuration shown at step 1 may include RVQoE assistance information. The information may indicate certain parameters to enable the MN 725 and / or SN 720 to generate one or more RVQoE configurations, such as a list of available QoE metrics that may be executed at the UE 605.

[0095] For example, in some aspects, a RAN entity (e.g., MN 725 and / or SN 720) may be able to configure RVQoE measurements for a given service type only if application layer QoE for the same service type has been configured by QoE configuration from MCE 730, etc. Additionally or alternatively, a RAN entity (e.g., MN 725 and / or SN 720) may be able to configure RVQoE measurements only for metrics specified by a wireless communication standard, such as metrics specified by 3GPP Technical Specification Group Service and System Aspects (SA) Working Group 4 (WG4) (e.g., SA4), and these metrics may be indicated by RVQoE assistance information or otherwise indicated to MN 725 and / or SN 720. Additionally or alternatively, the RAN entities (e.g., MN 725 and / or SN 720) may only be able to configure RVQoE measurements that UE 605 is capable of performing, and thus, in these aspects, UE 605 may send capability information to one or both of MN 725 or SN 720, such as in conjunction with Figure 5 As described in conjunction with step 0, and the one or more RVQoE configurations may be based at least in part on the capability information.

[0096] exist Figure 7 In the example shown, MN 725 can configure UE 605 itself (e.g., without input from SN 720 and / or without receiving configuration information from SN 720). Figure 7 As shown in step 4 of , the MN 725 may generate one or more QoE configurations (e.g., configurations of QoE measurements, which in some aspects may be transparent to the RAN node) and / or one or more RVQoE configurations (e.g., configurations of RVQoE measurements), which may be based at least in part on the QMC information and / or RVQoE assistance information received from the MCE 730. Figure 7As shown in step 2 of , MN 725 may send an SN add request to SN 720, which may be used to add SN 720 as a secondary node for dual connectivity (if SN 720 is not already connected to UE 605). In some aspects, the SN add request may include certain configuration information to add SN 720 as a secondary node for the purpose of dual connectivity, such as RRC configuration information, radio bearer configuration information, UE capability information, security information such as for the purpose of enabling SRB3, and the like. In addition, in aspects where a QMC activation IE has been previously received for UE 605, the QMC activation IE may be included in the SN add request, and if the QMC activation IE is included in the SN add request, the SN 720 may initiate the requested QMC function if supported. In some aspects, SN 720 may provide an SN add request confirmation (ACK) message, as shown in step 3, which may include information about radio resources and bearers, RRC configuration information, and the like to be sent to UE 605. Although in Figure 7 In the example shown, step 4 is shown as being performed before steps 2 and 3, but in some other aspects, steps 2 and 3 may be performed before step 4 without departing from the scope of the present disclosure.

[0097] In addition, in some aspects, as part of the SN add request or using additional signaling, the MN 725 may signal the SN 720 to request that the SN 720 initiate a QoE measurement procedure (sometimes referred to as a QMC session) for the UE 605. More specifically, the MN 725 may initiate the QMC start procedure by sending a QMC start message for a specific UE 605 to the SN 720. In some aspects, upon receiving the QMC start message, the SN 720 may initiate the requested QMC session. Relatedly, in some aspects, the MN 725 may use a deactivation QMC procedure to request the SN 720 to stop the QMC session for the indicated QoE reference. More specifically, the MN 725 may initiate the deactivation QMC procedure by sending a deactivation QMC message for a specific UE 605 to the SN 720. In some aspects, upon receiving the deactivation QMC message, the SN 720 may stop the QMC session for the indicated QoE reference. In some aspects, the deactivate QMC message may be part of a SN modification or release procedure.

[0098] Additionally or alternatively, in some aspects, a management-based QoE activation process may be utilized, such as the above in combination with Figure 5In some aspects, when the management-based QoE activation process is implemented, the SN 720 may send a cell service QMC message to the MN 725. The cell service QMC message may include certain QMC information, such as one or more QoE references, one or more RRC identifiers, privacy information, etc. In some aspects, upon receiving the cell service QMC message, the MN 725 may send a cell service QMC message (including the one or more QoE references, one or more RRC identifiers, privacy information, etc.) to the core network associated with the UE 605. In these aspects, the core network may forward certain information, such as the one or more QoE references and the UE 605 identity, to the MCE 730.

[0099] Additionally or alternatively, in some aspects, the SN 720 may utilize a cell service QMC procedure (sometimes referred to as a cell service tracking procedure) to provide certain information (such as one or more QoE references, one or more RRC identifiers, privacy information, etc.) to the MN 725. For example, the SN 720 may send a cell service QMC message including relevant information to the MN 725. In some aspects, if a privacy indicator IE is included in the cell service QMC message, the MN 725 may consider the information for the purpose of anonymization of the QMC data.

[0100] As shown in step 5, MN 725 may send an RRC reconfiguration message to UE 605 (more specifically, to UE AS 710). Figure 7In some aspects, the RRC reconfiguration message is shown as being provided through MN connectivity, but in some other aspects, the RRC reconfiguration message may be sent through SN connectivity and / or using split bearers. In aspects of sending the RRC reconfiguration information through SN connectivity, the MN 725 may provide the RRC message to the SN 720 through XnAP as a container sent through SN connectivity, and / or the MN 725 may provide the generated QoE and / or RVQoE configuration to the SN 720 through XnAP as a container for incorporation into the RRC message to be transmitted through SN connectivity. In some aspects, the RRC reconfiguration message may include the SN 720 RRC configuration information so that the UE 605 connects to the SN 720. Additionally or alternatively, the RRC reconfiguration message may include the one or more QoE and / or RVQoE configurations generated by the MN 725 at step 4. As shown in step 6, the UE AS 710 may send the one or more QoE and / or RVQoE configurations to the UE APP 705. The UE APP 705 may then perform one or more measurements based at least in part on the QoE and / or RVQoE configuration (e.g., the UE APP 705 may collect one or more QoE metrics and / or one or more RVQoE metrics). Figure 6 As described, the UE APP 705 may perform one or more of buffer occupancy level measurements (which may include measurement time of buffer level), average throughput measurements, playout delay measurements, playlist measurements, etc. during playout at normal speed.

[0101] As shown in step 7, the UE APP 705 may report the one or more QoE and / or RVQoE measurements and / or metrics to the UE AS 710 via a measurement report, etc. In some aspects, the UE APP 705 may also indicate certain identifiers, etc., for determining the interface and / or connectivity (e.g., MN connectivity or SN connectivity) associated with each QoE and / or RVQoE measurement and / or metric. For example, the UE APP 705 may indicate a PDU session identifier associated with each QoE and / or RVQoE measurement and / or metric, a QoS flow identifier associated with each QoE and / or RVQoE measurement and / or metric, etc. Then, as shown in step 8, the UE AS 710 may determine the interface information and / or connectivity (e.g., MN connectivity or SN connectivity) associated with each QoE and / or RVQoE measurement and / or metric. For example, the UE AS 710 may determine that a first set of one or more QoE and / or RVQoE measurements and / or metrics are associated with MN connectivity and / or MN interfaces, and a second set of one or more QoE and / or RVQoE measurements and / or metrics are associated with SN connectivity and / or SN interfaces. In some aspects, the UE AS 710 may determine the associated interface and / or connectivity associated with each QoE and / or RVQoE metric based at least in part on information provided by the UE APP 705. For example, the UE AS 710 may map a PDU session identifier and / or QoS flow identifier provided by the UE APP 705 to each connectivity and / or interface.

[0102] like Figure 7As shown in steps 9a and 9b in FIG. 1 , UE 605 (more specifically, UE AS 710) may report the one or more QoE and / or RVQoE measurements and / or metrics to one or both of MN 725 and SN 720. First, in an alternative form as shown in step 9a, UE AS 710 may send one of the one or more QoE and / or RVQoE measurements and / or metrics to MN 725. For example, in some aspects, a report for sending the one or more QoE and / or RVQoE measurements and / or metrics to MN 725 may be referred to as a measurement application layer report (meaAppLayerReport). The measurement report (e.g., a measurement application layer report) may include one or more QoE and / or RVQoE measurements and / or metrics and interface information so that the MN 725 determines which of the one or more QoE and / or RVQoE measurements and / or metrics are associated with the MN 725 and which of the one or more QoE and / or RVQoE measurements and / or metrics are associated with the SN 720. The interface information may be any information indicating which QoE and / or RVQoE measurements and / or metrics are associated with each of the MN 725 or the SN 720. For example, the interface information may include an indication of whether each QoE and / or RVQoE measurement and / or metric is associated with MN connectivity (and thus associated with the MN 725) or associated with SN connectivity (and thus associated with the SN 720). Additionally or alternatively, the interface information may include an indication of whether each QoE and / or RVQoE measurement and / or metric is associated with an MCG bearer (and thus associated with MN 725) or an SCG bearer (and thus associated with SN 720). Additionally or alternatively, the interface information may include an indication of whether each QoE and / or RVQoE measurement and / or metric is associated with an MCG leg of a split bearer (and thus associated with MN 725) or an SCG leg of a split bearer (and thus associated with SN 720). Additionally or alternatively, the interface information may include an indication of a bearer identifier associated with each QoE and / or RVQoE measurement and / or metric, which indication may then be mapped by MN 725 to one of MN 725 or SN 720. Additionally or alternatively, the interface information may include an indication of a PDU session identifier associated with each QoE and / or RVQoE measurement and / or metric, which may then be mapped by the MN 725 to one of the MN 725 or the SN 720. Additionally or alternatively, the interface information may include an indication of a QoS flow identifier associated with each QoE and / or RVQoE measurement and / or metric, which may then be mapped by the MN 725 to one of the MN 725 or the SN 720.Based at least in part on the interface information sent by the UE AS 710, the MN 725 may then determine which, if any, of the QoE and / or RVQoE measurements and / or metrics are associated with the SN 720 (e.g., which measurements and / or metrics are attributable to SN connectivity), and forward the measurements and / or metrics to the SN 720. More specifically, in some aspects, the MN 725 may forward applicable QoE and / or RVQoE measurements and / or metrics to the SN 720 using an XnAP protocol or the like.

[0103] In such Figure 7 In an alternative form as shown in step 9b of , UE AS 710 may send a first set of one or more QoE and / or RVQoE measurements and / or metrics to MN 725, and send a second set of one or more QoE and / or RVQoE measurements and / or metrics to SN 720. In these aspects, based at least in part on determining interface information associated with each QoE and / or RVQoE measurement or metric, as described above in conjunction with step 8, UE AS 710 may forward QoE and / or RVQoE measurements and / or metrics associated with MN connectivity directly to MN 725, and may forward QoE and / or RVQoE measurements and / or metrics associated with SN connectivity directly to SN 720. UE AS 710 may achieve this using a first measurement application layer report sent to MN 725 and a second measurement application layer report sent to SN 720.

[0104] In some aspects, the UE AS 710 may use an SCG bearer to report QoE and / or RVQoE measurements to the SN 720. For example, in some aspects, the UE AS 710 may use an SRB5 bearer to report QoE and / or RVQoE measurements to the SN 720. In aspects of reporting QoE measurements to the SN 720 using an SRB5 bearer, etc., the SN 720 may forward the QoE measurements directly to the MCE 730, or the SN 720 may forward the QoE report RRC message to the MN 725 using an XnAP message (sometimes referred to as an RRC transfer message), and then the MN 725 may forward the QoE measurements to the MCE 730.

[0105] Additionally or alternatively, in some aspects, the UE AS 710 may use a split bearer (which may be associated with SRB4 and / or SRB5) to report QoE and / or RVQoE measurements. For example, in some aspects, the MN 725 or the SN 720 may send a configuration of a split bearer to the UE 605 for QoE and / or RVQoE reporting. In some aspects, the configuration may indicate which branch (e.g., MCG branch and / or SCG branch) should be used for QoE and / or RVQoE reporting. Additionally or alternatively, the configuration may indicate which measurements (e.g., which QoE and / or RVQoE configurations) should be reported using the split bearer.

[0106] In some aspects, a RAN node (e.g., MN 725 and / or SN 720) may initiate suspension (or alternatively, resumption) of QoE and / or RVQoE reporting based at least in part on the RAN node being overloaded due to QoE and / or RVQoE reporting. For example, if MN 725 and / or SN 720 becomes overloaded due to QoE and / or RVQoE reporting, MN 725 and / or SN 720 may send a message to UE 605 to suspend QoE and / or RVQoE collection and / or reporting, and may later send a message to UE 605 to resume QoE and / or RVQoE collection and / or reporting when MN 725 and / or SN 720 is no longer overloaded. In some aspects, one of the RAN nodes may send such a suspension or resumption indication to another of the RAN nodes. For example, one of the SN 720 or the MN 725 may send a message to the other of the SN 720 or the MN 725 indicating that QoE reporting should be suspended or resumed. The other of the SN 720 or the MN 725 (e.g., the RAN node that receives the indication) may then send a suspend or resume request to the UE 605 indicating that the UE 605 should suspend or resume the QoE and / or RVQoE measurements indicated by the one of the SN 720 or the MN 725 (e.g., the RAN node that initiated the indication). Additionally or alternatively, the other of the SN 720 or the MN 725 (e.g., the RAN node that receives the indication) may reconfigure the bearer associated with the QoE and / or RVQoE configuration indicated by the suspend or resume request. For example, in the aspect that SN 720 initiates a suspension request for certain QoE and / or RVQoE measurements, MN 725 may reconfigure the bearer associated with those QoE and / or RVQoE measurements as an MCG bearer so that UE 605 will start forwarding the certain QoE and / or RVQoE measurements to MN 725.

[0107] In this regard, Figure 7The aspects of configuration of QoE and / or RVQoE measurements for dual connectivity mode shown in enable one or more RAN entities associated with a UE operating in dual connectivity mode to configure and / or use QoE and / or RVQoE measurements.

[0108] As indicated above, Figure 7 Other examples can be found in the Figure 7 The examples described are different.

[0109] Figure 8 is a diagram illustrating another example 800 associated with configuration of QoE and / or RVQoE measurements for dual connectivity mode according to the present disclosure.

[0110] exist Figure 8 In the example shown, MN 725 may generate one or more QoE and / or RVQoE configurations that include one or more QoE and / or RVQoE configurations associated with SN 720. In other words, rather than generating a common QoE and / or RVQoE configuration, such as in conjunction with Figure 7 As described, in this aspect, the MN 725 may generate one or more QoE and / or RVQoE configurations, which include a MN component (e.g., a MN-specific QoE and / or RVQoE configuration) and a SN component (e.g., a SN-specific QoE and / or RVQoE configuration). More specifically, as shown in step 1, the MN 725 may receive QoE configuration information (e.g., QMC information) from the MCE 730, including RVQoE assistance information, as described above. In this aspect, the MN 725 may provide the RVQoE assistance information to the SN 720 as part of the SN add request, as shown in step 2. The MN 725 may provide the RVQoE assistance information to the SN 720 using the XnAP protocol, etc. The SN add request may include additional information for adding the SN 720 as a secondary node for dual connectivity purposes (e.g., RRC configuration information, radio bearer configuration information, UE capability information, security information such as for the purpose of enabling SRB3, etc.), and / or may include a QMC activation IE, as described above in conjunction with Figure 7 described.

[0111] As shown in step 3, the SN 720 may provide the MN 725 with the SN-specific QoE and / or RVQoE configuration, which may be sent as part of the SN add request ACK message. In some aspects, the SN-specific QoE and / or RVQoE configuration may include the configuration of the QoE and / or RVQoE measurements and / or metrics requested by the SN 720 from the UE 605, and / or the period of the requested QoE and / or RVQoE measurements and / or metrics. The ACK message may include the configuration of the QoE and / or RVQoE measurements and / or metrics requested by the SN 720 from the UE 605. Figure 7 The additional information, such as information about radio resources and bearers, and / or RRC configuration information to be sent to UE 605. In addition, in some aspects, SN 720 may send SN-specific QoE and / or RVQoE configuration information to MN 725 using XnAP IE, etc., while in some other aspects, SN 720 may send SN-specific QoE and / or RVQoE configuration information to MN 725 in a CG container.

[0112] As shown in step 4, the MN 725 may generate one or more QoE and / or RVQoE configurations taking into account the SN-specific QoE and / or RVQoE configuration information. For example, insofar as the SN 720 sends the SN-specific QoE and / or RVQoE configuration information to the MN 725 using an XnAP IE or the like (and thus the SN-specific QoE and / or RVQoE configuration information is visible to the MN 725), the MN 725 may generate the one or more QoE and / or RVQoE configurations taking into account the SN-specific QoE and / or RVQoE configuration information, such as by generating QoE and / or RVQoE configurations that configure the QoE and / or RVQoE measurements and / or metrics and / or corresponding periods that the SN 720 requests from the UE 605, in addition to the QoE and / or RVQoE measurements and / or metrics and / or corresponding periods that the MN 725 requests from the UE 605. In the aspect that SN 720 sends SN-specific QoE and / or RVQoE configuration information to MN 725 using a CG container, etc. (and thus, the SN-specific QoE and / or RVQoE configuration information may be transparent to MN 725), MN 725 may forward the CG container to UE 605, and thus, at step 4, MN 725 may generate one or more QoE and / or RVQoE configurations including the QoE and / or RVQoE measurements and / or metrics and / or corresponding periods that MN 725 is requesting from UE 605.

[0113] As shown in step 5, MN 725 may send an RRC reconfiguration message to UE 605 (more specifically, to UE AS 710). Figure 7As described, in some aspects, the RRC reconfiguration message may include SN 720 RRC configuration information so that UE 605 is connected to SN 720, and additionally or alternatively, the RRC reconfiguration message may include the one or more QoE and / or RVQoE configurations generated by MN 725 at step 4 and / or provided to MN 725 at step 3. More specifically, in aspects where SN 720 sends SN-specific QoE and / or RVQoE configuration information to MN 725 using XnAP IE, etc., the one or more QoE and / or RVQoE configurations provided at step 5 may include QoE and / or RVQoE configurations that configure the QoE and / or RVQoE measurements and / or metrics and corresponding periods requested by MN 725 from UE 605. In the aspect where SN 720 sends SN-specific QoE and / or RVQoE configuration information to MN 725 using a CG container, etc., the one or more QoE and / or RVQoE configurations provided at step 5 may include the MN-specific QoE and / or RVQoE configurations generated at step 4, and the SN-specific QoE and / or RVQoE configurations in the CG container.

[0114] The UE AS 710 may send the one or more QoE and / or RVQoE configurations to the UE APP 705 (step 6), and the UE APP 705 may perform one or more measurements (e.g., collect one or more QoE and / or RVQoE metrics) based at least in part on the one or more QoE and / or RVQoE configurations, and may report the one or more QoE and / or RVQoE measurements and / or metrics to the UE AS 710 (step 7). These steps may be combined with the above Figure 7Steps 6 and 7 described above are performed in a substantially similar manner. In this regard, at step 7, the UE APP 705 may indicate certain identifiers, etc., for determining the interface and / or connectivity (e.g., MN connectivity or SN connectivity) associated with each QoE and / or RVQoE measurement and / or metric, such as a PDU session identifier associated with each QoE and / or RVQoE measurement and / or metric, a QoS flow identifier associated with each QoE and / or RVQoE measurement and / or metric, etc., as described. The UE AS 710 may determine the interface information and / or connectivity (e.g., MN connectivity or SN connectivity) associated with each QoE and / or RVQoE measurement and / or metric (step 8), and send a QoE and / or RVQoE measurement report and the associated interface information to the MN 725 (step 9a), or directly send a MN-applicable QoE and / or RVQoE measurement report to the MN 725, and directly send a SN-applicable QoE and / or RVQoE measurement report to the SN 720 (step 9b). Steps 8, 9a, and 9b may be combined with the above. Figure 7 Steps 8, 9a and 9b described are performed in a substantially similar manner.

[0115] As indicated above, Figure 8 Other examples can be found in the Figure 8 The examples described are different.

[0116] Fig. 9 is a diagram illustrating another example 900 associated with configuration of QoE and / or RVQoE measurements for dual connectivity mode according to the present disclosure.

[0117] exist Fig. 9 In the example shown, MN 725 and SN 720 may independently generate one or more QoE and / or RVQoE configurations, and / or MN 725 and SN 720 may independently configure UE 605. In other words, rather than MN 725 generating a common QoE and / or RVQoE configuration (e.g., in conjunction with Figure 7 ), or the MN 725 generates one or more QoE and / or RVQoE configurations including SN-specific QoE and / or RVQoE configuration components (such as in combination with Figure 8 As described above, in this regard, MN 725 and SN 720 may each generate one or more QoE and / or RVQoE configurations (e.g., MN 725 may generate MN-specific QoE and / or RVQoE configurations, and SN 720 may generate SN-specific QoE and / or RVQoE configurations), and / or MN 725 and SN 720 may configure UE 605, respectively.

[0118] More specifically, as shown in step 1, MN 725 may receive QoE configuration information (e.g., QMC information) from MCE 730, including RVQoE auxiliary information, such as in combination with Figure 7 and Figure 8 As described above. In this aspect, as shown in step 2a, the MN 725 may split the QoE reference between the MN 725 and the SN 720, and thus provide the QoE configuration information (in addition to the RVQoE assistance information) to the SN 720 as part of the SN add request (as shown in this aspect at step 2b). For example, the MN 725 may provide a list of UE application layer measurement configuration information items to the SN 720. In some aspects, each UE application layer measurement configuration information item may include one or more of a QoE reference, a service type, an MCE IP address, a slice range, an area range, drive test minimization (MDT) alignment information, an RRC identifier range that the SN 720 may allocate (described in more detail below), etc. In some aspects, the MN 725 may forward all of the UE application layer measurement configuration information items to the SN 720 to perform QoE configuration on all of the items, while in some other aspects, the MN 725 only forwards some of the UE application layer measurement configuration information items to the SN 720 to provide QoE configuration for a subset of these items. In some aspects, the SN 720 may determine which QMC is accepted and provide feedback to the MN 725 accordingly (e.g., using an SN Add Request ACK message, as shown at step 3). The SN Add Request may include additional information for adding the SN 720 as a secondary node for dual connectivity purposes (e.g., RRC configuration information, radio bearer configuration information, UE capability information, security information such as for the purpose of enabling SRB3, etc.), and / or may include a QMC Activation IE, as described above in conjunction with Figure 7 and Figure 8 described.

[0119] Additionally or alternatively, the SN add request may include a range of RRC identifiers. The RRC identifiers may be used to map certain QoE and / or RVQoE measurements and / or metrics to corresponding nodes (e.g., SN 720 or MN 725), as will be described more fully below. Thus, in some aspects, MN 725 may indicate to SN 720 via the SN add request a range of acceptable RRC identifiers (e.g., a set, a range, etc.) that SN 720 may use when generating an SN-specific QoE and / or RVQoE configuration. As shown in step 4 associated with SN 720, SN 720 may generate an SN-specific QoE and / or RVQoE configuration, which may include assigning one or more RRC identifiers to one or more requested QoE and / or RVQoE measurements and / or metrics. For example, SN 720 may assign a first RRC identifier to a first requested QoE and / or RVQoE measurement or metric, SN 720 may assign a second RRC identifier to a second requested QoE and / or RVQoE measurement or metric, and so on. As shown in step 3, SN 720 may send an SN add request ACK message to MN 725. Optionally, the SN add request ACK message may include an SN-specific QoE and / or RVQoE configuration. And as shown in step 4 associated with MN 725, MN 725 may generate an MN-specific QoE and / or RVQoE configuration, which may include assigning one or more RRC identifiers to one or more requested QoE and / or RVQoE measurements and / or metrics in a manner similar to that described in conjunction with SN 720. Although in Fig. 9 , MN 725 is shown as performing step 4 after receiving the SN add request ACK message, but in some other aspects, MN 725 may generate a MN-specific QoE and / or RVQoE configuration before receiving the SN add request ACK message (e.g., MN 725 may perform step 4 simultaneously with SN 720).

[0120] In this example, MN 725 and SN 720 may configure UE 605 with corresponding QoE and / or RVQoE configurations, respectively. Therefore, as shown in step 5 associated with MN 725, MN 725 may send an RRC reconfiguration message to UE 605 (more specifically, to UE AS 710), and as shown in step 5 associated with SN 720, SN 720 may send another RRC reconfiguration message to UE AS 710. As described above in conjunction with Figure 7 and Figure 8As described, each RRC reconfiguration message may include one or more QoE and / or RVQoE configurations, such as a MN-specific QoE and / or RVQoE configuration in the RRC reconfiguration message sent by the MN 725, and a SN-specific QoE and / or RVQoE configuration sent by the SN 720. Alternatively, a node may forward the MN-specific QoE and / or RVQoE configuration and the SN-specific QoE and / or RVQoE configuration to the UE 120 at step 5 (e.g., at step 5, the SN 720 may send the SN-specific QoE and / or RVQoE configuration to the MN 725 as part of the SN Add Request ACK message, and the MN 725 may send the MN-specific QoE and / or RVQoE configuration and the SN-specific QoE and / or RVQoE configuration to the UE 120).

[0121] The UE AS 710 may send the one or more QoE and / or RVQoE configurations to the UE APP 705 (step 6), and the UE APP 705 may perform one or more measurements based at least in part on the QoE and / or RVQoE configurations, and may report the one or more QoE and / or RVQoE measurements and / or metrics to the UE AS 710 (step 7). These steps may be combined with the above Figure 7 and Figure 8 Steps 6 and 7 described above are performed in a substantially similar manner. In this regard, at step 7, the UE APP 705 may indicate certain identifiers, etc., for determining the interface and / or connectivity (e.g., MN connectivity or SN connectivity) associated with each QoE and / or RVQoE measurement and / or metric, such as a PDU session identifier associated with each QoE and / or RVQoE measurement and / or metric, a QoS flow identifier associated with each QoE and / or RVQoE measurement and / or metric, etc., as described. The UE AS 710 may determine the interface information and / or connectivity (e.g., MN connectivity or SN connectivity) associated with each QoE and / or RVQoE measurement and / or metric.

[0122] In aspects where the SN 720 and / or MN 725 assign RRC identifiers to respective QoE and / or RVQoE configurations, the RRC identifiers may not overlap between the SN-specific QoE and / or RVQoE configurations and the MN-specific QoE and / or RVQoE configurations, or may overlap between the SN-specific QoE and / or RVQoE configurations and the MN-specific QoE and / or RVQoE configurations. For example, as described above in conjunction with the SN add request at step 2b, in some aspects the MN 725 may have provided the SN with a range of RRC identifiers such that the RRC identifiers assigned by the SN to the SN-specific QoE and / or RVQoE configurations do not overlap with the RRC identifiers assigned by the MN to the MN-specific QoE and / or RVQoE configurations. In these aspects, when determining the interface information at step 8, the UE 605 may determine the interface information on which the application for the reported QoE and / or RVQoE measurement is running, and then if the interface information for the measurement is aligned with the RAN node that provides the corresponding QoE and / or RVQoE configuration indicated by the RRC identifier, the measurement may be reported to the corresponding RAN node (e.g., MN 725 or SN 720). On the other hand, if the interface information for the measurement is not aligned with the RAN node that provides the corresponding QoE and / or RVQoE configuration indicated by the RRC identifier, the UE 605 may abandon the measurement report or report the measurement to the RAN node indicated by the interface information. In the latter case, the UE 605 may provide an indication to the RAN node that another RAN node provides the configuration corresponding to the reported measurement.

[0123] For example, MN 725 may provide MN-specific QoE and / or RVQoE configurations that configure QoE and / or RVQoE measurements and / or metrics associated with two RRC identifiers: RRC ID-1 and RRC ID-2 to UE 605. Similarly, SN 720 may provide SN-specific QoE and / or RVQoE configurations that configure QoE and / or RVQoE measurements and / or metrics associated with two non-overlapping RRC identifiers: RRCID-3 and RRC ID-4 to UE 605. If a first application associated with RRC ID-3 (in this example, which is indicated by the SN-specific QoE and / or RVQoE configuration) is running on the MN interface, and a second application associated with RRC ID-4 (in this example, which is indicated by the SN-specific QoE and / or RVQoE configuration) is running on the SN interface, the UE 605 may report the QoE and / or RVQoE measurements and / or metrics associated with RRC ID-4 to the SN because the RRC identifier is indicated by the SN-specific QoE and / or RVQoE configuration. For QoE and / or RVQoE measurements and / or metrics associated with RRC ID-3, UE 605 may forgo reporting QoE and / or RVQoE measurements and / or metrics because the application is running through MN connectivity, but the corresponding RRC identifier is not indicated by MN 725, or UE 605 may report QoE and / or RVQoE measurements and / or metrics to MN 725, optionally with SN 720 providing an indication of the configuration corresponding to the reported QoE and / or RVQoE measurements and / or metrics.

[0124] In some other aspects, the MN 725 may not provide the RRC identifier scope information to the SN 720 in conjunction with the SN add request and / or the RRC identifier associated with the SN-specific QoE and / or RVQoE configuration, otherwise the MN-specific QoE and / or RVQoE configuration may overlap. In other words, in some aspects, the UE 605 may receive the same RRC identifier from the MN 725 and the SN 720. In some aspects, when the QoE and / or RVQoE configurations include overlapping RRC identifiers, the UE AS 710 may forward only the QoE and / or QoE and / or RVQoE configurations associated with a predetermined RAN node (e.g., the MN 725) to the UE APP 705, may forward only the latest QoE and / or RVQoE configurations to the UE APP 705, or may forward both the QoE and / or RVQoE configurations to the UE APP 705, and the UE APP 705 may determine which QoE and / or RVQoE configuration should be used based on connectivity for the corresponding application or others.

[0125] For example, MN 725 may provide UE 605 with a MN-specific QoE and / or RVQoE configuration that configures QoE and / or RVQoE measurements and / or metrics associated with two RRC identifiers: RRC ID-1 and RRC ID-2. Similarly, SN 720 may provide UE 605 with an SN-specific QoE and / or RVQoE configuration that configures QoE and / or RVQoE measurements and / or metrics associated with RRC ID-1 and RRC ID-2. Accordingly, due to overlapping RRC identifiers, UE AS 710 may forward only the MN-specific QoE and / or RVQoE configuration to UE APP 705 (or alternatively, may forward only the SN-specific QoE and / or RVQoE configuration to UE APP 705). Alternatively, UE AS 710 may forward the latest (e.g., received later) QoE and / or RVQoE configuration to UE APP 705. In some other aspects, even if some configurations include overlapping RRC identifiers, the UE AS 710 may forward the QoE and / or RVQoE configurations to the UE APP 705, and if the UE APP 710 receives two QoE and / or RVQoE configurations with the same RRC identifier, the UE APP 710 may overwrite the first received QoE and / or RVQoE configuration with the later received QoE and / or RVQoE configuration. Alternatively, the UE AS 710 may forward the QoE and / or RVQoE configurations to the UE APP 705, and the UE APP 705 may determine that the MN-specific QoE and / or RVQoE configurations should be used for measurements associated with RRC ID-1 (because the first application is running on the MN interface), while the SN-specific QoE and / or RVQoE configurations should be used for measurements associated with RRC ID-2 (because the second application is running on the SN interface). When reporting QoE and / or RVQoE measurements and / or metrics, UE 605 may report QoE and / or RVQoE measurements and / or metrics associated with RRC ID-1 to MN 725 because a first application associated with RRC ID-1 is indicated by a MN-specific QoE and / or RVQoE configuration and because the first application associated with RRC ID-1 operates on the MN interface. Similarly, UE 605 may report QoE and / or RVQoE measurements and / or metrics associated with RRC ID-2 to SN 720 because a second application associated with RRC ID-2 is indicated by a SN-specific QoE and / or RVQoE configuration and because the second application associated with RRC ID-2 operates on the SN interface.

[0126] In addition, as mentioned above Figure 7 and Figure 8As described above, UE 605 may send QoE and / or RVQoE measurements and / or metrics and associated interface information to MN 725 (step 9a), or directly send MN applicable QoE and / or RVQoE measurements and / or metrics to MN 725, and directly send SN applicable QoE and / or RVQoE measurements and / or metrics to SN 720 (step 9b). Steps 9a and 9b may be combined with the above. Figure 7 and 8 Steps 9a and 9b described are performed in a substantially similar manner.

[0127] As indicated above, Fig. 9 Other examples can be found in the Fig. 9 The examples described are different.

[0128] Fig.10 is a diagram illustrating another example 1000 associated with configuration of RVQoE measurements for dual connectivity mode according to the present disclosure.

[0129] exist Fig.10 In the example shown, MN 725 and / or SN 720 may generate QoE and / or RVQoE configuration with the help of UE 605. More specifically, as shown in step 1, MN 725 may receive QoE configuration information (e.g., QMC information) from MCE 730, including RVQoE auxiliary information, such as in combination with Figures 7 to 9 As described. In this regard, as shown in step 5', the MN 725 sends the QoE configuration information to the UE 605 (and more specifically, to the UE AS 710) via an RRC message (such as an RRC reconfiguration message). The UE AS 710 may forward the QoE configuration to the UE APP 705, as shown in step 6'. As shown in step 7-1', the UE APP 705 may in turn send information associated with each configured QoE measurement to the UE AS 710, such as the corresponding PDU session identifier of each configured QoE measurement, the QoS flow identifier of each configured QoE measurement, the RRC identifier of each configured QoE measurement, or similar identification information.

[0130] In some aspects, the UE AS 705 may then map the identification information to the corresponding interface (e.g., one of the MN interface or the SN interface), or the UE AS 710 may forward the identification information to the RAN node (e.g., MN 725) to map the identification information to the corresponding interface. More specifically, as shown in step 7-2a', in a first alternative form, the UE AS 710 determines which interface (e.g., which of the MN interface or the SN interface) each QoE measurement is associated with. The UE AS 710 may achieve this by mapping the PDU session identifier of each QoE measurement to the corresponding interface, mapping the QoS flow identifier of each QoE measurement to the corresponding interface, mapping the RRC identifier of each QoE measurement to the corresponding interface, or mapping other identification information of each QoE measurement to the corresponding interface. In these aspects, as shown in step 7-3a', the UE AS 710 may then indicate to one or more RAN nodes (e.g., MN 725) which QoE measurements are associated with each interface.

[0131] In a second alternative form, the UE AS 710 may send identification information to a RAN node (e.g., MN 725), and the RAN node may thereby determine which QoE measurements apply to each interface. More specifically, as shown in step 7-2b', the UE AS 710 may send a PDU session identifier for each QoE measurement, a QoS flow identifier for each QoE measurement, an RRC identifier for each QoE measurement, or other identification information for each QoE measurement to the MN 725. As shown in step 7-3b', the MN 725 may then determine which interface (e.g., which of the MN interface or the SN interface) each QoE measurement is associated with. The MN 725 may achieve this by mapping the PDU session identifier for each QoE measurement to the corresponding interface, mapping the QoS flow identifier for each QoE measurement to the corresponding interface, mapping the RRC identifier for each QoE measurement to the corresponding interface, or mapping other identification information for each QoE measurement to the corresponding interface.

[0132] like Fig.10As shown in step 2 of , the MN 725 may then forward the information to the SN 720 for use by the SN 720 in generating an SN-specific QoE and / or RVQoE configuration. The information may be sent to the SN 720 using an SN Add Request and / or Modify message, and in some aspects, the information may include an RRC identifier and / or other RVQoE assistance information associated with QoE measurements of applications associated with the SN interface. As shown in step 4 associated with the SN 720, the SN may thus generate an SN-specific QoE and / or RVQoE configuration, which may configure one or more QoE and / or RVQoE measurements and / or metrics associated with applications associated with the SN connectivity. As shown in step 3, the SN 720 may send an SN Add Request and / or Modify ACK to the MN 725, which in some aspects may optionally include an SN-specific QoE and / or RVQoE configuration. Similarly, as shown in step 4 associated with MN 725, MN 725 can generate a MN-specific QoE and / or RVQoE configuration, which in some aspects can be generated after receiving the SN add request and / or modification message, but in some other aspects, the configuration can be generated at a different time (such as simultaneously with SN 720 generating the SN-specific QoE and / or RVQoE configuration).

[0133] Then, as shown in step 5, the MN-specific QoE and / or RVQoE configuration and the SN configuration may be sent to the UE 605 (more specifically, to the UE AS 710). As described above, the SN-specific QoE and / or RVQoE configuration may be provided via the SN interface or the MN interface. For example, in some aspects, the MN 725 may send an RRC reconfiguration message, etc., to the UE 605, the message including the MN-specific QoE and / or RVQoE configuration and the SN-specific QoE and / or RVQoE configuration. In some other aspects, the MN 725 may send an RRC reconfiguration message, etc. including the MN-specific QoE and / or RVQoE configuration to the UE 605, and the SN 720 may separately send an RRC reconfiguration message, etc. including the SN-specific QoE and / or RVQoE configuration to the UE 605.

[0134] As shown in step 6, the UE AS 710 may forward the QoE and / or RVQoE configuration (e.g., MN-specific QoE and / or RVQoE configuration and SN-specific QoE and / or RVQoE configuration) to the UE APP 705, which may perform the configured measurements, and as shown in step 7, the UE APP may report the QoE and / or RVQoE measurements and / or metrics to the UE AS 710. In some aspects, the UE APP 705 may indicate the corresponding RRC identifier for each reported QoE and / or RVQoE measurement and / or metric. The UE AS 710 may be combined with the above Figures 7 to 9 The QoE and / or RVQoE measurements and / or metrics are reported to the MN 725 and / or SN 720 in a manner similar to that described in step 9a or 9b described above.

[0135] As indicated above, Fig.10 Other examples can be found in the Fig.10 The examples described are different.

[0136] Fig.11 1 is a diagram illustrating an example process 1100 performed, for example, by a UE according to the present disclosure. The example process 1100 is an example of a UE (e.g., UE 605) performing operations associated with RVQoE metrics for a dual connectivity mode. Although the process 1100 is described in conjunction with RVQoE configuration, measurement, and reporting for ease of discussion, in some other aspects, the process 1100 can be used to configure, measure, and report QoE metrics in a substantially similar manner, such as in conjunction with Figures 7 to 10 as described.

[0137] like Fig.11 As shown, in some aspects, process 1100 may include receiving one or more RVQoE configurations from at least one of a MN or a SN, wherein the UE operates in a dual connectivity mode with the MN and the SN (block 1110). Fig.13 The communication manager 1308 and / or receiving component 1302 depicted in FIG. 1 may receive one or more RVQoE configurations from at least one of the MN or the SN, wherein the UE operates in a dual connectivity mode with the MN and the SN, as described above.

[0138] like Fig.11 As further shown in FIG. 1 , in some aspects, process 1100 may include sending at least one RVQoE measurement report to at least one of the MN or the SN based at least in part on the one or more RVQoE configurations (block 1120). Fig.13The communication manager 1308 and / or the sending component 1304 depicted in FIG. 1 may send at least one RVQoE measurement report to at least one of the MN or the SN based at least in part on the one or more RVQoE configurations, as described above.

[0139] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in combination with one or more other processes described elsewhere herein.

[0140] In a first aspect, the one or more RVQoE configurations include a common RVQoE configuration received from the MN.

[0141] In a second aspect, alone or in combination with the first aspect, the one or more RVQoE configurations include a MN-specific RVQoE configuration and a SN-specific RVQoE configuration.

[0142] In a third aspect, alone or in combination with one or more of the first and second aspects, the SN-specific RVQoE configuration is based at least in part on a list of available RVQoE configurations provided by the MN to the SN.

[0143] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the MN-specific RVQoE configuration and the SN-specific RVQoE configuration are received from the MN.

[0144] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the SN-specific RVQoE configuration is based at least in part on configuration information provided from the SN to the MN via an Xn application protocol information element.

[0145] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the SN-specific RVQoE configuration is based at least in part on configuration information provided from the SN to the MN via a cell group container.

[0146] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, a MN-specific RVQoE configuration is received from the MN and a SN-specific RVQoE configuration is received from the SN.

[0147] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the SN-specific RVQoE configuration is received from the SN via a signaling radio bearer.

[0148] In a ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the MN-specific RVQoE configuration and the SN-specific RVQoE configuration are at least partially based on the UE providing an indication to the MN that a first set of one or more RVQoE configurations is associated with the MN and a second set of one or more RVQoE configurations is associated with the SN.

[0149] In a tenth aspect, either alone or in combination with one or more of the first to ninth aspects, process 1100 includes collecting at least one RVQoE metric based at least in part on the one or more RVQoE configurations, and determining whether each RVQoE configuration is associated with one of MN connectivity or SN connectivity.

[0150] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the UE sends at least one RVQoE measurement report to the MN.

[0151] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the at least one RVQoE measurement report includes a first RVQoE measurement report associated with the MN and a second RVQoE measurement report associated with the SN, and the UE sends to the MN at least one of interface information or bearer information indicating that the first RVQoE measurement report is associated with the MN and the second RVQoE measurement report is associated with the SN.

[0152] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the at least one of the interface information or the bearer information includes at least one of the following: an indication of one of MN connectivity or SN connectivity, an indication of one of an MCG bearer or an SCG bearer, an indication of an MCG branch of a split bearer or one of an SCG branch of a split bearer, a bearer identifier, a packet data unit session identifier, or a quality of service flow identifier.

[0153] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the at least one RVQoE measurement report includes a first RVQoE measurement report associated with the MN and a second RVQoE measurement report associated with the SN, and the UE sends the first RVQoE measurement report to the MN and sends the second RVQoE measurement report to the SN.

[0154] In the fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the one or more RVQoE configurations include a MN-specific RVQoE configuration and an SN-specific RVQoE configuration, the MN-specific RVQoE configuration being associated with a first set of one or more RRC identifiers, and the SN-specific RVQoE configuration being associated with a second set of one or more RRC identifiers.

[0155] In the sixteenth aspect, either alone or in combination with one or more of the first to fifteenth aspects, the first set of one or more RRC identifiers includes a first RRC identifier, and the second set of one or more RRC identifiers includes a second RRC identifier different from the first RRC identifier.

[0156] In a seventeenth aspect, either alone or in combination with one or more of aspects one to sixteen, process 1100 includes reporting at least one of a first RVQoE measurement report associated with the first RRC identifier to the MN based at least in part on an application associated with the first RRC identifier being associated with MN connectivity, or reporting at least one of a second RVQoE measurement report associated with the second RRC identifier to the SN based at least in part on an application associated with the second RRC identifier being associated with SN connectivity.

[0157] In an eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, process 1100 includes at least one of the following: based at least in part on the application associated with the second RRC identifier being associated with MN connectivity, abandoning reporting a first RVQoE measurement report associated with the second RRC identifier, or based at least in part on the application associated with the second RRC identifier being associated with SN connectivity, reporting to the MN the first RVQoE measurement report associated with the second RRC identifier and an indication of SN connectivity associated with the RVQoE measurement report.

[0158] In a nineteenth aspect, either alone or in combination with one or more of the first to eighteenth aspects, the first set of one or more RRC identifiers and the second set of one or more RRC identifiers include a first RRC identifier.

[0159] In the twentieth aspect, either alone or in combination with one or more of the first to nineteenth aspects, process 1100 includes sending a MN-specific RVQoE configuration from an access layer layer of the UE to an application layer of the UE based at least in part on a first set of one or more RRC identifiers including a first RRC identifier and a second set of one or more RRC identifiers.

[0160] In the twenty-first aspect, alone or in combination with one or more of the first to twentieth aspects, process 1100 includes sending a latest received RVQoE configuration of a MN-specific RVQoE configuration or a SN-specific RVQoE configuration from an access layer layer of the UE to an application layer of the UE based at least in part on a first set of one or more RRC identifiers including a first RRC identifier and a second set of one or more RRC identifiers.

[0161] In the twenty-second aspect, alone or in combination with one or more of the first to twenty-first aspects, process 11O0 includes sending an MN-specific RVQoE configuration and an SN-specific RVQoE configuration from an access layer layer of the UE to an application layer of the UE based at least in part on a first set of one or more RRC identifiers including a first RRC identifier and a second set of one or more RRC identifiers, and determining whether to use the MN-specific RVQoE configuration and the SN-specific RVQoE configuration based at least in part on connectivity of an application associated with the first RRC identifier.

[0162] In the twenty-third aspect, alone or in combination with one or more of the first to twenty-second aspects, the first set of one or more RRC identifiers and the second set of one or more RRC identifiers include a first RRC identifier and a second RRC identifier, the UE reports a first RVQoE measurement report associated with the first RRC identifier to the MN based at least in part on the application associated with the first RRC identifier being associated with the MN connectivity, and the UE reports a second RVQoE measurement report associated with the second RRC identifier to the SN based at least in part on the application associated with the second RRC identifier being associated with the SN connectivity.

[0163] although Fig.11 An example block diagram of process 1100 is shown, but in some aspects, process 1100 may include Fig.11 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1100. Additionally or alternatively, two or more blocks of the blocks of process 1100 may be performed in parallel.

[0164] Fig.12 1 is a diagram illustrating an example process 1200 performed, for example, by a MN according to the present disclosure. The example process 1200 is an example of a MN (e.g., MN 610, MN 725) performing operations associated with RVQoE metrics for a dual connectivity mode. Although the process 1200 is described in conjunction with RVQoE configuration, measurement, and reporting for ease of discussion, in some other aspects, the process 1200 can be used to configure, measure, and report QoE metrics in a substantially similar manner, such as in conjunction with Figures 7 to 10 as described.

[0165] like Fig.12 As shown, in some aspects, process 1200 may include sending one or more RVQoE configurations to a UE (e.g., UE 605), where the UE operates in a dual connectivity mode with a MN and a SN (block 1210). Fig.14 The communication manager 1408 and / or the sending component 1404 depicted in FIG. 1404 may send one or more RVQoE configurations to a UE, where the UE operates in a dual connectivity mode with a MN and a SN, as described above.

[0166] like Fig.12 As further shown in FIG. 1 , in some aspects, process 1200 may include receiving at least one RVQoE measurement report from a UE based at least in part on the one or more RVQoE configurations (block 1220). Fig.14 The communication manager 1408 and / or receiving component 1402 depicted in FIG. 1404 may receive at least one RVQoE measurement report from the UE based at least in part on the one or more RVQoE configurations, as described above.

[0167] Process 1200 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in combination with one or more other processes described elsewhere herein.

[0168] In a first aspect, the one or more RVQoE configurations include a common RVQoE configuration.

[0169] In a second aspect, alone or in combination with the first aspect, the one or more RVQoE configurations include a MN-specific RVQoE configuration and a SN-specific RVQoE configuration.

[0170] In a third aspect, alone or in combination with one or more of the first and second aspects, the SN-specific RVQoE configuration is based at least in part on a list of available RVQoE configurations provided by the MN to the SN.

[0171] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the SN-specific RVQoE configuration is based at least in part on configuration information provided from the SN to the MN via an Xn application protocol information element.

[0172] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the SN-specific RVQoE configuration is based at least in part on configuration information provided from the SN to the MN via a cell group container.

[0173] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the one or more RVQoE configurations include only one or more MN-specific RVQoE configurations.

[0174] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the one or more MN-specific RVQoE configurations are based at least in part on the UE providing an indication to the MN that a set of one or more RVQoE configurations is associated with the MN.

[0175] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the at least one RVQoE measurement report includes a first RVQoE measurement report associated with the MN and a second RVQoE measurement report associated with the SN, and the MN receives from the UE at least one of interface information or bearer information indicating that the first RVQoE measurement report is associated with the MN and the second RVQoE measurement report is associated with the SN.

[0176] In the ninth aspect, alone or in combination with one or more of the first to eighth aspects, the at least one of the interface information or the bearer information includes at least one of the following: an indication of one of MN connectivity or SN connectivity, an indication of one of an MCG bearer or an SCG bearer, an indication of an MCG branch of a split bearer or one of an SCG branch of a split bearer, a bearer identifier, a packet data unit session identifier, or a quality of service flow identifier.

[0177] In a tenth aspect, either alone or in combination with one or more of aspects 1 to 9, the one or more RVQoE configurations include a MN-specific RVQoE configuration and an SN-specific RVQoE configuration, the MN-specific RVQoE configuration being associated with a first set of one or more RRC identifiers, and the SN-specific RVQoE configuration being associated with a second set of one or more RRC identifiers.

[0178] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the first set of one or more RRC identifiers includes a first RRC identifier, and the second set of one or more RRC identifiers includes a second RRC identifier different from the first RRC identifier.

[0179] In a twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, process 1200 includes receiving, from a UE, an RVQoE measurement report associated with a first RRC identifier based at least in part on an application associated with the first RRC identifier being associated with MN connectivity.

[0180] In a thirteenth aspect, either alone or in combination with one or more of aspects one to twelfth, process 1200 includes receiving, from the UE, an RVQoE measurement report associated with the second RRC identifier and an indication of SN connectivity associated with the RVQoE measurement report based at least in part on an application associated with the second RRC identifier being associated with SN connectivity.

[0181] In a fourteenth aspect, alone or in combination with one or more of aspects one to thirteen, the first set of one or more RRC identifiers and the second set of one or more RRC identifiers include a first RRC identifier and a second RRC identifier, and the MN receives a first RVQoE measurement report associated with the first RRC identifier from the UE based at least in part on an application associated with the first RRC identifier being associated with MN connectivity, and the MN does not receive a second RVQoE measurement report associated with the second RRC identifier from the UE based at least in part on an application associated with the second RRC identifier being associated with SN connectivity.

[0182] although Fig.12 An example block diagram of process 1200 is shown, but in some aspects, process 1200 may include Fig.12 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1200. Additionally or alternatively, two or more blocks of the blocks of process 1200 may be performed in parallel.

[0183] Fig.13 1 is a diagram of an example apparatus 1300 for wireless communication according to the present disclosure. Apparatus 1300 may be a UE (e.g., UE 605), or a UE may include apparatus 1300. In some aspects, apparatus 1300 includes a receiving component 1302 and a transmitting component 1304 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1300 may communicate with another apparatus 1306 (such as a UE, a base station, or another wireless communication device) using receiving component 1302 and transmitting component 1304. As further shown, apparatus 1300 may include a communication manager 1308 (e.g., communication manager 140). Communication manager 1308 may include one or more of a measurement component 1310, a determination component 1312, or a layer management component 1314, etc.

[0184] In some aspects, the apparatus 1300 may be configured to perform Figures 6 to 10 Additionally or alternatively, device 1300 may be configured to perform one or more processes described herein, such as process 1100 of 11. In some aspects, Fig.13The apparatus 1300 and / or one or more components shown in FIG. 1 may include a combination of Figure 2 Additionally or alternatively, Fig.13 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0185] The receiving component 1302 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1306. The receiving component 1302 may provide the received communications to one or more other components of the device 1300. In some aspects, the receiving component 1302 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) on ​​the received communications and may provide the processed signals to one or more other components of the device 1300. In some aspects, the receiving component 1302 may include combining Figure 2 The UE 120 is described as having one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof.

[0186] Transmit component 1304 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1306. In some aspects, one or more other components of device 1300 may generate communications and may provide the generated communications to transmit component 1304 for transmission to device 1306. In some aspects, transmit component 1304 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1306. In some aspects, transmit component 1304 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof, of the depicted UE 120. In some aspects, the transmit component 1304 can be co-located with the receive component 1302 in a transceiver.

[0187] The receiving component 1302 can receive one or more RVQoE configurations from at least one of the MN or the SN, wherein the UE operates in a dual connectivity mode with the MN and the SN. The sending component 1304 can send at least one RVQoE measurement report to at least one of the MN or the SN based at least in part on the one or more RVQoE configurations.

[0188] Measuring component 1310 can collect at least one RVQoE metric based at least in part on the one or more RVQoE configurations.

[0189] Determining component 1312 can determine whether each RVQoE configuration is associated with one of MN connectivity or SN connectivity.

[0190] The sending component 1304 and / or the measuring component 1310 may report a first RVQoE measurement report associated with the first RRC identifier to the MN based at least in part on the association of an application associated with the first RRC identifier with MN connectivity, or report a second RVQoE measurement report associated with the second RRC identifier to the SN based at least in part on the association of an application associated with the second RRC identifier with SN connectivity.

[0191] The sending component 1304 and / or the measuring component 1310 may forgo reporting the first RVQoE measurement report associated with the second RRC identifier based at least in part on the application associated with the second RRC identifier being associated with the MN connectivity, or may report to the MN the first RVQoE measurement report associated with the second RRC identifier and an indication of the SN connectivity associated with the RVQoE measurement report based at least in part on the application associated with the second RRC identifier being associated with the SN connectivity.

[0192] The layer management component 1314 can send a MN-specific RVQoE configuration from an access layer layer of the UE to an application layer of the UE based at least in part on a first set of one or more RRC identifiers including the first RRC identifier and a second set of one or more RRC identifiers.

[0193] The layer management component 1314 can send a latest received RVQoE configuration of a MN-specific RVQoE configuration or a SN-specific RVQoE configuration from the access layer layer of the UE to the application layer of the UE based at least in part on a first set of one or more RRC identifiers including a first RRC identifier and a second set of one or more RRC identifiers.

[0194] The layer management component 1314 can send a MN-specific RVQoE configuration and an SN-specific RVQoE configuration from an access layer layer of the UE to an application layer of the UE based at least in part on a first set of one or more RRC identifiers including a first RRC identifier and a second set of one or more RRC identifiers.

[0195] Determining component 1312 can determine whether to use a MN-specific RVQoE configuration and a SN-specific RVQoE configuration based at least in part on connectivity of an application associated with the first RRC identifier.

[0196] Fig.13 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.13 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.13 Two or more components shown may be implemented in a single component, or Fig.13 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.13 The illustrated set of component(s) may be described as being executable by Fig.13 Another component shown may be a collection of components that perform one or more functions.

[0197] Fig. 9 1 is a diagram of an example apparatus 1400 for wireless communication according to the present disclosure. Apparatus 1400 may be a MN (e.g., MN 610 or MN 725), or a MN may include apparatus 1400. In some aspects, apparatus 1400 includes a receiving component 1402 and a sending component 1404 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1400 may communicate with another apparatus 1406 (such as a UE, a base station, or another wireless communication device) using receiving component 1402 and sending component 1404. As further shown, apparatus 1400 may include a communication manager 1408 (e.g., communication manager 150). Communication manager 1408 may include configuration component 1410, etc.

[0198] In some aspects, the apparatus 1400 may be configured to perform Figures 6 to 10 Additionally or alternatively, the apparatus 1400 may be configured to perform one or more of the processes described herein (such as Fig.12 In some aspects, Fig.14 The apparatus 1400 and / or one or more components shown in FIG. 1 may include a combination of Figure 2 Additionally or alternatively, Fig.14One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0199] The receiving component 1402 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1406. The receiving component 1402 may provide the received communications to one or more other components of the device 1400. In some aspects, the receiving component 1402 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) on ​​the received communications and may provide the processed signals to one or more other components of the device 1400. In some aspects, the receiving component 1402 may include combining Figure 2 The base station 110 is depicted as having one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof.

[0200] The transmitting component 1404 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1406. In some aspects, one or more other components of the device 1400 may generate communications and may provide the generated communications to the transmitting component 1404 for transmission to the device 1406. In some aspects, the transmitting component 1404 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1406. In some aspects, the transmitting component 1404 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the depicted base station 110. In some aspects, the transmit component 1404 can be co-located with the receive component 1402 in a transceiver.

[0201] Transmitting component 1404 and / or configuring component 1410 can transmit one or more RVQoE configurations to a UE, wherein the UE operates in a dual connectivity mode with a MN and a SN. Receiving component 1402 can receive at least one RVQoE measurement report from the UE based at least in part on the one or more RVQoE configurations.

[0202] Receiving component 1402 can receive, from a UE, a RVQoE measurement report associated with the first RRC identifier based at least in part on an application associated with the first RRC identifier being associated with MN connectivity.

[0203] Receiving component 1402 may receive, from the UE, a RVQoE measurement report associated with the second RRC identifier and an indication of SN connectivity associated with the RVQoE measurement report based at least in part on the application associated with the second RRC identifier being associated with SN connectivity.

[0204] Fig. 9 The number and arrangement of components shown are provided as examples. In practice, there may be Fig. 9 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig. 9 Two or more components shown may be implemented in a single component, or Fig. 9 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig. 9 The illustrated set of component(s) may be described as being executable by Fig. 9 Another component shown may be a collection of components that perform one or more functions.

[0205] The following provides an overview of some aspects of the disclosure:

[0206] Aspect 1: A method of wireless communication performed by a UE, the method comprising: receiving one or more RVQoE configurations from at least one of a MN or a SN, wherein the UE operates in a dual connectivity mode with the MN and the SN; and sending at least one RVQoE measurement report to at least one of the MN or the SN based at least in part on the one or more RVQoE configurations.

[0207] Aspect 2: The method according to aspect 1, wherein the one or more RVQoE configurations include a common RVQoE configuration received from the MN.

[0208] Aspect 3: The method according to any one of aspects 1 to 2, wherein the one or more RVQoE configurations include a MN-specific RVQoE configuration and a SN-specific RVQoE configuration.

[0209] Aspect 4: The method according to aspect 2, wherein the SN-specific RVQoE configuration is based at least in part on a list of available RVQoE configurations provided by the MN to the SN.

[0210] Aspect 5: The method according to any one of aspects 3 to 4, wherein the MN-specific RVQoE configuration and the SN-specific RVQoE configuration are received from the MN.

[0211] Aspect 6: The method according to aspect 5, wherein the SN-specific RVQoE configuration is based at least in part on configuration information provided from the SN to the MN via an Xn application protocol information element.

[0212] Aspect 7: The method according to aspect 5, wherein the SN-specific RVQoE configuration is based at least in part on configuration information provided from the SN to the MN via a cell group container.

[0213] Aspect 8: The method according to aspect 3, wherein the MN-specific RVQoE configuration is received from the MN and the SN-specific RVQoE configuration is received from the SN.

[0214] Aspect 9: The method according to aspect 8, wherein the SN-specific RVQoE configuration is received from the SN via a signaling radio bearer.

[0215] Aspect 10: A method according to any one of Aspects 8 to 9, wherein the MN-specific RVQoE configuration and the SN-specific RVQoE configuration are at least partially based on an indication provided by the UE to the MN that a first set of one or more RVQoE configurations is associated with the MN and a second set of one or more RVQoE configurations is associated with the SN.

[0216] Aspect 11: The method according to any one of aspects 1 to 10, the method further comprising: collecting at least one RVQoE metric based at least in part on the one or more RVQoE configurations; and determining whether each RVQoE configuration is associated with one of MN connectivity or SN connectivity.

[0217] Aspect 12: The method according to any one of aspects 1 to 11, wherein the UE sends at least one RVQoE measurement report to the MN.

[0218] Aspect 13: A method according to Aspect 12, wherein the at least one RVQoE measurement report includes a first RVQoE measurement report associated with the MN and a second RVQoE measurement report associated with the SN, and wherein the UE sends to the MN at least one of interface information or bearer information indicating that the first RVQoE measurement report is associated with the MN and the second RVQoE measurement report is associated with the SN.

[0219] Aspect 14: A method according to Aspect 13, wherein the at least one of the interface information or the bearer information includes at least one of the following: an indication of one of MN connectivity or SN connectivity, an indication of one of MCG bearer or SCG bearer, an indication of one of MCG branch of split bearer or SCG branch of split bearer, a bearer identifier, a packet data unit session identifier, or a quality of service flow identifier.

[0220] Aspect 15: A method according to any one of Aspects 1 to 14, wherein the at least one RVQoE measurement report includes a first RVQoE measurement report associated with the MN and a second RVQoE measurement report associated with the SN, and wherein the UE sends the first RVQoE measurement report to the MN and sends the second RVQoE measurement report to the SN.

[0221] Aspect 16: A method according to any one of Aspects 1 to 15, wherein the one or more RVQoE configurations include a MN-specific RVQoE configuration and an SN-specific RVQoE configuration, wherein the MN-specific RVQoE configuration is associated with a first set of one or more RRC identifiers, and wherein the SN-specific RVQoE configuration is associated with a second set of one or more RRC identifiers.

[0222] Aspect 17: A method according to Aspect 16, wherein the first set of one or more RRC identifiers includes a first RRC identifier, and wherein the second set of one or more RRC identifiers includes a second RRC identifier different from the first RRC identifier.

[0223] Aspect 18: According to the method according to Aspect 17, the method also includes at least one of the following: reporting a first RVQoE measurement report associated with the first RRC identifier to the MN at least in part based on the application associated with the first RRC identifier being associated with MN connectivity; or reporting a second RVQoE measurement report associated with the second RRC identifier to the SN based at least in part on the application associated with the second RRC identifier being associated with SN connectivity.

[0224] Aspect 19: According to the method of Aspect 17, the method also includes at least one of the following: abandoning reporting the first RVQoE measurement report associated with the second RRC identifier based at least in part on the application associated with the second RRC identifier being associated with MN connectivity; or reporting the first RVQoE measurement report associated with the second RRC identifier and an indication of SN connectivity associated with the RVQoE measurement report to the MN based at least in part on the application associated with the second RRC identifier being associated with SN connectivity.

[0225] Aspect 20: The method according to aspect 16, wherein the first set of one or more RRC identifiers and the second set of one or more RRC identifiers include a first RRC identifier.

[0226] Aspect 21: According to the method according to Aspect 20, the method also includes sending the MN-specific RVQoE configuration from the access layer layer of the UE to the application layer of the UE based at least in part on the first set of one or more RRC identifiers including the first RRC identifier and the second set of one or more RRC identifiers.

[0227] Aspect 22: According to the method according to Aspect 20, the method also includes sending the latest received RVQoE configuration of the MN-specific RVQoE configuration or the SN-specific RVQoE configuration from the access layer layer of the UE to the application layer of the UE based at least in part on the first set of one or more RRC identifiers including the first RRC identifier and the second set of one or more RRC identifiers.

[0228] Aspect 23: According to the method according to Aspect 20, the method also includes: sending the MN-specific RVQoE configuration and the SN-specific RVQoE configuration from the access layer layer of the UE to the application layer of the UE based at least in part on the first set of one or more RRC identifiers including the first RRC identifier and the second set of one or more RRC identifiers; and determining whether to use the MN-specific RVQoE configuration and the SN-specific RVQoE configuration based at least in part on the connectivity of the application associated with the first RRC identifier.

[0229] Aspect 24: A method according to Aspect 16, wherein the first set of one or more RRC identifiers and the second set of one or more RRC identifiers include a first RRC identifier and a second RRC identifier, wherein the UE reports a first RVQoE measurement report associated with the first RRC identifier to the MN based at least in part on an application associated with the first RRC identifier being associated with MN connectivity, and wherein the UE reports a second RVQoE measurement report associated with the second RRC identifier to the SN based at least in part on an application associated with the second RRC identifier being associated with SN connectivity.

[0230] Aspect 25: A method of wireless communication performed by a MN, the method comprising: sending one or more RVQoE configurations to a UE, wherein the UE operates in a dual connectivity mode with the MN and a SN; and receiving at least one RVQoE measurement report from the UE based at least in part on the one or more RVQoE configurations.

[0231] Aspect 26: The method according to Aspect 25, wherein the one or more RVQoE configurations include public RVQoE.

[0232] Aspect 27: The method according to any one of aspects 25 to 26, wherein the one or more RVQoE configurations include a MN-specific RVQoE configuration and a SN-specific RVQoE configuration.

[0233] Aspect 28: The method according to aspect 27, wherein the SN-specific RVQoE configuration is based at least in part on a list of available RVQoE configurations provided by the MN to the SN.

[0234] Aspect 29: The method according to any one of aspects 27 to 28, wherein the SN-specific RVQoE configuration is based at least in part on configuration information provided from the SN to the MN via an Xn application protocol information element.

[0235] Aspect 30: The method according to any one of aspects 27 to 28, wherein the SN-specific RVQoE configuration is based at least in part on configuration information provided from the SN to the MN via a cell group container.

[0236] Aspect 31: The method according to aspect 25, wherein the one or more RVQoE configurations include only one or more MN-specific RVQoE configurations.

[0237] Aspect 32: The method according to any aspect of aspect 31, wherein the one or more MN-specific RVQoE configurations are based at least in part on the UE providing an indication to the MN that a set of one or more RVQoE configurations is associated with the MN.

[0238] Aspect 33: A method according to any one of Aspects 25 to 32, wherein the at least one RVQoE measurement report includes a first RVQoE measurement report associated with the MN and a second RVQoE measurement report associated with the SN, and wherein the MN receives at least one of interface information or bearer information from the UE indicating that the first RVQoE measurement report is associated with the MN and the second RVQoE measurement report is associated with the SN.

[0239] Aspect 34: A method according to Aspect 33, wherein the at least one of the interface information or the bearer information includes at least one of the following: an indication of one of MN connectivity or SN connectivity, an indication of one of MCG bearer or SCG bearer, an indication of one of MCG branch of split bearer or SCG branch of split bearer, a bearer identifier, a packet data unit session identifier, or a quality of service flow identifier.

[0240] Aspect 35: A method according to any one of Aspects 25 to 34, wherein the one or more RVQoE configurations include a MN-specific RVQoE configuration and an SN-specific RVQoE configuration, wherein the MN-specific RVQoE configuration is associated with a first set of one or more RRC identifiers, and wherein the SN-specific RVQoE configuration is associated with a second set of one or more RRC identifiers.

[0241] Aspect 36: A method according to Aspect 35, wherein the first set of one or more RRC identifiers includes a first RRC identifier, and wherein the second set of one or more RRC identifiers includes a second RRC identifier different from the first RRC identifier.

[0242] Aspect 37: The method according to aspect 36, the method also includes receiving an RVQoE measurement report associated with the first RRC identifier from the UE based at least in part on the application associated with the first RRC identifier being associated with MN connectivity.

[0243] Aspect 38: According to the method of Aspect 36, the method also includes receiving, from the UE, an RVQoE measurement report associated with the second RRC identifier and an indication of SN connectivity associated with the RVQoE measurement report.

[0244] Aspect 39: A method according to Aspect 35, wherein the first set of one or more RRC identifiers and the second set of one or more RRC identifiers include a first RRC identifier and a second RRC identifier, and wherein the MN receives a first RVQoE measurement report associated with the first RRC identifier from the UE based at least in part on an application associated with the first RRC identifier being associated with MN connectivity, and wherein the MN does not receive a second RVQoE measurement report associated with the second RRC identifier from the UE based at least in part on an application associated with the second RRC identifier being associated with SN connectivity.

[0245] Aspect 40: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to one or more of Aspects 1 to 24.

[0246] Aspect 41: A device for wireless communication, the device comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more aspects of aspects 1 to 24.

[0247] Aspect 42: An apparatus for wireless communication, the apparatus comprising: at least one component for performing the method according to one or more aspects of aspects 1 to 24.

[0248] Aspect 43: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 24.

[0249] Aspect 44: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions, which, when executed by one or more processors of a device, causes the device to perform a method according to one or more of Aspects 1 to 24.

[0250] Aspect 45: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to one or more of Aspects 25 to 39.

[0251] Aspect 46: A device for wireless communication, the device comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more aspects of aspects 25 to 39.

[0252] Aspect 47: An apparatus for wireless communication, the apparatus comprising: at least one component for performing the method according to one or more aspects of aspects 25 to 39.

[0253] Aspect 48: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 25 to 39.

[0254] Aspect 49: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions, which, when executed by one or more processors of a device, causes the device to perform a method according to one or more aspects of Aspects 25 to 39.

[0255] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of these aspects.

[0256] As used herein, the term "component" is intended to be broadly interpreted as hardware and / or a combination of hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes and / or functions, etc. As used herein, "processors" are implemented in hardware and / or a combination of hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by different forms of hardware and / or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit the various aspects. Therefore, no reference is made to specific software codes to describe the operation and behavior of the systems and / or methods herein, because those skilled in the art will understand that software and hardware can be designed to implement the systems and / or methods based at least in part on the descriptions herein.

[0257] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0258] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claims. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (which includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).

[0259] Any element, action or instruction used herein should not be interpreted as critical or necessary unless explicitly described as such. In addition, as used herein, the articles "one" and "an" are intended to include one or more items and can be used interchangeably with "one or more". In addition, as used herein, the article "described / the" is intended to include one or more items connected to the article "described / the" and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items and can be used interchangeably with "one or more". If you want to refer to only one item, use the phrase "only one" or similar terms. In addition, as used herein, the terms "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "an element with" A can also have B). In addition, the phrase "based on" is intended to mean "based at least in part on", unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless explicitly stated otherwise (eg, if used in conjunction with "either" or "only one of").

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and one or more processors coupled to the memory, the one or more processors configured to: receiving one or more radio access network visual quality of experience (RVQoE) configurations from at least one of a master node (MN) or a secondary node (SN), wherein the UE operates in a dual connectivity mode with the MN and the SN; as well as At least one RVQoE measurement report is sent to at least one of the MN or the SN based at least in part on the one or more RVQoE configurations.

2. The apparatus of claim 1, wherein the one or more RVQoE configurations comprise a common RVQoE configuration received from the MN.

3. The apparatus of claim 1, wherein the one or more RVQoE configurations include a MN-specific RVQoE configuration and a SN-specific RVQoE configuration.

4. The apparatus of claim 3, wherein the SN-specific RVQoE configuration is based at least in part on a list of available RVQoE configurations provided by the MN to the SN.

5. The apparatus of claim 3, wherein the MN-specific RVQoE configuration and the SN-specific RVQoE configuration are received from the MN.

6. The apparatus of claim 5, wherein the SN-specific RVQoE configuration is based at least in part on configuration information provided from the SN to the MN via an Xn application protocol information element.

7. The apparatus of claim 5, wherein the SN-specific RVQoE configuration is based at least in part on configuration information provided from the SN to the MN via a cell group container.

8. The apparatus of claim 3, wherein the MN-specific RVQoE configuration is received from the MN and the SN-specific RVQoE configuration is received from the SN.

9. The apparatus of claim 8, wherein the SN-specific RVQoE configuration is received from the SN via a signaling radio bearer.

10. The apparatus of claim 8, wherein the MN-specific RVQoE configuration and the SN-specific RVQoE configuration are based at least in part on the UE providing an indication to the MN that a first set of one or more RVQoE configurations is associated with the MN and a second set of one or more RVQoE configurations is associated with the SN.

11. The apparatus of claim 1 , wherein the one or more processors are further configured to: collecting at least one RVQoE metric based at least in part on the one or more RVQoE configurations; and It is determined whether each RVQoE configuration is associated with one of MN connectivity or SN connectivity.

12. The apparatus of claim 1, wherein the UE sends at least one RVQoE measurement report to the MN.

13. The apparatus according to claim 12, wherein the at least one RVQoE measurement report includes a first RVQoE measurement report associated with the MN and a second RVQoE measurement report associated with the SN, and wherein the UE sends to the MN at least one of interface information or bearer information indicating that the first RVQoE measurement report is associated with the MN and the second RVQoE measurement report is associated with the SN.

14. An apparatus according to claim 13, wherein the at least one of the interface information or the bearer information includes at least one of the following: an indication of one of MN connectivity or SN connectivity, an indication of one of a primary cell group (MCG) bearer or a secondary cell group (SCG) bearer, an indication of one of an MCG branch of a split bearer or an SCG branch of a split bearer, a bearer identifier, a packet data unit session identifier, or a quality of service flow identifier.

15. The apparatus of claim 1 , wherein the at least one RVQoE measurement report comprises a first RVQoE measurement report associated with the MN and a second RVQoE measurement report associated with the SN, and wherein the UE sends the first RVQoE measurement report to the MN and sends the second RVQoE measurement report to the SN.

16. The apparatus of claim 1 , wherein the one or more RVQoE configurations include a MN-specific RVQoE configuration and an SN-specific RVQoE configuration, wherein the MN-specific RVQoE configuration is associated with a first set of one or more radio resource control (RRC) identifiers, and wherein the SN-specific RVQoE configuration is associated with a second set of one or more RRC identifiers.

17. The apparatus of claim 16, wherein the first set of one or more RRC identifiers comprises a first RRC identifier, and wherein the second set of one or more RRC identifiers comprises a second RRC identifier different from the first RRC identifier.

18. The apparatus of claim 17, wherein the one or more processors are further configured to perform at least one of the following: reporting, to the MN, a first RVQoE measurement report associated with the first RRC identifier based at least in part on an application associated with the first RRC identifier being associated with MN connectivity; or Based at least in part on the application associated with the second RRC identifier being associated with SN connectivity, a second RVQoE measurement report associated with the second RRC identifier is reported to the SN.

19. The apparatus of claim 17, wherein the one or more processors are further configured to perform at least one of the following: Based at least in part on the application associated with the second RRC identifier being associated with MN connectivity, forgoing reporting a first RVQoE measurement report associated with the second RRC identifier; or Based at least in part on the application associated with the second RRC identifier being associated with SN connectivity, reporting to the MN a first RVQoE measurement report associated with the second RRC identifier and an indication of SN connectivity associated with the RVQoE measurement report.

20. The apparatus of claim 16, wherein the first set of one or more RRC identifiers and the second set of one or more RRC identifiers include a first RRC identifier.

21. The apparatus of claim 20, wherein the one or more processors are further configured to send the MN-specific RVQoE configuration from an access layer layer of the UE to an application layer of the UE based at least in part on the first set of one or more RRC identifiers including the first RRC identifier and the second set of one or more RRC identifiers.

22. The apparatus of claim 20, wherein the one or more processors are further configured to send, from an access layer layer of the UE to an application layer of the UE, a most recently received RVQoE configuration of the MN-specific RVQoE configuration or the SN-specific RVQoE configuration based at least in part on the first set of one or more RRC identifiers including the first RRC identifier and the second set of one or more RRC identifiers.

23. The apparatus of claim 20, wherein the one or more processors are further configured to: sending, from an access plane layer of the UE to an application layer of the UE, the MN-specific RVQoE configuration and the SN-specific RVQoE configuration based at least in part on the first set of one or more RRC identifiers including the first RRC identifier and the second set of one or more RRC identifiers; and Whether to use the MN-specific RVQoE configuration and the SN-specific RVQoE configuration is determined based at least in part on connectivity of an application associated with the first RRC identifier.

24. The apparatus of claim 16, wherein the first set of one or more RRC identifiers and the second set of one or more RRC identifiers include a first RRC identifier and a second RRC identifier, wherein the UE reports a first RVQoE measurement report associated with the first RRC identifier to the MN based at least in part on an application associated with the first RRC identifier being associated with MN connectivity, and wherein the UE reports a second RVQoE measurement report associated with the second RRC identifier to the SN based at least in part on an application associated with the second RRC identifier being associated with SN connectivity.

25. An apparatus for wireless communication at a master node (MN) for wireless communication, the apparatus comprising: Memory; and one or more processors coupled to the memory, the one or more processors configured to: sending one or more radio access network visual quality of experience (RVQoE) configurations to a user equipment (UE), wherein the UE operates in a dual connectivity mode with the MN and a secondary node (SN); as well as At least one RVQoE measurement report is received from the UE based at least in part on the one or more RVQoE configurations.

26. The apparatus of claim 25, wherein the at least one RVQoE measurement report comprises a first RVQoE measurement report associated with the MN and a second RVQoE measurement report associated with the SN, and wherein the MN receives at least one of interface information or bearer information from the UE indicating that the first RVQoE measurement report is associated with the MN and the second RVQoE measurement report is associated with the SN.

27. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving one or more radio access network visual quality of experience (RVQoE) configurations from at least one of a master node (MN) or a secondary node (SN), wherein the UE operates in a dual connectivity mode with the MN and the SN; as well as At least one RVQoE measurement report is sent to at least one of the MN or the SN based at least in part on the one or more RVQoE configurations.

28. The method according to claim 27, further comprising: collecting at least one RVQoE metric based at least in part on the one or more RVQoE configurations; as well as It is determined whether each RVQoE configuration is associated with one of MN connectivity or SN connectivity.

29. A method of wireless communication performed by a master node (MN), the method comprising: sending one or more radio access network visual quality of experience (RVQoE) configurations to a user equipment (UE), wherein the UE operates in a dual connectivity mode with the MN and a secondary node (SN); as well as At least one RVQoE measurement report is received from the UE based at least in part on the one or more RVQoE configurations.

30. The method of claim 29, wherein the at least one RVQoE measurement report includes a first RVQoE measurement report associated with the MN and a second RVQoE measurement report associated with the SN, and wherein the MN receives at least one of interface information or bearer information from the UE indicating that the first RVQoE measurement report is associated with the MN and the second RVQoE measurement report is associated with the SN.