WO2025031168A1

WO2025031168A1 - Continuity measurement for dual connectivity scenarios

Info

Publication number: WO2025031168A1
Application number: PCT/CN2024/107740
Authority: WO
Inventors: Jianhua Liu; Shankar Krishnan
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2023-08-09
Filing date: 2024-07-26
Publication date: 2025-02-13
Anticipated expiration: 2026-02-09
Also published as: WO2025030414A1

Abstract

Methods, systems, and devices for wireless communications are described. The described techniques enable a user equipment (UE) to resolve continuity issues for quality of experience (QoE) reporting resulting from a change in a dual connectivity (DC) scenario. For example, a master node (MN) may configure the UE to report one or more QoE measurements to the MN, to discard QoE measurement data, to discard the related QoE measurement configurations, or to suspend the related QoE measurements. In some examples, the UE may perform such operations autonomously. In some examples, the UE may additionally or alternatively transmit the QoE measurements to a secondary node (SN). Upon a node switch from a first SN to a second SN, the UE may receive an indication to discard or to keep one or more of the QoE measurement configurations.The UE may report the QoE measurements to the MN or to the SN.

Description

CONTINUITY MEASUREMENT FOR DUAL CONNECTIVITY SCENARIOS

CROSS REFERENCE

The present Application for Patent claims the benefit of Chinese PCT Application No. PCT/CN2023/111892 by LIU et al., entitled “CONTINUITY MEASUREMENT FOR DUAL CONNECTIVITY SCENARIOS, ” filed August 9, 2023, assigned to the assignee hereof, and expressly incorporated by reference in its entirety herein.

FIELD OF TECHNOLOGY

The following relates to wireless communications, including continuity measurement for dual connectivity (DC) scenarios.

BACKGROUND

Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power) . Examples of such multiple-access systems include fourth generation (4G) systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems which may be referred to as New Radio (NR) systems. These systems may employ technologies such as code division multiple access (CDMA) , time division multiple access (TDMA) , frequency division multiple access (FDMA) , orthogonal FDMA (OFDMA) , or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM) . A wireless multiple-access communications system may include one or more base stations, each supporting wireless communication for communication devices, which may be known as user equipment (UE) .

SUMMARY

The described techniques relate to improved methods, systems, devices, and apparatuses that support continuity measurement for dual connectivity (DC) scenarios. For example, the described techniques enable a user equipment (UE) to resolve continuity issues for quality of experience (QoE) measurement reporting that may result from a change in the DC scenario (e.g., a release or deactivation of a secondary cell group (SCG) (which may be referred to as a secondary connectivity) , or a node switch) . For example, the described techniques may enable the UE to determine to report, discard, or otherwise manage QoE measurements which were configured to be reported to a secondary network entity (e.g., via a signaling radio bearer (SRB) associated with the secondary network entity, such as SRB5) after the change in the DC scenario.

In some examples, the UE may transmit an indication to a primary network entity indicating that one or more QoE measurements were configured to be reported via SRB5. The primary network entity may reconfigure the UE, for example, to report the one or more QoE measurements to the primary network entity (e.g., via an SRB associated with the primary network entity, such as SRB4) , to discard the QoE measurement data, to release or discard the related QoE measurement configurations, or to suspend the related QoE measurements until the SCG is reactivated. In some examples, the UE may autonomously transmit the QoE measurements via SRB4, discard the QoE measurement data, discard the QoE measurement configurations, or suspend the related QoE measurements until the SCG is reactivated. In some examples (e.g., if an SCG is reactivated) , the UE may transmit the QoE measurements to the secondary network entity via SRB5. In some examples (e.g., if the active secondary network entity is changed from a first secondary network entity to a second secondary network entity) , the UE may receive an indication to release or to keep one or more of the QoE measurement configurations. If the UE receives an indication to keep one or more of the QoE measurement configurations, the UE may report the QoE measurements to the primary network entity or to the second secondary network entity (e.g., via SRB4 or via SRB5) .

A method for wireless communications by a UE is described. The method may include receiving, by the UE operating in a DC mode with a primary network entity and a secondary network entity, one or more messages indicating one or more parameters associated with a QoE measurement procedure for the secondary network entity, performing, by the UE operating in the DC mode, one or more QoE measurements based on the one or more parameters associated with the QoE measurement procedure, receiving an indication of a change associated with the DC mode, and performing a QoE reporting procedure associated with the one or more QoE measurements based on the change associated with the DC mode.

A UE for wireless communications is described. The UE may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories. The one or more processors may individually or collectively operable to execute the code to cause the UE to receive, by the UE operating in a DC mode with a primary network entity and a secondary network entity, one or more messages indicating one or more parameters associated with a QoE measurement procedure for the secondary network entity, perform, by the UE operating in the DC mode, one or more QoE measurements based on the one or more parameters associated with the QoE measurement procedure, receive an indication of a change associated with the DC mode, and perform a QoE reporting procedure associated with the one or more QoE measurements based on the change associated with the DC mode.

Another UE for wireless communications is described. The UE may include means for receiving, by the UE operating in a DC mode with a primary network entity and a secondary network entity, one or more messages indicating one or more parameters associated with a QoE measurement procedure for the secondary network entity, means for performing, by the UE operating in the DC mode, one or more QoE measurements based on the one or more parameters associated with the QoE measurement procedure, means for receiving an indication of a change associated with the DC mode, and means for performing a QoE reporting procedure associated with the one or more QoE measurements based on the change associated with the DC mode.

A non-transitory computer-readable medium storing code for wireless communications is described. The code may include instructions executable by a processor to receive, by the UE operating in a DC mode with a primary network entity and a secondary network entity, one or more messages indicating one or more parameters associated with a QoE measurement procedure for the secondary network entity, perform, by the UE operating in the DC mode, one or more QoE measurements based on the one or more parameters associated with the QoE measurement procedure, receive an indication of a change associated with the DC mode, and perform a QoE reporting procedure associated with the one or more QoE measurements based on the change associated with the DC mode.

In some examples of the method, UEs, and non-transitory computer-readable medium described herein, performing the QoE reporting procedure may include operations, features, means, or instructions for transmitting, to the primary network entity via a radio bearer associated with the primary network entity, a measurement report indicating the one or more QoE measurements based on the change associated with the DC mode, where the change associated with the DC mode includes one of a deactivation of a secondary connectivity associated with the secondary network entity, a release of the secondary connectivity, or a node switch associated with the secondary network entity.

Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving a second indication requesting the UE to transmit the one or more QoE measurements to the primary network entity via the radio bearer associated with the primary network entity.

Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, to the primary network entity, an availability message indicating an availability of the one or more QoE measurements associated with the QoE measurement procedure for the secondary network entity.

In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the change associated with the DC mode includes a deactivation of a secondary connectivity associated with the secondary network entity and the method, apparatuses, and non-transitory computer-readable medium may include further operations, features, means, or instructions for transmitting, to the secondary network entity via a radio bearer associated with the secondary network entity, a measurement report indicating the one or more QoE measurements based on reactivation of the secondary connectivity associated with the secondary network entity.

Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving a third indication requesting for the UE to transmit the one or more QoE measurements to the secondary network entity via the radio bearer associated with the secondary network entity, where transmitting the measurement report to the secondary network entity via the radio bearer associated with the secondary network entity may be based on receiving the third indication.

In some examples of the method, UEs, and non-transitory computer-readable medium described herein, performing the QoE reporting procedure may include operations, features, means, or instructions for discarding the one or more QoE measurements.

In some examples of the method, UEs, and non-transitory computer-readable medium described herein, performing the QoE reporting procedure may include operations, features, means, or instructions for suspending the QoE measurement procedure and resuming the QoE measurement procedure based on a reactivation of the secondary connectivity.

In some examples of the method, UEs, and non-transitory computer-readable medium described herein, performing the QoE reporting procedure may include operations, features, means, or instructions for discarding the one or more parameters associated with the QoE measurement procedure, where the change associated with the DC mode includes one of a release of a secondary connectivity associated with the secondary network entity or a node switch associated with the secondary network entity.

Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving a fourth indication requesting for the UE to discard the one or more parameters, where discarding the one or more parameters may be based on receiving the fourth indication.

In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the change associated with the DC mode includes a deactivation of a secondary connectivity associated with the secondary network entity.

In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the change associated with the DC mode includes a release of a secondary connectivity associated with the secondary network entity.

In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the change associated with the DC mode includes a switch from the secondary network entity to an additional secondary network entity.

A method for wireless communications by a network entity is described. The method may include transmitting, to a UE operating in a DC mode associated with a primary network entity and a secondary network entity, one or more messages indicating one or more parameters associated with a QoE measurement procedure for the secondary network entity, where the one or more parameters instruct the UE to perform one or more QoE measurements and transmitting, to the UE, an indication of a change associated with the DC mode.

A network entity for wireless communications is described. The network entity may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories. The one or more processors may individually or collectively operable to execute the code to cause the network entity to transmit, to a UE operating in a DC mode associated with a primary network entity and a secondary network entity, one or more messages indicating one or more parameters associated with a QoE measurement procedure for the secondary network entity, where the one or more parameters instruct the UE to perform one or more QoE measurements and transmit, to the UE, an indication of a change associated with the DC mode.

Another network entity for wireless communications is described. The network entity may include means for transmitting, to a UE operating in a DC mode associated with a primary network entity and a secondary network entity, one or more messages indicating one or more parameters associated with a QoE measurement procedure for the secondary network entity, where the one or more parameters instruct the UE to perform one or more QoE measurements and means for transmitting, to the UE, an indication of a change associated with the DC mode.

A non-transitory computer-readable medium storing code for wireless communications is described. The code may include instructions executable by a processor to transmit, to a UE operating in a DC mode associated with a primary network entity and a secondary network entity, one or more messages indicating one or more parameters associated with a QoE measurement procedure for the secondary network entity, where the one or more parameters instruct the UE to perform one or more QoE measurements and transmit, to the UE, an indication of a change associated with the DC mode.

Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, from the UE via a radio bearer associated with the primary network entity, a measurement report indicating the one or more of QoE measurements based on the change associated with the DC mode, where the change associated with the DC mode includes one of a deactivation of a secondary connectivity associated with the secondary network entity, a release of the secondary connectivity, or a node switch associated with the secondary network entity, and where the network entity may be the primary network entity.

Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting a second indication requesting for the UE to transmit the one or more QoE measurements to the primary network entity via a radio bearer associated with the primary network entity based on the change associated with the DC mode, where the change associated with the DC mode includes one of a deactivation of a secondary connectivity associated with the secondary network entity, a release of the secondary connectivity, or a node switch associated with the secondary network entity.

Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, from the UE, an availability message indicating an availability of the one or more QoE measurements associated with the QoE measurement procedure for the secondary network entity.

In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the change associated with the DC mode includes a deactivation of a secondary connectivity associated with the secondary network entity.

Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, via a radio bearer associated with the secondary network entity, a measurement report indicating the one or more QoE measurements based on a reactivation of the secondary connectivity, where the network entity may be the secondary network entity.

Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, to the UE, a third indication requesting the UE to transmit the one or more QoE measurements to the secondary network entity based on a reactivation of the secondary connectivity.

In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the change associated with the DC mode includes a release of a secondary connectivity associated with the secondary network entity.

Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, to the UE, a fourth indication requesting the UE to discard the one or more parameters.

Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, from the secondary network entity, an indication of the one or more parameters associated with the QoE measurement procedure, where the network entity may be the primary network entity.

In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the change associated with the DC mode includes a node switch from the secondary network entity to an additional secondary network entity.

Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, to the additional secondary network entity, an indication of the one or more parameters, where the network entity may be the primary network entity and receiving, from the additional secondary network entity, an acknowledgment message based on transmitting the indication of the one or more parameters.

Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, from the secondary network entity, an indication of the one or more parameters for the UE to discard and one or more additional parameters for the UE to maintain.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an example of a wireless communications system that supports continuity measurement for dual connectivity (DC) scenarios in accordance with one or more aspects of the present disclosure.

FIG. 2 shows an example of a wireless communications system that supports continuity measurement for DC scenarios in accordance with one or more aspects of the present disclosure.

FIG. 3 shows an example of a process flow that supports continuity measurement for DC scenarios in accordance with one or more aspects of the present disclosure.

FIG. 4 shows an example of a process flow that supports continuity measurement for DC scenarios in accordance with one or more aspects of the present disclosure.

FIGs. 5 and 6 show block diagrams of devices that support continuity measurement for DC scenarios in accordance with one or more aspects of the present disclosure.

FIG. 7 shows a block diagram of a communications manager that supports continuity measurement for DC scenarios in accordance with one or more aspects of the present disclosure.

FIG. 8 shows a diagram of a system including a device that supports continuity measurement for DC scenarios in accordance with one or more aspects of the present disclosure.

FIGs. 9 and 10 show block diagrams of devices that support continuity measurement for DC scenarios in accordance with one or more aspects of the present disclosure.

FIG. 11 shows a block diagram of a communications manager that supports continuity measurement for DC scenarios in accordance with one or more aspects of the present disclosure.

FIG. 12 shows a diagram of a system including a device that supports continuity measurement for DC scenarios in accordance with one or more aspects of the present disclosure.

FIGs. 13 through 18 show flowcharts illustrating methods that support continuity measurement for DC scenarios in accordance with one or more aspects of the present disclosure.

DETAILED DESCRIPTION

In some wireless communications systems, a user equipment (UE) may report one or more quality of experience (QoE) measurements to a network entity (e.g., to a primary network entity such as a master node (MN) or to a secondary network entity such as a secondary node (SN) when the UE is in a dual connectivity (DC) mode) . That is, the UE may receive a configuration from the network entity to measure and report one or more metrics (e.g., related to a flow of traffic which has been transmitted over a channel between the UE and the network entity) . The UE may receive a configuration to report the QoE measurements using one or more signaling radio bearers (SRBs) , such as SRB4 or SRB5 (e.g., to the primary network entity or to the secondary network entity, respectively) . However, in some DC scenarios, a secondary cell group (SCG) or secondary connectivity including the secondary network entity may be deactivated or released, or an active secondary network entity may change from a first secondary network entity to a second secondary network entity. Such scenarios may result in continuity issues for reporting QoE measurements that were configured to be reported to the secondary network entity (e.g., via SRB5) . For example, upon or after a change in the DC scenario, the UE may not report the QoE measurements via the configured SRB.

