Experience Quality Measurement

Abstract

This provides a novel method for estimating the downlink size for Quality of Experience (QoE) measurements. [Solution] According to embodiments of the present disclosure, a terminal device can coordinate between the access layer and the application layer to associate a QoE configuration with a corresponding report. In this way, unique identification of a single QoE configuration and corresponding QoE reporting on the terminal device become possible.

Description

Technical Field

[0001] Embodiments of the present disclosure generally relate to the field of telecommunication, and more particularly, to methods, devices, apparatuses, and computer-readable storage media for Quality of Experience (QoE) measurement.

Background Art

[0002] With the development of communication technologies, several solutions have been proposed to provide efficient and reliable solutions 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 technology 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. The Quality of Experience (QoE) of user perception using multimedia services and applications highly depends on QoS parameters. It is worth considering measuring QoE in a more efficient way.

Summary of the Invention

[0003] Generally, embodiments of the present disclosure provide solutions for QoE measurement.

[0004] In a first embodiment, a first device is provided. The first device includes at least one processor and at least one memory containing computer program code, the at least one memory and the computer program code are configured to cause the first device to use the at least one processor to: receive from a device a radio resource control (RRC) configuration which indicates a first identity generated at the RRC layer and a quality of service (QoE) configuration; determine a second identity for a 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 device; and receive a QoE report for a service together with the second identity from the second device.

[0005] In a second embodiment, a second device is provided. The second device includes at least one processor and at least one memory containing computer program code, wherein the at least one memory and the computer program code are configured to cause the second device to use the at least one processor to receive a Quality of Service (QoE) configuration along with a second identity from the first device, generate a QoE report for the service based on the QoE configuration, and transmit the QoE report along with the second identity to the first device.

[0006] In a third aspect, a method is provided. The method includes, in a first device, receiving a radio resource control (RRC) configuration from a device, which indicates a first identity generated at the RRC layer and a quality of service (QoE) configuration; 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 device; and receiving a QoE report for the service together with the second identity from the second device.

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

[0008] In a fifth aspect, an apparatus is provided. The apparatus includes, in a first apparatus, means for receiving from a device a radio resource control (RRC) configuration which indicates a first identity and a quality of service (QoE) configuration generated at the RRC layer; means for determining a second identity for a 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 a QoE report for a service together with the second identity from the second apparatus.

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

[0010] In the seventh aspect, a computer-readable medium is provided. The computer-readable medium includes program instructions for causing the device to perform at least one of the methods described in the third or fourth aspect above.

[0011] It should be understood that the Summary section is not intended to identify any material or essential features of the embodiments of this disclosure, nor is it intended to be used to limit the scope of this disclosure. Other features of this disclosure will be readily apparent through the following description.

[0012] Next, several examples of embodiments will be described with reference to the attached drawings. [Brief explanation of the drawing]

[0013] [Figure 1] This figure illustrates an example of a communication environment in which the embodiments of this disclosure can be implemented. [Figure 2] This figure illustrates the signaling flow for QoE measurement according to some embodiments of the present disclosure. [Figure 3] This figure illustrates a flowchart of a method for QoE measurement performed in a first apparatus according to some embodiments of the present disclosure. [Figure 4] This figure illustrates a flowchart of a method for QoE measurement performed in a second apparatus according to some other embodiments of the present disclosure. [Figure 5] This figure illustrates a simplified block diagram of an apparatus suitable for carrying out an embodiment of the present disclosure. [Figure 6]This figure illustrates block diagrams of computer-readable media examples according to some embodiments of the present disclosure. [Modes for carrying out the invention]

[0014] Throughout the drawing, identical or similar reference figures represent identical or similar elements.

[0015] Next, the principles of this disclosure will be described with reference to several examples of embodiments. These embodiments are provided for illustrative purposes only and are intended to help those skilled in the art understand and implement this disclosure, but should not be considered to imply any limitation on the scope of this disclosure. The embodiments described herein can be implemented in a variety of ways other than those described below.

[0016] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meanings as those broadly understood by those skilled in the art to which this disclosure belongs.

