QoE for RRC-IDLE mode

Abstract

Embodiments of the present disclosure relate to handling of QoE sessions existing in RRC-IDLE mode. After the access network equipment determines that the terminal equipment is disconnected from the first access network equipment, QoE (Quality of Experience) measurement collection needs to be carried out; sending a QoE context identifier to the terminal device on the basis of determining that the terminal device is to execute QoE measurement collection after disconnection, the QoE context identifier identifying QoE context information for QoE measurement collection; and transmitting the QoE context identifier and the QoE context information to the core network device. As provided in the present disclosure, the stored QoE report may be sent to a new serving gNB, and then sent to an MCE.

Description

Technical Field

[0001] Various example embodiments relate to the field of telecommunications, and more particularly to methods, devices, apparatuses and computer-readable storage media for Quality of Experience (QoE) Measurement Collection (QME) in Radio Resource Control Idle (RRC-IDLE) mode of a terminal device. Background Art

[0002] The QoE Measurement Collection (QME) feature allows the collection of QoE measurements (delay, jitter, etc.) generated by the application layer in the User Equipment (UE). This feature was specified for 3G, LTE, and was introduced in New Radio (NR) in Rel-17. In Rel-17, for NR, three services were associated with the collection of QoE measurements in RRC_CONNECTED mode, but in Rel-18, the UE may need to collect and store QoE measurements in RRC_IDLE mode. Summary of the invention

[0003] Generally speaking, example embodiments of the present disclosure provide a solution for QME in RRC_IDLE mode of a terminal device.

[0004] In a first aspect, a first access network device is provided. The first access network device includes at least one processor and at least one memory storing instructions. When the instructions are executed by the at least one processor, the first access network device at least: determines that a terminal device is going to perform quality of experience (QoE) measurement collection after being disconnected from the first access network device; based on determining that the terminal device is going to perform QoE measurement collection after being disconnected, sends a QoE context identifier to the terminal device, the QoE context identifier identifying QoE context information for QoE measurement collection; and sends the QoE context identifier and the QoE context information to a core network device.

[0005] In a second aspect, a second access network device is provided. The second network device includes at least one processor and at least one memory storing instructions. When the instructions are executed by at least one processor, the first access network device at least: determines that a terminal device that performs quality of experience QoE measurement collection in an idle state is connected to the second access network device; receives a QoE context identifier from the terminal device, the QoE context identifier identifying QoE context information used for the QoE measurement collection; sends a request for QoE context information associated with the QoE context identifier to a core network device; and receives QoE context information from the core network device.

[0006] In a third aspect, a terminal device is provided. The terminal device includes at least one processor and at least one memory storing instructions. When the instructions are executed by the at least one processor, the terminal device at least: receives a quality of experience (QoE) configuration for performing QoE measurement collection in an idle state from a first access network device, receives a QoE context identifier from the first access network device, and the QoE context identifier identifies QoE context information for QoE measurement collection; stores the QoE context identifier in the terminal device; disconnects from the first access network device and connects to a second access network device; and transmits the QoE context identifier to the second access network device based on the connection to the second access network device.

[0007] In a fourth aspect, a method implemented at a first access network device is provided. The method includes determining that a terminal device is to perform quality of experience (QoE) measurement collection after being disconnected from the first access network device; based on determining that the terminal device is to perform QoE measurement collection after being disconnected, sending a QoE context identifier to the terminal device, the QoE context identifier identifying QoE context information for QoE measurement collection; and sending the QoE context identifier and the QoE context information to a core network device.

[0008] In a fifth aspect, a method implemented at a second network access device is provided. The method includes determining that a terminal device that performs quality of experience (QoE) measurement collection in an idle state is connected to a second access network device; based on determining that the terminal device is connected to the second access network device, receiving a QoE context identifier from the terminal device, the QoE context identifier identifying QoE context information used for the QoE measurement collection; sending a request for QoE context information associated with the QoE context identifier to a core network device; and receiving the QoE context information from the core network device.

[0009] In a sixth aspect, a method implemented at a terminal device is provided. The method includes receiving a quality of experience (QoE) configuration for performing QoE measurement collection in an idle state from a first access network device, receiving a QoE context identifier from the first access network device, the QoE context identifier identifying QoE context information for the QoE measurement collection; storing the QoE context identifier in the terminal device; disconnecting from the first access network device; connecting to a second access network device; and transmitting the QoE context identifier to the second access network device based on the connection to the second access network device.

[0010] In a seventh aspect, a first apparatus is provided. The first apparatus includes a component for determining that a terminal device is to perform quality of experience (QoE) measurement collection after being disconnected from the first apparatus; a component for sending a QoE context identifier identifying QoE context information for the QoE measurement collection to the terminal device based on determining that the terminal device is to perform QoE measurement collection after being disconnected; and a component for sending the QoE context identifier and the QoE context information to a core network device.

[0011] In an eighth aspect, a second device is provided. The second device includes a component for determining that a terminal device performing quality of experience (QoE) measurement collection in an idle state is connected to the second device; a component for receiving a QoE context identifier identifying QoE context information for the QoE measurement collection from the terminal device based on determining that the terminal device is connected to the second device; a component for sending a request for QoE context information associated with the QoE context identifier to a core network device; and a component for receiving the QoE context information from the core network device.

[0012] In a ninth aspect, a third device is provided. The third device includes a component for receiving a QoE configuration for performing QoE measurement collection in an idle state from a first access network device; a component for receiving a QoE context identifier identifying QoE context information for the QoE measurement collection from the first access network device; a component for storing the QoE context identifier in the third device; a component for disconnecting from the first access network device; a component for connecting to a second access network device; and a component for transmitting the QoE context identifier to the second access network device based on the connection to the second access network device.

[0013] In a tenth aspect, a computer program comprising instructions is provided, which, when executed by a first device, causes the first device to at least: determine that a terminal device is to perform quality of experience (QoE) measurement collection after being disconnected from the first device; based on determining that the terminal device is to perform QoE measurement collection after being disconnected, send a QoE context identifier to the terminal device, wherein the QoE context identifier identifies QoE context information used for the QoE measurement collection; and send the QoE context identifier and the QoE context information to a core network device.

[0014] In an eleventh aspect, a computer program comprising instructions is provided, which, when executed by a second device, causes the second device to at least: determine that a terminal device that performs quality of experience (QoE) measurement collection in an idle state is connected to the second device; based on determining that the terminal device is connected to the second device, receive a QoE context identifier from the terminal device, the QoE context identifier identifying QoE context information used for the QoE measurement collection; send a request for QoE context information associated with the QoE context identifier to a core network device; and receive the QoE context information from the core network device.

