Apparatus and method for communication

Abstract

Embodiments of the present disclosure provide a solution for quality of experience (QoE) measurement configuration. In the solution, a terminal device receives, from a first network device, configuration information to handover a connection from the first network device to a second network device. The configuration information comprises a second configuration of quality of experience measurement associated with the second network device. The second configuration is different from a first configuration of quality of experience measurement associated with the first network device. The terminal device performs the quality of experience measurement based on the second configuration after the handover.

Description

Technical Field

[0001] The exemplary embodiments of this disclosure generally relate to the field of communication technology, and more specifically, to apparatus and methods for configuring quality of experience (QoE) measurement. Background Technology

[0002] Communication systems are widely deployed to provide various telecommunications services. For example, QoE measurement is already supported. In some cases, the QoE Measurement Collection (QMC) function enables the collection of application layer measurements from User Equipment (UE). To perform QoE measurement or the QMC function, a QoE measurement configuration can be configured. Work on QoE measurement configuration is underway. Summary of the Invention

[0003] Typically, embodiments of this disclosure provide methods, apparatus, and computer storage media for configuring QoE measurements.

[0004] In a first aspect, a terminal device is provided, the terminal device comprising: a processor configured to cause the terminal device to: receive configuration information from a first network device to switch a connection from the first network device to a second network device, the configuration information including a second configuration of a quality of experience measurement associated with the second network device, the second configuration being different from a first configuration of a quality of experience measurement associated with the first network device; and perform a quality of experience measurement based on the second configuration after the switch.

[0005] In a second aspect, a first network device is provided, the first network device comprising: a processor configured to cause the first network device to: send a request to a second network device for switching from a first connection to a second connection, the first connection being between a terminal device and the first network device, the second connection being between the terminal device and the second network device, the request including a first configuration of a quality of experience measurement; receive a response from the second network device to the request, the response including a second configuration of a quality of experience measurement associated with the first configuration; and send configuration information of the switching to the terminal device, the configuration information including the second configuration.

[0006] In a third aspect, a second network device is provided, the second network device comprising: a processor configured to cause the second network device to: receive from a first network device a request to switch from a first connection to a second connection, the first connection being between a terminal device and the first network device, the second connection being between the terminal device and the second network device, the request including a first configuration for quality of experience measurement; determine a second configuration for quality of experience measurement based on the first configuration; and send a response to the first network device to the request, the response including the second configuration for quality of experience measurement.

[0007] In a fourth aspect, a first network device is provided, comprising: a processor configured to cause the first network device to: send priority information of at least one configured quality of experience measurement associated with a terminal device to a third network device, wherein a switch from a first connection to a second connection is to be performed, the first connection being between the terminal device and the first network device, and the second connection being between the terminal device and the third network device.

[0008] In a fifth aspect, a third network device is provided, comprising: a processor configured to cause the third network device to: receive priority information of at least one configured quality of experience measurement associated with a terminal device from a first network device, wherein a switch from a first connection to a second connection is to be performed, the first connection being between the terminal device and the first network device, and the second connection being between the terminal device and the third network device.

[0009] In a sixth aspect, a communication method performed by a terminal device is provided. The method includes: receiving configuration information from a first network device for switching a connection from the first network device to a second network device, the configuration information including a second configuration of a quality of experience (QA) measurement associated with the second network device, the second configuration being different from a first configuration of a QA measurement associated with the first network device; and performing a QA measurement based on the second configuration after the switch.

[0010] In a seventh aspect, a communication method performed by a first network device is provided. The method includes: sending a request to a second network device for switching from a first connection to a second connection, the first connection being between a terminal device and the first network device, and the second connection being between the terminal device and the second network device, the request including a first configuration of a quality of experience measurement; receiving a response from the second network device to the request, the response including a second configuration of the quality of experience measurement, the second configuration being associated with the first configuration; and sending switching configuration information to the terminal device, the configuration information including the second configuration.

[0011] In an eighth aspect, a communication method performed by a second network device is provided. The method includes: receiving from a first network device a request to switch from a first connection to a second connection, the first connection being between a terminal device and the first network device, and the second connection being between the terminal device and the second network device, the request including a first configuration for a quality of experience measurement; determining a second configuration for the quality of experience measurement based on the first configuration; and sending a response to the request to the first network device, the response including the second configuration for the quality of experience measurement.

[0012] In a ninth aspect, a communication method performed by a first network device is provided. The method includes sending priority information of at least one configuration of a quality of experience measurement associated with a terminal device to a third network device, wherein a switch from a first connection to a second connection is to be performed, the first connection being between the terminal device and the first network device, and the second connection being between the terminal device and the third network device.

[0013] In a tenth aspect, a communication method performed by a third network device is provided. The method includes: receiving priority information from a first network device of at least one configured quality of experience measurement associated with a terminal device, wherein a switch from a first connection to a second connection is to be performed, the first connection being between the terminal device and the first network device, and the second connection being between the terminal device and the third network device.

[0014] In an eleventh aspect, a computer-readable medium is provided that stores instructions which, when executed on at least one processor, cause at least one processor to perform the method according to the sixth, seventh, eighth, ninth, or tenth aspect.

[0015] Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0016] The above and other objects, features and advantages of this disclosure will become more apparent from the accompanying drawings, which describe some exemplary embodiments of this disclosure in more detail, wherein: Figure 1 An example communication environment in which example embodiments of this disclosure may be implemented is shown; Figure 2 Signaling flows for QoE measurement configuration according to some embodiments of this disclosure are shown; Figure 3 The signaling flow used for QoE measurement reporting is shown; Figures 4 to 11 Further example signaling flows for QoE measurement configuration according to some embodiments of this disclosure are shown respectively; Figure 12 The following is illustrated: a signaling flow for priority information communication between network devices according to some embodiments of the present disclosure; Figure 13 Signaling flows for QoE measurement according to some embodiments of this disclosure are shown; Figure 14 A flowchart is shown illustrating a method implemented at a terminal device according to some example embodiments of the present disclosure; Figure 15 A flowchart is shown illustrating a method implemented at a first network device according to some example embodiments of the present disclosure; Figure 16 A flowchart is shown illustrating a method implemented at a second network device according to some example embodiments of the present disclosure; Figure 17 A flowchart is shown illustrating a method implemented at a first network device according to some example embodiments of the present disclosure; Figure 18 A flowchart is shown illustrating a method implemented at a third network device according to some example embodiments of the present disclosure; Figure 19 A simplified block diagram of an apparatus suitable for implementing an example embodiment of the present disclosure is shown.

[0017] In all the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0018] The principles of this disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described for illustrative purposes only and to help those skilled in the art understand and implement this disclosure, and do not imply any limitation on the scope of this disclosure. The embodiments described herein can be implemented in various ways other than those described below.

[0019] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0020] As used herein, the term "terminal device" refers to any device with wireless or wired communication capabilities. Examples of terminal devices include, but are not limited to, user equipment (UE), personal computers, desktop computers, mobile phones, cellular phones, smartphones, personal digital assistants (PDAs), portable computers, tablets, wearable devices, Internet of Things (IoT) devices, ultra-reliable and low-latency communication (URLLC) devices, Internet of Everything (IoE) devices, machine-type communication (MTC) devices, devices on vehicles used for V2X communication (where X refers to pedestrians, vehicles, or infrastructure / networks), devices used for integrated access and backhaul (IAB), space vehicles or air vehicles in non-terrestrial networks (NTNs) including satellites and high-altitude platforms (HAPs) covering unmanned aerial vehicle systems (UAS), extended reality (XR) devices including different types of reality (such as augmented reality (AR), mixed reality (MR), and virtual reality (VR)), unmanned aerial vehicles (UAVs) commonly referred to as drones (which are aircraft without any human pilots), devices on high-speed trains (HSTs), or image capture devices such as digital cameras, sensors, gaming devices, music storage and playback devices, or internet devices that enable wireless or wired internet access and browsing, etc. "Terminal equipment" can also have "multicast / broadcast" characteristics to support public safety and mission-critical applications, V2X applications, transparent IPv4 / IPv6 multicast delivery, IPTV, smart TV, radio services, software delivery over wireless, group communications, and IoT applications. It can also incorporate one or more Subscriber Identity Modules (SIMs), such as in the case of multi-SIM. The term "terminal equipment" is used interchangeably with UE, mobile station, subscriber station, mobile terminal, user terminal, or wireless device.

[0021] The term "network device" refers to a device that provides or hosts a cell or coverage area that terminal devices can communicate with. Examples of network devices include, but are not limited to, NodeB (or NB), evolved NodeB (eNodeB or eNB), next-generation NodeB (gNB), Transmit / Receive Point (TRP), Remote Radio Unit (RRU), Radio Head (RH), Remote Radio Head (RRH), IAB node, low-power nodes such as femtonodes, piconodes, and reconfigurable smart surfaces (RIS), etc.

[0022] Terminal devices or network devices can have artificial intelligence (AI) or machine learning capabilities. It typically includes a model that has been trained from a large amount of data collected from a specific function and can be used to predict some information.

[0023] The terminal or network device can operate on several frequency ranges, such as FR1 (e.g., 450 MHz to 6000 MHz), FR2 (e.g., 24.25 GHz to 52.6 GHz), bands greater than 100 GHz, and megahertz (THz). It can also operate on licensed / unlicensed / shared spectrum. In multiple radio dual connectivity (MR-DC) applications, the terminal device can have more than one connection to the network device. The terminal or network device can operate in full-duplex, flexible-duplex, and cross-split-duplex modes.

[0024] The embodiments of this disclosure can be executed in test equipment, such as a signal generator, signal analyzer, spectrum analyzer, network analyzer, test terminal device, test network device, or channel simulator. In some embodiments, the terminal device can be connected to a first network device and a second network device. One of the first network device and the second network device can be a master node, and the other can be a slave node. The first network device and the second network device can use different Radio Access Technologies (RATs). In some embodiments, the first network device can be a first RAT device, and the second network device can be a second RAT device. In some embodiments, the first RAT device is an eNB, and the second RAT device is a gNB. Information related to different RATs can be sent from at least one of the first network device or the second network device to the terminal device. In some embodiments, first information can be sent from the first network device to the terminal device, and second information can be sent directly or via the first network device from the second network device to the terminal device. In some embodiments, information related to the configuration of the terminal device configured by the second network device can be sent via the first network device from the second network device. Information related to the reconfiguration of the terminal device configured by the second network device can be sent directly or via the first network device from the second network device to the terminal device.

[0025] As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term “comprising” and its variations should be understood as open-ended terms meaning “including, but not limited to.” The term “based on” should be understood as “at least partially based on.” The terms “one embodiment” and “embodiment” should be understood as “at least one embodiment.” The term “another embodiment” should be understood as “at least one other embodiment.” The terms “first,” “second,” etc., can refer to different or the same objects. Further explicit and implicit definitions may be included below.

[0026] In some examples, values, processes, or devices are referred to as “best,” “lowest,” “highest,” “minimum,” “maximum,” etc. It should be understood that such descriptions are intended to indicate that a choice can be made among many functional alternatives used, and that such a choice does not need to be better, smaller, higher, or more preferred than other choices.

[0027] As used herein, the terms "resource," "transmission resource," "uplink resource," or "downlink resource" can refer to any resource used to perform communication, such as resources in the time domain, frequency domain, spatial domain, code domain, or any other resource used to implement communication. In the following, unless explicitly stated otherwise, resources in the frequency and time domains will be used as examples of transmission resources used to describe some exemplary embodiments of this disclosure. Note that the exemplary embodiments of this disclosure are equally applicable to other resources in other domains.

[0028] As used herein, the term "QoE configuration" or "QoE measurement configuration" may refer to the configuration of QoE measurements, which may be an application layer measurement configuration received by the gNB from Operation and Maintenance (OAM) or the core network (CN). As used herein, the term "QoE report" or "QoE measurement report" may refer to an application layer measurement report received from the UE's application layer.

[0029] Figure 1 A schematic diagram of an example communication environment 100 in which exemplary embodiments of the present disclosure may be implemented is shown. In the communication environment 100, a plurality of communication devices, including terminal device 110 and network device 120 (also referred to as first network device 120), network device 130 (also referred to as second network device 130), ... and network device 140 (also referred to as third network device 140), can communicate with each other.

[0030] exist Figure 1 In the example, terminal device 110 can be a UE, and the first network device 120, the second network device 130, and the third network device 140 can be base stations serving the UE. The service area of ​​the network devices can be referred to as a cell. For example, the service area of ​​the first network device 120 is cell 122, the service area of ​​the second network device 130 is cell 132, and the service area of ​​the third network device 140 is cell 142.

[0031] In some embodiments, the multiple network devices in the communication environment 100 may be the same or different. In an example, the first network device 120 may be a New Radio (NR) network node, such as a gNB or a Long Term Evolution (LTE) network node. The first network device 120 may provide NR user plane and control plane protocol termination to the terminal device 110 and may connect to the fifth-generation core network (5GC) via a Next Generation (NG) interface. The second network device 130 may be an Evolved Network Node, such as an eNB or a Next Generation Evolved Node B (ng-eNB). The second network device 130 may provide Evolved Universal Mobile Telecommunications System Area Radio Access (E-UTRA) user plane and control plane protocol termination to the terminal device 110 and may connect to the 5GC via an NG interface. In some embodiments, the third network device 140 may be an NR network node (such as a gNB) or any other suitable network device.