Accordingly, techniques described herein may enable the UE to resolve continuity issues for QoE measurement reporting that may result from a change in the DC scenario (e.g., a release or deactivation of an SCG or a node switch) . For example, the described techniques may enable the UE to determine to report, discard, or otherwise manage QoE measurements which were configured to be reported to the secondary network entity (e.g., via SRB5) after the change in the DC scenario.

In some examples (e.g., if the SCG group or secondary connectivity is deactivated) , the UE may transmit an indication to the primary network entity indicating that one or more QoE measurements were configured to be reported via SRB5 (e.g., to the secondary network entity in the deactivated SCG) . The primary network entity may accordingly reconfigure the UE, for example, to report the one or more QoE measurements via SRB4 (e.g., to the primary network entity) , to discard the QoE measurement data, or to buffer the QoE measurement data until the SCG is reactivated. In some examples, the primary network entity (e.g., or the secondary network entity) may indicate for the UE to report one or more of the QoE measurements via SRB4 (e.g., without receiving the indication from the UE) . In some examples, the UE may autonomously transmit the QoE measurements via SRB4, discard the QoE measurement data, or suspend the related QoE measurements until the SCG is reactivated (e.g., without receiving an indication from the primary network entity or the secondary network entity) . In some examples (e.g., if the SCG is reactivated) , the UE may autonomously transmit the QoE measurements to the secondary network entity via SRB5. Additionally, or alternatively (e.g., if the UE was configured to suspend the QoE measurements) , the UE may autonomously resume QoE measurement and reporting to the secondary network entity via SRB5. Additionally, or alternatively, the UE may receive an indication from the primary network entity or the secondary network entity to transmit one or more of the QoE measurements via SRB5.

In some examples (e.g., if the SCG group or secondary connectivity is released) , the UE may autonomously release the QoE measurements. For example, a radio resource control (RRC) layer of the UE may inform an application layer of the UE to release or discard one or more QoE measurement configurations (e.g., that were configured to be reported to the secondary network entity via SRB5) . Additionally, or alternatively, the UE may receive an indication (e.g., from the primary network entity or from the secondary network entity) to release one or more of the QoE measurements. The UE may additionally or alternatively report one or more QoE measurements (e.g., QoE measurements which were not indicated to be released) to the primary network entity via SRB4. The secondary network entity may forward the related QoE measurement configurations to the primary network entity.

In some examples (e.g., if the active secondary network entity is changed from a first secondary network entity to a second secondary network entity) , the UE may receive an indication (e.g., from the primary network entity or from the second secondary network entity) to release or to keep one or more of the QoE measurement configurations. If the UE receives an indication to keep one or more of the QoE measurement configurations, the UE may report the QoE measurements to the primary network entity or to the second secondary network entity (e.g., via SRB4 or via SRB5) . The second secondary network entity may receive an indication (e.g., from the primary network entity or from the first secondary network entity) of whether the one or more QoE measurement configurations can be released.

Aspects of the disclosure are initially described in the context of wireless communications systems. Aspects of the disclosure are further illustrated by and described with reference to process flow diagrams. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to continuity measurement for DC scenarios.

FIG. 1 shows an example of a wireless communications system 100 that supports continuity measurement for DC scenarios in accordance with one or more aspects of the present disclosure. The wireless communications system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communications system 100 may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

The network entities 105 may be dispersed throughout a geographic area to form the wireless communications system 100 and may include devices in different forms or having different capabilities. In various examples, a network entity 105 may be referred to as a network element, a mobility element, a radio access network (RAN) node, or network equipment, among other nomenclature. In some examples, network entities 105 and UEs 115 may wirelessly communicate via one or more communication links 125 (e.g., a radio frequency (RF) access link) . For example, a network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UEs 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area over which a network entity 105 and a UE 115 may support the communication of signals according to one or more radio access technologies (RATs) .

The UEs 115 may be dispersed throughout a coverage area 110 of the wireless communications system 100, and each UE 115 may be stationary, or mobile, or both at different times. The UEs 115 may be devices in different forms or having different capabilities. Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communications with various types of devices, such as other UEs 115 or network entities 105, as shown in FIG. 1.

As described herein, a node of the wireless communications system 100, which may be referred to as a network node, or a wireless node, may be a network entity 105 (e.g., any network entity described herein) , a UE 115 (e.g., any UE described herein) , a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be a UE 115. As another example, a node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In yet other aspects of this example, the first, second, and third nodes may be different relative to these examples. Similarly, reference to a UE 115, network entity 105, apparatus, device, computing system, or the like may include disclosure of the UE 115, network entity 105, apparatus, device, computing system, or the like being a node. For example, disclosure that a UE 115 is configured to receive information from a network entity 105 also discloses that a first node is configured to receive information from a second node.

In some examples, network entities 105 may communicate with the core network 130, or with one another, or both. For example, network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., in accordance with an S1, N2, N3, or other interface protocol) . In some examples, network entities 105 may communicate with one another via a backhaul communication link 120 (e.g., in accordance with an X2, Xn, or other interface protocol) either directly (e.g., directly between network entities 105) or indirectly (e.g., via a core network 130) . In some examples, network entities 105 may communicate with one another via a midhaul communication link 162 (e.g., in accordance with a midhaul interface protocol) or a fronthaul communication link 168 (e.g., in accordance with a fronthaul interface protocol) , or any combination thereof. The backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., an electrical link, an optical fiber link) , one or more wireless links (e.g., a radio link, a wireless optical link) , among other examples or various combinations thereof. A UE 115 may communicate with the core network 130 via a communication link 155.

One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB) , a next-generation NodeB or a giga-NodeB (either of which may be referred to as a gNB) , a 5G NB, a next-generation eNB (ng-eNB) , a Home NodeB, a Home eNodeB, or other suitable terminology) . In some examples, a network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140) .

In some examples, a network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) , which may be configured to utilize a protocol stack that is physically or logically distributed among two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance) , or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN) ) . For example, a network entity 105 may include one or more of a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN Intelligent Controller (RIC) 175 (e.g., a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC) ) , a Service Management and Orchestration (SMO) 180 system, or any combination thereof. An RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH) , a remote radio unit (RRU) , or a transmission reception point (TRP) . One or more components of the network entities 105 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 105 may be located in distributed locations (e.g., separate physical locations) . In some examples, one or more network entities 105 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU) , a virtual DU (VDU) , a virtual RU (VRU) ) .

The split of functionality between a CU 160, a DU 165, and an RU 170 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combinations thereof) are performed at a CU 160, a DU 165, or an RU 170. For example, a functional split of a protocol stack may be employed between a CU 160 and a DU 165 such that the CU 160 may support one or more layers of the protocol stack and the DU 165 may support one or more different layers of the protocol stack. In some examples, the CU 160 may host upper protocol layer (e.g., layer 3 (L3) , layer 2 (L2) ) functionality and signaling (e.g., RRC, service data adaption protocol (SDAP) , Packet Data Convergence Protocol (PDCP) ) . The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally, or alternatively, a functional split of the protocol stack may be employed between a DU 165 and an RU 170 such that the DU 165 may support one or more layers of the protocol stack and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or multiple different cells (e.g., via one or more RUs 170) . In some cases, a functional split between a CU 160 and a DU 165, or between a DU 165 and an RU 170 may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU 160, a DU 165, or an RU 170, while other functions of the protocol layer are performed by a different one of the CU 160, the DU 165, or the RU 170) . A CU 160 may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU 160 may be connected to one or more DUs 165 via a midhaul communication link 162 (e.g., F1, F1-c, F1-u) , and a DU 165 may be connected to one or more RUs 170 via a fronthaul communication link 168 (e.g., open fronthaul (FH) interface) . In some examples, a midhaul communication link 162 or a fronthaul communication link 168 may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 105 that are in communication via such communication links.

In wireless communications systems (e.g., wireless communications system 100) , infrastructure and spectral resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, providing an IAB network architecture (e.g., to a core network 130) . In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as a donor entity or an IAB donor. One or more DUs 165 or one or more RUs 170 may be partially controlled by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140) . The one or more donor network entities 105 (e.g., IAB donors) may be in communication with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120) . IAB nodes 104 may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by DUs 165 of a coupled IAB donor. An IAB-MT may include an independent set of antennas for relay of communications with UEs 115, or may share the same antennas (e.g., of an RU 170) of an IAB node 104 used for access via the DU 165 of the IAB node 104 (e.g., referred to as virtual IAB-MT (vIAB-MT) ) . In some examples, the IAB nodes 104 may include DUs 165 that support communication links with additional entities (e.g., IAB nodes 104, UEs 115) within the relay chain or configuration of the access network (e.g., downstream) . In such cases, one or more components of the disaggregated RAN architecture (e.g., one or more IAB nodes 104 or components of IAB nodes 104) may be configured to operate according to the techniques described herein.

In the case of the techniques described herein applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support continuity measurement for DC scenarios as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally, or alternatively, be performed by one or more components of the disaggregated RAN architecture (e.g., IAB nodes 104, DUs 165, CUs 160, RUs 170, RIC 175, SMO 180) .

A UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the “device” may also be referred to as a unit, a station, a terminal, or a client, among other examples. A UE 115 may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA) , a tablet computer, a laptop computer, or a personal computer. In some examples, a UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, or vehicles, meters, among other examples.

The UEs 115 described herein may be able to communicate with various types of devices, such as other UEs 115 that may sometimes act as relays as well as the network entities 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.

The UEs 115 and the network entities 105 may wirelessly communicate with one another via one or more communication links 125 (e.g., an access link) using resources associated with one or more carriers. The term “carrier” may refer to a set of RF spectrum resources having a defined physical layer structure for supporting the communication links 125. For example, a carrier used for a communication link 125 may include a portion of a RF spectrum band (e.g., a bandwidth part (BWP) ) that is operated according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR) . Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information) , control signaling that coordinates operation for the carrier, user data, or other signaling. The wireless communications system 100 may support communication with a UE 115 using carrier aggregation or multi-carrier operation. A UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers. Communication between a network entity 105 and other devices may refer to communication between the devices and any portion (e.g., entity, sub-entity) of a network entity 105. For example, the terms “transmitting, ” “receiving, ” or “communicating, ” when referring to a network entity 105, may refer to any portion of a network entity 105 (e.g., a base station 140, a CU 160, a DU 165, a RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities 105) .

Signal waveforms transmitted via a carrier may be made up of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM) ) . In a system employing MCM techniques, a resource element may refer to resources of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The quantity of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both) , such that a relatively higher quantity of resource elements (e.g., in a transmission duration) and a relatively higher order of a modulation scheme may correspond to a relatively higher rate of communication. A wireless communications resource may refer to a combination of an RF spectrum resource, a time resource, and a spatial resource (e.g., a spatial layer, a beam) , and the use of multiple spatial resources may increase the data rate or data integrity for communications with a UE 115.

The time intervals for the network entities 105 or the UEs 115 may be expressed in multiples of a basic time unit which may, for example, refer to a sampling period of T_s=1/ (Δf_max·N_f) seconds, for which Δf_max may represent a supported subcarrier spacing, and N_f may represent a supported discrete Fourier transform (DFT) size. Time intervals of a communications resource may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms) ) . Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023) .

Each frame may include multiple consecutively-numbered subframes or slots, and each subframe or slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a quantity of slots. Alternatively, each frame may include a variable quantity of slots, and the quantity of slots may depend on subcarrier spacing. Each slot may include a quantity of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period) . In some wireless communications systems 100, a slot may further be divided into multiple mini-slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N_f) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.

A subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system 100 and may be referred to as a transmission time interval (TTI) . In some examples, the TTI duration (e.g., a quantity of symbol periods in a TTI) may be variable. Additionally, or alternatively, the smallest scheduling unit of the wireless communications system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs) ) .

Physical channels may be multiplexed for communication using a carrier according to various techniques. A physical control channel and a physical data channel may be multiplexed for signaling via a downlink carrier, for example, using one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. A control region (e.g., a control resource set (CORESET) ) for a physical control channel may be defined by a set of symbol periods and may extend across the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESETs) may be configured for a set of the UEs 115. For example, one or more of the UEs 115 may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple control channel candidates in one or more aggregation levels arranged in a cascaded manner. An aggregation level for a control channel candidate may refer to an amount of control channel resources (e.g., control channel elements (CCEs) ) associated with encoded information for a control information format having a given payload size. Search space sets may include common search space sets configured for sending control information to multiple UEs 115 and UE-specific search space sets for sending control information to a specific UE 115.

A network entity 105 may provide communication coverage via one or more cells, for example a macro cell, a small cell, a hot spot, or other types of cells, or any combination thereof. The term “cell” may refer to a logical communication entity used for communication with a network entity 105 (e.g., using a carrier) and may be associated with an identifier for distinguishing neighboring cells (e.g., a physical cell identifier (PCID) , a virtual cell identifier (VCID) , or others) . In some examples, a cell also may refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) over which the logical communication entity operates. Such cells may range from smaller areas (e.g., a structure, a subset of structure) to larger areas depending on various factors such as the capabilities of the network entity 105. For example, a cell may be or include a building, a subset of a building, or exterior spaces between or overlapping with coverage areas 110, among other examples.

A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by the UEs 115 with service subscriptions with the network provider supporting the macro cell. A small cell may be associated with a lower-powered network entity 105 (e.g., a lower-powered base station 140) , as compared with a macro cell, and a small cell may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to the UEs 115 with service subscriptions with the network provider or may provide restricted access to the UEs 115 having an association with the small cell (e.g., the UEs 115 in a closed subscriber group (CSG) , the UEs 115 associated with users in a home or office) . A network entity 105 may support one or multiple cells and may also support communications via the one or more cells using one or multiple component carriers.

In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT) , enhanced mobile broadband (eMBB) ) that may provide access for different types of devices.

In some examples, a network entity 105 (e.g., a base station 140, an RU 170) may be movable and therefore provide communication coverage for a moving coverage area 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, the overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communications system 100 may include, for example, a heterogeneous network in which different types of the network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

