Experience Quality Measurement

By coordinating QoE configurations with unique identities across layers and network entities, the solution addresses the challenge of associating QoE configurations with reports, ensuring accurate tracking and efficient handling of multiple configurations, thus improving QoE measurement reliability and accuracy.

JP2024540967AActive Publication Date: 2024-11-06NOKIA TECHNOLOGIES OY
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
JP2024523796
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2021-10-22
Publication Date
2024-11-06
Estimated Expiration
2041-10-22

AI Technical Summary

Technical Problem

Current QoE measurement systems in communication networks face challenges in accurately associating QoE configurations with corresponding reports due to the use of RRC IDs, leading to issues like duplicate IDs and loss of identity during cell reselection or handover, which disrupts the QoE measurement and reporting process.

Method used

A method and apparatus that enable coordination between the access and application layers to associate QoE configurations with unique identities, ensuring that QoE reports can be correctly linked and tracked across different network entities, using mechanisms like AT commands and mapping tables to manage QoE configurations and reports.

Benefits of technology

This solution ensures accurate tracking and identification of QoE measurement configurations and reports, allowing for differentiated treatment of customer requirements and efficient handling of multiple QoE configurations, thereby enhancing the reliability and accuracy of QoE measurements.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024540967000001_ABST
    Figure 2024540967000001_ABST
Patent Text Reader

Abstract

The embodiments of the present disclosure relate to estimating downlink size for quality of experience (QoE) measurements. According to the embodiments of the present disclosure, a terminal device can coordinate between an access layer and an application layer to associate a QoE configuration with a corresponding report. In this way, a unique identification of a single QoE configuration and a corresponding QoE report in the terminal device is possible.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] FIELD OF THE DISCLOSURE Embodiments of the present disclosure relate generally to the field of telecommunications, and in particular to methods, devices, apparatus, and computer-readable storage media for quality of experience (QoE) measurement. [Background technology]

[0002] With the development of communication technology, several solutions have been proposed to provide an efficient and reliable solution for communication. To ensure communication performance, it is essential to measure communication quality. For example, Quality of Service (QoS) has been proposed. This refers to any technique that manages data traffic to reduce packet loss, latency, and jitter on the network. The fifth generation (5G) cellular network includes cloud computing, and QoS parameters may affect cloud network performance. User-perceived Quality of Experience (QoE) using multimedia services and applications depends heavily on QoS parameters. It is worth considering how to perform QoE measurement in a more efficient way. Summary of the Invention

[0003] Generally, the example embodiments of the present disclosure provide a solution to QoE measurement.

[0004] In a first aspect, a first apparatus is provided, the first apparatus including at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured to cause the first apparatus, using the at least one processor, to receive a radio resource control (RRC) configuration from a device, the radio resource control (RRC) configuration indicating a first identity generated in an RRC layer and a quality of experience (QoE) configuration of a service, determine a second identity for the QoE configuration based at least in part on the first identity indicated in the RRC configuration, transmit the QoE configuration together with the second identity to a second apparatus, and receive a QoE report of the service together with the second identity from the second apparatus.

[0005] In a second aspect, a second device is provided, the second device including at least one processor and at least one memory including computer program code configured to cause, using the at least one processor, the second device to receive a quality of experience (QoE) configuration of a service from the first device together with a second identity, generate a QoE report of the service based on the QoE configuration, and transmit the QoE report together with the second identity to the first device.

[0006] In a third aspect, a method is provided, the method including: receiving, at a first apparatus, a radio resource control (RRC) configuration from a device, the RRC configuration indicating a first identity generated in an RRC layer and a quality of experience (QoE) configuration of a service, determining a second identity for the QoE configuration based at least in part on the first identity indicated in the RRC configuration, transmitting the QoE configuration together with the second identity to a second apparatus, and receiving a QoE report of the service together with the second identity from the second apparatus.

[0007] In a fourth aspect, a method is provided, the method including: receiving, at a second device, a Quality of Experience (QoE) configuration of a service from a first device together with a second identity, generating a QoE report of the service based on the QoE configuration, and transmitting the QoE report together with the second identity to the first device.

[0008] In a fifth aspect, an apparatus is provided, the apparatus including: means for receiving, at a first apparatus, a radio resource control (RRC) configuration from a device, the RRC configuration indicating a first identity generated in an RRC layer and a quality of experience (QoE) configuration of a service, means for determining a second identity for the QoE configuration based at least in part on the first identity indicated in the RRC configuration, means for transmitting the QoE configuration together with the second identity to a second apparatus, and means for receiving, from the second apparatus, a QoE report of the service together with the second identity.

[0009] In a sixth aspect, an apparatus is provided, the apparatus including: means for receiving, at a second apparatus, a Quality of Experience (QoE) configuration of a service from a first apparatus together with a second identity, means for generating a QoE report of the service based on the QoE configuration, and means for transmitting the QoE report together with the second identity to the first apparatus.

[0010] In a seventh aspect, there is provided a computer readable medium comprising program instructions for causing an apparatus to perform at least a method according to any one of the third or fourth aspects above.

