Method and apparatus for supporting quality of experience (QoE) measurement collection

Abstract

[0003] Embodiments of the present application relate to a method and apparatus for supporting Quality of Experience (QoE) measurement collection. An exemplary method may include receiving first QoE configuration information from a first RAN node, receiving second QoE configuration information from a second RAN node, and sending overlap indication information to at least one of the first RAN node or the second RAN node in response to the first QoE configuration information and the second QoE configuration information being associated with the same QoE measurement, the overlap indication information indicating that at least one of the first QoE configuration information or the second QoE configuration information is to be ignored due to the overlap between the first and second QoE configuration information.

Description

[Technical Field]

[0001] TECHNICAL FIELD Embodiments of the present application generally relate to wireless communication technologies, and more particularly, to methods and apparatus for supporting quality of experience (QoE) measurement collection. [Background technology]

[0002] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts, and so on. Wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of wireless communication systems may 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, sometimes referred to as New Radio (NR) systems.

[0003] 3GPP Release (Rel)-17 specifies the basic mechanisms for NR QoE. Because NR dual connectivity (DC) is an important commercial deployment scenario for 5G networks, it is important to support NR-DC within the NR QoE framework. Therefore, QoE in Rel-18 supports QoE measurement configuration and measurement reporting for NR-DC scenarios as agreed below in RP-213159. - Specifying QoE configuration and measurement reporting via MN / SN for NR-DC architecture and QoE measurement reporting via other DC legs to maintain reporting continuity.

[0004] However, in some scenarios, for example, in management-based QoE measurement in NR-DC, both the master node (MN) and secondary node (SN) may receive QoE measurement configurations from the operation administration and maintenance (OAM) system. If there is no coordination between the MN and the SN, some problems may arise. For example, the application layer of a user equipment (UE) may receive two identical application layer measurement configurations with different measConfigAppLayerIds for QoE measurements configured by the MN and SN, respectively, which may cause QoE measurement failures in the application layer of the UE.

[0005] Given the above, the industry desires to improve techniques for improving QoE measurement collection, and in particular techniques that support QoE measurements for NR-DC. Summary of the Invention [Problem to be solved by the invention]

[0006] One objective of embodiments of the present application is to provide a technical solution that supports QoE measurement collection, for example, a method and apparatus that supports QoE measurement collection for NR-DC by coordinating MN and SN. [Means for solving the problem]

[0007] Some embodiments of the present application provide a UE, the UE including: a transceiver; and a processor coupled to the transceiver. The processor is configured to receive first QoE configuration information from a first Radio Access Network (RAN) node; receive second QoE configuration information from a second RAN node; and, in response to the first QoE configuration information and the second QoE configuration information being associated with the same QoE measurement, send overlap indication information to at least one of the first RAN node or the second RAN node. The overlap indication information indicates that at least one of the first QoE configuration information or the second QoE configuration information is to be ignored due to the overlap of the first QoE configuration information and the second QoE configuration information for the QoE measurement.

[0008] In some embodiments of the present application, the first QoE configuration information and the second QoE configuration information are received from the MN and the SN, respectively, by a radio resource control (RRC) layer of the UE. According to some embodiments of the present application, the first QoE configuration information and the second QoE configuration information are sent by the RRC layer to an application layer of the UE, and the application layer determines whether the first QoE configuration information and the second QoE configuration information are overlapping and which QoE configuration information to ignore.

[0009] In some embodiments of the present application, the overlap indication information indicates that only one of the overlapping first QoE configuration information and the second QoE configuration information is ignored by using an RRC identifier of the QoE configuration information to be ignored. According to some embodiments of the present application, the overlap indication information further indicates an RRC identifier of the other of the first QoE configuration information and the second QoE configuration information.

[0010] In some embodiments of the present application, the overlap indication information indicates that both the overlapping first QoE configuration information and the overlapping second QoE configuration information are ignored using an RRC identifier of each ignored QoE configuration information.

[0011] In some embodiments of the present application, the duplicate indication information is transmitted to at least one of the first RAN node or the second RAN node associated with the QoE configuration information to be ignored, or is transmitted to only one of the first RAN node and the second RAN node as the MN, respectively.

[0012] In some embodiments of the present application, the first QoE configuration information indicates an MN index and a measConfigAppLayerId, and the second QoE configuration information indicates an SN index and a measConfigAppLayerId.

[0013] In some embodiments of the present application, if either the first QoE configuration information or the second QoE configuration information indicates the information as an RRC identifier for an SN, the corresponding QoE measurement information is configured by the SN.

[0014] In some embodiments of the present application, if RVQoE measurement configuration information is also received, the RRC layer of the UE selects at least one leg of the MN and SN for reporting the RVQoE measurement result.

[0015] According to some embodiments of the present application, an RRC layer receives RVQoE measurement results and identification information of at least one of a data radio bearer (DRB), a quality of service (QoS) flow, or a protocol data unit (PDU) session from an application layer of a UE. The RRC layer selects at least one leg for reporting the RVQoE measurement results based on a bearer type, and if at least one of the DRB, the QoS flow, or the PDU session is served by only one of a master cell group (MCG) and a secondary cell group (SCG), the RRC layer reports the RVQoE measurement results to only the corresponding one of the MN and the SN. If at least one of the DRB, the QoS flow, or the PDU session is served by both the MCG and the SCG, the RRC layer reports the RVQoE measurement results to both the MN and the SN.

[0016] According to some embodiments of the present application, the RRC layer selects at least one leg for reporting the RVQoE measurement results based on reporting leg configuration information.

[0017] In some embodiments of the present application, the processor is configured to receive RVQoE measurement configuration information, where the RVQoE configuration information indicates a measConfigAppLayerId and one of an MN index and an SN index.

[0018] Some other embodiments of the present application provide a RAN node, e.g., a MN or SN, including a transceiver and a processor coupled to the transceiver, wherein the processor is configured to receive information indicative of at least one QoE measurement and determine information related to configuration of the at least one QoE measurement, where the information related to configuration of the at least one QoE measurement includes at least one of first information related to whether the same QoE measurement is configured in the UE by the MN or SN, second information related to an RRC identifier for the QoE measurement, or third information related to an RRC identifier for the RVQoE measurement.

[0019] In some embodiments of the present application, the RAN node is an MN and the peer node is an SN, and the processor is configured to receive QoE configuration request information from the SN to request whether QoE measurement is allowed, and to send first information to the SN in response to the QoE configuration request information, the first information being QoE configuration allowance indication information indicating that QoE measurement is allowed or QoE configuration rejection indication information indicating that QoE measurement is rejected. In some other embodiments of the present application, the RAN node is an SN and the peer node is an MN, and the processor is configured to send QoE configuration request information to the MN to request whether QoE measurement is allowed, and to receive first information from the MN, the first information being QoE configuration allowance indication information indicating that QoE measurement is allowed or QoE configuration rejection indication information indicating that QoE measurement is rejected.

[0020] According to some embodiments of the present application, the RRC identifier of the QoE measurement configuration is allocated by the MN and sent to the SN together with the QoE configuration allowance indication information, or allocated by the SN and sent to the MN together with the QoE configuration request information. In some scenarios, the RRC identifier of the QoE measurement configuration is determined as the third information to be used by the MN and the SN for the corresponding RVQoE measurement.

[0021] According to some embodiments of the present application, the QoE configuration rejection indication information indicates an RRC identifier of the corresponding configuration information of the QoE measurement allocated by the MN. In some scenarios, the RRC identifier is determined as the third information to be used by the SN for the corresponding RVQoE measurement.

[0022] According to some embodiments of the present application, the QoE configuration rejection indication information indicates a cause value to indicate why the QoE configuration is rejected.

[0023] According to some embodiments of the present application, the QoE configuration request information includes at least one of a QoE reference, an area range, or a service type of the QoE measurement.

[0024] In some embodiments of the present application, the processor is configured to transmit first information to the peer node, the first information being QoE measurement configuration indication information indicating that QoE measurements have been configured or will be configured in the UE by the RAN node. In some other embodiments of the present application, the processor is configured to receive first information from the peer node, the first information being QoE measurement configuration indication information indicating that QoE measurements have been configured or will be configured in the UE by the RAN node.

[0025] According to some embodiments of the present application, the QoE measurement configuration indication information indicates an RRC identifier of a corresponding QoE configuration of the QoE measurement allocated by the MN. In some scenarios, the RRC identifier is determined as the third information to be used by the RAN node and the peer node for the corresponding RV QoE measurement.

[0026] In some embodiments of the present application, the processor is configured to: send a QoE configuration accept request to the peer node for accepting QoE measurements configured by the peer node; and receive first information from the peer node, the first information being QoE configuration add indication information indicating QoE measurements configured in the UE or QoE configuration release indication information indicating released QoE measurements to the UE. In some other embodiments of the present application, the processor is configured to receive a QoE configuration accept request from the peer node for accepting QoE measurements configured by the peer node; and send first information to the peer node, the first information being QoE configuration add indication information responsive to configuring QoE measurements in the UE or QoE configuration release indication information responsive to releasing QoE measurements configured in the UE.

