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

Abstract

A method of supporting quality of experience (QoE) measurement collection may include receiving first QoE configuration information from a first RAN node; receiving second QoE configuration information from the second RAN node; and transmitting repetition 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, wherein the repetition indication information indicates that at least one of the first QoE configuration information and the second QoE configuration information is ignored due to the repetition of the first QoE configuration information and the second QoE configuration information.

Description

Technical Field

[0001] Embodiments of the present application relate generally to wireless communication techniques, and more particularly to methods and apparatuses supporting the collection of Quality of Experience (QoE) measurements. Background Art

[0002] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcast, etc. Wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources such as 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 which may also be referred to as new radio (NR) systems.

[0003] In 3GPP Release (Rel)-17, the basic mechanism for NR QoE is specified. Because NR Dual Connectivity (DC) is an important commercial deployment scenario for 5G networks, it is critical to support NR-DC in the NR QoE framework. Therefore, QoE in Rel-18 will support QoE measurement configuration and measurement reporting for NR-DC scenarios, as agreed in RP-213159 as follows:

[0004] -Specify the QoE configuration and measurement reporting of MN / SN through the NR-DC architecture and specify the QoE measurement reporting through other DC branches in order to maintain reporting continuity.

[0005] However, in some scenarios (e.g., management-based measurements in NR-DC), both the master node (MN) and the 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 occur. For example, the application layer of the user equipment (UE) may receive two identical application layer measurement configurations with different measConfigAppLayerIds of the QoE measurements configured by the MN and the SN, respectively, which will cause the QoE measurement failure in the UE application layer.

[0006] In view of the above, the industry is looking forward to improving the technology for collecting QoE measurements, especially improving the QoE measurements to support NR-DC. Summary of the invention

[0007] One object of embodiments of the present application is to provide a technical solution to support QoE measurement collection, for example, a method and apparatus to support QoE measurement collection of NR-DC by coordinating MN and SN or the like.

[0008] Some embodiments of the present application provide a UE, comprising: 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 transmit repetition 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 repetition indication information indicates that at least one of the first QoE configuration information or the second QoE configuration information is ignored because the first QoE configuration information and the second QoE configuration information are repeated for the QoE measurement.

[0009] In some embodiments of the present application, the first QoE configuration information and the second QoE configuration information are received by a radio resource control (RRC) layer of the UE from the MN and the SN, respectively. According to some embodiments of the present application, the first QoE configuration information and the second QoE configuration information are transmitted by the RRC layer to the application layer of the UE, and whether the first QoE configuration information and the second QoE configuration information are repeated and which QoE configuration information will be ignored is determined by the application layer.

[0010] In some embodiments of the present application, the repetition indication information indicates that only one of the repeated first QoE configuration information and the second QoE configuration information is ignored using the RRC identifier of the ignored QoE configuration information. According to some embodiments of the present application, the repetition indication information further indicates the RRC identifier of the other of the first QoE configuration information and the second QoE configuration information.

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

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

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

[0014] In some embodiments of the present application, when any one of the first QoE configuration information and the second QoE configuration information is information of an RRC identifier of the SN, the corresponding QoE measurement information is configured by the SN.

[0015] In some embodiments of the present application, when the RVQoE measurement configuration information is also received, the RRC layer of the UE will select at least one branch of the MN and the SN to report the RVQoE measurement result.

[0016] According to some embodiments of the present application, the RRC layer receives the RVQoE measurement result 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 the application layer of the UE. The RRC layer selects the at least one branch based on the bearer type to report the RVQoE measurement result, wherein in the case where the 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 result only to the corresponding one of the MN and the SN, and in the case where the 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 result to both the MN and the SN.

[0017] According to some embodiments of the present application, the RRC layer selects the at least one branch to report the RVQoE measurement result based on reporting branch configuration information.

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

[0019] Some other embodiments of the present application provide a RAN node, such as a MN or a SN, comprising: a transceiver; and a processor coupled to the transceiver. The processor is configured to: receive information indicating at least one QoE measurement; and determine information associated with the configuration of the at least one QoE measurement, wherein the information associated with the configuration of the at least one QoE measurement comprises at least one of the following: first information related to whether the same QoE measurement is configured to the UE by the MN or the SN; second information related to the RRC identifier of the QoE measurement; or third information related to the RRC identifier of the RVQoE measurement.

[0020] 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 for requesting whether to allow QoE measurement; and transmit the first information to the SN in response to the QoE configuration request information, wherein the first information is 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. 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: transmit QoE configuration request information to the MN for requesting whether to allow QoE measurement; and receive the first information from the MN, wherein the first information is 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.

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

[0022] According to some embodiments of the present application, the QoE configuration rejection indication information indicates an RRC identifier of the configuration information corresponding to 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 corresponding RVQoE measurement.

[0023] According to some embodiments of the present application, the QoE configuration rejection indication information indicates a reason value for indicating why the QoE configuration is rejected.

[0024] 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.

[0025] In some embodiments of the present application, the processor is configured to: transmit the first information to a peer node, wherein the first information is QoE measurement configuration indication information indicating that QoE measurement has been or will be configured by the RAN node for the UE. In some other embodiments of the present application, the processor is configured to: receive the first information from a peer node, wherein the first information is QoE measurement configuration indication information indicating that QoE measurement has been or will be configured by the RAN node for the UE.

[0026] 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 corresponding node for corresponding RVQoE measurement.

[0027] In some embodiments of the present application, the processor is configured to: transmit a QoE configuration subscription request to a peer node to subscribe to a QoE measurement configured by the peer node; and receive the first information from the peer node, wherein the first information is QoE configuration addition indication information indicating a QoE measurement configured for a UE or QoE configuration release indication information indicating a QoE measurement released to a UE. In some other embodiments of the present application, the processor is configured to: receive a QoE configuration subscription request from a peer node to subscribe to a QoE measurement configured by the peer node; and transmit the first information to the peer node, wherein the first information is QoE configuration addition indication information in response to configuring a QoE measurement for a UE or QoE configuration release indication information in response to releasing the configured QoE measurement to a UE.

[0028] According to some embodiments of the present application, when the QoE configuration subscription request indicates at least one QoE reference, only the addition or release of the QoE measurement associated with the at least one QoE reference is reported; and when no QoE reference is indicated in the QoE configuration subscription request, the addition or release of any QoE measurement is reported.

[0029] 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: transmit the second information to the SN, wherein the second information indicates a range of RRC identifier values ​​for QoE measurements used by the SN. In some scenarios, the second information indicating the range of RRC identifier values ​​for QoE measurements 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 a SN and the peer node is a MN, and the processor is configured to: receive the second information from the MN, wherein the second information indicates a range of RRC identifier values ​​for QoE measurements used by the SN. In some scenarios, the processor is configured to: transmit a request to the MN requesting the range of RRC identifier values.

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

[0031] 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: receive a request for an RRC identifier for QoE measurement from the SN; and transmit the second information to the SN, wherein the second information indicates the RRC identifier for the QoE measurement. In some other embodiments of the present application, the RAN node is a SN, and the peer node is a MN, and the processor is configured to: transmit a request for an RRC identifier for QoE measurement to the MN; and receive the second information from the MN, wherein the second information indicates the RRC identifier for the QoE measurement.

[0032] 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.

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

