A method, device, equipment and medium for monitoring terminal touch screen failure without perception

Abstract

The application discloses a kind of terminal touch screen fault monitoring methods, device, equipment and medium without perception, it is related to terminal touch screen fault detection technical field.The method includes: operating heat map construction process: during normal operation of terminal, the touch control operation data of terminal is collected without perception, the data in each preset period is built corresponding operating heat map;History standard heat map construction process: the multiple operating heat maps built in preset time length are fused, calibrated, and history standard heat map is built as the core benchmark for determining whether touch screen exists fault;Fault monitoring process: the touch control operation data in recent preset period is collected, and operating heat map is built as recent heat map, and whether touch screen exists fault is determined according to the difference between recent heat map and history standard heat map.The application provides a kind of terminal touch screen fault monitoring methods, device, equipment and medium without perception, realize the no-perception monitoring of touch screen fault, improve user experience.

Description

Technical Field

[0001] This invention relates to the field of terminal touchscreen fault detection technology, and in particular to a non-intrusive terminal touchscreen fault monitoring method, device, equipment and medium. Background Technology

[0002] Most existing Android terminal touch screen fault detection technologies adopt active detection mode, such as sending test commands to the touch IC, scanning the touch electrodes, and collecting the original capacitance data of the touch IC to achieve fault detection.

[0003] The existing active detection model has the following problems: 1. The detection process consumes terminal hardware resources, interferes with normal user operation, and cannot achieve seamless monitoring.

[0004] 2. It is mostly used for obvious faults (such as complete touch loss and screen skipping), but it is difficult to identify hidden faults such as micro short circuits, local sensitivity loss, and hidden electrode aging.

[0005] 3. Lacking long-term data accumulation and comparison, judging faults based solely on single-frame abnormal data results in a high misjudgment rate and makes it impossible to predict potential faults in advance. Summary of the Invention

[0006] The technical problem to be solved by the present invention is to provide a non-perceptible terminal touch screen fault monitoring method, device, equipment and medium that does not inject test signals and does not interfere with the user's normal operation. By comparing historical and recent usage through operation heatmaps, non-perceptible monitoring of touch screen faults is achieved, thereby improving the user experience.

[0007] In a first aspect, the present invention provides a non-intrusive terminal touchscreen fault monitoring method, comprising: Operation heatmap construction process: During normal operation of the terminal, touch operation data of the terminal is collected imperceptibly, and the data in each preset period is used to construct the corresponding operation heatmap; Historical standard heatmap construction process: Multiple operation heatmaps built within a preset time period are merged and calibrated to construct a historical standard heatmap, which serves as the core benchmark for determining whether a touchscreen is faulty; Fault monitoring process: Collect touch operation data within a recent preset period, construct an operation heatmap as the recent heatmap, and determine whether the touch screen has a fault based on the difference between the recent heatmap and the historical standard heatmap.

[0008] Furthermore, the historical standard heatmap is constructed by fusing touch frequency data from multiple heatmaps, removing abnormal data, and adjusting the weights of designated areas.

[0009] Furthermore, the step of determining whether the touchscreen is faulty based on the differences between recent heatmaps and historical standard heatmaps specifically includes: A fault determination threshold is preset for each difference parameter. Each calculated difference parameter is compared with its corresponding fault determination threshold. If any of the following conditions are met, the touchscreen is determined to have a hardware fault: A certain continuous area of ​​the touchscreen has no touch records in the recent heat map, and the area of ​​this area accounts for more than the threshold of no touch area in the total area of ​​the touchscreen. The ratio of the difference between the recent touch frequency of a certain area of ​​the touchscreen and the touch frequency of the corresponding area in the historical standard heatmap to the historical standard frequency exceeds the frequency difference rate threshold. The distribution of touch coordinates for the same operation on the touchscreen in recent heatmaps deviates from the coordinate distribution of the corresponding operation in historical standard heatmaps by more than the coordinate offset threshold.

[0010] Furthermore, the method also includes a fault silent handling process: after determining that there is a fault in the touch screen, adaptive processing is performed according to the severity of the fault, including automatic calibration and compensation for minor faults; local lightweight prompts that do not interfere with user operation are provided for moderate and severe faults, while the fault information is stored locally on the terminal and on the terminal management platform.