[0015] In a twelfth aspect, a computer program comprising instructions is provided, which, when executed by a third device, causes the third device to at least: receive a quality of experience (QoE) configuration for performing QoE measurement collection in an idle state from a first access network device; receive a QoE context identifier from the first access network device, the QoE context identifier identifying QoE context information used for the QoE measurement collection; store the QoE context identifier in the third device; disconnect from the first access network device; connect to a second access network device; and transmit the QoE context identifier to the second access network device based on the connection to the second access network device.

[0016] In the thirteenth aspect, a first network access device is provided, comprising: a determination circuit configured to determine that a terminal device is to perform quality of experience (QoE) measurement collection after being disconnected from the first access network device; based on determining that the terminal device is to perform QoE measurement collection after being disconnected, a sending circuit configured to send a QoE context identifier to the terminal device, wherein the QoE context identifier identifies Qo context information used for the QoE measurement collection; and a sending circuit configured to send the QoE context identifier and the QoE context information to a core network device.

[0017] In a fourteenth aspect, a second network access device is provided, comprising: a determination circuit configured to determine that a terminal device performing quality of experience (QoE) measurement collection in an idle state is connected to the second access network device; based on determining that the terminal device is connected to the second access network device, a receiving circuit is configured to receive a QoE context identifier from the terminal device, the QoE context identifier identifying QoE context information used for the QoE measurement collection; a sending circuit configured to send a request for the QoE context information associated with the QoE context identifier to a core network device; and a receiving circuit configured to receive the QoE context information from the core network device.

[0018] In a fifteenth aspect, a terminal device is provided, comprising: a receiving circuit configured to receive a quality of experience (QoE) configuration for performing QoE measurement collection in an idle state from a first access network device; a receiving circuit configured to receive a QoE context identifier from the first access network device, the QoE context identifier identifying QoE context information used for the QoE measurement collection; a storage circuit configured to store the QoE context identifier in the terminal device; a disconnection circuit configured to disconnect from the first access network device; a connection circuit configured to connect to a second access network device; and based on the connection to the second access network device, a sending circuit configured to send the QoE context identifier to the second access network device.

[0019] In a sixteenth aspect, a non-transitory computer-readable medium comprising program instructions is provided, wherein the program instructions are used to cause an apparatus to at least execute a method according to any one of the fourth to sixth aspects above.

[0020] It should be understood that the summary is not intended to identify the key or essential features of the embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Some example embodiments will now be described with reference to the accompanying drawings, in which:

[0022] Figure 1 shows an example communication network in which embodiments of the present disclosure may be implemented;

[0023] Figure 2 A flow chart illustrating an example of a process for QoE according to some embodiments of the present disclosure is shown;

[0024] Figure 3 shows a flow chart illustrating another example of a process for QoE according to some embodiments of the present disclosure;

[0025] Figure 4 A flowchart of a method implemented at a first access network device according to some embodiments of the present disclosure is shown;

[0026] Figure 5 A flowchart of a method implemented at a second access network device according to some other embodiments of the present disclosure is shown;

[0027] Figure 6 A flowchart of a method implemented at a terminal device according to some other embodiments of the present disclosure is shown;

[0028] Figure 7 shows a simplified block diagram of an apparatus suitable for implementing an embodiment of the present disclosure; and

[0029] Figure 8 A block diagram of an example computer-readable medium is shown in accordance with some embodiments of the present disclosure.

[0030] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION

[0031] The principles of the present disclosure will now be described with reference to some example 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 the present disclosure without implying any limitation on the scope of the present disclosure. The disclosure described herein can be implemented in various ways different from the ways described below.

[0032] In the following description and claims, unless defined otherwise, 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 belongs.

[0033] References in this disclosure to "one embodiment," "an embodiment," "an example embodiment," etc., indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes the particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in conjunction with an embodiment, it is considered to be within the knowledge of a person skilled in the art to affect such feature, structure, or characteristic in conjunction with other embodiments (whether or not explicitly described).

[0034] It should be understood that although the terms "first" and "second", etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element, and similarly, a second element may be referred to as a first element. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0035] The terms used herein are only used for the purpose of describing specific embodiments and are not intended to limit the exemplary embodiments. As used herein, the singular forms "one", "an" and "the" are also intended to include plural forms unless the context clearly indicates otherwise. It will also be understood that the terms "include", "comprise", "have", "have", "include" and / or "contain" specify the presence of the features, elements and / or components, etc. when used herein, but do not exclude the presence or addition of one or more other features, elements, components and / or their combinations. As used herein, "at least one of the following: "a list of two or more elements" and "at least one of the list of two or more elements" and similar wording, wherein the list of two or more elements is connected by "and" or "or", means at least any one element, or at least any two or more elements, or at least all elements.

[0036] As used in this application, the term "circuitry" may refer to one, more than one, or all of the following:

[0037] (a) only hardware circuit implementation (e.g., only implementation in analog and / or digital circuits) and

[0038] (b) a combination of hardware circuitry and software, such as (where applicable):

[0039] (i) a combination of analog and / or digital hardware circuitry and software / firmware, and

[0040] (ii) a hardware processor (including a digital signal processor) with software, software and any portion of memory that work together to enable a device such as a mobile phone or server to perform various functions) and

[0041] (c) Hardware circuits and / or processors (e.g., a microprocessor or a portion of a microprocessor) that require software (e.g., firmware) to operate, but where software is not required to operate, the software may not be present.

[0042] This definition of circuitry applies to all uses of this term in this application, including in any claims. As another example, as used in this application, the term circuitry also covers an implementation of only a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its (or its) accompanying software and / or firmware. The term circuitry also covers (for example and if applicable to a particular claim element) a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in a server, a cellular network device or other computing or network device.

[0043] As used herein, the term "communication network" refers to a network that complies with any suitable communication standard, such as New Radio (NR), Long Term Evolution (LTE), Advanced LTE (LTE-A), Wideband Code Division Multiple Access (WCDMA), High Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. In addition, the communication between the terminal equipment and the network equipment in the communication network can be performed according to any suitable generation of communication protocols, including but not limited to the first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, future fifth generation (5G) communication protocols, and / or any other protocols currently known or to be developed in the future. The embodiments of the present disclosure can be applied to various communication systems. In view of the rapid development of communication, there are of course future types of communication technologies and systems, which can be used to implement the present disclosure. It should not be regarded as limiting the scope of the present invention to the above-mentioned systems.

