QOE for RRC idle mode

Abstract

An embodiment of the present disclosure relates to handling a QoE session that remains in RRC-IDLE mode. An access network device determines that a terminal device will perform quality of experience (QoE) measurement collection after disconnection from a first access network device, and based on the terminal device's determination to perform QoE measurement collection after disconnection, transmits a QoE context identifier to the terminal device that identifies QoE context information to be used for QoE measurement collection, and transmits the QoE context identifier and the QoE context information to a core network device. As provided in the present disclosure, the stored QoE report can be transmitted to a new serving gNB and then transmitted to an MCE.

Description

[Technical Field]

[0001] Various exemplary embodiments relate to the field of telecommunications, and in particular 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 technology]

[0002] The QoE Measurement Collection (QME) feature enables the collection of QoE measurements (delay, jitter, etc.) generated by the application layer in the user equipment (UE). This feature was specified in 3G, LTE, and is being introduced in New Radio (NR) in Rel-17. In Rel-17, for NR, QoE measurement collection in RRC_CONNECTED mode involves three services, but in Rel-18, the UE may need to collect and store QoE measurements in RRC_IDLE mode. Summary of the Invention

[0003] Generally, the exemplary 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 comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first access network device to at least: determine that a terminal device will perform quality of experience (QoE) measurement collection after disconnection from the first access network device; transmit, to the terminal device, a QoE context identifier that identifies QoE context information to be used for QoE measurement collection based on the terminal device's determination to perform QoE measurement collection after disconnection; and transmit 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 comprising at least one processor and at least one memory that stores instructions that, when executed by the at least one processor, cause the first access network device to at least: determine that a terminal device performing quality of experience (QoE) measurement collection in an idle state will connect to the second access network device; receive, based on the determination that the terminal device will connect to the second access network device, from the terminal device a QoE context identifier that identifies QoE context information to be used for the QoE measurement collection; send, to a core network device, a request for QoE context information associated with the QoE context identifier; and receive the QoE context information from the core network device.

[0006] In a third aspect, a terminal device is provided, the terminal device comprising: at least one processor; and at least one memory that stores instructions that, when executed by the at least one processor, cause the terminal device to at least receive, from a first access network device, a Quality of Experience (QoE) configuration for performing QoE measurement collection in an idle state, receive, from the first access network device, a QoE context identifier that identifies QoE context information to be used for the QoE measurement collection, store the QoE context identifier in the terminal device, disconnect from the first access network device and 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.

[0007] In a fourth aspect, there is provided a method implemented in a first access network device, the method including: determining, by a terminal device, to perform Quality of Experience (QoE) measurement collection after disconnection from the first access network device; based on the terminal device's determination to perform QoE measurement collection after disconnection, transmitting a QoE context identifier to the terminal device, the QoE context identifier identifying QoE context information to be used for QoE measurement collection; and transmitting the QoE context identifier and the QoE context information to a core network device.

[0008] In a fifth aspect, there is provided a method implemented in a second access network device, the method including: determining that a terminal device performing quality of experience (QoE) measurement collection in an idle state will connect to the second access network device; based on the determination that the terminal device will connect to the second access network device, receiving, from the terminal device, a QoE context identifier that identifies QoE context information to be used for the QoE measurement collection; sending, to a core network device, a request for QoE context information associated with the QoE context identifier; and receiving the QoE context information from the core network device.

[0009] In a sixth aspect, there is provided a method implemented in a terminal device, the method including receiving, from a 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 that identifies QoE context information to be 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, 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 device is provided, the first device comprising: means for determining that a terminal device performs quality of experience (QoE) measurement collection after disconnection from the first device; means for transmitting a QoE context identifier to the terminal device, the QoE context identifier identifying QoE context information to be used for the QoE measurement collection, based on the terminal device's determination to perform QoE measurement collection after disconnection; and means for transmitting 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 comprising: means for determining that a terminal device performing quality of experience (QoE) measurement collection in an idle state will connect to the second device; means for receiving, based on the determination that the terminal device will connect to the second device, a QoE context identifier from the terminal device, the QoE context identifier identifying QoE context information to be used for the QoE measurement collection; means for transmitting, to a core network device, a request for QoE context information associated with the QoE context identifier; and means for receiving the QoE context information from the core network device.

[0012] In a ninth aspect, a third apparatus is provided, the third apparatus comprising: means for receiving, from a first access network device, a quality of experience (QoE) setting for performing QoE measurement collection in an idle state, means for receiving, from the first access network device, a QoE context identifier that identifies QoE context information to be used for the QoE measurement collection, means for storing the QoE context identifier in the third apparatus, means for disconnecting from the first access network device, means for connecting to the first access network device, and means 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, there is provided a computer program comprising instructions that, when executed by a first device, cause the first device to at least determine that a terminal device will perform quality of experience (QoE) measurement collection after disconnection from the first device; based on the terminal device's determination to perform QoE measurement collection after disconnection, send a QoE context identifier to the terminal device, identifying QoE context information to be used for QoE measurement collection; and send the QoE context identifier and the QoE context information to a core network device.