Some UEs 115 may be configured to employ operating modes that reduce power consumption, such as half-duplex communications (e.g., a mode that supports one-way communication via transmission or reception, but not transmission and reception concurrently) . In some examples, half-duplex communications may be performed at a reduced peak rate. Other power conservation techniques for the UEs 115 include entering a power saving deep sleep mode when not engaging in active communications, operating using a limited bandwidth (e.g., according to narrowband communications) , or a combination of these techniques. For example, some UEs 115 may be configured for operation using a narrowband protocol type that is associated with a defined portion or range (e.g., set of subcarriers or resource blocks (RBs) ) within a carrier, within a guard-band of a carrier, or outside of a carrier.

The wireless communications system 100 may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof. For example, the wireless communications system 100 may be configured to support ultra-reliable low-latency communications (URLLC) . The UEs 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communications may include private communication or group communication and may be supported by one or more services such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

In some examples, a UE 115 may be configured to support communicating directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., in accordance with a peer-to-peer (P2P) , D2D, or sidelink protocol) . In some examples, one or more UEs 115 of a group that are performing D2D communications may be within the coverage area 110 of a network entity 105 (e.g., a base station 140, an RU 170) , which may support aspects of such D2D communications being configured by (e.g., scheduled by) the network entity 105. In some examples, one or more UEs 115 of such a group may be outside the coverage area 110 of a network entity 105 or may be otherwise unable to or not configured to receive transmissions from a network entity 105. In some examples, groups of the UEs 115 communicating via D2D communications may support a one-to-many (1: M) system in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, a network entity 105 may facilitate the scheduling of resources for D2D communications. In some other examples, D2D communications may be carried out between the UEs 115 without an involvement of a network entity 105.

The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or 5G core (5GC) , which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management function (AMF) ) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , or a user plane function (UPF) ) . The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs 115 served by the network entities 105 (e.g., base stations 140) associated with the core network 130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions. The user plane entity may be connected to IP services 150 for one or more network operators. The IP services 150 may include access to the Internet, Intranet (s) , an IP Multimedia Subsystem (IMS) , or a Packet-Switched Streaming Service.

The wireless communications system 100 may operate using one or more frequency bands, which may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz) . Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features, which may be referred to as clusters, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to communications using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.

The wireless communications system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communications system 100 may employ License Assisted Access (LAA) , LTE-Unlicensed (LTE-U) radio access technology, or NR technology using an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band. While operating using unlicensed RF spectrum bands, devices such as the network entities 105 and the UEs 115 may employ carrier sensing for collision detection and avoidance. In some examples, operations using unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating using a licensed band (e.g., LAA) . Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.

A network entity 105 (e.g., a base station 140, an RU 170) or a UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of a network entity 105 or a UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with a network entity 105 may be located at diverse geographic locations. A network entity 105 may include an antenna array with a set of rows and columns of antenna ports that the network entity 105 may use to support beamforming of communications with a UE 115. Likewise, a UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally, or alternatively, an antenna panel may support RF beamforming for a signal transmitted via an antenna port.

Beamforming, which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that some signals propagating along particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference. The adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device. The adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation) .

The UEs 115 and the network entities 105 may support retransmissions of data to increase the likelihood that data is received successfully. Hybrid automatic repeat request (HARQ) feedback is one technique for increasing the likelihood that data is received correctly via a communication link (e.g., a communication link 125, a D2D communication link 135) . HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC) ) , forward error correction (FEC) , and retransmission (e.g., automatic repeat request (ARQ) ) . HARQ may improve throughput at the MAC layer in poor radio conditions (e.g., low signal-to-noise conditions) . In some examples, a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific slot for data received via a previous symbol in the slot. In some other examples, the device may provide HARQ feedback in a subsequent slot, or according to some other time interval.

In some examples of the wireless communications system 100, a UE 115 may operate in a DC mode (e.g., in a primary connectivity with a primary network entity 105 and in a secondary connectivity with a secondary network entity 105 in an SCG) . The UE 115 may be configured to report QoE measurements to the primary network entity 105 and the secondary network entity 105 via one or more SRBs (e.g., SRB4 or SRB5) . However, in some DC scenarios, the SCG or secondary connectivity including the secondary network entity 105 may be deactivated or released, or an active secondary network entity 105 may change from a first secondary network entity 105 to a second secondary network entity 105.

In some examples (e.g., if the SCG group or secondary connectivity is deactivated) , the UE 115 may transmit an indication to the primary network entity 105 indicating that one or more QoE measurements were configured to be reported via SRB5 (e.g., to the secondary network entity 105 in the deactivated SCG) . The primary network entity 105 may accordingly reconfigure the UE 115, for example, to report the one or more QoE measurements via SRB4 (e.g., to the primary network entity 105) , to discard the QoE measurement data, or to buffer the QoE measurement data until the SCG is reactivated. In some examples, the primary network entity 105 (e.g., or the secondary network entity 105) may indicate for the UE 115 to report one or more of the QoE measurements via SRB4 (e.g., without receiving the indication from the UE 115) . In some examples, the UE 115 may autonomously transmit the QoE measurements via SRB4, discard the QoE measurement data, or suspend the related QoE measurements until an SCG is reactivated.

In some examples (e.g., if the SCG group or secondary connectivity is released) , the UE 115 may autonomously release or discard the QoE measurement configurations. Additionally, or alternatively, the UE 115 may receive an indication (e.g., from the primary network 105 entity or from the secondary network entity 105) to release or discard one or more of the QoE measurement configurations. The UE 115 may additionally or alternatively report one or more QoE measurements (e.g., QoE measurements which were not indicated to be released or discarded) to the primary network entity 105 via SRB4.

In some examples (e.g., if the active secondary network entity 105 is changed from a first secondary network entity 105 to a second secondary network entity 105) , the UE 115 may receive an indication (e.g., from the primary network entity 105 or from the second secondary network entity 105) to release or to keep one or more of the QoE measurement configurations. If the UE 115 receives an indication to keep one or more of the QoE measurement configurations, the UE 115 may report the QoE measurements to the primary network entity 105 or to the second secondary network entity 105 (e.g., via SRB4 or via SRB5) .

FIG. 2 shows an example of a wireless communications system 200 that supports continuity measurement for DC scenarios in accordance with one or more aspects of the present disclosure. The wireless communications system 200 may implement or may be implemented by aspects of the wireless communications system 100. For example, the wireless communications system 200 may include a UE 115 (e.g., a UE 115-a) and a network entity 105 (e.g., a primary network entity 105-a, a secondary network entity 105-b, and a secondary network entity 105-c) , which may be examples of the corresponding devices as described with reference to FIG. 1.

In some examples of the wireless communications system 200, a UE 115-a may perform one or more QoE measurements. For example, the UE 115-a may measure a flow of traffic over one or more channels (e.g., uplink channels 215 or downlink channels 210) between one or more network entities 105. The UE 115-a may report the QoE measurements to the one or more network entities 105 such that the network entities 105 can adjust one or more parameters to improve a quality of the one or more channels.

In some cases, a QoE measurement procedure may be activated by a signaling-based activation procedure. For example, an operations administration and maintenance server (OAM) may initiate a QoE measurement activation by signaling a QoE measurement configuration 225 to a core network (CN) 205 associated with one or more network entities (e.g., a next generation (NG) RAN node such as a network entity 105-a) . The CN 205 may activate the QoE measurement procedure by transmitting the QoE measurement configuration 225 to the network entity 105-a. In some examples, the QoE measurement procedure may be activated by a management-based activation procedure. For example, the OAM may transmit one or more QoE measurement configurations 225 to the network entity 105-a (e.g., without transmitting the QoE measurement configurations 225 to the CN) .

In some cases, the one or more QoE measurement configurations 225 transmitted to the network entity 105-a (e.g., by the OAM or by the CN 205) may include information associated with the one or more QoE measurement configurations 225. For example, the information may include one or more of a QoE measurement collection (QMC) configuration container (e.g., as an XML file) , a QoE reference, a service type, a multicell coordination entity (MCE) IP address, an area or slice scope, minimization of drive test (MDT) alignment information, or an indication of one or more RAN-visible QoE metrics associated with the one or more QoE measurement configurations 225. The QoE reference may be an identifier which the OAM, CN 205, or the network entity 105-a may use to identify a QMC job associated with a QoE measurement configuration 225. The QoE reference may include a mobile country code (MCC) , a mobile network code (MNC) , and a QMC ID. The QoE reference may be associated with a specific QoE measurement configuration 225 (e.g., and may not be associated with any other QoE measurement configurations 225) .

The network entity 105-a may forward the QoE measurement configurations 225 to the UE 115-a (e.g., via an RRCReconfiguration message) over a downlink channel 210-a. For example, the forwarded QoE measurement configurations 225 may include information associated with the one or more QoE measurement configurations 225, such as the QMC configuration container, identification (ID) information for the QoE measurement configuration 225 (e.g., measConfigAppLayerID information) , and the service type. The ID information may be a group of bits (e.g., four bits) allocated by the network entity 105-a to identify a QoE measurement configuration 225. The ID information may be shorter than the QoE reference (e.g., to reduce signaling overhead) . The network entity 105-a may determine and maintain a mapping (e.g., a one-to-one mapping) between the ID information and the QoE reference received from the CN 205 or OAM. The UE 115-a may not maintain the mapping. The UE 115-a may receive the QoE measurement configuration 225 via an RRC layer (e.g., an access stratum (RS) layer) of the UE 115-a, and may transmit a command to an application layer of the UE 115-a to perform the QoE measurements. For example, the RRC layer may forward the QoE measurement configuration 225 (e.g., including the ID information) to the application layer.

In some examples, the OAM may initiate a deactivation or release of the QoE measurement configurations 225. For example, the OAM may trigger for the UE 115-a to deactivate QoE measurement collection by transmitting a list of QoE references to be deactivated to the CN 205 to forward to the network entity 105-a. The network entity 105-a may release one or more application layer measurement configurations from the UE 115-a by transmitting an RRCReconfiguration message (e.g., indicating the ID information associated with the deactivated QoE measurement configurations 225) . In some examples (e.g., upon or after entering an idle state) , the UE 115-a may release all QoE measurement configurations 225 autonomously. To deactivate or release the one or more QoE measurement configurations 225, the RRC layer of the UE 115-a may inform an upper layer (e.g., the application layer of the UE 115-a) to release the QoE measurement configurations 225.

In some cases, the UE 115-a may report one or more QoE measurements (e.g., measurements collected by the application layer in accordance with the QoE measurement configurations 225) in a QoE measurement report 230. For example, the RRC layer of the UE 115-a may receive a report container (e.g., containing a command to transmit the QoE measurement report 230 to the network entity 105-a) from the application layer of the UE 115-a. An application layer QoE measurement report 230 may be encapsulated in a transparent container (e.g., in a MeasurementReportAppLayer RRC message) . The RRC layer of the UE 115-a may transmit the QoE measurement report 230 to the network entity 105-a via a SRB, such as SRB4 or SRB5, over an uplink channel 215-a. The QoE measurement report 230 may include QoE measurement data and the ID information (e.g., one or more measConfigAppLayerIDs) .

The network entity 105-a may identify which application layer measurement configuration the QoE measurement report is for and may identify a multicell coordination entity (MCE) address (e.g., using the measConfigAppLayerID and the associated QoE reference) . The network entity 105-a may forward the QoE measurement report 230 to the OAM (e.g., with the QoE reference mapped to the measConfigAppLayerID) . In some examples, the network entity 105-a may enable the UE 115-a to perform segmentation of the QoE measurement report 230. That is, the UE 115-a may transmit the QoE measurement report 230 in segments (e.g., if the QoE measurement report exceeds a threshold PDCP service data unit (SDU) size) .

In some examples, the network entity 105-a may have a split architecture (e.g., may have a CU and one or more DUs) . In such examples, the CU of the network entity 105-a may generate one or more RAN-visible QoE measurement configurations 225. That is, the CU may generate one or more configurations for QoE measurements to be reported in a format visible to the network entity 105-a (e.g., without forwarding to the OAM) . In such examples, the network entity 105-a may transmit the RAN-visible QoE measurement configuration 225 and one or more non-RAN-visible QoE measurement configurations 225 to the UE 115-a together or separately. For example, the network entity 105-a may configure the UE 115-a with both QoE measurement configurations 225 at a same time, or may configure the UE 115-a with the RAN-visible QoE measurement configurations 225 after configuring the non-RAN-visible QoE measurement configurations 225. The RAN-visible QoE measurement configurations 225 may include information associated with the one or more QoE measurement configurations 225, such as one or more RAN-visible QoE metrics for the UE 115-a to report, a service type, and an RRC ID (e.g., a measConfigAppLayerID) associated with the QoE measurement configurations 225. The RRC layer of the UE 115-a may receive the RAN-visible QoE measurement configurations 225, and may forward the configurations to the application layer of the UE 115-a (e.g., including the service type and RRC ID associated with the QoE measurement configurations 225) .

In some examples of the wireless communications system 200, the UE 115-a may operate in a DC communication mode. That is, the UE 115-a may communicate with a primary network entity 105 (e.g., an MN, such as the network entity 105-a) and one or more secondary network entities 105 (e.g., SNs, such as a network entity 105-b) . The primary network entity 105-a and the secondary network entity 105-b may separately or jointly configure QoE measurement configurations 225 to the UE 115-a. For example, for signaling-based QoE measurement configurations 225, the UE 115-a may receive one or more QoE measurement configurations 225 from the primary network entity 105-a (e.g., via the downlink channel 210-a) . For management-based QoE measurement configurations 225, one or both of the primary network entity 105-a and the secondary network entity 105-b may receive the QoE measurement configurations 225 from the OAM. That is, if the primary network entity 105-a receives the QoE measurement configurations 225 from the OAM, the UE 115-a may receive one or more QoE measurement configurations 225 from the primary network entity 105-a (e.g., via the downlink channel 210-a) . If the secondary network entity 105-b receives the QoE measurement configurations 225 from the OAM, the UE 115-a may receive one or more QoE measurement configurations 225 from the secondary network entity 105-b (e.g., via a downlink channel 210-b) . If both of the primary network entity 105-a and the secondary network entity 105-b receive the QoE measurement configurations 225 from the OAM, the primary network entity 105-a and the secondary network entity 105-b may coordinate (e.g., using a backhaul message 235 via a backhaul channel 220-a) to determine which of the primary network entity 105-a and the secondary network entity 105-b may transmit the QoE measurement configurations 225 to the UE 115-a.

