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

By receiving and reporting QoE measurement identification information during the initial context setting program of the UE in the wireless communication system, the problem of QoE measurement collection and reporting in the RRC_IDLE state is solved, ensuring the identification and reporting of QoE measurement results from RRC_IDLE to RRC_CONNECTED state, Improved the quality experience monitoring and optimization capabilities of MBS and other services.

CN119032584APending Publication Date: 2024-11-26LENOVO (BEIJING) LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280094664.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-05-26
Publication Date
2024-11-26

AI Technical Summary

Technical Problem

Existing wireless communication systems cannot effectively support the collection and reporting of quality experience (QoE) measurements in the RRC_IDLE state, especially for multicast/broadcast services (MBS), resulting in the user equipment (UE) returning to the RRC_CONNECTED state from the RRC_IDLE state. , QoE measurement results cannot be correctly identified and reported.

Method used

By receiving the first identification information of the QoE measurement from the CN node during the initial context setting procedure of the UE, and receiving and reporting the second identification information of the QoE measurement when the UE transitions from the RRC idle state to the RRC connection state, combining the RAN node with the UE with the UE The QoE measurement configuration and reporting information between the two ensure that the QoE measurement results can be correctly identified and reported when the UE returns the RRC_CONNECTED status.

Benefits of technology

It realizes effective collection and reporting of QoE measurements in the RRC_IDLE state, supports quality experience monitoring and optimization of MBS and other services, and improves the user experience quality of wireless communication systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119032584A_ABST
    Figure CN119032584A_ABST
Patent Text Reader

Abstract

The embodiment of the invention relates to a method and equipment for supporting quality of experience (QoE) measurement collection. An exemplary method may include receiving first identification information of a QoE measurement from a core network (CN) node during an initial UE context setting procedure of a user equipment (UE); receiving a report of the QoE measurement and second identification information of the QoE measurement from the UE transitioning from a radio resource control (RRC) idle state to an RRC connected state; and identifying the report of the QoE measurement according to the first identification information and the second identification information.
Need to check novelty before this filing date? Find Prior Art

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 used 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 (e.g., time, frequency, and power). Examples of wireless communication systems may include fourth generation (4G) systems, such as long term evolution (LTE) systems, advanced LTE (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, basic mechanisms for NR QoE are specified. However, only QoE measurement configuration and reporting in the Radio Resource Control (RRC)_CONNECTED state (or RRC connected state) is supported in Rel-17. Support for QoE measurement settings and reporting in the RRC_IDLE state, for example, for multicast / broadcast services (MBS), is expected to be addressed in Rel-18. For example, for QoE measurements in the RRC_IDLE state (or RRC idle state), it is necessary to address how the gNB identifies the QoE measurement report when the user equipment (UE) returns to the RRC_CONNECTED state.

[0004] In view of the above, the industry desires techniques to support QoE measurement collection in RRC_IDLE state, for example, for MBS. Summary of the invention

[0005] One object of an embodiment of the present application is to provide a technical solution to support QoE measurement collection, for example, a method and device to support QoE measurement collection in the RRC_IDLE state.

[0006] Some embodiments of the present application provide a radio access network (RAN) node, such as a gNB, comprising: a transceiver; and a processor coupled to the transceiver, wherein the processor is configured to: receive first identification information of QoE measurements from a CN node during an initial UE context setup procedure of the UE; receive a report of the QoE measurements and second identification information of the QoE measurements from the UE that transitions from an RRC idle state to an RRC connected state; and identify the report of the QoE measurements based on the first identification information and the second identification information.

[0007] In some embodiments of the present application, both the first identification information and the second identification information include information identifying a QoE measurement configuration and report between a RAN node and a UE. According to some embodiments of the present application, the first identification information may further include information identifying a QoE measurement configuration between a RAN node and a CN or between a RAN node and an operation, administration and maintenance (OAM), and the information identifying the QoE measurement configuration between the RAN node and the CN or between the RAN node and the OAM is associated with the information identifying the QoE measurement configuration and report between the RAN node and the UE. An example of the information identifying the QoE measurement configuration and report between the RAN node and the UE is a measurement configuration application layer identifier (ID).

[0008] In some embodiments of the present application, both the first identification information and the second identification information include information identifying a QoE measurement configuration between a RAN node and a CN or between a RAN node and an OAM. An example of the information identifying a QoE measurement configuration between a RAN node and a CN or between a RAN node and an OAM is a QoE reference.

[0009] In some embodiments of the present application, before the UE transitions to the RRC idle state, the first identification information is transmitted to the CN, and before the UE transitions to the RRC idle state, the second identification information is transmitted to the UE.

[0010] In some embodiments of the present application, before the UE transitions to the RRC idle state, information indicating the QoE measurement performed by the UE in the RRC idle state is transmitted to the UE.

[0011] In some embodiments of the present application, during the UE context release procedure, information indicating the QoE measurements performed by the UE in the RRC idle state is also transmitted to the CN node.

[0012] In some embodiments of the present application, the RAN node is a serving gNB of the UE or a receiving gNB of the UE.

[0013] Some other embodiments of the present application provide a UE, comprising: a transceiver; and a processor coupled to the transceiver, wherein the processor is configured to cooperate with the transceiver to: receive information indicating QoE measurements performed by the UE in the RRC idle state from a first RAN node before the UE transitions to the RRC idle state; and after the UE transitions from the RRC idle state to the RRC connected state, transmit a report of the QoE measurements and identification information of the QoE measurements to a second RAN node, wherein the first RAN node is the same as or different from the second RAN node.

[0014] In some embodiments of the present application, the processor is configured to: receive the identification information of the QoE measurement before the UE transitions to the RRC idle state.

[0015] In some embodiments of the present application, the identification information of the QoE measurement includes information identifying the QoE measurement configuration and report between the RAN node and the UE. An example of the information identifying the QoE measurement configuration and report between the RAN node and the UE is a measurement configuration application layer ID.

[0016] In some embodiments of the present application, the identification information of the QoE measurement includes information identifying a QoE measurement configuration between a RAN node and a CN or between a RAN node and an OAM. An example of the information identifying a QoE measurement configuration between a RAN node and a CN or between a RAN node and an OAM is a QoE reference.

[0017] In some embodiments of the present application, both the first RAN node and the second RAN node are serving gNBs for the UE; or the first RAN node is the last serving gNB for the UE, and the second RAN node is the receiving gNB for the UE.

[0018] Some other embodiments of the present application provide a CN node comprising: a transceiver; and a processor coupled to the transceiver, wherein the processor is configured to cooperate with the transceiver to: receive identification information of QoE measurements from a first RAN node during a UE context release procedure of releasing a UE to an RRC idle state; and transmit the identification information of the QoE measurements to a second RAN node during an initial UE context setup procedure of the UE, wherein the first RAN node and the second RAN node are the same or different.

[0019] In some embodiments of the present application, the identification information of the QoE measurement includes information identifying a QoE measurement configuration and report between a RAN node and a UE. According to some embodiments of the present application, the identification information of the QoE measurement further includes information identifying a QoE measurement configuration between a RAN node and a CN or between a RAN node and an OAM, and the information identifying the QoE measurement configuration between a RAN node and a CN or between a RAN node and an OAM is associated with the information identifying a QoE measurement configuration and report between a RAN node and a UE. An example of the information identifying a QoE measurement configuration and report between a RAN node and a UE is a measurement configuration application layer ID.

[0020] In some embodiments of the present application, the identification information of the QoE measurement includes information identifying a QoE measurement configuration between a RAN node and a CN or between a RAN node and an OAM. An example of the information identifying a QoE measurement configuration between a RAN node and a CN or between a RAN node and an OAM is a QoE reference.

[0021] In some embodiments of the present application, during the UE context release procedure, information indicating the QoE measurements performed by the UE in the RRC idle state is also received.

[0022] In some embodiments of the present application, both the first RAN node and the second RAN node are serving gNBs for the UE; or the first RAN node is the last serving gNB for the UE, and the second RAN node is the receiving gNB for the UE.

[0023] The embodiments of the present application provide a technical solution to support QoE measurement collection, for example, a method and device to support QoE measurement collection for MBS or the like in RRC idle state. Therefore, the present application can promote and improve the implementation of NR. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0026] Figure 2 is a flow chart illustrating a method of supporting QoE measurement collection according to some embodiments of the present application.