[0034] In some embodiments of the present application, the processor is configured to transmit the second information to the UE, and when the RAN node is a MN, the second formation indicates the measConfigAppLayerId and MN index of the QoE measurement configured by the MN for the UE; and when the RAN node is a SN, the second formation indicates the measConfigAppLayerId and SN index of the QoE measurement configured by the SN for the UE.

[0035] 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: transmit the third information to the SN, wherein the third information indicates a range of RRC identifier values ​​for RVQoE measurements used by the SN.

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

[0037] In some embodiments of the present application, the RAN node is a SN, and the peer node is a MN, and the processor is configured to: receive the third information from the MN, and the third information indicates a range of RRC identifier values ​​for RVQoE measurement used by the SN.

[0038] According to some embodiments of the present application, the processor is configured to: transmit a request for the RRC identifier value range for RVQoE measurements used by the SN.

[0039] 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: receive a request for an RRC identifier for RVQoE measurement from the SN; and transmit the third information to the SN, wherein the third information indicates the RRC identifier for the RVQoE measurement. In some other embodiments of the present application, the RAN node is a SN, and the peer node is a MN, and the processor is configured to: transmit a request for an RRC identifier for RVQoE measurement to the MN; and receive the third information from the MN, and the third information indicates the RRC identifier for the RVQoE measurement.

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

[0041] In some embodiments of the present application, the processor is configured to transmit the third information to the UE, and when the RAN node is a MN, the third information indicates the measConfigAppLayerId and MN index of the RVQoE measurement configured by the MN for the UE; and when the RAN node is a SN, the third information indicates the measConfigAppLayerId and SN index of the RVQoE measurement configured by the SN for the UE.

[0042] In some embodiments of the present application, in the event that repetition indication information is received from the UE indicating that the QoE configuration information from the RAN node is ignored because it is repeated with other QoE configuration information for the same QoE measurement, the processor is configured to determine the RRC identifier of the other QoE configuration information received together with the repetition indication information as the third information, to be used by the RAN node for corresponding RVQoE measurement.

[0043] Some other embodiments of the present application provide a method for supporting QoE measurement collection, for example performed by a UE, comprising: receiving first QoE configuration information from a first RAN node; receiving second QoE configuration information from a second RAN node; and transmitting repetition 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, wherein the repetition indication information indicates that at least one of the first QoE configuration information or the second QoE configuration information is ignored because the first QoE configuration information and the second QoE configuration information are repeated for the QoE measurement.

[0044] Still other embodiments of the present application provide a method for supporting QoE measurement collection, which can be performed in a RAN node (e.g., MN or SN), and the method includes: receiving information indicating at least one QoE measurement; and determining information associated with the configuration of the at least one QoE measurement, wherein the information associated with the configuration of the at least one QoE measurement includes at least one of the following: first information related to whether the same QoE measurement is configured to the UE by the MN or the SN; second information related to the RRC identifier of the QoE measurement; or third information related to the RRC identifier of the RVQoE measurement.

[0045] In view of the above, embodiments of the present application provide a method and apparatus for supporting QoE measurement collection, which can coordinate QoE measurements (including RVQoE measurements in some scenarios) performed by MN and SN in NR-DC scenarios. Therefore, the present application can facilitate and improve the implementation of NR. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] In order to describe the manner in which the advantages and features of the present application can be obtained, the description of the present application is presented by reference to specific embodiments of the present application illustrated in the accompanying drawings. These drawings depict only example embodiments of the present application and therefore should not be considered to limit its scope.

[0047] Figure 1 A wireless communication system according to some embodiments of the present application is described.

[0048] Figure 2 is a flowchart of a QoE measurement collection procedure in scenario 1 according to some embodiments of the present application.

[0049] Figure 3 is a flowchart of a QoE measurement collection procedure in scenario 2 according to some embodiments of the present application.

[0050] Figure 4 is a flowchart of a QoE measurement collection procedure in scenario 3 according to some embodiments of the present application.

[0051] Figure 5 is a flowchart of a QoE measurement collection procedure in scenario 4 according to some embodiments of the present application.

[0052] Figure 6 A block diagram illustrating a device supporting QoE measurement collection according to some embodiments of the present application.

[0053] Figure 7 A block diagram illustrating an apparatus supporting QoE measurement reporting according to some other embodiments of the present application. DETAILED DESCRIPTION

[0054] The detailed description of the accompanying drawings is intended as a description of the preferred embodiments of the present application, and is not intended to represent the only form in which the present application can be practiced. It should be understood that the same or equivalent functions can be accomplished by different embodiments that are intended to be included in the spirit and scope of the present application.

[0055] Reference will now be made in detail to some embodiments of the present application, examples of which are illustrated in the accompanying drawings. To facilitate understanding, embodiments are provided under specific network architectures and new service scenarios (e.g., 3GPP 5G, 3GPP LTE, etc.). It is considered that all embodiments in the present application are also applicable to similar technical problems as network architectures and new service scenarios develop. In addition, the terms cited in the present application may be changed, which should not affect the principles of the present application.

[0056] In the 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. One of the nodes may provide NR access, and the other node may provide Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA) (E-UTRA) or NR access. One node may serve as a MN and the other node may serve as a SN. The MN and the SN are connected via a network interface (e.g., an Xn interface specified in a 3GPP standard profile), and at least the MN is connected to a core network (CN).

[0057] For example, Figure 1 A schematic diagram illustrating a wireless communication system 100 according to some embodiments of the present application.

[0058] like Figure 1 As shown in FIG. 1 , the wireless communication system 100 may be a dual-connectivity system 100 including at least one UE 101, at least one MN 102, and at least one SN 103. Specifically, for illustrative purposes, Figure 1 The dual connectivity system 100 in FIG. 1 includes a UE 101, a MN 102, and a SN 103. Figure 1 A specific number of UEs 101, MNs 102, and SNs 103 are depicted in FIG. 1 , but it is contemplated that any number of UEs 101, MNs 102, and SNs 103 may be included in the wireless communication system 100.

[0059] refer to Figure 1 UE 101 may be connected to MN 102 and SN 103 via an interface (e.g., a Uu interface specified in a 3GPP standard profile). MN 102 and SN 103 may be connected to each other via a network interface (e.g., an Xn interface specified in a 3GPP standard profile) (e.g., an NG interface specified in a 3GPP standard profile). MN 102 may be connected to SN 103 via a network interface (e.g., an Xn interface specified in a 3GPP standard profile). Figure 1 UE 101 may be configured to utilize resources provided by MN 102 and SN 103 to perform data transmission.

[0060] In some embodiments of the present application, 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 TV (e.g., a TV connected to the Internet), a set-top box, a game console, a security system (including a security camera), a car computer, a network device (e.g., a router, a switch, and a modem), or the like. In some other embodiments of the present application, UE 101 may include a portable wireless communication device, a smart phone, a cellular phone, a flip phone, a device with a subscriber identity module, a personal computer, a selective call receiving circuit system, or any other device capable of sending and receiving communication signals on a wireless network. In some other embodiments of the present application, UE 101 may include a wearable device, such as a smart watch, a fitness bracelet, an optical head-mounted display, or the like. In addition, UE 101 may be referred to as a subscriber unit, a mobile device, 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 described using other terms used in the art.