In some examples, the QoE measurement configurations 225 may indicate for the UE 115-a to transmit the QoE measurement report 230 via an SRB (e.g., via SRB4 to the primary network entity 105-a or via SRB5 to the secondary network entity 105-b) . For example, each QoE measurement configuration 225 may indicate which SRB the UE 115-a may use to transmit each QoE measurement report 230 (e.g., on a per-QoE measurement configuration 225 basis) .

However, in some examples (e.g., due to mobility of the UE 115-a) , the DC mode of operation used by the UE 115-a may change, which may result in a continuity issue for transmitting the QoE measurement report 230. For example, an SCG or a secondary connectivity associated with the secondary network entity 105-b may be deactivated or released, or the UE 115-a may switch from communicating with the secondary network entity 105-b to communicating with a secondary network entity 105-c. In such examples, the UE 115-a may not transmit one or more QoE measurement reports 230 which were indicated by the QoE measurement configuration 225 to be reported via SRB5 (e.g., to the secondary network entity 105-b) , or QoE measurement configurations 225 which were configured at both of the primary network entity 105-a and the secondary network entity 105-b (e.g., by the OAM) .

In some examples (e.g., if the SCG group is deactivated) , the UE 115-a may transmit an indication to the primary network entity 105-a indicating that one or more QoE measurement reports 230 were configured to be transmitted via SRB5 (e.g., to the network entity 105-b via an uplink channel 215-b) . The UE 115-a may transmit the indication in an RRC message (e.g., a UEAssistanceInformation message) . The primary network entity 105-a may accordingly reconfigure the UE 115-a, for example, to transmit the one or more QoE measurement reports 230 via SRB4 (e.g., to the primary network entity 105-a) , to discard QoE measurement data in the one or more QoE measurement reports 230, or to buffer the QoE measurement data until the SCG is reactivated.

In some examples, the primary network entity 105-a (e.g., or the secondary network entity 105-b) may indicate for the UE 115-a to transmit one or more of the QoE measurement reports 230 via SRB4 (e.g., without receiving the indication from the UE 115-a) . That is, the primary network entity 105-a or the secondary network entity 105-b may indicate (e.g., in the QoE measurement configurations 225 or in an SCG deactivation message) one or more of the QoE measurement reports 230 to report via SRB4. The indication may be per-QoE measurement configurations 225, or may apply to all QoE measurement reports 230 which were configured to be reported via SRB5. The UE 115-a may accordingly transmit the one or more QoE measurement reports 230 via SRB4 (e.g., to the primary network entity 105-a via the uplink channel 215-a) .

In some examples, the UE 115-a may autonomously transmit the QoE measurement reports 230 via SRB4 or discard the QoE measurement data. In some examples, the UE 115-a may buffer the related QoE measurement data and suspend the related QoE measurements and reporting until the SCG or secondary connectivity is reactivated (e.g., without receiving an indication from the primary network entity 105-a or the secondary network entity 105-b) .

In some examples (e.g., if the SCG is reactivated) , the UE may autonomously transmit the QoE measurements to the secondary network entity 105-b via SRB5 (e.g., via the uplink channel 215-b) . Additionally, or alternatively (e.g., if the UE 115-a suspended the QoE measurements and reporting) , the UE may autonomously resume QoE measurement and reporting to the secondary network entity 105-b via SRB5. Additionally, or alternatively, the UE may receive an indication from the primary network entity 105-a or the secondary network entity 105-b (e.g., in the QoE measurement configurations 225 or in the SCG deactivation message) to transmit one or more of the QoE measurement reports 230 via SRB5 upon or after reactivation. The indication may be per-QoE measurement configurations 225, or may apply to all QoE measurement reports 230 which were configured to be reported via SRB5. The UE 115-a may accordingly transmit the one or more QoE measurement reports 230 via SRB5 (e.g., to the secondary network entity 105-b via the uplink channel 215-b) . Such techniques may be used for container-based QoE measurement reporting and RAN-visible QoE measurement reporting.

In some examples (e.g., if the SCG group or secondary connectivity is released) , the UE 115-a may autonomously release or discard the QoE measurement configurations 225 that were configured to be reported to the secondary network entity 105-b via SRB5. For example, the RRC layer of the UE 115-a may inform the application layer of the UE 115-a to release the QoE measurement configurations 225. Additionally, or alternatively, the UE may receive an indication from the primary network entity 105-a or from the secondary network entity 105-b (e.g., in the QoE measurement configurations 225 or in the SCG release message) to release or refrain from releasing one or more of the QoE measurement configurations 225. The UE 115-a may, additionally, or alternatively, transmit one or more QoE measurement reports 230 (e.g., associated with QoE measurement configurations 225 which were not indicated to be released) to the primary network entity 105-a via SRB4. In some examples, the secondary network entity 105-b may forward the related QoE measurement configurations 225 to the primary network entity 105-a (e.g., in a backhaul message 235 via the backhaul channel 220-a) .

In some examples (e.g., if the UE 115-a switches from communicating with the secondary network entity 105-b to the secondary network entity 105-c) , the UE 115-a may receive an indication (e.g., from the primary network entity 105-a or from the secondary network entity 105-c) to release or to keep one or more of the QoE measurement configurations 225 that were configured to be reported to the secondary network entity 105-b. If the UE 115-a receives an indication to keep one or more of the QoE measurement configurations 225, the UE 115-a may report the QoE measurements to the primary network entity 105-a via the uplink channel 215-a or to the secondary network entity 105-c via an uplink channel 215-c (e.g., via SRB4 or via SRB5) .

The secondary network entity 105-c may receive an indication (e.g., from the primary network entity 105-a or from the secondary network entity 105-b) of whether the one or more QoE measurement configurations 225 can be released. That is, in some examples, the primary network entity 105-a may transmit an indication to the secondary network entity 105-c of whether the one or more QoE measurement configurations 225 can be released and whether the one or more QoE measurement configurations 225 have continuity (e.g., in an SN addition message) . The secondary network entity 105-c may receive the indication in a backhaul message 235 via a backhaul channel 220-b. The secondary network entity 105-c may transmit an acknowledgment message to the primary network entity 105-a (e.g., in a backhaul message 235 via the backhaul channel 220-b) . In some examples, the primary network entity 105-a may receive the indication of whether the one or more QoE measurement configurations 225 can be released from the secondary network entity 105-b (e.g., via the backhaul channel 220-a) , and may forward the indication to the secondary network entity 105-c.

FIG. 3 shows an example of a process flow 300 that supports continuity measurement for DC scenarios in accordance with one or more aspects of the present disclosure. The process flow 300 may implement or may be implemented by aspects of the wireless communications system 100 or the wireless communications system 200. For example, the process flow 300 may include a UE 115 (e.g., a UE 115-b) and one or more network entities 105 (e.g., a primary network entity 105-d, a secondary network entity 105-e) , which may be examples of the corresponding devices as described with reference to FIG. 1. For example, the UE 115-b may be a UE 115 operating in a DC mode with the primary network entity 105-d and the secondary network entity 105-e.

In the following description of the process flow 300, the operations between the UE 115-b, the primary network entity 105-d, and the secondary network entity 105-e may be transmitted in a different order than the example order shown. Some operations may also be omitted from the process flow 300, and other operations may be added to the process flow 300. Further, although some operations or signaling may be shown to occur at different times for discussion purposes, these operations may actually occur at the same time.

At 305, the UE 115-b may receive, from the primary network entity 105-d or the secondary network entity 105-e, one or more messages indicating one or more parameters instructing for the UE 115-b to perform a QoE measurement procedure. That is, the one or more parameters may indicate QoE measurement and reporting configurations for performing QoE measurements and reporting the QoE measurements to the secondary network entity 105-e (e.g., via SRB5) . The one or more messages may be, for example, RRC messages, medium access control-control element (MAC-CE) messages, downlink control information (DCI) messages, or the like. The UE 115-b may receive the one or more messages via a physical downlink shared channel (PDSCH) or a physical downlink control channel (PDCCH) . The UE 115-b may perform one or more QoE measurements in accordance with the QoE measurement and reporting configurations.

At 310, the UE 115-b may receive, from the primary network entity 105-d or the secondary network entity 105-e, an indication of a change associated with the DC mode. The change associated with the DC mode may be, for example, a deactivation of a secondary connectivity associated with the secondary network entity 105-e or a release of the secondary connectivity. The UE 115-b may receive the indication of the change in an RRC message, a MAC-CE message, or a DCI message. The UE 115-b may receive the indication of the change via a PDSCH or a PDCCH.

At 315, the UE 115-b may perform a QoE reporting procedure. The QoE reporting procedure may include one or more of steps 315-a, 315-b, 315-c, 315-d, 315-e, or 315-f, as described herein.

In some examples, at 315-a, the UE 115-b may transmit, to the primary network entity 105-d, an availability message indicating an availability of the one or more QoE measurements. For example, the availability message may include one or more of an indication of the one or more parameters, an indication of one or more QoE configurations for the one or more QoE measurements, or an indication that the one or more QoE measurements were configured to be reported to the secondary network entity 105-e (e.g., via SRB5) . In some examples, the primary network entity 105-d may receive, from the secondary network entity 105-e, an indication of the one or more parameters.

In some examples, at 315-b, the UE 115-b may transmit a measurement report including the one or more QoE measurements to the primary network entity 105-d (e.g., via SRB4) . The UE 115-b may transmit the one or more QoE measurements in response to receiving an indication from the primary network entity 105-d or from the secondary network entity 105-e. For example, the indication requesting the UE 115-b to transmit the one or more QoE measurements to the primary network entity 105-d may be in the one or more messages, in the indication of the change in the DC mode, or in a separate message from the primary network entity 105-d or the secondary network entity 105-e (e.g., in response to receiving the availability message) . In some examples, the UE 115-b may transmit the measurement report autonomously (e.g., without receiving a request) .

In some examples, at 315-c, the UE 115-b may discard the one or more QoE measurements. That is, if the secondary connectivity associated with the secondary network entity 105-e is deactivated, the UE 115-b may autonomously discard data associated with the one or more QoE measurements.

In some examples, at 315-d, the UE 115-b may buffer the QoE measurements. That is, if the secondary connectivity associated with the secondary network entity 105-e is deactivated, the UE 115-b may suspend the QoE measurement procedure and store the related QoE measurement data.

In some examples (e.g., in response to a reactivation of the secondary connectivity) , the UE 115-b may transmit a measurement report including the one or more QoE measurements to the secondary network entity 105-e (e.g., via SRB5) . For example, if the UE 115-b suspended the QoE measurement procedure, the UE 115-b may resume the QoE measurement procedure and may transmit the buffered QoE measurement data to the secondary network entity 105-e. In some examples, the UE 115-b may autonomously transmit the measurement report to the secondary network entity 105-e. In some examples, the UE 115-b may receive an indication requesting for the UE 115-b to transmit the measurement report to the secondary network entity 105-e from the primary network entity 105-d or from the secondary network entity 105-e. For example, the indication requesting the UE 115-b to transmit the measurement report to the secondary network entity 105-e may be in the one or more messages, in the indication of the change in the DC mode, or in a separate message from the primary network entity 105-d or the secondary network entity 105-e.

In some examples (e.g., if the secondary connectivity associated with the secondary network entity 105-e is released) , the UE 115-b may release or discard the one or more parameters. For example, the UE 115-b may discard the one or more parameters in response to receiving an indication requesting for the UE 115-b to discard the one or more parameters. The UE 115-b may receive the indication requesting for the UE 115-b to discard the one or more parameters from the primary network entity 105-d or from the secondary network entity 105-e. For example, the indication requesting the UE 115-b to discard the one or more parameters may be in the one or more messages, in the indication of the change in the DC mode, or in a separate message from the primary network entity 105-d or the secondary network entity 105-e. In some examples, the UE 115-b may discard the one or more parameters autonomously (e.g., without receiving the indication) .

FIG. 4 shows an example of a process flow 400 that supports continuity measurement for DC scenarios in accordance with one or more aspects of the present disclosure. The process flow 400 may implement or may be implemented by aspects of the wireless communications system 100, the wireless communications system 200, or the process flow 300. For example, the process flow 400 may include a UE 115 (e.g., a UE 115-c) and one or more network entities 105 (e.g., a primary network entity 105-f, a secondary network entity 105-g, and a secondary network entity 105-h) , which may be examples of the corresponding devices as described with reference to FIG. 1. For example, the UE 115-c may be a UE 115 operating in a DC mode with the primary network entity 105-f and the secondary network entity 105-g.

In the following description of the process flow 400, the operations between the UE 115-c, the primary network entity 105-f, the secondary network entity 105-g, and the secondary network entity 105-h may be transmitted in a different order than the example order shown. Some operations may also be omitted from the process flow 400, and other operations may be added to the process flow 400. Further, although some operations or signaling may be shown to occur at different times for discussion purposes, these operations may actually occur at the same time.

At 405, the UE 115-c may receive, from the primary network entity 105-f or the secondary network entity 105-g, one or more messages indicating one or more parameters instructing the UE 115-c to perform a QoE measurement procedure. That is, the one or more parameters may indicate QoE measurement and reporting configurations for performing QoE measurements and reporting the QoE measurements to the secondary network entity 105-g (e.g., via SRB5) . The one or more messages may be, for example, RRC messages, MAC-CE messages, downlink control information DCI messages, or the like. The UE 115-c may receive the one or more messages via a PDSCH or a PDCCH. The UE 115-c may perform one or more QoE measurements in accordance with the QoE measurement and reporting configurations.

At 410, the UE 115-c may receive, from the primary network entity 105-f or the secondary network entity 105-g, an indication of a change associated with the DC mode. The change associated with the DC mode may be, for example, a node switch associated with the secondary network entity 105-g. That is, the indication may indicate for the UE 115-c to switch from communicating with the secondary network entity 105-g to communicating with the secondary network entity 105-h. The UE 115-c may receive the indication of the change in an RRC message, a MAC-CE message, or a DCI message. The UE 115-c may receive the indication of the change via a PDSCH or a PDCCH.

In some examples, at 415, the secondary network entity 105-g may transmit, to the primary network entity 105-f, an indication of the one or more parameters. The indication may indicate one or more parameters for the UE 115-c to release (e.g., and one or more additional parameters for the UE 115-c to maintain) . The indication may be in an SN change indication message.