[0027] Figure 3An exemplary procedure for QoE measurement collection according to some embodiments of the present disclosure is described.

[0028] Figure 4 Another exemplary procedure for QoE measurement collection according to some other embodiments of the present disclosure is described.

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

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

[0031] The detailed description of the accompanying drawings is intended as a description of the preferred embodiments of the present application, but 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 implemented by different embodiments that are intended to be included in the spirit and scope of the present application.

[0032] 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 Long Term Evolution (LTE), etc.). It should be considered that, with the development of network architectures and new service scenarios, all embodiments in the present application are also applicable to similar technical problems. In addition, the terms cited in the present application may change, which should not affect the principles of the present application.

[0033] Figure 1 A schematic diagram illustrating an exemplary wireless communication system 100 in accordance with some embodiments of the present application.

[0034] As in Figure 1 As shown in FIG. 1 , the wireless communication system 100 includes at least one BS 101 and at least one UE 102. Specifically, for illustrative purposes, the wireless communication system 100 includes one BS 101 and two terminal devices 102 (eg, a first UE 102a and a second UE 102b). Although for simplicity, Figure 1 A specific number of BSs and terminal devices are illustrated in FIG. 1 , but it is considered that in some other embodiments of the present application, the wireless communication system 100 may include more or fewer BSs and terminal devices.

[0035] The wireless communication system 100 is compatible with any type of network capable of sending and receiving wireless communication signals. For example, the wireless communication system 100 is compatible with wireless communication networks, cellular telephone networks, networks based on time division multiple access (TDMA), networks based on code division multiple access (CDMA), networks based on orthogonal frequency division multiple access (OFDMA), LTE networks, networks based on 3GPP, 3GPP 5G networks, satellite communication networks, high altitude platform networks, and / or other communication networks.

[0036] BS101 may communicate with a CN node (not shown) via an interface, such as a mobility management entity (MME) or a serving gateway (S-GW), an access and mobility management function (AMF), or a user plane function (UPF), etc. BS may also be referred to as an access point, an access terminal, a base station, a macro cell, a Node B, an enhanced Node B (eNB), a gNB, a home Node B, a relay node or a device, or described using other terms used in the art. In 5G NR, a BS may also refer to a RAN node. Each BS may serve several UEs within a service area (e.g., a cell or a cell sector) via a wireless communication link. Neighbor BSs may communicate with each other as needed, for example, during a handover procedure of a UE.

[0037] The terminal device (or remote device) 102 (e.g., the first UE 102a and the second UE 102b) 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 vehicle onboard computer, a network device (e.g., a router, a switch and a modem), or the like. According to an embodiment of the present application, the terminal device 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 receiver, or any other device capable of sending and receiving communication signals on a wireless network. In some embodiments, the terminal device may include a wearable device, such as a smart watch, a fitness band, an optical head-mounted display, or the like. In addition, the terminal device 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. In this document (throughout the specification), although "UE" is exemplarily used as a classic terminal device for explaining a terminal device, it should be understood as any type of terminal device.

[0038] In 3GPP Rel-17, the basic mechanisms for NR QoE are specified. For example, regarding QoE measurement collection activation and reporting, TS38.300 specifies the following:

[0039] “Features are activated in NG-RAN by direct configuration from the OAM system (management-based activation) or by signalling from OAM via the core network (containing UE-associated QoE configuration) (signaling-based activation).