[0061] MN 102 refers to a radio access network (RAN) node that provides a control plane connection to a core network. In an embodiment of the present application, in an E-UTRA-NR DC (EN-DC) scenario, MN 102 may be an eNB. In another embodiment of the present application, in a next generation E-UTRA-NR DC (NGEN-DC) scenario, 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, MN 102 may be a gNB. In some embodiments of the present application, MN 102 may also be referred to as a master NG-RAN (M-NG-RAN) node.

[0062] A MN branch may be referred to as an MCG. An MCG may refer to a set of serving cells associated with MN 102 and includes a primary cell (PCell) and optionally one or more secondary cells (SCells). A PCell may provide control plane connectivity to UE 101.

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

[0064] An SN branch may be referred to as an SCG. An SCG may refer to a group of serving cells associated with an SN, and includes a primary supplementary cell (PSCell) and optionally one or more SCells.

[0065] The PCell of MCG and the PSCell of SCG can also be called special cells (SpCell).

[0066] In addition, regarding QoE measurement collection (QMC, also referred to as "QoE measurements") activation and reporting, TS38.300 specifies the following:

[0067] “The feature is activated in the NG-RAN by direct configuration from the OAM system (management-based activation) or by signaling from OAM via the core network containing the UE-associated QoE configuration (signaling-based activation). One or more QoE measurement collection operations may be activated at the UE per service type and each QoE measurement configuration is uniquely identified by a QoE reference.

[0068] For signaling-based QoE measurement, 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 with the help of UE-associated signaling. The QoE measurement configuration activated based on signaling contains a list of application layer measurement configurations and corresponding information for QoE measurement collection, such as QoE reference, service type, MCE IP address, slice range, area range, MDT alignment information, and available RAN visible QoE metric indication. 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 the AppLayerMeasConfig specified in TS38.331

[12] .

[0069] For management-based QoE measurement activation, OAM sends one or more QoE measurement configurations to the NG-RAN node. The management-based activated QoE measurement configuration also contains a list of application layer measurement configurations and corresponding information for QoE measurement collection. Each application layer measurement configuration is encapsulated in a transparent container. The NG-RAN node selects a UE that meets the required QoE measurement capability, area scope, and slice scope.

[0070] The UE reports the QoE measurement results to the NG-RAN node in the uplink RRC message, such as

[0071] Specified in TS 38.331

[12] . The NG-RAN node transmits the QoE report and the corresponding QoE reference ID to the MCE. QoE measurement collection is handled by application layer measurement configuration and measurement reporting, supported only in RRC_CONNECTED state. The application layer measurement configuration received by the gNB from OAM or CN is encapsulated in a transparent container, which is forwarded to the UE as an application layer configuration in the RRCReconfiguration message (multiple configurations may be present in the same message). Application layer measurement reports received from higher layers of the UE are encapsulated in a transparent container and sent to the network in a MeasurementReportAppLayer message as specified in TS 38.331

[12] . The UE may send multiple application layer measurement reports to the gNB in ​​one MeasurementReportAppLayer message. In order to allow the transmission of application layer measurement reports exceeding the maximum PDCP SDU size, segmentation of the MeasurementReportAppLayer message may be enabled by the gNB. The measConfigAppLayerId communicated in RRC signaling is used to identify the application layer measurement configuration and reporting between the gNB and the UE. The RRC identifier is mapped to a QoE reference in the gNB. The application layer measurement report is forwarded to OAM together with the QoE reference. The gNB may release one or more application layer measurement configurations from the UE in 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 a specific application layer measurement configuration. ”

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

[0073] According to RP-213159, support for QoE measurement configuration and measurement reporting of MN / SN through NR-DC scenarios will be addressed in Rel-18, and therefore a large number of issues need to be addressed. Taking management-based QoE measurement as an example, since both MN and SN can receive QoE measurement configuration from OAM, some problems may occur without coordination between MN and SN.

[0074] In an exemplary scenario, OAM may provide the same QoE measurement configuration to both MN and SN separately, because OAM does not know whether NR-DC is configured for the UE. In the absence of coordination between MN and SN, both MN and SN may provide QoE measurements with different allocated measConfigAppLayerId to the same UE respectively (Problem 1). Therefore, the application layer of the UE may receive two identical application layer measurement configurations with different mesConfigAppLayerId from MN and SN respectively, which may cause QoE measurement failure in the UE application layer. Even in the case where the measConfigAppLayerId allocated by MN and SN is the same for the same QoE measurement, there may be problems due to two duplicate QoE measurements.

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

[0076] In addition, in the case of RVQoE measurements whose measurement results are visible to RAN nodes, how to coordinate RVQoE configuration and reporting between MN and SN should also be addressed (Question 3). Regarding RVQoE measurements (or RVQoE configurations), they are configured by the gNB, where a subset of QoE metrics are reported from the UE as explicit IEs readable by the gNB. RVQoE measurements can be used 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 (regular QoE measurements). RVQoE measurements can be reported with a reporting periodicity different from one of the regular QoE measurements. If the reporting periodicity is not defined in the RAN-visible QoE configuration, the RAN-visible QoE report is sent together with the regular QoE report. In the absence of coordination between the MN and the SN, the MN or SN may not know the RRC identifier of the regular QoE measurement of the RVQoE configuration if the peer node has assigned an RRC identifier for the regular QoE measurement.

[0077] At least to solve the above-mentioned problems regarding QoE measurement, embodiments of the present application provide a technical solution that supports QoE measurement collection (even if RVQoE measurement is configured), for example, a method and device that supports QoE measurement collection that considers coordination between MN and SN.

[0078] For example, an embodiment of the present application provides a method for supporting QoE measurement collection, which can be performed by a UE or the like. The method includes: receiving first QoE configuration information from a first RAN node (e.g., MN), for example, by an RRC layer of a UE; receiving second QoE configuration information from a second RAN node (e.g., SN), for example, by an RRC layer of the UE; and transmitting repetition 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). An exemplary repetition indication information will indicate that one of the first and second QoE configuration information is ignored (or rejected or cancelled) because the first and second QoE configuration information are repeated for QoE measurement, and indicates the RRC identifier of the ignored QoE configuration information. Another exemplary repetition indication information will indicate that both the first and second QoE configuration information are ignored (or rejected or cancelled) because they are repeated for QoE measurement, and indicates the RRC identifier of each ignored QoE configuration information.

[0079] Some other embodiments of the present application provide another method for supporting QoE measurement collection, which can be performed in a RAN node (e.g., MN or SN or the like). The method includes: receiving information indicating at least one QoE measurement (e.g., by MN from CN or OAM or by SN from OAM or MN); and determining information associated with the configuration of at least one QoE measurement, wherein the information associated with the configuration of at least one QoE measurement includes at least one of the following: information related to whether the same QoE measurement is configured to the UE by the MN or the SN, information related to the RRC identifier of the QoE measurement, or information related to the RRC identifier of the RVQoE measurement.