[0014] In an eleventh aspect, there is provided a computer program including instructions that, when executed by a second device, cause the second device to at least determine that a terminal device performing quality of experience (QoE) measurement collection in an idle state will connect to the second device; based on the determination that the terminal device will connect to the second device, receive from the terminal device a QoE context identifier that identifies QoE context information to be used for QoE measurement collection; send to a core network device a request for QoE context information associated with the QoE context identifier; and receive the QoE context information from the core network equipment.

[0015] In a twelfth aspect, there is provided a computer program comprising instructions that, when executed by a third device, cause the third device to at least receive, from a first access network device, a Quality of Experience (QoE) setting for performing QoE measurement measurement collection in an idle state; receive, from the first access network device, a QoE context identifier that identifies QoE context information to be used for the QoE measurement 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, based on the connection to the second access network device, send the QoE context identifier to the second access network device.

[0016] In a thirteenth aspect, there is provided a first access network device comprising: a determination circuit configured to determine that a terminal device will perform quality of experience (QoE) measurement collection after disconnection from a first access network device; a transmission circuit configured to transmit to the terminal device a QoE context identifier that identifies QoE context information to be used for QoE measurement collection based on the terminal device's determination to perform QoE measurement collection after disconnection; and a transmission circuit configured to transmit the QoE context identifier and the QoE context information to a core network device.

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

[0018] In a fifteenth aspect, a terminal device is provided that includes a receiving circuit configured to receive, from a first access network device, a quality of experience (QoE) setting for performing QoE measurement value collection in an idle state; a receiving circuit configured to receive, from the first access network device, a QoE context identifier that identifies QoE context information to be used for QoE measurement value 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 a transmission circuit configured to transmit the QoE context identifier to the second access network device based on the connection to the second access network device.

[0019] In a sixteenth aspect, there is provided a non-transitory computer readable medium comprising program instructions for causing an apparatus to carry out at least 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 key features 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 apparent through the following description. [Brief explanation of the drawings]

[0021] Exemplary embodiments will now be described with reference to the accompanying drawings. [Figure 1] FIG. 1 illustrates an exemplary communication network in which embodiments of the present disclosure may be implemented. [Figure 2] FIG. 2 is a flowchart illustrating an example process for QoE in some embodiments of the present disclosure. [Figure 3] FIG. 3 is a flowchart illustrating another example of a process for QoE in some embodiments of the present disclosure. [Figure 4]FIG. 4 illustrates a flowchart of a method implemented in a first access network device according to some embodiments of the present disclosure. [Figure 5] FIG. 5 shows a flowchart of a method implemented in a second access network device according to some other embodiments of the present disclosure. [Figure 6] FIG. 6 shows a flowchart of a method implemented in a terminal device according to some other embodiments of the present disclosure. [Figure 7] FIG. 7 is a simplified block diagram of an apparatus suitable for practicing embodiments of the present disclosure. [Figure 8] 8 shows a block diagram of an exemplary computer-readable medium according to some embodiments of the present disclosure. Throughout the drawings, the same or similar reference numerals represent the same or similar elements. DETAILED DESCRIPTION OF THE INVENTION

[0022] The principles of the present disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are provided for illustrative purposes to help those skilled in the art understand and practice the present disclosure, and are not intended to imply any limitations on the scope of the present disclosure. The disclosure described herein may be implemented in various forms other than those described below.

[0023] 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 belongs.

[0024] References in this disclosure to "one embodiment," "embodiment," "exemplary embodiment," etc. indicate that the described embodiment may include a particular feature, structure, or characteristic, but not all embodiments need include the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is understood that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly stated.

[0025] Although terms such as "first" and "second" may be used herein to describe various elements, it should be understood that these elements are not limited by these terms. These terms are merely used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of the exemplary embodiments. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0026] The terminology in the examples is for the purpose of describing particular embodiments and is not intended to limit the exemplary embodiments. As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms unless the context clearly dictates otherwise. It will be further understood that, as used herein, the terms "comprises," "comprising," "has," "having," "includes," and / or "including" identify the presence of stated features, elements, and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof. As used herein, "at least one of: " and "at least one of " and similar expressions in which a list of two or more elements is joined by "and" or "or" mean at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0027] As used herein, the term "circuit" means (a) hardware-only circuit implementations (e.g., analog and / or digital-only implementations); (b) a combination of hardware circuitry and software (if applicable); (i) a combination of analog and / or digital hardware circuitry and software / firmware; (ii) software (including digital signal processors), software, and hardware processor portions with memory that work together to cause a device, such as a mobile phone or server, to perform various functions; (c) A hardware circuit or processor, such as a microprocessor or part of a microprocessor, that requires software (e.g., firmware) to operate, but the software may be absent when not required for operation; It may refer to one or more or all of the following:

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

[0029] As used herein, the term "communication network" refers to a network conforming to any suitable communication standard, such as New Radio (NR), Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), or Narrowband Internet of Things (NB-IoT). Furthermore, communication between terminal devices and network devices in the communication network may be based on first-generation (1G), second-generation (2G), 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, future fifth-generation (5G) communication protocols, and / or other protocols currently known or developed in the future. Embodiments of the present disclosure may be applied to various communication systems. Given the rapid development of communications, there will, of course, be future communication technologies and systems in which the present disclosure may be embodied. The scope of the present disclosure should not be considered limited to only the aforementioned systems.

