Quality of experience (QoE) method and apparatus

Abstract

Example embodiments of the present disclosure relate to a quality of experience (QoE) method and apparatus. A first device receives a Quality of Experience (QoE) configuration request from a second device, wherein the QoE configuration request indicates an action for at least one of: QoE measurement data, at least one QoE configuration maintained at the first device, or a QoE measurement collection; the first device performs an action indicated in the QoE configuration request. By this approach, QoE measurement behavior related to the execution of cached QoE measurement data, previous QoE configuration (s), and / or QoE measurement collection is controlled flexible without making the first device unambiguous.

Description

Technical Field

[0001] Various example embodiments of the present disclosure relate generally to the field of telecommunications, and in particular to methods, devices, apparatuses, and computer-readable storage media for Quality of Experience (QoE). Background Art

[0002] In order to manage the quality provided by the communication network, there is an increasing need for technologies to manage and guarantee the Quality of Experience (QoE). For this purpose, QoE measurement collection is introduced to measure the experience of end users when using specific applications to ensure the quality level that users can experience. Currently, QoE measurements for streaming services and for multicast broadcast services (MBS) in idle and / or inactive states are required to be supported by the Third Generation Partnership Project (3GPP). Summary of the invention

[0003] In a first aspect of the present disclosure, a first device is provided. The first device includes at least one processor; and at least one transceiver, the at least one transceiver is coupled to the at least one processor and is configured to: receive a quality of experience (QoE) configuration request from a second device, wherein the QoE configuration request indicates an action for at least one of the following: QoE measurement data, at least one QoE configuration maintained at the first device, or QoE measurement collection; the at least one processor is configured to perform the action indicated in the QoE configuration request.

[0004] In a second aspect of the present disclosure, a second device is provided. The second device is configured to determine an action to be performed by a first device for at least one of: QoE measurement data, at least one QoE configuration maintained at the first device, or a QoE measurement collection; and at least one transceiver coupled to at least one processor and configured to transmit a QoE configuration request indicating the action to the first device.

[0005] In a third aspect of the present disclosure, a method is provided. The method includes: receiving, at a first device, a quality of experience (QoE) configuration request from a second device, wherein the QoE configuration request indicates an action for at least one of the following: QoE measurement data, at least one QoE configuration maintained at the first device, or QoE measurement collection; and performing, at the first device, the action indicated in the QoE configuration request.

[0006] In a fourth aspect of the present disclosure, a method is provided. The method includes determining, at a second device, an action to be performed by a first device for at least one of: quality of experience (QoE) measurement data, at least one QoE configuration maintained at the first device, or a QoE measurement collection; and transmitting, from the second device to the first device, a QoE configuration request indicating the action.

[0007] In a fifth aspect of the present disclosure, a first device is provided. The first device includes: a component for receiving a quality of experience (QoE) configuration request from a second device, wherein the QoE configuration request indicates an action for at least one of the following: QoE measurement data, at least one QoE configuration maintained at the first device, or QoE measurement collection; and a component for performing the action indicated in the QoE configuration request.

[0008] In a sixth aspect of the present disclosure, a second device is provided. The second device includes: a component for determining an action to be performed by a first device for at least one of: QoE measurement data, at least one QoE configuration maintained at the first device, or a QoE measurement collection; and a component for transmitting a QoE configuration request indicating the action to the first device.

[0009] In a seventh aspect of the present disclosure, a computer-readable medium is provided, wherein the computer-readable medium includes instructions stored thereon, and the instructions are used to cause a device to at least execute the method according to the third aspect.

[0010] In an eighth aspect of the present disclosure, a computer-readable medium is provided, wherein the computer-readable medium includes instructions stored thereon, and the instructions are used to cause a device to at least execute the method according to the fourth aspect.

[0011] In a ninth aspect of the present disclosure, a computer program is provided. The computer program comprises instructions. When the instructions are executed by a device, the device is caused to at least perform the method according to the third aspect.

[0012] In a tenth aspect of the present disclosure, a computer program is provided, the computer program comprising instructions, which, when executed by a device, cause the device to at least perform the method according to the fourth aspect.

[0013] It should be understood that the invention 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

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

[0015] Figure 1 An example communication system is shown in which example embodiments of the present disclosure may be implemented;

[0016] Figure 2 shows a signaling diagram for communication according to some example embodiments of the present disclosure;

[0017] Figure 3shows a signaling diagram for communication according to some further example embodiments of the present disclosure;

[0018] Figure 4 A flowchart showing a method implemented at a first device according to some example embodiments of the present disclosure is shown;

[0019] Figure 5 A flowchart showing a method implemented at a second device according to some example embodiments of the present disclosure is shown;

[0020] Figure 6 shows a simplified block diagram of a device suitable for implementing an example embodiment of the present disclosure; and

[0021] Figure 7 A block diagram of an example computer-readable medium is shown according to some example embodiments of the present disclosure.

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

[0023] The principle of the present disclosure will now be described with reference to some example embodiments. It should be understood that these embodiments are described only for the purpose of illustrating and helping those skilled in the art to understand and implement the present disclosure, without implying any limitation on the scope of the present disclosure. The embodiments described herein can be implemented in various ways except for the way described below.

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

[0025] 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 must include the particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. In addition, when a particular feature, structure, or characteristic is described in conjunction with an example embodiment, whether or not explicitly described, it is considered to be within the knowledge of those skilled in the art to affect the combination of such feature, structure, or characteristic with other embodiments.

[0026] 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. 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 without departing from the scope of the example embodiments. As used herein, the term "and / or" includes any and all combinations of one or more listed terms.

[0027] As used herein, “at least one of: ” and “at least one of ” and similar expressions, where a list of two or more elements is combined 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.

[0028] As used herein, unless explicitly stated, performing a step "in response to A" does not indicate that the step is performed immediately after "A" occurs, and may include one or more intermediate steps.

[0029] The terms used herein are used only for the purpose of describing specific embodiments and are not intended to limit the exemplary embodiments. As used herein, the singular forms "a", "an", and "the" are also intended to include the plural forms unless the context clearly indicates otherwise. It will be further understood that the terms "comprises", "includes", "has", "contains", "has", and / or "comprising" when used herein specify 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.

[0030] As used in this application, the term "circuitry" may refer to one or more or all of the following: (a) hardware circuit implementation only (such as implementation only in analog and / or digital circuitry) and (b) a combination of hardware circuitry and software such as (where applicable): (i) a combination of analog and / or digital hardware circuits and software / firmware, and (ii) any portion of a hardware processor(s) with software (including digital signal processor(s), software, and memory(s) that work together to enable a device such as a mobile phone or server to perform various functions) and (c) Hardware circuits and / or processor(s), such as microprocessor(s) or portions of microprocessor(s), that require software (e.g., firmware) for operation, but where the software may not be present,