[0017] References in this disclosure such as “one embodiment,” “embodiment,” and “example embodiment” indicate that the described embodiment may include certain features, structures, or characteristics, but not all embodiments are required to include such features, structures, or characteristics. Furthermore, such phrases do not necessarily refer to the same embodiment. Moreover, if certain features, structures, or characteristics are described in relation to an embodiment, it is considered within the knowledge of those skilled in the art that they may affect features, structures, or characteristics related to other embodiments, whether explicitly described or not.

[0018] In this specification, terms such as “first,” “second,” etc., may be used to describe various elements, but it should be understood that these elements should not be limited by these terms. These terms are used solely to distinguish one element from another. For example, without departing from the scope of the embodiments, the first element can be called the second element, and similarly, the second element can be called the first element. As used herein, the term “and / or” includes any and all combinations of one or more of the enumerated terms.

[0019] The terms used herein are for the sole purpose of describing specific embodiments and are not intended to limit the embodiments. Where used herein, the singular forms "a," "an," and "the" are intended to include the plural form unless the context clearly indicates a different meaning. Furthermore, the terms "comprises," "comprising," "have," "includes," and / or "including," where used herein, specify the presence of the described features, elements, and / or components, but are understood not to 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 “circuit” may refer to one or more or all of the following: (a) Circuit implementations dedicated to hardware (such as implementations in analog and / or digital circuits only). (b) A combination of hardware circuitry and software, for example (if applicable), (i) A combination of analog and / or digital hardware circuits(s) and software / firmware, (ii) Any part of a hardware processor(s) (including a digital signal processor(s)) with software that operates together to cause a device such as a mobile phone or server to perform various functions (multiple possible), the software, and the memory(ies). (c) A hardware circuit(s) and / or processor(s) such as a microprocessor(s) or a part of a microprocessor(s) that requires software (e.g., firmware) for operation. However, the software may not exist if it is not necessary for operation.

[0021] This definition of circuit applies to all uses of this term in this application, including any claim. As a further example, when used in this application, the term circuit includes just a hardware circuit or processor (or processors), or a part of a hardware circuit or processor, and its (or their) accompanying software and / or firmware embodiments. The term circuit includes, for example, a baseband integrated circuit or a processor integrated circuit for a mobile device, or a similar integrated circuit in a server, a cellular network device, or other computing or network devices, if applicable to the components of a particular claim.

[0022] As used herein, the term “communication network” refers to a network conforming to any preferred communication standard, such as New Radio (NR), New Radio-Advanced (NR-A), Long-Term Evolution (LTE), LTE Advanced (LTE-A), Broadband Code Division Multiple Access (WCDMA®), High-Speed ​​Packet Access (HSPA), and Narrowband Internet of Things (NB-IoT). Furthermore, communication between terminal devices and network devices in a communication network may be conducted according to any preferred generation of communication protocol, including, but not limited to, first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G) communication protocols, and / or any other protocols currently known or to be developed in the future. Embodiments of this disclosure may be applied to various communication systems. Given the rapid development in communications, there will naturally be further futuristic communication technologies and systems that can embody this disclosure. This disclosure should not be considered to be limited to the aforementioned systems only.