[0032] In the following description, for illustrative purposes, some example embodiments are described in which the first network device 120 and the third network device 140 operate as NR network nodes, and the second network device 130 operates as an evolved NR network node. However, in some example embodiments, the operations described in connection with NR network nodes may be implemented at different network nodes or other devices, and the operations described in connection with evolved NR network nodes may be implemented at another network node or other device.

[0033] As shown in the figure, terminal device 110 is currently served by cell 122 of first network device 120. In this scenario, cell 122 can be referred to as the serving cell, and first network device 120 can be referred to as the serving network device or serving network node. In a handover scenario, cell 132 or cell 142 can be referred to as the candidate cell for handover, and second network device 130 or third network device 140 can be referred to as the candidate network device.

[0034] In some example embodiments, terminal device 110 may move to another cell. For example, if terminal device 110 moves to cell 132 of second network device 130, a handover or cell handover may occur. After the handover, cell 132 becomes the serving cell, and cell 122 may become a candidate cell. It should be understood that, under different circumstances, any cell can become a serving cell or a candidate cell.

[0035] In some embodiments, if terminal device 110 moves from cell 122 of gNB to cell 132 of eNB or from cell 132 to cell 122, the handover may be referred to as an "inter-RAT handover". As used herein, the term "inter-system" may refer to a system supporting a fifth-generation core network (5GC). The term "inter-RAT" may refer to an interaction between NR and LTE.

[0036] In the communication environment 100, network device 120, network device 130 or network device 140 and terminal device 110 can communicate data and control information with each other. Network device 120, network device 130 and network device 140 can also communicate with each other.

[0037] It should be understood that Figure 1 The number of devices and their connections shown are for illustrative purposes only and do not imply any limitation. Communication environment 100 may include any suitable number of devices configured to implement the exemplary embodiments of this disclosure. Although not shown, it should be understood that one or more additional devices may be located in a cell, and one or more additional cells may be deployed in communication environment 100. Note that although shown as a network device, network device 120, network device 130, or network device 140 may be another device besides a network device. Although illustrated as a terminal device, terminal device 110 may be another device besides a terminal device.

[0038] In the following description, for illustrative purposes, some example embodiments are described in which terminal device 110 operates as a UE and network devices 120, 130, and 140 operate as base stations. However, in some example embodiments, the operations described in connection with the terminal device can be implemented at the network device or other devices, and the operations described in connection with the network device can be implemented at the terminal device or other devices.

[0039] In some example embodiments, if terminal device 110 is a terminal device and network device 120, network device 130, or network device 140 is a network device, then the link from network device 120, network device 130, or network device 140 to terminal device 110 is referred to as a downlink (DL), and the link from terminal device 110 to network device 120, network device 130, or network device 140 is referred to as an uplink (UL). In the DL, network device 120, network device 130, or network device 140 is a transmitting (TX) device (or transmitter), and terminal device 110 is a receiving (RX) device (or receiver). In the UL, terminal device 110 is a TX device (or transmitter), and network device 120, network device 130, or network device 140 is an RX device (or receiver).

[0040] The communications in the communication environment 100 can conform to any suitable standard, including but not limited to Global System for Mobile Communications (GSM), Long Term Evolution (LTE), LTE-E Evolution, LTE-A Advanced, New Radio (NR), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), GSM EDGE Radio Access Network (GERAN), Machine Type Communication (MTC), etc. Embodiments of this disclosure can be implemented according to any generation of communication protocols currently known or developed in the future. Examples of communication protocols include, but are not limited to, first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G) communication protocols, 5.5G, 5G Advanced networks, or sixth-generation (6G) networks.

[0041] As mentioned above, QoE measurement configuration is already supported. In some cases, for Radio Resource Control (RRC) _CONNECTED (connected) state mobility, the source gNB can send (multiple) QoE measurement configurations and / or information related to (multiple) configurations for a specific UE to the target gNB via an interface such as the Xn Application Protocol (XnAP) or the Next Generation Application Protocol (NGAP). The XnAP can be an interface between two NG Radio Access Networks (RANs). The NGAP can be an interface between the gNB or NG-eNB and the Access and Mobility Management Function (AMF).

[0042] In some cases, QoE measurement can be signaling-based QoE measurement (also known as signaling-based QoE) or management-based QoE measurement (also known as management-based QoE).

[0043] For signaling-based QoE measurements, the OAM initiates QoE measurement activation for a specific UE via the 5GC, and the gNB receives one or more QoE measurement configurations via the signaling associated with the UE. The activated QoE measurement configuration for signaling-based activation includes a list of application-layer measurement configurations and corresponding information for QoE measurement collection, such as the QoE reference, service type, Measurement Collection Entity (MCE) Internet Protocol (IP) address, slice range, area range, Minimized Drive Test (MDT) alignment information, and an indication of available RAN-visible QoE metrics. For RRC_CONNECTED state mobility, for signaling-based QoE, the service type, QoE reference, MCE IP address, measurement configuration application-layer ID, MDT alignment information, area range, QMC slice support list, and measurement status are transmitted to the target gNB.

[0044] For managed QoE measurement activation, OAM directly sends one or more QoE measurement configurations to the gNB. The managed-activated QoE measurement configuration also includes a list of application-layer measurement configurations and corresponding information for QoE measurement collection. The gNB selects (or more) UEs that meet the required QoE measurement capabilities, area range, and slice range. For RRC_CONNECTED state mobility, for managed QoE, the service type, measurement configuration application-layer ID, MCE IP address, and QoE measurement status are transmitted to the target gNB.

[0045] For RRC_INACTIVE (inactive) state mobility, when a specific UE returns to the RRC_CONNECTED state, multiple QoE measurement configurations for that specific UE can be retrieved from the gNB hosting the UE context. Multiple sets of QoE measurement configurations can be supported during mobility.

[0046] For signaling-based QoE, when switching to a target gNB that supports QoE measurement collection, the target gNB determines, for example, which application layer measurement configurations should be retained or released based on application layer measurement configuration information received from the source gNB in ​​Xn / NG signaling.

[0047] A proposed feature allows the UE to maintain and continue measurements for only one configuration for the service types supported in LTE during a handover (HO) from NR to LTE / 5GC. It also proposes that, for an HO from LTE / 5GC to NR, the UE can maintain and continue measurements for the ongoing configuration for the service types supported in NR.

[0048] In some cases, inter-RAT handover is supported. That is, interaction between NR and LTE is supported. However, for intra-system inter-RAT handover, how to configure QoE measurements needs to be considered.

[0049] In some mechanisms, QoE measurement continuity from NR to LTE / 5GC and vice versa can be supported by the current area range of the QMC Information Element (IE). In the context of QoE measurement continuity during HOs within 5GC-RAT, scenarios where the UE switches from NR to LTE / 5GC and then back to NR are not considered. HOs from LTE / 5GC to NR can be supported without introducing any new IEs. For HOs from LTE / 5GC to NR, there is no impact on RAN3. From NR to LTE, the source node decides which QoE configuration to retain.

[0050] However, when the UE performs a handover from the gNB to the ng-eNB, QoE mobility was supported in previous meetings. Due to the limitations of the ng-eNB, only one QoE configuration can be passed from the gNB to the ng-eNB. How to select this unique QoE configuration needs to be addressed. Furthermore, the UE should release any other untransmitted QoE configurations. When and how to perform this release should be discussed.

[0051] The principles and implementation methods of this disclosure will now be described in detail with reference to the accompanying drawings.

[0052] To address at least some of the aforementioned or other potential problems, a solution regarding QoE measurement configuration is proposed. According to an embodiment of this disclosure, a first network device sends a request to a second network device to switch from a first connection to a second connection, the first connection being between a terminal device and the first network device, and the second connection being between the terminal device and the second network device. The request includes a first configuration for quality of experience measurement. The first network device receives a response to the request from the second network device. This response includes a second configuration for quality of experience measurement. The second configuration is associated with the first configuration. For example, the second configuration is determined by the second network device based on the first configuration. The first network device sends switchover configuration information to the terminal device, which includes the second configuration. The terminal device receives the second configuration and performs QoE measurement based on the second configuration. In this way, the second configuration for QoE measurement can be configured for the terminal device.

[0053] refer to Figure 2 This illustrates a signaling flow 200 for QoE measurement configuration according to some embodiments of the present disclosure. For purposes of discussion, reference will be made, for example, by using terminal device 110, first network device 120, and second network device 130. Figure 1 Discuss signaling flow 200.

[0054] In the following description, it is assumed that the first network device 120 can operate as an NR network node and the second network device 130 can operate as an evolved NR network node. It should be understood that in some embodiments, the first network device 120 and the second network device 130 may be different network devices or network nodes.

[0055] In signaling flow 200, it is assumed that terminal device 110 is currently serving in cell 122 of first network device 120. First network device 120 may be referred to as source network device. It is also assumed that cell 132 of second network device 130 is a cell used for handover. Second network device 130 may be referred to as target network device.

[0056] In operation, first network device 120 sends (210) a request to second network device 130 to switch from a first connection to a second connection, the first connection being between terminal device 110 and first network device 120, and the second connection being between terminal device 110 and second network device 130. This request includes a first configuration for quality of experience measurements. Second network device 130 receives (220) the first configuration. As used herein, the term “request for a switch from a first connection to a second connection” may be referred to as a “switching request” or a “switching request message” or a “switching request message”.

[0057] In some embodiments, the first network device 120 may determine a first configuration for QoE measurement from a plurality of configurations for QoE measurement configured by the first network device 120.

[0058] In some embodiments, the configuration of a QoE measurement among multiple QoE measurements can be an application-layer measurement configuration received by the first network device 120 from OAM or CN. This configuration can be encapsulated in a transparent container. This configuration can be forwarded to the end device 110 as an application-layer configuration in an RRCReconfiguration message. One or more QoE measurement configurations can exist within a single RRCReconfiguration message. For example, IEAppLayerMeasConf can indicate the configuration of the application-layer measurement. Table 1 shows an example of an AppLayerMeasConf IE.

[0059] Table 1

[0060] In some embodiments, the first network device 120 may select a first configuration from multiple configurations based on priority information of multiple configurations. Priority information may come from OAM and / or Application Function (AF) and other information. For example, the first network device 120 may select the QoE configuration with the highest priority.

[0061] Priority information can be included in auxiliary information such as QoE measurement IEs within the UE application layer measurement configuration information. The presence of auxiliary information for QoE measurement IEs can be zero.

[0062] In the example embodiment, priority information can be an integer. For example, a priority number can be assigned to each QoE configuration. The IE type and reference of the auxiliary information for QoE measurement IE can be integers (0…15…). In one option, the IE can indicate the priority information of the QoE configuration. The smaller the integer, the higher the priority. It is used for QoE reporting of RAN overload, where the terminal device 110 determines which reports to discard and select the QoE configuration for inter-RAT handover when the terminal device 110's QoE buffer is full in an idle or inactive state. In another option, the IE can indicate the priority information of the QoE configuration. The larger the integer, the higher the priority. It is used for QoE reporting of RAN overload, where the terminal device 110 determines which reports to discard and select the QoE configuration for inter-RAT handover when the terminal device 110's QoE buffer is full in an idle or inactive state.

[0063] In another embodiment, the priority information can be an enumeration type, such as low, medium, high. One of these priority levels can be assigned from each QoE configuration. The IE type and reference for auxiliary information of the QoE measurement IE can be an enumeration (high, medium, low), an enumeration (high, low), or an enumeration (high, ...). The IE can indicate the priority information of the QoE configuration. A lower bound of an integer. It is used for QoE reporting in RAN overload, where terminal device 110 determines which reports to discard and selects the QoE configuration for inter-RAT handover when the terminal device 110's QoE buffer is full in idle or inactive states.

[0064] In another embodiment, priority information can be an enumeration type, such as true and optional false. For example, if the enumeration type does not exist, it means that the type is false. In this case, such an enumeration type can be assigned to each QoE configuration. For example, "true" can indicate that the corresponding QoE configuration has a high priority, or something else. The IE type and reference of the auxiliary information for QoE measurement IE can be an enumeration (true, ...). This IE can define whether the QoE configuration is high. It is used for QoE reporting in RAN overload, where the terminal device 110 determines which reports to discard and select the QoE configuration for inter-RAT handover when the terminal device 110's QoE buffer is full in an idle or inactive state.

[0065] Alternatively or additionally, in some embodiments, the first network device 120 may select a first QoE configuration from multiple configurations based on additional information. For example, the first QoE configuration may be selected based on the corresponding service type of the multiple configurations. For example, there may be some services that the second network device 130 does not support. The first network device 120 may first select services supported by the second network device 130, and then select the first QoE configuration based on priority information.

[0066] In some embodiments, the first network device 120 may select a first QoE configuration based on multiple time points, with multiple configurations configured at multiple time points. For example, the earlier the QoE configuration is selected, the lower its priority is.