[0027] According to some embodiments of the present application, if the QoE configuration acceptance request indicates at least one QoE reference, then only the addition or release of QoE measurements related to said at least one QoE reference is reported, and if no QoE reference is indicated in the QoE configuration acceptance request, then the addition or release of any QoE measurement is reported.

[0028] In some embodiments of the present application, the RAN node is an MN and the peer node is an SN, and the processor is configured to transmit second information to the SN, the second information indicating an RRC identifier value range for QoE measurements to be used by the SN. In some scenarios, the second information indicating an RRC identifier value range for QoE measurements to be used by the SN is transmitted in response to a request from the SN. In some other embodiments of the present application, the RAN node is an SN and the peer node is an MN, and the processor is configured to receive second information from the MN, the second information indicating an RRC identifier value range for QoE measurements to be used by the SN. In some scenarios, the processor is configured to transmit a request to the MN requesting the RRC identifier value range.

[0029] According to some embodiments of the present application, the RRC identifier value range is determined by the SN as third information to be used by the SN for RVQoE measurement.

[0030] In some embodiments of the present application, the RAN node is an MN and the peer node is an SN, and the processor is configured to receive a request from the SN requesting an RRC identifier for QoE measurement and to send second information to the SN, where the second information indicates an RRC identifier for QoE measurement. In some other embodiments of the present application, the RAN node is an SN and the peer node is an MN, and the processor is configured to send a request to the MN requesting an RRC identifier for QoE measurement and to receive second information from the MN, where the second information indicates an RRC identifier for QoE measurement.

[0031] According to some embodiments of the present application, the request includes at least one of a QoE reference or a service type of the QoE measurement.

[0032] According to some embodiments of the present application, the RRC identifier is determined by the SN as third information to be used by the SN for corresponding RVQoE measurements.

[0033] In some embodiments of the present application, the processor is configured to send second information to the UE, where if the RAN node is an MN, the second information indicates a measConfigAppLayerId and an MN index for QoE measurements configured in the UE by the MN, and if the RAN node is an SN, the second information indicates a measConfigAppLayerId and an SN index for QoE measurements configured in the UE by the SN.

[0034] In some embodiments of the present application, the RAN node is a MN and the peer node is a SN, and the processor is configured to send third information to the SN, where the third information indicates an RRC identifier value range for RVQoE measurements to be used by the SN.

[0035] According to some embodiments of the present application, the third information indicating the RRC identifier value range for RVQoE measurements used by the SN is transmitted in response to a request from the SN.

[0036] In some embodiments of the present application, the RAN node is an SN and the peer node is an MN, and the processor is configured to receive third information from the MN, the third information indicating an RRC identifier value range for RVQoE measurements to be used by the SN.

[0037] According to some embodiments of the present application, the processor is configured to send a request to request an RRC identifier value range for RVQoE measurements to be used by the SN.

[0038] In some embodiments of the present application, the RAN node is an MN and the peer node is an SN, and the processor is configured to receive a request from the SN requesting an RRC identifier for the RVQoE measurement and to send third information to the SN, where the third information indicates an RRC identifier for the RVQoE measurement. In some other embodiments of the present application, the RAN node is an SN and the peer node is an MN, and the processor is configured to send a request to the MN requesting an RRC identifier for the RVQoE measurement and to receive third information from the MN, where the third information indicates an RRC identifier for the RVQoE measurement.

[0039] According to some embodiments of the present application, the RRC identifier for RVQoE measurements is used by the SN only or is shared by both the SN and the MN.

[0040] In some embodiments of the present application, the processor is configured to send third information to the UE, where if the RAN node is an MN, the third information indicates a measConfigAppLayerId and an MN index for RVQoE measurements configured in the UE by the MN, and if the RAN node is an SN, the third information indicates a measConfigAppLayerId and an SN index for RVQoE measurements configured in the UE by the SN.

[0041] In some embodiments of the present application, when overlap indication information is received from the UE indicating that QoE configuration information from the RAN node is to be ignored due to overlap with other QoE configuration information for the same QoE measurement, the processor is configured to determine an RRC identifier of the other QoE configuration information received together with the overlap indication information as third information to be used by the RAN node for the corresponding RVQoE measurement.

[0042] Some further embodiments of the present application provide a method, performed, for example, by a UE, for supporting QoE measurement collection, the method including: receiving first QoE configuration information from a first RAN node; receiving second QoE configuration information from a second RAN node; and sending overlap indication information to at least one of the first RAN node or the second RAN node in response to the first QoE configuration information and the second QoE configuration information being associated with the same QoE measurement, the overlap indication information indicating that at least one of the first QoE configuration information or the second QoE configuration information is to be ignored due to the overlap of the first QoE configuration information and the second QoE configuration information for the QoE measurement.

[0043] Some still other embodiments of the present application provide a method for supporting QoE measurement collection, which may be performed in a RAN node, e.g., an MN or an SN, comprising: receiving information indicative of at least one QoE measurement; and determining information related to configuration of the at least one QoE measurement, wherein the information related to configuration of the at least one QoE measurement comprises at least one of first information related to whether the same QoE measurement is configured in the UE by the MN or the SN, second information related to an RRC identifier for the QoE measurement, or third information related to an RRC identifier for the RVQoE measurement.

[0044] Given the above, embodiments of the present application provide methods and apparatuses that support QoE measurement collection, which can coordinate QoE measurements (including RVQoE measurements in some scenarios) by MN and SN in NR-DC scenarios. Thus, the present application can facilitate and improve the implementation of NR.

[0045] To explain the manner in which the advantages and features of the present application may be obtained, the present application will be described with reference to specific embodiments thereof that are illustrated in the accompanying drawings. These drawings depict only exemplary embodiments of the present application and therefore should not be considered limiting of its scope. [Brief explanation of the drawings]

[0046] [Figure 1] 1 illustrates a wireless communication system according to some embodiments of the present application. [Figure 2] 1 is a flowchart of a procedure for QoE measurement collection in Scenario 1 according to some embodiments of the present application. [Figure 3] 10 is a flowchart of a procedure for QoE measurement collection in scenario 2 according to some embodiments of the present application. [Figure 4] 10 is a flowchart of a procedure for QoE measurement collection in Scenario 3 according to some embodiments of the present application. [Figure 5] 10 is a flowchart of a procedure for QoE measurement collection in scenario 4 according to some embodiments of the present application. [Figure 6] 1 is a block diagram of an apparatus supporting QoE measurement collection according to some embodiments of the present application. [Figure 7] FIG. 10 is a block diagram of an apparatus supporting QoE measurement reporting according to some other embodiments of the present application. DETAILED DESCRIPTION OF THE INVENTION

[0047] The detailed description of the accompanying drawings is intended as an illustration of a preferred embodiment of the present application and is not intended to represent the only form in which the present application may be practiced. It is to be understood that the same or equivalent functions may be accomplished by various embodiments that are intended to be encompassed within the spirit and scope of the present application.

[0048] Reference will now be made in detail to several embodiments of the present application, examples of which are illustrated in the accompanying drawings. For ease of understanding, the embodiments are provided under specific network architectures and new service scenarios, such as 3GPP 5G and 3GPP LTE. It is contemplated that all embodiments in the present application are also applicable to similar technical problems, along with the development of network architectures and new service scenarios. Furthermore, the terms used in the present application may change, but this should not affect the principles of the present application.

[0049] In an NR-DC scenario, a UE with multiple transceivers may be configured to utilize resources provided by two different nodes connected via a non-ideal backhaul, where one node may provide NR access and another node may provide either Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA) (E-UTRA) or NR access. One node may act as the MN and the other node may act as the SN. The MN and SN are connected via a network interface, e.g., an Xn interface as specified in 3GPP standard documents, and at least the MN is connected to a core network (CN).

[0050] For example, FIG. 1 illustrates a schematic diagram of a wireless communication system 100 in accordance with some embodiments of the present application.

[0051] As shown in Figure 1, the wireless communication system 100 may be a dual connectivity system 100 that includes at least one UE 101, at least one MN 102, and at least one SN 103. In particular, the dual connectivity system 100 of Figure 1 includes, for purposes of explanation, what is designated as a UE 101, what is designated as a MN 102, and what is designated as an SN 103. Although a particular number of UEs 101, MNs 102, and SNs 103 are shown in Figure 1, it is contemplated that any number of UEs 101, MNs 102, and SNs 103 may be included in the wireless communication system 100.

[0052] 1, the UE 101 may be connected to the MN 102 and the SN 103 via an interface, for example, a Uu interface as specified in the 3GPP standard documents. The MN 102 and the SN 103 may be connected to each other via a network interface, for example, an Xn interface as specified in the 3GPP standard documents. The MN 102 may be connected to a core network via a network interface (not shown in FIG. 1), for example, an NG interface as specified in the 3GPP standard documents. The UE 101 may be configured to utilize resources provided by the MN 102 and the SN 103 to perform data transmission.

