A measurement reporting method, device and storage medium
After receiving QoE measurement configuration information, the terminal promptly reports QoE measurement data in industrial application scenarios based on triggered events, solving the problem of insufficient real-time performance of existing QoE measurement methods and enabling timely reporting of equipment downtime in industrial application scenarios.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- CHINA UNITED NETWORK COMM GRP CO LTD
- Filing Date
- 2025-01-06
- Publication Date
- 2026-05-26
AI Technical Summary
Existing QoE measurement methods are insufficient in terms of real-time performance and cannot meet the need for timely QoE measurement reports after equipment failure in industrial application scenarios.
The terminal receives QoE measurement configuration information sent by the access network device and reports a QoE measurement report when a trigger event is met. The trigger event includes not receiving an application layer response message within a preset period or not receiving an application layer message within multiple consecutive periods, thereby achieving real-time QoE measurement.
It improves the real-time performance of QoE measurements, enabling terminals to send timely reports to access network devices in the event of network failures, thus meeting the real-time requirements of industrial application scenarios.
Smart Images

Figure CN119865849B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of communication technology, and in particular to a measurement reporting method, apparatus and storage medium. Background Technology
[0002] Quality of Experience (QoE) measurement is an effective means of measuring network quality. For traditional video services and extended reality (XR) services, QoE measurement is mainly based on the collection and reporting of application layer data based on user experience.
[0003] Currently, most existing QoE measurement methods have poor real-time reporting capabilities, such as timely reporting of QoE measurement reports after a device experiences a network failure. However, industrial applications have higher real-time requirements, needing to promptly report QoE measurement reports after a device malfunctions. Therefore, existing QoE measurement methods cannot meet the real-time requirements of industrial applications. Summary of the Invention
[0004] This application provides a measurement reporting method, apparatus, and storage medium to address the technical problem of low real-time performance in existing QoE measurement methods.
[0005] To achieve the above objectives, this application adopts the following technical solution:
[0006] In a first aspect, a measurement reporting method is provided, comprising: receiving Quality of Experience (QoE) measurement configuration information sent by an access network device; the QoE measurement configuration information is used to instruct a terminal to report a QoE measurement report when a trigger event is met; when it is determined that the terminal meets the trigger event, a QoE measurement report is sent to the access network device; the QoE measurement report is generated by QoE measurement based on the QoE measurement configuration information.
[0007] Optionally, the triggering event is an event corresponding to the terminal's application layer protocol; the triggering event is: when no application layer response message is received from the access network device within the first preset period, the terminal is triggered to report a QoE measurement report; the application layer response message is used to respond to the first application layer message sent by the terminal to the access network device within the first preset period.
[0008] Optionally, the triggering event is an event corresponding to the terminal's application layer protocol; the triggering event is: when no second application layer message is received from the access network device within multiple consecutive second preset periods, the terminal is triggered to report a QoE measurement report.
[0009] Optionally, the system receives Quality of Experience (QoE) measurement configuration information sent by the access network device, including: the access layer of the terminal receives the QoE measurement configuration information sent by the access network device.
[0010] Optionally, sending QoE measurement reports to access network devices includes: sending QoE measurement reports to access network devices based on the terminal access layer.
[0011] Optionally, the measurement reporting method further includes: receiving Minimization of Drive-tests (MDT) measurement configuration information sent by the access network device based on the terminal's access layer; when the terminal's access layer receives a QoE measurement report sent by the terminal's application layer, generating an MDT measurement report based on the terminal's access layer and sending the MDT measurement report to the access network device; the MDT measurement report is obtained by performing MDT measurements based on the MDT measurement configuration information.
[0012] Optionally, the measurement reporting method further includes: after receiving the QoE measurement configuration information sent by the access network device, performing QoE measurement based on the application layer of the terminal; when the application layer of the terminal detects that the terminal meets the trigger event, generating a QoE measurement report based on the measurement result of the current QoE measurement.
[0013] Optionally, the measurement reporting method further includes: after receiving the QoE measurement configuration information sent by the access network device for a first preset time period, performing QoE measurement based on the application layer of the terminal; when the application layer based on the terminal detects that the terminal meets the trigger event, generating a QoE measurement report based on the measurement result of the current QoE measurement.
[0014] Optionally, the measurement reporting method further includes: after receiving the QoE measurement configuration information sent by the access network device, performing QoE measurement based on the application layer of the terminal to obtain a QoE measurement cache; when the QoE measurement cache is greater than the preset cache, performing QoE measurement again; when the application layer of the terminal detects that the terminal meets the trigger event, generating a QoE measurement report based on the measurement result of the current QoE measurement.
[0015] Optionally, the measurement reporting method further includes: after receiving the QoE measurement configuration information sent by the access network device, performing QoE measurement based on the application layer of the terminal; and ending the QoE measurement after a second preset time period to obtain a QoE measurement report.
[0016] Optionally, the QoE measurement report includes at least one of the following: Protocol Data Unit (PDU) session measurement information and Quality of Service (QoS) flow measurement information; wherein, the PDU session measurement information is obtained by performing QoE measurement on the PDU session based on the QoE measurement configuration information; and the QoS flow measurement information is obtained by performing QoE measurement on the QoS flow based on the QoE measurement configuration information.
[0017] Secondly, a measurement reporting device is provided, comprising: a receiving unit and a sending unit; the receiving unit is configured to receive Quality of Experience (QoE) measurement configuration information sent by an access network device; the QoE measurement configuration information is used to instruct a terminal to report a QoE measurement report when a trigger event is met; the sending unit is configured to send a QoE measurement report to the access network device when it is determined that the terminal meets the trigger event; the QoE measurement report is generated by QoE measurement based on the QoE measurement configuration information.
[0018] Optionally, the triggering event is an event corresponding to the terminal's application layer protocol; the triggering event is: when no application layer response message is received from the access network device within the first preset period, the terminal is triggered to report a QoE measurement report; the application layer response message is used to respond to the first application layer message sent by the terminal to the access network device within the first preset period.
[0019] Optionally, the triggering event is an event corresponding to the terminal's application layer protocol; the triggering event is: when no second application layer message is received from the access network device within multiple consecutive second preset periods, the terminal is triggered to report a QoE measurement report.
[0020] Optionally, the receiving unit is specifically used for: receiving QoE measurement configuration information sent by the access network device based on the terminal's access layer.
[0021] Optionally, the sending unit is specifically used for: sending a QoE measurement report from the terminal-based access layer to the access network device.
[0022] Optionally, the measurement reporting device further includes: a first processing unit; a sending unit, further configured to receive minimized drive test (MDT) measurement configuration information sent by the access network device based on the terminal's access layer; the first processing unit, configured to generate an MDT measurement report based on the terminal's access layer when a QoE measurement report sent by the terminal's application layer is received at the terminal's access layer; the sending unit, further configured to send the MDT measurement report to the access network device; the MDT measurement report is obtained by performing MDT measurements based on the MDT measurement configuration information.
[0023] Optionally, the measurement reporting device further includes: a second processing unit; the second processing unit is configured to perform QoE measurement based on the application layer of the terminal after receiving QoE measurement configuration information sent by the access network device; the second processing unit is also configured to generate a QoE measurement report based on the measurement result of the current QoE measurement when the application layer of the terminal detects that the terminal meets the trigger event.
[0024] Optionally, the measurement reporting device further includes: a third processing unit; the third processing unit is configured to perform QoE measurement based on the application layer of the terminal after receiving QoE measurement configuration information sent by the access network device for a first preset time period; the third processing unit is also configured to generate a QoE measurement report based on the measurement result of the current QoE measurement when the application layer based on the terminal detects that the terminal meets the trigger event.
[0025] Optionally, the measurement reporting device further includes: a fourth processing unit; the fourth processing unit is configured to perform QoE measurement based on the application layer of the terminal after receiving QoE measurement configuration information sent by the access network device, so as to obtain a QoE measurement cache; the fourth processing unit is also configured to re-perform QoE measurement when the QoE measurement cache is greater than a preset cache; the fourth processing unit is also configured to generate a QoE measurement report based on the measurement result of the current QoE measurement when the application layer of the terminal detects that the terminal meets the trigger event.
[0026] Optionally, the measurement reporting device further includes: a fifth processing unit; the fifth processing unit is configured to perform QoE measurement based on the application layer of the terminal after receiving QoE measurement configuration information sent by the access network device; the fifth processing unit is also configured to end the QoE measurement after a second preset time period to obtain a QoE measurement report.
[0027] Optionally, the QoE measurement report includes at least one of the following: Protocol Data Unit (PDU) session measurement information and Quality of Service (QoS) flow measurement information; wherein, the PDU session measurement information is obtained by performing QoE measurement on the PDU session based on the QoE measurement configuration information; and the QoS flow measurement information is obtained by performing QoE measurement on the QoS flow based on the QoE measurement configuration information.
[0028] Thirdly, a measurement reporting device is provided, including a memory and a processor; the memory is used to store computer execution instructions, and the processor is connected to the memory via a bus; when the measurement reporting device is running, the processor executes the computer execution instructions stored in the memory to cause the measurement reporting device to perform the measurement reporting method described in the first aspect.
[0029] The measurement reporting device can be a network device or a component of a network device, such as a chip system within the network device. This chip system supports the network device in implementing the functions involved in the first aspect and any of its possible implementations, such as acquiring, determining, and transmitting the data and / or information involved in the aforementioned measurement reporting method. The chip system includes a chip, but may also include other discrete devices or circuit structures.
[0030] Fourthly, a computer-readable storage medium is provided, comprising computer-executable instructions that, when executed on a computer, cause the computer to perform the measurement reporting method described in the first aspect.
[0031] Fifthly, a computer program product is also provided, which includes computer instructions that, when executed on a measurement reporting device, cause the measurement reporting device to perform the measurement reporting method as described in the first aspect above.
[0032] It should be noted that the aforementioned computer instructions may be stored, in whole or in part, on a computer-readable storage medium. This computer-readable storage medium may be packaged together with the processor of the measurement reporting device, or it may be packaged separately from the processor of the measurement reporting device; this application does not limit this.
[0033] The descriptions of the second, third, fourth, and fifth aspects of this application can be referenced to the detailed description of the first aspect.
[0034] In the embodiments of this application, the names of the aforementioned measurement and reporting devices do not limit the devices or functional modules themselves. In actual implementation, these devices or functional modules may appear under other names. For example, the receiving unit may also be called a receiving module, receiver, etc. As long as the functions of each device or functional module are similar to those of this application, they fall within the scope of the claims of this application and their equivalents.
[0035] The technical solution provided in this application brings at least the following beneficial effects:
[0036] Based on any of the above aspects, this application provides a measurement reporting method, comprising: a terminal receiving QoE measurement configuration information sent by an access network device. The QoE measurement configuration information is used to instruct the terminal to report a QoE measurement report when a trigger event is met. Subsequently, when it is determined that the terminal meets the trigger event, the terminal can send a QoE measurement report to the access network device. The QoE measurement report is generated based on QoE measurement performed using the QoE measurement configuration information.
[0037] As can be seen from the above, since the QoE measurement configuration information received by the terminal is used to instruct the terminal to report a QoE measurement report when a trigger event is met, the terminal can send a QoE measurement report to the access network device when it determines that the trigger event is met, thereby improving the real-time performance of QoE measurement. Thus, when the trigger event is a network failure between the terminal and the access network device, the terminal can promptly send a QoE measurement report to the access network device, thereby meeting the real-time requirements of industrial application scenarios. The beneficial effects of the first, second, third, fourth, and fifth aspects of this application can all be referred to in the above analysis of beneficial effects, and will not be repeated here. Attached Figure Description
[0038] Figure 1 A schematic diagram illustrating a master-slave response mode provided in an embodiment of this application;
[0039] Figure 2 A schematic diagram of a periodic firing pattern provided in an embodiment of this application;
[0040] Figure 3 This is a schematic diagram of the structure of a measurement reporting system provided in an embodiment of this application;
[0041] Figure 4 A schematic diagram of the hardware structure of a measurement reporting device provided in this application embodiment;
[0042] Figure 5 A flowchart illustrating a measurement reporting method provided in this application embodiment. Figure 1 ;
[0043] Figure 6 A flowchart illustrating a measurement reporting method provided in this application embodiment. Figure 2 ;
[0044] Figure 7 A flowchart illustrating a measurement reporting method provided in this application embodiment. Figure 3 ;
[0045] Figure 8 A flowchart illustrating a measurement reporting method provided in this application embodiment. Figure 4 ;
[0046] Figure 9 A flowchart illustrating a measurement reporting method provided in this application embodiment. Figure 5 ;
[0047] Figure 10 A flowchart illustrating a measurement reporting method provided in this application embodiment. Figure 6 ;
[0048] Figure 11A flowchart illustrating a measurement reporting method provided in this application embodiment. Figure 7 ;
[0049] Figure 12 A flowchart illustrating a measurement reporting method provided in this application embodiment. Figure 8 ;
[0050] Figure 13 A flowchart illustrating a measurement reporting method provided in this application embodiment. Figure 9 ;
[0051] Figure 14 This is a schematic diagram of a measurement reporting device provided in an embodiment of this application. Detailed Implementation
[0052] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0053] It should be noted that in the embodiments of this application, the words "exemplary" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the words "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.
[0054] To facilitate a clear description of the technical solutions of the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish the same or similar items with essentially the same function and effect. Those skilled in the art can understand that the terms "first" and "second" are not intended to limit the quantity or execution order.
[0055] As described in the background section, QoE measurement is the most effective means of measuring network quality. For traditional video services and XR services, QoE measurement is mainly based on the collection and reporting of application layer data based on user experience.
[0056] Currently, most existing QoE measurement methods have poor real-time reporting capabilities, such as failing to promptly report QoE measurement reports after equipment failure. However, industrial applications have higher real-time requirements, needing to promptly report QoE measurement reports after equipment experiences network failures. Therefore, existing QoE measurement methods cannot meet the real-time requirements of industrial applications.
[0057] When 5G networks carry industrial field network real-time communication (RT) services, the requirements for end-to-end latency, service experience, and user experience reporting measurements must meet the real-time requirements of these services. The bottleneck for real-time performance lies on the radio side of the 5G network. Changes in radio channel quality, such as changes in line-of-sight (LOS) and non-line-of-sight (NLOS) paths, fast fading, and frequency-selective fading, can lead to packet loss or errors in air interface transmission, thus affecting latency. Furthermore, because radio-side time-frequency resources are limited, and because frame structure and scheduling resource constraints differ from wired transmission, air interface latency is uncertain. Therefore, devices in industrial application scenarios need to promptly report QoE measurement reports so that the 5G RAN can quickly and in real-time update its scheduling strategies.
[0058] The following are several existing QoE measurement methods:
[0059] (1) The core network equipment and network management equipment trigger the collection and reporting of application layer data of user equipment (UE), and transmit the data to user equipment (UE) through the base station.
[0060] The network management equipment or core network equipment issues QoE measurement configuration information according to the rules set by the operator's staff. Then, the base station transmits the QoE measurement configuration information to the UE, so that the UE can initiate, collect, and report QoE measurements based on the QoE measurement configuration information.
[0061] In this process, QoE measurement is triggered by core network equipment or network management equipment. UE cannot directly trigger QoE measurement based on events, thus affecting the timeliness and accuracy of QoE reporting.
[0062] (2) QoE collection and reporting triggered based on buffer level.
[0063] In the 3rd Generation Partnership Project (3GPP) Release 18 QoE enhancement discussion, buffer level-triggered RVQoE reporting was determined. In this approach, the network side configures a threshold value for the buffer level. When the buffer level is lower than or higher than the threshold value, the UE is triggered to perform QoE reporting.
[0064] Although this method is based on event-triggered QoE reporting, the triggering event is only the buffer level, i.e., the data to be transmitted, which is suitable for QoE measurement of large packet services such as video. However, this event is not suitable for periodic small packet services in industrial application scenarios. Therefore, it cannot be applied to industrial application scenarios and cannot meet the real-time requirements.
[0065] (3) Quality of Service (QoS) monitoring function.
[0066] The QoS monitoring function was defined in 3GPP Release 16. This function can realize end-to-end latency segmentation statistics, mainly including core network latency and wireless access network (RAN) latency. Its measurement granularity is based on the Quality of Service (QoS) flow per user. Its latency measurement method is the average air interface latency of upload (UL) / download (DL) over a period of time. Therefore, the QoS monitoring function cannot reflect the performance of current network transmission and carried services in real time, such as at the millisecond (ms) level, and thus cannot be applied to industrial application scenarios.
[0067] Furthermore, in industrial applications, different industrial protocols employ different mechanisms to monitor network quality and determine whether network failures (also known as downtime) have occurred. Common industrial protocol modes include master-slave response mode and periodic peer-to-peer mode. Common industrial protocols include Modbus, Profinet, and Entecnet / IP.
[0068] Figure 1 This diagram illustrates a master-slave response mode. The Modbus protocol primarily uses the master-slave response mode for judgment, such as... Figure 1 As shown, the condition for determining a network failure between the terminal and the base station is: if the sending end sends an application layer message to the receiving end within the watchdog timer (WDT), and the sending end does not receive the application layer response message sent by the receiving end, then it can be determined that a network failure has occurred between the sending end and the receiving end.
[0069] Figure 2 A schematic diagram of a periodic transmission pattern is shown. The Profinet and Entecnet / IP protocols primarily use a periodic transmission pattern for decision-making, such as... Figure 2As shown, the criteria for determining a network failure between the terminal and the base station are: within a CT (Cyclestalling Time), the sending end sends an application layer message to the receiving end, and within multiple consecutive CTs (or survival times), i.e., CT*WDT (e.g., WDT is 3), the sending end does not receive an application layer response message from the receiving end. Therefore, a network failure between the sending and receiving ends can be determined. In the 3GPP protocol, the survival time can be CT*WDT. In TS22.261, the survival time is defined as: the time that an application consuming a communication service may continue to run without an anticipated message.
[0070] To address the aforementioned issues, this application provides a measurement reporting method, comprising: a terminal receiving QoE measurement configuration information sent by an access network device. The QoE measurement configuration information instructs the terminal to report a QoE measurement report when a trigger event is met. Subsequently, when it is determined that the terminal meets the trigger event, the terminal can send a QoE measurement report to the access network device. The QoE measurement report is generated based on QoE measurements performed using the QoE measurement configuration information.
[0071] As shown above, since the QoE measurement configuration information received by the terminal is used to instruct the terminal to report a QoE measurement report when a trigger event is met, the terminal can send a QoE measurement report to the access network device when it determines that the trigger event is met, thereby improving the real-time performance of QoE measurement. Thus, when the trigger event is a network failure between the terminal and the access network device, the terminal can promptly send a QoE measurement report to the access network device, thereby meeting the real-time requirements of industrial application scenarios.
[0072] This measurement reporting method is applicable to measurement reporting systems. Figure 3 One structure of the measurement reporting system is shown. For example... Figure 3 As shown, the measurement reporting system includes: access network device 301 and terminal 302.
[0073] The access network device 301 and the terminal 302 are connected in communication.
[0074] In this application, the access network device 301 can send QoE measurement configuration information to the terminal 302 and receive the QoE measurement report reported by the terminal 302, so that the access network device 301 can update the scheduling policy according to the QoE measurement report.
[0075] Terminal 302 can be used to receive QoE measurement configuration information sent by access network device 301. When terminal 302 determines that a trigger event is met, terminal 302 can generate a QoE measurement report and send the QoE measurement report to access network device 301.
[0076] It should be understood that in industrial applications, the service types with high requirements for real-time performance and latency are RT (Real-Time) services and Isochronous Real-Time Communication (IRT) services. RT services are suitable for scenarios with periodic data exchange, such as communication between input / output (IO) controllers and IO devices, with a communication period typically less than 10 milliseconds. For IRT services, the capabilities of 5G networks (mainly air interface latency) are insufficient to meet the service requirements. Therefore, this solution primarily targets RT services in industrial field networks within industrial application scenarios.
[0077] Optionally, the access network device 301 can be a base station or other types of electronic equipment in the access network, and this application embodiment does not limit this.
[0078] Optionally, the aforementioned terminal may be a device that provides voice and / or data connectivity to a user, a handheld device with wireless connectivity, or other processing device connected to a wireless modem. The terminal may communicate with one or more core networks via a radio access network (RAN). The terminal may be a mobile terminal, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal, or a portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile device that exchanges voice and / or data with the radio access network, such as a mobile phone, tablet computer, laptop computer, netbook, or personal digital assistant (PDA).
[0079] The basic hardware structure of terminal 302 includes Figure 4 The components included in the measurement reporting device are shown below. Figure 4 Taking the measurement and reporting device shown as an example, the hardware structure of terminal 302 is introduced.
[0080] like Figure 4 The diagram shown is a hardware structure schematic of a measurement reporting device provided in an embodiment of this application. The measurement reporting device includes a processor 21, a memory 22, a communication interface 23, and a bus 24. The processor 21, memory 22, and communication interface 23 are connected via the bus 24.
[0081] Processor 21 is the control center of the measurement reporting device. It can be a single processor or a collective term for multiple processing elements. For example, processor 21 can be a general-purpose central processing unit (CPU) or other general-purpose processors. Among them, the general-purpose processor can be a microprocessor or any conventional processor.
[0082] As one embodiment, processor 21 may include one or more CPUs, for example Figure 4 CPU 0 and CPU 1 are shown in the diagram.
[0083] The memory 22 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto.
[0084] In one possible implementation, the memory 22 can exist independently of the processor 21. The memory 22 can be connected to the processor 21 via a bus 24 and is used to store instructions or program code. When the processor 21 calls and executes the instructions or program code stored in the memory 22, it can implement the measurement reporting method provided in the following embodiments of this application.
[0085] In this embodiment, the software programs stored in the memory 22 differ for terminal 302, resulting in different functions implemented by terminal 302. The functions performed by each device will be described in conjunction with the following flowchart.
[0086] In another possible implementation, the memory 22 can also be integrated with the processor 21.
[0087] Communication interface 23 is used for connecting the measurement reporting device to other devices via a communication network, such as Ethernet, wireless access network, or wireless local area network (WLAN). Communication interface 23 may include a receiving unit for receiving data and a sending unit for sending data.
[0088] Bus 24 can be an industry standard architecture (ISA) bus, a peripheral component interconnect (PCI) bus, or an extended industry standard architecture (EISA) bus, etc. This bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 4 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.
[0089] It should be pointed out that, Figure 4 The structure shown does not constitute a limitation on the measurement reporting device, except Figure 4 In addition to the components shown, the measurement reporting device may include more or fewer components than illustrated, or combine certain components, or have different component arrangements.
[0090] The measurement reporting method provided in the embodiments of this application will be described in detail below with reference to the accompanying drawings.
[0091] The measurement reporting method provided in this application embodiment is applied to... Figure 3 Terminal 302 in the measurement reporting system shown, such as Figure 5 As shown, the measurement reporting method provided in this application includes:
[0092] S501, The terminal receives QoE measurement configuration information sent by the access network device.
[0093] Among them, the QoE measurement configuration information is used to instruct the terminal to report a QoE measurement report when a trigger event is met.
[0094] Specifically, the access network device can send QoE measurement configuration information to the terminal. The terminal can receive the QoE measurement configuration information sent by the access network device at its access layer. Then, the terminal can transmit the QoE measurement configuration information to its application layer, enabling the terminal to perform QoE measurements based on the application layer.
[0095] Optionally, the QoE measurement configuration information may include: the identifier of the trigger event and the parameter configuration information of the trigger event. Since there can be multiple types of trigger events, the trigger event can be characterized by its identifier.
[0096] Optionally, the QoE measurement configuration information can be configured for access network devices (such as base stations) or for operation administration and maintenance (OAM) network management / core network devices, and can be transparently transmitted to the terminal through the access network devices.
[0097] Optionally, the QoE measurement report may include trigger events.
[0098] Optionally, the terminal's application layer protocol can be divided into a master-slave response mode (also known as master-slave mode) protocol and a periodic communication mode (also known as communication mode) protocol.
[0099] Optionally, the triggering event is an event corresponding to the terminal's application layer protocol. The triggering event can be: when no application layer response message is received from the access network device within a first preset period, the terminal is triggered to report a QoE measurement report. The application layer response message is used to respond to the first application layer message sent by the terminal to the access network device within the first preset period.
[0100] It should be understood that this event is an application layer protocol in the master-slave response mode of the terminal. In this way, it is possible to determine whether the terminal meets the triggering conditions based on the existing application layer protocol of the terminal, without making major changes to the application layer protocol of the terminal. Only a small amount of information exchange is required between the application layer of the terminal and the terminal chip (5G module).
[0101] Specifically, within the first preset period, the sending end sends a first application layer message to the receiving end, while the receiving end sends an application layer response message to the sending end. Therefore, if the terminal (i.e., the sending end) does not receive the application layer response message sent by the access network device (i.e., the receiving end) within the first preset period, the terminal can determine that a network failure has occurred between the terminal and the access network device, thereby triggering the terminal to report a QoE measurement report.
[0102] Optionally, the triggering event is an event corresponding to the terminal's application layer protocol. The triggering event can be: when no second application layer message is received from the access network device within multiple consecutive second preset periods, the terminal is triggered to report a QoE measurement report.
[0103] It should be understood that this event is a periodic application layer protocol sent by the terminal. In this way, it is possible to determine whether the terminal meets the triggering conditions based on the existing application layer protocol of the terminal. There is no need to make major changes to the application layer protocol of the terminal. Only a small amount of information exchange is required between the application layer of the terminal and the terminal chip (5G module).
[0104] Specifically, the sending end (or receiving end) sends a second application layer response message to the receiving end within a second preset period. Correspondingly, the receiving end (or sending end) also sends a second application layer message to the sending end within the second preset period. Therefore, if the terminal (i.e., the sending end or the receiving end) does not receive a second application layer message from the access network device (i.e., the receiving end or the sending end) within multiple consecutive second preset periods, the terminal can determine that a network failure has occurred between the terminal and the access network device, thereby triggering the terminal to report a QoE measurement report.
[0105] Furthermore, since the QoE measurement configuration information can also include the identifier of the trigger event, it can also include parameter configuration information for the trigger event, such as the size of the first preset period, the size of the second preset period, and the number of second preset periods. Moreover, the QoE measurement report can also include the trigger event, allowing access network devices to obtain the trigger event reported by the QoE measurement and thus adjust their scheduling strategies based on the trigger event.
[0106] S502. When it is determined that the terminal meets the trigger event, the terminal sends a QoE measurement report to the access network equipment.
[0107] The QoE measurement report is generated based on the QoE measurement configuration information.
[0108] Specifically, after receiving the QoE configuration information, the terminal can perform QoE measurements at the terminal's application layer based on the QoE measurement configuration information to obtain a QoE measurement report. Next, the terminal can determine whether it meets the trigger event. When the trigger event is met, the terminal can send the QoE measurement report to the access network device. In this way, when the event corresponding to the terminal's application layer protocol occurs, the terminal can promptly send the QoE measurement report to the access network device, thereby meeting the real-time requirements in industrial scenarios.
[0109] Optionally, the QoE measurement reports reported by the terminal can be visible to the RAN. Since these reports are visible to the RAN, access network devices can parse them to obtain the terminal's quality of experience information. Because the access network devices are close to the terminal, they can quickly update scheduling policies using the QoE measurement reports, thus meeting the real-time requirements of industrial applications.
[0110] In addition, some metrics in the RAN-visible QoE measurement report can be RAN-visible, thereby reducing air interface resource overhead.
[0111] Optionally, when the access network device is a base station, the QoE measurement report can be visible to the base station.
[0112] Optionally, after receiving the QoE measurement report, the access network device can send the QoE measurement report to the OAM network management / application data acquisition and processing unit / application layer server, so that the OAM network management / application data acquisition and processing unit / application layer server can perform big data analysis, network optimization and other operations based on the QoE measurement report.
[0113] Optionally, trigger events in the QoE measurement report and the QoE measurement configuration information can be represented by identifiers. For example, if the trigger event ID is 2, then the trigger event can be represented as follows: {Event Trigger ID = 2, 1}. Here, 1 indicates that the event has occurred (i.e., a failure has occurred between the access network device and the terminal).
[0114] It should be noted that since both QoE measurement and determination of trigger conditions are performed at the terminal's application layer, after receiving the QoE measurement configuration information at the access layer, the terminal can transmit this information to the application layer, enabling QoE measurement to be performed at the application layer. Furthermore, since the QoE measurement report is generated at the terminal's application layer, while sending the report to the access network device occurs at the terminal's access layer, the terminal first transmits the QoE measurement report to its access layer before finally sending it to the access network device.
[0115] For example, assuming the access network device is a base station, and the terminal's application layer protocol is a master-slave response mode protocol. For application layer protocols in industrial application scenarios, the first preset period is generally WDT (Warning Time Limit), which is greater than 20 milliseconds. Terminals in industrial application scenarios typically include robot programmable logic controllers (PLCs), grippers, valve islands, etc. When the terminal does not receive an application layer response message (also called an application layer response data packet) from the base station within the WDT, the terminal can determine that a network failure has occurred between the terminal and the base station, thereby triggering the QoE measurement report to be submitted. Thus, since the triggering event is an event corresponding to the terminal's application layer protocol, and QoE is also measured at the terminal's application layer, there is no need to make extensive modifications to the terminal's application layer protocol; only a small amount of information exchange between the terminal's application layer and the terminal chip (5G module) is required.
[0116] QoE measurement reports can include trigger events, i.e., no application layer application message is received within the WDT time, which can be represented as follows: {WDT, Response for Transmitter = 0}.
[0117] When the application layer protocol is a periodic transmission mode protocol (such as Profinet RT or Entecnet / IP protocol over 5G), multiple second preset periods are either Cycle Time (CT) * WDT, or the survival time specified in the 3GPP protocol. If the terminal does not receive any application layer messages sent by the base station within CT * WDT, the terminal can determine that a network failure has occurred between the terminal and the base station, thereby triggering QoE measurement reporting.
[0118] QoE measurement reports can include trigger events, i.e., no application layer application message is received within CT*WDT or survival time, which can be represented as follows: {survival time, Received Packet = 0}.
[0119] In some embodiments, combined with Figure 5 ,like Figure 6 As shown, in the above S501, the terminal receiving the QoE measurement configuration information sent by the access network device specifically includes:
[0120] S601. The terminal receives QoE measurement configuration information sent by the access network device based on the terminal's access layer.
[0121] Specifically, since the terminal interacts with the access network device through the access layer, the terminal can receive QoE measurement configuration information sent by the access network device based on the access layer.
[0122] In some embodiments, combined with Figure 6 ,like Figure 7 As shown, in S502 above, the terminal sending a QoE measurement report to the access network device specifically includes:
[0123] S701. The terminal sends a QoE measurement report to the access network equipment based on the terminal's access layer.
[0124] Specifically, since QoE measurement is performed at the application layer, after receiving QoE measurement configuration information at the access layer, the terminal can transmit the QoE measurement configuration information to the application layer and perform QoE measurement based on the application layer to obtain a QoE measurement report. Then, when a trigger event is determined to be met, the terminal can transmit the QoE measurement report to the access layer and send the QoE measurement report to the access network device based on the access layer.
[0125] In some embodiments, combined with Figure 7 ,like Figure 8 As shown, the measurement reporting method provided in this application embodiment further includes:
[0126] S801, The terminal receives MDT measurement configuration information sent by the access network device based on the terminal's access layer.
[0127] Specifically, access network devices can also send MDT measurement configuration information to terminals, enabling terminals to report MDT measurement reports. Terminals can receive the MDT measurement configuration information sent by access network devices at the access layer. Furthermore, since MDT measurements are performed at the access layer, terminals can perform MDT measurements at the access layer based on the MDT measurement configuration information.
[0128] S802. When the terminal's access layer receives a QoE measurement report sent by the terminal's application layer, the terminal generates an MDT measurement report based on the terminal's access layer and sends the MDT measurement report to the access network equipment.
[0129] The MDT measurement report is obtained by performing MDT measurements at the access layer based on the MDT measurement configuration information.
[0130] Specifically, since the terminal sends QoE data to the access network device at the access layer, while the action of triggering the QoE measurement report is implemented at the application layer, after the QoE measurement is triggered and reported, the terminal transmits the QoE measurement report from the application layer to the access layer. Thus, when the QoE measurement report is transmitted to the access layer, the terminal can terminate the MDT measurement to obtain the MDT measurement report and send it to the access network device. This allows the access network device to perform network optimization based on the MDT measurement report, including big data analysis and AI-based operations.
[0131] In this way, MDT measurements and QoE measurements can be correlated, and access network devices can obtain MDT measurement reports when network failures occur, namely, the main network performance indicators such as Reference Signal Receiving Power (RSRP), Reference Signal Receiving Quality (RSRQ), location information measurement, and wireless link failure.
[0132] It should be understood that access network devices can send QoE measurement configuration information and MDT measurement configuration information separately to the same terminal, and associate the QoE measurement report and MDT measurement report through timestamps. There are two main types of MDT measurement reporting: logged MDT and immediate MDT (real-time reporting of MDT). For industrial application scenarios, in order to quickly obtain network performance measurement results, the immediate MDT method is mostly used.
[0133] Optionally, the QoE measurement report may include at least one of the following: Protocol Data Unit (PDU) session measurement information and Quality of Service (QoS) flow measurement information. The PDU session measurement information is obtained by performing QoE measurements on the PDU session based on the QoE measurement configuration information. The QoS flow measurement information is obtained by performing QoE measurements on the QoS flow based on the QoE measurement configuration information. In this way, the terminal can associate certain specific PDU sessions and / or QoS flows to obtain measurement information for QoE measurements of the PDU sessions and / or QoS flows.
[0134] In some embodiments, such as Figure 9 As shown, the measurement reporting method provided in this application embodiment further includes:
[0135] S901. After receiving the QoE measurement configuration information sent by the access network device, the terminal performs QoE measurement based on the terminal's application layer.
[0136] Specifically, after receiving the QoE measurement configuration information, the terminal can transmit the QoE measurement configuration information to the application layer and perform QoE measurement based on the application layer.
[0137] S902. When the terminal-based application layer detects that the terminal meets the trigger event, the terminal generates a QoE measurement report based on the measurement results of the current QoE measurement.
[0138] Specifically, when the terminal detects a trigger event at the application layer, it terminates the ongoing QoE measurement and generates a QoE measurement report based on the current QoE measurement results. This allows the terminal to report QoE measurement results in the event of a network failure, enabling access network devices to better adjust their operations based on these reports.
[0139] In some embodiments, such as Figure 10 As shown, the measurement reporting method provided in this application embodiment further includes:
[0140] S1001. After receiving the QoE measurement configuration information sent by the access network device within a first preset time period, the terminal performs QoE measurement based on the terminal's application layer.
[0141] Specifically, after receiving the QoE measurement configuration information, the terminal can transmit the QoE measurement configuration information to the application layer, and perform QoE measurement at the application layer after a first preset time period (also known as offset).
[0142] S1002. When the terminal-based application layer detects that the terminal meets the trigger event, the terminal generates a QoE measurement report based on the measurement results of the current QoE measurement.
[0143] Specifically, when the terminal detects a trigger event based on the application layer, it terminates the ongoing QoE measurement and generates a QoE measurement report based on the current QoE measurement results. This allows the terminal to report QoE measurement reports when network failures occur, enabling access network devices to better adjust based on these reports. Furthermore, the shorter QoE measurement time also saves terminal resources.
[0144] In some embodiments, such as Figure 11 As shown, the measurement reporting method provided in this application embodiment further includes:
[0145] S1101. After receiving the QoE measurement configuration information sent by the access network device, the terminal performs QoE measurement based on the terminal's application layer to obtain the QoE measurement cache.
[0146] Specifically, after receiving the QoE measurement configuration information, the terminal can transmit the QoE measurement configuration information to the application layer and perform QoE measurements at the application layer. Furthermore, the terminal can store the measured data locally to obtain a QoE measurement cache.
[0147] S1102. When the QoE measurement buffer is greater than the preset buffer, the terminal re-performs the QoE measurement.
[0148] Specifically, when the locally stored QoE measurement cache is larger than the preset cache (the preset cache can be bufferlevel), the terminal ends the QoE measurement and discards the locally stored QoE measurement cache. Then, the terminal performs the QoE measurement again and repeats this process.
[0149] S1103. When the terminal-based application layer detects that the terminal meets the trigger event, the terminal generates a QoE measurement report based on the measurement results of the current QoE measurement.
[0150] Specifically, when the terminal determines that it meets the trigger event based on the application layer protocol, the terminal ends the ongoing QoE measurement to obtain a QoE measurement report. In this way, the terminal can report the QoE measurement report when a network failure occurs, so that access network devices can better adjust based on the QoE measurement report when a network failure occurs.
[0151] In some embodiments, such as Figure 12 As shown, the measurement reporting method provided in this application embodiment further includes:
[0152] S1201. After receiving the QoE measurement configuration information sent by the access network device, the terminal performs QoE measurement based on the terminal's application layer.
[0153] Specifically, after receiving the QoE measurement configuration information, the terminal can transmit the QoE measurement configuration information to the application layer and perform QoE measurement based on the application layer.
[0154] S1202. After the second preset time period, the terminal ends the QoE measurement to obtain a QoE measurement report.
[0155] Specifically, the terminal can end the QoE measurement after a second preset time period following the initial QoE measurement and store the obtained QoE measurement report locally. This way, when the terminal meets a trigger event, it can directly report the locally stored QoE measurement report.
[0156] In some embodiments, the above description mainly focuses on the various steps of the measurement reporting method provided in this application. The complete flow of the measurement reporting method provided in this application is then described below in conjunction with the above embodiments. For example... Figure 13 As shown, the measurement reporting method provided in this application embodiment specifically includes:
[0157] S1301, the OAM network management / core network equipment generates RAN-visible QoE measurement configuration information and sends it to the base station (i.e., the access network equipment in this application).
[0158] S1302. After receiving the QoE measurement configuration information, the base station will transmit the QoE measurement configuration information to the terminal.
[0159] S1303. The terminal receives QoE measurement configuration information based on the access layer and transmits the QoE measurement configuration information to the terminal's application layer.
[0160] S1304. The terminal performs QoE measurement based on the QoE measurement configuration information at the application layer.
[0161] S1305. When the terminal determines that the trigger event is met based on the terminal's application layer, the terminal ends the QoE measurement to obtain a QoE measurement report visible to the RAN.
[0162] Correspondingly, when the terminal determines that the trigger event is not met, the terminal continues to perform QoE measurement.
[0163] S1306. The terminal transmits the QoE measurement report to the access layer at the application layer.
[0164] S1307. The terminal sends a RAN-visible QoE measurement report to the base station at the access layer.
[0165] Specifically, the terminal can send RAN-visible QoE measurement reports to the base station via Radio Resource Control (RRC) signaling or Medium Access Control (MAC) layer messages. However, the real-time performance of RRC signaling is inferior to that of MAC layer messages.
[0166] S1308. After receiving the QoE measurement report, the base station sends the QoE measurement report to the OAM network management / core network equipment.
[0167] It should be understood that after receiving the QoE measurement report, the OAM network management / core network equipment can perform big data analysis, network optimization, and other operations based on the QoE measurement report.
[0168] Specifically, when the OAM network management / core network device stores an index table of triggered events in the QoE measurement configuration information, the triggered events in the QoE measurement report can be represented by IDs.
[0169] The foregoing mainly describes the solutions provided by the embodiments of this application from a methodological perspective. To achieve the above functions, it includes corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0170] This application embodiment can divide the measurement reporting device into functional modules according to the above method example. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. Optionally, the module division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.
[0171] like Figure 14 The diagram shown is a structural schematic of a measurement reporting device provided in an embodiment of this application. This measurement reporting device can be used to perform... Figures 5-13 The method for reporting measurements as shown in any of the examples. Figure 14 The measurement reporting device shown includes: a receiving unit 1401 and a transmitting unit 1402;
[0172] The receiving unit 1401 is used to receive Quality of Experience (QoE) measurement configuration information sent by the access network device; the QoE measurement configuration information is used to instruct the terminal to report a QoE measurement report when a trigger event is met. For example, combined with... Figure 5 The receiving unit 1401 is used to execute S501.
[0173] The sending unit 1402 is configured to send a QoE measurement report to the access network device when it is determined that the terminal meets the trigger event; the QoE measurement report is generated based on QoE measurement configuration information. For example, combined with... Figure 5 The sending unit 1402 is used to execute S502.
[0174] Optionally, the triggering event is an event corresponding to the terminal's application layer protocol; the triggering event is: when no application layer response message is received from the access network device within the first preset period, the terminal is triggered to report a QoE measurement report; the application layer response message is used to respond to the first application layer message sent by the terminal to the access network device within the first preset period.
[0175] Optionally, the triggering event is an event corresponding to the terminal's application layer protocol; the triggering event is: when no second application layer message is received from the access network device within multiple consecutive second preset periods, the terminal is triggered to report a QoE measurement report.
[0176] Optionally, the receiving unit 1401 is specifically used for: receiving QoE measurement configuration information sent by the access network device based on the terminal's access layer. For example, in conjunction with... Figure 6 The receiving unit 1401 is used to execute S601.
[0177] Optionally, the sending unit 1402 is specifically used for: sending a QoE measurement report from the terminal-based access layer to the access network device. For example, in conjunction with... Figure 7 The sending unit 1402 is used to execute S701.
[0178] Optionally, the measurement reporting device further includes: a first processing unit 1403;
[0179] The transmitting unit 1402 is also used for receiving minimized drive test (MDT) measurement configuration information sent by the access network equipment based on the terminal at the access layer. For example, combined with Figure 8 The sending unit 1402 is used to execute S801.
[0180] The first processing unit 1403 is configured to generate an MDT measurement report based on the terminal's access layer when it receives a QoE measurement report sent by the terminal's application layer at the terminal's access layer. For example, in conjunction with... Figure 8 The first processing unit 1403 is used to execute S802.
[0181] The sending unit 1402 is also used to send an MDT measurement report to the access network equipment; the MDT measurement report is obtained by performing MDT measurements based on MDT measurement configuration information. For example, combined with Figure 8 The sending unit 1402 is used to execute S802.
[0182] Optionally, the measurement reporting device further includes: a second processing unit 1404;
[0183] The second processing unit 1404 is configured to perform QoE measurement based on the application layer of the terminal after receiving QoE measurement configuration information sent by the access network device. For example, in combination with Figure 9 The second processing unit 1404 is used to execute S901.
[0184] The second processing unit 1404 is further configured to generate a QoE measurement report based on the measurement results of the current QoE measurement when the application layer based on the terminal detects that the terminal meets a trigger event. For example, in conjunction with Figure 9 The second processing unit 1404 is used to execute S902.
[0185] Optionally, the measurement reporting device further includes: a third processing unit 1405;
[0186] The third processing unit 1405 is configured to perform QoE measurement based on the application layer of the terminal after receiving QoE measurement configuration information sent by the access network device within a first preset time period. For example, in conjunction with... Figure 10 The third processing unit 1405 is used to execute S1001.
[0187] The third processing unit 1405 is further configured to generate a QoE measurement report based on the measurement results of the current QoE measurement when the application layer based on the terminal detects that the terminal meets the trigger event. For example, combined with Figure 10 The third processing unit 1405 is used to execute S1002.
[0188] Optionally, the measurement reporting device further includes: a fourth processing unit 1406;
[0189] The fourth processing unit 1406 is configured to perform QoE measurement based on the application layer of the terminal after receiving QoE measurement configuration information sent by the access network device, in order to obtain a QoE measurement buffer. For example, combined with Figure 11 The fourth processing unit 1406 is used to execute S1101.
[0190] The fourth processing unit 1406 is also used to re-perform the QoE measurement when the QoE measurement buffer is larger than the preset buffer. For example, combined with Figure 11 The fourth processing unit 1406 is used to execute S1102.
[0191] The fourth processing unit 1406 is further configured to generate a QoE measurement report based on the measurement results of the current QoE measurement when the application layer based on the terminal detects that the terminal meets a trigger event. For example, in conjunction with Figure 11 The fourth processing unit 1406 is used to execute S1103.
[0192] Optionally, the measurement reporting device may further include: a fifth processing unit 1407;
[0193] The fifth processing unit 1407 is used to perform QoE measurement based on the application layer of the terminal after receiving QoE measurement configuration information sent by the access network device. For example, combined with Figure 12 The fifth processing unit 1407 is used to execute S1201.
[0194] The fifth processing unit 1407 is also configured to terminate the QoE measurement after a second preset time period to obtain a QoE measurement report. For example, in conjunction with Figure 12 The fifth processing unit 1407 is used to execute S1202.
[0195] Optionally, the QoE measurement report includes at least one of the following: Protocol Data Unit (PDU) session measurement information and Quality of Service (QoS) flow measurement information; wherein, the PDU session measurement information is obtained by performing QoE measurement on the PDU session based on the QoE measurement configuration information; and the QoS flow measurement information is obtained by performing QoE measurement on the QoS flow based on the QoE measurement configuration information.
[0196] This application also provides a computer-readable storage medium, which includes computer-executable instructions. When the computer-executable instructions are run on a computer, the computer performs the measurement reporting method provided in the above embodiments.
[0197] This application also provides a computer program that can be directly loaded into a memory and contains software code. After being loaded and executed by a computer, the computer program can implement the measurement reporting method provided in the above embodiments.
[0198] Those skilled in the art will recognize that, in one or more of the examples above, the functions described in this application can be implemented using hardware, software, firmware, or any combination thereof. When implemented in software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer-readable storage media and communication media, wherein communication media include any medium that facilitates the transmission of a computer program from one place to another. Storage media can be any available medium accessible to a general-purpose or special-purpose computer.
[0199] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.
[0200] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and other division methods may exist in actual implementation. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the shown or discussed mutual couplings, direct couplings, or communication connections may be through some interfaces; indirect couplings or communication connections between devices or units may be electrical, mechanical, or other forms. Units described as separate components may or may not be physically separate; components shown as units may be one physical unit or multiple physical units, i.e., they may be located in one place or distributed in multiple different places. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0201] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.
[0202] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
Claims
1. A measurement reporting method, characterized in that, The method includes: The terminal receives Quality of Experience (QoE) measurement configuration information sent by the access network device. This QoE measurement configuration information instructs the terminal to report a QoE measurement report when a trigger event is met. The trigger event is an event corresponding to the terminal's application layer protocol. The trigger event is: when no application layer response message is received from the access network device within a first preset period, the terminal is triggered to report the QoE measurement report; the application layer response message is used to respond to a first application layer message sent by the terminal to the access network device within the first preset period; or, when no second application layer message is received from the access network device within multiple consecutive second preset periods, the terminal is triggered to report the QoE measurement report. When it is determined that the terminal meets the trigger event, a QoE measurement report is sent to the access network device; the QoE measurement report is generated based on the QoE measurement configuration information.
2. The method of claim 1, wherein, The received Quality of Experience (QoE) measurement configuration information sent by the access network device includes: The terminal-based access layer receives QoE measurement configuration information sent by the access network device.
3. The method of claim 2, wherein, Sending the QoE measurement report to the access network device includes: The terminal's access layer sends the QoE measurement report to the access network device.
4. The method of claim 3, wherein, The method further includes: The terminal receives the minimized drive test (MDT) measurement configuration information sent by the access network device from the access layer. When the access layer of the terminal receives the QoE measurement report sent by the application layer of the terminal, it generates an MDT measurement report based on the access layer of the terminal and sends the MDT measurement report to the access network device; the MDT measurement report is obtained by performing MDT measurement based on the MDT measurement configuration information.
5. The method according to claim 3, characterized in that, The method further includes: After receiving the QoE measurement configuration information sent by the access network device, the QoE measurement is performed based on the application layer of the terminal; When the application layer of the terminal detects that the terminal meets the trigger event, the QoE measurement report is generated based on the measurement result of the current QoE measurement.
6. The method according to claim 3, characterized in that, The method further includes: After receiving the QoE measurement configuration information sent by the access network device, the QoE measurement is performed based on the application layer of the terminal. When the application layer of the terminal detects that the terminal meets the trigger event, the QoE measurement report is generated based on the measurement result of the current QoE measurement.
7. The method according to claim 3, characterized in that, The method further includes: After receiving the QoE measurement configuration information sent by the access network device, the QoE measurement is performed based on the application layer of the terminal to obtain the QoE measurement cache; When the QoE measurement buffer is larger than the preset buffer, the QoE measurement is performed again; When the application layer of the terminal detects that the terminal meets the trigger event, the QoE measurement report is generated based on the measurement result of the current QoE measurement.
8. The method according to claim 3, characterized in that, The method further includes: After receiving the QoE measurement configuration information sent by the access network device, the QoE measurement is performed based on the application layer of the terminal; After a second preset time period, the QoE measurement ends to obtain the QoE measurement report.
9. The method according to claim 3, characterized in that, The QoE measurement report includes at least one of the following: Protocol Data Unit (PDU) session measurement information and Quality of Service (QoS) flow measurement information; wherein the PDU session measurement information is obtained by performing QoE measurement on the PDU session based on the QoE measurement configuration information; and the QoS flow measurement information is obtained by performing QoE measurement on the QoS flow based on the QoE measurement configuration information.
10. A measurement reporting device, characterized in that, The device includes: a receiving unit and a transmitting unit; The receiving unit is configured to receive Quality of Experience (QoE) measurement configuration information sent by the access network device; the QoE measurement configuration information is used to instruct the terminal to report a QoE measurement report when a trigger event is met; the trigger event is an event corresponding to the application layer protocol of the terminal; the trigger event is: when no application layer response message is received from the access network device within a first preset period, the terminal is triggered to report the QoE measurement report; the application layer response message is used to respond to a first application layer message sent by the terminal to the access network device within the first preset period; or, when no second application layer message is received from the access network device within multiple consecutive second preset periods, the terminal is triggered to report the QoE measurement report; The sending unit is configured to send a QoE measurement report to the access network device when it is determined that the terminal meets the trigger event; the QoE measurement report is generated based on the QoE measurement configuration information.
11. A measurement and reporting device, characterized in that, It includes a memory and a processor; the memory is used to store computer execution instructions, and the processor is connected to the memory via a bus; when the measurement reporting device is running, the processor executes the computer execution instructions stored in the memory to cause the measurement reporting device to perform the measurement reporting method as described in any one of claims 1-9.
12. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes computer-executable instructions that, when executed on a computer, cause the computer to perform the measurement reporting method as described in any one of claims 1-9.