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

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 technologies, and in particular, to methods and apparatuses for supporting quality of experience (QoE) measurement collection (also referred to as QMC, QoE, QoE measurement, or QoE measurement collection job, etc.).

Background Art

[0002] Wireless communication systems have been widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcast, etc. A wireless communication system may employ a multiple access technology 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, configuring, collecting, mobility support, and reporting of QoE measurement, etc., are specified. However, only the QoE measurement collection continuity for in-system radio access technology (RAT) mobility is supported in Rel-17. Support for QoE measurement collection continuity for in-system RAT-to-RAT mobility is expected to be realized in Rel-18.

[0004] Therefore, the industry desires technologies for supporting QoE measurement collection continuity for in-system RAT-to-RAT mobility.

Summary of the Invention

Problems to be Solved by the Invention

[0005] One objective of an embodiment of the present application is to provide a technical solution for supporting QoE measurement collection, for example, a method and apparatus for supporting the continuity of QoE measurement collection for inter-RAT mobility within a system.

Means for Solving the Problems

[0006] Some embodiments of the present application are radio access network (RAN) nodes, for example, gNBs, including a processor and a transceiver coupled to the processor, the transceiver transmitting to a user equipment (UE) first information indicating a configuration of at least one set of QoE measurements, each set of QoE measurements including one or more QoE measurement values for the same service type, different sets of QoE measurements being for different service types, and transmitting, in response to an inter-RAT handover to a target RAN node, second information indicating a configuration of at least one QoE measurement to the UE, at least one QoE measurement being selected from at least one set of QoE measurements, different QoE measurement values of at least one QoE measurement being for different service types, and providing a RAN node configured to perform the above.

[0007] 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 from an OAM system or from an OAM system via a core network (CN), at least one QoE measurement being selected based on the information indicating the continuity of QoE measurement after the inter-RAT handover.

[0008] According to some embodiments of the present application, the information indicating the QoE measurement continuity after inter-RAT handover indicates which QoE measurements for the service type are continued after inter-RAT handover, or indicates the continuation priority order of each QoE measurement for the service type after inter-RAT handover. If there is only one QoE measurement in the set of QoE measurements, the information indicating the QoE measurement continuity after inter-RAT handover is the service type.

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

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

[0011] According to some embodiments of the present application, the processor is configured to select at least one QoE measurement based on the information indicating the QoE measurement continuity, and the transceiver is configured to transmit third information indicating only the configuration of at least one QoE measurement to the target RAN node, and receive second information indicating the configuration of at least one QoE measurement from the target RAN node, where 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 the corresponding service type.

[0012] According to some embodiments of the present application, the transceiver transmits to the target RAN node the third information indicating the configuration of at least one set of QoE measurements and the information indicating the QoE measurement continuity after the RAT - to - RAT handover, and receives from the target RAN node the 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. Exemplary third information further includes a measurement configuration application layer identifier assigned to the UE for each configuration of at least one set of QoE measurements by the RAN node, and the second information further includes a measurement configuration application layer identifier for each configuration of at least one QoE measurement. In one example, the transceiver is configured to receive information indicating the QoE measurements to be released from the target RAN node and transmit the information indicating the QoE measurements to be released to the UE. In another example, the transceiver is configured to receive information indicating the QoE measurements to be continued from the target RAN node and transmit the information indicating the QoE measurements to be continued to the UE. In yet another example, the third information and the information indicating the QoE measurement continuity after the RAT - to - RAT handover are transmitted to the target RAN node via a handover request message or via a source - target transparent container.

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

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

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

[0016] Some embodiments of the present application provide a RAN node, such as an ng-eNB, including a processor and a transceiver coupled to the processor, the transceiver being configured to receive, in response to an inter-RAT handover, from a source RAN node, first information indicating the 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 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 measurement values of the at least one QoE measurement are for different service types.

[0017] In some embodiments of the present application, the transceiver is configured to receive from the source RAN node information indicating QoE measurement continuity 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 QoE measurement continuity after the inter-RAT handover.

[0018] According to some embodiments of the present application, the information indicating QoE measurement continuity after an inter-RAT handover indicates which QoE measurements for the service type are to be continued after the inter-RAT handover, or indicates the continuation priority order of each QoE measurement for the service type after the inter-RAT handover.

[0019] In some embodiments of the present application, 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 first information.

[0020] In some embodiments of the present application, the transceiver is configured to send information indicating the QoE measurements to be released to the source RAN node.

[0021] In some embodiments of the present application, the transceiver is configured to send information indicating the QoE measurements to be continued to the source RAN node.

[0022] In some embodiments of the present application, information indicating QoE measurement continuity after an inter-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 the present 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 to the UE for each configuration of at least one set of QoE measurements by the RAN node, 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 the present application, the configuration of at least one set of QoE measurements indicated in the first information is in a first RAT, and the configuration of at least one QoE measurement indicated in the second information is in a second RAT different from the first RAT.