[0044] As used herein, the terms "network equipment" and "access network equipment" refer to nodes in a communication network, via which a terminal device accesses the network and receives services from it. Depending on the terminology and technology applied, a network device may refer to a base station (BS) or an access point (AP), for example, a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), a NR NB (also called a gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, a low-power node such as a femto, a pico, etc.

[0045] The term "terminal device" refers to any terminal device capable of wireless communication. As an example and not limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS) or access terminal (AT). The terminal device may include, but is not limited to, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet computer, a wearable terminal device, a personal digital assistant (PDA), a portable computer, a desktop computer, an image capture terminal device such as a digital camera, a game terminal device, a music storage and playback device, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, a laptop embedded device (LEE), a laptop mounted device (LME), USB dongles, smart devices, wireless client equipment (CPE), an Internet of Things (IoT) device, a watch or other wearable device, a head mounted display (HMD), a vehicle, a target, medical equipment and applications (e.g., remote surgery), industrial equipment and applications (e.g., robots and / or other wireless devices operating in an industrial and / or automated process chain environment, consumer electronic devices, devices operating on a commercial and / or industrial wireless network, etc. In the following description, the terms "terminal device", "communication device", "terminal", "user equipment" and "UE" may be used interchangeably.

[0046] As mentioned above, the QMC feature allows the collection of QoE measurements (delay, jitter, etc.) generated by the application layer in the terminal device and collected via the control plane of the radio interface (i.e., through the RRC layer). The QoE feature was specified for 3G, LTE and was introduced in Rel-17 in NR. Specific signaling radio bearers (SRBs) such as SRB4 are used to send QoE measurements to the network. In Rel-17, for NR, three services were relevant for the collection of QoE measurements (Dynamic Adaptive Streaming over HTTP (DASH), Multimedia Telephony Service for IMS (MTSI), and Virtual Reality (VR)). But in Rel-18, the Multicast Broadcast Service (MBS) service will be part of the collection. With this new service, the terminal device should be able to collect and store QoE measurements in RRC_IDLE and RRC_INACTIVE modes.

[0047] MBS is a new feature in 5G defined in Rel-17. MBS has been designed to allow resource-efficient transmission to multiple terminal users who need to receive the same content. And since broadcast is extended information only in the downlink (DL), it can even be used in RRC idle mode, that is, all terminal devices in the broadcast service area are authorized to receive data. 5G-MBS was introduced in 3GPP with Rel-17. It will be further standardized to support new Rel-18 targets in terms of radio access network (RAN) and core network (CN). Based on Rel-17 work, broadcast services can be received in all RRC states, while multicast can only be received in the RRC connected state. However, the purpose of Rel-18 is to also allow terminal devices to receive multicast in the RRC inactive state. The main difference between broadcast and multicast is that the terminal device joins the multicast session through non-access stratum (NAS) layer signaling, and the network is unaware that the terminal device receives broadcast services.

[0048] In Rel-17, for the QMC mechanism for RRC connection or inactivity, in addition to the container AppLayerMeasConfig sent to the terminal device app layer, there are some additional QMC context parameters used by the network device, such as MCEaddress (the address of the measurement collection entity (MCE)), QoE reference identification (ID) (the ID assigned to the QoE collection job) and Areascope (the area where QoE measurements are collected). The terminal device is unaware of these parameters (Note: QoE reference ID and area information can be included in the AppLayerMeasConfig container).

[0049] When the terminal device returns to RRC connection from idle mode, due to the new connection establishment, there is no QMC context of the terminal device in the new serving network device or any previous serving network device, because the terminal device context is not stored in the RAN when the terminal device is in idle mode. In the absence of these QMC contexts, the network device cannot forward the QoE measurement data collected by the terminal device to the corresponding MCE, and cannot manage the QoE measurement continuity of the terminal device, and will not know the configured RAN visible reports. For example, assume that the network device forwards the collected QoE measurement results to the MCE, but does not know the MCE address (where the data should be forwarded).

[0050] According to an embodiment of the present disclosure, a solution for QoE measurement collection in RRC idle mode is provided. When a terminal device is to be released as idle and the terminal device has a QoE measurement configuration that will not be deleted in idle mode (e.g., QMC configured for MBS), the last serving network device sends a QoE context identifier (e.g., "QoEInfo") to the terminal device access layer (AS) for storage. When the terminal device returns to RRC connected mode, the terminal device transmits the QoE context identifier to the current serving network device. The serving network device may obtain QMC context information from the core network using the QoE context identifier. The principles and embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings.

[0051] Figure 1 1 shows a schematic diagram of an example communication network 100 in which some embodiments of the present disclosure may be implemented. Figure 1 As shown, the communication network 100 may include a terminal device 110 and network devices 120 and 130. The network device 120 may provide a group of cells (for convenience, only one cell 121 is shown) to serve one or more terminal devices. The network device 130 may also provide a group of cells (for convenience, only one cell 131 is shown) to serve one or more terminal devices. For convenience, the term "group of cells" may be used interchangeably with "cell group". In some embodiments, the terminal device 110 may be located in the cell 121 and served by the network device 120. In some embodiments, the terminal device 120 may be located in the cell 131 and served by the network device 130.

[0052] The communication network 100 may further include a core network device 140, for example, a core network device carrying an access and mobility management function (AMF). The communication network 100 may further include a measurement collection entity (MCE) 160 and an operation management and maintenance (OAM) 150. It should be understood that AMF 140, MCE 160 and OAM 150 are merely examples, and any suitable form is also feasible.

[0053] In some embodiments, the terminal device 110 may perform signaling-based QoE measurement. In this case, the OAM 150 may initiate activation of QoE measurement for a specific terminal device via the CN, and the network device (eg, the network device 120) may receive one or more QoE measurement configurations.

[0054] In some embodiments, the network device 120 may detect that the terminal device 110 may enter idle mode. The network device 120 may then send a QoE context identifier for storage to the terminal device 110AS. When the terminal device 110 returns to RRC connection mode, the terminal device 110 transmits the QoE context identifier to the currently serving network device, such as the network device 130 or the network device 120. The network device 130 may obtain QMC context information from the AMF 140 using the QoE context identifier. In some embodiments, the terminal device 110 and the network device 120 may communicate via a direct SRB between the terminal device 110 and the network device 120. In some embodiments, the terminal device 110 and the network device 130 may communicate via a direct SRB between the terminal device 110 and the network device 130.

[0055] It should be understood that the number of network devices and terminal devices is only for illustrative purposes and does not imply any limitation. System 100 may include any suitable number of network devices and terminal devices suitable for implementing the embodiments of the present disclosure. Although not shown, it should be understood that one or more terminal devices may be located in cell 101 or 102.

[0056] The communication in the communication system 100 can be implemented according to any appropriate communication protocol, including but not limited to cellular communication protocols of the first generation (1G), the second generation (2G), the third generation (3G), the fourth generation (4G) and the fifth generation (5G), such as wireless local area network communication protocols such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11, and / or any other protocol currently known or developed in the future. In addition, the communication can utilize any appropriate wireless communication technology, including but not limited to: code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), frequency division duplex (FDD), time division duplex (TDD), multiple input multiple output (MIMO), orthogonal frequency division multiplexing (OFDM), discrete Fourier transform spread OFDM (DFT-s-OFDM) and / or any other technology currently known or to be developed in the future.

