Methods and apparatus for supporting the collection of Quality of Experience (QoE) measurements.

Abstract

Embodiments of the present disclosure relate to a method and apparatus for supporting QoE measurement collection. An exemplary method may include transmitting, to a UE, first information indicating a configuration of at least one set of QoE measurements, where each set of QoE measurements includes one or more QoE measurement values for the same service type, and different sets of QoE measurements are for different service types; and in response to an inter-RAT handover to a target RAN node, transmitting, to the UE, second information indicating a configuration of at least one QoE measurement, where the at least one QoE measurement is selected from at least one set of QoE measurements, and different QoE measurement values of the at least one QoE measurement are for different service types.

Description

[[Technical Field]]

[0001] Embodiments of the present application generally relate to wireless communication technology, and in particular to a method and apparatus supporting quality of experience (QoE) measurement collection (also referred to as QMC, QoE, QoE measurement, QoE measurement collection job, etc.). [[Background Art]]

[0002] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. Wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of wireless communication systems may include fourth generation (4G) systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems sometimes referred to as New Radio (NR) systems.

[0003] In 3GPP (registered trademark) Release (Rel)-17, basic mechanisms for NR QoE, such as basic mechanisms for triggering, configuration, collection, mobility support and reporting of QoE measurement, are specified. However, only QoE measurement collection continuity for intra-system intra-radio access technology (RAT) mobility is supported in Rel-17. It is expected that support for QoE measurement collection continuity for intra-system inter-RAT mobility will be implemented in Rel-18.

[0004] Therefore, there is a need in the industry for techniques for supporting QoE measurement collection continuity for intra-system inter-RAT mobility. [[Summary of the Invention]] [[Problem to be Solved by the Invention]]

[0005] One object of the embodiments of this application is to provide a technical solution that supports QoE measurement acquisition, for example, a method and apparatus that supports QoE measurement acquisition continuity for inter-RAT mobility within a system. [Means for solving the problem]

[0006] Some embodiments of the present application provide a radio access network (RAN) node, for example, a gNB, which includes a processor and a transceiver coupled to the processor, wherein the transceiver is configured to transmit to a user device (UE) first information indicating the configuration of at least one set of QoE measurements, each set of QoE measurements including one or more QoE measurements for the same service type, and different sets of QoE measurements for different service types, and to transmit to the UE, in response to an inter-RAT handover to a target RAN node, second information indicating the configuration of at least one QoE measurement, where at least one QoE measurement is selected from at least one set of QoE measurements, and different QoE measurements of the at least one QoE measurement are for different service types.

[0007] In some embodiments of the present application, the transceiver is further configured to receive information from or via the OAM system via the core network (CN) indicating the continuity of QoE measurements after an inter-RAT handover, wherein at least one QoE measurement is selected based on the information indicating the continuity of QoE measurements after an inter-RAT handover.

[0008] According to some embodiments of this application, the information indicating QoE measurement continuity after an inter-RAT handover indicates which QoE measurements for a service type will continue after the inter-RAT handover, or indicates the continuity priority of each QoE measurement for a service type after the inter-RAT handover. If there is only one QoE measurement in the set of QoE measurements, the information indicating QoE measurement continuity after an inter-RAT handover is the service type.

[0009] According to some embodiments of this application, the transceiver is configured to transmit information indicating the continuity of QoE measurement after an inter-RAT handover to a UE having first information.

[0010] According to some embodiments of this application, the transceiver is configured to transmit information indicating the continuity of QoE measurement after an inter-RAT handover to a UE having second information.

[0011] According to some embodiments of the present application, a processor is configured to select at least one QoE measurement based on information indicating QoE measurement continuity, and a transceiver is configured to transmit third information indicating only the configuration of at least one QoE measurement to a target RAN node and to receive second information indicating the configuration of at least one QoE measurement from the target RAN node, wherein the configuration of at least one QoE measurement indicated in the second information is generated or updated based on the configuration of at least one QoE measurement indicated in the third information. Each configuration of at least one QoE measurement indicated in the second information is identified by a corresponding service type.

[0012] According to some embodiments of the present application, the transceiver is configured to transmit to a target RAN node third information indicating the configuration of at least one set of QoE measurements and information indicating the continuity of QoE measurements after an inter-RAT handover, and to receive from the target RAN node second information indicating the configuration of at least one QoE measurement, wherein the configuration of at least one QoE measurement indicated in the second information is generated or updated based on the configuration of at least one set of QoE measurements indicated in the third information. The exemplary third information further includes a measurement configuration application layer identifier assigned by the RAN node to the UE for each configuration of the at least one set of QoE measurements, and the second information further includes a measurement configuration application layer identifier for each configuration of the at least one QoE measurement. In one example, the transceiver is configured to receive information indicating a QoE measurement to be released from the target RAN node and to transmit information indicating a QoE measurement to be released to the UE. In another example, the transceiver is configured to receive information from the target RAN node indicating that the QoE measurement should be continued, and to transmit information to the UE indicating that the QoE measurement should be continued. In yet another example, a third piece of information, and information indicating the continuity of the QoE measurement after the RAT handover, is sent to the target RAN node via a handover request message or via a source-target transparent container.

[0013] In some embodiments of this application, the transceiver is configured to transmit information to the UE indicating QoE measurement continuity after a RAT handover by indicating that it is releasing the other QoE measurements of at least one set of QoE measurements, excluding at least one QoE measurement.

[0014] In some embodiments of this application, the RAN node is a gNB and the target RAN node is an ng-eNB.

[0015] In some embodiments of this application, the configuration of at least one set of QoE measurements shown in the first information is located in a first RAT, and the configuration of at least one QoE measurement shown in the second information is located in a second RAT different from the first RAT.

[0016] Some embodiments of the present application provide a RAN node, for example, an ng-eNB, which includes a processor and a transceiver coupled to the processor, the transceiver being configured to receive, in response to an inter-RAT handover, first information from a source RAN node indicating the configuration of at least one set of QoE measurements, each set of QoE measurements including one or more QoE measurements for the same service type, and different sets of QoE measurements for different service types, and to transmit to the source RAN node second information indicating the configuration of at least one QoE measurement, where at least one QoE measurement is selected from at least one set of QoE measurements, and different QoE measurements of the at least one QoE measurement are for different service types.

[0017] In some embodiments of the present application, a transceiver is configured to receive information from a source RAN node indicating the continuity of QoE measurements after an inter-RAT handover, and the transceiver is configured to select at least one QoE measurement from at least one set of QoE measurements based on the information indicating the continuity of QoE measurements after an inter-RAT handover.

[0018] According to some embodiments of this application, information indicating the continuity of QoE measurements after an inter-RAT handover indicates which QoE measurements for a service type will continue after the inter-RAT handover, or indicates the continuity priority of each QoE measurement for a service type after an inter-RAT handover.

[0019] In some embodiments of this application, the configuration of at least one QoE measurement shown in the second information is generated or updated based on the configuration of at least one set of QoE measurements shown in the first information.

[0020] In some embodiments of this application, the transceiver is configured to transmit information to the source RAN node indicating a QoE measurement that should be released.

[0021] In some embodiments of this application, the transceiver is configured to transmit information to the source RAN node indicating that the QoE measurement should be continued.

[0022] In some embodiments of this application, information indicating the continuity of QoE measurement after a RAT handover is received from the source RAN node via a handover request message or via a source-target transparent container.

[0023] In some embodiments of this application, the RAN node is an ng-eNB and the source RAN node is a gNB.

[0024] In some embodiments of the present application, the first information further includes a measurement configuration application layer identifier assigned by a RAN node to the UE of each configuration of at least one set of QoE measurements, and the second information further includes a measurement configuration application layer identifier for each configuration of at least one QoE measurement.

[0025] In some embodiments of this application, the configuration of at least one set of QoE measurements shown in the first information is located in a first RAT, and the configuration of at least one QoE measurement shown in the second information is located in a second RAT different from the first RAT.

[0026] Some embodiments of the present application provide a RAN node, for example, an ng-eNB, comprising a processor and a transceiver coupled to the processor, wherein the transceiver is configured to, in response to inter-RAT handover, transmit, to a target RAN node, information indicating at least one QoE measurement and information indicating that the at least one QoE measurement is configured for a UE having first RAT identification information, wherein different QoE measurement values of the at least one QoE measurement correspond to different service types; receive, from the target RAN node, second RAT identification information and information associating the at least one QoE measurement with the second RAT identification information; and transmit, to the UE, the second RAT identification information and the information associating the at least one QoE measurement with the second RAT identification information.