[0011] Secondly, the present invention provides a non-intrusive terminal touchscreen fault monitoring device, comprising: The operation heatmap construction module is used to collect touch operation data of the terminal without being noticed during normal operation of the terminal, and to construct the corresponding operation heatmap from the data in each preset period. The historical standard heatmap construction module is used to merge and calibrate multiple operation heatmaps built within a preset time period to construct a historical standard heatmap, which serves as the core benchmark for determining whether the touchscreen is faulty. The fault monitoring module is used to collect touch operation data within a recent preset period, construct an operation heatmap as a recent heatmap, and determine whether the touchscreen has a fault based on the difference between the recent heatmap and the historical standard heatmap.

[0012] Furthermore, in the construction of the historical standard heatmap, the historical standard heatmap is constructed by fusing touch frequency data from multiple heatmaps, removing abnormal data, and adjusting the weights of specified areas.

[0013] Furthermore, the fault monitoring module determines whether the touchscreen is faulty based on the differences between recent heatmaps and historical standard heatmaps, specifically including: A fault determination threshold is preset for each difference parameter. Each calculated difference parameter is compared with its corresponding fault determination threshold. If any of the following conditions are met, the touchscreen is determined to have a hardware fault: A certain continuous area of ​​the touchscreen has no touch records in the recent heat map, and the area of ​​this area accounts for more than the threshold of no touch area in the total area of ​​the touchscreen. The ratio of the difference between the recent touch frequency of a certain area of ​​the touchscreen and the touch frequency of the corresponding area in the historical standard heatmap to the historical standard frequency exceeds the frequency difference rate threshold. The distribution of touch coordinates for the same operation on the touchscreen in recent heatmaps deviates from the coordinate distribution of the corresponding operation in historical standard heatmaps by more than the coordinate offset threshold.

[0014] Furthermore, it also includes a fault silent processing module, which is used to adaptively process the fault according to its severity after determining that the touch screen has a fault. This includes automatic calibration and compensation for minor faults; providing local lightweight prompts for moderate and severe faults without interfering with user operation; and storing the fault information on the terminal local and on the terminal management platform.

[0015] Thirdly, the present invention provides an electronic device including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the method described in the first aspect.

[0016] Fourthly, the present invention provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method described in the first aspect.

[0017] The technical solutions provided in the embodiments of the present invention have at least the following technical effects or advantages: Achieve seamless monitoring: By embedding a low-power background service into the Android system, real user touch operation data is collected without injecting test signals or interfering with normal user operation, thus achieving seamless monitoring of touch screen malfunctions and improving user experience. Strong ability to identify hidden faults: By generating a user operation heatmap and comparing historical and recent usage, it can accurately identify hidden faults that are difficult to detect with existing technologies, such as micro short circuits, local sensitivity degradation, and hidden electrode aging. It can also predict potential faults in advance. Low false alarm rate: Standard heatmaps are constructed based on long-term historical data and calibrated in combination with user operating habits. Faults are determined by comparing multi-dimensional difference parameters, which effectively reduces the false alarm rate and improves the accuracy of fault monitoring. Highly adaptable: It adopts a dynamic sampling mechanism to reduce power consumption and supports terminal adaptation for different models, Android versions, and touch ICs, making it widely applicable; User-friendly fault handling: Fault information is silently recorded in the background, minor faults are automatically compensated, and moderate and severe faults are given a light prompt. This does not interfere with user operation, but can provide timely feedback on the fault situation, which is convenient for subsequent maintenance.

[0018] The above description is merely an overview of the technical solution of the present invention. In order to better understand the technical means of the present invention and to implement it in accordance with the contents of the specification, and in order to make the above and other objects, features and advantages of the present invention more apparent and understandable, specific embodiments of the present invention are described below. Attached Figure Description

[0019] The present invention will be further described below with reference to the accompanying drawings and embodiments.