[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. The network device may refer to the following according to the applied terminology and technology. That is, a base station (BS) or an access point (AP), for example, Node B (NodeB or NB), evolved Node B (eNodeB or eNB), NR NB (also called gNB), remote radio unit (RRU), radio header (RH), remote radio head (RRH), relay, integrated access backhaul (IAB) node, low power node, for example, femto, pico, non-terrestrial network (NTN) or non-terrestrial network device, for example, satellite network device, low earth orbit (LEO) satellite and geostationary earth orbit (GEO) satellite, 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 described above, it is important to measure communication quality. Quality of Experience (QoE) is a measure of the pleasure or displeasure of a customer's experience with a service (for example, web browsing, phone call, TV broadcast). QoE takes into account the user's expectations, while QoS is more rational based on technical measurements. QoE focuses on the overall service experience. It is a holistic concept similar to the field of user experience, but its origin is in telecommunications.

[0025] As a measure of end-to-end performance in terms of service levels from the user's perspective, QoE is an important metric for the design of systems and engineering processes. This is particularly relevant to video services because, due to their high traffic demands, poor network performance can significantly impact the user experience. Therefore, when designing a system, the expected output (i.e., expected QoE) is often considered as a system output metric and optimization target. QoE metrics are often measured at the end device and can be conceptually thought of as the remaining quality after distortions introduced during content preparation and delivery over the network, up to the decoder at the end device. Several elements exist in the media preparation and delivery chain, some of which can introduce distortions. This causes content degradation, and some elements in this chain can be considered "QoE-related" to the service provided. The causes of degradation are applicable to any multimedia service, i.e., not limited to video or audio. Typical degradation occurs in the encoding system (compression degradation), the transport network, the access network (e.g., packet loss or packet delay), the home network (e.g., WiFi performance), and the end device (e.g., decoding performance).

[0026] Furthermore, a QoE measurement collection (QMC) mechanism has been standardized to enable the collection of application layer measurements from UEs. In addition, configuration, activation, and deactivation procedures have been 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 required air interface support (coordination between the UE and gNB), as well as internal coordination within the UE (between the UE's access layer and application layer). For the air interface, RRC downlink messages are designed to configure the UE (e.g., RRC reconfiguration messages), and RRC uplink messages (e.g., MeasReportAppLayer messages) are designed to send the QoE measurement report data container from the UE AS to the RAN node. The common understanding is that the Radio Access Network (RAN) node should not be required to decode the container contained in the MeasReportAppLayer message; the RAN node simply 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 configure for one particular UE, it was agreed to add an RRC short identity (ID) within the MeasReportAppLayer message to help the gNB identify the QoE report from the UE. However, the association of UE configurations in the RRC layer (between UE and gNB) does not allow for the identification of configurations in the UE application layer, making it impossible to know which configurations were originally associated with the report.

[0028] Currently, QoE reference IDs can be used to identify QoE measurement collection jobs at traffic nodes and measurement collection centers. Therefore, it is assumed that QMC requests / configurations from a management system (e.g., a network manager (NM)) are linked to the gNB, UE access layer (AS), and UE applications, and that QMC reports from UE applications are linked to the UE AS, gNB, and Multi-Broadcast Multi-Service (MBMS) Coordination Entity (MCE). Replacing the QMC reference ID with the RRC ID in AS signaling may disrupt the QMC request and report chain, as well as the links between requests and reports.

[0029] Furthermore, while reports can be provided to the access layer by the application layer, due to transparency and the avoidance of over-the-air QoE reference IDs, it is unknown which individual configuration triggered the report. Therefore, several ongoing sessions in the application layer lack tracked identities and unspecified references. In particular, during cell re-selection / handover or in other possible scenarios of multiple gNBs from one UE, potential duplicate RRC IDs may be configured on a single UE by different gNBs of the same or different PLMNs, causing the UE to forward and return QoE reports to the gNB that sent the QMC configuration to the UE.

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

[0031] Figure 1 illustrates a schematic diagram of a communication environment 100 in which an embodiment of the present disclosure can be implemented. The communication environment 100 is part of a communication network and further includes devices 110-1, 110-2, ..., and 110-N. These can be collectively referred to as the "first device(s) 110". The communication environment 100 also includes a second device 120. The number N can 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 can transmit data and control information to 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 called a downlink (DL), while the link from the first device 110 to the second device 120 is called an uplink (UL). The first device 110 can be composed of 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 given for illustrative purposes only and without any indication of limitation. The communication environment 100 may include any preferred number of devices and networks adapted to carry out embodiments of the present disclosure.

[0034] Communication in communication environment 100 may be carried out according to any suitable communication protocol(s). For example, this protocol includes, but is not limited to, cellular communication protocols such as first-generation (1G), second-generation (2G), third-generation (3G), fourth-generation (4G), and fifth-generation (5G), wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11, and / or any other protocol currently known or to be developed. Furthermore, communication may utilize any suitable wireless communication technology. For example, this wireless communication technology includes, but is not limited to, code division multiplexing access (CDMA), frequency division multiplexing access (FDMA), time division multiplexing access (TDMA), frequency division duplexing (FDD), time division duplexing (TDD), multiple input multiple output (MIMO), orthogonal frequency division multiplexing (OFDM), discrete Fourier transform spread OFDM (DFT-s-OFDM), and / or any other technology currently known or to be developed.

[0035] Examples of embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. Next, refer to Figure 2. Figure 2 illustrates a signaling flow 200 for QoE measurement according to an example of an embodiment of the present disclosure. For illustrative purposes, the signaling flow 200 will be described with reference to Figure 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 device 210 implemented in the AS layer or RRC layer. The first device 110-1 also includes a second device 220 implemented in the application layer. The signaling flow 200 may also include other core network entities not shown in Figure 1 (e.g., MCE240 and NM230).

[0036] NM230 may generate a QMC activation message. The QMC activation message may indicate a service. The QMC activation message may also include a QoE configuration container for the service. In some embodiments, the QMC activation message may indicate a QoE reference identity for the QoE configuration. NM230 can send the QMC activation message to a second device 120. The QMC activation message may include a QoE configuration container. The QoE reference identity may be within the QMC message, but may be placed outside the QoE configuration container. The QoE configuration may include any metrics necessary to evaluate the device's impact on the user experience. For example, the QoE configuration may include a threshold for service latency. Alternatively, the QoE configuration may include a threshold for service coverage. In other embodiments, the QoE configuration may include a quality of service threshold. Note that the QoE configuration may also include any appropriate 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 the "first identity") in the RRC layer and may map the QoE reference identity to the first identity. In some embodiments, the first identity can be an RRC identifier. Alternatively, the first identity can be a measurement application layer identifier assigned by the RRC layer. In other embodiments, the first identity can be a container identifier.

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

[0039] To enable differentiated treatment according to each customer's requirements, 5G also supports the concept of network slicing. Using slicing, mobile network operators (MNOs) can consider customers, each with different service requirements. Service requirements, based on service level agreements (SLAs) and subscriptions, define which slice type each customer is eligible to use. Support for network slicing relies on the principle that traffic for different slices is handled by different PDU sessions. Networks can implement different network slices through scheduling and by providing different configurations. Service types identified for the purpose of slicing are characterized by a slice identifier: S-NSSAI (Single Network Slice Selection Support Information). This consists of a slice / service type (SST) and optionally a slice differentiator (SD). Several typical standardized SST values ​​defined for the purpose of establishing global interoperability for slicing (so that PLMN can more efficiently support roaming use cases for the most commonly used slice / service types) are defined as follows: [Table 1]

[0040] Embodiments of this disclosure can be applied to slices. For example, the RRC configuration may include the QoE configuration of the slice. In the embodiment, the RRC configuration may indicate the type of slice. The slice type can be represented by one of the following: a slice identifier, slice support information, or slice group identifier.

[0041] The first device 210 determines an associated identity (hereinafter referred to as the "second identity") for the QoE configuration, at least in part, based on the first identity (2020). 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 can be generated based on the first identity and cell identity of the second device 120. In this way, the QoE configuration can 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 further QoE configurations for the service from further network devices. In this case, the first device 210 may generate further associated identities for the further QoE configurations.

[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 the mapping table for mapping the second identity to the second device 120. As mentioned above, the first device 210 may generate further associated identities for further QoE configurations. In this case, the first device 210 may store a mapping between the further associated identities and further network devices.

[0044] The first device 210 transmits the QoE configuration along with the second identity to the second device 220 (2025). For example, the QoE configuration and the second identity may be transmitted in an AT command +CAPPLEVMC. The AT command +CAPPLEVMC may indicate the service type. The AT command +CAPPLEVMC may contain 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 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 the second identity and the identity of the second device 220 (such as an application layer identity).

[0047] The second device 220 generates a QoE report based on the QoE configuration (2030). In some embodiments, the QoE report may be generated periodically. Alternatively, the QoE report can be generated based on any appropriate 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 the QoE report along with the second identity to the first device 210 (2035). For example, the QoE report and the second identity may be sent in the AT command +CAPPLEVMR. The AT command +CAPPLEVMR may indicate the service type. The AT command +CAPPLEVMR may include a container for the QoE report. The container for the QoE report may include the QoE measurement results.

[0049] In some embodiments, the first device 210 may determine which device the QoE report is forwarded to based on a second identity (2040). In some embodiments, the first device 210 can determine the device based on the mapping table described above. For example, if the QoE report is accompanied by a second identity and the second identity is mapped to a first identity, the first device 210 may determine that the QoE is sent to a second device 120 based on the first identity. Alternatively, if the QoE report is accompanied by 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 the QoE report along with the first identity to the second device 120 (2045). As described above, if the QoE report has a second identity and the second identity is mapped to the first identity, the first device 210 can 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 the 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 the QoE report along with the QoE reference identity to the MCE240 (2055). For example, a container of the QoE report containing the QoE measurement results can be sent to the MCE240.

[0052] The second device 120 may release the UE context for the QoE measurement (2060). The second device 120 may send another RRC message to the first device 210 to release the QoE configuration (2065). In some embodiments, the second device 120 may release multiple application layer measurement configurations in a single RRC message at any time. The other RRC message may include a release indication. In other embodiments, the other RRC message may indicate the 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 a QoE configuration based at least in part on a first identity indicated in another 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 could be the cell identity of the second device 120. In this way, the QoE configuration can be uniquely identified in the first device 110-1.

[0054] The first device 210 may transmit the QoE configuration and release indication along with the second identity to the second device 220 (2070). For example, the QoE configuration, the second identity, and the release indication may be transmitted in the AT command +CAPPLEVMC. The AT command +CAPPLEVMC may indicate the service type. The AT command +CAPPLEVMC may include a container for the QoE configuration. The second device 220 may terminate the QoE measurement by the second identity (2075).

[0055] According to the embodiments described above, unique tracking and identification of QoE measurement configurations and reporting across different layers or network entities of the UE become possible, potentially handling multiple QoE configurations of the same service type with different purposes and use cases (e.g., different analytical requirements). In this embodiment, a globally unique QoE reference ID allows linking of QMC configurations and reports on the network side, while a globally unique associated ID is used to coordinate QMC configurations and reports on the UE side, ultimately completing end-to-end QMC procedures without mismatches.

[0056] Figure 3 shows a flowchart of Method Example 300, based on several embodiments of the present disclosure. For illustrative purposes, Method 300 will be described in terms of the first device. For illustrative purposes only, Method 300 will be described with reference to the first apparatus 210 implemented in the first device 110-1.

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

[0058] In block 320, the first device 210 determines a second identity for a 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 can be generated based on the first identity and cell identity of the second device 120. In this way, the QoE configuration can be uniquely identified in the first device 110-1.

[0059] In some embodiments, the first device 210 may receive further QoE configurations for the service from further network devices. In this case, the first device 210 may generate further associated identities for the further QoE configurations.

[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 the mapping table for mapping the second identity to the second device 120. As mentioned above, the first device 210 may generate further associated identities for further QoE configurations. In this case, the first device 210 may store a mapping between the further associated identities and further network devices.

[0061] In block 330, the first device 210 transmits the QoE configuration along with the second identity to the second device 220. For example, the QoE configuration and the second identity may be transmitted in the AT command +CAPPLEVMC. The AT command +CAPPLEVMC may indicate the 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 from the second device 220 along with a second identity. For example, the QoE report and the second identity may be received in the AT command +CAPPLEVMR. The AT command +CAPPLEVMR may indicate the service type. The AT command +CAPPLEVMR may include a container for the QoE report. The container for the QoE report may include the QoE measurement results.

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

[0064] The first device 210 may send the QoE report along with the first identity to the second device 120. As described above, if the QoE report has a second identity and the second identity is mapped to the first identity, the first device 210 can 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 device 210 may receive other RRC messages 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 the service type. The other RRC configuration may message the first identity. Alternatively or in addition to that, the other RRC message may include a container for the QoE configuration.

[0066] The first device 210 may determine a second identity for a QoE configuration based at least in part on a first identity indicated in another 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 could be the cell identity of the second device 120. In this way, the QoE configuration can be uniquely identified in the first device 110-1.

[0067] Alternatively, or in addition to the above, the first device 210 may send the QoE configuration and release indication along 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 the AT command +CAPPLEVMC. The AT command +CAPPLEVMC may indicate the service type. The AT command +CAPPLEVMC may include a container for the QoE configuration.

[0068] Figure 4 shows a flowchart of Method Example 400, based on several embodiments of the present disclosure. For illustrative purposes, Method 400 will be described in terms of the first device. For illustrative purposes only, Method 400 will be described with reference to the second device 220 implemented in the first device 110-1.

[0069] In block 410, the second device 220 receives the QoE configuration along with the second identity from the first device 210. For example, the QoE configuration and the second identity may be received in the AT command +CAPPLEVMC. The AT command +CAPPLEVMC may indicate the 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 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 the second identity and the identity of the second device 220 (such as an application layer identity).

[0072] In 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 can be generated based on any appropriate 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 along with the second identity to the first device 210. For example, the QoE report and the second identity may be sent in the AT command +CAPPLEVMR. The AT command +CAPPLEVMR may indicate the service type. The AT command +CAPPLEVMR may include a container for the QoE report. The container for the QoE report may include the QoE measurement results.

[0074] The second device 220 may receive the QoE configuration and release indication along with the second identity from the first device 210. For example, the QoE configuration, the second identity, and the release indication may be transmitted in the AT command +CAPPLEVMC. The AT command +CAPPLEVMC may indicate the service type. The AT command +CAPPLEVMC may include a container for the QoE configuration. The second device 220 may terminate the QoE measurement by the second identity.

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

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

[0077] In some embodiments, means for determining a second identity for a QoE configuration include means for determining that the first identity is the second identity.

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

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

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

[0081] In some embodiments, an apparatus capable of performing Method 400 (for example, a first device 110) may include means for performing each operation of Method 400. The means may be implemented in any preferred form. For example, the means may be implemented in a circuit or a software module. The apparatus may be implemented as the first device 110 or may be included therein. In some embodiments, the means may include at least one processor and at least one memory containing computer program code. The at least one memory and the computer program code are configured to cause the apparatus to execute using at least one processor.

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

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

[0084] In some 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] Figure 5 is a simplified block diagram of a device 500 suitable for carrying out an embodiment of the present disclosure. The device 500 may be provided to implement a communication device, for example, a first device as shown in Figure 1. As shown, the device 500 includes one or more processors 510, one or more memories 520 coupled to the processors 510, and one or more communication modules 540 coupled to the processors 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 interfaces may represent any interfaces necessary for communication with other network elements. In some 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 and may include, in non-limiting examples, one or more of the following: a general-purpose computer, a dedicated computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multicore processor architecture. The device 500 may have multiple processors, such as application-specific integrated circuit chips that are time-dependent to a clock that synchronizes the main processor.

[0088] 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 discs (CDs), digital video discs (DVDs), optical discs, laser discs, 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 would not persist while the 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 memory, for example, ROM 524. The processor 510 may perform any preferred operations and processes by loading the program 530 into RAM 522.

[0090] Examples of embodiments of the present disclosure may be implemented by program 530 so that device 500 can perform any process of the present disclosure as described with reference to Figures 2-4. Examples of embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.

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

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

[0093] This disclosure also provides at least one computer program product tangibly stored on a non-temporary computer-readable storage medium. The computer program product includes computer-executable instructions, such as those contained within a program module, which are executed within a device on a target physical or virtual processor to perform one of the methods described above with reference to Figures 2-4. Generally, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform a specific task or implement a specific abstract data type. The functions of program modules may be combined or divided among program modules as needed in various embodiments. Machine-executable instructions for program modules may be executed within a local device or a distributed device. In a distributed device, program modules may reside on both local and remote storage media.

[0094] Program code for performing the methods disclosed herein may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, a dedicated computer, or other programmable data processing device, and when the program code is executed by the processor or controller, the functions / operations defined in the flowchart and / or block diagrams are performed. The program code may run entirely on a machine, partially on a machine as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0095] In the context of this disclosure, computer program code or related data may be carried by any suitable carrier so that a device, apparatus, or processor can perform the various processes and operations described above. Examples of carriers include signals and computer-readable media.

[0096] Computer-readable media may be computer-readable signal media or computer-readable storage media. Computer-readable media may include, without limitation, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any preferred combination thereof. More specific examples of computer-readable storage media include electrical connections having one or more wires, portable computer diskettes, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any preferred combination thereof.

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

[0098] While this disclosure has been described in language specific to structural features and / or method actions, it should be understood that the disclosure set forth in the attached claims is not necessarily limited to the specific features or actions described herein. Rather, the specific features and actions described herein are disclosed as exemplary forms of implementing the claims.

Claims

1. The first device, At least one processor, Includes at least one memory containing computer program code, The at least one memory and the computer program code are used by the at least one processor to send the first device to the first device. In a device, the device receives a radio resource control (RRC) configuration which indicates a first identity generated in the RRC layer and a quality of service (QoE) configuration. A second identity for the QoE configuration is determined based at least partially on the first identity indicated in the RRC configuration, The QoE configuration is transmitted to the second device along with the second identity. The second device receives the QoE report of the service along with the second identity, The first device is configured to perform the following action.

2. The at least one memory and the computer program code are further connected to the first device using the at least one processor. The first device according to claim 1, configured to determine 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 are further connected to the first device using the at least one processor. The first device according to claim 1, configured to determine 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 are further connected to the first device using the at least one processor. The first device according to claim 1, configured to store a mapping between the second identity and the device.

5. The at least one memory and the computer program code are further connected to the first device using the at least one processor. Based on the second identity, the device to which the QoE report is transferred is determined, Sending the QoE report along with the first identity to the device, The first apparatus according to claim 1, configured to perform the following:

6. The aforementioned first identity is, RRC identifier, The measurement application layer identifier associated with the RRC layer, or Container identifier, The first apparatus according to claim 1, comprising one of the following.

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

8. The second device, At least one processor, Includes at least one memory containing computer program code, The at least one memory and the computer program code are transmitted to the second device using the at least one processor. The first device receives the service experience quality (QoE) configuration along with the second identity, Based on the aforementioned QoE configuration, a QoE report for the service is generated. The first device is to transmit the QoE report along with the second identity, The second device, configured to perform the following action.

9. The at least one memory and the computer program code are further transmitted to the second device using the at least one processor. Associating the second identity with the identity of the second device, The mapping between the second identity and the identity of the second device is stored, The second apparatus according to claim 8, configured to perform the following:

10. The second identity is either the first identity generated in the Radio Resource Control (RRC) layer, or The second device according to 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 located in a terminal device, and the second device is located in the terminal device.

12. It is a method, In the first device, the device provides a Radio Resource Control (RRC) configuration, which includes a first identity generated at the RRC layer, and a Quality of Service (QoE) configuration. Receiving the aforementioned Radio Resource Control (RRC) configuration to indicate, A second identity for the QoE configuration is determined based at least partially on the first identity indicated in the RRC configuration, The QoE configuration is transmitted to the second device along with the second identity. The second device receives the QoE report of the service along with the second identity, The method, including the method described above.

13. Determining the second identity for the aforementioned QoE configuration is The method according to claim 12, comprising determining that the first identity is the second identity.

14. Determining the second identity for the aforementioned QoE configuration is The method according to claim 12, comprising determining the second identity based on the first identity and other identity information.

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

16. Based on the second identity, the device to which the QoE report is transferred is determined, Sending the QoE report along with the first identity to the device, The method according to claim 12, further comprising:

17. The aforementioned first identity is, RRC identifier, The measurement application layer identifier associated with the RRC layer, or Container identifier, The method according to claim 12, comprising one of the above.

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

19. It is a method, The second device receives the service experience quality (QoE) configuration along with the second identity from the first device, Based on the aforementioned QoE configuration, a QoE report for the service is generated. The first device is to transmit the QoE report along with the second identity, The method, including the method described above.

20. Associating the second identity with the identity of the second device, The mapping between the second identity and the identity of the second device is stored, The method according to claim 19, further comprising:

21. The second identity is either the first identity generated in the Radio Resource Control (RRC) layer, or The method according to 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. It is a device, In the first apparatus, means for receiving a radio resource control (RRC) configuration from a device, the RRC configuration being an RRC configuration that indicates a first identity and a quality of service (QoE) configuration generated in the RRC layer, A means for determining a second identity for the QoE configuration, based at least in part on the first identity indicated in the RRC configuration, The second device includes means for transmitting the QoE configuration along with the second identity, Means for receiving the QoE report of the service along with the second identity from the second device, The apparatus, including the above.

24. It is a device, The second device includes means for receiving the service quality of experience (QoE) configuration along with the second identity from the first device, A means for generating a QoE report for the service based on the QoE configuration, The first device includes means for transmitting the QoE report along with the second identity, The apparatus, including the above.

25. A computer-readable medium containing program instructions for causing a device to perform the method according to any one of claims 12 to 18 or any one of claims 19 to 22.

26. It is a device, Means for performing the method described in any one of claims 11 to 16, Means for carrying out the method described in any one of claims 17 to 20, The device, including the device.

Images