[0030] As used herein, the terms "network equipment" and "access network equipment" refer to nodes of a communication network through which terminal equipment accesses the network and receives services therefrom. Depending on the terminology and technology applied, network equipment may refer to a base station (BS) or access point (AP), e.g., a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), an NR NB (also referred to as gNB), a remote radio unit (RRU), a radio header (RH), a remote radio head (RRH), a relay, a low-power node such as a femto, or a pico, etc.

[0031] The term "terminal equipment" refers to any terminal equipment capable of wireless communication. By way of example and not limitation, a terminal equipment may also be referred to as a communication device, a user equipment (UE), a subscriber station (SS), a mobile subscriber station, a mobile station (MS), or an access terminal (AT). Terminal equipment includes, but is not limited to, mobile phones, cellular phones, smartphones, voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal equipment, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal equipment such as digital cameras, gaming terminal equipment, music storage and playback equipment, in-vehicle wireless terminal equipment, wireless endpoints, mobile stations, laptop embedded equipment (LEE), laptop mounted equipment (LME), USB dongles, smart devices, wireless customer premises equipment (CPE), Internet of Things (IoT) devices, wearables such as watches, head-mounted displays (HMD), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronics devices, devices operating in commercial and / or industrial wireless networks, etc. In the following description, the terms "terminal equipment," "communications equipment," "terminal," "user equipment," and "UE" may be used interchangeably.

[0032] As mentioned above, the QMC functionality allows the collection of QoE measurements (delay, jitter, etc.) generated at the application layer of the terminal device and collected via the control plane of the radio interface (i.e., via the RRC layer). The QoE functionality was specified in 3G and LTE and will be introduced to NR in Rel-17. A specific signaling radio bearer (SRB), such as SRB4, is used to transmit QoE measurements to the network. In Rel-17, three services were relevant for QoE measurement collection in NR: Dynamic Adaptive Streaming over HTTP (DASH), Multimedia Telephony Services in IMS (MTSI), and Virtual Reality (VR). However, in Rel-18, the Multicast Broadcast Service (MBS) service will also be part of the collection. This new service allows terminal devices to collect and store QoE measurements in RRC_IDLE and RRC_INACTIVE modes.

[0033] MBS is a new 5G feature defined in Rel-17. It is designed to enable resource-efficient transmission to multiple end users who require the same content. Furthermore, because broadcasting only spreads information on the downlink (DL), it can be used in RRC idle mode (where all terminal devices within the broadcast service area are authorized to receive data). 5G-MBS was introduced to 3GPP in Rel-17. Further standardization is planned to support new Rel-18 goals for certain aspects of the radio access network (RAN) and core network (CN). Based on the work in Rel-17, broadcast services can be received in all RRC states, while multicast can only be received in the RRC connected state. However, Rel-18 aims to enable terminal devices to receive multicast even in the RRC inactive state. The main difference between broadcast and multicast is that terminal devices join a multicast session via non-access stratum (NAS) signaling, while the network is unaware of terminal devices receiving broadcast services.

[0034] In Rel-17, in RRC connected or inactive QMC mechanism, besides the container AppLayerMeasConfig sent to the terminal equipment application layer, there are some additional QMC context parameters used by network equipment such as access network equipment, such as MCEaddress (address of the Measurement Collection Entity (MCE)), QoE Reference Identity (ID) (ID assigned to the QoE collection job), and Areascope (area where QoE measurements are collected). The terminal equipment is not aware of these parameters (Note: QoE Reference ID and area information may be included in the AppLayerMeasConfig container).

[0035] When a terminal device returns from idle mode to an RRC connection, the new connection setup results in no QMC context for the terminal device in the new or previous serving network equipment. Without these QMC contexts, the network equipment cannot forward the QoE measurement data collected by the terminal device to the corresponding MCE, cannot manage the continuity of the terminal device's QoE measurements, and has no knowledge of the configured RAN visible reporting. For example, the network equipment is supposed to forward the QoE measurements collected by the terminal device to the MCE, but does not know the MCE address (where to forward the data).

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

[0037] FIG. 1 illustrates a schematic diagram of an exemplary communication network 100 in which some embodiments of the present disclosure may be implemented. As illustrated in FIG. 1, 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) for serving one or more terminal devices. The network device 130 may also provide a group of cells (for convenience, only one cell 131 is shown) for serving 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 be served by the network device 120. In some embodiments, the terminal device 110 may be located in the cell 131 and be served by the network device 130.

[0038] The communication network 100 may further comprise core network equipment 140, e.g., core network equipment hosting an Access and Mobility Management Function (AMF). The communication network 100 may further comprise a Measurement Collection Entity (MCE) 160 and an Operation, Administration and Maintenance (OAM) 150. It should be noted that the AMF 140, MCE 160, and OAM 150 are merely exemplary and any other suitable configurations are possible.

[0039] In some embodiments, terminal device 110 can perform signaling-based QoE measurements, where OAM 150 can initiate activation of QoE measurements for a particular terminal device via the CN, and a network device (e.g., network device 120) can receive one or more QoE measurement configurations.