[0026] Some embodiments of the present application are RAN nodes, such as ng-eNBs, including a processor and a transceiver coupled to the processor, the transceiver being configured to transmit to a target 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 a first RAT identification information, wherein different QoE measurement values of the at least one QoE measurement are for different service types; receiving from the target RAN node a second RAT identification information and information associating at least one QoE measurement with the second RAT identification information; and transmitting to the UE the second RAT identification information and the information associating 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 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 are RAN nodes, such as gNBs, including a processor and a transceiver coupled to the processor, wherein the transceiver is configured to receive, in response to an inter-RAT handover, from a source RAN node, 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 identification information, wherein different QoE measurement values of the at least one QoE measurement are for different service types, and to transmit to the source RAN node information associating at least one QoE measurement identified by a second RAT identification information and the first RAT identification information with the second RAT identification information, and is configured to provide a RAN node.

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

[0032] Some embodiments of the present application are remote devices, such as UEs, including a processor and a transceiver coupled to the processor, wherein the transceiver is configured to receive, from a RAN node, first information indicating a configuration of at least one set of QoE measurements, wherein 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 from the RAN node to a target RAN node, to receive, from the RAN node, second information indicating a configuration of at least one QoE measurement, wherein 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, and is configured to provide a remote device.

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

[0034] In some embodiments of the present application, the transceiver is configured to receive information indicating that at least one other QoE measurement of a set of QoE measurements excluding at least one QoE measurement should be released in response to an inter-RAT handover, and the processor is configured to release at least one other QoE measurement of the 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 the present application, when information indicating QoE measurement continuity after inter-RAT handover is received together with the first information, each configuration of at least one QoE measurement indicated in the second information is identified by the corresponding service type.

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

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

[0039] In view of the above, embodiments of the present application provide at least a technical solution for supporting QoE measurement collection, for example, a method and apparatus for supporting the continuity of QoE measurement collection for inter-RAT mobility within a system. This technical solution takes into account both scenarios: from a source RAN node that supports two or more QoE measurements per service type to a target RAN node that supports only one QoE measurement per service type, and from a source RAN node that supports only one QoE measurement per service type to a target RAN node that supports two or more QoE measurements per service type. Therefore, the present application can facilitate and improve the implementation of NR.

[0040] To describe the manner in which the advantages and features of the present application can be obtained, the description of the present application is made by referring to specific embodiments of the present application shown in the accompanying drawings. These drawings illustrate only exemplary embodiments of the present application and are therefore not considered to limit its scope.

Brief Description of the Drawings

[0041]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

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

[0043] Next, some embodiments of the present application are referred to in detail, and examples thereof 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 (registered trademark) 5G and 3GPP (registered trademark) Long Term Evolution (LTE). It is contemplated that all embodiments in the present application are also applicable to similar technical problems with the development of network architectures and new service scenarios. Furthermore, the terms listed in the present application may change, which should not affect the principles of the present application.

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

[0045] As shown in FIG. 1, the wireless communication system 100 includes at least one BS 101 and at least one UE 102. In particular, the wireless communication system 100 includes, for purposes of illustration, one BS 101 and two terminal devices 102 (e.g., a first UE 102a and a second UE 102b). Although a specific number of BSs and terminal devices are shown in FIG. 1 for simplicity, it is contemplated that the wireless communication system 100 may include more or fewer BSs 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 a wireless communication network, a cellular telephone network, a time-division multiple access (TDMA)-based network, a code-division multiple access (CDMA)-based network, an orthogonal frequency-division multiple access (OFDMA)-based network, an LTE network, a 3GPP (registered trademark)-based network, a 3GPP (registered trademark) 5G network, a satellite communication network, a high-altitude platform network, and / or other communication networks.

[0047] The BS 101 can communicate with a CN node (not shown), e.g., 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. via an interface. The BS may be referred to as an access point, an access terminal, a base, a macrocell, a Node B, an enhanced Node B (eNB), a gNB, a home Node B, a relay node, or a device, or may be described using other terms used in the art. In 5G NR, the BS may also be referred to as a RAN node. Each BS can serve some UEs within a serving area, e.g., a cell or a cell sector, via a wireless communication link. Neighboring BSs can communicate with each other as needed, e.g., during a handover procedure for a UE.

