Prioritization settings for user experience quality
By introducing a QoE measurement priority setting mechanism in the new radio network, the problem of QoE report storms under overload was solved, ensuring the continuous transmission of high-priority reports and improving the load management capabilities of network devices.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-05-10
- Publication Date
- 2026-03-13
AI Technical Summary
In the new radio network, QoE measurement reports cannot be effectively controlled under overload conditions, leading to reporting storms and wasted resources, especially high-priority reports that cannot be delivered in a timely manner.
By establishing a priority setting mechanism for QoE measurements between user equipment and network equipment, instructions are generated based on the corresponding priority of QoE measurements to control the execution and suspension of QoE measurement reports, ensuring that high-priority reports are not interrupted under overload conditions.
It enables effective management of QoE measurement reports under overload conditions, ensures the continuous delivery of high-priority reports, reduces resource waste and report storms, and improves the load management capabilities of network devices.
Smart Images

Figure CN115918131B_ABST
Abstract
Description
Technical Field
[0001] Embodiments of this disclosure generally relate to the telecommunications field, and more particularly to devices, methods, apparatus, and computer-readable storage media for prioritizing Quality of Experience (QoE). Background Technology
[0002] QoE reflects user satisfaction with a service provider. QoE measurement is performed by the application layer of the user equipment (UE) and can refer to the service type. Configurations for QoE measurement can be specified for the UE.
[0003] Two QoE procedures are proposed for New Radio (NR): a signaling-based procedure and a management-based procedure. In the signaling-based procedure, the core network (CN) can initiate the activation of QoE measurements configured by the Operations and Maintenance (OAM) entity and send the QoE measurement configuration to the gNB. In the management-based procedure, the OAM entity can send the QoE measurement configuration to the gNB. Summary of the Invention
[0004] Overall, the example embodiments of this disclosure provide a solution for prioritizing QoE.
[0005] In a first aspect, a first device is provided. The first device includes 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 together with the at least one processor to cause the first device to at least: receive from a second device an indication associated with reporting at least one QoE measurement to be performed at the first device, the indication being generated by the second device based on a corresponding priority of the at least one QoE measurement; and determine a report based on the indication of the at least one QoE measurement.
[0006] In a second aspect, a second device is provided. The second device includes 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, together with the at least one processor, to cause the second device to at least: generate an indication associated with reporting at least one QoE measurement based on a corresponding priority of at least one QoE measurement to be performed at a first device, and transmit the indication to the first device.
[0007] In a third aspect, a method is provided. The method includes: receiving from a second device an indication associated with reporting at least one QoE measurement to be performed at a first device, the indication being generated by the second device based on a corresponding priority of the at least one QoE measurement; and determining a report of the at least one QoE measurement based on the indication.
[0008] In a fourth aspect, a method is provided. The method includes: generating an indication associated with reporting at least one QoE measurement based on a corresponding priority of at least one QoE measurement to be performed at a first device, and transmitting the indication to the first device.
[0009] In a fifth aspect, an apparatus is provided comprising: a component for receiving from a second device an indication associated with reporting at least one QoE measurement to be performed at a first device, the indication being generated by the second device based on a corresponding priority of the at least one QoE measurement; and a component for determining, based on the indication, a report of the at least one QoE measurement.
[0010] In a sixth aspect, an apparatus is provided, comprising: means for generating an indication associated with reporting at least one QoE measurement based on a corresponding priority of at least one QoE measurement to be performed at a first device; and means for transmitting the indication to the first device.
[0011] In a seventh aspect, a computer-readable medium having a computer program stored thereon is provided, which, when executed by at least one processor of the device, causes the device to perform the method according to the third aspect.
[0012] In an eighth aspect, a computer-readable medium having a computer program stored thereon is provided, which, when executed by at least one processor of the device, causes the device to perform the method according to the fourth aspect.
[0013] Other features and advantages of the embodiments of this disclosure will become clear from the following description of specific embodiments in conjunction with the accompanying drawings, which illustrate the principles of the embodiments of this disclosure by way of example. Attached Figure Description
[0014] Embodiments of this disclosure are presented in an exemplary sense, and their advantages are explained in more detail below with reference to the accompanying drawings, in which:
[0015] Figure 1 The illustration shows an example environment in which example embodiments of the present disclosure may be implemented;
[0016] Figure 2 A signaling diagram illustrating a process for prioritizing QoE according to some example embodiments of the present disclosure is shown;
[0017] Figure 3 A signaling diagram illustrating a process for prioritizing QoE according to some example embodiments of the present disclosure is shown;
[0018] Figure 4A signaling diagram illustrating a process for prioritizing QoE according to some example embodiments of the present disclosure is shown;
[0019] Figure 5 A flowchart illustrating an example method for setting priority for QoE according to some example embodiments of this disclosure is shown;
[0020] Figure 6 A flowchart illustrating an example method for setting priority for QoE according to some example embodiments of this disclosure is shown;
[0021] Figure 7 A simplified block diagram of a device suitable for implementing example embodiments of the present disclosure is shown; and
[0022] Figure 8 A block diagram of an example computer-readable medium according to some embodiments of the present disclosure is shown.
[0023] Throughout the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation
[0024] The principles of this disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described merely for illustration and to help those skilled in the art understand and implement this disclosure, and do not teach any limitation on the scope of this disclosure. The disclosure described herein can be implemented in various ways other than those described below.
[0025] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.
[0026] References to "an embodiment," "embodiment," "example embodiment," etc., in this disclosure indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes that particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Additionally, when a particular feature, structure, or characteristic is described in connection with an example embodiment, it is believed that in conjunction with other embodiments (whether explicitly described or not) affecting such a feature, structure, or characteristic is within the knowledge of those skilled in the art.
[0027] It should be understood that although the terms “first” and “second” may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish the functions of the various elements. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.
[0028] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that, when used herein, the terms “comprising,” “including,” “having,” “containing,” and / or “comprising” specify the presence of the stated features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.
[0029] As used in this application, the term "circuit system" may refer to one or more or all of the following:
[0030] (a) Pure hardware circuit implementation (such as, implementation of pure analog and / or digital circuit systems), and
[0031] (b) A combination of hardware circuitry and software, such as (if applicable):
[0032] (i) A combination of (multiple) analog and / or digital hardware circuits and software / firmware, and
[0033] (ii) Any part of a hardware processor(s) having software (including (multiple) digital signal processors), software, and (multiple) memories, which work together to cause a device (such as a mobile phone or server) to perform various functions, and
[0034] (c) (Multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or a portion thereof, which require software (e.g., firmware) for operation, but may be absent when operation is not required.
[0035] The definition of "circuit system" applies to all uses of the term in this application, including in any claim. As another example, as used herein, the term "circuit system" also covers implementations of hardware circuitry or processors (or multiple processors) or portions thereof and their accompanying software and / or firmware. For instance, if applicable to a particular claim element, the term "circuit system" also covers baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or network devices.
[0036] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as fifth-generation (5G) systems, Long Term Evolution (LTE), LTE-A 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 a communication network can be performed according to any suitable generation of communication protocols, including but not limited to first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, future fifth-generation (5G) New Radio (NR) communication protocols, and / or any other currently known or to be developed in the future. Embodiments of this disclosure can be applied to various communication systems. Given the rapid development of communications, there will naturally be future types of communication technologies and systems that can embody this disclosure. This disclosure should not be construed as limiting its scope to the systems described above.
[0037] As used herein, the term "network device" refers to a node in a communication network through which terminal devices access the network and receive services. Network devices can refer to base stations (BS) or access points (APs), such as Node B (NodeB or NB), evolved Node B (eNodeB or eNB), NR next-generation Node B (gNB), remote radio unit (RRU), radio head (RH), remote radio head (RRH), relay, low-power nodes such as femtoseconds and picoseconds, depending on the terminology and technology applied. The RAN split architecture includes a gNB-CU (centralized unit, hosting RRC, SDAP, and PDCP) that controls multiple gNB-DUs (distributed units, hosting RLC, MAC, and PHY). A relay node can correspond to the DU portion of an IAB node.
[0038] The term "terminal device" refers to any end device capable of wireless communication. As an example and not a limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices can include, but are not limited to, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image acquisition terminal devices such as digital cameras, gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEE), laptop mounted devices (LME), USB dongles, smart devices, wireless client devices (CPE), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. Terminal equipment can also correspond to the mobile terminal (MT) portion of an integrated access and backhaul (IAB) node (also known as a relay node). In the following description, the terms "terminal equipment," "communication equipment," "terminal," "user equipment," and "UE" are used interchangeably.
[0039] While the functions described herein may be implemented in fixed and / or wireless network nodes in various example embodiments, in other example embodiments, the functions may be implemented in a user equipment device (such as a cellular phone, tablet computer, laptop computer, desktop computer, mobile IoT device, or fixed IoT device). For example, the user equipment device may be suitably equipped with corresponding capabilities as described in combination with (multiple) fixed and / or wireless network nodes. The user equipment device may be a user equipment and / or control device, such as a chipset or processor, configured to control the user equipment when installed therein. Examples of such functions include boot server functions and / or home subscriber servers, which may be implemented in the user equipment device by providing software configured to cause the user equipment device to perform operations from the perspective of these functions / nodes.
[0040] Figure 1 An example communication network 100 in which embodiments of the present disclosure may be implemented is shown. Figure 1As shown, the communication network 100 may include a terminal device 110 (hereinafter also referred to as UE 110 or first device 110). The communication network 100 may also include a network device 120 (hereinafter also referred to as gNB 120 or second device 120). The network device 120 can manage cell 102. The terminal device 110 and the network device 120 can communicate with each other within the coverage area of cell 102.
[0041] It should be understood that Figure 1 The number of network devices and terminal devices shown is given for illustrative purposes and does not imply any limitation. Communication network 100 may include any suitable number of network devices and terminal devices.
[0042] As mentioned above, the QoE process in NR can refer to both signaling-based and management-based processes.
[0043] During signaling-based processes, the core network (CN) can initiate the activation of QoE measurements configured by the operations and maintenance (OAM) entity and send the QoE measurement configuration to the gNB. The gNB can also forward the QoE measurement configuration to a specific UE via RRC signaling. The UE access layer (AS) should then send the QoE measurement configuration to the UE application layer.
[0044] During the management-based process, the OAM entity can send QoE measurement configurations to the gNB. The gNB can identify multiple qualified UEs or a single specific UE that meet the criteria (e.g., area range, application layer capabilities, service type, etc.). The gNB can also send the QoE measurement configurations to a specific UE or the AS layer of each qualified UE. The UE AS layer should then send the QoE measurement configurations to the UE application layer.
[0045] In NR, it can still be assumed that the QoE measurement configuration is transmitted from the gNB to the UE AS layer within the AS container. This configuration will be passed in the DL RRC message "RRCReconfiguration," where the QoE measurement trigger is included in the AS container, and the QoE measurement trigger is transparent to both the gNB and the UE AS layer. Multiple measurements can be configured for the UE simultaneously.
[0046] In cases of gNB overload, to alleviate overload on the air interface, the gNB can stop new QoE measurement configurations, release existing QoE measurement configurations, and / or temporarily suspend QoE measurement reporting. The applicability of QoE configurations to different RRC states introduces additional complexity when handling unexpected application layer reports to the UE AS layer. In the worst-case scenario, the UE's RRC connection is released, and the UE's application layer can generate a report storm with reporting intervals, unable to transmit reports to the gNB due to the lack of active RRC connections or suspended RRC reports. Currently, neither the UE AS nor the gNB can control incoming unexpected application layer reports.
[0047] Furthermore, it has been agreed that a UE can be configured to perform multiple simultaneous QoE measurements and report the corresponding results, which also means that multiple QoE measurements will be configured within a single cell. However, the gNB may be unsure how to abort / resume QoE measurement reporting in the context of multiple simultaneous configurations. RRC or SRB4 versions can represent a hard stop for any QoE measurement reporting, although the concept of temporary abort has not yet been defined.
[0048] Therefore, it is expected that some configured QoE measurement reports can be maintained under conditions such as moderate overload, since these QoE measurements are more important than others. It is also expected that the gNB has the ability to control configured QoE measurement reports one by one within a cell. For example, an RRC connection with a low-priority QoE measurement can be released first. When the gNB recovers from the overload condition, it can resume the QoE measurement report with the high-priority configuration first.
[0049] This disclosure provides a solution for prioritizing QoE measurements. In this solution, the UE can receive from the gNB an indication associated with reporting at least one QoE measurement to be performed at a first device, the indication being generated by the gNB based on the corresponding priority of the at least one QoE measurement. Based on this indication, the UE can determine the reporting of the at least one QoE measurement. In this way, the gNB has the ability to control the configuration of QoE measurement reporting by the UE under overload conditions, and under low and medium overload conditions, the QoE reporting of the UE with high priority can be maintained without interruption.
[0050] The following is combined Figures 2-4 The principles and implementation of this disclosure will be explained in detail. Figures 2-4 A schematic procedure for setting priorities for QoE is shown. For discussion purposes, references will be made to... Figure 1 Describe process 200-400. Process 200-400 may involve, for example: Figure 1 The UE 110 and gNB 120 are shown.
[0051] The gNB 120 can obtain information about the corresponding priorities of at least one QoE measurement to be performed by the UE 110 from the CN node or OAM entity. Optionally, the gNB 120 can obtain information about the corresponding priorities of at least one QoE measurement, as well as configuration parameters configured for the at least one QoE measurement, from the CN node or OAM entity. It should be understood that information about the corresponding priorities of at least one QoE measurement can be transmitted to the gNB 120 from the CN node or OAM entity via a separate message. Alternatively, the gNB 120 can also request information about the corresponding priorities of at least one QoE measurement from the CN node or OAM entity. For example, the gNB 120 can send a request for the corresponding priorities of at least one QoE measurement to the CN node or OAM entity.
[0052] like Figure 2 As shown, gNB 120 can generate 202 an indication for UE 110 to report at least one QoE measurement based on obtained information regarding the corresponding priorities of at least one QoE measurement. gNB 120 can then transmit 204 this indication to UE 110. This indication can be transmitted to UE 110 when gNB 120 forwards configuration parameters configured for the at least one QoE measurement to UE 110. Alternatively, gNB 120 can also transmit this indication independently.
[0053] Based on this instruction, UE 110 can obtain information about the corresponding priority of at least one QoE measurement. UE 110 can store the corresponding priority of at least one QoE measurement.
[0054] Under normal circumstances, UE 110 can perform at least one QoE measurement based on the configured measurement parameters and report at least one QoE measurement to gNB 120.
[0055] When gNB 120 determines that the air interface between gNB 120 and UE 110 is overloaded, gNB 120 can determine a first overload level and transmit an indication of the first overload level to UE 110.
[0056] Based on the overload level, UE 110 can determine a first threshold priority for the first overload level. The association between the overload level and multiple threshold priorities can be pre-configured for UE 110. Alternatively, this association can also be transmitted to UE 110 from gNB 120 along with priority information for at least one QoE measurement. It should be understood that this association can be transmitted to UE 110 from gNB 120 via a separate message. For example, this message could be a SIB or RRC-specific message.
[0057] If UE 110 determines that the priority of the first group of QoE measurements in at least one QoE measurement is lower than the determined first threshold priority, UE 110 may stop, suspend, or pause reporting the first group of QoE measurements. In the following text, "suspend QoE measurement reporting" can be understood as the ability to temporarily stop or suspend reporting QoE measurements. UE 110 may report 210 other QoE measurements in at least one QoE measurement besides the first group of QoE measurements.
[0058] If gNB 120 determines that the overload situation has not recovered, gNB 120 may transmit an indication of a second overload level to UE 110. UE 110 may determine a second threshold priority for the second overload level, which may be higher than the first threshold priority.
[0059] Then, UE 110 can stop, abort, or suspend 214 reporting of a second group of QoE measurements out of at least one QoE measurement. The corresponding priority of the second group of QoE measurements can be higher than the first threshold priority and lower than the second threshold priority.
[0060] If gNB 120 determines that the overload situation has recovered, gNB 120 can update the overload level. For example, gNB 120 can transmit an indication of the first overload level to UE 110. Then, UE 110 can resume reporting QoE measurements with a priority higher than the first threshold priority. For example, UE 110 can resume a second set of QoE measurements.
[0061] In some example implementations, for QoE measurements that have been stopped or suspended from reporting, UE 110 may determine whether the results of these QoE measurements should be recorded or discarded based on the corresponding priority of the stopped or suspended QoE measurements.
[0062] For example, as described above, the first group of QoE measurements and the second group of QoE measurements have stopped, aborted, or suspended reporting. UE110 can record the results of the second group of QoE measurements and discard the results of the first group of QoE measurements because the corresponding priority of the second group of QoE measurements is higher than that of the first group of QoE measurements.
[0063] In some example embodiments, if UE 110 determines that the overload condition of gNB 120 has changed, for example, if UE 110 determines that the reporting of the second set of QoE measurements can be resumed, then UE 110 can determine whether the historical results of the second set of QoE measurements have been recorded at UE 110. If UE 110 determines that there are recorded historical results of the second set of QoE measurements, then UE 110 can report the recorded historical results to gNB 120.
[0064] It should be understood that if the corresponding historical results of more than one QoE measurement have been recorded, the UE 110 can report them one after another in priority order of the corresponding priority of the more than one QoE measurement.
[0065] In some example embodiments, indications of multiple overload levels may be transmitted from gNB 120 to UE 110 via RRC signaling. Alternatively, the indication may also be transmitted from gNB 120 to UE 110 via System Information Block (SIB) broadcast. It should be understood that any other suitable signaling may also carry the transmission of this indication.
[0066] Figure 3 Another illustrative procedure for prioritizing QoE is shown. (Compared to...) Figure 2 Similar to the process shown, gNB 120 can generate 302 an indication for UE 110 to report at least one QoE measurement based on the obtained information about the corresponding priority of at least one QoE measurement, and transmit 304 the indication to UE 110.
[0067] In this scenario, gNB 120 can transmit an indication of timer 306, which is used by the UE to detect the overload state of gNB 120. The timer can indicate a time interval within which the UE 110 can determine whether it has received an indication of the overload state of gNB 120 from gNB 120.
[0068] In some example embodiments, the timer indication may be transmitted from gNB 120 to UE 110 via RRC signaling. Alternatively, the indication may also be transmitted from gNB 120 to UE 110 via SIB broadcast. It should be understood that any other suitable signaling may also carry the transmission of this indication.
[0069] UE 110 can detect whether it receives an indication of an overload state from gNB 120 by starting a timer. If UE 110 determines that an overload state is detected before the timer expires, UE 110 can stop or suspend reporting at least one set of QoE measurements in 308. The corresponding priority of the first set of QoE measurements can be lower than the first threshold priority corresponding to the overload state.
[0070] The detection of the overload state of gNB 120 can be performed periodically based on a timer. In some example embodiments, UE 110 can also detect whether it has received an indication of the overload state of gNB 120 from gNB 120 by restarting the timer. If UE 110 fails to detect the overload state before the timer expires, UE 110 can resume the first set of QoE measurements that 310 has stopped or suspended reporting.
[0071] Alternatively, if UE 110 continues to receive indication of an overload state from gNB 120 312 before the timer expires, indicating that the overload state of gNB 120 has not improved after stopping or pausing the reporting of the first group of QoE measurements, then UE 110 may stop or pause the reporting of a second group of QoE measurements in at least one QoE measurement 314. The corresponding priority of the second group of QoE measurements may be higher than the first threshold priority and lower than the second threshold priority.
[0072] Similarly, for QoE measurements that have been stopped or suspended from reporting, UE 110 can determine whether the results of these QoE measurements should be recorded or discarded based on the corresponding priority of the stopped or suspended QoE measurements.
[0073] For example, as described above, the reporting of the first group of QoE measurements and the second group of QoE measurements has stopped or been suspended. UE 110 can record the results of the second group of QoE measurements and discard the results of the first group of QoE measurements because the corresponding priority of the second group of QoE measurements is higher than that of the first group of QoE measurements.
[0074] In some example embodiments, if UE 110 determines that the overload state of gNB 120 has been removed, for example, if UE 110 determines that reporting of the second set of QoE measurements can be resumed, then UE 110 can determine whether the historical results of the second set of QoE measurements have been recorded at UE 110. If UE 110 determines that there are recorded historical results of the second set of QoE measurements, then UE 110 can report the recorded historical results to gNB 120.
[0075] It should be understood that if the corresponding historical results of more than one QoE measurement have been recorded, the UE 110 can report them one after another in priority order of the corresponding priority of the more than one QoE measurement.
[0076] In some example embodiments, an overload status indication may be transmitted from gNB 120 to UE 110 via RRC signaling. Alternatively, the indication may also be transmitted from gNB 120 to UE 110 via System Information Block (SIB) broadcast. It should be understood that any other suitable signaling may also carry the transmission of this indication.
[0077] Now for reference Figure 4 , Figure 4 This illustrates another illustrative process for setting priority for QoE.
[0078] In this case, gNB 120 can be configured with the appropriate priority for at least one QoE measurement to be performed by UE 110.
[0079] When gNB 120 determines that the air interface between gNB 120 and UE 110 is overloaded, gNB 120 can determine the configuration for UE 110 to report at least one QoE measurement based on the corresponding configured priority.
[0080] For example, gNB 120 can determine a first group of QoE measurements that do not need to be reported and / or a second group of QoE measurements that are allowed to be reported, based on the corresponding priority of at least one QoE measurement.
[0081] In some example embodiments, gNB 120 can determine the identifiers of the first set of QoE measurements and the second set of QoE measurements, and generate a configuration based on the identifiers.
[0082] Alternatively, the gNB 120 can also determine the service type of the first set of QoE measurements and the second set of QoE measurements, and generate a configuration based on the service type.
[0083] gNB 120 can transmit configuration 404 to UE 110. After receiving the configuration, UE 110 can stop or pause reporting the first set of QoE measurements 406 and continue reporting the second set of QoE measurements 408.
[0084] When gNB 120 determines that the overload situation has been resolved, gNB 120 can update the configuration for UE 110 to report at least one QoE measurement based on the corresponding priority configured. For example, gNB 120 can determine the first set of QoE measurements that have been stopped or suspended and update the configuration based on that decision.
[0085] After UE 110 receives 410 to the updated configuration, UE 110 can resume 420 to report the first set of QoE measurements.
[0086] Similarly, for QoE measurements that have been stopped or suspended from reporting, UE 110 can determine whether the results of these QoE measurements should be recorded or discarded based on the corresponding priority of the stopped or suspended QoE measurements.
[0087] Furthermore, when UE 110 determines that the overload condition of gNB 120 has changed, for example, when UE 110 determines that the reporting of the first set of QoE measurements can be resumed, UE 110 can determine whether the historical results of the first set of QoE measurements have been recorded at UE 110. If UE 110 determines that there are recorded historical results of the first set of QoE measurements, then UE 110 can report the recorded historical results to gNB 120.
[0088] In this way, the gNB has the ability to control the configuration of the UE's QoE measurement reports, and the QoE reports of high-priority UEs can be maintained without interruption under low and medium overload conditions.
[0089] Figure 5 A flowchart of an example method 500 for setting priority for QoE according to some example embodiments of the present disclosure is shown. Method 500 can be implemented as follows: Figure 1 The first device 110 shown is implemented therein. For the purposes of discussion, reference will be made to... Figure 1 Let's describe method 500.
[0090] At 510, the first device receives from the second device an indication associated with reporting at least one Quality of Experience (QoE) measurement to be performed at the first device, the indication being generated by the second device based on the corresponding priority of the at least one QoE measurement.
[0091] In some example embodiments, the first device may receive information about the corresponding priority of at least one QoE measurement from the second device.
[0092] In some example embodiments, the first device may receive a configuration for reporting at least one QoE measurement, determined by the second device based on a corresponding priority. This configuration includes an identifier associated with a first group of QoE measurements that do not need to be reported to the second device; or a service type associated with the first group of QoE measurements that do not need to be reported to the second device.
[0093] At 520, the first device determines a report of at least one QoE measurement based on the instruction.
[0094] In some example embodiments, the first device may receive information from the second device regarding the overload level of the channel between the first and second devices, and determine a threshold priority based on the overload level. If the first device determines that the corresponding priority of a first group of QoE measurements in at least one QoE measurement is lower than the threshold priority, the first device may stop or suspend reporting the first group of QoE measurements.
[0095] In some example embodiments, if the first device determines an additional overload level of the channel received from the second device, the first device may determine an additional threshold priority based on the additional overload level. If the first device determines that the corresponding priority of the first set of QoE measurements exceeds the additional threshold priority, the first device may resume reporting the first set of QoE measurements.
[0096] In some example embodiments, the first device may receive additional information about a timer used by the first device to detect an overload state of the channel between the first device and the second device, and perform overload state detection by starting the timer. If the first device determines that an overload state is detected before the timer expires, the first device may determine a first threshold priority based on the overload state. If the first device determines that the corresponding priority of a first group of QoE measurements in at least one QoE measurement is lower than the first threshold priority, the first device may stop or suspend reporting of the first group of QoE measurements.
[0097] In some example embodiments, the first device can perform additional detection of the overload state by restarting a timer. If the first device determines that an overload state is detected before the timer expires, the first device can determine a second threshold priority based on the overload state, the second threshold priority being higher than the first threshold priority. If the first device determines that the corresponding priority of a second set of QoE measurements in at least one QoE measurement exceeds the first threshold priority but is lower than the second threshold priority, the first device can stop or pause reporting the second set of QoE measurements.
[0098] In some example embodiments, if the first device determines that it has failed to detect an overload condition before the timer expires, the first device may resume reporting the first set of QoE measurements.
[0099] In some example embodiments, the first device may perform at least one of the following based on the corresponding priority of the first set of QoE measurements: record the results of the first set of QoE measurements or discard the results of the first set of QoE measurements.
[0100] In some example embodiments, if the first device determines that the report of the first set of QoE measurements has been recovered, the first device may determine whether the historical results of the first set of QoE measurements have been recorded. If the first device determines that the historical results have been recorded, the first device may report the historical results to the second device based on the corresponding priority of the first set of QoE measurements.
[0101] In some example embodiments, if the first device determines that the indication includes a configuration for reporting at least one QoE measurement determined by the second device based on a corresponding priority, the first device may determine, based on the configuration, that a first set of QoE measurements of the at least one QoE measurement does not need to be reported to the second device, and stop or suspend reporting the results of the first set of QoE measurements.
[0102] In some example embodiments, the first device may perform at least one of the following: record the results of the first set of QoE measurements or discard the results of the first set of QoE measurements.
[0103] In some example embodiments, if the first device determines that the report of the first set of QoE measurements has been recovered, the first device may determine whether the historical results of the first set of QoE measurements have been recorded. If the first device determines that the historical results have been recorded, the first device may report the historical results to the second device.
[0104] In some example embodiments, if the first device determines that no historical results have been recorded, the first device may report the current results of the first set of QoE measurements to the second device.
[0105] In some example embodiments, the first device includes a terminal device, and the second device includes a network device.
[0106] Figure 6 A flowchart of an example method 600 for setting priority for QoE according to some example embodiments of the present disclosure is shown. Method 600 can be implemented as follows: Figure 1 The second device 120 shown is implemented therein. For the purposes of discussion, reference will be made to... Figure 1 Let's describe method 600.
[0107] At 610, the second device generates an indication associated with reporting at least one QoE measurement based on the corresponding priority of at least one Quality of Experience (QoE) measurement to be performed at the first device.
[0108] In some example embodiments, the second device may obtain the corresponding priority of at least one QoE measurement from at least one of the core network entity or the operations and maintenance entity.
[0109] In some example embodiments, the second device may determine the corresponding priority of at least one QoE measurement based on the corresponding service type of at least one QoE measurement.
[0110] In some example embodiments, the second device may transmit information about the corresponding priority of at least one QoE measurement from the second device.
[0111] In some example embodiments, the second device may transmit a configuration for reporting at least one QoE measurement, determined by the second device based on a corresponding priority. This configuration includes at least one of the following: an identifier associated with a first group of QoE measurements that do not need to be reported to the second device; or a service type associated with the first group of QoE measurements that do not need to be reported to the second device.
[0112] At 620, the second device transmits the instruction to the first device.
[0113] In some example embodiments, the second device may transmit information to the first device about the overload level of the channel between the first and second devices.
[0114] In some example embodiments, the second device may transmit additional information about a timer to the first device, which is used by the first device to detect an overload condition of the channel between the first and second devices.
[0115] In some example embodiments, the first device includes a terminal device, and the second device includes a network device.
[0116] In some example embodiments, an apparatus capable of performing method 500 (e.g., implemented at UE 110) may include components for performing corresponding steps of method 500. These components may be implemented in any suitable form. For example, the components may be implemented as a circuit system or a software module.
[0117] In some example embodiments, the apparatus includes components for receiving from a second device an indication associated with reporting at least one QoE measurement to be performed at a first device, the indication being generated by the second device based on a corresponding priority of the at least one QoE measurement; and components for determining a report of the at least one QoE measurement based on the indication.
[0118] In some example embodiments, an apparatus capable of performing method 600 (e.g., implemented at gNB 120) may include components for performing the corresponding steps of method 600. These components may be implemented in any suitable form. For example, the components may be implemented as a circuit system or a software module.
[0119] In some example embodiments, the apparatus includes components for generating an indication associated with reporting at least one QoE measurement based on a corresponding priority of at least one Quality of Experience (QoE) measurement to be performed at a first device; and components for transmitting the indication to the first device.
[0120] Figure 7 This is a simplified block diagram of a device 700 suitable for implementing embodiments of the present disclosure. The device 700 can be provided to implement a communication device, such as... Figure 1 The UE 110 and gNB 120 are shown in the figure. As shown, the device 700 includes one or more processors 710, one or more memories 740 coupled to the processors 710, and one or more transmitters and / or receivers (TX / RX) 740 coupled to the processors 710.
[0121] The TX / RX 740 is used for bidirectional communication. The TX / RX 740 has at least one antenna to facilitate communication. The communication interface can represent any interface necessary for communication with other network components.
[0122] Processor 710 can be any type suitable for a local technology network, and by way of non-limiting example, can include one or more of the following: general-purpose computer, special-purpose computer, microprocessor, digital signal processor (DSP), and processor based on a multi-core processor architecture. Device 700 can have multiple processors, such as application-specific integrated circuit chips that are time-dependent on a clock synchronized with the main processor.
[0123] Memory 720 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 724, electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disc (CD), digital video disk (DVD), and other magnetic and / or optical storage devices. Examples of volatile memories include, but are not limited to, random access memory (RAM) 722 and other volatile memories that do not persist during power outages.
[0124] Computer program 730 includes computer-executable instructions that are executed by the associated processor 710. Program 730 may be stored in ROM 720. Processor 710 can perform any suitable actions and processes by loading program 730 into RAM 720.
[0125] Embodiments of this disclosure can be implemented by means of program 730, thereby enabling device 700 to perform as described in the reference. Figures 2 to 6 Any process discussed in this disclosure. Embodiments of this disclosure may also be implemented by hardware or a combination of software and hardware.
[0126] In some embodiments, program 730 may be tangibly contained in a computer-readable medium, which may be included in device 700 (such as in memory 720) or in other storage devices accessible to device 700. Device 700 may load program 730 from the computer-readable medium into RAM 722 for execution. The computer-readable medium may include any type of tangible non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. Figure 8 An example of a computer-readable medium 700 in the form of a CD or DVD is shown. A program 730 is stored on the computer-readable medium.
[0127] Generally, the various embodiments of this disclosure can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of this disclosure are illustrated and described as block diagrams, flowcharts, or other graphical representations, it should be understood that, as non-limiting examples, the blocks, devices, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.
[0128] This 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 computer-executable instructions included in program modules, which execute in a device on a target real or virtual processor to perform the functions described above. Figures 5 to 6 The methods described are 500-600. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform specific tasks or implement specific abstract data types. In various embodiments, the functionality of a program module can be combined or split among program modules as needed. The machine-executable instructions of a program module can execute on a local or distributed device. In a distributed device, a program module can reside on both local and remote storage media.
[0129] Program code used to perform the methods of this disclosure 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, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a stand-alone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.
[0130] In the context of this disclosure, computer program code or related 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.
[0131] Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable media can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or any suitable combination thereof. More specific examples of computer-readable storage media will include electrical connections having one or more wires, portable computer floppy disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.
[0132] Furthermore, although operations are described in a specific order, this should not be construed as requiring the operations to be performed in the specific order shown or sequentially, or to perform all of the shown operations to obtain the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the foregoing discussion, these should not be construed as limiting the scope of this disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features described in the context of a single embodiment may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.
[0133] Although this disclosure has been described in language specific to structural features and / or methodological actions, it should be understood that this disclosure as defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as exemplary forms of implementing the claims.
Claims
1. A first device comprising: 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, with the at least one processor, cause the first device at least to: receive, from a second device, an indication associated with reporting at least one quality of experience, QoE, measurement to be performed at the first device, wherein the indication is generated based on respective priorities of the at least one QoE measurement; and determine the reporting of the at least one QoE measurement based on the indication, wherein the determining the reporting of the at least one QoE measurement based on the indication comprises discarding one or more of the at least one QoE measurement for which reporting has stopped, been suspended or paused based on the respective priorities of the at least one QoE measurement.
2. The first device of claim 1, wherein the first device is caused to receive the indication by: receiving, from the second device, information of the respective priorities of the at least one QoE measurement.
3. The first device of claim 1, wherein the first device is caused to receive the indication by: receiving a configuration for reporting at least one QoE measurement determined by the second device based on the respective priorities, the configuration comprising at least one of: an identifier associated with a first group of QoE measurements of the at least one QoE measurement for which reporting to the second device is not required; or a service type associated with a first group of QoE measurements of the at least one QoE measurement for which reporting to the second device is not required.
4. The first device of claim 1, wherein the first device is caused to determine the reporting of the at least one QoE measurement by: receiving, from the second device, information on an overload level of a channel between the first device and the second device; determining a threshold priority based on the overload level; and in accordance with a determination that a first group of QoE measurements of the at least one QoE measurement has respective priorities that are below the threshold priority, stopping or suspending reporting of the first group of QoE measurements.
5. The first device of claim 4, wherein the first device is further caused to: in accordance with a determination that a further overload level of the channel is received from the second device, determine a further threshold priority based on the further overload level; and in accordance with a determination that the first group of QoE measurements has respective priorities that exceed the further threshold priority, resume reporting of the first group of QoE measurements.
6. The first device of claim 1, wherein the first device is caused to determine the reporting of the at least one QoE measurement by: receiving further information on a timer for the first device to detect an overload state of a channel between the first device and the second device; performing the detection of the overload state by starting the timer; determining, based on the overload condition, a first threshold priority level in accordance with a determination that the overload condition is detected before expiration of the time; and stopping or suspending reporting of a first set of QoE measurements of the at least one QoE measurement in accordance with a determination that the first set of QoE measurements has a respective priority level that is below the first threshold priority level.
7. The first device of claim 6, wherein the first device is further caused to: perform further detection of the overload condition by restarting the timer; determine, based on the overload condition, a second threshold priority level in accordance with a determination that the overload condition is detected before expiration of the time, the second threshold priority level being higher than the first threshold priority level; and stop or suspend reporting of a second set of QoE measurements of the at least one QoE measurement in accordance with a determination that the second set of QoE measurements has a respective priority level that exceeds the first threshold priority level and is below the second threshold priority level.
8. The first device of claim 7, wherein the first device is further caused to: resume reporting of the first set of QoE measurements in accordance with a determination that the overload condition fails to be detected before expiration of the time.
9. The first device of claim 4 or 6, wherein the first device is further caused to: perform at least one of the following based on the respective priority level of the first set of QoE measurements: record results of the first set of QoE measurements; or discard results of the first set of QoE measurements.
10. The first device of claim 5 or 8, wherein the first device is caused to resume reporting of the first set of QoE measurements by: determining, in accordance with a determination that the reporting of the first set of QoE measurements is resumed, whether historical results of the first set of QoE measurements are recorded; and reporting, in accordance with a determination that the historical results are recorded, the historical results to the second device based on the respective priority level of the first set of QoE measurements.
11. The first device of claim 1, wherein the first device is caused to determine the reporting of the at least one QoE measurement by: determining, in accordance with a determination that the indication includes a configuration for reporting at least one QoE measurement determined by the second device based on the respective priority level, that a first set of QoE measurements of the at least one QoE measurement does not need to be reported to the second device based on the configuration; and stopping or suspending reporting of results of the first set of QoE measurements.
12. The first device of claim 11, wherein the first device is further caused to: perform at least one of the following: record the results of the first set of QoE measurements; or discard the results of the first set of QoE measurements.
13. The first device of claim 11, wherein the first device is further caused to: determine, in accordance with a determination that the reporting of the first set of QoE measurements is resumed, whether historical results of the first set of QoE measurements are recorded; and report, in accordance with a determination that the historical results are recorded, the historical results to the second device.
14. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a first device, cause the first device to perform any of the methods of claims 1-13.
15. A first device comprising means for performing any of the methods of claims 1-13.
14. The first device of claim 13, wherein the first device is further caused to: report current results of the first set of QoE measurements to the second device, according to a determination that no historical results are recorded.
15. The first device of claim 1, wherein the first device comprises a terminal device and the second device comprises a network device.
16. A method for communication, comprising: receiving, at a first device, an indication associated with reporting at least one quality of experience (QoE) measurement to be performed at the first device, wherein the indication is generated based on respective priorities of the at least one QoE measurement; and determining the reporting of the at least one QoE measurement based on the indication, wherein the determining the reporting of the at least one QoE measurement based on the indication comprises dropping one or more QoE measurements of the at least one QoE measurement that have stopped, suspended, or paused reporting based on the respective priorities of the at least one QoE measurement.
17. The method of claim 16, wherein the receiving the indication comprises: receiving, from the second device, information of the respective priorities of the at least one QoE measurement.
18. The method of claim 16, wherein the receiving the indication comprises: receiving a configuration for reporting at least one QoE measurement determined by the second device based on the respective priorities, the configuration comprising at least one of: an identifier associated with a first set of QoE measurements of the at least one QoE measurement that need not be reported to the second device; or a service type associated with a first set of QoE measurements of the at least one QoE measurement that need not be reported to the second device.
19. The method of claim 16, wherein the determining the reporting of the at least one QoE measurement comprises: receiving, from the second device, information regarding a level of overload of a channel between the first device and the second device; determining a threshold priority based on the level of overload; and stopping or suspending reporting a first set of QoE measurements of the at least one QoE measurement, according to a determination that the first set of QoE measurements have respective priorities that are lower than the threshold priority.
20. The method of claim 19, further comprising: determining, according to a determination that a further level of overload of the channel is received from the second device, a further threshold priority based on the further level of overload; and resuming reporting the first set of QoE measurements, according to a determination that the first set of QoE measurements have respective priorities that exceed the further threshold priority.
21. The method of claim 16, wherein the determining the reporting of the at least one QoE measurement comprises: receiving further information regarding a timer for the first device to detect an overload status of a channel between the first device and the second device; performing the detection of the overload status by starting the timer; determining a first threshold priority based on the overload condition, in accordance with a determination that the overload condition is detected prior to expiration of the time; and stopping or suspending reporting of a first set of the at least one QoE measurement, in accordance with a determination that a second set of the at least one QoE measurement has a respective priority that exceeds the first threshold priority and is below a second threshold priority.
22. The method of claim 21, further comprising: performing further detection of the overload condition by restarting the timer; determining a second threshold priority based on the overload condition, in accordance with a determination that the overload condition is detected prior to expiration of the time, the second threshold priority being higher than the first threshold priority; and stopping or suspending reporting of a second set of the at least one QoE measurement, in accordance with a determination that a second set of the at least one QoE measurement has a respective priority that exceeds the first threshold priority and is below a second threshold priority.
23. The method of claim 22, further comprising: resuming reporting of the first set of QoE measurements, in accordance with a determination that the overload condition fails to be detected prior to expiration of the time.
24. The method of claim 19 or 21, further comprising: performing at least one of the following based on the respective priority of the first set of QoE measurements: recording results of the first set of QoE measurements; or discarding results of the first set of QoE measurements.
25. The method of claim 20 or 23, wherein resuming reporting of the first set of QoE measurements comprises: determining whether historical results of the first set of QoE measurements are recorded, in accordance with a determination that the reporting of the first set of QoE measurements is resumed; and reporting the historical results to the second device based on the respective priority of the first set of QoE measurements, in accordance with a determination that the historical results are recorded.
26. The method of claim 16, wherein determining the reporting of the at least one QoE measurement comprises: determining that a first set of the at least one QoE measurement does not need to be reported to the second device based on a configuration for reporting at least one QoE measurement determined by the second device based on the respective priority, in accordance with a determination that the indication comprises the configuration; and stopping or suspending reporting of results of the first set of QoE measurements.
27. The method of claim 26, further comprising: performing at least one of the following: recording the results of the first set of QoE measurements; or discarding the results of the first set of QoE measurements.
28. The method of claim 27, further comprising: determining whether historical results of the first set of QoE measurements are recorded, in accordance with a determination that the reporting of the first set of QoE measurements is resumed; and reporting the historical results to the second device, in accordance with a determination that the historical results are recorded.
29. The method of claim 28, further comprising: reporting current results of the first set of QoE measurements to the second device, in accordance with a determination that no historical results are recorded.
30. The method of claim 16, wherein the first device comprises a terminal device and the second device comprises a network device.
31. An apparatus for communication, comprising: means for receiving, from a second device, an indication associated with reporting at least one quality of experience (QoE) measurement to be performed at a first device, wherein the indication is generated based on respective priorities of the at least one QoE measurement; and means for determining the reporting of the at least one QoE measurement based on the indication, wherein the determining the reporting of the at least one QoE measurement based on the indication comprises dropping one or more of the at least one QoE measurement that have stopped, suspended, or paused reporting based on the respective priorities of the at least one QoE measurement.
32. A non-transitory computer-readable medium comprising program instructions for causing an apparatus to perform at least the method of any one of claims 16-30.