[0027] In some embodiments of the present application, the first RAT identification information is a service type, and the second RAT identification information is a measurement configuration application layer identifier.

[0028] In some embodiments of the present application, the information associating the at least one QoE measurement with the second RAT identification information is implicitly indicated by the second RAT identification information.

[0029] In some embodiments of the present application, the RAN node is an ng-eNB, and the target RAN node is a gNB.

[0030] Some embodiments of the present application provide a RAN node, for example, a gNB, which includes a processor and a transceiver coupled to the processor, wherein the transceiver is configured to receive from a source RAN node in response to an inter-RAT handover information indicating at least one QoE measurement and information indicating that at least one QoE measurement is configured for a UE having first RAT identification information, wherein different QoE measurements of the at least one QoE measurement are for different service types, and transmit to the source RAN node information relating to second RAT identification information and at least one QoE measurement identified by the first RAT identification information to the second RAT identification information.

[0031] In some embodiments of this application, the RAN node is a gNB and the source RAN node is an ng-eNB.

[0032] Some embodiments of the present application provide a remote device, for example, a UE, comprising a processor and a transceiver coupled to the processor, wherein the transceiver is configured to receive first information from a RAN node indicating the configuration of at least one set of QoE measurements, each set of QoE measurements comprising one or more QoE measurements for the same service type, and different sets of QoE measurements for different service types, and to receive second information from a RAN node in response to a RAT handover from the RAN node to a target RAN node, indicating the configuration of at least one QoE measurement, where at least one QoE measurement is selected from at least one set of QoE measurements, and different QoE measurements of the at least one QoE measurement are for different service types.

[0033] In some embodiments of the present application, the transceiver is further configured to receive information indicating the continuity of QoE measurement after an inter-RAT handover, along with at least one of the first or second pieces of information, and to continue at least one QoE measurement after an inter-RAT handover based on the information indicating the continuity of QoE measurement after an inter-RAT handover.

[0034] In some embodiments of this application, the transceiver is configured to receive information indicating that in response to an inter-RAT handover, the other QoE measurements of at least one set of QoE measurements should be released, excluding at least one QoE measurement, and the processor is configured to release the other QoE measurements of at least one set of QoE measurements.

[0035] In some embodiments of the present application, the transceiver is configured to receive information indicating that at least one QoE measurement should be continued in response to an inter-RAT handover, and the processor is configured to continue at least one QoE measurement after the inter-RAT handover.

[0036] According to some embodiments of this application, when information indicating the continuity of QoE measurement after an inter-RAT handover is received along with the first information, each configuration of at least one QoE measurement shown in the second information is identified by the corresponding service type.

[0037] According to some embodiments of this application, when information indicating QoE measurement continuity after an inter-RAT handover is received together with second information, the information indicating QoE measurement continuity after an inter-RAT handover is indicated by a measurement application layer identifier included in the second information, and the measurement application layer is assigned by the source RAN node.

[0038] In some embodiments of this application, the configuration of at least one set of QoE measurements shown in the first information is located in a first RAT, and the configuration of at least one QoE measurement shown in the second information is located in a second RAT different from the first RAT.

[0039] In consideration of the foregoing, embodiments of the present application provide at least a technical solution to support QoE measurement collection, for example, a method and apparatus to support QoE measurement collection continuity for intrasystem RAT mobility, the technical solution considering both scenarios from a source RAN node supporting two or more QoE measurements per service type to a target RAN node supporting only one QoE measurement per service type, and scenarios from a source RAN node supporting only one QoE measurement per service type to a target RAN node supporting two or more QoE measurements per service type. Thus, the present application can facilitate and improve the implementation of NRs.

[0040] To describe the forms in which the advantages and features of this application can be obtained, this description of the application is made by reference to specific embodiments of this application shown in the accompanying drawings. These drawings illustrate only exemplary embodiments of this application and are therefore not intended to limit its scope. [Brief explanation of the drawing]

[0041] [Figure 1] This figure shows a wireless communication system according to several embodiments of the present application. [Figure 2] This flowchart shows a method for supporting QoE measurement acquisition in Scenario 1 according to several embodiments of the present application. [Figure 3] This flowchart shows a method for supporting QoE measurement and acquisition using Method 1 in Scenario 1, according to several embodiments of this application. [Figure 4]This flowchart shows a method for supporting QoE measurement and acquisition using Method 2 in Scenario 1, according to several other embodiments of this application. [Figure 5] This flowchart shows a method for supporting QoE measurement acquisition in Scenario 2, according to some embodiments of the present application. [Figure 6] This is a block diagram of an apparatus supporting QoE measurement and acquisition according to several embodiments of this application. [Figure 7] This is a block diagram of an apparatus supporting QoE measurement and acquisition according to some other embodiments of the present application. [Modes for carrying out the invention]

[0042] The detailed description of the attached drawings is intended to describe preferred embodiments of this application and is not intended to represent the only forms in which this application may be practiced. It should be understood that the same or equivalent functions may be achieved by different embodiments intended to be covered within the spirit and scope of this application.

[0043] Next, several embodiments of this application are referenced in detail, examples of which are shown in the accompanying drawings. For ease of understanding, the embodiments are provided under specific network architectures and new service scenarios such as 3GPP® 5G and 3GPP® Long-Term Evolution (LTE). As network architectures and new service scenarios evolve, it is intended that all embodiments in this application be applicable to similar technical challenges. Furthermore, the terms listed in this application may change, and this should not affect the principles of this application.

[0044] Figure 1 shows a schematic diagram of an exemplary wireless communication system 100 according to several embodiments of the present application.

[0045] As shown in Figure 1, the wireless communication system 100 includes at least one BS101 and at least one UE102. In particular, the wireless communication system 100 includes one BS101 and two terminal devices 102 (e.g., a first UE102a and a second UE102b) for illustrative purposes. While a specific number of BS and terminal devices are shown in Figure 1 for brevity, it is intended that the wireless communication system 100 may include more or fewer BS and terminal devices in some other embodiments of this application.

[0046] 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, time division multiple access (TDMA) based networks, code division multiple access (CDMA) based networks, orthogonal frequency division multiple access (OFDMA) based networks, LTE networks, 3GPP® based networks, 3GPP® 5G networks, satellite communication networks, high-altitude platform networks, and / or other communication networks.

[0047] BS101 may communicate via an interface with CN nodes (not shown), such as a Mobility Management Entity (MME) or Serving Gateway (S-GW), Access and Mobility Management Function (AMF) or User Plane Function (UPF). BS may also be referred to as an access point, access terminal, base, macrocell, node B, enhanced node B (eNB), gNB, home node B, relay node, or device, or described using other terms used in the art. In 5G NR, BS may also be referred to as a RAN node. Each BS may service a serving area, such as several UEs within a cell or cell sector, via a wireless communication link. Neighboring BSs may communicate with each other as needed, for example, during handover procedures for UEs.

[0048] The terminal device (or remote device) 102, for example, the first UE 102a and the second UE 102b, may include computing devices such as desktop computers, laptop computers, personal digital assistants (PDAs), tablet computers, smart televisions (e.g., Internet-connected televisions), set-top boxes, game consoles, security systems (including security cameras), in-vehicle computers, and network devices (e.g., routers, switches, and modems). According to one embodiment of this application, the terminal device may include portable wireless communication devices, smartphones, cellular telephones, flip phones, devices having subscriber identification modules, personal computers, selective call receivers, or any other devices capable of sending and receiving communication signals over a wireless network. In some embodiments, the terminal device may include wearable devices such as smartwatches, fitness bands, and optical head-mounted displays. Furthermore, the terminal device may be referred to as a subscriber unit, mobile, mobile station, user, terminal, mobile terminal, wireless terminal, fixed terminal, subscriber station, user terminal, or device, or described using other terms used in the art. In this specification (and throughout this specification), "UE" is used illustratively as a typical terminal device to indicate a terminal device, but it should be understood as any type of terminal device.