[0011] It should be understood that the summary section is not intended to identify 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 apparent through the following description.

[0012] Some example embodiments will now be described with reference to the accompanying drawings. [Brief description of the drawings]

[0013] [Figure 1] FIG. 1 illustrates an example communication environment in which example embodiments of the present disclosure may be implemented. [Diagram 2] FIG. 2 illustrates a signaling flow for QoE measurement, according to some example embodiments of the present disclosure. [Diagram 3] FIG. 2 illustrates a flowchart of a method for QoE measurement implemented in a first device, according to some example embodiments of the present disclosure. [Figure 4] FIG. 10 illustrates a flowchart of a method for QoE measurement implemented in a second device, according to some other example embodiments of the present disclosure. [Diagram 5] FIG. 1 illustrates a simplified block diagram of an apparatus suitable for practicing example embodiments of the present disclosure. [Figure 6]FIG. 1 illustrates a block diagram of an example computer-readable medium according to some example embodiments of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] Throughout the drawings, the same or similar reference numbers represent the same or similar elements.

[0015] The principles of the present disclosure will now be described with reference to some example embodiments. It should be understood that these embodiments are merely described for illustrative purposes, to assist those skilled in the art in understanding and implementing the present disclosure, but do not imply any limitations on the scope of the present disclosure. The embodiments described herein can be implemented in various ways other than those described below.

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

[0017] References in this disclosure to "one embodiment," "embodiment," "example embodiment," and the like indicate that the described embodiment may include a particular feature, structure, or characteristic, but not all embodiments need to include the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment. Moreover, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is believed to be within the knowledge of one of ordinary skill in the art that it affects the feature, structure, or characteristic associated with other embodiments, whether or not explicitly described.

[0018] Although the terms "first", "second", etc. may be used herein to describe various elements, it should be understood that these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first element can be referred to as a second element, and similarly, a second element can 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 of the listed terms.

[0019] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms unless the context clearly indicates otherwise. Furthermore, it is understood that the terms "comprises," "comprising," "having," "having," "includes," and / or "including," as 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.

[0020] As used in this application, the term "circuitry" may refer to one or more or all of the following: (a) Hardware-only circuit implementation (e.g., implementation in analog and / or digital circuitry only). (b) A combination of hardware circuitry and software, such as (where applicable) (i) A combination of analog and / or digital hardware circuitry(s) and software / firmware; (ii) Any portion of hardware processor(s) (including digital signal processor(s)), software, and memory(s) along with software that work together to cause a device such as a mobile phone or server to perform various function(s). (c) Hardware circuitry(s) and / or processor(s), such as a microprocessor(s) or part of a microprocessor(s), that requires software (e.g., firmware) for operation, although software may not be present if it is not necessary for operation.

[0021] This definition of circuitry applies to all uses of the term in this application, including any claims. As a further example, the term circuitry, as used in this application, also encompasses merely a hardware circuit or processor (or processors), or a portion of a hardware circuit or processor, and its (or their) associated software and / or firmware implementations. The term circuitry also encompasses, for example, baseband or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or network devices, if applicable to certain claim elements.

[0022] As used herein, the term "communication network" refers to a network conforming to any suitable communication standard, such as New Radio (NR), New Radio-Advanced (NR-A), Long Term Evolution (LTE), LTE Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. Furthermore, communication between terminal devices and network devices in the communication network may be performed according to any suitable generation of communication protocols, including, without limitation, first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G) communication protocols, and / or any other protocols now known or later developed. The embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communication, it is to be understood that there are also further future communication technologies and systems in which the present disclosure may be embodied. The scope of the present disclosure should not be considered as being limited to only the aforementioned systems.

[0023] As used herein, the term "network device" refers to a node in a communication network. Through the node, a terminal device accesses the network and receives services therefrom. A network device may refer to the following, depending on the terminology and technology applied: a base station (BS) or an access point (AP), e.g., a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), an NR NB (also called gNB), a remote radio unit (RRU), a radio header (RH), a remote radio head (RRH), a relay, an integrated access backhaul (IAB) node, a low power node, e.g., a femto, a pico, a non-terrestrial based network (NTN) or a non-terrestrial based network device, e.g., a satellite network device, a low earth orbit (LEO) satellite and a geostationary earth orbit (GEO) satellite, an aircraft network device, etc. The term "terminal device" refers to any end device that may be capable of wireless communication. In the following description, the terms "terminal device", "terminal", "user equipment", and "UE" may be used interchangeably.

[0024] As mentioned before, it is important to measure the quality of communication. Quality of Experience (QoE) is a measure of the pleasure or discomfort of a customer's experience with a service (e.g. web browsing, telephone call, TV broadcast). QoE considers the user's expectations, while QoS is more rational, based on technical measurements. QoE focuses on the whole service experience. It is a holistic concept, similar to the field of user experience, but has its origins in telecommunications.