[0020] Figure 1 This is a flowchart illustrating the overall process of the method in Embodiment 1 of the present invention. Figure 2 This is the operation heatmap constructed in the method of Embodiment 1 of the present invention; Figure 3 This is a schematic diagram of the fault log in the method of Embodiment 1 of the present invention; Figure 4 This is a schematic diagram of the device in Embodiment 2 of the present invention; Figure 5 This is a schematic diagram of the electronic device in Embodiment 3 of the present invention; Figure 6 This is a schematic diagram of the structure of the medium in Embodiment 4 of the present invention. Detailed Implementation

[0021] This invention provides a non-intrusive terminal touchscreen fault monitoring method, device, equipment, and medium that does not inject test signals or interfere with normal user operation. By comparing historical and recent usage data using an operation heatmap, it achieves non-intrusive touchscreen fault monitoring and improves user experience.

[0022] The overall concept of the technical solutions in the embodiments of the present invention is as follows: This invention addresses the problems of existing detection methods, such as interference with user operation, weak ability to identify hidden faults, and high false positive rate, and achieves seamless, long-term online, and accurate monitoring of touch screen faults on Android terminals.

[0023] 1. Seamlessly collect user touch operation data A low-power background monitoring service is embedded in the Android terminal Framework layer or driver layer. During normal operation of the terminal, the monitoring service collects real touch operation data of the user on the touch screen without being noticed. The touch operation data includes, but is not limited to, touch coordinates, click frequency, swipe trajectory, and touch response latency. No test signals are injected during the collection process, no additional hardware resources are occupied, and the user's foreground operation and normal operation of the terminal are not interfered with.

[0024] The low-power background monitoring service adopts a dynamic sampling mechanism. When the terminal is in a state of screen-on and user operation, the sampling frequency is increased; when the terminal is in a state of screen-on but no operation or screen-off, the sampling frequency is reduced or sampling is stopped to reduce terminal power consumption.

[0025] 2. Construct an operational heatmap Based on the collected real user touch operation data, the touch frequency and touch duration of each area of ​​the touch screen are statistically analyzed according to a preset period to generate a touch screen usage heat map for the corresponding period. The heat map uses pixels as the unit and the color depth represents the touch activity level of the corresponding area, realizing a visual presentation of the usage status of each area of ​​the touch screen.

[0026] During the generation of the heatmap, the collected touch operation data is noise-reduced, and abnormal data such as single touch duration less than a preset threshold (e.g., 50ms) and touch coordinates exceeding the effective area of ​​the touch screen are removed to ensure the accuracy of the heatmap.

[0027] 3. Establish historical standard heat map benchmarks When the terminal is in normal working condition, multiple heat maps generated from touch operation data collected within a continuously preset time period are fused and calibrated to eliminate abnormal operation data such as accidental touches and malicious clicks. Combined with the user's long-term operating habits, a historical standard heat map is constructed as the core benchmark for determining whether the touch screen is faulty. 4. Generate recent heatmaps and perform comparative analysis. Real-time collection of user touch operation data within a recent preset period generates a recent heat map. The recent heat map is then compared precisely with the historical standard heat map established in step S3, region by region. The difference parameters between the two are calculated, including the area ratio of non-touch areas, touch frequency difference rate, and touch coordinate offset, thus quantifying the degree of difference between the two. 5. Touchscreen Fault Diagnosis A fault determination threshold is preset for each difference parameter. Each calculated difference parameter is compared with its corresponding fault determination threshold. If any of the following conditions are met, the touchscreen is determined to have a hardware fault: A certain continuous area of ​​the touchscreen has no touch records in the recent heat map, and the area of ​​this area accounts for more than the threshold of no touch area in the total area of ​​the touchscreen. The ratio of the difference between the recent touch frequency of a certain area of ​​the touchscreen and the touch frequency of the corresponding area in the historical standard heatmap to the historical standard frequency exceeds the frequency difference rate threshold. The distribution of touch coordinates for the same operation on the touchscreen in recent heatmaps has an offset from the coordinate distribution of the corresponding operation in historical standard heatmaps that exceeds the coordinate offset threshold. 6. Silent Fault Handling After determining that the touchscreen is faulty, the system silently records complete fault information (including fault area, fault type, and fault occurrence time) in the background. It then adaptively processes the fault based on its severity, automatically calibrating and compensating for minor faults, and providing local, lightweight prompts for moderate and severe faults without interfering with user operations. At the same time, the fault information is stored on the terminal and on the terminal management platform to provide accurate reference for subsequent maintenance.