[0040] In some embodiments, network device 120 may detect that terminal device 110 may transition to idle mode. Network device 120 may then transmit a QoE context identifier to the AS of terminal device 110 for storage. Then, when terminal device 110 returns to RRC connected mode, terminal device 110 communicates the QoE context identifier to a current serving network device, such as network device 130 or network device 120. Network device 130 may use the QoE context identifier to fetch QMC context information from AMF 140. In some embodiments, terminal device 110 and network device 120 may communicate via a direct SRB between terminal device 110 and network device 120. In some embodiments, terminal device 110 and network device 130 may communicate via a direct SRB between terminal device 110 and network device 130.

[0041] It should be noted that the number of network equipment and terminal equipment is for illustrative purposes, without implying any limitation. System 100 may include any suitable number of network equipment and terminal equipment adapted to implement embodiments of the present disclosure. Although not shown, it will be understood that one or more terminal equipment may be located in cell 101 or 102.

[0042] Communications in communication system 100 may be conducted according to any suitable communication protocol(s), including, but not limited to, cellular communication protocols such as first generation (1G), second generation (2G), third generation (3G), fourth generation (4G), and fifth generation (5G), wireless local network communication protocols such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, and / or other protocols now known or developed in the future. Further, communications may utilize any suitable 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 multiple access (OFDM), discrete Fourier transform spread OFDM (DFT-s-OFDM), and / or other technologies now known or developed in the future.

[0043] Reference is now made to FIG. 2 , which illustrates a process 200 for QoE measurement in RRC idle mode, in accordance with some embodiments of the present disclosure. For illustrative purposes, process 200 will be described with reference to FIG. 1 . Process 200 may include terminal device 110, network device 120 operating as a first access network device, network device 130 operating as a second access network device, and AMF 140, as shown in FIG. 1 . While process 200 has been described in the context of communication system 100 of FIG. 1 , it will be appreciated that this process may be similarly applied to other communication scenarios in which different network devices are co-deployed to provide respective serving cells. Also, while QoE for terminal device 110 has been described, it will be appreciated that a similar process may also be applied to other terminal devices.

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

[0045] As shown in process 200, the first access network device 120 may transmit the QoE context identifier 206 and the QoE context information 212 to the AMF 140 (230). Upon receiving the QoE context identifier 206 and the QoE context information 212 (235), the AMF 140 stores the QoE context identifier 206 and the associated QoE context information 212 (240). 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 the QoE context identifier 206 to the terminal device 110 (220). Upon receiving the QoE context identifier 206 (225), the terminal device 110 stores the QoE context identifier (245). The terminal device 110 may then disconnect from the first access network device 120 (250).