[0025] As a measure of end-to-end performance at the service level from the user's point of view, QoE is an important metric for the design of systems and engineering processes. It is particularly relevant for video services, since due to their high traffic demand, poor network performance can greatly affect the user's experience. Therefore, when designing a system, the expected output (i.e., expected QoE) is often considered as a system output metric and also as an optimization goal. QoE metrics are often measured at the end device and can be conceptually considered as the remaining quality after distortions introduced during the content preparation and distribution through the network until it reaches the decoder at the end device. There are several elements in the media preparation and distribution chain, some of which may introduce distortions. This causes degradation of the content, and some elements in this chain can be considered "QoE relevant" for the service offered. The sources of degradation are applicable to any multimedia service, i.e., not limited to video or audio. Typical impairments occur in the encoding system (compression degradation), the transport network, the access network (eg, packet loss or packet delay), the home network (eg, WiFi performance), and the end device (eg, decoding performance).

[0026] Furthermore, a QoE Measurement Collection (QMC) mechanism is being standardized that enables collection of application layer measurements from the UE. Furthermore, configuration, activation and deactivation procedures are proposed for both signaling-based and management-based QoE measurement collection and reporting.

[0027] For the NR / LTE QoE Measurement Collection (QMC) mechanism, there is the required air interface support (coordination between the UE and the gNB) as well as internal coordination in the UE (between the access layer and the application layer of the UE). For the air interface, an RRC downlink message is designed to configure the UE (e.g., an RRC reconfiguration message) and an RRC uplink message (e.g., a MeasReportAppLayer message) is designed to transmit the QoE measurement report data container from the UE AS to the RAN node. The general understanding is that the Radio Access Network (RAN) node should not be required to decode the container included in the MeasReportAppLayer message, and the RAN node only forwards the QoE configuration as a transparent container. For NR QoE support in the RAN, since multiple QoE measurements for one service type are allowed to be configured for one specific UE, it was agreed to add an RRC short identity (ID) in the MeasReportAppLayer message to help the gNB identify the QoE report from the UE. However, the association of the UE configuration at the RRC layer (between the UE and the gNB) does not allow identifying the configuration at the UE application layer, and it is not known which configuration was originally associated with the report.

[0028] Currently, the QoE Reference ID may be used to identify the QoE measurement collection jobs in the traffic nodes and the measurement collection centers. Thus, it is envisioned to link QMC requests / configurations from the management system (e.g., Network Manager (NM)) to the gNB, UE Access Stratum (AS), and UE applications, and link QMC reports from the UE applications to the UE AS, gNB, and Multi-Broadcast Multi-Service (MBMS) Coordination Entity (MCE). Replacing the QMC Reference ID with the RRC ID in the AS signaling may break the QMC request and report chains, as well as the links between requests and reports.

[0029] Furthermore, reports may be provided by the application layer to the access stratum layer, but due to the avoidance of transparency and over-the-air QoE reference IDs, it is unknown which individual configuration triggered the report. Therefore, some ongoing sessions at the application layer have no tracked identity and no unspecified reference. In particular, during cell reselection / handover or other possible one UE to multiple gNB scenarios, potential overlapping RRC IDs may be configured on a single UE by different gNBs of the same or different PLMNs, which creates a problem for the UE to forward the QoE report back to the gNB that sent the QMC configuration to the UE.

[0030] A new solution to QoE measurement is needed. According to the embodiments of the present disclosure, the terminal device can coordinate between the access layer and the application layer to associate the QoE configuration with the corresponding report, thus enabling the unique identification of a single QoE configuration and the corresponding QoE report at the terminal device.

[0031] 1 illustrates a schematic diagram of a communication environment 100 in which embodiments of the present disclosure may be implemented. The communication environment 100 is part of a communication network and further includes device 110-1, device 110-2, ...., device 110-N, which may be collectively referred to as "first device(s) 110." The communication environment 100 includes a second device 120. The number N may be any suitable integer.

[0032] The communication environment 100 may include any suitable number of devices and cells. In the communication environment 100, the first device 110 and the second device 120 may communicate data and control information with each other. If the first device 110 is a terminal device and the second device 120 is a network device, the link from the second device 120 to the first device 110 is referred to as a downlink (DL), while the link from the first device 110 to the second device 120 is referred to as an uplink (UL). The first device 110 may be configured with two or more cells.

[0033] It should be understood that the number of first devices and cells and their connections shown in Figure 1 are provided for illustrative purposes, without implying any limitation, and that communication environment 100 may include any suitable number of devices and networks adapted to implement embodiments of the present disclosure.

[0034] Communications in the communication environment 100 may be performed according to any suitable communications protocol(s), including, for example, without limitation, cellular communications protocols such as first generation (1G), second generation (2G), third generation (3G), fourth generation (4G), and fifth generation (5G), wireless local network communications protocols such as, for example, Institute for Electrical and Electronics Engineers (IEEE) 802.11, and / or any other protocols now known or hereafter developed. Furthermore, communications may utilize any suitable wireless communication technology, including, for example, without limitation, code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), frequency division duplex (FDD), time division duplex (TDD), multiple-input multiple-output (MIMO), orthogonal frequency division multiplexing (OFDM), discrete Fourier transform spread OFDM (DFT-s-OFDM), and / or any other technology now known or hereafter developed.