[0028] The above method only requires processing at the software logic layer. The detection process does not consume terminal hardware resources, does not interfere with normal user operation, and only collects data. A heat map is generated from the collected data, and faults are determined based on threshold values. Example 1

[0029] This embodiment provides a seamless terminal touchscreen fault monitoring method, such as... Figure 1 As shown, including; S1. Operation Heatmap Construction Process: During normal terminal operation, touch operation data of the terminal is collected imperceptibly, and the data within each preset period is used to construct a corresponding operation heatmap, such as... Figure 2 As shown. The touch operation data includes, but is not limited to, touch coordinates, click frequency, swipe trajectory, touch response latency, etc.

[0030] In one specific embodiment, applied to a smart POS terminal (Android 13 system, 5.99-inch touchscreen), a low-power background monitoring service is embedded in the Android Framework layer. This service runs in the background by default. When the phone screen is on and the user performs touch operations (such as clicking, swiping, or inputting), it collects touch coordinates (accurate to pixels), click frequency, swipe trajectory, and touch response latency at a frequency of 10Hz. When the phone screen is on and there is no operation for more than 30 seconds, the sampling frequency drops to 1Hz, and there is no sampling when the screen is off, thus avoiding excessive power consumption. No prompts are displayed during the collection process, so it does not affect the user's normal use.

[0031] S2. Historical Standard Heatmap Construction Process: Multiple operation heatmaps constructed within a preset time period are merged and calibrated to construct a historical standard heatmap, which serves as the core benchmark for determining whether a touchscreen malfunctions. In this embodiment, a preset cycle of 1 day is used to collect all touch operation data collected on that day. The data is processed to reduce noise and remove abnormal data such as single touch duration of less than 50ms and touch coordinates that exceed the effective area of ​​the touch screen (720×1440 pixels). Then, the touch frequency of each area is counted by pixel to generate a touch screen usage heatmap for the day. The area with a touch frequency ≥100 times is displayed in dark red, 50-99 times in light red, 10-49 times in yellow, 1-9 times in light blue, and 0 times in white.

[0032] Touch operation data was collected continuously for 30 days to generate 30 operation heatmaps. The touch frequency data of the 30 heatmaps were merged, and abnormal data such as malicious clicks (such as continuous rapid clicks on the same coordinate more than 100 times / minute) and accidental touches (such as accidental touches on the pocket) were removed. Based on user operation habits, the weights of the navigation bar (bottom 300-pixel area) and the input method area (middle 400-800-pixel area) were adjusted (weight coefficient 1.2) to construct a historical standard heatmap as a benchmark for normal touch screen operation.

[0033] S3. Fault monitoring process: Collect touch operation data within a recent preset period, construct an operation heatmap as a recent heatmap, and determine whether the touchscreen has a fault based on the difference between the recent heatmap and the historical standard heatmap.

[0034] In this embodiment, operation heatmaps from the past 7 days are collected and fused to generate a recent heatmap. The recent heatmap is then compared pixel by pixel with the historical standard heatmap, and the following difference parameters are calculated: the proportion of non-touch area, the touch frequency difference rate, and the touch coordinate offset. Among them, the touch frequency difference rate = |recent frequency - historical standard frequency| / historical standard frequency × 100%, and the touch coordinate offset = the Euclidean distance between the average coordinate of the same recent operation and the average coordinate of the historical standard operation.