[0057] Reference now Figure 2 , which illustrates a process 200 for QoE measurement in RRC idle mode according to some embodiments of the present disclosure. For the purpose of discussion, reference will be made to Figure 1 The process 200 is described. The process 200 may include a terminal device 110, a network device 120 acting as a first access network device, a network device 130 acting as a second access network device, and Figure 1 It should be understood that although the AMF 140 shown in Figure 1The process 200 is described in the communication system 100 of FIG. 1 , but the process can also be applied to other communication scenarios in which different network devices are jointly deployed to provide corresponding service cells. It should also be understood that although the number of terminal devices 110 is discussed, similar processes can be applied to any other terminal devices.

[0058] As shown in the process 200, the terminal device 110 may receive (210) a QoE configuration 202 from the first access network device 120. And the first access network device 120 may determine 215 that the terminal device 110 is to perform QMC in idle mode. Therefore, when the terminal device 110 enters idle mode, the terminal device 110 may have a QoE measurement configuration that will not be deleted in idle mode. For example, QoE measurement may be used for MBS. In some embodiments, the access network device 120 may determine 215 that the terminal device 110 is to perform QoE measurement collection after disconnecting from the first access network device 120. And based on the determination, the first access network device 120 may send a QoE context identifier 206 to the terminal device 110. The QoE context identifier 206 may identify QoE context information 212 for QoE measurement collection. And the first access network device 120 may send 230 the QoE context identifier 206 and the QoE context information 212 to the AMF 140.

[0059] As shown in process 200, the first access network device 120 may send (230) a QoE context identifier 206 and QoE context information 212 to the AMF 140. Upon receiving (235) the QoE context identifier 206 and the QoE context information 212, the AMF 140 stores (240) the QoE context identifier 206 and the associated QoE context information 212. The access network devices 120 and 130 may then later retrieve the QoE context information 212 via the QoE context identifier 206. The first access network device 120 may transmit 220 the QoE context identifier 206 to the terminal device 110. Upon receiving (210) the QoE context identifier 206, the terminal device 110 stores (245) the QoE context identifier 212. The terminal device 110 may then disconnect (250) from the first access network device 120.

[0060] When the terminal device 110 returns to the connected mode, the terminal device 110 may connect (255) to the second access network device 130 and transmit (265) the QoE context identifier 206 to the second access network device 130. Upon receiving (270) the QoE context identifier 206, the second access network device 130 may send (275) a request for QoE context information 212 including the QoE context identifier 206 to the AMF 140. The first access network device 120 and the AMF use the QoE context identifier 206 to identify the relevant QoE context information 212. Upon receiving (280) the request, the AMF 140 may send (285) the QoE context information 212 to the second access network device 130. Therefore, the second access network device 130 can receive (290) the QoE context information 212 from the AMF140, and can obtain the MCE address in the QoE context information 212, and forward the QoE report received from the terminal device 110 and executed during the idle mode to the AMF140.

[0061] Reference now Figure 3 , which shows a detailed process 300 for QoE measurement in RRC idle mode according to some embodiments of the present disclosure. For the purpose of discussion, reference will be made to Figure 1 Process 300 is described. Process 300 may include the following: Figure 1 The terminal device 110, network device 120, network device 130, AMF 140, MCE 142 and OAM 150 are shown. It should be understood that although Figure 1 The process 300 is described in the communication system 100 of FIG. 1 , but the process can also be applied to other communication scenarios in which different network devices are jointly deployed to provide corresponding service cells. It should also be understood that although the number of terminal devices 110 is discussed, similar processes can be applied to any other terminal devices.

[0062] As shown in process 300, OAM 150 may send (301) a QMC configuration 302 to network device 120 for QoE measurement collection. Alternatively, OAM may send (304) the QMC configuration 302 to AMF 140 for QMC measurement collection. AMF 140 may then send (307) the QMC configuration 302 to network device 120 for QMC measurement collection of terminal device 110. Upon receiving (303) the QMC configuration from OAM 150 or (309) the QMC configuration from AMF 140, network device 120 may send (310) a QMC activation message 311 for QMC to terminal device 110 via an RRC message. The AS (terminal device-RRC) of terminal device 110 may send (313) an activation command and a QMC configuration 314 to the application layer of terminal device 110 for QMC. The QMC configuration includes a QoE configuration. The QoE configuration is determined based at least in part on the QoE context information. The QoE context information is identified by a QoE context identifier.

[0063] When QoE measurements are available, the application layer may send (316) a QoE report 317 to the AS of the terminal device 110. The AS of the terminal device 110 then sends (319) the report 317 to the network device 120. The network device 120 forwards (322) the report 317 to the MCE 160 based on the QoE context information.

[0064] When the terminal device 110 enters the idle mode, the terminal device 110 may have a QoE measurement configuration that will not be deleted in the idle mode. For example, the QoE measurement may be used for MBS.

[0065] In some embodiments, in order to maintain the QoE context information, the network device 120 may determine that the terminal device 110 is about to perform QoE measurement collection after being disconnected from the network device 120. And based on this determination, the network device 120 may send a QoE context identifier to the terminal device 110. The QoE context identifier may identify the QoE context information for QoE measurement collection. The access network device 120 may send the QoE context identifier and the QoE context information to the AMF 140.

[0066] As shown in process 300, network device 120 may send 325 a QoE context identifier and QoE context information 326 to AMF 140. AMF 140 stores 331 the QoE context identifier and the QoE context information. Network devices 120 and 130 may then later retrieve the QoE context information using the QoE context identifier.

[0067] In some embodiments, after the network device 120 has determined that the terminal device 110 will be disconnected from the network device 120 , the QoE context identifier and the QoE context information are sent to the AMF 140 .

[0068] In some embodiments, the QMC context information may include the complete QoE configuration of the terminal device 110, the MCE address, and the RAN-visible QoE (RV-QoE) configuration of the terminal device 110. The QMC context information may also contain a QoE reference ID and a regional scope.

[0069] As shown in process 300, network device 120 may send (328) an RRC message including a QoE context identifier 329 to terminal device 110. The RRC message may be any RRC message. For example, the RR message is, but is not limited to, an RRCRelease message or an RRCReconfiguration message. Terminal device 110 may store (332) the QoE context identifier.

[0070] In some embodiments, the QoE context identifier is sent to the terminal device 110 after the network device 120 has determined that the terminal device 110 will disconnect from the network device 120. Alternatively, the QoE context identifier is sent at an earlier point in time to ensure better robustness against radio connection failures.