[0049] 3GPP® Rel-17 specifies the basic mechanisms for NR QoE. For example, regarding the activation and reporting of QoE measurement collection, TS38.300 specifies the following: This function is activated in NG-RAN either by direct configuration from the OAM system (management-based activation) or by signaling including UE-related QoE configurations via the core network from OAM (signaling-based activation). One or more QoE measurement collection jobs may be activated in the UE for each service type, and each QoE measurement configuration is uniquely identified by a QoE reference. In the case of signaling-based QoE measurement, the OAM initiates QoE measurement activation for a specific UE via the core network, and the NG-RAN node receives one or more QoE measurement configurations via UE-related signaling. A QoE measurement configuration for signaling-based activation includes an application layer measurement configuration list and corresponding information about QoE measurement collection, such as QoE reference, service type, MCE IP address, slice range, area range, MDT alignment information, and indications of available RAN visible QoE metrics. Each application layer measurement configuration is encapsulated within a transparent container. The NG-RAN node forwards the corresponding QoE measurement configuration to the UE in a downlink RRC message containing AppLayerMeasConfig, as specified in TS38.331

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

[12] . The NG-RAN node sends the QoE report and the corresponding QoE reference ID to the MCE. QoE measurement collection is handled by application layer measurement configurations and measurement reports, which are supported only in the RRC_CONNECTED state. Application layer measurement configurations received by the gNB from the OAM or CN are encapsulated in a transparent container, which is then forwarded to the UE as application layer configurations in an RRCReconfiguration message (multiple configurations may exist in the same message). Application layer measurement reports received from the UE's upper layers are encapsulated in a transparent container, as specified in TS38.331

[12] , and sent to the network in a MeasurementReportAppLayer message. The UE can send multiple application layer measurement reports to the gNB in ​​a single MeasurementReportAppLayer message. Segmentation of MeasurementReportAppLayer messages may be enabled by the gNB to allow the transmission of application layer measurement reports exceeding the maximum PDCP SDU size. The measConfigAppLayerId carried in RRC signaling is used to identify the application layer measurement configurations and reports 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 the OAM along with the QoE reference. The gNB can release one or more application layer measurement configurations from the UE at any time in a single RRCReconfiguration message. Additionally, the UE may be configured by the gNB to report when the QoE measurement session starts or stops for a particular application layer measurement configuration.

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

[0051] TS38.300 also specifies the continuity of QoE measurement for mobility as follows: "Continuity of QoE measurement collection for in-system RAT mobility is supported by area range parameters configured by OAM, and the network is responsible for tracking whether the UE is inside or outside the area range. The UE should continue ongoing measurements even if it leaves the area range, unless the network instructs the UE to release the QoE configuration." In the case of RRC_CONNECTED state mobility, the source NG-RAN node may transmit information related to the QoE measurement configuration and / or the configuration of a particular 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. In the case of RRC_INACTIVE state mobility, the QoE measurement configuration of a particular UE may be restored from the node hosting the UE context when the UE resumes the RRC_CONNECTED state. Multiple sets of QoE measurement configurations should be supported during mobility. In the case of signaling-based QoE, during the handover to a QoE-supporting target gNB, the target gNB decides, for example, which application layer measurement configurations to retain and which to release, based on application layer measurement configuration information received from the source gNB in ​​Xn / NG signaling. When the UE resumes connectivity in a gNB that does not support QoE, the UE releases all application layer measurement configurations.

[0052] It can be seen that only Rel-17 specifies QoE measurement collection continuity for intra-system RAT mobility. QoE measurement collection continuity for intra-system RAT mobility is expected to be resolved in Rel-18. For example, according to RP-213159, it is agreed to "support the continuity of legacy QoE measurement jobs for streaming and MTSI services during the inter-RAT handover process within 5GC [RAN2, RAN3]". Related issues to be resolved include, but are not limited to, issues caused by mismatches in QoE measurement capabilities between two different RATs, for example, mismatches between NR QoE measurement collection capabilities and LTE QoE measurement collection capabilities. The term LTE refers to Advanced Universal Terrestrial Radio Access (E-UTRA). "LTE" is used for convenience. When BS is connected to 5GC, "LTE" may be replaced with "E-UTRA". RAN nodes within an intra-system RAT are NG-RAN nodes. An NG-RAN node is either a gNB that provides NR user plane and control plane protocol termination toward the UE and is connected via an NG interface to the 5GC, or an ng-eNB that provides E-UTRA user plane and control plane protocol termination toward the UE and is connected via an NG interface to the 5GC.

[0053] Specifically, NR QoE supports multiple QoE measurements per service type, and each QoE measurement (including the QoE measurement configuration and QoE measurement report) is identified by NR QoE identification information, such as a measurement configuration application layer identifier (ID) (currently designated as "measConfigAppLayerId" in the 3GPP® specification). The measurement configuration application layer ID can be carried in radio resource control (RRC) signaling as an RRC identifier to identify application layer measurement configurations and reports between the gNB and the UE. One or more QoE measurement collection jobs may be activated in the UE for each service type, and each QoE measurement configuration is uniquely identified by a QoE reference (e.g., QoE reference ID), with measConfigAppLayerId mapping to the QoE reference in the gNB.

[0054] However, LTE QoE supports only one QoE measurement per service type, and each QoE measurement collection job is implicitly identified by the QoE service type. LTE QoE does not provide additional identification information for different QoE measurement collection jobs. Currently, there are two service types supported in LTE QoE: streaming services and multimedia telephony services for IP multimedia subsystem (IMS) (MTSI) services. Therefore, there are two types of LTE QoE measurements: one is QoE measurement collection for streaming services, and the other is QoE measurement collection for MTSI services.

[0055] In some scenarios, where a RAT handover occurs from a source RAN node (e.g., gNB) that supports NR QoE, etc., to a target RAN node (e.g., ng-eNB) that supports LTE QoE, etc., other than NR QoE (Scenario 1 below), the source gNB may have two or more QoE measurement collection jobs activated for a particular service type (e.g., streaming service or MTSI service). However, the target ng-eNB can only support one QoE measurement collection job per service type. Therefore, it must be resolved how to ensure that the UE determines one QoE measurement collection job with QoE measurement continuity from two or more QoE measurement collection jobs per service type.

[0056] On the other hand, in some other scenarios where the RAT handover is from a source RAN node that supports LTE QoE (e.g., ng-eNB) to a target RAN node that supports NR QoE (e.g., gNB) (Scenario 2 below), it must also be resolved how to configure measConfigAppLayerId with QoE measurement continuity for QoE measurements identified only by service type, in order to ensure that the UE continues and reports the correct QoE measurements.

[0057] In consideration of the foregoing, embodiments of this application provide technical solutions, in particular methods and apparatus, for supporting QoE measurement collection continuity for inter-RAT mobility within a system, at least. The exemplary inter-RAT handovers shown herein are between an NR RAN node, e.g., a gNB, and an LTE RAN node, e.g., an ng-eNB, but those skilled in the art will be well aware that terminology, in particular "NR" and "gNB," may change with the evolution of 3GPP®. Any inter-RAT handover between a RAN node having a RAT supporting two or more QoE measurement collection jobs per service type and another RAN node having a RAT supporting only one QoE measurement collection job per service type will cause the same problem, which is solved by the technical solutions disclosed in embodiments of this application.

[0058] For example, considering Scenario 1, several embodiments of the present application provide a method that can be implemented by a RAN node (e.g., source gNB) having a RAT that supports two or more QoE measurement collection jobs per service type. An exemplary method includes the steps of sending first information to the UE indicating the configuration of at least one set of QoE measurements, and sending second information to the UE indicating the configuration of at least one QoE measurement in response to an inter-RAT handover to a target RAN node (e.g., ng-eNB) having another RAT that supports only one QoE measurement collection job per service type. Each set of QoE measurements contains one or more QoE measurements for the same service type, and different sets of QoE measurements are for different service types. At least one QoE measurement is selected from at least one set of QoE measurements, and different QoE measurements of at least one QoE measurement are for different service types.