[0031] This definition of circuitry applies to all uses of the 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 accompanying software and / or firmware. For example, the term circuitry also covers a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in a server, cellular network device, or other computing or network device, if applicable to the particular claim element.

[0032] 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 device and the network device in the communication network can be performed according to any suitable generation communication protocol, including but not limited to the third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G) communication protocol and / or any other protocol currently known or 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 will certainly be communication technologies and systems of future types that can embody the present disclosure. It should not be considered that the scope of the present disclosure is limited to the aforementioned system.

[0033] As used herein, the term "network device" refers to a node in a communication network, via which a terminal device accesses a network and / or serves a terminal device in a communication network. 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 NodeB (eNode B or eNB), a NR NB (also referred to as a gNB), a radio remote unit (RRU), a radio head (RH), a radio remote head (RRH), a relay, an integrated access and backhaul (IAB) node, a low power node (such as a femto), a micro, a non-terrestrial network (NTN) or a non-terrestrial network device (such as a satellite network device, a low earth orbit (LEO) satellite, and a geosynchronous earth orbit (GEO) satellite), an aircraft network device, etc., depending on the terminology and technology applied. In some example embodiments, a radio access network (RAN) split architecture includes a centralized unit (CU) and a distributed unit (DU) at an IAB donor node. The IAB node comprises a mobile terminal (IAB-MT) part that behaves like a UE towards the parent node, and the DU part of the IAB node behaves like a base station towards the next hop IAB node.

[0034] The term "terminal device" refers to any end device capable of wireless communication. As an example and not limitation, a terminal device may also be referred to as a communication device, a user equipment (UE), a subscriber station (SS), a portable subscriber station, a mobile station (MS), or an 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 ring 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), a USB dongle, a smart device, a wireless customer premises equipment (CPE), an Internet of Things (IoT) device, a watch or other wearable device, a head mounted display (HMD), a vehicle, a drone, medical equipment and applications (e.g., remote surgery), industrial equipment and applications (e.g., robots and / or other wireless devices operating in the context of an industrial and / or automated processing chain), consumer electronic devices, equipment operating on a commercial and / or industrial wireless network, etc. The terminal device may also correspond to the mobile terminal (MT) part of an integrated access and backhaul (IAB) node (also referred to as a relay node). In the following description, the terms "terminal device", "communication device", "terminal", "user equipment" and "UE" may be used interchangeably.

[0035] As used herein, the term "resource", "transmission resource", "resource block", "physical resource block" (PRB), "uplink resource" or "downlink resource" may refer to any resource used to perform communication, for example, communication between a terminal device and a network device, such as time domain resources, frequency domain resources, spatial domain resources, code domain resources or any other resource that enables communication. In the following, unless explicitly stated, resources in the frequency domain and the time domain will be used as examples of transmission resources for describing some example embodiments of the present disclosure. Note that the example embodiments of the present disclosure are also applicable to other resources in other domains.

[0036] Figure 1 An example communication system 100 is shown in which example embodiments of the present disclosure may be implemented. The communication system 100 includes a plurality of communication devices, including a first device 110 and a second device 120, which may communicate with each other.

[0037] exist Figure 1 In the example of , the first device 110 may include a terminal device, and the second device 120 and the third device 130 may include network devices. The service area of ​​the second device 120 or the third device 130 may be referred to as a cell.

[0038] The communication in the communication environment 100 can be implemented according to any appropriate (multiple) communication protocols, including but not limited to the third generation (3G), the fourth generation (4G), the fifth generation (5G), the sixth generation (6G), etc., 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 multiple access (OFDMA), discrete Fourier transform spread OFDM (DFT-s-OFDM) and / or any other technology currently known or developed in the future.

[0039] It should be understood that Figure 1 The number of devices and their connections shown in the figure is for illustrative purposes only and does not imply any limitation. The communication system 100 may include any suitable number of devices configured as an example embodiment of the present disclosure. Although not shown, it should be understood that one or more additional devices may be located in and included in the communication system 100. Note that although shown as a terminal device, the first device 110 may be a device other than a terminal device. Although shown as a network device, the second device 120 or the third device 130 may be a device other than a network device.

[0040] Hereinafter, for the purpose of illustration, some example embodiments are described in which the first device 110 is operated as a terminal device, and the second device 120 and the third device 130 are operated as network devices. However, in some example embodiments, the operations described in conjunction with the terminal device may be implemented at a network device or other device, and the operations described in conjunction with the network device may be implemented at a terminal device or other device.

[0041] In some example embodiments, if the first device 110 is a terminal device and the second device 120 and the third device 130 are network devices, the link from the second device 120 or the third device 130 to the first device 110 is referred to as a downlink (DL), and the link from the first device 110 to the second device 120 or the third device 130 is referred to as an uplink (UL). In the DL, the second device 120 or the third device 130 is a transmission (TX) device (or transmitter), and the first device 110 is a reception (RX) device (or receiver). In the UL, the first device 110 is a TX device (or transmitter), and the second device 120 or the third device 130 is an RX device (or receiver).

[0042] In the communication system 100, the first device 110 may change or switch between various operating states. In some cases, the first device 110 may be in a connected state with the second device 120 or the third device 130. In the connected state, the first device 110 may have at least one communication connection (e.g., a radio resource control (RRC) connection) with the second device 120 or the third device 130, on which the first device 110 may actively communicate with the second device 120 or the third device 130 to transmit and / or receive data and control information. In the connected state, the second device 120 or the third device 130 to which the first device 110 is connected may have a context (e.g., a UE context) of the first device 110. The device context (e.g., a UE context) may include at least one of an access layer context, one or more radio link configuration parameters, bearer configuration information, security information, layer configuration information, and / or other configuration information for the device.

[0043] In some cases, for the purpose of power saving, mobility, etc., the first device 110 may be converted to a power saving state, such as an inactive state or an idle state. In the inactive state, the first device 110 does not have an active communication connection (e.g., an RRC connection). In some example embodiments, the context of the first device 110 may be maintained on the network side, such as at the second device 120 or the third device 130 to which the first device 110 is connected. In some example embodiments, the first device 110 in the inactive state may be able to perform, for example, a small data transmission and / or control information exchange with the second device 120 or the third device 130. Being in the inactive state allows the first device 110 to quickly resume the communication connection with the second device 120 or the third device 130. It should be noted that the device to which the first device 110 is connected from the inactive state may be the same or different from the device to which the first device 110 was previously connected. In the idle state, the first device 110 has no communication connection (e.g., an RRC connection) with the network device, and no context is maintained on the network side (e.g., the second device 120 or the third device 130).