[0067] In some embodiments, the first network device 120 may select a first QoE configuration based on the respective sizes of multiple configurations. For example, the first network device 120 may select a first QoE configuration with an OCTET STRING that is smaller than a threshold size (such as 1000 or any other suitable size).

[0068] It should be understood that the first network device 120 may select the first configuration based on any combination of the parameters or information described above and any other suitable parameters or information. The scope of this disclosure is not limited in this respect.

[0069] In some embodiments, QoE measurement or QoE measurement collection can be used for Hypertext Transfer Protocol (HTTP) Dynamic Adaptive Streaming (DASH) streaming services, Internet Protocol (IP) Multimedia Subsystem (IMS) Multimedia Telephony Service (MTSI), and / or Virtual Reality (VR) services. For DASH, MTSI, and VR, QoE measurement collection can be supported in the RRC_CONNECTED state, unless the application data for DASH and VR is delivered via Multicast Broadcast Service (MBS). QoE measurement collection for application sessions delivered via MBS is supported in the RRC_CONNECTED, RRC_INACTIVE, and RRC_IDLE states. QoE measurement collection for application sessions delivered via MBS multicast is supported only in the RRC_CONNECTED state. QMC functionality is also supported in NR-Dual Connectivity (DC). In some embodiments, QoE measurement naming is used for the interfaces between NG, Xn, and OAM and gNB. In the Uu interface, application layer measurement naming is used and is equal to the QoE measurement.

[0070] Table 2 shows several IEs in the QMC configuration information, namely, the configuration information for QMC functions. The range maxnoofUEAppLayerMeas can refer to the maximum number of UE application layer measurements. The value of maxnoofUEAppLayerMeas can be 16 or any other suitable integer.

[0071] Table 2

[0072] In some embodiments, UE application layer measurement configuration information may include QMC function configuration information. QMC function configuration information may include one or more IEs, such as a QoE reference, a container for application layer measurement configuration, etc. The QoE reference IE may be defined in Clause 5.2 of Technical Specification (TS) 28.405

[45] and may consist of a Mobility Control Code (MCC) + Mobile Network Code (MNC) + QMC ID, wherein the MCC and MNC are derived from a QMC activation request from the management system to identify a Public Land Mobile Network (PLMN) containing the management system, and the QMC ID is a 3-byte octet string. The presence of the QoE reference IE may be M. The type of the QoE reference IE may be OCTET STRING (SIZE (6)). The container for the application layer measurement configuration IE may be defined in Appendix L of 26.247

[46] , Clause 16.5 of TS 26.114

[51] and Clause 9 of TS 26.118

[52] . The container IE for application layer measurement configuration may exist in the initial QoE configuration and should be included in the source-to-target transparent container IE for signaling-based QMC during NG-based handover. The presence of the container IE for application layer measurement configuration can be 0, and the IE type and reference of the container IE for application layer measurement configuration can be OCTETSTRING (SIZE (1..8000)).

[0073] In some embodiments, the QoE measurement continuity for mobility may follow Table 3 or Table 4 below, which may be included in TS 38.300.

[0074] Table 3

[0075] Table 4

[0076] The second network device 130 determines a second configuration for (230) QoE measurement based on the first configuration. The second configuration may be similar to the first configuration. For example, a portion of the first configuration may remain in the second configuration. The remainder of the second configuration may be modified based on information associated with the second network device 130.

[0077] The second network device 130 sends (240) a response to the request to the first network device 120. This response includes a second configuration associated with the first configuration. The first network device 120 receives (250) the response. In embodiments where the request is a handover request, the response may be a handover request confirmation or a "handover request confirmation message".

[0078] In some embodiments, communication between the first network device 120 and the second network device 130 may be via the Xn interface. Alternatively or additionally, in some embodiments, communication between the first network device 120 and the second network device 130 may be via the NG interface. For example, the request may be sent to the second network device 130 via the AMF or any other suitable function or device in the 5GC (210). Similarly, a response is received from the second network device 130 via the AMF (250).

[0079] First network device 120 sends (260) handover configuration information to terminal device 110. The configuration information includes a second configuration. Terminal device 110 receives (270) the configuration information. Terminal device 110 performs (280) QoE measurement based on the second configuration. As used herein, the configuration information may be a MobilityFromNRCommand or any other suitable message or IE.

[0080] In some embodiments, the first network device 120 may perform the release of a first configuration. The first network device 120 may also send a first indication of release to the terminal device 110. As an example, the first indication may be sent before at least one of the following: a handover, a request to the second network device 130, or configuration information to the terminal device 110. In this way, the source network device may decide which QoE configuration(s) to send to the target network device, and release (or release) other QoE configuration(s) after the handover decision.

[0081] In some embodiments, the response to the request may include a first RRC configuration and a second indication, the second indication indicating the release of a second RRC configuration configured by the first network device 120. The first configuration may be included in the first RRC configuration. In such a case, the configuration information may include the first RRC configuration and the second indication. In this way, the target network device can prepare a complete RRC configuration for the terminal device during NR to LTE handover.

[0082] In some embodiments, in response to receiving configuration information, terminal device 110 may release a third configuration of QoE measurement configured by first network device 120. Alternatively or additionally, in some embodiments, terminal device 110 may release a third configuration of QoE configured by first network device 120 after a handover. In some embodiments, by sending the QoE release configuration to second network device 130, second network device 130 may include these release configurations in configuration information, such as to terminal device 110's MobilityFromNRCommand, to release unselected QoE configurations.

[0083] In some embodiments, the configuration information may include a third indication of releasing a third configuration of QoE measurement configured by the first network device 120. As used herein, the indication of releasing the QoE configuration configured by the first network device 120 may also be referred to as a release indication or a release configuration. In response to receiving the configuration information, the terminal device 110 may perform the release of the third configuration of QoE measurement. In this way, the source network device may prepare a release configuration, which is included in configuration information such as MobilityFromNRCommand.

[0084] In some embodiments, the list of QoE references can be used to deactivate the corresponding QoE measurement collection jobs(s). Upon receiving a QoE release message in an application-layer measurement configuration, the terminal device 110 can discard any unsent application-layer measurement reports corresponding to the released application-layer configuration.

[0085] In this way, terminal device 110 can perform (280) QoE measurement based on a second configuration, which is based on a selected first configuration. In some embodiments, terminal device 110 can report the QoE measurement results. Figure 3 Signaling flow 300 for QoE measurement reporting is shown. Signaling flow 300 involves... Figure 1 The terminal device 110, network device 320, and MCE 330 are included. Network device 320 can be... Figure 1 The first network device 120, the second network device 130, or the third network device 140.

[0086] In signaling flow 300, it is assumed that the handover between the first network device 120 and the second network device 130 has been completed. Terminal device 110 is currently being served in cell 132 of the second network device 130. That is, it is assumed that network device 320 is the second network device 130.

[0087] Prior to signaling flow 300, terminal device 110 receives configuration information from first network device 120. The configuration information may include a second configuration of the QoE configuration. The second configuration may be a QoE container. Terminal device 110 may forward the QoE container (i.e., the second configuration) to the application layer (340). The application layer may perform (350) QoE measurements and encapsulate the QoE measurement results in a transparent container before sending them to the lower layer. For example, an application layer measurement report received from the application layer of terminal device 110 may be encapsulated in a transparent container.

[0088] In some embodiments, terminal device 110 may send a (360) QoE measurement result container to network device 320. For example, an application layer measurement report may be sent to network device 320 in a MeasurementReportAppLayer message. Terminal device 110 may send multiple application layer measurement reports to network device 320 in a single MeasurementReportAppLayer message. In response to receiving a QoE measurement result container, network device 320 may send a (370) QoE measurement result container to MCE 330. Examples of MeasurementReportAppLayer messages are shown in Table 5 below.

[0089] Table 5

[0090]

[0091] Already about Figure 2 and Figure 3 Several embodiments regarding QoE measurement configuration and QoE measurement reporting are described. (Refer to...) Figures 4 to 11 Other embodiments regarding QoE measurement are described. Figures 4 to 11 Signaling flows 400, 500, 600, 700, 800, 900, 1000, and 1100 for QoE measurement configuration according to some embodiments of this disclosure are shown respectively. For discussion purposes, reference will be made, for example, by using terminal device 110, first network device 120, and second network device 130. Figure 1 Discuss signaling flows 400 to 1100.

[0092] In the following description, it is assumed that the first network device 120 can operate as an NR network node and the second network device 130 can operate as an evolved NR network node. It should be understood that in some embodiments, the first network device 120 and the second network device 130 may be different network devices or network nodes.

[0093] In signaling flows 400 to 1100, it is assumed that terminal device 110 is currently being served in cell 122 of first network device 120. First network device 120 may be referred to as the source network device. It is also assumed that cell 132 of second network device 130 is the cell used for handover. Second network device 130 may be referred to as the target network device.

[0094] refer to Figure 4During operation, QoE measurement control and reporting are performed (410). For example, the first network device 120 can configure multiple QoE measurement procedures for the terminal device 110, and the terminal device 110 can report QoE measurement results based on the multiple QoE measurement configurations.

[0095] The first network device 120 can determine (415) the handover of the terminal device 110 to the second network device 130. For example, the first network device 120 can make the handover decision based on the Measurement Report and RRM information or any other suitable information.

[0096] The first network device 120 can select (420) the QoE measurement configuration to be transmitted to the second network device 130. For example, it can be based on priority information and such as... Figure 2 Any other suitable information described herein may be used to select the QoE measurement configuration. That is, the first network device 120 may decide which QoE configuration to send to the second network device 130 and release (multiple) other QoE configurations after the handover decision. As used herein, the selected QoE measurement configuration may also be referred to as the “selected QoE configuration” or the “first configuration of QoE measurement” or simply the “first configuration”.

[0097] In some embodiments, the first network device 120 may send a handover request (also referred to as a "handover request message") to the second network device 130. The handover request message includes the selected QoE configuration. For example, for signaling-based QoE measurements, the selected QoE configuration may be included in a measConfigAppLayerContainer (measurement configuration application layer container), which is included in the RRC context of the handover request. For management-based QoE measurements, the selected QoE configuration may be included in UE application layer measurement configuration information, which is included in the QMC configuration information of the handover request.

[0098] In some embodiments, the handover request may be sent in a transparent RRC container with the necessary information to prepare for handover on the target side. This information may include at least the target cell identifier (ID), KgNB*, the cell radio network temporary identifier (C-RNTI) of the terminal device 110 in the first network device 120, the RRM configuration including the inactivity time of the terminal device 110, and other information. Antenna information and DL carrier frequencyThe configuration includes the basic Angle Extension (AS) configuration, the current Quality of Service (QoS) flow-to-Data Radio Bearer (DRB) mapping rules applied to terminal device 110, System Information Block 1 (SIB1) from the first network device 120, the capabilities of terminal device 110 for different RATs, Protocol Data Unit (PDU) session-related information, and may include reported measurement information from terminal device 110, including beam-related information (if available). PDU session-related information may include slice information and QoS flow level (QoS) profiles (multiple). The first network device 120 may also request a Dual Active Protocol Stack (DAPS) handover for one or more DRBs.

[0099] The second network device 130 can perform (435) admission control. For example, if slice information is sent to the second network device 130, slice-aware admission control can be performed (435). If a PDU session is associated with an unsupported slice, the second network device 130 can reject such a PDU session.

[0100] The second network device 130 may prepare for a Layer 1 (L1) / Layer 2 (L2) handover and send a handover request confirmation (440) to the first network device 120. The handover request confirmation may include a transparent container to be sent as an RRC message to the terminal device 110 to perform the handover. The second network device 130 may also indicate whether the DAPS handover is accepted.

[0101] In some embodiments, the second network device 130 may determine a new QoE configuration based on the received selected QoE configuration. The second network device 130 may include the new QoE configuration in the handover request confirmation. For example, the new QoE configuration may be in measConfigAppLayerContainer-r15 within measConfigAppLayer-r15, and measConfigAppLayer-r15 is included in the RRC container in the handover request confirmation. As used herein, the new QoE configuration may also be referred to as a “new configuration for QoE measurement” or a “second configuration for QoE measurement” or simply “second configuration.”

[0102] The first network device 120 can send (425) QoE measurement release configuration to the terminal device 110. For example, once the first network device 120 selects the QoE configuration, the first network device 120 can directly send (425) QoE measurement release configuration to the terminal device 110. Alternatively, the release process can occur before the handover request or before receiving the handover request confirmation. The release process can be performed before MobilityFromNRCommand. The release configuration can be included in measConfigAppLayerToReleaseList, which is included in AppLayerMeasConfig in RRCReconfiguration.