[0059] Some other embodiments of this application provide alternative methods that can be implemented by a RAN node that supports only one QoE measurement per service type, such as a target ng-eNB. An exemplary method includes the steps of: receiving first information indicating the configuration of at least one set of QoE measurements from a source RAN node (such as a gNB) that supports two or more QoE measurements per service type in response to an inter-RAT handover; and transmitting second information indicating the configuration of at least one QoE measurement to the source RAN node. Similarly, each set of QoE measurements contains one or more QoE measurements for the same service type, and different sets of QoE measurements are for different service types. At least one QoE measurement is selected from at least one set of QoE measurements, and the different QoE measurements of at least one QoE measurement are for different service types.

[0060] Some further embodiments of this application provide yet another method that can be implemented by a UE, etc., in response to an inter-RAT handover from a RAN node having a RAT that supports two or more QoE measurements per service type to a target RAN node having another RAT that supports only one QoE measurement per service type. An exemplary method includes the steps of: receiving first information from a RAN node (e.g., source gNB) indicating the configuration of at least one set of QoE measurements; and receiving second information from the RAN node indicating the configuration of at least one QoE measurement in response to an inter-RAT handover from the RAN node to a target RAN node (e.g., ng-eNB). Similarly, each set of QoE measurements includes one or more QoE measurements for the same service type, and different sets of QoE measurements are for different service types. At least one QoE measurement is selected from at least one set of QoE measurements, and the different QoE measurements of at least one QoE measurement are for different service types.

[0061] Considering Scenario 2, several embodiments of the present application provide a method that can be implemented by a RAN node having a first RAT that supports only one QoE measurement per service type, e.g., a source ng-eNB. An exemplary method includes, in response to an inter-RAT handover, sending to a target RAN node (e.g., a gNB) having a second RAT that supports two or more QoE measurements per service type, information indicating at least one QoE measurement and information indicating that at least one QoE measurement is configured for a UE having a first RAT identifier (e.g., service type), wherein the different QoE measurements of the at least one QoE measurement are for different service types; receiving from the target RAN node a second RAT identifier (e.g., measConfigAppLayerId) and information associating at least one QoE measurement with the second RAT identifier; and sending to the UE the second RAT identifier and information associating at least one QoE measurement with the second RAT identifier.

[0062] Some other embodiments of this application provide a method that can be implemented by a RAN node having a second RAT that supports two or more QoE measurements per service type, such as a target gNB. An exemplary method includes the steps of: receiving information from a source RAN node (such as ng-eNB) having a first RAT that supports only one QoE measurement per service type in response to an inter-RAT handover, indicating that at least one QoE measurement is configured for a UE having a first RAT identifier (e.g., service type), wherein the different QoE measurements of the at least one QoE measurement are for different service types; and transmitting to the source RAN node information relating the second RAT identifier (e.g., measConfigAppLayerId) and the at least one QoE measurement identified by the first RAT identifier to the second RAT identifier.

[0063] Figure 2 is a flowchart illustrating a method for supporting QoE measurement acquisition in Scenario 1 according to several embodiments of this application. While the method is shown at the system level between the source RAN node, target RAN node, and remote device, those skilled in the art should understand that the method implemented in the source RAN node, target RAN node, and remote device may be separately implemented and / or incorporated by other devices having similar functionality.

[0064] As shown above, in Scenario 1, the RAT handover is from a source RAN node (e.g., an NR RAN node, gNB, etc.) with a RAT that supports two or more QoE measures per service type to a target RAN node (e.g., an E-UTRA RAN node, ng-eNB, etc.) with another RAT that supports only one QoE measure per service type.

[0065] Referring to Figure 2, a source RAN node can configure at least one set of QoE measurements for a remote device, e.g., a UE, in response to the activation of QoE measurements either by direct configuration from an OAM (not shown) (i.e., management-based activation) or by signaling from an OAM, e.g., a CN node, including UE-related QoE configuration via an AMF (i.e., signaling-based activation). Each set of QoE measurements contains one or more QoE measurements for the same service type, and different sets of QoE measurements are for different service types. For example, at least one set of QoE measurements may include a set of QoE measurements that includes one or more QoE measurements for streaming services. In another example, at least one set of QoE measurements may include a set of QoE measurements that includes one or more QoE measurements for MTSI services. In yet another example, at least one set of QoE measurements may include a first set of QoE measurements that includes one or more QoE measurements for streaming services and a second set of QoE measurements that includes one or more QoE measurements for MTSI services. Similar solutions can be applied to other service types in the future (if any).

[0066] In the case of management-based QoE measurement activation, the OAM sends one or more QoE measurement configurations to the source RAN node. In the case of signaling-based QoE measurement, the OAM initiates QoE measurement activation for a specific UE via a CN node, e.g., an AMF, and the CN node sends QoE measurement configuration information to the source RAN node for QoE measurement activation. Exemplary QoE measurement configuration information from the CN or OAM (also referred to as "CN / OAM QoE measurement configuration information") includes: - QoE Reference: Used to identify QoE measurements between gNB and CN or between gNB and OAM. - Service type: Indicates the service type for QoE measurement. - Container for application layer measurement configuration: Includes application layer measurement configuration, - Area range: The area range of the QoE measurement, including a list of cells, tracking area (TA), tracking area ID (TAI), or public land mobile network (PLMN) ID. Regarding the QoE reference (or QoE reference ID), it can be as defined in clause 5.2 of TS 28.405 and is an octet string of size (6). The QoE reference consists of a Mobile Country Code (MCC), a Mobile Network Code (MNC), and a QMC ID, where the MCC and MNC are accompanied by trace activation requests from that management system to identify a single PLMN including the management system, and the QMC ID is a 3-byte octet string.

[0067] In accordance with QoE measurement information from CN or OAM, the source RAN node sends first information to the UE in step 201 indicating the configuration of at least one set of QoE measurements, and the UE receives the first information accordingly. The configuration of at least one set of QoE measurements indicated in the first information lies in a first RAT, e.g., NR QoE, which supports two or more QoE measurements per service type. For example, the source RAN node provides the UE with a corresponding RRC QoE measurement configuration in a downlink RRC message that includes an application layer measurement configuration (e.g., AppLayerMeasConfig), which includes the following: - measConfigAppLayerId: The measurement configuration application layer ID used to identify application layer measurement configurations and reports between gNB and UE, and - Container for application layer measurement configuration: Contains application layer measurement configuration. Regarding the measurement configuration application layer ID, this can be an integer (0..61, ...) as defined in TS 38.331. The measurement configuration application layer ID is mapped to the QoE reference at the source RAN node.

[0068] Those skilled in the art will know that the above-mentioned information elements (IEs) or parameters are merely examples, and that these examples may change as the 3GPP® specification evolves, and therefore should not be used to unduly limit the scope of protection of this application.

[0069] Based on the received configuration of at least one set of QoE measurements, the UE performs the corresponding QoE measurement collection job. However, in step 203, the source RAN node may decide to perform an inter-system RAT handover to a target RAN node, for example, ng-eNB. For example, the source RAN node may send a handover request message to the target RAN node in step 205, and the target RAN node may send a handover response message, for example, a handover request acknowledgment (ACK) message, in step 207.

[0070] In response to the inter-RAT handover, the source RAN node, in step 208, for example in a handover command message (e.g., MobilityFromNRCommand), transmits second information to the UE indicating the configuration of at least one QoE measurement selected from at least one set of QoE measurements. The configuration of at least one QoE measurement indicated in the second information is in a second RAT different from the first RAT, for example, a RAT that supports only one QoE measurement per service type (e.g., LTE QoE). The different QoE measurements of the at least one QoE measurement are for different service types; that is, at least one QoE measurement is per service type, and only one QoE measurement is selected for each service type. Thus, the UE receives the second information indicating the configuration of at least one QoE measurement and continues with at least one QoE measurement after the inter-RAT handover. The other QoE measurements in at least one set of QoE measurements, excluding at least one QoE measurement, are stopped or released.

[0071] There are various ways of selecting at least one QoE measurement with QoE measurement continuity from at least one set of QoE measurements and / or indicating QoE measurement continuity to the UE after a RAT handover.

[0072] According to some embodiments of this application, a mechanism indicating the continuity of QoE measurement after an inter-RAT handover is used to determine which QoE measurements per service type will continue after the inter-RAT handover.