In some examples, at 420, the primary network entity 105-f may transmit, to the secondary network entity 105-h, an indication of the one or more parameters (e.g., via an SN addition indication message) . The indication may indicate the one or more parameters for the UE 115-c to release (e.g., and the one or more additional parameters for the UE 115-c to maintain) . In some examples, the primary network entity 105-f may transmit the indication in response to receiving the indication from the secondary network entity 105-g. In some examples, the primary network entity 105-f may transmit the indication without receiving the indication from the secondary network entity 105-g.

In some examples, at 425, the secondary network entity 105-h may transmit an acknowledgment message to the primary network entity 105-f. For example, the secondary network entity 105-h may transmit the acknowledgment message in response to receiving the indication from the primary network entity 105-f. The acknowledgment message may be, for example, an SN addition acknowledgment message.

At 430, the UE 115-c may perform a QoE reporting procedure. The QoE reporting procedure may include one or more of steps 430-a, 430-b, or 430-c as described herein.

In some examples, at 430-a, the UE 115-c may release or discard the one or more parameters. For example, the UE 115-c may discard the one or more parameters in response to receiving an indication requesting for the UE 115-c to discard the one or more parameters. The UE 115-b may receive the indication requesting for the UE 115-c to discard the one or more parameters from the primary network entity 105-f, from the secondary network entity 105-g, or from the secondary network entity 105-h. For example, the indication requesting for the UE 115-b to discard the one or more parameters may be in the one or more messages, in the indication of the change in the DC mode, or in a separate message from the primary network entity 105-f, the secondary network entity 105-g, or the secondary network entity 105-h. In some examples, the UE 115-b may discard the one or more parameters autonomously (e.g., without receiving the indication) .

In some examples, at 430-b, the UE 115-c may transmit a measurement report including the one or more QoE measurements to the secondary network entity 105-h (e.g., via SRB4 or SRB5) . In some examples, the UE 115-c may autonomously transmit the measurement report to the secondary network entity 105-h. In some examples, the UE 115-c may receive an indication requesting for the UE 115-c to transmit the measurement report to the secondary network entity 105-h from the primary network entity 105-f, from the secondary network entity 105-g, or from the secondary network entity 105-h. For example, the indication requesting the UE 115-c to transmit the measurement report to the secondary network entity 105-h may be in the one or more messages, in the indication of the change in the DC mode, or in a separate message from the primary network entity 105-f, the secondary network entity 105-g, or the secondary network entity 105-h.

In some examples, at 430-c, the UE 115-c may transmit a measurement report including the one or more QoE measurements to the primary network entity 105-f (e.g., via SRB4) . In some examples, the UE 115-c may autonomously transmit the measurement report to the primary network entity 105-f. In some examples, the UE 115-c may receive an indication requesting for the UE 115-c to transmit the measurement report to the primary network entity 105-f from the primary network entity 105-f, from the secondary network entity 105-g, or from the secondary network entity 105-h. For example, the indication requesting the UE 115-c to transmit the measurement report to the primary network entity 105-f may be in the one or more messages, in the indication of the change in the DC mode, or in a separate message from the primary network entity 105-f, the secondary network entity 105-g, or the secondary network entity 105-h.

FIG. 5 shows a block diagram 500 of a device 505 that supports continuity measurement for DC scenarios in accordance with one or more aspects of the present disclosure. The device 505 may be an example of aspects of a UE 115 as described herein. The device 505 may include a receiver 510, a transmitter 515, and a communications manager 520. The device 505, or one or more components of the device 505 (e.g., the receiver 510, the transmitter 515, and the communications manager 520) , may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .

The receiver 510 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to continuity measurement for DC scenarios) . Information may be passed on to other components of the device 505. The receiver 510 may utilize a single antenna or a set of multiple antennas.

The transmitter 515 may provide a means for transmitting signals generated by other components of the device 505. For example, the transmitter 515 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to continuity measurement for DC scenarios) . In some examples, the transmitter 515 may be co-located with a receiver 510 in a transceiver module. The transmitter 515 may utilize a single antenna or a set of multiple antennas.

The communications manager 520, the receiver 510, the transmitter 515, or various combinations thereof or various components thereof may be examples of means for performing various aspects of continuity measurement for DC scenarios as described herein. For example, the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be capable of performing one or more of the functions described herein.

In some examples, the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) . The hardware may include at least one of a processor, a digital signal processor (DSP) , a central processing unit (CPU) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure. In some examples, at least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory) .

Additionally, or alternatively, the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor. If implemented in code executed by at least one processor, the functions of the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure) .

In some examples, the communications manager 520 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 510, the transmitter 515, or both. For example, the communications manager 520 may receive information from the receiver 510, send information to the transmitter 515, or be integrated in combination with the receiver 510, the transmitter 515, or both to obtain information, output information, or perform various other operations as described herein.

The communications manager 520 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 520 is capable of, configured to, or operable to support a means for receiving, by the UE operating in a DC mode with a primary network entity and a secondary network entity, one or more messages indicating one or more parameters associated with a QoE measurement procedure for the secondary network entity. The communications manager 520 is capable of, configured to, or operable to support a means for performing, by the UE operating in the DC mode, one or more QoE measurements based on the one or more parameters associated with the QoE measurement procedure. The communications manager 520 is capable of, configured to, or operable to support a means for receiving an indication of a change associated with the DC mode. The communications manager 520 is capable of, configured to, or operable to support a means for performing a QoE reporting procedure associated with the one or more QoE measurements based on the change associated with the DC mode.

By including or configuring the communications manager 520 in accordance with examples as described herein, the device 505 (e.g., at least one processor controlling or otherwise coupled with the receiver 510, the transmitter 515, the communications manager 520, or a combination thereof) may support techniques for resolving continuity issues for QoE reporting, which may result in improved utilization of communication resources as a result of channel quality reporting.

FIG. 6 shows a block diagram 600 of a device 605 that supports continuity measurement for DC scenarios in accordance with one or more aspects of the present disclosure. The device 605 may be an example of aspects of a device 505 or a UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communications manager 620. The device 605, or one or more components of the device 605 (e.g., the receiver 610, the transmitter 615, and the communications manager 620) , may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .

The receiver 610 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to continuity measurement for DC scenarios) . Information may be passed on to other components of the device 605. The receiver 610 may utilize a single antenna or a set of multiple antennas.

The transmitter 615 may provide a means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to continuity measurement for DC scenarios) . In some examples, the transmitter 615 may be co-located with a receiver 610 in a transceiver module. The transmitter 615 may utilize a single antenna or a set of multiple antennas.

The device 605, or various components thereof, may be an example of means for performing various aspects of continuity measurement for DC scenarios as described herein. For example, the communications manager 620 may include a QoE measurement configuration manager 625, a QoE measurement performing manager 630, a DC mode change indication reception manager 635, a QoE reporting procedure manager 640, or any combination thereof. The communications manager 620 may be an example of aspects of a communications manager 520 as described herein. In some examples, the communications manager 620, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 610, the transmitter 615, or both. For example, the communications manager 620 may receive information from the receiver 610, send information to the transmitter 615, or be integrated in combination with the receiver 610, the transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

The communications manager 620 may support wireless communications in accordance with examples as disclosed herein. The QoE measurement configuration manager 625 is capable of, configured to, or operable to support a means for receiving, by the UE operating in a DC mode with a primary network entity and a secondary network entity, one or more messages indicating one or more parameters associated with a QoE measurement procedure for the secondary network entity. The QoE measurement performing manager 630 is capable of, configured to, or operable to support a means for performing, by the UE operating in the DC mode, one or more QoE measurements based on the one or more parameters associated with the QoE measurement procedure. The DC mode change indication reception manager 635 is capable of, configured to, or operable to support a means for receiving an indication of a change associated with the DC mode. The QoE reporting procedure manager 640 is capable of, configured to, or operable to support a means for performing a QoE reporting procedure associated with the one or more QoE measurements based on the change associated with the DC mode.

FIG. 7 shows a block diagram 700 of a communications manager 720 that supports continuity measurement for DC scenarios in accordance with one or more aspects of the present disclosure. The communications manager 720 may be an example of aspects of a communications manager 520, a communications manager 620, or both, as described herein. The communications manager 720, or various components thereof, may be an example of means for performing various aspects of continuity measurement for DC scenarios as described herein. For example, the communications manager 720 may include a QoE measurement configuration manager 725, a QoE measurement performing manager 730, a DC mode change indication reception manager 735, a QoE reporting procedure manager 740, a QoE measurement report transmission manager 745, a QoE availability message manager 750, a QoE measurement discarding manager 755, a QoE measurement suspension manager 760, a QoE measurement resumption manager 765, a QoE measurement configuration discarding manager 770, a QoE measurement request manager 775, a QoE measurement configuration discarding request manager 780, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories) , may communicate, directly or indirectly, with one another (e.g., via one or more buses) .

The communications manager 720 may support wireless communications in accordance with examples as disclosed herein. The QoE measurement configuration manager 725 is capable of, configured to, or operable to support a means for receiving, by the UE operating in a DC mode with a primary network entity and a secondary network entity, one or more messages indicating one or more parameters associated with a QoE measurement procedure for the secondary network entity. The QoE measurement performing manager 730 is capable of, configured to, or operable to support a means for performing, by the UE operating in the DC mode, one or more QoE measurements based on the one or more parameters associated with the QoE measurement procedure. The DC mode change indication reception manager 735 is capable of, configured to, or operable to support a means for receiving an indication of a change associated with the DC mode. The QoE reporting procedure manager 740 is capable of, configured to, or operable to support a means for performing a QoE reporting procedure associated with the one or more QoE measurements based on the change associated with the DC mode.

In some examples, to support performing the QoE reporting procedure, the QoE measurement report transmission manager 745 is capable of, configured to, or operable to support a means for transmitting, to the primary network entity via a radio bearer associated with the primary network entity, a measurement report indicating the one or more QoE measurements based on the change associated with the DC mode, where the change associated with the DC mode includes one of a deactivation of a secondary connectivity associated with the secondary network entity, a release of the secondary connectivity, or a node switch associated with the secondary network entity.

In some examples, the QoE measurement request manager 775 is capable of, configured to, or operable to support a means for receiving a second indication requesting the UE to transmit the one or more QoE measurements to the primary network entity via the radio bearer associated with the primary network entity.

In some examples, the QoE availability message manager 750 is capable of, configured to, or operable to support a means for transmitting, to the primary network entity, an availability message indicating an availability of the one or more QoE measurements associated with the QoE measurement procedure for the secondary network entity.

In some examples, the change associated with the DC mode includes a deactivation of a secondary connectivity associated with the secondary network entity, and the QoE measurement report transmission manager 745 is capable of, configured to, or operable to support a means for transmitting, to the secondary network entity via a radio bearer associated with the secondary network entity, a measurement report indicating the one or more QoE measurements based on a reactivation of the secondary connectivity associated with the secondary network entity.

In some examples, the QoE measurement request manager 775 is capable of, configured to, or operable to support a means for receiving a third indication requesting for the UE to transmit the one or more QoE measurements to the secondary network entity via the radio bearer associated with the secondary network entity, where transmitting the measurement report to the secondary network entity via the radio bearer associated with the secondary network entity is based on receiving the third indication.

In some examples, to support performing the QoE reporting procedure, the QoE measurement discarding manager 755 is capable of, configured to, or operable to support a means for discarding the one or more QoE measurements.

In some examples, to support performing the QoE reporting procedure, the QoE measurement suspension manager 760 is capable of, configured to, or operable to support a means for suspending the QoE measurement procedure. In some examples, to support performing the QoE reporting procedure, the QoE measurement resumption manager 765 is capable of, configured to, or operable to support a means for resuming the QoE measurement procedure based on a reactivation of the secondary connectivity.

In some examples, to support performing the QoE reporting procedure, the QoE measurement configuration discarding manager 770 is capable of, configured to, or operable to support a means for discarding the one or more parameters associated with the QoE measurement procedure, where the change associated with the DC mode includes one of a release of a secondary connectivity associated with the secondary network entity or a node switch associated with the secondary network entity.

In some examples, the QoE measurement configuration discarding request manager 780 is capable of, configured to, or operable to support a means for receiving a fourth indication requesting for the UE to discard the one or more parameters, where discarding the one or more parameters is based on receiving the fourth indication.

In some examples, the change associated with the DC mode includes a deactivation of a secondary connectivity associated with the secondary network entity.

In some examples, the change associated with the DC mode includes a release of a secondary connectivity associated with the secondary network entity.

In some examples, the change associated with the DC mode includes a switch from the secondary network entity to an additional secondary network entity.

FIG. 8 shows a diagram of a system 800 including a device 805 that supports continuity measurement for DC scenarios in accordance with one or more aspects of the present disclosure. The device 805 may be an example of or include the components of a device 505, a device 605, or a UE 115 as described herein. The device 805 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 805 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 820, an input/output (I/O) controller 810, a transceiver 815, an antenna 825, at least one memory 830, code 835, and at least one processor 840. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 845) .

The I/O controller 810 may manage input and output signals for the device 805. The I/O controller 810 may also manage peripherals not integrated into the device 805. In some cases, the I/O controller 810 may represent a physical connection or port to an external peripheral. In some cases, the I/O controller 810 may utilize an operating system such as or another known operating system. Additionally, or alternatively, the I/O controller 810 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, the I/O controller 810 may be implemented as part of one or more processors, such as the at least one processor 840. In some cases, a user may interact with the device 805 via the I/O controller 810 or via hardware components controlled by the I/O controller 810.

In some cases, the device 805 may include a single antenna 825. However, in some other cases, the device 805 may have more than one antenna 825, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 815 may communicate bi-directionally, via the one or more antennas 825, wired, or wireless links as described herein. For example, the transceiver 815 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 815 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 825 for transmission, and to demodulate packets received from the one or more antennas 825. The transceiver 815, or the transceiver 815 and one or more antennas 825, may be an example of a transmitter 515, a transmitter 615, a receiver 510, a receiver 610, or any combination thereof or component thereof, as described herein.

The at least one memory 830 may include random access memory (RAM) and read-only memory (ROM) . The at least one memory 830 may store computer-readable, computer-executable code 835 including instructions that, when executed by the at least one processor 840, cause the device 805 to perform various functions described herein. The code 835 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 835 may not be directly executable by the at least one processor 840 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the at least one memory 830 may contain, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.