[0103] The first network device 120 can send a (445) MobilityFromNRCommand to the terminal device 110. The new QoE configuration is included in the MobilityFromNRCommand. For example, the first network device 120 can trigger a Uu handover by sending an RRCReconfiguration message containing information required for accessing the target cell to the terminal device 110. This information may include at least the target cell ID, the new C-RNTI, and the security algorithm for the second network device 130 identifier used for the selected security algorithm. This information may also include a set of dedicated radio access channel (RACH) resources, the association between RACH resources and (multiple) SSBs, the association between RACH resources and (multiple) UE-specific channel state information reference signal (CSI-RS) configurations, public RACH resources, and system information of the target cell, etc. Terminal device 110 can receive MobilityFromNRCommand. Terminal device 110 can detach from the original cell (450) and synchronize with the new target cell. For example, terminal device 110 can synchronize with the target cell and by sending to the second network device 130 RRCReconfigurationComplete (RRC reconfiguration complete) message completes the (455) RRC handover process. In the case of DAPS handover, terminal device 110 receives RRCReconfiguration The message is not separated from the source cell. Terminal device 110 can release the source resources and configuration, and stop receiving / transmitting DL / UL with the source when an explicit release is received from the target node.

[0104] As shown in signaling flow 400, the signaling flow between the first network device 120 and the second network device 130 can be via the Xn interface. In this way, the first network device 120, such as the source gNB, can release (multiple) other QoE configurations after a handover decision on the Xn interface.

[0105] Alternatively or additionally, signaling flows between the first network device 120 and the second network device 130 may be via the NG interface, as shown in signaling flow 500. Signaling flow 500 also relates to AMF 510.

[0106] Similar to signaling flow 400, in signaling flow 500, QoE measurement control and reporting are performed (410). For example, the first network device 120 can configure multiple QoE measurement procedures for the terminal device 110, and the terminal device 110 can report QoE measurement results based on the multiple QoE measurement configurations.

[0107] The first network device 120 can determine (415) the handover decision to switch the terminal device 110 to the second network device 130. For example, the first network device 120 can make the handover decision based on MeasurementReport and RRM information or any other suitable information.

[0108] The first network device 120 can select (420) the QoE measurement configuration to be transmitted to the second network device 130. For example, it can be based on priority information and such as... Figure 2 Any other suitable information described to select the QoE measurement configuration. That is, the first network device 120 can decide which QoE configuration to send to the second network device 130, and release (multiple) other QoE configurations after the handover decision.

[0109] For example, the first network device 120 may send (515) a handover request, such as a handover request message, to the AMF 510. The handover request message includes the selected QoE configuration. For example, for signaling-based QoE measurements, the selected QoE configuration may be included in a measConfigAppLayerContainer, which is included in the RRC context within the source-to-target transparent container in the handover request. For management-based QoE measurements, the selected QoE configuration may be included in UE application layer measurement configuration information, which is included in the QMC configuration information within the source-to-target transparent container in the handover request.

[0110] In response to receiving a handover request message, AMF 510 may send a handover request (520) to the second network device 130. The second network device 130 may receive the handover request. The handover request includes a new QoE configuration. For example, for signaling-based QoE measurements, the selected QoE configuration may be included in a measConfigAppLayerContainer, which is included in the RRC context of the handover request. For management-based QoE measurements, the selected QoE configuration may be included in UE application layer measurement configuration information, which is included in the QMC configuration information of the handover request.

[0111] In response to receiving a handover request, the second network device 130 may perform (525) admission control. For example, if slice information is sent to the second network device 130, slice-aware admission control may be performed (525). If a PDU session is associated with an unsupported slice, the second network device 130 may reject such a PDU session.

[0112] The second network device 130 can prepare for a Layer 1 (L1) / Layer 2 (L2) handover and send a handover request confirmation (530) to the AMF 510. The handover request confirmation may include a transparent container to be sent as an RRC message to the terminal device 110 to perform the handover. The second network device 130 may also indicate whether the DAPS handover is accepted.

[0113] In some embodiments, the second network device 130 may determine a new QoE configuration based on the received selected QoE configuration. The second network device 130 may include the new QoE configuration in the handover request confirmation. For example, the new QoE configuration may be in measConfigAppLayerContainer-r15 within measConfigAppLayer-r15, and measConfigAppLayer-r15 may be included in an RRC container within the target-to-source transparent container in the handover request confirmation.

[0114] AMF 510 can send a (535) handover command to the first network device 120. The new QoE configuration can be included in the handover command. For example, the new QoE configuration can be in measConfigAppLayerContainer-r15 within measConfigAppLayer-r15, and measConfigAppLayer-r15 is included in the RRC container within the target-to-source transparent container in the handover command.

[0115] The first network device 120 can send (425) QoE measurement release configuration to the terminal device 110. For example, once the first network device 120 selects the QoE configuration, the first network device 120 can directly send (425) QoE measurement release configuration to the terminal device 110. Alternatively, the release process can occur before the handover request or before receiving the handover request confirmation. The release process can be performed before MobilityFromNRCommand. The release configuration can be included in measConfigAppLayerToReleaseList, which is included in AppLayerMeasConfig in RRCReconfiguration.

[0116] The first network device 120 can send (540) MobilityFromNRCommand to the terminal device 110. The new QoE configuration is included in the MobilityFromNRCommand.

[0117] Terminal device 110 can receive MobilityFromNRCommand. Terminal device 110 can detach from the original cell (450) and synchronize with the new target cell. For example, terminal device 110 can synchronize with the target cell and by sending to the second network device 130 RRCReconfigurationComplete The message completes the (455) RRC handover process. In the case of DAPS handover, terminal device 110 receives... RRCReconfiguration The message is not separated from the source cell. Terminal device 110 can release the source resources and configuration, and stop receiving / transmitting DL / UL with the source when an explicit release is received from the target node.

[0118] In this way, a first network device 120, such as the source gNB, can release (multiple) other QoE configurations via the NG interface after a handover decision. QoE measurements can then be performed based on the new QoE configuration of the second network device 130 after the handover.

[0119] In some embodiments, QoE measurement continuity for mobility can be performed as shown in Table 6, which may be included in TS 38.300.

[0120] Table 6

[0121] Several embodiments have been described whereby the first network device 120 releases multiple other QoE configurations. In some embodiments, the multiple QoE configurations can be released by the terminal device 110, which will relate to... Figures 6 to 11 Describe it.

[0122] refer to Figure 6 During operation, QoE measurement control and reporting are performed (410). For example, the first network device 120 can configure multiple QoE measurement procedures for the terminal device 110, and the terminal device 110 can report QoE measurement results based on the multiple QoE measurement configurations.

[0123] The first network device 120 can determine (415) the handover decision to switch the terminal device 110 to the second network device 130. For example, the first network device 120 can make the handover decision based on MeasurementReport and RRM information or any other suitable information.

[0124] The first network device 120 can select (420) the QoE measurement configuration to be transmitted to the second network device 130. For example, it can be based on priority information and such as... Figure 2 Any other suitable information described to select the QoE measurement configuration. That is, the first network device 120 can decide which QoE configuration to send to the second network device 130.

[0125] In some embodiments, the first network device 120 may send a handover request (610) to the second network device 130. The handover request includes a selected QoE configuration. For example, for signaling-based QoE measurements, the selected QoE configuration may be included in a measConfigAppLayerContainer, which is included in the RRC context of the handover request. For management-based QoE measurements, the selected QoE configuration may be included in UE application layer measurement configuration information, which is included in the QMC configuration information of the handover request.

[0126] The second network device 130 can perform (615) admission control. For example, if slice information is sent to the second network device 130, slice-aware admission control can be performed (615). If a PDU session is associated with an unsupported slice, the second network device 130 can reject such a PDU session.

[0127] The second network device 130 can prepare for a Layer 1 (L1) / Layer 2 (L2) handover and send a handover request confirmation (620) to the first network device 120. The handover request confirmation may include a transparent container to be sent as an RRC message to the terminal device 110 to perform the handover. The second network device 130 may also indicate whether the DAPS handover is accepted.

[0128] In some embodiments, the second network device 130 may determine a new QoE configuration based on the received selected QoE configuration. The second network device 130 may include the new QoE configuration in the handover request confirmation. For example, the new QoE configuration may be in measConfigAppLayerContainer-r15 within measConfigAppLayer-r15, and measConfigAppLayer-r15 may be included in the RRC container within the handover request confirmation.

[0129] The first network device 120 can receive a handover request confirmation. The first network device 120 can send (625) MobilityFromNRCommand to the terminal device 110. The new QoE configuration is included in the MobilityFromNRCommand.

[0130] Terminal device 110 can receive MobilityFromNRCommand. The terminal device can release (630) the original QoE configuration and apply the new QoE configuration. In this way, terminal device 110 can release an unselected QoE configuration.

[0131] In one option, if terminal device 110 detects measConfigAppLayer-r15 in the MobilityFromNRCommand IE and there are ongoing QoE measurements, terminal device 110 can release these QoE measurements. Terminal device 110 then applies the new QoE configuration in measConfigAppLayerContainer-r15, which is included in measConfigAppLayer-r15.

[0132] In another option, if terminal device 110 detects a MobilityFromNRCommand IE and there are ongoing QoE measurements, terminal device 110 can release these QoE measurements. Terminal device 110 then applies the new QoE configuration in measConfigAppLayerContainer-r15, which is included in measConfigAppLayer-r15.

[0133] In another option, QoE release and configuration can be applied after the RAN handover is complete or once it detects the MobilityFromNRCommand IE. It should be noted that the end device 110 can apply the new QoE configuration during MobilityFromNRCommand rather than after the handover is complete.

[0134] Terminal device 110 can detach from the original cell (450) and synchronize with the new target cell. For example, terminal device 110 can synchronize with the target cell and send data to the second network device 130. RRCReconfigurationComplete The message completes the (455) RRC handover process. In the case of DAPS handover, terminal device 110 receives... RRCReconfiguration The message is not separated from the source cell. Terminal device 110 can release the source resources and configuration, and stop receiving / transmitting DL / UL with the source when an explicit release is received from the target node.

[0135] As shown in signaling flow 600, the signaling flow between the first network device 120 and the second network device 130 can be via the Xn interface. Alternatively or additionally, the signaling flow between the first network device 120 and the second network device 130 can be via the NG interface, as shown in signaling flow 700. Signaling flow 700 also relates to AMF 710.

[0136] Similar to signaling flow 600, in signaling flow 700, QoE measurement control and reporting are performed (410). For example, the first network device 120 can configure multiple QoE measurement procedures for the terminal device 110, and the terminal device 110 can report QoE measurement results based on the multiple QoE measurement configurations.

[0137] The first network device 120 can determine (415) the handover decision to switch the terminal device 110 to the second network device 130. For example, the first network device 120 can make the handover decision based on MeasurementReport and RRM information or any other suitable information.

[0138] The first network device 120 can select (420) the QoE measurement configuration to be transmitted to the second network device 130. For example, it can be based on priority information and such as... Figure 2 Any other suitable information described to select the QoE measurement configuration. That is, the first network device 120 can decide which QoE configuration to send to the second network device 130.

[0139] In some embodiments, the first network device 120 may send (715) a handover request, such as a handover request message, to the AMF 710. The handover request message includes the selected QoE configuration. For example, for signaling-based QoE measurements, the selected QoE configuration may be included in a measConfigAppLayerContainer, which is included in the RRC context within the source-to-target transparent container of the handover request. For management-based QoE measurements, the selected QoE configuration may be included in UE application layer measurement configuration information, which is included in the QMC configuration information within the source-to-target transparent container of the handover request.

[0140] In response to receiving a handover request message, AMF 710 may send a handover request (720) to the second network device 130. The second network device 130 may receive the handover request. The handover request includes a new QoE configuration. For example, for signaling-based QoE measurements, the selected QoE configuration may be included in a measConfigAppLayerContainer, which is included in the RRC context of the handover request. For management-based QoE measurements, the selected QoE configuration may be included in UE application layer measurement configuration information, which is included in the QMC configuration information of the handover request.

[0141] The second network device 130 can receive a handover request. The second network device 130 can perform (725) admission control. For example, if slice information is sent to the second network device 130, slice-aware admission control can be performed (725). If a PDU session is associated with an unsupported slice, the second network device 130 can reject such a PDU session.

[0142] The second network device 130 can prepare for a Layer 1 (L1) / Layer 2 (L2) handover and send a handover request confirmation (730) to the AMF 710. The handover request confirmation may include a transparent container to be sent as an RRC message to the terminal device 110 to perform the handover. The second network device 130 may also indicate whether the DAPS handover is accepted.

[0143] In some embodiments, the second network device 130 may determine a new QoE configuration based on the received selected QoE configuration. The second network device 130 may include the new QoE configuration in the handover request confirmation. For example, the new QoE configuration may be in measConfigAppLayerContainer-r15 within measConfigAppLayer-r15, and measConfigAppLayer-r15 may be included in the RRC container within the handover request confirmation.

[0144] AMF 710 can send a (735) handover command to the first network device 120. The new QoE configuration can be included in the handover command. For example, the new QoE configuration can be in measConfigAppLayerContainer-r15 within measConfigAppLayer-r15, and measConfigAppLayer-r15 is included in the RRC container in the handover command.

[0145] The first network device 120 can receive a handover command. The first network device 120 can send (740) MobilityFromNRCommand to the terminal device 110. The new QoE configuration is included in the MobilityFromNRCommand.