[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 a desktop computer, a laptop computer, a personal digital assistant (PDA), a tablet computer, a smart television (e.g., a television connected to the Internet), a set-top box, a game console, a security system (including a security camera), an in-vehicle computer, a network device (e.g., a router, a switch, and a modem), etc. According to one embodiment of the present application, the terminal device may include a portable wireless communication device, a smartphone, a cellular phone, a flip phone, a device having a subscriber identification 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 wearable devices such as a smartwatch, a fitness band, an optical head-mounted display, etc. Further, the terminal device may be referred to as a subscriber unit, a mobile, a mobile station, a user, a terminal, a mobile terminal, a wireless terminal, a fixed terminal, a subscriber station, a user terminal, or a device, or may be described using other terms used in the art. In this specification (throughout this specification), "UE" is exemplarily used as a typical terminal device to indicate a terminal device, but this should be understood as any type of terminal device.

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

[12] . In the case of management-based QoE measurement activation, OAM sends one or more QoE measurement configurations to the NG-RAN node. The QoE measurement configuration for management-based activation also includes an application layer measurement configuration list and corresponding information for QoE measurement collection. Each application layer measurement configuration is encapsulated within a transparent container. The NG-RAN node selects a UE that meets 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 processed by application layer measurement configuration and measurement reports, which are only supported in the RRC_CONNECTED state. The application layer measurement configuration received by the gNB from the OAM or the CN is encapsulated within a transparent container, which is transferred to the UE as an application layer configuration in an RRCReconfiguration message (there may be multiple configurations within the same message). The application layer measurement reports received from the upper layers of the UE are encapsulated within 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 one MeasurementReportAppLayer message. To enable the transmission of application layer measurement reports that exceed the maximum PDCP SDU size, segmentation of the MeasurementReportAppLayer message may be enabled by the gNB. The measConfigAppLayerId carried in the RRC signaling is used to identify the application layer measurement configuration and reporting between the gNB and the UE. The RRC identifier is mapped to a QoE reference at the gNB. The application layer measurement reports are transferred to the OAM together with the QoE reference. The gNB can release one or more application layer measurement configurations from the UE in one RRCReconfiguration message at any time. Additionally, the UE can be configured by the gNB to report, for a specific application layer measurement configuration, when the QoE measurement session starts or stops.

[0050] Therefore, QoE measurement collection can be activated by two modes, namely, management-based activation and signaling-based activation. In the case of management-based activation, the RAN node, e.g., gNB, receives the configuration directly from the OAM (or OAM system). In the case of signaling-based activation, the RAN node receives signaling containing UE-related QoE configuration from the OAM via the CN. The application layer measurement configuration received by the gNB from the OAM or the CN is encapsulated in a transparent container in Rel-17, which is transferred 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 application layer of the UE 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 QoE measurement continuity for mobility as follows. "The QoE measurement collection continuity for in-system RAT-internal mobility is supported by area range parameters configured by the OAM, and the network is responsible for tracking whether the UE is inside or outside the area range. The UE should continue the ongoing measurements even when leaving 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 send information related to the QoE measurement configuration and / or the configuration of a specific UE to the target NG-RAN node via XnAP or NGAP. In the case of 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. In the case of 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 specific UE can 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, in the handover to the target gNB that supports QoE, the target gNB determines which application layer measurement configurations to maintain and which to release based on, for example, the application layer measurement configuration information received from the source gNB in the Xn / NG signaling. When the UE resumes the connection 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 the QoE measurement collection continuity for in-system RAT mobility. Regarding the QoE measurement collection continuity for between-system RAT mobility, it is expected to be solved in Rel-18. For example, according to RP-213159, "supporting the continuity of legacy QoE measurement jobs for streaming and MTSI services during the inter-RAT handover process [RAN2, RAN3] within 5GC" has been agreed. Related issues to be solved include, but are not limited to, problems caused by the inconsistency of QoE measurement capabilities between two different RATs, for example, the inconsistency between the NR QoE measurement collection capability and the LTE QoE measurement collection capability. The term LTE refers to evolved universal terrestrial radio access (E-UTRA). "LTE" is used for convenience. When the BS is connected to the 5GC, "LTE" can be replaced by "E-UTRA". The RAN node within the in-system RAT is an NG-RAN node. The NG-RAN node provides the NR user plane and control plane protocol termination towards the UE and is either a gNB connected via the NG interface to the 5GC or an ng-eNB that provides the E-UTRA user plane and control plane protocol termination towards the UE and is connected via the NG interface to the 5GC.

[0053] Specifically, NR QoE supports multiple QoE measurements for each service type, and the QoE measurements (including QoE measurement configuration and QoE measurement reporting) are identified by NR QoE identification information, such as a measurement configuration application layer identifier (ID) (currently specified as "measConfigAppLayerId" in the 3GPP (registered trademark) specification). The measurement configuration application layer ID can be carried in radio resource control (RRC) signaling as an RRC identifier for identifying the application layer measurement configuration and reporting between the gNB and the UE. One or more QoE measurement collection jobs can be activated at the UE for each service type, each QoE measurement configuration is uniquely identified by a QoE reference (e.g., a QoE reference ID), and the measConfigAppLayerId is mapped to the QoE reference at the gNB.

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

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

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

[0057] Considering the above, in order to support at least the continuity of QoE measurement collection for in-system RAT mobility, embodiments of the present application provide technical solutions to support QoE measurement collection, in particular, methods and apparatuses to support QoE measurement collection. 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. Those skilled in the art should be well aware that terms, in particular "NR" and "gNB", may change as 3GPP (registered trademark) evolves. Any inter-RAT handover between a RAN node having a RAT that supports two or more QoE measurement collection jobs per service type and another RAN node having a RAT that supports only one QoE measurement collection job per service type causes the same problem, and this problem is solved by the technical solutions disclosed in the embodiments of the present application.

[0058] For example, considering Scenario 1, some embodiments of the present application provide a method that may be implemented by a RAN node (such as a source gNB, etc.) having a RAT that supports two or more QoE measurement collection jobs per service type. An exemplary method includes transmitting, to a UE, first information indicating a configuration of at least one set of QoE measurements, and in response to an inter-RAT handover to a target RAN node (such as an ng-eNB, etc.) having another RAT that supports only one QoE measurement collection job per service type, transmitting, to the UE, second information indicating a configuration of at least one QoE measurement. 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. At least one QoE measurement is selected from at least one set of QoE measurements, and different QoE measurement values of at least one QoE measurement are for different service types.

[0059] Some other embodiments of the present application provide another method 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 receiving, in response to an inter-RAT handover, first information indicating a 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, and transmitting second information indicating a configuration of at least one QoE measurement to the source RAN node. Similarly, 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. 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.

[0060] Some further other embodiments of the present 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 receiving first information indicating a configuration of at least one set of QoE measurements from a RAN node (such as a source gNB), and receiving, in response to an inter-RAT handover from the RAN node to a target RAN node (such as an ng-eNB), second information indicating a configuration of at least one QoE measurement from the RAN node. Similarly, 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. 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.

[0061] Considering Scenario 2, some 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, for example, a source ng-eNB. An exemplary method includes, in response to an inter-RAT handover, transmitting to a target RAN node (for example, 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 identification information (for example, a service type), wherein different QoE measurement values of the at least one QoE measurement are for different service types; receiving, from the target RAN node, a second RAT identification information (for example, measConfigAppLayerId) and information associating the at least one QoE measurement with the second RAT identification information; and transmitting, to the UE, the second RAT identification information and the information associating the at least one QoE measurement with the second RAT identification information.

[0062] Some other embodiments of the present 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, for example, a target gNB. An exemplary method includes, in response to an inter-RAT handover, receiving from a source RAN node (for example, an ng-eNB) having a first RAT that supports only one QoE measurement 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 identification information (for example, a service type), wherein different QoE measurement values of the at least one QoE measurement are for different service types; and transmitting, to the source RAN node, a second RAT identification information (for example, measConfigAppLayerId) and information associating the at least one QoE measurement identified by the first RAT identification information with the second RAT identification information.

[0063] FIG. 2 is a flowchart showing a method for supporting QoE measurement collection in Scenario 1 according to some embodiments of the present application. The method is shown at a system level among a source RAN node, a target RAN node, and a remote device, but those skilled in the art should understand that the method implemented in the source RAN node, the target RAN node, and the remote device may be separately implemented and / or incorporated by other devices having similar functions.

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

[0065] Referring to FIG. 2, the source RAN node can configure at least one set of QoE measurements for a remote device, e.g., a UE, in response to the QoE measurements being activated either by direct configuration from the OAM (not shown) (i.e., management-based activation) or by signaling including UE-related QoE configuration from the OAM via a CN node, e.g., the AMF (i.e., signaling-based activation). 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. For example, at least one set of QoE measurements may include a set of QoE measurements including one or more QoE measurement values for a streaming service. In another example, at least one set of QoE measurements may include a set of QoE measurements including one or more QoE measurement values for an MTSI service. In yet another example, at least one set of QoE measurements may include a first set of QoE measurements including one or more QoE measurement values for a streaming service and a second set of QoE measurements including one or more QoE measurement values for an MTSI service. Similar solutions are applicable 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 particular UE via a CN node, e.g., the AMF, and the CN node sends QoE measurement configuration information to the source RAN node for QoE measurement activation. Exemplary QoE measurement configuration information (also referred to as "CN / OAM QoE measurement configuration information") from the CN or OAM includes the following. - QoE reference: Used to identify QoE measurements between the gNB and the CN or between the gNB and the OAM - Service type: Indicating the service type of the QoE measurement - Container for application layer measurement configuration: Including the application layer measurement configuration, and - Area scope: The area scope for QoE measurement, including a list of cells, a tracking area (TA), a tracking area ID (TAI), or a public land mobile network (PLMN) ID. Regarding the QoE reference (or QoE reference ID), this can be as defined in clause 5.2 of TS 28.405 and is an octet string of size (6). The QoE reference is composed of a mobile country code (MCC), a mobile network code (MNC), and a QMC ID. The MCC and MNC have a trace activation request from its management system for identifying one PLMN including the management system, and the QMC ID is a 3-byte octet string.

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

[0068] Those skilled in the art should well know that the above information elements (IEs) or parameters are merely shown as examples, and these examples may change along with the evolution of 3GPP (registered trademark) specifications. Therefore, they should not be used to unduly limit the protection scope of this application.

[0069] Based on at least one set of received configurations 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, an 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 confirmation response (ACK) message, in step 207.

[0070] In response to the inter-RAT handover, the source RAN node sends, in step 208, for example, in a handover command (for example, MobilityFromNRCommand) message, a second piece of information indicating the configuration of at least one QoE measurement selected from at least one set of QoE measurements to the UE. The configuration of at least one QoE measurement indicated in the second piece of information is in a second RAT different from the first RAT, for example, a RAT that supports only one QoE measurement per service type (for example, LTE QoE). Different QoE measurement values of 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 for the same service type is selected. Therefore, the UE receives the second piece of information indicating the configuration of at least one QoE measurement and continues at least one QoE measurement after the inter-RAT handover. At least one set of other QoE measurements excluding at least one QoE measurement are stopped or released.

[0071] There are various ways regarding how to select at least one QoE measurement having QoE measurement continuity from at least one set of QoE measurements and / or how to indicate QoE measurement continuity to a UE after an inter-RAT handover.

[0072] According to some embodiments of the present application, a mechanism for indicating QoE measurement continuity after an inter-RAT handover is used to determine which QoE measurements for each service type are to be continued after the inter-RAT handover.

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

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

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

[0076] Based on the received inter-RAT QoE continuity indication, in some embodiments of the present application, the source RAN node may either select at least one QoE measurement by itself 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 from at least one set of QoE by the target RAN node (Method 2).

[0077] Figure 3 is a flowchart showing a method for supporting QoE measurement collection using Method 1 in Scenario 1 according to some embodiments of the present application. The method is shown at the system level among the source RAN node, the target RAN node, and the remote device, but those skilled in the art should understand that the methods implemented in the source RAN node, the target RAN node, and the remote device may be separately implemented and / or incorporated by other devices having similar functions. In addition, since the embodiments shown in consideration of Figure 3 are also applicable to Scenario 1, the embodiments shown for Scenario 1 in consideration of Figure 2 are also applicable to Figure 3, and thus the same operations are simplified or omitted in the following description.

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

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

[0080] The source RAN node also receives, from the OAM or the CN, an inter-RAT QoE continuity indication indicating that QoE measurements having, e.g., a QoE reference ID "1" are to be continued after an inter-RAT handover. According to some embodiments of the present application, the source RAN node also transmits, in step 301, the inter-RAT QoE continuity indication to the UE together with the first information.

[0081] For example, the source RAN node provides UE with at least one set of QoE measurements in the first RAT, along with RAT - to - RAT QoE continuity indication, according to the application layer configuration (e.g., AppLayerMeasConfig IE) in the RRC re - configuration message. Each configuration of at least one set of QoE measurements is identified by the first RAT identification information carried in RRC signaling, which can identify the application layer measurement configuration and reporting between the source RAN node and UE, e.g., identified by measConfigAppLayerId. 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 access stratum (AS) layer of UE receives the RAT - to - RAT QoE continuity indication, the AS layer may forward the RAT - to - RAT QoE continuity indication to the application layer of UE.

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

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

[0084] After receiving the configuration of at least one QoE measurement configuration, for example, the configuration of the QoE measurement with QoE reference ID "1", the target RAN node 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. At 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 the handover response message. In the LTE RRC QoE configuration provided by the target RAN node, only the service type, for example, "streaming", is provided without any measConfigAppLayerId.

[0085] After receiving the configuration of at least one QoE measurement in the second RAT, e.g., the LTE RRC QoE configuration of the QoE measurement with QoE reference ID "1", the source RAN node transfers it to the UE in step 308, e.g., in the MobilityFromNRCommand message. That is, corresponding to step 208, the source RAN node transmits, in step 308, second information indicating the configuration of at least one selected QoE measurement to the UE, and the configuration of at least one selected QoE measurement is 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, e.g., the LTE RRC QoE configuration for each service type, the UE can determine which QoE measurements for each service type will be continued after the inter-RAT handover. Accordingly, the UE continues at least one QoE measurement, e.g., continues the QoE measurement for streaming having measConfigAppLayerId "1" mapped to QoE reference ID "1" indicated by the inter-RAT QoE continuity indication. The UE stops or releases other QoE measurements, e.g., stops or releases the QoE measurement for streaming having measConfigAppLayerId "2" mapped to QoE reference ID "2".

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

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

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

[0090] In some embodiments of the present application, the inter - RAT QoE continuity indication may be indicated to the UE in an implicit manner, for example, by transmitting information indicating to release at least one set of other QoE measurements of QoE measurements excluding at least one QoE measurement, for example, in the MobilityFromNRCommand message.

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

[0092] After receiving the MobilityFromNRCommand message, the UE releases the QoE measurements that were indicated to be released, maintains and continues the QoE measurements that are not released after an inter-RAT handover from the source RAN node to the target RAN node, for example, performs QoE measurements and / or sends QoE measurement reports to the target RAN node.

[0093] Method 2 Figure 4 is a flowchart showing a method for supporting QoE measurement collection using Method 2 in Scenario 1 according to some embodiments of the present application. The method is shown at a system level among a source RAN node, a target RAN node, and a remote device, but those skilled in the art should understand that the methods implemented in the source RAN node, the target RAN node, and the remote device may be separately implemented and / or incorporated by other devices having similar functions. In addition, since the embodiments shown in consideration of Figure 4 are also applicable to Scenario 1, the embodiments shown for Scenario 1 in consideration of Figure 2 are also applicable to Figure 4, and thus, the same operations are simplified or omitted in the following description.

[0094] Similarly, the inter-RAT handover is from a source RAN node (e.g., an NR RAN node, a gNB, etc.) having 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, an ng-eNB, etc.) having a second RAT that supports only one QoE measurement per service type.

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

[0096] For example, the source RAN node provides to the UE a configuration of at least one set of QoE measurements in the first RAT by an application layer configuration (e.g., AppLayerMeasConfig IE) within an RRC reconfiguration message, and each configuration of at least one set of QoE measurements is identified by first RAT identification information, e.g., measConfigAppLayerId, carried in RRC signaling that can identify application layer measurement configuration and reporting between the source RAN node and the UE. measConfigAppLayerId is mapped to a QoE reference, e.g., 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 to perform an inter-system RAT handover to the target RAN node in step 403, the source RAN node does not select QoE measurements. Instead, in step 405, the source RAN node transmits to the target RAN node a third piece of information indicating the configuration of at least one set of QoE measurements and an inter-RAT QoE continuity indication, for example, via a handover request message or via a source-target transparent container.

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

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

[0100] Similarly, the target RAN node generates the configuration of at least one QoE measurement in the second RAT, for example, the 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, the LTE RRC QoE configuration, to the source RAN node, together with the corresponding second RAT identification information, for example, measConfigAppLayerId, in, for example, a handover response message. measConfigAppLayerId may be included in the LTE RRC QoE configuration in some embodiments of this application.

[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 with the corresponding measConfigAppLayerId, the source RAN node transfers it to the UE in step 408, for example, in a MobilityFromNRCommand message.

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

[0103] In some other embodiments of the present application, in step 407, the target RAN node may send information indicating the QoE measurements to be released, for example, a QoE measurement release list, to the source RAN node in the handover response message. The QoE measurement release list may also present a QoE deactivation list including a list of QoE reference IDs of the 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 indicating the QoE measurements to be continued and maintained to the source RAN node by including, for example, a QoE measurement maintenance list (or continuity list) for the source RAN node in the handover response message to indicate that the QoE measurements are to be continued and maintained after the inter-RAT handover.

[0105] In some further other embodiments of the present application, the target RAN node may send both a QoE measurement release list and a QoE measurement maintenance list to the source RAN node.

[0106] After the source RAN node receives the QoE measurement release list and / or QoE measurement maintenance list in the handover response message, the source gNB sends the corresponding QoE measurement release list, e.g., measConfigAppLayerToReleaseList, to the UE in step 408 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 send the corresponding QoE measurement maintenance list, e.g., measConfigAppLayerToKeptList, to indicate the QoE measurements to be maintained and continued. 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 measurements indicated in measConfigAppLayerToReleaseList and maintains (continues) other QoE measurements, and / or the UE maintains the QoE measurements in measConfigAppLayerToKeptList and releases other QoE measurements.

[0108] In some other embodiments of the present 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 send the inter-RAT QoE continuity indication generated by 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] FIG. 5 is a flowchart showing a method for supporting QoE measurement collection in Scenario 2 according to some embodiments of the present application. The method is shown at a system level among the source RAN node, the target RAN node, and the remote device, but those skilled in the art should understand that the methods implemented in the source RAN node, the target RAN node, and the remote device may be separately implemented and / or incorporated by other devices having similar functions.

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

[0111] Referring to FIG. 5, the source RAN node can configure at least one QoE measurement for a remote device, e.g., a UE, in response to the QoE measurement being activated either by direct configuration from the OAM (not shown) (i.e., management-based activation) or by signaling including UE-related QoE configuration from the OAM via a CN node, e.g., the 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, the QoE measurements are per service type and are implicitly identified by the service type. For example, at least one QoE measurement may include at least one of a QoE measurement for a streaming service or a QoE measurement for an MTSI service. Similar solutions are applicable to other future service types (if any).

[0112] In step 501, the source RAN node, e.g., the ng-eNB, sends to the UE a configuration of at least one QoE measurement having a first RAT identification information, e.g., a service type. For example, the source RAN node may send a UE application layer configuration (e.g., AppLayerMeasConfig IE) in an RRC reconfiguration message, and the corresponding service type, e.g., a streaming service, is indicated 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, e.g., 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 an 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 a first RAT identification information (hereinafter referred to as indication information), for example, an indication indicating whether the QoE measurement has already been configured for the UE in LTE QoE. The indication information also represents that the QoE measurement is in progress when the inter-RAT handover occurs.

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

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

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

[0117] In addition to the method, embodiments of the present application also propose an apparatus for supporting QoE measurement collection.

[0118] For example, FIG. 6 shows a block diagram of an apparatus 600 for supporting QoE measurement reports according to some other embodiments of the present application.

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

[0120] In this figure, elements such as at least one processor 606, a transmission circuit 604, and a reception circuit 602 are described in the singular, but a plurality is contemplated unless a limitation to the singular is explicitly stated. In some embodiments of the present application, the reception circuit 602 and the transmission circuit 604 may be combined into a single device such as a transceiver. The processor 606 may be a CPU, a DSP, a microprocessor, or the like. In certain embodiments of the present application, the apparatus 600 may further include an input device, a memory, and / or other components.

[0121] In some embodiments of the present application, the non-transitory computer-readable medium 601 may store thereon computer-executable instructions for causing the processor 606 to implement a method for a RAN node as described above, for example, a gNB or an ng-eNB. For example, when executed, the computer-executable instructions cause the processor 606 to interact with the reception circuit 602 and the transmission circuit 604 to perform steps for a RAN node as shown above.

[0122] In some other embodiments of the present application, the non-transitory computer-readable medium 601 may store thereon computer-executable instructions for causing a processor to implement a method for a UE as described above. For example, when executed, the computer-executable instructions cause the processor 606 to interact with the reception circuit 602 and the transmission circuit 604 to perform steps for a UE as shown above.

[0123] FIG. 7 is a block diagram of an apparatus for supporting QoE measurement collection according to some embodiments of the present application.

[0124] Referring to FIG. 7, an apparatus 700, such as a UE or a RAN node, such as 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, a DSP, a microprocessor, or the like.

[0125] According to some embodiments of the present application, when the apparatus 700 is a RAN node, such as a source gNB, the apparatus transmits to the UE first information indicating a configuration of at least one set of QoE measurements, wherein 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, transmits to the UE second information indicating a configuration of at least one QoE measurement, wherein 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.

[0126] According to some embodiments of the present application, when the apparatus 700 is a RAN node, for example, a target ng-eNB, the apparatus receives, in response to an inter-RAT handover, from a source RAN node, 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 transmits to the source RAN node second information indicating a 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 measurement values of at least one QoE measurement are for different service types, and is configured to perform the above.

[0127] According to some embodiments of the present application, when the apparatus 700 is a RAN node, for example, a source ng-eNB, the apparatus transmits, in response to an inter-RAT handover, 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, where different QoE measurement values of at least one QoE measurement are for different service types, receives from the target RAN node second RAT identification information and information associating at least one QoE measurement with the second RAT identification information, and transmits to the UE the second RAT identification information and the information associating at least one QoE measurement with the second RAT identification information, and is configured to perform the above.

[0128] According to some embodiments of the present application, when the apparatus 700 is a RAN node, for example, a target gNB, the apparatus receives, in response to an inter-RAT handover, from a source RAN node, 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 identification information, wherein different QoE measurement values of the at least one QoE measurement are for different service types, and transmits to the source RAN node information associating at least one QoE measurement identified by a second RAT identification information and the first RAT identification information with the second RAT identification information.

[0129] According to some embodiments of the present application, when the apparatus 700 is a UE, the apparatus receives from a RAN node first information indicating a configuration of at least one set of QoE measurements, wherein 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 from the RAN node to a target RAN node, receives from the RAN node second information indicating a 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 measurement values of the at least one QoE measurement are for different service types.

[0130] The method according to an embodiment of the present application can also be implemented on a programmed processor. However, the controller, flowchart, and module can also be implemented on a general-purpose or special-purpose computer, a programmed microprocessor or microcontroller and peripheral integrated circuit elements, an integrated circuit, an electronic or logic circuit of hardware, for example, an individual element circuit, a programmable logic device, etc. Generally, any device capable of implementing the flowchart shown in the figure may be used to implement the processor function of the present application. For example, an embodiment of the present application provides an apparatus including a processor and a memory. The 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 as described above or other methods according to an embodiment of the present application.

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

[0132] Although this application has been described with its specific embodiments, it is clear that many alternative, modified, and variant forms may be apparent to those skilled in the art. For example, the various components of the embodiments may be exchanged, added, or replaced in other embodiments. Also, not all elements of each figure are necessary for the operation of the disclosed embodiments. For example, those skilled in the art of the disclosed embodiments will be able to create and use the teachings of this application by simply adopting the elements of the independent claims. Therefore, the embodiments of this application described herein are intended to be illustrative rather than limiting. Various changes may be made without departing from the spirit and scope of this application.

Explanation of Reference Numerals

[0133] 100 Wireless communication system 101 BS 102 UE, terminal device 102a First UE 102b Second UE 600 Device 601 Non-transitory computer-readable medium 602 Receiving circuit 604 Transmitting circuit 606 Processor 700 Device 702 Processor 704 Transceiver 706 Receiving circuit 708 Transmitting circuit

Claims

1. A radio access network (RAN) node, comprising: a processor; and a transceiver coupled to the processor, the transceiver being configured to:[ transmit, to a user equipment (UE), first information indicating a configuration of at least one set of quality of experience (QoE) measurements, each set of QoE measurements including one or more QoE measurement values for the same service type, and different sets of QoE measurements being for different service types; and in response to a radio access technology (RAT) - to - RAT handover to a target RAN node, transmit, to the UE, second information indicating a configuration of at least one QoE measurement, the at least one QoE measurement being selected from the at least one set of QoE measurements, and different QoE measurement values of the at least one QoE measurement being for different service types.[ The RAN node is configured to perform the above.[

2. The transceiver is further configured to:[ receive, from an operation, administration, and maintenance (OAM) system or from the OAM system via a core network (CN), information indicating QoE measurement continuity after an RAT - to - RAT handover, the at least one QoE measurement being selected based on the information indicating QoE measurement continuity after the RAT - to - RAT handover.[ The RAN node according to claim 1, further configured to perform the above.[

3. The information indicating QoE measurement continuity after an RAT - to - RAT handover indicates which QoE measurements for the service type are to be continued after the RAT - to - RAT handover, or indicates the continuation priority order of each QoE measurement for the service type after the RAT - to - RAT handover. The RAN node according to claim 2.[

4. The processor is configured to:[ select the at least one QoE measurement based on the information indicating QoE measurement continuity.[ The transceiver is configured to:[ transmit, to the target RAN node, third information indicating only the configuration of the at least one QoE measurement.[ ​ Receiving, from the target RAN node, the second information indicating the configuration of the at least one QoE measurement, wherein the configuration of the at least one QoE measurement indicated in the second information is generated or updated based on the configuration of the at least one QoE measurement indicated in the third information The RAN node according to claim 2, configured to perform the above **Claim 5** The transceiver is Sending, to the target RAN node, third information indicating a configuration of at least one set of the QoE measurements and the information indicating QoE measurement continuity after RAT - to - RAT handover Receiving, from the target RAN node, the second information indicating the configuration of the at least one QoE measurement, wherein the configuration of the at least one QoE measurement indicated in the second information is generated or updated based on the configuration of at least one set of the QoE measurements indicated in the third information The RAN node according to claim 2, configured to perform the above **Claim 6** The configuration of at least one set of the QoE measurements indicated in the first information is in a first RAT, and the configuration of the at least one QoE measurement indicated in the second information is in a second RAT different from the first RAT, the RAN node according to claim 1 **Claim 7** A radio access network (RAN) node, comprising A processor; and A transceiver coupled to the processor, the transceiver being Responsive to a radio access technology (RAT) - to - RAT handover, receiving, from a source RAN node, first information indicating a configuration of at least one set of quality - of - experience (QoE) measurements, wherein 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 Sending, to the source RAN node, second information indicating a configuration of at least one QoE measurement, wherein the at least one QoE measurement is selected from at least one set of the QoE measurements, and different QoE measurement values of the at least one QoE measurement are for different service types The RAN node configured to perform the above

8. A radio access network (RAN) node comprising: a processor; and a transceiver coupled to the processor, the transceiver being configured to: in response to a radio access technology (RAT) - to - RAT handover, transmit to a target RAN node information indicating at least one quality of experience (QoE) measurement and information indicating that the at least one QoE measurement is configured for a user equipment (UE) having a first RAT identification information, wherein different QoE measurement values of the at least one QoE measurement are for different service types; receive from the target RAN node a 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. The RAN node is configured to perform the above - mentioned operations.

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

10. The RAN node according to claim 8, wherein the information associating the at least one QoE measurement with the second RAT identification information is implicitly indicated by the second RAT identification information.

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

12. A remote device comprising: a processor; and a transceiver coupled to the processor, the transceiver being configured to: receive from a radio access network (RAN) node first information indicating a configuration of at least one set of quality of experience (QoE) measurements, wherein 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; Receiving, from the RAN node, second information indicating a configuration of at least one QoE measurement in response to an inter-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 the QoE measurements, and different QoE measurement values of the at least one QoE measurement are for different service types A remote device configured to perform the above.

13. The transceiver is Receiving information indicating QoE measurement continuity after an inter-RAT handover, together with at least one of the first information or the second information Continuing the at least one QoE measurement after the inter-RAT handover based on the information indicating QoE measurement continuity after the inter-RAT handover The remote device according to claim 12, further configured to perform the above.

14. The transceiver is Receiving information indicating that the at least one QoE measurement should be continued in response to the inter-RAT handover Configured as such The processor is Configured to continue the at least one QoE measurement after the inter-RAT handover The remote device according to claim 12, configured to perform the above.

15. The configuration of the at least one set of the QoE measurements indicated in the first information is in a first RAT, and the configuration of the at least one QoE measurement indicated in the second information is in a second RAT different from the first RAT. The remote device according to claim 12.

Images