[0053] In some embodiments of the present application, the UE 101 may include a computing device such as a desktop computer, a laptop computer, a personal digital assistant (PDA), a tablet computer, a smart television (e.g., a television connected to the Internet), a set-top box, a game console, a security system (including security cameras), an in-vehicle computer, a network device (e.g., a router, a switch, and a modem), etc. In some other embodiments of the present application, the UE 101 may include a portable wireless communication device, a smartphone, a cellular telephone, a flip phone, a device with a subscriber identity module, a personal computer, selective call receiving circuitry, or any other device capable of sending and receiving communication signals over a wireless network. In some other embodiments of the present application, the UE 101 may include a wearable device such as a smart watch, a fitness band, an optical head-mounted display, etc. Moreover, the UE 101 may be referred to as a subscriber unit, a mobile, a mobile station, a user, a terminal, a mobile terminal, a wireless terminal, a fixed terminal, a subscriber station, a user terminal, or a device, or may be referred to using other terms used in the art.

[0054] The MN 102 refers to a Radio Access Network (RAN) node that provides a control plane connection to a core network. In one embodiment of the present application, in an E-UTRA-NR DC (EN-DC) scenario, the MN 102 may be an eNB. In another embodiment of the present application, in a Next Generation E-UTRA-NR DC (NGEN-DC) scenario, the MN 102 may be a Next Generation (ng)-eNB. In yet another embodiment of the present application, in an NR-DC scenario or an NR-E-UTRA DC (NE-DC) scenario, the MN 102 may be a gNB. The MN 102 may also be referred to as a master-NG-RAN (M-NG-RAN) node in some embodiments of the present application.

[0055] The MN leg may be referred to as an MCG. The MCG may refer to a group of serving cells associated with the MN 102 and may include a primary cell (PCell) and optionally one or more secondary cells (SCells). The PCell may provide control plane connectivity to the UE 101.

[0056] The SN 103 may refer to a radio access network node that does not have a control plane connection to a core network but provides additional resources to the UE 101. In some embodiments of the present application, in an EN-DC scenario, the SN 103 may be an en-gNB. In some other embodiments of the present application, in an NR-DC scenario, the SN 103 may be an ng-eNB. In yet another embodiment of the present application, in an NR-DC scenario or an NGEN-DC scenario, the SN 103 may be a gNB. The SN 103 may also be referred to as a secondary-NG-RAN (S-NG-RAN) node in some embodiments of the present application.

[0057] The SN leg may be referred to as an SCG, which may refer to a group of serving cells associated with the SN, and may include a primary secondary cell (PSCell) and optionally one or more SCells.

[0058] The PCell of the MCG and the PSCell of the SCG are sometimes called special cells (SpCells).

[0059] Additionally, with regard to QoE Measurement Collection (QMC, also referred to as "QoE Measurement") activation and reporting, TS38.300 specifies the following: "The capability is activated in the NG-RAN either by direct configuration from the OAM system (management-based activation) or by signaling from the OAM via the core network (signaling-based activation), including UE-related QoE configuration. One or more QoE measurement collection jobs can be activated in the UE per service type, and each QoE measurement configuration is uniquely identified by a QoE reference." For signaling-based QoE measurement, the OAM initiates QoE measurement activation for a specific UE via the core network, and the NG-RAN node receives one or more QoE measurement configurations via UE-related signaling. The QoE measurement configuration for signaling-based activation includes an application layer measurement configuration list and corresponding information for QoE measurement collection, such as QoE reference, service type, MCE IP address, slice range, area range, MDT alignment information, and an indication of available RAN-visible QoE metrics. Each application layer measurement configuration is encapsulated in a transparent container. The NG-RAN node forwards the corresponding QoE measurement configuration to the UE in a downlink RRC message containing AppLayerMeasConfig, as specified in TS38.331

[12] . For management-based QoE measurement activation, the OAM sends one or more QoE measurement configurations to the NG-RAN node. The QoE measurement configuration for management-based activation also includes an application layer measurement configuration list and corresponding information for QoE measurement collection. Each application layer measurement configuration is encapsulated in a transparent container. The NG-RAN node selects UEs that meet the required QoE measurement capabilities, area range, and slice range. The UE reports the QoE measurement results to the NG-RAN node in an uplink RRC message as specified in TS38.331

[12] . The NG-RAN node sends the QoE report and the corresponding QoE Reference ID to the MCE. QoE measurement collection is handled by application layer measurement configurations and measurement reports, which are only supported in the RRC_CONNECTED state. Application layer measurement configurations received by the gNB from OAM or CN are encapsulated in transparent containers, which are forwarded to the UE as application layer configurations in RRCReconfiguration messages (multiple configurations can exist in the same message). Application layer measurement reports received from higher layers in the UE are encapsulated in transparent containers and sent to the network in MeasurementReportAppLayer messages as specified in TS38.331

[12] . The UE can send multiple application layer measurement reports to the gNB in ​​one MeasurementReportAppLayer message. Segmentation of the MeasurementReportAppLayer message may be enabled by the gNB to enable the transmission of application layer measurement reports that exceed the maximum PDCP SDU size. The measConfigAppLayerId carried in RRC signaling is used to identify application layer measurement configurations and reports between the gNB and the UE. The RRC identifier is mapped to the QoE reference within the gNB. The application layer measurement report is forwarded together with the QoE reference to the OAM. The gNB can release one or more application layer measurement configurations from the UE within one RRCReconfiguration message at any time. The UE may additionally be configured by the gNB to report when a QoE measurement session starts or stops for some application layer measurement configurations.

[0060] Therefore, QoE measurement collection in the NG-RAN can be activated by two methods: management-based activation and signaling-based activation. In the case of management-based activation, the RAN node, e.g., gNB, receives a direct configuration from the OAM (or OAM system). In the case of signaling-based activation, the RAN node receives signaling containing UE-related QoE configuration from the OAM via the CN. The application layer measurement configuration received by the gNB from the OAM or CN is encapsulated in a transparent container in Rel-17, which is forwarded to the UE as an application layer configuration in an RRCReconfiguration message (there can be multiple configurations in the same message). The application layer measurement report received from the UE's application layer is encapsulated in a transparent container and sent to the network in a MeasurementReportAppLayer message. To enable the transmission of application layer measurement reports that exceed the maximum PDCP SDU size, segmentation of the MeasurementReportAppLayer message may be enabled by the gNB.

[0061] According to RP-213159, support for QoE measurement configuration and measurement reporting via MN / SN for NR-DC scenarios will be finalized in Rel-18, and therefore a number of issues need to be resolved. Taking management-based QoE measurement as an example, since both MN and SN may receive QoE measurement configuration from OAM, several issues may arise if there is no coordination between MN and SN.

[0062] In an exemplary scenario, because the OAM does not know whether NR-DC is configured for the UE, the OAM may provide the same QoE measurement configuration to both the MN and the SN separately. In the absence of coordination between the MN and the SN, both the MN and the SN may provide QoE measurements with different allocated measConfigAppLayerIds to the same UE (Problem 1). Therefore, the application layer of the UE may receive two identical application layer measurement configurations with different measConfigAppLayerIds from the MN and the SN, respectively, which may cause QoE measurement failures within the application layer of the UE. Even if the measConfigAppLayerIds allocated by the MN and the SN are the same for the same QoE measurement, there is a problem due to two duplicated QoE measurements.

[0063] In another exemplary scenario, the OAM provides different QoE measurement configurations to both the MN and the SN separately, but the MN and the SN may each allocate the same measConfigAppLayerId for different QoE measurements to the same UE due to a lack of coordination between the MN and the SN (Problem 2). Thus, the RRC layer of the UE may receive two QoE measurements with the same measConfigAppLayerId and forward them to the application layer of the UE. However, the application layer of the UE is uncertain how to handle the two application measurement configurations, for example, whether the first received application measurement configuration with the measConfigAppLayerId should be replaced by a later application measurement configuration with the same measConfigAppLayerId.

[0064] In addition, if RVQoE measurements, whose measurement results are visible to the RAN node, are taken into consideration, how to coordinate RVQoE configuration and reporting between the MN and the SN should also be resolved (Problem 3). Regarding RVQoE measurements (or RVQoE configuration), RVQoE measurements are configured by the gNB, where a subset of QoE metrics is reported from the UE as an explicit IE readable by the gNB. RVQoE measurements can be utilized by the gNB for network optimization. Each RVQoE measurement configuration and report is identified by the same RRC identifier as the application layer measurement configuration and measurement report (normal QoE measurement). RVQoE measurements can be reported with a reporting periodicity different from that of normal QoE measurements. If there is no reporting periodicity specified in the RAN visible QoE configuration, RAN visible QoE reports are sent together with normal QoE reports. Without coordination between the MN and the SN, the MN or SN may not know the RRC identifier for normal QoE measurements for the RVQoE configuration if the RRC identifier for normal QoE measurements has already been allocated by the peer node.