[0044] At a radio resource control (RRC) layer of the first device 110, the connected state may be referred to as an RRC_Connected state, the inactive state may be referred to as an RRC_Inactive state, and the idle state may be referred to as an RRC_Idle state. The first device 110 may transition between different operating states, for example, from a connected state to an inactive state or an idle state, from an inactive state to a connected state or an idle state, and / or from an idle state to a connected or inactive state.

[0045] In operation of a communication system, a first device such as a terminal device may be configured to perform QoE measurement collection according to a quality of experience (QoE) configuration to collect QoE measurement data. The QoE measurement collection may be performed when the first device is in a connected state, and the collected QoE measurement data may be reported to a device to which the first device is connected. Currently, with more services being supported in a communication system, it is proposed that devices may also support QoE measurements in other states, such as in an inactive or idle state. For example, MBS (Multicast Broadcast Service), which allows resource-efficient transmission to multiple terminal users requesting to receive the same content, typically transmits information in DL, and may support information communication even in an idle or inactive state of the first device. The terminal device may perform real video (RV)-QoE measurements during a connected, idle, or inactive state.

[0046] However, new challenges arise from the fact that QoE measurement collection is performed in an idle or inactive state. The first device can continue QoE measurement collection, but may not be able to report the collected QoE measurement data during the idle or inactive state. One of the problems is that when the first device returns to the connected state, the first device cannot determine whether the collected QoE measurement data is still valid in the new cell, whether the new cell supports QoE measurement collection or configuration. In this case, the first device may not know how to handle the cached QoE measurement data, the previously configured (multiple) QoE configurations and / or whether to continue QoE measurement collection. In some other cases, the first device can be configured to suspend QoE measurement data reporting or QoE measurement collection even if it is still in a connected state. Similar problems arise when the first device can resume QoE measurement data reporting or QoE measurement collection.

[0047] An unexpected behavior is that when the first device enters an idle or inactive state, the first device potentially removes the previous (multiple) QoE configurations and previous QoE measurement data. In addition, this may cause signaling overhead when the device to which the first device is connected will preferably collect previous QoE measurement data and / or reuse previous QoE configurations for measurement collection.

[0048] According to some example embodiments of the present disclosure, a scheme for QoE measurement control is provided. In the scheme, a first device is instructed by a second device to perform an action on QoE measurement data, at least one QoE configuration at the first device, and / or QoE measurement collection is maintained. The first device accordingly performs an action on the QoE measurement data, at least one QoE configuration maintained at the first device, and / or QoE measurement collection.

[0049] Through this solution, controlling the QoE measurement behavior related to the cached QoE measurement data, the previous (multiple) QoE configurations and / or the execution of QoE measurement collection is flexible without making the first device unclear. In addition, by requesting the first device to properly handle the QoE measurement data, the previous (multiple) QoE configurations and / or the execution of QoE measurement collection, resources used to report invalid QoE measurement data, maintain invalid (multiple) QoE configurations and / or perform meaningless QoE measurement collection can also be saved.

[0050] Hereinafter, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

[0051] Reference now Figure 2 , which shows a signaling diagram 200 for communication according to some example embodiments of the present disclosure. Figure 2 As shown in FIG. 1 , the signaling diagram 200 involves a first device 110, a second device 120, and a third device 130. For discussion purposes, reference is made to FIG. Figure 1 Signaling diagram 200 is described.

[0052] In the signaling diagram 200, the second device 120 determines 210 an action to be performed by the first device 110 for at least one of: QoE measurement data, at least one QoE configuration maintained at the first device 110, or a QoE measurement collection. The second device 120 transmits 215 a QoE configuration request to the first device 110 indicating the action to be performed.

[0053] In the signaling diagram 200, it is assumed that the first device 110 may have QoE measurement data cached and / or to be cached. Alternatively or additionally, the first device 110 may maintain at least one QoE configuration for QoE measurement collection. Alternatively or additionally, the first device 110 may perform QoE measurement collection to collect QoE measurement data. In block 205, caching of QoE measurement data, maintenance of at least one QoE configuration, and / or QoE measurement collection are shown.

[0054] Upon receiving 220 the QoE configuration request from the second device 120 , the first device performs 225 the actions indicated in the QoE configuration request.

[0055] The first device 110 is configured to perform QoE measurement collection according to (multiple) QoE configurations to collect QoE measurement data. When communication resources are available for reporting, the QoE measurement data can be cached at the first device 110 and reported to the same or another communication device, for example, to a network device. The QoE measurement data includes various QoE measurement metrics that can be collected by the first device 110. The QoE configuration (also referred to as the QoE measurement configuration) includes QoE measurement parameters to configure QoE measurements at the first device 110. In some example embodiments, the QoE configuration may be sent to the first device 110 via a reconfiguration message (such as an RRC reconfiguration message). The message may indicate a QoE measurement collection (QMC) configuration container, a configuration for reporting QoE measurement data (such as a configuration for system resource block 4 (SRB4)), a service type for which the QoE measurement data is collected, and / or other information. In some example embodiments, the first device 110 may maintain multiple QoE configurations in parallel.

[0056] In some example embodiments, first device 110 may receive a QoE configuration for QoE measurement collection, for example, at an access stratum (AS) layer, such as an RRC layer. The AS layer of first device 110 may pass the QoE configuration and other required parameters, for example, to an application (App) layer of first device 110. QoE measurement collection may be performed at the App layer of first device 110, and the collected QoE measurement data may be cached for reporting.

[0057] It should be understood that some examples are provided above, and there is no specific limitation on QoE measurement data, QoE configuration, and QoE measurement collection in the embodiments of the present disclosure.

[0058] In an example embodiment of the present disclosure, configuration operations are provided for the second device 120 to configure the first device 110 to process previously cached QoE measurement data, previous(s) QoE configurations and / or whether the first device 110 needs to resume or stop QoE measurement collection.

[0059] In some example embodiments, the first device 110 may transition from an idle state or an inactive state to a connected state with the second device 120. The first device 110 may perform QoE measurement collection according to (multiple) QoE configurations, and cache the collected QoE measurement data during the idle state or the inactive state. As an example embodiment, assume that the first device 110 is connected to the second device 120. Figure 1The third device 130 in the embodiment is in a connected state and decides to transition to an idle or inactive state. The third device 130 may determine to select the first device 110 to continue the QoE measurement collection in the idle or inactive state. Then, the third device 130 transmits an indication to continue the QoE measurement collection in the idle or inactive state, for example, in a message (e.g., an RRC release message) that places the first device 110 in the idle or inactive state. After receiving the indication, the first device 110 may perform the QoE measurement collection when in the idle or inactive state.