[0073] In some embodiments of this application, information indicating QoE measurement continuity after a RAT handover (hereinafter referred to as RAT-to-RAT QoE continuity indication) is received from or from the OAM system via the CN. The RAT-to-RAT QoE continuity indication may be included in the UE application layer measurement information IE of the QMC configuration information IE in NG-AP signaling. For example, for a particular service type, e.g., a streaming service, the OAM system or CN may provide two or more QoE measurement configurations (e.g., application layer measurements), each QoE measurement configuration being uniquely identified by a QoE reference, e.g., QoE reference ID "1" for a first QoE measurement and QoE reference ID "2" for a second QoE measurement. The OAM system or CN also provides a RAT-to-RAT QoE continuity indicator for one of two or more QoE measures per service type, which is used, for example, to indicate which QoE measure will continue after an RAT-to-RAT handover from gNB to ng-eNB. For example, the RAT-to-RAT QoE continuity indicator is configured for a QoE measure having QoE reference ID "1" to indicate that the QoE measure having QoE reference ID "1" for a streaming service will continue after the RAT-to-RAT handover.

[0074] Those skilled in the art will know that while it is supported that one QoE measurement for each service type continues after an inter-RAT handover, this does not mean that one QoE measurement must continue for each service type. For example, if there is a set of QoE measurements for streaming services and a set of QoE measurements for MTSI services, in some embodiments of this application, only one QoE measurement for streaming services and only one QoE measurement for MTSI services are configured to continue after an inter-RAT handover.

[0075] Inter-RAT QoE continuity indicators can take various forms. For example, an inter-RAT QoE continuity indicator from an OAM or CN may explicitly indicate which QoE measures for a service type will continue after an inter-RAT handover. In another example, an inter-RAT QoE continuity indicator may implicitly indicate which QoE measures for a service type will continue after an inter-RAT handover, for example, by indicating the continuity priority of each QoE measure for that service type after an inter-RAT handover. The QoE measure with the highest priority among two or more QoE measures for a service type will continue after an inter-RAT handover. In some cases, there may be only one QoE measure in the set of QoE measures for a service type, and the service type can also be used as an inter-RAT QoE continuity indicator, which implicitly indicates that only one QoE measure for that service type will continue after an inter-RAT handover.

[0076] Based on the received inter-RAT QoE continuity indication, the source RAN node may, in some embodiments of this application, select at least one QoE measurement from at least one set of QoE (Method 1), or transmit the inter-RAT QoE continuity indication to the target RAN node, and at least one QoE measurement is selected by the target RAN node from at least one set of QoE (Method 2).

[0077] Figure 3 is a flowchart illustrating a method for supporting QoE measurement acquisition using Method 1 in Scenario 1, according to several embodiments of the present application. While the method is shown at the system level between the source RAN node, target RAN node, and remote device, those skilled in the art should understand that the method implemented in the source RAN node, target RAN node, and remote device may be separately implemented and / or incorporated by other devices having similar functionality. In addition, since the embodiments shown with reference to Figure 3 are also applicable to Scenario 1, the embodiments shown for Scenario 1 with reference to Figure 2 are also applicable to Figure 3, and therefore the same operation is simplified or omitted in the following description.

[0078] Similarly, RAT handover is from a source RAN node (e.g., an NR RAN node, gNB, etc.) with a first RAT that supports two or more QoE measurements per service type to a target RAN node (e.g., an E-UTRA RAN node, ng-eNB, etc.) with a second RAT that supports only one QoE measurement per service type.

[0079] Referring to Figure 3, similar to step 201, in step 301, the source RAN node may transmit first information indicating the configuration of at least one set of QoE measurements for a remote device, e.g., UE, in response to the QoE measurements being activated either by direct configuration from an OAM (not shown) (i.e., management-based activation) or by signaling from an OAM to a CN node, e.g., via an AMF, including UE-related QoE configuration (i.e., signaling-based activation).

[0080] The source RAN node also receives, for example, an inter-RAT QoE continuity indication from the OAM or CN indicating that a QoE measurement having QoE reference ID "1" will continue after the inter-RAT handover. According to some embodiments of the present application, the source RAN node also transmits the inter-RAT QoE continuity indication to the UE along with the first information in step 301.

[0081] For example, a source RAN node provides the UE with a configuration of at least one set of QoE measurements in a first RAT, along with an inter-RAT QoE continuity indication, by application layer configuration (e.g., AppLayerMeasConfig IE) in an RRC reconfiguration message, where each configuration of the at least one set of QoE measurements is identified by first RAT identification information carried in RRC signaling, e.g., measConfigAppLayerId, which can identify the application layer measurement configuration and reporting between the source RAN node and the UE. The measConfigAppLayerId is mapped to a QoE reference, for example, measConfigAppLayerId "1" is mapped to QoE reference ID "1", and measConfigAppLayerId "1" is mapped to QoE reference ID "2". When the UE's Access Layer (AS) layer receives the inter-RAT QoE continuity indication, the AS layer may forward the inter-RAT QoE continuity indication to the UE's Application Layer.

[0082] If the source RAN node decides in step 303 to perform an inter-system RAT handover to the target RAN node, the source RAN node may select at least one QoE measurement from at least one set of QoE measurements based on the inter-RAT QoE continuity indication. Each of the at least one QoE measurement is for a different service type required in the second RAT. In step 305, the source RAN node sends third information to the target RAN node, for example, via a handover request message or via a source-target transparent container, indicating only the configuration of at least one QoE measurement.

[0083] For example, based on an inter-RAT QoE continuity indication configured for a QoE measurement having QoE reference ID "1", the source RAN node selects the QoE measurement having QoE reference ID "1" and includes only the configuration of the QoE measurement having QoE reference ID "1" to the target RAN node, for example, in the handover request message in step 305. In some other embodiments, the source RAN node may also generate a QoE measurement configuration in the second RAT, for example, an LTE RRC QoE configuration of the QoE measurement configuration and include it in the source-to-target transparent container to the target RAN node. The LTE RRC QoE configuration may be encoded in LTE RRC ASN.1 format.

[0084] After receiving the configuration of at least one QoE measurement configuration, for example, a QoE measurement configuration having QoE reference ID "1", the target RAN node either generates an LTE RRC QoE configuration for the UE based on the received QoE measurement configuration, or updates the received LTE RRC QoE configuration to provide an updated LTE RRC QoE configuration for the UE. In step 307, the target RAN node sends the generated or updated LTE RRC QoE configuration to the source RAN node, for example, via the target RAT message container in a handover response message. The LTE RRC QoE configuration provided by the target RAN node provides only the service type, for example, "streaming", without any measConfigAppLayerId.

[0085] After receiving the configuration of at least one QoE measurement in the second RAT, for example, the LTE RRC QoE configuration of a QoE measurement having QoE reference ID "1", the source RAN node forwards it to the UE in step 308, for example, in a MobilityFromNRCommand message. That is, corresponding to step 208, in step 308, the source RAN node sends second information to the UE indicating the configuration of the selected at least one QoE measurement, which is located in the second RAT.

[0086] Based on the inter-RAT QoE continuity indication received from the source RAN node and the configuration of at least one selected QoE measurement in the second RAT, for example, the LTE RRC QoE configuration per service type, the UE can determine which QoE measurement per service type will be continued after the inter-RAT handover. Thus, the UE will continue at least one QoE measurement, for example, the streaming QoE measurement having measConfigAppLayerId "1" mapped to QoE reference ID "1" indicated by the inter-RAT QoE continuity indication. The UE will stop or release other QoE measurements, for example, the streaming QoE measurement having measConfigAppLayerId "2" mapped to QoE reference ID "2".

[0087] In addition to transmitting the inter-RAT QoE continuity indication to the UE along with the first information, in some other embodiments of this application, the source RAN node may, in step 308, transmit the inter-RAT QoE continuity indication to the UE along with the second information, for example, in a MobilityFromNRCommand message.

[0088] For example, inter-RAT QoE continuity indication is provided in an exemplary MobilityFromNRCommand message along with the LTE RRC QoE configuration, as follows: MobilityFromNRCommand := { inter-RAT QoE continuity indication measConfigAppLayerId; RRC container incl. LTE RRC QoE Configuration}

[0089] When a UE receives a MobilityFromNRCommand message indicating the configuration of at least one QoE measurement in a second RAT, the UE continues the QoE measurement of a particular service type with an inter-RAT QoE continuity indication and releases other QoE configurations of the same service type.