The at least one processor 840 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) . In some cases, the at least one processor 840 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the at least one processor 840. The at least one processor 840 may be configured to execute computer-readable instructions stored in a memory (e.g., the at least one memory 830) to cause the device 805 to perform various functions (e.g., functions or tasks supporting continuity measurement for DC scenarios) . For example, the device 805 or a component of the device 805 may include at least one processor 840 and at least one memory 830 coupled with or to the at least one processor 840, the at least one processor 840 and at least one memory 830 configured to perform various functions described herein. In some examples, the at least one processor 840 may include multiple processors and the at least one memory 830 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein. In some examples, the at least one processor 840 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 840) and memory circuitry (which may include the at least one memory 830) ) , or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. As such, the at least one processor 840 or a processing system including the at least one processor 840 may be configured to, configurable to, or operable to cause the device 805 to perform one or more of the functions described herein. Further, as described herein, being “configured to, ” being “configurable to, ” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code stored in the at least one memory 830 or otherwise, to perform one or more of the functions described herein.

The communications manager 820 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 820 is capable of, configured to, or operable to support a means for receiving, by the UE operating in a DC mode with a primary network entity and a secondary network entity, one or more messages indicating one or more parameters associated with a QoE measurement procedure for the secondary network entity. The communications manager 820 is capable of, configured to, or operable to support a means for performing, by the UE operating in the DC mode, one or more QoE measurements based on the one or more parameters associated with the QoE measurement procedure. The communications manager 820 is capable of, configured to, or operable to support a means for receiving an indication of a change associated with the DC mode. The communications manager 820 is capable of, configured to, or operable to support a means for performing a QoE reporting procedure associated with the one or more QoE measurements based on the change associated with the DC mode.

By including or configuring the communications manager 820 in accordance with examples as described herein, the device 805 may support techniques for resolving continuity issues for QoE reporting, which may result in improved communication reliability and improved coordination between devices.

In some examples, the communications manager 820 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 815, the one or more antennas 825, or any combination thereof. Although the communications manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 820 may be supported by or performed by the at least one processor 840, the at least one memory 830, the code 835, or any combination thereof. For example, the code 835 may include instructions executable by the at least one processor 840 to cause the device 805 to perform various aspects of continuity measurement for DC scenarios as described herein, or the at least one processor 840 and the at least one memory 830 may be otherwise configured to, individually or collectively, perform or support such operations.

FIG. 9 shows a block diagram 900 of a device 905 that supports continuity measurement for DC scenarios in accordance with one or more aspects of the present disclosure. The device 905 may be an example of aspects of a network entity 105 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communications manager 920. The device 905, or one or more components of the device 905 (e.g., the receiver 910, the transmitter 915, and the communications manager 920) , may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .

The receiver 910 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) . Information may be passed on to other components of the device 905. In some examples, the receiver 910 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 910 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

The transmitter 915 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 905. For example, the transmitter 915 may output information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) . In some examples, the transmitter 915 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 915 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 915 and the receiver 910 may be co-located in a transceiver, which may include or be coupled with a modem.

The communications manager 920, the receiver 910, the transmitter 915, or various combinations thereof or various components thereof may be examples of means for performing various aspects of continuity measurement for DC scenarios as described herein. For example, the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be capable of performing one or more of the functions described herein.

In some examples, the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) . The hardware may include at least one of a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure. In some examples, at least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory) .

Additionally, or alternatively, the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor. If implemented in code executed by at least one processor, the functions of the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure) .

In some examples, the communications manager 920 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 910, the transmitter 915, or both. For example, the communications manager 920 may receive information from the receiver 910, send information to the transmitter 915, or be integrated in combination with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

The communications manager 920 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 920 is capable of, configured to, or operable to support a means for transmitting, to a UE operating in a DC mode associated with a primary network entity and a secondary network entity, one or more messages indicating one or more parameters associated with a QoE measurement procedure for the secondary network entity, where the one or more parameters instruct the UE to perform one or more QoE measurements. The communications manager 920 is capable of, configured to, or operable to support a means for transmitting, to the UE, an indication of a change associated with the DC mode.

By including or configuring the communications manager 920 in accordance with examples as described herein, the device 905 (e.g., at least one processor controlling or otherwise coupled with the receiver 910, the transmitter 915, the communications manager 920, or a combination thereof) may support techniques for resolving continuity issues for QoE reporting, which may result in improved utilization of communication resources due to reporting of channel quality.

FIG. 10 shows a block diagram 1000 of a device 1005 that supports continuity measurement for DC scenarios in accordance with one or more aspects of the present disclosure. The device 1005 may be an example of aspects of a device 905 or a network entity 105 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communications manager 1020. The device 1005, or one or more components of the device 1005 (e.g., the receiver 1010, the transmitter 1015, and the communications manager 1020) , may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .

The receiver 1010 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) . Information may be passed on to other components of the device 1005. In some examples, the receiver 1010 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 1010 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

The transmitter 1015 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 1005. For example, the transmitter 1015 may output information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) . In some examples, the transmitter 1015 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 1015 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1015 and the receiver 1010 may be co-located in a transceiver, which may include or be coupled with a modem.

The device 1005, or various components thereof, may be an example of means for performing various aspects of continuity measurement for DC scenarios as described herein. For example, the communications manager 1020 may include a QoE measurement configuration component 1025 a DC mode change indication transmission component 1030, or any combination thereof. The communications manager 1020 may be an example of aspects of a communications manager 920 as described herein. In some examples, the communications manager 1020, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1010, the transmitter 1015, or both. For example, the communications manager 1020 may receive information from the receiver 1010, send information to the transmitter 1015, or be integrated in combination with the receiver 1010, the transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

The communications manager 1020 may support wireless communications in accordance with examples as disclosed herein. The QoE measurement configuration component 1025 is capable of, configured to, or operable to support a means for transmitting, to a UE operating in a DC mode associated with a primary network entity and a secondary network entity, one or more messages indicating one or more parameters associated with a QoE measurement procedure for the secondary network entity, where the one or more parameters instruct the UE to perform one or more QoE measurements. The DC mode change indication transmission component 1030 is capable of, configured to, or operable to support a means for transmitting, to the UE, an indication of a change associated with the DC mode.

FIG. 11 shows a block diagram 1100 of a communications manager 1120 that supports continuity measurement for DC scenarios in accordance with one or more aspects of the present disclosure. The communications manager 1120 may be an example of aspects of a communications manager 920, a communications manager 1020, or both, as described herein. The communications manager 1120, or various components thereof, may be an example of means for performing various aspects of continuity measurement for DC scenarios as described herein. For example, the communications manager 1120 may include a QoE measurement configuration component 1125, a DC mode change indication transmission component 1130, a QoE measurement report reception component 1135, a QoE measurement report request component 1140, a QoE measurement availability message reception component 1145, a QoE measurement configuration discarding request transmission component 1150, a QoE measurement configuration indication reception component 1155, a QoE measurement configuration indication transmission component 1160, a QoE measurement configuration indication acknowledgment reception component 1165, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories) , may communicate, directly or indirectly, with one another (e.g., via one or more buses) which may include communications within a protocol layer of a protocol stack, communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity 105, between devices, components, or virtualized components associated with a network entity 105) , or any combination thereof.

The communications manager 1120 may support wireless communications in accordance with examples as disclosed herein. The QoE measurement configuration component 1125 is capable of, configured to, or operable to support a means for transmitting, to a UE operating in a DC mode associated with a primary network entity and a secondary network entity, one or more messages indicating one or more parameters associated with a QoE measurement procedure for the secondary network entity, where the one or more parameters instruct the UE to perform one or more QoE measurements. The DC mode change indication transmission component 1130 is capable of, configured to, or operable to support a means for transmitting, to the UE, an indication of a change associated with the DC mode.

In some examples, the QoE measurement report reception component 1135 is capable of, configured to, or operable to support a means for receiving, from the UE via a radio bearer associated with the primary network entity, a measurement report indicating the one or more of QoE measurements based on the change associated with the DC mode, where the change associated with the DC mode includes one of a deactivation of a secondary connectivity associated with the secondary network entity, a release of the secondary connectivity, or a node switch associated with the secondary network entity, and where the network entity is the primary network entity.

In some examples, the QoE measurement report request component 1140 is capable of, configured to, or operable to support a means for transmitting a second indication requesting for the UE to transmit the one or more QoE measurements to the primary network entity via a radio bearer associated with the primary network entity based on the change associated with the DC mode, where the change associated with the DC mode includes one of a deactivation of a secondary connectivity associated with the secondary network entity, a release of the secondary connectivity, or a node switch associated with the secondary network entity.

In some examples, the QoE measurement availability message reception component 1145 is capable of, configured to, or operable to support a means for receiving, from the UE, an availability message indicating an availability of the one or more QoE measurements associated with the QoE measurement procedure for the secondary network entity.

In some examples, the QoE measurement report reception component 1135 is capable of, configured to, or operable to support a means for receiving, via a radio bearer associated with the secondary network entity, a measurement report indicating the one or more QoE measurements based on a reactivation of the secondary connectivity, where the network entity is the secondary network entity.

In some examples, the QoE measurement report request component 1140 is capable of, configured to, or operable to support a means for transmitting, to the UE, a third indication requesting the UE to transmit the one or more QoE measurements to the secondary network entity based on a reactivation of the secondary connectivity.

In some examples, the QoE measurement configuration discarding request transmission component 1150 is capable of, configured to, or operable to support a means for transmitting, to the UE, a fourth indication requesting the UE to discard the one or more parameters.

In some examples, the QoE measurement configuration indication reception component 1155 is capable of, configured to, or operable to support a means for receiving, from the secondary network entity, an indication of the one or more parameters associated with the QoE measurement procedure, where the network entity is the primary network entity.

In some examples, the change associated with the DC mode includes a node switch from the secondary network entity to an additional secondary network entity.

In some examples, the QoE measurement configuration indication transmission component 1160 is capable of, configured to, or operable to support a means for transmitting, to the additional secondary network entity, an indication of the one or more parameters, where the network entity is the primary network entity. In some examples, the QoE measurement configuration indication acknowledgment reception component 1165 is capable of, configured to, or operable to support a means for receiving, from the additional secondary network entity, an acknowledgment message based on transmitting the indication of the one or more parameters.

In some examples, the QoE measurement configuration indication reception component 1155 is capable of, configured to, or operable to support a means for receiving, from the secondary network entity, an indication of the one or more parameters for the UE to discard and one or more additional parameters for the UE to maintain.

FIG. 12 shows a diagram of a system 1200 including a device 1205 that supports continuity measurement for DC scenarios in accordance with one or more aspects of the present disclosure. The device 1205 may be an example of or include the components of a device 905, a device 1005, or a network entity 105 as described herein. The device 1205 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communications over one or more wired interfaces, over one or more wireless interfaces, or any combination thereof. The device 1205 may include components that support outputting and obtaining communications, such as a communications manager 1220, a transceiver 1210, an antenna 1215, at least one memory 1225, code 1230, and at least one processor 1235. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1240) .

The transceiver 1210 may support bi-directional communications via wired links, wireless links, or both as described herein. In some examples, the transceiver 1210 may include a wired transceiver and may communicate bi-directionally with another wired transceiver. Additionally, or alternatively, in some examples, the transceiver 1210 may include a wireless transceiver and may communicate bi-directionally with another wireless transceiver. In some examples, the device 1205 may include one or more antennas 1215, which may be capable of transmitting or receiving wireless transmissions (e.g., concurrently) . The transceiver 1210 may also include a modem to modulate signals, to provide the modulated signals for transmission (e.g., by one or more antennas 1215, by a wired transmitter) , to receive modulated signals (e.g., from one or more antennas 1215, from a wired receiver) , and to demodulate signals. In some implementations, the transceiver 1210 may include one or more interfaces, such as one or more interfaces coupled with the one or more antennas 1215 that are configured to support various receiving or obtaining operations, or one or more interfaces coupled with the one or more antennas 1215 that are configured to support various transmitting or outputting operations, or a combination thereof. In some implementations, the transceiver 1210 may include or be configured for coupling with one or more processors or one or more memory components that are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other outputting, or any combination thereof. In some implementations, the transceiver 1210, or the transceiver 1210 and the one or more antennas 1215, or the transceiver 1210 and the one or more antennas 1215 and one or more processors or one or more memory components (e.g., the at least one processor 1235, the at least one memory 1225, or both) , may be included in a chip or chip assembly that is installed in the device 1205. In some examples, the transceiver 1210 may be operable to support communications via one or more communications links (e.g., a communication link 125, a backhaul communication link 120, a midhaul communication link 162, a fronthaul communication link 168) .

The at least one memory 1225 may include RAM, ROM, or any combination thereof. The at least one memory 1225 may store computer-readable, computer-executable code 1230 including instructions that, when executed by one or more of the at least one processor 1235, cause the device 1205 to perform various functions described herein. The code 1230 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1230 may not be directly executable by a processor of the at least one processor 1235 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the at least one memory 1225 may contain, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices. In some examples, the at least one processor 1235 may include multiple processors and the at least one memory 1225 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories which may, individually or collectively, be configured to perform various functions herein (for example, as part of a processing system) .

The at least one processor 1235 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, discrete gate or transistor logic, a discrete hardware component, or any combination thereof) . In some cases, the at least one processor 1235 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into one or more of the at least one processor 1235. The at least one processor 1235 may be configured to execute computer-readable instructions stored in a memory (e.g., one or more of the at least one memory 1225) to cause the device 1205 to perform various functions (e.g., functions or tasks supporting continuity measurement for DC scenarios) . For example, the device 1205 or a component of the device 1205 may include at least one processor 1235 and at least one memory 1225 coupled with one or more of the at least one processor 1235, the at least one processor 1235 and the at least one memory 1225 configured to perform various functions described herein. The at least one processor 1235 may be an example of a cloud-computing platform (e.g., one or more physical nodes and supporting software such as operating systems, virtual machines, or container instances) that may host the functions (e.g., by executing code 1230) to perform the functions of the device 1205. The at least one processor 1235 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1205 (such as within one or more of the at least one memory 1225) . In some examples, the at least one processor 1235 may include multiple processors and the at least one memory 1225 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein. In some examples, the at least one processor 1235 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 1235) and memory circuitry (which may include the at least one memory 1225) ) , or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. As such, the at least one processor 1235 or a processing system including the at least one processor 1235 may be configured to, configurable to, or operable to cause the device 1205 to perform one or more of the functions described herein. Further, as described herein, being “configured to, ” being “configurable to, ” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code stored in the at least one memory 1225 or otherwise, to perform one or more of the functions described herein.