[0065] In order to solve at least the above problems in QoE measurement, the embodiments of the present application provide technical solutions that support QoE measurement collection (even when RVQoE measurement is configured), for example, methods and apparatuses that support QoE measurement collection taking into account the coordination between MN and SN.

[0066] For example, some embodiments of the present application provide a method for supporting QoE measurement collection, which may be performed by a UE or the like. The method includes receiving first QoE configuration information from a first RAN node (e.g., an MN), for example, by an RRC layer of the UE, receiving second QoE configuration information from a second RAN node (e.g., an SN), for example, by an RRC layer of the UE, and transmitting overlap indication information to at least one of the first RAN node or the second RAN node in response to the first QoE configuration information and the second QoE configuration information being associated with the same QoE measurement (e.g., the application layer measurement configurations of the two QoE configuration information are the same). The exemplary overlap indication information indicates that one of the first and second QoE configuration information is ignored (or rejected or erased) due to the first and second QoE configuration information being overlapping for the QoE measurement, and indicates an RRC identifier of the ignored QoE configuration information. Another exemplary overlap indication information indicates that both the first and second QoE configuration information are ignored (or rejected or erased) due to being overlapping for QoE measurement, and indicates the RRC identifier of each ignored QoE configuration information.

[0067] Some other embodiments of the present application provide another method for supporting QoE measurement collection, which may be performed in a RAN node, such as an MN or an SN. The method includes receiving information indicative of at least one QoE measurement (e.g., by the MN from the CN or OAM, or by the SN from the OAM or the MN), and determining information related to configuration of the at least one QoE measurement, wherein the information related to configuration of the at least one QoE measurement includes at least one of information related to whether the same QoE measurement is configured in the UE by the MN or the SN, information related to an RRC identifier for the QoE measurement, or information related to an RRC identifier for the RVQoE measurement.

[0068] Information related to whether the same QoE measurement is configured in a UE by an MN or an SN (hereinafter, "first information") can coordinate QoE configuration and reporting between two RAN nodes, e.g., an MN and an SN, to avoid the same QoE measurement, e.g., the same management-based QoE measurement, being configured in the same UE by both the MN and the SN. Exemplary first information is QoE configuration allowance indication information indicating that QoE measurement from the SN is allowed by the MN, or QoE configuration rejection indication information indicating that QoE measurement from the SN is rejected by the MN, or other related information. Information related to an RRC identifier for QoE measurement (hereinafter, "second information") can coordinate QoE configuration and reporting between two RAN nodes, e.g., an MN and an SN, to avoid two different QoE measurements, e.g., two different management-based QoE measurements with the same RRC identifier, being configured in the same UE. Exemplary second information is an RRC identifier value range, or a specific RRC identifier value for QoE measurement used by the MN or SN, or other related information. Information related to the RRC identifier for RVQoE measurements (hereinafter referred to as the third information) can coordinate RVQoE configuration and reporting between two RAN nodes, e.g., an MN and an SN, to avoid problems similar to those solved by the first and second information. An exemplary third information is an RRC identifier value range, a single RRC identifier value for RVQoE measurements used by the MN and / or SN, or other related information. The first, second, and third information may be applied singly or in any combination in embodiments of the present application to solve some or all of Problems 1 to 3. That is, an embodiment of the present application may apply all of the first, second, and third information, or may apply two of the first, second, and third information, or may apply only one of the first, second, and third information. In some embodiments of the present application, the second and / or third information may be implicit in the first information.

[0069] Some detailed embodiments of the present application are presented below in light of some exemplary NR-DC scenarios. Although MNs and SNs in NR-DC are shown in the exemplary embodiments, those skilled in the art should understand that the presented technical solutions may also be applied to similar RAN nodes and / or similar scenarios and should not be limited to specific devices and scenarios. In addition, for clarity, various exemplary embodiments are presented focusing on various technical measures, which may be combined in various ways by those skilled in the art under the disclosure and teachings of the present application, but are not shown in detail.

[0070] First, some embodiments of the present application that mainly take into consideration problem 1 are presented below.

[0071] According to some embodiments (Scenario 1) of the present application, the UE determines whether two QoE measurement configurations (or configuration information) from the MN and the SN overlap, and ignores (or rejects or deletes, etc.) one or both of the overlapping QoE measurement configurations. Figure 2 is a flowchart of a procedure for QoE measurement collection under Scenario 1 according to some embodiments of the present application.

[0072] 2, in step 201a, a RAN node serving as an MN may receive information indicating at least one QoE measurement. For example, the MN may receive QoE measurement activation information, which is either a direct configuration from the OAM (e.g., in the case of management-based QoE measurement) or signaling from the OAM via the CN, including UE-related QoE configurations (e.g., in the case of signaling-based QoE measurement). In the case of management-based QoE measurement, the OAM sends one or more QoE measurement configurations to the RAN node. In the case of signaling-based QoE measurement, the OAM initiates QoE measurement activation for a specific UE via the CN node, and the CN node sends QoE measurement configuration information to the RAN node for QoE measurement activation. Exemplary QoE measurement configuration information from the CN or OAM (also referred to as "CN / OAM QoE measurement configuration information") includes: - QoE Reference: Used to identify QoE measurements between the gNB and the CN or between the gNB and the OAM. - Service Type: Indicates the service type of the QoE measurement. - Container for application layer measurement configurations: Contains application layer measurement configurations. - Area Coverage: The area coverage of the QoE measurement, including a list of cells, Tracking Areas (TAs), Tracking Area Identifiers (TAIs), or Public Land Mobile Networks (PLMNs).

[0073] Similarly, in step 201b, another RAN node serving as an SN may also receive information indicating at least one QoE measurement. For example, the SN may receive QoE measurement activation information from the MN (in the case of signaling-based QoE measurement) or QoE measurement configuration information from the OAM (in the case of management-based QoE measurement). In the case of management-based QoE measurement, the SN may receive the QoE measurement configuration from the OAM as indicated above with respect to the MN, and the received QoE measurement configuration may be different from or identical to the QoE measurement configuration to the MN. In the case of signaling-based QoE measurement, the MN receives QoE measurement activation signaling from the OAM via the CN and then requests the SN to provide the UE with a QoE measurement configuration by sending QoE measurement activation information, for example, in an S-node addition request message or an S-node modification request message. The MN may also include the UE QoE measurement capability in the message. Exemplary QoE measurement activation information may include a QoE reference, a service type, a Measurement Collection Entity (MCE) Internet Protocol (IP) address, a slice range, an area range, or Minimization of Drive Test (MDT), alignment information, and an indication of available RVQoE metrics, etc. In some embodiments of the present application, the MN may also send a requested signaling radio bearer (SRB) type, e.g., an SRB3, for the requested QoE measurement to the SN.

[0074] In this specification, only management-based QoE measurement is shown in scenario 1 as an example to illustrate how to solve the problem caused by overlapping QoE measurement configurations from MN and SN. It is assumed that MN and SN receive the same QoE measurement, for example, with a QoE reference of 1, and both MN and SN select the same UE with DC configuration for management-based QoE measurement. However, those skilled in the art will well understand that the illustrated technical solution can also be applied to signaling-based QoE measurement.

[0075] In detail, after receiving the QoE measurements, the MN selects UEs that satisfy the required QoE measurements and allocates (or assigns or configures, etc.) an RRC identifier (hereinafter, MN RRC identifier), e.g., measConfigAppLayerId, which is 2, to the QoE measurements, where the RRC identifier is used to identify a QoE configuration for the QoE measurements between the MN and the UE, e.g., an application layer measurement configuration for the QoE measurements between the MN and the UE (also referred to as RRC QoE measurement configuration). Hereinafter, the QoE configuration for the QoE measurements between the MN and the UE identified by the RRC identifier is also referred to as the MN QoE configuration. An exemplary MN QoE configuration includes the MN RRC identifier and an application layer measurement container for the QoE measurements. In step 203a, the MN sends the MN QoE configuration to the selected UEs, e.g., by RRC signaling (e.g., in AppLayerMeasConfig in an RRCReconfiguration message).

[0076] Similarly, after receiving a QoE measurement whose QoE reference is 1, the SN selects the same UE that satisfies the required QoE measurement, but independently allocates another RRC identifier (hereinafter referred to as SN RRC identifier) ​​to the same QoE measurement, which may be identical to or different from the MN identifier, e.g., measConfigAppLayerId, which is 3. Hereinafter, the QoE configuration of the QoE measurement between the SN and the UE identified by the RRC identifier is also referred to as the SN QoE configuration. In step 203b, the SN sends the SN QoE configuration of the QoE measurement to the selected UE, e.g., by SRB3, e.g., by RRC signaling. An exemplary SN QoE configuration of the QoE measurement includes the SN RRC identifier of the QoE measurement and an application layer measurement container.