[0035] The method of determining whether a touchscreen is faulty based on the differences between recent heatmaps and historical standard heatmaps specifically includes: Preset fault judgment thresholds corresponding to each difference parameter, for example: The threshold for non-touch area is 5%, the threshold for frequency difference rate is 30%, and the threshold for coordinate offset is 10 pixels; Then, each calculated difference parameter is compared with its corresponding fault determination threshold. If any of the following conditions are met, the touchscreen is determined to have a hardware fault: A certain continuous area of ​​the touchscreen has no touch records in the recent heat map, and the area of ​​this area accounts for more than the threshold of no touch area in the total area of ​​the touchscreen. The ratio of the difference between the recent touch frequency of a certain area of ​​the touchscreen and the touch frequency of the corresponding area in the historical standard heatmap to the historical standard frequency exceeds the frequency difference rate threshold. The distribution of touch coordinates for the same operation on the touchscreen in recent heatmaps deviates from the coordinate distribution of the corresponding operation in historical standard heatmaps by more than the coordinate offset threshold.

[0036] In this embodiment, upon comparison, if the upper left corner of the touchscreen (coordinate range 0-200×0-200 pixels) has no touch records in the recent heatmap, the area of ​​this region is 40,000 pixels, accounting for approximately 3% of the total touchscreen area (720×1440=1036800 pixels), which does not exceed the threshold for no-touch area; if the right-center area of ​​the touchscreen (coordinate range 400-600×600-900 pixels) has a recent touch frequency of 28 times, the historical standard frequency is 50 times, and the frequency difference rate is 44%, which exceeds the threshold of 30%, then it is determined that there is a sensitivity reduction fault in this area.

[0037] S4. The silent fault handling process: After determining that there is a fault in the touch screen, it will adaptively handle the fault according to its severity, including automatic calibration and compensation for minor faults; and local lightweight prompts for moderate and severe faults that do not interfere with user operation. At the same time, the fault information will be stored locally on the terminal and on the terminal management platform.

[0038] In this embodiment, the system silently records fault information in the background (fault area: 400-600×600-900 pixels, slightly right of center; fault type: local sensitivity decrease; fault time: current time). An automatic calibration and compensation program is initiated to adjust the touch sensitivity parameters of this area. After calibration, the system continues to monitor the touch data of this area. Simultaneously, the fault information is stored in the phone's local fault log for the user to review during subsequent repairs. Figure 3 As shown.

[0039] This embodiment processes the data at the software logic layer. The detection process does not consume terminal hardware resources or interfere with normal user operation; it only collects data. A heatmap is generated from the collected data, and faults are determined based on threshold values.

[0040] Based on the same inventive concept, this application also provides an apparatus corresponding to the method in Embodiment 1, as detailed in Embodiment 2. Example 2

[0041] This embodiment provides a seamless terminal touchscreen fault monitoring device, such as... Figure 4 As shown, it includes: The operation heatmap construction module is used to collect touch operation data of the terminal without being noticed during normal operation of the terminal, and to construct the corresponding operation heatmap from the data in each preset period. The historical standard heatmap construction module is used to merge and calibrate multiple operation heatmaps built within a preset time period to construct a historical standard heatmap, which serves as the core benchmark for determining whether the touchscreen is faulty. The fault monitoring module is used to collect touch operation data within a recent preset period, construct an operation heatmap as a recent heatmap, and determine whether the touchscreen has a fault based on the difference between the recent heatmap and the historical standard heatmap.

[0042] Preferably, in the construction of the historical standard heatmap, the historical standard heatmap is constructed by fusing touch frequency data from multiple heatmaps, removing abnormal data, and adjusting the weights of specified areas.

[0043] Preferably, the fault monitoring module determines whether the touchscreen is faulty based on the differences between recent heatmaps and historical standard heatmaps, specifically including: A fault determination threshold is preset for each difference parameter. Each calculated difference parameter is compared with its corresponding fault determination threshold. If any of the following conditions are met, the touchscreen is determined to have a hardware fault: A certain continuous area of ​​the touchscreen has no touch records in the recent heat map, and the area of ​​this area accounts for more than the threshold of no touch area in the total area of ​​the touchscreen. The ratio of the difference between the recent touch frequency of a certain area of ​​the touchscreen and the touch frequency of the corresponding area in the historical standard heatmap to the historical standard frequency exceeds the frequency difference rate threshold. The distribution of touch coordinates for the same operation on the touchscreen in recent heatmaps deviates from the coordinate distribution of the corresponding operation in historical standard heatmaps by more than the coordinate offset threshold.