[0046] When the terminal device 110 returns to connected mode, the terminal device 110 may connect (255) to the second access network device 130 and send (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 including the QoE context identifier 206 to the AMF 140 for QoE context information 212. The QoE context identifier 206 is used by the first access network device 120 and the AMF to identify the associated 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 AMF 140, obtain the MCE address in the QoE context information 212, and forward to the AMF 140 the QoE reports received from the terminal device 110 and performed while in idle mode.

[0047] Reference is now made to FIG. 3 , which illustrates a detailed process 300 for QoE measurement in RRC idle mode, in accordance with some embodiments of the present disclosure. For illustrative purposes, process 300 will be described with reference to FIG. 1 . Process 300 may include terminal device 110, network device 120, network device 130, AMF 140, MCE 160, and OAM 150, as shown in FIG. 1 . While process 300 has been described in the context of communication system 100 of FIG. 1 , it will be appreciated that this process may be similarly applied to other communication scenarios in which different network devices are co-deployed to provide respective serving cells. Also, while the QoE of terminal device 110 has been described, it will be appreciated that a similar process may be applied to other terminal devices.

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

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

[0050] When the terminal device 110 enters idle mode, the terminal device 110 may have QoE measurement configurations that are not deleted in idle mode, for example, the QoE measurements may be for MBS.

[0051] In some embodiments, to maintain the QoE context information, the network device 120 may determine that the terminal device 110 performs QoE measurement collection after disconnection from the network device 120. Then, 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 to be used for the QoE measurement collection. The access network device 120 may then send the QoE context identifier and the QoE context information to the AMF 140.

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

[0053] In some embodiments, after network device 120 determines that terminal device 110 disconnects from network device 120 , the QoE context identifier and the QoE context information are sent to AMF 140 .

[0054] 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 include a QoE Reference ID and an AreaScope.

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

[0056] In some embodiments, the network device 120 transmits the QoE context identifier to the terminal device 110 after the terminal device 110 decides to disconnect from the network device 120. Alternatively, the QoE context identifier is transmitted at an earlier point in time to ensure greater robustness in case the wireless connection fails.

[0057] In some embodiments, the QoE context identifier may be a QoE Reference ID or an ID that can be mapped to a QoE Reference ID. Alternatively, there may be a container that contains the entire relevant configuration (including QMC context information). In this scenario, the network device 120 may send the container to the terminal device 110, which 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 QoE context information to the AMF 140. In some embodiments, the QoE context identifier may be terminal device specific. Alternatively, multiple terminal devices may share the same QoE configuration and therefore the same QoE context identifier.

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

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

[0060] The AMF 140 may send (342) the QMC context configuration 343 to the network device 130. The network device 130 may send (345) an RRC configuration 346 of the SRB4 of the terminal device 110 to transmit the stored QoE report. The terminal device 110 may send (348) the QoE report 334 stored while in idle mode to the network device 130. Based on the QMC context information received from the AMF 140, the network device 130 may forward (351) the QoE report 334 to the MCE 160 by the MCEAddress that is part of the QoE context information received from the AMF 140.

[0061] 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 it may continue to use the old QMC configuration. Alternatively, the network device 130 may instruct the terminal device 110 to stop the QMC configuration. Alternatively, the network device 130 may reuse the RAN visible (RV)-QoE configuration that was used before the terminal device 110 went into idle mode.

[0062] In some scenarios, the application layer of the terminal device 110 may detect that the logging period has ended or other stopping criteria have been met (354). The application layer of the terminal device 110 may then send a QMC session end notification 356 to the AS layer of the terminal device 110 (355). The AS layer of the terminal device 110 may then send the QMC session end notification 356 to the network device 130 (358). The network 130 stores the session end information in the terminal device context (361). The network device 130 sends the QMC session end notification 356 to the MCE 160 (362). The terminal device 110 then transitions to RRC idle mode.

[0063] The network device 120 sends (365) a terminal device context release request 366 to the AMF 140. The AMF 140 then sends (368) a terminal device context release command 369 to the network device 120. The network device 120 then sends (371) a notification of a terminal device context release complete message 372 to the AMF 140. This notification is related to the QoE session being terminated by the terminal device 110. The AMF 140 then releases (374) the QMC context.

[0064] 4 illustrates a flowchart of an exemplary method 400 implemented in an access network device in accordance with some embodiments of the present disclosure. For illustrative purposes, the method 400 will be described from the perspective of the access network device 120 with reference to FIG.

[0065] In block 410, access network equipment 120 determines that terminal equipment 110 will perform quality of experience (QoE) measurement collection after disconnection from access network equipment 120. In block 420, based on terminal equipment 110 determining that QoE measurement collection will be performed after disconnection, access network equipment 120 transmits, to terminal equipment 110, a QoE context identifier that identifies QoE context information to be used for QoE measurement collection. Then, in block 430, access network equipment 120 transmits the QoE context identifier and the QoE context information to core network equipment 140.

[0066] In some embodiments, access network device 120 transmits the QoE context identifier to terminal device 110 upon terminal device 110 deciding to disconnect from access network device 120, and transmits the QoE context identifier to terminal device 110 based on terminal device 110 deciding to disconnect from access network device 120. In some embodiments, the QoE context identifier is transmitted via a radio resource control (RRC) disconnect message.

[0067] In some embodiments, the access network equipment 120 transmits the QoE context identifier and the QoE context information to the core network equipment 140 in response to the terminal equipment 110 deciding to disconnect from the access network equipment 120, and transmits the QoE context identifier and the QoE context information to the core network equipment 140 based on the terminal equipment 110 deciding to disconnect from the access network equipment 120.

[0068] In some embodiments, the QoE context information sets the address of a Measurement Collection Entity (MCE) to which QoE measurement reports received from terminal device 110 should be forwarded. In some embodiments, access network equipment 120 transmits the QoE context identifier and the QoE context information to core network equipment 140 for further storage, and the QoE context information is subsequently retrieved by access network equipment 120 or by access network equipment 130.

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

[0070] In some embodiments, the QoE context identifier is specific to terminal device 110. In some embodiments, the QoE context identifier is common to multiple terminal devices, including terminal device 110. In some embodiments, core network device 140 hosts an Access and Mobility Management Function (AMF). In some embodiments, access network device 120 receives session termination information for terminating QoE measurement collection from terminal device 110, stores the session termination information in a context of terminal device 110, and transmits the session termination information for terminating QoE measurement collection to core network entity 160.

[0071] 5 illustrates a flowchart of an example method 500 implemented in another access network device in accordance with some embodiments of the present disclosure. For illustrative purposes, the method 500 will be described from the perspective of the access network device 130 with reference to FIG.

[0072] At block 510, access network device 130 determines that terminal device 110 performing quality of experience (QoE) measurement collection in an idle state connects to access network device 130. Then, at block 520, based on determining that terminal device 110 connects to access network device 130, access network device 130 receives, from terminal device 110, a QoE context identifier that identifies QoE context information to be used for QoE measurement collection. At block 530, access network device 130 transmits, to core network device 140, a request for QoE context information associated with the QoE context identifier. Then, at block 540, access network device 130 receives the QoE context information from core network device 140.

[0073] In some embodiments, the QoE context information includes an MCE address to which the QoE measurement report received from the terminal device 110 should be forwarded. In some embodiments, the access network device 130 receives the QoE measurement collection report from the terminal device 110 and transmits the report to the MCE, a measurement collection entity, 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).

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

[0075] 6 shows a flowchart of an example method 600 implemented in a terminal device in some embodiments of the present disclosure. For purposes of explanation, the method 600 will be described from the perspective of the terminal device 110 with reference to FIG.

[0076] In block 610, the terminal device 110 receives from the access network equipment 120 a QoE configuration for performing QoE measurement collection in idle state. In block 620, the terminal device 110 receives from the access network equipment 120 a QoE context identifier that identifies QoE context information to be used for QoE measurement collection. In block 630, the terminal device 110 stores the QoE context identifier. In block 640, the terminal device 110 disconnects from the access network equipment. In block 650, the terminal device 110 connects to the access network equipment 130. In block 660, upon connecting to the access network equipment 130, the terminal device 110 transmits the QoE context identifier to the access network equipment 130.

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