[0060] In this case, if the first device 110 is connected to the second device 120 and transitions from an idle or inactive state to a connected state, the second device 120 may configure the first device 110 to process the cached QoE measurement data, the previous (multiple) QoE configurations, and / or the QoE measurement collection through a QoE configuration request. The QoE configuration request sent from the second device 120 may indicate an action to be performed if the first device 110 transitions from an idle or inactive state to a connected state. Note that the second device 120 may be a different device (e.g., a different network device) than the device to which the first device 110 was previously connected, or may be the same device.

[0061] In some example embodiments, when performing QoE measurement collection according to (multiple) QoE configurations, the first device 110 may be in a connected state with the second device 120. The first device 110 may be configured to suspend QoE measurement reporting to the second device 120, and thus may need to cache the collected QoE measurement data. In this case, in the case where the first device 110 in the connected state is configured to resume reporting of QoE measurement data, the QoE configuration request sent from the second device 120 may indicate an action to be performed.

[0062] In some example embodiments, in the QoE configuration request, the action for the QoE measurement data may include discarding or retaining the QoE measurement data cached at the first device 110. In some example embodiments, the cached QoE measurement data may be collected during a time period when the first device is in an idle state or an inactive state. In some example embodiments, the cached QoE measurement data may be collected during a time period when the first device 110 is in a connected state in which reporting of QoE measurement data is suspended. The second device 120 may flexibly configure whether to allow the first device 110 to continue reporting QoE measurement data collected during an idle state or an inactive state or during a time period in which reporting is suspended. For invalid QoE measurement data, the second device 120 may command the first device 110 to discard the invalid QoE measurement data without reporting, which may save resources for transmitting measurement data and cache space at the first device 110 (e.g., in an air interface).

[0063] In some example embodiments, in the QoE configuration request, the action for the QoE configuration may include continuing or discarding at least one QoE configuration maintained at the first device 110. The (multiple) QoE configurations maintained at the first device 110 may include QoE configurations from one or more devices (e.g., the third device 130) to which the first device 110 was previously connected. The second device 120 may determine whether to reuse the (multiple) QoE configurations at a later stage for QoE measurement collection, and then determine whether to configure the first device 110 to continue or discard the (multiple) QoE configurations. For example, if the second device 120 is the same device to which the first device 110 was previously connected or the second device 120 is within a specific area where the previous QoE configuration is still valid, there is no need to reconfigure the first device 110 with a new QoE configuration. The second device 120 may request the first device 110 to reuse (e.g., continue) the previous QoE configuration maintained at the first device 110 by transmitting an indication in the QoE configuration request. In some other examples, for other reasons, the second device 120 may request the first device 110 to discard the previous QoE configuration(s). In this way, for invalid QoE configuration(s), the second device 120 may instruct the first device 110 to directly discard the invalid QoE configuration(s) or configure a new one as a replacement without reporting, which may save signaling resources (e.g., in the air interface).

[0064] In some example embodiments, in the QoE configuration request, the action for QoE measurement collection may include resuming or stopping QoE measurement collection. For example, if the first device 110 performs QoE measurement collection when in an idle or inactive state and connects to the second device 120 from the idle or inactive state, the second device 120 that does not support QoE measurement collection may request the first device 110 to stop QoE measurement collection. In some cases, if the second device 120 does not support QoE measurement collection due to a temporary overload and may want to resume QoE measurement reporting later, the second device 120 may indicate to the first device 110 to temporarily stop (or pause) or update QoE measurement collection (to obtain the latest collection). In another example, if the first device 110 does not perform QoE measurement collection (e.g., when in an idle or inactive state, or when requested to pause collecting QoE measurement collection), the second device 120 may request the first device 110 to resume collection.

[0065] In some example embodiments, the actions for QoE measurement data, at least one QoE configuration, and / or QoE measurement collection may be indicated explicitly or implicitly in the QoE configuration request. For the case of explicit indication, the QoE configuration request may include one or more fields for specific indications of the actions for QoE measurement data, the actions for at least one QoE configuration, and / or the actions for QoE measurement collection. For the case of implicit indication, in some example embodiments, the indication to continue the QoE configuration may implicitly indicate the action to resume QoE measurement collection.

[0066] In some example embodiments, for the case of implicit indication, the QoE configuration request may include information related to another QoE configuration provided by the second device 120 to the first device 110. Actions for QoE measurement data, at least one QoE configuration, and / or QoE measurement collection may be indicated by the presence of information related to another QoE configuration in the QoE configuration request.

[0067] In some example embodiments, the QoE configuration request indicates that a new QoE configuration (e.g., a QMC configuration container and an SRB4 configuration) is provided to the first device 110 to perform QoE measurement data, and the QoE configuration request may implicitly indicate that the new QoE configuration will overwrite the previous (multiple) QoE configurations maintained at the first device 110. The first device 110 may discard the previous (multiple) QoE configurations or stop using the previous (multiple) QoE configurations to collect QoE measurement data. The first device 110 may start QoE measurement collection using the new QoE configuration.

[0068] In some example embodiments, if the information included in the QoE configuration request indicates that no new QoE configuration is provided, the QoE configuration request may implicitly indicate that the first device 110 may continue to use the previous QoE configuration(s) for QoE measurement collection.

[0069] In some example embodiments, depending on a pre-agreement or pre-configuration between the first device 110 and the second device 120, the presence of a new QoE configuration may implicitly indicate to discard or retain the QoE measurements cached at the first device 110.

[0070] It should be understood that some examples of implicit indications are provided above, and there may be other ways to implicitly indicate an action in a QoE configuration request. It should also be understood that in some other example embodiments, in addition to one or more explicit indications for an action, the QoE configuration request may also include information related to another QoE configuration.

[0071] In some example embodiments, the action for QoE measurement data, the action for at least one QoE configuration, and / or the action for QoE measurement collection may be indicated in the same or different signaling to the first device 110. In some example embodiments, the QoE configuration request may be transmitted from the second device 120 to the first device 110 in any suitable signaling.

[0072] In some example embodiments, the QoE configuration request may be transmitted to the first device 110 in dedicated signaling.

[0073] Specifically, in some example embodiments, when first device 110 connects to second device 120 from an idle or inactive state, the QoE configuration request may be indicated in any signaling transmitted to first device 110. In some example embodiments, the QoE configuration request may be transmitted to first device 110 when first device 110 is in an idle or inactive state, during a state transition process, or after first device 110 has completed a state transition.

[0074] As an example, the first device 110 in an inactive state may request to connect to the second device 120 via an RRC recovery request. The second device 120 may accept the connection of the first device 110 and transmit an RRC recovery message to the first device 110, which may include a QoE configuration request. In another example, if the first device 110 is connected to the second device 120 from an idle state, the QoE configuration request may be included in a message transmitted to the first device 110 to indicate that the communication connection has been established. After the first device 110 has completed a state transition from an idle or inactive state, the QoE configuration request may be transmitted to the first device 110, for example, via an RRC reconfiguration message. In some examples, when the first device 110 is in an inactive state, the QoE configuration request may be carried in a message from the second device 120 for small data transmission.