[0071] In some embodiments, the QoE context identifier may be a QoE reference ID or an ID that may be mapped to a QoE reference ID. Alternatively, there may be a container containing the entire relevant configuration (including QMC context information). In this case, the network device 120 may send the container to the terminal device 110, and the terminal device 110 may return the container after reconnecting to the network device 120 or connecting to another network device. In this case, the network device 120 may not send the QoE context identifier and the QoE context information to the AMF 140. In some embodiments, the QoE context identifier may be terminal device specific. Alternatively, several terminal devices may share the same QoE configuration and thus the same QoE context identifier.

[0072] As shown in process 300, while the terminal device 110 remains in idle mode, the application layer of the terminal device 110 may send (333) a QoE report 334 to the AS of the terminal device 110. Alternatively, when the connection with the network is restored, the application layer of the terminal device 110 may store the QoE report in a memory of the application layer before forwarding the QoE report to the AS of the terminal device 110. When the terminal device 110 returns to a connection mode with another network device 130, the terminal device 110 may send (336) an RRC message including a QoE context identifier to the network device 130. The RRC message may be any RRC message. For example, the RRC message is, but is not limited to, an RRCConnectSetupComplete message.

[0073] The network device 130 may send (339) a request for QoE context information with a QoE context identifier 329 to the AMF 140. The QoE context identifier is used to identify the QMC context information. In some embodiments, the network device 130 may obtain all or part of the QMC context information from the AMF 140 using the QoE context identifier.

[0074] AMF 140 may send (342) a QMC context configuration 343 to network device 130. Network device 130 may send (345) an RRC configuration 346 of SRB4 of terminal device 110 for sending the stored QoE report. Terminal device 110 may send (348) a QoE report 334 stored during idle mode to network device 130. Based on the QMC context information received from AMF 140, network device 130 may forward (351) the QoE report 334 to MCE 160 via the MCEAddress that is part of the QoE context information received from AMF 140.

[0075] In some embodiments, the network device 130 may configure a new QMC configuration for the terminal device 110. Alternatively, the network device 130 may indicate to the terminal device 110 that the old QMC configuration may be continuously used. Alternatively, the network device 130 may indicate to the terminal device 110 that the QMC configuration is to be stopped. Alternatively, the network device 130 may reuse the RAN Visible (RV)-QoE configuration used before the idle mode of the terminal device 110.

[0076] In some cases, the application layer of the terminal device 110 may detect (354) the end of the recording duration, or meet other stopping criteria. The application layer of the terminal device 110 may then send (355) a QMC session end indication 356 to the AS layer of the terminal device 110. The AS layer of the terminal device 110 may send (358) the QMC session end indication 356 to the network device 130. The network 130 stores (361) the session end information in the terminal device context. The network device 130 sends (362) the QMC session end indication 356 to the MCE 160. The terminal device 110 then transitions to the RRC idle mode.

[0077] The network device 120 sends (365) a terminal device context release request 366 to the AMF 140. The AMF 140 sends (368) a terminal device context release command 369 to the network device 120. The network device 120 sends (371) an indication of a terminal device context release completion message 372 to the AMF 140. The indication regarding the QoE session is ended by the terminal device 110. The AMF 140 then releases (374) the QMC context.

[0078] Figure 4 FIG. 4 is a flow chart showing an example method 400 implemented at an access network device according to some embodiments of the present disclosure. For the purpose of discussion, reference will be made to Figure 1 The method 400 is described from the perspective of the access network device 120 .

[0079] At block 410, the access network device 120 determines that the terminal device 110 is to perform quality of experience QoE measurement collection after disconnecting from the access network device 120. Based on the determination that the terminal device 110 is to perform QoE measurement collection after disconnection, at block 420, the access network device 120 sends a QoE context identifier to the terminal device 110, the QoE context identifier identifying QoE context information for QoE measurement collection. At block 430, the access network device 120 sends the QoE context identifier and the QoE context information to the core network device 140.

[0080] In some embodiments, the access network device 120 sends the QoE context identifier to the terminal device 110 by determining that the terminal device 110 will be disconnected from the access network device 120, and based on the determination that the terminal device 110 will be disconnected from the access network device 120, sending the QoE context identifier to the terminal device 110. In some embodiments, the QoE context identifier is sent via a radio resource control RRC connection release message.

[0081] In some embodiments, the access network device 120 sends the QoE context identifier and QoE context information to the core network device 140 by determining that the terminal device 110 will be disconnected from the access network device 120, and based on the determination that the terminal device 110 will be disconnected from the access network device 120, sending the QoE context identifier and QoE context information to the core network device 140.

[0082] In some embodiments, the QoE context information includes a measurement collection entity MCE address to which the QoE measurement report received from the terminal device 110 will be forwarded. In some embodiments, the access network device 120 sends the QoE context identifier and the QoE context information to the core network device 140 through the following steps: the QoE context identifier and the QoE context information are sent to the core network device 140 for further storage, and the QoE context information will be retrieved by the access network device 120 or the access network device 130 later.

[0083] In some embodiments, the access network device 120 sends a QoE configuration for performing QoE measurement collection to the terminal device 110 before the terminal device is disconnected from the access network device 120 , wherein the QoE configuration is based on the QoE context information.

[0084] In some embodiments, the QoE context identifier is specific to the terminal device 110. In some embodiments, the QoE context identifier is common to multiple terminal devices including the terminal device 110. In some embodiments, the core network device 140 hosts an access and mobility management function AMF. In some embodiments, the access network device 120 receives session end information for ending QoE measurement collection from the terminal device 110, stores the session end information in the context of the terminal device 110, and sends the session end information for ending QoE measurement collection to the core network entity 160.

[0085] Figure 5 FIG. 5 is a flowchart of an example method 500 implemented at another access network device according to some embodiments of the present disclosure. For the purpose of discussion, reference will be made to Figure 1 The method 500 is described from the perspective of the access network device 130 .

[0086] At block 510, the access network device 130 determines that the terminal device 110 performing the quality of experience QoE measurement collection in the idle state is connected to the access network device 130. And based on the determination that the terminal device 110 is connected to the access network device 130, at block 520, the access network device 130 receives a QoE context identifier from the terminal device 110, the QoE context identifier identifying QoE context information for QoE measurement collection. At block 530, the access network device 130 sends a request for QoE context information associated with the QoE context identifier to the core network device 140. At block 540, the access network device 130 receives the QoE context information from the core network device 140.

[0087] In some embodiments, the QoE context information includes an MCE address to which the QoE measurement report received from the terminal device 110 will be forwarded. In some embodiments, the access network device 130 receives a report of QoE measurement collection from the terminal device 110 and sends the report to the measurement collection entity MCE based on the received QoE context information, more specifically based on the received MCE address. In some embodiments, the QoE context identifier is specific to the terminal device 110. In some embodiments, the QoE context identifier is common to multiple terminal devices including the terminal device 110. In some embodiments, the core network device 140 hosts an access and mobility management function AMF.