[0077] From the UE's perspective, the UE may receive QoE measurement configurations from both the MN and the SN, for example, two application layer QoE configurations from the MN and the SN (each corresponding to an MCG leg or an SCG leg), respectively. According to some embodiments of the present application, the UE determines (or detects, identifies, etc.) whether the QoE configuration from the MN and the QoE configuration from the SN relate to the same QoE measurement, i.e., whether the QoE configuration from the MN and the QoE configuration from the SN are overlapping. If there are two overlapping QoE configurations, the UE ignores at least one of the two overlapping QoE configurations. When only one QoE configuration is ignored, which one of the overlapping QoE configurations is ignored may be determined based on various standards, for example, the time it takes for the QoE configuration to reach the application layer of the UE, etc.

[0078] 2, the RRC layer of the UE receives an MN QoE configuration from the MN in step 203a and an SN QoE configuration from the SN in step 203b, and then forwards the MN QoE configuration and the SN QoE configuration to the application layer of the UE in steps 205a and 205b, respectively. For the received MN QoE configuration and SN QoE configuration, the application layer performs QoE measurement overlap detection (or determination, etc.) in step 207 to detect whether the MN QoE configuration and the SN QoE configuration overlap, for example, by decoding the application layer measurement container in each QoE configuration. If the application layer identifies that the two received application layer measurement containers are for the same QoE measurement, the application layer determines that the two QoE configurations from the MN and SN, respectively, overlap. In response to the overlap determination, the application layer ignores one or both of the two overlapping QoE configurations. For example, the application layer may ignore the later received QoE configuration and perform QoE measurement according to the first received QoE measurement configuration.

[0079] The UE generates overlap indication information (or QoE configuration overlap indication, etc.) by, for example, an application layer and sends it to the network side. The QoE configuration overlap indication indicates that the QoE configurations from the MN and the SN overlap. The QoE configuration overlap indication also indicates that one or both of the overlapping QoE configurations are ignored, and includes a corresponding RRC identifier for identifying the ignored QoE configuration.

[0080] 2 , the application layer of the UE sends a QoE configuration overlap indication to the RRC layer of the UE in step 209. For example, if the SN QoE configuration is ignored, the application layer of the UE provides an SN RRC identifier, for example, 3, in the QoE configuration overlap indication, so that the RRC layer of the UE knows that the RRC identifier based on which the QoE configuration provided by the SN is ignored is 3. If the MN QoE configuration is ignored, the application layer of the UE provides an MN RRC identifier, for example, 2, in the QoE configuration overlap indication, so that the RRC layer of the UE knows that the RRC identifier based on which the QoE configuration provided by the MN is ignored is 2. Then, the RRC layer of the UE sends the QoE configuration overlap indication to the network side.

[0081] In some embodiments of the present application, the QoE configuration overlap indication is sent to the RAN node associated with the QoE configuration to be ignored. For example, if the MN QoE configuration is to be ignored, the RRC layer of the UE sends a QoE configuration overlap indication with the MN RRC identifier to the MN in step 211a, for example, via SRB1, so that the MN knows that the MN QoE configuration is to be ignored by the UE due to the overlap. If the SN QoE configuration is to be ignored, the RRC layer of the UE sends a QoE configuration overlap indication with the SN RRC identifier to the SN in step 211b, for example, via SRB3, so that the SN knows that the SN QoE configuration is to be ignored by the UE due to the overlap. If both of the two overlapping QoE configurations are to be ignored, the QoE configuration overlap indication is sent to each of the MN and the SN. Both the MN RRC identifier and the SN RRC identifier may be included in each QoE configuration overlap indication to the MN and the SN, i.e., the QoE configuration overlap indications to the MN and the SN are identical. In some other embodiments of the present application, the MN RRC identifier is only indicated to the MN in the QoE configuration overlap indication, and the SN RRC identifier is only indicated to the SN in the QoE configuration overlap indication, i.e., the QoE configuration overlap indication to the MN and the SN are independent of each other, which is similar to the behavior when only one QoE configuration is ignored.

[0082] In some other embodiments of the present application, the UE sends the QoE configuration overlap indication only to the MN, regardless of which QoE configuration is ignored. If the SN QoE configuration is ignored (either only one QoE configuration is ignored or both are ignored), the MN conveys the received QoE configuration overlap indication to the SN in step 213. If the MN receives a QoE configuration overlap indication with an MN RRC identifier and an SN RRC identifier, the MN may convey the QoE configuration overlap indication to the SN directly, or may send a QoE configuration overlap indication with only the SN RRC identifier to the SN.

[0083] According to some further embodiments of the present application, when only one of the MN QoE configuration and the SN QoE configuration is ignored, the QoE configuration overlap indication may also indicate the RRC identifier allocated for the non-ignored QoE configuration. For example, when the SN QoE configuration is ignored, the QoE configuration overlap indication to the SN also indicates the MN RRC identifier, so that the SN may use the MN RRC identifier for RVQoE measurement. That is, the RRC identifier allocated by the RAN node for the non-ignored QoE configuration can be sent to a peer RAN node of the RAN node whose QoE configuration is ignored, and the peer RAN node can determine the RRC identifier allocated by the RAN node, e.g., the RVQoE RRC identifier, as third information and use it when configuring the corresponding RVQoE measurement. Therefore, the solution shown in view of Scenario 1 can also solve the problem of the RRC identifier for RVQoE measurement.

[0084] According to some embodiments (Scenario 2) of the present application, after receiving information indicating at least one QoE measurement, a RAN node serving as an SN sends a request, for example, QoE configuration request information, to another RAN node serving as an MN to request whether the indicated QoE measurement is allowed, so as to avoid the same QoE measurement being repeatedly configured in the UE by the MN and the SN. If the QoE measurement is not allowed, the SN does not send the QoE measurement to the UE. Figure 3 is a flowchart of a procedure for QoE measurement collection under Scenario 2 according to some embodiments of the present application.

[0085] Referring to Figure 3, in step 301, a RAN node served as an SN may receive information indicating at least one QoE measurement, which is identical to the QoE measurement shown in Figure 2 and will not be repeated here. For a RAN node served as an MN, the RAN node may or may not also receive information indicating at least one QoE measurement as shown in Figure 2.

[0086] Similarly, only management-based QoE measurement is shown in Scenario 2 as an example to illustrate how to solve the problem caused by overlapping QoE measurement configurations from MN and SN. However, those skilled in the art will well understand that the shown technical solution can also be applied to signaling-based QoE measurement.

[0087] The SN selects UEs that meet the required QoE measurements. In step 303, the SN sends QoE configuration request information to the MN to request whether QoE measurements are allowed. One or more QoE measurements may be included in the same request. Exemplary QoE configuration request information includes at least one of a QoE reference, an area range, or a service type associated with the QoE measurements. In some embodiments of the present application, the QoE configuration request information may further include an SN RRC identifier allocated (or configured) by the SN. The QoE configuration request information may be carried, for example, in an S-NG-RAN node modification request message.

[0088] After receiving the QoE configuration request information, the MN determines whether the requested QoE measurement is allowed (e.g., including whether the requested QoE measurement can be configured by the SN or whether the configuration of the QoE measurement is allowed), and then sends a response (first information) to the SN in step 305, for example, via an S-NG-RAN Node Modification Confirmation message, indicating whether the requested QoE measurement is allowed or rejected.

[0089] In some cases, the MN may determine that QoE measurements requested by the SN are allowed. For example, if the MN QoE configuration is not configured in the UE or is not configured in the UE by the MN, the MN may send QoE configuration allowance indication information to the SN. Exemplary QoE configuration allowance indication information includes a QoE reference to indicate which QoE measurements are allowed by the MN. The QoE configuration allowance indication information may be included in an S-NG-RAN node modification confirmation message, etc.

[0090] After receiving the QoE configuration allowance indication information, the SN provides the UE with an SN QoE configuration for QoE measurement in step 207. In some embodiments of the present application, before sending the QoE configuration request information, the SN has not yet configured an SN QoE configuration for QoE measurement. After receiving the QoE configuration allowance indication information, the SN first configures the SN QoE configuration for QoE measurement and then sends it to the UE.

[0091] In some other cases, the MN may decide to reject the requested QoE measurement. For example, if the MN QoE configuration for the QoE measurement is already configured in the UE or configured in the UE by the MN, the MN may determine that the requested QoE measurement is not allowed. For another example, if the MN is not within the area range provided in the QoE configuration request information, the MN rejects the QoE measurement. In response to determining that the QoE measurement is not allowed or rejected, the MN may send QoE configuration rejection indication information to the SN to indicate that the requested QoE measurement is not allowed. The MN may also provide a cause value in the QoE configuration rejection indication information to indicate why the QoE measurement is rejected or not allowed, for example, because the QoE measurement is already configured in the UE by the MN or is configured in the UE by the MN, or because the MN is not within the area range.

[0092] The solution shown in view of scenario 2 can also solve the problem with the RRC identifier for RVQoE measurement. For example, in some embodiments of the present application, if the SN RRC identifier is included in the QoE configuration request information and the requested QoE measurement is allowed, the MN may also store the SN RRC identifier and use it as the third information (e.g., the RRC identifier for RVQoE measurement) for the corresponding RVQoE measurement, if necessary. If the requested QoE measurement is not allowed, the MN may also indicate the MN RRC identifier for the QoE measurement to the SN. The SN may use the RRC identifier allocated by the MN as the third information for the corresponding RVQoE configuration, if necessary.