[0035] Exemplary embodiments of the present disclosure are described in detail below with reference to the accompanying drawings. Reference is now made to FIG. 2. FIG. 2 illustrates a signaling flow 200 for QoE measurement according to an exemplary embodiment of the present disclosure. For illustrative purposes, the signaling flow 200 is described with reference to FIG. 1. For illustrative purposes only, the signaling flow 200 may include a first device 110-1 and a second device 120. The first device 110-1 includes a first apparatus 210 implemented in an AS layer or an RRC layer. The first device 110-1 also includes a second apparatus 220 implemented in an application layer. The signaling flow 200 may also include other core network entities (e.g., MCE 240 and NM 230) not shown in FIG. 1.

[0036] The NM 230 may generate a QMC activation message. The QMC activation message may indicate a service. The QMC activation message may also include a container of QoE configurations for the service. In some embodiments, the QMC activation message may indicate a QoE Reference Identity for the QoE configuration. The NM 230 may send the QMC activation message to the second device 120 2005. The QMC activation message may include a container of QoE configurations. The QoE Reference Identity may be within the QMC message, but may be located outside the container of QoE configurations. The QoE configuration may include any metrics required for evaluation of the impact of the device on the user experience. For example, the QoE configuration may include a threshold for the delay of the service. Alternatively, the QoE configuration may include a threshold for the coverage of the service. In other embodiments, the QoE configuration may include a quality threshold for the service. It is noted that the QoE configuration may also include any suitable parameters.

[0037] The second device 120 may generate an RRC configuration based on the received QMC activation message (2010). The second device 120 may generate an ID (hereinafter referred to as a "first identity") in the RRC layer and may map the QoE reference identity to the first identity. In some embodiments, the first identity may be an RRC identifier. Alternatively, the first identity may be a measurement application layer identifier assigned by the RRC layer. In other embodiments, the first identity may be a container identifier.

[0038] The second device 120 sends (2015) an RRC configuration to the first apparatus 210. The RRC configuration includes a QoE configuration for the service and a first identity. The RRC configuration may indicate a service type for the service. In some embodiments, the RRC configuration may include two or more QoE configurations.

[0039] To enable differentiated treatment according to the requirements of each customer, 5G also supports the concept of network slicing. With slicing, Mobile Network Operators (MNOs) can consider customers, each with different service requirements. The service requirements specify which slice type each customer is eligible to use, based on the Service Level Agreement (SLA) and subscription. Support for network slicing relies on the principle that traffic for different slices is handled by different PDU sessions. A network can realize different network slices by scheduling and by providing different configurations. A service type identified for the purpose of slicing is characterized by a slice identifier: S-NSSAI (Single Network Slice Selection Assistance Information), which consists of a slice / service type (SST) and optionally a slice differentiator (SD). Some typical standardized SST values ​​defined for the purpose of establishing global interoperability for slicing (so that PLMNs can more efficiently support roaming use cases for the most commonly used slices / service types) are specified as follows: [Table 1]

[0040] The embodiments of the present disclosure can be applied to slices. For example, the RRC configuration can include a QoE configuration for a slice. In an example embodiment, the RRC configuration may indicate a type of slice. The slice type can be represented by one of a slice identifier, slice assistance information, or a slice group identifier.

[0041] The first device 210 determines (2020) an associated identity (hereinafter "second identity") for the QoE configuration based at least in part on the first identity. In some embodiments, the first device 210 may determine the first identity to be the second identity. In other embodiments, the first device 210 may determine the second identity based on the first identity and other identity information. For example, the second identity may be generated based on the first identity and a cell identity of the second device 120. In this manner, the QoE configuration may be uniquely identified in the first device 110-1. Furthermore, it may reduce the length of the identity.

[0042] In some embodiments, the first device 210 may receive a further QoE configuration for the service from a further network device, in which case the first device 210 may generate a further associated identity for the further QoE configuration.

[0043] In addition, the first device 210 may store a mapping between the second identity and the second device 120. For example, the first device 210 may create a record in a mapping table to map the second identity to the second device 120. As mentioned above, the first device 210 may generate a further associated identity for the further QoE configuration. In this situation, the first device 210 may store a mapping between the further associated identity and the further network device.

[0044] The first device 210 sends (2025) the QoE configuration together with the second identity to the second device 220. For example, the QoE configuration and the second identity may be sent in an AT command +CAPPLEVMC. The AT command +CAPPLEVMC may indicate a service type. The AT command +CAPPLEVMC may include a container for the QoE configuration. In this way, the QoE configuration can be distinguished from other QoE configurations associated with the service.

[0045] The second device 220 may measure the service based on the QoE configuration. For example, the second device 220 may measure the service according to the metrics in the QoE configuration.

[0046] In some embodiments, the second device 220 may associate the QoE configuration in the first device 210 with the QoE configuration in the second device 220. For example, the second device 220 may store a mapping between a second identity and an identity of the second device 220 (such as an application layer identity).