In some examples, a bus 1240 may support communications of (e.g., within) a protocol layer of a protocol stack. In some examples, a bus 1240 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack) , which may include communications performed within a component of the device 1205, or between different components of the device 1205 that may be co-located or located in different locations (e.g., where the device 1205 may refer to a system in which one or more of the communications manager 1220, the transceiver 1210, the at least one memory 1225, the code 1230, and the at least one processor 1235 may be located in one of the different components or divided between different components) .

In some examples, the communications manager 1220 may manage aspects of communications with a core network 130 (e.g., via one or more wired or wireless backhaul links) . For example, the communications manager 1220 may manage the transfer of data communications for client devices, such as one or more UEs 115. In some examples, the communications manager 1220 may manage communications with other network entities 105, and may include a controller or scheduler for controlling communications with UEs 115 in cooperation with other network entities 105. In some examples, the communications manager 1220 may support an X2 interface within an LTE/LTE-A wireless communications network technology to provide communication between network entities 105.

The communications manager 1220 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 1220 is capable of, configured to, or operable to support a means for transmitting, to a UE operating in a DC mode associated with a primary network entity and a secondary network entity, one or more messages indicating one or more parameters associated with a QoE measurement procedure for the secondary network entity, where the one or more parameters instruct the UE to perform one or more QoE measurements. The communications manager 1220 is capable of, configured to, or operable to support a means for transmitting, to the UE, an indication of a change associated with the DC mode.

By including or configuring the communications manager 1220 in accordance with examples as described herein, the device 1205 may support techniques for resolving continuity issues for QoE reporting, which may result in improved communication reliability and improved coordination between devices.

In some examples, the communications manager 1220 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the transceiver 1210, the one or more antennas 1215 (e.g., where applicable) , or any combination thereof. Although the communications manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1220 may be supported by or performed by the transceiver 1210, one or more of the at least one processor 1235, one or more of the at least one memory 1225, the code 1230, or any combination thereof (for example, by a processing system including at least a portion of the at least one processor 1235, the at least one memory 1225, the code 1230, or any combination thereof) . For example, the code 1230 may include instructions executable by one or more of the at least one processor 1235 to cause the device 1205 to perform various aspects of continuity measurement for DC scenarios as described herein, or the at least one processor 1235 and the at least one memory 1225 may be otherwise configured to, individually or collectively, perform or support such operations.

FIG. 13 shows a flowchart illustrating a method 1300 that supports continuity measurement for DC scenarios in accordance with aspects of the present disclosure. The operations of the method 1300 may be implemented by a UE or its components as described herein. For example, the operations of the method 1300 may be performed by a UE 115 as described with reference to FIGs. 1 through 8. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

At 1305, the method may include receiving, by the UE operating in a DC mode with a primary network entity and a secondary network entity, one or more messages indicating one or more parameters associated with a QoE measurement procedure for the secondary network entity. The operations of 1305 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed by a QoE measurement configuration manager 725 as described with reference to FIG. 7.

At 1310, the method may include performing, by the UE operating in the DC mode, one or more QoE measurements based on the one or more parameters associated with the QoE measurement procedure. The operations of 1310 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed by a QoE measurement performing manager 730 as described with reference to FIG. 7.

At 1315, the method may include receiving an indication of a change associated with the DC mode. The operations of 1315 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1315 may be performed by a DC mode change indication reception manager 735 as described with reference to FIG. 7.

At 1320, the method may include performing a QoE reporting procedure associated with the one or more QoE measurements based on the change associated with the DC mode. The operations of 1320 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1320 may be performed by a QoE reporting procedure manager 740 as described with reference to FIG. 7.

FIG. 14 shows a flowchart illustrating a method 1400 that supports continuity measurement for DC scenarios in accordance with aspects of the present disclosure. The operations of the method 1400 may be implemented by a UE or its components as described herein. For example, the operations of the method 1400 may be performed by a UE 115 as described with reference to FIGs. 1 through 8. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

At 1405, the method may include receiving, by the UE operating in a DC mode with a primary network entity and a secondary network entity, one or more messages indicating one or more parameters associated with a QoE measurement procedure for the secondary network entity. The operations of 1405 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed by a QoE measurement configuration manager 725 as described with reference to FIG. 7.

At 1410, the method may include performing, by the UE operating in the DC mode, one or more QoE measurements based on the one or more parameters associated with the QoE measurement procedure. The operations of 1410 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed by a QoE measurement performing manager 730 as described with reference to FIG. 7.

At 1415, the method may include receiving an indication of a change associated with the DC mode. The operations of 1415 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed by a DC mode change indication reception manager 735 as described with reference to FIG. 7.

At 1420, the method may include performing a QoE reporting procedure associated with the one or more QoE measurements based on the change associated with the DC mode. The operations of 1420 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1420 may be performed by a QoE reporting procedure manager 740 as described with reference to FIG. 7.

At 1425, the method may include transmitting, to the primary network entity via a radio bearer associated with the primary network entity, a measurement report indicating the one or more QoE measurements based on the change associated with the DC mode, where the change associated with the DC mode includes one of a deactivation of a secondary connectivity associated with the secondary network entity, a release of the secondary connectivity, or a node switch associated with the secondary network entity. The operations of 1425 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1425 may be performed by a QoE measurement report transmission manager 745 as described with reference to FIG. 7.

FIG. 15 shows a flowchart illustrating a method 1500 that supports continuity measurement for DC scenarios in accordance with aspects of the present disclosure. The operations of the method 1500 may be implemented by a UE or its components as described herein. For example, the operations of the method 1500 may be performed by a UE 115 as described with reference to FIGs. 1 through 8. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

At 1505, the method may include receiving, by the UE operating in a DC mode with a primary network entity and a secondary network entity, one or more messages indicating one or more parameters associated with a QoE measurement procedure for the secondary network entity. The operations of 1505 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed by a QoE measurement configuration manager 725 as described with reference to FIG. 7.

At 1510, the method may include performing, by the UE operating in the DC mode, one or more QoE measurements based on the one or more parameters associated with the QoE measurement procedure. The operations of 1510 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed by a QoE measurement performing manager 730 as described with reference to FIG. 7.

At 1515, the method may include receiving an indication of a change associated with the DC mode. The operations of 1515 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed by a DC mode change indication reception manager 735 as described with reference to FIG. 7.

At 1520, the method may include receiving a second indication requesting the UE to transmit the one or more QoE measurements to the primary network entity via a radio bearer associated with the primary network entity. The operations of 1520 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1520 may be performed by a QoE measurement request manager 775 as described with reference to FIG. 7.

At 1525, the method may include performing a QoE reporting procedure associated with the one or more QoE measurements based on the change associated with the DC mode. The operations of 1525 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1525 may be performed by a QoE reporting procedure manager 740 as described with reference to FIG. 7.

At 1530, the method may include transmitting, to the primary network entity via the radio bearer associated with the primary network entity, a measurement report indicating the one or more QoE measurements based on the change associated with the DC mode, where the change associated with the DC mode includes one of a deactivation of a secondary connectivity associated with the secondary network entity, a release of the secondary connectivity, or a node switch associated with the secondary network entity. The operations of 1530 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1530 may be performed by a QoE measurement report transmission manager 745 as described with reference to FIG. 7.

FIG. 16 shows a flowchart illustrating a method 1600 that supports continuity measurement for DC scenarios in accordance with aspects of the present disclosure. The operations of the method 1600 may be implemented by a network entity or its components as described herein. For example, the operations of the method 1600 may be performed by a network entity as described with reference to FIGs. 1 through 4 and 9 through 12. In some examples, a network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally, or alternatively, the network entity may perform aspects of the described functions using special-purpose hardware.

At 1605, the method may include transmitting, to a UE operating in a DC mode associated with a primary network entity and a secondary network entity, one or more messages indicating one or more parameters associated with a QoE measurement procedure for the secondary network entity, where the one or more parameters instruct the UE to perform one or more QoE measurements. The operations of 1605 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed by a QoE measurement configuration component 1125 as described with reference to FIG. 11.

At 1610, the method may include transmitting, to the UE, an indication of a change associated with the DC mode. The operations of 1610 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed by a DC mode change indication transmission component 1130 as described with reference to FIG. 11.

FIG. 17 shows a flowchart illustrating a method 1700 that supports continuity measurement for DC scenarios in accordance with aspects of the present disclosure. The operations of the method 1700 may be implemented by a network entity or its components as described herein. For example, the operations of the method 1700 may be performed by a network entity as described with reference to FIGs. 1 through 4 and 9 through 12. In some examples, a network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally, or alternatively, the network entity may perform aspects of the described functions using special-purpose hardware.

At 1705, the method may include transmitting, to a UE operating in a DC mode associated with a primary network entity and a secondary network entity, one or more messages indicating one or more parameters associated with a QoE measurement procedure for the secondary network entity, where the one or more parameters instruct the UE to perform one or more QoE measurements. The operations of 1705 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed by a QoE measurement configuration component 1125 as described with reference to FIG. 11.

At 1710, the method may include transmitting, to the UE, an indication of a change associated with the DC mode. The operations of 1710 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed by a DC mode change indication transmission component 1130 as described with reference to FIG. 11.

At 1715, the method may include receiving, from the UE via a radio bearer associated with the primary network entity, a measurement report indicating the one or more of QoE measurements based on the change associated with the DC mode, where the change associated with the DC mode includes one of a deactivation of a secondary connectivity associated with the secondary network entity, a release of the secondary connectivity, or a node switch associated with the secondary network entity, and where the network entity is the primary network entity. The operations of 1715 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed by a QoE measurement report reception component 1135 as described with reference to FIG. 11.

FIG. 18 shows a flowchart illustrating a method 1800 that supports continuity measurement for DC scenarios in accordance with aspects of the present disclosure. The operations of the method 1800 may be implemented by a network entity or its components as described herein. For example, the operations of the method 1800 may be performed by a network entity as described with reference to FIGs. 1 through 4 and 9 through 12. In some examples, a network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally, or alternatively, the network entity may perform aspects of the described functions using special-purpose hardware.

At 1805, the method may include transmitting, to a UE operating in a DC mode associated with a primary network entity and a secondary network entity, one or more messages indicating one or more parameters associated with a QoE measurement procedure for the secondary network entity, where the one or more parameters instruct the UE to perform one or more QoE measurements. The operations of 1805 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1805 may be performed by a QoE measurement configuration component 1125 as described with reference to FIG. 11.

At 1810, the method may include transmitting, to the UE, an indication of a change associated with the DC mode. The operations of 1810 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed by a DC mode change indication transmission component 1130 as described with reference to FIG. 11.

At 1815, the method may include transmitting a second indication requesting for the UE to transmit the one or more QoE measurements to the primary network entity via a radio bearer associated with the primary network entity based on the change associated with the DC mode, where the change associated with the DC mode includes one of a deactivation of a secondary connectivity associated with the secondary network entity, a release of the secondary connectivity, or a node switch associated with the secondary network entity. The operations of 1815 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1815 may be performed by a QoE measurement report request component 1140 as described with reference to FIG. 11.

The following provides an overview of aspects of the present disclosure:

Aspect 1: A method for wireless communications by a UE, comprising: receiving, by the UE operating in a DC mode with a primary network entity and a secondary network entity, one or more messages indicating one or more parameters associated with a QoE measurement procedure for the secondary network entity; performing, by the UE operating in the DC mode, one or more QoE measurements based at least in part on the one or more parameters associated with the QoE measurement procedure; receiving an indication of a change associated with the DC mode; and performing a QoE reporting procedure associated with the one or more QoE measurements based at least in part on the change associated with the DC mode.

Aspect 2: The method of aspect 1, wherein performing the QoE reporting procedure comprises: transmitting, to the primary network entity via a radio bearer associated with the primary network entity, a measurement report indicating the one or more QoE measurements based at least in part on the change associated with the DC mode, wherein the change associated with the DC mode comprises one of a deactivation of a secondary connectivity associated with the secondary network entity, a release of the secondary connectivity, or a node switch associated with the secondary network entity.

Aspect 3: The method of aspect 2, further comprising: receiving a second indication requesting the UE to transmit the one or more QoE measurements to the primary network entity via the radio bearer associated with the primary network entity.

Aspect 4: The method of any of aspects 1 through 3, further comprising: transmitting, to the primary network entity, an availability message indicating an availability of the one or more QoE measurements associated with the QoE measurement procedure for the secondary network entity.

Aspect 5: The method of any of aspects 1 through 4, wherein the change associated with the DC mode comprises a deactivation of a secondary connectivity associated with the secondary network entity, the method further comprising: transmitting, to the secondary network entity via a radio bearer associated with the secondary network entity, a measurement report indicating the one or more QoE measurements based at least in part on reactivation of the secondary connectivity associated with the secondary network entity.

Aspect 6: The method of aspect 5, further comprising: receiving a third indication requesting for the UE to transmit the one or more QoE measurements to the secondary network entity via the radio bearer associated with the secondary network entity, wherein transmitting the measurement report to the secondary network entity via the radio bearer associated with the secondary network entity is based at least in part on receiving the third indication.

Aspect 7: The method of any of aspects 1 through 4, wherein the change associated with the DC mode comprises a deactivation of a secondary connectivity associated with the secondary network entity, and wherein performing the QoE reporting procedure comprises: discarding the one or more QoE measurements.

Aspect 8: The method of any of aspects 1 through 6, wherein the change associated with the DC mode comprises a deactivation of a secondary connectivity associated with the secondary network entity, and wherein performing the QoE reporting procedure comprises: suspending the QoE measurement procedure; and resuming the QoE measurement procedure based at least in part on a reactivation of the secondary connectivity.

Aspect 9: The method of any of aspects 1 through 4, wherein performing the QoE reporting procedure comprises: discarding the one or more parameters associated with the QoE measurement procedure, wherein the change associated with the DC mode comprises one of a release of a secondary connectivity associated with the secondary network entity or a node switch associated with the secondary network entity.