[0090] In some embodiments of this application, inter-RAT QoE continuity indications may be indicated to the UE in an implicit manner, for example, by sending information in a MobilityFromNRCommand message indicating that the other QoE measurements of at least one set of QoE measurements are being released, except for at least one QoE measurement.

[0091] For example, according to the RAT-to-RAT QoE continuity indication, the source RAN node may trigger the release of other QoE measures of the same service type not indicated by the RAT-to-RAT QoE continuity, such as a QoE measure for streaming with measConfigAppLayerId "2". The source RAN node includes the measConfigAppLayerId of the QoE measure to be released in the exemplary MobilityFromNRCommand message, as follows: MobilityFromNRCommand := { measConfigAppLayerToRelease measConfigAppLayerId; RRC container incl. LTE RRC QoE Configuration}

[0092] After receiving the MobilityFromNRCommand message, the UE releases any QoE measurements that are indicated to be released, and maintains and continues any QoE measurements that are not released after the RAT handover from the source RAN node to the target RAN node, for example, by performing the QoE measurements and / or sending the QoE measurement report to the target RAN node.

[0093] Method 2 Figure 4 is a flowchart illustrating a method for supporting QoE measurement acquisition using Method 2 in Scenario 1, according to several embodiments of this application. While the method is shown at the system level between the source RAN node, target RAN node, and remote device, those skilled in the art should understand that the method implemented in the source RAN node, target RAN node, and remote device may be separately implemented and / or incorporated by other devices having similar functionality. In addition, since the embodiments shown with reference to Figure 4 are also applicable to Scenario 1, the embodiments shown for Scenario 1 with reference to Figure 2 are also applicable to Figure 4, and therefore the same operation is simplified or omitted in the following description.

[0094] Similarly, RAT handover is from a source RAN node (e.g., an NR RAN node, gNB, etc.) with a first RAT that supports two or more QoE measurements per service type to a target RAN node (e.g., an E-UTRA RAN node, ng-eNB, etc.) with a second RAT that supports only one QoE measurement per service type.

[0095] Referring to Figure 4, similar to step 201, in step 401, the source RAN node may transmit first information to a remote device, e.g., a UE, indicating the configuration of at least one set of QoE measurements in the first RAT, in response to the activation of the QoE measurements either by direct configuration from an OAM (not shown) (i.e., management-based activation) or by signaling from an OAM to a CN node, e.g., via an AMF, including UE-related QoE configuration (i.e., signaling-based activation). The source RAN node may also receive, for example, an inter-RAT QoE continuity indication from the OAM or CN indicating that the QoE measurement having QoE reference ID "1" will continue after the inter-RAT handover. However, the inter-RAT QoE continuity indication is not required in step 401.

[0096] For example, a source RAN node provides the UE with the configuration of at least one set of QoE measurements in a first RAT by application layer configuration (e.g., AppLayerMeasConfig IE) in an RRC reconfiguration message, and each configuration of at least one set of QoE measurements is identified by first RAT identification information carried in RRC signaling, for example, measConfigAppLayerId, which can identify the application layer measurement configuration and report between the source RAN node and the UE. measConfigAppLayerId is mapped to a QoE reference, for example, measConfigAppLayerId "1" is mapped to QoE reference ID "1", and measConfigAppLayerId "2" is mapped to QoE reference ID "2".

[0097] If the source RAN node decides in step 403 to perform an inter-system RAT handover to the target RAN node, the source RAN node does not select QoE measurements. Instead, in step 405, the source RAN node sends third information and an inter-RAT QoE continuity indication to the target RAN node, for example, via a handover request message or via a source-target transparent container, indicating the configuration of at least one set of QoE measurements.

[0098] For example, the source RAN node provides UE application layer measurement information IE of QMC configuration information IE in the XnAP handover request message. The source RAN node also provides the target RAN node with second RAT identification information, for example, the configured measConfigAppLayerId for each QoE measurement, in the same XnAP message. For example, the source RAN node provides the target RAN node with measConfigAppLayerId "1" for the QoE measurement with QoE reference ID "1" and measConfigAppLayerId "2" for the QoE measurement with QoE reference ID "2". The source RAN node may also provide the target RAN node with inter-RAT QoE continuity indications.

[0099] After receiving the third piece of information and the inter-RAT QoE continuity indication, the target RAN node selects from at least one set of QoE measurements to maintain and continue, according to the inter-RAT QoE continuity indication. For example, if the inter-RAT QoE continuity indication indicates that only QoE measurements with QoE reference "1" will continue after the inter-RAT handover, the target RAN node selects the QoE measurement with QoE reference ID "1" that should be maintained and continued after the inter-RAT handover. If the inter-RAT QoE continuity indication is represented as the continuation priority of QoE measurements after the inter-RAT handover, the target RAN node decides to select the QoE measurement with the highest continuation priority among one or more QoE measurements for the same service type.

[0100] Similarly, the target RAN node generates a configuration for at least one QoE measurement in the second RAT, for example, an LTE RRC QoE configuration for the UE, based on the received QoE measurement configuration, or updates the received LTE RRC QoE configuration to provide an updated LTE RRC QoE configuration for the UE. In step 407, the target RAN node sends the generated or updated configuration of at least one QoE measurement in the second RAT, for example, an LTE RRC QoE configuration, to the source RAN node, for example, in a handover response message, along with the corresponding second RAT identification information, for example, measConfigAppLayerId. In some embodiments of this application, measConfigAppLayerId may be included in the LTE RRC QoE configuration.

[0101] After receiving the configuration of at least one QoE measurement in the second RAT, for example, the LTE RRC QoE configuration of the QoE measurement having the corresponding measConfigAppLayerId, the source RAN node forwards it to the UE in step 408, for example, in a MobilityFromNRCommand message.

[0102] Based on the LTE QoE configuration, which includes the corresponding NR measConfigAppLayerId in the MobilityFromNRCommand message received from the source RAN node, the UE continues at least one QoE measurement with the corresponding measConfigAppLayerId, for example, continuing a streaming QoE measurement with measConfigAppLayerId "1" mapped to QoE reference ID "1". The UE stops or releases other QoE measurements, for example, stopping or releasing a streaming QoE measurement with measConfigAppLayerId "2" mapped to QoE reference ID "2".

[0103] In some other embodiments of this application, in step 407, the target RAN node may send information to the source RAN node in the handover response message indicating the QoE measurements to be released, for example, a QoE measurement release list. The QoE measurement release list may also present a QoE deactivation list, which includes a list of QoE reference IDs of QoE measurements to be released or deactivated.

[0104] In some other embodiments of the present application, in step 407, the target RAN node may send information to the source RAN node indicating the QoE measurements to be continued and maintained, for example, by including a QoE measurement maintenance list (or continuity list) to the source RAN node in the handover response message to indicate that the QoE measurements will be continued and maintained after the inter-RAT handover.

[0105] In some yet other embodiments of this application, the target RAN node may send both the QoE measurement release list and the QoE measurement retention list to the source RAN node.

[0106] After the source RAN node receives the QoE measurement release list and / or QoE measurement retention list in the handover response message, the source gNB, in step 408, sends the corresponding QoE measurement release list, e.g., measConfigAppLayerToReleaseList, to the UE to release the listed QoE measurements. measConfigAppLayerToReleaseList may include a list of measConfigAppLayerIds of the QoE measurements to be released. In some other embodiments of the present application, the source RAN node may also send the corresponding QoE measurement retention list, e.g., measConfigAppLayerToKeptList, to indicate the QoE measurements to be maintained and kept. In some other embodiments of the present application, the source RAN node may send both measConfigAppLayerToReleaseList and measConfigAppLayerToKeptList to the UE in step 408. measConfigAppLayerToReleaseList and / or measConfigAppLayerToKeptList may be included in the MobilityFromNRCommand message.

[0107] After receiving the MobilityFromNRCommand message, the UE releases the QoE measurement indicated in measConfigAppLayerToReleaseList and maintains (continues) other QoE measurements, and / or the UE maintains the QoE measurement in measConfigAppLayerToKeptList and releases other QoE measurements.