[0088] In some embodiments, the access network device 130 receives session end information for ending the QoE measurement collection from the terminal device, stores the session end information in the context of the terminal device, and sends the session end information to the MCE to end the QoE measurement collection. In some embodiments, the QoE context identifier is received via an RRC connection establishment complete message.

[0089] Figure 6 FIG. 6 is a flow chart showing an example method 600 implemented at a terminal device according to some embodiments of the present disclosure. For the purpose of discussion, reference will be made to Figure 1 The method 600 is described from the perspective of the terminal device 110 .

[0090] At block 610, the terminal device 110 receives a QoE configuration for performing QoE measurement collection in an idle state from the access network device 120. At block 620, the terminal device 110 receives a QoE context identifier from the access network device 120, the QoE context identifier identifying QoE context information for QoE measurement collection. At block 630, the terminal device 110 stores the QoE context identifier. At block 640, the terminal device 110 disconnects from the access network device. At block 650, the terminal device 110 connects to the access network device 130. Based on the connection to the access network device 130, at block 660, the terminal device 110 sends the QoE context identifier to the access network device 130.

[0091] In some embodiments, the terminal device 110 receives the QoE configuration based at least in part on the QoE context information identified by the QoE context identifier. In some embodiments, the terminal device 110 sends a report of the QoE measurement collection to the access network device 130 .

[0092] In some embodiments, the QoE context identifier is specific to the terminal device 110. In some embodiments, the QoE context identifier is common to multiple terminal devices including the terminal device 110. In some embodiments, the terminal device 110 sends a session end message for ending the QoE measurement collection to the access network device 130. In some embodiments, the access network device 120 and the access network device 130 are the same access network device.

[0093] In some embodiments, the QoE context identifier is received from the access network device 120 via an RRC connection release message. In some embodiments, the QoE context identifier is sent to the access network device 130 via an RRC connection setup complete message.

[0094] In some embodiments, the first device (e.g., access network device 120) capable of executing any method 400 may include a device for executing each step of method 400. The device may be implemented in any suitable form. For example, the device may be implemented in a circuit or a software module.

[0095] In some embodiments, the apparatus includes a component for determining that a terminal device will perform quality of experience (QoE) measurement collection after being disconnected from a first device; based on determining that the terminal device will perform QoE measurement collection after being disconnected, a component for sending a QoE context identifier identifying QoE context information used for the QoE measurement collection to the terminal device; and a component for sending the QoE context identifier and the QoE context information to a core network device.

[0096] In some embodiments, the component for sending a QoE context identifier to a terminal device includes: a component for determining that the terminal device is to be disconnected from the first device; and a component for sending the QoE context identifier to the terminal device based on determining that the terminal device is to be disconnected from the first device.

[0097] In some embodiments, the QoE context identifier is sent via a Radio Resource Control, RRC Connection Release, message.

[0098] In some embodiments, the component for sending the QoE context identifier and the QoE context information to the core network device includes: a component for determining that the terminal device will be disconnected from the first device; and based on determining that the terminal device will be disconnected from the first device, a component for sending the QoE context identifier and the QoE context information to the core network device.

[0099] In some embodiments, the QoE context information includes a measurement collection entity MCE address, and the QoE measurement report received from the terminal device will be forwarded to the measurement collection entity MCE address.

[0100] In some embodiments, the means for sending the QoE context identifier and the QoE context information to the core network device includes: means for sending the QoE context identifier and the QoE context information to the core network device for further storage, wherein the QoE context information will subsequently be retrieved by the first device or by another device.

[0101] In some embodiments, the apparatus comprises means for sending a QoE configuration to the terminal device for performing QoE measurement collection before the terminal device is disconnected from the first apparatus, wherein the QoE configuration is based on the QoE context information.

[0102] In some embodiments, the QoE context identifier is specific to the terminal device.

[0103] In some embodiments, the QoE context identifier is common to a plurality of terminal devices including the terminal device.

[0104] In some embodiments, the core network device hosts the access and mobility management function AMF.

[0105] In some embodiments, the first device includes a module for receiving session end information for ending QoE measurement collection from a terminal device; storing the session end information in the context of the terminal device; and sending the session end information for ending QoE measurement collection to a core network entity.

[0106] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of method 400. In some embodiments, the apparatus comprises at least one processor; and at least one memory comprising computer program code, the at least one memory and the computer program code being configured to cause the performance of the apparatus together with the at least one processor.

[0107] In some embodiments, a second device (e.g., access network device 130) capable of executing any one of the methods 500 may include components for executing the various steps of the method 500. The device may be implemented in any suitable form. For example, the device may be implemented in a circuit or a software module.

[0108] In some embodiments, the second device includes: a component for determining that a terminal device performing quality of experience (QoE) measurement collection in an idle state is connected to the second device based on determining that the terminal device is connected to the second device; a component for receiving a QoE context identifier identifying QoE context information used for the QoE measurement collection from the terminal device; a component for sending a request for QoE context information associated with the QoE context identifier to a core network device; and a component for receiving the QoE context information from the core network device.

[0109] In some embodiments, the QoE context information includes a measurement collection entity MCE address, and the QoE measurement report received from the terminal device will be forwarded to the measurement collection entity MCE address.

[0110] In some embodiments, the second apparatus comprises: means for receiving a report of said QoE measurement collection from said terminal device; and means for transmitting said report to a measurement collection entity MCE based on the received QoE context information.

[0111] In some embodiments, the QoE context identifier is specific to the terminal device.

[0112] In some embodiments, the QoE context identifier is common to a plurality of terminal devices including the terminal device.

[0113] In some embodiments, the core network device hosts the access and mobility management function AMF.

[0114] In some embodiments, the second device includes a module for receiving session end information for ending QoE measurement collection from a terminal device; storing the session end information in the context of the terminal device; and sending the session end information for ending QoE measurement collection to a core network entity.

[0115] In some embodiments, the QoE context identifier is received via a Radio Resource Control, RRC Connection Setup Complete message.

[0116] In some embodiments, the second device further comprises means for performing other steps in some embodiments of method 500. In some embodiments, the device comprises at least one processor; and at least one memory comprising computer program code, the at least one memory and the computer program code being configured to cause the performance of the device together with the at least one processor.

[0117] In some embodiments, a third device (eg, terminal device 110) capable of executing any method 600 may include components for executing the various steps of method 600. The device may be implemented in any suitable form. For example, the device may be implemented in a circuit or a software module.