[0080] Information related to whether the same QoE measurement is configured by the MN or the SN to the UE (hereinafter the first information) can coordinate the QoE configuration and reporting between the two RAN nodes (e.g., the MN and the SN) to avoid the same QoE measurement, for example, the same management-based QoE measurement is configured by both the MN and the SN to the same UE. Exemplary first information is QoE configuration allow indication information indicating that the MN allows the QoE measurement from the SN or QoE configuration reject indication information indicating that the MN rejects the QoE measurement from the SN, or other related information. Information related to the RRC identifier of the QoE measurement (hereinafter the second information) can coordinate the QoE configuration and reporting between the two RAN nodes (e.g., the MN and the SN) to avoid two different QoE measurements, for example, two different management-based QoE measurements with the same RRC identifier are configured to the same UE. Exemplary second information is an RRC identifier value range or a specific RRC identifier value of the QoE measurement used by the MN or the SN, or other related information. Information related to the RRC identifier for RVQoE measurement (hereinafter the third information) can coordinate RVQoE configuration and reporting between two RAN nodes (e.g., MN and SN) to avoid problems similar to those solved by the first information and the second information. Exemplary third information is a range of RRC identifier values ​​or a single RRC identifier value for RVQoE measurement used by the MN and / or SN or other related information. The first information, the second information, and the third information may be applied alone or in any combination in the embodiments of the present application to solve part or all of problems 1 to 3. That is, the embodiments of the present application may apply all of the first information, the second information, and the third information, or apply two of the first information, the second information, and the third information, or 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.

[0081] Some detailed embodiments of the present application will be described below in view of some exemplary NR-DC scenarios. Those skilled in the art should understand that although the MN and SN in NR-DC are described in the exemplary embodiments, the described technical solutions may also be applicable to similar RAN nodes and / or similar scenarios, and should not be limited to specific devices and scenarios. In addition, although different exemplary embodiments are described as focusing on different technical measures for the sake of clarity, those skilled in the art may combine the embodiments in various ways under the disclosure and teachings of the present application, although the combination is not explicitly described.

[0082] First, some embodiments of the present application which mainly consider Problem 1 are described below.

[0083] According to some embodiments of the present application (scenario 1), the UE will determine whether the two QoE measurement configurations (or configuration information) from the MN and the SN are repeated and ignore (or reject or cancel, etc.) one or both of the repeated QoE measurement configurations. Figure 2 is a flowchart of a QoE measurement collection procedure in scenario 1 according to some embodiments of the present application.

[0084] refer to Figure 2 , in step 201a, the RAN node acting as the MN may receive information indicating at least one QoE measurement. For example, the MN may receive QoE measurement activation information, which is a direct configuration from the OAM (e.g., in the case of management-based QoE measurement) or signaling from the OAM via the CN containing UE-associated QoE configuration (e.g., in the case of signaling-based QoE measurement). For management-based QoE measurement, the OAM will send one or more QoE measurement configurations to the RAN node. For signaling-based QoE measurement, the OAM will initiate QoE measurement activation for a specific UE via the CN node, and the CN node will send the 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:

[0085] -QoE Reference: It is used to identify the QoE measurement between gNB and CN or between gNB and OAM;

[0086] - Service Type: It indicates the service type of QoE measurement;

[0087] - Application layer measurement configuration container: it contains the application layer measurement configuration; and

[0088] - Area scope: The area scope for QoE measurement, which contains a list of cells, Tracking Area (TA), Tracking Area ID (TAI) or Public Land Mobile Network (PLMN).

[0089] Similarly, in step 201b, another RAN node acting as a 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). For management-based measurement, the SN may receive a QoE measurement configuration from the OAM, as described above in view of the MN, wherein the received QoE measurement configuration may be different from or the same as the QoE measurement configuration to the MN. For signaling-based QoE measurement, the MN will receive QoE measurement activation signaling from the OAM via the CN, and then request the SN to provide the QoE measurement configuration to the UE by, for example, transmitting the QoE measurement activation information in an S-node add request message or an S-node modify request message or the like. The MN may also include the UE QoE measurement capabilities 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 a driving test minimization (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., SRB3 for the requested QoE measurement) to the SN.

[0090] In this document, only management-based QoE measurement will be described in scenario 1 as an example to illustrate how to solve the problem caused by repeated QoE measurement configurations from MN and SN. It is assumed that MN and SN receive the same QoE measurement, for example, where the QoE reference is 1, and both MN and SN select the same UE with DC configuration for management-based QoE measurement. However, it should be clear to those skilled in the art that the described technical solution can also be applied to signaling-based QoE measurement.

[0091] Specifically, after receiving the QoE measurement, the MN will select a UE that satisfies the required QoE measurement, and allocate (or assign or configure, etc.) an RRC identifier (hereinafter, the MN RRC identifier) ​​to the QoE measurement, for example, measConfigAppLayerId is 2, and the RRC identifier is used to identify the QoE configuration of the QoE measurement between the MN and the UE, for example, the application layer measurement configuration of the QoE measurement between the MN and the UE (also referred to as the RRC QoE measurement configuration). Hereinafter, the QoE configuration of the QoE measurement 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 of the QoE measurement and the application layer measurement container. In step 203a, the MN will transmit the MN QoE configuration to the selected UE, for example, through RRC signaling (e.g., in AppLayerMeasConfig in the RRCReconfiguration message).

[0092] Similarly, the SN will select the same UE as the UE that meets the required QoE measurement after receiving the QoE measurement, where the QoE reference is 1, while independently allocating another RRC identifier (hereinafter the SN RRC identifier) ​​to the same QoE measurement, the other RRC identifier being the same as or different from the MN identifier, for example, measConfigAppLayerId 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 will transmit the SN QoE configuration of the QoE measurement to the selected UE, for example, via RRC signaling, for example, via SRB3. An exemplary SN QoE configuration of the QoE measurement includes the SN RRC identifier of the QoE measurement and an application layer measurement container.

[0093] From the perspective of the UE, it 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 or SCG branch). According to some embodiments of the present application, the UE will determine (or detect or identify, etc.) whether the QoE configuration from the MN and the QoE configuration from the SN are associated with the same QoE measurement, that is, whether the QoE configuration from the MN is repeated with the QoE configuration from the SN. If there are two repeated QoE configurations, the UE will ignore at least one of the two repeated QoE configurations. When ignoring only one QoE configuration, which of the repeated QoE configurations is ignored can be based on various criteria, such as the time when the QoE configuration reaches the application layer of the UE, etc.

[0094] Specifically, in Figure 2In the exemplary embodiment illustrated in FIG. 2 , the RRC layer of the UE will receive the MN QoE configuration from the MN in step 203a and the SN QoE configuration from the SN in step 203b, and then forward 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 the SN QoE configuration, the application layer will perform QoE measurement duplication detection (or determination or the like) in step 207 to detect whether the MN QoE configuration and the SN QoE configuration are duplicated, for example, by decoding the application layer measurement container in each QoE configuration. In the case where the application layer identifies that the two received application layer measurement containers are for the same QoE measurement, the application layer will make a decision that the two QoE configurations from the MN and the SN, respectively, are duplicated. In response to the decision that they are duplicates, the application layer will ignore one or both of the two duplicate QoE configurations. For example, the application layer may ignore the QoE configuration received later and perform QoE measurement according to the QoE measurement configuration received first.

[0095] The UE will generate repetition indication information (or QoE configuration repetition indication, etc.) through the application layer, for example, and transmit it to the network side. The QoE configuration repetition indication indicates that the QoE configurations from the MN and the SN are repeated. The QoE configuration repetition indication also indicates that one or both of the repeated QoE configurations are ignored, and includes a corresponding RRC identifier to identify the ignored QoE configuration.