[0108] In some other embodiments of this application, the source RAN node may select at least one QoE measurement based on its implementation in Method 1, i.e., the inter-RAT QoE continuity indication may be generated by the source RAN node instead of being received directly from the OAM or via the CN. In Method 2, the source RAN node may also transmit the inter-RAT QoE continuity indication, which it has generated itself, to the target RAN node. Similarly, the target RAN node may select at least one QoE measurement based on its implementation in Method 2, i.e., the inter-RAT QoE continuity indication may be generated by the target RAN node instead of being provided by the source RAN node.

[0109] Figure 5 is a flowchart illustrating a method for supporting QoE measurement acquisition in Scenario 2, according to several embodiments of this application. While the method is shown at the system level between the source RAN node, target RAN node, and remote device, those skilled in the art should understand that the method implemented in the source RAN node, target RAN node, and remote device may be separately implemented and / or incorporated by other devices having similar functionality.

[0110] As shown above, in Scenario 2, the RAT handover is from a source RAN node (e.g., an E-UTRA RAN node, ng-eNB, etc.) with a first RAT that supports only one QoE metric per service type to a target RAN node (e.g., an NR RAN node, gNB, etc.) with a second RAT that supports two or more QoE metrics per service type.

[0111] Referring to Figure 5, a source RAN node can configure at least one QoE measurement for a remote device, e.g., a UE, in response to the activation of a QoE measurement by either direct configuration from an OAM (not shown) (i.e., management-based activation) or by signaling from an OAM, e.g., a CN node, including UE-related QoE configuration via AMF (i.e., signaling-based activation). Each QoE measurement is for a service type, and different QoE measurements are for different service types. That is, QoE measurements are per service type and implicitly identified by the service type. For example, at least one QoE measurement may include at least one of the following: a QoE measurement for streaming services or a QoE measurement for MTSI services. Similar solutions are applicable to other service types in the future (if any).

[0112] In step 501, the source RAN node, for example ng-eNB, sends the UE a configuration of at least one QoE measurement having a first RAT identifier, for example, a service type. For example, the source RAN node may also send the UE application layer configuration (for example, AppLayerMeasConfig IE) in an RRC reconfiguration message, indicating the corresponding service type, for example, a streaming service, to the UE.

[0113] In step 503, the source RAN node may decide to perform an inter-system RAT handover to a target RAN node, for example, a gNB. In step 505, the source RAN node transmits the configuration of at least one QoE measurement to the target RAN node, for example, by transmitting the UE application layer measurement information IE of the QMC configuration information IE in the XnAP handover request message. The source RAN node may also provide information indicating that at least one QoE measurement is configured for a UE having first RAT identification information (hereinafter referred to as indication information), for example, an indication indicating whether a QoE measurement is already configured for a UE in LTE QoE. The indication information also indicates that a QoE measurement is in progress when the inter-RAT handover occurs.

[0114] After receiving at least one QoE measurement and indication information, the target RAN node identifies a QoE measurement already configured for the UE in the first RAT (e.g., LTE QoE). The target RAN node assigns (or allocates) a second RAT identifier, e.g., measConfigAppLayerId, to each of the at least one QoE measurement. In step 507, the target RAN node sends to the source RAN node, for example in a handover request acknowledgment message, the second RAT identifier for the at least one QoE measurement and information relating the at least one QoE measurement to the second RAT identifier (hereinafter referred to as association information), which instructs the UE to associate the ongoing QoE measurement identified by the first RAT identifier with the second RAT identifier. In some embodiments of the present application, the association information may be implicitly indicated by the second RAT identifier. For example, the association information for an ongoing QoE meter may be implicitly indicated by including the measConfigAppLayerId of one QoE meter for the service type.

[0115] The target RAN node generates a configuration for at least one QoE measurement in the second RAT, for example, an NR QoE measurement configuration, and transmits this configuration to the source RAN node, for example, in a handover request acknowledgment message.

[0116] In step 508, the source RAN node forwards the received information to the UE, for example, in a MobilityFromE-UTRACommand message. After receiving the association information and measConfigAppLayerId, the UE continues the QoE measurement after the RAT handover, including associating the ongoing QoE measurement with the assigned measConfigLayerId and sending the QoE measurement report to the target node. In some embodiments, the UE RRC layer forwards the received association information and measConfigAppLayerId to the UE application layer. The UE application layer continues the QoE measurement after the RAT handover, including associating the ongoing QoE measurement with the assigned measConfigLayerId and sending the QoE measurement report to the target node.

[0117] In addition to the method, the embodiments of this application also propose an apparatus to support QoE measurement and data acquisition.

[0118] For example, Figure 6 shows a block diagram of a device 600 that supports QoE measurement reporting according to some other embodiments of this application.

[0119] As shown in Figure 6, the device 600 may include at least one non-temporary computer-readable medium 601, at least one receiving circuit 602, at least one transmitting circuit 604, and at least one processor 606 coupled to the non-temporary computer-readable medium 601, the receiving circuit 602, and the transmitting circuit 604. The device 600 may also be a RAN node or terminal device (e.g., UE) configured to implement the methods described above, etc.

[0120] In this figure, elements such as at least one processor 606, a transmitting circuit 604, and a receiving circuit 602 are described singly, but unless explicitly stated otherwise, plural is intended. In some embodiments of this application, the receiving circuit 602 and the transmitting circuit 604 may be combined into a single device such as a transceiver. The processor 606 may be a CPU, DSP, microprocessor, etc. In certain embodiments of this application, the apparatus 600 may further include an input device, memory, and / or other components.

[0121] In some embodiments of this application, the non-temporary computer-readable medium 601 may store computer-executable instructions thereon that cause the processor 606 to implement methods relating to RAN nodes such as gNB or ng-eNB as described above. For example, when executed, the computer-executable instructions cause the processor 606 to interact with the receive circuit 602 and the transmit circuit 604 to carry out steps relating to RAN nodes as shown above.

[0122] In some other embodiments of this application, the non-temporary computer-readable medium 601 may store computer-executable instructions thereon for causing a processor to implement the methods relating to the UE as described above. For example, when executed, the computer-executable instructions cause the processor 606 to interact with the receiving circuit 602 and the transmitting circuit 604 to carry out the steps relating to the UE as shown above.

[0123] Figure 7 is a block diagram of an apparatus supporting QoE measurement and acquisition according to several embodiments of this application.

[0124] Referring to Figure 7, the device 700, for example, a UE or RAN node, for example, a source RAN node or a target RAN node, may include at least one processor 702 and at least one transceiver 704. The transceiver 704 may include at least one separate receiving circuit 706 and transmitting circuit 708, or at least one integrated receiving circuit 706 and transmitting circuit 708. The at least one processor 702 may be a CPU, DSP, microprocessor, etc.

[0125] According to some embodiments of the present application, when the device 700 is a RAN node, for example, a source gNB, the device is configured to transmit to the UE first information indicating the configuration of at least one set of QoE measurements, wherein each set of QoE measurements includes one or more QoE measurements for the same service type, and different sets of QoE measurements are for different service types, and in response to an inter-RAT handover to a target RAN node, the device is configured to transmit to the UE second information indicating the configuration of at least one QoE measurement, wherein at least one QoE measurement is selected from at least one set of QoE measurements, and different QoE measurements of at least one QoE measurement are for different service types.

[0126] According to some embodiments of the present application, when the device 700 is a RAN node, for example, target ng-eNB, the device is configured to, in response to an inter-RAT handover, receive first information from the source RAN node indicating the configuration of at least one set of QoE measurements, wherein each set of QoE measurements includes one or more QoE measurements for the same service type, and different sets of QoE measurements are for different service types; and transmit second information to the source RAN node indicating the configuration of at least one QoE measurement, wherein at least one QoE measurement is selected from at least one set of QoE measurements, and different QoE measurements of at least one QoE measurement are for different service types.

[0127] According to some embodiments of the present application, when the device 700 is a RAN node, for example, source ng-eNB, the device is configured to respond to a RAT handover by transmitting to a target RAN node information indicating at least one QoE measurement and information indicating that at least one QoE measurement is configured for a UE having first RAT identification information, wherein different QoE measurements of the at least one QoE measurement are for different service types; receiving from the target RAN node information relating to a second RAT identification information and at least one QoE measurement to the second RAT identification information; and transmitting to the UE information relating to the second RAT identification information and at least one QoE measurement to the second RAT identification information.