[0040] One or more QoE measurement collection tasks may be activated at the UE per service type, and each QoE measurement configuration is uniquely identified by a QoE reference.

[0041] For signaling-based QoE measurements, OAM initiates QoE measurement activation for a specific UE via the core network, and the NG-RAN node receives one or more QoE measurement configurations via UE-associated signaling. The QoE measurement configuration for signaling-based activation 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 an indication of available RAN-visible QoE metrics. Each application layer measurement configuration is encapsulated in a transparent container. The NG-RAN node forwards the corresponding QoE measurement configuration to the UE in a downlink RRC message containing AppLayerMeasConfig, as specified in TS 38.331

[12] .

[0042] For management-based QoE measurement activation, OAM sends one or more QoE measurement configurations to the NG-RAN node.

[0043] The QoE measurement configuration for management-based activation 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.

[0044] The UE reports QoE measurement results to the NG-RAN node in an uplink RRC message, as specified in TS 38.331

[12] .

[0045] The NG-RAN node transmits the QoE report and the corresponding QoE reference ID to the MCE.

[0046] 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 an 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 report 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.

[0047] The gNB may release one or more application layer measurement configurations from the UE in an RRCReconfiguration message at any time. The UE may additionally be configured by the gNB to report when a QoE measurement session for a certain application layer measurement configuration is started or stopped.