[0146] Terminal device 110 can receive MobilityFromNRCommand. The terminal device can release (745) the original QoE configuration and apply the new QoE configuration. In this way, terminal device 110 can release an unselected QoE configuration.

[0147] In one option, if terminal device 110 detects measConfigAppLayer-r15 in the MobilityFromNRCommand IE and there are ongoing QoE measurements, terminal device 110 can release these QoE measurements. Then, terminal device 110 applies the new QoE configuration in measConfigAppLayerContainer-r15, which is included in measConfigAppLayer-r15.

[0148] In another option, if terminal device 110 detects a MobilityFromNRCommand IE and there are ongoing QoE measurements, terminal device 110 can release these QoE measurements. Terminal device 110 then applies the new QoE configuration in measConfigAppLayerContainer-r15, which is included in measConfigAppLayer-r15.

[0149] In another option, QoE release and configuration can be applied after the RAN handover is complete or once it detects the MobilityFromNRCommand IE. It should be noted that the end device 110 can apply the new QoE configuration during MobilityFromNRCommand rather than after the handover is complete.

[0150] Terminal device 110 can detach from the original cell (450) and synchronize with the new target cell. For example, terminal device 110 can synchronize with the target cell and send data to the second network device 130. RRCReconfigurationComplete The message completes the (455) RRC handover process. In the case of DAPS handover, terminal device 110 receives... RRCReconfiguration The message is not separated from the source cell. Terminal device 110 can release the source resources and configuration, and stop receiving / transmitting DL / UL with the source when an explicit release is received from the target node.

[0151] In this way, terminal device 110 can release the QoE configuration of the first network device 120 when it receives MobilityFromNRCOmmand from the second network device 130 or after a handover is completed via the Xn interface or NG interface.

[0152] In some embodiments, the reception of MobilityFromNRCommand by the terminal device 110 (such as a UE) will follow option 1 in Table 7 or option 2 in Table 8. Tables 7 and 8 may be included in TS 38.331. Once MobilityFromNRCommand is received, the options in Table 7 can be applied to QoE release. Once the handover is complete, the options in Table 8 can be applied to QoE release.

[0153] Table 7

[0154] Table 8

[0155] QoE measurement collection deactivation can follow Table 9 below, which can be included in TS 38.300.

[0156] Table 9

[0157] In some embodiments, the second network device 130 may prepare a complete RRC configuration for the terminal device 110 during handover (such as a handover from NR to LTE), as relative to Figure 8 and Figure 9As stated above.

[0158] refer to Figure 8 During operation, QoE measurement control and reporting are performed (410). For example, the first network device 120 can configure multiple QoE measurement procedures for the terminal device 110, and the terminal device 110 can report QoE measurement results based on the multiple QoE measurement configurations.

[0159] The first network device 120 can determine (415) the handover decision to switch the terminal device 110 to the second network device 130. For example, the first network device 120 can make the handover decision based on MeasurementReport and RRM information or any other suitable information.

[0160] The first network device 120 can select (420) the QoE measurement configuration to be transmitted to the second network device 130. For example, it can be based on priority information and such as... Figure 2 Any other suitable information described to select the QoE measurement configuration. That is, the first network device 120 can decide which QoE configuration to send to the second network device 130.

[0161] In some embodiments, the first network device 120 may send a handover request (810) to the second network device 130. The handover request includes a selected QoE configuration. For example, for signaling-based QoE measurements, the selected QoE configuration may be included in a measConfigAppLayerContainer, which is included in the RRC context of the handover request. For management-based QoE measurements, the selected QoE configuration may be included in UE application layer measurement configuration information, which is included in the QMC configuration information of the handover request.

[0162] The second network device 130 can receive a handover request. The second network device 130 can perform (815) admission control. For example, if slice information is sent to the second network device 130, slice-aware admission control can be performed (815). If a PDU session is associated with an unsupported slice, the second network device 130 can reject such a PDU session.

[0163] The second network device 130 can prepare for a switch with Layer 1 (L1) / Layer 2 (L2) and send a (820) switch request confirmation to the first network device 120.

[0164] In some embodiments, the second network device 130 may generate an RRC configuration that includes the new QoE configuration. For example, the second network device 130 may determine the new QoE configuration based on the received selected QoE configuration. For example, the new QoE configuration may be in measConfigAppLayerContainer-r15 within measConfigAppLayer-r15, and measConfigAppLayer-r15 is included in the RRC container in the handover request confirmation. The second network device 130 may also set the full configuration IE in the RRC configuration to true.

[0165] The first network device 120 can receive a handover request confirmation. The first network device 120 can send (825) MobilityFromNRCommand to the terminal device 110. The new QoE configuration is included in MobilityFromNRCommand, where the full configuration IE is true.

[0166] Terminal device 110 can receive MobilityFromNRCommand. If terminal device 110 receives MobilityFromNRCommand with all configurations set to true, terminal device 110 can release all original RRC configurations configured by the first network device 120 and apply the new RRC configuration configured by the second network device 130, which includes the new QoE configuration. For example, the new QoE configuration can be in measConfigAppLayerContainer-r15. measConfigAppLayerContainer-r15 can be included in measConfigAppLayer-r15->measConfigAppLayerContainer-r15, which is included in the targetRAT-MessageContainer in MobilityFromNRCommand.

[0167] Terminal device 110 can detach from the original cell (450) and synchronize with the new target cell. For example, terminal device 110 can synchronize with the target cell and send data to the second network device 130. RRCReconfigurationComplete The message completes the (455) RRC handover process. In the case of DAPS handover, terminal device 110 receives... RRCReconfiguration The message is not separated from the source cell. Terminal device 110 can release the source resources and configuration, and stop receiving / transmitting DL / UL with the source when an explicit release is received from the target node.

[0168] In this way, the second network device 130 (such as the target ng-eNB) can prepare a complete RRC configuration for the terminal device 110 during the NR to LTE handover on the Xn interface.

[0169] As shown in signaling flow 800, the signaling flow between the first network device 120 and the second network device 130 can be via the Xn interface. Alternatively or additionally, the signaling flow between the first network device 120 and the second network device 130 can be via the NG interface, as shown in signaling flow 900. Signaling flow 900 also relates to AMF 910.

[0170] Similar to signaling flow 800, in signaling flow 900, QoE measurement control and reporting are performed (410). For example, the first network device 120 can configure multiple QoE measurement procedures for the terminal device 110, and the terminal device 110 can report QoE measurement results based on the multiple QoE measurement configurations.

[0171] The first network device 120 can determine (415) the handover decision to switch the terminal device 110 to the second network device 130. For example, the first network device 120 can make the handover decision based on MeasurementReport and RRM information or any other suitable information.

[0172] The first network device 120 can select (420) the QoE measurement configuration to be transmitted to the second network device 130. For example, it can be based on priority information and such as... Figure 2 Any other suitable information described to select the QoE measurement configuration. That is, the first network device 120 can decide which QoE configuration to send to the second network device 130.

[0173] In some embodiments, the first network device 120 may send (915) a handover request, such as a handover request message, to the AMF 910. The handover request message includes the selected QoE configuration. For example, for signaling-based QoE measurements, the selected QoE configuration may be included in a measConfigAppLayerContainer, which is included in the RRC context within the source-to-target transparent container of the handover request. For management-based QoE measurements, the selected QoE configuration may be included in UE application layer measurement configuration information, which is included in the QMC configuration information within the source-to-target transparent container of the handover request.

[0174] In response to receiving a handover request message, AMF 910 may send a (920) handover request to the second network device 130. The handover request includes a new QoE configuration. For example, for signaling-based QoE measurements, the selected QoE configuration may be included in a measConfigAppLayerContainer, which is included in the RRC context of the handover request. For management-based QoE measurements, the selected QoE configuration may be included in the UE application layer measurement configuration information, which is included in the QMC configuration information of the handover request.

[0175] The second network device 130 can receive a handover request. The second network device 130 can perform (925) admission control. For example, if slice information is sent to the second network device 130, slice-aware admission control can be performed (925). If a PDU session is associated with an unsupported slice, the second network device 130 can reject such a PDU session.

[0176] The second network device 130 can prepare for a switch with Layer 1 (L1) / Layer 2 (L2) and send a (930) switch request confirmation to AMF 910.

[0177] In some embodiments, the second network device 130 may generate an RRC configuration that includes the new QoE configuration. The generated RRC configuration may be included in the handover request confirmation. For example, the second network device 130 may determine the new QoE configuration based on the received selected QoE configuration. For example, the new QoE configuration may be included in measConfigAppLayerContainer-r15 within measConfigAppLayer-r15. measConfigAppLayer-r15 is included in the RRC container within the target-to-source transparent container in the handover request confirmation. The second network device 130 may also set the full configuration IE in the RRC configuration to true.

[0178] The AMF 910 can receive handover request confirmations. The AMF 910 can send a handover command (935) to the first network device 120, including the new QoE configuration and with all configurations set to true. For example, the new QoE configuration can be included in measConfigAppLayerContainer-r15 within measConfigAppLayer-r15. measConfigAppLayer-r15 is included in the RRC container within the target-to-source transparent container in the handover command.

[0179] The first network device 120 can receive a handover command. The first network device 120 can send (940) MobilityFromNRCommand to the terminal device 110. The new QoE configuration is included in the MobilityFromNRCommand, where the full configuration IE is true.

[0180] Terminal device 110 can receive MobilityFromNRCommand. If terminal device 110 receives MobilityFromNRCommand with all configurations set to true, terminal device 110 can release all original RRC configurations configured by the first network device 120 and apply the new RRC configuration configured by the second network device 130, which includes the new QoE configuration. For example, the new QoE configuration can be in measConfigAppLayerContainer-r15. measConfigAppLayerContainer-r15 can be included in measConfigAppLayer-r15->measConfigAppLayerContainer-r15, which is included in the targetRAT-MessageContainer in MobilityFromNRCommand.

[0181] In some embodiments, the second network device 130 may determine a new QoE configuration based on the received selected QoE configuration. The second network device 130 may include the new QoE configuration in the handover request confirmation. For example, the new QoE configuration may be in measConfigAppLayerContainer-r15 within measConfigAppLayer-r15, and measConfigAppLayer-r15 may be included in the RRC container within the handover request confirmation.

[0182] Terminal device 110 can detach from the original cell (450) and synchronize with the new target cell. For example, terminal device 110 can synchronize with the target cell and send data to the second network device 130. RRCReconfigurationComplete The message completes the (455) RRC handover process. In the case of DAPS handover, terminal device 110 receives... RRCReconfiguration The message is not separated from the source cell. Terminal device 110 can release the source resources and configuration, and stop receiving / transmitting DL / UL with the source when an explicit release is received from the target node.

[0183] In this way, the second network device 130 can prepare a complete RRC configuration for the terminal device 110 during the NR to LTE handover on the NG interface.

[0184] Table 10 shows an example of the MobilityFromNRCommand message, which can be included in TS 38.331.

[0185] Table 10

[0186] In Table 10, the field “measConfigAppLayerToAddModList” can be used to release the QoE configuration during the handover from gNB to ng-ENB. Upon receiving MobilityFromNRCommand, terminal device 110, such as a UE, can execute the following Table 11, which may be included in TS 38.311.

[0187] Table 11

[0188] The QoE measurement continuity of mobility can be configured as shown in Table 12, which can be included in TS 38.300.

[0189] Table 12

[0190] In some embodiments, the first network device 120 may prepare a release configuration, which may be included in the MobilityFromNRCommand of the terminal device 110. (See reference...) Figure 10 and Figure 11 Such an embodiment is described.

[0191] In signaling flow 1000, QoE measurement control and reporting are performed (410). For example, the first network device 120 can configure multiple QoE measurement procedures for the terminal device 110, and the terminal device 110 can report QoE measurement results based on the multiple QoE measurement configurations.

[0192] The first network device 120 can determine (415) the handover decision to switch the terminal device 110 to the second network device 130. For example, the first network device 120 can make the handover decision based on MeasurementReport and RRM information or any other suitable information.

[0193] The first network device 120 can select (420) the QoE measurement configuration to be transmitted to the second network device 130. For example, it can be based on priority information and such as... Figure 2 Any other suitable information described to select the QoE measurement configuration. That is, the first network device 120 can decide which QoE configuration to send to the second network device 130.

[0194] In some embodiments, the first network device 120 may send a handover request (1010) to the second network device 130. The handover request includes a selected QoE configuration. For example, for signaling-based QoE measurements, the selected QoE configuration may be included in a measConfigAppLayerContainer, which is included in the RRC context of the handover request. For management-based QoE measurements, the selected QoE configuration may be included in UE application layer measurement configuration information, which is included in the QMC configuration information of the handover request.

[0195] The second network device 130 can perform (1015) admission control. For example, if slice information is sent to the second network device 130, slice-aware admission control can be performed (1015). If a PDU session is associated with an unsupported slice, the second network device 130 can reject such a PDU session.

[0196] The second network device 130 can prepare for a Layer 1 (L1) / Layer 2 (L2) handover and send a handover request confirmation (1020) to the first network device 120. The handover request confirmation may include a transparent container to be sent as an RRC message to the terminal device 110 to perform the handover. The second network device 130 may also indicate whether the DAPS handover is accepted.