[0047] The second device 220 generates (2030) a QoE report based on the QoE configuration. In some embodiments, the QoE report may be generated periodically. Alternatively, the QoE report may be generated based on any suitable trigger condition. The second device 220 may associate a second identity with the QoE report. In addition, the QoE report may be generated with an association to an application layer identity. In this way, the application layer can distinguish between different QoE configurations for the same service.

[0048] The second device 220 sends (2035) the QoE report together with the second identity to the first device 210. For example, the QoE report and the second identity may be sent in an AT command +CAPPLEVMR. The AT command +CAPPLEVMR may indicate a service type. The AT command +CAPPLEVMR may include a container for the QoE report. The container for the QoE report may include QoE measurement results.

[0049] In some embodiments, the first device 210 may determine the device to which the QoE report is forwarded based on the second identity (2040). In some embodiments, the first device 210 may determine the device based on the mapping table described above. For example, if the QoE report is with a second identity and the second identity is mapped to the first identity, the first device 210 may determine that the QoE is sent to the second device 120 based on the first identity. Alternatively, if the QoE report is with a further associated identity and the further associated identity is mapped to a further first identity, the first device 210 may determine that the QoE is sent to a further network device based on the further first identity.

[0050] The first device 210 may send (2045) the QoE report along with the first identity to the second device 120. As described above, if the QoE report has the second identity and the second identity is mapped to the first identity, the first device 210 may send the QoE report to the second device 120. In this case, the QoE report may include the first identity received from the second device 120.

[0051] The second device 120 may identify a QoE Reference Identity based on the first identity (2050). For example, the second device 120 may map the first identity to the QoE Reference Identity. The second device 120 may send a QoE report to the MCE 240 along with the QoE Reference Identity (2055). For example, a container of QoE reports including QoE measurement results may be sent to the MCE 240.

[0052] The second device 120 may release 2060 the UE context for the QoE measurements. The second device 120 may send 2065 another RRC message to the first apparatus 210 to release the QoE configuration. In some embodiments, the second device 120 may release multiple application layer measurement configurations in one RRC message at any point in time. The other RRC message may include a release indication. In other embodiments, the other RRC message may indicate a service type. The other RRC message may include the first identity. Alternatively or in addition, the other RRC message may include a container for the QoE configuration.

[0053] The first device 210 may determine a second identity for the QoE configuration based at least in part on the first identity indicated in the other RRC message. For example, if the first device 210 has stored a mapping between the first identity and the second identity, the first device 210 may find or derive the second identity based on the first identity and the stored mapping. In some embodiments, the first device 210 may determine that the second identity is the first identity. In other embodiments, the first device 210 may determine the second identity based on the first identity and other identity information. For example, the other identity information may be the cell identity of the second device 120. In this manner, the QoE configuration may be uniquely identified in the first device 110-1.

[0054] The first device 210 may send the QoE configuration and the release indication together with the second identity to the second device 220 (2070). For example, the QoE configuration, the second identity, and the release indication may be sent in an AT command +CAPPLEVMC. The AT command +CAPPLEVMC may indicate a service type. The AT command +CAPPLEVMC may include a container of the QoE configuration. The second device 220 may terminate the QoE measurement according to the second identity (2075).

[0055] The above embodiment enables unique tracking and identification of QoE measurement configurations and reporting across different layers or network entities in the UE, potentially handling multiple QoE configurations of the same service type with different purposes and use cases (e.g., different analysis requirements). In this implementation, a global unique QoE Reference ID can link QMC configurations and reports on the network side, while the global unique associated ID is used to coordinate QMC configurations and reports on the UE side, and finally complete the end-to-end QMC procedure without mismatch.

[0056] 3 illustrates a flowchart of an example method 300 according to some example embodiments of the present disclosure. For illustrative purposes, the method 300 is described from the perspective of a first device. For illustrative purposes only, the method 300 is described with reference to a first apparatus 210 implemented in a first device 110-1.

[0057] In block 310, the first apparatus 210 receives an RRC configuration from the second device 120. The RRC configuration includes a QoE configuration and a first identity for a service. The RRC configuration may indicate a service type. In some embodiments, the RRC configuration may include two or more QoE configurations.

[0058] At block 320, the first device 210 determines a second identity for the QoE configuration based at least in part on the first identity. In some embodiments, the first device 210 may determine the first identity to be the second identity. In other embodiments, the first device 210 may determine the second identity based on the first identity and other identity information. For example, the second identity may be generated based on the first identity and a cell identity of the second device 120. In this manner, the QoE configuration may be uniquely identified in the first device 110-1.

[0059] In some embodiments, the first device 210 may receive a further QoE configuration for the service from a further network device, in which case the first device 210 may generate a further associated identity for the further QoE configuration.

[0060] In addition, the first device 210 may store a mapping between the second identity and the second device 120. For example, the first device 210 may create a record in a mapping table to map the second identity to the second device 120. As mentioned above, the first device 210 may generate a further associated identity for the further QoE configuration. In this situation, the first device 210 may store a mapping between the further associated identity and the further network device.

[0061] In block 330, the first device 210 sends the QoE configuration together with the second identity to the second device 220. For example, the QoE configuration and the second identity may be sent in an AT command +CAPPLEVMC. The AT command +CAPPLEVMC may indicate a service type. The AT command +CAPPLEVMC may include a container for the QoE configuration.