[0096] Specifically, in Figure 2 In the exemplary embodiment described in , the application layer of the UE will send the QoE configuration repetition 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 will provide the SN RRC identifier, for example, 3, in the QoE configuration repetition indication, so that the RRC layer of the UE knows that the QoE configuration provided by the SN is ignored based on the RRC identifier being 3. If the MN QoE configuration is ignored, the application layer of the UE will provide the MN RRC identifier, for example, 2, in the QoE configuration repetition indication, so that the RRC layer of the UE knows that the QoE configuration provided by the MN is ignored based on the RRC identifier being 2. Then, the RRC layer of the UE will send the QoE configuration repetition indication to the network side.

[0097] In some embodiments of the present application, a QoE configuration repetition indication will be transmitted to the RAN node associated with the ignored QoE configuration. For example, in the case where the MN QoE configuration is ignored, the RRC layer of the UE will transmit a QoE configuration repetition indication with the MN RRC identifier to the MN in step 211a, for example, through SRB1, so that the MN knows that the MN QoE configuration is ignored by the UE because it is repeated. If the SN QoE configuration is ignored, the RRC layer of the UE will send a QoE configuration repetition indication with the SN RRC identifier to the SN in step 211b, for example, through SRB3, so that the SN knows that the SN QoE configuration is ignored by the UE because it is repeated. In the case where both repeated QoE configurations are ignored, the QoE configuration repetition indication will be transmitted to the MN and the SN, respectively. Both the MN RRC identifier and the SN RRC identifier may be included in each QoE configuration repetition indication to the MN and the SN, that is, the QoE configuration repetition indication to the MN and the SN is the same. In some other embodiments of the present application, the MNRRC identifier will be indicated only in the QoE configuration repetition indication to the MN and the SN RRC identifier will be indicated only in the QoE configuration repetition indication to the SN, that is, the QoE configuration repetition indications to the MN and the SN are independent of each other, which is similar to the operation when only one QoE configuration is ignored.

[0098] In some other embodiments of the present application, the UE will transmit the QoE configuration repetition indication only to the MN, regardless of whether the QoE configuration is ignored. If the SN QoE configuration is ignored (in the case where only one QoE configuration is ignored or in the case where both are ignored), the MN will transmit the received QoE configuration repetition indication to the SN in step 213. In the case where the MN receives the QoE configuration repetition indication with the MN RRC identifier and the SN RRC identifier, the MN may directly transmit the QoE configuration repetition indication to the SN or transmit the QoE configuration repetition indication with only the SN RRC identifier to the SN.

[0099] According to some other embodiments of the present application, in the case where only one of the MN QoE configuration and the SN QoE configuration is ignored, the QoE configuration repetition indication may also indicate the RRC identifier assigned for the QoE configuration that is not ignored. For example, in the case where the SN QoE configuration is ignored, the QoE configuration repetition indication to the SN will also indicate the MN RRC identifier, so that the SN can use the MN RRC identifier for RVQoE measurement. That is, the RRC identifier assigned by the RAN node for the QoE configuration that is not ignored may be transmitted to the peer RAN node of the RAN node whose QoE configuration is ignored, and the peer RAN node may determine the RRC identifier assigned by the RAN node as the third information, for example, the RVQoE RRC identifier, and use the third information when configuring the corresponding RVQoE measurement. Therefore, the solution described in view of scenario 1 can also solve the problem of the RRC identifier for RVQoE measurement.

[0100] According to some embodiments of the present application (scenario 2), after receiving information indicating at least one QoE measurement, the RAN node used as the SN will transmit a request (e.g., QoE configuration request information) to another RAN node used as the MN to request whether the indicated QoE measurement is allowed, so as to avoid the same QoE measurement being repeatedly configured by the MN and the SN to the UE. If the QoE measurement is not allowed, the SN will not transmit the QoE measurement to the UE. Figure 3 is a flowchart of a QoE measurement collection procedure in scenario 2 according to some embodiments of the present application.

[0101] refer to Figure 3 In step 301, the RAN node acting as a SN may receive information indicating at least one QoE measurement, which is Figure 2 The contents described in are the same as those described in and will not be repeated in this article. Figure 2 Receive information indicating at least one QoE measurement as described in, or do not receive it.

[0102] Similarly, only management-based QoE measurement will be described as an example in scenario 2 to illustrate how to solve the problem caused by repeated QoE measurement configurations from MN and SN. However, those skilled in the art should clearly know that the described technical solution can also be applied to signaling-based QoE measurement.

[0103] The SN will select a UE that satisfies the required QoE measurement. In step 303, the SN will transmit a QoE configuration request message to the MN to request whether the MN allows QoE measurement. One or more QoE measurements may be included in the same request. An exemplary QoE configuration request message includes at least one of a QoE reference, an area range, or a service type associated with the QoE measurement. In some embodiments of the present application, the QoE configuration request message may further include an SN RRC identifier assigned (or configured) by the SN. The QoE configuration request message may be carried in an S-NG-RAN node modification required message or the like.

[0104] After receiving the QoE configuration request information, the MN will decide whether to allow the requested QoE measurement (for example, including: whether the requested QoE measurement can be configured by the SN or whether the configuration of the QoE measurement is allowed), and then in step 305, for example, transmit a response (first information) to the SN via an S-NG-RAN node modification confirmation message or the like, indicating whether the requested QoE measurement is allowed or rejected.

[0105] In some cases, the MN may decide to allow the QoE measurements requested by the SN. For example, if the MN QoE configuration has not been configured to the UE or will not be configured to the UE by the MN, the MN may send a QoE configuration allow indication message to the SN. An exemplary QoE configuration allow indication message includes a QoE reference for indicating which QoE measurements the MN allows. The QoE configuration allow indication message may be included in an S-NG-RAN node modification confirmation message or the like.

[0106] After receiving the QoE configuration permission indication information, the SN will provide the SN QoE configuration for QoE measurement to the UE in step 207. In some embodiments of the present application, before transmitting the QoE configuration request information, the SN has not configured the SN QoE configuration for QoE measurement. After receiving the QoE configuration permission indication information, the SN will first configure the SN QoE configuration for QoE measurement and then transmit it to the UE.

[0107] In some other cases, the MN may decide to reject the requested QoE measurement. For example, if the MNQoE configuration for the QoE measurement has been configured to the UE or will be configured to the UE by the MN, then the MN may decide not to allow the requested QoE measurement. As another example, if the MN is not in the area range provided in the QoE configuration request information, then the MN will reject the QoE measurement. In response to the decision to not allow or reject the QoE measurement, the MN may send a QoE configuration rejection indication message to the SN to indicate that the requested QoE measurement is not allowed. The MN may also provide a reason value in the QoE configuration rejection indication message to indicate why the QoE measurement is rejected or not allowed, for example, because the QoE measurement has been configured to the UE by the MN or will be configured to the UE by the MN, or because the MN is not within the area range.

[0108] The solution described in view of scenario 2 may also solve the problem of the RRC identifier for RVQoE measurement. For example, in some embodiments of the present application, in the case where 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 for the corresponding RVQoE measurement (e.g., the RRC identifier for RVQoE measurement) when necessary. In the case where the requested QoE measurement is not allowed, the MN may also indicate the MN RRC identifier for 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 when necessary.

[0109] Compared with Scenario 1, the description of Scenario 2 is simplified to avoid unnecessary repetition. Those skilled in the art should clearly know that some similar or identical details described in Scenario 1 can also be applied to Scenario 2 in the same or similar manner.