[0197] In some embodiments, the second network device 130 may determine a new QoE configuration based on the received selected QoE configuration. The second network device 130 may include the new QoE configuration in the handover request confirmation. For example, the new QoE configuration may be in measConfigAppLayerContainer-r15 within measConfigAppLayer-r15, and measConfigAppLayer-r15 may be included in the RRC container within the handover request confirmation.

[0198] The first network device 120 can receive a handover request confirmation. The first network device 120 can send a (1025) MobilityFromNRCommand to the terminal device 110. A new QoE configuration is included in the MobilityFromNRCommand. The MobilityFromNRCommand can also include a configuration for releasing unselected QoE configurations (also known as a release configuration). For example, the first network device 120 can generate a release configuration for unselected QoE configurations or a release configuration for all QoE configurations configured by the first network device 120. The release configuration can be included in the MobilityFromNRCommand, but can be outside the RRC container generated by the second network device 130. The new QoE configuration can be in measConfigAppLayerContainer-r15 within measConfigAppLayer-r15, which can be included in the targetRAT-MessageContainer within the MobilityFromNRCommand.

[0199] Terminal device 110 can receive a MobilityFromNRCommand with a release configuration. The terminal device can release (1030) (multiple) unselected QoE configurations and apply a new QoE configuration. For example, terminal device 110 can apply a new RRC configuration that includes the new QoE configuration. In this way, terminal device 110 can release unselected QoE configurations.

[0200] Terminal device 110 can detach from the original cell (450) and synchronize with the new target cell. For example, terminal device 110 can synchronize with the target cell and send data to the second network device 130. RRCReconfigurationComplete The message completes the (455) RRC handover process. In the case of DAPS handover, terminal device 110 receives... RRCReconfiguration The message is not separated from the source cell. Terminal device 110 can release the source resources and configuration, and stop receiving / transmitting DL / UL with the source when an explicit release is received from the target node.

[0201] As shown in signaling flow 1000, the signaling flow between the first network device 120 and the second network device 130 can be via the Xn interface. Alternatively or additionally, the signaling flow between the first network device 120 and the second network device 130 can be via the NG interface, as shown in signaling flow 1100. Signaling flow 1100 also relates to AMF 1110.

[0202] Similar to signaling flow 1000, in signaling flow 1100, QoE measurement control and reporting are performed (410). For example, the first network device 120 can configure multiple QoE measurement procedures for the terminal device 110, and the terminal device 110 can report QoE measurement results based on the multiple QoE measurement configurations.

[0203] The first network device 120 can determine (415) the handover decision to switch the terminal device 110 to the second network device 130. For example, the first network device 120 can make the handover decision based on MeasurementReport and RRM information or any other suitable information.

[0204] The first network device 120 can select (420) the QoE measurement configuration to be transmitted to the second network device 130. For example, it can be based on priority information and such as... Figure 2 Any other suitable information described to select the QoE measurement configuration. That is, the first network device 120 can decide which QoE configuration to send to the second network device 130.

[0205] In some embodiments, the first network device 120 may send (1115) a handover request, such as a handover request message, to the AMF 1110. The handover request message includes the selected QoE configuration. For example, for signaling-based QoE measurements, the selected QoE configuration may be included in a measConfigAppLayerContainer, which is included in the RRC context within the source-to-target transparent container of the handover request. For management-based QoE measurements, the selected QoE configuration may be included in UE application layer measurement configuration information, which is included in the QMC configuration information within the source-to-target transparent container of the handover request.

[0206] In response to receiving a handover request message, AMF 1110 may send a handover request (1120) to the second network device 130. The second network device 130 may receive the handover request. The handover request includes a new QoE configuration. For example, for signaling-based QoE measurements, the selected QoE configuration may be included in a measConfigAppLayerContainer, which is included in the RRC context of the handover request. For management-based QoE measurements, the selected QoE configuration may be included in the UE application layer measurement configuration information, which is included in the QMC configuration information of the handover request.

[0207] The second network device 130 can receive a handover request. The second network device 130 can perform (1125) admission control. For example, if slice information is sent to the second network device 130, slice-aware admission control can be performed (1125). If a PDU session is associated with an unsupported slice, the second network device 130 can reject such a PDU session.

[0208] The second network device 130 can prepare for a Layer 1 (L1) / Layer 2 (L2) handover and send a handover request confirmation (1130) to the AMF 710. The handover request confirmation may include a transparent container to be sent as an RRC message to the terminal device 110 to perform the handover. The second network device 130 may also indicate whether the DAPS handover is accepted.

[0209] In some embodiments, the second network device 130 may determine a new QoE configuration based on the received selected QoE configuration. The second network device 130 may include the new QoE configuration in the handover request confirmation. For example, the new QoE configuration may be in measConfigAppLayerContainer-r15 within measConfigAppLayer-r15, and measConfigAppLayer-r15 may be included in the RRC container within the handover request confirmation.

[0210] The AMF 710 can send a (1135) handover command to the first network device 120. The new QoE configuration can be included in the handover command. For example, the new QoE configuration can be in measConfigAppLayerContainer-r15 within measConfigAppLayer-r15, and measConfigAppLayer-r15 is included in the RRC container in the handover command.

[0211] The first network device 120 can receive a handover command. The first network device 120 can send a (1140) MobilityFromNRCommand to the terminal device 110. A new QoE configuration is included in the MobilityFromNRCommand. The MobilityFromNRCommand can also include a configuration for releasing unselected QoE configurations (also known as a release configuration). For example, the first network device 120 can generate a release configuration for unselected QoE configurations or a release configuration for all QoE configurations configured by the first network device 120. The release configuration can be included in the MobilityFromNRCommand, but can be outside the RRC container generated by the second network device 130. The new QoE configuration can be in measConfigAppLayerContainer-r15 within measConfigAppLayer-r15, which can be included in the targetRAT-MessageContainer within the MobilityFromNRCommand.

[0212] Terminal device 110 can receive a MobilityFromNRCommand with a release configuration. The terminal device can release (1145) (multiple) unselected QoE configurations and apply a new QoE configuration. For example, terminal device 110 can apply a new RRC configuration that includes the new QoE configuration. In this way, terminal device 110 can release unselected QoE configurations.

[0213] Terminal device 110 can detach from the original cell (450) and synchronize with the new target cell. For example, terminal device 110 can synchronize with the target cell and send data to the second network device 130. RRCReconfigurationComplete The message completes the (455) RRC handover process. In the case of DAPS handover, terminal device 110 receives... RRCReconfiguration The message is not separated from the source cell. Terminal device 110 can release the source resources and configuration, and stop receiving / transmitting DL / UL with the source when an explicit release is received from the target node.

[0214] In this way, terminal device 110 can release the QoE configuration(s) of the first network device 120 upon receiving MobilityFromNRCOmmand with release configuration.

[0215] Several embodiments regarding QoE measurement configurations during handover have been described, particularly for NR to LTE handover. These embodiments can be used to improve QoE measurement during handover.

[0216] To address at least some of the aforementioned or other potential problems, an alternative solution for QoE measurement is proposed. According to embodiments of this disclosure, a first network device sends priority information for at least one configuration of quality of experience measurement associated with a terminal device to a third network device. A handover from a first connection to a second connection is to be performed, the first connection being between the terminal device and the first network device, and the second connection being between the terminal device and the third network device. In this way, priority auxiliary information can be exchanged during the handover.

[0217] Figure 12 A signaling stream 1200 for sending priority information between network devices according to some embodiments of the present disclosure is illustrated. For purposes of discussion, reference will be made, for example, by using terminal device 110, first network device 120, and third network device 140. Figure 1 Discuss signaling flow 1200.

[0218] In the following description, it is assumed that the first network device 120 can operate as an NR network node, and the third network device 140 can operate as another NR network node. It should be understood that in some embodiments, the first network device 120 or the third network device 140 can be different network devices or network nodes.

[0219] In signaling flow 1200, it is assumed that terminal device 110 is currently serving in cell 122 of first network device 120. First network device 120 may be referred to as source network device. It is also assumed that cell 142 of third network device 140 is a cell used for handover. Third network device 140 may be referred to as target network device.

[0220] In operation, the first network device 120 sends (1210) priority information for at least one configuration of QoE quality associated with a terminal device (such as terminal device 110) to the third network device 140. A handover from a first connection to a second connection is performed, the first connection being between terminal device 110 and the first network device 120, and the second connection being between terminal device 110 and the third network device 140. The third network device 140 receives (1220) the priority information.

[0221] In some embodiments, the first network device 120 may send a handover request to the third network device 140. Priority information may be included in the request. The handover request may also be referred to as a handover request.

[0222] In some embodiments, priority information may be sent (1210) to the third network device 140 via the Xn interface or the NG interface. For example, priority information may be sent (1210) to the third network device 140 via the AMF.

[0223] Figure 13 Signaling flow 1300 for QoE measurement according to some embodiments of this disclosure is illustrated. For purposes of discussion, reference will be made, for example, by using terminal device 110, first network device 120, and third network device 140. Figure 1 Discuss signaling flow 1300.

[0224] In the following description, it is assumed that the first network device 120 can operate as an NR network node, and the third network device 140 can operate as another NR network node. It should be understood that in some embodiments, the first network device 120 or the third network device 140 can be different network devices or network nodes.

[0225] In signaling flow 1300, it is assumed that terminal device 110 is currently serving in cell 122 of first network device 120. First network device 120 may be referred to as source network device. It is also assumed that cell 142 of third network device 140 is a cell used for handover. Third network device 140 may be referred to as target network device.

[0226] During operation, measurement control and reporting can be performed (1310). A first network device 120 can determine (1315) a handover decision. The handover can proceed from the first network device 120 to the third network device 140. The first network device 120 can send a handover request (1320) to the third network device 140. Priority information of (multiple) QoE configurations can be included in the handover request.

[0227] The third network device 140 can receive a handover request. The third network device 140 can perform (1325) admission control. The third network device 140 can send (1330) handover request confirmation to the first network device 120. The first network device 120 can receive the handover request confirmation.

[0228] In response to receiving a handover request confirmation, the first network device 120 may send (1335) MobilityFromNRCommand to the terminal device 110. In response to receiving MobilityFromNRCommand, the terminal device 110 may (1340) separate from the original cell of the first network device 120 to the new cell of the third network device 140. RAN handover can be completed (135).

[0229] The third network device 140 can use (1350) priority information from the QoE configuration of the first network device 120. It should be understood that, although in Figure 13 In this implementation, signaling can be transmitted via the Xn interface, but in some embodiments, signaling can also be transmitted via the NG interface. This allows priority information to be exchanged during handover.

[0230] In some embodiments, the continuity of QoE measurements for mobility may be shown in Table 13 below, which may be included in TS 38.300.

[0231] Table 13

[0232] It should be understood that some example specifications and implementations are provided above, and the detailed description may be changed.

[0233] Example embodiments of QoE measurement configurations during handover have been described with reference to signaling flows 200, 300, 400, 500, 600, 700, 800, 900, 1000, 1100, 1200, and 1300. In some embodiments, two or more of the embodiments described above, referring to signaling flows 200 through 1300, may be combined. By using these signaling flows, QoE measurement during handover can be improved, especially during handover between RATs within the system.

[0234] Figure 14 A flowchart of a communication method 1400 implemented at a terminal device according to some embodiments of the present disclosure is shown. For discussion purposes, [the following will be discussed]. Figure 1 Angle description method 1400 for terminal device 110 in the middle.

[0235] At box 1410, terminal device 110 receives configuration information from a first network device to switch the connection from the first network device to a second network device. The configuration information includes a second configuration of the quality of experience measurement associated with the second network device, which is different from the first configuration of the quality of experience measurement associated with the first network device.

[0236] At box 1420, terminal device 110 performs experience quality measurement based on the second configuration after switching.

[0237] In some example embodiments, in response to receiving configuration information, terminal device 110 may release a third configuration for the quality of experience measurement configured by the first network device.

[0238] In some example embodiments, terminal device 110 may release a third configuration of the quality of experience measurement configured by the first network device after a handover.

[0239] In some example embodiments, terminal device 110 may receive a first indication from a first network device for the release of a first configuration for a quality of experience measurement.

[0240] In some example embodiments, the first instruction is received before at least one of the following: switching or receiving configuration information.

[0241] In some example embodiments, the configuration information includes a first radio resource control configuration and a second indication, the second indication indicating the release of a second radio resource control configuration configured by a first network device, the second configuration being included in the first radio resource control configuration. Terminal device 110 can apply the first radio resource control configuration and perform the release of the second radio resource control configuration.

[0242] In some example embodiments, the second configuration is determined by the second network device based on the first configuration, and the configuration information includes a third indication of releasing a third configuration for the quality of experience measurement configured by the first network device. In response to receiving the configuration information, the terminal device 110 can execute the release of the third configuration for the quality of experience measurement.

[0243] In some example embodiments, the first network device includes a new radio network node, and the second network device includes an evolved network node.