[0075] In some example embodiments, when first device 110 is in a connected state with second device 120 (e.g., in the case where reporting of QoE measurement data is suspended, second device 120 decides to resume reporting), a QoE configuration request may be transmitted to first device 110. In this case, the QoE configuration request may be transmitted to first device 110, for example, via an RRC reconfiguration message.

[0076] In some example embodiments, the QoE configuration request may be transmitted to the first device 110 via broadcast signaling, such as via system information block (SIB) signaling.

[0077] It should be appreciated that the QoE configuration request can be transmitted to the first device 110 in any other suitable message / signaling, and the scope of the present disclosure is not limited in this respect.

[0078] In some example embodiments, the second device 120 may make decisions on actions for QoE measurement data, at least one QoE configuration, and / or QoE measurement collection based on various factors and / or configuration information. As an example, in the case where the first device 110 is connected to the second device 120 from an inactive state, the second device 120 may be able to retrieve context information from a device (e.g., the third device 130) to which the first device 110 was previously connected, or the second device 120 may locally maintain context information for the first device 110. The context information may indicate the QoE configuration(s) used by the first device 110. By analyzing the QoE configuration(s) used by the first device 110, the second device 120 may decide whether to reuse the QoE configuration(s), whether to receive QoE measurement data collected according to the QoE configuration(s), and / or whether to allow the first device 110 to resume or stop QoE measurement collection according to the QoE configuration(s). In some example embodiments, the second device 120 may be configured via a core network element such as an operations administration and maintenance (OAM) function as to whether or how to process QoE measurement data, at least one QoE configuration and / or QoE measurement collection.

[0079] It should be understood that the second device 120 can determine actions for QoE measurement data, at least one QoE configuration, and / or QoE measurement collection based on any other factors and / or configuration information, which is not limited within the scope of the present disclosure.

[0080] In some example embodiments, considering QoE measurement collection performed when the first device 110 is in an inactive or idle state, in addition to or as an alternative to the QoE configuration request, the first device 110 may receive validity control information to control the validity of QoE measurement data, (multiple) QoE configurations and / or QoE measurement collection during the inactive or idle state. Figure 3 A signaling diagram 300 for communication according to such an example embodiment is shown. Figure 3 As shown in FIG. 3 , the signaling diagram 300 involves the first device 110, the second device 120, and the third device 130. For discussion purposes, reference is made to FIG. Figure 1 A signaling diagram 300 is described.

[0081] In the signaling diagram 300, for illustration purposes, it is assumed that the first device 110 is first in a connected state with the third device 130. The third device 130 may transmit 310, and the first device 110 may receive 315, validity control information for at least one of the following: QoE measurement data, at least one QoE configuration maintained at the first device, or QoE measurement collection in an idle or inactive state of the first device 110. If the first device 110 transitions to an idle or inactive state, the validity control information may be used to control the validity of the QoE measurement data, at least one QoE configuration maintained at the first device 110, or the QoE measurement collection.

[0082] The validity control information may be communicated to the first device 110 at any suitable time and with any suitable signaling. In some example embodiments, the validity control information may be transmitted to the first device 110 in a message used to place the first device 110 in an inactive or idle state. For example, an RRC release message used to instruct the first device 110 to switch from a connected state to an inactive state may include the validity control information. In some example embodiments, the validity control information may be included in any message transmitted to the first device 110 during the connected state, such as included in an RRC reconfiguration message. The scope of the present disclosure is not limited to the message used to communicate the validity control information.

[0083] In some example embodiments, the validity control information may indicate the validity time of the QoE measurement data cached during the idle or inactive state of the first device 110. The validity time may mean the latest time period for data collection / caching. In some example embodiments, the validity control information may indicate the validity time for at least one QoE configuration maintained at the first device 110 during the idle or inactive state of the first device 110. Alternatively or additionally, the validity control information may indicate the validity time for performing QoE measurement collection during the idle or inactive state of the first device 110. The validity control information may indicate the effective buffer size to be used for QoE measurement data collection. By configuring the validity time, the third device 130 to which the first device 110 is connected can effectively control the validity of the QoE measurement data at the first device 110 during the inactive or idle state, and / or the validity of the QoE configuration and / or QoE measurement collection during the inactive or idle state.

[0084] In some cases, the first device 110 can transition 320 from the connected state to an idle or inactive state. When the first device 110 is in the idle state or inactive state, the first device 110 can still perform QoE measurement collection to collect QoE measurement data according to one or more QoE configurations and cache the collected QoE measurement data. The caching of QoE measurement data, the maintenance of at least one QoE configuration, and / or the QoE measurement collection are collectively shown in block 325.

[0085] In the absence of an active communication connection, the collected QoE measurement data may be cached at the first device 110. In some example embodiments, there may be QoE measurement data collected when the first device 110 is in a connected state but has no chance to be reported to the third device 130.

[0086] Based on the validity control information received 310 from the third device 130, after the first device 110 transitions to an idle or inactive state, the first device 110 may control 330 the validity of at least one of the following based on the validity control information: QoE measurement data, at least one QoE configuration maintained at the first device, or QoE measurement collection.

[0087] In some example embodiments, the first device 110 may start at least one timer using the validity time indicated by at least one of the validity control information for the cached QoE measurement data, at least one QoE configuration maintained at the first device, and / or QoE measurement collection. In some example embodiments, if the validity time of the cached QoE measurement data expires, the first device 110 may discard the cached QoE measurement data. If new QoE measurement data is collected and / or cached, the first device 110 may continue to monitor the cache time of those QoE measurement data, and clear part or all of the collected and / or cached measurement data from the cache as long as the validity time expires. In some example embodiments, if the validity time of the QoE configuration expires, the first device 110 may stop the QoE measurement collection based on the QoE configuration, or may discard the QoE configuration. In some example embodiments, if the validity time for the QoE measurement collection expires, the first device 110 may stop the QoE measurement collection.

[0088] In some cases, the first device 110 can transition from an inactive or idle state to a connected state. Figure 3 In the example of , for illustration purposes, it is assumed that the first device 110 is connected to the second device 120, but it should be understood that the first device 110 can be connected to the third device 130 with which it was previously connected.

[0089] The second device 120 determines 335 and transmits 340 a QoE configuration request indicating an action to be performed by the first device 110 for at least one of: QoE measurement data, at least one QoE configuration maintained at the first device 110, or QoE measurement collection. By receiving 345 the QoE configuration request, the first device 110 performs 350 the action in the QoE configuration request. The operations at 335, 340, 345, and 350 are similar to Figure 2 For the sake of brevity, the operations at 210, 215, 220 and 225 are omitted here.