[0118] In some embodiments, the third device includes: a component for receiving a quality of experience (QoE) configuration for performing QoE measurement collection in an idle state from a first access network device; a component for receiving a QoE context identifier identifying QoE context information used for the QoE measurement collection from the first access network device; a component for storing the QoE context identifier in the third device; a component for disconnecting from the first access network device; a component for connecting to a second access network device; and a component for sending the QoE context identifier to the second access network device based on being connected to the second access network device.

[0119] In some embodiments, the third apparatus includes means for receiving a QoE configuration based on the QoE context information identified by the QoE context identifier.

[0120] In some embodiments, the third apparatus comprises: a component for sending the report of the QoE measurement collection to the second access network device.

[0121] In some embodiments, the QoE context identifier is specific to the terminal device.

[0122] In some embodiments, the QoE context identifier is common to a plurality of terminal devices including the third apparatus.

[0123] In some embodiments, the third device includes: a component for sending session end information for ending the QoE measurement collection to the second access network device.

[0124] In some embodiments, the first access network device and the second access network device are the same access network device.

[0125] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of method 600. In some embodiments, the apparatus comprises at least one processor; and at least one memory comprising computer program code, the at least one memory and the computer program code being configured to cause the performance of the apparatus together with the at least one processor.

[0126] Figure 7 is a simplified block diagram of a device 700 suitable for implementing embodiments of the present disclosure. The device 700 may be provided to implement a communication device, such as Figure 1 The terminal device 110 shown, the network device 120, the network device 130, the AMF 140 or the MCE 142. As shown in the figure, the device 700 includes one or more processors 710, one or more memories 740 coupled to the processor 710, and one or more transmitters and / or receivers (TX / RX) 740 coupled to the processor 710.

[0127] The TX / RX 740 is used for bidirectional communication. The TX / RX 740 has at least one antenna to facilitate communication. The communication interface may represent any interface required to communicate with other network elements.

[0128] Processor 710 may be of any type suitable for the local technology network and may include one or more of the following: as non-limiting examples, a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Device 600 may have multiple processors, such as application specific integrated circuit chips that are time slaved to a clock that synchronizes a main processor.

[0129] The memory 720 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 724, electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disc (CD), digital video disc (DVD), and other magnetic storage devices and / or optical storage devices. Examples of volatile memories include, but are not limited to, random access memory (RAM) 722 and other volatile memories that do not persist over the duration of a power outage.

[0130] Computer program 730 includes computer executable instructions executed by associated processor 710. Program 730 may be stored in ROM 1020. Processor 710 may perform any suitable actions and processes by loading program 730 into RAM 722.

[0131] The embodiment of the present invention can be implemented with the help of program 730, so that the device 700 can execute the Figures 2 to 6Any process of the present invention discussed. The embodiments of the present disclosure may also be implemented by hardware or a combination of software and hardware.

[0132] In some embodiments, the program 730 may be tangibly embodied in a computer-readable medium, which may be included in the device 700 (such as in the memory 720) or in other storage devices accessible by the device 700. The device 700 may load the program 730 from the computer-readable medium to the RAM 722 for execution. The computer-readable medium may include any type of tangible non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. Figure 7 An example of a computer readable medium 800 in the form of a CD or DVD is shown. The computer readable medium has a program 730 stored thereon.

[0133] Generally, various embodiments of the present disclosure may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software, which may be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure are shown and described as block diagrams, flow charts, or using some other graphical representations, it should be understood that the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general hardware or controllers, or other computing devices, or some combination thereof, as non-limiting examples.

[0134] The present 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, such as instructions included in a program module executed in a device on a target real or virtual processor to perform the above referenced Figure 2-5 The method 600 is described. In general, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The functions of program modules can be combined or separated between program modules as needed in various embodiments. The machine executable instructions of program modules can be executed in local or distributed devices. In distributed devices, program modules can be located in local and remote storage media.

[0135] The program code for executing the method of the present disclosure can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing device so that the program code enables the functions / operations specified in the flow chart and / or block diagram to be implemented when the program code is executed by the processor or controller. The program code can be executed entirely on the machine, partially on the machine, as an independent software package, partially on the machine, partially on a remote machine or entirely on a remote machine or server.

[0136] In the context of the present disclosure, computer program codes or related data may be carried by any suitable carrier to enable a device, apparatus or processor to perform various processes and operations as described above. Examples of carriers include signals, computer readable media, etc.

[0137] The computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. The computer-readable medium may include, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared or semiconductor system, device or apparatus, or any suitable combination of the foregoing. More specific examples of computer-readable storage media would include an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. The term "non-transient" as used herein is a limitation on the medium itself (i.e., tangible, not a signal), not a limitation on the persistence of data storage (e.g., RAM versus ROM).

[0138] In addition, although operations are described in a particular order, this should not be understood as requiring the specific order shown or to perform these operations in sequence, or to perform all the operations shown, to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these details should not be interpreted as limitations on the scope of the present disclosure, but should be interpreted as descriptions of features peculiar to a particular embodiment. Certain features described in the context of a separate embodiment may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable sub-combination.

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

Claims

1. A first access network device, comprising: at least one processor; as well as at least one memory storing instructions, wherein when the instructions are executed by the at least one processor, the first access network device at least: Determining that the terminal device is to perform quality of experience (QoE) measurement collection after being disconnected from the first access network device; Based on determining that the terminal device is to perform QoE measurement collection after disconnection, The terminal device sends a QoE context identifier, where the QoE context identifier identifies the QoE context information used for the QoE measurement collection; as well as The QoE context identifier and the QoE context information are sent to a core network device.

2. The first access network device according to claim 1, wherein: The first access network device is configured to send the QoE context identifier to the terminal device through the following steps: Determining that the terminal device is to be disconnected from the first access network device; and Based on determining that the terminal device is to be disconnected from the first access network device, the QoE context identifier is sent to the terminal device. 3 . The first access network device according to claim 2 , wherein the QoE context identifier is sent via a radio resource control (RRC) connection release message.

4. The first access network device according to claim 2, wherein: The first access network device is configured to send the QoE context identifier and the QoE context information to the core network device through the following steps: Determining that the terminal device is to be disconnected from the first access network device; as well as Based on determining that the terminal device is to be disconnected from the first access network device, the QoE context identifier and the QoE context information are sent to the core network device.

5. The first access network device according to any one of claims 1-4, wherein the QoE context information includes a measurement collection entity MCE address, and the QoE measurement report received from the terminal device will be forwarded to the measurement collection entity MCE address.

6. The first access network device according to any one of claims 1 to 5, wherein the first access network device is configured to send the QoE context identifier and the QoE context information to a core network device by: Sending the QoE context identifier and the QoE context information to the core network device for further storage, wherein: The QoE context information will then be retrieved by the first access network device or by another access network device.