[0078] In some embodiments, the QoE context identifier is specific to terminal device 110. In some embodiments, the QoE context identifier is common to multiple terminal devices, including terminal device 110. In some embodiments, terminal device 110 sends session termination information to access network device 130 to terminate QoE measurement collection. In some embodiments, access network device 120 and access network device 130 are the same access network device.

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

[0080] In some embodiments, a first device capable of performing any of the methods 400 (access network equipment 120 in the exemplary embodiment) may comprise means for performing each step of the method 400. The means may be implemented in any suitable form. For example, the means may be implemented in a circuit or a software module.

[0081] In some embodiments, the apparatus comprises means for determining that a terminal device will perform quality of experience (QoE) measurement collection after disconnection from the first device; means for transmitting a QoE context identifier to the terminal device, based on the terminal device's determination to perform QoE measurement collection after disconnection, the QoE context identifier identifying QoE context information to be used for QoE measurement collection; and means for transmitting the QoE context identifier and the QoE context information to a core network device.

[0082] In some embodiments, the means for transmitting the QoE context identifier to the terminal device comprises means for determining that the terminal device will disconnect from the first device, and means for transmitting the QoE context identifier to the terminal device based on the terminal device determining to disconnect from the first device.

[0083] In some embodiments, the QoE context identifier is transmitted via a Radio Resource Control (RRC) connection release message.

[0084] In some embodiments, the means for transmitting the QoE context identifier and the QoE context information to the core network equipment comprises: means for determining that the terminal equipment will disconnect from the first device; and means for transmitting the QoE context identifier and the QoE context information to the core network equipment based on the terminal equipment determining to disconnect from the first device.

[0085] In some embodiments, the QoE context information includes the address of a Measurement Collection Entity (MCE) to which QoE measurement reports received from the terminal device should be forwarded.

[0086] In some embodiments, the means for transmitting the QoE context identifier and the QoE context information to the core network equipment comprises means for transmitting the QoE context identifier and the QoE context information to the core network equipment for further storage, where the QoE context information is later retrieved by the first device or another device.

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

[0088] In some embodiments, the QoE context identifier is unique to the terminal device.

[0089] In some embodiments, the QoE context identifier is common to multiple terminal devices, including the terminal device.

[0090] In some embodiments, the core network equipment hosts an Access Mobility Management Function (AMF).

[0091] In some embodiments, the first device comprises means for receiving session termination information for terminating QoE measurement value collection from a terminal device, means for storing the session termination information in a context of the terminal device, and means for transmitting the session termination information for terminating QoE measurement value collection to a core network entity.

[0092] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of method 400. In some embodiments, the means comprises at least one processor and at least one memory containing computer program code, the at least one memory and the computer program code configured to cause the apparatus to be executed by the at least one processor.

[0093] In some embodiments, a second device (e.g., access network equipment 130) capable of performing any of the methods 500 may comprise means for performing each step of the method 500. The means may be implemented in any suitable form. For example, the means may be implemented in a circuit or a software module.

[0094] In some embodiments, the second device comprises means for determining that a terminal device performing quality of experience (QoE) measurement collection in an idle state will connect to the second device; means for receiving, based on the determination that the terminal device will connect to the second device, a QoE context identifier from the terminal device, the QoE context identifier identifying QoE context information to be used for QoE measurement collection; means for sending, to a core network device, a request for QoE context information associated with the QoE context identifier; and means for receiving the QoE context information from the core network device.

[0095] In some embodiments, the QoE context information includes an address of a Measurement Collection Entity (MCE) to which the QoE measurement report received from the terminal device should be forwarded.

[0096] In some embodiments, the second device comprises means for receiving a report of QoE measurement collection from the terminal equipment, and means for sending the report to the measurement collection entity MCE based on the received QoE context information.

[0097] In some embodiments, the QoE context identifier is unique to the terminal device.

[0098] In some embodiments, the QoE context identifier is common to multiple terminal devices, including the terminal device.

[0099] In one embodiment, the core network device hosts an Access Mobility Management Function (AMF).

[0100] In some embodiments, the second device comprises means for receiving session termination information for terminating QoE measurement value collection from a terminal device, means for storing the session termination information in a context of the terminal device, and means for transmitting the session termination information for terminating QoE measurement value collection to a core network entity.

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

[0102] In some embodiments, the second device further comprises means for performing other steps in some embodiments of method 500. In some embodiments, the means comprises at least one processor and at least one memory containing computer program code, the at least one memory and the computer program code configured by the at least one processor to cause the device to execute.

[0103] In some embodiments, a third device (e.g., terminal device 110) capable of performing any of method 600 may comprise means for performing each step of method 600. The means may be implemented in any suitable form. For example, the means may be implemented in a circuit or a software module.

[0104] In some embodiments, the third device comprises means for receiving, from the first access network equipment, a quality of experience (QoE) setting for performing QoE measurement collection in an idle state; means for receiving, from the first access network equipment, a QoE context identifier that identifies QoE context information to be used for QoE measurement collection; means for storing the QoE context identifier in the third device; means for disconnecting from the first access network equipment; means for connecting to a second access network equipment; and means for transmitting the QoE context identifier to the second access network equipment based on the connection to the second access network equipment.