[0062] In block 340, the first device 210 receives a QoE report together with a second identity from the second device 220. For example, the QoE report and the second identity may be received in an AT command +CAPPLEVMR. The AT command +CAPPLEVMR may indicate a service type. The AT command +CAPPLEVMR may include a container for the QoE report. The container for the QoE report may include QoE measurement results.

[0063] In some embodiments, the first device 210 may determine the device to which the QoE report is forwarded based on the second identity. In some embodiments, the first device 210 may determine the device based on the mapping table described above. For example, if the QoE report has a second identity and the second identity is mapped to the first identity, the first device 210 may determine that the QoE is sent to the second device 120 based on the first identity. Alternatively, if the QoE report has a further associated identity and the further associated identity is mapped to a further first identity, the first device 210 may determine that the QoE is sent to a further network device based on the further first identity.

[0064] The first device 210 may send the QoE report together with the first identity to the second device 120. As mentioned above, if the QoE report has the second identity and the second identity is mapped to the first identity, the first device 210 may send the QoE report to the second device 120. In this case, the QoE report may include the first identity received from the second device 120.

[0065] In some embodiments, the first apparatus 210 may receive another RRC message from the second device 120 to release the QoE configuration. The other RRC message may include a release indication. In other embodiments, the other RRC message may indicate a service type. The other RRC configuration message may include the first identity. Alternatively or in addition, the other RRC message may include a container of the QoE configuration.

[0066] The first device 210 may determine a second identity for the QoE configuration based at least in part on the first identity indicated in the other RRC message. For example, if the first device 210 has stored a mapping between the first identity and the second identity, the first device 210 may find or derive the second identity based on the first identity and the stored mapping. In some embodiments, the first device 210 may determine that the second identity is the first identity. In other embodiments, the first device 210 may determine the second identity based on the first identity and other identity information. For example, the other identity information may be the cell identity of the second device 120. In this manner, the QoE configuration may be uniquely identified in the first device 110-1.

[0067] Alternatively or in addition, the first device 210 may send the QoE configuration and the release indication together with the second identity to the second device 220. For example, the QoE configuration, the second identity, and the release indication may be sent in an AT command +CAPPLEVMC. The AT command +CAPPLEVMC may indicate a service type. The AT command +CAPPLEVMC may include a container of the QoE configuration.

[0068] 4 illustrates a flowchart of an example method 400 according to some example embodiments of the present disclosure. For purposes of explanation, the method 400 is described from the perspective of a first device. For purposes of explanation only, the method 400 is described with reference to a second apparatus 220 implemented in the first device 110-1.

[0069] In block 410, the second device 220 receives the QoE configuration together with the second identity from the first device 210. For example, the QoE configuration and the second identity may be received in an AT command +CAPPLEVMC. The AT command +CAPPLEVMC may indicate a service type. The AT command +CAPPLEVMC may include a container for the QoE configuration.

[0070] The second device 220 may measure the service based on the QoE configuration. For example, the second device 220 may measure the service according to the metrics in the QoE configuration.

[0071] In some embodiments, the second device 220 may associate the QoE configuration in the first device 210 with the QoE configuration in the second device 220. For example, the second device 220 may store a mapping between a second identity and an identity of the second device 220 (such as an application layer identity).

[0072] At block 420, the second device 220 generates a QoE report based on the QoE configuration. In some embodiments, the QoE report may be generated periodically. Alternatively, the QoE report may be generated based on any suitable trigger condition. The second device 220 may associate a second identity with the QoE report. In addition, the QoE report may be generated with an association to an application layer identity. In this way, the application layer can distinguish between different QoE configurations for the same service.

[0073] In block 430, the second device 220 sends the QoE report together with the second identity to the first device 210. For example, the QoE report and the second identity may be sent in an AT command +CAPPLEVMR. The AT command +CAPPLEVMR may indicate a service type. The AT command +CAPPLEVMR may include a container for the QoE report. The container for the QoE report may include QoE measurement results.

[0074] The second device 220 may receive the QoE configuration and the release indication together with the second identity from the first device 210. For example, the QoE configuration, the second identity, and the release indication may be sent in an AT command +CAPPLEVMC. The AT command +CAPPLEVMC may indicate a service type. The AT command +CAPPLEVMC may include a container of the QoE configuration. The second device 220 may terminate the QoE measurement according to the second identity.

[0075] In some example embodiments, an apparatus (e.g., the first device 110) capable of performing the method 300 may include means for performing each operation of the method 300. The means may be implemented in any suitable form. For example, the means may be implemented in a circuit or a software module. The apparatus may be implemented as or included in the first device 110. In some example embodiments, the means may include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to cause execution of the apparatus using the at least one processor.

[0076] In some example embodiments, the apparatus includes means for receiving a radio resource control (RRC) configuration from a device indicating a first identity and a quality of experience (QoE) configuration for the service, means for determining a second identity for the QoE configuration based at least in part on the first identity, means for sending the QoE configuration along with the second identity to the second device, and means for receiving a QoE report for the service along with the second identity from the second device.