[0093] Compared with Scenario 1, the description in Scenario 2 is simplified to avoid unnecessary duplication. Those skilled in the art will appreciate that some similar or identical details shown in Scenario 1 may also be applied to Scenario 2 in the same or similar manner.

[0094] According to some embodiments (Scenario 3) of the present application, after receiving information indicating at least one QoE measurement, for example, an M-based QoE measurement, and selecting a UE with a DC configuration, the RAN node serving as an MN or an SN sends QoE measurement configuration indication information to a peer RAN node serving as an SN or an MN, where the QoE measurement configuration indication information indicates that the QoE measurement has already been configured or will be configured in the UE by the RAN node, so as to avoid the same QoE measurement being repeatedly configured in the UE by the peer RAN node. Figure 4 is a flowchart of a procedure for QoE measurement collection under Scenario 3 according to some embodiments of the present application. In the embodiment shown in Figure 4, the RAN node is an MN and the peer RAN node is an SN, but those skilled in the art will well understand how to apply a similar solution in the case where the RAN node is an SN and the peer RAN node is an MN.

[0095] Referring to Figure 4, in step 401, the MN may receive information indicating at least one QoE measurement, which is identical to that shown in Figure 2 for the RAN node serving as the MN and will not be repeated here.

[0096] Similarly, only management-based QoE measurement is shown in Scenario 3 as an example to illustrate how to solve the problem caused by overlapping QoE measurement configurations from MN and SN. However, those skilled in the art will well understand that the shown technical solution can also be applied to signaling-based QoE measurement.

[0097] The MN selects a UE that satisfies the required QoE measurements. In step 403, the MN may configure QoE measurements and send them to the UE. The MN sends QoE configuration indication information (first information) to the SN in step 405, indicating that QoE measurements have already been configured or will be configured in the UE by the MN. In some embodiments of the present application, the MN may send the QoE configuration indication information before sending the QoE measurements to the UE. The QoE configuration indication information may be carried in an S-NG-RAN node addition request message or an S-NG-RAN node modification request message, for example. Exemplary QoE measurement configuration indication information includes a QoE reference for the QoE measurements.

[0098] After receiving the QoE measurement configuration indication information, the SN knows the M-based QoE measurements that are configured in the UE by the MN or that should be configured in the UE by the MN, and the SN will not trigger the same M-based QoE measurements (if received) to the UE, so that duplicate QoE measurements are not sent to the UE.

[0099] The solution shown in view of scenario 3 can also solve the problem in the RRC identifier for RVQoE measurement. For example, in some embodiments of the present application, a RAN node, e.g., an MN, may also include an RRC identifier of QoE measurement allocated by the RAN node in the QoE measurement configuration indication information, so that a peer RAN node can at least use the allocated MN RRC identifier as third information for corresponding RVQoE measurement when necessary.

[0100] Similarly, the description in Scenario 3 has been simplified to avoid unnecessary duplication compared to Scenario 1. Those skilled in the art will appreciate that some similar or identical details, in particular the information indicating QoE measurements shown in Scenario 1, may also be applied to Scenario 3 in the same or similar manner.

[0101] According to some embodiments (Scenario 4) of the present application, a RAN node serving as an MN or an SN sends a QoE configuration acceptance request to a peer RAN node serving as an SN or an MN to accept the QoE measurements configured by the peer node. Figure 5 is a flowchart of a QoE measurement collection procedure under Scenario 4 according to some embodiments of the present application. In the embodiment shown in Figure 5, the RAN node is an MN and the peer RAN node is an SN, but those skilled in the art will understand well how to apply a similar solution when the RAN node is an SN and the peer RAN node is an MN.

[0102] 5, in step 501, the MN sends a QoE configuration consent request to the SN to consent to QoE measurement configured by the SN. The exemplary QoE configuration consent request may indicate at least one QoE reference, for example, a QoE reference that is 1.

[0103] In response to the QoE configuration acceptance request, the SN sends a response (first information), for example, QoE configuration addition indication information indicating the addition of QoE measurements to the UE, or QoE configuration release indication information indicating the release of QoE measurements to the UE, to the MN step 503. For example, if the SN configures one or more QoE measurements to the UE, the SN reports a QoE configuration addition indication to the MN. If the SN releases one or more QoE measurements to the UE, the SN reports a QoE configuration release indication to the MN. If a QoE reference is indicated in the QoE configuration acceptance request, the SN reports the addition or release of only the QoE measurements related to the indicated QoE reference. If no QoE reference is indicated in the QoE configuration acceptance request, the SN reports the addition or release of any QoE measurements.

[0104] Based on the QoE configuration addition indication information and / or the QoE configuration release indication information, the RAN node knows which QoE measurements are configured for the UE and will not configure the same QoE measurements for the UE, and therefore will not send duplicate QoE measurements to the UE.

[0105] Similarly, the description in Scenario 4 has been simplified to avoid unnecessary duplication compared to Scenario 1. Those skilled in the art will appreciate that some similar or identical details, in particular the information indicating QoE measurements shown in Scenario 1, may also be applied to Scenario 4 in the same or similar manner.

[0106] Moreover, several embodiments of the present application that mainly take into consideration Problem 2 are presented below. Similarly, compared with Scenario 1, the descriptions in the following scenarios are simplified to avoid unnecessary duplication. Those skilled in the art will well understand that some similar or identical details, especially the information indicating QoE measurements shown in Scenario 1, may also be applied to the following in the same or similar manner.

[0107] According to some embodiments (Scenario 5) of the present application, the RAN node serving as the MN is responsible for allocating an RRC identifier value range (second information), e.g., measConfigAppLayerId value range, to QoE measurements from either the MN or the SN. For example, the overall value range of an RRC identifier, e.g., measConfigAppLayerId, is {0...63}. The MN may determine that the value range used by the MN is (0...31) and the value range used by the SN is (32...63), or vice versa. Because different RRC identifier value ranges are used by the MN and the SN, QoE measurements from the MN and the SN are not allocated the same RRC identifier. That is, problems caused by different QoE measurements from the MN and the SN with the same RRC identifier to the UE are avoided.

[0108] The MN sends information indicating the RRC identifier value range for QoE measurements to the SN, which may be sent at the MN's initiative or in response to a request from the SN. For example, when the SN decides to configure QoE measurements, the SN may request from the MN the RRC identifier value range to be used by the SN.

[0109] Exemplary messages or signaling transmitting information indicating the RRC identifier value range are an S-NG-RAN Node Modification Request message or an NG-RAN Node Addition Request message, etc. The information may explicitly indicate the RRC identifier value range for QoE measurements to be used by the SN, e.g., (32...63), or may implicitly indicate the RRC identifier value range for QoE measurements to be used by the SN, e.g., (0...31), or by indicating both the RRC identifier value range to be used by the SN and the RRC identifier value range to be used by the MN, e.g., (0...31) and (32...63).

[0110] When configuring a QoE measurement for a UE, either the MN or the SN selects an RRC identifier value within the corresponding value range. For example, when configuring an RRC identifier for an SN-triggered QoE measurement, the SN allocates an RRC identifier for the QoE measurement within the value range used by the SN. If the RRC identifier value range used by the SN, e.g., the measConfigAppLayerId range, is not received from the MN, the SN does not configure the QoE measurement for the UE.

[0111] The solution shown in view of scenario 5 can also solve the problem in RRC identifier for RVQoE measurement. For example, the RRC identifier value range allocated to the MN can also be used as the third information for RVQoE measurement by the MN, and the RRC identifier value range allocated to the SN can also be used as the third information for RVQoE measurement by the SN.

[0112] Similar to Scenario 5, according to some embodiments of the present application (Scenario 6), the RAN node serving as the MN is responsible for allocating an RRC identifier value (second information), e.g., measConfigAppLayerId, for QoE measurements configured by the SN.

[0113] For example, after receiving a QoE measurement, e.g., a management-based QoE measurement, the SN may send a request to the MN requesting an RRC identifier for the QoE measurement, e.g., information required by the QoE measurement identifier. An exemplary request includes at least one of a QoE reference or a service type. After receiving the request, the MN allocates an RRC identifier for the requested QoE measurement, e.g., measConfigAppLayerId, and sends it to the SN. The SN then uses the RRC identifier indicated by the MN for the QoE measurement.

[0114] In some embodiments of the present application, the SN may request an RRC identifier for QoE measurement in an implicit manner. For example, as shown in Scenario 2, when the SN sends QoE configuration request information with an SN RRC identifier to the MN, but the MN does not allow the requested QoE measurement because the same RRC identifier is allocated by the MN for a different QoE measurement, the MN may indicate another RRC identifier for QoE measurement to be used by the SN.

[0115] Similarly, the solution shown in view of Scenario 6 can also solve the problem of RRC identifier for RVQoE measurement. For example, the RRC identifier allocated by the MN to the SN can also be used as the third information for RVQoE measurement by the SN.