[0244] Figure 15 A flowchart of a communication method 1500 implemented at a first network device according to some embodiments of the present disclosure is shown. For discussion purposes, [the following will be discussed]. Figure 1 Method 1500 is described from the perspective of the first network device 120 in the middle.

[0245] At box 1510, a first network device 120 sends a request to a second network device to switch from a first connection to a second connection, the first connection being between the terminal device and the first network device, and the second connection being between the terminal device and the second network device. The request includes a first configuration for quality of experience measurement.

[0246] At box 1520, the first network device 120 receives a response to a request from the second network device, the response including a second configuration for experience quality measurement, the second configuration being associated with the first configuration.

[0247] At box 1530, the first network device 120 sends handover configuration information to the terminal device, which includes a second configuration.

[0248] In some example embodiments, the request is sent to the second network device via the access and mobility management function, and the response is received from the second network device via the access and mobility management function.

[0249] In some example embodiments, the first network device 120 may perform a release of the first configuration and send a first release instruction to the terminal device.

[0250] In some example embodiments, the first instruction is sent before at least one of the following: switching, sending a request to a second network device, or sending configuration information to a terminal device.

[0251] In some example embodiments, the response includes a first radio resource control configuration and a second indication, the second indication indicating the release of a second radio resource control configuration configured by a first network device, the first configuration being included in the first radio resource control configuration, and the configuration information including the first radio resource control configuration and the second indication.

[0252] In some example embodiments, the configuration information includes a third indication of the release of a third configuration for a quality of experience measurement configured by the first network device.

[0253] In some example embodiments, the first network device 120 may determine a first configuration for the quality of experience measurement from a plurality of configurations of the quality of experience measurement configured by the first network device.

[0254] In some example embodiments, the first network device 120 may select a first configuration from multiple configurations based on at least one of the following: priority information of multiple configurations, corresponding service types of multiple configurations, multiple time points at which multiple configurations are configured, or corresponding sizes of multiple configurations.

[0255] In some example embodiments, the first network device includes a new radio network node, and the second network device includes an evolved network node.

[0256] Figure 16 A flowchart of a communication method 1600 implemented at a second network device according to some embodiments of the present disclosure is shown. For discussion purposes, [the following will be discussed]. Figure 1 Method 1600 is described from the perspective of the second network device 130 in the middle.

[0257] At box 1610, the second network device 130 receives from the first network device a request to switch from a first connection to a second connection, the first connection being between the terminal device and the first network device, and the second connection being between the terminal device and the second network device. The request includes a first configuration for quality of experience measurement.

[0258] At box 1620, the second network device 130 determines a second configuration for quality of experience measurement based on the first configuration.

[0259] At box 1630, the second network device 130 sends a response to the request to the first network device, the response including a second configuration for experience quality measurement.

[0260] In some example embodiments, a request is received from a first network device via an access and mobility management function, and a response is sent to the first network device via the access and mobility management function.

[0261] In some example embodiments, the response includes a first radio resource control configuration and an indication to release a second radio resource control configuration configured by a first network device, the first configuration being included in the first radio resource control configuration.

[0262] In some example embodiments, the first network device includes a new radio network node, and the second network device includes an evolved network node.

[0263] Figure 17 A flowchart of a communication method 1700 implemented at a first network device according to some embodiments of the present disclosure is shown. For discussion purposes, [the following will be discussed]. Figure 1 Method 1700 is described from the perspective of the first network device 120 in the middle.

[0264] At box 1710, the first network device 120 sends priority information for at least one configuration of the quality of experience measurement associated with the terminal device to the third network device. A handover from a first connection to a second connection is to be performed, the first connection being between the terminal device and the first network device, and the second connection being between the terminal device and the third network device.

[0265] In some example embodiments, the first network device 120 may send a handover request to the third network device, the request including priority information.

[0266] In some example embodiments, priority information is sent to a third network device via access and mobility management functions.

[0267] Figure 18 A flowchart of a communication method 1800 implemented at a third network device according to some embodiments of the present disclosure is shown. For discussion purposes, [the following will be discussed]. Figure 1 Method 1800 is described from the perspective of the third network device 140 in the middle.

[0268] At box 1810, the third network device 140 receives priority information from the first network device for at least one configured quality of experience measurement associated with the terminal device. A handover from a first connection to a second connection is to be performed, the first connection being between the terminal device and the first network device, and the second connection being between the terminal device and the third network device.

[0269] In some example embodiments, the third network device 140 may receive a handover request from the first network device, the request including priority information; and apply the priority information after the handover.

[0270] In some example embodiments, priority information is received from the first network device via access and mobility management functions.

[0271] Figure 19 This is a simplified block diagram of a device 1900 suitable for implementing embodiments of the present disclosure. Device 1900 can be considered as... Figure 1 Another example implementation of any of the devices shown. Thus, device 1900 may be implemented or at least a part thereof at terminal device 110, first network device 120, second network device 130, or third network device 140.

[0272] As shown in the figure, device 1900 includes a processor 1910, a memory 1920 coupled to the processor 1910, a suitable transceiver 1940 coupled to the processor 1910, and a communication interface coupled to the transceiver 1940. The memory 1920 stores at least a portion of a program 1930. The transceiver 1940 can be used for required bidirectional or unidirectional communication. The transceiver 1940 may include at least one of a transmitter 1942 and a receiver 1944. The transmitter 1942 and receiver 1944 may be functional modules or physical entities. The transceiver 1940 has at least one antenna to facilitate communication; however, in practice, the access node mentioned in this application may have several antennas. The communication interface can represent any interface required for communication with other network elements, such as the X2 / Xn interface for bidirectional communication between eNBs / gNBs, the S1 / NG interface for communication between the Mobility Management Entity (MME) / Access and Mobility Management Function (AMF) / SGW / UPF and the eNB / gNB, the Un interface for communication between the eNB / gNB and the Relay Node (RN), or the Uu interface for communication between the eNB / gNB and the terminal equipment.

[0273] Assume that program 1930 includes program instructions that, when executed by the associated processor 1910, enable device 1900 to operate according to embodiments of this disclosure, as referenced herein. Figures 1 to 18 The embodiments discussed herein may be implemented by computer software executable by the processor 1910 of device 1900, or by hardware, or by a combination of software and hardware. Processor 1910 may be configured to implement various embodiments of this disclosure. Furthermore, a combination of processor 1910 and memory 1920 may form processing unit 1950 suitable for implementing various embodiments of this disclosure.

[0274] Memory 1920 can be of any type suitable for a local technology network and can be implemented using any suitable data storage technology, such as, as non-limiting examples, non-transitory computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. Although only one memory 1920 is shown in device 1900, several physically different memory modules may exist in device 1900. As a non-limiting example, processor 1910 can be of any type suitable for a local technology network and may include one or more of the following: general-purpose computer, special-purpose computer, microprocessor, digital signal processor (DSP), and processor based on a multi-core processor architecture. Device 1900 may have multiple processors, such as application-specific integrated circuit chips that are time-dependent on a clock of a synchronous main processor.

[0275] According to embodiments of this disclosure, a terminal device including a circuit system is provided. The circuit system is configured to: receive configuration information from a first network device for switching a connection from the first network device to a second network device, the configuration information including a second configuration for a quality of experience (QA) measurement associated with the second network device, the second configuration being different from a first configuration for a QA measurement associated with the first network device; and perform a QA measurement based on the second configuration after the switch. According to embodiments of this disclosure, the circuit system can be configured to perform any method implemented by the terminal device as described above.

[0276] According to embodiments of the present disclosure, a first network device including a circuit system is provided. The circuit system is configured to: send a request to a second network device for switching from a first connection to a second connection, the first connection being between a terminal device and the first network device, and the second connection being between the terminal device and the second network device, the request including a first configuration for a quality of experience measurement; receive a response from the second network device to the request, the response including a second configuration for the quality of experience measurement, the second configuration being associated with the first configuration; and send switching configuration information to the terminal device, the configuration information including the second configuration. According to embodiments of the present disclosure, the circuit system can be configured to perform any method implemented by the first network device as described above.

[0277] According to embodiments of the present disclosure, a second network device including a circuit system is provided. The circuit system is configured to: receive from a first network device a request to switch from a first connection to a second connection, the first connection being between a terminal device and the first network device, and the second connection being between the terminal device and the second network device, the request including a first configuration for a quality of experience measurement; determine a second configuration for the quality of experience measurement based on the first configuration; and send a response to the request to the first network device, the response including the second configuration for the quality of experience measurement. According to embodiments of the present disclosure, the circuit system can be configured to perform any method implemented by the second network device as described above.

[0278] According to embodiments of the present disclosure, a first network device including a circuit system is provided. The circuit system is configured to send priority information of at least one configuration of a quality of experience measurement associated with a terminal device to a third network device, wherein a handover from a first connection to a second connection is to be performed, the first connection being between the terminal device and the first network device, and the second connection being between the terminal device and the third network device. According to embodiments of the present disclosure, the circuit system can be configured to perform any method implemented by the first network device as described above.

[0279] According to embodiments of this disclosure, a third network device including a circuit system is provided. The circuit system is configured to receive priority information of at least one configured quality of experience measurement associated with a terminal device from a first network device, wherein a handover from a first connection to a second connection is to be performed, the first connection being between the terminal device and the first network device, and the second connection being between the terminal device and the third network device. According to embodiments of this disclosure, the circuit system can be configured to perform any method implemented by the third network device as described above.

[0280] As used herein, the term "circuit system" can refer to hardware circuitry and / or a combination of hardware circuitry and software. For example, a circuit system can be a combination of analog and / or digital hardware circuitry with software / firmware. As another example, a circuit system can be any part of a hardware processor with software, including (multiple) digital signal processors, software, and (multiple) memories, which work together to enable a device, such as a terminal device or a network device, to perform various functions. In yet another example, a circuit system can be hardware circuitry and / or a processor that requires software / firmware to operate, such as a microprocessor or a portion thereof, but which may be absent when software is not required to operate. As used herein, the term circuit system also encompasses an implementation of hardware circuitry or (multiple) processors alone, or a portion thereof, and its accompanying software and / or firmware.

[0281] According to embodiments of this disclosure, a terminal device is provided. The terminal device includes: components for receiving configuration information from a first network device for switching a connection from the first network device to a second network device, the configuration information including a second configuration of a quality of experience (QA) measurement associated with the second network device, the second configuration being different from a first configuration of a QA measurement associated with the first network device; and components for performing a QA measurement based on the second configuration after the switch. In some embodiments, the first device may include components for performing corresponding operations of method 1400. In some example embodiments, the first device may also include components for performing other operations in some example embodiments of method 1400. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module.

[0282] According to embodiments of this disclosure, a first network apparatus is provided. The first network apparatus includes: components for sending a request to a second network device for switching from a first connection to a second connection, the first connection being between a terminal device and the first network device, and the second connection being between the terminal device and the second network device, the request including a first configuration of a quality of experience measurement; components for receiving a response from the second network device to the request, the response including a second configuration of the quality of experience measurement, the second configuration being associated with the first configuration; and components for sending configuration information for the switch to the terminal device, the configuration information including the second configuration. In some embodiments, the second apparatus may include components for performing corresponding operations of method 1500. In some example embodiments, the second apparatus may also include components for performing other operations in some example embodiments of method 1500. This component may be implemented in any suitable form. For example, the component may be implemented in a circuit system or a software module.

[0283] According to embodiments of this disclosure, a second network apparatus is provided. The second network apparatus includes: components for receiving from a first network device a request to switch from a first connection to a second connection, the first connection being between a terminal device and the first network device, and the second connection being between the terminal device and the second network device, the request including a first configuration for a quality of experience measurement; components for determining a second configuration for the quality of experience measurement based on the first configuration; and components for sending a response to the request to the first network device, the response including the second configuration for the quality of experience measurement. In some embodiments, a third apparatus may include components for performing corresponding operations of method 1600. In some example embodiments, the third apparatus may also include components for performing other operations in some example embodiments of method 1600. This component may be implemented in any suitable form. For example, the component may be implemented in a circuit system or a software module.

[0284] According to embodiments of this disclosure, a first network apparatus is provided. The first network apparatus includes: components for transmitting priority information of at least one configuration of experience quality measurement associated with a terminal device to a third network device; and components for performing a switch from a first connection to a second connection to be executed, the first connection being between the terminal device and the first network device, and the second connection being between the terminal device and the third network device. In some embodiments, a fourth apparatus may include components for performing corresponding operations of method 1700. In some example embodiments, the fourth apparatus may also include components for performing other operations in some example embodiments of method 1700. This component may be implemented in any suitable form. For example, the component may be implemented in a circuit system or a software module.

[0285] According to embodiments of this disclosure, a third network device is provided. The third network device includes: components for receiving priority information of at least one configuration of experience quality measurement associated with a terminal device from a first network device; and components for performing a switch from a first connection to a second connection to be executed, the first connection being between the terminal device and the first network device, and the second connection being between the terminal device and the third network device. In some embodiments, the fifth device may include components for performing corresponding operations of method 1800. In some example embodiments, the fifth device may also include components for performing other operations in some example embodiments of method 1800. This component may be implemented in any suitable form. For example, the component may be implemented in a circuit system or a software module.