[0105] In some embodiments, the third device comprises means for receiving a QoE setting based on the QoE context information identified by the QoE context identifier.

[0106] In an embodiment, the third device comprises means for sending a report of the QoE measurements collection to the second access network device.

[0107] In some embodiments, the QoE context identifier is unique to the terminal device.

[0108] In some embodiments, the QoE context identifier is common to multiple terminal devices, including the third device.

[0109] In some embodiments, the third device comprises means for sending session termination information to the second access network device to terminate the QoE measurement collection.

[0110] In one embodiment, the first access network device and the second access network device are the same access network device.

[0111] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of method 600. In some embodiments, the means comprises at least one processor and at least one memory containing computer program code, the at least one memory and the computer program code configured by the at least one processor to cause the apparatus to execute.

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

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

[0114] The processor 710 may be of any type suitable for a local technology network and may include, by way of non-limiting example, one or more of 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. The device 700 may have multiple processors, such as application-specific integrated circuit chips that are time-slaved to a clock that synchronizes a main processor.

[0115] The memory 720 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memory include, but are not limited to, read-only memory (ROM) 724, electronically programmable read-only memory (EPROM), flash memory, hard disks, compact disks (CDs), digital video disks (DVDs), and other magnetic and / or optical storage devices. Examples of volatile memory include, but are not limited to, random access memory (RAM) 722 and other volatile memories that do not persist through power-down periods.

[0116] The computer program 730 includes computer-executable instructions that are executed by the associated processor 710. The program 730 may be stored in the ROM 724. The processor 710 can load the program 730 into the RAM 722 to perform any suitable operations and processes.

[0117] 2 to 6, the device 700 may be implemented by a program 730 such that the device 700 can execute any process of the present disclosure. The embodiment of the present disclosure may also be implemented by hardware or a combination of software and hardware.

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

[0119] In general, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described using block diagrams, flowcharts, or 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, special purpose circuits or logic, general purpose hardware or a controller or other computing device, or some combination thereof, in non-limiting examples.

[0120] 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 those included in program modules, that execute on a target real or virtual processor to perform the method 600 described above with reference to FIGS. 2-5. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split among program modules as desired in various embodiments. The machine-executable instructions of the program modules may be executed in local or distributed devices. In distributed devices, the program modules may be located in both local and remote storage media.

[0121] Program code for implementing the methods 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 apparatus, and when executed by the processor or controller, cause the specific functions / operations in the flowcharts and / or block diagrams to be performed. The program code can run entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

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

[0123] The computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. Computer-readable media 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 computer-readable storage media include an electrical connection having one or more wires, a portable computer diskette, 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 disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. The term "non-transitory" as used herein refers to the medium itself (i.e., tangible, not a signal) as opposed to the permanent limitation of data storage (e.g., RAM vs. ROM).

[0124] Furthermore, although operations are depicted in a particular order, this should not be understood as requiring such operations to be performed in the particular order shown, or sequentially, or to perform all of the illustrated operations, to achieve desirable results. In certain situations, multitasking and parallel processing may be preferred. Similarly, while several specific implementation details are included in the above description, these should not be construed as limiting the scope of the disclosure, but rather as descriptions of features that may be unique to particular embodiments. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.

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

Claims

1. a first access network device, at least one processor; When executed by the at least one processor, the method causes the first access network device to determining by a terminal device to perform Quality of Experience (QoE) measurement collection after disconnecting from the first access network device; Based on the terminal device determining to perform QoE measurement collection after disconnection, transmitting to the terminal device a QoE context identifier that identifies QoE context information to be used in the QoE measurement collection; sending the QoE context identifier and the QoE context information to a core network device; at least one memory storing instructions for executing the a first access network device comprising:

2. The first access network device determining that the terminal device disconnects from the first access network device; sending the QoE context identifier to the terminal device based on the terminal device deciding to disconnect from the first access network device; and transmitting the QoE context identifier to the terminal device by The first access network device of claim 1 .

3. The first access network device of claim 2 , wherein the QoE context identifier is transmitted via a Radio Resource Control (RRC) connection release message.

4. The first access network device determining that the terminal device disconnects from the first access network device; sending the QoE context identifier and the QoE context information to the core network device based on the terminal device deciding to disconnect from the first access network device; The first access network device according to claim 2 , wherein the first access network device causes the QoE context identifier and the QoE context information to be transmitted to the core network device by

5. The first access network device according to claim 1 , wherein the QoE context information comprises an address of a Measurement Collection Entity (MCE) to which QoE measurement reports received from the terminal device are forwarded.

6. The first access network device transmitting the QoE context identifier and the QoE context information to a core network device for further storage, wherein the QoE context information is subsequently acquired by the first access network device or another access network device; The first access network device according to claim 1 , wherein the first access network device transmits the QoE context identifier and the QoE context information to the core network device by

7. The first access network device further comprises: sending, to the terminal device, a QoE configuration for performing the QoE measurement collection before the terminal device is disconnected from the first access network device, the QoE configuration being based at least in part on the QoE context information; 7. A first access network device according to any preceding claim, adapted to execute:

8. The first access network device according to claim 1 , wherein the QoE context identifier is unique to the terminal device.