[0116] According to some embodiments (scenario 7) of the present application, the MN and SN may use an independent RRC identifier for the QoE measurement configuration, which is different from the current RRC identifier.

[0117] For example, the independent RRC identifier (second information) may further include an index in addition to the measConfigAppLayerId, where the index for the MN (also referred to as the MN index) and the index for the SN (also referred to as the SN index) are independent and different. Therefore, the QoE measurements from the MN and the SN to the UE can be uniquely identified according to the RRC identifier including the index and the measConfigAppLayerId. An exemplary index, for example, the MN index or the SN index, may be coded in an enumeration type or a bit string type.

[0118] In another example, specific information (second information) is defined as an RRC identifier used in the SN, which means that the QoE measurement is configured by the SN. For example, a specific information element (IE) is defined for the RRC identifier used by the SN. When the UE receives the specific information, the UE determines that the related QoE measurement is configured by the SN. In some embodiments of the present application, a similar solution may also be applied to the MN.

[0119] Similarly, the solution shown in view of scenario 7 can also solve the problem with the RRC identifier for RVQoE measurement. For example, specific information designed for the RRC identifier used by the SN can also be used as the third information for RVQoE measurement by the SN.

[0120] Additionally, with regard to RVQoE measurements, in addition to what is indicated above in scenarios 1 to 7, the following is further indicated: Similarly, with regard to QoE measurements related to RV QoE measurements, what is detailed in scenario 1 may also apply in the same or similar way to the following:

[0121] According to some embodiments of the present application, the MN and SN can configure separate or independent RVQoE configurations for either signaling-based QoE measurement or management-based QoE measurement. How to coordinate RVQoE configurations between the MN and SN for both of the two methods is addressed. The presented solution for RVQoE measurement can be applied independently of or in combination with the solutions for solving problems 1 and 2.

[0122] If RVQoE measurements (related to signaling-based QoE measurements or management-based QoE measurements) are configured by the MN and SN, respectively, a problem similar to problem 2 shown above may occur. Therefore, the MN and SN can be coordinated to use an RRC identifier for RVQoE measurements, as the solutions shown in scenarios 5 to 7 to solve such problems.

[0123] For example, one exemplary solution is similar to the solution shown in Scenario 5. For example, in addition to the embodiment shown in Scenario 5, in some embodiments, the MN is responsible for allocating RRC identifier value ranges for RVQoE measurements. When RVQoE measurements are to be configured by the MN or SN, it needs to select an RRC identifier within the corresponding value range. The MN allocates a value range of RRC identifiers for RVQoE measurements to be used by the SN. When the SN configures RVQoE measurements for a UE, the SN selects an RRC identifier within the allocated value range. If the RRC identifier value range from the MN is insufficient, the SN cannot configure RVQoE measurements for the UE.

[0124] Another exemplary solution is similar to the solution shown in Scenario 6. For example, in addition to the embodiment shown in Scenario 6, in some embodiments, when triggered to configure the UE with RVQoE measurements, the SN requests an RRC identifier for the RVQoE measurements from the MN, which may indicate at least one of a QoE reference or a service type. In response to the request, the MN allocates an RRC identifier for the RVQoE measurements, e.g., measConfigAppLayerId, and sends it to the SN.

[0125] Another exemplary solution is similar to the solution shown in Scenario 7. For example, in addition to the embodiment shown in Scenario 7, in some embodiments, the MN and SN use independent RRC identifiers for RVQoE measurement configuration. For example, RVQoE measurements from the MN and SN to the UE can be uniquely identified according to an RRC identifier including an index and measConfigAppLayerId. In another example, specific information such as an RRC identifier for RVQoE measurements used in the SN is specified, which means that the RVQoE measurements are configured by the SN. In some embodiments of the present application, a similar solution can also be applied to the RRC identifier for the MN used by the RVQoE measurements.

[0126] If the MN and the SN can only configure one (single) RVQoE measurement in the UE for the same QoE measurement, when the RAN node, e.g., the MN, has already configured the QoE measurement in the UE, the peer node, e.g., the SN, may also need to configure the RVQoE measurement in the UE to collect the RVQoE measurement results. Therefore, the peer node needs to know the RRC identifier of the QoE measurement for the RVQoE measurement configuration, which can be solved by the RAN node sending the RRC identifier of the configured QoE measurement to its peer RAN node (voluntarily or in response to a request from the peer RAN node), or by using a solution similar to the solutions shown in Scenarios 1 to 3.

[0127] For example, one exemplary solution is similar to the solution shown in Scenario 1. For example, in addition to the embodiment shown in Scenario 1, in some embodiments, the application layer of the UE may provide the RRC layer of the UE with an RRC identifier allocated for one RAN node for QoE measurement in other messages or scenarios, for example, when receiving one signaling-based QoE measurement from one RAN node. The RRC layer of the UE reports the RRC identifier allocated by the RAN node for QoE measurement to the peer RAN node, so that the peer RAN node knows the RRC identifier configured by the RAN node for QoE measurement. Thus, the peer RAN node can use the RRC identifier allocated by the RAN node for RVQoE configuration, if necessary.

[0128] Another exemplary solution is similar to the solution shown in Scenario 2. For example, in addition to the embodiment shown in Scenario 2, in some embodiments, the SN may send QoE configuration request information to the MN to request whether QoE measurement, e.g., signaling-based QoE measurement, is allowed. If an SN RRC identifier is included in the QoE configuration request information and the requested QoE measurement is allowed, the MN may also store the SN RRC identifier and use it as the RRC identifier for the corresponding RVQoE measurement, if necessary. If the requested QoE measurement is not allowed, the MN may also indicate the MN RRC identifier for the QoE measurement to the SN. The SN may use the RRC identifier allocated by the MN as third information for the corresponding RVQoE configuration, if necessary.

[0129] Yet another exemplary solution is similar to the solution shown in Scenario 3. For example, in addition to the embodiment shown in Scenario 3, in some embodiments, a RAN node, e.g., an MN, sends a QoE measurement configuration indication to a peer RAN node, e.g., an SN, to indicate that a QoE measurement configuration, e.g., signaling-based QoE measurement, is already configured or will be configured in the UE. The MN may also include an RRC identifier allocated by the MN in the QoE measurement to the SN. The SN may use the RRC identifier allocated by the MN for RVQoE configuration, if necessary.

[0130] Furthermore, for RVQoE measurement results generated by the UE, e.g., by an application layer of the UE, how the UE, e.g., the RRC layer, selects the reporting leg, e.g., MCG or SCG, needs to be addressed.

[0131] In some embodiments of the present application, the RRC layer selects at least one leg for reporting the RVQoE measurement result based on the bearer type as well as the RVQoE measurement result, and the application layer may also provide information on at least one of the DRB, QoS flow, or PDU session, for example, at least one of the DRB identifier, QoS flow identifier, or PDU session identifier. If at least one of the DRB, QoS flow, or PDU session is served by only one of the MCG (MCG bearer) or SCG (SCG bearer), the RRC layer reports the RVQoE measurement result to only the corresponding one of the MN and SN. If at least one of the DRB, QoS flow, or PDU session is served by both the MCG and the SCG, the RRC layer reports the RVQoE measurement result to both the MN and the SN.

[0132] In some other embodiments of the present application, the network configures the UE with reporting leg configuration information for RVQoE measurement result reporting legs, which may be, for example, per DRB, per QoS flow, or per PDU session, etc. The UE selects the reporting leg according to the configuration.

[0133] Besides the method, the embodiments of the present application also propose an apparatus for supporting QoE measurement collection. For example, Figure 6 is a block diagram of an apparatus for supporting QoE measurement collection according to some embodiments of the present application.

[0134] 6, the apparatus 600 may include at least one non-transitory computer-readable medium 601, at least one receiving circuit 602, at least one transmitting circuit 604, and at least one processor 606 coupled to the non-transitory computer-readable medium 601, the receiving circuit 602, and the transmitting circuit 604. The apparatus 600 may be a RAN node or a terminal device (e.g., a UE) configured to perform methods such as those shown above.

[0135] In this figure, elements such as at least one processor 606, transmit circuitry 604, and receive circuitry 602 are referred to in the singular, although the plural is contemplated unless limitation to the singular is explicitly stated. In some embodiments of the present application, the receive circuitry 602 and the transmit circuitry 604 may be combined into a single device such as a transceiver. The processor 606 may be a CPU, DSP, microprocessor, etc. In some embodiments of the present application, the apparatus 600 may further include an input device, memory, and / or other components.

[0136] In some embodiments of the present application, the non-transitory computer-readable medium 601 may have computer-executable instructions stored thereon to cause the processor 606 to perform a method relating to a RAN node, e.g., an MN or an SN, as described above. For example, the computer-executable instructions, when executed, cause the processor 606 to interact with the receive circuitry 602 and the transmit circuitry 604 to perform steps relating to a RAN node, as shown above.