[0044] Preferably, it also includes a fault silence handling module, which is used to adaptively handle the fault according to the severity of the fault after determining that the touch screen has a fault, including automatic calibration compensation for minor faults; providing local lightweight prompts for moderate and severe faults without interfering with user operation, and storing the fault information on the terminal local and the terminal management platform.

[0045] Since the apparatus described in Embodiment 2 of the present invention is an apparatus used to implement the method of Embodiment 1 of the present invention, those skilled in the art can understand the specific structure and variations of the apparatus based on the method described in Embodiment 1 of the present invention, and therefore will not be described again here. All apparatuses used in the method of Embodiment 1 of the present invention fall within the scope of protection of the present invention.

[0046] Based on the same inventive concept, this application provides an electronic device embodiment corresponding to Embodiment 1, as detailed in Embodiment 3. Example 3

[0047] This embodiment provides an electronic device, such as... Figure 5 As shown, it includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it can implement any of the embodiments in Example 1.

[0048] Since the electronic device described in this embodiment is the device used to implement the method in Embodiment 1 of this application, those skilled in the art can understand the specific implementation method and various variations of the electronic device in this embodiment based on the method described in Embodiment 1 of this application. Therefore, how the electronic device implements the method in the embodiment of this application will not be described in detail here. Any device used by those skilled in the art to implement the method in the embodiment of this application falls within the scope of protection of this application.

[0049] Based on the same inventive concept, this application provides a storage medium corresponding to Embodiment 1, as detailed in Embodiment 4. Example 4

[0050] This embodiment provides a computer-readable storage medium, such as... Figure 6 As shown, a computer program is stored thereon, which, when executed by a processor, can implement any of the embodiments in Example 1.

[0051] Since the computer-readable storage medium described in this embodiment is the same computer-readable storage medium used to implement the method in Embodiment 1 of this application, those skilled in the art can understand the specific implementation methods and various variations of the computer-readable storage medium in this embodiment based on the method described in Embodiment 1 of this application. Therefore, how this computer-readable storage medium implements the method in the embodiments of this application will not be described in detail here. Any computer-readable storage medium used by those skilled in the art to implement the method in the embodiments of this application falls within the scope of protection of this application.

[0052] The technical solutions provided in the embodiments of the present invention have at least the following technical effects or advantages: Achieve seamless monitoring: By embedding a low-power background service into the Android system, real user touch operation data is collected without injecting test signals or interfering with normal user operation, thus achieving seamless monitoring of touch screen malfunctions and improving user experience. Strong ability to identify hidden faults: By generating a user operation heatmap and comparing historical and recent usage, it can accurately identify hidden faults that are difficult to detect with existing technologies, such as micro short circuits, local sensitivity degradation, and hidden electrode aging. It can also predict potential faults in advance. Low false alarm rate: Standard heatmaps are constructed based on long-term historical data and calibrated in combination with user operating habits. Faults are determined by comparing multi-dimensional difference parameters, which effectively reduces the false alarm rate and improves the accuracy of fault monitoring. Highly adaptable: It adopts a dynamic sampling mechanism to reduce power consumption and supports terminal adaptation for different models, Android versions, and touch ICs, making it widely applicable; User-friendly fault handling: Fault information is silently recorded in the background, minor faults are automatically compensated, and moderate and severe faults are given a light prompt. This does not interfere with user operation, but can provide timely feedback on the fault situation, which is convenient for subsequent maintenance.

[0053] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0054] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0055] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0056] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0057] While specific embodiments of the present invention have been described above, those skilled in the art should understand that the specific embodiments described are merely illustrative and not intended to limit the scope of the present invention. Equivalent modifications and variations made by those skilled in the art in accordance with the spirit of the present invention should be covered within the scope of protection of the claims of the present invention.

Claims