[0077] In some example embodiments, the means for determining a second identity for the QoE configuration includes means for determining the first identity to be the second identity.

[0078] In some example embodiments, the means for determining a second identity for the QoE configuration includes means for determining the second identity based on the first identity and the other identity information.

[0079] In some example embodiments, the apparatus includes means for storing a mapping between the second identity and the device.

[0080] In some example embodiments, the apparatus includes means for determining a device to which the QoE report is forwarded based on the second identity, and means for sending the QoE report to the device along with the first identity.

[0081] In some example embodiments, an apparatus (e.g., the first device 110) capable of performing the method 400 may include means for performing each operation 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. The apparatus may be implemented as or included in the first device 110. In some example embodiments, the means may include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to cause execution of the apparatus using the at least one processor.

[0082] In some example embodiments, the apparatus includes means for receiving a Quality of Experience (QoE) configuration for the service together with the second identity from the first apparatus, means for generating a QoE report for the service based on the QoE configuration, and means for sending the QoE report together with the second identity to the first apparatus.

[0083] In some example embodiments, the apparatus includes means for associating the second identity with an identity of the second device, and means for storing a mapping between the second identity and the identity of the second device.

[0084] In some example embodiments, the second identity is a Radio Resource Control (RRC) identity, or the second identity is generated based on the first identity and other identity information.

[0085] 5 is a simplified block diagram of a device 500 suitable for implementing example embodiments of the present disclosure. The device 500 may be provided to implement a communications device, such as the first device shown in FIG 1. As shown, the device 500 includes one or more processors 510, one or more memories 520 coupled to the processor 510, and one or more communications modules 540 coupled to the processor 510.

[0086] The communication module 540 is for bidirectional communication. The communication module 540 has one or more communication interfaces to 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 540 may include at least one antenna.

[0087] The processor 510 may be of any type suitable for a local technology network, including, 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 500 may have multiple processors, such as application specific integrated circuit chips time-slaved to a clock that synchronizes the main processor.

[0088] The memory 520 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) 524, electrically programmable read only memory (EPROM), flash memory, hard disks, compact disks (CDs), digital video disks (DVDs), optical disks, laser disks, and other magnetic and / or optical storage devices. Examples of volatile memories include, but are not limited to, random access memory (RAM) 522 and other volatile memories that will not persist while power is off.

[0089] The computer program 530 includes computer executable instructions that are executed by the associated processor 510. The program 530 may be stored in a memory, for example in the ROM 524. The processor 510 may load the program 530 into the RAM 522 to perform any suitable operation and processing.

[0090] The embodiment of the present disclosure may be implemented by a program 530 such that the device 500 may perform any process of the present disclosure, such as those described with reference to Figures 2 to 4. The embodiment of the present disclosure may also be implemented by hardware or a combination of software and hardware.

[0091] In some example embodiments, the program 530 may be tangibly contained in a computer readable medium that may be included in the device 500 (such as in the memory 520) or other storage device accessible by the device 500. The device 500 may load the program 530 from the computer readable medium into the RAM 522 for execution. The computer readable medium may include any type of tangible non-volatile storage, such as ROM, EPROM, flash memory, hard disks, CDs, DVDs, and other magnetic and / or optical storage devices. FIG. 6 shows an example of a computer readable medium 600 in the form of an optical storage disk. The computer readable medium has the program 530 stored thereon.

[0092] In general, 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 illustrated and described as block diagrams, flow charts, or using some other graphical representations, it should be understood that the blocks, apparatus, systems, techniques, or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or controller, or other computing device, or some combination thereof.

[0093] 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 within a device on a target physical or virtual processor to perform any of the methods described above with reference to Figures 2-4. 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. Machine-executable instructions for program modules may be executed within local or distributed devices. In a distributed device, program modules may be located in both local and remote storage media.

[0094] The program codes for carrying out the methods of the present disclosure 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 apparatus, and when executed by the processor or controller, the functions / operations specified in the flowcharts and / or block diagrams are performed. The program codes may be executed 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.

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

[0096] The computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium.The computer-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the above.More specific examples of the computer-readable storage medium include an electrical connection with 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0097] Furthermore, although operations are shown in a particular order, this should not be understood as requiring such operations to be performed in the particular order or sequence shown, or to perform all of the illustrated operations, in order to achieve desired results. In certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although details of certain specific implementations are included in the foregoing description, these should not be construed as limitations on the scope of the disclosure, but rather as descriptions of features that may be specific to certain embodiments. Certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable subcombination.

[0098] Although the present disclosure has been described in language specific to structural features and / or method acts, it is to be understood that the present disclosure as 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. 1. A first device, comprising: At least one processor; at least one memory containing computer program code; The at least one memory and the computer program code are adapted to cause the first device, using the at least one processor, to: receiving, at the device, a radio resource control (RRC) configuration indicating a first identity generated at an RRC layer and a quality of experience (QoE) configuration of the service; determining a second identity for the QoE configuration based at least in part on the first identity indicated in the RRC configuration; sending said QoE configuration together with said second identity to a second device; receiving a QoE report for the service from the second device together with the second identity; The first device is configured to cause