[0286] In summary, the embodiments of this disclosure provide the following aspects.

[0287] In one aspect, a terminal device is proposed, the terminal device comprising: a processor configured to cause the terminal device to: receive configuration information from a first network device to switch a connection from the first network device to a second network device, the configuration information including a second configuration of a quality of experience measurement associated with the second network device, the second configuration being different from a first configuration of a quality of experience measurement associated with the first network device; and perform a quality of experience measurement based on the second configuration after the switch.

[0288] In some embodiments, the processor is further configured to cause the terminal device to: in response to receiving configuration information, perform the release of a third configuration for the quality of experience measurement configured by the first network device.

[0289] In some embodiments, the processor is further configured to cause the terminal device to: release a third configuration for the quality of experience measurement configured by the first network device after the handover.

[0290] In some embodiments, the processor is further configured to cause the terminal device to: receive from the first network device a first indication of the release of a first configuration for a quality of experience measurement.

[0291] In some embodiments, the first instruction is received before at least one of the following: switching, or receiving configuration information.

[0292] In some embodiments, the configuration information includes a first radio resource control configuration and a second indication, the second indication indicating the release of a second radio resource control configuration configured by a first network device, the second configuration being included in the first radio resource control configuration, and the processor being further configured to cause the terminal device to: apply the first radio resource control configuration; and perform the release of the second radio resource control configuration.

[0293] In some embodiments, the second configuration is determined by the second network device based on the first configuration, the configuration information includes a third indication of releasing a third configuration for the quality of experience measurement configured by the first network device, and the processor is further configured to cause the terminal device to: in response to receiving the configuration information, perform the release of the third configuration for the quality of experience measurement.

[0294] In some embodiments, the first network device includes a new radio network node, and the second network device includes an evolved network node.

[0295] In one aspect, a first network device is proposed, comprising: a processor configured to cause the first network device to: send a request to a second network device for switching from a first connection to a second connection, the first connection being between a terminal device and the first network device, the second connection being between the terminal device and the second network device, the request including a first configuration of a quality of experience measurement; receive a response from the second network device to the request, the response including a second configuration of a quality of experience measurement associated with the first configuration; and send configuration information of the switch to the terminal device, the configuration information including the second configuration.

[0296] In some embodiments, a request is sent to a second network device via an access and mobility management function, and a response is received from the second network device via the access and mobility management function.

[0297] In some embodiments, the processor is further configured to cause the first network device to: perform a release of the first configuration; and send a first instruction of the release to the terminal device.

[0298] In some embodiments, the first instruction is sent before at least one of the following: switching, sending a request to a second network device, or sending configuration information to a terminal device.

[0299] In some embodiments, the response includes a first radio resource control configuration and a second indication, the second indication indicating the release of a second radio resource control configuration configured by a first network device, the first configuration being included in the first radio resource control configuration, and the configuration information including the first radio resource control configuration and the second indication.

[0300] In some embodiments, the configuration information includes a third indication of the release of a third configuration for a quality of experience measurement configured by the first network device.

[0301] In some embodiments, the processor is further configured to cause the first network device to determine a first configuration for the quality of experience measurement from a plurality of configurations of the quality of experience measurement configured by the first network device.

[0302] In some embodiments, the processor is further configured to cause the first network device to select a first configuration from a plurality of configurations based on at least one of the following: priority information of the plurality of configurations, corresponding service types of the plurality of configurations, multiple time points at which the plurality of configurations are configured, or corresponding sizes of the plurality of configurations.

[0303] In some embodiments, the first network device includes a new radio network node, and the second network device includes an evolved network node.

[0304] In one aspect, a second network device is proposed, the second network device comprising: a processor configured to cause the second network device to: receive from a first network device a request to switch from a first connection to a second connection, the first connection being between a terminal device and the first network device, the second connection being between the terminal device and the second network device, the request including a first configuration for quality of experience measurement; determine a second configuration for quality of experience measurement based on the first configuration; and send a response to the first network device to the request, the response including the second configuration for quality of experience measurement.

[0305] In some embodiments, a request is received from a first network device via an access and mobility management function, and a response is sent to the first network device via the access and mobility management function.

[0306] In some embodiments, the response includes a first radio resource control configuration and an indication to release a second radio resource control configuration configured by a first network device, the first configuration being included in the first radio resource control configuration.

[0307] In some embodiments, the first network device includes a new radio network node, and the second network device includes an evolved network node.

[0308] In one aspect, a first network device is proposed, comprising: a processor configured to cause the first network device to: send priority information of at least one configuration of experience quality measurement associated with a terminal device to a third network device, wherein a switch from a first connection to a second connection is to be performed, the first connection being between the terminal device and the first network device, and the second connection being between the terminal device and the third network device.

[0309] In some embodiments, the processor is further configured to cause the first network device to send a handover request to the third network device, the request including priority information.

[0310] In some embodiments, priority information is sent to a third network device via access and mobility management functions.

[0311] In one aspect, a third network device is proposed, comprising: a processor configured to cause the third network device to: receive priority information of at least one configured quality of experience measurement associated with a terminal device from a first network device, wherein a switch from a first connection to a second connection is to be performed, the first connection being between the terminal device and the first network device, and the second connection being between the terminal device and the third network device.

[0312] In some embodiments, the processor is further configured to cause a third network device to: receive a handover request from a first network device, the request including priority information; and apply the priority information after the handover.

[0313] In some embodiments, priority information is received from a first network device via access and mobility management functions.

[0314] In one aspect, a terminal device includes: at least one processor; and at least one memory coupled to and storing instructions thereon, which, when executed by the at least one processor, cause the device to perform the methods implemented by the terminal device discussed above.

[0315] In one aspect, a first network device includes: at least one processor; and at least one memory coupled to and storing instructions thereon, which, when executed by the at least one processor, cause the device to perform the methods implemented by the first network device discussed above.

[0316] In one aspect, a second network device includes: at least one processor; and at least one memory coupled to and storing instructions thereon, which, when executed by the at least one processor, cause the device to perform the methods implemented by the second network device discussed above.

[0317] In one aspect, a third network device includes: at least one processor; and at least one memory coupled to and storing instructions thereon, which, when executed by the at least one processor, cause the device to perform the methods implemented by the third network device discussed above.

[0318] In one aspect, a computer-readable medium having instructions stored thereon, which, when executed on at least one processor, cause at least one processor to perform the method implemented by the terminal device discussed above.

[0319] In one aspect, a computer-readable medium storing instructions that, when executed on at least one processor, cause at least one processor to perform the method implemented by the first network device discussed above.

[0320] In one aspect, a computer-readable medium storing instructions that, when executed on at least one processor, cause the at least one processor to perform the method implemented by the second network device discussed above.

[0321] In one aspect, a computer-readable medium storing instructions that, when executed on at least one processor, cause at least one processor to perform the method implemented by the third network device discussed above.

[0322] In one aspect, a computer program includes instructions that, when executed on at least one processor, cause the at least one processor to perform the method implemented by the terminal device discussed above.

[0323] In one aspect, a computer program includes instructions that, when executed on at least one processor, cause the at least one processor to perform the method implemented by the first network device discussed above.

[0324] In one aspect, a computer program includes instructions that, when executed on at least one processor, cause the at least one processor to perform a method implemented by the second network device discussed above.

[0325] In one aspect, a computer program includes instructions that, when executed on at least one processor, cause the at least one processor to perform the method implemented by the third network device discussed above.

[0326] Generally, the various embodiments of this disclosure can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of this disclosure are illustrated and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that, as non-limiting examples, the blocks, apparatuses, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0327] This disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions that execute in a device on a target real or virtual processor, such as those included in a program module, to perform the above-referenced... Figures 1 to 19 The process or method described herein. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform specific tasks or implement specific abstract data types. In various embodiments, the functionality of a program module can be combined or split among program modules as needed. The machine-executable instructions for a program module can be executed locally or on a distributed device. In a distributed device, a program module can reside on both local and remote storage media.

[0328] Program code used to perform the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that, when executed by the processor or controller, the program code enables the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a stand-alone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0329] The aforementioned program code may be embodied on a machine-readable medium, which may be any tangible medium capable of containing or storing a program used by or in conjunction with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media may include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. More specific examples of machine-readable storage media will include electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0330] Furthermore, although the operations are described in a specific order, this should not be construed as requiring that these operations be performed in the specific order shown or sequentially, or that all the operations shown be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are contained in the above discussion, these details should not be construed as limiting the scope of this disclosure, but rather as descriptions of features specific to particular embodiments. Certain features described in the context of a single embodiment may also be implemented in combination in a single embodiment. Conversely, multiple features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0331] Although this disclosure has been described in language specific to structural features and / or methodological actions, it should be understood that the disclosure as defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as exemplary forms for implementing the claims.

Claims

1. A terminal device, comprising: Processor, the processor being configured to cause the terminal device to: Receive configuration information from a first network device to switch the connection to a second network device, the configuration information including a second configuration of quality of experience measurements associated with the second network device, the second configuration being different from a first configuration of quality of experience measurements associated with the first network device; and After the switch, experience quality measurement is performed based on the second configuration.

2. The terminal device according to claim 1, wherein the processor is further configured to cause the terminal device to: In response to receiving the configuration information, a third configuration for the experience quality measurement configured by the first network device is released.

3. The terminal device according to claim 1, wherein the processor is further configured to cause the terminal device to: After the switch, a third configuration for the quality of experience measurement configured by the first network device is released.

4. The terminal device according to claim 1, wherein the processor is further configured to cause the terminal device to: Receive a first instruction from the first network device to release a first configuration for the experience quality measurement.

5. The terminal device of claim 4, wherein the first instruction is received before at least one of the following: the switching, or the reception of the configuration information.

6. The terminal device of claim 1, wherein the configuration information includes a first radio resource control configuration and a second indication, the second indication indicating the release of a second radio resource control configuration configured by the first network device, the second configuration being included in the first radio resource control configuration, and The processor is also configured to enable the terminal device to: Apply the first radio resource control configuration; and The release is performed according to the second radio resource control configuration.

7. The terminal device of claim 1, wherein the second configuration is determined by the second network device based on the first configuration. The configuration information includes a third indication of releasing a third configuration for the quality of experience measurement configured by the first network device, and The processor is also configured to cause the terminal device to: in response to receiving the configuration information, execute the release of the third configuration of the experience quality measurement.

8. The terminal device according to any one of claims 1 to 7, wherein the first network device includes a new radio network node, and the second network device includes an evolved network node.

9. A first network device, comprising: The processor is configured to cause the first network device to: Send a request to a second network device to switch from a first connection to a second connection, the first connection being between the terminal device and the first network device, and the second connection being between the terminal device and the second network device, the request including a first configuration of experience quality measurement; Receive a response to the request from the second network device, the response including a second configuration for experience quality measurement, the second configuration being associated with the first configuration; as well as The configuration information for the handover is sent to the terminal device, and the configuration information includes the second configuration.

10. The first network device of claim 9, wherein the request is sent to the second network device via the access and mobility management function, and the response is received from the second network device via the access and mobility management function.

11. The first network device according to claim 9 or claim 10, wherein the processor is further configured to cause the first network device to: Perform the release of the first configuration; and Send the first instruction for release to the terminal device.

12. The first network device of claim 11, wherein the first instruction is sent prior to at least one of the following: The switching Send the request to the second network device, or The configuration information is sent to the terminal device.

13. The first network device of claim 9 or claim 10, wherein the response includes a first radio resource control configuration and a second indication, the second indication indicating the release of a second radio resource control configuration configured by the first network device, the first configuration being included in the first radio resource control configuration, and The configuration information includes the first radio resource control configuration and the second indication.

14. The first network device according to claim 9 or claim 10, wherein the configuration information includes a third indication of releasing a third configuration of a quality of experience measurement configured by the first network device.

15. The first network device according to any one of claims 9 to 14, wherein the processor is further configured to cause the first network device to: The first configuration of the quality of experience measurement is determined from a plurality of configurations of the quality of experience measurement configured by the first network device.

16. The first network device of claim 15, wherein the processor is further configured to cause the first network device to: The first configuration is selected from the plurality of configurations based on at least one of the following: The priority information of the multiple configurations, The corresponding service types of the multiple configurations, Multiple time points, at which the multiple configurations are configured, or The corresponding sizes of the multiple configurations.

17. The first network device according to any one of claims 9 to 16, wherein the first network device includes a new radio network node, and the second network device includes an evolved network node.

18. A communication method implemented at a first network device, comprising: Priority information for at least one configuration of experience quality measurement associated with the terminal device is sent to a third network device. A switch from a first connection to a second connection is to be performed, wherein the first connection is between the terminal device and the first network device, and the second connection is between the terminal device and the third network device.

19. A communication method implemented at a third network device, comprising: Priority information for at least one configuration of experience quality measurement associated with the terminal device is received from the first network device. A switch from a first connection to a second connection is to be performed, wherein the first connection is between the terminal device and the first network device, and the second connection is between the terminal device and the third network device.

20. A computer-readable medium storing instructions that, when executed on at least one processor, cause the at least one processor to perform the method according to any one of claims 18 to 19.

Images