[0090] In some example embodiments, with the validity control information, when a validity time indicated in the validity control information expires, for example, when a validity time for QoE measurement data, a validity time for at least one QoE configuration maintained at the first device, and / or a validity time for QoE measurement collection expires, the first device 110 may perform an action indicated in the QoE configuration request.

[0091] In the example embodiments discussed above, through QoE configuration requests and / or validity control information, QoE measurement-related behaviors (e.g., caching of QoE measurement data, QoE configuration, and / or QoE measurement collection) in inactive or idle states and / or other situations can be flexibly and efficiently controlled according to actual needs in different applications.

[0092] Figure 4 FIG. 4 is a flowchart of an example method 400 implemented at a first device according to some example embodiments of the present disclosure. Figure 1 The method 400 is described from the perspective of the first device 110.

[0093] At block 410, the first device 110 receives a request from a second device (eg, Figure 1 The second device 120 in the embodiment receives a quality of experience (QoE) configuration request, wherein the QoE configuration request indicates an action for at least one of the following: QoE measurement data, at least one QoE configuration maintained at the first device, or QoE measurement collection.

[0094] At block 420 , the first device 110 performs the actions indicated in the QoE configuration request.

[0095] In some example embodiments, the action with respect to the QoE measurement data includes discarding or retaining the QoE measurement data cached at the first device 110 .

[0096] In some example embodiments, the action for the QoE configuration includes continuing or discarding at least one QoE configuration maintained at the first device 110 .

[0097] In some example embodiments, the action with respect to QoE measurement collection includes resuming or stopping QoE measurement collection.

[0098] In some example embodiments, the QoE configuration request contains information related to another QoE configuration, and wherein the action is indicated by the presence of the information related to another QoE configuration in the QoE configuration request.

[0099] In some example embodiments, method 400 further includes: receiving validity control information in an idle or inactive state of first device 110 for at least one of: QoE measurement data, at least one QoE configuration maintained at first device 110, or QoE measurement collection; and if it is determined that first device 110 transitions from a connected state to an idle or inactive state, based on the validity control information, controlling the validity of at least one of: QoE measurement data, at least one QoE configuration maintained at first device 110, or QoE measurement collection.

[0100] In some example embodiments, the validity control information indicates at least one of a validity time for cached QoE measurement data, a validity time for at least one QoE configuration maintained at the first device 110, or a validity time for performing QoE measurement collection.

[0101] In some example embodiments, the validity control information is received from a third device to which the first device 110 is connected in a connected state.

[0102] In some example embodiments, the QoE measurement data is collected during time periods when the first device 110 is in an idle or inactive state.

[0103] In some example embodiments, the QoE configuration request indicates an action to be performed in one of the following situations: the first device 110 transitions from an idle or inactive state to a connected state, the validity time for at least one of the following is expired: QoE measurement data, at least one QoE configuration maintained at the first device 110, or QoE measurement collection when the first device 110 is in an idle or inactive state, or the first device 110 in a connected state is configured to resume reporting of QoE measurement data.

[0104] In some exemplary embodiments, the first device 110 includes a terminal device, and the second device 120 includes a network device.

[0105] In some example embodiments, the QoE configuration request is included in dedicated signaling or broadcast signaling.

[0106] Figure 5FIG. 5 is a flowchart of an example method 500 implemented at a second device according to some example embodiments of the present disclosure. Figure 1 The method 500 is described from the perspective of the second device 120.

[0107] At block 510, the second device 120 determines that the first device (eg, Figure 1 An action performed by a first device 110 in the embodiment of the present invention on at least one of: QoE measurement data, at least one QoE configuration maintained at the first device, or QoE measurement collection.

[0108] At block 520 , the second device 120 transmits a QoE configuration request indicating an action to the first device 110 .

[0109] In some example embodiments, the action with respect to the QoE measurement data includes discarding or retaining the QoE measurement data cached at the first device 110 .

[0110] In some example embodiments, the action for the QoE configuration includes continuing or discarding at least one QoE configuration maintained at the first device 110 .

[0111] In some example embodiments, the action with respect to QoE measurement collection includes resuming or stopping QoE measurement collection.

[0112] In some example embodiments, the QoE configuration request contains information related to another QoE configuration, and wherein the action is indicated by the presence of the information related to another QoE configuration in the QoE configuration request.

[0113] In some example embodiments, the method 500 further comprises transmitting to the first device validity control information in an idle or inactive state of the first device 110 for at least one of: QoE measurement data, at least one QoE configuration maintained at the first device 110, or a QoE measurement collection.

[0114] In some example embodiments, the validity control information indicates at least one of a validity time for cached QoE measurement data, a validity time for at least one QoE configuration maintained at the first device 110, or a validity time for performing QoE measurement collection.

[0115] In some example embodiments, the QoE measurement data is collected during time periods when the first device 110 is in an idle or inactive state.

[0116] In some example embodiments, the QoE configuration request indicates an action to be performed in one of the following situations: the first device 110 transitions from an idle or inactive state to a connected state, the validity time for at least one of the following is expired: QoE measurement data, at least one QoE configuration maintained at the first device 110, or QoE measurement collection when the first device 110 is in an idle or inactive state, or the first device 110 in a connected state is configured to resume reporting of QoE measurement data.

[0117] In some exemplary embodiments, the first device 110 includes a terminal device, and the second device 120 includes a network device.

[0118] In some example embodiments, the QoE configuration request is included in dedicated signaling or broadcast signaling.

[0119] In some example embodiments, a first device (eg, Figure 1 The first device 110 in the embodiment may include a component for performing the corresponding operation of the method 400. The component may be implemented in any suitable form. For example, the component may be implemented in a circuit system or a software module. The first device may be implemented as or included in Figure 1 In the first device 110.

[0120] In some example embodiments, a first device includes means for receiving a quality of experience (QoE) configuration request from a second device, wherein the QoE configuration request indicates an action for at least one of: QoE measurement data, at least one QoE configuration maintained at the first device, or QoE measurement collection; and means for performing the action indicated in the QoE configuration request.

[0121] In some example embodiments, the action with respect to the QoE measurement data comprises discarding or retaining the QoE measurement data cached at the first device.

[0122] In some example embodiments, the action with respect to the QoE configuration includes continuing or discarding at least one QoE configuration maintained at the first device.

[0123] In some example embodiments, the action with respect to QoE measurement collection includes resuming or stopping QoE measurement collection.

[0124] In some example embodiments, the QoE configuration request contains information related to another QoE configuration, and wherein the action is indicated by the presence of the information related to another QoE configuration in the QoE configuration request.

[0125] In some example embodiments, the first device further includes: a component for receiving validity control information in an idle or inactive state of the first device for at least one of: QoE measurement data, at least one QoE configuration maintained at the first device, or QoE measurement collection; and a component for controlling the validity of at least one of: QoE measurement data, at least one QoE configuration maintained at the first device, or QoE measurement collection based on the validity control information if it is determined that the first device transitions from a connected state to an idle or inactive state.

[0126] In some example embodiments, the validity control information indicates at least one of: a validity time for cached QoE measurement data, a validity time for at least one QoE configuration maintained at the first device, or a validity time for performing QoE measurement collection.

[0127] In some example embodiments, the validity control information is received from a third device to which the first device is connected in a connected state.

[0128] In some example embodiments, the QoE measurement data is collected during a time period when the first device is in an idle or inactive state.

[0129] In some example embodiments, the QoE configuration request indicates an action to be performed in one of the following situations: the first device transitions from an idle or inactive state to a connected state; the validity period for at least one of the following is expired: QoE measurement data, at least one QoE configuration maintained at the first device, or QoE measurement collection when the first device is in an idle or inactive state, or the first device in a connected state is configured to resume reporting of QoE measurement data.

[0130] Optionally, the first device includes a terminal device, and the second device includes a network device.

[0131] In some example embodiments, the QoE configuration request is included in dedicated signaling or broadcast signaling.

[0132] In some example embodiments, the first apparatus further comprises means for performing the method 400 or other operations in some example embodiments of the first device 110. In some example embodiments, the means comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the execution of the first apparatus.

[0133] In some example embodiments, a second device (eg, Figure 1The second device 120 in the embodiment may include a component for performing the corresponding operation of method 500. The component may be implemented in any suitable form. For example, the component may be implemented in a circuit system or a software module. The second device may be implemented as or included in Figure 1 In the second device 120.

[0134] In some example embodiments, the second device includes components for determining an action to be performed by the first device with respect to at least one of: QoE measurement data, at least one QoE configuration maintained at the first device, or a QoE measurement collection; and components for transmitting a QoE configuration request indicating the action to the first device.

[0135] In some example embodiments, the action with respect to the QoE measurement data comprises discarding or retaining the QoE measurement data cached at the first device.

[0136] In some example embodiments, the action with respect to the QoE configuration includes continuing or discarding at least one QoE configuration maintained at the first device.

[0137] In some example embodiments, the action with respect to QoE measurement collection includes resuming or stopping QoE measurement collection.

[0138] In some example embodiments, the QoE configuration request contains information related to another QoE configuration, and wherein the action is indicated by the presence of the information related to another QoE configuration in the QoE configuration request.

[0139] In some example embodiments, the second device further comprises: means for transmitting to the first device validity control information in an idle or inactive state of the first device for at least one of: QoE measurement data, at least one QoE configuration maintained at the first device, or a QoE measurement collection.

[0140] In some example embodiments, the validity control information indicates at least one of: a validity time for cached QoE measurement data, a validity time for at least one QoE configuration maintained at the first device, or a validity time for performing QoE measurement collection.

[0141] In some example embodiments, the QoE measurement data is collected during a time period when the first device is in an idle or inactive state.

[0142] In some example embodiments, the QoE configuration request indicates an action to be performed in one of the following situations: the first device transitions from an idle or inactive state to a connected state; the validity period for at least one of the following is expired: QoE measurement data, at least one QoE configuration maintained at the first device, or QoE measurement collection when the first device is in an idle or inactive state, or the first device in a connected state is configured to resume reporting of QoE measurement data.

[0143] Optionally, the first device includes a terminal device, and the second device includes a network device.

[0144] In some example embodiments, the QoE configuration request is included in dedicated signaling or broadcast signaling.

[0145] In some example embodiments, the second apparatus further comprises means for performing the method 500 or other operations in some example embodiments of the second device 120. In some example embodiments, the means comprises: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second apparatus to perform.

[0146] Figure 6 6 is a simplified block diagram of a device 600 suitable for implementing an example embodiment of the present disclosure. The device 600 may be provided to implement a communication device, such as Figure 1 The first device 110, the second device 120 or the third device 130 shown in FIG. As shown in the figure, the device 600 includes one or more processors 610, one or more memories 620 that can be coupled to the processor 610, and one or more communication modules 640 that can be coupled to the processor 610.

[0147] The communication module 640 may be used for two-way communication. The communication module 640 may have one or more communication interfaces that facilitate communication with one or more other modules or devices. The communication interface may represent any interface necessary for communication with other network elements. In some example embodiments, the communication module 640 may include at least one transceiver. In some example embodiments, the communication module 640 may include at least one antenna.

[0148] As non-limiting examples, processor 610 may be of any type suitable for a local technology network, and may include one or more of the following: 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 of a synchronized main processor.

[0149] The memory 620 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) 624, electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disk (CD), digital video disk (DVD), and other magnetic and / or optical memories. Examples of volatile memories include, but are not limited to, random access memory (RAM) 622 and other volatile memories that are not retained during power failure.

[0150] The computer program 630 includes computer executable instructions executed by the associated processor 610. The instructions of the program 630 may include instructions for performing the operations / actions of some example embodiments of the present disclosure. The program 630 may be stored in the ROM 624. The processor 610 may perform any suitable actions and processes by loading the program 630 into the RAM 622.

[0151] The embodiments of the present disclosure may be implemented with the aid of a program 630, so that the device 600 may execute the following steps: Figures 2 to 5 Any process of the present disclosure discussed. The embodiments of the present disclosure may also be implemented by hardware, or by a combination of software and hardware.

[0152] In some embodiments, the program 630 may be tangibly embodied in a computer-readable medium that may be included in the device 600 (e.g., memory 620) or in other storage devices accessible by the device 600. The device 600 may load the program 630 from the computer-readable medium to the RAM 622 for execution. In some embodiments, the computer-readable medium may include any type of tangible non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. The term "non-transitory" as used herein is a limitation of the medium itself (i.e., tangible, not a signal), not a limitation on data storage persistence (e.g., RAM versus ROM).

[0153] Figure 7 An example of a computer readable medium 700 in the form of a CD or DVD or other optical storage disk is shown. The computer readable medium 700 has a program 630 stored thereon.

[0154] 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 that 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, as non-limiting examples, 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.

[0155] Some example embodiments of the present disclosure also provide at least one computer program product tangibly stored on a non-transient computer-readable storage medium. The computer program product includes computer executable instructions, such as those included in a program module, which are executed in a device on a target real or virtual processor to implement any of the methods described above. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. In various embodiments, the functions of the program modules can be combined or split between program modules as needed. Machine executable instructions for program modules can be executed in local or distributed devices. In distributed devices, program modules can be located in both local and remote storage media.

[0156] The program code for implementing the disclosed method may be written in any combination of one or more programming languages. These program codes may 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, when executed by the processor or controller, enables the functions / operations specified in the flow chart and / or block diagram to be implemented. The program code may be executed entirely on the machine, partially on the machine, as an independent software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

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

[0158] 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, electronic, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices, or equipment, or any suitable combination of the foregoing. More specific examples of computer readable storage media will 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.

[0159] In addition, 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 in order, or performing all operations shown to achieve desired results. In certain cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these should not be interpreted as limitations on the scope of the present disclosure, but should be interpreted as descriptions of features that may be specific to a particular embodiment. The specific 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.

[0160] Although the disclosure has been described in language specific to structural features and / or methodological acts, it should be understood that the disclosure defined in 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 device, comprising: at least one processor; as well as at least one transceiver coupled to the at least one processor and configured to: receiving a quality of experience (QoE) configuration request from a second device, wherein the QoE configuration request indicates an action for at least one of: QoE measurement data, at least one QoE configuration maintained at the first device, or QoE measurement collection; as well as The at least one processor is configured to perform the action indicated in the QoE configuration request. 2 . The first device of claim 1 , wherein the action with respect to the QoE measurement data comprises discarding or retaining the QoE measurement data buffered at the first device. 3 . The first device according to claim 1 , wherein the action for the QoE configuration comprises continuing or discarding the at least one QoE configuration maintained at the first device. 4 . The first device according to claim 1 , wherein the action for QoE measurement collection comprises resuming or stopping the QoE measurement collection.

5. The first device according to any one of claims 1 to 4, wherein the QoE configuration request contains information related to another QoE configuration, and wherein the action is indicated by the following: the presence of the information related to the another QoE configuration in the QoE configuration request.

6. The first device according to any one of claims 1 to 5, wherein the at least one transceiver is further configured to receive validity control information in an idle or inactive state of the first device for at least one of: QoE measurement data, at least one QoE configuration maintained at the first device, or a QoE measurement collection; and The at least one processor is configured to: if it is determined that the first device transitions from a connected state to the idle or inactive state, Based on the validity control information, validity of at least one of: QoE measurement data, at least one QoE configuration maintained at the first device, or QoE measurement collection is controlled.

7. The first device according to claim 6, wherein the validity control information indicates at least one of the following: The validity period of the cached QoE measurement data. a validity period for the at least one QoE configuration to be maintained at the first device, or The effective time for performing the QoE measurement collection.

8. The first device according to claim 6 or 7, wherein the validity control information is received from a third device to which the first device is connected in the connected state.

9. The first device according to any one of claims 1 to 8, wherein the QoE measurement data is collected during a time period when the first device is in an idle or inactive state.

10. The first device according to any one of claims 1 to 9, wherein the QoE configuration request indicates the action to be performed in one of the following situations: The first device transitions from an idle or inactive state to a connected state; a validity time for at least one of: the QoE measurement data, the at least one QoE configuration maintained at the first device, or the QoE measurement collection while the first device is in the idle or inactive state is expired, or The first device in the connected state is configured to resume reporting of QoE measurement data.

11. The first device according to any one of claims 1 to 10, wherein the first device comprises a terminal device, and the second device comprises a network device. 12 . The first device according to claim 1 , wherein the QoE configuration request is included in dedicated signaling or broadcast signaling.

13. A second device, comprising: at least one processor configured to determine an action to be performed by a first device with respect to at least one of: QoE measurement data, at least one QoE configuration maintained at the first device, or a QoE measurement collection; as well as At least one transceiver is coupled to the at least one processor and configured to transmit a QoE configuration request indicating the action to the first device.

14. The second device of claim 13, wherein the action with respect to the QoE measurement data comprises discarding or retaining the QoE measurement data buffered at the first device.

15. The second device according to claim 13 or 14, wherein the action for QoE configuration comprises continuing or discarding the at least one QoE configuration maintained at the first device.

16. The second device according to any one of claims 13 to 15, wherein the action for QoE measurement collection comprises resuming or stopping the QoE measurement collection.

17. The second device according to any one of claims 13 to 16, wherein the QoE configuration request contains information related to another QoE configuration, and wherein the action is indicated by the presence of the information related to the another QoE configuration in the QoE configuration request.

18. The second device according to any one of claims 13 to 17, wherein the at least one transceiver is further configured to: Validity control information in an idle or inactive state of the first device is transmitted to the first device for at least one of: QoE measurement data, at least one QoE configuration maintained at the first device, or a QoE measurement collection.

19. The second device according to claim 18, wherein the validity control information indicates at least one of the following: The validity period of the cached QoE measurement data, a validity period of the at least one QoE configuration maintained at the first device, or The effective time for performing the QoE measurement collection.

20. The second device according to any one of claims 13 to 19, wherein the QoE measurement data is collected during a time period when the first device is in an idle or inactive state.

21. The second device according to any one of claims 13 to 20, wherein the QoE configuration request indicates the action to be performed in one of the following situations: The first device transitions from an idle or inactive state to a connected state; a validity time for at least one of: the QoE measurement data, the at least one QoE configuration maintained at the first device, or the QoE measurement collection while the first device is in the idle or inactive state is expired, or The first device in the connected state is configured to resume reporting of QoE measurement data.

22. The second device according to any one of claims 13 to 21, wherein the first device comprises a terminal device, and the second device comprises a network device.

23. The second device according to any one of claims 13 to 22, wherein the QoE configuration request is included in dedicated signaling or broadcast signaling.

24. A method comprising: Receiving, at a first device, a quality of experience (QoE) configuration request from a second device, wherein the QoE configuration request indicates an action for at least one of: QoE measurement data, at least one QoE configuration maintained at the first device, or QoE measurement collection; as well as The action indicated in the QoE configuration request is performed at the first device.

25. A method comprising: determining, at a second device, an action to be performed by a first device with respect to at least one of: quality of experience (QoE) measurement data, at least one QoE configuration maintained at the first device, or a QoE measurement collection; as well as A QoE configuration request indicating the action is transmitted from the second device to the first device.

26. A first device, comprising: means for receiving a quality of experience (QoE) configuration request from a second device, wherein the QoE configuration request indicates an action for at least one of: QoE measurement data, at least one QoE configuration maintained at the first device, or QoE measurement collection; as well as Means for performing the action indicated in the QoE configuration request.

27. A second device, comprising: means for determining an action to be performed by a first device with respect to at least one of: QoE measurement data, at least one QoE configuration maintained at the first device, or a QoE measurement collection; as well as Means for transmitting a QoE configuration request indicative of the action to the first device.

28. A non-transitory computer-readable medium, the non-transitory computer-readable medium comprising instructions stored thereon, the instructions for causing an apparatus to at least perform the method according to claim 24 or the method according to claim 25.

Images