Aspect 10: The method of aspect 9, further comprising: receiving a fourth indication requesting for the UE to discard the one or more parameters, wherein discarding the one or more parameters is based at least in part on receiving the fourth indication.

Aspect 11: The method of any of aspects 1 through 8, wherein the change associated with the DC mode comprises a deactivation of a secondary connectivity associated with the secondary network entity.

Aspect 12: The method of any of aspects 1 through 4 or 9 through 10, wherein the change associated with the DC mode comprises a release of a secondary connectivity associated with the secondary network entity.

Aspect 13: The method of any of aspects 1 through 4 or 9 through 10, wherein the change associated with the DC mode comprises a switch from the secondary network entity to an additional secondary network entity.

Aspect 14: A method for wireless communications by a network entity, comprising: transmitting, to a UE operating in a DC mode associated with a primary network entity and a secondary network entity, one or more messages indicating one or more parameters associated with a QoE measurement procedure for the secondary network entity, wherein the one or more parameters instruct the UE to perform one or more QoE measurements; and transmitting, to the UE, an indication of a change associated with the DC mode.

Aspect 15: The method of aspect 14, further comprising: receiving, from the UE via a radio bearer associated with the primary network entity, a measurement report indicating the one or more of QoE measurements based at least in part on the change associated with the DC mode, wherein the change associated with the DC mode comprises one of a deactivation of a secondary connectivity associated with the secondary network entity, a release of the secondary connectivity, or a node switch associated with the secondary network entity, and wherein the network entity is the primary network entity.

Aspect 16: The method of any of aspects 14 through 15, further comprising: transmitting a second indication requesting for the UE to transmit the one or more QoE measurements to the primary network entity via a radio bearer associated with the primary network entity based at least in part on the change associated with the DC mode, wherein the change associated with the DC mode comprises one of a deactivation of a secondary connectivity associated with the secondary network entity, a release of the secondary connectivity, or a node switch associated with the secondary network entity.

Aspect 17: The method of any of aspects 14 through 16, further comprising: receiving, from the UE, an availability message indicating an availability of the one or more QoE measurements associated with the QoE measurement procedure for the secondary network entity.

Aspect 18: The method of any of aspects 14 through 17, wherein the change associated with the DC mode comprises a deactivation of a secondary connectivity associated with the secondary network entity.

Aspect 19: The method of aspect 18, further comprising: receiving, via a radio bearer associated with the secondary network entity, a measurement report indicating the one or more QoE measurements based at least in part on a reactivation of the secondary connectivity, wherein the network entity is the secondary network entity.

Aspect 20: The method of any of aspects 18 through 19, further comprising: transmitting, to the UE, a third indication requesting the UE to transmit the one or more QoE measurements to the secondary network entity based at least in part on a reactivation of the secondary connectivity.

Aspect 21: The method of any of aspects 14 through 17, wherein the change associated with the DC mode comprises a release of a secondary connectivity associated with the secondary network entity.

Aspect 22: The method of aspect 21, further comprising: transmitting, to the UE, a fourth indication requesting the UE to discard the one or more parameters.

Aspect 23: The method of any of aspects 21 through 22, further comprising: receiving, from the secondary network entity, an indication of the one or more parameters associated with the QoE measurement procedure, wherein the network entity is the primary network entity.

Aspect 24: The method of any of aspects 14 through 17, wherein the change associated with the DC mode comprises a node switch from the secondary network entity to an additional secondary network entity.

Aspect 25: The method of aspect 24, further comprising: transmitting, to the UE, a fourth indication requesting the UE to discard the one or more parameters.

Aspect 26: The method of any of aspects 24 through 25, further comprising: transmitting, to the additional secondary network entity, an indication of the one or more parameters, wherein the network entity is the primary network entity; and receiving, from the additional secondary network entity, an acknowledgment message based at least in part on transmitting the indication of the one or more parameters.

Aspect 27: The method of aspect 26, further comprising: receiving, from the secondary network entity, an indication of the one or more parameters for the UE to discard and one or more additional parameters for the UE to maintain.

Aspect 28: A UE for wireless communications, comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to perform a method of any of aspects 1 through 13.

Aspect 29: A UE for wireless communications, comprising at least one means for performing a method of any of aspects 1 through 13.

Aspect 30: A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by a processor to perform a method of any of aspects 1 through 13.

Aspect 31: A network entity for wireless communications, comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the network entity to perform a method of any of aspects 14 through 27.

Aspect 32: A network entity for wireless communications, comprising at least one means for performing a method of any of aspects 14 through 27.

Aspect 33: A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by a processor to perform a method of any of aspects 14 through 27.

It should be noted that the methods described herein describe possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more of the methods may be combined.

Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communications systems such as Ultra Mobile Broadband (UMB) , Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Flash-OFDM, as well as other systems and radio technologies not explicitly mentioned herein.

Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed using a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor but, in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration) . Any functions or operations described herein as being capable of being performed by a processor may be performed by multiple processors that, individually or collectively, are capable of performing the described functions or operations.

The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as or transmitted using one or more instructions or code of a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.

Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) , or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD) , floppy disk and Blu-ray disc. Disks may reproduce data magnetically, and discs may reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media. Any functions or operations described herein as being capable of being performed by a memory may be performed by multiple memories that, individually or collectively, are capable of performing the described functions or operations.

As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of” ) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) . Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. ”

As used herein, including in the claims, the article “a” before a noun is open-ended and understood to refer to “at least one” of those nouns or “one or more” of those nouns. Thus, the terms “a, ” “at least one, ” “one or more, ” “at least one of one or more” may be interchangeable. For example, if a claim recites “a component” that performs one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “a component” having characteristics or performing functions may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent reference to a component introduced with the article “a” using the terms “the” or “said” may refer to any or all of the one or more components. For example, a component introduced with the article “a” may be understood to mean “one or more components, ” and referring to “the component” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components. ” Similarly, subsequent reference to a component introduced as “one or more components” using the terms “the” or “said” may refer to any or all of the one or more components. For example, referring to “the one or more components” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components. ”

The term “determine” or “determining” encompasses a variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database or another data structure) , ascertaining and the like. Also, “determining” can include receiving (e.g., receiving information) , accessing (e.g., accessing data stored in memory) and the like. Also, “determining” can include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If just the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label, or other subsequent reference label.

The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration, ” and not “preferred” or “advantageous over other examples. ” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

A user equipment (UE) , comprising:

one or more memories storing processor-executable code; and

one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to:

receive, by the UE operating in a dual connectivity mode with a primary network entity and a secondary network entity, one or more messages indicating one or more parameters associated with a quality of experience measurement procedure for the secondary network entity;

perform, by the UE operating in the dual connectivity mode, one or more quality of experience measurements based at least in part on the one or more parameters associated with the quality of experience measurement procedure;

receive an indication of a change associated with the dual connectivity mode; and

perform a quality of experience reporting procedure associated with the one or more quality of experience measurements based at least in part on the change associated with the dual connectivity mode.
The UE of claim 1, wherein, to perform the quality of experience reporting procedure, the one or more processors are individually or collectively operable to execute the code to cause the UE to:

transmit, to the primary network entity via a radio bearer associated with the primary network entity, a measurement report indicating the one or more quality of experience measurements based at least in part on the change associated with the dual connectivity mode, wherein the change associated with the dual connectivity mode comprises one of a deactivation of a secondary connectivity associated with the secondary network entity, a release of the secondary connectivity, or a node switch associated with the secondary network entity.
The UE of claim 2, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:

receive a second indication requesting the UE to transmit the one or more quality of experience measurements to the primary network entity via the radio bearer associated with the primary network entity.
The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:

transmit, to the primary network entity, an availability message indicating an availability of the one or more quality of experience measurements associated with the quality of experience measurement procedure for the secondary network entity.
The UE of claim 1, wherein the change associated with the dual connectivity mode comprises a deactivation of a secondary connectivity associated with the secondary network entity, and wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:

transmit, to the secondary network entity via a radio bearer associated with the secondary network entity, a measurement report indicating the one or more quality of experience measurements based at least in part on reactivation of the secondary connectivity associated with the secondary network entity.
The UE of claim 5, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:

receive a third indication requesting for the UE to transmit the one or more quality of experience measurements to the secondary network entity via the radio bearer associated with the secondary network entity, wherein transmitting the measurement report to the secondary network entity via the radio bearer associated with the secondary network entity is based at least in part on the third indication.
The UE of claim 1, wherein, to perform the quality of experience reporting procedure, the one or more processors are individually or collectively operable to execute the code to cause the UE to:

discard the one or more quality of experience measurements.
The UE of claim 1, wherein, to perform the quality of experience reporting procedure, the one or more processors are individually or collectively operable to execute the code to cause the UE to:

suspend the quality of experience measurement procedure; and

resume the quality of experience measurement procedure based at least in part on a reactivation of the secondary connectivity.
The UE of claim 1, wherein, to perform the quality of experience reporting procedure, the one or more processors are individually or collectively operable to execute the code to cause the UE to:

discard the one or more parameters associated with the quality of experience measurement procedure, wherein the change associated with the dual connectivity mode comprises one of a release of a secondary connectivity associated with the secondary network entity or a node switch associated with the secondary network entity.
The UE of claim 9, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:

receive a fourth indication requesting for the UE to discard the one or more parameters, wherein discarding the one or more parameters is based at least in part on the fourth indication.
The UE of claim 1, wherein the change associated with the dual connectivity mode comprises a deactivation of a secondary connectivity associated with the secondary network entity.
The UE of claim 1, wherein the change associated with the dual connectivity mode comprises a release of a secondary connectivity associated with the secondary network entity.
The UE of claim 1, wherein the change associated with the dual connectivity mode comprises a switch from the secondary network entity to an additional secondary network entity.
A network entity, comprising:

one or more memories storing processor-executable code; and

one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the network entity to:

transmit, to a user equipment (UE) operating in a dual connectivity mode associated with a primary network entity and a secondary network entity, one or more messages indicating one or more parameters associated with a quality of experience measurement procedure for the secondary network entity, wherein the one or more parameters instruct the UE to perform one or more quality of experience measurements; and

transmit, to the UE, an indication of a change associated with the dual connectivity mode.
The network entity of claim 14, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to:

receive, from the UE via a radio bearer associated with the primary network entity, a measurement report indicating the one or more quality of experience measurements based at least in part on the change associated with the dual connectivity mode, wherein the change associated with the dual connectivity mode comprises one of a deactivation of a secondary connectivity associated with the secondary network entity, a release of the secondary connectivity, or a node switch associated with the secondary network entity, and wherein the network entity is the primary network entity.
The network entity of claim 14, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to:

transmit a second indication requesting for the UE to transmit the one or more quality of experience measurements to the primary network entity via a radio bearer associated with the primary network entity based at least in part on the change associated with the dual connectivity mode, wherein the change associated with the dual connectivity mode comprises one of a deactivation of a secondary connectivity associated with the secondary network entity, a release of the secondary connectivity, or a node switch associated with the secondary network entity.
The network entity of claim 14, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to:

receive, from the UE, an availability message indicating an availability of the one or more quality of experience measurements associated with the quality of experience measurement procedure for the secondary network entity.
The network entity of claim 14, wherein the change associated with the dual connectivity mode comprises a deactivation of a secondary connectivity associated with the secondary network entity.
The network entity of claim 18, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to:

receive, via a radio bearer associated with the secondary network entity, a measurement report indicating the one or more quality of experience measurements based at least in part on a reactivation of the secondary connectivity, wherein the network entity is the secondary network entity.
The network entity of claim 18, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to:

transmit, to the UE, a third indication requesting the UE to transmit the one or more quality of experience measurements to the secondary network entity based at least in part on a reactivation of the secondary connectivity.
The network entity of claim 14, wherein the change associated with the dual connectivity mode comprises a release of a secondary connectivity associated with the secondary network entity.
The network entity of claim 21, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to:

transmit, to the UE, a fourth indication requesting the UE to discard the one or more parameters.
The network entity of claim 21, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to:

receive, from the secondary network entity, an indication of the one or more parameters associated with the quality of experience measurement procedure, wherein the network entity is the primary network entity.
The network entity of claim 14, wherein the change associated with the dual connectivity mode comprises a node switch from the secondary network entity to an additional secondary network entity.
The network entity of claim 24, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to:

transmit, to the UE, a fourth indication requesting the UE to discard the one or more parameters.
The network entity of claim 24, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to:

transmit, to the additional secondary network entity, an indication of the one or more parameters, wherein the network entity is the primary network entity; and

receive, from the additional secondary network entity, an acknowledgment message based at least in part on the indication of the one or more parameters.
The network entity of claim 26, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to:

receive, from the secondary network entity, an indication of the one or more parameters for the UE to discard and one or more additional parameters for the UE to maintain.
A method for wireless communications by a user equipment (UE) , comprising:

receiving, by the UE operating in a dual connectivity mode with a primary network entity and a secondary network entity, one or more messages indicating one or more parameters associated with a quality of experience measurement procedure for the secondary network entity;

performing, by the UE operating in the dual connectivity mode, one or more quality of experience measurements based at least in part on the one or more parameters associated with the quality of experience measurement procedure;

receiving an indication of a change associated with the dual connectivity mode; and

performing a quality of experience reporting procedure associated with the one or more quality of experience measurements based at least in part on the change associated with the dual connectivity mode.
The method of claim 28, wherein performing the quality of experience reporting procedure comprises:

transmitting, to the primary network entity via a radio bearer associated with the primary network entity, a measurement report indicating the one or more quality of experience measurements based at least in part on the change associated with the dual connectivity mode, wherein the change associated with the dual connectivity mode comprises one of a deactivation of a secondary connectivity associated with the secondary network entity, a release of the secondary connectivity, or a node switch associated with the secondary network entity.
A method for wireless communications by a network entity, comprising:

transmitting, to a user equipment (UE) operating in a dual connectivity mode associated with a primary network entity and a secondary network entity, one or more messages indicating one or more parameters associated with a quality of experience measurement procedure for the secondary network entity, wherein the one or more parameters instruct the UE to perform one or more quality of experience measurements; and

transmitting, to the UE, an indication of a change associated with the dual connectivity mode.