[0128] According to some embodiments of the present application, when the device 700 is a RAN node, for example, a target gNB, the device is configured to receive from the source RAN node in response to an inter-RAT handover information indicating at least one QoE measurement and information indicating that at least one QoE measurement is configured for a UE having first RAT identification information, wherein different QoE measurements of the at least one QoE measurement are for different service types, and to transmit to the source RAN node second RAT identification information and information relating at least one QoE measurement identified by the first RAT identification information to the second RAT identification information.

[0129] According to some embodiments of the present application, when the device 700 is a UE, the device may be configured to receive first information from a RAN node indicating the configuration of at least one set of QoE measurements, wherein each set of QoE measurements includes one or more QoE measurements for the same service type, and different sets of QoE measurements are for different service types; and in response to an inter-RAT handover from the RAN node to a target RAN node, the device may be configured to receive second information from the RAN node indicating the configuration of at least one QoE measurement, wherein at least one QoE measurement is selected from at least one set of QoE measurements, and different QoE measurements of at least one QoE measurement are for different service types.

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

[0131] An alternative embodiment preferably implements the method according to the embodiment of this application in a non-temporary computer-readable storage medium storing computer-programmable instructions. The instructions are preferably executed by a computer-executable component integrated with a network security system. The non-temporary computer-readable storage medium may be stored on any suitable computer-readable medium such as RAM, ROM, flash memory, EEPROM, optical storage devices (CD or DVD), hard drives, floppy drives, or any suitable device. The computer-executable component is preferably a processor, but the instructions may be executed by any suitable dedicated hardware device, either as an alternative or additional measure. For example, one embodiment of this application provides a non-temporary computer-readable storage medium storing computer-programmable instructions therein. The computer-programmable instructions are configured to implement the method described above or other methods according to one embodiment of this application.

[0132] While this application has been described in conjunction with its specific embodiments, it is evident that many alternative, modified, and variant forms may be apparent to those skilled in the art. For example, various components of the embodiments may be interchangeable, added, or substituted in other embodiments. Furthermore, not all elements in each figure are necessary for the operation of the disclosed embodiments. For example, a person skilled in the art of the disclosed embodiments may be able to formulate and use the teachings of this application simply by adopting the elements of the independent claims. Accordingly, the embodiments of this application described herein are intended to be illustrative, not restrictive. Various modifications may be made without departing from the spirit and scope of this application. [Explanation of symbols]

[0133] 100 Wireless Communication Systems 101 BS 102 UE, terminal device 102a First UE 102b Second UE 600 equipment 601 Non-temporary computer-readable media 602 Receiving Circuit 604 Transmitter Circuit 606 Processor 700 equipment 702 Processor 704 Transceiver 706 Receiving Circuit 708 Transmitter Circuit

Claims

1. A Wireless Access Network (RAN) node, Processor and The processor comprises a transceiver coupled to the processor, and the transceiver is Receiving information from the Operations Management and Maintenance (OAM) system, or from the OAM system via the Core Network (CN), indicating the continuity of QoE measurement after inter-RAT handover. Transmitting to a user device (UE) first information indicating the configuration of at least one set of quality-of-experience (QoE) measurements, wherein each set of QoE measurements includes one or more QoE measurements for the same service type, and different sets of QoE measurements are for different service types; In response to a radio access technology (RAT) handover to a target RAN node, transmit to the UE second information indicating the configuration of at least one QoE measurement, wherein the at least one QoE measurement is selected by the RAN node from at least one set of the QoE measurements based on the information indicating QoE measurement continuity after the RAT handover, and the different QoE measurements of the at least one QoE measurement are for different service types. A RAN node configured to perform the following actions.

2. The RAN node according to claim 1, wherein the information indicating the continuity of QoE measurements after an inter-RAT handover indicates which QoE measurements for a service type will be continued after the inter-RAT handover, or indicates the continuity priority of each QoE measurement for a service type after an inter-RAT handover.

3. The aforementioned processor, Select the at least one QoE measurement based on the information indicating the continuity of QoE measurements. It is configured in such a way, The aforementioned transceiver, Transmitting third information indicating only the configuration of at least one QoE measurement to the target RAN node, Receiving the second information from the target RAN node, which indicates the configuration of the at least one QoE measurement, wherein the configuration of the at least one QoE measurement shown in the second information is generated or updated based on the configuration of the at least one QoE measurement shown in the third information. A RAN node according to claim 1, configured to perform the following:

4. The aforementioned transceiver, Transmit to the target RAN node third information indicating the configuration of at least one set of the QoE measurements and the information indicating the continuity of QoE measurements after the RAT handover, Receiving the second information from the target RAN node, which indicates the configuration of the at least one QoE measurement, wherein the configuration of the at least one QoE measurement shown in the second information is generated or updated based on the configuration of the at least one set of QoE measurements shown in the third information. A RAN node according to claim 1, configured to perform the following:

5. The RAN node according to claim 1, wherein the configuration of at least one set of QoE measurements shown in the first information is located in a first RAT, and the configuration of at least one QoE measurement shown in the second information is located in a second RAT different from the first RAT.

6. A Wireless Access Network (RAN) node, Processor and The processor comprises a transceiver coupled to the processor, and the transceiver is Receiving, in response to a Radio Access Technology (RAT) handover, from a source RAN node, first information indicating the configuration of at least one set of perceived quality (QoE) measurements, and an inter-RAT QoE continuity indication indicating QoE measurements to be continued after the inter-RAT handover, wherein each set of QoE measurements includes one or more QoE measurements for the same service type, and different sets of QoE measurements are for different service types; Transmitting to the source RAN node second information indicating the configuration of at least one QoE measurement, wherein the at least one QoE measurement is selected by the RAN node from at least one set of QoE measurements based on the inter-RAT QoE continuity indication, and the different QoE measurements of the at least one QoE measurement are for different service types. A RAN node configured to perform the following actions.

7. A Wireless Access Network (RAN) node, Processor and The processor comprises a transceiver coupled to the processor, and the transceiver is In response to a wireless access technology (RAT) handover, transmit to a target RAN node information indicating at least one quality-of-effect (QoE) measurement and information indicating that the at least one QoE measurement is configured for a user equipment (UE) having first RAT identification information, wherein different QoE measurements of the at least one QoE measurement are for different service types. The system receives from the target RAN node a second RAT identification information and information relating the at least one QoE measurement to the second RAT identification information, and determines that the at least one QoE measurement will continue after the inter-RAT handover. To indicate to the UE that the at least one QoE measurement will continue after the RAT handover, the UE is to transmit the second RAT identification information and the information relating the at least one QoE measurement to the second RAT identification information. A RAN node configured to perform the following actions.

8. The RAN node according to claim 7, wherein the first RAT identification information is a service type and the second RAT identification information is a measurement configuration application layer identifier (ID).

9. The RAN node according to claim 7, wherein the information relating the at least one QoE measurement to the second RAT identification information is implicitly indicated by the second RAT identification information.

10. The RAN node according to claim 7, wherein the RAN node is an ng-eNB and the target RAN node is a gNB.

11. It is a remote device, Processor and The processor comprises a transceiver coupled to the processor, and the transceiver is Receiving first information from a Wireless Access Network (RAN) node indicating the configuration of at least one set of Quality of Experience (QoE) measurements, wherein each set of QoE measurements includes one or more QoE measurements for the same service type, and different sets of QoE measurements are for different service types; Receiving second information from the RAN node in response to a radio access technology (RAT) handover from the RAN node to a target RAN node, wherein the at least one QoE measurement is selected from at least one set of QoE measurements, and different QoE measurements of the at least one QoE measurement are for different service types. Continuing at least one QoE measurement after an inter-RAT handover based on information indicating the continuity of QoE measurement after an inter-RAT handover, wherein the information indicating the continuity of QoE measurement after an inter-RAT handover is received together with at least one of the first information or the second information. A remote device configured to perform the following actions.

12. The aforementioned transceiver, In response to the RAT handover, information is received indicating that the at least one QoE measurement should be continued. It is configured in such a way, The aforementioned processor, Continue the at least one QoE measurement after the RAT handover. The remote device according to claim 11, configured as follows.

13. The remote device according to claim 11, wherein the configuration of at least one set of QoE measurements shown in the first information is located in a first RAT, and the configuration of at least one QoE measurement shown in the second information is located in a second RAT different from the first RAT.

Images