[0048] Therefore, QoE Measurement Collection (QMC, also known as QoE Measurement) 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 as an application layer configuration in the RRCReconfiguration message (multiple configurations can 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 can be enabled by the gNB.

[0049] TS 38.300 also specifies QoE measurement continuity for mobility as follows:

[0050] “QoE measurement collection continuity for intra-RAT mobility within the system is supported through the area scope parameter configured by OAM, where the network is responsible for tracking whether the UE is within or outside the area scope. The UE shall continue ongoing measurements even if it leaves the area scope unless the network instructs the UE to release the QoE configuration.

[0051] For RRC_CONNECTED state mobility, the source NG-RAN node may transmit the QoE measurement configuration and / or information related to the configuration of a specific UE to the target NG-RAN node via XnAP or NGAP. For signaling-based QoE, the QoE reference, MCE IP address, measurement configuration application layer ID, MDT alignment information, area range, slice range, and measurement status are passed to the target node. For management-based QoE, the measurement configuration application layer ID, MCE IP address, and measurement status are passed to the target node. For RRC_INACTIVE state mobility, when a specific UE is restored to the RRC_CONNECTED state, the QoE measurement configuration for the specific UE may be restored from the node hosting the UE context. Multiple sets of QoE measurement configurations should be supported during mobility.

[0052] For signaling-based QoE, when switching to a target gNB that supports QoE, the target gNB decides which application layer measurement configurations to retain and which to release, for example based on the application layer measurement configuration information received from the source gNB in ​​Xn / NG signaling.

[0053] When the UE resumes connection in a gNB that does not support QoE, the UE releases all application layer measurement configurations.

[0054] It can be seen that the QoE measurement configuration and measurement report supported in the RRC_IDLE state have not been specified in Rel-17. However, for some services, such as MBS services (i.e. broadcast and multicast), QoE measurement collection in the RRC_IDLE state is also important. Therefore, Rel-18 will address the support for QoE measurement configuration and reporting in the RRC_IDLE state, such as for MBS, as agreed in 3GPP RP-213159:

[0055] -Specify QoE measurement configuration and collection in RRC_INACTIVE and RRC_IDLE states for MBS (at least for broadcast services). [RAN3, RAN2]

[0056] The issues to be resolved include but are not limited to: Considering that when the UE transitions to the RRC idle state, the UE context and RRC configuration are released on the gNB side, when the UE returns to the RRC connected state and reports the QoE measurement results, how does the gNB identify the QoE measurement report.

[0057] At least to support QoE measurement collection in the RRC idle state, the embodiments of the present application provide a technical solution to support QoE measurement collection, especially a method and device to support QoE measurement collection in the RRC idle state.

[0058] For example, some embodiments of the present application provide a method that can be performed by a RAN node, such as a serving gNB or a receiving gNB or the like. The exemplary method includes: receiving first identification information of QoE measurement from a CN node during an initial UE context setup procedure of the UE; receiving a report of QoE measurement and second identification information of QoE measurement from a UE transitioning from an RRC idle state to an RRC connected state; and identifying the report of QoE measurement according to the first identification information and the second identification information.

[0059] Some other embodiments of the present application provide another method that can be performed by a UE or the like. The exemplary method includes: receiving information indicating QoE measurements performed by the UE in the RRC idle state from a first RAN node before the UE transitions to the RRC idle state; and transmitting a report of the QoE measurements and identification information of the QoE measurements to a second RAN node after the UE transitions from the RRC idle state to the RRC connected state. The first RAN node and the second RAN node are the same or different. For example, when no cell reselection occurs, the first RAN node and the second RAN node are the same and both are serving gNBs for the UE; or when cell reselection occurs due to UE mobility in the RRC idle state, the first RAN node is the last serving gNB for the UE and the second RAN node is the receiving gNB for the UE.

[0060] Some other embodiments of the present application provide yet another method, which may be performed by a CN node, such as an AMF or the like. The exemplary method includes: receiving identification information of QoE measurements from a first RAN node during a UE context release procedure that releases the UE to an RRC idle state; and transmitting identification information of QoE measurements to a second RAN node during an initial UE context setup procedure of the UE. Similarly, when no cell reselection occurs, the first RAN node and the second RAN node are the same and both are serving gNBs for the UE; or different when cell reselection occurs, wherein the first RAN node is the last serving gNB for the UE and the second RAN node is a receiving gNB for the UE.

[0061] Figure 2 The method is a flowchart illustrating a method for supporting QoE measurement collection according to some embodiments of the present application. Although the method is described in the system level among a CN node (e.g., AMF) in the CN side, at least one RAN node (e.g., NG-RAN node) in the RAN side (e.g., a serving gNB when no cell reselection occurs, or the last serving gNB and receiving gNB when cell reselection occurs), and a UE or the like on the remote side; Those skilled in the art should understand that the method implemented in the CN node (or CN side, or CN), the RAN node (or the RAN side or the gNB side or the NG-RAN) and the UE (or the UE side or the remote side) can be implemented separately and / or combined by other devices with similar functions.

[0062] refer to Figure 2 Due to the UE mobility in the RRC idle state, two scenarios are considered, namely, a scenario without cell reselection and a scenario with cell reselection. In the scenario without cell reselection (hereinafter also referred to as the first scenario), only one RAN node is described, such as gNB1, which is the serving gNB of the UE. In the scenario with cell reselection (hereinafter also referred to as the "second scenario"), two RAN nodes are described, such as gNB1 and gNB2, where gNB1 is the last serving gNB of the UE (also referred to as: anchor gNB or old serving gNB or old gNB or the like), and gNB2 is the receiving gNB of the UE (also referred to as: new serving gNB or new gNB or the like). That is, the difference between the two scenarios is that, due to the UE mobility in the second scenario, the UE returns the RAN node to which the RRC_CONNECTED state changes.

[0063] In the first scenario or the second scenario, when sending the UE to the RRC idle state, gNB1 may configure the UE to perform QoE measurement collection in the RRC idle state. Therefore, in step 201, the UE will receive information indicating the QoE measurement performed by the UE in the RRC idle state (hereinafter also referred to as "indication of QoE measurement in the RRC idle state") from gNB1 before the UE transitions to the RRC idle state. For example, the indication of QoE measurement in the RRC idle state is transmitted from gNB1 and received by the UE in a downlink RRC message (e.g., an RRC release message that releases the UE to the RRC idle state) or in an RRC reconfiguration message.

[0064] In some cases, before transitioning to the RRC idle state, the UE has been performing QoE measurement collection in the RRC connected state. The UE may continue to use the configuration information for QoE measurement provided by gNB1 in the RRC connected state (hereinafter also referred to as "RRCQoE measurement configuration information", which is configured by the gNB side to the UE side). The gNB side may configure the RRC QoE measurement configuration information in response to QoE measurement (or QoE measurement collection) being activated by direct configuration from OAM (not shown) (i.e., management-based activation) or by signaling (containing UE-associated QoE configuration) from OAM via CN (i.e., signaling-based activation).

[0065] For management-based QoE measurement activation, OAM sends one or more QoE measurement configurations to a RAN node, such as gNB1. For signaling-based QoE measurement, OAM initiates QoE measurement activation for a specific UE via a CN node; and the CN node sends QoE measurement configuration information to gNB1 for QoE measurement activation. Exemplary QoE measurement configuration information from CN or OAM (also referred to as "CN / OAM QoE measurement configuration information") includes:

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

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

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

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

[0070] Regarding the QoE reference, it may be a QoE reference as defined in clause 5.2 of TS28.405, which is an octet string with SIZE (6). The QoE reference consists of a Mobile Country Code (MCC), a Mobile Network Code (MNC), and a QMC ID, wherein the MCC and MNC are included with a trace activation request from the management system to identify a PLMN containing the management system, and the QMC ID is a 3-byte octet string.

[0071] Based on the QoE measurement information from CN or OAM, the gNB shall provide the corresponding RRC QoE measurement configuration to the UE in a downlink RRC message containing the application layer measurement configuration (e.g., AppLayerMeasConfig), which includes:

[0072] -MeasConfigAppLayerId: measurement configuration application layer ID, which is used to identify the application layer measurement configuration and reporting between the gNB and the UE; and

[0073] -Container of application layer measurement configuration: It contains application layer measurement configuration.

[0074] Regarding the measurement configuration application layer ID, it may be the measurement configuration application layer ID as defined in TS 38.331 and is an integer (0..61,...).

[0075] It should be apparent to those skilled in the art that the above information elements (IEs) or parameters are merely described as examples, which may change with the evolution of 3GPP specifications and therefore should not be used to unduly limit the protection scope of the present application.

[0076] In some other embodiments of the present application, regardless of whether the UE performs QoE measurement in the RRC connected state, gNB1 may provide the UE with new RRC QoE measurement configuration information (which may be the same as the RRC QoE measurement configuration information used in the RRC connected state), which may be transmitted to the UE together with the indication of the QoE measurement in the RRC idle state, or may be transmitted to the UE separately from the indication of the QoE measurement in the RRC idle state. For example, gNB1 may also include new RRC QoE measurement configuration information for the UE in an RRC release message or an RRC reconfiguration message separate from the RRC release message. In the case where gNB1 sends new RRC QoE measurement configuration information for the UE during the procedure of releasing the UE into the RRC idle state, the indication of the QoE measurement in the RRC idle state may be implied in this manner, and no explicit indication may be transmitted to the UE.

[0077] In response to the indication of QoE measurement in the RRC idle state, the UE will use or continue to use the RRCQoE measurement configuration to perform QoE measurement in the RRC idle state. When the UE returns to the RRC connected state, in step 203, the UE will report the QoE measurement results in the RRC idle state to the serving gNB in ​​the absence of cell reselection, and report the QoE measurement results in the RRC idle state to the receiving gNB in ​​the case of cell reselection. The UE also transmits identification information of the QoE measurement to the serving gNB or the receiving gNB. For example, in step 203a, in the first scenario, after the UE transitions from the RRC idle state to the RRC connected state, the UE will transmit a report of the QoE measurement and identification information of the QoE measurement (or referred to as "report identification information of the QoE measurement") to gNB1. In another example, in step 203b, in the second scenario, after the UE transitions from the RRC idle state to the RRC connected state, the UE will transmit a report of the QoE measurement and identification information of the QoE measurement to gNB2.

[0078] The identification information of QoE measurement is diverse and is transmitted to both the UE side and the CN side before the UE transitions to the RRC idle state. Therefore, the UE and CN nodes will store the received identification information of the QoE measurement respectively. For example, the identification information of the QoE measurement is information that identifies the QoE measurement configuration and report between the RAN node and the UE (hereinafter also referred to as "RRC QoE measurement identification information"), such as the measurement configuration application layer ID. In another example, the identification information of the QoE measurement is information that identifies the QoE measurement configuration between the RAN node and the CN or between the RAN node and the OAM (hereinafter also referred to as "CN / OAM QoE measurement identification information"), such as a QoE reference. gNB1 can obtain the QoE reference from the CN / OAM QoE measurement configuration information, and then transmit it to both the UE side and the CN side before the UE transitions to the RRC idle state. In some other embodiments of the present application, the identification information of the QoE measurement transmitted to the UE side and the CN side respectively may be different, but associated with each other, and the gNB can still identify the QoE measurement report by associating them.

[0079] Specifically, for the UE side, similar to the indication of the QoE measurement in the RRC idle state, identification information of the QoE measurement may be received from gNB1 in various ways, such as RRC QoE measurement identification information or CN / OAM QoE measurement identification information. For example, in the case of a measurement configuration application layer ID, the identification information of the QoE measurement may be received in the RRC QoE measurement configuration information. In another instance, the identification information of the QoE measurement may be received in the same RRC reconfiguration message in which the RRC QoE measurement configuration information is transmitted, such as in the case of a QoE reference. In yet another instance, the identification information of the QoE measurement may be received in an RRC message separate from the RRC message in which the RRC QoE measurement configuration information is transmitted to the UE, such as in an RRC release message in the case of a QoE reference.

[0080] For CN, it is relatively simple. In step 202, during the UE context release procedure to release the UE to the RRC idle state, for example, in a UE context release request message or a UE context release complete message, identification information of QoE measurement, such as RRC QoE measurement identification information or CN / OAM QoE measurement identification information, may be received from gNB1, which also implies an indication of QoE measurement in the RRC idle state to the CN node. In some other embodiments of the present application, in addition to the QoE measurement identification information, gNB1 may also transmit an indication of QoE measurement in the RRC idle state to the CN node to explicitly indicate to the CN node that the UE is configured to perform QoE measurement in the RRC idle state.

[0081] When the UE requests to return to the RRC connected state, in response to the RRC setup procedure between the RAN side and the UE side, there will be an initial UE context setup procedure of the UE between the RAN side and the CN side, wherein the stored identification information of the QoE measurement, such as the RRC QoE measurement identification information or the CN / OAM QoE measurement identification information, will be transmitted from the CN side to the RAN side in step 204. Considering the UE mobility in the RRC idle state, the UE may request RRC reconnection to gNB1 in the first scenario, or request RRC reconnection to gNB2 in the second scenario. In step 204a, the CN node will transmit the stored identification information of the QoE measurement to gNB1 during the initial UE context setup procedure in the first scenario, or in step 204b, transmit the stored identification information of the QoE measurement to gNB2 during the initial UE context establishment procedure in the second scenario.

[0082] Therefore, in the RAN side, in step 205, the RAN node may identify the QoE measurement report received from the UE according to the QoE measurement identification information from the CN and the QoE measurement identification information from the UE. For example, in the first scenario, in step 205a, gNB1 may identify the received report of the QoE measurement according to the QoE measurement identification information from the CN and the QoE measurement identification information from the UE. In the second scenario, in step 205b, gNB2 may identify the received report of the QoE measurement according to the QoE measurement identification information from the CN and the QoE measurement identification information from the UE.

[0083] A more detailed embodiment of the present application will be described below in view of different identification information for identifying the QoE measurement reported by the UE in the RRC idle state. In addition, for simplicity, the UE mobility in the RRC idle state is not considered in the following embodiments, that is, only the embodiment in the first scenario is described. Since the difference between the first scenario and the second scenario is only the change of the gNB caused by the UE mobility in the RRC idle state, a person skilled in the art can be familiar with how to perform the QoE measurement based on the first scenario. Figure 2 The disclosed content and teachings of the following embodiments are used to apply the illustrated solution in the first scenario to the second scenario.

[0084] According to some embodiments of the present application, RRC QoE measurement identification information is used to at least identify a report of QoE measurement performed by the UE in the RRC idle state, which will be transmitted by the gNB to the UE side and the CN side respectively before the gNB sends the UE to the RRC idle state. Both the UE side and the CN side will store the RRC QoE measurement identification information. The CN node will send the stored RRC QoE measurement identification information to the gNB during the initial UE context setup procedure of the UE. The UE also transmits the stored RRC QoE measurement identification information to the gNB together with the QoE measurement report. Therefore, the gNB can identify the QoE measurement report based on the RRC QoE measurement identification information from the CN and the UE.

[0085] Figure 3 An exemplary procedure of QoE measurement collection according to some embodiments of the present application is described, wherein RRC QoE measurement identification information is used to at least identify a report of QoE measurement performed by a UE in an RRC idle state.

[0086] refer to Figure 3 In response to activating QoE measurement by direct configuration from OAM or by signaling from OAM via CN (containing UE-associated QoE configuration), the gNB will provide RRC QoE measurement configuration information to the UE before the UE transitions from the RRC connected state to the RRC idle state in step 301. The RRC QoE measurement configuration information includes a measurement configuration application layer ID, such as MeasConfigAppLayerId, which is used as RRC QoE measurement identification information to identify the QoE measurement configuration and reported between the gNB and the UE. The UE will store the RRC QoE measurement configuration information including the RRC QoE measurement identification information, and may perform QoE measurement collection in the RRC connected state accordingly.

[0087] In the case where the gNB decides to configure the UE to perform QoE measurement in the RRC idle state, the gNB will send an indication of the QoE measurement in the RRC idle state to the UE in a downlink RRC message, such as an RRC release message or an RRC reconfiguration message to the UE in step 303. In some other embodiments of the present application, the indication of the QoE measurement in the RRC idle state may be transmitted to the UE together with the RRC QoE measurement configuration information, such as in the RRC release message or the RRC reconfiguration message or the like.

[0088] On the other hand, after the gNB decides to configure the UE to perform QoE measurement in the RRC idle state, the gNB will also provide the CN node with identification information of the QoE measurement, which is the same as or associated with the identification information of the QoE measurement to the UE. For example, the gNB also provides the CN node (e.g., AMF) with RRC QoE measurement identification information, which is the same as the information provided to the UE (e.g., MeasConfigAppLayerId). In step 305, the gNB may transmit the RRC QoE measurement identification information to the CN node during the UE context release procedure, which releases the UE from the RRC connected state to the RRC idle state. The RRC QoE measurement identification information may be included in a UE context release request message or a UE context release complete message to the CN node. In some embodiments of the present application, the gNB may transmit the entire RRC QoE measurement configuration information including the RRC QoE measurement identification information to the CN node.

[0089] The RRC QoE measurement identification information to the CN node also implies that the UE is configured to perform QoE measurements in the RRC idle state. However, in some other embodiments of the present application, in addition to providing the RRC QoE measurement identification information to the CN node, the gNB may also provide the CN node with an indication of QoE measurements in the RRC idle state, which explicitly indicates to the CN node that the UE is configured to perform QoE measurements in the RRC idle state. The indication of QoE measurements in the RRC idle state may be transmitted to the CN node together with or separately from the RRC QoE measurement identification information, for example, in both a UE context release request message or a UE context release complete message to the CN node.

[0090] In some other embodiments of the present application, the gNB may also transmit CN / OAM QoE measurement identification information, such as QoE reference, to the CN node during the UE context release procedure. Similarly, in some cases, the gNB may transmit the entire CN / OAM QoE measurement configuration information including the CN / OAM QoE measurement identification information to the CN node.

[0091] Unlike the previous technology, the UE will not release the RRC QoE measurement configuration information. Instead, in step 307, the UE will store (or continue to store) the RRC QoE measurement configuration information with the RRC QoE measurement identification information in the RRC idle state, and accordingly perform (or continue to perform) QoE measurement in the RRC idle state based on the RRC QoE measurement configuration information.

[0092] For example, when the UE enters the RRC_IDLE state, the RRC layer of the UE will indicate to the upper layer of the UE (higher than the RRC layer, such as the application layer) that the UE is in the RRC_IDLE state and configures the QoE measurement in RRC_IDLE. The RRC layer may also provide RRC QoE measurement identification information, such as MeasConfigAppLayerId, to the upper layer. The upper layer of the UE will store the MeasConfigAppLayerId for QoE measurement. In some other embodiments of the present application, the RRC layer instead of the upper layer of the UE will store the RRC QoE measurement identification information, or even the entire RRC QoE measurement configuration information including the RRC QoE measurement identification information.

[0093] When the UE requests to return to the RRC Connected state via the RRC Setup procedure between the UE and the gNB, the CN node will provide the stored RRC QoE measurement identification information, such as MeasConfigAppLayerId, to the gNB during the initial UE context setup procedure between the gNB and the CN node, such as in the Initial UE Context Setup Request message in step 309. In the case where the CN node stores the entire RRC QoE measurement configuration information, the CN node may transmit the entire RRC QoE measurement configuration information or only the RRC QoE measurement identification information to the gNB.

[0094] During the initial UE context setup procedure, the CN node may also transmit to the gNB the stored CN / OAM QoE measurement identity information associated with the RRC QoE measurement identity information, such as the QoE reference associated with MeasConfigAppLayerId. Similarly, in the case where the CN node stores the entire CN / OAM QoE measurement configuration information, the CN node may transmit to the gNB the entire CN / OMA QoE measurement configuration information or only the RRC QoE measurement identity information.

[0095] After returning to the RRC connected state, the UE will report the QoE measurement results with the RRC QoE measurement identification information, such as MeasConfigAppLayerId, in step 311. In step 313, the gNB will identify the QoE measurement report based on the RRCQoE measurement identification information from the CN node and the UE to determine which QoE measurement the QoE measurement report is for. The gNB may further map the QoE measurement report with the CN / OAM QoE measurement configuration information (e.g., received QoE reference) received from the CN node. Therefore, the gNB will know which QoE measurement the QoE measurement report is for, and send the QoE measurement report of the QoE measurement to OAM directly or via the CN node.

[0096] According to some other embodiments of the present application, CN / OAM QoE measurement identification information instead of RRC QoE measurement identification information is used to at least identify a report of QoE measurement performed by the UE in the RRC idle state, which report will be transmitted by the gNB to the UE side and the CN side respectively before the gNB sends the UE into the RRC idle state. Both the UE side and the CN side will store the CN / OAM QoE measurement identification information. The CN node will send the stored CN / OAM QoE measurement identification information to the gNB during the initial UE context setup procedure of the UE. The UE also transmits the stored CN / OAM QoE measurement identification information together with the QoE measurement report to the gNB. Therefore, the gNB can identify the QoE measurement report based on the CN / OAM QoE measurement identification information from the CN and the UE.

[0097] Figure 4 Another exemplary procedure of QoE measurement collection according to some other embodiments of the present application is described, wherein the CN / OAM QoE measurement identification information is used to at least identify the report of the QoE measurement performed by the UE in the RRC idle state.

[0098] refer to Figure 4 In step 401, based on the CN / OAM QoE measurement information, the gNB will provide the UE with RRC QoE measurement configuration information before the UE transitions from the RRC connected state to the RRC idle state. The RRC QoE measurement configuration information includes a measurement configuration application layer ID, such as MeasConfigAppLayerId, which is used to identify the application layer measurement configuration and reporting between the gNB and the UE. The UE will store the RRC QoE measurement configuration information and perform QoE measurement and reporting in the RRC connected state accordingly.

[0099] In the case where the gNB decides to configure the UE to perform QoE measurement in the RRC idle state, the gNB will send an indication of the QoE measurement in the RRC idle state to the UE in a downlink RRC message, such as an RRC release message to the UE, in step 403. In some other embodiments of the present application, the indication of the QoE measurement in the RRC idle state may be transmitted to the UE together with the RRC QoE measurement configuration information, such as in the RRC release message or in the RRC reconfiguration message.

[0100] In order to identify the report of the QoE measurement performed in the RRC idle state, the gNB will also transmit CN / OAM QoE measurement identification information, such as a QoE reference, to the UE before the UE transitions to the RRC idle state. The CN / OAM QoE measurement identification information may be transmitted to the UE together with or separately from at least one of the indication of the QoE measurement in the RRC idle state and the RRC QoE measurement configuration information. In some embodiments of the present application, the gNB may transmit the entire CN / OAM QoE measurement configuration information including the QoE reference to the UE.

[0101] On the other hand, after the gNB decides to configure the UE to perform QoE measurements in the RRC idle state, the gNB will also provide the CN node with identification information for the QoE measurements, which is the same as or associated with the identification information for the QoE measurements to the UE. For example, the gNB also provides the CN node (e.g., AMF) with CN / OAM QoE measurement identification information, which is the same as the information provided to the UE (i.e., QoE reference). In step 405, the gNB may transmit the CN / OAM QoE measurement identification information to the CN node during the UE context release procedure, which releases the UE from the RRC connected state to the RRC idle state. The CN / OAM QoE measurement identification information may be included in a UE context release request message or a UE context release complete message to the CN node. In some embodiments of the present application, the gNB may transmit the entire CN / OAM QoE measurement configuration information including the CN / OAM QoE measurement identification information to the CN node.

[0102] The CN / OAM QoE measurement identification information to the CN node also implies that the UE is configured to perform QoE measurements in the RRC idle state. However, in some other embodiments of the present application, in addition to providing the CN / OAM QoE measurement identification information to the CN node, the gNB may also provide the CN node with an indication of QoE measurements in the RRC idle state, thereby explicitly indicating to the CN node that the UE is configured to perform QoE measurements in the RRC idle state. The indication of QoE measurements in the RRC idle state may be transmitted to the CN node together with or separately from the CN / OAM QoE measurement identification information in both a UE context release request message or a UE context release complete message to the CN node.

[0103] Similarly, the UE will not release the RRC QoE measurement configuration information and the CN / OAM QoE measurement identification information. Instead, in step 407, the UE will store (or continue to store) the RRC QoE measurement configuration information and the CN / OAM QoE measurement identification information in the RRC idle state, and accordingly perform QoE measurement in the RRC idle state based on the RRC QoE measurement configuration information.

[0104] For example, when the UE enters the RRC_IDLE state, the RRC layer of the UE will indicate to the upper layer of the UE (higher than the RRC layer, such as the application layer) that the UE is in the RRC_IDLE state and configures the QoE measurement in RRC_IDLE. The RRC layer may also provide the upper layer with CN / OAM QoE measurement identification information, such as a QoE reference. The upper layer of the UE will store the QoE reference for QoE measurement. In some other embodiments of the present application, the RRC layer instead of the upper layer of the UE will store the CN / OAM QoE measurement identification information, or even the entire CN / OAM QoE measurement configuration information including the CN / OAM measurement identification information.

[0105] When the UE requests to return to the RRC connected state via the RRC setup procedure between the UE and the gNB, the CN node will provide the stored CN / OAM QoE measurement identification information, such as the QoE reference, to the gNB during the initial UE context setup procedure between the gNB and the CN node, such as in the initial UE context setup request message in step 409. In the case where the CN node stores the entire CN / OAM QoE measurement configuration information, the CN node may transmit the entire RRC QoE measurement configuration information or only the CN / OAM QoE measurement identification information to the gNB.

[0106] After returning to the RRC connected state, in step 411, the UE will report the QoE measurement result including the CN / OAM QoE measurement identification information, such as the QoE reference. In step 413, the gNB will identify the QoE measurement report according to the CN / OAM QoE measurement identification information from the CN node and the UE to determine which QoE measurement the QoE measurement report is for. Therefore, the gNB will send the QoE measurement report of the QoE measurement to OAM directly or via the CN node.

[0107] In addition to the method, embodiments of the present application also propose a device that supports QoE measurement collection. Figure 5 is a block diagram of a device supporting QoE measurement collection according to some embodiments of the present application.

[0108] refer to Figure 5 , the device 500 (e.g., UE or RAN node or CN node) may include at least one processor 502 and at least one transceiver 504. The transceiver 504 may include at least one separate receive circuit system 506 and transmit circuit system 508, or at least one integrated receive circuit system 506 and transmit circuit system 508. The at least one processor 502 may be a CPU, a DSP, a microprocessor, etc.

[0109] According to some embodiments of the present application, when the device 500 is a RAN node (e.g., a serving gNB or a receiving gNB), the processor is configured to: receive first identification information of QoE measurement from a CN node during an initial UE context setup procedure of the UE; receive a report of QoE measurement and second identification information of QoE measurement from a UE that transitions from an RRC idle state to an RRC connected state; and identify the report of QoE measurement based on the first identification information and the second identification information.

[0110] According to some other embodiments of the present application, when the device 500 is a UE, the processor may be configured to: receive information indicating QoE measurements performed by the UE in the RRC idle state from a first RAN node before the UE transitions to the RRC idle state; and transmit a report of the QoE measurements and identification information of the QoE measurements to a second RAN node after the UE transitions from the RRC idle state to the RRC connected state, wherein the first RAN node is the same as or different from the second RAN node.

[0111] According to some other embodiments of the present application, when the device 500 is a CN node, the processor may be configured to: receive identification information of QoE measurement from a first RAN node during a UE context release procedure of releasing the UE to an RRC idle state; and transmit identification information of QoE measurement to a second RAN node during an initial UE context setup procedure of the UE, wherein the first RAN node and the second RAN node are the same or different.

[0112] For example, Figure 6 A block diagram illustrating an apparatus 600 supporting QoE measurement reporting according to some other embodiments of the present application.

[0113] As in Figure 6 As shown, the 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. The apparatus 600 may be a RAN node or a terminal device (e.g., UE) or a CN node configured to perform the method described above or the like.

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

[0115] In some embodiments of the present application, the non-transitory computer-readable medium 601 may store computer-executable instructions thereon to cause the processor 606 to implement the method described above with respect to a RAN node (e.g., a serving gNB or a receiving gNB). 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 RAN node.

[0116] In some other embodiments of the present application, the non-transitory computer-readable medium 601 may store computer-executable instructions thereon to enable the processor to implement the method for the UE as 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 for the UE as described above.

[0117] In some other embodiments of the present application, the non-transitory computer-readable medium 601 may store computer-executable instructions thereon to enable the processor to implement the method for the CN node as 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 for the CN node as described above.

[0118] The method according to the embodiment of the present application case can also be implemented on a programmed processor. However, the controller, flow chart and module can 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 case. For example, an embodiment of the present application case provides a device including a processor and a memory. Computer programmable instructions for implementing the 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 a method as stated above or other methods according to an embodiment of the present application case.

[0119] 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 can 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 in which computer programmable instructions are stored. The computer programmable instructions are configured to implement the method as stated above or other methods according to the embodiments of the present application.

[0120] Although the present application has been described with 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, in other embodiments, the various components of the embodiments may be interchangeable, added or replaced. In addition, all elements of each diagram are not necessary for the operation of the disclosed embodiments. For example, a person of ordinary skill in the art of the disclosed embodiments will be able 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 radio access network RAN ​​node, comprising: Transceiver; and a processor coupled to the transceiver, wherein the processor is configured to cooperate with the transceiver to: During an initial UE context setup procedure of a user equipment UE, receiving first identification information of a quality of experience (QoE) measurement from a core network (CN) node; Receiving the QoE measurement report and the second identification information of the QoE measurement from the UE that has transitioned from a radio resource control (RRC) idle state to an RRC connected state; as well as The report of the QoE measurement is identified according to the first identification information and the second identification information.

2. The RAN node according to claim 1, wherein: Both the first identification information and the second identification information include information identifying the QoE measurement configuration and report between the RAN node and the UE.

3. The RAN node according to claim 2, wherein: The first identification information further includes information identifying the QoE measurement configuration between the RAN node and the CN or between the RAN node and the operation administration and maintenance OAM, and the information identifying the QoE measurement configuration between the RAN node and the CN or between the RAN node and the OAM is associated with the information identifying the QoE measurement configuration and report between the RAN node and the UE.

4. The RAN node according to claim 2 or claim 3, wherein: The information identifying the QoE measurement configuration and report between the RAN node and the UE is a measurement configuration application layer identifier ID.

5. The RAN node according to claim 1, wherein: Both the first identification information and the second identification information include information identifying a QoE measurement configuration between a RAN node and a CN or between a RAN node and an operations administration and maintenance OAM.

6. The RAN node according to claim 3 or claim 5, wherein: The information identifying the QoE measurement configuration between the RAN node and the CN or between the RAN node and the OAM is a QoE reference.

7. The RAN node according to claim 1, wherein: Before the UE transitions to the RRC idle state, the first identification information is transmitted to the CN, and before the UE transitions to the RRC idle state, the second identification information is transmitted to the UE.

8. A user equipment UE, comprising: Transceiver; and a processor coupled to the transceiver, wherein the processor is configured to cooperate with the transceiver to: receiving, before the UE transitions to a radio resource control (RRC) idle state, information indicating quality of experience (QoE) measurements performed by the UE in the RRC idle state from a first radio access network (RAN) node; as well as After the UE transitions from the RRC idle state to the RRC connected state, the report of the QoE measurement and the identification information of the QoE measurement are transmitted to a second RAN node, wherein the first RAN node is the same as or different from the second RAN node.

9. The UE according to claim 8, wherein: The processor is configured to: The identification information of the QoE measurement is received before the UE transitions to the RRC idle state.

10. The UE according to claim 8, wherein: The identification information of the QoE measurement includes information identifying the QoE measurement configuration and report between the RAN node and the UE.

11. The UE according to claim 10, wherein: The information identifying the QoE measurement configuration and report between the RAN node and the UE is a measurement configuration application layer identifier ID.

12. The UE according to claim 8, wherein: The identification information of the QoE measurement includes information identifying the QoE measurement configuration between the RAN node and the core network CN or between the RAN node and the operation administration and maintenance OAM.

13. The UE according to claim 12, wherein: The information identifying the QoE measurement configuration between the RAN node and the CN or between the RAN node and the OAM is a QoE reference.

14. A core network CN node, comprising: Transceiver; and a processor coupled to the transceiver, wherein the processor is configured to cooperate with the transceiver to: receiving identification information of a quality of experience (QoE) measurement from a first radio access network (RAN) node during a UE context release procedure for releasing the user equipment (UE) to a radio resource control (RRC) idle state; as well as The identification information of the QoE measurement is transmitted to a second RAN node during an initial UE context setup procedure of the UE, wherein the first RAN node and the second RAN node are the same or different.

15. The CN node according to claim 14, wherein: The identification information of the QoE measurement includes information identifying the QoE measurement configuration and report between the RAN node and the UE.