2. The at least one memory and the computer program code further configure the first device, using the at least one processor, to: The first device of claim 1 , configured to cause determining the second identity for the QoE configuration by determining the first identity to be the second identity.

3. The at least one memory and the computer program code further configure the first device, using the at least one processor, to: The first device of claim 1 , configured to cause determining the second identity for the QoE configuration by determining the second identity based on the first identity and other identity information.

4. The at least one memory and the computer program code further configure the first device, using the at least one processor, to: The first apparatus of claim 1 , configured to cause storing a mapping between the second identity and the device.

5. The at least one memory and the computer program code further configure the first device, using the at least one processor, to: determining the device to which the QoE report is to be forwarded based on the second identity; sending the QoE report together with the first identity to the device; The first device of claim 1 configured to cause

6. The first identity is RRC identifier, a measurement application layer identifier associated by the RRC layer; or Container identifier, The first device of claim 1 , comprising one of:

7. The first device according to any one of claims 1 to 6, wherein the first device is in a terminal device, the second device is in the terminal device, and the devices are network devices.

8. A second device, At least one processor; at least one memory containing computer program code; The at least one memory and the computer program code are adapted to cause the second device, using the at least one processor, to: receiving a quality of experience (QoE) configuration for a service together with a second identity from the first device; generating a QoE report for the service based on the QoE configuration; sending the QoE report together with the second identity to the first device; The second device is configured to cause

9. The at least one memory and the computer program code further configure the second device, using the at least one processor, to: associating the second identity with an identity of the second device; storing a mapping between the second identity and the identity of the second device; The second device of claim 8 configured to cause

10. the second identity is a first identity generated in a Radio Resource Control (RRC) layer, or The second device of claim 8 , wherein the second identity is determined based on the first identity and other identity information.

11. The second device according to any one of claims 8 to 10, wherein the first device is in a terminal device and the second device is in the terminal device.

12. 1. A method comprising: In the first apparatus, a radio resource control (RRC) configuration, the first identity being generated in an RRC layer, and a quality of experience (QoE) configuration of the service are received from the device. receiving the indicating radio resource control (RRC) configuration; determining a second identity for the QoE configuration based at least in part on the first identity indicated in the RRC configuration; sending said QoE configuration together with said second identity to a second device; receiving a QoE report for the service from the second device together with the second identity; The method comprising:

13. Determining the second identity for the QoE configuration comprises: The method of claim 12 , comprising determining the first identity to be the second identity.

14. Determining the second identity for the QoE configuration comprises: The method of claim 12 , comprising determining the second identity based on the first identity and other identity information.

15. The method of claim 12 , further comprising storing a mapping between the second identity and the device.

16. determining the device to which the QoE report is to be forwarded based on the second identity; sending the QoE report together with the first identity to the device; The method of claim 12 further comprising:

17. The first identity is RRC identifier, a measurement application layer identifier associated by the RRC layer; or Container identifier, The method of claim 12, comprising one of:

18. The method according to any one of claims 12 to 17, wherein the first device is in a terminal device, the second device is in the terminal device and the devices are network devices.

19. 1. A method comprising: receiving, at the second device, from the first device, a quality of experience (QoE) configuration for the service together with the second identity; generating a QoE report for the service based on the QoE configuration; sending the QoE report together with the second identity to the first device; The method comprising:

20. associating the second identity with an identity of the second device; storing a mapping between the second identity and the identity of the second device; 20. The method of claim 19, further comprising:

21. the second identity is a first identity generated in a Radio Resource Control (RRC) layer, or The method of claim 19 , wherein the second identity is determined based on the first identity and other identity information.

22. The method according to any one of claims 19 to 21, wherein the first device is located in a terminal device and the second device is located in the terminal device.

23. An apparatus comprising: Means for receiving, in a first apparatus, a radio resource control (RRC) configuration from a device, the radio resource control (RRC) configuration indicating a first identity and a quality of experience (QoE) configuration of the service generated in an RRC layer; means for determining a second identity for the QoE configuration based at least in part on the first identity indicated in the RRC configuration; means for transmitting said QoE configuration together with said second identity to a second device; means for receiving a QoE report of the service together with the second identity from the second device; The apparatus comprising:

24. An apparatus comprising: Means for receiving, in the second device, from the first device, a Quality of Experience (QoE) configuration of the service together with the second identity; means for generating a QoE report for said service based on said QoE configuration; means for transmitting the QoE report together with the second identity to the first device; The apparatus comprising:

25. A computer readable medium comprising program instructions for causing an apparatus to perform the method of any one of claims 12 to 18 or any one of claims 19 to 22.

26. A device, comprising: Means for carrying out the method according to any one of claims 11 to 16, Means for carrying out the method according to any one of claims 17 to 20, The device comprising:

Citation Information

Patent Citations

  • Quality of service information notification to user equipment, users, and application server

    US20200112907A1

  • Technique for reporting quality of experience (QOE) - and application layer (AL) measurements at high load

    WO2021028397A1