[0110] According to some embodiments of the present application (scenario 3), after receiving information indicating at least one QoE measurement (e.g., M-based QoE measurement) and selecting a UE with a DC configuration, the RAN node acting as an MN or SN will send QoE measurement configuration indication information to a peer RAN node acting as an SN or MN, wherein the information indicates that the QoE measurement has been or will be configured by the RAN node for the UE to avoid the same QoE measurement being repeatedly configured by the peer RAN node for the UE. Figure 4 is a flowchart of a QoE measurement collection procedure under scenario 3 according to some embodiments of the present application. Figure 4 In the embodiments described in , the RAN node is a MN and the peer RAN node is a SN, but a person skilled in the art should clearly know how to apply a similar solution when the RAN node is a SN and the peer RAN node is a MN.

[0111] refer to Figure 4In step 401, the MN may receive information indicating at least one QoE measurement, which is similar to Figure 2 The contents regarding the RAN node serving as the MN are the same as those described in and will not be repeated herein.

[0112] Similarly, only management-based QoE measurement will be described as an example in scenario 3 to illustrate how to solve the problem caused by repeated QoE measurement configurations from MN and SN. However, those skilled in the art should clearly know that the described technical solution can also be applied to signaling-based QoE measurement.

[0113] The MN will select a UE that satisfies the required QoE measurement. In step 403, the MN may configure the QoE measurement and transmit it to the UE. The MN will transmit the QoE configuration indication information (first information) to the SN in step 405, indicating that the QoE measurement has been or will be configured by the MN for the UE. In some embodiments of the present application, the MN may transmit the QoE configuration indication information before transmitting the QoE measurement to the UE. The QoE configuration indication information may be carried in an S-NG-RAN node add request message or an S-NG-RAN node modify request message or the like. The exemplary QoE measurement configuration indication information includes a QoE reference for the QoE measurement.

[0114] After receiving the QoE measurement configuration indication information, the SN will know the M-based QoE measurement that has been configured or will be configured by the MN for the UE. The SN will not trigger the same M-based QoE measurement to the UE (if received), and therefore will not transmit repeated QoE measurements to the UE.

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

[0116] Similarly, the description of scenario 3 is simplified to avoid unnecessary repetition compared to scenario 1. It should be clear to those skilled in the art that some similar or identical details, specifically, information indicating QoE measurement described in scenario 1, can also be applied to scenario 3 in the same or similar manner.

[0117] According to some embodiments of the present application (scenario 4), a RAN node acting as a MN or SN will send a QoE configuration subscription request to a peer RAN node acting as a SN or MN to subscribe to the QoE measurements configured by the peer node. Figure 5is a flowchart of a QoE measurement collection procedure under scenario 4 according to some embodiments of the present application. Figure 5 In the embodiments described in , the RAN node is a MN and the peer RAN node is a SN, but a person skilled in the art should clearly know how to apply a similar solution when the RAN node is a SN and the peer RAN node is a MN.

[0118] refer to Figure 5 In step 501, the MN will transmit a QoE configuration subscription request to the SN to subscribe to the QoE measurement configured by the SN. An exemplary QoE configuration subscription request may indicate at least one QoE reference, for example, the QoE reference is 1.

[0119] In response to the QoE configuration subscription request, the SN will transmit a response (first information) to the MN in step 503, 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. For example, in the case where the SN configures one or more QoE measurements to the UE, the SN will report the QoE configuration addition indication to the MN. In the case where the SN releases one or more QoE measurements to the UE, the SN will report the QoE configuration release indication to the MN. In the case where the QoE reference is indicated in the QoE configuration subscription request, the SN will only report the addition or release of the QoE measurement associated with the indicated QoE reference. In the case where the QoE reference is not indicated in the QoE configuration subscription request, the SN will report the addition or release of any QoE measurement.

[0120] Based on the QoE configuration addition indication information and / or the QoE configuration release indication information, the RAN node will know which QoE measurement(s) have been configured for the UE, and will not configure the same QoE measurement for the UE, and thus will not transmit duplicate QoE measurements to the UE.

[0121] Similarly, the description of scenario 4 is simplified to avoid unnecessary repetition compared to scenario 1. It should be clear to those skilled in the art that some similar or identical details, specifically, information indicating QoE measurement described in scenario 1, can also be applied to scenario 4 in the same or similar manner.

[0122] In addition, some embodiments of the present application mainly considering Problem 2 are described below. Similarly, compared with Scenario 1, the description of the following scenarios is simplified to avoid unnecessary repetition. It should be clear to those skilled in the art that some similar or identical details, specifically, the information indicating the QoE measurement described in Scenario 1, can also be applied to the following in the same or similar manner.

[0123] According to some embodiments of the present application (scenario 5), the RAN node used as the MN will be responsible for the RRC identifier value range (second information), for example, the measConfigAppLayerId value range allocation for the QoE measurement from the MN or SN. For example, the entire value range of the RRC identifier, for example, measConfigAppLayerId is {0...63}. The MN may decide that the value range used by the MN is (0...31) and the value range used by the SN is (32...63), and vice versa. Since different RRC identifier value ranges are used by the MN and the SN, the QoE measurements from the MN and the SN will not be assigned the same RRC identifier. That is, problems caused by different QoE measurements with the same RRC identifier from the MN and the SN to the UE will be avoided.

[0124] The MN shall transmit information indicating the RRC identifier value range for QoE measurement to the SN, which may be transmitted by the MN proactively or in response to a request from the SN. For example, if the SN decides to configure QoE measurement, the SN may request the MN for the RRC identifier value range used by the SN.

[0125] An exemplary message or signaling for transmitting information indicating the RRC identifier value range is an S-NG-RAN node modification request message or an NG-RAN node addition request message or the like. The information may explicitly indicate the RRC identifier value range for QoE measurement used by the SN, for example, (32...63), or implicitly indicate the RRC identifier value range for QoE measurement used by the SN by indicating the RRC identifier value range for QoE measurement used by the MN (for example, (0...31)) or indicating both the RRC identifier value range used by the SN and the RRC identifier value range used by the MN (for example, both (0...31) and (32...63)).

[0126] When the MN or SN configures QoE measurements to the UE, it shall select an RRC identifier value within the corresponding value range. For example, when configuring an RRC identifier for QoE measurements triggered by the SN, the SN shall assign an RRC identifier for the QoE measurements within the value range used by the SN. If the RRC identifier value range, e.g., the measConfigAppLayerId range used by the SN, is not received from the MN, the SN shall not configure QoE measurements to the UE.

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

[0128] Similar to scenario 5, according to some embodiments of the present application (scenario 6), the RAN node acting as the MN will be responsible for allocating the RRC identifier value (second information), such as measConfigAppLayerId for the QoE measurement configured by the SN.

[0129] For example, after receiving a QoE measurement (e.g., a management-based QoE measurement), the SN may transmit a request to the MN for an RRC identifier for the QoE measurement, e.g., QoE measurement identifier required information. An exemplary request includes at least one of a QoE reference or a service type. After receiving the request, the MN will allocate an RRC identifier for the requested QoE measurement, e.g., measConfigAppLayerId, and transmit it to the SN. The SN will then use the RRC identifier indicated by the MN for QoE measurement.

[0130] In some embodiments of the present application, the SN may request an RRC identifier for QoE measurement in an implicit manner. For example, as described in Scenario 2, when the SN transmits a QoE configuration request message with the SN RRC identifier to the MN and the MN does not allow the requested QoE measurement because the same RRC identifier has been allocated by the MN to a different QoE measurement, the MN may indicate another RRC identifier for the QoE measurement used by the SN.

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

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