1. A non-intrusive terminal touchscreen fault monitoring method, characterized in that, include: Operation heatmap construction process: During normal operation of the terminal, touch operation data of the terminal is collected imperceptibly, and the data in each preset period is used to construct the corresponding operation heatmap; Historical standard heatmap construction process: Multiple operation heatmaps built within a preset time period are merged and calibrated to construct a historical standard heatmap, which serves as the core benchmark for determining whether a touchscreen is faulty; Fault monitoring process: Collect touch operation data within a recent preset period, construct an operation heatmap as the recent heatmap, and determine whether the touch screen has a fault based on the difference between the recent heatmap and the historical standard heatmap.

2. The method according to claim 1, characterized in that: The historical standard heatmap is constructed by fusing touch frequency data from multiple heatmaps, removing abnormal data, and adjusting the weights of specified areas.

3. The method according to claim 1, characterized in that, The method of determining whether a touchscreen is faulty based on the differences between recent heatmaps and historical standard heatmaps specifically includes: A fault determination threshold is preset for each difference parameter. Each calculated difference parameter is compared with its corresponding fault determination threshold. If any of the following conditions are met, the touchscreen is determined to have a hardware fault: A certain continuous area of ​​the touchscreen has no touch records in the recent heat map, and the area of ​​this area accounts for more than the threshold of no touch area in the total area of ​​the touchscreen. The ratio of the difference between the recent touch frequency of a certain area of ​​the touchscreen and the touch frequency of the corresponding area in the historical standard heatmap to the historical standard frequency exceeds the frequency difference rate threshold. The distribution of touch coordinates for the same operation on the touchscreen in recent heatmaps deviates from the coordinate distribution of the corresponding operation in historical standard heatmaps by more than the coordinate offset threshold.

4. The method according to claim 1, characterized in that, The method also includes a fault silent handling process: after determining that the touch screen has a fault, adaptive handling is performed according to the severity of the fault, including automatic calibration and compensation for minor faults. Provide lightweight local prompts for moderate and severe faults without interfering with user operations, while storing fault information on the terminal and the terminal management platform.

5. A non-intrusive terminal touchscreen fault monitoring device, characterized in that, include: The operation heatmap construction module is used to collect touch operation data of the terminal without being noticed during normal operation of the terminal, and to construct the corresponding operation heatmap from the data in each preset period. The historical standard heatmap construction module is used to merge and calibrate multiple operation heatmaps built within a preset time period to construct a historical standard heatmap, which serves as the core benchmark for determining whether the touchscreen is faulty. The fault monitoring module is used to collect touch operation data within a recent preset period, construct an operation heatmap as a recent heatmap, and determine whether the touchscreen has a fault based on the difference between the recent heatmap and the historical standard heatmap.

6. The apparatus according to claim 5, characterized in that: In the construction of the historical standard heatmap, the historical standard heatmap is constructed by integrating touch frequency data from multiple heatmaps, removing abnormal data, and adjusting the weights of specified areas.

7. The apparatus according to claim 5, characterized in that, The fault monitoring module determines whether the touchscreen is faulty based on the differences between recent heatmaps and historical standard heatmaps, specifically including: A fault determination threshold is preset for each difference parameter. Each calculated difference parameter is compared with its corresponding fault determination threshold. If any of the following conditions are met, the touchscreen is determined to have a hardware fault: A certain continuous area of ​​the touchscreen has no touch records in the recent heat map, and the area of ​​this area accounts for more than the threshold of no touch area in the total area of ​​the touchscreen. The ratio of the difference between the recent touch frequency of a certain area of ​​the touchscreen and the touch frequency of the corresponding area in the historical standard heatmap to the historical standard frequency exceeds the frequency difference rate threshold. The distribution of touch coordinates for the same operation on the touchscreen in recent heatmaps deviates from the coordinate distribution of the corresponding operation in historical standard heatmaps by more than the coordinate offset threshold.

8. The apparatus according to claim 5, characterized in that, Also includes: The fault silent processing module is used to adaptively process the fault according to its severity after determining that there is a fault in the touch screen, including automatic calibration and compensation for minor faults. Provide lightweight local prompts for moderate and severe faults without interfering with user operations, while storing fault information on the terminal and the terminal management platform.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the method as described in any one of claims 1 to 4.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method as described in any one of claims 1 to 4.

Images