[0137] In some embodiments of the present application, the non-transitory computer-readable medium 601 may have computer-executable instructions stored thereon for causing a processor to perform a method relating to a terminal device as described above. For example, the computer-executable instructions, when executed, cause the processor 606 to interact with the receiving circuitry 602 and the transmitting circuitry 604 to perform steps relating to a UE as shown above.

[0138] FIG. 7 shows a block diagram of an apparatus 700 for supporting QoE measurement reporting according to some other embodiments of the present application.

[0139] 7, an apparatus 700, e.g., a UE or RAN node, may include at least one processor 702 and at least one transceiver 704. The transceiver 704 may include at least one separate receiving circuit 706 and transmitting circuit 708, or at least one integrated receiving circuit 706 and transmitting circuit 708. The at least one processor 702 may be a CPU, DSP, microprocessor, etc.

[0140] According to some embodiments of the present application, when the apparatus 700 is a RAN node, e.g., an MN or an SN, the processor is configured to receive information indicating at least one QoE measurement and determine information related to the configuration of the at least one QoE measurement, wherein the information related to the configuration of the at least one QoE measurement includes at least one of first information related to whether the same QoE measurement is configured for the UE by the MN or the SN, second information related to an RRC identifier for the QoE measurement, or third information related to an RRC identifier for the RVQoE measurement.

[0141] According to some other embodiments of the present application, when the apparatus 700 is a UE, the processor may be configured to receive first QoE configuration information from a first Radio Access Network (RAN) node, receive second QoE configuration information from a second RAN node, and, in response to the first QoE configuration information and the second QoE configuration information being associated with the same QoE measurement, send overlap indication information to at least one of the first RAN node or the second RAN node, where the overlap indication information indicates that at least one of the first QoE configuration information or the second QoE configuration information is to be ignored due to the overlap of the first QoE configuration information and the second QoE configuration information for the QoE measurement.

[0142] The methods according to the embodiments of the present application may also be implemented on a programmed processor. However, the controller, flowcharts, and modules may also be implemented in hardware electronic or logical circuitry, such as a general-purpose or special-purpose computer, a programmed microprocessor or microcontroller, and peripheral integrated circuit elements, integrated circuits, discrete component circuits, programmable logic devices, etc. In general, any device capable of implementing the flowcharts shown in the figures may be used to perform the processor functions of the present application. For example, one embodiment of the present application provides an apparatus including a processor and a memory. Computer-programmable instructions for implementing the method are stored in the memory, and the processor is configured to execute the computer-programmable instructions to implement the method. The method may be as described above or another method according to an embodiment of the present application.

[0143] An alternative embodiment preferably implements a method according to an embodiment of the present application on a non-transitory computer-readable storage medium storing computer-programmable instructions. The instructions are preferably executed by a computer-executable component preferably integrated with the network security system. The non-transitory computer-readable storage medium may be stored on any suitable computer-readable medium, such as RAM, ROM, flash memory, EEPROM, an optical storage device (CD or DVD), a hard drive, a floppy drive, or any suitable device. The computer-executable component is preferably a processor, although the instructions may alternatively or additionally be executed by any suitable dedicated hardware device. For example, one embodiment of the present application provides a non-transitory computer-readable storage medium having computer-programmable instructions stored thereon. The computer-programmable instructions are configured to implement a method as described above or other methods according to an embodiment of the present application.

[0144] While the present application has been described using specific embodiments thereof, it is apparent that many alternatives, modifications, and variations may be apparent to those skilled in the art. For example, various components of the present embodiment may be interchanged, added, or substituted in other embodiments. Also, not all elements in each drawing are essential to the operation of the disclosed embodiments. For example, one skilled in the art of the disclosed embodiments will be enabled to make and use the teachings of the present application by simply employing the elements of the independent claims. Accordingly, the embodiments of the present application as described herein are intended to be illustrative, not limiting. Various changes may be made without departing from the spirit and scope of the present application. [Explanation of symbols]

[0145] 100 Wireless Communication System, Dual Connectivity System 101 User Equipment (UE) 102 Master Node (MN) 103 Secondary Node (SN) 600 equipment 601 Non-transitory computer-readable medium 602 receiving circuit 604 Transmitting circuit 606 processor 700 equipment 702 processor 704 Transceiver 706 Receiving Circuit 708 Transmitting Circuit

Claims

1. A transceiver; a processor coupled to the transceiver; wherein the processor: receiving first quality of experience (QoE) configuration information from a first radio access network (RAN) node; receiving second QoE configuration information from a second RAN node; transmitting overlap indication information to at least one of the first RAN node or the second RAN node in response to the first QoE configuration information and the second QoE configuration information being associated with the same QoE measurement, the overlap indication information indicating that at least one of the first QoE configuration information or the second QoE configuration information is ignored due to the overlap of the first QoE configuration information and the second QoE configuration information for a QoE measurement; A user equipment (UE) configured to:

2. 10. The UE of claim 1, wherein if RAN visible QoE (RVQoE) measurement configuration information is also received, a radio resource control (RRC) layer of the UE selects at least one leg of a master node (MN) and a secondary node (SN) for reporting RVQoE measurement results.

3. A transceiver; a processor coupled to the transceiver; wherein the processor: receiving information indicative of at least one quality of experience (QoE) measurement; determining information related to the configuration of the at least one QoE measurement, wherein the information related to the configuration of the at least one QoE measurement includes at least one of: first information related to whether the same QoE measurement is configured in a user equipment (UE) by a master node (MN) or a secondary node (SN); second information related to a radio resource control (RRC) identifier for QoE measurements; or third information related to an RRC identifier for RAN-visible QoE (RVQoE) measurements; A radio access network (RAN) node configured to:

4. the RAN node is a MN and the peer node is a SN, and the processor receiving QoE configuration request information from the SN to request whether QoE measurement is allowed; sending the first information to the SN in response to the QoE configuration request information, the first information being QoE configuration allowance indication information indicating that the QoE measurement is allowed or QoE configuration rejection indication information indicating that the QoE measurement is rejected; 4. The RAN node of claim 3, configured to:

5. 5. The RAN node of claim 4, wherein the RRC identifier of the QoE measurement is allocated by the MN and sent to the SN together with the QoE configuration allowance indication information, or allocated by the SN and sent to the MN together with the QoE configuration request information.

6. the processor: transmitting the first information to a peer node, the first information being QoE measurement configuration indication information indicating that QoE measurement has been configured or will be configured in the UE by the RAN node.

4. The RAN node of claim 3, configured to:

7. the processor: sending a QoE configuration acceptance request to a peer node to accept a QoE measurement configured by said peer node; receiving the first information from the peer node, the first information being a QoE configuration addition indication indicating a QoE measurement configured on a UE or a QoE configuration release indication indicating a QoE measurement released on a UE; 4. The RAN node of claim 3, configured to:

8. the RAN node is a MN and the peer node is a SN, and the processor transmitting the second information to the SN, the second information indicating an RRC identifier value range for QoE measurements to be used by the SN.

4. The RAN node of claim 3, configured to:

9. the RAN node is a MN and the peer node is a SN, and the processor receiving a request from the SN requesting an RRC identifier for QoE measurement; sending the second information to the SN, wherein the second information indicates the RRC identifier for the QoE measurement; 4. The RAN node of claim 3, configured to:

10. the processor is configured to transmit the second information to a UE; If the RAN node is an MN, the second information indicates a measConfigAppLayerId and an MN index for QoE measurement configured on the UE by the MN; 4. The RAN node of claim 3, wherein if the RAN node is an SN, the second information indicates a measConfigAppLayerId and an SN index for QoE measurements configured by the SN to the UE.

11. the RAN node is a MN and the peer node is a SN, and the processor transmitting the third information to the SN, wherein the third information indicates an RRC identifier value range for RVQoE measurements to be used by the SN.

4. The RAN node of claim 3, configured to:

12. the RAN node is an SN, the peer node is an MN, and the processor receiving the third information from the MN, the third information indicating an RRC identifier value range for RVQoE measurements to be used by the SN; 4. The RAN node of claim 3, configured to:

13. the RAN node is a MN and the peer node is a SN, and the processor receiving a request from the SN requesting an RRC identifier for RVQoE measurement; sending the third information to the SN, wherein the third information indicates the RRC identifier for the RVQoE measurement; 4. The RAN node of claim 3, configured to:

14. the processor is configured to transmit the third information to a UE; If the RAN node is an MN, the third information indicates a measConfigAppLayerId and an MN index for RVQoE measurement configured on the UE by the MN; 4. The RAN node of claim 3, wherein if the RAN node is an SN, the third information indicates a measConfigAppLayerId and an SN index for RVQoE measurements configured in the UE by the SN.

15. 4. The RAN node of claim 3, wherein, when overlap indication information is received from a UE indicating that QoE configuration information from the RAN node is to be ignored due to overlap with other QoE configuration information for the same QoE measurement, the processor is configured to determine an RRC identifier of the other QoE configuration information received together with the overlap indication information as the third information to be used by the RAN node for a corresponding RVQoE measurement.

Images