[0133] For example, in addition to measConfigAppLayerId, the independent RRC identifier (second information) may further include an index, wherein the index of the MN (also referred to as the MN index) and the index of the SN (also referred to as the SN index) are independent and different. Therefore, the QoE measurement from the MN and the SN to the UE can be uniquely identified according to the RRC identifier including the index and measConfigAppLayerId. Exemplary indexes, such as the MN index or the SN index, can be encoded in an enumeration type or a bit string type.

[0134] 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 will determine that the associated QoE measurement is configured by the SN. In some embodiments of the present application, a similar solution can also be applied to the MN.

[0135] Similarly, the solution described in view of scenario 7 may also solve the problem regarding the RRC identifier for RVQoE measurement. For example, specific information designed for the RRC identifier used by the SN may also be used by the SN as the third information for RVQoE measurement.

[0136] In addition, regarding RVQoE measurement, the following contents will be further described in addition to the above contents described in scenarios 1 to 7. Similarly, regarding QoE measurement associated with RV QoE measurement, the contents described in detail in scenario 1 may also be applied in the same or similar manner below.

[0137] According to some embodiments of the present application, the MN and the SN may configure separate or independent RVQoE configurations for signaling-based QoE measurement or management-based QoE measurement. How to coordinate the RVQoE configuration between the MN and the SN in two ways will be addressed. The described solution for RVQoE measurement can be applied independently of or in combination with the solution for solving problems 1 and 2.

[0138] In the case where RVQoE measurements (associated with signaling-based QoE measurements or management-based QoE measurements) are configured by the MN and SN, respectively, a problem similar to Problem 2 described above may occur. Therefore, the MN and SN may be coordinated to use the RRC identifier for RVQoE measurements as described in Scenarios 5 to 7 to resolve such problems.

[0139] For example, an exemplary solution is similar to the solution described in Scenario 5. For example, in addition to the embodiment described in Scenario 5, in some embodiments, the MN is responsible for the RRC identifier value range allocation for RVQoE measurement. When the RVQoE measurement is to be configured by the MN or the SN, it needs to select an RRC identifier within the corresponding value range. The MN will allocate a value range of the RRC identifier for the RVQoE measurement used by the SN. When the SN configures the RVQoE measurement to the UE, the SN will select an RRC identifier within the allocated value range. In the absence of the RRC identifier value range from the MN, the SN cannot configure the RVQoE measurement for the UE.

[0140] Another exemplary solution is similar to the solution described in scenario 6. For example, in addition to the embodiment described in scenario 6, in some embodiments, when triggered to configure RVQoE measurements to the UE, the SN will request the MN for an RRC identifier for RVQoE measurements, which may indicate at least one of a QoE reference or a service type. In response to the request, the MN will allocate an RRC identifier, such as measConfigAppLayerId for RVQoE measurements, and transmit it to the SN.

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

[0142] In the case where the MN and the SN can only configure one (single) RVQoE measurement of the same QoE measurement to the UE, when the RAN node (e.g., MN) has configured the QoE measurement to the UE, the peer node (e.g., SN) may also need to configure the RVQoE measurement to the UE for collecting the RVQoE measurement results. Therefore, the peer node needs to know the RRC identifier of the QoE measurement configured by the RVQoE measurement, which can be solved by the RAN node (spontaneously or in response to a request from the peer RAN node) transmitting the RRC identifier of the configured QoE measurement to its peer RAN node, or can be solved by a solution similar to the solution described in scenarios 1 to 3.

[0143] For example, an exemplary solution is similar to the solution described in Scenario 1. For example, in addition to the embodiment described in Scenario 1, in some embodiments, the application layer of the UE may provide the RRC identifier assigned to a RAN node for QoE measurement to the RRC layer of the UE in other messages or scenarios (e.g., receiving a signaling-based QoE measurement from a RAN node). The RRC layer of the UE will report the RRC identifier assigned by the RAN node for the QoE measurement to the peer RAN node, so that the peer RAN node knows the RRC identifier configured by the RAN node for the QoE measurement. Therefore, the peer RAN node can use the RRC identifier assigned by the RAN node for RVQoE configuration when necessary.

[0144] Another exemplary solution is similar to the solution described in Scenario 2. For example, in addition to the embodiment described in Scenario 2, in some embodiments, the SN may send a QoE configuration request message to the MN to request whether to allow QoE measurement, for example, signaling-based QoE measurement. In the case where the SN RRC identifier is included in the QoE configuration request message and the requested QoE measurement is allowed, the MN may also store the SN RRC identifier and use it as the RRC identifier for RVQoE measurement for the corresponding RVQoE measurement when necessary. In the case where the requested QoE measurement is not allowed, the MN may also indicate the MNRRC 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 when necessary.

[0145] Yet another exemplary solution is similar to the solution described in scenario 3. For example, in addition to the embodiment described in scenario 3, in some embodiments, a RAN node (e.g., MN) sends a QoE measurement configuration indication to a peer RAN node (e.g., SN) to indicate that a QoE measurement configuration (e.g., signaling-based QoE measurement) has been configured or will be configured to the UE. The MN may also include an RRC identifier for the QoE measurement assigned by the MN to the SN. The SN may use the RRC identifier assigned by the MN for RVQoE configuration when necessary.

[0146] In addition, for the RVQoE measurement results generated by the UE (eg, by the application layer of the UE), it is necessary to solve how the UE (eg, the RRC layer) selects a reporting branch, such as MCG or SCG.

[0147] In some embodiments of the present application, the RRC layer will select at least one branch based on the bearer type to report the RVQoE measurement results. In addition to the RVQoE measurement results, the application layer may also provide information of 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). In the case where at least one of the DRB, QoS flow, or PDU session is served by only one of the MCG (MCG bearer) or the SCG (SCG bearer), the RRC layer will report the RVQoE measurement results only to the corresponding ones of the MN and the SN. In the case where at least one of the DRB, QoS flow, or PDU session is served by both the MCG and the SCG, the RRC layer will report the RVQoE measurement results to both the MN and the SN.

[0148] In some other embodiments of the present application, the network will configure the RVQoE measurement result reporting branch to the UE, for example, reporting branch configuration information, which may be per DRB, QoS flow or PDU session, etc. The UE will select the reporting branch according to the configuration.

[0149] In addition to the method, embodiments of the present application also provide a device that supports QoE measurement collection. For example, Figure 6 is a block diagram of a device supporting QoE measurement collection according to some embodiments of the present application.

[0150] like Figure 6 As shown in FIG. 6 , apparatus 600 may include at least one non-transitory computer-readable medium 601, at least one receiving circuit system 602, at least one transmitting circuit system 604, and at least one processor 606 coupled to the non-transitory computer-readable medium 601, the receiving circuit system 602, and the transmitting circuit system 604. Apparatus 600 may be a RAN node or a terminal device (e.g., UE) configured to perform the method described above, or the like.

[0151] Although elements such as at least one processor 606, transmit circuit system 604, and receive circuit system 602 are described in the singular form in this figure, the plural form is considered unless it is explicitly stated to be limited to the singular form. In some embodiments of the present application, the receive circuit system 602 and the transmit circuit system 604 can be combined into a single device, such as a transceiver. The processor 606 can be a CPU, a DSP, a microprocessor, etc. In certain embodiments of the present application, the device 600 can further include an input device, a memory, and / or other components.