7. The first access network device according to any one of claims 1 to 6, wherein: The first access network device is further configured to: A QoE configuration for performing the QoE measurement collection is sent to the terminal device before the terminal device is disconnected from the first access network device, wherein the QoE configuration is at least partially based on the QoE context information.

8. The first access network device according to any one of claims 1-7, wherein the QoE context identifier is specific to the terminal device.

9. The first access network device according to any one of claims 1 to 7, wherein the QoE context identifier is common to a plurality of terminal devices including the terminal device.

10. The first access network device according to any one of claims 1-9, wherein the core network device carries an access and mobility management function AMF.

11. The first access network device according to any one of claims 1 to 10, wherein: The first access network device is further configured to: receiving, from the terminal device, session end information for ending the QoE measurement collection; storing session end information in the context of the terminal device; as well as A session end message for ending the QoE measurement collection is sent to a core network entity.

12. A second access network device, comprising: at least one processor; as well as at least one memory storing instructions, wherein when the instructions are executed by the at least one processor, the second access network device at least: Determine that a terminal device that performs quality of experience (QoE) measurement collection in an idle state is connected to the second access network device; Based on determining that the terminal device is connected to the second access network device, receiving a QoE context identifier from the terminal device, the QoE context identifier identifying QoE context information used for the QoE measurement collection; Sending a request for QoE context information associated with the QoE context identifier to a core network device; as well as The QoE context information is received from the core network device.

13. The second access network device according to claim 12, wherein the QoE context information includes a measurement collection entity MCE address, and the QoE measurement report received from the terminal device will be forwarded to the measurement collection entity MCE address.

14. The second access network device according to claim 12 or 13, wherein: The second access network device is further configured to: receiving a report of the QoE measurement collection from the terminal device; as well as The report is sent to the measurement collection entity MCE based on the received QoE context information.

15. The second access network device according to any one of claims 12 to 14, wherein the QoE context identifier is specific to the terminal device.

16. The second access network device according to any one of claims 12 to 14, wherein the QoE context identifier is common to a plurality of terminal devices including the terminal device.

17. The second access network device according to any one of claims 12-16, wherein the core network device carries an access and mobility management function AMF.

18. The second access network device according to any one of claims 12 to 17, wherein: The second access network device is further configured to: receiving, from the terminal device, session end information for ending the QoE measurement collection; storing the session end information in the context of the terminal device; as well as The session end information for ending the QoE measurement collection is sent to a measurement collection entity MCE.

19. The second access network device according to any one of claims 12 to 18, wherein the QoE context identifier is received via a radio resource control (RRC) connection setup complete message.

20. A terminal device, comprising: at least one processor; as well as at least one memory storing instructions that, when executed by the at least one processor, cause the terminal device to at least: receiving, from the first access network device, a quality of experience (QoE) configuration for performing QoE measurement collection in an idle state; receiving a QoE context identifier from the first access network device, wherein the QoE context identifier identifies QoE context information used for the QoE measurement collection; Storing the QoE context identifier in the terminal device; Disconnecting from the first access network device; Connecting to a second access network device; as well as Based on the connection to the second access network device, the QoE context identifier is sent to the second access network device.

21. The terminal device according to claim 20, wherein: The terminal device is also configured to: A QoE configuration is received based at least in part on the QoE context information identified by the QoE context identifier.

22. The terminal device according to claim 20 or 21, wherein: The terminal device is also configured to: Send the QoE measurement collection report to the second access network device.

23. The terminal device according to any one of claims 20 to 22, wherein: The QoE context identifier is specific to the terminal device.

24. The terminal device according to any one of claims 20 to 22, wherein: The QoE context identifier is common to a plurality of terminal devices including the terminal device.

25. The terminal device according to any one of claims 20 to 24, wherein the terminal device is further configured to: Sending session end information for ending the QoE measurement collection to the second access network device.

26. The terminal device according to any one of claims 20 to 25, wherein: The first access network device and the second access network device are the same access network device.

27. The terminal device according to any one of claims 20-26, wherein the QoE context identifier is received from the first access network device via a radio resource control (RRC) connection release message.

28. The terminal device according to any one of claims 20-27, wherein the QoE context identifier is sent to the second access network device via an RRC connection establishment complete message.

29. A method comprising: Determining at the first access network device that the terminal device is to perform quality of experience (QoE) measurement collection after being disconnected from the first access network device; Based on determining that the terminal device is to perform QoE measurement collection after disconnection, Sending a QoE context identifier identifying the QoE context information collected for the QoE measurement to the terminal device; as well as The QoE context identifier and the QoE context information are sent to a core network device.

30. A method comprising: Determining, at the second access network device, that a terminal device that performs quality of experience (QoE) measurement collection in an idle state is connected to the second access network device; Based on determining that the terminal device is connected to the second access network device, receiving from the terminal device a QoE context identifier identifying QoE context information used for the QoE measurement collection; Sending a request for QoE context information associated with the QoE context identifier to a core network device; as well as The QoE context information is received from the core network device.

31. A method comprising: Receiving, at the terminal device, from the first access network device, a quality of experience (QoE) configuration for performing QoE measurement collection in an idle state; receiving, from the first access network device, a QoE context identifier identifying QoE context information used for the QoE measurement collection; Storing the QoE context identifier in the terminal device; Disconnecting from the first access network device; Connecting to a second access network device; as well as Based on the connection to the second access network device, the QoE context identifier is sent to the second access network device.

32. A first device, comprising: means for determining that the terminal device is to perform quality of experience (QoE) measurement collection after being disconnected from the first apparatus; Based on determining that the terminal device is to perform QoE measurement collection after disconnection, a component for sending a QoE context identifier identifying QoE context information for the QoE measurement collection to the terminal device; as well as A component configured to send the QoE context identifier and the QoE context information to a core network device.

33. A second device, comprising: means for determining that a terminal device performing quality of experience QoE measurement collection in an idle state is connected to the second device; means for receiving, based on determining that the terminal device is connected to the apparatus, a QoE context identifier identifying QoE context information for the QoE measurement collection from the terminal device; means for sending a request for QoE context information associated with the QoE context identifier to a core network device; as well as A component for receiving the QoE context information from the core network device.

34. A third device, comprising: A component for receiving, from a first access network device, a quality of experience (QoE) configuration for performing QoE measurement collection in an idle state; A component for receiving, from the first access network device, a QoE context identifier identifying QoE context information used for the QoE measurement collection; means for storing the QoE context identifier in the terminal device; means for disconnecting from the first access network device; A component for connecting to a second access network device; as well as A means for sending the QoE context identifier to the second access network device based on the connection to the second access network device.

35. A non-transitory computer readable medium comprising program instructions which, when executed by an apparatus, cause the apparatus to at least perform the method of claim 29, 30 or 31.

Images