9. The first access network device according to claim 1 , 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 claim 1 , wherein the core network device hosts an Access and Mobility Management Function (AMF).

11. The first access network device further comprises: receiving session termination information from the terminal device to terminate QoE measurement collection; storing the session termination information in a context of the terminal device; sending the session termination information to a core network entity to terminate the QoE measurement collection; 11. A first access network device according to any preceding claim, adapted to execute:

12. a second access network device, at least one processor; When executed by the at least one processor, the method causes the second access network device to determining that a terminal device that is idle and performing quality of experience (QoE) measurement collection has connected to the second access network device; receiving, based on the terminal device determining that the terminal device connects to the second access network device, a QoE context identifier from the terminal device, the QoE context identifier identifying QoE context information to be used in the QoE measurement collection; sending a request for the QoE context information associated with the QoE context identifier to a core network device; receiving the QoE context information from the core network device; at least one memory storing instructions for executing the A second access network device comprising:

13. The second access network device of claim 12 , wherein the QoE context information includes an address of a Measurement Collection Entity (MCE) to which QoE measurement reports received from the terminal device are forwarded.

14. The second access network device further comprises: receiving a report of the QoE measurement collection from the terminal device; sending said report to a Measurement Collection Entity (MCE) based on said received QoE context information; 14. The second access network equipment according to claim 12 or 13, adapted to execute:

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

16. The second access network device according to claim 12 , 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 to 16, wherein the core network device hosts an Access and Mobility Management Function (AMF).

18. The second access network device further comprises: receiving session termination information from the terminal device to terminate the QoE measurement collection; storing the session termination information in a context of the terminal device; sending the session termination information to a Measurement Collection Entity (MCE) to terminate the QoE measurement collection; 18. A second access network device according to any one of claims 12 to 17, adapted to execute:

19. The second access network device according to any 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, at least one processor; When executed by the at least one processor, the terminal device is configured to: receiving a quality of experience (QoE) setting from a first access network device to perform QoE measurement collection in an idle state; receiving, from the first access network device, a QoE context identifier that identifies QoE context information to be 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; transmitting the QoE context identifier to the second access network device based on the connection to the second access network device; at least one memory storing instructions for executing the A terminal device comprising:

21. The terminal device further receiving a QoE configuration based at least in part on the QoE context information identified by the QoE context identifier; The terminal device according to claim 20, wherein the terminal device executes the following:

22. The terminal device further sending a report of said QoE measurement collection to said second access network device; The terminal device according to claim 20 or 21, which causes the terminal device to execute the following:

23. 23. A terminal device according to any one of claims 20 to 22, wherein the QoE context identifier is unique to the terminal device.

24. The terminal device according to claim 20 , wherein the QoE context identifier is common to a plurality of terminal devices including the terminal device.

25. The terminal device further sending, to the second access network device, session termination information to terminate the QoE measurement collection; 25. A terminal device according to any one of claims 20 to 24, adapted to execute:

26. 26. The terminal equipment according to claim 20, wherein the first access network equipment and the second access network equipment are the same access network equipment.

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

28. 28. The terminal device according to claim 20, wherein the QoE context identifier is transmitted to the second access network device via an RRC connection setup complete message.

29. determining, in a first access network device, that a terminal device performs Quality of Experience (QoE) measurement collection after disconnecting from the first access network device; Based on the terminal device determining to perform QoE measurement collection after disconnection, transmitting to the terminal device a QoE context identifier that identifies QoE context information to be used in the QoE measurement collection; sending the QoE context identifier and the QoE context information to a core network device; A method comprising:

30. determining, in a second access network device, that a terminal device performing quality of experience (QoE) measurement collection in an idle state connects to the second access network device; receiving, based on the terminal device determining that the terminal device connects to the second access network device, a QoE context identifier from the terminal device, the QoE context identifier identifying QoE context information to be used in the QoE measurement collection; sending a request for the QoE context information associated with the QoE context identifier to a core network device; receiving the QoE context information from the core network device; A method comprising:

31. receiving, at a terminal device, from a 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 that identifies QoE context information to be 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; transmitting the QoE context identifier to the second access network device based on the connection to the second access network device; A method comprising:

32. 1. A first device, comprising: means for determining, by a terminal device, to perform Quality of Experience (QoE) measurement collection after disconnection from the first device; Based on the terminal device determining to perform QoE measurement collection after disconnection, means for transmitting to said terminal device a QoE context identifier that identifies QoE context information used in said QoE measurement collection; means for transmitting the QoE context identifier and the QoE context information to a core network device; A first device comprising:

33. a second device, 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 the terminal device's decision to connect to the device, from the terminal device, a QoE context identifier that identifies QoE context information to be used in the QoE measurement collection; means for transmitting a request for the QoE context information associated with the QoE context identifier to a core network device; means for receiving the QoE context information from the core network equipment; A second device comprising:

34. a third device, means for receiving, from the first access network device, a Quality of Experience (QoE) setting for performing QoE measurement collection in an idle state; means for receiving from said first access network device a QoE context identifier that identifies QoE context information to be used in said QoE measurement collection; means for storing said QoE context identifier in said terminal device; means for disconnecting from the first access network device; means for connecting to a second access network device; means for transmitting the QoE context identifier to the second access network device based on the connection to the second access network device; A third device comprising:

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

Images