[0152] In some embodiments of the present application, a non-transitory computer-readable medium 601 may store thereon computer-executable instructions for causing a processor 606 to implement a method for a RAN node (e.g., the MN or SN described above). For example, when the computer-executable instructions are executed, the processor 606 interacts with the receiving circuit system 602 and the transmitting circuit system 604 to perform the steps described above for the RAN node.

[0153] In some embodiments of the present application, a non-transitory computer-readable medium 601 may store thereon computer-executable instructions for causing a processor to implement the method described above with respect to a terminal device. For example, when the computer-executable instructions are executed, the processor 606 interacts with the receiving circuit system 602 and the transmitting circuit system 604 to perform the steps described above with respect to the UE.

[0154] Figure 7 A block diagram illustrating an apparatus 700 supporting QoE measurement reporting according to some other embodiments of the present application.

[0155] refer to Figure 7, the apparatus 700 (e.g., 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 receive circuit system 706 and transmit circuit system 708 or at least one integrated receive circuit system 706 and transmit circuit system 708. The at least one processor 702 may be a CPU, a DSP, a microprocessor, etc.

[0156] According to some embodiments of the present application, when the device 700 is a RAN node (e.g., MN or SN), the processor is configured to: receive information indicating at least one QoE measurement; and determine information associated with the configuration of at least one QoE measurement, wherein the information associated with the configuration of at least one QoE measurement includes at least one of the following: first information related to whether the same QoE measurement is configured to the UE by the MN or the SN; second information related to the RRC identifier of the QoE measurement; or third information related to the RRC identifier of the RVQoE measurement.

[0157] According to some other embodiments of the present application, when the device 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 transmit repetition 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 repetition indication information indicates that at least one of the first QoE configuration information or the second QoE configuration information is ignored because the first QoE configuration information and the second QoE configuration information are repeated for the QoE measurement.

[0158] The method according to the embodiment of the present application may also be implemented on a programmed processor. However, the controller, flow chart and module may also be implemented on a general or special purpose computer, a programmed microprocessor or microcontroller and peripheral integrated circuit elements, an integrated circuit, a hardware electronic or logic circuit (such as a discrete element circuit), a programmable logic device or the like. In general, any device capable of implementing the flow chart shown in the figure can be used to implement the processor function of the present application. For example, an embodiment of the present application provides an apparatus comprising a processor and a memory. Computer programmable instructions for implementing a method are stored in a memory, and the processor is configured to execute the computer programmable instructions to implement the method. The method may be the method described above or other methods according to the embodiment of the present application.

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

[0160] Although the present disclosure has been described with reference to specific embodiments of the present application, it is apparent that many substitutions, modifications, and variations may be apparent to those skilled in the art. For example, the various components of the embodiments may be interchanged, added, or substituted in other embodiments. Moreover, all elements of each figure are not necessary for the operation of the disclosed embodiments. For example, it will enable a person of ordinary skill in the field of the disclosed embodiments to make and use the teachings of the present application by simply adopting the elements of the independent claims. Therefore, the embodiments of the present application set forth herein are intended to be illustrative rather than restrictive. Various changes may be made without departing from the spirit and scope of the present application.

Claims

1. A user equipment UE, comprising: Transceiver; and a processor coupled to the transceiver, wherein the processor is configured to: 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; and In response to the first QoE configuration information and the second QoE configuration information being associated with the same QoE measurement, repetition indication information is transmitted to at least one of the first RAN node or the second RAN node, wherein the repetition indication information indicates that at least one of the first QoE configuration information or the second QoE configuration information is ignored because the first QoE configuration information and the second QoE configuration information are repeated for the QoE measurement.

2. The UE according to claim 1, wherein in the case where RAN visible QoE RVQoE measurement configuration information is also received, the radio resource control RRC layer of the UE will select at least one branch of the master node MN and the secondary node SN to report the RVQoE measurement result.

3. A radio access network RAN ​​node, comprising: Transceiver; and a processor coupled to the transceiver, wherein the processor is configured to: receiving information indicating at least one quality of experience (QoE) measurement; and Determine information associated with the configuration of the at least one QoE measurement, wherein the information associated with the configuration of the at least one QoE measurement comprises at least one of: first information related to whether the same QoE measurement is configured to the user equipment UE by a master node MN or a secondary node SN; second information related to a radio resource control RRC identifier of the QoE measurement; or third information related to an RRC identifier of a RAN visible QoE RVQoE measurement.

4. The RAN node of claim 3, wherein the RAN node is a MN and the peer node is a SN, and the processor is configured to: receiving, from the SN, a QoE configuration request message for requesting whether to allow QoE measurement; and The first information is transmitted to the SN in response to the QoE configuration request information, wherein the first information is QoE configuration allowance indication information indicating that the QoE measurement is allowed or QoE configuration reject indication information indicating that the QoE measurement is rejected.

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

6. The RAN node of claim 3, wherein the processor is configured to: The first information is transmitted to a peer node, wherein the first information is QoE measurement configuration indication information indicating that QoE measurement has been or will be configured by the RAN node for the UE.

7. The RAN node of claim 3, wherein the processor is configured to: transmitting a QoE configuration subscription request to a peer node to subscribe to QoE measurements configured by the peer node; and The first information is received from the peer node, wherein the first information is QoE configuration addition indication information indicating configuration of QoE measurement for the UE or QoE configuration release indication information indicating release of QoE measurement for the UE.

8. The RAN node of claim 3, wherein the RAN node is a MN and the peer node is a SN, and the processor is configured to: The second information is transmitted to the SN, wherein the second information indicates a range of RRC identifier values ​​for QoE measurements used by the SN.

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

10. The RAN node of claim 3, wherein the processor is configured to transmit the second information to a UE, and In case the RAN node is a MN, the second forming a measConfigAppLayerId and a MN index indicating QoE measurements configured by the MN for the UE; and In case the RAN node is a SN, the second formation indicates measConfigAppLayerId and an SN index of the QoE measurement configured by the SN for the UE.

11. The RAN node of claim 3, wherein the RAN node is a MN and the peer node is a SN, and the processor is configured to: The third information is transmitted to the SN, wherein the third information indicates a range of RRC identifier values ​​for RVQoE measurements used by the SN.

12. The RAN node of claim 3, wherein the RAN node is a SN and the peer node is a MN, and the processor is configured to: The third information is received from the MN, and the third information indicates a range of RRC identifier values ​​for RVQoE measurements used by the SN.

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

14. The RAN node according to claim 3, wherein the processor is configured to transmit the third information to a UE, and In the case where the RAN node is a MN, the third information indicates a measConfigAppLayerId and a MN index configured by the MN for RVQoE measurement of the UE; and In the case where the RAN node is a SN, the third information indicates measConfigAppLayerId and an SN index configured by the SN for RVQoE measurement of the UE.

15. The RAN node according to claim 3, wherein in a case where repetition indication information indicating that the QoE configuration information from the RAN node is ignored due to being repeated with other QoE configuration information for the same QoE measurement is received from the UE, the processor is configured to determine the RRC identifier of the other QoE configuration information received together with the repetition indication information as the third information, to be used by the RAN node for corresponding RVQoE measurement.

Images